Develop Bugs

Noob Here.HTC Evo 4G boot loop, Red triangle recovery. Help plz

I tried rooting my evo and now every time I start it up it vibrates once and stays on the black lettered "HTC Evo 4G" screen. Help please. And if you can, can you make it so it's noob friendly step by step answer because I am a androind noob a bit.
When I try to go and recover it from the Hboot screen it shows a red triangle with an exclamation point.

jacker300 said:
I tried rooting my evo and now every time I start it up it vibrates once and stays on the black lettered "HTC Evo 4G" screen. Help please. And if you can, can you make it so it's noob friendly step by step answer because I am a androind noob a bit.
When I try to go and recover it from the Hboot screen it shows a red triangle with an exclamation point.
Click to expand...
Click to collapse
How far along into the process did you get? Please give me more info. I am willing to help but in the future try to be as detailed as you can in the original post so that the community can better assist you. Feel free to send me a PM and I will try to guide you. Also after your issue is settled please come back to the post and list the methods and steps you used to rectify the problem. It helps the rest of the community which may have the same problem.

The red triangle means you don't have a recovery like clockwork or amon RA installed. You can fix this by doing a quick search on xda for "HTC Evo amon RA." That will bring up the thread with the image you can flash.
Also, like wc_outlaw stated, we need more information.
Were you rooted before or is this your first attempt?
What method did you use? UnrEVOked or Revolutionary?
What is your radio version?
How far through the rooting process did you get?
Did you see any error messages?
Did you observe any weird behavior from your phone?
When you load into your hboot does it say S-on or S-off?
What hboot version do you have?
All of this information will narrow down things for us that will help us give you a more accurate answer in a shorter period of time.
Sent from my V6 Supercharged Evo.

Thanks for the replies, but I managed to fix it by using this version of RUU:
"RUU_SuperSonic_GB_Sprint_WWE_4.24.651.1_Radio_2.15.00.05.02_NV_2.15_release_199233_signed"
Here is what I did in steps and I will try to be descriptive keep in mind that I did this on Windows 7 and Windows vista should be similar but I don't know about XP. I know this seems like a lot of steps, but the whole process took me only about 5-8 mins:
*BEFORE DOING ALL OF THIS DELETE ANY OLD DRIVERS FROM THE DEVICE MANAGER AND YOUR ADD/REMOVE PROGRAMS IN YOUR CONTROL PANEL!*
- Go to this( wwwyou.tube.com/watch?v=qkRN1wd6SEM) video and in the description download the 2 links!. Credit goes to him for uploading them. I can't post them here because I don't got 8 posts yet. Just add the . between "www" and "youtube" and delete the . between "you" and "tube"
1) Download RUU(I don't think the latest one makes a difference either)
2) Download evo drivers
3) Unzip the evo drivers but don't touch them
4) After take out the battery from your evo and your evo should be OFF when the battery is taken out
5) plug in the usb to your evo and computer
6) put the battery back in the evo and hold the "power button" + " volume DOWN" button till you get to a screen with 3 skateboarding robots at the bottom
7) Select fast boot
8) Stay on that screen that shows power down, restart, etc, but DON'T touch anything
9) With your usb still plugged in and being on the fast boot screen you should see your computer installing the drivers for HTC( Doesn't matter if they successfully install or fail. I will get to that)
10) Now on your computer press start and right click on my computer and click manage
11) After that a window should pop up and click on the left hand side click "Device Manager"
12) You should see USB android device or android devices or something. Drop the list down by pressing the "+" next to it on its left
13) "MY HTC" Should show under the box. Right click that and select "update driver software"
14) With a new window popping up something that says search on my computer something like that
Make sure that "check sub-folders" is checked
Now browse and go to the extracted HTC drivers folder and click on it ONCE and DON'T click any of the sub folders within it. Just the folder that has all the other folders in inside it. ( Example you click: Desktop/HTC Drivers, and NOT: Desktop/HTC Drivers/AMD64)
Now it should detect it and install it.
============================================================
*IF YOU DON'T SEE USB ANDROID DEVICE OR ANDROID DEVICES THEN FOLLOW THIS. IF YOU DO SEE IT THEN IGNORE THIS PART AND SKIP TO STEP 15!*
- Ok you might see a yellow triangle box with an exclamation point next to a device in device manager.
- Press the "+" and it should say like ABD device
- Right click on it and click update driver software.
- With a new window popping up something that says search on my computer something like that
- Make sure that "check sub-folders" is checked
- Now browse and go to the extracted HTC drivers folder and click on it ONCE and DON'T click any of the sub folders within it. Just the folder that has all the other folders in inside it. ( Example you click: Desktop/HTC Drivers, and NOT: Desktop/HTC Drivers/AMD64)
- Now it should detect it and install it.
- Follow step 15 now
============================================================
15) Once installed run the RUU file that you downloaded(*Windows 7, Vista users run as admin and compatibility mode of Windows XP Service Pack 3!*)
16) Make sure your evo is still connected and is still in the fast boot screen
17) Follow the onscreen instruction on RUU
18) When a progress bar(0-100% Bar) shows up on RUU just let it do its thing and DON'T OPEN ANYTHING, OR CANCEL RUU!
19) Make sure your computer DOESN'T go in to Sleep, hibernation mode
20) Once it's done it should reboot and your evo should be working.
Cheers!
Hope I helped!

