Android Pie Treble Project DP3 DP4 DP5 PR1 Guide - Xiaomi Mi 5 Guides, News, & Discussion

Android "P" is the upcoming ninth major version of the Android operating system. It was first announced by Google on March 7, 2018, and the first developer preview was released on the same day. The second developer preview is expected to be released at the next Google I/O developer conference.
Requirements :
Qcom fully treblized device with 8.1 vendor
Global Bugs :
VoLTE
Device specific Bugs :
Mi5 = Reboot Loop into TWRP (Fixed by restore files)
ANDROID P DP3
installation :
- Flash [JDCTeam][TREBLE][v4][Gemini] The Full Treble support project HERE
- Unzip and Flash P-DP3-sGSI.img HERE
- Flash POST-sGSI_1_v0.9.zip HERE
- Flash POST-sGSI_2_v0.12.zip HERE
- Flash POST-sGSI_3.zip HERE
- Flash P-lag-fix.zip file below thread
- Flash incall2.zip HERE
- Reboot
When flashing POST-sGSI untill incall shown error in twrp, Go back to TWRP Home > Mount > check vendor and system
After bootup, you need to install Google Play services 12.8.72 (100400-202717283) HERE
If you are facing with bug Reboot Loop(always reboot into TWRP) you need to restore this backup file from me.
Unzip and put that folder at TWRP/Backups
Goto TWRP > Restore > Check system and vendor only > Reboot.
SECOND METHOD : Restore before 1st boot.
- Flash [JDCTeam][TREBLE][v4][Gemini] The Full Treble support project HERE
- Unzip and Flash P-DP3-sGSI.img HERE
- Flash POST-sGSI_1_v0.9.zip HERE
- Flash POST-sGSI_2_v0.12.zip HERE
- Flash POST-sGSI_3.zip HERE
- Restore this backup file
(Make sure choose System and Vendor only, Dont choose boot, system image, or vendor image and the size is 2101MB).
- Flash P-lag-fix.zip file below thread
- Flash incall2.zip HERE
- Reboot (If stuck at google logo about 3-5mins, try to force shutdown your phone, and turn it on again... it should be work.)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
ANDROID P DP4
CLEAN FLASH IS HIGHLY RECOMMEND
- Flash [JDCTeam][TREBLE][v4][Gemini] The Full Treble support project HERE
- Unzip and Flash P-DP4-sGSI-Aonly.zip HERE
- Flash POST-sGSI_1_v0.11.zip HERE
- Flash POST-sGSI_2_v0.14.zip HERE
- Flash POST-sGSI_3.zip HERE
- Restore this backup file
(Make sure choose System and Vendor only, Dont choose boot, system image, or vendor image and the size is 2180MB).
- Incall.zip already included. Dont need to flash it.
- Flash p-lag-fix DP4.zip file below thread
- Reboot
If your device become reboot loop into TWRP, like in DP3
- Restore this backup file
(Make sure choose System and Vendor only, Dont choose boot, system image, or vendor image and the size is 2180MB).
Click to expand...
Click to collapse
ANDROID P DP5
CLEAN FLASH IS HIGHLY RECOMMEND
- Flash [JDCTeam][TREBLE][v4][Gemini] The Full Treble support project HERE
- Unzip and Flash P-DP5-sGSI-Aonly.zip HERE
- Flash POST-sGSI_1_v0.13.zip HERE
- Flash POST-sGSI_2_v0.16.zip HERE
- Flash POST-sGSI_3 v0.2.zip HERE
- Flash lag-fix-DP5 attached below.
- Mount Vendor on TWRP
- Go to TWRP Advanced->Terminal, type the following and press enter
echo persist.sys.disable_rescue=true >> /vendor/build.prop
- Reboot to System
IF YOU STILL REBOOT INTO RECOVERY AFTER 1ST BOOT.
after flash POST-sGSI_3 v0.2.zip
- Restore this backup file
(Make sure choose System and Vendor only, Dont choose boot, system image, or vendor image and the size is 2180MB).
- Incall.zip already included. Dont need to flash it.
- Flash lag-fix-DP5 attached below.
- Reboot
Click to expand...
Click to collapse
Android P Public Release 1 (PR1)
1. Flash JDCTeam Full Treble Support Project
2. UNZIP and flash Pie A-only as System Image.
3. Mount System and Vendor on TWRP
4. Flash POST-sGSI_1_v0.14.zip
5. Flash POST-sGSI_2_v0.17.zip
6. Flash POST-sGSI_3_v0.2.zip
7. Mount System and Vendor on TWRP
8. Flash p-lag-fix.zip (Attached Below)
9. Mount Vendor on TWRP
10. Go to TWRP Advanced - Terminal, type the following and press enter
echo persist.sys.disable_rescue=true >> /vendor/build.prop
11. Reboot to System
12. Install Google Play Services Apk, reboot and proceed normally.
Click to expand...
Click to collapse
REBOOT LOOP THIRD METHOD by mlira1 and Maixf
1. Flash JDCTeam Full Treble Support Project
2. Flashi DP3/DP4 System Image
3. Mount System and Vendor on TWRP
4. Flash POST-sGSI_1
5. Flash POST-sGSI_2
6. Flash POST-sGSI_3 (skip if going to flash custom kernel)
7. (only if going to flash custom kernel) Flash fix.zip (attached below)
8. (optional) Flash custom kernel
9. (optional) Flash Magisk
10. Mount System and Vendor on TWRP
11. (only if flashed custom kernel) Flash POST-sGSI_3
12. Flash p-lag-fix DP3/4/5.zip
13. Mount Vendor on TWRP
14. Go to TWRP Advanced->Terminal, type the following and press enter
echo persist.sys.disable_rescue=true >> /vendor/build.prop
15. Reboot to System
16. Install Google Play Services Apk, reboot and proceed normally
Click to expand...
Click to collapse
TIPS
Mi5 'Fingerprint Always On' On Android P (Unlock when screen off, and without press any button. Just touch it FP)
- Root your Mi5 with 16.4/16.6 Treble version
- Install Karnel Auditor
- Go to Tab, Select Custom Control
- Press "+", and import this .json file
- Press 3 dots at there, check 'on boot'
- Reboot
Click to expand...
Click to collapse
Mi5 Fingerprint as Home by rmrbpt
- Root your Mi5 with 16.4/16.6 Treble version
- Install Karnel Auditor
- Go to Tab, Select Custom Control
- Press "+", and import this .json file
- Press 3 dots at there, check 'on boot'
- Reboot
Click to expand...
Click to collapse
Mi5 Double Tap to Wakeup Android P
- Root your mi5 with 16.4/16.6 Treble version
- Open Karnel Auditor
- Go to Tab
- Find 'Wake'
- Turn it on, and apply on boot
- Reboot
Click to expand...
Click to collapse
Disable backlight button
Flash Disable Backlight.zip from Magisk !
Attached below.
Click to expand...
Click to collapse
Fix Battery Drain Issue
Still working on it
Alternative for it
- Dissable Dev Mode in Setting
or
- Try custom karnel
Click to expand...
Click to collapse
Get Blue accent / Pixel theme
Add this to your /vendor/build.prop, save and reboot:
Code:
ro.boot.vendor.overlay.theme=com.google.android.theme.pixel
Click to expand...
Click to collapse
MTP Not Detected
- Goto Setting
- System > Advanced > Dev Options > Choose File Transfer at USB Default Configuration
Click to expand...
Click to collapse
How to flash custom kernel on P GSI
FLASHING CUSTOM KARNEL CAUSING YOU CANNOT ENABLE MTP FORVER AND CHARGING FROM PC/LAPTOP
- Follow instruction from flashing JDC untill POST GSI 2, dont flash POST GSI 3.
- Flash Custom Karnel
- Reboot
- Clean Flash is the only way to fix it for now
Click to expand...
Click to collapse
Fix/Solution Arnova/BSG/other dev Gcam lag when changging between front and back camera on P
- Flash Camera Switch Lag Fix.zip, attached below.
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Terribly sorry but at what point did you make that "backup file"? I couldn't fix bootloop without your backup. Just wondering, since it's so large and probably mi5-only maybe you could just give us instructions how to make a working system without using someone else's backup?

