Database Info

Official OTA Update Links and OTA updating modified systems

Don't forget to thank me and Radii it means a lot to us!
Click to expand...
Click to collapse
Upon discovering the reason people being given an error trying to flash OTAs in my TWRP recovery image I decided I would come up with a work around while I work out a way to fix it.
The following solution is group work between me and Radii.
If you came here just for OTA links then click HERE
Click below spoiler if you haven't installed TWRP on your device and you want to OTA update and then install TWRP.
First you need to download the version you would like, in theory you could backdate although this hasn't been tested and it may misbehave. For example the latest version as of 16/10/2015, build number cm-12.1-YOG4PAS38J.
On the spread sheet you will need two files, the fastboot and the signed. In the fastboot ZIP there is a file called recovery.img. Copy this to your android SDK platform tools folder. Now with the signed ZIP you either copy that to the same folder (platform-tools). Put your phone into fastboot mode and type.
Code:
fastboot -i 0x2b4c boot recovery.img
Or the name of the recovery if you renamed it.
Your phone will boot into Cyanogen OS Recovery. From there click Apply Update (Top option) and click ADB Sideload. Then type,
Code:
adb sideload cm-12.1-YOG4PAS38J-ham-signed.zip
Or whatever you renamed it to.
Reboot and you're done! Now you'll need to install TWRP to flash things like SuperSU and Xposed.
To install TWRP you need to download the latest TWRP image from HERE move that to platform-tools and type (with your phone in fastboot mode/bootloader mode of course)
Code:
fastboot -i 0x2b4c flash recovery "recovery.img"
Changing the name in the quotations to the name of the recovery and removing the quotes.
Click below spoiler if you have installed TWRP on your device and you want to OTA update and restore/preserve TWRP
Do the same as above, I have discovered it's impossible to preserve because Cyanogen will auto-write it's own recovery to the recovery parition.
Nerdy stuff
If you're wondering why you can't OTA without going through all this then it's because Cyanogen OS will do checks to see if the System has been r/w mounted. If so then it will stop all OTAs from installing. Simple when you think about it.
FAQ
Q: Why isn't TWRP still installed after installing the OTA? A: Because Cyanogen OS will write over the recovery partition with Cyanogen Recovery
Q: Will I lose all my data? A: Don't wipe and no, you can dirty flash to preserve data.

Thanks for your work, really appreciated.
However, it sucks a bit that we have tons of work just for the OTA updates if we want root, i guess we should annoy Cyanogen to add a Superuser option to CyanogenOS...

othe01 said:
Thanks for your work, really appreciated.
However, it sucks a bit that we have tons of work just for the OTA updates if we want root, i guess we should annoy Cyanogen to add a Superuser option to CyanogenOS...
Click to expand...
Click to collapse
It's designed to be shipped with devices like Samsung or LG's ROMs they'll never add that option.
Sent from my Z1 using Tapatalk

Breadcrust said:
It's designed to be shipped with devices like Samsung or LG's ROMs they'll never add that option.
Sent from my Z1 using Tapatalk
Click to expand...
Click to collapse
Why not? root is a normal option in CyanogenMod, why wouldn´t the "commercial" edition not support it? I see no reason they can´t add it to PrivacyGuard.
Here one of the forum admins said hes telling the team to add it -> http://community.cyngn.com/t/reques...-thethering-and-inbuilt-superuser-access/97/2

Breadcrust,
did you try this method used for oneplus one phones with CyanogenOS?
https://forums.oneplus.net/threads/flashable-zip-cm12-enable-integrated-superuser.297089/
https://github.com/julian-klode/bacon-superuser/
From what i´ve read OTA updates are working with it and all we need to do is update the recovery after installing a new ota, the script on github creates the patched boot files automatically, we just have to change the config to use the ZUK files.
All theory tho...as i don´t have my phone yet.

othe01 said:
Breadcrust,
did you try this method used for oneplus one phones with CyanogenOS?
https://forums.oneplus.net/threads/flashable-zip-cm12-enable-integrated-superuser.297089/
https://github.com/julian-klode/bacon-superuser/
From what i´ve read OTA updates are working with it and all we need to do is update the recovery after installing a new ota, the script on github creates the patched boot files automatically, we just have to change the config to use the ZUK files.
All theory tho...as i don´t have my phone yet.
Click to expand...
Click to collapse
I'll look into it at sunrise it currently 3:23AM here so can't do it now
P.s thanks for waking me :3
Sent from my Z1 using Tapatalk

