Database Info

unlock state relocks after reboot

Hi all,
I have a friend's nexus 5, that I try to unbrick. Unfortunally, and after dragging all threads about unlocking via fastboot, I'm still unable to fix his device.
The fact is, I'm able to unlock (fastboot oem unlock) , then when I reboot the bootloader, it's back locked.
I've tried to flash stock bootloader (for both nexus 5 bootloaders (HHZ11k, HHZ10x) but without success
The device is locked on a bootloop Google screen, impossible to access to recovery mode (via fastboot or via vol up + power)
Anybody's got an idea ?

here is a sequence of trying to update bootloader, you can see that I must unlock for allmost each step
Code:
./fastboot oem unlock
...
OKAY [ 2.596s]
finished. total time: 2.596s
./fastboot erase boot
erasing 'boot'...
OKAY [ 0.217s]
finished. total time: 0.217s
./fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.215s]
finished. total time: 0.215s
./fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.219s]
finished. total time: 0.219s
./fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.221s]
finished. total time: 0.221s
./fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.493s]
finished. total time: 0.493s
./fastboot flash bootloader bootloader-hammerhead-hhz11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.287s]
writing 'bootloader'...
OKAY [ 0.404s]
finished. total time: 0.691s
./fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
./fastboot oem unlock
...
OKAY [ 2.130s]
finished. total time: 2.130s
./fastboot oem unlock
...
OKAY [ 3.665s]
finished. total time: 3.665s
./fastboot flash radio radio-hammerhead-m8974a-1.0.25.0.23.img
sending 'radio' (42049 KB)...
OKAY [ 1.514s]
writing 'radio'...
OKAY [ 2.850s]
finished. total time: 4.364s
./fastboot oem unlock
...
OKAY [ 2.999s]
finished. total time: 2.999s
./fastboot -w update image-hammerhead-kot49h.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ10x
Baseband Version.....: M8974A-1.0.25.0.23
Serial Number........: 02ffc80f08e51d0d
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
FAILED
Device version-bootloader is 'HHZ10x'.
Update requires 'HHZ11k'.
finished. total time: 0.601s

You need to flash the right bootloader first before the rest can go through

yep, the fact is I can't find anywhere a bootloader to flash for my version (HHZ10x).
The only files I found are those from Google.
I've tried both for same result.
I've find updates from this thread but I can't boot in recovery mode (from fastboot mode or with fastboot boot recovery.img).
Maybe there is a way to flash those files (from above thread) but I've tried with files (like bootloader.aboot.img, bootloader.imgdata.img, bootloader.rpm.img, etc, ...) without success (FAILED (remote: invalid bootloader image))

benoit.bds said:
yep, the fact is I can't find anywhere a bootloader to flash for my version (HHZ10x).
The only files I found are those from Google.
I've tried both for same result.
I've find updates from this thread but I can't boot in recovery mode (from fastboot mode or with
Code:
fastboot boot recovery.img
).
Maybe there is a way to flash those files (from above thread) but I've tried with files (like bootloader.aboot.img, bootloader.imgdata.img, bootloader.rpm.img, etc, ...) without success (
Code:
FAILED (remote: invalid bootloader image)
)
Click to expand...
Click to collapse
Looks like you have corrupted memory and nothing is going to work. Time to rma.

jd1639 said:
Looks like you have corrupted memory and nothing is going to work. Time to rma.
Click to expand...
Click to collapse
i agree.

I don't want to come off as alarmist, but I'm starting to see a worrying trend here. If you look at other threads over the past few days, there have been quite a few people with dying flash chips (myself included). There are a few differences in some of the symptoms, but the most common being that 'fastboot oem unlock / lock' fails to stick. It's like the chip is left in some random state of corruption, and unable to be written to. If I were I betting man, I'd say we can expect to see a flood of these posts in coming days.
I would recommend to anyone with an unlocked bootloader, that you get it locked asap and reset the tamper flag too, just in case this same issue occurs with your phone in future, and you need to RMA it.
To the OP, can you confirm whether the device has been previously unlocked, and whether anything was done to the device leading up to the issue? I'm hoping that if this issue is happening to both locked and unlocked devices that Google / LG will have to take the issue seriously should it become an epidemic.

