Develop Bugs

Flashing Guide RoundUp for the LeEco Le Pro 3

Hi everyone, I finally got a little time to put together a guide to flashing stuff on the LeEco Le Pro 3 X727.
This phone comes with an unlockable bootloader out of the box, but we found some ways to get around that.
This guide will help anyone with a new X727 unlock the bootloader, install TWRP and root it.
First, I'd like to give huge props to @dr4stic for his excellent work on making it easier to unlock the phone, and for helping me get back to the US ROM after installing the Chinese rom.
On to the flashing...
If you want to take the long way around, this was the first method used for unlocking the bootloader:
First method is using the stock Chinese ROM & renaming it update.zip, place it in the root directory then use the Update app (or in settings) to select that update, then let it do its thing. It takes a while to boot back up so be patient.
Stock Chinese ROM: https://www.androidfilehost.com/?fid=529152257862681546
Once the Chinese ROM is installed and booted up, enable Developer Options, make sure OEM Unlocking is turned on, then enable USB Debugging.
For these next steps, I'm quoting @dr4stic:
Have ADB/Fasboot tools on your computer (I am not helping you here, it you're lucky, maybe your friends will help)
Make sure you have enabled the developer tools, turned on USB debugging, and authorized your computer on your device (again, I'm not helping with that)
Make sure adb can see your device when you run "adb devices"
Run "adb reboot bootloader"
Run "fastboot devices" to make sure you see your device
Run "fastboot oem unlock-go" to unlock your device temporarily
Run "fastboot oem device-info" to verify unlock status
Your bootloader is now permanently unlocked (well, until you re-lock it on purpose).
The second, and much shorter method, is outlined in @dr4stic's thread here: http://forum.xda-developers.com/le-pro3/development/x727-model-persistent-bootloader-unlock-t3500388
Once your bootloader is unlocked, you'll want to install TWRP.
Here are a couple options for TWRP:
https://www.androidfilehost.com/?fid=529152257862668751 (Chinese version)
https://www.androidfilehost.com/?fid=385035244224398544 (GrossoShop version)
Download either of those (or both if you want to try both), extract them and place the .img file(s) into the folder your ADB & Fastboot files are. To make the flashing easier, rename the twrp files to twrp.img. If you still have your command prompt window open, great! If not, open one again.
Now:
Run "fastboot flash recovery twrp.img" (or whatever the twrp image filename is on your computer) to flash TWRP.
When flashing is complete, reboot into TWRP by pressing and holding Power Button and Volume Up Button at the same time and holding until you see the TWRP splash screen.
If TWRP boots up in Chinese, tap the big button on the lower right to open the language settings and choose the language you can understand.
Alright, now you have an unlocked bootloader and custom recovery installed. Your world has opened up a little bit more
The main problem with installing the stock Chinese ROM is that it does not have Google Play and there is no band 12 support (at least for T-Mobile), but at least bands 2 & 4 still work.
It's easy enough to find methods to get that installed, but I tried the GrossoShop ROM which is a very good ROM, but if you must have band 12, you'll need to read down a little farther.
Link to GrossoShop ROM: https://www.androidfilehost.com/?fid=529152257862686304
Okay, if you chose to use the long route and installed the Chinese ROM, you can still get back to the full US version, complete with all LTE bands. dr4stic is responsible for this gem, and was my way back to US ROMdom.
To go from Chinese or Custom ROM back to Stock US version:
The file is located in his Android File Host space here: https://www.androidfilehost.com/?fid=601275311581036717
It's a little tricky to install, so follow these steps:
1. Enter TWRP and from Advanced Wipe, wipe Dalvick/ART Cache, Cache, System and Data (Leave Internal Storage untouched if that's where you copied the new ROM zip).
2. Install CN5.8.018s-to-US5.8.019s.zip
3. DO NOT REBOOT DIRECTLY AFTER FLASHING (Phone just vibrates forever if you reboot directly after flashing)
4. Go back to TWRP Home, then tap Reboot, then tap System.
The phone should reboot after that, and it might take a while. Then follow the setup process as you normally would and it should go through the Google setup as well.
To install root, I use SuperSU. Sometimes it's kinda hard to find the most up to date version, so I'll post the latest one that I have: https://www.androidfilehost.com/?fid=457095661767120474
There's probably a newer version already, but I haven't looked.
Simply download and flash that file in TWRP, reboot and you're rooted. Easy peasy.
To flash only the US modem to restore band 12 on any ROM:
Download: https://www.androidfilehost.com/?fid=601300970940399635
Extract the zip file and place it in your adb & fastboot folder.
From your abd & fastboot files folder (with the modem image in there too) open a command prompt and run
fastboot flash modem modem-5.8.019s.img
Then reboot your phone.
Keep this file handy because you'll need it every time you flash a ROM that doesn't have a US modem.
With the methods listed above, you should now be able to take a new LeEco Le Pro 3 X727 and unlock the bootloader, install TWRP, flash whatever ROMs you want, and restore US modem.
Again, big big thanks to @dr4stic to getting us to this point for the easy unlock option AND big thanks to all of you folks here in the forums for all of you suggestions, efforts and enthusiasm!
I imagine there will be some refinements and/or corrections to this guide as questions and suggestions come up, so please, if you see something in here that is wrong or unclear, please let me know.

Thank you for the good guide.

well done. Please keep it updated...

suhridkhan said:
well done. Please keep it updated...
Click to expand...
Click to collapse
lilila said:
Thank you for the good guide.
Click to expand...
Click to collapse
Thank you and you're welcome. I'll try to keep this updated as new info or procedures come up :good:

hondajohn88 said:
Hi everyone, I finally got a little time to put together a guide to flashing stuff on the LeEco Le Pro 3 X727.
This phone comes with an unlockable bootloader out of the box, but we found some ways to get around that.
This guide will help anyone with a new X727 unlock the bootloader, install TWRP and root it.
First, I'd like to give huge props to @dr4stic for his excellent work on making it easier to unlock the phone, and for helping me get back to the US ROM after installing the Chinese rom.
On to the flashing...
If you want to take the long way around, this was the first method used for unlocking the bootloader:
First method is using the stock Chinese ROM & renaming it update.zip, place it in the root directory then use the Update app (or in settings) to select that update, then let it do its thing. It takes a while to boot back up so be patient.
Stock Chinese ROM: https://www.androidfilehost.com/?fid=529152257862681546
Once the Chinese ROM is installed and booted up, enable Developer Options, make sure OEM Unlocking is turned on, then enable USB Debugging.
For these next steps, I'm quoting @dr4stic:
Have ADB/Fasboot tools on your computer (I am not helping you here, it you're lucky, maybe your friends will help)
Make sure you have enabled the developer tools, turned on USB debugging, and authorized your computer on your device (again, I'm not helping with that)
Make sure adb can see your device when you run "adb devices"
Run "adb reboot bootloader"
Run "fastboot devices" to make sure you see your device
Run "fastboot oem unlock-go" to unlock your device temporarily
Run "fastboot oem device-info" to verify unlock status
Your bootloader is now permanently unlocked (well, until you re-lock it on purpose).
The second, and much shorter method, is outlined in @dr4stic's thread here: http://forum.xda-developers.com/le-pro3/development/x727-model-persistent-bootloader-unlock-t3500388
Once your bootloader is unlocked, you'll want to install TWRP.
Here are a couple options for TWRP:
https://www.androidfilehost.com/?fid=529152257862668751 (Chinese version)
https://www.androidfilehost.com/?fid=385035244224398544 (GrossoShop version)
Download either of those (or both if you want to try both), extract them and place the .img file(s) into the folder your ADB & Fastboot files are. To make the flashing easier, rename the twrp files to twrp.img. If you still have your command prompt window open, great! If not, open one again.
Now:
Run "fastboot flash recovery twrp.img" (or whatever the twrp image filename is on your computer) to flash TWRP.
When flashing is complete, reboot into TWRP by pressing and holding Power Button and Volume Up Button at the same time and holding until you see the TWRP splash screen.
If TWRP boots up in Chinese, tap the big button on the lower right to open the language settings and choose the language you can understand.
Alright, now you have an unlocked bootloader and custom recovery installed. Your world has opened up a little bit more
The main problem with installing the stock Chinese ROM is that it does not have Google Play and there is no band 12 support (at least for T-Mobile), but at least bands 2 & 4 still work.
It's easy enough to find methods to get that installed, but I tried the GrossoShop ROM which is a very good ROM, but if you must have band 12, you'll need to read down a little farther.
Link to GrossoShop ROM: https://www.androidfilehost.com/?fid=529152257862686304
Okay, if you chose to use the long route and installed the Chinese ROM, you can still get back to the full US version, complete with all LTE bands. dr4stic is responsible for this gem, and was my way back to US ROMdom.
To go from Chinese or Custom ROM back to Stock US version:
The file is located in his Android File Host space here: https://www.androidfilehost.com/?fid=601275311581036717
It's a little tricky to install, so follow these steps:
1. Enter TWRP and from Advanced Wipe, wipe Dalvick/ART Cache, Cache, System and Data (Leave Internal Storage untouched if that's where you copied the new ROM zip).
2. Install CN5.8.018s-to-US5.8.019s.zip
3. DO NOT REBOOT DIRECTLY AFTER FLASHING (Phone just vibrates forever if you reboot directly after flashing)
4. Go back to TWRP Home, then tap Reboot, then tap System.
The phone should reboot after that, and it might take a while. Then follow the setup process as you normally would and it should go through the Google setup as well.
To install root, I use SuperSU. Sometimes it's kinda hard to find the most up to date version, so I'll post the latest one that I have: https://www.androidfilehost.com/?fid=457095661767120474
There's probably a newer version already, but I haven't looked.
Simply download and flash that file in TWRP, reboot and you're rooted. Easy peasy.
With the methods listed above, you should now be able to take a new LeEco Le Pro 3 X727 and unlock the bootloader, install TWRP, and flash whatever ROMs you want.
Again, big big thanks to @dr4stic to getting us to this point for the easy unlock option AND big thanks to all of you folks here in the forums for all of you suggestions, efforts and enthusiasm!
I imagine there will be some refinements and/or corrections to this guide as questions and suggestions come up, so please, if you see something in here that is wrong or unclear, please let me know.
Click to expand...
Click to collapse
Nice one John

seffmono said:
Nice one John
Click to expand...
Click to collapse
Thank you kind sir

"...It's easy enough to find methods to get that installed, but I tried the GrossoShop ROM which is a very good ROM, but if you must have band 12, you'll need to read down a little farther..."
Did I miss the part on how to keep the Band 12 capabilities?

Thanks John, you have been very kind and helpful! So here what my setup is...
1. I installed Chinese ROM on 727.
2. Unlocked bootloader
3. Installed twrp, installed CM13.
I'm happy with this setup. All I want is the T-Mobile band 12 support. Can you please post steps on this part as well?
I see a long process where I can install CN.x.x.to.US.x.x.zip file via twrp. But will this lock the bootloader again and replace it with stock recovery? I didn't know that TWRP can update bootloader so I'm curious. If so I can follow dr4stic's guide to unlock the bootloader and then install twrp and restore the backup of my CM13.
Sent from my LEX720 using Tapatalk

ceo.mtcl said:
Thanks John, you have been very kind and helpful! So here what my setup is...
1. I installed Chinese ROM on 727.
2. Unlocked bootloader
3. Installed twrp, installed CM13.
I'm happy with this setup. All I want is the T-Mobile band 12 support. Can you please post steps on this part as well?
I see a long process where I can install CN.x.x.to.US.x.x.zip file via twrp. But will this lock the bootloader again and replace it with stock recovery? I didn't know that TWRP can update bootloader so I'm curious. If so I can follow dr4stic's guide to unlock the bootloader and then install twrp and restore the backup of my CM13.
Sent from my LEX720 using Tapatalk
Click to expand...
Click to collapse
Flashing the CN-US ROM will not relock the bootloader, so you're safe there.

I followed the shorter version to unlock the bootloader and flashed twrp, and it worked. Once I reboot, and go back in recovery, it goes to stock recovery. I wonder if I need to delete the stock recovery?
Sent from my SM-N930V using Tapatalk

rob_z11 said:
I followed the shorter version to unlock the bootloader and flashed twrp, and it worked. Once I reboot, and go back in recovery, it goes to stock recovery. I wonder if I need to delete the stock recovery?
Sent from my SM-N930V using Tapatalk
Click to expand...
Click to collapse
If you install TWRP from fastboot (fastboot flash recovery twrp.img), it should replace the factory recovery.

rob_z11 said:
I followed the shorter version to unlock the bootloader and flashed twrp, and it worked. Once I reboot, and go back in recovery, it goes to stock recovery. I wonder if I need to delete the stock recovery?
Click to expand...
Click to collapse
In fastboot mode type "fastboot flash recovery recovery.img".... Fastboot boot recovery.img will only boot it and return back to stock after reboot. Flash will make it remain.

seffmono said:
In fastboot mode type "fastboot flash recovery recovery.img".... Fastboot boot recovery.img will only boot it and return back to stock after reboot. Flash will make it remain.
Click to expand...
Click to collapse
i will try that.

I am really interested in flashing my phone with cyanogen but I am a total newbie at this. Could someone post a video tutorial for 727 model?

worries said:
I am really interested in flashing my phone with cyanogen but I am a total newbie at this. Could someone post a video tutorial for 727 model?
Click to expand...
Click to collapse
I hate to speak for everyone here but it's highly unlikely someone will take the time to do that. I suggest you instead do as much research as you can, and make a video for the next person like yourself that prefers it. Speaking from experience most people on XDA will recommend spending as much time reading and learning as you can, and then taking the "leap" on your own. Rooting and unlocking is not for the faint of heart, and a bit of confidence in your own abilities can go a long way! I hope this doesn't sound condescending, but just my advice. Best of luck!

I just installed the stock chinese ROM and when it boots it asks for a password to start Android. Has anyone else seen this. Do you know what the password is?
---------- Post added at 05:55 AM ---------- Previous post was at 05:29 AM ----------
Nevermind. Booted into recovery and formatted the system then it ran fine.
huemedia said:
I just installed the stock chinese ROM and when it boots it asks for a password to start Android. Has anyone else seen this. Do you know what the password is?
Click to expand...
Click to collapse

It had this happen and If i remember correctly, their is a bug in the system and it wont let you past that screen regardless what. Just boot to twrp do a data backup. Format everything else except internal storage and reflash your rom

I followed this guide and flashed the US modem zip on top of stock 19s. However, my SIM is recognized and the "Mobile Networks" setting page is grayed out. However, my phone is still booting with Chinese text in the bootloader. How do I fix this?

Anyone tried this method on stock 20s. Build to unlock bootloader
LeEco Pro3

toanau said:
Anyone tried this method on stock 20s. Build to unlock bootloader
LeEco Pro3
Click to expand...
Click to collapse
I am trying the long way and it's failing (20s)
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device product name: [le_zl1_oversea]
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.083s]
finished. total time: 0.083s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock-go
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.011s
Im dumb, nevermind

How To Guide [Stock ROM] How to root the Snapdragon Moto E 2020

Alexenferman is not responsible for any damages or bricks made to your device. Please do some research if you have any concerns about rooting, its features and downsides. You are choosing to make these modifications, you should blame yourself for any mistakes you make.
Rooting may require a factory reset, please backup your data. Rooting will void your device warrany. By rooting your device, you will not be able to install OTA updates on your phone.
US carrier specific devices such as Verizon and Sprint might not be bootloader unlockable, therefore, not rootable.[/B]
You will need:
Platform Tools (Download from here)
Motorola Drivers
Windows or Linux PC
Bootloader Unlocked Moto E 2020
Your phone must be bootloader unlocked. Rooting your phone and not unlocking the bootloader will result in a soft brick.
Download the latest Magisk Manager APK from Github: https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.0/MagiskManager-v8.0.0.apk
Install the APK file. Make sure to enable "Unknown Sources" in the Settings app
Patching the boot image
To retrieve the boot image in order to patch it, you will need to download the stock ROM for your specific variant.
Download the ROM from your variant from here: https://mirrors.lolinet.com/firmware/moto/ginna/official/
To check which region is your device, go to Settings > About Phone > Software Channel.
After downloading, open the ROM zip file with an archive manager.
Extract the boot.img file only.
Transfer the boot.img file on your phone.
On your phone, open the Magisk app.
Select "Install" > "Install" > "Select and Patch a File"
Locate the boot image in the internal storage on your phone. Select the boot.img file.
Transfer the magisk_patched.img file on your computer.
Rooting the device
Boot the device into fastboot mode by holding the [Volume Down] and [Power] buttons.
Connect your phone to your PC.
On your PC, open a fastboot console window.
Type:
Code:
fastboot devices
Your phone serial number should be displayed along with the word "fastboot" or "device" in the console.
Now, type the following commands:
Code:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
Replace patched_boot.img with the path to your boot image we patched previously.
To reboot the device, type:
Code:
fastboot reboot
Once the device rebooted, open the Magisk app.
If you see the "Magisk is installed" message, you have successfully rooted your device!
You are done!
To view instructions with images, follow these instructions: https://www.alexenferman.com/articles/MotoE2020/root-moto-e-2020-magisk

I can confirm this works, I was about to give up on root or TWRP until I saw this. I'm now rooted, but I still can't find a download link for the latest TWRP for the Ginna model.

Hypercore said:
I can confirm this works, I was about to give up on root or TWRP until I saw this. I'm now rooted, but I still can't find a download link for the latest TWRP for the Ginna model.
Click to expand...
Click to collapse
Me neither, can anyone provide a TWRP for ginna?

I eventually found it after a ton of digging. I've uploaded it to my drive to assure the link stays active for anyone else who may need it.
For peace of mind, here's the VirusTotal scan HERE.
And here is the link to twrp-3.4.0-10_0-ginna HERE.

Hypercore said:
I eventually found it after a ton of digging. I've uploaded it to my drive to assure the link stays active for anyone else who may need it.
For peace of mind, here's the VirusTotal scan HERE.
And here is the link to twrp-3.4.0-10_0-ginna HERE.
Click to expand...
Click to collapse
Confirmed working. Tyvm!

Before I brick my phone. Can anyone confirm if the Tracphone version XT2052DL is rootable?

I'd like to know, too. Can we root our Tracfone XT2025DLs? Anyone successful?

dragonfire0501 said:
Before I brick my phone. Can anyone confirm if the Tracphone version XT2052DL is rootable?
Click to expand...
Click to collapse
Ranthalion75 said:
I'd like to know, too. Can we root our Tracfone XT2025DLs? Anyone successful?
Click to expand...
Click to collapse
I have one too and I've tried to unlock the bootloader however Motorola's website says the bootloader for this phone is not unlockable. It seems like this is what's preventing me from being able to install a different firmware like the stock one or root the device.
I do not know if there is any sort of workaround for this

For some reason on a Moto E, after rescuing using the Moto rescue assistant and then using

you guys can also use OFox Recovery and swipe magisk to root

Thank you. I used this guide to root my Moto E
QPGS30.82-135-2_Root.img

This method works well for QPGS30.82-135-2, but I just attempted it with QPGS30.82-135-9 and unfortunately the Magisk patched boot image will not work. I tried it 3 times, re-patching boot image each time. I suppose Motorola updated something in android to block this?

i can't get this to work at all, i cannot find a matching stock firmware being qpg30.82-135, there's no extra S and nothing else after the 135, got this phone from my motorola insiders rewards and now it's bootlooping after trying the 135-2 patched image

Has anyone been able to root and hopefully install a custom recovery on the lastest update? Mine is QPGS30.82-135-14, and so far I've only been able to get orangefox to boot but couldn't get it to decrypt my storage or install magisk. I tried twrp first, but to no avail, touch screen still doesn't work on it, so now I'm asking on a few different threads for this phone lol. Any help would be great!

Do you know of an updated method to get it to flash correctly? I was able to boot into ofox, but couldn't get it to properly flash. Ended up stuck on a screen that said my phone was unlocked and couldn't be trusted and that it'll reboot in 5 seconds. I don't know much about ofox either, been using twrp for years lol, it looks too different. Anyhow, any help would be appreciate much!
ace120ms said:
you guys can also use OFox Recovery and swipe magisk to root
Click to expand...
Click to collapse

You have to fastboot boot it anyway I don't have this phone anymore so idk

bouyakasha said:
This method works well for QPGS30.82-135-2, but I just attempted it with QPGS30.82-135-9 and unfortunately the Magisk patched boot image will not work. I tried it 3 times, re-patching boot image each time. I suppose Motorola updated something in android to block this?
Click to expand...
Click to collapse
I have the same problem with QPGS30.82-135-9. I can't get it to boot after Magisk patched boot image.

Flashing GSI ROMs onto Your Nord N10 5G

DISCLAIMER!!!
Any lost data, bricked device or issues caused by attempting everything below is not my fault. You assume responsibility of your own actions. This has ONLY BEEN TESTED ON A BE2026!! You have been warned!
What You'll Need
Full Fastboot/ADB installed, system wide helps
-- My method is use the ADB Quick Installer (here: ADB Reborn), then also download the platform-tools and put everything in the ADB Folder (here: Select for your OS)
A GSI ROM
-- So far, only tested /e/OS DeGoogled GSI ROM, which is Android 10 based. ZERO issues thus far (here, arm64 ab: CLICKY) this rom does have issues with Wifi if you patch the boot.img with Magisk. Recommend testing 11 Based GSI's instead like LeOS which is based off of eOS
GAPPS if you so choose
Stock vbMeta.img
-- found here from OnePlus: OnePlus Software ... just select the Nord N10 and click download. or find it on a post here
Video instructions
text instructions
Instructions
1.) Download your selected GSI ROM, GAPPS (if needed), Magisk Manager, stock firmware and make sure ADB is system wide installed
2.) Unlock your bootloader
-- 2a.) Go to Settings, then About phone, tap Build number a bunch to enable developer settings
-- 2b.) Go back and select System, then Developer Settings, enable USB Debugging and OEM Unlock
-- 2c.) Plug in device, give PC developer control, and reboot to bootloader with "adb reboot bootloader"
-- 2d.) Once in bootloader mode, use "fastboot flashing unlock" to unlock the bootloader. Device will wipe and reboot to system
3.) Plug your Device into your computer, open Command prompt and type the following command. It may ask for Debugging permission on device, select yes
Code:
adb reboot bootloader
4.) Now that you're back on the Bootloader, you can use fastboot commands to get started flashing your GSI, first command to enter is
Code:
fastboot reboot fastboot
5.) You're now in Fastbootd, this allows for easier flashing. You now need your vbmeta.img. Use the command below
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
6.) Reboot fastbootd with the command from step 4, then use the commands below once rebooted
Code:
fastboot erase system
fastboot delete-logical-partition product
fastboot flash system GSI.img
fastboot -w
fastboot reboot
7.) You should now have your GSI flashed onto your device! That simple
Do NOT patch the boot.img with Magisk Manager and flash it. It breaks Wifi and Bluetooth on every single GSI Right now. If I find a work around, I will post it here.
How to Root your GSI Based ROM and keep Wifi Working!!
1.) Go to the PixelExperience ROM page and download just the Custom Recovery (here: PixelExperience Post)
2.) Once you have the recovery, reboot to bootloader
Code:
adb reboot bootloader
3.) Flash the recovery
Code:
fastboot flash recovery recovery.img
4.) Reboot to recovery, then download MagiskManager APK from Github (just follow along, I promise, here: Magisk)
5.) Select Apply Update by USB in the Recovery, and sideload with the Magisk APK (it works, trust me)
Code:
adb sideload MagiskManager.apk
6.) Reboot device, select the Magisk Icon and you're Rooted and ROM'd with working Wifi!

