[Q] ATT HTC One X not booting - AT&T, Rogers HTC One X, Telstra One XL

Hello,
I have a carrier unlocked ATT HTC One x (sim unlocked), it is not rebooting after the battery was accedently drained. That happened after I put it on the charger and I saw it starting to charge, and then I hit the power on, but it did not go past the HTC One white screen. After the battery is fully charged, I tried to recover it but I got a red triangle with exclamation mark on a phone icon during the recovery process, then it go to the freezing welcome screen again. I saw many very useful posts but they all do not address the specific problem I am facing. The phone is locked for boot-loader, so I have problem installing an new image. As the phone shut down accidentally I did not set the usb debugger enable mode that seams to be required, also it is not rooted. From the posts I see that I needed to get a temporary superuser by accessing one of the phone files (mmcblk0p4) which is also not possible at this stage. I am able to communicate with the phone with my computer (I got fastboot usb on my phone when connected to the windows 7 pc), I can use fastboot command from the cmd-shell screen (when I do fastboot device, I get the serial number, when I do fastboot oem readcid I get CWS__001 as expected from a loced ATT booter as I understood, I got the identifier but got MID not allowed from the HTCdev site, fastboot command seams to work but when I try anything else that seams more useful to me, suggested in the posts, I got FAILD (remote: not allowed) error, when did fastboot flash recovery recoveryimage.img got sending, then writing, then FAILD (remote: signature verify fail) fastboot oem unlock give Command error, I can also do fastboot oem rebootRUU and reboot-bootloader, not sure what is rebootRUU does but seams that I can flash the system this way.. not sure if I need that now or not yet, or if it is even doable), also it seams that I can not use adb that is described in the very useful post below, when I do adb devices (The adb version 1.0.29) it give me "list of the devices attached" message only with no devices, it seams that adb is the key to what I am doing here and if it is not working then I do not know how to proceed.
http://forum.xda-developers.com/showpost.php?p=49019103
doing adb shell give error: device not found. I downloaded many useful packages that I think for 3.18 or 5.18 software, but I am not sure if these are appropriate to my phone software as I do not recall the exact build, not sure if the Hboot version can tell anything about that or not.
Now I know that I need to get superCID, unlock the bootloader, and then recovery, but I can not pass the first step. I am not clear about what is the S-on or off has to do with that or if it is a required step.
Sorry for the very long post, but wanted to be clear as much as I can, the bootloader info is below.
I appraciate your help very much
EVITA PVT SHIP s-on RL
Hboot ver 1.14.0002
radio ver 0.19as.32.09.11_2
openDSP-v29.1.0.45.0622
eMMc-boot
jun 11 2012, 14:36:28

As long as you have fastboot access you can run an RUU. I'd suggest running the 3.18 RUU to get your phone back up and running again. If you need a tutorial there's one here:
http://forum.xda-developers.com/showthread.php?t=2593037
The fastboot oem unlock command doesn't work on this phone unless you have s-off, to unlock the bootloader you need to go to htcdev and do it there. But you first need to follow section 1a in my guide thread to get SuperCID. You must run the 3.18 RUU first though.
I'd advise against using the rebootRUU mode unless you really know what you're doing, messing around with this stuff without proper knowledge is how phones become fully bricked.
So anyway, run the RUU and that should get your phone up and running again. If you want to unlock your bootloader after that then do what I suggested above.
Transmitted via Bacon

timmaaa said:
As long as you have fastboot access you can run an RUU. I'd suggest running the 3.18 RUU to get your phone back up and running again. If you need a tutorial there's one here:
http://forum.xda-developers.com/showthread.php?t=2593037
The fastboot oem unlock command doesn't work on this phone unless you have s-off, to unlock the bootloader you need to go to htcdev and do it there. But you first need to follow section 1a in my guide thread to get SuperCID. You must run the 3.18 RUU first though.
I'd advise against using the rebootRUU mode unless you really know what you're doing, messing around with this stuff without proper knowledge is how phones become fully bricked.
So anyway, run the RUU and that should get your phone up and running again. If you want to unlock your bootloader after that then do what I suggested above.
Transmitted via Bacon
Click to expand...
Click to collapse
Thank you timmaaa, I will go through this instruction and will tell you how it goes. I appreciate your prompt replay.. Regards ..

timmaaa said:
As long as you have fastboot access you can run an RUU. I'd suggest running the 3.18 RUU to get your phone back up and running again. If you need a tutorial there's one here:
http://forum.xda-developers.com/showthread.php?t=2593037
The fastboot oem unlock command doesn't work on this phone unless you have s-off, to unlock the bootloader you need to go to htcdev and do it there. But you first need to follow section 1a in my guide thread to get SuperCID. You must run the 3.18 RUU first though.
I'd advise against using the rebootRUU mode unless you really know what you're doing, messing around with this stuff without proper knowledge is how phones become fully bricked.
So anyway, run the RUU and that should get your phone up and running again. If you want to unlock your bootloader after that then do what I suggested above.
Transmitted via Bacon
Click to expand...
Click to collapse
Timmaaa, thank you again, your help is highly appreciated, I was able to run the specific RUU, as it turned out that I have the 2.20 software, after little hassle as the process stopped at 56% and I did not know what to do, but saw your comment on another post saying that there is no option, actually I did not take the USB cable out, but rebooted with fastboot from the command window and it worked in the second time. After that I went one step and rooted the phone successfully. Now, I need to get red of the AT&T software currently installed, I saw many posts about that where you also were involved, but the posts were old, so which is the most updated image that I should use to replace the AT&T image that you recommend? I also saw people updating the HTC One X with lollypop android .. is that good or bad, is the hardware able to work good with that new release? I am not clear on the relation between the software update from AT&T to another image, and updating the Android version, are they the same or two different steps? Thank you.

aabdo said:
Timmaaa, thank you again, your help is highly appreciated, I was able to run the specific RUU, as it turned out that I have the 2.20 software, after little hassle as the process stopped at 56% and I did not know what to do, but saw your comment on another post saying that there is no option, actually I did not take the USB cable out, but rebooted with fastboot from the command window and it worked in the second time. After that I went one step and rooted the phone successfully. Now, I need to get red of the AT&T software currently installed, I saw many posts about that where you also were involved, but the posts were old, so which is the most updated image that I should use to replace the AT&T image that you recommend? I also saw people updating the HTC One X with lollypop android .. is that good or bad, is the hardware able to work good with that new release? I am not clear on the relation between the software update from AT&T to another image, and updating the Android version, are they the same or two different steps? Thank you.
Click to expand...
Click to collapse
If you want to use custom ROMs you'll need to do some more work first.
1. Flash the Kickdroid 5.0 ROM. This is only temporary, you need this ROM to get s-off in the next step.
2. Go to the Rumrunner Site and follow the instructions there to get s-off.
3. Go to my guide thread and follow instructions there to flash the 2.15 firmware.
Now you can flash whatever ROM you like. Lollipop is perfectly fine for this device.
Transmitted via Bacon

timmaaa said:
If you want to use custom ROMs you'll need to do some more work first.
1. Flash the Kickdroid 5.0 ROM. This is only temporary, you need this ROM to get s-off in the next step.
2. Go to the Rumrunner Site and follow the instructions there to get s-off.
3. Go to my guide thread and follow instructions there to flash the 2.15 firmware.
Now you can flash whatever ROM you like. Lollipop is perfectly fine for this device.
Transmitted via Bacon
Click to expand...
Click to collapse
Thank you timmaaa, I will work on that and I will let you know how it goes. Best regards ..

