[ROOT] TMO/VZW/ATT/SPRINT/INTL Root your LG G4 with Low Effort Root! - G4 Original Android Development

Hello all,
It's that time of the night where I post things on XDA and wake up to a bajillion PMs.
Without further ado, I introduce "Low Effort Root".
What is this?
Low Effort Root is a root for your LG G4, named such because this is a root we really weren't too interested in releasing, but the phone is gaining critical mass so we figured waiting any longer would be a disservice to the community.
(We also don't like that the root ends up being ~4GB, since we're flashing whole new system partitions.)
We had originally planned on releasing an in-android root app, however time constraints on all the team members has prevented us from devoting the necessary time to it.
This root will root any LG G4, provided we have a pre-rooted system image for it. This is akin to 'flashing a rooted odin' image on a Samsung phone, as we're simply writing a system partition that contains Superuser.
No exploits here, no trickery, just a plain and simple flash and be on your merry way.
Click to expand...
Click to collapse
How do I use this?
Please read the whole directions here carefully. If you miss a step, or you copy the wrong command and run it, your phone will be BRICKED. You will have flashed a partition to some random place on your phone's internal SD, and no amount of sad private messages will be able to help you.
I'm 100% serious, if you do this wrong, you will turn your phone into a paperweight - so please don't go rooting your mom/dad's phone with this method. Wait for something better from us.
Ensure you have the proper drivers for your phone. If you don't, download and install the proper driver below.
Code:
All G4 (except Verizon) - [URL="http://downloads.codefi.re/autoprime/LG/LG_G4/LGUnitedMobile_Win_Driver_Ver_3.14.1.exe"]http://downloads.codefi.re/autoprime/LG/LG_G4/LGUnitedMobile_Win_Driver_Ver_3.14.1.exe[/URL]
Verizon - [URL="http://downloads.codefi.re/autoprime/LG/LG_G4/LG_VZW_United_WHQL_v2.22.0.exe"]http://downloads.codefi.re/autoprime/LG/LG_G4/LG_VZW_United_WHQL_v2.22.0.exe[/URL]
Open this forum link and keep it up in another tab. We'll refer to it again in step 6: http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772 (and while you're at it, give the op there a thanks!)
Download the appropriate files for your phone from the section below. Make sure to grab the Send_Command tools (named LG_Root.zip below)
Extract the tar.gz file you downloaded for your phone, and move the resulting "system.rooted.phonemodel.img" file to the root of your phone's internal SD card with MTP mode. Do not rename this file, or move it into any folders. If you don't get a file named "system.rooted.phonemodel.img" DO NOT continue. You need to properly extract the file.
On the page you opened in step 2, follow steps 1,2,3,6,7,8,and 9 on that page only, then come back here.
Ensure that on step 9, you use the right COM port.
Type "id" and press enter (no quotes).
You should get back some text starting with "uid=(0)root gid=(0)root". If not, press CTRL-C, and do step 9 again (the application sometimes doesn't respond on the first command).
Run the command specified in the section below titled 'Commands to Run' to flash the rooted system image.
After a few minutes of sitting, you should get back a "#" prompt. This indicates the process has finished.
Type "LEAVE" (no quotes) and press enter. Your phone should reboot, and your phone will be rooted.
Now that you're rooted, MAKE SURE YOU DISABLE OTA UPDATES, if you accidentally take an OTA, you might not be able to roll back or fix it.
You can also delete the system.rooted.modelnumer.img from your phone's internal SD card to save some space.
Click to expand...
Click to collapse
Commands to Run
T-Mobile H811 10H Version:
Code:
dd if=/data/media/0/system.rooted.H81110h.img bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
VZW VS986 11A Version:
Code:
dd if=/data/media/0/system.rooted.vs98611a.img bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
International H815 10c Version (NOT H815T, H815TR, H815P, etc - you will lose internationalization and possibly features):
Code:
dd if=/data/media/0/system.rooted.H81510c-EU.img bs=8192 seek=55296 count=529920 of=/dev/block/mmcblk0
AT&T H810 10G Version:
Code:
dd if=/data/media/0/system.rooted.h81010g.img bs=8192 seek=65536 count=579584 of=/dev/block/mmcblk0
Sprint LS991 ZV5 Version:
Code:
dd if=/data/media/0/system.rooted.LS991ZV5.img bs=8192 seek=65536 count=557312 of=/dev/block/mmcblk0
If your phone isn't listed here DO NOT run these commands on your phone. You will break your phone.
If your phone isn't running the EXACT firmware version specified, you will need to OTA to the proper version to root. If you'd like to not OTA, sit tight while we get a better root together.
Click to expand...
Click to collapse
Download Links (more to come soon)
Send_Command tools - ALL variants require this (you'll use this in step #5):
Code:
[URL="http://downloads.codefi.re/thecubed/lg_g4/lef/LG_Root.zip"]http://downloads.codefi.re/thecubed/lg_g4/lef/LG_Root.zip[/URL]
(I'm mirroring these because unfortunately Dev-Host is tricking users into downloading malware with a 'Download' versus 'Download Now' button. As much as I feel bad for mirroring, I'd feel worse if I let people get led astray by a site that is tricking users.)
Download one of the following, depending on your phone's model
T-Mobile:
Code:
[URL="http://downloads.codefi.re/thecubed/lg_g4/lef/h81110h.tar.gz"]http://downloads.codefi.re/thecubed/lg_g4/lef/h81110h.tar.gz[/URL]
Verizon:
Code:
[URL="http://downloads.codefi.re/thecubed/lg_g4/lef/vs98611a.tar.gz"]http://downloads.codefi.re/thecubed/lg_g4/lef/vs98611a.tar.gz[/URL]
International H815 10c Version:
Code:
[URL="http://downloads.codefi.re/thecubed/lg_g4/lef/h81510c-eu.tar.gz"]http://downloads.codefi.re/thecubed/lg_g4/lef/h81510c-eu.tar.gz[/URL]
AT&T:
Code:
[URL="http://downloads.codefi.re/thecubed/lg_g4/lef/h81010g.tar.gz"]http://downloads.codefi.re/thecubed/lg_g4/lef/h81010g.tar.gz[/URL]
Sprint:
Code:
[URL="http://downloads.codefi.re/thecubed/lg_g4/lef/LS991ZV5.tar.gz"]http://downloads.codefi.re/thecubed/lg_g4/lef/LS991ZV5.tar.gz[/URL]
Please do not mirror these files. Also, you do NOT have my permission to roll any of this into a 'one-click' root.
Click to expand...
Click to collapse
Ah Gawd, something went wrong!
Did it really? That's interesting... Luckily short of running the wrong command, you can easily recover from a bad flash by simply looking for the "Return to Stock" thread here on XDA for your phone, and flashing the KDZ from there.
KDZs cover a multitude of sins (short of you putting something in the completely wrong place on the EMMC).
Click to expand...
Click to collapse
Why isn't my variant supported?
See Post #2 by @autoprime (or click here: http://forum.xda-developers.com/showpost.php?p=62028523&postcount=2 )
Click to expand...
Click to collapse
Special Thanks
First, I really need to thank everyone that donated to get Team Codefire phones.
You all are *super* awesome, and we are very grateful to be the recipients of your kindness
That said, if you'd like to consider donating to us for our work, our donation links are here. Thanks!
@thecubed - Paypal Donate - That's me!
@IllegalArgument - Paypal Donate - As usual, IllegalArgument is a genius. He also might be a mad scientist, it won't surprise me when he achieves cold fusion somehow.
@autoprime - Paypal Donate - 99.92% of testing for this root and pretty much all our other goodies get tested by autoprime - he's awesome -- he even wrote up the instructions for this root for me
@jcase - Paypal Donate - Gotta add jcase here, he's a wealth of information and a damn smart dude all around.
Click to expand...
Click to collapse

I just wanna say thanks again to everyone who donated to the original gofundme so we could get these G4's in hand. :highfive:
If you use MTP it shouldnt take too long to move the system.img over to internal scard (no u cant use external sd for this).
If you use ADB push... it takes a good.. 20-25min to push the file over to internal storage.
Using the dd commands to flash the system img should only take a few minutes.
As for the bounty/donations for root... yes there are 4 paypals linked. Ideally you'd split each donation up... as we only get what's donated to each of us. Due to taxes.. multiple ppl involved etc... it's just more difficult (on us) to use a single email.
I'm gonna call out everyone who pledged but doesn't come thru. JK.. maybe.. :silly:
be sure to follow me on twitter to keep up with the latest news and updates.. @utoprime
Command to Flash System.img (All Variants):
These commands are an extension of the OP.. adding support for the rest of the G4 variants not included in initial release.
REPLACE "rootedsystem.img" in your command with the name of the actual rooted.system.img you're using.
Example... if you downloaded a rooted system img for F500K 10F you'd change:
dd if=/data/media/0/rootedsystem.img bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
into
dd if=/data/media/0/rooted.system.F500K10F.img bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
(or whatever the filename is...)
AS991:
Code:
dd if=/data/media/0/[B]rootedsystem.img[/B] bs=8192 seek=65536 count=509952 of=/dev/block/mmcblk0
F500K/L/S :
Code:
dd if=/data/media/0/[B]rootedsystem.img[/B] bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
H810 AT&T :
Code:
dd if=/data/media/0/[B]rootedsystem.img[/B] bs=8192 seek=65536 count=579584 of=/dev/block/mmcblk0
H810PR :
Code:
dd if=/data/media/0/[B]rootedsystem.img[/B] bs=8192 seek=55296 count=529920 of=/dev/block/mmcblk0
H811 T-Mobile :
Code:
dd if=/data/media/0/[B]rootedsystem.img[/B] bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
H812 Canada (All H812s) :
Code:
dd if=/data/media/0/[B]rootedsystem.img[/B] bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
H815 EU/SEA/TWN :
Code:
dd if=/data/media/0/[B]rootedsystem.img[/B] bs=8192 seek=55296 count=529920 of=/dev/block/mmcblk0
H815L :
Code:
dd if=/data/media/0/[B]rootedsystem.img[/B] bs=8192 seek=55296 count=529920 of=/dev/block/mmcblk0
H815P :
Code:
dd if=/data/media/0/[B]rootedsystem.img[/B] bs=8192 seek=55296 count=529920 of=/dev/block/mmcblk0
H815T :
Code:
dd if=/data/media/0/[B]rootedsystem.img[/B] bs=8192 seek=55296 count=529920 of=/dev/block/mmcblk0
H815TR :
Code:
dd if=/data/media/0/[B]rootedsystem.img[/B] bs=8192 seek=55296 count=529920 of=/dev/block/mmcblk0
H818 China:
Code:
dd if=/data/media/0/[B]rootedsystem.img[/B] bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
H818N :
Code:
dd if=/data/media/0/[B]rootedsystem.img[/B] bs=8192 seek=55296 count=529920 of=/dev/block/mmcblk0
H818P :
Code:
dd if=/data/media/0/[B]rootedsystem.img[/B] bs=8192 seek=55296 count=529920 of=/dev/block/mmcblk0
H819 China:
Code:
dd if=/data/media/0/[B]rootedsystem.img[/B] bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
LS991 Sprint :
Code:
dd if=/data/media/0/[B]rootedsystem.img[/B] bs=8192 seek=65536 count=557312 of=/dev/block/mmcblk0
VS986 Verizon :
Code:
dd if=/data/media/0/[B]rootedsystem.img[/B] bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
US991 US Cellular :
Code:
dd if=/data/media/0/[B]rootedsystem.img[/B] bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
Click to expand...
Click to collapse
Pre-Rooted System.img Download Links
These are links for pre-rooted system.imgs from the users.
I will not link to new threads... only system.imgs posted in this thread.
AS991 10C:
Code:
[URL="http://forum.xda-developers.com/showpost.php?p=62213418&postcount=1578"]http://forum.xda-developers.com/showpost.php?p=62213418&postcount=1578[/URL]
H810 10B / 10E:
Code:
[URL="http://forum.xda-developers.com/att-g4/development/root-images-h81010b-h81010e-t3168427"]http://forum.xda-developers.com/att-g4/development/root-images-h81010b-h81010e-t3168427[/URL]
H810 10I:
Code:
[URL="http://forum.xda-developers.com/showpost.php?p=62809806&postcount=2091"]http://forum.xda-developers.com/showpost.php?p=62809806&postcount=2091[/URL]
H810PR 10A:
Code:
[URL="http://forum.xda-developers.com/att-g4/development/ahhh-root-sweet-delicious-root-h810pr-t3168322"]http://forum.xda-developers.com/att-g4/development/ahhh-root-sweet-delicious-root-h810pr-t3168322[/URL]
H812 (All Variants):
Code:
[URL="http://forum.xda-developers.com/showpost.php?p=62115644&postcount=1249"]http://forum.xda-developers.com/showpost.php?p=62115644&postcount=1249[/URL]
H812 10G:
Code:
[URL="http://forum.xda-developers.com/showpost.php?p=63010862&postcount=2172"]http://forum.xda-developers.com/showpost.php?p=63010862&postcount=2172[/URL]
H815 10B Vodafone Germany:
Code:
[URL="http://forum.xda-developers.com/showpost.php?p=62132150&postcount=1365"]http://forum.xda-developers.com/showpost.php?p=62132150&postcount=1365[/URL]
H815 10B Germany EUR (Open):
Code:
[URL="http://forum.xda-developers.com/showpost.php?p=62161571&postcount=1477"]http://forum.xda-developers.com/showpost.php?p=62161571&postcount=1477[/URL]
H815 10D EUR (Open):
Code:
[URL="http://forum.xda-developers.com/showpost.php?p=62225446&postcount=1596"]http://forum.xda-developers.com/showpost.php?p=62225446&postcount=1596[/URL]
H815 SEA 10B:
Code:
[URL="http://forum.xda-developers.com/showpost.php?p=62140625&postcount=1400"]http://forum.xda-developers.com/showpost.php?p=62140625&postcount=1400[/URL]
H815T 10B HKG:
Code:
[URL="http://forum.xda-developers.com/showpost.php?p=62114467&postcount=1242"]http://forum.xda-developers.com/showpost.php?p=62114467&postcount=1242[/URL]
H818P 10D:
Code:
[URL="https://www.androidfilehost.com/?fid=24052804347781803"]https://www.androidfilehost.com/?fid=24052804347781803[/URL]
US991 10A Unlocked:
N/A
US991 10A US Cellular:
Code:
[URL="http://forum.xda-developers.com/showpost.php?p=64854943&postcount=2642"]http://forum.xda-developers.com/showpost.php?p=64854943&postcount=2642[/URL]
US991 10C US Cellular:
Code:
[URL="http://forum.xda-developers.com/showpost.php?p=62115811&postcount=1251"]http://forum.xda-developers.com/showpost.php?p=62115811&postcount=1251[/URL]
Click to expand...
Click to collapse
Backup System to Internal Storage (Commands for all variants):
Rather than flashing a pre-rooted system.img.. the following commands are to backup your current system partition into a system.img on your internal sdcard. You would do this if you want a stock system.img.. possibly to upload/share with others on this forum so someone can pre-root it... or to unroot and go back to stock (though it's probably easier to use a KDZ to go back to stock if you have one available).
AS991:
Code:
dd if=/dev/block/mmcblk0 bs=8192 skip=65536 count=509952 of=/data/media/0/system.img
H810PR, H815 (All variants), H818N/P :
Code:
dd if=/dev/block/mmcblk0 bs=8192 skip=55296 count=529920 of=/data/media/0/system.img
F500, H811, H812, H818, H819, VS986, US991 :
Code:
dd if=/dev/block/mmcblk0 bs=8192 skip=65536 count=548352 of=/data/media/0/system.img
H810 AT&T :
Code:
dd if=/dev/block/mmcblk0 bs=8192 skip=65536 count=579584 of=/data/media/0/system.img
LS991 :
Code:
dd if=/dev/block/mmcblk0 bs=8192 skip=65536 count=557312 of=/data/media/0/system.img
Click to expand...
Click to collapse
How-to Videos:
If you have a related video I think is worth sharing I will add it below.
[How to] Root the LG G4 without bootloader unlock by @rirozizo
How to Root your LG G4 all variants by @Tomsgt aka Rootjunky
Click to expand...
Click to collapse

I'm off to bed here shortly... If anything breaks, I blame autoprime

OMG!!! the links are down though.
I want to try it on mine H815L, i could flash H815 KDZ with no problem, can i root it?

Thanks for the BEST releasing, but does it support Hong Kong H818N? Or H818P? Thank you.

Derpling said:
OMG!!! the links are down though.
I want to try it on mine H815L, i could flash H815 KDZ with no problem, can i root it?
Click to expand...
Click to collapse
Links should be back up.. had some quick scheduled maintenance.
As for if H815L or H815T or H815TR or H815P will work with the existing H815 image... not sure to be honest. It SHOULD but I'm not sure what sort of localization files are included in each of those H815X variants. I would say.. if u wanna go for it.. go for it... just confirm you can grab a KDZ for your phone first.
See here for KDZ info http://forum.xda-developers.com/showthread.php?goto=newpost&t=3147406
Worst case.. the language is wrong or something and you flash back to stock KDZ. We plan on adding more intl system images later today/tomorrow if you don't wanna risk it.
jkvndst said:
Thanks for the BEST releasing, but does it support Hong Kong H818N? Or H818P? Thank you.
Click to expand...
Click to collapse
Like my above answer.. it's hard to say. Im not sure if there are any different files due to dual sim H818N/H818P. I can confirm worst case would be.. just flash KDZ if it doesnt work out with H815 img (for your exact models you mentioned). We plan on adding H818N/P and H818/H819 etc etc later today/tmw.
I can say, if you are H818/H819 china.. do NOT flash anything yet. You need your own images.
F500, H810, H812, H818/9, H818N/P, H815X, LS991, US991 all coming soon. :good:
(we need sleep)

When i flashed H815 KDZ over my L, it does give error when u start the phone, that some language was not found, but i have all languages and all works perfect, so i guess i good to go.
Anyway i gonna try it , need root so badly to change Kernel stuff, THANK YOU!

Excellent news for those not already rooted. I have been lucky enough to have been rooted from Day One but now thanks to you guys its finally time. Let the ROM's commence!

You guys are amazing, thank you very much. You mention blocking the OTA's immediately once we have root, should we use the same method as before with the debloater tool, or is there a better method once we're rooted to disable? Thanks again

My Verizon G4 has the latest OTA update, will that be an issue? Thanks

thenewbigmack said:
You guys are amazing, thank you very much. You mention blocking the OTA's immediately once we have root, should we use the same method as before with the debloater tool, or is there a better method once we're rooted to disable? Thanks again
Click to expand...
Click to collapse
No, users should look into seeing which apks to freeze/delete from system. Debloater tool is nice without root.. but freezing with titanium backup or something.. or just removing the apk might be best bet. As for which apks or services to freeze.. that's gonna differ for each variant.. and it's gonna take a community effort to compile all of that. I think we'll have enough time between now and the next OTA to sort that out. But anyone who doesnt keep up on this and doesnt block ota.. may be stuck without root after that ota. Of course.. there's also a chance that LG will not update the "bootloader version" used for anti-rollback for each update. And if thats the case.. it may still be possible to downgrade using KDZ. Only time will tell... but better to be safe than sorry.
slick_shoes said:
My Verizon G4 has the latest OTA update, will that be an issue? Thanks
Click to expand...
Click to collapse
not an issue. you can use it on 11A. Tmo users can use it on 10h.
no current OTA period will cause an issue for root. as for anything in the future... beware.

Is it now possible to backup the drm-keys before unlocking BL?
Gesendet von meinem LG-H815 mit Tapatalk

Model H815L, root is WORKING, no errors no bootloopes whatsoever, now time to install recovery and smile.
THANK YOU VERY MUCH!!!

Anyone tried H815TUR?

Bigdaddy168 said:
Is it now possible to backup the drm-keys before unlocking BL?
Gesendet von meinem LG-H815 mit Tapatalk
Click to expand...
Click to collapse
Sure, you can backup any partition now.
Code:
su
dd if=/dev/block/bootdevice/by-name/drm of=/sdcard/drm-backup.img
would save your drm partition to your internal sdcard.
Derpling said:
Model H815L, root is WORKING, no errors no bootloopes whatsoever, now time to install recovery and smile.
THANK YOU VERY MUCH!!!
Click to expand...
Click to collapse
Awesome, thanks for confirming... you've now made the "bounty" official :good:
But this is just root... no custom recovery yet (unless you are able to unlock officially thru LG.. but that is only H815 EU Open (no carrier version).

Will this work with v10c-OPT5-SI?
H815-Poland

sardroid said:
Will this work with v10c-OPT5-SI?
H815-Poland
Click to expand...
Click to collapse
yes.. H815 is supported. Country is not relevant. Check your box or settings menu for model.
ALL H815's are supported. User above has confirmed H815L working with the H815 method.
H815T, H815TR, H815P models most likely will work but languages or localization settings may not be included.
If anyone isnt up for "taking a risk".. please wait for us to add support for your exact model.
ALL firmware versions as of today are supported by this root. Future OTAs.. too early to say.

Tmobile H811 10H rooted. No issues so far. Installed Titanium Backup and Adaway and confirm both are working as normal.
Quick question just to confirm: Factory reset shouldn't affect the root right?

Bootup said:
Tmobile H811 10H rooted. No issues so far. Installed Titanium Backup and Adaway and confirm both are working as normal.
Quick question just to confirm: Factory reset shouldn't affect the root right?
Click to expand...
Click to collapse
Sorry, don't have the answer you're looking for, but have a quick question. How have you gone about disabling future OTA's? I'm also on TMobile which is why I ask. Thank you.
---------- Post added at 10:56 AM ---------- Previous post was at 10:53 AM ----------
You guys are amazing... thank you
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Am I doing this correctly?
Code:
C:\Users\Hubert\Desktop\LG_Root>Send_Command.exe \\.\COM3
Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
#id
uid=0(root) gid=0(root) context=u:r:recovery:s0
#
Code:
C:\Users\Hubert\Desktop\LG_Root>Send_Command.exe \\.\COM3
Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
#id
uid=0(root) gid=0(root) context=u:r:recovery:s0
#dd if=/data/media/0/system.rooted.H81510c-EU.img bs=8192 seek=55296 count=52992
0 of=/dev/block/mmcblk0
#

Related

[RECOVERY+LOKI][CWM][MDK][VZW] SCH-I545 CWM v1.0

DISCLAIMER:
Your device, your responsibility. I am not liable for anything you flash, including this.
As a result you'll probably want to read the rest of the thread and at least be aware of what you're flashing.
You've been warned.
CM: CWM Based Recovery for SCH-I545 (jfltevzw)​
Features:
This is comes from CM as it is provided in the source repos. I will be keeping it as such at this time.
If modifications deviate from CM source we will set up a new repo.
The recovery image has already been patched using the Loki method.
This also means it is tied to MDK signature and should only be flashed on MDK.
Screenshots: None
Latest Build: v1.1
Tar/ZIP Mirror: [CWM][RECOVERY]Team SXTP CWM for Galaxy S4 (Team SXTP Site)
Flash Instructions - READ THESE CAREFULLY!!!
1) Download Zip
2) Unpack Zip and place items on your phone. Assumes you're doing commands from folder where files were extracted to.
For the sake of testing let's say /data/local/tmp like djrbliss used. (ADB push was used in that example)
Code:
adb push recovery.lok /data/local/tmp/
adb push loki_flash /data/local/tmp/
3) Go to ADB shell, su and flash using following commands: (assumes path is /data/local/tmp for Step 2)
Code:
adb shell
su
chmod 755 /data/local/tmp/loki_flash
/data/local/tmp/loki_flash recovery /data/local/tmp/recovery.lok
If successful you should see something similar to:
Code:
[+] Loki validation passed, flashing image.
2253+1 records in
2253+1 records out
9230848 bytes transferred in 0.656 secs (14071414 bytes/sec)
[+] Loki flashing complete!
Assuming you see the above, you should be ready to boot to recovery.
If you do not see this you should immediately flash the stock recovery by dd.
If you don't know how to do that, stop, ask for help. Let's try not to brick a phone doing this, okay?
Summary Changelog:
Code:
v1.1 - Correct typo on device name (in CM device tree). Repo was still okay.
v1.0 - Initial based on Sprint progress (jf series shares same fstab)
Source:
CyanogenMod Official Repositories
Device Dependencies:
android_device_samsung_jf-common
android_device_samsung_msm8960-common
android_device_samsung_qcom-common
Verizon GS4 Device Repository
NOTE: Due to potential copyright issues I do not include a vendor repo.
You can extract the files from the phone or ROM as needed - should you decide to build on your own.
Credits:
Early Bringup Advice: Entropy512, Shabbypenguin, Cordell12
Current Advisors/Collaborators: Noobnl (CM CDMA Maintainer)
Testers: Mohogalore, robbyamor, crawj and others
Steve Kondik (Cyanogen) for CM development and jf common work
The CM maintainters who continue to improve CM along with Mr. Kondik
The crew that is Paranoid Android - Pure Hybrid!
Djrbliss for the Loki Method. (and for permission to include loki_flash in the zip!)
...and of course! You, the community, for your support as well! Thank you!
OP has been updated with a Loki patched recovery image and flash instructions.
If you run into problems, STOP and post here with the issue.
Let's do this as safely as possible until we confirm some safe flashes.
Again, asking that anyone who flashes this post their results. Obviously a lot of folks watching and although it shouldn't be an issue everyone likes to wait for first outside validation before flashing.
If it helps at all, I used the same process for the most part. It does indeed work.
1|[email protected]:/ # /data/local/tmp/loki_flash recovery /data/local/tmp/twrp.lok
covery /data/local/tmp/twrp.lok <
[+] Loki validation passed, flashing image.
2559+1 records in
2559+1 records out
10484224 bytes transferred in 0.713 secs (14704381 bytes/sec)
[+] Loki flashing complete!
only difference is I used TWRP
NxtGenCowboy said:
If it helps at all, I used the same process for the most part. It does indeed work.
1|[email protected]:/ # /data/local/tmp/loki_flash recovery /data/local/tmp/twrp.lok
covery /data/local/tmp/twrp.lok <
[+] Loki validation passed, flashing image.
2559+1 records in
2559+1 records out
10484224 bytes transferred in 0.713 secs (14704381 bytes/sec)
[+] Loki flashing complete!
only difference is I used TWRP
Click to expand...
Click to collapse
where'd you get the twrp.lok file? following djrbliss' instructions?
t3project said:
where'd you get the twrp.lok file? following djrbliss' instructions?
Click to expand...
Click to collapse
No.
thats what I renamed it to since I used a twrp img
im losing my damn mind. someone care to explain this?
Code:
[email protected]:/sdcard # /sdcard/loki_flash recovery /sdcard/twrp.lok
/sdcard/loki_flash recovery /sdcard/twrp.lok
sh: /adcard/loki_flash: not found
127|[email protected]:/sdcard #
i get this after a chmod of loki_flash. if i dont do chmod on it it says it cannot find the file loki_flash.....wtf?
Code:
[email protected]:/sdcard # /sdcard/loki_flash recovery /sdcard/twrp.lok
/sdcard/loki_flash recovery /sdcard/twrp.lok
sh: /sdcard/loki_flash: can't execute: Permission denied
126|[email protected]:/sdcard #
t3project said:
im losing my damn mind. someone care to explain this?
Code:
[email protected]:/sdcard # /sdcard/loki_flash recovery /sdcard/twrp.lok
/sdcard/loki_flash recovery /sdcard/twrp.lok
sh: /adcard/loki_flash: not found
127|[email protected]:/sdcard #
i get this after a chmod of loki_flash. if i dont do chmod on it it says it cannot find the file loki_flash.....wtf?
Code:
[email protected]:/sdcard # /sdcard/loki_flash recovery /sdcard/twrp.lok
/sdcard/loki_flash recovery /sdcard/twrp.lok
sh: /sdcard/loki_flash: can't execute: Permission denied
126|[email protected]:/sdcard #
Click to expand...
Click to collapse
Derp. What permissions are you giving it?
NxtGenCowboy said:
No.
thats what I renamed it to since I used a twrp img
Click to expand...
Click to collapse
I tried just renaming the .img file to .lok, but it gave me a few errors. So using djrbliss's Loki tool (much thanks!) I generated a file for the TWRP recovery.
Here is the link: twrp.lok - 10.00 MB
---------- Post added at 02:52 PM ---------- Previous post was at 02:50 PM ----------
t3project said:
im losing my damn mind. someone care to explain this?
Code:
[email protected]:/sdcard # /sdcard/loki_flash recovery /sdcard/twrp.lok
/sdcard/loki_flash recovery /sdcard/twrp.lok
sh: /adcard/loki_flash: not found
127|[email protected]:/sdcard #
i get this after a chmod of loki_flash. if i dont do chmod on it it says it cannot find the file loki_flash.....wtf?
Code:
[email protected]:/sdcard # /sdcard/loki_flash recovery /sdcard/twrp.lok
/sdcard/loki_flash recovery /sdcard/twrp.lok
sh: /sdcard/loki_flash: can't execute: Permission denied
126|[email protected]:/sdcard #
Click to expand...
Click to collapse
You have to put the files in a folder like /data/local/tmp since the sdcard folder does not allow executables contrary to the instructions provided. (At least that was my understanding when trying to debug the same issue!)
fallingup said:
Derp. What permissions are you giving it?
Click to expand...
Click to collapse
all the good ones. haha 755
trvrlol said:
I tried just renaming the .img file to .lok, but it gave me a few errors. So using djrbliss's Loki tool (much thanks!) I generated a file for the TWRP recovery.
Here is the link: twrp.lok - 10.00 MB
---------- Post added at 02:52 PM ---------- Previous post was at 02:50 PM ----------
You have to put the files in a folder like /data/local/tmp since the sdcard folder does not allow executables contrary to the instructions provided.
Click to expand...
Click to collapse
lol.....see told you i was losing it
I get a successful flash but still only get stock android recovery. I think it is because I can't find the install reovery.sh to delete it
mikebuck69 said:
I get a successful flash but still only get stock android recovery. I think it is because I can't find the install reovery.sh to delete it
Click to expand...
Click to collapse
It's in /system/etc.
I think I read in the other thread, they had success doing this on the pre-release kernal.
Sent from my SCH-I545 using Xparent Green Tapatalk 2
garwynn said:
It's in /system/etc.
Click to expand...
Click to collapse
not on my S4 it isn't lol. I get the successful flash, reboot to recovery, get stock recovery, reboot system from there and I then get the Samsung logo with the unlocked padlocked telling me SOMEthing unnoficiall got installed. Phone boots up and I boot back into recovery, still stock recovery, reboot system again and I get normal boot up, no padlock screen. I'm still on the mdk kernel so I will try flashing the pre-release kernel a little later and trying again.
I see a recovery-resource.dat in /system/etc but not recovery.sh.
Sent from my SCH-I545 using Xparent Green Tapatalk 2
You can use GooManager and install Twrp... Just have root first.
NxtGenCowboy said:
You can use GooManager and install Twrp... Just have root first.
Click to expand...
Click to collapse
Have you done this? I tried it on a (locked bootloader) Note 2 and got the screen that I needed to take the phone to a Verizon store. It took me an hour or more to fix it.
Sent from my SCH-I545 using Xparent Green Tapatalk 2
NxtGenCowboy said:
You can use GooManager and install Twrp... Just have root first.
Click to expand...
Click to collapse
I tried that and got the "You have installed unofficial blah blah contact Verizon" message. I had to generate a TWRP loki image and flash using the OP's instructions.
It works fine. Make sure you are rooted.
NxtGenCowboy said:
It works fine. Make sure you are rooted.
Click to expand...
Click to collapse
Yea they posted an updated release already that is Loki modified, so you are actually correct!

[how to] reset your lock status flag

first and formost special thanks CastleBravo,without whos testing and help in this thread,for DNA. he asked all the right questions,and gave others all the right answers while i was at work and couldnt respond. also to treadwayj,who dumped mmcblk0p3 from his still locked phone for comparison,providing valuable confirmation.
with m7,this is just one way to skin the cat. you can also use the revone tool to change back to *locked*
use clockwork recovery it did not work for me using twrp. agaion, if you want to flash these zips,do now use twrp.
i happened across this thread inthe gsm evo 3d forum: http://forum.xda-developers.com/showthread.php?t=1970252 and found it to work on the rezound,inc 4g,sensation 4g,cdma evo 3d,MT4GS,Amaze 4g,one s,droid DNA,m7,and prolly several others.
this does NOT mean you can unlock your bootloader without going thru htcdev. all this means,is that if your bootloader is unlocked after s-off,you can get rid of the relocked watermark and get back to 100% locked prior to s-on for legitimate warranty purposes.
ive always been unlocked. for S&Gs,i dumped mmcblk0p3 and found the described "HTCU" at 0x8404. changed it to 0x00000000 and voila! back to locked
afterward,relfashed my origianl mmcblk0p3,wich brought me back to unlocked with no getting or flashing tokens.
this is NOT a patched or hex edited hboot.again,this is ONLY to get back your original ***locked*** status.
*this is for s-off phones only
2 ways to do it:
1)old school
this assumes you to have drivers,adb/fastboot,a hex editor,a fair understanding about what youre doing,and the ability to follow directions on the linked thread
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="Red"]cd c:\mini-adb_vigor[/COLOR]
c:\mini-adb_vigor>[COLOR="red"]adb devices[/COLOR]
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HTxxxxxxxxxx device
c:\mini-adb_vigor>[COLOR="Red"]adb shell[/COLOR]
[email protected]:/ $ [COLOR="red"]su[/COLOR]
su
[email protected]:/ # [COLOR="red"]dd if=/dev/block/mmcblk0p3 of=/sdcard2/mmcblk0p3[/COLOR]
dd if=/dev/block/mmcblk0p3 of=/sdcard2/mmcblk0p3
64734+0 records in
64734+0 records out
33143808 bytes transferred in 9.519 secs (3481858 bytes/sec)
[email protected]:/ # [COLOR="red"]exit[/COLOR]
exit
[email protected]:/ $ [COLOR="red"]exit[/COLOR]
exit
c:\mini-adb_vigor>[COLOR="red"]adb pull /sdcard2/mmcblk0p3[/COLOR]
2292 KB/s (33143808 bytes in 14.116s)
[COLOR="Blue"]*modify mmcblk0p3 with a hex editor[/COLOR]
c:\mini-adb_vigor>[COLOR="Red"]adb push mmcblk0p3mod /sdcard2/mmcblk0p3mod[/COLOR]
2478 KB/s (33143808 bytes in 13.059s)
c:\mini-adb_vigor>[COLOR="red"]adb shell[/COLOR]
[email protected]:/ $ [COLOR="red"]su[/COLOR]
su
[email protected]:/ # [COLOR="red"]dd if=/sdcard2/mmcblk0p3mod of=/dev/block/mmcblk0p3[/COLOR]
dd if=/sdcard2/mmcblk0p3mod of=/dev/block/mmcblk0p3
64734+0 records in
64734+0 records out
33143808 bytes transferred in 18.937 secs (1750214 bytes/sec)
[email protected]:/ #[COLOR="red"] exit[/COLOR]
exit
[email protected]:/ $ [COLOR="red"]exit[/COLOR]
exit
c:\mini-adb_vigor>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\mini-adb_vigor>
2)noob friendly
-download the appropriate zips,place on sd card.
-boot to recoverywipe cache/dalvik
-flash in recovery. i recomend to run query first,to make sure its working. tested on my personal m7_u,and m7_ul, one s,amaze,jetstream,rezound,inc) 4g,sensation,MT4GS,and gsm evo 3d. tested by castlebravo on DNA.
query:query_bootloader.zip
query_bootloader.zip f335f78f9f46469c823da0c671026de5
unlock:unlock_bootloader.zip
unlock_bootloader.zip f335f78f9f46469c823da0c671026de5
lock:lock_bootloader.zip
lock_bootloader.zip f335f78f9f46469c823da0c671026de5
a little bit of explanation. yes,the md5s are all the same. its the same file,just named differently. the script behaves based on the name of the zip. i knew if i only included 1 download and instructed folks to change the name there would be confusion,so this is my attempt to keep it simple. feel free to download one file and just change the name to make the other zips.
it also works to make your phone relocked if for some reason you want it that way(rename relock_bootloader.zip). i didnt include a zip for that because i figued there would be no demand.
before:
after:
sure,i could have easily faked the above photos,but i dint.
again,all credit goes to s trace on the above thread,be sure to click the thanks button on his post. all i did was remove the device check per his instruction. DO NOT flash on other devices without checking for the proper location of the lock flag first.
DISCLAIMER:this is not my work. i have tested it on my own device,but use it at your own risk. if it melts your phone into a lil pile of goo,its not my fault.
enjoy
special thanks
-BC for originally dumping mmcblk0p3 for me to know this was worth exploring for dna
-CastleBravo for testing and suport on the original test thread,as well as the pics you see here
-treadwayj for dumping mmcblk0p3 from his still locked phone.
-brian for unlocking his bootloader,then dumping mmcblock0p3 to make sure it would work for cdma evo3d phones too
-brian and donb for fearless testing of the zip files on evo3d cdma
This is only for the flags, correct? It won't turn S-ON, will it? I'm not sure how thorough the T-mobile folks check to see if you've rooted your phone or not. Mine says locked but I have S-OFF so i can still do as I please with the phone. NINJA!
silentcovenant said:
This is only for the flags, correct? It won't turn S-ON, will it? I'm not sure how thorough the T-mobile folks check to see if you've rooted your phone or not. Mine says locked but I have S-OFF so i can still do as I please with the phone. NINJA!
Click to expand...
Click to collapse
It will lock the bootloader again, but that doesn't matter now that we have S-OFF.
I just used revone's guide for resetting the flag from "Relocked" to "Locked".
Lafenear said:
It will lock the bootloader again, but that doesn't matter now that we have S-OFF.
I just used revone's guide for resetting the flag from "Relocked" to "Locked".
Click to expand...
Click to collapse
Okay, yeah, me too.. I'm having a lot of issues with getting AOSP ROMs to work with my phone, I'm starting to think the phone is defective. I can't imagine what would be going wrong, though. What would I tell T-Mobile if/when I take the phone to them, I just want another HTC One that works with my flashing habit.
Also, anyone know how to reflash the stock recovery? I notice someone posted the .img file of it
silentcovenant said:
Okay, yeah, me too.. I'm having a lot of issues with getting AOSP ROMs to work with my phone, I'm starting to think the phone is defective. I can't imagine what would be going wrong, though. What would I tell T-Mobile if/when I take the phone to them, I just want another HTC One that works with my flashing habit.
Also, anyone know how to reflash the stock recovery? I notice someone posted the .img file of it
Click to expand...
Click to collapse
you should be able to just flash it in fastboot
Sent from my HTC One using xda premium
Can you actually S-ON again? Don't need to but just curious!
meleelord said:
Can you actually S-ON again? Don't need to but just curious!
Click to expand...
Click to collapse
http://androidforums.com/showthread.php?p=5918438
Sent from my ADR6425LVW using Tapatalk 2

