Hi everyone,
Being the more adventurous kind of person I am, and also rather sick of LG's android overlay, I decided to finally try rooting and installing a custom ROM, as my previous device was the Nexus 5, and I longed to return to the stock android world. It is a first for me to try this, so I read a few forum posts about it, and finally I rooted my G3 (D855 model), which went flawlessly. I then installed cyanogenmod 12 (I cannot remember which version, it was the most recent at the time) and I was finally satisfied by the software, which was as smooth as butter, unlike LGs skin. After a few months, I made the terrible mistake of installing one of the updates that where suggested, and then the problems began. While the phone was performing the update, it froze on the "optimizing apps" screen, and stayed so for several hours, until I decided to pull the plug on it, and it slowly died of a flat battery. I then tried to reboot the device, which stayed on the LG logo screen for a long time, until I again had to leave it to die. I then rebooted into TWRP recovery, which was the recovery I had installed and used to install CM12, and I tried to recover from the last backup I had performed a week prior about, and it failed with "error executing binary in script". After some googling, I found a forum where someone recommended to wipe the cache, data, system, and dalvik partitions. Having done this , the backup was successful and the phone was up again. A few days later I saw that CM13 with android M was released for the G3, and I decided to try it. I downloaded the rom, backed up my old version again and flashed it with TWRP. It worked, and the device booted into CM13, but I was greeted with a "process has crashed" message. I dismissed it, and the OS seemed to work, but then I realised it failed to recognize my SD card, and the phone internal memory (I own the 32GB model) was listed at a mighty 2gb. I decided to return to CM12 for the moment, so I rebooted into recovery, flashed the backup and got the same "error executing binary in script". I then wiped the cache, data, system, and dalvik partitions, and flashed my backup with no error. The phone reeboted, showed the LG screen, and then went black, then the LG screen, then black, etc... I quickly discovered this to be a boot loop. After some attempts to fix this, the phone booted to the LG screen, then the Cm logo pulsing, and then the "optimising apps". At the end of the process, the lock screen appeared, and after unlocking the device, I discovered it was back in CM13. This was suprising, and the errors I previously had were still here, so I returned to TWRP and tried to flash the original CM12 file I had, and this showed no error. After booting the device, CM13 greeted me again. I decided the device was seemingly possessed, and made the decision to unroot and reinstall into factory settings. But the first step of this process was out of reach, as the phone goes no further then the "download mode" screen with the small blue dots in the middle when I hold the volume down and plug it into the PC. After an hour on said screen, I pulled the plug and tried to reboot again. CM13 appeared once again, as if it was haunting my dreams, and I also found out that TWRP is no longer accessible, as the device stays on the blue loading screen of TWRP.
I have searched and not found anything saying how to get any further then this. I know that as I am not very experienced with this, it was rather foolish to act as I did, so spare me the lectures about that. But I didn't learn to ride a bike without falling off it, so it's kind of the same isn't it? Anyhow, is there someone out there who may assist me?
Many thanks to anyone who has any advice, I'm sick of my backup samsung S3 D:
Ed
Related
Hi folks,
I had my G920P on PB6 base, with TWRP from here; http://forum.xda-developers.com/spr...nt/tool-utility-twrp-3-0-0-1-teamwin-t3335260, and installed TeamSPR 3.6 ROM (http://forum.xda-developers.com/sprint-galaxy-s6/development/teamspr-rom-v3-t3380648). All was running dandy.
Then one day, I flashed @tdhite 's SkyHigh kernel (v3.2, can be grabbed here; http://forum.xda-developers.com/sprint-galaxy-s6/development/kernel-skyhigh-mm-6-0-1-kernel-t3350673). All was smooth.
Then I wanted to revert back to the default kernel that shipped with TeamSPR ROM, so extracted the boot.img from the ROM zip, and used Flashify (got latest from the Play Store) to flash it. This is where things went downhill.
Upon rebooting, and entering recovery, nothing happened. I don't recall what happened at this point (whether I rebooted, or went to flash SkyHigh zip again, because I was panicking?), but upon attempting to reboot, I entered this bootloop from hell, in which the ROM would not get past the "samsung" screen (I am assuming the equivalent of the Sprint LTE screen, since the TeamSPR ROM replaces that with the international screen :good.
In desperation, I booted into recovery, made a nandroid backup, and took out everything I wanted out of the device.
Then, I went here; http://forum.xda-developers.com/spr...ide-links-files-update-root-restore-t3366862/
got the latest (PF4) TAR (yes, MD5 checked out), wiped the phone from TWRP (system/data/cache/internal storage), and ODIN-ed that.
According to ODIN, all went without a hitch.
When the phone rebooted, it went into stock recovery, and it displayed a "applying update" message, followed by "erasing...", and then "applying update". And then, abruptly rebooted itself.
Bootup now went to the Sprint logo, and then "optimizing apps" green/teal screen (it optimizes 32 apps, for whatever it's worth). Almost instantly after the 32nd app is "optimized", the phone reboots again, and this bootloop restarts.
If I broke the loop by going to recovery (still stock recovery at this point), I am greeted again with with "applying update" message, but then I get the dreadful android with an exclamation point sign on top, undoubtedly having failed to apply whatever updated it was trying to do.
Pressing the power button at this stage, gets me to the stock recovery.
Here, I wiped cache, and did a factory reset. Both yielded no different behavior upon reboot from what has been outlined post-ODIN flash.
(I have tried versions 3.10.6 and 3.11.1 of ODIN, by the way - same result).
I got the latest TWRP available (link posted here; http://forum.xda-developers.com/spr...ide-links-files-update-root-restore-t3366862/), wiped system/cache/data/internal storage, and installed TeamSPR ROM (but not their 3.6 OTA). Rebooted the device, but the device goes into bootloop again on the flashing "Samsung" screen, so back to square 1.
At this point, I am not sure what else to try. The phone is a paperweight at this point, and I am really hoping for it not to remain as such.
Ideas?
Thanks in advance!
nostrings said:
Hi folks,
I had my G920P on PB6 base, with TWRP from here; http://forum.xda-developers.com/spr...nt/tool-utility-twrp-3-0-0-1-teamwin-t3335260, and installed TeamSPR 3.6 ROM (http://forum.xda-developers.com/sprint-galaxy-s6/development/teamspr-rom-v3-t3380648). All was running dandy.
Then one day, I flashed @tdhite 's SkyHigh kernel (v3.2, can be grabbed here; http://forum.xda-developers.com/sprint-galaxy-s6/development/kernel-skyhigh-mm-6-0-1-kernel-t3350673). All was smooth.
Then I wanted to revert back to the default kernel that shipped with TeamSPR ROM, so extracted the boot.img from the ROM zip, and used Flashify (got latest from the Play Store) to flash it. This is where things went downhill.
Upon rebooting, and entering recovery, nothing happened. I don't recall what happened at this point (whether I rebooted, or went to flash SkyHigh zip again, because I was panicking?), but upon attempting to reboot, I entered this bootloop from hell, in which the ROM would not get past the "samsung" screen (I am assuming the equivalent of the Sprint LTE screen, since the TeamSPR ROM replaces that with the international screen :good.
In desperation, I booted into recovery, made a nandroid backup, and took out everything I wanted out of the device.
Then, I went here; http://forum.xda-developers.com/spr...ide-links-files-update-root-restore-t3366862/
got the latest (PF4) TAR (yes, MD5 checked out), wiped the phone from TWRP (system/data/cache/internal storage), and ODIN-ed that.
According to ODIN, all went without a hitch.
When the phone rebooted, it went into stock recovery, and it displayed a "applying update" message, followed by "erasing...", and then "applying update". And then, abruptly rebooted itself.
Bootup now went to the Sprint logo, and then "optimizing apps" green/teal screen (it optimizes 32 apps, for whatever it's worth). Almost instantly after the 32nd app is "optimized", the phone reboots again, and this bootloop restarts.
If I broke the loop by going to recovery (still stock recovery at this point), I am greeted again with with "applying update" message, but then I get the dreadful android with an exclamation point sign on top, undoubtedly having failed to apply whatever updated it was trying to do.
Pressing the power button at this stage, gets me to the stock recovery.
Here, I wiped cache, and did a factory reset. Both yielded no different behavior upon reboot from what has been outlined post-ODIN flash.
(I have tried versions 3.10.6 and 3.11.1 of ODIN, by the way - same result).
I got the latest TWRP available (link posted here; http://forum.xda-developers.com/spr...ide-links-files-update-root-restore-t3366862/), wiped system/cache/data/internal storage, and installed TeamSPR ROM (but not their 3.6 OTA). Rebooted the device, but the device goes into bootloop again on the flashing "Samsung" screen, so back to square 1.
At this point, I am not sure what else to try. The phone is a paperweight at this point, and I am really hoping for it not to remain as such.
Ideas?
Thanks in advance!
Click to expand...
Click to collapse
Everything you have said is normal. EXCEPT rebooting after optimizing apps.
What I suggest, is power down phone COMPLETELY via TWRP. Boot phone to download mode. Flash PF4 TAR.
Let it do its thing, including rebooting to recovery to apply the update. But pay close attention!! After it shuts down to reboot to Android, interrupt it and go straight to recovery. Then WIPE data/factory reset from stock recovery.
Then reboot to Android.
nostrings said:
Hi folks,
I had my G920P on PB6 base, with TWRP from here; http://forum.xda-developers.com/spr...nt/tool-utility-twrp-3-0-0-1-teamwin-t3335260, and installed TeamSPR 3.6 ROM (http://forum.xda-developers.com/sprint-galaxy-s6/development/teamspr-rom-v3-t3380648). All was running dandy.
Then one day, I flashed @tdhite 's SkyHigh kernel (v3.2, can be grabbed here; http://forum.xda-developers.com/sprint-galaxy-s6/development/kernel-skyhigh-mm-6-0-1-kernel-t3350673). All was smooth.
Then I wanted to revert back to the default kernel that shipped with TeamSPR ROM, so extracted the boot.img from the ROM zip, and used Flashify (got latest from the Play Store) to flash it. This is where things went downhill.
Upon rebooting, and entering recovery, nothing happened. I don't recall what happened at this point (whether I rebooted, or went to flash SkyHigh zip again, because I was panicking?), but upon attempting to reboot, I entered this bootloop from hell, in which the ROM would not get past the "samsung" screen (I am assuming the equivalent of the Sprint LTE screen, since the TeamSPR ROM replaces that with the international screen :good.
In desperation, I booted into recovery, made a nandroid backup, and took out everything I wanted out of the device.
Then, I went here; http://forum.xda-developers.com/spr...ide-links-files-update-root-restore-t3366862/
got the latest (PF4) TAR (yes, MD5 checked out), wiped the phone from TWRP (system/data/cache/internal storage), and ODIN-ed that.
According to ODIN, all went without a hitch.
When the phone rebooted, it went into stock recovery, and it displayed a "applying update" message, followed by "erasing...", and then "applying update". And then, abruptly rebooted itself.
Bootup now went to the Sprint logo, and then "optimizing apps" green/teal screen (it optimizes 32 apps, for whatever it's worth). Almost instantly after the 32nd app is "optimized", the phone reboots again, and this bootloop restarts.
If I broke the loop by going to recovery (still stock recovery at this point), I am greeted again with with "applying update" message, but then I get the dreadful android with an exclamation point sign on top, undoubtedly having failed to apply whatever updated it was trying to do.
Pressing the power button at this stage, gets me to the stock recovery.
Here, I wiped cache, and did a factory reset. Both yielded no different behavior upon reboot from what has been outlined post-ODIN flash.
(I have tried versions 3.10.6 and 3.11.1 of ODIN, by the way - same result).
I got the latest TWRP available (link posted here; http://forum.xda-developers.com/spr...ide-links-files-update-root-restore-t3366862/), wiped system/cache/data/internal storage, and installed TeamSPR ROM (but not their 3.6 OTA). Rebooted the device, but the device goes into bootloop again on the flashing "Samsung" screen, so back to square 1.
At this point, I am not sure what else to try. The phone is a paperweight at this point, and I am really hoping for it not to remain as such.
Ideas?
Thanks in advance!
Click to expand...
Click to collapse
You have to let it die completely, and when it does die boot into download mode continuously until it wonr anymore (completely dead), and charge until 15% (incase u have to try again). Should b fixed
nostrings said:
Hi folks,
. . .
so extracted the boot.img from the ROM zip, and used Flashify (got latest from the Play Store) to flash it. This is where things went downhill.
. . .
Click to expand...
Click to collapse
The post above (assuming this gets there in time) about killing the battery and restarting is correct (generally).
But what you did was not correct (in the quote). You cannot simply pull a boot image, restore that and presume that's enough. The reason is at boot, before selinux is turned down to permissive (init.d processing usually), your file contexts will likely not be correct. There are many commands in the flash updater-script handlers that fixup the permissions to match the ramdisk used. Additionally, there will probably exist inconsistent init.d handling, or otherwise none at all (i.e., with a stock boot.img).
My Skyhigh kernels generally fixes up the permissions in updater-script, even for ROMs that did not set up their initial files contexts correctly, so things will be smooth as you note. Going back to an improperly formed kernel flash, or just pulling the boot image and forcing it into place is not a good idea in general. Flash the full kernel flash next time so it can do its work. Or ask for help first -- we can get you settled.
Let ur s6 die meaning go to odin mode let it sit for hours until it auto shuts off ..while off plug in cable charge to about 10% plug off cable go into recovery first wipe data and cache n restart ...and wallah ur phone is fixed ...hit like it will help...100% this will work on ur phone
nostrings said:
Hi folks,
I had my G920P on PB6 base, with TWRP from here; http://forum.xda-developers.com/spr...nt/tool-utility-twrp-3-0-0-1-teamwin-t3335260, and installed TeamSPR 3.6 ROM (http://forum.xda-developers.com/sprint-galaxy-s6/development/teamspr-rom-v3-t3380648). All was running dandy.
Then one day, I flashed @tdhite 's SkyHigh kernel (v3.2, can be grabbed here; http://forum.xda-developers.com/sprint-galaxy-s6/development/kernel-skyhigh-mm-6-0-1-kernel-t3350673). All was smooth.
Then I wanted to revert back to the default kernel that shipped with TeamSPR ROM, so extracted the boot.img from the ROM zip, and used Flashify (got latest from the Play Store) to flash it. This is where things went downhill.
Upon rebooting, and entering recovery, nothing happened. I don't recall what happened at this point (whether I rebooted, or went to flash SkyHigh zip again, because I was panicking?), but upon attempting to reboot, I entered this bootloop from hell, in which the ROM would not get past the "samsung" screen (I am assuming the equivalent of the Sprint LTE screen, since the TeamSPR ROM replaces that with the international screen :good.
In desperation, I booted into recovery, made a nandroid backup, and took out everything I wanted out of the device.
Then, I went here; http://forum.xda-developers.com/spr...ide-links-files-update-root-restore-t3366862/
got the latest (PF4) TAR (yes, MD5 checked out), wiped the phone from TWRP (system/data/cache/internal storage), and ODIN-ed that.
According to ODIN, all went without a hitch.
When the phone rebooted, it went into stock recovery, and it displayed a "applying update" message, followed by "erasing...", and then "applying update". And then, abruptly rebooted itself.
Bootup now went to the Sprint logo, and then "optimizing apps" green/teal screen (it optimizes 32 apps, for whatever it's worth). Almost instantly after the 32nd app is "optimized", the phone reboots again, and this bootloop restarts.
If I broke the loop by going to recovery (still stock recovery at this point), I am greeted again with with "applying update" message, but then I get the dreadful android with an exclamation point sign on top, undoubtedly having failed to apply whatever updated it was trying to do.
Pressing the power button at this stage, gets me to the stock recovery.
Here, I wiped cache, and did a factory reset. Both yielded no different behavior upon reboot from what has been outlined post-ODIN flash.
(I have tried versions 3.10.6 and 3.11.1 of ODIN, by the way - same result).
I got the latest TWRP available (link posted here; http://forum.xda-developers.com/spr...ide-links-files-update-root-restore-t3366862/), wiped system/cache/data/internal storage, and installed TeamSPR ROM (but not their 3.6 OTA). Rebooted the device, but the device goes into bootloop again on the flashing "Samsung" screen, so back to square 1.
At this point, I am not sure what else to try. The phone is a paperweight at this point, and I am really hoping for it not to remain as such.
Ideas?
Thanks in advance!
Click to expand...
Click to collapse
Hey bud thats that constant rebooting issue yes it reboots about ten times before it can optimize those apps then if u do get to start up itll still reboot every min right. well let it die completly man die so much it wont turn on at all then plug it in aand turn it on bingo
I'm not sure if anyone mentioned this but there is a Soft Power-Off(basically the same effect as pulling out your battery) on a Samsung Galaxy S6. All you need to do is Hold volume down and the power button.
tdhite said:
The post above (assuming this gets there in time) about killing the battery and restarting is correct (generally).
But what you did was not correct (in the quote). You cannot simply pull a boot image, restore that and presume that's enough. The reason is at boot, before selinux is turned down to permissive (init.d processing usually), your file contexts will likely not be correct. There are many commands in the flash updater-script handlers that fixup the permissions to match the ramdisk used. Additionally, there will probably exist inconsistent init.d handling, or otherwise none at all (i.e., with a stock boot.img).
My Skyhigh kernels generally fixes up the permissions in updater-script, even for ROMs that did not set up their initial files contexts correctly, so things will be smooth as you note. Going back to an improperly formed kernel flash, or just pulling the boot image and forcing it into place is not a good idea in general. Flash the full kernel flash next time so it can do its work. Or ask for help first -- we can get you settled.
Click to expand...
Click to collapse
The letting it die has done it. I am still not sure why it worked, but I am really glad it did. Thank you!!!
RE: writing boot.img into BOOT partition manually. Yeah, not the best idea to go about it (to put it nicely ). My line of thinking was, any file contexts would have been set by the init.d scripts that run as a result of your kernel having been previously flashed. Clearly, I paid for this assumption with an entire day of panic. There's so much I still have to learn about kernel development, and especially for our devices.
Trpling said:
I'm not sure if anyone mentioned this but there is a Soft Power-Off(basically the same effect as pulling out your battery) on a Samsung Galaxy S6. All you need to do is Hold volume down and the power button.
Click to expand...
Click to collapse
I did do that multiple times, to no avail.
So my phone has been perfect for over a year. Within the first month of owning it I rooted, installed TWRP, and jumped on CM13. Been updating nightlies all year long once every week or so and enjoying the phone. Its really been perfect. Tonight after work I jump in my car, throw it on my car charger, and drive home. When I get home I notice for some reason I have no cell service (Emergency Call Only) so I reboot. That was the end. The reboot got stuck on the CM boot screen flashing the circle out around the CM face over and over and over. So, I pop the battery, try again, same thing.
Well, being that I have rooted and flashed for years now I figured Id wipe dalvik and cache. Tried that, same thing. Did a full wipe and reinstalled the nightly from my SD card. This time I thought I made progress as it set up all the apps. Then it just hangs on "starting apps" and then it sits there forever. Never boots. Doesnt loop or restart or anything, just says its starting apps.
So, jump on here and find the bootloop issue. My serial is 505x so I was wondering if maybe thats my issue. Decide to download the all in one flash zip from here...
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
and I flash that. Stock rom works without any issue. Fired it up, logged in, no problems. Huh. Do a restart and even though I flashed that file it still shows bootloader unlocked as the LG logo comes up, and boots into TWRP as normal as well. Figured well I flashed a stock rom, lets give CM13 a try again. I download a fresh nightly through my pc and transfer it over via usb so I know its good. Full wipe, flash, reboot, hangs at "starting apps" again.
Now I am lost. The stock rom sucks and my love for this phone is based around what it is with CM installed. Am I missing something here? I really want to get back to CyanogenMod and away from the clunky slow stock rom.
Any input is greatly appreciated. Thank you all.
EDIT: Well went through the Android setup steps after flashing the stock rom so I would have a phone until this was all figured out. Turned out its not working. After setup I am not getting "Process System Isn't Reponding: wait or close" No matter what I do the phone is so slow or laggy I cant use it. Its trying to download my apps and restore my phone from my Google account but it just hangs up. No idea what to do at this point. Is my kernel messed up? Its a totally clean flash. What the heck. 3am, I give up, hopefully someone has insight in the morning. Thank you all.
ride1226 said:
So my phone has been perfect for over a year. Within the first month of owning it I rooted, installed TWRP, and jumped on CM13. Been updating nightlies all year long once every week or so and enjoying the phone. Its really been perfect. Tonight after work I jump in my car, throw it on my car charger, and drive home. When I get home I notice for some reason I have no cell service (Emergency Call Only) so I reboot. That was the end. The reboot got stuck on the CM boot screen flashing the circle out around the CM face over and over and over. So, I pop the battery, try again, same thing.
Well, being that I have rooted and flashed for years now I figured Id wipe dalvik and cache. Tried that, same thing. Did a full wipe and reinstalled the nightly from my SD card. This time I thought I made progress as it set up all the apps. Then it just hangs on "starting apps" and then it sits there forever. Never boots. Doesnt loop or restart or anything, just says its starting apps.
So, jump on here and find the bootloop issue. My serial is 505x so I was wondering if maybe thats my issue. Decide to download the all in one flash zip from here...
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
and I flash that. Stock rom works without any issue. Fired it up, logged in, no problems. Huh. Do a restart and even though I flashed that file it still shows bootloader unlocked as the LG logo comes up, and boots into TWRP as normal as well. Figured well I flashed a stock rom, lets give CM13 a try again. I download a fresh nightly through my pc and transfer it over via usb so I know its good. Full wipe, flash, reboot, hangs at "starting apps" again.
Now I am lost. The stock rom sucks and my love for this phone is based around what it is with CM installed. Am I missing something here? I really want to get back to CyanogenMod and away from the clunky slow stock rom.
Any input is greatly appreciated. Thank you all.
EDIT: Well went through the Android setup steps after flashing the stock rom so I would have a phone until this was all figured out. Turned out its not working. After setup I am not getting "Process System Isn't Reponding: wait or close" No matter what I do the phone is so slow or laggy I cant use it. Its trying to download my apps and restore my phone from my Google account but it just hangs up. No idea what to do at this point. Is my kernel messed up? Its a totally clean flash. What the heck. 3am, I give up, hopefully someone has insight in the morning. Thank you all.
Click to expand...
Click to collapse
You really have to investigate by adb. Look into the dmesg output and logcat as well. Maybe your sdcard is corrupt or 100 other issues are possible as well. What device do you own? H811? unlocked?
.
I have rooted my lg g4 h811 and am trying to flash cm 14, after flashing it through twrp, my phone stuck in bootloop. i try o put it in recovery but it only gives me factory reset option which i did several times but still stuck on bootloop. what should i do?
kunate said:
I have rooted my lg g4 h811 and am trying to flash cm 14, after flashing it through twrp, my phone stuck in bootloop. i try o put it in recovery but it only gives me factory reset option which i did several times but still stuck on bootloop. what should i do?
Click to expand...
Click to collapse
There are several users reporting that the latest cm version bootloop the best option is to start in download mode and Flash with LGUP Stock ROM.
You could also try to boot into Download Mode and then flash the latest twrp and then Boot into Factory Reset Mode again
After recovering from a previous bootloop issue with my Tab S, I'm in the same situation after flashing the official Samsung stock ROM for KitKat 4.4.2 via Odin.
When the ROM was first flashed, the tablet began working as per normal with the exception of it taking 10+ minutes to fully reboot and the device somehow restarting itself and loading the display within a second. However, after a few days, I kept receiving pop-up windows on the tablet stating that different applications (most of them I didn't have opened or running in the background at the time) weren't responding. A couple of days after that, more of said pop-up windows kept appearing on the screen, sometimes freezing the whole device until a push notification appeared in the background or the device force-rebooted itself.
I flashed the ROM again once or twice and cleared the cache partition to see if that made any difference, which it unfortunately didn't. I also removed the microSD card and SIM card, force-rebooting the device without them, and then with them when that test failed.
Now, for roughly about a week, the tablet has been stuck in a bootloop (the splash screen animation) where I have left it to drain the battery, leave it for about a day or so, and recharged it to 100%. So far there hasn't been any success.
Today I finally factory reset it to see if that may help, and the only thing that has changed is that the sound of the device rebooting is now playing when it does transition to the loading screen, which I had turned off previously when the tablet was still working.
Is there anything else that I may have missed that could help it work again? It's not rooted (and I would very much prefer to keep it that way) and has not had a custom ROM installed or flashed onto it. It can still enter Download Mode and Recovery Mode, but other than that and being about to use the Power-Volume Down technique, there's not much else I can do with it so far.
AussieMouse said:
After recovering from a previous bootloop issue with my Tab S, I'm in the same situation after flashing the official Samsung stock ROM for KitKat 4.4.2 via Odin.
When the ROM was first flashed, the tablet began working as per normal with the exception of it taking 10+ minutes to fully reboot and the device somehow restarting itself and loading the display within a second. However, after a few days, I kept receiving pop-up windows on the tablet stating that different applications (most of them I didn't have opened or running in the background at the time) weren't responding. A couple of days after that, more of said pop-up windows kept appearing on the screen, sometimes freezing the whole device until a push notification appeared in the background or the device force-rebooted itself.
I flashed the ROM again once or twice and cleared the cache partition to see if that made any difference, which it unfortunately didn't. I also removed the microSD card and SIM card, force-rebooting the device without them, and then with them when that test failed.
Now, for roughly about a week, the tablet has been stuck in a bootloop (the splash screen animation) where I have left it to drain the battery, leave it for about a day or so, and recharged it to 100%. So far there hasn't been any success.
Today I finally factory reset it to see if that may help, and the only thing that has changed is that the sound of the device rebooting is now playing when it does transition to the loading screen, which I had turned off previously when the tablet was still working.
Is there anything else that I may have missed that could help it work again? It's not rooted (and I would very much prefer to keep it that way) and has not had a custom ROM installed or flashed onto it. It can still enter Download Mode and Recovery Mode, but other than that and being about to use the Power-Volume Down technique, there's not much else I can do with it so far.
Click to expand...
Click to collapse
Factory reset, install stock firmware, wait ten minutes and you should be good.
But why kitkat? MM is available and working well.
ashyx said:
Factory reset, install stock firmware, wait ten minutes and you should be good.
But why kitkat? MM is available and working well.
Click to expand...
Click to collapse
It worked! Thank you so very much!
And I'm not a huge fan of updating my Android devices due to past experiences, but if this happens again, I might just update it to Marshmallow.
ashyx said:
Factory reset, install stock firmware, wait ten minutes and you should be good.
But why kitkat? MM is available and working well.
Click to expand...
Click to collapse
@ashyx
i love you man...this worked for me too...thank you...now i need to reinstall TWRP again and see what's cooking......
I had this problem recently too, with the added complexity that the "Factory Reset" option in recovery wasn't working -- it would say something like "MDM does not allow factory reset" and then just reboot.
Fixed it by directly flashing TWRP with heimdall, then booting into the new TWRP recovery, performing a factory reset, and then rebooting the OS. This time it got pass the bootloop.
i flashed new twrp for T700 it's bootloop cannot enter the twrp menu keep bootlooping ...what's the solution for this?please help
Help ME!
What are "stock firmware" and "MM"? and where to get it?
I've replaced the power button thinking it was a hardware issue but now I'm not sure. I've also installed a few different stock roms but still have the same problem. Does anyone have any insight as to what could be going wrong and what I can try to get it fixed? Thanks for any help you can give. The device is a Samsung SM T-800
A few months ago, the display broke on my Moto Z Play. It took me awhile, but I finally got a replacement display.
During the time I was not using it (starting immediately after it broke) it would make the sounds for my calendar notifications as they would come up, and continued to do so until the battery died.
While the battery was dead, I carefully took off the remnants of the old broken LCD.
About two weeks before I got the new display, I plugged it into my computer to see if I could pull any of my information off of it. Unfortunately, I was unable to get it to show up as a drive on my computer so I couldn't pull anything off of it.
Since it had power, it once again made sounds for my calendar notifications until the battery died.
I got my new display in the mail a couple days ago. I set about installing it and after I was done, I charged the battery to 96%. The charging screen appeared perfectly normal. I had no indication that there was going to be any problem when I went to use it until I powered it on at 96%. It looked like it was going to boot up just fine and made it three screens (not counting the triangle screen) into the boot up process and restarted the process.
The last time the phone was fully functional (as well as while it was on with a broken LCD) it was running OmniROM and it has TWRP 3.2.1-0 recovery on it.
First I tried clearing the cache and dalvik cache. That didn't help. Then, as I keep a copy of the zip for that ROM on my SD card, I decided to reflash OmniROM and 8.1 gapps. That didn't help. So, I decided to do a nandroid backup. It got part of the way through the back up and failed at system image. So, I decided to try to backup my data so that I can at least hopefully restore some of it at a later date on my computer or something. Thankfully, I was able to successfully backup my data partition.
After the backup finished, I decided to attempt to dirty flash CosmicOS.
However, I experienced the same boot loop.
I then did a full wipe and did a clean flash of OmniROM.
Still: the triangle screen, 3 seconds of the boot process and then it starts over again.
I am lost as to what to do now.
Help!
Hello?...
Okay, so i have an LG G3 D855, few months ago it worked like a charm.. But then shortly after i started noticing random reboots everytime during using apps. Then it went in bootloop. I tried to turn it on again, entered recovery screen, choosed factory reset and it did, but then it went through the same process, random restart. Eventually stuck up in factory resetting screen. However i think i made mistake when the phone freezed in reset screen : pulling out the battery. later it lost its IMEI & kept heating up (probably tried to find its cellular framework of some sort).
Days passed, several factory resets has been done. Now the phone's at its worst state. It refused to get past the boot logo. everytime it finishes booting, the display just goes black, tried to plug usb charger, chargin indicator doesn't want to turn on, neither after i pulled out the battery. I have to leave it a few days to get it working again, but it keeps persisting.
Addition : The phone's also feels warm post the blackscreen.
Any thoughts whether can this be fixed or i have to replace something inside the phone's board?
thanks in advance.
Sussudioo said:
Okay, so i have an LG G3 D855, few months ago it worked like a charm.. But then shortly after i started noticing random reboots everytime during using apps. Then it went in bootloop. I tried to turn it on again, entered recovery screen, choosed factory reset and it did, but then it went through the same process, random restart. Eventually stuck up in factory resetting screen. However i think i made mistake when the phone freezed in reset screen : pulling out the battery. later it lost its IMEI & kept heating up (probably tried to find its cellular framework of some sort).
Days passed, several factory resets has been done. Now the phone's at its worst state. It refused to get past the boot logo. everytime it finishes booting, the display just goes black, tried to plug usb charger, chargin indicator doesn't want to turn on, neither after i pulled out the battery. I have to leave it a few days to get it working again, but it keeps persisting.
Addition : The phone's also feels warm post the blackscreen.
Any thoughts whether can this be fixed or i have to replace something inside the phone's board?
thanks in advance.
Click to expand...
Click to collapse
Reflash with lgup.
Remove the SIM card and the memory card. try again. Full wipe system data ...
I've had the same problem. I've tried. Worked
found the problem. memory card
EDIT: Some kind of voodoo happened right now! I was about to unbrick again and wanted to give the phone a try to boot before. And it did! So no problem at the moment, but still a strong feeling of uncertainty...
EDIT: Phone is still randomly rebooting and gets stuck in bootloops
-----
Hej guys, I really need your advice,
but first things first: Thank you very much for all of your wonderful work on custom roms and further support of older devices. I've been reading here for a few years now and was more or less happy to have up-to-date-roms for some of my phones.
Now I'm facing quite the same problem like OP did / does. Everything started with me, following this guide to root my D855 (coming from stock rom) and flash TWRP: you tube.com/watch?v=8VOgM3jLas4 (Note: The guide told me to flash "3__HacerPermisivo.zip" for updating the kernel, which I did.)
Next, I flashed a newer version of TWRP ("twrp-3.2.3-0-d855.img") than the one provided in "2__AutoRecMMD855.apk" by the guide above. I wiped dalvik and cache and after that, I flashed "lineage-15.1-20190410-nightly-d855-signed.zip", wiped dalvik and cache again and flashed "open_gapps-arm-8.1-pico-20190411.zip". I wiped dalvik and cache again and told TWRP to reboot.
Here is, where problems began to occur. The phone got into a bootloop, showing up the LG splash screen again and again instead of booting into LOS correctly and set it up. At some point I decided to remove the battery. When I did, at the same time LOS was just going to load, which I saw because of its beginning boot animation. So I screwed it up right at the wrong moment, I guess.
From here, the phone bootlooped every time, I wanted it to start. No battery acrobatics helped and on top I couldn't get it into recovery mode. Any attempts ended in bootloops. I think, this might be what is called a brick / to brick your device, isn't it? I found this guide to unbrick a D855 and followed its steps: open -freax.fr/guide-unbrick-your-lg-g3/
Believe me, it was a real pain in the ass! Because of me, messing up something or the phone getting stuck into a bootloop during the unbrick process, I had to do it 4 to 5 times until success... I have to say: I didn't follow the last steps beginning from "Root". Instead, I followed the guide from the beginning of my post.
Finally, I got "lineage-15.1-20190410-nightly-d855-signed.zip" and "open_gapps-arm-8.1-pico-20190411.zip" to run. I set it up and began to load some of my apps of my Play Store collection. While downloading, the phone froze, crashed and began to bootloop, from here unable to boot normally or to get into recovery mode. So I unbricked and flashed again (again several times because of bootloops before LOS first set up). When I got it to work again, I was able to install my apps without being trolled by the phone again. But scrolling through the eBay app froze the phone and it began bootlooping again...
You can believe me, I was about to throw the D855 against the hardest piece of wall, I could possibly find in my rage. The reason why I didn't give up at this point is, that I LOS-rommed two other D855s just a few days before. Those were my mom's and my girlfriend's and they work fine until today. I bought this third one for myself, because I was impressed, how good LOS worked on the D855s. On top I wanted to get rid of my Samsung Galaxy S4 (GT-I9515), because LOS kinda sucks on it, but this is another story...
So I figuered that the earlier LOS version I used for the women's phones, could solve the problem. So I unbricked again and flashed "lineage-15.1-20190327-nightly-d855-signed.zip" and "open_gapps-arm-8.1-pico-20190329.zip". And hell yeah, that did work! No bootloops, eBay worked fine, just everything was as I loved it on the other phones, I flashed. Until tonight. I've been lucky for almost two days, but tonight this happened: I plotted a route in Google Maps and saved it as a shortcut on my homescreen. I closed Maps and tapped the route icon. Freeze - crash - bootloop - no recovery mode! I wanted to start crying, because Maps has already worked fine yesterday. And it still does on the other two phones, which run exactly the same rom...
So now, I'm sitting here, not knowing what can be done further. I'm not a programmer / developper or any of those cracks providing us the newest software for old phones. So I just can do wild guesses. Maybe the moment I removed the battery the very first time after flashing messed something up very deep inside the phones internals and it can not be cured any more. Maybe some of you guys have experienced similar things and know a tweak or a simple step, I forgot. Anyway, I hope I can use my phone on LOS some day which I bought especially for this case.
Keep up the great work, folks!
Greets
I ordered a new mainboard. It should arrive within 3 weeks. I'll keep you updated.