At a loss... SM-920P, MM, continuous reboot loop no matter what - Sprint Samsung Galaxy S6

I upgraded to MM back the beginning of the month, tripped my Knox bit (I had rooted via PingPong root on Lollipop), but I was eager to go to MM and try Xposed so I could improve the horrible battery life.
I had the system working fine, rooted using CFAR, and no problems. Randomly, about a week ago, it just "lost" root. I wasn't sure why, and CFAR from Odin wouldn't bring it back. I did a flash with SuperSU in TRWP yesterday and it worked, and I did a NANDroid backup, saved it to my computer, and installed Xposed... On a stock ROM.
And my phone has been a continuously rebooting brick ever since, no matter what I do.
So, I've tried everything I can think of. Because my data was completely backed up, I did a complete wipe, and nothing. I tried flashing the Xposed-uninstaller.zip and that supposedly worked, but the phone reboots about 53 seconds after it starts up, continuously, no matter what.
I've tried the default MM firmware, tried letting it go through it's paces on its own (but it just reboots every 53-57 seconds), and also tried with a fresh clean default MM ROM, which does dump TRWP, then restart into the default bootloader, have it dump the cache and do a complete re-wipe, and nothing. Still restarts.
With the stock MM firmware load, the first boot it always stops at 32%, reboots, and when it comes back up it sometimes makes it through "optimizing xx of 30 applications" but always reboots and comes back to it over and over, ad infinitum. Sometimes it makes it to 30, usually it doesn't, but it always fails, reboots, and comes back to the same menu on a stock ROM.
ADP and MTP in TRWP work fine, and all my data is backed up. So, I'm willing to do anything to the device; nothing left on it to care about (I already tried NAND erase in Odin and format partitions in TRWP). It still continuously reboots at around 53 seconds.
I've also tried custom ROMs loaded up from TRWP (Renegade 1.1 and TeamSPR V3). They apparently load - everything looks/works great from inside TRWP - then invariably they reboot at about the 53 second mark. Can't even get Renegade past the boot screen.
Nothing was done hardware-wise to break it; the Knox bit flipped three weeks ago, and the SuperSU upgrade had been working fine. The action that killed it was attempting to install the Xposed framework on a default ROM that only had SuperSU installed. But I've since installed a default ROM and ran the Xposed uninstall to no avail. The uninstall Zip in TRWP gave all the right responses that it worked, but it still rebooted 53 seconds after restart. Continuously.
I don't even know how to go back to Lollipop because attempts to load G920PVPU1AOCF in Odin gives me an immediate failure of "SW REV. CHECK FAIL. DEVICE: 3, BINARY: 1," so downgrading appears to be out of the question.
Someone has to have seen something like this before or there's something I'm missing. About the only thing I can think of is to try a custom ROM install and force the Xposed framework again without even letting it boot up (because it won't anyway) from a TRWP install. I'm going to attempt that while hopefully someone else comes up with ideas for me...

rebooting
people have had luck letting their phone battery die completely and rebooting after charging just a little bit. make sure its completely discharged before rebooting
zee3are0 said:
I upgraded to MM back the beginning of the month, tripped my Knox bit (I had rooted via PingPong root on Lollipop), but I was eager to go to MM and try Xposed so I could improve the horrible battery life.
I had the system working fine, rooted using CFAR, and no problems. Randomly, about a week ago, it just "lost" root. I wasn't sure why, and CFAR from Odin wouldn't bring it back. I did a flash with SuperSU in TRWP yesterday and it worked, and I did a NANDroid backup, saved it to my computer, and installed Xposed... On a stock ROM.
And my phone has been a continuously rebooting brick ever since, no matter what I do.
So, I've tried everything I can think of. Because my data was completely backed up, I did a complete wipe, and nothing. I tried flashing the Xposed-uninstaller.zip and that supposedly worked, but the phone reboots about 53 seconds after it starts up, continuously, no matter what.
I've tried the default MM firmware, tried letting it go through it's paces on its own (but it just reboots every 53-57 seconds), and also tried with a fresh clean default MM ROM, which does dump TRWP, then restart into the default bootloader, have it dump the cache and do a complete re-wipe, and nothing. Still restarts.
With the stock MM firmware load, the first boot it always stops at 32%, reboots, and when it comes back up it sometimes makes it through "optimizing xx of 30 applications" but always reboots and comes back to it over and over, ad infinitum. Sometimes it makes it to 30, usually it doesn't, but it always fails, reboots, and comes back to the same menu on a stock ROM.
ADP and MTP in TRWP work fine, and all my data is backed up. So, I'm willing to do anything to the device; nothing left on it to care about (I already tried NAND erase in Odin and format partitions in TRWP). It still continuously reboots at around 53 seconds.
I've also tried custom ROMs loaded up from TRWP (Renegade 1.1 and TeamSPR V3). They apparently load - everything looks/works great from inside TRWP - then invariably they reboot at about the 53 second mark. Can't even get Renegade past the boot screen.
Nothing was done hardware-wise to break it; the Knox bit flipped three weeks ago, and the SuperSU upgrade had been working fine. The action that killed it was attempting to install the Xposed framework on a default ROM that only had SuperSU installed. But I've since installed a default ROM and ran the Xposed uninstall to no avail. The uninstall Zip in TRWP gave all the right responses that it worked, but it still rebooted 53 seconds after restart. Continuously.
I don't even know how to go back to Lollipop because attempts to load G920PVPU1AOCF in Odin gives me an immediate failure of "SW REV. CHECK FAIL. DEVICE: 3, BINARY: 1," so downgrading appears to be out of the question.
Someone has to have seen something like this before or there's something I'm missing. About the only thing I can think of is to try a custom ROM install and force the Xposed framework again without even letting it boot up (because it won't anyway) from a TRWP install. I'm going to attempt that while hopefully someone else comes up with ideas for me...
Click to expand...
Click to collapse

Stick it in Odin mode and let it die, once it gets to the point where you cannot turn it on anymore, it's good :good:

1619415 said:
Stick it in Odin mode and let it die, once it gets to the point where you cannot turn it on anymore, it's good :good:
Click to expand...
Click to collapse
I just let it go through the boot loop all night...
AND IT TOTALLY WORKED!
Thanks to both you and wright0101!

zee3are0 said:
I just let it go through the boot loop all night...
AND IT TOTALLY WORKED!
Thanks to both you and wright0101!
Click to expand...
Click to collapse
NP, glad it worked:good:

Related

How I fixed my “stuck at Samsung" issue

Back story was basically I went to use my phone that was running dicksteele buttnaked and it was frozen so I did a battery pull and that just froze up at Samsung screen and wouldn't let me into twrp. Sorry if this is a bit all over the place but if you are stuck like I was it may offer some help or at least get you thinking that you may not have tried absolutely everything.
@terpin32 got it back up, thanks for the help and all the suggestions from my post and the others I read here. Read all the suggestions for stuck at Samsung posts. Flashed via Odin all the param tz files I could find no luck. Still couldn't get it to boot normally or into recovery. So I flashed twrp via Odin still couldn't get into recovery. So I tried Phillz via Odin and bam got into recovery.
Now the issue was I had no backups via Phillz. So I tried wipes of cache and davlik still no normal reboot. Then I tried to do a full wipe to load a new ROM and the phone locked up and rebooted again. So I got back into recovery and began just trying to flash ROMS since my options were getting more limited.
First tried Buttnaked and it wouldn't boot same thing as before. Went back into Phillz and tried a full wipe for new ROM again. Froze before it finished and rebooted again. So I tried zens 4.3 and it froze on bootup. Tried to full wipe same result. Thought hey I will give a Aosp Rom a go. Dirty unicorns and everything looked like it was going to boot because it didn't freeze but it also never booted and just hung. Back into Phillz and tried a full wipe again and it frikn worked. Now I was getting somewhere. So I flashed twrp back and wiped everything again. Went to my last backup of DickSteeles ButtNaked and it booted back up just like nothing happened. My sound issue I was also having is fixed since my save was before it went goofy.
Not sure if this will help anyone but thought I would share. I do troubleshooting a lot at work and sometimes it's extreme. I came to the realization that I might need a new phone so I tried everything I could think of. My wifi is a little wonky probably because of the tz files I flashed but I will take that over the stuck bootup.

MM 6.0.1 Xposed Update!

So, i recently have tried flashing Xposed on the MM 6.0.1 on G920P a.k.a Sprint S6
( ALL_SPT_G920PVPU3CPB6_G920PSPT3CPB6_CL7280193_QB8664149_REV02_user_low_ship.tar )
I have root and recovery, but Xposed doesnt seem to comply with me.
from multiple sources or builds.
And each Xposed file that i've tried so far that i've been flashing over and over again, rinse and repeat.
( Flash Stock through Odin, Go through setup process on the phone, Reboot Back to Download mode to Flash TWRP, Reboot, Back to TWRP to Flash Xposed, Once flashed i Restart it again, back to the s6 screen to becoming a black screen bootloop, thus having me restart the whole flashing process again )
from android file host website. And Default xda unofficialy build on this website.
xposed-v79-sdk23-arm64-by-romracer-20151218
xposed-v80.0-sdk23-arm64-custom-build-by-wanam-20160211 - ABDYASAR 7.8MB
xposed-v80.0-sdk23-arm64-custom-build-by-wanam-20160211 - SANOC 7.8mb
xposed-v80.0-sdk23-arm64-custom-build-by-wanam-20160211 -WANAM 7.8MB
xposed-v80-sdk23-arm64-by-romracer-20160202
It would go from the Galaxy S6 Boot Menu startup to black screen and bootloop back to the original BootMenu or screen.
NO LED cycles nothing, but i can access Download Mode and Recovery But Updating Nor Uninstalling doesn't do anything to the rom, it just keeps boot looping unless i Flash the Stock back into place.
I'd like to have Xposed working i havent found a version for me that would work for this but i would really appreciate if everyone could help out.
IAmTechFreq said:
So, i recently have tried flashing Xposed on the MM 6.0.1 on G920P a.k.a Sprint S6
( ALL_SPT_G920PVPU3CPB6_G920PSPT3CPB6_CL7280193_QB8664149_REV02_user_low_ship.tar )
I have root and recovery, but Xposed doesnt seem to comply with me.
from multiple sources or builds.
And each Xposed file that i've tried so far that i've been flashing over and over again, rinse and repeat.
( Flash Stock through Odin, Go through setup process on the phone, Reboot Back to Download mode to Flash TWRP, Reboot, Back to TWRP to Flash Xposed, Once flashed i Restart it again, back to the s6 screen to becoming a black screen bootloop, thus having me restart the whole flashing process again )
from android file host website. And Default xda unofficialy build on this website.
xposed-v79-sdk23-arm64-by-romracer-20151218
xposed-v80.0-sdk23-arm64-custom-build-by-wanam-20160211 - ABDYASAR 7.8MB
xposed-v80.0-sdk23-arm64-custom-build-by-wanam-20160211 - SANOC 7.8mb
xposed-v80.0-sdk23-arm64-custom-build-by-wanam-20160211 -WANAM 7.8MB
xposed-v80-sdk23-arm64-by-romracer-20160202
It would go from the Galaxy S6 Boot Menu startup to black screen and bootloop back to the original BootMenu or screen.
NO LED cycles nothing, but i can access Download Mode and Recovery But Updating Nor Uninstalling doesn't do anything to the rom, it just keeps boot looping unless i Flash the Stock back into place.
I'd like to have Xposed working i havent found a version for me that would work for this but i would really appreciate if everyone could help out.
Click to expand...
Click to collapse
Did it work. Ive only noticed a tad bit longer boot up the 1st time but all good.
i've tried most of them and i tried v80.0 or v80 and i got one part success half i didnt which was from it i got to the LTE spectrum screen and it just would go past that before it would just be the led flashing and bglank screen, i waited about and hour and still nothin changed from that screen.
Nevermind i made an update
This is what i've managed so far.... what am i missing here?
So here's what i"d take place in order to attempt a flash of Xposed Framework.
I start with Pre- Downloading the files for the MM 6.0.1 Stock Rom, it's in the forums Somewhere.
TWRP ( New_S6_Spr_TWRP_MM_Bootloader2 ) a.k.a 3.0.1
(This is a special version only for the Sprint SM-G920P and is meant to be flashed with Odin)
SuperSU 2.68 a.k.a ( BETA-SuperSU-v2.68-20160228150503 )
and obviously, Odin ( Odin3 v3.10 )
The steps that are taken place.
1st. I'd Boot my device into download/odin mode.
or
( while the device is powered off, i press and hold the home+power+volume down buttons.
and from there I'd be taken to a light blueish screen saying "Warning", and i follow through by pressing volume up)
2nd.
Once the device is in download/odin mode, and ready to go, i'd take my phone, plug it into my windows PC and open Odinv3 and from there
i'd select in odin, or i'd click the "AP" button and select the, tar file.
After that has been flashed thoroughly, I'd then proceed with the follow on screens, the 1st reboot and it updates or it says
Optimizing app 1 to 30.... the 2nd reboot where the hand free activation commences and
from that 3rd time it reboots and boots up again, i'd follow up with my login information.
3rd. once my device has been fully booted from the 2nd part, i'd then shut it down or restart it into "download mode again" and connect it to my pc again
and from there i'd load odin, and search or i'd find where I downloaded the special "TWRP .tar" or recovery file
and select the "Ap" option again and press start Afterwards.
After it flashes, right when its done i automatically hold the home+power+volume up buttons,
turn the device off and hold home+power+volume up and your should get some red text in the upper left hand corner with recovery not enforcing, that's okay dont be worried,
and from there it should boot into and be brought into TWRP...finally lol.
Now that's where you can flash SuperSU
4th. I'd leave my phone connected to my pc until, it's fully booting into twrp or i'd just connect it once im in the recovery.
I let my pc detect my phone and i'd copy both of these files.
SuperSU 2.68
and
Xposed
4th. After its copied, i'd go back into my phone, i tap install, and i select supersu and let it run, afterwards, i press reboot.
And let it sit for about another 2 minutes to do its own thing. Afterwards. once the phone is fully booted up.
I'd then go back into recovery, and flash Xposed and i'd wait about another 2-3 minutes for it to cycle
from the LTE Spectrum Screen to the, torquise colored screen where it's finally optimizing apps from 0 to 331.
5th. Once done, i'd finally have my advantage to install what i'd like which i'm doing as of right now still testing it out.
P.S if you do what i do for the SnapPrefs Module then i'd take in high note that before you flash the Xposed to download latest Snapchat 9.26
log in, once logged in then proceed with the rest and download XInstaller to downgrade from 9.26 to 9.17.1.0 to take full advantage of Snapprefs coolness.
upon note so far, after installing the modules, i rebooted my phone and it boots until it hits the LTE Spectrum screen and it has a light blueish pusling cycle and im stuck here.
maybe i can try another version. to be continued...
If you need any help feel free, i will try as best as i can, as i am a n00b but i have plenty of free time and have some decent knowledge about this.
After , i went back into recovery, i went to uninstall xposed thru the other flash file and its says optimizing 0 to 36 items and it booted so far, mayber after i flash the cache again and reinstall i should be fine but until further notice...tbc
Alright after a good amount of time i;ve finally concluded that the versions i;ve tired from xposed were the ones from the OFFICIAL thread and id always bootloop with that puling blue led and black screen, BUT with Wanams Xposed Version 80, and 79 they worked EXCEPT i can only get to the LTE SPecturm white boot screen and it does nothing from there BUT when i flash 80.1 it completely pulls through with the boot and completes but i had forgotten to mention that for some people on aanother thread that Xinstaller may leave you with bootloops and as it did for me thats exactly what happened. But i m still confused as to why the officials dont work by wanams does even after wiping cache,and dalvik cache multiple times and uninstall and reinstalling xposed.
Does yours still bootloop or did it finally pull through?

Bootloop from hell - messing around with kernels

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.

This doesnt quite seem like a boot loop... Help?

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

Samsung Galaxy Tab S stuck in bootloop after flashing official ROM and factory reset.

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

Categories

Resources