Hi all,
I have been trying to flash my Nexus 5X running on Android Oreo. Every time I flash it, boot into system and then go back into recovery it overwrites itself. Anybody ever heard of this?
Thanks.
c_ob said:
Hi all,
I have been trying to flash my Nexus 5X running on Android Oreo. Every time I flash it, boot into system and then go back into recovery it overwrites itself. Anybody ever heard of this?
Thanks.
Click to expand...
Click to collapse
Yes. Instead of flashing TWRP boot into it with fastboot. Then flash supersu in TWRP. After that boot into the bootloader from TWRP and turn flash TWRP with fastboot.
Related
Hello all,
Having a weird issue. I flashed a stock-based Nougat ROM today and everything went fine, flashed new bootloader/radio first and new vendor img after ROM. Set up the ROM without issues, everything running smooth. I just went to flash a custom kernel and found out that I can't seem to get into TWRP. When I reboot to bootloader and then select "Recovery mode" it brings up the TWRP splash screen but the recovery never loads, it just hangs there for several minutes. I've tried rebooting several times.
Anyone else having this issue? Afraid I might need to reflash the recovery but I'd like to avoid that if possible.
Thanks.
The_mamba said:
Hello all,
Having a weird issue. I flashed a stock-based Nougat ROM today and everything went fine, flashed new bootloader/radio first and new vendor img after ROM. Set up the ROM without issues, everything running smooth. I just went to flash a custom kernel and found out that I can't seem to get into TWRP. When I reboot to bootloader and then select "Recovery mode" it brings up the TWRP splash screen but the recovery never loads, it just hangs there for several minutes. I've tried rebooting several times.
Anyone else having this issue? Afraid I might need to reflash the recovery but I'd like to avoid that if possible.
Thanks.
Click to expand...
Click to collapse
You need to reflash recovery because you are on 3.0.2.0 and you need at least 2.1 or 2.2. Just fastboot that img and it'll boot
Stevica Smederevac said:
You need to reflash recovery because you are on 3.0.2.0 and you need at least 2.1 or 2.2. Just fastboot that img and it'll boot
Click to expand...
Click to collapse
Okay, thanks. Any idea if I will need to revert recoveries if I go back to 6.0 or are they backwards compatible?
The_mamba said:
Okay, thanks. Any idea if I will need to revert recoveries if I go back to 6.0 or are they backwards compatible?
Click to expand...
Click to collapse
No need, newest will work with MM
Hi, yestarday I flashed CM 14 with TWRP to try it, and today I have tried to return to stock rom & recovery but I can't do it. At the beginning I have tried to flash stock recovery that I have downloaded from op.net with fastboot and I couldn't do it and after I have tried to do the same process but this time flash it with TWRP and also this time I couldn't able to fix it. In fine I have installed the stock ROM via TWRP and I managed to install it but now the problem is that I still can not install the stock recovery and accordingly I can't install op3 update.
An another problem is that I have tried to re-lock OEM from fastboot and when I try to turn on the phone, is asks me a pin to enable it and I don't know that pin because I haven't set no one
ICosmin said:
Hi, yestarday I flashed CM 14 with TWRP to try it, and today I have tried to return to stock rom & recovery but I can't do it. At the beginning I have tried to flash stock recovery that I have downloaded from op.net with fastboot and I couldn't do it and after I have tried to do the same process but this time flash it with TWRP and also this time I couldn't able to fix it. In fine I have installed the stock ROM via TWRP and I managed to install it but now the problem is that I still can not install the stock recovery and accordingly I can't install op3 update.
An another problem is that I have tried to re-lock OEM from fastboot and when I try to turn on the phone, is asks me a pin to enable it and I don't know that pin because I haven't set no one
Click to expand...
Click to collapse
Need to download custom twrp http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Then use flashify to flash recovery
cbendixe84 said:
Need to download custom twrp http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Then use flashify to flash recovery
Click to expand...
Click to collapse
i have already flashed twrp 3.0.2.2 but now I would flash stock recovery but when I try to install it and turn into it op3 show me only op logo and after a few seconds the screen become black.
your phone is bricked I'm assuming. there is a thread for that. that should work for you!
sahed01 said:
your phone is bricked I'm assuming. there is a thread for that. that should work for you!
Click to expand...
Click to collapse
No it isn't. Because I managed to put stock ROM into it via adb with push command and after I have installed it from twrp that works. My only problem is that i can't flash stock recovery.
i have the same issue. Tried many times but i'm getting a black screen after one plus logo for both stck recovery and unmodified twrp. only moidified twrp is working. please let me know if u find a way to resolve this.
thanks in advance
varmasagiraju said:
i have the same issue. Tried many times but i'm getting a black screen after one plus logo for both stck recovery and unmodified twrp. only moidified twrp is working. please let me know if u find a way to resolve this.
thanks in advance
Click to expand...
Click to collapse
I downloaded the stock rom and inside it(stock rom.zip) i put the stock recovery after I reflashed the stock rom via adb from twrp and in fine I locked bootloader.
ICosmin said:
I downloaded the stock rom and inside it(stock rom.zip) i put the stock recovery after I reflashed the stock rom via adb from twrp and in fine I locked bootloader.
Click to expand...
Click to collapse
you can reboot in to stock recovery without any issues?? I think I should give it a try. And you are saying the bootloader is locked again ?
varmasagiraju said:
you can reboot in to stock recovery without any issues?? I think I should give it a try. And you are saying the bootloader is locked again ?
Click to expand...
Click to collapse
Yes, I manage to reboot into stock recovery and i relocked bootloader(you needn't relock bootloader if you do not want)
ICosmin said:
Yes, I manage to reboot into stock recovery and i relocked bootloader(you needn't relock bootloader if you do not want)
Click to expand...
Click to collapse
Great. Can I place the file in beta8 rom .zip file and flash it using adb ??
If this procedure doesn't you can download an older version of oxygen os and update it via ota. At the first attempt when you will try it will give you an error and at the second attempt It will download all the ROM again and it will reflash by itself
varmasagiraju said:
Great. Can I place the file in beta8 rom .zip file and flash it using adb ??
Click to expand...
Click to collapse
I suggest you to try at the beginning with the beta 7 because if that procedure not work for you, you can't downgrade to beta 7.
ICosmin said:
I suggest you to try at the beginning with the beta 7 because if that procedure not work for you, you can't downgrade to beta 7.
Click to expand...
Click to collapse
Thank you.
Will let you know if it worked.
I had that problem.
Solution as follows, worked everytime for me: (I have not tried this method with the newest beta 8)
1. Flash OOS 3.2.6 firmware in twrp.
2. Reboot to fastboot and flash official oxygen os recovery downloaded from the OnePlus website. (This is still the old version for some reason, thus why it won't work)
3. Side load community build with oxygen os recovery, this will flash the new firmware back and update the recovery to be community build compatible.
4. Before rebooting erase everything (factory restore)
5. Reboot to OOS, finish setting up.
6. Turn on advance reboot in developer settings.
7. Reboot to recovery via the reboot menu. First time boot into the recovery may take sometime, but it has always worked for me.
8. After everything looks good, go ahead and OEM lock in fastboot, recovery should work as usual this time and format your phone
OP did you find a solution to this?? Im on the same boat as you
i installed the official nougat update via VPN. Then rooted my op3 with nougat using modified twrp. Today i receieved OTA of 30mb, i downloaded it and click reboot. And then the problem started. The device continues to boot in twrp and im not able to use my op3.
Please HELP.......!!!!!!!!!!!!!!!
You messed up! Everyone knows that before flashing ota you should be on OnePlus recovery now you can sideload oos or flash through twrp.
neeraj679 said:
You messed up! Everyone knows that before flashing ota you should be on OnePlus recovery now you can sideload oos or flash through twrp.
Click to expand...
Click to collapse
should I flash any other rom or the oos 4.0...???
pranav_j619 said:
should I flash any other rom or the oos 4.0...???
Click to expand...
Click to collapse
which twrp version are you using? also do you have encryption issues in twrp? you might not need to reflash the rom butmay be reset the phone and install updated twrp. there are couple of threads. i myself saw this issue on my device
I faced the same issue. Just flash the stock recovery and boot the phone. The update will fail and you'll be back on.
You can flash newest BluSpark TWRP and the the 4.0.2 Full ZIP, then it should work
This is the solution that worked for me
MM MaD said:
I faced the same issue. Just flash the stock recovery and boot the phone. The update will fail and you'll be back on.
Click to expand...
Click to collapse
I had the same issue, flash the stock recovery 2.0 on the phone (the one that takes 64Mb) and then boot the phone. As mentioned it'll fail but then you get out of the loop and can flash whichever recovery and rom you feel like. And thanks for the people that mirrored the recovery while it was not on the official page, and to the people that suggested this, it was a pain to fix the first time.
pranav_j619 said:
i installed the official nougat update via VPN. Then rooted my op3 with nougat using modified twrp. Today i receieved OTA of 30mb, i downloaded it and click reboot. And then the problem started. The device continues to boot in twrp and im not able to use my op3.
Please HELP.......!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
Had this issue before, just look on your internal memory, there is a folder called ".OTAsomething", in there the OTA zip is stored, delete it and the phone will boot to Oxygen OS again.
I can't get TWRP to install on my phone. I've tried manually fastbooting all three TWRP images that are available from the TWRP website. I tried installing TWRP using the Skipsoft Toolkit. Whatever I do I never get past the TWRP splash screen--no menus ever come up. Since no menus ever come up I can't install the TWRP zip or a custom ROM. I've been trying this for hours and it's driving me crazy. Is there a different procedure to boot into temporary TWRP if you are on the June bootloader? Is there another version of the TWRP image file that I'm missing? Am I supposed to let the TWRP sit there for a really long time? This is driving me completely batty.
Did you downgrade from O?
If that is the case you should flash the stock bootloader and boot.img into both slots on your device and try again
pcriz said:
Did you downgrade from O?
If that is the case you should flash the stock bootloader and boot.img into both slots on your device and try again
Click to expand...
Click to collapse
I did. Will give that a try. Thanks.
pcriz said:
Did you downgrade from O?
If that is the case you should flash the stock bootloader and boot.img into both slots on your device and try again
Click to expand...
Click to collapse
That did the trick! Thanks.
jhs39 said:
That did the trick! Thanks.
Click to expand...
Click to collapse
Np
It took way too long but I installed TWRP, flashed DU, installed ElementalEx, rooted with custom Magisk for Pixel and got the phone to pass Safety Net. Everything seems to be working. However, whenever I go into recovery TWRP doesn't seem to be there. I appear to get the stock recovery which I don't understand. I can still boot into temporary TWRP and flash the TWRP zip and flash other zips on my phone but I can't seem to boot directly into TWRP. Is this normal or did I do something wrong somewhere?
jhs39 said:
It took way too long but I installed TWRP, flashed DU, installed ElementalEx, rooted with custom Magisk for Pixel and got the phone to pass Safety Net. Everything seems to be working. However, whenever I go into recovery TWRP doesn't seem to be there. I appear to get the stock recovery which I don't understand. I can still boot into temporary TWRP and flash the TWRP zip and flash other zips on my phone but I can't seem to boot directly into TWRP. Is this normal or did I do something wrong somewhere?
Click to expand...
Click to collapse
If I recall correctly, after flashing any rom you have to flash twrp again before rebooting. Apparently roms flash an img to our recovery partition that looks similar to a modified CWM.
noidea24 said:
If I recall correctly, after flashing any rom you have to flash twrp again before rebooting. Apparently roms flash an img to our recovery partition that looks similar to a modified CWM.
Click to expand...
Click to collapse
I actually did that. Maybe I was supposed to boot into the rom once, then back into recovery to flash TWRP. There are a lot of different flashing instructions for this phone. It's hard to keep it all straight.
jhs39 said:
I actually did that. Maybe I was supposed to boot into the rom once, then back into recovery to flash TWRP. There are a lot of different flashing instructions for this phone. It's hard to keep it all straight.
Click to expand...
Click to collapse
Booting into the rom, going back into temp TWRP and flashing the TWRP zip seems to have worked --TWRP actually stuck this time and I can boot directly into it now. It's a shame Google made the Pixel XL such a headache to flash on.
Hi everyone,
I found similar threads here on the forums, but none of them solved my problem!
My Zenfone 2 (Z00A/ZEE551ML) keeps bootlooping into TWRP, the cause of this issue is when i try to flash the SuperSU v2.8 zip!
My TWRP is 3.1.1, when i flash either Lineage 14 or AOSP/XOSP it boots normally into the OS, but the moment when I install SuperSU the bootloop happens (and yes, I've tried to flash it before and after the first boot of the OS, and it didn't work for either one of these methods)! The problem is that I want to use AOSP and I need Root access, and it doesn't come Rooted out of the box, unlike Lineage. Does anyone have any ideas how to solve this?
Thanks in advance!
dantekb43 said:
Hi everyone,
I found similar threads here on the forums, but none of them solved my problem!
My Zenfone 2 (Z00A/ZEE551ML) keeps bootlooping into TWRP, the cause of this issue is when i try to flash the SuperSU v2.8 zip!
My TWRP is 3.1.1, when i flash either Lineage 14 or AOSP/XOSP it boots normally into the OS, but the moment when I install SuperSU the bootloop happens (and yes, I've tried to flash it before and after the first boot of the OS, and it didn't work for either one of these methods)! The problem is that I want to use AOSP and I need Root access, and it doesn't come Rooted out of the box, unlike Lineage. Does anyone have any ideas how to solve this?
Thanks in advance!
Click to expand...
Click to collapse
try TWRP 3.0.2.. after that boot normally. then factory reset. boot again. go back to recovery flash su clear cache and dalvik cache.. boot. phone mat bootloop at logo few times don't interrupt it let it boot itself.
sukhwant717 said:
try TWRP 3.0.2.. after that boot normally. then factory reset. boot again. go back to recovery flash su clear cache and dalvik cache.. boot. phone mat bootloop at logo few times don't interrupt it let it boot itself.
Click to expand...
Click to collapse
Apparently.... my phone refuses to install TWRP 3.0.2......
I'm doing all the steps that I'm used to.... Enable Debugging on dev. options.... adb reboot fastboot.... fastboot flash recovery "TWRP 3.0.2" and it's sucessful....
However... when i try to boot into recovery, the phone goes back to fastboot (although, i can boot it to system normally).
I tried flashing 3.1.1 back again and it worked, it went back to 3.1.1 .... so I'm back at square one.
dantekb43 said:
Apparently.... my phone refuses to install TWRP 3.0.2......
I'm doing all the steps that I'm used to.... Enable Debugging on dev. options.... adb reboot fastboot.... fastboot flash recovery "TWRP 3.0.2" and it's sucessful....
However... when i try to boot into recovery, the phone goes back to fastboot (although, i can boot it to system normally).
I tried flashing 3.1.1 back again and it worked, it went back to 3.1.1 .... so I'm back at square one.
Click to expand...
Click to collapse
which version of super su you are flashing?
dantekb43 said:
Hi everyone,
I found similar threads here on the forums, but none of them solved my problem!
My Zenfone 2 (Z00A/ZEE551ML) keeps bootlooping into TWRP, the cause of this issue is when i try to flash the SuperSU v2.8 zip!
My TWRP is 3.1.1, when i flash either Lineage 14 or AOSP/XOSP it boots normally into the OS, but the moment when I install SuperSU the bootloop happens (and yes, I've tried to flash it before and after the first boot of the OS, and it didn't work for either one of these methods)! The problem is that I want to use AOSP and I need Root access, and it doesn't come Rooted out of the box, unlike Lineage. Does anyone have any ideas how to solve this?
Thanks in advance!
Click to expand...
Click to collapse
Check the following topic and download VerifiedBootSigner-v8.zip
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Flash SuperSU and don't reboot yet.
Flash VerifiedBootSigner-v8.zip and then reboot.
Let me now if it worked. I had the same problem after installing Magisk. Resigning the bootimage fixed the problem for me.
Vorstedt said:
Check the following topic and download VerifiedBootSigner-v8.zip
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Flash SuperSU and don't reboot yet.
Flash VerifiedBootSigner-v8.zip and then reboot.
Let me now if it worked. I had the same problem after installing Magisk. Resigning the bootimage fixed the problem for me.
Click to expand...
Click to collapse
I've had the same problem and your solution fixed it!
Thank you very much, sir! :good: