I'm desperate.
I've spent about 8 hours yesterday researching and fixing my phone which was stuck in a bootloop, I couldn't even get to TWRP.
In the end, what did it was the BLOD fix here in the forums. Flashed boot.img from stock 47Z, special TWRP from same thread and then from TWRP the EX kernel version 4.12 and then the latest OmniRom which I have used before. There it was again, working, even my 90 browser tabs were still there.
This is where I f***** up. My phone notified me at startup that I should flash vendor N2G47F (which is 7.1.2. - the latest OmniRom). Alright, phone is completely working, but still, couldn't hurt. Downloaded and flashed the wrong vendor (Factory Image 8.1.0) via TWRP because it was 3am and I didn't think anymore. And then... stuck at boot screen.
Alright, I discovered it was the wrong vendor image, so let's just flash the vendor again with the right version this time and it should work again, right?
Nope. Phone changed between bootloop-ing and just stuck on the Google loading screen with the open lock.
Okay, just start again from the beginning, you know what you did, so, easy. I thought.
This is what I did:
fastboot flash vendor vendorOPM7.1.2.-N2G47F.img
fastboot flash boot 47z…img [boot-img from BLOD-thread]
fastboot flash recovery twrp3_1_1_5X.img [also from BLOD-thread]
reboot-recovery
adb sideload 5xEX4…zip [also from BLOD-thread]
adb sideload omnirom_latest.zip [latest omnirom from official site]
reboot, should work because I fixed basically everything, right?
doesnt
remembered seeing boot.img getting flashed when sideloading omnirom (in the log that TWRP shows when sideloading)
flash boot.img again [from BLOD-thread]
still doesn't work.
cache was wiped either in twrp or fastboot after nearly every step.
I can't figure out anymore what the problem is. It worked before, and just because I flashed a false vendor it's not working at all anymore? I don't get it. Do you have any ideas for me? Many thanks in advance...
Related
I just flashed the July security update, MTC19Z, using the flash-all script that it comes with then flashed TWRP 3.0.2 before the first boot and it never went to the boot screen with the Google logo, just on the warning page about my OS not being able to get checked. I thought maybe I needed to let it boot the first time so I reflashed with flash-all, let it boot up the first time, then flashed TWRP with the same results.
Not really looking for technical support, I'm sure the update broke TWRP just making a thread for awareness/discussion.
I submitted a bug report to TWRP's GitHub. It can be found here.
I flashed all the *.img manually and then flashed the newest twrp and it booted up fine...
I just flashed bootloader, radio, boot, system, vendor with fastboot then booted right into TWRP and flashed supersu not issues.
That is so strange, I guess I'll give it another go in a bit.
from bullhead-mtc19z ,the bootloader is updating to bhz10p ,not bhz10m again .
i think it will make some problems.
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
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...
Has anyone noticed the recovery image is no longer a part of the full factory image?
I thought i had a bad/corrupt download at first, but after downloading on my other pc i got the same results, no recovery image.
Its nice that i dont have to boot and flash twrp after a factory flash, but i noticed some other weird things.
first time i flashed the January image after the process was completed it booted straight into twrp, i hit reboot to system, and when it booted all my personal data was still there. it remembered my password, wallpaper, all text and calls were still there, etc. i hadnt removed -w from the script and i couldnt figure out why it was like this.
All of this aside, anyone know why google didnt include the recovery in the latest factory image?
Recovery is included. It's just a part of the boot.img. They share the same partition.
This is also one of the reasons flashing on this device can be a pain in the a**.
If you flash TWRP then fastboot flash the stock boot image, your custom recovery will be replaced by the stock recovery.
Pain-N-Panic said:
Recovery is included. It's just a part of the boot.img. They share the same partition.
This is also one of the reasons flashing on this device can be a pain in the a**.
If you flash TWRP then fastboot flash the stock boot image, your custom recovery will be replaced by the stock recovery.
Click to expand...
Click to collapse
Thats the thing though. twrp was not replaced, and even in the terminal as it was going through the commands stated recovery and sig not found.
oddly enough i tried again late yesterday and everything was normal (fresh download)
noidea24 said:
Thats the thing though. twrp was not replaced, and even in the terminal as it was going through the commands stated recovery and sig not found.
oddly enough i tried again late yesterday and everything was normal (fresh download)
Click to expand...
Click to collapse
Pain-N-Panic is correct, recovery is included in the boot.img and your TWRP installation *should* have been replaced by stock when flashing a full factory build. Every build I've flashed has always said recovery.sig not found. That is normal as far as I'm aware. I've noticed that it all depends on how the flash-all script/an OTA flash handles seeing a TWRP installation. There have been a few circumstances where my TWRP installation stayed in tact as well.