I've had the great misfortune of bricking my phone within the first few hours of owning it. I should have known something was up, it wouldn't reboot when I changed the language to English, and I'd have to hard reset it (delete everything) and then let it load in Chinese again. Well, in an attempt to fix what I thought was a rom issue, I went through the song and dance of trying to root my phone.
I'm still not fully clear on how to do it, as it seems there's more to it than just what the tutorials say.
Anyway, like the title of this thread says, there's a pretty good way to figure out if your phone is really bricked, no need to ask or wonder anymore.
If your phone only boots to the htc magic screen (and then stops), and is unable to load bootloader, fastboot, usb connections, or anything else, it's bricked. 100%. You have to take it back. Don't bother searching the forums for the answer, I've wasted hours going through every related thread and trying every possible solution. Without the ability to access the fastboot screen, you're out of possibilities. Untill someone comes out with an unbricker which goes deeper than fastboot, there is absolutely no way to fix it.
A semi brick is much better on the other hand. There are plenty of ways to fix your phone, provided you're only semi bricked. I would define semi bricked as being able to enter fastboot, but being unable to boot the phone as normal. This can happen with a bad flash, or a mis step during a tutorial. I'm not exactly sure how easy it is to change a semi brick to a full brick, but my full bricking happened after semi bricking it while loading a new rom on it.
So. to summarize, if your phone WON'T go into the boot menu by pressing vol-down+power, you're in need of a new phone.
If you can still get into the boot menu, and access your phone through usb, you're ok, just get help (via a tutorial) before going any further, unless you're completely certain of what to do next.
Tis a shame to send a device, which is physically undamaged, to the digital graveyard. But such is life.
Caid.
444.
EDIT
on a side note, before my phone reset itself into it's endless loop of unloading, I noticed the screen flash an image of a box with what looked like a red arrow coming out of it. It was right in the center of the screen. This was in the recovery-RAv1.0H.img menu. What's that all about?
Did you try other key combinations such as Home+Power, or Back+Power?
I'm sorry but I think you're misunderstanding it all a little bit...
Caid444 said:
I've had the great misfortune of bricking my phone within the first few hours of owning it. I should have known something was up, it wouldn't reboot when I changed the language to English, and I'd have to hard reset it (delete everything) and then let it load in Chinese again. Well, in an attempt to fix what I thought was a rom issue, I went through the song and dance of trying to root my phone.
I'm still not fully clear on how to do it, as it seems there's more to it than just what the tutorials say.
Anyway, like the title of this thread says, there's a pretty good way to figure out if your phone is really bricked, no need to ask or wonder anymore.
Click to expand...
Click to collapse
It's easy if you follow the guides... I did it in two different phones with no problem at all in any of them... Anyway, let's stay on topìc
Caid444 said:
If your phone only boots to the htc magic screen (and then stops), and is unable to load bootloader, fastboot, usb connections, or anything else, it's bricked. 100%. You have to take it back. Don't bother searching the forums for the answer, I've wasted hours going through every related thread and trying every possible solution. Without the ability to access the fastboot screen, you're out of possibilities. Untill someone comes out with an unbricker which goes deeper than fastboot, there is absolutely no way to fix it.
Click to expand...
Click to collapse
Wrong. If your phone boots to the HTC Magic screen, the bootloader is doing it's job. The bootloader just takes you there. The linux kernel and ramdisk takes you to the boot animation, and there is where android really starts.
If your phone shows the first htc logo, or the Vodafone branded screen, you can start in bootloader mode. To make that you just have to remove the battery, put it back, and press and hold BACK + END KEY. From that, you can fastboot.
Also, and unless you destroyed the recovery partition, you can also boot in recovery mode, by pressing END KEY while holding HOME (no need to keep them both hold, just home button)
Caid444 said:
A semi brick is much better on the other hand. There are plenty of ways to fix your phone, provided you're only semi bricked. I would define semi bricked as being able to enter fastboot, but being unable to boot the phone as normal. This can happen with a bad flash, or a mis step during a tutorial. I'm not exactly sure how easy it is to change a semi brick to a full brick, but my full bricking happened after semi bricking it while loading a new rom on it.
Click to expand...
Click to collapse
I would call a semi brick this:
Your phone goes into an endless loop while booting.
Your phone gets stucked on the first boot logo.
You can't get access to the recovery partition.
Your phone boots all the way but then gets stucked.
Your phone gone bad during a software update.
That, all, can be solved by reflashing the affected region. There are tutorials for everything but if you need I can write some hints on each case (I suffered them all ).
Caid444 said:
So. to summarize, if your phone WON'T go into the boot menu by pressing vol-down+power, you're in need of a new phone.
Click to expand...
Click to collapse
Actually, VOLDOWN+POWER starts in Hboot mode. From there you can go back to fastboot mode, but hboot is used to make a software upgrade using complete images or running htc diagnostic images (SAPPDIAG.IMG, SAPP*.IMG /NBH).
Caid444 said:
If you can still get into the boot menu, and access your phone through usb, you're ok, just get help (via a tutorial) before going any further, unless you're completely certain of what to do next.
Tis a shame to send a device, which is physically undamaged, to the digital graveyard. But such is life.
Click to expand...
Click to collapse
If you can't get USB working on fastboot mode, or on recovery mode, your phone has probably a hardware fault. It happened with some of the first revisions of the Vodafone branded magic, don't know about htc branded ones though..
NOTE: Not talking about missing drivers, if you don't have drivers, that's another problem, but the computer should at least detect the device. Also, if your phone is off, and you connect the charger (or usb) and the orange led lights up, the bootloader should be ok.
Caid444 said:
on a side note, before my phone reset itself into it's endless loop of unloading, I noticed the screen flash an image of a box with what looked like a red arrow coming out of it. It was right in the center of the screen. This was in the recovery-RAv1.0H.img menu. What's that all about?
Click to expand...
Click to collapse
That's the recovery mode. With that you can unbrick your phone
Also, as another hint, if you're new to linux OSes, you might want to take a look at some manual on terminal commands. If your main software is bricked, it's possible that your SDCard doesn't get mounted on recovery mode, depending on wich recovery image you're running. Provided you have an update.zip on the sdcard you need to run, you might have to mount it manually.
To do that, you have to start the phone in recovery mode, and run an "adb shell" on the PC.
When you have a shell opened, you'll have to mount the sdcard manually:
mount /dev/block/mmcblk0p1 /sdcard
Then, on the phone you can use the option to run sdcard update.zip to restart the software upgrade procedure.
Regards!
Before I reply, I'd just like to say thank you very much for your extremely in depth reply.
biktor_gj said:
I'm sorry but I think you're misunderstanding it all a little bit...
It's easy if you follow the guides... I did it in two different phones with no problem at all in any of them... Anyway, let's stay on topìc
Wrong. If your phone boots to the HTC Magic screen, the bootloader is doing it's job. The bootloader just takes you there. The linux kernel and ramdisk takes you to the boot animation, and there is where android really starts.
If your phone shows the first htc logo, or the Vodafone branded screen, you can start in bootloader mode. To make that you just have to remove the battery, put it back, and press and hold BACK + END KEY. From that, you can fastboot.
Also, and unless you destroyed the recovery partition, you can also boot in recovery mode, by pressing END KEY while holding HOME (no need to keep them both hold, just home button)
I would call a semi brick this:
Your phone goes into an endless loop while booting.
Your phone gets stucked on the first boot logo.
You can't get access to the recovery partition.
Your phone boots all the way but then gets stucked.
Your phone gone bad during a software update.
That, all, can be solved by reflashing the affected region. There are tutorials for everything but if you need I can write some hints on each case (I suffered them all ).
Actually, VOLDOWN+POWER starts in Hboot mode. From there you can go back to fastboot mode, but hboot is used to make a software upgrade using complete images or running htc diagnostic images (SAPPDIAG.IMG, SAPP*.IMG /NBH).
If you can't get USB working on fastboot mode, or on recovery mode, your phone has probably a hardware fault. It happened with some of the first revisions of the Vodafone branded magic, don't know about htc branded ones though..
NOTE: Not talking about missing drivers, if you don't have drivers, that's another problem, but the computer should at least detect the device. Also, if your phone is off, and you connect the charger (or usb) and the orange led lights up, the bootloader should be ok.
That's the recovery mode. With that you can unbrick your phone
Also, as another hint, if you're new to linux OSes, you might want to take a look at some manual on terminal commands. If your main software is bricked, it's possible that your SDCard doesn't get mounted on recovery mode, depending on wich recovery image you're running. Provided you have an update.zip on the sdcard you need to run, you might have to mount it manually.
To do that, you have to start the phone in recovery mode, and run an "adb shell" on the PC.
When you have a shell opened, you'll have to mount the sdcard manually:
mount /dev/block/mmcblk0p1 /sdcard
Then, on the phone you can use the option to run sdcard update.zip to restart the software upgrade procedure.
Regards!
Click to expand...
Click to collapse
To the first answer.
It's not THAT easy, the guides are kinda (you should already know what you're doing at this point) in nature. It's confusing for newcomers, as we've no idea what to expect, that and there are a multitude of variations. More specification as to which guide works with which model, and which updates would be nice.
As for the second part, I could not get the phone working with any button variation pressed. I'm sorry I was not more clear in my description, to begin with. I could press (and hold) any button (or buttons) + power (end key) and the phone would just vibrate (briefly) and then display the original screen "htc magic"(endlessly). The orange light does come on when plugged into the usb or computer, but only while it is off, as soon as the device turns on, the light turns off.
Another thing of note is that, after bricking it, I had to remove the battery to turn it off (every time if it was on), and if I put the battery back in while it's plugged into the usb port of the computer, the phone would turn back on without pressing any buttons. It's also completely unresponsive or detectable by my computer after bricking it. The only other thing I can get it to do is make the orange light blue by holding the action button and turning on the device. That way the light on top of the device is blue when it turns on. Still unresponsive at that point.
This is my first android device, but not my first htc device (I've had MANY MANY different ones.) so I'm a bit familiar with trying different combinations to get a response.
I am not the first person who's had this happen, unfortunately. There have been a couple others, who've described the exact same encounter. Perhaps it's a mistake that I made, and perhaps they also made it themselves. I would like to figure out how it's happening, though, and perhaps write a tutorial for people like us unlucky few.
Again, a really big thanks. I've sent my phone back and am getting a new one soon. I much appreciate your reply, however, as it's probably the most understanding and considerate reply I've seen on these forums.
Cheers.
Caid.
444
One more quick question out of curiosity, when you press and hold back and press end to turn on the device (it still goes to the htc magic screen) SHOULD it go to a different screen, other than the "htc magic" screen? Or is that a process that runs without some sort of visual notification on the device itself?
The usb was completely unresponsive after this happened, but in the event that bootloader may have been running, (only possible if it runs without any visual notification on the device itself), I'll go pick up the device and see if my usb drivers on my computer just became unresponsive after being accessed too many times. Sometimes windows does that, right? Perhaps a reboot would have allowed fastboot and the drivers to connect again, if the device was trying to talk to the computer, but I just didn't know on account of not having any notification.
So, again, should pressing back and power bring me to a different screen? or would it also look like it was hanging on htc magic screen?
Caid.
444
p.s. Sorry for the confusing wording, I'm tired and trying very hard to be as specific as possible.
back+end/power should lead you to the fastboot screen right after it shows the HTC Magic screen or whatever splash screen you have installed.
Home+end/power should lead you to the recovery screen.
ok, it was bricked. Thanks for the answer.
Caid.
444
Caid444 said:
Before I reply, I'd just like to say thank you very much for your extremely in depth reply.
To the first answer.
It's not THAT easy, the guides are kinda (you should already know what you're doing at this point) in nature. It's confusing for newcomers, as we've no idea what to expect, that and there are a multitude of variations. More specification as to which guide works with which model, and which updates would be nice.
Click to expand...
Click to collapse
No problem, we all should be here to learn, and to help (except for the trolls)
This is the guide I followed for both Vodafone branded Magics: http://android-dls.com/wiki/index.php?title=Magic_Rooting
Maybe not for now, but for the next magic you get it may come handy
Caid444 said:
As for the second part, I could not get the phone working with any button variation pressed. I'm sorry I was not more clear in my description, to begin with. I could press (and hold) any button (or buttons) + power (end key) and the phone would just vibrate (briefly) and then display the original screen "htc magic"(endlessly). The orange light does come on when plugged into the usb or computer, but only while it is off, as soon as the device turns on, the light turns off.
Click to expand...
Click to collapse
When the phone is off with the charger connected and you press the power button, the light goes off, as for the others, you really should be able to enter the SPL if it could the magic bootlogo and vibrated upon boot...
Maybe you didn't try enough or maybe your bootloader behaved differently than mine... I should be more clear anyway, to get to the bootloader, the best way to make it go to the bootloader is press and hold back key, then while holding it, hold the power button too. It should take about a second or two before showing the three skater droids.
Caid444 said:
Another thing of note is that, after bricking it, I had to remove the battery to turn it off (every time if it was on), and if I put the battery back in while it's plugged into the usb port of the computer, the phone would turn back on without pressing any buttons. It's also completely unresponsive or detectable by my computer after bricking it. The only other thing I can get it to do is make the orange light blue by holding the action button and turning on the device. That way the light on top of the device is blue when it turns on. Still unresponsive at that point.
Click to expand...
Click to collapse
When you put the battery while USB or charger is connected, the phone boots up, that's the normal behaviour. About the blue led, that's the Radio bootloader. That's quite dangerous to play with, but it gives a lot of other functions. Another sign that your phone wasn't completely dead Even if you wipe the SPL (the three skater droids), you may be able to boot into the Radio bootloader and write or boot another one to fix it. But that's waaaay harder
Caid444 said:
This is my first android device, but not my first htc device (I've had MANY MANY different ones.) so I'm a bit familiar with trying different combinations to get a response.
I am not the first person who's had this happen, unfortunately. There have been a couple others, who've described the exact same encounter. Perhaps it's a mistake that I made, and perhaps they also made it themselves. I would like to figure out how it's happening, though, and perhaps write a tutorial for people like us unlucky few.
Click to expand...
Click to collapse
I guess the first advice when you start tricking with a phone is be careful with what you're doing. That's the good thing of fastboot.
When booting on fastboot mode, you can pick, for example a recovery image, and boot it without overwriting the original rom:
Code:
fastboot boot [recovery_image]
Then, when you see it's working, you can flash it:
Code:
fastboot flash recovery [recovery_image]
fastboot flash boot [boot_image]
fastboot flash system [system_image]
fastboot flash data [data_image]
You can't do that with the system.img since it's too big, but you can do it also with a boot.img
About the key combinations on the phone, it goes like this:
Code:
BACK + END KEY -> Fastboot mode (you shouldn't see the boot logo)
VOLDOWN + END KEY -> Hboot mode (you shouldn't see the boot logo)
ACTION (trackball center) + END KEY -> Radio Bootloader (you shouldn't see the boot logo)
HOME + END KEY -> Recovery mode (you should see the boot logo, then get the recovery menu)
SEND + MENU + END -> Reboot the phone (while the phone is on)
Maybe there are more (android has kind of 'safe mode' but I don't know it it goes there automatically if there's a problem or if it has to be called manually)
Anyway, I hope these things will be useful for the next phone, and for anybody who's a bit lost on this
Regards!
Let us know where you live , so maybe one can help you , I live in Sweden and will be glad to help you if you are near ;-)
Hey! Thanks again for all the help, and the offer to come help. Unfortunately, I'm in China. Coming here from Sweden (although it's a single large landmass) would take quite a bit of time
I appreciate all the support, though. Very cool community we're building here for the magic.
Caid.
444
htc semi-brick?
Hi to all. I'm in the same condition described in this tread; after installing SPL i get the htc block in Vodafone brand red screen.
None keys combination bring me to the boot menù. Only Action(trackball) + power have effect, but with a black screen...
Any suggest?
What do you do if you can boot into fastboot but can't flash anything because absolutely everything gives the error "FAILED (remote: signature verify fail)"?
I have a card reader and have tried just about every sappimg.zip, every boot.img, every recovery.img i could find. I can't even boot a recovery img because the screen just hangs at the HTC Magic logo.
I don't know what kind of warranty i have on this thing, but i might take it in tomorrow and see if i can get it replaced. I've only had it for just under two weeks.
Newbie need help
ok so i can still go to recovery mode but everytime i reboot my phone the mytouch 3g logo never goes away im new to Android but not htc can somebody plz help me out.
gruppler said:
What do you do if you can boot into fastboot but can't flash anything because absolutely everything gives the error "FAILED (remote: signature verify fail)"?
I have a card reader and have tried just about every sappimg.zip, every boot.img, every recovery.img i could find. I can't even boot a recovery img because the screen just hangs at the HTC Magic logo.
I don't know what kind of warranty i have on this thing, but i might take it in tomorrow and see if i can get it replaced. I've only had it for just under two weeks.
Click to expand...
Click to collapse
Instead of flashing something, you boot a recovery image, and then, from there, you flash whatever you need (using adb & flash_image for example)
PS: Be a little patient, if fastboot is letting you boot a recovery image, the recovery needs to boot, and that takes a little while, and while it's booting, you see the bootlogo until the menu appears. Also, you can try running adb shell after boot process started to try to get an error message (or at least to know if the thing is booting in some way)
I couldn't boot any recovery images. I had tried a few different Hero ROMs but decided i wanted to use Cupcake again because i have a 32B board and it just doesn't have enough RAM, though Swapper makes it usable at least. I don't know what exactly i did, but i've learned a lot from my mistakes. Everything i tried failed the signature check because the hboot version didn't match. If i could just flash the 1.33.2005 hboot again, i would have been in business, but no matter which recovery image i tried, it just sat there doing nothing. And believe me, i waited.
Fortunately, T-Mobile gave me a new device after i took it in and played dumb. And I just rooted it =]
Caid444 said:
ok, it was bricked. Thanks for the answer.
Caid.
444
Click to expand...
Click to collapse
Why not flashing it with an RUU from HTC. Not sure that would work but it is worth trying.
Hi there, people!
First of all, thanks because while I was reading ur posts I realized that my phone had been bricked, 100 %
I tried official ROM upgrade to Android 1.6 using the folowing steps
1. Copied radio zip to my sd card by renaming it in update.zip
2. Recovery screen was started by pressing HOME+END key
3.Applied update.zip, process was going on: Opening package, verifing package, installing radio...and message about success was shown and phone restarted
4. Phone stucked on HTC Magic logo screen...15 minutes
5. I removed a battery, put it back and tried to reach recovery or boot mode again
6.Unsuccessfully! Phone vibrates and turns on...but always stucks on the HTC Magic screen
7. USB does not recognize my phone is connected (I tried any adb and fastboot commands)
8. So, I just pray to give me a new phone if my warranty will be accepted
iivanovic said:
Hi there, people!
First of all, thanks because while I was reading ur posts I realized that my phone had been bricked, 100 %
I tried official ROM upgrade to Android 1.6 using the folowing steps
1. Copied radio zip to my sd card by renaming it in update.zip
2. Recovery screen was started by pressing HOME+END key
3.Applied update.zip, process was going on: Opening package, verifing package, installing radio...and message about success was shown and phone restarted
4. Phone stucked on HTC Magic logo screen...15 minutes
5. I removed a battery, put it back and tried to reach recovery or boot mode again
6.Unsuccessfully! Phone vibrates and turns on...but always stucks on the HTC Magic screen
7. USB does not recognize my phone is connected (I tried any adb and fastboot commands)
8. So, I just pray to give me a new phone if my warranty will be accepted
Click to expand...
Click to collapse
I have the same problem. I get up hboot and fast boot menus can not get it in recovery. try to add in sappimg but no luck
I'm having the exact same problem...
Any solution yet?
Hello! I can assure you that your phone is not fully bricked! Awhile ago I flashed a new radio only to discover that I hadn't done my research and was a complete and total idiot. I flashed the 1.76.xxxx on a 32B. It didn't like it. I got a quick HTC logo that disappeared then the phone never responded again. When I say never responded it was dead. no combination of buttons would get any response. If you can get into fastboot you have options. All that's necessary is to make sure you have the appropriate sappimg file. Try the Unlockr's gold card method file. He has a .zip file that may work for you. Just make sure that you find an image that is compatible with your board (32A or 32B). Hope this helps!
I literally had the worst combination of events take place the other day:
So, I was running Firefly 3.0, and I planned on replacing it with a gingerbread ROM, (since my apps weren't saving data, for some reason), and I started to notice that my unlock button was starting to hang a bit. I thought this was just another side effect from Firefly 3.0 acting weird.
So, I boot to download, and flash the CM7 kernel with CWM 3.0 on it, and it passes.
The next step is to navigate around in CWM to install the ROM file before you can boot up. But, the power/lock button still doesn't work! So I'm stuck in CWM 3.0, unable to boot correctly. The touch buttons don't work like they do in CWM 2.x, so I'm... stuck.
So, I call Samsung, and I'm having a replacement sent to me within the week, since I can't even power on/off my phone (if it wasn't for CM7's auto-boot when you put the battery in)
So, already having adb installed on my Linux boot, I jump over there to send the adb reboot download command. All this does is reboot the phone "normally"!
What are my options here? I've already copied everything off my phone with adb, and I'm not afraid to use terminal commands to flash something usable just to get it back to stock before I send it back.
*cough*JIG * COUGH*
Sent from my SAMSUNG-SGH-I897 using XDA App
Would that work with CWM 3.0/CM7 Kernel? I've always had weird issues with plugging things in and it just booting up, even when my power button worked.
The jig should work...the only thing that would cause the cm7 kernel to boot when plugged in is if it was off and you were only trying to charge it. The jig just redirects some power into pin 4 telling the bootloader to initiate download protocol...kinda the same way your phone knows when its hooked to a mountable usb port and when its charging out of the wall or something.
similar issue
I recently attempted a flash of fantasy II (2.3.5) captivate, and i got the bootload, and kernel installed and then installed the stock 2.3.5 rom to flash fantasy II over. . . . well after getting the stock rom, i found it had what i wanted, so i was going to stick with that.
i noticed about ten minutes after getting that rom, that my lock button was not working, and the phone would auto boot, i would pull the battery and put it back in and BOOM at&t boot screen right away, not one button pushed, I have bricked and unbricked my phone since then, and i am now simply running 2.1 stock, however; the dang lock button still does not respond at all, and it will auto boot still, is this the kernel or the bootloader? I know its not the rom now . . . . Please help this is awful!
and if you have a solution that i can download please post it!
I was on a call and when I hung up, wanted to unlock.
Push the power button, lights on the 4 bottom buttons come on. Screen stays black, no backlight.
Push the button again, lights go off.
Push again, lights come on, no screen.
etc, etc...
I pulled the battery, and put it back in.
Now it's just sitting here saying HTC, but it doesn't get to the "quietly brilliant" ever. It just sits there forever saying HTC.
The phone is hacked, rooted, ENG S-OFF, was running Android Revolution 4G 5.1.6 or something when this all happened.
I can get into the [vol-] + [power] menu (white BG) and to recovery (black BG), but I'm not sure how to transfer files to the SD card to load a new ROM on without Android.
Can I use ADB to push a file across? If so, how?
Is there anything I should try before I wipe my phone? I'd like to back up my apps and SMSs if possible, but won't break down in tears if I can't.
Edit: I don't really know very much about ADB/Fastboot, but when I type ADB Devices the phone doesn't show up, however if I go into "Fastboot" in the white screen, I can type Fastboot Devices and my phone is listed. I suspect I can somehow push across the Android Revolution 4G ROM zip file and wipe/install it from recovery? I'm not sure how though.
WHile the phone is completely off, press and hold the Volume (down) and the Power off/on button (press the volume down first if that makes it easier ,then the power button).
Then you should get to the Hboot screen (white back), in there you should have the option to go to recovery...
As long as you can get to recovery ,your perfectly safe (even if just the hboot page)...In here you can reinstall a new ROM.
You can do so by going to mounts and storage , and choose mount usb storage (or something; make sure your connected to the PC with the USB)..
Your phone should now be connected to your pc Via your SD card..
Just download a new ROM, and then put it somewhere in your SDcard and after that, choose install zip from SDcard and select the ROM file you just transfered.
ANd unfortunately but, if you cant get passed recovery..I believe there would be no way to back up any phone/internal data .
If he wanted to back up some data as long as he has AR 5.1.6 still he should be able to reflash the rom w/o a full wipe to try and get the phone to boot so he can back up.
Some times it works sometimes it doesn't.
Just boot into hboot , then from there get to recovery. Once in recovery, you should now be able to use adb (if fastboot is working, it should see the phone in recovery).
Now put the rom in the platform tools folder(or whereever your tools/adb is (not sure if your using Linux or windows but this should work with either. Now open a terminal to platform-tools(or like earlier, whereever adb and now the rom are) now -
adb push nameofrom.zip /sdcard
nameofrom.zip has to be exactly what the name of the rom is you put in the location that has adb in it.
It will take a few min. to push the whole rom, when its done flash it.
This is all assuming you don't have adb in your enviorn . path- it can be done a little differently if you have it in your path in windows or Linux, but this way will work either way.
Or use fastboot to flash a new system.img, but you'll have to find one or make one- don't know where.
Di11's method is fine, but pardon me if im mistaken, can't he, since he's able to boot into recovery, plug his cord in>mount usb storage>transfer rom to sdcard>unmount>and wipe data/cache/dalvik/flash rom? it would seem easiest
Ya, sometimes I've noticed in the past when ****s all muffed up it wont wanna mount as USB storage. (Dont know why but it happens)This works every time.
di11igaf said:
Ya, sometimes I've noticed in the past when ****s all muffed up it wont wanna mount as USB storage. (Dont know why but it happens)This works every time.
Click to expand...
Click to collapse
Never had a problem like that, least that i know of lol, my baffled mind forgets to put the rom on my phone since i flash your rom and sense rom's daily, so i always just mount while in recovery after wiping everything.. Anyways, OP report which method you used and how it works.
Hey Guys ,
I think my phone is dead or bricked... ...i have tried to root with the hack-ace and had an issue in the middle of the rooting !!...now my phone can't boot , not even recovery mode , pull the battery, put it back in , nothing happens ..when i plug the usb cable into the computer i have the orange led lighting up but no boot is possible...
have any solution for me ?? it would be highly appreciate !!
thanks
maostar said:
Hey Guys ,
I think my phone is dead or bricked... ...i have tried to root with the hack-ace and had an issue in the middle of the rooting !!...now my phone can't boot , not even recovery mode , pull the battery, put it back in , nothing happens ..when i plug the usb cable into the computer i have the orange led lighting up but no boot is possible...
have any solution for me ?? it would be highly appreciate !!
thanks
Click to expand...
Click to collapse
Go back to the hack kit thread, read the op, towards the bottom it talks about hitting the irc for help. Reeeaaadddd then go there for help.
I got your 10 char right here
I'm a noob and I wiped my phone before trying recovery! DERP. Not sure what to do next.
So... I need a little help. I've been looking around and havent been able to find a situation like mine. I've got a completely wiped/factory reset HTC Inspire 4g. SD card is good and reformatted to fat32. Heres the basics. When I press the power button I get 3 vibrate and orange light, when I press volume down and power I get 5 vibrates and green light. When I plug phone in with usb (to computer or charger) I get clockworkmod recovery v5.0.2.7. I am able to toggle through options, all works fine.
This is where I need help and I get easily confused. What do I do to get this phone back to stock settings? I've tried putting the stock pd98img.zip file onto the sd card, then installing via clockwork recovery. When I do this, I get failed installation EVERY time. I've also tried connecting through ace hack kit on my lap top and running the stock settings flash. Whenever it resets the phone it does the 3 vibrates/orange light and stops.
I would really appreciate someone with a little more experience to walk me through what I need to do to recover.
Update: When I try to download the zip from the sd card via clockworkmod I get the error E:Signature Verification Failed. I'm not sure what this means.
If someone can solve my problem I'll buy them lunch or coffee! Some kind of gift card to your favorite place? I'd really like my android back!
Drdandy said:
I'm a noob and I wiped my phone before trying recovery! DERP. Not sure what to do next.
So... I need a little help. I've been looking around and havent been able to find a situation like mine. I've got a completely wiped/factory reset HTC Inspire 4g. SD card is good and reformatted to fat32. Heres the basics. When I press the power button I get 3 vibrate and orange light, when I press volume down and power I get 5 vibrates and green light. When I plug phone in with usb (to computer or charger) I get clockworkmod recovery v5.0.2.7. I am able to toggle through options, all works fine.
This is where I need help and I get easily confused. What do I do to get this phone back to stock settings? I've tried putting the stock pd98img.zip file onto the sd card, then installing via clockwork recovery. When I do this, I get failed installation EVERY time. I've also tried connecting through ace hack kit on my lap top and running the stock settings flash. Whenever it resets the phone it does the 3 vibrates/orange light and stops.
I would really appreciate someone with a little more experience to walk me through what I need to do to recover.
Update: When I try to download the zip from the sd card via clockworkmod I get the error E:Signature Verification Failed. I'm not sure what this means.
If someone can solve my problem I'll buy them lunch or coffee! Some kind of gift card to your favorite place? I'd really like my android back!
Click to expand...
Click to collapse
You only flash pd98 files from fast boot not from CWM recovery. Boot in bootloader and it will find it
I am going to come off as the biggest noob here, but its got to be done. How do you boot in bootloader?
EDIT: Alright. So Bootloader is Volume down and power. My phone won't boot into bootloader. Phone vibrate 5 times and green led comes on. Screen stays black the whole time.
Drdandy said:
I am going to come off as the biggest noob here, but its got to be done. How do you boot in bootloader?
EDIT: Alright. So Bootloader is Volume down and power. My phone won't boot into bootloader. Phone vibrate 5 times and green led comes on. Screen stays black the whole time.
Click to expand...
Click to collapse
Ok i dont use CWM but there maybe an option in there to reboot into bootloader. Try holding volume up and power. Could be confusing devices on that though
zelendel said:
Ok i dont use CWM but there maybe an option in there to reboot into bootloader. Try holding volume up and power. Could be confusing devices on that though
Click to expand...
Click to collapse
Nah, no other combo's work for getting into bootloader or rebooting it. From what I've read on other forums, if I can't get into bootloader, I'm bricked. Do you think since the phone is wiped back to factory settings that HTC would replace it under the warranty?
Since you can boot into recovery, adb should still work. Enter recovery then plug in your phone to PC and run adb reboot bootloader
Have you tried reflashing a rom in recovery aswell?
Drdandy said:
Nah, no other combo's work for getting into bootloader or rebooting it. From what I've read on other forums, if I can't get into bootloader, I'm bricked. Do you think since the phone is wiped back to factory settings that HTC would replace it under the warranty?
Click to expand...
Click to collapse
If you are booting into CWM your not back to factory. As stated above you can use adb to boot into bootloader
Just making sure I'm doing this right as its the first time I've ever use adb commands to me phone. Do I need to downloand Android SDK to write commands to the phone?
Okay. I've learned how to use the adb commands. That was cool. haha. So I popped the battery out, then back in to get to CWM. With phone connected to computer I tried adb reboot bootloader. My phone rebooted itself, but it did the 3 vibrates with a flashing orange LED. Adb reboot recovery does the same thing.
For being in recovery. Are you guys talking about the volume down power combination, when I do this and connect the phone to the pc, the pc doesn't detect the phone. So there is no abd commands/flashing roms to it in recovery.
Drdandy said:
Okay. I've learned how to use the adb commands. That was cool. haha. So I popped the battery out, then back in to get to CWM. With phone connected to computer I tried adb reboot bootloader. My phone rebooted itself, but it did the 3 vibrates with a flashing orange LED. Adb reboot recovery does the same thing.
For being in recovery. Are you guys talking about the volume down power combination, when I do this and connect the phone to the pc, the pc doesn't detect the phone. So there is no abd commands/flashing roms to it in recovery.
Click to expand...
Click to collapse
OK looks like your bootloader is messed up. Go to the ace hack kit thread. There you will find a link foe the IRC chat room. Go there and tell them what you did. They maybe able to help you.
edit
I had the hTC EVO Design 4G as pretty much my first Smart Android. (Im not including the LG optimus M). The Switched to the Galaxy note & S3 for a while NOw Im using the HTC one S. I normally never have these problems or ever post on the forums. But Im desperate for fast help. I know how to do everything on both the htc evo 4g and design.
but The Ville is diff. without the removable battery
im blabbering....
let me try to STEPbySTEP explain my steps up to my not working Device.
!. I tried to Flash the Energy_9.07.2012.OneS.zip rom through TWRP at first. (thats was the suggesttion in the thread. So that the recovery would Flash the correct Kernel. But upon reboot. I discovered that contrary to the devs suggestion the WiFi still didnt work. So I flashed CWM through ROM manager. reboot into recovery flash wiped cache/ factory reset. But I dont think I wiped system, data, or anything not in the main Menu, Energy_9.07.2012.OneS.zip and I reboot. Upon reboot the HTC screen had the warning for use in htc do not distribute...then the bootanimation popped up and finally the booted up fine. Wifi was working this time. But now my network wasnt right. I didnt give the rom time to settle in though. I panic and open CMD and ran adb reboot fastboot.
Waited waited
now the boot loader was up. I had to unplug my deviice for the screen to show fastboot usb.
then this is where I think I ****ed up my phone
(I extracted the boot.img from the Energy_9.07.2012.OneS.zip and placed it in my android folder on C I also adb pulled my twrp recovery to
C:\android and renamed to recovery,img I wanted TWRP back I hate how CWM automaticaly boots when you plug it in tp charge from dead)
Now I had in my C:\Android\boot.img and \recovery.img.
I ran the command (im not sure if I ran boot or recovery first)Also my phone was anywhere near a full battery cloase to dead but my CMD window showed complete.
C:\Windows\system32>fastboot flash boot C:\android\boot.img
C:\Windows\system32>fastboot flash recovery C:\android\recovery.img
Now my phone is plugged into my Lenovo Thinkpad t410 with Win7 Pro OEM The red light to the top right isnt blinking like the battery to low to power on notification. Its steady. but when I hold down to turn on either the lights for the capacitie buttons flash untill I let go of the button or I do a combo of plugging in and out the usb and holding the power and volume bottons not sure Which order. PLEASE HELP! iM EXPECTING A PHONE CALL ABOUT A JOB INTERVIEW RESULTS.
In my time in CMD this error did pop up a few times. But I open HTC sync let it load. and then it would work.
C:\Windows\system32>adb reboot device
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
Would A ruu fix this????? Although I haven't once successively used one.
COMMENT, PM, IM, ME I DON'T CARE JUST PLEASE HELP ME AN MY POOR [PHONE] GUARANTEED THANKS BUTTON!!!!!!! USAGE AS FOR HELPING.
why would you flash something made for HTC ONE S if you have HTC EVO
especially when you're just starting to learn about
sorry, but I would guess that you're chance is to find somewhere a ruu for your model
ultimul said:
why would you flash something made for HTC ONE S if you have HTC EVO
especially when you're just starting to learn about
sorry, but I would guess that you're chance is to find somewhere a ruu for your model
Click to expand...
Click to collapse
I have the HTC One S Ville
I was stating how I use to have the evo
gisaac2157 said:
I had the hTC EVO Design 4G as pretty much my first Smart Android. (Im not including the LG optimus M). There is no development forum for that devices in XDA so I used SDX-DEV I actually started learning how to kang my own roms.
im blabbering....
let me try to STEPbySTEP explain my steps up to my not working Device.
!. I tried to Flash the Energy_9.07.2012.OneS.zip rom through TWRP at first. (thats was the suggesttion in the thread. So that the recovery would Flash the correct Kernel. But upon reboot. I discovered that contrary to the devs suggestion the WiFi still didnt work. So I flashed CWM through ROM manager. reboot into recovery flash wiped cache/ factory reset. But I dont think I wiped system, data, or anything not in the main Menu, Energy_9.07.2012.OneS.zip and I reboot. Upon reboot the HTC screen had the warning for use in htc do not distribute...then the bootanimation popped up and finally the booted up fine. Wifi was working this time. But now my network wasnt right. I didnt give the rom time to settle in though. I panic and open CMD and ran adb reboot fastboot.
Waited waited
now the boot loader was up. I had to unplug my deviice for the screen to show fastboot usb.
then this is where I think I ****ed up my phone
(I extracted the boot.img from the Energy_9.07.2012.OneS.zip and placed it in my android folder on C I also adb pulled my twrp recovery to
C:\android and renamed to recovery,img I wanted TWRP back I hate how CWM automaticaly boots when you plug it in tp charge from dead)
Now I had in my C:\Android\boot.img and \recovery.img.
I ran the command (im not sure if I ran boot or recovery first)Also my phone was anywhere near a full battery cloase to dead but my CMD window showed complete.
C:\Windows\system32>fastboot flash boot C:\android\boot.img
C:\Windows\system32>fastboot flash recovery C:\android\recovery.img
Now my phone is plugged into my Lenovo Thinkpad t410 with Win7 Pro OEM The red light to the top right isnt blinking like the battery to low to power on notification. Its steady. but when I hold down to turn on either the lights for the capacitie buttons flash untill I let go of the button or I do a combo of plugging in and out the usb and holding the power and volume bottons not sure Which order. PLEASE HELP! iM EXPECTING A PHONE CALL ABOUT A JOB INTERVIEW RESULTS.
In my time in CMD this error did pop up a few times. But I open HTC sync let it load. and then it would work.
C:\Windows\system32>adb reboot device
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
Would A ruu fix this????? Although I haven't once successively used one.
COMMENT, PM, IM, ME I DON'T CARE JUST PLEASE HELP ME AN MY POOR [PHONE] GUARANTEED THANKS BUTTON!!!!!!! USAGE AS FOR HELPING.
Click to expand...
Click to collapse
If you hold down the power button long enough the leds should stop flashing. You should try that and then once it goes off, hold down the volume down and the power button.
That should get you back into bootloader. From there you may want to try flashing a custom kernel (the SENSE version of Fusion, for example).
An RUU could help, but you would need to relock your bootloader in order to flash it. You would need to be able to get to your bootloader screen. RUUs are EXE files and are pretty self explanatory when you run them and have your phone connected. See http://www.4shared.com/folder/jKN2qjTl/HTC_Ville_RUU_Collection.html for RUUs. There is also a thread on RUUs in the development thread. Read that too.
But first things first, you need to be able to access your bootloader! Keep fiddling with your power button and volume down button.
AKToronto
gisaac2157 said:
I have the HTC One S Ville
I was stating how I use to have the evo
Click to expand...
Click to collapse
can you reboot into recovery/fastboot? press the power button for 5-7 seconds until the keys start blinking;
the phone should reset after it
some RUU, you can find here:
http://androidforums.com/one-s-all-things-root/560329-ruu-download-mirrors.html
Thanks so much.
AKToronto said:
If you hold down the power button long enough the leds should stop flashing. You should try that and then once it goes off, hold down the volume down and the power button.
That should get you back into bootloader. From there you may want to try flashing a custom kernel (the SENSE version of Fusion, for example).
An RUU could help, but you would need to relock your bootloader in order to flash it. You would need to be able to get to your bootloader screen. RUUs are EXE files and are pretty self explanatory when you run them and have your phone connected. See <font color="red"> as a new member cant post links</font> for RUUs. There is also a thread on RUUs in the development thread. Read that too.
But first things first, you need to be able to access your bootloader! Keep fiddling with your power button and volume down button.
AKToronto
Click to expand...
Click to collapse
I feel really stupid for not knowing THAT. Now whats up with the energy rom? the thread says stable. How am I suppose to flash it?