Develop Bugs

How to update to 4.4 with TWRP?

I rooted my tablet and installed TWRP end of august.
Two days ago I installed 4.4 with an OTA update which broke the phone, it always booted into recovery. I learned that TWRP was incompatible with 4.4 older versions of TWRP might cause problems with 4.4 and flashed the 4.3 factory image using adb. The tablet is now working again.
I'm just not sure how to proceed now. It seems the TWRP recovery is gone, because from Fastboot when I select recovery I get the dead android with the red triangle. Can I just update by following this post?

bur2000 said:
I rooted my tablet and installed TWRP end of august.
Two days ago I installed 4.4 with an OTA update which broke the phone, it always booted into recovery. I learned that TWRP was incompatible with 4.4 and flashed the 4.3 factory image using adb. The tablet is now working again.
I'm just not sure how to proceed now. It seems the TWRP recovery is gone, because from Fastboot when I select recovery I get the dead android with the red triangle. Can I just update by following this post?
Click to expand...
Click to collapse
Where have you read twrp is not compatible with 4.4? Many people are using twrp with 4.4. You should use the latest version which supports SELinux security contexts.
It is probably easiest if you just flash the KRT16S factory image from that thread.

sfhub said:
Where have you read twrp is not compatible with 4.4? Many people are using twrp with 4.4. You should use the latest version which supports SELinux security contexts.
Click to expand...
Click to collapse
It doesn't seem to happen for everybody, maybe it's older versions of TWRP. Mine was from August. I rephrased my original post to make that clear. There are some threads here about the problem and if you google for it you'll find some more warnings. It's always the same thing, the tablet will only boot into recovery after an OTA with TWRP:
http://forum.xda-developers.com/showthread.php?p=47709956
http://forum.xda-developers.com/showthread.php?p=47713265
http://forum.xda-developers.com/showthread.php?t=2537669
http://www.droid-life.com/2013/11/1...krt16o-official-update-for-nexus-7-2012-wifi/ (in the comments)
http://forum.xda-developers.com/showthread.php?t=2510810
Thanks for your reply though, so I'll try flashing the factory image. Should I use adb for that or newest TWRP? Also the red triangle means my custom recovery is gone, correct?

bur2000 said:
It doesn't seem to happen for everybody, maybe it's older versions of TWRP. Mine was from August. I rephrased my original post to make that clear. There are some threads here about the problem and if you google for it you'll find some more warnings. It's always the same thing, the tablet will only boot into recovery after an OTA with TWRP:
http://forum.xda-developers.com/showthread.php?p=47709956
http://forum.xda-developers.com/showthread.php?p=47713265
http://forum.xda-developers.com/showthread.php?t=2537669
http://www.droid-life.com/2013/11/1...krt16o-official-update-for-nexus-7-2012-wifi/ (in the comments)
http://forum.xda-developers.com/showthread.php?t=2510810
Thanks for your reply though, so I'll try flashing the factory image. Should I use adb for that or newest TWRP? Also the red triangle means my custom recovery is gone, correct?
Click to expand...
Click to collapse
Personally I think it is easiest to flash the factory image but you probably need around the same number of steps either way.
The factory image is meant to flash in boot loader using fastboot, not using adb.
The fallen android means you are using stock recovery. It is an image that hides the recovery menu. press/hold power, press/release VolUp, release Power to see the actual recovery menu and any errors which might have occured

sfhub said:
Personally I think it is easiest to flash the factory image but you probably need around the same number of steps either way.
Click to expand...
Click to collapse
Thanks again, all worked well going along with your guide. Only thing to do now is getting TWRP and SU flashed.
It seems like I'm not really up-to-date anymore when it comes to flashing, I only knew of using recovery and never heard of sideload or using fastboot to flash any images.

Started from V50020D and now we are here - DIM issue.

