[Q] Won't boot past HTC screen - EVO Shift 4G Q&A, Help & Troubleshooting

I rooted my HTC Evo Shift 4g successfully, but then tried to update the software through the phone, and now my phone won't boot past the white background with the HTC letters. Someone please help me, I just received this phone, and need it working asap! My fastboot menu or whatever says this:
Speedy XF SHIP S-ON
HBOOT-0.98.001
RADIO-1.08.00.0506
eMMC-boot

With an S-ON device after a full wipe in recovery you need to take the boot.img feom the ROM you flashed and place it where your fastboot is ( most likely platform-tools if you have the SDK ) and reboot into bootloader then choose fastboot USB. Once in fastboot mode you need to run
fastboot flash boot boot.img
After it writes the boot.img it should boot.
The problem with an S-ON device is you don't have the proper permissions to write to the boot partition with a zip, it had to be done through fastboot . once you get up and running once you can use a nifty app called Flash Image GUI to flash a new kernel before flashing a new ROM to avoid the fastboot ordeal.
If you don't have the SDK with adb and all that I suggest grabbing that and getting it all setup, its your best friend in the android world.
Sent From a Freaked out Nexus 4

strapped365 said:
With an S-ON device after a full wipe in recovery you need to take the boot.img feom the ROM you flashed and place it where your fastboot is ( most likely platform-tools if you have the SDK ) and reboot into bootloader then choose fastboot USB. Once in fastboot mode you need to run
fastboot flash boot boot.img
After it writes the boot.img it should boot.
The problem with an S-ON device is you don't have the proper permissions to write to the boot partition with a zip, it had to be done through fastboot . once you get up and running once you can use a nifty app called Flash Image GUI to flash a new kernel before flashing a new ROM to avoid the fastboot ordeal.
If you don't have the SDK with adb and all that I suggest grabbing that and getting it all setup, its your best friend in the android world.
Sent From a Freaked out Nexus 4
Click to expand...
Click to collapse
I didn't flash a rom, I was on the stock rom, but updated through the HTC Software update on the phone.

strapped365 said:
With an S-ON device after a full wipe in recovery you need to take the boot.img feom the ROM you flashed and place it where your fastboot is ( most likely platform-tools if you have the SDK ) and reboot into bootloader then choose fastboot USB. Once in fastboot mode you need to run
fastboot flash boot boot.img
After it writes the boot.img it should boot.
The problem with an S-ON device is you don't have the proper permissions to write to the boot partition with a zip, it had to be done through fastboot . once you get up and running once you can use a nifty app called Flash Image GUI to flash a new kernel before flashing a new ROM to avoid the fastboot ordeal.
If you don't have the SDK with adb and all that I suggest grabbing that and getting it all setup, its your best friend in the android world.
Sent From a Freaked out Nexus 4
Click to expand...
Click to collapse
My recovery mode does not work either, I only get a phone with a triangle...

Thats because you took the update through your phone, and removed root doing so.
Sent from my PG06100

CNexus said:
Thats because you took the update through your phone, and removed root doing so.
Sent from my PG06100
Click to expand...
Click to collapse
What do you suggest I do, i've been messing with my phone for about 5 hours straight now, I need it in a few hours!

Well, you need to reroot. Go to Settings > About Phone > Software Info and tell us what it says under Software Number
Sent from my PG06100

CNexus said:
Well, you need to reroot. Go to Settings > About Phone > Software Info and tell us what it says under Software Number
Sent from my PG06100
Click to expand...
Click to collapse
My phone won't boot up, that's the problem.

Oh sorry, it seemd like your phone could boot up now but you couldnt get in CWM recovery. Can you get into the bootloader?
Power off your phone, then hold Power+VolDown until you see a white screen with skating Androids at the bottom
EDIT: Seems like you can get there. Go to htcdev.com, make an account, and follow the steps to unlock your bootloader. After thats done you can flash a rom and your phone SHOULD boot up
Since you're gonna be S-ON, dont forget to follow strapped365's directions above for flashing the boot.img AFTER you flash the rom, htcdev.com gives you a zip with all the files you need (adb and fastboot executables) to do that, so you dont need to download the AndroidSDK
Sent from my PG06100

CNexus said:
Oh sorry, it seemd like your phone could boot up now but you couldnt get in CWM recovery. Can you get into the bootloader?
Power off your phone, then hold Power+VolDown until you see a white screen with skating Androids at the bottom
EDIT: Seems like you can get there. Go to htcdev.com, make an account, and follow the steps to unlock your bootloader. After thats done you can flash a rom and your phone SHOULD boot up
Since you're gonna be S-ON, dont forget to follow strapped365's directions above for flashing the boot.img AFTER you flash the rom, htcdev.com gives you a zip with all the files you need (adb and fastboot executables) to do that, so you dont need to download the AndroidSDK
Sent from my PG06100
Click to expand...
Click to collapse
I can get into the fastboot, but htcdev does not have the HTC Evo Shift 4g, so I used the HTC Evo 3D and it still won't work.