Thanks for the nice guide; I currently have a few problems right with installing this resurrection remix GSI:
1) I can't seem to get gapps installed on the GSI. There's never enough space, and due to the weird way the partitions on the N10 work, I can't resize the system partition in order to fit them in. Do you have any solutions for this problem?
2) I've created an overlay for the N10 in order to obtain auto brightness. It works well, but stops working after the first or second reboot. Again, do you have any solutions for this problem?
Thanks in advance.

Generic123. said:
Thanks for the nice guide; I currently have a few problems right with installing this resurrection remix GSI:
1) I can't seem to get gapps installed on the GSI. There's never enough space, and due to the weird way the partitions on the N10 work, I can't resize the system partition in order to fit them in. Do you have any solutions for this problem?
2) I've created an overlay for the N10 in order to obtain auto brightness. It works well, but stops working after the first or second reboot. Again, do you have any solutions for this problem?
Thanks in advance.
Click to expand...
Click to collapse
Personally I don't use any ROMs that have Google in them at all, so flashing gaps is something I don't think I can help you with. You could try my root method, but instead of flashing for root, Flash the gapps zip file. I found the method to root this completely by mistake. And it just happened to be the only way that worked
I did also notice that no matter what I do the screen is exceptionally bright on this phone even at its lowest setting. I have yet to try to find a solution for this because it discovered that the Sim slot on my phone is bad so I went back to my razor phone because now I have to warranty my phone