jacker300 said:
I tried rooting my evo and now every time I start it up it vibrates once and stays on the black lettered "HTC Evo 4G" screen. Help please. And if you can, can you make it so it's noob friendly step by step answer because I am a androind noob a bit.
When I try to go and recover it from the Hboot screen it shows a red triangle with an exclamation point.
Click to expand...
Click to collapse
Does your hboot say s-on or s-off? if s-off, you're rooted, just no recovery. In that case, go to the dev section and download your recovery of choice. The red exclamation mark you see when you go into recovery is stock recovery [no recovery].

jacker300 said:
Thanks for the replies, but I managed to fix it by using this version of RUU:
"RUU_SuperSonic_GB_Sprint_WWE_4.24.651.1_Radio_2.15.00.05.02_NV_2.15_release_199233_signed"
Here is what I did in steps and I will try to be descriptive keep in mind that I did this on Windows 7 and Windows vista should be similar but I don't know about XP. I know this seems like a lot of steps, but the whole process took me only about 5-8 mins:
*BEFORE DOING ALL OF THIS DELETE ANY OLD DRIVERS FROM THE DEVICE MANAGER AND YOUR ADD/REMOVE PROGRAMS IN YOUR CONTROL PANEL!*
- Go to this( wwwyou.tube.com/watch?v=qkRN1wd6SEM) video and in the description download the 2 links!. Credit goes to him for uploading them. I can't post them here because I don't got 8 posts yet. Just add the . between "www" and "youtube" and delete the . between "you" and "tube"
1) Download RUU(I don't think the latest one makes a difference either)
2) Download evo drivers
3) Unzip the evo drivers but don't touch them
4) After take out the battery from your evo and your evo should be OFF when the battery is taken out
5) plug in the usb to your evo and computer
6) put the battery back in the evo and hold the "power button" + " volume DOWN" button till you get to a screen with 3 skateboarding robots at the bottom
7) Select fast boot
8) Stay on that screen that shows power down, restart, etc, but DON'T touch anything
9) With your usb still plugged in and being on the fast boot screen you should see your computer installing the drivers for HTC( Doesn't matter if they successfully install or fail. I will get to that)
10) Now on your computer press start and right click on my computer and click manage
11) After that a window should pop up and click on the left hand side click "Device Manager"
12) You should see USB android device or android devices or something. Drop the list down by pressing the "+" next to it on its left
13) "MY HTC" Should show under the box. Right click that and select "update driver software"
14) With a new window popping up something that says search on my computer something like that
Make sure that "check sub-folders" is checked
Now browse and go to the extracted HTC drivers folder and click on it ONCE and DON'T click any of the sub folders within it. Just the folder that has all the other folders in inside it. ( Example you click: Desktop/HTC Drivers, and NOT: Desktop/HTC Drivers/AMD64)
Now it should detect it and install it.
============================================================
*IF YOU DON'T SEE USB ANDROID DEVICE OR ANDROID DEVICES THEN FOLLOW THIS. IF YOU DO SEE IT THEN IGNORE THIS PART AND SKIP TO STEP 15!*
- Ok you might see a yellow triangle box with an exclamation point next to a device in device manager.
- Press the "+" and it should say like ABD device
- Right click on it and click update driver software.
- With a new window popping up something that says search on my computer something like that
- Make sure that "check sub-folders" is checked
- Now browse and go to the extracted HTC drivers folder and click on it ONCE and DON'T click any of the sub folders within it. Just the folder that has all the other folders in inside it. ( Example you click: Desktop/HTC Drivers, and NOT: Desktop/HTC Drivers/AMD64)
- Now it should detect it and install it.
- Follow step 15 now
============================================================
15) Once installed run the RUU file that you downloaded(*Windows 7, Vista users run as admin and compatibility mode of Windows XP Service Pack 3!*)
16) Make sure your evo is still connected and is still in the fast boot screen
17) Follow the onscreen instruction on RUU
18) When a progress bar(0-100% Bar) shows up on RUU just let it do its thing and DON'T OPEN ANYTHING, OR CANCEL RUU!
19) Make sure your computer DOESN'T go in to Sleep, hibernation mode
20) Once it's done it should reboot and your evo should be working.
Cheers!
Hope I helped!
Click to expand...
Click to collapse
You didn't fix your problem. All you did by running that RUU was unroot your phone. You still have the stock recovery on your phone. So when you try to flash a ROM you will get the same red triangle that you did before. The reason is because you don't have a custom recovery installed that is necessary to flash a custom ROM.
In order to actually fix your problem you need to do what Teh Roxxorz and I suggested.

Concordium said:
You didn't fix your problem. All you did by running that RUU was unroot your phone. You still have the stock recovery on your phone. So when you try to flash a ROM you will get the same red triangle that you did before. The reason is because you don't have a custom recovery installed that is necessary to flash a custom ROM.
In order to actually fix your problem you need to do what Teh Roxxorz and I suggested.
Click to expand...
Click to collapse
Alright, thanks! I'm going to do that later