:crying:
My friend has admitted that his n5 had fallen into water...
He gave it for deoxidation + battery replace, but they didn't manage to boot it more than fastboot mode, so I proposed him to give it a try.
To reply to sir_earl, the device was early bought, stock rom and official OTAs.
Anyway, thank you all for your responses !
Regards

Help - device not booting

I was already on stock 4.4.2. Used RSD to flash it when the phone was on JB. My phone's suddenly not botting anymore though. Just stock on the boot animation screen. I tried flashing back the same firmware, but I get "Phone Returned Failed" error on RSD lite every time
What can I do? My phone was completely stock. Bootloader wasn't unlocked.
*edit*: Boot animation runs fine. Then it's just stuck at the orb thingy which just keeps going.

pyromaniac1 said:
I was already on stock 4.4.2. Used RSD to flash it when the phone was on JB. My phone's suddenly not botting anymore though. Just stock on the boot animation screen. I tried flashing back the same firmware, but I get "Phone Returned Failed" error on RSD lite every time
What can I do? My phone was completely stock. Bootloader wasn't unlocked.
*edit*: Boot animation runs fine. Then it's just stuck at the orb thingy which just keeps going.
Click to expand...
Click to collapse
Need more details on "fail." Just saying it failed won't narrow down anything.
Sent from my HTC6525LVW using Tapatalk

RikRong said:
Need more details on "fail." Just saying it failed won't narrow down anything.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Tried flashing VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml, get this error.

pyromaniac1 said:
Tried flashing VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml, get this error.
Click to expand...
Click to collapse
you have to edit the xml file and completely remove the line containing "gpt" in that error. the partition table cant be changed/downgraded once upgraded.

bweN diorD said:
you have to edit the xml file and completely remove the line containing "gpt" in that error. the partition table cant be changed/downgraded once upgraded.
Click to expand...
Click to collapse
I did
still luck. Whatever item it tries to flash it returns the same error. I even deleted everything in between that to system.img. Gives the same error trying to flash system.img

pyromaniac1 said:
I did
still luck. Whatever item it tries to flash it returns the same error. I even deleted everything in between that to system.img. Gives the same error trying to flash system.img
Click to expand...
Click to collapse
try this, its not the same as the utility in the dev forum, its a modified version.

bweN diorD said:
try this, its not the same as the utility in the dev forum, its a modified version.
Click to expand...
Click to collapse
Flashed the XML with RSD lite. still the same error. Removed the GPT line and tried again. Same thing.

pyromaniac1 said:
Flashed the XML with RSD lite. still the same error. Removed the GPT line and tried again. Same thing.
Click to expand...
Click to collapse
Mmk, do not use rsd, use the bat file at the bottom of the directory. You defeated the purpose of it by using rsd.
Sent from my G2 running SlimKat

bweN diorD said:
Mmk, do not use rsd, use the bat file at the bottom of the directory. You defeated the purpose of it by using rsd.
Sent from my G2 running SlimKat
Click to expand...
Click to collapse
Ran the script twice. Managed to copy this the second time :/. Phone reboots after flashing is done and like before still stuck at the end of the boot animation.
[*] Press any key to continue.
< waiting for device >
sending 'partition' (32 KB)...
OKAY [ 0.022s]
writing 'partition'...
This may take a few seconds, if a
different partition table is being
flashed since we need to backup
and restore a few partitions
Failed to program partition table
FAILED (remote failure)
finished. total time: 0.328s
sending 'sbl1' (101 KB)...
OKAY [ 0.028s]
writing 'sbl1'...
Failed to erase partition
Failed to flash partition sbl1
FAILED (remote failure)
finished. total time: 0.156s
sending 'sbl2' (126 KB)...
OKAY [ 0.029s]
writing 'sbl2'...
Failed to erase partition
Failed to flash partition sbl2
FAILED (remote failure)
finished. total time: 0.155s
sending 'sbl3' (512 KB)...
OKAY [ 0.058s]
writing 'sbl3'...
Failed to erase partition
Failed to flash partition sbl3
FAILED (remote failure)
finished. total time: 0.323s
sending 'rpm' (140 KB)...
OKAY [ 0.030s]
writing 'rpm'...
Failed to erase partition
Failed to flash partition rpm
FAILED (remote failure)
finished. total time: 0.279s
sending 'tz' (210 KB)...
OKAY [ 0.036s]
writing 'tz'...
Failed to erase partition
Failed to flash partition tz
FAILED (remote failure)
finished. total time: 0.286s
sending 'aboot' (256 KB)...
OKAY [ 0.038s]
writing 'aboot'...
Failed to erase partition
Failed to flash partition aboot
FAILED (remote failure)
finished. total time: 0.292s
sending 'modem' (30720 KB)...
OKAY [ 2.262s]
writing 'modem'...
Failed to erase partition
Failed to erase partition
Failed to write mmc
FAILED (remote failure)
finished. total time: 2.385s
sending 'fsg' (165 KB)...
OKAY [ 0.032s]
writing 'fsg'...
Failed to erase partition
Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.144s
erasing 'modemst1'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.045s
erasing 'modemst2'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.043s
sending 'logo' (854 KB)...
OKAY [ 0.081s]
writing 'logo'...
Failed to erase partition
Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.200s
sending 'boot' (10240 KB)...
OKAY [ 0.751s]
writing 'boot'...
Failed to erase partition
Failed to flash partition boot
FAILED (remote failure)
finished. total time: 1.468s
sending 'recovery' (10240 KB)...
OKAY [ 0.779s]
writing 'recovery'...
Failed to erase partition
Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.503s
erasing 'userdata'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.044s
sending 'system' (30720 KB)...
OKAY [ 3.806s]
writing 'system'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 5.397s
erasing 'tombstones'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.045s
erasing 'cache'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.044s
[*] Flash complete, Rebooting...
rebooting...
finished. total time: 0.006s

