Database Users

[Tutorial][ROOT][4.3]Root your own stock 4.3 firmware

Since every "best way to root stock 4.3" guide for LB in this forum involves flashing a deodexed ROM from a region that might not be yours and taken from someone's phone that might be different from yours, I've decided to make this guide which will (I hope) help you make YOUR OWN pre-rooted flashable zip using YOUR OWN phone and an FTF for YOUR OWN region.
Just a mandatory precaution: I'm not responsible for whatever happens to you, your phone, your family, your house, your dog, your car, etc resulting from the use of this guide.
Here goes.
What's needed:
==========================
1. Your SONY Xperia SP running a rooted stock ROM. You might need to downgrade to 4.1.2 and root that.
2. A recovery. See: http://forum.xda-developers.com/showthread.php?t=2649923 (Note: I only use CWM. I have not tried Philz or TWRP.)
3. SONY PC Companion
4. Flashtool
5. su + busybox binaries
6. META-INF
7. SuperSU
8. Stock .266 kernel. You could make this yourself, but for the sake of simplicity, just use this one instead.
8b. Stock .201 kernel.
9. (Optional) be2_album for Bravia Engine fix.
The good part:
=====================
1. Follow this guide to download and make your own FTF file. This file will contain the stock firmware for your own phone and region.
2. Then follow this guide to extract the system folder, but stop at step 9.
3. Navigate to the "bin" folder inside the system folder you just extracted and delete anything that's <10 bytes in size. Those are symlinks which will be recreated automatically in the flashing process. (Ignore this step if there are no files smaller than 10 bytes. Anything larger than 100 bytes should NOT be deleted.)
4. Extract the META-INF.zip file you downloaded above and copy the META-INF Folder in the folder alongside the system folder.
5. You should now have 2 folders, META-INF and system.
6. Extract the su + busybox binaries and put them in system/xbin.
6b. (Optional) Extract be2_album and put it in /system/etc.
7. Zip the two folders (META-INF and system) using store only (no compression).
8. Congrats, you just made your own pre-rooted pure stock ROM. Copy this zip and SuperSU into your sd card and we're good to go.
How to flash:
================
This might sound familiar, because this part is the same as the other guides.
1. Boot into CWM.
2. Clear dalvik cache and wipe cache. (Optional: wipe data)
3. Flash the zip you just made.
4. Flash SuperSU.
5. Power off.
6. Flash kernel using flashtool.
7. Boot up your phone and enjoy (or not) using a ROOTED STOCK firmware that was meant for YOUR phone and not for someone else's phone in another country on the other side of the world.
8. (Optional) If you get a reboot when remounting (e.g. when using Foldermount), apply this fix.
As a side note: Memory management is kinda crappy on 4.3. Dropping dalvik.vm.heapgrowthlimit to 64m and dalvik.vm.heapsize to 96m helps somewhat, but YMMV. Please experiment on your own to find a limit that works best for you.
This guide will (in theory) work for ANY future official release as long as the partitions stay the same. I hope this will at least reduce the nagging the devs (especially DoomLord) gets for a root exploit for stock 4.3.

Nice one

Grrrreeeatt.. This what I looking for all this time..
Whereas just last night I'd stay up finding how the way to put my region stock fw flashed to my device with root via dsixda andro kitchen, but the update script f***ing my brain all day long..
5 times xperimental flashing, but nothing happen. All kind of error Stats 7, 6, 0, etc just appear..
deodexed rom is suck considering it's not came from my own region..
I will try soon..
=============================
Edit :
- in step 3, are u sure to delete <10 "bytes" file? Bcause nothing here below 10 bytes. Just 10 kb are there..
Sent from my C5302 using XDA Premium 4 mobile app

Thanks!
I have ROOT

nasroed said:
- in step 3, are u sure to delete <10 "bytes" file? Bcause nothing here below 10 bytes. Just 10 kb are there..
Click to expand...
Click to collapse
Yes, I'm sure. Ignore this step if there are no files smaller than 10 bytes. Anything larger than 100 bytes should NOT be deleted.

Okay I followed the guide step by step. I have removed anything that was 7 bytes.. The others are min 156 bytes and 178 bytes the others are going to KB. So now I have to put the SU+Busybox into Xbin, make a .zip and flash it, flash Su and kernel?
See attachment for files smaler then 10 bytes

After few flashtattemps i get installtion aborted on touch CWM and TWRP cant even find the files.
Also I got some errors due to missing paths via the updater.script. Worth taking a look there.

mrjraider said:
Okay I followed the guide step by step. I have removed anything that was 7 bytes.. The others are min 156 bytes and 178 bytes the others are going to KB. So now I have to put the SU+Busybox into Xbin, make a .zip and flash it, flash Su and kernel?
See attachment for files smaler then 10 bytes
Click to expand...
Click to collapse
Yes. The zip should contain 2 folders. META-INF and system. Can you give me a listing of what you zipped? This guide is exactly how I rooted my 4.3 and it works fine. Also, try using store only when zipping. Sometimes the recovery doesn't work with zips that are to aggressively compressed.
Sent from my C5302 using xda app-developers app

Followed the guide step by step and the problem I have is it wont flash. It says instalation aborted and there were some errors about paths?
I zipped the meta-inf and system folder.
Added to archive and seleted .zip and store.. After copying to SD and flashing I got instalation aborted.
I will try this later tho. I just need my phone in a few hours

Please send me the directory listing of what you zipped and I'll look into it.
Sent from my C5302 using xda app-developers app

quetzalcoatl2435 said:
Please send me the directory listing of what you zipped and I'll look into it.
Sent from my C5302 using xda app-developers app
Click to expand...
Click to collapse
I can also share the entire zip if you want xD

mrjraider said:
I can also share the entire zip if you want xD
Click to expand...
Click to collapse
Do whichever is easier for you. Hahaha.
Sent from my C5302 using xda app-developers app

edit:
I know the probem xD
It was a sort of my fault
zip file>firmware> meta-inf and System
There was an extra folder that did not needed to be there
Will try it later tho.

Alright back to testing.. Will flash my own zip when downgrading and rooting is done
---------- Post added at 07:22 PM ---------- Previous post was at 06:37 PM ----------
It worked!!! Thank you!
---------- Post added at 08:15 PM ---------- Previous post was at 07:22 PM ----------
http://forum.xda-developers.com/showthread.php?t=2682651

quick one question I'm on doomlord v5 and Ultimate PureXSP (.266). But got some reebots. When I change kernel to stock via flashtool my root will stay? (quite noob question :< )