[Q] Semi-Brick? Stuck on HBOOT SCREEN --> Vol/Power keys NOT working

Hey all, I've officially hit a brick wall.
Basically, I bought a used G2 from an individual and it seemed to be working fine. Took it home and started playing with it a little more before it just froze up on me. Did a battery pull and tried to power on but nothing happened. Tried Vol Down + Power and got the HBOOT screen but the volume keys and power buttons are NOT moving. The only way to shut the phone off is to pull the battery out.
1) Plugging the phone into my laptop makes the accessory plugged in "doo doot" noise, but the phone isn't recognized by Windows 7 (I hadn't even installed HTC Sync yet bc it all happened so fast... did that eventaully, but it's not recognizing the device still)
2) I have downloaded SKD and Fastboot and ABD, but I'm an android noob and since the computer isn't recognizing the phone anyway, I'm not even sure what to do with those programs/commands.
3) I tried installing an RUU? from the HTC DEV website under Kernels (chose the first one as per some other thread suggestions) and get to a point where the program tells me it's incompatible or not for my phone model AFTER having to do a battery pull midway through b/c the phone shuts off and won't power back on, but when I disconnect everything and reconnect it, the program recognizes the phone and eventually reached the "not right software for your device"
4) Downloaded PC10IMG.zip file and tried to flash it, but like I said the volume/power buttons don't move the cursor so I can't select anything.
5) I DO NOT KNOW if the phone had CWM on it since it was second hand and the previous owner knows nothing about the phone really
6) I do not know if the phone was rooted, or at least I don't know how to tell from the HBOOT screen
7) I do not know if the USB function was turned on on the phone before it crashed
8) The screen reads as such:
VISION PVT ENG S-OFF
HBOOT-0.76.2000 (PC10*****)
MICROP-0425
RADIO-26.01.00.17_M2
eMMC-boot
Aug 20 2010, 16:51:01
FASTBOOT (Highlighted in red)
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
BOOTLOADER (Highlighted in blue)
REBOOT
REBOOT BOOTLOADER
POWER DOWN
SOMEBODY PLEASE HELP!!! I've tried everything I know, and searched everything I could think of, but nothing seems to cover my situation... SUMMARIZED:
Phone will NOT go past HBOOT screen, Vol keys not working, and computer not recognizing as USB device when plugged in.

Could be a sign of a busted emmc.
I reckon you should try see if it has clockworkmod reovery, and diagnose the problem from there.
For faster/better help, join #G2ROOT on Freenode irc
-Nipqer

How am I supposed to see if it has CWM on it if I can't get past the HBOOT screen? Also, what exactly is IRC? What am I supposed to do there?

You could also have a corrupt partition. If you cannot use the volume or power keys, you will have to use ADB and hope the phone allowed USB debugging before this happened. Try entering into a command prompt:
Code:
adb devices
If everything goes well you should see something that says "list of devices..." with your phone listed.

How do I do that... total noob here.. please walk me thru the procedure.

open cmd.exe and go to your platform-tool folder (means cd whatever until you are there) then type "adb devices"
or go to platform-tool folder and type "fastboot devices", if your phone shows up type "fastboot oem boot" and maybe your are lucky and your phone boots again
and use the thanks button if people try to help you

Yaaaa, I've downloaded something called adb_fastboot_and_other_tools AND android-sdk_r16-windows and unzipped the folders which are just sitting on the desktop now. I have windows 7 and it's been a loooooooong time since I used the cmd prompt, a bit more help would be great... or if there's a thread somebody could link me to that I missed I'll try that, but so far everything I've read seems to contradict and confuse me further.

Here is a good guide for setting up ADB
HTML:
http://forum.xda-developers.com/showthread.php?t=879701
Follow that guide to set up ADB. Once it is set up run cmd.exe. Use the command "cd" to change to the directory you installed the ADB files (...\android-sdk-windows\platform-tools).
Code:
cd ...\android-sdk-windows\platform-tools
Once in that directory, enter the code I listed in my previous post. That will tell you if you have USB debugging enabled. Once we know if debugging is enabled, we can go from there.

I noticed you joined the irc channel, unfortunately the guy who is normally on at that time decided to have a big one last night.
If you join again, there should be someone there to guide you and help you.
-Nipqer

Okay, I installed SDK, HTC sync, platform-tools and the necessary paths per the instructions on this thread: http://forum.xda-developers.com/showthread.php?t=865685 ( I believe the same one you recommended) and entered the command promt
typed adb devices after the C:\ prompt and it says "List of devices attached" and of course with my luck it's blank... my dear new friends, now what? I feel like I just threw a bunch of cash down the toilet, but I'm hoping somebody can rescue me still
****UPDATE***** Okay after having all of this on the computer, maybe it's random I don't know.... BUT I turned the phone on and all of a sudden it recognized the SD card and started running the PC10IMG.zip file. It made it through the first two steps and then the phone shut off (tried to reboot???) but left I left it alone, and it's not turning back on. What should I do? Leave it completely? Try to turn it on? Do another battery pull and turn it on? I'm so happy yet petrified at this development that I'm scared to f- it up again by mistake...
It gives a screen with
PC10DIAG.zip
No image
PC10DIAG.nbh
No image
PC10IMG.zip
Loading
Then gives:
Parsing...[SD ZIP]
[1] Bootloader
[2] Boot
[3] Recovery
[4] System
[5]Splash1
[6] Splash2
[7] Userdata
[8] TP
[9] TP
[10] Radio_V2
[11] Radio_Cust
Do you want to start update?
<vol up> yes
<vol down> no
*** I choose up and [1] get an OK
[2] - [7] give "Fail-PU"
[8] Bypassed
[9] OK
[10] Currently updating...
AAAANNNDDDD it's changed from ENG S-OFF to SHIP S-OFF... WTF?!?