jae_point said:
I can get into the fastboot, but htcdev does not have the HTC Evo Shift 4g, so I used the HTC Evo 3D and it still won't work.
Click to expand...
Click to collapse
You got the unlock_token.bin and pushed it through fastboot?
Sent from my PG06100

jae_point said:
I can get into the fastboot, but htcdev does not have the HTC Evo Shift 4g, so I used the HTC Evo 3D and it still won't work.
Click to expand...
Click to collapse
CNexus said:
You got the unlock_token.bin and pushed it through fastboot?
Sent from my PG06100
Click to expand...
Click to collapse
I can't get the token to appear, I get an error through the cmd command.

You said you were using the 3d info on htc dev. I believe you're supposed to use All Other Supported Models instead. At least that is what I did with my EVO 4G.

Chad The Pathfinder said:
You said you were using the 3d info on htc dev. I believe you're supposed to use All Other Supported Models instead. At least that is what I did with my EVO 4G.
Click to expand...
Click to collapse
I used the page for Evo 3d on mine and it worked.

klund29078 said:
I used the page for Evo 3d on mine and it worked.
Click to expand...
Click to collapse
I'll try it, if it doesn't work I will post the error code.

I tried using HTCDev, and here is the error that I get, I have everything set up right.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

jae_point said:
I tried using HTCDev, and here is the error that I get, I have everything set up right.
Click to expand...
Click to collapse
You have the 3 files that the HTCDev site requires, and they are all in that C:\Android folder correct?
And you're in the fastboot screen, and not the bootloader screen?

klund29078 said:
You have the 3 files that the HTCDev site requires, and they are all in that C:\Android folder correct?
And you're in the fastboot screen, and not the bootloader screen?
Click to expand...
Click to collapse
Yes, I have everything correct, and I'm in the fastboot screen. I just don't understand whats going on, anyway I can just flash to restore or something like that?

Well if it wont even unlock...then I think your best bet is to take it into Sprint, unfortunately
If you could unlock it then you could flash some rom and everything would be ok, but thats not the case...
Idk, I'm out of ideas, anyone who has something else in mind feel free to chime in
Sent from my PG06100

klund29078 said:
You have the 3 files that the HTCDev site requires, and they are all in that C:\Android folder correct?
And you're in the fastboot screen, and not the bootloader screen?
Click to expand...
Click to collapse
CNexus said:
Well if it wont even unlock...then I think your best bet is to take it into Sprint, unfortunately
If you could unlock it then you could flash some rom and everything would be ok, but thats not the case...
Idk, I'm out of ideas, anyone who has something else in mind feel free to chime in
Sent from my PG06100
Click to expand...
Click to collapse
Do you have any ideas of what sprint will say/do. I bought this phone used from a friend, anyway I can make up a story saying I didn't know it was rooted, so I tried upgrading over the phone and it did this?

Related

HTC Sensation XE stuck in bootloop [SOLVED]

