I have a S7 that is FRP locked and after touching it for a while i installed the stock firmware and it worked I could do anything like normal, I shut it down and now I can't start the phone, access the recovery or charge it, I can only go into download mode with the phone plugged in the PC, or else it wont work, btw when i install the stock firmware it goes into recovery, erases the data and for some reason it goes into a weird state of charging mode but when I unplug it it goes into the loop.
Update: I'm so dumb, since the phone is new I don't know how it works and made this post, basically it needed charge, after 10 mins with that symbol it went to 2% and back to normal...
Related
The unit has been used for about 2 months and remains quite new. It was quite stable before. Yesterday night, about half an hour after plugged in for charging and with WiFi Hotspot turned on for sharing 3G data to another netbook, the unit suddenly rebooted itself. It then stopped at the start-up screen and remained there for several minutes. I kept holding the power button for a few seconds to turn it off but it then automatically reboot itself afterwards, and stopped at the start-up screen again. It means that even complete turning off is not possible.
Trying to enter into recovery mode showed the following few lines:
# MANUAL MODE #
-- Updating application...
Copying Common Apks.
Click to expand...
Click to collapse
and then it automatically rebooted again. It means that it can't enter into recovery mode normally.
It was possible to enter into download mode. And it was the first time this machine went into download mode. I run Odin Downloader and flashed the official stock ROM. After showing "Pass", the device rebooted itself. Unfortunately, it still stopped at the start-up screen, just showing "Samsung Galaxy Tab 7.0 plus". It is really troubesome. I have experience playing several Android devices before and it is the first time I face such troublesome problem.
The device is an official product. The biggest problem is that the original purchase invoice was lost and most likely that I couldn't get official support, repair service or replacement.
May I ask if anyone would kindly provide me some help or advice. Thanks!
Instead of going into download mode go into recovery mode and see if there are any errors. Your scenario is sounding very similar to the one I had in the past.
I just ran into a nasty snag at boot logo as well. nandroid, stock kernel and factory reset were no help. Try Odin back to Stock, it still may not get past boot logo, hold vol up and power to get into recovery and factory reset. Hope it works for you.
Unfortunately I was unable to get into recovery mode even after odin flashing stock ROM.
It rebooted itself a few seconds after displaying some lines of text. I can't see the normal recovery menu.
My phone is rooted with stock rom. The only changes are listed below
Froze bloat that was safe
changed bootanimation to stock samsung
replaced some apps with inverted versions of themselves (ex. google +, stock messaging)
Here goes:
I was using navigation and I noticed that my phone was off after I had finished. Nothing worked at all, I could not boot into recovery or download. I connected the phone to a charger and red led flashes and an empty battery appears. The battery was full. I could reboot the phone while on the charger, but it would shut off as soon as it got to the homescreen. While off, If I pressed the home button, the green battery would appear as if it were charging. From here I could boot into recovery and download mode. The phone will only boot into these modes while connected to the charger. Here is where it went bad. I attempted to restore a backup while the phone was on the car charger and my car charger got pulled out in the middle of a restore. No charger meant that the phone shut off mid restore. Now, when I plug in the phone, the red led appears and the empty battery with a circle inside appears and then goes away. This repeats itself over and over and the phone buzzes when the empty battery reappears. I can still boot into download mode but not recovery. If I try to flash the stock samsung rom via odin, it says that it passes, however upon automatic reboot the samsung appears and nothing else. After the samsung appears the phone just continues to buzz every 5 seconds or so as if it is trying to do something. Could it be a bootloop? I have done a ton of searching here and now I am resorting to help! Your time is appreciated and beers on me if you can help me get my phone back to normal.
Put your phone into download mode and let it sit on the charger for 30 minutes. After pull and reinsert your battery and then try to power on your phone without your charger. Then proceed to charge your phone to full since it powered on.
Sent from my Freaked VzW s3 using xda premium
This did not work but thank you for the suggestion. From what I have gathered, as long as I can get into recovery then I should be able to get everything back to normal. Anyone?
elreydenj said:
This did not work but thank you for the suggestion. From what I have gathered, as long as I can get into recovery then I should be able to get everything back to normal. Anyone?
Click to expand...
Click to collapse
if you can get into download mode, you can use odin to fix everything.
you might have to do a complete wipe but it is what it is
http://forum.xda-developers.com/showthread.php?t=1840030
read that
I tried this already. My problem is that after I flash the first bootchain, the second bootchain will not flash. I gets stuck at the setup in odin. I see there is an option to disconnect the phone and exit odin and reconnect the phone without leaving download mode if this happens. My problem is that if I disconnect the phone from the computer or from the charger it shuts off automatically. I tried these steps the best that I could and when I click nand erase and it reboots, then all it does is buzz every few seconds. I then shut it off and do the data and cache wipe and reboot. It reboots and appears to be the stock rom asking me for language and activation after, but the phone shuts off almost immediately and reboots to a blank battery with a circle in the middle. This is after I have had the phone on the charger for a long time. This happened out of the blue after I was using navigation. This problem did not arise from changing something in the system or from flashing a rom or kernel or anything of the sort. No one has seen this issue with the blank battery? I saw someone mention in android forums but the resolution was that they returned it and got a refurb.
Alright so my Nexus 5 was running perfectly on 6.0. Today I was going back home from school and I had like 2% battery. It showed the powering off window and shut down. I plugged it in the OG charger that came with it and booted it up and started using it. When it reached about 5% the phone froze and restarted. However upon reaching the Android logo it froze again and repeated the process. So I thought I should leave it for a while to charge and boot it later. Charged it fully, powered on, Android is optimizing apps showed up and froze again. Tried a completely wipe but then I got a "TZ crash Demigod Crash Handler" telling me to take a ram dump of the phone.
DEmiGod Crash Handler : HW Reset!
Press key to choose Dload Mode or Reboot.
1) Volume Up : Dload Mode.
2) Volume Down : Reboot.
If you choose Dload Mode,
Please do following action.
1) Dload Mode. Please connect USB.
2) Get the ram dump image using QPST Configuration.
Tried flashing 6.0 via fastboot hoping it would solve the problem, but to no avail. Now the phone won't boot into anything. Bootloader, recovery, nothing. It won't even show the battery logo when it's charging. I've had this phone for a year and a half, and I haven't damaged it in any way.
Is it possible that I could do something to remedy this, or is it the repair shop?
Thanks in advance
Lynuxen said:
Alright so my Nexus 5 was running perfectly on 6.0. Today I was going back home from school and I had like 2% battery. It showed the powering off window and shut down. I plugged it in the OG charger that came with it and booted it up and started using it. When it reached about 5% the phone froze and restarted. However upon reaching the Android logo it froze again and repeated the process. So I thought I should leave it for a while to charge and boot it later. Charged it fully, powered on, Android is optimizing apps showed up and froze again. Tried a completely wipe but then I got a "TZ crash Demigod Crash Handler" telling me to take a ram dump of the phone.
DEmiGod Crash Handler : HW Reset!
Press key to choose Dload Mode or Reboot.
1) Volume Up : Dload Mode.
2) Volume Down : Reboot.
If you choose Dload Mode,
Please do following action.
1) Dload Mode. Please connect USB.
2) Get the ram dump image using QPST Configuration.
Tried flashing 6.0 via fastboot hoping it would solve the problem, but to no avail. Now the phone won't boot into anything. Bootloader, recovery, nothing. It won't even show the battery logo when it's charging. I've had this phone for a year and a half, and I haven't damaged it in any way.
Is it possible that I could do something to remedy this, or is it the repair shop?
Thanks in advance
Click to expand...
Click to collapse
Try manually flashing a new kernel, seeing most of it relating to a bad boot/kernel image
PS what happens when u try dload mode?
Sent from my Nexus 6 using Tapatalk
Lynuxen said:
Alright so my Nexus 5 was running perfectly on 6.0. Today I was going back home from school and I had like 2% battery. It showed the powering off window and shut down. I plugged it in the OG charger that came with it and booted it up and started using it. When it reached about 5% the phone froze and restarted. However upon reaching the Android logo it froze again and repeated the process. So I thought I should leave it for a while to charge and boot it later. Charged it fully, powered on, Android is optimizing apps showed up and froze again. Tried a completely wipe but then I got a "TZ crash Demigod Crash Handler" telling me to take a ram dump of the phone.
DEmiGod Crash Handler : HW Reset!
Press key to choose Dload Mode or Reboot.
1) Volume Up : Dload Mode.
2) Volume Down : Reboot.
If you choose Dload Mode,
Please do following action.
1) Dload Mode. Please connect USB.
2) Get the ram dump image using QPST Configuration.
Tried flashing 6.0 via fastboot hoping it would solve the problem, but to no avail. Now the phone won't boot into anything. Bootloader, recovery, nothing. It won't even show the battery logo when it's charging. I've had this phone for a year and a half, and I haven't damaged it in any way.
Is it possible that I could do something to remedy this, or is it the repair shop?
Thanks in advance
Click to expand...
Click to collapse
Maybe help you
forum.xda-developers.com/google-nexus-5/development/tool-06-03-14-one-click-factory-restore-t2513937
jordirpz, you have no idea how much I am thankful, it's running again.
Cheers!
I have this problem. AFter fitting KDIFIX replacement back cover (replacing one that overheated when charging on an LG WCP-300 charging pad) the replacement cover caused a little heating, spontaneous reboot of the phone, THEN this "green screen of death."
Have reflashed all partitions but user data with M4B30Z ( was running an earlier one), no joy. Have disconnected the battery for a few hours in hopes that perhaps this will resolve, as the partitions were erased and flashed A-OK with SDK fastboot. :fingers-crossed:
UPDATE:
Nope, didn't do it. It won't boot to Recovery, won't get past the Google logo before restarting. Will boot into fastboot and stay there for hours. Oddly, plugging into power will cause it to boot, NOT show teh b/w battery image. I wonder if this aftermarket cover fried something in the charging circuit. Brand new replacement battery, too.
Device is a LG G3 D850, rooted, TWRP installed, stock ROM on 5.0.1
Here's the story: Yesterday I was browsing normally when the device froze up, then shut off. Wouldn't power on with the power button. I had to pull the battery and then it turned on. When the device booted back up, it was running very sluggish. Immediately noticed that the WiFi was constantly trying to turn on with no success (When entering the WiFi menu it only said "WiFi turning on"). Bluetooth would not turn on either. The battery was draining rapidly, about 20% in 30 minutes with no use. GSam Battery Monitor reported that Kernel (OS) had used 95% of the battery. I tried rebooting the phone with no success. Booted into recovery and cleared cache, no success. Couldn't find anything online besides people saying to try a different ROM/Stock rom or that they were told it was a failed motherboard. I tolerated using the phone into the night, but the battery was constantly draining and the phone temperature reported ~98 degrees even without use. The WiFi and Bluetooth never started working. Today, a few hours into the day, the phone shut off again. This time it started boot looping, going from the LG splash screen then the spinning AT&T screen, it would then hang and reboot (constantly boot looping). Battery pulls didnt help. Once or twice, the phone actually booted into the OS. After a minute it would start bootlooping again. I then booted into recovery and performed a factory reset. After the factory reset, the phone still bootlooped. I then booted into recovery and recovered to a previous nandroid backup. The phone booted up afterwards, with the WiFi actually working. After 5 minutes, the WiFi stopped working again and the phone proceeded to start bootlooping. My next attempt was to flash back to Stock ROM, using this method: http://forum.xda-developers.com/att-lg-g3/general/unroot-return-to-factory-stock-att-lg-g3-t2820827. The flash worked successfully, booting into the OS on the setup screen, but instantly started bootlooping again... The bootloop is a little different now, going from LG splash screen > Green android with blue spinning circle in his stomach > AT&T splash screen > then rebooting. I cant even get into TWRP now (When trying to boot into recovery and clicking yes on the default factory reset screen, it just reboots instead of going into TWRP) Im out of options, should I give up and buy a new device, or does somebody have any other suggestions?
ccraw said:
Device is a LG G3 D850, rooted, TWRP installed, stock ROM on 5.0.1
Here's the story: Yesterday I was browsing normally when the device froze up, then shut off. Wouldn't power on with the power button. I had to pull the battery and then it turned on. When the device booted back up, it was running very sluggish. Immediately noticed that the WiFi was constantly trying to turn on with no success (When entering the WiFi menu it only said "WiFi turning on"). Bluetooth would not turn on either. The battery was draining rapidly, about 20% in 30 minutes with no use. GSam Battery Monitor reported that Kernel (OS) had used 95% of the battery. I tried rebooting the phone with no success. Booted into recovery and cleared cache, no success. Couldn't find anything online besides people saying to try a different ROM/Stock rom or that they were told it was a failed motherboard. I tolerated using the phone into the night, but the battery was constantly draining and the phone temperature reported ~98 degrees even without use. The WiFi and Bluetooth never started working. Today, a few hours into the day, the phone shut off again. This time it started boot looping, going from the LG splash screen then the spinning AT&T screen, it would then hang and reboot (constantly boot looping). Battery pulls didnt help. Once or twice, the phone actually booted into the OS. After a minute it would start bootlooping again. I then booted into recovery and performed a factory reset. After the factory reset, the phone still bootlooped. I then booted into recovery and recovered to a previous nandroid backup. The phone booted up afterwards, with the WiFi actually working. After 5 minutes, the WiFi stopped working again and the phone proceeded to start bootlooping. My next attempt was to flash back to Stock ROM, using this method: http://forum.xda-developers.com/att-lg-g3/general/unroot-return-to-factory-stock-att-lg-g3-t2820827. The flash worked successfully, booting into the OS on the setup screen, but instantly started bootlooping again... The bootloop is a little different now, going from LG splash screen > Green android with blue spinning circle in his stomach > AT&T splash screen > then rebooting. I cant even get into TWRP now (When trying to boot into recovery and clicking yes on the default factory reset screen, it just reboots instead of going into TWRP) Im out of options, should I give up and buy a new device, or does somebody have any other suggestions?
Click to expand...
Click to collapse
Sadly that is because of a hardware issue. Been happening. A lot lately.
hyelton said:
Sadly that is because of a hardware issue. Been happening. A lot lately.
Click to expand...
Click to collapse
Alright, that's what I had read. Just seemed like a software issue so I was hoping for the best. I went ahead and ordered a new device. Im guessing a full motherboard replacement would be required to fix the device?
Recurring Issue
Hello,
The same problem happened to me a few days ago so this is trully a recurring issue.
I also tried to fix my rom by reinstalling it, then tried to install multiple new rom, and finally flashed the original stock rom. I also am stuck on the bootloop issue.
I'm going to contact LG to see if they can do anything to repaire it but my hope are very low.
I'll try to update this message if I find a solution.
Mine just started bootlooping and no wifi and today it just died. Battery pulls didnt work either no power at all. Probably going to switch to the V30 when its released.
Sent from my One using Tapatalk
ccraw said:
Device is a LG G3 D850, rooted, TWRP installed, stock ROM on 5.0.1
Here's the story: Yesterday I was browsing normally when the device froze up, then shut off. Wouldn't power on with the power button. I had to pull the battery and then it turned on. When the device booted back up, it was running very sluggish. Immediately noticed that the WiFi was constantly trying to turn on with no success (When entering the WiFi menu it only said "WiFi turning on"). Bluetooth would not turn on either. The battery was draining rapidly, about 20% in 30 minutes with no use. GSam Battery Monitor reported that Kernel (OS) had used 95% of the battery. I tried rebooting the phone with no success. Booted into recovery and cleared cache, no success. Couldn't find anything online besides people saying to try a different ROM/Stock rom or that they were told it was a failed motherboard. I tolerated using the phone into the night, but the battery was constantly draining and the phone temperature reported ~98 degrees even without use. The WiFi and Bluetooth never started working. Today, a few hours into the day, the phone shut off again. This time it started boot looping, going from the LG splash screen then the spinning AT&T screen, it would then hang and reboot (constantly boot looping). Battery pulls didnt help. Once or twice, the phone actually booted into the OS. After a minute it would start bootlooping again. I then booted into recovery and performed a factory reset. After the factory reset, the phone still bootlooped. I then booted into recovery and recovered to a previous nandroid backup. The phone booted up afterwards, with the WiFi actually working. After 5 minutes, the WiFi stopped working again and the phone proceeded to start bootlooping. My next attempt was to flash back to Stock ROM, using this method: http://forum.xda-developers.com/att-lg-g3/general/unroot-return-to-factory-stock-att-lg-g3-t2820827. The flash worked successfully, booting into the OS on the setup screen, but instantly started bootlooping again... The bootloop is a little different now, going from LG splash screen > Green android with blue spinning circle in his stomach > AT&T splash screen > then rebooting. I cant even get into TWRP now (When trying to boot into recovery and clicking yes on the default factory reset screen, it just reboots instead of going into TWRP) Im out of options, should I give up and buy a new device, or does somebody have any other suggestions?
Click to expand...
Click to collapse
It's probably to late but theres another method returning to stock KitKat dont know the link off hand in development forums. Sucks you couldnt try no adb methods. Still have the Phone want to sell it i need a cheap screen ?
My father-in-law's S6 was rebooting right after the menu screen came up. After trying numerous things which wouldn't work (still had varying boot loops) like getting into the recovery mode and doing a factory wipe, I decided to use Odin and flash the base stock Android nougat on this (it had the one verizon security patch after that, so should be no issue doing this).
That went okay and it rebooted and got all the way to "Android is starting" which you see after a firmware upgrade. But I didn't realize the battery had run down through all this so it died at this stage. So it was taking a charge now, so let it charge overnight and give it another run.
Got up today, tried to start it...back to the boot loop. So I figured I'd flash stock again with Odin (can always get back to that mode).
It completes successfully and then after the reboot at about 32% jumps to "erasing" and then the boot loop again.
Got into recovery mode once and wiped cache (pointless at this point, but whatever) and did factory reset there, then boot to bootloader. Got all the way to the verizon screen...and then boot loop again.
Is this phone just done? The only thing I can consistently get to is Odin mode. I tried the stock reflash a couple more times and keep ending up in a boot loop and it doesn't even get past the "custom" screen now. And I can't even actually get it to shutdown for that matter. I can get to the battery pull mode but if I try to power off from there, I just get the black screen with the blue light.
And, to make matters even worse, now on restart, it brings up the blue system update screen for a second, then jumps over to the no command screen, sits there for a second, then reboots again. I think I've somehow managed to even blow the recovery menu but this has all been stock and never had any custom firmware or root.
Any help/suggestions would be greatly appreciated!