Hey all,
Just upgraded to the latest MM CM nightly on my Find7 and got everything working (SuperSU, Xposed etc). I wanted to encrypt my phone so I went and did the usual thing of charging it up and all. Once I hit encrypt it shows the Android guy (the encryption logo thingo) for a few seconds then goes to the boot logo. I let it go for >2 hours and nothing happened. I just held down the power button and rebooted properly and everything is fine. No files are corrupted or anything Then I tried doing it again after killing SuperSU as some have suggested, no dice either. I notice that during all the times I do it that my Pebble doesn't disconnect while it's on the boot logo so it doesn't seem to be rebooting properly at all (as BT doesn't disconnect). I've tried reinstalling the ROM from scratch again but that didn't work either. Any suggestions?
Related
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:
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
So 3 days ago I updated my stock kitkat rom to CM 13, but I realised that marshmallow cant write on my sd so i tried a couple of fixes flashed on my device, namely the latest sd fix (2.9b) and so far so good except it didnt solved my problem, so I tried flashing the 1.9b version of the fix through recovery mode, after I finished flashing the TWRP apk asked me if I wanted to install the su apk, I didnt, so I clicked the reboot option instead except it didnt rebooted my phone so I held the power button until it turned off, next thing i know I tried turning my phone on and It gets stuck on the blue mascot booting animation for as long as I let it sit.
I already tried flashing a new CM (14) and factory resetting all to no avail, basically Im blind as to what i must do now. ANY help is welcome.
You cloud try to flash the newest twrp: https://twrp.me/samsung/samsunggalaxys4minidsdd.html
And the official lineage 14.1: https://download.lineageos.org/serranodsdd
@thorium231 I love you man, the problem was with CM after all.
So i had lineage os 16 until it started to randomly restart multiple times. so i got the newest available Stock rom for the marlin, had some weird trouble flashing it until it finally worked. the phone booted and i set everything up. after a couple of log ins with apps and downloading it just turned off and started boot looping. Now usually you could enter the bootloader but.. it only stays in that for .5 to 4 seconds before restarting. i cant power off because the home button isnt working and i cant flash a clean rom.
Any ideas???
(currently letting my phones battery drain and leaving it for a bit. hopefully that could help but unlikely)
Hello!
After recently getting my hands on an old Samsung A50, I thought I might as well reflash and do some stuff with it.
After installing Orangefox and Lineage, everything worked fine until the phone eventually ran out of power.
I plugged it in and let it charge for a bit, but it was just constantly showing the gray circle with a charging/power icon in it, but no battery indicator.
This usually means that the phone is completely empty and has to charge a bit before booting.
After letting it sit for a long while and nothing changing, I got a bit worried.
At this point, unplugging the phone does not change anything - it will continue showing the indicator even while unplugged.
Holding power and volume down (or power + both volume) briefly blacks out the screen, but it simply comes back to the indicator a few seconds later.
All of this happened a few days ago - I eventually got it to boot again through some key combination while the screen blacked out, sending me to orangefox or download mode (i dont remember),
from which I was then able to boot into lineage again. In lineage, everything worked fine again, including the battery indicator which showed that the phone was full, and the battery seemed to work completely fine.
After that, I turned from lineage to Fresh, which also ran fine until Fresh wanted to install an update which sent me to TWRP. Not sure what to do, i just booted back into System which worked fine, but the Fresh update hadn't succeeded.
I attempted to update again and this time shut down from TWRP - big mistake. Now i am once again stuck in the low-power indicator.
I believe that last time i escaped by booting into orangefox - but i think fresh replaced orangefox with twrp?
Anyway, i tried holding different button combinations while the screen is briefly blacked out but nothing is happening (also tried getting into download by plugging into pc, holding power+volumedown, then holding volume up+down while screen is black).
I also let the battery empty itself until it went black by itself and then tried again, but no success.
I'm now again unsure what to do. How do i unbrick this to boot into the OS again? How do i prevent this from happening again?
Thank you all.
Same issue with my Redmi 9, it seems a battery issue idk if i had rekt mine after flashing a latest CN rom then after not being satisfied tried to flash thru recovery to its stock rom and it went bootloop. Fixed it by flashing with SP flashtool and some bypass stuff, but damage has been done with my batt. Maxing out the volume when I try to play something video or music would trigger a reboot to my phone.