Database Info

[Q] root for 4.1.1 on Nexus S without data loss

Hello,
I want to get root on my current stock android 4.1.1 on my Nexus S without data loss to backup the wifi settings.
I could only find this exploit for 4.1.1, which doesn't work for me: http://forum.xda-developers.com/showthread.php?t=1886460
Can anybody help me by pointing out a current exploit for stock 4.1.1 on Nexus S?

I've unlocked the bootloader now and stored the wifi settings on google servers, which worked, but it also restored some other things I wanted to get rid off. Now I would like to become root on my device with the current stock system to save only the wifi settings (e.g. with titanium backup) and install cm 10 later.

Now I've flashed clockworkMod Recovery v6.0.1.0 on my device as described in cyanogen wiki. I've found this guide for rooting the stock system with a custom recovery. Is this a good idea or is there something better?

white-gecko said:
Now I've flashed clockworkMod Recovery v6.0.1.0 on my device as described in cyanogen wiki. I've found this guide for rooting the stock system with a custom recovery. Is this a good idea or is there something better?
Click to expand...
Click to collapse
No it's a good idea, this guide was created not long ago so things haven't really changed since then.

Thank you. I rooted the device according to these instructions, installed a wifi backup tool from market and did a backup of only the wifi settings. Now I'm running CM 10.0 and I will reapply the wifi settings with this app.
Thank you
(I think this thread can be closed now, but I don't know how)

white-gecko said:
Thank you. I rooted the device according to these instructions, installed a wifi backup tool from market and did a backup of only the wifi settings. Now I'm running CM 10.0 and I will reapply the wifi settings with this app.
Thank you
(I think this thread can be closed now, but I don't know how)
Click to expand...
Click to collapse
Leave it to die a peaceful death, and good job rooting your Nexus S. Enjoy it!

[Completed] Making an unrooted Nandroid on xt907

I have a stock unrooted Motorola Droid Razr M xt907
4.4.2 OTA OS, but I DID remove a few stock items.
Sys Ver: 182.46.15.XT907.Verison.en.US
Kernel is: July 29 2014
I have never owned or worked with a smartphone before, but have OC exp dating back to MS Dos 1.x-2.1 and have some Linux exp using OpenSuse
If I understand correctly I need to back upi the system files BEFORE ROOTING the device to protect myself in the event I go to far while rooted and bootloop or brick the device.
I am trying to understand how to create a Nandroid backup without rooting, but I'm not understanding quite enough to have any great success.
I''d rather not wipe all the installed apps, but if I need to I'd like to know if I can
- back up apps and settings using a utility that does not require root access
- do a reset
- then back up the virgin unrooted 4.4.2 system files
- Then root
- Then install CM11 (KitKat 4.4.4 based)
- The restore the apps and settings fromt eh (non Nandroid) backup I need to do a real OTA reset because I killed some of the stock apps already. (At least, that's my understanding)
I really appreciate you all being here to help folks! Many thanks in advance!

XDA Visitor said:
I have a stock unrooted Motorola Droid Razr M xt907
4.4.2 OTA OS, but I DID remove a few stock items.
Sys Ver: 182.46.15.XT907.Verison.en.US
Kernel is: July 29 2014
I have never owned or worked with a smartphone before, but have OC exp dating back to MS Dos 1.x-2.1 and have some Linux exp using OpenSuse
If I understand correctly I need to back upi the system files BEFORE ROOTING the device to protect myself in the event I go to far while rooted and bootloop or brick the device.
I am trying to understand how to create a Nandroid backup without rooting, but I'm not understanding quite enough to have any great success.
I''d rather not wipe all the installed apps, but if I need to I'd like to know if I can
- back up apps and settings using a utility that does not require root access
- do a reset
- then back up the virgin unrooted 4.4.2 system files
- Then root
- Then install CM11 (KitKat 4.4.4 based)
- The restore the apps and settings fromt eh (non Nandroid) backup I need to do a real OTA reset because I killed some of the stock apps already. (At least, that's my understanding)
I really appreciate you all being here to help folks! Many thanks in advance!
Click to expand...
Click to collapse
Unlock your bootloader.
Flash the latest TWRP recovery in fastboot.
Make a backup with TWRP.
THEN flash SuperSU to gain root using the TWRP Recovery.
It's actually a great idea to hold onto a non-rooted backup, in case you want to return to stock one day to get an OTA update.

Okay, in looking for directions to unlock the bootloader, I'm jsut finding a lot of hits that begin y saying the phone needs to be rooted first, so I could use a push in the right direction there.

The forum linked here:
http://forum.xda-developers.com/showthread.php?t=2226729
should give you all of the info that you need.

xunholyx said:
The forum linked here:
http://forum.xda-developers.com/showthread.php?t=2226729
should give you all of the info that you need.
Click to expand...
Click to collapse
I'm so confused. The first instruction in the first post is to root the phone, but then how can I get an unrooted Nandroid backup?
I believe the answer I need may be covered here, but I'm not sure I follow how to flash this properly BEFORE rooting the phone. I intend to make a walkthrough on another forum once I get this all sorted, and would be happy to plug XDAD and you for the help.
There is a broken link in the guide you linked me to. I just wanted to make you aware. I have the motorola driver loaded on my Win 7 Ultimate Retail 64 bit driven PC, so I'm good, but the link for the drivers is returning a 404

I'm the one who is confused.
Sorry, I should have read the OP in that link better.
You can backup all of your data using ADB: adb backup -apk -shared -all -f C:\Users\NAME\backup.ab
And restore it using this command: adb restore C:\Users\NAME\backup.ab
Replace "NAME" with your Windows username of course.
There is a more comprehensive guide here.
Read the OP, then go to the last 10pgs or so to see if there is new info (didn't read that far, but the thread is still active).

Okay, I suspect this last link is probably more what I'm after, but before I do that, I'm HOPING it is possible to back up the installed apps and their respective settings first. The reason for this is that I really do want a squeaky clean, uprooted Nandroid backup of the last OTA update supported which, (no surprise), is 4.4.2, which includes the handy Heartbleed bug "feature" and makes the Razr M all but useless.
Of course, as we know, 4.4.4 runs very well on the Razr M and the Heartbleed bug is easily solved by it, but Motorola prefers you buy a new phone, so they introduce a bug, load it on everyone's 1-1/2 year old devices, and they refused to fix it by not allowing users access to the "new" unbroken OLD KitKat platform! You can only run that LAST version of the OLD KitKat on NEW HARDWARE!
The other tactic used on consumers by Motorola and others is not allowing customers to purchase new factory fresh batteries for their devices, whether "non-replaceable" or not. These are two strong-arm tactics adopted that now dominate cellular and other technologies.
I digress.
I am going to HAVE to restore this phone before making the Nandroid because I pulled some stock 4.4.2 Motorola firmware bloat out of it, adn now I need iot back for that backup to be truly virgin. :/
Soooooooo . . . .
The first order of business is to determine if I can add the stock stuff back, or if I have to actually do a reset on the phone. I fear adding the stock items back MAY still leave changes in the system folder, which is not acceptable to me. *IF* I CAN successfully add the stock bloat back in and get a clean Nandroid, I'd be happy about that, though I'd be concerned about it working properly none-the less.
This is why I ask if I can back up apps and app data and later successfully restore that stuff that was backed up under 4.4.2 once I have successfully loaded the (KitKat 4.4.4 based) CM11 Mod.
If the backup of apps and app settings WILL restore to 4.4.4, I'd like to:
- > back up all apps, app data adn user data > reset the phone loading the 4.4.2 OTA BONE STOCK > make my Nandroid of the bone stock unrooted 4.4.2 > Root > Load CM11 MOD ROM > Restore my apps and user data.
I will work on learning to make the unrooted Nandroid some while I wait for a reply, as I'm going to have to do that as a later step.
Giving this a try. I'm about to crash. I'm pretty zonked out.

If all that you want is to save apps and app data, and not system and boot partitions, then use the ADB commands that I posted. That will do exactly what you want.

Oh no no, that's not all I want to do by any means. I am going to load the KitKat 4.4.4 based CM11 ROM, but before I do that I want a clean OTA backup of the stock unrooted KitKat 4.4.2 so I have that to fall back on.
To that end, in preparation for the new ROM I'd like to back up all apps that are currently loaded along with the current app data, and also to back up all personal data.
Once that is done, I need to do a reset to get 4.4.2 back into it;s stock trim as this will be my original 4.4.2 OTA Nandroid.
THEN I will root and install CM11
Then, if it's possible, I'd like to restore all of my current apps and app data.
I've been working on understanding the steps needed to make that unrooted 4.4.2 Nandroid while awaiting suggestions about how to do the app/app data and personal data backup., as well as a yea or neigh about if the app backup can even be successfully restored under the new (4.44 based) os.

Completely Eliminated Static Boot on Rooted V20 with My Stock Kernel!!!

Alright guys, so this happened 100% ON ACCIDENT but it actually worked! I wanted to let you guys know because maybe it will help some of the devs figure out how to eliminate the static boot for good.
I have the H910 ATT V20. I initially rooted it using Dirty Santa but, at the time, nobody had made a custom ROM for the ATT variant yet. I flashed the Konverged Kernel and from then on, I had the dreaded static screen on boot. @Tilde88 was extremely generous in offering to make a custom ROM if I provided some files for him and he made the first excellent NotSoStock ROM for the ATT V20. However, I had some issues installing it on the first try. When I tried to flash his ROM, TWRP gave me an error telling me I had a US996. I patched the zip with a file from Tilde88 and it worked like magic!
Since then, there has been a lot of progress in ROMs and kernels for all the variants. For the sake of experimentation, I have tried different ROMs and kernels to see how they affect the phone. Since my phone is registering as a US996, I flashed that variant of the NotSoStock ROM. The Werewolf Kernel from @USA-RedDragon is the only one I know of so far that does not have the static on boot. I have been flashing Werewolf and Konverged along with different ROMs to see the difference in performance and battery.
The ROM I am on right now is Extreme Syndicate from @elliwigy. Since it is based off of the stock deodexed US996 firmware, I thought it sounded great to try since it has NONE of the bloat from any of the various carriers. I read in a post by @AlkaliV2 here about flashing the stock kernel located on my computer from the original Dirty Santa root method:
https://forum.xda-developers.com/v2...-nrd90m-modded-notsostock-rom-t3525344/page21
That gave me an idea to download and flash the stock unlocked US996 kernel since Extreme Syndicate is based off of that. I had Konverged Kernel at the time. I flashed the US996 kernel, but forgot to flash SuperSU before boot... Woops lol. So I went back to TWRP and formatted my phone to start from a fresh flash, but realized I also deleted my ROM backup when I formatted my phone. So I decided to install a ROM and kernel fresh.
HERE IS HOW I FIXED THE STATIC BOOT
After formatting my phone, I flashed the Extreme Syndicate ROM with the Werewolf Kernel. I chose this kernel so there would not be any static on boot.
Then
I booted back to TWRP, made a backup just in case, and flashed my stock H910 ATT kernel from the file named bootbackup.img. After that, I flashed SuperSU, wiped Cache and Dalvik, rebooted... and BAM, just like that, no static! It says under software information that I am on kernel version 3.18.31. 3C Toolbox shows the kernel as Linux 3.18.31g12e8957
It is still fresh so I have to see how it goes with battery and performance. Initially, it was noticeably slower. I completely fixed this by:
1. Implementing all options under "One Click -> Performance Optimizations" in the app 3C Toolbox
2. Selecting "Performance" under Profiles in the app L Speed
I just wanted to share this with everyone to put this info out there. I have not seen a fix for the static boot yet and though that this might be useful info for someone out there! I hope this helps!

Yes, there is an updated driver branch using CAF sources that fixes static boot. I'm far too busy in life to get anything done, and before anything else, I have to get v6.0 for the H918 going. Once that is up (using the latest build and soruces from LG), I can move forward for 6.0 for the other devices.

nikktrikk said:
I just wanted to share this with everyone to put this info out there. I have not seen a fix for the static boot yet and though that this might be useful info for someone out there! I hope this helps!
Click to expand...
Click to collapse
This is an interesting approach, I'm not entirely sure why it would work but I'm willing to give it a shot. I'm not entirely convinced that you are running the stock AT&T kernel though since you are seeing performance loss and no static on boot. I don't have a normal method for ensuring that you have the stock kernel (like Wi-Fi calling being enabled) but I do have one way you could check. Use any terminal emulator (no root/su needed) and pass the command
Code:
uname -r
and let me know the output.
I have the stock AT&T kernel installed with everything working aside from static boot and mine reads:
Code:
3.18.31-perf-ge3230fb

AlkaliV2 said:
This is an interesting approach, I'm not entirely sure why it would work but I'm willing to give it a shot. I'm not entirely convinced that you are running the stock AT&T kernel though since you are seeing performance loss and no static on boot. I don't have a normal method for ensuring that you have the stock kernel (like Wi-Fi calling being enabled) but I do have one way you could check. Use any terminal emulator (no root/su needed) and pass the command
Code:
uname -r
and let me know the output.
I have the stock AT&T kernel installed with everything working aside from static boot and mine reads:
Code:
3.18.31-perf-ge3230fb
Click to expand...
Click to collapse
Hmmm interesting. Mine returned with:
Code:
3.18.31-g12e8957
[/QUOTE]
Do you have any idea why that might have happened? I used the file directly from the Dirty Santa folder, but maybe there is an issue since I flashed it over the previous kernel.

AlkaliV2 said:
This is an interesting approach, I'm not entirely sure why it would work but I'm willing to give it a shot. I'm not entirely convinced that you are running the stock AT&T kernel though since you are seeing performance loss and no static on boot. I don't have a normal method for ensuring that you have the stock kernel (like Wi-Fi calling being enabled) but I do have one way you could check. Use any terminal emulator (no root/su needed) and pass the command
Code:
uname -r
and let me know the output.
I have the stock AT&T kernel installed with everything working aside from static boot and mine reads:
Code:
3.18.31-perf-ge3230fb
Click to expand...
Click to collapse
Also, I think it is an issue with my phone registering as a LG-US996. None of the ATT ROMs will flash onto it and I don't know how to convert it back to register as an H910. It seems like that is one of the primary reasons that the kernel I used from my computer may be having issues. Do you know how I can revert my phone? Nemisisg4 mentioned that when he tried to reflash the NotSoStockRom, it said no OS was installed. I also got that error numerous times when messing with different setups and it caused me to have to flash things all over again. I could not restore my saved backups of the 5.5 either after wiping the ROM I think because, since the ROM needed to go from the 5.1 to the 5.5, when I backed-up the 5.5, there was a conflict during the restore process.

nikktrikk said:
Also, I think it is an issue with my phone registering as a LG-US996. None of the ATT ROMs will flash onto it and I don't know how to convert it back to register as an H910. It seems like that is one of the primary reasons that the kernel I used from my computer may be having issues. Do you know how I can revert my phone? Nemisisg4 mentioned that when he tried to reflash the NotSoStockRom, it said no OS was installed. I also got that error numerous times when messing with different setups and it caused me to have to flash things all over again. I could not restore my saved backups of the 5.5 either after wiping the ROM I think because, since the ROM needed to go from the 5.1 to the 5.5, when I backed-up the 5.5, there was a conflict during the restore process.
Click to expand...
Click to collapse
Alright, I was out for a little but I'm back now and I have a suggestion. I'm going to write up a short how-to but go here: https://forum.xda-developers.com/v20/how-to/stock-att-h910-stock-recovery-boot-image-t3528060
You are not going to follow that guide directly as I need to update it to include the actual stock kernel bootbackup.img but the backup files need to be placed in TWRP for the Restore function to work.
So to modify the steps a bit for your usage:
!) You need SuperSU 2.79 stable and your bootbackup.img file saved to your microSD card
1.) Put the files in the TWRP > Backups folder (preferably on your microSD card because we are formatting your entire data and internal storage) *
2.) You are going to go to advanced wipe and wipe everything except microSD and USB-OTG
3.) Go back and choose Format Data from the wipe screen and swipe to wipe data again just to be sure
4.) Reboot to recovery
5.) Now we want to restore the system image you have saved to your MicroSD card. Hit the restore menu, make sure the system checkbox is checked only, and slide to start
6.) Once finished head back to the main menu and choose Install > Install image and choose your bootbackup.img file
7.) Once done immediately flash SuperSU 2.79 stable
8.) Power off the device from the menu leave it be for about 30 seconds then turn it back on and let it boot.
It SHOULD work. Let me know if it doesn't and I wish you luck. Also, avoid US996 ROMs for the time being. I am getting the H910 image out to devs as quickly as I can and it has files that are pretty important to the hardware in our phone. If you get this to boot just use TiBu to remove things you don't want and always keep a copy of this backup ROM on your drive.
*If you do not have a microSD card to put these files on you can do a full wipe like I mention above, but you'll have to fully wipe it as I have instructed, reboot recovery to TWRP, hook the phone up to the PC at that point and copy the files you need over to it at that point.

