Develop Bugs

Flasing GSI in realme 3 [Guide][Updated:21-08-19]

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

How to root?

Hi everyone
My phone model is xt2075-3,I want to root
Can I directly flash the latest magisk(20.4) to get root permission after unlocking BL?

I've succeeded in getting root.The steps are as follows
1.Download the twrp for your mobile phone,and magisk20.4.zip,magisk 7.5.1.apk
2.Visit Motorola official unlock website to unlock BL
3.You have 2 choice,A.boot on twrp one time;B.flash twrp;I choose A
4.Whatever your choose,in the twrp,install magisk zip,after done,reboot system
Enjoy root!

If you use the Magisk Manager to patch the boot image manually, and then flash that through fastboot - will that work also?
(My phone has yet to arrive so can't test this just yet...)

Update : i got the 8gb ram 128gb varient and i could boot into twrp from fastboot but i cannot flash replacing stock recovery nor i can see the internal or external memory due to decryption error
However, i basically unlocked boot loader and booted in fast boot then i flashed the patched boot.img ( installed magisk apk and added the stock boot.img inside the phone to patch it) then copy it back to pc and flashed it in fastboot mode and now i got root access
NOTE : if you happen to do something wrong you cannot use rescue and backup software to restore your phone to stock again ... flash stock boot.img in fastboot first so the software will recognize the phone back again

sniper9911 said:
Update : i got the 8gb ram 128gb varient and i could boot into twrp from fastboot but i cannot flash replacing stock recovery nor i can see the internal or external memory due to decryption error
However, i basically unlocked boot loader and booted in fast boot then i flashed the patched boot.img ( installed magisk apk and added the stock boot.img inside the phone to patch it) then copy it back to pc and flashed it in fastboot mode and now i got root access
NOTE : if you happen to do something wrong you cannot use rescue and backup software to restore your phone to stock again ... flash stock boot.img in fastboot first so the software will recognize the phone back again
Click to expand...
Click to collapse
where did you find the boot.img and the patched one?
Thanks

Mr.Krulez said:
where did you find the boot.img and the patched one?
Thanks
Click to expand...
Click to collapse
Get the full stock image by downloading rescue and smart assistant app from lenovo which supports moto phones ... Do login and get the fastboot rescue option while plugging your phone in the pc in fastboot mode .. then it will download it full firmware for your varient
Becareful that continue to flash the firmware will wipe your phone completely
After that get a copy of the boot.img file ... Copy it to the internal memory and install magisk manager apk from its official github site ... Now patch the boot.img you copied in your phone inside the magisk app then copy it back to your pc
Lear how to flash it from fastboot
Flash it
Done .. you are now rooted by patched boot.img with stock recovery !
Sent from my moto g 5G plus using Tapatalk
View attachment 5143479View attachment 5143477View attachment 5143481

Thank you for the answer but if I want to just root my phone I only need to flash magisk right? i don't need the patched boot.img?
sorry to bother you but the last phone I used supersu withouth flashing anything else than the recovery

Hi Guys,
my device is a/b device, bootloader unlocked, could you please kindly advise to flash twrp
what is the fastboot command, i use fastboot flash recovery twrp.img and i get a bootloop . the command fastboot boot twrp.img runs twrp onece and its fine, but how do i flash it please?
thanks and kind regards

emanuel said:
what is the fastboot command, i use fastboot flash recovery twrp.img and i get a bootloop . the command fastboot boot twrp.img runs twrp onece and its fine, but how do i flash it please?
Click to expand...
Click to collapse
I think the flash method fails because there is no partition called "recovery" - as an A/B device it looks like there are two:
Code:
nairo:/ $ ls -l /dev/block/by-name/ | grep recovery
lrwxrwxrwx 1 root root 16 1970-05-20 07:34 recovery_a -> /dev/block/sdd20
lrwxrwxrwx 1 root root 16 1970-05-20 07:34 recovery_b -> /dev/block/sdf20
if you have the Magisk zip file on the internal storage you can use the "fastboot boot twrp.img" method to flash it from there (for some reason TWRP can't see the SD card on my device)

Now for my question... my rooted (UK Retail) device has indicated that there is an OTA update:
I've tried using the method described here to restore the boot partition to stock so that it doesn't interfere with the process, but it fails (see attached images).
Does anyone know of a working method? I have downloaded the full (2+GB) update so am prepared to flash that (and restore everything else from backups) if necessary - but would rather not if it can be avoided...
{
"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"
}

xth88312 said:
I've succeeded in getting root.The steps are as follows
1.Download the twrp for your mobile phone,and magisk20.4.zip,magisk 7.5.1.apk
2.Visit Motorola official unlock website to unlock BL
3.You have 2 choice,A.boot on twrp one time;B.flash twrp;I choose A
4.Whatever your choose,in the twrp,install magisk zip,after done,reboot system
Enjoy root!
Click to expand...
Click to collapse
Hi @xth88312 ,
can you give the link you used to download TWRP for Moto XT2075-3?

I unlocked my phone through the official Motorola site:
Unlocking the Bootloader | Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.
motorola-global-portal.custhelp.com
I downloaded the latest Magisk and MagiskManager in the same directory from
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
I downloaded the original firmware from https://mirrors.lolinet.com/ and extracted the boot.img in the same directory, then issued, through the ADB connection:
Code:
adb install ./MagiskManager-*.apk
adb push ./boot.img /sdcard/Download/
(Replace the star as needed)
I opened MagiskManager app (you need to be connected to the Internet) and in the Magisk card I tapped Install > "Select and Patch a File". I browsed for and selected /sdcard/Download/boot.img and tapped "Let's go". A patched image /sdcard/Download/magisk_patched_*.img is created. Then, through the ADB connection, I issued:
Code:
adb pull /sdcard/Download/magisk_patched_*.img
adb reboot bootloader
fastboot devices
fastboot flash boot magisk_patched_*.img
fastboot reboot
At reboot, the phone was rooted.

boringtech said:
Hi @xth88312 ,
can you give the link you used to download TWRP for Moto XT2075-3?
Click to expand...
Click to collapse
[RECOVERY][UNOFFICIAL] TWRP 3.5.0.0
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com
thats the link for twrp for moto g 5g plus..
use at own risk as i havent tried it myself so im not responsible for bricked devices etc...FLASH AT OWN RISK....

Mr.Krulez said:
Thank you for the answer but if I want to just root my phone I only need to flash magisk right? i don't need the patched boot.img?
sorry to bother you but the last phone I used supersu withouth flashing anything else than the recovery
Click to expand...
Click to collapse
Mr.Krulez said:
Thank you for the answer but if I want to just root my phone I only need to flash magisk right? i don't need the patched boot.img?
sorry to bother you but the last phone I used supersu withouth flashing anything else than the recovery
Click to expand...
Click to collapse
youll have to patch bo
Mr.Krulez said:
Thank you for the answer but if I want to just root my phone I only need to flash magisk right? i don't need the patched boot.img?
sorry to bother you but the last phone I used supersu withouth flashing anything else than the recovery
Click to expand...
Click to collapse
you need to
Mr.Krulez said:
Thank you for the answer but if I want to just root my phone I only need to flash magisk right? i don't need the patched boot.img?
sorry to bother you but the last phone I used supersu withouth flashing anything else than the recovery
Click to expand...
Click to collapse
youll need the patched boot.img to gain root, thats how ive had to root all my moto phones ive had, never been able to just flash supersu etc, someone will jump in if im wrong but as far as i know you need to patch the boot.img....
Remember everything you do is at your own risk i take no responsibility for.what you do with your device

How To Guide Convert your T-Mobile (LE2127) to EU via MSM, No unlock.bin needed!

*** Use this at your very own risk.
*** You will lose all data
*** Backup your working modemst1/2 and persist. If you lose these for any reason, it's unique to your device and not recoverable if you didn't back up (via MSM or other people).
*** Read the entire post and follow the steps closely before asking for help. Post all error messages and steps you took. If you just ran a bunch of unknown commands, I would tell you to MSM.
*** Know how to use the MSMTool, Don't start before figuring it out. https://forum.xda-developers.com/t/op9pro-repository-of-msm-unbrick-tools-tmo-glo-in.4272549/
*** DO NOT ATTEMPT THIS IF YOU ARE NOT FAMILIAR WITH ANY STEP DESCRIBED IN THIS GUIDE
General notes:
NR and LTE bands are read only and not modifiable, not in modem.img or any other partition. You cannot get global bands by flashing a global ROM, nor can you lose TMO bands by flashing another ROM.
If you wish to unlock the bootloader without unlock_code.bin, you MUST do it from OOS11. If you upgrade to OOS12/OOS13, you will need the unlock_code.
The T-Mobile NON-HLOS is no longer necessary as of OOS13 release. If you must stay on OOS11 or OOS12, make a backup of the T-Mobile modem partition for the OOS version you want to stay on.
Dual-SIM does not work.
Prerequisites:
This conversion will not SIM unlock you. You can only SIM unlock on a T-Mobile ROM, meaning if you want to do that in the future, you must go back to a TMO ROM (and wipe)
Familiarity with MSMDownload tools. If the regular MSM tool doesn't work for you, turn back now.
Back up all data, it will be wiped.
Download:
Conversion: AndroidFileHost (MD5: 8cc3e5e81d15e28bb10dc5f1e7bd4133)
Steps:
Run the MSM file normally.
Unlock your bootloader if necessary. Now is the time if you don't have unlock.bin
Patch up to Android 13 while on Wifi if your mobile data doesn't work. Use this time to go to another variant (GLO, IN, etc) as needed.
Fastboot method:
* The steps in this guide will convert your TMO LE2127 to EU 11.2.3.3. This is intentionally not the latest version to force you to take a FULL OTA.
* You must already have the bootloader unlocked with an unlock_code.bin
* You can use this guide to convert to your own variant by extracting payload and flashing from a full OTA. No support will be given if you choose to manually do it.
* Use the latest platform tools: https://developer.android.com/studio/releases/platform-tools. DO NOT USE MINIMAL ADB, it has not been updated for years.
* Fastboot can't see your device? https://forum.xda-developers.com/t/...stboot-mode-windows-10.4194491/#post-84943553
* Test that you can boot to fastbootd prior to starting, "fastboot reboot fastboot" and you should see the OnePlus logo with the text "fastbootd" on top. Do not continue if this doesn't work.
* When encountering issues, describe all steps you took, paste any outputs, and take screenshots. Make sure to include the output of fastboot --version in your post.
Steps to convert your device to EU
You need your device bootloader and SIM unlocked. See https://forum.xda-developers.com/t/how-to-unlock-the-t-mobile-bootloader.4256319/
Download and unzip the conversion package:
EU 11.2.3.3
MD5: cb949816fa80d5f0d984359b819426c3
Boot to bootloader.
From adb:
Code:
adb reboot bootloader
From fastboot/bootloader:
Code:
fastboot reboot bootloader
Execute "flash_all.bat" from the unzipped directory from step 2.
Reboot into recovery, and wipe everything.
Once fully booted, connect to WiFi and download Oxygen Updater and take the FULL OTA (11.2.4.4 as of this writing)
Do a regular reboot, don't reboot to fastbootd, bootloader, recovery, etc. Reboot to system.
Reboot into bootloader or fastbootd, and flash the T-Mobile modem.
Code:
fastboot flash modem NON-HLOS.bin
After each Full OTA you take in the future, you will need to repeat step 7 & 8
FAQ
Q: The most recent version is 11.2.4.4, why is this guide converting to 11.2.3.3?
A: You didn't read the full post.
Q: Why is there no conversion to Global?
A: Global variant uses the Google incremental OTA server, and full OTAs are not always provided. There's no functional difference, and EU has better privacy requirements anyways. You can do it manually by extracting payload.bin and running the same flash script. No support will be provided if you choose to flash to Global.
Q: Can I re-lock the bootloader after conversion?
A: While you can go ahead lock your bootloader after conversion, I don't recommend it as you will not be able to take incremental OTA due to modem changes, and lose connectivity if you take a full OTA. To fix it, you need to unlock the bootloader and end up wiping.
Q: Where is the Linux guide?
A: Too lazy, if you're using Linux, you can make your own bash script from the Windows batch script.
Q: Help, I see is 'fastboot' is not recognized as an internal or external command.
A: Your fastboot.exe is not in your $PATH. You can either drop fastboot into the same folder as flash-all.bat, or you can fix your $PATH
Q: Help, I cannot boot to fastbootd because previous flashes messed things up.
A: MSM
Q: Help, "not enough space to resize [system, product, system_ext]"
A: MSM. If the error is on Vendor, it might still work and boot with a generic Android boot logo. If so, take the full OTA as described in the guide.
Q: Help, something went wrong!
A: Post in here the starting state of your device (Device model, ROM version, etc), all steps you've taken since unlocking bootloader, and the output of whatever is causing you trouble. Chances are, the answer is MSM, but read my MSM warning.
Q: Help, I see "Invalid sparse file format at header magic"
A: Ignore this message, not an error
Fixing the About Phone page
These steps are optional, and is only applicable for OOS11. It will fix the "About Phone" page. There are no performance differences. All that's done is change build.prop to reflect the correct model.
You need to rooted with Magisk
Download and install the magisk module: here
Reboot, the About Phone page is filled out.
Instructions to Bootloader Unlock a SIM locked device:
In ADB:
Code:
adb shell pm uninstall -k --user 0 com.qualcomm.qti.uim
Reboot
Go to dev settings and enable OEM Unlock
Reboot to bootloader
Code:
fastboot oem unlock
No unlock.bin needed
Issues so far (please post if you run into more):
If your mobile data doesn't work on OOS13, PM me details including HW Revision in About Phone.
What appears to work:
Everything else.
Much appreciation for everyone that help develop and test
@razercortex
@retryfail
@amaroney55

I went straight to the 11.2.4.4 as well, instead of the 11.2.3.3. Probably why I had such an issue also. Dummy me, wanted the latest and greatest right away and paid the price for it.

Goodness man. Presently I see where I wrecked. I did the EU 11.2.4.4 and not the 11.2.3.3. much obliged for this and clearing that up. Likewise, thank you again for assisting me with saving my mobile. JBBattery

Woohoo! Thank you!!

for some reason my Wildvine downgrades to L3, not sure how to fix it, also as other post indicates, voice mail on dialer doesn't work

avid_droid said:
It says to have magisk hiding from Google play services. Have you done that?
Click to expand...
Click to collapse
Yes, I toggled all options under google play services, no luck
{
"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"
}

ok going to give this a go later fingers crossed and just to clarify i only need to backup ModemST1 and ModemST2 img correct?

avid_droid said:
Nope. TRied again and its a no go since every damn thing is failing. fastboot mode and fastbootd is constantly failing on every file thats being flashed. What you need from me.?
Click to expand...
Click to collapse
you mind pasting some errors here? maybe the 1st error you got from cmd

Ultraman666 said:
ok going to give this a go later fingers crossed and just to clarify i only need to backup ModemST1 and ModemST2 img correct?
Click to expand...
Click to collapse
Persist

avid_droid said:
Nope. TRied again and its a no go since every damn thing is failing. fastboot mode and fastbootd is constantly failing on every file thats being flashed. What you need from me.?
Click to expand...
Click to collapse
* Test that you can boot to fastbootd prior to starting, "fastboot reboot fastboot" and you should see the OnePlus logo with the text "fastbootd" on top. Do not continue if this doesn't work.
* When encountering issues, describe all steps you took, paste any outputs, and take screenshots. Make sure to include the output of fastboot --version in your post.
Sounds like you tested that fastboot can't get you to fastbootd, but you continued anyways.
If you want troubleshooting, post the information I said to post

craznazn said:
Persist
Click to expand...
Click to collapse
Thanks for the hint, I backed up the persist.img but that's after root/unlock bl, so you are saying flash persist.img will get me back to L1?

avid_droid said:
everything fails in flashing. it just says FAILED on every .img that is being pushed. Im so confused. It says be in bootloader,but isnt it supposed to be in fastbootd???
Im still getting no response from fastboot reboot fastboot. Only way i can get into fastbootd is by adb reboot fastboot.
Which is it? in bootloader or fastbootd??
Click to expand...
Click to collapse
avid_droid said:
fastboot --version says unkown option
Click to expand...
Click to collapse
sounds to me like you don't get the proper version of fastboot, one thing to notice, if you install the one plus driver you may get the fastboot from C:\Android, DONT use this one. either put the correct platform-tool path to your $PATH or manually modify every fastboot.exe to be full path in script

sunxutian said:
Thanks for the hint, I backed up the persist.img but that's after root/unlock bl, so you are saying flash persist.img will get me back to L1?
Click to expand...
Click to collapse
No, persist just unique to your device. You just need a backup in case yours get wiped for any reason.
Honestly, you are the 2nd person I've heard from that had the L1 issue and we were never able to figure it out. I did these steps to 2 different devices and both kept L1. Does safetynet pass? Do you have magisk canary?

craznazn said:
No, persist just unique to your device. You just need a backup in case yours get wiped for any reason.
Honestly, you are the 2nd person I've heard from that had the L1 issue and we were never able to figure it out. I did these steps to 2 different devices and both kept L1. Does safetynet pass? Do you have magisk canary?
Click to expand...
Click to collapse
Yes, my safetynet passes and I do have magisk canary

avid_droid said:
I have it in C: and am opening powershell from that folder
Click to expand...
Click to collapse
Download a fresh copy of platform tools and unzip it into the folder that has flash_all.bat and .img files

craznazn said:
No, persist just unique to your device. You just need a backup in case yours get wiped for any reason.
Honestly, you are the 2nd person I've heard from that had the L1 issue and we were never able to figure it out. I did these steps to 2 different devices and both kept L1. Does safetynet pass? Do you have magisk canary?
Click to expand...
Click to collapse
what I suspect might be wrong is when I did the BL unlock I use fastboot oem unlock while some people use fastboot flashing unlock (not sure this makes any difference or not)

I did oem unlock, shouldn't make a difference

From that folder, run fastboot --version and share the screenshot

craznazn said:
I did oem unlock, shouldn't make a difference
Click to expand...
Click to collapse
Then anything I can try?

sunxutian said:
Then anything I can try?
Click to expand...
Click to collapse
Hmm, also try the fix about page magisk module, shouldn't affect anything but you never know.
If that doesn't fix it, take the 11.2.4.4 OTA again via local update, and then lock the bootloader and check. You won't have a working modem but I want to make sure your wildvine keys are still there.

Development [ROM][Android 11][OP9Pro] crDroid v7

{
"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"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Flashing Instructions:
Pre-installation:
Until TWRP is ready, this version of crDroid comes with prebaked core Gapps
Download LOS recovery
Download Tiny ADB & Fastboot
First time installation (clean flash):
It is recommended to come clean from latest OOS installation
Backup your data to PC, OTG flash drive
Reboot to bootloader (fastboot)
Run fastboot devices to confirm there is connection to the phone
Install LOS recovery with following command fastboot flash boot lineage-18.1-20210615-recovery-lemonadep.img
Power off and reboot to recovery by pressing VOL down + Power from shutdown state
Navigate with volume keys to Factory Reset -> Format data/factory reset and confirm format of data
Go back to main menu and choose Apply update and Apply from ADB
Now adb sideload latest crDroid package with adb sideload crDroid.zip
When asked to confirm flash, do confirm it
Sideload push will go up to 47% and fail - no worry is normal
Reboot to system
Update installation:
Through recovery:
Download latest crDroid zip and reboot to recovery
Choose Apply update and Apply from ADB
Now adb sideload latest crDroid package with adb sideload crDroid.zip
Sideload push will go up to 47% and fail - no worry is normal
Reboot to system
Built-in OTA (slower):
When ready
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/crdroidandroid/android_kernel_oneplus_sm8350
Download:
ROM https://crdroid.net/lemonadep#crDroid-v7
Changelog: https://crdroid.net/lemonadep#crDroid-v7/changelog
Known issues:
- waiting for more feedback to see
Visit official website @ crDroid.net
crDroid OnePlus 9 Pro Telegram
crDroid Community Telegram
crDroid is built with passion by @neobuddy89 and @gwolfu
If you like our work, do consider a donation to support further device development
ROM OS Version: Android 11
ROM Kernel: Linux 5.4

Awesome.

I have the Tmobile version of OP9pro. Will I need to flash the tmobile modem.img?

burtonlax said:
I have the Tmobile version of OP9pro. Will I need to flash the tmobile modem.img?
Click to expand...
Click to collapse
Testing of this rom has been done on the EU variant
I am not sure how Tmobile version works, but rom side, is same as on LOS

gwolfu said:
Testing of this rom has been done on the EU variant
I am not sure how Tmobile version works, but rom side, is same as on LOS
Click to expand...
Click to collapse
it's best to go global first coming from tmo. No, as long as you don't do an ota on Global. so flash global then boot, then flash custom rom(following their guide).
If u lose service modem is provided (Just unzip) Bootloader fastboot command "fastboot flash modem modem.img
This of course is assuming u got unlock.bin and unlocked Bootloader

Here we go!
Welcome @gwolfu
Hopefully we don't need 11.2.7.7?? It's not out here in EU yet, what's the reason most of the custom roms seem to want the EU build by the way?

CRDroid, fantastic to see this here my favorite ROM since the days of my LG G3! Can't wait to try this out, will sadly be waiting till TWRP tho as I'd prefer to avaoid gapps. Unless there is any chance of a non gapps build also? Cheeky....!

I'll flash and report tomorrow .
post logs through here or telegram?

ryantf420 said:
I'll flash and report tomorrow .
post logs through here or telegram?
Click to expand...
Click to collapse
preferably here as to better keep track of stuff

I know it may not be recommended, but has anyone been able to flash this without using a computer?

phr0zen said:
I know it may not be recommended, but has anyone been able to flash this without using a computer?
Click to expand...
Click to collapse
Since the instructions specify using fastboot (as well as sideloading the rom), that's not possible.

phr0zen said:
I know it may not be recommended, but has anyone been able to flash this without using a computer?
Click to expand...
Click to collapse
without TWRP, not possible

TWRP is death.

This is awesome news brother

So I've been out of the root and rom flashing game for a bit, got it side loaded and everything my issue is i cant get root permissions working wasn't sure how i go about setting it up since all i have worked with on the one plus is magisk and having to install to a .img and input on how to get it working?

crazyvash1 said:
So I've been out of the root and rom flashing game for a bit, got it side loaded and everything my issue is i cant get root permissions working wasn't sure how i go about setting it up since all i have worked with on the one plus is magisk and having to install to a .img and input on how to get it working?
Click to expand...
Click to collapse
extract crdroid.zip content
extract boot.img from payload.bin file using payload dumper
install magisk apk on phone as any other apk (I know we are not rooted yet)
copy boot.img to internal phone storage
open magisk and click on top install button
choose "select and patch a file"
select the boot.img from internal storage
after done, copy magisk patched boot image from Download folder on phone storage, to PC
now on PC, reboot to bootloader and run
Code:
fastboot flash boot magisk_patched-23000_xxxxx.img
check file name to match xxxxx = random generated text
reboot to system and enjoy

gwolfu said:
extract crdroid.zip content
extract boot.img from payload.bin file using payload dumper
install magisk apk on phone as any other apk (I know we are not rooted yet)
copy boot.img to internal phone storage
open magisk and click on top install button
choose "select and patch a file"
select the boot.img from internal storage
after done, copy magisk patched boot image from Download folder on phone storage, to PC
now on PC, reboot to bootloader and run
Code:
fastboot flash boot magisk_patched-23000_xxxxx.img
check file name to match xxxxx = random generated text
reboot to system and enjoy
Click to expand...
Click to collapse
Think you missed the last step to use Magisk again to root the installed boot image?

djsubterrain said:
Think you missed the last step to use Magisk again to root the installed boot image?
Click to expand...
Click to collapse
Not need
I used fastboot flash not fastboot boot so boot is already patched
No temp boot and patch after

gwolfu said:
Not need
I used fastboot flash not fastboot boot so boot is already patched
No temp boot and patch after
Click to expand...
Click to collapse
Didn't notice that, totally right. Sorry.

truly have found nothing broken
except power menu settings only work in crdroid Settings not in System>Gestures>power menu...
Great job

Question How to upgrade to the latest patch of Android 12

Hey guys recived an update through the OnePlus oxygen updater today, currently in the "Stable" Android 12 release but after downloading the latest patch i noticed that there is no local upgrade option like it used to be prior, am i missing something here ? Thanks.

How to update from OnePlus 9 Pro Oxygen OS 12.0.0.0.LE15 to today's fixed OOS 12? Local update no longer available in settings/update

This might help: https://oxygenos.oneplus.net/OPLocalUpdate_For_Android12.apk

Zip file not showing on update.. and yes is in main storage

Option 2: with incremental OTA Access (AA) :​
Step 1 - Get back your original boot image​1. open the Magisk Manager application, select “Uninstall”, and choose the “Restore Images” option. Magisk will restore your phone’s stock boot image that was backed up during the rooting process.
{
"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"
}
2. Now go to “Settings” → “System” → “System updates” and select “Download and Install Now” to install the OxygenOS OTA update on your rooted OnePlus 9 Pro
3. Open Magisk Manager
a. Select the Install option.
b. Use Install to inactive slot

Progaros said:
This might help: https://oxygenos.oneplus.net/OPLocalUpdate_For_Android12.apk
Click to expand...
Click to collapse
Thanks a ton! This helped me to upgrade my incremental update!

PKkeys said:
Thanks a ton! This helped me to upgrade my incremental update!
Click to expand...
Click to collapse
Didn't work for me guide above so used APK to bring back local upgrade

More importantly, now that you patched to the latest, is it still a cleveland steamer?

toolhas4degrees said:
Option 2: with incremental OTA Access (AA) :​
Step 1 - Get back your original boot image​1. open the Magisk Manager application, select “Uninstall”, and choose the “Restore Images” option. Magisk will restore your phone’s stock boot image that was backed up during the rooting process.
2. Now go to “Settings” → “System” → “System updates” and select “Download and Install Now” to install the OxygenOS OTA update on your rooted OnePlus 9 Pro
3. Open Magisk Manager
a. Select the Install option.
b. Use Install to inactive slot
Click to expand...
Click to collapse
any other option to install incremental update? because i am getting failed message during installation despite this procedures

AboAnas25 said:
any other option to install incremental update? because i am getting failed message during installation despite this procedures
Click to expand...
Click to collapse
No and it doesn't work on a12 as I have tried. You need to unroot. Install the update.
/save msm_pull
Using MSM tool to pull boot.img, vendor_boot.img, and vbmeta:
1) Find out what your current active slot with either adb shell getprop ro.boot.slot_suffix or fastboot getvar current-slot
2) Open the MSM tool select Other at the top and Next button if you have to
3) Hit F8. Put a checkbox in boot_a or boot_b, vendor_boot_a or vendor_boot_b, and vbmeta files (whichever is your current active slot.) Password is: oneplus (case sensitive.) There will be a new Read Back button at the top
3) Put the phone in EDL mode....adb reboot edl...is easier than buttons but whatever. As soon as you see it's connected, hit the Read Back button.
4) Read back will only take a few seconds. File(s) will end up on the root of your PC's C:\ drive.
Next put the vendor_boot and boot images on your phone patch each with magisk. Copy the patched images back to your fastboot folder and put the vbmeta image there as well.
Next Run this command:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
***_**_*Make sure it completes without errors before proceeding. If errors, update your ADB: https://developer.android.com/studio/releases/platform-tools
If no errors, run these commands:
fastboot flash vendor_boot vendor_boot_magisk.img
fastboot flash boot boot_magisk.img
8) If no errors, run
fastboot reboot