After restore, have been stuck in G logo for 25 minutes, just followed the instruction

mansonstein said:
After restore, have been stuck in G logo for 25 minutes, just followed the instruction
Click to expand...
Click to collapse
Try select system only. goodluck.

mansonstein said:
After restore, have been stuck in G logo for 25 minutes, just followed the instruction
Click to expand...
Click to collapse
dont choose system image and vendor image.
but system and vendor only

bukandenny said:
dont choose system image and vendor image.
but system and vendor only
Click to expand...
Click to collapse
Yes, exactly, and I tried just system and just vendor, all stucked in G logo. Someway else to try? What causes reboot loop? Thx

If anyone successed, please let me know how you did it.

mansonstein said:
If anyone successed, please let me know how you did it.
Click to expand...
Click to collapse
3 times i used that way, and always work.
asking someone to do that, its work.

mansonstein said:
If anyone successed, please let me know how you did it.
Click to expand...
Click to collapse
try second methode above.

https://drive.google.com/open?id=1VryExVHI-14NfgIcBPp2dFiN-rzhOeNO
I've tried both the methods , but I always end up at this error, please help.
It asks for password and then just reboots into recovery.
There's also a pop up stating "There's internal problem, please contact manufacturer for details"
The above link has the images of the issue.
It would be really helpful if someone can help me boot this rom up. Thank you.

Santosh Kolur said:
https://drive.google.com/open?id=1VryExVHI-14NfgIcBPp2dFiN-rzhOeNO
I've tried both the methods , but I always end up at this error, please help.
It asks for password and then just reboots into recovery.
There's also a pop up stating "There's internal problem, please contact manufacturer for details"
Click to expand...
Click to collapse
Start from beginning.
you need to FORMAT DATA (not wipe data)
then start from beginning dude.

Santosh Kolur said:
https://drive.google.com/open?id=1VryExVHI-14NfgIcBPp2dFiN-rzhOeNO
I've tried both the methods , but I always end up at this error, please help.
It asks for password and then just reboots into recovery.
There's also a pop up stating "There's internal problem, please contact manufacturer for details"
The above link has the images of the issue.
It would be really helpful if someone can help me boot this rom up. Thank you.
Click to expand...
Click to collapse
http://xiaomitips.com/media/2016/07/Format-Data-TWRP.png