Hi all,
I am trying to recover an HTC Sensation XE (PG58130), but I have no history on the unit, so I don't know if it's been modified or is genuinely faulty.
When you power the phone on, all you get is the HTC logo. Nothing else happens.
Vol Down + Power displays the following info:
*** LOCKED ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
RADIO-10.14.9035.02_2
eMMC-boot
Aug 2 2011,22:35:52
Click to expand...
Click to collapse
I have tried "Factory Reset". I also put the phone into Recovery, then wiped data and cache, but still only get the HTC logo.
Does anyone have any suggestions? Also, does the information above suggest the phone hasn't been modified?
It hasn't been modified. It still is S-on and has the original hboot 1.18
Sent from my Kindle Fire using Tapatalk 2
Ah, thanks for letting me know.
So, is there any way I can fix this boot loop problem?
blastcomms said:
Ah, thanks for letting me know.
So, is there any way I can fix this boot loop problem?
Click to expand...
Click to collapse
you need to soff your device which will let you flash a custom rom....
so that you can bring back your phone from hell
here is the guide to all the basic steps which are required to flash any rom
guide link
Thanks - I'll take a look.
Does that void the warranty with HTC? I would like to retain the warranty where possible, but if that's the only option then I don't mind.
blastcomms said:
Thanks - I'll take a look.
Does that void the warranty with HTC? I would like to retain the warranty where possible, but if that's the only option then I don't mind.
Click to expand...
Click to collapse
all the things you are doing are reversible but you need to be careful while doing it
Follow step by step for successful soff
Also STEP 5 in the guide helps you in reversing the process which will help you in claiming the warranty
PS: Read each and every step carefully and execute them ...then it'll be a piece of cake
Sorry, another question, but I want to make sure I get this right.
It says in the guide to run revolutionary and then connect the phone. However, it says the phone should be on and in HTC Sync mode.
Obviously this phone isn't powering on so that's a problem.
Any ideas?
blastcomms said:
Sorry, another question, but I want to make sure I get this right.
It says in the guide to run revolutionary and then connect the phone. However, it says the phone should be on and in HTC Sync mode.
Obviously this phone isn't powering on so that's a problem.
Any ideas?
Click to expand...
Click to collapse
oops forgot about that
try this
keep your phone in hboot mode (i.e. power + vol down button) you'll get a white screen
then run revolutionary (hopefully revolutionary detects the phone)
if it doesn't work (i mean if revolutionary didn't recognize your device) let me know..
Im currently looking for any other method and ill post you if i got any leads
EDIT:
found the guide (follow steps carefully)
http://forum.xda-developers.com/showthread.php?t=1469296
There seems to be different headers indicating different steps. Which steps should I follow in my case?
By the way, I saw your post before you edited it, and followed these steps to setup adb and fastboot: http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/
When I type 'adb devices' into cmd I get nothing (when in HBOOT), but when I go to fastboot and type 'fastboot devices' it shows me the phone's serial number. Is that normal?
Yeah that is normal.
Adb works when you are on your OS ie either GB or ICS and fastboot works when you are on bootloader..as fastboot was able to recognize your device can you post the cid
Command is "fastboot getvar cid"
Edit:
The thing is now you require a GB Rom which can be flashed which supports. your hboot and radio but by flashing that your hboot version should not change as that is the final version where soff works.
So try unlocking your device by using HTC dev and flash a stock 2.3 Rom mentioned in the guide.
Try the way where he mentioned about a member flashing rom (he has the same scenario hboot 1.18 and ics Rom on top of it with gb firmware)
sent from my blazing fast pyramid through sonic waves
Hi, sorry I was away yesterday.
My CID is HTC__001.
Does that make any difference to flashing, etc?
blastcomms said:
Hi, sorry I was away yesterday.
My CID is HTC__001.
Does that make any difference to flashing, etc?
Click to expand...
Click to collapse
yeah cid does require some changes...but have you tried
revolutionary by keeping your phone connected to your pc through usb ???
i mean when you ran revolutionary was it able to identify your device and asked for beta key??
if it did recognized your device then you'll be not having issues anymore
so just try revolutionary first and let me know the result
In the mean time i'll figure out the best solution for you
EDIT: Also you got recovery installed ?? can you check that by going into recovery from HBOOT -> (if it is an exclamatory mark with inverted triangle then stock recovery)
I ran revolutionary in HBOOT and it didn't do anything, just said it was waiting for the device.
Should it be in a different mode?
My recovery screen looks the same as this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
blastcomms said:
I ran revolutionary in HBOOT and it didn't do anything, just said it was waiting for the device.
Should it be in a different mode?
My recovery screen looks the same as this:
Click to expand...
Click to collapse
what about fastboot mode?
just try that too
let me know ASAP
(im online and ill give you further steps)
EDIT:
"I have tried "Factory Reset". I also put the phone into Recovery, then wiped data and cache, but still only get the HTC logo."
how did you wiped data and cache if you got stock recovery (fyi i haven't exploited stock recovery as i ran revolutionary and installed custom recovery the next minute i got my phone )
Even in fastboot mode, revolutionary just says "Waiting for device..."
To wipe data and cache I entered recovery, then pressed Vol Up + Power which brought up further options to wipe, etc.
blastcomms said:
Even in fastboot mode, revolutionary just says "Waiting for device..."
To wipe data and cache I entered recovery, then pressed Vol Up + Power which brought up further options to wipe, etc.
Click to expand...
Click to collapse
finally i got the ruu which installed should give you the GB on it
1.here is the link to download the RUU (it will be big file 358 MB)
RUU link
this RUU.exe is based on your CID and Radio so it will run fine
2.Guide to install RUU
guide
3.if any issue persists (there is 1 common one which was fixed by a guy)
here is the link for the fix if you run into issue
RUU running issues fix
run the ruu.exe and your phone will be reverted back to GB rom
then if you want to update to ICS there are some basuc steps to be done...
i.e SOFF and all so follow the "Guide to SOFF ,supercid ...." thread
after that you can take take this guide as reference for installing any custom rom
EDIT:
ahh man the RUU may be wrong ( will update you about this)
i got another ruu
download this also...this seems more proper for your CID
RUU 2 LINK
Thanks, will reply once I've done all that. The file is downloading now. It says I have to ensure an ActiveSync connection is established, so here's hoping it lets me do that in HBOOT/Fastboot/Recovery.
UPDATE:
1.72 RUU one was for XE version
and 1.52 one was for normal sensation
Oh this one is XE so I need the first link you gave, right? And what mode do you recommend it to be in? Recovery, Fastboot or HBOOT?
EDIT: first link doesn't work once download is supposed to commence.
blastcomms said:
Oh this one is XE so I need the first link you gave, right? And what mode do you recommend it to be in? Recovery, Fastboot or HBOOT?
Click to expand...
Click to collapse
from HBOOT (as that is the default bootloader that pops up)
if this didn't work then try FASTBOOT

Restore to Stock - losing my mind

I've been trying to restore back to stock for over a day now and still havn't figured it out.
All of the guides start talking about adb or fastboot right in the middle of the guide without any explanation.
Aruwizard keeps saying bootloader version fail when I try to flash whats supposed to be stock rogers rom, but everything i see is telling me to download the one im already using.
1. download rogers ruu.zip
2. get supercid or downgrade follow http://forum.xda-developers.com/showthread.php?t=1671135
3. use the windows ruu tool ..... or .... get adb and fastboot installed correctly. google this if you dont know how
4a. for windows ruu tool follow my post in dev section
4b. for adb and fastboot do
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip ruu.zip
it will ask u to run the last command again...
Berserk87 said:
I've been trying to restore back to stock for over a day now and still havn't figured it out.
All of the guides start talking about adb or fastboot right in the middle of the guide without any explanation.
Aruwizard keeps saying bootloader version fail when I try to flash whats supposed to be stock rogers rom, but everything i see is telling me to download the one im already using.
Click to expand...
Click to collapse
Have you relocked your bootloader?
1. make sure fastboot in android is turned off under power.
2. power off device
3. power phone on by holding down the volume down key + pressing power - don't release the volume down key until you see the bootloader screen
4. select fastboot
5. connect phone usb
6. screen should now read fastboot usb in red
7. type fastboot oem lock
Phone might restart back into fastboot can't really remember but now you can run the RUU.
The RUU should be an .exe for the above
im on 1.73 trying to flash reflash 1.73, so i shouldnt need to use super cid (?).
I download the rogers stock rom (PJ83IMG_Evita_UL_Rogers_WWE_1.73.631.1_Radio_0.16a.32.09.06_10.81.32.14L_release_254934_signed.zip)
and I downloaded ARUwizard to flash it.
I keep getting random errors from aruwizard.
ive tried finding adb tools or fastboot, but they all look like they're for specific phones.
Berserk87 said:
im on 1.73 trying to flash reflash 1.73, so i shouldnt need to use super cid (?).
I download the rogers stock rom (PJ83IMG_Evita_UL_Rogers_WWE_1.73.631.1_Radio_0.16a.32.09.06_10.81.32.14L_release_254934_signed.zip)
and I downloaded ARUwizard to flash it.
I keep getting random errors from aruwizard.
ive tried finding adb tools or fastboot, but they all look like they're for specific phones.
Click to expand...
Click to collapse
for aruwizard....did you install htc sync? and relocked your bootloader?...
u need both ...
niceppl said:
for aruwizard....did you install htc sync? and relocked your bootloader?...
u need both ...
Click to expand...
Click to collapse
I did.
and my bootloader has never been unlocked.
its giving me something about incorrect bootloader version. even though its the rogers rom.
Do i need to super cid if im flashing the same version? (1.73 to 1.73)
aruwizard just keeps saying "wrong bootloader version"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
this is what im getting everytime i try to use aruwizard.
Berserk87 said:
this is what im getting everytime i try to use aruwizard.
Click to expand...
Click to collapse
where did u get the aruwizard tool seems its not the one for hox...too old maybe...try the adb amd fastboot method i mentioned above
Sent from my HTC One X using xda app-developers app
niceppl said:
where did u get the aruwizard tool seems its not the one for hox...
Click to expand...
Click to collapse
downloaded it from your other thread. http://forum.xda-developers.com/showthread.php?t=1658929
using fastboot it starts doing the checks, then gets to :
Code:
INFOchecking main version...
FAILED (remote: 43 main version check fail)
looks like even though im trying to flash 1.73 to 1.73 i still need to do the downgrading firmware stuff...
im curious if my failed update upgraded some stuff and failed on the rest...
now its giving me
Code:
FAILED (remote: 44 hboot version check fail)
anyone?
$5 to anyone that can tell me how to fix this (get back to full stock)
Berserk87 said:
$5 to anyone that can tell me how to fix this (get back to full stock)
Click to expand...
Click to collapse
unlock
twrp
root
supercid (search in dev)
downgrade to 1.00.000 (search in dev)
relock
run ruu
everything should be back to stock
if you want to change supercid back to roger001
do previous steps again and change the cid to roger001 rather than supercid
Sent from my HTC One X using xda app-developers app
Berserk87 said:
$5 to anyone that can tell me how to fix this (get back to full stock)
Click to expand...
Click to collapse
Lol $5 thought a twenty was the customary amount
Sent from my HTC One XL
niceppl said:
unlock
twrp
root
supercid (search in dev)
downgrade to 1.00.000 (search in dev)
relock
run ruu
everything should be back to stock
\
Click to expand...
Click to collapse
I don't want to unlock, id rather keep my warranty as I might be RMA'ing it because of the bluetooth issues im having.
Berserk87 said:
I don't want to unlock, id rather keep my warranty as I might be RMA'ing it because of the bluetooth issues im having.
Click to expand...
Click to collapse
You need to unlock, but alas once you flash the ruu ... The unlocked/tampered proof will be rewritten to stock as well...
From my HTC One X possessed by the Illuminati hybrid kernel
It will show relocked instead of locked.Not sure if warranty accept it

[Q&A][CM 10.1][4.2.2] CyanogenMod 10.1 Questions and Help thread

[SIZE=+2]This thread has been created
for
Questions & Answers/Troubleshooting[/SIZE]​[SIZE=+2]Specific to[/SIZE]
The official Build
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
for the AT&T HTC One XL.
Click link here>> Link to Development Thread <<Click link here
Please feel free to share issues, questions and offer help
It is always best to thank a ROM OP, in lieu of simply posting "Thank you".
Please keep discussion focused, on the topic described in the OP
For the new kernel is it possible to flash the newest HBoot from this thread just to make life easier? http://forum.xda-developers.com/showthread.php?t=2156368
Would that be the 2.14 HBoot?
thanks again!
BTW I know I already posted this in the AOKP thread...Just wanted clarification from both devs.
mikelebz said:
For the new kernel is it possible to flash the newest HBoot from this thread just to make life easier? http://forum.xda-developers.com/showthread.php?t=2156368
Would that be the 2.14 HBoot?
thanks again!
BTW I know I already posted this in the AOKP thread...Just wanted clarification from both devs.
Click to expand...
Click to collapse
afaik, you MUST flash the RUU in its entirety. I believe h8 did something like just flash parts of the RUU and that bricked his phone. As long as your s-offed, no reason why you wouldn't want to RUU to 3.18.
I don't know if this is the correct place to ask this but I tried to RUU but I keep getting an error.
Torch not working
Anyone else getting FC's when trying to use the torch?
Misterowl said:
I don't know if this is the correct place to ask this but I tried to RUU but I keep getting an error.
Click to expand...
Click to collapse
What Error?
SuperCID? Yes or no?
S-ON or S-OFF?
Is s2w available on this kernel? My power button has been sticky so I've to move to the sense5 rom which I like. But definitely not as much as i love CM10.1
exad said:
What Error?
SuperCID? Yes or no?
S-ON or S-OFF?
Click to expand...
Click to collapse
Error 170
S-OFF
CID 11111111
ClassicalGas said:
Anyone else getting FC's when trying to use the torch?
Click to expand...
Click to collapse
Yeah, I'm pretty sure camera flash is broken too.
Misterowl said:
Error 170
S-OFF
CID 11111111
Click to expand...
Click to collapse
boot to bootloader/fastboot, ruu
So Girlfriend is finally getting tired of her Sense and is open to the idea of me rooting. Besides the camcorder resolution, hdmi, are there any bugs that would keep this from being a good dd. Thanks for the help guys
Hey whats up everybody I have a couple questions, Is it absolutely necessary to upgrade to 3.18 RUU for this ROM? The only reason I'm hesitating to ditch 1.09, is because I'm a bonafide flashaholic, and I'm not looking forward to fastboot flashing the boot image again, every time I want to try a new rom! (been there done that and it is totally NOT the business ) Which brings me to my second question, Does updating to 3.18 require you to fastboot flash the boot image before flashing new rom's? Evita/hboot 1.09/S-Off
JayDream said:
Hey whats up everybody I have a couple questions, Is it absolutely necessary to upgrade to 3.18 RUU for this ROM? The only reason I'm hesitating to ditch 1.09, is because I'm a bonafide flashaholic, and I'm not looking forward to fastboot flashing the boot image again, every time I want to try a new rom! (been there done that and it is totally NOT the business ) Which brings me to my second question, Does updating to 3.18 require you to fastboot flash the boot image before flashing new rom's? Evita/hboot 1.09/S-Off
Click to expand...
Click to collapse
Nah, with S-Off you don't need to fastboot flash anything.
Yesterday I was S-On, 1.09, now I'm S-Off 2.14 hboot (after using the 3.18 RUU). I've never had to fastboot flash the boot.img on this phone.
Sent from my One X using Tapatalk 4 Beta
ClassicalGas said:
Nah, with S-Off you don't need to fastboot flash anything.
Yesterday I was S-On, 1.09, now I'm S-Off 2.14 hboot (after using the 3.18 RUU). I've never had to fastboot flash the boot.img on this phone.
Sent from my One X using Tapatalk 4 Beta
Click to expand...
Click to collapse
OK thanks! Now can I fastboot flash the hboot using this method http://forum.xda-developers.com/showthread.php?t=2156686 or do I have to actually run the ruu?
JayDream said:
OK thanks! Now can I fastboot flash the hboot using this method http://forum.xda-developers.com/showthread.php?t=2156686 or do I have to actually run the ruu?
Click to expand...
Click to collapse
I RUU'd as per H8's recommendations, so can't confirm if that method works or not.
Sent from my One X using Tapatalk 4 Beta
So I RUU'd and downgraded the touch panel firmware and tried to flash a new recovery but my bootloader is locked.
I tried unlocking the bootloader in HTCdev and I keep getting this in my terminal.
ERROR: could not get pipe properties
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.013s]
finished. total time: 0.013s
ClassicalGas said:
I RUU'd as per H8's recommendations, so can't confirm if that method works or not.
Sent from my One X using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thanks man I appreciate it. But I think I'm gonna have to sit back on this one tho :/ at least until I have a better idea of what I'm getting into...
Sent from my HTC One XL using xda app-developers app
Misterowl said:
Error 170
S-OFF
CID 11111111
Click to expand...
Click to collapse
I kept getting an error that "Android phone is not connected"
Then i booted the phone into bootloader mode and tried it
That seemed to get it to work.
Still in the procees of downgrading and getting back to CM10.1
Just wanted to let you know
JayDream said:
Thanks man I appreciate it. But I think I'm gonna have to sit back on this one tho :/ at least until I have a better idea of what I'm getting into...
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Yeah I was a bit worried but was patient and followed all instruction instructions below (from the CarbonRom thread).
InflatedTitan said:
1. Download the 2 files for s-off and place in adb folder.
2. Download the recovery of choice and put in adb folder.
3 (optional) download the remove red text file and put in adb folder.
4. You'll have to downgrade touchscreen if you want to use aosp. Head to original dev sticky to download files from h8rift. Put those in adb folder
_________________________________________
1. S-off! Make sure you confirm in bootloader (it usually works easier from a sense rom btw.) 4.2.2 roms need updated adb but it may work.
2. When you ruu, it doesn't touch sdcard. But I would quickly mount and backup your pics and whatnot just in case.
3. Enter fast boot. Run the ruu on the computer. It'll bring you back to 100% stock.
4. Once you up and running, enter fast boot again and send twrp.
5. I recommend to get rid of the ugly ass red text on splash. Follow Liam's thread to rid it.
6. While in fastboot go ahead and downgrade touchscreen following h8rifts instructions.
7. Now you're golden to flash anything you want :thumbup:
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
I used the RUU from here
I used a windows computer instead of a Mac to unlock and it worked. So yeah Mac bad.
Sent from my One X using xda app-developers app