so, did everything work? or do you still have troubles?

It's been "updating" Radio V2 for the last 30 min or so... not sure if thats normal or not... I'm at least hoping this means the chip isnt fried and maybe i just need to flash the right ROM....?? Whichever that might be...

since its booting on fastboot and vol - and + dont work i think your problem its simpler
i think your trackpad is stuck, its permanently pressed , i had that exact same problem a while ago

Thanks for all the help/suggestions guys... right now I'm getting help on IRC #G2ROOT room...
Finally made some progress and got the RUU splash screen to load via fastboot/bootloader before the low battery error was returned on the phone...
unplugged the cable from the computer to charge it, and got the RUU screen with the typical VISION ENG S-OFF etc info at the top
unfortunately, now the phone does not appear to be charging from the laptop or the wall plug... gonna go to get a new cable, battery and standalone battery charger from the mobile market and go from there.
wish me lucK!

nonione said:
since its booting on fastboot and vol - and + dont work i think your problem its simpler
i think your trackpad is stuck, its permanently pressed , i had that exact same problem a while ago
Click to expand...
Click to collapse
How did you fix that? Just out of curiosity?

I just fixed a G2 that was stuck in hboot. First I noticed that the volume keys will mysteriously start working if you leave the phone on hboot and let the battery drain completely; then plug the power cable in, turn the phone on, and unplug the power cable in hboot. It may take a few seconds but it worked ...at least on the one I'm working on. Select fastboot then plug the USB cable in and issue a "fastboot oem boot" command on the computer. This should get you into the os so you can figure out if it is the trackpad or volume down. The next step is not for the faint of heart and if you ruin your phone it's not my fault or problem, (...don't do this on a phone under warranty) but physically remove the stuck component from the phone. The track pad prys out fairly easily with a small screwdriver. For the volume key, I removed the little button switch thing from the main board ...as best as I could without damaging the board. Find a disassembly write up if you want to see you to get to that.
I went a little crazy with mine and removed the track pad and volume down, but now it boots and works ...except for the removed buttons of course.
Even if you don't want to be selectively breaking parts of the phone, the battery drain to fastboot oem boot may help you diagnose things.
Sent from my HTC Sensation 4G using XDA App

the same issue.
if you're stucked in hboot every time - this is a hardware problem.
check/replace your volume buttons or trackpad/trackball.

that's a hardware problem you got a sticky volume down button. you could try repairing it yourself but it need some desoldering and soldering jobs and with those small parts it's very intimidating.

unknown kindle issues......

ok. this is my very first post....bare with me please. A friend recently gave me his kindle fire to fix. normally im awesome at this sort of thing. what it does is when booted up, first screen says kindle fire, then after 5 seconds or so the next screen has a pink pissed off unicorn and it says team kang under it. KFU says adb online bootmode 4000. when i try any option i get waiting for device, i dont belive any recovery was installed. it hangs on this team kang screen everytime. i have been working on this for almost a week off and on. ive used raw ADB commands, KFU, and the kindle unbricker, all say waiting on device of device not found. i am completly lost. so any help on this is greatly needed asap. thanks. ive looked into recoveries and how to get into them but none r working. theres no firefirefire or anything else that i can find.

When it says waiting for device leave it plugged in and hold the power button down for 20 seconds till its completely powered off and there is no backlight then power it back on check the kfu for status post the results
---------- Post added at 07:11 PM ---------- Previous post was at 07:07 PM ----------
If your seeing a pissed off pink unicorn I would bet fff and recovery are still there
---------- Post added at 07:19 PM ---------- Previous post was at 07:11 PM ----------
My guess is your friend doesn't know how to properly shut the device down wth the new roms and the battery went dead at some point. Or flashed a rom with out doing proper wipes in recovery
---------- Post added at 07:28 PM ---------- Previous post was at 07:19 PM ----------
If it boots to the system get it on a charger pronto or hold the power button down at the fff screen until it turns orange that will put you into recovery put it on the stock wall charger to get some charge to that battery or you'll have more trouble

i agree with everything u guys r sayin. ive left it plugged in for hours and left it plugged in while rebooting it for ADB, checked, rechecked and even reinstalled all drivers for the thing.....im broke and also broke my last spare usb thats able to be a factory cable.....im really at a loss.

I'll reiterate what I've said before...
When your device hangs at or after the boot animation, it's likely the error occurred at the recovery level. It's usually caused by not wiping the necessary data before flashing a new rom, or using a recovery that isn't compatible with the rom you're flashing. Recovery was definitely installed or you would have never have been able to install the Team Kang AOKP rom. Make sure you know how to access recovery in the first place and if you're still unable to, make sure you know whether or not you have a custom bootloader installed.
Based on your description, I'm willing to bet you're unclear whether or not you have either, so more information is needed.
From the second you press the power button until you see the blank screen, what happens and what do you see exactly?

We need more info if your friend flashed aokp via cwm recovery bad
If he didn't make a backup bad

when power is pressed...it says kindle fire.....goes black. screen comes back on and the pissed off lookin unicorn that just flashes team kang. the first screen the wird kindle is white and fire is orange if that means anything.

Did you power it down completely like I suggested holding the power button for 20 seconds

spidro said:
when power is pressed...it says kindle fire.....goes black. screen comes back on and the pissed off lookin unicorn that just flashes team kang. the first screen the wird kindle is white and fire is orange if that means anything.
Click to expand...
Click to collapse
That means quite a bit actually. It means you don't have a custom bootloader installed so access to recovery will be slightly more complicated. You need to issue the adb commands to change your bootmode to recovery and reboot.
Shift+right click on your KFU/tools folder and select "Run In Command...". In the prompt that opens up, enter the following command:
Code:
adb devices
...if it prints a string of numbers you can proceed with changing the bootmode. If you don't see a string of numbers, your drivers need to be reinstalled.
[Edit:] you need access to recovery to fix your problem

yes i have. many times. it was a first thought kinda thing.

DO NOT USE KFU TO INSTALL THE BOOTLOADER. There's an easier and safer way when you have access to recovery.
Just in case you were thinking about it.

When you say right click in the folder and run in cmd I don't get ya soup I can right click all day and have never been given that type of option

Shift + right click

ok...even if i wanted to i cant. all utilities i try to use say either waiting for device or device not found. but what is ur method that u got me thinking about now. oh also i tried adb commands and its the same issue. waiting or not found

spidro said:
ok...even if i wanted to i cant. all utilities i try to use say either waiting for device or device not found. but what is ur method that u got me thinking about now. oh also i tried adb commands and its the same issue. waiting or not found
Click to expand...
Click to collapse
I'm gonna bet you're going to need a factory cable...
http://forum.xda-developers.com/showthread.php?t=1550999
The white/orange kindle fire logo is the stock bootloader and if you can't get the device to boot completely, adb shell is not likely to work either. That eliminates the two possible ways for you to change bootmodes or access recovery.
Unless you want to pry the case open, build/borrow/buy a factory cable.

spidro said:
ok...even if i wanted to i cant. all utilities i try to use say either waiting for device or device not found. but what is ur method that u got me thinking about now. oh also i tried adb commands and its the same issue. waiting or not found
Click to expand...
Click to collapse
Try to pay attention. As I said earlier, if the adb command doesn't return a string of numbers, you need to reinstall your drivers.
You can use this as a reference:
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2

thanks I'll try it when I'm home
I've always just typed CD c:\kindleadb
Then adb devices
Then got the string of numbers thx for clearing that up for me

Ok post were coming in faster than my browser is refreshing. I've looked into prying the case open but I didn't see much for it with windows I saw doing that linux.
Sent from my LG-C800 using XDA

I did notice that the driver ADB composite device...there was a little gray ? But it also said everything is functioning properly.
Sent from my LG-C800 using XDA

Thepooch said:
thanks I'll try it when I'm home
I've always just typed CD c:\kindleadb
Then adb devices
Then got the string of numbers thx for clearing that up for me
Click to expand...
Click to collapse
In order to use adb in Windows, adbwin.dll is needed. It comes with the KFU but some people try to run adb from a different location and get an error. So rather than explain to people how to add the adbwin.dll to their PATH, I just tell them that.

I see thanks though I will surely check

[Q] My Desire HD is bricked, but I can get into bootloader. What can I do?

Dear members of XDA,
My phone froze, and I got the batery out and back in, and when I powered it on, suddenly everything went back to factory settings (Just like when you start the rom for the first time). I was like, what happening...But anyway, I started to set back everything as it was.
When I restarted my phone, the same happened. Factory reset again. The funny part, is that the phone storage shows there's 128MB of total internal space (but there should be around 1gb). Then I decided to try to re-flash my rom I was using (TakTik custom rom - worked fine for months), but I can't do it.
I did full wipe, but when I try to install the rom, it takes 3-4 seconds and it says it's installed successfully, but actually if I go to "Show logs" (In clockworkmod), there was an error saying "No enough space on the phone" (but I did the wipe, as I said).
Now, as I did this, when I try to power on the device, the htc logo shows up, vibrates once as It should, and after a few seconds vibrates 7 times in a row. And it's stuck there.
(By the way, I can still boot into clockworkmod)
What can I do to unbrick my phone?
Any tips?
I appreciate your help very much!

wex28 said:
Dear members of XDA,
My phone froze, and I got the batery out and back in, and when I powered it on, suddenly everything went back to factory settings (Just like when you start the rom for the first time). I was like, what happening...But anyway, I started to set back everything as it was.
When I restarted my phone, the same happened. Factory reset again. The funny part, is that the phone storage shows there's 128MB of total internal space (but there should be around 1gb). Then I decided to try to re-flash my rom I was using (TakTik custom rom - worked fine for months), but I can't do it.
I did full wipe, but when I try to install the rom, it takes 3-4 seconds and it says it's installed successfully, but actually if I go to "Show logs" (In clockworkmod), there was an error saying "No enough space on the phone" (but I did the wipe, as I said).
Now, as I did this, when I try to power on the device, the htc logo shows up, vibrates once as It should, and after a few seconds vibrates 7 times in a row. And it's stuck there.
(By the way, I can still boot into clockworkmod)
What can I do to unbrick my phone?
Any tips?
I appreciate your help very much!
Click to expand...
Click to collapse
Maybe one of your partitions is curropted or something. You can try erasing and formating your boot,system and data partitions from bootoloader.
Just boot your device into bootloader and connect it to your PC.
Now enter these commands one by one.
Code:
fastboot devices
Just to be sure your devices is really connected.Then...
Code:
fastboot erase boot
fastboot format boot
Code:
fastboot erase data
fastboot format data
Code:
fastboot erase system
fastboot format system
If you are able to do this successfully boot into recovery and reflash your rom.
If this doesnt work, try using the stock PD15IMG.zip. Download it, put it on your sdcard.make sure the name is PD15IMG.zip and reboot into bootloader. Once asked wether u want to update press volume up and wait for it to complete. Once its done, Your device would be unrooted.

Actually my PC doesn't recognize my phone. When I connect to it, the "FASTBOOT" title on the phone goes "FASTBOOT - USB" for a second, then goes back to "FASTBOOT", 3-4 times, and stays on "FASTBOOT".
What I am doing wrong?
The "fastboot" command works in command prompt, but it doesn't recognize the device.
Thanks for you help though

Code:
***** AAHK *****
ACE PVT ENG S-OFF RL
HBOOT-0.85.2425
MICROP-0438
RADIO-26.17.14.11_M
eMMC-boot
Apr 12 2011,00:55:45
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
+ClockworkMod Recovery v5.0.2.7
Today when I woke up and tried to power on the phone, it actually booted into the rom, and I got the welcome screen again, but everything was force-closing each second, one force-close after another.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I downloaded Minimal ADB and Fastboot from here: http://forum.xda-developers.com/showthread.php?t=2317790 (version 1.1.3) and installed it, however my PC still doesn't recognize the device.
When I plug it as I choose the Fastboot option, after a few seconds this comes out:
I'm using Windows 8.1 x86 (People say it in the thread it works for them on Win 8 x64 - so that's not the problem).