timmaaa said:
If you want to use custom ROMs you'll need to do some more work first.
1. Flash the Kickdroid 5.0 ROM. This is only temporary, you need this ROM to get s-off in the next step.
2. Go to the Rumrunner Site and follow the instructions there to get s-off.
3. Go to my guide thread and follow instructions there to flash the 2.15 firmware.
Now you can flash whatever ROM you like. Lollipop is perfectly fine for this device.
Transmitted via Bacon
Click to expand...
Click to collapse
I went through the steps, studied them all first .. then started one by one. First I downloaded Kickdroid 5.0 Rom on my phone storage, although I saw a requirement to have a special firmware package (that to install I needed S-off) post #4 in http://forum.xda-developers.com/showthread.php?t=2485865 , I skipped that requirement and then was able to install Kickdroid 5.0 from the recovery, it flashed successfully, but then the phone did not boot, it hanged on the first white screen, I tried 3 times with changing the options .. I started by not downloading any thing in the flashing process, then last I kept the default except I had to choose to keep sense 5 as there was no default option .. then I cleaned the catch and rebooted .. same result. So I had to go back and restore my original system (as I had it backed up before). I went through the post and in page 19 I saw someone had a similar problem and someone suggested to wipe the storage in order to make it work, which I did not, but then he said it worked without needing to do that. Another suggested to flash a boot.img first with fastboot, which was not in the instructions. Not sure what is the problem I am facing exactly. I use TWRP 2.3.1 to run the zip file on the phone SD, with 75 to 80% battery charged. One more question, I saw a youtube for someone who is getting S-off for HTC One (not x) without that Kikdroid step, https://www.youtube.com/watch?v=MCMJkVbIiIg , he is using your step 2 exactly, Would you please explain to me why I need the first step in my case? Thank you very much for your help.

aabdo said:
I went through the steps, studied them all first .. then started one by one. First I downloaded Kickdroid 5.0 Rom on my phone storage, although I saw a requirement to have a special firmware package (that to install I needed S-off) post #4 in http://forum.xda-developers.com/showthread.php?t=2485865 , I skipped that requirement and then was able to install Kickdroid 5.0 from the recovery, it flashed successfully, but then the phone did not boot, it hanged on the first white screen, I tried 3 times with changing the options .. I started by not downloading any thing in the flashing process, then last I kept the default except I had to choose to keep sense 5 as there was no default option .. then I cleaned the catch and rebooted .. same result. So I had to go back and restore my original system (as I had it backed up before). I went through the post and in page 19 I saw someone had a similar problem and someone suggested to wipe the storage in order to make it work, which I did not, but then he said it worked without needing to do that. Another suggested to flash a boot.img first with fastboot, which was not in the instructions. Not sure what is the problem I am facing exactly. I use TWRP 2.3.1 to run the zip file on the phone SD, with 75 to 80% battery charged. One more question, I saw a youtube for someone who is getting S-off for HTC One (not x) without that Kikdroid step, https://www.youtube.com/watch?v=MCMJkVbIiIg , he is using your step 2 exactly, Would you please explain to me why I need the first step in my case? Thank you very much for your help.
Click to expand...
Click to collapse
You need to flash the boot.img from the Kickdroid ROM zip via fastboot after flashing the ROM in recovery because you're s-on. I'm guessing you haven't done that, and that's why it didn't boot. I wouldn't go anywhere anything that OneXRoot posted honestly, just follow my directions here.
Transmitted via Bacon

timmaaa said:
You need to flash the boot.img from the Kickdroid ROM zip via fastboot after flashing the ROM in recovery because you're s-on. I'm guessing you haven't done that, and that's why it didn't boot. I wouldn't go anywhere anything that OneXRoot posted honestly, just follow my directions here.
Transmitted via Bacon
Click to expand...
Click to collapse
Yes I did not flash the boot.img after I used Kikdroid Rom .. Thank you for clarifying this .. I will try again and let you know .. best regards ..

timmaaa said:
You need to flash the boot.img from the Kickdroid ROM zip via fastboot after flashing the ROM in recovery because you're s-on. I'm guessing you haven't done that, and that's why it didn't boot. I wouldn't go anywhere anything that OneXRoot posted honestly, just follow my directions here.
Transmitted via Bacon
Click to expand...
Click to collapse
But would you please confirm that the second step is exactly as shown in the youtube clip? I am just not positive as it is another device and wanted to hear your opinion .. not sure if there is a difference or not between the hardware of HTC One X and HTC One. Thanks.

aabdo said:
But would you please confirm that the second step is exactly as shown in the youtube clip? I am just not positive as it is another device and wanted to hear your opinion .. not sure if there is a difference or not between the hardware of HTC One X and HTC One. Thanks.
Click to expand...
Click to collapse
Seeing as the steps in the clip aren't numbered I have no idea which part you're talking about. It's very straight forward though, flash Kickdroid (including the boot.img), go to Rumrunner and follow their instructions, flash the firmware in my guide.

timmaaa said:
Seeing as the steps in the clip aren't numbered I have no idea which part you're talking about. It's very straight forward though, flash Kickdroid (including the boot.img), go to Rumrunner and follow their instructions, flash the firmware in my guide.
Click to expand...
Click to collapse
Thanks .. yes it seams straight forward, but as I have no experience, I try to be cautious as much as I can, the entire clip is your step 2 in the instructions you gave me for running the rumrunner .. Sorry if I wasted your time to watch the clip, I should not have asked that, but thanks.
Now I am still stuck actually at the first step, I flashed the KickdroidXL 5 successfully, then I flashed the boot.img (fastboot flash boot boot.img) using the boot.img in the Kickdroid package, as you recommended, a little progress I saw, it start with a new logo "T" then the first HTC white screen I used to be stuck on before, then the One X white screen .. but then does not boot. I flashed the Kickdroid twice and every time I do cache erase with the TWRP and with fastboot (fastboot erase cache). Please let me know if I seam to be missing any steps that cause it to not boot .. Thank you for your help and prompt response .. Regards ..

aabdo said:
Thanks .. yes it seams straight forward, but as I have no experience, I try to be cautious as much as I can, the entire clip is your step 2 in the instructions you gave me for running the rumrunner .. Sorry if I wasted your time to watch the clip, I should not have asked that, but thanks.
Now I am still stuck actually at the first step, I flashed the KickdroidXL 5 successfully, then I flashed the boot.img (fastboot flash boot boot.img) using the boot.img in the Kickdroid package, as you recommended, a little progress I saw, it start with a new logo "T" then the first HTC white screen I used to be stuck on before, then the One X white screen .. but then does not boot. I flashed the Kickdroid twice and every time I do cache erase with the TWRP and with fastboot (fastboot erase cache). Please let me know if I seam to be missing any steps that cause it to not boot .. Thank you for your help and prompt response .. Regards ..
Click to expand...
Click to collapse
Ok, dust things first, lets get Kickdroid booting. When you flash a new ROM you need to perform a full wipe, this means wiping system, data, cache, and dalvik cache.
Transmitted via Bacon

timmaaa said:
Ok, dust things first, lets get Kickdroid booting. When you flash a new ROM you need to perform a full wipe, this means wiping system, data, cache, and dalvik cache.
Transmitted via Bacon
Click to expand...
Click to collapse
OK thank you temmaaa, that was my mistake the, I was trying to not wipe anything, but that seams to be wrong. The strange thing is that after I was able to boot, I still see my data on the phone sd storage. Question for you, when I failed to boot Kickdroid 5, I tried to restore my old AT&T system which I backed up with TWRP and saved on the phone (as well as outside) but that did not restore .. does the boot.img flashing is the reason for that? it seams that I needed to flash another boot.img to get back the old system.. is my understanding correct?
Now I will proceed to the second step .. running rumrunner.. I will follow the instruction from the link you gave me.
Also, would you please explain to me why I need to flash the 2.15 software which is step 3 in your instructions?
Is there any risky step here that I need to take special attention to?
Thank you for your help .. really appropriate it.

aabdo said:
OK thank you temmaaa, that was my mistake the, I was trying to not wipe anything, but that seams to be wrong. The strange thing is that after I was able to boot, I still see my data on the phone sd storage. Question for you, when I failed to boot Kickdroid 5, I tried to restore my old AT&T system which I backed up with TWRP and saved on the phone (as well as outside) but that did not restore .. does the boot.img flashing is the reason for that? it seams that I needed to flash another boot.img to get back the old system.. is my understanding correct?
Now I will proceed to the second step .. running rumrunner.. I will follow the instruction from the link you gave me.
Also, would you please explain to me why I need to flash the 2.15 software which is step 3 in your instructions?
Is there any risky step here that I need to take special attention to?
Thank you for your help .. really appropriate it.
Click to expand...
Click to collapse
No worries, please refer to my guide that I've linked you to, it contains instructions for pretty much anything you need to do.
The wipes that I mentioned don't wipe your sd card, that isn't wiped unless you explicitly choose to wipe it in the advanced wipe menu.
When you made the backup of your stock ROM did you backup boot? If not, that's why your restore isn't booting. If you did, did you restore that as well?
You need to flash the 2.15 firmware because all recent ROMs require the updated firmware to be installed in order to operate correctly. In fact, they won't even flash of the firmware isn't present as there's a check in the updater script that'll stop the install if you don't have the correct firmware. There's no real risk, as long as you follow the directions correctly. In saying that though, there's always a small risk when flashing anything to your phone, but as long as you do what you're supposed to do you can mitigate that risk.
Transmitted via Bacon

