About an hour ago I turned the phone off while it was plugged in to my PC charging. I was on CM14.1 20161208 nightly and whatever the newest opengapps ARM 7.1 mini was at the time of that nightly. After 5-10 minutes I turned the phone back on and ever since then it will boot up and I can do stuff or just let it idle for maybe 15 seconds before it freezes and reboots itself. I never had any problems with it prior to this, other than auto-rotate not wanting to work in some cases.
I have tried battery pulls, dalvik/cache wipes, a reflash of that nightly, a full wipe of everything by SDCARD/USB Storage and install of latest 20161225 nightly and latest opengapps ARM 7.1 mini(tried this 3 times so far). Nothing has fixed it.
It's obviously rooted, did the dev aboot bootloader unlock method last year, is on the bok3 firmware.
Not sure what to do at this point. Is the phone trashed?
ETA: It seems the problem goes away if I do a full wipe and install of my rom, but do not install opengapps. Makes no sense, I had no problems with the phone or opengapps before turning the phone off earlier today.
ETA2: After letting it sit for a while, and configuring some settings, I decided to reboot in to recovery and try the latest opengapps arm 7.1 pico to see if that made any difference. After boot it took about 15 seconds for the phone to freeze. Why am I suddenly not able to run opengapps on my phone at all?
ETA3: Fulled wiped and installed rom again. Worked fine until I google-searched for the play store apk, viewed a thread here, clicked on the apk link, and once it should have started downloading the phone froze and rebooted. Working fine now, but it for whatever reason that download trigged the freeze/reboot. Could really use help with this before I'm forced to go out and buy a new phone before I go back to work on Tuesday.
johnnyrichter said:
About an hour ago I turned the phone off while it was plugged in to my PC charging. I was on CM14.1 20161208 nightly and whatever the newest opengapps ARM 7.1 mini was at the time of that nightly. After 5-10 minutes I turned the phone back on and ever since then it will boot up and I can do stuff or just let it idle for maybe 15 seconds before it freezes and reboots itself. I never had any problems with it prior to this, other than auto-rotate not wanting to work in some cases.
I have tried battery pulls, dalvik/cache wipes, a reflash of that nightly, a full wipe of everything by SDCARD/USB Storage and install of latest 20161225 nightly and latest opengapps ARM 7.1 mini(tried this 3 times so far). Nothing has fixed it.
It's obviously rooted, did the dev aboot bootloader unlock method last year, is on the bok3 firmware.
Not sure what to do at this point. Is the phone trashed?
ETA: It seems the problem goes away if I do a full wipe and install of my rom, but do not install opengapps. Makes no sense, I had no problems with the phone or opengapps before turning the phone off earlier today.
ETA2: After letting it sit for a while, and configuring some settings, I decided to reboot in to recovery and try the latest opengapps arm 7.1 pico to see if that made any difference. After boot it took about 15 seconds for the phone to freeze. Why am I suddenly not able to run opengapps on my phone at all?
ETA3: Fulled wiped and installed rom again. Worked fine until I google-searched for the play store apk, viewed a thread here, clicked on the apk link, and once it should have started downloading the phone froze and rebooted. Working fine now, but it for whatever reason that download trigged the freeze/reboot. Could really use help with this before I'm forced to go out and buy a new phone before I go back to work on Tuesday.
Click to expand...
Click to collapse
you are on a Beta, it is expected, if you need stability flash CM13
GeTex said:
you are on a Beta, it is expected, if you need stability flash CM13
Click to expand...
Click to collapse
I didn't think it was the rom since I reflashed a previously working version, tried the latest version, performed several full wipes, etc. I'm fetching the latest 13.0 and will get the latest opengapps mini for it and see if that helps.
GeTex said:
you are on a Beta, it is expected, if you need stability flash CM13
Click to expand...
Click to collapse
Rebooted to recovery, wiped everything but externalsd and usbstorage, installed "cm-13.0-20161013-SNAPSHOT-ZNH5YAO21M-kltevzw.zip" and "open_gapps-arm-6.0-micro-20170121.zip", rebooted, went through preparing apps which I don't think it did on the repeated 14.1 installs earlier, now I'm going through my usual setup and app installs with no freezes. Seems like it was a 14.1 issue.
Thanks GeTex.
johnnyrichter said:
Rebooted to recovery, wiped everything but externalsd and usbstorage, installed "cm-13.0-20161013-SNAPSHOT-ZNH5YAO21M-kltevzw.zip" and "open_gapps-arm-6.0-micro-20170121.zip", rebooted, went through preparing apps which I don't think it did on the repeated 14.1 installs earlier, now I'm going through my usual setup and app installs with no freezes. Seems like it was a 14.1 issue.
Thanks GeTex.
Click to expand...
Click to collapse
I figured
If you don't mind answering one more for me...
I'm on OK3. Is there any path to upgrade to a newer firmware while maintaining unlocked bootloader and root, or is it advised that I stick to OK3 and use only the DEV ABOOT roms like I have been?
johnnyrichter said:
About an hour ago I turned the phone off while it was plugged in to my PC charging. I was on CM14.1 20161208 nightly and whatever the newest opengapps ARM 7.1 mini was at the time of that nightly. After 5-10 minutes I turned the phone back on and ever since then it will boot up and I can do stuff or just let it idle for maybe 15 seconds before it freezes and reboots itself. I never had any problems with it prior to this, other than auto-rotate not wanting to work in some cases.
I have tried battery pulls, dalvik/cache wipes, a reflash of that nightly, a full wipe of everything by SDCARD/USB Storage and install of latest 20161225 nightly and latest opengapps ARM 7.1 mini(tried this 3 times so far). Nothing has fixed it.
It's obviously rooted, did the dev aboot bootloader unlock method last year, is on the bok3 firmware.
Not sure what to do at this point. Is the phone trashed?
ETA: It seems the problem goes away if I do a full wipe and install of my rom, but do not install opengapps. Makes no sense, I had no problems with the phone or opengapps before turning the phone off earlier today.
ETA2: After letting it sit for a while, and configuring some settings, I decided to reboot in to recovery and try the latest opengapps arm 7.1 pico to see if that made any difference. After boot it took about 15 seconds for the phone to freeze. Why am I suddenly not able to run opengapps on my phone at all?
ETA3: Fulled wiped and installed rom again. Worked fine until I google-searched for the play store apk, viewed a thread here, clicked on the apk link, and once it should have started downloading the phone froze and rebooted. Working fine now, but it for whatever reason that download trigged the freeze/reboot. Could really use help with this before I'm forced to go out and buy a new phone before I go back to work on Tuesday.
Click to expand...
Click to collapse
i have the same problem and no matter witch custom rom that is 7.1.1 it does the same thing (turns on for 15 seconds, freezes, then reboots, and repeat)
N0rth3rnl1ght said:
i have the same problem and no matter witch custom rom that is 7.1.1 it does the same thing (turns on for 15 seconds, freezes, then reboots, and repeat)
Click to expand...
Click to collapse
My phone ran fine on CM14.1(7.1.1) for at least a month and a half. Not sure why turning the phone off made it stop working with that version. CM13.1 is stable, have you tried that?
Been having the same issues with a 7.1.1 rom Mokee. For the time I've reverted to my S4....
Exact same steps i took. Flashing, wiping, and everything minus external SD.
There is a bootloader update which I did. There is a full update bootloader (I updated and now on PL1) which takes you to Safestrap then back yo TWRP. Others have reported just flashing a PL1 firmware in Odin under AP runs stable.
At this point I'll drop to 6.0 roms, my issues is holding cell service. I can't get any clean flashed rom to give me full data and call service.
I'd like to update firmware/radios if it's possible and won't break my unlock/root and still allow TWRP. Just not sure how to do it properly, starting with my unlocked/rooted BOK3 firmware.
Hey,
I have been using the ColtOS rom based on Oreo 8.1.0 for quite sometime now. I had it rooted with Magisk too. I have the latest version of TWRP installed (version 3.3.0). I had no problem until now where it just randomly tried to reboot after I ended a call. It did reboot fine once, but it was when i ended a second call that it got stuck in a bootloop.
I have tried everything, clearing the cache/Dalvik , wipe data and system and flashed three different Oreo ROMs, uninstalling Magisk. However, I can only go as far as the set-up screen after the new ROM boots, after which it goes back to rebooting itself endlessly.
I seem to have exhausted all my options, any kind of help to restore my phone will be greatly appreciated.
Thank you.
I have found out that I can flash new ROM and even set up the phone by logging into Google, only when I connect my phone to my laptop. It even installs all the previous apps and data and thats it. It reboots to the lockscreen and when I try to unlock it, it reboots again. And this is all only when I keep the phone connected to my laptop, otherwise,it keeps looping into the bootscreen logo.
AndroGuy18 said:
Hey,
I have been using the ColtOS rom based on Oreo 8.1.0 for quite sometime now. I had it rooted with Magisk too. I have the latest version of TWRP installed (version 3.3.0). I had no problem until now where it just randomly tried to reboot after I ended a call. It did reboot fine once, but it was when i ended a second call that it got stuck in a bootloop.
I have tried everything, clearing the cache/Dalvik , wipe data and system and flashed three different Oreo ROMs, uninstalling Magisk. However, I can only go as far as the set-up screen after the new ROM boots, after which it goes back to rebooting itself endlessly.
I seem to have exhausted all my options, any kind of help to restore my phone will be greatly appreciated.
Thank you.
I have found out that I can flash new ROM and even set up the phone by logging into Google, only when I connect my phone to my laptop. It even installs all the previous apps and data and thats it. It reboots to the lockscreen and when I try to unlock it, it reboots again. And this is all only when I keep the phone connected to my laptop, otherwise,it keeps looping into the bootscreen logo.
Click to expand...
Click to collapse
Flash crdroid nougat
So tl;dr version - i was using my tablet, saw an update to magisk, installed it, now it boots to black screen while running sambones rom
[SM-P580] [BQK1] SaMBoNeS
TWRP 3.2.3.0 --> 3.3.1.0
longer story:
i was trying to get a game to run, it wasnt...and realized it has been a while for a restart, so i checked to see if anything needs to be updated and saw magisk needed an update. i didnt note what version it was before but it was a version or two earlier than what it was trying to install.
rebooted to blackscreen no samsung logo
have tried restarting a dozen times, booted to TWRP, tried to force normal system boot through the UI, nothing.
I tried installing a new kernal [SiriKernel], it made it to the samsung logo, waited 15 - 20 minutes and it never made it past. restored a backup using TWRP
updated TWRP to 3.3.1.0, still no luck.
i had this problem a long time ago, and cannot figure out how i fixed it....it may have fixed itself but it isnt this time. any advice would be appreciated. I am trying to avoid wiping and starting again if at all possible because the problem seems familiar. also trying to stick to a rom for use with adaptive storage. if i do have to wipe if that can be done on a newer stock OS that's fine as well but last time i messed with this tablet it wasnt
Hi XDA, I hope someone can help me.
I am struggeling with a strange problem. But first let me tell you something about my phone and what i did to it.
I have a S10 G973F with unlocked bootloader, TWRP 3.3.1, Magisk and HadesRom 2.0 installed and everything is working so far.
Except one thing: when I power down the phone and put it on the charger it starts to boot without the charging animation which has been there when I was on stock.
I am not sure if it has been there right after I installed HadesROM but it's pretty annoying when your phone is completely empty and it starts over and over again because it drains too much battery while starting. (fyi I disabled fastcharge - with fastcharge enabled everything is okay but that's not the point)
I believe it has something to do with modifications to the Hadeskernel because it always starts rooted - even when I start my phone without volume+ and power.
Of course I already asked in the HadesROM-Thread and got no answer since 2 weeks or so.
Many people try to get their phone to boot when plugged in but what I want is exactly the opposite
What I've tried so far:
- Reinstalling ROM without wiping
- Reinstalled ROM with wiping
- Installed the old HadesROM version 1.0 with wiping.
- Formatted everything including internal storage
- Reflashing TWRP
- I tried to edit some kind of lpm file located at /system/bin but stopped doing this without some help
- Tried using the fastboot command "fastboot oem off-mode-charge 1" but obviously this wont work because samsung doesn't have fastboot implemented...
What I didn't tried:
- Installing another ROM
- Flashing stock ROM
Maybe someone has experienced the same thing on Hades and is able to help me.
Thank you in advance
EDIT: I posted in the wrong forum. Probably I was too sleepy last night. I reposted it in the right forum. Please delete.
Hello XDA community,
I would never post on here unless it was a last resort. I tried everything with this phone to have it rooted. I rooted successfully in Android 10, 11 all of them worked, but all of them failed over the same issue after a few days which ill describe below. On TWRP + Stock Root Rom, the logs read something about "android telephony". This time around the logs (Adb logcat) is huge and I can't find what causes the bootloop. I am sure it could be fixed somehow.
I Installed Lineage OS 18.1 successfully. In all root roms (phone is dual sim) and even in normal rom, after 2-3 weeks the phone will crash and enter into bootloop. On LIneage OS 18.1 it started after 2-3 days.
Strangely this seems to be related to using express VPN (not sure why). Pressing reconnect on this software causes always the first bootloop. From there on phone repeats the bootloop every time it's rebooted, non stop. It restarts itself and bootloops again.
I have tried installing every rom there is available including root official rom. Nothing fixed this problem.
I am to where i will definitely provide financial compensation if anyone can really help me find out what this is and stop it. I cannot send the phone to OnePlus as they will not provide help over these matters.
I Need liberty of root user without all the harassment of the bootloop.
Now the phone is at LineageOS recovery and lineageOS 18.1 build. It WORKS in safemode, but it bootloops only in normal mode. There is nothing I know to do to stop it.
So I have access to every other function except the normal use of the phone.
Please advise.
It's one of the apps running in normal mode. Seek and destroy... obviously it runs at start up, that should help narrow it down.
Thanks for the help, but I have attempted this to no avail. I have removed all user apps but still the issue persists.
This has also happened on every rom I installed, after about a few days or weeks.
Could it be some remote command is used to terminate the handset? How can I diagnose what is happening?
What if you reflash without Google apps?
LR7875 said:
What if you reflash without Google apps?
Click to expand...
Click to collapse
I have tried, it was without Google Apps to begin with.
I am going to repeat same process and see if the next one bootloops too.
The strange bug occur when VPN connection was activated/deactivated. AFwall was also enabled, running as admin. Then this persist even when I uninstall all apps through safemode ADB.