Database Info

d80020y issues getting recovery flashed

New to the G2 world, unit just came in yesterday, rooted with stump root brute force. Worked well, got busybox, flashify, sqlite, and tibu all working. Tried to flash twrp 2.8.5.0 in flashify and think I fubared my recovery. When I try to boot into recovery using quickboot, I get white text up top
ERROR: boot certification verify
Secure boot failure
Then screen quickly goes black, from there I can hold power button and reboot, only issue when booting phone, upon unlock I get com.google.process.location has stoped, otherwise phone seems to function perfectly.
If I use hardware buttons to boot into recovery, I get a white screen with two option, yes or no to factory reset. Assuming this is stock LG recovery, regardless not sure if I should try CWM or stick with my trusty twrp. A lot of stuff on the forum about downgrading bootloaders/ firmwares, making sure modems match the rom flashing. At this point I just want a custom recovery. Any help would be very much appreciated. Don't want to screw it up anymore.

Nerds, help a brother out... this forum sucks compared to note 3 section.

I think I replied elsewhere recognize your username. Use autorec.
If you can get into Android.

thor1k said:
I think I replied elsewhere recognize your username. Use autorec.
If you can get into Android.
Click to expand...
Click to collapse
I use this Autorec, it stated it completed and gave option to boot into recovery or to exit, do we need to use this program to initiate recovery or should it be an option when I choose reboot?
I see everyone mention to use this Autorec apk but I did not see any sticky on our phone about how to use it after we install it or any mention of enabling or using recovery after the install on any of the 6 threads I located with its reference...
When it ran it said 2.7.0.0 in the header, is the version I used old?
If you used this Autorec, what next? Thanks..

sobitthen said:
I use this Autorec, it stated it completed and gave option to boot into recovery or to exit, do we need to use this program to initiate recovery or should it be an option when I choose reboot?
I see everyone mention to use this Autorec apk but I did not see any sticky on our phone about how to use it after we install it or any mention of enabling or using recovery after the install on any of the 6 threads I located with its reference...
If you used this Autorec, what next? Thanks..
Click to expand...
Click to collapse
it's an option for me when I reboot because of GravityBox and Xposed framework, but you can use the usual method to get to recovery after it's flashed. Use the app to get to the recovery once to make sure it's there, then you can safely do the "factory reset" on startup (it won't actually reset it'll just go to recovery) to go to the recovery.
yeah there isn't too much clear documentation about the whole process but follow the steps in sequence that are listed under the Guide section here: http://forum.xda-developers.com/showthread.php?t=2715496
finally you may need to update the touch firmware after-- I did at least: http://forum.xda-developers.com/showthread.php?t=2736166

thor1k said:
it's an option for me when I reboot because of GravityBox and Xposed framework, but you can use the usual method to get to recovery after it's flashed. Use the app to get to the recovery once to make sure it's there, then you can safely do the "factory reset" on startup (it won't actually reset it'll just go to recovery) to go to the recovery.
yeah there isn't too much clear documentation about the whole process but follow the steps in sequence that are listed under the Guide section here: http://forum.xda-developers.com/showthread.php?t=2715496
finally you may need to update the touch firmware after-- I did at least: http://forum.xda-developers.com/showthread.php?t=2736166
Click to expand...
Click to collapse
I tried to see if the TWRP manager would detect it, said it wasn't there, so installed Clockwork manager and it installed some old version of recovery, wouldn't let me choose the IMG file for touch I had downloaded, there was option for boot into recovery within that app, I did, and poof, I was into TWRP .
Unknown waters since never used it. I tried same method as other ROMs, although did not factory reset, or see option to install new ROM like in CWM, wiped dalvik n cache, installed zip of cm12, gapps, su, wiped cache again, it started process of updating android, hope all is well, that app was new and different for me and I was expecting the good old clockwork I used for years to be there so I didn't research it too much since I thought it failed to load since our device is not on list of supported devices.
Looks like it worked, and it knew my previous device and all my apps from my other Lollipop Atrix HD I had, likely through Google back-up, and is downloading all my apps for me, even before logging into Cyanogen account, which usually did that for me...
Was like 40 apps to load, will see if she still works after all the apps load, didn't think I had that many on previous device, hope not every app I ever tried out...
Will try and uninstall the CWM app if that is still there since TWRP seems to load, or just keep to initiate recovery mode for updates..
---------- Post added at 03:44 PM ---------- Previous post was at 03:05 PM ----------
No, that must not have been the correct way...
All was fine until I opened up Facebook, then every single app on my phone started to open up, settings were moving about, like a dozen people were in my phone remotely changing up every setting possible...
ruh roh...
After another forced reboot it seems to be working fine for now, although the phone is now called a AT&T Lge LG-D801 in Google Play when it is a D800.