So from stock V50020D, I have installed kkroot, and then able to install custom recovery of TWRP. First version I tried was 2.7.1.0 and then went to version 2.8.0.0.
Same happens at either TWRP version. I am able to get into recovery, WIPE, add a ROM of my choice, but as soon as it starts booting up the =with whoever's ROM boot animation, the screen is dim all the way up to the Android setup screen. It remains dim but I can at least lock the tablet and then unlock it and the brightness is normal until my next reboot.
I thought this version of TWRP 2.8.0.0 fixes this issue? If so, I can't get it to work.
I've read you can also try to flash back to version V50020A with the 4.2.2 kernel and work your way up back to 4.4.2 by updating to higher versions of TWRP, but that's not really a fix, that's more of a workaround and I can't get it to work.
I've tried flashing to LG-V500_JDQ39B.V50010A_US_Stock-BB-Rooted .zip but I start getting a boot loop (as in nothing happens when booting but if you try to get into TWRP, it's stuck running a script of some sort and kicks me out back to the beginning of the LG boot sequence, thus my loop). I then have to do a LG Factory restore and start the process over.
Has anyone successfully fix the dimming issue without updating/upgrading from kernel 4.2.2 and old stock ROM.
Thanks in advance.

If you are talking about the recovery being dim make sure to flash the version built specifically for the 4.4.2 base.
If you are running a ROM that is dim either switch to the 4.2.2 base or use a different kernel. I use a 4.4.2 base with RedKernel and SlimKat rom as an example...

Hello, I have tablet version V50020D and it is rooted. I haven't figured out how to get TWRP on it because the bootloader is locked. Can I ask how you got TWRP to work on this software version? Thanks.

shampiaj said:
Hello, I have tablet version V50020D and it is rooted. I haven't figured out how to get TWRP on it because the bootloader is locked. Can I ask how you got TWRP to work on this software version? Thanks.
Click to expand...
Click to collapse
I used a process a lot like this:
http://forum.xda-developers.com/lg-...e-root-twrp-customrom-kot49i-v50020d-t2894277
Basically the tablet is 4.4.2 except for the aboot partition, which has the older piece from 4.2.2...

muiriddin said:
I used a process a lot like this:
http://forum.xda-developers.com/lg-...e-root-twrp-customrom-kot49i-v50020d-t2894277
Basically the tablet is 4.4.2 except for the aboot partition, which has the older piece from 4.2.2...
Click to expand...
Click to collapse
Awesome. Thanks!

Hey, I was just about to start an a question tonight but saw yours and I was like 'how?!'.
I have a LG G Pad V50020d. Rooting is not an issue but the ability to flash TWRP is just not working for me. I have tried every guide possible, even the one you have suggested. I amended the runme file and things seem to go well but when I boot into recovery I get the fallen android and this message at the bottom of the screen;
"E:missing bitmap stage_empty
(Code -1)
E:missing bitmap stage_fill
(Code -1)"
Don't suppose you can help me?
Sent from my LG-D802 using XDA Free mobile app

Need help in going back to Stock OOS ROm 3.2.6 after unrooting the OP3

I have followed the below link from Oneplus community pages to unroot the mobile completely and install stock OOS
https://forums.oneplus.net/threads/...lus-3-and-go-back-completely-to-stock.456232/
but now when I tried to follow the same steps to back to Stock OOS from CM 14.1 with TWRP 3.2.2 after running OEM LOCK command the mobile reboots and stalls at Oneplus logo screen with both the hardware buttons lights on and nothing happens I have tried several times to go to recovery mode manually but the same thng happens...after trying a lot I was forced to again unlock the bootloader and go back to CM 14.1 rom (it went back just after installing the twrp recovery ..which means that Stock recovery was not installed properly I guess)
Kindly help me with a solution to this problem as I want to go back to stock ROM again as Nougat Beta Might be released by this november end....
If u any other way of going back to stock OS fully kindly tell that also..

