Can we get a Step by Step to update to 27? - ZTE Axon 7 Questions & Answers

So my scenario.
I'm on the unlocked B20_boot Build. Rooted. TWRP.
What files are needed to upgrade to B27?
What are the step by step?
I have read through the different threads, but it is confusing at times and rather not make a mistake. It would probably benefit multiple people.
Cheers!

I'm in the same boat. I downgraded to B20 and cannot get the .up file provided recognized in recovery to flash. Using the system updater just puts me right back on B20_Boot. Just using the twrp backup does not flash the B27 firmware.

bhazard451 said:
I'm in the same boat. I downgraded to B20 and cannot get the .up file provided recognized in recovery to flash. Using the system updater just puts me right back on B20_Boot. Just using the twrp backup does not flash the B27 firmware.
Click to expand...
Click to collapse
Change the .up to .zip and try again. This is the safest method to B27.

jkuczera said:
Change the .up to .zip and try again. This is the safest method to B27.
Click to expand...
Click to collapse
Changing it to .zip does not work.

B4oE said:
Changing it to .zip does not work.
Click to expand...
Click to collapse
From stock recovery?

jkuczera said:
From stock recovery?
Click to expand...
Click to collapse
Correct. I was on stock B20 and downloaded the .up file from the following link: https://dl1.ztems.com/zxmdmp/download.do?doWhat=getUp&filename=firmwarepackages/US/ZTE/ZTE%20A2017U/81526/update_P996A01_B20_to_B27.up. After I downloaded it, I simply changed the .up extension to .zip to try to install through stock recovery. However, it was not even recognized. I even moved it to my SD Card but got the same results.

B4oE said:
Correct. I was on stock B20 and downloaded the .up file from the following link: https://dl1.ztems.com/zxmdmp/downlo...TE A2017U/81526/update_P996A01_B20_to_B27.up. After I downloaded it, I simply changed the .up extension to .zip to try to install through stock recovery. However, it was not even recognized. I even moved it to my SD Card but got the same results.
Click to expand...
Click to collapse
Maybe verify checksum? That's the method I used (from SD card).

Interesting. ADB Sideload should work if the Apply Update from SD Card method doesn't.

B4oE said:
Correct. I was on stock B20 and downloaded the .up file from the following link: https://dl1.ztems.com/zxmdmp/download.do?doWhat=getUp&filename=firmwarepackages/US/ZTE/ZTE%20A2017U/81526/update_P996A01_B20_to_B27.up. After I downloaded it, I simply changed the .up extension to .zip to try to install through stock recovery. However, it was not even recognized. I even moved it to my SD Card but got the same results.
Click to expand...
Click to collapse
Enable OEM unlocking under dev. Option and go back to stock recovery > Apply using SDCard.

DrakenFX said:
Enable OEM unlocking under dev. Option and go back to stock recovery > Apply using SDCard.
Click to expand...
Click to collapse
I did that already too. But it still didn't work. Don't worry about it, though. I appreaciate the help, however, I am just going to wait for CyanogenMod to be released. I only wanted to test out the new update. It's not worth the frustration, though. I honestly prefer CyanogenMod.

B4oE said:
I did that already too. But it still didn't work. Don't worry about it, though. I appreaciate the help, however, I am just going to wait for CyanogenMod to be released. I only wanted to test out the new update. It's not worth the frustration, though. I honestly prefer CyanogenMod.
Click to expand...
Click to collapse
Don't expect it anytime soon within the next 3 months.
The updates to the firmware and software are substantial enough that I need to find a 100% working method that I can confirm that takes me from B20_boot, downgraded to B20, then updated to B27 from stock recovery.

bhazard451 said:
Don't expect it anytime soon within the next 3 months.
The updates to the firmware and software are substantial enough that I need to find a 100% working method that I can confirm that takes me from B20_boot, downgraded to B20, then updated to B27 from stock recovery.
Click to expand...
Click to collapse
I am with you. @DrakenFX Do you have the steps mentioned above? What is the best way to get back to B20 so it can be updated to B27?

swehes said:
I am with you. @DrakenFX Do you have the steps mentioned above? What is the best way to get back to B20 so it can be updated to B27?
Click to expand...
Click to collapse
The best way would be a System Image from ZTE, but we are SOL on that for now.

Related

Can't upgrade to MM. Getting 'Error' during process

