Okay, so after nearly a whole day of not getting any work done trying to revive my effed-up RAZR, reading through the forums and beyond, I think it's just time to buckle down and ask for some help.
So I'm trying to revert to stock ICS on my RAZR after going through a bunch of custom ROMs. Downloaded a bunch of Fastboot files and tried both the Eternity Project batch file and flashing through RSD Lite (I'm on 6.14), and no go. Results are as follows:
1. Eternity Project flashes successfully(?) albeit with several error prompts, specifically:
a. writing 'boot'... INFOPreflash validation failure
b. writing 'cdrom'... INFOPreflash validation failure
c. writing 'recovery'... INFOPreflash validation failure
d. writing 'devtree'... INFOPreflash validation failure
End result for this is that it boots into the green Android with its chest open and a red exclamation mark and then into the Motorola Dual Core logo for a couple of seconds then goes to a blank screen. From there, it's unresponsive, but no "Failure" prompts reflected on AB Fastboot Flash Mode.
2. RSD Lite fails much earlier on. It stops at flashing cdt.bin, phone returns FAILED and then stops. Afterwards, phone only boots into Fastboot mode and shoes a "Flash Failure" prmopt next to AB Fastboot Flash Mode. I read that cdt.bin is usually linked to flashing a wrong region image onto my phone. Thing is, this phone was given to me by my aunt, and she only gave me the phone itself. No box, no nothing, and she doesn't remember where she bought it from, as it in turn was given to her by a former boyfriend who she no longer has contact with. Do I have any alternatives aside from downloading every single file on the SBF repository and trying them all one-by-one?
Any help?
Other info is that I used to be on stock Motorola ICS on System_1 partition with AOKP Unofficial Jelly Bean on System_2 partition. Bootloader is 0A.6C, RAZR XT910 GSM.
Related
My almost two-year-old Hero froze this morning, so I had to take out the battery, but after this I've been unable to boot, it's stuck on the HeRO screen. I can't start recovery either, the only thing working is hboot / fastboot. Erasing user data using fastboot doesn't do anything.
Also, plugging the phone into charger doesn't signalize charging – the LED doesn't light up, and the PC doesn't recognize the phone either. Only fastboot does connect the phone to the PC, but adb doesn't work and all attempts to flash a new recovery or do anything else via fastboot end with "FAILED (remote: not allowed)":
Code:
c:\adb>fastboot devices
HT97JL903267 fastboot
c:\adb>fastboot boot recovery-RA-hero-v1.7.0.1.img
downloading 'boot.img'... FAILED (remote: not allow)
c:\adb>fastboot flash boot recovery-RA-hero-v1.7.0.1.img
sending 'boot' (3972 KB)... FAILED (remote: not allow)
I tried installing the official RUU updates (2.73.405.66, 2.73.405.5 and 1.76.405.1 too) but none of them could connect to the phone, Error [170]: USB Connection error.
I was using Elelinux-Hero-2.1-update1-Reloaded with radio 63.18.55.06SU_6.35.17.03 and recovery was Amon RA 1.6.2 I guess.
The phone did a similar thing 3 weeks ago but I was able to boot into recovery and erase data and cache and it worked fine afterwards. Now only fastboot is accessible.
Is there anything else I can do at this point or is the phone dead for good?
Disregard my previous post.
I left the phone booting for 30 minutes, the battery got uncomfortably hot, but the phone booted up eventually. Then I managed to install the official RUU from here.
It didn't solve anything though – it still takes around 20 minutes to boot, the touch screen doesn't work and I get an "android.process.acore" error all the time – but since the phone seems untouched (thanks to the RUU install) I can lodge a claim and get a replacement phone hopefully.
You could try putting HEROIMG.NBH on the sdcard and booting into hboot. If you go into fastboot and press vol-down it quickly scans for files on the SD, of which heroimg is one, and if it finds them, installs them.
Can't really help more than that. My phone did that last year, took it to the shop and ended up getting a new motherboard, cause the ROM chip was knackered.
One thing I would recommend though when you get it fixed is to flash an engineering bootloader, do if it breaks again you've got none of this "remote not allow" rubbish.
Of all the times to say disregard my last post.........
Sorry about that, thanks a lot though!
I suppose some hardware is broken in my Hero as well, I will take it back to the shop tomorrow.
Thanks again!
Hi,
For resume, i was just following frastertag instruction to change framework-res.apk with artic 3.0, and during the process i had a reboot from nowhere!!!
and now my phone is bootlooping on "droid" animation.
So what i did:
Trying to flash with alternative script from Kholk, but during the flash i had those error:
Code:
writing 'logo'...
(bootloader) no such partition
FAILED (remote: )
Code:
writing 'system'...
(bootloader) Preflash validation failure
FAILED (remote: )
it reboot and same probleme, just like nothing changed on my phone same bootanimation looping up.
It seems that my bootloader partition is broken.
Is there any solution to fix it or i have to send it to motorola ?
Thanks for your help!!
I had the same 1st error with logo partition but it continued and it frozen at system partition.
I unplugged usb cable and boot, I believed it was bricked, I have do the two times the flash to get a Razr booting correctly.
I change the line in the script: "flash logo logo.bin" to "flash logo.bin logo.bin"
and it worked and boot properly.
Thanks kholk for the tips.
I have come across several posts the are identical or very similar to my issue. However, I am having an additional issue which seems to be the cause of my not being able to unbrick. I'll try to provide enough details, but let me know if I missed something important.
My prime appears to be completely bricked, because I tried to fix another problem. When I tried to upgrade a stock ICS prime to JellyBean, I had many problems because the recovery kept error out with the droid guy with the red triangle and ! symbol. Somehow, I ended up actually do it and ended up with the US_epad-user-10.4.2.15.zip rom (US_epad-10.4.2.15-20120917). Because I am overseas, I had problems installing some things in the market and was considering root or a custom rom. At some point, I unlocked the device, which still displays clearly every time I boot. While look through several things that appeared very straight-forward, I ultimately ended up with a brick. The device is stuck on the splash screen. I have access to fastboot. However, adb doesn't recognize the device.
When trying to RCK (or wipe data) from the bootloader, I get:
Code:
Booting Recovery kernel image
Booting failed
[COLOR="Red"]Unrecoverable bootloader error (0x00000000).[/COLOR]
This post:
[Q] Transformer Prime possibly bricked. Help?
appeared identical to my current problem. The suggested use of universal drivers has not helped, however.
This post:
[SOLVED] Can access fastboot but can't get past splash screen
also appears identical...
These two also appears to provide hope:
[GUIDE] nvFlash General Users Guide [Unbrick/Recover/Downgrade/Upgrade]- TF201
[ROOT] Urkel's Fresh Start 1.0 (Jelly Bean - Unlocked bootloaders only)
...but ultimately, continue to evade my tablet.
Why? you may ask...
Well, it seems that I can boot into fastboot. When I manually run any command, it seems to work fine. But the prime becomes unresponsive to all subsequent commands. It requires that I force reboot and re-enter fastboot. When I try to run Urkel's Fresh Start, the wiping all runs smoothly, and the staging command
Code:
fastboot -i 0x0b05 flash staging system.blob
run smoothly. From that point, it becomes unresponsive again. It appears that although the flashing completes without errors, it doesn't take...or perhaps is inaccessible because the bootloader is jacked. Here's the output from Urkel's Fresh Start, for example:
Code:
Press any key to continue . . .
.: Now cleaning the TF201 partitions :.
erasing 'cache'...
OKAY [ 2.160s]
finished. total time: 2.160s
******************************
erasing 'userdata'...
OKAY [ 39.644s]
finished. total time: 39.645s
******************************
erasing 'recovery'...
OKAY [ 1.953s]
finished. total time: 1.954s
******************************
erasing 'staging'...
OKAY [ 0.948s]
finished. total time: 0.948s
******************************
erasing 'system'...
OKAY [ 2.208s]
finished. total time: 2.209s
******************************
.: Partitions now clean, continuing to reboot back into bootloader. Do not miss
selecting FASTBOOT with VOL+D and then VOL+U on the USB Icon. If you miss it no
big deal reboot back into FASTBOOT before continuing :.
Press any key to continue . . .
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
.: Confirm you are in FASTBOOT before continuing to flash a fresh image/blob. Th
is will take 3-5 minutes because of the size of the image :.
Press any key to continue . . .
sending 'staging' (537604 KB)...
OKAY [ 94.723s]
writing 'staging'...
OKAY [ 1.329s]
finished. total time: 96.054s
rebooting...
finished. total time: 0.548s
.: No need to set up the tablet but let the tablet fully boot to welcome screen
then hold down the power to shut if off. When off turn it back on and enter FAST
BOOT. Once at FASTBOOT then continue :.
Press any key to continue . . .
It appears fine...however, it doesn't reboot, even thought the command said it was successful. So, I try manually rebooting and get stuck at the welcome screen again. It's a vicious cycle... Anyhow, this type of situation is the same for all of the other workarounds that I have found to this problem.
It seems that fastboot is semi-responsive, but no actions that I take are recognized upon reboot. I would love to try and figure out why fastboot is having these issues... and unbrick my tablet. So, please let me know if I have missed any threads that have exactly this solution (ie. fastboot works...but not really).
Thanks in advance, and let me know if I missed details that are necessary.
flueterflam said:
I have come across several posts the are identical or very similar to my issue. However, I am having an additional issue which seems to be the cause of my not being able to unbrick. I'll try to provide enough details, but let me know if I missed something important.
My prime appears to be completely bricked, because I tried to fix another problem. When I tried to upgrade a stock ICS prime to JellyBean, I had many problems because the recovery kept error out with the droid guy with the red triangle and ! symbol. Somehow, I ended up actually do it and ended up with the US_epad-user-10.4.2.15.zip rom (US_epad-10.4.2.15-20120917). Because I am overseas, I had problems installing some things in the market and was considering root or a custom rom. At some point, I unlocked the device, which still displays clearly every time I boot. While look through several things that appeared very straight-forward, I ultimately ended up with a brick. The device is stuck on the splash screen. I have access to fastboot. However, adb doesn't recognize the device.
When trying to RCK (or wipe data) from the bootloader, I get:
Code:
Booting Recovery kernel image
Booting failed
[COLOR="Red"]Unrecoverable bootloader error (0x00000000).[/COLOR]
This post:
[Q] Transformer Prime possibly bricked. Help?
appeared identical to my current problem. The suggested use of universal drivers has not helped, however.
This post:
[SOLVED] Can access fastboot but can't get past splash screen
also appears identical...
These two also appears to provide hope:
[GUIDE] nvFlash General Users Guide [Unbrick/Recover/Downgrade/Upgrade]- TF201
[ROOT] Urkel's Fresh Start 1.0 (Jelly Bean - Unlocked bootloaders only)
...but ultimately, continue to evade my tablet.
Why? you may ask...
Well, it seems that I can boot into fastboot. When I manually run any command, it seems to work fine. But the prime becomes unresponsive to all subsequent commands. It requires that I force reboot and re-enter fastboot. When I try to run Urkel's Fresh Start, the wiping all runs smoothly, and the staging command
Code:
fastboot -i 0x0b05 flash staging system.blob
run smoothly. From that point, it becomes unresponsive again. It appears that although the flashing completes without errors, it doesn't take...or perhaps is inaccessible because the bootloader is jacked. Here's the output from Urkel's Fresh Start, for example:
Code:
Press any key to continue . . .
.: Now cleaning the TF201 partitions :.
erasing 'cache'...
OKAY [ 2.160s]
finished. total time: 2.160s
******************************
erasing 'userdata'...
OKAY [ 39.644s]
finished. total time: 39.645s
******************************
erasing 'recovery'...
OKAY [ 1.953s]
finished. total time: 1.954s
******************************
erasing 'staging'...
OKAY [ 0.948s]
finished. total time: 0.948s
******************************
erasing 'system'...
OKAY [ 2.208s]
finished. total time: 2.209s
******************************
.: Partitions now clean, continuing to reboot back into bootloader. Do not miss
selecting FASTBOOT with VOL+D and then VOL+U on the USB Icon. If you miss it no
big deal reboot back into FASTBOOT before continuing :.
Press any key to continue . . .
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
.: Confirm you are in FASTBOOT before continuing to flash a fresh image/blob. Th
is will take 3-5 minutes because of the size of the image :.
Press any key to continue . . .
sending 'staging' (537604 KB)...
OKAY [ 94.723s]
writing 'staging'...
OKAY [ 1.329s]
finished. total time: 96.054s
rebooting...
finished. total time: 0.548s
.: No need to set up the tablet but let the tablet fully boot to welcome screen
then hold down the power to shut if off. When off turn it back on and enter FAST
BOOT. Once at FASTBOOT then continue :.
Press any key to continue . . .
It appears fine...however, it doesn't reboot, even thought the command said it was successful. So, I try manually rebooting and get stuck at the welcome screen again. It's a vicious cycle... Anyhow, this type of situation is the same for all of the other workarounds that I have found to this problem.
It seems that fastboot is semi-responsive, but no actions that I take are recognized upon reboot. I would love to try and figure out why fastboot is having these issues... and unbrick my tablet. So, please let me know if I have missed any threads that have exactly this solution (ie. fastboot works...but not really).
Thanks in advance, and let me know if I missed details that are necessary.
Click to expand...
Click to collapse
If you don't have universal naked drivers downloaded and installed, do that.... also you should install twrp as your recovery, just make sure you get the right one.... I think I read at the top you installed JB so your bootloader is probably JB...... don't install the ics twrp over the jb bootloader or you will have a unrecoverable mess I think.....
Gage_Hero said:
If you don't have universal naked drivers downloaded and installed, do that.... also you should install twrp as your recovery, just make sure you get the right one.... I think I read at the top you installed JB so your bootloader is probably JB...... don't install the ics twrp over the jb bootloader or you will have a unrecoverable mess I think.....
Click to expand...
Click to collapse
Hey thanks for the help. Unfortunately, as I mentioned, I already tried the naked drivers to no avail. Just to be safe, I tried once more, removed/deleted/uninstalled the drivers and even force turned off driver installation for good measure to make sure. I have the same behavior with both the ASUS drivers and the Universal Naked drivers.
I think I forgot to mention explicitly that I tried installing twrp as recovery. I was careful to get the JB bootloader. It hasn't helped. I tried it again today after the re-install of naked drivers. Same behavior as before. Fastboot appears to flash the blob successfully,, but then the prime becomes unresponsive, will not reboot via fastboot, and sticks at flash screen and no RCK.
Any other things that I could have missed or done incorrectly?
Bootloader Error
Hi,
any solution to this yet? I do have the exact same problem!
It seems to me the procedure is locked and it accepts only one comand (maybe the key) then rejects al subsequent comands.
.
From everything I have seen "Unrecoverable bootloader error" means exactly what it says. its unrecoverable. You need a new motherboard
Bootloader Error
Well, that's exactly what Asus wants us to think. My logical thinking tells me there is no defect other than a software failure in connection with Asus locking down bootloaders in order to torture their customers.
I can still access Fastboot, it is just locked down. I guess the first comand (which it always accepts should be a key to unlock the fastboot procedure, without that key nothing is possible. Why can they not recover it at the service center? Maybe they do not want the key to get public.
It's all business after all.
Still, they use open source software for free and then neglect warranty...
I just cannot understand. Well, not Asus for me again I guess...
whycali said:
From everything I have seen "Unrecoverable bootloader error" means exactly what it says. its unrecoverable. You need a new motherboard
Click to expand...
Click to collapse
Same problem, posted http://forum.xda-developers.com/showthread.php?t=2154851
Hello All.
Apologies if I am missing something obvious, but I am experiencing an issue with my US VZW XT912. Over a year ago, the phone bricked itself seemingly out of nowhere, only booting up into the "Encryption Failed" state. I went ahead and put it into AP fastboot and grabbed a copy of Matt's droid razr utility. I installed the motorola drivers and fired up the utility, then tried to flash the factory JB image to it WITH data wipe (option 1 on the utility). The process started, but right after "sending 'mbm' (512 KB)... OKAY [ 0.092s]" I got the message in the title of this post: "writing 'mbm'... FAILED (remote: )".
No matter how many different USB cables I tried, or how many different USB ports I used on several different computers and Operating Systems, I always got the same result; "writing 'mbm'... FAILED (remote: )".
I've gone as far as using ADB by hand and going through the flash instructions from an XML file step by step, but that fails in the same spot as well. RSDlite also failed.
My suspicions here are either A) The partition table is messed up somehow (which I unfortunately do not know how to fix) or B) The flash memory is actually just bad on the phone, which would obviously suck.
Now, most of my troubleshooting took place a year or so ago, so I've included a screenshot of Matt's utility that I just ran this morning. imgur<dot>com / QHsJbtO (sorry about the link; new user)
Any input is most appreciated.
Regards,
Steve P
physicsmaster131 said:
Hello All.
Apologies if I am missing something obvious, but I am experiencing an issue with my US VZW XT912. Over a year ago, the phone bricked itself seemingly out of nowhere, only booting up into the "Encryption Failed" state. I went ahead and put it into AP fastboot and grabbed a copy of Matt's droid razr utility. I installed the motorola drivers and fired up the utility, then tried to flash the factory JB image to it WITH data wipe (option 1 on the utility). The process started, but right after "sending 'mbm' (512 KB)... OKAY [ 0.092s]" I got the message in the title of this post: "writing 'mbm'... FAILED (remote: )".
No matter how many different USB cables I tried, or how many different USB ports I used on several different computers and Operating Systems, I always got the same result; "writing 'mbm'... FAILED (remote: )".
I've gone as far as using ADB by hand and going through the flash instructions from an XML file step by step, but that fails in the same spot as well. RSDlite also failed.
My suspicions here are either A) The partition table is messed up somehow (which I unfortunately do not know how to fix) or B) The flash memory is actually just bad on the phone, which would obviously suck.
Now, most of my troubleshooting took place a year or so ago, so I've included a screenshot of Matt's utility that I just ran this morning. imgur<dot>com / QHsJbtO (sorry about the link; new user)
Any input is most appreciated.
Regards,
Steve P
Click to expand...
Click to collapse
do you know which version the utility is?
what RSD Lite version?
Firmware version?
what is on AP Fastboot screen?
Sent from my XT1060 using XDA Labs
sd_shadow said:
do you know which version the utility is?
what RSD Lite version?
Firmware version?
what is on AP Fastboot screen?
Click to expand...
Click to collapse
Couldn't find a version number in the batch file of Matt's utility, but the created date on the file is August 26, 2014.
RSDLite 6.1.4
Was running stock JB when it bricked but I believe the phone shipped with ICS. I never loaded any custom ROMS, though.
"
AP Fastboot Flash Mode (S)
0A.77
eMMC Info: Size 16G
To return to normal mode - first press power key to power down
Device is LOCKED. Status Code: 0
Battery OK
OK to Program
Transfer Mode:
USB Connected
"
Some (relatively poor) pictures of the AP screen: imgur<dot>com / a / mEFxz
sd_shadow said:
do you know which version the utility is?
what RSD Lite version?
Firmware version?
what is on AP Fastboot screen?
Sent from my XT1060 using XDA Labs
Click to expand...
Click to collapse
This is probably a dead thread, but I've been troubleshooting this issue on/off for over a year and still haven't managed to make any headway. Any other thoughts?
physicsmaster131 said:
This is probably a dead thread, but I've been troubleshooting this issue on/off for over a year and still haven't managed to make any headway. Any other thoughts?
Click to expand...
Click to collapse
What's the bootloader saying?
Sent from my sailfish using XDA Labs
sd_shadow said:
What's the bootloader saying?
Click to expand...
Click to collapse
Everything looks pretty normal on the bootloader. Trying to attach images but I keep getting an error so I'll type it out:
AP Fastboot Flash Mode (S)
0A.77
eMMC Info: Size 16G
To Return to normal mode - first press power key to power down
Device is LOCKED. Status Code: 0
Battery OK
OK to Program
Transfer Mode:
USB Connected
Some additional info:
When I try to boot normally I always get the "encryption failed" screen, and the reset button doesn't do anything.
When I try to boot into recovery, the android logo comes up, but I am never able to make it into the actual recovery menu.
Hi,
I'm newb in this forum and i'm looking for your advice and help,
my situation is as titled in the thread...my phone stuck on huawei logo...the situation starts when i'd tried to flash TWRP recovery..but it seems that was a wrong one...after then i erased system (stupid i was :crying: ) trying a factory reset (i'd downloaded the original stock)....this is when things gets worst ...now i can't get into recovery mode and the phone stuck on the logo...one last detail when the phone is turned on and usb connected to the PC the Hisuite seems identifying the phone but couldn't connect...
any help would be very appreciated
thank you all for your time,
BoFar said:
Hi,
I'm newb in this forum and i'm looking for your advice and help,
my situation is as titled in the thread...my phone stuck on huawei logo...the situation starts when i'd tried to flash TWRP recovery..but it seems that was a wrong one...after then i erased system (stupid i was :crying: ) trying a factory reset (i'd downloaded the original stock)....this is when things gets worst ...now i can't get into recovery mode and the phone stuck on the logo...one last detail when the phone is turned on and usb connected to the PC the Hisuite seems identifying the phone but couldn't connect...
any help would be very appreciated
thank you all for your time,
Click to expand...
Click to collapse
FYI,
now i can get into bootloader but without a recovery...
with the already downloaded stock rom i'd extracted all IMG files from the UPDATE.APP.
the step where i'm stucking is that flashing system with fastboot gives this :
target reported max download size of 266338304 bytes
erasing 'system'...
OKAY [ 1.094s]
sending sparse 'system' (259466 KB)...
OKAY [ 17.422s]
writing 'system'...
FAILED (remote: size too large)
finished. total time: 18.547s
the system.img is 2.39 Go.
same things and messages happens with recovery & boot files [ FAILED (remote: size too large) ]
I thank you advising how to resolve this
[SOLVED]
Here's steps that I made (after a long search with Dr. GOOGLE ):
1- Download & install the Android Studio and its SDK tools (that include fastboot and adb latest version). when having the famous message of FAILED (....TOO LARGE) use the -S switch and be patient with SYSTEM.IMG since file size is big (first tries gave me the error message but after many try it works),
2- Download the official stock ROM from Huawei webpage,
3- Download Huawei Update extractor,
4- Extract BOOT.IMG & RECOVERY.IMG & SYSTEM.IMG from the UPDATE.APP extracted file,
5- flash sequentially : RECOVERY then BOOT then SYSTEM (Remember the reboot after each flash),
That's all...Folks