Database Info

Unlock/Root/TWRP OTA updates?

I've only had two phones prior to this but I have always unlocked the boot loader / rooted the device / installed a custom recovery / installed custom ROMS.
I believe with my MOTO X 1st gen this disabled the OTA updates.
Is that the case with the Honor 8? I'm wondering if it is worth it to install TWRP at this point as there seems to be so little in the way of kernels and ROMS.
Would I still be able to use SU or Xposed modules without Root?
What is the best move with this phone?

I have unlocked my bootloader as well as rooted my Honor 8. The only way to get SU and Xposed is by doing both of these procedures(root involves getting TWRP).
As for any Xposed modules, I tried amplify+greenify but instead of getting better battery life, my standby time decreased significantly. I am not sure why, but for some reason my Cell standby was showing to be eating a ton of my battery. Another big problem was that the dialer app would not let me call anyone, it kept crashing whenever I tried to. Both problems were fixed after I managed to get amplify+greenify uninstalled. Currently I am just running YouTube AdAway and MinMinGuard which seem to work fine.
So at this point, is it worth unlocking bootleader, installing TWRP, and rooting your phone? Well if there are certain Xposed modules that you really want then sure, and if there are certain apps you like that require root, then yes go ahead and root your phone. Note that if you try any OTA updates, you will have to remove TWRP as having your phone automatically restart and try to install the update wont work.

Imagine that the Honor 8 receives an update to say, Nougat, what is the pathway to update for someone who has rooted their phone. Will the OTA be able to be flashed if a .zip is provided here? Would we need to flash an entirely new ROM?
This is what I faced with my MOTO X. When Marshmallow came out there was talk... but no one was working on the at phone any longer so was never able to update.

pairustwo said:
Imagine that the Honor 8 receives an update to say, Nougat, what is the pathway to update for someone who has rooted their phone. Will the OTA be able to be flashed if a .zip is provided here? Would we need to flash an entirely new ROM?
This is what I faced with my MOTO X. When Marshmallow came out there was talk... but no one was working on the at phone any longer so was never able to update.
Click to expand...
Click to collapse
It doesnt matter whether or not your phone is rooted. You will get updates the same way, through OTA. Of course you can find .zip files to flash(although personally I am struggling to get the latest update flashed through TWRP).
The real question is for how long will we be receiving updates? Nougat is pretty much guaranteed with the new EMUI update. Huawei/Honor has promised up to 2 years of updates from what I have heard, but who knows what that actually means. They have also have a "partnership" with XDA, and the phone is decently popular so I am sure there will be a few roms, just not as many as say a OP3.

Why are people trying to flash via TWRP if the OTA updates still work after rooting and unlocking the boot loader?

pairustwo said:
Why are people trying to flash via TWRP if the OTA updates still work after rooting and unlocking the boot loader?
Click to expand...
Click to collapse
Okay so I just figured it out, but for the OTA update to work after rooting and having a non-stock recovery, you need to go to Settings->Updater->Menu(located on the bottom)->Download latest full package.
The full package is ~1.6GB and the regular update is ~280mb. The full package will work even if you have TWRP installed. But if you want the regular 280mb update, you need to get rid of TWRP and go back to a stock recovery.
Of course you will need to reinstall TWRP and root your phone again after doing this update.

Rakeen70210 said:
Okay so I just figured it out, but for the OTA update to work after rooting and having a non-stock recovery, you need to go to Settings->Updater->Menu(located on the bottom)->Download latest full package.
The full package is ~1.6GB and the regular update is ~280mb. The full package will work even if you have TWRP installed. But if you want the regular 280mb update, you need to get rid of TWRP and go back to a stock recovery.
Of course you will need to reinstall TWRP and root your phone again after doing this update.
Click to expand...
Click to collapse
I see the full package but I cant click on this, nothing is happened when I click on this.

Nas42O said:
I see the full package but I cant click on this, nothing is happened when I click on this.
Click to expand...
Click to collapse
I am not sure what you mean. Do you mean you can see the text "Download latest full package" but it is greyed out? If so please check to see if you arent currently at the latest version. If there is another problem, you might want to try to find a .zip of the full package and flash it that way.

Rakeen70210 said:
I am not sure what you mean. Do you mean you can see the text "Download latest full package" but it is greyed out? If so please check to see if you arent currently at the latest version. If there is another problem, you might want to try to find a .zip of the full package and flash it that way.
Click to expand...
Click to collapse
Yes , not greyed , but red color , and cant click on this .
I downloaded a full update of B31 about 1.77giga , just copy to the phone and flash it in twrp ?

Nas42O said:
Yes , not greyed , but red color , and cant click on this .
I downloaded a full update of B31 about 1.77giga , just copy to the phone and flash it in twrp ?
Click to expand...
Click to collapse
The exact latest update that I currently have is FRD-L04C567B150. I am not sure where you got your update but I suggest you just flash back to a complete stock image and try to update again from there.

Rakeen70210 said:
The exact latest update that I currently have is FRD-L04C567B150. I am not sure where you got your update but I suggest you just flash back to a complete stock image and try to update again from there.
Click to expand...
Click to collapse
its normal , you live in India no ?
i'm live in European country , so update are different .. Last update for us is FRD-L04C432B130