AboAnas25 said:
any other option to install incremental update? because i am getting failed message during installation despite this procedures
Click to expand...
Click to collapse
The problem is Google installer... And the fact you need to patch 2 images and remove verification and verity

toolhas4degrees said:
No and it doesn't work on a12 as I have tried. You need to unroot. Install the update.
/save msm_pull
Using MSM tool to pull boot.img, vendor_boot.img, and vbmeta:
1) Find out what your current active slot with either adb shell getprop ro.boot.slot_suffix or fastboot getvar current-slot
2) Open the MSM tool select Other at the top and Next button if you have to
3) Hit F8. Put a checkbox in boot_a or boot_b, vendor_boot_a or vendor_boot_b, and vbmeta files (whichever is your current active slot.) Password is: oneplus (case sensitive.) There will be a new Read Back button at the top
3) Put the phone in EDL mode....adb reboot edl...is easier than buttons but whatever. As soon as you see it's connected, hit the Read Back button.
4) Read back will only take a few seconds. File(s) will end up on the root of your PC's C:\ drive.
Next put the vendor_boot and boot images on your phone patch each with magisk. Copy the patched images back to your fastboot folder and put the vbmeta image there as well.
Next Run this command:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
***_**_*Make sure it completes without errors before proceeding. If errors, update your ADB: https://developer.android.com/studio/releases/platform-tools
If no errors, run these commands:
fastboot flash vendor_boot vendor_boot_magisk.img
fastboot flash boot boot_magisk.img
8) If no errors, run
fastboot reboot
Click to expand...
Click to collapse
Makes sense. Thank you for this post.
If possible, I think it would be helpful to others if you (or somebody else) can upload and share those new stock vendor-boot/boot/vbmeta images that were dumped using the msmtool. Would save a lot of trouble to others.
Thanks again!

