Database Info

[Q] Help! Desire S Not Booting - Possible eMMC issue.

I'm having problems with my girlfriend's Desire S. I installed CyanogenMod the day it was purchased, and have had no major problems with it at all, up until last night. Apps from the Market wouldn't update, throwing out a standard error with the option to force close. On restarting the phone thanks to it crashing, the phone now boots to the HTC logo and doesn't get any further.
I have CWM installed and I'm still able to access the bootloader. I've scoured this forum and many others trying to find a solutions, and wouldn't be posting for help if I knew there was some way of getting this sorted without bothering you guys. It appears to be a somewhat common problem, but some of it goes straight over my head. I've tried flashing a new recovery, wiping the cache, a factory reset but none of it seems to register. Can't install a new ROM
It appears it's the dreaded "eMMC" issue, but before I'm reluctant to send it off given it's S-OFF, so thought I'd throw it out there. I understand it's an issue that's cropped up a fair few times but I'm tearing my hair out trying to sort it and really don't know what to do with it. Any suggestions would be super helpful.
Not sure if this information helps at all:
Revolutionary Hboot 6.98.1002
Hboot Factory Rest option just freezes phone.
Fastboot seems to register with PC, but trying to install a new recovery or new hboot brings about an "error: cannot load 'hboot.img/recovery.img' in cmd.
Install ZIP from SD Card brings the following error:
"E:Error in /sdcard/updatecm-7.1.0-DesireS-signed.zip
(Status 1)
Installation aborted."
Attempted to install 4EXT Recovery via CWM though when restarting phone it's still just CWM. Probably doing this totally wrong but again not really sure how to go about it to fix Cache issue.
Also get the standard E:Can't mount /cache/recovery/command, etc errors on using CWM.
Thanks in advance, any help is absolutely appreciated, and would stop my girlfriend having to use, in her words, a "crappy, dying, useless Sony Ericsson," after only having this one for less than a month.
Nathan.

Flash 4EXT recovery via fastboot. Use search.
If you still can access recovery and/or bootloader, there may still be hope. Based on research, complete eMMC failure will just give you a vibrating phone, that's it.
Hint!

Check my signature
Sent from my HTC Desire S using Tapatalk

Thanks guys for the quick replies, really appreciate the help.
Skanob, I've tried to Flash 4EXT recovery via flashboot, but it never seems to move past "writing 'recovery'. . . Should it take a particularly long time or pretty much straight away? Also, when in flashboot USB I find I'm unable to move up or down, as if flashboot has crashed as soon as it attempts to flash recovery.
amidabuddha, when I boot into recovery and use cmddmesg | grep mmc0, I get the error message "'cmddmesg' is not recognized as an internal or external command, operable program or batch file.
Again, really appreciate the help. I try to steer clear of starting help threads if possible but as it's not my phone I really wanted to get this fixed for her as soon as possible, and I'm a complete noob.

NathanRandom said:
...
amidabuddha, when I boot into recovery and use cmddmesg | grep mmc0, I get the error message "'cmddmesg' is not recognized as an internal or external command, operable program or batch file.
Click to expand...
Click to collapse
the command is:
Code:
dmesg | grep mmc0
copy it from here and paste it to your command prompt

Sorry, I get the same error with that command. Really at a loss as to what I should do now.

NathanRandom said:
Sorry, I get the same error with that command. Really at a loss as to what I should do now.
Click to expand...
Click to collapse
sorry, my miss I did not add the "adb shell" command in my guide
type in the command prompt:
Code:
adb devices [I](your device serial number should be listed)[/I]
adb shell
dmesg | grep mmc0
try this and if the output is positive continue with the steps described in the guide

Help, I Broke My phone!!
A big hello to the fans of this forum, I would like to explain my problem and I will so much appreciate your answers:
I try to flash-Android_Revolution_HD 4G_6.1.5 [ROM] on my HTC_Desire_S, after I reboot and waited several minutes, the screen remained blank with no access to my phone several times but no available and more when I reboot in recovery mode, i push on recovery but the screen remains blank and I can not access the ClockworkMod menu to uninstall the ROM bleow.!.
My God, what shall I do??

viadora13 said:
A big hello to the fans of this forum, I would like to explain my problem and I will so much appreciate your answers:
I try to flash-Android_Revolution_HD 4G_6.1.5 [ROM] on my HTC_Desire_S, after I reboot and waited several minutes, the screen remained blank with no access to my phone several times but no available and more when I reboot in recovery mode, i push on recovery but the screen remains blank and I can not access the ClockworkMod menu to uninstall the ROM bleow.!.
My God, what shall I do??
Click to expand...
Click to collapse
search for RUU

amidabuddha said:
sorry, my miss I did not add the "adb shell" command in my guide
type in the command prompt:
Code:
adb devices [I](your device serial number should be listed)[/I]
adb shell
dmesg | grep mmc0
try this and if the output is positive continue with the steps described in the guide
Click to expand...
Click to collapse
Thanks for that, I don't get any of the error messages that would indicate a fried chip which is a relief!
However I'm still a little confused as to the next best step. The SD card had an error on it when connecting it to a PC and needed to be formatted, there isn't a backup of the ROM on their. I've got Revolutionary Hboot 6.98.1002.
When I try to factory reset using Revolutionary, it seems to just stall and not do anything, crashing and not letting me select any other options.
I've also tried flashing a stock ROM via fastboot USB with the RUU, and it again just crashes and needs a hard reset.
Trying to install CM7 via ClockworkMod also doesn't work. Says it's installing update then after about 5 minutes get the following:
"E:Error in /sdcard/update-cm-7.1.0-DesireS-signed.zip
(Status 1)
Installation aborted."
When I switch on the phone and it boots to HBOOT, I get an error stating that "Loading... P88IMG not found. No image or wrong image." When I place P88IMG onto SD Card and start hboot, it says it's updating and then just stays that way, crashing the phone. Again.
Sorry to throw a wall of errors at you guys.