I am unlocked and unrooted. I had previously upgraded to MM, but ran into some major problems after setting my SD card as internal, and ended up having to use the stock Lollipop tool. So, now i am running stock Lollipop and have received the OTA update. I try running it and it enters the stock recovery ok, the progress bar starts, then after a couple of minutes, i get the dead Andy icon and a quick 'Error' message. It reboots me back to Lollipop and tells me there is an update available and i can try (and fail) again if i want.
A few notes on things i tried to work around this issue (rather than solve it):
1) I have a nandroid i took while in Lollipop, I had it on my PC and i moved it to my sd card but TWRP can't see my SD Card still (E failure to mount SD card). I tried look for solutions to this, but nothing i found worked.
2) so i tried taking the stock MM ROM and moving it to my internal storage and flash that through TWRP, but I couldn't get it to appear in TWRP for selection. I tried look for solutions to this, but nothing i found worked.
3) I took my SD card out completely out, then tried taking the OTA update. Same result: "Error" then reboot.
So, any ideas on how i can get some info on what is causing the failure? Any thoughts on what i can try to resolve this?
chuck-fu said:
I am unlocked and unrooted. I had previously upgraded to MM, but ran into some major problems after setting my SD card as internal, and ended up having to use the stock Lollipop tool. So, now i am running stock Lollipop and have received the OTA update. I try running it and it enters the stock recovery ok, the progress bar starts, then after a couple of minutes, i get the dead Andy icon and a quick 'Error' message. It reboots me back to Lollipop and tells me there is an update available and i can try (and fail) again if i want.
A few notes on things i tried to work around this issue (rather than solve it):
1) I have a nandroid i took while in Lollipop, I had it on my PC and i moved it to my sd card but TWRP can't see my SD Card still (E failure to mount SD card). I tried look for solutions to this, but nothing i found worked.
2) so i tried taking the stock MM ROM and moving it to my internal storage and flash that through TWRP, but I couldn't get it to appear in TWRP for selection. I tried look for solutions to this, but nothing i found worked.
3) I took my SD card out completely out, then tried taking the OTA update. Same result: "Error" then reboot.
So, any ideas on how i can get some info on what is causing the failure? Any thoughts on what i can try to resolve this?
Click to expand...
Click to collapse
I was in the exact same predicament last night, for different reasons though. No matter what I did, I kept getting that same error. I gave up and just flash one of the Roms from this thread since it includes the kernel, radio and stuff http://forum.xda-developers.com/showthread.php?t=3262242.
Sent from my XT1575 using Tapatalk
I had the same issue when i downgraded to LP. There a file you need to flash if you downgraded from MM to LP. I'll post back as soon as I find it.
Sent from my XT1575 using Tapatalk
I have same issue like you guys. I want to root my Moto, and my Wi-Fi won't working. So I downgraded to LL using Restore-To-Stock-Tool and try to upgrade to MM unfortunatelly it isn't work. From OTA I received error, and from recovery also upgrade didn't work? Any ideas how to solve existing problem?
bulsara said:
I had the same issue when i downgraded to LP. There a file you need to flash if you downgraded from MM to LP. I'll post back as soon as I find it.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
That would be great- looking forward to trying out that file.
After running the restore to stock tool you need to flash a file named hlnos in the tools folder.
Sent from my Moto XPE
JoeNeckbone said:
After running the restore to stock tool you need to flash a file named hlnos in the tools folder.
Sent from my Moto XPE
Click to expand...
Click to collapse
I want to make sure i understand the exact files you're referring to. Are you talking about this restore to stock tool?
http://forum.xda-developers.com/mot...ndows-tool-moto-x-style-pure-edition-t3199905
If so, I don't see a 'tools' folder in this zip file. So, i am obviously looking in the wrong place. Note: I do remember flashing an additional file at some point after my downgrade. I believe I flashed it when i learned that my wifi didn't work after downgrading to LP. So, if my wifi is now working, it MAY be possible that i already flashed the file you are referring to (though i can't remember what the name of that one was)
chuck-fu said:
I want to make sure i understand the exact files you're referring to. Are you talking about this restore to stock tool?
http://forum.xda-developers.com/mot...ndows-tool-moto-x-style-pure-edition-t3199905
If so, I don't see a 'tools' folder in this zip file. So, i am obviously looking in the wrong place. Note: I do remember flashing an additional file at some point after my downgrade. I believe I flashed it when i learned that my wifi didn't work after downgrading to LP. So, if my wifi is now working, it MAY be possible that i already flashed the file you are referring to (though i can't remember what the name of that one was)
Click to expand...
Click to collapse
I'm a little confused, if your trying to go back to lollipop that is the correct modem file, I haven't tried it myself, but I read there should be a tools folder with a hlnos file. If still trying mm then here is the mm modem file.
http://forum.xda-developers.com/showthread.php?p=63574299
Edit: you should verify the md5 for all the files you are using, might have a bad download.
Edit 2: just downloaded the restore zip and took a look, there is no tools folder but filename is
NON-HLOS.bin for lollipop modem.
Sent from my Moto XPE
Sorry for the delay, this is the correct file you need to download NON-HLOS.bin. You can grab it from the link below and only need to flash that file. Hope this helps!
http://thunderztech.com/download-stock-android-6-0-marshmallow-for-moto-x-stylepure-edition-xt1575/
I am in the same issue, but I have the XT1572. Any thoughts?
bulsara said:
Sorry for the delay, this is the correct file you need to download NON-HLOS.bin. You can grab it from the link below and only need to flash that file. Hope this helps!
http://thunderztech.com/download-stock-android-6-0-marshmallow-for-moto-x-stylepure-edition-xt1575/
Click to expand...
Click to collapse
Thanks for trying to help, but that was the file I had originally flashed. I did try again and no luck still.
I just tried again to manually flash the MM ROM and still can't do it. I keep getting the error: "E:Cannot restore System -- mounted read only. " from TWRP. Looking around it seems like i'm sort of stuck. Other phone owners have had to resort to using ruu and restoring directly from their PC. I've done this in the past with my HTC M7, but don't know if things are different (or even applicable) with the MotoXPE, so i need to do some searching around.
If anyone has any thoughts on how to best install a ROM directly from my PC, please share your thoughts. I think this is sideloading, right? I've sideloaded files before, but never ROMs (expect for maybe when i did it with my old M7)
chuck-fu said:
Thanks for trying to help, but that was the file I had originally flashed. I did try again and no luck still.
I just tried again to manually flash the MM ROM and still can't do it. I keep getting the error: "E:Cannot restore System -- mounted read only. " from TWRP. Looking around it seems like i'm sort of stuck. Other phone owners have had to resort to using ruu and restoring directly from their PC. I've done this in the past with my HTC M7, but don't know if things are different (or even applicable) with the MotoXPE, so i need to do some searching around.
If anyone has any thoughts on how to best install a ROM directly from my PC, please share your thoughts. I think this is sideloading, right? I've sideloaded files before, but never ROMs (expect for maybe when i did it with my old M7)
Click to expand...
Click to collapse
Are you rooted and have custom recovery on your device?
Sent from my XT1575 using Tapatalk
bulsara said:
Are you rooted and have custom recovery on your device?
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
I'm not rooted, but i do have TWRP 2.8.7.1-clark on the device.
chuck-fu said:
I'm not rooted, but i do have TWRP 2.8.7.1-clark on the device.
Click to expand...
Click to collapse
You need to make sure you are on factory recovery.
1. downgrade again to moto 5.1 with stock recovery
2. from stock recovery factory reset your device
3. reboot bootloader and then flash the file again.
that should solve your issue.
chuck-fu said:
I'm not rooted, but i do have TWRP 2.8.7.1-clark on the device.
Click to expand...
Click to collapse
In twrp, settings, mount, is system checked or not checked? I checked mine and it is off by default and I don't switch it when flashing.
Sent from my Moto XPE
bulsara said:
You need to make sure you are on factory recovery.
1. downgrade again to moto 5.1 with stock recovery
2. from stock recovery factory reset your device
3. reboot bootloader and then flash the file again.
that should solve your issue.
Click to expand...
Click to collapse
I tried that with the same issue as the op to no avail, ended up going with one of the stock roms. Have another issue but I'll be making a new thread with that.
Sent from my XT1575 using Tapatalk
bulsara said:
You need to make sure you are on factory recovery.
1. downgrade again to moto 5.1 with stock recovery
2. from stock recovery factory reset your device
3. reboot bootloader and then flash the file again.
that should solve your issue.
Click to expand...
Click to collapse
Thanks for the advice. I'll try that here. Just to be sure, for step 1, I assume you mean to use this tool, correct: (http://forum.xda-developers.com/mot...ndows-tool-moto-x-style-pure-edition-t3199905)
Or did you downgrade to moto 5.1 using a different method?
bulsara said:
You need to make sure you are on factory recovery.
1. downgrade again to moto 5.1 with stock recovery
2. from stock recovery factory reset your device
3. reboot bootloader and then flash the file again.
that should solve your issue.
Click to expand...
Click to collapse
Also- when you say: "3. reboot bootloader and then flash the file again." Are you suggesting that i should flash my stock MM Rom at that point? If so, just to be clear, i'll need to flash TWRP recovery again, move the MM ROM over, then flash it from inside TWRP, correct?
Or are you saying something different?
Edit: Well, I went ahead and loaded TWRP back on and tried restoring the stock MM Rom. Once again, i got the E: Failure to Mount error when trying to restore (interestingly, i can backup the existing ROM without issue). So, i went ahead and just booted up in hopes that i'd now be able to accept the OTA rom. I just downloaded it, and with stock recover in place, got the same Error and Dead Andy screen.
One note: When i first loaded TWRP, it asks if i want to leave things Read Only and receive OTAs or allow it to be writable. I think in the past i allowed it to be writable (which would've explain the OTA failures of the past), so this time I left it Read Only figuring that would fix my issue. No luck. It still failed.
Any additional ideas would be most welcome. I'm out of ideas here.
JoeNeckbone said:
In twrp, settings, mount, is system checked or not checked? I checked mine and it is off by default and I don't switch it when flashing.
Sent from my Moto XPE
Click to expand...
Click to collapse
Just checked this and system is not checked. I don't think i've ever changed it either.
Issue resolved-
I never figured out how to get around the Error during OTA install, but i did get on MM. I case this somehow helps anyone, here's what i ended up doing.
1) Used the Restore to 511 stock tool (non-rooted)
2) booted into 511 and set things up
3) reformatted my SD card for use (it had previously been set up to be used as internal storage when i had MM working a couple of weeks ago)
4) flashed TWRP 5.1.1
5) rooted using install of SU zip file (rather than TWRP's "do you want to root this device"
6) Rebooted? (maybe i did this. don't remember)
7) Loaded the stock MM rom onto my SD card
8) Went back into TWRP and made my internal partition writeable (Note: i initially tried to say yes to when TWRP asked me if i wanted to root, but this prevented the device from booting after i restored the MM Rom (in the next step), so i just said no to that. If i decide to root later, i will do so by installing SU from zip.
9) Restored the stock MM rom from the SD card
Now up and running on MM. Will not allow my SD card to be used as internal- which is what started this mess.
Currently don't seem to have wifi working. I had this issue when i downgraded to 5.1.1 and needed to flash the NON-HLOS.bin file. I am trying to find out if i need to do the same here.

