Develop Bugs

A100 Brick....cannot find answers!!!

Hey all,
This is my official "first" post. I rooted the A100 while it was on Honeycomb. Everything was fine. I got an ota update and updated to 3.2.1. Rooted it again and everything SEEMED fine. I got the ota ICS update and the tab would hang at the green android and give me a "!" after about 5 seconds. I fiddled with the update for a while and took it to a friend that knows more about this than I. He proceded to try and unlock the bootloader with the ICS unlock, while it was on Honeycomb. Now my tab is bricked with the green Acer logo, it will not boot. I have no access to recovery, fastboot, adb, bootloader. I can get it to APX mode. I tried to NVflash it, but when I use any NVflash commands, device manager just kicks my device off and the command doesnt execute. I cant use the EUU, because it keeps telling me my CPU ID is wrong, even though I KNOW its correct. I have searched the forums and sent PM's to everyone that has experienced this and fixed it, but no one has answered. Could SOMEONE, ANYONE, PLEASE help!!!!!!
Thank you in advance!!!!!
Cory

Really
No one out there has any insight into this? Ive seen that there are a couple people in the forums that have fixed this issue, but in their posts it doesn't really describe how because they were being PM'd. PLEASE, any info would be GREATLY appreciated!!!!

cooki3monst3r77 said:
No one out there has any insight into this? Ive seen that there are a couple people in the forums that have fixed this issue, but in their posts it doesn't really describe how because they were being PM'd. PLEASE, any info would be GREATLY appreciated!!!!
Click to expand...
Click to collapse
Try using the search on the forums, it's been discussed several times and the only way to fix it currently is to send it in to acer for repair and hope they replace it with a different board that the euu works with. Please stop posting this same question when its been asked repediatly already there are 4 separate posts with this same question being asked by 3 different people
Sent from my MB860 using XDA

OK
I have searched the forums for the past I cant tell you, how many hours. I have looked and looked and in one forum, it looks as though someone fixed this issue because they were able to somehow get to fastboot. I would not just post this on here without my resources having been exhausted. The problem is, in EVERY FORUM I CHECK, the answers and such are PM'd to each other! I have even PM'd the people that seemed to get something working.......to which I have received no reply. Ive seen the posts on this, Ive tried NVflash, I tried to boot holding EVERY combination of buttons, EUU doesnt work, because of the CPUID being "wrong". I have done my research, sir. Please PM me if you think I have wronged you in some way by posting something in a forum meant for helping others, instead of putting me on blast because you think Ive been lazy and not searched the forums.

cooki3monst3r77 said:
No one out there has any insight into this? Ive seen that there are a couple people in the forums that have fixed this issue, but in their posts it doesn't really describe how because they were being PM'd. PLEASE, any info would be GREATLY appreciated!!!!
Click to expand...
Click to collapse
can you boot into fastboot mode?

dunno
Im not sure if I can get to fastboot. There are a couple of people that, it seems, could get to fastboot and APX. Could you direct me on the ways of getting to fastboot? Adb doesn't work for me. Only APX mode. It boots to the green Acer logo. When I try to get to recovery (VOL+PWR), it hangs and will not go to recovery.
Sorry for being short earlier, Im just so frustrated with this. Ive been researching this issue for DAYS. (NVflash, APX, bootloaders, adb, etc....) No progress on it. I even have a DEV friend who may try to decompile the EUU and see if he can force push it to the tab....he just has to find the time. lol

done
At this point Im willing to use the tablet for target practice. If anyone wants it, to mess around with or whatever, you can pay for shipping and keep it.

cooki3monst3r77 said:
At this point Im willing to use the tablet for target practice. If anyone wants it, to mess around with or whatever, you can pay for shipping and keep it.
Click to expand...
Click to collapse
Well that is a hard offer to pass up...
Sent from my LG-P999 using Tapatalk 2