AlkaliV2 said:
Alright, I was out for a little but I'm back now and I have a suggestion. I'm going to write up a short how-to but go here: https://forum.xda-developers.com/v20/how-to/stock-att-h910-stock-recovery-boot-image-t3528060
You are not going to follow that guide directly as I need to update it to include the actual stock kernel bootbackup.img but the backup files need to be placed in TWRP for the Restore function to work.
So to modify the steps a bit for your usage:
!) You need SuperSU 2.79 stable and your bootbackup.img file saved to your microSD card
1.) Put the files in the TWRP > Backups folder (preferably on your microSD card because we are formatting your entire data and internal storage) *
2.) You are going to go to advanced wipe and wipe everything except microSD and USB-OTG
3.) Go back and choose Format Data from the wipe screen and swipe to wipe data again just to be sure
4.) Reboot to recovery
5.) Now we want to restore the system image you have saved to your MicroSD card. Hit the restore menu, make sure the system checkbox is checked only, and slide to start
6.) Once finished head back to the main menu and choose Install > Install image and choose your bootbackup.img file
7.) Once done immediately flash SuperSU 2.79 stable
8.) Power off the device from the menu leave it be for about 30 seconds then turn it back on and let it boot.
It SHOULD work. Let me know if it doesn't and I wish you luck. Also, avoid US996 ROMs for the time being. I am getting the H910 image out to devs as quickly as I can and it has files that are pretty important to the hardware in our phone. If you get this to boot just use TiBu to remove things you don't want and always keep a copy of this backup ROM on your drive.
*If you do not have a microSD card to put these files on you can do a full wipe like I mention above, but you'll have to fully wipe it as I have instructed, reboot recovery to TWRP, hook the phone up to the PC at that point and copy the files you need over to it at that point.
Click to expand...
Click to collapse
Wow, thank you for such a detailed post! So just to clarify, after flashing the bootbackup.img that includes the stock kernel AND the stock ROM? And this is basically unrooting my phone and putting it back to stock, so I would need to go through this process, then re-root?
Before you responded, I managed to flash the stock US996 kernel to my phone with the extreme syndicate ROM. So far it is lightning fast, the battery seems good. Usage so far is about 7 hours with an estimated time remaining of 35h 27 min. I know you said to avoid the US996 ROMs, do you think it is worth it to go back to stock if I am getting those stats as of right now, will the battery life and speed be comparable? Isn't the hardware the same, just each phone has it's own OS, hence why my phone functions on the US996 after the conversion happened? I have no idea about this so I am just throwing that out there to ask!
Thanks again for your help!