Nas42O said:
its normal , you live in India no ?
i'm live in European country , so update are different .. Last update for us is FRD-L04C432B130
Click to expand...
Click to collapse
No I am in the US. I am not sure about the EU version, but yes if you can find a .zip update file just put it on your phone and go into TWRP to install it. Might wanna make a backup too and wipe cache too just in case.

So if i download the full package in update and install it, bootloader will still be open? No full wipe? And later i only need to install twrp and root the phone again?

Palindrom87 said:
So if i download the full package in update and install it, bootloader will still be open? No full wipe? And later i only need to install twrp and root the phone again?
Click to expand...
Click to collapse
Updating or wiping your phone does not lock the Bootloader. The only way to lock the Bootloader again is by doing it manually yourself.
Yes after doing a full update you will need to reinstall TWRP as it will be replaced with the stock recovery and then re-root your phone again.

Rakeen70210, you sound really confident about doing full updates after rooting. Will these full updates also replace the kernel?
palendrome87 and NAS420 could you guys report back with any success or errors you have flashing full updates?
Where can one download full updates for Honor 8?

pairustwo said:
Rakeen70210, you sound really confident about doing full updates after rooting. Will these full updates also replace the kernel?
palendrome87 and NAS420 could you guys report back with any success or errors you have flashing full updates?
Where can one download full updates for Honor 8?
Click to expand...
Click to collapse
Seeing as how the full update package was ~1.65GB in size, I think its ok to assume that it replaces everything with the stock Honor 8 image. So yes it will replace the kernel too.
For downloading full updates, the only way I got mine was an OTA directly from the phone itself. Look at my previous comments to see how I got this update. If for some reason you cant update, check if your model is ready for an update. If it is and you cant update, try to flash back to a stock image. You should be able to find one on this site or anywhere else.

Flash stock recovery will lock boot loader ?

Nas42O said:
Flash stock recovery will lock boot loader ?
Click to expand...
Click to collapse
No, the only way to lock the bootloader is to manually lock it yourself using a similar operation to unlocking it.

Rakeen70210 said:
No, the only way to lock the bootloader is to manually lock it yourself using a similar operation to unlocking it.
Click to expand...
Click to collapse
I thought the same thing, but after taking the full OTA update my bootloader was locked again. If you want to update I would suggest first making a full backup to the external SD card in TWRP.

Then , its better to download à full update ( update.zip) ,copy to root of the phone , reboot in twrp and flash it ? Anyone already did it ?

[Q]How to change root from phh.superuser to Magisk and upgrade firmware?

Hi Guys, I've been an active user of XDA in the past but didn't have time to follow in the last couple of years so my memory about flashing and tinkering is quite blank.
Here is my situation:
Mate 9 MHA-L29C636B158 (very old ROM)
Bootloader unlocked with paid code from dc-unlocker
Rooted with PHH's Superuser (the only root that was available for our device back in March 2017)
EMUI 5.0 and Android 7.0 (that was obvious from my Build number but I just wanted to state it again)
TWRP 3.0.2-2 is installed with system kept read-only. Internal SD seems to be encrypted
I never took any OTAs as I was afraid that they would break something
In the last month's many of my banking or financial apps have stopped working because I'm rooted so I read that Magisk would be able to circumvent this safetynet thing and would allow me to continue using these apps. Google Pay would be a nice addition also.
At this point I would like to upgrade my firmware and get rid of PHH's Superuser switching to Magisk instead
Could someone please write a detailed guide how to do that? It might be interesting for other users also that are in my same situation. I'm willing to donate a few bucks for a complete and foolproof guide.
Thanks a lot