If you and orient fastboot and has the bootloader on the A200 prepare to unlock and install cwm recovery and is saved
hard-resset first try with the buttons
1 tablet off completely its
2 lock button on the screen is right
3 hold down power and volume - that is left
4 when the tablet vibrate release the power button and quickly move the screen lock button to the right and left without releasing the volume -
5 your tablet should start
but it works I say and try fastboot

I dont know if the boot loader is locked or not. I cant flash cwm because I cant get to recovery/adb/fastboot/etc. I tried the hard reset and the tablet hangs on the green Acer screen after reboot. NVflash doesnt work because ???, device manager just drops it when I try to send commands and nvflash says something about not being able to write to usb. And yes, I have the Nvidia apx drivers installed.

peporras said:
1 tablet off completely its ( holding it in landscape)
2 lock button on the screen is right
3 hold down power and volume - that is left
4 when the tablet vibrate release the power button and quickly move the screen lock button to the right and left without releasing the volume -
5 your tablet should start in fastboot mode
are you able to get fastboot going?
if so try to flashing a custom recovery from thor 17 ( google it)
i had a problem like this and was able to fix it by flashing the leak isc rom through this recovery. it might be worth a try.
Click to expand...
Click to collapse

Bricked Device after partially using HTC ONE V AIO Kit by Hasoon2000

Hello everyone,
After unlocking my HTC One V PrimoU (simcard version) bootloader succesfully, flashing clockworkmod succesfully using HTC ONE V AIO Kit by Hasoon2000 my phone rebooted one last time and after that turned into a brick.
- Holding Power 30 seconds: Doesn't respond / no LED
- Plugging in Power: Doesn't respond / no LED
- Plugging in PC: Doesn't respond / NO LED / Unable to recognise QHUSB_DLOAD
I've searched through the forum's and I'm not sure if I did the Power+VolumeUP combination.. but yea can't find any more information and I think my only option is to bring it back to my carrier-store with some "inconvenient excuse".
QUESTIONS:
- Am I able to repair this on my own?
- Am I able to bring this to my carrier to get it fixed without me getting into trouble? (Are my actions "easily" traceable?)
- What kind of "inconvenience" could have caused this?
- What did I do wrong?
Kind Regards,
Narayan
HTC One V | PrimoU
Vodafone NL

repair centre time dude, it's in the wise words of myself ****ed

Aphromode said:
Hello everyone,
After unlocking my HTC One V PrimoU (simcard version) bootloader succesfully, flashing clockworkmod succesfully using HTC ONE V AIO Kit by Hasoon2000 my phone rebooted one last time and after that turned into a brick.
- Holding Power 30 seconds: Doesn't respond / no LED
- Plugging in Power: Doesn't respond / no LED
- Plugging in PC: Doesn't respond / NO LED / Unable to recognise QHUSB_DLOAD
I've searched through the forum's and I'm not sure if I did the Power+VolumeUP combination.. but yea can't find any more information and I think my only option is to bring it back to my carrier-store with some "inconvenient excuse".
QUESTIONS:
- Am I able to repair this on my own?
- Am I able to bring this to my carrier to get it fixed without me getting into trouble? (Are my actions "easily" traceable?)
- What kind of "inconvenience" could have caused this?
- What did I do wrong?
Kind Regards,
Narayan
HTC One V | PrimoU
Vodafone NL
Click to expand...
Click to collapse
First, I would remove what you did right before that. I will put 100% certainty and my rep on the line it wasn't specifically that mod that made it happen. And its just ****ty to call out a rom for a brick. It was going to happen even if you just rebooted. Ask Lloir. Its a known issue with the primou phones. Check development for a possible fix. It might work and it might not.

jmztaylor said:
First, I would remove what you did right before that. I will put 100% certainty and my rep on the line it wasn't specifically that mod that made it happen. And its just ****ty to call out a rom for a brick. It was going to happen even if you just rebooted. Ask Lloir. Its a known issue with the primou phones. Check development for a possible fix. It might work and it might not.
Click to expand...
Click to collapse
Thank you for your reply. I'm not blaming anyone/anything I'm just explaining my steps; and it's all very frustrating because yea.. I just followed the steps because I wanted to install the CM9-rom on my phone..