bukandenny said:
http://xiaomitips.com/media/2016/07/Format-Data-TWRP.png
Click to expand...
Click to collapse
Thank you. I got it to boot using your solution.

Santosh Kolur said:
Thank you. I got it to boot using your solution.
Click to expand...
Click to collapse
Decrypting internal storage fixes reboots?

Yes it did for me.

First method did it for me, too. I had the bootloop after first reboot and it did the trick, everything is working fine, a bit laggy, but Android P is running smooth on my phone!! I think that's very importat that after first boot you install Play Services as stated in OP and let Google finish its whole Pixel Configuration and updates, then you can try and reboot the phone, if you're hit by the bug, just follow what's in OP.
Few things if you install the GSI and have these issues:
- for Magisk, install version 16.4, just install that after you have set up the phone and stuff, you reboot to twrp and flash it, that's the way it works for me;
- if you have missing network on SIM, just go and configure your apn manually, it'll do the trick;
- for MTP, it's not working for me out of the box, the trick is to enable developers options, go to "Default USB Configuration" or something similar (I have it on italian, so I think that's how it's in English) and select the first one option;
Edit: also there's fingerprint that cannot wake the device, I've read in Telegram groups that some fixes are around for fingerprint, I'll check it out later and report if I find something interesting.

I've suceeded but my FP isn't working, already sent the logcat to the main xda page of GSI

g33k0 b3lk0w said:
I've suceeded but my FP isn't working, already sent the logcat to the main xda page of GSI
Click to expand...
Click to collapse
Cool! So I think there's no solution to this issue at the moment?

aittamattia said:
Cool! So I think there's no solution to this issue at the moment?
Click to expand...
Click to collapse
wait ill upload, u can see my chat on group

Related

[BUG FIX UPDATE] [Lollipop] CyanogenMod 12S YNG1TAS1k0

