Develop Bugs

[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

[Q] ANOTHER "Stuck on White HTC Screen"

ANOTHER "Stuck on White HTC Screen" however, I am not: Rooted. UNLocked. S-OFF or custom ROM'ed.
I am stock ROM, UNrooted, locked, S-on.
All the other threads seem to be something different than mine and either UNlocked, S-Off or ROM Customized so, here I go.
After a factory reset, and a few days I was all set to install frivolous stuff like games. So, off to the play-store to shop. I started one donwload/install and then another install and another and another another another..... seems that you can download/install too many things at one time because, that is when my screen went blank,
I hit the power button to wake it up and it wouldn't.
I held the power button down to boot it back up.... and it didn't.
Removed the battery and it started (whew). Then the starting stopped.
It stuck on the White HTC Screen and has been there since.
I tried the (Vol Down - Power ON) factory reset and it doesn't do anything except lock it up with no screen change and no button movement/control either.
Previously to all of this I had to order a new charging/data port because the existing one only charged. The new port came in and was installed but, I can't get any ROM to load (via ADB). I think this is because I am either locked or s-on or not rooted.
If you haven't figured this out, let me put this simply:
I dunno what I am doing with Droid OS's or phones and need someone to tell me what to do. Step 1, 2, 3, etc I have no idea which steps come in which order OR.... how do to the steps.
I'd say I am a noob but, that is a tad too advanced for me at this point
Here's my set up that I am hoping someone can help me with.
(Verizon) HTC Droid Incredible 2 (ADR6350)
*** LOCKED ***
VIVO_W XB SHIP S-ON RL
HBOOT-0.98.0000
RADIO-1.09.01.1111
eMCC-boot
Jul 10 2011,12:39:36
Since I have already ordered a replacement (and had to send that one back as defective) I can do this recovery any-which-way but really don't want to brick the ol' gal if I can avoid it.
THANKS! ! !
p.s. - If I missed the post/thread that has my problem and configuration, please don't hesitate to link me. thx
</Edit> I also stuck the ROMs that I was trying to use ADB with on the SD card as PG32img.zip's which didn't work. But, I dunno what is and is not supposed to be inside of that file either so..... (at least the data port is working now)<Edit>

Question
avibp said:
I am not: Rooted. UNLocked. S-OFF or custom ROM'ed.
Click to expand...
Click to collapse
Are you looking to Unlock, S-OFF or custom ROM? Or am I correct in assuming you want to keep your phone as stock as possible?

avibp said:
ANOTHER "Stuck on White HTC Screen" however, I am not: Rooted. UNLocked. S-OFF or custom ROM'ed.
I am stock ROM, UNrooted, locked, S-on.
All the other threads seem to be something different than mine and either UNlocked, S-Off or ROM Customized so, here I go.
After a factory reset, and a few days I was all set to install frivolous stuff like games. So, off to the play-store to shop. I started one donwload/install and then another install and another and another another another..... seems that you can download/install too many things at one time because, that is when my screen went blank,
I hit the power button to wake it up and it wouldn't.
I held the power button down to boot it back up.... and it didn't.
Removed the battery and it started (whew). Then the starting stopped.
It stuck on the White HTC Screen and has been there since.
I tried the (Vol Down - Power ON) factory reset and it doesn't do anything except lock it up with no screen change and no button movement/control either.
Previously to all of this I had to order a new charging/data port because the existing one only charged. The new port came in and was installed but, I can't get any ROM to load (via ADB). I think this is because I am either locked or s-on or not rooted.
If you haven't figured this out, let me put this simply:
I dunno what I am doing with Droid OS's or phones and need someone to tell me what to do. Step 1, 2, 3, etc I have no idea which steps come in which order OR.... how do to the steps.
I'd say I am a noob but, that is a tad too advanced for me at this point
Here's my set up that I am hoping someone can help me with.
(Verizon) HTC Droid Incredible 2 (ADR6350)
*** LOCKED ***
VIVO_W XB SHIP S-ON RL
HBOOT-0.98.0000
RADIO-1.09.01.1111
eMCC-boot
Jul 10 2011,12:39:36
Since I have already ordered a replacement (and had to send that one back as defective) I can do this recovery any-which-way but really don't want to brick the ol' gal if I can avoid it.
THANKS! ! !
p.s. - If I missed the post/thread that has my problem and configuration, please don't hesitate to link me. thx
</Edit> I also stuck the ROMs that I was trying to use ADB with on the SD card as PG32img.zip's which didn't work. But, I dunno what is and is not supposed to be inside of that file either so..... (at least the data port is working now)<Edit>
Click to expand...
Click to collapse
Ok long answer short style. To install a ROM you need root access.
To do any pg321.IMG flashing you need s off.
Can't do both if you don't have either.
So you have adb on your computer? Plug in the phone and type: adb devices . It should give a long number. Type :adb reboot . should reboot the phone. If after typing adb devices n it hangs on waiting for device try another computer port or cable.
I'm unsure if you can factory reset using adb but check around. Might have to do one if possible.
Sent from my Incredible 2 using xda app-developers app

FordNate said:
Ok long answer short style. To install a ROM you need root access.
To do any pg321.IMG flashing you need s off.
Can't do both if you don't have either.
So you have adb on your computer? Plug in the phone and type: adb devices . It should give a long number. Type :adb reboot . should reboot the phone. If after typing adb devices n it hangs on waiting for device try another computer port or cable.
I'm unsure if you can factory reset using adb but check around. Might have to do one if possible.
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
The DINC2's connected Via the micro USB to a Windows 7 (32 bit version) computer. (64-bit version is availalbe if needed).
Phone starts with (Vol Down/Power Buttons)
------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------
HBOOT in blue/on top
FASTBOOT in blue in the selection choices.
------------------------------------------------------------------------------------------------
"Device Manager" as well as "Devices and Printers".
-UNKNOWN DEVICE​------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------
If Either FASTBOOT OR HBOOT USB is chosen.
------------------------------------------------------------------------------------------------
"Devices and Printers" reflect
-Unspecified (1)
-Android 1.0​------------------------------------------------------------------------------------------------
When FASTBOOT is selected (is changed to "FASTBOOT USB"(in red)
"Device Manager" reflects
-Android USB Devices
-My HTC​------------------------------------------------------------------------------------------------
When HBOOT USB is selected (is changed to "HBOOT USB PLUG"(in blue)
"Device Manager" reflects
-Android USB Devices
-Android Bootloader Interface​------------------------------------------------------------------------------------------------​Both "adb devices" as well as "adb reboot" commands are executed in all three modes and return the following the results
------------------------------------------------------------------------------------------------
Code:
C:\android-sdk-windows\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\android-sdk-windows\platform-tools>adb devices
List of devices attached
C:\android-sdk-windows\platform-tools>adb reboot
error: device not found
C:\android-sdk-windows\platform-tools>
I would suggest these are not good results.
Now I am getting scared that I bricked my phone. Should I be scared?

Madd-Panda said:
Are you looking to Unlock, S-OFF or custom ROM? Or am I correct in assuming you want to keep your phone as stock as possible?
Click to expand...
Click to collapse
ANY of those choices would be welcome TYVM. Which do you think I should start with seeing that I'm (It's) stuck on the HTC White Screen?

2 options
avibp said:
ANY of those choices would be welcome TYVM. Which do you think I should start with seeing that I'm (It's) stuck on the HTC White Screen?
Click to expand...
Click to collapse
This link will take you to a very in depth guide on getting your phone rooted with S-OFF. It's got the commands and links to everything you will need. Fairly easy to follow.
I Highly recommend reading that.
However, if your having problems with ADB, you might want to look into the official HTC developer boot unlocker so you can load a custom recovery, and then a ROM, and get back to working phone status.
I have had a lot of trouble with HTC's Dev-unlock, because it does not completely unlock, so you have to flash the boot.img separately, but it is an option, and it's very easy to follow if your new (why I used it)

Madd-Panda said:
This link will take you to a very in depth guide on getting your phone rooted with S-OFF. It's got the commands and links to everything you will need. Fairly easy to follow.
I Highly recommend reading that.
However, if your having problems with ADB, you might want to look into the official HTC developer boot unlocker so you can load a custom recovery, and then a ROM, and get back to working phone status.
I have had a lot of trouble with HTC's Dev-unlock, because it does not completely unlock, so you have to flash the boot.img separately, but it is an option, and it's very easy to follow if your new (why I used it)
Click to expand...
Click to collapse
Awesome. Links to short-cuts. Thank you very much !
However, all these things require access to some level of the phone that I don't have yet since I am stuck at the white HTC Screen.
Do you have anything that can get me past that? Seriously. I want to learn how to ROOT, UNLock, S-Off and install custom ROMs but, I have to get my phone back first !
<Edit>The HTC Unlocker didn't work before because, again, I am stuck on the white HTC Screen. </Edit>

I want to root my ZE551ML but I don't know what to do pls help.

I tried to root my phone last night, but I stop midway of the process because of some problems like "phone not turning on with no vibrate at all when I restart after its stuck to inverted white screen, when I luckily turn it back on but it bootloops".
Heres the details:
I run unlock.bat then after its done it reboots with inverted white screen with logo then I run restore.bat and after it restart there is no sign of warning "failed verification" until it fully loads up, I go back to fastboot again to flash TWRP after running twrp.bat it says "flash succesfully" and the program closed by itself, then I go to recovery mode after rebooting I saw android error just like how it use to be. I press power button + volume up then release the volume up then I see the stock recovery (which it should be TWRP since I've done flashing it).
I think that my bootloader is still locked since there's no warning display of "failed verification". So I repeat the steps again after running unlock.bat, it reboots and the screen is inverted but it's stuck up to white logo, I waited for a while but nothing happens so I tried to reboot my phone "holding power button (power off)" when power on, it wont turn on, no vibration just a sound on laptop "connected sound and disconnected sound" I tried to power it on many times but still no luck I got panicked, jittery walking back and forth :crying:. Then I disconnect the usb cable and I tried to turn it on and suddenly I feel the vibration on my phone then it boots up but still stuck in white screen then it restart after keeping it for too long (while watching videos related to my problem)...
then my friend here said "ohh it bootloop" he read the instruction and he said to try this
"FAQ 1. Stuck at white screen with asus logo?
Sol. a) White screen means you are unlocked (action of unlock.bat), so you may give a try to restore.bat in fastboot mode."
and it solve my problem my phone is working again ... But I want to continue to root it but I'm afraid which steps I should go next, I still don't see the warning "failed verification" after my phone boots up and works again... I need HELP thank you
I also got question: is my bootloader unlock since it inverted white screen? or it still locked since there no sign of warning "failed verification"?

@PrinceLys
What is your build number in settings ,about phone ?

timbernot said:
@PrinceLys
What is your build number in settings ,about phone ?
Click to expand...
Click to collapse
ahmm I think this?
model number: ASUS_Z00AD
android version: 6.0.1
software information: WW_4.21.40.223_20161216
P.S my phone is back on working state.
I just don't know if I can proceed to root after the incident. I don't know, I just want to make sure that my bootloader is still unlocked after what I've done (it did white screen with black asus logo) or.... it doesn't unlocked at all since I don't see this warning "your device has failed verification and may not work properly." (I've attach screenshot from the video tutorial)
I tried to manualy check if my bootloader is really on unlock state but I can't using these methods
method 1: on device’s dialer dial *#*#7378423#*#* (failed)
method 2: fastboot oem device-info (failed)
my recovery it still on stock recovery even after I flash twrp
btw guide source: https://forum.xda-developers.com/zenfone2/general/root-install-xposed-marshmallow-6-0-1-t3456443
Q: should I still continue to flash twrp until it install?