@othe01
No COS device allows you to flash incremental OTA if your /system partition is modified. Your quoted package puts compatible su binary in /system & flashes boot-debuggable kernel so that root can be achieved from both app & ADB. It has nothing to do with OTA. Your only choice is to get the signed zip & flash it manually.
@Breadcrust
It would be nice to put incremental OTA zip links too. My posts regarding OTA links also contain them.
:highfive:

Titokhan said:
@othe01
No COS device allows you to flash incremental OTA if your /system partition is modified. Your quoted package puts compatible su binary in /system & flashes boot-debuggable kernel so that root can be achieved from both app & ADB. It has nothing to do with OTA. Your only choice is to get the signed zip & flash it manually.
@Breadcrust
It would be nice to put incremental OTA zip links too. My posts regarding OTA links also contain them.
:highfive:
Click to expand...
Click to collapse
sounded different here: [FLASHABLE ZIP] [CM12] Enable integrated superuser
But is prolly just a misunderstanding from my side.
How exactly does CyanogenOS check if System is modified and can´t we patch the check with an xposed module?

@othe01
He must used the signed zip to update. Regarding OTA faliure, I've discussed the issue here: http://forums.yuplaygod.com/index.php?threads/15124/
You need to registered in the forum to read, so I've uploaded a PDF of the same: https://drive.google.com/file/d/0B9zZIJPXbMsubkFBYmZ4eGtMQjQ/view?usp=sharing
I personally own OnePlus One & YU Yureka so already have a good experience with these things.
The whole procedure is clearly explained - no 'Xposed' module can bypass it. You can, in theory, deploy a file based OTA (I've already requested it through YU developers) instead of block based OTA or patch the update-binary to return always true (unmodified) value while checking the state of partitions.
:good:

@Titokhan I will post them later
Sent from my Z1 using Tapatalk

@Breadcrust can you please help me if you can, I have problem flashing any ota (increments or full), it return error " this package is for device:Z1 this device is k9", all ota was installed directly till unlocked bootloader and root .

aaswar said:
@Breadcrust can you please help me if you can, I have problem flashing any ota (increments or full), it return error " this package is for device:Z1 this device is k9", all ota was installed directly till unlocked bootloader and root .
Click to expand...
Click to collapse
Issue is noted method is in post
Sent from my Z1 using Tapatalk

@Breadcrust
cm-12.1-20150805-EXPERIMENTAL-YOG4PAP1CG-ham: http://forum.xda-developers.com/showpost.php?p=63390843&postcount=223

@Breadcrust
for clarification:
-isn't "cm-12.1-YOG4PAS38J-ham-signed-fastboot.zip" is the same as "cm-12.1-YOG4PAS38J-ham-signed.zip", but with the recovery image include, can sideload this file using the same process you mentioned?
-if the phone is rooted, boot with the COS recovery and sideload the "cm-12.1-YOG4PAS38J-ham-signed.zip" will not work as the system partition is already been modified by the root process, am I right?

aaswar said:
@Breadcrust
for clarification:
-isn't "cm-12.1-YOG4PAS38J-ham-signed-fastboot.zip" is the same as "cm-12.1-YOG4PAS38J-ham-signed.zip", but with the recovery image include, can sideload this file using the same process you mentioned?
-if the phone is rooted, boot with the COS recovery and sideload the "cm-12.1-YOG4PAS38J-ham-signed.zip" will not work as the system partition is already been modified by the root process, am I right?
Click to expand...
Click to collapse
re: above
if using cos recovery and sideload via abd or from file the full signed version , and your have root, it will work, root will be lost though.
fastboot zip has recovery signed doesn't. you need to flash recovery extracted from the fastboot zip and then flash the signed full zip using cos either using abd or sideload file onto system

I flash the rom, but when I insert CDMA SIM into slot one, there is no signal
and there is no option to choose band from the menu.
would you please instruct on how to get CMDA works?

@taitai
As you can see here, it is not an CDMA device.

As regards technical faults as well we're unable to help in most cases as ROMs are from Cyanogen and unedited.
Sent from my Z1 using Tapatalk

I have a chinese version of Z1 and it has CDMA capability

None of them do. They're the exactly the same under the hood.
Sent from my Z1 using Tapatalk

[ROOT] Moto X Style - XT1572 BR - Marshmallow

Hello guys!
I make my own ROOT (systemless, thanks for Chainfire) images for Moto X Style with Marshmallow (build MPH24.49-18). Its use "experimental" systemless SuperSU version 2.56 - more info on http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2. No need replace bootloader or recovery. Still need unlocked booloader.
Because TWRP didn't work in this version of bootloader (0xA048), I cooked "su.img" in a Linux box and used "/data/local/tmp" as bridge (accessible by ADB).
WARNING! I am not responsible for any harm on your phone. When you're not sure if you can do it, leave it!
For use, you need
1) unlocked bootloader.
2) if your bootloader not unlocked, make sure you have copy of your data, because this process will erase your device.
3) install ADB and FASTBOOT on your pc using minimal ADB or Android SDK.
4) install ADB drivers from Motorola or Universal ADB.
5) download provided files.
6) download SuperSU ver. 2.56 from http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344.
Steps:
1) extract files in a folder of your choice (su.img, boot.img).
2) extract Superuser.apk from SuperSU-v2.56-20151030013730.zip from common folder.
3) enable USB debugging on Android.
4) connect your device on pc.
5) open a command prompt in a new folder.
6) type "adb push su.img /data/local/tmp" without quotes.
7) type "adb install Superuser.apk" without quotes.
8) now reboot your device into fastboot mode by typing "adb reboot bootloader".
9) type "fastboot flash boot boot.img" without quotes.
10) type "fastboot reboot" without quotes.
And enjoy!
Now you have a rooted MotoX Style Marshmallow. To apply any OTAs, you only need reflash stock boot.
Ivan

