Related
(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
According to the Verizon Galaxy S5 Update Page:
Android® Security Patch Level: 2017–08-01
August 2017 Android security patches.
Fixed an issue where device was unable to connect and pair with some Bluetooth® Low Energy (BLE) devices.
Click to expand...
Click to collapse
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQH2_G900VVZW2DQH2_G900VVRU2DQH2_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQH2_G900VVZW2DQH2_G900VVRU2DQH2_HOME_No_Aboot.tar.md5.zip
This update prevent downgrading for older builds?
enmanuel255 said:
This update prevent downgrading for older builds?
Click to expand...
Click to collapse
I doubt it since the only time that really happens is when the number in the bootloader is increased.
For example, the first time the VZW S5 was updated to prevent downgrading was when the firmware version went from G900VVRU1BOD5 to G900VVRU2BOE1.
The VRU1 and VRU2 are the bootloader versions. Once updated to VRU2/VRS2, you can't go back to VRU1. For some reason they keep changing back and forth from VRU2 to VRS2 at random times. The past few updates have either been VRU2 or VRS2 but you can still go all the way back to the first firmware with VRU2.
TLDR; Since this firmware is using the VRU2 bootloader, it is very unlikely that it will prevent downgrading.
On a side note, this is the longest that it has taken for the complete Odin firmware to be uploaded to Samsung's servers. The update was out the 13th. Normally it takes 3 days for it to be available on their servers and it still isn't. I even tried using the Verizon Software Upgrade Assistant and both of my S5's say they are up to date on QF2.
It's rolled out:
Checking firmware for SM-G900V/VZW/G900VVRU2DQF2/G900VVZW2DQF2/G900VVRU2DQF2/G900VVRU2DQF2
Model: SM-G900V
Version: G900VVRU2DQH2/G900VVZW2DQH2/G900VVRU2DQH2/G900VVRU2DQH2
OS: Marshmallow(Android 6.0.1)
Filename: SM-G900V_1_20170824083446_06zw9gofua_fac.zip.enc4
Size: 2292181872 bytes
LogicValue: 0zmklm1qb9k6sfxe
Click to expand...
Click to collapse
P.S. I would not hurry with this upgrade. As for now I experience sound stuttering in my Samsung Level Active earbuds.
Trying to found out the cause but it definitely happened after bootloader/kernel/modems upgrade to DQH2.
bbsc said:
It's rolled out:
P.S. I would not hurry with this upgrade. As for now I experience sound stuttering in my Samsung Level Active earbuds.
Trying to found out the cause but it definitely happened after bootloader/kernel/modems upgrade to DQH2.
Click to expand...
Click to collapse
Yep I literally just saw that it was. I checked at 12:30am EST and it wasn't.
It's odd that you'd be having problems with bluetooth headphones since this update is supposed to fix bluetooth problems, other than the security related bluetooth problems.
Dudash said:
It's odd that you'd be having problems with bluetooth headphones since this update is supposed to fix bluetooth problems
Click to expand...
Click to collapse
See below.
Lost Hotspot Functionality
Once I flashed this update I lost the ability to bypass Verizon's check to use the hotspot functionality. Now it keeps checking my account and wanting me to pay for the service. Is there anyway I can get around this again, as I was able to with basic root?
I did flash the Developer Bootloader Friendly version using FlashFire.
In addition to my previous post.
Ok, I've been experimenting for a few days with two units of SM-G900V and two pairs of Samsung Level Active wireless earbuds.
I was walking in the same places and listening the same music in the same conditions with different earbuds and different phones, having different (DQF2 and DQH2) firmware (kernel, modem, recovery). In all cases the phones were loaded with the same /system ROM - stock-near ALEXNDR.G900FXXS1CQH1
My conclusion is: DQH2 keeps bluetooth connection much worse than DQF2.
I cannot say that we have a crystal-clear sound in one case and a crappy stuttering in the other.
But the difference is noticeable and obvious.
That's why I personally am reverting back to DQF2 firmware.
wbr.
Updated to this build from QA1, flashed in odin, then booted up, reflashed TWRP and SU, froze system updater all good. No problems here with BT streaming music 2hrs a day in my car for 3 days.
After Flashear everything is fine except autorotation, it does not work for me
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQH2_G900VVZW2DQH2_G900VVRU2DQH2_HOME.tar.md5.zip
Is there a full stock non rooted retail download available? I would like to revert completely to stock.
MrTrumpz said:
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQH2_G900VVZW2DQH2_G900VVRU2DQH2_HOME.tar.md5.zip
Is there a full stock retail download available? I would like to revert completely to stock.
Click to expand...
Click to collapse
That will return you to stock, it just won't delete all of your data.
If you want stock firmware that will completely wipe your device, you can go to my thread here.
Keep in mind that if you are on a firmware that has VRU2 or VRS2 in the name, you cannot downgrade to a firmware that has VRU1 in the name.
Dudash said:
That will return you to stock, it just won't delete all of your data.
If you want stock firmware that will completely wipe your device, you can go to my thread here.
Keep in mind that if you are on a firmware that has VRU2 or VRS2 in the name, you cannot downgrade to a firmware that has VRU1 in the name.
Click to expand...
Click to collapse
Thanks so much. I appreciate the response.
If i unlocked my bootloader on PB1 firmware, will I have issues flashing this firmware? For some reason I've always thought updating my firmware without updating the bootloader like I originally had to would cause some serious problems. Or did I misinterpret the necessity of updating the bootloader to match the firmware? Is that even an actual problem if they don't match?
Maphack said:
Is that even an actual problem if they don't match?
Click to expand...
Click to collapse
Nobody knows the exact answer except Samsung itself.
In most cases it works.
But this bootloader can be unlocked in the same way as the others if you have CID15.
bbsc said:
Nobody knows the exact answer except Samsung itself.
In most cases it works.
But this bootloader can be unlocked in the same way as the others if you have CID15.
Click to expand...
Click to collapse
Sorry, I was unclear. I unlocked my bootloader and chose PB1 as the firmware to be... Unlocked on, I guess? Not sure the proper phrasing for it.
So I have an unlocked bootloader, but am afraid of updating my firmware in case that messes up something.
If you already answered my question and my response to your question is just due to my lack of knowledge, I apologize.
@Maphack
Ok, let's clarify the things a little.
1. Locked bootloader is called "locked" because it doesn't boot custom unsigned kernels, i.e. rooted 6.0.1 kernels, TWRP kernels, kernels from kernel modders, etc.
2. Virtually all bootloaders in SM-G900V are locked by default.
3. Some of them can be unlocked if the phone has CID15.
4. People unlock bootloaders to install a custom recovery, to have root on 6.0.1, etc.
5. BPB1 is Android 5.0 and it does not require unlocked bootloader for to be rooted because root on 5.0 does not require kernel modification. So you may not know if it's locked or unlocked if you're on BPB1 currently.
But you can see it in download mode.
So if you want to update to QH2 or another 6.0.1 ROM, you need first:
1. Decide if you need root on 6.0.1.
2. Check the CID of your phone with EMMC Brickbug Check app from Market.
P.S. Probably I misunderstood you and your current firmware is not BPB1 but some 6.0.1 firmware and you are talking about BPB1 as about that firmware you've used to unlock bootloader on.
That's another story.
You can find directions how to update unlocked bootloader here.
bbsc said:
@Maphack
Ok, let's clarify the things a little.
1. Locked bootloader is called "locked" because it doesn't boot custom unsigned kernels, i.e. rooted 6.0.1 kernels, TWRP kernels, kernels from kernel modders, etc.
2. Virtually all bootloaders in SM-G900V are locked by default.
3. Some of them can be unlocked if the phone has CID15.
4. People unlock bootloaders to install a custom recovery, to have root on 6.0.1, etc.
5. BPB1 is Android 5.0 and it does not require unlocked bootloader for to be rooted because root on 5.0 does not require kernel modification. So you may not know if it's locked or unlocked if you're on BPB1 currently.
But you can see it in download mode.
So if you want to update to QH2 or another 6.0.1 ROM, you need first:
1. Decide if you need root on 6.0.1.
2. Check the CID of your phone with EMMC Brickbug Check app from Market.
P.S. Probably I misunderstood you and your current firmware is not BPB1 but some 6.0.1 firmware and you are talking about BPB1 as about that firmware you've used to unlock bootloader on.
That's another story.
You can find directions how to update unlocked bootloader here.
Click to expand...
Click to collapse
Thanks. Yeah, I'm already on an unlocked bootloader running 7.1.4. I'll look into updating an unlocked bootloader. I appreciate the help.
Or is there even a point for me to tweak my phone at this point?
Maphack said:
Or is there even a point for me to tweak my phone at this point?
Click to expand...
Click to collapse
None.
Modem upgrade, maybe...
But if you're satisfied, don't repair a working thing.
Help
Dudash said:
According to the Verizon Galaxy S5 Update Page:
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQH2_G900VVZW2DQH2_G900VVRU2DQH2_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQH2_G900VVZW2DQH2_G900VVRU2DQH2_HOME_No_Aboot.tar.md5.zip
Click to expand...
Click to collapse
Currently this is my System info.
Model - SM G900V
Baseband - G900VVRU2DPD1
Kernel - 3.4.0 [email protected] #1
Build Number - MMB29M.G900VVRU2DPF4
I flashed NI2 using Odin and have Safestrap. I have been away from this phone for long so lost touch of the updates. I have not flashed the Dev bootloader or unlocked it as far as I remember because when I installed this rom, there was no method to unlock bootloader. Can I still flash the QH2 update on this in Safestrap, the Developer Friendly version or the official.
Still says 2017-08-01 security patch, but now with Blueborne and Krack patched as well.
https://www.verizonwireless.com/support/galaxy-s5-update/
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQL1_G900VVZW2DQL1_G900VVRU2DQL1_HOME.tar .md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQL1_G900VVZW2DQL1_G900VVRU2DQL1_HOME_No_ Aboot.tar.md5.zip
I also received the software update notification. Now hoping someone will be able to make the bootloader friendly/no aboot version to flash...
stormified said:
I also received the software update notification. Now hoping someone will be able to make the bootloader friendly/no aboot version to flash...
Click to expand...
Click to collapse
Been a while since I've been to this section of the forums but I'm already uploading a Dev Friendly version and the untouched one right now.
EDIT:
@Silent Patriot
Feel free to add this to the OP.
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQL1_G900VVZW2DQL1_G900VVRU2DQL1_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQL1_G900VVZW2DQL1_G900VVRU2DQL1_HOME_No_Aboot.tar.md5.zip
Dudash said:
Been a while since I've been to this section of the forums but I'm already uploading a Dev Friendly version and the untouched one right now.
EDIT:
@Silent Patriot
Feel free to add this to the OP.
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQL1_G900VVZW2DQL1_G900VVRU2DQL1_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQL1_G900VVZW2DQL1_G900VVRU2DQL1_HOME_No_Aboot.tar.md5.zip
Click to expand...
Click to collapse
Hi, I am running the Resurrection Remix Final N ROM on my g900v and I have this bootloader (g900vvrs2dqb2). I looked it up and saw that it was from February 2017.
I would like to update my modem and boot so I am ready for Oreo but I'm not sure best way to go about it,(Odin)?
I know this information is available on XDA and probably in this forum, but I am paranoid because I had a hell of a time unlocking the bootloader because I was fallowing old directions.
I would be very grateful to anyone willing to point me towards simple, but accurate directions.
Thanks in advance, and apologize for my ignorance!
Sent from my kltevzw using XDA Labs
Awesome! Thanks very much. I'm gonna give this a shot like the previous install/upgrade some time Friday afternoon PDT.
Jeebus I need sleep....
Can I flash this over LOS in TWRP to return to stock or do I have to use Odin?
Once flashed will the bootloader remain unlocked to allow me to reinstall LOS?
I got a new screen installed and it appears there may be an issue with how the digitizer interfaces with the software/kernal and going back to stock should update the software to allow the screen to function normally then allowing me to reflash LOS.
Hey Everyone,
Thanks for all your great work on the Galaxy S5. This thing is still kicking! I know I'm way behind on what's been going on. I'm still back on the TowelRoot days. The time has come to finally update my phone because some of the apps won't work anymore. I'm not into ROMs and stuff, I just want the latest firmware without all the bloatware. I had originally gone the TowelRoot method because people were having such a hard time with battery life (me included) with Lollipop. I was fortunate enough to get TowelRoot before updating to the newer version of Lollipop and went back to KitKat and I've been there ever since.
I'm currently on G900VVZW1ANCG (Kitkat 4.4.2) with root access and superuser. I have a CID 15 emmc which is a good thing from all the research I've been doing on XDA.
That's where I get stuck and confused with the newer stuff that's going on. Do I even need to unlock the bootloader?
In the end, I don't mind wiping the entire phone, I just want to get to the latest Marshmallow (which this thread seems to have) without all the bloatware or the ability to delete all the bloatware.
nickbike1 said:
Hey Everyone, Thanks for all your great work on the Galaxy S5. This thing is still kicking! I know I'm way behind on what's been going on. I'm still back on the TowelRoot days...
Click to expand...
Click to collapse
Welcome back!
You had asked some questions that is actually 2 separate ones upon themselves and I'll, hopefully, try to answer them...
Question 1: Should you unlock the bootloader?
Answer 1: The only need for anyone to require this is if they want to perform something outside the scope of just Rooting a device.
What I mean is... for example, if an individual would like to install a Custom Recovery and/or Firmware then you will need to unlock the bootloader.
Question 2: You would, ultimately, like to just debloat the Firmware?
Answer 2: Debloating Stock Firmware only requires root and not an unlocked bootloader.
The proper rooting of a device just means that you will be able to modify areas of the root directory that's restricted for devices without root and Debloating falls into this category.
Just an FYI regarding the following 2:
1) The 2 differences between the CID11 & CID15...
GS5 with CID11 = Toshiba EMMC
GS5 with CID15 = Samsung EMMC
2) There are a handful of Custom Firmwares that are based upon the stock Firmware that is already Debloated. Some of them only requires a Rooted device and Some requires an unlocked bootloader and recommends a Custom Recovery like TWRP.
This is just a brief summary to help you further but, I would recommend that you take note of/highlight the following 2threads that would be a bit more helpful depending on what your looking to do.
https://forum.xda-developers.com/showthread.php?t=2700073
https://forum.xda-developers.com/showthread.php?t=3561529
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
From this post here, I think the way to get this done for an unlocked bootloader is:
- flash the HOME_No version using Odin 3.12 AP option
- flash TWRP via Odin AP
- reinstall Magisk from TWRP and Magisk Manager.
1) Will that work?
2) What’s the most reliable tool for creating a backup—a) in case I screw up, AND b) in case everything goes well, so I can restore my apps and data into the new clean phone, preferably without screwing up the new clean phone?
I have a G900V.05 on QB2, rooted and unlocked bootloader and custom recovery, that I got to using this method by jrkruse and a false start via another method. So I’ve got Titanium Backup, TWRP, and FlashFire all in play. I'll probably shoot out backups from all of them, not sure which one restores best or if FlashFire survives the update.
Full System Backup method needed!
BigBird9906 said:
From this post here, I think the way to get this done for an unlocked bootloader is:
- flash the HOME_No version using Odin 3.12 AP option
- flash TWRP via Odin AP
- reinstall Magisk from TWRP and Magisk Manager.
1) Will that work?
2) What’s the most reliable tool for creating a backup—a) in case I screw up, AND b) in case everything goes well, so I can restore my apps and data into the new clean phone, preferably without screwing up the new clean phone?
I have a G900V.05 on QB2, rooted and unlocked bootloader and custom recovery, that I got to using this method by jrkruse and a false start via another method. So I’ve got Titanium Backup, TWRP, and FlashFire all in play. I'll probably shoot out backups from all of them, not sure which one restores best or if FlashFire survives the update.
Click to expand...
Click to collapse
1) -Yes, I just tried it, and it works perfectly! The only correction - you have to unzip
G900VVRU2DQL1_G900VVZW2DQL1_G900VVRU2DQL1_HOME_No_Aboot.tar.md5.zip file and flash md5 file with Odin (Odin won't work with that zip file).
2) -I have exactly the same question to fellow members - what is the current most simple and reliable method of full system backup (like ghost image for PC)? I want to try Lineage, but I already spent many hours on system customization (applications, app settings, accounts with login names/passwords, etc.). I really need some fast method to revert phone back to QL1 with all my current setup. I will flash again System and TWRP from Odin, and Magisk from TWRP. How can I then restore my full setup with one click? I used to use 'Titanium Backup' in the past, but that is not an option anymore. It freezes every time when I try to restore 'All apps with system data'
Thank you for reading that and for any possible advices.
So, if I have an unlocked bootloader, will it stay unlocked if I flash the boot from the "Developer Bootloader Friendly/No Aboot No-Wipe Firmware" version? Will it upgrade the baseband to the latest version as well?
Nerva said:
So, if I have an unlocked bootloader, will it stay unlocked if I flash the boot from the "Developer Bootloader Friendly/No Aboot No-Wipe Firmware" version? Will it upgrade the baseband to the latest version as well?
Click to expand...
Click to collapse
If your looking for the Baseband Modem Firmware, the following link has them all for the G900V and won't affect what you have (i use them on my Unlocked G900V to update the Modem Baseband Firmware and I've got TWRP and LineageOS).
[BASEBAND-FIRMWARE-MODEMS]Verizon Samsung Galaxy S5 {SM-G900V/KLTEVZW}[ODIN] by Ibuprophen
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Thanks. Are the baseband modem firmware also included in the QL1 "Developer Bootloader Friendly/No Aboot No-Wipe Firmware"? I've been told I should upgrade both my modem and bootloader, but I don't want to re-lock my unlocked bootloader.
WTF?? I was running TWRP 3.2.1.0 and crDroid 7.1.2, and I used Odin to flash the "Developer Bootloader Friendly/No Aboot No-Wipe Firmware" and checked the BL and CP options, which I thought should update just the bootloader and modem, and now it boots up with the Samsung logo and then the Verizon logo, and then just sits there. I tried to go to recovery so I could restore a backup, but it looks like the stock recovery. What did I do wrong and how do I fix it??
Since crDroid 7.1.2 is older than the bootloader, I'm wondering if that's the issue. I do have crDroid 8.1 on the microSD card. I also have TWRP 3.2.1.0 on the microSD card. So I'm wondering if I can use the stock recovery to flash TWRP. I haven't played around with custom ROM's in four years, but prior to that I did it all the time, so apparently I now remember just enough to be dangerous...
@Nerva, I apologize for the delay but, I'm curious to know where, why and what gave you the impression that you were/was required, on your your working device, to update your devices bootloader???
I'm just perplexed about this...
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
I went back and tried to find where I read it, and at the very least it was in this post:
godofsalt said:
Yep all true. .... But....
Once he sends you the info (model numbers and such) might want to also double check that he is on the latest firmware, for his devise. Important!
All reads good. If it's rather, "New" then, I would keep it as well.
Click to expand...
Click to collapse
I think I saw it someplace else as well, but I haven't stumbled across it -- I was posting a lot of questions in a lot of threads as well as PMing people.
Nerva said:
I went back and tried to find where I read it, and at the very least it was in this...
Click to expand...
Click to collapse
Your situation prompted me to confirm what I knew and others that you can see on the recent posts on the following thread...
https://forum.xda-developers.com/showthread.php?t=2259645
... I just wanted to state that if your devices bootloader was already unlocked and the device wasn't bricked (or similar) then you should not need to update the bootloader or it'll lock it up again and, potentially, can even cause FRP issues as well. Luckily your FRP didn't trip and the device was able to be unlocked again.
I have the same device that was unlocked a long time ago and never ever needed its bootloader updated.
Your question regarding the Baseband Modem Updates...
Those are the Modem files extracted from the stock Firmware and only updates the devices Modem. That controls the WiFi, Carrier Data, etc...
This is similar to updating the Drivers for something specific on a PC (like the PC LAN, WiFi, Video Card, etc... ).
When you had flashed what you did on your device, you basically flashed an optimized version of the Stock Firmware. This is why you saw the Samsung Boot Screen.
I hope that I had explained this okay via text...
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
I'm curious, if the bootloader version has so little importance for us custom-ROM users, why does Samsung/Verizon update their bootloader versions -- to what purpose?
It looks like this website will generate a cf-auto-root package for QL1:
https://desktop.firmware.mobi/device:840/firmware:14884
I'm wondering if I flash that with Odin, would it upgrade my current unlocked QB2 to an unlocked QL1?
Nerva said:
I'm curious, if the bootloader version has so little importance for us custom-ROM users, why does Samsung/Verizon update their bootloader versions -- to what purpose?...
Click to expand...
Click to collapse
I'm not stating that Bootloaders doesn't get updated upon themselves but, they specifically seldom require it.
One way to look at it is that the function of the bootloader is allot like the BIOS of a PC. They both handle the boot process and seldomly require to be updated specifically.
When a new Stock Firmware version is released, the bootloader is only updated accordingly to reflect the updates of the firmware. This reflection is to protect the device from being updated to an incompatible firmware version.
In short, when the bootloader is unlocked, the bootloader still protects the device from an incompatible firmware from being installed but, it being unlocked just bypasses the "Samsung Stock firmware only" restriction.
TWRP is just the conduit between the Firmware and the bootloader that just handles the communication between the bootloader and the Firmware.
.
I'm wondering if I flash that with Odin, would it upgrade my current unlocked QB2 to an unlocked QL1?
Click to expand...
Click to collapse
If you flash the firmware, your just going to relock your bootloader and be back to stock.
To get the QL1, just flash the Baseband Modem Update from the following link and you'll be good to go and you'll see this in your device info.
[BASEBAND-FIRMWARE-MODEMS]Verizon Samsung Galaxy S5 {SM-G900V/KLTEVZW}[ODIN] by Ibuprophen
Have I clarified this okay?
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
What I want to do: I was trying to OTA update my phone software to the latest, but it seems I am behind on many updates. On the AT&T website, I saw that I need the previous updates installed first, in order to get the latest ones. I have to go in order.
Problem: Every-time I try to do a software update from the settings, it says “Current software is up to date.” It’s been saying that for over a year now. I can’t even get the updates from last year.
So is there a way I can flash one of the stock firmware updates from last year on to my phone with Odin and see if it will fix the ‘over the air’ updates? Or can I just skip to the most recent firmware and flash that one.
By the way, I have never done anything like this to my phone before, so I am a bit nervous, but I want to get this problem fixed so I would love if someone helped me out. I did see some articles online about flashing stock firmware, that’s how I learned about Odin.
If this is doable, can someone please link me to a thorough tutorial on this process? If it isn’t, can you guys recommend another way of getting to the latest 8.0 stock firmware?
My phone:
Galaxy S8 plus (AT&T)
Model#: SM-G955U
Android version: 7.0
Baseband version: G955USQS1AQF7
Android security patch level: June 1, 2017
Kernel version: 4.4.16-11449429
My phone isn't unlocked.
Zendrop said:
What I want to do: I was trying to OTA update my phone software to the latest, but it seems I am behind on many updates. On the AT&T website, I saw that I need the previous updates installed first, in order to get the latest ones. I have to go in order.
Problem: Every-time I try to do a software update from the settings, it says “Current software is up to date.” It’s been saying that for over a year now. I can’t even get the updates from last year.
So is there a way I can flash one of the stock firmware updates from last year on to my phone with Odin and see if it will fix the ‘over the air’ updates? Or can I just skip to the most recent firmware and flash that one.
By the way, I have never done anything like this to my phone before, so I am a bit nervous, but I want to get this problem fixed so I would love if someone helped me out. I did see some articles online about flashing stock firmware, that’s how I learned about Odin.
If this is doable, can someone please link me to a thorough tutorial on this process? If it isn’t, can you guys recommend another way of getting to the latest 8.0 stock firmware?
My phone:
Galaxy S8 plus (AT&T)
Model#: SM-G955U
Android version: 7.0
Baseband version: G955USQS1AQF7
Android security patch level: June 1, 2017
Kernel version: 4.4.16-11449429
My phone isn't unlocked.
Click to expand...
Click to collapse
You can Odin flash CRG3 and the next OTA should be CRHI, so once you go thru settings, check for updates it should want to go to CRHI. And then you should be in the Update path to receive OTA's automatically
Josephigloe said:
You can Odin flash CRG3 and the next OTA should be CRHI, so once you go thru settings, check for updates it should want to go to CRHI. And then you should be in the Update path to receive OTA's automatically
Click to expand...
Click to collapse
Thanks, so is it okay to flash it with the latest version of Odin? Also, do you mind linking me with an up to date / reliable tutorial on this? This is my first time attempting to do something like this.
One more thing, on Sammobile, there is only one firmware available for at&t, and it's the oldest one.
https://www.sammobile.com/firmwares/galaxy-s8-plus/SM-G955U/ATT/
Zendrop said:
Thanks, so is it okay to flash it with the latest version of Odin? Also, do you mind linking me with an up to date / reliable tutorial on this? This is my first time attempting to do something like this.
Click to expand...
Click to collapse
https://drive.google.com/folderview?id=1okPBAupxRljTcSPI70ZVv7KqrccKNqwU
This is a patched odin.
Odin instructions.
https://www.xda-developers.com/update-firmware-any-samsung-phone/
Josephigloe said:
https://drive.google.com/folderview?id=1okPBAupxRljTcSPI70ZVv7KqrccKNqwU
This is a patched odin.
Odin instructions.
https://www.xda-developers.com/update-firmware-any-samsung-phone/
Click to expand...
Click to collapse
Okay, and is it okay if I flash from a firmware from May 2018? It's about 4 months old. Would I be able to OTA update from there on? Also, what is AT&T userdata? I came across it in this thread and I was wondering. https://forum.xda-developers.com/att-galaxy-s8+/how-to/g955u-att-stock-odin-files-firmware-t3769140
Zendrop said:
Okay, and is it okay if I flash from a firmware from May 2018? It's about 4 months old. Would I be able to OTA update from there on? Also, what is AT&T userdata? I came across it in this thread and I was wondering. https://forum.xda-developers.com/att-galaxy-s8+/how-to/g955u-att-stock-odin-files-firmware-t3769140
Click to expand...
Click to collapse
Yes you can use this firmware and start to receive updates, User data I'm not 100% sure but I think its supposed to flash your data so you wont have to reinstall everything but I heard it dosent work for At&t it will still do a complete wipe before install.
Josephigloe said:
Yes you can use this firmware and start to receive updates, User data I'm not 100% sure but I think its supposed to flash your data so you wont have to reinstall everything but I heard it dosent work for At&t it will still do a complete wipe before install.
Click to expand...
Click to collapse
I flashed it and it works great so far. Thanks for all the help! The OTA update also seems to be working!
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