rahulopg42 said:
I have followed the below link from Oneplus community pages to unroot the mobile completely and install stock OOS
https://forums.oneplus.net/threads/...lus-3-and-go-back-completely-to-stock.456232/
but now when I tried to follow the same steps to back to Stock OOS from CM 14.1 with TWRP 3.2.2 after running OEM LOCK command the mobile reboots and stalls at Oneplus logo screen with both the hardware buttons lights on and nothing happens I have tried several times to go to recovery mode manually but the same thng happens...after trying a lot I was forced to again unlock the bootloader and go back to CM 14.1 rom (it went back just after installing the twrp recovery ..which means that Stock recovery was not installed properly I guess)
Kindly help me with a solution to this problem as I want to go back to stock ROM again as Nougat Beta Might be released by this november end....
If u any other way of going back to stock OS fully kindly tell that also..
Click to expand...
Click to collapse
Did you try maybe return to 3.5.5 using the custom TWRP and then follow that guide?

Crash said:
Did you try maybe return to 3.5.5 using the custom TWRP and then follow that guide?
Click to expand...
Click to collapse
ya I just did that only...just that I didnt flash 3.5.5 rather restored it....so now I am on 3.5.5 rooted .....so you are saying to try the tutorial now..okh I will..
but wht to do if I face the same thng again..kiindly say tht as well

rahulopg42 said:
ya I just did that only...just that I didnt flash 3.5.5 rather restored it....so now I am on 3.5.5 rooted .....so you are saying to try the tutorial now..okh I will..
but wht to do if I face the same thng again..kiindly say tht as well
Click to expand...
Click to collapse
Well mate is a matter of test I really don´t have more answers maybe to wait other users to comment :good:,

thnxx man

Ah just seen you restored 3.5.5
Flash the stock 3.5.5 and then you should be good and I know why it's not booting when you restore from a backup you HAVE to also restore the system partition as well which is generally 3008mb in size or it simply will not boot.
I have no idea why this is the case but it's easily fixed by flashing stock 3.5.5 over the top.

daleski75 said:
Ah just seen you restored 3.5.5
Flash the stock 3.5.5 and then you should be good and I know why it's not booting when you restore from a backup you HAVE to also restore the system partition as well which is generally 3008mb in size or it simply will not boot.
I have no idea why this is the case but it's easily fixed by flashing stock 3.5.5 over the top.
Click to expand...
Click to collapse
i just tried to install stock 3.5.5 over freedom os and it said
error 7
Error installing zip file
this package is for "oneplus 3" yours is a " "
i was trying the unlocker guide https://www.youtube.com/watch?v=h5a9XOQceC8
so if you guys have any ideas
btw @daleski75 i get random reboots in the same locations with any 7.1/7.0 roms... thats basicaly why i want to go back to stock

gigeaky said:
i just tried to install stock 3.5.5 over freedom os and it said
error 7
Error installing zip file
this package is for "oneplus 3" yours is a " "
i was trying the unlocker guide
so if you guys have any ideas
btw @daleski75 i get random reboots in the same locations with any 7.1/7.0 roms... thats basicaly why i want to go back to stock
Click to expand...
Click to collapse
Side load it.

OnePlus 3 recovery issue

So I don't know what I did...
If I'm trying to flash either twrp or stock recovery and boot them, it shows the "powered by android" and the screen goes black.
Well except twrp-3.1.1-2oneplus3.img....
I tried to flash stock recovery to install updates didn't work... Tried to flash the update with twrp, didn't work now I'm trying to downgrade twrp but my screen just goes black :c
Well my phone runs android 8.0 and it works but i still want the new fixes ^^
ohh and maybe i'm just stupid u had to forgive me that ': D

Aduentix said:
So I don't know what I did...
If I'm trying to flash either twrp or stock recovery and boot them, it shows the "powered by android" and the screen goes black.
Well except twrp-3.1.1-2oneplus3.img....
I tried to flash stock recovery to install updates didn't work... Tried to flash the update with twrp, didn't work now I'm trying to downgrade twrp but my screen just goes black :c
Well my phone runs android 8.0 and it works but i still want the new fixes ^^
ohh and maybe i'm just stupid u had to forgive me that ': D
Click to expand...
Click to collapse
Unless is missed something, I am pretty sure that there is no TWRP fully working with Oreo yet. If you want to go back to stock recovery then you should just flash the full OxygenOS zip.