Do I still need to unlock the bootloader in order to root this device

ivcarlos said:
2) write "boot.img" with fastboot.
Click to expand...
Click to collapse
What do you mean? Como assim?

Oh I see thanx partner

How can I copy "su.img"?
If no Root I can not copy into data/local/tmp.

Marccelllorzn said:
How can I copy "su.img"?
If no Root I can not copy into data/local/tmp.
Click to expand...
Click to collapse
Restart in bootloader
1) adb push su.img /data/local/tmp
2) fastboot flash boot boot.img
3) Install SuperSu ver 2.56 apk

would this work on xt1575 us? if not why?..... i mean .. why the indian MM would work 4 any variation and this one would not?

zittorb said:
would this work on xt1575 us? if not why?..... i mean .. why the indian MM would work 4 any variation and this one would not?
Click to expand...
Click to collapse
Yes, work with XT1575.

I dont test on another device, only on XT1572.
After 24h, no errors, work like a charm.
With this approuch you dont need to downgrade bootloader.

assuming that we need a "CLEAN", unrooted system for this as advised by @Chainfire in his instructional post regarding this experimental root method!
Instructions
You must absolutely re-flash your stock /system partition, or the separate root instances will interfere with each other. The installer for this experiment will not clean up old root files.
- Flash stock /system
- Flash the attached boot image
- Flash the attached SuperSU ZIP in TWRP
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2
Also you should probably make a point of mentioning that this method is an experiment.
Aside from this, let me take my "high-visibility" jacket off, along with my "safety helmet" and say thank you very much for taking the time to do this for us all @ivcarlos! You are a gentleman!

Is Android pay confirmed working with this root method?
Sent from my XT1575 using Tapatalk

@bb12489
I dnt know because I dnt use this feature.
@Doktaphex
I dnt mentioned this - clean and unrooted system - because after apply OTA on XT1572, custom recovery (TWRP) didn't work anymore. By the way, I assume no root and clean system.
I know this method is "experimental", but it's best at this time, without downgrade bootloader (not safe).
Thanks for comments! I make this work because I need root and I dnt like to make heavy changes on smart...
In this way, I share for everyone.

ivcarlos said:
@bb12489
I dnt know because I dnt use this feature.
@Doktaphex
I dnt mentioned this - clean and unrooted system - because after apply OTA on XT1572, custom recovery (TWRP) didn't work anymore. By the way, I assume no root and clean system.
I know this method is "experimental", but it's best at this time, without downgrade bootloader (not safe).
Thanks for comments! I make this work because I need root and I dnt like to make heavy changes on smart...
In this way, I share for everyone.
Click to expand...
Click to collapse
Could you please give me the link that how you created modified boot.img ? I want to make it work on Indian XT1572