NathanRandom said:
Thanks for that, I don't get any of the error messages that would indicate a fried chip which is a relief!
However I'm still a little confused as to the next best step. The SD card had an error on it when connecting it to a PC and needed to be formatted, there isn't a backup of the ROM on their. I've got Revolutionary Hboot 6.98.1002.
When I try to factory reset using Revolutionary, it seems to just stall and not do anything, crashing and not letting me select any other options.
I've also tried flashing a stock ROM via fastboot USB with the RUU, and it again just crashes and needs a hard reset.
Trying to install CM7 via ClockworkMod also doesn't work. Says it's installing update then after about 5 minutes get the following:
"E:Error in /sdcard/update-cm-7.1.0-DesireS-signed.zip
(Status 1)
Installation aborted."
When I switch on the phone and it boots to HBOOT, I get an error stating that "Loading... P88IMG not found. No image or wrong image." When I place P88IMG onto SD Card and start hboot, it says it's updating and then just stays that way, crashing the phone. Again.
Sorry to throw a wall of errors at you guys.
Click to expand...
Click to collapse
Do not be sorry the purpose of this forum is to ask and answer The good news are that your eMMC is still in shape!
Now wipe the cache partition from ClockworkMod (there is an option in the menu) and reboot the phone
If no sucess follow the steps described here
This will bring you back to Stock.
Then you can S-OFF and flash a custom ROM again if you like
Good luck

But which of those steps I mentioned is the correct thing to be doing? I'm confused as to what I should do now once I've wiped the cache and rebooted the phone.
Also I've tried the steps you mentioned, but the file it created on the SDCard was 0bytes and brings up nothing when I open it in Hex Editor. It's only actually written the file once, other times it's appeared to but nothings there when I move the card to the PC.
I'm fairly certain of the ROM needed as it was a branded Vodafone unit sold in the UK. Using the links provided to change hboot, in what order should they be used? When trying to flash hboot I receive the following error:
2767 KB/s (1048576 bytes in 0.370s)
chmod: /data/local/tmp/hboot.img: Not a directory
Please accept superuser request on your phone
/sbin/sh: su: not found
Press any key to continue . . .
And when placing PG88IMG onto SD Card, when phone attempts to update it simply crashed hboot, which I'm assuming is to do with the hboot being the wrong version needed.

NathanRandom said:
But which of those steps I mentioned is the correct thing to be doing? I'm confused as to what I should do now once I've wiped the cache and rebooted the phone.
Also I've tried the steps you mentioned, but the file it created on the SDCard was 0bytes and brings up nothing when I open it in Hex Editor. It's only actually written the file once, other times it's appeared to but nothings there when I move the card to the PC.
I'm fairly certain of the ROM needed as it was a branded Vodafone unit sold in the UK. Using the links provided to change hboot, in what order should they be used? When trying to flash hboot I receive the following error:
2767 KB/s (1048576 bytes in 0.370s)
chmod: /data/local/tmp/hboot.img: Not a directory
Please accept superuser request on your phone
/sbin/sh: su: not found
Press any key to continue . . .
And when placing PG88IMG onto SD Card, when phone attempts to update it simply crashed hboot, which I'm assuming is to do with the hboot being the wrong version needed.
Click to expand...
Click to collapse
Ok, since I am not much experienced with branded devices I made some research across the forum and probably flashing this hboot on a branded device will be risky.
Create a GoldCard (look in the index thread in Android Development subforum for a guide). Then download and install RUU_Saga_Vodafone_UK_1.32.161.1_Radio_20.28b.30.08 05U_38.03.02.15_M_release. With the GoldCard it should overwrite everything on your device.
Try this and post back.
EDIT: note that not every SDcard is suitable for a GoldCard. Recommended is a 2 GB one.

After trying multiple lutions I decided to pop into the Vodafone store yesterday and get it sent away. I'm sure they'll probably send it back and claim a void warranty but it's worth a shot, I got the guy there to mention it was due to the Update All Market error, so hoping the fact it was rooted doesn't play too much of a role.
Thanks for your help, may not have managed to sort it myself in the end but it was definitely appreciated.

TF300 bricked?

So I've searched thru the thread...but I don't know what to search for. Let me explain my problem:
I had Unlocked the device, had TWRP as recovery and was running cleanROM 1.2. So I downloaded cleanROM 2.5 (JB) and put that on my SD card. I also read that I needed TWRP 2.2.2.0 to load it.
So I downloaded and fastbooted TWRP 2.2.2.0 ICS.blob, recovery flashed ok and was able to install cleanROM. Upon reboot, it just bootlooped.
So I figured I needed TWRP 2.2.2.0 JB.blob. I fastboot installed that with no problem but when I rebooted to fastboot mode, I stupidly selected to wipe data from there and now the tablet bootloops with no option for the fastboot. when I try to hold down the power and volume down key the device states "Android cardhu-user bootloader (2.10 e) released by "US_ePad-9.4.3.30-20120604" A03 checking for Android ota revovery" then goes to Booting recovery kernal image.
Did I kill it?

I'm going to assume from your post that you were running ICS bootloader and had never updated to stock JB, if so you were ICS.
I read your post last night but didn't have an answer to your problem so I decided to sleep on it.
If I surmised correctly in my previous statements you had an ICS bootloader and flashed a JB rom, then you flashed a JB recovery while you still had an ICS bootloader. I don't think the data wipe is a factor here. You can't mix and match ICS and JB recoveries and roms the bootloader must match.
I know; how does this help me. We need to establish your situation absolutely if there is any chance of recovery.
I'm still thinking about your situation and your reply will give myself and many others reading your post enough info to consider your options.

I fastboot is not working and you were still on ICS bootloader, try if ADB works.
If yes type this:
dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1
then press enter
Then type this
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
and press enter.
Now try if you get fastboot back. If yes fastboot the ICS recovery and then you should be good to go.
1st flash the ICS Stock Rom and then fastboot the ICS recovery again. Now you should be back to normal.
If this doesn´t work dl this file:
http://www.4shared.com/zip/7XYW-4c4/WSG_UnBricker_TF300T_V102.html
unpack it
run WSGFlasher batch
choose 2 as selection and press enter
in the new window choose 1 to fully unbrick and press enter
in the new window choose 1 to Full recovery and press enter
let it run. Needs about 5 to 15 minutes
When everything is done reboot.