toolhas4degrees said:
No and it doesn't work on a12 as I have tried. You need to unroot. Install the update.
/save msm_pull
Using MSM tool to pull boot.img, vendor_boot.img, and vbmeta:
1) Find out what your current active slot with either adb shell getprop ro.boot.slot_suffix or fastboot getvar current-slot
2) Open the MSM tool select Other at the top and Next button if you have to
3) Hit F8. Put a checkbox in boot_a or boot_b, vendor_boot_a or vendor_boot_b, and vbmeta files (whichever is your current active slot.) Password is: oneplus (case sensitive.) There will be a new Read Back button at the top
3) Put the phone in EDL mode....adb reboot edl...is easier than buttons but whatever. As soon as you see it's connected, hit the Read Back button.
4) Read back will only take a few seconds. File(s) will end up on the root of your PC's C:\ drive.
Next put the vendor_boot and boot images on your phone patch each with magisk. Copy the patched images back to your fastboot folder and put the vbmeta image there as well.
Next Run this command:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
***_**_*Make sure it completes without errors before proceeding. If errors, update your ADB: https://developer.android.com/studio/releases/platform-tools
If no errors, run these commands:
fastboot flash vendor_boot vendor_boot_magisk.img
fastboot flash boot boot_magisk.img
8) If no errors, run
fastboot reboot
Click to expand...
Click to collapse
You shouldn't need all those extra images/partitions if you use magisk alpha. Just boot patched boot.img then open magisk and do a direct install.

