I had rooted my Oneplus 2 and installed TWRP two years back, and was on default Oxygen OS [Android 5.1] and did not install update since then. My TWRP version number was 2.8.7.0. Now as of yesterday, the phone exhibited an unusual behaviour, apps closing, dialer and message app closing etc. So I decided to update it to Android 7.1 ROM. I took a backup of required data.
The rom I was planning to flash was RR 5.85 along with TWRP 3.1.1.0-oneplus2.img as updated on TWRP website. So I began with flashing TWRP version. I rebooted in my recovery [TWRP 2.8.7.0]. Selected the file from .img menu, and selected Recovery partition when asked to. It gave me a success prompt. And I selected an option for TWRP to reboot to recovery. It was stuck at OnePlus screen [the one which pops up when we restart] with the capacitive lights [Button Lights] on the entire time. I waited for 10 minutes, but without recourse. So I loaded it into fastboot and flashed an earlier version of TWRP recovery twrp-3.0.2-2-oneplus2.img using [fastboot flash recovery twrp-3.0.2-2-oneplus2.img] command. I again tried to reboot into recovery mode, yet the same problem was displaying.
Please help guys. Did I miss something here such as bootloader upgrade or something like that, since I had not performed any updates for 2 Years.
Edit: Never mind fixed it. Please feel free to delete this thread
x0nar said:
I had rooted my Oneplus 2 and installed TWRP two years back, and was on default Oxygen OS [Android 5.1] and did not install update since then. My TWRP version number was 2.8.7.0. Now as of yesterday, the phone exhibited an unusual behaviour, apps closing, dialer and message app closing etc. So I decided to update it to Android 7.1 ROM. I took a backup of required data.
The rom I was planning to flash was RR 5.85 along with TWRP 3.1.1.0-oneplus2.img as updated on TWRP website. So I began with flashing TWRP version. I rebooted in my recovery [TWRP 2.8.7.0]. Selected the file from .img menu, and selected Recovery partition when asked to. It gave me a success prompt. And I selected an option for TWRP to reboot to recovery. It was stuck at OnePlus screen [the one which pops up when we restart] with the capacitive lights [Button Lights] on the entire time. I waited for 10 minutes, but without recourse. So I loaded it into fastboot and flashed an earlier version of TWRP recovery twrp-3.0.2-2-oneplus2.img using [fastboot flash recovery twrp-3.0.2-2-oneplus2.img] command. I again tried to reboot into recovery mode, yet the same problem was displaying.
Please help guys. Did I miss something here such as bootloader upgrade or something like that, since I had not performed any updates for 2 Years.
Edit: Never mind fixed it. Please feel free to delete this thread
Click to expand...
Click to collapse
How did you fix it? My brother's phone has the same problem.
Sent from my Nexus 6 using Tapatalk
merikgvr401 said:
How did you fix it? My brother's phone has the same problem.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
You have to install marshmallow firmware first.
Best option would be to go back to the working TWRP version, flash oxygenos, reboot to Oxygen once, flash new recovery in fastboot, reboot recovery, flash rom
merikgvr401 said:
How did you fix it? My brother's phone has the same problem.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I don't know if this does anything different, but here's what worked for me
1. Ensure that device enters into fastboot mode
2. "fastboot flash recovery recovery.img"
3. **IMP** After your flashing is successful, directly enter the device into recovery mode by pressimg Power (+) Vol Down button.
4. Now a TWRP prompt shall appear asking your permit for modifications, swipe yes.
Note that: I'm not sure if this makes a difference, but earlier I rebooted after Fastboot and then entered into recovery, but the key was to directly enter into recovery after fastboot.
Let me know if that works for you.
Related
Hey XDA, Recently installed Paranoid Android coming from Chroma and it's not stuck in a boot loop. I can boot just fine every time besides the annoying corruption google warning, but no matter how many times I try to install TWRP it just won't let me boot into recovery. I'm using WugFresh's NRT kit. Can't seem to figure it out. Any suggestions?
carterl96 said:
Hey XDA, Recently installed Paranoid Android coming from Chroma and it's not stuck in a boot loop. I can boot just fine every time besides the annoying corruption google warning, but no matter how many times I try to install TWRP it just won't let me boot into recovery. I'm using WugFresh's NRT kit. Can't seem to figure it out. Any suggestions?
Click to expand...
Click to collapse
My suggestion is for you to fastboot flash the TWRP recovery image instead of using a toolkit. You cant see the inner workings of a toolkit and have no idea of what it is doing. The toolkit could be using the wrong commands to install a recovery image to your 6P. Go to www.twrp.me and search for the recovery image for your specific device and download the file. Next, rename the file to recovery.img Then, on your PC, navigate to the folder where you downloaded the TWRP image. Open a command prompt in that folder by pressing and holding the SHIFT KEY + RIGHT CLICK on your mouse and select OPEN A COMMAND WINDOW HERE. Boot to the bootloader on your device and connect it to your PC. Then type this:
fastboot flash recovery recovery.img
Then type this:
fastboot reboot bootloader
fastboot reboot recovery
Here is the link to download TWRP for your Nexus 6P
This will reboot your device to TWRP
All of this is based on the assumption that you have a working ADB installation and unlocked the bootloader and have USB Debugging turned on in DEVELOPER OPTIONS.
Sent from my Nexus 6 using XDA-Developers mobile app
Same thing, successful install and it won't open. Just shows the dead android when going to recovery.
carterl96 said:
Same thing, successful install and it won't open. Just shows the dead android when going to recovery.
Click to expand...
Click to collapse
You get the same results after fastboot flashing the TWRP image? I'd say your next step is to start fresh by fastboot flashing the factory images to return to a fully stock state. Then fastboot flash TWRP again.
Sent from my Nexus 6 using XDA-Developers mobile app
Do not boot directly into system after flashing the custom recovery.
After flashing boot into TWRP. I remember on previous devices that I owned that if you do not boot into the custom recovery after flashing it, you revert to the factory recovery.
Just a thought
tech_head said:
Do not boot directly into system after flashing the custom recovery.
After flashing boot into TWRP. I remember on previous devices that I owned that if you do not boot into the custom recovery after flashing it, you revert to the factory recovery.
Just a thought
Click to expand...
Click to collapse
I thought about that too. What is probably happening is his custom recovery is being patched by the ROM each time he boots into recovery. Thanks for picking up on that. I forgot to include that in my last post.
Sent from my Nexus 6 using XDA-Developers mobile app
tech_head said:
Do not boot directly into system after flashing the custom recovery.
After flashing boot into TWRP. I remember on previous devices that I owned that if you do not boot into the custom recovery after flashing it, you revert to the factory recovery.
Just a thought
Click to expand...
Click to collapse
That's correct. After flashing TWRP the next step is reboot into the bootloader using the volume keys and power key , then from there boot into recovery using the volume keys and power key, then the phone can be rebooted from TWRP into Android and then after that TWRP should stick.
If the boot image is not patched, the ROM will overwrite TWRP once you reboot. flashing latest SU from TWRP will prevent this.
Thanks for all the replies guys! All the advice combined got it to work. I did some more research and found that Paranoid doesn't actually come preprooted like all the other roms I've been used to. So using the tool kit I just had it root it with the latest SuperSu and also flash a custom recovery. It has booted into TWRP no problems now a few times. Hopefully it will stay like this. Will keep everyone posted and appreciate the advice. Thanks XDA!
Hello folks,
today I updated my TWRP with help of the adb-console on my Nexus 6P from TWRP 3.0.2-2 to 3.0.3-0 and after rebooting into twrp everything was fine as it told me that the new version was correctly installed. After clicking to reboot to system the device start again in recovery.
I tried to install TWRP 3.0.2-2 and even the stock recovery.img extracted from the new images, but I cannot get into my system. The phone reboots only in TWRP 3.0.3-0
Any help is appreciated. Thanks in advance!
Regards
dergoce
Did you flash anything like a ROM or an .img. if there is no system image it will continue to go back to recovery
No, only flashed the twrp-3.0.3-0-angler.img file. Nothing else. My idea why it has gone wrong is that I rebooted to fastboot mode with an app by antaresone. The app is called quick reboot.
Now I reflashed the hole stock image and it works again.
Conclusion: be careful when flashing anything if you not shut down the phone and manually started fastboot mode by volume down + power button!
dergoce said:
No, only flashed the twrp-3.0.3-0-angler.img file. Nothing else. My idea why it has gone wrong is that I rebooted to fastboot mode with an app by antaresone. The app is called quick reboot.
Now I reflashed the hole stock image and it works again.
Conclusion: be careful when flashing anything if you not shut down the phone and manually started fastboot mode by volume down + power button!
Click to expand...
Click to collapse
Are you using 7.1.1? Were you enrolled in BETA Program as well?
Yes 7.1.1 but no, I am not in beta anymore.
Hi, hope you can help solve the problem that happened with my Moto E4 "woods". Installing TWRP recovery (TWRP-3.2.1.-0_woods_UNOFFICIAL.img) went smoothly via ADB fastboot flash recovery etc. The phone rebooted however in "Orange State- your device has been unlocked and can't be trusted". Having searched the internet the solution seemed to be to prevent the phone from installing it's own recovery again by getting it to reboot via ADB with the command "fastboot boot ....recovery.img (the name of the TWRP image). It does so succesfully by first downloading "boot.img" and then the same thing happened as before, it boots into the unlocked orange state warning. The phone still has the stock rom on it and will boot into that normally once I've removed the battery and put it back in. But I have no recovery at all now, not the stock recovery either. Pressing volume down and power gets me into adb connection, and volume up into the warning. Any solutions? Anyone else had the same problem? Thanks!
[email protected] said:
Hi, hope you can help solve the problem that happened with my Moto E4 "woods". Installing TWRP recovery (TWRP-3.2.1.-0_woods_UNOFFICIAL.img) went smoothly via ADB fastboot flash recovery etc. The phone rebooted however in "Orange State- your device has been unlocked and can't be trusted". Having searched the internet the solution seemed to be to prevent the phone from installing it's own recovery again by getting it to reboot via ADB with the command "fastboot boot ....recovery.img (the name of the TWRP image). It does so succesfully by first downloading "boot.img" and then the same thing happened as before, it boots into the unlocked orange state warning. The phone still has the stock rom on it and will boot into that normally once I've removed the battery and put it back in. But I have no recovery at all now, not the stock recovery either. Pressing volume down and power gets me into adb connection, and volume up into the warning. Any solutions? Anyone else had the same problem? Thanks!
Click to expand...
Click to collapse
When you're in bootloader, keep pressing volume button until it says recovery. Then tap power. If you already fastboot flashed recovery, no need to fastboot boot recovery recovery.img. just boot to bootloader and tap volume until you see recovery, then tap power.
madbat99 said:
When you're in bootloader, keep pressing volume button until it says recovery. Then tap power. If you already fastboot flashed recovery, no need to fastboot boot recovery recovery.img. just boot to bootloader and tap volume until you see recovery, then tap power.
Click to expand...
Click to collapse
Thanks for your reply and thinking with me, but like I wrote, all there is left is the option to use ADB. Pressing volume up and power no longer gets me into a choice menu, only a black screen with small white letters telling me to attach a cable.
No tapping whatsoever will change that. Volume up gets the orange state message again. So....
You need to flash the old recovery first ....from one of my threads ..follow full guide by flash no dm-verity ..THEN install new recovery via old twrp recovery ...the "NEW" recovery has errors so be warned :good:that will work
Go look in one of my guides for woods for old files
KevMetal said:
You need to flash the old recovery first ....from one of my threads ..follow full guide by flash no dm-verity ..THEN install new recovery via old twrp recovery ...the "NEW" recovery has errors so be warned :good:that will work
Go look in one of my guides for woods for old files
Click to expand...
Click to collapse
Thank you for taking the time to help out! Today I somehow got lucky after I reflashed it again, after having spent the morning deciphering the Chinese recovery which occasionally appeared. Rebooting into recovery inside TWRP held it stable. I manage to flash one custom rom, Dot Os, the Lineage OS for Moto E4 Woods got a TWRP message the zip wasn't correct (though I trust it was) and my backup made by TWRP did not restore. Is this what you mean by the errors? Very lucky to have a working Dot Os, and maybe I'll wait until an official TWRP is available now. Since I lost it again by forgetting to flash SuperSu again at the install of the custom rom....
Will look through your posts to find the guide with the files to have them at the ready Happy New Year's Eve!
[email protected] said:
Thank you for taking the time to help out! Today I somehow got lucky after I reflashed it again, after having spent the morning deciphering the Chinese recovery which occasionally appeared. Rebooting into recovery inside TWRP held it stable. I manage to flash one custom rom, Dot Os, the Lineage OS for Moto E4 Woods got a TWRP message the zip wasn't correct (though I trust it was) and my backup made by TWRP did not restore. Is this what you mean by the errors? Very lucky to have a working Dot Os, and maybe I'll wait until an official TWRP is available now. Since I lost it again by forgetting to flash SuperSu again at the install of the custom rom....
Will look through your posts to find the guide with the files to have them at the ready Happy New Year's Eve!
Click to expand...
Click to collapse
Don't forget to join us on telegram
We have a lot going on and if we chat via one central chat development , bug fixing and general help happens fast .
https://t.me/joinchat/G3XDFEO7AR4fGdyBRfwVOw
http://telegra.ph/woods-development-01-07
twrp for 1762 ?
I can't seem to find TWRP-3.2.1.-0_woods_UNOFFICIAL.img annywhere on the internet
I found this but i don't realy trust that site.
https://romprovider.com/2017/12/twrp-3-2-0-moto-e4-xt1762-woods/
I installed TWRP custom recovery on my Nexus 6P. I was able to boot into it ONCE. When i next tried to enter Recovery, i get a screen showing the Android Robot and the following statement: NO COMMAND
I tried to re-install TWRP using adb twice, but the result is the same.
How can i either fix TWRP, or re-install the stock recovery
I am basically a beginner here, so any help would be appreciated
If you installed the stock system image and then booted into it, it likely automatically reinstalled stock recovery also. I don't know why it does that, but it does. This is why I usually just reinstall TWRP again after each monthly update is completed.
You should use fastboot to install the images, not adb. The command should look like:
fastboot flash recovery twrp.img
I think i just worded it wrong - I used the above command (fastboot flash recovery twrp.img) to install twrp, and then, when i couldn't get back into recovery (Power - Volume Up combo just lest to screen that stated "No Command".), i used the fastboot flash recovery twrp.imp twice to try to re-install TWRP, but it didn't work
I also downloaded the latest stock Oreo ROM, copied the recovery.img file, and used fastboot.flash.recovery.img to try to re-install the stock recovery, but that didn't work either
The once time that TWRP work, it asked it I wanted to use TWRP is read only, to twice i selected NO (don't know if this matters)
Any other suggestions to fix TWPR, or re-install the stock recovery image???
When you say it didn't work, can you expand on that? Was there an error or anything?
hmodiano said:
I think i just worded it wrong - I used the above command (fastboot flash recovery twrp.img) to install twrp, and then, when i couldn't get back into recovery (Power - Volume Up combo just lest to screen that stated "No Command".), i used the fastboot flash recovery twrp.imp twice to try to re-install TWRP, but it didn't work
I also downloaded the latest stock Oreo ROM, copied the recovery.img file, and used fastboot.flash.recovery.img to try to re-install the stock recovery, but that didn't work either
The once time that TWRP work, it asked it I wanted to use TWRP is read only, to twice i selected NO (don't know if this matters)
Any other suggestions to fix TWPR, or re-install the stock recovery image???
Click to expand...
Click to collapse
If you want TWRP to stick, you need to flash either SuperSU or magisk. The Android with the exclamation mark is what stock recovery looks like.
Once you have TWRP installed and wish to keep it, you don't need to flash stock recovery in the monthly update. Just boot into TWRP after flashing update and root again.
chaoticyeshua said:
When you say it didn't work, can you expand on that? Was there an error or anything?
Click to expand...
Click to collapse
When the phone is turned on, it never progresses beyond the first screen. No error codes, it just does not proceed to boot up.
I had to buy a new phone (need it for business, but i given up on trying to install Resurrection Remix on the Nexus 6P, which was the reason I was trying to install TWPR and SuperSU. So far, I have only accomplished turning the phone into a brick door stop!!!
hmodiano said:
When the phone is turned on, it never progresses beyond the first screen. No error codes, it just does not proceed to boot up.
I had to buy a new phone (need it for business, but i given up on trying to install Resurrection Remix on the Nexus 6P, which was the reason I was trying to install TWPR and SuperSU. So far, I have only accomplished turning the phone into a brick door stop!!!
Click to expand...
Click to collapse
Use Magisk it's the better solution for root. Never had boot up issues with it just stock you have to boot once through before flashing. Custom ROMs you can flash right away.
I stupidly tried using franco's app to flash cleanKernel on my rooted phone on 9.0.11, it failed of course and now can't boot my phone. I'm able to fastboot boot twrp.img but I'm not sure what is needed next. I've downloaded the full 9.0.11 ota file thinking something in it (or all of it) needs to be flashed from twrp. Afraid to do anything at this point for fear of losing data. Any tips are appreciated.
I've downloaded mauronofrio's rom-stock-fastboot utility but see he says it will clear data. I'm assuming all the .bat files will do this. Any way to avoid clearing internal storage?
soundneedle said:
From bootloader screen, using fastboot boot twrp.zip results in OP going to "Fastboot Mode" screen...and staying there. The zip is pushed to the phone but won't boot into TWRP. This started after I stupidly tried using franco's app to flash cleanKernel on my rooted phone. It failed of course and now can't boot my phone. My phone recently updated itself to 9.0.11, fyi.
Any ideas on how to fix this boot issue? Is it just a matter of flashing something from the full ota 9.0.11 file---some img file or something?
Click to expand...
Click to collapse
Wouldn't you want to be using a twrp.img not .zip?
fastboot boot twrp.img
Boot twrp from the img and then flash the zip once twrp boots?
I was able to recover...thank god. Just used mauronofrio's flash utility. Removed the "-w" flag from the flash-all.bat file and all is good.
Stuck on Fastboot Mode screen once I run fastboot boot twrp.img
bp328i said:
Wouldn't you want to be using a twrp.img not .zip?
fastboot boot twrp.img
Boot twrp from the img and then flash the zip once twrp boots?
Click to expand...
Click to collapse
Hi, I have just got a OnePlus 6T and I am getting this same error even though I am using the twrp.img - when I run fastboot boot 'twrp.img' it sticks on the Fastboot Mode screen.
I have the .zip on the phone's internal storage along with Magisk ready to install but I can't get there.
I did manage to get into Recovery once in the last 3 hours but under Advanced the only 2 options I have are to reboot to fastloader of reboot to recovery which just takes me round in circles!
Have tried everything I can find/think of right now and am no further down the line
Any help guidance will be greatly recieved as nothing I can find on the threads here seem to help
Thanks
s
Is the twrp.img even being flashed
SimmoMaz said:
Hi, I have just got a OnePlus 6T and I am getting this same error even though I am using the twrp.img - when I run fastboot boot 'twrp.img' it sticks on the Fastboot Mode screen.
I have the .zip on the phone's internal storage along with Magisk ready to install but I can't get there.
I did manage to get into Recovery once in the last 3 hours but under Advanced the only 2 options I have are to reboot to fastloader of reboot to recovery which just takes me round in circles!
Have tried everything I can find/think of right now and am no further down the line
Any help guidance will be greatly recieved as nothing I can find on the threads here seem to help
Thanks
s
Click to expand...
Click to collapse
When I think about it, it seems that the twrp.img I am flashing is not taking. When I go into recovery I get to choose 1 of 3 languages, I choose English and then I just get the 2 options as above - thing is, the font, layout etc. make it look like stock recovery and nothing like TWRP I have used before, no TWRP logo etc. Nothing
SimmoMaz said:
When I think about it, it seems that the twrp.img I am flashing is not taking. When I go into recovery I get to choose 1 of 3 languages, I choose English and then I just get the 2 options as above - thing is, the font, layout etc. make it look like stock recovery and nothing like TWRP I have used before, no TWRP logo etc. Nothing
Click to expand...
Click to collapse
Ok.. can you get into TWRP? Is so reflash the stock rom.. the once it has flashed do not reboot, go back to install and flash the lastest twrp .zip do not reboot, go back to install and flash/install magisk, once it installs then reboot to system... It will take a bit... Once it reboots check your Magisk manager you may need to reinstall it, reboot to TWRP and reflash it.. reboot to system band you should be good to go...
TWRP isn't there
lilbrat said:
Ok.. can you get into TWRP? Is so reflash the stock rom.. the once it has flashed do not reboot, go back to install and flash the lastest twrp .zip do not reboot, go back to install and flash/install magisk, once it installs then reboot to system... It will take a bit... Once it reboots check your Magisk manager you may need to reinstall it, reboot to TWRP and reflash it.. reboot to system band you should be good to go...
Click to expand...
Click to collapse
Thanks and apologies if a two posts appear from me, I submitted one about 20 minutes ago and it isn't showing.
The issue is more than that, even when I try to flash the TWRP image it doesn't seem to take. The phone gets stuck on the 'Fastboot Mode' OnePlus flash screen and hangs there.
I have to hold the power and vol+ keys to get the device to restart and I then receive a message saying 'bootloader unlocked, data insecure etc.' and to press the power to stop the boot process. If I leave it the phone boots into OOS10.3.3.
If I press the power button I can get to recovery mode (albeit there is a password screen there which I have never seen on other devices I've had). I put my password in and choose English. I am then given the two options; reboot to fastboot or reboot to recovery. There is no advanced option to allow me to install TWRP or Magisk zips, as a matter of fact I don't get any TWRP at all, it looks like stock recovery.
Is the phone defaulting to stock recovery and not the TWRP image? That is what, in my very non-expert opinion seems to be happening. Is that possible and if so, any ideas how to fix?
I have completely flashed the phone so it is on stock OOS (10.3.3.) so can start afresh. It is a refurbed 'like new' so could that have anything to do with it?
Thanks for reading the long post - am wondering if there are some other tools I need use to change how it boots?
S
SimmoMaz said:
Thanks and apologies if a two posts appear from me, I submitted one about 20 minutes ago and it isn't showing.
The issue is more than that, even when I try to flash the TWRP image it doesn't seem to take. The phone gets stuck on the 'Fastboot Mode' OnePlus flash screen and hangs there.
I have to hold the power and vol+ keys to get the device to restart and I then receive a message saying 'bootloader unlocked, data insecure etc.' and to press the power to stop the boot process. If I leave it the phone boots into OOS10.3.3.
If I press the power button I can get to recovery mode (albeit there is a password screen there which I have never seen on other devices I've had). I put my password in and choose English. I am then given the two options; reboot to fastboot or reboot to recovery. There is no advanced option to allow me to install TWRP or Magisk zips, as a matter of fact I don't get any TWRP at all, it looks like stock recovery.
Is the phone defaulting to stock recovery and not the TWRP image? That is what, in my very non-expert opinion seems to be happening. Is that possible and if so, any ideas how to fix?
I have completely flashed the phone so it is on stock OOS (10.3.3.) so can start afresh. It is a refurbed 'like new' so could that have anything to do with it?
Thanks for reading the long post - am wondering if there are some other tools I need use to change how it boots?
S
Click to expand...
Click to collapse
Ok.. are you using the latest TWRP? If you want in the guide section you can you the msmdow like ad tools to reset you phone to stock, and retry again..
THIS. I have the exact same issue. In short, I have the T-mobile version, and was able to unlock successfully. I am using twrp-3.2.3-0, and I have the img and zip in the same folder, same way Techibee does on Youtube. I then type "fastboot boot twrp-3.2.3-0-fajita.img", I get the "OKAY... OKAY... Booting... Finished" response in console. Then, the Fastboot screen appears and never leaves. I have done this 3 times now. I kept tweaking the process, but I'm nervous to keep debugging.
Stuck (
Hello guys,
I wanted to overclock my 6t global. so i had unlocked the bootloader then flashed the twrp. In twrp i firstly reset the os to factory setting and then i flash magisk and smurf kernel. but when i reboot after this my phone is stuck on the phone unlocked message.
ive tried flashing magisk only and then boot, it works. but when i flash smurf kernel i get stuck . why this happening plz help (