pyromaniac1 said:
Ran the script twice. Managed to copy this the second time :/. Phone reboots after flashing is done and like before still stuck at the end of the boot animation.
Click to expand...
Click to collapse
hmm, not good!
it looks like the hole phone is r/o when in fastboot. i have seen this before several times and have yet to see any one fix it.
i thought a few of those may fail, although you weren't actually downgrading any of them, they shouldn't have, but every writing and erasing command has failed. i was hoping that didn't happen.
we didn't try a factory reset but that's pointless, as the script tried it and it failed.
i dont think there is a way to fix this. maybe @SamuriHL has an idea.
just so you know Sam, the "modified" script i gave him a few post down uses moto fastboot to flash everything.
figured that was the best shot, if there was one, given what he already tried.
thanks

Without having read everything cause I'm pressed for time, my gut instinct says this:
USB cable (make sure it's the oem cable that came with the phone...yes, it matters), USB port (usb 2.0 NOT 3.0), or USB driver issue.

SamuriHL said:
Without having read everything cause I'm pressed for time, my gut instinct says this:
USB cable (make sure it's the oem cable that came with the phone...yes, it matters), USB port (usb 2.0 NOT 3.0), or USB driver issue.
Click to expand...
Click to collapse
thanks!
i hope its something that simple. since the other instances were unlocked devices running custom recovery (with other mitigating factors), this seems rarely fixable as none of the other causes for a true r/o situation apply here.
im afraid to tell him to try a fdr in recovery, as i have seen quite a few cases go worse lately for no reason.
maybe a simple fix is what is needed.
thanks for your input either way.

I always try simple before moving on to the hard stuff. To me it feels like a communication issue with the phone but I don't know for sure. It's a guess. I'd start there at the very least.

SamuriHL said:
I always try simple before moving on to the hard stuff. To me it feels like a communication issue with the phone but I don't know for sure. It's a guess. I'd start there at the very least.
Click to expand...
Click to collapse
Well a factory reset was the first thing I tried anyway. So no luck there. I've tried it with the OEM cable on my laptop as well as a different cable on my PC. Not sure about the USB 3.0 or 2.0 though. I have a lenovo x230 laptop with 2 USB 3.0 ports so ill try again and see if using those ports with the OEM cable makes a difference.

You can not use a USB 3 port. It will fail.
Sent from my SM-P600 using Tapatalk

Nope. Tried it on my PC and laptop both on the usb 2.0 port with the oem cable. Still the same

pyromaniac1 said:
Nope. Tried it on my PC and laptop both on the usb 2.0 port with the oem cable. Still the same
Click to expand...
Click to collapse
I would go an uninstall all drivers, reboot, and then reinstall the drivers and then hook your phone up again to see if that helps. Could be either drivers are corrupted or something else is hosed up.
Since you've tried it on two different computers and it failed, I'm assuming you used the same drivers on both machines? What version of the drivers are you using?
You might want to go to the moto site and get the Motorola helper to bring down the drivers.

i assume you've tried both RSD Lite and motofastboot?

SamuriHL said:
i assume you've tried both RSD Lite and motofastboot?
Click to expand...
Click to collapse
he did, several times.
---------- Post added at 04:09 PM ---------- Previous post was at 04:03 PM ----------
SamuriHL said:
i assume you've tried both RSD Lite and motofastboot?
Click to expand...
Click to collapse
results from mfastboot are in post 9.
failed writing and or erasing at every step. i made the script for him, he posted the results.
even if a couple would have failed as writing equal code, they all wouldn't have as it flashes each separately.

Yea, not a situation I've seen before. Almost like the partition table is screwed up somehow so it doesn't know the mount points to flash to. Just for fun, let's try something.
Boot her up in AP Fastboot mode, connect it to USB 2.0, then try this:
o) From a cmd prompt, type: fastboot oem fb_mode_clear
o) Then flash the FXZ again either with motofastboot or RSD.
I'm just curious.