terlynn4 said:
You shouldn't need all those extra images/partitions if you use magisk alpha. Just boot patched boot.img then open magisk and do a direct install.
Click to expand...
Click to collapse
Where did you get a boot image from? This method will work on an6 magisk. You can't on a incremental update.. if you had a full zip yes I tried with alpha first the old method of removing and patching no longer works. So msm tool is your option... Other than that show me how you updated without pulling it. Since the ita won't work with payload dumper

toolhas4degrees said:
You can't on a incremental update.. if you had a full zip yes I tried with alpha first
Click to expand...
Click to collapse
There's no need to do vendor boot when using Magisk Alpha, even on instrumentals. All I had to do to root was restore stock c.36 boot and vbmeta, update to c.39 and then use MSM to pull vbmeta and boot. I patched the boot with Magisk Alpha, booted the patched boot.img and then when in OS did a direct install. Didn't have to re-disable verity or flash vbmeta again either after updating, only using patched boot.img.

toolhas4degrees said:
You can't on a incremental update.. if you had a full zip yes I tried with alpha first
Click to expand...
Click to collapse
If you're already rooted before updating you can just restore images from magisk, install the update, install magisk to inactive slot, then reboot. That's what I did for the incremental. But even if you're already rooted you shouldn't need vbmeta. Granted, things don't *always* work like they should.
jeffsga88 said:
There's no need to do vendor boot when using Magisk Alpha, even on instrumentals. All I had to do to root was restore stock c.36 boot and vbmeta, update to c.39 and then use MSM to pull vbmeta and boot. I patched the boot with Magisk Alpha, booted the patched boot.img and then when in OS did a direct install. Didn't have to re-disable verity or flash vbmeta again either after updating, only using patched boot.img.
Click to expand...
Click to collapse
Yeah, this is the behavior I would expect. So you didn't actually do anything with vbmeta, right? You just pulled it in case you needed it?

