Database Users

Install non-market apps without File Manager: Possible?

Simply put is there a way to get an app onto my phone without the market or file manager?
I ask because I want to use Haykuro's G build but I cant download any apps. I do however have all the ones I use regularly backed up onto my SD card but I cant access them without a File Manager (which I cant download to use). Is there a way?
|Spike|

There's always the option of using AppsInstaller/APKInstaller and putting APK's onto your SD Card. Though, to install AppsInstaller, you have to install it through ADB.

Unicornasaurus said:
There's always the option of using AppsInstaller/APKInstaller and putting APK's onto your SD Card. Though, to install AppsInstaller, you have to install it through ADB.
Click to expand...
Click to collapse
How do I install thru ADB?
|Spike|

Get the android usb drivers, adb.exe and adbwinapi.dll from an Android SDK. Plug the Dream in via USB and point to the location of the drivers when it is installed. Then open your command line, navigate to whatever folder adb.exe is in and type adb install <full path to the apk>. If you run Linux hopefully you can figure it out on your own based on the steps above.
Alternately, upload all the apks you want to the internet somewhere. Check the box to enable installation from Non-market sources in the system settings, then type the full URL of the apk into the browser. The package installer will take over from there.

Here's how you do it. Assuming your G1 is rooted
1. Download the attched files, and copy them into your \system32 folder (Start > Run > %systemroot%\system32)
2. Sure your G1 is enabled for USB Debugging (Settings > Applications > Development > USB debugging) and that your G1 has the appropriate drivers installed. If not, download the USB drivers from HERE
3. Plug your G1 into your computer (Make sure you have USB 2.0 - Click here to find out how to check). When your G1 says "USB Connected" DO NOT click "Mount"..don't do anything
4a. Vista users - Follow these steps. For XP Users, skip to step 5
4b. On your computer, browse to the directory where the APK for your file is located
4c. Once located, hold SHIFT and right click on a blank area of the folder
4d. Click on "Open Command Window Here"
4e. Type "adb install nameofyourapkhere.apk" - without the quotes.
4f. It might say something like "daemon service not started" or something, but it will start it and continue. It'll then say something like 626k/1293k bla bla bla
4g. If it was successful, it will just say "Success". You can close the command window and SHAZAM! Your program will now be installed on your G1, and you can access it like any other program on your phone
5. XP Users - Follow these directions:
a) You can either go Start > Run > type CMD and press enter
OR
Windows Key + R > type CMD and press enter
Navigate to your APK file via the command prompt. For easy usage, put your APK file on your desktop. That way all you have to do is type "CD Desktop" into the command prompt
b)Type "adb install nameofyourapkhere.apk"
c)You may get a couple of messages like in the steps for Vista users
d)If all goes well, you too will get the success message
e)Enjoy your application!
Any confusions, let me know. Hope it helps, and Good Luck!

I've been using a local web server and the android browser.

untermensch:
Thats a possibility, but oddly enough, that requires a http-server
AGx-07_162:
With unicornasaurus's method above, you can install all the apk's you want... you can install apkinstaller and use that through that method, but you can just aswell install your apk's directly through it

I ran into the same problem. Here is the easiest ways to get the appinstaller on your G1. Download this file from your g1 browser or Gmail yourself this file, and download.
http://www.mediafire.com/?egy0mop2qqx

Problems with adb not working!!! Fixed

Originally Posted by Spin Dr Wolf
Gah. I can't get adb running, i keep getting the message below whenever i try any adb command.
" 'adb' is not recognised as an internal or external command, operable program or batch file. "
I have no idea where its going wrong though, i have the USD drivers installed got the SDK kit unzipped on the drive too, using the commands in the right place. Anyone got any ideas ?
I'm using Vista sadly if that makes any difference ?
HI! I understand you reading this part:
Section 3: Running ADB from Command Prompt
Running Command Prompt:
Windows XP: Select Start or Tap the Windows Key on your Keyboard, select "Run" and type "CMD" then hit "Enter".
Windows Vista/Win7: Select Start or Tap the Windows Key on your Keyboard, select the search box on the left and type "cmd" then hit "Enter".
- Also, Mikey1022 has reminded me to add the "ADB" directory path as a system variable in windows...
To do this right-click on "My Computer" and select Properties. Next select the Advanced tab(Advanced Settings in Vista) then select Environment Variables.
Click "New" under System Variables and add the following:
Variable: adb
Value: C:\android-sdk-windows-x.x_rx\tools "x = version you are using"
The Value is WRONG!!! It has changed. It should be C:\android-sdk-windows-x.x_rx\platform-tools\
Dont forget to x10christian

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?