This Update Provides power improvements and security enhancement for your device​
Heating and Battery issues are seems to be fixed
Before you proceed:
Updating to this update doesn’t wipe your data. Still, you should back up all your important data, just in case.
This is an official bug fix update. Installing this, even manually using the method we are providing, doesn’t void your manufacturer warranty in any way.
Make sure that your phone isn’t low on battery. Anything above 35% should be good enough to go ahead with. (Any guide on the internet that asks you to charge your phone above 80% before following a guide, is simply taking unrequired precaution.)
Update Yu Yureka
1.Download the Update file from below (official link).
2.Transfer this zip file as it is (don’t extract it) to the internal storage of your Yureka.
3.Once you’ve done so, reboot your Yureka in recovery mode. To do that, do either of the following steps:
Go to Settings > About phone and tap on the Build Number field seven times. This would unlock Developer Options. Now go to Settings > Developer Options and tick the Advanced Reboot option. Now long press the power button, and then 4.
select the reboot option to get the reboot to recovery option. Select it to boot into the recovery option.
Otherwise, power off your Yureka. Once it shuts down completely, press and hold the Volume Up, Volume Down and 5.
4.Power buttons together till the phone boots up into the recovery mode.
When you enter the recovery mode, select the Apply update option, then the Choose from internal storage option, then the 0/ option, and finally select the cm-tomato-56deeca328-to-00b2e333e8-signed.zip file that you copied to your phone in step 2.
5.Once you select the file in the last step, the recovery will start flashing the update. When the flashing completes, you will be back on the main screen in the Recovery mode.
6.Select the Reboot system now option and wait for the reboot process to complete
Download link
great!
We desperately needed this!
how to flash this update, you provided
Rakesh251 said:
how to flash this update, you provided
Click to expand...
Click to collapse
Thread updated with Procedure
Sangeet007 said:
This Update Provides power improvements and security enhancement for your device​
Heating and Battery issues are seems to be fixed
Before you proceed:
Updating to this update doesn’t wipe your data. Still, you should back up all your important data, just in case.
This is an official bug fix update. Installing this, even manually using the method we are providing, doesn’t void your manufacturer warranty in any way.
Make sure that your phone isn’t low on battery. Anything above 35% should be good enough to go ahead with. (Any guide on the internet that asks you to charge your phone above 80% before following a guide, is simply taking unrequired precaution.)
Update Yu Yureka
1.Download the Update file from below (official link).
2.Transfer this zip file as it is (don’t extract it) to the internal storage of your Yureka.
3.Once you’ve done so, reboot your Yureka in recovery mode. To do that, do either of the following steps:
Go to Settings > About phone and tap on the Build Number field seven times. This would unlock Developer Options. Now go to Settings > Developer Options and tick the Advanced Reboot option. Now long press the power button, and then 4.
select the reboot option to get the reboot to recovery option. Select it to boot into the recovery option.
Otherwise, power off your Yureka. Once it shuts down completely, press and hold the Volume Up, Volume Down and 5.
4.Power buttons together till the phone boots up into the recovery mode.
When you enter the recovery mode, select the Apply update option, then the Choose from internal storage option, then the 0/ option, and finally select the cm-tomato-56deeca328-to-00b2e333e8-signed.zip file that you copied to your phone in step 2.
5.Once you select the file in the last step, the recovery will start flashing the update. When the flashing completes, you will be back on the main screen in the Recovery mode.
6.Select the Reboot system now option and wait for the reboot process to complete
Download link
Click to expand...
Click to collapse
OTA or manual update, both have to be flashed using stock recovery, right?
Plz give me the link for stock recovery compatible with CM12S
i am using ThunderZap 4.1 kernel, i am on official lollipop rom,and using twrp recovery. so can i direct flash this.zip via twrp?
Mohammed Raza said:
OTA or manual update, both have to be flashed using stock recovery, right?
Plz give me the link for stock recovery compatible with CM12S
Click to expand...
Click to collapse
Rakesh251 said:
i am using ThunderZap 4.1 kernel, i am on official lollipop rom,and using twrp recovery. so can i direct flash this.zip via twrp?
Click to expand...
Click to collapse
Stock recovery :- http://d-h.st/oYvV
and maybe if youre on stock rom you can flash it using thunderzap's kernel (But im not sure)
Better to use Stock recovery thou
Mohammed Raza said:
OTA or manual update, both have to be flashed using stock recovery, right?
Plz give me the link for stock recovery compatible with CM12S
Click to expand...
Click to collapse
Rakesh251 said:
i am using ThunderZap 4.1 kernel, i am on official lollipop rom,and using twrp recovery. so can i direct flash this.zip via twrp?
Click to expand...
Click to collapse
@Rakesh: no you can not flash it with twrp. ammm may be you will get "installation aborted" error
here is link for stock Recovey.
Stock kernel and recovery
Following error
sal_rc said:
Stock kernel and recovery
Following error
Click to expand...
Click to collapse
amitroutray said:
I am rooted With stock recovery by temporary method.. I am purely on Stock only. When I am manually updating through my stock recovery.. It is showing me the errors...
I have checked the md5 also it is correct.
Thank I advance.
Triggered from YU
Click to expand...
Click to collapse
donwload this whole rom which is included update.
LINK
this should be flash by CM stock recovery only.
I don't feel any change specifically can anyone suggest me why
---------- Post added at 10:01 AM ---------- Previous post was at 09:54 AM ----------
Getiing same error
And can I know the size of the ROM u have given link
#akadroid said:
I don't feel any change specifically can anyone suggest me why
---------- Post added at 10:01 AM ---------- Previous post was at 09:54 AM ----------
Getiing same error
And can I know the size of the ROM u have given link
Click to expand...
Click to collapse
the size of the rom is 643.767MB
i am downloading it.
I can't afford downloading it dude please send me a CD
Lol
But plzzz tell surely if u feel any change
I am rooted With stock recovery by temporary method.. I am purely on Stock only. When I am manually updating through my stock recovery.. It is showing me the errors...
I have checked the md5 also it is correct.
Thank I advance.
Triggered from YU
I think we have to relock the boot loader..
The zip is too large. If I download the OTA on phone, is it the same size or is it a smaller file size?
And if I manually flash from recovery, don't I need to clear cache?
sal_rc said:
Stock kernel and recovery
Following error
Click to expand...
Click to collapse
Hi
The message is very clear:
Your /system partition is RW (read write)
Thats becouse you rooted the device and enabled RW on /system.
Put the /system partition back to his stock state (Read only) and you should be good to go
Cheers
superdragonpt said:
Hi
The message is very clear:
Your /system partition is RW (read write)
Thats becouse you rooted the device and enabled RW on /system.
Put the /system partition back to his stock state (Read only) and you should be good to go
Cheers
Click to expand...
Click to collapse
Mine also same error how to put it back to read only
Worked For ME!!!
I'm on Stock Kernel+Stock Recovery+Non-Rooted+Bootloader Locked :silly:
That Means I have not tinkered with my Device in any means, It is as it was when It was Delivered .
I flashed this update and it was successful. :good: Thanks Pressed.
Faizal Mhate said:
I'm on Stock Kernel+Stock Recovery+Non-Rooted+Bootloader Locked :silly:
That Means I have not tinkered with my Device in any means, It is as it was when It was Delivered .
I flashed this update and it was successful. :good: Thanks Pressed.
Click to expand...
Click to collapse
You flashed the one which is 120MB or so or the 600MB one?

[TWRP OFFICIAL] [3.2.1-0] c9ltechn/SM-C9000 Galaxy C9 Pro

