Note:
Please take full twrp backup of your phone before you proceed with the below steps
Steps to Flash GSI:
You can follow one of the two methods to flash GSI in Realme 3
Fastboot Method:
1. Install TWRP:
Follow this guide on installing TWRP on your phone:
https://forum.xda-developers.com/realme-3/development/screen-doesnt-twrp-realme-3-t3944022
2a. Commands to execute in fastboot mode:
fastboot erase system
fastboot flash system name_of_system.img
fastboot -w
fastboot reboot
TWRP Method:
1. Install TWRP:
Follow this guide on installing TWRP on your phone:
https://forum.xda-developers.com/realme-3/development/screen-doesnt-twrp-realme-3-t3944022
2. Copy system.img file to your sdcard.
3. Boot your phone to TWRP.
4. Press Install - > Install Image button -> Select the System.img file -> Select System Image-> Swipe to Flash
5. Format Data and then Wipe Cache, Dalvik Cache
6. Reboot, Done.
I used gsi from here (use aosp_arm64, download aosp_arm64-img.zip from artifacts tab and extract and flash system.img only):
https://ci.android.com/builds/branches/aosp-pie-gsi/grid
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Incase you want to go back to stock follow the same process and flash stock system.img instead of gsi system.img
stock system image: https://www.androidfilehost.com/?fid=1395089523397966778
GSI List(use ARM64 AB or A/B images):
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
ADB Installer tool: https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445
what Custom rom did you user sir ?
jeffalaiza said:
what Custom rom did you user sir ?
Click to expand...
Click to collapse
AOSP
fawazahmed0 said:
AOSP
Click to expand...
Click to collapse
can i flash the gsi rom in gsi list of a-only partition ?
jeffalaiza said:
can i flash the gsi rom in gsi list of a-only partition ?
Click to expand...
Click to collapse
You have to use ab gsi for realme 3 phone, but if you are downloading from ci.android.com, use aosp_arm64
fawazahmed0 said:
AOSP
Click to expand...
Click to collapse
can i use this rom for daily driver that less of bugs ?
myeganz said:
can i use this rom for daily driver that less of bugs ?
Click to expand...
Click to collapse
I have not used that aosp gsi for much time, so not sure whether it is good for daily usage or not.
You can give it a try and see
What the meaning of veritydecrypt?
jeffalaiza said:
What the meaning of veritydecrypt?
Click to expand...
Click to collapse
Its a file ,link is there in the OP,
https://www.androidfilehost.com/?fid=6006931924117905745
How can i know my device use A,B, or AB ?
Link A.14 .ozip
@fawazahmed0 please link a.14 ozip file? thanks
My baseband becomes unknown (no network signal) everytime I flash disable-dm-verity.
---------- Post added at 02:45 AM ---------- Previous post was at 02:37 AM ----------
krimstix01 said:
My baseband becomes unknown (no network signal) everytime I flash disable-dm-verity.
Click to expand...
Click to collapse
Fixed it lol. Just run
Code:
fastboot erase nvram
fastboot erase nvdata
After flashing any rom i lost my cellular network did not showed sim card, i tried to flash stock back, but it was same,
I tried doing fastboot erase nvdata and nvram, now it recognises sim but no network coverage. Is there something I'm missing?
krimstix01 said:
My baseband becomes unknown (no network signal) everytime I flash disable-dm-verity.
---------- Post added at 02:45 AM ---------- Previous post was at 02:37 AM ----------
Fixed it lol. Just run
Code:
fastboot erase nvram
fastboot erase nvdata
Click to expand...
Click to collapse
android Q ba yung GSI na to bro?
(This problem is solved now, it's just for future reference)
Hi, I just came to know that Disable_Dm-Verity_ForceEncrypt.zip by @Zackptg5, was causing null imei or no network issue (I have raised an issue at github for this), if you have backup of nvdata, then go to fastboot mode and do:
fastboot flash nvdata nvdata.img
I know most of the guys will not have that backup.
I tested the Disable_Dm-Verity_ForceEncrypt.zip, when my phone didn't have sim cards in it. So I never came to know about the sim problem. I am really sorry for you guys.
And one more thing, some people are suggesting to do:
fastboot erase nvram
fastboot erase nvdata
NEVER DO THAT, I REPEAT NEVER DO THAT
you are erasing the partitions, then the phone will never recover.
Thats why it is very important to take complete twrp backup of all partitions. (currently there is no twrp for realme3 which allows backup for all partitions)
So I request twrp, pbrp etc developers to modify their device tree fstab to include all the partitions in this phone and also add backup flag for all partitions (also include preloader partitions)
Here is the list of all partitions in realme 3
https://www.androidfilehost.com/?fid=6006931924117922953
For those guys who have erased their nvram and nvdata partitions, please go to service center, nothing much can be done from my side , maybe someone else can help you out.
So, guys who are having network issue after flashing Disable_Dm-Verity_ForceEncrypt.zip and have not erase their nvram and nvdata, please do the following:
1. boot to custom recovery (twrp, pbrp etc)
2. connect your phone to pc/laptop
3. execute these commands:
adb shell mkdir test
adb shell mount /dev/block/by-name/nvdata test
adb shell chcon ubject_r:nvdata_file:s0 /test/fstab.mt6771
adb shell reboot
fawazahmed0 said:
Hi, I just came to know that Disable_Dm-Verity_ForceEncrypt.zip by @Zackptg5, was causing null imei or no network issue (I have raised an issue at github for this), if you have backup of nvdata, then go to fastboot mode and do:
fastboot flash nvdata nvdata.img
I know most of the guys will not have that backup.
I tested the Disable_Dm-Verity_ForceEncrypt.zip, when my phone didn't have sim cards in it. So I never came to know about the sim problem. I am really sorry for you guys.
And one more thing, some people are suggesting to do:
fastboot erase nvram
fastboot erase nvdata
NEVER DO THAT, I REPEAT NEVER DO THAT
you are erasing the partitions, then the phone will never recover.
Thats why it is very important to take complete twrp backup of all partitions. (currently there is no twrp for realme3 which allows backup for all partitions)
So I request twrp, pbrp etc developers to modify their device tree fstab to include all the partitions in this phone and also add backup flag for all partitions (also include preloader partitions)
Here is the list of all partitions in realme 3
https://www.androidfilehost.com/?fid=6006931924117922953
For those guys who have erased their nvram and nvdata partitions, please go to service center, nothing much can be done from my side , maybe someone else can help you out.
So, guys who are having network issue after flashing Disable_Dm-Verity_ForceEncrypt.zip and have not erase their nvram and nvdata, please do the following:
1. boot to custom recovery (twrp, pbrp etc)
2. connect your phone to pc/laptop
3. execute these commands:
adb shell mkdir test
adb shell mount /dev/block/by-name/nvdata test
adb shell chcon ubject_r:nvdata_file:s0 /test/fstab.mt6771
adb shell reboot
Click to expand...
Click to collapse
Is magisk root now stable?
yametekudasai said:
Is magisk root now stable?
Click to expand...
Click to collapse
yeah
Does anyone try to flash Havoc Os? It's stable or not ? And does Bluetooth,Fingerprint,... work well? Or you have tried to flash another gsi rom is stable, please share.
my realme 3 1821 is only black screen .. can you tell me why?
Tấn Ho said:
Does anyone try to flash Havoc Os? It's stable or not ? And does Bluetooth,Fingerprint,... work well? Or you have tried to flash another gsi rom is stable, please share.
Click to expand...
Click to collapse
I tried many GSI ROMs, but VoLTE and Fingerprint works in none of them, execept for these two, everything else seems to work, in Havoc OS atleast
Related
Presenting the TWRP Recovery for Asus Zenfone Lite L1 (ZA551KL) (asus_x00r)(Treble Supported)(Encryption Fixed) Disclaimer : I am not responsible for any bricked device, all responsibility bears the user.
First Unlock Boot-loader using official asus ubl tool - Download UBL App
Team Win Recovery Project (TWRP) is the most famous custom recovery used by the people who like to flash custom roms, patches, flashable zips etc. The latest version is TWRP 3.2.3-0.
Flash zips through otg or Micro sd Cards as device is encrypted , if you format data and decry-pt then the Flashlight (torch) and the Camera will not Work.ENCRYPTION IS FIXED NOW
Installation By PC
1. Install fastboot tools - minimal adb and fastboot
2. Download twrp image and rename it as "twrp.img", then copy it to the Minimal ADB and Fastboot folder
3. Boot the device to fastboot mode - press and hold power button and volume down button
4. Connect device to pc
5. Open command prompt from Minimal ADB and Fastboot
6. Run command " fastboot flash recovery twrp.img "
7. Twrp will be flashed immediately
8. To boot in to twrp run " fastboot boot twrp.img " or disconnect device from pc and press and hold power button and volume up button
9. Device will be booted to twrp
NOW LETS DECRY-PT DATA
*Download the data Decrypt patch Zip :- Download
*Put it in otg (pendrive) or microsd card
*Then in twrp , Go to wipe section in twrp and tap on Format data (Important )
*Do not wipe data partiton , you have to format it
*then flash the Decrypt zip from your sdcard or pendrive
*after flashing wipe caches
*then reboot , and see camera and flashlight is working and Storage in Decrypted
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Join telegram group for updates
Downloads:-
1. Minimal Fastboot and Adb
2.TWRP_3.2.3.0_asus_lite_l1
3. Decrypt Patch Download
Device tree
Credits:
@Ashish Gupta1999 (me)
Tester - for testing a lot of builds time to time
if you like my work you can donate me also
Dose it support g cam portrait mode
Yes works fantastic(front cam)
Doesn't work for me. Anyone have a working root method for Asus zenfone live L1?
dexx121 said:
Doesn't work for me. Anyone have a working root method for Asus zenfone live L1?
Click to expand...
Click to collapse
Live l1 and lite l1 is a completely different devices
This TWRP actually partially works for Live L1 (ZA550KL, SD425). The problems are 1) it can't decrypt /data, 2) it fails to mount /xrom (which is inexistent on the Go variant) and 3) no ADB/MTP, but for flashing ROMs/addons, backing up and restoring, it works nicely. Just letting y'all know about it.
AndyYan said:
This TWRP actually partially works for Live L1 (ZA550KL, SD425). The problems are 1) it can't decrypt /data, 2) it fails to mount /xrom (which is inexistent on the Go variant) and 3) no ADB/MTP, but for flashing ROMs/addons, backing up and restoring, it works nicely. Just letting y'all know about it.
Click to expand...
Click to collapse
there is a specific twrp for live l1
Ashish Gupta1999 said:
there is a specific twrp for live l1
Click to expand...
Click to collapse
Can you link me to the one you know of? I just found another one from TWRP Builder, and it did fix most problems, but I still can't use decrypted data (shows "encryption unsuccessful" on boot). And it doesn't expose /vendor either which is a small letdown. <- Fixed by unpacking and editing recovery.fstab.
AndyYan said:
Can you link me to the one you know of? I just found another one from TWRP Builder, and it did fix most problems, but I still can't use decrypted data (shows "encryption unsuccessful" on boot). And it doesn't expose /vendor either which is a small letdown. <- Fixed by unpacking and editing recovery.fstab.
Click to expand...
Click to collapse
Contact me on telegram @yoursenpai1 i will provide you there
it works
Ashish Gupta1999 said:
Contact me on telegram @yoursenpai1 i will provide you there
Click to expand...
Click to collapse
Something gone wrong. System in boot loop. Able to load TWRP through PC. Tried to flash a new ROM but only 2 options (Boot & Recovery) available. Please help
Abhicr said:
Something gone wrong. System in boot loop. Able to load TWRP through PC. Tried to flash a new ROM but only 2 options (Boot & Recovery) available. Please help
Click to expand...
Click to collapse
All I know there is no rom for this device as of now , if you flash a gsi , it. Will definitely show system image option , for now flash stock rom using stock recovery to unbrick
Ashish Gupta1999 said:
All I know there is no rom for this device as of now , if you flash a gsi , it. Will definitely show system image option , for now flash stock rom using stock recovery to unbrick
Click to expand...
Click to collapse
I used a GSI to update from Oreo to Pie. But the TWRP has only 2 options (boot & Recovery) to flash the .img file. However, I did a restore & back with the old Oreo. I want to upgrade my Asus Lite 1 to Pie!! Is there any possibility to get the mobile back to the factory state including recovery? So, that I can begin from one.
Abhicr said:
I used a GSI to update from Oreo to Pie. But the TWRP has only 2 options (boot & Recovery) to flash the .img file. However, I did a restore & back with the old Oreo. I want to upgrade my Asus Lite 1 to Pie!! Is there any possibility to get the mobile back to the factory state including recovery? So, that I can begin from one.
Click to expand...
Click to collapse
Well there is a fastboot rom available in my telegram channel of lite l1 check in there
Accidentally deleted the OS and now the mobile isn't even switching on. Any solution for this? Anyway I can install an OS ?
My mobile is ASUS Zenfone Lite L1.
WARNING: We are not responsible to any damage you might have done to your device. Always follow the instructions CAREFULLY.
This thread is about flashing custom roms properly on your Redmi Note 9, specifically Redmi 10x 4g (Merlin). Make sure you've backup everything (Files, Apps etc) since it includes wiping your entire internal storage.
PRE-REQUISITE:
1. MIFLASH TOOL:
Download Xiaomi Flash Tool - Official Xiaomi Mi Flash Tool Download
Download Xiaomi Flash tool is for Xiaomi smartphone and tablet device users that runs on Windows PC platforms to flash fastboot firmware files on Xiaomi smartphones. All versions of Xiaomi Mi Flash Tool download is available here
xiaomiflash.com
2. XIAOMI UNSIGNED DRIVERS (HIGHLY RECOMMENDED):
xiaomi_usb_driver.rar
drive.google.com
Check this site first for more info about it:
https://c.mi.com/thread-3312019-1-0.html
3. SP FLASH TOOL (FOR BACKING UP THE IMEI):
SP Flash Tool for Windows (all versions)
SP Flash Tool for Windows enables users to flash Stock Firmware (ROMs), unbrick bricked devices, upgrade or downgrade their operating system, and perform advanced tasks like memory testing and parameter editing.
spflashtools.com
For a clear instructions on backing up the IMEI:
4. ADB and Fastboot drivers:
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
5. MTK Drivers (Recommended)
MTK_driver
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
6. Xiaomi Fastboot Rom (Indonesia version)
NOTE: Choose wisely since it requires one of the given fastboot roms to be installed for a specific reason:
a. Xiaomi Redmi note 9 Indonesia (ID) Fastboot ROM MIUI V12.0.1.0.QJOIDXM (Required for installing Custom Roms such as Pixel Experience, LIneageOS etc)
Download Redmi 10X 4G / Note 9 (merlin) V12.0.1.0.QJOIDXM MIUI 12 Stable Full Rom | XiaomiROM.com
The Stable update V12.0.1.0.QJOIDXM has been officially released for Redmi 10X 4G / Note 9 (codename is merlin). Before updating, please make sure you …
xiaomirom.com
b. Xiaomi Redmi note 9 Indonesia (ID) Fastboot ROM MIUI V11.0.2.0.QJOIDXM (For installing ports by Communos such as ShapeshiftOS, Bliss etc.)
Download Redmi 10X 4G / Note 9 (merlin) V11.0.2.0.QJOIDXM MIUI 11 Stable Full Rom | XiaomiROM.com
The Stable update V11.0.2.0.QJOIDXM has been officially released for Redmi 10X 4G / Note 9 (codename is merlin). Before updating, please make sure you …
xiaomirom.com
INSTRUCTIONS:
Flash Indonesian fastboot rom on a Global Variant via ADB and Miflash
Turn off phone and reboot to fastboot. Connect the said device to PC.
In PC, run cmd-here.exe in the adb directory and enter:
fastboot reboot fastboot
//.(this will take you to fastbootD where you can access the "super" partition consisting of:
system.img
vendor.img
product.img ).//
fastboot erase system
fastboot erase vendor
fastboot reboot bootloader to enter bootloader
Make sure you backup the IMEI to ensure safety before flashing via SP Tools.
Download an Indonesian fastboot rom from source then flash it to phone via MIFlash. (Recommend: 12.0.1 or lower)
After flashing, reboot the device and viola, you've got an Indonesian version of the MIUI to your Global Variant Device.
Flashing TWRP on a Redmi Note 9
Download the said recovery from this link below
"https://drive.google.com/uc?id=1TPdi1UGf_kUxFOdTl3u8xY5h-aQUDz9h&export=download"
Reboot device to bootloader and connect to PC.
In PC, run adb and type
"fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" (vbmeta from the indonesian fastboot rom, NOT from the Global fastboot rom)
"fastboot flash recovery recovery.img"
"fastboot reboot recovery"
After that, the recovery should be working.
FLASHING CUSTOM ROM (for 12.0.1.0) OR PORT (11.0.2.0)
Flashing a Custom Port.
Download a Custom Port from a telegram or the links provided below (made by Communos)
Bliss port
https://drive.google.com/uc?id=1wLAJkQvqS0A8EtNbOpGUdmo4oO0XZnl3&export=download
Lineage port
https://tdrive.elytra8.workers.dev/LineageOS%2017.1%20Port%20Merlin.zip
crDroid Port
Google Drive - Quota exceeded
drive.google.com
ShapeshiftOS port
https://drive.google.com/uc?id=1zQNHf67S8UQfgQT5qE0jtVIN2pDzjZnw&export=download
Then, connect phone to PC and copy your preferred rom to SDCard (Memory card is recommended).
Reboot your phone to recovery.
In TWRP, you have to wipe data, dalvik, cache and internal storage.
Select install and choose the rom from SDcard. Then, flash it.
Reboot your device.
Viola, you just installed a custom port or rom to your device.
Note: I will add more detail in the future but right now, if you have questions, please ask in this thread.
Special Thanks to:
@Communos
@VD171
You forgot fastboot reboot fastboot before fastboot erase system, it's an important step.
And before flashing the Port, you have to wipe data, dalvik, cache and internal in TWRP.
Would appreciate if credits are added in the guide.
[Q&A] [ Updated on 02-16-2021]
Q. My UI lags after I flashed these ports, what should I do?
A.
From Communos,
...
If your UI lags, place props_conf in internal storage,flash MagiskHide Props config module in magisk manager and reboot
Props conf link: https://drive.google.com/file/d/1g8B2DIsz-l7oDBYpUdi3dXUsEPU35H9s/view?usp=sharing
....
Click to expand...
Click to collapse
Q. Why do I need to flash these ports/ roms?
A.
From what I have seen, MIUI is very meticulous in secretly invading someone's privacy. This was said by @phhusson and @erfan that GSI Ports are more secure than MIUI.
Proof (Picture not mine, from twitter took by Communos)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
c.whoopee said:
Sorry about that. I fell asleep right before I put the credits and other details. my bad
Click to expand...
Click to collapse
The guide looks great now
Communos said:
The guide looks great now
Click to expand...
Click to collapse
Thanks, man... So anything that I would add?
c.whoopee said:
Thanks, man... So anything that I would add?
Click to expand...
Click to collapse
You can add the UI lag fix mentioned in the end of this post
Building Rom from Source for Redmi Note 9/10X Merlin
Hello guys, I was planning to build a rom from source so that we can start integrating different custom roms for our devices. I have a rig with good specs and a good internet connection too. What roms do you suggest to build? I was kinda...
forum.xda-developers.com
I booted into fastbootd then erased System , Vendor & Product then I booted to bootloader & flashed the Indonesia ROM Using Fastboot Then when I Reboot It stuck Into Bootlogo & Keeps Rebooting..
Note : I'm Still able to boot to Fastboot & Recovery
Help Pls..
Rhythm113 said:
I booted into fastbootd then erased System , Vendor & Product then I booted to bootloader & flashed the Indonesia ROM Using Fastboot Then when I Reboot It stuck Into Bootlogo & Keeps Rebooting..
Note : I'm Still able to boot to Fastboot & Recovery
Help Pls..
Click to expand...
Click to collapse
did you fixed it?
Jhon_Locke said:
did you fixed it?
Click to expand...
Click to collapse
Yes I switched to global again..
Hello, when doing inside fastboot
fastboot reboot fastboot
it reboots to TWRP instead.
What can be the cause?
0xSteeW said:
Hello, when doing inside fastboot
fastboot reboot fastboot
it reboots to TWRP instead.
What can be the cause?
Click to expand...
Click to collapse
I'm not sure, but I think you can't reboot to fastboot inside the fastboot.
Try
fastboot reboot bootloader
Nevermind, seems that TWRP implements user space fastboot (basically TWRP works as fastbootd when connected to the PC.
This can be verified with:
fastboot getvar is-userspace
0xSteeW said:
Nevermind, seems that TWRP implements user space fastboot (basically TWRP works as fastbootd when connected to the PC.
This can be verified with:
fastboot getvar is-userspace
Click to expand...
Click to collapse
TWRP, PBRP and other recovery projects are so essential than Magisk
Has anyone tried this method and got it working successfully? I want to know before going ahead.
yes,it is working perfectly
c.whoopee said:
Flashing TWRP on a Redmi Note 9
Download the said recovery from this link below
"https://drive.google.com/uc?id=1TPdi1UGf_kUxFOdTl3u8xY5h-aQUDz9h&export=download"
Click to expand...
Click to collapse
the link does not work
I second that: Link does not work; I tried TWRP for V11.0.4.0.QJOCNXM which is then stuck on bootscreen.
EDIT: Download working again and I just installed Lineage 18.1. Love you, guys!!
Apologies for the newbie (to flashing redmi devices) question but I can't get SP Flash tool to back up the IMEI. Drivers are all on, but when you plug in the phone to the USB cable nothing is read back. Do I need to have unlocked the bootloader before this works? I'm still waiting for mine to be allowed
The Xiaomi Unlock tool doesn't recognize the phone. I installed the drivers in the fist post of this thread, but still. Any idea?
Hi all. Can I backup the IMEI code using the scatter file from the Indonesian 12.0.1 ROM, or must I use the latest stock?
This manual will be useful for phones with Oxygen firmware, because very often they are get incremental updates and many users cannot install update with root, cannot find a stock boot, etc.
Also for those who want to unlock the bootloader at the first time and can save the persist patririon.
What are we need:
* MSMTools
* working fastboot
Let's start:
* reboot your phone in fastboot mode
* enter in cmd console
Code:
fastboot getvar current-slot
in that step we determine the current slot to extract the correct partitions
* start MSMTool program
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
* press F8 and you will see this windows
* choose right partitions (if your current slot are b, then choose for example boot_b, etc)
* in Password: field enter oneplus and press Ok
* if you make all right you will see that new button
* press on it, connect your phone and wait.
* selected images are saved on C:\
* profit
P.S. sorry for my english
Are you able to expand this tutorial on how to change partitions or on how to "update" msm so it uses a later version of OOS to unbrick the device?
The actual msm tool for OP9 Pro would install OOS11. But can it be changed to flash OOS12?
this tutorial only for how to extract partitions. android 11, 12, coloros, no matter.
for others can't help you
This part was empty for me:
Command "Fastboot devices" was working..
The tutorial in the first post is somewhat misleading. Fastboot is needed to flash back the partitions. In order for the partitions to be secured with the MSM tool, the phone must be in the EDL mode.
1. that means shutdown the phone
2. Start the MSM tool and press F8 on the keyboard
3. Press both volume keys at the same time and then connect the USB cable
4. Now the tool would have to recognize your phone and the partitions can be selected
The rest is well described in the first post.
I have a question, Im new in xda and I want to backup modest 1/2 and persist. In this post you can do it in MSM but I cannot see modemst1 or 2 in the partitions checkbox. They have another name? Or I cannot backup those partitions via MSM?
Cris092 said:
I have a question, Im new in xda and I want to backup modest 1/2 and persist. In this post you can do it in MSM but I cannot see modemst1 or 2 in the partitions checkbox. They have another name? Or I cannot backup those partitions via MSM?
Click to expand...
Click to collapse
Try Partitions Backup in the play store
TheGhost1951 said:
Try Partitions Backup in the play store
Click to expand...
Click to collapse
Do I need root or unlocked bootloader? Im unroot and with locked bootloader, that's why Im trying to do it like this post
Cris092 said:
Do I need root or unlocked bootloader? Im unroot and with locked bootloader, that's why Im trying to do it like this post
Click to expand...
Click to collapse
You don't need root to backup, but you do to restore the backup.
This is what my phone says when I open partitions backup
So that's why I want to do it via MSM like this post, but I don't know what partitions do I have to check in MSM. I can see persist but modest 1/2 I cant
Cris092 said:
This is what my phone says when I open partitions backupView attachment 5830269
So that's why I want to do it via MSM like this post, but I don't know what partitions do I have to check in MSM. I can see persist but modest 1/2 I cant
Click to expand...
Click to collapse
Sorry for misleading you, other than that not sure how to get the images you want.
Ok so I made backups using this method like 2 days ago, if we ever need to restore them, how do we do it?
immortalwon said:
Ok so I made backups using this method like 2 days ago, if we ever need to restore them, how do we do it?
Click to expand...
Click to collapse
With partitions backup?
TheGhost1951 said:
With partitions backup?
Click to expand...
Click to collapse
No, using the MSM tool to do a flash readback, which saves most of the firmware to the C: drive
If your phone is already on, you can also use the following command in command prompt to use ADB to reboot into EDL.
adb reboot edl
Still waiting for an answer from OP or anyone else: After we have made a flash read-back via MSM, how are these firmware files restored????
immortalwon said:
Still waiting for an answer from OP or anyone else: After we have made a flash read-back via MSM, how are these firmware files restored????
Click to expand...
Click to collapse
Flashed via Fastboot. For example if you extract boot.img from read-back and you want to restore the boot.img. Reboot your device into Fastboot and enter the following command in command prompt on your computer:
fastboot flash boot boot.img.
Depending on what you are flashing, you need to change the command accordingly. e.g vendor_boot.img
fastboot flash vendor_boot vendor_boot.img
Hi,
Everytime I try to install recovery device stucks in fastboot screen the only way to get out of it is to install miui thru mi flash
Guide me through how to install custom rom on miui 13.0.7.0
Thanks in advance
Crazymods said:
Hi,
Everytime I try to install recovery device stucks in fastboot screen the only way to get out of it is to install miui thru mi flash
Guide me through how to install custom rom on miui 13.0.7.0
Thanks in advance
Click to expand...
Click to collapse
Installed the correct firmware before flashing.
for example for this rom
https://forum.xda-developers.com/t/rom-12-1-official-pixelos-aosp-stable-15-08-2022.4392297/
This firmware
https://sourceforge.net/projects/pixelos-releases/files/twelve/lisa/firmware/
Most often it is global or CN firmware.
NOSS8 said:
Installed the correct firmware before flashing.
for example for this rom
https://forum.xda-developers.com/t/rom-12-1-official-pixelos-aosp-stable-15-08-2022.4392297/
This firmware
https://sourceforge.net/projects/pixelos-releases/files/twelve/lisa/firmware/
Most often it is global or CN firmware.
Click to expand...
Click to collapse
Thanks for the quick reply
I wanted to install CorvusOs also tried but failed, everytime I try to install recovery it mess ups my firmware
Crazymods said:
Thanks for the quick reply
I wanted to install CorvusOs also tried but failed, everytime I try to install recovery it mess ups my firmware
Click to expand...
Click to collapse
Can you post the rom link?
NOSS8 said:
Can you post the rom link?
Click to expand...
Click to collapse
Thread '[SHARED] CorvusOS 4.0-L v12.1 - UNOFFICIAL | Android 12L. Vanilla/GApps | Updated: 2022/08/22' https://forum.xda-developers.com/t/...12l-vanilla-gapps-updated-2022-08-22.4484681/
Crazymods said:
Thread '[SHARED] CorvusOS 4.0-L v12.1 - UNOFFICIAL | Android 12L. Vanilla/GApps | Updated: 2022/08/22' https://forum.xda-developers.com/t/...12l-vanilla-gapps-updated-2022-08-22.4484681/
Click to expand...
Click to collapse
Seems this ROM is for Renoir device
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Think I should flash pixelos
Crazymods said:
Think I should flash pixelos
Click to expand...
Click to collapse
Yeap, try this rom.
Flashing the correct firmware with the TWRP but sometimes it does not work, the method that works 100% is to use Miflash(without relocking the bootloader) and let the phone restart then switch to fastboot mode once arrived at the request of the Xiaomi account.
Install TWRP
Twrp
Wipe/format data type yes
reboot twrp
put the rom in internal storage or use Otg
Flash rom
• After installation complete, Reboot system
if bootloop format data and reboot system.
This method differs from that recommended by the OP but remains the most common one, you can use that of the OP, at your choice.
In any case, formatting the data does not erase the previously installed firmware.
.Use 12 version
https://pixelos.net/download/lisa
NOSS8 said:
Yeap, try this rom.
Flashing the correct firmware with the TWRP but sometimes it does not work, the method that works 100% is to use Miflash(without relocking the bootloader) and let the phone restart then switch to fastboot mode once arrived at the request of the Xiaomi account.
Install TWRP
Twrp
Wipe/format data type yes
reboot twrp
put the rom in internal storage or use Otg
Flash rom
• After installation complete, Reboot system
if bootloop format data and reboot system.
This method differs from that recommended by the OP but remains the most common one, you can use that of the OP, at your choice.
In any case, formatting the data does not erase the previously installed firmware.
.Use 12 version
https://pixelos.net/download/lisa
Click to expand...
Click to collapse
Can you guide more briefly because I messed my os everytime I use adb command
Crazymods said:
Can you guide more briefly because I messed my os everytime I use adb command
Click to expand...
Click to collapse
No ADb command performed.
where are you with the method?
NOSS8 said:
No ADb command performed.
where are you with the method?
Click to expand...
Click to collapse
The moment I type "fastboot flash boot" Drag and drops file I get stuck at bootloop
Crazymods said:
The moment I type "fastboot flash boot" Drag and drops file I get stuck at bootloop
Click to expand...
Click to collapse
Clean flash (coming from a different ROM):
• Reboot to bootloader (fastboot)
• Connect phone to PC
• fastboot flash boot boot.img
• fastboot reboot recovery
• Select Wipe data/factory reset & confirm
• Go back and select Apply update from ADB
• adb sideload PixelOS*.zip
• Flash latest firmware from the link above
• adb sideload fw_lisa*.zip
• After installation complete, Reboot system.
or use my method with twrp.
NOSS8 said:
Clean flash (coming from a different ROM):
• Reboot to bootloader (fastboot)
• Connect phone to PC
• fastboot flash boot boot.img
• fastboot reboot recovery
• Select Wipe data/factory reset & confirm
• Go back and select Apply update from ADB
• adb sideload PixelOS*.zip
• Flash latest firmware from the link above
• adb sideload fw_lisa*.zip
• After installation complete, Reboot system.
or use my method with twrp.
Click to expand...
Click to collapse
Thanks I, ll get back to you
Crazymods said:
Thanks I, ll get back to you
Click to expand...
Click to collapse
In case that doesn't work, detail what you did.
so heres what i did till now
1-i tried to flash twrp and orange fox but unable to boot them i`m stuck at fastboot now
Crazymods said:
so heres what i did till now
1-i tried to flash twrp and orange fox but unable to boot them i`m stuck at fastboot now
Click to expand...
Click to collapse
What command did you use?
NOSS8 said:
What command did you use?
Click to expand...
Click to collapse
"fastboot flash boot" drag and dropped file
Crazymods said:
"fastboot flash boot" drag and dropped file
Click to expand...
Click to collapse
Command is" fastboot boot twrp.img' phone in fastboot mode.
then in Twrp go to Advanced -> flash current TWRP
NOSS8 said:
Command is" fastboot boot twrp.img' phone in fastboot mode.
then in Twrp go to Advanced -> flash current TWRP
Click to expand...
Click to collapse
Rename to twrp.img.
The command from the folder where the img is.
You must have flashed the xiaomi rom first to be on the correct firmware. How did you proceed?
Okay，while you upgrade your op9pro to oos 13 ,and unlock your phone ,you'll got Orange state message , F.16 is upgrade from F.11 ,so ive extract both F.11 & F.16 playload.bin ,and compared each partition of them : those red bleow are different partition between OOS 13.0.0 F.16 and OBT OOS 13.0.0 F.11
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
so ,which partition contains orange state messages ?
i'm worked for a while try to figure out ,finally ,after extract abl.img ,i got LinuxLoader , use winhex to search key word Orange :
F.16 contains orange state ,F.11 not.
maybe flash F.11's abl.img partition would remove the orange state message text ?
anyone could have a try ? haha ,i'm not sure ,i only have one phone ,I‘ll try it when I am on vacation
I've uploaded both f.11 & f.16 abl.img to gdrive ,my device is le2125 https://drive.google.com/file/d/1AKivwtKzF2cMXM15TQA1AlQVCpuUy1ck/view?usp=share_link
or maybe you'll get bootloop after flash this partition
UpArrows said:
or maybe you'll get bootloop after flash this partition
Click to expand...
Click to collapse
Or a brick that could be maybe recovered by MSM
Steve0007 said:
Or a brick that could be maybe recovered by MSM
Click to expand...
Click to collapse
Can you open the current able.img and edit out any warning txt info? Or is an image (png or jpg) that gets displayed?
TheGhost1951 said:
Can you open the current able.img and edit out any warning txt info? Or is an image (png or jpg) that gets displayed?
Click to expand...
Click to collapse
it's hex string , i don't know how to repack the img file after modified
Finally i flashed f.11's abl.img ,actually it works , no Orange state message text ,but emm , stuck at setupwizard ,continue button not work ,i can't enter the desktop ,
UpArrows said:
anyone could have a try ? haha ,i'm not sure ,i only have one phone ,I‘ll try it when I am on vacation
Click to expand...
Click to collapse
As far as i know message about unlocked state comes from bootloader.
OOS11 bootloader has this message, OOS12 hasn't, but OOS13 starting from some build has it again. As you probably identified right, abl.img is a bootloader one.
If oneplus implemented additional checks in bootloader, you will not be able to run one firmware build with bootloader from another, because bootloader allows boot after checks of digital signatures of partitions at minimum: system, vendor, dtbo, boot, vbmeta. If they mismatch boot is not allowed, so you can't just use bootloader from one build on another.
But as OOS13 is relatively new at the moment, additional investigation on the topic should be made to clarify some things.
Finally finally it works ,Congratulations, while i stuck at setupwizard ,i use command :dumpsys activity top | grep ACTIVITY found com.coloros.bootreg/.security.activity.AgreementPage a996400 pid=4001 Prevent i enter the desktop ，so use command am force-stop com.coloros.bootreg stop this activity ,but it restart automaticly ,then i use command: pm uninstall --user 0 com.coloros.bootreg uninstall package com.coloros.bootreg , haha, successfully entered the desktop ,and there is no Orange state message text on boot now .
Rootk1t said:
As far as i know message about unlocked state comes from bootloader.
OOS11 bootloader has this message, OOS12 hasn't, but OOS13 starting from some build has it again. As you probably identified right, abl.img is a bootloader one.
If oneplus implemented additional checks in bootloader, you will not be able to run one firmware build with bootloader from another, because bootloader allows boot after checks of digital signatures of partitions at minimum: system, vendor, dtbo, boot, vbmeta. If they mismatch boot is not allowed, so you can't just use bootloader from one build on another.
But as OOS13 is relatively new at the moment, additional investigation on the topic should be made to clarify some things.
Click to expand...
Click to collapse
finally it works ,haha,
UpArrows said:
finally it works ,haha,
Click to expand...
Click to collapse
So using bootloader from recently released builds is possible.
Thanks for checking!
To make it clear, just removing com.coloros.bootreg before flashing DD the beta abl.img should work?
Will flashing DD erase data?
Steve0007 said:
To make it clear, just removing com.coloros.bootreg before flashing DD the beta abl.img should work?
Will flashing DD erase data?
Click to expand...
Click to collapse
I'm recommended to clear all data after updated and flashed abl.img, if not full screen gestures may not work properly .
Steve0007 said:
To make it clear, just removing com.coloros.bootreg before flashing DD the beta abl.img should work?
Will flashing DD erase data?
Click to expand...
Click to collapse
The steps are below：
1. upgrade from c66 to F16 & do not reboot
2. magisk patch another slot & do not reboot
3. dd flash abl.img
4. reboot & upgrade
5. you'll got stuck at setupwizard ,if uninstall com.coloros.bootreg ,also you can entered the desktop ,but full screen gestures may not work properly .
6 . reboot to recovery & clear all data ,and everything works well !
Before flash abl.img , use command : getprop ro.boot.slot_suffix to identify currently active slot ，make sure do not flash to current slot .
UpArrows said:
The steps are below：
1. upgrade from c66 to F16 & do not reboot
2. magisk patch another slot & do not reboot
3. dd flash abl.img
4. reboot & upgrade
5. you'll got stuck at setupwizard ,if uninstall com.coloros.bootreg ,also you can entered the desktop ,but full screen gestures may not work properly .
6 . reboot to recovery & clear all data ,and everything works well !
Click to expand...
Click to collapse
soooooooooooooooo....I was already on F16. Just wanted to say that all I did was
1. Got abl.img from F11 and placed at /sdcard
2. Restore images from Magisk
3. Magisk patch to other slot
4. got into a root shell and ran "blockdev --setrw /dev/block/sde13" and "dd if=/sdcard/abl.img of=/dev/block/sde13"
5. Rebooted
no longer have orange prompt and everything is working normal.
Zeus0fyork said:
soooooooooooooooo....I was already on F16. Just wanted to say that all I did was
1. Got abl.img from F11 and placed at /sdcard
2. Restore images from Magisk
3. Magisk patch to other slot
4. got into a root shell and ran "blockdev --setrw /dev/block/sde13" and "dd if=/sdcard/abl.img of=/dev/block/sde13"
5. Rebooted
no longer have orange prompt and everything is working normal.
Click to expand...
Click to collapse
Thanks. What is the purpose of restoring boot with magisk and patch the other slot? Did you flash again F16?
Zeus0fyork said:
soooooooooooooooo....I was already on F16. Just wanted to say that all I did was
1. Got abl.img from F11 and placed at /sdcard
2. Restore images from Magisk
3. Magisk patch to other slot
4. got into a root shell and ran "blockdev --setrw /dev/block/sde13" and "dd if=/sdcard/abl.img of=/dev/block/sde13"
5. Rebooted
no longer have orange prompt and everything is working normal.
Click to expand...
Click to collapse
Can anybody understand the purpose of restoring original boot using Magisk and patching the other slot before replacing the abl.img?
Won't replacing abl.img work as it should w/o having to do 2 and 3 from above instructions?
Still works on LE2125_11_F.17
UpArrows said:
I've uploaded both f.11 & f.16 abl.img to gdrive ,my device is le2125 https://drive.google.com/file/d/1AKivwtKzF2cMXM15TQA1AlQVCpuUy1ck/view?usp=share_link
Click to expand...
Click to collapse
i have LE2123 F72 version,how can i use for this version this methot ?