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

(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

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 it Safe to Take 4.4.3 OTA Update on Stock?

Hi, i'm kinda new to Rooting HTC Devices, but not to rooting android devices in general. I was wondering if it was safe to take the OTA Update to get the Latest Firmware / Radios Etc, and then Install Viper One 2.5.0. I haven't touched the Firmware at all and i heard from Team Venom that you had to update your firmware and so far i haven't found any RUU's that work properly and whenever i try to flash Viper One 2.4.0, i get VERY long boot screens and sometimes it hangs on the HTC Logo, like the post suggested. Is there any way of safely doing this to a Verizon Phone without loosing S-OFF, Root or an Unlocked Bootloader? Considering they said:
Notice: at the time of writing, both T-Mobile US and Verizon’s 4.4.3 Updates were not available yet, but announced.
Click to expand...
Click to collapse
which i think its not true since people are already running 4.4.3 and Viper One Running on the latest Firmware, and they also said
While the Verizon and T-Mobile US guys need to wait (with “method #1″), the TmoUS folks could head over to my thread (linked above) and set their phones to S-OFF and flash an international firmware as a shortcut (it should be ok, not sure on the impact, maybe losing some WiFi calling functionality which can be restored by flashing TmoUS Firmware once it becomes available), going by “method #2″. However, Verizon: do NOT flash an international GSM firmware! You would regret it badly! Same goes for Sprint by the way. No INT firmware for you ever!
Click to expand...
Click to collapse
Yet on the Verizon Post on Xda, they point you directly to it like i'm supposed to do that, and when i try "Method 2" which is also on their Website's Post that Links you to their Special Firmware Thread here , They Say:
I will cover GSM PHONES ONLY - no cdma / sprint firmware except when i wish to do otherwise.
Click to expand...
Click to collapse
which makes no sense considering they basically told me to go there from linking me in their Verizon Thread. I mean i'm totally confused how your supposed to flash the newest Firmware and it doesn't help that NO ONE has a tutorial online for this. I'm sorry if i'm coming off as a noob, but Normally Verizon OTA Updates have a tendency to Break Root and Lock the Bootloader and i don't know if this is any different.
My Device:
Verizon HTC One M8 (M8_WLV)
4.4.2, 1.55.605.2 Stock Sense
Rooted, S-OFF, Bootloader Unlocked
It's really easy to apply the radio and firmware. Just follow the instructions here
http://forum.xda-developers.com/showthread.php?t=2824882
Also you are correct that taking the ota directly will cause you to lose root. Once you have applied the firmware you should be good with the ROM

Not able to update Verizon HTC ONE M8 to Android 4.4.3

Hello!
I have a Verizon HTC ONE M8 that no matter what it won't download the new update. I've bought 3 of them (identical) 1 month ago from Ebay. One of them was able to receive the update. On the other two i keep receiving the following message: "We were not able to download this update. To retry, go to Settings > Software update. "
My device is S-off (after a lot of effort). I've tried to get rid of all the bloatware and many more by flashing a new ROM. I have tried flashing ViperROM, ARHD, Clean ROM using TWRP Recovery, without any success. All of my attempts got stuck at the booting screen for more than 30 minutes without any success of booting into the OS. Clean ROM even refused to flash properly. Keep in mind that all the ROMs that I've flashed were based on 4.4.2 firmware, the one that my phone came with, not 4.4.3. I've searched on this forum for a flashable 4.4.3 OTA update, but no success either. What's to be done !?!? All my attempts of installing a new OS failed. Please HELP!
P.S: I'm a newbie when it comes to all of this stuff. First time doing S-off/ installing custom ROMs.
hgpt said:
Hello!
I have a Verizon HTC ONE M8 that no matter what it won't download the new update. I've bought 3 of them (identical) 1 month ago from Ebay. One of them was able to receive the update. On the other two i keep receiving the following message: "We were not able to download this update. To retry, go to Settings > Software update. "
My device is S-off (after a lot of effort). I've tried to get rid of all the bloatware and many more by flashing a new ROM. I have tried flashing ViperROM, ARHD, Clean ROM using TWRP Recovery, without any success. All of my attempts got stuck at the booting screen for more than 30 minutes without any success of booting into the OS. Clean ROM even refused to flash properly. Keep in mind that all the ROMs that I've flashed were based on 4.4.2 firmware, the one that my phone came with, not 4.4.3. I've searched on this forum for a flashable 4.4.3 OTA update, but no success either. What's to be done !?!? All my attempts of installing a new OS failed. Please HELP!
P.S: I'm a newbie when it comes to all of this stuff. First time doing S-off/ installing custom ROMs.
Click to expand...
Click to collapse
You probably won't be able to take the OTA with a custom recovery, it has to be stock. Best bet is to flash the 4.4.3 firmware from the development section since you're s-off, then flash an already rooted stock 4.4.3 rom. It's been a while since I've done this stuff so if I mentioned some incorrect info, my apologies.
dynofrk666 said:
You probably won't be able to take the OTA with a custom recovery, it has to be stock. Best bet is to flash the 4.4.3 firmware from the development section since you're s-off, then flash an already rooted stock 4.4.3 rom. It's been a while since I've done this stuff so if I mentioned some incorrect info, my apologies.
Click to expand...
Click to collapse
I flashed back again the stock ROM and i keep receiving the same message over and over again. No TWRP recovery this time, just the red triangle. I guess my best bet is to try and flash the CleanROM ODEX 4.4.3 as mentinoned here: @branmuffin17
I'll come back with the results.
hgpt said:
I flashed back again the stock ROM and i keep receiving the same message over and over again. No TWRP recovery this time, just the red triangle. I guess my best bet is to try and flash the CleanROM ODEX 4.4.3 as mentinoned here: @branmuffin17
I'll come back with the results.
Click to expand...
Click to collapse
If you are on the old firmware you need to update firmware separately.
And btw, if you freeze just one system app that can cause a Vzw ota to fail.
Question.....Is the phone active on your account? I also had one in the drawer and got the same error till I switched it to the active device on my account.
It honestly sounds like there is something preventing the ota to even download, if that's the case use dottat's ruu to return to a clean slate, if it still won't download the OTA then I would be willing to bet money that they are defective or not genuine Verizon M8s And if I were to guess it's more of the latter that would be the only valid reason every Rom you've tried fails no matter what.
sent from space
runandhide05 said:
It honestly sounds like there is something preventing the ota to even download, if that's the case use dottat's ruu to return to a clean slate, if it still won't download the OTA then I would be willing to bet money that they are defective or not genuine Verizon M8s And if I were to guess it's more of the latter that would be the only valid reason every Rom you've tried fails no matter what.
sent from space
Click to expand...
Click to collapse
Based on what you said i went on some websites to check the IMEI/ESN of the device it seems to be OK. After that i went to the Verizon Wireless website to try an activate my phone and when it comes to "Enter your Device ID to check eligibility", I type in the IMEI and the following message apears: "The phone associated with the Device ID you entered is not compatible with the Verizon Wireless network." To me is strange because on the back of the phone it says Verizon 4G LTE. When it comes to the identity of the phone it is a HTC6525LVW. The phone is GSM Unlocked (I use my phone in Europe so i needed it to be GSM unlocked). More strange it is to me that i don't receive the same message when i type in the IMEI of the others Verizon GSM unlocked HTC's ONE M8 that i bought along with this one.
I guess my only chance is to flash the new firmware @here[and after that flash the Deoxed 4.4.3 Stock Clean ROM @here. If it's not going to work i really don't know what's else it's to be done.
hgpt said:
Based on what you said i went on some websites to check the IMEI/ESN of the device it seems to be OK. After that i went to the Verizon Wireless website to try an activate my phone and when it comes to "Enter your Device ID to check eligibility", I type in the IMEI and the following message apears: "The phone associated with the Device ID you entered is not compatible with the Verizon Wireless network." To me is strange because on the back of the phone it says Verizon 4G LTE. When it comes to the identity of the phone it is a HTC6525LVW. The phone is GSM Unlocked (I use my phone in Europe so i needed it to be GSM unlocked). More strange it is to me that i don't receive the same message when i type in the IMEI of the others Verizon GSM unlocked HTC's ONE M8 that i bought along with this one.
I guess my only chance is to flash the new firmware @here[and after that flash the Deoxed 4.4.3 Stock Clean ROM @here. If it's not going to work i really don't know what's else it's to be done.
Click to expand...
Click to collapse
The message from the vzw site tells me something is not right.
Google goophone or knock off gs4, the goophone also has an m8 now too... Even with all the branding and everything. And I've seen some gs4s that run what appears to be TouchWiz cloned to a T.
I'd try calling vzw and talk to a rep and it's possible that they could give you more info other than just what the site said.
sent from space
So I did what I've said:
1. Installed firmware provided here @Tigerstown
2. Installed the Odex Stock Rooted ROM proivede here: @scrosler
I am pleased to announce you that everything is fully functional now
Phone is showing:
Android Version: 4.4.3
Software number: CleanROM 2.0.0 (after flashing it from @here)
Baseband version: 1.09.20.0702
Bulid number: 2.21.605.2 CL362279 release-keys
After managing to flash the 4.4.3 version of Android all went up without any problem. Tried to ARHD but it's still not booting. After that installed ViperROM which went up all, but to me it is not the pure HTC Sense 6 experience i was looking about and all that customization is to much for me, so i flashed CleanROM 2.0.0 and here I am. Everything is as it should be: no bloatware, pure HTC Sense 6, optimized performance... and above all the mobile hotspot is now fully functional, not to mention the EXT SAVER.
As a conclusion, to all that guys that are not able to update to the 4.4.3 version via the OTA updates provided by Verizon do what I did above (steps 1 and 2).
ATTENTION: Your device needs to be S-Off and bootloader unlocked + custom recovery!!!
Another thing worth to be mentioned: it would be great if the admins could flag this thread, cause I've seen so many users on different forums that are not able to update via the OTAs.
In the end i would like to thank to all the devs out there for their work and to the users for their support. Cheers!:highfive:

New Update - QH2

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.

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