timmaaa said:
No worries, please refer to my guide that I've linked you to, it contains instructions for pretty much anything you need to do.
The wipes that I mentioned don't wipe your sd card, that isn't wiped unless you explicitly choose to wipe it in the advanced wipe menu.
When you made the backup of your stock ROM did you backup boot? If not, that's why your restore isn't booting. If you did, did you restore that as well?
You need to flash the 2.15 firmware because all recent ROMs require the updated firmware to be installed in order to operate correctly. In fact, they won't even flash of the firmware isn't present as there's a check in the updater script that'll stop the install if you don't have the correct firmware. There's no real risk, as long as you follow the directions correctly. In saying that though, there's always a small risk when flashing anything to your phone, but as long as you do what you're supposed to do you can mitigate that risk.
Transmitted via Bacon
Click to expand...
Click to collapse
First I would like to express my appreciation for your help and detailed instructions, Thank you.
Kikdroid 5 seams really nice, I finally got rid of the AT&T image.
You are right, I did not backup the stock boot.img .. I did not know I needed to .. or overlooked it in some instructions, well as I said, I have no experience and trying to learn... If there is a reference that I can read to understand mainly the terminology and the relationship better them .. please point it to me .. I have problem understanding some the used terminology, specially that kernel word seams that the kernel is the Android version .. maybe..
My worry with firmware flash is that I see in some instructions .. if it did not work .. or give an error .. flash it again "immediately" .. that immediately word scares me very much .. what if I did not do it fast enough .. am I going to loose my phone. That is something completely unclear to me, I have some knowledge in computers, but I do not understand how a software can damage a hardware.
Best regards ..

aabdo said:
First I would like to express my appreciation for your help and detailed instructions, Thank you.
Kikdroid 5 seams really nice, I finally got rid of the AT&T image.
You are right, I did not backup the stock boot.img .. I did not know I needed to .. or overlooked it in some instructions, well as I said, I have no experience and trying to learn... If there is a reference that I can read to understand mainly the terminology and the relationship better them .. please point it to me .. I have problem understanding some the used terminology, specially that kernel word seams that the kernel is the Android version .. maybe..
My worry with firmware flash is that I see in some instructions .. if it did not work .. or give an error .. flash it again "immediately" .. that immediately word scares me very much .. what if I did not do it fast enough .. am I going to loose my phone. That is something completely unclear to me, I have some knowledge in computers, but I do not understand how a software can damage a hardware.
Best regards ..
Click to expand...
Click to collapse
The XDA Encyclopedia is pretty handy for learning terminology:
http://forum.xda-developers.com/other-special/encyclopedia
The kernel isn't the Android version, it's a low level layer of firmware that basically handles interactions between the hardware and the software. Searching "what is a kernel" on Google should return a much better explanation than I can give.
When those instructions say you must give the same command again immediately it really just means to do it without anything else in between. You should actually give the command twice even if you don't receive the error, so make sure you do it twice.
Transmitted via Bacon

timmaaa said:
The XDA Encyclopedia is pretty handy for learning terminology:
http://forum.xda-developers.com/other-special/encyclopedia
The kernel isn't the Android version, it's a low level layer of firmware that basically handles interactions between the hardware and the software. Searching "what is a kernel" on Google should return a much better explanation than I can give.
When those instructions say you must give the same command again immediately it really just means to do it without anything else in between. You should actually give the command twice even if you don't receive the error, so make sure you do it twice.
Transmitted via Bacon
Click to expand...
Click to collapse
Thank you timmaaa .. I will work on the following steps and update you with my progress .. best regards ..

timmaaa said:
The XDA Encyclopedia is pretty handy for learning terminology:
http://forum.xda-developers.com/other-special/encyclopedia
The kernel isn't the Android version, it's a low level layer of firmware that basically handles interactions between the hardware and the software. Searching "what is a kernel" on Google should return a much better explanation than I can give.
When those instructions say you must give the same command again immediately it really just means to do it without anything else in between. You should actually give the command twice even if you don't receive the error, so make sure you do it twice.
Transmitted via Bacon
Click to expand...
Click to collapse
timmaaa, I successfully got S-off on my phone, which is the second step in your instruction, that was not possible without your help, Thank you ..
I will now study the third step which I see explained very well in your guide to flash the 2.15 firmware.
I still have the Kickdroid 5 and I noticed that the phone is restarting very often now, it also looses signal, and that Google hangouts is not working, hopefully that will get better with the 2.15 firmware. By the way, what is that 2.15 Firmware? is that HTC officially released ROM? (firmware is a ROM?), I hope the relationship between the recovery, the boot, and the firmware are explained in the link you provided, because still these not clear to me. I am guessing I will not have Kickdroid 5 after flashing the 2.15 firmware .. is that correct?
Thank you very much for your help throughout this process.

aabdo said:
timmaaa, I successfully got S-off on my phone, which is the second step in your instruction, that was not possible without your help, Thank you ..
I will now study the third step which I see explained very well in your guide to flash the 2.15 firmware.
I still have the Kickdroid 5 and I noticed that the phone is restarting very often now, it also looses signal, and that Google hangouts is not working, hopefully that will get better with the 2.15 firmware. By the way, what is that 2.15 Firmware? is that HTC officially released ROM? (firmware is a ROM?), I hope the relationship between the recovery, the boot, and the firmware are explained in the link you provided, because still these not clear to me. I am guessing I will not have Kickdroid 5 after flashing the 2.15 firmware .. is that correct?
Thank you very much for your help throughout this process.
Click to expand...
Click to collapse
Those problems will stop once you have flashed the firmware. The firmware isn't a ROM, it's a lower level of firmware that includes the radio/modem, hboot, and various drivers. It is official from HTC. You will still have Kickdroid after installing the firmware.
XDA Moderator
Transmitted via Bacon

Related

Adventures of a newbie...........Clockwork mod and Ruu Radio Update. 1.06es

