Ok so I messed up trying to root my phone for the first time. I skipped the whole S-Off step and now my favorite phone is just this brick.
So my situation is I was running a GPE edition no problems but when I tried to flash stock recovery so it would do an OTA update everything went bad.
My bootloader turned black and my bootup screen has this lock icon at the bottom now.
I can't flash any ROMs on my phone and nothing seems to work. I just need to get any sense based ROM to work on my phone so I can get it working.
I will probably S-OFF next chance i get though.
HTC BOOTLOADER SCREEN
***TAMPERED***
***UNLOCKED***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-1,16,21331931
OpenDSP~V38.2.2-00542-M8974.0311
OS-
eMMC-BOOT 2048MB
JUN 16 2014,18:47:55.0
RECOVERY=TWRP V2.8.1.0
fombat said:
Ok so I messed up trying to root my phone for the first time. I skipped the whole S-Off step and now my favorite phone is just this brick.
So my situation is I was running a GPE edition no problems but when I tried to flash stock recovery so it would do an OTA update everything went bad.
My bootloader turned black and my bootup screen has this lock icon at the bottom now.
I can't flash any ROMs on my phone and nothing seems to work. I just need to get any sense based ROM to work on my phone so I can get it working.
I will probably S-OFF next chance i get though.
HTC BOOTLOADER SCREEN
***TAMPERED***
***UNLOCKED***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-1,16,21331931
OpenDSP~V38.2.2-00542-M8974.0311
OS-
eMMC-BOOT 2048MB
JUN 16 2014,18:47:55.0
RECOVERY=TWRP V2.8.1.0
Click to expand...
Click to collapse
I don't think you absolutely NEED s-off. In fact, if you have s-on then your phone is fine and it protected and most likely not bricked. Can you boot into your twrp recovery?
OP is missing a lot of facts and details (needed to help properly):
fombat said:
So my situation is I was running a GPE edition
Click to expand...
Click to collapse
Was it originally a GPE version, did you convert it by RUU, or just running a GPE ROM?
fombat said:
So my situation is I was running a GPE edition no problems but when I tried to flash stock recovery so it would do an OTA update everything went bad.
Click to expand...
Click to collapse
What did you try to flash?
fombat said:
I can't flash any ROMs on my phone and nothing seems to work.
Click to expand...
Click to collapse
Meaning what? Does it fail to flash in TWRP, any error message, or it flashes but doesn't boot?
What ROMs have you tried? Did you try a GPE or AOSP ROM?
redpoint73 said:
OP is missing a lot of facts and details (needed to help properly):
Was it originally a GPE version, did you convert it by RUU, or just running a GPE ROM?
What did you try to flash?
Meaning what? Does it fail to flash in TWRP, any error message, or it flashes but doesn't boot?
What ROMs have you tried? Did you try a GPE or AOSP ROM?
Click to expand...
Click to collapse
OK I'm sorry this was my first post and I didn't know
It was working with a GPE ROM I didn't flash any RUU or anything like that
Also I have tried a number of different m8 Roms such as skydragon, android revolution, maximus hd and various others all to no avail the only ROM I have gotten to work is Sinless GPE edition but it's a 4.4.2 ROM and also CM 11 but there are no sense features.
Using Sinless and Sunshine I managed to get s-off but none of the roms I want skydragon or android revolution to work.
With skydragon it will flash successfully but not boot up and if it does boot up after I turn it off it won't boot up again. With android revolution I get the error that syslink failed.
fombat said:
Using Sinless and Sunshine I managed to get s-off but none of the roms I want skydragon or android revolution to work.
With skydragon it will flash successfully but not boot up and if it does boot up after I turn it off it won't boot up again. With android revolution I get the error that syslink failed.
Click to expand...
Click to collapse
For the current Skydragon (Sense) and ARHD, you need to update your firmware. This might be your issue right there.
More info here: http://forum.xda-developers.com/showthread.php?t=2696282
Also you mentioned you tried to flash stock recovery, and I asked what you flashed. You didn't answer that (only mentioned the ROMs you tried). What stock recovery did you try to flash?
Related
I purchased a ATT HTC One from one of my friends, it was rooted and had TWRP installed. It was also running Bigxie 4.3 GPe rom. I would like to go to the GPe 4.4 rom but the problem im having is all they ones I can find say they require S-OFF. My phone is S-ON and I have not been able to obtain S-OFF with revone or rumrunner. I tried moonshine but my phone would not boot after the fastboot process. Revone gives me an error 1 and rumrunner tells me to flash a unsecure kernal and try again. The phone is hboot 1.44. After doing a little research I found that someone pleople are saying to go back to the factory rom, the problem is im not sure if the guy backed up the factory rom before he flashed the 4.3 GPe rom. I have asked him and he can remember and blew me off... so my question is how can I find out if he backed up the factory rom, how to restore it or how to obtain S-OFF with bigxie 4.3 GPe rom. Thanks in advance for the help, btw im a noob at this so the more dumbed down responses the better
epcon said:
I purchased a ATT HTC One from one of my friends, it was rooted and had TWRP installed. It was also running Bigxie 4.3 GPe rom. I would like to go to the GPe 4.4 rom but the problem im having is all they ones I can find say they require S-OFF. My phone is S-ON and I have not been able to obtain S-OFF with revone or rumrunner. I tried moonshine but my phone would not boot after the fastboot process. Revone gives me an error 1 and rumrunner tells me to flash a unsecure kernal and try again. The phone is hboot 1.44. After doing a little research I found that someone pleople are saying to go back to the factory rom, the problem is im not sure if the guy backed up the factory rom before he flashed the 4.3 GPe rom. I have asked him and he can remember and blew me off... so my question is how can I find out if he backed up the factory rom, how to restore it or how to obtain S-OFF with bigxie 4.3 GPe rom. Thanks in advance for the help, btw im a noob at this so the more dumbed down responses the better
Click to expand...
Click to collapse
I'm not trying to sound rude but this question gets ask every day
their are dozens of post on how to return to stock
Look Here Guru Reset
Wow I'm not sure how I missed that in my research. Thanks!!!
Before I go through these steps does anyone know of another way I can get S-OFF?
Sent from my HTC One using Tapatalk
epcon said:
Wow I'm not sure how I missed that in my research. Thanks!!!
Before I go through these steps does anyone know of another way I can get S-OFF?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Rumrunner works just fine on your hboot. Reread the instructions and try again.
Also read up on how you make a backup of your soff when you are done.
epcon said:
Wow I'm not sure how I missed that in my research. Thanks!!!
Before I go through these steps does anyone know of another way I can get S-OFF?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
If you have an AT&T phone - MID - PN0712000 - CID - CWS__001
just run this http://www.htc1guru.com/dld/guru_reset_m7_1-26-502-15-zip/
Install the stock recovery and take the OTA Update... then just use rumrunner to s-off
clsA said:
If you have an AT&T phone - MID - PN0712000 - CID - CWS__001
just run this
Install the stock recovery and take the OTA Update... then just use rumrunner to s-off
Click to expand...
Click to collapse
Thanks cLsA, I restored that RUU and stock recovery, it was still not able to get rumrunner to work... error -6 this time. Im just giving up on getting 4.4... this is becoming a lot more trouble than its worth. I do have one more question though, is there a way to hide the system update is ready to install on 4.3 GPe ROM?
epcon said:
Thanks cLsA, I restored that RUU and stock recovery, it was still not able to get rumrunner to work... error -6 this time. Im just giving up on getting 4.4... this is becoming a lot more trouble than its worth. I do have one more question though, is there a way to hide the system update is ready to install on 4.3 GPe ROM?
Click to expand...
Click to collapse
I used the developers edition and had the 4.4 updated in 30 min or so
http://forum.xda-developers.com/showpost.php?p=47992226&postcount=469
if you did the guru reset to at&t stock how are you back on GPe Rom ?
clsA said:
I used the developers edition and had the 4.4 updated in 30 min or so
http://forum.xda-developers.com/showpost.php?p=47992226&postcount=469
if you did the guru reset to at&t stock how are you back on GPe Rom ?
Click to expand...
Click to collapse
I installed the guru with root off. rumrunner would not run unless I had root so I installed the newest TWRP and gained root access. Rumrunner then did get futher but still gave me an error. I tried tried with revone then but it gave me a error -6. Also when I installed the guru I did not have a OTA update ready. My phone said it was already up to date. So I used TWRP and restored from a backup of my 4.3GPe rom.
My phone is HBOOT 1.44
MID - PN0712000 - CID - CWS__001
DevUnlocked Bootloader
epcon said:
I installed the guru with root off. rumrunner would not run unless I had root so I installed the newest TWRP and gained root access. Rumrunner then did get futher but still gave me an error. I tried tried with revone then but it gave me a error -6. Also when I installed the guru I did not have a OTA update ready. My phone said it was already up to date. So I used TWRP and restored from a backup of my 4.3GPe rom.
My phone is HBOOT 1.44
MID - PN0712000 - CID - CWS__001
DevUnlocked Bootloader
Click to expand...
Click to collapse
try the developer edition reset I posted above and try rumrunner again
The phone is rooted and unlocked. Other info:
JEWEL PVT SHIP S-ON RL
HBOOT-2.09.0000
RADIO-1.13.11.0830
OpenDSP-v31.1.0.45.0815
eMMC-boot
Oct 18 2012 15:46:20
I have this: d-h.st/SUc version of TWRP installed (2.6.3.0).
I was following this video: youtube: v=OANqKp0tguE
After the ROM and GAPP installed I rebooted the phone and then the "HTC quietly brilliant" white logo screen looped infinitely.
Other things tried:
At some point after I got back into TWRP recovery I hit factory reset which wiped my SDCard and made it unmountable.
I fixed the unmount issue by formatting the drive on my computer (Win7 x64). I, again, loaded the CM11 Kitkat and the GAPPS back on the SDCard and tried to re-install it.
It seemed to install successfully but it said at the end "Unable to mount to '/cache' ".
Rebooted, infinite boot loop again. Went back in to recovery and wiped.
Found the stock rooted ROM, installed, and booted back in to the default OS.
So my questions is, how do I install Kitkat properly to the device? Or any custom ROM? Any help or advice would be greatly appreciated!
Thank you.
You have to install the kernel separately from the ROM since you're S-on. Hit the top link in my sig for more info. Also, make sure you're using the right recovery (the one posted in the CM11 thread, not on the TWRP site).
You should look at using the Rumrunner method to gain S-off on your phone.
Sent from my HTC EVO 4G LTE
FinZ28 said:
You have to install the kernel separately from the ROM since you're S-on. Hit the top link in my sig for more info. Also, make sure you're using the right recovery (the one posted in the CM11 thread, not on the TWRP site).
You should look at using the Rumrunner method to gain S-off on your phone.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Wow that first link is so informative! Thank you
Is there a significant risk of turning s-on to off? Does it make loading ROMs easier if I have S-Off?
I assume with my version I can only use rumrunner?
rwind said:
Wow that first link is so informative! Thank you
Is there a significant risk of turning s-on to off? Does it make loading ROMs easier if I have S-Off?
I assume with my version I can only use rumrunner?
Click to expand...
Click to collapse
You're welcome
"Significant risk" no. Risk, yes, but then again there is risk in everything in life. A little research and knowledge will help you have a better understanding of S-off versus S-on. It makes ROM flashing very simple, as all you have to do when S-off is flash the ROM zip once and that's it-no fooling with flashing the kernel separately, among other things. It allows a multitude of other things, also.
To answer your last question, yes, Rumrunner is the method you'll need to use being on the latest Hboot/firmware version.
Sent from my HTC EVO 4G LTE
FinZ28 said:
You're welcome
"Significant risk" no. Risk, yes, but then again there is risk in everything in life. A little research and knowledge will help you have a better understanding of S-off versus S-on. It makes ROM flashing very simple, as all you have to do when S-off is flash the ROM zip once and that's it-no fooling with flashing the kernel separately, among other things. It allows a multitude of other things, also.
To answer your last question, yes, Rumrunner is the method you'll need to use being on the latest Hboot/firmware version.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
I got rumrunner installed and working, tried installing CM11 Kitkat and everything went smooth and simple. Thank you!
You mentioned something about the TWRP, how do I know which version to get?
Use the version posted in the OP for the CM 11 thread.
Sent from my HTC EVO 4G LTE
Hi everyone,
My phone specifications:
TAMPERED
UNLOCKED
T6UL PVT SHIP S-ON RH
HBOOT- 2.47.0000
RADIO-4T.21.3218.31
OpenDSP-V33.120.274_T6.0829
QSC-
OS-1.54.401.1
eMMC-boot 2048mb
My phone freeze at boot, when i switched it off, it reboots automatically. Yesterday I've unlocked my bootloader install cwm touch version and rooted my phone. installing superuser. but could not s-off my phone using Rumrunner.
So i leave it like this but today i notice that my battery was draining. I decided to install the unsecure kernel. I found only the sprint verizon version unless i'm not using Sprint cause I read somewhere that only the CWM needs to be international. (I think this was the mistake)
I flashed it using CWM. The phone switched on normally and noticed no network at all on the phone. when i restarted the phone, it freeze at boot.
Is my phone bricked??
I can access fastboot menu and recovery.
Thanks and sorry for my bad English.
Your phone is definitely not bricked. You should not flash the Sprint kernel on your phone - yours is an International Model.
Since your OS is 1.54.401.1 - its the European version, you could download the ROM and flash it and your phone should be back to normal.
You could also just flash the stock kernel and it should work, the only reason i suggest to install a complete ROM is to have a clean install.
PS: CWM seems to have issues, please use TWRP for flashing ROM.
pradeepvizz said:
Your phone is definitely not bricked. You should not flash the Sprint kernel on your phone - yours is an International Model.
Since your OS is 1.54.401.1 - its the European version, you could download the ROM and flash it and your phone should be back to normal.
You could also just flash the stock kernel and it should work, the only reason i suggest to install a complete ROM is to have a clean install.
PS: CWM seems to have issues, please use TWRP for flashing ROM.
Click to expand...
Click to collapse
Thank you very much Pradeep.
Just flash the stock rom you uploaded. Camera not working, and no network signal but did not get the message sim invalid like i was getting before.
All other stuff running fine.
That is weird! was your bootloader LOCKED or UNLOCKED when you performed this?
i would suggest to do it when it's UNLOCKED or i would ask you to you to flash the boot.img from the zip file using fastboot flash boot boot.img
Hope you used TWRP and not CWM.
pradeepvizz said:
That is weird! was your bootloader LOCKED or UNLOCKED when you performed this?
i would suggest to do it when it's UNLOCKED or i would ask you to you to flash the boot.img from the zip file using fastboot flash boot boot.img
Hope you used TWRP and not CWM.
Click to expand...
Click to collapse
Problem solved! :laugh: i ran the same procedure again and now everything running fine and smooth. battery very good.
Thanks for your help Pradeep. You made my day. When switching on the phone i get the red message about the build and so on, but i don't care as the running very well.
Bootloader now indicating unlock and s off by firewater.
hellxprexx said:
Problem solved! :laugh: i ran the same procedure again and now everything running fine and smooth. battery very good.
Thanks for your help Pradeep. You made my day. When switching on the phone i get the red message about the build and so on, but i don't care as the running very well.
Bootloader now indicating unlock and s off by firewater.
Click to expand...
Click to collapse
Welcome! we get the red message as well, don't care about it too.
pradeepvizz said:
Welcome! we get the red message as well, don't care about it too.
Click to expand...
Click to collapse
I found that once I re-locked the bootloader (which you must do if you have any intention of using your fingerprint scanner again), I no longer get the red developer disclaimer message during a normal boot. The only time I see it is if I boot into recovery from hboot, and that doesn't bother me at all!
Sprint HTC One Max - Stock Android (barely ) 4.3 JB rooted, s-off, locked BL - HTC EVO 3D - Android 4.0.3 ICS rooted, s-off + a few Galaxies lol
Hi everyone. New to the forum and new to flashing etc. I have been playing with my phone for a couple of nights now but finally gave in and think I need to ask for help.
Here is a bit of background info so far. The last few weeks my One X+ has been suffering from getting stuck coming out of airplane mode. I am currently using an old Desire HD so thought I have nothing to lose by trying to fix the +.
I have managed so far to unlock the bootloader and root the phone. I have flashed TWRP and created a backup.
I have tried to load Android Revolution 8 which complete successfully along with the boot image but when the phone starts I get the HTC splash screen (quietly Brilliant & One X Beats Audio) but it then goes to just HTC then the phone turns itself off.
Have tried a couple of time but end up having to flash my recovery to revert back to how it was.
I feel I may be missing something and would appreciate it if someone could help me out.
Many Thanks :good:
Battery empty?
Sent from my Find 5 using Tapatalk
Lloir said:
Battery empty?
Sent from my Find 5 using Tapatalk
Click to expand...
Click to collapse
No I don't think so. Like I say I have had a few goes at it now and from reading some of the guides on here which say it is important to make sure it has plenty of charge, I have made sure it is well charged before starting.
If it helps, here is some info phone the phone:
HTC One X+
CID-HTC__001
ENRC2B
HBOOT-1.72.0000
Model ID-PM3511000
Have you tried doing a full wipe before or during flashing ARHD? Can you still get into the bootloader or recovery? I had similar problem, changed the cable then flashed the boot image again.
qasimrb said:
Have you tried doing a full wipe before or during flashing ARHD? Can you still get into the bootloader or recovery? I had similar problem, changed the cable then flashed the boot image again.
Click to expand...
Click to collapse
I have done a wipe yes. I have been picking my way through these guides which all have small differences.
http://forum.xda-developers.com/showthread.php?t=2066390
http://forum.xda-developers.com/showthread.php?t=1987885
http://forum.xda-developers.com/showthread.php?t=1995685
Yes I can still access the bootloader and TWRP recovery. The phone is currently restored back to how it was originally.
Are you flashing the boot image before or after you install the rom? With the ARHD he recommends flashing his firmware.zip before flashing the rom.
But from what I remember when my phone was stuck on the splash screen I went back into the bootloader, used another cable and flashed the firmware.zip again, restarted it and it was fine.
Info when I'm in bootloader is:
***UNLOCKED***
ENRC2B_U S-ON
HBOOT-1.30
CPLD- None
MICROP- None
RADIO- None
(Don't know why it says "none" next to radio, network etc is fine, Vodafone UK)
qasimrb said:
Are you flashing the boot image before or after you install the rom? With the ARHD he recommends flashing his firmware.zip before flashing the rom.
But from what I remember when my phone was stuck on the splash screen I went back into the bootloader, used another cable and flashed the firmware.zip again, restarted it and it was fine.
Info when I'm in bootloader is:
***UNLOCKED***
ENRC2B_U S-ON
HBOOT-1.30
CPLD- None
MICROP- None
RADIO- None
(Don't know why it says "none" next to radio, network etc is fine, Vodafone UK)
Click to expand...
Click to collapse
I have tried both ways. Flashing the boot image before and after the installing the ROM and both ways reproduce the same effect.
I have read the page where it mentions loading the firmware but as I have just set out about learning the in's and out's of loading ROMS I wasn't sure what this was. I now understand what the boot image is and what the ROM is but take it the firmware is something different. Should loading the firmware be the first step before falshing the boot image and ROM?
I have been over to his download page with the two 401 firmwares which I believe are the ones I require. The only issue I have is, it seems these are earlier versions so wasn't sure they would be correct to use. I cannot check currently as I'm at work but I think I am running firmware version 2.18.401.3.
So which one should I load?
Also here is the info from my bootloader screen:
HTC One X+
ENRC2B_U PVT SHIP S-ON RL
HBOOT-1.72.0000
CPLD-None
MICROP-None
RADIO-3.1204.171.33
eMMC-bootmode: disabled
CPU-boomode: disabled
HW Secure Path: enabled
MODEM PATH: OFF
Model ID-PM3511000
Software Number - 2.18.401.3
CID-HTC__001
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.