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?
Related
Hello everyone,
This is lsplash, a linux port of EZ Splash Screen Flasher by TrueBlue_Drew + small additions.
You can use this script to convert picture file to image and flash this image as splash screen.
I added some crop feature to create multiple .img from a larger picture.
I think this script should work on Mac OSX but I did not test it...
Thanks
TrueBlue_Drew! Most of the command to convert / flash are coming from his script.
Original script and thread : http://forum.xda-developers.com/showthread.php?t=956434
xda dev and community. Learning each day with you guys!
YOU ARE USING THIS TOOL AT YOUR OWN RISK AND I AM NOT RESPONSABLE
FOR ANY DAMAGE THAT MAY OCCUR FROM YOU MODIFYING YOUR PHONE.
Dependencies
ffmpeg
imagemagick
android SDK / adb
fastboot
lsplash is not shipped with any dependencies. You must use your package manager to install them.
You can find fastboot here : http://koushikdutta.blurryfox.com/G1/
Info : http://wiki.cyanogenmod.com/wiki/Fastboot
* Using i386 on 64 bits system is fine
Usage
lsplash is a command line utilities. Use ./lsplash -h to print help.
You can find the result of each command in workdir/. lsplash create a copy of your picture and always work in this sub folder.
Convert an picture :
./lsplash.sh -i glacier.png -o mycustom.img
Click to expand...
Click to collapse
Crop large picture :
./lsplash.sh -i One_Piece_wall.jpg -c 480x800
Click to expand...
Click to collapse
Result :
$:>ls workdir
ffmpeg.log
One_Piece_wall.CROP-0.jpg
One_Piece_wall.CROP-0.jpg.img
One_Piece_wall.CROP-1.jpg
One_Piece_wall.CROP-1.jpg.img
One_Piece_wall.CROP-2.jpg
One_Piece_wall.CROP-2.jpg.img
One_Piece_wall.CROP-3.jpg
One_Piece_wall.CROP-3.jpg.img
One_Piece_wall.CROP-4.jpg
One_Piece_wall.CROP-4.jpg.img
One_Piece_wall.CROP-5.jpg
One_Piece_wall.CROP-5.jpg.img
One_Piece_wall.CROP-6.jpg
One_Piece_wall.CROP-6.jpg.img
One_Piece_wall.CROP-7.jpg
One_Piece_wall.CROP-7.jpg.img
One_Piece_wall.jpg
Click to expand...
Click to collapse
You can also use the -c option with a smaller image. Black border will be added.
Backup your current splash screen :
./lsplash.sh -b
Click to expand...
Click to collapse
Flash image to your phone :
./lsplash.sh -f workdir/mycustom.img
Click to expand...
Click to collapse
Download
http://4nakama.net/share/dev/lsplash-1.0.tar.bz
Note
I'm a J2EE developer; not a bash developer. If you spot any error or if you want to contribute, feel free to contact me or to submit your suggestion here.
This script is available under wtfpl licence
Click Thanks button if you like it
Regards.
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!
Hello everybody. I need help figuring out what command line configuration to put inside of the parentheses of
Code:
fastboot -c " "
How can I find out what command line to put in so that I can use
Code:
fastboot boot
Apparently since Android 4.4 you can no longer simply do the command
Code:
fastboot boot img.mg
and you have to do it something like
Code:
fastboot -c "console=ttyHSL0,115200,n8 androidboot.hardware=mako lge.kcal=0|0|0|x" img.img
or
Code:
fastboot -c "lge.kcal=0|0|0|x" boot img.img
or else it won't boot. The above commands work for the nexus 4. I do not have the source for my device but I do have the boot.img and zimage. I need this info to help me root the HD6!
can you put the boot and zimage somewhere so i can download them.
HT123 said:
can you put the boot and zimage somewhere so i can download them.
Click to expand...
Click to collapse
Yes I will do that later today
[quote name="AdamOutler" post=57883049]So that is your CMDLINE. You can get the default CMDLINE from the stock boot.img. If you are on Ubuntu, you can
apt-get install abootimg
Click to expand...
Click to collapse
, then
abootimg -x path/to/boot.img
Click to expand...
Click to collapse
The file named something.cfg will contain the stock CMDLINE. Hope that helps.[/QUOTE]
I appreciate your reply. Neat tool. Before I was using unpackbootimg and it would create a blank boot.img-cmdline file. I just tried out your method and got similar results:
bootsize = 0x51f100
pagesize = 0x800
kerneladdr = 0x10008000
ramdiskaddr = 0x11000000
secondaddr = 0x10f00000
tagsaddr = 0x10000100
name =
cmdline =
Click to expand...
Click to collapse
I am guessing that the image should not require an additional command line param. But I am unable to boot even the stock boot img with fastboot boot. Is this a result of a locked bootloader?
kernel
Any progress? may be you can give us the kernel binary, so we can also test together
senzhk said:
Any progress? may be you can give us the kernel binary, so we can also test together
Click to expand...
Click to collapse
HT123 said:
can you put the boot and zimage somewhere so i can download them.
Click to expand...
Click to collapse
https://drive.google.com/open?id=0Bx_94ujbh0qoTm5rd0R5a041Ymc&authuser=0
Tried fastboot boot boot.img. It said Downloaded, and booting, but nothing happened.
I remember you have UART output, do you get any output whille 'booting'?
senzhk said:
Tried fastboot boot boot.img. It said Downloaded, and booting, but nothing happened.
I remember you have UART output, do you get any output whille 'booting'?
Click to expand...
Click to collapse
It shows some log about kernel size and ram size and then stops loging
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
#
Hello Everyone!
After i managed to change the boot animation, i started researching some ways to change the boot logo or the splash screen that appears before the boot animation.
Boot animations and splash screens are two different things. The splash screen is the first static frame that you see the moment you turn on your phone. It is displayed before boot animation and it is usually much harder to change.
To change your boot animation, view my post at: http://forum.xda-developers.com/honor-7/help/how-to-change-boot-animation-huawei-t3247851
Back to the splash screen, so far I know the following:
1. The image file must be stored in RGB565 format. Photoshop and Paint.Net (with a plugin) are capable of saving in this format. In Photoshop, you can find it from the advanced options of .bmp.
2. There is a file called "oemlogo.mbn" which i think is responsive for the boot logo. After changing it though, it did not have any affect on the boot logo or splash screen.
If someone knows which file is responsive for the splash screen or he/she can point out a way to change that, it would be greatly appreciated.
Thanks in advance for your help!
Best Regards,
Ken
Here is the solution
All the credits goes to Ziolek67 and Kostyan_nsk, I just made the zip to revert back to our stock logo, and made his guide compatible to our device. Thanks to @kenshiwara for helping me.
**TAKE NANDROID BACKUP VIA TWRP RECOVERY BEFORE DOING THIS**
1. Install adb and fastboot in your PC.
2. Dump your "oeminfo" partition by executing this command
Code:
adb shell su -c "dd if=/dev/block/platform/hi_mci.0/by-name/oeminfo of=/sdcard/oeminfo"
this will be saved in your internal storage as "oeminfo". Saving this to PC is recommended. To do that execute this command
Code:
adb pull /sdcard/oeminfo oeminfo
3. Now, Ziolek67 mentioned to edit the pulled "oeminfo" but in our case I tried and got error "resolution mismatch", so I pulled out his provided stock "oeminfo" of Huawei Ascend P7, which works fine, the sizes are also same of both the "oeminfo". Download this tool, extract and save it to the folder having adb and fastboot.
4. Make your own image with extension *.bmp. The resolution of the image should match your device resolution (1080x1920 pixels). Put it to adb folder.
5. Download OEMinfo.zip extract it and put "oeminfo" in adb folder.
6. Put your *.bmp image in "oeminfo" by executing this command.
Code:
OEM_logo.exe oeminfo *your_logo.bmp*
7. Push new "oeminfo" to your internal storage by executing this command
Code:
adb push oeminfo /sdcard/oeminfo
8. Put new "oeminfo" with new logo in your device by executing this command
Code:
adb shell su -c "dd bs=32768 if=/sdcard/oeminfo of=/dev/block/platform/hi_mci.0/by-name/oeminfo"
**UPDATED THE ABOVE COMMAND, THANKS TO @sminki
9. Now reboot your device to see your changed logo.
10. To revert back to stock Honor logo simply flash this file using TWRP recovery.
You can get more info here thanks to Kostyan_nsk.
How to make a compatible *.bmp image
Create a new file in Adobe Photoshop with these parameters:
Width: 1080 pixels
Height: 1920 pixels
Resolution: 72 pixels/inch
Color Mode: RGB Color, 8-bit
Click to expand...
Click to collapse
After making your image save it with these parameters:
Extension: *.bmp
File Format: Windows
In "Advanced Options"
Select R5 G6 B5 from 16-bit depth options.
Click to expand...
Click to collapse
The Android Hero Of Today! ~ Amazing guide. Thank you very much!
Thank you @kenshiwara
it should be noted that in the wrong hands dd can brick your device, you are writing directly to the block device and dd does not care what you are doing.. especially if you do not add bs and/or count
I don't think adding bs would do any good, as dd automatically stops when the input of blocks runs out, in our case that is 32768, it can't go forever . Hope this was what you were pointing out, if no then please explain, I don't know much about other attribs and if the commands need any improvements then please suggest it so that I can add it.
Thank you
no it's fine, just giving general advice
when i said "you" i didn't mean you
you never know who is reading these things and what they might do, dd can be very dangerous, as you (DigiGoon) know... Man that was confusing
Oh, Okay
I have just written a clearer version of your solution, at my post here:
http://forum.xda-developers.com/honor-7/general/guide-beginners-how-to-root-update-fix-t3255452
Everything is the same, i just made it bit more organized for the absolute beginners to understand.
Thank you @DigiGoon and @sminki for writing and updating this guide.
Anytime buddy @kenshiwara