Database Info

-SOLVED- [Q] Trying to root, but can't boot into CWM...can anyone help?

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?

[Q] failure after root and tried to recovery

Hi there I have a Nexus S with 4.04 on it, so the other day I followed the instruction online and tried to root the phone, I have phone driver installed, and able to unlock my bootloader, the LOCK STATE is UNLOCKED. and I was able to flash Clockworkmod recovery v5.0.2.0.
But after this step, and I tried to reboot, my phone just stuck at the google logo with the unlock sign at the bottom, and wouldn't do anything afterward. (seems like a root loop?)
I tried pulling off the batt a few times but no good. I am still able to lock and unlock bootloader through cmd.(just like in normal state)
I tried to install factory img as shown in the thread http://forum.xda-developers.com/showthread.php?t=1572307. but when I type in the first line "adb reboot bootloader", it says adb devices not found.
so, any idea on how I can restore back to the factory img?
bootloader version i9020xxkl1
model GT-i9020T or if any more info is needed I will be here.....>.<

Did you correctly installed the recovery?
Hi.
First at all let me tell you that I'm not an expert. So, I understand that you should double check this.
I think that you should try to:
- If you have successfully installed the ClockworkMod recovery, you should turn on the device on recovery mode. Vol up + on pushbutton to go inside bootloader. Going down with Vol down, go to recovery and select with on pushbutton.
- Download the correct superuser app for your version. I would double check the md5sum of the file that you have downloaded on your computer.
- Mounting the usb storage of the device on your computer, add the superuser app on /sdcard.
- Umount the usb storage.
- Flash the superuser app, installing from /sdcard from your recovery menu.
- Download a custom kernel on your computer, once that you are unlocked. I'm using CyberGR, and I'm happy with it. You can see all the intallation instructions in the Nexus S development part.
- I that works, I would try to install the kernel in a clear way. For installing the CyberGR ROM, you need to wipe everything and format all. After that, you mount the device on the computer, and try the installation.
Then, if everything is ok, the device will turn on.
Again, I'm not an expert, and I don't know how you can be in contact with the developers that are posting in the developers area. I'm not responsible if your device doesn't works or get bricked.
However, I understand that all that I have described, should not put your device in a worst situation.
And is it doesn't turn on, if it doesn't do anything, then, you can use the linux tooll for bicked devices explained on the developers area.

[Q] Factory Reset using TWRP now it asks for encypted password upon boot

I just got my new S5, so it was time to nuke my S3 to get it ready for sale. My S3 is running 4.1.2 rooted with an unlocked bootloader and TWRP 2.5.0.0. To ensure a better wipe I encrypted the device and then did a factory reset. Now upon booting back up, I get a screen that reads: Enter password to access encrypted device storage. So I entered my password and it won't accept it. I cancel out of it, nothing works - I'm stuck.
I'm trying to reset the phone back to 4.1.2 and have no idea what I need to do next. Any help appreciated.

If no one knows how to fix this is there a way using TWRP or something other method to flash my S3 back to stock 4.1.2?

I looked at your thread earlier and I was wondering how to do it myself. Since your on an unlocked bootloader you can flash it back to another version, however I'm not sure if because having encryption enable it will let you
From my CM11 S3

SOLVED!
This Wonderful Guide from droidstyle helped me out.
1. I already had the USB drivers installed so I skipped to Section 5: How to Odin back to Stock from any rom/recover from a soft brick/flash a stock radio.
2. Downloaded the appropriate stock firmware, in my case it was VRALG1 4.0 ICS since I was on 4.1.2 and was not unfortunate enough to use any OTAs (4.3 and up) which permanently locked the bootloader.
3. Power on phone to Download mode (Hold Power on, Volume down and Home key at the same time). Make sure Binary Flash Counter is set to NO. Press Volume Up to select download mode.
4. Connect phone to computer and follow the steps on using ODIN to flash the stock image.
Phone reboots, wait and then viola - it booted just fine and asked me to set up the phone. Just to play it safe I rebooted to stock recovery, wiped cache and did a hard reset.
Now I will unlock and root the phone and then it's ready for sale. :good:
BTW I tried to find a stock 4.1.2 rooted and unlocked image but couldn't. If I find it I will flash it.