Being fairly new to all this and keep getting told to read forums and search etc i thought id make this little post.
id already managed to work out how to root and flash recovery and then custom roms.................
It was when i had to reverse everything and go for a RUU radio update i became unstuck.........
http://www.xda-developers.com/andro...-mytouch-4g-slide-amaze-4g-rezound-and-vivid/
thats one of the main tools i as a newbie use to save all them fastboot commands...........
Right once youve downloaded this tool i used it to reflash stock recovery and then re lock the bootloader..............
http://www.androidauthority.com/one-s-clockworkmod-recovery-unofficial-77818/ <<<<<<<<<<<<<<but in reverese
you need to rename the stock recovery to recovery.img and put it in the recovery data folder(of the htc one s tookit) and then flash custom recovery from with menu in the htc one s toolkits ui
I then just relocked the boot loader................
all ok so far....................
After this i then updated the RUU and followed the on screen instructions..............Bear in mind it takes a little while.
Latest one is here
http://www.lastnite.de/RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5.exe
http://www.freefilehosting.net/ruuv...radio106es5002311009a5004lrelease275655signed
HTC one s toolkit works just fine but doesnt at least on my phone flash the recovery back so it works...................
I have to do it this way via fastboot.
http://www.androidauthority.com/one-s-clockworkmod-recovery-unofficial-77818/
WARNING!
This is how it works on my phone and mine alone. Do any of the above at your own risk. As i am by no means a expert!!
Gavin01 said:
Being fairly new to all this and keep getting told to read forums and search etc i thought id make this little post.
id already managed to work out how to root and flash recovery and then custom roms.................
It was when i had to reverse everything and go for a RUU radio update i became unstuck.........
http://www.xda-developers.com/andro...-mytouch-4g-slide-amaze-4g-rezound-and-vivid/
thats one of the main tools i as a newbie use to save all them fastboot commands...........
Right once youve downloaded this tool i used it to reflash stock recovery and then re lock the bootloader..............
you need to rename the stock recovery to recovery.img and put it in the recovery data folder(of the htc one s tookit) and then flash custom recovery from with menu in the htc one s toolkits ui
I then just relocked the boot loader................
all ok so far....................
After this i then updated the RUU and followed the on screen instructions..............Bear in mind it takes a little while.
Latest one is here
http://www.lastnite.de/RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5.exe
http://www.freefilehosting.net/ruuv...radio106es5002311009a5004lrelease275655signed
HTC one s toolkit works just fine but doesnt at least on my phone flash the recovery back so it works...................
I have to do it this way via fastboot.
http://www.androidauthority.com/one-s-clockworkmod-recovery-unofficial-77818/
WARNING!
This is how it works on my phone and mine alone. Do any of the above at your own risk. As i am by no means a expert!!
Click to expand...
Click to collapse
This is not development work and therefore should never have been posted in the section.
Thanks i really appreciate it
And i only went from other threads here that imformation about things like this..
http://forum.xda-developers.com/showthread.php?p=30923825#post30923825
http://forum.xda-developers.com/showthread.php?t=1861981
Gavin01 said:
Thanks i really appreciate it
And i only went from other threads here that imformation about things like this..
http://forum.xda-developers.com/showthread.php?p=30923825#post30923825
http://forum.xda-developers.com/showthread.php?t=1861981
Click to expand...
Click to collapse
Really appreciate what? He said nothing other than it's in the wrong forum, lol.
Thread moved to general.

[SOLVED] One S - a little stuck between roms

Hello.
I'm coming from HD2 and Sensation recently and wanted to get a custom rom for my new One S. I'm inexperienced with this model.
I followed the unlock / cwm / root procedure in the excellent guide sticky. Everything went very well and I tried Jellybam. Got the boot anim but no full boot. I forgot to back up the stock rom so there I was with no working rom and no way to copy a new one onto the sdcard partition.
After some research I've been able to push new rom files to the sdcard partition through adb but I can't seem to get anything to boot on this thing.
I also tried relocking but I cant find which RUU to match my CID (HTC__Y13), I tried all the EU RUU's but they all give me the signature error upon flashing.
So I'm not bricked, I can still install different recoveries and use fastboot. It's just that nothing boots. What am I missing out on here? Oh, and QuickADB tells me that I am not rooted and busybox is missing although I've ran SuperSU CWM.
Any thoughts?
QuickADBPusher is unable to acquire root because you are on stock rom/kernel. The Q&A section tells you that
Have to fastboot flashed boot.img? Its required for hboot above.... urm.. Dunno, but 1.14 needs it anyway.
Goatshocker said:
QuickADBPusher is unable to acquire root because you are on stock rom/kernel. The Q&A section tells you that
Have to fastboot flashed boot.img? Its required for hboot above.... urm.. Dunno, but 1.14 needs it anyway.
Click to expand...
Click to collapse
I now tried to follow the instructions for flashing custom rom on HBOOT > 1.09. So I extracted the boot.img from my desired ROM package. Then I went for another adb push of the rom file (I had done a clear memory in the meantime) and now I'm getting protocol error all over the place.
I miss my HD2. I even miss my Pyramid now...
EDIT: The boot.img flashed fine though.
Wait wait! It worked!
Finally got MIUI (my secret lover) pushed and boot.img extracted and flashed.... and voila!!
Goatshocker! Major respect and bigups for your little advice for the n00bs but first and foremost for all the work you do for our community. You rock man.
Oh thanks. I dont think I do that much though but I try to help where I can
Goatshocker said:
Oh thanks. I dont think I do that much though but I try to help where I can
Click to expand...
Click to collapse
It's always those little things that pass us by.
Hope this thread can help other EU users though. Many of the posts on One S kind of imply that your'e on a low hboot. (Other markets, branded and so forth) But the phones we get these days up here are unbranded 2.15 by stock and you'd always have to manually flash boot as I understand.
Hopefully theres enough food in here for the search engines so that others might find it. Ah. A great day after all.

New to One S and need some help