KaptinBoxxi said:
Personally I don't use any ROMs that have Google in them at all, so flashing gaps is something I don't think I can help you with. You could try my root method, but instead of flashing for root, Flash the gapps zip file. I found the method to root this completely by mistake. And it just happened to be the only way that worked
I did also notice that no matter what I do the screen is exceptionally bright on this phone even at its lowest setting. I have yet to try to find a solution for this because it discovered that the Sim slot on my phone is bad so I went back to my razor phone because now I have to warranty my phone
Click to expand...
Click to collapse
Ah, I used to own the RP2. Sold it because the battery life for my device was so mediocre. Anyways, I don't think it's possible to install GAPPS separately; they have to be integrated into what GSI I want to install or I just can't get them to fit. It seems like the traditional partitions like system have been combined into a single "super" partition. Also, when your N10 comes back from repair, you can try this overlay I've built. It should fix auto-brightness and maybe fixes the brightness curve(so the lowest setting should be much less bright).

Generic123. said:
Ah, I used to own the RP2. Sold it because the battery life for my device was so mediocre. Anyways, I don't think it's possible to install GAPPS separately; they have to be integrated into what GSI I want to install or I just can't get them to fit. It seems like the traditional partitions like system have been combined into a single "super" partition. Also, when your N10 comes back from repair, you can try this overlay I've built. It should fix auto-brightness and maybe fixes the brightness curve(so the lowest setting should be much less bright).
Click to expand...
Click to collapse
I disable auto-brightness entirely, but its still exceptionally bright. Its so weird. I still have it, haven't sent it in yet, so I'll give it a shot soon
Actually just realized its the GSI I'm using, the sim card doesn't work. Gonna try a different gsi and see what happens