Theres 2 bootloader unlock tools in general section , one is automatic

Read this from start to finish before doing anything.. also have on another device to refer to as you are doing the steps also download the ROM and gapps you want and put on SD card before you start even if you have to download them and move them from PC to SD card. https://plus.google.com/113955136844726294013/posts/aLJdNZN3g8q
Sent from my ASUS_Z00A using Tapatalk

timbernot said:
Theres 2 bootloader unlock tools in general section , one is automatic
Click to expand...
Click to collapse
I'm going to look for it... thanks

musicman5844 said:
Read this from start to finish before doing anything.. also have on another device to refer to as you are doing the steps also download the ROM and gapps you want and put on SD card before you start even if you have to download them and move them from PC to SD card. https://plus.google.com/113955136844726294013/posts/aLJdNZN3g8q
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
I've haven't fully read the instruction maybe tomorrow I will read it.
I just downloaded the files early and look into it... it seems like the versions are kinda latest (I don't know much about the droidboot ver. but I just look at the number on it "the higher the latest /heh") also the twrp is 3.0.3.
the ones that I used are all in package and it was 3.0.2 so I kinda go for the link you gave me
Thanks :good:

Hi,I've had the same situation,but it is solved now.If you have any problem,maybe I can help you .

nanobrain---- said:
Hi,I've had the same situation,but it is solved now.If you have any problem,maybe I can help you .
Click to expand...
Click to collapse
(I've finally think my bootloader is unlock after all.)
btw, did you succesfylly flash twrp?
Mine didn't flash (using twrp.bat), I guess I will try it again tonight if it fails again im gonna dl twrp from official and manually flash it.

BOOTLOADER is LOCKED and Usb debugging is not enabled

My phone is gone into LOOPMODE only showing GOOGLE , and no OEM enabled , no USB debugging Enabled also DEVICE state is LOCKED...
please help me to restore my set.
how to Unlock the bootloader or how to enable USB debugging ?

From the reading that I have done, if the device state is locked you are in a bad way.
I have almost had success freezing my phone down to -18C, it will then complete the boot process but reboots before I can get into turn on OEM unlocking in the settings.
I am going to try and boot the phone whilst it is disassembled and use some freeze spray to keep it cool, in a couple of days when I have some free time.

First off , thankyou for replying
sconno said:
From the reading that I have done, if the device state is locked you are in a bad way.
I have almost had success freezing my phone down to -18C, it will then complete the boot process but reboots before I can get into turn on OEM unlocking in the settings.
I am going to try and boot the phone whilst it is disassembled and use some freeze spray to keep it cool, in a couple of days when I have some free time.
Click to expand...
Click to collapse
yeah sure, i m on HOLD , i have tried all things such as adb, nexus toolkit and all adb commands .
Reply soon bro !

Freezing you phone is nonsense and won't do anything for a software problem!
What you need to do is unlock the bootloader again. (do a search for howto do this)
And then give the adb command to format userdata! ("fastboot format userdata") This will wipe any encryption on the phone that's blocking further acces.
The next step is to download the lastest OTA and sideload it through adb. This will unconditionally write a clean stock ROM on your phone and you should be good to go.
MIND THAT THIS WILL WIPE EVERYTING ON YOUR PHONE!!!

r3act said:
Freezing you phone is nonsense and won't do anything for a software problem!
What you need to do is unlock the bootloader again. (do a search for howto do this)
And then give the adb command to format userdata! ("fastboot format userdata") This will wipe any encryption on the phone that's blocking further acces.
The next step is to download the lastest OTA and sideload it through adb. This will unconditionally write a clean stock ROM on your phone and you should be good to go.
MIND THAT THIS WILL WIPE EVERYTING ON YOUR PHONE!!!
Click to expand...
Click to collapse
but how to unlock bootloader , thats the problem bro ! i have done evrytthing to do so !

OK, so after trying to get my phone to boot for the past 3 days, I have finally done it and enabled the OEM unlock option.
I am running bullhead 7.1.2
1. Put phone in freezer at -18C for about 30 minutes.
2. Plugged phone into USB, pressed the power button and it then finally booted all the way.
3. Went into settings
4. Enabled developer options
5. Went into developer options and enabled OEM unlock. (I had to enter my pin number to make this happen)
I can now access the device using adb and device in no longer locked.

sconno said:
OK, so after trying to get my phone to boot for the past 3 days, I have finally done it and enabled the OEM unlock option.
I am running bullhead 7.1.2
1. Put phone in freezer at -18C for about 30 minutes.
2. Plugged phone into USB, pressed the power button and it then finally booted all the way.
3. Went into settings
4. Enabled developer options
5. Went into developer options and enabled OEM unlock. (I had to enter my pin number to make this happen)
I can now access the device using adb and device in no longer locked.
Click to expand...
Click to collapse
but i think my Android is corrupt , it showing only google when i press and hold the power button.
give me another solution bro !
And anyone from MUMBAI (BORIVALI WEST)

Try this. It worked for me on 2 devices.
https://hackaday.com/2017/02/11/nexus-5x-phone-resurrected-by-the-oven/

harihacker said:
Try this. It worked for me on 2 devices.]
Thanks for this, I am going to give this a go with a heat gun later on today.
Click to expand...
Click to collapse

harihacker said:
Try this. It worked for me on 2 devices.
https://hackaday.com/2017/02/11/nexus-5x-phone-resurrected-by-the-oven/
Click to expand...
Click to collapse
lol , I think my Phone is dead RIP .

Remove VMware Hub bloatware

Good morning,
I'm writing this post 'cause I'd like to know if it's a possibility to "unlock", if I can say this, my phone. My company installs on my phone VMware Hub and the Debug USB is locked because I cannot unlock the related menu. I've tried to format the phone from original recovery by wiping data and nothing changed. So, I've run my phone into bootloader in order to overwrite the original firmware with a new original one. The process is ok but when I restart my phone, VMware is installed and configured.
Now, a question, is it possible to remove it withouth root or debug USB? I'm so annoyed because it is possible to check everything I do in my phone

Did someone answer you? I have the same problem.
Thanks.

Hello, sorry for such late reply been way for too long, the answer is simple, go to developer options, select the oem unlock option reboot the phone to download or recovery i don't remember, a message will come before that will alow you to unlock bootloader, precede to unlock, i can't recall if the phoene will reset but i assume so, when it comes back it will no longer be tied to your employer, it will be an A50 like any other bougt on the store, keep in mind that from then foword you will get a message saying that bootloader is unlocked at phone power on, that's it