TWRP for C9LTECHN/SM-C9000 Galaxy C9 Pro
Special Notes:
1. DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options).
2. KNOX will be tripped once you flashed custom binaries to your phone.
(Your warranty may be voided. However this may not affect you if your country forces Samsung to provide hardware warranty regardless of software status.)
3. Samsung Firmware OTA (aka System Updates) will no longer work once you flashed custom binaries.
(You can flash custom ROMs if you want to keep the OS up-to-date.)
PLEASE BEFORE YOU FLASH ROMS MAKE A COMPLETE BACKUP OF YOUR SYSTEM INCLUDING EFS SO YOU DO NOT BRICK YOUR MOBILE
WHAT IS TWRP?
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
How to intall TWRP using ODIN
1) Go to Settings » About phone » and tap “Build number” seven times to enable “Developer options”.
2) Go back to the main Settings page, scroll to bottom and select“Developer options” from there.
3) Under Developer options, look for “Enable OEM unlock”checkbox/toggle and make sure you Check it or turn it ON.
4) Now Boot your Samsung Android device into Download mode.To Do So Follow the steps below
5) Switch off your device.
6) Press and hold “Home + Power + Volume down” buttons for a few seconds until you see a warning screen.
Press Volume Up on the warning screen to accept it and boot into Download mode.
Once your device is in download mode, connect it to the PC with a USB cable. The Odin will automatically detect the device and show an “Added!!” message. If not then your device is not connected properly
7) Now click on the AP tab on Odin window and select the TWRP recovery .tar file that you downloaded for your device.
8) Click the Start button on Odin to start Flashing and wait for it to finish the process.
Once it finished successfully, a pass message on the Odin screen will pop up
Your device will automatically reboot when Odin is done flashing. Now You can disconnect your device.
Done!!! TWRP is now installed on your device
NOTE: YOU MAY HAVE TO UNCHECK AUTO REBOOT IN THE OPTIONS TAB IN ODIN
TWRP source code: https://github.com/TeamWin
Source code device tree: https://github.com/travismills82/twrp_android_device_samsung_c9ltechn https://github.com/TeamWin/android_device_samsung_c9ltechn/
TWRP Nougat Download: https://www.androidfilehost.com/?fid=889964283620775437
TWRP Oreo Download: https://www.androidfilehost.com/?fid=1322778262903985796
no-verity-no-encrypt: https://www.androidfilehost.com/?fid=745425885120752506
ROOT OPTIONS:
SuperSU: https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Contributors @travis82 @k2wl @deadman96385
I can confirm this works. backup, mount data, restore, otg usb, install.
I am runnung it now
Does this work on a SM-C9000?
Flavio said:
Does this work on a SM-C9000?
Click to expand...
Click to collapse
That's already for C9000. Can't you see the c9ltechn article. That's c9 pro's code
Thank you. I have already installed it.
I have flashed TWRP, formatted Data twice, flashed no-verity-opt-encrypt-5.1.zip, flashed SuperSU and after that I can mount Data. But after a reboot I can't anymore? Am I doing something wrong?
Flavio said:
Thank you. I have already installed it.
I have flashed TWRP, formatted Data twice, flashed no-verity-opt-encrypt-5.1.zip, flashed SuperSU and after that I can mount Data. But after a reboot I can't anymore? Am I doing something wrong?
Click to expand...
Click to collapse
You can flash any file still that just an article but you can't mount data anymore or backup data
I can flash files but cannot mount Data. I presume it is still encrypted despite being formatted twice?
Format data and reboot to recovery
ivanox1972 said:
Format data and reboot to recovery
Click to expand...
Click to collapse
So in TWRP format Data and then reboot again in TWRP.
And then flash SuperSU and no_verity?
Ok, I formatted Data twice in TWRP. Mounting Data works.
I flashed SuperSU in TWRP. Mounting Data works.
I flashed no_verity. Mounting Data works.
I rebooted into TWRP. Mounting Data works.
I rebooted into system and then switched off and rebooted into TWRP. Mounting Data does not work.
What am I doing wrong?
Correction:
I have now used this no-verity-no-encrypt_ashyx file:
https://www.androidfilehost.com/?fid=24591000424951049
And now Data stays decrypted!
I do have a stock debloated rom that is made out of HK firmware if this community is interested, I can put it up. All I see is you guys using Aurora. Anyone interested or do you all want to stick to Aurora rom?
I tested it few days, it works perfect and it is perfectly debloated
Please share Travis. Thank you for your work.
travis82 said:
I do have a stock debloated rom that is made out of HK firmware if this community is interested, I can put it up. All I see is you guys using Aurora. Anyone interested or do you all want to stick to Aurora rom?
Click to expand...
Click to collapse
can you share it please ???
I presume you would have to flash GApps separately with this ROM?
Flavio said:
I presume you would have to flash GApps separately with this ROM?
Click to expand...
Click to collapse
no god no, HK firmware has gapps built in like normal. I'll tweak it up some more and release it today on a separate thread. Right now I'm trying to get kernels to boot-up since they compile fine.
travis82 said:
I do have a stock debloated rom that is made out of HK firmware if this community is interested, I can put it up. All I see is you guys using Aurora. Anyone interested or do you all want to stick to Aurora rom?
Click to expand...
Click to collapse
I am interested, currently I just using the package disabler to disable all bloat samsung app..
do you have flashable s8 systemui for c9pro.. thanks
TWRP updated with a new kernel, USB MTP is now working. Everything should be working now.
travis82 said:
TWRP updated with a new kernel, USB MTP is now working. Everything should be working now.
Click to expand...
Click to collapse
Awesome work buddy, ill try to make my own ROM for this device :highfive:
will be pushing f2fs and ntfs support soon too when TWRP becomes official.

twrp 3.1 ZenFone 4 Pro Z01GD