tobdaryl said:
I'm going to assume from your post that you were running ICS bootloader and had never updated to stock JB, if so you were ICS.
I read your post last night but didn't have an answer to your problem so I decided to sleep on it.
If I surmised correctly in my previous statements you had an ICS bootloader and flashed a JB rom, then you flashed a JB recovery while you still had an ICS bootloader. I don't think the data wipe is a factor here. You can't mix and match ICS and JB recoveries and roms the bootloader must match.
I know; how does this help me. We need to establish your situation absolutely if there is any chance of recovery.
I'm still thinking about your situation and your reply will give myself and many others reading your post enough info to consider your options.
Click to expand...
Click to collapse
So I'm new to the TF300 as you can probably guess. I flash roms constantly with my S-off Rezound and my prior OG Droid. I'm not new to the game, just new to the TF300t.
I did finally grab the right keywords and found pretty similar posts to what happened to me, and it looks like I bricked it. (though I sure hope not.)
I think you are right that the data wipe isn't the factor. I just thought I needed a JB recovery to flash the JB rom. You know how a certain boot.img will just send your phone into a bootloop, but you flash the correct boot.img, and it'll boot straight into the rom? That was my thinking going into this. (guess I should have taken MORE time to read instead of bullishly charging in...
I also believe you are right in your first statement, I received the tablet with ICS. I rooted it and flashed CleanRom 1.2 immediately, and haven't flashed again. I saw jellybean (Cleanrom 2.5) out and thought, why not? Flashed TWRP 2.2.2.0 ICS and proceeded to install CleanROM 2.5. I did not know I needed to be on a JB bootloader. You are correct in that. BUT....after flashing the TWRP 2.2.2.0 JB recovery, I WAS able to go back into fastboot mode and could switch between Android/USB/Wipe Data... if only I had chosen the USB option.....
I await any help you can offer.
Thanks so much.

mikaole said:
I fastboot is not working and you were still on ICS bootloader, try if ADB works.
If yes type this:
dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1
then press enter
Then type this
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
and press enter.
Now try if you get fastboot back. If yes fastboot the ICS recovery and then you should be good to go.
1st flash the ICS Stock Rom and then fastboot the ICS recovery again. Now you should be back to normal.
If this doesn´t work dl this file:
http://www.4shared.com/zip/7XYW-4c4/WSG_UnBricker_TF300T_V102.html
unpack it
run WSGFlasher batch
choose 2 as selection and press enter
in the new window choose 1 to fully unbrick and press enter
in the new window choose 1 to Full recovery and press enter
let it run. Needs about 5 to 15 minutes
When everything is done reboot.
Click to expand...
Click to collapse
Thanks so much, I just returned home from a trip and will try this first thing in the morning.
Though I feel like the bootloop it's stuck in doesn't give me enough time for ADB to work. If ADB doesn't work, I think I'm bjorked.

SO if I read you guys correctly, I would manually have to flash a JB bootloader? It's not something that happens automagically when you flash a ROM? I never flashed a bootloader, just the two recoveries, then once in recovery, the ROM.

Xsoldier2000 said:
So I'm new to the TF300 as you can probably guess. I flash roms constantly with my S-off Rezound and my prior OG Droid. I'm not new to the game, just new to the TF300t.
I did finally grab the right keywords and found pretty similar posts to what happened to me, and it looks like I bricked it. (though I sure hope not.)
I think you are right that the data wipe isn't the factor. I just thought I needed a JB recovery to flash the JB rom. You know how a certain boot.img will just send your phone into a bootloop, but you flash the correct boot.img, and it'll boot straight into the rom? That was my thinking going into this. (guess I should have taken MORE time to read instead of bullishly charging in...
I also believe you are right in your first statement, I received the tablet with ICS. I rooted it and flashed CleanRom 1.2 immediately, and haven't flashed again. I saw jellybean (Cleanrom 2.5) out and thought, why not? Flashed TWRP 2.2.2.0 ICS and proceeded to install CleanROM 2.5. I did not know I needed to be on a JB bootloader. You are correct in that. BUT....after flashing the TWRP 2.2.2.0 JB recovery, I WAS able to go back into fastboot mode and could switch between Android/USB/Wipe Data... if only I had chosen the USB option.....
I await any help you can offer.
Thanks so much.
Click to expand...
Click to collapse
Please see the post directly below mine. mikaole has already provided an excellent path to recover your unit.
Good Luck!

tobdaryl said:
Please see the post directly below mine. mikaole has already provided an excellent path to recover your unit.
Good Luck!
Click to expand...
Click to collapse
Thanks all, but I can't get ADB working on it. It's just a constant reboot - loop.
I guess I need to contact ASUS and try to get it repaired... cheaply, I hope.

Xsoldier2000 said:
Thanks so much, I just returned home from a trip and will try this first thing in the morning.
Though I feel like the bootloop it's stuck in doesn't give me enough time for ADB to work. If ADB doesn't work, I think I'm bjorked.
Click to expand...
Click to collapse
Time for adb; interesting statement. It brings to mind something I have used on another unit with bootloop and on several other units to get boot logs.
I'll try to describe. In terminal you use a command and afterwards if you wish to use the same command you use up arrow and the last command is typed for you and just hit return. I think this also works in windows cmd but can't verify.
Why do we care? Get in terminal and type the first adb command given above and hit return. Now we can send this command twice in one second. Up arrow ( command typed for you ) power on unit, hit return, up arrow hit return, etc. You could verify if there is an adb window of time available by typing adb devices and look at the output. Anything other than devices and blank means there is an adb window.
Sorry; easy to do but hard to describe. Worth a try if you are ready to ship off. This is the only other thing I can think of for your situation.
Good Luck!

tobdaryl said:
Time for adb; interesting statement. It brings to mind something I have used on another unit with bootloop and on several other units to get boot logs.
I'll try to describe. In terminal you use a command and afterwards if you wish to use the same command you use up arrow and the last command is typed for you and just hit return. I think this also works in windows cmd but can't verify.
Why do we care? Get in terminal and type the first adb command given above and hit return. Now we can send this command twice in one second. Up arrow ( command typed for you ) power on unit, hit return, up arrow hit return, etc. You could verify if there is an adb window of time available by typing adb devices and look at the output. Anything other than devices and blank means there is an adb window.
Sorry; easy to do but hard to describe. Worth a try if you are ready to ship off. This is the only other thing I can think of for your situation.
Good Luck!
Click to expand...
Click to collapse
I will def. try that. I have only usually tried the adb once it's in the loop, not from cold start.
I am aware of the command line trick, I've been using Linux for about 7 years, and was surprised to see it in windows.
Great idea to get it running before hand though, enter > up Arrow . enter > up arrow......

Xsoldier2000 said:
I will def. try that. I have only usually tried the adb once it's in the loop, not from cold start.
I am aware of the command line trick, I've been using Linux for about 7 years, and was surprised to see it in windows.
Great idea to get it running before hand though, enter > up Arrow . enter > up arrow......
Click to expand...
Click to collapse
No go. I drained the battery, then plugged it in for like 20 minutes to charge. I got ADB ready with adb devices and began trying.
No devices. for the heck of it I plugged in my phone during the up arrow enter marathon, and adb picked up the phone right away.
Sucks, but thanks so much for all your help. Looking for a refurb or a repair place now.

I'm sorry but I don't know anything else to try.
There is a manual reset on the side below the sdcard.

tobdaryl said:
I'm sorry but I don't know anything else to try.
There is a manual reset on the side below the sdcard.
Click to expand...
Click to collapse
No Worries, I appreciate all your help.

My problem was more or less similar and i managed to fix mine
Link to my thread ---> http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
In my case I installed the wrong recovery (TWRP-JB) with the wrong bootloader 4.2 and bricked, I also did the mistake to wipe everything. but after several tries I fixed mine, go to my thread on the link above for details.
Hope it helps.

help.

i just installed pacman rom using clockworkmod recovery something..

fastboot flash boot boot.img.
Google that, instead of spamming threads in all the forums. This is the most commonly occurring beginner error, it's stated multiple times in multiple places, and still people keep asking instead of reading.
If it's not your case - look at "non-Sony screen" thread.

Jack_R1 said:
fastboot flash boot boot.img.
Google the damn thing, instead of spamming threads in all the forums.
Click to expand...
Click to collapse
m extremely sorry..
but i have been trying since 2 hrs..
still could not find a solution..
pleae help!

jigi1993 said:
m extremely sorry..
but i have been trying since 2 hrs..
still could not find a solution..
pleae help!
Click to expand...
Click to collapse
please guys help..
the bloody boot.img is not supportted by winzip..
'fastboot' is not recognized as
operable program or batch file.
error

Jack_R1 said:
fastboot flash boot boot.img.
Google that, instead of spamming threads in all the forums. This is the most commonly occurring beginner error, it's stated multiple times in multiple places, and still people keep asking instead of reading.
If it's not your case - look at "non-Sony screen" thread.
Click to expand...
Click to collapse
jigi1993 said:
please guys help..
the bloody boot.img is not supportted by winzip..
'fastboot' is not recognized as
operable program or batch file.
error
Click to expand...
Click to collapse
Did you do what Jack said and GOOGLE IT????? Go away and put some effort in for yourself - it will be much better for you to understand WHAT and WHY you need to do things - or next time you will brick your phone beyond recovery.

SimonTS said:
Did you do what Jack said and GOOGLE IT????? Go away and put some effort in for yourself - it will be much better for you to understand WHAT and WHY you need to do things - or next time you will brick your phone beyond recovery.
Click to expand...
Click to collapse
Sir m damn serious..
i hve been googling in around 4 hrs now..
i did my best but i cant now..
please provide an easy solution..
the boot image error comes in..
i cant extract that file .

Here you go

SimonTS said:
Here you go
Click to expand...
Click to collapse
kk.

So you've installed ADB then?

SimonTS said:
So you've installed ADB then?
Click to expand...
Click to collapse
i downloaded pacman rom.
copied it into root of sd.
wiped data and installed it through clockmod recovery .!
it was installed properly but after reboot it stuck on htc white screen..

:banghead:

teadrinker said:
:banghead:
Click to expand...
Click to collapse
I couldn't agree more - I give up on this guy, if he can't even deal with what I asked then there is no hope for him.

Ok I don't know why I'm doing this but your answer is in this thread
http://forum.xda-developers.com/showthread.php?t=1525100
[Guide] How to root, install EXT4 recovery and custom ROM on HBOOT 2.00.0002
Everyone has a right to be stupid. Some just abuse the privilege

jugg1es said:
Ok I don't know why I'm doing this but your answer is in this thread
http://forum.xda-developers.com/showthread.php?t=1525100
[Guide] How to root, install EXT4 recovery and custom ROM on HBOOT 2.00.0002
Everyone has a right to be stupid. Some just abuse the privilege
Click to expand...
Click to collapse
Because we are too nice...
@op cd ( http://en.wikipedia.org/wiki/Cd_(command) ) in the directory where your fastboot and adb in located ( path-to/platform-tools) and fastboot commands should be working.

Oh c'mon guys don't be so rude. You've been noobs too.
To return in topic:
1) you have the clockwork mod recovery, so I'm assuming that you already have unlocked the boot loader but you still S-ON ( you can check it by powering up the phone by pressing TOGETHER the volume down AND the power button). But i may ask you to verify that you have installed on your PC at least ADB and FASTBOOT? If you're not, please install them, otherwise you won't be able to get your phone work.
2) now, you say that you have flashed the pacman ROM but you are stuck on the HTC logo. Don't panic. It is a common issue, i have done it a lot of times. Just check from adb if it can see you device (you have to plug in the phone to the computer via your recharge cable). If it sees the phone it is quite simple to return to the boot loader. Simply open a terminal on your pc, navigate on the folder in which you have saved adb and write "adb reboot bootloader". This will bring you to the bootloader screen. Check now if there is written "FASTBOOT USB". If not and it is written HBOOT USB navigate with the volume keys on fastboot. This should bring you to the fastboot usb.
Now double click on the .zip containing the pacman ROM you've installed. Extract ONLY the boot.img and place it in the same directory in which you've placed fastboot. Now in the terminal of you PC write "fastboot flash boot boot.img" and then reboot the phone. This should solve your issue.
If the adb doesn't see you phone you have to pull out the battery, WAIT at least 30 seconds, replace it, and then press TOGETHER volume down and power button to enter into bootloader. From there follow the step that i wrote you previously and you'll be good to go!
Sent from my Desire S using xda app-developers app

Jedioscuro said:
Oh c'mon guys don't be so rude. You've been noobs too.
To return in topic:
1) you have the clockwork mod recovery, so I'm assuming that you already have unlocked the boot loader but you still S-ON ( you can check it by powering up the phone by pressing TOGETHER the volume down AND the power button). But i may ask you to verify that you have installed on your PC at least ADB and FASTBOOT? If you're not, please install them, otherwise you won't be able to get your phone work.
2) now, you say that you have flashed the pacman ROM but you are stuck on the HTC logo. Don't panic. It is a common issue, i have done it a lot of times. Just check from adb if it can see you device (you have to plug in the phone to the computer via your recharge cable). If it sees the phone it is quite simple to return to the boot loader. Simply open a terminal on your pc, navigate on the folder in which you have saved adb and write "adb reboot bootloader". This will bring you to the bootloader screen. Check now if there is written "FASTBOOT USB". If not and it is written HBOOT USB navigate with the volume keys on fastboot. This should bring you to the fastboot usb.
Now double click on the .zip containing the pacman ROM you've installed. Extract ONLY the boot.img and place it in the same directory in which you've placed fastboot. Now in the terminal of you PC write "fastboot flash boot boot.img" and then reboot the phone. This should solve your issue.
If the adb doesn't see you phone you have to pull out the battery, WAIT at least 30 seconds, replace it, and then press TOGETHER volume down and power button to enter into bootloader. From there follow the step that i wrote you previously and you'll be good to go!
Sent from my Desire S using xda app-developers app
Click to expand...
Click to collapse
Hey, i wasn't rude. I gave e a thread that is a good starting point to solve his issue without talking him through it
A word to the wise ain't necessary -- it's the stupid ones that need the advice.
Bill Cosby

