Hello,
I am having trouble getting my xoom to boot into the OS. The xoom boots to "reading ODM fuse: 1" and gets stuck. I have been a xoom owner since launch and have unlocked, rooted, flashed roms for a while now and am fairly comfortable with the rooting process. About a week ago I used SBF to return my xoom to its factory default settings so I can pass it on to my daughter. The process completed successfully, however, when the xoom rebooted it got stuck with the following message on the screen.
LTE modem is OFF
Cold-booting Linux
Reading ODM fuse: 1
I no longer get the M logo. I can still access fastboot. I am able to flash recoveries through fastboot however when I reboot the device I get the same message. I tried the following to see if I could resolve the problem but it did not work.
Completed the below steps through fastboot.
Flashed Tiamat's CWM Recovery (Older and newer version)
Flashed TWRP Recovery
Flashed boot.img
Flashed system.img
Erased boot, system, recovery, cache
Flashed boot and recovery after erasing them first.
And for some people who may wonder if I have tried booting directly into recovery, Yes I have. I get the following message when I try to get into recovery and the system freezes.
Entering Android Recovery Mode
Reading ODM fuse: 1
Xoom information:
Original Xoom 3G upgraded to 4G by Motorola
Last flashed ROM was EOS Jelly Bean nightly.
Flashed SBF from Motorolas Developement site and have not been able to boot into the OS since.
Any help would be greatly appreciated.
Please post all questions in the Q & A section. Thanks! Thread moved.
Sent from my Galaxy Nexus using Tapatalk 2
http://developer.motorola.com/products/software/
I suggest you find the correct ROM and follow the procedures in that website. Flash back all the original files then your XOOM should boot up.
Thanks for the reply. But oI tried that already but still no luck.
Sent from my EVO 4G LTE using xda app-developers app
You sure? If you can flash it in using fastboot, and it says successful then it should work. Those files are suppose to downgrade you back to honeycomb and restore everything back to factory default. It be like the day you got your XOOM.
Yes I am positive. I but I did just go ahead and do it again just now, still no success. Every step completes successfully but the end result is the same. Stuck at 5hat same place.
Sent from my EVO 4G LTE using xda app-developers app
Related
Hey all. I have reached a defect in my research and I could use some help.
I have a Wifi Xoom that I fried the mother board on. Not sure how, just woke up one morn and it wouldn't turn on anymore.
So I replaced that MOBO with another that was listed as soft bricked (It was cheep so I figured why not try).
Anyway with the new board installed I can boot to the Motorola Logo, I can load fastboot, recovery and RSD. The device appears as it should on my pc and I can fastboot flash.
I replaced the system image, the recovery image, The userdata image and the boot image. using fastboot. I also cleared cache, from fastboot and recovery as well as deleting all user data from recovery (Factory Reset).
I also re-installed the whole system using an RSD Image which went successfully as well.
Now I know its actual flashing because I flashed a different recovery to test and that worked, but for some reason im stuck in a boot loop at the Motorola Logo. I can still access all features (fastboot, recovery and RSD) but it will not boot past the Moto Logo.
I have tried installing the 4.1.1 and 4.1.2 updates through recovery which both installed their updated boot loaders and for a moment I thought I had success when I saw the xoom boot image with the flashing squares, but then that froze and it rebooted never to be seen again.
So my question is, is this a hard brick and I should just stop trying or does anyone have any other suggestions?
Also I am not using a Moto cable, but it tells me that I am successfully flashing, and as I stated I am seeing the recovery flash correctly, Does this make a difference being that I have successful flashes for other partitions? Is the Boot partition special? It tells me I'm flashing, but is it lying to me?
Everything I read thus far indicates that if you can access fastboot and recovery that its not hard bricked, but what exactly does a hard brick look like?
Thanks All any insight is appreciated.
Hey all, i made my own Motorola usb cable and tried to reflash again with no success. I'm still boot looping.
Sent from my SCH-I535 using xda premium
I have and tried with an official Motorola cable now as well without success. ideas?
Sent from my SCH-I535 using xda premium
Try reflashing the official imgs (provided from motodev site) with fastboot and after locking your bootloader. Try booting up, if nothing changes, sorry but I doesn't know how to fix then. Hope it works...
Sent from my MZ601 using XDA HD Premium using 1/8of my brain, the other 7/8 is thinking in my love Isadora
Yea I tried that, no worries, but do you know what does a hard brick look like? I have searched and found no real description, all anyone says is if you can get to fast boot is more than likely not.
Sent from my SCH-I535 using xda premium
OK , I know its been a while but I just started playing with this again.
OK so I got the idea that it might be a permissions issue. so I wiped everything again and re-installed again. Following this I tried to fix permissions in TWRP which failed. I installed CWM and ran fix permission which was successful. after that I was able to boot the tablet to android and install an account.
However now it is rebooting with some frequency and periodically it will get stuck at the moto screen again.
At this point if I perform a data wipe and clear cache I can get the tablet to boot again but I still have this issue.
Also If I fix permissions again from either recovery or rom manager it sends me back to the being stuck at the moto screen and I have to start again.
Thoughts?
Hey guys,
I've been using this website as reference for years but never had an issue I hadn't already seen asked.
I've been looking for weeks for a solution to this and haven't found anything.
I tried to flash cm10.1 over my stock 4.1.2 and corrupted the system.
It was booting directly to AP Fastboot and showing an error about not calling the ROM properly.
I tried reflashing using RSD Light 5.7 but every time it tried to flash the system it said the phone returned failed.
So I upgraded RSD to v6.1 and tried again. This time the phone says it flashed properly but it freezes during the droid boot logo.
I've tried using the utility and it gives me the same results.
I can get into factory recovery and I've performed several hard resets. But the phone still freezes whenever it tries to load the system.
I'm using a Motorola Factory Cable on a high speed USB port.
Any ideas why I'm stuck in a soft brick that I can't flash out of?
ShiningRaven said:
Hey guys,
I've been using this website as reference for years but never had an issue I hadn't already seen asked.
I've been looking for weeks for a solution to this and haven't found anything.
I tried to flash cm10.1 over my stock 4.1.2 and corrupted the system.
It was booting directly to AP Fastboot and showing an error about not calling the ROM properly.
I tried reflashing using RSD Light 5.7 but every time it tried to flash the system it said the phone returned failed.
So I upgraded RSD to v6.1 and tried again. This time the phone says it flashed properly but it freezes during the droid boot logo.
I've tried using the utility and it gives me the same results.
I can get into factory recovery and I've performed several hard resets. But the phone still freezes whenever it tries to load the system.
I'm using a Motorola Factory Cable on a high speed USB port.
Any ideas why I'm stuck in a soft brick that I can't flash out of?
Click to expand...
Click to collapse
Format system via any of the custom recoveries before flashing your new ROM - this will wipe out any leftover problems completely & should let you start 100% fresh with a new ROM.
tzlot said:
Format system via any of the custom recoveries before flashing your new ROM - this will wipe out any leftover problems completely & should let you start 100% fresh with a new ROM.
Click to expand...
Click to collapse
I lost my root when I originally got stuck in fastboot. And I can't boot up the phone until I can get it fixed.
ShiningRaven said:
I lost my root when I originally got stuck in fastboot. And I can't boot up the phone until I can get it fixed.
Click to expand...
Click to collapse
Can you get back into fastboot now? If so
Use fastboot to flash a custom recovery (CWM, TWRP or OUDHS)
use the recovery to factory reset, wipe cache/dalvic, AND format system (sometimes in the advanced menu)
then flash rom of your choice.
If you can't get fastboot working you'll need smarter help than I can give you... but the format system step clears out all kinds of gremlins.
I can get into fast boot but I don't have an unlocked boot loader to flash anything custom.
ShiningRaven said:
I can get into fast boot but I don't have an unlocked boot loader to flash anything custom.[/QUOTE
If you can get into fastboot then you should be able to unlock b/l with this toolkit I used it and it worked for me you can also flash rom with it its in the orginial development thread
http://forum.xda-developers.com/showthread.php?t=2154995
Click to expand...
Click to collapse
ShiningRaven said:
So I upgraded RSD to v6.1 and tried again. This time the phone says it flashed properly but it freezes during the droid boot logo.
I've tried using the utility and it gives me the same results.
I can get into factory recovery and I've performed several hard resets. But the phone still freezes whenever it tries to load the system.
I'm using a Motorola Factory Cable on a high speed USB port.
Any ideas why I'm stuck in a soft brick that I can't flash out of?
Click to expand...
Click to collapse
Had the same problem after a fastboot via the utility. Try powering your phone down completely and leaving it off for about 5-10 min. This can be tricky with the hardware buttons so if you have access to TWRP that will help as it has a power off option. You might also try flashing again via the utility. I believe that's what I had to do, but the power down method is what a friend suggested based of his experience with the same exact problem you documented.
FIXED!!!
OK first I want to thank everybody who responded. I got tied up with work and kind of forgot about this project for a few days.
Repeated uses of the Utility and RSD both left me stuck with the phone freezing every time it tried to load the system into memory.
I had checked out the toolbox before but I didn't think I could do much from a locked bootloader.
After your suggestion jmcdonald I tried it again. It says my device isn't available to be unlocked so I tried downgrading back to ICS.
The toolbox says that it failed but it must have fixed something because the phone booted back up to android 4.1.2 stock!
So far I have bricked a lot of phones and learned a lot about ADB in the process of fixing them but I've never had one I was so certain was bricked permanently. But now it seems to be working fine, I'm scared to try rebooting in now.
Definatly going to unlock the bootloader pronto.
Thanks again jmcdonald!
I haven't seen this written anywhere yet but I've found something weird with the TWRP loop, months back I used the asus system wipe and got stuck in the TWRP loop because I supposedly erased all the data and file structures on my system but every now and then I keep checking for fixes and playing around with the tablet, today I charged it up again and went into TWRP, on the PC (win 7) ran the cmd "ADB reboot bootloader", for the hell of it I chose the middle option, the android, is said cold booting linux, the chrome asus logo came up with the spinning dot animation and I just waited and then it began updating my app's and my system loaded right up, everything was there. There's no sd-card in the external slot so it's pulling straight from the tablet, wifi connected, all my apps began updating from the marketplace, I can download, TWRP just says the tablet is blank. It seems to have no root access anymore though, hopefully this can be helpful. Also if I reboot it goes right back to TWRP but if I run the reboot bootloader cmd and choose the android it starts right back up without having to update everything again.
pariahcomplex said:
I haven't seen this written anywhere yet but I've found something weird with the TWRP loop, months back I used the asus system wipe and got stuck in the TWRP loop because I supposedly erased all the data and file structures on my system but every now and then I keep checking for fixes and playing around with the tablet, today I charged it up again and went into TWRP, on the PC (win 7) ran the cmd "ADB reboot bootloader", for the hell of it I chose the middle option, the android, is said cold booting linux, the chrome asus logo came up with the spinning dot animation and I just waited and then it began updating my app's and my system loaded right up, everything was there. There's no sd-card in the external slot so it's pulling straight from the tablet, wifi connected, all my apps began updating from the marketplace, I can download, TWRP just says the tablet is blank. It seems to have no root access anymore though, hopefully this can be helpful. Also if I reboot it goes right back to TWRP but if I run the reboot bootloader cmd and choose the android it starts right back up without having to update everything again.
Click to expand...
Click to collapse
so if you can get to bootloader. why dont you fastboot flash the blob file for the latest update? this would install system and new bootloader and stock recovery. from there regaining control of tablet. then just fastboot flash twrp and flash a custom rom....just a thought but if your getting into bootloader you should be able to flash blob.
I tried that right when I saw fast boot coming up, nothing would go through, I did fix it by using the method posted by Buster by using fast boot to systematically erase everything one by one then flash new firmware, just thought this info might be helpful, it's almost like twrp becomes a separate partition when you use asus wipe since everything is still there and bootable
kaos420 said:
so if you can get to bootloader. why dont you fastboot flash the blob file for the latest update? this would install system and new bootloader and stock recovery. from there regaining control of tablet. then just fastboot flash twrp and flash a custom rom....just a thought but if your getting into bootloader you should be able to flash blob.
Click to expand...
Click to collapse
I'm having issues and this won't help me. I flashed the JB version of twrp 2.5 instead of the 4.2 one and am getting a bootloop on the Asus screen. I reflash the update blob and it just doesn't boot
It IS Lupus said:
I'm having issues and this won't help me. I flashed the JB version of twrp 2.5 instead of the 4.2 one and am getting a bootloop on the Asus screen. I reflash the update blob and it just doesn't boot
Click to expand...
Click to collapse
search i have seen a guide for your specific issue on how to correct. it i was under q&a.
kaos420 said:
search i have seen a guide for your specific issue on how to correct. it i was under q&a.
Click to expand...
Click to collapse
I figured it out. I downgraded my bootloader back to 4.1(I know it went because I had the fastboot USB icon back) flashed the correct recovery and wiped everything. My data partition got corrupted. Got back into a working environment and flashed 4.2.1 again, with the proper recovery.
Sent from my HTC6435LVW using xda app-developers app
It IS Lupus said:
I figured it out. I downgraded my bootloader back to 4.1(I know it went because I had the fastboot USB icon back) flashed the correct recovery and wiped everything. My data partition got corrupted. Got back into a working environment and flashed 4.2.1 again, with the proper recovery.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
alternativly this should work as well for latest fw
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
(just for reference)
cheers
-Buster
Buster99 said:
alternativly this should work as well for latest fw
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
(just for reference)
cheers
-Buster
Click to expand...
Click to collapse
This is how I ended up fixing mine, can't thank you enough Buster
Sent from my GT-I9505 using XDA Premium 4 mobile app
Hey guys, first off new here though I've perused the forums for a couple of years without a profile. Anyways, I just recently picked up my lovely nexus 5, Sunday. And today I got around to rooting/custom recovery and updating to 4.4.1 via sideloader. But for some reason when I flashed CWM or TWRP both the latest versions, neither work. At the moment I have no functioning recovery. All it does is show the Google logo screen, never goes to the little android guy or the custom recovery screen, nothing. Just the white Google logo with black background and small lock at the bottom. Any help would be greatly appreciated. I am on 4.4.1, rooted with cf auto, I have erased the install-recovery.sh, I have tried twrp one click, I have tried manually flashing cwm img file and twrp img file. Each time through adb, each time using fastboot erase recovery and fastboot install recovery recovery.img.
I've followed countless tutorials, and followed them to the letter but nothing has worked. Any help is greatly appreciated!
Sent from my Nexus 5 using xda app-developers app
imyourpriest said:
Hey guys, first off new here though I've perused the forums for a couple of years without a profile. Anyways, I just recently picked up my lovely nexus 5, Sunday. And today I got around to rooting/custom recovery and updating to 4.4.1 via sideloader. But for some reason when I flashed CWM or TWRP both the latest versions, neither work. At the moment I have no functioning recovery. All it does is show the Google logo screen, never goes to the little android guy or the custom recovery screen, nothing. Just the white Google logo with black background and small lock at the bottom. Any help would be greatly appreciated. I am on 4.4.1, rooted with cf auto, I have erased the install-recovery.sh, I have tried twrp one click, I have tried manually flashing cwm img file and twrp img file. Each time through adb, each time using fastboot erase recovery and fastboot install recovery recovery.img.
I've followed countless tutorials, and followed them to the letter but nothing has worked. Any help is greatly appreciated!
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
mmh you don't need to erase the recovery before installing a new one, i wouldn't even recommend it
maybe just trying: fastboot devices
fastboot flash recovery recovery.img
fastboot reboot-bootloader
by the way, doesn't even the stock rec. occur?
its fastboot flash recovery recoveryname.img not fastboot install recovery recoveryname.img
stay away from root toolkits, its much faster without. without a toolkit this is all you do..
fastboot oem unlock (unlocks bootloader)
fastboot flash a recovery
flash the supersu su binaries in your new recovery
reboot
Sorry about the late response to this, but the conclusion was apparently the guide that sent me to a certain twrp (and cwm for that matter) were previous editions that weren't compatible. As for the question about stock rec. No stock wasn't showing at all, it got stuck on the little Andy with an exclamation mark logo. Finally fixed it by going through a walk through, unrooting it, flashing the stock .IMG and then locking the bootloader. THEN using kwonggers toolkit to unlock, root, twrp etc.
Anyways, in the end it all worked out thanks to looking around XDA thanks guys!
PS: drivers with this thing and windows 7/8 can be quite silly.
Sent from my Nexus 5 using xda app-developers app
Weirdest problem, and not one that I've ever encountered after playing around with Android since the G1 days!
My Boost Moto G 2013 will only boot into the recovery, no matter what I do. I've searched and searched through Google and on XDA and found nothing that matches my problems exactly.
I can get into the bootloader (am running version 41.1A) and flash a new recovery. I've got TWRP on there right now, but I've tried CWM as well -- same problem. I've actually installed Android 5.1 from the stock flashable zip, and it says it flashes fine, but still won't boot into it. No matter how I restart the phone, it just goes straight into recovery.
Any ideas?
I'm assuming that you've tried different ROMs? I had a weird problem where I could no longer flash any ROM's without getting an error. Only after I did a complete wipe of everything (including internal storage which was the key) was I able to properly boot up. Not quite the issue you're having but worth a shot, make sure you can access the phone on your PC so that you can copy over the ROM after the wipe.
I have had this problem recently. I believe I had to fastboot flash stock recovery, then an older, smaller CWM to avoid partition mismatch problems. Then flash the TWRP you want with a zip with CWM.
Sent from my XT1031 using Tapatalk