Database Info

Magic bricked

Test methods need to unbrick my magic, so far I've tried one that I have not worked. If someone want to try things that I communicate them and I try.
After an upgrade of radio has been fried. I can not get into recovery, or fastboot. Even so I try to send commands and the command window stays and even restart <waiting for device> clicking to enter recovery fastboot or does nothing.
Excuse the translation but my English is very bad and I use the google translator

edugg said:
Test methods need to unbrick my magic, so far I've tried one that I have not worked. If someone want to try things that I communicate them and I try.
Click to expand...
Click to collapse
wow so much information don't know where to start!!!

hard to say..someone managed to the the phone to respond to fastboot/adb by starting up ADB..
wait for the waiting for device msg, then connect the phone to usb and turn it on.
if all method fails, bring it back to claim for warranty.

edugg said:
Test methods need to unbrick my magic, so far I've tried one that I have not worked. If someone want to try things that I communicate them and I try.
After an upgrade of radio has been fried. I can not get into recovery, or fastboot. Even so I try to send commands and the command window stays and even restart <waiting for device> clicking to enter recovery fastboot or does nothing.
Excuse the translation but my English is very bad and I use the google translator
Click to expand...
Click to collapse
What OS are you using on your computer?

zeroplace said:
What OS are you using on your computer?
Click to expand...
Click to collapse
I tested with Windows 7, Vista and XP and the same.

You know any way to flash as factory?

Will it actually turn on or does it just flash a red led when you press power?

bonesy said:
Will it actually turn on or does it just flash a red led when you press power?
Click to expand...
Click to collapse
Starts, appears the splash but only gets to that point

In that case it isnt bricked its just stuck...Bricked is when it wont turn on at all
Do you have a nandroid backup?
Have you taken the battery out and the power lead so it has no power?
i have had this problem
If you have a backup get it ready, Once you have let the phone power down totally (battery out and no lead) hold back and press power (keep holding back) this should get you into fastboot.if it doesnt unplug the lead and try again.
If thats successful.... using your nandroid files
FASTBOOT COMMANDS
fastboot erase system -w
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot flash recovery recovery.img
Sorry if you cant get this to work i have to go out and wont be back to check till tomorrow so just giving you all the info

bonesy said:
In that case it isnt bricked its just stuck...Bricked is when it wont turn on at all
Do you have a nandroid backup?
Have you taken the battery out and the power lead so it has no power?
i have had this problem
If you have a backup get it ready, Once you have let the phone power down totally (battery out and no lead) hold back and press power (keep holding back) this should get you into fastboot.if it doesnt unplug the lead and try again.
If thats successful.... using your nandroid files
FASTBOOT COMMANDS
fastboot erase system -w
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot flash recovery recovery.img
Sorry if you cant get this to work i have to go out and wont be back to check till tomorrow so just giving you all the info
Click to expand...
Click to collapse
I have tried many times to do this and nothing ever stays <waiting for device> and does nothing

Phone is not bricked, so this shouldnt be a problem.
If you cant get into fastboot with current setups, then use another recovery image and a custom rom.
(all that stuff is on SD-card.. its not that hard)
Update SDK.

daihiep said:
Phone is not bricked, so this shouldnt be a problem.
If you cant get into fastboot with current setups, then use another recovery image and a custom rom.
(all that stuff is on SD-card.. its not that hard)
Update SDK.
Click to expand...
Click to collapse
Great! And how should the recovery image and custom rom be put into the Magic? Sledgehammer?
The problem that almost everyone seems to not understand is that it's impossible to access fastboot, adb or any other (known) means.
The magic will hang at the first splashscreen no matter which buttons are pushed during power up. If the track ball is pressed during power on, the led lights up blue (still hanging at first splash). All other combos of buttons during power on makes no difference at all.
I have tried keeping fastboot waiting while power cycling the device (as explained in another thread), but there are no reaction. I have tried in xp, vista and linux.
I have also tried with a gold card, but since the phone seems unable to get any further than the first splash, this will not work.
So unless someone has a _NEW_ method to actually enter fastboot/ADB mode, these devices are BRICKED!
People have been discussing what the criteria for calling a phone a brick, but as far as I have care my Magic can only function as a paper weight and can therefore be called bricked.

