Hey guys,
Recently, I have been trying to re-root my LG G2 VS980 that was returned to lollipop stock (LG Firmware). However, all the tools I knew that previously worked, (Ioroot, Towelroot, Stumproot, Kingoroot, etc..) did not work. After months of testing, I finally found one app that currently works called KingRoot.
As far as I know, it is the only root method that acutally still works after LG patched most of the exploits so I thought I would share the info with you guys in case some of you are still interested in rooting your G2.
Instructions:
1. Install Kingroot: http://kingroot.net/ (the APK doesn't work for the G2)
2. Go to settings in your phone and click the build number 7-10 times to enable Developer Options
3. Go to Developer Options and enable USB Debugging
4. plug the phone into your computer and launch the program. Make sure you see the USB Debugging card that will pop up on your phone.
Launch the program and allow the program to root your phone.
Sidenote: The only downside to the app is it is all in Korean but it is very easy to tell what it is asking due to excellent pictures
After you receive root, download the app RootChecker just to make sure.
To Install TWRP:
1. Instructions: Go to Play Store and type in the search window, "AUTOREC".
2. Select the correct variant: ex. VS980=Verizon etc...
3. Install the app.
4. Watch TWRP Install on your phone.
5. Reward yourself on your hard work with a pat on the back.
So that's it; A fast easy, and trouble free method on getting root and installing TWRP
Thanks for this. I recently acquired a G2, and will be trying this out tonight.
tribalartgod said:
Thanks for this. I recently acquired a G2, and will be trying this out tonight.
Click to expand...
Click to collapse
No problem. Have fun with your custom ROM of choice.
Can you share the setup files? I also need to re-root my Verizon phone. The kingroot ownload links looks dead
i downlaoded it from here. I have usb dev enabled. now what? http://kingroot-pc.en.uptodown.com/download
Stuck on that step. I know its telling me to enable USB debuggin which I have, it doens' do anythong when I click Go in Korean
I managed to enable debugging mode which was by setting the 'USB Type" on the phone to "Internet -> Ethernet"
But Kingroot isn't managing to root the phone. It goes 100 percent and nothing.
Ioroot managed to get the phone into the reboot phase but the phone no longer processed the splash screen of the recover/bootloader. The splash screen which has the android mascot on its back with abdomen open.
"LG G2 One lick Tool" makes the phone go to "download mode" but its stuck at 0 percent. I disconnect and replug in hope of kickstarting it, doesn't work.
What can I do now?
y300owner said:
I managed to enable debugging mode which was by setting the 'USB Type" on the phone to "Internet -> Ethernet"
But Kingroot isn't managing to root the phone. It goes 100 percent and nothing.
Ioroot managed to get the phone into the reboot phase but the phone no longer processed the splash screen of the recover/bootloader. The splash screen which has the android mascot on its back with abdomen open.
"LG G2 One lick Tool" makes the phone go to "download mode" but its stuck at 0 percent. I disconnect and replug in hope of kickstarting it, doesn't work.
What can I do now?
Click to expand...
Click to collapse
Where you able to get it to work? I am running into the same problems.
Sent from my SM-N920V using Tapatalk
y300owner said:
Can you share the setup files? I also need to re-root my Verizon phone. The kingroot ownload links looks dead
i downlaoded it from here. I have usb dev enabled. now what? http://kingroot-pc.en.uptodown.com/download
Stuck on that step. I know its telling me to enable USB debuggin which I have, it doens' do anythong when I click Go in Korean
Click to expand...
Click to collapse
Hmm... Sorry for the late response. Try this link and see if it works: http://www.kingroot.org/
mach01 said:
Hmm... Sorry for the late response. Try this link and see if it works: http://www.kingroot.org/
Click to expand...
Click to collapse
Thanks I tried almost almost everything.
Stumbled upon Stump root last night and it brute forced it way in.
---------- Post added at 12:46 PM ---------- Previous post was at 12:44 PM ----------
Jshokamp said:
Where you able to get it to work? I am running into the same problems.
Sent from my SM-N920V using Tapatalk
Click to expand...
Click to collapse
What problem? Check one of the thread I started. Posted everything on it.
y300owner said:
Thanks I tried almost almost everything.
Stumbled upon Stump root last night and it brute forced it way in.
---------- Post added at 12:46 PM ---------- Previous post was at 12:44 PM ----------
What problem? Check one of the thread I started. Posted everything on it.
Click to expand...
Click to collapse
You on 39aa or just 39a?
Lawlrus said:
You on 39aa or just 39a?
Click to expand...
Click to collapse
No idea. I was on a downgraded stock ROM, VS980_27A or was it VS980_24A. Can't remember; 4.4.2
Whatever it was, none of the popular rooting method was working. They were managing to do 'semi root' as in root message was displayed in "hard reset mode" and in 'download mode' but there was no root when the OS fully booted. The 'stock recovery' was also corrupted as in it showed a dead android with red exclamation mark. From the searching I did, people were saying there was no recovery installed so I needed one but I could not install. No stock recovery means no 'adb'.
Stump root gave 'complete' root. I hope you understand what I'm trying to say.
Will this work if I am on the 39aa update from Verizon? I am skeptical about this because this is my only phone and don't need to mess it up.
UserofAndroid1813 said:
Will this work if I am on the 39aa update from Verizon? I am skeptical about this because this is my only phone and don't need to mess it up.
Click to expand...
Click to collapse
I don't think I've seen a way to root 39aa as of yet. One of our developers was asking about it as well, if you do find a way, please @ me so I can hook him up
I'm still looking around for a way.
Lawlrus said:
I don't think I've seen a way to root 39aa as of yet. One of our developers was asking about it as well, if you do find a way, please @ me so I can hook him up
I'm still looking around for a way.
Click to expand...
Click to collapse
I tried and failed at it. I am downgrading to VS98039A_05 and going from there. it seems VS9803AA was meant to patch root and also SF security patches.
This XML file does not appear to have any style information associated with it.
The document tree is shown below.
<Error><Code>AccountProblem</Code><Message>
Your Google account is not currently enabled for this operation. Please check https://code.google.com/apis/console/#:billing to see if you have a past due balance or if the credit card (or other payment mechanism) on your account is expired. You can find additional information at https://developers.google.com/storage/docs/signup</Message></Error>
Thanks for this. For people who don't want to mess with Korean, or if Kingroot doesn't work, LG One Click Root still works on VS9803AA, although you may have to run it 3 or 4 times. Here's the original post: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
And here's a good guide: http://webtrickz.com/how-to-root-lg-g2-running-lollipop-with-lg-one-click-root/
Interesting... I've tried that method four times and it never worked for me. Good to hear it works for other people though. I agree not to many people want to use
Korean deciphering skills just to root their phone but its just an option.
marathonjon said:
Thanks for this. For people who don't want to mess with Korean, or if Kingroot doesn't work, LG One Click Root still works on VS9803AA, although you may have to run it 3 or 4 times. Here's the original post: http://forum.xda-developers.com/lg-g...lipop-t3056951
And here's a good guide: http://webtrickz.com/how-to-root-lg-...ne-click-root/
Click to expand...
Click to collapse
Both of these links are dead.
CruelSun said:
Both of these links are dead.
Click to expand...
Click to collapse
Links are fixed. The whole URLs don't show in the post, but if you click on them, they should work.
those with the issue of kingroot not reading your phone plugged in. put your usb option on phone to PTP camera mode and it will work now.
Even doing all, i m still unable to get my phone recognized. Switched many times befween ptp
Sent from my VS980 4G using Tapatalk
---------- Post added at 05:55 AM ---------- Previous post was at 05:54 AM ----------
Furqan Ullah said:
Even doing all, i m still unable to get my phone recognized. Switched many times befween ptp
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
And other file transfer option. USB picture is displaying sometimes or sometimes circle
Sent from my VS980 4G using Tapatalk
Related
I've bought my son and daughter a nexus 7 each for Christmas.
His upgraded over the air fine, hers downloaded the firmware, rebooted and the installation started.
After a couple of minutes the Android fell over with a red exclamation mark.
I've tried forcing the upgrade and the same happened.
Any ideas how to upgrade her nexus 7?
Thanks
Fastboot mode is working ?
Sent from my GT-I9100 using xda premium
I've not tried it.
How do I try it?
Assuming it's ok, does that help with upgrading?
Any issue truing fast boot mode?
Any ideas? Or will it need replacing?
Factory reset and try again
Sent from my Nexus 7
I have the same problem.
Hey guys,
I made an account just to post this, however it was all done my G2 so I apologize for poor formatting and/or not completely clear instructions. This issue has kept me up for hours upon hours, and I finally figured out how to fix it. The issue apparently has something to do with the way the Nexus was formatted, prohibiting the update from working. Google/Asus support have been useless regarding the issue which is a very simple fix just requiring the user to reflash the N7 with a stock image. It has been confirmed working by not just me but other people on the reddit nexus 7 board. Here is what I did (copy/pasted from my reddit thread):
---------------------------------------------------------------------------------------------------------------------
There are two methods to fix this, an in depth method, and an easy and quick method. My first time I used the in depth, but I tested this with the easy method too so I'll just post that. I'm on a cell phone so I'm not going into the in depth method - I'm posting this so hopefully the other people like me who got this on Christmas won't have to return it.
----------------
For the quick and easy method, download Wug's toolkit here:
(google this, forums wont let me post links until I reach 10 posts)
Run the driver install guide, making sure to follow the parts about uninstalling previous drivers. Follow this to a T. Next, unlock your bootloader. Its painless and takes seconds. Next, go here and download your Nexus specific update.
(Find this on google developer site, you can google it too - forums wont let me post links - also make sure its 4.2.1)
Click on the "back to stock + unroot" -- we never rooted, but just do this. Select other/browse and browse to the image you downloaded. Flash this. You WILL fail on three files - it says something like recovery.sig failed - it will do it for two other .sig files. This is fine. Let it do its thing. A few minutes later your android will boot up. Log in, and go to settings. Click about tablet. Click on build number like 10 times, until it tells you developer options unlocked. Go into developer options and enable USB debugging. Now, go back to Wugs toolkit and lock the bootloader. There you have it, an updated nexus running stock everything, and locked so your warranty is not void.
----------------------------------------------------------------------------------------------------------------------------
This was a very sloppy guide put together on my cell phone. Any questions just post and I'll do my best to get back to you. Goodluck!
Hi.
Thanks for the reply.
Just wondering if there is an easier way to do this.
I'm not comfortable flashing a new device.
What was the suggestion about fast boot?
Thanks
albert_htc said:
Hi.
Thanks for the reply.
Just wondering if there is an easier way to do this.
I'm not comfortable flashing a new device.
What was the suggestion about fast boot?
Thanks
Click to expand...
Click to collapse
This is definitely the easiest way for you to fix your problems. The risk of your device becoming unusable is practically none. This is the beauty of nexus devices, Google provides official factory reset ROMs for you to flash in these sorts of situations. You can either use Wugs or mskip's tookit as advised to automate the process (fastboot commands used to flash the recovery image, fastboot commands are simply used to flash it to your device) or you can use fastboot to flash it yourself manually (still very easy)
I would 100% do this to fix your device. Don't be scared! This is the official way of fixing a nexus device when it doesn't function.
Thanks.
I'm trying this now.
I've uninstalled all previous drivers, and it's updated to an 'Android Phone -> Android Composite ADB Interface'
I've clicked the Reboot BootLoader Button.. and nothing happens on the tablet.
This was trying with the #3 driver option.
I'm now trying driver #2 !!
Another quick question...
Once all this is done, will I have issues with it in the future, or should this resolve future updates.?
albert_htc said:
Another quick question...
Once all this is done, will I have issues with it in the future, or should this resolve future updates.?
Click to expand...
Click to collapse
I'm not certain about the driver issues because I don't use Wug's toolkit, sorry!
However, when you get this completed, it should solve this problem in the future.
I've had to go with option 1 for the drivers..
but it's done and working
One thing I did have to do after unlocking the boot loader was reset up on the wifi and re enable USB debugging before I could continue.
all sorted thanks
albert_htc said:
Thanks.
I'm trying this now.
I've uninstalled all previous drivers, and it's updated to an 'Android Phone -> Android Composite ADB Interface'
I've clicked the Reboot BootLoader Button.. and nothing happens on the tablet.
This was trying with the #3 driver option.
I'm now trying driver #2 !!
Click to expand...
Click to collapse
Let us know how it comes out and if there's problems, exactly where you're hitting the problem. I will try to help you out and later today I could probably get on team viewer and help you figure the drivers out.
Sent from my Nexus 7 using Tapatalk HD
Hi CharliesTheMan..
It's working. Had to use option 1 for the drivers.. but its updated and working
Thanks
Glad it worked out!
Sent from my Nexus 7 using Tapatalk HD
Hello all, after spending many hours Googling, rebooting, retrying, and staying up way too late, I am stuck. Hopefully someone can provide some guidance as I'm lost.
Yesterday I received my 64GB Nexus 6 from Motorola. I'm on Verizon. Popped in my SIM and was in business. Got it set up in short order, and it applied 5.0.1 OTA almost immediately. I downloaded the .zip for 5.1 and wanted to sideload it as I didn't want to wait for the OTA to hit my phone who-knows-when. Downloaded all the proper utilities and got the phone to show up when executing adb devices. I followed the sideloading guide and was golden up to the point of adb sideload xxxxxxx.zip. Error is "device not found". I uninstalled and reinstalled more drivers than I can shake a stick at, and the phone just won't show up in Device Manager once it's in Recovery. I did my fair share of Googling before posting here and there are many suggestions - most of which point to the driver - but none of them seem to work. I even tried the NRT by Wug and while it gives me two thumbs up as far as drivers are concerned, no dice once the phone is in Recovery.
I am on a Windows 7 Pro 64-bit machine.
So my questions are:
What the heck am I doing wrong?
Is there a way to sideload with the file on the phone already and not have to use adb?
Any help, suggestions, "hey dummy you forgot this", etc., is most welcome . Thank you in advance!
@Lucky Armpit
When you are in recovery, at the adb sideload screen, unplug your N6 and plug it in again.
Lucky Armpit said:
Hello all, after spending many hours Googling, rebooting, retrying, and staying up way too late, I am stuck. Hopefully someone can provide some guidance as I'm lost.
Yesterday I received my 64GB Nexus 6 from Motorola. I'm on Verizon. Popped in my SIM and was in business. Got it set up in short order, and it applied 5.0.1 OTA almost immediately. I downloaded the .zip for 5.1 and wanted to sideload it as I didn't want to wait for the OTA to hit my phone who-knows-when. Downloaded all the proper utilities and got the phone to show up when executing adb devices. I followed the sideloading guide and was golden up to the point of adb sideload xxxxxxx.zip. Error is "device not found". I uninstalled and reinstalled more drivers than I can shake a stick at, and the phone just won't show up in Device Manager once it's in Recovery. I did my fair share of Googling before posting here and there are many suggestions - most of which point to the driver - but none of them seem to work. I even tried the NRT by Wug and while it gives me two thumbs up as far as drivers are concerned, no dice once the phone is in Recovery.
I am on a Windows 7 Pro 64-bit machine.
So my questions are:
What the heck am I doing wrong?
Is there a way to sideload with the file on the phone already and not have to use adb?
Any help, suggestions, "hey dummy you forgot this", etc., is most welcome . Thank you in advance!
Click to expand...
Click to collapse
Use Wugs toolkit to install drivers. It has a great step by step set-up to make sure it works and it tests everything so you know it works..
cam30era said:
@Lucky Armpit
When you are in recovery, at the adb sideload screen, unplug your N6 and plug it in again.
Click to expand...
Click to collapse
Hi cam30era, I tried that but it didn't help. I didn't try it after using Wug's toolkit so it's worth another shot.
Xplicit84 said:
Use Wugs toolkit to install drivers. It has a great step by step set-up to make sure it works and it tests everything so you know it works..
Click to expand...
Click to collapse
Hi Xplicit84, I used the Wugs toolkit provided in the NRT to install the proper drivers (it worked fantastic, by the way... mad props to Wug). That didn't help unfortunately.
try a different usb port
goto the device manager in windows and see if everything is good (no ! by a device)
apristel said:
try a different usb port
goto the device manager in windows and see if everything is good (no ! by a device)
Click to expand...
Click to collapse
Hi apristel, yup, tried that too, as I had read that perhaps there may be an issue with USB 3.0 ports. I don't think I have USB 3.0 ports (my laptop is a 2012-era Alienware M17x R3) but I tried a different port for the sake of doing it and it didn't make a difference.
Where did you get the 5.1 .zip file? Give us the exact name of the file because the 5.1 VZW .zip file that has been posted here that ends with .xml.zip is not designed for an adb sideload command. I.e., not designed to be flashed in recovery at all.
teddyearp said:
Where did you get the 5.1 .zip file? Give us the exact name of the file because the 5.1 VZW .zip file that has been posted here that ends with .xml.zip is not designed for an adb sideload command. I.e., not designed to be flashed in recovery at all.
Click to expand...
Click to collapse
Hi teddyearp, I downloaded it from a link on Droid-Life. I don't remember the exact name of the file because I renamed it to something much shorter, but here's where I got it from -
http://www.droid-life.com/2015/03/1...s-for-nexus-devices-4-5-6-7-9-10/#more-163271
Edit - Here's the direct link (the one I used) - http://android.clients.google.com/p...ed-shamu-ota-LMY47D-from-LRX22C-fullradio.zip
Lucky Armpit said:
Hello all, after spending many hours Googling, rebooting, retrying, and staying up way too late, I am stuck. Hopefully someone can provide some guidance as I'm lost.
Yesterday I received my 64GB Nexus 6 from Motorola. I'm on Verizon. Popped in my SIM and was in business. Got it set up in short order, and it applied 5.0.1 OTA almost immediately. I downloaded the .zip for 5.1 and wanted to sideload it as I didn't want to wait for the OTA to hit my phone who-knows-when. Downloaded all the proper utilities and got the phone to show up when executing adb devices. I followed the sideloading guide and was golden up to the point of adb sideload xxxxxxx.zip. Error is "device not found". I uninstalled and reinstalled more drivers than I can shake a stick at, and the phone just won't show up in Device Manager once it's in Recovery. I did my fair share of Googling before posting here and there are many suggestions - most of which point to the driver - but none of them seem to work. I even tried the NRT by Wug and while it gives me two thumbs up as far as drivers are concerned, no dice once the phone is in Recovery.
I am on a Windows 7 Pro 64-bit machine.
So my questions are:
What the heck am I doing wrong?
Is there a way to sideload with the file on the phone already and not have to use adb?
Any help, suggestions, "hey dummy you forgot this", etc., is most welcome . Thank you in advance!
Click to expand...
Click to collapse
Any luck, having the same problem and it's driving me nuts.
Mongo23ny said:
Any luck, having the same problem and it's driving me nuts.
Click to expand...
Click to collapse
Are you selecting "apply update from ADB" in recovery and then hitting power?
Then: adb sideload <filename of update.zip>
?
apristel said:
Are you selecting "apply update from ADB" in recovery and then hitting power?
Then: adb sideload <filename of update.zip>
?
Click to expand...
Click to collapse
Yes, as soon as boots into recovery it completely disappears from device manager. If I run the command after apply update from adb it says device not found.
Mongo23ny said:
Yes, as soon as boots into recovery it completely disappears from device manager. If I run the command after apply update from adb it says device not found.
Click to expand...
Click to collapse
Most likely a driver issue. I can remote in and check it out if you want using teamviewer
Go through the driver setup in wug again, pay close attention when you are deleting any old drivers..... delete anything that says google nexus or android... I had to do it twice.... put the phone into adb side load mode... check device manager again.. make sure you dont have a ? by android device... I did... update the driver from wug ( also I hid the sdk driver folder by renaming it so windows didn't try to pick up the driver from there again... once installed bingo!
apristel said:
Most likely a driver issue. I can remote in and check it out if you want using teamviewer
Click to expand...
Click to collapse
When I run the command reboot bootloader, no problem. But when it is in recovery I watched it disappear from device manager.
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
Gage_Hero said:
Go through the driver setup in wug again, pay close attention when you are deleting any old drivers..... delete anything that says google nexus or android... I had to do it twice.... put the phone into adb side load mode... check device manager again.. make sure you dont have a ? by android device... I did... update the driver from wug ( also I hid the sdk driver folder by renaming it so windows didn't try to pick up the driver from there again... once installed bingo!
Click to expand...
Click to collapse
I used CF auto root to unlock the bootloader and root. I do have the NRT on my computer though.
Mongo23ny said:
When I run the command reboot bootloader, no problem. But when it is in recovery I watched it disappear from device manager.
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
I used CF auto root to unlock the bootloader and root. I do have the NRT on my computer though.
Click to expand...
Click to collapse
I still think its a driver issue for you though. I am using the ones you can download here and it works fine.
http://developer.android.com/sdk/win-usb.html#download (Where it says... Click here to download the latest Google USB Driver ZIP file.)
apristel said:
I still think its a driver issue for you though. I am using the ones you can download here and it works fine.
http://developer.android.com/sdk/win-usb.html#download (Where it says... Click here to download the latest Google USB Driver ZIP file.)
Click to expand...
Click to collapse
How do I install it properly? I got rid of some old drivers as well
Mongo23ny said:
How do I install it properly? I got rid of some old drivers as well
Click to expand...
Click to collapse
Well you can just change them in the device manager.
I'm willing to use team viewer and show you how. (you'd see everything i do) It's hard to write it out for me right now..just had hand surgery this morning and my hand is still completely numb. If you want to download this and run it http://download.teamviewer.com/download/TeamViewerQS_en.exe
PM me the id and password and i'll connect up and show ya. Just so you know, it'd be a one time thing connecting, your password changes everytime and you'd have to have that running to connect. I own a computer repair store and use it frequently.
apristel said:
I still think its a driver issue for you though. I am using the ones you can download here and it works fine.
http://developer.android.com/sdk/win-usb.html#download (Where it says... Click here to download the latest Google USB Driver ZIP file.)
Click to expand...
Click to collapse
I'm thinking that's the problem for me too, but I don't understand what I'm missing. When I ran Wug, I removed anything and everything that had the word "Google" next to it. Wug installed the drivers (had to do option #2 before I got no errors at all) and it reports that everything is hunky-dory. But as Mongo23ny said, that's exactly what happens... when it's at the boot menu it's in Device Manager but the moment I select Recovery it disappears.
Lucky Armpit said:
I'm thinking that's the problem for me too, but I don't understand what I'm missing. When I ran Wug, I removed anything and everything that had the word "Google" next to it. Wug installed the drivers (had to do option #2 before I got no errors at all) and it reports that everything is hunky-dory. But as Mongo23ny said, that's exactly what happens... when it's at the boot menu it's in Device Manager but the moment I select Recovery it disappears.
Click to expand...
Click to collapse
I can try to fix your drivers too, just follow the link i posted for him and send me the info. I don't have stock recovery on my phone to replicate your issue.
apristel said:
I can try to fix your drivers too, just follow the link i posted for him and send me the info. I don't have stock recovery on my phone to replicate your issue.
Click to expand...
Click to collapse
PM sent. Thanks
I just sent back the N6 that had the screen burn out, I got my RMA device and its on just 5.1 not 5.1.1 should I update it or keep it does it matter? Also this N6 is doing some of the same issues that the other device did before it burned out. The screen has a lot of flickering and triangle flashes but only when I'm using my web browser, also, today I got off of a phone call and the proximity sensor failed to turn the screen on. What's up with that? I'm starting to wonder about these N6's man. Any ideas guys. I think I may need to just flash the s#-t out of this thing
electrojas said:
I just sent back the N6 that had the screen burn out, I got my RMA device and its on just 5.1 not 5.1.1 should I update it or keep it does it matter? Also this N6 is doing some of the same issues that the other device did before it burned out. The screen has a lot of flickering and triangle flashes but only when I'm using my web browser, also, today I got off of a phone call and the proximity sensor failed to turn the screen on. What's up with that? I'm starting to wonder about these N6's man. Any ideas guys. I think I may need to just flash the s#-t out of this thing
Click to expand...
Click to collapse
If it was mine, I'd RMA this one too.
Unlock it. Fastboot flash the updated 5.1.1 factory image and see what you have. If bad send it back. If good it all good.
---------- Post added at 12:47 PM ---------- Previous post was at 12:39 PM ----------
What browser. It may be the problem. There were proximity sensor fixes in one of the updates. Not sure which.
prdog1 said:
Unlock it. Fastboot flash the updated 5.1.1 factory image and see what you have. If bad send it back. If good it all good.
---------- Post added at 12:47 PM ---------- Previous post was at 12:39 PM ----------
What browser. It may be the problem. There were proximity sensor fixes in one of the updates. Not sure which.
Click to expand...
Click to collapse
I'm using adblock browser. I just updated to Windows 10 so now my adb is all jacked up for some reason. When I turned on the phone it said that there was a 5.1.1 update ready to be installed. Should I just take that one before I unlock the BL and root or do the unlock first? Thanks to all of you who are helping me out. Good people.
electrojas said:
I'm using adblock browser. I just updated to Windows 10 so now my adb is all jacked up for some reason. When I turned on the phone it said that there was a 5.1.1 update ready to be installed. Should I just take that one before I unlock the BL and root or do the unlock first? Thanks to all of you who are helping me out. Good people.
Click to expand...
Click to collapse
Unlock first. Too many been bricked on that update with bootloader locked. I wouldn't take it. Win 10 didn't jack with my adb. I have full SDK tho. Some are using the 15 minute adb/fastboot. I would search and try to reinstall it. Does your usb debug work as far as showing device MTP on PC. If not you lost the Google driver.
---------- Post added at 03:13 PM ---------- Previous post was at 03:10 PM ----------
More than likely that browser is the flicker problem. I use Chrome but with Adaway and MOAB. No adds anywhere. lol
I'll have to check. I'm so gunshy now I only hooked this to pc just to put music on it. I'll unlock BL and try the update after. Thanks
electrojas said:
I'll have to check. I'm so gunshy now I only hooked this to pc just to put music on it. I'll unlock BL and try the update after. Thanks
Click to expand...
Click to collapse
If able to put music on your driver is good. Need ADB/Fastboot working or you are already dead in the water.
prdog1 said:
Unlock first. Too many been bricked on that update with bootloader locked. I wouldn't take it. Win 10 didn't jack with my adb. I have full SDK tho. Some are using the 15 minute adb/fastboot. I would search and try to reinstall it. Does your usb debug work as far as showing device MTP on PC. If not you lost the Google driver.
---------- Post added at 03:13 PM ---------- Previous post was at 03:10 PM ----------
More than likely that browser is the flicker problem. I use Chrome but with Adaway and MOAB. No adds anywhere. lol
Click to expand...
Click to collapse
15 minute adb? What is that like a tool that does all of that for you?
electrojas said:
15 minute adb? What is that like a tool that does all of that for you?
Click to expand...
Click to collapse
It the lazy man ADB/Fastboot for those that don't want to install full SDK and edit the environmental path.
http://forum.xda-developers.com/showthread.php?t=2588979
So I just follow the unlock procedure in the how to post like normal now right
electrojas said:
So I just follow the unlock procedure in the how to post like normal now right
Click to expand...
Click to collapse
Enable unlock in developers options. Boot to bootloader. in command prompt type "fastboot devices" to make sure your device id shows up. If shows device type "fastboot oem unlock". Will see prompt on phone to agree.
It's just finished so now does it matter which 5.1.1 I take, and do I have to put TWRP on this in order to do it
I suppose now I can take the downloaded one or do you recommend a better file. I really would like to keep this Damn phone
electrojas said:
It's just finished so now does it matter which 5.1.1 I take, and do I have to put TWRP on this in order to do it
Click to expand...
Click to collapse
Latest for all carriers is I version unless you are on TMobile then it is the one that says TMobile only. They don't have the security update yet. No need for TWRP yet as long as unlocked. Get it booted and see if everything works. Do NOT relock. DO NOT use toolkit. Do it manually with fastboot commands.
prdog1 said:
Latest for all carriers is I version unless you are on TMobile then it is the one that says TMobile only. They don't have the security update yet. No need for TWRP yet as long as unlocked. Get it booted and see if everything works. Do NOT relock.
Click to expand...
Click to collapse
Mine is unbranded factory unlocked. It's restoring all my backed up poo right now. I guess I have 2 options. 1 take the Ota they send down or install the one I downloaded yesterday. It says for all carriers except tmobile. I got it from Google yesterday. It's the exact one that was on the phone I sent back. Do you have any particular preference or reccomendation?
electrojas said:
Mine is unbranded factory unlocked. It's restoring all my backed up poo right now. I guess I have 2 options. 1 take the Ota they send down or install the one I downloaded yesterday. It says for all carriers except tmobile. I got it from Google yesterday. It's the exact one that was on the phone I sent back. Do you have any particular preference or reccomendation?
Click to expand...
Click to collapse
The new I version has the Stagefright security fix otherwize the Z version is fine. That is what I am on. Haven't updated yet.. You can try OTA as long as unlocked. Have seen posts that say OTA won't work unlocked. Not sure. If it bootloops and it is locked you are hosed again and have to RMA.
prdog1 said:
The new I version has the Stagefright security fix otherwize the Z version is fine. That is what I am on. Haven't updated yet.. You can try OTA as long as unlocked. Have seen posts that say OTA won't work unlocked. Not sure. If it bootloops and it is locked you are hosed again and have to RMA.
Click to expand...
Click to collapse
The new I version? Is the best place to get it on here or Motorola? Also your gonna think this is a stupid question but what is I version? I'm coming from Sammy to LG back to Sammy, now this. Learning about fastboot its all new to me. Thanks bro
Sent from my Nexus 6 using XDA Forums Pro.
electrojas said:
The new I version? Is the best place to get it on here or Motorola? Also your gonna think this is a stupid question but what is I version? I'm coming from Sammy to LG back to Sammy, now this. Learning about fastboot its all new to me. Thanks bro
Sent from my Nexus 6 using XDA Forums Pro.
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/images
Hi Im just wondering if this phone is actually rootable? If so can someone help? Thank you
zipl0cc said:
Hi Im just wondering if this phone is actually rootable? If so can someone help? Thank you
Click to expand...
Click to collapse
Took me less than a minute to locate the following thread that answers your question.
http://forum.xda-developers.com/showthread.php?t=3587174
Good Luck!
***Please Note: As always, I welcome any member to help with further valuable information/clarification for any of my posts.
Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise...
If you use the method described in the thread DON'T flash the SuperSu zip mentioned until you delete Kingoroot s 'superuser'.
I did this and bricked my phone for about 10 days until I could manage to keep the system running long enough to get rid of all the KingCrap from it.
Better yet NEVER USE KINGOROOT FOR ANYTHING EXCEPT AS A LAST RESORT
I've spent many hours fixing the damage it can do to a system.
Recommendation?
equitube said:
If you use the method described in the thread DON'T flash the SuperSu zip mentioned until you delete Kingoroot s 'superuser'.
I did this and bricked my phone for about 10 days until I could manage to keep the system running long enough to get rid of all the KingCrap from it.
Better yet NEVER USE KINGOROOT FOR ANYTHING EXCEPT AS A LAST RESORT
I've spent many hours fixing the damage it can do to a system.
Click to expand...
Click to collapse
Hi, Steven
As a new forum user, what do you recommend to use to root my phone instead? I have just done this and am having a terrible time with it! I can't move any of the bloatware or anything yet.
Thanks in advance,
Dr Cheryl
DrCheryl said:
Hi, Steven
As a new forum user, what do you recommend to use to root my phone instead? I have just done this and am having a terrible time with it! I can't move any of the bloatware or anything yet.
Thanks in advance,
Dr Cheryl
Click to expand...
Click to collapse
Did you replace the Kinguser (it might be called something a bit different like Superuser) with SuperSu or another SU? That is the first step to get out of the Kingroot trap.
DrCheryl said:
Hi, Steven
As a new forum user, what do you recommend to use to root my phone instead? I have just done this and am having a terrible time with it! I can't move any of the bloatware or anything yet.
Thanks in advance,
Dr Cheryl
Click to expand...
Click to collapse
Welcome Dr Cheryl
If you've rooted your n817 using this method and managed to replace KU congratulations. This one is not an easy root. Id be xurious what you're using to remove bloatware. 3c works good, Titanium backup, theres a lot
You can pm me iff you need help.
---------- Post added at 03:00 PM ---------- Previous post was at 02:57 PM ----------
equitube said:
Welcome Dr Cheryl
If you've rooted your n817 using this method and managed to replace KU congratulations. This one is not an easy root. Id be xurious what you're using to remove bloatware. 3c works good, Titanium backup, theres a lot
You can pm me iff you need help.
Click to expand...
Click to collapse
Rereading your question/ i guess you don't have root. I'm not aware of any other rooting methods for this phone. I've got one in my hands right now I'll be rooting soon, so Ill knpw if the new twrp is working
---------- Post added at 03:01 PM ---------- Previous post was at 03:00 PM ----------
equitube said:
Welcome Dr Cheryl
If you've rooted your n817 using this method and managed to replace KU congratulations. This one is not an easy root. Id be xurious what you're using to remove bloatware. 3c works good, Titanium backup, theres a lot
You can pm me iff you need help.
Click to expand...
Click to collapse
Rereading your question/ i guess you don't have root. I'm not aware of any other rooting methods for this phone. I've got one in my hands right now I'll be rooting soon, so Ill knpw if the new twrp is working
Doesnt work said:
As probably to be expected with this website, yet another complete failure.
Absolutely NOTHING will ever root an N817. Why are people still pushing the obvious lie??
15 attempts. ALL resulted in "root failed".
If you do not know what you are talking about, try NOT posting suggestions because they all lead to the exact same non-functional outcome.
Tried literally everything. All steps posted throughout the internet. NONE of them actually function as advertised.
I am sick of the lies. It is clear that no one on this site actually knows what they are talking about.
The "apps" suggested on this site, along with dr.fone, and even the debloater apps are ALL non-functional.
What is it going to take to stop the lies????
Face it. The N817 can not be rooted nor cleaned up. It is the sole intention of ZTE.
When you call ZTE and navigate past their red tape, you find out the truth.
The device will never allow ANY user access over the device.
STOP the lies and remove this entire topic already.
---------- Post added at 06:13 PM ---------- Previous post was at 06:07 PM ----------
Well, you asked for it. NONE of these suggestions, and NONE of the other suggestions this site has offered works in any way what so ever.
"root failed" is the only outcome for everything this site has claimed.
The N817 can NOT be rooted, nor debloated. ALL N817's are blocked. Meaning that there is no possible way to clean up nor root them. ZTE will tell everyone the same if they bother to investigate the claims made by users of this site.
I have tried everything this site has stated numerous times. The only result possible is "root failed" or device not recognized.
Click to expand...
Click to collapse
Actually, I just obtained ROOT with 360Root that chinese app on android. Then I flashed TWRP, then SuperSU, boom fully rooted
I did some thread cleanup. Please stop the ranting and be respectful to other users.
BIatu said:
Actually, I just obtained ROOT with 360Root that chinese app on android. Then I flashed TWRP, then SuperSU, boom fully rooted
Click to expand...
Click to collapse
Well, some people, like the poster above can't seem to do any critical thinking for themselves. If it doesn't go 'just like the video' heaven forbid they would have to synthesize their own methods.
Hey guys I've tried everything and it's just not happening I have Qlink ZTE 818 with a 7.1.1 OS and it's just not working. I guess I'm not smart enough to do this.
zipl0cc said:
Hi Im just wondering if this phone is actually rootable? If so can someone help? Thank you
Click to expand...
Click to collapse
360root works, but you will lose root if you restart/reboot your system.
Similar result but still not the same.
texas4la said:
360root works, but you will lose root if you restart/reboot your system.
Click to expand...
Click to collapse
I also ran 360root but I tried to run Root Checker and System App Safe Remover and neither worked. Root Checker didn't even pull up the prompt, yet SASR brought the prompt up but still wouldn't remove system apps. Any thoughts from anyone? When I ran kingoroot it brought the menu up at 70% and restarted and nothing changed. I'd like to remove the bloatware not just disable it.
I have searched countless forums and have tried kingroot, kingoroot, 360, the PC version of kingo, I have tried adb root exploits. I have tried fastboot (I have never been able to type "fastboot devices" and receive recognition) I have downloaded Qualcomm drivers, adb drivers, zte drivers. I have used the software for flashing zte devices which failed when I tried to flash. I have enabled developer options and ticked OEM unlocking and USB debugging. The device I am referencing is the ZTE sapphire from qlink. MODEL# Z3001S. If anyone knows a method I'm all ears and would greatly appreciate some help here
Ive got root before on this device. Helped me girlfriends mom out.
Notes: This trips KNOX so you will void your warranty, read all the steps carefully before beginning, flashing can be dangerous if you do it wrong. Don't blame me if you brick your device.
Backup all of your data and settings before starting as you will need to reset to factory defaults during this process.
With that being said, the process is relatively straightforward and easy.
PS: my device is the A908B, there is also an A908N if anyone wants to test on that be my guest.
Needed:
ADB
SamFirm
Odin
Magisk Manager
Step 1 - Downloading your firmware.
Go to SamMobile SM-A908B
Find the correct firmware for your device according to country and operator.
Note: You can use generic country firmware instead, this will remove carrier added software and limitations but may remove features and disables OTA updates.
Note the 'product code'.
Now open SamFirm.
Type SM-A908B for model
In the region box type the product code you noted earlier.
Click Check Updates.
When it has found the firmware, make sure decrypt automatically is checked and then click download rom.
The firmware is around 4gb.
Part 2 - Unlocking the Bootloader
Go to settings > about phone > software information. Hit build number a bunch of times until you activate developer options.
Go back to settings > developer options
Enable OEM unlocking
Enable USB debugging
Turn off the phone
Hold volume up and volume down whilst inserting the USB cable
This should take you to the bootloader unlock screen.
Long press Volume up to unlock the bootloader.
Part 3 - Obtaining root
After SamFirm finished downloading the rom it should have extracted it into 5 tar files.
Copy the tar file beginning with AP to your device.
Download Magisk Manager on the device and install.
Press Install on Magisk Manager
Confirm the Install
Select the option 'select and patch file', then locate the APdjkfgrsdkfhgkjrg.tar.md5 on your device and select it.
Magisk will then patch the file and dump the patched version to your phone.
Copy the patched.tar to your PC
Reboot phone into download mode
Open Odin
For BL use the BL.tar.md5 file from stock firmware
For AP use the patched.tar file
For CP use the CP.tar.md5 file from stock firmware
For CSC use the CSC.tar.md5 file from stock firmware (not the CSC_HOME)
Press Start and wait for it to flash
After flashing, the phone will reset.
After initial setup, install magisk manager again.
Remove the USB cable and turn off the phone.
Turn on the phone by holding volume up and power, let go when you see the bootloader warning.
Open Magisk Manager Click Install.
Phone is now rooted.
Note: Powering on the device normally will disable root, you must hold volume up to power on the device to activate root.
Awesome job thanks a lot
Going to put a few hours into compiling twrp tonight but this might take me forever, I'm really busy with work and I got 2 kids too so free time is scarce. So feel free to have a go at it yourself.
After root activation with the volume button start up will the root persist? Can the device be restarted without any hidden key?
Thank you
Yes the root persists, but every time you turn the phone off and back on again you will have to hold up to activate the root. Resetting the phone while root is enabled does not disable it though iirc.
More work done on twrp last night, nearly ready to attempt compiling.
Edit: So I made a device tree and compiled twrp fine. Unfortunately it needs a custom kernel to be able to boot. Working on this now.
Any further progress??
No not really. I need to reach out to the twrp Devs of the S10 and see what modifications they did to theirs, but super busy at the moment. Sorry.
johnoponi said:
Any further progress??
Click to expand...
Click to collapse
Ok so I made a lot of progress since last post. I'm compiling the kernel as I type. But the process takes a long time. If we are lucky it will boot twrp straight away if not I'll keep at it until I manage.
triggz881 said:
Ok so I made a lot of progress since last post. I'm compiling the kernel as I type. But the process takes a long time. If we are lucky it will boot twrp straight away if not I'll keep at it until I manage.
Click to expand...
Click to collapse
Are you still trying?
Failure on Model SM-A9080 (China Version)
Today I did this on model SM-A9080 but unluckily failed, and the OS could not be loaded, with boot loop on the phone.
Really the specified TWRP should be developed.
triggz881 said:
Ok so I made a lot of progress since last post. I'm compiling the kernel as I type. But the process takes a long time. If we are lucky it will boot twrp straight away if not I'll keep at it until I manage.
Click to expand...
Click to collapse
Hey - did you manage to get anywhere with this? If you'd like help, i'd be happy to get stuck in. Could you put the code on Github?
Hello,
I tried to root my phone today, and I followed every step exactly, but now I am stuck in a Boot Loop, after the Step of Flashing. Can someone help, or knows why this happened? Thank you.
---------- Post added at 07:48 PM ---------- Previous post was at 07:03 PM ----------
Okay I fixed it myself. The Problem was, I only Flashed the BL File. After that I flashed the other files one by one, did a Factory Reset in Recovery mode and now it worked! I even have root now.
Do we have a custom rom yet? Can't stand the samsung rom or whatever its called.
xijaw said:
Do we have a custom rom yet? Can't stand the samsung rom or whatever its called.
Click to expand...
Click to collapse
So why did you buy a Samsung.
Srbija2012 said:
So why did you buy a Samsung.
Click to expand...
Click to collapse
Lmao, true. He could of easily went for one plus etc..
And bull****, Samsung ui is definitely top it's really nice.. just the notifications could be improved
Srbija2012 said:
So why did you buy a Samsung.
Click to expand...
Click to collapse
I live in Australia and here we don't have a market like Europe and India. We only have couple of brands- Apple and Samsung.
---------- Post added at 01:31 PM ---------- Previous post was at 01:30 PM ----------
underdog_656 said:
Lmao, true. He could of easily went for one plus etc..
And bull****, Samsung ui is definitely top it's really nice.. just the notifications could be improved
Click to expand...
Click to collapse
Lets stick to the topic and get the damn custom rom built. Aren't there any devs who willing to take A90 as a project ?
can you get the ctsprofile pass in the magisk manager？
Steveee101 said:
Hey - did you manage to get anywhere with this? If you'd like help, i'd be happy to get stuck in. Could you put the code on Github?
Click to expand...
Click to collapse
can i ask you whather you can get the cts profile pass or false or not after you root by magisk？
Hello please can someone help me root this phone, i have followed the steps but i just seem to be missing something so can someone take me through this step by step for a dumb person like myself lol?
At first i was struggling with part one of this tutorial but once i updated samfirm i was able to download it without a problem. moving over to the last step which is using odin to do its thing with the tar files and upon finishing where it should reboot it is stuck into a boot loop saying "this phone is not running samsungs offical software", i am not sure what i am missing and i am able to fix the phone without any problems but no root is achieved
Hello. May I ask about the progress on TWRP for this phone?