OTA storage location?

Does anybody know where the OTA file is being saved in our phone?
I'm downloading the file now but I won't be installing it yet until I put back my stock recovery.
Nevermind. I already found the location. If anyone wants to know, it can be found in data/data/com.zte.zdm/files
Can you confirm the location. I am on 7.1.1 and trying to save the latest OTA (on A2017G). Under /data, I only have a mail directory and nothing else.
piet8stevens said:
Can you confirm the location. I am on 7.1.1 and trying to save the latest OTA (on A2017G). Under /data, I only have a mail directory and nothing else.
Click to expand...
Click to collapse
Is your phone rooted?
otaconremo said:
Is your phone rooted?
Click to expand...
Click to collapse
No, not yet. Am trying to do so via magisk.
piet8stevens said:
No, not yet. Am trying to do so via magisk.
Click to expand...
Click to collapse
I see. I think you can view that location once you're rooted.
piet8stevens said:
No, not yet. Am trying to do so via magisk.
Click to expand...
Click to collapse
Magisk doesn't work on our phone. Use SuperSU.
crashnova said:
Magisk doesn't work on our phone. Use SuperSU.
Click to expand...
Click to collapse
Interesting but I don't get it. The entire Badboyz ROM is based on Magisk. And it runs on my phone. ?
piet8stevens said:
Interesting but I don't get it. The entire Badboyz ROM is based on Magisk. And it runs on my phone. ?
Click to expand...
Click to collapse
They don't use the newest version magisk. Try pulling the zip from their room that contains magisk and flash it. I've tried and had no luck. It would cause the phone to bootloop.
otaconremo said:
Does anybody know where the OTA file is being saved in our phone?
I'm downloading the file now but I won't be installing it yet until I put back my stock recovery.
Click to expand...
Click to collapse
Did you use flashfire or something like that to flash stock recovery? I made a backup in TWRP thought about trying to restore stock recovery with that. I have did it on other phones just not this one.
neo4uo said:
Did you use flashfire or something like that to flash stock recovery? I made a backup in TWRP thought about trying to restore stock recovery with that. I have did it on other phones just not this one.
Click to expand...
Click to collapse
Usually I just use the backup boot and recovery I have when I installed twrp using tenfar's tool. I flash my backup images in twrp. Then, i use adb sideload to upgrade rather than sd method.
otaconremo said:
I see. I think you can view that location once you're rooted.
Click to expand...
Click to collapse
Thank you. But when I am rooted, do I still receive OTAs?
piet8stevens said:
Thank you. But when I am rooted, do I still receive OTAs?
Click to expand...
Click to collapse
yes, you can still receive and download the OTA like I how figured out the location.
However, you can't update using the downloaded OTA file unless you revert your boot and recovery partitions to stock.
otaconremo said:
yes, you can still receive and download the OTA like I how figured out the location.
However, you can't update using the downloaded OTA file unless you revert your boot and recovery partitions to stock.
Click to expand...
Click to collapse
Thank you. I have now a rooted stock phone. I received the OTA, but there is no /data/data. Anything I need to do?
piet8stevens said:
Thank you. I have now a rooted stock phone. I received the OTA, but there is no /data/data. Anything I need to do?
Click to expand...
Click to collapse
Are you using root explorer? I think you need to download the ota update first but don't install.
Also, are trying to update to nougat? Here's the latest b15 rom on the official site.
http://www.zte.com.cn/china/sitecor...?id=B4C0ACE418834F588FED0C72D6046C78#software
otaconremo said:
Are you using root explorer? I think you need to download the ota update first but don't install.
Also, are trying to update to nougat? Here's the latest b15 rom on the official site.
http://www.zte.com.cn/china/sitecor...?id=B4C0ACE418834F588FED0C72D6046C78#software
Click to expand...
Click to collapse
OK, finally got it. Thank you so much.

