Related
I have a T-Mobile UK DHD that I'd fully rooted, Eng-Off, Radio S-Off & SuperCID
I was running a LeeDroid ROM but yesterday it began frequently locking up so I tried to do a wipe and reinstall the ROM but at the end of the ROM installation after "Writing boot.img" it said:
assert failed: write_raw_image ("/tmp/boot.img","boot")
E:Error in /sdcard/LeeDrOiD_HD_V2.0.0.zip
(Status 7)
Installation aborted.
I also kept getting the messages E:Can't mount CACHE:recovery/log & E:Can't open CACHE:recovery/log
I then tried to install the stock 1.32 RUU but that stuck at the Updating User Data stage at 40%.
I'm now stuck with the bootloader options and simply have a white screen with the below and warning triangles bottom left & right.
ACE PVT SHIP S-OFF
HBOOT-0.85.0007
MICROP-0438
RADIO-26.04.02.17_M2
eMMC-BOOT
Oct 11 2010, 12:47:02
RUU (This is highlighted yellow)
I have tried ADB but the device isn't shown as attached. However, Fastboot shows it attached but I've had no success pushing the ROM this way either. Below is copy of the cmd window:
C:\AndroidSDK\tools>fastboot boot PD98IMG.zip
creating boot image...
creating boot image - 301006848 bytes
downloading 'boot.img'...
OKAY [ 47.302s]
booting...
FAILED (remote: not allowed)
finished. total time: 47.302s
Can anyone offer any assistance as I've run out of ideas and fear I've bricked it.
you cant just flash rom via ADB. you need recovery. Do you have clockwork mod recovery?
The message you get about being unable to write boot suggests you are no longer S-off, whilst bootloader suggests you have s-off, l would start from scratch and s-off again and then try reinstalling the rom
20mark said:
you cant just flash rom via ADB. you need recovery. Do you have clockwork mod recovery?
Click to expand...
Click to collapse
I used to but it's been wiped as part of the the failed RUU installation. Power On/Vol Down now does nothing
ghostofcain said:
The message you get about being unable to write boot suggests you are no longer S-off, whilst bootloader suggests you have s-off, l would start from scratch and s-off again and then try reinstalling the rom
Click to expand...
Click to collapse
Do you mean Eng or Radio off? Can I do that with no bootloader options or recovery?
How would you suggest installing the ROM and which one?
Thanks for any advice.
I've just tried jkolo's easy S-Off tool but I get an error message pop-up "Module or hboot fail. Aborting."
So what happenes when you choose the recovery option?
Oh and btw don't worry too much about the void warranty, I've read of a few people who've had to send phones back to HTC without being able to revert to stock first and they've been successful - obviously this is a last resort.
EmprtArea said:
So what happenes when you choose the recovery option?
Click to expand...
Click to collapse
I don't have a recovery option on the Phone.
So can you use fastboot to do this successfully?
fastboot erase recovery
fastboot flash recovery clockwork-recovery.img
If you need the image it here: http://mirror1.kanged.net/recoveries/recovery-clockwork-3.0.0.6-ace.img
EmprtArea said:
So can you use fastboot to do this successfully?
fastboot erase recovery
fastboot flash recovery clockwork-recovery.img
Click to expand...
Click to collapse
I haven't tried that yet but fear the 1st line may wipe my only way of communicating if the 2nd part doesn't work
well you say you haven't got the recovery option anyway, so you could leave that line out I only put it because that's what I'd do.
HOWEVER: I'm no expert.
Question after Re-reading your post: Are you worried you'll delete fastboot? I'm sure that's not what I'm suggesting. But as it's your £500 device wait for someone else to confirm.
EmprtArea said:
So can you use fastboot to do this successfully?
fastboot erase recovery
fastboot flash recovery clockwork-recovery.img
If you need the image it here: http://mirror1.kanged.net/recoveries/recovery-clockwork-3.0.0.6-ace.img
Click to expand...
Click to collapse
No luck
Code:
C:\AndroidSDK\tools>fastboot flash recovery recovery-clockwork-3.0.0.6-ace.img
sending 'recovery' (3334 KB)...
OKAY [ 0.560s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.562s
Everytine you try writing it fails what else can you do?
Sent from my Desire HD using XDA App
I'd jump to thinking you're not ENG S-Off anymore (got to say probably the failed 1.32 flash that did it. And you can't use that tool so look for an alternative description of how to get there.
If you can't use ADB I don't know how to get there.
If somehow ADB does start working then the CyanogenMod wiki might be useful.
http://wiki.cyanogenmod.com/index.php?title=HTC_Desire_HD:_Full_Root_Guide
If you lost s-off while flashing the 1.32 rom then I also suspect you lost root.
Sent from my Desire HD using XDA App
I've got backups of:
hboot_original.bin & part7backup-1294609557.bin
Are they of any help?
I can't see any way to gain Eng-Off without root so I'm at a loss.
The frustrating thing is I don't know what happened in the 1st place that froze my phone and kicked all this off. I'm guessing I have a hardware fault of some sort
Would T-Mobile exchange or repair under warranty, despite the mods I'd made?
Aamir.Badat said:
If you lost s-off while flashing the 1.32 rom then I also suspect you lost root.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
I'm starting to regret trying that as a solution now
I remembered something similar being posted on these forums a few months ago, so I had a search and found this thread:
http://forum.xda-developers.com/showthread.php?p=9139950
I'm not an expert on these things, so I don't know if this would work for you. I would suggest waiting for someone with a bit more experience than me to join the discussion, as I don't know how similar your circumstances are to the ones in that thread. Do you get any error messages on your PC when you run the RUU? I take it that it finds your phone, whereas in the thread above the RUU wasn't seeing the phone.
However I thought reading that might give you some hope. Worth reading the thread all the way through.
I think what disabled most of your options was flashing a stock ruu. It overwrites hboot and the recovery.
Edit: since the ruus fail installing, maybe someting is off with your device, NAND error or someting.
this sort of thing doesnt happen if you are flashing custom roms though right? its making me nervous now!
preacher65 said:
I remembered something similar being posted on these forums a few months ago, so I had a search and found this thread:
http://forum.xda-developers.com/showthread.php?p=9139950
I'm not an expert on these things, so I don't know if this would work for you. I would suggest waiting for someone with a bit more experience than me to join the discussion, as I don't know how similar your circumstances are to the ones in that thread. Do you get any error messages on your PC when you run the RUU? I take it that it finds your phone, whereas in the thread above the RUU wasn't seeing the phone.
However I thought reading that might give you some hope. Worth reading the thread all the way through.
Click to expand...
Click to collapse
Thanks for the tip. I'll have a read and may give that a go.
KamikaZeeFu said:
I think what disabled most of your options was flashing a stock ruu. It overwrites hboot and the recovery.
Edit: since the ruus fail installing, maybe someting is off with your device, NAND error or someting.
Click to expand...
Click to collapse
I don't get errors, the RUU just freezes and I have to pull the plug.
danrobz said:
this sort of thing doesnt happen if you are flashing custom roms though right? its making me nervous now!
Click to expand...
Click to collapse
The errors started when I was on a Custom ROM but my suspicion is that it's a hardware fault to blame. If I can't fix this then whilst the custom ROM probably didn't cause the damage, the general unlocking etc may have voided my warranty.
Howdy
I have a Razr M which was the old BDH debloated stock rom.
I flashed over to PACMan this morning, rebooted, stuck in fastboot!
I have tried the Razr M Utility and RSD Lite to try to flash back to stock, but I am met with incessant errors:
#1 When I try RSD Lite, it fails at writing the system.img
#2 When I try Matt's utility, I get a 'remove fail' when writing system.img
FastBoot reasons vary between "No PIV in system block" or "stick bit in factory_reset"
I am unable to get to any kind of recovery, or any kind of logo screen. M will flash, but then immediately to fastboot.
Phone was previously unlocked and rooted
shlazzer said:
Howdy
I have a Razr M which was the old BDH debloated stock rom.
I flashed over to PACMan this morning, rebooted, stuck in fastboot!
I have tried the Razr M Utility and RSD Lite to try to flash back to stock, but I am met with incessant errors:
#1 When I try RSD Lite, it fails at writing the system.img
#2 When I try Matt's utility, I get a 'remove fail' when writing system.img
FastBoot reasons vary between "No PIV in system block" or "stick bit in factory_reset"
I am unable to get to any kind of recovery, or any kind of logo screen. M will flash, but then immediately to fastboot.
Phone was previously unlocked and rooted
Click to expand...
Click to collapse
not sure if your problem has been resolved, but are you able to get into recovery? also, make sure you charge the phone up to 100% first (if you can't tell, then just charge it for about 2 hours)
Fortunately, my issues have been resolved.
Not sure what the specific fix was, but all I really did was just retry flashing over and over and over, with RSD Lite and matt's utility. One time it finally worked.
from there, the factory_fastboot sticky bit was fixed by clearing oem fastboot userdata and cache in ADB
phone was good as new!
Enter fastboot oem fb_mode_clear and problem gone.
I find the solution
:laugh::laugh::laugh: I find the solutions reply me if u want
shlazzer said:
Howdy
I have a Razr M which was the old BDH debloated stock rom.
I flashed over to PACMan this morning, rebooted, stuck in fastboot!
I have tried the Razr M Utility and RSD Lite to try to flash back to stock, but I am met with incessant errors:
#1 When I try RSD Lite, it fails at writing the system.img
#2 When I try Matt's utility, I get a 'remove fail' when writing system.img
FastBoot reasons vary between "No PIV in system block" or "stick bit in factory_reset"
I am unable to get to any kind of recovery, or any kind of logo screen. M will flash, but then immediately to fastboot.
Phone was previously unlocked and rooted
Click to expand...
Click to collapse
i got one stuck at no valid piv block in SP for system. tried to flash to kitkat but always got stuck at system partition with rsd. tried to downgrade without sbls but does not work.
el_venga said:
i got one stuck at no valid piv block in SP for system. tried to flash to kitkat but always got stuck at system partition with rsd. tried to downgrade without sbls but does not work.
Click to expand...
Click to collapse
If you want to downgrade, remove commands to flash gpt.main and tz from the xml of the ROM
Klen2 said:
If you want to downgrade, remove commands to flash gpt.main and tz from the xml of the ROM
Click to expand...
Click to collapse
left it for like 2 hours with rsd. finally system was flashed. thanks for response.
Alright Ladies and Gentlemen.
Background: (skip if you don't think it's relevant)
I just bought a xt907 with the latest OTA.
I wanted root, however after looking into it, I read that the bootloader was forever locked from the new OTA.
But, me being as stubborn as I am, and always have had a rooted phone, I tried anyways, and with my surprise, somehow, I actually achieved root using motochopper after only clearing the dalvik cache and trying it for shiggles.
No backups.
Even though I couldn't flash a new recovery or a full rom without safestap, I just decided to mod the stock rom.
Installed pimp my rom, es file explorer, some app uninstallers for bloatware (no i didn't uninstall any COM files or important things), etc etc.
Then I Installed a font, didn't like it, went to try a few others.
NOW.
After installing a font and rebooting, I was stuck at the droid boot logo with the red eye and sparks flying about.
I booted into stock recovery, cleared the cache. Nothing. Reset to factory defaults. Nothing.
I was still stuck on the boot logo.
Now, the dumb part of my actions.
I downloaded matt's utility 1.20. I tried option 1, Which failed. So I tried option 2, flashing the recovery. Which was "successful".
Tried option 1 again, it keeps saying
Code:
sending 'system' (30720 KB)...
OKAY [ 2.318s]
writing 'system'...
OKAY [ 2.798s]
sending 'system' (30720 KB)...
OKAY [ 6.569s]
writing 'system'...
OKAY [ 1.358s]
Over and over again.
Now I can not boot the phone. AP Fastboot comes up.
Code:
AP Fastboot Flash Mode
(blah)
Device is LOCKED. Code 0.
No Valid PIV block in SP for system.
PIV validation failed (system)
Fastboot reason: Flash Failure
Same thing comes up when I try to go into recovery. Every time I turn on the phone, this comes up.
I tried RSD Lite, to flash the old rom back on, it keeps failing. I keep trying to flash VZW_XT907_4.1.2-9.8.1Q-66_1FF
With no avail.
So, Anyone who can help me, I would be forever grateful. Thanks.
cheno1115 said:
Alright Ladies and Gentlemen.
Background: (skip if you don't think it's relevant)
I just bought a xt907 with the latest OTA.
I wanted root, however after looking into it, I read that the bootloader was forever locked from the new OTA.
But, me being as stubborn as I am, and always have had a rooted phone, I tried anyways, and with my surprise, somehow, I actually achieved root using motochopper after only clearing the dalvik cache and trying it for shiggles.
No backups.
Even though I couldn't flash a new recovery or a full rom without safestap, I just decided to mod the stock rom.
Installed pimp my rom, es file explorer, some app uninstallers for bloatware (no i didn't uninstall any COM files or important things), etc etc.
Then I Installed a font, didn't like it, went to try a few others.
NOW.
After installing a font and rebooting, I was stuck at the droid boot logo with the red eye and sparks flying about.
I booted into stock recovery, cleared the cache. Nothing. Reset to factory defaults. Nothing.
I was still stuck on the boot logo.
Now, the dumb part of my actions.
I downloaded matt's utility 1.20. I tried option 1, Which failed. So I tried option 2, flashing the recovery. Which was "successful".
Tried option 1 again, it keeps saying
Code:
sending 'system' (30720 KB)...
OKAY [ 2.318s]
writing 'system'...
OKAY [ 2.798s]
sending 'system' (30720 KB)...
OKAY [ 6.569s]
writing 'system'...
OKAY [ 1.358s]
Over and over again.
Now I can not boot the phone. AP Fastboot comes up.
Code:
AP Fastboot Flash Mode
(blah)
Device is LOCKED. Code 0.
No Valid PIV block in SP for system.
PIV validation failed (system)
Fastboot reason: Flash Failure
Same thing comes up when I try to go into recovery. Every time I turn on the phone, this comes up.
I tried RSD Lite, to flash the old rom back on, it keeps failing. I keep trying to flash VZW_XT907_4.1.2-9.8.1Q-66_1FF
With no avail.
So, Anyone who can help me, I would be forever grateful. Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2379833
you have this as a sure thing.
I have wondered if my restore method would work on a locked BL phone. Scroll down to near the bottom and I comment on the possibility of getting custom recovery and then root? Impossible! But you are borked already..... My wife won't let me try it on her updated & locked M.
http://forum.xda-developers.com/showthread.php?t=2391641
aviwdoowks said:
http://forum.xda-developers.com/showthread.php?t=2379833
you have this as a sure thing.
I have wondered if my restore method would work on a locked BL phone. Scroll down to near the bottom and I comment on the possibility of getting custom recovery and then root? Impossible! But you are borked already..... My wife won't let me try it on her updated & locked M.
http://forum.xda-developers.com/showthread.php?t=2391641
Click to expand...
Click to collapse
I did try that and that is how I obtained root. Didn't have a problem up until now.
Anyways, I managed to fix my issue on my own.
Long story short, RSD Lite was flashing the VZW_XT907_4.1.2-9.8.1Q-66_1FF I downloaded from droid-developers.
My phone kept rejecting the tz.mbn saying it was invalid.
Sooooo, I searched for a 98.18.78 OTA pull and I found one.
This is the one for reference.
I swapped the tz.mbn files between the two folders and it flashed it without a problem. Phone booted up as if I just unboxed it.
So, I won't delete this just as a reference for anyone who has the same problems as me.
Sorry for taking anyone's time.
cheno1115 said:
....QUOTE]
I am curious, that link is the prev OTA.
Even then could you share how an ota useful in RSD?
"I swapped the tz.mbn files between the two folders and it flashed it without a problem. Phone booted up as if I just unboxed it."
You got the file from the old OTA?
Click to expand...
Click to collapse
aviwdoowks said:
cheno1115 said:
....QUOTE]
I am curious, that link is the prev OTA.
Even then could you share how an ota useful in RSD?
"I swapped the tz.mbn files between the two folders and it flashed it without a problem. Phone booted up as if I just unboxed it."
You got the file from the old OTA?
Click to expand...
Click to collapse
Yes, I just went in my phone settings and did realize this is a previous OTA. I checked for updates and my phone wants me to update to 98.18.78.
I am curious, that link is the prev OTA.
Even then could you share how an ota useful in RSD?
Click to expand...
Click to collapse
Well, Pretty much, my phone had no rom at the time. I ruined it by trying to flash stuff.
So I downloaded the bottom rom from
sbf.droid-developers.org/scorpion_mini_xt907/list.php
and was trying to flash it onto my phone. My phone kept rejecting the tz.mbn file, it said it was invalid. So I found that old OTA and swapped the two files, and to my surprise, my phone accepted that file. I don't know why it wouldn't take the original one.
Anyways, I'm updating my phone to OTA 98.18.78 right now, so all is good.
Click to expand...
Click to collapse
Samuri HL Downgrade Tool
cheno1115 said:
Alright Ladies and Gentlemen.
Background: (skip if you don't think it's relevant)
I just bought a xt907 with the latest OTA.
I wanted root, however after looking into it, I read that the bootloader was forever locked from the new OTA.
But, me being as stubborn as I am, and always have had a rooted phone, I tried anyways, and with my surprise, somehow, I actually achieved root using motochopper after only clearing the dalvik cache and trying it for shiggles.
No backups.
Even though I couldn't flash a new recovery or a full rom without safestap, I just decided to mod the stock rom.
Installed pimp my rom, es file explorer, some app uninstallers for bloatware (no i didn't uninstall any COM files or important things), etc etc.
Then I Installed a font, didn't like it, went to try a few others.
NOW.
After installing a font and rebooting, I was stuck at the droid boot logo with the red eye and sparks flying about.
I booted into stock recovery, cleared the cache. Nothing. Reset to factory defaults. Nothing.
I was still stuck on the boot logo.
Now, the dumb part of my actions.
I downloaded matt's utility 1.20. I tried option 1, Which failed. So I tried option 2, flashing the recovery. Which was "successful".
Tried option 1 again, it keeps saying
Code:
sending 'system' (30720 KB)...
OKAY [ 2.318s]
writing 'system'...
OKAY [ 2.798s]
sending 'system' (30720 KB)...
OKAY [ 6.569s]
writing 'system'...
OKAY [ 1.358s]
Over and over again.
Now I can not boot the phone. AP Fastboot comes up.
Code:
AP Fastboot Flash Mode
(blah)
Device is LOCKED. Code 0.
No Valid PIV block in SP for system.
PIV validation failed (system)
Fastboot reason: Flash Failure
Same thing comes up when I try to go into recovery. Every time I turn on the phone, this comes up.
I tried RSD Lite, to flash the old rom back on, it keeps failing. I keep trying to flash VZW_XT907_4.1.2-9.8.1Q-66_1FF
With no avail.
So, Anyone who can help me, I would be forever grateful. Thanks.
Click to expand...
Click to collapse
I lost root after the OTA update. Inused SamuriHL Downgrade tool to roll back to the stae my phone was in before update. then it gives instructions on how to retore and keep root. then yuo tkae the update again.
THANK YOU
I thought I was doomed to a bricked phone. This fix saved me.
Important to note for any other poor suckers who find themselves in the same spot - make sure you have an updated version of RSD Lite when you do this. My first (15) attempt(s) failed flashing system.img because I was running an old version of RSD Lite, but when I updated to 6.1.4 it worked fine.
cheno1115, THANK YOU!
I had the same issue with my xt907 after rooting with "DROID_RAZR_M_Utility_1.20" and after restoring my apps (including with framework mods.. stupid, I know) from xt890 via nandroid manager.
I thought oh my god, that is an expensive brick I have now.
I have just reflashed "VZW_XT907_4.1.2-9.8.1Q-66_1FF.xml.zip" via RSD (with "tz.mbn" file raplaced from "Blur_Version.98.16.1.XT907.Verizon.en.US.zip") and it did boot up, however it booted with all my "restored" apps. The problem is that I have tried to restore my home screen via nandroid backup manager and it failed, so I got only upper status bar, soft buttons and black screen... I'm lucky that Motorola placed a settings shortcut on upper drawer, so I was able to navigate to settings and do a factory reset. So this is how I got a fresh start again.
However if I launch "DROID_RAZR_M_Utility_1.20" with option 1 again, I get the same thing - many repeating "sending system.img", have to terminate it and then - a brick. So I had to repeat RSD reflash procedure once more. BTW flashing of "system.img" takes surprisingly long, like 5 minutes or so.
So that got me thinking... Isn't this repeating "sending system" and "writing system" just doing it in pieces and one should wait?
Anyway that has solved my problem. THANKS!
Does this mean you fully rooted your XT907 that had the latest OTA updates? Can you install other ROM's?
As far as I know, once you get the latest OTA update you're screwed and can't do anything.
I have a locked xt907
nifty101 said:
Does this mean you fully rooted your XT907 that had the latest OTA updates? Can you install other ROM's?
As far as I know, once you get the latest OTA update you're screwed and can't do anything.
I have a locked xt907
Click to expand...
Click to collapse
We have SafeRoot now. See the general section.
No custom roms though.
See my xt907 stuff
Can you send me a link to each the general section and your XT907 stuff? Not sure where or what you are referencing. Thanks so much.
nifty101 said:
Can you send me a link to each the general section and your XT907 stuff? Not sure where or what you are referencing. Thanks so much.
Click to expand...
Click to collapse
You are on tapatalk or xda app?
Go here & take your punishment. Lol.
http://forum.xda-developers.com/showthread.php?t=2610531
Links
http://forum.xda-developers.com/showpost.php?p=45548210&postcount=3
SamuriHL has fix for "cannot load system img"
http://www.droidrzr.com/index.php/topic/37658-green-robot-after-using-house-of-moto/#entry400767
No valid piv
Mr hello I have this problem with no valid PIV on my motorola RARZ M can you help me?
i have a droid razr m running 98.16.3 i was trying to downgrade to version in which i would be able to root and unlock it and it says failure preflash validation failed for tz my phone is unrooted and locked at this time and softbricked also what can i do to get it back please this is somewhat of an emergency
Magic19er said:
i have a droid razr m running 98.16.3 i was trying to downgrade to version in which i would be able to root and unlock it and it says failure preflash validation failed for tz my phone is unrooted and locked at this time and softbricked also what can i do to get it back please this is somewhat of an emergency
Click to expand...
Click to collapse
There is NO unlock if not unlocked prior to 98.16.3.
http://forum.xda-developers.com/showpost.php?p=48295502&postcount=47
Here is a users drama. You can do the same.
Link to my restore thread
http://forum.xda-developers.com/showthread.php?t=2391641
Magic19er said:
i have a droid razr m running 98.16.3 i was trying to downgrade to version in which i would be able to root and unlock it and it says failure preflash validation failed for tz my phone is unrooted and locked at this time and softbricked also what can i do to get it back please this is somewhat of an emergency
Click to expand...
Click to collapse
You can't downgrade versions. However, that system version is rootable, though. With that being said, go through those threads that Avi posted or download your firmware from this website and flash in RSD. Your battery needs to be charged prior to doing this, though, so if it's not, put it on the charger now.
http://sbf.droid-developers.org/phone.php?device=8
Hi everyone !
I searched for a case like mine on the forum, but didn't find a solution to my problem, so you're my last hopes !
I have a Nexus 7 (2012) WIFI for a while now and I wanted to return to stock, on Lollipop (I was on Paranoid Android ROM, 4.4.4).
So, l used the Nexus Root Toolkit and ran the "return to stock + unroot" feature.
I downloaded the last google image for my device (5.0.2) and let the thing began.
It erases all partitions like it has to do, but when it needs to write bootloader, it fails and says: "FAILED (command write failed (Unknown error))".
I tried severals time, but always same problem. So I tried to flash stock 4.4.4, but can't write bootloader too: "FAILED (No suck device)" or "FAILED (too many links)" errors appear, something like those.
So, in last hopes, I tried to do this manually and followed this thread: http://forum.xda-developers.com/showthread.php?t=1907796
I erased correctly all partitions, but when I need to flash bootloader with "fastboot flash bootloader bootloader-tilapia-4.23.img" command, I get "FAILED (command write failed (Unknown error))" too...
I can't flash recovery, get the same error as the bootloader one...
If someone had the same problem or if someone can help me to restore my Nexus 7, it would be very kind !
Thanks to everyone who'll read this
Also have the same problem generated by the very same software!!
Anyone have any further info please?
MiMilz said:
Hi everyone !
I searched for a case like mine on the forum, but didn't find a solution to my problem, so you're my last hopes !
I have a Nexus 7 (2012) WIFI for a while now and I wanted to return to stock, on Lollipop (I was on Paranoid Android ROM, 4.4.4).
So, l used the Nexus Root Toolkit and ran the "return to stock + unroot" feature.
I downloaded the last google image for my device (5.0.2) and let the thing began.
It erases all partitions like it has to do, but when it needs to write bootloader, it fails and says: "FAILED (command write failed (Unknown error))".
I tried severals time, but always same problem. So I tried to flash stock 4.4.4, but can't write bootloader too: "FAILED (No suck device)" or "FAILED (too many links)" errors appear, something like those.
So, in last hopes, I tried to do this manually and followed this thread: http://forum.xda-developers.com/showthread.php?t=1907796
I erased correctly all partitions, but when I need to flash bootloader with "fastboot flash bootloader bootloader-tilapia-4.23.img" command, I get "FAILED (command write failed (Unknown error))" too...
I can't flash recovery, get the same error as the bootloader one...
If someone had the same problem or if someone can help me to restore my Nexus 7, it would be very kind !
Thanks to everyone who'll read this
Click to expand...
Click to collapse
PaulG2000 said:
Also have the same problem generated by the very same software!!
Anyone have any further info please?
Click to expand...
Click to collapse
It's pretty well known that for some reason, the bootloader images included on many of the factory images for grouper are not valid, and Google has never corrected this. You'll need to grab a valid bootloader from a different factory image, and flash it manually.
Check this thread out, it's all been covered in great detail there: http://forum.xda-developers.com/showthread.php?t=2573015
Edit: Also, if you're already on a valid bootloader version 4.23, then there's no need to flash the bootloader again.