After rooting my nexus 5 is not booting up with non stop booting animation

I have a nexus 5 16 GB and i downloaded the recent software update android 6.0.1 and then I decided to root and I used 'Nexus root toolkit v2.06' and first unlocked the bootloader and then rooted. Everything worked fine but after the process was complete it was rebooting and the booting animation went on and on for many hours and the device did not root. I really don't know what's going on. My purpose is to install a custom rom: cyanogenmod 12. Now what should I do ???? PLEASE HELP. When i try to enter recovery mode it shows a picture of the android mascot with opened back and exclamation and cannot enter command as well. and after some time the booting animation begins and goes on and on...
please help...

nexus_5_ said:
I have a nexus 5 16 GB and i downloaded the recent software update android 6.0.1 and then I decided to root and I used 'Nexus root toolkit v2.06' and first unlocked the bootloader and then rooted. Everything worked fine but after the process was complete it was rebooting and the booting animation went on and on for many hours and the device did not root. I really don't know what's going on. My purpose is to install a custom rom: cyanogenmod 12. Now what should I do ???? PLEASE HELP. When i try to enter recovery mode it shows a picture of the android mascot with opened back and exclamation and cannot enter command as well. and after some time the booting animation begins and goes on and on...
please help...
Click to expand...
Click to collapse
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally

funnel71 said:
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally
Click to expand...
Click to collapse
Thank you very much for the reply, I really do have no idea as to how to flash the factory image because i am very new in this area. Could you please recommend software and which factory image i should download, please ?? thanks very much.
:good:

funnel71 said:
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally
Click to expand...
Click to collapse
Also, you mentioned a 'special kernel' what does that mean. All i want to do to my device is install cyanogenmod 12 and for that i believe it needs to be rooted, so i am really confused. What should I do know

I'm having this same problem, and unfortunately, when I start the phone on fastboot, I can not access the recovery mode in order to upload a factory image of nexus 5.
I used the new tool available her for quick flash, and now, I don't have a phone.

First, don't panic. Your phone is still very easy to recover. Unfortunately I can't get you a complete walkthrough here (for now at least), so I'll give you the main idea and you'll have to do your homework (as maybe you should have done before).
1. You need to get fastboot working on your computer. It's included in the Android sdk package, but there might be some easier way to get it. Google it. You might need drivers for your pc too. Google it as well.
2. Then you need to get into fastboot mode on your phone. To do it, hold down power button AND volume down button until it gets into fastboot mode. You will see an android on his back with the cover open. At this point, connect your phone to your pc, open a terminal on your pc and type "fastboot devices" without the quotes "". It should find your phone if fastboot is working. If it doesn't work go back to step 1.
3. Download TWRP recovery on your pc and place the img file in the same folder as your fastboot executable (not mandatory but easier). It can be found here https://dl.twrp.me/hammerhead/
4. Always in fastboot mode, type "fastboot flash recovery twrp-2.8.7.1-hammerhead.img" assuming you downloaded that file, which you should have by the way. It should install fine. If you haven't placed the file in the same directory as your fastboot executable, you will need to provide the path to your img file as well.
5. Then use the volume rocker to switch between modes and choose reboot recovery.
6. You should now be in TWRP recovery. At this point, download a custom kernel (anyone found on xda for hammerhead should do) and push it to your phone. It should be fairly simple with TWRP. Then flash your new kernel using install. It should help you get your phone booting normally. Alternatively, you can download a custom ROM like cm12.1 and flash it altogether. It will install everything needed for your phone to boot up too. Beware if flashing a ROM though, I strongly advice you to do a factory reset before flashing it. You will find that option in the wipe menu.
Hope it helps, let me know if you need further assistance.

