479 replies to this topic

[BladeRunner]

Was it pushed to you?

Sent from my Nexus 6P using Tapatalk

yes it was

[livinginkaos]

And they didn't get you hooked up?

Sent from my Nexus 6P using Tapatalk

[BladeRunner]

And they didn't get you hooked up?

Sent from my Nexus 6P using Tapatalk

Nah, they were just going to replace the device.

[gustavobap]

Hello, guys, this forum is really great. Thanks for your work SamuriHL.

I'm new to flashing android, can you guys help me figuring what is the problem ?

I have a motoE 2 LTE (XT1514 Surnia) that originally had Android 5.02, but it went to motorola for repair and came back with 6.0. Despite the upgrade, the bootloader screen still showed "software status: official".

Now I have unlocked the bootloader, installed TRWP and used it to flash the stock ROM again. I downloaded the XT1514_SURNIA_RETBR_DS_6.0_MPI24.65-39_cid12_subsidy-DEFAULT_CFC.xml ROM from this

Please Login or Register to see this Hidden Content

I found on xda-developers. The system works but the bootloader screen now says "software status: modified".

Before this process I made a backup using TWRP but even after restoring the bakcup image the message still didn't change back to "software status: official".

I appreciate any help

[SamuriHL]

You can't flash a stock ROM with twrp. It should be flashed with the house of moto.

Sent from my Nexus 6P using Tapatalk

[gustavobap]

Hey, SamurHL, I did already flash the ROM with RSD Lite, everything works fine, except for the message "Software Status: modified". There is a supersu folder that keeps being recreated even if I flash a new ROM, do you think this might be the problem ? The phone is not rooted, but unlocked (3)

[SamuriHL]

Something got missed in the flash.  My guess would be the boot image LOL.  On newer SuperSU versions, they modify the ramdisk in the boot image to provide root.  It's not added to system anymore.  So my guess is that the boot image didn't get flashed correctly.  You could post the swdl.txt file from RSD and we could take a look at what happened during your flash attempt.  Or you could simply retry with the House of Moto and post the output of what happens.

[gustavobap]

This is really weird, don't seems to be any problem in the log. There is only this timeout at the end, waiting for the phone to reboot, this is because it takes a long time to startup the first time after flashing.

I will give a try to house of moto and post the logs here also.

Thanks again for the help = )

 

Edit: Maybe something at this line ?

09/28/16 05:48:08  00002de8    Phone.cpp    1571    0    ERROR    Waiting for phone's handle is setted successfully after restart [430000 ms] completion. failed

 

