I installed Cyanogen Mod (cm-11-20140504-SNAPSHOT-M6-falcon.zip) on my 1st generation Moto G using TWRP. When I boot into CM, I keep getting the message that "Unfortunately, the process com.android.systemui has stopped". Every time I banish that popup, I get a split second of usage before it pops up again. After some troubleshooting and web searching, I found that I have to revert to CM 10. The details are documented at androidforums.com/threads/windows-mtb-usb-device-driver-error-when-moto-g-running-twrp.901001 and forum.xda-developers.com/chef-central/android/windows-mtb-usb-device-driver-error-t3022946
I haven't searched for CM 10 yet, but I'm scouting out the process to push it to the device. I can't find a way to get ADB to see the device, even after enable USB debugging (www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android and android.stackexchange.com/questions/67249/how-to-enter-usb-debugging-mode-in-cyanogenmod). Given that I only have a split second after banishing each error message, that took forever, but I confirmed that USB debugging is enabled after rebooting.
The only alternative I know to ADB is fastboot. According to forum.xda-developers.com/showthread.php?t=702069, it is theoretically possible for fastboot to flash a ROM, but the zip file should contain a data.img and system.img. I checked the CM 11 zip file to see what I can expect from CM 10, and found no such img files.
Given that ADB and fastboot processes don't work for me (at least the the degree that I've explored them), what other options are there for flashing CM 10?
P.S. Does anyone know how to get exit (say) Settings or the browser and get back to the cyanogenmod start page? There is no home button, and web searching refers an icon with 3 bars on the top, which I don't have. I basically have to reboot.
my1stSmartPhone said:
I installed Cyanogen Mod (cm-11-20140504-SNAPSHOT-M6-falcon.zip) on my 1st generation Moto G using TWRP. When I boot into CM, I keep getting the message that "Unfortunately, the process com.android.systemui has stopped". Every time I banish that popup, I get a split second of usage before it pops up again. After some troubleshooting and web searching, I found that I have to revert to CM 10. The details are documented at androidforums.com/threads/windows-mtb-usb-device-driver-error-when-moto-g-running-twrp.901001 and forum.xda-developers.com/chef-central/android/windows-mtb-usb-device-driver-error-t3022946
I haven't searched for CM 10 yet, but I'm scouting out the process to push it to the device. I can't find a way to get ADB to see the device, even after enable USB debugging (www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android and android.stackexchange.com/questions/67249/how-to-enter-usb-debugging-mode-in-cyanogenmod). Given that I only have a split second after banishing each error message, that took forever, but I confirmed that USB debugging is enabled after rebooting.
The only alternative I know to ADB is fastboot. According to forum.xda-developers.com/showthread.php?t=702069, it is theoretically possible for fastboot to flash a ROM, but the zip file should contain a data.img and system.img. I checked the CM 11 zip file to see what I can expect from CM 10, and found no such img files.
Given that ADB and fastboot processes don't work for me (at least the the degree that I've explored them), what other options are there for flashing CM 10?
P.S. Does anyone know how to get exit (say) Settings or the browser and get back to the cyanogenmod start page? There is no home button, and web searching refers an icon with 3 bars on the top, which I don't have. I basically have to reboot.
Click to expand...
Click to collapse
This is the wrong forum to post this in. Also, Snapshot M6 is almost a year old. Flash the latest nightly. That will work better. There's no CM10 for this device since it shipped with Android 4.3, so you'd be wasting your time looking for it. Even though systemui is crashing, mtp will still work, so you can transfer files to your phone normally. Also, this should teach you, that it is dangerous to experiment with your phone without a legitimate way out of issues or a backup.
As you able to flash a custom rom via custom recovery?
Press and hold power and volume down button together till 10 secs after your phone is turned off. You will go to bootloader menu. Connect it via USB to access fastboot.
@audit13: Re. whether I can flash via custom recovery, the short answer is no. I haven't been able to get CWM working, but with TWRP, I could flash CM 11 if I first push the zip file to /sdcard with the device booted up normally. TWRP has a problem with MTP drivers (seems endemic, from what I've been able to find online), and ADB on my laptop can't see the device when it is running TWRP. I've documented this in the 1st 2 links of paragraph 1 in my original post. Unfortunately, with CM 11 installed, the laptop can't see the device at all, so no push is possible. That is the reason why I was trying to find info on flashing via fastboot in my original post. Please note that I also haven't been able to get TWRP to sideload, probably due to the invisibility of the device to the laptop.
@i_rnb: I can get into bootloader OK, but my concern is how to use fastboot to flash an OS rather than a recover. According to forum.xda-developers.com/showthread.php?t=702069, it is theoretically possible for fastboot to flash a ROM, but the zip file should contain a data.img and system.img. I checked the CM 11 zip file to see what I can expect from CM 10, and found no such img files.
Did you try the latest Philz from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/falcon/
That's what I used on my xt1032 and it's fine for install ROMs via OTG and internal SD card.
Flashing via fastboot should work as long as you are able to boot into fastboot mode and the proper drivers are installed.
Stock ROMs with have the system.img or data.img files you need where as custom ROMs do not.
my1stSmartPhone said:
@audit13: Re. whether I can flash via custom recovery, the short answer is no. I haven't been able to get CWM working, but with TWRP, I could flash CM 11 if I first push the zip file to /sdcard with the device booted up normally. TWRP has a problem with MTP drivers (seems endemic, from what I've been able to find online), and ADB on my laptop can't see the device when it is running TWRP. I've documented this in the 1st 2 links of paragraph 1 in my original post. Unfortunately, with CM 11 installed, the laptop can't see the device at all, so no push is possible. That is the reason why I was trying to find info on flashing via fastboot in my original post. Please note that I also haven't been able to get TWRP to sideload, probably due to the invisibility of the device to the laptop.
@i_rnb: I can get into bootloader OK, but my concern is how to use fastboot to flash an OS rather than a recover. According to forum.xda-developers.com/showthread.php?t=702069, it is theoretically possible for fastboot to flash a ROM, but the zip file should contain a data.img and system.img. I checked the CM 11 zip file to see what I can expect from CM 10, and found no such img files.
Click to expand...
Click to collapse
I'm sorry, but you're misunderstanding/reading the wrong things. You WILL NEVER find CM10 for the Moto G because CM 10 simply never existed for this device. You need to look for issues which are device specific and not just general issues all over the internet. Also, you WILL NEVER find a system.img and data.img in a CM11 zip. Those are only found in the stock ROM meant specifically for flashing via fastboot. All that information can be found by looking around the Moto G XDA forums itself. You'll find a lot of helpful stuff in the General section. You can also push a zip to /sdcard. You need to boot into bootloader and then push via ADB. MTP works on the latest TWRP recovery. So you can transfer it to your phone that way too.
audit13 said:
Did you try the latest Philz from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/falcon/
That's what I used on my xt1032 and it's fine for install ROMs via OTG and internal SD card.
Flashing via fastboot should work as long as you are able to boot into fastboot mode and the proper drivers are installed.
Stock ROMs with have the system.img or data.img files you need where as custom ROMs do not.
Click to expand...
Click to collapse
I need to become familiar with Philz. Being a newcomer to smartphones, it's not familiar to me. One of the fundamental requirements that I established at the outset of my search for a smartphone was to have the provider of the OS & phone be trustworthy or, failing that, go to open source so that it has the eyes of the world on it. It is also why I seek to be familiar with the source of ROMs, tools, etc. So far, I tried to download to from main sites for CWM, TWRP, and CM 11.
I know, it sounds odd these days, but I'm spoiled from before the internet days, when you can store any personal info you want on electronic organizers that had no connection, wired or wireless, to computers or the internet (which didn't exist). These days, it seems that you have to be very careful if you wish store any personal info on these personal devices. Either that, or carry a paper organizer around for the personal stuff (and I don't want to do that).
Thanks for confirming flashability via fastboot even without system.img and data.img. As it turns out, however, it isn't as promising a way ahead for me because I found out that the reversion back to CM 10 was a mistake (www.reddit.com/r/cyanogenmod/comments/2gvmqu/cm11moto_g_comandroidsystemui_is_crashing_after). The OP meant M10 snapshot, not CM 10. Which is odd, since the Moto G has no M10 snapshot (download.cyanogenmod.org/?type=snapshot&device=falcon). There's no M10 in the names of the nightly snapshots either (though that's less of a concern for me as I don't want to wander into nightly territory until I get the confidence of having my first attempt working).
I'll mull over Philz after some web search. I also distinctly recall backing up the stock Carrier ROM, so perhaps another way out is to find it and go through the details of restoring it.
my1stSmartPhone said:
@i_rnb: I can get into bootloader OK, but my concern is how to use fastboot to flash an OS rather than a recover. According to forum.xda-developers.com/showthread.php?t=702069, it is theoretically possible for fastboot to flash a ROM, but the zip file should contain a data.img and system.img. I checked the CM 11 zip file to see what I can expect from CM 10, and found no such img files.
Click to expand...
Click to collapse
1. Boot into Fastboot.
2. Flash TWRP recovery via Fastboot.
3.. Select Recovery from the menu and boot to TWRP recovery.
4. Put the ROM zip in a USB OTG drive.
5. Connect it to your device and mount it from recovery menu.
6. Install the zip via TWRP recovery from USB OTG.
DONE !
This is very odd.
I could not restore from my pre-CyanogenMod backups because when I browse to the date+time-stamped folders, it was empty. However, I had previously copied to contents of at least one date+time-stamped folder to my laptop.
I used fastboot to uprade TWRP from 2.8.3 to 2.8.4 in hopes of getting past the MTP driver problem, which would enable me to copy the files back to the device. Halleluya, it did allow the device to be seen in Windows Explorer. But I didn't need to use the copy on the laptop because moving to 2.8.4 also allowed the backups to be seen on the device.
I gleefully restored the backup. It said "failed", but I rebooted anyway. Unfortunately, the failed restoration was real, and I was still with CyanogenMod. I interrupted the boot process to get back to bootloader.
I reverted back to TWRP 2.8.3, hoping that it would still see the backup. I was hoping that 2.8.3 would properly restore the backup because it was created using 2.8.3. It did indeed see the backup, but the restoration still resulted in "failed", and a reboot still led to the CyanogenMod bootup.
Oddly, CyanogenMod booted properly this time without the repeated systemui popups. It's great! Though I wonder if I somehow affected CyanogenMod with the failed attempts at restoring the stock carrier's ROM. Not that I care right now. CyanogenMod awaits exploration.
But there are a couple of things that I hope someone can comment on. What might cause CyanogenMod to boot properly after upgrading TWRP and reverting back, failing to restore the stock carrier ROM with both versions? Could CyanogenMod now be corrupt? And why won't my backups restore? How can I ensure that I create good backups?
P.S. Thanks to i_rnb for the tip about USB OTG. I did not go that route because I only have the cable that came with the device.
P.P.S. I'm a bit (or rather, quite) unsettled by the randomness with which things work...
I downloaded the CyanogenMod nightly for Moto G, cm-12-20150213-NIGHTLY-falcon.zip. I got it working. Pretty robust so far, so I want to enjoy it a bit before clobbering it by attempting to restore the Carrier stock ROM. I admit that I will have to do that at some point because I need to ensure that my backups are good.
I would like to take this opportunity to recount how I got around the problems I faced. I think that others may run into this, and my story may help them get back to a working phone when it looks like it is bricked.
The problem was that CM 11 was crippled by the repeated systemui popup messages. I thought it went away, but it came back. I still don't know what triggers it. And my backups of the carrier OS either failed to restore (twrp 2.8.3) or were not visible (twrp 2.8.4). I had spent so many days trying to think of a way ahead that simply didn't care about bricking the phone anymore. After all, it wasn't doing a whole lot of good as-is. So in one of my attempts of trying something, I erased the OS in the process of re-installing CM 11. And the re-install failed. Not a good situation, since ADB worked only when an OS was running (not when a recovery was running), and the MTP driver errors prevented the device from being accessed from windows when recovery was running. It didn't matter whether I was running twrp 2.8.3, 2.8.4, or CWM. So sideload didn't work in any of those recoveries.
There was basically no way to push *any* new OS to the phone. I forgot the details, but the CM 11 imag file that was on the phone might not have been visible to the one or more of the recoveries I tried. I was so out of options that I even tried fastboot to flash to OS, and that did not succeed.
Here is what I found worked. I don't know what particular detail was responsible for the success, so it requires experimentation.
First, I un-installed re-installed the SDK tool set for installing custom ROMs, making sure that I included Google USB drivers. The subsequent update required many more things to be installed, so that might have been part of the solution. I then looked for Motorola driver apps in Windows's Programs menu, uninstalled both, and re-installed. I don't know what contribution it had to the success, as I never got the Device Manager running. Whenever I launched it, it searched for updates, came back and reported no updates and that my device was uknown, then quit. Maybe because no OS on the device was running.
The one thing that seemed to help was that, even though the device was otherwise incommunicato from the laptop, I was able to fastboot flash recoveries. After the above re-installs, a re-install of twrp 2.8.4 allowed the computer to see the device in Windows Explorer. I believe it had something to do with better-functioning MTP USB drivers in the re-install, but I can't be sure. So I was able to copy the nightly CM 12 to the device, then use one of the recoveries to install it.
But the story didn't end there. Even after the CM install, I was still getting repeated popups. This time, however, it was something other than systemui, but otherwise, the symptoms were the same. At that point, I had pretty well concluded that my experiment with Moto G was at its end, and that I would look at Blackberry (now that they committed to stay in the handset market). But I did half-heartedly experiment a bit more. Good thing, too, because the 2nd attempt at re-installing CM 12 seems to have worked. No repeated popups so far. What I made sure that I did was to wipe out anything for which there was a check box, e.g., any cache, data partition, OS, etc. Since it was a virgin phone, I could do this with impunity, so I'm not sure how well this "solution" would fit someone else's situation. Also, I did try to wipe things in past attempts, just not with so much thoroughness.
So there you have it. I hope this helps someone.
EDIT: removed issues and added current.
Edit 2:
well, good new, im able to fastboot and log in to TWRP.
also flashed the previous file working.
anyway, to get the best help i will post some links and stuff...
The journey started here:
http://www.honornews.de/downloads/honor-6-android-6-0-marshmallow-beta-verfuegbar/
i did this and it worked.
B803 was running fine until i decided i wanted to run 804 and 805.
so i downloaded 804 TWRP and installed from this post:
http://forum.xda-developers.com/honor-6/general/emui-4-0-download-honor-6-l04-b803-t3290927/page20 (post 198 or something like that)
this also worked after some fiddling around.
the problems arose when i was trying to install the 805 recovery from the same post.
what I am wondering now is:
1. Could there be some issues with build.prop and local prop (and how can i check these files?)
2. could it be that either of the B805 i downloaded added some code, images or kernels to internal storage(the hidden directories that wont get wiped in TWRP)?
3. I notice that theres a whole lot of new folders in the internal memory, even after wiping in TWRP, which ones to delete?what is obsolete and can be safely removed.
4. Could it possibly be a permissions issue?one of my attempts with 805 booted into EMUI 4.0 but didnt recognize my simcard etc. and lagged after i tried changing permissions for both options. the linux and other android code.
After some charging i will try to do the unbrick feature again and test with the 550 update.app and/or mix the system.img and recovery.img from this one and then the other two files from the 805 update.zip...
so the downgrade to 550 worked!
its located here:
and extensively posted to. i laughed when it said i needed to wait to insert the SD until install screen, but it was truth.
note that the last two steps of installing 550, there is really no need to push those two images again.
just remember to add it to your SD before installing...
so, now i will update to 803 again
Full story:.
I downloaded the Android M, 803 last week and it worked fine, but i noticed that 804 and 805 had arrived so I wanted to test those.
Installing 804 went like normal and i used one of the guides here.
However, i wanted to root so I could downscale to 720p as i almost gain half a day extra on my device.
so i downloaded the tool and used the various steps, installed TWRP
and added root at the end
got stuck at bootloop
downloaded a recovery of 804 and restored with TWRP
this worked after some messing around in the logfile etc.
then the next step was trying to do the same with 805
i got stuck on bootloop for a while
tried the unbrick solution in the tool, tried to flash stock and other recovery options
tried adding manual update. app(on SD)
tried using cmd to add .img files(system, cust, boot, recovery)
this didnt work either
mixed and matched some old .img and new ones.
tried TWRP recovery of 805, also did not work
so i downloaded a downgrade pack that was intended for 803 to 521.
tried that
didnt work
used unbrick and added the system, cust, boot, recovery images from my B521.
and finally then i achieved a full brick
at least it appears i cant load into fastboot or any recovery,
eventually the phone boots to the b/w bootscreen but stuck there til battery runs out
the bootloader is unlocked, but im afraid its now hardbricked and not just softbricked, (at least when charging, the light turns on, but it doesnt appear to be charging much and it doesnt dim like it usually does when charging. i wish i somehow could enter the internal storage and just wipe everything(i guess i could run kali of it or something for a while) but i dont know how i can do that. i guess pros have tools for this.
if anyone can confirm, and/or know what the repair costs of this might be(i know this varies around the world, but any european estimate would be ok)
how did you resolve your problem? can you share with us?
kmlnvm said:
how did you resolve your problem? can you share with us?
Click to expand...
Click to collapse
look at post 198 or somewhere along pages 12-14 if i remember correctly, i followed those instructions...however, im properly done for now...
I’ll make this short.
I was successfully rooted. But I couldn’t update to 9.5.6.
I updated but it keeps failing. I switch to slot A and I was on 9.5.6 but WiFi didn’t work and apps would crash randomly, and it was laggy. I would go back to slot b and WiFi worked and everything was great but I’m on 9.5.3. And I would try to update again and it would fail and sometimes I would have to have in fastboot and reflash twrp to reboot to restore. I restored the device multiple times, removed root but it still happens. I used to always use android but I was on iOS for years and I’m used to jailbreaking and Apple IOS. Please help me. How can I restore and start from scratch? Or how can I fix this? It’s very annoying. I have my info backed up so I don’t care what I have to do. I love this phone but I had the Verizon iPhone bug when people call me and I answer it fails on there end. Or else I would deal with 9.5.3. All help is greatly appreciated.
You need to read the threads better, it's already been explained that wifi can end up being disabled because the rooted boot.img is older than your current rom version. Flashing one of the kernels available usually fixes this. You can also extract the boot image from the rom you downloaded and patch that boot.img file using Magisk, then when you apply that everything should work correctly.
From reading your post it would appear you're on T-Mobile (US) so you would need to download the 9.5.6 package and then extract the boot.img, then patch that using Magisk and push it to the phone using fastboot, once you reboot everything should be rooted and working.
Hello there.
I'm using tulip for few months now. One of first things that I've done, have been unlocking device, rooting it and put stock rom with root access on it. So far, so good. I did not encounter any serious glitches etc, but now I would like to finally upgrade miui to 11 (currently having 10.3).
And there's my problem. I would love to dodge making clean installation (wipe data etc) and I do not wish to risk to bootlooping my phone. I've read on some threads (older ones, but still) that you cannot simply install ota update in system, because due to changed recovery (I do have TWRP instead of fabric one) you will cause bootloop. I've tried alternative method of installing zip BY twrp, but program says, that it encounter a problem called "package expects build fingerprint (...) of tulip 0/PKQ1.180904.001/V10.3.2.0.PEKMIXM or PKQ1.180804.001/V11.0.2.0; this device has omni_tulip/tulip:8.1.0/OPM8.181105.002/1", and then sait, that in had error 7.
Is it simply wrong rom being installed and I have to choose something that is being named the same way and supports ota, or is there a way to go more swiftly through this process? If so and I should pick rom with ota - what to choose? I like deep level customisation, but compatibility with google store, being able to use store, payments and paid apps, instead of "opening them" by some lucky patchers kind of apps.
OR MAYBE I just need to change recovery from TWRP to something different - like PBRP f.e.? Just like this thread says - https://forum.xda-developers.com/re...how-to-setup-official-miui-breeaking-t3893703
Just a quick update - changing twrp to pbrp does not change anything in upgrade process - still get the same error, now just without telling me, which version do I have.
Also, what's interesting, apparently twrp said to me that I do have android 8.1, but "about phone" in system says, that its android 9 (9PKQ1.180904.001 to be exact).
That's werid, because everywhere I check, phone says "android 9" as a version of it.
Have you tried wiping system and installing?
Nitin Rai said:
Have you tried wiping system and installing?
Click to expand...
Click to collapse
Not yet. I've found method of flashing via PBRB with usage of downloaded file and one option check, but I'm not gonna try it, unless I do a backup of my apps. If that won't work, I'll perform a clean instalation and choose rom that supports ota.
well, I've tried to do this with the method, that I've described before, but this did not ended successfully. I'll look for rom with ota update possibility and then install it most likely. Apps had backup, so I lost almost nothing.
It worked. I had to download bigger patch (1.7 GB, instead of circa 700 MB, that I've tried before), I also had to use method described here -> https://c.mi.com/thread-1782169-1-1.html (pitch black recovery, instead of twrp + one tweak in options). Start after flash was very long (it took like 10 minutes or so), but it booted successfully in the end. Not sure which rom I do have after all, but as far as I remember it was so close to stock, as possible (with only few extra options and tweaks). So yea, it just works.
Cant flash twrp nor the patched magisk boot img to both slot a and b.
Bootloader is unlocked.
Flashing scripts via .bat files for stock zips of both android 10 and 12 results in "FAILED (remote: Partition product not found)" or "FAILED (remote: variable not found)" respectively.
I have no recovery.
When I had twrp, I've made the mistake of wiping my whole android 12 data, storage, and system and flashing an android 10 rom without reading up of the separate a and b boot slots nor the effects of my actions leading to bootlooping. (I've done with this other devices before with no problems). This in turn wiped the twrp recovery I had flashed and left me only fastboot commands and a twrp version up to 3.3 and 3.2 with no hope of getting usb otg to work as it was only available with the later versions of twrp and since I and now technically on an android 10 bootloader, any attempt at that time to flash twrp 3.6 was met with a (remote: Error calling AvbLoadAndVerifyBootImages Load Error) or some kind of other error I have no logs for. Now I cant even tetherboot to twrp 3.2 nor 3.3 and I get that error regardless.
[Boots to bootloader no matter what. Shows as UFS:Micron, Error reason - reboot bootloader - bootloader version is b1c1-0-4-7617406]
I believe I can get access to internal storage to flash these updates once I get a recovery tethered from the bootloader. I do not know if its possible to boot to fastbootd or whatever its called (used for write permissions/sideload update zips) even if I hadn't gotten into this predicament. I will be buying another Pixel 3 in the meantime as I have money to burn and like to hurt myself financially, and emotionally to get to my goal with this device. ( Didn't buy another one, I was committed to the cause!)
I am not a noob nor a pro, but somewhere in between. My biggest point of failure is not reading up on how the partitions are set up and the various issues others had when flashing android 10 and 11 roms. Any suggestions other than "uPdAtE tHe fAsTbOoT aNd AdB dRiVeRs" are not welcomed. Thank you. I will update once I find a soluton to my problem Which I Will.
Again, my main concern right now is getting tethered twrp to work again and need suggestions. I have older versions of platform tools and the latest so please non of those comments I see on literally every other thread.
Edit: I didn't mention this before, but I did have the ability yo sideload when I had twrp at the time before crapping everything out the window, but nothing would work and gave up. Just wanted to add if anyone was wondering.
First update, I used the propriatary "Tool All In One Tool" and I was able to boot to fastbootd, and wipe my data and storage, while updating my stock zip to android 12. Now I can tetherboot twrp 3.6.1_11-0 with the option for usb otg, wish me luck boys. I'm in.
Second update. Still stuck on first update, but weighing my options in the meantime. I flashed twrp via the flash current twrp option, but when I boot to it, touch is disabled so thats great... I can fast boot to only the twrp versions after 3.6+, so not so bad. I have no os installed, but I will try my hand again at that tool all in one tool again. I'll update tomorrow if anything comes of it.
3rd update. FROM THE BRINK OF DEATH!!! WHOOOOOOOOOO!!!!! I got the pixeldust rom flashed and working like a BOSS!!!!! You won't believe the 2 days I've had trying to get this thing to work. All in all 1 out of my 3 flashdrives finally worked with otg. I had a windows recovery drive premade on it so I just copied and pasted the files there without a hitch! Thank you Google for having to make me miss work and actually do research to get this thing working again! Thank you for the guys at Tool All In One Tool for making this recovery possible, I will shout out your thread. If anyone who's in a similar situation needs any help from me or any info, I'll be glad to help. This will be the second to last update. I can also make phone calls and use data so Pixel Dust rom is good to go if that was one of your concerns. See ya!
Final update, I got crdroid flashed with root and safetynet passed, I just found out that google Pay was imbedded in gapps so now I don't need the pay app anymore to do transactions! My banking app also works, got vanced finally installed (couldn't do it on regular stock ROM) some glitches with the ROM here and there but no worries. For who ever reads this. There's hope. I fd up as bad as you can get shy of a hard brick. I still don't know too much but learned near twice as much as I knew just a few days ago. If you need help just DM me and I'll work my hardest to bring the light. This phone is absolutely amazing and on god wished google was a better company to praise. I have more plans for these phones and hope more Roms come out to support it.
I have one question however, how do I make a backup of my system/system_ext partitions? I can make a back up of everything else but that with these two Roms... I have a backup of it with my stock ROM, but it resumed to mount when I used otg... Didn't try internal yet but I'll assume the same, is it a glitch with current twrp?