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.
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! Sorry about this rude way but I am in an emergency situation.
I have a ZTE RACER with Android 2.2.2 (official ZTE Frimware) which it keeps rebooting at the splash screen.
Before that, I did a root using SuperOneClick 2.3.3 by Shortfuse. After following the instructions (USB debug, plug-in, root) I've rebooted the phone normally (NOT with adb), and when it got after the ZTE Logo (the first one, not the splash screen and not the Android logo). The animation goes a little and freezes for a few seconds, then restarts automaticly (but not entirely, just repeats the splash screen) and reboot. Rance and repeat! I tried to unroot, but the app hangs, restarting with adb and nothing happens. adb restart command doesn't help that much. What should I do to fix it?
Additional info:
Phone recives adb commands normally.
Possibly Superuser app was leftover before unrooting and rooting again (yes I already did root, but superuser stoped working properly afer app and su files update)
Can't go to FTM Mode, ROM Manager gave me a broken CWM.
Unsure If I can install CWM manually since SD doesn't seem to get mounted.
Phone Info:
ZTE-RACER
Android 2.2.2 (FROYO_P2XXGV_V1.0.0_B2)
CWM 5.0.x (Installed with ROM Manager. Broken.)
Carrier: GR COSMOTE (that's unknown carrier for you.)
Thanks for any help.
P.S.: Does anyone here is greek and has a ZTE RACER with the official 2.2 upgrade? I need the FTM Mode.
From what you have said, it seems like you are in a soft brick not a hard one. This means that there is chance of recovery but you have to be very careful.
You weren't rude so don't worry bout that.
You may want to try a hard reset.
Now that we have identified the problem, you have the ability to try and find it yourself at least.
It is possible to manually flash the generic default 2.2 and this will restore your device.
or
turn off your phone and then press power button and volume up button.Programing will open and there is a option of reset and restore.By using volume button go to reset and restore option and then press power button and home key programing will start and your phone will reset.
Hit thanks if you found this useful.
Deftone said:
It is possible to manually flash the generic default 2.2 and this will restore your device.
or
turn off your phone and then press power button and volume up button.Programing will open and there is a option of reset and restore.By using volume button go to reset and restore option and then press power button and home key programing will start and your phone will reset.
Hit thanks if you found this useful.
Click to expand...
Click to collapse
For the first one, I don't know how since the only way I had was to reflash it with the 1-Click Update (I did that on my ZTE MF636 3G Modem).
About the second, you mean that I must use the adb command, or I just hold it down without connecting it (I am newbie to the Android), but thanks for the help. I'll keep you posted for the results.
(NOTE: 1-click update is the offline frimware updater made by ZTE.)
if the logo appears look for a solution, if nothing happens buy a new one because is a full brick
rivas1981 said:
if the logo appears look for a solution, if nothing happens buy a new one because is a full brick
Click to expand...
Click to collapse
Logo appears but... I still don't get it.
Was that for CWM? Or for the phone?
CWM is broken by the ROM Manager. After installing, I tried to get in, but it got frozen to the Android logo + the red led is on. (Temporal brick).
Should I flash a working CWM to the phone?
Anyone?
If there is a working CWM recovery .img file for your device, flash that using fastboot.
-- Sent from my TouchPad using Communities
post-mortem said:
If there is a working CWM recovery .img file for your device, flash that using fastboot.
-- Sent from my TouchPad using Communities
Click to expand...
Click to collapse
a) I am not sure if it works but for sure it doesn't come from ROM Manager.
b)Where do I find fastboot and what's the command?
Anyone, please?
I think you get it when you install the SDK, along with ADB. You put your phone into fastboot mode, plug the USB into your computer, and use fastboot flash_image to flash the .img file to your device's recovery partition.
If you can boot your device into fastboot mode, search for "Android Flash Recovery" by Bill.Weckel (Windows only). That'll be the easiest way.
-- Sent from my TouchPad using Communities
post-mortem said:
I think you get it when you install the SDK, along with ADB. You put your phone into fastboot mode, plug the USB into your computer, and use fastboot flash_image to flash the .img file to your device's recovery partition.
If you can boot your device into fastboot mode, search for "Android Flash Recovery" by Bill.Weckel (Windows only). That'll be the easiest way.
-- Sent from my TouchPad using Communities
Click to expand...
Click to collapse
This command doesn't work. Is it fastboot flash recovery [image_file]?
Will somebody please help me out!
Here is the thread for Android Flash Recovery:
http://forum.xda-developers.com/showthread.php?t=1827723
Doesn't work! It does detect it, but it can't flash it (on normal boot only. On recovery/bootloader it just getting bricked). Any other options? Or I have to send it for reflashing?
I rebooted my OnePlus One yesterday and found myself in a weird situation. The phone would go to the initial OnePlus logo then after, a smal android logo with a red warning sign appears for a split second, and I boot into the CM stock recovery. I can't turn it on or enter fastboot, nor can I turn on ADB Debugging on my phone and would really appreciate help as I do not want this phone to be gone. Pretty scared guys, help would be much appreciated!
I've never seen this problem before.
I supose you are bootloader unlocked, rooted and have costum recovery, right?
For fastboot, if it does not work normally, try: up button + power with the phone connected to the PC; if it does not work, try the same button combo + plug the phone to the pc while you are holding down the buttons.
badjoras said:
I've never seen this problem before.
I supose you are bootloader unlocked, rooted and have costum recovery, right?
For fastboot, if it does not work normally, try: up button + power with the phone connected to the PC; if it does not work, try the same button combo + plug the phone to the pc while you are holding down the buttons.
Click to expand...
Click to collapse
Thanks for the prompt response. I think you should also know that I attempted to put a custom recovery on my OPO, but after saying that it worked, I only loaded into the CM Stock Recovery. I do not, have my phone with me at the moment as I did not think it would be necessary to bring to school with me, but I will attempt everything you have said. Thanks for the help so far!
badjoras said:
I've never seen this problem before.
I supose you are bootloader unlocked, rooted and have costum recovery, right?
For fastboot, if it does not work normally, try: up button + power with the phone connected to the PC; if it does not work, try the same button combo + plug the phone to the pc while you are holding down the buttons.
Click to expand...
Click to collapse
I attempted both ways but nothing happens as I press the buttons. It will only boot in the CM Simple Recovery.
NizzleFish98 said:
I attempted both ways but nothing happens as I press the buttons. It will only boot in the CM Simple Recovery.
Click to expand...
Click to collapse
I believe you messed it up for good, since you: can't get into fastboot; have no recovery; have no backups... If you could get fastboot to go you would only need to flash twrp and then sideload a rom =/
Does the stock recovery let you sideload?
badjoras said:
I believe you messed it up for good, since you: can't get into fastboot; have no recovery; have no backups... If you could get fastboot to go you would only need to flash twrp and then sideload a rom =/
Does the stock recovery let you sideload?
Click to expand...
Click to collapse
Yes. It does.
Download the stock image. I'm sure it will be there somewhere in the forums.
Then go to recovery and do the following:
Select 'apply update'. Then you either have the option to apply update from Internal Storage or from adb.
Select adb and enter: adb sideload update_filename.zip
badjoras said:
I believe you messed it up for good, since you: can't get into fastboot; have no recovery; have no backups... If you could get fastboot to go you would only need to flash twrp and then sideload a rom =/
Does the stock recovery let you sideload?
Click to expand...
Click to collapse
assuming it's the stock android recovery, i'm pretty sure it allows for sideloading.
Def sounds like something got flashed to the wrong parition though
Ok, I have tried google and search and can't get any help, I can't access the recovery on a xt926, it is rooted and unlocked on 4.4.2 but I can't get it to load from the PWR/ VOL UP menu immediately after flashing either twrp, or cwm. when I try to use fastboot to flash the recovery I get told that the variable is not supported but then it continues with flashing and says it's complete but obviously doesn't work.
Any ideas?
I have an XT925. I got the latest DROID_RAZR_HD_Utility_1.41. Used that included TWRP 2.7.1.0 specifically for the XT 925.
Make sure you have the most recent drivers for your PC to recognize the XT925.
Boot to fastboot.
Connect the phone and make sure it is recognized.
Flash into the recovery partition the above TWRP.
yes, I also received the 'variable not supported' message. But the flash does confirm completion.
Once the flash is completed, unplug the phone. Then a quick press and release of the power switch to turn off. Once off, use simultaneous power and Volume+- press to get into boot menu. From there, select Recovery option and you should get into TWRP.
This worked for me after I thought I had completely bricked my XT925.
Cheers
Latheman said:
Ok, I have tried google and search and can't get any help, I can't access the recovery on a xt926, it is rooted and unlocked on 4.4.2 but I can't get it to load from the PWR/ VOL UP menu immediately after flashing either twrp, or cwm. when I try to use fastboot to flash the recovery I get told that the variable is not supported but then it continues with flashing and says it's complete but obviously doesn't work.
Any ideas?
Click to expand...
Click to collapse
Power phone off and press volume up, down, and power buttons simultaneously and hold them until you see white text with boot options. Scroll down to recovery and press vol up. Of thia still doesn't work, then you may be flashing a bad recovery image.
Thanks guys, I already got it fixed, I used flashify and it worked great.
So I received my Yuphoria about a week ago. Decided to attempt rooting, unlocked the bootloader but I cannot seem to get a custom recovery to run on it, be it CWM or TWRP.
When I try to hotboot the image in fastboot mode, as soon as I enter the fastboot boot recovery command, my PC loses connection to the phone and a message pops up saying "USB device not recognised".
When I try to flash the recovery images, it is always successful. However, when I boot into the recovery, it always loads up the stock recovery, which is strange since the flash was successful.
Any solutions to this problem?
EDIT 1: Tried it with multiple PCs. Same problem for each one.
tirtha2shredder said:
So I received my Yuphoria about a week ago. Decided to attempt rooting, unlocked the bootloader but I cannot seem to get a custom recovery to run on it, be it CWM or TWRP.
When I try to hotboot the image in fastboot mode, as soon as I enter the fastboot boot recovery command, my PC loses connection to the phone and a message pops up saying "USB device not recognised".
When I try to flash the recovery images, it is always successful. However, when I boot into the recovery, it always loads up the stock recovery, which is strange since the flash was successful.
Any solutions to this problem?
EDIT 1: Tried it with multiple PCs. Same problem for each one.
Click to expand...
Click to collapse
its not strange. its the way it works. after flashing custom recovery DO NOT REBOOT THROUGH FASTBOOT. just pull out the usb cord. remove and reinsert the battery and then press the volume down and power button together. You will boot into recovery. I will recommend twrp.
enrique_fire said:
its not strange. its the way it works. after flashing custom recovery DO NOT REBOOT THROUGH FASTBOOT. just pull out the usb cord. remove and reinsert the battery and then press the volume down and power button together. You will boot into recovery. I will recommend twrp.
Click to expand...
Click to collapse
Thank you! that worked perfect!
Hi which method did you use to root yu50101a? if possible can you share a link as well
:crying:I am also facing the same problem . i also have yu5010a but cannot root it . twrp or cwm not correctly flashing.just tell me if anyone have any solution .