Database Develop

Can't boot from stock internal eMMC

On my eMMC I have a stock Nook Color OS which is rooted. Worked great for quite a while. Last night I force shut it down (held the power button for 10 seconds).
Today I'm trying to boot it back up and it won't boot. I see the "Reading Forever" logo, then the "Nook Color" logo (believe from the rooting) comes up. That logo animates once, then it repeats, but stops at "Nook Co" stops, and the just keeps looping like that forever. Never finishes booting up.
Now I can boot up with my CWR SD card and also from my CM7 SD card. I'm hoping there might be some easy fix to be able to boot my stock rooted image again without having to wipe it out and starting over. Should I clear some cache or some other idea?
Thanks.
Update: I decided to just go ahead and blow way the install and do a factory wipe and reload and reroot it again. After I did this, I started wondering, I had Nook OS 1.2 installed and rooted. I wonder if 1.3 might have automatically installed on me and blown up because of the root? *shrug* Well, don't matter now. I started over.

Wow... after wiping it and starting over. It happened again.
Everything was going well. Rooted successfully, Market mostly working, installed a few apps. Rebooted a few times without issue. Then I noticed some apps were missing from the Market that should be there (no ADW.Launcher) so I was doing the normal Market fix. Shut down. Powered up, now it's hanging again on that "Nook Color" animated logo.
Argh! Maybe it's a sign I need a Kindle Fire. Haha.

Did another factor wipe. Rooted it again. All going well. And finally once again tried to do the Market fix. Cleared the Market cache, cleared the Framework data. Powered off. And again it won't boot back up.
This is so weird. I've done that millions of times before without issue.

Curious. Tried again after another factory wipe. And this time I decided to not bother with the Market app. All is going well. Until I reboot after the newest Market (with the music section) installs. It's all fubar again.
Could be the reason it blew up in the first place too. Hmm... Wondering if anyone has been able to reboot their rooted Nook Color since getting this new Market without issue?

Search the forums, there is a thread on this issue, you have to keep it from updating Adobe flash I think. I had this problem too, but haven't had time to root again and check for myself.
Sent from my HTC Sensation 4G using XDA App

The issue I'm having definitely seems to have the exact same symptoms those with the Flash Player issue are having.
But I never installed or updated Flash, manually anyway. And I installed the Flash Player fix and it still didn't fix my boot up problem. Bummer, thought it was going to be it.
I think I'll do another factory wipe, go through the process again. And when I see the Market update (kinda still my only suspect at the moment), I'll go in and uninstall that update and reboot and see what happens.

It's the Adobe AIR update. Argh.
I had gone through my factor wipe/root process again, I immediately uninstalled the Market update as soon as it came. Also looked for Flash Player and it isn't installed. Rebooted and it still blew up.
So I went through the start over process again. And since an Adobe Flash Player updated caused problems similar to mine and while I don't have Flash, I do have Adobe AIR and it happens to be updating after I run Market. So this time I was able to cancel that Adobe AIR update. Rebooted. And it is still working.
Apparently that Flash Player Fix tool doesn't seem to work with Adobe AIR and that update is breaking my Nook Color.

Fire 5.1.2 Brick... What went wrong?

So I bricked my new Fire and I'm trying to figure out what went wrong. It came with 5.1.3 and I successfully downgraded to 5.1.2 and was able to root with Kingroot. Unfortunately SuperSU-Me never worked to replace King with SuperSU and I was unable to replace it manually. I tried multiple times, reflashing a clean image of 5.1.2 each time. Today I was going to give it another shot and started by reflashing the image I flashed a dozen time yesterday, both ADB and the tab said it was successful. I rebooted and its hard bricked. The screen and backlight never come on but if plugged into a computer you hear the usb connect and disconnect sound. Will not boot into recovery or fastboot.
Is this just a fluke or is there anything that may have happened? I just don't want a repeat... I like learning from mistakes but I don't have any ideas or anything to go on.