Yesterday, I have tried everything to have my computer to recognize the "fastboot" command, and I installed like 2 or 3 different programs for that. With my old Windows 7, I have been able to push a flashed image to fix this issue, using the fastboot command, but with Windows 10, it's always telling me it's not a valid command. I'll keep trying it, otherwise, i'll have to "resurrect" my old Windows XP computer.
Also, I noticed now that, while trying to install the fastboot, as per some files that I could download, but no file has been copied into my computer, not even if I run it as admin.

fixed. but no RECOVERY mode options....
Hi Guys,
Thank you very much for the help, I have finally recovered the phone and running android 6.0 MRA58N but it is not rooted. Now if you don't mind could you teach me how to root because i have checked lots of videos and tuts but none worked for me...
IMPORTANT:
when i am in recovery mode why cannot I access options even when i press volume up + power button and release them at the same time...????
Thanks in advance.

Just flash a custom recovery via fastboot. Just make sure your bootloader is unlocked. Can't link though.

hi guys i have used nexus 5 mobile with cyanogenmod 14.1 .It worked properly in 1 year. after that suddenly switched off and it not properly boot up .i try to switch on my mobile , first it show google with unlock logo properly and when it show cyanogenmod logo it stuck and again show google with unlock logo....i try recovery mode to wipe and flash the same rom ....the process is interrupt at middle stage and again show the google..i try lots of time . after few try that process finished completely without interrupt. then use my mobile 1 day same as i used first time root. after that same problem occur on my mobile ..so help me guys

@[email protected], possible power button problem?

Nexus 5 (stock) stuck on Google logo screen

Hallo everyone,
since yesterday my Nexus 5 (with Android 6.0.1 stock without any root) doen't won't start anymore, he just stay freezed on the Google Logo screen.
I have been trying to go on the standard recovery mode and wipe the chace partiton, but I get the error message "E: failed to mount /cache (Invalid argument)".
Before trying a wipe data/factory reset, I would save the files from my Nexus in my computer. Sadly when I connect the Phone to the PC (Win7) the device doen't appear in the x: devices list, tought I can hear the sound of new connected device and see it on the Windows Device Manager (under Android Device->Android Bootloader Interface).
How I could save my files now? and then if I succed, should I simply do the wipe data/factory reset? or there's an alternative?

Install TWRP whit **** program http://www.wugfresh.com/nrt/
Make sure you are in bootloader
Launch > custom recovery

Kcetin20 said:
Install TWRP whit **** program http://www.wugfresh.com/nrt/
Make sure you are in bootloader
Launch > custom recovery
Click to expand...
Click to collapse
The guys phone is stock. Unlocking the bootloader will wipe the data, he is trying to save.
---------- Post added at 07:38 PM ---------- Previous post was at 07:35 PM ----------
If I were you I'd take the easy way. Use Wugfreshes toolkit to back up. It will talk you though installing drivers etc and backup your data.

Sadly Wugfreshes toolkit doen't work, here's what I have done:
Started the Device with Power Button and Vol- together
then as It shows the recovery interface I connect the usb cable to my computer
the device has been detected as "Android Device->Android Bootloader Interface" in Device Manager.
I open the Wugfreshes toolkit an I select my device name and android version, the I try to create a backup.
When I do this the device reset itself and goes back to the Google Logo, that as usual is stuck. After a few minutes the toolkit gives an error message.
I'm really frustrated, I hope that someone could help me.
EDIT:
I have been trying to select on the main Rootkit page the option "Current Statuts: Soft-bricked/Bootloop", but the same problem appears again.

I have lost my patience and I tryed to full wipe...and even this doens't work!
After the reboot comes again the Bootloop.
EDIT:
I have been trying the guide to unlock the bootloader (in order to flash the a stock image), but I'm stuck again with this damn bootloop, here the post about it.

When you unlock the bootloader using fastboot commands, does the bootloader relock when you reboot into fastboot?
If the bootloader remains unlocked after rebooting into fastboot, flash the userdata.img that from a stock ROM that matches the currently installed ROM, immediately boot into recovery after flashing, and perform a factory wipe.

Here's my answer in the other thread.
We have ascertained with audit, that my Nexus 5 got problems with the Memory Chip, seems that the only solution now is contact the reseller and change the motherboard/whole phone.