@gulshanstrider
I make boot image based on post of Chainfire (http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344), with applying steps:
1) unpack stock "boot.img";
2) patch sepolicy;
3) edit "init.rc" and "init.environ.rc";
4) edit "file_contexts";
5) repack "boot.img".
Use Chainfire generated images with model.
Without TWRP, I cooked "su.img" in a Linux box, and use "/data/local/tmp" with bridge.

ivcarlos said:
@gulshanstrider
I make boot image based on post of Chainfire (http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344), with applying steps:
1) unpack stock "boot.img";
2) patch sepolicy;
3) edit "init.rc" and "init.environ.rc";
4) edit "file_contexts";
5) repack "boot.img".
Use Chainfire generated images with model.
Without TWRP, I cooked "su.img" in a Linux box, and use "/data/local/tmp" with bridge.
Click to expand...
Click to collapse
wifi not working now please tell me how to revert everything back pleaseeee help !!!!

Shishir Singhal said:
wifi not working now please tell me how to revert everything back pleaseeee help !!!!
Click to expand...
Click to collapse
Your model is XT1575 or XT1572?

Shishir Singhal said:
wifi not working now please tell me how to revert everything back pleaseeee help !!!!
Click to expand...
Click to collapse
@Shishir Singhal
Whats your model and version?
I make this image for my XT1572 (BR, dual) and wifi working.
To revert back you must write back stock boot.img version. On first post I provided stock of XT1572 RETLA 6.0 (my base).
On my device no issues at all.

Not working on my XT1572
Didn't work on my XT1572 with Android 6.0.
Enable root option is disabled in SuperSU with a message saying that system-less root is currently not supported.

ivcarlos said:
@Shishir Singhal
Whats your model and version?
I make this image for my XT1572 (BR, dual) and wifi working.
To revert back you must write back stock boot.img version. On first post I provided stock of XT1572 RETLA 6.0 (my base).
On my device no issues at all.
Click to expand...
Click to collapse
Thank u for quick reply got it working by flashing NON-HLOS.bin now everything is working fine thank u soo much

roberto.marcal said:
Didn't work on my XT1572 with Android 6.0.
Enable root option is disabled in SuperSU with a message saying that system-less root is currently not supported.
Click to expand...
Click to collapse
What version of SuperSU you was installed?
You put "su.img" into "/data/local/tmp"?
If you enter in shell with ADB, ls command show "su" directory in root? Image was monted successfully?

Stock recovery and boot collection

In case, you want the stock boot/recovery to install Magisk like me, you can get it out of the firmware.zip inside the OTA zip, which you can download from HTC server using the link:
Taiwan model 1.10.709.23:
http://fotadl-az.htc.com/secure/OTA....05.709.12_release_517077z7dxrjhjj6rk2y9h.zip
Taiwan model 1.23.709.3:
http://fotadl-az.htc.com/secure/OTA....10.709.23_release_518569sr63mm3mtji85ret.zip
Hong Kong model 1.10.400.23
http://fotadl-az.htc.com/secure/OTA....05.400.13_release_517158ov5r8lbbi6tc9m38.zip
I have extracted the recovery.img and boot.img for Taiwan version. If someone doesn't want to extract it themselves, let me know through PM. I can send it to you.

devsk said:
In case, you want the stock boot/recovery to install Magisk like me, you can get it out of the firmware.zip inside the OTA zip, which you can download from HTC server using the link:
http://fotadl-az.htc.com/secure/OTA....05.709.12_release_517077z7dxrjhjj6rk2y9h.zip
I have extracted the recovery.img and boot.img. If someone doesn't want to extract it themselves, let me know through PM. I can send it to you.
Click to expand...
Click to collapse
Desk
Thank you your work .Is this version recovery work for HTC U 11 PLUS China. Mainland version 2Q4D200.THANK YOU again.

Would you know how to enable volte and wifi calling?

cameljockey1 said:
Would you know how to enable volte and wifi calling?
Click to expand...
Click to collapse
Not yet.

