Hello all,
My Note 10+ notified me that the Jan update is available and as usual I chose to install it. However, it rebooted and now won't boot past the Samsung logo. It gets past the initial Powered by Android screen to the "Samsung" logo where it dims then suddenly reboots to the Powered by Android screen again. It does this a second time then eventually goes to a screen saying that the phone couldn't start normally etc.
I haven't backed up my Whatsapp or more crucially my 2FA recovery codes for some important services.
Is there any chance that I can rescue my phone without factoring reset?
Could installing BSL7 (December build) fix this?
I have the same issue
What Model 10+
What model Note 10 do you have?
Cheers
UK Samsung dual sim model
SM-N975F/DS
Update:
Tried installing BSL7 and things got worse in that it wouldn't even attempt to boot the system. Reinstalling BSLD put it back in the current state which is a bootloop with a delay that allows me to run some adb commands before it reboots.
Guys I'm getting desperate here. Should I be asking elsewhere on the forum?
I found a new build N975FXXS1BSLE with CSC of THL. Since downgrading didn't seem to work, would flashing everything from the seemingly newer BSLE build along with the HOME_CSC_OMC_OXM_N975FOXM1BSL7 from BSL7 cause any issues? I've never mixed builds like that.
I'm thinking the OS and everything else will be from BSLE but CSC will be from the BTU build.
Please help
I had no issues at first, but when I tried to turn on Secure Folder it started the bootloop, I partially solved it by disabling and clearing secure folder app data and cache, can you guys try that and confirm?
crzr said:
I had no issues at first, but when I tried to turn on Secure Folder it started the bootloop, I partially solved it by disabling and clearing secure folder app data and cache, can you guys try that and confirm?
Click to expand...
Click to collapse
Dammit Samsung. I had Secure Folder enabled before updating. How on earth do I disable it now without factory resetting?
Update:
So I flashed the Thai build and it went as far as showing a small window "updating apps xx of xx" but when it finished it bootlooped again so I reverted to BSLD and it did the same but is still bootlooping.
Related
Hi All,
Having some issues with my Galaxy Note 10.1 which I've had for quite a while now. It's rooted but with Android 5.0 stock rom and a custom kernel.
Just now (like 20mins ago) I tried to enable Adblock plus app, the app said it can't automatically change the settings - even though SuperSU was installed and had no issues with it previously. So like all things thought I'd give it a reboot that ought to clear it out. That didn't work, so tried clearing cache (Dalvik/ART/Cache), Still no joy.
I'm a s/w engineer, but not and android/bootloader expert, so I've tried to grab the dmesg and boot logs which I've attached, I've got some stuff on the internal SD (app data) which I'd like to keep, hence I'm not going for the full wipe.
Please take a look at the logs and see if you can determine how to fix this issue, my initial thoughts were there are some issues with the flash storage (bad sectors/partition table?), if I could grab the image and dd the image again I'd be OK - but I don't know much about about android boot loader/kernel etc so can't say.
Ok it has been fixed by wiping data - but I've lost my data and installed apps!
Is there anyway to find out which file/app is causing the boot loop so I can restore data, delete the offending file?
Well, I shall give a bump to this topic, with a little more info. Though probably not really useful.
First I had stock 5.1.1 deodex pre root etc ROM that, after I tried to insert a nano sim card (mine is a 601 3G model) that got stuck, it entered on a bootloop, I had to open it, take the sim card out, and it was still on a boot loop. Tried to install another image, still bootloop, tried to reinstall the original one I had, still bootloop, wiped data, worked fine.
Then almost 2 weeks later, everything worked fine, went to watch a video, the sound was mute, tried to turn it on but everything looked fine, decided to restart because it would probably fix the problem. Got a bootloop. Wiped the data, everything was fine again.
Now, a little more than 2 weeks later, seems like the wifi is not working, thought all my other devices are, guess it's the same problem, decided to restart it, and bootloop again. I'm currently trying to update my TWRP, and gonna try a different ROM, and wait to see if something like that happens, until then, I wonder what could be happening... I remembered an Asus Device that I had that had different firmware versions for 4.4 and 4.1, so if I tried to flash a 4.4 on a 4.1 firmware it wouldn't work, and for downgrade, the same problem happened, and wondered if Samsung has some difference between versions 4 and 5.
ssj4maiko Let me know if you find a more stable rom - I went back to pretty much stock, but with root as I wanted to use all the Samsung apps, but this constant random bootloops are annoying!
Hello,
I'm having a weird issue with my Note 7 that I didn't have at all until tried to root for the first time....
It randomly restarts, sometimes is very often and sometimes it take a few hours to do it, but when it does it just restarts out of nothing and when Android loads again it asks me for a password that doesn't even exsits
"To start your device, enter your password" (Picture attached)
This started to happen after used the rootable kernel that was published before SuperSU 2.77 Beta but even reflashing the stock firmware, bootloader, modem, CSC it keeps doing it even when my Android is not yet configured (at the first Welcome screen before setting the phone up), so there is no password at all at this point. I've tried my Google account password, but it doesn't work.
This message is the same that comes up when you select "Secure Boot" so you need to enter a password or PIN to decrypt your data and be able to load it, but I don't have that option checked, and could not be checked when the phone is not even configured.
The way to work around this issue is flashing the no-verity-opt-encrypt mod that is not supposed to be needed anymore after SuperSU 2.77 has been released. So flashing this mod will get me into my Android home screen but it will eventually restart again and I need to flash this mod again.
This is what I've tried so far and it keeps happening:
- Flashed the rootable kernel when it was published and the no-verity mod. I formated data as indicated in the post. Then this problem appeared.
- Flashed stock firmware, bootloader, modem, csc thinking this would remove any trace of the mods I flashed, but kept happening.
- Factory reset from the Samsung recovery, had the "no verity" errors sometimes and sometimes not.
- Flashed other firmwares, bootloaders, modems, csc from other countries but for the same model N930F and kept happening.
- Flashed custom ROMs, formated system, data, everything.
- Flashed stock firmware again.
- Flashed custom ROMS again with the new SuperSU 2.77 and keeps happening.
I have done every single flash that actually exists for the Note 7 and formated everything with no luck....
Has anyone have this issue or had it at all at some moment? If so... How did you manage to get rid of this message?
I hope someone can help, If it was faulty phone I think it would restart at any point even in Recovery or Download mode, but only happens inside of Android.
Seems a common problem I think?
http://forum.xda-developers.com/showthread.php?t=3444510
Sent from my Nexus 6P using Tapatalk
Yep, saw that post... But never seen anyone complaining about the phone asking for a password when reboots (only when it crashes) its like it was asking for a password to decrypt the phone.
Hey, I have a question.
I've encountered something kind of strange with this device. I've been running Android P with the December 2018 security patch, rooted with Magisk. I've never encountered any problems with it so far except for a few bootloops I've got for deleting some modules in Magisk.
One day I decided to restart my phone because it was kind of laggy and so far so good it was booting. It showed me the Xiaomi logo and then it asked for the pattern to start Android. I entered the pattern and it just got into bootloop. (I've gotten bootloops before but it never got to the point where it shows me the logo and asks for pattern). I don't know what caused the bootloop because lately I haven't been messing with Magisk. However I thought it was a good idea to get into recovery and factory reset it (this has gotten me out of bootloops before so I gave it a try). After the reset it started to bootloop again, I just restarted it and it worked out just fine. I set up my phone, obviously root was gone because of the reset but I realized my phone's gotten updated to the March 2019 security patch. This was quite a surprise because I've been trying to update it and nothing seemed to work. (I tried updating it once by reflashing the original firmware with MiFlash, it was version 10.0.2.0, and before rooting it to install the security updates, they were just failing for no reason because there was no root on the phone).
So do you guys have any idea why my phone got into bootloop out of a sudden? And also why did the update successfully got installed after the factory reset?
Merky_21 said:
Hey, I have a question.
I've encountered something kind of strange with this device. I've been running Android P with the December 2018 security patch, rooted with Magisk. I've never encountered any problems with it so far except for a few bootloops I've got for deleting some modules in Magisk.
One day I decided to restart my phone because it was kind of laggy and so far so good it was booting. It showed me the Xiaomi logo and then it asked for the pattern to start Android. I entered the pattern and it just got into bootloop. (I've gotten bootloops before but it never got to the point where it shows me the logo and asks for pattern). I don't know what caused the bootloop because lately I haven't been messing with Magisk. However I thought it was a good idea to get into recovery and factory reset it (this has gotten me out of bootloops before so I gave it a try). After the reset it started to bootloop again, I just restarted it and it worked out just fine. I set up my phone, obviously root was gone because of the reset but I realized my phone's gotten updated to the March 2019 security patch. This was quite a surprise because I've been trying to update it and nothing seemed to work. (I tried updating it once by reflashing the original firmware with MiFlash, it was version 10.0.2.0, and before rooting it to install the security updates, they were just failing for no reason because there was no root on the phone).
So do you guys have any idea why my phone got into bootloop out of a sudden? And also why did the update successfully got installed after the factory reset?
Click to expand...
Click to collapse
You want help without logs? This is a developers site not Magic kingdom!
Hi there,
Last week, I get the OTA from my OWO CSC, it get updated to ZTO and the PDA version is CTCA. Not sure if this is newer or have a big difference from CTC9.
Does anybody here from OWO CSC and with this update experience some issues?.
I have already tried everything, also have received some help in this forum and it helps for few hours and then the problem appears again.
Regarding few points I have tried:
-I have already flashed again CTCA ZTO CSC using odin.
-I have already flashed the previous one, CTC9 ARO CSC using odin.
-I have done a factory reset with the CTCA ZTO CSC using the recovery menu.
Once i finished to reset the phone, i downloaded all appss and configured the phone from 0. Just restored some settings that i have backed up using samsung cloud. The phone works super perfectly for 48 hours and this morning it started again with the constant reboot.
Regarding few points i do have a question first, do you know or does it exist any software that can detect what reboots the phone or any log that track the error that can cause the phone to reboot?
I came from ZTO BTB9 that was from march security patch and till now it never happen to me before with this phone and Odin updates. I did not do and touch anything during update period, did it till the end. IT was just plugged into the charger. The phone finished the process completely normal, after it ends, i start it using and checking the new features. I configured the camera, the keyboard and not much. Not installed any software, just update all apps to the latest from store (samsung and google). The reboot is just random, the first one i detect while running app booster from samsung, but then it reboots without running that app (just reboot again). It looks like a softt reboot or a quick reboot because it get quickly back again but i should put the pin and it loads all again (notification from 0). It does not show the screen that say "samsung galaxy note 10+ powered by androird", just the "Samsung" logo screen and then lock screen. I did not reboot it as soon as it ends updating. The cache wipe did it just this morning after i detect it reboot over the night. It reboots like 6 time already. Since the previous one to last one have passed 3 hours but the very first reboots occurs between 20 or 10 minuts from each other. Now the reboot happen every 1 minute.
It looks like there is a problem somewhere and it sounds like a software problem. But i'm trying to know if it is a build problem or personal problem.
Now i have the phone running in SAFE MODE and it is fine, so for sure is something in system that try to synch, update or w hatever in background that crash the phone. I have the same apps as always installed, no new apps added so far
Thanks for the time.
Regards.
Yamil.
Hello everyone.
I'm currently with an annoying issue:
My Samsung Galaxy S9 (non-rooted) is randomly rebooting only while idle.
Whenever I'm charging, playing or perform any interactive activity, the phone works as it has been working for the past 2 years.
As soon as I left it idle for a while, it simply reboots. Usually do not take more than an hour for the reboot to happen.
Already performed a facory reset, cleared cache, force shutdown (power + volume down), worked on safe mode and nothing seems to lead me to the root cause.
It started on tuesday (December 29th @2020).
Thanks in advance,
Caio
I have had a similar problem for a long time. Sometimes my Galaxy has given to restart without stopping as far as it wants ... Once it happened to me that for a day it did not stop restarting after installing the Google assistant, only by entering safe mode and deleting it I could solve it .. . And one of the last was that I changed the CSC and the mobile just did not stop restarting, even after downloading and reloading it, I deleted and formatted absolutely everything and I could not use the mobile normally ... After several tests I realized that it restarted after unlocking, so I deactivated the passwords and fingerprint but it did not work, so it occurred to me to install another launcher and problem solved. I have no idea why this is happening to me, maybe is an error in the internal memory due to a bug in the firmware (?)... Anyway, I had read some time ago that there were similar problems caused by a GPU failure in the Snapdragon models, but I no idea.
Renos_Z said:
I have had a similar problem for a long time. Sometimes my Galaxy has given to restart without stopping as far as it wants ... Once it happened to me that for a day it did not stop restarting after installing the Google assistant, only by entering safe mode and deleting it I could solve it .. . And one of the last was that I changed the CSC and the mobile just did not stop restarting, even after downloading and reloading it, I deleted and formatted absolutely everything and I could not use the mobile normally ... After several tests I realized that it restarted after unlocking, so I deactivated the passwords and fingerprint but it did not work, so it occurred to me to install another launcher and problem solved. I have no idea why this is happening to me, maybe is an error in the internal memory due to a bug in the firmware (?)... Anyway, I had read some time ago that there were similar problems caused by a GPU failure in the Snapdragon models, but I no idea.
Click to expand...
Click to collapse
I already use Nova Launcher, so I dont think this will fix my problem. Now its taking more time between rebooting cycles buts its still there.
I guess my last attempt will be to flash a stock ROM and see if it works.
CaioBomani said:
Hello everyone.
I'm currently with an annoying issue:
My Samsung Galaxy S9 (non-rooted) is randomly rebooting only while idle.
Whenever I'm charging, playing or perform any interactive activity, the phone works as it has been working for the past 2 years.
As soon as I left it idle for a while, it simply reboots. Usually do not take more than an hour for the reboot to happen.
Already performed a facory reset, cleared cache, force shutdown (power + volume down), worked on safe mode and nothing seems to lead me to the root cause.
It started on tuesday (December 29th @2020).
Thanks in advance,
Caio
Click to expand...
Click to collapse
reflash firmware via Odin. gert FW(firmware) from sammobile.com/firmware and use SamFirm to download, as it downloads 4x faster than from thr site directly. When flashing, use the HOME_CSC vs just the CSC file, as the csc factory resets whereas home_csc keeps your files and settings etc etc. If that doesnt fix it, you have a hardware issue(IMO, at least, and ive been rooting samsungs for a decade). If you have a hardware issue, id get it as good as i could and use the trade-in specials sammy has going