Aphromode said:
Thank you for your reply. I'm not blaming anyone/anything I'm just explaining my steps; and it's all very frustrating because yea.. I just followed the steps because I wanted to install the CM9-rom on my phone..
Click to expand...
Click to collapse
Its not very easy to repair ur phone by yourself. Try the fix added in the one v general section. If that doesnt work out, go to the htc support centre and
-Pretend you dont know what rooting means
-act like and elderly grandmom who just got her hands on a smartphone
-If they still keep on asking how it became bricked, say that u were trying to take a snapshot and most probably kept on pressing vol up+power
If they guy is convinced that you did not try to root, he'll replace urs for free
Cheers

soham_sss said:
Its not very easy to repair ur phone by yourself. Try the fix added in the one v general section. If that doesnt work out, go to the htc support centre and
-Pretend you dont know what rooting means
-act like and elderly grandmom who just got her hands on a smartphone
-If they still keep on asking how it became bricked, say that u were trying to take a snapshot and most probably kept on pressing vol up+power
If they guy is convinced that you did not try to root, he'll replace urs for free
Cheers
Click to expand...
Click to collapse
they will not replace it for free. they will try and see why you have it bricked. if the system partition is untouched, you are somewhat f**ed because then you will need to pay for the service.
if they cannot see anything inside, all the partitions are fried, they will replace the mainboard. not the whole phone.

...another one bites the dust...
First off, let me just clarify that this is clearly a fookup on HTC's part primarily.
That being said, this forum needs to have more thorough and consistent WARNINGS about this issue on EVERY post that has to do with unlocking/rooting/flashing your HTC ONE device.
No guides I read here mentioned specifically of this issue when instructing you to hold the power and volume buttons together.
It's just unbelievably awesome to see this post here after going through the process of bricking my phone 5 minutes ago. We have a full thread dedicated to this, yet none of the custom ROM guides refer to it.

sunnyata said:
...another one bites the dust...
First off, let me just clarify that this is clearly a fookup on HTC's part primarily.
That being said, this forum needs to have more thorough and consistent WARNINGS about this issue on EVERY post that has to do with unlocking/rooting/flashing your HTC ONE device.
No guides I read here mentioned specifically of this issue when instructing you to hold the power and volume buttons together.
It's just unbelievably awesome to see this post here after going through the process of bricking my phone 5 minutes ago. We have a full thread dedicated to this, yet none of the custom ROM guides refer to it.
Click to expand...
Click to collapse
The key combo "brick" isn't really a brick. So go look through development forum for a post by globatron for unbricking. You are in a engineering state. His tool will get you out of it
Sent from my One V using xda premium

Has anyone else experienced dead one x in APX Mode

