Hi Team,
I am unable to boot into recovery mode. I just have installed OOS 3.5.2 rom through TWRP 3.0.2(1). I am able to boot up the device. Once I complete the setup process, I turned on Advanced options in developers and selected the boot in to recovery.
Device is restarting and then it is stuck at 1+ logo.
I have tried it through boot loader (Vol down and then power button) to start the recovery mode but is also showing 1+ logo and then device got turned off.
Any idea about the issue? Unable to restore backup.
I am completely stuck.
Plz help
Try booting into fastboot flash this version of Twrp
http://forum.xda-developers.com/showpost.php?p=68691560&postcount=56
Hopefully that will do it but you may need to boot into Twrp right away and reflash twrp-3.0.2-19-oneplus3.img from within Twrp and hopefully it will then stick.
It just worked like a charm.... :good:
3.5.2 Broke TWRP compatibility, there's a new unofficial TWRP available but I can't link to it at present. Although looking now it's in the last post.
So I recently updated my op3 to 3.5.2 Community Build of oxygen OS. It was working well with a few changes from the official builds but a little time passed and the 3.5.3 Community Build was released. Of course I wanted to update so I downloaded it and tried to update but when it booted into the recovery it froze on the logo. So I downloaded the update on the computer and flashed twrp to the recovery and booted into the recovery and it froze again. Currently i have no Recovery and no access to adb.
*When trying to flash a recovery it says it was done successfully but freezes when trying to boot into it.
Normal OS booting is unaffected.
When executing the command "fastboot boot recovery.img", to boot into the recovery without flashing it i get "(remote dtb not found)"
When trying to manually update the OS through "fastboot zip Update.zip", I get "(remote: data too large)".
I also tried to do "fastboot erase recovery" before issuing the flash command.
*In trying to fix this i flashed the boot image of 3.5.3 onto the boot partition but nothing happened and now the phone reads as 3.5.3 on 3.5.2 firmware :crying:
I tried to use SkipSoft ToolKit,custom and official twrp, and recoveries such as CWM.
This would probably be better placed into the, ONEPLUS 3 ROMS, KERNELS, RECOVERIES, & OTHER DEVELOPMENT, section but I can not post there yet. If anyone can help me or find a mod that knows about this problem it would be much appreciated.
Found a Solution
http://forum.xda-developers.com/showpost.php?p=68691560&postcount=56
Hey guys and gals,
Silly question.
For a few months now, I've had TWRP 3.1.0 RC2 installed and no matter what I do, I absolutely cannot reboot into recovery. If I choose reboot to recovery while the phone is running, it results in a ramdump and eventually boots to system. If I reboot into the bootloader and choose to boot into recovery mode from there, it just boots to system. It's incredibly annoying. Literally the only time I can get into recovery is when I connect my phone to a computer and fastboot boot into a temporary TWRP Img and install TWRP again. Once I boot into system, I can never boot into recovery again. This is extremely inconvenient on the go, like right now, because I want to flash V4A before I start playing music from my Bluetooth speaker. Guess I'll just listen to low quality music :'(
What am I doing wrong? This is stupid.
Alcolawl said:
Hey guys and gals,
Silly question.
For a few months now, I've had TWRP 3.1.0 RC2 installed and no matter what I do, I absolutely cannot reboot into recovery. If I choose reboot to recovery while the phone is running, it results in a ramdump and eventually boots to system. If I reboot into the bootloader and choose to boot into recovery mode from there, it just boots to system. It's incredibly annoying. Literally the only time I can get into recovery is when I connect my phone to a computer and fastboot boot into a temporary TWRP Img and install TWRP again. Once I boot into system, I can never boot into recovery again. This is extremely inconvenient on the go, like right now, because I want to flash V4A before I start playing music from my Bluetooth speaker. Guess I'll just listen to low quality music :'(
What am I doing wrong? This is stupid.
Click to expand...
Click to collapse
I had the same problem, then I got a twrp boot loop, ended up having to boot into slot b and reflash stock img through adb, beware...
I was JUST about to post this! Exact same problem to the tee (except using RC1)! Hopefully someone smarter can chime in lol
NYYFan325 said:
I was JUST about to post this! Exact same problem to the tee (except using RC1)! Hopefully someone smarter can chime in lol
Click to expand...
Click to collapse
I was on RC1 also
Anyone got some insight to this? Can't be that uncommon of a problem...
Try starting the process again.
Boot to bootloader
Fastboot boot 3.0.2 rc1
In twrp flash 3.1.0 r 2
Reboot recovery and check if it works
noidea24 said:
Try starting the process again.
Boot to bootloader
Fastboot boot 3.0.2 rc1
In twrp flash 3.1.0 r 2
Reboot recovery and check if it works
Click to expand...
Click to collapse
I never had TWRP stick unless I added another step to your instructions --boot completely into the rom once, go back into the bootloader, open temp TWRP and flash the TWRP zip again. If I didn't do this my recovery would always revert to stock but, strangely, even though I was running a custom rom the combination of the custom rom and stock recovery never bootlooped my phone and I was able to boot from the stock recovery to the custom rom with no problems. The only reason not being able to boot into TWRP was even an issue was that you can't flash any zips in recovery without it. Otherwise the phone ran so perfectly I didn't even realize at first that TWRP wasn't still the installed recovery.
Get the stock boot.img (this will remove root/kernel/twrp)
Boot into the bootloader
Fastboot flash boot boot.img
Fastboot --set-active=a or b (switch to the inactive slot)
Fastboot reboot bootloader
Fastboot flash boot boot.img
Fastboot --set-active=a or b (reload previous slot)
Fastboot reboot bootloader
Fastboot BOOT twrp.img
Flash TWRP in twrp..
If you can do that I would be interested in your results.
Also pointing out flashing rooms and certain zips here in the forums WILL revert you back to a stock recovery. Just my last bit of helpful information, hope someone gets it figured out, flashing is already a chore for those of us who like to experiment.
pcriz said:
Get the stock boot.img (this will remove root/kernel/twrp)
Boot into the bootloader
Fastboot flash boot boot.img
Fastboot --set-active=a or b (switch to the inactive slot)
Fastboot reboot bootloader
Fastboot flash boot boot.img
Fastboot --set-active=a or b (reload previous slot)
Fastboot reboot bootloader
Fastboot BOOT twrp.img
Flash TWRP in twrp..
If you can do that I would be interested in your results.
Click to expand...
Click to collapse
I was able to boot into recovery after doing this. Got a bootloop booting into system though, but flashing the ROM (and TWRP) fixed it.
Hello,
Try booting to TWRP 3.0.2 RC1 then flash TWRP 3.0.2 RC1 + SR1-SU v2.82SR1 + SU Pixel Fix (from Chains beta thread) one right after the other in the same TWRP session then reboot. Should fix your issue, give you recovery+root without ram dump.
Cheers
Everytime you flash a rom you need to flash twrp before rebooting or you'll lose twrp recovery.
Unfortunately I've had to get my Pixel XL replaced due to a defect and received a Verizon edition XL running 7.1.1. This is what I get for buying it from Best Buy Therefore I cannot unlock the bootloader and this problem no longer applies to me.
I'll keep this thread open for a bit in case it's useful for anyone else. I'll just sit here in all of my Stock-ness.
I couldn't get this to work. Tried flashing stock boot.img, then booting off of the TWRP images but I keep getting TWRP boot loop. Any suggestions? Tried flashing the entire stock image as well and no dice...
For some reason, my phone boots in to stock recovery. I flashed TWRP recovery and then installed lineage is. When I am trying to enter the recovery now, my phone boots into stock recovery and not TWRP. Any help will be highly appreciated.
I've gone through the posts trying to find an answer. seems like people are having similar issues, but either not exactly the same or no solution found.
I have flashed to stock 7.1.2 ( i know its old, but i want back button kill function). I can use the twrp image to fastboot into it. But when i try to flash the twrp zip (ive tried from 3.1-current), i get the encryption issue. I tried doing this with security passcode set and also with it turned off. same result.
And when twrp is encrypted, i can no longer boot into system. If i try to, it just boots back into twrp (which remains encrypted). I then have to use fastboot and twrp.img to open an unencrypted twrp. From there I can at least boot into android. But i lose root.
Could i potentially use fastboot to get into twrp, flash magisk and xposed and it would work? Yes, i wouldnt be able to boot into twrp without fastboot. But at this point im just trying to get things working any way i can.
Was going to try custom rom but when i tried to flash RR i couldnt get past the boot screen (left it going for at least 20-30 min before forcing a reboot).
Since I cant even get twrp to stick. dont want to go trying to flash roms.
cnoevl21 said:
Could i potentially use fastboot to get into twrp, flash magisk and xposed and it would work?.
Click to expand...
Click to collapse
yes, this should work. it's what i do. i fastboot boot the twrp image and then flash magisk. i don't used xposed and i don't flash the twrp zip anymore. if i need to use twrp, i'll just fastboot boot it.