Database Info

[GUIDE] HOW To Multiboot on Lenovo P2

Hi guys I'll share with you how to multiboot roms on Lenovo P2 using an app called DualBoot Patcher.
Currently I'm using 3 roms, they're simultaneously installed on my phone and all I need to switch the rom is a single tap via the app we'll discuss below.
The roms I have installed right now:
-S062_170117_ROW as primary
-RR 5.8.2 as secondary
-S232_170320_ROW as data-slot
As you may already think about it, yes having 3 roms or more installed on your phone is eating your internal storage a bit.
Check the shots attached below for all the storage details for each Rom. I currently have 12GB free on the internal storage.
---
Okay let's start with the tutorial.
Requirements:
-Root
-Unlocked Bootloader
First of all I want to say Big Thanks to the developer of the DualBoot Patcher @chenxiaolong. Feel free to visit the official thread of the app, say/press thanks and if you're good even donate to him.
Also you can thank me for adding our great device Lenovo P2 to the supported devices. I opened pull request on GitHub that is already processed.
I'll start with the steps of my tutorial:
1)
The first thing of course is to download the app from it's official page
As of the time this guide is written make sure to download the build 9.2.0.r8.g4da14ed or newer as the older builds don't support Lenovo P2. Currently only the P2a42 model is supported, if there is interest from a P2c72 owners I'll add a pull request on GitHub.
2)
You have the apk, install it and set the kernel when the app asks you. Good thing is to update the ramdisk of the primary rom, but you still can multiboot even if you didn't. You can force update the ramdisk by hitting the update ramdisk button 3 times. Always reboot after setting kernel or updating the ramdisk.
3)
Now I assume you have the zip file for the other rom. Select "Patch zip file" from the side menu and choose where to install it. You have a choice of:
-Primary Rom Upgrade (not recommended, it will override your primary rom! For security reasons can only be selected from a rom different from primary.)
-Secondary (I recommend this if you wish to use only 2 Roms, the rom will be installed on the same partition as the primary rom, it won't affect the internal storage. Only the data will be on internal. The system partition of P2 is 3.87GB and you can put 2 roms there easily.)
-Multi-slot (not recommended, suitable for phones with large cache partitions, 1.5-2G)
-Data-slot (this will affect your internal storage, system and data on internal, reliable option if you use 3 or more roms.
-Extsd-slot ( the rom will be installed on your extsd card! Yeah you hear me, an awesome feature, but unfortunately kind of unstable, you have issues here and there and also you have slightly decreased performance as you're running the rom from your sdcard which is several times slower than the internal storage unless you're running one of the most expensive extsd cards.
Select secondary or data slot, choose a save path and patch the rom.
4)
Install the rom. Easy as it sounds. Press the pink button in bottom right, press it once again and select the rom you patched in the previous step. As you can see you can even restore a backup made with the app. It's not for restoring a twrp backup. You can backup roms within the DualBoot Patcher. Also you can flash roms patched with this app in twrp. Choose where to install it or leave it as it is and press the ✓ button in up right. The rom will be flashed.
Important! Don't switch to another app or do anything else when the rom is being installed, otherwise the patcher will crash! 1-2 minutes and you're done, not much of a waiting.
5)
Hey you made it. You now have 2 roms simultaneously installed on your phone! When you install a new rom the patcher will automatically switch to it. That doesn't mean it will auto reboot to the new rom, it will just switch to it in the Roms list, you can always switch to the primary or other rom again. I think that's pretty much about it guys. Now just switch to the new rom and select reboot from the side menu of the patcher, it will reboot to the new rom. You can repeat the procedure as many times as you want.
My record is 8 Roms, that was in the past with other phone. Because of this crazy number I'm a proud winner of the gold medal for the "Most number of multiboot roms installed lmao.
If you have questions feel free the write below and as always hit thanks if I was helpful. See ya. :highfive:
Update: Starting from build 9.2.0.r54.g8b79a2b the patcher now supports the P2c72 too!

so my P2c72 is on the way, you think it's not supported? Isn't everything the same except for the internal space? I was planning to flash the official P2a42 ROM anyways.
Thoughts?

tanush said:
so my P2c72 is on the way, you think it's not supported? Isn't everything the same except for the internal space? I was planning to flash the official P2a42 ROM anyways.
Thoughts?
Click to expand...
Click to collapse
I don't think, I'm sure it's not supported because I put the codenames on github and P2c72 is not in the list. No problem if you want to multiboot I'll add it in no time. You can flash all the roms available here for p2a42 on your P2c72 just fine by removing the first lines "assert get prop" in the updater-script. You can flash these roms the usual way via twrp. But if you use the DualBoot Patcher as for now it won't recognize the P2c72.

911-Future_Maker said:
I don't think I'm sure it's not supported because I put the codenames on github and P2c72 is not on the list. No problem if you want to multiboot I'll add it in no time.
Click to expand...
Click to collapse
Cheers! My phone is on the way from china. Might be another week or so Right now just browsing everything that we have here.
Thanks for this. After so many ROMS ported recently, this would really help me out with having one stable daily driver and others to try to. Not an android developer but I'd like to try my hands as well finally to make a ROM and maybe look into the two bugs that are persistent across all ROMS. Let's see. I've just developed apps for now.
Anyways, thanks, this is indeed good stuff.

Yes, I love this app. It's the future of Rom's flashing, just switching between Roms like a boss. Btw congrats you bought the P2c72, it's 64gb right?

911-Future_Maker said:
Yes, I love this app. It's the future of Rom's flashing, just switching between Roms like a boss. Btw congrats you bought the P2c72, it's 64gb right?
Click to expand...
Click to collapse
yes, thats the only reason I had to get it from china. Apparently, only 32 gb version is available outside china.

Thank You Bro

Starting from build 9.2.0.r54.g8b79a2b the patcher now supports the P2c72 too!

911-Future_Maker said:
Starting from build 9.2.0.r54.g8b79a2b the patcher now supports the P2c72 too!
Click to expand...
Click to collapse
thanks, waiting for the bootloader to get done with its 15 days. All ready to flash everything!
Although can you tell me how it works? Like my phone is flashed with the global p2a42 ROM but it is p2c72. Should I change the name in build.prop?

tanush said:
thanks, waiting for the bootloader to get done with its 15 days. All ready to flash everything!
Although can you tell me how it works? Like my phone is flashed with the global p2a42 ROM but it is p2c72. Should I change the name in build.prop?
Click to expand...
Click to collapse
This is why I made this tutorial, just follow it closely and all will be fine. You don't need to mess with the build.prop.

911-Future_Maker said:
Starting from build 9.2.0.r54.g8b79a2b the patcher now supports the P2c72 too!
Click to expand...
Click to collapse
911-Future_Maker said:
This is why I made this tutorial, just follow it closely and all will be fine. You don't need to mess with the build.prop.
Click to expand...
Click to collapse
Sorry brother didn't go through as I can't actually do it. Still waiting on my bootloader :/

So anyone had any success with p2c72?
I tried, but it fails. Doesn't throw any error but gets stuck in the boot and eventually reboots in twrp.
My only doubt is how does it know that the phone is p2c72? The build.prop says p2a42 so does the app thinks that its p2142 and wrongly patch it?

Is this just for experimenting or is there any advantage using 2 os same time? Isn't this can be cause a heat problem because of the more cpu/ram usage?

Can't find supported version of app! Can anyone here help me out wuth version?
---------- Post added at 04:29 AM ---------- Previous post was at 04:20 AM ----------
911-Future_Maker said:
Hi guys I'll share with you how to multiboot roms on Lenovo P2 using an app called DualBoot Patcher.
Currently I'm using 3 roms, they're simultaneously installed on my phone and all I need to switch the rom is a single tap via the app we'll discuss below.
The roms I have installed right now:
-S062_170117_ROW as primary
-RR 5.8.2 as secondary
-S232_170320_ROW as data-slot
As you may already think about it, yes having 3 roms or more installed on your phone is eating your internal storage a bit.
Check the shots attached below for all the storage details for each Rom. I currently have 12GB free on the internal storage.
---
Okay let's start with the tutorial.
Requirements:
-Root
-Unlocked Bootloader
First of all I want to say Big Thanks to the developer of the DualBoot Patcher @chenxiaolong. Feel free to visit the official thread of the app, say/press thanks and if you're good even donate to him.
Also you can thank me for adding our great device Lenovo P2 to the supported devices. I opened pull request on GitHub that is already processed.
I'll start with the steps of my tutorial:
1)
The first thing of course is to download the app from it's official page
As of the time this guide is written make sure to download the build 9.2.0.r8.g4da14ed or newer as the older builds don't support Lenovo P2. Currently only the P2a42 model is supported, if there is interest from a P2c72 owners I'll add a pull request on GitHub.
2)
You have the apk, install it and set the kernel when the app asks you. Good thing is to update the ramdisk of the primary rom, but you still can multiboot even if you didn't. You can force update the ramdisk by hitting the update ramdisk button 3 times. Always reboot after setting kernel or updating the ramdisk.
3)
Now I assume you have the zip file for the other rom. Select "Patch zip file" from the side menu and choose where to install it. You have a choice of:
-Primary Rom Upgrade (not recommended, it will override your primary rom! For security reasons can only be selected from a rom different from primary.)
-Secondary (I recommend this if you wish to use only 2 Roms, the rom will be installed on the same partition as the primary rom, it won't affect the internal storage. Only the data will be on internal. The system partition of P2 is 3.87GB and you can put 2 roms there easily.)
-Multi-slot (not recommended, suitable for phones with large cache partitions, 1.5-2G)
-Data-slot (this will affect your internal storage, system and data on internal, reliable option if you use 3 or more roms.
-Extsd-slot ( the rom will be installed on your extsd card! Yeah you hear me, an awesome feature, but unfortunately kind of unstable, you have issues here and there and also you have slightly decreased performance as you're running the rom from your sdcard which is several times slower than the internal storage unless you're running one of the most expensive extsd cards.
Select secondary or data slot, choose a save path and patch the rom.
4)
Install the rom. Easy as it sounds. Press the pink button in bottom right, press it once again and select the rom you patched in the previous step. As you can see you can even restore a backup made with the app. It's not for restoring a twrp backup. You can backup roms within the DualBoot Patcher. Also you can flash roms patched with this app in twrp. Choose where to install it or leave it as it is and press the ✓ button in up right. The rom will be flashed.
Important! Don't switch to another app or do anything else when the rom is being installed, otherwise the patcher will crash! 1-2 minutes and you're done, not much of a waiting.
5)
Hey you made it. You now have 2 roms simultaneously installed on your phone! When you install a new rom the patcher will automatically switch to it. That doesn't mean it will auto reboot to the new rom, it will just switch to it in the Roms list, you can always switch to the primary or other rom again. I think that's pretty much about it guys. Now just switch to the new rom and select reboot from the side menu of the patcher, it will reboot to the new rom. You can repeat the procedure as many times as you want.
My record is 8 Roms, that was in the past with other phone. Because of this crazy number I'm a proud winner of the gold medal for the "Most number of multiboot roms installed lmao.
If you have questions feel free the write below and as always hit thanks if I was helpful. See ya. :highfive:
Update: Starting from build 9.2.0.r54.g8b79a2b the patcher now supports the P2c72 too!
Click to expand...
Click to collapse
Not able to find the version as mentioned. Tried newer version but not supported.

Multuboot log uploaded.

What to do for setting up kernel in 2nd step?

Hi , dual boot patcher app crash every time whenever I try to flash patched ROM in ROM section .pls help me with that .I really want it

muniphs said:
Hi , dual boot patcher app crash every time whenever I try to flash patched ROM in ROM section .pls help me with that .I really want it
Click to expand...
Click to collapse
Try different version.

kanwaljeetsm said:
Try different version.[/QUOTE
Thanks for reply
I tried these both versions
DualBootPatcherAndroid-9.2.0.r54.g8b79a2b
And
DualBootPatcherAndroid-9.2.0.r8.g4da14ed
These are recommended on this thread
Is there any other supported version for our model
Click to expand...
Click to collapse

muniphs said:
kanwaljeetsm said:
Try different version.[/QUOTE
Thanks for reply
I tried these both versions
DualBootPatcherAndroid-9.2.0.r54.g8b79a2b
And
DualBootPatcherAndroid-9.2.0.r8.g4da14ed
These are recommended on this thread
Is there any other supported version for our model
Click to expand...
Click to collapse
I had tried r201.
Click to expand...
Click to collapse

[ROM][7.1.2] LineageOS for microG [6/17/18]

Code:
I am not responsible for anything that happens as a result of you using the ROM. Sure, i'm willing to help with bugs, but if you get fired because the Alarm app crashed, gremlins crawl out of your arse, thermonuclear war starts, or if your progress in Clash of Clans gets reset, i'm not the one to blame.
Features
Code:
microG and F-Droid pre-installed
Anything else LineageOS can do
Is not certified cancer-free in California
Stuff you need to actually use this
- Unlocked Bootloader (duh). Seriously, I will ignore you if you mention that you tried to boot this with Safestrap.
- Update TWRP to Android-7.1 builds located here. Please make sure to use the recovery image which is appropriate for your device (Thor or Apollo)
How do I actually install this?
- Backup existing ROM if you want. Or don't. I don't really care, truth be told.
- Wipe /data partition. You can keep media storage if you want, but I prefer to format it to make it SQUEAKY CLEAN
- Flash the .zip
- Do not flash OpenGapps. Or any Gapps. That defeats the purpose of microG.
- Flash any other crap you want. This'll probably Magisk.
- Reboot.
Downloads
AndroidFileHost: Thor, Apollo
Extra junk you might want
Magisk
Yalp Store (play store wrapper)
Flashable Standalone Google Play Store
Sources
I didn't make any of this. I just compiled and signed it. People smarter than me, like hashcode and ggow did, made this work on the HDX. Lots of other people made LineageOS and microG. Thanks to you all.
Phoenix Kernel
HDX-Common device tree
Thor device tree
Apollo device tree
Docker instance that I use to build this
How do I tell the NSA didn't tamper with my download?!
Luckily, I signed the builds with my own key!
Code:
$ keytool -list -printcert -jarfile lineage-14.1-20180613-UNOFFICIAL-thor.zip
Signature:
Owner: [email protected], CN=steamport, OU=steamport, O=steamport, C=US
Issuer: [email protected], CN=steamport, OU=steamport, O=steamport, C=US
Serial number: b1b3cdcf593b5030
Valid from: Tue Jun 12 20:49:48 EDT 2018 until: Sat Oct 28 20:49:48 EDT 2045
Certificate fingerprints:
MD5: 13:E0:38:54:47:CC:FA:B8:24:50:16:6D:41:90:C7:4F
SHA1: 5F:AD:C9:4B:43:D3:1E:C3:6B:5F:86:DE:6A:F6:C7:F8:72:CB:B7:04
SHA256: BB:A1:BB:0F:7B:E1:62:2D:87:27:FE:EC:C5:CA:C6:B7:E3:EA:1A:CB:32:33:7E:F4:2C:D6:BC:BC:6E:46:27:CC
Signature algorithm name: SHA256withRSA
Subject Public Key Algorithm: 2048-bit RSA key
Version: 3
XDA:DevDB Information
LineageOS for microG, ROM for the Amazon Kindle Fire HDX 7" & 8.9"
Contributors
steamport
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader, TWRP
Based On: LineageOS
Version Information
Status: Testing
Created 2018-06-13
Last Updated 2018-06-22

so confuse about microg. there are some games we must live with google play or the games can't run.
but micro g are great for user who not play games rely on google play.

locolyric said:
so confuse about microg. there are some games we must live with google play or the games can't run.
but micro g are great for user who not play games rely on google play.
Click to expand...
Click to collapse
What is there to be confused about? Yes, Google Play Games doesn't work with microG yet. Just don't play with games that mine your data. Problem solved. Or just try to lubricate it with cat piss. I don't care.

Stupid Question: does this support LTE?

CCF_100 said:
Stupid Question: does this support LTE?
Click to expand...
Click to collapse
I don't think any Nougat ROM for thor or apollo supports LTE. Sadly, no.

CCF_100 said:
Stupid Question: does this support LTE?
Click to expand...
Click to collapse
steamport said:
I don't think any Nougat ROM for thor or apollo supports LTE. Sadly, no.
Click to expand...
Click to collapse
Correct - only KitKat based custom ROMs support LTE (data only). FireOS 4.5.x is the best choice for voice and mobile data support.

New zips are out. I just updated microG's GMSCore to one I built myself based on master and a fix PR. Also pulled from latest Lineage 14.1 sources.

Bluetooth issue ? I still use kitkat because i can use bluetoooth. But so boring ..

NeverSmile said:
Bluetooth issue ? I still use kitkat because i can use bluetoooth. But so boring ..
Click to expand...
Click to collapse
Likely won't be any different with this ROM as core issue resides at the kernel level. Inconsistent connection behavior leads to erroneous claims based on individual experiences but really not ROM related other than the binary KitKat (Android 4.4.x) or above checkpoint.

Firstly this is an amazing ROM! Well done to you and the team! However, the recent Apollo release is broken. Not sure about the Thor version, i would check but the device I bricked because I was messing around... Anyway it boots successfully but the screen is blank and is still turned on, no boot animation other than the generic grey kindle fire. I can still tap the screen and hear android feedback noises after waiting awhile so it works! Just I cant see anything :laugh: The previous release worked fine, no problems! Maybe you could keep the recent previous releases available for download for backups in case? Thanks again
Edit: Obviously I have the bootloader unlocked etc. Using latest TWRP if that helps at all.

kfhdxuser said:
Firstly this is an amazing ROM! Well done to you and the team! However, the recent Apollo release is broken. Not sure about the Thor version, i would check but the device I bricked because I was messing around... Anyway it boots successfully but the screen is blank and is still turned on, no boot animation other than the generic grey kindle fire. I can still tap the screen and hear android feedback noises after waiting awhile so it works! Just I cant see anything :laugh: The previous release worked fine, no problems! Maybe you could keep the recent previous releases available for download for backups in case? Thanks again
Edit: Obviously I have the bootloader unlocked etc. Using latest TWRP if that helps at all.
Click to expand...
Click to collapse
I don't have an apollo, so can you do some debugging for me? ADB into it. It'll ask for authorization on the screen, just guess where the OK button is til it works. Anyways, when you do get adb auth, run this:
Code:
adb shell
logcat > log.txt
exit
adb pull log.txt
, then put the log.txt on pastebin and give me the link

Been trying for about an hour now all i'm getting is feedback noises, is the confirmation dialog being prevented due to the setup process if there is one? Cant seem to get out of it and ADB keeps saying the device is unauthorized. I'll keep trying on the OS and once i get anything i'll update you as soon as i can.

kfhdxuser said:
Been trying for about an hour now all i'm getting is feedback noises, is the confirmation dialog being prevented due to the setup process if there is one? Cant seem to get out of it and ADB keeps saying the device is unauthorized. I'll keep trying on the OS and once i get anything i'll update you as soon as i can.
Click to expand...
Click to collapse
I've seen the dialog pop up as soon as it finishes booting

Done!
steamport said:
I've seen the dialog pop up as soon as it finishes booting
Click to expand...
Click to collapse
Okay i've got a log file after a few unsuccessful attempts, i'm not sure why the code you gave me did not work but I tried myself using "adb shell adb logcat -d > Lineage14.1.txt" and that seemed to do the trick. (Hopefully this is what you were after).
I tried to upload this to pastebin but it refused so i've uploaded it to an alternative website here: https://paste.ee/p/kL4Ur

kfhdxuser said:
Okay i've got a log file after a few unsuccessful attempts, i'm not sure why the code you gave me did not work but I tried myself using "adb shell adb logcat -d > Lineage14.1.txt" and that seemed to do the trick. (Hopefully this is what you were after).
I tried to upload this to pastebin but it refused so i've uploaded it to an alternative website here: https://paste.ee/p/kL4Ur
Click to expand...
Click to collapse
Thanks.... this is a weird log. It mentions turning the screen on several times? Can you try fully wiping system and reinstalling?

steamport said:
Thanks.... this is a weird log. It mentions turning the screen on several times? Can you try fully wiping system and reinstalling?
Click to expand...
Click to collapse
Yep i'll do that, was it the method that I used to extract the log file that could be the culprit? I should probably mention that you can see the screen when it turns off and on its just a different shade of black indicating that the screen works but it just won't display anything if that makes sense. I'll do a complete wipe and start again to see if its any different this time around.
Edit: Here is the new log: https://paste.ee/p/VK4oS
^^^
I've noticed it is considerably smaller this time around so hopefully this a good sign haha.
It is weird how the previous release worked and this one doesn't, i'd assume it's an application interfering from the latest build but if it works on Thor then it mustn't be right? Maybe something was accidentally changed for the Apollo release somewhere. Sorry if my ramblings aren't useful

Thanks @steamport! What is the security patch level on this build?

NextDroid said:
Thanks @steamport! What is the security patch level on this build?
Click to expand...
Click to collapse
Whatever the latest for 14.1 was as of 6/7/18?

steamport said:
Whatever the latest for 14.1 was as of 6/7/18?
Click to expand...
Click to collapse
Well, that depends, as the last AEX build, for example, was still on May 5.
Tapatalk を使用して私の LG-RS988 から送信

steamport said:
I don't have an apollo, so can you do some debugging for me? ADB into it. It'll ask for authorization on the screen, just guess where the OK button is til it works. Anyways, when you do get adb auth, run this:
Code:
adb shell
logcat > log.txt
exit
adb pull log.txt
, then put the log.txt on pastebin and give me the link
Click to expand...
Click to collapse
I've got the same problem. Loads but no screen and unable to find the "ok" to authorize the device. There must be a better way.
I will revert back to previous version until this is fixed.

[AIO] Prepare your device (and your knowledge) for any GSI

Preliminary operations/infos
First of all: what's Treble?
Find it out here.
How do I obtain my bootloader unlock code?
GO HERE, FAST!
Huawei officially ceased the unlocking service.
How do I get Treble on my device?
At the moment of this write down, EMUI it's still in private BETA.
The only chance to obtain it it's to follow this guide CAREFULLY.
What if I want to revert to EMUI 8/5?
Follow the steps described in the guide to get treble on your device using EMUI 8 files if you want to revert to EMUI 8, or EMUI 5 if you wish to revert to it.
The road it's long...
So, you're sitting there, not understanding why there are so much ROMs in this section and why you shouldn't use the ones appearing in Treble-Enabled Device Development since you worked so hard to get Treble on it.
Let's try to answer a universal question.
What's the difference from the "standard" GSIs and the ROMs in this section?
Well, the ROMs here were made keeping an eye on the "optimization per-platform" concept, basically tracking down some proprietary stuff inheriting them under /system .​
**WHAT FOLLOWS ARE PERSONAL OPINIONS**
I honestly think, that we should cut off this approach.
Inheriting stuff under /system has no more sense.
Am I saying that what I did till now had no sense?
Yes.
The whole Treble concept relies on moving away from system, any vendor related stuff.
So why in the hell should we inherit proprietary stuff in our system partition again?
When we have other ways to don't mess with it?
The only stuff that still "deserves" to have something to do with /system it's the Huawei Camera.
Everything else, belongs to /vendor.
Furthermore, our goal, as developers and users, should be to track down specific-platform bugs and report them.
Co-operation is the sake of open-source and the key to success in a wonderful GSI experience for everyone.​

Is my device ready to use a "standard" GSI?
Pretty much.
Huawei doesn't ship any overlay under /vendor in our PRA, because it's inherited in EMUI under /system.
But, you can follow this guide, to include the needed overlay to be fully GSI-ready.
Also, you need this thread too to fix offline charging on your Huawei device.​
Known Bugs on GSI and "specific-GSI"
NFC has been an annoying issue all along the development process on some Huawei devices.
But this flashable zip, seems to solve the issue on our PRA.
Indeed it needs more testing.​
Available tools/software for your PRA
ADB and Fastboot
TWRP
MindTheGapps
Huawei Camera Magisk
OEMInfo (TWRP backup)
HuRU
Stock Ramdisk (ramdisk partition)
Stock Recovery (recovery_ramdisk partition)​​
Specific-GSI available
Lineage OS https://forum.xda-developers.com/p8...t/rom-lineage-os-huawei-p8-lite-2017-t3787193
CrDroidhttps://forum.xda-developers.com/p8.../rom-crdroid-4-2-huawei-p8-lite-2017-t3785615
AospExtendedhttps://forum.xda-developers.com/p8.../rom-aospextended-5-4-huawei-p8-lite-t3778938
AOSPhttps://forum.xda-developers.com/p8...ent/rom-aosp-r23-huawei-p8-lite-2017-t3779115
Resurrection Remix 6https://forum.xda-developers.com/p8lite/p8-lite-2017-development/rom-rros-pra-t3774444
SlimRom 8
AICP​
Specific GSIs are now discontinued.
Go to the Treble Enabled Development sub to get some ROMs to flash!
NOTE:
This ROMs will be discontinued in a couple of weeks, since the installation of the overlay (previously highlighted in the paragraph "Is my device ready to use a "standard" GSI?") will give access to a full fledged GSI experience without the need of specific GSIs.
Custom kernels
Labyrinth​

Disable encryption to use Adoptable Storage (or just because you can)
open /vendor/etc/fstab.hi6250
make a backup just in case
find "/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inlinedata,inlinexattr wait,check,fileencryption=aes-256-xts:aes-256-cts"
remove ",fileencryption=aes-256-xts:aes-256-cts"
factory reset via stock recovery
If this isn't clear enough, please, check this contribution.
Playstore download pending fix
Access https://play.google.com/apps/testing/com.google.android.gms/join
Apply for the beta
Update Google Play Services to the beta
Profit
Magisk keeps crashing?
Turn off its "Check for update feature" and praise for the arrival of a new Magisk version.
From 16.6 version, Magisk it's fully working.
Please, refer to this thread for a correct installation.
How to report bugs
Boot problems:
Please do dump /splash2 partition and sys/fs/pstore content via adb pull in my TWRP.
adb logcat > file.txt
Quirks on booted system:
Please take a full bugreport when the bugs happens via Developer Options
or​
adb logcat > file.txt
send file.txt to the developer

Hey you!
If you're reading this message I want you to help this community.
Share your thoughts about this posts or post your un-answered questions below.
The more we share, the best experience we'll get.
Also, please respect my work.
If you do integrate some of this infos in your thread/website or whatever, add me in the credits.
Furthermore, feel free to join us at @GSI_HI6250 on Telegram, we're funny people, I swear.
Is this non-clear somehow?
Or you just need help?
Fill the help form below.
Device Variant:
Device Firmware:
Is your device rebranded?:
How frequently this issue happens?
Is this happening now?
Describe the issue:
Describe steps to reproduce the issue:
Attach logcats/full bugreports as described on the paragraph "How to report bugs"​
Or simply join the telegram group.
Peace.

Dil3mm4 said:
Kaioken reserved
Click to expand...
Click to collapse
Super Saiyan reserved
Lol

Dil3mm4 said:
Disable encryption to use Adoptable Storage (or just because you can)
open /vendor/etc/fstab.hi6250
make a backup just in case
find "/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inlinedata,inlinexattr wait,check,fileencryption=aes-256-xts:aes-256-cts"
remove ",fileencryption=aes-256-xts:aes-256-cts"
factory reset via stock recovery
Playstore download pending fix
Access https://play.google.com/apps/testing/com.google.android.gms/join
Apply for the beta
Update Google Play Services to the beta
Profit
Magisk keeps crashing?
Turn off its "Check for update feature" and praise for the arrival of a new Magisk version.
How to report bugs
Boot problems:
Please do dump /splash2 partition and sys/fs/pstore content via adb pull in my TWRP.
Quirks on booted system:
Please take a full bugreport when the bugs happens via Developer Options
or​
adb logcat > file.txt
send file.txt to the developer
Click to expand...
Click to collapse
THAT WORKED. FINALLY 8.1 WITH BOOTLEGGERS GSI, 128GB micro SDXC as INTERNAL. I AM HAPPY
for beginners:
boot after working rom in twrp
go in advanced
go to file manager
go to /vendor/etc/
open file "fstab.hi6250" (after copying with and having a recovery of it, open with notepad++ or something else)
there should be a line with: "/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inlinedata,inlinexattr wait,check,fileencryption=aes-256-xts:aes-256-cts"
erase the part: ",fileencryption=aes-256-xts:aes-256-cts"
save
erase the original fstab.hi6250 file in vendor/etc
and put the new fstab.hi6250 file in
reboot in bootloader
flash stockrecovery.img
reboot recovery
factory reset in stock recovery
reboot
DONE.
now you can see the SD card as internal and use for apps.

Need your help
Hey OP,
Thanks for all your work. Really a big fan.
There is a problem I've noticed on most of the treble roms. After using apps for a while, they begin to FC.
Love your roms and would like to continue using them

Mister746 said:
Hey OP,
Thanks for all your work. Really a big fan.
There is a problem I've noticed on most of the treble roms. After using apps for a while, they begin to FC.
Love your roms and would like to continue using them
Click to expand...
Click to collapse
Updated last post, please submit the infos needed via that form.
Thanks.

Hi, i am experiencing a weird bug on every GSI, specifically, snapchat video recording is fine and smooth, but after tapping on the "send" button it says "failed to add" and doesnt even give a chance to resend the same snap. It happens on all treble roms i've teted so far (i tested every specific GSI for PRA, and some openkirin and otger ones). @dill3m4 do you have any idea how to fix it? I hope there is a way to do a flashable zip or something like the NFC fix. Once i get back home (2-3 days) i will post some logs, in the meantime, can someone please confirm if the issue persists, and gather logs? ?

can i use this method in stock firmware(rooted) because i cant see any fstab file in vendor/etc/

jedtan025 said:
can i use this method in stock firmware(rooted) because i cant see any fstab file in vendor/etc/
Click to expand...
Click to collapse
Just making sure but you are on emui8 right? Also are you checking with a file manager in Android or are you searching in twrp?

neondragon1909 said:
Just making sure but you are on emui8 right? Also are you checking with a file manager in Android or are you searching in twrp?
Click to expand...
Click to collapse
im searching in twrp bro. bro question. im using pra lx2 oreo firmware. and im wanna go back to nougat. it is possible? i got the firmware now but dont know how to flash nougat. dload failed. and i cant use hurupdarer bcos nougat firmware only has 2 zip file

jedtan025 said:
im searching in twrp bro. bro question. im using pra lx2 oreo firmware. and im wanna go back to nougat. it is possible? i got the firmware now but dont know how to flash nougat. dload failed. and i cant use hurupdarer bcos nougat firmware only has 2 zip file
Click to expand...
Click to collapse
I couldn't find the file using TWRP either. Had to use root explorer to find and edit the file. As for hurupdater, I'm not sure if it's the same for your region, but for pra-la1 there were 3 files.
And as for the the 2 files, I successfully flashed using the updater with only the update.zip so try updating anyway. If that doesn't work, use the eRecovery

Update:
Added Magisk news;
Added stock PRA ramdisk

UPDATE:
Added Offline Charging Fix in post #2
Added references to Treble Enabled device development;
New Huawei Magisk Camera;

Hello,
I'm having problems finding the download links in the guide to obtain Treble, I've searched here and clicked on the link to the guide but there i can't find it eather.

cyprian99 said:
Hello,
I'm having problems finding the download links in the guide to obtain Treble, I've searched here and clicked on the link to the guide but there i can't find it eather.
Click to expand...
Click to collapse
Obtain what?
Treble roms?

Yay! Emui 8.0 has arrived on my c432 pra-lx1 (b360) . Everything is perfect.

The guide to get treble is unclear, how can the very first step be to download update.zip? I did and now i have a trojan, thanks a lot

How to unlock bootloader? Now the Huawei site is unavailable
Wysłane z mojego PRA-LX1 przy użyciu Tapatalka

Deep TEST fot OPPO RENO ACE(unlock bootloader)

OPPO's official website provides users with an official way to unlock bootloader.
coloros link:
https://bbs.coloros.net/graphic?id=1498611
you need to install the deeptest.apk to submit unlock request.
The application must meet all the following conditions:
1. The time to market must be more than 3 months;
2. No application record within 60 days;
3. The last consecutive login time of the OPPO account on this machine exceeds 60 days;
4. The number of in-depth test users has not reached the quota limit;
5. Non-government enterprises and operators customize mobile phones;
6. Support mobile phones listed in mainland China.
Unfortunately, there are currently no available quota.But if you want , you have to register an oppo account,and login time should more than 60 days.

So does this mean we can install custom rooms?

So... Hey guys,
I just wanted to let everyone know that I was actually able to flash the GSI from the link below on my OPPO Reno Ace:
https://forum.xda-developers.com/project-treble/trebleenabled-device-development/aosp-10-0-quack-phh-treble-t3992559
I am super new to all this, but I decided to take the risk anyways because I really wanted to get away from ColorOS. Luckily it worked out to the point that the phone seems functional so far (just flashed it as of writing this).
Disclaimer: Do this at your own risk! I am not responsible for what happens to your phone for following what I did. Please think twice before trying! Also remember to back-up your phone first!
Before I continue on how I got it to work, I got the Reno Ace Gundam edition. Not sure if that makes a difference but I thought this should be mentioned. Also since I couldn't find a version of TWRP for the Reno Ace; I followed the instructions on how to flash without it.
Here are all the main links I used:
Walkthrough for Deep Test app: https://forum.xda-developers.com/find-X/how-to/guide-how-to-apply-deep-testing-pafm00-t3888013
GSI: https://forum.xda-developers.com/project-treble/trebleenabled-device-development/aosp-10-0-quack-phh-treble-t3992559
Flashing Instructions and "vbmeta.img": https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
Extra Links in case of weird trouble. Hopefully you won't need it:
Google Usb Driver: https://developer.android.com/studio/run/oem-usb#InstallingDriver
How to manually install Google USB Driver: https://visualgdb.com/KB/usbdebug-manual/
Useful Key Word: Kedacom USB Device
*** Backup your phone before going forward.
Getting the Deep Testing app:
Now first, you do need to sign-up for an OPPO account. The link from the OP will take you to their site and you can sign-up from there.
- You will be required to login to your OPPO account in order to use the app.
- The file you download is named "Reno Ace深度测试.apk".
- Add ".apk" to the end of the filename if it's not already there. DO NOT rename the file.
- Once logged into your OPPO account on your phone, you stay logged in so you don't need to worry about actively logging in everyday.
- Next, follow the instructions on how to use the app from the Deep Test thread.
- Keep trying until your submission gets accepted, then the hardest part begins: you...wait...
- Once approved, it took ~2 days for me to be able unlock.
Make sure you have ADB ready on your computer:
- There are plenty of guides on it, so I'll just leave a link here; honestly I forgot the specifics already: https://www.xda-developers.com/install-adb-windows-macos-linux/
Steps:
- Prepare your GSI: You can look for other GSI(s), but from my research it seems safest to get it from here first; before trying others: GSI thread
- This link explains what GSI are and how to choose which one to get.
- *Make sure to extract the ".img" file from the ".img.xz" zip file.*
- Download "vbmeta.img" from "Troubleshooting Tips" of the "Flash GSI without TWRP" section of the How to Flash GSI Guide.
-After you've extracted the ADB folder, keep the files (.img files) you intend to flash within the "platform-tools" folder.
*Noob tip lol: Clicking on the folder address and typing "cmd" is the quick way to open command prompt within the directory.*
- *** There are some unique steps for the Reno Ace, if not all OPPO phones, due to the Deep Testing app. ***
- After you get your approval, note that if you press the "Start Deep Testing" text you will be immediately put into fastboot mode. SO DO NOT PRESS IT NOW.
- Make sure you have OEM Unlock and USB Debugging enabled within Developer Options. Then connect your phone to your PC and set it to transfer files.
- On computer, open command prompt within the "platform- tools" folder. Enter the command "adb devices", when you see your device ID and "device" next to it, this means the phone has been connected. (If a prompt on your phone pop-ups, tap the "Always allow this computer to USB Debug" and "Allow". This is just what I did, not sure if it's necessary).
- Now go into the Deep Testing app on your phone, tap on "Queue status" and then "Start Deep Testing".
- You should see the images from this Oppo Find X tutorial, on your phone. Landing on the screen with the big green "Start" on top.
- Once you're here, enter "fastboot flashing unlock" into ADB and you'll move on to the next screen where you select "Unlock the Bootloader".
- After confirming, your phone will factory reset itself, and reboot into ColorOS again.
- Check to make sure your phone is connected to adb.
- From here on you follow "Flash GSI without TWRP" part of the How to Flash GSI Guide starting at step 2. If you have your ".img" files in the "platform-tools" folder then you can skip step 3.
- Before step 5 you need to flash the vbmeta: fastboot flash vbmeta name_of_vbmeta.img
Then flash the GSI ".img" file with fastboot -w flash system name_of_system.img.
(The comments there mentions that the "-u" is incorrect and should be "-w", which worked for me.)
* Important: without flashing "vbmeta.img" you'll be stuck in a boot loop because the phone prevents you from booting into the GSI. If this does happen, hold down Volume Down and Power until the phone vibrates to boot back into "fastboot mode". Enter "fastboot device" in ADB to confirm the phone is connected, and start over from step 4 in the How to Flash GSI Guide. *
- Once you finish step 6 your phone should boot into the GSI.
Hopefully this proves useful. I'm no expert, I simply found my way around things.
I honestly have no idea where to go from here, Magisk? LineageOS? If anyone can give me some pointers, that would be very much appreciated.
Things that are not working for me:
- Can't setup In-screen Fingerprint sensor

I got a twrp that works just finished rooting with help of the vbmeta above

Darktron13 said:
I got a twrp that works just finished rooting with help of the vbmeta above
Click to expand...
Click to collapse
Would you mind giving a link to the twrp you found? I was searching around for one as well, but I couldn't find anything I felt comfortable with.
Also did you also flash a gsi? If you did, I was wondering if your headphone jack is working. Mine doesn't work anymore; the phone seems to recognize it, but no headphone icon shows up and sound plays through the speakers only.

falsewind said:
Would you mind giving a link to the twrp you found? I was searching around for one as well, but I couldn't find anything I felt comfortable with.
Also did you also flash a gsi? If you did, I was wondering if your headphone jack is working. Mine doesn't work anymore; the phone seems to recognize it, but no headphone icon shows up and sound plays through the speakers only.
Click to expand...
Click to collapse
Haven't install any gsi just have ColorOS 7.1 C.27 I cant remember where I got that twrp from all I know is a Chinese twrp think I found it on some baidu drive I was just waiting on approval from the in depth testing app.

Darktron13 said:
Haven't install any gsi just have ColorOS 7.1 C.27 I cant remember where I got that twrp from all I know is a Chinese twrp think I found it on some baidu drive I was just waiting on approval from the in depth testing app.
Click to expand...
Click to collapse
Thanks for the quick reply. I think I know where that's from. I believe that it's from here:
http://www.romleyuan.com/lec/read?id=348
Let me know if it looks familiar. Great to know that it works!

falsewind said:
Thanks for the quick reply. I think I know where that's from. I believe that it's from here:
http://www.romleyuan.com/lec/read?id=348
Let me know if it looks familiar. Great to know that it works!
Click to expand...
Click to collapse
Yes looks familiar it should be that one the twrp itself has Chinese and English languages.
Formatting and wipe is working otg also haven't really tested alot also you can flash ozip stock rom with it if you plan on rooting the boot gets corrupted but with the vbmeta bypasses it.
if you plan on installing V4A don't do the magisk module will bootloop have to look for the rootless V4A. (also need AML and the sound is great)
also don't change to f2fs i did it and the phone make weird noises went back to ext4.

Darktron13 said:
Yes looks familiar it should be that one the twrp itself has Chinese and English languages.
Formatting and wipe is working otg also haven't really tested alot also you can flash ozip stock rom with it if you plan on rooting the boot gets corrupted but with the vbmeta bypasses it.
if you plan on installing V4A don't do the magisk module will bootloop have to look for the rootless V4A. (also need AML and the sound is great)
also don't change to f2fs i did it and the phone make weird noises went back to ext4.
Click to expand...
Click to collapse
Awesome! Thanks for the info, it will come in handy later on. Still just learning and getting familiar with all this.

A follow up after a couple of days of using phhusson's gsi.
Overall the phone is functioning very well. Generally smoother than on ColorOS.
Things to note:
- Battery life is good, same if not better than on ColorOS.
- Fast charge works. Full charge in around under 30 mins.
- Wi-fi works and Data works.
- Phone and Text work.
- Camera works.
- Headphone jack won't work until you go into the treble-settings (Phh Treble Settings) -> Qualcomm features -> and turn on "Use alternate audio policy"; then restart your phone. Then it will work again, although no headphone icons will appear. I don't use Headsets, so I couldn't test if that works as well.
- The phone will be rooted by default, so certain apps can't be downloaded, or used. (Root can be removed, but it doesn't seem like a good idea.) There are ways around this, but I didn't dive very deep into it.
Problems to note:
- In-screen fingerprint sensor can't be used.
- No auto-adjusting brightness.
- Brightness is a lot brighter than in ColorOS. Even lowest brightness is bright.
- Auto-Rotate is very sensitive and won't stay landscape when phone is flat on a table.
- Certain apps may not be full screen if you use the new gesture navigation. (Shadowverse)
- I didn't test Bluetooth or NFC. I don't use them much, or at all, so I'll follow up on that when the time comes and no one else has mentioned anything on them yet.
That should be all for now. Honestly very happy with the move. Hope this helps.
**Just an extra reminder that this is my experience with this specific gsi. **

Is this still available? I can't download the APK from Oppo, I logged onto my 'heytap' account but the download link just brings me to my account information.

twgib said:
Is this still available? I can't download the APK from Oppo, I logged onto my 'heytap' account but the download link just brings me to my account information.
Click to expand...
Click to collapse
I've reply back on the other post about Oppo Reno which model you have Ive posted both apks

Darktron13 said:
I've reply back on the other post about Oppo Reno which model you have Ive posted both apks
Click to expand...
Click to collapse
Thank you so much! You're too kind!

Nice to see some progress on this phone it has so much power and potential!

Help
Darktron13 said:
Haven't install any gsi just have ColorOS 7.1 C.27 I cant remember where I got that twrp from all I know is a Chinese twrp think I found it on some baidu drive I was just waiting on approval from the in depth testing app.
Click to expand...
Click to collapse
Please can you share the twrp, I have the device but it is really hard for me to download it from baidu, if you were already kind to share it, you would help me a lot to test the phone, thanks in advance. Sorry for my English, it's not very good.

is there any info about what stock rom you're using? i was trying to install Phh's AOSP gsi thourh fastboot, the system-quack-arm64-aonly-vanilla.img , and only to get stucked at the OPPO logo, i'm using C26 curently

刘欲杰lol said:
is there any info about what stock rom you're using? i was trying to install Phh's AOSP gsi thourh fastboot, the system-quack-arm64-aonly-vanilla.img , and only to get stucked at the OPPO logo, i'm using C26 curently
Click to expand...
Click to collapse
ok, i figured it out. Ace is a System-as-root device,so i need to use a/b img files

I wanna root my phone

OPPO Reno Ace Twrp.7z
1 file sent via WeTransfer, the simplest way to send your files around the world
we.tl
[这是color7 可以用的twrp 如果你们可以进去下载的话

xdsfh said:
OPPO's official website provides users with an official way to unlock bootloader.
coloros link:
ColorOS 12_话题_OPPO手机官方社区
ColorOS 12延续“无边界”设计理念，为你带来更懂你的智慧操作系统！
bbs.coloros.net
you need to install the deeptest.apk to submit unlock request.
The application must meet all the following conditions:
1. The time to market must be more than 3 months;
2. No application record within 60 days;
3. The last consecutive login time of the OPPO account on this machine exceeds 60 days;
4. The number of in-depth test users has not reached the quota limit;
5. Non-government enterprises and operators customize mobile phones;
6. Support mobile phones listed in mainland China.
Unfortunately, there are currently no available quota.But if you want , you have to register an oppo account,and login time should more than 60 days.
Click to expand...
Click to collapse
URL not found

Question TWRP?

I understand that the TWRP team is apparently still working on an official release for Android 13, but is there even an unofficial build available for the P7Pro? If not, is there a recovery alternative? I really want to be able to do a full system (all partitions) backup of my device. Thanks!

You can create dumps of your partitions using ADB shell in system; TWRP is not required to do this.

Though it wouldn't necessarily be any good for doing full partition backups, I'm currently running the recovery from the StagOS ROM in combination with the stock Pixel ROM. I like it because it allows flashing recovery zips without having to say "Yes" every time due to signature stuff.

A very similar thread with the same topic has been discussed a few days ago - you can check here

Anyone can compile TWRP - it's opensource. Pixel 6+ owners are unlikely to get an official build from TWRP since it requires a volunteer to maintain the repo, deal with bug reports, etc.
It's recommended to simply compile the image on an individual basis (you really don't want to rely on a third-party supplied image when you have no way of knowing whether it's safe or not). Compiling isn't a difficult process, but does require an hour or two of reading TWRP's and Google's applicable developer pages, along with ~30 - 60 minutes of set up time on a PC/laptop (I prefer to compile within an Ubuntu VM, but I believe it can also be done in Windows' WSL).

robroy90 said:
I understand that the TWRP team is apparently still working on an official release for Android 13, but is there even an unofficial build available for the P7Pro? If not, is there a recovery alternative? I really want to be able to do a full system (all partitions) backup of my device. Thanks!
Click to expand...
Click to collapse
They still haven't finished official support for Android 12. Since recovery resources on A12+ are located in vendor_boot, bigbiff is trying to figure out a decent way for TWRP to live there, at least as far as the Pixel 5 is concerned. Not sure what other obstacles may be present on the Pixel 6 series and above.

nooted1 said:
Though it wouldn't necessarily be any good for doing full partition backups, I'm currently running the recovery from the StagOS ROM in combination with the stock Pixel ROM. I like it because it allows flashing recovery zips without having to say "Yes" every time due to signature stuff.
Click to expand...
Click to collapse
Hey thanks for this! How did you flash just the recovery partiton on the Pixel? I am an old hand with Odin on the Samsung devices, but Google official devices are still new to me. Will the StagOS recovery recognize an external USB-C flash drive for storage?

s3axel said:
A very similar thread with the same topic has been discussed a few days ago - you can check here
Click to expand...
Click to collapse
Thank you, I went over there and read everything. Much appreciated!