Related
With the impending Nougat update coming soon for our device I thought it might be useful to put this information out there for those rooted individuals that want to not only be able to check for new updates in their device, but to download and possible install them too. Keep in mind though that, while you'll definitely be able to see and download the updates with this method, the actual installation may not work, especially if you have a custom kernel or the Xposed framework installed. If you rooted with SuperSU and are running the stock kernel like me however, then this should work just fine. Otherwise, just flash the stock kernel and uninstall Xposed before installing the update.
REQUIREMENTS:
Note 5
Stock Kernel(so the update works)
Stock Firmware(Only in some cases, may work with custom roms depending on how stock-based they are.)
Xposed Framework Installed(to get the update)
Flashfire App Installed(to install the update)
DISCLAIMER: As usual, I accept no responsibilty for what happens to your device. Though, in my opinion, thanks to ODIN, it's nearly impossible to brick a Samsung, anything you do to your device is obviously at your own risk.
(NOTE: This method does NOT work with Nougat roms right now, as there is currently no Xposed framework for Nougat.)
STEPS:
(Skip to step #5 if you've already installed the Xposed Framework.)
1) Go to Wanam's "Xposed for Samsung" page.
https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
2) Download and install the "Xposed Installer" app linked in the OP.
3) Then click on "Download" in the OP. Click on the latest version(currently "87.1"), then click on "Marshmallow" and download the zip file that says "ARM 64" to your device. Also, download the file that says "Xposed Uninstaller" from the link above to your device.
4) Reboot into TWRP, click "Install" and flash the 87.1 Xposed zip file and reboot.
-You now have Xposed.-
5) Open the Xposed app and click on "Download".
6) Press the search button and search for a module called "XTouchWiz" and install the latest version of it, then check the box next to "XTouchWiz" in the "Modules" section of Xposed to activate it.
7) Open the app and click on "Security Hacks" and make sure that "Fake System Status" is checked. This will set your device status to "Official" instead of "Custom". Afterwards reboot.
-You should now be able to check for updates.-
8) Open "Settings", click on "About Device", then click on "Download updates manually" to check for updates now.
9) If there is an update, then download it, but once the download is finished DO NOT INSTALL IT yet. If you do the regular install while rooted, then the installation may fail. It also may fail if you have the Xposed framework installed so you're going to want to uninstall that now. You're not going to be able to use it on Nougat at this point anyway.
10) Reboot into TWRP and flash the "Xposed Uninstaller" file that we downloaded earlier. Then reboot your device.
(NOTE: If you have a custom kernel installed, then you may want to flash the stock one back in ODIN first too or the install also may not work.)
-You should now be without Xposed or a custom kernel.-
11) Download the "Flashfire" app by Chainfire from the Play Store and open it. Once the app is opened it should automatically detect your downloaded OTA update. Just click on "Ok" to open the flash menu, then click on "Flash" to install the update.
-You should now have your new OTA update installed.-
12) You can now flash back any custom kernels or whatever. If for any reason the update failed then all you have to do is download the stock firmware and flash it back in ODIN, then just take the update regularly. You shouldn't lose any data or anything in the process.
Anyhow, I hope this has been helpful. Be sure to hit the THANKS button below if you found this helpful. Thank you!
Delete
If anyone wants to update manually to the new firmware version N920TUVS4DQA2(from February 01) in ODIN btw, then I linked it on this resource post here too:
https://forum.xda-developers.com/tm...esource-firmwareqa2-easy-root-method-t3555500
Also, anyone who wants to try and root with the SuperSU method that I mentioned above(rather than the modified kernel method), just to ensure you can still check for and install OTA updates after rooting by using this guide, then I also linked an easy way to do that at the link above.
I don't know about you guys, but personally I can't wait. Should be soon!
Android Nougat for the SM-N920C was released in Turkey a few days ago in case any of you aren't aware, which means that it's only a matter of weeks probably before the rest of us get it!
https://www.sammobile.com/firmwares/download/125835/N920CXXU3CQC7_N920COJV3CQC7_TUR/
Just a heads up, a couple of days ago T-Mobile released a new update N920TUVU4DQC2 for the SM-N920T variant of the Note 5. The update is not Nougat yet. It's still only Android 6.0.1, with the update content listed as "Various System Improvements". Since Nougat is coming out soon I'm not sure why they didn't just wait for that release to include any improvements. Maybe it's meant to help with the transition into Nougat somehow?
Anyhow, I thought I'd mention it in case any T-Mobile users out there, who are rooted and maybe running stock based custom roms, were unaware that there was a new firmware update available for download. You can refer to the OP for more details on how to download and install that update while rooted.
If you have another Note 5 variant, be sure to check the website for your service provider to see if you have any new updates you can be installing as well.
UPDATE: The Nougat update has already arrived for Sprint, AT&T and Verizon devices. The T-Mobile website now says that the Nougat update just went from being in the "Manufacturer Development" stage to the "Testing" stage, which means it could be tonight or maybe up to next week sometime.
Hey Man thankyou for the update's and the awesome tutorial.
Sent from my SM-G955F using XDA-Developers Legacy app
I have purchased a OnePlus 7 Pro from a friend of mine. He has already changed it from the T-Mobile to the International version via MSM. The current build number is 9.5.3.GM21AA and model number GM1915. I have currently installed TWRP 3.3.1-0 and rooted with Magisk 20.4. As I am new to OnePlus, I am confused as to go about updating the stock firmware, if I will lose root, updating to a custom rom. I have done this with other phones, Nexus 6P, 5X, Pixel 1 and Essential PH-1, but this seems different as I have a build number that is not necessarily meant for the T-Mobile version of this phone. I have read multiple guides and instructions throughout this forum, but don't seem to find the answers for my specific phone. Any help and direction would be very helpful.
If the phone has been updated to the international version then that's a REALLY old version, the latest version for International (Global) is 10.3.5, have you checked for an update via the phone already?
Update settings are in Settings > System > System Updates
If you want to upgrade manually, you can do that via Settings > System > System Updates > (Top Right) > Local Upgrade (Make sure the zip is in the main storage folder though or it won't be listed)
However, If you want to upgrade and keep root then you need to upgrade TWRP first, the latest is 3.4.0-0 from here : https://twrp.me/oneplus/oneplus7pro.html
Flash that first.
I've uploaded both the most recent versions onto my Android File Host :
Oxygen OS - Android 10.3.5 - Global - OnePlus 7 Pro (GM21AA) : https://www.androidfilehost.com/?fid=8889791610682950702
Oxygen OS - Android 10.0.8 - EU - OnePlus 7 Pro (GM21BA) : https://www.androidfilehost.com/?fid=8889791610682950715
My Android 10 Folder : https://www.androidfilehost.com/?w=files&flid=296897
So....
Grab the international version (which is the full rom)
Download the latest TWRP and Magisk
Reboot to TWRP (3.4.0-0)
Flash the full rom build (do not reboot yet)
Flash TWRP 3.4.0-0 (before rebooting) then reboot back into recovery
Flash latest Magisk then clear cache (not data)
Reboot
Check the Magisk version with the app : https://github.com/topjohnwu/Magisk/releases
I would suggest choosing the beta release in the app as Magisk 21.0 is available and works fine (see attached)
If it shows that the phone is not rooted then just reboot back into TWRP and flash Magisk again and reboot.
-----------------
If you're going to install a custom rom then ensure you read the first posts in the thread first as the dev will usually advise pre-requisites (i.e. A specific stock rom version to have installed first, a specific version of TWRP to use, etc)
(Also, try to use paragraphs, makes your post a lot more legible)
Thank you for the information, it is very helpful!!
I am currently on 9.3.5 which is how I got it from my friend. I was thankfully for it. I will review the files and upgrade when I get home from work and then look into crDroid 6.10. It has worked great on my PH-1.
In the event I need to reflash to stock, do I just Fastboot back?
njsges said:
Thank you for the information, it is very helpful!!
I am currently on 9.3.5 which is how I got it from my friend. I was thankfully for it. I will review the files and upgrade when I get home from work and then look into crDroid 6.10. It has worked great on my PH-1.
In the event I need to reflash to stock, do I just Fastboot back?
Click to expand...
Click to collapse
No, if you change rom you should really clear data so make sure you do backups before moving from rom to rom. As long as you still have TWRP you should be able to move between them.
djsubterrain said:
No, if you change rom you should really clear data so make sure you do backups before moving from rom to rom. As long as you still have TWRP you should be able to move between them.
Click to expand...
Click to collapse
Thank you again for your help!! The more I've used the Oxygen OS, it seems to have everything the custom roms have that I might need.
I did get an update message on Oxygen Updater app to install 10.0.3, also an older version. Per what you wrote previously, I am going to bypass that to 10.3.5.
njsges said:
Thank you again for your help!! The more I've used the Oxygen OS, it seems to have everything the custom roms have that I might need.
I did get an update message on Oxygen Updater app to install 10.0.3, also an older version. Per what you wrote previously, I am going to bypass that to 10.3.5.
Click to expand...
Click to collapse
Check this thread first : https://forum.xda-developers.com/oneplus-7-pro/help/how-to-convert-tmobile-op7-to-t3935947
Especially the part labelled *Future proofing Update*, the OPS file is part of the MSM fix.
You should really check in that thread first to confirm how to update properly. The process might be different since you're changing firmware.
djsubterrain said:
Check this thread first : https://forum.xda-developers.com/oneplus-7-pro/help/how-to-convert-tmobile-op7-to-t3935947
Especially the part labelled *Future proofing Update*, the OPS file is part of the MSM fix.
You should really check in that thread first to confirm how to update properly. The process might be different since you're changing firmware.
Click to expand...
Click to collapse
Thank you. The phone has already been switched from T-Mobile to Global. I'm not sure if the OPS patcher was done yet. I will text my friend and ask him. I wonder if it is detrimental to do it again while I am still on 9.3.5?
UPDATE: My friend flashed the ops file with the MSM tool download
SUCCESS!! Thank you for all of your help!!
Preamble / RamblingHello dear xda-community,
I am a little desperate right now. After hours of searching for solutions I am sadly out of luck and afraid I might destroy the system if I try to solve this issue any further by my own. :/
By no means I am an expert in flashing / rooting mobile devices, so please forgive me if I did something stupid.
But with that out of the way I hope you can help me. Thank you already for your efforts.
Have a great day,
TheAverageUser
The ProblemWhen trying to connect to a WiFi the connection disrupts and apparently the entire network management component (?) crashes and restarts.
I suspect it of crashing because the connection to the internet via my SIM card is disconnected as well for a short period of time after the WiFi tries to connect to a base station.
How I got here
Upgraded from LOS 17.1 to 18.1 like so
Installed TWRP as described here
Installed Magisk as described in the "Custom Recovery" section of this guide
Additional Information
After upgrading to LOS 18.1 I noticed that Magisk did not work anymore, so I tried to find a way to re-root my device.
A long search later I decided that I needed TWRP in order to root the device as many guides I found required this to be the case. Sadly I can't remember how I rooted the device the first time.
The mentioned method for installing Magisk seemed to be the only one working for me. (I did not find anything better.)
I would love to fix my current OS without having to start over, because setting it up again is very tedious.
Previous Setup (Before Upgrade)
OnePlus 6 (obviously ^^)
Lineage OS 17.1
Magisk
Lineage Recovery
Updates:
#1 Okay. Now I am even more confused. The phone just connected to my WiFi and it seems to work. I didn't do anything as of yet. I am going to investigate further to find out when exactly the connections fail. Honestly I don't like a 50:50 chance of it working ^^ (Just to be clear. My problem is not fixed as of yet.)
#2 For some reason the WiFi is now working. The only thing that I can think of which might have solve the issue is that I have uninstalled and reinstalled the "F-Droid Privilgeded Extension" for Magisk.
TheAverageUser said:
Preamble / RamblingHello dear xda-community,
I am a little desperate right now. After hours of searching for solutions I am sadly out of luck and afraid I might destroy the system if I try to solve this issue any further by my own. :/
By no means I am an expert in flashing / rooting mobile devices, so please forgive me if I did something stupid.
But with that out of the way I hope you can help me. Thank you already for your efforts.
Have a great day,
TheAverageUser
The ProblemWhen trying to connect to a WiFi the connection disrupts and apparently the entire network management component (?) crashes and restarts.
I suspect it of crashing because the connection to the internet via my SIM card is disconnected as well for a short period of time after the WiFi tries to connect to a base station.
How I got here
Upgraded from LOS 17.1 to 18.1 like so
Installed TWRP as described here
Installed Magisk as described in the "Custom Recovery" section of this guide
Additional Information
After upgrading to LOS 18.1 I noticed that Magisk did not work anymore, so I tried to find a way to re-root my device.
A long search later I decided that I needed TWRP in order to root the device as many guides I found required this to be the case. Sadly I can't remember how I rooted the device the first time.
The mentioned method for installing Magisk seemed to be the only one working for me. (I did not find anything better.)
I would love to fix my current OS without having to start over, because setting it up again is very tedious.
Previous Setup (Before Upgrade)
OnePlus 6 (obviously ^^)
Lineage OS 17.1
Magisk
Lineage Recovery
Updates:
#1 Okay. Now I am even more confused. The phone just connected to my WiFi and it seems to work. I didn't do anything as of yet. I am going to investigate further to find out when exactly the connections fail. Honestly I don't like a 50:50 chance of it working ^^ (Just to be clear. My problem is not fixed as of yet.)
Click to expand...
Click to collapse
Is it not because of your base OOS version?
Just do this and you are 100% okay.
1. Use MSM Tool here (it is like a full factory reset with a clean install - you have to unlock your bootloader again!!!)
2. Download latest OOS Full Update here, latest TWRP here, NikGapps here (Magisk if you like) and copy them into Device
3. Flash OOS, TWRP & Reboot to Recovery
4. Flash OOS, TWRP & Reboot to Recovery
5. Flash LOS-ROM, TWRP & Reboot to Recovery
6. Flash NikGapps (and Magisk) & get back to Menu
7. Select Wipe and just swipe to wipe data
8. Reboot to system
9. Done
Hello @tiga016 and @Pundy,
so here is an update on my situation:
For some reason the WiFi is now working. The only thing that I can think of which might have solve the issue is that I have uninstalled and reinstalled the "F-Droid Privilgeded Extension" for Magisk.
@Pundy
Thank you very much for this guide. For now I will continue to use my device in its current state, but as soon as I try to do a major update I will come back to your guide in order to install everything in a clean manner.
@tiga016
Thank you for your interest in my issue. For now I will consider this problem to be solved.
Pundy said:
Just do this and you are 100% okay.
1. Use MSM Tool here (it is like a full factory reset with a clean install - you have to unlock your bootloader again!!!)
2. Download latest OOS Full Update here, latest TWRP here, NikGapps here (Magisk if you like) and copy them into Device
3. Flash OOS, TWRP & Reboot to Recovery
4. Flash OOS, TWRP & Reboot to Recovery
5. Flash LOS-ROM, TWRP & Reboot to Recovery
6. Flash NikGapps (and Magisk) & get back to Menu
7. Select Wipe and just swipe to wipe data
8. Reboot to system
9. Done
Click to expand...
Click to collapse
Hello Pundy,
I have updated from LOS 17.1 to 18.1 (clean install) sadly wifi was not working with 17.1 and also not with 18.1. Therefore I have installed OOS (without TWRP) one of the latest version and made an update via wifi to the current version. So wifi is ok. Following the LOS howto, I was successful in installing the latest LOS BUT again wifi is not working...
Sadly also using the MSM Tool is not working. The MSM Tool does not connect with the OP6 (Sahara problem). I have tried it many times...
Any alternative?
BR Martin
Hi everyone, I could really use some help. My KB2005 is stuck in what looks like a boot loop. I took an OTA update after going into magisk and restoring images. After the update finished installing and before rebooting, I installed magisk to the inactive slot. Now when my phone boots up, it is stuck on the spinning circle boot up logo. It stays there, screen goes black, then maybe 30 seconds later I see the boot logo again.
I used MSM download to restore my phone to stock. Re rooted + safetynetfix, attempted to take the OTA update using the procedure above, and the same result happened (boot loop).
I then used the fastboot method to unbrick. Re rooted + safetynet fix, attempted to take OTA update using the procedure above, and again the same thing happened.
My phone will successfully take an OTA and not boot loop if I'm not rooted.
I could root + safetynet fix after taking the OTA, but the next time an update comes along, I'd like to be confident that using the magisk method to install the OTA will work.
Any help would be greatly appreciated. If there is any other information I can provide that can help please let me know. Cheers
EDIT - I did some digging - according to getvar all, my slot b is not 'successful'. To confirm, I force booted slot b and get a qualcomm crush dump screen.
behel1t said:
Hi everyone, I could really use some help. My KB2005 is stuck in what looks like a boot loop. I took an OTA update after going into magisk and restoring images. After the update finished installing and before rebooting, I installed magisk to the inactive slot. Now when my phone boots up, it is stuck on the spinning circle boot up logo. It stays there, screen goes black, then maybe 30 seconds later I see the boot logo again.
I used MSM download to restore my phone to stock. Re rooted + safetynetfix, attempted to take the OTA update using the procedure above, and the same result happened (boot loop).
I then used the fastboot method to unbrick. Re rooted + safetynet fix, attempted to take OTA update using the procedure above, and again the same thing happened.
My phone will successfully take an OTA and not boot loop if I'm not rooted.
I could root + safetynet fix after taking the OTA, but the next time an update comes along, I'd like to be confident that using the magisk method to install the OTA will work.
Any help would be greatly appreciated. If there is any other information I can provide that can help please let me know. Cheers
EDIT - I did some digging - according to getvar all, my slot b is not 'successful'. To confirm, I force booted slot b and get a qualcomm crush dump screen.
Click to expand...
Click to collapse
After you used magisk to flash to the inactive slot, did you disable all of the modules before rebooting? That might help. And you are not using twrp correct?
azoller1 said:
After you used magisk to flash to the inactive slot, did you disable all of the modules before rebooting? That might help. And you are not using twrp correct?
Click to expand...
Click to collapse
Hi, correct I am not using twrp. I tried unlocking the boot loader and not rooting. Receiving an OTA works and I can reboot. But oddly enough if I do a --set-active=otherslot, i get a qualcomm crashdump.
It appears that whenever I or magisk force change the active slot, I get a crash dump.
EDIT - Still unsuccessful. I've tried numerous times using MSM Download and the fastboot unbrick method by coomac. I haven't been able to --set-active=b a single time, it always ends up in a qualcomm crash dump. I suspect slot is B is corrupt.
Try to restore both slots with an older version of rom using local update. Then take ota and try.
kjslabber said:
Try to restore both slots with an older version of rom using local update. Then take ota and try.
Click to expand...
Click to collapse
I'd like to give this a shot but I have a couple of follow up questions: does an older version of the rom restore both slots vs newer versions just containing one slot? Or if I have that wrong, how do I flash both slots from local upgrade?
behel1t said:
I'd like to give this a shot but I have a couple of follow up questions: does an older version of the rom restore both slots vs newer versions just containing one slot? Or if I have that wrong, how do I flash both slots from local upgrade?
Click to expand...
Click to collapse
Install rom to first slot, boot system and do local update again and reboot. That will put same version on both slots. Then take the regular update to current new version. You do know how to do local updates don't you?
kjslabber said:
Install rom to first slot, boot system and do local update again and reboot. That will put same version on both slots. Then take the regular update to current new version. You do know how to do local updates don't you?
Click to expand...
Click to collapse
Thanks for the reply. I do yes. I'll give this method a shot. Cheers
UPDATE - Just finished using msm download to restore OOS 11.0.5.6 and then used local upgrade to flash OnePlus8TOxygen_15.O.20_GLO_0200_2011132216 (both 11.0.5.6). I can now successfully boot both slots!
Now I am going to root. install riru and safetynet fix in magisk.
When I am ready to take an OTA, the correct process would be to uninstall the safetynet fix and riru. Then uninstall magisk using restore images, download and install OTA but do not reboot. Go into magisk and install to other slot. Then providing a successfully boot, reinstall safetynet and riru. Is this correct?
UPDATE 2 - Qualcomm crashdump happened after taking an OTA using the method I outlined above. So I reverted back to the previous slot and am in the process of doing a local upgrade again using 11.0.5.6 to hopefully restore that slot to working.
Something about magisk installing to the other slot and forcing a slot change is causing this crash dump.
I had 11.0.5.6 on both slots. I rooted. I then completely unrooted (not restore images). Took an update. That booted. I booted that. Rooted it. Then for testing, completely unrooted again. Then I received the latest OTA. That installed and booted. So I'm rooting now on the latest getting ready for daily use.
I have no idea why using magisk to install root to the other slot and forcing a slot change is not working. I'm grateful that, with extra steps, i can at least reliably receive OTAs and continue on living rooted life.
So, right after the ota is finished installing, before rebooting, you go to magisk and install to inactive slot, then you reboot immediately correct?
azoller1 said:
So, right after the ota is finished installing, before rebooting, you go to magisk and install to inactive slot, then you reboot immediately correct?
Click to expand...
Click to collapse
Yup. Doing exactly that results in a Qualcomm crash dump every single time.
Only way for me to bypass the crash dump is to completely uninstall magisk. I take the OTA and reboot losing root. I use twrp to dump updated boot partition, and reinstall magisk to patch the boot dump. Then fastboot flash the new rooted boot dump.
behel1t said:
Yup. Doing exactly that results in a Qualcomm crash dump every single time.
Only way for me to bypass the crash dump is to completely uninstall magisk. I take the OTA and reboot losing root. I use twrp to dump updated boot partition, and reinstall magisk to patch the boot dump. Then fastboot flash the new rooted boot dump.
Click to expand...
Click to collapse
Well, that's really weird. Have you tried magisk-canary? Or are you using the stable v23?
azoller1 said:
Well, that's really weird. Have you tried magisk-canary? Or are you using the stable v23?
Click to expand...
Click to collapse
I'm on v23, I haven't tried Canary.
This used to work on v23, the Qualcomm crash dump just started four days ago. What happened? In early September, I started failing safetynet out of the blue. Safetynetfix was not working so I followed the steps that are now crossed out (they were not then) at the following link. About a week after following those steps, I revisited the site to find that a new safetynetfix was released that worked. It didn't need LSposed or Xprivacylua. I went into Xprivacylua and reversed the changes i made, and uninstalled it and Lsposed. Then I applied the new safetynetfix. Immediately upon reboot, my finger print sensor started say 'finger print hardware failure' on the lock screen, and I was unable to enroll any new fingerprints; I would get a popup error saying enrollment failed.
At this point I decided to restore my phone using an unbrick method for a couple of reasons: 1) I wanted my finger print scanner to work, 2) I wanted to start fresh on my phone for a few months, and 3) I used to unbrick my phone to restore to factory all the time when I messed around with my OP5T. This is when the Qualcomm crash dumps started happening every time when Magisk installs to the other slot. I've used the MSM download linked on this forum and the fastboot unbrick method. I Qualcomm crash every time magisk installs to the other slot and switches slots.
behel1t said:
I'm on v23, I haven't tried Canary.
This used to work on v23, the Qualcomm crash dump just started four days ago. What happened? In early September, I started failing safetynet out of the blue. Safetynetfix was not working so I followed the steps that are now crossed out (they were not then) at the following link. About a week after following those steps, I revisited the site to find that a new safetynetfix was released that worked. It didn't need LSposed or Xprivacylua. I went into Xprivacylua and reversed the changes i made, and uninstalled it and Lsposed. Then I applied the new safetynetfix. Immediately upon reboot, my finger print sensor started say 'finger print hardware failure' on the lock screen, and I was unable to enroll any new fingerprints; I would get a popup error saying enrollment failed.
At this point I decided to restore my phone using an unbrick method for a couple of reasons: 1) I wanted my finger print scanner to work, 2) I wanted to start fresh on my phone for a few months, and 3) I used to unbrick my phone to restore to factory all the time when I messed around with my OP5T. This is when the Qualcomm crash dumps started happening every time when Magisk installs to the other slot. I've used the MSM download linked on this forum and the fastboot unbrick method. I Qualcomm crash every time magisk installs to the other slot and switches slots.
Click to expand...
Click to collapse
Sorry, at this point I don't know why it isn't working. You seem to be doing everything correctly so I am not sure why it's not working properly. The only thing I could think of that might be the issue is, as far as I know, that Oneplus hasn't pushed a september update yet to merge the september security patch which could be the culprit, but I cant say for certain. I know for me, I use Sakura ROM, SafetyNet was failing early september when android had pushed the september patch, but Sakura ROM hadnt merged it yet, but when they did merge it everything was working fine. Anyways, hopefully someone else may be able to give you a better answer.
EDIT: It seems the latest OOS incremental update is breaking when trying to upgrade while rooted. You need to use the full ota zip and do local manual upgrade. See the last couple of posts in here: https://forum.xda-developers.com/t/oneplus-8t-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4193183/
azoller1 said:
Sorry, at this point I don't know why it isn't working. You seem to be doing everything correctly so I am not sure why it's not working properly. The only thing I could think of that might be the issue is, as far as I know, that Oneplus hasn't pushed a september update yet to merge the september security patch which could be the culprit, but I cant say for certain. I know for me, I use Sakura ROM, SafetyNet was failing early september when android had pushed the september patch, but Sakura ROM hadnt merged it yet, but when they did merge it everything was working fine. Anyways, hopefully someone else may be able to give you a better answer.
EDIT: It seems the latest OOS incremental update is breaking when trying to upgrade while rooted. You need to use the full ota zip and do local manual upgrade. See the last couple of posts in here: https://forum.xda-developers.com/t/oneplus-8t-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4193183/
Click to expand...
Click to collapse
Thanks for bringing this to my attention. This is definitely what is happening. You just just saved me from spending any more time on this mess. Cheers!
I just wanted to add that I had same problem with my OP8T and couldn't reflash the ROM and had to send my phone to OP to get the ROM put back on. Slot B still doesn't work. You at least were able to get the phone back working with MSN.
I have an LE2115. I tried to update install CRdroid, and during the process the guide required an upgrade to firmware F18.
I was already on the newest (F20 I think) firmware, so I figured a small roll back would be needed. I downloaded F18 from the CRdroid firmware link, and when it was run it ended up bricking the phone. Annoying, but I didn't think it the end of the world.
To unbrick it I downloaded the MSM global 11.2.10.10 and flashed the phone with A11 (11.2.10.10). I was able to get back into the phone, and everything seemed ok at first glance.
The problem is now I can't install any updates to get it back to android 13.
If I do a system ->system update -> check for updates -> download and install. It says it downloads update LE2115_11.F.17_2170_20021123112, installs it, and reboots.
After rebooting the phone shows a successfully installed update message, but when I look at under About the system is still on Android 11 (11.2.10.10). No change at all.
If I try sticking the OTA zip LE2115_11.F.17_2170_202211231112 in root, and using that for a local update the phone gives me a update failed message after a few seconds. No useful error messages at all.
Can someone point me in the right direction? I can't figure out how to get this off A11 and back to A13 (F18).
This is making me want to rip out my hair as everything I have tried has failed to get me onto a current firmware.
wizardknight said:
I have an LE2115. I tried to update install CRdroid, and during the process the guide required an upgrade to firmware F18.
I was already on the newest (F20 I think) firmware, so I figured a small roll back would be needed. I downloaded F18 from the CRdroid firmware link, and when it was run it ended up bricking the phone. Annoying, but I didn't think it the end of the world.
To unbrick it I downloaded the MSM global 11.2.10.10 and flashed the phone with A11 (11.2.10.10). I was able to get back into the phone, and everything seemed ok at first glance.
The problem is now I can't install any updates to get it back to android 13.
If I do a system ->system update -> check for updates -> download and install. It says it downloads update LE2115_11.F.17_2170_20021123112, installs it, and reboots.
After rebooting the phone shows a successfully installed update message, but when I look at under About the system is still on Android 11 (11.2.10.10). No change at all.
If I try sticking the OTA zip LE2115_11.F.17_2170_202211231112 in root, and using that for a local update the phone gives me a update failed message after a few seconds. No useful error messages at all.
Can someone point me in the right direction? I can't figure out how to get this off A11 and back to A13 (F18).
This is making me want to rip out my hair as everything I have tried has failed to get me onto a current firmware.
Click to expand...
Click to collapse
I have the same device. After the 11.2.10.10 comes C48 first a12 build but it's marked F17 update. Then comes C-66 it's also marked F-17. Take it. Next update you guessed is labeled F-17 and it is actually F-17. Android 13. Then you will get F-18 ota as well. Then have to go into oxygen updater from playstore and update to F20. Latest with Jan sec patch. Since they dropped Android 13 all their device updates for op9 are labeled wrong. After msm you started on 11.2.4.4. I flash lineage and mess with things but mostly stay on stock as it's great and cam is good on os. Good luck. Check out pixelify by Kingsman 44. Real nice for op9 also.
mattie_49 said:
I have the same device. After the 11.2.10.10 comes C48 first a12 build but it's marked F17 update. Then comes C-66 it's also marked F-17. Take it. Next update you guessed is labeled F-17 and it is actually F-17. Android 13. Then you will get F-18 ota as well. Then have to go into oxygen updater from playstore and update to F20. Latest with Jan sec patch. Since they dropped Android 13 all their device updates for op9 are labeled wrong. After msm you started on 11.2.4.4. I flash lineage and mess with things but mostly stay on stock as it's great and cam is good on os. Good luck. Check out pixelify by Kingsman 44. Real nice for op9 also.
Click to expand...
Click to collapse
Ok. Thanks. I will run the update multiple times, and see if I can get to F18.
I can't believe the naming is all buggered up. Ok, well maybe I can believe it. Seems like OnePlus is just not doing a good job anymore, but there are not many other flagship grade phones with unlocked boot loaders and custom roms anymore (and I have been using custom android roms since the touch pro 2 days). It's making me a sad panda.
I just upgraded from a OnePlus 7t to the 9 because I got a crazy good price for an open box phone on clearance. Now I am starting to wonder if I made the wrong decision.
If I have to download 5+ updates every time something doesn't flash right I am going to burn though my 1TB internet cap in no time.
Update:
After ~10gb of updates I got to F18.
Now to go and get a custom rom on this thing, and hope I don't have to unbrick it again.