Database Info

[Q] PLEASE HELP! random rebooting about every 5 min

random rebooting after flashing CM9 nightly roms. seems to be some kind of bug every time i start an application or turn on mobile data it cuases a reboot. i have flashed all of the following roms in an attempt to fix the problem:
PkMn ROM 4.1 Charmander
OrDroid V6.0.0
and the latest official cyanogenmod nightly
i did a restore to an ics lee droid rom i previously backed up before
and it seemed to run without a problem but after that i re flashed PkMn ROM for the sensation and now it performs a hot reboot instead. if anyone could help it would be greatly apprieciated as the problem seems to worsen after every reboot.
some times it would just go into a bootloop.

bryancruzdr said:
random rebooting after flashing CM9 nightly roms. seems to be some kind of bug every time i start an application or turn on mobile data it cuases a reboot. i have flashed all of the following roms in an attempt to fix the problem:
PkMn ROM 4.1 Charmander
OrDroid V6.0.0
and the latest official cyanogenmod nightly
i did a restore to an ics lee droid rom i previously backed up before
and it seemed to run without a problem but after that i re flashed PkMn ROM for the sensation and now it performs a hot reboot instead. if anyone could help it would be greatly apprieciated as the problem seems to worsen after every reboot.
some times it would just go into a bootloop.
Click to expand...
Click to collapse
I think some partition is still corrupted.. I recommend you to do a wipe from recovery rather than scripts (if using 4ext then wipe/format ->>format all partitions except sdcard) and then flash another rom Again
If that didn't solved the issue RUU is the next thing.. If you are soff and supercid then get any ics RUU and run it.. It completely formats through phone and takes everything to stock.. But still retains soff.. So you revert back to normal once you do a ruu run(remember ruu run should be done with device in fastboot)
Sent from my pyramid.. Through blazing fast sonic waves

Thank You so much!
i will try this, but which RUU do you recommend i run?

bryancruzdr said:
Thank You so much!
i will try this, but which RUU do you recommend i run?
Click to expand...
Click to collapse
RUU is just to clean the partitions.. So just get any.. If you want one get the Europe umbranded one(latest)
Check in pyramid shipped rom collections thread in sensation Android Development section
Sent from my pyramid.. Through blazing fast sonic waves

Before you look into a partition problem, which is a pain to fix, check to make sure the battery is securely seated in the phone.
The batteries can become loose over time. Not very loose, but just enough to break electrical contact. And if the electrical contact is broken and restored quickly, a reboot is likely.
Open the phone and see if the battery wiggled. See if you can create the reboot problem by jiggling the battery. If you can, there are a few things to try to make the battery tighter.

Skipjacks said:
Before you look into a partition problem, which is a pain to fix, check to make sure the battery is securely seated in the phone.
The batteries can become loose over time. Not very loose, but just enough to break electrical contact. And if the electrical contact is broken and restored quickly, a reboot is likely.
Open the phone and see if the battery wiggled. See if you can create the reboot problem by jiggling the battery. If you can, there are a few things to try to make the battery tighter.
Click to expand...
Click to collapse
Thanks for your suggestion. i saw a post on this yesturday, and this doesnt seem to be my issue, althought i tried the trick that is mentioned on the post, about putting a business card to make it tighter, and it deffinitely made it very tight, but the issue remained. thanks for your help though
such a friendly and helpful community

bryancruzdr said:
random rebooting after flashing CM9 nightly roms. seems to be some kind of bug every time i start an application or turn on mobile data it cuases a reboot. i have flashed all of the following roms in an attempt to fix the problem:
PkMn ROM 4.1 Charmander
OrDroid V6.0.0
and the latest official cyanogenmod nightly
i did a restore to an ics lee droid rom i previously backed up before
and it seemed to run without a problem but after that i re flashed PkMn ROM for the sensation and now it performs a hot reboot instead. if anyone could help it would be greatly apprieciated as the problem seems to worsen after every reboot.
some times it would just go into a bootloop.
Click to expand...
Click to collapse
I always use super wipe when flashing new roms
Sent from my HTC Sensation using xda premium

OreoBoyVa said:
I always use super wipe when flashing new roms
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
Formatting all partitions is better than SuperWipe. It will ensure everything is completely cleaned out.

ganeshp said:
RUU is just to clean the partitions.. So just get any.. If you want one get the Europe umbranded one(latest)
Check in pyramid shipped rom collections thread in sensation Android Development section
Sent from my pyramid.. Through blazing fast sonic waves
Click to expand...
Click to collapse
While Running RUU i get "Error [156] Image Error" ive downloaded atleast 4 different ics ruu's and get the same error. perhaps this is the initial problem?

bryancruzdr said:
While Running RUU i get "Error [156] Image Error" ive downloaded atleast 4 different ics ruu's and get the same error. perhaps this is the initial problem?
Click to expand...
Click to collapse
no no are you SOFF ?
if you are not SOFF but has unlocked bootloader..then relock it before running RUU
(fastboot oem lock)
then run the RUU..with phone connected in bootloader

i am s-off
if it helps heres what it says on the bootloader:
-Revolutionary-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.22.3504.07_M
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
i put it on fastboot and connect it to my computer when running RUU. am i missing anything?

bryancruzdr said:
i am s-off
if it helps heres what it says on the bootloader:
-Revolutionary-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.22.3504.07_M
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
i put it on fastboot and connect it to my computer when running RUU. am i missing anything?
Click to expand...
Click to collapse
ok we do it different way then
first extract the rom.zip from any ICS RUU (choose one )
here is the guide to extract the rom.zip
http://www.htcsensationforum.com/htc-sensation-rooting/how-to-extract-rom-zip-from-ruu/
then keep the rom.zip in adb folder
keep the phone in fastboot
and connect it to pc (mobile reads "fastboot usb")
now type these commands one by one
1.fastboot erase cache
2.fastboot oem rebootRUU
3.fastboot flash zip rom.zip
4.fastboot reboot
if worked fine otherwise
im particularly interested in the complete output of the third command
so use PASTEBIN to paste the output and then repost the url with the pasted output

