So last night, while my phone was charging, I went to check some messages and I noticed it was frozen (couldn't turn on the screen).
After unpluging it, I pulled out the battery and rebooted the phone and that's when I saw that it wouldn't check the USB Storage for errors.
Now I have a USB Storage that isn't recognized by the phone, but works if I mount it from cwm to my pc.
I tried: formatting USB Storage, resetting the phone to factory settings, flashing a new ROM, and none worked. Plus, now when it tries to boot, I get the boot animation for ages, and it doesn't do anything else.
If someone knows how to help me, please reply. (I searched xda and the internet and all I managed to find was USB Storage not mounting to pc...)
The ROM is CodenameAndroid 2 with android version 4.0.4.
It seems an hardware failure, or at least, a serious corruption of the boot and recovery.
Does it boot to fastboot(vol up plus power button)? If yes, I would try to go completely stock by installing through fastboot one of the factory images which are available here on xda.( Before doing that you would need to perform a backup of your \efs folder.)
In this way you rewrite boot,radio, recovery, kernel and ROM. If the malfunction was due to some corruption of system files, that should fix it.
If it does not boot to fastboot, there may be another chance with Odin. I have seen in a thread for booting with a broken power button that by simultaneously pressing vol up and vol down you enter in download mode. You need a Odin factory image, which also includes the fastboot, I think. Such a file, together with the right version of Odin is provided in that link.
Hope that this helps,
Good luck
Lionhe
Inviato dal mio Nexus S
I am able to get the phone into recovery mode, where it says it can mount SD Card and even USB Storage, but when I try to flash the stock image, it stops and says "(bad)", even though that's the same image I've flashed a couple of times before. I am also considering it could be a hardware failure, but for the moment I'm trying to elimminate all possibilities.
EDIT: it seems I can flash recovery and boot through fastboot, but not system.img
flodb113 said:
I am able to get the phone into recovery mode, where it says it can mount SD Card and even USB Storage, but when I try to flash the stock image, it stops and says "(bad)", even though that's the same image I've flashed a couple of times before. I am also considering it could be a hardware failure, but for the moment I'm trying to elimminate all possibilities.
EDIT: it seems I can flash recovery and boot through fastboot, but not system.img
Click to expand...
Click to collapse
hi me also but i flash cwr recovery-twrp-2.2.0-crespo and mit fixfor at lees
flodb113 said:
I am able to get the phone into recovery mode, where it says it can mount SD Card and even USB Storage, but when I try to flash the stock image, it stops and says "(bad)", even though that's the same image I've flashed a couple of times before. I am also considering it could be a hardware failure, but for the moment I'm trying to elimminate all possibilities.
EDIT: it seems I can flash recovery and boot through fastboot, but not system.img
Click to expand...
Click to collapse
go to seetings and format sd card or plug to your pc and format in fat32. then go to fastboot and reflash stock image... it will erase your data but at least u will not gona have any more problems
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?
I've looked for 2hours and cant find an answer to my problem seen bricks where it wouldnt turn on at all or diff soft bricks but nothing quite like mine. If some one can help me out I'd be a nice guy and pay pal them a few beers
Today got a new Nexus S 4G. Rooted it with OneClickRoot from here
downloaded rom manager and updated recovery to version 5.0.2(I think)
did a back up
Then installed [NS4G] gingerbread-deck rom from here
it had no market app and a few others missing so I decided to go back to original until I found something else.
Stupid me thought you held down vol + power to get into bootloader as on other phones I've had in the past so when it wouldnt get me in I stupidly(again :/) ran the oneClick method my thinking being it would gain me temp root access to recovery well it downgraded recovery back to 3.0.2.4 and when I went to restore my back up it skipped a few things saying "system.img,data.img and cache.img not found" then restore complete.
So phone hung during boot with that so I then went to reinstall the deck rom thinking i could send a new rom to the phones storage via USB with that and get back to recovery now that i knew vol up + power would get me into bootloader.
trying that gave a variety of errors the last saying
E:Error in /sdcard/rom.zip
status 7
installation aborted
so i can get into boot loader and recovery but that is it
Any help is greatly appreciated
Definitely not as bad as you think it is.
Have a working fastboot setup on your computer.
Use fastboot to flash the latest CWM recovery (5.0.2.0) instead of ages old 3.0.2.4
From there flash any custom ROM.
Read this to learn how to use fastboot
http://wiki.cyanogenmod.com/wiki/Fastboot
Get the latest CWM recovery from your phone here
http://www.clockworkmod.com/rommanager
Read this to learn about the mount function of CWM recovery and get a ROM on your memory even if you don't have a ROM installed
http://www.addictivetips.com/mobile...-and-how-to-use-it-on-android-complete-guide/
Tried going into Mount/Unmount and selecting Mount USB Storage but Under windows 7 I get no drive to transfer things to.
Thanks for the other tips I'll read up on those.
mysongranhills said:
Tried going into Mount/Unmount and selecting Mount USB Storage but Under windows 7 I get no drive to transfer things to.
Thanks for the other tips I'll read up on those.
Click to expand...
Click to collapse
You just need to do mount USB storage. Then unplug and replug your phone to make it detect. That will mount your internal memory used as SD card.
Tried that. it still won't pull up under My computer. Maybe after I update clcok work???
I'll try. Thanks!
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
Hey All,
I know there are a lot threads like this on here, so I made sure I tried everything possible before asking for help.
First off, It is a MZ604 wifi version.
Ok, upon powering up my Xoom, it will get to the Motorola screen/ dual core and stall.
I am able to get into recovery, however the version I am running, 5.8.3.1 apparently does not allow sd card mounting, so I am unable to restore or flash a new rom.
A factory reset/ data wipe does nothing.
I have tried to flash a new rom via ADB, however my computer will not install the Xoom drivers. It will say "installing device drivers" for about 2 minutes or so before failing. I have tried using moto helper and the other Motorola usb drivers
I am unable to boot into android to enable usb debugging
I have tried all of the above on my laptop too and to the same result.
My question is, is this a brick? or can it be solved.
Thanks for your time
Yes it can be fixed, if you can access recovery then it means you can access fastboot. So what you do is once you're in the fastboot protocol, is flash in TWRP recovery http://forum.xda-developers.com/showthread.php?t=1782235
With that recovery you can mount SD cards, so use a computer to download the ROM you want then flash. Hopefully you get the idea, but I can post in more detail if you want.
Chaosgod27 said:
Yes it can be fixed, if you can access recovery then it means you can access fastboot. So what you do is once you're in the fastboot protocol, is flash in TWRP recovery http://forum.xda-developers.com/showthread.php?t=1782235
With that recovery you can mount SD cards, so use a computer to download the ROM you want then flash. Hopefully you get the idea, but I can post in more detail if you want.
Click to expand...
Click to collapse
Thanks for responding, I appreciate it. The thing is that my xoom cannot connect to my computer, and therefore and cannot use fastboot to send it the image correct?
I could fix all of this if I could just get the drivers to install, but because of my xoom's condition, the drivers cannot install no matter what.
Hmm usually fastboot drivers should automatically install. Does your recovery have an option to boot into fastboot? Once you're in fastboot it should automatically install the drivers, and in the android sdk folder in CMD (assuming you're running windows) put in this command: fastboot devices
It should show up your XOOM if not install this http://www.motorola.com/Support/AU-EN/Support-Homepage/Software-and-Drivers/USB-PC-Charging-Drivers
And try again
Hi all!
I got the same problem...
I can connect it to PC and do fastboot, I've flashed it many times, but it didn't affect my Xoom, i've reflashed the recovery to a lower version (tiamat rc4) but the recovery still shows version 5.8.3.1...
I even tried RSD, but it still the same...
no errors, and no effects...
is my Xoom bricked?
^I heard of this before, sounds like your new recovery image just gets overwritten by the current recovery. Though I thought it was only for stock recovery.
but, how can I overwrite it? it seems like they are read only...
It's all about timing, to access recovery once you see the Moto logo wait 2-3 seconds then vol + then vol + again. This is right after you flashed in your new recovery.
You can also access your fastboot like that as well, instead of pressing vol + again, press vol - then vol +.
Chaosgod27 said:
It's all about timing, to access recovery once you see the Moto logo wait 2-3 seconds then vol + then vol + again. This is right after you flashed in your new recovery.
You can also access your fastboot like that as well, instead of pressing vol + again, press vol - then vol +.
Click to expand...
Click to collapse
that's not the problem... of course I can access the recovery, fastboot and RSD, the problem is that I whatever I do to the xoom just don't work... and it reports no error at all... it's just succeed, but nothing happened... It's like a PC running windows with DeepFreeze installed...
Anyone got the same problem? can anybody help me?:crying:
No you're missing the whole point, after you flashed your new recovery it may get overwritten if you don't reboot into recovery straight way. It never happened to me but I have read that people has that issue.
Ok so I recently upgraded to lineage OS and it had a few issues, as in it kept restarting when you left it alone, so I went into TWRP and did a factory reset and then tried reinstalling it. But when it rebooted it went straight into recovery so, I thought oh lets just use a backup I made, same issues will only boot into recovery. So looking around I couldn't find much to help with this, so I tried flashing other ROMs including stock, no luck, I then tried re-flashing TWRP including all compatible versions, no luck either. So I don't know what to do as I don't have a way to boot the phone anymore, also Windows only sees an empty TWRP folder with one file in so all the other folders have gone so I now have 22.6 GB free of 23.4GB. Any help will be great as I would like my phone back.
Ps all my backups are on an external sd card and I don't care about lost data as it's mostly on the sd card anyway
Any help appreciated
Fixed it myself
Ok so what I did was flash the stock recovery and then rebooted it fixed itself
how did you manage to go into fastboot mode to flash stock recovery??? i am unable to flash recovery via the TWRP reboot>bootloader i keep having an unknown command
mine's the same, if it goes to fastboot I can't do anything, just get a blackscreen with fastboot mode written in tiny writing in the bottom left hand corner. How do you flash the stock recovery?
andydgg said:
mine's the same, if it goes to fastboot I can't do anything, just get a blackscreen with fastboot mode written in tiny writing in the bottom left hand corner. How do you flash the stock recovery?
Click to expand...
Click to collapse
Connect to PC. Use fastboot from PC to flash recovery. From a command window type:
fastboot flash recovery original.img
Replace "original" with the name of the original recovery image.