jugg1es said:
Hey, i wasn't rude. I gave e a thread that is a good starting point to solve his issue without talking him through it
Click to expand...
Click to collapse
^^^^ This ^^^^ There is a HUGE difference between helping someone when they need help and helping someone when they are just being too lazy to actually read and find things out themselves.
I see it as no different to when I need tech-support from one of my equipment suppliers. If I call them up with a genuine problem they will help me, but if I phone them and say "Where do I plug the keys in?" or "I've turned the kit on but didn't bother reading the instructions first, now it's broken" - what do you think their reply to me will be?

SimonTS said:
^^^^ This ^^^^ There is a HUGE difference between helping someone when they need help and helping someone when they are just being too lazy to actually read and find things out themselves.
I see it as no different to when I need tech-support from one of my equipment suppliers. If I call them up with a genuine problem they will help me, but if I phone them and say "Where do I plug the keys in?" or "I've turned the kit on but didn't bother reading the instructions first, now it's broken" - what do you think their reply to me will be?
Click to expand...
Click to collapse
Yeah, you're right. But from the disperation of the guy It seemed to me pointless to leave him with a non-functioning phone without any advise. After all this is a forum plenty of people that know how to do practically everything with an android device, but I don't think that everyone have started from a solid programming base or a perfect hardware knowledge.
Regarding me, I have looked into this forum a couple of months BEFORE even try to unlock my phone and flashing something other than the horrible desire's gingerbread stock rom, but I understand the people who wants to try something new, even if they are not so expert.
For the next time, don't worry I'll be mercyless

