Related
So I have a Starmobile Quest which is a local smartphone and I rooted it using a chinese rooting program called iroot, formerly vroot, as suggested by people using the same phone. At first the superuser app(which is a Chinese one) is working fine and I could use apps requiring root access but suddenly, something happened and now it won't give root access to any of the apps. I think, maybe root was somehow removed, and downloaded the root checker app and when I ran it, it told me that I wasn't rooted.
So I unrooted my phone using iroot and it was successful and again rooted it which was again successful. I go and run root checker again and I was surprised to see that I wasn't rooted. From there I repeated the unrooting and rooting process several times and still nothing. What I did notice was that whenever iroot was checking whether my phone was rooted, a pop up would appear on my phone which is from the superuser app asking for permission to give "shell" root access and I would always say yes.
I believe that my phone is actually rooted but the superuser app isn't promting me for root access whenever I use apps that require root, plus there is no log saved except for the "shell" one. I tried changing root access manager app to supersu and when I run it it tells me that it needs to update su binary. I click yes and use the normal method(I don't have cwm) and it tells me it's installing but after awhile I receive an error saying "installation failed. try rebooting.". I reboot my phone and try updating again and it still fails.
I tried everything the internet threw at me, reroot, factory reset, clear data, clear cache, etc and nothing's working. Can someone help me here?
Note: I can't find a stock/custom rom for my device. So flashing roms isn't an option for me.
Bump.
have you tried to flash another version of superuser?
Crom4rtie said:
have you tried to flash another version of superuser?
Click to expand...
Click to collapse
How do I do that?
black_fire21 said:
How do I do that?
Click to expand...
Click to collapse
go to your recovery and go to install zip ..choose your zip ..or just download supersu from the playstore
Crom4rtie said:
go to your recovery and go to install zip ..choose your zip ..or just download supersu from the playstore
Click to expand...
Click to collapse
Do you need a custom recovery for that? Because the model of the phone doesn't have a custom recovery yet.
Also, I tried to install supersu from the play store and it didn't work.
black_fire21 said:
Do you need a custom recovery for that? Because the model of the phone doesn't have a custom recovery yet.
Also, I tried to install supersu from the play store and it didn't work.
Click to expand...
Click to collapse
yes you need a custom recovery...but if the su from the playstore didn´t work then will this also not work
Crom4rtie said:
yes you need a custom recovery...but if the su from the playstore didn´t work then will this also not work
Click to expand...
Click to collapse
Damn it. I guess I'll have to wait till they make a stock rom which I think isn't gonna happen since it's been half a year since the phone is released and there hasn't been any development.
Last question, Is it possible to flash your phone using a computer?
black_fire21 said:
Damn it. I guess I'll have to wait till they make a stock rom which I think isn't gonna happen since it's been half a year since the phone is released and there hasn't been any development.
Last question, Is it possible to flash your phone using a computer?
Click to expand...
Click to collapse
Yes absolutely. Just note that there are no rooting apps on the Play Store. Simply downloading SuperSU or Superuser will NOT root your phone. You need to be rooted first, and if the SuperSU or Superuser app isn't automatically installed, then once you root you can install SuperSU or Superuser to manage apps that require root.
Popular methods of rooting include z4root, framaroot, MTKTools and iroot (or vroot)
Z4root and framaroot are both android applications which you will need to get from their sites or XDA (just run a search). MTKtools and iroot/vroot are computer applications and use ADB. MTKTools can also create a custom recovery for your device, though I don't remember the process too well.
Once you're rooted you will either have your Superuser app installed or you'll have to install it yourself (I personally prefer SuperSU). I also recommend installing busybox as well.
Hope that helps.
Don't forget to hit the thanks button if I helped you~
SeraphSephiroth said:
Yes absolutely. Just note that there are no rooting apps on the Play Store. Simply downloading SuperSU or Superuser will NOT root your phone. You need to be rooted first, and if the SuperSU or Superuser app isn't automatically installed, then once you root you can install SuperSU or Superuser to manage apps that require root.
Popular methods of rooting include z4root, framaroot, MTKTools and iroot (or vroot)
Z4root and framaroot are both android applications which you will need to get from their sites or XDA (just run a search). MTKtools and iroot/vroot are computer applications and use ADB. MTKTools can also create a custom recovery for your device, though I don't remember the process too well.
Once you're rooted you will either have your Superuser app installed or you'll have to install it yourself (I personally prefer SuperSU). I also recommend installing busybox as well.
Hope that helps.
Don't forget to hit the thanks button if I helped you~
Click to expand...
Click to collapse
So how do I do that?
Hello my buddy so I 've read your thread, there are many apps to do root like root master, framaroot, towel root, towelpieroot. And the way to install super su is doing again the root. And after to install it again.
These apps to do root.
YAMALILLO JR said:
These apps to do root.
Click to expand...
Click to collapse
Okay so some of those do. But not all are supported anymore.
---------- Post added at 04:47 AM ---------- Previous post was at 04:11 AM ----------
black_fire21 said:
So how do I do that?
Click to expand...
Click to collapse
So MTKTools can be found scattered all over XDA, and Framaroot has a dedicated thread (which I cannot link right now as I am on my phone). If memory serves, Jellybean and below had Dev options enabled by default. If not, go to settings -> About Device and tap on the build number several times until your dev options are enabled. Then simply enable USB debugging. When you plug in your device you may need to authenticate your PC to use the Debug bridge. Just hit accept. (I'm sure that you were aware of how to enable ADB but I felt I had to explain anyway)
I assume you have the ADB drivers for your device, but if not, there is a naked USB driver installer floating around XDA (I really would only trust XDA with stuff like this)
With ADB enabled you can use the iroot and MTKTools PC applications. Both are generally straightforward but don't hesitate to ask me if you have a question.
With the APK apps you can get from XDA and abroad, you can root the device somewhat easily.
Framaroot (last time I used it) has four options for rooting (latest version is 1.9.3) you will see all info you need on that thread.
Z4 root I do not recommend. It is somewhat outdated now, though you might want to try it as a last resort
Towelroot is fairly simple as well. Simply download and run the app and you'll either get root or you won't.
My personal recommendations are MTKTools for a pc toolkit (seeing as it can compile a custom recovery too, which it did for my Lenovo S6000)
For apk rooting, I suggest Framaroot. I've never had any problems with it thus far.
I hope that explained it enough but if not, don't hesitate to ask questions. After all, you never learn if you don't ask ^-^
Nevermind guys. I downloaded a bunch of rooting programs and tried them. Root Genius worked and now I have root access. Thanks for replying to this thread.
ReInstall SuperSU and check with Android Terminal Emulator.
Ok dudes just i share this thread, cuz i like to help other dudes that they are juniors or they're beginning .
I'm running 47A from here:
http://forum.xda-developers.com/ver...t/vs985-46a-stock-flashable-firmware-t3304365
It's got systemless root, I'm using SuperSU and I have TWRP installed. No xposed.
I really don't want to use xposed/magisk and I'm probably willing to lose root (would be nice if it was temporary vs permanent).
If I uncheck enable superuser in SuperSU and reboot, Android Pay still doesn't work.
So what exactly do I need to do in order to get Android Pay working?
lexluthor said:
I'm running 47A from here:
http://forum.xda-developers.com/ver...t/vs985-46a-stock-flashable-firmware-t3304365
It's got systemless root, I'm using SuperSU and I have TWRP installed. No xposed.
I really don't want to use xposed/magisk and I'm probably willing to lose root (would be nice if it was temporary vs permanent).
If I uncheck enable superuser in SuperSU and reboot, Android Pay still doesn't work.
So what exactly do I need to do in order to get Android Pay working?
Click to expand...
Click to collapse
I'm not rooted (anymore), but with bumped TWRP and SuperSU, apparently you can work around this. It appears PokeMon GO is blocking rooted users due to people spoofing their GPS location via Xposed modules, etc. This article explains how to flash something called Magisk that apparently works for both Pokemon GO as well as Android Pay. Again, I'm not rooted so I have no idea if this will work or not, but he lays out the instructions pretty well. I believe that since you are already rooted and bumped with TWRP, and no Xposed, you just need to obtain Magisk and flash from within TWRP.
http://www.androidpolice.com/2016/09/11/guide-play-pokemon-go-0-37-rooted-android-magisk/
Hope this helps. I just happen to come across this article in my Feedly feed and remembered reading your post, so hopefully this helps you.
Let us know!
iBolski said:
I'm not rooted (anymore), but with bumped TWRP and SuperSU, apparently you can work around this. It appears PokeMon GO is blocking rooted users due to people spoofing their GPS location via Xposed modules, etc. This article explains how to flash something called Magisk that apparently works for both Pokemon GO as well as Android Pay. Again, I'm not rooted so I have no idea if this will work or not, but he lays out the instructions pretty well. I believe that since you are already rooted and bumped with TWRP, and no Xposed, you just need to obtain Magisk and flash from within TWRP.
Hope this helps. I just happen to come across this article in my Feedly feed and remembered reading your post, so hopefully this helps you.
Let us know!
Click to expand...
Click to collapse
Hi iBolski,
Did you mean to include a link to an article about installing Magisk with an Verizon LG G3?
I've been looking for a way to install a stock unrooted rom for days but have been coming up short. Magisk would be ideal but I can't seem to find any threads that have a stock (unrooted) firmware image or a guide on how to unroot a pre-rooted firmware. I wish a tutorial specifically for a Bumped VS985 existed to set up a stock firmware or other ROM with Magisk because I have been having trouble piecing information together and am nervous about causing problems with my phone!
If anyone else has a Bump'd VS985 Verizon LG G3 with TWRP installed that is either unrooted or have Magisk running successfully with Android Pay or Pokemon GO, please let us know how you did it!
Thanks!!
EDIT: I just noticed that you yourself are running stock unrooted 46A iBolski... do you have TWRP installed or are you fully stock and accepted an OTA? If TWRP, does Android Pay or Pokemon Go work for you? And how'd ya get to where you are?
eagle132 said:
Hi iBolski,
Did you mean to include a link to an article about installing Magisk with an Verizon LG G3?
I've been looking for a way to install a stock unrooted rom for days but have been coming up short. Magisk would be ideal but I can't seem to find any threads that have a stock (unrooted) firmware image or a guide on how to unroot a pre-rooted firmware. I wish a tutorial specifically for a Bumped VS985 existed to set up a stock firmware or other ROM with Magisk because I have been having trouble piecing information together and am nervous about causing problems with my phone!
If anyone else has a Bump'd VS985 Verizon LG G3 with TWRP installed that is either unrooted or have Magisk running successfully with Android Pay or Pokemon GO, please let us know how you did it!
Thanks!!
EDIT: I just noticed that you yourself are running stock unrooted 46A iBolski... do you have TWRP installed or are you fully stock and accepted an OTA? If TWRP, does Android Pay or Pokemon Go work for you? And how'd ya get to where you are?
Click to expand...
Click to collapse
Sorry about forgetting the link. I updated my previous reply with the article in question.
As to your answer, I do not have TWRP installed. I do have all the official OTAs applied.
iBolski said:
Sorry about forgetting the link. I updated my previous reply with the article in question.
As to your answer, I do not have TWRP installed. I do have all the official OTAs applied.
Click to expand...
Click to collapse
Thanks for updating with the link. I did see that guide but am unsure about how to handle it with BUMP and what ROMs it works with.
If anyone else has a stock unrooted ROM or working Magisk with their TWRP/BUMP'd G3... please let us know!
eagle132 said:
Thanks for updating with the link. I did see that guide but am unsure about how to handle it with BUMP and what ROMs it works with.
If anyone else has a stock unrooted ROM or working Magisk with their TWRP/BUMP'd G3... please let us know!
Click to expand...
Click to collapse
As a follow up to my own post, I was able to pass the SafetyNet check (I used SafetyNet Helper from the Play Store to check) on my CloudyG3 2.5 LG G3 VS985. This was not without it's negatives however (no Xposed or root).
I simply flashed the Xposed Uninstaller and uninstalled the app, then from within the SuperSU app settings selected the option to permanently unroot. I did of course make a nandroid backup before doing this so restoring will not be an issue, but I do now get a green screen / pass to SafetyNet which should mean Android Pay and Pokemon Go will work.
eagle132 said:
As a follow up to my own post, I was able to pass the SafetyNet check (I used SafetyNet Helper from the Play Store to check) on my CloudyG3 2.5 LG G3 VS985. This was not without it's negatives however (no Xposed or root).
I simply flashed the Xposed Uninstaller and uninstalled the app, then from within the SuperSU app settings selected the option to permanently unroot. I did of course make a nandroid backup before doing this so restoring will not be an issue, but I do now get a green screen / pass to SafetyNet which should mean Android Pay and Pokemon Go will work.
Click to expand...
Click to collapse
Did you try Magisk at all? I am on Jasmine ROM (Android 5.1.1) and would love a way to still have Root & Xposed, but be able to pass SafetyNet for PokemonGO and Wallet
Question on XDABBEB's VS985 ROM
Considering that this phone will probably see no more OTA's, I'm ready to go back to root, but I don't want to break Android Pay. Also, I'm not going to use Kingroot. Don't trust it. So, I'll TOT back to 10B to flash XDABBEB VS985 ROM. But i have some questions regarding it (I haven't ran a custom ROM in almost a year).
Does anyone know if removing SuperSU from XDABBEB VS985 ROM will allow Android Pay to work? Curious if so, otherwise, I'll probably just stick with my stock 48A unrooted phone in order to keep Android Pay.
I also miss TiBu as my backup tool. Yes, LG Backup is nice and all, but TiBu is so much more flexible, including the scheduled backups that I like to do as well as pushing to my Google Drive for backing up the files. Also, TiBu doesn't store it in one giant backup file. I really wish LG Backup would store each app as a separate file, rather than one giant, humongous file. Also, if I do upgrade to a new phone that's not LG, LG Backup won't work for me, so I'll need TiBu (and of course, I have to make sure the new phone is rootable).
Thanks!
While I have not tried this (I plan to try magisk later this week) supposedly Reddit says we can use this bump script after applying magisk in order to make everything will boot. I'm reading mixed comments about if/which certain bootloader is needed to have this work (KitKat vs Lollipop vs Marshmallow) or which ROM to start with as a base (though I saw CM 13 mentioned). If anyone tries this, let me know. I'll post my results in the coming days.
Huge thanks to vadosnake for discovering this !
It's been a wait of 2 years, and King root has finally achieved root on this device. This method was tested on the Lollipop firmware, and others have said it works on KitKat as well. To root the G850A, follow these steps:
1.) Download the two APKs provided below, which we'll need for later
2.) Enable Unknown Sources by going to Settings, then Security, and the option should be right there
3.) Now install KingRoot 4.81. A message will pop up saying that the app is malicious, but just click "Install Anyway"
4.) Now enter the King root app and click Root. The phone will reboot, but that is normal. Go back into the app again and the process should continue until it's complete. Voila, your phone is now rooted. However, we will be replacing KingRoot with SuperSU.
5.) Install the second APK called SuperSume. After it's done, click the big green button, give it root access, and it will replace KingRoot with SuperSU in 1 minute.
6.) Go into the Play Store and update SuperSU. After it's done updating, go into the app and it will pop up with a message saying to update the binaries. Click continue then "Normal". DO NOT CLICK TWRP/CWM, OR IT WILL SOFTBRICK YOUR DEVICE.
7.) After that., you're done. You now have root with SuperSU.
Please make sure to show this to AT&T Galaxy Alpha users. Especially developers, so we can get some roms
Did anyone try this? Why does King Root need internet access to root? I'm afraid to turn on the internet in case it tries to steal data.
PopTartKing said:
Huge thanks to vadosnake for discovering this !
It's been a wait of 2 years, and King root has finally achieved root on this device. This method was tested on the Lollipop firmware, and others have said it works on KitKat as well. To root the G850A, follow these steps:
1.) Download the two APKs provided below, which we'll need for later
2.) Enable Unknown Sources by going to Settings, then Security, and the option should be right there
3.) Now install KingRoot 4.81. A message will pop up saying that the app is malicious, but just click "Install Anyway"
4.) Now enter the King root app and click Root. The phone will reboot, but that is normal. Go back into the app again and the process should continue until it's complete. Voila, your phone is now rooted. However, we will be replacing KingRoot with SuperSU.
5.) Install the second APK called SuperSume. After it's done, click the big green button, give it root access, and it will replace KingRoot with SuperSU in 1 minute.
6.) Go into the Play Store and update SuperSU. After it's done updating, go into the app and it will pop up with a message saying to update the binaries. Click continue then "Normal". DO NOT CLICK TWRP/CWM, OR IT WILL SOFTBRICK YOUR DEVICE.
7.) After that., you're done. You now have root with SuperSU.
Please make sure to show this to AT&T Galaxy Alpha users. Especially developers, so we can get some roms
Click to expand...
Click to collapse
cqdiep said:
Did anyone try this? Why does King Root need internet access to root? I'm afraid to turn on the internet in case it tries to steal data.
Click to expand...
Click to collapse
It needs Internet access to search in their database for a root solution.
I got SuperSU to install, but it can't update the binaries. It says "Installation failed! Please reboot and try again." after trying to update the binaries. The Root Checker app did confirm that it was rooted.
PopTartKing said:
It needs Internet access to search in their database for a root solution.
Click to expand...
Click to collapse
cqdiep said:
I got SuperSU to install, but it can't update the binaries. It says "Installation failed! Please reboot and try again." after trying to update the binaries. The Root Checker app did confirm that it was rooted.
Click to expand...
Click to collapse
For now, I tend to leave the app closed, and just wait until root prompts appear for root apps
Yeah, I'm doing that too.
PopTartKing said:
For now, I tend to leave the app closed, and just wait until root prompts appear for root apps
Click to expand...
Click to collapse
No Luck
I just ran the included 4.8.1 and online 5.0.1 versions, neither worked. So I tried the 4.8.1 a few times (including restarts) and the Super-SuMe anyway, but it didn't do anything past "Preparing environment" for 20 minutes.
Additional note, the 4.8.1 seems to have problems in general. After trying to root and failing, it'll continue using 80% of my cpu on some other processes within it's directory (mostly Schrodinger).
I'm running Android 5.0.2 (G850AUCU1BOC7), Kernel 3.4.0-4486597, Build LRX22G. It's the last update ATT gave us.
zyphuris55 said:
I just ran the included 4.8.1 and online 5.0.1 versions, neither worked. So I tried the 4.8.1 a few times (including restarts) and the Super-SuMe anyway, but it didn't do anything past "Preparing environment" for 20 minutes.
Additional note, the 4.8.1 seems to have problems in general. After trying to root and failing, it'll continue using 80% of my cpu on some other processes within it's directory (mostly Schrodinger).
I'm running Android 5.0.2 (G850AUCU1BOC7), Kernel 3.4.0-4486597, Build LRX22G. It's the last update ATT gave us.
Click to expand...
Click to collapse
Same, tried both 4.8.1 and 5.0.1, neither worked. Same android and baseband version as yours.
Thanks so much for this. I'm curious exactly which version of Lollipop on the g850a this was tested and working on? Was it specifically 5.0.1 or 5.0.2 something like that? I just want to make sure I can follow it exactly so it works.
Root access was lost after a couple of days. I'm on 4.4.4.
cqdiep said:
Yeah, I'm doing that too.
Click to expand...
Click to collapse
Well this is strange, I followed this exact tutorial about 1 month ago and everything worked fine, now the app just freezes and after 5 minutes gives off a "Root Fail" message. I'm still running v4.8.1 on the app and still running on the KitKat firmware. This makes no sense at all.
Edit: The phone is no longer supported by Kingroot
Hey guys, sorry for not replying, my internet has been down for the past two weeks . It seems that everyone is having problems keeping root after a while. I might not be a developer, but here's my advice: Once root is obtained, do what you want to do (ie. change emojis or install ViperAudio), then don't touch the SuperSU app until some more skilled developers put this root to full use . I'm sorry for not being more useful, but I just want everyone to know that this device isn't dead. What we need right now is something like SafeStrap for some some-what custom roms.
Any one having issue getting this to work?
PopTartKing said:
Hey guys, sorry for not replying, my internet has been down for the past two weeks . It seems that everyone is having problems keeping root after a while. I might not be a developer, but here's my advice: Once root is obtained, do what you want to do (ie. change emojis or install ViperAudio), then don't touch the SuperSU app until some more skilled developers put this root to full use . I'm sorry for not being more useful, but I just want everyone to know that this device isn't dead. What we need right now is something like SafeStrap for some some-what custom roms.
Click to expand...
Click to collapse
Yeah, Kingroot pulled support from it after people started using supersu-me to get supersu on their devices instead of kingroot. Well, to me, it sounds like a jealousy problem on Kingroots end. It's not like everyone is buying the pro version of the app. Their main source of money is ad revenue. They also pulled support from the Galaxy S5 and many other devices mainly because of people using supersu-me. Kingroot has got to get the stick that is in it's butt right now out ASAP. A 'friend' of mine literally sold his S5 because it couldn't be rooted anymore, and i'm thinking about selling my G850A because it can't be rooted anymore.
Just to clarify this, there's absolutely no way on the internet that the G850A can be rooted, ever?
chocolatewings said:
Just to clarify this, there's absolutely no way on the internet that the G850A can be rooted, ever?
Click to expand...
Click to collapse
Not anymore. It only had root for like 1 month then Kingroot removed support, you can blame them. Unless someone is exploit something so we can have root back, there is no way to root this phone anymore. I know, it sucks, just like the Kingroot developers, but that's just life.
cqdiep said:
Root access was lost after a couple of days. I'm on 4.4.4.
Click to expand...
Click to collapse
Hi
Im doing that and 100% complete but i check root by root check not request from super user
Solution found!
Hi guys. I think I found the trick. Just disable Internet connection (Mobile data and WiFi) just before lunching kingroot app this would evade the app from "searching the best root solution" which is "nothing found".
I used the exact same files uploaded in the OP and it works great, including the supersume part.
Good luck.
I'm very lucky to root my device. waited One year and 4 months and got the fruit of patience. Now I love my device. I have patched Tethering Provision. Now I can easily open hotspot.. no need of foxfi etc... ? Congratulations to those who got there device ROOOOTED.. ?
babarjoya said:
I'm very lucky to root my device. waited One year and 4 months and got the fruit of patience. Now I love my device. I have patched Tethering Provision. Now I can easily open hotspot.. no need of foxfi etc... Congratulations to those who got there device ROOOOTED..
Click to expand...
Click to collapse
Salam. Babar bhai hamen bhi bata den k kaise root kar lia ap ne. please
Hello everybody,
There has been an confusing about the in-build root of LineAgeOS. Wether is is there or not. Well it's only available for ADB. Anyway, I have been browsing the web for a solution and I've come across this site from the Lineage Team that let you download a add-on for Lineage that enables the built-in root.
NOTE THAT THIS IS NOT CHAINFIRE'S SUPERSU ZIP.
If you want SUPERSU go to this link:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
So I'm not gonna hold you any further.
Here is the link to the site.
DOWNLOAD:
https://download.lineageos.org/extras
Have fun with Root on your unofficial Lineage ROMs and Lineage based ROMs:good:
Greetings,
Paulo
Another method to get root access is Magisk. I think the system-less root will work nicely with app like Snapchat.
serdotlinecho said:
Another method to get root access is Magisk. I think the system-less root will work nicely with app like Snapchat.
Click to expand...
Click to collapse
Thats very true. Thanks for the tip:good:
is there a root script i can use for verizon lg g3 for LOS root? supersu binary update caused my handset to lose root and will only bootloop now. :good: in advance
Why-Fi said:
is there a root script i can use for verizon lg g3 for LOS root? supersu binary update caused my handset to lose root and will only bootloop now. :good: in advance
Click to expand...
Click to collapse
Do a full unroot in SuperSU, it will reboot automatically, just in case reboot again, then install the Root add-on with TRWP or any custom recovery.
Report back if it works:good:
Why-Fi said:
is there a root script i can use for verizon lg g3 for LOS root? supersu binary update caused my handset to lose root and will only bootloop now. :good: in advance
Click to expand...
Click to collapse
That's no even related to J5 or this addon!
Try Magisk or phh's SuperUser.
American_Jesus said:
That's no even related to J5 or this addon!
Try Magisk or phh's SuperUser.
Click to expand...
Click to collapse
This thread is not only for J5. I made this so that everyone could see it.
paulo boë said:
This thread is not only for J5. I made this so that everyone could see it.
Click to expand...
Click to collapse
i really appreciate it. i've been getting sideways comments from quite a few individuals concerning this. to elaborate, since the binary update i have absolutely no access to my handset other than with adb shell via a program developed for lg g3 called dp root. the program does not detect root, and since i am boot looping into a lineage os based rom, i figured i would stay away from supersu, since that is the problem. i have to run script into the adb shell to force root. that is the only w ay i will be able to gain root. i cannot boot into recovery since my root got lost. the shell detects the vs985 and also detects android 7.1.1. the rom is octN, which is LOS based.
and to the individual that got nasty because i don't have a j5, i have been trying for days now to find a solution, and if this was j5 specific, which i saw that it was not, i would have looked elsewhere so as to avoid offending anyone for posting on the "wrong thread".
Like magisk hide, iSU can disable or hide the cm-su. Should work with app like Snapchat and Pokemon Go.
Why-Fi said:
i really appreciate it. i've been getting sideways comments from quite a few individuals concerning this. to elaborate, since the binary update i have absolutely no access to my handset other than with adb shell via a program developed for lg g3 called dp root. the program does not detect root, and since i am boot looping into a lineage os based rom, i figured i would stay away from supersu, since that is the problem. i have to run script into the adb shell to force root. that is the only w ay i will be able to gain root. i cannot boot into recovery since my root got lost. the shell detects the vs985 and also detects android 7.1.1. the rom is octN, which is LOS based.
and to the individual that got nasty because i don't have a j5, i have been trying for days now to find a solution, and if this was j5 specific, which i saw that it was not, i would have looked elsewhere so as to avoid offending anyone for posting on the "wrong thread".
Click to expand...
Click to collapse
I guess that is a no that it didnt work Cant you at all boot into recovery?
paulo boë said:
I guess that is a no that it didnt work Cant you at all boot into recovery?
Click to expand...
Click to collapse
no I can't. all I can get is:
1. firmware update screen but the code says it is a g2
or
2.official stock recovery, where, from there it would boot into recovery from factory data reset, but it bypasses that and goes to lg splash screen then boot loop for octos boot screen.
is there a way to bump with adb shell?
here is exactly what happened...
The actions that led to the boot loop were as follows:
1. clean install of rom, gapps, supersu, mr. bump through twrp (clean as in wipe system, data, cache, dalvik)
2. installed all apps backed up to google account through playstore.
3. reset all permissions.
4. verified root and busybox install through root checker app.
5. root checker suggested installation of supersu app for proper functionality
6. installed supersu pro via playstore
7. supersu pro notified of a binary update requirement, binary was updated.
8. reboot from update led to boot loop.
I believe that updating the binary through the supersu pro app without bump caused loss of root, hence the inability to access recovery. I have tried to return to stock with lg software via .tot method. The software doesn't recognize the device. It does recognize a device i have with a bad esn, so the drivers are correct. I can put the device in download mode, but the id that it gives for the device in the box at the bottom of the screen is consistent with lg g2.
I have adb shell access to the device, which is recognized as vs985 with Android 7.1.1., no root detected (dp root lg g3). What i don't have is working knowledge of adb commands and scripts.
I have posted on the supersu thread as well, but as of yet, no one has helped. I get the same "wrong thread go post somewhere else." I figured I might be able to force los root, since it doesn't need bump. I just don't know scripts and can't find any that I would be able to use.
Why-Fi said:
no I can't. all I can get is:
1. firmware update screen but the code says it is a g2
or
2.official stock recovery, where, from there it would boot into recovery from factory data reset, but it bypasses that and goes to lg splash screen then boot loop for octos boot screen.
is there a way to bump with adb shell?
here is exactly what happened...
The actions that led to the boot loop were as follows:
1. clean install of rom, gapps, supersu, mr. bump through twrp (clean as in wipe system, data, cache, dalvik)
2. installed all apps backed up to google account through playstore.
3. reset all permissions.
4. verified root and busybox install through root checker app.
5. root checker suggested installation of supersu app for proper functionality
6. installed supersu pro via playstore
7. supersu pro notified of a binary update requirement, binary was updated.
8. reboot from update led to boot loop.
I believe that updating the binary through the supersu pro app without bump caused loss of root, hence the inability to access recovery. I have tried to return to stock with lg software via .tot method. The software doesn't recognize the device. It does recognize a device i have with a bad esn, so the drivers are correct. I can put the device in download mode, but the id that it gives for the device in the box at the bottom of the screen is consistent with lg g2.
I have adb shell access to the device, which is recognized as vs985 with Android 7.1.1., no root detected (dp root lg g3). What i don't have is working knowledge of adb commands and scripts.
I have posted on the supersu thread as well, but as of yet, no one has helped. I get the same "wrong thread go post somewhere else." I figured I might be able to force los root, since it doesn't need bump. I just don't know scripts and can't find any that I would be able to use.
Click to expand...
Click to collapse
Im sorry to disappoint you. But I cannot find any scripts or anything actually to help you. Im not new to all of this but im still learning. I have been searching Google for a couple of hours but i have found nothing concerning your problem.
paulo boë said:
Im sorry to disappoint you. But I cannot find any scripts or anything actually to help you. Im not new to all of this but im still learning. I have been searching Google for a couple of hours but i have found nothing concerning your problem.
Click to expand...
Click to collapse
that in itself is a big help. thank you. it means a lot. have a good one, brother.
Why-Fi said:
that in itself is a big help. thank you. it means a lot. have a good one, brother.
Click to expand...
Click to collapse
Thanks, you too:good:
paulo boë said:
Thanks, you too:good:
Click to expand...
Click to collapse
thanks for sharing.
this root addon has no user interface.
we cannot manage the apps which can be root granted/denied in later stages once u tick remember in the pop up
@paulo boë do you have any suggestion or idea how to get a manager or UI for CM root.
reversegear said:
thanks for sharing.
this root addon has no user interface.
we cannot manage the apps which can be root granted/denied in later stages once u tick remember in the pop up
@paulo boë do you have any suggestion or idea how to get a manager or UI for CM root.
Click to expand...
Click to collapse
Isnt there in the developer options an option to manage root? Otherwise i have no idea how to manage.
paulo boë said:
Isnt there in the developer options an option to manage root? Otherwise i have no idea how to manage.
Click to expand...
Click to collapse
I'm using RR nougat
Root options not available in developers option...
Anyway I'll search for something which does the job. I'll let u know if I find something
serdotlinecho said:
Another method to get root access is Magisk. I think the system-less root will work nicely with app like Snapchat.
Click to expand...
Click to collapse
pretty much I get same result on Magisk since if I need to bypass root check I just need to disable in built root or Magisk, since Magisk doesent pass Safety net.
So after having a metric f**k ton of issues trying to get a custom recovery to work on 6.0.1, I gave up trying to install a custom rom and eventually went back to stock unrooted. After updating to 7.0 and waiting a bit, I gave it another go and managed to get TWRP to work and rooted my phone. Now I'm looking to install a custom ROM and have a few questions.
Is there anything I should know before going in? Any prerequisites I need to get before/after flashing a custom ROM so certain features will work?
Can I use any custom ROM that is listed as compatible with 7.0/G925F? Or do I have to be more specific as to what version I get?
What should I keep an eye out for? Any features that are good/bad?
Anything else I should know?
As for my choices, it's currently between Nemesis and Noble. Anyone used either and care to share your experience? Any other recommendations?
ProdigyThirteen said:
So after having a metric f**k ton of issues trying to get a custom recovery to work on 6.0.1, I gave up trying to install a custom rom and eventually went back to stock unrooted. After updating to 7.0 and waiting a bit, I gave it another go and managed to get TWRP to work and rooted my phone. Now I'm looking to install a custom ROM and have a few questions.
Is there anything I should know before going in? Any prerequisites I need to get before/after flashing a custom ROM so certain features will work?
Can I use any custom ROM that is listed as compatible with 7.0/G925F? Or do I have to be more specific as to what version I get?
What should I keep an eye out for? Any features that are good/bad?
Anything else I should know?
As for my choices, it's currently between Nemesis and Noble. Anyone used either and care to share your experience? Any other recommendations?
Click to expand...
Click to collapse
The first and most important thing to do is make a backup. A nandroid backup is fine but make sure you back up your EFS folder. If this gets corrupted you will corrupt your IMEI and have no signal permanently. So backup efs and store somewhere safe like your pc.
I recommend doing full wipe before installing a custom ROM just so it's a clean install.
After that your pretty much good to go.
You can use any ROM that's compatible for your model only. So any G925F ROMs will work fine. Most support a number of models like G925F/I/V etc.
Most s6 edge custom ROMs are stable and have very few issues, and if there are issues then generally there are fixes for them.
Nemesis and Noble are both good stable ROMs. Also Omega ROM is a good choice. But my favourite that I used for over a year is CarHD ROM. It's customisation is endless.
One more is AlexisROM. Good ROM used for a while.
Hope this helps.
callumbr1 said:
snip
Click to expand...
Click to collapse
So after a painfully long download, I installed CarHD and I'm liking everything I see. My only issue is trying to get SafetyNet to pass. I've removed SuperSU, installed Magisk and its kernel and now whenever I check SafetyNet, it fails with "CTS profile mismatch". I've looked around on a few different threads about it and everything I've tried hasn't worked. Mostly because they revolve around MagiskHide, which isn't showing up for me.
My first thought is to completely uninstall magisk, go back to a stock kernel and start off fresh, but I'm not going to do that just yet as I wanted your opinion first. Is that the best thing to do or would it cause more harm than good?
And if it wasn't already obvious, yes I'm still pretty damn new to this, but I'm trying not to **** up as I quite like my phone working.
Edit: solved the MagiskHide not showing.. I'm an idiot and forgot it was under settings and not enabled by default.
ProdigyThirteen said:
So after a painfully long download, I installed CarHD and I'm liking everything I see. My only issue is trying to get SafetyNet to pass. I've removed SuperSU, installed Magisk and its kernel and now whenever I check SafetyNet, it fails with "CTS profile mismatch". I've looked around on a few different threads about it and everything I've tried hasn't worked. Mostly because they revolve around MagiskHide, which isn't showing up for me.
My first thought is to completely uninstall magisk, go back to a stock kernel and start off fresh, but I'm not going to do that just yet as I wanted your opinion first. Is that the best thing to do or would it cause more harm than good?
And if it wasn't already obvious, yes I'm still pretty damn new to this, but I'm trying not to **** up as I quite like my phone working.
Click to expand...
Click to collapse
You don't need any kind of custom kernel to use magisk, or at least you shouldn't. It should work perfectly fine with stock.
Try updating magisk manager app from xda labs and magisk hide should appear.
If it does then just enable magisk hide and hide all apps that require safety net, hide knox also if it's still on the ROM. Then you should pass.
If this fails I recommend to flash the ROM again, no need to wipe data and then choose magisk in aroma installer and flash again.
Let me know if you need help :good:
callumbr1 said:
You don't need any kind of custom kernel to use magisk, or at least you shouldn't. It should work perfectly fine with stock.
Try updating magisk manager app from xda labs and magisk hide should appear.
If it does then just enable magisk hide and hide all apps that require safety net, hide knox also if it's still on the ROM. Then you should pass.
If this fails I recommend to flash the ROM again, no need to wipe data and then choose magisk in aroma installer and flash again.
Let me know if you need help :good:
Click to expand...
Click to collapse
Fixed the MagiskHide issue, but simply enabling hide on the apps that I want to use doesn't work. I tried reinstalling the ROM as you said, but it never gave the option to choose Magisk over SuperSU. Then when I switched from SuperSU to Magisk, SuperSU was removed normally, but Magisk is installed and saying I don't have root access. Flashed Magisk kernel from CarHD as TWRP wasn't allowing install of Magisk with the other that came stock, then flashed Magisk again. Magisk saying I now have root access, but Magisk isn't installed and when I try to install it, the app crashes. Currently checking Magisk threads for a solution for that.
Tried reinstalling Magisk and clearning data/cache to no avail... I still have root access, but can't install Magisk through the manager.
Uninstalled Magisk, flashed stock kernel, re flashed magisk and now SafetyNet is passing, but still can't install Magisk through the Manager
ProdigyThirteen said:
Uninstalled Magisk, flashed stock kernel, re flashed magisk and now SafetyNet is passing, but still can't install Magisk through the Manager
Click to expand...
Click to collapse
If you have root access and safety net pass then I don't understand what you mean by can't install magisk through the app?
So you have magisk manager app installed?
callumbr1 said:
If you have root access and safety net pass then I don't understand what you mean by can't install magisk through the app?
So you have magisk manager app installed?
Click to expand...
Click to collapse
Yeah, the manager is installed, but when I open it, it says there is an update available and under status says Magisk is not installed, v130 is available. There is no option to enable Magisk hide or any other extras available for download.
Screenshot of magisk
ProdigyThirteen said:
Screenshot of magisk
Click to expand...
Click to collapse
It's the magisk manager app. You need to install the new one. Delete the one you currently have installed and download latest one from magisk Thread here or from xda labs.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Should look similar to this.
callumbr1 said:
It's the magisk manager app. You need to install the new one. Delete the one you currently have installed and download latest one from magisk Thread here or from xda labs.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Should look similar to this.
Click to expand...
Click to collapse
Tried to uninstall it, no option to. Downloaded something to uninstall system apps, tried to uninstall it, still there. Tried to install a new app over it, gave an error saying app already installed with same name.
ProdigyThirteen said:
Tried to uninstall it, no option to. Downloaded something to uninstall system apps, tried to uninstall it, still there. Tried to install a new app over it, gave an error saying app already installed with same name.
Click to expand...
Click to collapse
You should be able to uninstall it with titanium backup or any app to remove system app.
Infact you should be able to just remove it as you would remove any other app.
Use what you used before to remove it when it didn't go and then reboot and it should go. If not flash the uninstaller from magisk thread.
Then start again, if you flash the newest magisk from the thread on here then it also should install newest magisk manager app.
callumbr1 said:
You should be able to uninstall it with titanium backup or any app to remove system app.
Infact you should be able to just remove it as you would remove any other app.
Use what you used before to remove it when it didn't go and then reboot and it should go. If not flash the uninstaller from magisk thread.
Then start again, if you flash the newest magisk from the thread on here then it also should install newest magisk manager app.
Click to expand...
Click to collapse
No app that removes system apps can remove Magisk Manager it seems... TB says "Failed to locate the apk file", NoBloat Free says it removed it, but even after rebooting it's still there. Flashing the uninstall doesn't remove it either. I would manually uninstall through root explorer, but there's a risk I delete the wrong file and screw something else up.
Edit: Found Magisk Manger in root/system/app/magisk, backed it up, deleted it, rebooted, seems to be gone. Will try intalling new APK
Fixed it. Had to manually delete the apk, then installed the updated version and now it's showing as magisk is installed perfectly fine. Thanks for all the help.
Third and hopefully final edit: Getting kernel is not seandroid enforcing. Tried uninstalling magisk, flashing stock kernel, reinstalling magisk and still getting it. But it doesn't seem to be messing with anything, can still boot fine, safetynet is still passing so all looks pretty good.
callumbr1 said:
snip
Click to expand...
Click to collapse
No point starting a new thread when I can just ask here as it's a somewhat follow on question. I can't seem to get V4A to work. I've installed the module from Magisk, installed the APK, restarted my phone, loaded up the app and checked the driver just for it to say Status: Abnormal / Audio Format: Unsupported. Can't seem to find anything about a fix for it, been searching for about an hour, so either I'm blind or there's nothing on it (I'm betting it's the former).
When I open the app, I get a message prompting me to update/install the driver, despite it already being installed through Magisk. I've tried both the standard v2.5.0.5 apk and Nougat test fix, standard doesn't do anything and test fix has update/install prompt.
ProdigyThirteen said:
No point starting a new thread when I can just ask here as it's a somewhat follow on question. I can't seem to get V4A to work. I've installed the module from Magisk, installed the APK, restarted my phone, loaded up the app and checked the driver just for it to say Status: Abnormal / Audio Format: Unsupported. Can't seem to find anything about a fix for it, been searching for about an hour, so either I'm blind or there's nothing on it (I'm betting it's the former).
When I open the app, I get a message prompting me to update/install the driver, despite it already being installed through Magisk. I've tried both the standard v2.5.0.5 apk and Nougat test fix, standard doesn't do anything and test fix has update/install prompt.
Click to expand...
Click to collapse
Good stuff. As for the seandroid message on boot you can just ignore it. It's not an error and will stay but doesn't affect anything.
As for viper first thing to try is remove the currently installed app and remove it from magisk manager modules.
Install busybox.
Freeze sound alive with titanium backup (don't delete just freeze)
Then flash this through TWRP
https://mega.nz/#!CV5wQYSa!i-V1UvJ_Lh9YoZDPN9rUUXuJNgXWcXRlhBE83fYH7e8
After this if it doesn't work let me know and I'll tell you next steps.
callumbr1 said:
Good stuff. As for the seandroid message on boot you can just ignore it. It's not an error and will stay but doesn't affect anything.
As for viper first thing to try is remove the currently installed app and remove it from magisk manager modules.
Install busybox.
Freeze sound alive with titanium backup (don't delete just freeze)
Then flash this through TWRP
https://mega.nz/#!CV5wQYSa!i-V1UvJ_Lh9YoZDPN9rUUXuJNgXWcXRlhBE83fYH7e8
After this if it doesn't work let me know and I'll tell you next steps.
Click to expand...
Click to collapse
Tried that, still getting abnormal/unsupported.
ProdigyThirteen said:
Tried that, still getting abnormal/unsupported.
Click to expand...
Click to collapse
Now check that magisk module is enabled and the audio modification module is enabled.
You may also need a permissive kernel to get viper to work.
callumbr1 said:
Now check that magisk module is enabled and the audio modification module is enabled.
You may also need a permissive kernel to get viper to work.
Click to expand...
Click to collapse
Googling permissive kernel is just coming back with a bunch of threads saying get a terminal emulator, type su / setenforce 0. Tried that, trips safetynet and doesn't change Viper.
I feel like it's not changing viper because I need it to stick through reboots, enable it, then reboot, but it's not persistent. How would one go about making it stick?
And honestly, is viper really worth all this hassle?
ProdigyThirteen said:
Googling permissive kernel is just coming back with a bunch of threads saying get a terminal emulator, type su / setenforce 0. Tried that, trips safetynet and doesn't change Viper.
I feel like it's not changing viper because I need it to stick through reboots, enable it, then reboot, but it's not persistent. How would one go about making it stick?
And honestly, is viper really worth all this hassle?
Click to expand...
Click to collapse
You can try Hacker kernel
https://forum.xda-developers.com/ga...l-hacker-kernel-s6-universal-t3254487/page234
Or arter kernel
http://arter97.com/browse/exynos7420/kernel/22.0/g925fi/
As for is it worth it? In my opinion yes 100%.
It depends really if you like the stock effects enough. Personally I love music and love been able to customise it. It sounds 10000x better in my opinion.