Related
My phone keeps restarting after few minutes or seconds of usage in ramdump mode.
I try to unlock the bootloader, I convert it to GPE but the same problem.
Anyone can give me an advice if it can be repaired.
Thank you in advance!
Sent from my iPhone using Tapatalk
Nobody has no idea?
Sent from my iPhone using Tapatalk
a friend of mine has the same problem is GPE and it restarts in rumdump mode everything freezes .. i think this has to do with wrong rom ( drivers let's say ) or a bad hardware on the device . not 100 % sure is just my opinion
So I am new to the XDA community, but I have not found anything that discusses this already. Has anyone with the HTC 10 had the issue of the phone restarting and then getting caught in a BootLoop? I have tried going through the Recover from BootLoaded and Wiping Data/Factory Reset but I am still having this issue.
Any suggestions?
Hugglester said:
So I am new to the XDA community, but I have not found anything that discusses this already. Has anyone with the HTC 10 had the issue of the phone restarting and then getting caught in a BootLoop? I have tried going through the Recover from BootLoaded and Wiping Data/Factory Reset but I am still having this issue.
Any suggestions?
Click to expand...
Click to collapse
did you install xposed? Rooted? Any other modifications?
jollywhitefoot said:
did you install xposed? Rooted? Any other modifications?
Click to expand...
Click to collapse
Nothing, had it out of the box for about an hour.
Hugglester said:
Nothing, had it out of the box for about an hour.
Click to expand...
Click to collapse
return it then. something isn't right.
Hugglester said:
So I am new to the XDA community, but I have not found anything that discusses this already. Has anyone with the HTC 10 had the issue of the phone restarting and then getting caught in a BootLoop? I have tried going through the Recover from BootLoaded and Wiping Data/Factory Reset but I am still having this issue.
Any suggestions?
Click to expand...
Click to collapse
Hi there.
Yes I have encountered this issue. But I'm not sure if I had it from the box or I got it after the update.
When I got this issue and my phone started boot looping, the only way I tried to recover from it is by hooking up the charger and I got it too boot up, it showed an error report and I sent the error report to HTC.
So the phone works normally after it boots, but is this software related? Should I wait for the next update or also replace my phone, it's so hard after setting up everything to again go through the annoying process of getting a replacement or a fix just to find that the issue still happens or is caused by the update.
UPDATE:
Ok so after testing and trying to recreate the issue I have discovered that when trying to do a normal restart or power off the phone while the phone is on battery this issue doesn't happen.
The last time it happened is when my phone battery drained and powered off then I hook it up to the charger and went to sleep, when I woke up I removed the phone from the charger and powered it on then the issue happened and the phone went into a boot loop, tried restarting with no luck then I figured I would plug in the charger again, then it booted up normally. (Unplugging the charger from the phone makes a weird metallic noise, so I checked my USB type c port and it wasn't lose or rattly). Anyways when the phone booted up it had 99% charge while I was certain it should have been full at 100%, I waited for it till it got to a 100% then unplugged it.
So I tried my best to cover how this issue happened to me, and if it happens I would get the error report thing that the phone had unexpected boot or something like that.
Could it be because I'm using adoptable storage?
Is it hardware or software related?
Could it be a corrupt file or something in the file system?
Or I just need to wait for the next update?
So my issue came right out of the box. I was trying to get everything transferred over from my old HTC device and about half way through downloading my apps the issue started for me. Tried similar steps to you as well with charging the phone and it was only off charger when I had the issue. I am returning the phone and getting a new one as of now. Not sure what else to do to fix it.
p1r8t3 said:
Hi there.
Yes I have encountered this issue. But I'm not sure if I had it from the box or I got it after the update.
When I got this issue and my phone started boot looping, the only way I tried to recover from it is by hooking up the charger and I got it too boot up, it showed an error report and I sent the error report to HTC.
So the phone works normally after it boots, but is this software related? Should I wait for the next update or also replace my phone, it's so hard after setting up everything to again go through the annoying process of getting a replacement or a fix just to find that the issue still happens or is caused by the update.
UPDATE:
Ok so after testing and trying to recreate the issue I have discovered that when trying to do a normal restart or power off the phone while the phone is on battery this issue doesn't happen.
The last time it happened is when my phone battery drained and powered off then I hook it up to the charger and went to sleep, when I woke up I removed the phone from the charger and powered it on then the issue happened and the phone went into a boot loop, tried restarting with no luck then I figured I would plug in the charger again, then it booted up normally. (Unplugging the charger from the phone makes a weird metallic noise, so I checked my USB type c port and it wasn't lose or rattly). Anyways when the phone booted up it had 99% charge while I was certain it should have been full at 100%, I waited for it till it got to a 100% then unplugged it.
So I tried my best to cover how this issue happened to me, and if it happens I would get the error report thing that the phone had unexpected boot or something like that.
Could it be because I'm using adoptable storage?
Is it hardware or software related?
Could it be a corrupt file or something in the file system?
Or I just need to wait for the next update?
Click to expand...
Click to collapse
Hugglester said:
So my issue came right out of the box. I was trying to get everything transferred over from my old HTC device and about half way through downloading my apps the issue started for me. Tried similar steps to you as well with charging the phone and it was only off charger when I had the issue. I am returning the phone and getting a new one as of now. Not sure what else to do to fix it.
Click to expand...
Click to collapse
Hi there, i think the newer update fixed the issue for me. Hope this helps.
Any news?
HTC One M9 cihazımdan Tapatalk kullanılarak gönderildi
same issue for me, just made an update and then got the bootloop.
even ****tory reset didnt help
any idea what to do.
phone never rooted
Your phones right out of the box and on the stock rom should be in perfect working order. If not, I would send it back for a replacement pronto. Don't wait for an update.
you guys got an external sdcard in the phone?
It's reported by a couple of users that the boot up process took a few cycles for them till it booted.
It was caused by a corrupted sdcard. Try to take the external sdcard out and see if the issue is fixed.
If yes, try to format it with the overwrite option in the "SDFormatter" program..if that does not help. get a new sdcard.
El mismo problema de bootloop después de actulizar
me ocurrió el mismo problema después de actualizar mi HTC 10, luego de actualizarlo al Android 7 llegó una nueva actualización luego de completada la descarga procedió a instalarse la actualización y aquí quedo el teléfono en bootloop por más de una hora, se soluciono el problema conectando el teléfono a cargar la batería después de pocos minutos el teléfono arranco correctamente. Al completar la descarga de esta ultima actualización el teléfono tenia más del 90% de carga aun así se generó este problema de bootloop.
I am experiencing the same problem. The phone has the latest update installed. (not rooted, bootloader locked).
Initially soft (backlit) keys weren't working, so i tried restarting and it never booted up as its stuck in boot loop. I cannot go to any recovery modes.
Its so disappointing ! I'm in India but I bought this phone from middle-east on December 2016 and I have to sent it back there for warranty claim which will not happen very soon.
Have anyone found a solution for this problem ??
jeraldsm said:
I am experiencing the same problem. The phone has the latest update installed. (not rooted, bootloader locked).
Initially soft (backlit) keys weren't working, so i tried restarting and it never booted up as its stuck in boot loop. I cannot go to any recovery modes.
Its so disappointing ! I'm in India but I bought this phone from middle-east on December 2016 and I have to sent it back there for warranty claim which will not happen very soon.
Have anyone found a solution for this problem ??
Click to expand...
Click to collapse
I had a similar issue....backlit keys stop responding, a few days later the phone ran out of battery during the night and I got the boot loop when I turned it on the morning after. I can just get into the bootloader (no normal boot, no recovery, no download mode). An purchased in the US but I am now in Argentina .
Same here
I had the same issue. I factory reset a couple of times. I even rooted and installed custom ROM. But it still would do it (though much less frequently). I ultimately exchanged it with a warranty phone with my carrier. Crossing my fingers that my phone will stop doing this.
Hugglester said:
So I am new to the XDA community, but I have not found anything that discusses this already. Has anyone with the HTC 10 had the issue of the phone restarting and then getting caught in a BootLoop? I have tried going through the Recover from BootLoaded and Wiping Data/Factory Reset but I am still having this issue.
Any suggestions?
Click to expand...
Click to collapse
I have same promlem
I had the same problem... After the last update, it entered a BootLoop... It was pretty difficult to even shut down the phone! It got so hot I was afraid it's going to burn out its motherboard...
Mine is not rooted or anything of the sort...
Eventually I managed to shut it down...
Went to claim my warranty... They opened it up... Don't really know what they did... But before throwing it in the garbage... I tried one more time to power it up... And it worked !
I've stopped all the updates since and I never let it run out of battery.. It's clearly a software problem.
And it's not related to HTC only. Samsung has it too. I know for a fact that the S8 has it....
I am having the same problem , has anyone found a fix ?
I had the same problem with mine. Bought it used from Swappa and out of the box it would randomly reboot. I also noticed the phone was abnormally hot doing nothing on the lockscreen or homepage. The random reboots quickly escalated to bootloop. Unfortunately I had to return it. I think the phone during initial stages of booting up relies purely on internal battery power, regardless if it's plugged into AC power or not. So, when the internal battery is dead, in the sense that it can no longer provide sufficient power even at a fully charged state, then you get stuck in the eternal bootloop.
I believe the only fix is to replace the battery with a new cell. However, due to the complexity of the tear down, I literally could not find one shop that would be willing to do it. Otherwise, I would have sucked it up and paid to have a new battery put in.
j to the 4n said:
you guys got an external sdcard in the phone?
It's reported by a couple of users that the boot up process took a few cycles for them till it booted.
It was caused by a corrupted sdcard. Try to take the external sdcard out and see if the issue is fixed.
If yes, try to format it with the overwrite option in the "SDFormatter" program..if that does not help. get a new sdcard.
Click to expand...
Click to collapse
I've been encountering exactly this problem. Anywhere after 40% it'll just die and get stuck in a boot loop until I hook it up to a charger. If the boot loop happens multiple times before I manage to get to the charger, widgets stop working and I'll have to wipe the cache. Sometimes when the phone dies, it'll have said 20% or so before dying, but after hooking it up the charger it'll claim 2%.
So the battery or battery level sensor ain't great, that's a given. But 40% and dying? Something's wrong.
So after it completely died and refused to turn on again because it went through the boot loop until it just stopped trying, I decided to try this trick. I removed the SD card, tried everything to turn it on, finally getting it going by long-pressing volume down and power, went to recovery mode, rebooted the phone and it's working again. For now.
I'm not sure whether the SD card removal will fix the entire problem (or at least limit it to a ****ty battery) but I'll report back if that's the case. At least it got it to boot again, so thanks for at least giving me a strand of hope
In the beginning nexus 5x , h791 , 16GB was giving a warning "Your device is corrupt. It can't be trusted and may not work properly." (Red)
Although I have not done anything to change in the system.
So I left the device a week and tried to communicate with warranty . but i couldn't because I am not in the country where i purchased the device.
afer that week when i tried to boot the red led work so i put the device in the charger but still not boot no battery shows it just gives heat the battery charging but screen not showing any thing .I am sure that the battery intact . also iam sure it's software and not hardware problem.
so help me please
So you did not root there device or change recovery? That would cause that message.
Can you get to fastboot screen? Hold volume down and power at the same time. If that works load the factory image by using flash all. You can download it from googles site.
Sent from my Nexus 5X using Tapatalk
Hello everyone,
to this day I was a happy owner of Nexus 5X - it was doing pretty well, I even installed Pure Nexus ROM on this device to make it even better and this is where the trouble begins. Today I was listening to music on my device when it froze. I was like - "yeah, another freeze, I will just reboot my phone". It didn't help. The phone started rebooting, but it froze again and then the screen went black. Forever. Now my device is not responding to any commands, I can not even charge it. I still have few months of warranty left, so this is where my question begins:
is it possible for LG employees to detect that my device was rooted and so to cancel my warranty if the phone is totally dead? I think that the components died.
Thanks for your help. :good:
I had the same thing happen to me 21 days after my warranty expired. They told me the motherboard was bad and it had to be replace, and it was going to cost $72. My device was fully rooted and they made no mention of that when I asked for the full diagnostic report from their technician. I would say it is safe to say they can't tell if it was rooted if you motherboard went out like mine.
- Side note: my phone crashes almost once a day since I've gotten back and had small cracks in the back from where they pried it open. But I can't go without my phone for another 3 weeks again while they fix it.
Razeer123 said:
Hello everyone,
to this day I was a happy owner of Nexus 5X - it was doing pretty well, I even installed Pure Nexus ROM on this device to make it even better and this is where the trouble begins. Today I was listening to music on my device when it froze. I was like - "yeah, another freeze, I will just reboot my phone". It didn't help. The phone started rebooting, but it froze again and then the screen went black. Forever. Now my device is not responding to any commands, I can not even charge it. I still have few months of warranty left, so this is where my question begins:
is it possible for LG employees to detect that my device was rooted and so to cancel my warranty if the phone is totally dead? I think that the components died.
Thanks for your help. :good:
Click to expand...
Click to collapse
Sounds TOO familiar. Like exactly what happened to my first N5X mid-March. I was listening to Spotify, the device's software froze and it never turned on again. I connected it to my PC and I happened to have the dreaded Qualcomm HS-USB QDloader 9008 error (that's what showed up in Device Manager). The only thing I did different and for the first time before that happened was using F2FS. I have no idea if it's related.
theGekkoST said:
I had the same thing happen to me 21 days after my warranty expired. They told me the motherboard was bad and it had to be replace, and it was going to cost $72. My device was fully rooted and they made no mention of that when I asked for the full diagnostic report from their technician. I would say it is safe to say they can't tell if it was rooted if you motherboard went out like mine.
- Side note: my phone crashes almost once a day since I've gotten back and had small cracks in the back from where they pried it open. But I can't go without my phone for another 3 weeks again while they fix it.
Click to expand...
Click to collapse
nirogu325 said:
Sounds TOO familiar. Like exactly what happened to my first N5X mid-March. I was listening to Spotify, the device's software froze and it never turned on again. I connected it to my PC and I happened to have the dreaded Qualcomm HS-USB QDloader 9008 error (that's what showed up in Device Manager). The only thing I did different and for the first time before that happened was using F2FS. I have no idea if it's related.
Click to expand...
Click to collapse
Today the diode started to blink red, I connected Nexus 5X to charger and waited ~30 mins to charge a bit. Then I wanted to flash stock system + recovery and unroot but when booting to recovery device again stopped on Google logo and went black. From this moment no sign of beeing alive. I think I'll wait to this situation to happen again and will try to install stock firmware.
Mine would flash red when the battery was completely drained. I could plug it in and get the battery logo, but if I tried to boot it up; the screen would hit to the Google logo and then just go black. I could wait a day and the red battery light would flash again when I pressed the power button. After a few times of doing this, it wouldn't even charge anymore.
Honestly I seriously doubt they have time to go Sherlock Holmes on your phone and void your warranty. They are most likely going to get your phone see if it boots, if not replace the motherboard and go on.
Not to mention if its not responding to anything at this point what do you have to lose. Send it in and see what happens.
This problem is frequent on the Nexus 5x, V10,V20,G4 and G5, the only issu is to use heat gun on the CPU, these devices will starts normally but the problem will appear again
Envoyé de mon HTC One_M8 en utilisant Tapatalk
Same thing happened to me
Same thing happened to me last night. I tried everything I could think of, I was running the latest stock Nougat version with no root and all of a sudden the device froze. After manually powering it down, I could not get it to boot up again. No LED, battery charging icon on the screen, nothing worked, so as it was still under warranty, I got in touch with someone at Google. They've sent me a replacement device that's set to arrive tomorrow and I am to return the faulty one free of charge. Luckily my Nexus 4 still works otherwise I would've missed several calls today. I suggest you get in touch and see what they say. I know of cases where despite the phone being rooted, if they were running stock the warranty was still applicable. With your device being completely dead, you really have nothing to lose.
Okay, update - I was able to reinstall stock firmware via Nexus Root Toolkit on this device, because I booted it into fastboot and it worked for few minutes. Bootloader is still unlocked - should I wait and lock it (I don't know when will my phone be accessible again, red diode is blessing right now because it boots when it's blinking) or should I send it to repair without worrying?
I would lock it.
Okay, yesterday I flashed stock ROM + unrooted and now I locked bootloader. However the device still seems to have something wrong inside - it shows that the custom OS is installed on my phone. Should I flash again or do you recommend something else?
It shows: "Your device has loaded a different operating system". (Yellow).
How can I get rid of it?
Welcome to the boot kingdom
Envoyé de mon HTC One_M8 en utilisant Tapatalk
Razeer123 said:
Okay, yesterday I flashed stock ROM + unrooted and now I locked bootloader. However the device still seems to have something wrong inside - it shows that the custom OS is installed on my phone. Should I flash again or do you recommend something else?
It shows: "Your device has loaded a different operating system". (Yellow).
How can I get rid of it?
Click to expand...
Click to collapse
Try flashing the latest stock package manually. No toolkits. Sometimes toolkits cause flashing issues.
Sent from my Nexus 5X
nirogu325 said:
Try flashing the latest stock package manually. No toolkits. Sometimes toolkits cause flashing issues.
Sent from my Nexus 5X
Click to expand...
Click to collapse
Thanks for your reply. I succesfully flashed the stock image as you said, but unfortunately I couldn't replace recovery - the phone died and can't boot since yesterday. I'm going to take it to LG service, so keep fingers crossed
Razeer123 said:
Thanks for your reply. I succesfully flashed the stock image as you said, but unfortunately I couldn't replace recovery - the phone died and can't boot since yesterday. I'm going to take it to LG service, so keep fingers crossed
Click to expand...
Click to collapse
No worries, you are in luck.
I tried it with oreo and nougat, but it did not work, it keeps freezing.
Hello guys,
I just need your help after 2 days of searching on internet about this problem: I just updated accidentally my note 7 firmware and after the process was completed my phone died <=> black screen, not even charging or led blinking while charging and off course it's not entering in download mode/recovery menu.
I don't know what anything else to do, I was thinking to take out the battery and charge it with an universal charger, but I really don't want to unseal the back of this phone.
Did you have any ideas about this problem?
Thank you guys and I am waiting for your proposals.
Cheers !
zuzulic said:
Hello guys,
I just need your help after 2 days of searching on internet about this problem: I just updated accidentally my note 7 firmware and after the process was completed my phone died <=> black screen, not even charging or led blinking while charging and off course it's not entering in download mode/recovery menu.
I don't know what anything else to do, I was thinking to take out the battery and charge it with an universal charger, but I really don't want to unseal the back of this phone.
Did you have any ideas about this problem?
Thank you guys and I am waiting for your proposals.
Cheers !
Click to expand...
Click to collapse
Is it the first generation or second? Mine first generation is dead after several reboots for 2 weeks. It was definitely a hardware issue for me...
Envoyé de mon SM-G935F en utilisant Tapatalk
It is the first generation, but it's not a hard issue for sure, because it has been worked just fine till the update..
zuzulic said:
It is the first generation, but it's not a hard issue for sure, because it has been worked just fine till the update..
Click to expand...
Click to collapse
If you can't charge it, if you can't put it in download mode, it's definitely hardware issue...
Envoyé de mon SM-G935F en utilisant Tapatalk
I am thinking that is something from the firmware witch can control the charging process, something that doesn't allow anymore the arival of the voltage in the acumulator.And I am thinking to charge tha battery separately.But I thought that somebody has experienced already this issue.
Let's say that it will work aftet this charging process and then I will be able to boot in download mode.What firmware should I have to choose to enable the 100% percent of charging process? Is that downgrade possible? Thank.s
zuzulic said:
I am thinking that is something from the firmware witch can control the charging process, something that doesn't allow anymore the arival of the voltage in the acumulator.And I am thinking to charge tha battery separately.But I thought that somebody has experienced already this issue.
Let's say that it will work aftet this charging process and then I will be able to boot in download mode.What firmware should I have to choose to enable the 100% percent of charging process? Is that downgrade possible? Thank.s
Click to expand...
Click to collapse
The downgrade is impossible from the kill update. The only way to charge 100% it's to install a custom rom [emoji6]
Envoyé de mon SM-G935F en utilisant Tapatalk
Ok then, I will try to charge the battery and I will flash some custom rom from here.After that I will let you know about the succes or not !
zuzulic said:
Ok then, I will try to charge the battery and I will flash some custom rom from here.After that I will let you know about the succes or not !
Click to expand...
Click to collapse
Your phone is recognized by the computer? I mean do you hear the sound when you plug it?
Envoyé de mon SM-G935F en utilisant Tapatalk
No, not even a sound on the PC or a led blinking from the phone..Maybe the battery is uncharged.I mean not even one volt
zuzulic said:
No, not even a sound on the PC or a led blinking from the phone..Maybe the battery is uncharged.I mean not even one volt
Click to expand...
Click to collapse
No, no need the battery to plug it to the computer. Your phone is totally dead, sorry for you [emoji853]
Envoyé de mon SM-G935F en utilisant Tapatalk
the latest firmware killed your n7 you know, need to charging before update, and rooted then flash custom rom before your battery drop down to zero, mean if your battery 0% you cannot do anything, your n7 dead forever
Bro I had same problem i just fixed by custom ROM . You can put your phone on download mode it's fine
By the way now your phone is working on charger just try different chargers.
Hi guys , just a little info about my note 7 UK n930f experience.. I got the 0% battery kill update and I'm still at a loss on how to fix it because I didn't enable OEM unlock before it died but what I can tell you is even the it looks completely dead I can still get into download mode. ( No led's no battery symbol when charging no boot up or recovery, ) what I did to get it into download mode was :- plug the note 7 into my computer's USB and immediately hold volume down, home and power for 3 seconds then release for 1 second then immediately repeat the process for 5 times and on the fifth time when I release the buttons it shows press up for download or down to restart. Without doing it this way it just won't go into download mode but if I follow those steps exactly I can always access download mode. Very strange, but I hope it helps others... I'm on binary 3 so I can only flash v3 firmware which I believe is the 0% battery kill so can't get my phone started at all gutted
KevandLynds said:
Hi guys , just a little info about my note 7 UK n930f experience.. I got the 0% battery kill update and I'm still at a loss on how to fix it because I didn't enable OEM unlock before it died but what I can tell you is even the it looks completely dead I can still get into download mode. ( No led's no battery symbol when charging no boot up or recovery, ) what I did to get it into download mode was :- plug the note 7 into my computer's USB and immediately hold volume down, home and power for 3 seconds then release for 1 second then immediately repeat the process for 5 times and on the fifth time when I release the buttons it shows press up for download or down to restart. Without doing it this way it just won't go into download mode but if I follow those steps exactly I can always access download mode. Very strange, but I hope it helps others... I'm on binary 3 so I can only flash v3 firmware which I believe is the 0% battery kill so can't get my phone started at all gutted
Click to expand...
Click to collapse
I already fixed a Note 7 from the kill 0% update. I got the 30% firmware you need to recover your Note 7. The 30% is also a v3 firmware. Once you got the 30%, you can install a custom rom or custom kernel to get the 100% battery again [emoji6]
Envoyé de mon SM-N950F en utilisant Tapatalk
Could you tell.me which is the 30% and where is it?
KevandLynds said:
Could you tell.me which is the 30% and where is it?
Click to expand...
Click to collapse
It's in my personal Google Drive. I searched of it in the web for hours and hours. Now I m glad to share it with you. Remember to use only BL, AP and CP files cause it's firmware from Dubai. You don't need the csc. Happy to help Note 7 users [emoji6]
https://drive.google.com/file/d/0B6Uhi22wqzZIT0pKVS1aSzJrSlE/view?usp=drivesdk
Envoyé de mon SM-N950F en utilisant Tapatalk
You absolute legend, thank you so much.. my note 7 booted up for the first time this morning since I got the dredded 0% update, thank you so much
KevandLynds said:
You absolute legend, thank you so much.. my note 7 booted up for the first time this morning since I got the dredded 0% update, thank you so much
Click to expand...
Click to collapse
Good news. First step now : oem unlock, usb debug. Then you can find a custom kernel or custom rom to get back to 100% battery.
Enjoy again this amazing Note 7 ! [emoji6]
Envoyé de mon SM-N950F en utilisant Tapatalk
note 7 help
new this forum or to any forum, so sorry if I'm doing this wrong, but can anyone help with my note 7 that's been dead since the updates last year. I wnt to keep my note 7 its still new please help or point my in the direction of help thanks. and help my with doing this forum the right way if u can
NOTE 7
hi Guys, I have the note 7 and it is completely dead, but when you connect the charger and press the power button it power on and you can make calls and browse but as soon as you disconnect the charger then it goes off, and it also shows 50% battery, but you it does not charge at all so as soon as you disconnect it also goes off,
It cants go to download mode and when you connect it to the computer it does not power
please help me solve this,