wex28 said:
Actually my PC doesn't recognize my phone. When I connect to it, the "FASTBOOT" title on the phone goes "FASTBOOT - USB" for a second, then goes back to "FASTBOOT", 3-4 times, and stays on "FASTBOOT".
What I am doing wrong?
The "fastboot" command works in command prompt, but it doesn't recognize the device.
Thanks for you help though
Click to expand...
Click to collapse
Your device is supposed to stay on FASTBOOT USB once its connected to your PC.
Okay then try downloading stock rom PD15IMG.zip and do what i made mention off in my previous reply.
EDIT: Can you take a screenshot of your Pc's device manager?
If you dont know how its done:
Right Click My Computer or This PC=> Then select Manage=> Then on the left of select Device Manager.

Yes, here it is:
Btw, I found this, but there's PD98IMG.zip, not PD15IMG.zip. All PD15IMG's I found are for MyTouch4G. Is this one good?

wex28 said:
Yes, here it is:
Btw, I found this, but there's PD98IMG.zip, not PD15IMG.zip. All PD15IMG's I found are for MyTouch4G. Is this one good?
Click to expand...
Click to collapse
You are right. Its PD98IMG.zip. I used to use a mytouch 4g so it kinda popped out of no where.
Sorry for that.
Its the PD98IMG.zip rather. Download it and put it on the root of your sdcard and boot to bootloader and press volume up and let it update.
EDIT: With the device manager, right click on the enimration failed device and try uninstalling the drivers. Then Unplug and reconnect ur phone.Then try re-installing it.