PIYIRIO said:
So I bricked my new Fire and I'm trying to figure out what went wrong. It came with 5.1.3 and I successfully downgraded to 5.1.2 and was able to root with Kingroot. Unfortunately SuperSU-Me never worked to replace King with SuperSU and I was unable to replace it manually. I tried multiple times, reflashing a clean image of 5.1.2 each time. Today I was going to give it another shot and started by reflashing the image I flashed a dozen time yesterday, both ADB and the tab said it was successful. I rebooted and its hard bricked. The screen and backlight never come on but if plugged into a computer you hear the usb connect and disconnect sound. Will not boot into recovery or fastboot.
Is this just a fluke or is there anything that may have happened? I just don't want a repeat... I like learning from mistakes but I don't have any ideas or anything to go on.
Click to expand...
Click to collapse
- there is always a risk associated with flashing (reloading/sideloading FireOS) sensitive bootloader components as a single flipped bit can/likely will brick the device; flakey usb cables are a common culprit
- avoid KingRoot builds >4.96 as removal can be problematic
- recommend using the latest 5th gen SuperTool to transition from KingUser to SuperSU after rooting; SuperSume is increasing ineffective, especially on more recent versions of FireOS and/or KingRoot (not sure which).

Rooting Samsung Galaxy Tablet E (8.0) SM-T377V Please Help

So I've had success rooting the SM-T377V thanks to electronhacker post on the forums.
I thought I would give my experience because anyone else doing this will most likely run into the same problems I did. I still have a few problems I am running into. I hope someone can help me out.
electronhacker had said to downgrade to stock firmware LMY47X.T377VVRU1AOL7 (5.1.1) Lollipop, from firmware MMB29K.T377VVRS1BPL1 (6.0.1) Marshmallow using Odin.
I ran into problems finding LMY47X.T377VVRU1AOL7 but I eventually did find it on samsung-firmware.org Thank you moonsh0t!
It did actually work and passed with Odin, however it got stuck in a bootloop. I thought there was nothing that could be done but after looking into the bootloop matter more I figured out how to get out of it and start it up.
1.) Wait for the device to turn off while it's bootlooping.
2.) Then hold down the power button and the volume up buttons to enter recovery mode.
3.) Restore factory defaults. "I think this actually gave me an error but clearing the cache got it to work."
4.) Clear the cache.
5.) Reboot the device.
There you have it now you're out of your bootloop, the device will start up now.
Now that we have downgraded electronhacker had said to run a program called Kingoroot using the Windows application.
I ran Kingoroot and it got stuck at 44% and my screen went black and would not come on or turn off. I am pretty sure you call this a soft brick, but maybe it's called hard brick as there was nothing that could be done.
So this is what I did to Unbrick the tablet:
1.) Hold the power button and the volume down button for 15 to 30 seconds.
2.) The screen should come back on.
3.) Scroll through settings to reboot device normally.
I tried to use Kingoroot again. This time it got stuck at 51% and my screen on the tablet got stuck. Nothing was responding, not the power buttons, the volume buttons, home button, nor the screen. This is because Google Application had showed up on the tablet while I was in the middle of rooting. The Google Application said "Do you want to enable Google Security?".
Again;
1.) Hold the power button and the volume down button for 15 to 30 seconds.
2.) The screen should come back on.
3.) Scroll through settings to reboot device normally.
The device booted normally and I tried Kingoroot again. I wasn't going to give up. This time it worked, 100% Root Successful. I couldn't believe it the SM-T377V was rooted. I checked and verified with Root Checker.
Now this is where I need help!
#1.) The device only stays rooted until you restart it. Then you have to Re-Root it with Kingoroot every time you restart. I found out if you run SuperSu and go into setting you can stop this from happening. I'm not exactly sure what you do yet because I can NOT get into SuperSu. It tried to install the binaries but gets interrupted by Knox. It says disable Knox on SuperSu but this does NOT work. This tablet does NOT have a way to open Knox in order to disable it. So I need to figure out how to delete it that way I can run SuperSu and stop the never ending root process. So if someone could help me figure out how to do that I would very much appreciate it.
So far I've figured out that you can run an application called Titanium Backup to freeze the Knox files and then remove them followed by a Re-Boot to get rid of Knox. I looked further into my SuperSu problems and found out that you can manually download a SuperSu.apk file that should bypass Knox and actually disable it.
Here is my new problem, installed Titanium Backup from Google Play Store only to find out that I can't freeze the Knox settings unless I pay the $5.99 for Titanium Backup Pro. So I removed Titanium Backup and downloaded Titanium Backup Pro.apk which I found for free on the internet. I can NOT install it though, because I have a new error that says "APP not installed".
This happens with the SuperSu.apk that I found on the internet too. I've tried a lot of things but can't get them to install. Google Play Store gives me error (-504) I've tried clearing cache and data for Google Play Store and Google Play Services but no luck. I even tried downloading APK Installer but it doesn't even work. Please help I don't know what to do.
02-09-2017
<UPDATE>
I'm at a loss, so I decided to do a factory reset from settings and that did not get the applications to install. So then I tried to clear the cache but again no suck luck. Then I decided to enter recovery mode and factory reset, but then got stuck on "Your tablet is getting ready for you". or something along the lines of that and wouldn't get past that on start up. (This is because I disabled setup with another application, and is my fault.) Not being able to get past that I realized I had no choice but to Re-Flash the System Update LMY47X.T377VVRU1AOL7 (5.1.1) Lollipop with Odin and that was successful, thank God. Now I have to Re-Root and before installing the wrong applications, which are Google Play Store SuperSu and Titanium Backup. Reason being that once you install these once and uninstall them you can't install them again without getting error (-504) in Google Play Store or even outside the Google Play Store such as manually downloaded .APK files or you will get the error "APP not installed".
Here is my idea, and I haven't done it yet. Re-Flash, Re-Root, Install for the FIRST time the right SuperSu.apk and Titanium Backup Pro.apk in order to disable Knox and stop the never ending Re-Root every time the tablet it restarted.
02-10-2017
<UPDATE>
I have been running Kingoroot with my PC using USB. This gives me temporary Root access until Re-Boot. So I installed Kingoroot.apk and tried using to mobile application but this one works, but I get stuck in bootloop on restart of tablet. Then have to Re-Flash with Odin to get out of bootloop. I'm not having any luck.
#2.) Even with my temporary root I can not seem to install Xposed because of SDK 22 not supported. I was wondering if anyone knows a way to get it to work on SDK 22 so I can run IMEI Changer. Unless there is another way to change the IMEI without Xposed.
Thank you to electronhacker for your post I found on this forum which has made me a lot of progress, and thank you moonsh0t for your help redirecting me to find that firmware. :good:

I just got a SM-T377V this weekend and have been trying o root it as well. Wow seems like nobody has had any luck getting a reliable root on it. Please update me as you keep at it! Brent your attempts at this are amazing!! Keep at it!

I'm trying to get this thing rooted too, so please keep me updated if you find a
Way!! Thanks for your help!

Yep
Ok

Same issues here. I never have trouble rooting with the APK, but its super annoying having to reroot all the time. also the superuser app is absolute cancer so learning to replace that would be dope.

Alright, so your goal is to run an IMEI changer, but why?
Also my luck was to get it temped root and try and use chainfire's supersu to take over.
from there I tried unlocking the bootloader with samdunk. The issue though, is the CID was deleted from the tablet, so when I restarted, never ending bootloops.
I just Odin'd it back to the AOL firmware today, will look more into samdunk later.

Treyday645 said:
Same issues here. I never have trouble rooting with the APK, but its super annoying having to reroot all the time. also the superuser app is absolute cancer so learning to replace that would be dope.
Click to expand...
Click to collapse
If you use Odin to flash android 5.1.1 via package T377VVRU1AOL7, you can use the kingroot or kingoroot app (desktop or android) to temporarily root the device. From there, if you delete the kingroot or kingoroot app from the device you can use SuperSu to take the binary over. From there you can use any flashing apps you'd like.
The issue is at this point, the second the device turns off, when it comes back it will no longer have root. (note so far in my attempts I've found that Kingroot, will reboot rootless, whereas kingoroot will bootloop.)
Kingoroot will bootloop because it modifies the boot file in some way, which causes the bootlooping. The work around to this is just flashing over the previous android. However, if you flash with Odin, you lose root, but keep your files.
Going back to flashing, when you attempt to use Odin to flash other packages, they are denied, due to the locked bootloader, however, you can use Flashfire to flash these firmwares. I attempted to flash the T-377P firmware and bootloader. Obviously the locked bootloader stayed locked, the recovery partition got errored out, but the android system itself actually started. Just sans root.
It's worth noting I've also attempted using SamDunk, the S5 bootloader unlocking tool, and so far all I've noticed is it deletes the CID file and doesn't finish. So I'm of the impression that the temp root, isn't a full root either.

Help needed to keep my DINC alive!

I have an old DINC that I've used over the years primarily for reading Kindle books and for network troubleshooting. I've been through the CyanogenMod ROMs from 9 to 11, and Evervolv KK. I have TWRP 2.0 installed.
I recently got a Google Cardboard VR viewer, and when I tried to install some software for it from the Play store, I got the bogus "Insufficient space" message, even though the only non-ROM app installed was Kindle and ES File Explorer, and there was. That's when the fun began.
I tried reinstalling ev_inc-4.0.0, using my standard procedure of Factory Reset, Flash ROM and GAPPS, clear dalvik cache and reboot. That got stuck in a boot loop, and then I started to work my way backwards through CM 11, 10.2, 10.1, 10.0, still with either a boot loop or a crash as soon as I tried to turn WIFI on. (At this point I am only flashing the ROM, not GAPPS until I'm convinced the ROM will work).
Finally, I got a copy of Stock_inc_4.08.605.16_deodexed.zip and flashed it with TWRP as usual. It actually seemed to work OK for a while, but still would not install the VR program (insufficient space).
Then I began think about how much of a mess I have probably left lying around nooks and crannies of memory, so I took every "erase" option I could find in TWRP and the boot loader, then went into fastboot:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip ______
fastboot reboot
That worked once, to get the Stock ROM running, but still could not install any software.
Before this all started I made a backup with TWRP. When I restore from that backup, I get a running ROM, but with an ancient version of PlayStore (actually "Market!), and when I try to run that, I get a very long license agreement, with no "OK" button - no way out!
I think I need to somehow get the DINC back to some known place and start fresh, but I'm out of ideas. Please help, someone!
Walt

Ive seen a fix patch for this issue somewhere around here. I just stumbled across it, so you should be able to find it easy, if you already have not.

What New Hell Is This? Boot loop, will not even completely power off.

I thought I had finally reached nirvana with this device thanks to the help of so many here. I had TWRP, root, defeated encryption, and a nicely running Android. I was even able to make TWRP backups of /data and /boot (to be precise, at one point - not sure when it was but I think after initial Android setup - I was able to make a much more complete TWRP backup with many partitions never shown again but that disappeared at some point).
So I went on with my transition from my old Note3 phone to this device. I spent all day yesterday moving TiBackups of user apps, copying across data, making more limited TWRP backups (of data and boot the only options - except if I mounted system_root, which allowed me to include /system but that did not actually work either), polishing settings, and thinking I had it made! Throughout all of this I had no problems or signs of problems other than some apps not working on the new device and having to be replaced with alternatives which I completely expected.
At cocktail hour I decided to do a reboot to see the "finished product" of all this effort. When I did, the device tried to boot into Android: I saw the thinq logo but no boot animation, just the thinq logo for a very long time - followed by a screen blank and bootloop. I was able to enter TWRP and things looked "normal" from there. I kept trying to boot into system with no progress. I tried wiping /data, I tried restoring the backups I had made. Nothing changed - still bootlooping.
From within TWRP I can use adb shell to look around. I can see familiar stuff from my installed apps in /data/data and /data/app - including from one of the very last apps I installed (from Play not via TiBackup). I know this was not in any TWRP backup I had taken or restored. So this makes me think that my attempts to restore /data from backups or even wiping /data from TWRP have had no effect despite no errors showing. I wanted to see what was in /system so I mounted system and now in adb shell I can see familiar stuff in there too - including busybox installed into xbin. I can also mount vendor and in /vendor/etc I can see the fstab.judypn with encryptable for /data.
One thing I do NOT see is the result of one of the last things I did/tested. I installed Termux, installed the dropbear package, and copied the resulting dbclient binary to /data/local. After doing this I actually invoked /data/local/dbclient with success. Now, I do not see anything in /data/data/com.termux/files/usr related to dropbear nor do I see the dbclient in /data/local.
When I tried to power off from TWRP, the device never fully turned off. The animation showing the power level remained showing all the time but it was just a circle with lightening bolt but no actual power level showing. Removing power cable made no difference. Finally, I left the device in TWRP and powered on. At least I could blank the screen and prevent the battery from running dry.
All of this is with slot A current as reported by TWRP. I cannot seem to enter fastboot mode (I was previously able to do this from a power off condition by holding volume up and inserting USB). Of course, I am not able to achieve a real powered-off condition. Thankfully, I am still able to enter engineering mode and see the device in QFIL. But I have not tried anything here as of now. I can switch to slot b and get into download mode by holding power up and inserting USB. All attempts to use other TWRP boot options (save recovery and "power off") just put me into bootloop again.
I am stumped as to what is happening, how to "fix" this, or what to do.
Thanks for any suggestions.

Same thing happened to me. Yesterday.
I was going through my system programs, and nuked several of the extra Google Play items (Movies, Music, etc.). Same thing. Boot to V40 ThinkQ screen. Sat there for a while. Then reboot.
Nothing I did brought the old girl back to life. So I started over with kdz and redid everything again. Pain in the ass, but it's working again. Interestingly enough, loading the full kdz didn't relock the bootloader. I used both Refurbish and Partition DL on two separate attempts. Bootloader stayed unlocked throughout, and is still unlocked.
Had a devil of a time getting system to mount. Tried over and over again to get Magisk installed.
What finally worked was rebooting into recovery after pushing the .magisk file, and only then installing Magisk.
[NG]Owner

NGOwner said:
Same thing happened to me. Yesterday.
I was going through my system programs, and nuked several of the extra Google Play items (Movies, Music, etc.). Same thing. Boot to V40 ThinkQ screen. Sat there for a while. Then reboot.
Nothing I did brought the old girl back to life. So I started over with kdz and redid everything again. Pain in the ass, but it's working again. Interestingly enough, loading the full kdz didn't relock the bootloader. I used both Refurbish and Partition DL on two separate attempts. Bootloader stayed unlocked throughout, and is still unlocked.
Had a devil of a time getting system to mount. Tried over and over again to get Magisk installed.
What finally worked was rebooting into recovery after pushing the .magisk file, and only then installing Magisk.
[NG]Owner
Click to expand...
Click to collapse
Well, they say misery loves company and I do feel a bit better just knowing I am not alone here.
Since I could enter download mode, I too decided to try re-flashing the .kdz using LGUP's partition dl and specifically NOT checking boot_a, laf_a or boot_b as described here <https://forum.xda-developers.com/showpost.php?p=82206107&postcount=115>. I was not fast enough to get into TWRP on the automatic reboot and saw that I was brought to a bootable system and an Android start page with the boot loader still locked and TWRP still there.
So did the partition dl again and managed to catch TWRP. I mounted vendor but when I tried to push the fstab I got something I have not seen before "remote could not create file: Read-only file system" and 0 files pushed. To be sure, I used adb shell and cat'ed /vendor/etc/fstab.judypn and it contains force encrypt. So I know things are not quite right.
Trying again from the partition dl. And this time I managed the push. I think I missed re-doing the ramdisk and rebooting into recovery. I made sure to do that this time and now I can proceed. I seem to have managed to get back to a bootable Android with TWRP, Magisk, and defeated encryption once again.
So I wonder if I should try to restore anything from a backup or just redo all of yesterday's efforts (like the movie Groundhog Day)?
Can I ask which device and firmware you are using? Thanks

I would not use any backups aside from the backups in your google account. Redo all of yesterday's efforts (except the one thing that caused the reboot loop ... whatever that was!).
You said your bootloader was relocked after LGUP? Or did you mistype there?
Odd. Mine wasn't, not once. Despite multiple LGUP loads.
I've got a crossflashed Sprint LM-V405UA to US specs 20E.
And yes, misery does love company!
[NG]Owner

NGOwner said:
I would not use any backups aside from the backups in your google account. Redo all of yesterday's efforts (except the one thing that caused the reboot loop ... whatever that was!).
You said your bootloader was relocked after LGUP? Or did you mistype there?
Odd. Mine wasn't, not once. Despite multiple LGUP loads.
I've got a crossflashed Sprint LM-V405UA to US specs 20E.
And yes, misery does love company!
[NG]Owner
Click to expand...
Click to collapse
No, you are correct - I mistyped. My bootloader has remained unlocked (this time I got it right)
Nor sure it matters any, but mine if a 405QA with 20E.
I have read some recently (while searching for this bootloop problem) that LG seems to have long had a problem with bootloops on their devices. Not sure I saw anything specifically about the V40 though. Seems that in the past they were "fixed" with software updates. I do not expect any updates beyond 20E and wonder if 20a (which I think I had earlier) would be any different/better.
I have had great luck with Nandroid and TWRP backups in the past. They have really saved me (most often from myself but also from apps/mods gone wild). Indeed, I used TWRP restore yesterday with the previous night's auto-made backup on my Note 3. It seems that in doing something - maybe the TiBackup of all user apps/data - the phone got messed up and even reboots would not fix it. The TWRP restore certainly did!
I am new to the whole Magisk "systemless" root as I have always used SuperSu before. As I understand it (which is limited for sure) the idea here is to NOT modify system in any way. But I also note that this does not seem to preclude me from modifying things in system using my file manager, for example. And I did some of this sort of thing. If you are nuking pre-installed apps, that would be changing system as well, no? I wonder if that is the activity that caused this?
I am a bit hesitant to re-live yesterday. At least not until I have some idea of what I did that caused this. Not sure what I will do.
Thanks for all the help.
PS - given that I had TWRP backup (of at least /data) and how often I rely upon these in everyday life, I decided to at least try restoring and see what happened. Hard to imagine ending up worse that I was earlier this morning. I did the restore and rebooted to system. I was shocked, quite frankly, to see the system come right up and have many of my previously installed apps visible and working. I did find that I had to re-enable the modules in EdXposed (even though they showed as enabled already) since they were not working) and that brought them back to life.
So I guess I can move forward from here being careful, taking TWRP backups even more often, and rebooting more often to see what, if anything, kills this again.

NGOwner said:
Same thing happened to me. Yesterday.
I was going through my system programs, and nuked several of the extra Google Play items (Movies, Music, etc.). Same thing. Boot to V40 ThinkQ screen. Sat there for a while. Then reboot.
Nothing I did brought the old girl back to life. So I started over with kdz and redid everything again. Pain in the ass, but it's working again. Interestingly enough, loading the full kdz didn't relock the bootloader. I used both Refurbish and Partition DL on two separate attempts. Bootloader stayed unlocked throughout, and is still unlocked.
Had a devil of a time getting system to mount. Tried over and over again to get Magisk installed.
What finally worked was rebooting into recovery after pushing the .magisk file, and only then installing Magisk.
[NG]Owner
Click to expand...
Click to collapse
Well, this happened to me once again. I saw no reason why it should not do so. So I have been re-introducing apps from my TiBackup slowly and in under a strict protocol in an effort to (a) limit the damage done to my work and (b) try to isolate the culprit(s). I decided, since I found that I could restore TWRP backups of /data after re-doing the most of the TWRP install and defeat encryption process, that I would install apps slowly and execute them and in small groups. After each group I would do a reboot to see if that worked. If that worked, I would go into TWRP, run a backup, and name the backup of /data with something to id the app group that was added and seemed fine.
I started working backwards by the first letter of the app name. I first did U-Z and found that worked fine. Took a backup and went on to S-T. After this group it was bootloop time! So I put humpty-dumpty back together, restored the /data backup from U-Z, and this time installed only those apps starting with T. After this a no-problem reboot and a backup of /data and I will continue to plod on with those apps starting with S (and so on).
Horribly tedious. I can see no other way to proceed unless someone has a better idea.
PS - So I re-installed apps starting with S and basically had no problems. Hmmm. But I do recall that when testing execution of some of these apps the first time around, I decided to install busybox (Stericson), AdAway, and Afwall+ out of sequence. Before I did this I decided to check a bit more. I found that there is a Magisk busybox module and even though I have always used Stericson without troubles, I thought it best to use the Magisk module for this. I also found that Magisk has a setting for systemless hosts which could be affected by AdAway. So I enabled that before doing anything with AdAway. I also checked to see if AfWall+ might have any issues and found none. So I guess it is possible that using Stericson busybox or failing to use systemless hosts could have been an issue. I may never know for sure but at least so far I am fine after installing apps that I previously installed and had a bootloop. So FYI.

Alright, I'm a total idiot. I went and did this again, following the mantra: If it aint broke, you're not trying hard enough.
Setting all that aside, I went and tried to do some more debloating of my v40 (used this guide, that I was linked to from here), and wound up in "this fresh hell" again. Dammit! Crap.
So apparently there is a system application that is crucial to the boot of the phone that I uninstalled.
There is a fix to this, but it comes at a cost. Get into TWRP. Navigate to advanced, select Fix Recovery Reboot. Your phone will boot normally now. But you will lose root. And (so far) any attempt to reinstall Magisk to re-obtain root will result in the same bootloop again.
So here's where I need some help:
1) So if I wanted to reinstall my system partition to get back to stock from a KDZ, but still keep my installed apps, etc., how do I do that?
2) How do I get my Slot B to work correctly? It has only bootlooped there. Since I got my phone. Once I get my phone back to operational state with root, how do I make sure that Slot B works (so I have a backup I can fall back on if (when) I bork something else?
[NG]Owner