[Q] Stock Nexus S stuck on Google logo: is it possible to recover the data?

Hi guys,
I know it sounds like one of many threads already created here.
I have read a bunch of them and the information sounds a bit contradictory or at least I'm unsure.
My Nexus S i9020 has sunk in salt water. I washed it in distilled water then gave it two weeks in a dry, warm environment.
When I try to turn it on I see a menu which is asking do I want to unlock a bootloader or not.
While on Power + Volume Up I can get into recovery menu. When I choose reboot I can see a Google logo with no progress. Pressing the Power button doesn't turn the phone off so I have to take the battery out. But power off through the menu works fine.
I installed necessary drivers / bits of SDK on Windows 7. ADB doesn't see the phone but fastboot does, so I can turn the phone off or can try to reboot it from PC. Looks like USB debugging is off.
Now the question is: can I actually turn it on without unlocking a bootloader? Can I _run_ CWM without unlocking a bootloader?
If not are there other options to turn USB debugging on?
If there are no options and I have to unlock a bootloader, would it 100% kill the data on memory card?
If it will is there any chance to restore it afterwards? If so, how can I do that?
Or should I just forget about it?
Thank you!

First try to flash the factory system.img and boot.img through fastboot, don't wipe and only flash these, you may be able to get in and recover data this way.
If not and you want to try a custom recovery to the best of my knowledge you will need to unlock bootloader which will erase all data
There is a chance that you can still recovery some though, there are apps in the market (disc digger?)
But know that more than likely you won't get anything back
Best of luck though!