Perfectionalism said:
Desk
Thank you your work .Is this version recovery work for HTC U 11 PLUS China. Mainland version 2Q4D200.THANK YOU again.
Click to expand...
Click to collapse
I would like to know this too. I have the Chinese U11+ and I'm desperately looking for the boot.img and recovery.img for this variant (2Q4D200)
Thanks in advance!

Prot02018 said:
I would like to know this too. I have the Chinese U11+ and I'm desperately looking for the boot.img and recovery.img for this variant (2Q4D200)
Thanks in advance!
Click to expand...
Click to collapse
screenshot of your software information page in settings showing "Software number" (e.g. 1.10.709.23 for me, it would be 1.xx.1405.xx for you).

devsk said:
screenshot of your software information page in settings showing "Software number" (e.g. 1.10.709.23 for me, it would be 1.xx.1405.xx for you).
Click to expand...
Click to collapse
Here's the screenshots! Many thanks devsk.

Perfectionalism said:
Desk
Thank you your work .Is this version recovery work for HTC U 11 PLUS China. Mainland version 2Q4D200.THANK YOU again.
Click to expand...
Click to collapse
Prot02018 said:
I would like to know this too. I have the Chinese U11+ and I'm desperately looking for the boot.img and recovery.img for this variant (2Q4D200)
Thanks in advance!
Click to expand...
Click to collapse
OCEAN_M_DTWL
modelid: 2Q4D20000
cidnum: HTCCN701
OTA zip link (1.05.1405.16 - 1.03.1405.1)
https://drive.google.com/file/d/1Q3Kz88fJm1NA6ccPcb1jbQstZYWASnFO/view?usp=sharing

nenebear said:
OCEAN_M_DTWL
modelid: 2Q4D20000
cidnum: HTCCN701
OTA zip link (1.05.1405.16 - 1.03.1405.1)
https://drive.google.com/file/d/1Q3Kz88fJm1NA6ccPcb1jbQstZYWASnFO/view?usp=sharing
Click to expand...
Click to collapse
Thanks nenebear. Is this is the OTA file to go from stock 1.03.1405.1 to latest 1.05.1405.16 ?
I found the RUU's for the version of my phone also. Can anybody here confirm that the stock recovery zip file found at the following link will allow me to go back to stock recovery if I decide to flash TWRP?
https://androidfilehost.com/?w=search&s=OCEAN_M_DTWL
Thanks guys

Please help me!
I have unlocked my bootloader, installed twrp. Unfortunately, twrp is worthless since it can not be used as it seems...
Now I wonder if I can use this guide to root my phone:
"1. Download http://fotadl-az.htc.com/secure/OTA_...bbi6tc9m38.zip
Edit / Important: Read next post down below before Step 2/
2. Extract firmware.zip.
3. Extract boot.img from firmware.zip from step 2 and transfer to the /sdcard.
4. Install Magisk Manager and select Beta channel
5. Click install and choose to use "patch the stock boot image" method. It will browse you to /sdcard. Choose the boot.img from step 3. After its done, it will give you path of patched boot image.
6. Transfer the patched boot image from step 5 to PC using 'adb pull'
7. Boot the phone into download mode and flash the patched boot image.
8. Reboot and enjoy!!"
Where/how can I get the correct boot.img för my device?
My version is "1.10.401.23 9.0_g CL991677 release-keys" and none of the download links match my version? Or can I use some of them anyway?
I would be very happy and thanksful if I got help so I can get root access!
Best regards/ David

Davil_79 said:
Please help me!
I have unlocked my bootloader, installed twrp. Unfortunately, twrp is worthless since it can not be used as it seems...
Now I wonder if I can use this guide to root my phone:
"1. Download http://fotadl-az.htc.com/secure/OTA_...bbi6tc9m38.zip
Edit / Important: Read next post down below before Step 2/
2. Extract firmware.zip.
3. Extract boot.img from firmware.zip from step 2 and transfer to the /sdcard.
4. Install Magisk Manager and select Beta channel
5. Click install and choose to use "patch the stock boot image" method. It will browse you to /sdcard. Choose the boot.img from step 3. After its done, it will give you path of patched boot image.
6. Transfer the patched boot image from step 5 to PC using 'adb pull'
7. Boot the phone into download mode and flash the patched boot image.
8. Reboot and enjoy!!"
Where/how can I get the correct boot.img för my device?
My version is "1.10.401.23 9.0_g CL991677 release-keys" and none of the download links match my version? Or can I use some of them anyway?
I would be very happy and thanksful if I got help so I can get root access!
Best regards/ David
Click to expand...
Click to collapse
I think yours is the Europe model. If so, download the following ZIP:
https://androidfilehost.com/?fid=889964283620770441
Extract firmware.zip from it, and you will then extract boot.img from the firmware.zip, and then, patch that in magisk manager. Hope that helps!