Need help on how to flash TWRP properly (Exynos) (SM-G930F)

Hi there. Recently (just yesterday) I tried flashing TWRP 3.1.0-0-herolte via Odin V3.12.3.0. However I ran into a little issue. Bootloop. TWRP seemed to work fine, but the phone wouldn't boot into android (stock touchwiz), exhibiting the 'samsung galaxy S7' logo periodically, but not going past that. Firstly I'll give some details on the phone and how I 'tried' to to flash TWRP. The phone I have is an Exynos variant SM-G930F running Android 7.0 and the recent update from late March. It is an Australian model (otherwise known as the 'international' version I think). Anyway as for what I was using as a guide, it was this. Before attempting this I enabled 'OEM unlocking' within the developer options but not 'USB debugging' (not sure if this contributed to the issue, but thought I'd mention it anyway). Later on I downloaded the Samsung Mobile Drivers and the tar file for TWRP. Installed the drivers, opened up Odin, entered download mode on the S7. I placed the tar file in AP and connected via micro usb. Almost everything, including auto-reboot, was turned off except F. Reset Time. Though chances are I probably left it on because I'm a doofus. After all that I pressed 'start' without doing any button combinations. Then after the screen went blank I pressed volume up + home hey + power button, roughly all at the same time. And then I entered TWRP. I then swiped to 'allow system modifications'. However as I didn't want to root the phone at the time, I decided to power it off through the menu. The next time I pushed the power button however, it was stuck in a bootloop. I then went back into TWRP and noticed that when I went into the install menu and was looking at the internal storage it appeared as 0mb (I thought that twrp had deleted all my files at the time), and I couldn't access the files I normally do like the downloads folder or app folders. However it seemed like most of the system folders were there like 'root' and 'data' etc. I then formatted the data and then did a factory reset as I thought it might fix the problem but it didn't. I swiped to install the twrp app but unchecked the two boxes. I then did some research and found out that if I ever were to run into an issue like this that I should flash the stock firmware, which is what I did. And viola! It worked again! I was slightly stressed at the time, lol. Luckily the apps and data I had previously were stored in the cloud.
After all this I have a question, what do you guys think I did wrong? Have you ran into this issue before? And what do you think may have caused the bootloop. I eventually want to start rooting my S7 and perhaps flash a rom, but I don't want to run into the issue again. Cheers!
P.S. I'm probably the biggest tech noob I know so go into a little bit of detail if you know what I did wrong so I don't make the same mistake again

Sounds like you hit the problem listed in step 9 & 10.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot
Click to expand...
Click to collapse
You swiped to allow system modifications, but you chose not to root and turned it off.
I don't see any mention of you flashing the dm-verity and force encryption disabler zip in TWRP which is required even if you're not rooting.

Beanvee7 said:
Sounds like you hit the problem listed in step 9 & 10.
You swiped to allow system modifications, but you chose not to root and turned it off.
I don't see any mention of you flashing the dm-verity and force encryption disabler zip in TWRP which is required even if you're not rooting.
Click to expand...
Click to collapse
Hm, that might actually be it. As a question how would be able to do that? Do I need to download that separately or something ( the dm-verity and encryption disabler zip I mean)?
EDIT
Actually never mind, it seems to say it right within the guide lol. So the problem should go away if I do that first yeah?

Yep just download it and put it on an SD card or transfer to the phones internal storage (I think TWRP lets you USB transfer) and go install zip in TWRP and select it.
That should stop your boot issues after installing TWRP, should even work even if you do it after a failed boot.

Beanvee7 said:
Yep just download it and put it on an SD card or transfer to the phones internal storage (I think TWRP lets you USB transfer) and go install zip in TWRP and select it.
That should stop your boot issues after installing TWRP, should even work even if you do it after a failed boot.
Click to expand...
Click to collapse
Hey bro, just wanted to say thanks. Got it rooted soon after as well. I found out I had to format data first before because it wouldn't let me install any zips. But after doing that it worked without any hiccups.
Cheers.

You should reset/wipe ur device after you have installed twrp through odin. That's a simple that some people wouldn't see in the tutorial. Then if you want root access you can flash SuperSu. Hope your problem will be solved. Good luck.

amalantony said:
You should reset/wipe ur device after you have installed twrp through odin. That's a simple that some people wouldn't see in the tutorial. Then if you want root access you can flash SuperSu. Hope your problem will be solved. Good luck.
Click to expand...
Click to collapse
Already did that before bro. Works as swell as a bell.

TheNickleS said:
Hey bro, just wanted to say thanks. Got it rooted soon after as well. I found out I had to format data first before because it wouldn't let me install any zips. But after doing that it worked without any hiccups.
Cheers.
Click to expand...
Click to collapse
Glad it's all working.
First time I installed TWRP I installed a ROM straight after which said to to format data, so never knew TWRP install alone needed the format data too.

Beanvee7 said:
Glad it's all working.
First time I installed TWRP I installed a ROM straight after which said to to format data, so never knew TWRP install alone needed the format data too.
Click to expand...
Click to collapse
From what I understand that's because the ldm-verity triggers. And so formating the data removes any encryption allowing for things to be flashed. But because I didn't do all of that first my S7 wouldn't boot up past flashing twrp.

OP6 stuck in bootloop - how do I fix this?

Hello!
I seem to only post on this homepage whenever I f*** up, and so here I am...
I'll try to explain this as best as possible.
I decided I wanted to root my OP6 so I could cheat in PoGO since the weather turned bad.
I followed a guide precisely - https://oneplus.gadgethacks.com/how-to/root-your-oneplus-6-with-magisk-beginners-guide-0185541/ - this one specifically.
So my phone is now rooted and I've got Magisk and TWRP, everything seems fine. I go to download the Root Checker and it gives me an error that it's not compatible with my device.
I freak out and try out various things inside Magisk Hide to make it work. It eventually works out and "YAY MY PHONE IS IN FACT ROOTED". Although the SafetyNet thing gives me an error.
Okay, I Install PoGo, go to Magisk Hide and select it. Start it up, log in.... Failed.... "Oh no". Failed... Failed... Failed...
Urgh, whatever I think. Let's just get rid of the root and TWRP then. Can't be too hard? Oh Magisk has an uninstall feature, let's hit that up. Uninstalled. Huh? PoGo still not working.
I've spent a few hours now trying to get this to work, my phone is wiped and not really useful. Let's remove TWRP then right? Right??! Steps are simple.
Wipe Phone, get a stock OP6 rom thing.
Press the install button. Nothing happens, wait for 10 minutes. It now asks me to reboot, no errors show up.
Good, it's booting. It's been twenty minutes, still booting... 30 minutes, still booting...
I'm stuck.
I know I screwed up somewhere, but does anyone know what I can do?
I can reboot to recovery, which is stock recovery now.
EDIT: Okay, so I couldn't idly sit by, so I went into recovery and wiped data yet again. It booted up this time and is now asking me to update my OS!
One problem resides, I can't download Netflix, which means I'm tripping the safetynet thing. Is it because my bootloader is unlocked? If so, how do I lock it again?
EDIT2: I really can't sit still. Googled, found out how to lock bootloader. Let's see if Netflix works.
EDIT3: Netflix can be downloaded, so I think everything works as it should again. I'm now installing official updates to my phone. If it breaks, I'll be here again.

LOL.
At least you have a working device again.
Once you unlock your bootloader your widevine level goes to 3 (level 1 is default meaning bootloader locked). There are people reporting to get netflix working but HD streams seem to be broken then so just SD quality.
I guess you messed up with your a/b partitions. This happens when you don't install twrp properly to both slots. Installing means to boot twrp with fastboot and install latest twrp.zip.
After that you flash magisk. Right now to keep dm verity you need to flash magisk 16.0 (stable). After rebooting your system, open magisk switch to beta channel and install latest version (16.7) directly through the magisk app. After reboot you should have dm verity ticked.
For safety.net passing: magisk needs an update due to api changes from safety.net/ google.
If my rom doesn't boot I just reinstall latest oos build, boot twrp and flash twrp.zip, then magisk.

lol, glad you have everything up again. I remember when i used to go through these scenarios on the regular. Do you want root for any specific reason? i only ask because after years of being rooted, i really feel that the pros no longer outweigh the cons. Once the whole A/B partition thing was introduced (i believe it was in Nougat?), it opened up the doors to a lot of possible issues with softbricking, etc. I'm still here on xda to see if there's anything that will bring back the itch for tinkering/rooting, but for the time being, you can find just about any nonroot alternative to what you might need.
PhilGizzle said:
Hello!
I seem to only post on this homepage whenever I f*** up, and so here I am...
I'll try to explain this as best as possible.
I decided I wanted to root my OP6 so I could cheat in PoGO since the weather turned bad.
I followed a guide precisely - https://oneplus.gadgethacks.com/how-to/root-your-oneplus-6-with-magisk-beginners-guide-0185541/ - this one specifically.
So my phone is now rooted and I've got Magisk and TWRP, everything seems fine. I go to download the Root Checker and it gives me an error that it's not compatible with my device.
I freak out and try out various things inside Magisk Hide to make it work. It eventually works out and "YAY MY PHONE IS IN FACT ROOTED". Although the SafetyNet thing gives me an error.
Okay, I Install PoGo, go to Magisk Hide and select it. Start it up, log in.... Failed.... "Oh no". Failed... Failed... Failed...
Urgh, whatever I think. Let's just get rid of the root and TWRP then. Can't be too hard? Oh Magisk has an uninstall feature, let's hit that up. Uninstalled. Huh? PoGo still not working.
I've spent a few hours now trying to get this to work, my phone is wiped and not really useful. Let's remove TWRP then right? Right??! Steps are simple.
Wipe Phone, get a stock OP6 rom thing.
Press the install button. Nothing happens, wait for 10 minutes. It now asks me to reboot, no errors show up.
Good, it's booting. It's been twenty minutes, still booting... 30 minutes, still booting...
I'm stuck.
I know I screwed up somewhere, but does anyone know what I can do?
I can reboot to recovery, which is stock recovery now.
EDIT: Okay, so I couldn't idly sit by, so I went into recovery and wiped data yet again. It booted up this time and is now asking me to update my OS!
One problem resides, I can't download Netflix, which means I'm tripping the safetynet thing. Is it because my bootloader is unlocked? If so, how do I lock it again?
EDIT2: I really can't sit still. Googled, found out how to lock bootloader. Let's see if Netflix works.
EDIT3: Netflix can be downloaded, so I think everything works as it should again. I'm now installing official updates to my phone. If it breaks, I'll be here again.
Click to expand...
Click to collapse

thefallen924 said:
lol, glad you have everything up again. I remember when i used to go through these scenarios on the regular. Do you want root for any specific reason? i only ask because after years of being rooted, i really feel that the pros no longer outweigh the cons. Once the whole A/B partition thing was introduced (i believe it was in Nougat?), it opened up the doors to a lot of possible issues with softbricking, etc. I'm still here on xda to see if there's anything that will bring back the itch for tinkering/rooting, but for the time being, you can find just about any nonroot alternative to what you might need.
Click to expand...
Click to collapse
It is just different.
You have to forget the "old way" and then you don't face any problems.
Same with encryption that wasn't present before.
I still can't live without root.
Too many missing functions (xpsoed edge, titanium, afwall, xprivacy, gravitybox).
And the newer rom system by just applying a magisk module is pretty cool.

pdppdp said:
LOL.
At least you have a working device again.
Once you unlock your bootloader your widevine level goes to 3 (level 1 is default meaning bootloader locked). There are people reporting to get netflix working but HD streams seem to be broken then so just SD quality.
I guess you messed up with your a/b partitions. This happens when you don't install twrp properly to both slots. Installing means to boot twrp with fastboot and install latest twrp.zip.
After that you flash magisk. Right now to keep dm verity you need to flash magisk 16.0 (stable). After rebooting your system, open magisk switch to beta channel and install latest version (16.7) directly through the magisk app. After reboot you should have dm verity ticked.
For safety.net passing: magisk needs an update due to api changes from safety.net/ google.
If my rom doesn't boot I just reinstall latest oos build, boot twrp and flash twrp.zip, then magisk.
Click to expand...
Click to collapse
hey, i rooted my device yesterday on 10.3.3, all was good until i got into a bootloop after installing busybox from the magisk repo. i keep going back to the fastboot mode, i still have access to twrp but sadly i didnt make a nandroid backup. i really dont know what to do now and i know this is not the relevant thread to ask this question. im sorry, but if anyone knows a method to solve this please let me know. thanks

I would make a nandroid (just in case) now and then flash the full firmware again, reflash twrp and then xxx. This keeps your data and you should have a working system.

pdppdp said:
I would make a nandroid (just in case) now and then flash the full firmware again, reflash twrp and then xxx. This keeps your data and you should have a working system.
Click to expand...
Click to collapse
Make a nandroid of the Bootlooped system? Is it OK to flash the full firmware without performing a factory reset? Thanks...
EDIT- thanks a lot for this method Bro. .worked like a charm and now I'm back into system. .reflashing twrp and magisk now..thanks again

You're welcome.
Nandroid of your data in case something goes wrong and wipes the device. System is 'replacable'

pdppdp said:
You're welcome.
Nandroid of your data in case something goes wrong and wipes the device. System is 'replacable'
Click to expand...
Click to collapse
Yup that's a good precaution to take in case things go south. Anyways i was reading your earlier post on how unlocking the bootloader sets the widevine level to 3 and causes some problems to use netflix. I was unaware of this issue before i rooted. It's really a bummer, soon after reading your post i realized that netflix was missing and i went to play store to download. I couldn't find the app,then i downloaded the app from apk mirror and after installation i had this error that the device is not supported by the app. I did some research on the issue and on a OnePlus forum i found a solution, i went to the netflix website and logged in with my account, then i tried playing something which indicated me to download the app from play store and viola, the app got downloaded and works perfectly fine, it's kinda surprising. Thought I'd share this here if in case it might work for someone else...

I used a magisk module that I can't reverse even with a full wipe

I downloaded a Magisk module to test out that purported to bypass DRM of netflix, Amazon, and a couple others and it put my phone into a boot loop. I installed a recovery magisk module zip for recovery that allowed me to disable the module from TWRP but it didn't matter because it just stopped the module and didn't replace the changed DRM file. After that I just gave up and fully formatted my phone with the All in One tool using "Decrypt phone / erase all data" and then installed a fresh stock ROM image via fastboot. The problem is, even after doing all of this, the DRM file that this module changed is still changed and I can't use streaming services and my phone is incredibly unstable. When I open Netflix for instance, it says I need an update and when I go to the play store it tells me "Netflix is not compatible with your device". Also, even after a full wipe, Nova launcher is still installed, and it's not supposed to be, I have no clue how these files are persisting through a full wipe. I've been tinkering with my phone for over a year now and this is the first problem I've found that not even fastboot can seem to fix. I'm on Tmobile and originally was able to unlock my bootloader by flashing Android 10 Developer preview 3, which they accidentally allowed you to unlock the bootloader with. I did that to unlock my bootloader then rooted and I've been using international ROM's ever since. I'm worried if I have to go back to Stock tmobile ROM I won't be able to get my bootloader locked again, and I still have no clue if this will even fix the issue. Does anyone have any clue how to fix this? If you search "drm" on magisk modules you'll find two things, one that removes all drm, and one from 2019 that attempts to bypass it. (I figured I'd test this out to see if I could watch Netflix in 1440p with my bootloader unlocked and didn't expect it to work, just didn't expect it to find a way to soft brick my phone) I'm using the 2019 one. Is it possible if I re-root my phone to somehow aquire the original DRM files this thing changed and replace them? Are these not included as part of a stock ROM? I don't understand how I can't fix this. My last plan is to reinstall TWRP and wipe literally every option on there then flash a ROM via fastboot, but I doubt it's going to work if formatting the entire phone doesn't work
Edit: Installed TWRP, wiped literally every option so I didn't even have an OS anymore, used fastboot to decrypt / erase all data then when installing stock ROM I chose again to wipe all data. If nova launcher and the changed DRM persists through this I'm going to be completely stumped. The only thing I can conclude is that somehow my phone is not actually fully wiping itself even though I'm using 3 different methods to do it
Edit 2: This still didn't work. I think I'm gonna have to use the MSM tool and go back to tmobile stock. If I flash far back enough I should in theory still be able to flash Android 10 DP3 and unlock my bootloader again, it's just gonna be an unexpected pain in the ass task to deal with today
Edit 3: Thank god for modified msm tool, I didn't know they were able to modify it to convert your tmobile phone to international and unlock the bootloader. This is going to be much easier than anticipated as long as doing this actually fixes my drm files and really wipes everything
Edit 4: Even using MSM tool to install a factory international ROM fixed the Netflix issue but somehow Nova Launcher is persisting through every single kind of wipe I've done lol. Despite the bootloader being locked (wasn't supposed to be) after this update, Netflix still wouldn't play in HD which is kind of odd. I'm now going through the process of installing Android 10 DP3 and unlocking my bootloader then downgrading back to pie to root and install TWRP again. I'm just going to have to accept that Nova Launcher is a part of my phone now lol

Maybe I'm wrong but didnt op7 pro have an irreversible e-fuse that once triggered with root it wiped out the ability to see HD forever ? Something to do with downgrading widevine drm levels if I remember correctly... The nova thingy I cant explain but hey it could be worse you could be stuck with Microsoft's launcher [emoji1787]
Sent from my GM1913 using Tapatalk
---------- Post added at 10:41 PM ---------- Previous post was at 10:17 PM ----------
Just a thought that crossed my mind, could it be that Nova is surviving as a system app in A or B slot? Are you sure you are wiping system in both slots?
Sent from my GM1913 using Tapatalk

Rooting Pixel 4a, Android 12

Hello, I've searched and haven't found any thread like that.
Does anybody know is there a chance, after installing Android 12 by OTA, to root the phone?
I've followed the instruction from: https://www.droidwin.com/how-to-root-pixel-devices-via-magisk-on-android-12/
but I get a bootloop. I've tried:
adb reboot bootloader
fastboot flash boot magisk_patched.img
fastboot reboot
then, I've tried:
adb reboot bootloader
fastboot getvar current-slot (it's 'b' in my case)
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
fastboot reboot
It's bootlooping until I flash original boot.img.
I'm using the latest Magisk canary.
It would be really, really nice to be able to use Andorid 12, but rooted.

Happened to me a week ago,
go to https://developers.google.com/android/images and flash the latest image. then flash the modified boot img.
Also r u aware on how to pass safety net on android 12.

khcubee said:
Happened to me a week ago,
go to https://developers.google.com/android/images and flash the latest image. then flash the modified boot img.
Also r u aware on how to pass safety net on android 12.
Click to expand...
Click to collapse
But would I keep the data? My modified boot img seems not to work at all (flash, nor even boot).

No u would not keep ur data. but i backed up my **** with swift backup. then restored and its working perfect.

khcubee said:
No u would not keep ur data. but i backed up my **** with swift backup. then restored and its working perfect.
Click to expand...
Click to collapse
There is a problem with Swift Backup that you can't copy data with no root

@wolfenstein3de
Thank you for the link. I used it to root my Pixel 4a after I did the OTA to Android 12 today and wanted to share my experience.
I had it unlocked and rooted with magisk before and had existing backups of everything.
When I did me root just now, I did not loose any data when uploading the patched boot. Everything went smoothly.
Obviously this doesn't mean you or anybody else might loose their data so to try to create a proper backup first!

Hotsndot said:
@wolfenstein3de
Thank you for the link. I used it to root my Pixel 4a after I did the OTA to Android 12 today and wanted to share my experience.
I had it unlocked and rooted with magisk before and had existing backups of everything.
When I did me root just now, I did not loose any data when uploading the patched boot. Everything went smoothly.
Obviously this doesn't mean you or anybody else might loose their data so to try to create a proper backup first!
Click to expand...
Click to collapse
Hello, I tried putting the fresh system and then - rooting. No problem! But then I've read about no more support for Magisk Hide.
I used root (in order of importance):
- yt vanced (can be used as separated app, no root needed)
- tasks for tasker (some doesn't work, like turning wifi on while the airplane mode, creating hotspot etc.)
- adblock (apparently work cool without root)
- Magisk advanced battery control (I preferre charging with 0.5A during the night up to 89%, disable charging during flying the drone and keeping 49-50% during card rides)
- ads in apps
- possibility of recoding the calls
- possibility for creating backups, also with data apps
- removing apps (still, I can hide them with Nova Launcher, though)
But I stopped being able to use one of my bank apps and some others.
I know that it was hard, from time to time, that after updating some apps, root make them impossible to use them. I gave up! Maybe I'm getting old. Long time ago I needed root to play with kernels, changing power of my cpu and killing taks from RAM, but now days, even with 6 communicators in background, recording the screen, some post apps running, gmail + DjiFly, everything seems to work fine. But if not yt vanced - I would stay rooted.
Maybe somebody knows if there's a way that making backup with no root, but using the bootloader would work or if there's a way to record the calls?

I had my 4a rooted with version 11 using Magisk and sunfish-rq3a.211001.001-factory-5d6da39f and made the mistake of OTA updating to 12. 4a is still unlocked but I lost root which is why I am reading this thread.
I see the instructions to go to here https://developers.google.com/android/images for the latest version. As you may know Google pushed out the Verizon version of 12 which is on my phone now SP1A.211105.002.A1, Nov 2021, Verizon, Verizon MVNOs). I would like to not have the Verizon version on my phone (does that even make sense?) and was wondering which load to use - this one: SQ1A.211205.008, Dec 2021?
I know enough to get the root done but not much else about the hardware/sw versions.
Thanks

Lakesidepark said:
I would like to not have the Verizon version on my phone (does that even make sense?) and was wondering which load to use - this one: SQ1A.211205.008, Dec 2021?
Click to expand...
Click to collapse
Yeah, there's only 1 December version. No variants like November.

Is it possible to root the 4a, flash with stock ROM and then use banking apps or is it prohibited due to SafetyNet or so?
I am asking because I would like to use apps that require root like greenify, adaway, titanium backup, naptime, etc to get rid of ads and optimize battery life.... But, before, I need to know if banking apps will work.
Thanks in advance...

ErnstHaft said:
Is it possible to root the 4a, flash with stock ROM and then use banking apps or is it prohibited due to SafetyNet or so?
I am asking because I would like to use apps that require root like greenify, adaway, titanium backup, naptime, etc to get rid of ads and optimize battery life.... But, before, I need to know if banking apps will work.
Thanks in advance...
Click to expand...
Click to collapse
Greenify? Naptime?? Holy time warp! Root was great when root was needed. AOSP has come a long way since then. Root still viable but a high bar and even greater use restrictions. And ya'h, safety net will ruin your day over and over again. Cheers, mate!