I had some problems using all the toolkit around and was not able to unlock my bootloader and root my phone. (Shame on me it was already three days since I got hands on my device). I had upgraded to 4.3 some toolkits didn't support my build etc.
Some pre-reqs:
1) BACKUP ( I back uped using the helium app, but forgot to backup my internal storage, and it too got wiped)
2) Thats all
I am using the wifi only version of this tablet (grouper)
I am using debian wheezy 7.2 64 bit
Here is what I did:
1)I installed adb and fastboot using wheezy-backports repository
Code:
apt-get install android-tools*
2) I connected my phone to my laptop in usb debugging mode and ran the following commands:
Code:
adb reboot bootloader
fastboot oem unlock
3) Then I downloaded the CF-ROOT script from this link
4)Extracted the file.
5)Some more commands
Code:
cd /path/to/extracted/folder/image
fastboot boot CF-Auto-Root-grouper-nakasi-nexus7.img
thats all folks, you have an unlocked bootloader and a rooted device.
That's the normal method if you don't use a toolkit! You are able to use that for example on windows too. It's nothing new
Sent from my Nexus 4 running Android 4.3
Yeah, I figured out that later! LOL
Thanks anyways
Related
Using a linux PC I was attempting to unlock my bootloader following the directions at http://www.geek.com/articles/mobile/how-to-unlock-and-root-the-nexus-7-2012081/.
I can execute adb reboot bootloader just fine.... however when I issue the fastboot oem unlock command nothing happens on the tablet, and I see "< waiting for device >" in the terminal window. If I CTRL-C to break out and then do a 'adb devices' I see that there are no devices listed.
The Nexus 7 is a stock 16gb, C70 running 4.1.2/JZO54K.
Probably unrelated - I noticed in the last couple of weeks that the tablet has become slugging/laggy. Available space was at about 2gb. I removed some storage hungry games and got available space back up to about 5.5 gb.... but it's still laggy and touch detection barfs on occasion.
Any help/advice would be greatly appreciated.
Being on Linux make sure hat your fastboot command either has suid-bit set and owner is set to root or you need to run the command by sudo:
sudo fastboot devices
For adb there should be no problems, but adb is not working if your device is in fastboot mode.
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
Being on Linux make sure hat your fastboot command either has suid-bit set and owner is set to root or you need to run the command by sudo:
sudo fastboot devices
For adb there should be no problems, but adb is not working if your device is in fastboot mode.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Uggg.... Years of using Odin has made me stupid and lazy.... sudo did the trick. Thanks!!
recently got a nexus 4 and now i trying to root but i need ADB well i installed the correct drivers and for it and then i go to use either nexus 4 tool kits and both say device is found but adb is offline i tried updating drivers even changing path for adb in environmental properties updated my sdk.. idk what else to do
do it the right way, use fastboot instead of a root toolkit. you dont need adb to root, all you need is fastboot.
fastboot oem unlock, fastboot flash a custom recovery, flash the su binaries or a custom rom in your new recovery, then reboot and profit.
KeemGoodFella said:
recently got a nexus 4 and now i trying to root but i need ADB well i installed the correct drivers and for it and then i go to use either nexus 4 tool kits and both say device is found but adb is offline i tried updating drivers even changing path for adb in environmental properties updated my sdk.. idk what else to do
Click to expand...
Click to collapse
The toolkits are using an outdated version of adb, 4.2.2 requires the latest release, and will have to be updated by their developers before they will work again.
http://forum.xda-developers.com/showpost.php?p=37989017&postcount=956
Hi all,
First let me start by saying that I've been trying to get past this for the last 2 days. I just bought a nexus 10 (YAY!), However when i try to root it via skipsoft toolkit, i get the above error code...
Ive done the ctrl+shift+del and stopped any running adb processes, I've switched usb ports, and cannot figure this out. Am i missing a completely obvious step here? I've rooted many items using rhe same computer, and same type of toolkits offered by Mark... Any help would be truly appreciated!
Cheers,
Well its a nexus, toolkits are from needed
fastboot oem unlock
All data is wiped here, now make a choice for stock rooted or custom rom, but youre on xda so next steps
fastboot flash recovery nameofrecovery.img
Now reboot to new recovery (twrp is a good choice)
And flash rom and or any gapps here
If none on device, which after unlock i doubt it, use an otg cable or adb sideload
Then reboot, all takes 5min tops
For your adb issue make sure you update your sdk, then open cmd/terminal and type
adb kill server
adb start server
If you just want stock rooted or cant find needed files let me know
Happy flashing
Sent from my SGH-T699 using XDA Premium 4 mobile app
Hi.
First I have to apologize for being a noob, and if I am posting questions that has already been answered. I can't post these question in the original thread about F2FS file system, so I am posting this here.
I am currently running stock Android 4.4.4 on my Nexus 7 WiFi (2012), and because it has become very slow, I want to root, install Cyanogenmod and use F2FS file system.
I have used CWM-recovery and installed custom roms on a Huawei device before, so I have some experience with this. I have also some experience with Linux and using ADB. But I don't want to brick my Nexus 7, so I have some questions before I start:
I want to unlock the bootloader and install custom recovery. I want to avoid using toolkits, as I don't know what they installs on my Nexus 7. I found a tutorial here that I am using, but I am not 100% sure if I am following the correct steps?:
1. Install SDK and drivers
2. Enable Debug on the Nexus 7
3. Download CWM-recovery to the same directory as adb.exe on my PC running Windows 8.1
4. With CMD: run command "adb reboot bootloader" then run command "fastboot oem unlock" (I know this will delete all data on my Nexus 7)
5. After unlocking, flash CWM-recovery with the steps from the tutorial: run command "fastboot flash recovery recovery-clockwork-touch-6.0.4.3-grouper.img".
6. Permanent flash CWM-recovery: mount "/System" and rename/backup "recovery-from-boot.p" with the command "mv recovery-from-boot.p recovery-from-boot.bak" (Is this step necessary? I have seen other tutorials skipping this step.)
7. Backup everything from recovery, and move the backup from the Nexus 7 to my PC. (I don't know if this step is necessary, but I'll do it anyway)
Are these seven steps above correct, or am I missing something? If the steps above are correct, then can I now install CM11 Snapshot M7 with F2FS with these steps?:
1. Download and copy "CM11.zip", "gapps.zip" and "LegoKernel-F2FS-140228.zip" from PC to Nexus 7, then install them from CWM-recovery.
2. Download "recovery-F2FS-A.img" to the same directory as adb.exe
3. Reboot the Nexus 7 into Android(CM11), activate Debug, run command "adb reboot bootloader" then flash custom TWRP with the command "fastboot flash recovery recovery-F2FS-A.img"
4. Reboot into TWRP-recovery, go to Wipe menu and format data.
5. Reboot into Android(CM11)
Will these seven+five steps work, or am I missing something? I don't want to brick my Nexus 7, so if someone could verify that these steps is correct, that would be great.
And one more question: Can I change back to CWM-recovery without losing the F2FS file system, or should I just use TWRP?
~Liloolil
Hi!
Liloolil said:
I am currently running stock Android 4.4.4 on my Nexus 7 WiFi (2012), and because it has become very slow, I want to root, install Cyanogenmod and use F2FS file system.
I have used CWM-recovery and installed custom roms on a Huawei device before, so I have some experience with this. I have also some experience with Linux and using ADB. But I don't want to brick my Nexus 7, so I have some questions before I start:
I want to unlock the bootloader and install custom recovery. I want to avoid using toolkits, as I don't know what they installs on my Nexus 7. I found a tutorial here that I am using, but I am not 100% sure if I am following the correct steps?:
1. Install SDK and drivers
2. Enable Debug on the Nexus 7
3. Download CWM-recovery to the same directory as adb.exe on my PC running Windows 8.1
4. With CMD: run command "adb reboot bootloader" then run command "fastboot oem unlock" (I know this will delete all data on my Nexus 7)
5. After unlocking, flash CWM-recovery with the steps from the tutorial: run command "fastboot flash recovery recovery-clockwork-touch-6.0.4.3-grouper.img".
6. Permanent flash CWM-recovery: mount "/System" and rename/backup "recovery-from-boot.p" with the command "mv recovery-from-boot.p recovery-from-boot.bak" (Is this step necessary? I have seen other tutorials skipping this step.)
7. Backup everything from recovery, and move the backup from the Nexus 7 to my PC. (I don't know if this step is necessary, but I'll do it anyway)
Click to expand...
Click to collapse
The tutorial sounds ok to me even though adb is not even needed to unlock the bootloader and flash a new recovery.
Instead you might need "fastboot" for this. Oh and I would use TWRP instead of CWM on the Nexus 7 (it includes F2FS support out of the box):
Code:
fastboot oem unlock
fastboot flash recovery openrecovery-twrp-2.7.1.1-grouper.img
Liloolil said:
Are these seven steps above correct, or am I missing something? If the steps above are correct, then can I now install CM11 Snapshot M7 with F2FS with these steps?:
1. Download and copy "CM11.zip", "gapps.zip" and "LegoKernel-F2FS-140228.zip" from PC to Nexus 7, then install them from CWM-recovery.
2. Download "recovery-F2FS-A.img" to the same directory as adb.exe
3. Reboot the Nexus 7 into Android(CM11), activate Debug, run command "adb reboot bootloader" then flash custom TWRP with the command "fastboot flash recovery recovery-F2FS-A.img"
4. Reboot into TWRP-recovery, go to Wipe menu and format data.
5. Reboot into Android(CM11)
Will these seven+five steps work, or am I missing something? I don't want to brick my Nexus 7, so if someone could verify that these steps is correct, that would be great.
And one more question: Can I change back to CWM-recovery without losing the F2FS file system, or should I just use TWRP?
~Liloolil
Click to expand...
Click to collapse
As long as you can boot through fastboot, it should be ok to make experiments. I don't think that you can brick the device permanently.
Your tutorial again sounds good but I would choose a few different files instead. LegoKernel is from February 2014, there are other kernels in newer versions available...
I have just posted a howto for this in another thread: http://forum.xda-developers.com/showpost.php?p=54004629&postcount=3342
Good luck!
michael_ch said:
Hi!
The tutorial sounds ok to me even though adb is not even needed to unlock the bootloader and flash a new recovery.
Instead you might need "fastboot" for this. Oh and I would use TWRP instead of CWM on the Nexus 7 (it includes F2FS support out of the box):
Code:
fastboot oem unlock
fastboot flash recovery openrecovery-twrp-2.7.1.1-grouper.img
As long as you can boot through fastboot, it should be ok to make experiments. I don't think that you can brick the device permanently.
Your tutorial again sounds good but I would choose a few different files instead. LegoKernel is from February 2014, there are other kernels in newer versions available...
I have just posted a howto for this in another thread: http://forum.xda-developers.com/showpost.php?p=54004629&postcount=3342
Good luck!
Click to expand...
Click to collapse
Thank you! I have now successfully rooted and installed CM11 on my Nexus 7.
Credit goes to @Vincent_vann for offering original and patched boot image
Prerequisite:
You should have ADB installed
LG unified driver 4.2.0 or later installed
USB cable and battery should be at least 60%
Bootloader unlocked
Code:
fastboot oem unlock
Data should be backed up
USB debug should be enabled and your host computer is allowed
Patched boot image downloaded https://mega.nz/#F!zLIkzbwY!-sPXZvcv30t6oxyuOqdFfg
Steps
1. Plug your tablet to your host computer.
2. Open your command prompt and locate your ADB folder and enter the following
Code:
adb devices
You should see your device
3. Go to bootloader
Code:
adb reboot bootloader
If you have not unlocked bootloader, do it now
Warning: your data on the tablet will be wiped!!!
Code:
fastboot oem unlock
4. Flash your boot image. Locate the folder where the patched_boot.img is
Code:
fastboot flash boot
make sure you have pressed a space. Drag and drop the patched boot into the command prompt and press Enter. It should say OK
5. Restart
Code:
fastboot reboot
6. Make initial setup, enable developer option again and USB debug, and enable unknown source in Security Settings
7. Download and install Magisk Manager, and upgrade when necessary.
8. Your tablet is rooted.
How much can we expect to speed this tablet up with just root?
@mingkee, thanks for the tutorial. Finally got around to doing it. All good.
For Magisk, do we use it as a basic root or can modules be used. Haven't done anything on it yet (powered off and charging).
ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HellsGate Kernel, Multiboot, Tapatalk 4.9.3
marcdw said:
@mingkee, thanks for the tutorial. Finally got around to doing it. All good.
For Magisk, do we use it as a basic root or can modules be used. Haven't done anything on it yet (powered off and charging).
ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HellsGate Kernel, Multiboot, Tapatalk 4.9.3
Click to expand...
Click to collapse
I have not added other module.
I root this table so I can install CF.Lumen to fix that muddy tint.
Ahh thanks for this!! I haven't had root in any device for awhile. hoping for twrp soon. Let me know if I can assist in any way!
These instructions are not fully understandable please advise after step 4. Flash your boot image. Locate the folder where the patched_boot.img is
Code: fastboot flash boot this is very very vague please give more information on how this is setup some people have ADB and ANDROID installers installed. You need to fix the steps please.
Ice
ice5192 said:
These instructions are not fully understandable please advise after step 4. Flash your boot image. Locate the folder where the patched_boot.img is
Code: fastboot flash boot this is very very vague please give more information on how this is setup some people have ADB and ANDROID installers installed. You need to fix the steps please.
Ice
Click to expand...
Click to collapse
Yeah, that does sound kind of odd.
What it means is type in (no quotes) "fastboot flash boot " ( note the space after) and then you are to drag the patched_boot.img file into the cmd window to complete the line.
Not necessary if the file is in the same directory as fastboot. So full line is
"fastboot flash boot patched_boot.img"
I too had to reread that line of instruction a couple of times.
LG G3 D851, CyanogenMod CM12.1 ROM, Fechda R7 Kernel, MultiROM, Tapatalk 4.9.5
Is anyone using TWRP? What version?
I've tried it and not getting anywhere.
adb devices - shows the tablet
fastboot devices - shows nothing connected
fastboot oem unlock - <shows waiting on any devices>
anyone else run into this?
beymapwrd said:
I've tried it and not getting anywhere.
adb devices - shows the tablet
fastboot devices - shows nothing connected
fastboot oem unlock - <shows waiting on any devices>
anyone else run into this?
Click to expand...
Click to collapse
Did you install the LG driver's? Happened to me because I forget to install the LG unified drivers. Link in OP
Sent from my [device_name] using XDA-Developers Legacy app
Some one created Twrp for our tablets, but I can't figure out why when I try to reboot into it , it goes to the fastboot screen...anybody??
Drivers installed, had to run first:
adb kill-server
adb start-server
then the rest of the commands..
coolchris305 said:
Some one created Twrp for our tablets, but I can't figure out why when I try to reboot into it , it goes to the fastboot screen...anybody??
Click to expand...
Click to collapse
where did you get the twrp from i cant find it anywhere i see other models but not lg v530
itzmehotsauce said:
where did you get the twrp from i cant find it anywhere i see other models but not lg v530
Click to expand...
Click to collapse
Download twrp builder...but even then i still can't boot into it...
coolchris305 said:
Download twrp builder...but even then i still can't boot into it...
Click to expand...
Click to collapse
well i got it rooted withthe method from this thread but when i go into rootchecker it says its not rooted im guessing its because i dont have su installed but i cant install the su without twrp if im not mistaken so im a bit confused its been a while since i rooted anything
itzmehotsauce said:
well i got it rooted withthe method from this thread but when i go into rootchecker it says its not rooted im guessing its because i dont have su installed but i cant install the su without twrp if im not mistaken so im a bit confused its been a while since i rooted anything
Click to expand...
Click to collapse
Yeah. Rootchecker confirms I have root on mines
I've run into the same issue. The image seemed to have been flashed, but whenever I try to boot into recovery it just goes to fastboot (bootloader).
Canadian Variant
Anyone know if there's any general rule to modifying stuff to work with other models? Other than build.prop edits to v533 instead of v530 I'm at a loss, and I'm guessing the boot image is specific to T-Mobile variants..
There's gotta be a way to work off this framework, but again I've got no idea, and it may be way beyond my skill level
So I've had this tablet since March but really haven't used it much. My question is once I root it using your written guide do you recommend a app to use for getting Free Hotspot Tether on it? I am a 11 year tenure TMO Customer & have a legacy grandfathered rate/data plan.
Even tho my data plan says I have unlimited hotspot tether it is blocked by TMO. I have reached out to T-Mobile on Twitter & even the executive resolutions team of the president office but they just said that at one point it was allowed but that TMO took it away for whatever reason.
So rather than fighting tthem further or getting the FCC or FTC involved for false advertising I figured I'll just use an app once rooted to bypass root. Just wondering if anyone knows what is the best app to use to achieve this once rooted. Thank you very much & have a wonderful day!! ?
All the best,
Ron.
---------- Post added at 04:13 PM ---------- Previous post was at 04:09 PM ----------
mingkee said:
Credit goes to @Vincent_vann for offering original and patched boot image
Prerequisite:
You should have ADB installed
LG unified driver 4.2.0 or later installed
USB cable and battery should be at least 60%
Bootloader unlocked
Code:
fastboot oem unlock
Data should be backed up
USB debug should be enabled and your host computer is allowed
Patched boot image downloaded https://mega.nz/#F!zLIkzbwY!-sPXZvcv30t6oxyuOqdFfg
Steps
1. Plug your tablet to your host computer.
2. Open your command prompt and locate your ADB folder and enter the following
Code:
adb devices
You should see your device
3. Go to bootloader
Code:
adb reboot bootloader
If you have not unlocked bootloader, do it now
Warning: your data on the tablet will be wiped!!!
Code:
fastboot oem unlock
4. Flash your boot image. Locate the folder where the patched_boot.img is
Code:
fastboot flash boot
make sure you have pressed a space. Drag and drop the patched boot into the command prompt and press Enter. It should say OK
5. Restart
Code:
fastboot reboot
6. Make initial setup, enable developer option again and USB debug, and enable unknown source in Security Settings
7. Download and install Magisk Manager, and upgrade when necessary.
8. Your tablet is rooted.
Click to expand...
Click to collapse
Hello would you happen to know of a app to use with this to get Free Hotspot Tether for TMO once I Root it. Hotspot is currently blocked on my legacy grandfathered data plan even tho my plan shows I have unlimited hotspot tether.
So rather than fighting T-mobile regarding this I figure I'll just root & use an app to get my free hotspot tether back. Thank you very much & have a wonderful day!! ?
@QkTreasures, I use WiFi Tether Router. Had it a few years. It works for the most part. Sometimes I can go hours tethering without using my hotspot data but there's been a time or two where it didn't hide the tethering.
LG G3 D851, PAC-MAN LP ROM, MultiROM, XDA Legacy