Hi,
Normally, I try to troubleshoot things myself without bothering others, but I'm in need of help this time. The tricky part is, I just bought this HTC One S from a stranger, so I don't have its complete history. With that said, here's what I need help with. The phone came with Pacman installed (v18.0.0). But, I would like to install this ROM: http://forum.xda-developers.com/showthread.php?t=2082451
It's basically a stock ICS ROM (the lite version mentioned with stuff removed). In attempt to do this myself, I found this post on here:
Yes the only other solution for you involves rooting. It is possible to go back to ICS by rooting your phone, going through a bootloader downgrade, hexediting a particular partition, then running an older compatible RUU... Its all possible, but requires some time to understand and do. And definately requires a few wipes of phone data in the mean time (which can be backed up through titanium and custom recoveries).
Only need to do that if you want to downgrade hboot. All you have to do is root and flash a rom, I have JB radio and hboot and run ICS Trickdroid 8.1.0.
So, I put the ICS ROM in the internal sdcard, did the usual wiping stuff (I've owned several HTC phones, so this part I know how), then installed the ROM. Unfortunately, it didn't work. When I rebooted the phone, it got stuck in boot loop. It would go to HTC logo screen with the development purpose only warning and just keep turning off and on. Fortunately, I was able to get back into recovery and restored it to Pacman. So, apparently, you can't just flash any ICS ROM over JB setup... Can someone help me figure out what I need to do to install that modified stock ROM please? I very much appreciate your help. My One S is S4 from T-Mobile.
Thank you,
GT
Did you flash boot.img?
Sent from my HTC VLE_U using xda app-developers app
thats weird.. if you wipe cache, dalvik, factory reset and system.. it should be fine.
which recovery do you have? cwm or twrp? flashing the rom after wiping everything i stated before, and then flashing boot.img depending on your hboot [btw, go to bootloader and see what it says for hboot. if it is higher than 1.13, you need to fastboot boot.img.
dr_rick13 said:
thats weird.. if you wipe cache, dalvik, factory reset and system.. it should be fine.
which recovery do you have? cwm or twrp? flashing the rom after wiping everything i stated before, and then flashing boot.img depending on your hboot [btw, go to bootloader and see what it says for hboot. if it is higher than 1.13, you need to fastboot boot.img.
Click to expand...
Click to collapse
Thank you for tending to my thread. The recovery installed is CWM 5.8.3.1
Here's what it says on fastboot:
Tampered
Unlocked
VLE PVT SHIP S-On RL
HBOOT-1.14.0004
RADIO-1.08ts.50.02.16
OpenDSP-v29.1.0.45.0622
eMMC-boot
Please let me know what exactly I need to do in step by step or point me to a thread that contains the steps. Thank you so much.
goldentequila said:
Thank you for tending to my thread. The recovery installed is CWM 5.8.3.1
Here's what it says on fastboot:
Tampered
Unlocked
VLE PVT SHIP S-On RL
HBOOT-1.14.0004
RADIO-1.08ts.50.02.16
OpenDSP-v29.1.0.45.0622
eMMC-boot
Please let me know what exactly I need to do in step by step or point me to a thread that contains the steps. Thank you so much.
Click to expand...
Click to collapse
no prob, i HIGHLY suggest you flash TWRP recovery.. it's a loot better.
2. are you trying to install a TMOUS ROM?
3. since your hboot is higher than 1.13, you will need to fastboot boot.img [let me know if you know how to do that]
4. also since your hboot is higher than 1.13, you will need to flash some partitions or else your WiFi won't work.
Let me know if you need help doing any of the above, but start out with installing TWRP first.
dr_rick13 said:
no prob, i HIGHLY suggest you flash TWRP recovery.. it's a loot better.
2. are you trying to install a TMOUS ROM?
3. since your hboot is higher than 1.13, you will need to fastboot boot.img [let me know if you know how to do that]
4. also since your hboot is higher than 1.13, you will need to flash some partitions or else your WiFi won't work.
Let me know if you need help doing any of the above, but start out with installing TWRP first.
Click to expand...
Click to collapse
Thank you for such a prompt reply. Here are some of my answers.
2. Yes, the ROM I want to install is this one: http://forum.xda-developers.com/showthread.php?t=2082451
It's the light version mentioned in that first post.
3. I just read up on this page: http://forum.xda-developers.com/showthread.php?t=1752270
I think I got the idea, but just to double check, is this what I need to do after every time I install a custom ROM?
4. The partition files exist on the phone already, and I read some, so I have a basic understanding of it. But, the developer of the ROM I want to install says it is not necessary with that ROM, so hopefully that's true.
I am amazed by how different everything is from a HTC phone to another HTC phone even when they seem so similar!
A quick question. Does EXT4 exist for HTC One S? I used to use that for HTC Sensation and loved it. I'm guessing no, but I thought I'd ask.
So, to sum it up, is this what I need to do?
1. Flash TWRP recovery (please tell me how to find the right version for S4. all in one toolkit doesn't work on my phone).
2. Wipe everything and install the ROM
3. Flash boot.img
4. If wifi is not working, try the partition files
Please let me know if I got this right. Thank you,
goldentequila said:
Thank you for such a prompt reply. Here are some of my answers.
2. Yes, the ROM I want to install is this one: http://forum.xda-developers.com/showthread.php?t=2082451
It's the light version mentioned in that first post.
3. I just read up on this page: http://forum.xda-developers.com/showthread.php?t=1752270
I think I got the idea, but just to double check, is this what I need to do after every time I install a custom ROM?
4. The partition files exist on the phone already, and I read some, so I have a basic understanding of it. But, the developer of the ROM I want to install says it is not necessary with that ROM, so hopefully that's true.
I am amazed by how different everything is from a HTC phone to another HTC phone even when they seem so similar!
A quick question. Does EXT4 exist for HTC One S? I used to use that for HTC Sensation and loved it. I'm guessing no, but I thought I'd ask.
So, to sum it up, is this what I need to do?
1. Flash TWRP recovery (please tell me how to find the right version for S4. all in one toolkit doesn't work on my phone).
2. Wipe everything and install the ROM
3. Flash boot.img
4. If wifi is not working, try the partition files
Please let me know if I got this right. Thank you,
Click to expand...
Click to collapse
If the Toolkit can't see your phone then you might need to install the drivers that come with it for it to work.
goldentequila said:
Thank you for such a prompt reply. Here are some of my answers.
2. Yes, the ROM I want to install is this one: http://forum.xda-developers.com/showthread.php?t=2082451
It's the light version mentioned in that first post.
3. I just read up on this page: http://forum.xda-developers.com/showthread.php?t=1752270
I think I got the idea, but just to double check, is this what I need to do after every time I install a custom ROM?
4. The partition files exist on the phone already, and I read some, so I have a basic understanding of it. But, the developer of the ROM I want to install says it is not necessary with that ROM, so hopefully that's true.
I am amazed by how different everything is from a HTC phone to another HTC phone even when they seem so similar!
A quick question. Does EXT4 exist for HTC One S? I used to use that for HTC Sensation and loved it. I'm guessing no, but I thought I'd ask.
So, to sum it up, is this what I need to do?
1. Flash TWRP recovery (please tell me how to find the right version for S4. all in one toolkit doesn't work on my phone).
2. Wipe everything and install the ROM
3. Flash boot.img
4. If wifi is not working, try the partition files
Please let me know if I got this right. Thank you,
Click to expand...
Click to collapse
3. Yes, since your hboot is higher than 1.13, you will need to fastboot boot.img everytime you flash a ROM, unless you want to downgrade?
3.5: like Darknites said, you will need to install drivers for your the One S if you haven't already. You can download HTC Sync, and they'll install automatically [this is needed for being able to fastboot the boot.img]
4. They do exist, but everytime you wipe before flashing a ROM, they also get deleted, but try using the ROM without flashing the partition files and see if it works, if not then flash the partition files.
5. Yes, I'm pretty sure EXT4 exists with the One S, but am not 100% sure, maybe someone else can confirm this?
Lastly, here is where you download TWRP:
http://teamw.in/project/twrp2/100
scroll down and download the link for the S4 VARIANT, but you need to have drivers installed before doing this. and you will need to fastboot the recovery, since the download is an image: to do so, go into cmd, type cd c:\ (whatever your fastboot folder is called) and enter
then, type: fastboot flash [name of recovery, which is the name of the file you downloaded).img. Should take about 2 seconds to flash.
BTW, here are the drivers:
http://d-h.st/users/Inferi0r/?fld_id=2736#files
dr_rick13 said:
3. Yes, since your hboot is higher than 1.13, you will need to fastboot boot.img everytime you flash a ROM, unless you want to downgrade?
3.5: like Darknites said, you will need to install drivers for your the One S if you haven't already. You can download HTC Sync, and they'll install automatically [this is needed for being able to fastboot the boot.img]
4. They do exist, but everytime you wipe before flashing a ROM, they also get deleted, but try using the ROM without flashing the partition files and see if it works, if not then flash the partition files.
5. Yes, I'm pretty sure EXT4 exists with the One S, but am not 100% sure, maybe someone else can confirm this?
Lastly, here is where you download TWRP:
http://teamw.in/project/twrp2/100
scroll down and download the link for the S4 VARIANT, but you need to have drivers installed before doing this. and you will need to fastboot the recovery, since the download is an image: to do so, go into cmd, type cd c:\ (whatever your fastboot folder is called) and enter
then, type: fastboot flash [name of recovery, which is the name of the file you downloaded).img. Should take about 2 seconds to flash.
BTW, here are the drivers:
http://d-h.st/users/Inferi0r/?fld_id=2736#files
Click to expand...
Click to collapse
Ya 4EXT is coming soon.
dr_rick13 said:
3. Yes, since your hboot is higher than 1.13, you will need to fastboot boot.img everytime you flash a ROM, unless you want to downgrade?
3.5: like Darknites said, you will need to install drivers for your the One S if you haven't already. You can download HTC Sync, and they'll install automatically [this is needed for being able to fastboot the boot.img]
4. They do exist, but everytime you wipe before flashing a ROM, they also get deleted, but try using the ROM without flashing the partition files and see if it works, if not then flash the partition files.
5. Yes, I'm pretty sure EXT4 exists with the One S, but am not 100% sure, maybe someone else can confirm this?
Lastly, here is where you download TWRP:
http://teamw.in/project/twrp2/100
scroll down and download the link for the S4 VARIANT, but you need to have drivers installed before doing this. and you will need to fastboot the recovery, since the download is an image: to do so, go into cmd, type cd c:\ (whatever your fastboot folder is called) and enter
then, type: fastboot flash [name of recovery, which is the name of the file you downloaded).img. Should take about 2 seconds to flash.
BTW, here are the drivers:
http://d-h.st/users/Inferi0r/?fld_id=2736#files
Click to expand...
Click to collapse
Thank you so much. Yes, I tried installing the drivers using the toolkit's function, but I haven't tried HTC Sync option. Maybe that'll work better. I think I know what I need to do now. Thanks a bunch!
goldentequila said:
Thank you so much. Yes, I tried installing the drivers using the toolkit's function, but I haven't tried HTC Sync option. Maybe that'll work better. I think I know what I need to do now. Thanks a bunch!
Click to expand...
Click to collapse
Also try rebooting the computer if its still not working.
goldentequila said:
Thank you so much. Yes, I tried installing the drivers using the toolkit's function, but I haven't tried HTC Sync option. Maybe that'll work better. I think I know what I need to do now. Thanks a bunch!
Click to expand...
Click to collapse
Thank you, dr_rick13 and other kind members who responded to my call for help.
I was able to troubleshoot this, and now my phone's working the way I wanted it. Just one correction on dr_rick13's instruction:
then, type: fastboot flash [name of recovery, which is the name of the file you downloaded).img. Should take about 2 seconds to flash
recovery is missing in that line, so it should be fastboot flash recovery [name of recovery, which is the name of the file you downloaded).img
I know it was just a typo or forgot to write it, but I wanted to point this out in case some other user finds this thread and follows that instruction.
All in all, thanks for everything! You guys rock!
GT
goldentequila said:
Thank you, dr_rick13 and other kind members who responded to my call for help.
I was able to troubleshoot this, and now my phone's working the way I wanted it. Just one correction on dr_rick13's instruction:
then, type: fastboot flash [name of recovery, which is the name of the file you downloaded).img. Should take about 2 seconds to flash
recovery is missing in that line, so it should be fastboot flash recovery [name of recovery, which is the name of the file you downloaded).img
I know it was just a typo or forgot to write it, but I wanted to point this out in case some other user finds this thread and follows that instruction.
All in all, thanks for everything! You guys rock!
GT
Click to expand...
Click to collapse
oops, it was late last night when I wrote that.. my bad
Sent from my HTC One S using xda premium
I'm new here too. I understand that you need to flash the boot.img with that hboot, but why? And will it ever be fixed?
I've owned and rooted many a phones and never had to do that. Just curious why it's like that, and if it will be fixed. It's just easier to not be that way. Again, I'm new here, just trying to understand
Sent from my HTC Glacier using Tapatalk 2
pnut22r said:
I'm new here too. I understand that you need to flash the boot.img with that hboot, but why? And will it ever be fixed?
I've owned and rooted many a phones and never had to do that. Just curious why it's like that, and if it will be fixed. It's just easier to not be that way. Again, I'm new here, just trying to understand
Sent from my HTC Glacier using Tapatalk 2
Click to expand...
Click to collapse
we do not have S-OFF yet, so until we do.. people with hboots 1.13+ will need to flash boot.img. But HTC still hasn't said anything about when we will get S-OFF or if we will get it.
pnut22r said:
I'm new here too. I understand that you need to flash the boot.img with that hboot, but why? And will it ever be fixed?
I've owned and rooted many a phones and never had to do that. Just curious why it's like that, and if it will be fixed. It's just easier to not be that way. Again, I'm new here, just trying to understand
Sent from my HTC Glacier using Tapatalk 2
Click to expand...
Click to collapse
Its just the way HTC wants us to do it and maybe they feel it be better for us but mostly them. There is a way round it but you have to downgrade the Hboot.
Darknites said:
Its just the way HTC wants us to do it and maybe they feel it be better for us but mostly them. There is a way round it but you have to downgrade the Hboot.
Click to expand...
Click to collapse
Thanks. Is there any downside to downgrading the hboot? Why don't people do that instead?
When I had the Amaze, the recovery 4ext had "smart flash" which did this same thing because it was s-on
Sent from my HTC Glacier using Tapatalk 2
pnut22r said:
Thanks. Is there any downside to downgrading the hboot? Why don't people do that instead?
When I had the Amaze, the recovery 4ext had "smart flash" which did this same thing because it was s-on
Sent from my HTC Glacier using Tapatalk 2
Click to expand...
Click to collapse
Because of Linux and the fact you brick it to do it too. We meant to be getting 4ext but don't know when.
Darknites said:
Because of Linux and the fact you brick it to do it too. We meant to be getting 4ext but don't know when.
Click to expand...
Click to collapse
Thanks
http://forum.xda-developers.com/showthread.php?p=33233125
This seems like out would make things so much easier. I'm not always around a pc when wanting to flash things. If I use this, I should be able to flash away.
But what about resorting nandroids. This doesn't work with that. Hmmm
Just trying to wrap my mind around it
Sent from my HTC Glacier using Tapatalk 2
pnut22r said:
Thanks
http://forum.xda-developers.com/showthread.php?p=33233125
This seems like out would make things so much easier. I'm not always around a pc when wanting to flash things. If I use this, I should be able to flash away.
But what about resorting nandroids. This doesn't work with that. Hmmm
Just trying to wrap my mind around it
Sent from my HTC Glacier using Tapatalk 2
Click to expand...
Click to collapse
Yep very good app I did use it in till I downgraded.

How to apply OTA update on Rooted At&t One X

Hi,
I have this AT&T one x, (I m using on NON AT&T network), so cant have an ota update.
Looking at few forums, downloaded the OTA version on XDA (631 Mb)
Saw people writing, that just rename the file to update.zip and then go to recovery and choose install from internal memory.
That dint work for me.
Error: not able to mount sd mem
Then few people wrote to choose install from external mem.
That dint work either.
Error: not able to mount sd mem
Then saw few people saying that I need to root my device and unlock bootloader.
I dint that, and tried from bootlaoder to install from zip.
That also dint work.
Now saw, I few wrote that i need to be S - OFF.
Which I tried doing it, but i m not able to do s-off for myself.
Pls pls pls.... can any of you EXPERTs out here help me.
Waited like for AT&T to release the update, now when it is out, i m not able to make it through.
Your step by step instruction would be highly appreciable.
Be aware, that if you have the AT&T version, and you are rooted, then you probably have SuperCID (in fact, you must have SuperCID, unless it was already changed back). If you have SuperCID you must S-off (or return to the AT&T CID) before applying the OTA, or you will brick your phone!
I am not all that familiar with the process to install using OTA.zip (and haven't done it myself), but it was discussed in these threads:
http://forum.xda-developers.com/showthread.php?t=2180408
forum.xda-developers.com/showthread.php?t=1701460
redpoint73 said:
Be aware, that if you have the AT&T version, and you are rooted, then you probably have SuperCID (in fact, you must have SuperCID, unless it was already changed back). If you have SuperCID you must S-off (or return to the AT&T CID) before applying the OTA, or you will brick your phone!
I am not all that familiar with the process to install using OTA.zip (and haven't done it myself), but it was discussed in these threads:
http://forum.xda-developers.com/showthread.php?t=2180408
forum.xda-developers.com/showthread.php?t=1701460
Click to expand...
Click to collapse
How to S Off ATT HOX???
Thats the big question.
I have rooted my phone through one click TWRP Toolkit.
abhishek jain said:
How to S Off ATT HOX???
Thats the big question.
Click to expand...
Click to collapse
No, that is a very small question. Or at least a very easy one to answer.
Take 5 minutes to look around before asking "big" questions: http://forum.xda-developers.com/showthread.php?t=1671237
http://forum.xda-developers.com/showthread.php?t=2136172
If you would read my first post, I have already posted that I tried doing that was not able to do.
On the third comment that we need push in , where it given an error 92 or something like that, I dint got that.
Tried many times and then it became a "big" for me.
We all are born not experts in every field.
So before comenting pls try to know what's behind it
Sent from my HTC One X using xda app-developers app
Lol it doesn't take an expert to read and take five mins..this is probably one if the easiest s off methods you'll see for awhile... You probably didn't set up your adb fastboot environment up right
a box of kittens said:
Lol it doesn't take an expert to read and take five mins..this is probably one if the easiest s off methods you'll see for awhile... You probably didn't set up your adb fastboot environment up right
Click to expand...
Click to collapse
Changed my laptop and tried again.
Now I am S-OFF
THough I applied the same comments on three different machine.
4th Time it worked.
Now how to install this OTA updated which I have downlaoded
abhishek jain said:
Changed my laptop and tried again.
Now I am S-OFF
THough I applied the same comments on three different machine.
4th Time it worked.
Now how to install this OTA updated which I have downlaoded
Click to expand...
Click to collapse
Anyone to help me out in this case:
I am S OFF
Rooted
Unlocked bootloader
AT&T HOX on non AT&T network
631 mb update.zip
Looking top update
Rename file update.zip and copy to internal storage.
Reboot to bootloader and enter recovery.
Push power+ vol up when recovery screen appears to enter recovery dialog.
Ignore errors.
Select install from internal storage
Select update.zip
Phone will reboot a couple of times.
iElvis said:
Rename file update.zip and copy to internal storage.
Reboot to bootloader and enter recovery.
Push power+ vol up when recovery screen appears to enter recovery dialog.
Ignore errors.
Select install from internal storage
Select update.zip
Phone will reboot a couple of times.
Click to expand...
Click to collapse
I tried this method couple of time before : unlocking, rooting and S-off ing
In this case , do i need to relock my bootloader and stock recovery?
If yes, where can i find stock recovery, i have deleted it.
By "i deleted it" do you mean you installed a custom recovery? If so, yes you need to get stock recovery back on.
Only way I know of to reinstall stock recovery is to run the 2.20 ruu. Since you're s-off, you don't need to relock; just run it.
iElvis said:
By "i deleted it" do you mean you installed a custom recovery? If so, yes you need to get stock recovery back on.
Only way I know of to reinstall stock recovery is to run the 2.20 ruu. Since you're s-off, you don't need to relock; just run it.
Click to expand...
Click to collapse
I am not a techie but as far as i know, i have not installed a custom recovery.
I did TWRP tool kit, rooting and unlocking bootloader.
How can see if i am custom recovery or stock
abhishek jain said:
I am not a techie but as far as i know, i have not installed a custom recovery.
I did TWRP tool kit, rooting and unlocking bootloader.
How can see if i am custom recovery or stock
Click to expand...
Click to collapse
You probably have a custom recovery. Reboot to bootloader and select recovery and see what you get. If it's TWRP, you'll get a teamwin splash screen and then some options. Stock recovery will just show a screen with a green circle.
iElvis said:
You probably have a custom recovery. Reboot to bootloader and select recovery and see what you get. If it's TWRP, you'll get a teamwin splash screen and then some options. Stock recovery will just show a screen with a green circle.
Click to expand...
Click to collapse
Then I have custome recovery.
Could you gimme a link for stock recovery image
I do not know if one is available. I have never seen one posted. Running a ruu will put it back on.
iElvis said:
I do not know if one is available. I have never seen one posted. Running a ruu will put it back on.
Click to expand...
Click to collapse
Yes now i have got my phone updated with the OTA update
abhishek jain said:
Yes now i have got my phone updated with the OTA update
Click to expand...
Click to collapse
Please click "Thanks" if anyone in the thread helped you.
iElvis said:
Please click "Thanks" if anyone in the thread helped you.
Click to expand...
Click to collapse
I have already done that.
And now in case anyone needs help, i can help those people out.
Coz the method is simple, but it is not at all explained clearly in any of the threads.
It has come in bit and pieces.
I have noticed one thing.
That after installing the update and again unlockin the bootloader and rooting, I am not able to see "TAMPERED" being written in the boatloader.
Also, now when I am rooted and also have SU permission, I m not able to switch on my WiFi tether with the files mentioned in the thread
http://forum.xda-developers.com/showthread.php?t=1677261
The "TAMPERED" flag goes away when you're s-off and flash a new hboot.
I believe wifi tether is blocked on the new AT&T base. You can flash a custom rom on the 3.17 base and it should work.

[Q] I Soft Bricked my HTC One M8

Hey guys,
Tonight I went to install cleanrom on my Verizon HTC One M8. I made a nandroid backup as I always do before flashing a new ROM and then proceeded to flash the new ROM. That went great but then I did something I wouldn't normally do I wiped my data just because I wanted a fresh start and all of my important stuff was backed up online. But when I went to boot I'm stuck on the HTC logo. I have an OTG cable so I proceeded to put the ROM on a flash drive and flash it. Same problem. So I put my old ROM ViperOne 2.4 on the flash drive and flashed it. Now I instantly boot into fastboot. This all seems really strange to me but I'm sure its caused by me stupidly formatting data. I need a bigger flash drive to install the original nandroid backup I found online so I will get one today and post my results. I'm almost positive that will fix my problem but I know there might be an HTC guru out there that knows exactly what my problem is and it may be more then what I'm thinking. Sorry this is scattered ive been messing with my phone all night and kinda tired now. Any help is greatly appreciated and thank you in advance for taking time to help me with this issue. And if I missed anything let me know and I will be sure to post it.
Edit
Sorry I completely forgot to add that I put my nandroid backup on my flash drive but when I went to use it it did not work. I believe this is because I did not have a big enough flash drive so it did not completely back up. LOL! Tonight was not my night.
radiowavedev said:
Hey guys,
Tonight I went to install cleanrom on my Verizon HTC One M8. I made a nandroid backup as I always do before flashing a new ROM and then proceeded to flash the new ROM. That went great but then I did something I wouldn't normally do I wiped my data just because I wanted a fresh start and all of my important stuff was backed up online. But when I went to boot I'm stuck on the HTC logo. I have an OTG cable so I proceeded to put the ROM on a flash drive and flash it. Same problem. So I put my old ROM ViperOne 2.4 on the flash drive and flashed it. Now I instantly boot into fastboot. This all seems really strange to me but I'm sure its caused by me stupidly formatting data. I need a bigger flash drive to install the original nandroid backup I found online so I will get one today and post my results. I'm almost positive that will fix my problem but I know there might be an HTC guru out there that knows exactly what my problem is and it may be more then what I'm thinking. Sorry this is scattered ive been messing with my phone all night and kinda tired now. Any help is greatly appreciated and thank you in advance for taking time to help me with this issue. And if I missed anything let me know and I will be sure to post it.
Click to expand...
Click to collapse
Did you flash newest "firmware" as well? The 2.xx.xxx.x ROM's need newest firmware to boot correctly. (Radio, hboot). Old hboot would cause it to hang at boot.
When I flash ROMs in TWRP I go into advanced and check data, dalvik cache, system, and data every time, never had an issue.
andybones said:
When I flash ROMs in TWRP I go into advanced and check data, dalvik cache, system, and data every time, never had an issue.
Click to expand...
Click to collapse
+1
andybones said:
When I flash ROMs in TWRP I go into advanced and check data, dalvik cache, system, and data every time, never had an issue.
Click to expand...
Click to collapse
That is why this was so strange to me. The hboot firmware sounds promising though.
bigblueshock said:
Did you flash newest "firmware" as well? The 2.xx.xxx.x ROM's need newest firmware to boot correctly. (Radio, hboot). Old hboot would cause it to hang at boot.
Click to expand...
Click to collapse
Thank you for the response. I never even knew it was necessary to flash hboot. I've flashed a couple of ROMs before and never flashed hboot. I will try this tonight. Is this just as simple as flashing a zip? And I pick the newest available version?
radiowavedev said:
Thank you for the response. I never even knew it was necessary to flash hboot. I've flashed a couple of ROMs before and never flashed hboot. I will try this tonight. Is this just as simple as flashing a zip? And I pick the newest available version?
Click to expand...
Click to collapse
not just hboot my friend.
the whole firmware.
if you were to take the OTA you would get this firmware installed.
since we are S-OFF and we don't want to take the OTA, as it's MUCH easier to just fastboot the firmware.zip once someone takes the OTA and pulls all the needed files..
here is the thread you want - here
here is a direct copy and paste from the thread full credit to the OP
"4.4.3 DOWNLOADS BELOW no boot or recovery included in this (what this means is that you won't have to re-flash a custom recovery after the firmware, they removed it to make things easier on us.)
https://www.androidfilehost.com/?fid=23622183712470028
CREDIT TO dottat as he posted it 1st so no need for me too well just use his. Be sure to thank him if you see if around.
Flash via fastboot or Sd card method. Flash at your own risk.
directions for flashing firmware via fastboot an radios below.
Place the zip in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip firmware.zip (rename file to firmware.zip)
It will say that the update did not finish, to flush again, so repeat the above step:
fastboot flash zip firmware.zip
Then fastboot reboot-bootloader��
FYI on my m8 i did not need to be reflushed on 1.55 but on the new update it did.
credit for these directions also come from santod "
andybones said:
not just hboot my friend.
the whole firmware.
if you were to take the OTA you would get this firmware installed.
since we are S-OFF and we don't want to take the OTA, as it's MUCH easier to just fastboot the firmware.zip once someone takes the OTA and pulls all the needed files..
here is the thread you want - here
here is a direct copy and paste from the thread full credit to the OP
"4.4.3 DOWNLOADS BELOW no boot or recovery included in this (what this means is that you won't have to re-flash a custom recovery after the firmware, they removed it to make things easier on us.)
https://www.androidfilehost.com/?fid=23622183712470028
CREDIT TO dottat as he posted it 1st so no need for me too well just use his. Be sure to thank him if you see if around.
Flash via fastboot or Sd card method. Flash at your own risk.
directions for flashing firmware via fastboot an radios below.
Place the zip in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip firmware.zip (rename file to firmware.zip)
It will say that the update did not finish, to flush again, so repeat the above step:
fastboot flash zip firmware.zip
Then fastboot reboot-bootloader��
FYI on my m8 i did not need to be reflushed on 1.55 but on the new update it did.
credit for these directions also come from santod "
Click to expand...
Click to collapse
Thank you for all of the useful information I will give this a shot tonight.
radiowavedev said:
Thank you for all of the useful information I will give this a shot tonight.
Click to expand...
Click to collapse
Quite welcome, be sure to go into the thread I posted and thank them, it's all their words, I simply copy and pasted it for you.
andybones said:
Quite welcome, be sure to go into the thread I posted and thank them, it's all their words, I simply copy and pasted it for you.
Click to expand...
Click to collapse
Yeah I'm quite used to the ways of XDA but honestly had no idea about hboot. And I definitely will be thanking them. I'm now home and will test it out. I'll post my results afterwards.
andybones said:
Quite welcome, be sure to go into the thread I posted and thank them, it's all their words, I simply copy and pasted it for you.
Click to expand...
Click to collapse
Okay so I downloaded m8.443.firmware.zip does this have to be flashed via fastboot? And once I flash it should I flash my custom rom cleanrom 2.0 rc and that should be it for my issue?
radiowavedev said:
Okay so I downloaded m8.443.firmware.zip does this have to be flashed via fastboot? And once I flash it should I flash my custom rom cleanrom 2.0 rc and that should be it for my issue?
Click to expand...
Click to collapse
well in bootloader/fastboot yes.. but you DO NOT run the fastboot command..
this is exactly what you do
1) the file you downloaded, m8.443.firmware.zip - rename this to firmware.zip
2) adb reboot bootloader (or however you get there)
3) fastboot oem rebootRUU - this is the important part you will be brought to a black screen with a gray HTC logo IIRC, run the next command - the green bar may stop 3/4 of the way this is because you when you run the last command it will finish it.
4) fastboot flash zip firmware.zip
5) fastboot reboot-bootloader
Im sorry this might be stupid but what do you mean by not running fastboot command? And you say reboot-bootloader shouldn't I do reboot-recovery and flash my custom rom after factory resetting of course. Sorry im just trying to make sure im thorough. I would think messing up hboot would permanently brick my phone.
andybones said:
well in bootloader/fastboot yes.. but you DO NOT run the fastboot command..
this is exactly what you do
1) the file you downloaded, m8.443.firmware.zip - rename this to firmware.zip
2) adb reboot bootloader (or however you get there)
3) fastboot oem rebootRUU - this is the important part you will be brought to a black screen with a gray HTC logo IIRC, run the next command - the green bar may stop 3/4 of the way this is because you when you run the last command it will finish it.
4) fastboot flash zip firmware.zip
5) fastboot reboot-bootloader
Click to expand...
Click to collapse
Would it just be easier to use a nandroid backup?
I figure in the meantime ill fill you in on everything I know about my phone. I was previously running the newest version of ViperOne which was 2.5.0 This problem came up after flashing cleanrom 2.0 RC. I am S-off and unlocked of course and I am running CWM-based Recovery v6.0.4.8 and my hboot stats are as follows:
***UNLOCKED***
M8_WLV PVT SHIP S-OFF
CID-VZW__001
HBOOT-3.16.0.0000
RADIO-0.89.20.0321
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.55.605.2
eMMC-boot 2048MB
I have searched the forums looking for anything related to my issue and cant seem to come up with anything. I have come across a few people with the same issues as me but there questions go unanswered which makes me very nervous... I do believe it is related to my hboot firmware but I cant seem to find a thorough explanation of hboot. Sorry I am a former Motorola guy. This HTC stuff is really mixing it up for me. LOL!
I really appreciate all of the help you have given me and am grateful that you are hanging in with my HTC stupidity and phobia of bricking this 700 dollar piece of aluminum and magnesium.
radiowavedev said:
I figure in the meantime ill fill you in on everything I know about my phone. I was previously running the newest version of ViperOne which was 2.5.0 This problem came up after flashing cleanrom 2.0 RC. I am S-off and unlocked of course and I am running CWM-based Recovery v6.0.4.8 and my hboot stats are as follows:
***UNLOCKED***
M8_WLV PVT SHIP S-OFF
CID-VZW__001
HBOOT-3.16.0.0000
RADIO-0.89.20.0321
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.55.605.2
eMMC-boot 2048MB
I have searched the forums looking for anything related to my issue and cant seem to come up with anything. I have come across a few people with the same issues as me but there questions go unanswered which makes me very nervous... I do believe it is related to my hboot firmware but I cant seem to find a thorough explanation of hboot. Sorry I am a former Motorola guy. This HTC stuff is really mixing it up for me. LOL!
I really appreciate all of the help you have given me and am grateful that you are hanging in with my HTC stupidity and phobia of bricking this 700 dollar piece of aluminum and magnesium.
Click to expand...
Click to collapse
Separate the terminology "ROM" and "Firmware" for a moment. Firmware should/will never change regardless of what ROM's you flash. Think of firmware as a computers BIOS, And ROM as your computers operating system.
First, turn your phone off. Second, hold volume down + power button and do NOT let go of volume down until you're in the boot loader screen. Step 3) switch the boot loader into fast boot within that screen(Fast boot or fast boot USB may come up by default it will be highlighted in red). If you're plugged up to your computer via USB, it should automatically say "Fastboot USB". Then you can execute the commands in the command prompt andybones was talking about.
Did i loose you anywhere?
You could just nandroid back to your previous ROM... but that defeats the purpose. You'll never be able to go to a newer Sense ROM without the firmware upgrade anyway. You might as well get it done because it may improve your network signal, boot times, etc. Usually only benefits you,
After you upgrade firmware, it will say hboot 3.18.0000, Radio: 1.09.20.0702,
radiowavedev said:
Would it just be easier to use a nandroid backup?
Click to expand...
Click to collapse
I didn't just waste my time to write you up a STEP BY STEP FOOL proof guide.
I am not doing this for my benefit...
You made a thread.
You asked for help.
I gave detailed, if you mess up you didn't follow them exactly..
Why would you have me give you exact directions to fix your phone, then ask about a nandroid?
NO. If it were that simple my friend, don't you think I would have let you known this?
I'm sorry if this comes off rude, but I went out of my way to give you exact detailed instructions and you blow them off.
Why make a thread and then not take the advice from a Recognized Contributor to this site!?
I hope you can understand how frustrating this is.
I don't do this because it's fun for me to help get your phone fixed, I do it because you asked for help, and I like to help, but when my help goes un-heard and blown off - I walk away. - Best of luck my friend.
I am still going to help because that's the kind of guy I am..
Run the RUU since you are S-OFF if nothing else works.
You are a SOFT-brick. Very easy to fix.
Andybones, I totally understand. I wasnt trying to be rude im just confused and trying to come up with ideas. I understand it was dumb to mention the nandroid now. I hope you can accept my sincerest apology. I appreciate everything you have done for me and understand if you dont want to help me any longer. Like I said it was not my intention to be rude but I see how it can look like that. I just dont know what im doing.
Hi there, I believe I may have been in the same position as you at some point. What actually is happening is that you are trying to flash a new ROM (4.4.3 I believe) with the old hboot. The ROM should still boot but it will take up to 20min.
How to fix this:
1. Boot into boot loader, (manually or adb)
2. Choose fastboot
3. Connect to USB
4. Open command prompt
5. Fastboot devices
6. fastboot oem rebootRUU
7. You should see a black screen with a dark HTC logo.
8. fastboot flash zip (nameofzip).zip
9. When it finishes type fastboot reboot-bootloader (hyphen required)
10. You just flashed the new firmware but it has no os. You now need to flash a ROM or restore a nandroid backup.
Sent from my HTC One M8 GPE converted using XDA Premium mobile app

Categories

Resources