Puddi_Puddin said:
Unless is missed something, I am pretty sure that there is no TWRP fully working with Oreo yet. If you want to go back to stock recovery then you should just flash the full OxygenOS zip.
Click to expand...
Click to collapse
Yes exactly what I did after getting bored with flashing different recoverys over and over...
I should have known cause I bricked my device a few times too, by flashing old supersu.zips ^^
Anyway thank you for the answer

Can't boot into recovery, ANY recovery rom!

So I've long been had PE (Pixel Experience) installed on my phone and I've never had any issues flashing recovery, not even in the CFW days. But I noticed there was an update to PE last month and decided I should update it. The instructions are clean, you must start fresh (format data, system, dalvik, etc..) so prior to attempting to install PE, first order of business is to get a newer recovery. Simple right? I tried flashing the twrp that was listed in the instrucitons, I tried Orange Fox, which worked only once but hasn't since. So if figured, ok, too many issues, let me start from scratch. I fastboot flashed my phone using the last Miui firmware I had on my phone. Didn't wan't the newer firmware getting in the way with whatever new locks they may have installed. Flashing to factory using fastboot went without a hitch. I first opted to save my data, but that failed at boot, so I did a flash-all.bat and that got me to a pristine factory from Miui 11 Android 9. Enabled USB Debug and Relaxed USB App upload secruity settings and now I should be able to boot into the bootloader and Flash any recovery right? No such luck. Flashed the latest and even a version prior of TWRP and Orange fox and they just don't boot. When I hold the Vol Up + Power it boots showing the Redmi logo and just when it's suppoed to show the splash screen of whatever recovery I'm trying, it simply reboots and I'm sure the miui os already restored the original factory so I try flashing again and no dice. I've flashed and tried to boot probably 50 times by now. Only once did I get a little ray of hope when I flashed Orange fox after doing a clean fastboot rom flash and I simply got 3 menu choices asking to boot to recovery, bootloader ,or system. I of course chose recovery and FAIL it just went black screen and rebooted to system! OK, so frustrated, I went and downloaded the latest firmware from Mi and for sure, whever it has that's preventing booting into recovery for sure will get erased and started from scratch, especially cuz I'm going from Miui11 Android 9 all the way up to Miui 12.5 Android 11 right? After re-enableing the developer setting and adjusting the settings and making sure my computer is authorized on the phone I rebooted to the bootloader, flashed Orange Fox and FAIL! still no joy. WTF?!? This is getting frustrating. What am I doing wrong? What can I do to try and fix this?