ganeshp said:
no no are you SOFF ?
if you are not SOFF but has unlocked bootloader..then relock it before running RUU
(fastboot oem lock)
then run the RUU..with phone connected in bootloader
Click to expand...
Click to collapse
Check point 4 of my RUU guide. You can link all such questions there. Detailed explanation & methods.
I'm just suggesting because you gave him a very short explanation.
EDIT: Sorry, I probably didn't see that this is solved.
ganeshp said:
keep the phone in fastboot
and connect it to pc (mobile reads "fastboot usb")
now type these commands one by one
1.fastboot erase cache
2.fastboot oem rebootRUU
3.fastboot flash zip rom.zip
4.fastboot reboot
Click to expand...
Click to collapse
Some questions. The method from above is the same one used for flashing engineering bootloader after JB S Off
So, what exactly is this RUU mode? And does it bypass CID and fw version checks?
Also, what are the requirements for this mode to work (i.e. S-Off, unlocked bootloader)?
What are the benefits of using this over renaming rom.zip to PG58IMG.zip and flashing?
Thanks a lot for this. It will surely come in handy sometime & will definitely go into my guide.

kgs1992 said:
Some questions. The method from above is the same one used for flashing engineering bootloader after JB S Off
So, what exactly is this RUU mode? And does it bypass CID and fw version checks?
Also, what are the requirements for this mode to work (i.e. S-Off, unlocked bootloader)?
What are the benefits of using this over renaming rom.zip to PG58IMG.zip and flashing?
Thanks a lot for this. It will surely come in handy sometime & will definitely go into my guide.
Click to expand...
Click to collapse
its the same way as flashing via PG58IMG way
to bluntly say the PG58IMG flashing ..internally does the flashing the same way I've put it
RUU mode is the lowest level(visible) mode where flashing of bootloader,firmware,radio and even ROM is possible but the file format should be of PG58IMG zip
so simply put any PG58IMG.zip file which is not being parsed by bootloader properly can be manually flashed the above way
the same requirements that apply for PG58IMG.zip file applies over here too
i.e SOFF (irrespective of type of bootloader)
or unlocked bootloader with SON ...(remember in this case as only recovery,boot,data,system partitions are opened only those partitions can be flashed )

ganeshp said:
its the same way as flashing via PG58IMG way
to bluntly say the PG58IMG flashing ..internally does the flashing the same way I've put it
RUU mode is the lowest level(visible) mode where flashing of bootloader,firmware,radio and even ROM is possible but the file format should be of PG58IMG zip
so simply put any PG58IMG.zip file which is not being parsed by bootloader properly can be manually flashed the above way
the same requirements that apply for PG58IMG.zip file applies over here too
i.e SOFF (irrespective of type of bootloader)
or unlocked bootloader with SON ...(remember in this case as only recovery,boot,data,system partitions are opened only those partitions can be flashed )
Click to expand...
Click to collapse
Thanks a lot Ganesh! Very useful info. So you mean that in this mode CID check is bypassed. That's nice.

kgs1992 said:
Thanks a lot Ganesh! Very useful info. So you mean that in this mode CID check is bypassed. That's nice.
Click to expand...
Click to collapse
no please don't get me wrong
at the end the zip we are flashing requires android-info.txt too (PG58IMG.zip has it too) which has cid and mid to it
the cid check is bypassed only when you are SOFF or has unlocked bootloader (for unlocked bootloader ..we still require cid signed radio,hboot (firmware) to update them via this method ..this is required as they are still secured [SON])
the above way of flashing gives you much more detail of whats happening when on command prompt..where we can identify the problem ..when flashing RUU..precisely

ganeshp said:
no please don't get me wrong
at the end the zip we are flashing requires android-info.txt too (PG58IMG.zip has it too) which has cid and mid to it
the cid check is bypassed only when you are SOFF or has unlocked bootloader (for unlocked bootloader ..we still require cid signed radio,hboot (firmware) to update them via this method ..this is required as they are still secured [SON])
the above way of flashing gives you much more detail of whats happening when on command prompt..where we can identify the problem ..when flashing RUU..precisely
Click to expand...
Click to collapse
Thanks for the clarifications. I will add it to the guide because this is really a nice method.

[Q] Phone stuck in a boot loop, plus other problems

My phone, HTC Sensation XE, is S-ON, on default ROM, and has HBOOT 1.29.000. Needless to say, my phone is not rooted.
The phone is on a boot loop ever since I last took off the battery and placed it back. I sometimes get a message that my Android system is getting upgraded, terminating with an error "System UI has stopped working" before the phone restarts itself again.
I don't know if this is a hardware issue or software.
How do I get my phone to a normal state? I don't mind rooting the phone if I need to for the purpose of installing default/custom ROM. But I don't know if this would be possible because I only have access to boot screen at present.
Please suggest me suitable solutions. Thank you

jiteshgawali said:
My phone, HTC Sensation XE, is S-ON, on default ROM, and has HBOOT 1.29.000. Needless to say, my phone is not rooted.
The phone is on a boot loop ever since I last took off the battery and placed it back. I sometimes get a message that my Android system is getting upgraded, terminating with an error "System UI has stopped working" before the phone restarts itself again.
I don't know if this is a hardware issue or software.
How do I get my phone to a normal state? I don't mind rooting the phone if I need to for the purpose of installing default/custom ROM. But I don't know if this would be possible because I only have access to boot screen at present.
Please suggest me suitable solutions. Thank you
Click to expand...
Click to collapse
if you are completely stock then i think you only option is to use a ruu.exe
http://forum.xda-developers.com/showthread.php?t=1672425
find the one which corresponds with your region and cid

rzr86 said:
if you are completely stock then i think you only option is to use a ruu.exe
http://forum.xda-developers.com/showthread.php?t=1672425
find the one which corresponds with your region and cid
Click to expand...
Click to collapse
Thanks rzr86
I looked into the thread you suggested. For my region and CID, I was not able to get the RUU from the thread. What I could get was this - an OTA zip file that matches my software version exactly (3.33.720.106) from this thread: http://forum.xda-developers.com/showthread.php?t=1764025
How do I proceed further with this zip file, since I don't have an executable RUU file?
I am hoping you can be of help -)
(The zip file contains -- META-INF, patch, system, firmware.zip, fotaBoot, version.txt)

Get s off
Install custom recovery(4ext)
and flash any ics / jelly bean custom Rom