nikktrikk said:
Wow, thank you for such a detailed post! So just to clarify, after flashing the bootbackup.img that includes the stock kernel AND the stock ROM? And this is basically unrooting my phone and putting it back to stock, so I would need to go through this process, then re-root?
Before you responded, I managed to flash the stock US996 kernel to my phone with the extreme syndicate ROM. So far it is lightning fast, the battery seems good. Usage so far is about 7 hours with an estimated time remaining of 35h 27 min. I know you said to avoid the US996 ROMs, do you think it is worth it to go back to stock if I am getting those stats as of right now, will the battery life and speed be comparable? Isn't the hardware the same, just each phone has it's own OS, hence why my phone functions on the US996 after the conversion happened? I have no idea about this so I am just throwing that out there to ask!
Thanks again for your help!
Click to expand...
Click to collapse
I can't even begin to tell you what the right thing to do here is. I can only say what my experience was having my device run as a US996. Broken comfort view, no wifi-calling, FM radio not working (variant kernel related), and issues with battery drain. But that was my experience. If you are having good results running 996 then don't feel obligated to change. My post was just to get your phone back to being recognized as a H910. Now to answer your original question:
The files I linked to above in the guide are for the H910 system, recovery, and boot image made immediately after I got dirty cow working. The kernel in that backup set is the US996 kernel, not the one you need to go back to full rooted stock. The restore method I mention does not remove root or break TWRP it just puts back the stock ROM in full and then you flash bootbackup.img along with SuperSu to keep root and boot the stock kernel. It is the config I am running right now because it gets me all the features working aside from the static boot. So you only need to follow my guide if you can't get back to stock H910 rooted.
Edit: let me be clear in case it wasn't before. If you decide to use my backup files: do NOT use the boot or recovery image from those restore files. Use just the system restore image and your own personal bootbackup.img kernel along with SuperSu 2.79 stable.

