My htc desire 816 ran out of charge and on charging it booted normally and after 10-15 seconds of starting up it resatrted by itself and continues to do so through out.
Anyone with a solution please Help.
amomaniac said:
My htc desire 816 ran out of charge and on charging it booted normally and after 10-15 seconds of starting up it resatrted by itself and continues to do so through out.
Anyone with a solution please Help.
Click to expand...
Click to collapse
Are you rooted??
no its not rooted. i tried the safe boot but no success. i tried the hard reset but all it showed me was a red triangle with a red exclamation mark amd went back to its restarting behaviour.
amomaniac said:
no its not rooted. i tried the safe boot but no success. i tried the hard reset but all it showed me was a red triangle with a red exclamation mark amd went back to its restarting behaviour.
Click to expand...
Click to collapse
Unlocked bootloader??
no the bootloader is not unlocked
amomaniac said:
no the bootloader is not unlocked
Click to expand...
Click to collapse
I'm helpless bro.
jithumon said:
I'm helpless bro.
Click to expand...
Click to collapse
what software is installed?
Related
Hi. Sorry for the noob question, i accidentally flashed my phone with not enough battery left so what happened was it just got stuck to the htc quietly brilliant screen, can i still charge in that mode? tried to get in CWM however, it just reboots to the htc quietly brilliant screen. Please help me if there are other ways to charge it so i can get to the homescreen. Thank you.
Try wiping cache in fastboot
amadz72 said:
Hi. Sorry for the noob question, i accidentally flashed my phone with not enough battery left so what happened was it just got stuck to the htc quietly brilliant screen, can i still charge in that mode? tried to get in CWM however, it just reboots to the htc quietly brilliant screen. Please help me if there are other ways to charge it so i can get to the homescreen. Thank you.
Click to expand...
Click to collapse
If you can boot into bootloader just Reflash the recovery and boot into it
XxVcVxX said:
Try wiping cache in fastboot
Click to expand...
Click to collapse
My problem though is that i can't seem to charge the phone so i can go into CMW mode.
amadz72 said:
Hi. Sorry for the noob question, i accidentally flashed my phone with not enough battery left so what happened was it just got stuck to the htc quietly brilliant screen, can i still charge in that mode? tried to get in CWM however, it just reboots to the htc quietly brilliant screen. Please help me if there are other ways to charge it so i can get to the homescreen. Thank you.
Click to expand...
Click to collapse
Is there no other way to charge the phone while in htc splash screen?
amadz72 said:
Is there no other way to charge the phone while in htc splash screen?
Click to expand...
Click to collapse
can't you just shut down the phone and then charge it while it is off?
My Rooted samsung galaxy s3 will not boot up ,only shows the samsung logo
i get into recovery for about 5 seconds and then it shuts off. same thing for the download mode
ive looked around and can not find a fix any information would be helpful thanx!
HELP ME PLEASE
neveronie said:
My Rooted samsung galaxy s3 will not boot up ,only shows the samsung logo
i get into recovery for about 5 seconds and then it shuts off. same thing for the download mode
ive looked around and can not find a fix any information would be helpful thanx!
HELP ME PLEASE
Click to expand...
Click to collapse
did you just root it? what method? is it still stock recovery or are you using cwm/twrp? it also sounds like the battery is low
xBeerdroiDx said:
did you just root it? what method? is it still stock recovery or are you using cwm/twrp? it also sounds like the battery is low
Click to expand...
Click to collapse
I used PhoneRebels CF Auto root. Im using cwm recovery, No my battery is fully charged. I Flashed to Synergys custom rom it was working for a while then my phone died and hasnt been able to boot
neveronie said:
I used PhoneRebels CF Auto root. Im using cwm recovery, No my battery is fully charged. I Flashed to Synergys custom rom it was working for a while then my phone died and hasnt been able to boot
Click to expand...
Click to collapse
i dont understand why you're device is powering off in recovery/download mode. any issues with the ROM should not be affecting the recovery partition. especially once its been booted into. lemme look around
xBeerdroiDx said:
i dont understand why you're device is powering off in recovery/download mode. any issues with the ROM should not be affecting the recovery partition. especially once its been booted into. lemme look around
Click to expand...
Click to collapse
Yea i tried going into download mode and connecting it to odin on my computer But as soon as it started to recognize it the phone reboots back to the logo as always
neveronie said:
Yea u tried going into download mode and connecting it to odin on my computer But as soon as it started to recognize it the phone reboots back to the logo as always
Click to expand...
Click to collapse
do you have enough time in recovery to wipe data/factory reset? possibly even wipe cache?
so this device was running the ROM fine, you did nothing new and this issue just sprang up?
xBeerdroiDx said:
do you have enough time in recovery to wipe data/factory reset? possibly even wipe cache?
so this device was running the ROM fine, you did nothing new and this issue just sprang up?
Click to expand...
Click to collapse
Yes ive wiped cache successfully and ive tried to factory reset but it doesnt have enough time before the device shuts off, Ya it was running decently then it froze and i took out the battery and thats when the problem began
xBeerdroiDx said:
i dont understand why you're device is powering off in recovery/download mode. any issues with the ROM should not be affecting the recovery partition. especially once its been booted into. lemme look around
Click to expand...
Click to collapse
maybe being soft bricked in a custom boot screen will have something to do with it?
neveronie said:
maybe being soft bricked in a custom boot screen will have something to do with it?
Click to expand...
Click to collapse
good morning. did you figure anything out?
xBeerdroiDx said:
good morning. did you figure anything out?
Click to expand...
Click to collapse
No i found someone who had a similar problem like this guy [ http://forum.xda-developers.com/showthread.php?t=1843053 ] but he doesn't really say how he fixed it or went into download mode because when i try It goes in for a few seconds then restarts vibrates and hangs in the loop
ok so this is my problem. i have an htc evo 4g which it was working the last 4 months i just did not use it any more and well i had problems with my evo 3d and i decided to activate the supersonic again but when i tried to turn it on it just booted up and turn off so fast i removed the battery and tried again but this time it just showed the htc logo and vibrated 5 times and turn off with the green led blinking i did wipe and did a factory reset i flashed 2 different roms with no luck i last the latest ruu it went well but no luck i was reading about this issue and no results
The phone boots up whenever it wants i can use it boot it turn off it self. when it turns off on the pc a message shows ---qualcomm driver
what can i do ? to fix it?
i can access bootloader and recovery and adb is tlaking to my phone too
Efrencalvario said:
ok so this is my problem. i have an htc evo 4g which it was working the last 4 months i just did not use it any more and well i had problems with my evo 3d and i decided to activate the supersonic again but when i tried to turn it on it just booted up and turn off so fast i removed the battery and tried again but this time it just showed the htc logo and vibrated 5 times and turn off with the green led blinking i did wipe and did a factory reset i flashed 2 different roms with no luck i last the latest ruu it went well but no luck i was reading about this issue and no results
The phone boots up whenever it wants i can use it boot it turn off it self. when it turns off on the pc a message shows ---qualcomm driver
what can i do ? to fix it?
i can access bootloader and recovery and adb is tlaking to my phone too
Click to expand...
Click to collapse
Didja ever figure this out?
swing4thefence said:
Didja ever figure this out?
Click to expand...
Click to collapse
mine did the same thing when it got warm. put it in the fridge for like 20 min then try again if it boots up successfully when its cold then you have a hardware problem
My Pixel XL downloaded and installed PP5 yesterday, seemed to go okay. Initially, it would boot but spontaneously reboot after 1-2 minutes of run time. But it degraded and now it is stuck on a white screen with Google, and reboots before the animation begins.
I can get into the Bootloader, but when I try to select Recovery mode it just goes back to the white boot screen and repeats. In Bootloader I can select Off, but it only shuts off for a short time then reboots on its own into the boot loop.
This was running stock Android, bought from Google Play store, unlocked, 32GB version, and I had run the previous 3 versions of Android P Beta without problems.
Is there anyway I can do a factory data reset without the Recovery mode?
Thanks,
...Patrick
pamack said:
My Pixel XL downloaded and installed PP5 yesterday, seemed to go okay. Initially, it would boot but spontaneously reboot after 1-2 minutes of run time. But it degraded and now it is stuck on a white screen with Google, and reboots before the animation begins.
I can get into the Bootloader, but when I try to select Recovery mode it just goes back to the white boot screen and repeats. In Bootloader I can select Off, but it only shuts off for a short time then reboots on its own into the boot loop.
This was running stock Android, bought from Google Play store, unlocked, 32GB version, and I had run the previous 3 versions of Android P Beta without problems.
Is there anyway I can do a factory data reset without the Recovery mode?
Thanks,
...Patrick
Click to expand...
Click to collapse
You didn't relock the bootloader did you? After unlocking it?
Phalanx7621 said:
You didn't relock the bootloader did you? After unlocking it?
Click to expand...
Click to collapse
No, I did not lock the bootloader. The phone was originally unlocked, and I never rooted it. It was completely stock. But it was definitely acting crazy....at one point I did see the Recovery mode but I did not know at the time what to do with it. Once I had a minute to research that on my laptop then it would never go back into Recovery mode.
So maybe I inadvertently locked it, but not that I know that I did it.
...Patrick
Phalanx7621 said:
You didn't relock the bootloader did you? After unlocking it?
Click to expand...
Click to collapse
No, I did not lock the bootloader. The phone was originally unlocked, and I never rooted it. It was completely stock. But it was definitely acting crazy....at one point I did see the Recovery mode but I did not know at the time what to do with it. Once I had a minute to research that on my laptop then it would never go back into Recovery mode.
So maybe I inadvertently locked it, but not that I know that I did it.
...Patrick
pamack said:
No, I did not lock the bootloader. The phone was originally unlocked, and I never rooted it. It was completely stock. But it was definitely acting crazy....at one point I did see the Recovery mode but I did not know at the time what to do with it. Once I had a minute to research that on my laptop then it would never go back into Recovery mode.
So maybe I inadvertently locked it, but not that I know that I did it.
...Patrick
Click to expand...
Click to collapse
I ended up asking uBreakiFix to diagnose the problem....and they indicate it is a bad motherboard.
It can be repaired for $380. I passed, and now own a brick that flashes from one Boot to the next, occassionally running for 30 seconds, but not quite long enough for me to run Reset Factory Settings.
Oh bother, < 2 years old.
...Patrick
pamack said:
I ended up asking uBreakiFix to diagnose the problem....and they indicate it is a bad motherboard.
It can be repaired for $380. I passed, and now own a brick that flashes from one Boot to the next, occassionally running for 30 seconds, but not quite long enough for me to run Reset Factory Settings.
Oh bother, < 2 years old.
...Patrick
Click to expand...
Click to collapse
Still probably worth flashing via adb to check?
mikefnz said:
Still probably worth flashing via adb to check?
Click to expand...
Click to collapse
He means fastboot.
here's what happened, the phone started freezing and restarting every 5 mins, I uninstalled some apps thinking that's what's causing it, I used it for around 10 minutes and it was fine, installed the latest security patch update, restarted and everything looked fine.
plugged it in, saw it had restarted again and it was stuck on the Samsung Galaxy A50 secured by Knox screen,
rn: I can't enter recovery mode, (the phone won't shut down and releasing the volume down and holding volume up thing doesn't work)
I can only enter download mode, Connected to Odin, flashed the latest firmware and it passed successfully, but still it gets stuck and won't boot.
any ideas?:crying:
anyone?
SallyTheDevil said:
anyone?
Click to expand...
Click to collapse
What firmware you.flashed??Stock firmware??Stuck at samsung screen?
muhamet said:
What firmware you.flashed??Stock firmware??Stuck at samsung screen?
Click to expand...
Click to collapse
yh I flashed the latest stock firmware,
n it's stuck there, like in th screenshot
SallyTheDevil said:
yh I flashed the latest stock firmware,
n it's stuck there, like in th screenshot
Click to expand...
Click to collapse
Force restart,press volume up and power button same time
muhamet said:
Force restart,press volume up and power button same time
Click to expand...
Click to collapse
Volume up and power doesn't do anything
Volume down + power restarts the phone but it comes to the same samsung black screen
Are you sure you flashed correct firmware? Tried to factory reset in recovery? Full Wipe and then flash the firmware?
You can also try 'adb logcat' to see what the error is if adb is available..
k3lcior said:
Are you sure you flashed correct firmware? Tried to factory reset in recovery? Full Wipe and then flash the firmware?
You can also try 'adb logcat' to see what the error is if adb is available..
Click to expand...
Click to collapse
I can't enter recovery mode
Volume down + power restarts but I did try to go to recovery by releasing volume down and pushing volume up the second screen goes black but it's not working
I can only enter download mode when it's connected to pc with odin running
Could it be a hard drive problem?
And I'm pretty sure i got the right firmware
Tbh not sure i got my A50 just recently, didn't even flash anything yet. Is you phone detected when you type "adb devices" in windows cmd?
k3lcior said:
Tbh not sure i got my A50 just recently, didn't even flash anything yet. Is you phone detected when you type "adb devices" in windows cmd?
Click to expand...
Click to collapse
tried it, it doesn't recognize the phone.
is there anyway to figure out if it's a hardware issue?
cuz I've heard it's a somewhat common problem in the A50 for the hard drive/storage to go corrupt.
SallyTheDevil said:
is there anyway to figure out if it's a hardware issue?
cuz I've heard it's a somewhat common problem in the A50 for the hard drive/storage to go corrupt.
Click to expand...
Click to collapse
Connect the phone to pc,press same time volume up and down.You will boot on download mode.Then flash firmware
SallyTheDevil said:
here's what happened, the phone started freezing and restarting every 5 mins, I uninstalled some apps thinking that's what's causing it, I used it for around 10 minutes and it was fine, installed the latest security patch update, restarted and everything looked fine.
plugged it in, saw it had restarted again and it was stuck on the Samsung Galaxy A50 secured by Knox screen,
rn: I can't enter recovery mode, (the phone won't shut down and releasing the volume down and holding volume up thing doesn't work)
I can only enter download mode, Connected to Odin, flashed the latest firmware and it passed successfully, but still it gets stuck and won't boot.
any ideas?:crying:
Click to expand...
Click to collapse
I am having a very similar problem to yours, so I will follow this thread. I was using my phone two days ago and it simply turned itself off and since then I am stuck in the logo screen. When the phone is loading I have no indication whatsoever of the battery percentage at all. I still can access option and factory reset and wipe cache (unlike you, apparently - but it does nothing for me). This simply does not help. I end up back at the logo Samsung Galaxy A50 screen. I have downloaded two different firmware... android 9 and 10 from Samsung mobile, and have used Odin to flash it. The process goes through ok and without errors. I get the pass message and the message that the phone is being updated. Then it is time for the logo screen again and form then on the phone simply does not start. I am lost. Can anyone help?
muhamet said:
Connect the phone to pc,press same time volume up and down.You will boot on download mode.Then flash firmware
Click to expand...
Click to collapse
done that already, it flashes the firmware successfully but still won't boot, it just gets stuck at the same screen.
JulianaO said:
I am having a very similar problem to yours, so I will follow this thread. I was using my phone two days ago and it simply turned itself off and since then I am stuck in the logo screen. When the phone is loading I have no indication whatsoever of the battery percentage at all. I still can access option and factory reset and wipe cache (unlike you, apparently - but it does nothing for me). This simply does not help. I end up back at the logo Samsung Galaxy A50 screen. I have downloaded two different firmware... android 9 and 10 from Samsung mobile, and have used Odin to flash it. The process goes through ok and without errors. I get the pass message and the message that the phone is being updated. Then it is time for the logo screen again and form then on the phone simply does not start. I am lost. Can anyone help?
Click to expand...
Click to collapse
hey there.
apart from the factory reset thing it seems like we have quite the same problem,
at this point I'm afraid it might be hardware thing
SallyTheDevil said:
hey there.
apart from the factory reset thing it seems like we have quite the same problem,
at this point I'm afraid it might be hardware thing
Click to expand...
Click to collapse
You know... I am not really sure. The only different thing I did was to accept to instal a new firmware one or two days prior. I am inclined to think that was it. Anyway... I tried to flash Android 10... Android 9 (both via Odin) and did not work. The support team instructed me to do the hard reset a couple of times ... and wipe cache and nothing. Today I sent my phone to Samsung assistance since it is still under the guarantee because that is what they thought I should do. I'll keep you posted. Hope you can get yours fixed soon.
JulianaO said:
You know... I am not really sure. The only different thing I did was to accept to instal a new firmware one or two days prior. I am inclined to think that was it. Anyway... I tried to flash Android 10... Android 9 (both via Odin) and did not work. The support team instructed me to do the hard reset a couple of times ... and wipe cache and nothing. Today I sent my phone to Samsung assistance since it is still under the guarantee because that is what they thought I should do. I'll keep you posted. Hope you can get yours fixed soon.
Click to expand...
Click to collapse
yh I installed that update too and this happened later the same night.
unfortunately for me all the shops n services are currently shut down because of the Co-Vid situation so i have to wait for now.
thanks for sharing, lemme know what happens.
I've had these same problems before. When flashing with Odin, don't populate the last slot with anything (the HOME_CSC slot). Flash it to the device without auto reboot on, restart the device manually and hold vol up + down to get to blue scrern, then unlock bootloader. Let it restart, then reflash ROM.