Database Info

Is my phone bricked?

Hi everyone,
Sorry for sounding like a total noob, but today I was trying to flash my phone to "SUPER-HERO" rom. but first I needed to update the radio and hboot.
I went into recovery mode with "fastboot boot recovery.img".
Updated to radio image
6.35.08.29
And rebooted.... my phone showed up an HTC boot screen (probably was doing some updating) and then the problem started..
My phone is now booting through the vodafone logo then the HTC Magic logo (usb sound on my laptop for a second) and reboot.
No key combination is working except for the action button which shows up a blue LED.
Anyone can help?
My phone is an HTC Magic 32A (Vodafone Branded).
Thanks.

N4rc071x said:
Hi everyone,
Sorry for sounding like a total noob, but today I was trying to flash my phone to "SUPER-HERO" rom. but first I needed to update the radio and hboot.
I went into recovery mode with "fastboot boot recovery.img".
Updated to radio image
6.35.08.29
And rebooted.... my phone showed up an HTC boot screen (probably was doing some updating) and then the problem started..
My phone is now booting through the vodafone logo then the HTC Magic logo (usb sound on my laptop for a second) and reboot.
No key combination is working except for the action button which shows up a blue LED.
Anyone can help?
My phone is an HTC Magic 32A (Vodafone Branded).
Thanks.
Click to expand...
Click to collapse
You must to revert to old radio, when you update to new radio you need to install a rom/kernel port that works with new radio.
Look here
http://forum.xda-developers.com/showthread.php?t=605239
to come back to old radio
merlos

I can't reach fastboot I don't know why.. fastboot usually gets launched as soon as I press back + power.. I just get the vodafone logo then the HTC logo right after that.. and then it restarts.

If you flashed an incorrect radio or recovery (flashing the wrong radio is a surefire way to get bricked), and as a result are not able to get to fastboot or recovery, then you're bricked and as a result need a new phone.

I managed to get the phone to fastboot but when I load the recovery ROM the phone just resets.
What can I do in fastboot?

N4rc071x said:
I managed to get the phone to fastboot but when I load the recovery ROM the phone just resets.
What can I do in fastboot?
Click to expand...
Click to collapse
You can flash a new (Correct) radio and/or recovery rom, or even a new SPL. Course reason instructions carefully for whatever you grab.

[Q] Stuck in bootloop after firmware update 3.24.401.1 RUU