AlkaliV2 said:
I can't even begin to tell you what the right thing to do here is. I can only say what my experience was having my device run as a US996. Broken comfort view, no wifi-calling, FM radio not working (variant kernel related), and issues with battery drain. But that was my experience. If you are having good results running 996 then don't feel obligated to change. My post was just to get your phone back to being recognized as a H910. Now to answer your original question:
The files I linked to above in the guide are for the H910 system, recovery, and boot image made immediately after I got dirty cow working. The kernel in that backup set is the US996 kernel, not the one you need to go back to full rooted stock. The restore method I mention does not remove root or break TWRP it just puts back the stock ROM in full and then you flash bootbackup.img along with SuperSu to keep root and boot the stock kernel. It is the config I am running right now because it gets me all the features working aside from the static boot. So you only need to follow my guide if you can't get back to stock H910 rooted.
Edit: let me be clear in case it wasn't before. If you decide to use my backup files: do NOT use the boot or recovery image from those restore files. Use just the system restore image and your own personal bootbackup.img kernel along with SuperSu 2.79 stable.
Click to expand...
Click to collapse
Definitely makes sense. Yeah I have been having issues with battery drain and all that, as well. This is the very first time since I have been having issues with the US996/H910 conversion and incompatibility that I have actually got it to be stable. I also didn't like not having comfort view, and this actually fixed it! Comfort view now works on my phone, it didn't work earlier today before this most recent flash. I think that I will just give it some time before I make a decision and see how the battery fares. You have been a HUGE help, I really appreciate you taking the time to explain the process to restore my phone. I do want to do it, but being that it currently seems to be doing a lot better than before, I'll wait before making the leap back to stock just for comparison.

