Hi,
Can someone help me please. I am looking for a rom for my AT&T US, HTC One M8. I'm running 4.4.2, Hboot 3.16, Radio 1.16..., and 1.58.502.1 firmware.I have the 3.4 kernel. I am unlocked, TWRP latest custom recovery, and rooted with SuperSU. I am S-On. I can't S-Off and can't update my Firmware. I need it to work in the US, so what rom can I flash that will work. When I go to Dev sites every rom I see only has the 4.4.3/4.4.4 versions with the new Firmware, for my device. When I try to flash .zip's through TWRP, Aroma gives me a success, but it auto reboots and I get stuck in boot loop... I am able to recover the stock image, but can't get a custom rom to stick. I have watched hours of videos and read hundreds of pages of threads. HELP
Thank You,
-Shane
HitShane said:
Hi,
Can someone help me please. I am looking for a rom for my AT&T US, HTC One M8. I'm running 4.4.2, Hboot 3.16, Radio 1.16..., and 1.58.502.1 firmware.I have the 3.4 kernel. I am unlocked, TWRP latest custom recovery, and rooted with SuperSU. I am S-On. I can't S-Off and can't update my Firmware. I need it to work in the US, so what rom can I flash that will work. When I go to Dev sites every rom I see only has the 4.4.3/4.4.4 versions with the new Firmware, for my device. When I try to flash .zip's through TWRP, Aroma gives me a success, but it auto reboots and I get stuck in boot loop... I am able to recover the stock image, but can't get a custom rom to stick. I have watched hours of videos and read hundreds of pages of threads. HELP
Thank You,
-Shane
Click to expand...
Click to collapse
There are 4.4.2 roms still available but your best bet is pay the $25 for sunshine s-off utility that way you can update your firmware and run whatever rom/kernel you want.
If you've tried the flash various ROMs, and they all won't boot, then the problem is not what ROM, but something else.
adb erase cache
Then, flash recovery again. Possibly re-download recovery, to make sure the file is not corrupt.
redpoint73 said:
If you've tried the flash various ROMs, and they all won't boot, then the problem is not what ROM, but something else.
adb erase cache
Then, flash recovery again. Possibly re-download recovery, to make sure the file is not corrupt.
Click to expand...
Click to collapse
^^ I did that when I rooted the phone. I used the HTCDev to unlock it. I used Fastboot and adb in cmd from my PC to install TWRP and the Recovery file and clear the cache. Should I reflash recovery again???
I have wiped and tried factory resets before installing a rom. The problem is that I can't find the download link for an old rom for my specific phone. I need the 1.58.502.1 version (Don't I ?), so that I don't have to change my Firmware through S-OFF... When I find a rom that did make one that would work on my device, they have already updated the OP download link with their latest version to run with the updated AT&T 4.4.3/4.4.4 and 2.22.1540.3.
* I have the newest TWRP installed with the 24MB Recovery.img. I have SU installed with privileges. The phone passes rooted tests. Phone is S-ON... *
iRunLinux said:
There are 4.4.2 roms still available but your best bet is pay the $25 for sunshine s-off utility that way you can update your firmware and run whatever rom/kernel you want.
Click to expand...
Click to collapse
^^I have seen even sunshine fail with the latest devices from AT&T.
?----->Does anyone have a good link to a rom that will run on my; AT&T HTC One M8 running 4.4.2 & 1.58.502.1, (1.16.21331931.LA11G)? It was bought a month ago from an AT&T store...
Thank You,
-Shane
HitShane said:
Should I reflash recovery again???
Click to expand...
Click to collapse
I just told you to adb wipe cache and flash recovery again. Why are you asking me this? A lot of issues with TWRP not flashing ROMs can be solved by wiping cache and flashing again (probably just a bad initial install).
HitShane said:
I need the 1.58.502.1 version (Don't I ?), so that I don't have to change my Firmware through S-OFF...
Click to expand...
Click to collapse
Any ROM that is not 2.xx Sense based.
I haven't checked every single thread/link, but most (if not all) 1.54 and 1.58 based Sense ROMs on my Index thread seem to be working:
http://forum.xda-developers.com/showthread.php?t=2751432
This also includes the stock rooted 1.58 ROM, if you wish to go that route.
HitShane said:
^^I have seen even sunshine fail with the latest devices from AT&T.
Click to expand...
Click to collapse
You sure? I haven't seen sunshine fail for anybody, much less AT&T, which hasn't had their software updated for sometime now. Regardless of how new the device is, its still the same 1.58 software, which is 3 months old at this point.
firewater, on the other hand is known to fail for more recent AT&T versions.
918
redpoint73 said:
I just told you to adb wipe cache and flash recovery again. Why are you asking me this? A lot of issues with TWRP not flashing ROMs can be solved by wiping cache and flashing again (probably just a bad initial install).
Any ROM that is not 2.xx Sense based.
I haven't checked every single thread/link, but most (if not all) 1.54 and 1.58 based Sense ROMs on my Index thread seem to be working:
http://forum.xda-developers.com/showthread.php?t=2751432
This also includes the stock rooted 1.58 ROM, if you wish to go that route.
You sure? I haven't seen sunshine fail for anybody, much less AT&T, which hasn't had their software updated for sometime now. Regardless of how new the device is, its still the same 1.58 software, which is 3 months old at this point.
firewater, on the other hand is known to fail for more recent AT&T versions.
Click to expand...
Click to collapse
So for instance on your Index, I followed the link to ViperOneM8 1.6.0. This takes you to the Dev page for that rom. I follow the page to downloads that directs me another page. Along the way I find out that it looks like ViperOneM8 1.8 is the last update before 2.xx. The download page only has the most recent ViperOneM8_2.2.0.zip, or they offer the OTA increments of each previous version. Those aren't large enough to be the whole rom. How do I find the legacy full roms?
-Shane
HitShane said:
So for instance on your Index, I followed the link to ViperOneM8 1.6.0. This takes you to the Dev page for that rom. I follow the page to downloads that directs me another page. Along the way I find out that it looks like ViperOneM8 1.8 is the last update before 2.xx. The download page only has the most recent ViperOneM8_2.2.0.zip, or they offer the OTA increments of each previous version. Those aren't large enough to be the whole rom. How do I find the legacy full roms?
Click to expand...
Click to collapse
I think you picked one of the few (maybe the only one) that doesn't link to an actual 1.xx ROM. Just pick any other one.
EDIT: Oh, wait InsertCoin also. Will update the Index to show those as 2.22 ROMs.
Devs usually don't keep their legacy versions posted. Most you can do is ask if another member has the zip.
redpoint73 said:
I think you picked one of the few (maybe the only one) that doesn't link to an actual 1.xx ROM. Just pick any other one.
EDIT: Oh, wait InsertCoin also. Will update the Index to show those as 2.22 ROMs.
Devs usually don't keep their legacy versions posted. Most you can do is ask if another member has the zip.
Click to expand...
Click to collapse
Thank you for all of the information. I guess the roms develop faster than I can get a phone for them It baffles me that a version for each baseline of a current device isn't listed. I guess I should flash back to the most current stock rom and wait for the OTA from AT&T. I might try the S-Off for $25, but I have seen a lot of chatter about newly bought M8 ATT devices not working. Something about them having a patch from HTC...
-Shane
Related
This is last resort. I've been at this for a while so please someone help out.
Got the phone.
Did the OTA update to Telus 1.20.661.1.
Unlocked and Rooted with AIO Toolkit.
Tryed to install a few roms to get rid of Sense (Venom XL+ 1.2.7). None worked and confirmed by others users with newer software.
Trying to get back to stock and can't do that either. Downloaded the "RUU_EVITARE_UL_JB_45_TELUS_WWE_1.15.661.11_Radio_1.09.55.17_18.20.95.55L_release_290307_signed" and get either USB or general errors 155/159
Can't figure out how to get back to an older firmware and stock rom/boot image.
Can someone please help?
HTC One X+ Telus unlocked
Soft. 1.20.661.1
kernel 3.1.10-g262c6aa
BB 2.14.55.11_18.21.95.55L
Build 1.20.661.1 CL164725
I have the same issues after the AT&T firmware update, I can't flash any ROM. The only one I can use is the stock nandroid backup.
I've tried everything with no avail.
I'll try with CWM recovery and let you know.
Sent from my HTC One X+ using Tapatalk 2
I was able to use CMW recovery and reinstall a backed up rom but since trying the RUU exe it worked just enough to wipe that so I don't have it anymore.
Where do I find a stock backup?
I'm reading in other threads that the RUU's don't work with hboot versions above 3.5. Not sure if that's why the RUU exe won't work for me or not.
Seems like very outdated files on HTCdev. Nice of them to break their last resort recovery tools and not bother updating them.
garmig said:
I have the same issues after the AT&T firmware update, I can't flash any ROM. The only one I can use is the stock nandroid backup.
I've tried everything with no avail.
I'll try with CWM recovery and let you know.
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
Did actually get it out of boot loop.
Had to catch it at a very specific position during start up to be detected long enough to flash the boot image.
Got it on the AT&T 1.19 rom now but really want to get rid of sense and get the Venom rom working. Wish I hadn't hit that upgrade button..
meboy said:
I was able to use CMW recovery and reinstall a backed up rom but since trying the RUU exe it worked just enough to wipe that so I don't have it anymore.
Where do I find a stock backup?
I'm reading in other threads that the RUU's don't work with hboot versions above 3.5. Not sure if that's why the RUU exe won't work for me or not.
Seems like very outdated files on HTCdev. Nice of them to break their last resort recovery tools and not bother updating them.
Click to expand...
Click to collapse
Because you have the new hboot, you cannot go back to an earlier rom. If you flash the rom from this thread http://forum.xda-developers.com/showthread.php?t=2235248 you should have updated stock. You will need to push the zip from the link to your phone with adb. You can then use TWRP or CWM to install rom and fastboot to flash the updated boot.img.
Thanks. I noticed others mention the hboot and RUU issue.
That's the rom I ended up getting to work. But it's stock only.
I haven't tried it yet but others are reporting that the AT&T 1.19 doesn't work with custom roms either.
artiemon said:
Because you have the new hboot, you cannot go back to an earlier rom. If you flash the rom from this thread http://forum.xda-developers.com/showthread.php?t=2235248 you should have updated stock. You will need to push the zip from the link to your phone with adb. You can then use TWRP or CWM to install rom and fastboot to flash the updated boot.img.
Click to expand...
Click to collapse
meboy said:
Thanks. I noticed others mention the hboot and RUU issue.
That's the rom I ended up getting to work. But it's stock only.
I haven't tried it yet but others are reporting that the AT&T 1.19 doesn't work with custom roms either.
Click to expand...
Click to collapse
HI, I've the AT&T's HOX+ with AT&T 1.19 boot, working with Viper+-v2.0.0; yes, with some lacks in the boot. I tested it with hxore_v1.0_ATnT.img (Kernel) and also with the embbeded in Viper, the Kernel boot-1.19.502.1, when the boot is sucess the device works fine ...
So i just got my One yesterday and it still has the .7 firmware / rom on it. I am going to root it and s-off right now, but just wondering a couple things.
1. Can or should i use an ruu to update the firmware to the more recent versions?
2. If yes, will this make me lose root or s-off? (i would imagine root would be easy enough to get back as long as i still have s-off)
thanks!!
At the moment, unless the situation has changed, there isn't an RUU for the TMo HTC One. One was released the other day, but it didn't work and HTC pulled the download. For now, I'd wait a couple of days to see if they release a fixed version. Your only other option would be to flash the .ZIP with the updated radio after going S-OFF.
Sisyphus306 said:
At the moment, unless the situation has changed, there isn't an RUU for the TMo HTC One. One was released the other day, but it didn't work and HTC pulled the download. For now, I'd wait a couple of days to see if they release a fixed version. Your only other option would be to flash the .ZIP with the updated radio after going S-OFF.
Click to expand...
Click to collapse
Ah.. ok. That makes sense. I downloaded one that was labeled for TMO, but i will just wait until it all gets sorted out. I am not to concerned about the radio, those are always easy to flash. Was wondering if there was anything else in the firmware i needed (like when the one s got jellybean there was WIFI partitions that needed to get flashed for everything to work properly)
For anyone else that is searching for this answer, here is what i ended up doing and it worked well.
My phone came with the .7 build install (this was the very first build before any updates). I rooted, and went s-off BEFORE ANY OTA's we taken. At this point i still had the original stock rom, it was just rooted. Since I always like to at least try the newest firmware out (cause you never know what benefits it may have) I flashed the STOCK TMO recovery back onto the phone.
Now you can boot into your OS, and go through the normal OTA process that you would get in any unrooted rom. Once those updates are complete you will be on the latest firmware and ROM from TMO, but no root access. Since you still are S-OFF, you have no problems here, flash TWRP back on (or CWM, i prefer TWRP) and flash whatever you want.
Hope that helps someone else that may be looking for the same answers.
frettfreak said:
For anyone else that is searching for this answer, here is what i ended up doing and it worked well.
My phone came with the .7 build install (this was the very first build before any updates). I rooted, and went s-off BEFORE ANY OTA's we taken. At this point i still had the original stock rom, it was just rooted. Since I always like to at least try the newest firmware out (cause you never know what benefits it may have) I flashed the STOCK TMO recovery back onto the phone.
Now you can boot into your OS, and go through the normal OTA process that you would get in any unrooted rom. Once those updates are complete you will be on the latest firmware and ROM from TMO, but no root access. Since you still are S-OFF, you have no problems here, flash TWRP back on (or CWM, i prefer TWRP) and flash whatever you want.
Hope that helps someone else that may be looking for the same answers.
Click to expand...
Click to collapse
Would you mind linking the T-mobile stock recovery that you flashed? I'm in about the same situation you were in.
FYI, there is a working TMOUS RUU available now, you can download it through the following link. I downloaded it yesterday and used it last night, I can confirm it works.
http://forum.xda-developers.com/showpost.php?p=43963285&postcount=9
Hi All,
I bought this refurbished AT&T unlocked HTC One from eBay. I am with T Mobile.
I already unlocked the bootloader and rooted the phone. Why I did this:
1) I wanted to remove all the AT&T stuff including their update check which doesn't work with T Mobile SIM. (But not able to do it even after uninstalling with Titanium, those just come back on restart)
2) I wanted KitKat (either like an unlocked or international HTC one or the Google Play KitKat)
But I am not sure how to proceed.
I already have downloaded a ROM from this link: htconeroot.com/htc-one-stock-roms/android-4-4-kitkat-sense-5-5-stock-rom-for-htc-one
But not sure about S-OFF/ON etc because I am a newbie, this is my second android phone and first rooting.
Can anyone give me step by step instructions to install either a google play kitkat or a pure sense 5.5 kitkat? I would prefer if I can do this just once now and get future updates automatically from google/htc.
Mine is Android 4.3 based Sense 5.0 with all the AT&T stuff. I am in the US.
There is no real difference between AT&T Kitkat and Jellybean on the One. In fact there are a few bugs with Kitkat. Such as the camera and a few others that have been posted.
njaustin123 said:
Hi All,
I bought this refurbished AT&T unlocked HTC One from eBay. I am with T Mobile.
I already unlocked the bootloader and rooted the phone. Why I did this:
1) I wanted to remove all the AT&T stuff including their update check which doesn't work with T Mobile SIM. (But not able to do it even after uninstalling with Titanium, those just come back on restart)
2) I wanted KitKat (either like an unlocked or international HTC one or the Google Play KitKat)
But I am not sure how to proceed.
I already have downloaded a ROM from this link: htconeroot.com/htc-one-stock-roms/android-4-4-kitkat-sense-5-5-stock-rom-for-htc-one
But not sure about S-OFF/ON etc because I am a newbie, this is my second android phone and first rooting.
Can anyone give me step by step instructions to install either a google play kitkat or a pure sense 5.5 kitkat? I would prefer if I can do this just once now and get future updates automatically from google/htc.
Mine is Android 4.3 based Sense 5.0 with all the AT&T stuff. I am in the US.
Click to expand...
Click to collapse
You could just try this
http://forum.xda-developers.com/showthread.php?t=2659374
I dont want AT&T again
mb_guy said:
You could just try this
http://forum.xda-developers.com/showthread.php?t=2659374
Click to expand...
Click to collapse
I dont want AT&T again.
njaustin123 said:
I dont want AT&T again.
Click to expand...
Click to collapse
I'd say switch to the Developer Edition rom, it doesn't contain all of the AT&T bloat.
1. Unlock the bootloader here.
2. S-Off via rummrunner or firewater.
3. Change CID to BS_US001 'fastboot oem writecid BS_US001'
4. Install Developer Edition 4.3 RUU, get it here.
5. Take OTA to 4.4.2.
There are guides in the One General and Q&A sections that cover all of this. Do a lot of reading, and then ask questions as needed.
Thanks. Any more Info?
cschmitt said:
I'd say switch to the Developer Edition rom, it doesn't contain all of the AT&T bloat.
1. Unlock the bootloader
2. S-Off via rummrunner or firewater.
3. Change CID to BS_US001 'fastboot oem writecid BS_US001'
4. Install Developer Edition 4.3 RUU, get it
5. Take OTA to 4.4.2.
There are guides in the One General and Q&A sections that cover all of this. Do a lot of reading, and then ask questions as needed.
Click to expand...
Click to collapse
Thanks a lot Schmitt. I think that is exactly what I have to do.
My bootloader is already unlcoked, Also I think I can handle Step 2 and Step3. Could you please pour or point me to more info on Step 4 and 5. Links to discussions here or other links will do. Being a newbie I am totally confused about stock, kernel, RUU etc.
njaustin123 said:
Could you please pour or point me to more info on Step 4 and 5. Links to discussions here or other links will do. Being a newbie I am totally confused about stock, kernel, RUU etc.
Click to expand...
Click to collapse
The RUU is easy, it is a complete software package for the phone that will restore it to the original software of the Developer Edition phones.
For the RUU to work, the CID (carrier id) must be set to BS_US001. This why you'll need to s-off the phone, so that you can change the CID.
Go to http://www.htcdev.com/devcenter/downloads and select 'Brightstar US' as the carrier, then 'Find Files' and download the 'RUU 3.22.1540.1 Developer Edition'. It is an EXE, just run it with the phone connected to the USB port of the computer and it will walk you through the install. After it reboots you will have developer edition 4.3, then update to 4.4.2 by OTA, just check in the Software Update menu in settings on the phone. It will download a file to the phone that will update it.
rumrunner didn't work
cschmitt said:
The RUU is easy, it is a complete software package for the phone that will restore it to the original software of the Developer Edition phones.
For the RUU to work, the CID (carrier id) must be set to BS_US001. This why you'll need to s-off the phone, so that you can change the CID.
.
Click to expand...
Click to collapse
rumrunner gave this error:
unfortunately this isn't going to work out with your configuration. you have 2
options:
1.) flash an unsecure kernel that's compatible with your ROM and retry rumrunner
(preferred and most reliable method).
2.) flash a different rom.
NOTE: No amount of messing around with su binaries and apk's is going to fix thi
s issue for you!!!.
njaustin123 said:
rumrunner gave this error:
unfortunately this isn't going to work out with your configuration. you have 2
options:
1.) flash an unsecure kernel that's compatible with your ROM and retry rumrunner
(preferred and most reliable method).
2.) flash a different rom.
NOTE: No amount of messing around with su binaries and apk's is going to fix thi
s issue for you!!!.
Click to expand...
Click to collapse
Flash the ElementalX kernel from here http://forum.xda-developers.com/showthread.php?p=40682393 and try again.
It's unsecured and should make rumrunner successful.
Thanks. It's S-OFF Now
cschmitt said:
Flash the ElementalX kernel from here and try again.
It's unsecured and should make rumrunner successful.
Click to expand...
Click to collapse
Thanks a lot. I did the kernel update and then S-OFF. Will try RUU tonight.
njaustin123 said:
Thanks a lot. I did the kernel update and then S-OFF. Will try RUU tonight.
Click to expand...
Click to collapse
See, this stuff is easy. You'll like the Dev Edition ROM.
In Dev Edition
cschmitt said:
See, this stuff is easy. You'll like the Dev Edition ROM.
Click to expand...
Click to collapse
Thank you again. I installed 4.3 RUU and OTAed to KitKat.
Very much satisfied and happy with it.
Some questions:
My root and custom kernel are gone. Even the TWRP recovery is lost.
Do I need to flash TWRP as recovery again? And install SU and 4.4 ElementalX again for root and getting the kernel? If yes and if I do these, will my future OTAs be blocked?
njaustin123 said:
Thank you again. I installed 4.3 RUU and OTAed to KitKat.
Very much satisfied and happy with it.
Some questions:
My root and custom kernel are gone. Even the TWRP recovery is lost.
Do I need to flash TWRP as recovery again? And install SU and 4.4 ElementalX again for root and getting the kernel? If yes and if I do these, will my future OTAs be blocked?
Click to expand...
Click to collapse
Yes
yes and Yes
you get future OTA by returning to stock first (flashing stock recovery will sometimes be all that's needed)
How do I flash stock recovery?
clsA said:
Yes
yes and Yes
you get future OTA by returning to stock first (flashing stock recovery will sometimes be all that's needed)
Click to expand...
Click to collapse
How do I flash stock recovery? If that alone doesn't work, is a complete installation with RUU the only way?
njaustin123 said:
How do I flash stock recovery? If that alone doesn't work, is a complete installation with RUU the only way?
Click to expand...
Click to collapse
Flash it using fastboot just like you would flash TWRP. The stock recovery can be pulled out of a firmware.zip.
Could not find the recovery image
cschmitt said:
Flash it using fastboot just like you would flash TWRP. The stock recovery can be pulled out of a firmware.zip.
Click to expand...
Click to collapse
I got the notification for 4.19.1540.9 update. I was about to go back to the stock recovery to update this.
But could not unzip the recovery image from the RUU zip
(PN07IMG_M7_UL_JB43_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1.zip). It was not unzippable and even after repairing it with zip_repair tool I could not get the recovery image.
Also I downloaded recovery_1.29.1540.16_R.img from another xda post. That didn't work. After giving start update, it was stuck at a red triangle with a warning sign.
njaustin123 said:
I got the notification for 4.19.1540.9 update. I was about to go back to the stock recovery to update this.
But could not unzip the recovery image from the RUU zip
(PN07IMG_M7_UL_JB43_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1.zip). It was not unzippable and even after repairing it with zip_repair tool I could not get the recovery image.
Also I downloaded recovery_1.29.1540.16_R.img from another xda post. That didn't work. After giving start update, it was stuck at a red triangle with a warning sign.
Click to expand...
Click to collapse
I think both of those recoveries are too old, you need the one for your currently installed kitkat version.
Any idea where can I get it?
mb_guy said:
I think both of those recoveries are too old, you need the one for your currently installed kitkat version.
Click to expand...
Click to collapse
Any idea where can I get it?
njaustin123 said:
Any idea where can I get it?
Click to expand...
Click to collapse
I can't find the 4.19.1540.x version but I believe any 4.19.x.x version will work.
I think the stock recovery may be in this dark bootloader firmware download .
http://www.htc1guru.com/downloads/firmware-downloads/
Get the 4.19.401.8 download and see if the recovery.img is included.
Best I can come up with for now.
No. That doesn't have it
mb_guy said:
I can't find the 4.19.1540.x version but I believe any 4.19.x.x version will work.
I think the stock recovery may be in this dark bootloader firmware download .
http://www.htc1guru.com/downloads/firmware-downloads/
Get the 4.19.401.8 download and see if the recovery.img is included.
Best I can come up with for now.
Click to expand...
Click to collapse
I just downloaded it and checked, it doesn't have the recovery.img
Just updated to the 4.4.3 OTA then rooted flashed TWRP and install Venom One ROM. Now I get that annoying message on boot. My OCD is drving me nuts! found a few tutorials about flashing fastboot, but they all seem pretty old. Not sure if theres an update or an easy to fallow tutorial using adb or an AIO software. Thanks.
Need to wait for hboot to be modded to have that removed
Wonders_Never_Cease said:
Need to wait for hboot to be modded to have that removed
Click to expand...
Click to collapse
Ah okay thanks. Wasnt sure if Hboot was universal or if it was by build.
2.23.503.2 ota? If not s-off cannot flash firmware...if s-off the hboot has been modified already. Link is located in my thread in the at&t m8 section
Wonders_Never_Cease said:
2.23.503.2 ota? If not s-off cannot flash firmware...if s-off the hboot has been modified already. Link is located in my thread in the at&t m8 section
Click to expand...
Click to collapse
I'm on build 2.22.401.5 running VenomOne rom, S-Off, rooted all the good stuff. Will your hboot mod work for mine?
if on an att device its been discussed many times to use the appropriate firmware for us devices...2.22.1540.3/.4 is latest developer edition device firmware, 2.23.502.3 is latest for att devices...imo use one of those packages @firmware instead of euro.
Wonders_Never_Cease said:
if on an att device its been discussed many times to use the appropriate firmware for us devices...2.22.1540.3/.4 is latest developer edition device firmware, 2.23.502.3 is latest for att devices...imo use one of those packages @firmware instead of euro.
Click to expand...
Click to collapse
OK and I can just install either one of those hboots over my existing one and it wont brick my phone or is this more to this?
look in the htc one m8 forum since your using a euro firmware for the modified 2.22.401.5 hboot im sure its been done...
Wonders_Never_Cease said:
look in the htc one m8 forum since your using a euro firmware for the modified 2.22.401.5 hboot im sure its been done...
Click to expand...
Click to collapse
Found it, thanks man. Gonna mess with it a little later.
CavyS said:
Just updated to the 4.4.3 OTA then rooted flashed TWRP and install Venom One ROM. Now I get that annoying message on boot. My OCD is drving me nuts! found a few tutorials about flashing fastboot, but they all seem pretty old. Not sure if theres an update or an easy to fallow tutorial using adb or an AIO software. Thanks.
Click to expand...
Click to collapse
Hey Cavy..I got a couple of questions for you, if you don't mind. Were you completely stock after taking the 4.4.3 update? I just received my update a couple of days ago and I'm thinking about taking the plunge and rooting. How did you go about rooting and flashing Venom One? Thanks for your help!
thinkhope said:
Hey Cavy..I got a couple of questions for you, if you don't mind. Were you completely stock after taking the 4.4.3 update? I just received my update a couple of days ago and I'm thinking about taking the plunge and rooting. How did you go about rooting and flashing Venom One? Thanks for your help!
Click to expand...
Click to collapse
Yeah I was completely stock after updating. To root I used the AIO toolkit found here (http://forum.xda-developers.com/showthread.php?t=2699065) Once youre rooted reboot into recovery and make a backup. Then download the ViperOne rom here (http://venomroms.com/htc-one-m8/) copy the zip folder onto your SD or internal storage and reboot into recovery again and flash the ViperOne zip folder.
CavyS said:
Yeah I was completely stock after updating. To root I used the AIO toolkit found here (http://forum.xda-developers.com/showthread.php?t=2699065) Once youre rooted reboot into recovery and make a backup. Then download the ViperOne rom here (http://venomroms.com/htc-one-m8/) copy the zip folder onto your SD or internal storage and reboot into recovery again and flash the ViperOne zip folder.
Click to expand...
Click to collapse
You don't need to root if you are going to flash a custom ROM right away. Unlock bootloader, install custom recovery, then put the custom ROM on the phone and flash it.
So the toolkit still works?? Thought I read somewhere the 4.4.3 patched something. Are you also S-OFF??
Sent from my HTC One_M8 using XDA Free mobile app
redpoint73 said:
You don't need to root if you are going to flash a custom ROM right away. Unlock bootloader, install custom recovery, then put the custom ROM on the phone and flash it.
Click to expand...
Click to collapse
It was just easier for me to fallow a set of instructions going step by step than jumping around just to avoid 1 easy step.
thinkhope said:
So the toolkit still works?? Thought I read somewhere the 4.4.3 patched something. Are you also S-OFF??
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah still works, you might of read that Firewater for some people doesnt work on 4.4.3. For me Firewater worked and I'm S-Off for some people it doesnt and you have to use Sunshine in that case.
thinkhope said:
So the toolkit still works??
Click to expand...
Click to collapse
I highly recommend doing it manually and steering clear of toolkits. Using a toolkit robs you of an important learning opportunity, and leaves you with little understanding of the processes. Skills and knowledge that are important when things don't go quite right (which will inevitably happen).
redpoint73 said:
I highly recommend doing it manually and steering clear of toolkits. Using a toolkit robs you of an important learning opportunity, and leaves you with little understanding of the processes. Skills and knowledge that are important when things don't go quite right (which will inevitably happen).
Click to expand...
Click to collapse
I agree and that's the route I'm trying to take, however just need a bit more of a solid guide to lean on. I haven't messed around with adb or pushed anything via fastboot since my One X. Don't want to end up with a fancy paper weight.
Sent from my HTC One_M8 using XDA Free mobile app
thinkhope said:
I agree and that's the route I'm trying to take, however just need a bit more of a solid guide to lean on. I haven't messed around with adb or pushed anything via fastboot since my One X. Don't want to end up with a fancy paper weight.
Click to expand...
Click to collapse
If you did it on your One X, its really not any different on the M8. Actually, probably a good deal easier if you had the AT&T One X (EVITA), since that phone required temp root and SuperCID to unlock the bootloader, for the most part.
In short:
-Go to HTCDev.com to unlock the bootloader. The website walks you though step-by-step, so there is really nothing to that part.
- Use adb to flash your recovery of choice (TWRP or CWM)
- Flash SU/SuperSU or flash a custom ROM
-S-off, if you want
- That's it!
redpoint73 said:
If you did it on your One X, its really not any different on the M8. Actually, probably a good deal easier if you had the AT&T One X (EVITA), since that phone required temp root and SuperCID to unlock the bootloader, for the most part.
In short:
-Go to HTCDev.com to unlock the bootloader. The website walks you though step-by-step, so there is really nothing to that part.
- Use adb to flash your recovery of choice (TWRP or CWM)
- Flash SU/SuperSU or flash a custom ROM
-S-off, if you want
- That's it!
Click to expand...
Click to collapse
I definitely did have the evita. Had to alter the cid to make htc dev believe it was a different phone or something like that, if I remember correctly.
S-ON really is only if I want to mess with different radios, right? All I want is xposed and and maybe some cm 11 or gpe once Android L is out.
Well, sounds easy enough. I will be attempting later tonight after work. Thanks for all of your help. If it's OK, mind if I PM you if something goes wrong?
Sent from my HTC One_M8 using XDA Free mobile app
thinkhope said:
S-ON really is only if I want to mess with different radios, right? All I want is xposed and and maybe some cm 11 or gpe once Android L is out.
Click to expand...
Click to collapse
S-off is needed to flash radio, hboot, SIM unlock, and some other things. But not for root or to flash ROMs. Pretty much similar to how things were on the EVITA; with the exception that boot.img will flash automatically along with the ROM (not possible on most hboots on the EVITA, and had to be flashed manually with fastboot).
It sounds like you are already on the "official" 2.23 software (Android 4.4.3) by OTA? If so, you don't need to update firmware (radio, hboot, etc.) as the OTA already updated it. Otherwise, s-off is needed to flash the firmware manually; which is pretty much required for any 2.xx Sense based custom ROMs (otherwise there will be serious bugs like very long boot times, broken WiFi, Bluetooth). While s-off is not strictly needed to flash the ROM (it will flash correctly) things just won't run right if firmware is outdated. This is the only reason you would "need" to have s-off for flashing ROMs. AOSP and GPE ROMs won't suffer this issue.
But if you are already on the new OTA, this isn't an issue for flashing any ROM. You can verify by looking at the hboot version and baseband. If you are on hboot 3.18 and baseband 1.19; your firmware is up to date, and won't be an issue for running any ROMs.
thinkhope said:
mind if I PM you if something goes wrong?
Click to expand...
Click to collapse
I actually prefer you just posting to the forums. Either to an existing relevant thread, or start a new one if a relevant one does not already exist.
Couple reasons for this:
- Info given to you can help others reading the forums, and benefit the community as a whole instead of being hidden away in PM
- You can get help from more than just one user. I don't claim to even remotely know everything, and often its helpful to have more than one set of eyes on a problem (especially the tougher ones). And I might not even be online to help.
In particular for the 2nd point: my wife and I are going to be having a baby, with scheduled induction tomorrow (Sept. 5) unless it happens by itself sooner. So I won't be available to help you when that happens, anyway!
In any case, good luck!
I tried to s-off my Desire 601 using rumrunner unde ubuntu and I received tis message:
unfortunately this isn't going to work out with your configuration. you have 2 options:
1.) flash an unsecure kernel that's compatible with your ROM and retry rumrunner (preferred and most reliable method).
2.) flash a different rom.
NOTE: No amount of messing around with su binaries and apk's is going to fix this issue for you!!!.
Better luck next time!!!!bye
When I enter in recovery apears S-OFF, but the phone restarting at the HTC logo.
Where can I find unsecure kernel or differnt room?
boot into recovery and select "mount" then select "system" then select "file manager" and go to /system/bin/hcheck and delete or rename "hcheck" then reboot
Thank you! You save my day!
Another issue now.
I've instaled Lyberty kernel and the only rom working is ClockWorkSenseless. Antoher rom's put the phone in bootloop and I cant do anything. The /system/bin folder is empty.
I want to go back to stock kernel and rom. How can i do that?
I'm on 4.2.2 S-off twrp 2.8.0.2
L.E. Solved. TWRP 2.8.0.2 was the problem. I put 2.7.0.0 and now I can see all the files.
What's means this message?
This build is for
development purposes
only Do not distribute outside of
HTC without HTC's written permission.
Failure to comply may lead to legal action
blue74lion said:
What's means this message?
This build is for
development purposes
only Do not distribute outside of
HTC without HTC's written permission.
Failure to comply may lead to legal action
Click to expand...
Click to collapse
It's hTC's standard message on S-OFF devices.
I have a thread going for removing that red text, but it's only got hboots from the 4.4.4 OTA.
If you want to remove it you can follow the instructions in post 2 of this thread which help you with saving your OTA zip if you plan to update to to 4.4.4 (only need to save it if your carrier's version isn't there already) or dump your current hboot if you plan on staying on 4.2.2.
blue74lion said:
Another issue now.
I've instaled Lyberty kernel and the only rom working is ClockWorkSenseless. Antoher rom's put the phone in bootloop and I cant do anything. The /system/bin folder is empty.
I want to go back to stock kernel and rom. How can i do that?
I'm on 4.2.2 S-off twrp 2.8.0.2
L.E. Solved. TWRP 2.8.0.2 was the problem. I put 2.7.0.0 and now I can see all the files.
Click to expand...
Click to collapse
Also, not sure where/why you got 2.7.0.0 on there, but as of 10/22 2.8.1.0 is the official version. Yes, the version of TWRP posted here on XDA is for KitKat devices, but the official builds from their website work fine on JB (4.2.2) devices.
I've tried to update to 4.4.2, but something is missing me. OTA didnt find nothing. What are the steps to following to update?
Software number is 1.10.401.8
Kernel version 3.4.10-g31cb4f3
Zara_UL pvt ship s-off
CID-VODAP021
HBOOT-2.20.0000
Flash a stock kernel via fastboot and flash a stock rom via twrp
Child's Play said:
Flash a stock kernel via fastboot and flash a stock rom via twrp
Click to expand...
Click to collapse
You'll also need to flash stock recovery.
-Duir- said:
You'll also need to flash stock recovery.
Click to expand...
Click to collapse
No he wanted to go back to a stock kernel and rom
Child's Play said:
No he wanted to go back to a stock kernel and rom
Click to expand...
Click to collapse
Oh, I thought what you posted was in response to getting the OTA update to work.
Still no working to update to 4.4.2. I followed this steps to back to stock:
http://forum.xda-developers.com/showpost.php?p=55850035&postcount=23
Can be an issue that my phone has CID Vodafone Australia and the stock is for Europe?