Related
When Android 7.0 ( Nougat ) is finally released for Motorola X Pure (2015) XT1575 ( Hopefully by the end of the year ), will SystemLess Root still work as is it does now for 6.0 or should we wait for someone to run it in a sandbox? Should we wait for the First Quarter of 2017 before we get anxious and upgrade to the newest Android, to give all of the developer time to perfect they're processes.
We all know now that it will be released as a STOCK image, but I have a lot of Root Apps (i.e. Titainium, Backup, Root Explorer, Xposed, Gravity Box for MM, etc) which I would still like to use. From what I can see of 7.0 it's not much different than 6.0 except for split screen and some other features that I'm sure we.re not aware of yet..
All I can say it It doesn't work on the G4... yet. I maintain a root thread on the G4, haven't found a viable way to root it on Nougat, all methods mess up data and a bunch of framework stuff (like settings menu). I assume the Nougat on this will be roughly the same. Don't worry, it will come though.
And Xposed isn't available for Nougat, it isn't known yet if it will be. Remember when Marshmallow came out they almost dropped Xposed completely, they were so close they had actually said they shutting down development of Xposed then had a unexpected breakthrough. The developers of Xposed have said that it will die in the hear future due to changes in Android.
Yeah, xPosed isn't something I would rely on moving forward. Right now AICP & CM are making great strides with N 7.1 and including Root so you can go that route and get the Root you desire. I'm on TurboROM which is still an MM base and will move to AICP N 7.1 once things settle in some more, but as of right now AICP is pretty darn nice as is. I've tested it every few days to see the progress, but for daily, revert to my most current backup of Turbo for now. AICP usually includes a LARGE amount of customizations. I go that route normally and remove all the AOSP stuff I can replace with Google APPs directly and use Moto Camera instead as well giving me a really clean and functional bug-free experience. GravityBox becomes mostly unnecessary with AICP or CM. Boy I'm rambling worse than normal today...
Back on track... Try out AICP with N 7.1 or wait for a Stock Rooted
Thank you for the reply, I wasn't sure if I should upgrade or not.
My pure has been running pretty good since I got it back in May of this year thru SWAPPA, and I have the latest security mod for May 1 (Build MPHS24.49-18-4), I wasn't sure if Lenovo would push another Security update for 6.0 (MM) or push 7.0 for the next update, and I didn't want to mess anything up..
I love this phone, and I'm not sure if and when I will upgrade, but I know it won't be MOTO/LENOVO anymore, unless they can unlock the bootloader for Pixel and gain root, I may lean that way...
NEVER, NEVER, Never will I go the way of the Apple, anything that comes from that place sucks, it's too restrictive..
DROID Forever !!!!!
CLETjB said:
Thank you for the reply, I wasn't sure if I should upgrade or not.
My pure has been running pretty good since I got it back in May of this year thru SWAPPA, and I have the latest security mod for May 1 (Build MPHS24.49-18-4), I wasn't sure if Lenovo would push another Security update for 6.0 (MM) or push 7.0 for the next update, and I didn't want to mess anything up..
I love this phone, and I'm not sure if and when I will upgrade, but I know it won't be MOTO/LENOVO anymore, unless they can unlock the bootloader for Pixel and gain root, I may lean that way...
NEVER, NEVER, Never will I go the way of the Apple, anything that comes from that place sucks, it's too restrictive..
DROID Forever !!!!!
Click to expand...
Click to collapse
Pixel bootloader is unlockable. Verizon Pixel has bootloader unlock tool from the Sunshine team free of charge. Also It is rootable via newest SuperSU beta I believe.
I have been unsuccessful at rooting stock nougat, it just gets stuck on the boot animation forever and the battery heats up.
So, has anyone rooted it on nougat 7.0 and how?
Every time I try it just gets stuck loading and since I can't logcat to it I have no idea where its failing, but fastboot flashing the system image and the boot image fixes it, but then I am stuck back at non-root.
I know there has to be a way as many others say they are rooted just fine so I must be missing something.
I have several apps that use root and do system tweaks that would be helpful, mostly battery saving, option enabling, etc... But I can't use any of them for now. I especially wanted to use the undervolt and system governers min max settings.
roadrun777 said:
I have been unsuccessful at rooting stock nougat, it just gets stuck on the boot animation forever and the battery heats up.
So, has anyone rooted it on nougat 7.0 and how?
Every time I try it just gets stuck loading and since I can't logcat to it I have no idea where its failing, but fastboot flashing the system image and the boot image fixes it, but then I am stuck back at non-root.
I know there has to be a way as many others say they are rooted just fine so I must be missing something.
I have several apps that use root and do system tweaks that would be helpful, mostly battery saving, option enabling, etc... But I can't use any of them for now. I especially wanted to use the undervolt and system governers min max settings.
Click to expand...
Click to collapse
Yes, lots of people have rooted it... latest TWRP and Magisk, nothing special to do at all... Flash or boot TWRP and flash Magisk zip file, reboot and go.
Unlocked bootloader must have.
1st method:
Boot twrp - fastboot boot twrp3x.img
Do full backup,
Restore boot only,
In twrp install magisk14.zip, optionally wipe cache+dalvik, reboot.
2nd method
...the same steps,
Twrp terminal - type + ok:
echo SYSTEMLESS=true>>/data/.supersu
Install SuperSu2.82.zip, opt.wipe..., reboot.
Both method works.
I finally find magisk and it worked first time for me.
I tried SuperSU about 10 times in a row, systemless false, systemless true, etc, without it, and it always ended the same way boot loops.
So I am not sure that SuperSu2.82.zip is currently compatible with nougat, or at least with nougat + xt1565 hardware.
roadrun777 said:
...
So I am not sure that SuperSu2.82.zip is currently compatible with nougat, or at least with nougat + xt1565 hardware.
Click to expand...
Click to collapse
I wrote here(#8):
1st December 2017, 02:11 PM,
Here:
https://forum.xda-developers.com/moto-x-style/general/stock-xt-1572-reteu-7-0-ddumped-files-t3712521
30. November, 2017...rooted 29.
SuSu 2.82 is compatible.
Magisk Framework comes with SuperUser built in.. so when you flash another superuser, you mixing Binaries and it doesn't know which one to use.
After several weeks of battling terrible battery drain, lag and sluggish performance I am back on Stock Nougat, build number NPJS25.93-14-8. With moderate use, my battery is now averaging less than 2% per hour ( < 1% while sleeping), where on the custom ROM of choice it was running over 5% per hour, even while sleeping. I tried every trick and tweak I could find and Better Battery Stats didn't show anything that could account for the high drain. I even tried a different ROM to no avail. So I threw in the towel, returned to stock, and did the latest OTA updates. I am now running rooted with ElementalX kernel 1.04 and I couldn't be more pleases with the overall performance and battery life.
I am sure it was something I missed but I got tired of spending hours trying to get back to the original performance and battery life the custom ROM had several weeks ago. Sometimes you just gotta do what you gotta do.
While ota updates.......i brought to twrp only.... instead of installing latest security update.......... manually tried to install update...bt i can't..... gets an error... didn't u faced such problems
Harshseth said:
While ota updates.......i brought to twrp only.... instead of installing latest security update.......... manually tried to install update...bt i can't..... gets an error... didn't u faced such problems
Click to expand...
Click to collapse
None of STOCK ROM or OTA updates can be flashed/updated by TWRP, you need to be on stock recovery as well everything stock (unmodified system, boot and all).
I faced this problem too, but I fixed mostly of the battery drain tweaking the kernel with the ElementalX app to ~0,80/h. I had to set the little cores working like big cores do, because all little cores and one big were in use always; and applied LightingBlade profile.
Harshseth said:
While ota updates.......i brought to twrp only.... instead of installing latest security update.......... manually tried to install update...bt i can't..... gets an error... didn't u faced such problems
Click to expand...
Click to collapse
In order to use the OTA path you have to be on stock recovery, boot and kernel, not on TWRP. Otherwise you get the error that you experienced.
xAnkris said:
I faced this problem too, but I fixed mostly of the battery drain tweaking the kernel with the ElementalX app to ~0,80/h. I had to set the little cores working like big cores do, because all little cores and one big were in use always; and applied LightingBlade profile.
Click to expand...
Click to collapse
I went that path but it didn't seem to help much. Besides, I am happy with this stock setup. It is much better than when I was on Marshmallow stock and went over to custom ROMs. I can do anything I want to do and install any app I desire to use. Good performance, great battery life, and customizable as much as I want. No need to be on custom.
pastorbob62 said:
After several weeks of battling terrible battery drain, lag and sluggish performance I am back on Stock Nougat, build number NPJS25.93-14-8. With moderate use, my battery is now averaging less than 2% per hour ( < 1% while sleeping), where on the custom ROM of choice it was running over 5% per hour, even while sleeping. I tried every trick and tweak I could find and Better Battery Stats didn't show anything that could account for the high drain. I even tried a different ROM to no avail. So I threw in the towel, returned to stock, and did the latest OTA updates. I am now running rooted with ElementalX kernel 1.04 and I couldn't be more pleases with the overall performance and battery life.
I am sure it was something I missed but I got tired of spending hours trying to get back to the original performance and battery life the custom ROM had several weeks ago. Sometimes you just gotta do what you gotta do.
Click to expand...
Click to collapse
Are you able to root the stock nougat build npjs25 14-8.?
If yes how you rooted your phone. Plzz guide me. I also want to root my stock nougat
ADITYA_KUMAR said:
Are you able to root the stock nougat build npjs25 14-8.?
If yes how you rooted your phone. Plzz guide me. I also want to root my stock nougat
Click to expand...
Click to collapse
Before you can root stock Nougat you must first unlock you bootloader, install TWRP then flash Elemental X kernel 1.04 from TWRP.
pastorbob62 said:
Before you can root stock Nougat you must first unlock you bootloader, install TWRP then flash Elemental X kernel 1.04 from TWRP.
Click to expand...
Click to collapse
What is elemental x kernel. I have a unlocked bootloader.
ADITYA_KUMAR said:
What is elemental x kernel. I have a unlocked bootloader.
Click to expand...
Click to collapse
Instead of asking questions that have been answered numerous times (ad nauseam) you should try reading through the forums. I realize you are a raw noob, but if you wanted to learn Calculus, would you ask a bunch of questions without doing any reading and studying? It's no different when you are modifying your smart phone.
Here is a link to a thread that will guide you to rooting stock Nougat. It works for all versions of stock Nougat.
https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
But don't do anything until you have read through the procedures and fully understand. Above all, make a backup of your system from TWRP before you do anything else.
pastorbob62 said:
Instead of asking questions that have been answered numerous times (ad nauseam) you should try reading through the forums. I realize you are a raw noob, but if you wanted to learn Calculus, would you ask a bunch of questions without doing any reading and studying? It's no different when you are modifying your smart phone.
Here is a link to a thread that will guide you to rooting stock Nougat. It works for all versions of stock Nougat.
https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
But don't do anything until you have read through the procedures and fully understand. Above all, make a backup of your system from TWRP before you do anything else.
Click to expand...
Click to collapse
once I tried to root on stock nogut, so I installed TWRP and flashed SuperSu and my phone got bricked
pastorbob62 said:
After several weeks of battling terrible battery drain, lag and sluggish performance I am back on Stock Nougat, build number NPJS25.93-14-8. With moderate use, my battery is now averaging less than 2% per hour ( < 1% while sleeping), where on the custom ROM of choice it was running over 5% per hour, even while sleeping. I tried every trick and tweak I could find and Better Battery Stats didn't show anything that could account for the high drain. I even tried a different ROM to no avail. So I threw in the towel, returned to stock, and did the latest OTA updates. I am now running rooted with ElementalX kernel 1.04 and I couldn't be more pleases with the overall performance and battery life.
I am sure it was something I missed but I got tired of spending hours trying to get back to the original performance and battery life the custom ROM had several weeks ago. Sometimes you just gotta do what you gotta do.
Click to expand...
Click to collapse
Very true.
Also try LightningBlade tunables(v 1.2.3 ; the newer version does not work that well for me..).
Stock rom provides the best balance between Performance and Battery life.
siddhesh9146 said:
once I tried to root on stock nogut, so I installed TWRP and flashed SuperSu and my phone got bricked
Click to expand...
Click to collapse
If you're rooting on stock Nougat, you must have a custom kernel flashed (or used the temporary dm-verity disabler on the stock kernel) before you root. Else, without the mentioned modifications, you'll trip the anti-rooting protection built into the stock kernel, and you'll have bootloops unless you reflash your stock ROM as you experienced.
Easiest way, as per the guide is to:
Flash/boot TWRP.
Backup.
Flash ElementalX or vegito (any custom kernel will do, as these kernels do not have the anti-rooting protection).
Reboot to test.
Boot back to TWRP
Flash SuperSU v2.79 or newer, or magisk 13 or newer
Reboot.
You should be rooted, on stock, and if you've flashed magisk, Safetynet should be working It's working well on NPJS25.93-14-8 and it's stable. Granted, a few apps now seem to detect root/magisk (and fail to download/update from the Play Store, with an error 0), but nothing that a sideload from a legitimate source wouldn't solve...
champsp said:
Very true.
Also try LightningBlade tunables(v 1.2.3 ; the newer version does not work that well for me..).
Stock rom provides the best balance between Performance and Battery life.
Click to expand...
Click to collapse
True that! :good:
siddhesh9146 said:
once I tried to root on stock nogut, so I installed TWRP and flashed SuperSu and my phone got bricked
Click to expand...
Click to collapse
If you had followed the link I supplied you would have had your answer as to why you had problems and also how to fix it.
echo92 said:
If you're rooting on stock Nougat, you must have a custom kernel flashed (or used the temporary dm-verity disabler on the stock kernel) before you root.
Click to expand...
Click to collapse
Hi, sorry for ask, do you know where can i find the temporary dm-verity disabler?
I tried with a script named "no-verity-opt-encrypt-5.1" (this works for the G5 Plus 'Potter') but i haven't had any success. Even i unpacked the stock boot.img and i tried to manually patch it, but i failed here too.
Honestly i would like to test the stock kernel, because i never used it, i am always attached to flashing EX to get root access. Thank you in advance.
moonlightdrive said:
Hi, sorry for ask, do you know where can i find the temporary dm-verity disabler?
I tried with a script named "no-verity-opt-encrypt-5.1" (this works for the G5 Plus 'Potter') but i haven't had any success. Even i unpacked the stock boot.img and i tried to manually patch it, but i failed here too.
Honestly i would like to test the stock kernel, because i never used it, i am always attached to flashing EX to get root access. Thank you in advance.
Click to expand...
Click to collapse
I don't know if this will still work on later builds than the November/December 2016 builds, but here's the kernel with dm-verity disabled: https://forum.xda-developers.com/mo...t-how-to-root-n-firmware-npj25-93-11-t3532556 Seems to cause bootloops though on the later builds however
Strictly speaking, I misspoke - it's not really a dm-verity disabler, more a stock kernel with dm-verity disabled. I think EX kernel is still the more stable and more reliable option. It would be nice to be able to root the stock kernel though...
echo92 said:
I don't know if this will still work on later builds than the November/December 2016 builds, but here's the kernel with dm-verity disabled: https://forum.xda-developers.com/mo...t-how-to-root-n-firmware-npj25-93-11-t3532556 Seems to cause bootloops though on the later builds however
Strictly speaking, I misspoke - it's not really a dm-verity disabler, more a stock kernel with dm-verity disabled. I think EX kernel is still the more stable and more reliable option. It would be nice to be able to root the stock kernel though...
Click to expand...
Click to collapse
Oh, i see, thanks for your response. I'll look into it to see how he did to by-pass the dm verity, and try to modify the last boot.img that we have.
I mentioned earlier in this thread about getting Error 0 whilst updating apps in Google Play. As it turns out, thanks to this tip here https://forum.xda-developers.com/showpost.php?p=73552496&postcount=57 it appears to be an error with permissions on the /data/media partition.
I managed to fix it with osm0sis' script:
Download from here https://forum.xda-developers.com/showthread.php?t=2239421 the sdcard Fix Permissions script http://forum.xda-developers.com/attachment.php?attachmentid=3761904&d=1464187934
You may wish to back up your data with TWRP or ensure you have your photos and videos somewhere safe prior to flashing this.
Reboot to TWRP and backup your device.
Flash the above script.zip in TWRP and wait for it to complete. (it should be fixing the permissions in /data/media)
Reboot and you should be able to download/update apps again from Google Play afterwards. You may have to uninstall the app and re-install the app if it keeps failing.
I've got this working on a XT1642 running June 2017 stock ROM, rooted with magisk 13.3 and apps including Snapchat and Google Chrome update without issue now.
echo92 said:
I mentioned earlier in this thread about getting Error 0 whilst updating apps in Google Play. As it turns out, thanks to this tip here https://forum.xda-developers.com/showpost.php?p=73552496&postcount=57 it appears to be an error with permissions on the /data/media partition.
I managed to fix it with osm0sis' script:
Download from here https://forum.xda-developers.com/showthread.php?t=2239421 the sdcard Fix Permissions script http://forum.xda-developers.com/attachment.php?attachmentid=3761904&d=1464187934
Click to expand...
Click to collapse
Useful info, this happened to me a couple of days ago. I thought it was something related to the integrated Chrome WebView in conflict with the system WebView, because it only happened when i tried to update Chrome, or any of his variants (dev, beta, canary, etc). Thanks.
I have a question. I want to root my phone (upgraded from oreo to pie, stock), but i'm not sure what should i do. Should i use oreo rooting instructions? I can't find any tutorial for rooting on pie. I don't want to change my rom, i just want to have a root and be able do use the magick and modules that's all. It would be nice to have step by step instruction.
I know i have to unlock my bootloader first at htcdev, then install twrp (not sure which twrp and if the installation is same as on oreo?)
In the past i rooted one phone but it was completely different and i almost bricked my device, because some idiot posted wrong link on the forum... There is so many versions of everything and i'm feeling lost in it.
I hope this helps, but Pie is still very new for the HTC U11. Some even are saying that clean flashes of the Pie RUU have flash, camera, and wifi issues. I am currently running the amazing RR-P rom (which is based on pie), but it runs on the latest Oreo RUU. I have no issues with the ROM and I get insane SoT even without battery savings. I am excited for the future of this phone, since I love the hardware navbar (never liked the on-screen one / though my HTC m8 is still a boss, and even the forums there have a very solid Lineage 17.0 (android 10) working on it).
https://dl.twrp.me/ocn/
Above is the official link to the US HTC u11 TWRP recoveries. I don't think (to be safer than sorry) these are 100% compatible over the PIE firmware though.
I checked HTCdev, and it doesn't seem to have any difference in the instructions in unlocking the bootloader. No mention of Nougat or Oreo, so I would assume there's no difference in doing the same with Pie.
I flashed my U11 after Pie update, working fine, no problems with flash, wifi or anything else (CID: HTC__034)
1. Unlock bootloader via htcdev
2. Flash latest TWRP from the official site. Instructions here for example: https://www.xda-developers.com/how-to-install-twrp/
3. Flash Magisk (also from official Magisk site)… that was a little trickier, since TWRP can't mount the encrypted partitions. The workaround is to copy the Magisk ZIP onto an SD Card and flash it from there while in TWRP.
4. Enjoy.
I decided to root this U11 for the first time, since I don't expect any futur software updates coming form HTC.
Thank you for all your help, i'll try this out today. :good:
So i did everything and it's working but i have one problem. After installing magisk i tried to install some modules, and one of them caused bootloop and i was unable to delete it, and also i was unable to install module uninstaller (fail). So i had to do factory reset - any solution to avoid this kind of problems in future?
Also i installed xposed successfully, but none of modules was working..
Togzyk said:
So i did everything and it's working but i have one problem. After installing magisk i tried to install some modules, and one of them caused bootloop and i was unable to delete it, and also i was unable to install module uninstaller (fail). So i had to do factory reset - any solution to avoid this kind of problems in future?
Also i installed xposed successfully, but none of modules was working..
Click to expand...
Click to collapse
I have no answers, but as u can see a rooted pie is problematic, hence the many people reverting back to oreo and or nougat, but some people somehow make it work. Not me I could not downgrade quick enough after rooting, unrooted pie worked great, but my many 'need for root apps' did not , so back to oreo for me . Just my 2 cents!! Good luck.
hammered58 said:
I have no answers, but as u can see a rooted pie is problematic, hence the many people reverting back to oreo and or nougat, but some people somehow make it work. Not me I could not downgrade quick enough after rooting, unrooted pie worked great, but my many 'need for root apps' did not , so back to oreo for me . Just my 2 cents!! Good luck.
Click to expand...
Click to collapse
I found many working apps. The biggest problem is "substratum", especially when it comes to changing navbar buttons. But gravitybox is working, and I'm happy with it. Thanks for your help
My rooted Pie works fine, but I didn't install Substratum or Xposed.
Or wait a couple of months for them to tweak it a bit?
I only run Magik and not Xposed, not that it matters!
I'm not rooted, but I've been running R since the first public ßeta.
It's been the smallest update so far in a long time for Android. Very little has changed, compared to previous major version upgrades.
If you can root (and from what I read i think you can with Magisk), make a full backup and try it.
Sent from my Pixel 4 XL using Tapatalk
I don't really know what you'd be waiting for. I don't think a non-rooted person would notice much in terms of drawbacks. Magisk modules level, there were some issues... but I think most things are getting worked out. Xposed technically works, but more than half of my modules broke in a way that probably won't be fixed for a while. I still feel like I'm at a net-negative in terms of phone features. A11 brought little and broke a lot of my QoL tweaks that used Xposed.
I make no claims about SafetyNet as I use no apps that even check it.
I think A11 has been released formally by google and most of issues have been fixed or addressed.
I used magisk and edxposed. That's not a problem for me(I used Edxposed for fingerface only). Regarding of safetynet issue, it also has solution to make it pass by magisk modules and kernel side.
Until now, I'm happy with A11.
I ended up doing a full wipe and upgrade to Android 11 Oct 2020.
I have Magisk running with the SQL Lite mods for Google Pay and obviously I have root so I'm basically back where I was on Android 10.
I hadn't use Xposed yet and I don't know if I will yet. I was using Viper Audio mod but I don't know if I noticed a major difference, mostly I just stream bluetooth in my SUV.
So far, so good.
I tried it and reverted back to 10 - as mentioned didn't gain much but broke a lot. Even in stock form I can't get videos to load a subtitle file because of storage permissions and what not. A tweaked out install of 10 is faaaar nicer imo so that's what I'm running, probably until a new phone comes out sadly.
Kris Chen said:
I think A11 has been released formally by google and most of issues have been fixed or addressed.
I used magisk and edxposed. That's not a problem for me(I used Edxposed for fingerface only). Regarding of safetynet issue, it also has solution to make it pass by magisk modules and kernel side.
Until now, I'm happy with A11.
Click to expand...
Click to collapse
can i ask how you upgraded to A11? Im on 10 rooted with magisk and keep hearing mixed messages on upgrading. And is it necessary to wipe? I really don't want to.
A11 is not too bad, but as others have said little things here and there that break. Like for me I listen to SiriusXM app on mobile and for some odd reason it will stop playing all of a sudden and close. It's like the aggressive memory management kills the app for no reason. I even have battery optimization turned off and still does it.
Thinking about moving back to A10 from August, not really much I have to have to stick with latest A11 updates.
qman66 said:
can i ask how you upgraded to A11? Im on 10 rooted with magisk and keep hearing mixed messages on upgrading. And is it necessary to wipe? I really don't want to.
Click to expand...
Click to collapse
Flash the factory image, but remove the -w in the flash-all file. Then in Magisk Manager switch tot he beta channel and patch the boot image with that. Flash it and you're done.
GjorgiDxc said:
Flash the factory image, but remove the -w in the flash-all file. Then in Magisk Manager switch tot he beta channel and patch the boot image with that. Flash it and you're done.
Click to expand...
Click to collapse
You do know the latest version of magisk has a11 support?
GjorgiDxc said:
Flash the factory image, but remove the -w in the flash-all file. Then in Magisk Manager switch tot he beta channel and patch the boot image with that. Flash it and you're done.
Click to expand...
Click to collapse
Ok so I shouldn't install it via the ota? I keep getting the pop up to update every day.
Does using Magisk to dl / install the OTA, then patch the non-live and newly flashed partition, then finally rebooting not work?
When I was rooted that was always the easiest way.
And based upon the post 2 above this one, Magisk now supports A11 without ẞeta, right?
From Coral, with Tapatalk.
kdoggy said:
I ended up doing a full wipe and upgrade to Android 11 Oct 2020.
I have Magisk running with the SQL Lite mods for Google Pay and obviously I have root so I'm basically back where I was on Android 10.
I hadn't use Xposed yet and I don't know if I will yet. I was using Viper Audio mod but I don't know if I noticed a major difference, mostly I just stream bluetooth in my SUV.
So far, so good.
Click to expand...
Click to collapse
How is 11 for you going so far, I am thinking in reverting back to 10, battery is awful on 11
Hello everyone. Long time since I had an android device and I'm cutting the chains of my iPhone wanting to be de-Googled and de-Appled. I was running Lineage 17.1 from Microg and thought I had everything working on it until I started updating some software on my phone over the air. I rebooted and it went to bootloop. Since then I re-installed 17.1 and got things working again. I just upgraded to 18.1 and want to make sure it's all set up properly and won't have any errors.
Magisk says SafetyNet has an "SafetyNet API Error." "Basicintegrity, ctsProfile, evalType N/A." all in red when I check if it's working. I've done some digging, but want to make sure I do this right. I need to get the boot.img file from the original firmware. Should I get this from the oneplus website, or should I be looking for something else since I have Lineage? Can anyone provide the raw boot.img file for the OnePlus 7 Pro that I should use? I'm a little overwhelmed with all of the steps to extract it from the original firmware. Please and thanks for any help getting this phone set up the way I need it to work!
That error show when safety net API download was incomplete/corrupt, you can try to erase data from magisk manager and check safetynet again but with a better internet connection or use another magisk version like canary
And if you end in a bootloop for any magisk module just turn off your device and in your computer in a CMD/powershell/terminal window enter this command
adb wait-for-device shell magisk --remove-modules
Then connect and turn on your phone and automatically your phone will reboot with all your magisk modules disabled
Use magisk canary bro,,,
I sideloaded Canary and still get the red SafetyNet API error screen after opening it. Can someone direct me to a full tutorial on how Magisk works and what the modules do? I'm thinking I might need to do a full uninstall of Magisk and start over. If I do this will I lose all the data on the phone and have to start from scratch? Thanks for your help so far!
Well I've spent several hours researching tutorials and typing in codes via Terminal on my Mac and have gotten the phone restocked twice and working normal on stock OS, but after putting TWRP on it and then installing Lineage 18.1 it goes into a Lineage logo boot loop. What am I missing here?
It seems to me that TWRP is not compatible with Lineage. Sometimes when I rebooted the phone and was playing with the Recovery.IMG I saw the Lineage Recovery, then other times the TWRP would flash on and off in a boot loop. I have been careful about using the command " ./fastboot boot TWRP.img " and not "flash" TWRP, as would be the case for non a/b storage devices. On a couple occasions I could reboot with the Lineage Recovery.IMG and it would boot to startup, but if I rebooted to Recovery from the home screen, it would get stuck on TWRP.
I'm probably just missing something simple, but what might I be doing wrong? Is it the timing of installing TWRP and then installing Lineage in the same TWRP session?
This all stemmed from me wanting to get TWRP with Lineage 18.1 and getting Magisk and Microg working correctly for a "de-googled" phone with working apps. I'm frustrated, but will keep trying if I can get some direction. Thanks for your input.
-L
Lear31pilot said:
Well I've spent several hours researching tutorials and typing in codes via Terminal on my Mac and have gotten the phone restocked twice and working normal on stock OS, but after putting TWRP on it and then installing Lineage 18.1 it goes into a Lineage logo boot loop. What am I missing here?
It seems to me that TWRP is not compatible with Lineage. Sometimes when I rebooted the phone and was playing with the Recovery.IMG I saw the Lineage Recovery, then other times the TWRP would flash on and off in a boot loop. I have been careful about using the command " ./fastboot boot TWRP.img " and not "flash" TWRP, as would be the case for non a/b storage devices. On a couple occasions I could reboot with the Lineage Recovery.IMG and it would boot to startup, but if I rebooted to Recovery from the home screen, it would get stuck on TWRP.
I'm probably just missing something simple, but what might I be doing wrong? Is it the timing of installing TWRP and then installing Lineage in the same TWRP session?
This all stemmed from me wanting to get TWRP with Lineage 18.1 and getting Magisk and Microg working correctly for a "de-googled" phone with working apps. I'm frustrated, but will keep trying if I can get some direction. Thanks for your input.
-L
Click to expand...
Click to collapse
TWRP is not working for OOS11 or A11 ROMs using Oos11 blobs.
Lossyx said:
TWRP is not working for OOS11 or A11 ROMs using Oos11 blobs.
Click to expand...
Click to collapse
Got it! I'll go back to 17.1 Thanks!
Bump
Still trying to find a solution. I get fairly far into flashing the ROM, getting TWRP working and then end up stuck at Microg not letting me open the location menu. If only there were a guide with start to finish Lineage 17.1 or 18.1 with Microg and Magisk for my OnePlus 7 Pro. I find some guides, but there isn't one that encompasses everything that actually works. I'm going to try Lineage 18.1 with Microg built in and then flash Magisk.
Lear31pilot said:
Bump
Still trying to find a solution. I get fairly far into flashing the ROM, getting TWRP working and then end up stuck at Microg not letting me open the location menu. If only there were a guide with start to finish Lineage 17.1 or 18.1 with Microg and Magisk for my OnePlus 7 Pro. I find some guides, but there isn't one that encompasses everything that actually works. I'm going to try Lineage 18.1 with Microg built in and then flash Magisk.
Click to expand...
Click to collapse
I never installed lineage but i guess you can flash the ROM, change slots, then format data(this will erase all your stuff) and flash magisk then reboot into system
And for the safety net error yesterday was released a "fix" for that so try again
RokCruz said:
I never installed lineage but i guess you can flash the ROM, change slots, then format data(this will erase all your stuff) and flash magisk then reboot into system
And for the safety net error yesterday was released a "fix" for that so try again
Click to expand...
Click to collapse
Thank you. I'll have to address this at some point. I got the phone restocked, and flashed 18.1 Lineage on it again. Got all my apps and accounts back up on it. I'm just debating running Magisk again knowing that I'll likely have to start from scratch again. I wasn't able to get TWRP working correctly, so I left Lineage Recovery on, so it will be some time before I try going through this again. I'm going to do some research on what exactly is happening when I put recoveries and ROMs on different slots. Same goes for the Magisk. It's all quite new to me with the "slots" and what information has to go on which slot. I also need to find out how to backup my apps so if I re-flash a ROM, it's not so painful to get my data back on the phone.
At least I have a working phone without a Google login and most of the apps I want work. I'm only missing Lyft and my bank app. Again, thanks for the reply, and I'll look into this when I have some time to play with the phone again.
Lear31pilot said:
Thank you. I'll have to address this at some point. I got the phone restocked, and flashed 18.1 Lineage on it again. Got all my apps and accounts back up on it. I'm just debating running Magisk again knowing that I'll likely have to start from scratch again. I wasn't able to get TWRP working correctly, so I left Lineage Recovery on, so it will be some time before I try going through this again. I'm going to do some research on what exactly is happening when I put recoveries and ROMs on different slots. Same goes for the Magisk. It's all quite new to me with the "slots" and what information has to go on which slot. I also need to find out how to backup my apps so if I re-flash a ROM, it's not so painful to get my data back on the phone.
At least I have a working phone without a Google login and most of the apps I want work. I'm only missing Lyft and my bank app. Again, thanks for the reply, and I'll look into this when I have some time to play with the phone again.
Click to expand...
Click to collapse
TWRP can't boot in devices with OOS 11 blobs and encrypted data, for Magisk the only way I can imagine is using a patched boot.img.
Make a backup of your current boot.img(lineage) with apps like Franco kernel, then Patch it with magisk, then flash it in fastboot (fastboot flash boot boot.img)
if something woes wrong you can restore the backup from Franco kernel
RokCruz said:
TWRP can't boot in devices with OOS 11 blobs and encrypted data, for Magisk the only way I can imagine is using a patched boot.img.
Make a backup of your current boot.img(lineage) with apps like Franco kernel, then Patch it with magisk, then flash it in fastboot (fastboot flash boot boot.img)
if something woes wrong you can restore the backup from Franco kernel
Click to expand...
Click to collapse
Thanks RokCruz,
I'm going to get 18.1 back on with the LOS Recovery again. I'll try the boot patch method with the LOS boot.img from 18.1 for Magisk. I haven't tried the Franco kernel as I just now found out about it. I don't really need to do anything else fancy with the phone in terms of overclocking or underclocking. Does that kernel facilitate easier backups? I'm still learning a LOT about how Android works. It's been a steep learning curve. Fortunately, I can get myself out of any binds with a restock and fastboot!
Lear31pilot said:
Thanks RokCruz,
I'm going to get 18.1 back on with the LOS Recovery again. I'll try the boot patch method with the LOS boot.img from 18.1 for Magisk. I haven't tried the Franco kernel as I just now found out about it. I don't really need to do anything else fancy with the phone in terms of overclocking or underclocking. Does that kernel facilitate easier backups? I'm still learning a LOT about how Android works. It's been a steep learning curve. Fortunately, I can get myself out of any binds with a restock and fastboot!
Click to expand...
Click to collapse
Yes only for boot backups, I always made a backup of my boot.img of every OB just in case something goes wrong but i have never experienced that.
I personally prefer OOS, just install custom kernel and some mods like Cyberpunk 2077 theme, Riru Lsposed and a adbloker and that's all I need
RokCruz said:
Yes only for boot backups, I always made a backup of my boot.img of every OB just in case something goes wrong but i have never experienced that.
I personally prefer OOS, just install custom kernel and some mods like Cyberpunk 2077 theme, Riru Lsposed and a adbloker and that's all I need
Click to expand...
Click to collapse
I'm trying to de-google. Can I de-google on OOS? Most stock ROMs require a google login.
Lear31pilot said:
I'm trying to de-google. Can I de-google on OOS? Most stock ROMs require a google login.
Click to expand...
Click to collapse
I guess you can, just use a debloater
But it's better to install HydrogenOS just disable Chinese apps, install micro g and it's complements and you can run any Google dependant app, safety net passes without problems too.
I installed hydrogen and it runs smoothly but Cyberpunk isn't available for it so I reinstalled OOS
RokCruz said:
I guess you can, just use a debloater
But it's better to install HydrogenOS just disable Chinese apps, install micro g and it's complements and you can run any Google dependant app, safety net passes without problems too.
I installed hydrogen and it runs smoothly but Cyberpunk isn't available for it so I reinstalled OOS
Click to expand...
Click to collapse
Thanks for the tip about Hydrogen. I'll do some research on that. And thanks for getting back so quickly. The Android community really has some great people. Happy to be apart of it!
So
Lear31pilot said:
Thanks for the tip about Hydrogen. I'll do some research on that. And thanks for getting back so quickly. The Android community really has some great people. Happy to be apart of it!
Click to expand...
Click to collapse
So at the end of the day, I ended up with HydrogenOS 11 and have F-Droid and Aurora Store installed and working fine. I didn't/don't need Magisk or MicroG since HOS apparently is OK'd by google and all of my apps work.
So this worked perfectly for me. I have a fully functional OS and no Google sign-in needed. I did as you said and just deleted the Chinese bloat apps. I can't manage to get rid of the "Market" app though.
Lyft works and all of my location requiring apps like Waze work as well. Thanks for pointing me in the right direction.
Question: Will OxygenOS work the same without a google login? If so, what would be the advantage of HOS vs OOS? HOS 11 has an entire section devoted to a Google login for different services. I left it blank, but just wondering what the difference would be on OOS.
Lear31pilot said:
So
So at the end of the day, I ended up with HydrogenOS 11 and have F-Droid and Aurora Store installed and working fine. I didn't/don't need Magisk or MicroG since HOS apparently is OK'd by google and all of my apps work.
So this worked perfectly for me. I have a fully functional OS and no Google sign-in needed. I did as you said and just deleted the Chinese bloat apps. I can't manage to get rid of the "Market" app though.
Lyft works and all of my location requiring apps like Waze work as well. Thanks for pointing me in the right direction.
Question: Will OxygenOS work the same without a google login? If so, what would be the advantage of HOS vs OOS? HOS 11 has an entire section devoted to a Google login for different services. I left it blank, but just wondering what the difference would be on OOS.
Click to expand...
Click to collapse
Market can be disabled if my mind serve me right, OOS could end in a bootloop if we remove all Google apps so it's better not to do that.
I never see that section, I only installed OB1 and OB2 and never see that.
And remember you need to install magisk in order to pass safetynet.
RokCruz said:
Market can be disabled if my mind serve me right, OOS could end in a bootloop if we remove all Google apps so it's better not to do that.
I never see that section, I only installed OB1 and OB2 and never see that.
Click to expand...
Click to collapse
Looks like I'm denied the ability to disable the Market App.
Photo's attached for the Google settings I have available on HOS 11.
Also unable to make the microphone work in the keyboard for voice to text, but I have a feeling I won't be able to make that work without logging in to Google. Currently looking for some workarounds.
What will passing Safetynet allow me to do that I'm not already able to do now? Use banking apps and "tap to pay" type apps? I haven't found my bank app on the Aurora Store just yet. "US Bank" if it makes a difference.
I'll continue to play with this OS, but so far, it seems the easiest to get working right from the get-go.