how to go back from Custom rom to Oreo Beta 3

im not sure what are the procedure to go back to stock rom
i got alot of questions but i couldn't find them like can i sideload oreo beta 3 thru the bootloader (coming from AOSIP 8.1 ROM) and should i re-lock the bootloader after sideloading oreo beta 3?
AsianDuck said:
im not sure what are the procedure to go back to stock rom
i got alot of questions but i couldn't find them like can i sideload oreo beta 3 thru the bootloader (coming from AOSIP 8.1 ROM) and should i re-lock the bootloader after sideloading oreo beta 3?
Click to expand...
Click to collapse
Go over to the rom thread and get the B3 rom and unzip it on your computer and run flash_all.bat/sh
tech_head said:
Go over to the rom thread and get the B3 rom and unzip it on your computer and run flash_all.bat/sh
Click to expand...
Click to collapse
did this , it didnt worked . im testing out the latest stable rom though
The factory zips on the Essential website can be flashed like any other ROM using TWRP.
spotmark said:
The factory zips on the Essential website can be flashed like any other ROM using TWRP.
Click to expand...
Click to collapse
So flashing them will allow you to take an ota? Do you need to flash them to both slots
Sent from my PH-1 using Tapatalk
dandan2980 said:
So flashing them will allow you to take an ota? Do you need to flash them to both slots
Click to expand...
Click to collapse
I've always just used TWRP, but as long as you're not rooted, I don't see why it wouldn't take an OTA.
AsianDuck said:
did this , it didnt worked . im testing out the latest stable rom though
Click to expand...
Click to collapse
Can you elaborate on what didn't work?
The thread about factory images of OB 3 contains all the stock image of OB3, in fact, it even restores more files than the one provided on essential website.
It should be the way to go because the script has also been edited so that it restores both partition A and B, making the bootloader locking process more safe
Take any version you wish https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
but make sure you take full dumps.
By the way, flash-all.bat is for Windows, flash-all.sh is for Mac and Linux
jamesst20 said:
Can you elaborate on what didn't work?
The thread about factory images of OB 3 contains all the stock image of OB3, in fact, it even restores more files than the one provided on essential website.
It should be the way to go because the script has also been edited so that it restores both partition A and B, making the bootloader locking process more safe
Take any version you wish https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
but make sure you take full dumps.
By the way, flash-all.bat is for Windows, flash-all.sh is for Mac and Linux
Click to expand...
Click to collapse
there were problems when installing the ob3 like the system a and system b refuses to be installed so i used the latest 7.1 and that works. i wasnt sure whats the problem i did unlock_critical too. (i took the first ob3 full dumps btw)
spotmark said:
I've always just used TWRP, but as long as you're not rooted, I don't see why it wouldn't take an OTA.
Click to expand...
Click to collapse
It worked and I was able to OTA accidently flashed OB1 and updated to OB2 and OB3 thanks for the info
Sent from my PH-1 using Tapatalk
dandan2980 said:
It worked and I was able to OTA accidently flashed OB1 and updated to OB2 and OB3 thanks for the info
Click to expand...
Click to collapse
We all know how to use TWRP, I don't know why people are so reluctant to flash the factory zips that way. It's easy as can be.
spotmark said:
We all know how to use TWRP, I don't know why people are so reluctant to flash the factory zips that way. It's easy as can be.
Click to expand...
Click to collapse
Totally agree it was simple AF makes back to stock a breeze I had no idea we could flash them.
Sent from my PH-1 using Tapatalk