Tin_Man_0 said:
So I've long been had PE (Pixel Experience) installed on my phone and I've never had any issues flashing recovery, not even in the CFW days. But I noticed there was an update to PE last month and decided I should update it. The instructions are clean, you must start fresh (format data, system, dalvik, etc..) so prior to attempting to install PE, first order of business is to get a newer recovery. Simple right? I tried flashing the twrp that was listed in the instrucitons, I tried Orange Fox, which worked only once but hasn't since. So if figured, ok, too many issues, let me start from scratch. I fastboot flashed my phone using the last Miui firmware I had on my phone. Didn't wan't the newer firmware getting in the way with whatever new locks they may have installed. Flashing to factory using fastboot went without a hitch. I first opted to save my data, but that failed at boot, so I did a flash-all.bat and that got me to a pristine factory from Miui 11 Android 9. Enabled USB Debug and Relaxed USB App upload secruity settings and now I should be able to boot into the bootloader and Flash any recovery right? No such luck. Flashed the latest and even a version prior of TWRP and Orange fox and they just don't boot. When I hold the Vol Up + Power it boots showing the Redmi logo and just when it's suppoed to show the splash screen of whatever recovery I'm trying, it simply reboots and I'm sure the miui os already restored the original factory so I try flashing again and no dice. I've flashed and tried to boot probably 50 times by now. Only once did I get a little ray of hope when I flashed Orange fox after doing a clean fastboot rom flash and I simply got 3 menu choices asking to boot to recovery, bootloader ,or system. I of course chose recovery and FAIL it just went black screen and rebooted to system! OK, so frustrated, I went and downloaded the latest firmware from Mi and for sure, whever it has that's preventing booting into recovery for sure will get erased and started from scratch, especially cuz I'm going from Miui11 Android 9 all the way up to Miui 12.5 Android 11 right? After re-enableing the developer setting and adjusting the settings and making sure my computer is authorized on the phone I rebooted to the bootloader, flashed Orange Fox and FAIL! still no joy. WTF?!? This is getting frustrating. What am I doing wrong? What can I do to try and fix this?
Click to expand...
Click to collapse
OK, your one sentence text is a bit difficult to read but I'll try to explain the best I can (there might be errors).
You can split the custom recoveries into two types. CFW and non-CFW.
You can split the custom ROMs into two types. CFW and non-CFW.
CFW recoveries have to go hand in hand with CFW custom ROMs.
non-CFW recoveries have to go hand in hand with non-CFW custom ROMs.
What about stock MIUI? That depends on the custom recovery. The developer usually states which ROMs the recovery is designed for (if CFW or non-CFW; if stock MIUI 12.0.x or stock MIUI 12.5.x; etc). If you mix a CFW recovery with a non-CFW custom ROM you'll probably have issues.
If you install a compatible recovery for MIUI 12.5.x and simply let MIUI boot into system it erases the custom recovery, which means you have to install the custom recovery again and boot straight into it. That's why some recoveries have extras to prevent its erasure (you'll have to research this).
This video below should contain everything you need.
Compass.

Compass Linux said:
OK, your one sentence text is a bit difficult to read but I'll try to explain the best I can (there might be errors).
You can split the custom recoveries into two types. CFW and non-CFW.
You can split the custom ROMs into two types. CFW and non-CFW.
CFW recoveries have to go hand in hand with CFW custom ROMs.
non-CFW recoveries have to go hand in hand with non-CFW custom ROMs.
What about stock MIUI? That depends on the custom recovery. The developer usually states which ROMs the recovery is designed for (if CFW or non-CFW; if stock MIUI 12.0.x or stock MIUI 12.5.x; etc). If you mix a CFW recovery with a non-CFW custom ROM you'll probably have issues.
If you install a compatible recovery for MIUI 12.5.x and simply let MIUI boot into system it erases the custom recovery, which means you have to install the custom recovery again and boot straight into it. That's why some recoveries have extras to prevent its erasure (you'll have to research this).
This video below should contain everything you need.
Compass.
Click to expand...
Click to collapse
Way ahead of you my friend. I got off of CFW roms several versions ago. BUT I think I found what the problem may have been. The official TWRP gives instructions to disable AVB via fastboot flashing vbmeta with the following command. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img. I'm guessing the custom TWRP or Orange fox are supposed to have that command built into it or something cuz they didn't mention it in their instructions to flash the roms. Unfortuately I upgraded to MIUI 12.5 Android 11 and Xaiomi appears to have added some new locks because I'm reading reports from other users that attempting to flash custom recovery roms on MIUI 12.5 is resulting in bootloops. Sigh, just my luck. Stuck until further notice. BTW, once upgraded to 12.5 there's no flashing previous versions either. Exactly what I was originally trying to avoid, but I needed a working phone, so I'm on stock again for the time being.