demkantor said:
First try to flash the factory system.img and boot.img through fastboot, don't wipe and only flash these, you may be able to get in and recover data this way.
If not and you want to try a custom recovery to the best of my knowledge you will need to unlock bootloader which will erase all data
There is a chance that you can still recovery some though, there are apps in the market (disc digger?)
But know that more than likely you won't get anything back
Best of luck though!
Click to expand...
Click to collapse
Hi demkantor,
Thanks a lot for reply!
Before I kill it completely... :cyclops: How do I find out which image I need to download?
I obviously need 4.1.2 one but do I need "soju" for Nexus S (worldwide version, i9020t and i9023) or "sojua" for Nexus S (850MHz version, i9020a)?
The phone I have is the UK version, as far as I remember (I'll double check it later) there was just i9020 on the phone, no other index.
Any ideas about this? Can device ID help here?
And after that the only thing I have to do would be:
> fastboot flash system system.img
> fastboot flash boot boot.img
> fastboot reboot
Am I right?

https://developers.google.com/android/nexus/images?csw=1
More than likely soju, since you can't get to about phone to check maybe it will say under battery or if you have original box?
And yes those are the correct commands
Best of luck!

Hi demkantor,
This is what I see in fastboot mode:
PRODUCT NAME - HERRING
HW VERSION - REW 11
BOOTLOADER VERSION - I9020XXLC2
BASEBAND VERSION - I9020XXKI1
CARRIER INFO - EUR
According to android-info.txt from soju-jzo54k-factory-36602333.tgz everything is fine so i downloaded it, extracted system.img and boot.img and tried to flash them with fastboot.
Unfortunately I got this:
C:\android-sdk-windows> fastboot flash system system.img
sending 'system' (337443 KB)... OKAY [ 53.034s]
writing 'system'... FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 53.035s
C:\android-sdk-windows> fastboot flash boot boot.img
sending 'boot' (3964 KB)... OKAY [ 0.621s]
writing 'boot'... FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 0.622s
Looks like whatever I want to flash I still have to unlock the bootloader. Any other ideas?
Can I boot into CWM without flashing and turn USB debugging on from there?

You can try to just boot the recovery but its unlikely
fastboot boot nameofrecovery.img
That will probably fail too, my guess is you'll end up having to unlock bootloader or run the flashall.bat but either way will do a full wipe, there is the slight chance there are apps in the play store that can recover some stuff if you run them right away but I can't recall if unlocking the bootloader is a format or a wipe (format being much less likely to recover)

demkantor said:
You can try to just boot the recovery but its unlikely
fastboot boot nameofrecovery.img
That will probably fail too, my guess is you'll end up having to unlock bootloader or run the flashall.bat but either way will do a full wipe, there is the slight chance there are apps in the play store that can recover some stuff if you run them right away but I can't recall if unlocking the bootloader is a format or a wipe (format being much less likely to recover)
Click to expand...
Click to collapse
Yep looks like it is very unlikely that I will be able to do it without unlocking. I've seen a thread somewhere where the guy was in the same situation and he had to unlock the bootloader but after that was able to restore the data.
Okay then, I'll dig on this a bit more and then try it out. Thanks a lot!

Okay. So finally I had to try unlocking a bootloader and flashing the phone with flash-all.bat script.
The log looks like this
Code:
c:\android-sdk-windows\soju-jzo54k>flash-all.bat
sending 'bootloader' (1536 KB)... OKAY [ 0.241s]
writing 'bootloader'... OKAY [ 0.355s]
finished. total time: 0.597s
rebooting into bootloader... OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
sending 'radio' (12288 KB)... OKAY [ 1.925s]
writing 'radio'... OKAY [ 1.740s]
finished. total time: 3.665s
rebooting into bootloader... OKAY [ 0.001s]
finished. total time: 0.001s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXLC2
Baseband Version.....: I9020XXKI1
Serial Number........: SERIAL
--------------------------------------------
checking product... OKAY [ 0.001s]
checking version-bootloader... OKAY [ 0.001s]
checking version-baseband... OKAY [ 0.001s]
sending 'boot' (3964 KB)... OKAY [ 0.620s]
writing 'boot'... OKAY [ 0.520s]
sending 'recovery' (4308 KB)... OKAY [ 0.674s]
writing 'recovery'... OKAY [ 0.565s]
sending 'system' (337443 KB)... OKAY [ 52.764s]
writing 'system'... OKAY [ 37.667s]
erasing 'userdata'... OKAY [ 0.185s]
erasing 'cache'... OKAY [ 1.999s]
rebooting...
finished. total time: 95.001s
After rebooting the phone I got the same problem i.e. it's stuck on Google logo. The same result I get when I insert the battery while the phone is unplugged from PC. But if I press Volume Up + Power (while disconnected from PC) I get a yellow triangle and the text "Downloading... Do not turn off the target".
Data is lost. Fine. Any ideas what could be done in order to make the phone bootable?

Try wiping through fastboot and then flashing the images one by one (instead of the flash all.bat)
This may help
http://forum.xda-developers.com/showthread.php?t=2277112

[Q] xt926 - help is appreciated

device: VZW motorola droid razr hd xt926 - completely stock, no customizing at all, every update that came to the phone I installed without problem.
About a month ago (~dec 16, 2014 I believe) the phone was lagging and unresponsive so I powered down, restarted, and that is when the problem began. Upon restart the phone got to the red motorola logo and would hang there. holding the power button would power down for a second, then restart.. so I soft reset it to the boot menu where it atleast wasnt heating up drastically. I left it plugged in because there was no way to power down. From there I began researching the xt926 and seeing other people's problems about the phone hanging at boot logo.
I scoured these forums (and numerous others) for problems similar to mine. Since I was able to get into the boot options menu I've tried everything I could find.. rsd lite, rsd flasher, motorola device manager, house of motorola, droid razr utility...
I tried for about 5 days straight and gave up, took it to a local cell repair place and asked what they would do to repair it. They mentioned a few of the things I tried and said that I had went further than they would go. Out of pity (I believe) they gave me an old BB curve which I've been using the last month. I've been shopping around lately for new phones and wanted to give the razr hd one last crack before relenting and getting a new phone (either S5 or HTC one M8).
First question I guess is, is the phone unusable and beyond repair? upon power up, the phone gets to the red motorola logo for about 2 seconds then goes to this presumed fail boot screen.
it lists:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-61146a2, 2014-07-29 03:17:13)
eMMC Info: Size 16GB
Device is LOCKED. Status Code: 0
Battery OK
Transfer Mode: USB Connected
Load kernel (boot) failed
Fastboot Reason: Boot Failure
I can restart the phone from here by clicking the power button, it restarts, hits logo screen, then right back here.
I can get to the boot selection screen by holding the volume up button when its restarting.. it'll get to the boot menu and then restart after about 3 seconds of idle time if I dont pick something quickly.. the 5 options at the boot selection are:
Normal Powerup
Recovery
AP Fastboot
Factory
BP Tools
Normal Powerup, Factory, and BP Tools do nothing.. the phone restarts and hits logo screen then boot failure.
AP Fastboot restarts phone and goes to the same boot screen, but instead of the load kernel boot failure stuff it says: Fastboot Reason: Key Pressed. This is the same result as during powerup/restart holding the volume down key.
Recovery restarts, gets to logo screen, then after about 5 seconds gets to the droid dude with the red exclamation triangle over his open chest. From here I can get it into the recovery mode with 5 selections..
reboot system now
apply update from sdcard
apply update from ADB
wipe data/factory reset
wipe cache partition
All of that being said.. do I have any options to get this phone functional?
Your time and effort is greatly appreciated.
Cheers