Downgrading from B35

Hi all,
I have A2007U running B35 all stock and locked bootloader.
I'm having problems with MiFlash so I'm trying to find another solution.
Is there a way to downgrade using Sdcard and stock recovery?
you should able to downgrade to B32 with edl tool following this post
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
vic_singh said:
Hi all,
I have A2007U running B35 all stock and locked bootloader.
I'm having problems with MiFlash so I'm trying to find another solution.
Is there a way to downgrade using Sdcard and stock recovery?
Click to expand...
Click to collapse
You can downgrade without a PC. you need to find the official B32 update package, unzip it (there should be an update.zip inside the zip that you downloaded), and put that update.zip on the SD card. Then go to Settings, Updates, and install the B32. It will downgrade the system no problem.
Any reason to roll back from the 35?
Skv012a said:
Any reason to roll back from the 35?
Click to expand...
Click to collapse
I'm having tons of issues with unlocking bootloader. I used the tool but I was only able to unlock fastboot. I can't even install twrp.
Choose an username... said:
You can downgrade without a PC. you need to find the official B32 update package, unzip it (there should be an update.zip inside the zip that you downloaded), and put that update.zip on the SD card. Then go to Settings, Updates, and install the B32. It will downgrade the system no problem.
Click to expand...
Click to collapse
any clue where i can find the image from?
vic_singh said:
any clue where i can find the image from?
Click to expand...
Click to collapse
Well nope. It was on the US servers but they got shut down. Maybe @raystef66 knows?
Choose an username... said:
Well nope. It was on the US servers but they got shut down. Maybe @raystef66 knows?
Click to expand...
Click to collapse
looks like its still there
https://www.zteusa.com/axon-7
At fastboot, you need run a command "fastboot oem unlock", then you should be able to access twrp.
Your twrp is probably already flashed, just can not be access as you have not run the command "fastboot oem unlock".
vic_singh said:
I'm having tons of issues with unlocking bootloader. I used the tool but I was only able to unlock fastboot. I can't even install twrp.
Click to expand...
Click to collapse

