My Motorola Xoom is stuck in an BootLoop
It is an European Xoom.
It had 3.1 (OTA).
I unlocked the bootloader, with succes.
Using this guide: http://imransarwar.com/index.php/how-to-unlock-and-re-lock-motorola-xoom-for-flashing/
Then I used this guide:
http://imransarwar.com/index.php/how-to-root-motorola-xoom-wifi-from-stock-3-1/
http://forum.xda-developers.com/showthread.php?t=1078019
After catch-the-boot, I came in the ClockWorkMod Recovery, as expected.
But the clicking on 'Install zip from SD card' showed the contents of the internal storage, not the physical SD.
So I rebooted the device, and have put the Zip-file on the internal Storage.
I went into recovery-again, i selected the zip-file.
It says 'Done '.
I Click on Reboot Device Now.
*BOOT LOOP*
I can still use:
adb reboot
And when i have done 'adb reboot', i can also reach fastboot.
(there is still hope?)
My Assumptions:
As the recovery 'install zip from sd' uses the internal storage,
it has no use to try putting something on the physical sd-card.
Is there a way to get something (read: some fix zip-file) on the internal storage, using nothing but ADB and Fastboot?
like adb push, would that work? if that would work, what do i have to push?
Any help is appreciated !
EDIT:
Found possible solution.
I'll think I should try this:
http://www.dkszone.net/unroot-relock-motorola-xoom-honeycomb-guide
It will get the device back to stock (I hope).
EDIT2:
Ok.. I tried the guide above.
My Device hangs on the Dual Core-screen.
Just found out that the File i have downloaded for the above guide is not the right version for my European Xoom (Wifi).
It was for 3G-Xoom-devices.
Downloading the right version now..
I Hope that i can come into Fastboot again, so i can flash the correct version.
EDIT3:
The device is still hanging on the Dual-Core-Screen,
it does not respond to anything, no buttons, no adb, no fastboot...
I guess i have to wait till the battery is empty, (this might take a while)
then turn it on while holding the volume down button to try to get into fastboot
If I cannot get into fastboot, my device is bricked I guess.
frankkienl said:
My Motorola Xoom is stuck in an BootLoop
It is an European Xoom.
It had 3.1 (OTA).
I unlocked the bootloader, with succes.
Using this guide: http://imransarwar.com/index.php/how-to-unlock-and-re-lock-motorola-xoom-for-flashing/
Then I used this guide:
http://imransarwar.com/index.php/how-to-root-motorola-xoom-wifi-from-stock-3-1/
http://forum.xda-developers.com/showthread.php?t=1078019
After catch-the-boot, I came in the ClockWorkMod Recovery, as expected.
But the clicking on 'Install zip from SD card' showed the contents of the internal storage, not the physical SD.
So I rebooted the device, and have put the Zip-file on the internal Storage.
I went into recovery-again, i selected the zip-file.
It says 'Done '.
I Click on Reboot Device Now.
*BOOT LOOP*
I can still use:
adb reboot
And when i have done 'adb reboot', i can also reach fastboot.
(there is still hope?)
My Assumptions:
As the recovery 'install zip from sd' uses the internal storage,
it has no use to try putting something on the physical sd-card.
Is there a way to get something (read: some fix zip-file) on the internal storage, using nothing but ADB and Fastboot?
like adb push, would that work? if that would work, what do i have to push?
Any help is appreciated !
EDIT:
Found possible solution.
I'll think I should try this:
http://www.dkszone.net/unroot-relock-motorola-xoom-honeycomb-guide
It will get the device back to stock (I hope).
EDIT2:
Ok.. I tried the guide above.
My Device hangs on the Dual Core-screen.
Just found out that the File i have downloaded for the above guide is not the right version for my European Xoom (Wifi).
It was for 3G-Xoom-devices.
Downloading the right version now..
I Hope that i can come into Fastboot again, so i can flash the correct version.
EDIT3:
The device is still hanging on the Dual-Core-Screen,
it does not respond to anything, no buttons, no adb, no fastboot...
I guess i have to wait till the battery is empty, (this might take a while)
then turn it on while holding the volume down button to try to get into fastboot
If I cannot get into fastboot, my device is bricked I guess.
Click to expand...
Click to collapse
It's not bricked. It's really hard (but not impossible) to brick a Xoom. They are hardy beasts.
I do wish you hadn't tried the revert/relock thing. You just made it worse as you tried to flash a 3G image on a WiFi only device.
But don't worry, it is possible to come back from this.
Just so you know, your first mistake was using old guides (though filled with good info, but files are not necessarity right) and mixing the sources. There are much newer guides in the Development section (page 1) for non-US Xoom, and I think people have better result when they stick with one source (in this case xda Xoom forum).
Second mistake is that you used the wrong recovery image...you used the v4.0.0.4 from RomManager, which is not compatible with the external micro sd card. You need the v3.2.0.0 R4c (Tiamat version). That's still the best most current version for the Xoom.
http://forum.xda-developers.com/showthread.php?t=1074979
If you had not gotten impatient and tried to revert/relock, you could have just flashed the proper recovery image and you would be good to go.
Good luck!
You seem to know your way around adb and fastboot so I'm sure you will be able to recover. Find the proper stock images for your Euro WiFi Xoom and flash them, download and flash the correct recovery image and you can take it from there.
It works again !
I Fixed it it works again
( I Do not have Root, but i'm glad its not bricked)
My device was hanging on the Dual-core screen.
So I waited till the battery was empty.
I connected the charger and usb cable, powered it on while holding volume-down.
Guess what, I came into fastboot
I have downloaded the correct images from the motodev-website.
Just followed the instructions (on the motodev site) and was good to go.
All what was left was updating to 3.1. That also worked fine.
I will be more carefull next time I try to Root an Android device, and make sure the guide is not for a different device. I have learned from my mistake.
frankkienl said:
I Fixed it it works again
( I Do not have Root, but i'm glad its not bricked)
My device was hanging on the Dual-core screen.
So I waited till the battery was empty.
I connected the charger and usb cable, powered it on while holding volume-down.
Guess what, I came into fastboot
I have downloaded the correct images from the motodev-website.
Just followed the instructions (on the motodev site) and was good to go.
All what was left was updating to 3.1. That also worked fine.
I will be more carefull next time I try to Root an Android device, and make sure the guide is not for a different device. I have learned from my mistake.
Click to expand...
Click to collapse
Excellent! So glad to hear it. You have skills so I'm sure you will be coool from now on.
just an update
This is an old thread so I'm putting this here for google searchers, like me.
I had the same problem but here's what extra I found/noticed
(1) To restart the xoom when it's in this state hit power button and volume up
(2) You can see that the tablet is still responsive if you hit volume down after 2 seconds as you'll get some options
(3) For me it wouldn't work if I used the motorola cable (yes, the real one) in the front pc usb ports. I had to use the usb 3 ports at the back of my pc. Yes, it's that picky! The difference was when I used fastboot to install the system image. It took 3 minutes then gave up, stuck the cable in the back of the pc instead and it took about 10 seconds and worked first go!
(4) The pc didn't recognise the xoom and adb didn't work, i.e. it said no device attached. However fastboot did recognise it
After point (4) I realised it wasn't bricked and could move forward
thanks to the other posters here for making me realise there was hope
NS4G
Will boot to fastboot and recovery
CWMR Touch 6.0.1.0
Situation:
My device started bootlooping after about a week of random restarts and freezes. I had just flashed BlackBean and now this, so I decided I was just going to flash a new ROM/Kernel combo. I remembered someone saying I should format /system to install the specific ROM, but I'm fairly sure I formatted /boot along with it, like an idiot. FYI - Fast Charge and a build.prop tweak to set permissions on boot was enabled when this happened. So then I try and flash a new ROM/Kernel combo to fix my bootloop and it wouldn't read the sdcard afterwards. Now it boots straight to fastboot everytime. Toolkit seems to be able to do some things via USB control like reboot the bootloader, but it does not detect an ADB device when I run the driver check or try to restore my CWM backup. I ran the stock+unroot option in Toolkit (was going to send it in thinking the sdcard thing was hardware at first) and it seemed to have went through the whole process correctly... Until the end when it did not reboot automatically like it should have. After doing this, I now get "STANDARD_SET_CONFIGURATION" on the phone when I insert the USB cord while in fastboot. It did not do this before, whether it is the new cord or the flash I do not know. My old cord WAS having problems with data though.
Problem:
I now have no USB debug or SDcard functionality. I assume because of missing files on /boot. I can mount nothing (except cache, but the PC doesn't recognize) without getting a "can't mount" error. This puts a serious dent in my novice ability to fix it. Anything in Toolkit that runs via ADB commands doesn't seem to work properly because it says the device is not in debug mode. PDAnet USB Drivers seemed to install without a hitch and device is recognized on my PC.
Errors:
When trying to mount ANYTHING except the cache while in CWM, I only get: "E:/ Can't mount /sdcard/".
If I try to mount USB storage I get: "E:/ Unable to write to ums lunfile (No such file or directory)Error mounting /sdcard!"
If I try to run any one click methods that use ADB I get: "Daemon not running* No ADB device detected. Make sure you have debugging enabled on your phone"
The log in CWM recovery always shows: "I: Set boot command "" failed to open /sys/class/android_usb/android0/state: No such file or directory" over and over (as many times as I tried to mount something while in recovery for that session)
Questions:
Do you think USB Fast Charge or having the build.prop tweaks enabled could have done something to USB debug? Is there a way to at least just fix the USB Debug problem? Am I correct in assuming that wiping the /system along with the /boot folder is what caused me to not be able to mount the /sdcard to flash another ROM? Is there a way to push the files I need onto the device to restore sdcard function and flash another zip?
Also, what fastboot do I need to be in to do the StockROM+Unroot method in the Toolkit? I have two. Only hold Vol Up/Power takes me to "FASTBOOT". Holding both Volumes+Power puts me into "FASTBOOT - NO BOOT OR RECOVERY IMG"
What is the difference?
I only ask because the Toolkit wants me to hold both volumes and up to get into bootloader mode, but they describe a big green "Start" with an android lying on it's back, mine does not look like that. It simply looks like regular fastboot, but says "FASTBOOT - NO BOOT OR RECOVERY IMG" instead.
It seems you messed with the ROM zip with some tool. Sorry could read your lengthy post completely.
I just want to know one thing clearly, what is the problem basically? where are you stuck?
Edit - Made it as concise as I could, hope it helps. Sorry for length.
Basically, the phone has a formatted /boot, /data, /sdcard, /system, dalvik cache, and I can't seem to use any of the flashing tools via Toolkit in Fastboot mode because the Toolkit says it "cannot find ADB device" please enable "debug" mode. Even when I run the driver check, it says ADB Device Not Found. Though I do have some control of the device via USB (I can use Toolkit to soft reboot from the bootloader) telling me my drivers are probably OK? I couldn't flash any ROM zips (or anything, even backups on the device) because I lost /sdcard functionality.
After a bunch of reading last night, it seems I want to Push a backup of /system and /boot onto the device, which should then restore USB functionality and allow me to flash a ROM... Right?
DizturbedOne said:
Edit - Made it as concise as I could, hope it helps. Sorry for length.
Basically, the phone has a formatted /boot, /data, /sdcard, /system, dalvik cache, and I can't seem to use any of the flashing tools via Toolkit in Fastboot mode because the Toolkit says it "cannot find ADB device" please enable "debug" mode. Even when I run the driver check, it says ADB Device Not Found. Though I do have some control of the device via USB (I can use Toolkit to soft reboot from the bootloader) telling me my drivers are probably OK? I couldn't flash any ROM zips (or anything, even backups on the device) because I lost /sdcard functionality.
After a bunch of reading last night, it seems I want to Push a backup of /system and /boot onto the device, which should then restore USB functionality and allow me to flash a ROM... Right?
Click to expand...
Click to collapse
Your storage memory is completely inaccessible?
Yes, no way to access it via CWM. ADB stuff does not work either. It seems Fastboot stuff DOES. I would like to find a boot.img and system.img to flash via Toolkit (I believe toolkit uses fastboot or odin for these) to see if that would work for me. Any ideas?
It seems like the easy nature of unlocking, rooting, and customizing this phone leads to less of these kind of discussions, I can usually find many files and discussions pertaining to this for HTC phones, but never for this phone.
My bootloader version is KE1, but my baseband version is LF2, makes no sense to me.
The KE1 bootloader was when I was on ICS, but the LF2 baseband was from Jellybean... wth?
Do you think the time I flashed "stock+unroot" on the toolkit that it only partially took? (I did try to back it up to ICS because the Jellybean download didn't work). It seemed as if it flashed everything via fastboot, but never restarted at the end and still won't boot when done.
same problem kinda
i am having the same problem as this with my nexus. mine started after i downloaded Jellybean.it worked fine for about 1 month. i had changed nothing but when i would change my battery or restart my phone it would get stuck at the google screen every now and then, then it started more often. i could normally pull the battery and restart it and it would work after a couple of times doing that. but now this last time i tried that the phone wouldnt go past google screen at all. i can access my clockwork mods recovery but when i try to install zip from sd i get the error cant load sd i have tried everything i know and cant get nothing to work. please help. i miss my nexus this prevail is too slow and small...
Your drivers don't seem to be installed properly.
Get that right, then you can reflash your recovery via fastboot, then you can mount your usb and transfer anything (rom kernel gapps etc etc)
Edit: oh and Bamamac82, that's not the same problem at all. Create a topic of your own.
polobunny said:
Your drivers don't seem to be installed properly.
Get that right, then you can reflash your recovery via fastboot, then you can mount your usb and transfer anything (rom kernel gapps etc etc)
Edit: oh and Bamamac82, that's not the same problem at all. Create a topic of your own.
Click to expand...
Click to collapse
@ polobunny - There is no way for me to install them more properly if I can't go into debug mode to install them though... I wiped out ALL drivers and manually reinstalled the drivers from PDAnet that had previously worked perfectly on my device. But now it never installs as Nexus S, only as Samsung ADB Interface or some such. I've tried it with PDAnet drivers and the Samsung drivers and have followed every driver install guide on the web... Any other suggestions on how to do this properly? I was even thinking of installing a Google SDK just to see if the drivers would work better...
@ Bamamac82 - Yes, that is pretty much the exact same problem, with the exception of the fact that you didn't wipe the /boot partition as I did. But yeah, I installed a JB ROM, it got a few random restarts, froze up twice, then one morning got stuck in a bootloop after I pulled the battery on a freeze up. Not having a working USB cord at the time botched me, because I couldn't get my drivers reliably installed before anything happened, I was using AirDroid because my OEM cable wasn't working with data reliably.
I totally thought the sdcard problem was because I formatted /boot in a hasty ROM flash though. Could I be wrong here?
DizturbedOne said:
There is no way for me to install them more properly if I can't go into debug mode to install them though... I wiped out ALL drivers and reinstalled the drivers from PDAnet that had previously worked perfectly on my device. But now it never installs as Nexus S, only as Samsung ADB Interface or some such.
And Bamamac82 has the exact same problem, with the exception of the fact that he didn't wipe the /boot partition as I did. But yeah, I installed a JB ROM, it got a few random restarts, froze up twice, then one morning got stuck in a bootloop after I pulled the battery on a freeze up.
I totally thought the sdcard problem was because I formatted /boot in a hasty ROM flash though. Could I be wrong here?
Click to expand...
Click to collapse
When you're in fastboot mode on your phone, on your windows PC point the unknown device or the device with an exclamation/question mark to the path where the .inf for the drivers are located. If it still doesn't detect it, you can always try and force it to install a certain device (adb debug bridge or something of the sort).
Once that is done as I said you won't have any problem fastboot'ing to your phone and doing the other steps. Windows drivers and especially the adb drivers can be finnicky.
Your SDcard problem has nothing to do with the fact your formatted boot partition though, those are not linked.
Edit: Oh and I know there is some people, namely with NS4Gs, that had issues with the drivers. I believe for some reason there's some missing IDs in the inf making it impossible to install automatically. Forcing it should work though.
Polobunny thank you so much for your help so far. My device has been softbricked for a week and I'm using a HTC Hero for now! It's atrocious. I'm going to try as you said when I get home tonight and will update if fastboot allows me to flash after that.
Any idea where I can get all the .img's I need? I can only find the complete .tgz for IMM76D (which is fine for now just want it back to working state) and don't know how to extract .img's from it. Can't even find the complete .tgz for JRO03R though, the link is always down. At this point, all I want is a factory img to start from so I can upgrade to JRO03R, root it, and then make a fresh NAND backup from there.
If I were you, I would download Odin, a factory image from Google (just search nexus s factory image), the SDK tools (Google it) and would "reset" the phone.
You will easily find a guide for Odin. Then you'll just have to follow it and your nexus should be fine (but it will be factory reseted and you will have lost all your data )
Sent from my Nexus S using xda premium
Sorry guys, have been putting late hours in at work and haven't had much time until this weekend.
@BenHeng, that's what I am about to look into tonight. I didn't want to learn an entirely new aspect to restore this, I have been limited on free time and am starting to think it will be less hassle than dealing with this.
Only caveat to that, is that I definitely would like to know what happened to cause the SDCARD problem, because that was the main problem that got to me here, would like to prevent that from happening again.
ADB
Make sure ADB debuging is checked under Developer options
localpagefirst said:
Make sure ADB debuging is checked under Developer options
Click to expand...
Click to collapse
Please read the thread before replying.
@polobunny - I did a complete manual install of the RAW drivers, and got it to recognize properly as a Nexus S, as it did when USB Debug and everything worked correctly... But it still does not recognize it as an ADB device when running a driver check.
Is it safe to continue forward with a flash via ODIN in this state?
Hi, I don't understand why you want to use ODIN, fastboot commands still don't work after you installed correctly your driver?
Anyway you can find all (new and old) originals google image here:
http://www.randomphantasmagoria.com/firmware/nexus-s/
Listen mate, the best way would be to flash the factory image via fastboot in bootloader mode. Follow this simple step to step guide.
If you have any issues. post them there on the blog post itself :good:
DizturbedOne said:
Please read the thread before replying.
@polobunny - I did a complete manual install of the RAW drivers, and got it to recognize properly as a Nexus S, as it did when USB Debug and everything worked correctly... But it still does not recognize it as an ADB device when running a driver check.
Is it safe to continue forward with a flash via ODIN in this state?
Click to expand...
Click to collapse
Please, please don't use a shi**y 1-click package thing. There's no driver check to be done other than using adb and typing "adb devices". Do it manually and report the results. It should show your adb device ID, a long string of number and letters.
polobunny said:
Please, please don't use a shi**y 1-click package thing. There's no driver check to be done other than using adb and typing "adb devices". Do it manually and report the results. It should show your adb device ID, a long string of number and letters.
Click to expand...
Click to collapse
I get nothing when I do that. It says "List of devices attached" and a blank line underneath. When I plug the USB in during fastboot I get "STANDARD_SET_CONFIGURATION" at the bottom, which I never get until I install the drivers.
It seems as if the computer must recognize the device in debug mode in some way to properly install the drivers.
Why is my sdcard partition unable to be written to? This never would have been a problem as I always keep a couple backup ROM's on the phone. Either way, it seems as if all of this is for nothing if the phone will not allow me to read/write to the memory in the device.
Hey guys,
I have an HTC One XL with TWRP and Pac rom's 4.4.4 and about a week ago my touch went out. Hoping it was the digitizer, I got one but that wasn't it. I believe it's the mainboard since it doesn't even work in recovery mode.
Well anyway, I got a new phone, LG G flex, and I would really like my data out of the one X. (Pics, messages, etc)
Is there any way to take it out not having to use the touch or the soft buttons?
And I know it's been asked before but I tried the similars and got nothing.
Theres numerous remote control apps in the app store that will let you remotely control your android device from a pc eitger wirelessly or over usb. Also, if you just want to get data off there's just using the usb cable to access the phone storage.
Web key app may be worth a try.
Sent from my Nexus 7 using Tapatalk
The latest versions of TWRP are MTP enabled, so if you can flash that and then connect the phone to your PC while booted into recovery it'll be as simple as using Windows Explorer to copy your data across.
Transmitted via Bacon
I'm gonna bring this up again since last time produced no results.
I can't instal softwares without touch. But that TWRP option seemed viable.
Can someone elaborate on that?
Put the phone into fastboot mode, unlock the bootloader (if it isn't already), flash TWRP recovery, boot into TWRP recovery, connect to PC.
Transmitted via Bacon
timmaaa said:
The latest versions of TWRP are MTP enabled, so if you can flash that and then connect the phone to your PC while booted into recovery it'll be as simple as using Windows Explorer to copy your data across.
Transmitted via Bacon
Click to expand...
Click to collapse
I have TWRP installed on my GS5. I can't see my screen so I think I've booted to it and it's plugged in, but I'm not getting my usb connection. Could you tell me the sequence of volume keys to press to mount MTP? Or why isn't it happening automatically?