[ROOT][GUIDE] Stock Lollipop 14.5.A.0.270 using Ubuntu! Xperia Z1 Compact

Dear all,
This took me forever to figure out, so I'd thought I'd share how I rooted my Xperia Z1 Compact (Mini) using Ubuntu 14.10. (You could do this using Windows by skipping Step 2).
First, these were the problems I encountered using other methods:
- Using kingroot worked, but it was very suspicious (there's a nice thread that listed all the mysterious behaviours of kingroot - I can't find it so please just search for it).
- I never tried PRF Creator, since it was yet another Windows app.
- Flashing any boot.img into boot would cause an eternal boot loop.
- Thus I had to use Sony's Emma to enable flashing a recovery.img into recovery; but for this, I needed VirtualBox, and for VirtualBox, I needed USB 2.0 (3.0 didn't work).
- Old versions of SuperSu would never work. The only version that worked is the BETA 2.49.
So here are the steps that worked for me. (I don't guarantee that it will work for you). Make sure you back everything up and unlock your bootloader (you can relock it again using FlashTool).
Here are the steps in brief (details below):
0. Get Ubuntu to recognise your device.
1. Make sure you have stock firmware (either officially by Sony Update, or by flashing a .ftf using FlashTool).
2. Use VirtualBox and a copy of Windows straight from Microsoft (yes, it's free and legal).
3. Use Sony's Emma on Windows to do a "TA update".
4. Back on Ubuntu use fastboot to flash a recovery (fastboot flash recovery recovery.img).
5. Boot your phone into recovery and flash the SuperSu.
The Details:
0. Get Ubuntu to recognise your device
On Ubuntu, open a terminal and type:
Code:
gksudo gedit /etc/udev/rules.d/51-android.rules
type:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", MODE="0664", GROUP="plugdev"
Save, then exit.
Then type this command:
Code:
sudo service udev restart
Next, test that it's working:
Code:
sudo apt-get install android-tools-adb
sudo apt-get install android-tools-fastboot
On your phone, enable USB debugging:
Settings -> About Phone -> Build Number (tap Build Number 7 times until developer options enabled)
Settings -> Developer options -> USB debugging
Connect your phone to your Ubuntu and type:
Code:
adb devices
This command may cause your phone to alert you that your computer is trying to modify your phone. Allow it. Then type the above command again in your ubuntu and you should get something like this:
Code:
List of devices attached
XXXXXXXXXX device
where XXXXXXXXXX is your serial number.
1. Get stock Lollipop (14.5.A.0.270) on your phone
You can either get the update straight from Sony or download it and flash it using FlashTool.
From Sony:
If your bootloader is unlocked, relock it using FlashTool (click on the BLU button)
Use the update tool on your phone: Settings -> About Phone -> Software Update.
Using FlashTool:
Download FlashTool and unzip it.
In a terminal cd into the FlashTool folder and type:
Code:
./FlashTool
(you may have to give it permissions first: chmod +x FlashTool)
Click on the "BLU" button to unlock your bootloader (this is necessary for any fastboot command, see below).
Click on the XperiFirm button (the last one on the right that says "XF"). Select a firmware of your choice. Then click on the line under the PayPal symbol that says "14.5.A.0.270..." (for some reason, there's no button, just a line of text). Then click Download. If you didn't change the default "User home", the files will be downloaded to your home directory in .flashTool/firmwares/Downloads
Once it finishes downloading, close the XperiFirm windows in order to return to FlashTool. FlashTool will then take some time converting the stock firmware into a flashable .ftf file (placing it in .flashTool/firmwares).
Once it's done, click on the button with the lightning symbol, select Flashmode and then your firmware and click Flash. It will wait for you to connect your phone in Flashmode (turn phone off, hold the volume down button and then connect the USB cable). Once it detects your phone, FlashTool will flash your firmware, again taking some time.
2. Install VirtualBox with a Windows 7 Guest
Install VirtualBox and the Extension Pack from the virtualbox website (make sure the version of the extension pack is the same as the version of virtualbox. I used 5.0.
Download the image of Windows 7 (what I used) available free from the Microsoft Dev download page (dev.modern.ie/tools/vms/linux/). Unzip it and then double click it to open it in VirtualBox. Follow the VirtualBox prompts to install it (Microsoft recommends assigning between 1 and 2 GB of RAM).
Before running the guest machine, select the Windows 7 machine in Virtualbox and click on "Storage" then "USB". Make sure that USB controller is enabled, and select USB 2.0. (It never worked with USB 3.0 for me. Also, my laptop has one USB 2.0 port and one USB 3.0 port, and I had to make sure I used the correct port.)
3. Install and run Sony's Emma
The following will only work with an unlocked bootloader. Use FlashTool to unlock it (BLU button - see step 1 under FlashTool).
Run the guest Windows and install Emma (developer.sonymobile.com/services/flash-tool/). In the downloaded zip file for Emma, copy the customization.ini file to C:\Program Files\Sony Mobile\Emma\
Run Emma.
Turn off your phone and put it in flash mode (hold volume down and then connect usb). At the top of the VirtualBox window that shows your Windows running, click on the Devices menu, then USB, then "Sony D5503...". Your guest Windows should now detect your phone, and so will Emma.
In Emma, in the list of "Services" on the right, select the one that ends with "TA Update" and flash. When it's done, close Emma and VirtualBox.
4. Flash a recovery
On Ubuntu, download a recovery image. I used this one: Z1_DooMLoRD_AdvStkKernel_FW-757_v04.zip from this page:
http://doomlord.xperia-files.com/ (scroll down a bit to find it). Unzip this file and rename it to recovery.img
Then in a terminal type:
Code:
fastboot flash recovery recovery.img
This command flashes to "true" recovery as opposed to the command "fastboot flash boot boot.img" which installs into boot. I'm no expert, and I'm not sure what the difference is between boot and recovery, but you need Emma to enable recovery. (I tried doing things the boot way, ie, without Emma, but it resulted in a bootloop.)
Note also that this recovery is based in CWM. I read somewhere that TWRP won't work using this method, but I never tried it.
5. Use recovery to flash SuperSu
Download BETA-SuperSu-v2.49.zip from here (this is the only version of SuperSu that worked for me; earlier versions failed).
Copy this file into your SD card (using a card reader, or boot up your phone normally and connect it to your computer).
Boot into recovery: Turn off your phone. Press the power button and volume down button together. When the phone vibrates the first time, release the power button (but keep holding the volume down button). When the phone vibrates again, release the volume down button.
On the recovery menu, select "Install zip" and then choose your the BETA-SuperSu-v2.49.zip from your sdcard. When it's done flashing, go back and select "reboot system now". It might complain that "Root access possibly lost. Fix". Ignore it and select "No".
Your phone should now start up and SuperSu should appear in your app drawer. If you open it, it should start up with no complaints. (Or install the app Root Checker just to be sure).

AFAIK Virtualbox doesn't add your user automatically to vboxusers group which is required to share USB devices between the host and guest machine.
You can do that by running
Code:
sudo usermod -aG vboxusers <your username>

Makenai said:
Code:
sudo usermod -aG vboxusers <your username>
Click to expand...
Click to collapse
thanks for the tip, I would like to note that there's a missing blank space and ' - ' symbol in the sentence, it should be like this:
Code:
sudo usermod -a -G vboxusers <your username>
Regards

Hi,
i did everything until step 3 where i loaded 14.5.A.0.270. I didn't do "TA update"
My question is: because after that i used a lot the phone and configured many things, is it possible con continue with step 4 and later, without loosing any data?
cheers

While every documentation is useful - post's subject does not exactly corresponds to action.
Using Windows under Ubuntu is still using Windows.
As far as I am aware there is flashtool working directly on Linux platform.
This allows to get rid of virtual devices, host-to-guest device delegations, problems with direct hardware access from guest, something what always may be potential source of problems.

Hi there, now 5 years later i got hold on this device and i want to root this very same model.
Unfortunately important links are dead. I can't find a trustworthy recovery image for this device since doomlord.xperia-files is gone. (4. Flash a recovery)
Can anybody help?

[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