itenos said:
Hi Guys, I've been an active user of XDA in the past but didn't have time to follow in the last couple of years so my memory about flashing and tinkering is quite blank.
Here is my situation:
Mate 9 MHA-L29C636B158 (very old ROM)
Bootloader unlocked with paid code from dc-unlocker
Rooted with PHH's Superuser (the only root that was available for our device back in March 2017)
EMUI 5.0 and Android 7.0 (that was obvious from my Build number but I just wanted to state it again)
TWRP 3.0.2-2 is installed with system kept read-only. Internal SD seems to be encrypted
I never took any OTAs as I was afraid that they would break something
In the last month's many of my banking or financial apps have stopped working because I'm rooted so I read that Magisk would be able to circumvent this safetynet thing and would allow me to continue using these apps. Google Pay would be a nice addition also.
At this point I would like to upgrade my firmware and get rid of PHH's Superuser switching to Magisk instead
Could someone please write a detailed guide how to do that? It might be interesting for other users also that are in my same situation. I'm willing to donate a few bucks for a complete and foolproof guide.
Thanks a lot
Click to expand...
Click to collapse
Do you still have the unlock code? You'll want it, as the update from EMUI 5 to EMUI 8, on every device I've got, has relocked the bootloader.
With that said:
If you want to keep your data, make a backup using Hisuite.
Download the FullOTA firmware for your current version. Extract system, boot, recovery, recovery2 (as you're on EMUI 5) and flash them either in TWRP or fastboot; that should eliminate PHH SU and TWRP, and ultimately leave the system in a clean state.
If you modified other partitions on the device using TWRP or su in general, it wouldn't be a bad idea to use a nocheck recovery or HuRupdater to flash the entire system, to leave everything in a pristine state, since there are partitions you can't flash with fastboot, even with an unlocked bootloader. The instructions for HuR can be found elsewhere on XDA, as can details about nocheck recoveries, though the latter I'd be careful with - using HWOTA7 on Oreo, for example, WILL cause a brick. You've been warned.
Start the update process - you've already been approved for OTAs and they've been offered, so they should happen automatically. When Oreo is installed, it'll automatically relock your bootloader; you can continue updating here, though if you've got a particular target you want to go to, you might want to unlock and use HuR again to flash that specific one now that you're on Oreo. (The latest firmwares can't be rolled back to Nougat.) If you have no intention of going back to Nougat, you have your unlock code, and you aren't planning to do any other modifications like rebranding, then update away, though you may want to hold off of the Pie update if offered. (Shouldn't be, yet, but it could have been approved for your device already; it changes the boot partitions yet again.)
Now that you're on Oreo and presumably unlocked again, make sure you've got the FullOTA image downloaded for that firmware to your PC. (Always a good idea, anyway.)
Magisk can be installed by:
1) Flashing TWRP with fastboot, then flashing a suitable Magisk zip
2) Using Magisk Manager to patch a boot image and flashing that.
For TWRP:
Get a copy of TWRP from the forum here. When I use one, it's the 3.2.1-0 from @Pretoriano80, you'll find it in the development section. Any 3.2.x for Oreo should work though - a Nougat TWRP will not work.
Flash TWRP to recovery_ramdisk in fastboot. Boot to TWRP, flash Magisk.
For Magisk Manager:
Extract "ramdisk" from your FullOTA firmware. Place it in internal storage on your device. Use Magisk Manager to patch the image (install / patch boot image). Transfer the patched_boot.img created by Magisk back to your PC and flash that to the "ramdisk" partition in fastboot.

Just stumbled over your reply, didn't get an email notification from XDA. Thank you so much. Let's see if I can follow your instructions.
irony_delerium said:
Do you still have the unlock code? You'll want it, as the update from EMUI 5 to EMUI 8, on every device I've got, has relocked the bootloader.
Click to expand...
Click to collapse
Yes, I still have the code
irony_delerium said:
With that said:
If you want to keep your data, make a backup using Hisuite.
Click to expand...
Click to collapse
Done
irony_delerium said:
Download the FullOTA firmware for your current version. Extract system, boot, recovery, recovery2 (as you're on EMUI 5) and flash them either in TWRP or fastboot; that should eliminate PHH SU and TWRP, and ultimately leave the system in a clean state.
Click to expand...
Click to collapse
I downloaded the FullOTA with the FirmwareFinder app on my phone and transferred it to my laptop. Extracted the update.app with WinRAR and extracted system, boot, recovery and recovery2 using the Huawei Update Extractor 0.9.9.3.
Just to make no mistake, could you please confirm the order of flashing these 4 files? And maybe the correct command to use in fastboot?
irony_delerium said:
If you modified other partitions on the device using TWRP or su in general, it wouldn't be a bad idea to use a nocheck recovery or HuRupdater to flash the entire system, to leave everything in a pristine state, since there are partitions you can't flash with fastboot, even with an unlocked bootloader. The instructions for HuR can be found elsewhere on XDA, as can details about nocheck recoveries, though the latter I'd be careful with - using HWOTA7 on Oreo, for example, WILL cause a brick. You've been warned.
Click to expand...
Click to collapse
I don't think that I modified any other partitions, at least not willingly. I even left the system in read-only state. Don't know if phh.su did something by itself?
irony_delerium said:
Start the update process - you've already been approved for OTAs and they've been offered, so they should happen automatically. When Oreo is installed, it'll automatically relock your bootloader; you can continue updating here, though if you've got a particular target you want to go to, you might want to unlock and use HuR again to flash that specific one now that you're on Oreo. (The latest firmwares can't be rolled back to Nougat.) If you have no intention of going back to Nougat, you have your unlock code, and you aren't planning to do any other modifications like rebranding, then update away, though you may want to hold off of the Pie update if offered. (Shouldn't be, yet, but it could have been approved for your device already; it changes the boot partitions yet again.)
Now that you're on Oreo and presumably unlocked again, make sure you've got the FullOTA image downloaded for that firmware to your PC. (Always a good idea, anyway.)
Magisk can be installed by:
1) Flashing TWRP with fastboot, then flashing a suitable Magisk zip
2) Using Magisk Manager to patch a boot image and flashing that.
For TWRP:
Get a copy of TWRP from the forum here. When I use one, it's the 3.2.1-0 from @Pretoriano80, you'll find it in the development section. Any 3.2.x for Oreo should work though - a Nougat TWRP will not work.
Flash TWRP to recovery_ramdisk in fastboot. Boot to TWRP, flash Magisk.
For Magisk Manager:
Extract "ramdisk" from your FullOTA firmware. Place it in internal storage on your device. Use Magisk Manager to patch the image (install / patch boot image). Transfer the patched_boot.img created by Magisk back to your PC and flash that to the "ramdisk" partition in fastboot.
Click to expand...
Click to collapse
Will continue to do the above after your kind confirmation of my last questions. Thanks again

