Not sure if anyone else has tried but today's ioroot 25 update includes root for those on 4.4.2. I tried using the manual method indicated only to realize that I can't reboot into the stock recovery. Apparently two other people with the D801 have the same problem, where after doing "adb reboot recovery" the phone boots into recovery for an instant and immediately reboots. Can anyone else running stock 4.4.2 confirm whether they experience the same behavior?
ChaoticKinesis said:
Not sure if anyone else has tried but today's ioroot 25 update includes root for those on 4.4.2. I tried using the manual method indicated only to realize that I can't reboot into the stock recovery. Apparently two other people with the D801 have the same problem, where after doing "adb reboot recovery" the phone boots into recovery for an instant and immediately reboots. Can anyone else running stock 4.4.2 confirm whether they experience the same behavior?
Click to expand...
Click to collapse
Same issue for me, I suppose the only difference is mine rebooted then wiped my phone the booted back up. Looks like we can not boot into recovery?
18.4009 said:
Same issue for me, I suppose the only difference is mine rebooted then wiped my phone the booted back up. Looks like we can not boot into recovery?
Click to expand...
Click to collapse
Same problem, just posted about this actually haha. Where's our solution?!?!
18.4009 said:
Same issue for me, I suppose the only difference is mine rebooted then wiped my phone the booted back up. Looks like we can not boot into recovery?
Click to expand...
Click to collapse
That sucks. By any chance did you happen to have a copy of the stock ROM on your phone? I'm wondering if it just automatically flashes whatever file is made available to it. I did notice some of my widgets were reset but otherwise I can't see that anything about my phone was changed.
ChaoticKinesis said:
That sucks. By any chance did you happen to have a copy of the stock ROM on your phone? I'm wondering if it just automatically flashes whatever file is made available to it. I did notice some of my widgets were reset but otherwise I can't see that anything about my phone was changed.
Click to expand...
Click to collapse
No, sure didn't. I have it all setup again.. Going to hold off now until we see a for sure fix.
I really miss having root so I decided to follow this guide: http://forum.xda-developers.com/showthread.php?t=2432476
But now for what ever reason attempting to back to 4.2.2 will not work. Fails every time... I didn't have that issue before so I am not sure what the deal is.
autoprime said:
TMO D801 users on KK... there is SOME hope still. I am on ZVA on my Sprint G2(4.2.2) which has no "adb reboot recovery" option... it does tne same thing thats happening to you guys.. quick "system update" msg (or something along those lines) and then reboots phone.
now.. on sprint g2.. vol up + power brings you to the hard reset menu. BUT.. vol down + power brings me to the full STOCK recovery menu.
Now I know your method to get into the hard reboot screen is different.. i believe its vol down + power.. let go at lg screen the press again? well has anyone tried any alternate combos? there may be another button combo to bring you into the full stock recovery menu instead of the hard reset menu. once at the full recovery menu you can use adb sideload to flash to kk_root.zip in ioroot25.
good luck
Click to expand...
Click to collapse
It seems that ours is not the only model G2 with this issue. Looks like if we can figure out the button combo to bring us into stock recovery we should be able to get this to work. Having spent the greater part of the last hour trying to come up with something, I still haven't found anything. What I do know is pressing vol down + power until the LG logo and either vol down + power OR vol up + power will take me to the hard reset menu.
I also managed to get to a menu that asked if I want to answer phone calls with physical buttons by holding down all three, releasing and holding them again. But for some reason I wasn't able to replicate this. Now when I continue holding down all three buttons at the LG logo, after getting there using any button combo, the phone just shuts off.
Has anyone successfully entered the D801 stock recovery using button combos? I have yet to find any method other G2 users discussed that works for me.
Related
Anyone knows how to enter recovery mode on Optimus one?
vol down + home + power
aint working on mine...
I tried vol down + home + power when my phone was switched off and voila, it got reset . Does not matter much as I am playing with it and shoud be ready for consequences But this is not what I expected to see.
What did I do wrong? I tried using vol down + home + power when phone is ON unlocked/locked both, did not do anything.
Install the custom recovery, then the 3-button-combo should work.
With stock firmware, I think you can't enter recovery...
owunstorf said:
Install the custom recovery, then the 3-button-combo should work.
With stock firmware, I think you can't enter recovery...
Click to expand...
Click to collapse
I am hearing this (Custom Recovery) for first time, I don't know how I missed it. :| Thanks, will try that too.
I was having the same problem, so I downloaded on Google Play the "Rom Recovery", inside app I download the Recovery.
Fine, now [ Home + volume donw + power ] enters into custom recovery.
Reboot into Recovery
You first have to install Custom Recovery, The easiest way is to download Rom Manager and flash recovery from there (your phone should be rooted for that).
After the recovery is successfully flashed, you can reboot into recovery from there itself (there is an option for that).
Or if you want to manually reboot into recovery, shut down the phone and press and hold Power + Vol up + Home keys.
If it didn't work, again shut down the phone, turn on the phone and as soon as you see the LG logo, press and hold Vol UP/DOWN + Home keys (no need to press or hold the Power key).
Guys, i was having the same issue on mine. Luckly i'm as dumb as i am smart and i kept trying... What happened on mine was that i was using the custom recovery named "TWRP - 2.8.3".. Specifically in this version, the shortcut keys combo to access the recovery mode is with Vol UP+home+power. Hope i have helped you! See ya!
theSuda said:
I tried vol down + home + power when my phone was switched off and voila, it got reset . Does not matter much as I am playing with it and shoud be ready for consequences But this is not what I expected to see.
What did I do wrong? I tried using vol down + home + power when phone is ON unlocked/locked both, did not do anything.
Click to expand...
Click to collapse
Idiot you have to install recovery first than use this key sequence.
niral.naik said:
Idiot you have to install recovery first than use this key sequence.
Click to expand...
Click to collapse
Oh the irony of calling me idiot and you don't realize this is a post from 14th February 2011. duh.
I ended up trying at least 10 roms until I finally went back to stock V20 from LG which worked best of all in long run. Later bought multiple android devices like HTC M8, LG G4, V10 etc. and played with them.
Also I was new at the time of the comment, starting with my first android phone and all. Just thought I would try whatever I could find to play with the phone. Also my post clearly shows I understood the risk and was amused at my stupidity myself.
theSuda said:
Oh the irony of calling me idiot and you don't realize this is a post from 14th February 2011. duh.
I ended up trying at least 10 roms until I finally went back to stock V20 from LG which worked best of all in long run. Later bought multiple android devices like HTC M8, LG G4, V10 etc. and played with them.
Also I was new at the time of the comment, starting with my first android phone and all. Just thought I would try whatever I could find to play with the phone. Also my post clearly shows I understood the risk and was amused at my stupidity myself.
Click to expand...
Click to collapse
Wanna sell your lg phone?
Have LG Optimus screen cracked and froze switched screens with good one phone turned on but stuck at lg boot screen .Can't get passed lg screen phone just keeps looping back .Took it to metro PCs where it was factory reset and still lg screen stops .Is there anyway to get my phone working again
?
I need help getting the wife's phone out of safe mode. I rooted the phone and its on a stock rooted 2.2.1 rom and if you do a restart it loads the the boot loader screen and I can pick recovery and then restart but it still boots in to safe mode says it in the bottom left corner. She has apps and stuff on there so trying to get everything back but not really sure how to get this fixed. Also have pulled the battery out and still no luck going to safe mode. I guess if I can't get it fixed can I install a factory stock rom back on it to fix this? I know if I do she will lose everything. Just need the best option to get this fixed.
Thanks
"Safe mode"???? I've never heard of that.
Yeah it the bottom left corner of the phone it says safe mode it says it down near the home icon and over top off the circle with the up arrow. It looks like it may only load mainly core apps and some others but not all kind of like a windows pc in safe mode. And like I said I've pulled the battery out and rebooted and still says it and also from the boot loader screen picked recovery and then restart and once booted it still says it in the bottom left corner.
I gotta ask... Are you sure this is an Inspire?
Yes this is a inspire. I'm at work and once I get home I will use my inspire and take a pic of the screen with it saying it and upload it here. Mine I just got and haven't rooted it yet still a little unsure on the new way so you may see some questions from me on it a little later.
I have seen people stuck in safe mode . The guy was stuck in hboot and would not boot up. somehow he managed to boot it up but he said it was in safe mode. he was going to flash the gingerbread ruu, but havent gotten an update.
you posted in the thread gene it was titled bricked.
as to the question isse here. you might have to flash a new rom, though not ideal. But google does a good job of backing up apps/settings
I'll be damned:
http://www.technipages.com/htc-hero-start-in-safe-mode.html
This seems more applicable to the Inspire:
http://www.myvusers.com/forums/htc-thunderbolt/7426-safe-mode-htc-thunderbolt-adr6400.html
I'll try and see if one of these works. I think I read some where about the hero and tried it but may not have. So will give it a shot.
Thanks
sreadesjr said:
I'll try and see if one of these works. I think I read some where about the hero and tried it but may not have. So will give it a shot.
Thanks
Click to expand...
Click to collapse
Apparently the hero has a "hard" menu key. The Inspire does not so you have to ue a different "hard" key. I tried it and the thunderbolt method works for the Inspire (using VOL "hard" key).
It was mentioned over on #liberatedAria that you may have a stuck VOL-UP key so it goes into safe mode every time you boot.
Ok thanks Gene I'll try it for the thunderbolt method. Like you said the key maybe stuck. So when you powered back on you held power and vol up key and it turned safe mode off for you then? Just checking cause not sure if vol down does any thing or you always use the up vol.
sreadesjr said:
Ok thanks Gene I'll try it for the thunderbolt method. Like you said the key maybe stuck. So when you powered back on you held power and vol up key and it turned safe mode off for you then? Just checking cause not sure if vol down does any thing or you always use the up vol.
Click to expand...
Click to collapse
No, I just rebooted. That's why we thought the key might be stuck.
yeah I think it is the vol key stuck as soon as you try to turn phone on it just goes to hboot screen. Sense I do believe the volume key is stuck does anyone know how hard it would be to fix this problem? I'm sure I can order a new volume button on ebay but not sure that will fix the problem. I need to get it fixed so I can get it back to factory rom so I then can take it back to AT&T cause I do have insurance on the phone but don't believe they will take it back cause of it loading to the hboot screen menu.
Can anyone give me any suggestions on what to do to get this fixed? And would it be possible to use the stock rom or stock exe file to put it back to stock form to take it back to AT&T to get it repaired or can I repair this problem myself by ordering a new volume key off ebay.
You should try gene pooles s-on tool in the Dev section. Since you have insurance I would just have it replaced
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:
I just received my pre-ordered One today, and I excitedly hooked it up to the computer and unlocked the bootloader. All went fine, and I re-launched the software to enable usb debugging, and disable the recovery update option that reinstalls the stock recovery (both still setup correctly). I then rebooted into the bootloader and flashed the newest 2.8.1.0 TWRP. I rebooted back into the system, then adb reboot-ed into the recovery, but it just sits at the logo forever until I hold the power button. I've tried 2.8.1.0, 2.7.1.1, and 2.7.1.0, none of them boot into the recovery. I have tried the Cannibal Open Touch recovery, and it functioned, but I really would prefer to use TWRP, anyone know what's going wrong?
Have you only tried adb rebooting? Or have you actually tried the other methods?
Transmitted via Bacon
The vol up + pwr button has never worked for me in all my attempts (maybe once), not sure why, maybe I'm doing something wrong there. The vol down + pwr button shortcut however has been working with the temporary recovery I have installed, I've just found the adb reboot recovery to be a much easier method.
NotDisliked said:
The vol up + pwr button has never worked for me in all my attempts (maybe once), not sure why, maybe I'm doing something wrong there. The vol down + pwr button shortcut however has been working with the temporary recovery I have installed, I've just found the adb reboot recovery to be a much easier method.
Click to expand...
Click to collapse
Power + volume up gets you to fastboot mode, not recovery. Power + volume down should work. The easiest method is just by using the reboot menu in Android though. You need to enable the advanced reboot menu in Developer Options, then whenever you select reboot after holding the power button you can choose from normal reboot, soft reboot, recovery, or bootloader. It should work, and it saves you from having to use adb every time.
Transmitted via Bacon
Sorry, let me rephrase what I was saying. All these methods work for getting the phone to what should be TWRP, but it never boots. It just hangs at the OnePlus logo until I force power it off. Other recoveries I've tried work, only TWRP hangs like that.
NotDisliked said:
Sorry, let me rephrase what I was saying. All these methods work for getting the phone to what should be TWRP, but it never boots. It just hangs at the OnePlus logo until I force power it off. Other recoveries I've tried work, only TWRP hangs like that.
Click to expand...
Click to collapse
Yeah I know what the problem is, I'm just making sure you've actually tried to boot into TWRP using all methods. I was specifically asking whether you've used the advanced reboot menu because you said you've been using adb and it seems odd to be using adb instead of a much easier option. So, it's not working with the button combination, or with adb, or with the reboot menu, correct?
Transmitted via Bacon
None of the methods of getting to the recovery are working so far. I did however just re-flash the 2.8.1.0 recovery and now instead of it hanging on the logo, the logo turns blue (which looks really glitched out), and slowly fades to a black screen, which it then freezes on indefinitely like the logo. This has happened before, but I can't isolate when it freezes on the logo or this black screen, but both end up having the same effect.
Edit: Also, I attempted to fastboot boot with the twrp, and it just turned the fastboot logo blue then it slowly faded away to the same black screen which, of course, it froze on.
There have been several other people discussion this exact problem that you're describing here in the q&a section. I don't know if they every found a solution but it might be worth a bit of a search.
Transmitted via Bacon
I've encountered those posts as well, from what I could tell they all just had to settle for a CWM-based recovery. I hoped someone would be able to answer the question, but I really don't know what's wrong with it. I even factory reset to 38R from the new 44S or whatever it was, and it still wouldn't work. I guess I'll just have to settle.
NotDisliked said:
I've encountered those posts as well, from what I could tell they all just had to settle for a CWM-based recovery. I hoped someone would be able to answer the question, but I really don't know what's wrong with it. I even factory reset to 38R from the new 44S or whatever it was, and it still wouldn't work. I guess I'll just have to settle.
Click to expand...
Click to collapse
It just doesn't make any sense. There must be something about the newer firmware and TWRP that just don't go together well. I'm still on 2.7.1.1 and I'm too afraid to try to update now in fear of losing TWRP altogether. I can't stand other recoveries, they're so outdated.
Transmitted via Bacon
I could try posting on the TWRP thread and see whether anyone who knows better than us can either patch TWRP or give a solution. I hate other recoveries as well, but if I'm forced to I'll use an alternative.
NotDisliked, i have the same problem here, did you find any solution?
Indutor said:
NotDisliked, i have the same problem here, did you find any solution?
Click to expand...
Click to collapse
I've had this problem ever since I got my OPO. Today I think it was solved for me at least!
I just flashed newly released Unofficial TWRP 2.8.2.0 from katinatez. First boot after flashing it froze at the splash-screen and rebooted, but second time I booted into recovery it started working!!!
androidfilehost.com/?w=files&flid=19646
Hi all,
First of all I would like to apologize if my question is answered somewhere else already, I have searched the web for 2+ hours and cannot find anything that gives a solution to my specific problem/question.
After wiping my data/system/cashe etc. through TWRP 3.0 I rebooted ignoring the message that there was no OS installed. I knew there was no OS installed and my intention was to get back into TWRP after the reboot.
To my surprise my phone did not go into the TWRP menu on its own like it did before (previous problem was a TWRP bootloop, but that's a different story). Pressing the volume down + power button does not bring me back into the recovery modem for TWRP either.
The only screen I can reach is the download mode (by holding volume down + power + home button) where I previously used Odin to flash the Kernel and install TWRP.
I think I messed it up by rebooting without any OS, which now prevents me from getting back into TWRP. I hope there's anyone who can help me by either pointing me in the right direction or put me out of my misery by telling me I should accept my fate of having a bricked phone.
Any help or answer is GREATLY appreciated.
Thanks in advance,
no0bstar
Odin back to stock
What was posted above orrrrr you could try booting into download mode and hit cancel (restart) then quickly hit and hold the TWRP combo, this method works for me.
AFAIK ROMs don't touch recovery so OS or no OS you're fine I believe.
christopherrrg said:
What was posted above orrrrr you could try booting into download mode and hit cancel (restart) then quickly hit and hold the TWRP combo, this method works for me.
AFAIK ROMs don't touch recovery so OS or no OS you're fine I believe.
Click to expand...
Click to collapse
I'd say it is simply a matter of not doing the button combo properly tbh... That is the impression I get
crixley said:
I'd say it is simply a matter of not doing the button combo properly tbh... That is the impression I get
Click to expand...
Click to collapse
Yeah more or less, I just noticed it gives you an extra few seconds with DL mode.
I've managed to get back into TWRP by installing the stock rom and TWRP through Odin.
Right now im installing Nougat, hopefully it was worth the few extra grey hairs...
Thanks for the help all!