28/16 05:39:10  The FlashLog key is turned off.
09/28/16 05:39:10  Multi upgrade started for 1 phones
09/28/16 05:39:10  [Device ID: 0] 1/20 getvar max-sparse-size
09/28/16 05:39:10  [Device ID: 0] 2/20 oem fb_mode_set
09/28/16 05:39:10  [Device ID: 0] 3/20 flash partition "gpt.bin"
09/28/16 05:39:11  [Device ID: 0] 4/20 flash bootloader "bootloader.img"
09/28/16 05:39:12  [Device ID: 0] 5/20 flash logo "logo.bin"
09/28/16 05:39:12  [Device ID: 0] 6/20 flash boot "boot.img"
09/28/16 05:39:15  [Device ID: 0] 7/20 flash recovery "recovery.img"
09/28/16 05:39:18  [Device ID: 0] 8/20 flash system "system.img_sparsechunk.0"
09/28/16 05:39:42  [Device ID: 0] 9/20 flash system "system.img_sparsechunk.1"
09/28/16 05:40:03  [Device ID: 0] 10/20 flash system "system.img_sparsechunk.2"
09/28/16 05:40:22  [Device ID: 0] 11/20 flash system "system.img_sparsechunk.3"
09/28/16 05:40:42  [Device ID: 0] 12/20 flash system "system.img_sparsechunk.4"
09/28/16 05:40:49  [Device ID: 0] 13/20 flash modem "NON-HLOS.bin"
09/28/16 05:40:54  [Device ID: 0] 14/20 erase modemst1
09/28/16 05:40:54  [Device ID: 0] 15/20 erase modemst2
09/28/16 05:40:54  [Device ID: 0] 16/20 flash fsg "fsg.mbn"
09/28/16 05:40:54  [Device ID: 0] 17/20 erase carrier
09/28/16 05:40:55  [Device ID: 0] 18/20 erase cache
09/28/16 05:40:55  [Device ID: 0] 19/20 erase userdata
09/28/16 05:40:57  [Device ID: 0] 20/20 oem fb_mode_clear
09/28/16 05:40:57  [Device ID: 0] reboot
09/28/16 05:40:57  CMultiFlashFlex::RebootPhone, waiting for phone to disconnect, status=2, state=0.
09/28/16 05:40:58  Removal, interface=28(0x0), device id=1636460.
09/28/16 05:40:58  CMultiFlashFlex::RebootPhone, waiting for phone to connect, status=3, state=4.
09/28/16 05:48:08  00002de8    Phone.cpp    1571    0    ERROR    Waiting for phone's handle is setted successfully after restart [430000 ms] completion. failed
09/28/16 05:48:08  CMultiFlashFlex::RebootPhone, unable to wait for phone, status=3, state=4.
09/28/16 05:48:08  [Device ID: 0] Please manually power up this phone.
09/28/16 05:55:18  00002de8    Phone.cpp    3974    -1    ERROR    CPhone::WaitForPhone timed out. Iteration-1
09/28/16 05:55:18  [Device ID: 0] Please manually power up this phone.
09/28/16 06:02:28  00002de8    Phone.cpp    3974    -1    ERROR    CPhone::WaitForPhone timed out. Iteration-2
09/28/16 06:02:28  [Device ID: 0] Please manually power up this phone.
09/28/16 06:08:36  Arrival, interface=36(0x0), device id=1636460.
09/28/16 06:08:36  [Device ID: 0] Waiting for others to finish current operation.
09/28/16 06:08:36  Arrival, interface=20(0x0), device id=1636460.
09/28/16 06:08:36  Arrival, interface=19(0x0), device id=1636460.
09/28/16 06:08:36  The FlashLog key is turned off.
09/28/16 06:08:36  FlashLog file is turned off.
09/28/16 06:08:36  Multi upgrade finished.

[SamuriHL]

Log looks ok.  I'm not sure what could be causing your issue.

[gustavobap]

How is it possible the supersu folder still there after flashing if even the bootloader is replaced ?

Also, do you know how does the bootloader check if the software is official ? I mean, this could be because the original ROM image was somehow modified ? Or because originally the phone had firmware with android 5.0.2 ?

[SamuriHL]

I can't explain the supersu folder since you flashed the whole stock rom and that should have removed all traces of supersu.  You even erased userdata so you're good there.

 

The downgrade to 5.0.2 probably is what is triggering the modified message.  I'm guessing Moto never released a 6.0 image anywhere?  Trying to find a 6.0 image would be a good idea.

[gustavobap]

SamuriHL, the currently flashed ROM is the 6.0 image I got from xda. The phone originally came with 5.0.2, but after going to motorola repair it came back with android 6.0 and Software Status: Official. Also, I found that the official TWRP

has issues with surnia, xda has a

Please Login or Register to see this Hidden Content

fixing this issues. Using squid's TRWP file manager there is no more a supersu folder at the root, so I guess twrp was mounting the supersu folder in case I wanted to install it.

 

Do you think it is worth a try to downgrade to original 5.0.2 image and then upgrade manually ? I have the ROM image downloaded from xda and already tryed to downgrade, but the flash fails in the gpt partition. You mention in the first page of this thread, when talking about house of moto features, that it will ask if you want to flash  GPT and TZ partitions, and you should answer NO if downgrading, is this the only difference in the procedure of flashing when downgrading ?

