First,
I really want to thank everyone for their support in this forum. Everyone has been amazing.
I was trying to bring my MZ601 back to stock yesterday. Something bad happened during fastboot and asked me if I wanted to unlock my device. Then the screen locked up and didnt do anything. I rebooted the device and now it gets stuck in a boot loop with the EOS symbol (last rom I installed). When I enter recovery there is nothing there, all of my data is gone.
Worse the device is not recognized on my computer nor can it be found in adb fastboot. I have updated motorola drivers, but I think the device never gets past a certain point in order to be found.
Can somebody please help me.
Thanks,
Pretty impossible to brick XOOM's but i'll ask the basics. Can you get into recovery from a cold boot? Can you get into fastboot from a cold boot?
By the sounds of it you've just corrupted your rom or tried to re-unlock the device which would cause the entire sdcard partition to be erased.
Boot XOOM into Recovery, Fastboot, or RSD mode
So you need to get into Recovery to backup your XOOM (you do nandroid don't you?). Or perhaps you were working on creating new levels of awesome and something happend and you find yourself staring at the Motorola Dual Core boot screen with your XOOM refusing to boot any further. Fear not, you are only a few clicks away from finding your way back into recovery or fastboot goodness.
Turn your XOOM off
Press Power to turn your XOOM back on
When the Motorola Dual Core boot screen appears tap Volume Down repeatedly until "Android Recovery" is displayed
Press Volume Up to enter Recovery
You can also choose from Fastboot protocol support and RSD mode by using the same method but instead selecting their respective menu prompts.
Note:
If your XOOM is caught in bootloops or you find yourself stuck in RSD mode or Fastboot Protocol support you can hardware reboot your XOOM by pressing and holding Volume Up + Power until the tablet reboots (usually a few seconds but could be longer).
demunted said:
Pretty impossible to brick XOOM's but i'll ask the basics. Can you get into recovery from a cold boot? Can you get into fastboot from a cold boot?
By the sounds of it you've just corrupted your rom or tried to re-unlock the device which would cause the entire sdcard partition to be erased.
Boot XOOM into Recovery, Fastboot, or RSD mode
So you need to get into Recovery to backup your XOOM (you do nandroid don't you?). Or perhaps you were working on creating new levels of awesome and something happend and you find yourself staring at the Motorola Dual Core boot screen with your XOOM refusing to boot any further. Fear not, you are only a few clicks away from finding your way back into recovery or fastboot goodness.
Turn your XOOM off
Press Power to turn your XOOM back on
When the Motorola Dual Core boot screen appears tap Volume Down repeatedly until "Android Recovery" is displayed
Press Volume Up to enter Recovery
You can also choose from Fastboot protocol support and RSD mode by using the same method but instead selecting their respective menu prompts.
Note:
If your XOOM is caught in bootloops or you find yourself stuck in RSD mode or Fastboot Protocol support you can hardware reboot your XOOM by pressing and holding Volume Up + Power until the tablet reboots (usually a few seconds but could be longer).
Click to expand...
Click to collapse
Hi,
Thanks for the tips. Unfortunately, it seems that I have caused the entire sd card partition to be erased. That mean when I trry to fastboot my device is not recognized. Also, i cannot add anything to my xoom through usb. I have tried to flash through the external sd card, but to no avail. What do I have to do?
What does your xoom show up as when plugged into your pc APX? Can you boot into fastboot mode. with power off press power and volume down until you see fastboot.
dfib1 said:
What does your xoom show up as when plugged into your pc APX? Can you boot into fastboot mode. with power off press power and volume down until you see fastboot.
Click to expand...
Click to collapse
Hi thanks for the reply to my message.
Unfortunately I cannot find my device when it is plugged into my computer (PC). It does not show up on my computer nor in the device manager. I can start the fastboot protocol on my device by rebooting, but I also cannot find my device in ADB.
Thanks for the reply, but I am still very stuck.
are you sure your device is in fastboot ? did you reinstall the drivers, try with another usb cable, adb shoud see the device after the drivers were installed correctly ...
Sent from my MZ601 using xda app-developers app
ndanl said:
are you sure your device is in fastboot ? did you reinstall the drivers, try with another usb cable, adb shoud see the device after the drivers were installed correctly ...
Sent from my MZ601 using xda app-developers app
Click to expand...
Click to collapse
I did everything I have done before. I have setup android sdk, java, and motorola drivers on two different PCs. Both fail to find my device when i type ADB devices nor does ADB reboot bootloader work. I tried the different cable, but that also did not work.
Hi,
I see that your problem is quite hard, try doing this:
1 - Force your tablet to shut down (vol+ + Power)
2 - Turn on while holding the vol- button
3 - Keep pressing vol-
4 - Plug on your PC and try fastboot devices, adb won't work!
5 - If 4 didn't work, keep trying until it does
6 - Install a Stock ROM (so you will solve your problems)
If the above don't work, contact me via PM, so we can talk easily (maybe GTalk or something like this). Good Luck
~XxLordxX
"This Story Ends Where It Began" - Octavarium (Dream Theater)
XxLordxX thank you!!!
I took your advice and just used fastboot. Then I flashed the stock rom I wanted to use. My xoom is back up and running. I really appreciate the tip.
Also thank you to everyone that responded in the post, again, that is why I love coming here.
demunted said:
Pretty impossible to brick XOOM's but i'll ask the basics. Can you get into recovery from a cold boot? Can you get into fastboot from a cold boot?
By the sounds of it you've just corrupted your rom or tried to re-unlock the device which would cause the entire sdcard partition to be erased.
Boot XOOM into Recovery, Fastboot, or RSD mode
So you need to get into Recovery to backup your XOOM (you do nandroid don't you?). Or perhaps you were working on creating new levels of awesome and something happend and you find yourself staring at the Motorola Dual Core boot screen with your XOOM refusing to boot any further. Fear not, you are only a few clicks away from finding your way back into recovery or fastboot goodness.
Turn your XOOM off
Press Power to turn your XOOM back on
When the Motorola Dual Core boot screen appears tap Volume Down repeatedly until "Android Recovery" is displayed
Press Volume Up to enter Recovery
You can also choose from Fastboot protocol support and RSD mode by using the same method but instead selecting their respective menu prompts.
Note:
If your XOOM is caught in bootloops or you find yourself stuck in RSD mode or Fastboot Protocol support you can hardware reboot your XOOM by pressing and holding Volume Up + Power until the tablet reboots (usually a few seconds but could be longer).
Click to expand...
Click to collapse
I have this problem now but I don't know what to do. Please help me out
Related
I almost had a heart attack last night doing some kernel work. This is what happened, and how I got out of it.
I had just finished compiling a kernel I was working on and was excited to flash it and give it a run. So I built the boot.img and did
Code:
adb reboot bootloader
I got into the bootloader and
Code:
fastboot flash boot [B][I]boot.zip[/I][/B]
fastboot reboot
Working quickly, a got a little sloppy. Most unfortunately, I had a boot.zip in the same folder as the boot.img so boot.zip got flashed to the boot partition. Upon reboot, I got the usual splash screen but the upper left hand corner indicated I was in "RSD Mode 3". I pressed and held Vol up + power to get into bootloader but that was unresponsive. All I could do was press Vol Down + power which brought me back to the same state. I was unable to issue fastboot commands from here as well. This is what I did to fix it.
While I was in "RSD Mode 3" I did
Code:
fastboot flash boot boot.img
Even though there was no response from the device, I pressed Vol Down + power until the screen went black. I then quickly pressed and held Vol Up + power. The device then went into the bootloader, received the queued command from fastboot, and flashed the boot.img. Finally, I did
Code:
fastboot reboot
and was back in the game.
Guys, I think the moral of the story is to slow down and be careful with fastboot. You can bet i'll be a little more careful
good post I'm sure this will help devs in the future
way to stay calm under pressure lol. good info.
Small world, I used to live in Fontana for 25 years and moved to NY couple of years ago Oh and thanks for the tip
Ran into this today, i had a similar, but different experience..hope this helps
Once i got into the RSD 3 mode, fastboot commands were basically dead...all i would get was <waiting for device>...
in order to get out, i had to hold BOTH VOL+ and VOL- and Power at the same time, then as soon as the screen turned off, I had to press VOL- and power at the same time to get to a 'regular' looking boot screen. I saw regular because there was no text at the top ofthe screen; however fastboot commands would work here. Because i FUBAR'd a kernel install, i just did
fastboot flash boot boot.img
fastboot reboot
and voila...it was alive again
a bit scary though
Ok, so I definitely know the heart attack feeling, and hopefully someone here can help me out. I got my Xoom today(wifi), and went looking for a root. I found a link to a root here that -said- it worked for both 3g and wifi models(found out later that it doesn't, obviously). So, I flashed the boot image, and came up with the RSD message. At that point all fastboot and adb capability was lost, and I can't seem to get it back.
Here's what happens with the following button combo's:
Hold Power+VolUp and release on screen-black: Motorola splash screen(dual core etc) with no text in corner
Hold Power+VolUp until after the splash comes up: splash with "Starting RSD protocol support 3"
Hold Power+VolUp and then hold VolDown immediatedly afterward: Splash screen with "Starting Fastboot protocol support."
Hold Power+VolUp and then VolDown after waiting a second: Splash screen with NvFlash/RSD/Fastboot menu
Hold Power+VolUp and then press VolUp again: Splash with "Starting RSD protocol support 3"
If I choose Fastboot from the menu, it just sits at the "starting fastboot protocol support".
If I choose RSD, it gives me the "starting RSD protocol support 3"
If I choose NvFlash, it says "entering nvFlash (something) and the screen immediately goes black and the notification led comes on (sits there until reboot)
No other button combinations seem to do anything. Holding Power+VolDown doesn't do anything from any mode, and Power+VolUp+VolDown acts just like Power+VolUp.
In any mode, I can't issue fastboot or adb commands. Fastboot simply says <waiting for device> for anything. I tried the advice above, to queue up a "good" boot.img (from here at xda), but it doesn't recognize it on a reboot from/to any mode I can get to. I've tried each about 20-30 times now, and I'm about ready to test the thing's shatter-resistance with my fist, so any help here would be -greatly- appreciated.
Quick update to previous post: Resolved!!
My advice? If you get stuck unable to fastboot or adb in linux, try it in windows. I hadn't booted into win for over a year, so it never occured to me until I saw someone mention it in the Tiamat thread. Even a fresh JDK/SDK install in Ubuntu didn't work for me. I didn't have any tools or SDK's installed in my winXP partition, but after a quick install, it worked first time, so now I'm the happy owner of a rooted Wifi Xoom with SD card.
Once again, the XDA forum saves the day. I love this place.
I recommend everyone keep a backup copy of their system.img around just in case too. I was going nuts after messing with my framework-res.apk file to get SMS working (for the verizon web account activiation message). I used root explorer, and BAM! crash, crash, FC, FC, then stuck at the moto logo at boot. I couldnt get it back with just a boot.img flash. I went for broke and found a post of the HI66 system.img. it was HUGE, dont know if thats what I needed. but flashed that and I was back in business as nothing else was working and couldnt get ADB to take to push the old framework-res.apk.
I have a similar issue. I have tried for over three hours now to understand why I cannot reboot into fastboot. It seems lika I have lost both fastboot and NVflash. Only RSD mode and a logo screen without text. Can't shut it down with powerbutton or factory reset. I tried to root it with a 3g boot.img whitch was terribly wrong on a wifi-only xoom and I'm now trying to flash a stock wifi boot.img. It just sits there on the M dual core screen.
What can I do from RSD mode 3?
EDIT: I have a feeling that it has freezed on that logo screen. I want to try a hard reset and the only way for me is to try to first shut it down then power it on again. Don't know if it helps but it is silly to be unable to stop it. How can I shut it down?
I've tried all the suggestions above with no luck
Will try a windows machines tonight to see if that will help, but I fear I will need to send my Xoom back to mfg for rework
may seem a stupid suggestion but what if you let the battery go dead. it will turn off. Then connect to power supply and do a fast boot restart, holding power button and vol down.
Just a thought!
I will try but I think I already tried that. It seems like boot and recovery is dead. I tried to flash the 3g .sbf file today. Thought that an already bricked tab couldn't be more bricked and perhaps it would restore the recovery or boot but RSD Lite couldn't do it. It's unvisible for a computer. I've tried both win7 and my Arch Linux box. The device is dead. Hopefully they wont have to replace the motherboard. I'm sending it for repair on Monday.
mines bricked also says
failed image lnx 0x0002
starting rsd mode 2
i can get it in the fastboot protocol mode with the - button and power but cmd window says waiting on device. my started after i did an fastboot oem lock with a bad kernel.
dogma444 said:
mines bricked also says
failed image lnx 0x0002
starting rsd mode 2
i can get it in the fastboot protocol mode with the - button and power but cmd window says waiting on device. my started after i did an fastboot oem lock with a bad kernel.
Click to expand...
Click to collapse
iirc the Failed Image lnx 0x0002 is due to locking the boot loader with custom stuff.
Unplug xoom usb
boot into fastboot
plug in xoom usb
fastboot oem unlock
orionshock said:
iirc the Failed Image lnx 0x0002 is due to locking the boot loader with custom stuff.
Unplug xoom usb
boot into fastboot
plug in xoom usb
fastboot oem unlock
Click to expand...
Click to collapse
Man that just sound to easy to work. ADB has no clue the device is.....wel, a device! Its like my xoom de-evolutionized to a primitive state and is suffering from tourrets. Anyway command typed in adb gives you back < waiting for device >. I've tried just about all the techniques here on the forums. And the people who claim to have been brought back to life are not victims of this "RSD mode 2" Im pretty sure this is like a failsafe if you blow up the original bootloader, 3. IDK though, pretty sure they are going to require some hardware replacements. Im not sure people are recognizing the degree of our bricks. These are what appear to be real BRICKS. no "soft" ness up in here. straight up cement
http://forum.xda-developers.com/showthread.php?t=1041192
adb wait-for-device && adb reboot recovery
tried this command and seemed pretty slick but, still nothing
Same thing here, was there any solution?
Give this a try:
http://forum.xda-developers.com/showthread.php?t=1079784
Please, I have same problem, but I can just reset it by pressing and holding Vol Up + Power On. When I press Vol Down + Power Down, nothing happens. If I press Vol Down when it restarts, it doesn't show me the message but shows the Motorola Dual Core logo and stops. Even in this situation I can't comunicate via usb. Now it just turn off when the battery is totally low.
I CAN boot into fastboot mode and issue fastboot commands from CMD. apparently mine is booting into RMD 3 mode or whatever it's called. when I boot normally (just hold down power button, I get the moto dual-core screen, and then it boots into the Clockwork Recovery Mod... PLEASE HELP
Hi. I was on #xoom at freenode earlier and I got some help, but unfortunately no solution. (thank you Kas, EbonyGhost, Pyrator and the others)
I flashed the recovery here:
http://forum.xda-developers.com/showthread.php?t=1074979
I flashed... THE ZIP!!
The flash went well, then the device rebooted and showed "Starting RSD mode 3"
I have only 2 screens:
- with VolUp + power = dual core techno + "Starting RSD mode 3"
- with VolUp + power then immediately VolDown = only the dual core tech logo, no text
Either way: no adb, no fastboot. Tried other usb slots. Tried reinstalling moto drivers.
The xoom never gets recognised by windows. I don't have the dongdong sound when I plug it, in either mode.
I already tried this:
http://forum.xda-developers.com/showthread.php?t=973355
but I get < waiting for device > because it's not recognised by windows...
Any other idea?
Thanks
Regards
Note: I might be away for several days. I'll try everything you say, but maybe I won't be able to post my feedback until monday night (around GMT timezone)
I have this exact problem.
So, when you power up the device, you press 'vol-down' when you see the Motorola logo? Because that should put you into fastboot mode. Don't use the power+vol-up, only turn on device and press vol-down when you see the logo. I've been in the same situation, but was able to get fastboot working like this...
if you hold the volume down button and power on the device and get no fastboot then you may as well just send it to motorola. looks like this is becoming a problem and cannot be fixed.
mbroeders said:
So, when you power up the device, you press 'vol-down' when you see the Motorola logo? Because that should put you into fastboot mode. Don't use the power+vol-up, only turn on device and press vol-down when you see the logo. I've been in the same situation, but was able to get fastboot working like this...
Click to expand...
Click to collapse
This. Flashing the wrong partition should *not* mean that you can't get into fastboot any more.
I know that volume down should get me to fastboot but in fact it doesn't. Windows never makes dong dong when i plug the xoom... My drivers are ok because my nexus one gets recognized instantly and adb is working fine on the phone...
Any reason you don't use RSD to flash the wifi xoom sbf file? (I'm pretty sure someone said that was released not too long ago)
I didn't try yet, I can't find the SBF for the wifi xoom.
I tried the 3G SBF file it's not even working. I know it's not the right file for my device but since it's already bricked...
I have RSD Lite 4.9, latest moto drivers, updated using the moto tool.
When I load the sbf file in rsd lite, I can't see the device, and pushing start has no effect.
I did that when the device was showing "Starting RSD mode 3"
How can I get it back?! I tried on my windows laptop and also on a macbook, without any luck.
This is happened to me , and i flipped cuz i rendered my $600 Xoom to a paper weight , i rebooted (Volup+power then voldown) , i tried ADB and it didn't work... then i left my computer to do something, i returned to my PC and i was flipping through DOS command lines (up and down arrows) and click enter in one of the commands by mistake and it worked! the command was "fastboot erase cache"
i then typed the following to return to stock (you need the stock files)
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
Thanks, but I don't have fastboot. It's always < waiting for device >
Topper Harley said:
Thanks, but I don't have fastboot. It's always < waiting for device >
Click to expand...
Click to collapse
You mentioned you tried the steps in http://forum.xda-developers.com/showthread.php?t=973355, but how did this section go:
"Even though there was no response from the device, I pressed Vol Down + power until the screen went black. I then quickly pressed and held Vol Up + power. The device then went into the bootloader, received the queued command from fastboot, and flashed the boot.img."
ed. The other suggestion I heard floating around is to flash the CDMA Xoom's SBF -- yes, it won't get you all the way there, but it might restore things up to the point where you can get into fastboot and then flash the stock images.
I did try already to fastboot flash boot boot.img (stock), then reboot pushing vol up, vol down, both, using clicking or holding them... no luck
I also tried to flash the VZW SBF file but RSD Lite doesn't even see the device. I'm trying now to get some linux running and use sbf_flash instead because I was told that it's more efficient than the linux one.
No luck yet on that part either.
I was able to get my xoom restore with the following steps:
Hold Power + Vol up to start reboot
immdiately hold Power + Vol down (This will get you to the Fastboot menu)
enter the commands
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
You've now successfully flashed your Xoom back to stock. Now it's time to relock the device.
Type fastboot oem lock, wait for the menu, the press the volume-down button. Then press the volume up button. It'll take a minute or so, then reboot. You're now completely back to stock and ready for the update.
hoopsdavis said:
I was able to get my xoom restore with the following steps:
Hold Power + Vol up to start reboot
immdiately hold Power + Vol down (This will get you to the Fastboot menu)
Click to expand...
Click to collapse
It stops here. I can't get fastboot.
I tried waiting for the battery to die and tried every combination of vol up/down/power, hold/click/double click the buttons...
I'll let it cool off for one day without battery... maybe it'll wake up wanting to give me fastboot...
I'm losing hope...
Topper Harley said:
It stops here. I can't get fastboot.
I tried waiting for the battery to die and tried every combination of vol up/down/power, hold/click/double click the buttons...
I'll let it cool off for one day without battery... maybe it'll wake up wanting to give me fastboot...
I'm losing hope...
Click to expand...
Click to collapse
I'm in the same situation here... tried basically all the same steps. I'm lost too... can't connect with ADB, Fastboot or RSD... tried all kinds of key combos as well. "Starting RSD Mode 3"... its wearing me down!!
How can i change the topic title? I wanted to say "xoom bricked?" but I typed rooted by mistake
I'm in this exact situation, and I've tried everything suggested here. I spent some time in IRC talking to a few developers, and we tried pretty much everything to get fastboot to work. No luck, so I tried RSD like you said, and that didn't work, either. Eventually we gave up, and I got an RMA from Motorola via their website. I should receive the FedEx box tomorrow so I can return it to them.
If you want, I'll report back here when the whole process is over and tell you if they end up fixing it for free or not. It sounds like it'll probably be at least a week, though.
benso87: yes, tell me. I have time don't worry (away from home until may 28th)
Otherwise, I think mine is definitely a brick. I tried the last thing I didn't: boot linux and test sbf_flash: not working.
I'll try to send it to moto (the device is imported).
I'm kinda sad... not for the money, but for the bad command that completely destroys a device in seconds... and right, for the money aswell...
Small update: I got the box yesterday and sent it back, then got an email this morning saying Motorola received it. Hopefully the whole process will go this fast.
They gave me a tracking number and a site to check to see how things are going, so that's more info than I was expecting. They haven't asked any questions yet, so that's also good.
I have flashed the CWM from TF201 by accident. Now the tablet is stuck in that CWM mode. I can't connect to usb using adb mode. Power+volume down does not work anymore. Any way I can reflash the correct CWM?
THanks
If you can boot to OS - you can use fastboot to flash any recovery.. or flash TWRP from goomanager.
upd: sry..don't see about "stuck".
abe_cedar said:
I have flashed the CWM from TF201 by accident. Now the tablet is stuck in that CWM mode. I can't connect to usb using adb mode. Power+volume down does not work anymore. Any way I can reflash the correct CWM?
THanks
Click to expand...
Click to collapse
I have made the same mistake. Although I can get the device to fastboot USB mode. I have tried to use CWM with the restore I made before I put in Cyanogenmod 9, as well as putting on the Cyanogenmod experimental #2 for TF300. No error messages at all and it wipes data and cash without any problems.
But I get locked on the Asus boot screen and it does not continue ie I am stuck as well.
I have as well tried to use the TWRP 2.1.5. I get the Teamwin loggo screen, it wipes all the data and verifies all the filesystems and reboots. Still stuck.
Is the device bricked ?
upd:The TF300 can not be shutoff either. When you hold the power button the screen goes black, but after ~5 s the device is starting again and is still stuck on the Asus bootup screen.
if you reboot it holding vol down and power, can you get back into the boot menu, to reselect fastboot?
if holding the power button doesn't switch it off, what happens if you leave it to run out of batteries then do this?
then you can flash the correct recovery.img
cheedear said:
if you reboot it holding vol down and power, can you get back into the boot menu, to reselect fastboot?
if holding the power button doesn't switch it off, what happens if you leave it to run out of batteries then do this?
then you can flash the correct recovery.img
Click to expand...
Click to collapse
Yes, I can get access to the fastboot and I have already tried to flash with the recovery.img. I have as well let the battery run out and tried it once more with the same result.
Still stuck on the asus bootup screen.
power
Hare,
I have same problem.tab cannot power off. Just reboots into cwm.
I was thinking to drain bat. Thanks for sharing that info.
There are a lot of topics about people who broke their devices with TF201's recovery.
Afaik, no one recovered it. Send to Asus.
So the device is bricked then :'(.
Thanks for clearing it up.
Sent from my GT-I9100 using XDA
RMA..
Guillaume,
Thanks for clarification.
I have read that ASUS wants 700USD for replacing/reflashing the bootloader. That was for the tf201. Any way to nvflash it back to factory? I don't believe that they have to change the MB.
I have no warranty left, but I don't want to be gouged by them either.
Any thoughts, info?
Hi,
I've do the same mistake, but I can use adb.
Do youhave any news about our problem?
Thanks
Midyr
unable to power off
My issue is that I have the CWM for the tf201. I did the update from the CWM app in Android. Bad idea. So now the tab does not power off s.t. I can get into the power+vol down mode. Adb does not work since I cannot ( don't know how) to make it go into the usb debugging mode. I have tried several things none of which have worked. Still stuck.
I wanted some feedback for a RMA from ASUS, posted it here but sor far no answers.
Not sure if it would really work, but on my Evo, I don't have to completely power off the phone to do the recovery sequence. I can do it during a normal reboot. There is a point just before the device starts booting again where it is technically "off", and if I hold volume down (don't even have to hold power on my Evo; volume down seems to be the only necessary button) starting at this point, the phone will boot into the bootloader.
So, next time the device reboots, just start holding volume down (possibly power also, just in case) at the "off" point.
Yesterday I went to go on my Motorola xoom wifi and boot logo was displayed and the back was very warm. Reset the device and it stayed on boot logo. Tablet was running fine the day before. I tried fastboot, RSD and recovery and the pc only discovers Xoom in RSD mode, Recovery does not even load. I grabbed RSD lite and tried to flash a sbf file. program detects tablets flashes rom and reboots tablet when finished. then the program sits there counting up to 100% then says "please manually power up this phone". If I reboot tablet stays at logo screen. Is there any way to sort, bear in mind I cant only connect to tablet in RSD mode. tried 2 computers and four cables and still fastboot is waiting for device.
Thank you for reading this post.
Current device Properties in RSD Lite.
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Boot Version: N / A
DRM Version: N / A
Your battery might be bad but try these with your xoom plugged into a power source.
Can you get into recovery? with power off press the power button 3 seconds after moto logo press volume down you will see recovery across top press vol up. If you can do a factory wipe
Have you tried getting into fastboot mode? with power off press press power while holding vol down. if you can we can try and fastboot the files.
If I select recovery I get
-->Android Recovery
Entering Android Recovery Mode
and the Motorola Logo in center of screen. Nothing else Happens.
In Fastboot mode Nothing shows in Device Manager and all I get at cmd is Waiting for device after "fastboot devices" command
I managed to flash "HUBWF_W5.H.6.4-20_SIGNED_UCAHUBLWFRTCOREEU_P010_A010_M004_HWwifi_hubble_AP1FF" in RSD Lite but same prob loads boot logo and nothing else. Is it possible this could be a cpu error ? as rom was running at 1.5ghz and if stuck in boot at 1.5ghz for a few hours more likely damage would occur.
I don't think it is the cpu overclock because when you flash a new rom it would wipe your settings.
Do you have adb install on your pc?
I have adb installed on pc yes but no way to talk to the tablet.
Thank you for your response.
Do you have another device such as your phone you can plug in to your pc and see if adb is working by typing adb devices.
dfib1 said:
Do you have another device such as your phone you can plug in to your pc and see if adb is working by typing adb devices.
Click to expand...
Click to collapse
If I plug my HTC one X into the computer both fastboot and adb list it.
Thank you for your response.
The only thing I can think of is that the battery is going bad and causing issues. Since you flash new software, can't get out of the bootloop and the back is hot I would see about replacing it. You can try a soft reset but I don't think it will help. hold down both vol buttons and the power button until your xoom restarts.
I am not 100% sure if it is your battery but I am out of suggestions. I know when the batteries go bad in our devices it can cause issues.
http://www.portatronics.com/product_info.php?info=p9278_Motorola-Xoom-Battery-Original.html
Hi!
I've read many threads and I haven't found the answer I'm looking for.
I've flashed the 5.1 update via TWRP on my tablet, and in the first boot it rapidly installed something, rebooted and never worked again. I can't use adb fastboot because my pc doesn't recognize my tablet. It shows as APX. I've tried to install the APX drivers and I can't, even after I reboot into advance settings.
Have I not read the correct post? Please help get my tablet back. I know it was stupid of me not to disable wifi before deleting the TegraOTA, I was in a hurry and forgot. Is there any hope?
Thanks for your patience.
Sounds like it took the forced update to kill it. If you can't get into the bootloader to use fastboot I don't think you'll be able to do much.
I might have done the same thing as you. If you do vol down+power does that still start up? if so this worked for me
https://forum.xda-developers.com/shield-tablet/help/help-stuck-nvidia-boot-screen-t3076462
I'm stuck now I'm on the stock rom and dont want to connect to wifi and get a killswitch, but I can't get a custom recover to load to change roms
Edit: When on the laying down android with "no command" if you hit the power+volup+voldown it will go into recovery settings. I guess the custom recovery isn't really flashing over.
Unplug USB cable press power for 30 seconds and then press the power and vol down should go to bootloader if your tablet didn't get kill switched. If it still doesn't boot and shows apx once connected then its been kill switched. Pressing power and vol up will place it into apx mode by default.
Sent from my SHIELD Tablet K1 using Tapatalk