I'm assuming that you tried the wipe data from recovery option ? And then to be clear did you actually download and install a factory image using RSD?

i would try rsd lite again with all the latest version of the fxz/sbf in case you were using an old one. this thread from @SamuriHL http://forum.xda-developers.com/droid-razr-hd/general/fxz-4-4-2-183-46-15-t2873083 is the latest for the xt926 make sure you have the moto drivers installed. if you need i can help with teamviwer or hangouts if you want just pm me for details.
as a side note i do not think that your phone is dead just soft bricked.
---------- Post added at 10:21 PM ---------- Previous post was at 10:14 PM ----------
randymancanstand said:
device: VZW motorola droid razr hd xt926 - completely stock, no customizing at all, every update that came to the phone I installed without problem.
Cheers
Click to expand...
Click to collapse
__

I appreciate the input, sorry for the delay in my response.
I'm assuming that you tried the wipe data from recovery option ? And then to be clear did you actually download and install a factory image using RSD?
Click to expand...
Click to collapse
yes, I factory wiped and using rsd lite, droid razr utility, rsd flasher I tried many different images.. through different iterations and combinations. When rsd lite had no effect installing the different images I had, I moved onto a different program. I wasnt exactly sure which image the system required.. I went through the following:
VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml
VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-4_VQW_CFC.xml
VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml
VZW_XT926_4.4.2-KDA20.62-10_1FF.xml
VZW_XT926_4.4.2-KDA20.62-15.1_1FF.xml
I am unsure if they are 'factory' images
i would try rsd lite again with all the latest version of the fxz/sbf in case you were using an old one. this thread from @SamuriHL http://forum.xda-developers.com/droi...46-15-t2873083 is the latest for the xt926 make sure you have the moto drivers installed. if you need i can help with teamviwer or hangouts if you want just pm me for details.
as a side note i do not think that your phone is dead just soft bricked.
Click to expand...
Click to collapse
I am glad to hear that the phone may have a chance yet. I will look into the latest image. I have RSD Lite v6.2.4.. could someone remind me of the basic flash process?
connect the phone to my pc
put the phone into fastboot,
load up rsd lite
load up image in rsd lite
????
profit?
Again, thank you for your time.
edit: I also have motorola mobile driver 6.4.0 installed

RSD Lite v6.2.4
VZW_XT926_4.4.2-KDA20.62-15.1_1FF.xml
When i click start it fails and gives status:
Failed flashing process. 1/17 flash partition "gpt.bin" -> Phone returned FAIL.
Am currently trying house of moto..

