[Q] Bootloader upgrade after Android 5.0 update - Nexus 5 Q&A, Help & Troubleshooting

I have updated my Nexus 5 to Android 5.0 manually via "adb sideload" and noticed, that the bootloader was not upgraded.
Should i upgrade my bootloader manually?
Thanks for your answers in advance.
Greetings,
mst0

Does nobody know an answer?

It's the same bootloader as the last preview so if you were using that it won't change

I've never installed the preview.
I updated from 4.4.4 to 5.0 and noticed, that my bootloader didnt't upgrade(but the radio did).

(To the top)

If your stock then when a update comes out it won't install. Other then that it doesn't affect anything.

So if i don't upgrade manually i won't be able to update Android.
Did i understand this correctly?
Are there any downsides, if I upgrade the bootloader?

mst0 said:
So if i don't upgrade manually i won't be able to update Android.
Did i understand this correctly?
Are there any downsides, if I upgrade the bootloader?
Click to expand...
Click to collapse
If your running perfectly fine now then don't worry about it. If in the future you have issues upgrading or device won't boot properly then update it.
If you recieve a OTA update it'll check the version number of your bootloader and if it doesn't match what it's supposed to be then the OTA will refuse to install. I ran my nexus 7 1st edition for 8 months with an older version bootloader with no neg results. Updated it when flashing the Factory image, not that it needed it. Just for the sake of argument go ahead and update the bootloader using fastboot. Google updated the bootloader for a reason right?

Related

will I lose root on the latest OTA update?

