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] Bricked Xoom?

So im running 3.1 rooted with the 1.4.4 Tiamat Kernel. I had this weird force closing issue where gapps would force close whenever i tried to connect to wifi. I powered down, turned on, and am now stuck in a boot animation loop. I can hold down the Vol Down button and it says "Starting Fastboot Protocol Support." but nothing changes. Is there anything I can do it fix it/turn it off until i get home to my computer with the SDK? On another note I did install the wpa supplicant (sp?) files to allow it to connect to an adhoc wifi source (eris tether). Please and thank you
EDIT: I have booted into recovery, but I am unable to mount any of the drive locations or wipe them. I did a factory data reset (as much as it could I guess?), but im still at the boot loop.

Hook it up to computer while its in fastboot and open a command prompt from the folder you have fastboot. Type "fastboot reboot-bootloader" and you should get adb to recognize, then push stock images or root images and recovery.
What recovery were you using? Did you flash the one from ROM manager?

I am using the CM from the ROM manager the latest one I think that it is version 4 something. does this make a difference? I have backups from my previous flash but when I tried to recover it won't take them. where can I get the root image? I might have it already since I rooted using adb, I will have to look on my laptop when I get home. Any other info you have will help. Thank you,,,,

razor532 said:
I am using the CM from the ROM manager the latest one I think that it is version 4 something. does this make a difference? I have backups from my previous flash but when I tried to recover it won't take them. where can I get the root image? I might have it already since I rooted using adb, I will have to look on my laptop when I get home. Any other info you have will help. Thank you,,,,
Click to expand...
Click to collapse
You will need to flash a good recovery, I suggest you you use the .img file in this thread through adb when you get to your laptop:
http://forum.xda-developers.com/showthread.php?t=1074979
The recovery version you updated to won't look at your external sdcard, so you can't flash from it until you re-install a good recovery.
Can't we get a pinned warning about this issue?

Thanks everyone, sorry for the delay. I ended up fixing it with a fastboot oem unlock command. However after countless flashes unable to get it to boot again i realized i was flashing the tiamat rom and then a different tiamat kernel boot.img, most likely the culprit in my boot loop. The minute i did a factory reset, updated cwr and only flashed the rom, everything works fine. Thanks for everyones help
Sent from my Eris using XDA App

So glad you were able to fix it!

[Q] I have a blank device need some help

So in clockworkmod I formatted boot, cache, system, and data. Sometimes I do this when having problems changing roms. Well this time I have a problem, the one and only rom on my phone is Bionix and it will not install. Now my phone will not connect to my computer. If I restart the phone it goes straight to the bootloader and says no boot or recovery image. I can scroll down to recovery and it will go to CWM 5 but I have no roms in there to flash other than Bionix. The computer will not recognize the phone in either fastboot or recovery so I have no idea what the heck to do to get this thing running again. Any help would be greatly appreciated.

you can try going into CWM go to scroll to advanced then mounts and storage..then mount sd...connect phone to pc...n transfer rom to phone...u should b able to flash the rom then
Sent from my Nexus S 4G using XDA Premium App

neo_x22000 said:
you can try going into CWM go to scroll to advanced then mounts and storage..then mount sd...connect phone to pc...n transfer rom to phone...u should b able to flash the rom then
Sent from my Nexus S 4G using XDA Premium App
Click to expand...
Click to collapse
Tried that. I'm going to pick up a new usb cord tonight at Best Buy and maybe that will get it.

maybe u can try reflashing recovery via fastboot then use mounts and storage and see if that will work..

If you can go in CWM then you're far from bricked, haha.
As neo_x22000 said
1) Go to Clockworkmod Recovery
2) Mounts and storage menu
3) Mount /sdcard
4) Mount USB storage
5) Plug phone to computer
6) ????
7) PROFIT!!!!

Got it working. The problem was the USB cord. Now running ICS! Thanks for all the help.
Sent from my LG-VM670 using XDA App

[Q] asus transformer sort semi brick need help asap please...