[SamuriHL]

Yea, that's the only difference but I would caution you against downgrading and then trying to apply an OTA update.  It could lead to a brick potentially.  If you've flashed TWRP it would say your software is not official so that could be the cause.  I wouldn't worry about it...if the device is working for you and you're happy with it, leave it as it is now.

[frankpettit]

Thank you so much. My Droid Razr Maxx XT912 would just get stuck on bootup at the red Droid eye. I really needed to download the data on my phone, so I couldn't just do a factory reset, that would wipe my data. I went to the Verizon store and they said it was too technical for them.

But I followed your instructions, and, amazingly, the phone rebooted. I did extract and back up my data. Yay. Still, time to buy a new phone...

[Murphman25]

Okay so I have been researching for weeks trying to understand this whole world of phone technology and what I can do to fix my stuck at boot-up XT926. I didn't want to be "that guy" but I really want help badly. To my (probably incorrect) knowledge I download House of Moto to the C drive. I did the snapdragon patch, and I searched the internet for hours trying to find a LINK THAT WORKS to some firmware! Then I finally found some, picked the newest version, ran the .jar and it said

"Custom recovery not found.

Using factory image: VRZ_XT926_9.8.1Q-79-1_CFC.xml.zip

ERROR: XML script not found in this factory image.  This is not yet supported."

 

I'm gonna be completely honest I have no idea what I am doing I just want to fix my phone. I used to think I was above average with technology knowledge but this is WAY WAY over my head.

 

If someone is willing to give me STEP-BY-STEP and I mean very literal STEP BY STEP instructions (and working links to everything) I would honestly compensate you with like $50 or something.

 

I know if I keep f%$king around I will just brick it, if someone can fix this for me I would love them forever.

 

Info:

My phone is "locked" not sure what that means not gonna lie. I don't want to do any fancy technical stuff with it I just want it to work. I don't care if it is rooted or not or if I can never root it, I just want my data. (Even then I always considered the XT926 decently powerful and not bloatey but what do I know I am a moron).

 

You can call my lazy all you want but there are 2 ways to get $#!+ done in life, pay people or do it yourself... and when I literally DON'T UNDERSTAND how to do it myself I know when to ask for help.

 

Also RSD was able to extract the XML but would not detect my phone, yes I am using USB 2.0 and yes I am using a factory Motorola cable, it says it on the cable in 3 different places. (but maybe it is broken idk)

[spainter]

The xml file you referenced is an old one. Dusting off my memory I believe that it is Jellybean not kitkat. You can flash the same version or newer file to a locked 926.

This is the newest file for the 926:

Please Login or Register to see this Hidden Content

Use that file with HOM 4.3 and it should work.

[Murphman25]

Nope :/

[Pmassey85]

Hey guys I have a problem and really hoping I can get some help. I have a Droid Turbo 2 through Verizon and a couple days ago a OTA update was pushed out, I had been putting off installing it then last night my gf was on my phone and accepted the update. Somehow or another the update got interrupted and now all the phone does and stay on the boot screen. Will simply following the steps for using house of moto and flashing the latest version of android fix this issue? please forgive me for I am ignorant when it comes to this. Thanks very much in advance.

[livinginkaos]

You should be able to. With a locked bootloader you are only able to flash same or newer builds to your device, so finding the appropriate firmware may be the issue. There are sites such as this -

Please Login or Register to see this Hidden Content

- that keep firmwares, so you can do some searching.

Now, not to deter you from using HoM, because it is a great tool, but if you have trouble locating the proper files, Verizon's Software tool is actually a good tool for those who just need a device fixed. It will detect your device, download the appropriate software from their servers then flash it for you.

Please Login or Register to see this Hidden Content

Sent from my Pixel XL using Tapatalk

[angel_626__]

Can someone help me, im trying to restore a bricked xt926 on Verizon