As the title says - the latest OTA update, if I update will I lose root?
Thanks!
From what I understand, for a clean update OTA the firmware needs to be stock unrooted. The bootloader locked or unlocked.
Other people have succeeded in updating OTA with a modified system and able to patch, but it varies and it seems a lot of tweaking was involved after. I am no expert though.
eastdata said:
From what I understand, for a clean update OTA the firmware needs to be stock unrooted. The bootloader locked or unlocked.
Click to expand...
Click to collapse
Till yesterday i thought the same.
Seems like it works also when it is rooted.
[GUIDE] How To Update Rooted Moto G ( US Global GSM)
secretkloud said:
Then I tried again. It went smoothly. And I still have root
Click to expand...
Click to collapse
mokkami said:
Till yesterday i thought the same.
Seems like it works also when it is rooted.
[GUIDE] How To Update Rooted Moto G ( US Global GSM)
Click to expand...
Click to collapse
So if I understand that thread correctly, if a system file is modified, the update will fail? So adding files (su apk and binaries) doesn't create a situation where the update fails? ...This is my dilemma in trying to understand what modified actually means. It's been a while since attempting mods on a device and it was easier on my last one.
Off topic, will unlocking the bootloader allow access to the stock recovery? I can reboot into it, but any command from the menu just gives me a No command screen or reboots the device. I can't remember it being this convoluted on my old phone. Yes, I know that the up key selects and the down is to navigate...
i just flash stock recovery and then updated.
after update i still have root, so i just flash back TWRP
Backup with CWM, factory reset, update, restore data.
@kurt99 and @theoneofgod
What firmware are you running and what model (any mods)?
I imagine that OTA updates are different for each version firmware...
eastdata said:
So if I understand that thread correctly, if a system file is modified, the update will fail? So adding files (su apk and binaries) doesn't create a situation where the update fails? ...This is my dilemma in trying to understand what modified actually means. It's been a while since attempting mods on a device and it was easier on my last one.
Off topic, will unlocking the bootloader allow access to the stock recovery? I can reboot into it, but any command from the menu just gives me a No command screen or reboots the device. I can't remember it being this convoluted on my old phone. Yes, I know that the up key selects and the down is to navigate...
Click to expand...
Click to collapse
While it seems that OTAs are quite sensible to system changes whatever that means, it turned out that root doesn´t break the possibility to update.
You can access stock recovery with or without unlocked bootloader. This "no command screen" is a known thing and can easily be overcome by holding power and volume up buttons for 3 secs while on that screen.
drfr said:
You can access stock recovery with or without unlocked bootloader. This "no command screen" is a known thing and can easily be overcome by holding power and volume up buttons for 3 secs while on that screen.
Click to expand...
Click to collapse
Thanks so much (I've been living in Android 2.1 world). :angel:
Standard UK retail, rooted ran the OTA update with no issues, and remains rooted.
eastdata said:
@kurt99 and @theoneofgod
What firmware are you running and what model (any mods)?
I imagine that OTA updates are different for each version firmware...
Click to expand...
Click to collapse
Also Standard UK retail and remains rooted, also use XPOSED .

Is Unlocking the Bootloader prevent automatic OTA updates?

Greetings,
Just bought a brand new (directly from Google) Nexus 5. It came with 4.4.3 and immediately notified about an "update available", in which it downloaded and installed 4.4.4.
I then went on and Unlocked my bootloader in preparation for a root (I did not root yet, full stock). But I am not getting any update for Lollipop, not even when I manually Check for Updates.
Are these OTA updates come/pushed randomly, or did the Unlocking of the bootloader prevented an automatic OTA update?
I am aware of the option to manually update, I am just curious if the Unlocking prevents updates. If so, if I re-lock the bootloader again will I then get the OTA update?
Thanks.
No, it doesn't change anything. OTA updates are staged so you just probably haven't had it yet...
Unlocking does not affect OTA. But keep in mind you'll likely have to re-root if you get auto updated.
Thank you both!
Am I correct to assume that Rooting also will not prevent OTA updates?
sbi1 said:
Thank you both!
Am I correct to assume that Rooting also will not prevent OTA updates?
Click to expand...
Click to collapse
It won't prevent getting the ota but it will prevent it from installing
Sent from my Nexus 9 using XDA Free mobile app
Gota. So either:
Stock+Root and no updates
Stock+No-Root
Or Root+Custom
?!
sbi1 said:
Gota. So either:
Stock+Root and no updates
Stock+No-Root
Or Root+Custom
?!
Click to expand...
Click to collapse
In order for the ota to install you have to be 100% stock system, kernel, recovery, and radio. If you've modified any of those you'll have to return them to stock before the ota will install. There are ways to do that but it depends on the specifics of any modifications you've done to the device. Frankly, it's easier to just flash the new factory image than it is to take the ota if you've modified your device.
Edit, to the best of my knowledge modifying your device, short of deleting our freezing some system files specifically related to receiving updates, will not prevent you from getting the ota, just installing it.
Sent from my Nexus 9 using XDA Free mobile app
OK, so just to make sure I understand: Is Unlocking the Bootloader making my system not 100% stock? Which means, even if the update downloads it will not install?
Also - again, if I understand correctly - based on what you say I can root, I will receive the update OTA but it won't install. Is this correct?
sbi1 said:
OK, so just to make sure I understand: Is Unlocking the Bootloader making my system not 100% stock? Which means, even if the update downloads it will not install?
Also - again, if I understand correctly - based on what you say I can root, I will receive the update OTA but it won't install. Is this correct?
Click to expand...
Click to collapse
If you just unlock the bootloader you should have no trouble installing the ota. You'll have to unroot to install the ota. You can use the full unroot option in supersu
Sent from my Nexus 9 using XDA Free mobile app

[Q] Can't update to Android 5.0 Lollipop, the update isn't showing up anymore.

Hello,
I own a Nexus 5 and it has not been Rooted or Unlocked (bootloader) but now when I check for the official Lollipop 5.0 OTA update it doesn't show up. The notification was there for about a month but i didn't wanted to download to avoid early bugs. Now when i check it doesn't show any update ? stuck on 4.4.4 for now. Is the roll out on Hold ? Can anyone help me out here.
akki0920 said:
Hello,
I own a Nexus 5 and it has not been Rooted or Unlocked (bootloader) but now when I check for the official Lollipop 5.0 OTA update it doesn't show up. The notification was there for about a month but i didn't wanted to download to avoid early bugs. Now when i check it doesn't show any update ? stuck on 4.4.4 for now. Is the roll out on Hold ? Can anyone help me out here.
Click to expand...
Click to collapse
Wait or flash it by yourself.
Looking for the Official Update via OTA. Flashing will require me to Unlock the Bootloader and loose all data
akki0920 said:
Looking for the Official Update via OTA. Flashing will require me to Unlock the Bootloader and loose all data
Click to expand...
Click to collapse
I know. But nobody can tell you for how much time you will have to look for OTA. I also read somewhere, that all units probably wouldn't get 5.0.1 and will go straight to 5.1.
So it's your choose. It's not such a big deal to copy data to PC and vice versa.
Regards, Zagor
Thanks Pal, I shall then wait for Android 5.1 As KitKat 4.4.4 is stable enough to use.
akki0920 said:
Looking for the Official Update via OTA. Flashing will require me to Unlock the Bootloader and loose all data
Click to expand...
Click to collapse
Flashing an OTA manually doesn't require unlocking of bootloader or losing data. Follow Section A from here: http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217 - you just need the zipped update and ADB on your PC.
This zip will go from KTU84P to LRX21O (aka 5.0): http://android.clients.google.com/p...ed-hammerhead-LRX21O-from-KTU84P.c1a33561.zip
You could then see if you get prompted to update to 5.0.1. If not, then flash this to go from LRX21O to LRX22C: http://android.clients.google.com/p...ed-hammerhead-LRX22C-from-LRX21O.785a2f7a.zip
It's interesting that you're not being given that option in 4.4.4 though... have Google stopped pushing the Lollipop updates altogether?
akki0920 said:
Hello,
I own a Nexus 5 and it has not been Rooted or Unlocked (bootloader) but now when I check for the official Lollipop 5.0 OTA update it doesn't show up. The notification was there for about a month but i didn't wanted to download to avoid early bugs. Now when i check it doesn't show any update ? stuck on 4.4.4 for now. Is the roll out on Hold ? Can anyone help me out here.
Click to expand...
Click to collapse
This has been asked and answered a million times.
Search before posting.
surrealjam said:
Flashing an OTA manually doesn't require unlocking of bootloader or losing data. Follow Section A from here: http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217 - you just need the zipped update and ADB on your PC.
This zip will go from KTU84P to LRX21O (aka 5.0): http://android.clients.google.com/p...ed-hammerhead-LRX21O-from-KTU84P.c1a33561.zip
You could then see if you get prompted to update to 5.0.1. If not, then flash this to go from LRX21O to LRX22C: http://android.clients.google.com/p...ed-hammerhead-LRX22C-from-LRX21O.785a2f7a.zip
It's interesting that you're not being given that option in 4.4.4 though... have Google stopped pushing the Lollipop updates altogether?
Click to expand...
Click to collapse
Thanks, I did what you suggested. Now on official 5.0.1

How to get Rooted, TWRP'd Sprint A9 to Nougat? (Edited)

(From later on in this thread)
Jaxas said:
Hello again, sorry to bother you guys but I'm seeing a surprising amount of conflicting information about this...
So I'm trying to upgrade to Nougat, but I'm having some troubles figuring out what I need to do for that.
I know I need to get my phone back to stock so I can accept the OTA update, but I'm not sure how to go about that.
My phone currently:
- Phone Model: HTC One A9 (Sprint - 2PQ93)
- Android Version: 6.0.1
- Software Version: 1.60.651.4
- Root: Yes
- Recovery: TWRP v2.8.8.2_CPTB-TEST2
- S: ON
- Bootloader: Unlocked
- Software Status: Modified
So as far as I'm aware, I need to restore the Stock recovery (how?), re-flash the RUU for my current software version, and then... relock the bootloader? Maybe?
So my questions are...
- How do I actually restore the stock recovery?
- Are there any steps I'm missing?
- Do I need to re-lock the bootloader, or does that not matter?
(- Is there anything I need to do once I get Nougat to root besides flash TWRP 3.0.3 & SuperSU through that?)
Thanks!
Click to expand...
Click to collapse
=============== ORIGINAL POST ===============
Hello,
I'm basically at my wit's end and I'd just like to see if anyone knows whether it's actually possible to get Android 7.0 Nougat on my phone?
I currently have a rooted, RUU-updated 6.0.1 build of Android (Version Number: 1.60.651.4) running on a Sprint (so CDMA) HTC One A9 (Model Number: 2PQ9300). My phone is still S-On (I'm willing to pay for Sunshine if it'll actually work for me, but I'd like to confirm that first), and due to the updating process I do not currently have TWRP - that's easily fixed, however.
Mostly, I'd just like to know if there's a way to get Android 7.0 on my phone, as it is not the International version, while also retaining things like mobile data and calling.
So far, I've looked into simply flashing the RUU (seems to be both not compatible with my phone version, and also has the signing issue mentioned Here), however with the signing issue I'd have to OTA update first so that's not relevant.
I've looked into Sunshine for S-OFF as well as This thread to convert to the "Unlocked" version that has the update, however I'm seeing comments about it not being compatible with the Sprint edition.
I've most recently tried to follow This guide, however I've had no luck and I'm still seeing talk of random reboots, dropped calls, and the like.
Basically, if there's any way I can get Android 7.0 Nougat on my phone, I would love to know how - if I can't (reasonably), then I'd also like to know that so I can stop beating my head into the wall, so to speak
Thanks!
Jaxas said:
Basically, if there's any way I can get Android 7.0 Nougat on my phone, I would love to know how - if I can't (reasonably), then I'd also like to know that so I can stop beating my head into the wall, so to speak
Thanks!
Click to expand...
Click to collapse
So far, the CDMA versions of the A9 can't run Nougat. As you know, HTC hasn't updated it for Nougat, and our phones run different enough firmware from the GSM-Locked and Dev versions that we can't use theirs. And so far, HTC's Dev Nougat requires Nougat firmware. So... we're boned.
Hopefully this won't be forever; HTC should eventually update American phones, so we'll just have to factory reset from system image (and maybe RUU) and OTA. For now, we can only hope guys like Captain_Throwback figure out how to backport Nougat to the 1.60.651.4 firmware.
Jaxas said:
Hello,
I'm basically at my wit's end and I'd just like to see if anyone knows whether it's actually possible to get Android 7.0 Nougat on my phone?
I currently have a rooted, RUU-updated 6.0.1 build of Android (Version Number: 1.60.651.4) running on a Sprint (so CDMA) HTC One A9 (Model Number: 2PQ9300). My phone is still S-On (I'm willing to pay for Sunshine if it'll actually work for me, but I'd like to confirm that first), and due to the updating process I do not currently have TWRP - that's easily fixed, however.
Mostly, I'd just like to know if there's a way to get Android 7.0 on my phone, as it is not the International version, while also retaining things like mobile data and calling.
So far, I've looked into simply flashing the RUU (seems to be both not compatible with my phone version, and also has the signing issue mentioned Here), however with the signing issue I'd have to OTA update first so that's not relevant.
I've looked into Sunshine for S-OFF as well as This thread to convert to the "Unlocked" version that has the update, however I'm seeing comments about it not being compatible with the Sprint edition.
I've most recently tried to follow This guide, however I've had no luck and I'm still seeing talk of random reboots, dropped calls, and the like.
Basically, if there's any way I can get Android 7.0 Nougat on my phone, I would love to know how - if I can't (reasonably), then I'd also like to know that so I can stop beating my head into the wall, so to speak
Thanks!
Click to expand...
Click to collapse
hey,
can you try this ...
https://forum.xda-developers.com/one-a9/general/htc-one-a9-android-7-nougat-t3546557
New info: Nougat is now available via OTA. Now we just need to... get back to full stock.
Woo! Just saw the notification. So now the question is if TWRP will work with 7.0 on our phones.. I think I'd rather keep root than upgrade and lose it if there's a choice.
JohnRogers23 said:
Woo! Just saw the notification. So now the question is if TWRP will work with 7.0 on our phones.. I think I'd rather keep root than upgrade and lose it if there's a choice.
Click to expand...
Click to collapse
TWRP 3.0.3 beta is available for nougat
MGfusion said:
TWRP 3.0.3 beta is available for nougat
Click to expand...
Click to collapse
I saw, but I'm not sure what's going on in the thread right now. It seems it sometimes bootloops? I'm hesitant to upgrade until there's either an RUU for 2.whatever out or I'm sure TWRP is reliable. I'm resigning myself to living without Xposed, but I at least need root and Magisk.
JohnRogers23 said:
Woo! Just saw the notification. So now the question is if TWRP will work with 7.0 on our phones.. I think I'd rather keep root than upgrade and lose it if there's a choice.
Click to expand...
Click to collapse
Whelp.
I'm upset, lol.
Time to re-reset my phone (finally got it set back up the way I wanted it yesterday on 6.0.1)
Oh well, thanks for the heads up!
I have the Sprint a9. I flashed the ruu and flashed TWRP 3.0.3-1 I believe, with no issues
Okay, so before I go re-wipe my phone and upgrade, I have a few quick questions...
1) Can this update be flashed with S-ON? (I'm assuming so, but always good to check) and
2) Can the Sprint A9 be rooted on Nougat yet?
Thanks!
I used TWRP 3.0.3.-4 and root with Magisk. Still miss Xposed, but the N features are pretty nice too. All seems to be working well.
Hello again, sorry to bother you guys but I'm seeing a surprising amount of conflicting information about this...
So I'm trying to upgrade to Nougat, but I'm having some troubles figuring out what I need to do for that.
I know I need to get my phone back to stock so I can accept the OTA update, but I'm not sure how to go about that.
My phone currently:
- Phone Model: HTC One A9 (Sprint - 2PQ93)
- Android Version: 6.0.1
- Software Version: 1.60.651.4
- Root: Yes
- Recovery: TWRP v2.8.8.2_CPTB-TEST2
- S: ON
- Bootloader: Unlocked
- Software Status: Modified
So as far as I'm aware, I need to restore the Stock recovery (how?), re-flash the RUU for my current software version, and then... relock the bootloader? Maybe?
So my questions are...
- How do I actually restore the stock recovery?
- Are there any steps I'm missing?
- Do I need to re-lock the bootloader, or does that not matter?
(- Is there anything I need to do once I get Nougat to root besides flash TWRP 3.0.3 & SuperSU through that?)
Thanks!
Jaxas said:
So as far as I'm aware, I need to restore the Stock recovery (how?), re-flash the RUU for my current software version, and then... relock the bootloader? Maybe?
So my questions are...
- How do I actually restore the stock recovery?
- Are there any steps I'm missing?
- Do I need to re-lock the bootloader, or does that not matter?
(- Is there anything I need to do once I get Nougat to root besides flash TWRP 3.0.3 & SuperSU through that?)
Thanks!
Click to expand...
Click to collapse
If you don't have an unmodified system image from before you mounted the system partition then yes, you do have to use an RUU, which will also give you stock recovery. No, you don't need to do anything with the bootloader.
Flash the RUU for the version you're on now, start up normally and take the OTA. No, I didn't have to do anything special besides making double checking /system is mounted read-only in TWRP. Personally I like using Magisk for root, etc, but I've heard SuperSU works fine. too. I'm S-on as well and it was all very easy.
I have a modified htc one a9 sprint, i want to get back to fully stock so i can update my device by using RUU side load. Please help
samweli benjamin said:
I have a modified htc one a9 sprint, i want to get back to fully stock so i can update my device by using RUU side load. Please help
Click to expand...
Click to collapse
What is your CID, MID and version-main? Is your bootloader locked or unlocked? S-ON or S-OFF?
I have attached a screenshot of getvar all for my device, when i was attemping to update it by using RUU its status was LOCKED and S-OFF but currently its status is **RE-LOCKED** and S-OFF
samweli benjamin said:
I have attached a screenshot of getvar all for my device, when i was attemping to update it by using RUU its status was LOCKED and S-OFF but currently its status is **RE-LOCKED** and S-OFF
Click to expand...
Click to collapse
What ruu version were you trying to flash and what was the error?
It was RUU_HIA_AERO_WHL_N70_SENSE80GP_SPCS_MR_Sprint_WWE_2.18.651.2 and the ERROR that I received was SIGNARURE ERROR: 132
samweli benjamin said:
It was RUU_HIA_AERO_WHL_N70_SENSE80GP_SPCS_MR_Sprint_WWE_2.18.651.2 and the ERROR that I received was SIGNARURE ERROR: 132
Click to expand...
Click to collapse
You can't flash a nougat ruu (2.xx.xxx.x) on a phone running the marshmallow firmware (1.xx.xxx.x). You need to manually update your firmware to 2.xx.651.x before being able to flash the 2.18.651.2 RUU. This is because the new signature key implemented in all 2.xx.xxx.x ruu, explained here at faq #4
Or you can flash the older 1.60.651.4 ruu and after, update your phone using OTA updates. Probably the easiest way for you :good:
http://dl3.htc.com/application/RUU_HIA_AERO_WHL_M60_SENSE7GP_SPCS_MR_Sprint_WWE_1.60.651.4.exe
This seems to be of great help to me, but am afraid i can't install the OTA in my device, b'se I received it and i did downloaded it but when i click to install it finish unzipping file and then fail and the phone boots in TWRP recovery so i thought i can update it by running a RUU side load

Downgrading my (unrooted) carrier locked At&t Note 8.

My note 8 had OneUI pushed to it about a week ago even though I kept refusing not wanting to while I was sleeping. It says my bootloader is v5. This is actually what it says (N950USQU5DSD3). My problem is that when I search for the firmware I'm wanting to downgrade to (the last oreo update possible for this particular phone) on Sammobile I can't find the one for At&t. I see ones for Verizon, sprint, etc. But nothing for at&t, which one am I supposed to use and where can I get it? This is going to be my very first downgrade/upgrade, really my first time doing anything like it on android. And I CAN do this right? There's nothing I should be aware of that makes what I'm trying to do not able to be done is there? The biggest reason I'm asking is because I have very limited tools to work with, I have a little 12" Acer aspire one (no disk drive) running windows 7 home basic, mobile hotspot from my wife's phone(the last software I tried to download and use came from xda out of a thread I found titled, "Stock Oreo N950USQS5CRF6 Odin*files*for AT&T*NOTE*8" it failed halfway through 2 nights ago during the beginning of storm, and the whole time it would only download around 32kbs so it literally to FOREVER! Only for it to fail halfway through. Was I wasting my time or was this in fact the firmware I'm looking for? If not, as I asked before, where could I find it?? Thanks a bunch for any help.
https://forum.xda-developers.com/at...n950u-stock-n950usqs5crf6-odin-files-t3821222
^^^^^^^Is this all I need? Do I need to follow this tutorial or a different one?? What version of odin, do I need anything else
Sorry for so much all at once, I really hate this update and want Oreo back.
https://forum.xda-developers.com/ga...m-n950u-u1-t3685884/post74087340#post74087340
Follow the steps from the above-linked post, and follow them very carefully. I did, and I was able to successfully downgrade from Pie to Oreo on my AT&T NOTE8.
I actually flashed the unlocked firmware, which has zero AT&T bloat. It works just fine for my needs. I don't think AT&T WiFi calling works on this unlocked firmware (I haven't tried - I don't use it).
Caveat emptor: whichever version of Oreo you choose (either the AT&T stock, or the unlocked firmware), we are stuck on the February 2019 Android security patch.
Only Pie gets the latest security patches. As long as you are ok with this, then proceed with the downgrade to Oreo!
pyrolad said:
Caveat emptor: whichever version of Oreo you choose (either the AT&T stock, or the unlocked firmware), we are stuck on the February 2019 Android security patch.
Only Pie gets the latest security patches. As long as you are ok with this, then proceed with the downgrade to Oreo!
Click to expand...
Click to collapse
A little off topic, but has anyone seen an AT&T security update for May yet? I'm still on April security, and it's basically mid June?
Tha k you I'll check it out when I get off work, I didn't know you could flash the unlocked firmware on a carrier locked phone
Let me get this straight. Can a locked bootloader AT&T SM-N9500U on Android 9, N9500USQU5DSD3 downgrade to Oreo? I thought this bootloader whould not let you go back.
I LOATH Pie and wan to go back to Oreo so bad, please tell me there is a for sure way. This is my first permanently locked bootloader phone and it's killing me not to flash an software I prefer.
I dont know I wish someone could tell me forsure whether it will work or not because now my phone is getting another software update notification so it's getting ready to force another update on me and I doubt after that I will still have bootloader v5. Can someone please verify whether my current bootloader (N9500USQU5DSD3) will downgrade successfully to back to oreo or not? I have the oreo firmware I want to use downloaded and ready to go which is (SM-N950USQU5CRL1). Can I downgrade to this without messing anything up?? Please I need a fast reply I dont want this new update forced to my phone and updating my bootloader to v5 where I can ever go back to oreo.
marhodges said:
Let me get this straight. Can a locked bootloader AT&T SM-N9500U on Android 9, N9500USQU5DSD3 downgrade to Oreo? I thought this bootloader whould not let you go back.
I LOATH Pie and wan to go back to Oreo so bad, please tell me there is a for sure way. This is my first permanently locked bootloader phone and it's killing me not to flash an software I prefer.
Click to expand...
Click to collapse
Yes you CAN downgrade back to Oreo. BUT you MUST go to a bootloader 5 firmware.
---------- Post added at 07:55 AM ---------- Previous post was at 07:54 AM ----------
Superloud024 said:
I dont know I wish someone could tell me forsure whether it will work or not because now my phone is getting another software update notification so it's getting ready to force another update on me and I doubt after that I will still have bootloader v5. Can someone please verify whether my current bootloader (N9500USQU5DSD3) will downgrade successfully to back to oreo or not? I have the oreo firmware I want to use downloaded and ready to go which is (SM-N950USQU5CRL1). Can I downgrade to this without messing anything up?? Please I need a fast reply I dont want this new update forced to my phone and updating my bootloader to v5 where I can ever go back to oreo.
Click to expand...
Click to collapse
Yes you can go to that firmware. You will want to back up and allow it to factory reset. Be sure to use the modified version of Odin. Go HERE, post #2

Categories

Resources