Itsakash said:
Get s off
Install custom recovery(4ext)
and flash any ics / jelly bean custom Rom
Click to expand...
Click to collapse
I was of the same opinion itsakash, but I am not sure if I can SOFF from the bootloader screen because I have only that option available with me. Can you please refer to me a good guide on this forum where I can SOFF from bootloader?

jiteshgawali said:
I was of the same opinion itsakash, but I am not sure if I can SOFF from the bootloader screen because I have only that option available with me. Can you please refer to me a good guide on this forum where I can SOFF from bootloader?
Click to expand...
Click to collapse
Yes u can s off from bootloader
Use KGS utility or ganeshp one click root. ,s off method Check general section in sensation forum
Connect mobile to pc on bootloader screen( mobile should say fastboot USB )
And follow instruction carefully
:thumbup:

Itsakash said:
Yes u can s off from bootloader
Use KGS utility or ganeshp one click root. ,s off method Check general section in sensation forum
Connect mobile to pc on bootloader screen( mobile should say fastboot USB )
And follow instruction carefully
:thumbup:
Click to expand...
Click to collapse
When I try and do SOFF using KGS utility, it restarts my phone because my phone is not HTC dev unlocked. (My phone's motherboard was replaced some time ago, and so I cannot unlock my phone.)
ganeshp's one click root requires SOFF. I can't SOFF using his technique because temp_root.bat doesn't work in bootloader screen.
I am in trouble, and don't look like getting out of it

jiteshgawali said:
When I try and do SOFF using KGS utility, it restarts my phone because my phone is not HTC dev unlocked. (My phone's motherboard was replaced some time ago, and so I cannot unlock my phone.)
ganeshp's one click root requires SOFF. I can't SOFF using his technique because temp_root.bat doesn't work in bootloader screen.
I am in trouble, and don't look like getting out of it
Click to expand...
Click to collapse
@ganeshp's one click root doesn't require htc dev unlock (meaning no prequisite permanent root; the guide has steps for temproot).
You just need one boot.
Do this: get the boot.img of your current (stock rom) and type fastboot boot boot.img.

jiteshgawali said:
My phone, HTC Sensation XE, is S-ON, on default ROM, and has HBOOT 1.29.000. Needless to say, my phone is not rooted.
The phone is on a boot loop ever since I last took off the battery and placed it back. I sometimes get a message that my Android system is getting upgraded, terminating with an error "System UI has stopped working" before the phone restarts itself again.
I don't know if this is a hardware issue or software.
How do I get my phone to a normal state? I don't mind rooting the phone if I need to for the purpose of installing default/custom ROM. But I don't know if this would be possible because I only have access to boot screen at present.
Please suggest me suitable solutions. Thank you
Click to expand...
Click to collapse
I know its a long shot, but you should try doing a factory-reset from the bootloader, just in case it works.
Otherwise run an RUU from the bootloader.

firstly Itsakash he can't S-OFF because the device must be booted to the OS
secondly Far_SighT the command is fastboot flash boot boot.img
thirdly as raz0rf1sh suggested factory reset is a good idea and
fourthly jiteshgawali can you post your bootloader details?

It really is great to see your input guys.
@Far_SighT: I have tried doing the temp_root method, but it doesn't work for me. I could successfully run temp_root.bat just once (luckily, even in boot loop), but next when I tried doing the Juopunutbear SOFF it missed detecting my phone (again, because of the bootloop)
I don''t know where I can get a boot.img file from; for what it's worth, I could only get an OTA zip file for my region/CID from this thread: http://forum.xda-developers.com/showthread.php?t=1764025
@raz0rf1sh: I have done factory reset several times from bootloader, doesn't help friend. I don't have an RUU for my region/CID, all I have is an OTA zip file for my phone from the link I have specified right above this. Can't seem to get an RUU for firmware base 3.33, and CID HTC__038.
@rzr86: Posting all the details I am aware of currently:
PYRAMID PVT SHIP S-ON RL
HBOOT - 1.29.0000
eMMC-boot
Mar 2 2012, 18:14:34
CID - HTC__038
Software version - 3.33.720.106

rzr86 said:
firstly Itsakash he can't S-OFF because the device must be booted to the OS
secondly Far_SighT the command is fastboot flash boot boot.img
thirdly as raz0rf1sh suggested factory reset is a good idea and
fourthly jiteshgawali can you post your bootloader details?
Click to expand...
Click to collapse
Nope
Not necessary to boot into os for s off

Itsakash said:
Nope
Not necessary to boot into os for s off
Click to expand...
Click to collapse
It would help if you can tell me how to do this or direct me to any specific guide

jiteshgawali said:
I have tried doing the temp_root method, but it doesn't work for me. I could successfully run temp_root.bat just once (luckily, even in boot loop), but next when I tried doing the Juopunutbear SOFF it missed detecting my phone (again, because of the bootloop)
Click to expand...
Click to collapse
Did u connected mobile to pc from bootloader??
If yes then I'm helpless may b rzr was right
But in s off section I read somewhere that it doesn't require boot into android
Anyway do PM to Ganeshp he is good guy. I'm damn sure he will help u

jiteshgawali said:
I don''t know where I can get a boot.img file from; for what it's worth, I could only get an OTA zip file for my region/CID from this thread: http://forum.xda-developers.com/showthread.php?t=1764025
Click to expand...
Click to collapse
For stock rom go http://forum.xda-developers.com/showthread.php?t=1923629.
Get the rom and extract boot.img.
Then use the earlier command I posted.

Yes I haven't seen Indian version ruu until now ..so ruu is out of question AFAIK
Now the factory reset over boot loader should help if you have software problems but as per your replies it didn't work it seems
Tried HTC Dev unlock ? Even if the motherboard is replaced its worth a try
If htcdev unlock failed
Then try to go to recovery first ..from boot loader and if you went to recovery properly let me know
The other solution I propose is try to do change the cid ..even on locked bootloader sometimes it works
Try these commands one by one
fastboot oem writecid HTC__001
Then
fastboot reboot-bootloader
Then check cid using this command
fastboot getvar cid
If cid changed that's a good sign
Sent from my Nexus 7 using XDA Premium 4 mobile app

rzr86 said:
secondly Far_SighT the command is fastboot flash boot boot.img
Click to expand...
Click to collapse
I said fastboot boot boot.im instead of fastboot flash boot booti.img as the previous one boots the rom with with the new image but doesn't attempt to write that to the boot partition. Hence it might get him a much needed boot to s-off.

jiteshgawali said:
It really is great to see your input guys.
@Far_SighT: I have tried doing the temp_root method, but it doesn't work for me. I could successfully run temp_root.bat just once (luckily, even in boot loop), but next when I tried doing the Juopunutbear SOFF it missed detecting my phone (again, because of the bootloop)
I don''t know where I can get a boot.img file from; for what it's worth, I could only get an OTA zip file for my region/CID from this thread: http://forum.xda-developers.com/showthread.php?t=1764025
@raz0rf1sh: I have done factory reset several times from bootloader, doesn't help friend. I don't have an RUU for my region/CID, all I have is an OTA zip file for my phone from the link I have specified right above this. Can't seem to get an RUU for firmware base 3.33, and CID HTC__038.
@rzr86: Posting all the details I am aware of currently:
PYRAMID PVT SHIP S-ON RL
HBOOT - 1.29.0000
eMMC-boot
Mar 2 2012, 18:14:34
CID - HTC__038
Software version - 3.33.720.106
Click to expand...
Click to collapse
as you stated your current is 3.33.720.106 so the OTA update is unnecessary
do as ganeshp suggested
Itsakash said:
Did u connected mobile to pc from bootloader??
If yes then I'm helpless may b rzr was right
But in s off section I read somewhere that it doesn't require boot into android
Anyway do PM to Ganeshp he is good guy. I'm damn sure he will help u
Click to expand...
Click to collapse
both S-OFF guides say that stock rom is required in order to follow the S-OFF procedure

ganeshp said:
Yes I haven't seen Indian version ruu until now ..so ruu is out of question AFAIK
Now the factory reset over boot loader should help if you have software problems but as per your replies it didn't work it seems
Tried HTC Dev unlock ? Even if the motherboard is replaced its worth a try
If htcdev unlock failed
Then try to go to recovery first ..from boot loader and if you went to recovery properly let me know
The other solution I propose is try to do change the cid ..even on locked bootloader sometimes it works
Try these commands one by one
fastboot oem writecid HTC__001
Then
fastboot reboot-bootloader
Then check cid using this command
fastboot getvar cid
If cid changed that's a good sign
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for responding Ganesh. HTC Dev Unlock never worked for me post change of motherboard, but thanks for the suggestion.
I am able to browse the recovery option from bootloader properly.
And it gives me a little satisfaction to let you know that I was able to change the CID to HTC__001 following your steps. Can you suggest what I should be doing next?

jiteshgawali said:
Thanks for responding Ganesh. HTC Dev Unlock never worked for me post change of motherboard, but thanks for the suggestion.
I am able to browse the recovery option from bootloader properly.
And it gives me a little satisfaction to let you know that I was able to change the CID to HTC__001 following your steps. Can you suggest what I should be doing next?
Click to expand...
Click to collapse
Great now just download the HTC wwe ruu and install it... I'll link it up in a second.. Watch this space
Here is the link
http://htc.vi8.info/Sensation-XE/RU...0U-11.24A.3504.31-M-release-281004-signed.exe
Sent from my HTC Sensation 4G using XDA Premium 4 mobile app

Need serious Help concerning roms

Hey guys,
I have a serious problem with my at&t htc one x, first time when i wanted to install a custom rom, i didn't backup ( i know my fault)
i had some problems with installation that drives me to change my cid to HTC_621 ( i don't know why i changed the 1st time, im noob)
now i can only install custom roms like viperXL and also,but it drains my battery,so i want to go back to stock room, or CM10.2 but i can't, when i try RUU it always give me an error, and when i downloaded the CM10.2.zip and tried to flash it via twrp it says Installation Failed. im totally confused and need real help.
my HBOOT infos:
Tampered
Unlocked
EVITA PVT SHIP S ON RL
HBOOT 1.14.0002
RADIO 0.19as.32.09.11_2
OpenDSP-v29.1.0.45.622
eMMC-boot
Jun 11 201. 14:36

What's your Cid? It should be 1111 etc.. Make sure ur super cid, then s- off.. After following those steps then try running the RUU
Sent from my Nexus 4 using XDA Premium 4 mobile app

zinter95 said:
Hey guys,
I have a serious problem with my at&t htc one x, first time when i wanted to install a custom rom, i didn't backup ( i know my fault)
i had some problems with installation that drives me to change my cid to HTC_621 ( i don't know why i changed the 1st time, im noob)
now i can only install custom roms like viperXL and also,but it drains my battery,so i want to go back to stock room, or CM10.2 but i can't, when i try RUU it always give me an error, and when i downloaded the CM10.2.zip and tried to flash it via twrp it says Installation Failed. im totally confused and need real help.
my HBOOT infos:
Tampered
Unlocked
EVITA PVT SHIP S ON RL
HBOOT 1.14.0002
RADIO 0.19as.32.09.11_2
OpenDSP-v29.1.0.45.622
eMMC-boot
Jun 11 201. 14:36
Click to expand...
Click to collapse
Why did you change the CID to HTC__621? That doesn't even look like it's for our device. That's the reason the RUU is failing.
The reason cm10.2 won't boot is because you need to RUU to 3.18 with the 2.14 hboot to flash that ROM, it does state that clearly in the install instructions for that ROM.
You're gonna need to get SuperCID first, then you can get s-off, then you can RUU to 3.18, then you can flash the cm10.2 ROM.
Sent from my Evita

I tried to SuperCID but i couldnt, i tried the hex editor way, but it gives me always errors, i guess thats why i can s-off.
Any solutions?

Ok, but why did you change it HTC__621? I don't think that's a CID for our device, were you trying to install software or something? The only problem is that without s-off you can only manually change the CID once, and you've used that one chance up by changing it to HTC__621. As far as a solution goes I'm not sure, there are a few different methods to change your CID, I'd suggest you try them all.
Sent from my Evita

zinter95 said:
I tried to SuperCID but i couldnt, i tried the hex editor way, but it gives me always errors, i guess thats why i can s-off.
Click to expand...
Click to collapse
SuperCID is mandatory for the s-off method. So yes, that is why you can't s-off.

i changed my cid to 11111111 now, but i still cannot change it to s-off i followed the instructions but i always failed.

You need to give more info. Where in the process did it fail?
Sent from my Evita

At the first time i failed when i type that code;
Code:
adb push soffbin3 /data/local/tmp/
adb shell chmod 744 /data/local/tmp/soffbin3
adb shell su -c "/data/local/tmp/soffbin3"
and when i wanted to try another time it keeps failing in the step before that one.

You're not being very specific, just saying it fails doesn't help diagnosing the problem.
Have you extracted the soffbin zip into the fastboot folder as per the instructions? Do you have usb debugging enabled in developer options? If applicable (on aosp ROM) have you granted adb root access in developer options?
When you say the step before that one, you mean the fastboot flash zip command right? And my guess is that you're getting error 99 instead of error 92? If you get error 99, force a reboot into the bootloader (by holding volume down and power) and start again from the beginning.
Sent from my Evita

timmaaa said:
You're not being very specific, just saying it fails doesn't help diagnosing the problem.
Have you extracted the soffbin zip into the fastboot folder as per the instructions? Do you have usb debugging enabled in developer options? If applicable (on aosp ROM) have you granted adb root access in developer options?
When you say the step before that one, you mean the fastboot flash zip command right? And my guess is that you're getting error 99 instead of error 92? If you get error 99, force a reboot into the bootloader (by holding volume down and power) and start again from the beginning.
Sent from my Evita
Click to expand...
Click to collapse
heey, im in this step right now
adb push soffbin3 /data/local/tmp/
adb shell chmod 744 /data/local/tmp/soffbin3
adb shell su -c "/data/local/tmp/soffbin3"
any time i run that command it says Device offline or device not found, but i have the latest updates of htc synmanager ..
im running RageXl 1.03 ROM.
How can i solve it please?

Uninstall HTC Sync Manager but leave the drivers installed. Make sure you have usb debugging enabled in developer options. When you try again you might get error 99 instead of error 92 after flashing the zip st the beginning. If this happens, force a reboot back to bootloader by holding volume down and power and start again from the beginning of the process.
Sent from my Evita

timmaaa said:
Uninstall HTC Sync Manager but leave the drivers installed. Make sure you have usb debugging enabled in developer options. When you try again you might get error 99 instead of error 92 after flashing the zip st the beginning. If this happens, force a reboot back to bootloader by holding volume down and power and start again from the beginning of the process.
Sent from my Evita
Click to expand...
Click to collapse
i uninstalled htc syn manager but it still telling me device offline!!!!!!!!!!!!!!!!!

Wow, that's a lot of exclamation marks. Maybe you need to try on a different ROM. Check your drivers, check adb, make sure usb debugging is enabled. It's almost impossible for me to diagnose what's going on without being there, you need to troubleshoot it.
Sent from my Evita

timmaaa said:
You're not being very specific, just saying it fails doesn't help diagnosing the problem.
Have you extracted the soffbin zip into the fastboot folder as per the instructions? Do you have usb debugging enabled in developer options? If applicable (on aosp ROM) have you granted adb root access in developer options?
When you say the step before that one, you mean the fastboot flash zip command right? And my guess is that you're getting error 99 instead of error 92? If you get error 99, force a reboot into the bootloader (by holding volume down and power) and start again from the beginning.
Sent from my Evita
Click to expand...
Click to collapse
Heey,
I installed an aosp rom, and everything was going alrgiht until the last step , the last command;
C:\Android>adb shell su -c "/data/local/tmp/soffbin3.zip"
/data/local/tmp/soffbin3.zip[2]: ┴¹Í♣î¶: not found
/data/local/tmp/soffbin3.zip[4]: syntax error: '³' unexpected
/data/local/tmp/soffbin3.zip[2]: ©╚ÇÎ⌂idþº╬R░4↔´NØU÷Å┘)È¿jØ&j+ò╩U¿PñF╩‗ÇTAäBÑJÇJ
ôç
►╝D<B}░wYQéäèÈ─ï¨╬▄;╗wªnEÃ>{¯╣þþ×{¯╣?þ╣╣┼yMË╚*ö: not found
/data/local/tmp/soffbin3.zip[2]: ┘ªnc↕♂mè◄←ßîÃÚ: not found
/data/local/tmp/soffbin3.zip[2]: can't create │╗▒Î÷: Read-only file system
/data/local/tmp/soffbin3.zip[2]: ô♦ý☻─Q└: not found
/data/local/tmp/soffbin3.zip[2]: ª↕Wê2└Ù}▄G╗2öó^*▲ñ¹®ç♦/│.×: not found
C:\Android>
i dont know whats the problem, may you help me?

What language and locale is your Windows and phone set to?
To me it looks like an application that does not correctly handle non-English locales.
Or something is corrupt.

twistedddx said:
What language and locale is your Windows and phone set to?
To me it looks like an application that does not correctly handle non-English locales.
Or something is corrupt.
Click to expand...
Click to collapse
my phone is set to english and my computer to french!but i dont think thats the problem.

anyone can help me guys??

You've entered the command incorrectly. There should be no ".zip" at the end of the command. Because of this I'm also assuming you haven't extracted (unzipped) the soffbin zip file into your adb/fastboot folder? Read the instructions on the s-off thread again, you must follow them absolutely precisely with no deviations.
Sent from my Evita

timmaaa said:
You've entered the command incorrectly. There should be no ".zip" at the end of the command. Because of this I'm also assuming you haven't extracted (unzipped) the soffbin zip file into your adb/fastboot folder? Read the instructions on the s-off thread again, you must follow them absolutely precisely with no deviations.
Click to expand...
Click to collapse
Yeah, when modding your phone, don't improvise or add things, unless you are positive of what you are doing. Folks have bricked their phones by not following instructions exactly.

Stuck at boot loop???

Hi, i had a S4 which got a broken screen and costs too much to fix a the moment so i brought a Telstra HTC ONE XL off a friend for $100.
I do like the phone but was over the 4.2.1 software as used to the 4.3 on the S4 which i rooted and put on CM10.
I tried with this phone to put on the nightly cm 10.3 but i hit a problem ,when install the nightlies it boot loops and when i try install the stable 10.1 it fails with an error which i do belive is to do with my V2 hboot.
I downloaded the RRU which is supposted to update the hboot to v3 then i can install cm10.3 (aparently) but when i run the rru it fails saying not for my phone.
RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial
I have unlocked through htcdev and rooted it ok.
Im stuck now though as i pressed backup current original rom which turns out its not.
The phone details are
CID TELST001
Model: HTC ONE XL TELSTRA
If someone can tell where to either find the newest telstra rru for my phone or how to update my hboot so i can use cm10?
My phone is pretty useless at the moment

stueee said:
I downloaded the RRU which is supposted to update the hboot to v3 then i can install cm10.3 (aparently) but when i run the rru it fails saying not for my phone.
Click to expand...
Click to collapse
Where are you getting CM from (link it) and what is the file named? CM will typically have the phone's code name (EVITA) in the file name. If the code name ENDEAVORU is in the file name, it is in fact for the wrong device, as the ENDEAVORU is for the quad core Tegra3 (non-LTE) version, which is completely different hardware.
Also, I don't know if 10.3 is even released yet for our device, or for the ENDEAVORU for that matter. I think you might be confused about what you are flashing. So again, link what you are trying to install.

The reason you couldn't run that RUU is because the CID check wouldn't allow it, it's looking for an at&t CID which you don't have. Getting s-off disables the security check which would let you run any Evita RUU but you need to get a ROM to boot first before you try that. You also need SuperCID.
Your best bet is probably to flash an older Sense ROM (4.0 or 4.1), then you can at least boot, and get SuperCID and s-off so you can run the 3.18 RUU to meet the requirements for the latest cm ROMs.
Sent from my Evita

timmaaa said:
The reason you couldn't run that RUU is because the CID check wouldn't allow it, it's looking for an at&t CID which you don't have.
Click to expand...
Click to collapse
For some reason, I got confused and thought the OP was saying that the ROM install was failing. But it clearly says the RUU (or "rru" anyway) failed.
But yes, you can only run an RUU for your carrier version. So you will need s-off to run the AT&T RUU (the RUU referenced in the OP).
But still confused about the mention of CM10.3. From what I can see, it doesn't exist for either our EVITA, or the ENDEAVORU.

Maybe he meant cm10.2 and it was a typo?
Sent from my Evita

timmaaa said:
Maybe he meant cm10.2 and it was a typo?
Click to expand...
Click to collapse
Could be. Although if so, its a type that appears twice.
It seems fairly common for folks to try to install the wrong CM (wrong device). So I want to make sure the OP isn't doing that.

redpoint73 - the CM i downloaded and installed was from http://get.cm/?device=evita and i tried
cm-10.2-20131030-NIGHTLY-evita.zip which installed but bootloops
and then i tried the stable - cm-10.1.3-evita.zip which gave me the failed error.

stueee said:
redpoint73 - the CM i downloaded and installed was from http://get.cm/?device=evita and i tried
cm-10.2-20131030-NIGHTLY-evita.zip which installed but bootloops
and then i tried the stable - cm-10.1.3-evita.zip which gave me the failed error.
Click to expand...
Click to collapse
Okay, neither of those are CM10.3, as stated in your first post. Please post accurate information to prevent form confusing those that are trying to help.
What hboot are you currently on? Its listed on the bootloader screen.
What version of TWRP?
You should be able to mount SD in TWRP, put a Sense ROM on the phone, and get back up and running.

Hi Red,
Sorry i typed out that post at almost 1am after pulling my hair out over a few hours and got a little confused.
My hboot is 2.15 and twrp is 2.6.3.0 which I believe is the latest.
What sense rom would work on mine as i really need this working now as i cant find a rom to suit anywhere with my lesser expertees.
I tried changing the cid using the super cid Telstra bat file but it won't recognize the phone as its not loaded, i tried in off state, bootloader, fastboot and twrp but is just keeps saying cant find phone.
I also tried the hex editor method but it didnt seem to update the CID after i completed it without errors.
thanks for you help.
redpoint73 said:
Okay, neither of those are CM10.3, as stated in your first post. Please post accurate information to prevent form confusing those that are trying to help.
What hboot are you currently on? Its listed on the bootloader screen.
What version of TWRP?
You should be able to mount SD in TWRP, put a Sense ROM on the phone, and get back up and running.
Click to expand...
Click to collapse

With 2.15 hboot, you cannot modify the files required for supercid.
You can try the ever so risky jet tool. But this tool deliberately bricks to downgrade your hboot.
Sent from my HTC One XL using xda app-developers app

Any recent Sense ROM will suit your current setup, have a look here and you'll find a whole bunch. Unfortunately for you the 2.15 hboot has write protection enabled so there's no way you can get SuperCID (abd therefore can't get s-off), at least not until an exploit is released.
When you tried to flash CM did you also flash the boot.img via fastboot afterwards? You're s-on so that's necessary to get it to boot. Phones on a higher hboot like yours are unable to flash the boot.img through recovery so it must be done manually.
All you do is retrieve the boot.img from the root of the ROM zip, put it in your fastboot folder on your PC, and after you've flashed the ROM in recovery you reboot to bootloader, connect the phone to the PC, open a command prompt from within your fastboot folder (shift + right click anywhere in the folder then select open command prompt here), then give the following command:
fastboot flash boot boot.img
Once that's done you can reboot the phone and it should boot into the ROM.
Sent from my Evita

stueee said:
My hboot is 2.15
Click to expand...
Click to collapse
That's pretty important. This is the reason why the older CM10.1 failed to install. CM was having issues with older hboots, so a script was added to require hboot 2.14.
Once hboot 2.15 came along, folks found that CM failed to install since the install script explicitly requires 2.14. Later versions include hboot 2.15 in the install script.
As exad and timmaaa mention, SuperCID (and therefore s-off) are not possible on hboot 2.15. So you are stuck with s-on (assuming that is what you are on now). It also means you can't currently run any RUU. Reason being, with s-on you can't run older RUUs, RUUs from another carrier, and there are no RUUs based on hboot 2.15. No "current" RUU exists (for your hboot), you can't run "previous" RUUs with the S-on restriction. So therefore you can't currently run any RUU.
But hboot 2.15 will work with newer versions of CM (and other AOSP ROMs which have been recently updated) as well as any Sense ROMs. But with s-on, you need to extract boot.img and flash manually with fastboot every time you install a ROM (as timmaaa points out). If you did not do this, this is why flashing the recent CM10.2 nightly resulted in a bootloop. Failure to falsh boot.img is the most common reason for bootloop after flashing a ROM.

stuck in bootloop
ive recently have been flashing different roms onto my htc one with no problem..then i decided to try the google play edition and realised i had to be s-off...now i have super cid 11111111 and s-off and was running skydagon 14.1 with no prob...today i did a nand backup and thought i would try the liquid rom then half way through the fresh install (i wiped cache and dalvik first)my phone shut down and boots up into a loop..if i go to recovery (twrp 2.6.3.3) it only stays in recovery a few seconds then goes back to the start of bootloop...i have tried cwmr also...i have otg cable and have used adb a few times however im not highly skilled so any help would be appreciated...apologies on the excessive post..

martin-m7 said:
ive recently have been flashing different roms onto my htc one with no problem..then i decided to try the google play edition and realised i had to be s-off...now i have super cid 11111111 and s-off and was running skydagon 14.1 with no prob...today i did a nand backup and thought i would try the liquid rom then half way through the fresh install (i wiped cache and dalvik first)my phone shut down and boots up into a loop..if i go to recovery (twrp 2.6.3.3) it only stays in recovery a few seconds then goes back to the start of bootloop...i have tried cwmr also...i have otg cable and have used adb a few times however im not highly skilled so any help would be appreciated...apologies on the excessive post..
Click to expand...
Click to collapse
You're in the wrong forum, buddy. This is the HTC One XL forum.

[Q] Stuck on Hboot/fastboot with full stock phone

Hi guys,
My sister sent me her HTC One SV aka K2-UL i offered her from expansys on june, it is stuck on Hboot
*** LOCKED***
K2_UL XA SHIP S-ON RL
HBOOT-2.00.0000
eMMC Boot
...
I can go to Fastboot USB ( or AC )
She 's worst than a noob so phone is stock, up to date but non-root non-unlock, still S-ON and so on.
just once phone reboot and stay stuck...
From here i can navigate but after reboot i'm still here.
I tried :
factory reset and recovery (with rom renamed PL80DIAG but would be too easy...)
RUU but RUU asked for bootloader so stuck on "waiting for bootloader"
go to htc dev to unlock bootloader but after flash unlock token ( unlock token check successfully) but : Nothing happens and still writtten ***Locked*** then if I "fastboot oem unlock" it says failed :<remote : loading custom splash failed>
fastboot flash boot.img but nothing works since still S-on and locked bootloader (superCID is out too)
flash custom recovey or even fresh stock recovery but nothing worked for the same reasons...
Do you guys have any idea of something i could do?
Thanks for your answer and forgive my English I'm French

As long as you are ***LOCKED*** you can quiet do nothing.
To use our available RUU you must also be unlocked & S-Off.

Somewhat the same situation
I am stuck here:
***Tampered***
***Unlocked***
K2_PLC_CL PVT Ship S-ON RL
HBOOT -1.01.0000
Radio - 1.12.00.0208
OpenDSP - v.7.2.0221.1123
eMMC - boot
Feb 8 2013, 16:29:40:-1
I can get into Fastboot as well as bootloader, I CANNOT GET INTO RECOVERY. I have tried to restore with the respective RUU files from the All things HTC ONE SV forum. I have also tried to flash the recovery boot and radio img files through fastboot usb. NONE of this has worked for me. I really enjoyed this phone before I went and made it all FUBR. If there is anyway to get it to boot to any recovery or rom, i will much appreciate it. Thanks for all your help from previous posts as well as any future help I get from information posted here.

Related to your hboot, you should be able to flash any recoveries, but i usually recommend this one.
What command do you use to flash recovery and do you get an output from "fastboot devices"?

Thedc24 said:
I am stuck here:
***Tampered***
***Unlocked***
K2_PLC_CL PVT Ship S-ON RL
HBOOT -1.01.0000
Radio - 1.12.00.0208
OpenDSP - v.7.2.0221.1123
eMMC - boot
Feb 8 2013, 16:29:40:-1
Click to expand...
Click to collapse
Oops you already are 4.2.2. I have a system.img and a boot.img that I can make into a rom.zip to flash via the OEM-RUU mode.

eduardog131 said:
Oops you already are 4.2.2. I have a system.img and a boot.img that I can make into a rom.zip to flash via the OEM-RUU mode.
Click to expand...
Click to collapse
HBOOT 1.01 is ICS (4.0.x).
Sent from my C525c using Tapatalk

Modding.MyMind said:
HBOOT 1.01 is ICS (4.0.x).
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Well then I was right then I was wrong. Sorry. HBOOT versions for the Sensation are stuck in my mind.
Sent from my HTC Sensation

Thanks a million for the replies. I was able to lead the recovery and get into it (the most progress i have had in a year with this phone). With that being done. When I go into recovery I am unable to mount the internal storage. I am not too sure of the procedures I need to go through to get this thing functional again. I have been tinkering with my S3 for the last few months, but with KNOX on now I am looking to Jump ship completely from both verizon and samsung. Enough rambling, Like I said thanks for the help, any assistance in getting this thing to boot to a ROM would be much appreciated.
BTW
I used the fastboot flash recovery recovery.img
I have tried this before with no success. This time it worked.
I also flased the Radio and Boot img for ICS.
Thanks.

Thedc24 said:
Thanks a million for the replies. I was able to lead the recovery and get into it (the most progress i have had in a year with this phone). With that being done. When I go into recovery I am unable to mount the internal storage. I am not too sure of the procedures I need to go through to get this thing functional again. I have been tinkering with my S3 for the last few months, but with KNOX on now I am looking to Jump ship completely from both verizon and samsung. Enough rambling, Like I said thanks for the help, any assistance in getting this thing to boot to a ROM would be much appreciated.
BTW
I used the fastboot flash recovery recovery.img
I have tried this before with no success. This time it worked.
I also flased the Radio and Boot img for ICS.
Thanks.
Click to expand...
Click to collapse
If you want I can just skip you to 4.2.2. You don't need to reflash recovery and stuff. I will make a package that will update HBOOT and radios. And system/boot.img.
Sent from my HTC Sensation

He first needs to be S-off, to flash radio & hboot. I have made a 4.1.2 rom for cricket, must be linked in my index thread. Wipe all, flash the rom, flash boot.imgwith fastboot and hope that little baby is booting.
If yes, use moonshine.io or rumrunner.us to get S-off.
Then we will do next steps.

old.splatterhand said:
He first needs to be S-off, to flash radio & hboot. I have made a 4.1.2 rom for cricket, must be linked in my index thread. Wipe all, flash the rom, flash boot.imgwith fastboot and hope that little baby is booting.
If yes, use moonshine.io or rumrunner.us to get S-off.
Then we will do next steps.
Click to expand...
Click to collapse
Wow! Awsome! This bad boy booted. I was able to flash the rom through recovery. This is much further than I expected to get with this device. Now when I try to go S-Off with either moonshine or rumrunner I get an error saying not able to make adb connection. When I use fastboot devices my device will show up...if i do adb devices nothing...Would love to have S-Off and SU installed. But like I said this is much further than I expected to get so anything further is icing on the cake. Thanks in Advance.

Is Usb-Debugging enabled?
Any output from adb devices? HTC Sync installed (for the drivers)?

old.splatterhand said:
Is Usb-Debugging enabled?
Any output from adb devices? HTC Sync installed (for the drivers)?
Click to expand...
Click to collapse
He can just use the Naked Driver for the adb driver. http://forum.xda-developers.com/showthread.php?t=2263822

Ok I DID have USB debugging enabled. After messing with the drivers and my Windows 8 computer, I have came to the conclusion that it is something with the drivers and their compatibility with Windows 8. Either way moonshine or rumnunner never worked for me in a windows 8 environment. I dual boot ubuntu 12.04 anyway, it saw my device just fine adb and fastboot. I ran moonshine and it went through all the testing stages, but was never able to completely run...so I still have no S-Off. Do I need to update Hboot or anything? Also am I able to load a custom rom on this device with S-ON? I have been looking but I do not see many out for this device at all, which is a shame because I feel as though it is very comparable to my GS3. It would be nice to see a nice AOSP ROM on this device. But all take any updates I can for the device, hopefully it will help with the issue I have will cell reception dropping all the time. Thanks

To answer some of your questions:
- you can't update hboot because you are not stock and not S-off
- there are indeed not much roms to flash, but you could do with S-on (and unlocked bootloader)
- if you would flash the Sense 5/Android 4.2.2 rom, you would have noizy sound, without the firmware files (which you need S-Off to flash)
Another way for getting S-off (which should work with your hboot), is facepalm.
But the part of changing CID to SuperCID is very risky, read carefully and only do, when you are sure you understand, what to do!!!

old.splatterhand said:
To answer some of your questions:
- you can't update hboot because you are not stock and not S-off
- there are indeed not much roms to flash, but you could do with S-on (and unlocked bootloader)
- if you would flash the Sense 5/Android 4.2.2 rom, you would have noizy sound, without the firmware files (which you need S-Off to flash)
Another way for getting S-off (which should work with your hboot), is facepalm.
But the part of changing CID to SuperCID is very risky, read carefully and only do, when you are sure you understand, what to do!!!
Click to expand...
Click to collapse
Thanks for all the help! I am now SuperCID with S-OFF, Facepalm worked like a charm. Would it be possible to put slimrom on this device? Anyway thanks for all the help, I am going to check out some ROMS..as far as flashing goes, I am assuming how I have my phone now I should be able to flash any rom that is compatible with the device.
---------- Post added at 05:46 PM ---------- Previous post was at 05:24 PM ----------
eduardog131 said:
If you want I can just skip you to 4.2.2. You don't need to reflash recovery and stuff. I will make a package that will update HBOOT and radios. And system/boot.img.
Sent from my HTC Sensation
Click to expand...
Click to collapse
Yea that would be cool. I am assuming I would just flash it through recovery?

Thedc24 said:
Thanks for all the help! I am now SuperCID with S-OFF, Facepalm worked like a charm. Would it be possible to put slimrom on this device? Anyway thanks for all the help, I am going to check out some ROMS..as far as flashing goes, I am assuming how I have my phone now I should be able to flash any rom that is compatible with the device.
---------- Post added at 05:46 PM ---------- Previous post was at 05:24 PM ----------
Yea that would be cool. I am assuming I would just flash it through recovery?
Click to expand...
Click to collapse
You're completely S-OFF? The radios and new HBOOT update need to be flashed in RUU mode. Let me get my bearings and you can flash everything. (adb reboot oem-42 or fastboot oem rebootRUU is a way to get to RUU mode.)
Sent from my HTC Sensation using Tapatalk

eduardog131 said:
You're completely S-OFF? The radios and new HBOOT update need to be flashed in RUU mode. Let me get my bearings and you can flash everything. (adb reboot oem-42 or fastboot oem rebootRUU is a way to get to RUU mode.)
Sent from my HTC Sensation using Tapatalk
Click to expand...
Click to collapse
Yes I am completely S-OFF with CID 111111 and SU. The phone has been working good, Cricket service is not all that great in my area. I see there is a software update 2.04.1050.5 (15.1 MB), I am assuming if i run this update it will most likely wipe everything I just did. Is this correct?

Thedc24 said:
Yes I am completely S-OFF with CID 111111 and SU. The phone has been working good, Cricket service is not all that great in my area. I see there is a software update 2.04.1050.5 (15.1 MB), I am assuming if i run this update it will most likely wipe everything I just did. Is this correct?
Click to expand...
Click to collapse
I think. Anyways, download this: http://www.mediafire.com/download/maa60jha4eod834/rom.zip
Contents of said rom.zip:
4.2.2 system.img with root.
4.2.2 stock boot.img.
4.2.2 stock recovery.
New HBOOT and radios and stuff.
If you get an error (flush again or something.), then just resend the command. (fastboot flash zip path/to/rom.zip)

eduardog131 said:
I think. Anyways, download this: http://www.mediafire.com/download/maa60jha4eod834/rom.zip
Contents of said rom.zip:
4.2.2 system.img with root.
4.2.2 stock boot.img.
4.2.2 stock recovery.
New HBOOT and radios and stuff.
If you get an error (flush again or something.), then just resend the command. (fastboot flash zip path/to/rom.zip)
Click to expand...
Click to collapse
Downloading now. I will let you know how it goes...thanks a million.
This is what I got when I tried to flash the rom:
sending 'zip' (691470 KB)...
OKAY [ 37.267s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 37.301s
I dont understand if I am S-Off and super CID.