Installing the PD98IMG.zip took around 5 seconds (it's only 3MB?!), and nothing changed. It said it's successfully done, but everything is the same.
Isn't this dependable on which radio i have? (I have updated it before). And this small file size, I guess it's wrong.

wex28 said:
Installing the PD98IMG.zip took around 5 seconds (it's only 3MB?!), and nothing changed. It said it's successfully done, but everything is the same.
Isn't this dependable on which radio i have? (I have updated it before). And this small file size, I guess it's wrong.
Click to expand...
Click to collapse
You downloaded a recovery or an hboot.
Look, the file should be almost 300mb. Its a stock rom

Okay, I found one. It went good, took a few minutes, and as I rebooted the phone, it vibrated seven times at the htc logo, and stuck there. I pulled out the battery, powered on again, and the old, custom rom's splash screen appeared. It's funny that whatever I do, it goes back to that point where the custom rom starts and the welcome screen appears for choosing the language and all that stuff...
I have no idea what to do. :/

wex28 said:
Okay, I found one. It went good, took a few minutes, and as I rebooted the phone, it vibrated seven times at the htc logo, and stuck there. I pulled out the battery, powered on again, and the old, custom rom's splash screen appeared. It's funny that whatever I do, it goes back to that point where the custom rom starts and the welcome screen appears for choosing the language and all that stuff...
I have no idea what to do. :/
Click to expand...
Click to collapse
From what you are saying, it looks like your data partition is corrupted or has some pretty bad blocks.
If only you could access fastboot from your PC, you could erase the partitions.

I will try it on another PC. What the PC should have installed on it to work? Is this enough?
Thanks a lot for your help and time!

wex28 said:
I will try it on another PC. What the PC should have installed on it to work? Is this enough?
Thanks a lot for your help and time!
Click to expand...
Click to collapse
Yea its cool. Maybe you should try changing usb ports. Try using a USB 2.0 port instaed of 3.0.

No changes. I have read a few topics about Fastboot with Win 8.1 having a lot of issues...So I will have to go somewhere and try it on a Win 7 PC. I'll tell what happened.

Punkyboy, I posted the informations about s-off and all that in previous page Also have installed what you wrote

Yes, but my phone isn't recognized by my pc, as I wrote

Okay, I did that. I typed what u told me. It returns nothing (phone connected on fastboot - but not recognized as I said)

punkyboy906 said:
OK. Now that u installed it,open file location shift right click open cmd here
Sent from my HTC One X using Tapatalk
---------- Post added at 12:46 AM ---------- Previous post was at 12:42 AM ----------
Same principal as flashing ROMs via fastboot
Sent from my Desire HD using Tapatalk
---------- Post added at 12:50 AM ---------- Previous post was at 12:46 AM ----------
While that's being done.. DL the ruu..3.20
Sent from my Desire HD using Tapatalk
---------- Post added at 12:55 AM ---------- Previous post was at 12:50 AM ----------
U there?
Sent from my KFSOWI using Tapatalk
Click to expand...
Click to collapse
wex28 said:
Yes, but my phone isn't recognized by my pc, as I wrote
Click to expand...
Click to collapse
punkyboy906 said:
Did u open via min and?
Sent from my KFSOWI using Tapatalk
---------- Post added at 01:48 AM ---------- Previous post was at 01:41 AM ----------
Listen..right click min adb and chose open file location..when inside file location hold shift right click and chose open cmd here. Then type fastboot devices..
Sent from my KFSOWI using Tapatalk
---------- Post added at 01:52 AM ---------- Previous post was at 01:48 AM ----------
I can't help unless u listen
Sent from my KFSOWI using Tapatalk
Click to expand...
Click to collapse
Listen..from what he is saying. Windows is unable to recognize the device. Windows sees the device as a mulfunctioned device. Hence, fastboot wont be able to reach it.
And i think its problem with windows 8.1. A friend of mine wanted to issue some commands to a sony xperia device. He kept getting such errors but my pc worked fine. So i think you should let him find a windows 8,7 or xp pc and try.

By the way: Tomorrow late afternoon I will be going over to a friend's house to try it on Windows 7, so I will have more informations.

punkyboy906 said:
ok..lol..sorry..that is odd..im runing the same os and it works for me..wierd
Click to expand...
Click to collapse
That is what we have been trying to tell you buddy....:silly::silly:

[Q] [Q ]!HELP! After RUU wildfire s can't boot

I flashed a RUU for wildfire s, everything seems to be fine.
But after it finished and told me your phone will now restart............---------> only the screen turns on and off, on and off.
Nothing else. I cannot go into bootloader or start the phone, no htc logo... nothing =(
I pulled the battery and tried to restart the phone, restarting into bootloader, connecting to fastboot, flashing ruu again, but nothing worked.
No connection to pc at all and no signal on the phone. Only: background light turns on and off, turns on and off.
What can i do ?
Please help me.
I am happy for any replies.
I will pay 20 Euros, if someones solution works.

You might want to take a look at this.
http://forum.xda-developers.com/showthread.php?t=1622178
Hope that helps.

cortezthekiller said:
You might want to take a look at this.
http://forum.xda-developers.com/showthread.php?t=1622178
Hope that helps.
Click to expand...
Click to collapse
Thanks a lot, but i have already known this thread.
The guy, B3NJY, with same problem, could not solve it. At least he sent his phone to repair service.
Maybe someone else knows how to unbrick a softbricked wildfire s.?
I flashed a lot and know how to use fastboot etc., ....
Like i said, backlight is working but nothing else.

appyleptiker said:
I flashed a RUU for wildfire s, everything seems to be fine.
But after it finished and told me your phone will now restart............---------> only the screen turns on and off, on and off.
Nothing else. I cannot go into bootloader or start the phone, no htc logo... nothing =(
I pulled the battery and tried to restart the phone, restarting into bootloader, connecting to fastboot, flashing ruu again, but nothing worked.
No connection to pc at all and no signal on the phone. Only: background light turns on and off, turns on and off.
What can i do ?
Please help me.
I am happy for any replies.
Click to expand...
Click to collapse
I think you flash wrong RUU. Before flash RUU 100% confirm about it. Otherwise you will lost your device. Anyway let's begin...
[WARNING: PLEASE DON'T TRY THIS WITHOUT HAVING GOOD ENOUGH KNOWLEDGE !! BE SURE TO CHOOSE THE RIGHT RUU OR THIS MAY HARM/BRICK YOUR DEVICE !! I AM NOT RESPONSIBLE FOR ANYTHING !!]
Before you start, you will need to set up your computer to properly recognize the device. You probably did this when rooting originally, but just in case... Install SDK tools for Android, Java runtime, and HTC Sync (only for USB drivers). Make sure that HTC Sync is not running in the background when this process is ongoing. To kill that you can use "Task Manager in Windows"
:cyclops: Do step by step: :cyclops:
1. Download the correct RUU for your device from Here and please 100% confirm you are downloading right RUU for your device. Make sure you download a Marvel_C RUU for a CDMA device (no sim card) or a Marvel RUU for a GSM device (uses a sim card)!! Also make sure you get the correct RUU for your carrier.
2. Charge the battery above 80%. If the battery dies during the flashing process, you could hard brick the phone!
3. Run the RUU until the wizard comes up (step 1). While the RUU wizard is open, don't do anything. Just find the temporary folder it created. (Open Explorer in Windows and type %temp% in the navigation bar.) There will be two folders with long encrypted names. In one of them you will find ROM.zip. Copy that and keep it on another location. Close the RUU wizard.
Now, open ROM.zip with 7zip and extract "System, Boot and recovery img's" [.img file/s]. Put it in the location were you've installed Android SDK tools.
4. Boot the phone into bootloader (power off, hold down volume and press power) and highlight FASTBOOT using the volume rocker and pressing power. Then connect the USB cable. You should see FASTBOOT USB.
5. Open a command prompt in Windows and navigate to the folder where you installed Android SDK tools.
Flash the stock recovery, boot, system img's using the following command/s:
step by step
For recovery
Code:
fastboot flash recovery recovery.img
For boot
Code:
fastboot flash boot boot.img
For system
Code:
fastboot flash system system.img
Now go back to device recovery and DO FACTORY RESET and reboot your device.
If everything done perfectly then the phone will booted normally on STOCK ROM! Remember Now bootloader is UNLOCKED but NOT rooted. Don't worry, you can root your device and also install CWM as before.
Hope this method will solve your issue.

Thank you very much testmasterbd =) , for this excellent description.
But..... i can`t start my phone into the bootloader. The phone turns on (only seeing the backlight) and suddenly it turns off (again the backlight). It does this ever and ever again until i pull out the battery . =(
how can i get into the bootloader? volume down and power doesn`t work anymore.
Maybe i can connect the phone to the pc, not via usb but via other contacts. Or is there another way to get the phone into fastboot mode?

Try this
Remove and reinsert the battery [don't press the power button of your device, that's means device should be turned off]
Plug it into a computer via USB cable
Wait and see if the computer detects it
If it does, then - Open a command prompt in Windows and navigate to the folder where you installed Android SDK tools.
Code:
adb devices
See if it shows up or not.
I am not sure about your device get hard brick.
---------- Post added at 10:30 PM ---------- Previous post was at 10:12 PM ----------
I forgot to ask one thing :silly:
Did your device vibrate when you pressed the power button for normal boot?

testmasterbd said:
Try this
Remove and reinsert the battery [don't press the power button of your device, that's means device should be turned off]
Plug it into a computer via USB cable
Wait and see if the computer detects it
If it does, then - Open a command prompt in Windows and navigate to the folder where you installed Android SDK tools.
Code:
adb devices
See if it shows up or not.
I am not sure about your device get hard brick.
---------- Post added at 10:30 PM ---------- Previous post was at 10:12 PM ----------
I forgot to ask one thing :silly:
Did your device vibrate when you pressed the power button for normal boot?
Click to expand...
Click to collapse
You are very friendly.
But i cannot power off the phone. It turns only off if i remove battery =)
When i plug in the usb cable while the phone is off, after some seconds, it turns on - shows its backgound light - and turns off and again on, like a turn signal. no vibration at all.
When i type in windows command adb devices it shows:
C:\android>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
but no device is listed =(
so it should be hard bricked!?
Damn it.
thanks a lot for your help and wasted time.
i am sorry
have a nice day

appyleptiker said:
You are very friendly.
But i cannot power off the phone. It turns only off if i remove battery =)
When i plug in the usb cable while the phone is off, after some seconds, it turns on - shows its backgound light - and turns off and again on, like a turn signal. no vibration at all.
When i type in windows command adb devices it shows:
C:\android>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
but no device is listed =(
so it should be hard bricked!?
Damn it.
thanks a lot for your help and wasted time.
i am sorry
have a nice day
Click to expand...
Click to collapse
If it is then, you need an expert who is capable for JTAG repairs. So find someone in your place. You can get an idea from HERE.
Good luck

testmasterbd said:
If it is then, you need an expert who is capable for JTAG repairs. So find someone in your place. You can get an idea from HERE.
Good luck
Click to expand...
Click to collapse
Yeah, thanks a lot.:good: Luck is what i need. But i don`t think that it will be too easy to repair. :silly:

appyleptiker said:
Yeah, thanks a lot.:good: Luck is what i need. But i don`t think that it will be too easy to repair. :silly:
Click to expand...
Click to collapse
It is don't be frustrated