TWRP for ASUS ZenFone 4 Pro Z01GD-
Disclaimer-
Code:
Do at own Risk i am Not Responsible for any Damage to your Phone.
- Download:
https://androidfilehost.com/?fid=817906626617939092
1. Install TWRP recovery :
- Go Setting > Developer mode > turn on USB deburg and oem unlock..
- unlock bootloader using unlock app
- Download Provided twrp use fastboot or inbuild script
Code:
fastboot flash recovery recovery.img
2. Root your device
- Swipe modified system
- Install > Select No verity file. Then select tab Reboot > Recovery. DO NOT MISS STEP, YOU PHONE WILL BE BOOTLOOP OR KEEP RED WARNING IN BOOTING
- Install > Select No-verity
- Install > Select Magisk
- Reboot your phone and enjoy...
I hope You will get successfully
Thanks All
This is a Materialized recovery if You need default twrp you can use @shakalaca's build here
https://forum.xda-developers.com/zenfone-4-pro/development/recovery-twrp-3-1-1-0-zs551kl-t3692186
XN Logos said:
TWRP for ASUS ZenFone 4 Pro Z01GD-
Disclaimer-
Code:
Do at own Risk i am Not Responsible for any Damage to your Phone.
- Download:
https://androidfilehost.com/?fid=817906626617939092
1. Install TWRP recovery :
- Go Setting > Developer mode > turn on USB deburg and oem unlock..
- unlock bootloader using unlock app
- Download Provided twrp use fastboot or inbuild script
Code:
fastboot flash recovery recovery.img
2. Root your device
- Swipe modified system
- Install > Select No verity file. Then select tab Reboot > Recovery. DO NOT MISS STEP, YOU PHONE WILL BE BOOTLOOP OR KEEP RED WARNING IN BOOTING
- Install > Select No-verity
- Install > Select Magisk
- Reboot your phone and enjoy...
I hope You will get successfully
Thanks All
Click to expand...
Click to collapse
Your file is stolen from @shakalaca 's
please remove this post and apologize to him
samyeh9999 said:
Your file is stolen from @shakalaca 's
please remove this post and apologize to him
Click to expand...
Click to collapse
this one is materialized recovery, so first of all check and don't blem okay...
samyeh9999 said:
Your file is stolen from @shakalaca 's
please remove this post and apologize to him
Click to expand...
Click to collapse
Don't Submit any claim Before checking the files...
XN Logos said:
Don't Submit any claim Before checking the files...
Click to expand...
Click to collapse
@shakalaca has check the file, he is very sure that the file was stolen from his.
I has downloaded the file and record the MD5.
You can use any open code or file on web, but please give credit in the post.
so please don't forget to give credit ..
https://gist.github.com/shakalaca/397c278794d872235f49d3560127f909
My build is here ..
https://www.androidfilehost.com/?fid=889964283620758458
wow we're using the same editor so even the backup file is identical..
shakalaca said:
so please don't forget to give credit ..
https://gist.github.com/shakalaca/397c278794d872235f49d3560127f909
My build is here ..
https://www.androidfilehost.com/?fid=889964283620758458
wow we're using the same editor so even the backup file is identical..
Click to expand...
Click to collapse
Can you create this for the Zenfone AR as well?
Codename_Falcon said:
Can you create this for the Zenfone AR as well?
Click to expand...
Click to collapse
You should ask XN Logos, he's good at building tools
shakalaca said:
You should ask XN Logos, he's good at building tools
Click to expand...
Click to collapse
I read the thread. I'm asking you. Can you please help?

Bootloader unlockable

