Related
Hiya,
After dealing with a half-bricked Xoom, I did some research on this problem and found a solution.
If in any case, you happen to get stuck on the "Motorola Dual-Core Technology"
Solution to this (For the MZ604, One-Click rooted):
MZ604 Stock .imgs Download: http://developer.motorola.com/products/software/
*Make sure you have fastboot in the same directory as your adb for easy access*
1. Plug in your USB cord
2. Turn off your Xoom (Vol-Up + Power)
3. Boot into fastboot (Vol-Down + Power)
4. On your computer, open up a command prompt, and type the following:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
-or-
Code:
fastboot flash boot <path to boot.img>
fastboot flash system <path to system.img>
fastboot flash recovery <path torecovery.img>
fastboot flash userdata <path userdata.img>
fastboot erase cache
fastboot oem lock
5. Reboot the Xoom
Code:
fastboot reboot
6. There you go, back to stock!
On the real though, if you can get to Fastboot (or even the Moto "Android Recovery" state), you're not THAT bricked you've got to relock and go back to out-of-box; just keep a known-good boot.img around somewhere.
You just saved my life!
Thanks for sharing OP.
I take it this method is the same for 3.1?
I hope this works. Although, I can't turn my xoom off. It also appears that my computer will not recognize my device when it is plugged in. In addition, I can't turn off my Xoom? It just reboots... so I can't enter fastboot mode.
I just posted this in a new thread.
Lcsglvr said:
I tried reverting back to stock using the "one click" root/unroot tool that was the first to come out for the Xoom.
Anyway, I tried the unroot process and everything was going fine, until something occurred. Now, it tries to boot up and says at the Moto Dual Core Technology screen, "Failed to boot LNX 0x0004 // Starting RSD mode 2".
Can someone help
Click to expand...
Click to collapse
Can anyone help!
Lcsglvr said:
I hope this works. Although, I can't turn my xoom off. It also appears that my computer will not recognize my device when it is plugged in. In addition, I can't turn off my Xoom? It just reboots... so I can't enter fastboot mode.
I just posted this in a new thread.
Can anyone help!
Click to expand...
Click to collapse
same here, anyone help ((
Lcsglvr said:
I hope this works. Although, I can't turn my xoom off. It also appears that my computer will not recognize my device when it is plugged in. In addition, I can't turn off my Xoom? It just reboots... so I can't enter fastboot mode.
I just posted this in a new thread.
Can anyone help!
Click to expand...
Click to collapse
You can still enter fastboot if you xoom won't shut off. Just hold the appropria oncete buttons as it reboot. Happened to me last night upgrading to 3.1. It. Wouldn't shut down at all. Once I got into fastboot my computer saw it and I was able to fix
Honestly, I almost went through all of this last night when my WIFI Xoom got stuck in a boot loop.
However, I noticed that when my recovery went to flash the new 3.1 file, I felt like it didn't take as long as it should have. The file was the right size and all and it even said that everything installed successfully, but it just kept boot looping regardless of trying over and over. So I went ahead and re-downloaded the 3.1 file and repeated the steps to flash it and everything worked.
So, before you spend a whole lot of time restoring your Xoom, simply re-download the files and try it one more time. It worked for me.
rebill said:
You can still enter fastboot if you xoom won't shut off. Just hold the appropria oncete buttons as it reboot. Happened to me last night upgrading to 3.1. It. Wouldn't shut down at all. Once I got into fastboot my computer saw it and I was able to fix
Click to expand...
Click to collapse
Thanks! Finally have some hope to recovering. I'll post steps I took later once I get this damn thing fixed.
hmmm... I'm in fastboot supposedly and tried to flash boot.img but it seems to be stuck at <waiting for device>
This happen to anyone else?
After search seems like a driver issue, but I have installed the drivers... I was previous rooted, so I know I have the drivers. Just to be sure, I ran the MotoHelper again. I don't understand. It's just seeing my device on the "Starting Fastboot protocol support."
help?
Lcsglvr said:
hmmm... I'm in fastboot supposedly and tried to flash boot.img but it seems to be stuck at <waiting for device>
This happen to anyone else?
After search seems like a driver issue, but I have installed the drivers... I was previous rooted, so I know I have the drivers. Just to be sure, I ran the MotoHelper again. I don't understand. It's just seeing my device on the "Starting Fastboot protocol support."
help?
Click to expand...
Click to collapse
Yes. How did I fix it? I returned the xoom and had a new one two days later.
If the screen says something like "Entering RSD 2" then you're boned. The xoom won't be recognized in either the current state or in fastboot state by the computer, so no amount of commands will help. Even having the stock images doesn't help with that. Even RSDLite can't see the xoom in that state.
There have been several reports of people just being honest to Motorola and them fixing the device under the warranty.
Hmm honesty. I'll give it a shot.
Sent from my ADR6300 using XDA App
Is the final OEM lock necessary? It's quite a pain as your userdata gets wiped if you unlock it...
I was stuck on bootloop, with unrecognised device, through adb was able to get back into clockwork recovery somehow at first boot, think twice down volume? Could be wrong.
I was able tto rreflash zip 3.1 over thet top again.
sry if this is different and unhelpful, bu imagine things are pretty desperate if you are considering returning the device
zerin said:
Yes. How did I fix it? I returned the xoom and had a new one two days later.
If the screen says something like "Entering RSD 2" then you're boned. The xoom won't be recognized in either the current state or in fastboot state by the computer, so no amount of commands will help. Even having the stock images doesn't help with that. Even RSDLite can't see the xoom in that state.
There have been several reports of people just being honest to Motorola and them fixing the device under the warranty.
Click to expand...
Click to collapse
You're not boned at all. I had that happen to me so I just got back into fastboot, downloaded the files in the OP put ADB, Fastboot and the adb extensions into the file I downloaded then ran the commands and got me XOOM back up and running fine.
jbartcaps said:
You're not boned at all. I had that happen to me so I just got back into fastboot, downloaded the files in the OP put ADB, Fastboot and the adb extensions into the file I downloaded then ran the commands and got me XOOM back up and running fine.
Click to expand...
Click to collapse
You were likely in RSD 3, which is recognized by the computer. RSD 2 means adb and fastboot cannot see the device at all, so no flashing images is possible.
There's several states that all look very similar. Because some success was had with one doesn't mean it works for all. Motorola recognizes and is telling users that, in this state, the device needs to be sent back to them.
Can someone help us wifi xoom. Im stuck on the motorola screen and have a lil experience. I can fast boot reboot/fastboot device and it work but cant get the files from the hwi69 to fastboot on to it. I think im entering the commands wrong. Any advice would be appreciated
TheRedDroid said:
Hiya,
After dealing with a half-bricked Xoom, I did some research on this problem and found a solution.
If in any case, you happen to get stuck on the "Motorola Dual-Core Technology"
Solution to this (For the MZ604, One-Click rooted):
MZ604 Stock .imgs Download: http://developer.motorola.com/products/software/
*Make sure you have fastboot in the same directory as your adb for easy access*
1. Plug in your USB cord
2. Turn off your Xoom (Vol-Up + Power)
3. Boot into fastboot (Vol-Down + Power)
4. On your computer, open up a command prompt, and type the following:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
-or-
Code:
fastboot flash boot <path to boot.img>
fastboot flash system <path to system.img>
fastboot flash recovery <path torecovery.img>
fastboot flash userdata <path userdata.img>
fastboot erase cache
fastboot oem lock
5. Reboot the Xoom
Code:
fastboot reboot
6. There you go, back to stock!
Click to expand...
Click to collapse
Very good info to get into fastboot protocol:
Much thanks for the info. Worked like a champ. On an updated 3.2.1 XOOM I did an unlock, re-locked the wrong way, soft bricked, unbricked back to locked state. Finally followed your steps applied stock files and XOOM is re-locked and stock rocking back at 3.01. I needed to do all this to make sure I could get it back to stock in case it goes back to BB in 2 weeks. I was lucky enough to find one at a BB just not sure if I'll keep it. I plan on trying out some roms plus I heard Motorola is planning on doing an ICS push to the XOOM. ICS is very nice. It runs great on my unlocked Verizon G-Nex.. Again Thanks..
This post not only saved my half-bricked non-rooted Xoom, but also let me flash it from the Singapore firmware (bought if from Amazon, don't ask lol) to the regular USA firmware so that I can properly root it!
Thank you so very much!!
After using rsdlite to flash telstra Australia over FR jellybean leak, my phone is now bricked because it says at 16/19: no valid PIV block in SP for system. Piv validation failed (system).*So I tried to re flash the FR Vodafone ica stock through rsd and then it fails at 16/19 and says phone read failed.*Now my phone can't get into recovery, and is stuck at fast boot..*What can I do??
The PIV error means the image you tried to flash wasn't properly marked and signed (not sure about the details, but there is some magic header missing I'm the file...), you may need an unlocked bootloader and/or fastboot instead of rsdlite, or something else, to flash that.
If you can get into fastboot mode, you should be able to unbrick it, with a properly signed image, like the one coming from a leak or official fastboot.
Make sure you're not running rsd lite from a virtual machine like virtual box, as that will fail. I had virtual box with win xp running on my macbook and it won't work, I had to use a real windows machine, or fastboot.
If you're comfortable with the command line, get the system image out of the zip file and try with fastboot instead:
fastboot flash system system.img.ext4
If you still get errors, with either rsdlite or fastboot, post the exact error then we'll see.
Sent from my XT907 using xda app-developers app
tried flashing the system_signed with the fastboot command from official telstra stock ics, (flashed the firmware (which got the error at 16/19 system - phone read failed error), then took out the system_signed and tried to flash that.
error is bootloader prevalidation failed when trying to write in the cmd window
error on fastboot mode is :invalid entry hash for system:index=0
EDIT: ok i changed the system_signed (to system)signed.ex4 and flashed it with the ex4 extension, and wierdly it started working and finished writing system with an OKAY!
but now its just stuck at motorola logo, and not loading, just seems to be stuck at the M logo..
i guess it means 16/19 flash step is over, so what is 17/19? do i fast boot the rest, and if so, which files are they?
royalbloodvi said:
tried flashing the system_signed with the fastboot command from official telstra stock ics, (flashed the firmware (which got the error at 16/19 system - phone read failed error), then took out the system_signed and tried to flash that.
error is bootloader prevalidation failed when trying to write in the cmd window
error on fastboot mode is :invalid entry hash for system:index=0
EDIT: ok i changed the system_signed (to system)signed.ex4 and flashed it with the ex4 extension, and wierdly it started working and finished writing system with an OKAY!
but now its just stuck at motorola logo, and not loading, just seems to be stuck at the M logo..
i guess it means 16/19 flash step is over, so what is 17/19? do i fast boot the rest, and if so, which files are they?
Click to expand...
Click to collapse
I'm not sure exactly which firmware/zip file you are using, but there should be a .xml file in it. Unzip the whole thing into some folder, then open the .xml file with your favorite text editor (yeah, even wordpad ... but not notepad please), there you'll see all the steps, so you can search for "system" and see what's after ... in fact you can edit that file, remove the steps you don't want, then open it and run it in rsdlite
I'm not really sure, but since you managed to flash system manually, you could try removing the system line from that .xml file, then flash the whole thing with rsd lite, that should flash everything else.
Edit: are you bootloader unlocked by chance? You shouldn't need it to restore your phone, but, for example, an unlocked bootloader will let you flash garbage on system, while the locked one won't, so if you are locked and system flashed with an OKAY, you're pretty sure it's good
aslomagic said:
I'm not sure exactly which firmware/zip file you are using, but there should be a .xml file in it. Unzip the whole thing into some folder, then open the .xml file with your favorite text editor (yeah, even wordpad ... but not notepad please), there you'll see all the steps, so you can search for "system" and see what's after ... in fact you can edit that file, remove the steps you don't want, then open it and run it in rsdlite
I'm not really sure, but since you managed to flash system manually, you could try removing the system line from that .xml file, then flash the whole thing with rsd lite, that should flash everything else.
Edit: are you bootloader unlocked by chance? You shouldn't need it to restore your phone, but, for example, an unlocked bootloader will let you flash garbage on system, while the locked one won't, so if you are locked and system flashed with an OKAY, you're pretty sure it's good
Click to expand...
Click to collapse
ok so i managed to flash the system_signed manually, edited out system_signed from the xml file, and all went well.
and went to reboot. flash complete.
now when it loads up, all went back to step 1.
and ends up being fastboot reason: sticky bit factory_fastboot
do u happen to have the boot.img of stock ics? maybe thats the reason..
&
same error, PIV validation failed... i even went to morola service engineer. he said i killed the motherboard and its $300 replacement... is this true?
royalbloodvi said:
ok so i managed to flash the system_signed manually, edited out system_signed from the xml file, and all went well.
and went to reboot. flash complete.
now when it loads up, all went back to step 1.
same error, PIV validation failed... i even went to morola service engineer. he said i killed the motherboard and its $300 replacement... is this true?
Click to expand...
Click to collapse
So, what do you mean "back to step 1" .. does the phone boot at all? Does it get past bootloader/fastboot mode?
Again, is your bootloader locked or unlocked?
I doubt you killed the motherboard, but who knows ... if you still get fastboot mode you should be able to flash it, you just need to flash something that works.
Was the jellybean leak working? maybe just reflash that for now, so you confirm that it still works, and at least you won't have a brick ...
aslomagic said:
So, what do you mean "back to step 1" .. does the phone boot at all? Does it get past bootloader/fastboot mode?
Again, is your bootloader locked or unlocked?
I doubt you killed the motherboard, but who knows ... if you still get fastboot mode you should be able to flash it, you just need to flash something that works.
Was the jellybean leak working? maybe just reflash that for now, so you confirm that it still works, and at least you won't have a brick ...
Click to expand...
Click to collapse
back to step 1, as in after going through the rsd lite process and removing system from the xml, it completes the flashing process. but it gets to the motorola, stock recovery, and when it looks liek it was success, it goes back to the initial error piv validation failed..
Now I cant even try go back to jelly bean leak, cause when flashing it fails at step 1. it seems like my phone is even more screwed up now.
error is : 1/17 flash partition ''partition_signed"" -> phone returned FAIL..
as a side note: i accidentally flashed the CWM backup boot.img to my phone in my other post: http://forum.xda-developers.com/showthread.php?p=35045589#post35045589
is this the reason it keeps failing now when it should not? i flashed this command halfway during the rsd lite process..
royalbloodvi said:
back to step 1, as in after going through the rsd lite process and removing system from the xml, it completes the flashing process. but it gets to the motorola, stock recovery, and when it looks liek it was success, it goes back to the initial error piv validation failed..
Now I cant even try go back to jelly bean leak, cause when flashing it fails at step 1. it seems like my phone is even more screwed up now.
error is : 1/17 flash partition ''partition_signed"" -> phone returned FAIL..
Click to expand...
Click to collapse
Hmm, maybe somebody with more knowledge can help you better at this point, but let's see ...
If you can, look in the actual system file you are trying to flash (system_signed I guess) with a hex editor (or heck, again, even wordpad), and see if you see anything that says MOT_PIV ... if not, well, yeah, it will probably fail with that error.
I just seen you said you flashed a boot.img from something completely unrelated ... are you able to flash back a sane boot.img from jellybean/telstra/something that is known working with fastboot (I'd say forget rsdlite here, but it's a matter of preference)?
Also, let's assume your bootloader is unlocked, cause you keep not saying. Try to re-lock it, then flash. If you get an error when before you were getting success, as assuming the things you are flashing are supposed to be signed, then it means it's not really flashing it right. At least, it'll tell you what is not flashed right...
Other than that, I'd try flashing things manually with fastboot (I like it better than rsdlite), especially partition, then boot and/or system, maybe from jellybean, and see if the phone gets a little further in booting ...
aslomagic said:
Hmm, maybe somebody with more knowledge can help you better at this point, but let's see ...
If you can, look in the actual system file you are trying to flash (system_signed I guess) with a hex editor (or heck, again, even wordpad), and see if you see anything that says MOT_PIV ... if not, well, yeah, it will probably fail with that error.
I just seen you said you flashed a boot.img from something completely unrelated ... are you able to flash back a sane boot.img from jellybean/telstra/something that is known working with fastboot (I'd say forget rsdlite here, but it's a matter of preference)?
Also, let's assume your bootloader is unlocked, cause you keep not saying. Try to re-lock it, then flash. If you get an error when before you were getting success, as assuming the things you are flashing are supposed to be signed, then it means it's not really flashing it right. At least, it'll tell you what is not flashed right...
Other than that, I'd try flashing things manually with fastboot (I like it better than rsdlite), especially partition, then boot and/or system, maybe from jellybean, and see if the phone gets a little further in booting ...
Click to expand...
Click to collapse
sorry it is a locked bootloader.
so what do i do if i do see mot_piv?
royalbloodvi said:
sorry it is a locked bootloader.
so what do i do if i do see mot_piv?
Click to expand...
Click to collapse
Nothing, if you see that you know it's (probably) a legitimate, signed image and not garbage, or in another format
Not sure if the file name actually matters, but yeah, name it system.img.ext4 and flash it (not ex4, ext4).
Try to flash boot from a known good firmware (i.e. from jellybean, it was working, right?)
fastboot flash boot boot.img
Then check if it boots, it should at least show the motorola logo (but that's not enough of course).
If it doesn't, flash the corresponding system, again with fastboot, see what happens ... worst case, can you unlock the bootloader and flash CWM or something, like madmonkey57 was suggesting in the other thread (i.e. is your bootloader unlockable)?
aslomagic said:
Nothing, if you see that you know it's (probably) a legitimate, signed image and not garbage, or in another format
Not sure if the file name actually matters, but yeah, name it system.img.ext4 and flash it (not ex4, ext4).
Try to flash boot from a known good firmware (i.e. from jellybean, it was working, right?)
fastboot flash boot boot.img
Then check if it boots, it should at least show the motorola logo (but that's not enough of course).
If it doesn't, flash the corresponding system, again with fastboot, see what happens ... worst case, can you unlock the bootloader and flash CWM or something, like madmonkey57 was suggesting in the other thread (i.e. is your bootloader unlockable)?
Click to expand...
Click to collapse
unfortunately its not dev edition, device is locked.. =(
but i will try the JB method and see what happens now
royalbloodvi said:
sorry it is a locked bootloader.
Click to expand...
Click to collapse
Sorry, I just realized ... yours is a XT925 right? You kept talking about Telstra, is yours the australian version?
I'm pretty sure you can unlock the bootloader, get the code from motorola. You need dev edition only for verizon model, all others should be unlockable even if retail. Yes you'll lose the warranty, but if the alternative is a paperweight ...
aslomagic said:
Sorry, I just realized ... yours is a XT925 right? You kept talking about Telstra, is yours the australian version?
I'm pretty sure you can unlock the bootloader, get the code from motorola. You need dev edition only for verizon model, all others should be unlockable even if retail. Yes you'll lose the warranty, but if the alternative is a paperweight ...
Click to expand...
Click to collapse
ive tried to unlock the bootloader, got the code, but it just doesnt seem to unlock when doing the fastboot oem unlock command..
also, after writing system into it, everything works, motorola logo boots. but nothing happens and just stays like that,
when trying to enter recvery, comes up with errors :
e:\ cannot mount cache/recovery/command
e:\ cannot open cache/recovery/caller
and similar cache/recovery errors
royalbloodvi said:
ive tried to unlock the bootloader, got the code, but it just doesnt seem to unlock when doing the fastboot oem unlock command..
also, after writing system into it, everything works, motorola logo boots. but nothing happens and just stays like that,
when trying to enter recvery, comes up with errors :
e:\ cannot mount cache/recovery/command
e:\ cannot open cache/recovery/caller
and similar cache/recovery errors
Click to expand...
Click to collapse
I am in the exact same boat as you... No success and I have tried everything!
royalbloodvi said:
ive tried to unlock the bootloader, got the code, but it just doesnt seem to unlock when doing the fastboot oem unlock command..
also, after writing system into it, everything works, motorola logo boots. but nothing happens and just stays like that,
when trying to enter recvery, comes up with errors :
e:\ cannot mount cache/recovery/command
e:\ cannot open cache/recovery/caller
and similar cache/recovery errors
Click to expand...
Click to collapse
Well, at this point, I really don't know ... if it happened to me, I'd be in "trial and error mode" now
Have you tried wiping the cache partition (fastboot erase cache, I think)?
Also, you didn't say if you managed to flash back a known-good boot.img, as well ...
I unbricked my phone, had to mix and match system files between telstra and Vodafone fr, and get it to boot up to the Motorola logo.
If you so manage to get to logo, it can be re stored just take it to Motorola service centre and they will flash their software and Walah.. Costed me 55$ but but better than a expensive junk
Sent from my XT925 using xda app-developers app
Paying is not an option. I'm currently fixing my Atrix HD. Not that hard once you find the right file. Mine failed in RSDlite on step 1/23 and I just hit it again and it went through all the way. You should've tried that. Next time, because there WILL be a next time, just send through the xml file again through rsdlite.
My phone just finished booting up as I typed this.
Hi everyone,
this is the first time i post in this forum and i am totally beginner to the andriod system.....And i do think i am exactly in the same status with nicolas(http://forum.xda-developers.com/showthread.php?p=33211630)----my a700 bricked beacuse proceed ICS root's procedures in jb system
i have tried MD instruction to get into fastboot mode....but i dont know if i get into fastboot mode:
i only get "acer" logo in the middle and i have two statement at the top left corner:
"Bootloader version JB-653b3d3 (Unlock Mode)
Bootloader VJB-653b3d(UnlockMode): Starting Fastboot USB download protocol"
When i open "window device manager" in PC, it showed "ADB interface"-"Acer fastboot interface"
Have i got into fastboot mode?
what is my next step then?????:crying::crying::crying::crying:
i dont know how can i copy image from Verboth's ROM(http://forum.xda-developers.com/showthread.php?t=1952124)
THX A LOT!!!!!!!!!!!!!!
hksrichard said:
Hi everyone,
this is the first time i post in this forum and i am totally beginner to the andriod system.....And i do think i am exactly in the same status with nicolas(http://forum.xda-developers.com/showthread.php?p=33211630)----my a700 bricked beacuse proceed ICS root's procedures in jb system
i have tried MD instruction to get into fastboot mode....but i dont know if i get into fastboot mode:
i only get "acer" logo in the middle and i have two statement at the top left corner:
"Bootloader version JB-653b3d3 (Unlock Mode)
Bootloader VJB-653b3d(UnlockMode): Starting Fastboot USB download protocol"
When i open "window device manager" in PC, it showed "ADB interface"-"Acer fastboot interface"
Have i got into fastboot mode?
what is my next step then?????:crying::crying::crying::crying:
i dont know how can i copy image from Verboth's ROM(http://forum.xda-developers.com/showthread.php?t=1952124)
THX A LOT!!!!!!!!!!!!!!
Click to expand...
Click to collapse
Eh.... another one
Mate, you probably only need to fastboot a JB 700 boot.img on your tab.
Yes, you are in fastboot mode.
So if I get this right, you have a JB operating system, but you decided to use an ICS root procedure?
If you haven't changed anything else, it should be simple enough as running Verboth's 700 JB easy root program. If you don't want to do the whole thing, then you can simply install his boot.img by using fastboot.
fastboot flash boot xxxxxxxxx.img (where xxxxxxxx.img is the name of the boot.img)
Did you attempt to install some type of update file? Just asking to be sure I know exactly how you got to this situation.
MD
Moscow Desire said:
Eh.... another one
Mate, you probably only need to fastboot a JB 700 boot.img on your tab.
Yes, you are in fastboot mode.
So if I get this right, you have a JB operating system, but you decided to use an ICS root procedure?
If you haven't changed anything else, it should be simple enough as running Verboth's 700 JB easy root program. If you don't want to do the whole thing, then you can simply install his boot.img by using fastboot.
fastboot flash boot xxxxxxxxx.img (where xxxxxxxx.img is the name of the boot.img)
Did you attempt to install some type of update file? Just asking to be sure I know exactly how you got to this situation.
MD
Click to expand...
Click to collapse
Thx for yr help so i have the command of flashing img!!! i havent attempt any update file or other things but i have clicked the factory reset once...does it matter???
Do u prefer the img inside the easy root or iconiaN2.6??? i dont know which one i should choose??? my version is jelly bean 4.1.1
so after i download it, do i have to move the boot.img to the sdk/platform-tools folder???
or do i just download it any place, then change the directory in the Window Command Prompt to the Rom folder???
lets say "cd C:\ iconiaN 2.6"?? then "C:\ iconiaN2.6\fastboot flash boot boot.img"??
Thz for yr patience...
Moscow Desire said:
Eh.... another one
Mate, you probably only need to fastboot a JB 700 boot.img on your tab.
Yes, you are in fastboot mode.
So if I get this right, you have a JB operating system, but you decided to use an ICS root procedure?
If you haven't changed anything else, it should be simple enough as running Verboth's 700 JB easy root program. If you don't want to do the whole thing, then you can simply install his boot.img by using fastboot.
fastboot flash boot xxxxxxxxx.img (where xxxxxxxx.img is the name of the boot.img)
Did you attempt to install some type of update file? Just asking to be sure I know exactly how you got to this situation.
MD
Click to expand...
Click to collapse
ar...i have forgotten to answer yr last q...How i get to this situation??
After googling, all webs say 4.2 is jelly bean and 4.0 is ICS...i guess i am ICS i am so careless
then i follow yr thread instruction..i try method1. it still okay i can run the system but i cant root it. So i try the second method...
doing factory reset is after i have bricked..does it matter??
Moscow Desire said:
Eh.... another one
Mate, you probably only need to fastboot a JB 700 boot.img on your tab.
Yes, you are in fastboot mode.
So if I get this right, you have a JB operating system, but you decided to use an ICS root procedure?
If you haven't changed anything else, it should be simple enough as running Verboth's 700 JB easy root program. If you don't want to do the whole thing, then you can simply install his boot.img by using fastboot.
fastboot flash boot xxxxxxxxx.img (where xxxxxxxx.img is the name of the boot.img)
Did you attempt to install some type of update file? Just asking to be sure I know exactly how you got to this situation.
MD
Click to expand...
Click to collapse
At last, I have chosen the boot.img in the easy root zip from Verboth...but i type the flash command it said it does not recognized.
BUT after i move the boot.img into the platform-tools next to the fastboot.exe, i type the command again and it works!!!!!!!!!!!!!!!!!!!!!!!!!
Thx a lot!!!!!!!!!!!!!!!!!!!!!!!!!1
my tablet is back!!!!!!!!!!! i can go back to the normal mode !!!!!
One last question about the root...so after i done all these step, can my A700 still follow yr easy root guide in here???: http://forum.xda-developers.com/showthread.php?t=1997350
my A700 details:
Andriod Version: 4.1.1
Kernel version: 3.1.10+
Image version: Acer_AV051_A700_RV18RC02_PA_CA
Build number: Acer_AV051_A700_1.053.00_PA_CA
Image P/N: FM.S1MA0.04F
can i still root by easy root??? looking forward to hearing yr gd news
anyway, you are very kind moderator, thx!
My computer doesn't recognize the A700 tablet. It say <waiting for device> after I try the boot.img command.
See daily results of ceribenanoche. Sinuano Noche
alan0923 said:
My computer doesn't recognize the A700 tablet. It say <waiting for device> after I try the boot.img command.
Click to expand...
Click to collapse
I figure it's issue with Windows 10. All the adb drivers are for windows 7. Ran on a computer running windows 7 and there is response showing bootloader locked. Will look at the other posts and continue. Thanks for all the posts on XDA.
I got the other computer on windows 10 to recongize the tablet as well now.
Guys really need some help.
Bought an unlocked Razr HD from the web, and ungraded via OTA from 4.0.4 to 4.1.2. Then I rooted using dan's method, ran the script, phone was rooted. Then i decided to install TWRP, same way, in fastboot mode, ran the cmd 'fastboot flash recovery twrp-2.5.0.0-recovery-vanquish.img' then rebooted, but what essentially happened after, i was never able to boot the phone in recovery and every single time i ended up with fastboot reason" flash failure.
Then i was able to recovery from falsh failure by running 'empty_radio.img', after rebooting, the phone started up normally, but stock recovery was still corrupt, every single time i used to get the 'red triangle dead andriod', so booted back into fastboot, performed a clean wipe with fastboot -w and booted back normally, and flash failure was gone, and i was was able to reboot the phone normally.
Then i decided to unlock the bootloader, was was successful using Dan's method; my goal was to install 4.2 from recovery. Then i installed DroidUtility and decided to perform an clean install wiping all data. The problem was at every step i got the FAILED (remote failure) line, soon after phone got stuck with fastboot reason: 'Sticky bit fastboot'.....every single time i reboot phone gets stuck in the initial screen ' WARNING BOOTLOADER UNLOCKED' and thats it....i can't do anything...stuck....screen stays on for 10mins, then reboots back to this screen and keeps on looping.
Please help guys!! i hope i haven't bricked the phone.
eomahos said:
Guys really need some help.
Bought an unlocked Razr HD from the web, and ungraded via OTA from 4.0.4 to 4.1.2. Then I rooted using dan's method, ran the script, phone was rooted. Then i decided to install TWRP, same way, in fastboot mode, ran the cmd 'fastboot flash recovery twrp-2.5.0.0-recovery-vanquish.img' then rebooted, but what essentially happened after, i was never able to boot the phone in recovery and every single time i ended up with fastboot reason" flash failure.
Then i was able to recovery from falsh failure by running 'empty_radio.img', after rebooting, the phone started up normally, but stock recovery was still corrupt, every single time i used to get the 'red triangle dead andriod', so booted back into fastboot, performed a clean wipe with fastboot -w and booted back normally, and flash failure was gone, and i was was able to reboot the phone normally.
Then i decided to unlock the bootloader, was was successful using Dan's method; my goal was to install 4.2 from recovery. Then i installed DroidUtility and decided to perform an clean install wiping all data. The problem was at every step i got the FAILED (remote failure) line, soon after phone got stuck with fastboot reason: 'Sticky bit fastboot'.....every single time i reboot phone gets stuck in the initial screen ' WARNING BOOTLOADER UNLOCKED' and thats it....i can't do anything...stuck....screen stays on for 10mins, then reboots back to this screen and keeps on looping.
Please help guys!! i hope i haven't bricked the phone.
Click to expand...
Click to collapse
Seeing how the phone is now updated to latest ota try Matt's Utility for the Droid RAZR HD i used this to get my phone is working condition then i did some adb and fastboot commands using some files to get rid of the sticky bit fastboot.
Heres a link to the RAZR HD utility: http://forum.xda-developers.com/showthread.php?t=2239425
Heres a link to get rid of the sticky bit fastboot menu (if you do end up getting this menu):http://forum.xda-developers.com/showthread.php?t=2260105
Hope this helps and good luck bro.
P.S if you did brick your phone its not the end of the world. the epic devs of XDA figured out how to fix problems like this. I bricked my phone by installing beats audio app ( worst mistake ever) came here for help and next thing i know my phone up and running like a charm ^^
well i did try matt's droid utility, and that's what put me in this state in the first place, since my stock recovery was corrupt, i decided to just clean install JB from Matt, but all the steps failed, it said remote failure at every step....and that was it! fastboot reason: flash failure,if i hold +/- and power, the phones boots up and gets stuck on the first screen..in this case since the bootloader is unlocked, it gets stuck on the WARNING message.
Also did try to fastboot with these commands:
adb reboot bootloader
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
fastboot erase userdata
fastboot erase cache
fastboot reboot
same, gets stuck on WARNING screen after reboot.
eomahos said:
well i did try matt's droid utility, and that's what put me in this state in the first place, since my stock recovery was corrupt, i decided to just clean install JB from Matt, but all the steps failed, it said remote failure at every step....and that was it! fastboot reason: flash failure,if i hold +/- and power, the phones boots up and gets stuck on the first screen..in this case since the bootloader is unlocked, it gets stuck on the WARNING message.
Also did try to fastboot with these commands:
adb reboot bootloader
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
fastboot erase userdata
fastboot erase cache
fastboot reboot
same, gets stuck on WARNING screen after reboot.
Click to expand...
Click to collapse
Have you tried flashing the phone with rsd lite?
Oh boy!! i made a major error, i someone didn't read the version...and used matt's utility xt912 on my xt925. is there a link for xt925? what can i do now? Can i use matt's xt926 on my 925?
eomahos said:
Oh boy!! i made a major error, i someone didn't read the version...and used matt's utility xt912 on my xt925. is there a link for xt925? what can i do now? Can i use matt's xt926 on my 925?
Click to expand...
Click to collapse
Try this: http://forum.xda-developers.com/showthread.php?t=2241788 from what i heard it works both on xt925 and xt926
oh wow....it did work. But now the problem is not sure if it locked the phone or not, but it's not recognizing my SIM. it said stock rom for both xt925/926. it seems that this is a verizom ROM, and on the device info it's listed at xt926. Not sure if that is the issue or not? can flashing the ROM lock the phone?
unfortunately, i have tried everything to install RSD, but it just wont install. Having a nightware, so all i need now is to install a stock JB ROM for xt925, but the recovery is corrupt, so need Matt's or MR. PARKINSON'S to flash a xt925 ROM. Can someone please help?
eomahos said:
unfortunately, i have tried everything to install RSD, but it just wont install. Having a nightware, so all i need now is to install a stock JB ROM for xt925, but the recovery is corrupt, so need Matt's or MR. PARKINSON'S to flash a xt925 ROM. Can someone please help?
Click to expand...
Click to collapse
Why dont you just flash twrp. Have it the same directory as the fastboot files from Hashcodes page on goo. Im. Cd to the directory with a command prompt and type faatboot flash recovery then the name of the file. Should overwrite your stock recovery and allow you to flash whatever you want.
Sent from my Transformer TF101 using xda premium
eomahos said:
unfortunately, i have tried everything to install RSD, but it just wont install. Having a nightware, so all i need now is to install a stock JB ROM for xt925, but the recovery is corrupt, so need Matt's or MR. PARKINSON'S to flash a xt925 ROM. Can someone please help?
Click to expand...
Click to collapse
I know you've stated that you can't get RSD to install, however if you can; perhaps borrow a friends computer to do it, then there's a variety of stock XT925 ROMs on this page http://sbf.droid-developers.org/vanquish_u/list.php
and instructions for flashing here http://www.andromods.com/tips-trick...-unroot-unbrick-droid-razr-maxx-hd-xt926.html which states its for the XT926 however I restored my 925 using my carrier's ROM from the first link and the tool and instructions on the second link. I only had one line with getvar in it to remove from the xml file. I've actually flashed both my carrier's ROM and then a generic one for my locale.
If you go this route, borrowing a friends computer, make sure you download the ROM from your carrier (assuming its there) with the higher version number or you'lle be attempting to flashing ICS and there's some post floating around that implies a downgrade from 4.1.2 to ICS causes problems.
The instructions look a little daunting but the xml files I saw, in both ROMs, were very short. Just be sure to use notpad when you edit. The other thing to be sure of, which isn't otherwise stated, is that RSDlite runs for a while even after the phone reboots. I made the mistake of pulling the cable when I got to the setup screen the first time I did it and thought it was a problem with the ROM or the flash of it. The reality, I think, after looking more carefully the second time, is that RSD is still running and doesn't say finished for a little bit after the boot and until I was still filling out the thing for the intial phone setup... Google acount, Google Plus, etc.
Link to a thread on the subject (also heavily 926 implied) http://forum.xda-developers.com/showthread.php?t=2211234
Since your'e unlocked you no longer need to use any exploit to gain root. Get a flashable supersu.zip on the phone, install a recovery and root you will have; just install the zip...
Have a full battery when starting the ROM flash.
thanks alot buddy, i'll start reading into it. So, i did finally manage to install TWRP, and did manage to flash the ROM with stock 4.2, tried both xt926/925, however, now the issue is i dont get any reception, nothing at all, everytime i search, it comes back with no network found. Can you please advise? i was able to bypass the corrupt recovery, install a clean 4.1.2 xt926 ROM, but i never got any reception, installed TWRP, then tried 4.2 ROMs. No, i get nothing...miss i mess up the radio?
eomahos said:
thanks alot buddy, i'll start reading into it. So, i did finally manage to install TWRP, and did manage to flash the ROM with stock 4.2, tried both xt926/925, however, now the issue is i dont get any reception, nothing at all, everytime i search, it comes back with no network found. Can you please advise? i was able to bypass the corrupt recovery, install a clean 4.1.2 xt926 ROM, but i never got any reception, installed TWRP, then tried 4.2 ROMs. No, i get nothing...miss i mess up the radio?
Click to expand...
Click to collapse
Hi, I tried replying to your PM however the server isn't reporting it sent or is having troubles sending or whatnot. Let me know if you got it or not.
In any case, of most relevance, who was your carrier when your phone did work? That is going to hopefully be the starting point, I believe.
...also, please quote my text if responding so that I get an email notification, otherwise I'll forget XDA exists for days at a time...
I have been rooting for about a year now, albeit largely with Samsung devices via Odin and CWM Recovery. I now have a Verizon Motorola RAZR HD (xt925) and have been unsuccessful with unlocking the bootloader. I decided to use Safestrap with it, and tried to load Eclipse-v5.0-build2-xt926, reportedly compatible with my XT925... now i am stuck with this screen:
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
AP Fastboot Flash Mode (S)
10.9B(*) (sha-1e9f557, 2013-02-14 09:13:08)
eMMC Info: Size 16GB
Deviced is LOCKED. Status Code: 0
Battery Low
Transfer Mode:
USB Connected
Failed to hab check for boot: 0x56
Fastboot Reason: Boot Failure
usb connected
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I have been looking to XDA for my answers over the last year. Help would be appreciated. Twenty-five dollars worth of appreciation.
(Yes, I have resorted to bribes....)
Easy fix,
download what ever version of the system software you had on it previously.
Flash it in fast boot mode.
?????
Profit.
Edit: also Verizon RAZRs are xt926 not xt925
Darbness said:
Easy fix,
download what ever version of the system software you had on it previously.
Flash it in fast boot mode.
?????
Profit.
Edit: also Verizon RAZRs are xt926 not xt925
Click to expand...
Click to collapse
Phone identified itself as 925... either way, i am unsure where i can find stock software for it and seem to be unable to flash anything from fastboot, because as it turns out, i am code-retarded. definitely profit when this is solved. I can "cd" through dos and get to where fastboot commands are entered and I have even tried to "fastboot recovery recovery.img" but for the life of me, i must be typing the string incorrectly somehow. But I am excellent at following clear-cut directions. i will try to find a stock image...for motorola, it is a .sbf file, right? If i seem stupid, i apologize, i'm not. just not up on all the nomenclature native to adb and fastboot (or linux). Thanks for helping me though.....i need it.
Ok,
First thing I want you to do is look on the back of the phone, It will have the model on the lower half of it.
Second thing is to find the official software.
For XT96:
http://sbf.droid-developers.org/vanquish/list.php
For xt925
http://sbf.droid-developers.org/vanquish_u/list.php
Flash the ROM file using RSD Lite.
If it dosnt work:
Make sure you have the moto drivers installed.
open up the .xml file in the rom and remove the "getvar" lines.
Still trying
Failed at 16/27 flash system system.img
What version did you try?
VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-4_VQW_CFC.xml
having a hard time finding other .xml files to use... any non-stock .xml available? really want to get into an AOKP/CM/PAC/Liquidsmooth/Carbon/Paranoid.....whatever is 4.2.2
No, only official roms are packaged like that.
You need to have RSDlite at least Version 6 or higher. Also, edit the xml file as stated here.
If your phone is up & running again you can consider going to another rom either with safestrap or by unlocking your BL, installing a recovery and flashing any ROM you like. As stated above you can only flash Stock FW using RSDLite. All other roms can only be applied with either safestrap or CWM Recovery (or similiar).
HELP-ME
FRIENDS, AFTER I TRY TO INSTALL A ROOM 4.2.2 MY PHONE NO OUT OF AP fastboot.
JA TRIED TO PUT ALL ROOMS OF MOTOROLA BUT NOT RESOLVED.
SCREEN IS BLACK AND PHONE DOES NOT NOTHING COULD HELP ME?: (