Database Info

SOFT bRICKED. HELP

well i had trouble installing the trickroid v7 on my [S3] and it will say OS not installed.
then after many tries, of pulling the usb in and out and restarting several times to bootlocker
I cannot open to bootlocker anymore and the phone seems to died and not be able to charge.
WHEN I HOLD POWER button and volume down, all 3 soft touch keys lit up for 6~7 seconds, then the the black screen flashes a green line and off.
I cannot connect to the computer through usb either, for some reason.

i have the same problem.my phone worked fine, i unlocked bootloader, installed recovery and rooted. yesterday i put my phone on charging and today it was dead??? it flashes 7 times while holding vol down + power and then nothing happens.
EDIT:
i got it working!!! i connected it to pc, run adb command: adb reboot-bootloader and i got bootloader menu, after that i went into recovery and i did factory defaults and rebooted phone,now it's charging and everything is OK!

Bubach28 said:
i have the same problem.my phone worked fine, i unlocked bootloader, installed recovery and rooted. yesterday i put my phone on charging and today it was dead??? it flashes 7 times while holding vol down + power and then nothing happens.
EDIT:
i got it working!!! i connected it to pc, run adb command: adb reboot-bootloader and i got bootloader menu, after that i went into recovery and i did factory defaults and rebooted phone,now it's charging and everything is OK!
Click to expand...
Click to collapse
man.. i know i can fix it... but i cant connect to the damn pc. it unable to detect it... !!!

this is what i have done and got it working. connect phone to pc that has installed htc drivers, hold down volume down button + power, phone flashes 7 times and orange led is working now. after that go to adb, type adb devices and my phone serial number was shown. after that i did the adb reboot-bootloader and my phone was alive again.
p.s. i tried also with HTC One S All-In-One Toolkit V1.1,before i made it, to send command, but phone led only show orange light and again went off. u can give a try.... if that dont work, then i think phone is dead and ready for repair :/

