Develop Bugs

Stuck in WFS Recovery (White HTC Logo)

It all goes like this - I wanted to root my WPS to solve space problem, although, there was a solution for it without rooting, I figured I will be wanting to use some apps that need root access and some roms sooner or later.
So I did a search and found few ways to root my phone. Being a lazy ass I decided to use "the simple" one click solutions - gingerbreak (http://forum.xda-developers.com/showthread.php?t=1044765) or Root Unlocker (http://www.unlockroot.com/) This was no success. Gingerbreak kept rooting when I launched the app, but Root Unlocker displayed " FAIL TO GET SHELL ROOT". I figured that problem with Gingerbeak might be that I updated the software to the latest version -
Then I went on and tried another tutorial(http://forum.xda-developers.com/showthread.php?t=1195275). Everything was fine till I selected Recovery from bootloader. It got stuck with white HTC logo. Took out the battery tried to use newer version of ClockworkMod Recovery, but still was a no-go. I also can't do a factory restart. I can't do it from bootloader or settings > SD & phone storage > Factory data reset. (But could do it at first. Before trying to root my device I did a factory reset once.)
Is there a way to use another Recovery (not CMR) or force Recovery from fastboot? As I found there are some other people that got stuck with similar problem.
Other problems:
My phone doesn't show up in HTC Sync. Althought, when I tipe adb devices in cmd, it shows up. I did turn my AntiVirus off when I installed HTC Sync, but it still didn't display my phone.
Here are my specs:
Model HTC Wildfire S A510e
It shows Marvel in bootloader.
Phone was S-OFF when I bought it.
Android 2.3.5
HTC Sence 2.1
Software number 2.26.401.3
I bought my phone without a contract from a local internet shop. I am from Baltics.
The phone might be somewhere from Europe.
My bet would be Poland. (guessing that manual language is Polish, but I might be wrong)
Thanks in advance.

7axew3ku said:
It all goes like this - I wanted to root my WPS to solve space problem, although, there was a solution for it without rooting, I figured I will be wanting to use some apps that need root access and some roms sooner or later.
So I did a search and found few ways to root my phone. Being a lazy ass I decided to use "the simple" one click solutions - gingerbreak (http://forum.xda-developers.com/showthread.php?t=1044765) or Root Unlocker (http://www.unlockroot.com/) This was no success. Gingerbreak kept rooting when I launched the app, but Root Unlocker displayed " FAIL TO GET SHELL ROOT". I figured that problem with Gingerbeak might be that I updated the software to the latest version -
Then I went on and tried another tutorial(http://forum.xda-developers.com/showthread.php?t=1195275). Everything was fine till I selected Recovery from bootloader. It got stuck with white HTC logo. Took out the battery tried to use newer version of ClockworkMod Recovery, but still was a no-go. I also can't do a factory restart. I can't do it from bootloader or settings > SD & phone storage > Factory data reset. (But could do it at first. Before trying to root my device I did a factory reset once.)
Is there a way to use another Recovery (not CMR) or force Recovery from fastboot? As I found there are some other people that got stuck with similar problem.
Other problems:
My phone doesn't show up in HTC Sync. Althought, when I tipe adb devices in cmd, it shows up. I did turn my AntiVirus off when I installed HTC Sync, but it still didn't display my phone.
Here are my specs:
Model HTC Wildfire S A510e
It shows Marvel in bootloader.
Phone was S-OFF when I bought it.
Android 2.3.5
HTC Sence 2.1
Software number 2.26.401.3
I bought my phone without a contract from a local internet shop. I am from Baltics.
The phone might be somewhere from Europe.
My bet would be Poland. (guessing that manual language is Polish, but I might be wrong)
Thanks in advance.
Click to expand...
Click to collapse
Wrong section mate,its wildfire,not wildfire S.

Wasimk32 said:
Wrong section mate,its wildfire,not wildfire S.
Click to expand...
Click to collapse
This lame. I can't find delete. Thanks though.

[Q] HTC Wildfire S not booting beyond FTC screen.

I have HTC Wildfire S (Telstra NextG Network). I have unlocked bootloader 2 days back and also rooted the phone. After rooting I accidentally uninstalled some of HTC core components with uninstall feature. Now the problem is it shows only HTC screen (green HTC logo) and nothing happens.Its not even showing "Testra NextG network screen" it was showing before this problem.
I have very limited knowledge on how to make my phone functional again. I don't know what is the procedure to get back the "Telstara Next G" package again. I am totally clueless on what to do next. PLEASE HELP ME. :crying:

arnieage said:
I have HTC Wildfire S (Telstra NextG Network). I have unlocked bootloader 2 days back and also rooted the phone. After rooting I accidentally uninstalled some of HTC core components with uninstall feature. Now the problem is it shows only HTC screen (green HTC logo) and nothing happens.Its not even showing "Testra NextG network screen" it was showing before this problem.
I have very limited knowledge on how to make my phone functional again. I don't know what is the procedure to get back the "Telstara Next G" package again. I am totally clueless on what to do next. PLEASE HELP ME. :crying:
Click to expand...
Click to collapse
Did you make a back up in recovery before you rooted?
Tapped out from my sexy nexus 7

heavy_metal_man said:
Did you make a back up in recovery before you rooted?
Tapped out from my sexy nexus 7
Click to expand...
Click to collapse
Unfortunately I didn't make backup in recovery before rooting. I would really be grateful if guided step by step on how to get my phone functional again.

Solved at last.
Finally got help from following thread, so thought I should mention it -
http://forum.xda-developers.com/showthread.php?t=1916045

[Q] Stock HTC One X rebooting constantly - Pls help

Hello all,
I have a stock HTC One X that keeps rebooting.
I am attaching a a picture of the screen that comes up with the three androids starts with ***LOCKED***
Can anyone pls help ? and how can I prevent this from happening ?
I had bought the app 'TASKER', could this have caused it.
Thanks

Do a factory reset, otherwise send it for warranty

Tried factory reset from the ***LOCKED*** screen
Mr Hofs said:
Do a factory reset, otherwise send it for warranty
Click to expand...
Click to collapse
Hi Mr Hofs,
I tried the factory reset from the ***LOCKED*** screen, that did not work it kept rebooting and unfortunately, I do not have warranty.
Thanks

So it boots to the BootLoader Screen, this is a good thing, so its not 'dead' ... yet
As you say you have no warranty, First thing I would try is unlocking it ... your in for a ride
go to http://www.htcdev.com/ create an account, and follow the steps for unlocking the device
The fact that you can get into the boot loader means you should be able to generate your bin code, to unlock the thing
If you do manage to get it unlocked, I would follow the instructions in this forum for flashing a custom rom onto the thing
you start by unlocking, rooting, then CWM Recovery
Once you have that done, flash a custom rom, such as IceColdJelly which is what I use
Hopefully this works for you, Its already busted, no harm in trying
Good luck to you!
EDIT: You may find this useful: http://forum.xda-developers.com/showthread.php?t=2069904

Hardbricked

Hi all,
I have a big problem
I think that my HTC Wildfire got hardbricked, My friend was trying to install custom rom but it went wrong
My wildfire doesnt turn on and my battery is working I tried my battery with a other wildfire so its not the battery..
Is there a way to unbrick my wildfire ??

Wildfire64 said:
Hi all,
I have a big problem
I think that my HTC Wildfire got hardbricked, My friend was trying to install custom rom but it went wrong
My wildfire doesnt turn on and my battery is working I tried my battery with a other wildfire so its not the battery..
Is there a way to unbrick my wildfire ??
Click to expand...
Click to collapse
OK let's figure this out. Gonna need specific information from you.
Is the phone s-on or s-off? If s-off how was this done?
What procedure was used to flash the ROM?
What state is the phone in now? Won't turn on at all, or sits on the HTC screen, or only vibrates?
And has your friend done this before?
Sent from my HTC Desire S using Tapatalk

heavy_metal_man said:
OK let's figure this out. Gonna need specific information from you.
Is the phone s-on or s-off? If s-off how was this done?
What procedure was used to flash the ROM?
What state is the phone in now? Won't turn on at all, or sits on the HTC screen, or only vibrates?
And has your friend done this before?
Sent from my HTC Desire S using Tapatalk
Click to expand...
Click to collapse
I think the phone was s-on
the phone doesnt turn on , no vibrate , no led by charging just nothing..
my friend has flashed many roms but this time it went wrong and he tryed to fix it but i think he hardbricked it now..

Wildfire64 said:
I think the phone was s-on
the phone doesnt turn on , no vibrate , no led by charging just nothing..
my friend has flashed many roms but this time it went wrong and he tryed to fix it but i think he hardbricked it now..
Click to expand...
Click to collapse
Hmmmm. If it was s-on then HTC safeguards would have prevented a hard brick. Is it possible the hardware has been damaged?
Sent from my HTC Desire S using Tapatalk

Try hard reset through youtube
Sent from my GT-S5570 using xda app-developers app

My advice is to flash an RUU and revert back to stock.
This is only because it's hard bricked, plus it happened to me before. I thought to give it a go, and it worked.
After that I just re root my phone, and install CWM recovery, and then flash a new ROM. It's simple
Just follow my leads and it'll work.
P.S Your hardware hasn't damaged at all. Why do users say these things?
1. Download an RUU from the buzz forums
2. Install and revert back to stock with RUU
3. After the process is done, enable adb in settings [Applications]
4. re root your device, and install CWM
5. Flash any custom ROM and follow the instructions 'fully'.
I had to rush this, I hope you understand what i'm saying.
Users if you think i'm wrong then correct me as you wish.
But this all managed to work for me, when my device was hard bricked xD

Stone. Cold said:
My advice is to flash an RUU and revert back to stock.
This is only because it's hard bricked, plus it happened to me before. I thought to give it a go, and it worked.
After that I just re root my phone, and install CWM recovery, and then flash a new ROM. It's simple
Just follow my leads and it'll work.
P.S Your hardware hasn't damaged at all. Why do users say these things?
1. Download an RUU from the buzz forums
2. Install and revert back to stock with RUU
3. After the process is done, enable adb in settings [Applications]
4. re root your device, and install CWM
5. Flash any custom ROM and follow the instructions 'fully'.
I had to rush this, I hope you understand what i'm saying.
Users if you think i'm wrong then correct me as you wish.
But this all managed to work for me, when my device was hard bricked xD
Click to expand...
Click to collapse
Hey @Stone Cold, the confusion people are having here is between hard bricked and soft bricked. A "hard brick" can only occur in 2 situations which are
1: the bootloader is corrupted/damaged/deleted and the device cannot boot. This can Only be fixed by using a JTAG. A ruu will not work as the ruu is flashed by the hboot(bootloader) and if it won't function then its dead.
2: that hardware has been damaged so much that the device cannot physically boot.
Depending on the damage this can sometimes be fixed.
All other forms of "bricking" are "soft bricks" or software bricks. These include bootlooping, trapped at the splash screen etc. These can be fixed as the bootloader and or custom recovery still function. If either of these still function you are not hard bricked. If a ruu worked then you were soft bricked.
Now this user states that his device was s-on so bootloader corruption is massively unlikely as nand protection is still active. This coupled with the owner stating that the device will not boot and shows no signs of life a hardware failure is the most likely option.
Sent from my HTC Desire S using Tapatalk

heavy_metal_man said:
Hey @Stone Cold, the confusion people are having here is between hard bricked and soft bricked. A "hard brick" can only occur in 2 situations which are
1: the bootloader is corrupted/damaged/deleted and the device cannot boot. This can Only be fixed by using a JTAG. A ruu will not work as the ruu is flashed by the hboot(bootloader) and if it won't function then its dead.
2: that hardware has been damaged so much that the device cannot physically boot.
Depending on the damage this can sometimes be fixed.
All other forms of "bricking" are "soft bricks" or software bricks. These include bootlooping, trapped at the splash screen etc. These can be fixed as the bootloader and or custom recovery still function. If either of these still function you are not hard bricked. If a ruu worked then you were soft bricked.
Now this user states that his device was s-on so bootloader corruption is massively unlikely as nand protection is still active. This coupled with the owner stating that the device will not boot and shows no signs of life a hardware failure is the most likely option.
Sent from my HTC Desire S using Tapatalk
Click to expand...
Click to collapse
Oh, so I was wrong.
Thought it was that way though, anyway thanks. This makes more sense now
Cheers

Stone. Cold said:
Oh, so I was wrong.
Thought it was that way though, anyway thanks. This makes more sense now
Cheers
Click to expand...
Click to collapse
That's no problem pal it's good to keep these terms clear, so many people have misinterpreted them in the past. That being said thank you for reminding me of the black screen hboot issue. It's been ages since I've heard of that happening. Its good to keep notes
But back on topic, OP do you or your friend have a working fastboot path? If so try to boot into hboot with volume down and power, wait 30 seconds then push power. Then on the PC issue the command
Fastboot devices
If nothing happens its toast :/
Sent from my HTC Desire S using Tapatalk

European Stock One M8 stuck in HTC logo

I have a european One M8. I turned it off when I got in the plane and after landing it never started back
It gets stuck in the HTC logo.
Some times it moves on and says that "android is updating 165 applications"...and when that finishes it says that Sense Home has crashed and shows the HTC logo again (strangely I can change the volume at that stage ).
I tried to enter Recovery and did a Factory Reset but still nothing. When I select the Recovery option inside that menu I only see an icon of a phone with a red icon, no options to wipe cache etc...
The phone is STOCK, S-ON, no root nothing.
Any suggestions? Can I just reflash the stock rom?

panagath said:
Can I just reflash the stock rom?
Click to expand...
Click to collapse
Possibly. What does it say for OS number on the bootloader screen?
Also, please confirm near the top of the bootloader screen, it says LOCKED (versus UNLOCKED or RELOCKED).

redpoint73 said:
Possibly. What does it say for OS number on the bootloader screen?
Also, please confirm near the top of the bootloader screen, it says LOCKED (versus UNLOCKED or RELOCKED).
Click to expand...
Click to collapse
Hello, thanks for the reply. What I see are the following:
LOCKED
HBOOT - 3.19.0.0000
RADIO-1.29.214500021.12G
OpenDSP-v51.2.2-00593-M8974_F0.1015
OS-6.12.61.4

vagon1 said:
Did you find solution/fix pls ?
I seem to have similar problem.
After Factory Reset phone went into White HTC Screen and stopped. I'm only able to access Bootloader and Stock Recovery now. There is no OS.
OS.1.21.401.1
HTC___001
HBOOT 3.19.0.0000
S-ON
LOCKED
Software Status: Official
I tried to Unlock bootloader. I used Hasoon's tool. I confirmed YES to unload bootloader. But after restart Bootloader is still locked.
I tried to flash boot.img and recovery.img but all FAILS.
I can access the phone via ADB but anything flashing always fails. Tried sideload via ADB in Phone's recovery. But always Fails.
I can't access SD via Recovery, says E: mount fail. Tried to re-format the SD but no result
To me it seems like bootloader is corrupt and seems that without proper hardware I won't be able to do anything...
I spent many hours now and about to give up. Please let me know if I missed anything before I will, sadly, have to try professionals.
Vash
Click to expand...
Click to collapse
Hey, thanks for the reply. I haven't managed to do anything neither did I spend a lot of time on this. I was waiting in case someone could help. Such a shame if the phone is bricked. I do not know if it is worth taking to professionals as its value as a used phone is quite low at the moment...

panagath said:
OS-6.12.61.4
Click to expand...
Click to collapse
Unfortunately, I don't think your version has an RUU (or from a free source, anyway) that would restore your phone fairly easily (assuming the problem is software, and not hardware).
That being the base (no RUU) you can restore by unlocking the bootloader, installing custom recovery TWRP, and restore a stock TWRP backup (stock ROM).
So it is possible to recover (again, as long as it's not a hardware problem). But it's not a short/simple procedure, if you aren't familiar with these terms and methods.

I fixed it by unlocking the bootloader from HTC's website, installed TWRP and then flashed the LineageOS Rom...

panagath said:
I fixed it by unlocking the bootloader from HTC's website, installed TWRP and then flashed the LineageOS Rom...
Click to expand...
Click to collapse
Nice work. It was hard to tell from your post, your level of knowledge. Did you have to learn how to do this, or had prior experience unlocking bootloader, TWRP, etc?
I was on vacation/holiday last week, and not on XDA. So sorry it took so long to get back to you.

redpoint73 said:
Nice work. It was hard to tell from your post, your level of knowledge. Did you have to learn how to do this, or had prior experience unlocking bootloader, TWRP, etc?
I was on vacation/holiday last week, and not on XDA. So sorry it took so long to get back to you.
Click to expand...
Click to collapse
Thanks for the help. I have had previous experience installing custom ROMs on HTCs
(HTC Diamond, Wildfire, Desire, Desire HD, Desire S, One S, One X and now the One M8 )
I was just hopping I could get an easy solution without having to go through the whole process