Related
I was using this guide http://forum.xda-developers.com/showthread.php?t=1078019 to unlock, install CWM, and then root. Unlocking was fine, installing that version of CWM seemed okay, but when I enter command "fastboot reboot", then hold down the volume - button after 3 seconds of the Moto logo showing, then pressing the volume + key, I get only 1 option....-->Android Recovery. I press the Volume + key, get "Entering Android Recovery Mode", and below that "Reading ODM Fuse 1", then the screen switches to an android with a yellow hazard sign in his tummy.
From that screen, if I press Volume + and power, I see:
Android system recovery <3e>
Use volume keys to highlight; power button to select.
reboot system now
apply update from USB drive
wipe data/factory reset
wipe cache partition
I don't get a choice to apply something from the microSD card I have installed with the WiFi_RootTool_3.1.zip I put on the card.
Has anyone had this happen? I can't ask in the development forum. I also just got the Xoom back from a repair, and it was wiped to stock, then I did the 3.1 update when I got it back this morning. Is the fuse thing something they may have done to block rooting?
Have you tried reformat your sd card?
becu4xda said:
Have you tried reformat your sd card?
Click to expand...
Click to collapse
I'll try that. But would that stop it from going into recovery?
becu4xda said:
Have you tried reformat your sd card?
Click to expand...
Click to collapse
I reformatted my sd card, but I still can't get CWM to work and boot into recovery. Same message-
-->Android Recovery
Entering Android Recovery Mode
Reading ODM fuse: 1
And that's it....no options to load the root zip from an SD card or anything. Is there a way to push root without using the SD card? Or is that ODM fuse thing making it impossible?
becu4xda said:
Have you tried reformat your sd card?
Click to expand...
Click to collapse
Nothing at all to do with CWM.
OP: Try flashing the recovery again. To get into recovery, type adb reboot recovery, or use an app such as Quick Boot.
Edit: You can't use CWM to root, you need to do that first.
siscim23 said:
Nothing at all to do with CWM.
OP: Try flashing the recovery again. To get into recovery, type adb reboot recovery, or use an app such as Quick Boot.
Edit: You can't use CWM to root, you need to do that first.
Click to expand...
Click to collapse
I have to root first? I'm not sure how to do it....can't find any other methods of rooting 3.1....everything on Google just points me to the same method, using the SD card that won't work cuz I can't boot into recovery. Ugh.
Hey jump hour PM me.
Hey guys,
I called JumpHour and we tried to troubleshoot this over the phone. We aren't able to get into the recovery because of error "reading odm fuse: 1". The OP is using Windows 7 64 BIT and has the SDK installed properly. He updated the sources and installed them so those are up to date. We also verified that USB debugging was enabled and that the correct files were in the tools section in the SDK folder.
We ran the commands:
adb reboot bootloader
fastboot-recovery ........ (we typed it in correctly accoriding the thread)
fastboot reboot
and we get that error message.
This was all initiated while the Xoom was powered on. JumpHour stated that he had to send his Xoom back to Moto because his Xoom got messed up during the re-locking process when he unrooted a one click root and re-locked.
We then went ahead and downloaded the recovery image again and replace the one in the tools folder. We ran the commands again and we were getting the same error.
Does anyone have any idea what is going on with this process? Are we missing something? Is something broken?
Get the official images. I am assuming you have a USA 3g or wifi model.
Follow the steps to return the device to stock. But do not issue the reclock bootloader command. There is no need to relock.
From there power up the device and turn on USB debugging.
Then adb reboot into recovery. That should bring you to the stock recovery.
If all goes well from here just do what ever else you where intending to do in the first place.
You most likely can just flash the stock recovery but I would just do a full flash back to official images minus relocking bootloader.
Sent from my Xoom using Tapatalk
Then let the ota update it to 3.1 and so on.
Sent from my Xoom using Tapatalk
What's the status JumpHour? Did you get it to work. I told you it may have been due to the images. Hopefully that fixes your issue. Take care dude.
gqstatus0685 said:
What's the status JumpHour? Did you get it to work. I told you it may have been due to the images. Hopefully that fixes your issue. Take care dude.
Click to expand...
Click to collapse
Hi, thanks for the response. I'm gonna try it now. I was up REALLY late last night, and just got up a little while ago. I'll definately respond after I try it out.
Finally, I did it!
Okay, I fixed it finally. Reloaded the stock images, and it's now rooted with SD support. Yay! Only took 2 days!
Thanks for all your help guys.
Can reflashing with original images fix recovery mode mount problem?
Does any window is flashing to the original images can restore access to the sdcard IF the recovery mode in the official recovery mode (not CWM) says that you cannot mount the sdcard?
Hi. I'm trying to root my brand new xoom but it's a little tough here
My problem is that I just flashed a recovery (recovery-Tiamat-R4c-100611-1150-cwm) and when i reboot in recovery, i'm stuck with a droid and it's because my sdcart seems to not be recognize... Any ideas why? Thanks
doumi215 said:
Hi. I'm trying to root my brand new xoom but it's a little tough here
My problem is that I just flashed a recovery (recovery-Tiamat-R4c-100611-1150-cwm) and when i reboot in recovery, i'm stuck with a droid and it's because my sdcart seems to not be recognize... Any ideas why? Thanks
Click to expand...
Click to collapse
You seem to have the correct recovery installed...if that's the version you have, don't change that.
Are you sure your sdcard is good? If you have an android phone, can you use it in it? Sometimes an sd card needs to be formated in an android phone first.
Anyway, I would check the sdcard's authenticity and whether it is formated right.
Don't worry, you'll get it.
Yes i tried 2 differents sd cards (one I use everyday in my desire HD). I flashed the recovery once more still the same problem. Weird...
doumi215 said:
Yes i tried 2 differents sd cards (one I use everyday in my desire HD). I flashed the recovery once more still the same problem. Weird...
Click to expand...
Click to collapse
Check which recovery version you are flashing. You need v3.2.0.0 R4c. If you are flashing through Rom Manager, you may be flashing v4.0.0.4, which doesn't recognize the external sdcard.
I justed checked it's v3.2.0.0 R4c.. I unlocked it, flashed th recovery. tried to flash my rom and then get stuck with the little droid... really irritating
Ok solved. I had to force the recovery when the tablet start (wait 3 sec when you see the motorola logo then volume down, then volume up)
Thanks for the help
doumi215 said:
Ok solved. I had to force the recovery when the tablet start (wait 3 sec when you see the motorola logo then volume down, then volume up)
Thanks for the help
Click to expand...
Click to collapse
Great! I'm glad to hear it.
Hi,
I rooted my Samsung Infuse and flashed CM7 as explained in http://forum.xda-developers.com/showthread.php?t=1311960
It looks awesome, many thanks to the people who put it together. ( I couldn't reply there since I am a "noob")
My phone boots fine in to CM7 and I can make calls and use other hardware, no problem so far.
I was trying to get Gapps by going to Rom Manger -> Download ROM -> Scroll down to Google Apps. It reboots and ends up at the screen with the white triangle around an exclamation and the android icon. I do not get the ClockworkMod menu. I have to press and hold the power button to reboot normally and get back to CM7.
Am I missing the recovery executable file? I looked in /system/bin and /sbin and it is not there. Should I copy the one I used earlier in to /system.bin ?
Thank you.
I believe cwm can show that when it is working, on some builds you can toggle between it showing the files being copied and that screen with the power button if I remember right.
Thanks for the reply, Dani897.
I am trying to get the Google apps installed which I couldn't since the recovery mode isn't showing up.
Any hint how I can get them on?
suryathesun said:
Thanks for the reply, Dani897.
I am trying to get the Google apps installed which I couldn't since the recovery mode isn't showing up.
Any hint how I can get them on?
Click to expand...
Click to collapse
Not really sure, I don't run CM7. But if you are using ROM manager it might just start flashing and never enter the menu.
If it is hanging maybe you can find gapps.zip on xda somewhere and put it on the sd card. Then use the reboot into recovery option instead of the flash ROM option in ROM manager.
Why not install the. Apk's instead of flashing the Google aps
Sent from my SAMSUNG-SGH-I997R using xda premium
Dani897 said:
Not really sure, I don't run CM7. But if you are using ROM manager it might just start flashing and never enter the menu.
If it is hanging maybe you can find gapps.zip on xda somewhere and put it on the sd card. Then use the reboot into recovery option instead of the flash ROM option in ROM manager.
Click to expand...
Click to collapse
Thanks Dani897, didn't realize the reboot has recovery option. Now I have the Gapps installed.
In fact, CWM showed up when I rebooted into recovery mode. Wonder why ROM Manager couldn't do that.
suryathesun said:
Thanks Dani897, didn't realize the reboot has recovery option. Now I have the Gapps installed.
In fact, CWM showed up when I rebooted into recovery mode. Wonder why ROM Manager couldn't do that.
Click to expand...
Click to collapse
If I remember correct ROM manager has several options, 1 is to download and flash roms, 1 is to flash from sd card 1 is to reboot into recovery. if you use the first two options it goes into recovery but not the menu, it skips strait to flashing so you don't needed to do any more work, it only shows the menu if you reboot into recovery.
Sarius24 said:
Why not install the. Apk's instead of flashing the Google aps
Sent from my SAMSUNG-SGH-I997R using xda premium
Click to expand...
Click to collapse
Thanks for the reply Sarius24, I will try that the next time.
Do you happen to know of a reliable source for such apk's?
Dani897 said:
If I remember correct ROM manager has several options, 1 is to download and flash roms, 1 is to flash from sd card 1 is to reboot into recovery. if you use the first two options it goes into recovery but not the menu, it skips strait to flashing so you don't needed to do any more work, it only shows the menu if you reboot into recovery.
Click to expand...
Click to collapse
Good to know that. In fact, I tried the "Download ROM" option which downloaded the Gapps zip and rebooted in to the white triangle screen.
Now moving onto fixing other issues
Thank you.
For all who are having issues with custom recovery not working, rebooting etc. flash the linked file. The issue stems from using reboot to recovery commands in android rather than using vol-,power button combo from power off. In the future, ONLY use the combo.
Major thanks to gee one for the file.
http://www.mediafire.com/?5ih9s5i59xys9zd
Been on various versions of ics for a while now. As I don't use my tf all the time (might go a couple of weeks without touching) i came to update to latest revolver today and every time I reboot it takes me back to cwm. I can cold boot into the system but thats not a good resolution, especially as i am thinking of selling.
Tried wiping system, reflashing and booting from cwm or off.
Sent from my Transformer TF101 using xda premium
Did you use ROM manager to flash CWM? It can cause bootloops.. Try roaches repacked touch thread, he's got a diff of the fix there.
Hmm. Tried flashing roaches touch but it wont stick. Also tried updating to the latest from rom manager but that wont stick either.
I use 4ext recovery on my desire z but the app isnt available from tablets (mine anyway).
I run linux and dont have adb setup. Is there any other way to flash recovery?
Sent from my Transformer TF101 using xda premium
No, what I mean is, use the fix in Roach's thread to fix recovery. Don't just ROM manager, it just doesn't work on the tf101 very well. Use Gnufabio's RecoveryInstaller app (in development) to flash CWM 3.2.0.1 then update to a later if you wish, manually without ROM manager.
^^
Reading your post, if you have no access to android on your tab (you have ubuntu only) then you need to set up adb to fix it. I assume you're running android though.
Your right. I could cold boot to android. After following your aim I landed on a nice little file to flash that wipes the reboot to recovery. The initial issue was worse than I thought. Anything I flashed wouldn't take regardless of what the scrolling text said.
Even though this thread is so short I am going to update the OP with the details for others as it seems quite a common issue.
To summarise, its all fixed.
Sent from my Transformer TF101 using xda premium
The bad thing is .. I can't even cold boot into android ..
As of my knowledge cold-booting is volume-down + power.
This only takes me to recovery again, no matter what I do..
So when you hit the button combo do you see the asus screen with some writing at the top left? Something along the lines of 'press up for recovery or wait 5 secs for other options'.
Sent from my HTC Vision using xda premium
If you can access adb shell from recovery, flash a new recovery using:
su
dd if=/your/blob/here of=/dev/block/mmcblk0p4
reboot
Place the recoveryblob extracted from the CWM flashable zip somewhere on your tf accessible from cwm.
MarkyG82 said:
For all who are having issues with custom recovery not working, rebooting etc. flash the linked file. The issue stems from using reboot to recovery commands in android rather than using vol-,power button combo from power off. In the future, ONLY use the combo.
Major thanks to gee one for the file.
http://www.mediafire.com/?5ih9s5i59xys9zd
Been on various versions of ics for a while now. As I don't use my tf all the time (might go a couple of weeks without touching) i came to update to latest revolver today and every time I reboot it takes me back to cwm. I can cold boot into the system but thats not a good resolution, especially as i am thinking of selling.
Tried wiping system, reflashing and booting from cwm or off.
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Had to use it tonight big thanks..
I have the same problem, after flash a kernel [KERNEL][ICS] Harmony (OC/UV), boot loop on recovery (rogue XM 1.5.0), tried in adb to push a recovery blob, but don't work....
Line error is /sbin/sh: push: not found
The same with the other comand, like: device, /sbin/sh: device: not found
I have tried a flash, new rom, new kernel, new recovery, any trick but nothing!!!
in adb only reboot comand work
Help me please
try the /temp/ folder or somewhere like that, which doesn't need system write permissions, or mount the system as writable. The commands to use after getting the blob on are a few posts up.
I've try this, dd if=/sdcard/blobrecovery of=/dev/block/mmcblk0p4 end adb whrite new recoveryblob, but after reboot won't work, restart anytimes on recovery....
If nothing else works, try NvFlash (in my sig) just released for Sbkv2
I also facing same problem. When i switch on my pad every time going to recovery mod can't go to android. restart anytimes on recovery....
Try a reflash of recovery, if all else fails, Nvflash.
Ok so run into same problem. However I can't get ADB to recognize it, I also can't get it to cold boot. Then lastly I can't get the version on her to see the sd card so I can't even load files onto the tablet to even try running the one script that was on here. Any suggestions from here?
Ok so managed to get it back to cold boot after running a new rom into it. Dunno why that'd work but it did. Gonna keep this file in place permanently. Would still like to see other options if you were in my spot since everything seems to rely on everything I was missing.
Nvflash. Yet again, only true rescue in a really bad brick situation.
MarkyG82 said:
Your right. I could cold boot to android. After following your aim I landed on a nice little file to flash that wipes the reboot to recovery. The initial issue was worse than I thought. Anything I flashed wouldn't take regardless of what the scrolling text said.
Even though this thread is so short I am going to update the OP with the details for others as it seems quite a common issue.
To summarise, its all fixed.
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Hi Marky,
Can you help me how you fix your problem because i also facing same problem.
Minnaing.
Can you cold-boot to android? Volume down + power and wait.
yes, I can go cool-boot to android.with Vol+
TeamApexQ is proud to release TWRP (from our OmniToad builds) for general use.
Current release: 2.8.1.0_0001
Raw image (for heimdall/Crazy 'cat'ing):
https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/apexqtmo_twrp-2.8.1.0_0001.img
md5: https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/apexqtmo_twrp-2.8.1.0_0001.img.md5sum
update.zip format (Recovery flashable/sideloadable):
https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/apexqtmo_twrp-2.8.1.0_0001.zip
md5: https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/apexqtmo_twrp-2.8.1.0_0001.zip.md5sum
ODIN compatible tarball format (ODIN):
https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/apexqtmo_twrp-2.8.1.0_0001.tar.md5
Please let us know of any other issues. Also with any other issues, please include a copy of your recovery.log, and dmesg from the TWRP session.
Thanks for your work TeamApexQ!
Sent from my SGH-T699 using XDA Premium 4 mobile app
falle21 said:
Thanks for your work TeamApexQ!
Sent from my SGH-T699 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nice...Will be building some twrp themes just for the Relay 4G....glad you guys built it as ive been pretty busy
The work around for the "failed" flash. Unmount system in the "mount" menu prior to doing any flashing of zips. Even I have to do this on the G2 with TWRP 2.6.3.4.
Sent from my LG-VS980 using Tapatalk 4
New build posted in the OP!
Will now flash old Android builds (I've tested with every build I could get my hands on.)
I've never used TWRP, how does it differ from CWM for Backups ?
Are my CWM "nandroid" backups cross compatible ? I have Carbon, Omni and CM11 backups ready to switch at any time for testing in .tar format.
No twrp backups differ from cwm...however Philz can handle twrp and cwm backups...however and in my opinion twrp can do a lot more as a recovery than any other recovery...one thing you can do...and is a slight pain...is boot the backup with cwm or philz. flash twrp and re backup that ROM in twrp then delete the old one...repeat for all backups
Sent from my ADR6425LVW using xda app-developers app
REV3NT3CH said:
No twrp backups differ from cwm...however Philz can handle twrp and cwm backups...however and in my opinion twrp can do a lot more as a recovery than any other recovery...one thing you can do...and is a slight pain...is boot the backup with cwm or philz. flash twrp and re backup that ROM in twrp then delete the old one...repeat for all backups
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
hmm yea ... or switch between recoveries restore w/ cwm, install twp, reboot re-create backup .. repeat.
Is there a fix permissions in twrp ? and is usb mounting in windows ? I found I didn't have the functionality of either with the latest CWM
yohan4ws said:
hmm yea ... or switch between recoveries restore w/ cwm, install twp, reboot re-create backup .. repeat.
Is there a fix permissions in twrp ? and is usb mounting in windows ? I found I didn't have the functionality of either with the latest CWM
Click to expand...
Click to collapse
thats what i was refferring too for saving your backups and restorable via twrp....and yes to all the other questions...twrp can do so many things while in recovery...for example..say you downloaded a rom from phone and forgot to put it in root of sdcard...twrp has a file manager with copy and paste functionalities to do so...it supports adb sideloading, mounting for both windows and linux, permissions, much better and clearer wiping method...all touchscreen...very themable for example http://forum.xda-developers.com/showpost.php?p=45122951&postcount=1 i made this theme specifically for my htc rezound as well as many others...which ill more than likely port to the relay as it has to match screen dimensions for resolution...overall it just has a bulk of many great options for a recovery and is very easy to use and get used to
New build posted in the OP. Small bugfixes in this release. (Including some SELinux and settings fixes.)
Did something wrong. How to fix?
Magamo said:
TeamApexQ is proud to release TWRP (from our OmniToad builds) for general use.
Current release: 2.7.0.0_0002
Raw image (for heimdall/Crazy 'cat'ing):
https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/apexqtmo_twrp-2.7.0.0_0002.img
Click to expand...
Click to collapse
I wanted to install this version of twrp on my apexqtmo using heimdall under linux.
I booted into "download" mode, connected my USB table to my linux box, and I then stupidly flashed the wrong twrp module by mistake (for a different phone).
Without realizing my mistake, I then rebooted. I ended up back in my OS, and then, using the Power Menu, I booted into recovery mode. I got the blue text saying RECOVERY BOOTING.... , but after that, the screen remained black.
From then on, I cannot boot into the normal OS, nor into "download" mode.
Even if I remove the battery and then perform a standard boot using the power button alone, I get the blue text saying I'm booting into recovery, and the dead, black screen shows up.
I want to boot into the OS or download mode, but I can no longer do either. No matter what combinations of Volume-Up, Volume-Down, Home, and Power that I press, I always get back to RECOVERY BOOTING...., and I can't get into download mode again, no matter what.
Did I brick my phone?
If not what can i do to fix it?
Thanks for any help.
.
The only way to clear the reboot mode is to either trigger a different mode or complete the boot. If key combinations don't work, you can try to see if the device comes up in adb and then you can "reboot bootloader" failing that you can trigger download mode with a resistor on the usb port. Google galaxy s 3 jig to find out how to make one or buy one
Sent from my Nexus 7 using Tapatalk
Nardholio said:
The only way to clear the reboot mode is to either trigger a different mode or complete the boot. If key combinations don't work, you can try to see if the device comes up in adb and then you can "reboot bootloader" failing that you can trigger download mode with a resistor on the usb port. Google galaxy s 3 jig to find out how to make one or buy one
Click to expand...
Click to collapse
Thank you very much!
... and I fixed it!!!!
Your adb suggestion led me to the solution ...
I tried adb, but it didn't work.
However, after that adb attempt, the usb cable was still plugged into my device from my linux box, and I noticed that the device was in some sort of boot loop. The device kept giving short vibrations every few seconds.
At that point, I tried one more key combination that I hadn't thought of before: with the cable still plugged in, I held down Volume-down and Home without pressing the Power button ... because I guessed that the existence of the boot loop means that power might already be on, which would cause the power key to be unnecessary.
And my guess was correct: I got into Download mode!
I flashed the correct version of TWRP, and now all is well.
Thank you again for providing the suggestion that led me to my solution!
Also, thank you for telling me about the jig. I'm now going purchase one anyway, just in case I screw up again in the future. I think I can get one for $8 or less (I'm too lazy and clumsy to try to make one on my own).
.
It's weird, but I had the same experience with the blue "RECOVERY BOOTING" followed by dead phone as described a couple posts ago... and I was flashing the correct file, the twrp zip in the OP, from recovery (cwm 6.0.3.7). I did it twice and got the same bad result.
To get around the bad dead phone result, I held volume down and power for 15 seconds, got into download mode, and then selected volume down to allow the phone to boot normally. Once it did, I went to the Play store and installed an app that could flash another recovery (cwm 6.0.4.5). Which worked.
I will try flashing the .img file and see if that works, but I'm kinda perplexed why the twrp zip didn't work from recovery...
Sent from my Nexus 5 using Tapatalk
reaper000 said:
I will try flashing the .img file and see if that works, but I'm kinda perplexed why the twrp zip didn't work from recovery...
Click to expand...
Click to collapse
You indeed have to flash the .img file, at least if you're installing from the command line using heimdall.
.
Ended up successfully flashing the .img file with recovery tools app from play store. Thanks all!
Sent from my Nexus 5 using Tapatalk
reaper000 said:
Ended up successfully flashing the .img file with recovery tools app from play store. Thanks all!
Click to expand...
Click to collapse
Glad it worked.
Also, FYI: you can't flash a recovery from within recovery. This is why your earlier attempt to flash the .zip from within recovery didn't work.
As far as I know, you have to be in bootloader mode (also called "download" mode) in order to flash a recovery. You have to boot into that mode and use somthing like heimdall to install the .img file. There are also tools you can use which will flash a recovery from a .zip file, but they actually just extract the .img file from the .zip file and then load that .img file via bootloader mode.
.
HippoMan said:
Glad it worked.
Also, FYI: you can't flash a recovery from within recovery. This is why your earlier attempt to flash the .zip from within recovery didn't work.
As far as I know, you have to be in bootloader mode (also called "download" mode) in order to flash a recovery. You have to boot into that mode and use somthing like heimdall to install the .img file. There are also tools you can use which will flash a recovery from a .zip file, but they actually just extract the .img file from the .zip file and then load that .img file via bootloader mode.
.
Click to expand...
Click to collapse
The .zip file provided here CAN be flashed from within recovery. What likely happened was a bad download.
Magamo said:
The .zip file provided here CAN be flashed from within recovery. What likely happened was a bad download.
Click to expand...
Click to collapse
Yeah, was thinking bad download, but I dl'd it twice. And there was no MD5 checksum that I could see
Sent from my Nexus 5 using Tapatalk
reaper000 said:
Yeah, was thinking bad download, but I dl'd it twice. And there was no MD5 checksum that I could see
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Actually, which version of CWM were you using to attempt to install this from? Likely significantly old versions were not set up to flash recovery properly.