[Root][V500] G Pad 4.4.2 Stock w/ IOroot25 [Yippee!]

IOroot
IOroot was originally a Windows script to root the LG G2 on 4.2.2 made by IOMonster... based on the original adb backdoor found by GiantPune and later posted by jcase.
The script has grown to support various other LG devices on Android 4.0 - 4.4.2... 4.4.2 kk_root.zip by autoprime. Current IOroot25r1 by autoprime.
Supported devices include LG Optimus G, G2, G3, G Pro, G Pro 2, G Flex and G Pad just to name a few.
4.4.2 root will NOT work for you if you cannot get into the stock recovery menu w/the "adb reboot recovery" command.
Check the supported devices list below. You may have to downgrade to 4.2.2 or below and root that instead.
Or your device may not be supported at all. Again.. check the supported device list below.
Current Version - IOroot25 refresh 1
Download IOroot zip, extract and run script to root. ADB must be enabled (USB Debugging ON).
Click the button below for IOroot device support list, manual and automated root and other info.
Device Model and Firmware Supported List:
LG G Pad - 4.4.2 Only
LG Optimus G - all 4.2.2 and 4.4.2
LG G2:
AT&T D800 - D80010d/D80010o/4.4.2
D801 - TMO(all 4.2.2 // No 4.4.2 support), CLR(all 4.2.2 // 4.4.2 ??), WND(all 4.2.2 // 4.4.2 ??), VTR(all 4.2.2 // 4.4.2 ??)
D802 - all 4.2.2 and 4.4.2
D803 - all
D805 - all
D806 - all
F320K - Shipping 4.2.2 ROM/F320K20a/20f // 4.4.2 ??
F320L - Shipping 4.2.2 ROM/F320L20b/20e // 4.4.2 ??
F320S - Shipping 4.2.2 ROM/F320S20a/20g // 4.4.2 ??
Sprint LS980 - All 4.2.2 and 4.4.2
Verizon VS980 - All 4.2.2 and 4.4.2
LG G Flex:
F340 series - All 4.2.2 // 4.4.2 ??
D950 - All 4.2.2 // No 4.4.2 support
D955 series - All 4.2.2
D958 series - All 4.2.2 // No 4.4.2 support
D959 - All 4.2.2 // No 4.4.2 support
LS995 - All 4.2.2 and 4.4.2
LG G Pro - All 4.4.2 Only
LG G Pro 2:
F350 series - Shipping ROM // 4.4.2 ??
D838 - Shipping ROM // 4.4.2 ??
LG G3
F400 Series - Shipping ROM
Manual Root Method:
Code:
[B][SIZE="2"]Windows Drivers:[/SIZE][/B]
[I]Verizon Drivers - [URL="http://bit.ly/1ibRvc3"]HERE[/URL]
Drivers for everyone else - [URL="http://bit.ly/18EPHZN"]HERE[/URL][/I]
[B]4.4.2 Manual Root:[/B]
[SIZE="1"]
Download and extract the latest IOroot.zip
Enable USB Debugging. VZW users must also enable ethernet mode.
Open terminal/command prompt. windows/linux users: cd into /ioroot folder. mac users cd into /ioroot/mac
(windows users can hold shift key, right click in ioroot folder. Select "[URL="http://www.techsupportalert.com/content/how-open-windows-command-prompt-any-folder.htm"]open command window[/URL]" option.[/SIZE]
[B]1. adb devices[/B]
[B]2. adb reboot recovery[/B]
(when booted in recovery, select: 'apply update from adb' with power button)
[B]3. adb sideload kk_root.zip[/B]
You should see [URL="http://forum.xda-developers.com/showthread.php?p=51530027"]DAT ROOT[/URL] when finished.
reboot phone. done.
[B]4.2.2 Manual Root:[/B]
[SIZE="1"]Download and extract the latest IOroot.zip
Enable USB Debugging. VZW users must also enable ethernet mode.
Open terminal/command prompt. windows/linux users: cd into /ioroot folder. mac users cd into /ioroot/mac
(windows users can hold shift key, right click in ioroot folder. Select "[URL="http://www.techsupportalert.com/content/how-open-windows-command-prompt-any-folder.htm"]open command window[/URL]" option.[/SIZE]
copy/paste commands below.. hitting enter/return after each line.
Linux/Mac users may have to enter ./ before adb on each line.
Example: ./adb push g2_security /sdcard/g2_security
[SIZE="1"][B]1:[/B] [B][I]adb devices[/I][/B]
(make sure it sees your device; if "offline" turn on phone/unlock and accept RSA key prompt)
[B]2:[/B] Choose next line based on model and firmware version:
AT&T D80010d (Shipping ROM): [B][I]adb push g2_security /sdcard/g2_security[/I][/B]
AT&T D80010o/10q: [B][I]adb push ytiruces_1a_att /sdcard/ytiruces_1a[/I][/B]
KT F320k (Shipping ROM): [B][I]adb push g2_security /sdcard/g2_security[/I][/B]
KT F320K20a/20f (KitKat): [B][I]adb push ytiruces_1a_kk /mnt/shell/emulated/0/ytiruces_1a[/I][/B]
LGU F320L (Shipping ROM): [B][I]adb push g2_security /sdcard/g2_security[/I][/B]
LGU F320L20b/20e (KitKat): [B][I]adb push ytiruces_1a_kk /mnt/shell/emulated/0/ytiruces_1a[/I][/B]
D802(T) (4.2.2): [B][I]adb push g2_security /sdcard/g2_security[/I][/B]
D803 (4.2.2): [B][I]adb push ytiruces_1a_d803 /sdcard/ytiruces_1a[/I][/B]
D805 (4.2.2): [B][I]adb push g2_security /sdcard/g2_security[/I][/B]
D806 (4.2.2): [B][I]adb push g2_security /sdcard/g2_security[/I][/B]
SKT F320S (Shipping ROM): [B][I]adb push g2_security /sdcard/g2_security[/I][/B]
SKT F320S20a/20g (KitKat): [B][I]adb push ytiruces_1a_kk /mnt/shell/emulated/0/ytiruces_1a[/I][/B]
Sprint LS980ZV7/ZV8: [B][I]adb push g2_security_spr /sdcard/g2_security[/I][/B]
Sprint LS980ZVA (OTA): [B][I]adb push ytiruces_1a_ls980 /sdcard/ytiruces_1a[/I][/B]
T-Mobile D80110c (Shipping ROM): [B][I]adb push g2_security /sdcard/g2_security[/I][/B]
T-Mobile D80110g (OTA): [B][I]adb push ytiruces_1a_tmo /sdcard/ytiruces_1a[/I][/B]
Verizon VS98010B (Shipping ROM): [B][I]adb push g2_security_vzw /sdcard/g2_security[/I][/B]
Verizon VS98011A/12B (OTA): [B][I]adb push ytiruces_1a_vzw /sdcard/ytiruces_1a[/I][/B]
Videotron D801 (4.2.2): [B][I]adb push ytiruces_1a_d803 /sdcard/ytiruces_1a[/I][/B]
Wind D801 (4.2.2): [B][I]adb push ytiruces_1a_d803 /sdcard/ytiruces_1a[/I][/B]
F340-Series (4.2.2): [B][I]adb push ytiruces_1a_F340JB /sdcard/ytiruces_1a[/I][/B]
D950 (4.2.2): [B][I]adb push ytiruces_1a_kk /sdcard/ytiruces_1a[/I][/B]
D955-Series (4.2.2): [B][I]adb push ytiruces_1a_kk /sdcard/ytiruces_1a[/I][/B]
D956-Series (4.2.2): [B][I]adb push ytiruces_1a_kk /sdcard/ytiruces_1a[/I][/B]
D958-Series (4.2.2): [B][I]adb push ytiruces_1a_kk /sdcard/ytiruces_1a[/I][/B]
D959 (4.2.2): [B][I]adb push ytiruces_sumtz /sdcard/ytiruces_sumtz[/I][/B]
LS995 (4.2.2): adb push ytiruces_1a_ls995 /sdcard/ytiruces_1a
F350K/L/S (4.4.2): [B][I]adb push ytiruces_1a_kk /sdcard/ytiruces_1a[/I][/B]
[B]********************************************************
This next depends on your computer/phone model...
USB Connection Mode needs to be toggled.
Ways to do this are listed below...
a. Unplug usb cable from phone then re-plug.
b. Toggle USB mode from Charge to MTP back to Charge
c. Toggle USB mode from Ethernet to MTP back to Ethernet (VZW users)
********************************************************[/B]
[B]3:[/B] [B][I]adb shell[/I][/B]
(you should now see a # instead of a $. # = root)
[B]4:[/B] [B][I]exit[/I][/B]
[B]5:[/B] [B][I]adb shell "mount -o remount,rw /system"[/I][/B]
[B]6:[/B] [B][I]adb push su /system/xbin/su[/I][/B]
[B]7:[/B] [B][I]adb push su /system/xbin/daemonsu[/I][/B]
[B]8:[/B] [B][I]adb push install-recovery.sh /system/etc/install-recovery.sh[/I][/B]
[B]9:[/B] [B][I]adb shell "chown 0.0 /system/xbin/su;chmod 06755 /system/xbin/su"[/I][/B]
[B]10:[/B] [B][I]adb shell "chown 0.0 /system/xbin/daemonsu;chmod 06755 /system/xbin/daemonsu"[/I][/B]
[B]11:[/B] [B][I]adb shell "chown 0.2000 /system/etc/install-recovery.sh;chmod 755 /system/etc/install-recovery.sh"[/I][/B]
[B]12:[/B] [B][I]adb shell "sync;mount -o remount,ro /system"[/I][/B]
[B]13:[/B] [B][I]adb install Superuser.apk[/I][/B]
REBOOT AFTER STEP #13
[/SIZE]
v
Automated .bat/.sh Directions:
Download latest ioroot.zip. Unzip and run bat/sh. Follow the onscreen instructions.
4.4.2 is rooted through stock recovery. Once in recovery use volume keys to select "update with adb" then hit the power button... then continue with the script.
4.4.2 users will see DAT ROOT when finished rooting. Reboot phone. Done.
Windows:
Download and install proper ADB driver. Enable USB Debugging. Double-click on root.bat
Linux:
cd into /IOroot/ folder
chmod +x root.sh
./root.sh
Mac:
cd into /IOroot/mac/ folder
chmod +x root.sh
./root.sh
Windows Drivers:
Verizon Drivers - HERE
Drivers for everyone else - HERE
EFS Backup:
EFS is automatically backed up for all 4.2.2(and below) devices.
EFS is backed up into the ioroot folder on your computer. If running ioroot on mac.. it'll be in the ioroot/mac folder.
Store backed up EFS partitions somewhere safe.
4.4.2 devices will not have automatic EFS backup.
Use the commands below to backup EFS.
Code:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst1 of=/sdcard/modemst1.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst2 of=/sdcard/modemst2.img
Not Working?
If you are on 4.4.2 and cannot get into a stock recovery menu with adb reboot recovery then you CANNOT root 4.4.2 on your device.
You must downgrade to 4.2.2 with stock tot or kdz, retain root and take OTA updates to 4.4.2
OR
downgrade to 4.2.2 and install custom recovery and manually upgrade your way to 4.4.2 by flashing a KK rom + modem.
Make sure to read all of the scripts on-screen text or you may miss something. Hitting a button when it's not time to do so or not reading everything on screen can cause problems. Make sure the phone is unlocked with the screen on whenever possible as well.
If the scripts fail for you check out the manual directions further down the page. The manual method is only a few ADB commands and can help if I've messed up in the scripts somewhere... or if the scripts just don't seem to be working for you. Taking it one step at a time manually almost always results in success.
Still not working?
I need the output from the 4 ADB commands below along with IOroot version and if it was on Windows/Linux/Mac. Any errors you come across would help as well...
adb shell "getprop ro.product.model"
adb shell "getprop ro.build.target_operator"
adb shell "getprop ro.lge.swversion"
adb shell "getprop ro.build.fingerprint"
What's Next?
Confirm full root with rootchecker. ( @joeykrim )
Support a great dev by buying the Pro version.
If you only did the "temp root/adb only root" then you can confirm root by opening adb shell and seeing # instead of $.
For custom recovery(TWRP/CWM) on 4.2.2 and below run FreeGee ( @Shelnutt2 )
Check out the FreeGee donate version if you want to support a great dev.
For custom recovery(TWRP) on 4.4.2 run AutoRec by @Cloudyfa for a safe and easy install.
IOroot25r1 Download: HERE
Changelog:
v25r1: Fixed LG OG EFS backup. Added D802T 4.2.2 support. Script checks for 4.4.2 first.
v25: Added root for 4.4.2 devices. Now works on most LG 4.4.2 devices. Thanks to @jarari2 for the idea to go through stock recovery.
v24: added support for G2 D800 10q, G Flex D956 and G Pro 2 F350K/L/S(thanks to @hkfriends for confirming ioroot method still works)
v23: added support for AT&T G Flex D950 10c.
v22: added support for TMO D959 G Flex. Tweaked scripts EFS backup... hopefully no more errors.
v21: added support for Sprint LS980ZVA update. Added EFS backup support.
v20: added support for all D802/D805/D806. Updated all scripts. Added LG Optimus G and LG G Flex support. SuperSu now installed in /system.
v19: added support for MORE F320 4.4 firmware. Added Singtel D802 support. Linux/Mac script fixes.
v18: added support for MORE F320 4.4 firmware. Added Vodafone(VDF) carrier(should work with at least Shipping ROM). Tweaked scripts.
v17: added F320* 4.4 KitKat root. Added SuperSu.4.4 users must reboot after running root script(mac/linux)
v16: added TMO 10g root and "SCA" root(D802/D805)
v15: added ATT 10o root.
v12: added Verizon 12B root.
v11: added linux support and Sprint LS980 root(both thanks to @Shelnutt2)
​y u no hit thanks button?​
@autoprime You da man
id10terror said:
@autoprime You da man
Click to expand...
Click to collapse
The lack of root was the only reason I withheld from upgrading to stock KK with the G2. I can live without a lot of things, but not UDN.
Many thanks!
Thank autoprime, regained root smoothly on my newly updated G Pad.
How to make EFS backup without root? I updated my G Pad to 4.4.2 and lost root.
thank you. installed on my G Pad 4.4.2 stock
I uploaded the zip on VirusTotal (Link )
and ClamAV says it's an Andr.Exploit.Ratc.
A false report?
Recovery
I managed to root my 4.4.2 tablet with this method.
I have had no luck to unlock the bootloader or install a custom recovery.
Anybody with advice on this when the tablet is running stock 4.4.2.
mortenchristensen said:
I managed to root my 4.4.2 tablet with this method.
I have had no luck to unlock the bootloader or install a custom recovery.
Anybody with advice on this when the tablet is running stock 4.4.2.
Click to expand...
Click to collapse
dd the old aboot. Look at step 3 here. http://forum.xda-developers.com/showthread.php?t=2698267 you probably want to delete the build.prop out of the directory if you want to keep your current build.prop. I don't know if this ever got finished but this would work as well http://forum.xda-developers.com/showpost.php?p=51613184&postcount=54
Wolkenstern said:
I uploaded the zip on VirusTotal (Link )
and ClamAV says it's an Andr.Exploit.Ratc.
A false report?
Click to expand...
Click to collapse
did you look into what Andr.Exploit.Ratc even is?
it's a root exploit... deemed a virus because it roots android. you do want root right?
autoprime said:
did you look into what Andr.Exploit.Ratc even is?
it's a root exploit... deemed a virus because it roots android. you do want root right?
Click to expand...
Click to collapse
Sorry, I didn't look futher into it
But it works, I had this fastboot error because TWRP was gone, even after flashing it again.
Then I did Step 3, like suggested in the comment above and it works.
i have a problem... after upgrade from stock 4.2.2 to 4.4.2 with LG tool at first execute of ioroot they do a factory format and only after this they do a success at 2nd try.
But i lost all my data. Fortunately i have a nandroid.
how to regain root without data lost?
and if i try to restore \data partition from a 4.2.2 nandroid backup on this rooted 4.4.2 factory resetted?
nozyk12 said:
How to make EFS backup without root? I updated my G Pad to 4.4.2 and lost root.
Click to expand...
Click to collapse
bump.
EFS backup is necessary?
Works perfectly
I just downloaded KitKat (in the US) using the LG Mobile Support Tool and rooted with ioroot25 last night. Excellent root tool, very easy way to root your G Pad 8.3!
Works fine, but erase all your data
Rooting worked fine. Warning about the the possible loss of data would have been nice.
Running the Xposed Framework with Gravitybox. PIE Control gives a better real estate.
Too early to comment on the battery performance. Nova launcher gives a smooth, stutter
experience.
Done on my Gpad with 4.4.2 rooting worked fine, no data loss
autoprime, thanks a lot :good:
Sent from my LG-V500 using xda app-developers app
Hey I am trying to root with a Mac. Having troubles going about doing the process. I followed all instructions. And when the tablet goes to stock recovery.... It says no command with a android icon.
Any pointers?
Sent from my Nexus 5 using xda app-developers app
---------- Post added 12th April 2014 at 12:09 AM ---------- Previous post was 11th April 2014 at 11:13 PM ----------
Nevermind..... Rooted it
Sent from my Nexus 5 using xda app-developers app
Hi, thanks for the work!
If I root using this, can I go back to stock if I need to?
Tried it and it doesn't work for me. Followed manual precisely.
Once it boots into recovery there is no "apply update from adb" which I could click on. There are only the normal buttons from TWRP 2.7.0.1 like install, backup etc. Anyone can help?
Sent from my LG-V500 using Tapatalk
Edit:
Got it installed via adb but root didn't work. Went into TWRP, Mounted System, went to File Manager and deleted anything related to my previous SuperSU and then reflashed SuperSu and all went well.
When executing the .bat file, and then entering stock recovery,
at the bottom it reads:
E:missing bitmap stage_empty
(Code -1)
E:missing bitmap stage_fill
(Code -1)
The root is fine, and I have root access.
However does this cause problems in the future?

Help install cm-11-UNOFFICIAL-d620 Alpha

Do not know what I did right
SD file transfer
Do
Command
Su
Sync
Reboot recovery
I pressed install file is shown getting error
Why?
CM11 is in alpha. You must expect a brick if something goes wrong.
And (no offense) from that you wrote, you don't seem to know how to restore a brick.
My recommendation is not to try it!!
Also, isn't one post enough for your problem?!
Sent from my D620R [Stock 4.4.2]
Vagelis1608 said:
CM11 is in alpha. You must expect a brick if something goes wrong.
And (no offense) from that you wrote, you don't seem to know how to restore a brick.
My recommendation is not to try it!!
Also, isn't one post enough for your problem?!
Sent from my D620R [Stock 4.4.2]
Click to expand...
Click to collapse
Hahaha do not understand what you record
Just realized that trying to install it.. why?
The stock recovery not install CM11 need to flash CWM or TWRP. To do this, first unlock the bootloader. Here is the topic http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
Vagelis1608 said:
CM11 is in alpha. You must expect a brick if something goes wrong.
And (no offense) from that you wrote, you don't seem to know how to restore a brick.
My recommendation is not to try it!!
Also, isn't one post enough for your problem?!
Sent from my D620R [Stock 4.4.2]
Click to expand...
Click to collapse
Using CM11 from 09.08.2014 and I have no problem with it. Rom a lot better and smoother than stock
eta82 said:
Using CM11 from 09.08.2014 and I have no problem with it. Rom a lot better and smoother than stock
Click to expand...
Click to collapse
He obviously doesn't know what to do if anything goes wrong (no offense).
If he bricks his phone, it's his responsibility, not ours!
Sent from my D620R [Stock 4.4.2]
Vagelis1608 said:
He obviously doesn't know what to do if anything goes wrong (no offense).
If he bricks his phone, it's his responsibility, not ours!
Sent from my D620R [Stock 4.4.2]
Click to expand...
Click to collapse
You're right. It's not our problem if you decide to take this step and unlock the bootloader must reckon with the possibility to brick your phone. On this subject is mentioned in the subject line phone unlock and flash CWM so I guess is aware of what they are reading
eta82 said:
You're right. It's not our problem if you decide to take this step and unlock the bootloader must reckon with the possibility to brick your phone. On this subject is mentioned in the subject line phone unlock and flash CWM so I guess is aware of what they are reading
Click to expand...
Click to collapse
You say my phone can be brick... brick I do not know what it is but I guess it lock Cell Phones
http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
What's this? I need to do this?
You can return to its former wonder anyway? Reset?
I just want step by step how to install it did not confuse me
Or, should you? http://forum.xda-developers.com/g2-mini/development/rom-pac-rom-lg-g2-mini-d620-alpha-t2876820
http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
How do I install this example TWRP-d620.img
What do I do with this file?
I have ADB
There are all [=
Just what to do where to start an application I beg help me
Write me step by step how to do this request
You can also talk to me on Skype haimmalka85
haimmalka said:
You say my phone can be brick... brick I do not know what it is but I guess it lock Cell Phones
http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
What's this? I need to do this?
You can return to its former wonder anyway? Reset?
I just want step by step how to install it did not confuse me
Or, should you? http://forum.xda-developers.com/g2-mini/development/rom-pac-rom-lg-g2-mini-d620-alpha-t2876820
Click to expand...
Click to collapse
This means that you can spoil your phone. Already it does not run, it will be worthless :crying:
But if you're not afraid to lose a few $ no to help these subjects
http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
http://forum.xda-developers.com/g2-mini/development/recovery-testing-lg-g2-mini-d620-t2835276
If you do not understand what it says forsake activities
Try it on your own risk
and once you decide to unlock the bootloader then flash CWM then download CM11 upload on SD back up the rom and flash Cm11 in CWM
eta82 said:
This means that you can spoil your phone. Already it does not run, it will be worthless :crying:
But if you're not afraid to lose a few $ no to help these subjects
http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
http://forum.xda-developers.com/g2-mini/development/recovery-testing-lg-g2-mini-d620-t2835276
If you do not understand what it says forsake activities
Try it on your own risk
and once you decide to unlock the bootloader then flash CWM then download CM11 upload on SD back up the rom and flash Cm11 in CWM
Click to expand...
Click to collapse
I understand ..
You send me a link
I went not understand what to do
I explain I consumed
Give me a direction where to start
This material misunderstood me explain a little request briefed
haimmalka said:
I understand ..
You send me a link
I went not understand what to do
I explain I consumed
Give me a direction where to start
This material misunderstood me explain a little request briefed
Click to expand...
Click to collapse
First Unlock the bootloader of this guidance document http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748 editing aboot.img own or use this with attachet
Next flash CWM http://forum.xda-developers.com/g2-mini/development/recovery-testing-lg-g2-mini-d620-t2835276
in terminal emulator enter a command
su
reboot recovery to enter CWM
next use CWM to flash CM11
eta82 said:
First Unlock the bootloader of this guidance document http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748 editing aboot.img own or use this with attachet
Next flash CWM http://forum.xda-developers.com/g2-mini/development/recovery-testing-lg-g2-mini-d620-t2835276
in terminal emulator enter a command
su
reboot recovery to enter CWM
next use CWM to flash CM11
Click to expand...
Click to collapse
Thanks for attempting to help
http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
I came here
I do not know what to do here
What this example
Get aboot.img and abootb.img:
Use "ADB SHELL" or a Terminal Emulator:
dd if = / dev / block / platform / msm_sdcc.1 / by-name / aboot of = / sdcard / aboot.img
dd if = / dev / block / platform / msm_sdcc.1 / by-name / abootb of = / sdcard / abootb.img
Open each with a hex editor.
Search for the byte chain 20 00 EB 00 00 50 FF FF E0 E3 0A
Make sure that it exists only once.
Replace the next 4 byte by DF FF FF EA.
You will get: 20 00 EB 00 00 50 E3 FF E0 FF FF FF DF 0A EA
Save aboot.img as aboot4.img and abootb.img as abootb4.img
Do it on your own risk!
Flash back unto them:
dd if = / sdcard / aboot4.img of = / dev / block / platform / msm_sdcc.1 / by-name / aboot
dd if = / sdcard / abootb4.img of = / dev / block / platform / msm_sdcc.1 / by-name / abootb
It also
What to do where to start
What actions do
http://forum.xda-developers.com/g2-mini/development/recovery-testing-lg-g2-mini-d620-t2835276
I think I give up I'm selling this instrument complicated
Request If you want to help spare 10 minutes of your time
Skype picks me together (haimmalka85) made ​​this request, I brought up in front of you
haimmalka said:
Thanks for attempting to help
http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
I came here
I do not know what to do here
What this example
Get aboot.img and abootb.img:
Use "ADB SHELL" or a Terminal Emulator:
dd if = / dev / block / platform / msm_sdcc.1 / by-name / aboot of = / sdcard / aboot.img
dd if = / dev / block / platform / msm_sdcc.1 / by-name / abootb of = / sdcard / abootb.img
Open each with a hex editor.
Search for the byte chain 20 00 EB 00 00 50 FF FF E0 E3 0A
Make sure that it exists only once.
Replace the next 4 byte by DF FF FF EA.
You will get: 20 00 EB 00 00 50 E3 FF E0 FF FF FF DF 0A EA
Save aboot.img as aboot4.img and abootb.img as abootb4.img
Do it on your own risk!
Flash back unto them:
dd if = / sdcard / aboot4.img of = / dev / block / platform / msm_sdcc.1 / by-name / aboot
dd if = / sdcard / abootb4.img of = / dev / block / platform / msm_sdcc.1 / by-name / abootb
It also
What to do where to start
What actions do
http://forum.xda-developers.com/g2-mini/development/recovery-testing-lg-g2-mini-d620-t2835276
I think I give up I'm selling this instrument complicated
Request If you want to help spare 10 minutes of your time
Skype picks me together (haimmalka85) made ​​this request, I brought up in front of you
Click to expand...
Click to collapse
Make a backup of the file aboot
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img
Phone must be rooted and install busybox instal it
If you have D620r you can download the file from the first post at the bottom of the attached here you have a direct link to this file. you have to download it to your computer. Then copy the file to the phone memory (sdcard), download the terminal emulator play store and install on your phone.
OK
Next
Open terminal emulator and give root privileges type in the terminal
Code:
su
dd if=/sdcard/aboot4.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Done
eta82 said:
Make a backup of the file aboot
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img
Phone must be rooted and install busybox instal it
If you have D620r you can download the file from the first post at the bottom of the attached here you have a direct link to this file. you have to download it to your computer. Then copy the file to the phone memory (sdcard), download the terminal emulator play store and install on your phone.
OK
Next
Open terminal emulator and give root privileges type in the terminal
Code:
su
dd if=/sdcard/aboot4.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Done
Click to expand...
Click to collapse
D620r
Yes it is my device
I need someone to help me guidance
Do it with me together
You can do this with me via Skype request?
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img This stage right?
Now with I understand correctly download it aboot.img - [Click for QR Code] (2.00 MB, 234 views)
Copy it to the SD memory card!??
Copy it to the SD memory card
Then this command register
su
dd if = / sdcard / aboot4.img of = / dev / block / platform / msm_sdcc.1 / by-name / aboot
Then do what it will do?
Should be connected USB device?
Or after it copies a file can then install rom memory?
eta82 said:
Make a backup of the file aboot
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img
Phone must be rooted and install busybox instal it
If you have D620r you can download the file from the first post at the bottom of the attached here you have a direct link to this file. you have to download it to your computer. Then copy the file to the phone memory (sdcard), download the terminal emulator play store and install on your phone.
OK
Next
Open terminal emulator and give root privileges type in the terminal
Code:
su
dd if=/sdcard/aboot4.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Done
Click to expand...
Click to collapse
Busybox is not needed
Stock includes the dd command
Sent from my D620R [Stock 4.4.2]
Vagelis1608 said:
Busybox is not needed
Stock includes the dd command
Sent from my D620R [Stock 4.4.2]
Click to expand...
Click to collapse
I'm going nuts who can help me it has been installed properly
https://www.youtube.com/watch?v=8aRrmxCOnQ0 It's okay to do the right directory request is made?
haimmalka said:
D620r
Yes it is my device
I need someone to help me guidance
Do it with me together
You can do this with me via Skype request?
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img This stage right?
Now with I understand correctly download it aboot.img - [Click for QR Code] (2.00 MB, 234 views)
Copy it to the SD memory card!??
Copy it to the SD memory card
Then this command register
su
dd if = / sdcard / aboot4.img of = / dev / block / platform / msm_sdcc.1 / by-name / aboot
Then do what it will do?
Should be connected USB device?
Or after it copies a file can then install rom memory?
Click to expand...
Click to collapse
what you can see on the screenshot does not have assigned permissions root is visible stamp ($) and should be (#)
# You get when you give root privileges
haimmalka said:
Then do what it will do?
Should be connected USB device?
Or after it copies a file can then install rom memory?
Click to expand...
Click to collapse
If you are using a terminal on the phone there is no need to connect the USB
eta82 said:
what you can see on the screenshot does not have assigned permissions root is visible stamp ($) and should be (#)
# You get when you give root privileges
If you are using a terminal on the phone there is no need to connect the USB
Click to expand...
Click to collapse
Before I make this Guide
https://www.youtube.com/watch?v=8aRrmxCOnQ0
I have a strange problem why it does not appear to me
??
I get this message
haimmalka said:
D620r
Yes it is my device
I need someone to help me guidance
Do it with me together
You can do this with me via Skype request?
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img This stage right?
Now with I understand correctly download it aboot.img - [Click for QR Code] (2.00 MB, 234 views)
Copy it to the SD memory card!??
Copy it to the SD memory card
Then this command register
su
dd if = / sdcard / aboot4.img of = / dev / block / platform / msm_sdcc.1 / by-name / aboot
Then do what it will do?
Should be connected USB device?
Or after it copies a file can then install rom memory?
Click to expand...
Click to collapse
haimmalka said:
Before I make this Guide
https://www.youtube.com/watch?v=8aRrmxCOnQ0
I have a strange problem why it does not appear to me
??
I get this message
Click to expand...
Click to collapse
To access the options developers have to tap 7-10 times is an option in Settings> Info About phone> Build number
haimmalka said:
Before I make this Guide
https://www.youtube.com/watch?v=8aRrmxCOnQ0
I have a strange problem why it does not appear to me
??
I get this message
Click to expand...
Click to collapse
Google: How to activate adb
Google: Install adb in 15 seconds
Sent from my D620R [Stock 4.4.2]
Vagelis1608 said:
Google: How to activate adb
Google: Install adb in 15 seconds
Sent from my D620R [Stock 4.4.2]
Click to expand...
Click to collapse
OK I managed to figure out what to do
I'm stuck here
I did not get here just like what?
Continue?

Changing SPLASH SCREEN / BOOTLOGO

TUTORIAL TO CHANGE BOOT LOGO​
Hey Guys ,
This is a Detailed Explained Steps for changing your boot logo / splash image by @UditKarode [DEV OF CRIMSON KERNEL]
So here it goes :-
Open termux, type su and press enter. Then type:
1) dd if=/dev/block/by-name/splash of=splash.img
This will extract your splash/boot partition image into splash.img
-----------------------
2) dd skip=0 count=16384 ibs=1 if=splash.img of=header.img
dd skip=16384 count=6998454 ibs=1 if=splash.img of=1.bmp
dd skip=7014838 count=6998454 ibs=1 if=splash.img of=2.bmp
dd skip=14013292 count=6998454 ibs=1 if=splash.img of=3.bmp
dd skip=21011746 count=6998454 ibs=1 if=splash.img of=4.bmp
dd skip=28010200 count=39098664 ibs=1 if=splash.img of=end.img
exit
This will 'extract' images so that they can be changed
-----------------------------------
3) edit 3.bmp according to your liking and replace it
------------------------------------
4) cat header.img 1.bmp 2.bmp 3.bmp 4.bmp end.img > patched_splash.img
------------------------------------
5) su -c dd if=patched_splash.img of=/dev/block/by-name/splash
------------------------------------
Now whenever you reboot your phone you will see the new splash image before the boot logo. Always keep backup of original splash.img in case something goes wrong.
Done , Enjoy , Profit
HIT THE THANK BUTTON ITS FREE OF COST IF IT HELPED YOU​
WELL, IF U LIKE MY WORK THEN DON'T FORGET TO HIT THE LIKE BUTTON . KThanks.
sourav24071999 said:
TUTORIAL TO CHANGE BOOT LOGO​
Hey Guys ,
This is a Detailed Explained Steps for changing your boot logo / splash image by @UditKarode [DEV OF CRIMSON KERNEL]
So here it goes :-
Open termux, type su and press enter. Then type:
1) dd if=/dev/block/by-name/splash of=splash.img
This will extract your splash/boot partition image into splash.img
-----------------------
2) dd skip=0 count=16384 ibs=1 if=splash.img of=header.img
dd skip=16384 count=6998454 ibs=1 if=splash.img of=1.bmp
dd skip=7014838 count=6998454 ibs=1 if=splash.img of=2.bmp
dd skip=14013292 count=6998454 ibs=1 if=splash.img of=3.bmp
dd skip=21011746 count=6998454 ibs=1 if=splash.img of=4.bmp
dd skip=28010200 count=39098664 ibs=1 if=splash.img of=end.img
exit
This will 'extract' images so that they can be changed
-----------------------------------
3) edit 3.bmp according to your liking and replace it
------------------------------------
4) cat header.img 1.bmp 2.bmp 3.bmp 4.bmp end.img > patched_splash.img
------------------------------------
5) su -c dd if=patched_splash.img of=/dev/block/by-name/splash
------------------------------------
Now whenever you reboot your phone you will see the new splash image before the boot logo. Always keep backup of original splash.img in case something goes wrong.
Done , Enjoy , Profit
HIT THE THANK BUTTON ITS FREE OF COST IF IT HELPED YOU​
Click to expand...
Click to collapse
Thanks a lot bro .. it worked for me as u given this violet channel :good:
Arav Aggarwal said:
Thanks a lot bro .. it worked for me as u given this violet channel :good:
Click to expand...
Click to collapse
Anytime bro :good::angel:
If anyone needed urget help related to this ping me on TG (ONLY URGENT) :good:
Why not this?
Sudeep Duhoon said:
Why not this?
Click to expand...
Click to collapse
Ayee Puru sir is here... Maybe all users dont have pc hahaha.. Ur one is simple af
sourav24071999 said:
Ayee Puru sir is here... Maybe all users dont have pc hahaha.. Ur one is simple af
Click to expand...
Click to collapse
Hahahaha like me mobi user
Arav Aggarwal said:
Hahahaha like me mobi user
Click to expand...
Click to collapse
yeah, it's working very well
mathan7 said:
yeah, it's working very well
Click to expand...
Click to collapse
I didnt get thease steps please help me i want some help
i found a orignal google splash screen for violet's *.img file
can use it on levender(n7p)?
Is bootloader unlock or root needed???
Basith FReZze said:
Is bootloader unlock or root needed???
Click to expand...
Click to collapse
Try?
Hi, are you able to make bootanimation like pixel android 10 animation? Thanks
bryan081686 said:
Hi, are you able to make bootanimation like pixel android 10 animation? Thanks
Click to expand...
Click to collapse
It's in rom
Change Android bootscreen to Android log or kernel ring buffer with Magisk module.
You guys can Use "Foxy boot" Module from Magisk modules. It will replace your default boot screen with Linux command line like boot screen. You can see what is actually happening while booting your device.
Does it need a rooted device..?
Got it , it needs a rooted device.
will this work on redmi note 7?

Categories

Resources