I have TWRP installed and everytime I try to install the newest version I load into TWRP and get an error. Any way to either relock the bootloader or force the update?
Flash stock recovery
Enviado desde mi CLT-L09 mediante Tapatalk
TWRP has a fixed fingerprint key that doesn't work anymore with recent updates... If you are not using a custom ROM that supports TWRP (like AmazeROM) your only option is to flash stock recovery back (if you are using a custom ROM, and probably you are since you still have TWRP, probably you need to install other stock files as well, so maybe it's just simpler to flash stock firmware back).
davigar said:
Flash stock recovery
Enviado desde mi CLT-L09 mediante Tapatalk
Click to expand...
Click to collapse
lfom said:
TWRP has a fixed fingerprint key that doesn't work anymore with recent updates... If you are not using a custom ROM that supports TWRP (like AmazeROM) your only option is to flash stock recovery back (if you are using a custom ROM, and probably you are since you still have TWRP, probably you need to install other stock files as well, so maybe it's just simpler to flash stock firmware back).
Click to expand...
Click to collapse
Thanks guys! I'll just flash the stock recovery. seems the most simple since the OS is stock.
Related
I have official unlocked bootloader, with TWRP that patches boot.img automatically, and rooted Global Beta ROM on SD version. I successfully flashed full ROM zip without any problem, by just flashing in TWRP without any modifications or any other boot.img.
But I never flashed OTA before. I'm a little paranoid about this, I don't wanna brick my phone again. By my given condition, I should be able to flash OTA zips without any modifications, and keeping my TWRP and unlocked bootloader, right?
Sent from my Redmi Note 3 using Tapatalk
Did you flash official TWRP?
Klanac89 said:
Did you flash official TWRP?
Click to expand...
Click to collapse
No I didn't. I flashed the modified one that I do not have to flash boot.img when flashing miui rom
Sent from my Redmi Note 3 using Tapatalk
You don't need boot.img if you use official TWRP.
http://linuxwelt.blogspot.de/2016/04/twrp-recovery-flashen-xiaomi-anleitung.html
Flash TWRP (just check the Screenshots) and after that you can flash OTA without problems (I did it 2 times). Have no problems.
But first take the new TWRP and make a backup with EFS on a USB Stick or sd card. If something go wrong you can restore your RN3P.
Official twrp?
Lol yea u mite be able to flash ota with official twrp but won't it lock the bootloader and boot.img..
But there mite be a way to make it work .
Use the original boot.img of the current ROM and flash then flash the otathat(so there won't be error 7) will fix the issue .and the twrp will auto patch the boot.img after update
So i am on the new miui using the oficial flash thing (unlocked bootloader oficialy).
The thing is i always wanted to get root and use a kernel on xda here that gives more available memory and solves some of the heating problems when charging (but i know need TWRP ofc) .
So i went to here and checked a few guides however there are many twrp's versions some of them i can't flash miui oficial roms, some of them i need installl boot.img every single time or when i want to restore backup is not just select the backup and done, i need to do something else (is a bit confusing)... so instead i decided to ask you guys directly
The question is:
- If i wanted to use oficial miui but have root and install a kernel and in future just flash the new miui rom again without any stress (just twrp -> flash-> select rom and gapps and done), no boot.img bull****, no flash another twrp etc is it possible??
(before this phone i had moto g(1st gen) and was easy as to put ONE twrp and then would be always flash rom + gapps every single time, no boot.img no firmware, worked for CM12, 12.1 and 13)
Install Alka recovery and back up all the partitions before doing anything.
tigax said:
- If i wanted to use oficial miui but have root and install a kernel and in future just flash the new miui rom again without any stress (just twrp -> flash-> select rom and gapps and done), no boot.img bull****, no flash another twrp etc is it possible??
Click to expand...
Click to collapse
Although I haven't tried it personally, the TWRP explanation guide here says the Cofface TWRP (linked on that page) automatically patches the boot.img when you flash a new ROM, which I believe solves your problem.
harishmenace said:
Install Alka recovery and back up all the partitions before doing anything.
Click to expand...
Click to collapse
so this one allows me to flash new roms from Miui? without any boot.img and stuff?
tigax said:
so this one allows me to flash new roms from Miui? without any boot.img and stuff?
Click to expand...
Click to collapse
Yes, I was doing it all the time.
Sent from my Redmi Note 3 using Tapatalk
timberwolf60 said:
Yes, I was doing it all the time.
Click to expand...
Click to collapse
Thank you will use then
I know OTA updates are generally frowned up in here, but my point is that they should work.
I've been trying to get my OPX to upgrade to 3.1.3, and despite being offered the official OTA update, it won't install.
What state should the phone be in (recovery etc.) for the OTA to work? I've done a factory reset, wiped data and cache and fastboot oem lock / unlock to try and resest it, with no luck.
Sent from my ONE E1003 using Tapatalk
Fastboot flash old stock recovery. Then flash 2.2.3 with no extras and should be able to update. OTA won't work if the system partion has been modified ie TWRP etc.
Exodusche said:
Fastboot flash old stock recovery. Then flash 2.2.3 with no extras and should be able to update. OTA won't work if the system partion has been modified ie TWRP etc.
Click to expand...
Click to collapse
Thanks. I probably have modified the system partition. How do I unmodify it?
Sent from my ONE E1003 using Tapatalk
maxnutter said:
Thanks. I probably have modified the system partition. How do I unmodify it?
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
Get the flashable zips of 3.1.3 or 3.1.4 and shouldn't be issue once you have stock recovery and 2.2.3 installed.
Exodusche said:
Get the flashable zips of 3.1.3 or 3.1.4 and shouldn't be issue once you have stock recovery and 2.2.3 installed.
Click to expand...
Click to collapse
Nope, doesn't work.
It flashes from stock recovery okay, but hangs at the 1+ logo on reboot.
Would formatting the userdata partition from stock recovery get it back to a pre TWRP state?
Sent from my ONE E1003 using Tapatalk
OK so I'm on cm13 and I initially wanted to flash cm14.1 so I flashed the updated TWRP (v3.0.2-0 bc 3.0.2-1 wouldn't boot) and I factory reset and try to flash cm14.1 but I get an error7 and I read that that might be bc I'm on the old bootloader so I try to flash OOS 3.1.4 (newest to my knowledge) but that also fails with an error7 and I tried flashing the stock recovery via fastboot but it won't boot.. any suggestions?
Sent from my Pixel XL using XDA-Developers mobile app
ArmStrongDickPunch said:
OK so I'm on cm13 and I initially wanted to flash cm14.1 so I flashed the updated TWRP (v3.0.2-0 bc 3.0.2-1 wouldn't boot) and I factory reset and try to flash cm14.1 but I get an error7 and I read that that might be bc I'm on the old bootloader so I try to flash OOS 3.1.4 (newest to my knowledge) but that also fails with an error7 and I tried flashing the stock recovery via fastboot but it won't boot.. any suggestions?
Click to expand...
Click to collapse
Look here
http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917/page1
saurabh40629 said:
Look here
http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917/page1
Click to expand...
Click to collapse
Thanks, I figured it out tho, I had to flash OOS v2.2.0 and it boot fine then after a little searching I found my stock recovery backup from OOS 2.2.0 and it worked, and now I'm updating it to the newest oos version by the OTA in system and after I'm done and fully updated, I'll reflash the latest TWRP and make a nadroid backup and try flashing cm14.1
Sent from my Pixel XL using XDA-Developers mobile app
ArmStrongDickPunch said:
Thanks, I figured it out tho, I had to flash OOS v2.2.0 and it boot fine then after a little searching I found my stock recovery backup from OOS 2.2.0 and it worked, and now I'm updating it to the newest oos version by the OTA in system and after I'm done and fully updated, I'll reflash the latest TWRP and make a nadroid backup and try flashing cm14.1
Click to expand...
Click to collapse
Yeah.. Little long way. But whatever fixes your problem.
saurabh40629 said:
Yeah.. Little long way. But whatever fixes your problem.
Click to expand...
Click to collapse
Hey quick question, do I need to reunlock the bootloader after the method I did? The reason I'm asking is bc when I boot into fastboot to try to reflash twrp (after flashing) I reboot to recovery and it's still the stock recovery? Any suggestions? Thanks
Sent from my Pixel XL using XDA-Developers mobile app
ArmStrongDickPunch said:
Hey quick question, do I need to reunlock the bootloader after the method I did? The reason I'm asking is bc when I boot into fastboot to try to reflash twrp (after flashing) I reboot to recovery and it's still the stock recovery? Any suggestions? Thanks
Click to expand...
Click to collapse
If it's already unlocked, you don't need to do it. Did you lock it again? If you have bootloader locked, flashing recovery will fail. Anyways unlocking will not hurt. FYI Just don't lock bootloader unless you are totally stock with stock recovery.
saurabh40629 said:
If it's already unlocked, you don't need to do it. Did you lock it again? If you have bootloader locked, flashing recovery will fail. Anyways unlocking will not hurt. FYI Just don't lock bootloader unless you are totally stock with stock recovery.
Click to expand...
Click to collapse
I didn't relock it but was curious if by reverting to stock and updating to the latest version of oos that it might be locked considering I'm on the newest bootloader now or so I think at least haha
Sent from my Pixel XL using XDA-Developers mobile app
ArmStrongDickPunch said:
I didn't relock it but was curious if by reverting to stock and updating to the latest version of oos that it might be locked considering I'm on the newest bootloader now or so I think at least haha
Click to expand...
Click to collapse
No it will not. I hope you have solved your issue by now.
Hello,
I am a newbie into this.
I want to root the Pad to run some apps that require root access. The bootloader is already unlocked via the miflash unlock tool.
Next I tried to install TWRP 3.4.0.0 via using the guide from twrp.me
https://twrp.me/xiaomi/xiaomimipad4.html
I am able to load the image into recovery section and I am also able to boot into recovery straight after that in order to enter TWRP (using Vol up plus power button as the guide mentioned). But once the Android system is booted up the TWRP bootloader in the recovery section is gone/wiped whatever because the Mi boot menu appears again.
What do I miss out?
It is also recommend to perform a backup in TWRP before rooting (magisk) or flashing a custom rom. The backup fails with a couple of red line "unable to mount...".
Any help is appreciated. Thanks.
You are using the stock MIUI right? MIUI will automatically revert recovery back to the stock one. You have to install a custom rom to retain TWRP.
Never_Sm1le said:
You are using the stock MIUI right? MIUI will automatically revert recovery back to the stock one. You have to install a custom rom to retain TWRP.
Click to expand...
Click to collapse
Correct still using stock MIUI. Sadly, that means root and stock MIUI won't work at the same time.
andyyy1 said:
Correct still using stock MIUI. Sadly, that means root and stock MIUI won't work at the same time.
Click to expand...
Click to collapse
Although I never use stock MIUI, I think you can root normally. You don't need TWRP to maintain root.