randymancanstand said:
RSD Lite v6.2.4
VZW_XT926_4.4.2-KDA20.62-15.1_1FF.xml
When i click start it fails and gives status:
Failed flashing process. 1/17 flash partition "gpt.bin" -> Phone returned FAIL.
Am currently trying house of moto..
Click to expand...
Click to collapse
this may sound to simple but are you unziping the sbf/fxz?

billycar11 said:
this may sound to simple but are you unziping the sbf/fxz?
Click to expand...
Click to collapse
yes definitely

okay maybe your partitions are messed up then i have seen @bweN diorD help people with that before so he may be able to help.

randymancanstand said:
yes definitely
Click to expand...
Click to collapse
flash this in fastboot. use the data wipe batch file.
if the phone doesnt boot fully to the setup screen within 10min after flashing, its likely toast.
edit,
on second thought, dont close the prompt until you see if it boots up or not. if not, copy all the text from inside the prompt and post it here for me to look at.
thanks

The download is going incredibly slow, but when its done I will flash it and report back.
Thanks for the direction

randymancanstand said:
The download is going incredibly slow, but when its done I will flash it and report back.
Thanks for the direction
Click to expand...
Click to collapse
so the download is crawling along.. it has finished prematurely a couple times already. I'll open the .rar and it says its incomplete.
Is this for matt's droid utility? I have a copy of it I got on 12/17/14.. with an fxz labeled:
VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_RSD
I'll keep trying the download from the link you provided in the mean time

randymancanstand said:
so the download is crawling along.. it has finished prematurely a couple times already. I'll open the .rar and it says its incomplete.
Is this for matt's droid utility? I have a copy of it I got on 12/17/14.. with an fxz labeled:
VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_RSD
I'll keep trying the download from the link you provided in the mean time
Click to expand...
Click to collapse
You need to use the one I just provided.
Not sure what's up with the DL speeds, my account is paid, so that almost never happens.

bweN diorD said:
You need to use the one I just provided.
Not sure what's up with the DL speeds, my account is paid, so that almost never happens.
Click to expand...
Click to collapse
no dice...
[*] Simple Razr Restore
[*] Windows Version
[*] Created by mattlgroff
[*] Maintained by bweN diorD
[*] Before continuing, ensure your device is in the
[*] "AP Fastboot" mode and connected via USB.
[*] Be VERY aware! This WILL wipe your userdata, including contacts, apps, etc.
[*] I am not responsible if this wipes your internal sdcard, and you should
[*] backup anything worth it to you to your external sdcard and computer before
[*] you choose to continue. You can exit now with the X button on this window.
[*] WARNING: Do not do this at LOW BATTERY! You have been warned!
[*]
[*] This script will also wipe your data (did i mention this will wipe your data
?).
[*] Press any key to continue.
sending 'partition' (32 KB)...
OKAY [ 0.020s]
writing 'partition'...
This may take a few seconds, if a
different partition table is being
flashed since we need to backup
and restore a few partitions
Failed to program partition table
FAILED (remote failure)
finished. total time: 0.340s
sending 'sbl1' (101 KB)...
OKAY [ 0.030s]
writing 'sbl1'...
Failed to erase partition
Failed to flash partition sbl1
FAILED (remote failure)
finished. total time: 0.160s
sending 'sbl2' (127 KB)...
OKAY [ 0.030s]
writing 'sbl2'...
Failed to erase partition
Failed to flash partition sbl2
FAILED (remote failure)
finished. total time: 0.160s
sending 'sbl3' (512 KB)...
OKAY [ 0.060s]
writing 'sbl3'...
Failed to erase partition
Failed to flash partition sbl3
FAILED (remote failure)
finished. total time: 0.350s
sending 'rpm' (140 KB)...
OKAY [ 0.030s]
writing 'rpm'...
Failed to erase partition
Failed to flash partition rpm
FAILED (remote failure)
finished. total time: 0.300s
sending 'tz' (210 KB)...
OKAY [ 0.030s]
writing 'tz'...
Failed to erase partition
Failed to flash partition tz
FAILED (remote failure)
finished. total time: 0.300s
sending 'aboot' (256 KB)...
OKAY [ 0.040s]
writing 'aboot'...
Failed to erase partition
Failed to flash partition aboot
FAILED (remote failure)
finished. total time: 0.310s
sending 'modem' (30720 KB)...
OKAY [ 2.400s]
writing 'modem'...
Failed to erase partition
Failed to erase partition
Failed to write mmc
FAILED (remote failure)
finished. total time: 2.540s
sending 'fsg' (165 KB)...
OKAY [ 0.030s]
writing 'fsg'...
Failed to erase partition
Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.160s
erasing 'modemst1'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.060s
erasing 'modemst2'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.050s
sending 'logo' (854 KB)...
OKAY [ 0.090s]
writing 'logo'...
Failed to erase partition
Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.220s
sending 'boot' (10240 KB)...
OKAY [ 0.810s]
writing 'boot'...
Failed to erase partition
Failed to flash partition boot
FAILED (remote failure)
finished. total time: 1.550s
sending 'recovery' (10240 KB)...
OKAY [ 0.822s]
writing 'recovery'...
Failed to erase partition
Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.556s
erasing 'userdata'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.060s
sending 'system' (30720 KB)...
OKAY [ 2.400s]
writing 'system'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 4.010s
erasing 'tombstones'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.053s
erasing 'cache'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.060s
[*] Flash complete, Rebooting...
rebooting...
finished. total time: 0.010s
Hit ENTER to return.