itenos said:
I downloaded the FullOTA with the FirmwareFinder app on my phone and transferred it to my laptop. Extracted the update.app with WinRAR and extracted system, boot, recovery and recovery2 using the Huawei Update Extractor 0.9.9.3.
Just to make no mistake, could you please confirm the order of flashing these 4 files? And maybe the correct command to use in fastboot?
Click to expand...
Click to collapse
The order shouldn't be particularly relevant, just that it's safest to reflash all of them:
- boot because phhsu may have modified the boot image to add su to it
- recovery and recovery2 because you loaded TWRP. recovery2 is specified because it's used to be recommended to flash to erecovery as well as normal recovery.
- system because I'm pretty sure that's the biggest thing modified Hy phhsu, and any other system changes you may have made.
Theoretically, other modified partitions won't matter since the upgrade to 8.0 replaces most (all, I think) of them anyway, but if you have to go through update steps through EMUI 5 first before it'll give you 8, then it's safest that they aren't modified. I mentioned other partitions because, with root & TWRP, you technically could have modified any and all of them.

irony_delerium said:
Download the FullOTA firmware for your current version. Extract system, boot, recovery, recovery2 (as you're on EMUI 5) and flash them either in TWRP or fastboot; that should eliminate PHH SU and TWRP, and ultimately leave the system in a clean state.
Start the update process - you've already been approved for OTAs and they've been offered, so they should happen automatically.
Click to expand...
Click to collapse
Flashing of 158 (original ROM version) went fine. Phone rebooted and titanium reported no root access, so it looks good.
After that I started the OTA update to 172 that waited already long time in my settings and it downloaded it. After downloading it gave me an error during the validation process of the file and asked to download it again.
Unfortunately now both the phone updater and the HiSuite app on my laptop say that 158 is the latest available firmware and no update is available.
I guess that I can download directly the newer firmware but I'm not exactly sure how to flash the whole package and what I should do with the other 2 files that come with it besides the update.zip

itenos said:
Flashing of 158 (original ROM version) went fine. Phone rebooted and titanium reported no root access, so it looks good.
After that I started the OTA update to 172 that waited already long time in my settings and it downloaded it. After downloading it gave me an error during the validation process of the file and asked to download it again.
Unfortunately now both the phone updater and the HiSuite app on my laptop say that 158 is the latest available firmware and no update is available.
I guess that I can download directly the newer firmware but I'm not exactly sure how to flash the whole package and what I should do with the other 2 files that come with it besides the update.zip
Click to expand...
Click to collapse
It might be tweaking out about the fact that you'd previously modified system.
I'd grab the last Nougat release (looks like 191; there are 2 of them, be sure it's not the rollback one you grab) and use hurupdater in TWRP to install it, then let the system try running OTA again.

irony_delerium said:
It might be tweaking out about the fact that you'd previously modified system.
I'd grab the last Nougat release (looks like 191; there are 2 of them, be sure it's not the rollback one you grab) and use hurupdater in TWRP to install it, then let the system try running OTA again.
Click to expand...
Click to collapse
I had to insert the SIM card of the country I bought my phone in to get the OTAs coming. Luckily I still had it with a few $ credit on it. It used just a few cents in data roaming for finding the new firmware, then I downloaded through wifi.
After 4 updates now I'm on 378 and no sign of Pie yet so this afternoon if I find some time I'll continue with rooting.

itenos said:
I had to insert the SIM card of the country I bought my phone in to get the OTAs coming. Luckily I still had it with a few $ credit on it. It used just a few cents in data roaming for finding the new firmware, then I downloaded through wifi.
After 4 updates now I'm on 378 and no sign of Pie yet so this afternoon if I find some time I'll continue with rooting.
Click to expand...
Click to collapse
Easy way:
Unlock phone, if you haven't yet again.
Download and flash TWRP from here: https://forum.xda-developers.com/mate-9/development/recovery-twrp-3-2-1-0-t3783353 (has decryption support) (flash to recovery_ramdisk as Huawei decided to split recovery partition into different parts)
Boot to TWRP, input pin (if you set a pin, else it will decrypt automatically)
Download Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Transfer Magisk to phone.
Flash Magisk zip in TWRP.
Reboot and you're done.
You might have to tinker around with Magisk Hide and hide apps if your banking apps still detect root.

As the Huawei Backup took over 4 hours to finish and i can't use Titanium, which is much faster, because I'm not rooted at the moment, I thought it's a good idea to first upgrade to Pie before unlocking my bootloader and losing all data. If I need to stay a few days without root it's ok.
Is there any way to get to Pie without being rooted? I tried the erecovery method on firmware finder. It says that my IMEI is now registered to download the update but when I enter erecovery it starts downloading the 378 oreo package.
I would like to avoid backing up and restoring twice this lengthy process, probably 16 hours all in all

