Development [RECOVERY][3.7.0-12.1][UNOFFICIAL] TWRP with A12/A13 encryption support

[ThePresence]

Sounds like you flashed it incorrectly then... If you're trying to use Lineage Recovery then follow the flashing instructions on their OP9Pro wiki page. Also that's the end of our troubleshooting here since it's not TWRP's fault you didn't format data when switching from custom to stock ROM.

I flashed it from TWRP only. I'm now trying to flash lineage.

 

[ChrisFeiveel84]

But now my laptop won't even detect my phone. Is there anything I can do about it?

Adb and fastboot /fastbootd driver installed ?

 

[ThePresence]

Adb and fastboot /fastbootd driver installed ?

Now it's working fine. I'm trying to find a way to flash twrp again.

Edit flashed vendor.boot image and boot.img and now my phone is dead I gues it's not responding at all.

Phone is booted to bootloader now.

 

[ThePresence]

Sounds like you flashed it incorrectly then... If you're trying to use Lineage Recovery then follow the flashing instructions on their OP9Pro wiki page. Also that's the end of our troubleshooting here since it's not TWRP's fault you didn't format data when switching from custom to stock ROM.

Is there anyway to flash twrp via fastboot?

 

[IamTheBRAVE]

Is there anyway to flash twrp via fastboot?

You flashed twrp boot.img on top of your rom i think. You need to flash your rom's boot and vendor boot imgs with same commands.
At least that's how i'd do it. Maybe someone can add to this...

 

[der_akinator]

Is there anyway to flash twrp via fastboot?

The best way is probably to use installation option 3. I don't know which partitions you flashed with which ROM/firmware images but if all partitions are setup as described by your ROM maintainer option 3 should work.

 

[der_akinator]

Works great on 9 pro oos13 F17. One issue I've noticed is factory data reset doesn't work until you unmount and mount data. Also "Failed to mount '/vendor_dlkm ' ( Block device required" showed but doesn't seem to cause any issues.
Data restore worked didn't try to restore super.img yet tho.
It does work installing .img from internal storage. Tried super.img and boot.img both successful.

Could you safe the logcat output from the factory reset problem? Otherwise I can't do much. The vendor_dlkm thing is already listed at bugs but isn't problematic.

I didn't know twrp can flash super images. Do you think it's possible by directly flashing super to switch from custom roms back to stock? It seems that thsi is currently only possible with the MSM tool. Maybe I will try that.

 

[JWnSC]

Could you safe the logcat output from the factory reset problem? Otherwise I can't do much. The vendor_dlkm thing is already listed at bugs but isn't problematic.

I didn't know twrp can flash super images. Do you think it's possible by directly flashing super to switch from custom roms back to stock? It seems that thsi is currently only possible with the MSM tool. Maybe I will try that.

Not near a PC currently I'll grab log later. You would need more than super.img (boot, dtbo,vendor_boot..ect)to switch from customs back to stock. If you create a flashable.zip it's possible. Most customs that are out lately have fw included. I've used twrp to flash A12 & A13 customs.. Even though it's not recommended stay decrypted though so it's easier to switch between roms.
Recently flashed an ext4 r/w oos13 super.img(converted from erofs) using this twrp with no issues.
I'm only using fastboot and recovery to flash between stock and customs. If you need anything to test let me know. Thanks for your work

 

[ThePresence]

So I have used msm tool and I'm on OOS13 and I want to switch to custom rom 13. What are the steps I should follow. Do I need to wipe internal storage also?

 

[psychemisha]

So I have used msm tool and I'm on OOS13 and I want to switch to custom rom 13. What are the steps I should follow. Do I need to wipe internal storage also?

Msm back to a12 and fpash c 63 firmware then you ready

 

[jamescable]

So I have used msm tool and I'm on OOS13 and I want to switch to custom rom 13. What are the steps I should follow. Do I need to wipe internal storage also?

Just flash the C.63 firmware flasher

 

[TheSayaMan]

Now it's working fine. I'm trying to find a way to flash twrp again.

Edit flashed vendor.boot image and boot.img and now my phone is dead I gues it's not responding at all.

Phone is booted to bootloader now.

If you flashed boot then that's the problem. You don't flash boot. You boot it first.
fastboot boot boot.img
Follow the instructions and you won't have any problems.

 

[cave.man1908]

Absolutely amazing! Thank you! Thank you! Thank you!

 

[Skynet30]

I have TWRP, Magisk and OOS F.17 on my 2nd device. It is running w/o issues, I'm just wondering if there is something to take into account with OTA updates? My gut tells me I should only install full .zips from oxygen updater since TWRP and Magisk alter the boot.img and the image restore option in Magisk would only "restore" the boot.img to a state that still has twrp in it and incremental OTA would fail. Correct?

Update procedure should then be:
1. install the full zip from Oxygen Updater
2. install magisk to "inactive" slot
3. reboot to system
4. install TWRP zip from Magisk Manager
5. profit?

 

[TheSayaMan]

I have TWRP, Magisk and OOS F.17 on my 2nd device. It is running w/o issues, I'm just wondering if there is something to take into account with OTA updates? My gut tells me I should only install full .zips from oxygen updater since TWRP and Magisk alter the boot.img and the image restore option in Magisk would only "restore" the boot.img to a state that still has twrp in it and incremental OTA would fail. Correct?

Update procedure should then be:
1. install the full zip from Oxygen Updater
2. install magisk to "inactive" slot
3. reboot to system
4. install TWRP zip from Magisk Manager
5. profit?

The OTA would definately fail if you have the T-Mobile variant, but not on the Global variant. Not sure about the India, or Europe variants. If you have the T-mobile variant, it won't work because you have to install update first before you install magisk to inactive slot and it will detect root and fail. However the Global version will work and I'm not sure of the rest. Wouldn't hurt to try. Won't brick your phone for trying, it will just fail.

 

[rboone18]

Wow last time u could install twrp within Android so easy , no man this way is easiest way to install twrp then all years I can remember because I remember twrp app wasnt as easy as install as this

 

[jamescable]

Wow last time u could install twrp within Android so easy , no man this way is easiest way to install twrp then all years I can remember because I remember twrp app wasnt as easy as install as this

Just flash the magisk version

 

[rboone18]

First time I ever been told I could flash twrp via magisk

 

[rboone18]

I always did boot twrp.img or flash twrp.img or million other steps. Right now I am after get gf her Christmas present next week having to replace USB port. Not sure exactly , I don't do hardware got someone locally going to put new one in

 

[TheSayaMan]

Unfortunately I had to give up on this because every time I flash a custom rom update, my phone bootloops and ultimately I have to factory reset, format data and start all over. Custom recovery works fine with updates. reboot to bootloader, fastboot --set-active=other then reboot to recovery, adb sideload rom, reboot recovery, adb sideload gapps. reboot to system, no issues. I tried all recommendation to install via twrp will all failures. I reboot to twrp, install update rom, it automatically flashes to opposite slot, I reboot twrp, install gapps, phone boots up with all kinds of force closes. I've tried flashing update then not rebooting and then flashing gapps and doesn't boot at all. I give up!! Staying on custom recovery. Too bad because it would be nice to not use my computer for updates.