Help me
I also have h910 model but when i tried to boot after dirtysanta 3 rd step it didnt boot into twrp..even though i tried to flash recovery with fastboot flash recovery command.
I m stuck and static screen is a mess..plz help me

Hi, I'm a bit of a novice at this, can you please explain this line:
"flashed my stock H910 ATT kernel from the file named bootbackup.img"
Where do I get this file, and how do I flash it?

titmus said:
Hi, I'm a bit of a novice at this, can you please explain this line:
"flashed my stock H910 ATT kernel from the file named bootbackup.img"
Where do I get this file, and how do I flash it?
Click to expand...
Click to collapse
you where supposed to back up your original filesystem you would have gotten it from there.

D801 TWRP Issue - Bottom portion of touch screen doesn't respond

tl;dr - TWRP touch screen won't work after installing custom ROM, much hassle to unbrick, looking for a "bumped" (still not actually sure what that term means) or otherwise modified version of TWRP that won't go haywire when installing a custom ROM.
tl;dr 2 - Also interested in the LATEST "stock-based" ROM recommendations anyone may have... G3 backports or whatever. She needs her Camera to work well but older 4.4.x and 5.0.x OS is missing a lot of new functionality and compatibility with new apps.
I'll just start out by saying that I've figured out just about every way to brick and subsequently un-brick this device that is feasibly possible, and am considering starting a thread specific to those various methods... but that's not what this is for.
This is an issue I've encountered a few times now, definitely on my girlfriend's T-Mobile LG G2 D801 with Lollipop (30B and now again on D801 30C), and iirc, also on KitKat.
I'll explain what I can remember, most of this has been done in the middle of the night after many frustrating hours of attempting various methods... I have to say, this phone has been much more difficult to mod compared to my previous experiences with Samsung and Nexus devices.
I had gotten this device all the way through to CM12 or 13 a year or so ago but recent issues made us decide to attempt to revert back to a Stock-based ROM.
Steps:
1. Root (ioroot / Autorec, can't remember which or for what reason, I have multiple versions of each)
2. Install TWRP Custom Recovery (most recently and successfully using a modified version of the "30B Freedom Tool", although I haven't tried that on 30C - yet.
3. Transfer custom ROM & Kernel to SDCard.
4. Boot into TWRP and install custom ROM & Kernel - most recently GoogleEdition 1.5 and then DorimanX 12.0 Kernel
5. Clear Cache / DALVIK Cache.
6. Reboot device. This is where the trouble begins...
Results: Won't boot into OS at all, instead I end up at the text-based "fastboot" screen, which after multiple tries I can eventually get back into TWRP or into Download Mode.
Once in TWRP after installing custom ROM, the bottom ~1" of the screen won't respond and all other touches aren't accurate... playing with it, I can usually eventually get into some of the TWRP screens, but for most purposes it's about useless.
I managed to restore a backup of the original 30B system image via command line over MTP using ADP TWRP commands, but that bricked the phone in an entirely separate manner where I couldn't access Recovery anymore and the system wouldn't boot at all... I ended up using the LG Update tool to get it up to 30C, and was surprised to find that it still had the restored backup data (apps, pictures, settings, etc), and the phone is now working again, albeit back to stock recovery.
Now, as I mentioned, this isn't the first time I've run into this "phantom touch" issue in TWRP on this device, although the circumstances seem to be a little backwards this time vs when I was taking the device over to CM12/13. I think I remember something about a "bumped" or otherwise modified version of TWRP being out there, but I can't find it now or put my finger on what the changes were.
Has anyone else run into this? I am hoping I've just overlooked something, but days of digging through threads hasn't turned up much.
/edit/ To give you an idea, attached is the folder I've got files stored in... with tons more in Archive and Stock-Based... I've used them ALL at some point. I'd like to get enough info in here to write a Step by Step guide for new owners who are picking these devices up on the cheap, and would appreciate if anyone wants to help out with this!

Leagoo Shark 1 - SafetyNet Issues.

I've basically been trying to root this phone for over a week now - first of all I had problems with the ADB drivers and such, but now I can actually flash stuff onto the phone.
I then also managed to flash SuperSU and XPosed and now herein lies the problem. I want to play PokémonGO.
Now, after doing a lot of reading up on the subject, it seems P-GO now uses Google's SafetyNet API in order to block Root, Xposed, etc users from playing the game.
So, I did a complete reset and tried flashing a different rom. I used the ''Stock Android 6.0 ROM'' from this thread: https://forum.xda-developers.com/android/general/leagoo-shark-1-development-support-t3415599
HOWEVER, flashing that ROM seems to wipe the recovery partition (even if you untick recovery in sp flash tool) and you end up with some chinese 4G logo banner, before it boots into the OS.
So, back to square 1. I found and re-flashed the stock Leagoo OS ROM and then tried using Magisk (because supposedly Magisk can hide itself and allow me to play P-GO).
No digs...
So, after many hours of flashing many different ROMs, performing countless resets and wipes on my phone, I think I may have found the issue.
After reading through the support forum of Magisk, it was recommended trying to go back to 0 (un-rooting, re-wiping partitions, re-flashing stock rom, etc) and seeing if my phone would then pass SafetyNet Check - It doesn't.
Purely stock ROM, does not pass SafetyNET, which I reckon is because the phone's bootloader is unlocked from the get-go.
Now, weirdly, the stock rom CAN play PokémonGo without a hitch, but installing root then mucks it up.
Seeing as Leagoo isn't exactly a common brand, I cannot install LineageOS with it's custom kernel which hides the bootloader settings....
what can I do if I want to have a rooted phone, but also want to play PokemonGo?