Sony's bootloader unlock page added the xperia 10 II to the list.
It's wrongly listed as "Xperia X10 II", so it's near the middle of the list, but gives the code with the IMEI
Edit:
Can't post link yet, the unlock page is: https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/​
I've done it but i'm facing a problem with rooting could you help me with that ?
hq8aus said:
I've done it but i'm facing a problem with rooting could you help me with that ?
Click to expand...
Click to collapse
As long as BL is unlocked, you may be able to root your device using XperiFirm, UnSIN and Magisk.
- XperiFirm > Download fw
- UnSIN > Get the boot_XXXX.sin file from the downloaded fw folder, and drop it over unsin.exe (you'll get boot_XXXX.img file).
- Move the boot_XXXX.img file to the device's internal storage (or sdcard).
- Install Magisk Manager app
- Magisk Manager app > Install > Uncheck 'Keep AVB 2.0/dm-verity' > Next > Select and patch a file > Choose the boot_XXXX.img (you'll get /Download/magisk_patched.img)
- Flash magisk_patched.img with fastboot with command:
Code:
fastboot flash boot magisk_patched.img
- Reboot
If something goes wrong, you'll need to flash original stock boot img file (boot_XXXX.img) with fastboot (or even flash whole fw again).
Try it at your own risk.
serajr said:
As long as BL is unlocked, you may be able to root your device using XperiFirm, UnSIN and Magisk.
- XperiFirm > Download fw
- UnSIN > Get the boot_XXXX.sin file from the downloaded fw folder, and drop it over unsin.exe (you'll get boot_XXXX.img file).
- Move the boot_XXXX.img file to the device's internal storage (or sdcard).
- Install Magisk Manager app
- Magisk Manager app > Install > Uncheck 'Keep AVB 2.0/dm-verity' > Next > Select and patch a file > Choose the boot_XXXX.img (you'll get /Download/magisk_patched.img)
- Flash magisk_patched.img with fastboot with command:
Code:
fastboot flash boot magisk_patched.img
- Reboot
If something goes wrong, you'll need to flash original stock boot img file (boot_XXXX.img) with fastboot (or even flash whole fw again).
Try it at your own risk.
Click to expand...
Click to collapse
Thank you for the tutorial i will try it after few hour
I have one question : my phone refuse to enter recovery mode once the recovery mode boot the phone restart and start normally so i'm surprised do u know if this a common problem?
hq8aus said:
Thank you for the tutorial i will try it after few hour
I have one question : my phone refuse to enter recovery mode once the recovery mode boot the phone restart and start normally so i'm surprised do u know if this a common problem?
Click to expand...
Click to collapse
You're welcome. Xperia devices are not provided with a recovery, you need a custom one (by the way not yet available for this model).
serajr said:
You're welcome. Xperia devices are not provided with a recovery, you need a custom one (by the way not yet available for this model).
Click to expand...
Click to collapse
Thank you very much the method u wrote worked
now i'm free to install mods ? " i know it's stupid question but i'm beginner in rooting"
hq8aus said:
Thank you very much the method u wrote worked
now i'm free to install mods ? " i know it's stupid question but i'm beginner in rooting"
Click to expand...
Click to collapse
Glad to know that.
Sure you are! You can flash EdExposed and, for e.g., install my xposed modules ( Home Xposed for Q and Call Recording ).
Also any other hack you want to (my debloat script >> here << may also work).
Just a warning: due the lack of a recovery, if you face a bootloop after mess with something, you'll need to disable all the installed magisk modules to be able to boot up device, and to do so, you'll need to create a Core Mode Only magisk (google it) and fastboot it.
sorry to bother you .. but is there anyway to mount the "/system" to r/w ? because i'm having problem in moving file into it
hq8aus said:
sorry to bother you .. but is there anyway to mount the "/system" to r/w ? because i'm having problem in moving file into it
Click to expand...
Click to collapse
First of all ensure all your installed magisk modules are disabled (disable them all and reboot).
Magisk bind-mounts /system/* (specific modules folders) to do its initial mount logic, so changes into those system folders at runtime won't be allowed (if that specific system folder is used by a magisk module).
I don't know if this is your case, but I drop here this warning.
adb commands to mount system (rootfs)
rw:
Code:
mount -orw,remount /
ro:
Code:
mount -oro,remount /
You could try also to disable the vbmeta params by fastbooting vbmeta*_.img (vbmeta_*.sin > unsin.exe > vbmeta*_.img) with command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta*_.img
hi everyone,
after rooting with the boot.img patch method is there a good way to de-google the stock rom? i've seen twrp scripts for this but obviously those don't apply here, and i'm not exactly sure what is safe to remove and what is not, as a few days ago when i did this (via the /d/gapps app from f-droid) the system got stuck in a bootloop.
any ideas?
Ber7az said:
Sony's bootloader unlock page added the xperia 10 II to the list.
It's wrongly listed as "Xperia X10 II", so it's near the middle of the list, but gives the code with the IMEI
Edit:
Can't post link yet, the unlock page is: https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/​
Click to expand...
Click to collapse
Hi, is it possible to relock the bootloader?
Supercharlie25 said:
Hi, is it possible to relock the bootloader?
Click to expand...
Click to collapse
You could try and confirm. Xperia 1 and Xperia 5 are lockable but is not the Xperia 10, maybe the Xperia 10 II could be lockable, try on your own risk
serajr said:
As long as BL is unlocked, you may be able to root your device using XperiFirm, UnSIN and Magisk.
- XperiFirm > Download fw
- UnSIN > Get the boot_XXXX.sin file from the downloaded fw folder, and drop it over unsin.exe (you'll get boot_XXXX.img file).
- Move the boot_XXXX.img file to the device's internal storage (or sdcard).
- Install Magisk Manager app
- Magisk Manager app > Install > Uncheck 'Keep AVB 2.0/dm-verity' > Next > Select and patch a file > Choose the boot_XXXX.img (you'll get /Download/magisk_patched.img)
- Flash magisk_patched.img with fastboot with command:
Code:
fastboot flash boot magisk_patched.img
- Reboot
If something goes wrong, you'll need to flash original stock boot img file (boot_XXXX.img) with fastboot (or even flash whole fw again).
Try it at your own risk.
Click to expand...
Click to collapse
Hi, is possible flash custom Rom without recovery? I saw that it is already available for download Pixel Experience for our device. Thanks for replay.
Thapsus-cz said:
Hi, is possible flash custom Rom without recovery? I saw that it is already available for download Pixel Experience for our device. Thanks for replay.
Click to expand...
Click to collapse
I have no idea (I've never played with custom roms - stock only).
Pay attention to the 2020/08/19 build, it has a recovery image file available (as per I could see).
serajr said:
I have no idea (I've never played with custom roms - stock only).
Pay attention to the 2020/08/19 build, it has a recovery image file available (as per I could see).
Click to expand...
Click to collapse
Thank you, I'd rather wait, maybe we'll see TWRP soon.
Has anyone installed LineageOS on this?
xdauserart said:
Has anyone installed LineageOS on this?
Click to expand...
Click to collapse
The only custom ROM for our device I found Pixel Experience here https://download.pixelexperience.org/xqau52 But unfortunately I failed to flash the their recovery and twrp is not yet.
Thapsus-cz said:
The only custom ROM for our device I found Pixel Experience here ... But unfortunately I failed to flash the their recovery and twrp is not yet.
Click to expand...
Click to collapse
That doesn't sound great. I'm looking for ways to de-google it, remove tracking apps, etc. Looks like now only way is to remove apps manually via `adb`. But I'm not sure what apps to remove.
Will installing AOSP for Android 11 with Sony image be without Google apps (like Google Play and other bloat)? Did anyone try installing this? Sony has added Xperia 10 II to Open devices program recently.
@xdauserart, @Thapsus-cz, Do you know if after Unlock BL of xperia 10 II, boots with the message "Your device can't be checked by corruption. Please lock the bootloader '? And if its available some method to backup TA before, for this model? Thanks......

Development [RECOVERY] [11] [OFFICIAL] TeamWin Recovery Project

Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Hello, this is TWRP, for Mi 11 lite 5G
bugs:
backup/restore is unreliable
adb sideload and fastbootd
Installation:
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3. after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
Updating to a newer build:
1. download new build to internal storage
2. go to Advanced > Install Recovery Ramdisk
4. select the new image
5. after that is done, if you were using a custom kernel, reflash it now
6. if you were using magisk, reflash it now
Send me a beer: Crypto (Preferred) | PayPal
Contributors:
@VladV1V , @TheMalachite
Tree:
GitHub - TeamWin/android_device_xiaomi_renoir
Contribute to TeamWin/android_device_xiaomi_renoir development by creating an account on GitHub.
github.com
Kernel:
https://github.com/VladV1V/kernel_xiaomi_renoir
Telegram group: https://t.me/NSSFB
Download: https://twrp.me/xiaomi/xiaomimi11lite5g.html
Sorry, but the installation did not work for me... :-( What i have done:
- i renamend the downloaded file to "twrp.img"
- i copied this file to the internal storage
- i startet the phone in fastboot mode
- then i startet adb
- i used the command "fastboot boot twrp.img"
Then i saw the following:
downloading 'boot.img'...
OKAY [ 2.826s]
booting...
OKAY [ 0.201s]
finished. total time: 3.027s
But the phone only switched off and nothing happend. What's wrong?
EDIT: i solved the problem! I forgot to put the file "twrp.img" into the adb folder. After doing this, the installation worked! Now i tried to make a backup, but it was not possible to select the external sd-card. How can i solve this problem?
Hi, thank's for your work for our device...
I read somewhere, that if we have TWRP installed, that we cannot flash update with fastboot...I want to know if it's true and if yes, how can we flash update..we have to find recovery update, or we can extract from fastboot archive and flash it??
thanks for your answer
Rainman67 said:
Now i tried to make a backup, but it was not possible to select the external sd-card. How can i solve this problem?
Click to expand...
Click to collapse
certainly not available yet...you have to backup in internal storage and then copy to SD...
Another question: how to go back to stock recovery?
Rainman67 said:
Another question: how to go back to stock recovery?
Click to expand...
Click to collapse
I'm on Xiaomi EU ROM. After last update via fastboot Miui Recovery 5.0 comes back.
Great hopefully this leads to development of some easy to flash roms, cant wait to get rid of this buggy MIUI trash.
I tried last version (16th July). Sadly no touchscreen.
Anyway many thanks!
same with #8 boot into twrp and no touchscreen
Peterpaulmarie said:
I tried last version (16th July). Sadly no touchscreen.
Anyway many thanks!
Click to expand...
Click to collapse
FuLuLu said:
same with #8 boot into twrp and no touchscreen
Click to expand...
Click to collapse
Boot TWRP from fastboot and touch will work.
Peterpaulmarie said:
I tried last version (16th July). Sadly no touchscreen.
Anyway many thanks!
Click to expand...
Click to collapse
FuLuLu said:
same with #8 boot into twrp and no touchscreen
Click to expand...
Click to collapse
How did you flash it?
Nebrassy said:
How did you flash it?
Click to expand...
Click to collapse
Fastboot boot twrp.img
Advanced - > flash current recovery
As well tried
Fastboot flash recovery twrp.img
Failed
Also
Advanced - > install recovery ramdisk
But magisk said ramdisk Yes
Peterpaulmarie said:
Fastboot boot twrp.img
Advanced - > flash current recovery
As well tried
Fastboot flash recovery twrp.img
Failed
Also
Advanced - > install recovery ramdisk
But magisk said ramdisk Yes
Click to expand...
Click to collapse
pm me on telegram if you can get logs and have adb access
dannejanne said:
Boot TWRP from fastboot and touch will work.
Click to expand...
Click to collapse
Nebrassy said:
How did you flash it?
Click to expand...
Click to collapse
i just boot to try if it can boot in twrp lol, no need to flash it so far,if needed it i will use the method u guys said(real flash in)
Well then both of you make sure you're actually using the build from afh and only use it for fastboot boot, when you want to flash use flash current twrp don't flash it with fastboot
Touch works when using fastboot boot and when flashed, it Was already tested on multiple devices
@Nebrassy Thanks for your contribution. Looking forward to the stable version with the known bugs fixed and touch works normally, without fastboot.
Thanks again.
doclucas said:
@Nebrassy Thanks for your contribution. Looking forward to the stable version with the known bugs fixed and touch works normally, without fastboot.
Thanks again.
Click to expand...
Click to collapse
Touch already works normally without fastboot
Nebrassy said:
Touch already works normally without fastboot
Click to expand...
Click to collapse
Nebrassy said:
Touch already works normally without fastboot
Click to expand...
Click to collapse
Yes, I can confirm. After start recovery wait 10-15sec touchscreen will work
With the test builds from telegram twrp was not able to recognize my SD card. Is this now fixed?
Is it possible to flash Xiaomi.eu weekly rom only by starting twrp from fastboot without installing it?

Categories

Resources