ok so ive had my tf101 rooted since i got the thing over a year and a half ago, i was running the megatron rom which was cm9 based and everything was good. today i tried to flash Eos4 and i got F%$ked out the a$$. so i did my standard procedure which was put the rom and gapps package on my device and then i wiped everything (after making a nandroid) and flash the rom along with its gapps. then i went to reboot it then i got shot back into recovery...so i was like wtf. i then found a way where if i hold the power and volume down for about 10 seconds i could cold boot android and once booted fix this problem with my recovery. unfortunately when i go to boot into android my device just bootloops on the boot animation ( ive left for about ten mins just to make sure) then i was like oh well ill just restore my nandroid, but for some reason clockwork mod touch wont let me use my microsd card, and its also not letting me restore from the backup i made earlier, it says files not found. i tried to connect it to my pc so i could just factory reflash it but unfortunately it will not be picked up by my pc through adb or apx.
so here is my main issue,
i just need to boot into android one time successfully so i can change the location of some ROM files and fix this stupid recovery bull****.
or if i could some how factory reset the tablet completely then that would be fine too
or or i could flash a different recovery that actually worked (currently on CWM 5.8.3.4 installed from rom manager which i realize now to be a huge mistake)
and i've tried ever tool on this forum as well and nothing works because it cannot pick up my device.
*** one other side note i am running windows 8 pro 32bit through Vmware (if this can be problematic)
thanks for any help in advance

To fix this, you will need to get your tablet recognized by your computer via ADB (in recovery) or APX mode.
You could have a bad cable, or it could be the VM causing the detection issues.
Is there a way you can connect it to a computer running Windows natively?
Does your computer make the new hardware sound when connecting?
Once you get it detected via one method or the other, here are my suggestions:
APX - Use the Naked Driver 0.72 and replace whatever driver is being used. Then use EasyFlasher to install TWRP 2.2.1.4 (it blows CWM away, and can read internal AND external memory)
ADB - use the Naked Driver 0.72 and replace whatever driver is being used. Then download the TWRP 2.3.2.3 blob from the TWRP project: http://techerrata.com/browse/twrp2/tf101
Call the downloaded file TWRP.blob.
Then run the following from your computer via ADB:
Code:
adb push TWRP.blob /sdcard/
adb shell
su
dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4
reboot
Make sure it is a normal reboot to complete the recovery. Then reboot to recovery and you should be able to see the external card (so long as it is formatted for FAT32).

Thanks for the quick response and it probably is because I am using vmware... Unfortunately I don't have access to a windows machine right now. But I will definitely try to find one
Sent from my SAMSUNG-SGH-I747 using xda premium

Ok so now it looks like this... All i did was flash some random ass jb rom I found in my cwm folder... It has been like this for about 15 mins
Sent from my SAMSUNG-SGH-I747 using xda premium
** edit I'm assuming it got stuck boot the apps because now a my directories seem F&#cked up too... It now goes sdcard/0/0/0/(everthing else)

That's because your recovery is not compatible with 4.2.1. TWRP recovery 2.3.2.3 or 2.3.3.x should be fine as federuco said, to fix the sdcard/0/0/... issue.
For the stuck at apps thing, usually it's because you didn't wipe everything when changing rom. Make sure to do a full reset, wipe cache dalvik and system.

Lethe6 said:
That's because your recovery is not compatible with 4.2.1. TWRP recovery 2.3.2.3 or 2.3.3.x should be fine as federuco said, to fix the sdcard/0/0/... issue.
For the stuck at apps thing, usually it's because you didn't wipe everything when changing rom. Make sure to do a full reset, wipe cache dalvik and system.
Click to expand...
Click to collapse
But my problem is I can't flash another recovery... I can't access the memory on my micro sd card... So like idk what to do
Sent from my SAMSUNG-SGH-I747 using xda premium

What happens if you reboot it after it is at the starting apps screen?
If you can get into the OS, install GooManager and install TWRP.

frederuco said:
What happens if you reboot it after it is at the starting apps screen?
If you can get into the OS, install GooManager and install TWRP.
Click to expand...
Click to collapse
I can't get into the os that's the problem... I just clean installed Windows via boot camp on my mac... Gunna try a few tools now... Hopefully I can get it back to stock... I'll update in a little bit
Sent from my SAMSUNG-SGH-I747 using xda premium

Ok so my computer can sort of detect it... I installed the drivers via brks root kit but when I plug it in in apx mode it says unknown device... Tried all my programs and they all failed...
Sent from my SAMSUNG-SGH-I747 using xda premium

Ok so I've tried to to reinstall the drivers... Tried to flash everything in apx and adb but it's not being properly detected By the PC... So I have no idea what to do at this point... If I could somehow either boot into android or flash TWRP
Sent from my SAMSUNG-SGH-I747 using xda premium