I learned a lot with this tutorial. Thank you very much.
I'll begin to try some GSI roms now and see which one adapts best for me. I don't use Google either, so this GSI project was like finding a gold mine next door ha ha ha.
Thank you again.
EDIT: I was too optimistic, because following this guide only takes me to this error
Code:
Resizing 'system_a' FAILED (remote: 'Not enough space to resize partition')
fastboot: error: Command failed
What can I do to avoid this?
Thank you again.

bbabel said:
I learned a lot with this tutorial. Thank you very much.
I'll begin to try some GSI roms now and see which one adapts best for me. I don't use Google either, so this GSI project was like finding a gold mine next door ha ha ha.
Thank you again.
EDIT: I was too optimistic, because following this guide only takes me to this error
Code:
Resizing 'system_a' FAILED (remote: 'Not enough space to resize partition')
fastboot: error: Command failed
What can I do to avoid this?
Thank you again.
Click to expand...
Click to collapse
I suggest this method instead

MetaruSonikkuX said:
I suggest this method instead
Click to expand...
Click to collapse
I tried that method and also failed. I noticed when the script was working that it had the same errors like me: every file the script tried to flash to slot a was followed by FAILED (remote: 'Not enough space to resize partition').
So I decided to restore everything with this tool (and downgrade to Android 11 in the process) and now this guide works as it should. Right now I'm trying to use Havoc OS and the future looks bright
Thank you.

