I apologize if this is the wrong place to ask, but when I try to boot my phone (Mi 6) normally I end up seeing TWRP's OpenRecoveryScript running briefly before the phone shuts off and boots again. My phone started doing this last night without any apparent prompt while I had it charging and plugged into my computer. I think it might be because of the MIUI update I installed earlier that day. I can still boot the phone into the TWRP recovery screen with all its options, and into fastboot, but I can't boot it normally. How can I fix this without encrypting/deleting or otherwise messing up the data currently on my phone?
I was able to fix this problem by downloading the stock recovery .img file posted in this thread ( en.miui.com/thread-639221-1-1.html ) and flashing the recovery section using TWRP. I hope whatever caused my problem is fixed in future updates of TWRP.
If you want a advice, no worry about use TWRP for root or any other feature you can need, but don't flash it, only boot it. If you replace the Recovery, you will have problem with otas and other stuff. Instead:
fastboot flash recovery twrp.img
use
fastboot boot recovery twrp.img
Yes, you must use it everytime you want enter on twrp, but it by far, less problematic
Related
Hi guys i flashed the 3.5.3 CM today but i decided to go back with 3.26 again, so i followed a guide that tells me to install stock recovery over twrp before i install the rom but after i fastboot flash the recovery i cannot go into the recovery anymore.
i tried to flashed the modified twrp and then boot to recovery but still wont open it.
the phone works and can go into fastboot still but it just wont access recovery
anyway to fix it? sorry if this has been discussed before. im on a mac for more info
TIA
1+3
Is your OS booting?
yea
Got the same problem here. Can boot into system and fastboot but if boot to recovery i get the oneplus logo and the bootloaderscreen and then i get a black screen where i should get my recovery. And if wanna Force shutdown my oneplus it freezes somehow. I tried everything to fix this with no result. Stock recovery doesnt work too.
Hi I just had the same problem, I have sent it back to Oneplus for repair. According to the ticket, I had a faulty motherboard, which has been replaced. If you can, do it. I only had to wait for a week before it was sent back.
Had the same problem last night. Following method nr 2 in thos thread solved it.
http://forum.xda-developers.com/showthread.php?t=3405700
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
using fastboot to wipe the recovery partition then fastboot flashing modified twrp twice worked for me, i think the oneplus recovery image thats doing the rounds doesn't want to play nice lol
If youre phone boots in to system, download Flashify from play, flash recovery.img (you need to extract .img file). Go to recovery to check if it works. If not try other recovery.
after flashing the community build i cant boot my device in fastboot mode, it wont start the recovery or boot the system sucessfully.
danxtian said:
Hi guys i flashed the 3.5.3 CM today but i decided to go back with 3.26 again, so i followed a guide that tells me to install stock recovery over twrp before i install the rom but after i fastboot flash the recovery i cannot go into the recovery anymore.
i tried to flashed the modified twrp and then boot to recovery but still wont open it.
the phone works and can go into fastboot still but it just wont access recovery
anyway to fix it? sorry if this has been discussed before. im on a mac for more info
TIA
Click to expand...
Click to collapse
If your device is unlocked, flash the recovery.img from fastboot.
You can download TWRP for oneplus 3 from their site.
Rename the downloaded recovery to recovery.img.
And open fastboot in the path of the recovery image.
Use the command:
Code:
fastboot flash recovery recovery.img
Hopefully this helps
g3ck08 said:
If your device is unlocked, flash the recovery.img from fastboot.
You can download TWRP for oneplus 3 from their site.
Rename the downloaded recovery to recovery.img.
And open fastboot in the path of the recovery image.
Use the command:
Code:
fastboot flash recovery recovery.img
Hopefully this helps
Click to expand...
Click to collapse
managed to fix it the other day, by flashing the modded twrp.. somehow that one worked after that i flashed the 3.26 plus the 3.26 modem ones because if i didnt, my touch screen wont work...
For me, I flashed the twrp from fastboot.
But still the 1+ logo shows when I try to boot in to recovery for 5 sec and shuts down with 2 dots of lights in the navigation button area
The normal boot is working fine. Did flash the recovery using apps like TWRP Manager, Flashify etc. It will show successfulll. But when I try to boot in to recovery, same result.
Please help
Hello Everyone I am hoping there is a solution to this however I have been unable to find anything.
I flashed the latest OTA image via sideload and everything was fine until I tried to install TWRP. When trying to install the latest TWRP I could find ( 3.1.0-0RC2 ) my phone would then boot loop. I tried this process several times and each time after installing my phone would boot loop for 10 minutes until I forced it into fastboot, fast booted the TWRP image, and finally sideload the OTA once again.
I have seen a couple threads which I believe indicate that May update changed/broke something with the bootloader but I will be honest I
haven't read into it much.
This is on a Google version of the device with the bootloader unlocked. (failed to mention that).
Thanks in advance.
Bijiont said:
Hello Everyone I am hoping there is a solution to this however I have been unable to find anything.
I flashed the latest OTA image via sideload and everything was fine until I tried to install TWRP. When trying to install the latest TWRP I could find ( 3.1.0-0RC2 ) my phone would then boot loop. I tried this process several times and each time after installing my phone would boot loop for 10 minutes until I forced it into fastboot, fast booted the TWRP image, and finally sideload the OTA once again.
I have seen a couple threads which I believe indicate that May update changed/broke something with the bootloader but I will be honest I
haven't read into it much.
This is on a Google version of the device with the bootloader unlocked. (failed to mention that).
Thanks in advance.
Click to expand...
Click to collapse
Please read the other Posts about this
Flash the bootloader from april.
****************************
Download last months 7.1.2 factory image.
Extract it and find "bootloader-marlin-xxxxblahblah.img".
Rename it to "bootloader.img" for simplicity's sake, then move it to the side.
:Flash-all" the latest factory image, after its done stay in fastboot.
Run "fastboot flash bootloader_a bootloader.img" from wherever you moved the file to
Disregard if "partition_a" isnt your primary, once the command is ran it will auto flash to the primary partition.
Boot and setup, reboot back to bootloader.
Boot and install twrp, then reboot to recovery.
Delete fstab.marlin in main directory, then flash preferred supersu (i use 2.79 sr3).
Reboot to system and your done. from here reboot to recovery or bootloader to flash your preferred kernel and mods.
Was able to get this all sorted out.
If anyone else happens to see this thread with the same issues and missed the April bootloader deal you can find a good overview Here
To get the April bootloader image which is something I have never loaded myself you need to download the Factory Image from April then extract it. Inside there you will see the bootloader image.
Hope this helps anyone else who didn't read far enough into this issue.
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...
Every time a new image comes out I wipe the device and flash the new release image using the flash-all.bat. However, this time I'm running into the issue of just trying to install Magisk beta 15.2 because it won't let the device boot. I've tried two methods:
Without Installing TWRP
1.) Wipe phone (factory data reset), flash-all.bat, and set-up device to get pin and fingerprint setup
2.) Reboot to fastboot and fastboot flash boot twrp-3.2.1-0-marlin.img
3.) Boot from fastboot screen into recovery and flash Magisk beta 15.2 (1520)
4.) Reboot to system and won't pass G logo
Installing TWRP
1.) Wipe phone (factory data reset), flash-all.bat, and set-up device to get pin and fingerprint setup
2.) Reboot to fastboot and fastboot flash boot twrp-3.2.1-0-marlin.img
3.) Boot from fastboot screen into recovery and flash TWRP-installer-3.2.1-0.zip
4.) Reboot to full TWRP recovery
5.) Flash Magisk 15.2 (1520)
6.) Reboot to system and will not boot past G Logo
The only thing I am trying to accomplish is get Magisk working with the stock kernel; I don't care if TWRP is installed or not. Someone else has to have tried this or has to have seen this issue because nothing I do short of restoring stock boot will allow it to boot up. Anyone have this issue and know how to get around it using the Jan 18 software?
i think the problem is that you're flashing the twrp image with fastboot instead of booting it. in #2 for either method that you tried, you ran fastboot flash boot twrp-3.2.1-0-marlin.img. try it without the word flash. fastboot flash boot twrp-3.2.1-0-marlin.img. the twrp web page for the pixel xl recommends this as the way to initially run twrp. fastboot flash boot changes the boot image. fastboot boot doesn't. when you flash the magisk zip or twrp zip from recovery, they're expecting the stock boot image. but since you ran fastboot flash boot, the boot image was modified and no longer stock. that's about all i understand about the pixel's partitioning and the boot image. there are others who can explain it better than me.
altwu said:
i think the problem is that you're flashing the twrp image with fastboot instead of booting it. in #2 for either method that you tried, you ran fastboot flash boot twrp-3.2.1-0-marlin.img. try it without the word flash. fastboot flash boot twrp-3.2.1-0-marlin.img. the twrp web page for the pixel xl recommends this as the way to initially run twrp. fastboot flash boot changes the boot image. fastboot boot doesn't. when you flash the magisk zip or twrp zip from recovery, they're expecting the stock boot image. but since you ran fastboot flash boot, the boot image was modified and no longer stock. that's about all i understand about the pixel's partitioning and the boot image. there are others who can explain it better than me.
Click to expand...
Click to collapse
I definitely missed that and I actually know exactly what you mean by not using the "flash" term. I'm going to give this another shot, thank you for pointing out my mistake I definitely see the issue now. :good:
Edit: That was exactly it. Booting directly to twrp fixed my issue because I was modifying my boot partition every time I flashed twrp. My own worst enemy. Thanks for helping me out @altwu
no problem. glad to hear that you're up and running.
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.