when in twrp recovery its stuck/frozen cant swipe or put in pin or flash mods. any help would be appericiated
freddienuxx said:
when in twrp recovery its stuck/frozen cant swipe or put in pin or flash mods. any help would be appericiated
Click to expand...
Click to collapse
Remove lock screen security and set it to swipe. Then boot into twrp a couple of times. If it starts working, then add your security back in.
Badger50 said:
Remove lock screen security and set it to swipe. Then boot into twrp a couple of times. If it starts working, then add your security back in.
Click to expand...
Click to collapse
ok thx gonna try now
freddienuxx said:
ok thx gonna try now
Click to expand...
Click to collapse
thank you so much that worked
freddienuxx said:
thank you so much that worked
Click to expand...
Click to collapse
Happy to help my friend :good:
After helping one of my friends troubleshoot this on his pixel 2 xl we came to the conclusion that twrp doesnt seem to like the phone having a saved fingerprint either. disabling the fingerprint and keeping the password works. we havent tried turning it back on after the first decrypt though, will post after further testing
---------- Post added at 12:55 AM ---------- Previous post was at 12:50 AM ----------
KittyRgnarok said:
After helping one of my friends troubleshoot this on his pixel 2 xl we came to the conclusion that twrp doesnt seem to like the phone having a saved fingerprint either. disabling the fingerprint and keeping the password works. we havent tried turning it back on after the first decrypt though, will post after further testing
Click to expand...
Click to collapse
so during our initial testing we had two fingerprints which seemed to upset twrp. after a successful decrypt we added one single fingerprint and now it decrypts properly
I'm getting this suddenly even though I deleted pin and fingerprints. Maybe I need to return to stock recovery again somehow? Then flash twrp all over again. Anybody know where to get stock recovery?
benjmiester said:
I'm getting this suddenly even though I deleted pin and fingerprints. Maybe I need to return to stock recovery again somehow? Then flash twrp all over again. Anybody know where to get stock recovery?
Click to expand...
Click to collapse
Flash the boot.img. That's where the stock recovery now resides.
Badger50 said:
Flash the boot.img. That's where the stock recovery now resides.
Click to expand...
Click to collapse
Thanks again Badger. It gives me "no command" with the mr. droid in surgery. Is that normal? It at least got rid of TWRP so I can try that again.
benjmiester said:
Thanks again Badger. It gives me "no command" with the mr. droid in surgery. Is that normal? It at least got rid of TWRP so I can try that again.
Click to expand...
Click to collapse
What's the "Mr droid in surgery"?? What gives you no command?? Did you run fastboot flash boot boot.img ??
Badger50 said:
What's the "Mr droid in surgery"?? What gives you no command?? Did you run fastboot flash boot boot.img ??
Click to expand...
Click to collapse
Sorry, yeah I ran fastboot flash boot boot.img, do I need to boot it like the 1st step of installing TWRP? The android symbol with the red triangle and 'no command' is what I get after trying to enter recovery after flashing stock boot (to verify stock recovery was back). I don't see stock recovery though, shows that no command and Droid red triangle instead. I'm still critical unlocked from when I fastboot flashed factory image yesterday.
benjmiester said:
Sorry, yeah I ran fastboot flash boot boot.img, do I need to boot it like the 1st step of installing TWRP? The android symbol with the red triangle and 'no command' is what I get after trying to enter recovery after flashing stock boot (to verify stock recovery was back). I don't see stock recovery though, shows that no command and Droid red triangle instead. I'm still critical unlocked from when I fastboot flashed factory image yesterday.
Click to expand...
Click to collapse
Ah, now I understand. The droid dude in surgery, is the stock recovery. You have to hold power button and volume up simultaneously a couple seconds, then release volume up. It's a little tricky though. You can just fastboot twrp now if you'd like.
Badger50 said:
Ah, now I understand. The droid dude in surgery, is the stock recovery. You have to hold power button and volume up simultaneously a couple seconds, then release volume up. It's a little tricky though. You can just fastboot twrp now if you'd like.
Click to expand...
Click to collapse
So turns out the problem both before and just now when I tried flashing twrp and it was still frozen.... I forgot to flash magisk after flashing the twrp installer zip :crying::crying: It was trying to run TWRP on an unrooted system. Doh! I booted twrp a 3rd time, flashed twrp installer AND magisk. Now all is working fine.
It's the little things that always mess me up :laugh:
benjmiester said:
So turns out the problem both before and just now when I tried flashing twrp and it was still frozen.... I forgot to flash magisk after flashing the twrp installer zip :crying::crying: It was trying to run TWRP on an unrooted system. Doh! I booted twrp a 3rd time, flashed twrp installer AND magisk. Now all is working fine.
It's the little things that always mess me up :laugh:
Click to expand...
Click to collapse
Been there myself more times than I can remember over the last 7 years I've been hacking these things. At least you figured it out ?
Badger50 said:
Been there myself more times than I can remember over the last 7 years I've been hacking these things. At least you figured it out
Click to expand...
Click to collapse
Badger50, you've been a great help and I hope you can come thru again for me. Maybe I'm missing something but I just finished updating my Pixel 2 XL to the June update and went to boot TWRP so I can flash Magisk and install TWRP but I get to the teamwin recovery project 3.2.1-2 splash screen and it's just frozen. I never got to flash anything. Any help is greatly appreciated.
rsnyc said:
Badger50, you've been a great help and I hope you can come thru again for me. Maybe I'm missing something but I just finished updating my Pixel 2 XL to the June update and went to boot TWRP so I can flash Magisk and install TWRP but I get to the teamwin recovery project 3.2.1-2 splash screen and it's just frozen. I never got to flash anything. Any help is greatly appreciated.
Click to expand...
Click to collapse
Do you have screen lock security disabled?
Badger50 said:
Do you have screen lock security disabled?
Click to expand...
Click to collapse
Yes sir. I set it to swipe.
rsnyc said:
Yes sir. I set it to swipe.
Click to expand...
Click to collapse
Did you let the OS boot up once? If so, then shut the phone off, and manually go into bootloader mode, then fastboot into twrp and try again
Badger50 said:
Did you let the OS boot up once? If so, then shut the phone off, and manually go into bootloader mode, then fastboot into twrp and try again
Click to expand...
Click to collapse
I didn't let the phone boot up. I just flashed the update and then ran the command fastboot boot twrp... I will do that and report back.
rsnyc said:
I didn't let the phone boot up. I just flashed the update and then ran the command fastboot boot twrp... I will do that and report back.
Click to expand...
Click to collapse
No worries. Let me know :good:
Related
Here's a video tutorial on how to root your Nexus 10 for noobs!
Windows video tutorial:
Mac video tutorial:
Linux video tutorial:
All the files you need in one zip (adb+SuperSU+fastboot+Windows drivers):
http://downloadandroidrom.com/file/Nexus10/Nexus10RootNew.zip
Step-by-Step tutorial with photos here:
http://nexus10root.com/nexus-10-root/how-to-root-nexus-10-easiest-method/
Also, if you get stuck on bootloop after unlocking bootloader (This happened to me couple times), do a factory reset in stock recovery to fix:
Thanks to shimp208 for the sideload method and working CWM, ChainFire for awesome SuperSU and to all the developers who are worked on CWM recovery!
So the CWM that was just updated by Koushik on CWM does not work properly or does it work? Was asking based on this
While CWM Recovery is still being fixed
Click to expand...
Click to collapse
Edit: There's no driver issue if it were on a Mac right? Especially adb sideloading the CWM SuperSu zip?
How do I flash the stock recovery? CWM isn't working and I tried to update the driver like in the video but couldn't find the "manta" that I needed to update. I'm just stuck in bootloop animation now. I'm downloading the stock image right now to try and flash it back to stock..
johno86 said:
How do I flash the stock recovery? CWM isn't working and I tried to update the driver like in the video but couldn't find the "manta" that I needed to update. I'm just stuck in bootloop animation now. I'm downloading the stock image right now to try and flash it back to stock..
Click to expand...
Click to collapse
If you go into fastboot mode then choose recovery to get to the screen with the red triangle, keep pressing the power button and volume buttons randomly until the stock recovery pops up. From there do a factory reset and it'll work, I just did it to mine!
I flashed the CWM recovery img so when I do what you say it takes me to the bootloader screen and says Downloading. No red triangle. It boots into CWM and then after 20 seconds restarts itself and hits the bootanimation loop. Any clue what to do next? Trying to flash the stock image but having issues using cmds in windows cmd
*edit
I cleared cache through cmd and i got to the red triangle...thank ****ing the lord. DTWAZERE, I will remember tonight. Thank you for your help.
johno86 said:
I flashed the CWM recovery img so when I do what you say it takes me to the bootloader screen and says Downloading. Any clue what to do next? Trying to flash the stock image but having issues getting it into fastboot now...
Click to expand...
Click to collapse
Thing is it will delete the CWM recovery when you leave it so you'll have to reflash it, which is why this is so unstable!
I had the exact same thing as you and this is what I did:
Press the power button to turn it off while it says downloading
Hold both volume buttons down and power on to get into fastboot
Choose recovery
Press power and volume buttons randomly when the red triangle appears until you get stock recovery
Choose Factory Reset
Reboot
You should be able to get back into the rom that way,
to root it you need to boot into fastboot again, reflash the recovery, and sideload the superuser apk
dtwazere said:
Thing is it will delete the CWM recovery when you leave it so you'll have to reflash it, which is why this is so unstable!
I had the exact same thing as you and this is what I did:
Press the power button to turn it off while it says downloading
Hold both volume buttons down and power on to get into fastboot
Choose recovery
Press power and volume buttons randomly when the red triangle appears until you get stock recovery
Choose Factory Reset
Reboot
You should be able to get back into the rom that way,
to root it you need to boot into fastboot again, reflash the recovery, and sideload the superuser apk
Click to expand...
Click to collapse
Yeah this is exactly what I did and it worked. I'll wait on flashing anything until there's a stable recovery. I was fairly confident in what I was doing until that happened. Not being able to input commands from cmd prompt made me sick so I'll wait for a dev to release something that works without having to quickly install the drivers again within a 15-20 second timeframe. Too much stress.
cant boot
I got a huge problem.
I follow the step and going on. Ive seen the done in CWMR. But the tablet cant boot.
It stops in the second animation( X mark) cant boot in os.
Anyone can help me?
lc684760 said:
I got a huge problem.
I follow the step and going on. Ive seen the done in CWMR. But the tablet cant boot.
It stops in the second animation( X mark) cant boot in os.
Anyone can help me?
Click to expand...
Click to collapse
Heh im having the same issue.
lc684760 said:
I got a huge problem.
I follow the step and going on. Ive seen the done in CWMR. But the tablet cant boot.
It stops in the second animation( X mark) cant boot in os.
Anyone can help me?
Click to expand...
Click to collapse
I'm having the same issue. Stuck on the 2nd splash screen with the Nexus Logo.
I received successful messages after every entry.
deevooneh said:
I'm having the same issue. Stuck on the 2nd splash screen with the Nexus Logo.
I received successful messages after every entry.
Click to expand...
Click to collapse
sucks. But we can boot in fastboot and downloading . I think we may have some tricks to fix.
i did everything, and it all went successfully after a few tried. Now i am stuck with the JB X load screen.
How do i get the stock google rom and how do i flash it?
lc684760 said:
sucks. But we can boot in fastboot and downloading . I think we may have some tricks to fix.
Click to expand...
Click to collapse
Ok. Let me know if you figure something out. Hopefully we didnt brick it.
deevooneh said:
Ok. Let me know if you figure something out. Hopefully we didnt brick it.
Click to expand...
Click to collapse
I just called service phone. But goole play agent told me that they didnt know how to deal with that. Its the new device. They dont know much. Damn it!
lc684760 said:
I just called service phone. But goole play agent told me that they didnt know how to deal with that. Its the new device. They dont know much. Damn it!
Click to expand...
Click to collapse
How do we get back to stock? Might need to reattempt this.
If you are stuck on the boot animation (X) screen... power off your device and enter fastboot mode and then type fastboot -w... I has this problem and this fixed it!
NOTE: fastboot -w will wipe your internal storage completely
dtwazere said:
If you go into fastboot mode then choose recovery to get to the screen with the red triangle, keep pressing the power button and volume buttons randomly until the stock recovery pops up. From there do a factory reset and it'll work, I just did it to mine!
Click to expand...
Click to collapse
deevooneh said:
How do we get back to stock? Might need to reattempt this.
Click to expand...
Click to collapse
Stock is here
https://developers.google.com/android/nexus/images#mantarayjop40c
Still need a way to get CWM stable, so we have time to copy to sd
craigacgomez said:
If you are stuck on the boot animation (X) screen... power off you devices and enter fastboot mode and then type fastboot -w... I has this problem and this fixed it!
NOTE: fastboot -w will wipe your internal storage completely
Click to expand...
Click to collapse
THIS WORKED!!
Youre a genius. thanks!
When I try to install the manta drivers manually and tell it to search the same area that it searched and found the android bootloader drivers for fastboot mode it says that the drivers couldn't be found and installed. Am I missing something? Also if i try to do fastboot flash recovery it gives me an error message stating that it cannot determine the image filename for the recovery image.
Well i guess i did it the long way around.
Went to https://developers.google.com/android/nexus/images#mantarayjop40c
and downloaded the Nexus 10 file. extracted, and the actual files in the Nexus10Root folder.
Opened the flash-all.sh and entered each command manually because it was erroring out running the script.
After the 3rd command it booted right into android!
So I clean flashed the newest community edition of Oxygen. Directly after I flashed it I flashed SuperSU. Everything goes well, no big error messages (I edited the updater-script for Oxygen). So I boot into Oxygen, and I can't find root. Everything is working beautifully but there's just no SuperSU. So I reboot to recovery, about to flash the zip again, but I get a black screen. Doesn't go away until I hold the power button for 15 seconds. Rebooted to fastboot, flashed TWRP recovery image. Same result, black screen when booting into recovery. Is there something I'm doing wrong? It's usable but I'd really like root....
Use this recovery http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
daleski75 said:
Use this recovery http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Click to expand...
Click to collapse
Thanks so much!
camcorder123 said:
Thanks so much!
Click to expand...
Click to collapse
No problem.
I've got this same problem. Thanks for the TWRP fix!
Did you manage to get SuperSU / Root to work?
daleski75 said:
Use this recovery http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Click to expand...
Click to collapse
Thanks. It worked.
daleski75 said:
Use this recovery http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Click to expand...
Click to collapse
you are awesome, thanks so much this fixed my issue
recovery black screen and fastboot not working on computer
HI .
I am stuck with this black screen on recovery problem. And fastboot is not working on my system. Please help.
vijaysivakula said:
HI .
I am stuck with this black screen on recovery problem. And fastboot is not working on my system. Please help.
Click to expand...
Click to collapse
If your bootloader is unlocked and you can access the bootloader insteead of recovery just get fastboot working on your computer and you should be able to flash the TWRP listed above.
Fastboot not working
HermitDash said:
If your bootloader is unlocked and you can access the bootloader insteead of recovery just get fastboot working on your computer and you should be able to flash the TWRP listed above.
Click to expand...
Click to collapse
Fastboot not working on my office laptop. Funnily, it used to work earlier. Could someone help me with that? Or I will flash it over the weekend when i am home and revert to complete stock. The Community Build did not seem very attractive or useful in the few days I tried.
vijaysivakula said:
Fastboot not working on my office laptop. Funnily, it used to work earlier. Could someone help me with that? Or I will flash it over the weekend when i am home and revert to complete stock. The Community Build did not seem very attractive or useful in the few days I tried.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2317790
Minimal ADB and Fastboot.
Then just install drivers for your phone or do a search and you'll find it for the OnePlus 3
Worked For me too!
camcorder123 said:
So I clean flashed the newest community edition of Oxygen. Directly after I flashed it I flashed SuperSU. Everything goes well, no big error messages (I edited the updater-script for Oxygen). So I boot into Oxygen, and I can't find root. Everything is working beautifully but there's just no SuperSU. So I reboot to recovery, about to flash the zip again, but I get a black screen. Doesn't go away until I hold the power button for 15 seconds. Rebooted to fastboot, flashed TWRP recovery image. Same result, black screen when booting into recovery. Is there something I'm doing wrong? It's usable but I'd really like root....
Click to expand...
Click to collapse
Helped me too, thanks big time
LunaticWinchester said:
Helped me too, thanks big time
Click to expand...
Click to collapse
Got same issue. Notify me if there is any solutions...thx.
Thanks work like a charm!
Sorry for reviving this thread, but I managed to solve my problem with this solution. however after a while, because of some problems I booted into recovery, and after seeing the TWRP logo the phone goes black and I can't do anything. I believe I might have killed my phone, but does anyone have some idea?
coyotejodido said:
Sorry for reviving this thread, but I managed to solve my problem with this solution. however after a while, because of some problems I booted into recovery, and after seeing the TWRP logo the phone goes black and I can't do anything. I believe I might have killed my phone, but does anyone have some idea?
Click to expand...
Click to collapse
Plz check some of my older posts. I posted a stock recovery Link. Use that and you'll be able to boot just fine.
Sent from my ONEPLUS A3003 using Tapatalk
HermitDash said:
If your bootloader is unlocked and you can access the bootloader insteead of recovery just get fastboot working on your computer and you should be able to flash the TWRP listed above.
Click to expand...
Click to collapse
I have unlocked my bootloader. when i flashed twrp it showed a blank screen it is not tuning on after holding the power button for 20 min. please help
can anyone help me? i have flashed H2os with modified twrp and when i have flashed the rom i have reflashed the original twrp.. now my phone is working but op3 dont want to boot into recovery.. oneplus show black screen when trying booting twrp.. i dont have root.
i have tryed to flash twrp with the toolkit, it flash right but it shows black screen,
thank you!
Go to blusparks kernel thread from there download the latest recovery. Boot your phone into fastboot, then flash that recovery. Boot into recovery then flash whatever you wish!
Here is the recovery:
http://forum.xda-developers.com/devd...t/dl/?id=21065
ajaysoranam said:
Go to blusparks kernel thread from there download the latest recovery. Boot your phone into fastboot, then flash that recovery. Boot into recovery then flash whatever you wish!
Here is the recovery:
http://forum.xda-developers.com/devd...t/dl/?id=21065
Click to expand...
Click to collapse
It would be good to flash flash twrp couple of times just to make sure, just run the comand 3-4 times.
nemexs said:
It would be good to flash flash twrp couple of times just to make sure, just run the comand 3-4 times.
Click to expand...
Click to collapse
That's like pressing the elevator button once and then pressing it a couple of times more, just in case.
But we've all done it.
ajaysoranam said:
Go to blusparks kernel thread from there download the latest recovery. Boot your phone into fastboot, then flash that recovery. Boot into recovery then flash whatever you wish!
Here is the recovery:
http://forum.xda-developers.com/devd...t/dl/?id=21065
Click to expand...
Click to collapse
Dead link?
daviss101 said:
Dead link?
Click to expand...
Click to collapse
here you go
http://forum.xda-developers.com/devdb/project/dl/?id=21065
I have reflashed the modified twrp and all good! Big thanks anyway!
diegololol said:
can anyone help me? i have flashed H2os with modified twrp and when i have flashed the rom i have reflashed the original twrp.. now my phone is working but op3 dont want to boot into recovery.. oneplus show black screen when trying booting twrp.. i dont have root.
i have tryed to flash twrp with the toolkit, it flash right but it shows black screen,
thank you!
Click to expand...
Click to collapse
Did you get this fixed? Im having the same issue
hawki said:
Did you get this fixed? Im having the same issue
Click to expand...
Click to collapse
Read before posting. The answer is just above your post.
Here are the steps that got me to where I am.
1. Stock Pixel XL March 2017
2. Installed TWRP
3. Installed SU
4. All worked correctly for the last month
5. Saw that there was a new April release
a. It would not install as I was rooted
b. I installed the April OTA using TWRP
c. Rebooted
6. Saw that I was no longer rooted
7. Tried to go to Bootloader
8. Got dead droid with no command error
9. Went to recovery (Power + up vol) to enter sideload
10. Sideloaded the April updated
11. Rebooted
a. Same no command error
b. Went to recovery (Power + up vol) to enter factory restore
c. Rebooted
12. Tried to go into boot loader
a. Same no command error
13. Problem is that twrp was not asking for pattern And would not install correctly with image file. Solution was to keep loading the twrp image file until it asks for pattern. Then follow standard twrp /su instructions.
Thanks.
Power device off, use key combo (power+voldown) to boot bootloader. Fastboot flash stock boot.img to both slot a and b. Then reboot, take the OTA, or sideload it. Reboot. Now reboot to bootloader, fastboot boot TWRP, then reboot to twrp. Now you can flash TWRP to keep it as the recovery, or just su then reboot. Should be good.
Sent from my Pixel XL using Tapatalk
This should be posted under Q&A not development
wyrdtrtle said:
Power device off, use key combo (power+voldown) to boot bootloader. Fastboot flash stock boot.img to both slot a and b. Then reboot, take the OTA, or sideload it. Reboot. Now reboot to bootloader, fastboot boot TWRP, then reboot to twrp. Now you can flash TWRP to keep it as the recovery, or just su then reboot. Should be good.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Bootloader does not load.
When you get the dead Droid just hit vol up, no power button.
Sent from my Pixel XL using Tapatalk
Then what?
bschatzow said:
Then what?
Click to expand...
Click to collapse
I think I know where you went wrong you installed an incremental OTA with TW RP. If I'm not mistaken that new firmware had an updated bootloader and I believe that's dangerous to do. You may be out of luck
Why would the built in factory restore fix it?
bschatzow said:
Why would the built in factory restore fix it?
Click to expand...
Click to collapse
Can you get into fastboot?
So no bootloader.
Just my thoughts. I don't know if that's even possible.
Isn't it possible to edit the ota script to flash a bootloader?
Or even make a full factory update like this?
To use fastboot you need to be in bootloader mode.
mikaole said:
So no bootloader.
Just my thoughts. I don't know if that's even possible.
Isn't it possible to edit the ota script to flash a bootloader?
Or even make a full factory update like this?
Click to expand...
Click to collapse
If it is, I don't know how. I would need it to be able to load from Sideload.
Does phone boot at all? To OS?
Yes it does. Only thing not working is bootloader. Without out this I can't root.
bschatzow said:
Yes it does. Only thing not working is bootloader. Without out this I can't root.
Click to expand...
Click to collapse
Ok..if phone boots ur bootloader is still there. Phone wouldnt boot without it. You on stock rom? Hit me up on hangouts and I will try to help you if you want. For the sake of time. Im sure you wanna get this resolved ASAP.
Sent you a pm requesting contact info.
Moderator Close
Worked for a long time with BDogg718. He generously spent a great deal of his time with me and opened several Chats with Developers and No one had a solution. He is very knowledgeable and really did not want to give up. For now the solutions seems to be send it back to Google and get a replacement. It would be nice if someone could talk to Google, as a phone that has a recovery built in firmware should be able to restore itself. The dual slots seems to be a problem for them as well.
I think I had the same thing happen with me! I installed the update via TWRP. The update installation seemed to crash at the end, resulting in a reboot. The phone did install 7.1.2 successfully, but I lost root and the ability to successfully boot into any recovery. I tried flashing TWRP again, but it failed "FAILED (remote: partition recovery doesn't exist). It appeared to attempt to flash it into slot "_b", if that means anything.
TWRP will not boot on 7.1.2. At least that's the conclusion formed last night in #twrp while the devs were working with someone else with this issue. I don't think they know why yet, but I doubt it will be overly long til they figure it out.
Sent from my Pixel XL using Tapatalk
Glad to hear someone is on the case. I will be sure to send a few shekels their way for my clumsiness.
I am no longer able to boot into my recovery. TWRP nor stock / default. I am on a custom ROM. I am on 7.1.2 root with magisk 12. I have tried all the fastboot commands to live boot into recovery. I have tried TWRP official app. I have tried FlashFire. Everytime I try to boot into my recovery my phone just reboots back into the OS.
Wrong section
Hacker101 said:
I am no longer able to boot into my recovery. TWRP nor stock / default. I am on a custom ROM. I am on 7.1.2 root with magisk 12. I have tried all the fastboot commands to live boot into recovery. I have tried TWRP official app. I have tried FlashFire. Everytime I try to boot into my recovery my phone just reboots back into the OS.
Click to expand...
Click to collapse
So you have tried booting into the bootloader and entered "fastboot boot twrp.img" in adb?
This happens to me all the time. Using the advanced reboot menu on my ROM or "adb reboot recovery" while connected to my PC just results in the phone booting back into the OS. Pretty annoying. It has to have something to do with the Slots.
Anyways, to get around this, disconnect the phone from any power source, turn the phone completely off, wait 5-10 seconds, then press and hold Vol Down + Power to get to the bootloader. Then use the volume keys to select Recovery Mode and press power to boot into recovery. This method works every time for me. If this does not work for you or results in some other screen/error/whatever other than booting into TWRP, then you must live boot (as suggested in the above post) into TWRP and flash TWRP RC2.
Alcolawl said:
This happens to me all the time. Using the advanced reboot menu on my ROM or "adb reboot recovery" while connected to my PC just results in the phone booting back into the OS. Pretty annoying. It has to have something to do with the Slots.
Anyways, to get around this, disconnect the phone from any power source, turn the phone completely off, wait 5-10 seconds, then press and hold Vol Down + Power to get to the bootloader. Then use the volume keys to select Recovery Mode and press power to boot into recovery. This method works every time for me. If this does not work for you or results in some other screen/error/whatever other than booting into TWRP, then you must live boot (as suggested in the above post) into TWRP and flash TWRP RC2.
Click to expand...
Click to collapse
I have done this 100+ times. Booting into recovery using any method does not work. Including live booting.
Hacker101 said:
I have done this 100+ times. Booting into recovery using any method does not work. Including live booting.
Click to expand...
Click to collapse
If you are still able to access the bootloader, I would suggest flashing a factory image (removing -w if you want to keep your data) with the flash-all.bat. It sounds as if your recovery partition has been removed somehow making it unable to be booted into. Perhaps flashing the factory image will fix your partitions and solve the problem. It's worth a shot I guess if you can't access it at all. Good luck to you!
TheBobMiller said:
If you are still able to access the bootloader, I would suggest flashing a factory image (removing -w if you want to keep your data) with the flash-all.bat. It sounds as if your recovery partition has been removed somehow making it unable to be booted into. Perhaps flashing the factory image will fix your partitions and solve the problem. It's worth a shot I guess if you can't access it at all. Good luck to you!
Click to expand...
Click to collapse
How am I supposed to flash a factory image if I can't flash anything? Plus I am on a Linux computer not windows. Isn't .bat windows? Would I need a .sh type of command?
Hacker101 said:
How am I supposed to flash a factory image if I can't flash anything? Plus I am on a Linux computer not windows. Isn't .bat windows? Would I need a .sh type of command?
Click to expand...
Click to collapse
The factory image flashes in bootloader mode and should correct any issue you have. You have to install the Android SDK platform on your Linux machine. Go to this link https://developer.android.com/studio/index.html#tos-header and scroll down to almost the bottom for just the command line tools and follow the instructions to install. Then go to https://developers.google.com/android/images and download the factory image you want to flash and follow the instructions in that link to flash. I don't have a Linux machine myself, but I believe the process is fairly similar and it should work just fine.
TheBobMiller said:
The factory image flashes in bootloader mode and should correct any issue you have. You have to install the Android SDK platform on your Linux machine. Go to this link https://developer.android.com/studio/index.html#tos-header and scroll down to almost the bottom for just the command line tools and follow the instructions to install. Then go to https://developers.google.com/android/images and download the factory image you want to flash and follow the instructions in that link to flash. I don't have a Linux machine myself, but I believe the process is fairly similar and it should work just fine.
Click to expand...
Click to collapse
Sweet I'll give it a try when I get home later. We got a nasty storm blowing in so I may not get to it today. Also I'll remember to Thank that post tomorrow lol limited to eight a day. When you have 100+ people helping you out at once it's hard to thank each one.
Hacker101 said:
Sweet I'll give it a try when I get home later. We got a nasty storm blowing in so I may not get to it today. Also I'll remember to Thank that post tomorrow lol limited to eight a day. When you have 100+ people helping you out at once it's hard to thank each one.
Click to expand...
Click to collapse
Don't worry about the Thanks, cause I'm sure others have contributed more. Sorry I'm not more familiar with the Linux instructions!
Ok having the same issue as OP. A and B slots do not allow me to boot into recovery mode. It just immediately restarts as soon as the white Google splash screen appears. I have just done a factory reset with N2G47O. After complete, the stock default recovery works fine. I booted TWRP from fast boot to install the latest, issue came again. Trying to get into recovery mode just causes it to bootloop until you hold the volume down button to get bootloader up to boot to system instead. I am downloading and will flash NOF27D (last 7.1.1) to see if I can reinstall twrp from that. I can confirm that installing twrp when on that image worked. Will report back...
Hacker101 said:
Sweet I'll give it a try when I get home later. We got a nasty storm blowing in so I may not get to it today. Also I'll remember to Thank that post tomorrow lol limited to eight a day. When you have 100+ people helping you out at once it's hard to thank each one.
Click to expand...
Click to collapse
jkashuba07 said:
Ok having the same issue as OP. A and B slots do not allow me to boot into recovery mode. It just immediately restarts as soon as the white Google splash screen appears. I have just done a factory reset with N2G47O. After complete, the stock default recovery works fine. I booted TWRP from fast boot to install the latest, issue came again. Trying to get into recovery mode just causes it to bootloop until you hold the volume down button to get bootloader up to boot to system instead. I am downloading and will flash NOF27D (last 7.1.1) to see if I can reinstall twrp from that. I can confirm that installing twrp when on that image worked. Will report back...
Click to expand...
Click to collapse
I forgot to ask if you were on the latest May security update. If you were on that version then you need to use the Android Verified Signer.zip from chainfire after you flash twrp. What version are you running?
jkashuba07 said:
Ok having the same issue as OP. A and B slots do not allow me to boot into recovery mode. It just immediately restarts as soon as the white Google splash screen appears. I have just done a factory reset with N2G47O. After complete, the stock default recovery works fine. I booted TWRP from fast boot to install the latest, issue came again. Trying to get into recovery mode just causes it to bootloop until you hold the volume down button to get bootloader up to boot to system instead. I am downloading and will flash NOF27D (last 7.1.1) to see if I can reinstall twrp from that. I can confirm that installing twrp when on that image worked. Will report back...
Click to expand...
Click to collapse
Ok, I can confirm after doing factory reset to NOF27D I was able to reinstall TWRP and boot to it successfully
---------- Post added at 04:57 PM ---------- Previous post was at 04:56 PM ----------
TheBobMiller said:
I forgot to ask if you were on the latest May security update. If you were on that version then you need to use the Android Verified Signer.zip from chainfire after you flash twrp. What version are you running?
Click to expand...
Click to collapse
Yes I was on May.. Do you have link to Verified Signer?
jkashuba07 said:
Ok, I can confirm after doing factory reset to NOF27D I was able to reinstall TWRP and boot to it successfully
---------- Post added at 04:57 PM ---------- Previous post was at 04:56 PM ----------
Yes I was on May.. Do you have link to Verified Signer?
Click to expand...
Click to collapse
Here is the link to the verifiedbootsigner.zip from Chainfire: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Make sure you give him some Thanks and Donate if possible! He has earned plenty of both from all of us Android users!
Instructions: Anytime you flash anything that affects the boot partition (ie. twrp, rom, kernel, etc), make sure to flash the boot signer zip at the end of the flashing before a reboot.
TheBobMiller said:
Here is the link to the verifiedbootsigner.zip from Chainfire: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Make sure you give him some Thanks and Donate if possible! He has earned plenty of both from all of us Android users!
Instructions: Anytime you flash anything that affects the boot partition (ie. twrp, rom, kernel, etc), make sure to flash the boot signer zip at the end of the flashing before a reboot.
Click to expand...
Click to collapse
Thank you, and will do.. yes chainfire has done a lot of good work, definitely have appreciated him over the years
TheBobMiller said:
Here is the link to the verifiedbootsigner.zip from Chainfire: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Make sure you give him some Thanks and Donate if possible! He has earned plenty of both from all of us Android users!
Instructions: Anytime you flash anything that affects the boot partition (ie. twrp, rom, kernel, etc), make sure to flash the boot signer zip at the end of the flashing before a reboot.
Click to expand...
Click to collapse
That's only for May and so on correct? I am on April. Heard nasty things form root uses about root screwing up, bootloader problems, etc. So I stayed away from May and stayed on April.
Hacker101 said:
That's only for May and so on correct? I am on April. Heard nasty things form root uses about root screwing up, bootloader problems, etc. So I stayed away from May and stayed on April.
Click to expand...
Click to collapse
Correct. Only the may bootloader requires the extra zip file to be flashed. I am still on April but I have heard people not having any problems and some having nothing but problems from May. I think I'm going to give it a try tomorrow and see how it goes.
Edit: Tried the May bootloader and couldn't get it to boot a custom rom or TWRP, so I went back to April after flashing the Android O Beta and playing with it for a couple of hours. I feel that the Beta is still too early for a daily driver, but it was nice to mess around with some of the features we will have once this OS is released.