[Q] Nexus Root Toolkit 1.6.1 will unlock will NOT root - Nexus 7 Q&A, Help & Troubleshooting

So I unlocked and rooted my first N7 and then a young little girl decided to knock it off the counter during christmas and rendered it useless. Now today I get another one, unlock/wipe it and works fine. Then tell it to root and it now says No fast boot device detected. re-did the driver installs etc and the same thing. What gives? It unlocked just fine.
I'm willing to paypal some skrilla if someone will just get this damn thing rooted so I can move on with life! I use TeamViewer if anyone is willing to help that route, too.
Regards,
Jon

well, i manually loaded the zips from the bootloader and got it rooted. but now the n7 wont show up in "my computer" as a drive...?

meh. dumped the adp drivers. that wugs kit really did a number on my win7 machine this time around

For Nexus 7 to show up on your computer, you must have USB debugging enabled.

Related

Trying to root again after 4.2.1 update

I rooted using Mskip's rootkit. I updated with the OTA update thinking I could use the kit to root again. I'm on the latest version of the toolkit after donating and updating it. I go to option 4(root options) then I choose option 1(root). I do this while in fastboot mode. The Nexus 10 reboots, goes to the home screen, and the toolkit says it is "Waiting for Device" Nothing happens. I tried rebooting into fastboot mode again, but nothing. I ran root checker, and it says I do not have root.
Any ideas on what I'm doing wrong.
Dynesh said:
I rooted using Mskip's rootkit. I updated with the OTA update thinking I could use the kit to root again. I'm on the latest version of the toolkit after donating and updating it. I go to option 4(root options) then I choose option 1(root). I do this while in fastboot mode. The Nexus 10 reboots, goes to the home screen, and the toolkit says it is "Waiting for Device" Nothing happens. I tried rebooting into fastboot mode again, but nothing. I ran root checker, and it says I do not have root.
Any ideas on what I'm doing wrong.
Click to expand...
Click to collapse
First off, do you have "USB Debugging" checked in settings? Sounds like ADB isn't working. (Especially since you were already in fastboot mode, which doesn't require debugging.
See THIS thread.
If you have a custom recovery installed, download the superSU app and Su binaries from Chainfire's thread I just linked and flash them in recovery.
If you don't have a custom recovery, use the toolkit to either temp flash or fully flash the right recovery onto your tablet.
Also, if I remember correctly, options 3 & 4 in the toolkit's root menu will essentially do this for you.
NOTE: For future OTA updates, download "OTA Rootkeeper" or "SuperSU Pro" from the market. They both have options to protect root during an OTA update. (SuperSU Pro has never failed me when I used it to protect root when I had my Asus TF700.
xIC-MACIx said:
First off, do you have "USB Debugging" checked in settings? Sounds like ADB isn't working. (Especially since you were already in fastboot mode, which doesn't require debugging.
See THIS thread.
If you have a custom recovery installed, download the superSU app and Su binaries from Chainfire's thread I just linked and flash them in recovery.
If you don't have a custom recovery, use the toolkit to either temp flash or fully flash the right recovery onto your tablet.
Also, if I remember correctly, options 3 & 4 in the toolkit's root menu will essentially do this for you.
NOTE: For future OTA updates, download "OTA Rootkeeper" or "SuperSU Pro" from the market. They both have options to protect root during an OTA update. (SuperSU Pro has never failed me when I used it to protect root when I had my Asus TF700.
Click to expand...
Click to collapse
Thanks for the answer. I'm not a total newb to rooting things, but defintely not a pro, so some of this goes beyond what I've done before. I'll have to approach slowly. I don't really need root for anything right now, I only rooted to connect BT controllers to the Nexus, and those apps are broken right now anyway.
I do have usb debugging checked. I'm not sure about the other things you asked. I've never flashed anything to my droid devices, so I'll try and go through that thread and see what makes sense.
Thanks!
Well, I tried to run that program from the link, and it said some files were missing, so I stopped it. I tried to flash clockwork mod recovery and when it booted back into Android to rename the files, it got stuck on waiting on ADB. Frustrating.
Dynesh said:
Thanks for the answer. I'm not a total newb to rooting things, but defintely not a pro, so some of this goes beyond what I've done before. I'll have to approach slowly. I don't really need root for anything right now, I only rooted to connect BT controllers to the Nexus, and those apps are broken right now anyway.
I do have usb debugging checked. I'm not sure about the other things you asked. I've never flashed anything to my droid devices, so I'll try and go through that thread and see what makes sense.
Thanks!
Click to expand...
Click to collapse
Yeah, it seems more intimidating than it really is. Luckily, all of the things I listed in my above post are all achievable through the Nexus 10 Toolkit that you have downloaded.
I agree though, take it slow and read through the instructions, that is the best way to avoid breaking something. Rooting is a pretty safe procedure these days, my first Android phone was quite the headache.
When you do decide to root again, you can use the toolkit to either:
-- Install root through ADB (no recovery needed) like you already tried. Beforehand, you should check to make sure you correctly installed the correct drivers.You also need to check the toolkit's "List of attached devices" section to see if you see your device (represented by a string of letters & numbers) whenever your device boots back to the homescreen.
--Or temporarily install the necessary recovery to flash a root package, once it is flashed the device will revert to the stock recovery. (When you see "CWM" the toolkit is referring to a custom recovery BTW.)
xIC-MACIx said:
Yeah, it seems more intimidating than it really is. Luckily, all of the things I listed in my above post are all achievable through the Nexus 10 Toolkit that you have downloaded.
I agree though, take it slow and read through the instructions, that is the best way to avoid breaking something. Rooting is a pretty safe procedure these days, my first Android phone was quite the headache.
When you do decide to root again, you can use the toolkit to either:
-- Install root through ADB (no recovery needed) like you already tried. Beforehand, you should check to make sure you correctly installed the correct drivers.You also need to check the toolkit's "List of attached devices" section to see if you see your device (represented by a string of letters & numbers) whenever your device boots back to the homescreen.
--Or temporarily install the necessary recovery to flash a root package, once it is flashed the device will revert to the stock recovery. (When you see "CWM" the toolkit is referring to a custom recovery BTW.)
Click to expand...
Click to collapse
Success!
I think the problem coming in for me was not understanding ADB and fastboot. I have the drivers installed, but it wasn't seeing it. I switched to PTP mode and instantly it was being seen in ADB mode by the toolkit. I then ran option 4-->Option 1(Root Device) from fastboot mode. This time when it booted back to the homescreen the toolkit was able to continue with the root and I am now rooted again.
Thanks for taking the time to respond to this and help me out. You mention of the drives is what kind of kicked me in the right direction.
Dynesh said:
Success!
I think the problem coming in for me was not understanding ADB and fastboot. I have the drivers installed, but it wasn't seeing it. I switched to PTP mode and instantly it was being seen in ADB mode by the toolkit. I then ran option 4-->Option 1(Root Device) from fastboot mode. This time when it booted back to the homescreen the toolkit was able to continue with the root and I am now rooted again.
Thanks for taking the time to respond to this and help me out. You mention of the drives is what kind of kicked me in the right direction.
Click to expand...
Click to collapse
Glad it's working, Android can be temperamental at times & the issue is typically caused by the small things!
Dynesh said:
Success!
I think the problem coming in for me was not understanding ADB and fastboot. I have the drivers installed, but it wasn't seeing it. I switched to PTP mode and instantly it was being seen in ADB mode by the toolkit. I then ran option 4-->Option 1(Root Device) from fastboot mode. This time when it booted back to the homescreen the toolkit was able to continue with the root and I am now rooted again.
Thanks for taking the time to respond to this and help me out. You mention of the drives is what kind of kicked me in the right direction.
Click to expand...
Click to collapse
Which root method did you use? The only one I've looked at requires unlock to root. Ive rooted every phone ive owned and they are super easy, they never do a factory reset/unlock to root. BTW I'm on 4.2.1 and i gave up when the toolkit i used wouldnt connect to fastboot.
kane1513 said:
Which root method did you use? The only one I've looked at requires unlock to root. Ive rooted every phone ive owned and they are super easy, they never do a factory reset/unlock to root. BTW I'm on 4.2.1 and i gave up when the toolkit i used wouldnt connect to fastboot.
Click to expand...
Click to collapse
I rooted using this method.
http://forum.xda-developers.com/showthread.php?t=2001868
I did have to unlock the bootloader so I did lose everything, but it wasn't that hard and I did it early enough that I didn't lose too much of what I had on there.

[Q] Problems with the root after 4.2.2 update

Hello everyone, I am fairly new to rooting, roms and what not. The only other experience I had rooting something was with my old g2x. Anyways, I was reading everywhere that the new 4.2.2 OTA update was available and people had provided urls. I decided I would go ahead and root my nexus 10 while it was on 4.2.1. I followed the instructions with rooting a nexus 10 by using the nexus root toolkit by WugFresh. I followed every instruction (backing up, unlocking, then rooting) without making any mistakes. Everything went fine with the rooting process until i tried to install a paid app. I then went ahead and looked up what the -24 error was. They said to fix it i needed to go into data/data and delete the folders. This is when I realized the my root hadn't worked. The unlock worked but the root didnt. I downloded rootchecker and it said I wasnt rooted. Now I'm attempting to root my nexus 10 again but it keeps saying my adb device is listed as offline. No matter what I do, uninstalling all the usb drivers related to google and such, wiping my nexus 10 etc. I can't get it to root. Some assistance is needed! Anything I can do to root my tablet?
itstommy said:
Hello everyone, I am fairly new to rooting, roms and what not. The only other experience I had rooting something was with my old g2x. Anyways, I was reading everywhere that the new 4.2.2 OTA update was available and people had provided urls. I decided I would go ahead and root my nexus 10 while it was on 4.2.1. I followed the instructions with rooting a nexus 10 by using the nexus root toolkit by WugFresh. I followed every instruction (backing up, unlocking, then rooting) without making any mistakes. Everything went fine with the rooting process until i tried to install a paid app. I then went ahead and looked up what the -24 error was. They said to fix it i needed to go into data/data and delete the folders. This is when I realized the my root hadn't worked. The unlock worked but the root didnt. I downloded rootchecker and it said I wasnt rooted. Now I'm attempting to root my nexus 10 again but it keeps saying my adb device is listed as offline. No matter what I do, uninstalling all the usb drivers related to google and such, wiping my nexus 10 etc. I can't get it to root. Some assistance is needed! Anything I can do to root my tablet?
Click to expand...
Click to collapse
I recommend trying the Nexus 10 Toolkit 1.3.0. I successfully rooted my 4.2.1 N10 with this tool a few days ago (and promptly lost it in the OTA). http://forum.xda-developers.com/showthread.php?t=2001868
nalf38 said:
I recommend trying the Nexus 10 Toolkit 1.3.0. I successfully rooted my 4.2.1 N10 with this tool a few days ago (and promptly lost it in the OTA). http://forum.xda-developers.com/showthread.php?t=2001868
Click to expand...
Click to collapse
Yeah, but the thing is it doesn't recognize the device being plugged in. I don't know what else to do. I've tried using that toolkit (the one click all) and it wont even start.
itstommy said:
Yeah, but the thing is it doesn't recognize the device being plugged in. I don't know what else to do. I've tried using that toolkit (the one click all) and it wont even start.
Click to expand...
Click to collapse
Have you tried the Naked ADB drivers? What Windows OS are you using?
nalf38 said:
Have you tried the Naked ADB drivers? What Windows OS are you using?
Click to expand...
Click to collapse
where did you find the naked drivers? I'm running W7 64 bit. I only installed the drivers that came with pdanet as required by the guide I followed. Now im stuck in an unrooted 4.2.2.
ADB mode offline Both toolkits
nalf38 said:
I recommend trying the Nexus 10 Toolkit 1.3.0. I successfully rooted my 4.2.1 N10 with this tool a few days ago (and promptly lost it in the OTA). http://forum.xda-developers.com/showthread.php?t=2001868
Click to expand...
Click to collapse
I too have the same problem. Been searching for hours trying to find a solution.
I have tried both Wug's and mskips (paid version) toolkits and still the device shows offline.
I have ADB debuging enabled and tried in PTP and MTP modes. Have uninstalled the drivers and tried the PDAnet versions as well as the ones from mskips toolkit.
Both toolkits show that the device is connected, and I have booted to recovery and done the driver install (sees it as a Nexus 4 btw), but it's in offline mode.
My G-Nex works just fine, and I'm no stranger to rooting/custom roms. Not sure if having both devices loaded on this laptop is the issue.
Any help would be appreciated
Thanks
Jim
mrlow999 said:
I too have the same problem. Been searching for hours trying to find a solution.
I have tried both Wug's and mskips (paid version) toolkits and still the device shows offline.
I have ADB debuging enabled and tried in PTP and MTP modes. Have uninstalled the drivers and tried the PDAnet versions as well as the ones from mskips toolkit.
Both toolkits show that the device is connected, and I have booted to recovery and done the driver install (sees it as a Nexus 4 btw), but it's in offline mode.
My G-Nex works just fine, and I'm no stranger to rooting/custom roms. Not sure if having both devices loaded on this laptop is the issue.
Any help would be appreciated
Thanks
Jim
Click to expand...
Click to collapse
You're not researching in the right places. Wug's toolkit 1.6.2 have been confirm by the developer to not be working properly and he states that an update is in the horizon so be patient. Also, if you click on his website he wrote a paragraph about a temporary fix and he gives you a zip file so you can replace the files on the computer. I can assure you it works. If the files are replaced properly your device will show online instead of offline.
Here is his website where he gives you the tools to make it work: http://www.wugfresh.com/nrt/
THANK YOU SO MUCH FOR POSTING THIS. I've been scouring the forums everywhere just trying to fix this when the answer was right under my nose.
Thanks!
RawBott Bigg said:
You're not researching in the right places. Wug's toolkit 1.6.2 have been confirm by the developer to not be working properly and he states that an update is in the horizon so be patient. Also, if you click on his website he wrote a paragraph about a temporary fix and he gives you a zip file so you can replace the files on the computer. I can assure you it works. If the files are replaced properly your device will show online instead of offline.
Click to expand...
Click to collapse
Thanks a bunch! :good:
I did finally get it working late last night using mskips toolkit (donate version). Went without a hitch.
I can't believe I didn't see that. It's easy to miss something when you're frustrated, and not thinking about the right search terms.
The solution I found was it was a permission problem. As soon as I tried to do something with the toolkit, I got a popup on the tablet asking if I wanted to let my laptop control it. As soon as I said yes and always it worked beautifully. Had to do it again when it did the factory reset, but I was ready that time.
It threw me for a loop, never had to do that with my GNex or my OG Droid.
For now, I'll stick with mskips toolkit.
Thanks again.
Jim

[Q] Can't unlock Nexus 7 2013

Went thru other problems in here but none of them worked.
I'm using Nexus Root Toolkit 1.8.2.
Everything seems to work except when Unlock finishes, it does not go back to "new" state. Everything is still there: all my apps, settings, everything.
I tried another USB port, another USB cable, and then used a different computer and went thru it all again. Same problem.
I made sure I set it to v2 and 4.4.2 KOT49H. Went thru the drivers setup. Everything passed after I followed all the instruction.
I even tried to Root it and still nothing. It reboots, it does everything it's supposed to do. I even watched the video on their webpage about my Nexus. It does exactly as it should, except when it comes out of unlock, apparently it's not unlocked.
Maybe try a different root program?
goofy173 said:
Went thru other problems in here but none of them worked.
I'm using Nexus Root Toolkit 1.8.2.
Everything seems to work except when Unlock finishes, it does not go back to "new" state. Everything is still there: all my apps, settings, everything.
I tried another USB port, another USB cable, and then used a different computer and went thru it all again. Same problem.
I made sure I set it to v2 and 4.4.2 KOT49H. Went thru the drivers setup. Everything passed after I followed all the instruction.
I even tried to Root it and still nothing. It reboots, it does everything it's supposed to do. I even watched the video on their webpage about my Nexus. It does exactly as it should, except when it comes out of unlock, apparently it's not unlocked.
Maybe try a different root program?
Click to expand...
Click to collapse
Did you try unlocking manually by using the fastboot drivers? See if that works.
How do I do that? Its that something within Nexus Root Toolkit?
I tried manually putting it into bootloader and then running the toolkit with no luck
I have these options on the bootloader:
Restart Bootloader
Recovery Mode
Power Off
Start
At the bottom I have:
FASTBOOT MODE
PRODUCT NAME - flo
VARIANT - flo 32G
HW VERSION - rev_e
BOOTLOADER VERSION - FLO-04.02
CARRIER INFO - None
SERIAL NUMBER - 05858bae
SIGNING - yes
SECURE BOOT - enabled
LOCK STATE - unlocked
Does that last one mean it's already unlocked?
Here's what I did:
I tried another method. I got the clockwork recovery image, SuperSU and Fastboot.
I opened a command prompt to get it into bootloader but it never worked so I did it manually.
I typed fastboot oem unlock and that worked. It looks like its already unlocked.
Rebooted but all my data was still there.
Then I typed fastboot flash recovery recovery-clockwork-6.0.4.3-flo.img (Now I see WiFi only I was supposed to use 6.0.4.4, oh well)
and it said it was successful. When I rebooted it was back the way it always is, with my data.
I sent ahead with the root by copying SuperSU.zip over to the root directory.
Rebooted to recovery mode
and install teh zip file
It all said it worked but I rebooted and it's still all the same.
Now this would have normally told me it was already rooted, but I tried to install an adblocker the other day that required a rooted tablet, and it said it could perform the install because it wasn't rooted.
So???
Unlocking the bootloader destroys your data. If they're still there, I doubt you successfully unlocked the bootloader. Check by powering down. Boot back up. You should see the word Google followed by an icon of an open lock if you successfully unlocked the bootloader.
Sent from my Nexus 7 using Tapatalk
exglynco said:
Unlocking the bootloader destroys your data. If they're still there, I doubt you successfully unlocked the bootloader. Check by powering down. Boot back up. You should see the word Google followed by an icon of an open lock if you successfully unlocked the bootloader.
Click to expand...
Click to collapse
I've had that open lock icon from when I first got the tablet.
I don't think i can post images.
https://www.dropbox.com/s/is51bsgh11zxkcu/100_1690[1].JPG
I tried 2 other root required apps, one which is for checking if it rooted, and it said it wasn't, and a root-required app also said it wasn't.
Dude you are already unlocked. If it says in bootloader mode that you are unlocked and you have the unlock symbol when you boot you are unlocked. You just need to root. Rooting is is not the same as unlocking your bootloader. To root you can either use a toolkit. Or get the LATEST Supersu flashable zip file. Then download the Supersu app from the play store and update your binaries
Sent from my SCH-I535 using Tapatalk
And I've done both of those and neither has rooted it. Says it did it, but when I check it with 2 apps that require a rooted tablet, it says it's not rooted. I dl'ed a root check app and it also says its not rooted. Gonna go thru it again right now.
And it worked with Nexus Root Toolkit and just clicking root and following everything from then on out.
not sure where I messed up. Not even sure that mine came already unlocked now. Maybe I unlocked it the first time I tried?
Anyway, the root checker app said its rooted! Thanks for your help as this is my first root of anything.
I guess since I never lost my data and apps since I first started trying to root this Nexus yesterday, it must have already been unlocked, since from my understanding, unlocking it would have lost the apps and data and took it back to as-new setup.
goofy173 said:
I guess since I never lost my data and apps since I first started trying to root this Nexus yesterday, it must have already been unlocked, since from my understanding, unlocking it would have lost the apps and data and took it back to as-new setup.
Click to expand...
Click to collapse
Unlocking doesn't delete your apps. But it does delete everything on the internal SD card
Sent from my SCH-I535 using Tapatalk
Sandman-007 said:
Unlocking doesn't delete your apps. But it does delete everything on the internal SD card
Click to expand...
Click to collapse
oh. I figured that was everything. I do remember at one point I had to put my password in manually to connect to my router. Must have been when it unlocked.
Now when I just did my daughter's Nexus 7 (2012) it did erase everything and took it back to original, but she's only had a for a week so she can reinstall everything.

nexus 7 2012 partial root

My brother unlocked my boot loader and the tried to root it. Half way through the process he got a phone call and had to leave. Is there a way to root the rest of the way without a PC?
Well things have improved I got my computer back and can now properly root my tablet

Does unlocked BL automatically mean root is possible.

I've always been a Samsung fan, but this phone is packed with features I like. With samsung , unlocked BL then twrp, then flash SU..done. is LG a little different or is it Nouget that is making the process harder or even not possible? Any thoughts from any LG veterans?
Bubba Fett said:
I've always been a Samsung fan, but this phone is packed with features I like. With samsung , unlocked BL then twrp, then flash SU..done. is LG a little different or is it Nouget that is making the process harder or even not possible? Any thoughts from any LG veterans?
Click to expand...
Click to collapse
AFAIK it's Nougat. This is my first LG device, coming from HTC 10. I've had many others, just never LG.
lightninbug said:
AFAIK it's Nougat. This is my first LG device, coming from HTC 10. I've had many others, just never LG.
Click to expand...
Click to collapse
Did you get the phone yet? Try to unlock? I think i saw you involved over at the s7 edge root thread when i was watching that right? The things I'm going to have to get used to is power button and no physical home/back buttons however if root is achieved and maintained through FW updates I think this phone will be the best out there and development for LG should rise.
Bubba Fett said:
Did you get the phone yet? Try to unlock? I think i saw you involved over at the s7 edge root thread when i was watching that right? The things I'm going to have to get used to is power button and no physical home/back buttons however if root is achieved and maintained through FW updates I think this phone will be the best out there and development for LG should rise.
Click to expand...
Click to collapse
No.. thought I was getting it today via UPS... Guess I was tracking the wrong package lmao (stoner moment)... The G pad X came today instead... Lammmmme!!!
LG blocked fastboot commands since MM so the standard would usually be Unlock BL, flash recovery then flash SU.
But its not the case anymore.
Now its Unlock BL wait till an official.tot or .kdz to be released or leaked from LG, then repack it with root or a recovery and flash via LGUP or LG Tool.
just curious, what do you need root for?
phones nowadays come great out of the box. just disable what you dont need.
Z51 said:
just curious, what do you need root for?
phones nowadays come great out of the box. just disable what you dont need.
Click to expand...
Click to collapse
Are you really on XDA posting this?...What do we need root for???... Maybe head to the T-Mobile forums bro.
lightninbug said:
Are you really on XDA posting this?...What do we need root for???... Maybe head to the T-Mobile forums bro.
Click to expand...
Click to collapse
Does someone really need to want to root his phone to be on XDA? There's a whole lot of learning and shared experience going on out in those threads and there's not one rooted V20 to be found.
The fact of the matter is, a lot of people who come to XDA shouldn't be allowed anywhere near an ADB command or a one touch root.
On my short time with the Note 7, XDA showed me that it really wasn't smart to root that phone. Rooting broke too much of the stuff I used, and the developers didn't get enough time to iron out those problems. If they root this phone, I won't be doing it to mine until I see how all of the problems shake out.
douger1957 said:
Does someone really need to want to root his phone to be on XDA? There's a whole lot of learning and shared experience going on out in those threads and there's not one rooted V20 to be found.
The fact of the matter is, a lot of people who come to XDA shouldn't be allowed anywhere near an ADB command or a one touch root.
On my short time with the Note 7, XDA showed me that it really wasn't smart to root that phone. Rooting broke too much of the stuff I used, and the developers didn't get enough time to iron out those problems. If they root this phone, I won't be doing it to mine until I see how all of the problems shake out.
Click to expand...
Click to collapse
I think that's a good opinion. Mine is I want to be the administrator of my $800 hand computer. Not tmobile. Not LG, Samsung , or anyone else. I bought it. It's mine. If I want to block ads, or change the color of my clock then I should be able to. I agree on waiting for bugs to be fixed, but being able to flash a backup or backed up app is a nice feature. I miss the days where root came easy and we owned the rights to our devices. It's bull5hit!
Bubba Fett said:
I think that's a good opinion. Mine is I want to be the administrator of my $800 hand computer. Not tmobile. Not LG, Samsung , or anyone else. I bought it. It's mine. If I want to block ads, or change the color of my clock then I should be able to. I agree on waiting for bugs to be fixed, but being able to flash a backup or backed up app is a nice feature. I miss the days where root came easy and we owned the rights to our devices. It's bull5hit!
Click to expand...
Click to collapse
Amen to that lol! Do you know how long does it take to restore every single app when you dont have titanium backup installed and your device rooted? (i have 113 user apps in my lg g3), you can easily take up to 2 hours installing and setting up. while when you have titanium, you can sit there and drink up your coconut juice while it does everything on its own and everything already set up, and it is pretty quick too. Also, i hate ads. unless the benefit me (that's how i found out about the LG V20 lol) Not to mention that many of the ads out there are either scam or viruses . Also, rooting is the way to really owning your device. a device is not yours until whatever thing you want to do can actually be achieved because you (the owner) wanted to and not because the company wanted to. :good:
I need root for adblocking and xprivacy , that's it. No root within 15 days, its getting returned.
Amd4life said:
I need root for adblocking and xprivacy , that's it. No root within 15 days, its getting returned.
Click to expand...
Click to collapse
Lol you might as well return it now then. Beucase i doubt it will be done that quick. I mean, i bought this phone because of its great features. And even though i like to root, flash, and all that, well, i have set up my mind in a balanced mode and said "well, chances to get root are 50%, sure i like to root my phone but probably it wont be possible ". To be honest i usually wait about 3 month before buying a new released smartphone because by around that time, they usually have root and have gotten bugs already fixed. But i couldnt resist the offers on this one LOL. so, if it doesnt get root, i will stuck with it for a while anyway.
Amd4life said:
I need root for adblocking and xprivacy , that's it. No root within 15 days, its getting returned.
Click to expand...
Click to collapse
I'm in the exact same boat as you. My V20 is sitting all pretty on my desk. T-14 days before I return it if no root. Been rocking the OnePlus 3 with an awesome ROM since the first Note 7 recall. Absolutely loving it. Got the V20 only because of the screen, camera, and supposedly better sound--all of which are probably marginal upgrades compared to OP3 especially considering it's well over twice the price.
V521 didn't have root until update was released. I grabbed and uploaded the ROM, and soon rooted .dz was there.
Confirmed: Similar to T-Mobile LG G5 there are not flash commands in fastboot to write a new recovery. Will need someone to create a TOT file to get us TWRP and root I think.
confirmed that I have unlocked my t-mobile bootloader also. TRY THIS AT YOUR OWN RISK!!!!
booted into fastboot mode by
a) powering down the device
b) putting the cable into the PC USB drive
c) hold down - volume down button, insert USB-C cable into the phone.
d) check the USB drivers in device manager.
e) I manually installed USB driver using the google USB drive from SDK tools 2.2 (LG drivers may also work)
f) cmd, run as administrator, changed directory to my adb folder
g) fastboot oem device, listed my device (so im good to go)
h) [FONT=&quot]fastboot oem unlock (doing such will erase your phone)
I) fastboot getvar unlock[/FONT]
j) fastboot reboot
device boots with security warning (ie bootloader unlocked), boots fine, clean device
went back into fastboot tried to compile a basic TWRP using my v10 TWRP as a basis....fail on my coding skills ( I am still learning)
using command fastboot boot XXX.img
c:\adb>fastboot boot v20.img
downloading 'boot.img'...
OKAY [ 0.700s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.721s
Click to expand...
Click to collapse
lightninbug said:
Are you really on XDA posting this?...What do we need root for???... Maybe head to the T-Mobile forums bro.
Click to expand...
Click to collapse
Don't get your panties in a bunch. It was a simple question. I come on here to make money. I fix phones for a living and I come here to fix what people attempting to root broke and brought to me to fix. If you don't want to root, you don't have to. If you do, then by all means root your phone. No need to be a **** about it.
Sent from my SM-G928V using Tapatalk
Amd4life said:
confirmed that I have unlocked my t-mobile bootloader also. TRY THIS AT YOUR OWN RISK!!!!
booted into fastboot mode by
a) powering down the device
b) putting the cable into the PC USB drive
c) hold down - volume down button, insert USB-C cable into the phone.
d) check the USB drivers in device manager.
e) I manually installed USB driver using the google USB drive from SDK tools 2.2 (LG drivers may also work)
f) cmd, run as administrator, changed directory to my adb folder
g) fastboot oem device, listed my device (so im good to go)
h) [FONT=&quot]fastboot oem unlock (doing such will erase your phone)
I) fastboot getvar unlock[/FONT]
j) fastboot reboot
device boots with security warning (ie bootloader unlocked), boots fine, clean device
went back into fastboot tried to compile a basic TWRP using my v10 TWRP as a basis....fail on my coding skills ( I am still learning)
using command fastboot boot XXX.img
Click to expand...
Click to collapse
Apparently LG disables boot/flash. I'm going to try to get a tmobile TOT file tomorrow. I'm working on updating a TOT extractor tool right now to work it.
Can someone run this:
Code:
fastboot getvar all
Bubba Fett said:
I think that's a good opinion. Mine is I want to be the administrator of my $800 hand computer. Not tmobile. Not LG, Samsung , or anyone else. I bought it. It's mine. If I want to block ads, or change the color of my clock then I should be able to. I agree on waiting for bugs to be fixed, but being able to flash a backup or backed up app is a nice feature. I miss the days where root came easy and we owned the rights to our devices. It's bull5hit!
Click to expand...
Click to collapse
I will most likely root my phone when the time comes. I am not against rooting at all... I rooted all of my phones except the Note 7. What I'm saying is that root isn't for everyone, not everyone should root their phone even if they think it's the thing to do and that I think there's a place at XDA for people who don't want to learn ADB commands.

Resources