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?
Hey everyone im trying to unroot my transformer.I instaleed repacked-8.2.3.13_US+root-CWR-update.zip.Rebooted it and then i shut it back down.I then booted into clockword mod and installed this recovery 8239usrecovery zip.After that i wiped cache,data and system.I rebooted and now im stuck on the eeepad asus boot screen.When i try to go into recovery i get the triangle.Is there anything i can do?Or did i brick my transformer by formatting the system?Please some one help.
never delete system as it is what has all of the stock apps and framework and library. So it will not boot. The stock firmware will NOT install if you do not have everything in system perfectly. If possible try to use NVFlash to get back to a stable rom if not i don't know if there is anything you can do.
enviidisnut said:
After that i wiped cache,data and system.I rebooted and now im stuck on the eeepad asus boot screen.
Click to expand...
Click to collapse
Don't do **** if you don't know what you're doing or you don't have the full instructions in front of you...
What you've done is the following equivalent in any PC or laptop:
Start PC/Laptop with LiveCD/RescueCD
Format C: (or /dev/sda)
Try to start PC/Laptop
Start to ROFL!
You were supposed to flash the stock rom from asus before flashing the recovery.
Try downloading the rom from asus, unizziping it and placing it on your microSd card and see if theres a prompt to update the rom when you attempt to go into recovery.
Als you could try wiping it again.
Boot while holding the volume down button, When the text shows up don't press anything, wait and you'll get two images show up. Press volume down highlight select wipe cache, the volume up to confirm.
See if that works.
Thanks i will try that now.
Hello XDA community !
LAst week I bought my Acer A700, but after a few days a dead pixel appeared...
So I was on my way to send back my toy, when I saw that CMWR was available.
"Nice ! I can do a factory reset so my toy will be clean to be sent back !"
But the factory reset didn't work... It was stuck at "Formatting /data" for a while...
So I rebooted the A700, and now it's stuck at the ACER logo... I only have access to recovery...
Any ideas ?
Thanks a lot :good:
Since you have recovery try and do data wipe, then wipe cache then davlik cache, then reboot.
If you have recovery you can install a ROM by renaming it update.zip and using CWM.
Itchiee said:
Since you have recovery try and do data wipe, then wipe cache then davlik cache, then reboot.
If you have recovery you can install a ROM by renaming it update.zip and using CWM.
Click to expand...
Click to collapse
I already tried this, when I want to install a update.zip, it stucks at "installing update".
When I want to wipe a partition, it stucks at "formating /xxx" and nothing happens...
I wanted to flash stock bootloader with Nvflash, but I can't find APX drivers for ACER A700
Can you install the update.zip without the use of CWM (By pressing the powerbutton with the vol down)?
Also, where is your update.zip located?
Edit:
I guess it could do no harm if you'd hook up your device to the PC and enter the following commands:
adb reboot bootloader
fastboot erase cache
Click to expand...
Click to collapse
TomONeill said:
Can you install the update.zip without the use of CWM (By pressing the powerbutton with the vol down)?
Also, where is your update.zip located?
Edit:
I guess it could do no harm if you'd hook up your device to the PC and enter the following commands:
Click to expand...
Click to collapse
_ update.zip putted on a extrenal SD card doesn't work, it's skipped and CWM is launched.
_ the "adb reboot bootloader" puts the A700 in "APX" mode... and the "fastboot erase cache" is stuck at "waiting for device"...
Thanks for trying to help !!!
May this be a relevant solution??
http://androidforums.com/esteem-all...w-get-out-clockworkmod-recovery-bootloop.html
Edit:
I don't think the device checks for update.zip on the sdcard. Maybe there is a way to move the file to the internal. (adb mount sdcard adb push /sdcard/update.zip update.zip ?
Yeah,
The current CWM seems to corrupt the Data partition (amongst other things). Seems to be a going thing lately. Remember, these are new tabs, and new root & recovery methods, so there are going to be some bricked tabs before things get sorted out. This happens in "ALL" development, and everybody knows the risks involved.
I had the same issue. Couldn't reboot into fastboot, as it seems the OS has to be running?
This is why Skirlax_CZ built the bootloader for the 500/501, so you could boot it into fastboot mode, bypassing the OS. Unfortunately, the stock 70x OEM bootloader doesn't seem to allow this.
Best bet if you can't find the "exact" version rom the tab was shipped with, is to try renaming some full roms to update.zip, copy to sd, reboot (vol + and PWR, and see if it will install and boot. At the worst, it will install a stock bootloader and recovery.
Also, holding PWR, Vol - (I believe) and toggling the rotation lock should wipe User Data.
At the very worse, turn it into Acer Service, suck it up and pay the repair bill.
They will just install the correct service rom and give it back to you.
MD
Touns said:
Hello XDA community !
LAst week I bought my Acer A700, but after a few days a dead pixel appeared...
So I was on my way to send back my toy, when I saw that CMWR was available.
"Nice ! I can do a factory reset so my toy will be clean to be sent back !"
But the factory reset didn't work... It was stuck at "Formatting /data" for a while...
So I rebooted the A700, and now it's stuck at the ACER logo... I only have access to recovery...
Any ideas ?
Thanks a lot :good:
Click to expand...
Click to collapse
your situation is just same as mine,seeming bricked after using fatory rest or wiping from cwm,I think it's the problem of the damn cwm.as i know from now there are several devices got bricked,all because of the goddamn cwm.as we know factory rest is the same as recovery wiping,i use the under the official recovery,everything wen fine,but after wiping via cwm from the forum,it appeared the problem.
i tried a lot of method,just as u mentioned,to flash *.img
but i found a curious thing,after dumping series of *.img from a well-mailfuntioning device i can use fastboot to flash "userdata" which the loaction is mmcblk010 or /dev/block/platform/sdhci-tegra.3/by-name/UDA,but after flashing,i can't erase userdata block in fastboot.then i reflashing the data.img to userdata block,then in cwm,i can mount /data,but it's still not able to wipe or format it.then i've found a data.img and flashing the userdata and reboot.then i enter the system,and it forced me to do a factory reset,of course as before,it's not mailfunctioning because of the cwm or the block itself damaged..
but i can enter adb,and i found that i can see the /data and the filesystem in it.then i use mount to modify it,for i can delete or modify the files in /data,and it appears normally.i delete everything in /data.then i want to try to reboot to see if it's working,but after rebooting,the device stuck at acer logo,then i reboot into the cwm,it can't be mounted again.it seems that i can flash the userdata but i can't format or wipe or modify...
and i tried to reflash the bootloader from a well-mailfunctioning deivece,not working,either.
then i go for searching the situation in google,i found there are a lot of similar problems of the tegra device,and the solution is nvflash...
i don't know if there are a block saving the information of partitions just like the PIT file of my galaxy s2,seems we should wait for nvflash?or the method to flashing PIT partitions file?
i installed the nvflash driver by modifying the usb id,but i can't do anything from nvflash,it's not matching.
I had the same problem after I upgraded to JB with CWM recovery 6.0.14 and I tried to root it. But it stuck in acer logo. Then I went to recovery mode, but it couldn't mount sdcard or external card, too.
In my case, I solved it by these steps:
1. Try to go to fastboot mode by press vol (-) + power. After it vibrate, release power, and then play lock button. Then tablet will go to fastboot mode. http://forum.xda-developers.com/showthread.php?t=1861092
2. Download these boot and recovery images: https://www.box.com/s/3321wf8gg4at639nfn06
3. Try to flash these boot and recovery images to table:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
And then, reboot tablet:
fastboot reboot
WOW, my tablet works again.
:victory:
kwaiding said:
I had the same problem after I upgraded to JB with CWM recovery 6.0.14 and I tried to root it. But it stuck in acer logo. Then I went to recovery mode, but it couldn't mount sdcard or external card, too.
In my case, I solved it by these steps:
1. Try to go to fastboot mode by press vol (-) + power. After it vibrate, release power, and then play lock button. Then tablet will go to fastboot mode. http://forum.xda-developers.com/showthread.php?t=1861092
2. Download these boot and recovery images: https://www.box.com/s/3321wf8gg4at639nfn06
3. Try to flash these boot and recovery images to table:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
And then, reboot tablet:
fastboot reboot
WOW, my tablet works again.
:victory:
Click to expand...
Click to collapse
Unfortunately, although somewhat similar, this is not the same situation as the OP had.
The first CWM originally posted a few months ago, was posted by a user who used the totally wrong partition tables, and also, didn't own the tab so it was never tested (after the fact). Basically, it damaged the chipset which required a motherboard replacement. Not to mention a specifically nasty Data_Cap bug in the CWM kernel. No image flashing via fastboot (and probably NVFlash) would repair the damage. The result was several bricked tabs till the CWM was removed. (mine included)
Also note, that the current root procedure is by the same person. Although there is an alternative.
What you had, was simple data corruption on one of the Dev Blocks. This is why you were able to fastboot an image.
Corrupting a partition can happen at any time. Whether rooted, stock, or custom rom. So it's always nice to have ADB to pull your partition images. Just in case.
MD
First things first, I am using the SL101 but as I could not find a place for that, I figured this is the best place for this post.Also I hate posting and creating new threads but there is absolutely no other thread like this, I have been searching for 3 days.
So I rooted my SL101 using vipermod with ease, then downloaded ROM manager but I think here is where I hit an issue, When cwm was installed it asked for me to confirm my device and the only device available to click was "Asus Transformer". As every other transformer tf101 firmware has worked on my tablet, I thought it would be fine. Then I was in the process of flashing Revolver 4.2.1 and my battery went flat so that was not ideal and this is when the issues began.
I booted into cwm recovery (vol- + power and then vol+ on the splash screen) and tried to "install zip from sdcard", I got the "Cant mount sdcard" dialog. I then rebooted and tried to flash the rom from ROM manager, when it rebooted, cwm went through a 20 second loop waiting for sdcard, and it did not find the sdcard so the operation was aborted. I tried a factory reset through cwm and when it rebooted, I would get the splash screen and the ASUS logo with the spinning dots loading, but it would not go past that (bootloop?). From here I could not access the OS at all.
Again into cwm and used the peri OneClick R&R Easyrecoveryv0.4. It went through all the unbricking dialog with three reboots, but one of the commands said it could not find "sdcard/recoveryblob". The system still did not work. I then put it into APX mode (vol+ and power) and installed the APX driver, used the download.bat method but the minute it opens commandprompt, it immediately disconnects the APX driver, the tablet remains in APX mode. This method did not work.
Somewhere along the lines I also managed to format the system and data so not when I turn it on it just goes into the splashscreen with the EEEpad logo and nvidia Tegra.
Also tried adb push to push revolver rom onto the system /sdcard/ directory, that works fine but then again it cant mount sdcard so I cant actually do anything with it. adb devices lists the device as 0123456789ABCDEF recovery. Finally I did try boot twrp.img using fastboot with the "fastboot boot twrp.img" command but it hangs on "waiting for device". fastboot devices also does not list any devices.
So I basically have a tablet whose cwm cant mount sdcard, adb works, fastboot doesnt see the device and I can only go onto cwm on the tablet or splashscreen. Can somebody help me out? I have spent a long time trying to fix this.
Fixed
Hi again, sorry for the double post but after posting that I realised the answer was pretty much staring me in the face and now this has been fixed. so this thread can be closed by the bigdogs.
For future reference to anybody who has this or a similar problem, especially if you format the system and fastboot is not working, the issue is cwm v6.0.1.3 (cant mount sdcard issue), I used the PERI oneclickrecovery v0.4. The unbrick selection did not work for my slider as I had already pretty much wiped any data from the system that could have been salvaged by the unbrick, but if you press "r" in the main menu it flashes a new recovery tool over cwm, and this new tool can access external sdcard so just upload the rom zip file onto there and flash. :fingers-crossed: Revolver 4.2.1 is now flashed and working. :victory:
Hi guys,
My A510 just turned itself off with no apparent reason. Now I'm experiencing the following, looping :
- It tries to boot,
- freezes on the boot logo (previously "NoThrills", now "Acer"),
- vibrates and reboots.
I can boot in recovery (CWM). When I do, CWM apparently can't access the logs. Here's what I tried :
- wiping everything (data, cache, dalvik)
- restoring Nandroid backup (it was previously a NoThrills JB, now it's back to a stock JB) but I get an error when it tries to restore /data ("Error while restoring /data!").
My computer doesn't detect the tablet when it's plugged in... so I think I can't push or adb anything.
I guess it might be a hardware problem, but does anyone have any idea ? Maybe I could try to diagnose the problem?
Thanks a lot!
You can try to put a full update.zip on your sdcard, and flash it with your recovery
(a custom ROM or a full Acer Stock ROM)
You can also try to format every partitions via fastboot and then, reflash a proper ROM
Hey Shreps,
Thanks for your answer.
- I tried flashing NoThrills' CM10 from the external SD card, it didn't throw any error (although it skipped formatting the boot partition as well as extracting the files to the data partition, I don't know if it's a valuable information or not). Now instead of having the Acer logo during boot, the screen is doing weird stuff and it still won't boot. I can still boot into recovery though.
- I'm not sure how to use fastboot on this device. I get the option to boot into fastboot on my Moto G, but not on my A510. Do I need to flash a more recent CWM to enable it?
Thanks!
Boot in Fastboot via physical button http://forum.xda-developers.com/showthread.php?t=1747802
Thanks!
Volume down + Power on + Rotation switch got me to a black screen with the Acer logo and the following on top :
"Bootloader Version JB-d0ca683 (Unlock Mode)" -> that's normal
"Bootloader VJB-d0ca683(UnlockMode): Starting Fastboot USB download protocol" -> It's stuck there and I'm not sure it completes the operation.
My PC doesn't detect the A510, and "fastboot devices" returns nothing in the terminal.
Any idea?
Thank you!
Ghoorg said:
Thanks!
Volume down + Power on + Rotation switch got me to a black screen with the Acer logo and the following on top :
"Bootloader Version JB-d0ca683 (Unlock Mode)" -> that's normal
"Bootloader VJB-d0ca683(UnlockMode): Starting Fastboot USB download protocol" -> It's stuck there and I'm not sure it completes the operation.
Click to expand...
Click to collapse
That's normal/ok
Ghoorg said:
My PC doesn't detect the A510, and "fastboot devices" returns nothing in the terminal.
Any idea?
Thank you!
Click to expand...
Click to collapse
Should work, try to proper install the Acer drivers & check your USB Cable/port
"fastboot devices" should return a device with its ID
Still no luck after reinstalling the acer drivers... I think some components may be fried at this point?
There's something I'm wondering, it seems I can't mount anything from my pc but I can see files and folders from CWM. Is there any way I could copy everything on the external SD card that's in my A510?
Thanks!
Reply
Ghoorg said:
There's something I'm wondering, it seems I can't mount anything from my pc but I can see files and folders from CWM. Is there any way I could copy everything on the external SD card that's in my A510?
Thanks!
Click to expand...
Click to collapse
With the Tablet in CWM Recovery you can do a Backup on an SD Card
search for cwm recovery backup on the net
lists you the possibilities.
I had the same Problem, fastboot did not list my device because the mode was for receiving data only. But you can try this:
Tablet off.
Enter the Fastboot Commands in the Command-Line
Then turn your tablet in fastboot-mode.
Good luck.