[Q] HELP! changed windows and phone is now unusable! - GT540 Optimus General

so my laptop recently crashed and the ony way to get it back was to re-installl windows which is what i did, but after setting my laptop back up i try to install the new cm7 v1.8 but when i go into cmd and type fastboot.exe -w
it comes back with " fastboot .exe" is not recognized as an internal or external command
i have tryed to install the fastboot drivers ( but i cant seem to find how to, because the computer recognizes the phone as fastboot and doesnt have a problem with it). can anyone please help i have been trying for 3 days now and i have no phone :'(

hi friend
I think u need to check the following thinks
1) had you placed the total folder which contains necessary file (the folder must contain the following files . adb.exe , AdbWinApi.dll , AdbWinUsbApi.dll , boot.img , fastboot.exe , flash_all.bat , flash_all_nowipe.bat , flash_boot_nowipe.bat , flash_system_nowipe.bat , system.img )
if you downloaded V1.8 from the link then the file will not have this all file so you need to download all this so if you are not able to download just mail me at [email protected] i will send all this file then you can able to carry out the flashing of ROM as per the following guide
Checklist:
adb - needed to flash the ROM
fastboot - needed to flash the ROM
AdbWinApi.dll - needed to flash the ROM
AdbWinUsbApi.dll - needed to flash the ROM
boot.img - the boot part of the ROM
system.img - the actual OS
***EXTRACT THE CONTENTS OF THIS ZIP FILE IN A FOLDER CALLED ANDROID ON THE C: DRIVE (you need to create the folder)***
1. Open CMD with administrator privileges (Search for CMD in the start menu and right click on 'cmd' and click 'Run as Administrator' )
2. Prepare the phone by switching it off and holding 'Volume Down' + 'Camera' whilst powering on again, the phone should then display the LG logo then show a blank screen, this indicates the phone is now in fastboot mode.
(i) connect the phone to the computer via USB cable, and wait for the necessary drivers to install
2. Then type into the cmd window:
'cd C:\Android' (without the '')
(i) Then type:
'fastboot.exe -w' (without the '')
(ii) Once that's completed, type:
'fastboot.exe erase system' (without the '')
(iii) Once that's completed, type:
'fastboot.exe flash system system.img (without the '')
(iv) Once that's completed, type:
'fastboot.exe flash boot boot.img' (without the '')
(v) Once that's completed, type:
'fastboot.exe reboot' (without the '')

Have u changed tha envoirnment parameters?
Sent from my GT540 using XDA App

i am assuming that you have to download sdk for the adb files? the thing is i didnt download it before and it all worked through cmd? and im not sure what the enviromentable thing is ?

there are some downloadable packages on xda wich have all the files needed extracted from the android sdk. Just download the android sdk and use cmd to go to the tools directory and use fastboot. it will work (possibly have to copy some dll files from an other directory to ..\tools\

thanks everyone for their help!! will download these files for future use. but found this and downlaoded it and it install for me!! XD
http://download975.mediafire.com/zchh935v5omg/hw03ruc1qeiancu/Install+SwiftDroid+v
by the way do you know where i could find the extracted files?http://media.xda-developers.com/images/smilies/smile.gif

Just Write
cd C:\Android ... or where ever you extracted it and hit enter

Related

[Q] Please Help!!!!!Rogers magic

Rogers magic in continuous reboot
I have a ROGERS MAGIC that is in continuous reboot. I Have to take the battery out to get it to power off. I have done a hard reboot but still have the same result. I got tired of waiting for an update from 1.5 from rogers and was using the new cyangon Rom using ROM Manager.I can get the fastboot screen up but I don't have a clue what to try next. Any help would be greatly appreciated.
This is the procedure I used to root my Rogers' Magic and worked just fine...I guess if you do this from the beginning that will work for you too
I have not created this list or did the research for it, another great man has done it! Kudos!
MANUAL PROCEDURE FOR ROGERS MAGIC
Status of script will be written at bottom of file
.
You must have ADB working to connect to your magic before this procedure will work.
On XP machines, you can install HTC sync on your PC, put the phone into USB-debugging
and connect it to the PC. The correct drivers should install automaticly, if not, Google will
be your friend.
.
1. Make sure that the listed files are present in the folder with the Rootme.bat file
.
a) update-cm-5.0.8-DS-signed.zip
b) bc-5.0.8-ebi1-signed.zip
c) gapps-ds-ERE36B-signed.zip
d) exploid
e) Radio_HTC_PVT_32A_3.22.26.17.img
f) hboot-1.33.2010.img
g) recovery-RA-sapphire-v1.7.0H.img
h) update-hboot-1.76.2007-signed.zip
i) recovery-RA-hero-v1.6.2.img
.
2. Connect your magic to your PC and enable USB debugging on your phone.
.
3. Open up a command window and navigate to the directory containg the data
files that need to be sent to your phone.
.
4. Using the syntax "ADB PUSH {file name} {location}" push the following files to
phone. Pay attention to the "/" and make sure you don't miss or add any
a) update-cm-5.0.8-DS-signed.zip to folder /sdcard/
b) bc-5.0.8-ebi1-signed.zip to folder /sdcard/
c) gapps-ds-ERE36B-signed.zip to folder /sdcard/
d) exploid to folder /sqlite_stmt_journals
e) recovery-RA-hero-v1.6.2.img to folder /data/local
f) update-hboot-1.76.2007-signed.zip to folder /sdcard/
.
Eg: adb push update-cm-5.0.8-DS-signed.zip /sdcard/
.
5. Run the following commands in the command window
a) adb shell chmod 777 /sqlite_stmt_journals/exploid
b) adb shell /sqlite_stmt_journals/exploid
.
6. Turn bluetooth on and then off on your magic
.
7. Unplug and then replug the usb cable from your magic
.
8. Enter the following commands into the command window
a)adb shell (you will get a $ prompt)
b)rootshell (you will be prompted for a password)
c)secretlol (you will get a # prompt)
d)chmod 666 /dev/mtd/mtd1
e)exit (you will be back to $ prompt)
f)flash_image recovery /data/local/recovery-RA-hero-v1.6.2.img
g)exit
.
9. Turn off your phone.
.
10. Boot into recovery by holding the Home + Power keys.
.
11. Using the trackball, select "Flash ZIP from SD Card"
.
12. Select update-hboot-1.76.2007-signed.zip
.
13. Press the HOME key to confirm selection.
14. Reboot phone as requested. It will boot back into recovery.
14. Enter the fillowing into the command windown
a)adb shell reboot bootlaoder
.
15A. When phone has booted into fastboot enter the following into the command window.
a)fastboot flash radio Radio_HTC_PVT_32A_3.22.26.17.img
b)fastboot flash hboot hboot-1.33.2010.img
c)fastboot flash recovery recovery-RA-sapphire-v1.7.0H.img
d)fastboot reboot-bootloader
.
16. When phone has booted into fastboot enter the following inot the command window.
a)fastboot erase system -w
b)fastboot erase boot
c)fastboot oem powerdown
.
17. After phone powers off, reboot into recovery by holding Home + Power keys.
.
18. Using the trackball, select "Flash ZIP from SD Card" and flash the following files.
Select the home key to confirm each file
a)update-cm-5.0.8-DS-signed.zip
b)bc-5.0.8-ebi1-signed.zip
c)gapps-ds-ERE36B-signed.zip
.
19. After the last file has finished flashing reboot the phone normally.
It can take anywhere from 5-15 min for the first boot.

