[Q] Touch the android to begin w/ broken power button - General Questions and Answers

So here's a puzzle.
My nexus one has a broken power button, and I learnt to get around it with apps like quickboot, that let me boot into recovery automatically.
I flashed cyanogenmod 7 (nandroid before that) and turned the phone on. It worked perfectly, but I had forgotten to flash gapps, so I do.
Now I turn my phone on and it boots to the "Touch the android to begin" tutorial/thing. The android lights up when I touch it, but doesn't change screen. It just stays there. Now that is apparently not unheard of, and the advice is to wipe or reflash the rom and/or gapps. The problem is, since I don't have a power button, I can't go into recovery mode from the bootloader, I'd have to do it using the quickboot, but I can't because the screen is stuck.
Is there a way to flash a rom from a pc? Any other ideas? Anything is much appreciated.

Try a method called "passimg" which is used to revert to stock android. I don't have much to time to look into it for you, but it's possible, because i had to do the same for mine. You place the file on your sd card root then boot (using the battery removal/insertion method) while holding the volume down button. You'd have to re-root then you can try to recover again.

Related

help cant reboot into recovery after root

I'm new to Android and had my phone rooted everything seems good with the root but as soon as I go into rom manager and try to go into recovery mode I get the white HTC screen then starts to turn kinda brownish then black and will stay like that until phone is shut off. Please help I can't download any custom roms due to this I'm guessing. Thanks
Open Rom manager again. Press the option at the top to flash the recovery. After its done try to boot into recovery again.
Sent from Desire HD or Inspire 4G or whatever this thing is called via premium XDA app.
Ya I tried that already a few times and still does not work also changed the clockworkmod recoveries and nothing
Have you tried booting into recovery manually by holding volume down and pressing the power button? I find this way is more reliable that ROM manager.
Is there a trick to that I tried it my phone vibrates and get the power off option but no reboot to recovery thanks
Have you turned fastboot off? settings - applications - remove check from fastboot
Make sure fastboot is off, like the poster above me said. Turn your phone off. Hold the volume down and press the power button. You should then be able to scroll down and select recover.
All you guys are awesome the headache is gone it worked thanks very much
actually when i go into recovery i still get that htc screen that turns black and will frezze up
Did you use Bubby323's root method? That is what it sounds like. If you did, then read the FAQ. There is a fix for this graphical error.

[Q] Help Nexus S Totally Bricked!