itenos said:
As the Huawei Backup took over 4 hours to finish and i can't use Titanium, which is much faster, because I'm not rooted at the moment, I thought it's a good idea to first upgrade to Pie before unlocking my bootloader and losing all data. If I need to stay a few days without root it's ok.
Is there any way to get to Pie without being rooted? I tried the erecovery method on firmware finder. It says that my IMEI is now registered to download the update but when I enter erecovery it starts downloading the 378 oreo package.
I would like to avoid backing up and restoring twice this lengthy process, probably 16 hours all in all
Click to expand...
Click to collapse
The erecovery method won't work unless you can change the DNS settings on the network being used - it hijacks some of the requests to Huawei's servers to force the update. (And even then it's a bit finicky; I have yet to successfully use it, all things considered.)

Yesterday I finally received 9.0.1.159 with EMUI 9.0.1 by OTA. It installed fine and it's amazing how fast my phone became and how much screen on time I have now with my 2 year old device (8 full hours!). Good job Google and Huawei.
Being on Pie now I suppose that the instructions to root from you and ante0 are not valid anymore as they were meant for Oreo.
Could you please modify the instructions for Pie? And further, as I see that since yesterday in FirmwareFinder a new Pie update 9.0.1.178 popped up, could you please also add instructions how to take this OTA being rooted with Magisk once it arrives?
I've read a bit in the Magisk thread but I did not really understand the part of having to boot to recovery everytime I switch on the phone. Further they are talking there about EMUI 9 but I have already 9.0.1, is there maybe a difference I have to take care about?
Last but not least, I didn't forget my initial promise to donate a few bucks for the detailed instructions so please drop me your email in PM and I'll sent you a few through PayPal or in alternative, if you have some paid apps on the Playstore I could buy them so they might get more visibility.

itenos said:
Yesterday I finally received 9.0.1.159 with EMUI 9.0.1 by OTA. It installed fine and it's amazing how fast my phone became and how much screen on time I have now with my 2 year old device (8 full hours!). Good job Google and Huawei.
Being on Pie now I suppose that the instructions to root from you and ante0 are not valid anymore as they were meant for Oreo.
Could you please modify the instructions for Pie? And further, as I see that since yesterday in FirmwareFinder a new Pie update 9.0.1.178 popped up, could you please also add instructions how to take this OTA being rooted with Magisk once it arrives?
I've read a bit in the Magisk thread but I did not really understand the part of having to boot to recovery everytime I switch on the phone. Further they are talking there about EMUI 9 but I have already 9.0.1, is there maybe a difference I have to take care about?
Last but not least, I didn't forget my initial promise to donate a few bucks for the detailed instructions so please drop me your email in PM and I'll sent you a few through PayPal or in alternative, if you have some paid apps on the Playstore I could buy them so they might get more visibility.
Click to expand...
Click to collapse
The reason recovery boot is needed for Pie is because Huawei removed the ramdisk - in Pie, it's system as root with no way of forcing a ramdisk except by a recovery boot. So as a workaround, Magisk takes over recovery.
The installation instructions for it on Pie are pretty much the same as Oreo, except:
* Patch recovery_ramdisk, not ramdisk. Latest stable Magisk should work (18.1, iirc, has the patches to support recovery boot.)
* When booting, go to recovery. Magisk will start from there and take over the startup process.

irony_delerium said:
The installation instructions for it on Pie are pretty much the same as Oreo, except:
Click to expand...
Click to collapse
Hmm, where do I find the TWRP for Pie in order to flash?
And most importantly how do I have to behave in case of new OTAs coming?

itenos said:
Hmm, where do I find the TWRP for Pie in order to flash?
And most importantly how do I have to behave in case of new OTAs coming?
Click to expand...
Click to collapse
TWRP on this case, don't bother.
Extract your stock recovery from your firmware's update.app file, patch with Magisk Manager, and flash the patched image. When you want to flash an ota, put the stock recovery back.

[GM-1910 OP7PRO] Reset everything back to Oxygen OS ( Help:( )

Hey I was experiencing some display issues so I flashed a custom ROM to test / narrow the problem (hardware issue sadly).
—Now I'm not sure how to revert back to completely stock as I've never unlocked the bootloader and worked much with fastboot.
On Samsung's you just download the official stock file, get Odin and put the file into AP, flash, done.
On one plus this is a bit different, first of all there's barely any mentioning of GM-1910 in the MSMDownloaderTool thread(s), I also don't want to have Hydrogen OS.
—My OP7Pro came with Oxygen OS pre-installed, GM1910 "international version" ← def. Chinese with oxygen flashed over it.
*What have you altered so far?*
Unlocked Bootloader/OEM
Flashed TWRP with fastboot
Flashed Havoc 3.0 OS, Magisk, OpenGapps
My perspective on the nature of special relativity.
*What do I want to reset?*
EVERYTHING, ROM, recovery, bootloader, you name it, I don't care about apps and pictures. worth noting I have a One plus Switch Backup, does that help?

Look for the MSM tool... that can reset the phone completely back to stock.

UpdateYourBrowser said:
Hey I was experiencing some display issues so I flashed a custom ROM to test / narrow the problem (hardware issue sadly).
—Now I'm not sure how to revert back to completely stock as I've never unlocked the bootloader and worked much with fastboot.
On Samsung's you just download the official stock file, get Odin and put the file into AP, flash, done.
On one plus this is a bit different, first of all there's barely any mentioning of GM-1910 in the MSMDownloaderTool thread(s), I also don't want to have Hydrogen OS.
—My OP7Pro came with Oxygen OS pre-installed, GM1910 "international version" ← def. Chinese with oxygen flashed over it.
*What have you altered so far?*
Unlocked Bootloader/OEM
Flashed TWRP with fastboot
Flashed Havoc 3.0 OS, Magisk, OpenGapps
My perspective on the nature of special relativity.
*What do I want to reset?*
EVERYTHING, ROM, recovery, bootloader, you name it, I don't care about apps and pictures. worth noting I have a One plus Switch Backup, does that help?
Click to expand...
Click to collapse
You can use the fastboot ROM or Guac (MSM tool for oxygen OS). Links below:
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
or
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Good luck!!

Gr8man001 said:
You can use the fastboot ROM or Guac (MSM tool for oxygen OS). Links below:
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
or
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Good luck!!
Click to expand...
Click to collapse
excuse my stupidity but given that I want to get rid of my custom ROM and back to stock oxygen which tool do I have to use?
secondly all images (androidfilehost) for the second link are for GM1911,17,13,15 but mine is 1910 which is not listed, what do I do now?

UpdateYourBrowser said:
excuse my stupidity but given that I want to get rid of my custom ROM and back to stock oxygen which tool do I have to use?
secondly all images (androidfilehost) for the second link are for GM1911,17,13,15 but mine is 1910 which is not listed, what do I do now?
Click to expand...
Click to collapse
I am sorry but I am not familiar with Chinese stock ROMs. For some reason, I got the impression that you wanted to restore it to an international version and not the Chinese/HK version. You may want to post a question in the OnePlus community forum or check out their download section for your specific model.
https://forums.oneplus.com/forums/oneplus-7pro-support/

Gr8man001 said:
I am sorry but I am not familiar with Chinese stock ROMs. For some reason, I got the impression that you wanted to restore it to an international version and not the Chinese/HK version. You may want to post a question in the OnePlus community forum or check out their download section for your specific model.
https://forums.oneplus.com/forums/oneplus-7pro-support/
Click to expand...
Click to collapse
no no I want to restore it to international version, the phone itself is GM1910. should I flash GM21AA file or the global file?
I think I will go with the global file, makes most sense in this moment

UpdateYourBrowser said:
no no I want to restore it to international version, the phone itself is GM1910. should I flash GM21AA file or the global file?
I think I will go with the global file, makes most sense in this moment
Click to expand...
Click to collapse
GM21AA should be fine. If you decided to use the MSM tool (the one in the first link), hardest part is to get the L2/qualcomm drivers installed on your PC with the method described. Alternatively you can download and install the drivers yourself which will make the job easier. This will LOCK your bootloader and wipe off everything on your phone. You will get a brand new phone running 10.0.3 OS
Easiet way would be to go fastboot ROM route. It will also wipe your phone but won't lock the bootloader. Once installation is complete you could use the adb command to lock the bootloader. It's one extra step but may be much easier IMO. Download the zip file on PC>unzip it>Hit flash all bat file while the phone is connected in the fastboot mode. You may get some error messages regarding header parsing, ignore them and sit tight until your phone boots.
Good luck!!

WORKS NOW! Can confirm this reverts all back to stock (it will revert back to Oxygen OS (OOS) 9.5 so you'll have to update to Android 10 via OTA if you want)
For anyone wondering, I had Android 10 installed before / Havoc 3.0 and the MSMTool will revert you back to Oxygen OS 9.5. Widevine jumped back to L1 so everything should be stock.
If you have any questions, don't wait, I am sure someone out there had the same questions/issue as me and I hope this will help you.
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691

UpdateYourBrowser said:
WORKS NOW! Can confirm this reverts all back to stock (it will revert back to Oxygen OS (OOS) 9.5 so you'll have to update to Android 10 via OTA if you want)
For anyone wondering, I had Android 10 installed before / Havoc 3.0 and the MSMTool will revert you back to Oxygen OS 9.5. Widevine jumped back to L1 so everything should be stock.
If you have any questions, don't wait, I am sure someone out there had the same questions/issue as me and I hope this will help you.
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Click to expand...
Click to collapse
Hey, I have a problem, I re-locked the bootloader, it is currently blocked, but my Widevine status is still L3, can you tell me if you used MsmTool first and then you did relock, or did you block the bootloader first?

Oneplus7pro back to stock

Hello there,
I tried the open beta on the OnePlus 7pro for a while, but I have some massive issues with speaker distortion, so I decided to go back to stock. I know this involves a wipe of the entire system, and I have fully prepared that.
However: I seem to be to stupid to perform this. I used to flash all kinds of roms to my OP3 back in the day, but I can't find an option for simply flashing the zip in the recovery.
My big big question is: How do I perform the full reflash of this phone?
Do I get an factory rom like with the pixel, or do I need to sideload something and flash it in recovery?
I am really clueless rightnow, expecially since the factory image told me, that the bootloader is locked, but to my unterstandig, flashing an original manufacturer image should not require the bootloader to be unlocked...
So I am really hoping on your help, as rightnow, I have a beta phone that is waiting to be setup...
:crying:

Follow this tutorial.
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691

Or easier way would be to download rollback package from oneplus which will wipe everything on your phone. You will have os9.5.3
You can then do Ota upgrade to latest os version. Rollback package is listed in in the middle of the post
https://forums.oneplus.com/threads/...-for-the-oneplus-7-and-oneplus-7-pro.1099154/

So my OnePlus 7 Pro is rooted, has twrp, xxx ROM and renovate ice. If I want to go back stock and relock bootloader, can I simply flash the latest ROM (in this way I should loose twrp and root) and then relock bootloader with ADB command?

Jack_Sparrow_ said:
So my OnePlus 7 Pro is rooted, has twrp, xxx ROM and renovate ice. If I want to go back stock and relock bootloader, can I simply flash the latest ROM (in this way I should loose twrp and root) and then relock bootloader with ADB command?
Click to expand...
Click to collapse
I'd just use the MSMtool detailed here: https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595

jdgesmlls said:
I'd just use the MSMtool detailed here: https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595
Click to expand...
Click to collapse
That's what I did eventually, faster and easier

jdgesmlls said:
I'd just use the MSMtool detailed here: https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595
Click to expand...
Click to collapse
Bro.. I'm on 10.3.4 i just want to go complete stock. The msm tool version seems older? Or can I use the older one or use that roll back rom to go to 9.5.3 and ota update to latest version?

RANJITH THRISSUR said:
Bro.. I'm on 10.3.4 i just want to go complete stock. The msm tool version seems older? Or can I use the older one or use that roll back rom to go to 9.5.3 and ota update to latest version?
Click to expand...
Click to collapse
There is a newer one available search for unbrick tools in forums and also you can use this old one too you have to do local upgrade after that

muhammadshais said:
There is a newer one available search for unbrick tools in forums and also you can use this old one too you have to do local upgrade after that
Click to expand...
Click to collapse
Thanks bro!!
Local upgrade is a cake walk! All my worry was, if I go for a random version msm tool, which is not specific to 10.3.4(more like the case of fast boot Roms), i may stuck at bootloop/something undesirable.
From your reply, i understand, i can use any msm tool zip that supports one plus 7 pro, and get back to stock with an older oos version in it. From there i can choose OTA upgrade or local upgrade.. Whichever way? Right ?

RANJITH THRISSUR said:
Thanks bro!!
Local upgrade is a cake walk! All my worry was, if I go for a random version msm tool, which is not specific to 10.3.4(more like the case of fast boot Roms), i may stuck at bootloop/something undesirable.
From your reply, i understand, i can use any msm tool zip that supports one plus 7 pro, and get back to stock with an older oos version in it. From there i can choose OTA upgrade or local upgrade.. Whichever way? Right ?
Click to expand...
Click to collapse
Yes I used 9.3.4 and then did local update but if you are on 9.3.4 you have to flash first 10.0.3 and then after that 10.3.4 to upgrade.

Question Downgrade LE2115 from 12 to 11 - confused.

Hello all,
My phone came with ColorOS OOS 12 and I hate it. As soon as I rooted it it started crashing daily, I even reflashed a fresh oos12 image using the local update tool and only granted superuser to one app (solid explorer so I could access user files) and it still crashes. Not to mention all the apps i want to use don't work on android 12 (call recorder, busy box) and no custom recovery.
I've been reading through the forum and I found a downgrade package that looks like its hosted by oneplus: https://oxygenos.oneplus.net/OnePlu...all_2107082125_downgrade_059624cc7298428b.zip
I just wanted to make sure I am doing this correctly...
Do I use the OP Local Update app to flash?
Will I be able to flash TWRP for android 11 afterwards?
Will i need to relock the bootloader?
Should i re-root using the magisk slot b method or wait until its flashed and use TWRP?
Will it try to OTA back to android 12? If so, what's the best method to get on the latest version of android 11?
Thanks for the help.

I am running COS C.62 on my OP9 with root and having no issues. Did you make sure to do all the things in this guide?
Root OnePlus ColorOS 12 OxygenOS Android 12 via Magisk
In this tutorial, we will show you detailed steps to root your OnePlus device running ColorOS 12 Android 12 via Magisk Patched Boot.img file.
www.droidwin.com
Anyway, yes, use the local upgrade APK, put the downgrade file in the root of storage, run it. Reboot. Factory reset and wipe data to clear out any leftover crap (don't restore a backup - if you want to use Clone Phone you can do that but only restore app APKs and messages). When it reboots it should offer the latest OOS11 OTA first. If not, just download it and place it in the root and use the local upgrade function in the settings menu of the OOS11 system updater.
There is no need re-lock the bootloader and if you do, you risk a brick that has to be recovered with MSM Tool.
Root by following the guide I linked. I just went through this yesterday after flashing COS broke mobile data. I have Magisk 24.3 working with denylist, Widevine L1, and SafetyNet passes so I have Google Pay.

EtherealRemnant said:
I am running COS C.62 on my OP9 with root and having no issues. Did you make sure to do all the things in this guide?
Root OnePlus ColorOS 12 OxygenOS Android 12 via Magisk
In this tutorial, we will show you detailed steps to root your OnePlus device running ColorOS 12 Android 12 via Magisk Patched Boot.img file.
www.droidwin.com
Anyway, yes, use the local upgrade APK, put the downgrade file in the root of storage, run it. Reboot. Factory reset and wipe data to clear out any leftover crap (don't restore a backup - if you want to use Clone Phone you can do that but only restore app APKs and messages). When it reboots it should offer the latest OOS11 OTA first. If not, just download it and place it in the root and use the local upgrade function in the settings menu of the OOS11 system updater.
There is no need re-lock the bootloader and if you do, you risk a brick that has to be recovered with MSM Tool.
Root by following the guide I linked. I just went through this yesterday after flashing COS broke mobile data. I have Magisk 24.3 working with denylist, Widevine L1, and SafetyNet passes so I have Google Pay.
Click to expand...
Click to collapse
Thank you, ill give it a try.
First i used the payload.bin method and it was crashing, then i reflashed the latest OTA using the local update tool and used the magisk slot b method. still crashing.
It might have less to do with the root and more with me using root to disable certain apps (youtube, chrome, OP community, google news/podcast/tv) i dont want them on my phone but they might be too tightly integrated. If its still crashing on android 11 ill re-enable them and see if that helps.

aaronbaird1 said:
Thank you, ill give it a try.
First i used the payload.bin method and it was crashing, then i reflashed the latest OTA using the local update tool and used the magisk slot b method. still crashing.
It might have less to do with the root and more with me using root to disable certain apps (youtube, chrome, OP community, google news/podcast/tv) i dont want them on my phone but they might be too tightly integrated. If its still crashing on android 11 ill re-enable them and see if that helps.
Click to expand...
Click to collapse
Okay you're on OOS, not COS. COS doesn't have Google apps by default (but has plenty more bloatware, I just don't use it).
It's certainly possible that disabling Google apps is your problem. If you don't want Google apps, you're better off with a custom ROM that doesn't have them. CalyxOS has a beta for OnePlus 9 and it's totally de-Googled. There's also Lineage.

EtherealRemnant said:
Okay you're on OOS, not COS. COS doesn't have Google apps by default (but has plenty more bloatware, I just don't use it).
It's certainly possible that disabling Google apps is your problem. If you don't want Google apps, you're better off with a custom ROM that doesn't have them. CalyxOS has a beta for OnePlus 9 and it's totally de-Googled. There's also Lineage.
Click to expand...
Click to collapse
ahhhh. i didnt realize there was a difference. I thought OP was just calling their android 12 build ColorOS.
Either way, for custom roms i would have to go back to 11 to flash TWRP right? or can you flash custom roms using fastboot?

aaronbaird1 said:
ahhhh. i didnt realize there was a difference. I thought OP was just calling their android 12 build ColorOS.
Either way, for custom roms i would have to go back to 11 to flash TWRP right? or can you flash custom roms using fastboot?
Click to expand...
Click to collapse
You would need to back to 11 because OnePlus hasn't released working sources for 12. Just use the downgrade package, factory reset, then upgrade to 11.2.10.10 and you'll be good to go for custom ROMs. TWRP isn't used for flashing them, they all generally post their own recovery. StagOS was the best one I used (plus the dev is really responsive when there are issues) and people seem to really be enjoying Nameless but that came out after I went back to stock so I haven't tried it yet.
Before you mess with custom ROMs, make sure that you download the global MSM Tool and make sure you can connect it. Honestly since you have to go back anyway, might as well download and use the MSM Tool to get the device back to 11 anyway.
GLOBAL OnePlus 9 MSM TOOL UPDATED
Frist off Im not responsible for anything that happens to your phone!!! VERY SIMPLE IF YOU ARE BICKED,BOOTLOOPED OR JUST WANT TO GO BACK TO 100% STOCK THIS WILL WIPE ALL DATA!!! AN RELOCK BOOTLOADER OOS 11.2.4.4.LE25AA MUST HAVE QAULCOMM...
forum.xda-developers.com
Easiest way to get it into EDL is adb reboot edl but if you want to practice the key combination in case you can't get into the OS, I found if you open the MSM, check use lite firehose, and click Start before you connect the phone, it has less connection errors because it's waiting for the phone so as soon as you connect the cable, it pops up.

EtherealRemnant said:
TWRP isn't used for flashing them, they all generally post their own recovery.
Click to expand...
Click to collapse
Really??? you can tell I haven't messed with custom roms in a long time.
Thank you for all the help. I'll try it out.

aaronbaird1 said:
Really??? you can tell I haven't messed with custom roms in a long time.
Thank you for all the help. I'll try it out.
Click to expand...
Click to collapse
Yeah TWRP has issues. I soft bricked last time I tried to do anything with it and had to use MSM Tool to get back to working order.