Hi guys
I have a normal HTC Sensation (i.e. non-XE). I have had my phone for a couple of months, and have tried all of the different ARHD versions. My phone is s-off, supercid, and I haven't had any problems installing custom ROMS previously.
I was on ARHD 6.0.3. and this morning I was trying to update the firmware to change to the new ARHD 6.1.0 ROM.
I am stuck in a bootloop, after flashing the 3.24.401.1 RUU firmware update.
When the firmware update was completed, I removed the SD card and rebooted. But I think this is where I messed up, because I didn't reboot into recovery!
Now I can't get back into recovery mode. When I hold down the volume key and power key, it just goes to the HTC boot screen, then it gets stuck in the bootloop!
How can I fix this if I am no longer able to boot into recovery
I have tried pulling the battery and SD card, but nothing gets me out of the bootloop.
I did some thread searches, but most solutions assume that you can at least boot back into recovery mode (which I can't seem to do now...) I'd appreciate any help that can get my phone back up and running.

Okay, so I have managed to fix the problem myself after piecing together bits of information from searching existing posts.
While I was searching for answers, I put my SD card into my PC and removed the firmware file. Then I put the SD card back into my phone.
I plugged my phone into my PC while the phone was turned off.
Then I used the windows command prompt to start adb "cd c:\adb"
Then I typed "adb reboot bootloader" to boot the phone into the bootloader. I didn't think this would work with the phone powered off...but it did.
Once in the bootloader, I unplugged the USB cable, and went into Recovery and flashed the ARHD 6.1.1 ROM.
Once the ROM had flashed, I rebooted and everything is working fine again now

You just needed to pull out battery and reinsert.. Then power+ Vol button to enter bootloader ...

jjdoctor said:
You just needed to pull out battery and reinsert.. Then power+ Vol button to enter bootloader ...
Click to expand...
Click to collapse
That's what I thought. But I tried that several dozen times, and it didn't work.

thanks for posting what you did to fix it...every time i'm flashing something i always think i'm going to mess it up

No problem. At least now I know that if I ever get stuck in a bootloop again, and I can't get into the bootloader with Vol down + Power, I can use ADB

How can i fix my One S (Bootloop)

Hi, i wanted to upgrade my rom from black dragon 4.5 til 5.0 but as i was in a bit of a hurry i failed to read the innstalation notes..
So i just flashed the rom.zip from cwm touch and tried to reboot, now im stuck in a bootloop with the HTC screen with the red writings and a blackscreen.
I cant seem to be able to power-off my device either, i guess i have to let the power run out..
Is there any way i can fix this and flash mayby LeeDroid rom or is my phone permanently bricked?

rom.zip from an RUU ??
If it wasnt, most custom roms require the boot.img to be flashed.
Plug your phone in via USB and use adb to do a full factory reset, Flash boot.img and flash the rom
you should be good to go in no time

azzledazzle said:
rom.zip from an RUU ??
If it wasnt, most custom roms require the boot.img to be flashed.
Plug your phone in via USB and use adb to do a full factory reset, Flash boot.img and flash the rom
you should be good to go in no time
Click to expand...
Click to collapse
yep what he said you can also hole power button for a bit and it will power of the phone

^^What they said. You need to fastboot yourboot.img through adb. Since that rom has the base upgraded to 1.78, you need to update your boot.img, it's provided right under the logo.

[Q] Yet Another Potential Brick

Hello,
Earlier today I installed BAKED ROM on my AT&T HTC ONE XL that was at the time running CM 10.1 After having some issues with wifi not working I decided to restore from my backup made in CWR when installing CM 10.1 on my phone. After the restore finished i was stuck in a bootloop. So i went back into CWR to re install the BAKED ROM. Once i cleared drive i came to realize that i somehow deleted the .zip files for the ROM on my phone and no longer had a ROM to install. After that i decided that I would mount my phone from CWR so i can transfer the .zip to my phone and then install. After realizing i need to use TWRP to be able to mount and transfer files i was going to flash over TWRP in fastboot. My issue currently is that my phone is powered off after telling it to shutdown in bootloader, and i can not get it to turn back on or to boot into bootloader so that i can flash TWRP. Hopefully i am missing something small here. Any advise is appreciated.
Thank You

coltp10 said:
Hello,
Earlier today I installed BAKED ROM on my AT&T HTC ONE XL that was at the time running CM 10.1 After having some issues with wifi not working I decided to restore from my backup made in CWR when installing CM 10.1 on my phone. After the restore finished i was stuck in a bootloop. So i went back into CWR to re install the BAKED ROM. Once i cleared drive i came to realize that i somehow deleted the .zip files for the ROM on my phone and no longer had a ROM to install. After that i decided that I would mount my phone from CWR so i can transfer the .zip to my phone and then install. After realizing i need to use TWRP to be able to mount and transfer files i was going to flash over TWRP in fastboot. My issue currently is that my phone is powered off after telling it to shutdown in bootloader, and i can not get it to turn back on or to boot into bootloader so that i can flash TWRP. Hopefully i am missing something small here. Any advise is appreciated.
Thank You
Click to expand...
Click to collapse
hold the power button down for about 15 seconds. wait for 5 seconds, then press the power button and volume down at the same time after a few seconds you should get the bootloader screen.
does the led come on when you're charging it?

cr1960 said:
hold the power button down for about 15 seconds. wait for 5 seconds, then press the power button and volume down at the same time after a few seconds you should get the bootloader screen.
does the led come on when you're charging it?
Click to expand...
Click to collapse
Thank you for your response. From following your instructions i was still not able to get into bootloader, and when i plug it in to charge the LED does not come on

coltp10 said:
Thank you for your response. From following your instructions i was still not able to get into bootloader, and when i plug it in to charge the LED does not come on
Click to expand...
Click to collapse
Sadly based on my knowledge and experience(I learned this the hard way by taking the ATT OTA) if the led doesn't come on while charging and you cant access your bootloader your phone is sadly dead. However you can double check to see if its your cord and if it is not then call HTC if device is still under warranty. They replaced the internals of mine and recieved it back at no charge.
If I have helped in any way hit the Thanks button please.

Why did you "need" to go to TWRP to mount SD? Clockworkmod has had SD mount fixed for some time now, hasn't it?
Leave the phone on wall charger (not connected to computer) overnight or 8 Hrs or so, and see if you get any LED's or can get into bootloader. If you were only messing with ROMs and recovery, I don't see how you can be bricked (as long as anything you were trying to flash was for the EVITA). The battery may just have run down while you were messing with the device.

redpoint73 said:
Why did you "need" to go to TWRP to mount SD? Clockworkmod has had SD mount fixed for some time now, hasn't it?
Leave the phone on wall charger (not connected to computer) overnight or 8 Hrs or so, and see if you get any LED's or can get into bootloader. If you were only messing with ROMs and recovery, I don't see how you can be bricked (as long as anything you were trying to flash was for the EVITA). The battery may just have run down while you were messing with the device.
Click to expand...
Click to collapse
Well when i went into clockworkmod and told it to mount SD it did not work, i have all of my drivers installed properly so it couldn't be a driver issue. So i figured that i would just flash over TWRP and use mount to usb as a second shot. I will have to try and leave it plugged in later after work. Yes the ROM that i installed was for the EVITA, it was running fine except the wifi wouldnt turn on.

coltp10 said:
Well when i went into clockworkmod and told it to mount SD it did not work, i have all of my drivers installed properly so it couldn't be a driver issue.
Click to expand...
Click to collapse
If/when you get back up and running, if still on CWM, make sure its up to date. I think the SD mount was fixed quite some time ago.

redpoint73 said:
If/when you get back up and running, if still on CWM, make sure its up to date. I think the SD mount was fixed quite some time ago.
Click to expand...
Click to collapse
Okay thanks for the input i will check it out as soon as I am able

When i came home from work and plugged it in the red LED light came on. After letting it charge for about 5 hours i tried to access the bootloader by pressing power down for 15 seconds, then waiting 5, and then power and volume down, to no result. Only when holding down power for the first 15 seconds the soft on screen keys did flash

coltp10 said:
When i came home from work and plugged it in the red LED light came on. After letting it charge for about 5 hours i tried to access the bootloader by pressing power down for 15 seconds, then waiting 5, and then power and volume down, to no result. Only when holding down power for the first 15 seconds the soft on screen keys did flash
Click to expand...
Click to collapse
After holding the power button down and let the capacitive keys flash 6 times. The 6 flashes means a hard reset and it's about to start rebooting. Let go of the power button and immediately hold volume down. It should take you into the bootloader. Then you can fastboot flash TWRP.
Sent from my HTC One X using Tapatalk 2

Thank you
Finally after letting it charge all night, i was able to access my bootloader, i flashed over TWRP and am in the process of mounting my sd to transfer the rom and hopefully install. Thank you all for you help!!

coltp10 said:
Finally after letting it charge all night, i was able to access my bootloader, i flashed over TWRP and am in the process of mounting my sd to transfer the rom and hopefully install. Thank you all for you help!!
Click to expand...
Click to collapse
Good luck
Sent from my HTC One X using xda premium

Well i was able to install cm 10.1 back to my phone and successfully load it, my only issue now as before when i installed the BAKED rom, is my wifi doesn't seem to work or recognize any networks

coltp10 said:
Well i was able to install cm 10.1 back to my phone and successfully load it, my only issue now as before when i installed the BAKED rom, is my wifi doesn't seem to work or recognize any networks
Click to expand...
Click to collapse
Glad you got it working.
What hboot are you on? If you are on one of the newer ones, not 1.09, and don't have s-off you have to manually flash the boot.img through fastboot after installing the ROM. That sounds like it might be your issue.

pside15 said:
Glad you got it working.
What hboot are you on? If you are on one of the newer ones, not 1.09, and don't have s-off you have to manually flash the boot.img through fastboot after installing the ROM. That sounds like it might be your issue.
Click to expand...
Click to collapse
Agreed, i did forget to flash to boot image during my excitement to a working phone again, even so, if i hadn't flashed the boot image why is it that my phone was actually able to start up the rom and go through phone system setup?

coltp10 said:
Agreed, i did forget to flash to boot image during my excitement to a working phone again, even so, if i hadn't flashed the boot image why is it that my phone was actually able to start up the rom and go through phone system setup?
Click to expand...
Click to collapse
because the rom you flashed is based on CM so it was compatible enough to boot but not have everything working as it should. if you don't flash the boot.img, the previously used kernel would still be used.

The ROM was running and i was able to use my phone. Then i flashed over the boot.img for my rom and now it doesnt boot up it is stuck at the Cyanogen Mod loading screen

coltp10 said:
The ROM was running and i was able to use my phone. Then i flashed over the boot.img for my rom and now it doesnt boot up it is stuck at the Cyanogen Mod loading screen
Click to expand...
Click to collapse
boot to recovery, wipe everything (cache, dalvik, system, factory reset), reflash the rom you want to use, then reboot to bootloader and fastboot flash boot boot.img extracted from the rom you just flashed.
Not sure where you went wrong but that will get you booting. To avoid having to fastboot flash boot boot.img everytime, you can S-OFF.

exad said:
boot to recovery, wipe everything (cache, dalvik, system, factory reset), reflash the rom you want to use, then reboot to bootloader and fastboot flash boot boot.img extracted from the rom you just flashed.
Not sure where you went wrong but that will get you booting. To avoid having to fastboot flash boot boot.img everytime, you can S-OFF.
Click to expand...
Click to collapse
I will have to look into the S-OFF. As of right now i wiped everything, installed rom, installed gaps, went to bootloader flashed boot.img and now just waiting to see if it will start up

coltp10 said:
I will have to look into the S-OFF. As of right now i wiped everything, installed rom, installed gaps, went to bootloader flashed boot.img and now just waiting to see if it will start up
Click to expand...
Click to collapse
You can also use the flash image GUI app to flash a boot image in Android right before you boot to recovery to flash the ROM. But I would definitely look into s-off. It's a very easy process and then you don't ever have to worry about the boot.img at all.

Power & vol down no longer loads bootloader after flashing

Hello,
I am getting myself deeper into trouble working on this.
First I will explain what I did, I wanted marshmallow and read TWRP needs to be updated to load it and also that that I cannot restore from older backup, so I figured I update TWRP first then do a backup.
I did the TWRP update via app, verified the partition and when done and rebooted to recovery, TWRP was still v2.7 and the phone won't boot, the OS was gone.
so then I figured I flash Dottat M8firmwareandRecovery to get the new TWRP and backed up the Data partition.
then found out that I can't use that Data partition with a different OS. So I figured I flash KitKat back on.
did that, now I can not get back into recovery, holding the Vol down with power will not go to HBOOT.
now KitKat loads, had root, but the dang thing auto updated to 4.4.3 and now lost root. I thought it can't auto update with s-off
so it as asking for another update now and I turned it off. Waiting for someone to help , I keep making it worse.
my phone was unlocked and s-off, I hope it still is, can anything undo that?
Please help

Fireflynj said:
Hello,
I am getting myself deeper into trouble working on this.
First I will explain what I did, I wanted marshmallow and read TWRP needs to be updated to load it and also that that I cannot restore from older backup, so I figured I update TWRP first then do a backup.
I did the TWRP update via app, verified the partition and when done and rebooted to recovery, TWRP was still v2.7 and the phone won't boot, the OS was gone.
so then I figured I flash Dottat M8firmwareandRecovery to get the new TWRP and backed up the Data partition.
then found out that I can't use that Data partition with a different OS. So I figured I flash KitKat back on.
did that, now I can not get back into recovery, holding the Vol down with power will not go to HBOOT.
now KitKat loads, had root, but the dang thing auto updated to 4.4.3 and now lost root. I thought it can't auto update with s-off
so it as asking for another update now and I turned it off. Waiting for someone to help , I keep making it worse.
my phone was unlocked and s-off, I hope it still is, can anything undo that?
Please help
Click to expand...
Click to collapse
I've personally never seen a device go back to S-ON without the user doing it with the cmd.
That isn't to say it's never happened before.
I'd assume you are still S-OFF.
What happens when you flash a ROM that has a power menu and you select to reboot to recovery or bootloader?
Or you can root and download an app that works the same way. curious what it does.
Also how long are you holding the buttons?
If everything else is working you should be able to get to hboot/recovery - but I honestly don't know.
My suggestion?
Get a more recent RUU .exe and run it on your PC and see what happens.
here is the link
https://www.androidfilehost.com/?fid=24052804347812372

andybones said:
I've personally never seen a device go back to S-ON without the user doing it with the cmd.
That isn't to say it's never happened before.
I'd assume you are still S-OFF.
What happens when you flash a ROM that has a power menu and you select to reboot to recovery or bootloader?
Or you can root and download an app that works the same way. curious what it does.
Also how long are you holding the buttons?
If everything else is working you should be able to get to hboot/recovery - but I honestly don't know.
My suggestion?
Get a more recent RUU .exe and run it on your PC and see what happens.
here is the link
https://www.androidfilehost.com/?fid=24052804347812372
Click to expand...
Click to collapse
I would, but I don't know how to flash without the HBOOT, I got some research to do to learn how to do it from the PC.

Fireflynj said:
I would, but I don't know how to flash without the HBOOT, I got some research to do to learn how to do it from the PC.
Click to expand...
Click to collapse
Download the .exe and click open. Follow directions on the screen. It doesn't get easier, trust me you'll be fine. Wouldn't steer you wrong.

Fireflynj said:
I would, but I don't know how to flash without the HBOOT, I got some research to do to learn how to do it from the PC.
Click to expand...
Click to collapse
The only time I've seen a phone be a pita when trying to enter boot loader is when it's connected to USB.
Sent from my HTC6545LVW using Tapatalk

dottat said:
The only time I've seen a phone be a pita when trying to enter boot loader is when it's connected to USB.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
My Galaxy Tab2 did that. I tried the M8 again today with USB unplugged, did not get boot loader menu, but then while it was on, I did a Vol up and power (forced shutdown) then while still holding the power button switched to Vol down right when the screen blanked, then I got the boot loader! :victory:

Fireflynj said:
My Galaxy Tab2 did that. I tried the M8 again today with USB unplugged, did not get boot loader menu, but then while it was on, I did a Vol up and power (forced shutdown) then while still holding the power button switched to Vol down right when the screen blanked, then I got the boot loader! :victory:
Click to expand...
Click to collapse
and to correct myself.. one other condition. The older version of software included a "fastboot" option in settings->power that was more like a hibernate feature. That feature when enabled would prevent you from getting into bootloader.

dottat said:
and to correct myself.. one other condition. The older version of software included a "fastboot" option in settings->power that was more like a hibernate feature. That feature when enabled would prevent you from getting into bootloader.
Click to expand...
Click to collapse
That makes sense, 'fastboot' was on, its now off.
The bootloader works, KitKat OS is working, but not recovery. I get 'Entering Recovery . . .' on white htc screen and stuck there.
I used adb command prompt to flash recovery with fastboot then I tried HTC_fastboot and different versions of TWRP.
tried flashing with Flashify , no errors, it just doesn't load. I think something else is broke.
dottat, do you have an image of RUU rooted Kitkat with TWRP?
Thank you for the help.

Fireflynj said:
That makes sense, 'fastboot' was on, its now off.
The bootloader works, KitKat OS is working, but not recovery. I get 'Entering Recovery . . .' on white htc screen and stuck there.
I used adb command prompt to flash recovery with fastboot then I tried HTC_fastboot and different versions of TWRP.
tried flashing with Flashify , no errors, it just doesn't load. I think something else is broke.
dottat, do you have an image of RUU rooted Kitkat with TWRP?
Thank you for the help.
Click to expand...
Click to collapse
Your firmware is too old. That's why the newer recovery won't work. Do you want to update everything first and then RE-root?
Sent from my HTC6545LVW using Tapatalk

dottat said:
Your firmware is too old. That's why the newer recovery won't work. Do you want to update everything first and then RE-root?
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
Yup , that was it, the older one worked.
So dumped the idea of getting KitKat back and I flashed the Marshmallow custom s-off RUU with TWRP that you provided. so far good now I just need to re-root it.
Thank you