Hi all, I've began to realise that no one can help get me out of APX mode on my one x but after reading stories about the Asus Transformer battery reset and LG optimus reboot from apx I am convinced there must be a way to get the device to reboot into bootloader or perhaps flash a boot.img to reboot the phone.
I am just wondering if anyone else has experienced apx and what they did about it......?
And if anyone can explain what may have happened to cause the phone to simply go dead and stay stuck in APX mode. A bad boot.img, overheating(although it didn't seem to be hot)ect....?
If I was to have the phone repaired where would I be able to do that in the uk apart from the network and HTC?
Does anyone think that removing and replacing the battery will allow the phone to boot normally?

My phone is also in APX mode after a strange crash during flashing a ROM and a strange kernel flash...

what is apx mod?

Dam how many people are in apx does it still boot into apx if you hold the power and volume down without letting go until bootloader
Sent from my HTC One X using xda premium

joewong1991 said:
Dam how many people are in apx does it still boot into apx if you hold the power and volume down without letting go until bootloader
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Muy phone does not boot at all, when I plug into the pc it says apx in device manager, what ever I try it will not boot

a friend of mine had the same after playing for an hour or so.
The Device won't boot up at all and only showed apx in device manager.
Send it to htc or wait till there's a solution for that.

APX mode == NVFlash recovery mode. A low-level recovery mode that allows you to flash the whole device. There's no known way of getting to this mode, but several people are reporting it and suggesting a faulty device is to blame.
You can try using NVFlash utility for Tegra 3 to find out more. Fetch partition table, download partition data, flash new data etc. Search forums for more info on nvflash.
But, chances are that your phone is just busted.

HOX in APX mode
I have HOX indicating APX in device manager. Just tu add one more sad story with short description of attempts to solve it.
I have two HOX one is ok. Both handesets diassembled fixed WIFI issue changed battery from good one to bad with no results, when replaced motherboard everything works well but that is half of the phone. APX is still appearing in device manager when only motherboard connected.
Tried all other methods nvflash, drivers etc as others with no results. Hope something will leak soon.

I also bought two, one for my son. His has the same problem. It won't boot but shows in devices as apx device on the pc.
Took it to my supplier four weeks ago and after many emails they tell me it is fixed but they wont send it for another week.
It took ages to get it delivered the first time. Last time I buy gadgets online. Any other Aussies get one from Topbuy or Kogan and had trouble with warranty?

Sadly mine got stuck in apx mode and I returned it to my carrier 3UK. They said it was due to me loading illegal software on it and demanded I pay them £76 to repair it. So I want my phone back now and agreed to pay it on my next bill, I will dispute it when I get it back. Looks more and more like hardware to me.

APX Mode is supposed to allow access to an nVidia based device if it is soft-bricked, but unlike other nVidia based devices such as the ASUS Transformer TF 101/201 or LG Optimus 2X, it is impossible to revive an HTC One X that is stuck in APX Mode. No-one has a guaranteed way of getting into APX mode, let alone getting out of it. As you may or may not know, the One X is very locked down and restricted. The bootloader is locked, and it's very hard to get updated stock ROMs as RUUs. Surprisingly, it is easier to get a custom ROM working through fastboot/recovery than it is to get a stock ROM working due to all the restrictions.
In fact, the One X is so locked down that even NVFlash cannot access it in APX Mode.
For example, if you try to send any commands to a One X using NVFlash, all you'll get in return is this error due to its heavy restriction:
Code:
Command send failed (usb write failed)
I have wasted 5 hours trying to revive a One X stuck in APX Mode, only to discover that it is impossible. Even HTC themselves can't fix a One X stuck in APX Mode - that is why they accuse you of installing illegal software, but in truth they have to replace the motherboard because they locked themselves out of their own hardware. This is a result of flawed internal hardware design.
So in short, don't think just because a computer can dectect the One X means that you can still save it. There is a barrier in the device itself that is above software-level.

Ah yes, this "news" is not new ...... its a known problem for several months already.
But thank you for sharing
A search would have come up with several threads, this is one of them

i am trying to fix a one x stucked at apx mode :/...are there any news about this issue?? probably a fix?

http://forum.xda-developers.com/showthread.php?t=2326009

Stock HOX - now in APX mode - help

Hi guys,
Some time ago, my HOX (everything stock) decided to loop boot and entering by itself in the bootloader menu. I tried to fiddle around with the options but the phone kept loop booting/[email protected]/enter bootloader. I left it discharge for some time (about 2 months I think). Now it won't power on (no LED, black screen). Connected to the PC, it shows up as 'APX' in device manager.
What are the steps to getting it working again?
Thanks in advance.

varzmaster said:
Hi guys,
Some time ago, my HOX (everything stock) decided to loop boot and entering by itself in the bootloader menu. I tried to fiddle around with the options but the phone kept loop booting/[email protected]/enter bootloader. I left it discharge for some time (about 2 months I think). Now it won't power on (no LED, black screen). Connected to the PC, it shows up as 'APX' in device manager.
What are the steps to getting it working again?
Thanks in advance.
Click to expand...
Click to collapse
Take a couple of deep breaths and follow the RUU-instructions you can find in several topics here. The empty battery shouldn't be a problem. After one of my misflashes (yep, test some and screw it up sometimes ) i leave my phone bootlooping when charging. Leave it so for a night and de the battery will be charged enough to pull you trough the RUU-process.

Htc one x apx
bazs2000 said:
Take a couple of deep breaths and follow the RUU-instructions you can find in several topics here. The empty battery shouldn't be a problem. After one of my misflashes (yep, test some and screw it up sometimes ) i leave my phone bootlooping when charging. Leave it so for a night and de the battery will be charged enough to pull you trough the RUU-process.
Click to expand...
Click to collapse
Probably you will wait until somebody find or some info leak about Tegra3 NVFLASH for HTC ONE X. I have two HTC ONE X one is in APX mode
i replaced motherboard from this good one to bad and it was working, but that is expensive solution.
Up to now it is not possible to NVFLASH new bootloader (hboot) without HTC service. Hope something will apear soon.
Anyway i suspect that due to overheating there is some hardware fault, mine unit was in the car during somertime and i noticed to late
that position is not good. And as other people reported several force close, and going to boot loader itself then all stops just APX appeared
in device manager, also when you take off motherboard and connnect it to computer (only motherboard it also indicate APX after some minutes.
Until good news . bye!

varzmaster said:
Hi guys,
Some time ago, my HOX (everything stock) decided to loop boot and entering by itself in the bootloader menu. I tried to fiddle around with the options but the phone kept loop booting/[email protected]/enter bootloader. I left it discharge for some time (about 2 months I think). Now it won't power on (no LED, black screen). Connected to the PC, it shows up as 'APX' in device manager.
What are the steps to getting it working again?
Thanks in advance.
Click to expand...
Click to collapse
If you phone boots into APX mode its because of a hardware failure that causes the firm/software to crash.
Theres no way to fix it yourself without replacing hardware stuff. Your Hoxis still under full warranty, send it for repair.

maybe this one will help you .. i manage to get out in apx mode by holding volume + button then plug charger .. ) then red light comes out .. leave for a full night .. then fry to open it . it will bootloop because you are in a bootloop state then try to access fastboot .. ) hit thanks if i helped you ...
Sent from my GT-I9100 using xda premium