Please help if you can, would really appreciate, dont know how to unbick my totally F$$$$### Nexus S Phone.
Even in recovery/fastboot mode on my Nexus S (Vol up+power), I cannot get my system to recognize the device....in fact, even in Windows, I am not able to get the system to recognize my device in Recovery mode/Fastboot mode....the only way it will recognize the device is if it is turned on the normal way, and hangs on the "Google unlocked icon" screen.
Some background info:
My power button recently stopped working...I thought it had to do with the fact that I updated NexusTools (was running a CyberGR rom...cant remember the name...had V4 Ultimate in it (downloaded from Rom Manager)).
So what I did was download/install (from the same developer) their hybrid ics rom....that did not brick it...but it also did not fix the power button...so after not liking the new rom, and the fact that it didnt fix my power button, I reflashed to the original rom I had installed (wiped everything, including doing a factory reset), and it just hung on "Google unlocked icon"
Now my phone does the following:
- First of all, the only way to power the device up is to plug it in (it automatically turns on and tries to boot without me pressing the non-functional power button)
- If I let it try to boot, it infinity hangs on the Google unlocked icon screen
- If I boot into recovery (by holding vol up button and plugging the phone into a power source), it hangs on the recovery screen...meaning the power button, as well as the volume buttons, as well as any buttons are non responsive.
- If I boot into recovery, the device doesnt even register on my system....
What am I doing wrong? What can I do to try and fix this?
I would truly appreciate if anyone reading this has some insights for me.
THANKS!!
Knightsage said:
Please help if you can, would really appreciate, dont know how to unbick my totally F$$$$### Nexus S Phone.
Even in recovery/fastboot mode on my Nexus S (Vol up+power), I cannot get my system to recognize the device....in fact, even in Windows, I am not able to get the system to recognize my device in Recovery mode/Fastboot mode....the only way it will recognize the device is if it is turned on the normal way, and hangs on the "Google unlocked icon" screen.
Some background info:
My power button recently stopped working...I thought it had to do with the fact that I updated NexusTools (was running a CyberGR rom...cant remember the name...had V4 Ultimate in it (downloaded from Rom Manager)).
So what I did was download/install (from the same developer) their hybrid ics rom....that did not brick it...but it also did not fix the power button...so after not liking the new rom, and the fact that it didnt fix my power button, I reflashed to the original rom I had installed (wiped everything, including doing a factory reset), and it just hung on "Google unlocked icon"
Now my phone does the following:
- First of all, the only way to power the device up is to plug it in (it automatically turns on and tries to boot without me pressing the non-functional power button)
- If I let it try to boot, it infinity hangs on the Google unlocked icon screen
- If I boot into recovery (by holding vol up button and plugging the phone into a power source), it hangs on the recovery screen...meaning the power button, as well as the volume buttons, as well as any buttons are non responsive.
- If I boot into recovery, the device doesnt even register on my system....
What am I doing wrong? What can I do to try and fix this?
I would truly appreciate if anyone reading this has some insights for me.
THANKS!!
Click to expand...
Click to collapse
yes, sounds like a dead power button(i have one myself).
try going back into your recovery, do a full data wipe(factory reset), then reflash the rom(and gapps). if still nothing, redownload the rom and try again. in your recovery, there is an usb option. use it to transfer your newly downloaded rom from your computer to phone.
Once I am in recovery mode it "freezes" though...as in not even the volume buttons work...they worked fine before, and even work to get into recovery mode...but once there they no longer work...nor does connecting the device in recovery mode to my laptop....so im kind of at a loss, as I cant even use Fastboot/adb to wipe/push anything on the Nexus S through my laptop
Knightsage said:
Once I am in recovery mode it "freezes" though...as in not even the volume buttons work...they worked fine before, and even work to get into recovery mode...but once there they no longer work...nor does connecting the device in recovery mode to my laptop....so im kind of at a loss, as I cant even use Fastboot/adb to wipe/push anything on the Nexus S through my laptop
Click to expand...
Click to collapse
im guessing that your using cwm recovery?
give your phone a few smacks on the back near the power button, your phone thinks its being pressed in.
yes, it definitely thinks it is being pressed in...thats for sure...and makes sense...ill try that haha!
Yes latest CWM Recovery...5.0.2 or something like that...just updated that before phone died...
Weird...so i "smacked" the phone a bit...when I do it in recovery mode, it reboots the phone into recovery....so it definitely thinks its being pressed down constantly...but I have found no way to make it "un-pressed"...only briefly by smacking it...
Knightsage said:
yes, it definitely thinks it is being pressed in...thats for sure...and makes sense...ill try that haha!
Yes latest CWM Recovery...5.0.2 or something like that...just updated that before phone died...
Click to expand...
Click to collapse
in twrp recovery, theres an option to not use the power button to select(thats what im using), is there a similar option in the newer cwm recovery? tr\y pressing the soft buttons). also, see if sticking a fingernail in between the power button helps, to pull out the button a bit.
After continuingto smack it...as well as "pulling" on the power button, I am not able to use volume buttons and power buttons within recovery...flashing a new rom now...will let you know if that fixes it...otherwise I will try unbickable in ubuntu again and see if that fixes it thanks for the pro-tip of smacking it, haha!

Cannot boot into recovery

i have a Galaxy Tab 2 7.0 p3113.
i used heimdall to flash CWM into the tablet.
after what seemed like a succesful flash, my tablet rebooted. but for some reason, it would only go as far as showing the galaxy tab logo. it seems stuck there. i could not turn the unit off. i would hold the power button to force shutdown, but it always starts right back up. it seemed like i could only shut it down if it was connected to my mac while holding down the power button. i can however, boot into download mode.
after consulting google, it seems like the appropriate step was to restore the unit to stock. problem is, i can't seem to boot into recovery. i'm being told by the internet that to boot into recovery, i need to hold [power] and [volume down] until it turns on and then release [power] but keep on holding [volume down] and CWM will load. but nothing happens.
i know this is a total noob post, but i've been scouring the web for two days. i'm at my wits end. any help would be greatly appreciated.
I think recovery mode accessed via volume up+power if you could not so use download mode to flash stock or so to return to normal operation
Sent from my GT-I9100 using xda app-developers app
I press the power and UP ( button next to the power button) I normally hold BOTH buttons down at once and let the boot cycle process twice just to make sure i am going into recovery .....so i see the white samsung text twice i mean. It may take around 10 seconds to complete the process. Then release BOTH keys at once.
The battery needs a good charge for it to work.. Try charging over night before you try it via the mains supply.
Holding the power button and down will bring you into download mode and thats what you use for an odin/heimdall flash.
Hope that works for you
Let us know how you get on .....
Thanks. The battery of the gtab2 drained overnight, so i've got it charging back up now. Will definitely post my results when i have something.
Thank you guys. I'm able to boot into recovery now.
But unfortunately, i still need a little guidance on my original problem. And that problem being that my gtab2 will not startup. After rebooting, it gets stuck on the logo screen. It also plays a startup audio clip. But after that, it just displays the startup logo screen. It does not go into the animation screen and start.
I should also mention that when i plug my gtab2 into my computer, no drives show up.
My question now is, if i were to select [wipe data/factory reset] in CWM, would this restore my gtab2 to it's original factory state? Or would I need to flash a ROM for this? And if i need to flash a ROM, could i place a ROM on a microsd card and flash from there?
*********UPDATE*************
Everything is fine (so far).
I went poking around CWM and realized that I had put a cyanogenmod 9 update.zip in the root of the internal sd card before all this happened. So i went back to cyanogenmods wiki on how to install it on my gtab2 and followed the rest of the instructions on flashing it and VOILA!! I have my gtab2 back.
you should use ODIN instead CWM.
CWM is not designed specifically for Gtab2.

