Database Develop

Unable to flash TWRP after with OOS 4.0.2

I flashed TWRP with succes according to cmd. But when booting to recovery it gives me the stock recovery. I had the same problem with my OPX. Someone on here said that MM had a new bootloader so i had a TWRP that was compatible with that bootloader. Is this the same for OP3T? If so can anyone link this

medick_ said:
I flashed TWRP with succes according to cmd. But when booting to recovery it gives me the stock recovery. I had the same problem with my OPX. Someone on here said that MM had a new bootloader so i had a TWRP that was compatible with that bootloader. Is this the same for OP3T? If so can anyone link this
Click to expand...
Click to collapse
flash twrp 3.0.4.0 (in OP3 forums, now unified), from fastboot boot immediately to recovery it should boot TWRP, flash SuperSU or similar (or kernel that will rename stock recovery) to keep TWRP, reboot recovery from TWRP to check it works, reboot to system and profit.
if you don't root, stock recovery will keep coming back.

Update TWRP to 3.0.2.0 - XZDualRecovery

Hello, I installed TWRP via XZDualRecovery ( https://forum.xda-developers.com/showthread.php?t=2647487 ), because I have locked bootloader.
I want to update TWRP to 3.0.2.0. I tried TWRP app from Play Store - it said "Flash succesful", but I stil have 2.8.7.0. I wanted to flash 3.0.2.0 image via TWRP, but I can flash .img only to Kernel partition - no option to flash to recovery partition shows.
I'm new to this. Is there other some way to flash recovery or I have to wait for XZDualRecovery update? (Not sure if fastboot would work - i have locked bootloader)
Thanks!
(And sorry for my bad english ^^)

Install it to your FOTAKernel and than another rom because I think stock .236 doesnt work with recovery partition.

I've should also wrote, that I'm not using stock ROM, but DStrikerZ1's ROM.
But thanks, I'll take a look at that FOTAKernel thing ^^

Installing Twrp 3.1.x or 3.2.x in order to ultimately install CarbonROM

Long time ago, I switched to CM12.1, and I figured I would give a try to CarbonROM (Lineage = CM's successor and I used CM and didn't like it much, omnirom = too new and probably buggy, carbonrom = still maintained and "older").
Here's what I did so far:
- downgraded to 23.0.A.2.93 (4.4.4) (flashed ftf with flashtool)
- rooted it using giefroot 3.1
- installed twrp using another tool with an installer (http://nut.xperia-files.com/)
- then upgraded to pre-rooted version of .291 D5803_23.5.A.1.291_1289-7524_R5D_PreRooted_RecRoot_v4_SuperSU_276.zip, which comes with TWRP 3.0.2.0 (did that using twrp I had just installed)
Then my plan was to upgrade directly to CarbonRom by flashing from TWRP, but it gives me the error 7, so I figured I'd just upgrade TWRP but:
- tried upgrading TWRP (followed instructions here:https://forum.xda-developers.com/z3-compact/general/d5803-z3c-aries-twrp3-0-t3543113), using lineage or omni recovery: will flash "successfully" with fastboot, but when I actually go into recovery mode it's the same old twrp version
- tried flashing the img directly from old twrp version, both recoveries, and same results: when I reboot to recovery, it's the same old version.
I'm therefore stuck right now and can't figure out what I'm doing wrong, nor how I could work around this issue.
Installed twrp 3.1.1 from zip, which allowed me to install Carbon.
Still trying to figure out why flashing didn't work, and why the zip did. Anybody can tell me?
Edit: phone is a D5803. unlocked bootloader, TA partition backed up (just in case), i have latest flashtool, drivers are installed, I know how to go into fastboot, I know how to flash a zip...

Try to flash FOTAKernel instead of recovery
Example:
Code:
fastboot.exe flash FOTAKernel "recovery-Lineage 14.1.img"

How to install TWRP

Nwver had problem like that, but I canno manage it on my own.
What I have:
rooted E1 Single (e2005),
kernel with Philx Touch,
zip with FalconSS Revamp R2,
zips with TWRP 2 and TWRP 3.
What I do:
Flash kernel with Philz.
Copy zips to E1.
Boot to Philz.
Flash FalconSS.
Flash either of TWRPs.
WIpe Cache and Dalvik.
Bootloop on Sony logo.
Should I use normal Falcon? (will try it in a moment)
Or maybe other stock firmware? (have 20.1.A.2.19)
All I want is working TWRP with support for Nougat.

Ok. Normal Falcon was what I needed. Now LOS14.1 is booting

Stock boot.img is not booting on boot_b

Hi there,
I've been rooting phones since Android 2, but lately it has been quite a challenge.
What I did so far:
Unpack new Xiaomi MI A2 (jasmine) device
Enabled Developer, USB debugging, OEM unlock in Android settings
Code:
fastboot oem unlock
Code:
fastboot flash boot_b TWRP-3.2.3-jasmine-20180804.img
TWRP ran fine. However, started with boot_a again.
OTA updated (about 6 times) to the newest version (Android 10, QKQ1.190910.002 V11.0.12.0.QDIMIXM)
Code:
fastboot flash boot_b twrp-3.4.0-0-jasmine_sprout.img
TWRP started only to the splash screen (showing "teamwin" and "Recovery Project 3.4.0-0"). Why is TWRP not starting properly?
Downloaded the stock fastboot image V11.0.12.0.QDIMIXM from https ://xiaomifirmwareupdater.com/archive/miui/jasmine/ and flash the stock boot.img via
Code:
fastboot flash boot_b jasmine_global_images_V11.0.12.0.QDIMIXM_10.0/images/boot.img
(my goal is to later patch it with Magisk and then install the patched version). However, the stock boot.img just hangs forever on the androidone screen. Why is the stock boot.img not starting properly?
I haven't used the Mi Unlock app and I didn't do an "fastboot flashing unlock_critical" yet. Is this necessary? What do I have to do to make the boot images work?

floydsen said:
Hi there,
I've been rooting phones since Android 2, but lately it has been quite a challenge.
What I did so far:
Unpack new Xiaomi MI A2 (jasmine) device
Enabled Developer, USB debugging, OEM unlock in Android settings
TWRP ran fine. However, started with boot_a again.
OTA updated (about 6 times) to the newest version (Android 10, QKQ1.190910.002 V11.0.12.0.QDIMIXM)
TWRP started only to the splash screen (showing "teamwin" and "Recovery Project 3.4.0-0"). Why is TWRP not starting properly?
Downloaded the stock fastboot image V11.0.12.0.QDIMIXM from https ://xiaomifirmwareupdater.com/archive/miui/jasmine/ and flash the stock boot.img via (my goal is to later patch it with Magisk and then install the patched version). However, the stock boot.img just hangs forever on the androidone screen. Why is the stock boot.img not starting properly?
I haven't used the Mi Unlock app and I didn't do an "fastboot flashing unlock_critical" yet. Is this necessary? What do I have to do to make the boot images work?
Click to expand...
Click to collapse
why do you feel you must use boot images ...the tried and working method for "jasmine" is to boot custom recovery and then flash magisk zip ( root only ) ..or...flash custom recovery installer zip which will flash recovery to both a/b slots.. then flash magisk
to properly boot you need to overcome stuff like secure boot and force encryption
if you aren't planning on custom roms just boot twrp to flash magisk
or
flash installer zip for recovery and wipe everything including formatting data to remove encryption and boot directly to recovery to install custom rom
twrp custom recovery had problems with decryption on stock rom ...secure boot won't allow booting modified images ..
lastly remember on jasmine there is no recovery partition..so everything is in the boot image ..magisk and recovery ..so everytime you flash stock , stock boot overwrites these changes and should flash everything again
tbh that's why i converted to wayne to get old partition layout as the A/B story pissed me off

KevMetal said:
why do you feel you must use boot images ...the tried and working method for "jasmine" is to boot custom recovery and then flash magisk zip ( root only ) ..or...flash custom recovery installer zip which will flash recovery to both a/b slots.. then flash magisk
to properly boot you need to overcome stuff like secure boot and force encryption
if you aren't planning on custom roms just boot twrp to flash magisk
or
flash installer zip for recovery and wipe everything including formatting data to remove encryption and boot directly to recovery to install custom rom
twrp custom recovery had problems with decryption on stock rom ...secure boot won't allow booting modified images ..
lastly remember on jasmine there is no recovery partition..so everything is in the boot image ..magisk and recovery ..so everytime you flash stock , stock boot overwrites these changes and should flash everything again
tbh that's why i converted to wayne to get old partition layout as the A/B story pissed me off
Click to expand...
Click to collapse
Ok. So I'm back to Stock image jasmine_global_images_V11.0.12.0.QDIMIXM_10.0 by executing "flash_all.sh". You are saying I should "simply boot". You mean:
Code:
fastboot boot TWRP-3.4.0-0-jasmine_sprout-for_V11.0.12.0.img
right? That doesn't work, it won't boot. How do I overcome secure boot and force encryption?

floydsen said:
Ok. So I'm back to Stock image jasmine_global_images_V11.0.12.0.QDIMIXM_10.0 by executing "flash_all.sh". You are saying I should "simply boot". You mean:
right? That doesn't work, it won't boot. How do I overcome secure boot and force encryption?
Click to expand...
Click to collapse
yes im saying that but post a pic of the error ...why or how doesn't it boot ..
if it is the official twrp just dump it and look for the unofficial Russian one or one modified by Nebrassy or use Orange fox and or Pitch black ..official is broken last time i checked
also the name of that looks like one hell of a job ..shorten it to
recovery.img or twrp.img
fastboot boot recovery.img
but first run
fastboot getvar all
& also run fastboot flashing unlock_critical
but most importantly get another recovery
& i don't want to insult your intelligence but after flashing stock did you check to make sure bootloader was still unlocked and that dev settings was activated and that adb was toggled to on and that you authorised adb again
basicall after stock boot device and do the above ..plug in usb ..toggle adb ..authorise ..run adb devices ..if you see your device ..adb reboot bootloader ..fastboot devices ..see your device ..fastboot getvar all ..see bootloader is unlocked ..fastboot flashing unlock_critical if not done yet ...make sure to do ALL the above again after data gets wiped.....put twrp in adb folder ( MUST BE UNOFFICIAL RUSSIAN OR MODUFIED BY NEBRASSY ..rename to revovery.img ...fastboot boot recovery.img .. use file manager to put magisk.zip on internal then flash ..then reboot to rooted phone with stock recovery ...
Sent from my wayne using XDA Labs

KevMetal said:
why do you feel you must use boot images ...the tried and working method for "jasmine" is to boot custom recovery and then flash magisk zip ( root only ) ..or...flash custom recovery installer zip which will flash recovery to both a/b slots.. then flash magisk
to properly boot you need to overcome stuff like secure boot and force encryption
if you aren't planning on custom roms just boot twrp to flash magisk
or
flash installer zip for recovery and wipe everything including formatting data to remove encryption and boot directly to recovery to install custom rom
twrp custom recovery had problems with decryption on stock rom ...secure boot won't allow booting modified images ..
lastly remember on jasmine there is no recovery partition..so everything is in the boot image ..magisk and recovery ..so everytime you flash stock , stock boot overwrites these changes and should flash everything again
tbh that's why i converted to wayne to get old partition layout as the A/B story pissed me off
Click to expand...
Click to collapse
KevMetal said:
yes im saying that but post a pic of the error ...why or how doesn't it boot ..
if it is the official twrp just dump it and look for the unofficial Russian one or one modified by Nebrassy or use Orange fox and or Pitch black ..official is broken last time i checked
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Of course it is the official one. OMFG twrp-3.4.0-0-jasmine_sprout.img is broken (freezes on the TWRP splash screen), but version 3.3.1 seems to work. That's a relief, so I will try to flash magisk now. Although, I think I will need to do the decryption thing for jasmine first, but I guess I'll follow https://www.the***********.com/install-twrp-recovery-root-xiaomi-mi-a2-a2-lite/ mostly

floydsen said:
Of course it is the official one. OMFG twrp-3.4.0-0-jasmine_sprout.img is broken (freezes on the TWRP splash screen), but version 3.3.1 seems to work. That's a relief, so I will try to flash magisk now. Although, I think I will need to do the decryption thing for jasmine first, but I guess I'll follow https://www.the***********.com/install-twrp-recovery-root-xiaomi-mi-a2-a2-lite/ mostly
Click to expand...
Click to collapse
jajaja well now you know ...be careful ...some "official" roms are also more buggy than unofficial ones for Jasmine/Wayne..
LOS is an example ..so be forewarned .. if you like android 1 i guess stock rooted is a smart option to keep updates and keep device certified for google stuffs . .
alternativeky go FULL custom rom because stock and custom recovery is just a pain and not worth the hassle on an A/B treble device flashable by fastboot ..just boot the recovery when if ever needed
fyi ..you can flash magisk and it will boot ...if you don't try changing the recovery ..so you can have stock rooted with magisk without rcustom recovery...* recommended by me if you only wamt stock with root
Sent from my wayne using XDA Labs

All good now, thanks for your help! I just flashed Magisk (and also TWRP) and everything works nicely! I will need to get some experience, but I'll keep in mind that I maybe want to get rid of the TWRP recovery. Finally security testing is fun again. Thx!