3 vibrate brick please help :(

First of all sorry for my english
I have bricked my inspire 4g eng s-off i was just trying to root my inspire 4g without unlocking bootloader noob i just know nothing about unlocking bootloader i used htc quick root software when the process start the software requested me an hboot image and unfortunatly i located to recovery image and phone turned off now when ever i try to turn it on it gives three vibrates vol down +pwr five vibrates please help m

volume up +voldown+pwr button five vibrates and a stable green led vol down +pwr three vibrates and red blinking led just pwr on button three vibrates red blinking led

If your bootloader wasn't unlocked, I don't see how you could have bricked it. Also, do you know if you had usb debug mode turned on? You couldn't have flashed an image with a locked bootloader and the scripts won't work either since the adb/fastboot utilities cannot talk to your phone if debug mode is off.
At any rate, pull out the battery for a few minutes, reseat the battery, connect the phone to your pc, hold down vol- and power and see if you can get to a bootloader screen. Even if it seems to boot but hangs at the green htc logo, you should still be able to issue adb commands and recover.
Once the phone boots, on your pc, open a command prompt and type the command "adb devices" without quotes to see if your phone is recognized. Let us know the status then.

turboyoshi said:
If your bootloader wasn't unlocked, I don't see how you could have bricked it. Also, do you know if you had usb debug mode turned on? You couldn't have flashed an image with a locked bootloader and the scripts won't work either since the adb/fastboot utilities cannot talk to your phone if debug mode is off.
At any rate, pull out the battery for a few minutes, reseat the battery, connect the phone to your pc, hold down vol- and power and see if you can get to a bootloader screen. Even if it seems to boot but hangs at the green htc logo, you should still be able to issue adb commands and recover.
Once the phone boots, on your pc, open a command prompt and type the command "adb devices" without quotes to see if your phone is recognized. Let us know the status then.
Click to expand...
Click to collapse
the bootloader was lock but eng s-off and there is is no adb no fastboot boot i have tried all methods putting battry out for 15 mints i have checked with another battery with no luck when ever i try to turn on my phone it give three vibrates and my pc recognize it as QUALCOMM DIAGNOSTIC 900e when i press vol down +pwr it gives three vibrates vol down +up+pwr five vibrates is there any way to flash the rom in qualcomm diagnostic mode and the usb debug was on last time kindly help me !!

Branded badmash said:
the bootloader was lock but eng s-off and there is is no adb no fastboot boot i have tried all methods putting battry out for 15 mints i have checked with another battery with no luck when ever i try to turn on my phone it give three vibrates and my pc recognize it as QUALCOMM DIAGNOSTIC 900e when i press vol down +pwr it gives three vibrates vol down +up+pwr five vibrates is there any way to flash the rom in qualcomm diagnostic mode and the usb debug was on last time kindly help me !!
Click to expand...
Click to collapse
Qualcomm mode is what happens when you hold volume down instead of up while booting. A common issue with the inspire is the volume rocker malfunctioning and becoming "stuck". Usually it is volume up that gets stuck. Either way you will have to probably repair the volume rocker by replacing it. With the age of the device though I don't think it's worth it to spend any money on repairs. It's almost 3 years old now. I know it seems concidental to happen at the same time your trying to unlock it but it can happen. If it is something that went wrong while you were trying to unlock it your pretty much in the same boat. If it only goes to Qualcomm mode there is nothing you can do.

Gizmoe said:
Qualcomm mode is what happens when you hold volume down instead of up while booting. A common issue with the inspire is the volume rocker malfunctioning and becoming "stuck". Usually it is volume up that gets stuck. Either way you will have to probably repair the volume rocker by replacing it. With the age of the device though I don't think it's worth it to spend any money on repairs. It's almost 3 years old now. I know it seems concidental to happen at the same time your trying to unlock it but it can happen. If it is something that went wrong while you were trying to unlock it your pretty much in the same boat. If it only goes to Qualcomm mode there is nothing you can do.
Click to expand...
Click to collapse
i have checked the volume rocker and replaceed it with no luck

Branded badmash said:
i have checked the volume rocker and replaceed it with no luck
Click to expand...
Click to collapse
Then something happened when you tried to unlock it. If you can't access the device via fastboot or adb then it is not fixable. Reflashing a boot img or hboot would be what you would want to do if you could gain access.

Need help with HTC sensation, i think he's bricked?

K got this HTC from a friend of me, was working before, had it rooted and fixed with custom rom
It was S-on on v1.27
k now gonna try to explain what's going wrong:
When i shut down the phone, put battery out, back in, connect to usb, i get the phone recognized by ADB (my HTC phone)
when i type adb reboot-bootloader, device responds and boots into fastboot mode
when i use vul up i get Fastboot usb on screen
from this point i can't get any further, device doesnt respond from any button action except for vol up.
Device is not recongized in windows now (windows 8 64bit) got the famous error 43
So in ADB everything is fine, but in fastboot nothing is working/responding
when i pull battery out, then put it back in, i can succesfully boot with volup en power, then i get everything running (custom rom from before) but it says safe mode
Any ideas what i can do to get this thing back on it's feet?
regards,
Robin

robin-sips said:
K got this HTC from a friend of me, was working before, had it rooted and fixed with custom rom
It was S-on on v1.27
k now gonna try to explain what's going wrong:
When i shut down the phone, put battery out, back in, connect to usb, i get the phone recognized by ADB (my HTC phone)
when i type adb reboot-bootloader, device responds and boots into fastboot mode
when i use vul up i get Fastboot usb on screen
from this point i can't get any further, device doesnt respond from any button action except for vol up.
Device is not recongized in windows now (windows 8 64bit) got the famous error 43
So in ADB everything is fine, but in fastboot nothing is working/responding
when i pull battery out, then put it back in, i can succesfully boot with volup en power, then i get everything running (custom rom from before) but it says safe mode
Any ideas what i can do to get this thing back on it's feet?
regards,
Robin
Click to expand...
Click to collapse
In bootloader(fastboot mode) no buttons will works except vol up,down and power..
If you want to flash a custom rom then
First goto bootloader
Now enter to recovery by using vol down and then power button to ok.
Place a Rom.zip in sdcard format cache/dalvik , all partition except sd and then flash rom..

ahsan64 said:
In bootloader(fastboot mode) no buttons will works except vol up,down and power..
If you want to flash a custom rom then
First goto bootloader
Now enter to recovery by using vol down and then power button to ok.
Place a Rom.zip in sdcard format cache/dalvik , all partition except sd and then flash rom..
Click to expand...
Click to collapse
problem was that none of the button's where responsive, i found the cause of this, volume buttons are damaged (the strip inside was broken)
So now i have a new problem much wurse i think
only power button works, so i did a complete reinstall with ruu, booted up fine, but always in safe mode for some strange reason,
Now after shutdown, i can't get the phone on anymore, only goes to Hboot, and there is nothing responsive, non eof the buttons work, can't use vol buttons because they are broken.
Adb is not responding either, only getting HTC Android USB device in my device list....
I think the phone is ready for trash? :S

robin-sips said:
problem was that none of the button's where responsive, i found the cause of this, volume buttons are damaged (the strip inside was broken)
So now i have a new problem much wurse i think
only power button works, so i did a complete reinstall with ruu, booted up fine, but always in safe mode for some strange reason,
Now after shutdown, i can't get the phone on anymore, only goes to Hboot, and there is nothing responsive, non eof the buttons work, can't use vol buttons because they are broken.
Adb is not responding either, only getting HTC Android USB device in my device list....
I think the phone is ready for trash? :S
Click to expand...
Click to collapse
in bootloader adb doesn't work only fastboot
so when you are in hboot screen try this command
fastboot reboot (in the hboot screen should say fastboot usb)

rzr86 said:
in bootloader adb doesn't work only fastboot
so when you are in hboot screen try this command
fastboot reboot (in the hboot screen should say fastboot usb)
Click to expand...
Click to collapse
can't get into adb anymore so i think the phone is dead unless we repair the volume buttons right?

robin-sips said:
can't get into adb anymore so i think the phone is dead unless we repair the volume buttons right?
Click to expand...
Click to collapse
since you are dealing with a hardware problem then yes
but try this
boot normally(even on safe mode)
connect it to pc and type
adb reboot bootloader
it will take you directly into fastboot mode
then type fastboot reboot
see how it goes and check volume button from there(to confirm the hardware issue)
otherwise repeat the procedure but instead of fastboot reboot run the ruu.exe again

Pixel Stuck in Bootloop, ADB Unauthorized, Bootloader Unlocked

Hello, I recently came on a pixel phone to build and use lineageOS on. Upon rebuilding, I believe I performed adb sync wrong the device and damaged system. After that, my adb keys became unauthorized and I am unable to access the bootloader menu(I press power and volume, but phone boots into Bootloop). I tried the steps to get to bootloader menu, but the phone doesn't power completely off, and when I press the power button it gives me the launch screen saying press power to pause/continue boot, not allowing me to go into bootloader
My bootloop goes like this: Bootloader integrity screen(bootloader unlocked, cannot be verified) --> Google loading screen --> Android recovery. This shows 2 options with the message, "Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device". The two options are to try again or data reset.
I press try again, and the same bootloop ensues, sometimes getting to lineage loading logo, but then back to the same recovery error regardless. If I press the buttons(power and vol up), to go into recovery, it just shows an android with a warning sign above it, giving a message saying "Error!" on the bottom. My adb on the computer shows as unauthorized, so I don't know how I can fix this. Google has said the warranty is expired and cannot do anything to help. Ideas to fix? Thanks for help in advance!

Use power and volume down (not up) to go into Fastboot mode. Then flash the stock images

NZedPred said:
Use power and volume down (not up) to go into Fastboot mode. Then flash the stock images
Click to expand...
Click to collapse
I tried that, but whenever I press any button, the phone is never turning completely off unless it dies. Even after that, it goes to the screen showing the secure boot integrity(Press power to continue/stop boot)
How can I completely shut off the device and restart it? And if system is messed up, will that leave my bootloader intact(I'm assuming so as boot is a different partition?)

mycalculations said:
I tried that, but whenever I press any button, the phone is never turning completely off unless it dies. Even after that, it goes to the screen showing the secure boot integrity(Press power to continue/stop boot)
How can I completely **** off the device and restart it? And if system is messed up, will that leave my bootloader intact(I'm assuming so as boot is a different partition?)
Click to expand...
Click to collapse
Does holding down the power button for 5-10 seconds turn it off? Or if you do that does it appear to turn off and then restart?
If that fails to turn it off, try just holding power and volume down for 5 seconds, and if the screen flashes (goes off and then on) let go of the power button but keep holding volume down and hopefully it goes into Fastboot.
That should work unless you have a dodgy power or volume button. The bootloader is completely separate to the boot partition, and the fact that it's doing anything at all suggests that it's still functioning.
Only other option I can think of is trying ADB commands when it's in recovery mode, e.g. adb reboot bootloader. However, if you have the stock recovery, that may not work.

NZedPred said:
Does holding down the power button for 5-10 seconds turn it off? Or if you do that does it appear to turn off and then restart?
If that fails to turn it off, try just holding power and volume down for 5 seconds, and if the screen flashes (goes off and then on) let go of the power button but keep holding volume down and hopefully it goes into Fastboot.
That should work unless you have a dodgy power or volume button. The bootloader is completely separate to the boot partition, and the fact that it's doing anything at all suggests that it's still functioning.
Only other option I can think of is trying ADB commands when it's in recovery mode, e.g. adb reboot bootloader. However, if you have the stock recovery, that may not work.
Click to expand...
Click to collapse
Thank You!!! It didn't work in the bootloop, so I had to let the phone drain its battery and shut itself off, then I was able to enter the bootloader and reinstall lineage. Thanks so much!

mycalculations said:
Hello, I recently came on a pixel phone to build and use lineageOS on. Upon rebuilding, I believe I performed adb sync wrong the device and damaged system. After that, my adb keys became unauthorized and I am unable to access the bootloader menu(I press power and volume, but phone boots into Bootloop). I tried the steps to get to bootloader menu, but the phone doesn't power completely off, and when I press the power button it gives me the launch screen saying press power to pause/continue boot, not allowing me to go into bootloader
My bootloop goes like this: Bootloader integrity screen(bootloader unlocked, cannot be verified) --> Google loading screen --> Android recovery. This shows 2 options with the message, "Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device". The two options are to try again or data reset.
I press try again, and the same bootloop ensues, sometimes getting to lineage loading logo, but then back to the same recovery error regardless. If I press the buttons(power and vol up), to go into recovery, it just shows an android with a warning sign above it, giving a message saying "Error!" on the bottom. My adb on the computer shows as unauthorized, so I don't know how I can fix this. Google has said the warranty is expired and cannot do anything to help. Ideas to fix? Thanks for help in advance!
Click to expand...
Click to collapse
Similar problem when i try to flash pixel dust rom through adb sideload... After successful installation reboots to system through twrp it shows no os installed then after i cant get to bootloader only black screen shows no display and now on pc phone not detecting .... connect and disconnect sound is there but nothing on screen

LANDTESTER said:
Similar problem when i try to flash pixel dust rom through adb sideload... After successful installation reboots to system through twrp it shows no os installed then after i cant get to bootloader only black screen shows no display and now on pc phone not detecting .... connect and disconnect sound is there but nothing on screen
Click to expand...
Click to collapse
Is ur bootloader unlocked? If so, use twrp to perform a full wipe and install from twrp as well. Of you can't access trwp, and are in a bootloop, do the same thing I did: let the phone lose all it's battery, so it's outta the loop, connect the phone to a charger, then hold power and volume down. This should get you into bootloader mode where you can then use fastboot to flash twrp.

mycalculations said:
Is ur bootloader unlocked? If so, use twrp to perform a full wipe and install from twrp as well. Of you can't access trwp, and are in a bootloop, do the same thing I did: let the phone lose all it's battery, so it's outta the loop, connect the phone to a charger, then hold power and volume down. This should get you into bootloader mode where you can then use fastboot to flash twrp.
Click to expand...
Click to collapse
Oh so after that i can get to bootloader .....hmm let me try thanks bro

mycalculations said:
Is ur bootloader unlocked? If so, use twrp to perform a full wipe and install from twrp as well. Of you can't access trwp, and are in a bootloop, do the same thing I did: let the phone lose all it's battery, so it's outta the loop, connect the phone to a charger, then hold power and volume down. This should get you into bootloader mode where you can then use fastboot to flash twrp.
Click to expand...
Click to collapse
My bootloader is unlocked but phone not detected on pc only black screen nothing else.... Red light flashes whenever connect to charger

stuk intro boot.

Hey guys off the forum,
my phone wont turn on anymore and is stuck on the boot picture.
I was running stock android 10 with unlocked bootloader. somehow it wasn't running smoothly and was planning on doing fresh install.
was running cmd then adb reboot bootloader then I did flash-all.bat ( I did not change the file just stock) everything went good until I restarted and cmd said error on the end. now cmd wont see the phone and phone wont turn on.
I was hoping if someone can please help me out I really appreciate it.

webjo said:
Hey guys off the forum,
my phone wont turn on anymore and is stuck on the boot picture.
I was running stock android 10 with unlocked bootloader. somehow it wasn't running smoothly and was planning on doing fresh install.
was running cmd then adb reboot bootloader then I did flash-all.bat ( I did not change the file just stock) everything went good until I restarted and cmd said error on the end. now cmd wont see the phone and phone wont turn on.
I was hoping if someone can please help me out I really appreciate it.
Click to expand...
Click to collapse
I had the same exact issue when it switched to slot B and stopped showing up on my computer when the device was in fastboot and I had no access to recovery mode. Try powering the phone down from fastboot with the power off menu. Then turn the phone on by holding the power button down and keep it pressed (it should cycle on and off b/w fastboot and a black screen. Keep holding until you feel a short vibration after about 30s - 1 min) It should then show it in adb and fastboot on your computer.
EDIT: If the phone isn't powering on, try charging it and if that doesn't work, try hard resetting it by holding the power button down for 30s-1 min. Can't imagine a bad flash would completely cause the phone to at least not load the bootloader.