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
Related
I have flashed the CWM from TF201 by accident. Now the tablet is stuck in that CWM mode. I can't connect to usb using adb mode. Power+volume down does not work anymore. Any way I can reflash the correct CWM?
THanks
If you can boot to OS - you can use fastboot to flash any recovery.. or flash TWRP from goomanager.
upd: sry..don't see about "stuck".
abe_cedar said:
I have flashed the CWM from TF201 by accident. Now the tablet is stuck in that CWM mode. I can't connect to usb using adb mode. Power+volume down does not work anymore. Any way I can reflash the correct CWM?
THanks
Click to expand...
Click to collapse
I have made the same mistake. Although I can get the device to fastboot USB mode. I have tried to use CWM with the restore I made before I put in Cyanogenmod 9, as well as putting on the Cyanogenmod experimental #2 for TF300. No error messages at all and it wipes data and cash without any problems.
But I get locked on the Asus boot screen and it does not continue ie I am stuck as well.
I have as well tried to use the TWRP 2.1.5. I get the Teamwin loggo screen, it wipes all the data and verifies all the filesystems and reboots. Still stuck.
Is the device bricked ?
upd:The TF300 can not be shutoff either. When you hold the power button the screen goes black, but after ~5 s the device is starting again and is still stuck on the Asus bootup screen.
if you reboot it holding vol down and power, can you get back into the boot menu, to reselect fastboot?
if holding the power button doesn't switch it off, what happens if you leave it to run out of batteries then do this?
then you can flash the correct recovery.img
cheedear said:
if you reboot it holding vol down and power, can you get back into the boot menu, to reselect fastboot?
if holding the power button doesn't switch it off, what happens if you leave it to run out of batteries then do this?
then you can flash the correct recovery.img
Click to expand...
Click to collapse
Yes, I can get access to the fastboot and I have already tried to flash with the recovery.img. I have as well let the battery run out and tried it once more with the same result.
Still stuck on the asus bootup screen.
power
Hare,
I have same problem.tab cannot power off. Just reboots into cwm.
I was thinking to drain bat. Thanks for sharing that info.
There are a lot of topics about people who broke their devices with TF201's recovery.
Afaik, no one recovered it. Send to Asus.
So the device is bricked then :'(.
Thanks for clearing it up.
Sent from my GT-I9100 using XDA
RMA..
Guillaume,
Thanks for clarification.
I have read that ASUS wants 700USD for replacing/reflashing the bootloader. That was for the tf201. Any way to nvflash it back to factory? I don't believe that they have to change the MB.
I have no warranty left, but I don't want to be gouged by them either.
Any thoughts, info?
Hi,
I've do the same mistake, but I can use adb.
Do youhave any news about our problem?
Thanks
Midyr
unable to power off
My issue is that I have the CWM for the tf201. I did the update from the CWM app in Android. Bad idea. So now the tab does not power off s.t. I can get into the power+vol down mode. Adb does not work since I cannot ( don't know how) to make it go into the usb debugging mode. I have tried several things none of which have worked. Still stuck.
I wanted some feedback for a RMA from ASUS, posted it here but sor far no answers.
Not sure if it would really work, but on my Evo, I don't have to completely power off the phone to do the recovery sequence. I can do it during a normal reboot. There is a point just before the device starts booting again where it is technically "off", and if I hold volume down (don't even have to hold power on my Evo; volume down seems to be the only necessary button) starting at this point, the phone will boot into the bootloader.
So, next time the device reboots, just start holding volume down (possibly power also, just in case) at the "off" point.
I just rooted my One S using this thread: http://forum.xda-developers.com/showthread.php?t=2008440. I flashed Clockworkmod touch recovery and installed the latest CM10 Nightly. I ended up installing the standard Clockworkmod recovery (non touch) through ROM manager once my phone was up and running. Everything on my phone was working great until I let my battery run all the way down to the point my phone shut off. I plugged my phone in and it automatically booted to recovery. I waited a little bit for the phone to charge and selected "reboot system now" from recovery. My phone did not boot and only goes to recovery. When it reboots, it briefly flashes a green stripe twice in the upper third of the screen prior to booting all the way but never shows the HTC screen or anything other than recovery. I tried reflashing the ROM in recovery, formatting every partition in recovery, entering fasboot using ADB, rebooting using ADB, and nothing seems to get my phone to do anything other than boot to recovery. I tried running the latest RUU and it fails (presumably because it can't enter fasboot). I tried pressing and holding volume+, -, and the power button at the same time, I tried holding just the volume down button while holding the power button, but no luck so far.
Is there a way to reflash the recovery from ADB while the phone is in recovery? Is there any other way I can force my phone into fastboot? Can I safely use the method in this thread http://forum.xda-developers.com/showthread.php?t=1990043 to "unbrick" my phone by entering commands via ADB shell while in recovery rather than in terminal emulator? Thanks in advance for all the collective XDA wisdom that I'm sure will help get my phone back up and running.
Hey I had the same problem about a week ago. Are you sure you used the latest the RUU file?
chilaca91 said:
Hey I had the same problem about a week ago. Are you sure you used the latest the RUU file?
Click to expand...
Click to collapse
I'm using RUU_Ville_U_ICS_40_S_TMOUS_2.35.531.7_Radio_1.08ts.50.02.16_10.08e.50.04L_release_279577_signed.exe. I don't think it would matter which one I used though because it gives me an error that says it can't connect to the phone.
Try holding down the power button for 10 sec and then let go of the power and hold down the volume button. I had to do this a couple of times until I finally got into the bootloader
Sent from my One S using xda app-developers app
chilaca91 said:
Try holding down the power button for 10 sec and then let go of the power and hold down the volume button. I had to do this a couple of times until I finally got into the bootloader
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Amazing! That did the trick. Thanks a ton for that info. I knew it would be something simple.
I also had a similar problem. Seemed to occur only when I had the USB cable plugged into the phone. Once I removed it, I could then get into fastboot. Once I was in fastboot, I simply plugged the USB cable back in, and everything worked flawlessly.
All that crap you got wouldn't have happened if you use TWRP instead of CWM.
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.
I got this phone used. (Droid Razr HD) Not sure of its history. As far as I know it was all stock until today.
When I found out I could root and unlock the bootloader I did so. Then I wanted to go into recovery and make a backup (yea I know...did that backwards) I powered the device off...hit the volume rocker switch and the power button at the same time and it entered into the Boot Mode selection menu. I hit the volume down to move to the recovery option and then hit the volume up button to select recovery.
At this point the big red M & Dual Core Technology logo appears. Stays there for 1.5 minutes then disappears briefly, comes back on for 15 seconds and then boots the phone normally.
So....I downloaded and installed Rom Manager and had it flash the latest CMW Recovery, turned the phone off to access the newly flashed recovery and the phone again went to the big red M & Dual Core Technology logo set there for 1.5 minutes, disappeared briefly and then booted the phone normally.
So.....I downloaded the lasted CMW Recovery image and used ADB and Fastboot to flash the recovery. Same result. Cannot access the recovery.
So....I downloaded a Stock recovery image and used ADB and Fastboot to flash the stock recover. Same result....cannot access the recovery.
Can someone tell me what I am missing or what I am doing wrong? Or what I can do access recovery.? A rooted phone with an unlocked bootloader isn't much good if you can't access recovery.
Thanks for reading and for any advice you might be able to give.
Jeff
I believe when in the boot loader menu, you need to Volume down to your choice, then Volume up to select the highlighter choice. Pressing power just resets the phone as you experienced.
ESCollins90 said:
I believe when in the boot loader menu, you need to Volume down to your choice, then Volume up to select the highlighter choice. Pressing power just resets the phone as you experienced.
Click to expand...
Click to collapse
Sorry....my op is wrong and has been corrected. You are right, the volume up selects the highlighted choice. Which is the way I was doing it, I just described it wrong.
And my problem still exists, I can't access recovery. Thanks for your reply.
jlstark1 said:
Sorry....my op is wrong and has been corrected. You are right, the volume up selects the highlighted choice. Which is the way I was doing it, I just described it wrong.
And my problem still exists, I can't access recovery. Thanks for your reply.
Click to expand...
Click to collapse
If you haven't tried it already, since you seem to have ADB setup and working, try to use "adb reboot recovery" and see if you have change in luck. If not, my knowledge does not go much further, I hope someone knows how to answer this for you. I can imagine how distraught I'd be.
The only other thing is to ensure you've installed the correct recovery:
Google Dhacker29 and choose the AndroidHosting site, choose msm8960.
(I can't post url's because i've had less than 10 posts... spam thing)
Since you seem to have unlocked bootloader with the most recent case of KitKat make sure you have the "TWRP2710-RAZR-HD_M-KITKAT.img" file.
I will say I didn't use ADB to push mine, I'm not home often, I used Flashify from the Google Play Store. I had no problem with this method.
Hope you can figure it out! Good luck!
ESCollins90 said:
Since you seem to have unlocked bootloader with the most recent case of KitKat make sure you have the "TWRP2710-RAZR-HD_M-KITKAT.img" file.
I will say I didn't use ADB to push mine, I'm not home often, I used Flashify from the Google Play Store. I had no problem with this method.
Click to expand...
Click to collapse
Thanks!! Your 2 suggestions made the difference. Works like a charm!
jlstark1 said:
Thanks!! Your 2 suggestions made the difference. Works like a charm!
Click to expand...
Click to collapse
Awesome! Enjoy your new phone!![emoji1]
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!