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!
Related
I had rooted my phone and removed some of the bloatware (I wish I knew better at that time).
But anyway, I got the OTA notification. I unrooted my phone and applied the update.
Things seemed to work fine but when the phone rebooted, the dreaded "Error" dead bot appeared. But unlike many, I didn't get stuck in a boot loop as the phone started normally.
And it looks like the update was applied because the System Update build number shows "2.18.40.12" (earlier was 2.17.40.12)
Should I be worried? Should I flash the stock ROM? Or is there any other method of restoring the bloatware?
Thanks for your time.
EDIT: I flashed my phone just to be sure. I suppose this thread is irrelevant now.
Hello, I'm having a strange issue with March Security Patch update. 3 days ago I received via ota this update, did it and everything was OK. The day after, I rebooted the phone, and sudden it turns black and rebooted by itself looping on coloured little balls before G logo. Another reboot and when it turns on I noticed that it downgraded by itself on February patch security, giving me the March update aviable via ota again.
I reupdated but the day after, once again the same thing. And once again yesterday...and once again today. What have I to do?
hbkekko said:
Hello, I'm having a strange issue with March Security Patch update. 3 days ago I received via ota this update, did it and everything was OK. The day after, I rebooted the phone, and sudden it turns black and rebooted by itself looping on coloured little balls before G logo. Another reboot and when it turns on I noticed that it downgraded by itself on February patch security, giving me the March update aviable via ota again.
I reupdated but the day after, once again the same thing. And once again yesterday...and once again today. What have I to do?
Click to expand...
Click to collapse
Is your bootloader unlocked or any root or anything of that sort? That's a very weird issue. There are reports of the Nexus 6 being downgraded to 7.0 by Google but I'm not sure if it's a software push they are doing to cause that to happen.
You may have to wipe cache and try the update again.
Jammol said:
Is your bootloader unlocked or any root or anything of that sort? That's a very weird issue. There are reports of the Nexus 6 being downgraded to 7.0 by Google but I'm not sure if it's a software push they are doing to cause that to happen.
You may have to wipe cache and try the update again.
Click to expand...
Click to collapse
I tried to wipe cache from settings, storage but didn't work. Yes I've unlocked bootloader but no root. Could this be the problem?
No, shouldn't affect anything just being unlocked. Now if you installed TWRP, that might cause this. I didn't use an OTA to go to the march update so idk if it might be at fault, I was on pure Nexus so chose to flash the factory image and haven't had any issues so far.
Sent from my Pixel XL using Tapatalk
Solved flashing the latest factory image via fastboot
So about a few years ago, I tried to root my galaxy note 4 (n910aucu2doi3), but I guess it rejected the root because it instantly bricked my phone, to the point where I had to completely wipe it using android recovery. The only way to get my operating system back was to download it online and install it through my PC (I had to find the exact version for my phone as well, 5.1.1 at the time, because it rejected every single other version).
Everything seemed to be working fine, except that I couldn't install software updates on my phone anymore. It was permanently stuck on 5.1.1. It was a bit of an annoyance but I didn't think much of it at the time.
Fast forward to now, and I'm getting several signs that my OS may be corrupted. My phone is constantly freezing, crashing and restarting. Maneuvering through applications causes the phone to freeze for a few seconds before either restarting or crashing the app. I want to say it's definitely a software issue, but I did install a new battery recently and it was working fine for a few weeks, could that be the issue?
If not, I want to start over, but I'm not sure how, and I don't know if it's safe to do a factory reset on this OS. Is there anyway I can get a fresh stock version of an android OS that can also update?
Any help is appreciated, I'm pretty much desperate.
I manually updated to 6.0.1 with the help of this thread https://forum.xda-developers.com/note-4-att/general/updates-thread-t3663943
It seems to have fixed the issues so far, and my phone can automatically update again
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.
Hello,
I'm using the Wileyfox Swift with Magisk for Root and the Firewall AFwall+. Since the last update I can't get access to the internet, either through wifi nor through the SIM-card. What wonders me is, I had to reinstall Magisk from the recovery (TWRP) Magisk seems to work fine, but AFwall+ doesn't work at all, saying that it can't get root-access. Normally the updates of LineageOS worked without any problem and doesn't change root.
I already tried installed the LineageOS version form the lineage-17.1-20210116- but it doesn't changed anything.
Has anyone an idea how to solve this problem? I would be grateful.
Thanx for now.
UPDATE: Now I changed to the lineage version two weeks earlier lineage-17.1-20210109- which made the situation now even worse. After logging-in, I just get a black blanc screen showing nothing to me. Thankful for any help
Second Update: After all I wiped the phone and installed everything new. I also tried the newest update, but got still the same problem – so I switched to an ealier LineageOS version. Now it works again. Has anyone similiar problems?