devsk said:
I think yours is the Europe model. If so, download the following ZIP:
https://androidfilehost.com/?fid=889964283620770441
Extract firmware.zip from it, and you will then extract boot.img from the firmware.zip, and then, patch that in magisk manager. Hope that helps!
Click to expand...
Click to collapse
Many thanks!
I should have a European model. If I'm looking in the Download mode:
"htc_ocmdugl PVT S-ON
LK-1.0.0.0000
RADIO 8998-002772-1711021849
OpenDSP-UNKNOWN
OS 1.10.401.23
Nov 25 2017.01: 13: 33 (991677)"
If something goes wrong, or if it would be the wrong boot.img, can I flash a complete RUU via adb fastboat so I dont brick my phone?

Davil_79 said:
Many thanks!
I should have a European model. If I'm looking in the Download mode:
"htc_ocmdugl PVT S-ON
LK-1.0.0.0000
RADIO 8998-002772-1711021849
OpenDSP-UNKNOWN
OS 1.10.401.23
Nov 25 2017.01: 13: 33 (991677)"
If something goes wrong, or if it would be the wrong boot.img, can I flash a complete RUU via adb fastboat so I dont brick my phone?
Click to expand...
Click to collapse
That link matches your version exactly. You should be good with boot.img from that ZIP. Make backup of your stuff and be very careful with commands you fire...

devsk said:
That link matches your version exactly. You should be good with boot.img from that ZIP. Make backup of your stuff and be very careful with commands you fire...
Click to expand...
Click to collapse
Hmm.. It is 25 pcs. compressed zip-files in this download.
In one of the zip there is "boot_signed.img"
It must be it. But when I try to unzip it doesn't work. It says the file is corrupt [emoji852]️.
I will try to download the file again, mayby the download failed.
Edit: The file is corrupt. I cant unzip it
Skickat från min HTC U11 plus via Tapatalk

Davil_79 said:
Hmm.. It is 25 pcs. compressed zip-files in this download.
In one of the zip there is "boot_signed.img"
It must be it. But when I try to unzip it doesn't work. It says the file is corrupt [emoji852]️.
I will try to download the file again, mayby the download failed.
Edit: The file is corrupt. I cant unzip it
Skickat från min HTC U11 plus via Tapatalk
Click to expand...
Click to collapse
You need RUU decrypt tool to retrieve the boot and recovery image

Root HTC U11+ European model software number 1.10.401.23
To root your HTC U11+ thru twrp use version 3.2.0.0
1. make sure you got Magisk-15.2 on you sd-card
2. boot into TWRP and leave system read only
3.goto install and install Magisk (in my case 15.2)
4. you will get error, like "can't mount data" (not to worry)
5. after install GO BACK!! DO NOT REBOOT!!
6. format data AND THEN reboot!!
7 You'll have to setup your phone as a new one; finish that and install Magisk_Manager
8 your now rooted!!! check with root checker
Hope this will help you;
Davil_79 said:
Please help me!
I have unlocked my bootloader, installed twrp. Unfortunately, twrp is worthless since it can not be used as it seems...
Now I wonder if I can use this guide to root my phone:
"1. Download http://fotadl-az.htc.com/secure/OTA_...bbi6tc9m38.zip
Edit / Important: Read next post down below before Step 2/
2. Extract firmware.zip.
3. Extract boot.img from firmware.zip from step 2 and transfer to the /sdcard.
4. Install Magisk Manager and select Beta channel
5. Click install and choose to use "patch the stock boot image" method. It will browse you to /sdcard. Choose the boot.img from step 3. After its done, it will give you path of patched boot image.
6. Transfer the patched boot image from step 5 to PC using 'adb pull'
7. Boot the phone into download mode and flash the patched boot image.
8. Reboot and enjoy!!"
Where/how can I get the correct boot.img för my device?
My version is "1.10.401.23 9.0_g CL991677 release-keys" and none of the download links match my version? Or can I use some of them anyway?
I would be very happy and thanksful if I got help so I can get root access!
Best regards/ David
Click to expand...
Click to collapse