Awesome - a rather clean method of rooting - inserting a modified meta-inf and su/busybox into the system file and flash it.
LocaMobile said:
quick one question I'm on doomlord v5 and Ultimate PureXSP (.266). But got some reebots. When I change kernel to stock via flashtool my root will stay? (quite noob question :< )
Click to expand...
Click to collapse
I don't think so, as there are very few and 'minor' changes to the system file...
[not going to 4.3 as I didn't like the lag - still mulling about it]
Edit: A question
For the necessary process, one needs to downgrade in order to install CWM, say .254.
If I flash the new modified system+meta-inf, plus the original .266 (kernel only), I am still on hybrid 254+266 system, yes?
[after all there are other sin files not replaced: eg loader, fota, partition, etc]

how big is the zip file after making the compression? is 1,08 GB normal?

noel_din said:
how big is the zip file after making the compression? is 1,08 GB normal?
Click to expand...
Click to collapse
So is mine...

headache59 said:
So is mine...
Click to expand...
Click to collapse
thanks, so its normal, will try in my C5302

Locked bootloader
hello...is this guide is applicable for locked boot loader also ?

Help please , price for helpers!

HELLO XDA USERS
i've got a GALAXY S4 SPRINT
Can anyone just tell me how to USE TWRP and mount INTERNAL STORAGE to RECOVER my DELETED FILES :/? i have read somewhere that it is possible to mount INTERNAL STORAGE through TWRP
HELP PLEASE I NEED MY FILES BACK :crying::crying::crying::crying::crying::crying::crying:
A MONEY PRICE FOR WHO HELPS ME SOLVE MY PROBLEM

PhillipAmal said:
HELLO XDA USERS
i've got a GALAXY S4 SPRINT
Can anyone just tell me how to USE TWRP and mount INTERNAL STORAGE to RECOVER my DELETED FILES :/? i have read somewhere that it is possible to mount INTERNAL STORAGE through TWRP
HELP PLEASE I NEED MY FILES BACK :crying::crying::crying::crying::crying::crying::crying:
A MONEY PRICE FOR WHO HELPS ME SOLVE MY PROBLEM
Click to expand...
Click to collapse
TWRP is a recovery kinda like CWM. Flash it and use it like you would use CWM. Nothing fancy about it.

emperorHadrian said:
TWRP is a recovery kinda like CWM. Flash it and use it like you would use CWM. Nothing fancy about it.
Click to expand...
Click to collapse
He asked how to mount the internal storage and recover accidently deleted files.
I gave him a solution weeks back, but that is too tough for him to take up..
@Lennyz1988 @MAX 404 @AntaresOne help required here.
Sent from my GT-I9500 using XDA Free mobile app

Recover all your files
PhillipAmal said:
HELP PLEASE I NEED MY FILES BACK :crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Don't panic
Follow these steps and you'll good.
1. Download this: http://techerrata.com/file/twrp2/jfltespr/openrecovery-twrp-2.8.0.1-jfltespr.tar
2. Download this: http://forum.xda-developers.com/attachment.php?attachmentid=1168421
3. Extract the downloaded Odin307.zip anywhere.
4. Open the extracted folder location and open the file "Odin3 v3.07.exe".
5. Now you'll see the ODIN window. Click on the "PDA" button and then select the the "openrecovery-twrp-2.8.0.1-jfltespr.tar" file that you have downloaded in the first step.
6. Turn your phone completely off. And then hold "VOLUME DOWN" + "HOME" + "POWER" and when appear a warning screen, press "VOLUME UP", connect your phone on your computer and wait until it installs all drivers.
7. Press "Start" on ODIN and wait to complete. In the above tabs will appear "RESET" and your phone will reboot.
8. Grab imediately your phone and hold "VOLUME UP" + "HOME" + "POWER" and keep holding and wait until appear a blue 'wallpaper' with the words "TWRP" on it. Great, now don't make anything in these menus, just follow the steps!!
9. Now you must download ADB in order to pull your files to your pc. Download here: https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc
10. Create a folder in "C:/" called BackupFiles.
11. Now open the CMD window (Press on your keyboard "WINDOWS" + "R", write "cmd" and press "ENTER".)
12. Write in the CMD window: adb pull /sdcard/ "C:/BackupFiles"
13. Wait until it completes all the process and you are done All your files should be in "C:/BackupFiles" folder.
EDIT: If your have trouble in step 13, point to the complete path where ADB was installed, like this: C:/your/adb/install/location/adb.exe pull /sdcard/ "C:/BackupFiles"
Aaaaand.... If you have trouble with the drivers, download these here and install: http://www.mediafire.com/download/uw3z23dqz3y7kgn/Samsung-Usb-Driver-v1.5.45.0.exe

---------- Post added at 11:10 AM ---------- Previous post was at 11:07 AM ----------
You can try a guide like this.
http://forum.xda-developers.com/gal...de-internal-memory-data-recovery-yes-t1994705
You only need to change this part: "if=/dev/block/mmcblk0" to the block of the internal storage. I don't have time to look it up now which one it is, but maybe @DeepankarS knows which block it is.
This won't help him because he deleted all his files.
Fusseldieb said:
Don't panic
Follow these steps and you'll good.
1. Download this: http://techerrata.com/file/twrp2/jfltespr/openrecovery-twrp-2.8.0.1-jfltespr.tar
2. Download this: http://forum.xda-developers.com/attachment.php?attachmentid=1168421
3. Extract the downloaded Odin307.zip anywhere.
4. Open the extracted folder location and open the file "Odin3 v3.07.exe".
5. Now you'll see the ODIN window. Click on the "PDA" button and then select the the "openrecovery-twrp-2.8.0.1-jfltespr.tar" file that you have downloaded in the first step.
6. Turn your phone completely off. And then hold "VOLUME DOWN" + "HOME" + "POWER" and when appear a warning screen, press "VOLUME UP", connect your phone on your computer and wait until it installs all drivers.
7. Press "Start" on ODIN and wait to complete. In the above tabs will appear "RESET" and your phone will reboot.
8. Grab imediately your phone and hold "VOLUME UP" + "HOME" + "POWER" and keep holding and wait until appear a blue 'wallpaper' with the words "TWRP" on it. Great, now don't make anything in these menus, just follow the steps!!
9. Now you must download ADB in order to pull your files to your pc. Download here: https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc
10. Create a folder in "C:/" called BackupFiles.
11. Now open the CMD window (Press on your keyboard "WINDOWS" + "R", write "cmd" and press "ENTER".)
12. Write in the CMD window: adb pull /sdcard/ "C:/BackupFiles"
13. Wait until it completes all the process and you are done All your files should be in "C:/BackupFiles" folder.
EDIT: If your have trouble in step 13, point to the complete path where ADB was installed, like this: C:/your/adb/install/location/adb.exe pull /sdcard/ "C:/BackupFiles"
Aaaaand.... If you have trouble with the drivers, download these here and install: http://www.mediafire.com/download/uw3z23dqz3y7kgn/Samsung-Usb-Driver-v1.5.45.0.exe
Click to expand...
Click to collapse

@Lennyz1988 Earlier I gave him this as a possible solution
http://forum.xda-developers.com/showthread.php?p=54722303
Rest it is a task
And block is 26/29
persdata -> /dev/block/mmcblk0p26
userdata -> /dev/block/mmcblk0p29
Bdw would Undelete from playstore work on this type of a phone? (It is a risk as writing anything new would damage the images there)
Can he also try recuva?
I've heard it works. Still not sure.
Edit : It doesnt till you mount internal storage.
And this is the source for mounting internal storage.
External Link but the post is By a XDA member on How to Mount Internal Storage.
@Fusseldieb This helps in recovering the accidently deleted files too? Or just mentioned how to dump the system..........
Sent from my GT-I9500 using XDA Free mobile app

DeepankarS said:
@Fusseldieb This helps in recovering the accidently deleted files too? Or just mentioned how to dump the system..........
Click to expand...
Click to collapse
He wiped his whole system?
OK, then his files are gone...
This tutorial only shows, how to dump all files.

Fusseldieb said:
He wiped his whole system?
OK, then his files are gone...
This tutorial only shows, how to dump all files.
Click to expand...
Click to collapse
Haha he flashed a new stock rom and it reset by itself.
Well no the files haven't gone. You still can recover them by using any windows recovery tool if you manage to mount the internal storage (somehow) and use a data recovery tool like TOKIWA or Panda or Recuva.
Sent from my GT-I9500 using XDA Free mobile app

DeepankarS said:
Well no the files haven't gone.
Click to expand...
Click to collapse
I know, but it's much effort to recover these. And IF these files could be recovered, it would be totally out of order, all in one folder, probably without their original names :silly:
He could somehow mount the EXT4 system, as described here: http://www.maketecheasier.com/access-linux-ext4-partition-from-windows/
I have done this one day with my cellphone, but I don't remember how.

Fusseldieb said:
I know, but it's ....
Click to expand...
Click to collapse
Dual boot windows and linux?
Tell me how did you do this to recover files from your erased android phone.
"If you dual boot your computer with both Windows and Linux, you will discover that while you can access the*Windows NTFS partition from Linux, you won’t be able to access Linux partition from Windows. If you have urgent needs to access Linux Ext4 partition from Windows (without wanting to boot into Linux), here is one tool that can help you."
Read the link that you're sending before posting anything..
Sent from my GT-I9500 using XDA Free mobile app

DeepankarS said:
Tell me how...
Click to expand...
Click to collapse
Here it's explained: http://mohammadag.xceleo.org/mounting-your-android-devices-internal-storage/
This also meant you could not run recovery software on /sdcard anymore, at least not with MTP.
With a few tweaks, you could, however, do just that!
Click to expand...
Click to collapse

Fusseldieb said:
Here it's explained: http://mohammadag.xceleo.org/mounting-your-android-devices-internal-storage/
Click to expand...
Click to collapse
See post 7.
Click the external link..and see where you land.
Sent from my GT-I9500 using XDA Free mobile app

DeepankarS said:
Click the external link..and see where you land.
Click to expand...
Click to collapse
Oh sorry, it's the same link :silly:

Fusseldieb said:
Oh sorry, it's the same link :silly:
Click to expand...
Click to collapse
Haha nvm buddy
Sent from my GT-I9500 using XDA Free mobile app

I am confused guys here, i have experienced androids and computer, but with these arguments i am kinda lost, help here please, did someone managed to Mount THE INTERNAL STORAGE ?
no matter what Method i will do it!

PhillipAmal said:
I am confused guys here, i have experienced androids and computer, but with these arguments i am kinda lost, help here please, did someone managed to Mount THE INTERNAL STORAGE ?
no matter what Method i will do it!
Click to expand...
Click to collapse
Post 7 and Post 11 have your replies..
The steps are not tough if you follow properly.
And do post here if you get stuck somewhere..
We are all here for you..
Sent from my GT-I9500 using XDA Free mobile app

DeepankarS said:
Post 7 and Post 11 have your replies..
The steps are not tough if you follow properly.
And do post here if you get stuck somewhere..
We are all here for you..
Sent from my GT-I9500 using XDA Free mobile app
Click to expand...
Click to collapse
First of all thank all of uu
Does Guide mentioned in #5 plus with codes to change #6 will work ?
btw #7 and #11 aren't guides at all

Lennyz1988 said:
---------- Post added at 11:10 AM ---------- Previous post was at 11:07 AM ----------
You can try a guide like this.
http://forum.xda-developers.com/gal...de-internal-memory-data-recovery-yes-t1994705
You only need to change this part: "if=/dev/block/mmcblk0" to the block of the internal storage. I don't have time to look it up now which one it is, but maybe @DeepankarS knows which block it is.
This won't help him because he deleted all his files.
Click to expand...
Click to collapse
Thank u
can u please explain about Cygwin mentioned in steps ? :
Cygwin installed to [c:\cygwin] with pv and util-linux from the repo. Make sure to open Cygwin once to make sure that the /bin folder is created. Also, I made a folder at [c:\cygwin\nexus] to put the exported .RAW file ?

PhillipAmal said:
Thank u
can u please explain about Cygwin mentioned in steps ? :
Cygwin installed to [c:\cygwin] with pv and util-linux from the repo. Make sure to open Cygwin once to make sure that the /bin folder is created. Also, I made a folder at [c:\cygwin\nexus] to put the exported .RAW file ?
Click to expand...
Click to collapse
You need to download pv and util-linux seperately from here https://cygwin.com/packages/package_list.html
and put those files in the cygwin map.

Looking for how to change System Images for Droid Turbo

I believe the next step for the Droid Turbo are system images.
With MofoRoot, the next goal is to create a system image that is lollipop 5.1 and has root.
I've only flashed system images that were created up to this point but I'd be interested in learning how to take apart a system image and go as far as changing/manipulating it have wifi tether and root. Anyone have any good suggestions on where to start learning?
I plan to collect what I discover in this thread.

windraver said:
I believe the next step for the Droid Turbo are system images.
With MofoRoot, the next goal is to create a system image that is lollipop 5.1 and has root.
I've only flashed system images that were created up to this point but I'd be interested in learning how to take apart a system image and go as far as changing/manipulating it have wifi tether and root. Anyone have any good suggestions on where to start learning?
I plan to collect what I discover in this thread.
Click to expand...
Click to collapse
You will need a different kernel to work with a 5.1 or 5.0 system image. We cannot flash a kernel with this method yet just system images.

Right, so the only thing we can do are modified "roms" based on stock. Can't flash recovery or kernel since those are on separate partitions.

This tool, yaffy, might be of some help. I'm downloading it now to see if it works...

timmyk465 said:
This tool, yaffy, might be of some help. I'm downloading it now to see if it works...
Click to expand...
Click to collapse
Not going to work. You need to mount an ext4 image which is not what that tool is designed for. I'm currently doing so by using Linux and mounting the image as a loop device. I can create a guide for doing so if there's demand.

Ekkoria said:
Not going to work. You need to mount an ext4 image. I'm currently doing so by using Linux and mounting the image as a loop device. I can create a guide for doing so if there's demand.
Click to expand...
Click to collapse
I'd definitely be interested in a guide. I just wish there was a tool for windows that would work.

You can do it on windows but it's way easier on Linux.
I'm gonna get Linux back up and running and see what I can cook up.

Ekkoria said:
Not going to work. You need to mount an ext4 image which is not what that tool is designed for. I'm currently doing so by using Linux and mounting the image as a loop device. I can create a guide for doing so if there's demand.
Click to expand...
Click to collapse
All I want to do is build a flashable img with a modified hosts file. I've found a guide for mounting the image as a loop (which Ive done....) the issue Im running into is changing permissions to be able to actually edit the file once its mounted.
Guess I'll read more and keep tinkering..

ntxct said:
All I want to do is build a flashable img with a modified hosts file. I've found a guide for mounting the image as a loop (which Ive done....) the issue Im running into is changing permissions to be able to actually edit the file once its mounted.
Guess I'll read more and keep tinkering..
Click to expand...
Click to collapse
Open your file manager as root, then open the file.
---------- Post added at 11:49 PM ---------- Previous post was at 11:44 PM ----------
I wrote up and posted a quick guide (which probably sucks) for this purpose.

[6045] If you want to be able to install OTA updates after root READ THIS!

2015/10/07 The information below will be kept to help folks make backups and for linux/mac users to have some images to restore but if you have bricked your phone the recommended solution now is to install Alcatel's Mobile Q software version 4.9.2 or newer and use it to restore your phone to factory condition. Basically turn off the phone..plug it up to the pc via usb and run the software...it should prompt you from there. The link to download the software is here: http://alcatelonetouch.com/global-en/support/download/pixi_3_7_4g.html
*****Warning***** Recent updates from Alcatel have REMOVED the fastboot commands that allow root and custom recovery for some models of the 6039. Before updating read the details here: http://forum.xda-developers.com/showthread.php?t=3173598 and make sure the new update doesn't do the same!
You should also be aware that if your phone hangs on boot and you are rooted don't do a factory reset or you will lose adb access if you had it enabled which can be used to restore your phone
Table of Contents
Post #1: Intro
Post #2: Backup Instructions http://forum.xda-developers.com/showpost.php?p=62006344&postcount=2
Post #3: System Images http://forum.xda-developers.com/showpost.php?p=62006344&postcount=3
Post #4: Restore Instructions and firmware issues http://forum.xda-developers.com/showpost.php?p=62006344&postcount=4
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Folks, OTA updates for Lollipop check if your system has ever been mounted read/write (which is required to root) and if it has they do not allow the update to install. What that means is before you root you need to first go into fastboot and do a fastboot boot of TWRP (this boots twrp on your phone without installing it) then go into twrp and backup your system directory so you always have something to restore to if you want future OTA updates.
The bad news is that for folks who have already rooted, we need TWRP backups of the system partition for each model of the idol 3 BEFORE someone has rooted. 6045i, 6045k, 6045y...are there more?
If you have NOT yet rooted your phone and are willing to help out please post here with your model number(It shows in settings, about phone as Model Number). I'll add some instructions on how to take a backup then the backup needs to be uploaded online somewhere we can access it. The system partition is normally read only so it contains NONE of your personal information.
This paragraph from the TWRP documentation is taken from: https://twrp.me/site/update/2015/06/22/twrp-2.8.7.0-released.html
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.]
Here's an article that explains it better than I can: https://www.androidpit.com/android-5-0-lollipop-ota-update-fail
20150810 - Turns out all thats required to get updates at least for now is doing a FULL unroot. (That may not be the case with a major jump such as from 5.0.2 to 5.1.1) Failure to do a full unroot can result in boot loops after applying updates that currently DO NOT HAVE A SOLUTION because the default recovery for the 6045i and 6045Y do not have the reboot to bootloader option that IS present in the 6045K and all models of the 6039 Idol 3. Thanks Alcatel! An easier solution is to flash an already upgraded firmware if it is available. Canadian users have also found it useful to flash USA firmware (both have a 6045i) to get updates sooner than being released by the cell providers in canada.

