Hi All,
I'm not sure if i messed up my phone or not by updating to ARHD 11.1
I had to flash something on the phone as I was going overseas. I unlocked the phone from network but the APN was still attached to ATT cell towers
Current Problems:
- No Vibrations few weeks after flashing ARHD (checked/unchecked and restarted the haptic feedback or when it rings)
- Slow Startup when restarting (power ON/OFF is fine)
- Restarting phone will have red text that says "This version is for Developing Purposes only...."
- No Music on Google Play Music or Music application
The procedure I took goes as follows:
1. Unlocked bootloader
2. Flashed TWRP recovery
3. Flashed ARHD 11.1 ROM
4. Originally ATT phone but selected International Generic ROM
***didn't flash a new firmware before flashing ROM?***
I flashed from ATT Stock 4.2 > 4.4.3
Currently I am:
Android: 4.4.3 S-ON
Baseband: 1.16.21331931
Build Number: 2.22.401.5
Can someone show me step by step of how I should revert the process and get ARHD working on my phone again?
Slow boot is a known issue if you didn't update the firmware and using a 2.x Sense ROM.
Since you are s-on, one way to update is to relock the bootloader and RUU to 2.23. You will then need to unlock the bootloader again and re-install custom recovery (and your desire custom ROM).
No sound in some apps is known issue if you picked the Harmon Kardon mod, and do not have the corresponding firmware. Easiest way around this is to just re-flash the ROM and do not pick the HK mod. If you didn't pick HK, it might be another symptom of the outdated firmware issue described above.
The red text on the boot screen is normal on a modded phone. It will appear once you have a custom recovery installed. You can either just live with it; or s-off an flash a modified hboot to get rid if the red text.
redpoint73 said:
Slow boot is a known issue if you didn't update the firmware and using a 2.x Sense ROM.
Since you are s-on, one way to update is to relock the bootloader and RUU to 2.23. You will then need to unlock the bootloader again and re-install custom recovery (and your desire custom ROM).
No sound in some apps is known issue if you picked the Harmon Kardon mod, and do not have the corresponding firmware. Easiest way around this is to just re-flash the ROM and do not pick the HK mod. If you didn't pick HK, it might be another symptom of the outdated firmware issue described above.
The red text on the boot screen is normal on a modded phone. It will appear once you have a custom recovery installed. You can either just live with it; or s-off an flash a modified hboot to get rid if the red text.
Click to expand...
Click to collapse
Thanks for the help. My vibration came back....dont exactly know how but I just kept tapping on the bottom part of the phone
So, I can relock bootloader and use RUU even if I am S-ON?
Is there a guide I should be following?
@oogierule
Google search,Google Now is one option you can use to find guides with the right key words
fastboot oem lock will relock your bootloader.
oogierule said:
Thanks for the help. My vibration came back....dont exactly know how but I just kept tapping on the bottom part of the phone
So, I can relock bootloader and use RUU even if I am S-ON?
Is there a guide I should be following?
Click to expand...
Click to collapse
oogierule said:
So, I can relock bootloader and use RUU even if I am S-ON?
Click to expand...
Click to collapse
Of course, why else would I have stated exactly that in my previous post?
In fact, s-on is the only thing that makes this a requirement. With s-on, you don't need to relock to RUU.
redpoint73 said:
Slow boot is a known issue if you didn't update the firmware and using a 2.x Sense ROM.
Since you are s-on, one way to update is to relock the bootloader and RUU to 2.23. You will then need to unlock the bootloader again and re-install custom recovery (and your desire custom ROM).
No sound in some apps is known issue if you picked the Harmon Kardon mod, and do not have the corresponding firmware. Easiest way around this is to just re-flash the ROM and do not pick the HK mod. If you didn't pick HK, it might be another symptom of the outdated firmware issue described above.
The red text on the boot screen is normal on a modded phone. It will appear once you have a custom recovery installed. You can either just live with it; or s-off an flash a modified hboot to get rid if the red text.
Click to expand...
Click to collapse
Would i need to RUU back to 1.58 first and then RUU to 2.23? or would i be able to RUU to 2.23 directly from my custom ROM?
oogierule said:
Would i need to RUU back to 1.58 first and then RUU to 2.23? or would i be able to RUU to 2.23 directly from my custom ROM?
Click to expand...
Click to collapse
You can just run the 2.23 RUU. RUU is a complete image, and therefore they do not need to be installed "sequentially".
This is in direct contrast to OTAs, which are not always a complete image, and typically need to be installed in proper sequence.
Related
i've been wondering if anyone else has been having any issues with mean rom ics, i've flashed it twice, and even done a full wipe and everything. but it seems every time i restart (or the phone powers down) i go through about 6 - 10 crashes before it can run stable enough for me to use it at all. has anyone else had this issue or have this issue and can shed any light on what could be causing it?
Strange. Are you s-on or s-off?
Read, Search, Read again, ... Then Ask with Tapatalk 2
Im s-off via Juopunutbear. My phone came with bootloader 1.50 but I updated for ics using what was posted Here, so I could retain s-off
I was having some odd things happen when I first moved to MeanROM 2.6 as well so I flashed the 2.89 RUU when it became available to make sure that the software and firmware were completely in sync. That's pretty easy to do if you are S-OFF since all you have to do is connect your phone to a Windows PC and run the RUU.exe, then flash a custom recovery and optionally a different bootloader.
Things seem to be a little smoother for me after flashing the 2.89 RUU as a base.
ramjet73
ramjet73 said:
I was having some odd things happen when I first moved to MeanROM 2.6 as well so I flashed the 2.89 RUU when it became available to make sure that the software and firmware were completely in sync. That's pretty easy to do if you are S-OFF since all you have to do is connect your phone to a Windows PC and run the RUU.exe, then flash a custom recovery and optionally a different bootloader.
Things seem to be a little smoother for me after flashing the 2.89 RUU as a base.
ramjet73
Click to expand...
Click to collapse
but isn't flashing via bootloader the firmware bits doing (the long-ish way) the same thing as what the RUU would do? I'm still on the stock HTC bootloader for 1.58 because i was updated to it from the firmware bits, but if the RUU does something extra then maybe i would benefit from flashing with it. but i mean i also have MIUI 2.8.17 and i installed it (after i was able to use my phone) through boot manager a few weeks after installing MeanROM and booting to it yields me no issues of crashing or anything. do note its based off (supposedly) the GSM port for the E3D as well as files from the sprint/htc ICS release
AlexxSeven said:
but isn't flashing via bootloader the firmware bits doing (the long-ish way) the same thing as what the RUU would do? I'm still on the stock HTC bootloader for 1.58 because i was updated to it from the firmware bits, but if the RUU does something extra then maybe i would benefit from flashing with it. but i mean i also have MIUI 2.8.17 and i installed it (after i was able to use my phone) through boot manager a few weeks after installing MeanROM and booting to it yields me no issues of crashing or anything. do note its based off (supposedly) the GSM port for the E3D as well as files from the sprint/htc ICS release
Click to expand...
Click to collapse
There's no guaranty that flashing the RUU will fix anything but it did seem to help on my phone. The RUU flashes both the stock ROM and all the firmware, including the bootloader, so it makes your phone 100% stock except for the S-ON/S-OFF radio security and bootloader locked/unlocked status. It won't change either of those, but you must have your bootloader locked (or relocked) to run the RUU if S-ON.
After running the RUU.exe you can flash a custom recovery and bootloader if you want. It should be the same as returning to stock and taking the OTA update, but flashing the RUU.exe is faster and easier.
ramjet73
Hboot 1.5 s-on and I'm running meanrom ICS 2.6 .
I did the HTC unlock. Then installed Su zip from this site. Then I installed 4ext and rebooted into recovery...flashed the meanrom zip (it flashed the kernel that comes w the Rom ) and that was it. Now I'm on sw 2.89 build w the 3.0.16 kernel and like I said still s off and hboot 1.5
If anyone knows any where to get a kernel to overclock please let me know
Sent from my PG86100 using xda app-developers app
ramjet73 said:
There's no guaranty that flashing the RUU will fix anything but it did seem to help on my phone. The RUU flashes both the stock ROM and all the firmware, including the bootloader, so it makes your phone 100% stock except for the S-ON/S-OFF radio security and bootloader locked/unlocked status. It won't change either of those, but you must have your bootloader locked (or relocked) to run the RUU if S-ON.
After running the RUU.exe you can flash a custom recovery and bootloader if you want. It should be the same as returning to stock and taking the OTA update, but flashing the RUU.exe is faster and easier.
ramjet73
Click to expand...
Click to collapse
i actually decided to give it a try after making a nand backup ofc, and still had the same issues :s after re-flashing from my backup though it seems to boot fairly stable now. even between switching roms im not sure exactly why but could it have been an issue with anything that is permanent between any rom?
Hi I need to take my phone in for repair and want to revert to Sprint's stock ICS, however I am on the engineering hboot 1.04 and don't want to lose that. I have flashed the OTA ROM from here (http://forum.xda-developers.com/showthread.php?t=1808150) but I am boot looping due to the kernel. Can anyone point me to a compatible flashable kernel?
And as a follow up, if I were to flash directly to Sprints current OTA, is it possible to downgrade all the way back to HBOOT 1.04?
daviderickson said:
Hi I need to take my phone in for repair and want to revert to Sprint's stock ICS, however I am on the engineering hboot 1.04 and don't want to lose that. I have flashed the OTA ROM from here (http://forum.xda-developers.com/showthread.php?t=1808150) but I am boot looping due to the kernel. Can anyone point me to a compatible flashable kernel?
Click to expand...
Click to collapse
The reason you are boot looping is because that ROM requires bootloader (hboot) 1.58, which is part of the updated 2.89.651.2 firmware. You can either flash the firmware from the OP of that thread, or reset everything to 100% stock by downloading the Sprint ICS RUU from here and flashing it from Windows.
Your radio status will stay S-OFF, and you can easily flash any bootloader you want from the stock bootloader once you get your phone back.
ramjet73
ramjet73 said:
The reason you are boot looping is because that ROM requires bootloader (hboot) 1.58, which is part of the updated 2.89.651.2 firmware. You can either flash the firmware from the OP of that thread, or reset everything to 100% stock by downloading the Sprint ICS RUU from here and flashing it from Windows.
Your radio status will stay S-OFF, and you can easily flash any bootloader you want from the stock bootloader once you get your phone back.
ramjet73
Click to expand...
Click to collapse
Thanks ramjet- And this won't require me having to go through HTC's unlock procedure right?
daviderickson said:
Thanks ramjet- And this won't require me having to go through HTC's unlock procedure right?
Click to expand...
Click to collapse
That's correct.
As long as you are S-OFF now and don't set S-ON before bringing the phone in for service, you can flash whatever bootloader you want after you get your phone back and then flash any ROM/kernel combination that works with that hboot.
Of course, S-ON could be set by whoever works on your phone, but I've never heard of that happening and the wire trick is pretty easy if you should need to get S-OFF again.
ramjet73
Hey ramjet-
I just got my phone back from repair, it is still listed as S-OFF, but is listed as locked. Since this seems to be a somewhat unique starting point compared to other threads, what is the procedure to go from S-OFF/locked to another hboot? Do I just pick an arbitrary RUU and flash with it?
daviderickson said:
Hey ramjet-
I just got my phone back from repair, it is still listed as S-OFF, but is listed as locked. Since this seems to be a somewhat unique starting point compared to other threads, what is the procedure to go from S-OFF/locked to another hboot? Do I just pick an arbitrary RUU and flash with it?
Click to expand...
Click to collapse
It's good that it has the bootloader locked because that's the stock status and you don't need it unlocked if you have S-OFF. However, if you want to run fastboot commands like "flash", "erase" and "boot" from a PC you need to flash a custom bootloader, then you can flash a custom recovery after that using the "fastboot flash recovery recovery.img" command. Your bootloader status will still be "locked" but the custom hboots ignore that status and run the fastboot commands anyway.
This post explains how to select and flash a different hboot when you are S-OFF.
ramjet73
Thanks for the pointer, I was able to flash back to 1.04 ENG, and get 4ext back installed. Is there any particular reason to run a newer hboot like Jbear's 1.58 other than if needed for kernel/ROM compatibility?
daviderickson said:
Thanks for the pointer, I was able to flash back to 1.04 ENG, and get 4ext back installed. Is there any particular reason to run a newer hboot like Jbear's 1.58 other than if needed for kernel/ROM compatibility?
Click to expand...
Click to collapse
No. Only if you want to run the ROM's that require it like coolexe's Cool ICS and Virus's Viper3D. The thread I linked on bootloaders gives a lot more detail on compatibility with different types of ROM's.
ramjet73
i bought the m8 on att froma guy on craigslist i cant figure out how to unroot it ive tried installing skydragon a maximus but i cant get pass the htc boot screen ive tried updating the twrp to the newest and no i dont have a recovery ive even tried downgrading to an older one any help?? edit!! i cant get pass the boot screen i had cwm and tried installing stock att firmware please help
Jduncan312 said:
i bought the m8 on att froma guy on craigslist i cant figure out how to unroot it ive tried installing skydragon a maximus but i cant get pass the htc boot screen ive tried updating the twrp to the newest and no i dont have a recovery ive even tried downgrading to an older one any help?? edit!! i cant get pass the boot screen i had cwm and tried installing stock att firmware please help
Click to expand...
Click to collapse
What does your heart really want? Do you want to run custom ROMs and have root or not? It mostly sounds like you may want to return to stock due to lack of understanding and knowledge. That's okay if you want to do that. But kinda against the spirit of XDA!
Relock the bootloader and RUU will return the phone to stock and unrooted.
But it just sounds like you have mismatched firmware (results in long boot times with no boot animation, which some folks mistake for it not being booted).
Also, the newest TWRP require updated hboot, so that is probably the problem there.
If you want the phone rooted, and running a custom ROM: either run a ROM that corresponds with your firmware, or s-off and update your firmware.
What hboot and radio numbers? S-on or S-off?
redpoint73 said:
What does your heart really want? Do you want to run custom ROMs and have root or not? It mostly sounds like you may want to return to stock due to lack of understanding and knowledge. That's okay if you want to do that. But kinda against the spirit of XDA!
Relock the bootloader and RUU will return the phone to stock and unrooted.
But it just sounds like you have mismatched firmware (results in long boot times with no boot animation, which some folks mistake for it not being booted).
Also, the newest TWRP require updated hboot, so that is probably the problem there.
If you want the phone rooted, and running a custom ROM: either run a ROM that corresponds with your firmware, or s-off and update your firmware.
What hboot and radio numbers? S-on or S-off?
Click to expand...
Click to collapse
my hboot is 3.16.0 not sure about the s on and off thing but yeah iw ould love to run roms on it I tried downloading the skydragon 5.0.1 on it but it was stuck at the boot screen im using clockwork mod but I cant get twrp back on because I cant boot into the phone and ive tried everything to install the drivers and ive tried to manually install them also but no luck if you can email me or something to help me out it would be great!! [email protected]
Jduncan312 said:
my hboot is 3.16.0 not sure about the s on and off thing but yeah iw ould love to run roms on it I tried downloading the skydragon 5.0.1 on it but it was stuck at the boot screen im using clockwork mod but I cant get twrp back on because I cant boot into the phone and ive tried everything to install the drivers and ive tried to manually install them also but no luck if you can email me or something to help me out it would be great!! [email protected]
Click to expand...
Click to collapse
Holy run-on sentence! Seriously, please take the time to type a proper response with punctuation. Making it easier to read, makes it easier for me to help you. And that is what you want, isn't it???
I don't use my personal email for this type of support. That is what these forums are for.
Skydragon is probably not "stuck" but rather taking an extremely long time to boot (10+ minutes) with no boot animation, which often leads folks to believe its stuck altogether. If you leave it alone, it will probably boot eventually, but you may also find that WiFi is broken. Both are symptoms of the wrong firmware for the ROM you flashed.
Your hboot number also indicates that you don't have the right firmware installed, as firmware includes hboot as well as radio, WiFi, Bluetooth, and other modules.
On the AT&T variant, you will not have any "official" way to update the firmware to anything more up-to-date than 2.x firmware (hboot 3.17). You need 4.x firmware (hboot 3.19) to run the ROM you mentioned. Therefore you need s-off by sunshine (if not s-off already).
You can check s-on or s-off by booting into bootloader, and you will see it says one of the other near the top of the screen.
Alternately, if you don't s-off, you can flash a ROM that corresponds to your firmware. Try the following ROM, but putting the ROM zip on a removable SD card using a card reader connected to your computer (if you have those available). Then boot into recovery,navigate to the file and flash: http://forum.xda-developers.com/showthread.php?t=2705640
Aside from that, you should really get your USB connectivity issue sorted out. You can't do much without it. Verify no response when you type fastboot devices when the phone is in fastboot mode. If it doesn't respond (should return device ID) then try a different USB cable, and different USB port. If on Windows, try going to Device Manager, finding the phone, and pick the option to manually select the drivers, than pick the USB MTP drivers (not the HTC ones). This will often fix adb/fastboot connectivity issues.
Ok I unlocked my loader, then i think what happend was clockwerk installed its self to the boot partition so i was stuck in a loop. I used One_M8_All-In-One_Kit_v to flash a new recovery lower version at that and now i do have a bootable recovery. Problem is now i didn't backup like a dumb arse my working OS and flashed a bad one or maybe the radio or some crap needed to be done first since it was going from 4.4.2 to 5+. In short all i have is recovery and sideload and every rom i download fails to sideload on the phone side and says sucessful on the pc cmd window. Need help with this please
Darthdiddy said:
Ok I unlocked my loader, then i think what happend was clockwerk installed its self to the boot partition so i was stuck in a loop. I used One_M8_All-In-One_Kit_v to flash a new recovery lower version at that and now i do have a bootable recovery. Problem is now i didn't backup like a dumb arse my working OS and flashed a bad one or maybe the radio or some crap needed to be done first since it was going from 4.4.2 to 5+. In short all i have is recovery and sideload and every rom i download fails to sideload on the phone side and says sucessful on the pc cmd window. Need help with this please
Click to expand...
Click to collapse
Wipe data, cache, dalvik, put the appropriate ROM for your carrier/build on SD card or root of internal storage and flash. All else fails run an RUU, bring you back to 100% stock then you can properly reinstall the custom recovery of your choice.
CavyS said:
Wipe data, cache, dalvik, put the appropriate ROM for your carrier/build on SD card or root of internal storage and flash. All else fails run an RUU, bring you back to 100% stock then you can properly reinstall the custom recovery of your choice.
Click to expand...
Click to collapse
I do the proper wipe before flashing my new rom, i'm under the AT&T HTC One M8 section i believe my phone was only @ 4.4.2 before this and here is the bootloader info is :
***Tampered***
***Unlocked***
M8_UL_CA_ PVT SHIP S-On
HBOOT-3.16.0.0000
RADIO-1.16.21331931.LA11G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Apr 18 2014,16:06:33.22985
Tried cm-12-20150131-NIGHTLY-m8 it fails to flash and its on the sd and internal. SkyDragon M8 Sense Rom installs but doesn't boot (tried 2 versions of this rom 700mb and a 1.6gb), believe i tried a couple other roms in my phones section there's only like 9 of them there. I have the stock RUU but fails to detect the phone and fails i think it's meant to sense a turned on functional phone i don't see any kind of recovery method with the stock ruu. All i want is a rom to work with Straight talk the stock os even being unlocked and rooted with su still shoved the default APN down my throat(I even paid 2.99$ for the SQLlite and deleted all other APNs still won't let me check off a APN profile i created as default) making my signal on ST flakey and couldn't get mms to work just picture txting wasn't working. So i went full on like my old HTC One X but dived head first too fast didn't backup my old OS and didn't know firewater was gone till i was at that step of the procedure and it was too late Oh and using TWRP 2.7.1.0 it's the highest i can use before it won't boot.
Darthdiddy said:
I do the proper wipe before flashing my new rom, i'm under the AT&T HTC One M8 section i believe my phone was only @ 4.4.2 before this and here is the bootloader info is :
***Tampered***
***Unlocked***
M8_UL_CA_ PVT SHIP S-On
HBOOT-3.16.0.0000
RADIO-1.16.21331931.LA11G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Apr 18 2014,16:06:33.22985
Tried cm-12-20150131-NIGHTLY-m8 it fails to flash and its on the sd and internal. SkyDragon M8 Sense Rom installs but doesn't boot (tried 2 versions of this rom 700mb and a 1.6gb), believe i tried a couple other roms in my phones section there's only like 9 of them there. I have the stock RUU but fails to detect the phone and fails i think it's meant to sense a turned on functional phone i don't see any kind of recovery method with the stock ruu. All i want is a rom to work with Straight talk the stock os even being unlocked and rooted with su still shoved the default APN down my throat(I even paid 2.99$ for the SQLlite and deleted all other APNs still won't let me check off a APN profile i created as default) making my signal on ST flakey and couldn't get mms to work just picture txting wasn't working. So i went full on like my old HTC One X but dived head first too fast didn't backup my old OS and didn't know firewater was gone till i was at that step of the procedure and it was too late Oh and using TWRP 2.7.1.0 it's the highest i can use before it won't boot.
Click to expand...
Click to collapse
Boot into fastboot, check device manager (if youre on windows) for any unknown drivers and install them if you can. Then run the RUU I posted here http://forum.xda-developers.com/att-htc-one-m8/help/100-stock-4-4-4-ruu-t3017594 which would update you to 4.4.4.
CavyS said:
Boot into fastboot, check device manager (if youre on windows) for any unknown drivers and install them if you can. Then run the RUU I posted here http://forum.xda-developers.com/att-htc-one-m8/help/100-stock-4-4-4-ruu-t3017594 which would update you to 4.4.4.
Click to expand...
Click to collapse
Ok TY i'll try that soon as it downloads, i did finally get RUU_M8_UL_K44_SENSE60_ATT_SECURITY_Cingular_US_1.58.502.1_Radio_1.16.21331931.LA11G_20.31A.4145.02L_release_368350_signed_2
To see the phone and no progress bar shows up on the phone and the program errors out, i even did a full system wipe before i tried it again still to no avail.
CavyS said:
Boot into fastboot, check device manager (if youre on windows) for any unknown drivers and install them if you can. Then run the RUU I posted here http://forum.xda-developers.com/att-htc-one-m8/help/100-stock-4-4-4-ruu-t3017594 which would update you to 4.4.4.
Click to expand...
Click to collapse
Ok tried that stock ruu and it failed i did finally get the phone running on a badseed rom based on 4.4.2 all seems to be working now except i can't send pictures in texts but regular text, calls, and internet work seems to be a common problem with straight talk. So new problem probably a thread somewhere on here about it i'll take a look, thank you for the help
Darthdiddy said:
Ok tried that stock ruu and it failed i did finally get the phone running on a badseed rom based on 4.4.2 all seems to be working now except i can't send pictures in texts but regular text, calls, and internet work seems to be a common problem with straight talk. So new problem probably a thread somewhere on here about it i'll take a look, thank you for the help
Click to expand...
Click to collapse
You'll have to setup your APN and mms message size settings for straight talk, that should fix the text messaging problems.
CavyS said:
You'll have to setup your APN and mms message size settings for straight talk, that should fix the text messaging problems.
Click to expand...
Click to collapse
No matter what message app i try i can't send pictures or large txts my mms is borked and to make matters worse when i installed this rom i must of removed the stock HTC messaging app so i can't find any settings to set the mms size limits. I'd like to figure out how to put the stock messaging app back on the phone without redoing the whole OS
Using Handcent and hangouts and i see no size limit options within the apps or anywhere in the phone settings. Looked up my phone specifically and where the option/s is supposed to be the said section of options is not even there.
If you've got a stock rom downloaded to your computer or sd card you can unzip it and look in system app folder and find the htc messaging apks. Then just install them as system apps and fix permissions.
Sent from my HTC One_M8 using XDA Free mobile app
Before i try and fix my obvious other problems does anyone know how to fix a bad flash of TWRP? I'm used to just adb command line flashing it and never had a issue before on my HTC One X, but seems it a was bad idea and it landed on boot partition and is causing glitches. is there a stock boot i can flash or what do i need?
Darthdiddy said:
but seems it a was bad idea and it landed on boot partition and is causing glitches.?
Click to expand...
Click to collapse
Why do you think that partition, in particular? If you are talking about boot.img, that gets re-flashed any time your flash a ROM.
Try fastboot erase cache, and flash recovery by fastboot. If Clockwork doesn't work, try TWRP.
If you indeed have some corrupted partition(s), your best bet is to RUU. You are non-specific about what error codes, so its hard to help you troubleshoot why the RUU failed. Try a more updated RUU, such as 2.23.
redpoint73 said:
Why do you think that partition, in particular? If you are talking about boot.img, that gets re-flashed any time your flash a ROM.
Try fastboot erase cache, and flash recovery by fastboot. If Clockwork doesn't work, try TWRP.
If you indeed have some corrupted partition(s), your best bet is to RUU. You are non-specific about what error codes, so its hard to help you troubleshoot why the RUU failed. Try a more updated RUU, such as 2.23.
Click to expand...
Click to collapse
Error 155 Unknown Error it says, do i need to relock the bootloader? I could never find a way to S-Off the device so idk if its that or corrupted partition like you said but all my services on my phone crash constantly. But that's better then aokp_task650_m8_kitkat_5.13.2014 that one won't even make it through setup the services crash so often the badseed rom is the only other rom i found that is actually usable. Oh my RUU is 2.0.16 how can i find the newest one for my HTC One M8?
Darthdiddy said:
Error 155 Unknown Error it says, do i need to relock the bootloader?
Oh my RUU is 2.0.16 how can i find the newest one for my HTC One M8?
Click to expand...
Click to collapse
You always need to relock the bootloader to run RUU with s-on. No exceptions.
Hopefully this will clear up your RUU problem, although the RUU number you just supplied above doesn't make any sense (doesn't correspond to any RUU for this device) Where did you find it, and its not what you referenced in Post #5 above.
CavyS already supplied a link for the "latest" AT&T RUU in Post #4 above. Although be aware, that if you are successful in running the latest RUU, it will render sunshine unable to achieve s-off. I suggest RUU to 1.58 or 2.23 (if you want s-off), as those should still be supported by sunshine.
Darthdiddy said:
I could never find a way to S-Off the device
Click to expand...
Click to collapse
Did you try sunshine? Its the only way to s-off at this time.
redpoint73 said:
You always need to relock the bootloader to run RUU with s-on. No exceptions.
Hopefully this will clear up your RUU problem, although the RUU number you just supplied above doesn't make any sense (doesn't correspond to any RUU for this device) Where did you find it, and its not what you referenced in Post #5 above.
CavyS already supplied a link for the "latest" AT&T RUU in Post #4 above. Although be aware, that if you are successful in running the latest RUU, it will render sunshine unable to achieve s-off. I suggest RUU to 1.58 or 2.23 (if you want s-off), as those should still be supported by sunshine.
Did you try sunshine? Its the only way to s-off at this time.
Click to expand...
Click to collapse
Relocked and flashed the ruu utility version said 2.0.16.2014 and is KK 4.4, idk about sunshine as to reading about people with my phone and it not working so for a 25$ leap of faith not sure what to do about that. My phone is running perfect now in a locked down carrier branded and bloatware way lol. Thanks guys, anyway i can tell if sunshine will work on my phone?
Darthdiddy said:
Relocked and flashed the ruu utility version said 2.0.16.2014 and is KK 4.4
Click to expand...
Click to collapse
I think that is the version of the actual installer software (.exe) not the ROM version it will install on your phone. Kitkat for AT&T would be either 1.58 or 2.23. That number will be in the actual file name of the RUU, so just look there (actually a much longer string of numbers starting with 1.58 or 2.23, but I've abbreviated them for convenience).
Darthdiddy said:
idk about sunshine as to reading about people with my phone and it not working so for a 25$ leap of faith not sure what to do about that. My phone is running perfect now in a locked down carrier branded and bloatware way lol. Thanks guys, anyway i can tell if sunshine will work on my phone?
Click to expand...
Click to collapse
You install the sunshine APK, run it, and sunshine will tell you whether it can s-off the phone or not. You won't be charged unless it can successfully s-off the phone. I haven't heard of any folks here that got charged, and sunshine couldn't s-off the device.
redpoint73 said:
I think that is the version of the actual installer software (.exe) not the ROM version it will install on your phone. Kitkat for AT&T would be either 1.58 or 2.23. That number will be in the actual file name of the RUU, so just look there (actually a much longer string of numbers starting with 1.58 or 2.23, but I've abbreviated them for convenience).
You install the sunshine APK, run it, and sunshine will tell you whether it can s-off the phone or not. You won't be charged unless it can successfully s-off the phone. I haven't heard of any folks here that got charged, and sunshine couldn't s-off the device.
Click to expand...
Click to collapse
Wow thanks for the info! Before i try this can after S-OFF/rooting/SU can i install the unlocked/developer ruu from HTC and get HTC OTA and get away from this bloated carrier branded crap? So much in the forums and i can't find a answer to this question anywhere.
hey, ihave a htc one m7 on 4.2.2 android ice cold project rom and ive been trying to go back to stock htc sense rom but downgrade from stock 5.0.2 and I cant seem to do it, ive tried ota update zip files, stock odexed rom but nothing seems to work, I got the stock rom on but then the touch screen didn't work so had to go back to aicp. I also cant get s-off as ive got hboot 1.61 and cant afford to buy sunshine.
any help would be much appreciated thanks.
You need the RUU then. The reason touch won't work is because the firmware is not matched to the OS. This is a common HTC thing. You have to find the RUU that corresponds to your carrier or region as well as being the same or newer than the firmware you are on now since you are S-On. You must relock your bootloader to install the RUU while being S-On as well.
es0tericcha0s said:
You need the RUU then. The reason touch won't work is because the firmware is not matched to the OS. This is a common HTC thing. You have to find the RUU that corresponds to your carrier or region as well as being the same or newer than the firmware you are on now since you are S-On. You must relock your bootloader to install the RUU while being S-On as well.
Click to expand...
Click to collapse
could you help me find then compatible RUU please? I don't know what one id use. I was hoping to downgrade from lollipop but I don't think ill be able to.
ive went back to the os that didn't work with touch and am going to do and ota update, but how would I get my device to allow ota updates again? do I have to put the recovery back to stock as well as relock bootloader or is there more to it?
You'll need fastboot to make sure you are getting the correct version. If you do not have it, get it from here: http://forum.xda-developers.com/showthread.php?t=2317790 then boot to the bootloader and run this command:
fastboot getvar all
Post results but remove your IMEI and serial number.
You definitely can not downgrade while S-On. You won't need to worry about OTAs as the RUU will do everything for you. If you do want to enable OTAs after you get everything matched up, then yes, you would need to leave the system and the recovery stock.
would there be anyway for me to downgrade then? ive tried flashing other firmware and so far I might have got it, I just need to wait for my phone to charge till I know
You can flash an older rom, but a true downgrade with everything matched is not possible while being S-On.
es0tericcha0s said:
You can flash an older rom, but a true downgrade with everything matched is not possible while being S-On.
Click to expand...
Click to collapse
what rom could I flash?
How could I know without knowing which M7 you are using and what firmware is on it? I've already provided instructions for what was needed for additional info.