[Q] Phone boots to recovery only. HELP!

Hi,
My Oneplus One boots only to the CWM recovery. I noticed that my volume down button not working. So I restarted the phone, and now it only boots to CWM only.
In the recovery, the volume down button still doesn't work. It looks like the button may be stuck? and my guess is it's initiating the volume button down + power button to boot to CWM.
But I also tested the Button Test function in CWM, and the down button doesn't even register.
Is there any way to bypass this? I don't need the volume button down to work necessarily, but I need my phone to work.
I'd appreciate if there's any other way to bypass this, or maybe modify CWM file to change the recovery button combo.
If the button is stuck, then no amount of altering CWM is going to help because you'll never be able to boot into the OS with a stuck volume button. You're going to need to physically inspect and fix that volume button. In the meantime in order to have a functional recovery, ditch CWM and flash TWRP, the UI is all touchscreen so no replying on buttons, and it's leaps and bounds better than CWM anyway.
Transmitted via Bacon
Hey, Thanks for the reply.
I noticed a few more things, which makes me to believe that this is not a physical button problem.
First, whenever I charge the device, the device won't stay OFF. It constantly turns on automatically.
However, if I don't charge, the device will stay OFF.
Second, I can't even go to Bootloader. I tried "adb reboot bootloader" from the command prompt and the phone boots directly to CWM recovery.
Third, if the volume down button is stuck, wouldn't it be activated all the times? So when I'm in CWM, it'll constantly go down, and when I test on Button Test, it should register constantly.
But that's not happening. It's simply dead.
I'm going to try the RMA process, but meanwhile, I would be glad if someone has better idea with the new info I provided here.
Thanks
Im having the same issue did u get it fixed? plz help

Help! Stuck on TWRP loading. I can't even turn off the phome!

So I have Galaxy S7 (Flat). It had installed TWRP with Magisk on stock Android. I decided to install LineageOS (https://forum.xda-developers.com/t/rom-q-s-lineageos-with-microg-for-samsung-s7-flat-edge.3921094/) (clean install using TWRP) and it installed successfully, everything was fine, I've turned my phone off and on few times and system was booting without any problems.
But then I decided to boot into TWRP (using key combination) to install magisk and... it's stuck on loading screen forever.
I can't even turn it off ! And my phone is getting hotter and hotter. Please help !
I can't turn it off, because simply holding power button doesn't do anything.
I can restart it by holding power + volume down ,but it just opens TWRP again.
I've read I could boot into Maintenance Boot Mode ,but it requires to turn off a phone, which I'm unable to do.
Only thing I am able to do is to boot into Download Mode, but it doesn't change anything (still cant turn off phone in this mode)
Should I try to disassembly the phone and take out the battery manually? I don't really see any other option.
Did I bricked my phone ?
@edit
I have backup of stock system made by TWRP, but it doesn't change anything as I cant use TWRP.
I didn't install LineageOS custom recovery.
Ok, so I left phone overnight to deplete the battery. And it didn't work ! I thought that battery is dead and phone is off, but the moment I've plugged the power cord it automatically turned on into TWRP screen, like a zombie !
However I've solved the problem. As I was able to get phone into Download Mode (by holding power+volume down+home) I used Odin. I've installed newest Odin on PC, Samsung USB drivers and flashed the newest TWRP tar. Although it was scary, I was almost sure I've bricked my phone. Adb/fastboot were not detecting the phone.
And after re-flashing TWRP everything works fine. Also LineageOS booted like a charm, it stay intact.
So, it seems that installing LineageOS somehow corrupted my TWRP, despite that I un-ticked the option to install LineageRecovery ,so technically it shouldn't mess with it at all.
Anyway, problem solved.

Categories

Resources