I'm always ready to help where i can but. It seems like the op followed half a guide then just assumed it would work, i must of read all the guides until my head hurt, and most of my first posts were silly questions already posted. I learnt far more about my phone from searching than i think i could have from my first posts
A word to the wise ain't necessary -- it's the stupid ones that need the advice.
Bill Cosby

He would have avoided all the pain if he used the boot img flashing software
Sent from my Desire S using xda premium

[Q] Updating new One XL for my father?

Hi. I'm a newbie on these forums, so please be easy on me. My father recently decided that he wanted to enter the smartphone world and decided on a One XL. He bought it on eBay from a Chinese seller, so I'm pretty sure the One XL is the Chinese variant w/ the 2600 band for LTE.
I'm generally a BlackBerry guy (currently own a Z10), but have used all the phone OSes at some point. I've been pretty comfortable modifying my own BlackBerry, I use Linux at home as my main OS, and I'm also a computer science major studying programming (so I'm not in over my head here).
There are few things that I think would be cool for my Dad:
1) LTE speeds on T-Mobile. If not, 3G or HSPA
2) Android 4.4 KitKat
3) Sense 5
I'm pretty familiar with sideloading so that shouldn't be a problem (Flappy Bird).
I hope my Dad didn't didn't mess up for himself by buying the Chinese version if he wants faster speeds (than EDGE) on T-Mobile. I appreciate any help you may give. Thank you!