Use the Naked Drivers.
Let me find the link to the thread....
Here you go: http://forum.xda-developers.com/showthread.php?t=1514942
Grab the driver pack in the first thread, update the device using the APX driver when in APX mode.
Then you should be good to go. I have used EasyFlasher via APX with great success.

frederuco said:
Use the Naked Drivers.
Let me find the link to the thread....
Here you go: http://forum.xda-developers.com/showthread.php?t=1514942
Grab the driver pack in the first thread, update the device using the APX driver when in APX mode.
Then you should be good to go. I have used EasyFlasher via APX with great success.
Click to expand...
Click to collapse
Not to sound like a complete noob at this point but idk how to install these naked drivers
Sent from my SAMSUNG-SGH-I747 using xda premium

I think I installed the drivers right but idk can someone please like teamviwer or Google + hangout with me
Sent from my SAMSUNG-SGH-I747 using xda premium

Put your device in APX mode. To do so, make sure it's completely powered off (hold the power button 10 seconds), then hold down volume up + power for about 5 seconds. Do that while it's connected through USB. The screen will remain black so you won't see anything on the device, but you will hear a new device found in windows. Go in your device manager and look for either "unkown device" or "NVIDIA boot-recovery driver for mobile devices". If you see the nvidia one, right click and delete it; it should be come unknown. Right click the unknown device, install driver... navigate to where you extracted the naked drivers, and install.
Then use easyflasher.

Lethe6 said:
Put your device in APX mode. To do so, make sure it's completely powered off (hold the power button 10 seconds), then hold down volume up + power for about 5 seconds. Do that while it's connected through USB. The screen will remain black so you won't see anything on the device, but you will hear a new device found in windows. Go in your device manager and look for either "unkown device" or "NVIDIA boot-recovery driver for mobile devices". If you see the nvidia one, right click and delete it; it should be come unknown. Right click the unknown device, install driver... navigate to where you extracted the naked drivers, and install.
Then use easyflasher.
Click to expand...
Click to collapse
Not working... :/ I swear it's not me
Sent from my SAMSUNG-SGH-I747 using xda premium

Bricked TF700? Not able to enter recovery

I did something stupid. I pulled the micro SD-card in frustration and used it for something else. A 500$ black screen won't do much, so I figured I would get it running again.
I was running CROMBI(?) with Data2SD. Now - of course - the tablet won't boot. It boots straight into the Android "guy" and a progress bar. I can't enter recovery.
Connecting the tablet to a PC, gives me a APX device (no driver). I tried installing it with the ADB driver, and it says "recovery" while using the "adb devices" command. I can't however flash a new recovery using fastboot.
Is there anything I can do to install a new recovery (TRWP/CWM) and a new rom?
Is it bricked? (Will someone buy it? )

Slekvak said:
I did something stupid. I pulled the micro SD-card in frustration and used it for something else. A 500$ black screen won't do much, so I figured I would get it running again.
I was running CROMBI(?) with Data2SD. Now - of course - the tablet won't boot. It boots straight into the Android "guy" and a progress bar.
Click to expand...
Click to collapse
Did you wait for it to finish whatever it's trying to do? How long? Anything under 2 hours doesn't count. Connect it to power though....
I tried installing it with the ADB driver, and it says "recovery" while using the "adb devices" command.
Click to expand...
Click to collapse
Just "recovery" or preceded by letters/numbers?
I can't however flash a new recovery using fastboot.
Click to expand...
Click to collapse
Why? Because you cannot enter the bootloader? Did you wipe data from there?
Is it bricked?
Click to expand...
Click to collapse
Not yet, but you have to give us more details...

Slekvak said:
I did something stupid. I pulled the micro SD-card in frustration and used it for something else. A 500$ black screen won't do much, so I figured I would get it running again.
I was running CROMBI(?) with Data2SD. Now - of course - the tablet won't boot. It boots straight into the Android "guy" and a progress bar. I can't enter recovery.
Connecting the tablet to a PC, gives me a APX device (no driver). I tried installing it with the ADB driver, and it says "recovery" while using the "adb devices" command. I can't however flash a new recovery using fastboot.
Is there anything I can do to install a new recovery (TRWP/CWM) and a new rom?
Is it bricked? (Will someone buy it? )
Click to expand...
Click to collapse
Your external SD may be corrupted. You should be able to boot your device into your internal /data. So you need to force your device to reboot and quickly remove your external SD. Your device should boot into your internal /data and ask you to setup your device again, good luck... Never pull out your external SD if you are running Data2SD because it will corrupt your /data partition....