Sorry, but throw it in the trash and move on.
I have seen this exact scenario many times, its not fixable.

bweN diorD said:
Sorry, but throw it in the trash and move on.
I have seen this exact scenario many times, its not fixable.
Click to expand...
Click to collapse
I figured as much.. any idea what could bring this on?
Like I said, no modifications to the phone, it was lagging/hanging so I restarted it.. simply would not boot afterward..
Anyway, thanks for your time and effort. Atleast I know for sure it is done with.
Cheers

randymancanstand said:
I figured as much.. any idea what could bring this on?
Like I said, no modifications to the phone, it was lagging/hanging so I restarted it.. simply would not boot afterward..
Anyway, thanks for your time and effort. Atleast I know for sure it is done with.
Cheers
Click to expand...
Click to collapse
no one seems to know whats causing it. some have mods, some dont. the hole device just seems to become write protected for no reason.

Z3 bricked, no recovery

Hi all,
somehow my sons' D6603 messed up and didn't boot anymore. Had an old CarbonROM installed before, but that failed for no reason I can pinpoint.
OK, to recover I tried to reflash the ROM - but boot process got stuck in boot animation for hours (until battery ran out).
OK, so I fired up flashtool and tried to install an FTF - but all FTFs I tried to retrieve failed to unpack.
OK - one more try - got me a stock ROM that was supposed to be flashed through recovery.
Now I get Sony splashscreen, then display turns black and stays like that forever. Only sign of something happening is that the notification LED blinks occasionally.
I tried to enter recovery - wouldn't work at all: never saw any change in boot process.
I can put the phone into flash mode and into fastboot - so I tried to flash a new TWRP:
Code:
[email protected] ~/temp/TWRP-z3 $ fastboot flash FOTAKernel recovery.img
target didn't report max-download-size
sending 'FOTAKernel' (15904 KB)...
OKAY [ 0.502s]
writing 'FOTAKernel'...
OKAY [ 1.056s]
finished. total time: 1.558s
[email protected] ~/temp/TWRP-z3 $ fastboot flash recovery recovery.img
target didn't report max-download-size
sending 'recovery' (15904 KB)...
OKAY [ 0.501s]
writing 'recovery'...
OKAY [ 1.055s]
finished. total time: 1.556s
But still the mobile won't boot into recovery
OK, there's a different TWRP available - but I can't flash it to FOTAkernel:
Code:
[email protected] ~/Downloads $ fastboot flash FOTAkernel twrp_z3_2018-03-28.img
target didn't report max-download-size
sending 'FOTAkernel' (10808 KB)...
OKAY [ 0.342s]
writing 'FOTAkernel'...
FAILED (remote: Command not allowed)
finished. total time: 0.345s
[email protected] ~/Downloads $ fastboot flash recovery twrp_z3_2018-03-28.img
target didn't report max-download-size
sending 'recovery' (10808 KB)...
OKAY [ 0.342s]
writing 'recovery'...
OKAY [ 0.721s]
finished. total time: 1.063s
Can anyone help me to get stuff working again? I'm lost for options right now - TWRP won't come up, and I can't get an FTF via flashtool to my harddrive. Any other ways to unbrick the phone?
Got a recent LinuxMint 19.x here as my machine right now. Getting a Windows up and running would be an obstacle (although I might get a hand to one).