You should have no problems getting LTE on the device. You can have KitKat but it will be via an aosp ROM, not Sense. Sense ROMs for our device only go up to Android 4.2.2 and that's probably where they'll stay.
If you want to run a custom ROM on it just head over to htcdev and unlock the bootloader, then you can install a custom recovery, and from there you can install a custom ROM. I have detailed instructions for many of these operations in my How-To Guide For Beginners thread in my signature. You should also read the Evita FAQ thread in my signature, and bookmark the resource thread.
What are the bootloader details on the device? To boot into the bootloader there are two methods.
With phone powered on
Hold the volume down button, then hold the power button (so you're holding both buttons together), the button lights will start to flash, they will stop flashing and the screen will go blank, after a couple of seconds let go of the power button but continue to hold the volume down button until you reach the white screen with text, this is your bootloader.
With phone powered off
Hold the volume down button, then hold the power button (so you're holding both buttons together), after a couple of seconds let go of the power button but continue to hold the volume down button until you reach the white screen with text, this is your bootloader.
Please post the first five lines.
Sent from my One XL using Tapatalk

timmaaa said:
You should have no problems getting LTE on the device. You can have KitKat but it will be via an aosp ROM, not Sense. Sense ROMs for our device only go up to Android 4.2.2 and that's probably where they'll stay.
If you want to run a custom ROM on it just head over to htcdev and unlock the bootloader, then you can install a custom recovery, and from there you can install a custom ROM. I have detailed instructions for many of these operations in my How-To Guide For Beginners thread in my signature. You should also read the Evita FAQ thread in my signature, and bookmark the resource thread.
What are the bootloader details on the device? To boot into the bootloader there are two methods.
With phone powered on
Hold the volume down button, then hold the power button (so you're holding both buttons together), the button lights will start to flash, they will stop flashing and the screen will go blank, after a couple of seconds let go of the power button but continue to hold the volume down button until you reach the white screen with text, this is your bootloader.
With phone powered off
Hold the volume down button, then hold the power button (so you're holding both buttons together), after a couple of seconds let go of the power button but continue to hold the volume down button until you reach the white screen with text, this is your bootloader.
Please post the first five lines.
Sent from my One XL using Tapatalk
Click to expand...
Click to collapse
Thanks! My dad can live without KitKat. Here's the bootloader details:
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT-1.09.0000
RADIO-0.16a.32.09.17_2
OpenDSP-v25.1.0.32.0405
eMMC-boot
Apr 2 2012,21:08:24
EVITA

Jaguarandine said:
Thanks! My dad can live without KitKat. Here's the bootloader details:
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT-1.09.0000
RADIO-0.16a.32.09.17_2
OpenDSP-v25.1.0.32.0405
eMMC-boot
Apr 2 2012,21:08:24
EVITA
Click to expand...
Click to collapse
Well you got really lucky and bought a device that's been modified in the past. It already has s-off and SuperCID (11111111). That's half the work done for you. What does it say above those lines though? It should say locked/unlocked/relocked and possibly also tampered.
Your firmware is a bit outdated so you'll need to update that, which will be easy because you already have s-off on the device. Before we go any further I need the other lines from the bootloader though.
Sent from my One XL using Tapatalk

timmaaa said:
Well you got really lucky and bought a device that's been modified in the past. It already has s-off and SuperCID (11111111). That's half the work done for you. What does it say above those lines though? It should say locked/unlocked/relocked and possibly also tampered.
Your firmware is a bit outdated so you'll need to update that, which will be easy because you already have s-off on the device. Before we go any further I need the other lines from the bootloader though.
Sent from my One XL using Tapatalk
Click to expand...
Click to collapse
I'm at work now, and left the phone at home. I believe it said unlocked. I'll be able to work on this some more in a few hours. Thanks for all your help so far.

No problems. I'm subscribed to this thread so just pop in later and we'll sort you out. If it does say unlocked that leaves very little actual work for you to do, it's pretty much all been done. One thing you will need to do though is to install adb & fastboot on your PC, if you Google "minimal adb & fastboot" the first result will be an XDA thread which details how to do it, that's the easiest way. Another thing you'll need to do is install HTC drivers on the PC, the best way to do this is to install HTC Sync Manager and then connect your phone (first while booted into the OS, and secondly while in bootloader mode), this should install the drivers automatically. Once you've done that you test it by doing the following:
Navigate to the folder where adb.exe and fastboot.exe are located on your PC, shift + right click, select open command prompt here, then issue these commands:
Code:
adb devices
(While booted into Android)
Code:
fastboot devices
(While in bootloader mode, with "fastboot usb" showing on the phone screen)
Each command should return the serial number of your device. While you're issuing the adb command make sure your screen is on and unlocked because you may see a prompt asking to grant access which you need to confirm.
Before doing this you will also need to navigate to /settings/developer options on the device and enable usb debugging. If developer options doesn't appear in your settings you just need to navigate to /settings/about phone, then find the "build number" category and tap it about eight or so times, this unlocks developer options.
Sent from my One XL using Tapatalk

timmaaa said:
No problems. I'm subscribed to this thread so just pop in later and we'll sort you out. If it does say unlocked that leaves very little actual work for you to do, it's pretty much all been done. One thing you will need to do though is to install adb & fastboot on your PC, if you Google "minimal adb & fastboot" the first result will be an XDA thread which details how to do it, that's the easiest way. Another thing you'll need to do is install HTC drivers on the PC, the best way to do this is to install HTC Sync Manager and then connect your phone (first while booted into the OS, and secondly while in bootloader mode), this should install the drivers automatically. Once you've done that you test it by doing the following:
Navigate to the folder where adb.exe and fastboot.exe are located on your PC, shift + right click, select open command prompt here, then issue these commands:
Code:
adb devices
(While booted into Android)
Code:
fastboot devices
(While in bootloader mode, with "fastboot usb" showing on the phone screen)
Each command should return the serial number of your device. While you're issuing the adb command make sure your screen is on and unlocked because you may see a prompt asking to grant access which you need to confirm.
Before doing this you will also need to navigate to /settings/developer options on the device and enable usb debugging. If developer options doesn't appear in your settings you just need to navigate to /settings/about phone, then find the "build number" category and tap it about eight or so times, this unlocks developer options.
Sent from my One XL using Tapatalk
Click to expand...
Click to collapse
So it looks like my Dad bought a used phone, right? With everything that's been done, I'm not sure if that's a bad thing or not. Since my Dad wouldn't be happy, I do think I'll keep this little detail between us though
4.2.2 + Sense is better, right? I wouldn't want to shoehorn KitKat on here if there are some features missing and the performance is not as good.
Btw out of curiosity, do these programs have a Linux equivalent? If not, it's cool, I have a Windows machine at home too.

Jaguarandine said:
So it looks like my Dad bought a used phone, right? With everything that's been done, I'm not sure if that's a bad thing or not. Since my Dad wouldn't be happy, I do think I'll keep this little detail between us though
4.2.2 + Sense is better, right? I wouldn't want to shoehorn KitKat on here if there are some features missing and the performance is not as good.
Btw out of curiosity, do these programs have a Linux equivalent? If not, it's cool, I have a Windows machine at home too.
Click to expand...
Click to collapse
Oh yeah, the phone is without a doubt pre-owned. Whether Sense or aosp is better is a matter of taste, and your dad won't really know which one is best for him unless he's able to play with each of them for a few days to get the feel of them both.
I had forgotten you mentioned having Linux as your main OS at home, and yes adb & fastboot are Linux compatible, they're actually much easier to install because they don't require drivers on Linux. Just Google how to install them on Linux, you should get a bunch of results with clear directions.
Sent from my One XL using Tapatalk

Well, I was wrong. The top line says *** LOCKED ***. Looking for the other programs now.
Edit: Took me a while, but I was able to find and get the drivers working in Ubuntu successfully
Code:
[email protected]:~$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT288W303498 device
After going into bootloader, and entering fastboot mode, I get the following:
Code:
[email protected]:~$ sudo fastboot devices
HT288W303498 fastboot

Ok, that's good. Your bootloader is actually in a relocked state but the previous owner has spoofed it to say locked, that's my guess anyway. Either way, your next step is to head over to htcdev and dole the directions there to unlock your bootloader. You can skip the installing fastboot part obviously.
Sent from my Evita

Ok, bootloader now says unlocked.

Jaguarandine said:
Ok, bootloader now says unlocked.
Click to expand...
Click to collapse
Cool. Now is the point where you need to upgrade the firmware on the device. This is pretty straight forward command line stuff using fastboot.
Download the firmware from here:
http://www.androidfilehost.com/?fid=23060877490004040
Place it in your fastboot folder (the folder where you have fastboot located on your PC). Rename it to "215firmware.zip" to make things easier later on. Open a command prompt from within that folder, or just open a command prompt and use the CD command to change directory to that fastboot directory. Connect your phone in fastboot mode and issue this command to make sure your connection is good:
Code:
fastboot devices
Once you've established a working connection (it'll show your serial number) you can start the process with this command:
Code:
fastboot oem rebootRUU
The phone will not boot into rebootRUU mode which is a black screen with the HTC logo. Now issue this command:
Code:
fastboot flash zip 215firmware.zip
If the output ends with "FAILED (remote: 90 hboot pre-update! please flush image again immediately)", run the previous command again. If it ends with "INFO..... OK", just reboot to the bootloader with this command:
Code:
fastboot reboot-bootloader
Verify everything was successful by looking at the hboot version and radio version in the bootloader screen. They should be as follows:
Hboot: 2.15
Radio: 1.31a.32.45.16_2
Now just reboot your phone by issuing this command:
Code:
fastboot reboot
Sent from my Evita

timmaaa said:
Cool. Now is the point where you need to upgrade the firmware on the device. This is pretty straight forward command line stuff using fastboot.
Download the firmware from here:
http://www.androidfilehost.com/?fid=23060877490004040
Place it in your fastboot folder (the folder where you have fastboot located on your PC). Rename it to "215firmware.zip" to make things easier later on. Open a command prompt from within that folder, or just open a command prompt and use the CD command to change directory to that fastboot directory. Connect your phone in fastboot mode and issue this command to make sure your connection is good:
Code:
fastboot devices
Once you've established a working connection (it'll show your serial number) you can start the process with this command:
Code:
fastboot oem rebootRUU
The phone will not boot into rebootRUU mode which is a black screen with the HTC logo. Now issue this command:
Code:
fastboot flash zip 215firmware.zip
If the output ends with "FAILED (remote: 90 hboot pre-update! please flush image again immediately)", run the previous command again. If it ends with "INFO..... OK", just reboot to the bootloader with this command:
Code:
fastboot reboot-bootloader
Verify everything was successful by looking at the hboot version and radio version in the bootloader screen. They should be as follows:
Hboot: 2.15
Radio: 1.31a.32.45.16_2
Now just reboot your phone by issuing this command:
Code:
fastboot reboot
Sent from my Evita
Click to expand...
Click to collapse
Very detailed instructions, thanks! everything Seems to be working well and Hboot and Radio have been updated.

Jaguarandine said:
Very detailed instructions, thanks! everything Seems to be working well and Hboot and Radio have been updated.
Click to expand...
Click to collapse
You're doing well, all that's left to do now is to flash TWRP recovery and install a ROM. You'll need to decide what kind of ROM you're going to flash because currently Sense ROMs and KitKat aosp ROMs need different recoveries.
For any Sense ROM you can use this recovery:
http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.6.3.0-evita.img
For any KitKat aosp ROM you need to ue this recovery:
http://www.androidfilehost.com/?fid=23252070760973615
Once you've installed the recovery you will need to make a backup of your current system just in case anything goes wrong in future, or if you want to use it again. Check the How-To Guide For Beginners thread in my signature for detailed instructions on how to do that.
Once you've done that you can go ahead and find a ROM you want to install and flash it. Our two develpment sections are as follows:
Android Development
(for Sense ROMs)
Original Android Development
(for aosp ROMs)
Once you've picked one you can download it and head back to my guide thread for full instructions on how to flash it.

@timmaaa your awesome dude, keep up the great help you offer :thumbup:
Sent from my One using Xparent Red Tapatalk 2

I started noticing this strange flickering on the sides of the screen. The screen is fine on a white background or when the brightness is turned down. But as soon as color is introduced on a white background, the flickering starts. Is this normal? And will it go away?

Jaguarandine said:
I started noticing this strange flickering on the sides of the screen. The screen is fine on a white background or when the brightness is turned down. But as soon as color is introduced on a white background, the flickering starts. Is this normal? And will it go away?
Click to expand...
Click to collapse
Was this happening before the firmware flash? Is it happening since the firmware flash?
---------- Post added at 04:00 AM ---------- Previous post was at 04:00 AM ----------
rc420head said:
@timmaaa your awesome dude, keep up the great help you offer :thumbup:
Sent from my One using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
Thanks buddy, appreciate it.

Well, I've never noticed it before. I am however, using the phone a lot more regularly since I started updating it. I looked around, and it seems to be an issue a number of people have with the screen. I'll deal with it for now and see if gets any better. Brightness levels won't be too high most of the time anyway.
I think I'll choose Sense 5 and start installing the recovery.

It could simply be a mismatch between the firmware and whatever software version is currently installed on it. Or it could be a hardware defect. You could try running an RUU to rule that out, but that would require a Windows machine with adb/fastboot plus drivers.
Sent from my Evita

Now it's gone away. I dunno. The phone otherwise seems fine. I'll keep observing and if anything happens, I'll report back here.
Recovery installation went well. Now on to flashing the ROM.
Out of curiosity, which ROM do you have on your phone?
One thing I did notice is that some ROMS recommend Jellybean should be installed. Is that an issue for this phone?

[Q] automatic and continuous reboot

First off: I have an AT&T HTC one X
I am an almost total noob when it comes to this stuff so please bear with me here.
I had my roommate put cyanogenmod onto my phone when I got it and all was well until I moved to Asia and got an unlock code from AT&T to be able to use it over here. The unlock code wouldn't work and I found some stuff online saying that it might be a problem with cyanogenmod.
I followed a youtube instruction guide on how to get rid of the mod and everything was going fine until right at the end when I got a windows notification that the RUU had stopped working. I figured I would just do it again, but the actual program itself said it was successful. As I waited for it to reboot and load the roms, it started a loop. The loop is the white screen with the green htc letters for a few seconds and then it goes to a black screen with a phone logo in the middle. Around the phone logo is what looks like a recycling symbol except circular instead of triangular and on the screen portion of the phone logo there is an arrow facing down.
I assume this is just telling me I need to actually download some software on the phone, but it won't connect via USB and every time it starts up it says that the drivers were not successfully installed and htc sync manager doesn't recognize that a device is even connected. The loop continued and i tried to boot it back into the fastloader which did nothing. I held down the buttons as if to boot it into fastloader, but this time for about 15 seconds which took me to a battery charging screen and finally ended the loop.
I assume(hope) that since it's actually responding to input from the buttons that it's not irreversibly bricked. Is there any way I can get some version of android back on this thing? Any help would be much appreciated

Are you able to get the phone into the bootloader?
To boot into the bootloader there are two methods.
With phone powered on
Hold the volume down button, then hold the power button (so you're holding both buttons together), the button lights will start to flash, they will stop flashing and the screen will go blank, after a couple of seconds let go of the power button but continue to hold the volume down button until you reach the white screen with text, this is your bootloader.
With phone powered off
Hold the volume down button, then hold the power button (so you're holding both buttons together), after a couple of seconds let go of the power button but continue to hold the volume down button until you reach the white screen with text, this is your bootloader.
Please post the first five lines. Also, exactly which RUU did you try to use?
Sent from my Evita

Happened to me as well..I reran ruu and then flashed a custom recovery. That symbol of charging with that arrow scared me. Lol

Yeah I was the friend that helped tpank unlock and put cyanogenmod on. I'm just too noob to help him halfway across the world get his phone back to stock

Swilli89 said:
Yeah I was the friend that helped tpank unlock and put cyanogenmod on. I'm just too noob to help him halfway across the world get his phone back to stock
Click to expand...
Click to collapse
This is why people should be learning to do things themselves. Now you've put him in a situation where he doesn't know what he's doing, very dangerous on a modified device with root access.
Sent from my Evita

the RUU i tried was the update from the htc site "HTC One X for AT&T Software Upgrade 1.29.2014"
the first five lines that appear on the phone are
*** RELOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-2.18.0000
RADIO-1.35A.32.45.27
OpenDSP-v33.1.0.45.1128
also my computer doesn't recognize my phone is even plugged in at this point

Before you attempt to run the RUU again it's very important that we find out what your current CID is, if it's still SuperCID and you run the RUU you could brick your phone. To do this you're gonna need to have a working connection between your phone and your PC, so you'll need to make sure you have drivers installed, and you'll also need to have adb/fastboot installed. Do you have any drivers currently installed? If so, how did you install them?
Sent from my Evita

i have the RUU that I showed you and I just installed another RUU on my computer: RUU_M7_UL_JB43_SENSE50_MR_CINGULAR_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed.2.exe but I haven't done anything with that yet. The only drivers I would have on my phone might be the ones from the original RUU I downloaded and ran which got me into this mess in the first palce, but I dont even know if they're on the phone since it's in its current state. I have adb and fastboot from downloading the android sdk slim pack. I also have HTC sync, but I'm not sure how that fits into the equation

tpankfashank said:
i have the RUU that I showed you and I just installed another RUU on my computer: RUU_M7_UL_JB43_SENSE50_MR_CINGULAR_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed.2.exe but I haven't done anything with that yet. The only drivers I would have on my phone might be the ones from the original RUU I downloaded and ran which got me into this mess in the first palce, but I dont even know if they're on the phone since it's in its current state. I have adb and fastboot from downloading the android sdk slim pack. I also have HTC sync, but I'm not sure how that fits into the equation
Click to expand...
Click to collapse
Whoa. Whoa, whoa, whoa. Where on earth did you get that RUU? It isn't even for this device. Delete it now.
Drivers don't go on your phone, they're on your PC. HTC Sync Manager fits into the equation because it's the best way to get the drivers installed on your PC.
Uninstall HTC Sync Manager and the drivers that should be in the same sub-menu in the start bar on your PC. Uninstall any other phone software you might have on your PC.
Install HTC Sync Manager again, put your phone in fastboot mode, connect your phone to your PC, drivers should begin to auto-install.
Navigate to where you have adb.exe and fastboot.exe on your PC (we'll call this your fastboot folder). Shift + right click anywhere within that folder, select open command prompt here, issue the following command:
Code:
fastboot oem readcid
Please post the result.
Before we go any further, I need to be brutally honest with you. Once you have successfully run the correct RUU, which will return the phone to a stock configuration, leave it stock. Judging from your couple of posts here you're on a collision course to bricking your phone. You just don't seen to posses the slightest idea of what you're doing, couple that with owning a modified device, and the results are almost always disastrous. I'm not saying this to be cruel, I'm saying this because I'd hate to see you brick your device. The only way it's safe to have a modified device is if you're willing to put in the hard work of researching (days/weeks/months/years), and continuing to research to stay on top of this ever changing game.
Sent from my Evita

ok i attempted all of this, but nothing happens because my computer won't even recognize that my phone is plugged in. So htc sync manager is telling me to connect a device and the command prompt just says <waiting for device> when I type in the command to figure out the CID.
Also, I take no offense from your warning. I wasn't going to try to mess with it any more after I got my the stock OS and my phone unlocked for asian networks. I really appreciate all the help

tpankfashank said:
ok i attempted all of this, but nothing happens because my computer won't even recognize that my phone is plugged in. So htc sync manager is telling me to connect a device and the command prompt just says when I type in the command to figure out the CID.
Also, I take no offense from your warning. I wasn't going to try to mess with it any more after I got my the stock OS and my phone unlocked for asian networks. I really appreciate all the help
Click to expand...
Click to collapse
There's no point in attempting any fastboot command until you can get the PC to recognise the device. Are you using a usb 2.0 port, and the original HTC usb cable? What does it say on the screen of your phone when you connect it while it's in the bootloader? It should say fastboot, fastboot usb, or fastboot ac.
Sent from my Evita

timmaaa said:
There's no point in attempting any fastboot command until you can get the PC to recognise the device. Are you using a usb 2.0 port, and the original HTC usb cable? What does it say on the screen of your phone when you connect it while it's in the bootloader? It should say fastboot, fastboot usb, or fastboot ac.
Sent from my Evita
Click to expand...
Click to collapse
Tpank, use the snipping tool on your computer to post a screen capture of your fastboot adb folder. its the folder that you are running the command prompt from (or should be).
BTW thanks Timaaaaa for helping my friend out. When I unlocked his phone we didn't know he would have the opportunity to move out of the US to Thailand so I figured I would be around to help with something like this. Thanks again.

Why would we need a screenshot of the fastboot folder?
Sent from my Evita

These guys are on a collision course. ?

timmaaa said:
There's no point in attempting any fastboot command until you can get the PC to recognise the device. Are you using a usb 2.0 port, and the original HTC usb cable? What does it say on the screen of your phone when you connect it while it's in the bootloader? It should say fastboot, fastboot usb, or fastboot ac.
Sent from my Evita
Click to expand...
Click to collapse
ok so it says "Fastboot usb". I am using the original htc usb cable. I'm not sure if it's a usd 2.0 port all I know is that it's an Intel 6 Series/C200 Series.
When I ran the command prompt it says:
<bootloader> cid: 11111111
OKAY [ 0.017s]

Ok, so you have a working fastboot connection now, right? The problem you face at the moment is that you can't run an RUU with your phone in the current configuration. S-on + SuperCID + jb RUU = brick. Your only real option at this stage is to do this:
-Unlock the bootloader at htcdev.
-Flash TWRP recovery.
-Flash a ROM to get the phone booting.
-Get s-off via Facepalm S-off.
-Run the correct at&t RUU to return the device to stock
-Change the CID back to the at&t CID.
-Relock the bootloader.
-Go back to s-on.
That probably seems like a lot of work but it's the only way for you to proceed. I have detailed instructions for several of those procedures in the How-To Guide For Beginners thread in my signature.
Sent from my Evita

So I can;t get past the first step because it's not recognizing my phone still. When I ran the first command in the command prompt, where it should have listed my phone it says "List of connected devices" and nothing underneath it.

How did you get the CID?
Sent from my Evita

I'm not sure why I can find the CID and not get it listed as an attached device. I tried to run the adb devices command a few times and then ran the fastboot oem readcid command in the same window and I could get the cid but still cant get it to recognize the device

Are you attempting adb commands while the device is in fastboot mode? They won't work, only fastboot commands will work there, adb commands work while the phone is booted into the OS. Use "fastboot devices" while in fastboot mode.
Sent from my Evita