bnwg said:
You need RUU decrypt tool to retrieve the boot and recovery image
Click to expand...
Click to collapse
Aha! Hm ok So it wasnt that easy. I am such a Noob .
I have never used that RUU decrypt tool and it seems a bit complicated but I have to try.
Thanks for your answer!
---------- Post added at 04:22 PM ---------- Previous post was at 04:12 PM ----------
freebsd124 said:
To root your HTC U11+ thru twrp use version 3.2.0.0
1. make sure you got Magisk-15.2 on you sd-card
2. boot into TWRP and leave system read only
3.goto install and install Magisk (in my case 15.2)
4. you will get error, like "can't mount data" (not to worry)
5. after install GO BACK!! DO NOT REBOOT!!
6. format data AND THEN reboot!!
7 You'll have to setup your phone as a new one; finish that and install Magisk_Manager
8 your now rooted!!! check with root checker
Hope this will help you;
Click to expand...
Click to collapse
Thank you! I will try this!
I'm considering starting a new thread. I know there are more people who have similar problems and considerations within this.

HTC-RUU-Decrypt_Tool
You'll find the htc-ruu_decrypt-tool here
Davil_79 said:
Aha! Hm ok So it wasnt that easy. I am such a Noob .
I have never used that RUU decrypt tool and it seems a bit complicated but I have to try.
Thanks for your answer!
---------- Post added at 04:22 PM ---------- Previous post was at 04:12 PM ----------
Thank you! I will try this!
I'm considering starting a new thread. I know there are more people who have similar problems and considerations within this.
Click to expand...
Click to collapse

freebsd124 said:
To root your HTC U11+ thru twrp use version 3.2.0.0
1. make sure you got Magisk-15.2 on you sd-card
2. boot into TWRP and leave system read only
3.goto install and install Magisk (in my case 15.2)
4. you will get error, like "can't mount data" (not to worry)
5. after install GO BACK!! DO NOT REBOOT!!
6. format data AND THEN reboot!!
7 You'll have to setup your phone as a new one; finish that and install Magisk_Manager
8 your now rooted!!! check with root checker
Hope this will help you;
Click to expand...
Click to collapse
YES! Root access :good: Finaly a success! :victory:
Now my phone is like I want it to be!! Thank you so much!!'

If it's useful for somebody wanting to try twrp and/or custom kernel...you can find inside stock boot and recovery for India/HK version, 1.10.400.23 and the new 1.24.400.2
https://drive.google.com/file/d/18FgmqIb_4UNpmRsXyxKj2bbCf6TnTXSd/view?usp=sharing

HELP, How Am I Supposed To Root This Phone? Any Guides?

Self explaining :highfive:

mods please keep it up until a reference is shown to inspire writers with good wills:angel::fingers-crossed:

2B_4G10 said:
Self explaining :highfive:
Click to expand...
Click to collapse
1. Unlock bootloader via MiUnlock software for PC (you have to wait at least 168 hours)
2. Flash TWRP recovery img via fastboot
3. Download and put into internal memory magisk.zip installer (you need version 20.4 or newer)
4. Install this zip via TWRP
5. Boot into the system and download Magisk Manager apk (version 8.0.3 or newer) then install it.
6. Voilà. That's all [emoji106]

zencooler said:
1. Unlock bootloader via MiUnlock software for PC (you have to wait at least 168 hours)
2. Flash TWRP recovery img via fastboot
3. Download and put into internal memory magisk.zip installer (you need version 20.4 or newer)
4. Install this zip via TWRP
5. Boot into the system and download Magisk Manager apk (version 8.0.3 or newer) then install it.
6. Voilà. That's all [emoji106]
Click to expand...
Click to collapse
Thanks! i found the basics but i couldn't find a proper TWRP version out there, and the ROMs too, isn't there a legit source to get em?

