Hi everyone,
AT&T published a new OTA update.
I am unlocked, rooted and have TWRP. Is this safe?
Also, any thoughts on the purpose of this? The change log says:
What's changing?
New FOTA enhancement – support for 1GB+ file size (OMA DI Client Update).
Is this a setup for the AT&T Marshmallow update?
Thanks.
When I received the message I thought it was going to be the MM update but it turns out it's some sort of LP update. Very disappointed. I can't find release notes as well.
Android Version: 5.0.2
Software Version: 4.28.502.8
Baseband Version: [email protected]_40.56.C33074.00_F
Kernel Version: [email protected] #1 SMP PREEMPT
Build Number: Android Version: 5.0.2
Software Version: 4.28.502.8
Baseband Version: [email protected]_40.56.C33074.00_F
Kernel Version: [email protected] #1 SMP PREEMPT
Build Number: 4.28.502.8 CL511189 release-keys CL511189 release-keys
I can find stuff on 4.28.502.1 and 4.28.502.2 but not Software Version: 5.28.502.8
The only difference I saw was the radio version in the bootloader. I realized the update wasn't MM and impatience got the best of me so I went ahead and flashed a GPE MM rom.
Gotcha gotcha. I couldn't make or receive calls with the MM ROMs so returned to stock AT&T. I hope the MM update is coming.
Sent from my HTC One_M8 using XDA-Developers mobile app
matt11601 said:
Gotcha gotcha. I couldn't make or receive calls with the MM ROMs so returned to stock AT&T. I hope the MM update is coming.
Click to expand...
Click to collapse
This is almost certainly due to AT&T specific deployment of Voice over LTE (VoLTE, which ATT calls "HD Voice") not playing well with non-ATT ROMs. You can call AT&T to have HD Voice option turned off on your account. Details in my post here: http://forum.xda-developers.com/showpost.php?p=62001970&postcount=28
Another option, you can try the stock Developer's Edition MM ROM here (just need to flash the ROM, don't need the flash the firmware; and s-off would be required to do so): http://forum.xda-developers.com/htc-one-m8/development/rom-stock-unlocked-developer-sense-7-t3262894
The Dev Ed is designed to work on AT&T's network, so I'm guessing it shouldn't have the same voice call issue. Although I haven't personally ran into that issue, so I can't confirm that. Plus, the Dev Ed ROM is clean of AT&T branding and bloat, so IMO much better than any stock AT&T ROM, anyway.
redpoint73 said:
This is almost certainly due to AT&T specific deployment of Voice over LTE (VoLTE, which ATT calls "HD Voice") not playing well with non-ATT ROMs. You can call AT&T to have HD Voice option turned off on your account. Details in my post here: http://forum.xda-developers.com/showpost.php?p=62001970&postcount=28
Another option, you can try the stock Developer's Edition MM ROM here (just need to flash the ROM, don't need the flash the firmware; and s-off would be required to do so): http://forum.xda-developers.com/htc-one-m8/development/rom-stock-unlocked-developer-sense-7-t3262894
The Dev Ed is designed to work on AT&T's network, so I'm guessing it shouldn't have the same voice call issue. Although I haven't personally ran into that issue, so I can't confirm that. Plus, the Dev Ed ROM is clean of AT&T branding and bloat, so IMO much better than any stock AT&T ROM, anyway.
Click to expand...
Click to collapse
Yea I remember reading that post. It was very helpful but also disappointing because I had to return to stock. I'm hoping the MM update will come soon, but if not, may try the Dev Edition.
theandies said:
When I received the message I thought it was going to be the MM update but it turns out it's some sort of LP update. Very disappointed. I can't find release notes as well.
Android Version: 5.0.2
Software Version: 4.28.502.8
Baseband Version: [email protected]_40.56.C33074.00_F
Kernel Version: [email protected] #1 SMP PREEMPT
Build Number: Android Version: 5.0.2
Software Version: 4.28.502.8
Baseband Version: [email protected]_40.56.C33074.00_F
Kernel Version: [email protected] #1 SMP PREEMPT
Build Number: 4.28.502.8 CL511189 release-keys CL511189 release-keys
I can find stuff on 4.28.502.1 and 4.28.502.2 but not Software Version: 5.28.502.8
Click to expand...
Click to collapse
Still on .2 firmware
I'm very interested in getting the baseband update. ATT HTC M8 Unlocked S-off. I tried loading the stock ROM and using the OTA update, but it went into TWRP recoery mode and then only upgraded the software version to 4.28.502.8 not the radio. I've also tried the "manual" method using the utility provided by HTC and it hangs about 14% into the upgrade (I gave it a full 30 minutes before I gave up). Any help for this novice?
4/29/16: I'm such an idiot...flashed a stock recovery, so the the manual RUU method worked...except it was the update from last August, not the one from April 7, 2016. So now all that I've accomplished is to (it would seem) unroot, and factory reset. Going to leave as is until the 24 hour wait is over and can re-try the OTA. Maybe now it will work. Still unlocked and s-off.
Does anyone know the device location of the download? If so, I can post it since I haven't updated yet.
matt11601 said:
Does anyone know the device location of the download? If so, I can post it since I haven't updated yet.
Click to expand...
Click to collapse
I have been searching high and low for where on the device the download is stored!
Ok, so i ran RUU_M8[email protected]50319A_40.45.C33065.00_F_release_446225_signed_2
Then ran the april 7 OTA update on my unlocked, rooted, s-off M8. It all seemed to go great, and then bootloop. Tried factory reset, still hangs on HTC screen after ATT "bells". At least I know from the bootloader screen the stupid radio firmware was upgraded (that was the goal) I wish I had used TWRP to save a copy of the above RUU state before I went and did the OTA. Tried booting (not flashing) TWRP to load my last working ROM prior to the RUU which was CM-12 stable release-yay it booted! But if I need to go back to stock ROM I guess I'll need to downgrade with the RUU above?
---------- Post added at 09:38 PM ---------- Previous post was at 09:33 PM ----------
PS this does NOT solve the issue of not receiving phone calls while on a custom ROM the ATT LTE network...so a huge waste of time.
charger1969 said:
But if I need to go back to stock ROM I guess I'll need to downgrade with the RUU above?
Click to expand...
Click to collapse
You can typically on downgrade by RUU if you have s-off.
redpoint73 said:
You can typically on downgrade by RUU if you have s-off.
Click to expand...
Click to collapse
Yup I'm S-off
charger1969 said:
Yup I'm S-off
Click to expand...
Click to collapse
Then yes, downgrade by RUU is probably your best bet to get back to stock (until we have a newer RUU).
So I flashed the RUU 4.28.502.1 through HBOOT. It booted up to LL but I'm not able to update my phone at all. It will take the update file approx around 28MB but when it reboots after flashing the file it gets stuck at the HTC logo after the AT&T logo. I tried to reboot and restore the phone but it doesn't go anywhere. I would have to enter HBOOT again and flash the stock RUU file again to get the phone to boot up again.
Could anyone help me into the right direction? I'm trying to get MM eventually on it.
Sent from my Nexus 6P using Tapatalk
volcalstone said:
So I flashed the RUU 4.28.502.1 through HBOOT. It booted up to LL but I'm not able to update my phone at all. It will take the update file approx around 28MB but when it reboots after flashing the file it gets stuck at the HTC logo after the AT&T logo. I tried to reboot and restore the phone but it doesn't go anywhere. I would have to enter HBOOT again and flash the stock RUU file again to get the phone to boot up again.
Could anyone help me into the right direction? I'm trying to get MM eventually on it.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Sounds like you need to flash the last working ROM you have a back up of. I had the same bootloop issue, if you read post #11
Best,
charger1969 said:
Sounds like you need to flash the last working ROM you have a back up of. I had the same bootloop issue, if you read post #11
Best,
Click to expand...
Click to collapse
Thx I'm unlocked, rooted with s-off. My concern is that by doing the bootable RUU to LL which has stock recovery, why can't I take the OTA updates?
My last rom was actually stock KK with TWRP. I modded so much files so I would at this point I have do an RUU to update. I will probably do a KK RUU with stock recovery and take the LL update OTA. I could be missing something in between, dunno.
Thx
Sent from my Nexus 6P using Tapatalk
Related
Hey, my Friend had buy an unlock HTC Hero (germany).
Now, we has root already, but he is not the guy that change every week his rom like me^^. So, we have load this Rom on the Hero. But he can't call!!! He can answer call's but not call! Any idea's?
I would just reflash the ROM and the latest radio to be safe.
thanks, please post the Link
izmar said:
I would just reflash the ROM and the latest radio to be safe.
Click to expand...
Click to collapse
thanks, but I odnt know how i get the latest Radio and latest Spl and a instruction for a neewbie please^^ Because when i brick that phone I musst Pay! sry for my english
no answer? please help.
check the video tutorials posted here. if you want a stable phone go for a 1.5 rom (sensehero or mcr) now, the 2.1 roms have flaws untill the official release.
okay 1.5, but where are the video tutorials?
at the moment i write it is the thread right below of this one...
I tried to create a new thread for this but I kept getting this message.
To prevent spam to the forums, new users are not permitted to post outside links in their messages. All new user accounts will be verified by moderators before this restriction is removed.
Click to expand...
Click to collapse
So i decided to post here since it is also related to flashing ROM.
I can't wait anymore for HTC to release its '2.1 with sense' update for my HTC Hero. I read an article today that they are pushing the update date (yet again) to May and also that not all features of 2.1 will make it to Hero. So I decided to go the 'Rebels' way & root my device.
Model number: HTC Hero
Firmware version: 1.5
Baseband version: 63.18.55.06EU_6.35.06.18
Kernel version: 2.6.27-8dd6deee [email protected] )
Build number: 2.73.720.5 146733 CL#61267 release-keys
Software version: 1.0.0.A6288
Click to expand...
Click to collapse
Date of purchase: 26-OCT-2009
Country: India
Currently on AIRTEL network. It is not carrier locked. Works with SIM card from other networks too.
What I've done so far:
I downloaded Android SDK. I have successfully rooted my phone & have recovery-RA-hero-v1.6.2.img as my recovery image. I did a nandroid backup. I also updated my radio to 63.18.55.06JU_6.35.09.26. I just finished downloading Villain 5.02 ROM for Hero.
On starting the device with holding POWER+BACK (Fastboot) i see three android robots on skateboards. And following info is displayed on the screen:
HERO CVT SHIP S-ON
HBOOT-1.76.007 (HERO10000)
MICROP-010f
TOUCH PANEL-SYN0104
RADIO-6.35.09.26
Aug 4 2009, 19:43:30
Click to expand...
Click to collapse
So is 1.76.007 the SPL of this phone? Do I need to update it or do anything at all? Will it interfere with flashing custom ROMS?
So by the above info, can anybody please tell me whether my phone is qualified to be flashed with Villain 5.02 ROM without any problems? Do I need to do anything more before going ahead with flashing the custom ROM?
you have done everything right so far, and are good to go. villain5.1 is being uploaded as we speak, so if you can wait a few more minutes you get a more stable version...
kendong2 said:
you have done everything right so far, and are good to go. villain5.1 is being uploaded as we speak, so if you can wait a few more minutes you get a more stable version...
Click to expand...
Click to collapse
Thanks for the reply!
Villain doesn't give MD5 checksum for his downloads. When i tried to unzip it on my PC (i know it is not needed, but just out of curiosity i unzipped it) WinRar told me that the zip archive is corrupt. I'm downloading BeHero 1.3.2 (he gives MD5 checksum, so integrity of file can be checked before flashing)
Do you see any problem with the SPL? Does it not have any bearing on flashing ROM. It didn't interfere with "recovery-RA-hero-v1.6.2.img" image update & Radio update. So am I to assume that it won't interfere with ROM flash as well?
83a6584aefe2221f060775a181c00901
md5 for http://www.villainrom.co.uk/VillainROM5.1.zip
Thanks for that... downloading 5.1 now
What about the SPL thingy?
prmd142 said:
Thanks for that... downloading 5.1 now
What about the SPL thingy?
Click to expand...
Click to collapse
No need to worry about SPLs.
If you want you can update the unlocked version from here:
http://android.modaco.com/content/htc-hero-hero-modaco-com/296389/24-nov-unlocked-spl-for-gsm-hero/
vjprakashbe said:
No need to worry about SPLs.
If you want you can update the unlocked version from here:
http://android.modaco.com/content/htc-hero-hero-modaco-com/296389/24-nov-unlocked-spl-for-gsm-hero/
Click to expand...
Click to collapse
Thanks for all the replies... Just flashed Villain 5.1 & SPL didn't interfere with ROM flash, everything is fine & dandy!
Hey, I got my replacement phone only to find out that I can't root my OTA! Apparently the phone provided by Asurion was running 2.1 OTA as stock and the HBOOT version was 1.49? Does this mean that future versions will be running 1.49 or will it stay at 1.47, and for how long?
Same here. My New eris (not refurb) came in today with 2.1 (2.36.605.1 CL165907) with hboot 1.49 installed (PB0010000).
-------------------------------------
Sent from my EvilEris using TapaTalk
Might be a good thing or a bad thing. We might be able to get the 1.49 bootloader from these new 2.1 OTA phones and so allow us to root.
was my thought as well.
-------------------------------------
Sent from my EvilEris using TapaTalk
I wonder if they used to belong to people who couldn't wait and installed the leak, then claimed their phone broken so they could have them replaced. Refurbs that were once leak. Sound like a bad porno.
-------------------------------------
Sent via the XDA Tapatalk App
I highly doubt that, because we don't have a 2.1 OTA update for the 1.49 hboot. If they didn't have that, then there's no way Asurion could have updated the leaks. If they DID update the leaks, then how come they aren't releasing it to the public?
V3 is the leak. The only difference is the hboot.
-------------------------------------
Sent via the XDA Tapatalk App
Just an FYI that I'm rooted (currently running leak4base) and my HBOOT is 1.49.
fritzel67 said:
Just an FYI that I'm rooted (currently running leak4base) and my HBOOT is 1.49.
Click to expand...
Click to collapse
really? huh
fritzel67 said:
Just an FYI that I'm rooted (currently running leak4base) and my HBOOT is 1.49.
Click to expand...
Click to collapse
I'd like to learn more about this, PM / post here how you did it please. I haven't been keeping up with the other devs lately but last I checked thats the leak 2.1 rom's hboot version. Maybe there are some differences in your 1.49 and the leak 1.49, and we may be able to use that to our advantage, as there are ways to change the nvram that we found earlier.
Yeah 1.49 s-on bootloader out of the box won't get you root.
anyone want to trade an eris with 1.49 for one with 1.46? lol had my hopes up this morning.
homer169 said:
I wonder if they used to belong to people who couldn't wait and installed the leak, then claimed their phone broken so they could have them replaced. Refurbs that were once leak. Sound like a bad porno.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
I've returned three different Eris handsets with various 2.1 leaks on them. The first one I didn't ask for, Verizon just randomly sent me a new phone, so I swapped them. I thought maybe there was a recall, but apparently they're just idiots. The other two were because the trackballs failed. I've been afraid that they would go to refurb these, see the 2.1 leak, then charge me for the replacement.
jcsugrue said:
I've returned three different Eris handsets with various 2.1 leaks on them. The first one I didn't ask for, Verizon just randomly sent me a new phone, so I swapped them. I thought maybe there was a recall, but apparently they're just idiots. The other two were because the trackballs failed. I've been afraid that they would go to refurb these, see the 2.1 leak, then charge me for the replacement.
Click to expand...
Click to collapse
I ran through 6 bb storms, all for hardware issues, and I never got hit for the leaks I had left on them.
homer169 said:
V3 is the leak. The only difference is the hboot.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
You mean v3 is the OTA? Only difference is the setup program to get the phone going (the OTA is intended to move from 1.5, the v3 leak is a complete wipe/flash).
HBOOT doesn't upgrade with OTA.
Do any of you want to see if this isn't just the 2.1 leak v3? Hope I can help. Here's all my info:
Firmware Version: 2.1
Baseband version: 2.42.00.04.12
Kernel version: 2.6.29-8a03cb9a | [email protected] #1
Build number: 2.36.605.1 CL165907 release-keys
Software number: 2.36.605.1
Browser version: WebKit 3.1
PRI Version: 2.11_002
PRL Version: 51866
ERI Version: 5
ANOTHER QUESTION: Why can't we just have the root running the HBOOT 1.49?
If there was root with hboot 1.49 that would mean that those of us on the OTA leak would get root too right?
crax0r said:
Do any of you want to see if this isn't just the 2.1 leak v3? Hope I can help. Here's all my info:
Firmware Version: 2.1
Baseband version: 2.42.00.04.12
Kernel version: 2.6.29-8a03cb9a | [email protected] #1
Build number: 2.36.605.1 CL165907 release-keys
Software number: 2.36.605.1
Browser version: WebKit 3.1
PRI Version: 2.11_002
PRL Version: 51866
ERI Version: 5
ANOTHER QUESTION: Why can't we just have the root running the HBOOT 1.49?
Click to expand...
Click to collapse
That's actually does seem to be a rather strange combination - it seems you have a locked bootloader but the OTA install.
Someone over at Androidforums posted a HTC ROM decoder ring tonight, and from all appearances, you have a mystery combination that does not appear natural.
My bet is on someone who went crazy with fastboot after the 2.1OTA, and wasn't paying attention.
Who wants to bet that techs for Asurion just FR the phone with the (2.1) stock recovery boot - that clears out phone activation as well as /data.
bftb0
erisuser said:
If there was root with hboot 1.49 that would mean that those of us on the OTA leak would get root too right?
Click to expand...
Click to collapse
There actually is a root with 1.49, provided you have 1.49 S-OFF (which is the engineering SPL). What I'm not clear on is where this came from (including how my phone went from .47/.48 to it. (I never installed a leak...just rooted 1.5 to 2.1 then ran custom ROM's...currently on leak4base)
From what I understand, 1.49 S-ON (leak users) cannot be updated with the engineering SPL because the phone sees it as the same or older and won't complete the update. And it can't be hacked, but it's digitally signed by HTC and any attempts to change it corrupt the authentication.
(I'm not 100% sure on all this so please correct any errors)
Does anyone know how I can get hboot 1.49 S-OFF?
An OTA patch has been released for Virgin Mobile Evo V users that includes updated firmware and ICS software. I've added a post in my QADERSO guide thread with more information and a link to the update, and would appreciate feedback from any Evo V users that try it so I can decide whether or not to include it as part of that guide.
ramjet73
FWIW, here is my update experience:
I had TWRP recovery on stock VM ICS rom (Odexed), and S-OFF, and the update would error out with some nonsense about DefaultContainerService.apk hashes not matching up (for its respective patch).
Flashed the RUU (which got rid of TWRP), then applied the update successfully. Still S-OFF, which is good. I have a feeling that TWRP and the update dont play nice, and it doesn't matter if you are S-OFF and Rooted, so long as you have the stock HTC recovery... so that might be a helpful note to someone.
malakai1911 said:
FWIW, here is my update experience:
I had TWRP recovery on stock VM ICS rom (Odexed), and S-OFF, and the update would error out with some nonsense about DefaultContainerService.apk hashes not matching up (for its respective patch).
Flashed the RUU (which got rid of TWRP), then applied the update successfully. Still S-OFF, which is good. I have a feeling that TWRP and the update dont play nice, and it doesn't matter if you are S-OFF and Rooted, so long as you have the stock HTC recovery... so that might be a helpful note to someone.
Click to expand...
Click to collapse
Thanks for the feedback.
Yes, the OTA updates won't install properly without the stock recovery even when they are flashed from the bootloader with S-OFF.
Did you notice any improvement in network connectivity and performance? My understanding is that the primary purpose of this update was to address radio performance with new firmware that was previously being patched with pieces of the Evo 3D firmware.
ramjet73
Well, not really much difference for me so far. I always got full bars at home, and always bearly any signal at work, and this didn't change that. I *very* rarely got the radio interface shortage error when sending a text (most often if I was in a poor signal area), and rarely had a problem where a call would not go out (it would just sit there, but a toggle of airplane or a reboot of phone would fix it). Thusfar, I have not seen these issues, but I have not used my phone much since the update.
Another thing to note in your guide, the stock VM firmware, even with the new update, does not appear to have the latest Adreno drivers. Here is a before/after of a clean, stock VM rom with literally no other apps installed besides Quadrant:
New OTA Update, OTA drivers:
Total: 2363
CPU/Mem/I-O/2D/3D: 3560, 2151, 3904, 400, 1798
New OTA Update, Latest Adreno drivers (ARMv7, 13 Mar 12):
Total: 2621
CPU/Mem/I-O/2D/3D: 4596, 2190, 3943, 388, 1989
User Mode Driver (free download, registration required): https://developer.qualcomm.com/mobi...phics-optimization-adreno/tools-and-resources or here on XDA: http://forum.xda-developers.com/showthread.php?t=1636758
Patch for problem with 3g
Hi ramjet...I am a noob that has just rooted and flashed my evo v on the virgin mobile network. I see you in many threads pertaining to the evo 3d and seem very knowledgeable on the subject. First off I'd like to thank you for your help downgrading my hboot. Your provided links made it much easier when flashing 4.1.2. But when installing jellybean, 3g runs extremely slow or not at all. My speed test run at 20-50k a sec download (usually 800-1200k) and 900k-1100k upload (same as usual). 4g works find when available. Here are my specs from the bootloader
Shooter xc eng s-off rl
Hboot-1.04.2000 (pg8610000)
Radio 1.0600.0426
emmc-boot
apr 16 2011,19:34:31
Have you seen a patch or fix for this? do I need to update my radio? Any help would be greatly appreciated. I am on CyanogenMod 10 Gangnam style rom.
Thanks,
Jeff
ramjet73 said:
An OTA patch has been released for Virgin Mobile Evo V users that includes updated firmware and ICS software. I've added a post in my QADERSO guide thread with more information and a link to the update, and would appreciate feedback from any Evo V users that try it so I can decide whether or not to include it as part of that guide.
ramjet73
Click to expand...
Click to collapse
justinkase said:
Have you seen a patch or fix for this? do I need to update my radio? Any help would be greatly appreciated. I am on CyanogenMod 10 Gangnam style rom.
Thanks,
Jeff
Click to expand...
Click to collapse
The OTA update that was released for Virgin Mobile users includes firmware that is supposed to improve radio performance. Based on what I have seen from other VM users that have installed it, the new "Baseband version" is 1.09.00.0706, which matches the firmware level for the Sprint ICS (2.89.651.2) build so I suspect they are just pushing that firmware to VM users.
The firmware only zip can be downloaded from this post and flashed from the bootloader as PG86IMG.zip in the root of your SD card since you are S-OFF. If that doesn't resolve your issues I would suggest going through the procedure in the post I linked from the OP to install the complete OTA update, then rooting again.
Note to other users: Do not flash that version of firmware if your phone is not a Virgin Mobile Evo V 4G.
ramjet73
Thank you so much for the fast response. I tried the firmware upgrade..still no change in speed. I will try the complete ota update and root again.
jeff
FWIW: On 3G I am getting ~2mbit down, ~768k up, ~83ms ping as per speedtest.net (tested via tethered laptop using phone as wi-fi hotspot). So this radio seems good, but I have nothing to compare it against because I never bothered to test the speed before.
Hboot: 1.57.0000
Software number: 1.14.652.0.710RD
Kernel: 3.0.16-g4211684 [email protected] #1 SMP PREEMPT
Baseband (Radio): 1.09.00.0706
Build: 1.14.652.0 CL372137 release-keys
Browser: WebKit/534.30
PRI: 1.53_144
PRL: 61009
lose root with OTA update?
ramjet73 said:
An OTA patch has been released for Virgin Mobile Evo V users that includes updated firmware and ICS software.
ramjet73
Click to expand...
Click to collapse
Hi!
I have a simple phone that makes me happy. Evo 4G V running stock except it's rooted so I cane use it occassionally as a hotspot.
Does accepting the recent OTA update lose root? if so, can I re-root it using the same method as the first time?
I didn't see a thread on this in particular but if there is one please drop me a link.
Thanks in advance.
Tim
tlyonstlyons said:
Hi!
I have a simple phone that makes me happy. Evo 4G V running stock except it's rooted so I cane use it occassionally as a hotspot.
Does accepting the recent OTA update lose root? if so, can I re-root it using the same method as the first time?
I didn't see a thread on this in particular but if there is one please drop me a link.
Thanks in advance.
Tim
Click to expand...
Click to collapse
Installing the OTA update requires the stock recovery and it applies patches to the stock ROM so the best way to get the update for S-ON users is to relock the bootloader, flash the 1.13.652.2 RUU.exe, download and install the OTA, then unlock again with the same token and root by flashing a custom recovery from fastboot and a superuser zip for the recovery.
If you are completely stock it might be possible to flash the stock recovery from fastboot and apply the OTA, but that would probably require relocking the bootloader anyway since firmware updates are included in the OTA.
Don't forget to backup everything (nandroid and TB recommended) before flashing the RUU.exe since it will reset all your partitions except for those on the SD card. You should be able to do an advanced restore from your nandroid in 4EXT recovery of only the data partition to get your apps and settings back after rooting again. The software patches installed by the OTA only affect the system partition.
ramjet73
Main Version (mainver) changed with Virgin Mobile OTA
To make a long story short, the main version (mainver) was changed in the firmware update zip file flashed as part of the Virgin Mobile (VM) OTA update so if that's installed your mainver will be changed from 1.13.652.2 to 1.14.652.0. That's not a big deal for S-OFF users but it will prevent S-ON users from flashing the original 1.13.652.2 RUU. See this post for more detail and a link to my original VM OTA post which contains a workaround to flash the RUU if you are S-ON.
ramjet73
I have my phone flashed to virgin mobile. Can i use this too or will it brick my HTC EVO 3D CDMA?
kevin130 said:
I have my phone flashed to virgin mobile. Can i use this too or will it brick my HTC EVO 3D CDMA?
Click to expand...
Click to collapse
I'm not sure since I don't know what was done to flash it to Virgin Mobile. If the RUU.exe was used to do that, it shouldn't hurt to do it again, then flash the OTA.
ramjet73
Needed update
I downgraded my phone to hboot 1.40 so I could install a new ROM. After the downgrade and original ROM reload (Negalite is the best), my calls would not go through.
I installed the update file and my radio went from 1.06 to 1.09 and I was able to make reliable calls again. Nothing else was affected, and I'm very happy Ramjet made this available.
I need help inrooting my Evo, I want to go with Jelly bean update but everytime i have tried to unroot i fail and lock my phone and i try by doing the OTA (heard that works and will remove root) but i can error when flashing the file.
If anyone could please help or point in the directions of some good links on how to remove root. Im currently on stock root 1.22.651.3
I didnt really like any of the roms and would rather just go with being unrooted.
Thanks.
vmgarcia15 said:
I need help inrooting my Evo, I want to go with Jelly bean update but everytime i have tried to unroot i fail and lock my phone and i try by doing the OTA (heard that works and will remove root) but i can error when flashing the file.
If anyone could please help or point in the directions of some good links on how to remove root. Im currently on stock root 1.22.651.3
I didnt really like any of the roms and would rather just go with being unrooted.
Thanks.
Click to expand...
Click to collapse
check in the development section.. there is a few threads on how to unroot..
If your HBOOT is 2.09 your hosed with bad radios.
See here:
http://forum.xda-developers.com/showthread.php?t=2074643
tankerkevo said:
If your HBOOT is 2.09 your hosed with bad radios.
See here:
http://forum.xda-developers.com/showthread.php?t=2074643
Click to expand...
Click to collapse
how do i see what hboot i have?
okay after trying to unroot my phone i think i bricked it, it stuck on the htc load up page, and if i try to turn it off it just turns back on. i cant even get into recovery mode, any help?
Read the link above. Sounds like you ran the 3.15 RUU and didn't get the radio update like the rest is us. You are SOL.
That said, you can get back into the phone, all you gotta do is HTC unlock the phone. Just be aware that unless you have the 1.12 radios any JB Rom, stock or custom, will have unstable radios. For an almost stable experience you will need to flash an old ICS Rom.
Sent from my EVO using xda app-developers app
I just arrived from the search button, and this is the closest question I have found to what I need, but I don't quite see an answer to where I am, but I figured I would ask here rather than bother everyone with a new post.
I'm on an HTC EVO 4G LTE rooted with supersu, teamwin and all that stuff. I can't quite remember what package I got, but I did it right when the phone came out and have been happily using it rooted since. I would like to go and either make my phone capable of getting the OTA sprint jellybean update, or find a flash rom that I can install.
I haven't done anything yet. My phone is still rooted and fully functional, but I want to get all the advice before risking anything. I did try to OTA update it earlier, but the Teamwin recovery program came up on the reboot.
Model: Evo 4G LTE
Hardware Version: 0003
Software Version 1.13.651.710RD
Android Version 4.0.3
HTC Sense: 4.0
HTCExtension version : HTCExtension_403_1_GA_8
PRI Version 2.28_003
PRL Version 25010
Kernel Version: 3.0.8-01360-g3fd0422 [email protected] #1 SMP PREEMPT
Baseband Version 1.02.12.0427
Build number 1.13.651.1_R2 CL60201 release-keys
Hi everyone, I'm Josh and I'm a long time reader of XDA. I'm really struggling with the next steps on my HTC one despite reading ton's of information on XDA and many other sources. I could use some help / clarification.
I recently purchased an HTC One m7 ATT version. I've rooted, installed SuperSU, TWRP and unlocked the phone. I was stuck on choosing a rom but I've hit a new snag. I was going to try ViperOne but noticed they insist you install the latest firmware updates first. Here's where I'm lost. I'm running the stock version that came with my phone when it was locked.
Kitkat 4.4.2, Sense 6
FW# - 5.12.502.2
Hboot - 1.57
Radio - 4m.27.3218.14
I can't seem to get the OTA's, how do you get OTA's, do you have to run official att service sim like gophone? Or can you use straight talk like I currently have? Or do you not even need a sim for OTA's? I don't currently have a sim in the phone, was waiting to get all this sorted first. Will OTA's break root? Would it be beneficial to turn the phone into international version to get OTA's faster and would I lost the 4g lte abilities of phone if I did this?
How do I go about putting these firmware updates on, is s-off required even if you use a signed RUU from "androidruu dot com" for example?
I would like to get the latest official firmware releases on the phone and get it updated to kitkat 4.4.4 from the official releases and then put a custom rom on of my choice.
Is any of this even necessary? Are firmware updates included with the Rom's? How is an RUU different than a rom?
Someone, if possible please help me get this all sorted out, I'm so confused, it would be very much appreciated. Thanks!
jpcreativeimagery said:
I recently purchased an HTC One m7 ATT version. I've rooted, installed SuperSU, TWRP and unlocked the phone. I was stuck on choosing a rom but I've hit a new snag. I was going to try ViperOne but noticed they insist you install the latest firmware updates first. Here's where I'm lost. I'm running the stock version that came with my phone when it was locked.
Kitkat 4.4.2, Sense 6
FW# - 5.12.502.2
Hboot - 1.57
Radio - 4m.27.3218.14
I can't seem to get the OTA's, how do you get OTA's, do you have to run official att service sim like gophone? Or can you use straight talk like I currently have? Or do you not even need a sim for OTA's? I don't currently have a sim in the phone, was waiting to get all this sorted first. Will OTA's break root? Would it be beneficial to turn the phone into international version to get OTA's faster and would I lost the 4g lte abilities of phone if I did this?
Click to expand...
Click to collapse
You wont get OTA's unless you are stock, you can use this to get back to stock: http://forum.xda-developers.com/showthread.php?t=2775650 to be able to receive OTA updates.
jpcreativeimagery said:
Are firmware updates included with the Rom's? How is an RUU different than a rom?
Click to expand...
Click to collapse
No firmwares are never included in ROMs, and RUU reset your phone (both firmware and ROM) to fully stock, but you would need an RUU with same or higher version that you are on now. (with S-ON)
what is latest att firmware
@clsA, nkk71 and I have been talking on the #AndroidRevolution irc channel, we/I am trying to get this resolved to figure out if I need s-off in order to grab latest firmware's before I apply a custom rom because it seems att is way behind everyone else since the rest seem to be 6.0.something. Can you confirm what latest att firmware # is for htc one via their software update on the phone? I have reset phone to stock but it's still stuck on 5.12.xxx.xx (whatever the # is, don't remember right now) and claiming it's up-to-date, trying to figure out if boot-loader also has to be locked in addition to stock rom and stock recovery and root removed (cause I did all that but left bootloader unlocked), I've been reading that it does, but neither of us can confirm this. And do you need official att sim/service to do the updates? Additionally, could you direct to a list of signed firmware updates for flashing with s-on if this is not the latest firmware. Thanks!
clsA, just fyi, he used your Guru Reset ROM 5.12.502.2
but doesnt get any OTA updates
I tried it, but since i'm not on ATT, it doesnt even accept my device
nkk71 said:
clsA, just fyi, he used your Guru Reset ROM 5.12.502.2
but doesnt get any OTA updates
I tried it, but since i'm not on ATT, it doesnt even accept my device
Click to expand...
Click to collapse
@jpcreativeimagery
Well that may be because their have been no updates since that release
http://www.htc.com/us/support/htc-one-att/news/
clsA said:
@jpcreativeimagery
Well that may be because their have been no updates since that release
http://www.htc.com/us/support/htc-one-att/news/
Click to expand...
Click to collapse
aha :laugh:
quick question though.... seems ATT has it's own software update "solution"? flashed your Guru Reset ROM, and gave me "Device not provisioned" (or something like that), and the system update is not the usual htc system updated... weirdish (well, at least for me)
thanks bud
nkk71 said:
aha :laugh:
quick question though.... seems ATT has it's own software update "solution"? flashed your Guru Reset ROM, and gave me "Device not provisioned" (or something like that), and the system update is not the usual htc system updated... weirdish (well, at least for me)
thanks bud
Click to expand...
Click to collapse
Yes they do and you have to be on their network to even download the update on Wifi
clsA said:
Yes they do and you have to be on their network to even download the update on Wifi
Click to expand...
Click to collapse
nasty
nkk71 said:
nasty
Click to expand...
Click to collapse
Well their are enough working RUU + OTApkg.zip you don't really miss much
latest firmware
clsA said:
Well their are enough working RUU + OTApkg.zip you don't really miss much
Click to expand...
Click to collapse
@clsA, do you know of thread that list the latest firmware updates for flashing to an ATT M7_UL with s-off? I'm going to s-off the phone and bite the bullet with sunshine so i can take advantage of the latest firmware with a custom rom since ATT is so slow/behind with the software/firmware updates.
Thanks again for all your help and let me know.
jpcreativeimagery said:
@clsA, do you know of thread that list the latest firmware updates for flashing to an ATT M7_UL with s-off? I'm going to s-off the phone and bite the bullet with sunshine so i can take advantage of the latest firmware with a custom rom since ATT is so slow/behind with the software/firmware updates.
Thanks again for all your help and let me know.
Click to expand...
Click to collapse
Sure ... I recommend converting to the Developers edition for the most updates
after your s-off Change your CID fastboot oem writecid BS_US001
then flash this RUU >> http://www.androidruu.com/getdownlo...8_10.38r.1157.04L_release_353887_signed_3.exe
And then you can take OTA updates up to the current 6.07.1540.2 (3 updates I think)
I'm uploading the file's I used Here >> https://www.androidfilehost.com/?w=files&flid=24178
Their is also a RUU now from HTC >> http://dl3.htc.com/application/RUU_...4_10.33E.1718.01L_release_404528_signed_2.exe
bricked / boot hang / fixed with reset
clsA said:
Sure ... I recommend converting to the Developers edition for the most updates
after your s-off Change your CID fastboot oem writecid BS_US001
then flash this RUU >>
And then you can take OTA updates up to the current 6.07.1540.2 (3 updates I think)
I'm uploading the file's I used Here >>
Click to expand...
Click to collapse
@clsA, thank you so much for that, I actually ended up following @vomer 's guide and turning it into super CID because it seemed that the firmware updates were newer than the developer ones oddly enough, 6.0.9 and 6.0.9.xxx.10 and then there's 6.0.9.xxx.11 and .12 but this is where i hit a snag, all went smoothly using vomers firmwares up till 6.0.9.xxx.10 but then i tried to flash the .11 and .12 from ARHD and the device bricked/ hangs on boot....ended up having to use adb push to get your reset on there and reset the device, flash the original firmware etc...phone is working again (I was tempted to panic but maintained control ;P) but ultimately means i wasted a bunch of time only to have start over again....for now I've left it 5.12 and stock....maybe you could help figure out what went wrong when you get a chance.
Thanks.!
i left recovery and root on during the reset just in case it didn't work but did flash back the stock radio for that rom as well
jpcreativeimagery said:
i left recovery and root on during the reset just in case it didn't work but did flash back the stock radio for that rom as well
Click to expand...
Click to collapse
Theirs nothing wrong with the Stock 5.12.502 firmware from AT&T in fact it's one of the most stable. You can flash mostly any rom you want with that firmware installed. The reason I recommend the Developer edition right now is because Lollipop+Sense is due out any day now on that model.
how to proceed
clsA said:
Theirs nothing wrong with the Stock 5.12.502 firmware from AT&T in fact it's one of the most stable. You can flash mostly any rom you want with that firmware installed. The reason I recommend the Developer edition right now is because Lollipop+Sense is due out any day now on that model.
Click to expand...
Click to collapse
@clsA, I was bent on the firmware update to take advantage of latest enhancements with ARHD and they recommended at least v6 xxx .11 eventhough the rom is based on v6 xxx.12, viperone also strongly advised latest firmware updates....does the developer versions you sent me have the calling fix for when the audio in the call was lost because of google update? Also, quick question, why did you include the 4 xxx something base firmware...i can just proceed with the CID change and start at the 6 series firmwares because I'm already at later version with att stock 5.12 right?
Any idea what happened the other night with the bricking - would boot, hang on black screen after first htc logo on white background and then just have the hardware touch buttons lit....was it because the firmwares ARHD posted required the bootloader to be re-locked? (failed to notice this until after I had semi-bricked it)
Also, what backup app would you recommend? looking to restore all my apps and settings after these wipes etc...getting tired of redoing it all again each time.
Thanks!
jpcreativeimagery said:
@clsA, I was bent on the firmware update to take advantage of latest enhancements with ARHD and they recommended at least v6 xxx .11 eventhough the rom is based on v6 xxx.12, viperone also strongly advised latest firmware updates....does the developer versions you sent me have the calling fix for when the audio in the call was lost because of google update? Also, quick question, why did you include the 4 xxx something base firmware...i can just proceed with the CID change and start at the 6 series firmwares because I'm already at later version with att stock 5.12 right?
Any idea what happened the other night with the bricking - would boot, hang on black screen after first htc logo on white background and then just have the hardware touch buttons lit....was it because the firmwares ARHD posted required the bootloader to be re-locked? (failed to notice this until after I had semi-bricked it)
Also, what backup app would you recommend? looking to restore all my apps and settings after these wipes etc...getting tired of redoing it all again each time.
Thanks!
Click to expand...
Click to collapse
The Developers Edition 4.x RUU is the last RUU .. then it's 3 updates and your at the current version and ready for the Lollipop update
The ARHD International firmware needs the MID changed to work, You can eather edit the android_info.txt or change you MID to make them work
clsA said:
The Developers Edition 4.x RUU is the last RUU .. then it's 3 updates and your at the current version and ready for the Lollipop update
The ARHD International firmware needs the MID changed to work, You can either edit the android_info.txt or change you MID to make them work
Click to expand...
Click to collapse
@clsA, hmm, did not see that anywhere in the post...def. did not change MID...but they did specify needing locked bootloader, any idea why? will either of those cause the boot problem I described? Or can the firmware after 6.xxx.10 be incompatible with the att stock rom and i actually needed to flash a rom before proceeding?
When you said earlier "And then you can take OTA updates up to the current 6.07.1540.2 (3 updates I think)" you mean flash them or can take them via the OTA update service....in the dev edition does the built in OTA update service work with unlock and root?
what version does .401 mean, is that international? I know the .1540 designates developer edition.
What backup for settings and apps would you recommend, would titanium suffice?
Thanks again for all the help.
jpcreativeimagery said:
@clsA, hmm, did not see that anywhere in the post...def. did not change MID...but they did specify needing locked bootloader, any idea why? will either of those cause the boot problem I described? Or can the firmware after 6.xxx.10 be incompatible with the att stock rom and i actually needed to flash a rom before proceeding?
When you said earlier "And then you can take OTA updates up to the current 6.07.1540.2 (3 updates I think)" you mean flash them or can take them via the OTA update service....in the dev edition does the built in OTA update service work with unlock and root?
what version does .401 mean, is that international? I know the .1540 designates developer edition.
What backup for settings and apps would you recommend, would titanium suffice?
Thanks again for all the help.
Click to expand...
Click to collapse
Lollipop is coming in the next few days. Just go back to post #11 and flash the RUU and the OTA updates
I gave you the link to all the file's I used. Your S-off no need to lock the bootloader and you flash the OTA updates from stock recovery yourself
just download them all to your phone sdcard and flash them in order.
I use HTC Backup is all I need. And google keeps my contacts and calender
clsA said:
Lollipop is coming in the next few days. Just go back to post #11 and flash the RUU and the OTA updates
I gave you the link to all the file's I used. Your S-off no need to lock the bootloader and you flash the OTA updates from stock recovery yourself
just download them all to your phone sdcard and flash them in order.
I use HTC Backup is all I need. And google keeps my contacts and calender
Click to expand...
Click to collapse
@clsA: What bout with:
** Tampered **
** unlocked **
M7_UL PVT SHIP S-OFF RH
HBOOT-1.56.0000
RaDIO-4T.24.3218.09
OpenDSP-v32.120.274.0909
OS-4.18.502.7
eMMC-boot 2048MB
Jan 28 2014, 09.32.41.0
Should I follow the same procedure? I want to try out the GPE Lollipop. Just wondering which firmware I should flash?
fc3211 said:
@clsA: What bout with:
** Tampered **
** unlocked **
M7_UL PVT SHIP S-OFF RH
HBOOT-1.56.0000
RaDIO-4T.24.3218.09
OpenDSP-v32.120.274.0909
OS-4.18.502.7
eMMC-boot 2048MB
Jan 28 2014, 09.32.41.0
Should I follow the same procedure? I want to try out the GPE Lollipop. Just wondering which firmware I should flash?
Click to expand...
Click to collapse
Depends on what you mean "Try Out " ? you aether convert to Full GPe or you flash a rom.
If you convert, you simple change your CID and flash the RUU.
If you want to just see if it's for you, flash the rom .. I like this one >> http://forum.xda-developers.com/htc-one/development/rom-google-play-edition-lollipop-v1-00-t2963927
But it does require the latest firmware so yes post #11 would get you to the newest firmware