HOX APX
I tried vol+ and power connect as suggested but no any indication, except APX disappear and unknown device appear, then on power on APX appear again. But tks anyway .

Htc locked apx mode, hence if you can access it either your board is fully discharged(rare cases) or something is burnt and it cannot be fixed without hardware replacement.
Sent from my HTC One X

j to the 4n said:
If you phone boots into APX mode its because of a hardware failure that causes the firm/software to crash.
Theres no way to fix it yourself without replacing hardware stuff. Your Hoxis still under full warranty, send it for repair.
Click to expand...
Click to collapse
No its not.
APX mode is the first mode the device will ever see, it is the first part of its life and the APX mode is used to flash software onto it. Its like flashing the boot.img etc but at the very start of the devices life. Hense why it can be flashed without an unlocked bootloader or rooted etc.
APX mode isnt well known with the HOX however, and HTC will not help at all, as they know this is a work around from unlocking the phone to flash, which voids their warranty.
If your in APX mode, I would try and get the RUU for your device and run that.

Wilks3y said:
No its not.
APX mode is the first mode the device will ever see, it is the first part of its life and the APX mode is used to flash software onto it. Its like flashing the boot.img etc but at the very start of the devices life. Hense why it can be flashed without an unlocked bootloader or rooted etc.
APX mode isnt well known with the HOX however, and HTC will not help at all, as they know this is a work around from unlocking the phone to flash, which voids their warranty.
If your in APX mode, I would try and get the RUU for your device and run that.
Click to expand...
Click to collapse
I know that the APX Mode is the lowest software level of our devices, its more or less the BIOS of Android/Linux...
But do you know why NO one managed to boot into APX Mode on the HOX so far...WITHOUT a broken device? (-:
If you're following the Hox forums you will notice that there are sevearl threads about hox that are stucking in apx mode and once you are in apx mode their isnt a way yet to bring it back to life again. Often you will read as well, that the Hox behaved werid before, it was dropped, battery complety drained, or whatever...so i'm 99% sure that the reason that the Hox booted into APX Mode is a hardware defect/bug that leads the firmware to crash and boots the device into APX Mode.
..and no just running a RUU wont work. Also installing the correct nvflash drivers for you desktop OS wont help.
Your Desktop PC wont recognize your Device anymore...at least not in the state that is required to falsh it. It will show that your device is in APX mode..and here you are definatly not able to run a RUU.

Bump. Having the exact same problem. Any help appreciated:crying:

coolsid1234 said:
Bump. Having the exact same problem. Any help appreciated:crying:
Click to expand...
Click to collapse
Bump what, have you read the thread ?
APX = dead hox ! Get it fixed. No other real solution available.

Mr Hofs said:
Bump what, have you read the thread ?
APX = dead hox ! Get it fixed. No other real solution available.
Click to expand...
Click to collapse
anyone knows what part of the motherboard or what chipset needs to be replaced to escape the apx problem/

All the mainboard should be replaced
Sent from my HTC One X using Tapatalk 4

How can you solder new processor on motherboard without dammiging board. I saw site where they sell processors for HOX . Be carefull when buying used motherboards on ebay or elsewere, I did 2 times and both useless.
Sent from my GT-I9500 using XDA Premium 4 mobile app

[Q] htc wildfire s boot loop problem

So i was trying to root my phone and now i won't start, can't even go to bootloader menu or so. when i'm pressing the power up button its just flashes and then shuts down. It loops so frequently that even my pc won't recognize it. What i did to the phone is this:
//androidforums.com/wildfire-s-all-things-root/502772-guide-how-update-htc-wildfire-s-marvel-a510e-gsm-software-version-2-3-5-a.html
i tried to flash a new 2.3.5 to it but now it wont do anything.
Is there any ways to fix this or should i just send this to graveyard :good:

a bit more info plz
alemale said:
So i was trying to root my phone and now i won't start, can't even go to bootloader menu or so. when i'm pressing the power up button its just flashes and then shuts down. It loops so frequently that even my pc won't recognize it. What i did to the phone is this:
//androidforums.com/wildfire-s-all-things-root/502772-guide-how-update-htc-wildfire-s-marvel-a510e-gsm-software-version-2-3-5-a.html
i tried to flash a new 2.3.5 to it but now it wont do anything.
Is there any ways to fix this or should i just send this to graveyard :good:
Click to expand...
Click to collapse
I think you might have soft bricked your phone. Search the forum how to unbrick a soft-bricked phone. That might help
Are you positive that your WFS is GSM -marvel-a510e ?
Also ,Could you be a bit more specific about what happens when you try to go to boot-loader mode or when you try to boot it.
As in the provided link, did you have to perform procedure 3 or did you perform procedure 2 and was it working? A bit more info about what you did could help others analyze the issue

rishr4 said:
I think you might have soft bricked your phone. Search the forum how to unbrick a soft-bricked phone. That might help
Are you positive that your WFS is GSM -marvel-a510e ?
Also ,Could you be a bit more specific about what happens when you try to go to boot-loader mode or when you try to boot it.
As in the provided link, did you have to perform procedure 3 or did you perform procedure 2 and was it working? A bit more info about what you did could help others analyze the issue
Click to expand...
Click to collapse
At the link i did the procedure 1 because my phone couldn't update to 2.3.5 so i tried to update it that way.
when i start the phone it just flashes it's screen and then goes off. it doesn't show htc logo or anything it just flashes some pixels. the loop is so frequent that it happens in 3 sec. Even if i try to start the phone by pressing "volume -" key and "power" key it does same thing, just loops every 3 sec.
I have tried to find a way to fix this but it seem that there is nothing to do because i can't boot to recovery. Is there a way to put the phone to recovery in other way or is here a way to make factory install?
It's really hard to do anything to this phone because my pc won't recognize it in any possible ways and it won't boot to recovery mode.
Do anyone know if i split the phone in to pieces and then manage to boot it or find the system memory and change files in there.

alemale said:
At the link i did the procedure 1 because my phone couldn't update to 2.3.5 so i tried to update it that way.
when i start the phone it just flashes it's screen and then goes off. it doesn't show htc logo or anything it just flashes some pixels. the loop is so frequent that it happens in 3 sec. Even if i try to start the phone by pressing "volume -" key and "power" key it does same thing, just loops every 3 sec.
I have tried to find a way to fix this but it seem that there is nothing to do because i can't boot to recovery. Is there a way to put the phone to recovery in other way or is here a way to make factory install?
It's really hard to do anything to this phone because my pc won't recognize it in any possible ways and it won't boot to recovery mode.
Do anyone know if i split the phone in to pieces and then manage to boot it or find the system memory and change files in there.
Click to expand...
Click to collapse
Even if you want to unbrick the device using back-toback tool , you need to enter the boot-loader mode.
Even for other ways, still it needs to be detected by the PC so that we can pass commands using ADB.
Sorry Dude, I can't help much either I am new to this myself. But i hope somebody here will definitely help you
2. There is a possibility that you could "brick" or bootloop your phone. There are two types of brick: soft (recoverable) and hard (non-recoverable). With a soft brick, the phone will not boot or keeps rebooting ("bootloop"), but it can be started in bootloader mode which allows repair of the ROM. With a hard brick, the phone won't even boot into bootloader after holding the power button for 10 seconds and the phone must be returned to HTC for service.
Click to expand...
Click to collapse
Have you unlocked your Boot-Loader from HTC Dev? Also, you need to install a recovery tool in order to boot into recovery. If you have done only the steps mentioned in the
PROCEDURE 1
Click to expand...
Click to collapse
then you haven't unlocked the boot loader and no recovery is also installed (I believe) . In this case, I think this is a hard-brick(Correct me if am wrong) which is impossible to recover . Anyways, we shall await other replies from DEVs here in the Forum.

rishr4 said:
Even if you want to unbrick the device using back-toback tool , you need to enter the boot-loader mode.
Even for other ways, still it needs to be detected by the PC so that we can pass commands using ADB.
Sorry Dude, I can't help much either I am new to this myself. But i hope somebody here will definitely help you
Have you unlocked your Boot-Loader from HTC Dev? Also, you need to install a recovery tool in order to boot into recovery. If you have done only the steps mentioned in the then you haven't unlocked the boot loader and no recovery is also installed (I believe) . In this case, I think this is a hard-brick(Correct me if am wrong) which is impossible to recover . Anyways, we shall await other replies from DEVs here in the Forum.
Click to expand...
Click to collapse
I tried to unlock the bootloader but it wanted 2.3.5 so i tried to install the new version. now it can't do anything. Well this didn't broke my heart because the phone is pretty worthless . now i have to buy new phone sooner than i planned but still all help is still accepted.

Hi, exactly the same for me : I bought the phone 2 years ago and immediately unbranded it with a goldcard, but never tried to unlock it because it was my wife's and I didn't want to risk anything.
Now she got a new phone, I wanted to play a little with the Wildfire S ^^.
In order to unlock the phone on htcdev I had to update it from 2.13.401.2 to 2.13.401.3, with RUU because can't update with OTA (different CID), with goldcard inside.
After the RUU finished, it says "congratulations everything went well", but actually the phone does not boot, stocked in a loop "quick flash / turns off", can't access bootloader, no USB detection for ADB.
Can't send it to HTC because the 2 years warranty is expired, how ironic ! :laugh:
So... if anyone does know or see any trick that could help to boot anything on this "seems to be hard-bricked" kid... huge thanks to you