Related
Hi all,
Some time ago i asked, and received, some support on these forums on how to properly carry out a nandroid backup... following the sound advice i got, i carried out my backup (using TWRP for the record, with all the options checked), and stored it away for a rainy day... said day came yesterday, when i messed up my system and rendered it instable (i tried to manually delete the dalvik cache directory in order to free up the 2,5GB of space it was taking)... since i knew there was i high chance of this ending in disaster, the last thing i did before the delete was carry out another nandroid, so i could easily return to where i had left off... how wrong i turned out to be
as soon as i the system became instable following my experiment of deleting the d. cache directory, i recovered the latest nandroid (i.e. the one i had made just hours before) and everything seemd to go smoothely until the first reboot... when the following happened:
- first reboot after recovery took ages, much like the first reboot following the flashing of a new rom... not the end of the world, but that was the first sign that all was not well
- the status bar disappeared, and there was no way of making it come back (i.e. nothing to do with the launcher, i typically use apex but i i tried switching to both nova and touchwiz which i also kept up to date but the stats bar was nowhere to be seen)
- even if not having a status bar with all the info on it is acceptable (which of course it isn't, but lets just say), the sytem became completely instable after 5minutes of operation... with each app taking turns to shutting down until i kept getting the message "system UI has closed" over and over, to the point that doing a reboot was challenging since i barely had the time to press on the screen between instances of this bloody error message appearing...
...i did of course try and return to my older nandroid backup, but... lo and behold... exactly same behaviour...
so now i have resorted to formatting the internal memory card and flashing a new rom and basically starting over... just what i hope the nandroid would spare me basically :/
question is: does this sort of error sound familiar to anyone? can someone give me a tip maybe on what i may have done wrong?
any opinion, tips& advice much appreciated
I have the exact same problem. It happens on TW Lollipop ROMs. Haven't found a fix. I'm using Philz Touch Recovery and the old no knox bootloader.
Anyone? I have researched this but cannot find any similar problems reported... it can't just be me and pavelcheto...
Maybe it a recovery fault. Faulty backup or faulty restore.
No problems with my older backups. I restored my KitKat TW backup, working fine. Restoring CM12 backups also works fine. I've looked for a new recovery, Philz is discontinued, CWM hasn't been updated for a year and I really don't like TWRP.
I use TWRP 2.8.3.0 and never have (and hopefully never will) encountered any issues with restoring backups.
Considering i recovered 2 separate backups for a total of 3 times (i tried recovering the first backup twice) i doubt the issue was with the recovery itself... however since pavelcheto had no issues with the kk recovery maybe it could be lollipop related?
Anyone successfully recovered a lollipop nandroid backup?
platypus78 said:
Considering i recovered 2 separate backups for a total of 3 times (i tried recovering the first backup twice) i doubt the issue was with the recovery itself... however since pavelcheto had no issues with the kk recovery maybe it could be lollipop related?
Anyone successfully recovered a lollipop nandroid backup?
Click to expand...
Click to collapse
I recovered my lollipop gpe backup a couple of times without a problem.
Data encryption may cause restoring problems.
I have restored CM12 backups (based on 5.0.2) serveral times, no problem there. I've had issues only with TouchWiz Lollipop ROMs, I have tried different custom roms, all get bugged at restore.
pavelcheto said:
I have tried different custom roms, all get bugged at restore.
Click to expand...
Click to collapse
Just to make sure I understand correctly : you mean all TW custom roms you've restored have had problems?
Wonder if anyone else has managed a bug-free restore of a 5.x TW?
Yes, but only on Lollipop. KitKat TW roms restore just fine. I am using Philz Touch Recovery. I have tried 3 different TW Lollipop roms and they all fail to restore properly. No wallpaper, black wallpaper and no status bar. And after a minute or two System UI starts crashing. If then I do factory reset from recovery and the rom starts normally (welcome guide and stuff) and works fine.
bumping this thread because i cant seem to find a solution for this anywhere.
TheAwesomeBit said:
bumping this thread because i cant seem to find a solution for this anywhere.
Click to expand...
Click to collapse
There's no solution for this as per comments above. TW LP is not restorable. You can flash a new lollipop ROM tho'
Sent from my GT-I9505
Good Day Everyone...
I hope you all are fine...
Allow me to explain my story till we hit the big problem that is the hotboot/fastboot...
10 months ago, I bought Samsung Note 4 SM-N910C ... Was switching from Broken screen Note 4... I had a Nandroid backup of it... but while restoring I messed up badly as I wiped the new device IMEI that time... but I managed to find someone to fix the phone and create a backup... Now Why did I change my phone again...? Battery degrading, phone heating and of course from time to another I must restore the IMEI backup as it gets corrupted suddenly and randomly... In addition to the Note 4 Great Offer...
All 3 phones were SM-N910C, however the first 2 came as KitKat 4.4.4 and the latest phone came as Lollipop 5.0.1 ...I didn't really care much as I grabbed the Nandroid and restored it carefully... Everything works great, Until after installing Xposed... softboot / hotboot / fastboot / quickboot whatever you wish to call acts similar to REBOOT but without shutdown... This issue is Critically annoying as I play from time to another with Xposed and rebooting sometimes don't give Xposed enough time to load the modules ... In addition the SIM lock is active at every reboot and the loading TIME...
I took a backup for all my application on Titanium Backup... Preformed a clean Install of Kitkat 4.4.4 ROM on the phone and restored the applications, Hotboot remained the same... I thought perhaps Xposed is the issue... So I went to ADB command ... adb reboot fastboot ... same results ... phone keeps REBOOTING without shutdown...
How Reboot without Shutdown? Do I know the difference between Hotboot & Reboot?
Yes I do know the difference...
a Reboot would go to shutdown animation, reboot to Samsung NOTE 4 then load the BootAnimation followed by its loop till device has loaded, reboot clears all memory and reload everything, Enter SIM Lock and takes time...
a Hotboot would go immediately to BootAnimation then loop while in the background it's just refreshing the Apps and services briefly, no SIM Lock needed, it doesn't take time...
My HOTBOOT is doing same as REBOOT but skipping the Shutdown animation...
So my Question: What is wrong with my Hotboot? Is it Lollipop? Do I need to check something?
I Thank you all for your patience and reading all what I wrote whether you Answered or not...
P.S: Some Xposed apps are acting weird on this phone compared to the 2 previous Note 4 phones...
Dante63 said:
Good Day Everyone...
I hope you all are fine...
Allow me to explain my story till we hit the big problem that is the hotboot/fastboot...
10 months ago, I bought Samsung Note 4 SM-N910C ... Was switching from Broken screen Note 4... I had a Nandroid backup of it... but while restoring I messed up badly as I wiped the new device IMEI that time... but I managed to find someone to fix the phone and create a backup... Now Why did I change my phone again...? Battery degrading, phone heating and of course from time to another I must restore the IMEI backup as it gets corrupted suddenly and randomly... In addition to the Note 4 Great Offer...
All 3 phones were SM-N910C, however the first 2 came as KitKat 4.4.4 and the latest phone came as Lollipop 5.0.1 ...I didn't really care much as I grabbed the Nandroid and restored it carefully... Everything works great, Until after installing Xposed... softboot / hotboot / fastboot / quickboot whatever you wish to call acts similar to REBOOT but without shutdown... This issue is Critically annoying as I play from time to another with Xposed and rebooting sometimes don't give Xposed enough time to load the modules ... In addition the SIM lock is active at every reboot and the loading TIME...
I took a backup for all my application on Titanium Backup... Preformed a clean Install of Kitkat 4.4.4 ROM on the phone and restored the applications, Hotboot remained the same... I thought perhaps Xposed is the issue... So I went to ADB command ... adb reboot fastboot ... same results ... phone keeps REBOOTING without shutdown...
How Reboot without Shutdown? Do I know the difference between Hotboot & Reboot?
Yes I do know the difference...
a Reboot would go to shutdown animation, reboot to Samsung NOTE 4 then load the BootAnimation followed by its loop till device has loaded, reboot clears all memory and reload everything, Enter SIM Lock and takes time...
a Hotboot would go immediately to BootAnimation then loop while in the background it's just refreshing the Apps and services briefly, no SIM Lock needed, it doesn't take time...
My HOTBOOT is doing same as REBOOT but skipping the Shutdown animation...
So my Question: What is wrong with my Hotboot? Is it Lollipop? Do I need to check something?
I Thank you all for your patience and reading all what I wrote whether you Answered or not...
P.S: Some Xposed apps are acting weird on this phone compared to the 2 previous Note 4 phones...
Click to expand...
Click to collapse
Lollipop 5.1.1 fix the "Hotboot" problem, also disable fingerprint (it's the main cause).
Next iteration of update will fix fingerprint problem.
d4rkkn16ht said:
Lollipop 5.1.1 fix the "Hotboot" problem, also disable fingerprint (it's the main cause).
Next iteration of update will fix fingerprint problem.
Click to expand...
Click to collapse
Thank you @d4rkkn16ht for responding...
So I should Flash lollipop 5.1.1 then flash back to kitkat?
I have done many tests for hotboot via trying multipl 4.4.4e apps... 2 apps out of 6 managed to hotboot...
Xposed installer failed...
TWRP manager failed...
APM+ failed...
Fastboot failed...
Simple reboot success...
Root toolbox success...
I have Kitkat 4.4.4 on my phone... Rooted with TWRP recovery and xposed installed... Busybody is present... Selinux enforcing... What more information do I need to provide?
Dante63 said:
Thank you @d4rkkn16ht for responding...
So I should Flash lollipop 5.1.1 then flash back to kitkat?
I have done many tests for hotboot via trying multipl 4.4.4e apps... 2 apps out of 6 managed to hotboot...
Xposed installer failed...
TWRP manager failed...
APM+ failed...
Fastboot failed...
Simple reboot success...
Root toolbox success...
I have Kitkat 4.4.4 on my phone... Rooted with TWRP recovery and xposed installed... Busybody is present... Selinux enforcing... What more information do I need to provide?
Click to expand...
Click to collapse
XPOSED is still problematic on TW odexed Lollipop ROM, so it is not recommended to install EXPOSED on your Note 4 with Lollipop.
Fingerprint causing many problem on Lollipop 5.0.1 - 5.1.1 (sudden lag, random hotboot, random apps kill), so disable fingerprint while you are on Lollipop.
Some said that COI update (5.1.1) fix fingerprint bug.
d4rkkn16ht said:
XPOSED is still problematic on TW odexed Lollipop ROM, so it is not recommended to install EXPOSED on your Note 4 with Lollipop.
Fingerprint causing many problem on Lollipop 5.0.1 - 5.1.1 (sudden lag, random hotboot, random apps kill), so disable fingerprint while you are on Lollipop.
Some said that COI update (5.1.1) fix fingerprint bug.
Click to expand...
Click to collapse
I am really getting lost...
You talk about Lollipop while I have downgraded to Kitkat... In other words, I have kitkat now on my phone... With hotboot problem...
Dante63 said:
I am really getting lost...
You talk about Lollipop while I have downgraded to Kitkat... In other words, I have kitkat now on my phone... With hotboot problem...
Click to expand...
Click to collapse
Upgrade to lollipop then, but you can't install Xposed on stock ROM
d4rkkn16ht said:
Upgrade to lollipop then, but you can't install Xposed on stock ROM
Click to expand...
Click to collapse
By why?
My two previous phones had KitKat and no problems...
Dante63 said:
By why?
My two previous phones had KitKat and no problems...
Click to expand...
Click to collapse
After a few KitKat updates my phone started random hotboot too.
On lollipop 5.1.1 (COH update) it's all gone with 2 drawbacks.
Fingerprint must be off or I'll get another random hotboot+random lag.
Xposed Framework is out of the question for Stock 5.1.1 ROM.
The only way to install Xposed is to flash non a TW ROM or flash a Deodexed Stock ROM which is not my preferences as XPOSED for 5.1.1 is still in ALPHA stage.
COI update said to be the best update as it fix fingerprint bug. But COI update is still unavailable in my country.
Since no solutions were found...
I'd share mine... You need Root...
Simply use this apk:
https://play.google.com/store/apps/details?id=simple.reboot.com
Create a widget and drop it on the home screen...
This solution is temporarily until the cause is found which will likely take a lot of time...
After upgrading to Andriod N on the 6p, many of us have been plagued by the Bootloop of Death and/or random reboots. Some have tried RMAs, have purchased new devices or moved to backup devices. Huawei has claimed software is the culprit and Google has stated that it's the hardware. Personally I've tried a clean install of the ROM, Dirty flashing the ROM, clearing the caches, etc.
Nothing has worked... Until now!
I'm days in without a single random reboot or Bootloop.
This advice is provided without warranty or any guarantee that it'll work for you but it may work.
I'm not a developer and I've not tried multiple devices.
Steps:
*Note I'm on the latest Pure Nexus build.
1. If you're currently stuck in a Bootloop, then leave your 6p to Bootloop until it actually starts or until the battery dies. If it starts skip to step 3.
2. If it Bootloops, then intervene occasionally by getting the device to boot into the bootloader (Hold down power and volume down). Once there, attempt to reboot recovery. It'll probably keep Bootlooping but occasionally the device will start up.
3. Once your 6p starts, download the ElementalX apk from the Google Play Store. Don't do anything else. I've only tried this app so it's the only one that I recommend for this "fix".
4. Download the ElementalX kernel through the ElementalX app and follow the prompts in order to install the kernel. Allow it to reboot. *You may be able to complete the following steps with the stock kernel.
5. Once your device has rebooted, open the ElementalX app and click the leaf icon in order to enable power saving. This will lower your CPU's freq, GPU's freq, and most importantly, it will disable the BIG CPU cluster.
After these steps were completed I haven't experienced any random rebooting or Bootloops. Yes, this ”fix" hobbles your device but it is still quite functional. I think that on Nougat the constant switching between the two processor clusters causes random restarts and Bootlooping.
There may be an alternative that will allow you to disable the little CPU cluster instead and not lower the GPU performance. I've not tried any other methods yet.
Specs added thanks to @510jungleboy
Nexus 6p 128 GB
ROM: Pure Nexus 7.1.2 r6
Kernel: ElementalX
Bootloader: Unlocked
Recovery: TWRP
Warranty: Expired
Please comment with results.
Multiple people have reported getting the boot loop of death while on Marshmallow. I think the idea that Nougat is causing the problem was discredited long ago, the fact that its a hardware issue with these phones is widely accepted and that the age of the phone is much more of a factor than the operating system you are running. Most of these phones are experiencing the boot loop of death shortly after the warranty expires, when the phone is 12-14 months old. Your phone is generating less heat since you ramped down the CPU which is likely why it isn't currently bootlooping.
Well...
jhs39 said:
Multiple people have reported getting the boot loop of death while on Marshmallow. I think the idea that Nougat is causing the problem was discredited long ago, the fact that its a hardware issue with these phones is widely accepted and that the age of the phone is much more of a factor than the operating system you are running. Most of these phones are experiencing the boot loop of death shortly after the warranty expires, when the phone is 12-14 months old. Your phone is generating less heat since you ramped down the CPU which is likely why it isn't currently bootlooping.
Click to expand...
Click to collapse
You may be right but I didn't notice any Bootloops or random reboots until I upgraded to Nougat. After putting this "fix" in place my device still gets pretty warm under load but it doesn't exhibit random reboots or Bootloops... Heat didn't seem to be the issue since my phone would reboot into a Bootloop while just sitting on my desk at work with only background tasks running. Regardless, this workaround works for me and it may work for others.
Mine just reboots over and over, for days and days, my bootloader is locked and usb debugging is off.
HOW would one install APk from playstore if their phone can't even load up, aka bootloop of death ? You need to be more specific , like locked bootloader , unlock bootloader ..etc.... smh
Once battery dies what i have to do? (my phone dies two hours ago when I was with a 3% of charge and its bootlooping over and over) Full charge? Another thing?
Note:
1)I'm on the latest Pure Nexus build, stock kernel, unlocked bootloader
2)When i connect to the charger one hour ago the phone shows battery charge mode but stills bootlooping. I'm waiting to battery dies
jhs39 said:
Multiple people have reported getting the boot loop of death while on Marshmallow. I think the idea that Nougat is causing the problem was discredited long ago, the fact that its a hardware issue with these phones is widely accepted and that the age of the phone is much more of a factor than the operating system you are running. Most of these phones are experiencing the boot loop of death shortly after the warranty expires, when the phone is 12-14 months old. Your phone is generating less heat since you ramped down the CPU which is likely why it isn't currently bootlooping.
Click to expand...
Click to collapse
510jungleboy said:
HOW would one install APk from playstore if their phone can't even load up, aka bootloop of death ? You need to be more specific , like locked bootloader , unlock bootloader ..etc.... smh
Click to expand...
Click to collapse
Sorry that I wasn't more specific. My bootloader is unlocked and I'm rooted. Users may not need to be in order to get back the device's functionality.
It's a shot in the dark but if a user that is having the Bootlooping issue follows my steps, then they may get back up and running. I've yet to have another random reboot or a Bootloop since...
RyomaEchizen said:
Once battery dies what i have to do? (my phone dies two hours ago when I was with a 3% of charge and its bootlooping over and over) Full charge? Another thing?
Note:
1)I'm on the latest Pure Nexus build, stock kernel, unlocked bootloader
2)When i connect to the charger one hour ago the phone shows battery charge mode but stills bootlooping. I'm waiting to battery dies
Click to expand...
Click to collapse
Since it's died, you'll need to power it on once it's charged for a while. When you power on and it starts Bootlooping, boot into the bootloader and follow my steps. If it Bootloops continuously, boot into the bootloader again and try to get into recovery. It will probably continue to Bootloop. That's what happened to me. I'd come back to it from time to time, boot to the bootloader, prompt it boot to recovery... over and over again. Eventually, it would fully boot up instead (not into recovery).
If it starts DON'T check messages or try to use your phone normally. Instead, follow the steps. Seriously. I made that mistake over and over again.
FYI: This process can take a looong time. Not days but sometimes it was hours until I figured my solution out. I don't know exactly how long it takes because I'd leave the phone Bootlooping and come back to it later in the day.
Many thanks!
Its work for my nexus 6p too
My nexus work normal in interval 1-5% of charge. If charge increase 11% - bootloop...
After enable powersave elementalx, charging to 100% and work well
I have a smartphone. Automatically went into reboot, but did not boot. It constantly reboots. First, the test is reflected that I've been unlocked by the bootloader, and then the Google inscription, and after that the smartphone reloads again. The recovery menu does not enter.
Thanks! Finally something that worked! The big cluster is indeed the problem. I had the porblem that the phone freezes and gets stuck in the bootloop when the battery is above 10-12%. I guess that the cpu disables the big cluster when you are underneath that threshhold(?).
One big problem I am still facing is that I can't reboot my phone and I have to make it discharge until I can boot it up again. Do you have have something that prevents that?
Big thanks again!
Still bootloops
haieb said:
Thanks! Finally something that worked! The big cluster is indeed the problem. I had the porblem that the phone freezes and gets stuck in the bootloop when the battery is above 10-12%. I guess that the cpu disables the big cluster when you are underneath that threshhold(?).
One big problem I am still facing is that I can't reboot my phone and I have to make it discharge until I can boot it up again. Do you have have something that prevents that?
Big thanks again!
Click to expand...
Click to collapse
I followed all the steps but my Nexus 6P still bootloops after crossing 10% charging. Is it possible for you to share your Kernel Manager settings screenshots please?
I too began to experience the boot loop issue literally 8 days after my warranty expired which was 11 days ago today! Have tried flashing several factory images from MM to N and even a saved backup I made from day 1 of having the phone. This method of disabling the big cluster thru ExK has definitely been the furthest I have gotten. Me and my friend(da guy) did find out that in order for the phone to boot up at all, the battery has to be at approx. 6% or lower. In that time is when you must quickly download ExK and activate power saver mode. I just called Huawei support and they did absolutely nothing to help me in this manner. I really do hope that this lawsuit wins in our favor. Speaking of which, does anybody know where we can check for status of this current litigation?
Update: Ordered a new battery and installed it... still bootlooping. This is very frustrating as i have been forced to use my ancient Moto Droid X2 as my daily
I wonder if someone could compile a kernel that always disables the big cluster for those with bootloop problems. Then you could just flash the kernel and not have to try repeatedly to get the phone to boot long enough to install the app.
Sent from my Galaxy S8 using Tapatalk
inneyeseakay said:
I wonder if someone could compile a kernel that always disables the big cluster for those with bootloop problems. Then you could just flash the kernel and not have to try repeatedly to get the phone to boot long enough to install the app.
Sent from my Galaxy S8 using Tapatalk
Click to expand...
Click to collapse
is this possible?
headcreepz said:
is this possible?
Click to expand...
Click to collapse
I'll have to look into kernel building, but I'd imagine if you built a kernel that had powersaving as the default profile, it would work.
Got into recovery long enough to flash pure Nexus and root, but haven't been able to get it to boot yet.
Looking forward to one day being able to use it again. ?
Sent from my Galaxy S8 using Tapatalk
A little help!
nicotinic said:
After upgrading to Andriod N on the 6p, many of us have been plagued by the Bootloop of Death and/or random reboots. Some have tried RMAs, have purchased new devices or moved to backup devices. Huawei has claimed software is the culprit and Google has stated that it's the hardware. Personally I've tried a clean install of the ROM, Dirty flashing the ROM, clearing the caches, etc.
Nothing has worked... Until now!
I'm days in without a single random reboot or Bootloop.
This advice is provided without warranty or any guarantee that it'll work for you but it may work.
I'm not a developer and I've not tried multiple devices.
Steps:
*Note I'm on the latest Pure Nexus build.
1. If you're currently stuck in a Bootloop, then leave your 6p to Bootloop until it actually starts or until the battery dies. If it starts skip to step 3.
2. If it Bootloops, then intervene occasionally by getting the device to boot into the bootloader (Hold down power and volume down). Once there, attempt to reboot recovery. It'll probably keep Bootlooping but occasionally the device will start up.
3. Once your 6p starts, download the ElementalX apk from the Google Play Store. Don't do anything else. I've only tried this app so it's the only one that I recommend for this "fix".
4. Download the ElementalX kernel through the ElementalX app and follow the prompts in order to install the kernel. Allow it to reboot. *You may be able to complete the following steps with the stock kernel.
5. Once your device has rebooted, open the ElementalX app and click the leaf icon in order to enable power saving. This will lower your CPU's freq, GPU's freq, and most importantly, it will disable the BIG CPU cluster.
After these steps were completed I haven't experienced any random rebooting or Bootloops. Yes, this ”fix" hobbles your device but it is still quite functional. I think that on Nougat the constant switching between the two processor clusters causes random restarts and Bootlooping.
There may be an alternative that will allow you to disable the little CPU cluster instead and not lower the GPU performance. I've not tried any other methods yet.
Specs added thanks to @510jungleboy
Nexus 6p 128 GB
ROM: Pure Nexus 7.1.2 r6
Kernel: ElementalX
Bootloader: Unlocked
Recovery: TWRP
Warranty: Expired
Please comment with results.
Click to expand...
Click to collapse
I really want this to work. Can you please share your settings? I'm not getting passed 10-12% charge. It makes a loud noise and bootloop till around 6% but runs fine if it's below 10%. I can watch videos and listen to music
Same issue !
haieb said:
Thanks! Finally something that worked! The big cluster is indeed the problem. I had the porblem that the phone freezes and gets stuck in the bootloop when the battery is above 10-12%. I guess that the cpu disables the big cluster when you are underneath that threshhold(?).
One big problem I am still facing is that I can't reboot my phone and I have to make it discharge until I can boot it up again. Do you have have something that prevents that?
Big thanks again!
Click to expand...
Click to collapse
Did u ever figure it out? Also can u show me some screenshots of your settings?
Got mine up and running!! [emoji41]
Here are my settings:
Sent from my Galaxy S8 using Tapatalk
UPDATE: Please read the next post.
A while back, I rooted my v20 with magisk using this method and everything worked fine for a few months, except for a few issues that reflashing the system would fix. Last night, SystemUI kept crashing (the status bar and the buttons would disappear). After a while, the phone crashed, and then it completely refused to boot. It would very rarely get to the lock screen, but it usually crashes soon after I unlock it. I tried everything I know of that could fix it, such as restoring the boot partition and reflashing magisk, reflashing the system partition, and wiping the cache and dalvik/ART cache. I eventually gave up with this and just reset it through the wipe menu in TWRP. I was able to get the phone to work for about a day without any issues, and then the same thing started happening again. It would take a really long time to boot and the system would crash. I tried using that ~1 minute it gives me before crashing to enable core mode in magisk to prevent any modules from loading, but that didn't do anything. I am really confused as to why this would happen considering that I reset the boot and system partitions multiple times in this process, and eventually did a full reset. It should be like a brand new phone. I really don't know what could possibly be the issue. Any help would be greatly appreciated.
Update: It turns out that Magisk Core Only Mode did not properly apply because of yet another crash. I cleared my cache once more, which gave me enough time to properly apply it, and now my phone is staying on and not crashing. But this still is concerning to me. I was able to run Magisk modules perfectly fine in the past, including after the most recent Magisk zip update, so why is it that I can no longer run modules, and that this issue persists after a factory reset? It can't be an update, because, as I stated, I was able to run modules just fine for at least a week before these issues occurred. Please correct me if I'm wrong, but this makes absolutely no sense and I want to be able to run modules again. I even deleted the modules through TWRP but the only thing that seems to fix this issue is completely disabling all other features via Magisk Core Only Mode.
Update 2: A Magisk update came out recently and I tried updating to that to see if it would fix the issue. This only brought back the original crashes. I tried using the Magisk uninstaller zip (because I found that simply reflashing Magisk isn't enough, there are other files which magisk uses to store data.) After doing this and reflashing Magisk, it worked for a little bit, but, me being me and wanting busybox installed, I managed to bring back the crashes. After that, uninstalling and flashing magisk would work, but only until a reboot. I am at a complete loss. I am currently backing up my internal storage (manually since TWRP doesn't) and I will try a full /data format.
Ok, it has been a few days since I wrote the previous section but I decided not to post it because if the /data format worked, I didn't want to have bumped it for no reason. At first, it worked, and I decided to leave it like that without rebooting it for a few days or messing with Magisk, and my phone worked perfectly. I had to restart my phone because Google photos was acting up, and it started crashing again. I am genuinely confused. I completely formatted my phone and reflashed Magisk several times, and it is still crashing. I just reset my phone again because I attempted to just restore a stock boot backup from before I installed Magisk, which made my phone completely unbootable. I pulled the battery and found that it tried re-encrypting the phone (AFAIK, TWRP doesn't support encrypted data on the v20, which really sucks) so I had to wipe it and flash Magisk so it wouldn't re-encrypt it. I will try to do this again, but I don't want to not be able to restart my phone (which is so far the only thing that's working for me). This time, not even uninstalling and re-flashing Magisk worked this time, as it has all of my previous attempts. I had to completely reset it. Again. I really need this issue fixed. I probably already said this, but I would greatly appriciate any possible help I could get. I really want my phone back.
Ok I forgot to include some basic information about my phone.
Model number: LG-H910
Android version: 7.0
Android security patch level: April 1, 2017
Kernel version: 3.18.55
Build number: NRD90M
Software version: H91010m
According to Kernel Auditor:
Kernel: Linux version 3.18.55-Werewolf-2.0-Basilisk ([email protected]) (gcc version 6.3.1 20170430 (GCC) ) #1 SMP PREEMPT Sat Jun 24 00:56:07 CDT 2017
Bump/Update: This is a small one, but, despite not restarting my phone, Magisk is showing an error "Magisk is not installed". Root access also disappeared. I don't know how much longer I can keep it on without having to restart it due to random issues like these that usually fix themselves with a reboot. I would appreciate any help.
Seems like your phone is all sorts of wacked out. I noticed from the specs your using the werewolf kernel. I had all sorts of performance issues as well as random reboots using that kernel. Since you're losing root and the system is overall unstable I recommend wiping clean and starting over. Wipe system, data, cache, and dalvik in twrp and flash the full stock 10r zip by runningnak3d. It will put you on the latest security patch with the newest firmware available. I recommend installing askerm2000 1.4 kernel as it is very stable and works well on the h910. Flash magisk last (latest 15.3 works great for me) and reboot. Hopefully will solve your problems. The 10r zip for the h910 plus askermk2000 kernel and magisk has served me well for a while now.
toastyp said:
Seems like your phone is all sorts of wacked out. I noticed from the specs your using the werewolf kernel. I had all sorts of performance issues as well as random reboots using that kernel. Since you're losing root and the system is overall unstable I recommend wiping clean and starting over. Wipe system, data, cache, and dalvik in twrp and flash the full stock 10r zip by runningnak3d. It will put you on the latest security patch with the newest firmware available. I recommend installing askerm2000 1.4 kernel as it is very stable and works well on the h910. Flash magisk last (latest 15.3 works great for me) and reboot. Hopefully will solve your problems. The 10r zip for the h910 plus askermk2000 kernel and magisk has served me well for a while now.
Click to expand...
Click to collapse
Thank you. Before I do this, I have a few questions.
1. How do I disable force encrypt with Magisk? I remember when I flashed Magisk 14.0, that managed to disable force encrypt, but any other version of Magisk wouldn't do that when installing fresh (updates kept this setting). AFAIK TWRP is unusable on the v20 for things such as backups, file browser, etc because it isn't compatible with the encryption algorithm used by the v20. How would I turn off force encrypt with the latest Magisk zip
2. Should I do a full format data (where you have to actually type "yes" to confirm it) or just wipe those partitions using advanced wipe?
3. Will the askerm2000 kernel hide modified boot, unlocked bootloader, etc from safetynet just as Werewolf kernel did, and will it get rid of the static boot issue?
4. Will this increment ARB? If anything goes wrong, I want to be able to roll back.
5. If it was working perfectly fine before, what suddenly made everything come crashing down, even after multiple wipes? This is not as important as the other ones, I am just curious.
Sorry if these questions seem over excessive and/or obvious. Doing stuff like this tends to make me a bit nervous and I want to think of everything I can that might affect the outcome.
NullBite said:
Thank you. Before I do this, I have a few questions.
1. How do I disable force encrypt with Magisk? I remember when I flashed Magisk 14.0, that managed to disable force encrypt, but any other version of Magisk wouldn't do that when installing fresh (updates kept this setting). AFAIK TWRP is unusable on the v20 for things such as backups, file browser, etc because it isn't compatible with the encryption algorithm used by the v20. How would I turn off force encrypt with the latest Magisk zip
2. Should I do a full format data (where you have to actually type "yes" to confirm it) or just wipe those partitions using advanced wipe?
3. Will the askerm2000 kernel hide modified boot, unlocked bootloader, etc from safetynet just as Werewolf kernel did, and will it get rid of the static boot issue?
4. Will this increment ARB? If anything goes wrong, I want to be able to roll back.
5. If it was working perfectly fine before, what suddenly made everything come crashing down, even after multiple wipes? This is not as important as the other ones, I am just curious.
Sorry if these questions seem over excessive and/or obvious. Doing stuff like this tends to make me a bit nervous and I want to think of everything I can that might affect the outcome.
Click to expand...
Click to collapse
Twrp can properly decrypt the v20. Twrp backup and restore works just fine for me. Never had an issue with this. You format data and then type yes. Wipes the data partition but this is only needed once. Decrypts the device and twrp can then do it's thing. Encryption problems stem from booting into system with a stock boot image that has force encryption enabled without flashing magisk or supersu. They modify the kernel to prevent the device from rencrypting. Latest magisk 15.3 has zero issues keeping the phone decrypted. The modified boot warning has nothing to do with the kernel. This is caused by the debug bootloader used to achieve root on the US carrier v20's. Nothing can be done to change that. ARB has not been incremented on the h910 so that isn't an issue currently. Potentially in the future, but not right now. The problems you're having could stem from a multitude of issues. Could be modifications you made, bad flashes, etc. If you're having issues with encryption and stuff sounds like magisk wasn't functioning properly at the end. I've been rooted since last January and haven't experienced anything like that before so I'm not sure
toastyp said:
Twrp can properly decrypt the v20. Twrp backup and restore works just fine for me. Never had an issue with this. You format data and then type yes. Wipes the data partition but this is only needed once. Decrypts the device and twrp can then do it's thing. Encryption problems stem from booting into system with a stock boot image that has force encryption enabled without flashing magisk or supersu. They modify the kernel to prevent the device from rencrypting. Latest magisk 15.3 has zero issues keeping the phone decrypted. The modified boot warning has nothing to do with the kernel. This is caused by the debug bootloader used to achieve root on the US carrier v20's. Nothing can be done to change that. ARB has not been incremented on the h910 so that isn't an issue currently. Potentially in the future, but not right now. The problems you're having could stem from a multitude of issues. Could be modifications you made, bad flashes, etc. If you're having issues with encryption and stuff sounds like magisk wasn't functioning properly at the end. I've been rooted since last January and haven't experienced anything like that before so I'm not sure
Click to expand...
Click to collapse
Ok, I cannot possibly thank you enough for this. After this started happening, I seriously thought my phone was at the end of its life. If this were to happen, I wouldn't be able to get a new phone anytime soon. Not only did it fix the crashes (I only restarted it once, I'm not going to try to intentionally make it crash), It ALSO managed to fix my FM radio and (I think) the Google Assistant Voice Match unlock thing, both of which I never even thought I would be able to get back. Let's just hope that it stays this way. I have one last question. Would you say it's safe to download and install Magisk modules now?
NullBite said:
Ok, I cannot possibly thank you enough for this. After this started happening, I seriously thought my phone was at the end of its life. If this were to happen, I wouldn't be able to get a new phone anytime soon. Not only did it fix the crashes (I only restarted it once, I'm not going to try to intentionally make it crash), It ALSO managed to fix my FM radio and (I think) the Google Assistant Voice Match unlock thing, both of which I never even thought I would be able to get back. Let's just hope that it stays this way. I have one last question. Would you say it's safe to download and install Magisk modules now?
Click to expand...
Click to collapse
Yes. I use a few modules myself without an issue. If you're unsure of the stability of a module, you can always take a nandroid backup in twrp prior to installation. If things are stable, and then you flash something and the phone freaks out, it's most definitely the mod you have flashed causing problems. Some modules make changes to the system partition that have the potential to problems. But I haven't had a module cause my device to bootloop or reencrypt. So I think you're good to go. Glad you're phone is up and running as it should. Very strange that it was in such a bad way, but crap happens. I have had zero issues with this setup (10r + 1.4 askermk kernel + magisk 15.3).
I have the stock firmware on the H990 version, I end up on the Crash LK screen error. I can access TWRP, how can I restore access to my device without losing data? Thanks.
Morning guys.
I'm having an issue with my 6p.. Last night while I was browsing 9gag application, my phone had a crash/bug and went into boot loop. The phone battery was around 16% when this happened. And since then I haven't been able to boot into the system. I have already succeed in flashing twrp and formatting all the data from there as it seemed that the data could've been corrupted or something like that. After that I have also succeeded i
<bcuraboy> n installing DU and the vendor on it. However the problem persists and I can't boot into the system... It remains in some kind of boot loop although fastboot is working fine... What could be the culprit of this and how to solve it??
Thanks a lot in advance
You try any of the 4 core mods see if it's the big cores causing the problem? I believe there is a universal one check out the threads for BLOD. You can always revert back.