Help
I have the same problem , the fastboot can not acces, i stay at the vodafone logo.
Any ideas?
HHHHHHHHHHHEEEEEEEEEEEELLLLLLLLLLPPPPPPPPPP.

frankiboy1 said:
Great! And how should the recovery image and custom rom be put into the Magic? Sledgehammer?
Click to expand...
Click to collapse
take out the sd card, put it in a usb adaptor and copy them over.
Also search for a thread "how i unbricked my phone"

frankiboy1 said:
Great! And how should the recovery image and custom rom be put into the Magic? Sledgehammer?
The problem that almost everyone seems to not understand is that it's impossible to access fastboot, adb or any other (known) means.
Click to expand...
Click to collapse
Think before answering.
Btw, question answered by htcmagic.

daihiep said:
Think before answering.
Btw, question answered by htcmagic.
Click to expand...
Click to collapse
I repeat: The problem that almost everyone seems to not understand is that it's impossible to access fastboot, adb or any other (known) means.
Having a recovery image and a custom rom on the SD card is useless if you are not able to get the phone accessing those files.
I have tried the "how I unbricked my phone" method (like I wrote in my first post) without any success. If you read the whole "how I unbricked my phone" thread you can see that there are several guys that did not have success with this method.
I have done a lot of thinking.... and searching...
Thanks

http://forum.xda-developers.com/showthread.php?t=571457 try there

Wrong HBOOT = real brick
Guys,
With a wrong HBOOT (what happend to me), the phone is a real brick...
And they refused to repair it... I bought a new phone. But I keep the old one in case someone break his screen. Then I can get the mobo.

just curious.
superkikim said:
Guys,
With a wrong HBOOT (what happend to me), the phone is a real brick...
And they refused to repair it... I bought a new phone. But I keep the old one in case someone break his screen. Then I can get the mobo.
Click to expand...
Click to collapse
How did you brick it?
Btw, have you tried to run any RUU update?
At least singapore one.

Flashed CM6 RC2, can't boot into recovery PLZ HELP!!!

Okay I just recently Flashed CM6 Rc2, Everything was working fine. Then I noticed the Market started FC every time I tried to load it. I can't get it to open at all anymore. So I figured I would wipe and reflash, but I when I reboot and hold down HOME AND POWER it just stays stuck on the TMobile G1 Splash screen. But if I pull the battery out and put it back in, I can start up the phone again. Everything else works pretty good besides random things at times. Every now and then it will randomly restart. Also, I tried to factory wipe through the settings, and it just rebooted and then stuck on the G1 screen again.
Can anyone PLEASE help??

Try ADB? Or through the terminal? CMD, lol. I had the same problem with market, so i got tired of it. And flashed Cannon Complete Eclair, It works better than Froyo, and they aren't that much different.