Instructions to backup your system prior to rooting.
-Get/install Alcatel USB driver if Windows. (no need for Mac). FROM HERE: http://54.247.87.13/softwareupgrade/Driver/ALCATEL_ADB_ Driver Qualcomm_ADB.rar , or just connect your idol3 to the computer and from the phone select "cd rom" drive..it will install the drivers automatically
Windows and Mac users should have downloaded the android sdk to get adb and fastboot. [ https://developer.android.com/sdk/ ] Linux (ubuntu based) users should install packages android-tools-adb and android-tools-fastboot Windows users can try a minimal adb and fastboot install using the instructions here: http://forum.xda-developers.com/showthread.php?t=2317790 or here: http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/
download twrp from here: https://www.androidfilehost.com/?fid=24052804347778862
-Set USB debugging on in Developer settings (if these are not exposed, go to Settings/About Phone/Build number, and tap 7 times.)
-Plug in USB cable to phone and computer. Tap on USB icon in notifications panel; select MTP (file transfer) mode or PTP also works fine.
-ON your pc open command prompt in the directory where you have placed twrp-2.8.7.0-idol3.img (when using windows in the directory hold shift and press the right button on the mouse, it will pop-up a window where you have to select "open command prompt here" and type "adb reboot-bootloader" to reboot into bootloader
-Then type "fastboot -i 0x1bbb devices" This should show the device
-Type "fastboot -i 0x1bbb boot twrp-2.8.7.0-idol3.img" This will boot twrp on your phone without installing it.
-On your phone do a normal backup but make sure only "system image" (not system) and Boot (to keep the kernel in sync with the system) is checkmarked to be backed up. You can go into TWRP settings and have it write to the external_sd vs using internal "sdcard" before starting the backup if you have one installed
-After backup has completed it will have created a folder named TWRP on your /sdcard or /storage/sdcard1 depending on which you selected (/sdcard by default). Assuming this is your first use of twrp then copy the whole twrp folder over to your pc and zip or rar it then post a message with your model stating you have a backup and we'll work to get it uploaded. If you have previously used twrp and have multiple backups then just go one directory in "/sdcard/TWRP/" and backup only the directory with the date timestamp of your most recent backup.
When uploading to the cloud zip'ing or rar'ing the file will cut it's size by about half. (it's 3gb initially and roughly 900mb afterward) It's still a rather large file so you might look at http://www.filedropper.com/ to upload the file...they claim files allowed up to 5gb and no registration required. https://mega.co.nz is also a good alternative but can be slow. If you have suggestions for a better place to put the files please let me know.
If you are willing to contribute space that will not expire to host the system backups please contact me via pm. Make sure to hit thanks for our generous uploaders.

System Downloads Available [Each download is +- 1GB in size]
(Do not crossflash devices ie flash the 6045i image to a 6045K or 6045Y. We don't know what the results will be!):
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
6045 (5.5 inch model)
From most recent back to "out of the box".
Model: 60450(USA-Cricket) Firmware: 5.0.2-010 03 Link: https://mega.nz/#!xhhy0AKC!hWhDgXCQOGt0cNHcfkkejEEBiP1pjOT5-ZK6mAY5MUU Thanks to squeakychu for the upload!
Model: 6045i(usa) Firmware: 5.0.2.7SRA-UEA2 Link: https://mega.nz/#!dRkgxA5L!z7yVmmgeUWBpAGwJW6ixnGhGBzUky1dfhKksu3yGPKg Thanks to Brian117 for the uploads! (09/28/2015)
Model: 6045i(usa) Firmware: 5.0.2.7SR4-UE40 Link: https://mega.co.nz/#!K9szRIKR!ZdjIiH2Ol0ZCNe2VTSl6cbRyQeZFtafG3Y9CM0ecCkg 20150810 md5sum: 56376824f7c10d8debaec6c3a7100e50
Model: 6045i(usa) Firmware: 5.0.2-7SQR-UER0 Link: https://mega.co.nz/#!FB0DQAhQ!rQ4H39hQR2tDhfniEej-RvsSe5OqWY42_xCsjY08o4k Thanks to buggleston for the upload!
Model: 6045i(usa) Firmware: 5.0.2-7SQ3-UE30 Link: https://mega.co.nz/#!focwnJJL!VQW3Omi3TF4iJzIyNLu73P9gb8i_WKA_fu7ZWUiIsN0 Thanks to Electriccars for the upload!
Model: 6045i(usa) Firmware: 5.0.2.7SMA-UEA1 Link: https://mega.nz/#!pdlWhQLR!D2-mEnxp2SnxH0QBDsSSZ-YrDooJC8BdKronYxziF_A Thanks to lordlittlebrooks for the upload!
Model: 6045i(canada) Firmware: 5.0.2-7SQB-UCB0 Link: https://mega.nz/#!opolxbIY!A9dEfORplfhkmuNwobKsEF2wX6yY3oLq8M9dgWpDNq8 Thanks to KryPTiCk0d3 for the upload!
Model: 6045i(canada) Firmware: 5.0.2-7SQ9-UV93 Link: http://drive.google.com/file/d/0B8Gqss1TYorTaXZrRFdBdDJ2Vnc/view Thanks to green3water5 for the upload!
Model: 6045K(Serbia, Bulgaria, Macedonia and maybe Cz) Firmware: 5.0.2-010 0101001 Link: https://mega.nz/#!L5El0QqA!IrxnA4qyXONyWehaJltc7JsE5TgaAXIdT9RQ73K0Rdw Thanks to bokaco7 and Nikola Jovanovic for the upload!
Model: 6045Y(Europe) Firmware: 5.0.2-010 06 Link: https://mega.nz/#!N9phSbTR!hH0bTJnHcUrwKxdpA-RKyecHNPKls7Cy0fi-Ih3BWkM Thanks to Gynoid for the upload!
Model: 6045Y(Europe) Firmware: 5.0.2-010 05 Link: https://mega.nz/#!pxgwXKIA!TInG7xK9Z-qObX1Cc3BObGp88zx0FCpWI3RDt_wdD0Q and https://mega.nz/#!l5xnSDrL!-y2ye27vODfNAR2qcBAQN7q0gGYA579iRzla07lFkd4 [You will need to flash both as one has the system backup and the other has the boot] Thanks to Gynoid for the upload!
Model: 6045Y(Europe) Firmware: 5.0.2-010 03 Link: http://mega.co.nz/#!CYk2mBCa!XJd1nJI1cUcTcGjwzhApcAyABQ8y54D-bATvgxxHMsE Thanks to zrkkrz for uploading this 2 times!
Model: 6045Y(Europe) Firmware: 5.0.2-010 01 Link: http://data.nettitoimisto.com/f/e308c56574/ Thanks to tommihut for the upload!
Other models not listed? NEEDED!
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
All backups will eventually be mirrored to MEGA. If the file is missing I'm more than likely still trying to get it uploaded. MEGA can be slow however the files should never expire. The folder is here: https://mega.co.nz/#F!DgNhkDKR!GyJsku7nw4F6nLiT4XFRKA
If an individual download link is dead please let me know via post or pm.
Thanks to kirplunk and zrkkrz for uploading backups that ended up having to be replaced due to incorrect instructions to backup system instead of "system image" from within TWRP.

When using these backups.....
There is currently a bug in TWRP that appears to be showing 6045Y for ALL idol3 devices in the recovery.log so make SURE the system image you are flashing is meant for your device to the best of your ability.
Restoring a TWRP backup image:
If you wish to update to a newer firmware or restore an older one you can follow purple.epod's basic instructions here but use the firmware you want to restore: http://forum.xda-developers.com/showpost.php?p=62313284&postcount=1 Also make sure you restore both boot AND system image in the newer firmware's when selecting what to restore.
When restoring the UE40 firmware the first time you go into system update checker you need to delete the existing UE40 update as it kept it around...you should then be able to check updates as normal.

This was brought up in the main rooting thread, but you might also be able to unroot via SuperSU with the Full Unroot option. Haven't tried it yet but if it works, you can just unroot, install whatever OTA there may be, and re-root.

brian117 said:
This was brought up in the main rooting thread, but you might also be able to unroot via SuperSU with the Full Unroot option. Haven't tried it yet but if it works, you can just unroot, install whatever OTA there may be, and re-root.
Click to expand...
Click to collapse
Yeah, I'm the one who brought it up. I thought those about to root should be made aware.
Based on the twrp documentation it sounds like once it's been mounted once as read/write there is a way for them to check and it will kill the ota update. unrooting isn't going to fix that. We also have no good way to intercept the updates so we could alter them to install anyway. I used a squid transparent proxy to find the download url but won't do me any good if my phone can't download the update. If it lets the phone dwonload and then when it runs aborts I may still be able to grab the url and the update could be modified to apply anyway.

tried to upload stock system backup for 6045i
famewolf said:
Reserved 1
Click to expand...
Click to collapse
i have backed up the stock system twrp backup for 6045i zipped in folder then tried your file link to up load, after about 15 minutes it was still uploading seemed to long so i stopped the upload. do you or dallascz have another place to upload or email maybe? i still have not installed the recovery or rooted yet, trying to give back to Idol3ers.
---------- Post added at 01:51 AM ---------- Previous post was at 01:34 AM ----------
famewolf said:
Folks, OTA updates for Lollipop check if your system has ever been mounted read/write (which is required to root) and if it has they do not allow the update to install. What that means is before you root you need to first go into fastboot and do a fastboot boot of TWRP (this boots twrp on your phone without installing it) then go into twrp and backup your system directory so you always have something to restore to if you want future OTA updates.
The bad news is that for folks who have already rooted, we need TWRP backups of the system partition for each model of the idol 3 BEFORE someone has rooted. 6045i, 6045k, 6045y...are there more?
If you have NOT yet rooted your phone and are willing to help out please post here with your model number(It shows in settings, about phone as Model Number). I'll add some instructions on how to take a backup then the backup needs to be uploaded online somewhere we can access it. The system partition is normally read only so it contains NONE of your personal information.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.]
Click to expand...
Click to collapse
i have backed up the stock system twrp backup for 6045i zipped in folder then tried your file link to up load, after about 15 minutes it was still uploading seemed to long so i stopped the upload. do you or dallascz have another place to upload or email maybe? i still have not installed the recovery or rooted yet, trying to give back to Idol3ers.

kirplunk said:
i have backed up the stock system twrp backup for 6045i zipped in folder then tried your file link to up load, after about 15 minutes it was still uploading seemed to long so i stopped the upload. do you or dallascz have another place to upload or email maybe? i still have not installed the recovery or rooted yet, trying to give back to Idol3ers.
---------- Post added at 01:51 AM ---------- Previous post was at 01:34 AM ----------
i have backed up the stock system twrp backup for 6045i zipped in folder then tried your file link to up load, after about 15 minutes it was still uploading seemed to long so i stopped the upload. do you or dallascz have another place to upload or email maybe? i still have not installed the recovery or rooted yet, trying to give back to Idol3ers.
Click to expand...
Click to collapse
kirplunk, how large is the file after you have zipped it? I'll check into some more services. I'm limited by the fact I don't have hi speed and I don't think xda rules allow me to mention any file sharing service that requires registration. If you do a google of "upload large file" and find a service that works for you let me know. If others have a suggestion also let me know. I'm reply back as soon as I find some other sites. Thanks for your assistance!
*update* In other areas of XDA they suggest https://mega.co.nz/ for large file uploads however it would require creating your own account. They give you 50GB. Let me know if this works for you please.

size reply
famewolf said:
kirplunk, how large is the file after you have zipped it? I'll check into some more services. I'm limited by the fact I don't have hi speed and I don't think xda rules allow me to mention any file sharing service that requires registration. If you do a google of "upload large file" and find a service that works for you let me know. If others have a suggestion also let me know. I'm reply back as soon as I find some other sites. Thanks for your assistance!
Click to expand...
Click to collapse
the unzipped folder with files was 2.1gb in size, the zipped folder with files that i tried to upload is 855mb in size. i do not use the cloud at all so i don't have a drop box or any thing of the type. the site you referenced said it was uploading but it seemed 15 minutes was more than enough time for that size of file. my browser kept saying it was uploading and connecting to site.

kirplunk said:
the unzipped folder with files was 2.1gb in size, the zipped folder with files that i tried to upload is 855mb in size. i do not use the cloud at all so i don't have a drop box or any thing of the type. the site you referenced said it was uploading but it seemed 15 minutes was more than enough time for that size of file. my browser kept saying it was uploading and connecting to site.
Click to expand...
Click to collapse
Can you please try https://mega.co.nz/ and see if it works better for you? It will require creating an account but they will give you 50GB and you could use a disposable email address if you prefer. I'm checking other areas of xda to see how they handle large file uploads and this is what I've seen so far.
I have no problem sharing one I've created but there will always be that one person who wants to come along and delete everything in it.
Another is http://www.filedropper.com/ which allows up to 5gb files and keeps them till 30 days of not being downloaded. No registration required.
Also is your backup after the two system updates? Just FYI your upload bandwidth is not going to be as high as your download typically so uploads of large files can take a while.

attempting the second site now, called file dropper.
the file folder i'm uploading is called, 6045i twrp stock system backup.7z
upload is at 10% right now
now at 20%, yes with updates firmware is 5.0.2-7sqr-uero
30% my upload speed should put this file up in 3 minutes but their server is taking it like sucking coffee up through a stir stick, slow
will update when it reaches 100%, but as a junior member i can not post links so you will have to find it at the file dropper.
100% uploaded,
as a junior member this is the best i can do for the link.
www dot filedropper dot com/6045itwrpstocksystembackup
hope this helps

Uploads tend to be much slower than downloads. LTE connections are an exception, but cable and DSL upstream speeds aren't fast.

kirplunk said:
the file folder i'm uploading is called, 6045i twrp stock system backup.7z
upload is at 10% right now
now at 20%, yes with updates firmware is 5.0.2-7sqr-uero
30% my upload speed should put this file up in 3 minutes but their server is taking it like sucking coffee up through a stir stick, slow
will update when it reaches 100%, but as a junior member i can not post links so you will have to find it at the file dropper.
Click to expand...
Click to collapse
Feel free to send me the link in a PM and I'll post it so others can download it in addition to me or I'm sure I can find it based on filename if they have search.
With your permission I'll put it in post #3 with your name and a thank you. I'll have to visit the local library that has rather fast internet to get these files downloaded and moved to one folder for everyone assuming others share theirs as well.

So using stock recovery to Wipe Data/Factory Reset back to new doesn't remove root or r/w status?

mk3 said:
So using stock recovery to Wipe Data/Factory Reset back to new doesn't remove root or r/w status?
Click to expand...
Click to collapse
A factory reset wipes the data and cache partitions. It does nothing to /system since it expects it to be read only.

famewolf said:
A factory reset wipes the data and cache partitions. It does nothing to /system since it expects it to be read only.
Click to expand...
Click to collapse
ahhh.... bummer. Thanks for the clarification.
So I used Hide My Root to hide su binary and the system update doesn't give me the error (like all is fine). Prior to hiding the su binary it throws the error about being rooted.
.

Is the /system partition different than the /system directory that's in the root of the device? If it's the same, we can change the read/write permissions with ES File Explorer if the device is rooted? I'm not sure if it'll offer us the chance, if we want it, to make all the contents of the dir have the same permissions we set for the dir itself. Can the same thing be done from a command line in TWRP?

Why does TWRP show "system" and "system image" as two different options and sizes to backup? I've never seen that before.

maigre said:
Is the /system partition different than the /system directory that's in the root of the device? If it's the same, we can change the read/write permissions with ES File Explorer if the device is rooted? I'm not sure if it'll offer us the chance, if we want it, to make all the contents of the dir have the same permissions we set for the dir itself. Can the same thing be done from a command line in TWRP?
Click to expand...
Click to collapse
The system partition is the same as the /system folder however it's not a file permission that's an issue and you'd never want to set all your files to the same permissions. Here is an article that explains it better than I can: https://www.androidpit.com/android-5-0-lollipop-ota-update-fail

kirplunk said:
the file folder i'm uploading is called, 6045i twrp stock system backup.7z
upload is at 10% right now
now at 20%, yes with updates firmware is 5.0.2-7sqr-uero
30% my upload speed should put this file up in 3 minutes but their server is taking it like sucking coffee up through a stir stick, slow
will update when it reaches 100%, but as a junior member i can not post links so you will have to find it at the file dropper.
100% uploaded,
as a junior member this is the best i can do for the link.
www dot filedropper dot com/6045itwrpstocksystembackup
hope this helps
Click to expand...
Click to collapse
Thanks kirplunk! I've got it downloading and will add my folder as a mirror to try to prevent the file from expiring.

Root ANY LG G4 Variant 100% Success Directives | Root Injection | Less Bricks

Hi everyone. As I found out there's root for the G4 but doing this isn't easy especially if your variant is hard to find or has less users. This may result in you waiting for longer than you should. This thread is for those who can take things into their own hands and do it themselves. The tools are available everywhere but I'll give you the best order and steps. I'm using the China LG G4 H818 Dual SIM variant but this method is UNIVERSAL FOR ALL LG G4s.
The process will involve extracting a system image, injecting root and reflashing this image. Most of the steps are effortless and need just copy and paste with keen eyes. Do it slowly. You need an Ubuntu installation for step 2 of this 3-step tutorial. I used universal USB installer and put in on my 8GB USB. Anywhere will do so far as it boots&works. Beware this thread is not dumb-proof but this will not wipe your data or void your warranty if done successfully.
Step 1 -> Getting the proper system image.
Check here and skip to step 3 if you have your rootedsystem.img
>Don't worry because this doesn't require searching. It is from your device. Every device has a system partition and this method will pull it out as an image without root required.
1--Make sure all drivers are installed properly. I'll not be talking about this. We're on XDA not kindergarten.
2--Download the LG_root file or send command file from here and extract it. US Carrier specific check here
3--Put your device in download mode and connect it to your PC.
4--Open(double-click duh) port.bat and make sure to write down the number after com. There maybe different com numbers but choose the com on the DIAG1 line and write down that number. This is important.
5--Hold shift and right-click in any empty space in the extracted folder. Choose open command windows here.
6-- In that copy and paste this
Code:
[FONT=Lucida Console][COLOR=#ff8c00]Send_Command.exe \\.\COM[/COLOR][COLOR=#00ff00][*insert your number here][/COLOR][/FONT]
7--Now you're in send command mode. Nothing looks different on your phone but that's ok. It should just remain in download mode.
8-- On the computer screen in the window you now see #.
9--Now in this post copy the Backup system to internal storage command specific to your device model number. Check in you settings >general >about if in doubt. This is the most important step. Copy the whole line of code. Highlight with your mouse, select everything on the line and copy.
10--You didn't come all this way to fail so do it. Remember it is device model specific.
11-- Paste it in the command window and hit enter. It should take a while so wait until you see#reappear.
12--Now typeLEAVEall in capital letters. Your device will reboot. Check using the file manager if you have a file called system.img in your internal storage. If yes step 2 is next and you did well. If no repeat it and follow the steps properly. Make sure drivers are installed especially windows 10/8/8.1 users. Check device manager
Step 2 -> Root injection.
1--Prepare your Ubuntu USB or virtual machine or computer.
2--Download inject_root zip from here and extract.
3--Copy the system.img from your phone to the extracted inject_root folder on your PC.
4-Reboot into Ubuntu.
5--Here open a terminal.
6--Gain root access on Ubuntu by typing or copy and paste sudo -i
7--You should either be asked for your password which you have to enter or if you used a USB drive like me you'll see the name change to[email protected]
8--Navigate to the inject_root folder by using cd commands. This can also be done by typing cd then [space] then dragging and dropping the folder into the terminal and hitting enter.
9--You'll now see the name in the terminal become longer with the name of the folder in it.
10--Now type chmod +x autoroot.sh
11--Hit enter then sudo ./autoroot.sh
12--If you get any thing like command not recognized or something of the sort use sudo sh autoroot.sh
-That worked for me.
13--If you're successful the name of the file should change from system.img torootedsystem.img
-Please note don't rename the files. Leave them as they are.
14--Now go back to Windows let's finish this.
Step 3 ->Root
1--Transfer the rootedsytem.img to your phones internal storage.
2--Put your phone in download mode and connect it to your PC.
3--Get into send command mode as in step one.
-Put your device in download mode and connect it to your PC.
-Open port.bat and make sure to write down the number after com. There maybe different com numbers but choose the one that has DIAG1 on the same line as it. Note it down this is important.
-Hold shift and right click in any empty space in the extracted folder. Choose open command windows here.
- In that copy and paste this
Send_Command.exe \\.\COM[*insert your number here]
-Now you're in send command mode. Nothing looks different on your phone but it's find. It should just remain in download mode.
4-Now grab your command to flash system.img line of code from this post. It isn't the same as step one. Copy that an paste in the command window. Make sure it is for your device. They are model specific.
5--This should take a while so wait until you see the # again.
6--After thatLEAVEand upon reboot you should have root.
To Un-root just flash a KDZ file compatible with your device here.
Testimonies
Spudnubs said:
Rooted H812 10g for my fellow Canadians. Enjoy!
https://www.androidfilehost.com/?fid=24052804347821979
Click to expand...
Click to collapse
Wildsheep said:
This root method works for my G4 purchased in Singapore (H815 SEA)
Click to expand...
Click to collapse
luongquang said:
Thanks to @hackarchive, H818p10f done with tut.
Click to expand...
Click to collapse
player911 said:
Fantastic. This method will also ease devs for future rooted firmwares. I really cannot see LG being able to patch this, since this is basically a 3rd party LG Flashing tool. If they block this method, then their own tool will ultimately die with it.
Click to expand...
Click to collapse
GavTheStoner said:
Fantastic! I had almost given up hope of root on my EE LG G4. Have just used this method and now rooted perfectly!
hackarchive You rock! Have a thanks!
Click to expand...
Click to collapse
articular said:
everything worked fine and i successfully got my g4 rooted
my variant is H815TR
all steps easy only the ubuntu part was a bit hard especially for a windows user ( finding an ubuntu version and usb install etc. not root injection part)
ty ty ty again )
Click to expand...
Click to collapse
rirozizo said:
if it were for me to decide if we should delete the low effort root method, i'd totally delete it.
"The more 'manual', the better"
Click to expand...
Click to collapse
Moe5508 said:
Only method that roots my device successfully...I updated to 10e of the H815P and using this method (and only this!0 I was able to root my phone...ah felt so good...
The other 1-click rooting methods I came across in other parts of this forum just fail on the G4...
Click to expand...
Click to collapse
Marshmallow and root situation read here
Hit thanks if you appreciate. Hope I helped.
Credits to them whom without this won't be possible :good:
Thecubed
Team Codefire
ManhIT

This is a good method, thanks for writing this up.
I would like to add a few points....
I recommend you do keep your original system.img on your phones regular internal storage. If you encounter any boot issues you can then re-enter download mode and write the original system.img over the top of the failed root attempt. Use the same command from "step 3: root" but replace rootedsystem.img with system.img. This should still be on your phone from step 1 and will recover your phone from a failed root injection attempt. Note that it will not recover your phone if you messed up the dd command and overwrote other partitons. Be sure to use the right dd command and cut n paste to prevent seek/offset typeos.
I also recommend that you keep a backup of your system.img on your pc. When you run autoroot.sh in step 2 the copy on your pc will be renamed and patched. I suggest copying system.img somewhere else first, or re-copy it off your phone.
Additional credits to blog.lvu.kr. This is the blog of the hobbyist who reverse engineered the download mode protocol, created send_command.exe and gave it to the world. Kudos to you.

How is this any easier than the original method....if anything this requires even more work

kyle1867 said:
How is this any easier than the original method....if anything this requires even more work
Click to expand...
Click to collapse
It's for those who have rare variants.

psycho_asylum said:
It's for those who have rare variants.
Click to expand...
Click to collapse
Then you should probably take out the claim that this method is easier from the OP

Can this be used to inject Xposed as well for those of us with locked BLs.

djkinetic said:
Can this be used to inject Xposed as well for those of us with locked BLs.
Click to expand...
Click to collapse
No, we need to wait for a custom recovery.

psycho_asylum said:
No, we need to wait for a custom recovery.
Click to expand...
Click to collapse
Just used flash fire it worked rocking xposed now on 810!

djkinetic said:
Just used flash fire it worked rocking xposed now on 810!
Click to expand...
Click to collapse
Oh nice! I wasn't adventurous enough to try it. I'll make a system backup and give it a whirl!

Very nice thread, thank you. The steps were short, few, and fairly concise.
I was waiting for something like this where I could modify my own image and I wouldn't have to wipe everything or replace it with a new image.
One thing you might want to mention is that if your phone is encrypted, you'll need to unencrypt it first.
Can anyone link me to some instructions on how to disable OTA updates for an unlocked/international H815T?

kyle1867 said:
How is this any easier than the original method....if anything this requires even more work
Click to expand...
Click to collapse
This is what XDA is all about. It tells you how to inject root into your OWN system image. it's the opposite of spoon feeding. it's about teaching members how to do things for themselves. Too many people come here expecting to be spoon fed and have thigns done for them. This thread teaches people how to do their own work, while learning something at the same time.
Good work OP! :good:

the_scotsman said:
This is what XDA is all about. It tells you how to inject root into your OWN system image. it's the opposite of spoon feeding. it's about teaching members how to do things for themselves. Too many people come here expecting to be spoon fed and have thigns done for them. This thread teaches people how to do their own work, while learning something at the same time.
Good work OP! :good:
Click to expand...
Click to collapse
Thanks. I guess people don't know what XDA is about. Seeing noobs and others trying to spit on hard work when I used my time and device as Guinea pig. Also people don't know this is almost brick-proof because the system image if from their devices. Unless they use wrong commands but all here is just copy and paste. They see lot's of text and get cold feet. Anyways will be updating the OP with system images. If yours is available please share. If you see your image available and you have drivers and LG_root downloaded proceed to step 3.

The only downside is that I have to drag out my windows laptop instead of doing everything on the ubuntu machine I use at work.
But if that's the biggest of my problems then I don't really have a problem

hi, thx for this tutorial, looks good
when flashing back the rooted img,does it wipe everything ? apps, data ... etc
thx
EDIT: just correct me if im wrong
using this method WILL NOT wipe everything on my device cause im rooting my system with everything on it
correct ???
must make sure before i go ahead
thx

How to calculator extractly bs/seek/count ?

Is there a possibility of any personal data being written to /system on a phone during normal use? I can provide 10c Optus AU (carrier 505-02) if I can be sure its not identifying, but ive been using the phone a couple of weeks.
Download link:
https://www.androidfilehost.com/?fid=24052804347799013

optiplex2012 said:
using this method WILL NOT wipe everything on my device cause im rooting my system with everything on it
correct ???
Click to expand...
Click to collapse
correct.
---------- Post added at 06:01 PM ---------- Previous post was at 05:29 PM ----------
djkinetic said:
Can this be used to inject Xposed as well for those of us with locked BLs.
Click to expand...
Click to collapse
HTCuser90 said:
How to calculator extractly bs/seek/count ?
Click to expand...
Click to collapse
I would also like to know this. You can resolve system by running the following. Note that this is for the H815T and is not the same on all variants.
# ls -lZ /dev/block/bootdevice/by-name/system
You'll get something like:
lrwxrwxrwx root root ubject_r:block_device:s0 system -> /dev/block/mmcblk0p47
Which tells you the actual block device (partition its on).
And you can see the size of that with:
# cat /proc/partitions
where you see:
major minor #blocks name
<snip>
259 15 4239360 mmcblk0p47
<snip>
However I dont know how to identify how large a block is or how to calculate the start offset in the main partition.

ok, it worked great
wasnt easy, since im not so familiar with using ubuntu, but all is ok
the explanation of the how to... was great and nothing lost
my H815L is now rooted
thx guys

djkinetic said:
Just used flash fire it worked rocking xposed now on 810!
Click to expand...
Click to collapse
I know it's kind of going off topic, but I figured I'd mention that Flash Fire doesn't work on VS986. It just goes to a black screen and sits there forever. I left it sit for almost an hour. I saw elsewhere it has something to do with automount, I'll have to mess with it further.

hackarchive said:
Hit thanks if you appreciate. I spent hours trying to root so hope I helped.
Click to expand...
Click to collapse
Appreciated but you should include a way to unroot (undo) as well, ie how do we get back to stock (if required) ?