From the recent FTC-HTC settlement:
IT IS FURTHER ORDERED that respondent shall develop security patches to fix the
security vulnerabilities described in Attachment A for each affected covered device having an
operating system version released on or after December 2010. Within thirty (30) days of service
of this order, respondent shall release the applicable security patch(es) either directly to affected
covered devices or to the applicable network operator for deployment of the security patch(es) to
the affected covered devices. Respondent shall provide users of the affected covered devices
with clear and prominent notice regarding the availability of the applicable security patch(es) and
instructions for installing the applicable security patch(es).
Click to expand...
Click to collapse
Sadly:
Provided, however, that this Part does not obligate respondent to identify and correct security
vulnerabilities in third parties’ software on covered devices to the extent the vulnerabilities are
not the result of respondent’s integration, modification, or customization of the third party
software.
Click to expand...
Click to collapse
This applies to HTC Logger, Carrier IQ, and a HTC application installer. So bugs in Android itself are going unpatched, i.e., no obliged ICS upgrade. Still, any patch at all might motivate HTC to release some of the more egregious issues.
...I wasn't watching for updates and now I have a boot loop...
Hmmmmmmmm, it seems that HTC rolled out an OTA for my View 4g and now the device is boot-looping to clockworkmod recovery to install an update that I don't want installed automatically...
i can adb shell into the device... I've formatted cache... How do i get the device into a normal boot and apply the update via zip file?
I'm running globatron's rooted stock honeycomb rom for the View 4g (sprint's flyer variant).
hackvan said:
Hmmmmmmmm, it seems that HTC rolled out an OTA for my View 4g and now the device is boot-looping to clockworkmod recovery to install an update that I don't want installed automatically...
i can adb shell into the device... I've formatted cache... How do i get the device into a normal boot and apply the update via zip file?
I'm running globatron's rooted stock honeycomb rom for the View 4g (sprint's flyer variant).
Click to expand...
Click to collapse
How big was the download? Can you grab the update.zip and post it to be downloaded?
Sent from my SPH-D700 using Tapatalk 2
hackvan said:
Hmmmmmmmm, it seems that HTC rolled out an OTA for my View 4g and now the device is boot-looping to clockworkmod recovery to install an update that I don't want installed automatically...
i can adb shell into the device... I've formatted cache... How do i get the device into a normal boot and apply the update via zip file?
I'm running globatron's rooted stock honeycomb rom for the View 4g (sprint's flyer variant).
Click to expand...
Click to collapse
OTA requires stock recovery to install. It will never install by CWM.
It seems that gremlins were responsible for that reboot into cw-recovery...
i eventually kicked my view4g back into a normal boot somehow and i haven't been able to reproduce the problem.
my tablet doesn't seem to think that an update is available for my device, and I disabled automatic update checking in setting so i don't get another rude surprise...
This experience really makes me want to experiment with a jellybean rom for the flyer/view....but the roms for the flyer don't work on the view. grrrrrrrrr. it's a great device and i like the scribble/note software better than samsung's s-note app on the galaxy note 2... great pen, samsung, but crappy software.
hackvan said:
It seems that gremlins were responsible for that reboot into cw-recovery...
Click to expand...
Click to collapse
Not, its not gremlins. You still are not understanding. If you try to install an OTA, it needs to reboot into stock recovery to install the update. And since it doesn't find it (CWM is a custom recovery, and different from the stock recovery) it bootloops or gets stuck.
Usually, you need to mount the SD card on your computer and delete the OTA file to get out of the bootloop. So if you booted normally without having to do that, you are lucky. You should find and delete the file before you get stuck again.
Related
This guide will enable you to easily root your phone in 6 steps. I've taken out the mystery and complications.
1) Go to HTC Dev site and manually unlock your bootloader. Select "register" and create your account.
1a) After you are registered select "all other supported models" in the pull down box
1b) Click "begin unlock bootloader". it will ask "are you sure" yes of course you are. acknowledge legal terms. then continue.
1c) Ignore the battery pull instructions as we can't pull the battery. hold down the power key and the volume down key until the bottom buttons stop flashing and your phone shuts off (don't worry if you take a screenshot. It happens all the time). then release ONLY THE POWER BUTTON. Keep holding the volume down key until the bootloader screen shows up.
1d) Follow "step 3" and the rest of the instructions as listed on the HTC site to unlock your bootloader manually.
2) Install android ADB/SDK on your pc. This video shows how to do it nicely:
2a) ****NEW UPDATED 03/05/13*** Alternatively if you DON'T want to install ADB/SDK you can just download the NON-FLASHABLE platform-tools.zip file located in my dropbox folder here.
Just extract this folder to your desktop using WINZIP or whatever archive tool you use and proceed to step 3.
3) Open a command line in your "platform-tools" folder by holding shift+right click anywhere within the folder and selecting the menu option "open a command window here". Then click here to install TWRP using fastboot. Follow the "Download - Fastboot Method:" instructions.
3a) If your phone isn't detected by windows please install the proper USB drivers for your operating system. Go here for 32bit. Go here for 64 bit.
4) Flash SuperSu and Busybox on your device:
4a) Click here and download the latest version of SuperSu. save it to your sdcard.
4b) Go to my dropbox and download Busybox 1.20.2 and save it to your sdcard.
5) Reboot into recovery (via the bootloader selection)
6) Flash the SuperSu zip and the Busybox zip listed in 4a and 4b
That's it!
"So now what?" you may be asking.
You are now free to flash ROMs that support s-on.
Two are my favorites are
(1) Stock with Goodies. (my personal favorite and the one I use today). This is a great ROM for beginners and people who prefer a slimmed down ROM (minus the bloat) and lots of free memory!
(2) Viper4G. This is a ROM for more experienced users and offers TONS of customization.
You can also run apps from Google play that required ROOT access!
If you're feeling slightly adventurous you can flash a custom kernel (which will allow you to overclock your phone). Two of the kernels I use are:
(1) ElementalX by flar2. Click here to take a trip over there. This one is especially important to flash as it seems HTC was up to shenanigans with the latest HBoot (2.09).
If you're unlucky enough to have HBoot 2.09 they have RESTRICTED access to your /system partition. What does this mean to you? It means that if any app writes to your /system partition (ROOTED or not) the phone will "panic" and reboot. Shady behavior if you ask me. The solution? Flash this kernel! it will give you write access so that everything works properly.
(2) The Arc-Reactor kernel! This one is for people that are s-off (see below for an explanation of s-off) only! It's the kernel I currently use and is the fastest kernel out there! Highly recommended if you decide to go s-off!!!
If and when you're feeling more adventurous you can go "s-off" (security off) which removes any security limitations of your phone. It makes flashing ROMs and updating firmware a lot easier. You can find out about s-off by taking a trip over to the DirtyRacun thread here. I will NOT walk you through this process. They will totally help you on their IRC channel. Just read post # 1 in that thread.
There's also a new method of s-off which literally takes 2 minutes. It's called facepalm and is located here But is NOT for the feint of heart, bad typers, nor people that cannot follow instructions! Why? One typo here and your phone is a brick. A paperweight. Useless. Well...you can recover...but that's not the purpose of this thread. If you DO brick your phone PM me. I'll help you out.
I take NO credit for any of this. It's all out there to learn I just put it all together. In one spot. Any questions feel free to PM me.
If I helped you out hit the THANKS button...or buy me a beer! Either way lol!
Tested and works with 3.16.651.3 (even if you took the OTA and have hboot 2.09 and are s-on)
Did you use SuperSU or Superuser for root access? Either way could you please update the binary to see if it succeeds or if you get an instant reboot?
lancemoreland said:
Did you use SuperSU or Superuser for root access? Either way could you please update the binary to see if it succeeds or if you get an instant reboot?
Click to expand...
Click to collapse
Everyone that is using supersu is experiencing that issue. The program itself will grant superuser access to your device. You don't need to open it. When you try and open it it will attempt to update the binary and then reboot the phone. You can ALWAYS reflash a new version of supersu when they update it.
To be clear: I'm up and running on my phone right now with superuser access. I'm fine unless I try to open the supersu program itself. Then I experience this issue you pointed out.
rawintellect said:
Everyone that is using supersu is experiencing that issue. The program itself will grant superuser access to your device. You don't need to open it. When you try and open it it will attempt to update the binary and then reboot the phone. You can ALWAYS reflash a new version of supersu when they update it.
To be clear: I'm up and running on my phone right now with superuser access. I'm fine unless I try to open the supersu program itself. Then I experience this issue you pointed out.
Click to expand...
Click to collapse
I agree. I am up and running also but the new hboot locks the system partition and any app that tries to write to it will cause a reboot. Ad-free is another example.
lancemoreland said:
I agree. I am up and running also but the new hboot locks the system partition and any app that tries to write to it will cause a reboot. Ad-free is another example.
Click to expand...
Click to collapse
Indeed this is a well documented problem but really not what this thread is about. Perhaps you can check out THIS thread where they are discussing this issue at length and hopefully they will come up with a solution for it?
http://forum.xda-developers.com/showthread.php?t=1538053
It also looks as though chainfire (the OP) is working on a fix if I read the last few posts correctly. and when he gets it I will update this post with it.
rawintellect said:
It also looks as though chainfire (the OP) is working on a fix if I read the last few posts correctly. and when he gets it I will update this post with it.
Click to expand...
Click to collapse
Yes I am participating in that thread. Chainfire is looking for a work around for his specific app, other apps that write to the system partition will no longer work. The point is that with Hboot 2.09 there are limitations and we will not enjoy full root as we have before when we were s-on.
Updated with an alternative superuser program.
SuperSU would ask to update binary and then just reboot. This fixed my problem for being able to access/deny and turn off messages. However it did not uninstall superSU will this cause a conflict having them both?
Edit: Okay I am dumb, I had to uninstall superSU first. Then I reflashed superuser to be able to have root privileges for my apps. When I just reflashed superuser hoping it would get ride of and superuser and keep root it did not.
Thanks it worked!
Help with rooting please.
So my phone was updated OTA without being rooted to 3.15.651.16 but now it is frozen. The touch screen will work temporarily upon a simulated battery pull and then freeze again only for me to simpull again and then it freeze again. I've gone into the bootloader and factory reset and wiped the cache but it's still messed up. So I think that maybe it's the software not installing correctly or something because this only started happening immediately after I download the new update.
I'm thinking about rooting my phone and even though I'm a pretty techy person this is new to me. I'm hoping that if I root my phone I can put it back to the stock software before the update and then just re-update OTA stock to the new update. I think that may fix it. Do y'all have any input it would be greatly appreciated as I have been dealing with this useless phone for over a week now.
Thanks.
MrSteez said:
So my phone was updated OTA without being rooted to 3.15.651.16 but now it is frozen. The touch screen will work temporarily upon a simulated battery pull and then freeze again only for me to simpull again and then it freeze again. I've gone into the bootloader and factory reset and wiped the cache but it's still messed up. So I think that maybe it's the software not installing correctly or something because this only started happening immediately after I download the new update.
I'm thinking about rooting my phone and even though I'm a pretty techy person this is new to me. I'm hoping that if I root my phone I can put it back to the stock software before the update and then just re-update OTA stock to the new update. I think that may fix it. Do y'all have any input it would be greatly appreciated as I have been dealing with this useless phone for over a week now.
Thanks.
Click to expand...
Click to collapse
Well my suggestion is to go ahead and unlock your phone, flash a recovery and root it using my instructions. Then if you want BONE stock flash the odexed version of Jellybean that Viperboy has in his thread located here: http://forum.xda-developers.com/showthread.php?t=2045929
Why am I suggesting you do this? Because the OTA was very bugged. HTC is VERY slow with fixes. Developers can fix errors in the base errors usually faster than HTC. And most importantly when you are feeling like a change you can flash a custom zip at any time. The ONLY downside to unlocking and rooting is that you void your warranty with HTC, but NOT with sprint! Sprint will still honor a replacement phone when you RELOCK your phone and use the RUU (which isn't available yet but will be) to bring it back to stock. Your bootloader will say *RELOCKED* which lets them know you unlocked it but again they will honor a replacement.
Updated thread with instructions on manually uninstalling supersu first before installing superuser 3.2
Thank you very much!
rawintellect said:
Well my suggestion is to go ahead and unlock your phone, flash a recovery and root it using my instructions. Then if you want BONE stock flash the odexed version of Jellybean that Viperboy has in his thread located here: http://forum.xda-developers.com/showthread.php?t=2045929
Why am I suggesting you do this? Because the OTA was very bugged. HTC is VERY slow with fixes. Developers can fix errors in the base errors usually faster than HTC. And most importantly when you are feeling like a change you can flash a custom zip at any time. The ONLY downside to unlocking and rooting is that you void your warranty with HTC, but NOT with sprint! Sprint will still honor a replacement phone when you RELOCK your phone and use the RUU (which isn't available yet but will be) to bring it back to stock. Your bootloader will say *RELOCKED* which lets them know you unlocked it but again they will honor a replacement.
Click to expand...
Click to collapse
Thanks I seriously appreciate it. I'm at work right now (I actually work at Sprint by the way which is why I'm not worried about having the phone replaced my tech will do it regardless) so I'm probably gonna look over your instructions carefully and then do this tomorrow. I'll let you know what happens I'm really hoping this will do it. It has to be some kind of serious installation bug in the new update because I never had this problem until literally minutes after updating.
And then after the completely stock RUU comes out (with no root or anything special) I can go back to completely locked and stock again? That's what I think I'd prefer but who knows I'm a Android and tech fanboy maybe I'll prefer the root.
MrSteez said:
Thanks I seriously appreciate it. I'm at work right now (I actually work at Sprint by the way which is why I'm not worried about having the phone replaced my tech will do it regardless) so I'm probably gonna look over your instructions carefully and then do this tomorrow. I'll let you know what happens I'm really hoping this will do it. It has to be some kind of serious installation bug in the new update because I never had this problem until literally minutes after updating.
And then after the completely stock RUU comes out (with no root or anything special) I can go back to completely locked and stock again? That's what I think I'd prefer but who knows I'm a Android and tech fanboy maybe I'll prefer the root.
Click to expand...
Click to collapse
yes. going back to stock is as simple as this:
(1) Boot your phone into the bootloader. make sure fastboot is selected. if you have the drivers installed correctly your phone will read "fastboot usb"
(2) if you followed my instructions on rooting you have ADB/SDK installed. so issue the command to relock your phone. type: fastboot oem lock
(3) run the RUU for 3.15.651.16. Done. Your bootloader will say *relocked* but it will be 100% stock.
Uh oh
I think i messed up. I did not see busy box installed and SuperSU is not updating.
The file listed in step 6 contains busybox. It also contains supersu. You want to flash the superuser file after flashing the file in step 6. It will overlay supersu with superuser 3.2. There is no need to update superuser 3.2 once you flashed it. It is the latest release.
Sent from my EVO using xda app-developers app
do i need to just flash the new superuser and it will fix the binary problema nd the titanium problem?
mobilecj said:
do i need to just flash the new superuser and it will fix the binary problema nd the titanium problem?
Click to expand...
Click to collapse
I replied to your email. But check my first post on the subject of superuser and how to uninstall supersu. if you need to that is. I tested this myself and it did uninstall supersu for me by just flashing superuser 3.2. Some people have reported this doesn't work for them.
okay sorry just got both i am going to try it now.. Its all knew to me it seemed like the information was explaining a dual process and i only had acquired one problem.. will post back in a few!
Hello, recently I have rooted my phone using the toolkit. The current recovery I have is TWRP. I wanted the root in the first place to be able to use xposed. However, it wont work, Whenever I try to install the update or new version it force reboots my phone. Also I found out I cannot update my software! I tried unrooting using the unroot option on SU but it was only temporarily. I want a permanent unroot and back to stock.
Android version : 4.4.2
Software number : 1.12.502.18
I downloaded my stock image from http://forum.xda-developers.com/showthread.php?t=2701376 and the toolkit from http://forum.xda-developers.com/showthread.php?t=2699065
I tried to flash it using the toolkit but it gave me an error when I tried to flash it. I don't recall correctly but it said something about a remote error right when it was sending the image over. Honestly I do not want to do it again to see what it said in fear of bricking my phone. So I will try to be as detailed as possible.
When I downloaded the image it said something about the name not being the original one. When I first tried flashing the stock ROM with the original name when I download it"stock recovery 1.12.502 recovery.img" it (the toolkit) gave me an immediate error of not being able to select it. So I renamed it to "recovery.img". I tried again and it actually was in the process of flashing. THen the error showed up as said above. Someone please help me. Thank you.
Update
So i just downloaded a different image. I flashed it successfully! I am currently rebooting from the original recovery! Currently I am on the htc one loading screen. It's been a couple minutes, hopefully I did not brick it...
NOPE! I successfully returned to stock! ANother issue...I still have root access! How can remove SU? I tried the unroot option in the app but I am still rooted after reboot...
UNROOTED. Sadly SU won't delete...but at least I'm unrooted and can update now.
Sent from my HTC One_M8 using XDA Free mobile app
helpmeunrootmyphone said:
UNROOTED. Sadly SU won't delete...but at least I'm unrooted and can update now.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
I don't know if the app is that big of a deal to you, but if it is, your options are...
1. Try factory reset in settings (may or may not work)
2. Reflash TWRP and flash the SuperSU.zip again than do a full unroot in settings.
3. Reflash TWRP and flash stock Sense ROM
Also, I made a guide in general which will help you fully return to stock. To begin the guide, you will need to be unlocked, rooted, and S-Off. That guide will help you hide the tampered and relocked banner.
If you don't care about the banners and the SuperSU app, it's probably not worth the effort and time.
Good luck.
Sent from my HTC One_M8 using Tapatalk
So you had an issue with Xposed, and you solution was to unroot? Wouldn't it have made more sense to troubleshoot the xposed problem? If you bothered to unlock the bootloader and root in the first place, IMO unrooting is a step backwards.
I'm also not a big fan of applying OTAs to a modded device. Yes, you cannot install official OTA updates on a modded phone. In particular, if stock recovery is not present, as its required for the OTA to install. If you want the latest software, just wait until the rooted version is posted in the Development section. Custom ROMs based on the 1.58 update started to be posted one day after the OTA started rolling out; and the stock rooted version was posted only 2 days after OTA release. For some people, getting it from here may even be faster than waiting for the OTA! That's pretty much how it goes. As long as there is developer interest in the device, you can rely on the latest software being available very quickly in the Development section.
The stock AT&T software is garbage anyway. I can't stand the amount of bloat, gimped features (WiFi hotspot) and other AT&T meddling. I don't understand why anyone would prefer this over other options. Software updates are always going to go to the international version first, anyway (AT&T is notorious for delaying updates for "testing"). What are you really getting with the 1.58 update? Extreme Power Savings mode, and a few other fixes? International M8 has had EPS mode for some time now.
---------- Post added at 09:31 AM ---------- Previous post was at 09:17 AM ----------
helpmeunrootmyphone said:
I downloaded my stock image from http://forum.xda-developers.com/showthread.php?t=2701376 and the toolkit from http://forum.xda-developers.com/showthread.php?t=2699065
I tried to flash it using the toolkit but it gave me an error when I tried to flash it. I don't recall correctly but it said something about a remote error right when it was sending the image over. Honestly I do not want to do it again to see what it said in fear of bricking my phone. So I will try to be as detailed as possible.
When I downloaded the image it said something about the name not being the original one. When I first tried flashing the stock ROM with the original name when I download it"stock recovery 1.12.502 recovery.img" it (the toolkit) gave me an immediate error of not being able to select it. So I renamed it to "recovery.img". I tried again and it actually was in the process of flashing. THen the error showed up as said above. Someone please help me.
Click to expand...
Click to collapse
Why do you need to use the toolkit at all, to flash recovery? Flashing recovery is a single fastboot command. Easy.
The toolkit adds unnecessary complication; and I've seen them cause errors when doing it "manually" works just fine. The toolkit might not be the problem in your case, but we would never know unless you try to do it manually.
If you really want to flash stock recovery (not my personal recommendation), I would start by wiping cache and flashing recovery with fastboot. I've seen maybe dozens of cases where issues with flashing a recovery was solved simply by wiping cache:
fastboot erase cache
fastboot flash recovery "filename.img"
I am having the same issue as above using the same build file from the link given in the other thread. However, whenever I am in Bootloader, the computer or terminal does not recognize my device.
1.12.502.18
Anytime I try to use the toolkit or manually through the command line, it gives me "unc paths are not supported" or "device not found". It is the same for both Bootloader and Recovery. My original problem was the person I bought it from had root on it so I decided to wipe the OS without backing up and now cannot get the Stock Recovery ROM or any other Custom ROM to install on the phone. I have also tried the SD card method and that brought up an error as well resulting in "failed."
Any help would be appreciated as the phone as it sits right now does not have any OS on it so it is stuck on the HTC Boot up screen.
Thanks in advance for those that can help.
So I rooted my EVO 4G LTE, hurray! I have a number of questions and after some tedious searching I could not find any clear and consise answers. There is just too much info out there, even the rooting was not so easy!
So I have three main issues; 1) Bloatware 2) A stuck OTA update 3) System error messages after each reboot.
Bloatware
Using ESFileExplorer and even TitaniumBackup(free) I attempted to uninstall a number of the apps that came pre-installed and that hog RAM. Each time I reboot they come back, some attempts to uninstall apps have sent the phone straight into reboot and all the apps came right back.
I am not looking to get rid of sense, this phone is a lifeline to my livelihood and its dependability is paramount, so I would like to remain as stock as possible. I just want to free it up so that it runs a bit better and less laggy.
My task manager app shows that 0.89/1.0GB is is use and that is ridicules!
OTA Update
Sometime after rooting (this was a brand new replacement device when I started) the 3.17.651.5 update got downloaded and is now showing up all the time asking to do the actual installation. Is there any way to delete the update files and prevent the message from popping up all the time?
Reboot Error
This is just really a minor nuisance, but while we are at it I figure why not ask. After each reboot since rooting I get a System Error Message saying something like 'the phone experienced an abnormal reboot'. Any way to prevent it from doing that?
Misc
Also, I cannot seem to find any instructions (that are relevant to today, all are from 2012 and early 2013) for allowing the EVO to act as a WiFi hotspot. Any tips?
Thank you all for this great resource and in advance for all your help!
You need to S-OFF. Your system is write protected, which is why when you reboot, the apps return. I'd honestly also recommend updating to the data/media partition layout and then achieving S-OFF with Rumrunner. Once you're S-OFF, everything will work fine, and as a bonus you'll have Sense 5 .
Captain_Throwback said:
You need to S-OFF. Your system is write protected, which is why when you reboot, the apps return. I'd honestly also recommend updating to the data/media partition layout and then achieving S-OFF with Rumrunner. Once you're S-OFF, everything will work fine, and as a bonus you'll have Sense 5 .
Click to expand...
Click to collapse
I just figured the S-OFF out thanks to exhaustive Google searches, now I am seeing your post about partitions and I am not sure what you are talking about.
How do I update partitions? Do I have to do that before I use the rumrunner exploit to gain S-OFF?
webby88 said:
I just figured the S-OFF out thanks to exhaustive Google searches, now I am seeing your post about partitions and I am not sure what you are talking about.
How do I update partitions? Do I have to do that before I use the rumrunner exploit to gain S-OFF?
Click to expand...
Click to collapse
All you have to do is run the 4.13.651.4 RUU. @Magnum_Enforcer has a guide that I believe will assist you.
Captain_Throwback said:
All you have to do is run the 4.13.651.4 RUU. @Magnum_Enforcer has a guide that I believe will assist you.
Click to expand...
Click to collapse
This Post?
This will simply give me JellyBean and Sense 5? Also, will I loose root? Weren't there major problems with this update?
That's the guide he's referring to, yes. Just scroll down to the section on RUU's for more info. Link to the aforementioned RUU is at the bottom of the first post. You will lose root but you can use HTC Dev to unlock and root again, and no, there were not major problems with this update.
Magnum_Enforcer said:
That's the guide he's referring to, yes. Just scroll down to the section on RUU's for more info. Link to the aforementioned RUU is at the bottom of the first post. You will lose root but you can use HTC Dev to unlock and root again, and no, there were not major problems with this update.
Click to expand...
Click to collapse
Aha, but why did HTC pull it then?
Also, will this resolve my stuck 'update pending' issue? And will I loose data? Will my installed TWRP recovery be an issue?
webby88 said:
Aha, but why did HTC pull it then?
Also, will this resolve my stuck 'update pending' issue? And will I loose data? Will my installed TWRP recovery be an issue?
Click to expand...
Click to collapse
It was never pulled, per se, but it was never released to the masses, either. The issue was how Android 4.3 was implemented on this device-that it required a RUU instead of a traditional OTA update, which is somewhat unusual but that's how the update had to be handled due to the internal storage getting re-partitioned. Anything you have on your internal storage you'll need to back up to your computer because it will be lost when the RUU runs. Also, TWRP won't be an issue. Just reinstall the modified version from @Captain_Throwback once you've updated with the RUU (you can click on the TWRP version number in his sig & it will take you to the appropriate link).
Note that there were issues with the initial Android 4.3 updates but they were resolved with the .4 RUU, which is why I don't have links to any of the previous RUU's. The issue was with the roaming option, mostly.
Magnum_Enforcer said:
It was never pulled, per se, but it was never released to the masses, either. The issue was how Android 4.3 was implemented on this device-that it required a RUU instead of a traditional OTA update, which is somewhat unusual but that's how the update had to be handled due to the internal storage getting re-partitioned. Anything you have on your internal storage you'll need to back up to your computer because it will be lost when the RUU runs. Also, TWRP won't be an issue. Just reinstall the modified version from @Captain_Throwback once you've updated with the RUU (you can click on the TWRP version number in his sig & it will take you to the appropriate link).
Note that there were issues with the initial Android 4.3 updates but they were resolved with the .4 RUU, which is why I don't have links to any of the previous RUU's. The issue was with the roaming option, mostly.
Click to expand...
Click to collapse
Ok, I get it. Thanks for taking the time to explain this!
One more question though, I see in your post a link to 4.13.651.4, but I see another thread from @Captain_Throwback here which mentions a Odex or Deodex - what is that? And all those useful mods (battery percentage, camera shutter sound, power menu, 30 step volume etc etc), which should I use?
webby88 said:
Ok, I get it. Thanks for taking the time to explain this!
One more question though, I see in your post a link to 4.13.651.4, but I see another thread from @Captain_Throwback here which mentions a Odex or Deodex - what is that? And all those useful mods (battery percentage, camera shutter sound, power menu, 30 step volume etc etc), which should I use?
Click to expand...
Click to collapse
He has rooted odex & deodexed ROM's based off the RUU. If you want to install any mods you'll need to run the deodexed version.
I am very interested to see if it helps!!
http://phandroid.com/2015/04/09/htc-one-m9-camera-update/
Me too
AT&T Update
What happened to the AT&T update they said would be released on the 17th (today)? Has anyone else on AT&T received it yet?
rmc69 said:
What happened to the AT&T update they said would be released on the 17th (today)? Has anyone else on AT&T received it yet?
Click to expand...
Click to collapse
I've been checking all day; No word from anybody. Even searched on Twitter to see if anyone mentioned it...
I just received this email:
Camera quality improvements
Update to the HTC camera is hitting the HTC One M9
An important update will begin rolling out to the HTC One M9 camera improving the overall image quality.
Expected results are:
• Reduced blur in photos thanks to enhanced exposure times
• Increased sharpness in photos making them clear but with a less artificial feeling.
• Reduced image noise
• Improved low light performance and HDR processing
• Better Auto Exposure interface performance when tapping the screen
The camera update is included in the launch software of the Verizon and Sprint variants. The T-Mobile camera update will come in the form of a user initiated over-the-air update on April 20th with the AT&T update coming on April 21st.
verks said:
I just received this email:
The camera update is included in the launch software of the Verizon and Sprint variants. The T-Mobile camera update will come in the form of a user initiated over-the-air update on April 20th with the AT&T update coming on April 21st.
Click to expand...
Click to collapse
:good:cool! I just got that too from HTC Champions. At least we know now.
verks said:
I just received this email:
Camera quality improvements
Update to the HTC camera is hitting the HTC One M9
An important update will begin rolling out to the HTC One M9 camera improving the overall image quality.
Expected results are:
•Reduced blur in photos thanks to enhanced exposure times
•Increased sharpness in photos making them clear but with a less artificial feeling.
•Reduced image noise
•Improved low light performance and HDR processing
•Better Auto Exposure interface performance when tapping the screen
The camera update is included in the launch software of the Verizon and Sprint variants. The T-Mobile camera update will come in the form of a user initiated over-the-air update on April 20th with the AT&T update coming on April 21st.
Click to expand...
Click to collapse
Thanks
Update is available on AT&T as of now. Downloading to phone, but am sure since the phone is rooted it won't install.
dratsablive said:
Update is available on AT&T as of now. Downloading to phone, but am sure since the phone is rooted it won't install.
Click to expand...
Click to collapse
I am rooted as well, but with stock recovery... downloading the update now. Is there a way to capture the update? Maybe someone can make a flashable zip of it.
sdotagain said:
I am rooted as well, but with stock recovery... downloading the update now. Is there a way to capture the update? Maybe someone can make a flashable zip of it.
Click to expand...
Click to collapse
That's what I am hoping for.
dratsablive said:
That's what I am hoping for.
Click to expand...
Click to collapse
I take it your update didn't install?
sdotagain said:
I take it your update didn't install?
Click to expand...
Click to collapse
Nope, failed probably because I have TWRP installed.
dratsablive said:
Nope, failed probably because I have TWRP installed.
Click to expand...
Click to collapse
Mine failed as well with stock recovery so it must be because of unlocked bootloader/root
sdotagain said:
Mine failed as well with stock recovery so it must be because of unlocked bootloader/root
Click to expand...
Click to collapse
The stock recovery is needed to install the OTA, but it won't download if the system partition has been modified. Having the beta version of TWRP won't break the ability to download an OTA, but having flashed a root package or any other modification will.
navalynt said:
The stock recovery is needed to install the OTA, but it won't download if the system partition has been modified. Having the beta version of TWRP won't break the ability to download an OTA, but having flashed a root package or any other modification will.
Click to expand...
Click to collapse
Will temp unroot fix the permissions?
dratsablive said:
Will temp unroot fix the permissions?
Click to expand...
Click to collapse
Nope. Once you make the modification you're done. What you could potentially do is restore someone else's unmolested TWRP backup of the system partition. The files can be found HERE and the process can be found HERE to get you started on that path.
There are usually drivers or firmware files within the ROM that interface with the device hardware/firmware so after upgrading to the new OTA you'll want to use the stock ROM or a custom ROM based on the same OTA. If you try to backup your current ROM and restore it afterwards you may not see the benefits or you could run into some funky problems with the camera and radios.
Stock 1.32.502.31 RUU
Stock AT&T 1.32.502.31 RUU
This software upgrade available for your HTC One provides the following key enhancements:
· Camera improvements
· Thermal improvements
· Various bug fixes and improvements
This will wipe your phone and restore it back to stock (how you purchased it)
RUU_HIMA_UL_L50_SENSE70_ATT_Cingular_US_1.32.502.31_Radio_01.01_U11440221_62.05.50320G_F_release_426950_signed_2.exe
MD5: e68438231773b8d93091392844939993
How to perform the ROM Update:
1. Download and save the HTC One™ update to your PC.
2. Connect your device to your PC via the supplied USB cable.
3. If the device is not recognized by the PC, ensure you have HTC Sync Manager installed and then disconnect and reconnect the device from the USB cable.
4. Once the device is properly recognized on the PC, locate the HTC One™ ROM Update that you downloaded. Double-click on the file to launch the system update wizard.
5. Follow all of the system update wizard instructions shown on your PC.
6. Once the update is complete, click Finish in the Wizard and the device will reboot.
7. Once the device reboots, the initial setup wizard will appear.
8. Once the initial setup process is complete, the device is ready for use.
Note : If the ROM update wizard fails to recognize the device, close the wizard and then follow the steps below:
· From a powered off state, hold VOLUME DOWN while powering on the device.
· Connect the device to the PC while in this state and attempt the ROM update again.
To exit download mode manually, use the volume keys to navigate to reboot and press the POWER button to select it.
So I have an unlocked Att M9 on T-Mobile, I'm gonna assume I have to do it manually via the RUU correct?
I used the RUU Utility provided on the HTC Website. At first it appeared to fail, and I had to restart the utility. It asked to repower the phone, but I could power it down. Thought it was a soft brick. But I reran the utility and it worked. Still unlocked and S-OFF.
effortless said:
Stock AT&T 1.32.502.31 RUU
This software upgrade available for your HTC One provides the following key enhancements:
Click to expand...
Click to collapse
Application fails to run on my PC - Win8.1/64 - anyone else having the same problem?
Today I have pulled an MM Firmware-Over-The-Air update from my AT&T Galaxy S7 and uploaded the original .CFG file and my compiled .ZIP files for flashing via recovery. Download the file of your choice and place it onto your devices external storage, reboot into recovery, select "Apply Update From External Storage", search for the downloaded file, select it, click yes, and wait for the flash to complete.
Another note: As normal, this WILL NOT wipe any of your personal data. But just know that your recovery might not allow you to flash from External storage if your device is rooted, which means you will either have to completely unroot and restore dm-verity status or try flashing the file via ADB.
If you have any troubles please feel free to write below about it. If this helped you, please be sure to hit the thanks button.
To be clear, I will capture the Nougat update for this device once it is OFFICIALLY released. The update file in this thread is a MM update.
PDA Version: G930AUCU4APJ4
CSC Version: G930AATT4APJ4
--Download links--
Original .CFG File: https://mega.nz/#!D4wzSbhR!IyQKit5s0M-s4_5XbYb0sOWVePk1zcU-TJDJMffwL5A
Compiled .ZIP File: https://mega.nz/#!e0w1RaIa!SmKZ0Gr8iN7ETEUmEUdWljgGZZc_x-x_qhxvXQfUBm8
Cheers!
anyone tried to flash this that's on the unofficial Nougat (G930AUCU4BQA4)
Looking at the CSCVersion.txt File inside the ZIP shows that this is G930AATT4APJ4 for anyone wondering which version
elijahblake said:
anyone tried to flash this that's on the unofficial Nougat (G930AUCU4BQA4)
Click to expand...
Click to collapse
Note that I believe this is just an update to MM. I would expect that you'd need to get the ODIN files for the G930AATT4APJ4 build and do a full flash / wipe to this one.
thelostsoul said:
Note that I believe this is just an update to MM. I would expect that you'd need to get the ODIN files for the G930AATT4APJ4 build and do a full flash / wipe to this one.
Click to expand...
Click to collapse
Is it possible to ask you to flash the update to tell me if it truly works? If it doesn't I'll replace the files.
KingOfTheNet said:
Is it possible to ask you to flash the update to tell me if it truly works? If it doesn't I'll replace the files.
Click to expand...
Click to collapse
Sorry, I already have Nougat on my phone and I'm holding out for the official release before I start flashing again.
thelostsoul said:
Sorry, I already have Nougat on my phone and I'm holding out for the official release before I start flashing again.
Click to expand...
Click to collapse
Most likely be Spring with AT&T and their release record.
thelostsoul said:
Sorry, I already have Nougat on my phone and I'm holding out for the official release before I start flashing again.
Click to expand...
Click to collapse
It's fine, I just flashed it to mine and it's just a security patch for MM. I will capture the official Nougat FOTA release once it comes out.
4APJ4 is Old (October) the latest is 4APK1 (MM)
4=Bootloader Version
A=Marshmallow
P=2016
K=November
1=Build Number
And latest for Nougat is 4BQA6
4=Bootloader Version
B=Nougat
Q=2017
A=January
6=Build
Omar04 said:
4APJ4 is Old (October) the latest is 4APK1 (MM)
4=Bootloader Version
A=Marshmallow
P=2016
K=November
1=Build Number
And latest for Nougat is 4BQA6
4=Bootloader Version
B=Nougat
Q=2017
A=January
6=Build
Click to expand...
Click to collapse
One issue with that... qa6 is feb update...
twizt3d said:
One issue with that... qa6 is feb update...
Click to expand...
Click to collapse
Added screenshot
twizt3d said:
One issue with that... qa6 is feb update...
Click to expand...
Click to collapse
Yeap it doesnt apply for Beta they are always ahead of time only official releases match. (There's always that one build that wants to break the rules, but only happen with unreleased builds mostly because they apply the security patch early for testing and compiler gives that build code.)
It always has been that way with Samsung since the OG Galaxy S.
Check my posts from several years ago on earlier galaxies and you'll notice.
KingOfTheNet said:
Today I have pulled an MM Firmware-Over-The-Air update from my AT&T Galaxy S7 and uploaded the original .CFG file and my compiled .ZIP files for flashing via recovery. Download the file of your choice and place it onto your devices external storage, reboot into recovery, select "Apply Update From External Storage", search for the downloaded file, select it, click yes, and wait for the flash to complete.
Another note: As normal, this WILL NOT wipe any of your personal data. But just know that your recovery might not allow you to flash from External storage if your device is rooted, which means you will either have to completely unroot and restore dm-verity status or try flashing the file via ADB.
If you have any troubles please feel free to write below about it. If this helped you, please be sure to hit the thanks button.
To be clear, I will capture the Nougat update for this device once it is OFFICIALLY released. The update file in this thread is a MM update.
PDA Version: G930AUCU4APJ4
CSC Version: G930AATT4APJ4
--Download links--
Original .CFG File: https://mega.nz/#!D4wzSbhR!IyQKit5s0M-s4_5XbYb0sOWVePk1zcU-TJDJMffwL5A
Compiled .ZIP File: https://mega.nz/#!e0w1RaIa!SmKZ0Gr8iN7ETEUmEUdWljgGZZc_x-x_qhxvXQfUBm8
Cheers!
Click to expand...
Click to collapse
Can I ask you a question? how did you manage to compile .Zip file to flash from recovery? is it flashable from stock recovery? how did you manage to add original signature?
suyash1629 said:
Can I ask you a question? how did you manage to compile .Zip file to flash from recovery? is it flashable from stock recovery? how did you manage to add original signature?
Click to expand...
Click to collapse
There was no compiling. You can flash the ota update files from stock recovery after renaming the file name extension from .cfg to .zip.
suyash1629 said:
Can I ask you a question? how did you manage to compile .Zip file to flash from recovery? is it flashable from stock recovery? how did you manage to add original signature?
Click to expand...
Click to collapse
I didn't flash the update file itself, I had the ODIN files for it. They're the same thing.
When it comes to official updates, no signature modification should be necessary (Or possible, for that matter. I don't think there's a way to modify the signature. If there is, I don't know about it.). The only thing different between the 2 files is the file format.
Hope I answered your questions.
Cheers!
Can You Supply the Latest FOTA roms For.
G930AUCU4BQK2
G930AUCS4BQJ2
G930AUCS4BQH1
I have an Unlocked G930A (not really unlocked just using a cricket SIM) But I cannot Get the Software Updates For it because of AT&T. I have seen the information on reflashing it to the U software but i really dont want to have to restore everything to my phone unless i have to..
The Version currently running on my phone is vulnerable to the bluebourne exploit and im trying to get that patched. :/
On a side note. are you able to do a packet capture while scanning for the updates? There is one on the play store that will also let you perform a MITM on the application and you should be able to capture anything sent over SSL in plain text/hex/etc
I did Want to Ask you a quick question. How did you capture the FOTA package to begin with?
I wonder if it is possible to setup an Authoritative only dns server and then use it to spoof the location of the update servers. to create a DNS method that would allow the FOTA to be pushed to devices no longer on AT&T
Anywho if you can get those firmwares and get me full packet captures of just the update application while it is checking and downloading the update, i might be able to create a web application that is able to capture the headers sent by the phone that identify its model/fw version/etc and be able to push the firmware update Via the built in option in the settings, (although you may need to swap your dns settings for a moment and install a CA cert that allows validation of a connection. im not too sure if a CA cert will need to be installed because im not sure if they push the updates over a SSL/TLS connection. Using the data collected here may also pave the way to enable this to work with other models and carriers and manufacturers. (my hypothesis is that packet captures would be needed on any firmware updates "you" would want to push with this)
Basically Im thinking it might be possible to download those zip files along with the packet capture data to create a simple web application that is able to tell the phone there is a software update available. It would require using a 3rd party DNS server to "redirect" the connection to a server that doesnt care if your an at&t customer. It might also need a self signed CA cert installed into the device to Validate TLS/SSL. From there it might be possible to have the server 301 redirect the zipfile to another url that is behind a CDN to reduce the risk of ddos and keep the server(s) stable keeping the downloads reliable and fast.
Seeing how the Firmware update is already digitally signed by Samsung and/or AT&T it should probably install without an issue. I dont see the possibility of the wrong stock firmware being flashed on the wrong phone provided the manufactuer had a proper assert statement in place to verify the model and sw/hw versions, and im pretty sure a stock recovery wont accept a firmware signed by any key.
I might be Going off topic here, But one more question.
Do i actually need AT&T service to download the OTA updates from the Software update function in the phone settings.
What i mean by this is does the SIM card need to have an active plan on it? or can it just be provisioned to their network with out a phone plan and downloaded over wifi?
UPDATE: It Can Now be officially confirmed that Carriers and Samsung Deliberately block OTA updates when you unlock the device. there are thousands if not tens of thousands out there on a variety of devices as far back as the S4 that may not have been able to get updates. just because they used a Cricket Sim or unlocked the device. I also Spoke with AT&T customer support today and got told the blatant Lie that they push the same OTA updates through the cricket network to ensure that AT&T devices on it can be updates. I also went to samsung service center at bestbuy and they told me my phone was up to date when its not. Samsung Smart Switch Also Reports that my device is up to date when i know for a 900% fact it is not.
So it looks like Someone is going to have to write an app that Hijacks the Requests and replays a valid packet capture just to get the phone to update in its orignial intended built in method.
The sad part is the carriers would see this and just write a patch to prevent it rather then change their policies.
Basically The carrier has the right to deny you a software update because you left their network and leave you exposed to Critical Security Vulnerabilities.
That is their way of sticking up their Middle Finger at the FCC for mandating carriers unlock their devices and the end user who either met his/her contract obligation or outright paid for his/her device
[SARCASM] basically its like saying hey we know you paid for your device, but **** you, you left our network and even though the updates come from a samsung controlled server were going to ensure our middleware deliberately blocks your device from updating so you remain vulnerable and you information is stolen, That'l teach you for unlocking your device and leaving our network because we charge literally an arm and leg for service, how dare you as a customer go against our big monopoly that seeks to buy out every major ISP and cable provider in america but hey thats alright were still winning but because you left our network we will block these updates so we can further Sell your information and viewing browsing habits off to the NSA (Google TITANPOINTE tinfoil hatters!!!!) unless you want to send your phone off to one of our service centers where one of our butthurt technicians will see you rooted your phone and say it has damage and turn our free reflashing service into a paid repair and charge you through the ass for service, also did we mention were not going to update the software because our application is designed not to tell you there is an update available if you unlocked it or used our Subsidary cricket SIM in the device and didnt unlock it Or you can go on XDA and grab an odin package an potentially invalidate your warranty and then when your device comes to us for a cracked screen we can deny you the repair even though the modifcation wasnt a modifcation and has nothing to do with a cracked screen. [/SARCASM]
Anywho im going to Bite the Bullet and Grab an Assortment of AT&T contract Sims and Go Phone sims and Other Carriers, Im going to go to the local pawn shops and buy an assortment of devices and attempt to downgrade each and every single one of them back to their old original firmware versions, Dump all the FOTA updates and dump the packet captures and i guess i will have to research the possibility And be that asshole who gets sued for reverse engineering their software.