Tin_Man_0 said:
Way ahead of you my friend. I got off of CFW roms several versions ago. BUT I think I found what the problem may have been. The official TWRP gives instructions to disable AVB via fastboot flashing vbmeta with the following command. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img. I'm guessing the custom TWRP or Orange fox are supposed to have that command built into it or something cuz they didn't mention it in their instructions to flash the roms. Unfortuately I upgraded to MIUI 12.5 Android 11 and Xaiomi appears to have added some new locks because I'm reading reports from other users that attempting to flash custom recovery roms on MIUI 12.5 is resulting in bootloops. Sigh, just my luck. Stuck until further notice. BTW, once upgraded to 12.5 there's no flashing previous versions either. Exactly what I was originally trying to avoid, but I needed a working phone, so I'm on stock again for the time being.
Click to expand...
Click to collapse
You might like this MIUI 12.5.x mod:
Updated version of the mod (11/08/2021): MOD EDIT: Link Removed
Downgrade MIUI 12.5.x to MIUI 12.0.x via TWRP:
Good luck!
Compass.

Compass Linux said:
You might like this MIUI 12.5.x mod:
Updated version of the mod (11/08/2021): MOD EDIT: Link Removed
Downgrade MIUI 12.5.x to MIUI 12.0.x via TWRP:
Good luck!
Compass.
Click to expand...
Click to collapse
Thanks! I'll give these a try, but what I was looking for and don't see where exactly to download is that batch file and version of twrp that was show on the video. They launched a batch file and adb waited for the phone and then off it went. I assume that these some extra little steps added to the batch file besides the "fastboot flash recovery recovery.img" routine? Also, the moded ROM looks intresting from the pling page. Can if just copy the "flash_all.bat" from Miui's fastboot firmware installer and drop it in santosh's moded firmware files list? That would be just way to convenient, but keeping my fingers crossed lol.

Tin_Man_0 said:
Thanks! I'll give these a try, but what I was looking for and don't see where exactly to download is that batch file and version of twrp that was show on the video. They launched a batch file and adb waited for the phone and then off it went. I assume that these some extra little steps added to the batch file besides the "fastboot flash recovery recovery.img" routine? Also, the moded ROM looks intresting from the pling page. Can if just copy the "flash_all.bat" from Miui's fastboot firmware installer and drop it in santosh's moded firmware files list? That would be just way to convenient, but keeping my fingers crossed lol.
Click to expand...
Click to collapse
On MIUI 12 Android 10: MOD EDIT: Link Removed
On MIUI 12.5 Android 11: MOD EDIT: Link Removed
The batch and twrp are inside each fastboot zip.
Yeah, don't mix flash_all.bat from a stock MIUI with any custom ROM.
Compass.

Yes! You are the man! Finally. It took every try too ciz I had even found a BRP Twrp, just one version prior to the link you provied Ver 2.7 and that still failed. Tried it a couple dozen which ways too. But this last one finally did the trick. I noticed they went and hid all the files and left only the batch files to launch. I'm guessing people were trying to use the files the wrong way lol. So one last question, cuz I got TWRP running now on my phone and I'm wondering if it'll still be there if I reboot it? I assume this twrp automatically kills the MIUI recovery restore from attempting to take back the recovery?

Tin_Man_0 said:
Yes! You are the man! Finally. It took every try too ciz I had even found a BRP Twrp, just one version prior to the link you provied Ver 2.7 and that still failed. Tried it a couple dozen which ways too. But this last one finally did the trick. I noticed they went and hid all the files and left only the batch files to launch. I'm guessing people were trying to use the files the wrong way lol. So one last question, cuz I got TWRP running now on my phone and I'm wondering if it'll still be there if I reboot it? I assume this twrp automatically kills the MIUI recovery restore from attempting to take back the recovery?
Click to expand...
Click to collapse
I haven't tested either of those recoveries myself but both should survive a MIUI reboot (I've downloaded both recoveries and looking at the files inside they should stay).
The first video I posted covers TWRP for both MIUI 12.0.x and MIUI 12.5.x.
User Alice! got TWRP to be permanent (she's on stock MIUI): https://forum.xda-developers.com/t/cant-flash-custom-recovery.4318347/
Compass.