bbabel said:
I tried that method and also failed. I noticed when the script was working that it had the same errors like me: every file the script tried to flash to slot a was followed by FAILED (remote: 'Not enough space to resize partition').
So I decided to restore everything with this tool (and downgrade to Android 11 in the process) and now this guide works as it should. Right now I'm trying to use Havoc OS and the future looks bright
Thank you.
Click to expand...
Click to collapse
Could you post your experience? I tried LoS 18.1 and couldn't get microg installed, then tried AOSP 11 with gapps and kept getting a google authentication error.

MetaruSonikkuX said:
Could you post your experience? I tried LoS 18.1 and couldn't get microg installed, then tried AOSP 11 with gapps and kept getting a google authentication error.
Click to expand...
Click to collapse
You have to use GSIs with GAPPS in them to get gapps for now. no way around it

MetaruSonikkuX said:
Could you post your experience? I tried LoS 18.1 and couldn't get microg installed, then tried AOSP 11 with gapps and kept getting a google authentication error.
Click to expand...
Click to collapse
As KaptinBoxxi says, look for a GSI rom with GAPPS included, otherwise you'll have a lot of problems. I'd start for Pixel Experience but you can look for other roms here: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list

Generic123. said:
Ah, I used to own the RP2. Sold it because the battery life for my device was so mediocre. Anyways, I don't think it's possible to install GAPPS separately; they have to be integrated into what GSI I want to install or I just can't get them to fit. It seems like the traditional partitions like system have been combined into a single "super" partition. Also, when your N10 comes back from repair, you can try this overlay I've built. It should fix auto-brightness and maybe fixes the brightness curve(so the lowest setting should be much less bright).
Click to expand...
Click to collapse
Is there a tutorial on making these that you followed? The one I found on phh wiki didn't go so well