[ROM][STOCK IN2011_11_C.21][FASTBOOT] Easily return method to OOS from custom ROMs or simply reflash OOS

Oneplus 8 Fastboot ROMs
DOWNLOADS:
https://www.androidfilehost.com/?w=files&flid=326825
Mirror:
Current version: IN2011_11_C.21_202205172355
PASSWORD: XDA2021 or XDA2022 (newest files)
​
infected_ said:
Made this little project using the script from @mauronofrio FASTBOOT ROMs to return OP8 to latest OOS, since I was always having issues doing so, and always ended up using the unbrick tool for OP8.
Enjoy! If you have any issues, just let me know using a post.
Regards.
Current FASTBOOT ROM 11.0.5.5 download link:
AFH Server:
OP8 OOS 11.0.5.5 FASTBOOT ROM
OP8 OOS 11.0.5.5 MAGISK PATCHED BOOT.IMG
Click to expand...
Click to collapse
I have a T-Mobile device, which I converted to Global and finally installed a custom ROM. For any updates, I have to follow the same route - go back to T-Mobile, then global and then any other ROM. Can I use this utility to go back directly to Global from custom or would I still need to first flash T-Mobile ROM?
sjgoel said:
I have a T-Mobile device, which I converted to Global and finally installed a custom ROM. For any updates, I have to follow the same route - go back to T-Mobile, then global and then any other ROM. Can I use this utility to go back directly to Global from custom or would I still need to first flash T-Mobile ROM?
Click to expand...
Click to collapse
Technically, this process would be the same as a conversion. Just see if you need to backup any other extra partition, like persist.img or other.
Regards.
thank you so much for this, ive been stuck or soft bricked for the last 4 days and this might just be my out.
Hi, thanks for this! Now I have a question, I have latest OOS with Magisk, but since upgrade to 11 i have System UI crashes and serious lags and freeze, I did 4 factory resets and its still there, I want to reflash all from 0, can I use this?
Thank you very much for the contribution
nikola1970 said:
Hi, thanks for this! Now I have a question, I have latest OOS with Magisk, but since upgrade to 11 i have System UI crashes and serious lags and freeze, I did 4 factory resets and its still there, I want to reflash all from 0, can I use this?
Click to expand...
Click to collapse
try reflashing on both slots.
infected_ said:
try reflashing on both slots.
Click to expand...
Click to collapse
Ok, so first I need to flash slot a, and right after that i am gonna flash b slot? Thanks man
showing my ignorance...where is the flash-all.bat script? Is that somewhere in this thread?
gloster2 said:
showing my ignorance...where is the flash-all.bat script? Is that somewhere in this t
Click to expand...
Click to collapse
There's a self extracting file (*.exe) inside the zip file. Have you run it, and checked the extracted files?
infected_ said:
There's a self extracting file (*.exe) inside the zip file. Have you run it, and checked the extracted files?
Click to expand...
Click to collapse
Thanks -- I didn't notice it was an executable. I think I'm ready to go, but just checking. Here's what I've done so far with my T-Mobile version OnePlus 8:
1. completed process to unlock the bootloader (unlocked phone, got token, applied token)
2. set up fastboot in a directory on my Windows PC
3. ran the self-extraction on OnePlus8Oxygen_15.E.35_OTA_0350_all_2103221815-FASTBOOT
Now I'm going to run flash-all.bat. Before I do that, do I need to back up any files, e.g. modem files? Thanks!
gloster2 said:
Thanks -- I didn't notice it was an executable. I think I'm ready to go, but just checking. Here's what I've done so far with my T-Mobile version OnePlus 8:
1. completed process to unlock the bootloader (unlocked phone, got token, applied token)
2. set up fastboot in a directory on my Windows PC
3. ran the self-extraction on OnePlus8Oxygen_15.E.35_OTA_0350_all_2103221815-FASTBOOT
Now I'm going to run flash-all.bat. Before I do that, do I need to back up any files, e.g. modem files? Thanks!
Click to expand...
Click to collapse
backup persist.img and modem.img just in case, and you should be ok to go.
PS: i'm going to upload the fastboot rom without the self extracting method to be easier for users.
Deleted
@infected_ Considering that I am coming from an unlocked bootloader, will this method re-lock the bootloader and is this carrier-branded compatible?
rodken said:
@infected_ Considering that I am coming from an unlocked bootloader, will this method re-lock the bootloader and is this carrier-branded compatible?
Click to expand...
Click to collapse
No, it won't relock the bootloader
infected_ said:
No, it won't relock the bootloader
Click to expand...
Click to collapse
Safe to use for Verizon OP8 5G UW or is this a method to go Global from a carrier-branded version?
infected_ said:
backup persist.img and modem.img just in case, and you should be ok to go.
PS: i'm going to upload the fastboot rom without the self extracting method to be easier for users.
Click to expand...
Click to collapse
sorry for another simple question; I haven't done system level things with Android in a long time. Where are instructions on how to backup those files? I did a little searching, but haven't found anything that works yet.
gloster2 said:
sorry for another simple question; I haven't done system level things with Android in a long time. Where are instructions on how to backup those files? I did a little searching, but haven't found anything that works yet.
Click to expand...
Click to collapse
There is an app for that.
rodken said:
There is an app for that.
Click to expand...
Click to collapse
Thanks! Now I realize that even though I have an unlocked bootloader, I don't have root access. Now I have to figure out how to get that. Sigh.
And...I see much conflicting information on how to root my bootloader unlocked T-Mobile version OnePlus 8. Any advice/pointers to info on the best/easiest way to root it?

Categories

Resources