[Q] [ assistance required ] lets wake up this ONE S!

Hello, my HTC ONE S is soft bricked, its stuck now at boot loop. I have done many many tutorials, many custom tools tryed, no luck. I don't know what else to do.. The only hope is you guys, could please someone would supervise me on step by step instructions on what to do?
I would try to respond in details as fast as i can about the situation and wait for later instructions.
STATUS:
S4 class device
CID O2___001
TAMPERED
UNLOCKED
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.12.50.05.05
OpenDSP-v31.1.0.45.0815
eMMC-boot
TWRP v2.6.3.0
Last installed rom: cm-10-2.0.-ville.zip When device boots in to a rom, after HTC logo boot-loop appears, and all over again.
Booting in to HBOOT Works, booting in to a Recovery also works.
SDK platform-tools installed, USB ADB drivers installed.
FASTBOOT commands works,
ADB commands - does not, adb device not found because rom wont boot.
Adb sideload works.
what i should do?
Did you flash kernel when installing the rom?
Sent from my HTC One S
ka_55 said:
Did you flash kernel when installing the room?
Sent from my HTC One S
Click to expand...
Click to collapse
as far as i remember - yes, but cm 10 did not provide separate boot.img or instructions about it.
You have to flash it separately since you are s-on. There should be a boot.img in the rom's zip, extract it and flash via fastboot
Sent from my HTC One S
ka_55 said:
You have to flash it separately since you are s-on. There should be a boot.img in the rom's zip, extract it and flash via fastboot
Sent from my HTC One S
Click to expand...
Click to collapse
This should fix your problem, good luck!
Sent from my One S
ka_55 said:
You have to flash it separately since you are s-on. There should be a boot.img in the rom's zip, extract it and flash via fastboot
Sent from my HTC One S
Click to expand...
Click to collapse
OMG, it just booted in to a CyanogenMOD!! but how lol , i mean, i could swear i had done this before and no luck. lol but i did it now anyway exact what u said anyways, and it works!! lol this phone was unused for a month and a half just because i tough i did everything lol thank you!
gab1one said:
This should fix your problem, good luck!
Sent from my One S
Click to expand...
Click to collapse
thanx, it should did! :victory:
Good to know I could help.
By the way you said that you installed cm-10, and strongly recommend you to try cm-11. I think it's far more stable right now.
Anyway have fun
Sent from my HTC One S
ka_55 said:
Good to know I could help.
By the way you said that you installed cm-10, and strongly recommend you to try cm-11. I think it's far more stable right now.
Anyway have fun
Sent from my HTC One S
Click to expand...
Click to collapse
oh yes yes, i only used cm10 as a base rom, something clean to wake this phone up now what i will do is supercid, s-off and then go for something like maximus hd
It can be tough to supercid for you. Hboot 2.15 is a little problematic cause it has write protection. I hope you can do it. You shouldn't forget to enable root access to adb from developer options or you won't be able to use adb.
S-OFF
Saiyaru said:
oh yes yes, i only used cm10 as a base rom, something clean to wake this phone up now what i will do is supercid, s-off and then go for something like maximus hd
Click to expand...
Click to collapse
If you use rummrunner.us to S-OFF you wont need supercid.
I used it and it worked fine. You might need to experiment with the ROM.
Some aren't compatible, but you will only use it for the S-OFF.
Hope this helps you :good:
ka_55 said:
It can be tough to supercid for you. Hboot 2.15 is a little problematic cause it has write protection. I hope you can do it. You shouldn't forget to enable root access to adb from developer options or you won't be able to use adb.
Click to expand...
Click to collapse
Lol i did it! its now SUPERCID and S-OFF with Hboot 2.15
it was not easy... i did first supercid with hex editing trick, was hard to pull the special file, but i did some actions with manual pulling by recovery and build in file manager, but i managed to change and push back in with adb shell su.
the s-off part was the hardest. i tryed first rumrunner 0.5.0, dint worked, then moonshine 3.16 - dint worked, got error pretty quick, then i did soffbin3 method - no luck, but it might did some shanges in system anyways. Then, i did revone method by chmoding and sending revone commands with adb shell su. it did something but failed, but i told myself - hey, its still s-on, but maybe now i did some changes to the system anyways and now rumrunner will do is job more easily, well, here is what happened: i actually laughed my ass off reading this lol
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
it took long time, BUT IT DID THE JOB! XD
finally i can install pretty much anything i want :victory:
oh by the way: a little tip: if anybody would get trouble to install HTC ADB drivers with error (as windows cant find the patch specified), i installed samsung drivers instead by force (from galaxy s3 adb) cause i dint find any solution to solve htc driver issue.., but samsung adb drivers works perfectly with HTC!

