I am desperate. I have been at this for almost 3 days. I screwed up and tried a one click root. I really need some "dumb down" instruction. My xoom wont even power off. . I have a Xoom 3g. I tried a one click root, and after about 2-3 reboots in the process, It is locked on the "M Dual Core" screen. I can push the power+up button to reboot, but the thing won't power down. It will only restart. When it restarts, I can hit the down button and get the Android Recovery options. I have selected "Wipe/Factory Reset" and "Wipe cache" they both reboot me to the "M Dual Core" screen where it is locked again. As I said before.....It won't even power off. It has stayed on for 3 days now. On the "M Dual Core" screen. Please help. Or send me somewhere that can. I need noob language and instruction. I am an Old Retired Soldier, with a rattled brain. Thanks, Bob D.
spywiz said:
I am desperate. I have been at this for almost 3 days. I screwed up and tried a one click root. I really need some "dumb down" instruction. My xoom wont even power off. . I have a Xoom 3g. I tried a one click root, and after about 2-3 reboots in the process, It is locked on the "M Dual Core" screen. I can push the power+up button to reboot, but the thing won't power down. It will only restart. When it restarts, I can hit the down button and get the Android Recovery options. I have selected "Wipe/Factory Reset" and "Wipe cache" they both reboot me to the "M Dual Core" screen where it is locked again. As I said before.....It won't even power off. It has stayed on for 3 days now. On the "M Dual Core" screen. Please help. Or send me somewhere that can. I need noob language and instruction. I am an Old Retired Soldier, with a rattled brain. Thanks, Bob D.
Click to expand...
Click to collapse
I'm assuming since you were using the 1 click stuff you aren't at all familiar with JDK, the android dev kit, or adb... you kinda need to get your hands dirty here.
You can download stock images from http://developer.motorola.com/products/software/ and then reflash your Xoom back to factory if you are able to get into fastboot mode.
Optionally, you can send your Xoom and $100 to Bigrushdog I hear he's challenged the entire community to bring him an a Xoom he can't unbrick
Related
Running CM 10.1, 06/08 Nightly
I did search the threads and google, but could not find any posts about a phone that works normally except for download and recovery.
Problems:
1. Can't boot into recovery (via apps, power menu, or manually). It gets to the boot logo, and then blank screen and resets. It will keep resetting trying to go into recovery (a battery pull will put it back to normal).
2. Can't stay in download mode. When I put the phone in download mode, it turns off after a couple seconds. I can't ODIN it if it keeps turning off.
3. Power button doesn't work properly (sometimes it works, most of the times it doesn't). Example: I press the power button to close the screen. No response. A few minutes later I might press it, and the screen will close, but come back on and this time with power menu. I took out the button to verify that it wasn't stuck, and tried pressing the actual button inside the phone with the stick. I can feel it click, but it still has the same problems. Pretty sure it's not a stuck button.
What's working:
-Everything else. If I let the phone boot normally, it loads perfectly fine and into cyanogenmod. No issues with voice/data, any apps, or instability. No battery issue. No lag. No crashes. The only issue is with the power button, and my inability to boot into recovery or go into download mode.
History:
-I was experiencing a random reboot problem (and power button issue) from an earlier nightly, and I waited a couple months for a more stable version. The CWM recovery for some reason only worked sometimes. When I did get it to work, I flashed RC5 (format and wipe data, dalvik, cache, factory reset, etc.), which fixed my reboot problem, but not my power button.
-I came across this thread: at plus.google(.com)104277415207525128383/posts/iAVpVPYqMtM and updated the radio, even though the RC5 fixed my random reboot.
-I did try flashing CWM, TWRP, and Stock recoveries (the latest ones, and from CWM/EZ recovery apps), but have not tried CWM Touch. It doesn't seem to matter, it won't boot into recovery.
Perceived Solution:
-I have a plan with Best Buy - I am considering smashing the phone and getting it replaced with a refurb, but would like to avoid that if possible.
Anyone have any ideas? I am okay with the phone as is, but I would like to be able to update CM or to another ROM in the future
Thanks for helping me out!
Can you get into recovey just long enough to do a system wipe?
Sent from my Rooted Verizon Samsung Galaxy S4 using xda premium
DarkMenace said:
Can you get into recovey just long enough to do a system wipe?
Sent from my Rooted Verizon Samsung Galaxy S4 using xda premium
Click to expand...
Click to collapse
Thanks for responding; It doesn't boot into recovery at all. Right after holding Vol. Up, Menu + Power, I get the screen with the small text in the corner, so you know it's going to enter recovery. Then the logo appears, except after that the phone either hangs with a blank screen, shuts off, or resets itself.
I think something got corrupted, but I'm not sure how to find out what, or what steps I could take to fix it.
phospholipid1 said:
Thanks for responding; It doesn't boot into recovery at all. Right after holding Vol. Up, Menu + Power, I get the screen with the small text in the corner, so you know it's going to enter recovery. Then the logo appears, except after that the phone either hangs with a blank screen, shuts off, or resets itself.
I think something got corrupted, but I'm not sure how to find out what, or what steps I could take to fix it.
Click to expand...
Click to collapse
Unfortunately if you can't get into the recovery mode or the Odin mode then you would need to replace the phone. It's bricked.
DarkMenace said:
Unfortunately if you can't get into the recovery mode or the Odin mode then you would need to replace the phone. It's bricked.
Click to expand...
Click to collapse
Thanks for the response.
Yeah, that's what I thought. I've never really heard or seen someone with a "functionally bricked" phone, so I'm not sure what to do.
Before I go ahead and smash it for the insurance replacement, I want to see if anyone else has any ideas..
Like I said, the phone boots normally just fine. Is there some kind of app that can flash files? Or maybe some commands I can enter in the terminal emulator?
phospholipid1 said:
Thanks for the response.
Yeah, that's what I thought. I've never really heard or seen someone with a "functionally bricked" phone, so I'm not sure what to do.
Before I go ahead and smash it for the insurance replacement, I want to see if anyone else has any ideas..
Like I said, the phone boots normally just fine. Is there some kind of app that can flash files? Or maybe some commands I can enter in the terminal emulator?
Click to expand...
Click to collapse
Have you tried Odin Mobile Pro? I've never used it myself, but I've heard a lot of good things about from some friends.
It sounds to me like a faulty power button, it isn't hardbricked because your phone is able to boot into recovery and download mode. But If for some reason your power button is stuck in the on position, it will skip booting into recovery and eventually boot out of download mode. Just because the power button physically moves and clicks doesn't mean it can't get stuck, there's obviously something funny going on with it that isn't rom/kernel regulated.
You can try terminal emulator to see if it will work, but I honestly wouldn't do anything in any menu because your phone has the potential to reboot during a process and destroy your phone. Commands are:
su
reboot recovery
su
reboot download
If it's a power button issue, best buy should replace it anyways, you shouldn't have to smash it. Samsung will also fix it under your manufacturer warranty despite it being rooted.
Sent from my SCH-I535 using Tapatalk 2
Thanks for responding, guys
rellomar said:
Have you tried Odin Mobile Pro? I've never used it myself, but I've heard a lot of good things about from some friends.
Click to expand...
Click to collapse
Yes, I did. This brings me back into download mode, at which the phone just turns off.
BadUsername said:
It sounds to me like a faulty power button, it isn't hardbricked because your phone is able to boot into recovery and download mode. But If for some reason your power button is stuck in the on position, it will skip booting into recovery and eventually boot out of download mode. Just because the power button physically moves and clicks doesn't mean it can't get stuck, there's obviously something funny going on with it that isn't rom/kernel regulated.
You can try terminal emulator to see if it will work, but I honestly wouldn't do anything in any menu because your phone has the potential to reboot during a process and destroy your phone. Commands are:
su
reboot recovery
su
reboot download
If it's a power button issue, best buy should replace it anyways, you shouldn't have to smash it. Samsung will also fix it under your manufacturer warranty despite it being rooted.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the commands; they ended up just shutting the phone off.
Yeah, I did ponder the idea that even though the power button "clicked," it might not necessarily be working. I google searched "galaxy s 3 broken power button" and there was a video with a description where the guy mentioned something about the circuit always being switched "on"
But his phone experienced different symptoms than mine (because the circuit was always switched on, the phone actually restarted itself while in normal operation. This hasn't happened to me).
Is there an app for me to definitely determine which buttons are being registered as they are pressed? Similar to programs that tell you what buttons you're pressing on your keyboard.
I would take it back to Best Buy, but I just don't want to give them any reason to say it was my own fault since I rooted and put a custom ROM on it.
Haha, I'll dunk it in salt water in favor of smashing it
Thanks again for your suggestions and ideas :cyclops:
Hello there!
I asked this question a few months ago, but I decided to redo it again because at the moment I didn't have the necessary things to do it.
We have an ASUS Transformer Pad TF300T that is stuck looping at the boot loader.
It is running stock Android 4.2.1, never been unlocked!
What do I need to do to fix it so it boots into Android?
--------------------------------------------------------------------------------
If you could also give step by step instructions on what I need to do that would be great!
1. (Like This!)
2. (Like This!)
P.S My Father found "another way", where he pressed the middle android icon, that simply shows the Android Man, and the words Android underneath. He forgot what happened next so we're here on the Coldboot Screen with nothing happening. Do we have to fastboot now?
Fast Replies are appreciated!
Potential Answer?
McGirk242 said:
Hello there!
P.S My Father found "another way", where he pressed the middle android icon, that simply shows the Android Man, and the words Android underneath. He forgot what happened next so we're here on the Coldboot Screen with nothing happening. Do we have to fastboot now?
Fast Replies are appreciated!
Click to expand...
Click to collapse
Assuming this is a noob question, do you mean the boot loader as in the ASUS loading screen or the stock recovery bootloader?
The boot loader can be accessed by holding down the "volume down" while turning your device on. To navigate it, use the "volume down" button. To go through with your option, use the volume up button.
When you enter the "bootloader" (assuming you can get to it), you should see three options, RCK, Android and Wipe Data. RCK is recovery mode, the Android logo "cold boots" android, and the wipe data selection does a factory reset.
Try cold booting it (you will NOT lose any data),and theoretically, it should work. Otherwise, factory reset it. (You will loose date)
If it doesn't work, could you try give even more detail about what happened next time? It helps alot when answering questions in general.
I hope this helped.
Live long and prosper.
P.S. If you want to find out more about fastboot/ADB, check out these post.
http://forum.xda-developers.com/showthread.php?t=2141817 ADB
http://forum.xda-developers.com/showthread.php?t=2277112 Fastboot
http://forum.xda-developers.com/showthread.php?p=42407269 Minimalistic ADB and Fastboot
If I helped you in any way, shape or form, I would appreciate it if you hit the "thanks" button. If I gave you a link to someone that helped you in any way shape or form, give them some thanks as well.
McGirk242 said:
Hello there!
I asked this question a few months ago, but I decided to redo it again because at the moment I didn't have the necessary things to do it.
We have an ASUS Transformer Pad TF300T that is stuck looping at the boot loader.
It is running stock Android 4.2.1, never been unlocked!
What do I need to do to fix it so it boots into Android?
--------------------------------------------------------------------------------
If you could also give step by step instructions on what I need to do that would be great!
1. (Like This!)
2. (Like This!)
P.S My Father found "another way", where he pressed the middle android icon, that simply shows the Android Man, and the words Android underneath. He forgot what happened next so we're here on the Coldboot Screen with nothing happening. Do we have to fastboot now?
Fast Replies are appreciated!
Click to expand...
Click to collapse
1. Hold power button until unit is off
2. Hold power button + Vol down button
3. Select the android icon for a cold boot (use the vol rocker to make the selection)
Hopefully that resolves the issue.
Okay, I have a 16 gig us moto g with a unlocked 4.4 boot loader, cmw recovery, and root. The other day I was going to flash the unofficial beanstalk rom, so I did the usual data wipe and what the installation guide said on the thread. I got stuck in a bootloop so held down the power button to try and reset the phone and get it to the bootloader menu but my screen went black. It has been black ever since, no matter what combination of button I press I can't get the screen to do anything, I have never had this problem before on any android device. Do you guys think if I contact Motorola they'll give me a replacement even though the bootloader is unlocked. Any help is appreciated.
Edit: fixed! I read on a faq that you sometimes have to hold power button for as long as 30 seconds so that's what I did and it worked
So, I bought an HTC one M8 yesterday, everything on the phone works great, couldn't be happier with it. Today I decided to boot into the bootloader, just to see what it looked like, make sure I was s-on, etc. Phones locked, s-on, no flags or anything. Cool I say, let's see what the stock recovery looks like. I try to boot into the recovery, it shows a black backlit screen for about 60 seconds, then it shows a phone with a red triangle with an explanation point in the center. I cannot do anything from here, try to hard reboot it, hold down the power button for 45 seconds, nothing. So I just let it sit there, after about 5min it reboots, I have recreated the above steps three times, same results. Once again I have done absolutely nothing to this phone, it is in an out of the box state, still has the stock wallpaper lol. I searched the forum and couldn't find anything related. I'm starting to think that it was not properly flashed from the factory, or it is a referb, and they never properly restored it. I'm new to HTC am I missing something? Are there some special steps to get to the stock recovery? Anyone experienced this?
That is stock recovery. U have to wait 30 seconds or so and then press a 2 buttons at the same time. Not sure witch ones, I just press all 3. Try it a few times and the menu should pop up. I've had to do this on several phones of different makes so it's not new.
Sent from my HTC6525LVW using Tapatalk
csstamatin said:
That is stock recovery. U have to wait 30 seconds or so and then press a 2 buttons at the same time. Not sure witch ones, I just press all 3. Try it a few times and the menu should pop up. I've had to do this on several phones of different makes so it's not new.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
OK, I'm used to nexus devices. So your telling me the bootloader menu is the recovery? I mean there's an option to factory data reset, but when I select the "recovery" option it hangs as stated above. Like on a nexus you boot into fastboot, with adb reboot bootloader (or with the volume down and power, jut like the M8) then you are presented with options, one of them is "recovery" if you select it you are taken to a separate menu, or you can "adb reboot recovery" This phone seems to be set up the same way, but when I select recovery, after the hardware key combination, it hangs, no separate menu. I have tried different hardware key combinations while it is hanging, nothing you simply have to wait till it reboots. I've messed with quite a few phones, and I have never seen this.
So after the hardware key combo, when you press volume down once to highlight "recovery", then press the power button to select "recovery" our M8 just hangs then shows a phone with a red explanation point?
Just to make sure you guys know what I'm talking about, when I get to step 5 in this guide, it hangs with a red explanation point:
http://androidvibe.com/how-to-enter-your-htc-one-m8-into-recovery-mode/
I have tried rebooting to recovery via the command line with the SDK tools, same result, just hangs, then reboots.
No the screen with the red triangle is the recovery. Yes bootloader is still bootloader. But when u hit recovery in bootloader u see the red triangle after. That's stock recovery. Then u try the button combo.
Sent from my HTC6525LVW using Tapatalk
The official combo is power and volume up. It's kinda tricky to do though can take a few minutes
Sent from my HTC6525LVW using Tapatalk
thisguysayswht said:
OK, I'm used to nexus devices. So your telling me the bootloader menu is the recovery? I mean there's an option to factory data reset, but when I select the "recovery" option it hangs as stated above. Like on a nexus you boot into fastboot, with adb reboot bootloader (or with the volume down and power, jut like the M8) then you are presented with options, one of them is "recovery" if you select it you are taken to a separate menu, or you can "adb reboot recovery" This phone seems to be set up the same way, but when I select recovery, after the hardware key combination, it hangs, no separate menu. I have tried different hardware key combinations while it is hanging, nothing you simply have to wait till it reboots. I've messed with quite a few phones, and I have never seen this.
So after the hardware key combo, when you press volume down once to highlight "recovery", then press the power button to select "recovery" our M8 just hangs then shows a phone with a red explanation point?
Just to make sure you guys know what I'm talking about, when I get to step 5 in this guide, it hangs with a red explanation point:
http://androidvibe.com/how-to-enter-your-htc-one-m8-into-recovery-mode/
I have tried rebooting to recovery via the command line with the SDK tools, same result, just hangs, then reboots.
Click to expand...
Click to collapse
You have to turn off "fast boot" in Settings > Power.
Then hold Volume Down and press Power. That will get you to the bootloader.
Sent from my HTC6525LVW using Tapatalk
wtoj34 said:
The official combo is power and volume up. It's kinda tricky to do though can take a few minutes
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
csstamatin said:
No the screen with the red triangle is the recovery. Yes bootloader is still bootloader. But when u hit recovery in bootloader u see the red triangle after. That's stock recovery. Then u try the button combo.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Thanks guys I finally got it to boot to recovery. Never had such a hard time doing something so simple. Sorry for being such a ditz. the phones fine lol, still think it's strange that it's so many steps (sketchy, time consuming steps lol) to boot to stock recovery. I've never had a phone like "this" (a flagship manufacturer device), I have always had nexus devices, (since the galaxy nexus). It's always been pretty straight forward to boot to recovery. I really appreciate your help tho, I really thought my phone is was jacked up, thanks for setting me straight.:highfive:
berndblb said:
You have to turn off "fast boot" in Settings > Power.
Then hold Volume Down and press Power. That will get you to the bootloader.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Thanks, but as I said I had no problem booting to the bootloader menu, just problems with booting to the stock recovery. I appreciate you help tho.
I'm going to try to keep this as simple as possible as I don't really know what I did wrong or how I ended up where I am now.
I have a Samsung Galaxy 8+ and I decided to root it. I decided to follow this guy's instructions on how to do it: youtube.com/watch?v=eh-I4uxAmUY.
I follow his steps and am bought to the "Unmodified System Partition" menu after having gone through the process of factory resetting, wiping my data and using Odin to flash twrp-3.1.0-r1_dreamlteks.
The problem is that now the touch screen is unresponsive. It does literally nothing.
I am stuck at the screen that says "Keep System Read only?" where I have to "Swipe to Unlock Modifications", but find myself unable to do so because my touch screen doesn't let me swipe!
So now I'm panicking:
Firstly, I can't get the phone to shut down. Holding the power button does nothing, even if I hold it for a full minute.
Secondly, I can't boot the phone into anything except this unresponsive TWRP thing.
Thirdly, my computer no longer recognizes my phone when I try to connect it via USB (might be unrelated?).
How ****ed am I?
Is my phone just bricked now?
Can I save this rooting attempt in any way, or at least revert to the stock?
Will bringing the phone to a retailer help me in any way, or have I already broken the warranty?
Please guys I am desperate for some assistance here.
ViRALiC said:
I'm going to try to keep this as simple as possible as I don't really know what I did wrong or how I ended up where I am now.
I have a Samsung Galaxy 8+ and I decided to root it. I decided to follow this guy's instructions on how to do it: youtube.com/watch?v=eh-I4uxAmUY.
I follow his steps and am bought to the "Unmodified System Partition" menu after having gone through the process of factory resetting, wiping my data and using Odin to flash twrp-3.1.0-r1_dreamlteks.
The problem is that now the touch screen is unresponsive. It does literally nothing.
I am stuck at the screen that says "Keep System Read only?" where I have to "Swipe to Unlock Modifications", but find myself unable to do so because my touch screen doesn't let me swipe!
So now I'm panicking:
Firstly, I can't get the phone to shut down. Holding the power button does nothing, even if I hold it for a full minute.
Secondly, I can't boot the phone into anything except this unresponsive TWRP thing.
Thirdly, my computer no longer recognizes my phone when I try to connect it via USB (might be unrelated?).
How ****ed am I?
Is my phone just bricked now?
Can I save this rooting attempt in any way, or at least revert to the stock?
Will bringing the phone to a retailer help me in any way, or have I already broken the warranty?
Please guys I am desperate for some assistance here.
Click to expand...
Click to collapse
You have voided your warranty so you can't take it down to the shop and get it replaced.
It isn't fully bricked because you can still boot into an "os" that isn't fully functional. It ain't recognised because you have to swipe past this and hop into the ADB sideload interface. Btw, try holding your home button, power button and volume up (or down) and report results.
If I was you, I would wait till the battery drains and shuts off and then let it be off for the rest of the night or something and then try again.
RAZERZDAHACKER said:
You have voided your warranty so you can't take it down to the shop and get it replaced.
It isn't fully bricked because you can still boot into an "os" that isn't fully functional. It ain't recognised because you have to swipe past this and hop into the ADB sideload interface. Btw, try holding your home button, power button and volume up (or down) and report results.
If I was you, I would wait till the battery drains and shuts off and then let it be off for the rest of the night or something and then try again.
Click to expand...
Click to collapse
Alright, I'll give it until it passes out from battery loss and then get back on when things change. Thanks for the reply!