Question Rooting with Magisk failed (FAILED (status read failed (Too many links)))

Hello everyone,
I have a new Xiaomi 11T EEA device, tried rooting it with the following steps, but failed:
- Updated to the latest official MIUI version (13.0.9.0)
- Unlocked bootloader with MiUnlock (shows the unlocked padlock at boot, and also in developer options)
- Downloaded the latest ROM with the updater app in phone (also tried from c.mi.com, same files, checked checksums)
- Used payload dumper at PC to extract the boot.img from the ROM
- Installed latest Magisk Manager (25.2) to the phone
- Pached the boot.img with Magisk
- Installed latest adb and drivers to my PC (restarted it after the install)
And then I tried booting the phone to the patched boot.img (fastboot boot patched_boot.img), but failed (even tried with the stock boot.img, same result):
downloading 'boot.img'...
OKAY [ 3.188s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 11.135s
I tried with my PC, with another notebook, 3 different USB A to C cable, 2 different USB C to C cable (different orientations too), all of the USB ports on the devices, but I got the exact same result.
So far I succeeded with these steps with 3 other Xiaomi phones (Redmi Note7, Mi 9T, Poco F3), but not with this one, and I have no idea what else I can do.
I suspected it has something to do with MediaTek SOC, that's the only meaningful difference I can think of.
Does anyone have any idea what else I can try, or maybe have a working patched boot.img?
Thanks for reading it, have a nice day!

Once the boot modify install with Fastboot, use fastboot reboot.

NOSS8 said:
Once the boot modify install with Fastboot, use fastboot reboot.
Click to expand...
Click to collapse
Maybe I understand it wrong, but I didn't install the boot.img, and don't really want to install it until I am sure I don't soft brink the phone.

s-zoli said:
Maybe I understand it wrong, but I didn't install the boot.img, and don't really want to install it until I am sure I don't soft brink the phone.
Click to expand...
Click to collapse
Obviously if you don't flash the modified boot.img, the phone won't be rooted.
See here (different device but same method).
https://forum.xda-developers.com/t/root-xiaomi-11t-pro-on-latest-miui-13-working.4450535/

NOSS8 said:
Obviously if you don't flash the modified boot.img, the phone won't be rooted.
See here (different device but same method).
https://forum.xda-developers.com/t/root-xiaomi-11t-pro-on-latest-miui-13-working.4450535/
Click to expand...
Click to collapse
It will be rooted until reboot, which is fine for a temporary root and testing things before making it permanent.
From my understanding it should be working either way, booting to it, or flashing right away. Previously I tested the patched boot.img just by booting into it, and worked every time. At the Redmi phone when I tried to flash the boot.img (that was used to boot into and worked), it didn't boot and got stuck to fastboot, and had to flash back the original boot.img.
I read the mentioned thread, it's the same steps I did, except the last booting vs flashing with fastboot.
Am I missing some key information how the booting mechanism works?

s-zoli said:
It will be rooted until reboot, which is fine for a temporary root and testing things before making it permanent.
From my understanding it should be working either way, booting to it, or flashing right away. Previously I tested the patched boot.img just by booting into it, and worked every time. At the Redmi phone when I tried to flash the boot.img (that was used to boot into and worked), it didn't boot and got stuck to fastboot, and had to flash back the original boot.img.
I read the mentioned thread, it's the same steps I did, except the last booting vs flashing with fastboot.
Am I missing some key information how the booting mechanism works?
Click to expand...
Click to collapse
Newer devices have A/B partitions unlike old ones.

NOSS8 said:
Newer devices have A/B partitions unlike old ones.
Click to expand...
Click to collapse
So you are saying that flashing the boot.img replaces both A and B partition and will most probably work, even if booting into it doesn't?

s-zoli said:
So you are saying that flashing the boot.img replaces both A and B partition and will most probably work, even if booting into it doesn't?
Click to expand...
Click to collapse
The .img boot never replaces the partitions, I was answering that you had already rooted other but old devices, that is to say without A/B partitions.
And why do you want to root this model with soc MTK(No or few development for Xiaomi with Mediatek processors)?

NOSS8 said:
The .img boot never replaces the partitions, I was answering that you had already rooted other but old devices, that is to say without A/B partitions.
And why do you want to root this model with soc MTK(No or few development for Xiaomi with Mediatek processors)?
Click to expand...
Click to collapse
The Poco F3 is a newer phone, and I just checked with Treble Check app, that it has seamless system update, therefore A/B system partitions (and so does the 11T).
The reason is the same as for every other phone... customization, automations, battery management... etc.
The things that should be available for power users, not just in fancy gaming phones.
It just happens to have MTK instead of QC (like the 11T Pro).
Do you have any information if this SOC difference can affect the booting and therefore rooting it?

s-zoli said:
The Poco F3 is a newer phone, and I just checked with Treble Check app, that it has seamless system update, therefore A/B system partitions (and so does the 11T).
The reason is the same as for every other phone... customization, automations, battery management... etc.
The things that should be available for power users, not just in fancy gaming phones.
It just happens to have MTK instead of QC (like the 11T Pro).
Do you have any information if this SOC difference can affect the booting and therefore rooting it?
Click to expand...
Click to collapse
MTK=MediaTek
QC=Qualcomm
Change nothing at the root level.
Everything you want to optimize is possible without rooting, moreover you will have to install modules which themselves consume battery.
Except for personalization.

NOSS8 said:
MTK=MediaTek
QC=Qualcomm
Change nothing at the root level.
Everything you want to optimize is possible without rooting, moreover you will have to install modules which themselves consume battery.
Except for personalization.
Click to expand...
Click to collapse
Sure, you're right, but I already started the rooting process, the bootloader is unlocked, so I already lost a few things (Google Pay, Netflix... etc).
The only way out is re-lock the bootloader or find a way to install Magisk and modules for it.
We deviated a bit from the original question...
I haven't found any source of information what does "Too many links" error means?
Also I didn't find any information if I can easily get back to original state if flashing the supposedly good pached boot.img doesn't work. (bootloop, stuck at fastboot... etc)
My way of being somewhat sure it works was first booting to it, but that doeasn't work now, and it's suspicious for me that the flashing won't work either.

To have the play store certified, use Magisk + zygisk.
https://topjohnwu.github.io/Magisk/
https://www.droidwin.com/fix-status-read-failed-too-many-links/
Once the boot modify install with Fastboot, use fastboot reboot.

Long story short... I just went for it and flashed the patched boot.img, and it's working just fine.
I don't know why it didn't want to boot, but flashing worked and now I have root access.

NOSS8 said:
Obviously if you don't flash the modified boot.img, the phone won't be rooted.
See here (different device but same method).
https://forum.xda-developers.com/t/root-xiaomi-11t-pro-on-latest-miui-13-working.4450535/
Click to expand...
Click to collapse
thats snapdragon, and this is mediatek
will this work with mediatek? without specifying a/b partitions?
Code:
fastboot flash boot patched_boot.img

bluviper said:
thats snapdragon, and this is mediatek
will this work with mediatek? without specifying a/b partitions?
Code:
fastboot flash boot patched_boot.img
Click to expand...
Click to collapse
Check:
https://www.xda-developers.com/how-to-check-android-device-supports-seamless-updates/
getprop ro.build.ab_update
Then you will know which command to choose.

NOSS8 said:
Check:
https://www.xda-developers.com/how-to-check-android-device-supports-seamless-updates/
getprop ro.build.ab_update
Then you will know which command to choose.
Click to expand...
Click to collapse
i have the a/b partition

bluviper said:
i have the a/b partition
Click to expand...
Click to collapse
So,use
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
or
fastboot flash boot_ab patched_boot.img
fastboot reboot

I just flashed without _a _b or _ab and it flashed still to both slots

oneplus 5T, did badly something? modem files looks corrupted

hi guys
I have a problem :
I tried to do this manipulation to get freemobile ISP using the following one, on a oneplus 5T
howerver, I tried several manipulation,such as :
[Guide]Activate VoLTE/VoWiFi OOS 11(OB1&OB2)
Hi everyone. /* * Your warranty is void. Or vaild, probably? * * I am not responsible for bricked devices, dead SD cards, Ebolation X, * thermonuclear war, or the current economic crisis caused by you following * these directions. YOU are...
forum.xda-developers.com
until at reboot :
blackscreen + fixed blue led.
I understood it wrote on the modem partition, probably the wrong .mbn files.
I tried to do a wipe cache firstly, then to totally factory reset the device.
Then, it started to bootup android to almost end of user session.
wifi and cell modules are not working right now.
Well, it looks like modem drivers are not the right ones.
problem #1: without internet connection, the oxygen oneplus android stock rom, is stuck on installation wizard.
problem #2: phone is not bootloader-unlocked, which means that I cant install lineageos/twrp.
I tried to do an adb sideload with OEM stock rom zip file several times. It finishes the operation well, but again : at startup of android session, wizard is blocked and doesnt go ahead, sim not detected nor wifi networks detected
how could I fix it?
I thank you vm

Your best bet would probably be MSM, see the guide here and grab the tool from the OP community server in case AFH doesn't work.

Nimueh said:
Your best bet would probably be MSM, see the guide here and grab the tool from the OP community server in case AFH doesn't work.
Click to expand...
Click to collapse
thank you for your answer
unfortunately the corrupted modem drivers block cell+wifi at google startup wizard. everything looks like stuck
bootloader is not unlocked, so I can only adb sideload.
adb sideload worked only with OnePlus5TOxygen_43_OTA_069_all_2010292144_76910d123e3940e5.zip
even into that file it seems that there is the image file for right modem configuration and bin bloobs I guess
even with that, after the end/reboot, android keeps blocked at google installation
I tried the different android images of the link you gave me : none is about to be adb sideloaded (I guess that oneplus made a whitelist of md5 or other kind of file signature to avoid it)
each time Im trying a new android zip file, adb sideload says :
[email protected]:/home/user/$ adb sideload OnePlus_5T_OxygenOS_4.7.6.zip
Total xfer: 0.00x
how could I get this solved?
is it possible to bypass google assistant and cutitoff before starting?

Not sure why you're talking about cell or wifi - MSM tool doesn't need either of those, you simply need to install the drivers and use your PC with the cable. Locked bootloader doesn't matter either and MSM is EDL mode, nothing to do with sideload.
Read + follow the guide I linked

Nimueh said:
Not sure why you're talking about cell or wifi - MSM tool doesn't need either of those, you simply need to install the drivers and use your PC with the cable. Locked bootloader doesn't matter either and MSM is EDL mode, nothing to do with sideload.
Read + follow the guide I linked
Click to expand...
Click to collapse
hey
thank you for your reply
I tried and this putted back the oneplus original firmware
BUT
as I said previously I tried on to upgrade with the xda link above, to get volte enabled on oneplus 5T, using that efstools software command
after few attemps and lot of phone reboots without success of volte, I tried a last one
after rebooting, phone was just black screen+ blue fixed led
but since that moment, I had absolutely no way to get back my modem files
even doing adb sideload with the official oneplus recovery zip, it refreshed the phone from factory reset ; but without any connection
thanks to your new "how to" given in link, Im able now to start an android whom doesnt requires internet connection to use it.
BUT
there is still no qualcomm backup restored.. means that it doesnt see wifi nor cellular connection
Im wondering about how to solve it :
fastboot flash modem NON-HLOS.bin
but, even with oem bootloader unlocked in the developper options :
fastboot flash modem NON-HLOS.bin
Sending 'modem' (108724 KB) OKAY [ 3.267s]
Writing 'modem' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
how could I fix it?
thank you vm

Just use MSM and stop messing with whatever it is you're messing with. You can NOT fastboot one of those MSM roms from the links, you HAVE to use the MSM tool.
MSM will restore your device to a stock OOS version and if VoLTE doesn't work on stock then just leave that alone, try a custom rom or switch to a provider that offers it.

I was able to unlock bootloader finally
but anyway, I flashed twice with the links/tutos you gave me, it doesnt brings back working files for modem

lm8lm8 said:
I was able to unlock bootloader finally
but anyway, I flashed twice with the links/tutos you gave me, it doesnt brings back working files for modem
Click to expand...
Click to collapse
I don't know what exactly you are doing, but you're not supposed to "flash" anything - you're supposed to use the MSM tool to restore the device to it's original state. I'm pretty sure it's not even possible for the modem files to not get restored, but maybe I'm wrong. In which case I don't know how else to help you, sorry

Nimueh said:
I don't know what exactly you are doing, but you're not supposed to "flash" anything - you're supposed to use the MSM tool to restore the device to it's original state. I'm pretty sure it's not even possible for the modem files to not get restored, but maybe I'm wrong. In which case I don't know how else to help you, sorry
Click to expand...
Click to collapse
okay guys, here is a little message to explain what happened
well, in a way I wanted, on OnePlus 5T, to enable volte or/and vowifi, for my ISP Free Mobile...
as several messages reported it (1), it was not an impossible operation. Mainly from xda howto, here is what happened.
1. with last andro running on 5T, I downloaded both apk to answer the original prcoess, with PDC software (whom is not maintained anymore)
while stuck on PDC detecting my device but blocking on an error message : dunno if the software is bugged or just new OT software doesnt allow it.
2. get back on the latest howto, running EFS command line howto (2). It was supposed to work. After several injection plus different reboots without volte working, a last one has been made but.. at reboot, the screen was totally black, with blue fixed led.
I factory reset it, wiping out everything (already saved before), then android was starting back but.. without any wifi/bt/cellular! It was stuck at the end of installation wizard : google doesnt allow usage of this phone, with last update, without connecting to google account, it forbidd it unfortunately.
3. I had so to find back a way to get back android+wifi/bt/cell : I spent hours and days looking for a solution to restore it ; I had no unlocked bootloader, and I finally discovered a way with Oneplus after sales tools (3), that made me able to get a new refreshed old android booting well, but still no wifi/cell/bt. Was however able, so, to unlock the bootloader.. with hope another android image from oneplus could work and bring back my cell working !
4. I was wrong.. so I opened a thread on XDA. Then I remind that on frenchy lafibre forum (dedicated to telecommunications), someone attempted to do so weeks ago... and was also stuck while, after (2) first operation, at reboot wifi/bt/cell were not working anymore too, with others feedbacks showing it! (4). Unfortunately, the link shown in the forums of onplus brings to "internal server error". After that, I did a little investigation to understand that the modem files has to be flashed again. Modem, wifi, BT. I did it several times, thinking fastboot was able to apply directly .img on the destinated partition of phone. Was wrong : erase the partition was necessary! (5)
fastboot erase modemst1
fastboot erase modemst2
fastboot erase modem
fastboot flash modem NON-HLOS.bin
fastboot erase oem_stanvbk
fastboot flash oem_stanvbk static_nvbk.bin
fastboot erase bluetooth
fastboot flash bluetooth BTFM.bin
Was then about to get back cell/wifi/BT ! but the tools of OnePlus doesnt do that.. EFS restoration is really something you have to backup before, and most brand doesnt restore it..
1:
Tutoriel - Activer la VoLTE et VoWifi sur OnePlus 6/7/8
Tutoriel - Activer la VoLTE et VoWifi sur OnePlus 6/7/8
lafibre.info
[Guide] VoLTE + VoWiFi working for German carriers
[UPDATE] Updated QPST version + new how to Exciting news, jamal2367 from https://jamal2367.com has developed a way to get VoLTE + VoWifi working for many countries + carriers. If you are on Vodafone and you are having problems with...
forum.xda-developers.com
2:
[Guide]Activate VoLTE/VoWiFi OOS 11(OB1&OB2)
Hi everyone. /* * Your warranty is void. Or vaild, probably? * * I am not responsible for bricked devices, dead SD cards, Ebolation X, * thermonuclear war, or the current economic crisis caused by you following * these directions. YOU are...
forum.xda-developers.com
3:
[OP5T][LATEST 9.0.11] Collection of unbrick tools
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
OnePlus 5T Unbricking Tool
OnePlus 5T Unbrick tool Here is the Oneplus 5T Unbricking Tool files provided by OnePlus during a Remote Session Download No Password Needed OxygenOS 4.7.4 (Nougat 7.1.1) OxygenOS 5.1.3 Thanks to Titokhan OxygenOS 5.1.7 (Oreo 8.0.1) Drivers...
forum.xda-developers.com
OnePlusCommunityServer
This webserver contains various resources that may be useful to the OnePlus community.
onepluscommunityserver.com
4: https://lafibre.info/4g/tutoriel-activer-la-volte-et-vowifi-sur-oneplus-7/msg782650/#msg782650
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
5. https://droidwin.com/how-to-fix-corrupt-efs-no-imei-network-issues/