I'm running stock RUU on Verizon's latest 1.55.605.2. All radios, etc are current. I'm rooted with s-off. Now my question is am I able to flash a rom like a GPE that is based off the 4.4.4 update even though it hasn't been rolled out yet to Verizon. I am very confused because I see some roms based on that update despite the Ota not being available. I've tried flashing a couple of roms that are 4.4.4 based but was unable to. Why can't I run a 4.4.4 rom even though I am s-off? And how are developers basing their roms off of it when it hasn't been released to Verizon. I am just completely lost.
I think you're confusing Sense with Android (GPE). Sense is currently at 4.4.2 and about to be 4.4.3 later this week. (HTC is going to skip 4.4.4 because the updates to 4.4.4 are rolled into Sense's 4.4.3.)
You are able to flash GPE based on 4.4.4 or 4.4.3 because the Android version is unrelated to the baseband version. Don't hold me to that though. With Samsung (what I had before this) baseband enforced a minimum Android API level (OS version) but not a maximum. For example, when I flashed MJA, I had to use 4.3 and later. Could not go back to 4.2 or prior. But never mind that, that's Samsung talk. But I assume it's the same. Samsung uses alphanumeric, HTC uses what looks like IP addresses but aren't. 1.55.605.2 is indeed the latest for the VZW One M8.
I don't know why you were unable to flash 4.4.4 ROMs. Sometimes an older version of your recovery (e.g. TWRP) can make it impossible to flash recent ROMs. Check and make sure your recovery is current.
You can definitely flash either of our GPEs, but be warned they are not ready for prime time just yet. The current issue is that signal will drop irregularly in both of them. But we have some smart people working on figuring that out. GPE is typically only available for GSM phones (e.g. AT&T, T-Mobile, International unlocked) and making it work with CDMA (i.e. Verizon) is a nontrivial task. But they're trying. And for some, the issues are forgivable. For me... I'm patiently watching and waiting.
Lastly, you won't get the OTA because you're S-Off and/or because you're rooted and/or because you have a custom recovery. You'll never officially have Sense based on 4.4.4 because HTC's not doing it. Next week or by the weekend, we'll probably start seeing Sense ROMs based on 4.4.3 since that's what's coming.
You're able to flash GPE simply because you're s-off. Once you have s-off, you can flash anything you desire. No guarantees it's going to work though. If the rom isn't ported for Verizon, it's not going to work. You have to do a little homework before you flash a given rom. Read through the thread. If nothing else, search the rom thread for Verizon. More than likely somebody has asked if it will work on Verizon and if so, you'll find your answer.
As to flashing back to an earlier version, once again, you're s-off. You should be able to flash anything you want. I'm somewhat new to HTC also but from what I've read, I don't think you'd have any problem going back. I know with Moto phones it wasn't possible but that was because the bootloader wasn't unlocked and the newer version came with a new bootloader. Since it was locked and the new bootloader had a different signature than the old, you couldn't go back. You're unlocked on here though and it should take anything you throw at it. Old bootloader should be no problem. Should be able to go back. Somebody can correct me if I'm wrong but from what I've read, that's how I see it.
There are two gpe ROMs in the Verizon Android development thread which have been specifically ported and catered to the Verizon devices. Both sjould suffice. Under NO circumstance would I recommend that you flash a GPE ROM from the unbranded HTC development. Same goes for GPE/SENSE kernels.
(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
Hi all, I'm relatively new to the Android world and seeking help from experts here.
I recently bought a used S7 (SM-G930K), it came with Android 8.0 and I want to downgrade to 7.0.
I tried downgrading using its stock firmware with Odin. Attempted many times but only realized that it can only be downgraded as far as the bootloader version goes.
Think my S7 was on bootloader version 2. So as checked for the available stock firmwares, the "earliest" version 2 was still on Android 8.0 (PDA G930KKKU2ERJ1 and CSC G930KKTC2ERJ1).
Anyone can advise me how to go about downgrading to Android 7.0? Though this S7 may not be my primary phone and there's obviously no warranty, I won't want to brick anything.
Do I have to downgrade the bootloader version to 1.0 first? And how do I do that?
Apologies, do excuse these noob questions, I'm not familiar with many Android terms. Cheers!
Model: S7 SM-G930K (KT Telco)
Android version: 8.0
Baseband version: G930KKKU2ERJ1
Security patch: Oct 1, 2018
Basically, on Samsung phones, once you upgrade your bootloader, they put a lock on it, so you can never downgrade it, for security reasons, of course.
The only thing you can do is flashing custom rom, or stock rom with custom recovery & kernel.
Mohamedkam000 said:
Basically, on Samsung phones, once you upgrade your bootloader, they put a lock on it, so you can never downgrade it, for security reasons, of course.
The only thing you can do is flashing custom rom, or stock rom with custom recovery & kernel.
Click to expand...
Click to collapse
I see, now i understand why..
"Custom roms" - does this mean it's made by users like us? And what does "stock rom with custom recovery & kernel" mean?
Can you point me where can i find these roms for my S7? Is it the same as flashing them on Odin?
Many thanks!
Yes custom ROM's are community made. The kernal is kind of like the foundation that sits beneath the ROM, so you can use the official ROM but run a custom kernal to tweak phone behaviour.
Flashing ROM's involves using TWRP instead of Odin. If you're going down that path I would recommend you read very carefully and educate yourself, instead of just gung ho'ing it. Wouldn't want to brick your device.
It's also worth mentioning while you can flash an older custom ROM via TWRP, that doesn't downgrade your bootloader with it. Having a newer bootloader on an older ROM can cause issues.
Most custom ROM's are also made for G930F, while some also support the G930K you may want to make sure before flashing anything.
Beanvee7 said:
Yes custom ROM's are community made. The kernal is kind of like the foundation that sits beneath the ROM, so you can use the official ROM but run a custom kernal to tweak phone behaviour.
Flashing ROM's involves using TWRP instead of Odin. If you're going down that path I would recommend you read very carefully and educate yourself, instead of just gung ho'ing it. Wouldn't want to brick your device.
It's also worth mentioning while you can flash an older custom ROM via TWRP, that doesn't downgrade your bootloader with it. Having a newer bootloader on an older ROM can cause issues.
Most custom ROM's are also made for G930F, while some also support the G930K you may want to make sure before flashing anything.
Click to expand...
Click to collapse
Definitely will be more mindful as rooting does involve some kind of risk of bricking my phone.
Wow that's great info, really appreciate you explaining this to me.
Something new I've learnt! :good: