Related
Test methods need to unbrick my magic, so far I've tried one that I have not worked. If someone want to try things that I communicate them and I try.
After an upgrade of radio has been fried. I can not get into recovery, or fastboot. Even so I try to send commands and the command window stays and even restart <waiting for device> clicking to enter recovery fastboot or does nothing.
Excuse the translation but my English is very bad and I use the google translator
edugg said:
Test methods need to unbrick my magic, so far I've tried one that I have not worked. If someone want to try things that I communicate them and I try.
Click to expand...
Click to collapse
wow so much information don't know where to start!!!
hard to say..someone managed to the the phone to respond to fastboot/adb by starting up ADB..
wait for the waiting for device msg, then connect the phone to usb and turn it on.
if all method fails, bring it back to claim for warranty.
edugg said:
Test methods need to unbrick my magic, so far I've tried one that I have not worked. If someone want to try things that I communicate them and I try.
After an upgrade of radio has been fried. I can not get into recovery, or fastboot. Even so I try to send commands and the command window stays and even restart <waiting for device> clicking to enter recovery fastboot or does nothing.
Excuse the translation but my English is very bad and I use the google translator
Click to expand...
Click to collapse
What OS are you using on your computer?
zeroplace said:
What OS are you using on your computer?
Click to expand...
Click to collapse
I tested with Windows 7, Vista and XP and the same.
You know any way to flash as factory?
Will it actually turn on or does it just flash a red led when you press power?
bonesy said:
Will it actually turn on or does it just flash a red led when you press power?
Click to expand...
Click to collapse
Starts, appears the splash but only gets to that point
In that case it isnt bricked its just stuck...Bricked is when it wont turn on at all
Do you have a nandroid backup?
Have you taken the battery out and the power lead so it has no power?
i have had this problem
If you have a backup get it ready, Once you have let the phone power down totally (battery out and no lead) hold back and press power (keep holding back) this should get you into fastboot.if it doesnt unplug the lead and try again.
If thats successful.... using your nandroid files
FASTBOOT COMMANDS
fastboot erase system -w
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot flash recovery recovery.img
Sorry if you cant get this to work i have to go out and wont be back to check till tomorrow so just giving you all the info
bonesy said:
In that case it isnt bricked its just stuck...Bricked is when it wont turn on at all
Do you have a nandroid backup?
Have you taken the battery out and the power lead so it has no power?
i have had this problem
If you have a backup get it ready, Once you have let the phone power down totally (battery out and no lead) hold back and press power (keep holding back) this should get you into fastboot.if it doesnt unplug the lead and try again.
If thats successful.... using your nandroid files
FASTBOOT COMMANDS
fastboot erase system -w
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot flash recovery recovery.img
Sorry if you cant get this to work i have to go out and wont be back to check till tomorrow so just giving you all the info
Click to expand...
Click to collapse
I have tried many times to do this and nothing ever stays <waiting for device> and does nothing
Phone is not bricked, so this shouldnt be a problem.
If you cant get into fastboot with current setups, then use another recovery image and a custom rom.
(all that stuff is on SD-card.. its not that hard)
Update SDK.
daihiep said:
Phone is not bricked, so this shouldnt be a problem.
If you cant get into fastboot with current setups, then use another recovery image and a custom rom.
(all that stuff is on SD-card.. its not that hard)
Update SDK.
Click to expand...
Click to collapse
Great! And how should the recovery image and custom rom be put into the Magic? Sledgehammer?
The problem that almost everyone seems to not understand is that it's impossible to access fastboot, adb or any other (known) means.
The magic will hang at the first splashscreen no matter which buttons are pushed during power up. If the track ball is pressed during power on, the led lights up blue (still hanging at first splash). All other combos of buttons during power on makes no difference at all.
I have tried keeping fastboot waiting while power cycling the device (as explained in another thread), but there are no reaction. I have tried in xp, vista and linux.
I have also tried with a gold card, but since the phone seems unable to get any further than the first splash, this will not work.
So unless someone has a _NEW_ method to actually enter fastboot/ADB mode, these devices are BRICKED!
People have been discussing what the criteria for calling a phone a brick, but as far as I have care my Magic can only function as a paper weight and can therefore be called bricked.
Help
I have the same problem , the fastboot can not acces, i stay at the vodafone logo.
Any ideas?
HHHHHHHHHHHEEEEEEEEEEEELLLLLLLLLLPPPPPPPPPP.
frankiboy1 said:
Great! And how should the recovery image and custom rom be put into the Magic? Sledgehammer?
Click to expand...
Click to collapse
take out the sd card, put it in a usb adaptor and copy them over.
Also search for a thread "how i unbricked my phone"
frankiboy1 said:
Great! And how should the recovery image and custom rom be put into the Magic? Sledgehammer?
The problem that almost everyone seems to not understand is that it's impossible to access fastboot, adb or any other (known) means.
Click to expand...
Click to collapse
Think before answering.
Btw, question answered by htcmagic.
daihiep said:
Think before answering.
Btw, question answered by htcmagic.
Click to expand...
Click to collapse
I repeat: The problem that almost everyone seems to not understand is that it's impossible to access fastboot, adb or any other (known) means.
Having a recovery image and a custom rom on the SD card is useless if you are not able to get the phone accessing those files.
I have tried the "how I unbricked my phone" method (like I wrote in my first post) without any success. If you read the whole "how I unbricked my phone" thread you can see that there are several guys that did not have success with this method.
I have done a lot of thinking.... and searching...
Thanks
http://forum.xda-developers.com/showthread.php?t=571457 try there
Wrong HBOOT = real brick
Guys,
With a wrong HBOOT (what happend to me), the phone is a real brick...
And they refused to repair it... I bought a new phone. But I keep the old one in case someone break his screen. Then I can get the mobo.
just curious.
superkikim said:
Guys,
With a wrong HBOOT (what happend to me), the phone is a real brick...
And they refused to repair it... I bought a new phone. But I keep the old one in case someone break his screen. Then I can get the mobo.
Click to expand...
Click to collapse
How did you brick it?
Btw, have you tried to run any RUU update?
At least singapore one.
I bricked my xoom trying to fix the uastring. For some reason cw doesnt recognize my sd card so i cant just reflash, ive tried it with a different sdcard so it must be something with cw.. anyway, how should i proceed from this point?
Adb push the old framework-res.apk back to system/framework. If you didn't back it up download a rom extract the file then push it.
Oh and to edit the framework-res.apk i had to replace the res folder and the resources.xx file then it worked.
Sent from my Xoom using XDA Premium App
thanks for the help, but that was like speaking greek to my...lol seeriously, i know just enough to get myself into troulble... is there a step by step anywhere?
Try this
http://www.lmgtfy.com/?q=xoom+cwm+not+recognized+sd
Moved to QA since this is a Question.
wardo5757 said:
thanks for the help, but that was like speaking greek to my...lol seeriously, i know just enough to get myself into troulble... is there a step by step anywhere?
Click to expand...
Click to collapse
OK, you unfortunately updated your recovery to the dreaded 4.0.0.x in CWM and it doesn't see your sd card. You need to install a good version of the recovery (specifically 3.2.0.0) that does read it. Are you stuck at the dual core screen, or can you get into any recovery? You sound like you know enough to get out of this jam since you rooted. Now that you know what the problem is, I'm sure you can resolve it. Xooms are actually pretty hard to really brick. I've gotten myself into and out of some very hairy situations.
Thanks for all the help! Unfortunately I'm at my inlaws tonight, when I get back home tomorrow I will use your guidance...... Yes, I am stuck at the dual core screen but I can still get into cwm. Thanks again, I can't wait to get it fixed, I am having to type this on my wife's iPad, yes, it's killing me!
wardo5757 said:
Thanks for all the help! Unfortunately I'm at my inlaws tonight, when I get back home tomorrow I will use your guidance...... Yes, I am stuck at the dual core screen but I can still get into cwm. Thanks again, I can't wait to get it fixed, I am having to type this on my wife's iPad, yes, it's killing me!
Click to expand...
Click to collapse
Let us know if and how you get it worked out.
****............. i did it this time guys... i now have " failed to boot LNX 0x0004
starting RSD mode 2" is it done?
i think im going to try the SBF, what do you guys think?
wardo5757 said:
****............. i did it this time guys... i now have " failed to boot LNX 0x0004
starting RSD mode 2" is it done?
Click to expand...
Click to collapse
Boot your xoom into fastboot mode manually. To do this hold the volume up and power button until the xoom turns off. As soon as you see the moto logo start tapping the volume down button. in the upper left corner you should get options, choose fastboot. In Fastboot mode try running "fastboot devices" from command promt on PC first to see if the xoom is recognized. If it is, you can be saved. From here try "fastboot oem unlock", you should then see intructions to follow on the xoom screen. If when you reboot you get the same issue, get into fastboot again and flash the original stock moto images. Good luck.
jase33 said:
Boot your xoom into fastboot mode manually. To do this hold the volume up and power button until the xoom turns off. As soon as you see the moto logo start tapping the volume down button. in the upper left corner you should get options, choose fastboot. In Fastboot mode try running "fastboot devices" from command promt on PC first to see if the xoom is recognized. If it is, you can be saved. From here try "fastboot oem unlock", you should then see intructions to follow on the xoom screen. If when you reboot you get the same issue, get into fastboot again and flash the original stock moto images. Good luck.
Click to expand...
Click to collapse
it will not go into options when doing that sequence, goes to that error code. sbf using rsd lite didnt work either....
forget that last post! ok, i got it into "fastboot protocal support" what next?
for some reason, the comand promt in sdk isnt accepting any keys. i have no idea whats going on.....
just a progress update, by using the one click root method i was able to get back into recovery, unfortunately its the 4.0.0.4, but im getting closer. now if i can figure out whats going on the sdk, TE will not take any input
ok,ive gotten sdk sorted out. i have been using this guide (starting at step 4), file on my pc are in the right place but i cannot seem to get the proper cwm flashed. is this the right command, except for the file location? I put the .img file in the root of c:
SHE"S BACK!!! I was having probleams flashing becuse the c: in that command line psoted was in the worng place. once i got flashed back to 3.2 cwm it was a breeze ofcourse.
Thanks for all the help guys, I know its a pain helping a dumb ass,,, thanks again!
Hello, i recently bought a xoom (wifi only) and now im in a quite frustrating situation.
When i got it first i flashed CWM recovery and rooted it successfully, it worked all fine for a few days.
yesterday i left the xoom on charger over night and today morning it was stuck on the red M logo saying "Dual Core Technology".
well, my situation is like:
- i can restart the xoom using power + volume up, but every time it stucks on the M logo again
- i can boot into RSD with volume up while starting
- i can boot into fastboot with volume down while starting
- i can NOT boot into recovery, when i try it gets stuck at "Reading ODM fuse: 1"
i reflashed the original ROM from MOTODEV, but the device still behaves the same like before..
normal boot gets stuck at the M logo, recovery gets stuck on Reading ODM fuse: 1, just fastboot working fine (unlocking & flashing works fine)
i also searched for similar problems on the forums, but any promising solution links to filesonic links wich are not working/down
any ideas what i can do now? any help is appreciated
thanks
unlock the bootloader and flash Rogue Recovery v1.3.0
then try to enter cwm
are u on stock? or customrom? and have u tried to lock the bootloader using a customrom? cauz locking the bootloader with customrom = not good
hi, thanks for your reply.
im on stock rom and my bootloader is unlocked. i did relock the bootloader once, but only after flashing the original ROM from MOTODEV to my device, now it is unlocked again.
i first flashed the CWM 3.2.0.0 wich is available as .img via fastboot, but it does not start (Stuck on "Reading ODM Fuse: 1").
now i flashed the recovery.img inside of Rogue Recovery 1.3.0 (since i read in the corresponding thread that it works also this way), but again: Stuck on "Reading ODM Fuse: 1"
Maybe u r 2 quick? Turn on your xoom - if u see the M wait 3 sec then press vol down and then vol up
But as i said wait 3 secs - if u r 2 quick it will stuck at entering recovery
okay, so you flashed a new recovery image (did you verify the images md5-sum?) and without trying to reboot into android you cannot get into recovery? That is really odd.
If so, I suspect that something has really screwed up your internal memory. You might be able to fix it using a factory cable.
Btw: after flashing the recovery image, does the xoom say that it succeeded in writing the recovery image to its memory?
There should be a command to reboot the device to recovery? A function reboot to recovery is possible on eos 1.0 maybe theres a adb or fastboot command 4 that?
llama-power said:
okay, so you flashed a new recovery image (did you verify the images md5-sum?) and without trying to reboot into android you cannot get into recovery? That is really odd.
If so, I suspect that something has really screwed up your internal memory. You might be able to fix it using a factory cable.
Btw: after flashing the recovery image, does the xoom say that it succeeded in writing the recovery image to its memory?
Click to expand...
Click to collapse
after flashing the recovery, i can read
"Flashing StorMgr partition recovery STATUS: done!" on the xoom
the recovery image is fine, and until today i was able to boot into CWM 3.2.0.0
what is the thing with the factory cable?
about the factory cable: seems to be a modified usb-cable with two terminals on the micro-usb end being connected with each other. As far as I read, it should enable you to write to the xooms memory as long as the hardware is still okay, no matter how much you f***ed up your software I haven't had to use yet, though.
@what Unholy said: sure, adb reboot recovery will boot your xoom into recovery, but only if you have a working android running and usb-debugging enabled.
Reading ODM Fuse: 1, according to my information, means that the thing is trying to boot into recovery. Why nothing else shows up: I have no clue.
here is a thread where some us-users had a similar problem. They tried to root their xoom after getting the 4g-upgrade and ended up with the red M-Logo. After some screwing around, they even managed to wreck the fastboot-mode, thus only enabling rsd access. So no help on that side.
What especially bothers me about your problem is that it just appeared on its own. Right before your xoom showed its issues, you weren't flashing anything. Just charging shouldn't cause any of this.
I am beginning to suspect a hardware failure that can naturally be only fixed by motorola. But that's only my current opinion.
If I was you, I would try downloading the files from motorola again, check their md5-sums and then flash those using fastboot using these instructions.
If that still doesn't help, there may be a way to get a .sbf file from motorola for your xoom. That is a file which can be flashed using the windows software rsd-lite, but I haven't used that in a long time and it has been reported to not work really well with the xoom.
Next, I'd research a little on the factory cable thing, but I'd be careful with that.
As a last resort, I'd send the xoom to my dealer. Unluckily, there is a way to determine if you have had your bootloader unlocked, at least as long as fastboot is still working...
About the factory cable - with that cable u can flash your xoom if nothing else is working anymore (adb or cwm)
To build a factory cable u have to tie pin 1 (+) to pin 4 on the micro usb plug
I build one but never used it and hope i will never have to
i did download the original ROM from motodev again, checked the md5, and flashed according to the tutorial posted by llama-power, but the device still wont boot neither the rom nor into recovery.
since its now on 15% battery i think i will let it run out of power and then try to boot again...
The_Revenge said:
i did download the original ROM from motodev again, checked the md5, and flashed according to the tutorial posted by llama-power, but the device still wont boot neither the rom nor into recovery.
since its now on 15% battery i think i will let it run out of power and then try to boot again...
Click to expand...
Click to collapse
does the xoom charge when connected to ac power? I know that other devices (cellphones) wouldn't charge without working os.
However, I do not think that letting the battery run low will help you. Lithium ion batteries should not be low discharged as that will most likely destroy them and lead to a massive risk of explosion upon the next charge. Because of that, devices powered by a lithium ion battery will power down before depleting the battery, the xooms mainboard itself will most likely still be supplied with some power.
If you really want to cut the power supply to the mainboard, you'll have to open the xoom (two screws) and unplug the battery (the connector is held down by another two screws) for a couple of seconds. (here is a teardown of the xoom with pictures)
by the way, if you want to track your battery status without booting android (as that would obviously not work), you can use fastboot getvar battery-status.
well my xoom actually charges when i connect it to power, and the LED also lights up, so (thinking of what you said) it seems like the os and everything still is present, just like the bootloader cant load it or something?! is there maybe any way to update the bootloader itself?
yeah, i can also check the battery status when i'm booting with power and volume up (RSD) =)
well i'm actually thinking about disconnecting the battery, but i'm a bit unsure, i will study that now..
The_Revenge said:
well my xoom actually charges when i connect it to power, and the LED also lights up, so (thinking of what you said) it seems like the os and everything still is present, just like the bootloader cant load it or something?!
Click to expand...
Click to collapse
not neccessarily. Maybe the xoom just doesn't need any software to charge the battery.
The_Revenge said:
is there maybe any way to update the bootloader itself?
Click to expand...
Click to collapse
don't know, but since fastboot works I suspect that the bootloader itself is still fine.
The_Revenge said:
well i'm actually thinking about disconnecting the battery, but i'm a bit unsure, i will study that now..
Click to expand...
Click to collapse
have fun, but I wouldn't get my hopes up too high. I still suspect some sort of a hardware failure... Also, opening the device might leave some traces (botched screws, etc) that could lead motorola to say that you messed with your xoom if you should finally decide to send it in
well thats the same i thought about opening the device..
do you know any way to dump the partitions to the pc (maybe with fastboot?)
The_Revenge said:
do you know any way to dump the partitions to the pc (maybe with fastboot?)
Click to expand...
Click to collapse
nope, not without a working recovery.
fastboot erase partition_name should be able to clear your partitions, though. Replace partition_name with boot, system, userdata, cache or recovery
http://www.xoomforums.com/forum/xoo...ery-stuck-red-m-logo-fastboot-works-help.html
apparently that user seems to have had the same problem, he says he fixed it using 1.35 Everest Bootloader (SBF).
i also had that idea some time earlier and found a thread with the SBF files here on xda, also for the wifi model, but the only links i could find to SBF files were filesonic links wich are not working ._.
i'm now up to googling for SBF files (for the wifi only model), if i cant find anything promising i'll send it back tomorrow.
btw, erasing the partitions does not help, i've already tried that
Have u done the lte update?
UnholyX said:
Have u done the lte update?
Click to expand...
Click to collapse
he's got an wifi-only model (as stated in post #1) and is from germany (at least that's what his location and flag says). LTE upgrade is neither available in germany, nor for wifi-only-xooms. So I'd say no
@OP: that sounds quite promising. .sbf-files still seem to be available on some sites, downloading one for my xoom right now, just in case that site goes down in the future...
Yes he got the wifi version like me but something must happened ,-)
I also charge my xoom and nothing happens. He got wifi version but he maybe flashed a false update or so
There r people flashing stingray instead of the wingray version etc. - just asking what happened before - thats the reason - something must happened before ;-)
it seemed promising, but i cannot find any usable sbf file
i think i'll send the unit back tomorrow
Greetings! First of all, I would like to thank anyone who takes the time to help me diagnose and resolve this issues, let alone anyone who takes the time to read this thread.
I've been having issues with my Xoom (ICS 4.0.0) for about 3 weeks now.
A brief history of the issue's occurrence:
-I unrooted the device and returned it to stock.
-Everything was fine and dandy until one day it spontaneously said something along the lines of 'Android is upgrading..', and then performed a reset.
-Since resetting, it bootloops.
The device only turns on when plugged into a charger and hard reset.
The device only turns off when allowed to boot loop for minutes and then hard reset (it simply does not reset, and just turns off).
I'm not the most technically-savvy person with android devices but here are some things I've done/noted.
When trying to use adb commands, it does not recognize the device or properly issue commands.
I've tried wiping data/clearing cache to no avail.
EDIT: I've tried fastbooting, but the bootloader will not unlock. When trying to unlock, it simply resets and then acts as though it was never unlocked.
I have no idea how to return it to a stock image. All I know is that I have a micro-SD and some spare time.
Could anyone help me understand what exactly is going on with my Xoom?
If I can provide you with any more information, please let me know.
Thanks again. (=
If it was stock and spontaneously upgraded it sounds like a bad OTA upgrade. I've been rooted from the start so never have taken an OTA upgrade...don't you need to accept it or can it just upgrade on it's own?
Anyway, can you get it into fastboot mode?
Volume up and power, then at dual core screen, press volume down...if you see something like "entering fastboot mode" you're not bricked. You do not have to re lock your bootloader. Just make sure you have downloaded the correct stock files for your Xoom model to your PC and flash it.
If you haven't done so, just google 'recovering Xoom using fastboot' and you should get some good information.
Good luck!
Remember to grab the MZ604 files if you have the Wifi only version of the Xoom.
http://developer.motorola.com/products/software/ <------ Grab the files here. The files are for the US version of the Wifi Xoom only.
Instructions to return it to stock
1) First you need the Moto Drivers - Read this thread to START you - http://forum.xda-developers.com/showthread.php?t=981578
Should have these drivers installed if you have rooted your Xoom before.
2) Make sure you have the latest SDK - adb and fastboot should be in /platform-tools -
http://developer.android.com/sdk/index.html
Should have the android SDK if you have rooted your Xoom before.
3) Place all the downloaded stock image files into the SDK Tools folder.
4) If you are booting up from scratch, you can get the Xoom in fastboot mode by doing the following. Use command prompt to perform the rest of the steps
Hold VolDown and Power button will boot unit for fastboot mode
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
If you Xoom is booted up already follow the commands below using command prompt to perform the steps
adb reboot bootloader <---- reboots the Xoom into fastboot mode.
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
As Always If This Was Helpful Hit the Thanks!
Yeah, what Mjamocha said...
okantomi said:
Yeah, what Mjamocha said...
Click to expand...
Click to collapse
LOL Thanks.
okantomi said:
Anyway, can you get it into fastboot mode?
Click to expand...
Click to collapse
Yes, I can. But so far nothing has been successful in terms of fastboot commands.
okantomi said:
You do not have to re lock your bootloader. Just make sure you have downloaded the correct stock files for your Xoom model to your PC and flash it.
Click to expand...
Click to collapse
When I try to execute fastboot commands such as 'fastboot flash boot boot.img'.. it says the following:
Device still locked. Device must be unlocked first. Failed to process command error(0x8)
Whenever I try to unlock the bootloader, it appears to be successful at first and then the device reboots. But it just reboots to a bootloop, and the bootloader still says its locked. Perhaps I made a mistake in communication. The bootloader is currently locked and will not unlock, as just described.
When I try to unlock it and it reboots, even if I access the fastboot menu right away, it still says the device is still locked.
Thoughts?
Can you get into recovery? With the Xoom off (to make sure it's really off, hold volume up + power for a few seconds), hit the power button and when you see the M logo, wait a very brief moment (like a fraction of a second) and hit the volume down button. When it says "recovery" on the top left, hit the volume up. If you can get in there, either restore a nandroid (if you have one) or do a factory reset.
slacka-vt said:
Can you get into recovery? With the Xoom off (to make sure it's really off, hold volume up + power for a few seconds), hit the power button and when you see the M logo, wait a very brief moment (like a fraction of a second) and hit the volume down button. When it says "recovery" on the top left, hit the volume up. If you can get in there, either restore a nandroid (if you have one) or do a factory reset.
Click to expand...
Click to collapse
Yes, I can get into android recovery. However, within a second of switching into recovery mode, the robot falls down and there appears to be a red triangle caution sign containing an exclamation point.
When trying to do a factory reset, it says all data is wiped (as normal). Upon rebooting, it continues to bootloop. So essentially the factory reset and cache clear options in the Android Recovery menu do not produce the expected results.
Pretty odd. I didn't mess with the Xoom at all prior to this issue.
Try flashing just a recovery img to hopefully get your recovery working again. I think you can flash a custom recovery even if the bootloader is locked (i could be wrong but worth a shot) I attached the Rogue "recovery-rogue-1.3.0.img". Try a "fastboot flash recovery recovery-rogue-1.3.0.img"
EDIT: Sorry, I guess you can't flash a custom recovery with a locked bootloader.
slacka-vt said:
Try flashing just a recovery img to hopefully get your recovery working again. I think you can flash a custom recovery even if the bootloader is locked (i could be wrong but worth a shot) I attached the Rogue "recovery-rogue-1.3.0.img". Try a "fastboot flash recovery recovery-rogue-1.3.0.img"
EDIT: Sorry, I guess you can't flash a custom recovery with a locked bootloader.
Click to expand...
Click to collapse
Yeah, just tried it to no avail. Thanks so much for your help anyway. (=
I'm not sure what to do now.
I would keep trying to unlock it using different USB cables and different USB ports on your computer. I've had unlocks fail a bunch of times and for some reason, it was because of a $hity USB cable and/or a bad port on my computer.
slacka-vt said:
I would keep trying to unlock it using different USB cables and different USB ports on your computer. I've had unlocks fail a bunch of times and for some reason, it was because of a $hity USB cable and/or a bad port on my computer.
Click to expand...
Click to collapse
I hear ya. I've tried 2 different cords and 3 different computers. I'm using a Mac (10.6.8) right now, but have used 2 PCs (Vista + 7).
Out of curiosity, when you tried to flash the custom recovery, did you get the same "device still locked" error or did it appear to flash but then recovery failed?
slacka-vt said:
Out of curiosity, when you tried to flash the custom recovery, did you get the same "device still locked" error or did it appear to flash but then recovery failed?
Click to expand...
Click to collapse
I got the 'device still locked' error. Weird, huh?
How about trying to lock it again even though it says it's locked -maybe it's stuck in an "in-between state"? Try a "fastboot oem lock" and if it finishes then try a "fastboot oem unlock". I know, I'm grabbing at straws here. I thought I bricked my Xoom last week. All I did was an "adb reboot bootloader" and the device went to a black screen. Volume Up + Power did nothing. I ended up buying a T5 (Torx 5) bit at the store, removed the back cover and disconnected the battery for 30 seconds using a piece of paper to separate the contacts. The Xoom booted right up after that.
slacka-vt said:
How about trying to lock it again even though it says it's locked -maybe it's stuck in an "in-between state"? Try a "fastboot oem lock" and if it finishes then try a "fastboot oem unlock". I know, I'm grabbing at straws here. I thought I bricked my Xoom last week. All I did was an "adb reboot bootloader" and the device went to a black screen. Volume Up + Power did nothing. I ended up buying a T5 (Torx 5) bit at the store, removed the back cover and disconnected the battery for 30 seconds using a piece of paper to separate the contacts. The Xoom booted right up after that.
Click to expand...
Click to collapse
Yeah I tried that. Won't lock or unlock successfully. Locking produces no difference, and unlocking produces the same 'device still locked' error. This is getting out of hand! Thanks so much for your advice. You think I should open it up?
I hate to be so persistently annoying about this, but could anyone possibly suggest a method of working around the locked bootloader?
Is there anything I can do with an SD card to remedy the device's stubborn foolery?
I think you should give it a try, I have bricked my xoom a few times and have always been able to flash the stock imagine to recover. You really have nothing to lose by pulling the battery pin just be careful.
Sent from my Xoom using xda premium
I don't know if I'm technically-equipped enough to do that. )=
Sounds easy, but I imagine it would be rather easy to screw something up? Essentially what I should do is unseat the battery, right?
cherlamperter said:
I don't know if I'm technically-equipped enough to do that. )=
Sounds easy, but I imagine it would be rather easy to screw something up? Essentially what I should do is unseat the battery, right?
Click to expand...
Click to collapse
I have looking for a utube how to guide but no luck, I just might make one for you so you will know what to expect. Give me a few and I will get back to ya.
Sent from my Xoom using xda premium
So I think I might have a bricked xoom. Its the 3G/WIFI version. I tried to downgrade it to WIFI only version and got stuck from there.
Now the Xoom is stuck at the red M when booted.
If you go through recovery it says: "Reading ODM fuse:1."
If you go through fastboot it says: "Starting fastboot protocol support."
RSD: battery level
The Xoom freezes after each option is selected and that's about as much action as I can get from it. So am I screwed? If not, what can I do?
Is it recognised via ADB?
Send to service center and they should have special tool to recover it!
re-flashing Rogue Recovery
mikeay93 said:
So I think I might have a bricked xoom. Its the 3G/WIFI version. I tried to downgrade it to WIFI only version and got stuck from there.
Now the Xoom is stuck at the red M when booted.
If you go through recovery it says: "Reading ODM fuse:1."
If you go through fastboot it says: "Starting fastboot protocol support."
RSD: battery level
The Xoom freezes after each option is selected and that's about as much action as I can get from it. So am I screwed? If not, what can I do?
Click to expand...
Click to collapse
If you are getting "Starting fastboot protocol support" then you should be able to then plug in the USB cable and use ADB. I would then try re-flashing Rogue Recovery, then with a working recovery kernel you can flash the correct ROM.
Grege50 said:
If you are getting "Starting fastboot protocol support" then you should be able to then plug in the USB cable and use ADB. I would then try re-flashing Rogue Recovery, then with a working recovery kernel you can flash the correct ROM.
Click to expand...
Click to collapse
Thanks for the help guys,
So I tried re-flashing the Rogue Recovery, and other kernels, but the Xoom says,
"Device still locked. Device must be unlocked first.
Failed to process command error (0x8)"
I'll be some research too and let you guys know what happens
mikeay93 said:
So I think I might have a bricked xoom. Its the 3G/WIFI version. I tried to downgrade it to WIFI only version and got stuck from there.
Now the Xoom is stuck at the red M when booted.
If you go through recovery it says: "Reading ODM fuse:1."
If you go through fastboot it says: "Starting fastboot protocol support."
RSD: battery level
The Xoom freezes after each option is selected and that's about as much action as I can get from it. So am I screwed? If not, what can I do?
Click to expand...
Click to collapse
could you be more specific with your device details before the flash, during the flash, after the flash?
Before the flash; model mz???, ICS/JB, Rooted, custom rom, unlocked bootloader, custom recovery.....etc.
During the flash: you said that you downgraded to the WiFi version......which version? Did you fast boot the image files? Did you use RSD lite and sbf image? Which image and rsd lite image?
After; in detail explain what you did after the flash up til now.
I know that this is a lot but it will help.
From first guess it sounds like your bootloader is locked or you downgraded your boot loader to an earlier version prior to the latest ver#1050 when you downgraded your device to a WiFi version. This would also keep your device in the condition you describe or worse. I would try to unlock your boot loader.....if that fails then you need to find the latest 3G image version sbf (if there is one) using rsd lite. If that is not an option then try to flash with RSD lite the 604 combo sbf for the mz604. I had to flash it a couple times plus do a manual factory restore......good luck.
Galaxy Nexus (SCH-I515 VZW/LTE) using Tapa2
cdexsw said:
could you be more specific with your device details before the flash, during the flash, after the flash?
Before the flash; model mz???, ICS/JB, Rooted, custom rom, unlocked bootloader, custom recovery.....etc.
During the flash: you said that you downgraded to the WiFi version......which version? Did you fast boot the image files? Did you use RSD lite and sbf image? Which image and rsd lite image?
After; in detail explain what you did after the flash up til now.
I know that this is a lot but it will help.
From first guess it sounds like your bootloader is locked or you downgraded your boot loader to an earlier version prior to the latest ver#1050 when you downgraded your device to a WiFi version. This would also keep your device in the condition you describe or worse. I would try to unlock your boot loader.....if that fails then you need to find the latest 3G image version sbf (if there is one) using rsd lite. If that is not an option then try to flash with RSD lite the 604 combo sbf for the mz604. I had to flash it a couple times plus do a manual factory restore......good luck.
Galaxy Nexus (SCH-I515 VZW/LTE) using Tapa2
Click to expand...
Click to collapse
Ok its a MZ600 Xoom 3G+WiFi, rooted, don't know the rom but I can find out.
I don't know too much about the details as to how this problem occurred, but if it is absolutely necessary to know, I can find out.
I can successfully flash all of these images using fastboot. But after I flash all images, clear cache, lock oem, and restart it leads me to the motorola logo and a message that says "Failed to boot LNX 0x0004; Starting RSD mode 2; (battery level)." I tried flashing this sbf file but it gave an error reading "Failed flashing process". (My device is recognizable in RSD) But it's not a recognized device when I run adb devices
So I can scroll through RSD, Fastboot, and Android Recovery fine, but I've tried several images to flash yet I still get stuck on the "M" .
mikeay93 said:
Ok its a MZ600 Xoom 3G+WiFi, rooted, don't know the rom but I can find out.
I don't know too much about the details as to how this problem occurred, but if it is absolutely necessary to know, I can find out.
I can successfully flash all of these images using fastboot. But after I flash all images, clear cache, lock oem, and restart it leads me to the motorola logo and a message that says "Failed to boot LNX 0x0004; Starting RSD mode 2; (battery level)." I tried flashing this sbf file but it gave an error reading "Failed flashing process". (My device is recognizable in RSD) But it's not a recognized device when I run adb devices
So I can scroll through RSD, Fastboot, and Android Recovery fine, but I've tried several images to flash yet I still get stuck on the "M" .
Click to expand...
Click to collapse
the problem is when you relocked the bootloader. It was a "bad lock". You need to UNLOCK the bootloader then the device should boot up normal......RSD will recognized your device but with a screwed up bootloader nothing will flash.......also fastboot and adb will have the same result because of this
**here is what to do**
Option#1 - Try this first
1. connect Xoom to PC with Moto USB Cable (the one shipped with Xoom if possible)
2. ADB command: fastboot reboot-bootloader
3. It will show
4. Then Press Pwr + Vup (reset xoom)
5. When Xoom go into black screen (before the Moto logo appear), press and hold volume down button. I was then successfully get into Fastboot.
In step no. 5, you must press and hold the volume down button, if you release the button, Xoom will reset by itself and you will again caught in the "Failed to boot LNX 0x0004" screen. If you accidentally let go the volume down button, repeat step 4 - 5, and make sure you will not let go the volume down button this time.
Then, one of your hand is holding the volume down button, use your another hand to enter an ADB command: "fastboot oem unlock", you will be able to unlock your bootloader, and xoom will reboot normally.
Yes, I understand your xoom is not working proper but this may take 5 or 6 tries......keep at it. This has had many successes.
-------------
Option#2 - If option#1 does not work
Follow these steps to modify your USB cable to a programming cable
http://forum.xda-developers.com/showthread.php?t=1108518&page=2
Here is a tutorial if you decided to go this route
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
This too works......but make sure your contacts/wires do not touch other wise you zoom may die when everything gets plugged making the cable is a pain but it's a life saver.
------------
Those are your ONLY options for recovering from this brick.
NOTE - DO NOT RELOCK BOOTLOADER WHEN CONVERTING FROM 3G TO WIFI ONLY. I recommend never touching it after it is unlocked, ever.
The only time locking the bootloader will work is only when you return the device to its original factory condition..........and the only time. Best advice.......after you unlock the bootloader never touch it again.
I hope this helps. Good luck.
Sent from my Xoom using Tapatalk 2
Oh ya I forgot to mention that I've been able to unlock the device, but the problems are still there.
Cdexsw, I'll use the second method as a last resort.
mikeay93 said:
Oh ya I forgot to mention that I've been able to unlock the device, but the problems are still there.
Cdexsw, I'll use the second method as a last resort.
Click to expand...
Click to collapse
Do you know what version of the bootloader you currently have on your Xoom?
Galaxy Nexus (SCH-I515 VZW/LTE) using Tapa2
I've been swamped with work and finals guys I didn't forget about this. As soon as school finishes I'll put more time into trying to find a solution in case anyone is going through the same thing. Thanks to anyone trying to help out.
Hey guys I'm back. My memory is a little rusty on the topic so let me just tell you where I'm at.
I will be convinced that I have a messed up bootloader once someone explains me this... the Xoom model number on the box says MZ600. Using RSD lite, I have several sbf files downloaded: MZ600, MZ602, MX604. Running the program under administrator, I can only start RSD with the MZ604 sbfs loaded. But once again, my model is a MZ600 yet it will not load that sbf file. Can someone explain to me what is going on here?
Cdexsw, as for the bootloader I have no idea which one is installed.
The error I get from RSD when I flash the mz600 is "Failed flashing process. Unable to retrieve installation values from INI file. (0x7029); phone connected"
The only difference that sets the 600 apart from the 604 is is 3G chip in the 600. They are basically the same units other than that. You can flash a 604 SBF on a 600 with no issues, hence the term "Gedified" my xoom which means converted a 3G/4G to a WiFi only Google Experience Device.
The bootloader issue......not sure on this. Don't flash any bootloader older than 1050 (I think). And stay away from 601, 602 and other SBF files. Use only 600 or 604.
Have you tried fastboot to flash ALL the images instead of the sbf/rsd? There is a thread in this forum containing all of the stick images from HC, ICS, and JB (wifi only). Start with the images for 600, if no work then try the 604 images.
Here is the link for the images
http://forum.xda-developers.com/showthread.php?t=1049485
Oh and if your bootloader is unlocked, DO NOT LOCK IT!!! Skip any step that says to lock it......again, skip ANY step that says to lock it.....trust me......I am saving you a potential headache since you already have enough issues.
Sent from my Galaxy Nexus using Tapatalk 2
cdexsw said:
The only difference that sets the 600 apart from the 604 is is 3G chip in the 600. They are basically the same units other than that. You can flash a 604 SBF on a 600 with no issues, hence the term "Gedified" my xoom which means converted a 3G/4G to a WiFi only Google Experience Device.
The bootloader issue......not sure on this. Don't flash any bootloader older than 1050 (I think). And stay away from 601, 602 and other SBF files. Use only 600 or 604.
Have you tried fastboot to flash ALL the images instead of the sbf/rsd? There is a thread in this forum containing all of the stick images from HC, ICS, and JB (wifi only). Start with the images for 600, if no work then try the 604 images.
Here is the link for the images
http://forum.xda-developers.com/showthread.php?t=1049485
Oh and if your bootloader is unlocked, DO NOT LOCK IT!!! Skip any step that says to lock it......again, skip ANY step that says to lock it.....trust me......I am saving you a potential headache since you already have enough issues.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I tried flashing various boot, system, recovery, and userdata files and they all successfully get flashed through. But on reboot, I still get stuck on the Motorola logo. I tried several 604 images, because those are the only ones that actually start in RSD, but those fail as well. I tried finding out my bootloader information with the command fastboot oem get_unlock_data but the command fails and gives an error on the xoom saying Failed to process command error(0x120000)
So I'm really stuck on what to do next...
Where did you buy it
Reading the posts, you have not indicated which country you are in or where the Xoom came from.
I live in Australia and have a European model MZ601 Xoom purchased in Hong Kong. All of that makes a difference in which ROMs I use and why.
Grege50 said:
Reading the posts, you have not indicated which country you are in or where the Xoom came from.
I live in Australia and have a European model MZ601 Xoom purchased in Hong Kong. All of that makes a difference in which ROMs I use and why.
Click to expand...
Click to collapse
U.S.A....
mikeay93 said:
U.S.A....
Click to expand...
Click to collapse
OK, I will butt out. My only other thought is going into recovery and using the format option to re-format the internal partitions, then re-flash.
Read this thread
http://forum.xda-developers.com/showthread.php?t=2069809