[Q] Ye Old HTC Logo boot lock up

Just got an unlocked HTC One X to replace my old T989 and I have not been into switching ROMS since the days of the HD2 Leo. I tried to update to Kit Kat and sense 5.0 through ATTs OTA update. Now the phone will not boot up and only gets so far as the HTC screen.
All I want to do is just revert back to stock for now. Should I just reinstall the stock or is there more to this.
Boot loader works and the phone does indicate that it is charging. Any help would be awesome.
There is no official KitKat update for this phone, Android 4.2.2 is the latest official update available. Anyway, more information required. Please post your bootloader details, and did you use the build in updater in settings or did you apply the update manually?
Sent from my Evita
g29er123 said:
Just got an unlocked HTC One X to replace my old T989 and I have not been into switching ROMS since the days of the HD2 Leo. I tried to update to Kit Kat and sense 5.0 through ATTs OTA update. Now the phone will not boot up and only gets so far as the HTC screen.
All I want to do is just revert back to stock for now. Should I just reinstall the stock or is there more to this.
Boot loader works and the phone does indicate that it is charging. Any help would be awesome.
Click to expand...
Click to collapse
Need bootloader details. Post what is in the first 5 lines of bootloader.
Also, the latest AT&T OTA updates to 4.2.2, not KitKat (although it is Sense 5).
---------- Post added at 02:29 PM ---------- Previous post was at 01:36 PM ----------
timmaaa said:
There is no official KitKat update for this phone, Android 4.2.2 is the latest official update available. Anyway, more information required. Please post your bootloader details, and did you use the build in updater in settings or did you apply the update manually?
Click to expand...
Click to collapse
Beat me to it by 2 minutes . . .
redpoint73 said:
Beat me to it by 2 minutes . . .
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
^^^
Sent from my Evita
timmaaa said:
There is no official KitKat update for this phone, Android 4.2.2 is the latest official update available. Anyway, more information required. Please post your bootloader details, and did you use the build in updater in settings or did you apply the update manually?
Sent from my Evita
Click to expand...
Click to collapse
Oops you are right..it is 4.2.2 I updated the phone through settings...software update. It will only one note of the start up jingle and the top quarter of the screen flashes white on occasion.
Boot loader:
EVITA PVT SHIP S -ON RL
HBOOT-2.18.0000
Radio-0.19as.32.09.11.2
openDSP-v29.1.0.45.0622
eMMC-boot
It looks like the OTA has somehow only done half the job. Before I advise you any further I need to know what it says above the bootloader info you gave, it'll be locked, relocked, or unlocked. I'm also going to need you to check your CID using fastboot. If you don't have adb and fastboot installed you'll need to do that, there are plenty of guides available on XDA.
Sent from my Evita
timmaaa said:
It looks like the OTA has somehow only done half the job. Before I advise you any further I need to know what it says above the bootloader info you gave, it'll be locked, relocked, or unlocked. I'm also going to need you to check your CID using fastboot. If you don't have adb and fastboot installed you'll need to do that, there are plenty of guides available on XDA.
Sent from my Evita
Click to expand...
Click to collapse
Locked
CID: CWS_001
Ok. What method did you use to get your CID? Fastboot?
Sent from my Evita
timmaaa said:
Ok. What method did you use to get your CID? Fastboot?
Sent from my Evita
Click to expand...
Click to collapse
Downloaded Minimal ADB and Fasboot.
Went into fastboot and typed: fastboot getvar cid
Cool, that's what I wanted to hear. I think your best option is probably to run the official 5.18 RUU, which you'll find here:
http://dl3.htc.com/application/HTC_One_X_RUU_5.18.502.1.exe
Sent from my Evita
timmaaa said:
Cool, that's what I wanted to hear. I think your best option is probably to run the official 5.18 RUU, which you'll find here:
Sent from my Evita
Click to expand...
Click to collapse
For some reason my device is not recognized by my computer unless I am in boot loader options.
The phone needs to be in bootloader mode to run an RUU anyway, but it's probably a good idea to fix your problem first. What OS are you running on your PC?
Sent from my Evita
timmaaa said:
The phone needs to be in bootloader mode to run an RUU anyway, but it's probably a good idea to fix your problem first. What OS are you running on your PC?
Sent from my Evita
Click to expand...
Click to collapse
Windows 7. Running the RUU now from bootloader for the last 15 minutes and the install wizard is still updating rom image and only HTC logo showing on the phone.
Did you confirm a proper connection before starting the RUU?
Sent from my Evita
timmaaa said:
Did you confirm a proper connection before starting the RUU?
Sent from my Evita
Click to expand...
Click to collapse
Yes. according to HTC sync manager.
Ok, but did you confirm your drivers are ok by testing adb and fastboot?
Also, you need to uninstall HTC Sync Manager (but leave the drivers installed), it interferes with the RUU process.
Sent from my Evita
timmaaa said:
Ok, but did you confirm your drivers are ok by testing adb and fastboot?
Also, you need to uninstall HTC Sync Manager (but leave the drivers installed), it interferes with the RUU process.
Sent from my Evita
Click to expand...
Click to collapse
No I didnt do that. How do I test the drivers in adb and fastboot and how do I leave only the drivers for HTC sync manager. Do I put them in a folder or something? And yeah the the install never got past installing ROM image. Now the phone just has the backlight on.
You choose to uninstall Sync Manager, but don't choose HTC drivers (they're separate). Test your connection by using the "adb devices" command while booted into Android, and "fastboot devices" while connected in fastboot usb mode.
Sent from my Evita
timmaaa said:
You choose to uninstall Sync Manager, but don't choose HTC drivers (they're separate). Test your connection by using the "adb devices" command while booted into Android, and "fastboot devices" while connected in fastboot usb mode.
Sent from my Evita
Click to expand...
Click to collapse
Uninstalled HTC Sync but I had no option to keep drivers. In my program mananger there is a file that says that says HTC driver installer. I did check the connection in android boot.
I got:
daemon started sucessfully
List of devices attached
When I check in fastboot it says
ht2b3w303351 fastboot
I am assuming maybe I am missing the drivers?
I also want to thank you for helping me thus far, I have learned alot and hopefully I can get it working.
How about when you use the adb command? In the start menu under the HTC section it should have HTC Sync Manager and HTC drivers as separate options, in any case it looks like they're still there if your commands are working.
Sent from my Evita

Categories

Resources