2B_4G10 said:
Thanks! i found the basics but i couldn't find a proper TWRP version out there, and the ROMs too, isn't there a legit source to get em?
Click to expand...
Click to collapse
I do not remember where I found the correct sources so I will upload these files for you into wetransfer in few minutes.
EDIT: here you are: https://we.tl/t-xTbsJVTtzA

Putting your post in large bold letters makes you look like a troll, not like you have an urgent issue.

Firmware, http://mifirm.net, twrp at the same place

Question Does anyone know how to root oneplus 9 Android 13.1?

Alguém sabe como fazer root no oneplus 9 Android 13.1?

First of all, please write in English. This is an English-only forum.
You can root the latest 13.1 firmware the same way you root others. I assume you already have the bootloader unlocked, proper drivers installed on your PC, and basic know-how of fastboot/adb commands. Here is the process:
You need to get the boot.img of your current firmware. You can extract it through MSM Tool's Read Back feature. In case you don't know about MSM, I have attached the boot.img for latest OOS13.1 firmware LE2115_13.1.0.500(EX01). Download and extract zip file and you will have boot.img. Copy this boot.img to your phone. Next you need to download/install Magisk v26.1 on your phone. Open the app, click Install and select that boot.img. Magisk will patch that boot.img and create a new patched_boot.img in your phone's Download folder. Copy that patched_boot.img to your PC. Reboot your phone to bootloader mode. Run this command to temporarily boot the patched_boot.img:
fastboot boot <your_patched_boot.img>
Note that this command is to boot it temporarily. It DOES NOT flash it. Ok, so once your phone boots up, open Magisk app again, click Install and select Direct Install. Now Magisk will root your current firmware permanently.
By this method of temporary booting and then rooting with Magisk's Direct Install method, Magisk will backup your original boot.img. So whenever there is a new software update, you can go to Magisk, select Uninstall, choose Restore Images, and Magisk will revert your original stock boot.img from it's backup. Then you can proceed with system update. Otherwise, without restoring original boot.img, the system update will fail because of patched_boot.img.

Here is the zip attachment. Make sure to extract it.

Thank you friend

shadabkiani said:
First of all, please write in English. This is an English-only forum.
You can root the latest 13.1 firmware the same way you root others. I assume you already have the bootloader unlocked, proper drivers installed on your PC, and basic know-how of fastboot/adb commands. Here is the process:
You need to get the boot.img of your current firmware. You can extract it through MSM Tool's Read Back feature. In case you don't know about MSM, I have attached the boot.img for latest OOS13.1 firmware LE2115_13.1.0.500(EX01). Download and extract zip file and you will have boot.img. Copy this boot.img to your phone. Next you need to download/install Magisk v26.1 on your phone. Open the app, click Install and select that boot.img. Magisk will patch that boot.img and create a new patched_boot.img in your phone's Download folder. Copy that patched_boot.img to your PC. Reboot your phone to bootloader mode. Run this command to temporarily boot the patched_boot.img:
fastboot boot <your_patched_boot.img>
Note that this command is to boot it temporarily. It DOES NOT flash it. Ok, so once your phone boots up, open Magisk app again, click Install and select Direct Install. Now Magisk will root your current firmware permanently.
By this method of temporary booting and then rooting with Magisk's Direct Install method, Magisk will backup your original boot.img. So whenever there is a new software update, you can go to Magisk, select Uninstall, choose Restore Images, and Magisk will revert your original stock boot.img from it's backup. Then you can proceed with system update. Otherwise, without restoring original boot.img, the system update will fail because of patched_boot.img.
Click to expand...
Click to collapse
Thank you for the specifics. I haven't decided whether or not I will modify my OnePlus 9 but I will keep this in mind.

Get token.
Flash token.
Enable unlock bl in dev options.
Install Magisk inside Andoid.
Congrats you did it.

Is there a boot img for LE2115_13.1.0.101(CN01)?

oneplus 9 LE2115_13.1. colorOS

ahumzert said:
Is there a boot img for LE2115_13.1.0.101(CN01)?
Click to expand...
Click to collapse
You can use MSM Tool to extract the Boot.img file, this is how most of use get our hands on the image files. I have provided a guide below on how to do this.
MSM Download Tool Read Back Mode: Create OnePlus Backup!
In this guide, we will show you the steps to take a backup of all the partitions on your OnePlus device via MSM Download Tool Read Back Mode.
droidwin.com