Related
Team Win Recovery Project 3.2.3-0
This is for the Exynos SM-J710F, SM-J710FN, SM-J710GN, SM-J710MN, SM-J710K models only!
WARNING: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
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.
DOWNLOAD
Build 3 3.2.3-0
Older builds:
Build 2 3.2.3-0
I highly recommend using Odin to flash when possible.
You can find a zip containing Odin as well as a link to Samsung's Mobile drivers page here:
https://odindownload.com/
FULL STEPS FOR ROOTING
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
Make sure your don't have Factory Reset Protection enabled in your Google account or you may never be able to boot again!
More information: https://support.google.com/nexus/answer/6172890?hl=en
Extract Odin_(version).zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for j7xelte.
Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
Open Odin and place that TWRP tar file in the [AP] slot, under Options tab disable Auto Reboot, then press [Start].
Once the flash is complete (Odin should tell you in the log, and progress bar on phone should stop), you can pull the battery then place the battery back in. Now hold [Volume Up] + [Home] + [Power] buttons until you reach recovery mode.
If you end up in stock recovery, start again from download mode step.
At this point, you will reach the screen asking you if you want to allow system modifications.
You will want to swipe to allow, otherwise the OS will replace TWRP once you boot!
If you want to be rooted with Magisk:
Download the latest Magisk.
Without exiting TWRP, transfer the Magisk zip to your device over MTP* and flash it using [Install] in TWRP.
Go to [Reboot] -> [System].
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
KNOWN ISSUES
You need to wipe Data when on stock ROM
Changelog
Build 1: Initial release
Build 2: Update to M10 kernel and android-8.1 source (from android-6.0)
Build 3: Fix MTP problems and /vendor (invalid argument) + upstreamed M10 kernel to 3.18.134 with google recommended changes to kernel
NOTE: If you're on stock Oreo rom always make sure your system is read only. Don't let it be r/w
SOURCE CODE:
TWRP (android-9.0)
Device tree (android-8.1)
Kernel: (pie)
why is not on the official web?
idk this seems pretty sketchy
M4T145 said:
why is not on the official web?
idk this seems pretty sketchy
Click to expand...
Click to collapse
I can't instantly get official i can upload pictures btw
Is it support Android 8.1.0 Firmware?
TRalperenTR said:
Is it support Android 8.1.0 Firmware?
Click to expand...
Click to collapse
Yes but make sure you leave system read only and flash magisk instantly to fix dm verify
Thanks man. It's worked! Every features is working. But why does it say E: on the console? I didn't understand.
TRalperenTR said:
Thanks man. It's worked! Every features is working. But why does it say E: on the console? I didn't understand.
Click to expand...
Click to collapse
I don't know. Its a twrp bug maybe. Also download it again i built it using the M10 kernel now but it also says /vendor invalid argument
...
It is working fine checked it
This TWRP doesn't install Oxygen Kernel. It says "Recovery Busybox Setup Failed."
I have already installed official twrp from website do i have to reinstall fresh on just download a zip for flash without installing magisk plus kindly upload a video for step by step process.
By the way a quick question is kernel 3.18.135 is latest or 3.18.14
Sulltan Mehmood said:
I have already installed official twrp from website do i have to reinstall fresh on just download a zip for flash without installing magisk plus kindly upload a video for step by step process.
By the way a quick question is kernel 3.18.135 is latest or 3.18.14
Click to expand...
Click to collapse
3.18.135 newer then 3.18.14
If you have other twrp extract the .tar archive and move .img to phone and goto Install on twrp select Install Image and Click on it. Select recovery and swipe to confirm. Done
Hi, the link of the latest build is down, can you re-upload please?
I saw in other tutorials that when in stock 8.1 rom you need to erase all data from internal memory. If i do this, there is no longer a, /system folder so there is no rom and bootloop happens.
Do i need to do factory wipe instead? I know i have to wipe data because Its encripted and twrp cant access internal memory.
Im asking what kind of "wipe data" i need to do
just format data to decrypt
link please
bro it says download file does not exist on google drive
download link ??
https://drive.google.com/open?id=1Xq4TAkcs9plY3zfGHiall21a3GgjdgHS
---------- Post added at 17:28 ---------- Previous post was at 17:28 ----------
saquib996 said:
bro it says download file does not exist on google drive
Click to expand...
Click to collapse
Ofogh said:
download link ??
Click to expand...
Click to collapse
https://drive.google.com/open?id=1Xq4TAkcs9plY3zfGHiall21a3GgjdgHS
[ZE620KL/Android 9][TREBLE] COMPLETE GUIDE: Unlocking, Rooting & Flash GSI + Fixes
Unlocking bootloader to Flashing GSI (Asus Zenfone 5 [ZE620KL] / Android 9.0)
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
About :
The last guide could leads to soft brick, as the instructions were not clear nor the files not supported for Android 9.0.
Here is a complete guide with TWRP 3.3.0 for Android 9.0, clear instructions and multiple fixes for GSI.
It has been tested on stock version v16.0615.1903.92.
Requirements :
- A stock version V16.0610.XXXX.XX or higher
- A phone on Android 9.0 (not 8.0!)
- A fully working USB cable
- Latest ADB / Fastboot drivers
- Bootloader unlocker (download latest from Asus website or from here)
- TWRP 3.3.0 image
- Android9EncryptionDisablerZE620KL.zip
- Magisk v19.3
Instructions :
Unlocking Bootloader
1. Backup all your important data.
2. Install the bootloader unlocker APK, and follow the steps. You will loss your warranty here, and it will factory reset your data
3. If there is any issue here, go into your stock recovery (volume down + power button) and factory reset.
Installing TWRP
4. Shutdown your device & boot in fastboot mode using volume up + power button.
5. Check that the connection between your device and your computer by typing this in your command line :
Code:
fastboot devices
6. Flash TWRP recovery using :
Code:
fastboot flash recovery <twrp_name>.img
7. Now reboot in recovery mode using :
Code:
fastboot oem reboot-recovery
8. In TWRP, select Wipe > Format Data > enter "yes" and confirm
9. Return to the main menu, select Reboot > Recovery
10. Do 8. & 9. and again
11. Using TWRP or ADB, install Android9EncryptionDisablerZE620KL.zip (on TWRP, go into Install > find Android9EncryptionDisablerZE620KL.zip > Install zip)
If everything has gone successfully, you now have a custom recovery.
As for some GSIs, a patched boot partition may cause bootloop, you should try installing Magisk after installing the GSI. If you want to keep your stock ROM, go directly to "Magisk Installation" section.Installing a GSI
This step may vary depending on the different GSIs distribution. I assume you install Havoc OS v2.7 GSI which actually works on this device.
1. Backup all your important data using TWRP backup.
2. Select the arm64-aonly GSI image you want, and move it on your external SD.
3. Wipe Data, Dalvik, and Cache.
4. Go back in the main menu of TWRP, and reboot to recovery.
5. Remove Magisk if it was previously installed, by using its uninstaller script.
6. Flash the GSI to system partition.
7. Boot and perform a factory reset.
Installing Magisk
1. Add the Magisk zip archive to your external storage.
2. Boot into TWRP recovery, and install the zip.
3. Enjoy!
Bug fixes:
Insufficient storage in the system partition to flash GApps : Download your OpenGApps archive on your external SD, and use MagicGApps 2018.9.23 to install GApps.
Auto-Brightness doesn't work: Download framework-res__auto_generated_rro.apk from here.
Using a root explorer or command-line, push the APK to /vendor/overlay.
Then run the following command in a rooted terminal or ADB shell:
Code:
chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay;chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay/framework-res__auto_generated_rro.apk
My camera doesn't work well (green tint on face camera) and/or the app doesn't boot: If Asus Camera doesn't launch on your GSI, you should probably edit your /system/build.prob file.
You need to edit ro.product.model, ro.product.brand, ro.product.name, ro.product.device, ro.product.manufacturer & ro.build.product properties to be:
Code:
ro.product.model=ASUS_X00QD
ro.product.brand=asus
ro.product.name=WW_Phone
ro.product.device=ASUS_X00QD
ro.product.manufacturer=asus
ro.build.product=ZE620KL
You can instead use Google Camera mod (port from Arnova8G2 & modded by 5Z community, thanks to them!), which works well (edit: there is a bug on HavocOS, we can't access settings).Bonus:
- You can reinstall DTS Headphone:X here.
- For booting your kernel in Permissive mode, check here
Sources:
TWRP 3.3.0 : On GitHub
If you need help or if you want to help on ZE620KL development go here:
https://t.me/Zenfone5Dev
(We will continue to update & help here though.)
Many thanks to all of the Zenfone 5 community (particularly Emincan, Pandolfi and Lmajkej),
Phhusson & Erfan for their works on GSI, and Shakalaca for its work on TWRP 3.3.0!
On HavocOS v2.8 GSI (13-08-2019):
It works:
- Almost anything
- Adaptive Brightness (after manual fix)
- Notch overlay
- DTS Headphone X (after manual installation)
- NFC
- Face unlock
- Stock camera (after manual fix)
- Magisk
- SDcard access
It doesn't works:
- VoLTE / VoWifi
- Google Camera settings
- External speaker amplifier (NXP amp)
- APT-X / APT-X HD bluetooth
- Low microphone in normal use
- No microphone in calls (only headphone microphone works)
GCam settings
But my google camera keep crashing when I want to go into camera settings
Hi thanks for this tutorial, this is my first time rooting my phone. I'm encountering a problem with my sd card after installing havoc os, everytime i try to move, save or any write functionality i do to my sd card, it always says the android version isn't compatible. I could still see my files from my sd, but everytime it asks permission it always say this
bentley0928 said:
But my google camera keep crashing when I want to go into camera settings
Click to expand...
Click to collapse
Same issue here. I will update the thread when I will find a more working GCam port (perhaps, this GCam port works well on ZenUI)
Jolo110 said:
Hi thanks for this tutorial, this is my first time rooting my phone. I'm encountering a problem with my sd card after installing havoc os, everytime i try to move, save or any write functionality i do to my sd card, it always says the android version isn't compatible. I could still see my files from my sd, but every time it asks permission it always say this
Click to expand...
Click to collapse
It's a known issue, the GSI maintainer @vince31fr is working on it. I don't have it, but I can advice you to use Solid File Manager, which works like a charm on my device.
"- No microphone in calls (only headphone microphone works)"
Funny... I'm on stock latest firmware and I have this issue, so I thought I try something new, and this has that issue. It can't be a coincidence. Something is ****ed up with this device.
Wonder if this will work for the Zenfone 5 Lite (or 5Q)? I wanna root my 5Q so bad haha
Thanks for the great instructions! Steps 1 through 11 worked perfectly for me, then I installed LineageOS (lineage-17.0-20191231-UNOFFICIAL-treble_arm64_avN.img) and it works properly. Then when I go back to TWRP and install Magisk v20.1 it reboots into an endless Lineage bootup logo animation (not boot loop). I can get an adb shell, but now also the external SD card has become invisible. Any suggestions?
UPDATE: I switched over to the patched Magisk version from PHH (https://forum.xda-developers.com/zenfone-5/general/ze620kl-add-support-to-evey-android-9-t3966918) and everything works perfectly now!
Hi!! I thanks for these instructions you gave. I know this post is a bit older. But is the only one I think could help me.
I got an ZE620KL and I'm trying to root this device. I have some experience in unlocking bootloader and rooting devices. But this one... Is giving me a lot of work. Researching in a lot of forums and websites I tried a lot of things with no success. In theory, is just install the official apk provided by ASUS and run the application. But the app doesn't work for a long time as I researched (error accusing network problem). I tried unlock via fastboot commands but I always got stucked by "remote: permission denied" even with latest drivers and ADB Fastboot installed. And yes... I let my device with no one security feature enabled and didn't worked. I tried everything even after wiped data / cache and factory reset and no progress.
In my researches, I realized something about 'oem unlock'. It appears to be the key to solve this. And I guess the tool to work with this is the damn unlock tool from ASUS which don't work! Also, I've heard about workaround with Magisk by flashing a custom recovery to achieve the root. Magisk no longer supports zip files to flash. Only '.img' and '.tar' files. I'd like to find some light here... I don't know what to do. I appreciate any help!
Hello do I need to flash Android9EncryptionDisablerZE620KL.zip if Im gonna flash a non-GSI custom ROM? Or its only for GSI Treble ROM?
[email protected] said:
Hi!! I thanks for these instructions you gave. I know this post is a bit older. But is the only one I think could help me.
I got an ZE620KL and I'm trying to root this device. I have some experience in unlocking bootloader and rooting devices. But this one... Is giving me a lot of work. Researching in a lot of forums and websites I tried a lot of things with no success. In theory, is just install the official apk provided by ASUS and run the application. But the app doesn't work for a long time as I researched (error accusing network problem). I tried unlock via fastboot commands but I always got stucked by "remote: permission denied" even with latest drivers and ADB Fastboot installed. And yes... I let my device with no one security feature enabled and didn't worked. I tried everything even after wiped data / cache and factory reset and no progress.
In my researches, I realized something about 'oem unlock'. It appears to be the key to solve this. And I guess the tool to work with this is the damn unlock tool from ASUS which don't work! Also, I've heard about workaround with Magisk by flashing a custom recovery to achieve the root. Magisk no longer supports zip files to flash. Only '.img' and '.tar' files. I'd like to find some light here... I don't know what to do. I appreciate any help!
Click to expand...
Click to collapse
Im not sure if you still have your phone or you have successfully unlocked bl. but I found an updated version of their tool which works.
*tried unlocking from android 10 not working, it says device model not supported*
Zenfone 5 Unlock BL
cf100clunk said:
Thanks for the great instructions! Steps 1 through 11 worked perfectly for me, then I installed LineageOS (lineage-17.0-20191231-UNOFFICIAL-treble_arm64_avN.img) and it works properly. Then when I go back to TWRP and install Magisk v20.1 it reboots into an endless Lineage bootup logo animation (not boot loop). I can get an adb shell, but now also the external SD card has become invisible. Any suggestions?
UPDATE: I switched over to the patched Magisk version from PHH (https://forum.xda-developers.com/zenfone-5/general/ze620kl-add-support-to-evey-android-9-t3966918) and everything works perfectly now!
Click to expand...
Click to collapse
Do you still have the patched Magisk zip file, the original link in the post seems not working
Code:
#include "std_disclaimer.h"
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Requirements
Unlocked bootloader
working ADB/fastboot on a PC
the TWRP image downloaded
Pie firmware on the active slot
Installation guide (pre metadata encryption):
Copy the twrp image to your phones storage and/or micro sdcard
Start cmd/powershell/terminal with working adb/fastboot
Reboot to bootloader
adb reboot bootloader OR
turn off the phone (or reboot), as soon as it turns on, hold volume down while USB cable is connected
If youre unofficially bootloader unlocked, and you nuked laf, its volume up and USB for you
fastboot boot TWRP-judypn-boot.img
Confirm allow system modifications if asked
Press cancel if asked for a password (aka when youre encrypted, could also be that it doesnt show you /data at all and no password screen)
Go to Advanced -> Install Recovery Ramdisk
Select the TWRP image which you copied to your phone/sdcard earlier
TWRP will now be installed to both slots (boot_a and boot_b)
Go to Reboot -> Recovery to make sure TWRP is successfully installed
Features:
Install recovery ramdisk:
Selecting this, and then an image (e.g. of TWRP) allows you to install the ramdisk (where TWRP resides for example) into both currently installed kernels/boot images
Inject TWRP after install:
Automatically injects current installed TWRP into the boot image of the ROM/zip youre installing when ticked
Broken:
LGs encryption on Stock
encryption on other ROMs(?)
How to flash ROMs (PRE metadata encryption):
Reboot to TWRP
Make a backup
Install -> select the ROM zip -> tick Inject TWRP -> Swipe for install
wait... ROM will be installed into the NON ACTIVE slot (if youre on a, it will be installed to b, and vice versa)
Reboot system
for gapps, magisk or other mods:
DO NOT REBOOT TO SYSTEM from last step
Go back -> Reboot -> select the non active slot (to where the rom got installed to) -> select recovery
Install gapps, magisk, and whatever else you want
Reboot system
How to initially flash ROMs (metadata encryption):
Reboot to existing TWRP
Make a backup of everything you want to keep
Copy backup to PC (or another external medium)
Flash the ROM
Do NOT inject TWRP (this will break recovery otherwise)
Go to reboot -> Select opposite slot
Reboot to recovery
Perform factory reset (this is to setup encryption)
Apply update (from ADB) with adb sideload for gapps/magisk
reboot to bootloader
fastboot boot judypn_TWRP_bootable-metadata.img
Use as usual
Reboot system
How to update ROMs (metadata encryption):
Reboot to bootloader
fastboot boot judypn_TWRP_bootable-metadata.img
Install -> Select ROM zip
do NOT inject TWRP
Reboot -> select opposite slot (it will tell you even which it installed the ROM to)
Reboot bootloader
fastboot boot judypn_TWRP_bootable-metadata.img
Install gapps/magisk
Or
reboot recovery
apply update -> from adb (in e.g. Lineage recovery)
On PC: adb sideload <new version zip>
(Advanced -> ) Reboot recovery
adb sideload gapps/magisk
reboot system
Warnings:
Updating a ROM means reflashing the mods you flashed too (e.g. Gapps), addon.d doesnt work properly
Be aware of the slot you are currently on
If youre flashing a ROM to a slot, make sure you also have the required firmware (abl, modem, and so on) in that slot
Infos:
System image/Vendor image and system/vendor are redundant, the image variants are direct copies of the partition (and also their size) while the others are "simply" files copied and repacked
How to use decrypted stock by @Xsavi : https://forum.xda-developers.com/lg-v40/how-to/guide-twrp-data-access-stock-t3970149
Metadata encryption TWRP requires 10 firmware to use properly, no guarantee for it to work on Pie firmware!
Download:
Metadata bootable: https://drive.google.com/file/d/1hdzeH3AIQVf3siQNsI27IS_vmghPESEG/view?usp=sharing + Install zip: https://drive.google.com/file/d/1CQUfg54zD838detcIJqdRiKXdVNtd6Iy/view?usp=sharing
Bootable: https://drive.google.com/open?id=1UnIFbJlXHl6x4azq6H6yS-PRfk-omdTP
Old: https://drive.google.com/open?id=1p3IrbeOxM4ay01JccyifWDuxqqrE0_Dl
Sources:
device tree: https://github.com/SGCMarkus/android_device_lge_judypn-twrp/tree/android-9.0
kernel: https://github.com/SGCMarkus/android_kernel_lge_sdm845/tree/lge-pie-v409-20a
XDA:DevDB Information
TWRP for Judypn, ROM for the LG V40
Contributors
SGCMarkus
ROM OS Version: 9.x Pie
Version Information
Status: Alpha
Created 2019-09-20
Last Updated 2019-09-20
Hmm interesting I see ?
Wow. The V40 got TWRP too. Awesome.
Wooo new twrp! Great work Markus!
How hard would it be to get this working on the V35? I can get it to install and boot into recovery, but it does not register touch input.
Well, having a big issue. I installed TWRP, Install custom rom w/ twrp inject, reboot menu, selected the slot where the rom, restarted, no TWRP, No root, but custom rom and now it comes up as unknown in LG UP so I can try to fix it. I think its mostly a brick since I can't do anything. No Fastboot either because im in slot b and cant switch because no root or fastboot.
lowridincrew said:
Well, having a big issue. I installed TWRP, Install custom rom w/ twrp inject, reboot menu, selected the slot where the rom, restarted, no TWRP, No root, but custom rom and now it comes up as unknown in LG UP so I can try to fix it. I think its mostly a brick since I can't do anything. No Fastboot either because im in slot b and cant switch because no root or fastboot.
Click to expand...
Click to collapse
did you have pie firmware also in the slot where you installed LOS to?
otherwise.... nothing is ever really a brick, you still have 9008 mode as last option
Fixed. Case of the bad drivers. LGUP didn't wanna read so I went to a different computer. Read it through LGUP, flashed Stock, rebooted to recovery, TWRP popped up.
How do the two slots work? I thought that these were for current ROM in one and then new ROM in the other, alternating with each ROM update. Why is one for the ROM and the other holding system partition additions? I would expect gapps to integrate into both A and B sides at once on top of each ROM...
Is there documentation on this?
So I'm bootloader unlocked, rooted on pie and cannot access fastboot. How do I go about installing twrp?
EDIT: tried different USB-C cables and one worked like a charm.
seacrow01 said:
So I'm bootloader unlocked, rooted on pie and cannot access fastboot. How do I go about installing twrp?
Click to expand...
Click to collapse
What happens if you try and access the bootloader aka the fastboot...
Ainz_Ooal_Gown said:
What happens if you try and access the bootloader aka the fastboot...
Click to expand...
Click to collapse
Nothing, phone just reboots like nothing is there. neither the button combo nor the "adb reboot bootloader" command works.
So I got on of the US models unlocked bootloader Verizon I got fastboot can I flash this one to my 405ua verizon?
In fastboot i see Judypn But I believe they flashed a open Korean on mine Im trying to get back to US firmware twrp and magisk if at all possible
Well I can confirms this works for pie on a 405ua unlocked bootloader...Nice work mate...
After reading through a bit and playing around. I got recovery installed on ramdisk recovery. Got out of my bootloop by fastboot flashing stock boot img from my current firmware. I did notice slot b I still have stock recovery which helped getting out of the failed encryption loop. And I also have download mode there.
How to unlock bootloader in indian firmware????
why i cannot enter fastboot mode on my lg v40 v405UM with android pie. When i command adb reboot bootloader it goes to restart phone.Not enter fastboot mode. Please help me.Sorry for my english
Hi anyone can help me after flashing twrp my phone doesnt reboot or does it take long to boot after flashing twrp
lowridincrew said:
Fixed. Case of the bad drivers. LGUP didn't wanna read so I went to a different computer. Read it through LGUP, flashed Stock, rebooted to recovery, TWRP popped up.
Click to expand...
Click to collapse
What drivers did you use? I can't get my LGUP to recognize the device. I'm trying to flash stock back to a working copy of Lineage 16 with twrp.
Broken:
LGs encryption on Stock
encryption on other ROMs(?)
exFat for external SDs
Does this mean just within recovery or within Pie?.... The exFat part, that is
xaxxelous said:
Broken:
LGs encryption on Stock
encryption on other ROMs(?)
exFat for external SDs
Does this mean just within recovery or within Pie?.... The exFat part, that is
Click to expand...
Click to collapse
Both, as pie uses the same kernel as TWRP when booted
Original thread.
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software. *This is not entirely true for Realme devices since bootloader unlock or custom rom flash via TWRP or fastboot does not void your warranty but rooting does.
* So I heard. But that's question of detail.
* Same statement for XDA.
[DETAILED DESCRIPTION]:
I've spent my whole afternoon testing. And found out there are way more well made gsi roms out there and theoretically all of them should work. First, you gotta read this one. Then pick a gsi rom. I recommend one that has everything (must be AB image) since we don't have a working twrp yet thus can't flash opengapps but if the image file contains it then it's good to go. Go there. Pick one. Make sure it has ab-gapps-su in it's name meaning it's A/B partition dependent treble rom. Gapps means it has gapps ofc. Su means it has built in superuser (that you can ignore later for you'll be replacing it with Magisk naturally). After picking a gsi rom image successfully you can download it to your external sd card and flash it via twrp (yes, that half ass twrp for rmq provided on xda) or you can flash it via fastboot flash system system.img. Wiping data, cache, dalvik, system is necessary before doing so. Also formatting data in twrp after flashing the system image helps a lot just as OP said. If you want to try out other gsi roms you must flash stock vendor image file and do the flashing circle again. If you don't flash stock rom or stock vendor img before doing so your new gsi rom won't be able to work with screen lock. At least that's what I got on 4 different gsi roms. And one more thing. These gsi systems doesn't seem to support exfat file system. Meaning they'll want to format your external sd card. This can by bypassed if you flash lineage os boot.img. And then Magisk and at last modified vbmeta.img for RMQ. That file will make realme vendor think nothing is changed and won't try to fck you over with recovery destroyed issue.
[Prerequisites]:
unlocked bootloader
twrp recovery
External SD card
[BUGS]:
Face unlock and fingerprint isn't present on gsi roms which means they cannot work
Screen lock issue in cases when you don't flash stock vendor.img before migrating from one custom rom, be it gsi or zip to system gsi.img
[STEP BY STEP TUTORIAL IN CASE YOU'RE COMING FROM OTHER ROM]:
!! Most of these steps are precaution !!
Read these points carefully to have a basic knowledge what you're about to do
Pick a gsi image of your choice (official Android 9 Pie, especially AOSP is highly advised)
Put your image file onto your external SD card for your internal one will likely be erased
You should grab the appropriate vendor.img and boot.img files for your device by decompressing the 7z files
Get the modified vbmeta.img file for spoofing system to boot
Get Magisk
Get SuperSu remover(Beware! It also removes Magisk if installed)
Get Lineage OS boot.img
It's better to be safe than sorry so you better download whole rom package too
Put all these files onto your external SD card
Make sure you have your twrp recovery on your external SD card too
If you done everything well you should have these on your external SD: twrp, desired system gsi.img as AB variant, your vendor.img, modified vbmeta.img, stock boot.img, Lineage OS boot.img, color os flashable.ozip/zip, Magisk, SuperSu remover
Wipe system, data, dalvik, cache
Flash stock vendor.img as vendor
Flash system gsi.img as system
Flash lineage os boot.img as boot
Flash twrp.img as recovery
Flash modified vbmeta.img as vbmeta
Reboot to system (if the device reboots into recovery you'll have to format data sadly)
After reboot successful and you've done the initial google setup steps reboot to recovery and flash superuser unroot
Flash Magsik
Reboot, now you should have a working aosp like system as I do
[STEP BY STEP TUTORIAL IN CASE YOU'RE COMING FROM COLOR OS]:
!! You could have the same files as above just to make sure but system gsi.img,vbmeta.img,SuperSu remover,Magisk and Lineage OS boot.img should be enough if everything goes as planned and system boots for first try !!
Read the frequently asked questions, step one previously
Get your desired system gsi.img
Put your system gsi.img, twrp.img, Magisk, SuperSu remover, vbmeta.img, Lineage OS boot.img onto your external SD card
Wipe data, system, cache, dalvik
Flash system gsi.img as system
Flash lineage os boot.img
Flash twrp.img as recovery
Flash vbmeta.img ad vbmeta
Reboot (if reboots to recovery you have to format data) then do the Android setup
Reboot to recovery
Flash SuperSu remover.zip
Flash Magisk.zip
Reboot
Now your device should have successfully booted up
In case the gsi rom would be stuck on boot logo then you may reboot back to recovery by holding down volume up + power button and flash permissiver_v5.zip. It helped me boot Pixel Experience gsi rom.
Update.:
As you already know development on realme devices suck beacuse of ****ty or incomplete sources, lack of developers interest and biggest reason is lack of community support.
Our man here @BabluS is a legendary developer of Asus Zenfone Max M1 Pro and is willing to compile stable ROMs for our device. But, he needs some donations to buy the device. He has already compiled Android 10 (PE) for our device which is 99% stable. To continue this tremendous work he needs to have the device in hand.
Reasons To Donate:
1. Official PixelExperience ROM
2. Official POSP ROM
3. Will maintain & provide public Device Trees/Sources (So anyone can compile ROMs)
4. More development for realme 5 Pro
Name : Baswanth Madhav Saladi
Donate Using UPI: [email protected]
Donate using Paypal : [email protected]
Send screenshots of payment to @orgasmtron
We have to reach 6-7k in total out of which we have collected 2.6k..
Keep donating & get closer to stable custom ROM experience. Kudos!
All the donations will be public.Anyone can view and verify them.All details will be transparent.
NOTE:
We will update money collection daily evening. All details will be transparent.
List of Donators will get updated here
CLICK HERE TO CHECK!
Has anybody got Android 10 working properly?
tonibm19 said:
Has anybody got Android 10 working properly?
Click to expand...
Click to collapse
Yes. Method is same.
greenys' said:
Yes. Method is same.
Click to expand...
Click to collapse
Yeah but I mean, everything is working fine?
Fingerprint? Camera?
tonibm19 said:
Yeah but I mean, everything is working fine?
Fingerprint? Camera?
Click to expand...
Click to collapse
Dunno. As I said I never tried Android Q. But I presume fingerprint is missing and I'm quite sure no 48mp camera is present either.
What GSI File for Realme 5 Pro
what type GSI Image for Realme 5 pro, A or AB type?
Tegarcs142 said:
what type GSI Image for Realme 5 pro, A or AB type?
Click to expand...
Click to collapse
AB. On Android 9 and above you must use AB variant. It doesn't matter whether or not does your device use seamless updates. If you try to flash A only variant your device won't boot.
I installed GSI resurrection remix on my Realme 5 Pro and when I trying install Gapps get error not enough system partition. So I use resize file system in twrp and it worked.
Tegarcs142 said:
I installed GSI resurrection remix on my Realme 5 Pro and when I trying install Gapps get error not enough system partition. So I use resize file system in twrp and it worked.
Click to expand...
Click to collapse
Nice. Which twrp did you use?
greenys' said:
Nice. Which twrp did you use?
Click to expand...
Click to collapse
3.3.1-0
Tegarcs142 said:
... So I use resize file system in twrp and it worked.
Click to expand...
Click to collapse
Hi, can you please tell me what option you clicked for resizing the system partition?
the steps you did.
I tried doing that but don't find the option in TWRP.
For better experience with using gsi make sure to check Screenshot resolution if it's lower than our Device
Change Resolution :
1) download termux app
https://play.google.com/store/apps/d...?id=com.termux
2) run commands:
su
wm size 1080x2340
3) reboot*device
Enjoy better experience with gsi
greenys' said:
Original thread.
[DETAILED DESCRIPTION]:
I've spent my whole afternoon testing. And found out there are way more well made gsi roms out there and theoretically all of them should work. First, you gotta read this one. Then pick a gsi rom. I recommend one that has everything (must be AB image) since we don't have a working twrp yet thus can't flash opengapps but if the image file contains it then it's good to go. Go there. Pick one. Make sure it has ab-gapps-su in it's name meaning it's A/B partition dependent treble rom. Gapps means it has gapps ofc. Su means it has built in superuser (that you can ignore later for you'll be replacing it with Magisk naturally). After picking a gsi rom image successfully you can download it to your external sd card and flash it via twrp (yes, that half ass twrp for rmq provided on xda) or you can flash it via fastboot flash system system.img. Wiping data, cache, dalvik, system is necessary before doing so. Also formatting data in twrp after flashing the system image helps a lot just as OP said. If you want to try out other gsi roms you must flash stock vendor image file and do the flashing circle again. If you don't flash stock rom or stock vendor img before doing so your new gsi rom won't be able to work with screen lock. At least that's what I got on 4 different gsi roms. And one more thing. These gsi systems doesn't seem to support exfat file system. Meaning they'll want to format your external sd card. This can by bypassed if you flash lineage os boot.img. And then Magisk and at last modified vbmeta.img for RMQ. That file will make realme vendor think nothing is changed and won't try to fck you over with recovery destroyed issue.
[Prerequisites]:
unlocked bootloader
twrp recovery
External SD card
[BUGS]:
Face unlock and fingerprint isn't present on gsi roms which means they cannot work
Screen lock issue in cases when you don't flash stock vendor.img before migrating from one custom rom, be it gsi or zip to system gsi.img
[STEP BY STEP TUTORIAL IN CASE YOU'RE COMING FROM OTHER ROM]:
!! Most of these steps are precaution !!
Read these points carefully to have a basic knowledge what you're about to do
Pick a gsi image of your choice (official Android 9 Pie, especially AOSP is highly advised)
Put your image file onto your external SD card for your internal one will likely be erased
You should grab the appropriate vendor.img and boot.img files for your device by decompressing the 7z files
Get the modified vbmeta.img file for spoofing system to boot
Get Magisk
Get SuperSu remover(Beware! It also removes Magisk if installed)
Get Lineage OS boot.img
It's better to be safe than sorry so you better download whole rom package too
Put all these files onto your external SD card
Make sure you have your twrp recovery on your external SD card too
If you done everything well you should have these on your external SD: twrp, desired system gsi.img as AB variant, your vendor.img, modified vbmeta.img, stock boot.img, Lineage OS boot.img, color os flashable.ozip/zip, Magisk, SuperSu remover
Wipe system, data, dalvik, cache
Flash stock vendor.img as vendor
Flash system gsi.img as system
Flash lineage os boot.img as boot
Flash twrp.img as recovery
Flash modified vbmeta.img as vbmeta
Reboot to system (if the device reboots into recovery you'll have to format data sadly)
After reboot successful and you've done the initial google setup steps reboot to recovery and flash superuser unroot
Flash Magsik
Reboot, now you should have a working aosp like system as I do
[STEP BY STEP TUTORIAL IN CASE YOU'RE COMING FROM COLOR OS]:
!! You could have the same files as above just to make sure but system gsi.img,vbmeta.img,SuperSu remover,Magisk and Lineage OS boot.img should be enough if everything goes as planned and system boots for first try !!
Read the frequently asked questions, step one previously
Get your desired system gsi.img
Put your system gsi.img, twrp.img, Magisk, SuperSu remover, vbmeta.img, Lineage OS boot.img onto your external SD card
Wipe data, system, cache, dalvik
Flash system gsi.img as system
Flash lineage os boot.img
Flash twrp.img as recovery
Flash vbmeta.img ad vbmeta
Reboot (if reboots to recovery you have to format data) then do the Android setup
Reboot to recovery
Flash SuperSu remover.zip
Flash Magisk.zip
Reboot
Now your device should have successfully booted up
In case the gsi rom would be stuck on boot logo then you may reboot back to recovery by holding down volume up + power button and flash permissiver_v5.zip. It helped me boot Pixel Experience gsi rom.
Click to expand...
Click to collapse
Hi
I wanna install fortnite on RMQ
Through epic games I should register a realme account (but I can do that only with a Chinese phone number which I don't have )
Any solution pls
Tarikooo said:
Hi
I wanna install fortnite on RMQ
Through epic games I should register a realme account (but I can do that only with a Chinese phone number which I don't have )
Any solution pls
Click to expand...
Click to collapse
Wth no. Idk. It's not even a gsi related thing. I have no idea sorry.
hi guys i tried flashing havoc 3.0 gsi, and it works great. which one gapps should i use?
Does fingerprint and face unlock work?
This method worked on global rm5p.
I tried to flash the GSI Miui Erfan, but when entered in the initial settings, the screen cannot be touched.
Salmankapuas said:
I tried to flash the GSI Miui Erfan, but when entered in the initial settings, the screen cannot be touched.
Click to expand...
Click to collapse
Don't bother with miui. Only aosp or caf.
i flashed GSI rom, pixel, OxygenOS but the system cannot boot, only stuck on boot loading screen, is that normal?? how do i fix it?
Android 13 for Xperia XZ Premium
Code:
/*
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
What's AOSP?
AOSP is Android as Google publish without any modifications. .
What's working :
Boots
Bluetooth
Fingerprint
Wi-Fi
Camera
Camcorder
Video Playback
Audio
Sensors
Flash
GPS
Encryption
Offline Charging
Whats not working?
Notification LED
IMS/VOLTE
Half Screen issue(For some users) - Need testing if still persist
Test and Report(with logcat)
Instructions to install up ROM :
Flash latest available Stock ROM(47.2.A.10.107) and boot into it once.
Reboot to Fastboot
Download the OEM Image from HERE, Extract and Flash it. (V5B)
fastboot flash oem SW_binaries_for_Xperia_Android_11_4.14_v5b_yoshino.img
Flash the userdata,boot and system image (Will wipe all the userdata).
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash system system.img
Install Magisk/Gapps(Optional).
Reboot
Downloads :
G8142 : https://sourceforge.net/projects/xzp/files/SODP13/android-13.0.0_r2/G8142/
G8141 : https://sourceforge.net/projects/xzp/files/SODP13/android-13.0.0_r2/G8141/
Kernel Source Code: https://github.com/sonyxperiadev/kernel
Changelog :
08/18/2022 :
Initial release for G8142
08/19/2022:
Initial release for G8141
08/22/2022
Notification LED Fixed
Switched to custom lights hal
Kernel upstreamed to 4.14.260
Good
support gcam?
Markutthel said:
support gcam?
Click to expand...
Click to collapse
It does, you need to find the compatible one.
Shujath said:
It does, you need to find the compatible one.
Click to expand...
Click to collapse
okeyy thx my bruhh
mmmmm,how to raw support?
ooh, brilliant. Unfortunately I have single SIM/8184.
I still have to wait. I am really happy about it.
Can you provide GAAPs and TWRP recovery? Link?
Gordon1979 said:
ooh, brilliant. Unfortunately I have single SIM/8184.
I still have to wait. I am really happy about it.
Can you provide GAAPs and TWRP recovery? Link?
Click to expand...
Click to collapse
Mostly tomorrow, I will share the single sim versions.
Sure, will share the links and steps to install gapps too ..
Great work!
Alright, Links for Single sim variant are up.
Steps to install GAPPS :
Install the attached recovery via fastboot
fastboot flash recovery recovery.img
Boot into recovery mode by pressing and holding power button and volume down button at the same time.
Sideload the gapps or install it from SD card as it cannot decrypt the internal storage yet.
I am using Litegapps (https://sourceforge.net/projects/litegapps/files/litegapps/arm64/33/lite/v2.6/) (Recovery version).
Flash the Gapps and the attached fix for gapps(REQUIRED).
Reboot
other GAAPs for Android 13 cannot be found.
Or does GAAPs for Android 12L work too ?
Gordon1979 said:
other GAAPs for Android 13 cannot be found.
Or does GAAPs for Android 12L work too ?
Click to expand...
Click to collapse
Litegapps are the only one I found currently.
a13 is very in very early stage and other gapps will adapt to it soon.
Do you know if it is possible to install GAAPs12 on Android 13?
Gordon1979 said:
Do you know if it is possible to install GAAPs12 on Android 13?
Click to expand...
Click to collapse
I dont think so....
Litegapps 14, is this for Android 14???
LiteGapps - Browse /litegapps/arm64/34/lite/v2.6 at SourceForge.net
LiteGapps is a custom gapps which is ,small, friendly and complete.
sourceforge.net
Gordon1979 said:
Litegapps 14, is this for Android 14???
LiteGapps - Browse /litegapps/arm64/34/lite/v2.6 at SourceForge.net
LiteGapps is a custom gapps which is ,small, friendly and complete.
sourceforge.net
Click to expand...
Click to collapse
Yes lol :d
@Shujath
After the install, no recovery comes from the device.
Factory reset not possible
I can't restore my APPs, SMS, ..... everything.
Can you remove the search bar on the homescreen?
The display on/off in seconds cycle is also there.
how to flash i don't understand
Flash latest available Stock ROM(47.2.A.10.107) and boot into it once.
Reboot to Fastboot
fastboot flash oem SW_binaries_for_Xperia_Android_11_4.14_v5b_yoshino.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
Boot into recovery mode by pressing and holding power button and volume down button at the same time.
go in to Sideload
flash over PC , Litegapps
Flash the Litegapps fix over TWRP
Reboot
ROM Updated :
22nd Aug'22
Changelog :
Notification LED Fixed
Switched to custom lights hal
Kernel upstreamed to 4.14.260
Download links in first post.