If you want to repost this internal OTA to other websites (other than XDA itself), please ask me for permission, thanks.
Click to expand...
Click to collapse
WARNING!
This is early internal test build, so LATER OTA UPDATES CAN'T BE GUARANTEED!
If you don't have unlocked bootloader, you'll unable to roll back to stable build!
Please be careful when testing!
Click to expand...
Click to collapse
Now I think it's time to bring you back to canary labs faster than beta labs.
Internal build version: CTL-4040-0-00WW-B01
It will be updated from: CTL-354K-0-00WW-B01, which is not pushed to public
As I've warned before - having an unlocked bootloader is strongly recommended.
So recent builds removed handy 874 dialing codes, we have to install them under recovery or Nokia Extensions.
UPDATE: Thanks everyone. To fix microphone bug, please disable the microphone permission of the "Google" app.
You'll lose "OK Google" ability, but you can make telephone call properly.
Click to expand...
Click to collapse
Let me tell you how to verify:
1. Dial *#*#227#*#* to check current Version. If older than CTL-354J-0-00WW-B01 (check if the letter is greater than J), update to 354J before proceed.
FYI, 354J is August 2019 Security Update.
Alternately, you can use command "fastboot oem getversions" under fastboot mode / Download mode to check current firmware version.
If newer than 354J (probably 354N when this post released), you'll need to downgrade your phone back to at most 354H - which can't be done easily without unlocked bootloader.
2. Install CTL-354K-0-00WW-B01-354J-0-00WW-B01-update.zip with Nokia Extensions OTA Update module or adb sideload under recovery.
3. Reboot your phone.
4. Install CTL-4040-0-00WW-B01-354K-0-00WW-B01-update.zip with Nokia Extensions OTA Update module or adb sideload under recovery.
5. Reboot your phone.
That's it.
If minor fixes released, I will upload them as well, then use the same method to install it.
To root the phone, you may want to use Magisk 20 released October 12th, 2019 or newer.
Download link:
Full OTA link (CTL-408B-0-00WW-B03-update.zip): https://android.googleapis.com/pack.../29ad191f90eedc643ed008dc06c81ed3c5b5565a.zip
Following link now discontinued.
https://www.androidfilehost.com/?w=files&flid=299362
Dude I Did Not Find TA-1097 NOKIA 7.1?
[email protected]! said:
Dude I Did Not Find TA-1097 NOKIA 7.1?
Click to expand...
Click to collapse
Packages are identical, regardless of TA-1085, 1095, 1096, 1097, 1100.
Anybody try this? It's everything ok? No issues?
Sent from my TA-1021 using Tapatalk
Support for Project Mainline?
Will this update (or perhaps a future update) for the Nokia 7.1 to Android 10 support Project Mainline?
I ask because I’ve read in some places that only devices that ship with Android 10 can support Project Mainline, and in other places that devices upgraded to Android 10 can support Project Mainline.
Hello, There is an issue with going from 4080 to 408A. Noticed it's also uploaded twice, but not sure what the issue is. I get a sideload package zip error.
hikari_calyx said:
Packages are identical, regardless of TA-1085, 1095, 1096, 1097, 1100.
Click to expand...
Click to collapse
How to get its TWRP image?
UPDATE:
1. To users who have installed 4090: Please rollback the phone to 408B B01, and wait for the full OTA link to 408B B03.
2. To users who have installed 408B B01: Please rollback the phone to 408A then install 408A to 408B B03 package instead.
3. To users who have 354P currently, you can update to 408B B03 directly.
You can confirm the current build by dialing *#*#7837#*#*, expected output should look like this:
Version: 00WW_3_54P-B01
Click to expand...
Click to collapse
How to rollback?
1. Enter fastboot mode / download mode
2. Check your current slot by using "fastboot getvar current-slot"
3. If current slot is A, then execute:
Code:
fastboot --set-active=b oem HALT
4. If current slot is B, then execute:
Code:
fastboot --set-active=a oem HALT
5. Disconnect the phone and boot to recovery mode.
6. To users rollback from 408B B01, you can apply update package to 408B B03 here. To users rollback from 4090 B01, you may perform factory reset.
Zip package ota Android 10?! Anyone? [emoji1]
Sent from my Nokia 7.1 using Tapatalk
Full OTA link:
https://android.googleapis.com/pack.../29ad191f90eedc643ed008dc06c81ed3c5b5565a.zip
CTL-408B-0-00WW-B03-update.zip
Thx Calyx, work on every 7.1? ta-1095?!
Sent from my Nokia 7.1 using Tapatalk
dex87xda said:
Thx Calyx, work on every 7.1? ta-1095?!
Sent from my Nokia 7.1 using Tapatalk
Click to expand...
Click to collapse
It works on any version of Nokia 7.1, regardless of TA-1085, 1095, 1096, 1097, 1100.
is there diffence between this OTA and updated with CTL-408B-0-00WW-B03-354P-0-00WW-B01-update.zip????
There is different file size??
No difference
Sent from my TA-1021 using Tapatalk
hikari_calyx said:
It works on any version of Nokia 7.1, regardless of TA-1085, 1095, 1096, 1097, 1100.
Click to expand...
Click to collapse
Hi. Can the stable OTA be sideloaded over any Android Pie version or do we specifically need to be on 3.54P?
I would greatly appreciate any direction attempting to move from 4080 to 408A. When I try to sideload with adb in recovery I'm getting a package zip error and it will not update. I do have an unlocked bootloader and I've tried resetting the phone with twrp but not having any luck.
i have version ctl-256a-0-00ww-b07 . i need a file to update to android 9 then 10 using ADB sideload method .. thx HIKari
Related
Here are the latest updates for the dual sim and single sim Nova variants:
CAN-L11C432:
Full Update:
CAN-L11C432B340: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v77947/f1/full/update.zip
Changelog: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v77947/f1/full/changelog.xml
Small Update:
CAN-L11C432B340: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v77944/f1/full/update.zip
Changelog: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v77944/f1/full/changelog.xml
CAN-L01C432:
Full Update:
CAN-L01C432B340: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v77904/f1/full/update.zip
Changelog: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v77904/f1/full/changelog.xml
Small Update:
CAN-L01C432B340: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v77930/f1/full/update.zip
Changelog: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v77930/f1/full/changelog.xml
The Full Updates you should be able to install from Marshmallow which will bring you to the current release of Nougat on the Nova and the Small Updates you can install from the Nova Nougat build CAN-L11C432B320 and CAN-L01C432B320.
If your device comes up with NRD90M test-keys then for the CAN-L11C432 variant you can try installing this after to get the correct Build number showing and functionality working: http://update.hicloud.com:8180/TDS/...-L11_hw_eu/update_data_full_CAN-L11_hw_eu.zip and for the CAN-L01C432 variant: http://update.hicloud.com:8180/TDS/...-L01_hw_eu/update_data_full_CAN-L01_hw_eu.zip.
I have managed to get it to work on the CAN-L01C432 variant but a couple of others have not managed to install the hw eu update for their device which has left them with NRD90M test-keys showing under Build number and themes not working.
I tried to update but it fails at 41%. I'm on CAN-L01C02B130 , Vodafone branded.
pasmadferit said:
I tried to update but it fails at 41%. I'm on CAN-L01C02B130 , Vodafone branded.
Click to expand...
Click to collapse
These updates are for CAN-L01C432 and CAN-L11C432 variants of the Nova. You can try this if you want to but I am not sure if it will work on a branded device: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74460/f1/full/update.zip. This is the latest Nougat update I have found for the CAN-L01C02 variant of the Nova.
lintern said:
These updates are for CAN-L01C432 and CAN-L11C432 variants of the Nova. You can try this if you want to but I am not sure if it will work on a branded device: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74460/f1/full/update.zip. This is the latest Nougat update I have found for the CAN-L01C02 variant of the Nova.
Click to expand...
Click to collapse
thanks for the link but i have the same problem. On "updater" the phone didn't find it, i tried with putting down the phone with volume and power keys but it gave me the same error at 41%. Shame on Huawei that don't release the original firmware yet >.<
pasmadferit said:
thanks for the link but i have the same problem. On "updater" the phone didn't find it, i tried with putting down the phone with volume and power keys but it gave me the same error at 41%. Shame on Huawei that don't release the original firmware yet >.<
Click to expand...
Click to collapse
I had the same problem at first but after flashing this: https://drive.google.com/open?id=0B4T1GJ6EZ3LvTWNpZ0p5YXVINGs the Nougat update installed fine. The link is the stock EMUI 5 recovery which is for Nougat which I got of this page: https://forum.xda-developers.com/nova-plus/how-to/c432b320-android-7-0-available-try-t3527084/page7.
lintern said:
I had the same problem at first but after flashing this: https://drive.google.com/open?id=0B4T1GJ6EZ3LvTWNpZ0p5YXVINGs the Nougat update installed fine. The link is the stock EMUI 5 recovery which is for Nougats which I got of this page: https://forum.xda-developers.com/nova-plus/how-to/c432b320-android-7-0-available-try-t3527084/page7.
Click to expand...
Click to collapse
I'll try, thanks for the help man
pasmadferit said:
I'll try, thanks for the help man
Click to expand...
Click to collapse
It's up to you if you want to try it. You have to flash the recovery by adb first if you do this and then try updating again I see no reason why it should not work.
lintern said:
It's up to you if you want to try it. You have to flash the recovery by adb first if you do this and then try updating again I see no reason why it should not work.
Click to expand...
Click to collapse
I have to unlock bootloader first i think, right?
pasmadferit said:
I have to unlock bootloader first i think, right?
Click to expand...
Click to collapse
Unfortunately yes which is why I said it's up to you if you want to try it out. Some guys were lucky with the beta Nougat releases on the Nova which installed easily via the updater app or recovery on the device whereas you, me and others have had a bit more trouble which has required us to do more to update. Where it is a official Huawei recovery you may be able to flash it with adb without issues but I'm not sure. It's your call if you want to try it.
Thanks for the help man, i flashed first the recovery and then the update and all was ok. Very grateful.
pasmadferit said:
Thanks for the help man, i flashed first the recovery and then the update and all was ok. Very grateful.
Click to expand...
Click to collapse
No problem, did you install CAN-L01C02B130B407?
lintern said:
No problem, did you install CAN-L01C02B130B407?
Click to expand...
Click to collapse
I don't know what firmware is... In settings It shows me only model Number (Huawei CAN-L01) and serial number. Do you know how i can see it on emui 5.0?
pasmadferit said:
I don't know what firmware is... In settings It shows me only model Number (Huawei CAN-L01) and serial number. Do you know how i can see it on emui 5.0?
Click to expand...
Click to collapse
Extract this: http://update.hicloud.com:8180/TDS/...-L01_ti_it/update_data_full_CAN-L01_ti_it.zip and put the UPDATE.APP in a dload folder on the root of your SD Card and install it like the main Nougat update. This should fix it so the Build number shows up correctly and some other functionality issues. Once this is done next to Build Number it should say: CAN-L01C02B307, if it does then everything is working fine.
Hey I have downloaded CAN-l01 version, installed via fastboot (recovery.img, boot.img and system.img) but the updater is still missing from settings and the version number is NRD90M test-keys i'm not able to install the eu pack (update stops at 5%), how can I solve the missing updater?
mArIuS% said:
Hey I have downloaded CAN-l01 version, installed via fastboot (recovery.img, boot.img and system.img) but the updater is still missing from settings and the version number is NRD90M test-keys i'm not able to install the eu pack (update stops at 5%), how can I solve the missing updater?
Click to expand...
Click to collapse
I never installed mine by fastboot using adb, I extrated the big update then put it in a dload folder and installed using the three button method. I dunno why the hw eu pack is not installing as I had this issue and that installed fine for me.
If you installed this: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v77904/f1/full/update.zip then try installing this using the three button method: http://update.hicloud.com:8180/TDS/...-L01_hw_eu/update_data_full_CAN-L01_hw_eu.zip and if you have tried that and it did not work then try this: http://update.hicloud.com:8180/TDS/...L01_hw_eu/update_data_full_CAN-L01_hw_eu.zip.
lintern said:
I never installed mine by fastboot using adb, I extrated the big update then put it in a dload folder and installed using the three button method. I dunno why the hw eu pack is not installing as I had this issue and that installed fine for me.
If you installed this: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v77904/f1/full/update.zip then try installing this using the three button method: http://update.hicloud.com:8180/TDS/...-L01_hw_eu/update_data_full_CAN-L01_hw_eu.zip and if you have tried that and it did not work then try this: http://update.hicloud.com:8180/TDS/...L01_hw_eu/update_data_full_CAN-L01_hw_eu.zip.
Click to expand...
Click to collapse
It was the only way I was able to install the update method of the three buttons stopped updating to 5% whatever recovery I use.
Update.zip archive goes installed from CWM?
mArIuS% said:
It was the only way I was able to install the update method of the three buttons stopped updating to 5% whatever recovery I use.
Update.zip archive goes installed from CWM?
Click to expand...
Click to collapse
I have no idea then. The update worked fine for me using the three button method and all I had to do after was install the hw eu update that matched and it is all working fine. Yes you can install archived updates through custom recovery but I have not tried it with Huawei updates so I dunno what the outcome will be.
Here is a couple of screenshots which show the update working for me.
Flashed the CAN-L11C432B340 full update with the 3-button-method coming from Emui 4.1 (Android 6).
The update was successful up to 100%, but then I got a flash failed error. Phone booted succesful to Emui 5.0 with the NRD90M test-keys bug so in addition i flashed update_data_full_CAN-L11_hw_eu.zip and all seems to be fine except the hotspot functionality.
Does the hotspot feature work for you on B340? I cant enable it and after a while i get a settings force close....
will this work on Canadian Huawei Nova Plus variant?
jrosero said:
will this work on Canadian Huawei Nova Plus variant?
Click to expand...
Click to collapse
If your device Is CAN-L01C432 or CAN-L11C432 then yes if not then no.
I had trouble updating my Honor 6X (BLN-L21) after I rooted it, so I searched the whole xda to gain some information. Finally I made it, so I thought I could share this information with you guys, hope it helps, but I do not take responsibility if not, as you may have already heard, the Honor 6X (like every Kirin device) is very easy to brick.
- If everything is gone alright you should keep all of your data, apps and settings.
- If there is a big update, like from MM to N you maybe should backup all your stuff and relock the bootloader to update (big updates can relock frp so you can't unlock your bootloader then a rollback is the only way.
Successfully tried from:
B360 to B365
B365 to B367
Short Version (for expert users):
1. uninstall busybox bynaries and the Xposed Framework
2. uninstall magisk (inside the app)
3. flash stock recovery.img (of your actual firmware)
4. flash stock boot.img (of your actual firmware)
5. make OTA update (Reminder: safe update file)
6. flash twrp again and root
7. you are all done
Detailed Version:
#cmd commands#
1. backup your system over TWRP #adb reboot recovery# and do a backup there (for safety reasons)
2. #fastboot reboot#
3. uninstall busybox bynaries and the Xposed Framework(not just the app) (if you have it)
4. uninstall magisk (in app over "complete Uninstall button")
5. restart to bootloader #adb reboot bootloader#
6. flash stock recovery #fastboot flash recovery recovery.img# [use the recovery out of your actual firmware, how to extract is explained in the Forum I added at the end
7. flash stock boot #fastboot flash boot boot.img# [also use the extracted version of your actual package]
8. #fastboot reboot#
9. download update over OTA Update app (System update) in stock system. -> If the "System updater" app does not provide a Full version of the update package, the update could get stopped at 8% saying it could not verify the update, if so, just take the step to the error and reboot, if you then search for an update again, the "System updater" should now show you a Full version of the update package. like "BLN-L21C432B365-FULL"
10. you should safe that update files out of the HwOUC folder, so you can extract the recovery.img and boot.img later before you restart your device to do the update, because the system deletes these files after successful update
11. update over OTA Update app (System update) in stock system
12. restart to bootloader (#adb restart bootloader#)
13. flash twrp again #fastboot flash recovery twrp-3.1.1-0-berlin.img# [use the OpenKirin twrp edition (the official leads to a bootloop] -> [url]https://forum.xda-developers.com/honor-6x/development/twrp-t3583413[/URL]
14. Important is not to boot to system after flashing TWRP, exactly like as you installed it the first time. So you do #fastboot reboot# and then Vol down + lock
15. backup your system over TWRP (for safety reasons)
16. #adb reboot recovery#
17. flash Magisk zip in TWRP again
18. reboot in twrp
19. you are ready to go with the latest stock rom
How to extract boot.img and recovery.img out of your actual firmware is explained here:
[url]https://forum.xda-developers.com/honor-6x/how-to/extract-stock-recovery-img-boot-img-img-t3676880[/URL] thanks @Khan ubaid
citizenserious said:
the Honor 6X is very easy to brick.
Click to expand...
Click to collapse
Not just the 6X but every Kirin device.
This work only with packages like "xxxB360-FULL" or even with smaller downloaded packages that just updates some files? And, if I choose to do this with the FULL package do i have to re modify all the settings that i use actually?
RedSkull23 said:
This work only with packages like "xxxB360-FULL" or even with smaller downloaded packages that just updates some files? And, if I choose to do this with the FULL package do i have to re modify all the settings that i use actually?
Click to expand...
Click to collapse
I already tried it with the FULL package (edited the Guide btw.) you keep all your settings and stuff like before.
If it doesn't show you the FULL package just try the update until it fails, the system than will show you a FULL version of the update after the restart and research. That worked for me so far.
Hope I could help
citizenserious said:
I already tried it with the FULL package (edited the Guide btw.) you keep all your settings and stuff like before.
If it doesn't show you the FULL package just try the update until it fails, the system than will show you a FULL version of the update after the restart and research. That worked for me so far.
Hope I could help
Click to expand...
Click to collapse
What a nice notice, thanks dude! I already own the FULL, i only was worried about the fact that i could lose my data with the FULL one, i waa seeing it a clean firmware install but after this i can go straight with the update. I'll do that later today
RedSkull23 said:
What a nice notice, thanks dude! I already own the FULL, i only was worried about the fact that i could lose my data with the FULL one, i waa seeing it a clean firmware install but after this i can go straight with the update. I'll do that later today
Click to expand...
Click to collapse
I have done it that way yesterday, from B365 to B367 with the FULL package.
But nevertheless please back up your data.
edit: please let us know if it worked for you too
Thank for this guide. I might use this when an update comes.
[email protected] said:
Click to expand...
Click to collapse
What's the matter?
citizenserious said:
I have done it that way yesterday, from B365 to B367 with the FULL package.
But nevertheless please back up your data.
edit: please let us know if it worked for you too
Click to expand...
Click to collapse
Finally i found some time to dedicate on updating my phone, and I'm happy to say that it worked. I made from B360 to B365 and from B365 to B367, both worked at first shot. The only thing that i just can't understand is why the OTA package downloaded yesterday worked immediately, while the same B365-FULL package downloaded a month ago, copied on PC before starting it and later started didn't. With stock recovery and boot images obviously. I tried to start it later but nothing, i tried dload method with the update.app but neither that worked. Probably the OTA downloaded creates a sort of signature that can't be recreated that easily, if the same package fails through dload method... But what matters most is that now I'm on B367, protected with the latest security patch. Sorry for the late answer, time is hard to find... Thanks
Hi
Can someone upload the boot.img and and recovery.img from B367
Thanks in advance
Archerous said:
Hi
Can someone upload the boot.img and and recovery.img from B367
Thanks in advance
Click to expand...
Click to collapse
B367 of which model BLN-LXXCXXX?
shashank1320 said:
B367 of which model BLN-LXXCXXX?
Click to expand...
Click to collapse
I forgot sorry
BLN-L21C432B367
Archerous said:
I forgot sorry
BLN-L21C432B367
Click to expand...
Click to collapse
Check repository thread. Redskull23 has updated there. You may find in OP also in that thread. Link to the thread in my signature
shashank1320 said:
Check repository thread. Redskull23 has updated there. You may find in OP also in that thread. Link to the thread in my signature
Click to expand...
Click to collapse
There is no B367 in the Repository,no boot.img or recovery. thanks for you help
I wait for the next update,and i will not forget to save the update.app to pc. And extract the files
Archerous said:
There is no B367 in the Repository,no boot.img or recovery. thanks for you help
I wait for the next update,and i will not forget to save the update.app to pc. And extract the files
Click to expand...
Click to collapse
@RedSkull23, please see bro. You have updated to this and may be able to share :good:
shashank1320 said:
@RedSkull23, please see bro. You have updated to this and may be able to share :good:
Click to expand...
Click to collapse
I share ist,with the next update :good:
shashank1320 said:
@RedSkull23, please see bro. You have updated to this and may be able to share :good:
Click to expand...
Click to collapse
If we find the B367 package I'll upload everything from it!
I was on rooted BLN-L24C5678B360, and I want to take the OTA 365, so I flashed stock recovery and boot, reboot into system and started the update, but it failed, afterwards the phone stuck at booting up screen.
I have to boot into fastboot and run "fastboot oem relock [my unlock code]" to relock it, then followed by a factory reset. But when it comes to update, it failed again. Upon reboot, it stuck again with the message "Your device has failed verification and may not work properly."
What did I do wrong?
Update: recovered with the official rollback software to 6.0.
shadowcliffs said:
I was on rooted BLN-L24C5678B360, and I want to take the OTA 365, so I flashed stock recovery and boot, reboot into system and started the update, but it failed, afterwards the phone stuck at booting up screen.
I have to boot into fastboot and run "fastboot oem relock [my unlock code]" to relock it, then followed by a factory reset. But when it comes to update, it failed again. Upon reboot, it stuck again with the message "Your device has failed verification and may not work properly."
What did I do wrong?
Click to expand...
Click to collapse
You can try full firmware for b365 if available via dload.
Unlock your bootloader and it will boot to twrp and then boot normally.
Hi folks
Can you help me to find last modem for pixel XL?
I attached my current baseband version
My volte is off and can't turn it on
I'm on pure nexus last version
And lte+ not showing up
anyone ? any help ??
Wouldn't the latest radio be in the most recent factory images from google? Can't you just download it from google (October security patch) and flash it via fastboot?
Pain-N-Panic said:
Wouldn't the latest radio be in the most recent factory images from google? Can't you just download it from google (October security patch) and flash it via fastboot?
Click to expand...
Click to collapse
^^^^ This is correct.
Download the latest factory and unzip it.
Inside youll see another zip archive, unzip it.
One of the files inside the second zip archive is "modem.img"
Start a cmd or terminal window in the location of the file, and put your phone into bootloader/fastboot.
Run the command "fastboot devices" and make sure your device is connected, then run "fastboot flash modem modem.img"
Pain-N-Panic said:
Wouldn't the latest radio be in the most recent factory images from google? Can't you just download it from google (October security patch) and flash it via fastboot?
Click to expand...
Click to collapse
Thank you very much
Didn't know that
But October security patch is for Oreo 8 and I'm currently running pure nexus 7.1.2
Is that OK to install Oreo radio and modem to 7.1.2?
daniking said:
Thank you very much
Didn't know that
But October security patch is for Oreo 8 and I'm currently running pure nexus 7.1.2
Is that OK to install Oreo radio and modem to 7.1.2?
Click to expand...
Click to collapse
Based on what another user stated in this thread.....yes. however, I've never mixed radios with mismatched builds before so I can't say from personal experience.
If you are having the cannot update issue and have the global variant of the OP9 Pro, you probably had flashed the EU (or other / wrong software version) boot.img.
If your software version is anything other than 11.2, (including 11.2.1.1) you will need to get a boot.img from someone else or pull it from OnePlus website for your software version (once OnePlus gets to adding the OnePlus 9 Pro to their website) for that OOS Software version and can still use the following, but replace steps 3 and 6 with your .img file name.
If your software version is 11.2 and you have a global model, the stock boot.img for global 11.2 is attached.
Simply plug your phone into the computer with USB debugging enabled and trust the computer for the adb connection. Open up command prompt window and make sure you cd [platform tools \ adb directory], a.k.a. change the command prompt directory to your platform tools / adb folder.
Type in the command prompt window: adb reboot bootloader
Once in bootloader, type: fastboot boot 11.2_global_OP9Pro_boot.img
Verify the phone boots
If it boots fine, follow step 2 again then...
Once in bootloader, type: fastboot flash boot 11.2_global_OP9Pro_boot.img
You will now be unrooted and able to update your OP9 Pro to the latest software version, which is currently (as of 4/2/21) 11.2.2.2.
All credit goes to purpleman2k for providing the boot image on 11.2 Global and other diagnosing help.
-----------------------------------------------------------------------------
11.2 Global Boot.img download links:
Gofile - Free Unlimited File Sharing and Storage
Gofile is a free, secure file sharing and storage platform. With unlimited bandwidth and storage, you can easily store and share files of any type without any limits. Our advanced features, such as CDN support and password protection, make Gofile the ideal choice for individuals and businesses...
gofile.io
Filebin | 84b77xbio25j9cfh
Convenient file sharing. Think of it as Pastebin for files. Registration is not required. Large files are supported.
filebin.net
Contact me if links are expired when you try to download.
Prior to this it would download the OTA update but I would have error installing. I'm not unable to download it.
Do you know where the OTA is download is stored so I can manually remove it and try to download it again
do I use this if I want to get back on the global firmware? I flashed the EU to get the latest update as I couldn't get the updates due to my EU boot.img.
Also, do we patch it to get root again?
ahh123 said:
Prior to this it would download the OTA update but I would have error installing. I'm not unable to download it.
Do you know where the OTA is download is stored so I can manually remove it and try to download it again
Click to expand...
Click to collapse
Its a hidden folder in storage. It's under ".ota".
vibrantliker said:
do I use this if I want to get back on the global firmware? I flashed the EU to get the latest update as I couldn't get the updates due to my EU boot.img.
Also, do we patch it to get root again?
Click to expand...
Click to collapse
What OOS software version are you on? If you are not on 11.2.2.2 now, I can assist...
bulletbling said:
Its a hidden folder in storage. It's under ".ota".
What OOS software version are you on? If you are not on 11.2.2.2 now, I can assist...
Click to expand...
Click to collapse
It's not there. When I start up the OTA update, it immediately states it "Couldn't update".
ahh123 said:
It's not there. When I start up the OTA update, it immediately states it "Couldn't update".
Click to expand...
Click to collapse
If it's not there then it's not downloaded.
bulletbling said:
Its a hidden folder in storage. It's under ".ota".
What OOS software version are you on? If you are not on 11.2.2.2 now, I can assist...
Click to expand...
Click to collapse
I'm on 11.2.2.2 BA, but would like to get back to AA 11.2.2.2
vibrantliker said:
I'm on 11.2.2.2 BA, but would like to get back to AA 11.2.2.2
Click to expand...
Click to collapse
Currently that is not possible until OnePlus posts the full system images or a fellow member can get a fresh one and backed up and packed for install.
bulletbling said:
Currently that is not possible until OnePlus posts the full system images or a fellow member can get a fresh one and backed up and packed for install.
Click to expand...
Click to collapse
ok thanks
bulletbling said:
If it's not there then it's not download
Click to expand...
Click to collapse
Makes sense. I'm not sure why it's no longer even able to download the update.
I get an installation error and when I hit resume, it states "couldn't update, installation problem"
ahh123 said:
Makes sense. I'm not sure why it's no longer even able to download the update.
I get an installation error and when I hit resume, it states "couldn't update, installation problem"
Click to expand...
Click to collapse
What software version are you on? And are you rooted?
bulletbling said:
What software version are you on? And are you rooted?
Click to expand...
Click to collapse
I'm on 11.2.1.1.LE15AA, not rooted anymore after I flashed boot.img in the OP.
ahh123 said:
I'm on 11.2.1.1.LE15AA, not rooted anymore after I flashed boot.img in the OP.
Click to expand...
Click to collapse
That boot image is for 11.2., which is not for your 11.2.1.1, that's why.
Standby for upload...
ahh123 said:
I'm on 11.2.1.1.LE15AA, not rooted anymore after I flashed boot.img in the OP.
Click to expand...
Click to collapse
This is either 11.2.1.1 or 11.2.2.2 global boot.img. Sent to me by someone else for testing. Go ahead and try it with above instructions.
boot_wife.img
drive.google.com
If it doesn't work, I have two more for you to try.
bulletbling said:
This is either 11.2.1.1 or 11.2.2.2 global boot.img. Sent to me by someone else for testing. Go ahead and try it with above instructions.
boot_wife.img
drive.google.com
If it doesn't work, I have two more for you to try.
Click to expand...
Click to collapse
Thanks, so that was definitely part of the problem. The OTA now downloads but fails on installation. When I press resume to try again, it restarts the download.
ahh123 said:
Thanks, so that was definitely part of the problem. The OTA now downloads but fails on installation. When I press resume to try again, it restarts the download.
Click to expand...
Click to collapse
Is the .ota folder still empty / not there?
bulletbling said:
Is the .ota folder still empty / not there?
Click to expand...
Click to collapse
Don't see an .ota folder (I do see other hidden folders)
Edit: it's seems like it's installing now, "installing system update." Still fails and no .ota folder
ahh123 said:
Don't see an .ota folder (I do see other hidden folders)
Edit: it's seems like it's installing now, "installing system update." Still fails and no .ota folder
Click to expand...
Click to collapse
If it's still not working, try these boot images:
global_boot.img
drive.google.com
global_boot2.img
drive.google.com
bulletbling said:
If it's still not working, try these boot images:
global_boot.img
drive.google.com
global_boot2.img
drive.google.com
Click to expand...
Click to collapse
It seems like the same issue. Guess I'll just wait for the full download to be available
ahh123 said:
It seems like the same issue. Guess I'll just wait for the full download to be available
Click to expand...
Click to collapse
That's unfortunate. Make a post and see if anyone has the global boot image for 11.2.1.1.
Here's the F.13 update. The bootloader is back after this update so you guys can root again.
https://www.androidfilehost.com/?w=files&flid=337023
g96818 said:
Here's the F.13 update. The bootloader is back after this update so you guys can root again.
https://www.androidfilehost.com/?w=files&flid=3
Click to expand...
Click to collapse
Deleted
I had rooted my 9rt Indian version running Android 12.1 and the upgraded to Android 13 via OTA. Since then i have lost root and banking and other apps do not work. Currently i am running build MT2111_11_F.13. Can some one tell me what i need to do to get root back on Android 13 and necessary files i need. i am fairly new to this so any help would be much appreciated. Now on every reboot i'm getting orange state your device has been unlocked and can't be trusted and will now reboot in 5 seconds
milpro_7 said:
I had rooted my 9rt Indian version running Android 12.1 and the upgraded to Android 13 via OTA. Since then i have lost root and banking and other apps do not work. Currently i am running build MT2111_11_F.13. Can some one tell me what i need to do to get root back on Android 13 and necessary files i need. i am fairly new to this so any help would be much appreciated. Now on every reboot i'm getting orange state your device has been unlocked and can't be trusted and will now reboot in 5 seconds
Click to expand...
Click to collapse
There is link in the first post of the thread. Boot.img is what you need.
Open magisk app and patch boot.img.
Copy patched image to your computer, adb folder. Rename it to boot.img.
Take your phone to fastboot mode.
Connect to computer, open adb folder.
Open cmd. "Fastboot devices" - to control connectivity. Then "fasboot flash boot boot.img". That's it. Restart your phone.
F.14 continues to disable Fastboot mode
kunkute28 said:
F.14 continues to disable Fastboot mode
Click to expand...
Click to collapse
fastboot is open in F.14 as well as in F.13
penguinus said:
fastboot is open in F.14 as well as in F.13
Click to expand...
Click to collapse
I used abd to access fastboot mode but faied.
kunkute28 said:
I used abd to access fastboot mode but faied.
Click to expand...
Click to collapse
What exactly failed? What error you got?