Cannot get fastboot working in command line (win 7)

Hi to all I have a provlem I need help with.While trying to unlock my bootloader using rsd and fastboot.I get as far as the cmd line entries and have problems basically I cant seem to get my command line to use the fastboot command and or any other fastboot command I can find.What seems to happen all the time is that the command line responds with "this is not an internal or external command" or similar.
Any help appreciated Windows 7 64bit all latest drivers installed
scotty7910 said:
Hi to all I have a provlem I need help with.While trying to unlock my bootloader using rsd and fastboot.I get as far as the cmd line entries and have problems basically I cant seem to get my command line to use the fastboot command and or any other fastboot command I can find.What seems to happen all the time is that the command line responds with "this is not an internal or external command" or similar.
Any help appreciated Windows 7 64bit all latest drivers installed
Click to expand...
Click to collapse
are you in the same folder that the FASTBOOT.EXE is in when you run the command???
Make sure your running CMD as administrator. You can tell by the path that shows when cmd is launched. If its a regular user account it will path to something like: c:\users\"your username"\
If your running as admin it will path to something like: c:\windows\system32
Sent from my MB860 using XDA Premium App
Take your fastboot files and images and put them in a folder on the root of your C: drive... I use one named phone
Then you should be able to open your Command line and type
cd c:\phone
That will change you to the Phone directory you made in the root of C: earlier
If you want to make sure you can type DIR and it should list all the files you have in there.
At this time you can start using your fastboot commands and it will recognize them.
beatphreek said:
Take your fastboot files and images and put them in a folder on the root of your C: drive... I use one named phone
Then you should be able to open your Command line and type
cd c:\phone
That will change you to the Phone directory you made in the root of C: earlier
If you want to make sure you can type DIR and it should list all the files you have in there.
At this time you can start using your fastboot commands and it will recognize them.
Click to expand...
Click to collapse
Another handy thing is to open the folder then hold the shift key and then right click. You'll have an "Open command window here" option.
Yep I use that all the time...
used both the suggestions in here and still having trouble,can do the root of c folder,use the dir command see it is all there but the cd C:\fastbootpackage brings the same response again.Can anyone see where I am going wrong?Once the command line changes to fastboot what do I need to command?Phone is still attached (as per the guide I am following?)showing 100% phone needs manually rebooted.
I have all latest drivers on win 7 64bit and I am definetely running cmd as an administrator
Also as the third suggestion suggests if I open the cmd box from the folder what is the exact command to use from there?Is there an alternative to doing this as I am beginning to struggle?
Unlock your Bootloader
1. You need to download and install RDS lite on your PC:http://forum.xda-developers.com/attachment.php?attachmentid=634879&d=1308872277
2. Download and extract IHOP_Bell.rarhttp://api.viglink.com/api/click?format=go&drKey=1359&loc=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1136261&v=1&libid=1311795928774&out=http%3A%2F%2Fdiamantephoto.com%2FIHOP_Bell.rar&ref=http%3A%2F%2Fforum.xda-developers.com%2Fforumdisplay.php%3Ff%3D997&title=%5BPUDDING%5D%20International%20House%20of%20Pudding!%20(Unlock%2Froot%20thread)%20Updated%20July%2023%202011%20-%20xda-developers&txt=http%3A%2F%2Fdiamantephoto.com%2FIHOP_Bell.rar
3. Download and extract Fastboot tools http://gititbit.ch/FAST
4. Power down your Motorola Atrix
5. Take out your microSD card and SIM*card*for the flashing process
6. While turning the phone on, hold the Volume Up button until it acknowledges RSD
7. Your device will say “Starting RSD protocol support”
8. Run “RSD Lite” on your computer
9. Press the “. . .” button next to the box labeled “Filename”
10. Load up the SBF file – IHOP_Bell.sbf
11. Plug your device into your computer
12. RSD Lite should recognize your device and say “Model: NS Flash Olympus” and “Connected…”
13. Press the “Start” button
14. Be patient while the phone*reboots. It will take a long time.
15. Open and extract the Fastboot package from above
16. Open a command prompt window
a.On Windows, press Start and type “cmd” then press the enter button
17.Type the following command. Your directory will be the folder where you extracted the Fastboot package.
(Example:* cd C:\Users\Kenneth\Desktop\fastboot-package)
a.cd*your directory here
18. Power down your Atrix device
19. Hold the power button and the downward volume button until you see “Fastboot”
20. Let go of the buttons and press the upward volume button once
21. You will now see “Starting Fastboot protocol support”
22. Plug your device into a USB port in the back slot of your computer
a.Front slots sometimes do not have enough power to stay connected to the device.
23. Type the following command:
a.fastboot oem unlock
24. You will now receive a warning along with a unique device ID
25. Type the following commands using your unique device ID in place of the ####:
a.fastboot oem unlock ####
b.fastboot reboot
26. Wait for your device to reboot. Congratulations! You now have an unlocked bootloader!
This is the guide I have been using, thanks again
scotty7910 said:
"this is not an internal or external command"
Click to expand...
Click to collapse
This msg will only show if you are in different folder than your fastboot. You don't need to run cmd as administrator. The best thing to do is:
copy those 3 files (AdbWinApi.dll, AdbWinUsbApi.dll, fastboot.exe) to your main c:\ (do not put to the folder)
Run cmd and type "cd \" this will move you to c:\
Now type fastboot and press enter - you should see various commands that can be used. (your mobile doesn't need to be connect to your pc to see this)
Now you can continue with unlocking. If you applied ihop.sbf already then startt from step 18.
I'm 99% sure that you were in the wrong folder.
Thanks very much that last post got it.In fact I would say that is the simplest way I have read so far as far as fastbooting goes.Many thanks.I have been having problems installing tenfars cwm so I will be using the rom manager "official cwm,will using the fastboot-w command be a problem for me do you think?
scotty7910 said:
Thanks very much that last post got it.In fact I would say that is the simplest way I have read so far as far as fastbooting goes.Many thanks.I have been having problems installing tenfars cwm so I will be using the rom manager "official cwm,will using the fastboot-w command be a problem for me do you think?
Click to expand...
Click to collapse
Don't use the Rom Manager app. It sucks and doesn't work properly. Do things properly.
With XDA forum members there's no reason to do things half assed. Use your hole ass, dammit.
scotty7910 said:
Thanks very much that last post got it.In fact I would say that is the simplest way I have read so far as far as fastbooting goes.Many thanks.I have been having problems installing tenfars cwm so I will be using the rom manager "official cwm,will using the fastboot-w command be a problem for me do you think?
Click to expand...
Click to collapse
Well if you came that far then try to install tenfar's recovery, download this file :recovery-en-goapk-0630-1029.zip Unzip and move recovery-en-goapk-0630-1029.img to your c:\....Now reboot your phone and enter to fastboot mode. In cmd go to c:\ and type "fastboot flash recovery recovery-en-goapk-0630-1029.img" and then "fastboot reboot" DONE
If you have any problems try to download moto-fastboot (http://forum.xda-developers.com/attachment.php?attachmentid=635584&d=1308928440). It's kind of the same thing as fastboot and to be honest I don't know what's the different between both (I think moto-fastboot is designed for 2.3.4 firmware). Extract zip and move moto-fastboot to c:\ and type the same command but instead of fastboot type moto-fastboot. I hope this make sense.
Also it's recommended to delete "install_recovery.sh" which apparently is in /system/etc/ BUT I never managed to find this file and I just ignored this step.
thanks foka, but I have already tried and tried again unsuccessfully to use tenfars cwm.I can install the recovery and delete the sh file all as normal using fastboot and astro.However for some reason there seems to be no way I can get into cwm having flashed it.when I attempt it I dont see the same menu I could scroll through as before.Then I tried a cwm of tenfars that was supposed to flash through rom manager.Again the flash went fine but could not seem to enter recovery mode.I see you installed aura 1.1 didi you flash a radio afterwards?My signal is comnstantly 1 bar.Could you reccomend a uk radio?
Well Ive flashed at&t radio N_01.77.30p which solved battery draining and 1 bar issue. I'm not sure why you can't use cwm recovery...
Sent from Motorola Atrix
What do you mean you don't see the same menu as before? When you hold volume down, power up phone, fastboot, scroll through the list and none of them say Android Recovery?

Need help returning to stock

I purchased my nexus 7 from Walmart. The first thing I did was unlock and root it. But it turns out that my nexus has the screen flicker hardware issue. So how do I unroot, relock, and return to stock?
I think Google gives the factory .img's that I could flash through fast boot, but will that relock the boot loader and unroot it?
Also does the splash screen keep the 'unlocked' icon after being relocked?
That's a lot of questions, but if anyone can help that'd be great. Thanks!
Sent from my Nexus 7 using xda app-developers app
EDIT: since its a hardware issue, can I just factory reset? Its not like the people at Walmart will know...
you can follow this guide.
1. Download the 4.1 (JRN84D) image files to your computer. A direct download link is found here: [Only registered users can view links. ]
While a link to the Google page you can search on if you need, is here: [Only registered users can view links. ]
2. Extract the files from that downloaded file. This will give you a folder called "nakasi-jrn84d-factory-8b0bd791"... inside of which you will find a folder called "nakasi-jrn84d"... and inside of that you will see the files we are going to fastboot to your tablet. We want to place these files into the folder we located earlier which contains our "fastboot" file. Move or copy them over to that folder.
Note: On Linux/Ubuntu you may just extract them to any easily located folder.. Create a new one on the desktop or your home folder is my recommendation.
For reference, there should be 4 files, named:
bootloader-grouper-3.34.img
flash-all.sh
flash-base.sh
image-nakasi-jrn84d.zip
3. Open a command prompt inside the folder we have set up our files in. On windows this can be done by holding shift as you right-click in the folder, then select "Open command window here". On Mac or on a Linux system you want to open a terminal/command prompt and navigate to that folder using "cd" or "change directory" commands. For example if your folder is called "fastbootfiles" and it is on your desktop, you would enter:
Code:
cd desktop
Code:
cd fastbootfiles
4. Power down your tablet. Reboot into the bootloader by holding Volume Down + Power until you see the bootloader screen. In red letters toward the top of the text you will see fastboot mode. Once here, plug it into your computer.
5. Let's make sure you have your fastboot drivers installed and recognizing your device. Enter in the command prompt:
Code:
fastboot devices
For Mac:
Code:
./fastboot-mac devices
And press enter. You should see "List of attached devices" Followed by a string of numbers. If you do not see this, you do not have your drivers installed correctly! Go back to Zero Neck's Unlocking guide and grab the correct drivers, and make sure you install them correctly. You can also find the procedure during the video posted by Ragnarokx.
If you got the expected response, let's move on to fastbooting you back to stock...
6. This first command is going to wipe all your old EVERYTHING from the device. Credit to our resident AC cowboy, Jerry Hildenbrand, for pointing out to me a minor bug with the Nexus 7 bootloader that makes this a wise step to do first. Type each of these lines followed by Enter between them, waiting for one to finish before moving on to the next:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
7. This command will flash the stock bootloader on to your device. Enter:
Code:
fastboot flash bootloader bootloader-grouper-3.34.img
And press enter. Make sure you type the command exactly as you see it.
Note: As we noted earlier, replace "fastboot" above with the exact name of the fastboot file in your folder, for your system, such as "fastboot-windows" or "fastboot-mac". Addtionally for Mac's only, the command should be entered as such
Code:
./fastboot-mac flash bootloader bootloader-grouper-3.34.img
Noting the period and forward slash before the command.
Going forward you Mac folks just remember that with the rest of the commands
Now reboot the bootloader:
Code:
fastboot reboot-bootloader
Enter.
8. This next command will both wipe your old system and flash the factory image in its place, which includes the stock system, recovery, kernel, and userdata partitions:
Code:
fastboot -w update image-nakasi-jrn84d.zip
Enter, and wait, make sure the command finishes. This might take a few minutes.
Reboot the bootloader again:
Code:
fastboot reboot-bootloader
Enter.
9. We are done with the hard part... pretty easy right? Now we're just going to lock that bootloader.
Code:
fastboot oem lock
Enter.
Yes, this step is optional but I strongly recommend it if you had issues earlier which led to this procedure. Now you can unlock again if you like, which will give your tablet that final full wipe to clear out any bad data remaining:
Code:
fastboot oem unlock
Enter.
10. Finally, reboot and setup your tablet again from scratch!
Code:
fastboot reboot
5implelove said:
you can follow this guide.
1. Download the 4.1 (JRN84D) image files to your computer. A direct download link is found here: [Only registered users can view links. ]
While a link to the Google page you can search on if you need, is here: [Only registered users can view links. ]
2. Extract the files from that downloaded file. This will give you a folder called "nakasi-jrn84d-factory-8b0bd791"... inside of which you will find a folder called "nakasi-jrn84d"... and inside of that you will see the files we are going to fastboot to your tablet. We want to place these files into the folder we located earlier which contains our "fastboot" file. Move or copy them over to that folder.
Note: On Linux/Ubuntu you may just extract them to any easily located folder.. Create a new one on the desktop or your home folder is my recommendation.
For reference, there should be 4 files, named:
bootloader-grouper-3.34.img
flash-all.sh
flash-base.sh
image-nakasi-jrn84d.zip
3. Open a command prompt inside the folder we have set up our files in. On windows this can be done by holding shift as you right-click in the folder, then select "Open command window here". On Mac or on a Linux system you want to open a terminal/command prompt and navigate to that folder using "cd" or "change directory" commands. For example if your folder is called "fastbootfiles" and it is on your desktop, you would enter:
Code:
cd desktop
Code:
cd fastbootfiles
4. Power down your tablet. Reboot into the bootloader by holding Volume Down + Power until you see the bootloader screen. In red letters toward the top of the text you will see fastboot mode. Once here, plug it into your computer.
5. Let's make sure you have your fastboot drivers installed and recognizing your device. Enter in the command prompt:
Code:
fastboot devices
For Mac:
Code:
./fastboot-mac devices
And press enter. You should see "List of attached devices" Followed by a string of numbers. If you do not see this, you do not have your drivers installed correctly! Go back to Zero Neck's Unlocking guide and grab the correct drivers, and make sure you install them correctly. You can also find the procedure during the video posted by Ragnarokx.
If you got the expected response, let's move on to fastbooting you back to stock...
6. This first command is going to wipe all your old EVERYTHING from the device. Credit to our resident AC cowboy, Jerry Hildenbrand, for pointing out to me a minor bug with the Nexus 7 bootloader that makes this a wise step to do first. Type each of these lines followed by Enter between them, waiting for one to finish before moving on to the next:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
7. This command will flash the stock bootloader on to your device. Enter:
Code:
fastboot flash bootloader bootloader-grouper-3.34.img
And press enter. Make sure you type the command exactly as you see it.
Note: As we noted earlier, replace "fastboot" above with the exact name of the fastboot file in your folder, for your system, such as "fastboot-windows" or "fastboot-mac". Addtionally for Mac's only, the command should be entered as such
Code:
./fastboot-mac flash bootloader bootloader-grouper-3.34.img
Noting the period and forward slash before the command.
Going forward you Mac folks just remember that with the rest of the commands
Now reboot the bootloader:
Code:
fastboot reboot-bootloader
Enter.
8. This next command will both wipe your old system and flash the factory image in its place, which includes the stock system, recovery, kernel, and userdata partitions:
Code:
fastboot -w update image-nakasi-jrn84d.zip
Enter, and wait, make sure the command finishes. This might take a few minutes.
Reboot the bootloader again:
Code:
fastboot reboot-bootloader
Enter.
9. We are done with the hard part... pretty easy right? Now we're just going to lock that bootloader.
Code:
fastboot oem lock
Enter.
Yes, this step is optional but I strongly recommend it if you had issues earlier which led to this procedure. Now you can unlock again if you like, which will give your tablet that final full wipe to clear out any bad data remaining:
Code:
fastboot oem unlock
Enter.
10. Finally, reboot and setup your tablet again from scratch!
Code:
fastboot reboot
Click to expand...
Click to collapse
Thanks for the quick reply! I'll do this in the morning and report back. Does anyone have a link to the factory .imgs?
Sent from my Nexus 7 using xda app-developers app
https://dl.google.com/dl/android/aosp/nakasi-jro03d-factory-e102ba72.tgz
A simpler and easier solution is to use the nexus root toolkit from http://forum.xda-developers.com/showthread.php?t=1766475
Get the latest official image from google from https://developers.google.com/android/nexus/images#nakasi and use the factory restore.
Just a few things:
1. Install the toolkit to default location
2. Restart after installing
3. Click where it says "full driver installation guide" and follow the simple instructions/script to install the appropriate drivers. (necessary before you can use it; there are two possible issues with v1.5.2 mentioned but I didn't encounter any driver issues on win7 x64 nor did I encountered the issue with adb mentioned)
4. Run the flash stock + unroot script.
5. Run the relock script.
taltamir said:
A simpler and easier solution is to use the nexus root toolkit from http://forum.xda-developers.com/showthread.php?t=1766475
Get the latest official image from google from https://developers.google.com/android/nexus/images#nakasi and use the factory restore.
Just a few things:
1. Install the toolkit to default location
2. Restart after installing
3. Click where it says "full driver installation guide" and follow the simple instructions/script to install the appropriate drivers. (necessary before you can use it; I didn't have any driver issues on win7 x64 not did I encountered the issue with adb mentioned there as a possible workaround)
4. Run the flash stock + unroot script.
5. Run the relock script.
Click to expand...
Click to collapse
I agree the toolkit is the way to go. I stayed away from it when I rooted because the whole one click method never appealed to me on any of my android devices. That was until I soft bricked my n7 by trying to change the LCD density, then I went to the toolkit it is the real deal.
Sent from my EVO using xda premium
taltamir said:
A simpler and easier solution is to use the nexus root toolkit from http://forum.xda-developers.com/showthread.php?t=1766475
Get the latest official image from google from https://developers.google.com/android/nexus/images#nakasi and use the factory restore.
Just a few things:
1. Install the toolkit to default location
2. Restart after installing
3. Click where it says "full driver installation guide" and follow the simple instructions/script to install the appropriate drivers. (necessary before you can use it; there are two possible issues with v1.5.2 mentioned but I didn't encounter any driver issues on win7 x64 nor did I encountered the issue with adb mentioned)
4. Run the flash stock + unroot script.
5. Run the relock script.
Click to expand...
Click to collapse
I used the root tool kit to root. I have a windows 7 x64 also and I had no problems with it.
Sent from my Nexus 7 using xda app-developers app

[GUIDE]-Updated 17March - Unlock/Root - Return to Stock/Unbrick - Nexus7 3G - 4.2.2

[GUIDE] UNLOCK - ROOT - RETURN TO STOCK and/ or UNBRICK your Nexus 7 3G “Nakasig- Tilapia” v4.2.2
- Disclaimer: I don't take any responsibility for anything you do to your tablet, which is to transform it into brick, break, or transform it into coffee machine -
Requirements:
1. You must have the sdk (ADT Bundle for Win) installed on your Pc and you are able to access, and use adb and fastboot.
NOTE: Notice the install location. This defaults to C:\Users\<user name>\AppData\Local\Android\android-sdk the platform tools (adb, fastboot) and usb drivers will be downloaded to this location. This will be referred to from here on as your sdk directory
But in case you haven't install all SDK, you can use only fastboot by the easy way.(Go here if you want to use the easy way to fastboot)
2. You must have ticked USB Debugging mode in your Nexus 7 3G
3 You must download and install - USB DRIVERS r_06 for Windows 7 & 8
4. Download one of both root-tool
CF- Auto-Root by Chainfire - Download link for Version Tilapia - Nakasig
or the Superboot r4 by Paul O’Brien - Actually I'm not sure if Superboot is functionnal for version 4.2.2 - I tested with my Grouper v4.2.2 and I stayed in Google screen with bootloop.
5. Download your recovery special for your Tilapia - Nakasig
CWM (Touch version or not)
TWRP - latest versions
ClockworkMod - Google Nexus 7 (GSM) - Superuser (fixed) for Android 4.2.
and rename your select with the name of the recovery image you chose to download.
6. The factory image for the Nexus 7 3G => 4.2.2 (JDQ39) - nakasig-jdq39-factory-0798439d.tgz - md5: ee8db1ed6ff1c007fe12136d4bc65cd8- size: 279.9MB - The Version Zip if you prefer
Click to expand...
Click to collapse
AND DON'T FORGET THAN IT'S BETTER FOR YOUR SPECIAL N7 3G+
TO USE THE SPECIAL RECOVERIES "TILAPIA - NAKASIG"
and NOT "GROUPER" WHICH ARE DIFFERENTS​
Click to expand...
Click to collapse
**********************************************************************************************************************************************************************
Pre-Steps
To make this easier,
1 - you should put the root-tool.zip selected on the folder “fastboot” (if you use the easy way - Goto post #2)
2 – You should put the recovery.img selected on the folder “fastboot”
UNLOCK YOUR NEXUS 7 3G+
Click to expand...
Click to collapse
To unlock your device, you must go to your bootloader. To do that, you have possibilities;
1. Turn your device on while pressing volume down
or
1. Connect your device and go to cmd terminal
Code:
> cd \Users\<user name>\AppData\Local\Android\android-sdk\platform-tools (it's common localization for an auto install)
> adb devices
# the following output should be returned
List of devices attached
<device serial number> device
2. Boot to the bootloader by use adb
Code:
adb reboot bootloader
or
2 Bis. Boot to the bootloader by use fastboot
Code:
fastboot reboot-bootloader
3. Unlock your device* by
Code:
fastboot oem unlock
*You will have to accept and erase all of your data on the tablet.
You are unlocked :good:
By Fastboot only easy way - Unlock you device
Code:
C:\Users\Username>cd c:\fastboot
Code:
c:\fastboot>fastboot oem unlock
**********************************************************************************************************************************************************************
FLASH THE RECOVERY
Click to expand...
Click to collapse
You can choose one of both recoveries - CWM or TWRP
Flash ClockworkMod Recovery as Permanent recovery
Click to expand...
Click to collapse
(You're still inside the bootloader and connected through the usb cable)
1. Flash CWM especially for your N7 3G
Code:
fastboot flash recovery recovery-name of your recovery.img
To make CWM Permanent recovery
2. Boot into recovery by pressing “volume up” and when the menu says ‘recovery mode’ press the power button
3. Go to “Mounts and Storage” menu
4. select “mount system”
5. Type in cmd terminal
Code:
adb shell
cd /system
mv recovery-from-boot.p recovery-from-boot.bak
exit
If you having trouble gaining shell, try
Code:
adb kill-server
then
Code:
adb start-server
. And restart the lines command above
* For some people, it has been reported that you don't have to replace recovery-from-boot.bak. The flash is enough to make the recovery stick.
**********************************************************************************************************************************************************************
Flash TWRP as Permanent recovery
Click to expand...
Click to collapse
(You're still inside the bootloader and connected through the usb cable)
1. Flash TWRP especially for your N7 3G
Code:
fastboot flash recovery recovery-twrp-tilapia-2.4.4.0.img
To make TWRP Permanent recovery
2. Boot into recovery by pressing “volume up” and when the menu says ‘recovery mode’ press the power button
3. Go to “Mounts and Storage” menu
4. select “mount system”
5. Type in cmd terminal
Code:
adb shell
cd /system
mv recovery-from-boot.p recovery-from-boot.bak
exit
**********************************************************************************************************************************************************************
FOR THE ROOT
Click to expand...
Click to collapse
- [2013.02.20][N7 WiFi | N7 3G] CF-Auto-Root
Click to expand...
Click to collapse
What's installed
- SuperSU binary and APK
- Nothing else, that's it.
Installation and usage
- Download the ZIP file (see post below for link)
- Extract the ZIP file (you will see - 2 folders=> images & tools and 3 files: root-windows // root-mac // root-linux)
- Boot your device in bootloader/fastboot mode. Usually this can be done by turning your device off, then holding VolUp+VolDown+Power to turn it on.
- Connect your device to your computer using USB
- Windows:
Code:
Run root-windows.bat
- Linux
Code:
chmod +x root-linux.sh
Code:
Run root-linux.sh
- Mac OS X
Code:
chmod +x root-mac.sh
Code:
Run root-mac.sh
- [ROOT] Superboot - Nexus 7 WiFi / 3G root solution
Click to expand...
Click to collapse
How to use Superboot - Windows, Linux and OSX
- Download the Superboot zip file above and extract to a directory
- Put your device in bootloader mode - Turn off the phone then turn on with the 'volume up' and 'volume down' buttons both pressed to enter the bootloader (as pictured below)
- WINDOWS - double click 'superboot-windows.bat'
- MAC - Open a terminal window to the directory containing the files,
and type
Code:
chmod +x superboot-mac.sh
followed by
Code:
./superboot-mac.sh
- LINUX - Open a terminal window to the directory containing the files,
and type
Code:
chmod +x superboot-linux.sh
followed by
Code:
./superboot-linux.sh
**********************************************************************************************************************************************************************
RETURN TO STOCK and/or UNBRICK your N7 3G+
Click to expand...
Click to collapse
Before you begin, please make sure you have ADB and Fastboot drivers installed and working.
1. Download the factory image for the Nexus 7 3G=> 4.2.2 (JDQ39) - nakasig-jdq39-factory-0798439d.tgz - md5: ee8db1ed6ff1c007fe12136d4bc65cd8- size: 279.9MB - The Version Zip if you prefer
2. Extract the factory image into the same directory as your ADB and Fastboot executables (e.g. "\android-sdk\platform-tools")
3. Plug in your device. If you are booted into Android, open a command prompt to your ADB and Fastboot directory, then type:
Code:
adb reboot bootloader
If your device is powered off, press and hold both volume keys and the power button simultaneously. After holding all three buttons for a couple of seconds, your bootloader should launch. This should reboot you into the bootloader.
4. Type:
Code:
fastboot flash bootloader bootloader-tilapia-4.18.img
5. Type:
Code:
fastboot reboot-bootloader
6. Now type:
Code:
fastboot -w update image-nakasig-jdq39.zip
7. Optional: If you would like to relock your bootloader for warranty or security purposes, make sure you are in your bootloader screen again and type:
Code:
fastboot oem lock
8. If your tablet hasn't already rebooted automatically, you can type
Code:
fastboot reboot
Well done. You should now be back on stock Android 4.2.2
**************************************************************************************************************************************************************************************
These root tools are actually the easy way for rooting your device, so you can use them without problems.
IF YOU NEED MORE ABOUT THE NEXUS 7 3G+ "NAKASIG - TILAPIA" YOU MUST GO HERE
=> [Index]- 29 Dec 2012 - All for NEXUS 7 - "Nakasig/Tilapia" - (GSM/HSPA+)
and
=> NEXUS 7 3G-"nakasig"-For all Your Jelly Bean Discussions, Problems and Solutions
Click to expand...
Click to collapse
For my part I’ve used
the easy way by my fastboot guide for unlock my device,
Adb lines command for flash TWRP as permanent recovery,
Thanks for @mateorod, @Chainfire, @paulobrien and all members who helps for the development about the Nexus 7 3G+
The EASY WAY TO USE FASTBOOT LINES COMMAND
HELP FOR FLASH MORE FASTER WHEN YOU USE FASTBOOT LINE COMMAND​
If you have got a problem with your adb or fastboot or recovery....it's very simply and faster
use this:
Download this file "fastboot.zip"
Install this file somewhere in one folder which is named "fastboot" on your PC
=> disk C: root
Unzipped this file on the folder "fastboot" and you will find 3 files:
- adb.exe
- AdbWinApi.dll
- fastboot.exe
and when you need to push something by the bootloader, you can use it.
Don't forget to push on this folder the file that you need. For exemple: boot.img or a recovery.img, etc...
The line command is :
Code:
c:\fastboot>
Enter
Code:
c:\fastboot>fastboot flash recovery recovery.img
Enter
If you want to flash the "recovery.img" file
******************************************************************
******************************************************************
If you want to know all lines of command
Code:
c:\fastboot>fastboot
Code:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default: 2048
Reserved in case
Hello, this is my first post on xda.
When i tried use "adb fastboot bootloader" cmd say to me : no device. Where is problem?
piski93 said:
Hello, this is my first post on xda.
When i tried use "adb fastboot bootloader" cmd say to me : no device. Where is problem?
Click to expand...
Click to collapse
Try the easy way on first
Use the post 2.
You can use it for all the install, except for for the permanent recovery where you will have to use ADB line command.
The best you can do, it's to use fastboot easy way and when you have finished, you learn and install correctly your sdk and check all your parameters. And when you will be ready you will be able to use adb lines command easily to install your recovery in a permanent way.
It's too long for a course about sdk, the best you can do it's to to search and read. Go to my index, and read the General guides
Gonna try this later today. Though something is a bit fishy. When I use adb from the fastboot.zip it can't find my device but from the platform-tools dir it seems to work fine. Are they different versions? How big risk is it to brick the device while unlocking/rooting and installing recovery? Pls tell me its unbrickable. cheers
Skickat från min GT-I9300 via Tapatalk 2
znejk said:
Gonna try this later today. Though something is a bit fishy. When I use adb from the fastboot.zip it can't find my device but from the platform-tools dir it seems to work fine. Are they different versions? How big risk is it to brick the device while unlocking/rooting and installing recovery? Pls tell me its unbrickable. cheers
Click to expand...
Click to collapse
I can't says it's unbrickable !!!
The differences between these versions is:
If you use sdk/platform tools it's the more complete install and the easy way for fastboot, that just if you need to use fastboot line command, but it's not more complete for using with adb lines command.
If you go to the post 2, you will see all the lines command for fastboot.
If your sdk install is correct, you can use it without problems.
The easy way by fastboot is just a shotcut
philos64 said:
I can't says it's unbrickable !!!
The differences between these versions is:
If you use sdk/platform tools it's the more complete install and the easy way for fastboot, that just if you need to use fastboot line command, but it's not more complete for using with adb lines command.
If you go to the post 2, you will see all the lines command for fastboot.
If your sdk install is correct, you can use it without problems.
The easy way by fastboot is just a shotcut
Click to expand...
Click to collapse
I tried and everything seemed to work fine ... i Unlocked/flashed twrp then "mv recovery-from-boot.p recovery-from-boot.bak" didnt work cause it couldnt find the file... :/ i continued and flashed superboot and it seemed to work fine. Downloaded latest cm and gapps rebooted inte recovery and flashed them. Now I only have bootloop with cm10.1...
I know it aint bricked cause I think I can get into bootloader.
Edit: After a factory reset it worked! :>
znejk said:
How big risk is it to brick the device while unlocking/rooting and installing recovery? Pls tell me its unbrickable. cheers
Click to expand...
Click to collapse
The Nexus7 is very difficult to brick. It still is possible, but as far as I know there is only one way to do it - remove or destroy the bootloader.
Under normal circumstances, the only time you do anything with the bootloader is unlocking/locking it, which simply does a minor modification. That's perfectly fine. And the normal custom-recovery/root process doesn't touch it, so that's fine too. Doing system updates (even legit OTA ones) might upgrade the bootloader, as might flashing custom roms. But as long as you don't interrupt the process during that critical step, it should be OK.
So outside of erasing the bootloader or flashing a completely incompatible bootloader and rebooting, your N7 should be safe.
adb command line Linux support
Hi All,
Am new to this forum and also to my newly bought N73G. So I am unsure about the complete process though explained step by step. One thing that i wanted to confirm was Does ADT Bundle for linux work the same as that of windows? Cause I run the same on my PC; these command line instructions would they work the same way on Linux terminal?
It's not the same as Windows. You can download the ADT Bundle for Linux.
Sent from my N7 3G between sky and earth
Is there any solution for unlock and root Nexus 7 3G only with Apple Mac assistance? Thank you in advance!!!
foxstam said:
Is there any solution for unlock and root Nexus 7 3G only with Apple Mac assistance? Thank you in advance!!!
Click to expand...
Click to collapse
Can you explain what do you think by Apple Mac Assistance ?
If it's for SDK Tools, you will find here the Apple version => DOWNLOAD FOR OTHER PLATFORMS
I'm not sure which recovery images should be downloaded.
Is this one correct? - recovery-twrp-tilapia-2.3.2.1.img
what does this mean? "rename your select with the name of the recovery image you chose to download."
quote:
Requirements:
...
4. Download:
CWM (Touch version or not) or TWRP and rename your select with the name of the recovery image you chose to download.
thanks
elelab said:
I'm not sure which recovery images should be downloaded.
Is this one correct? - recovery-twrp-tilapia-2.3.2.1.img
what does this mean? "rename your select with the name of the recovery image you chose to download."
Requirements:
4. Download:
CWM (Touch version or not) or TWRP and rename your select with the name of the recovery image you chose to download.
Click to expand...
Click to collapse
Yes, you can use the recovery-twrp-tilapia-2.3.2.1.img without problem
and when I writes "rename your select with the name of the recovery image you chose to download", I mean that you can rename the IMG file by "recovery" simply. It's more faster.
minimum steps to root Nexus7(3G) - for beginners
confused by too much info. on how to root Nexus 7
can this be as simple as:
1 unlock
2 root
question:
1. unlock step - erase all of your data on the tablet
If I don't care my data (I just bought it), after unlocking, can Nexus start as normal?
2. Why do we need flash the recovery?
"Pre-Steps
To make this easier,
1 - ...
2 – You should put the recovery.img selected on the folder “fastboot” (if you use the easy way - Goto post #2)
" fastboot flash recovery recovery-twrp-tilapia-2.3.2.1.img"
does "recovery-twrp-tilapia-2.3.2.1.img" mean the "recovery.img"?
thanks
elelab said:
confused by too much info. on how to root Nexus 7
can this be as simple as:
1 unlock
2 root
question:
1. unlock step - erase all of your data on the tablet
If I don't care my data (I just bought it), after unlocking, can Nexus start as normal?
2. Why do we need flash the recovery?
Click to expand...
Click to collapse
Answers:
1 - Yes, the advert is clear, all of your data will be erased !
2 - If you want to flash a rom custom, you need a recovery
elelab said:
"Pre-Steps
To make this easier,
1 - ...
2 – You should put the recovery.img selected on the folder “fastboot” (if you use the easy way - Goto post #2)
" fastboot flash recovery recovery-twrp-tilapia-2.3.2.1.img"
does "recovery-twrp-tilapia-2.3.2.1.img" mean the "recovery.img"?
Click to expand...
Click to collapse
Yes, it's correct. it's more faster to write: "recovery.img" than "recovery-twrp-tilapia-2.3.2.1.img".
It's the same file, just rename.
This has no effect on the recovery flash
Can I root my device (4.2.2) using Superboot yet ?
Re: [GUIDE] - Updated 08 Feb - Unlock and Root a Nexus7 3G “Nakasig- Tilapia”
I received 4.2.2 update today. I haven't installed it for fear of losing root. Should i repeat the procedure to root again after updating my n7. Will i again loose my data? Or the bootloader will remain unlocked? Please help
Sent from my Nexus 7 using xda app-developers app
sukhjit_bhullar said:
I received 4.2.2 update today. I haven't installed it for fear of losing root. Should i repeat the procedure to root again after updating my n7. Will i again loose my data? Or the bootloader will remain unlocked? Please help
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I can flash UPDATE-SuperSU-v1.04.zip in CWM/TWRP recovery to get root after update from 4.2.1
You will not loose any data.
Your bootloader will upgrade to 4.18 and still unlocked.

[TUT/GUIDE] [/COLOR][U]Step by Step Guide[/U] in Rooting any H818P and H818N.

[TUT/GUIDE] Step by Step Guide in Rooting any H818P and H818N.
From Own STOCK .KDZfile >> Own stock system.img >> Own ROOTED system.img>> Flashing/rooting your LG G4 H818P/N
This is compatible with H818P and H818N versions. Do this with confidence. Read and understand carefully, type codes as it is(sensitive case). Do it slowly. No need to rush!
Method 1: Involves the downloaded .kdz file to extract system.img (Desktop only)
Method 2: Involves Desktop and LG G4 to extract the system.img
Requirements.
1.) Windows Drivers
Download the content here if your want to DOWNLOAD the Latest KDZ file and use Method 1 (Safer method in my opinion).
2.) a.) VC_redistinstaller this is needed for windows lg firmware extract to work
__b.) Windows LG Firmware Extract.zipTo get the system.img from kdz file using method 1
__c.) H818P V10F <COUNTRY> )the .kdz file. (i think the country name in the version automatically adjusts base from where your location is. Mine became ESA (same as previous downloaded from philippines kdz link) although I download it from the other country kdz link.
__d.) For H818N and H818P (I don't know the site where the latest firmware can be found, but pluging your IMIE here(in the url) will give you link for your latest kdz file) http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=YourIMEIGoesHere
This option "d.)" In my case I found it link starting in. "pkg03" but it does not continue to download, so I change that to "pkg02" and it worked.
3.) LG_Root.zip
4.) Ubuntu and universtal USB installer (to install ubuntu into a 8GB USB Drive -> These will be used to in step inject root.
5.)Inject Root.zip the file that contains the root.
Method 1 (If you download the kdz file)
Step 1. Getting the system.img (using Windows Desktop)
1. ) After Downloading all requirements, Install the drivers and the VC_redistinstaller.
2.) Create one folder and name it "adb" folder in "C:". This will be our working folder. Copy all the files you have downloaded there and UnZip LG_Root.zip, Inject_Root_G4.zip and windows LG firmware Extract.zip into that folder.
3.) Plug in LG G4, then Double click "ports.bat" look for the "COM<number>" of the same line of LGANDNETDIAG1 . it is the second COM, mine is COM4 ( just also to check if LG G4 is recognized and is installed properly)
4.)a.) Open the WindowsLGFirmwareExtract.exe.
4.b.) 1. Click Open > select the kdz file. b.) check all
4.b.) 2. Click Extract KDZ ---processing--- b.) check all
4.b.) 3. Click Extract DZ ---processing--- b.) check all
4.b.) 4. Click Merge System.bin --- processing---
5.) a.) go back to the "adb" Folder that you created in step 2. then open "merge_ouput" folder., you will now see there the Stock System.img
5.) b.) Copy System.img from the merge_ourput to the adb folder (C:\adb)
Method 2 (if you already have stock H818P V10F and don't want to download the kdz file)
Step 1. Getting the system.img (using Windows Desktop and LG G4)
1.) After Downloading all requirements, Install the drivers.
2.) Create one folder name it "adb" folder in "C:". This will be our working folder. Copy all the files you have downloaded there and Unzip LG_Root.zip and Inject_Root_G4.zip into that folder.
3.) Plug in LG G4, then Double click "ports.bat" look for the "COM<number>" of the same line of LGANDNETDIAG1 . it is the second COM, mine is COM4 ( just to check if LG G4 is recognized and is installed properly)
3.) Put your phone to download mode: turn it off. then hold the volume up(+) button then plug the LG G4 to the Desktop.
4.) Double click "ports.bat" find and remember the "COM<number>" of the same line of LGANDNETDIAG1 . it is the second COM, mine is COM4.
5.) Hold shift and right click in any empty space in the "adb" folder. Choose open command windows here.
6.) Type: Send_Command.exe \\.\COM[*insert your number here] mine is Send_Command.exe \\.\COM4
7.) Then nothing will happen to the LG G4 phone. It is normal.
8.) Copy and paste to command window: dd if=/dev/block/mmcblk0 bs=8192 skip=55296 count=529920 of=/data/media/0/system.img
9.) Notice the # is gone. Wait for it to Come back. this takes a few minutes.
10.) Once the # is back. Type: LEAVE
11.) The device will automatically reboot. Now go to your file manager and see if system.img is in phone's internal storage. Copy the system.img from phone'sinternal memory to the folder we created. (C:\adb)
Step 2. Setting up Ubuntu (using Windows Desktop)
1.) Plug in the 8GB USB Drive
2.) Open the universal USB installer follow the installation , select Ubuntu, then browse and select the Ubuntu .iso file you download in the requirements, select your USB drive , and just continue normal install without selecting any other options until Finish. (now your USB will be named "Install Ubuntu")
3.) Open the USB flash drive folder. open wubi.exe, select "demo and full installation" select "help me boot from CD" click finish and then restart.
3.) After the restart, there will be option to boot on Ubuntu. and select it to boot.
Step 3. Injecting root to system.img (using Ubuntu from step 2)
1.) On Ubuntu. Click the ubuntu logo on the upper right. then type "Terminal" then select the Terminal application
2.) On the terminal type: sudo -i and then you will see [email protected]
3.) Then type: cd C:\adb or cd then drag the "adb" folder you created where the inject_root_g4.zip and its unzip files is located.
3.) Now, the name in the terminal will be longer. type: chmod +x autoroot.sh
4.) Then, type: sudo ./autoroot.sh
5.) If the "command is invalid" appears or something like that...
6.) Type: sudo sh autoroot.sh -this worked for me.
7.) If you are successfull, you will see that the system.img is changed to rootedsystem.img DO NOT RENAME THIS.
8.) Close the terminal. Then turn off the Desktop. Then remove the USB drive.
9.) Turn on and boot on Windows
Step 4. Flashing the rooted system.img (using Windows Desktop and LG G4)
1.) Copy the created "rootedsystem.img" to your phone's internal storage.
2.) Put your phone to download mode: turn it off. then hold the volume up(+) button then plug the LG G4 to the Desktop.
3.) Double click "ports.bat" find and remember the "COM<number>" of the same line of LGANDNETDIAG1 . it is the second COM, mine is COM4.
4.) Hold shift and right click in any empty space in the "adb" folder. Choose open command windows here.
5.) Type: Send_Command.exe \\.\COM[*insert your number here] mine is Send_Command.exe \\.\COM4
6.) Then nothing will happens to the LG G4 phone.
7.) Copy and paste to command window: dd if=/data/media/0/rootedsystem.img bs=8192 seek=55296 count=529920 of=/dev/block/mmcblk0 this is DIFFERENT CODE from method 2 step 1.
8.) Notice the # is gone. Wait for it to Come back. this takes a minute or a few minutes. mine was 2 minutes.
9.) Once the # is back. Type LEAVE
10.) The device will automatically reboot. and just wait for it to boot. It will take a bit longer than usual. It will do Optimizing apps screen. and now you are rooted!
Hit thanks if you appreciate. Hope I helped!
All of this was compiled and written (method 1 and Step 2) by me, @makwell24, for the H818P and H818N Users. The method 2 step1, step 3 and step 4 was guided and base from this post by @hackarchive

Categories

Resources