Database Info

Opo in bootloop with almost any stock rom

Hi, the problem is the one from the title, i want to start from the beginning: a couple of days ago, i was on facebook (on COS13, no twrp upgraded from COS12.1 with the incremental fom the stock recovery) then facebook crashed and then my phone rebooted and entered in a bootloop(and coldn't boot into stock recovery to wipe cache) I tried going back to stock with this guide: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
but still bootloop with no possibility to access stock recovery and twrp , then i tried to flash cm 11s with oneplus one toolkit but still bootloop(but i was able to boot in twrp), i also tried bacon root toolkit to flash cm 12.1 but guess what, still bootloop with no acces to any recovery, then i tried coloros, i flashed it with oneplus one toolbox: http://inthiaano.com/oneplus-one-color-os-installer/
but i get an "invalid nv partition" then it shuts off. Currently i'm on cm11s XNPH44S in bootloop (EDIT: I can access also stock recovery now)
What should i do? Thanks

[Solved][C2105]Can't install custom recovery with anything contanining FOTAKernel way

Only thing is works for me is https://forum.xda-developers.com/xperia-l/orig-development/cwm-recovery-installer-t2589320
su into dd via adb, twrp app, recovery installer by corphish (https://forum.xda-developers.com/xp...-installer-t3187915/post62536810#post62536810)
Every "fotakernel"-style ways saying that it is finishes its jobs successfully, yet when I "adb reboot recovery" it always loads stock recovery.
Bootloader is unlocked, I've checked it via *#*#737...
I've spent over 8 hours trying everything I've found to flash img, but it just doesn't becomes custom recovery, it is always reverts to default.
What I'm doing wrong or what is wrong with my phone?

qqzzxxcc said:
Only thing is works for me is https://forum.xda-developers.com/xperia-l/orig-development/cwm-recovery-installer-t2589320
su into dd via adb, twrp app, recovery installer by corphish (https://forum.xda-developers.com/xp...-installer-t3187915/post62536810#post62536810)
Every "fotakernel"-style ways saying that it is finishes its jobs successfully, yet when I "adb reboot recovery" it always loads stock recovery.
Bootloader is unlocked, I've checked it via *#*#737...
I've spent over 8 hours trying everything I've found to flash img, but it just doesn't becomes custom recovery, it is always reverts to default.
What I'm doing wrong or what is wrong with my phone?
Click to expand...
Click to collapse
IIt's not your fault, it's because stock ROM only supports and allows this recovery!
So if you don't have any problem, use only that one!
But if you want to install custom ROMs using latest TWRP, then you have two choices:
1- Install some Lollipop ROM from current recovery and then use its own recovery to update your recovery to latest one, and continue your works!
2- Use adb & fastboot to flash latest TWRP to BOOT partition (not fota or recovery partition!!!) by booting into fastboot mode and using this command:
Code:
fastboot flash boot [I]yourimagename[/I].img
So it directly boots into recovery( instead of ROM!) But be careful!!! You must install your new ROM right after recovery is opened to avoid any potential problems with missing boot!
I recommend using first method for your convenience and safety

Kungfu73 said:
IIt's not your fault, it's because stock ROM only supports and allows this recovery!
So if you don't have any problem, use only that one!
But if you want to install custom ROMs using latest TWRP, then you have two choices:
1- Install some Lollipop ROM from current recovery and then use its own recovery to update your recovery to latest one, and continue your works!
2- Use adb & fastboot to flash latest TWRP to BOOT partition (not fota or recovery partition!!!) by booting into fastboot mode and using this command:
Code:
fastboot flash boot [I]yourimagename[/I].img
So it directly boots into recovery( instead of ROM!) But be careful!!! You must install your new ROM right after recovery is opened to avoid any potential problems with missing boot!
I recommend using first method for your convenience and safety
Click to expand...
Click to collapse
Thanks, that helped me so much!

Okay, just reporting how stuff worked for me
Flashed boot.img from cwm11 - flashed cm11 = 4.4.4
TWRP to FOTAKernel didn't worked - still old CWM
Installed CM12 from that CWM - 5.0 as you mentioned.
Tried TWRP to FOTAKernel using su+dd. Still old recovery (don't remember which one, probably same CWM).
Decided to go all-in, flashed TWRP img to boot using fastboot - Finally got TWRP, but obviously couldn't run anything else. Also had flickering\shaky screen left and right but it's functions seemed to working alright.
Flashed [7.1.1]LineageOS 14.1 || Beta 4 by corphish (I've tried to flash it before from that old TWRP (2.7.10) it would run once (all functions were working fine), after you reboot device it gets stuck in bootloop.) result = everything works, no bootloop after restart, and TWRP 3.0.2.0 either fixed it self or maybe it comes with ROM so that helped, dunno.
Thanks for mentioning "fastboot flash boot yourimagename.img" and that I can flash recovery into boot.

qqzzxxcc said:
Okay, just reporting how stuff worked for me
Flashed boot.img from cwm11 - flashed cm11 = 4.4.4
TWRP to FOTAKernel didn't worked - still old CWM
Installed CM12 from that CWM - 5.0 as you mentioned.
Tried TWRP to FOTAKernel using su+dd. Still old recovery (don't remember which one, probably same CWM).
Decided to go all-in, flashed TWRP img to boot using fastboot - Finally got TWRP, but obviously couldn't run anything else. Also had flickering\shaky screen left and right but it's functions seemed to working alright.
Flashed [7.1.1]LineageOS 14.1 || Beta 4 by corphish (I've tried to flash it before from that old TWRP (2.7.10) it would run once (all functions were working fine), after you reboot device it gets stuck in bootloop.) result = everything works, no bootloop after restart, and TWRP 3.0.2.0 either fixed it self or maybe it comes with ROM so that helped, dunno.
Thanks for mentioning "fastboot flash boot yourimagename.img" and that I can flash recovery into boot.
Click to expand...
Click to collapse
Glad that it worked for you and you finally could get latest one!
I forgot to mention that in first method, after installing LP ROM, install recovery installer app and flash TWRP v2.8.7.2 and use that to install latest one !!! and LoL very long way
I just wanted to say that it is possible!

flash back to the factory/Stock rom..unable to flash TWRP or boot into TWRP anymore :

flash back to the factory/Stock rom..unable to flash TWRP or boot into TWRP anymore :
- I ran the flash-all.bat and basically wipe the entire phone..
- after that, I used Nexus Root Toolkit v2.1.9 and tried to root + flash custom recovery..
the first time it didn't go thru.
the second time, it was able to boot into TWRP,, then after rebooting the phone, (the toolkit automated steps..)
i couldn't find the SuperSU under Settings :/
also, TWRP recovery mode doesn't work too.
when I boot into the recovery mode, it basically just a broken green android laying there :/
(My main goal is to uninstall the bloatware it came with the Stock rom..)
any ideas on how can I get this fixed ?
here is the link to the stock rom:
https://developers.google.com/android/images
I was able to follow the instruction and used flash-all.bat to flash my Nexus 5 back to the latested Stock Image.. 6.0.1 (M4B30Z, Dec 2016)

hi..
same like me..but you can try to click on top options>custom recovery>tick utilize an alternate custom recovery image and browser your recovery.img...and my nexus 5 was successful install twrp and root via nexus root tool v2.19..

The broken green Android on his back means that stock recovery could be on the phone.
Did yo try manually flashing TWRP using fast boot commands ?

Error 18 when trying to flash custom roms with Twrp

Hey all,
I unlocked the bootloader, flashed the latest bootloader, radio and vendor from april factory image, to both the slots with fastboot, booted into the twrp 3.2.3-0 (also tried booting into 3.3.0 version) and tried to flash the latest official DU 13.1 rom but I get the Error 18 kDownloadPayloadPubkeyVerificationError at the STEP 2 every damned time! I did a factory reset before flashing, and tried to start all over again many times, flashing factory image with the flash all script, rebooting and then flashing the A/B slots again, but I get that error when I try to flash the rom zip every time. I really don't know how to solve, can someone help me please?
EDIT: thanks to this thread https://forum.xda-developers.com/pixel-3/development/twrp-3-2-3-0-pixel-3-t3861622/post79346061#post79346061 I solved by doing this:
- fastboot boot twrp-3.3.0.0.img
- advanced->Install Recovery Ramdisk and choose the 3.3.0.0 image
- reboot to recovery
- factory reset
- flash the zip
- done

[Q] SM-G928F / zenlte logo bootloop after twrp flash

I was trying to get lineageos on my s6 edge+ but it is stuck in a samsung logo loop after being unable to flash the rom and now it won't go back into TWRP either.
Initially I flashed the official TWRP for the zenlte which worked fine, it just did not want to install the rom due to apparently not having any device data. (Rom is for zenlte, this device is . (or something along those lines))
after a few attempts and doing a quick wipe I flashed an unofficial twrp and thats when it started looping without being able to get back into recovery mode.
Download mode does still work after a power off but flashing the official twrp again makes no difference.
This is a little beyond me and I'm not entirely sure what is going on.
The last phone I installed a custom rom on was an s4 so I'm a bit out of the loop with this new security stuff. I would have expected to at least be able to boot back into twrp.

Ok some progress:
Recovery mode worked again after leaving phone off (but still attached to computer) for a while. (I had given up but decided to try again after a few hours)
Partitions were missing / corrupted. Did a full format.
Installing rom still gave the 'device type is .' message.
Edited the rom zip to allow "" and " " ( in META-INF\com\google\android\updater-script )
Flashed rom + gapps + magisk in 1 go.
This ended up in LineageOS trying to start but rebooting into recovery after about 5 minutes.
Re-instralled just the rom, this gave a few errors about Magisk missing, re-installed Magisk as well before wiping cache and rebooting.
Now it came up with the welcome screen rather quickly.
Weird, but problem solved any ways.

Thanks! That was also my problem.