terlynn4 said:
If you're already rooted before updating you can just restore images from magisk, install the update, install magisk to inactive slot, then reboot. That's what I did for the incremental. But even if you're already rooted you shouldn't need vbmeta. Granted, things don't *always* work like they should.
Yeah, this is the behavior I would expect. So you didn't actually do anything with vbmeta, right? You just pulled it in case you needed it?
Click to expand...
Click to collapse
I did this others did this also it did not update it stayed on last version I was using latest alpha going from c36 to c39 global. Just stayed on 36 if I tried it again sent to boot loop. That method did not work
Would been nice if you read what I posted earlier

toolhas4degrees said:
I did this others did this also it did not update it stayed on last version I was using latest alpha going from c36 to c39 global. Just stayed on 36 if I tried it again sent to boot loop. That method did not work
Click to expand...
Click to collapse
Interesting. I never flashed vbmeta or vendor except when I was on open beta. I used the incremental method above for both the update to c38 "stable" and to c39. Folks in another thread lost root and re-rooted with only boot.img. Not sure what went wrong in your case.

terlynn4 said:
Interesting. I never flashed vbmeta or vendor except when I was on open beta. I used the incremental method above for both the update to c38 "stable" and to c39. Folks in another thread lost root and re-rooted with only boot.img. Not sure what went wrong in your case.
Click to expand...
Click to collapse
Maybe an issue from 36 to 39 you know 38 is basically 39 right. So you really didn't change anything

toolhas4degrees said:
Maybe an issue from 36 to 39 you know 38 is basically 39 right. So you really didn't change anything
Click to expand...
Click to collapse
It's still an install to inactive slot and reboot, regardless if there are any/many differences. The same process also worked from 36 to 38. And there are two threads besides this one with other people who rooted using only boot.img and direct install with alpha. Maybe you had issues because of skipping a version? In any case, the simple steps are the easiest path for most people. Great info in your post for anyone who has problems though.