Try using fastboot in the bootloader. That happened to me a couple of times with the Clockwork rom manager and going between roms.
1) Download another copy of the recovery img
2) Rename it something simple like recovery.img
3) boot into the bootloader (Camera + Power)
4) open a command prompt navigate to the directory that you have the image in
5) run this command without the quotes "fastboot flash recovery recovery.img" (if you didn't name it recovery.img then substitute the name you chose)
Hopefully that works for you.
**If you don't have the sdk tools files (adb.exe..., fastboot.exe) copied into your /system32 folder like I do then you will need to put the new copy of your recovery.img into the sdk tools folder and navigate there in the command prompt, coping them into the /system32 folder lets use them regardless of the directory that you are workin.

I had a similar problem like this a few days ago where I couldn't load up my recovery so I used the method similar to the post above me. After searching for just trying stuff I was able to learn how to use adb on my own (where was ya post when i needed it roadmasta01 lol)
But I think I did almost he same steps he took except I loaded into fastboot by holding the back button and the power button and I erased the old recovery before flashing the recovery again.(fastboot recovery erase)

I too used a similar process Roadmasta01 and biglo used. I had a buddy that had the exact same problem today. His G1 was progressively getting worse ... pretty soon everything would FC and he couldnt get it to the boot loader and then it just wouldnt boot past teh G1 logo.
Booted the G1 into fastboot
downloaded the latest clockwork recovery image from koush's site and saved it to the folder location adb and fastboot are located in the sdk.
fastboot erase recovery
fastboot flash recovery <recovery you downloaded.img>
rebooted and al was well again.

biglo said:
I had a similar problem like this a few days ago where I couldn't load up my recovery so I used the method similar to the post above me. After searching for just trying stuff I was able to learn how to use adb on my own (where was ya post when i needed it roadmasta01 lol)
But I think I did almost he same steps he took except I loaded into fastboot by holding the back button and the power button and I erased the old recovery before flashing the recovery again.(fastboot recovery erase)
Click to expand...
Click to collapse
Sorry homie, just happened to see this thread. Besides I still consider myself a novice at this stuff, I am usually able to pull my butt out of the fire; Except for when I took my phone completely apart to replace the housing and android.process.acore started to FCing whenever I tried to call somebody or received a call. That was frustrating as all get out, everything but the actual phone worked on my phone. On top of that I tore the ribbon for the digitizer when I replaced my housing so when I tried wiping and flashing a different ROM to try to fix it, I could do the whole "touch the android to start" thing. I eventually fixed the FC issue by flashing the dreaimg.nbh file and just starting over from scratch. ezterry helped me with that issue and he was very patient. I realize you didn't ask and you were joking, but I starting into a background ramble and I had to finish it.

Roadmasta01 said:
Sorry homie, just happened to see this thread. Besides I still consider myself a novice at this stuff, I am usually able to pull my butt out of the fire; Except for when I took my phone completely apart to replace the housing and android.process.acore started to FCing whenever I tried to call somebody or received a call. That was frustrating as all get out, everything but the actual phone worked on my phone. On top of that I tore the ribbon for the digitizer when I replaced my housing so when I tried wiping and flashing a different ROM to try to fix it, I could do the whole "touch the android to start" thing. I eventually fixed the FC issue by flashing the dreaimg.nbh file and just starting over from scratch. ezterry helped me with that issue and he was very patient. I realize you didn't ask and you were joking, but I starting into a background ramble and I had to finish it.
Click to expand...
Click to collapse
Its kool man its always good to hear about users with different experiences on things they try in case we run into that same problem. I'm juust like you I try to figure things out myself before I resort to posting on how to because I know most answers are already out there.

Guys, thanks to this thread, I was able to bring my G1 back from the brink. This morning it reset itself and froze at the G1 screen no matter what I did. Pulling the battery and rebooting... nothing. Plugging it to a charger when starting...nothing. I thought it was done for since I couldn't access the recovery section.
Something mine was doing that I didn't see mentioned above is that if I went into the HBOOT/Fastboot screen (camera/power held to startup), it would freeze at that screen after just a couple of seconds. Once I got adb up and running, it wouldn't even find the phone at first. After playing with it for a few minutes, I noticed that I had, literally, about 3 seconds of time that it would register seeing the G1 at the fastboot terminal screen. I took a chance and set up the command line to reflash the recovery, rebooted to flashboot, and plugged in the USB. As soon as the screen showed that it saw my phone, I hit enter. Luckily, it transferred the new recovery .img in time and I was able to bring it back to life. DAMN...
Anyway, thanks again to you fellas!

reese.leblanc said:
Guys, thanks to this thread, I was able to bring my G1 back from the brink. This morning it reset itself and froze at the G1 screen no matter what I did. Pulling the battery and rebooting... nothing. Plugging it to a charger when starting...nothing. I thought it was done for since I couldn't access the recovery section.
Something mine was doing that I didn't see mentioned above is that if I went into the HBOOT/Fastboot screen (camera/power held to startup), it would freeze at that screen after just a couple of seconds. Once I got adb up and running, it wouldn't even find the phone at first. After playing with it for a few minutes, I noticed that I had, literally, about 3 seconds of time that it would register seeing the G1 at the fastboot terminal screen. I took a chance and set up the command line to reflash the recovery, rebooted to flashboot, and plugged in the USB. As soon as the screen showed that it saw my phone, I hit enter. Luckily, it transferred the new recovery .img in time and I was able to bring it back to life. DAMN...
Anyway, thanks again to you fellas!
Click to expand...
Click to collapse
Good job thinking on your feet!!

i`m having kind of the same problem with my G1 it won't boot all of a sudden and when i try to enter recovery mode it freezez at " Build : " once after about 5-10 minutes it loaded the recovery menu but nothing was working it was extremely slow ... i tried the options above to erase and reflash the recovery.img but it just won't work it does the same thing ... anyone have a solution ? ...

reese.leblanc said:
Guys, thanks to this thread, I was able to bring my G1 back from the brink. This morning it reset itself and froze at the G1 screen no matter what I did. Pulling the battery and rebooting... nothing. Plugging it to a charger when starting...nothing. I thought it was done for since I couldn't access the recovery section.
Something mine was doing that I didn't see mentioned above is that if I went into the HBOOT/Fastboot screen (camera/power held to startup), it would freeze at that screen after just a couple of seconds. Once I got adb up and running, it wouldn't even find the phone at first. After playing with it for a few minutes, I noticed that I had, literally, about 3 seconds of time that it would register seeing the G1 at the fastboot terminal screen. I took a chance and set up the command line to reflash the recovery, rebooted to flashboot, and plugged in the USB. As soon as the screen showed that it saw my phone, I hit enter. Luckily, it transferred the new recovery .img in time and I was able to bring it back to life. DAMN...
Anyway, thanks again to you fellas!
Click to expand...
Click to collapse
Lol I'm glad my problem helped ya out. I actually ended up fixing it myself luckily enough. But thanks to all who posted responses
Sent from my HTC Vision using XDA

lg mytouch c800 bricked?

hi im pretty new here a friend of mine gave me her lg c800 mytouch to try and fix it for her.. not sure what she did she said she rooted the phone and the root was successful but i have a good idea that she doesnt know what she was doing..i will post a pic of the error screen im getting. but it says
E:Cant find misc
E:cant find misc
Finding update package...
E:unknown volume for path [sd:/download/adb_fastboot_and_other_tools.Zip]
E:Cant mount SDCARD:/download/adb_fastboot_and_other_tools.zip
Installation aborted
facory reset failed
restart factory reset..
now im far from a pro at this i know a lil more about computers and Ios devices..but ive rooted a few phones and to me it looks like she unzipped adb fastboot on her phone from her sd card??
ive tried holding F..A..vol down..and power..Nothing..
ive tried volume up .volume down and power still nothing..
BUT if i hold E..vol UP and power it brings me to a white screen that says S/W update
the big problem is the phone wont stay on long enough to do anything on the computer it stays on 3 sec. then reboots to same screen (computer says phone is unplugged) then phone just keeps restarting.
but the phone WILL stay on when i put it on the S/W update screen..but computer wont recognize the phone at all on that screen
ive tried the adb and fastboot commands but the phone wont stay recognized..it will recognize the phone and say thats its in recovery mode but when phone restarts it dont see phone no more..
well thanks ahead of time if anyone has any input or solution
and hopefully all this will make sense to someone lol
i think this pic will work.. if not ill try again

any ideas please?? or am i completely out of luck?

When you say:
delilah25 said:
it will recognize the phone and say thats its in recovery mode but when phone restarts it dont see phone no more..
Click to expand...
Click to collapse
...do you mean that you can successfully communicate with the phone over USB, but you only have 3 seconds? What way is the phone recognized? Is it visible to adb/fastboot?

post-mortem said:
When you say:
...do you mean that you can successfully communicate with the phone over USB, but you only have 3 seconds? What way is the phone recognized? Is it visible to adb/fastboot?
Click to expand...
Click to collapse
Yes In Adb device list it shows the phone and then says recovery..but after that I don't have enough time to type any other commands ..the phone is also recognized in "my computer" as removable device then when the phone restarts seconds later it says device unplugged ..and just keeps restarting on its own till I remove the battery...I just read on the forum in a post that Adb will recognize the phone if it's off but I remove the battery and put it back in and plug in USB and phone turns on and keeps restarting won't even let me turn it off!! I'm losing patience with this thing lol
But I don't get why the error mentions fastboot? Not my phone so if it's not fixable I don't really care but I'm just the stuborn type when it comes to fixing electronics ..again thanks ahead of time to anyone that helps cuz I'm completely lost on this one

Have you tried timing it to send a quick "adb reboot recovery"? If you can use fastboot, you can tell it to boot off a new, custom recovery img, without actually flashing it.

i have the same problem
post-mortem said:
Have you tried timing it to send a quick "adb reboot recovery"? If you can use fastboot, you can tell it to boot off a new, custom recovery img, without actually flashing it.
Click to expand...
Click to collapse
i used an app on the market to remove bloatware. i removed slacker and the app stated that after two reboots that everything would be fine and the app would be gone. after one reboot the phone has the same screen this gentlemans lady friend has. it looks like the app its looking for is no longer zip aligned properly. someone told me to rename a recovery image the error message to trick the bootloader into thinking the missing app is there. hes an app dev so i figured he knows whats what. ive tried everything the gentleman in this post said and more. hell i have two of these phones and rooted the other and made a backup of that phone and dragged the backup to an sd card and rebooted to see if any of the backed up system apks would trigger a successful reboot but to no avail. i have all the drivers i need and adb commands but nothing works because the phone doesnt stay connected to my pc long enough for anything. please reply with some knowledge. ive been scouring the web for at least a month. i was so happy when i came across this. i actually became a member just to post about this erroer (look up diabolus ae in the forum search field. my post is about 3 days old with a better pic of the screen message. i bought a galaxy s II but i want to give the lg to my son. please help or respond:cyclops:

diabolus ae said:
i used an app on the market to remove bloatware. i removed slacker and the app stated that after two reboots that everything would be fine and the app would be gone. after one reboot the phone has the same screen this gentlemans lady friend has. it looks like the app its looking for is no longer zip aligned properly. someone told me to rename a recovery image the error message to trick the bootloader into thinking the missing app is there. hes an app dev so i figured he knows whats what. ive tried everything the gentleman in this post said and more. hell i have two of these phones and rooted the other and made a backup of that phone and dragged the backup to an sd card and rebooted to see if any of the backed up system apks would trigger a successful reboot but to no avail. i have all the drivers i need and adb commands but nothing works because the phone doesnt stay connected to my pc long enough for anything. please reply with some knowledge. ive been scouring the web for at least a month. i was so happy when i came across this. i actually became a member just to post about this erroer (look up diabolus ae in the forum search field. my post is about 3 days old with a better pic of the screen message. i bought a galaxy s II but i want to give the lg to my son. please help or respond:cyclops:
Click to expand...
Click to collapse
Normally, if you want to flash a custom recovery through fastboot, people will tell you to run 2 commands:
fastboot flash recovery nameofimagefile.img
fastboot reboot recovery
Since you don't have time to execute those 2 commands, you can tell it to just boot from the .img file, without flashing over your current recovery. (This is actually proper form, as you can test if the .img file works properly without damaging your existing recovery.) The way you do that is to 1st copy a recovery .img file to the root of your SD card, then execute the following 1 command:
fastboot boot nameofimagefile.img
Since you only have ~3 seconds, type the command in, and wait for the right instant to hit enter on the keyboard. If the command is successfully sent to the phone, it will reboot into that .img.
See if that works for you. Good luck.

[Q] One S Brick? HELP!

Novice here.
Ran the All-in-One utility today and after the CWM installed I hit "Perm root" without reading the thing below telling me to boot to recovery first. It's now stuck in boot loop. Everything went off fine up until the Perm root. Even that said successful and then restarted. Only after the process was completed did the recovery loop begin. No HTC logo loop. Just reboots into CWM over and over no matter what technique I use (except for opening the case).
I've read this: http://forum.xda-developers.com/showthread.php?t=1599363
And am trying to install ADB to push ANY possible ROM over to the SD card. My recovery allows the toggle of /mount sdcard and /mount system, however adb fastboot push doesn't work. "error: device not found"
And I can't do this: http://forum.xda-developers.com/showthread.php?t=1644730 because my phone is stuck in the recovery loop. If I try volume down + power, it just comes back to recovery screen. I've tried factory reset, I've tried wiping cache, I've tried wiping Dalvik, and still nothing. I did flash the SuperSu.zip after I had used the Perm Root button on Haroon2000's app.
I'm incredibly flustered as I've rooted devices for years and this is my first problem. I've seen similar complaints all with ideas of breaking into the phone and unplugging it's battery so I can get to the bootloader etc, but I'm so very confused. So many posts telling me to do so many things.
Can someone please help break down a tangible solution here? I'm freaking out.
Cheers
EDIT: If someone can get my phone fixed, I'll Paypal them $50 USD. I really need my phone back ASAP :\

I don't know if this is your solution, but you did not mention it as one of your attempts.
Have you looked into running an RUU?
Sent from my HTC One S using xda premium

beats4x said:
I don't know if this is your solution, but you did not mention it as one of your attempts.
Have you looked into running an RUU?
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
I'll update this again once I try breaking the phone down and yanking the battery. But I have tried running the RUU. I can't get to the bootloader right now and it's not listing the device when I adb devices.
I'm going to go home from work since I've spent 7 hours on two machines (XP/7) trying to fix this PoS and redo everything from the ground up. Hopefully my anger will have overcome it.
Something I've noticed however, is that within the CWM recovery, I can use the All-in-one tool to reboot the phone. So it is reacting to ADB commands. Perhaps trying to use ADB fastboot (Right-click method) instead of full ADB installation could be a problem with trying to push a ROM zip. Also, as far as the RUU goes. I don't remember what happened there. I'll edit this when I get home.

nik.the said:
I'll update this again once I try breaking the phone down and yanking the battery. But I have tried running the RUU. I can't get to the bootloader right now and it's not listing the device when I adb devices.
I'm going to go home from work since I've spent 7 hours on two machines (XP/7) trying to fix this PoS and redo everything from the ground up. Hopefully my anger will have overcome it.
Something I've noticed however, is that within the CWM recovery, I can use the All-in-one tool to reboot the phone. So it is reacting to ADB commands. Perhaps trying to use ADB fastboot (Right-click method) instead of full ADB installation could be a problem with trying to push a ROM zip. Also, as far as the RUU goes. I don't remember what happened there. I'll edit this when I get home.
Click to expand...
Click to collapse
Okay, update.
I was able to get ADB working and detect my phone.
Next, I was able to push Venom Rom to phone. I factory reset, wiped cache, wiped Dalvik, and was able to install Venom.zip. It then asked to reboot (per Venom screen) and I said okay. It then returned to CWM Recovery. I was confused but left everything as is. I have now reset the phone by holding the power button for around 10 seconds. It then restarted to the HTC Quietly Brilliant screen. I have been looking at that screen for about 5 minutes.
Also pertinent: I did try to run the RUU, but it didn't connect through USB. (I forget what it said verbatim). So that didn't work. I also was able prior to this entire process get into the bootloader via dumb luck.
Any suggestions? I am staring at the HTC boot screen still. Do I try to restart and enter bootloader? If so, then what? It seems there is something wrong with CWM. Can I switch recoveries? Can I uninstall it?

Calm down we have all been there,
When you flashed venom did you flash the boot image? Also i use twrp instead of cwm i find twrp better .
To enter bootloader hold power button and down vol together .

As gazknight said, this seems like proper kernel not being flashed or having an issue. If you flashed the boot.img with fastboot, try again erasing cache from fastboot first. The commands are as follow:
fastboot erase cache
fastboot flash boot boot.img (where this boot.img is the one inside the zip from the rom you choose and must be left in the same folder than fastboot)
It happened to me a couple times when i was on hboot 1.14 that I had to flash the boot.img a second time sometimes, somehow it was not working the first time, randomly, even though the flash had completed ok on fastboot.
If still doesn't work try doing a factory reset from TWRP and flashing ViperOneS again.
If that still doesn't work, you might want to try another rom, like TrickDroid, you would then have to flash the boot.img from this other room with fastboot, remember that.
Try and let us know

Hold down volume down while you're trying to boot, that will get you in boot loader, go to fast boot by pressing the power key, connect your phone to your computer, run the flash viper boot img thingy and you're set!
Envoyé depuis mon HTC One S avec Tapatalk

Same issue with HTC One S bricked but in European version, Stock ROM
hello,
I did't want to start a new topic, as I'm experiencing a similar issue with my HOS. Briefly, yesterday morning I plug the phone from charger at 06.00 am. Play with it for a while and then go to work. Used it at work for a few phone calls until 10.00 am (so 4 hours on fully charge battery). Then at 10.00 am I went into a meeting and left the phone out of my sight for 20-30 minutes. When I came back from the meeting I realize that the phone was closed. I try to open it (power button) but nothing. Press power for 10-30 seconds with volume down - still no effect.
Then I took the charger (the original one that I always use to cherge it) and plug it, left it for 2-3 minutes and press power. The phone starts but all I have is the white screen with HTC logo and if I press the power button + volume down the phone goes into bootloader. That's all I can do with it for now.
I have stock rom, bootloader is locked and I never try to root the phone. Is it any chance to repair it by myself or I have to sent it to the repair shop.
many thanks in advance.

Alright so I feel like I'm getting closer.
Here's whats happening now. It's in the HTC boot screen loop. I can get it into bootloader whenever I want, but now it's not detecting /sdcard in recovery. Within the bootloader, fastboot won't detect my device and my computer (Windows 8) claims the device is malfunctioning. I can still use fastboot adb commands from my computer when it is in recovery. I have gone into bootloader and cleared storage, as well as factory reset after. Also, it used to reboot into recovery endlessly. Now it appears that isn't hte case and reboots from recovery into the OS, but will not work.
I'm going to try and flash using adb w/o sdcard the boot.img as suggested above. I'll keep updating so others can know the process if they soft-brick their phone (I'm assuming this is a soft brick because I can still run things etc).
Update: trying to do fastboot erase cache from within recovery gives me "Waiting for device". As I've said, for some reason, it says the device is malfunctioning/not detected when I'm in the 1.14 Hboot Bootloader. But again, I can issue adb devices from within recovery. Sdcard still not mounting.
Edit: I'm issuing adb commands through adbfastboot files. Do I need to have the Android SDK fully installed with the Manager thing, or does the basic adbfastboot work (From here: http://www.htconeforum.com/forum/ht...e-your-htc-one-s-back-100-stock-relocked.html). That adb fastboot has the following files: adb, fastboot, adbwinapi.dll, adbwinusbapi.dll.
I think the source of the current problem is that I can no longer access my /sdcard or mount it. One step forward, then two steps back -_-.

nik.the said:
Alright so I feel like I'm getting closer.
Here's whats happening now. It's in the HTC boot screen loop. I can get it into bootloader whenever I want, but now it's not detecting /sdcard in recovery. Within the bootloader, fastboot won't detect my device and my computer (Windows 8) claims the device is malfunctioning. I can still use fastboot adb commands from my computer when it is in recovery. I have gone into bootloader and cleared storage, as well as factory reset after. Also, it used to reboot into recovery endlessly. Now it appears that isn't hte case and reboots from recovery into the OS, but will not work.
I'm going to try and flash using adb w/o sdcard the boot.img as suggested above. I'll keep updating so others can know the process if they soft-brick their phone (I'm assuming this is a soft brick because I can still run things etc).
Update: trying to do fastboot erase cache from within recovery gives me "Waiting for device". As I've said, for some reason, it says the device is malfunctioning/not detected when I'm in the 1.14 Hboot Bootloader. But again, I can issue adb devices from within recovery. Sdcard still not mounting.
Edit: I'm issuing adb commands through adbfastboot files. Do I need to have the Android SDK fully installed with the Manager thing, or does the basic adbfastboot work (From here: http://www.htconeforum.com/forum/ht...e-your-htc-one-s-back-100-stock-relocked.html). That adb fastboot has the following files: adb, fastboot, adbwinapi.dll, adbwinusbapi.dll.
I think the source of the current problem is that I can no longer access my /sdcard or mount it. One step forward, then two steps back -_-.
Click to expand...
Click to collapse
You might need to do it as administrator.

I think I've got it. One last tip. All of the above has been helpful, but I think the problem was trying to use my Windows 8 laptop. The second I got to work, I plugged it in on the bootloader to my XP machine and voila! it recognized fastboot and listed devices.
I have tried to run the RUU 2.35.531.7 but just like unrooting my old phone, I had issues because that update was already on this phone, so it goes through the entire process only to tell me on the windows XP utility that it had failed because it was the wrong update. When I did this to my old One S right before I sent it into Tmobile for warranty, it did the same thing with the 1.53 RUU, then when I found the 2.35, it worked like a charm.
So my last question (hopefully) then is, am I missing something as for installing an OLD or exact same RUU? Or is there a newer one than the 2.35.531.7?
I haven't tried on a Windows 7 machine, but I have one available here at work. I'm wondering if I should try to fastboot a ROM. Any suggestions what I can do to get it back to stock, or an old old stock version? I'd like to root it so I can use my Titanium Backup.
Update: Before ending this reply, I read that the RUU may be failing because the bootloader is unlocked/tampered still. I'm going to run it again to grab the error code to make sure of the issue, because it seems you should be able to revert or use any RUU (correct?).

nik.the said:
I think I've got it. One last tip. All of the above has been helpful, but I think the problem was trying to use my Windows 8 laptop. The second I got to work, I plugged it in on the bootloader to my XP machine and voila! it recognized fastboot and listed devices.
I have tried to run the RUU 2.35.531.7 but just like unrooting my old phone, I had issues because that update was already on this phone, so it goes through the entire process only to tell me on the windows XP utility that it had failed because it was the wrong update. When I did this to my old One S right before I sent it into Tmobile for warranty, it did the same thing with the 1.53 RUU, then when I found the 2.35, it worked like a charm.
So my last question (hopefully) then is, am I missing something as for installing an OLD or exact same RUU? Or is there a newer one than the 2.35.531.7?
I haven't tried on a Windows 7 machine, but I have one available here at work. I'm wondering if I should try to fastboot a ROM. Any suggestions what I can do to get it back to stock, or an old old stock version? I'd like to root it so I can use my Titanium Backup.
Update: Before ending this reply, I read that the RUU may be failing because the bootloader is unlocked/tampered still. I'm going to run it again to grab the error code to make sure of the issue, because it seems you should be able to revert or use any RUU (correct?).
Click to expand...
Click to collapse
The bootloader does need to be relocked for the RUU too work and the RUU you used before should work because I have used the same RUU a few times and it worked fine.

Darknites said:
The bootloader does need to be relocked for the RUU too work and the RUU you used before should work because I have used the same RUU a few times and it worked fine.
Click to expand...
Click to collapse
I'll try that. thanks.
Now on the same XP computer, it's not showing when I adb devices, however it does show in device manager. This changed after trying to do the RUU without relocking.

Yeah! Fixed!
After enough toggling, I changed the recovery to the T one and relocked my bootloader. It turns out detecting the device wasn't necessary somehow. Then I ran the RUU and voila!

nik.the said:
I'll try that. thanks.
Now on the same XP computer, it's not showing when I adb devices, however it does show in device manager. This changed after trying to do the RUU without relocking.
Click to expand...
Click to collapse
Not sure whats up with that, never had any issue on win7.

Windows 8 fastboot works on my laptop for some reason. I installed the drivers from the HTC Sync folder.
Sent from my HTC One S using Tapatalk 2

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