Database Users

G4 Root (Testing)

This is a test root method for the G4. It is based off of the original root method for rooting LG devices. The original method showed modified in the boot loader but it didn't have su. This a modified script to push su correctly and the su used by the H815.
Note: On the H815 If you would like root all you have to do is unlock boot loader, flash twrp for G4 then flash the supersu.zip
WARNING: USE AT YOUR OWN RISK!!
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
Click to expand...
Click to collapse
This is a new method that i discovered. Instead of rooting we are just going to flash TWRP then we can root through the recovery. I have tested this on my G3 and i can confirm that you are able to flash recoveries through download mode.
The Recovery used in this is TWRP for H815 and I am not sure of how compatible it is with other variants but if it gives you root then its worth testing.
Files:LGG4_rFLASH.zip
Drivers:HERE
Step 1: Enable USB Debugging
Step 2: Download G4 Flasher and unzip, Also Install Drivers
Step 3: In unzipped folder open a new command prompt window (Shift+Right click)
Step 4: Run this command
adb.exe push recovery.img /data/local/tmp/
Click to expand...
Click to collapse
Step 5: Enter Download Mode (Hold Volume Up While plugging in Usb Cable)
Step 6: Check Device Manager> Serial Port (Windows) and make sure your Phones COM is set to 41, if not then change it. After changing it you may have to unplug usb, pull battery and then reboot into download mode.
Step 7: Open a new Command prompt window just like before. in the folder you extracted.
Step 8: Run this Command
Send_Command.exe \\.\COM41
Click to expand...
Click to collapse
.
Step 9: Run this to Backup your current recovery
dd if=/dev/block/platform/f9824900.sdhci/by-name/recovery of=/data/local/tmp/recoverybak.img
Click to expand...
Click to collapse
Step 10: It will now show a # then run this
dd if=/dev/zero of=/dev/block/platform/f9824900.sdhci/by-name/recovery
Click to expand...
Click to collapse
Step 11: Then run this
dd if=/data/local/tmp/recovery.img of=/dev/block/platform/f9824900.sdhci/by-name/recovery
Click to expand...
Click to collapse
Step 12: Pull battery and try to boot into recovery
Step 13: Flash Supersu.zip
Note:: to restore original Recovery all you have to do is pull it
adb pull /data/local/tmp/recoverybak.img \
Rename it recovery.img (you might have to delete or rename the one that was extracted from the zip earlier because the can only be one recovery.img in a folder )
then rinse and repeat all the steps

I've got a Verizon version coming tomorrow. Can't wait to give this a try. Thanks.
Edit - Just tried to download the root zip, and I got a message that it's infected with a virus.

cant download G4_Rootbeta1.zip
her it is

hytin said:
cant download G4_Rootbeta1.zip
Click to expand...
Click to collapse
This is the error we get when attempting to download it:
Code:
Sorry, this file is infected with a virus
Only the owner is allowed to download infected files.
EDIT: See my post below for a copy of the ZIP

i think i found a way will upload it later

Does anyone tried this method on the T-Mobile G4 H811?

I was able to use a web-based ZIP extractor to extract then compress it. I have done no scanning for viruses, I simply extracted and repackaged the files.
G4_Rootbeta1
ZIP - https://www.dropbox.com/s/wmbz005aqs52r9j/G4_Rootbeta1.zip?dl=0
7z - https://www.dropbox.com/s/tnmnbak62zdrgu6/G4_Rootbeta1.7z?dl=0

hytin said:
cant download G4_Rootbeta1.zip
Click to expand...
Click to collapse
New link... I uploaded to drop box. Google drive acts funny when it come to certain files.

geoff5093 said:
This is the error we get when attempting to download it:
Code:
Sorry, this file is infected with a virus
Only the owner is allowed to download infected files.
EDIT: See my post below for a copy of the ZIP
Click to expand...
Click to collapse
New link available

do we still need to enable oem unlock?
Sent from my LG-H815 using Tapatalk 2

deejay6901 said:
do we still need to enable oem unlock?
Sent from my LG-H815 using Tapatalk 2
Click to expand...
Click to collapse
I think I am unlock is only for unlocking the boot loader not rooting

So I tried this on the H811 (T-Mobile) version.
Everything worked just as described UNTIL the part where I needed to run the root script.
After I paste the SH command, it thinks for a moment, and returns me to the # line...
Not sure how to continue from here, but will be happy to be a guinea pig if someone can tell me what to try.
{
"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"
}

madhouze said:
So I tried this on the H811 (T-Mobile) version.
Everything worked just as described UNTIL the part where I needed to run the root script.
After I paste the SH command, it thinks for a moment, and returns me to the # line...
Not sure how to continue from here, but will be happy to be a guinea pig if someone can tell me what to try.
Click to expand...
Click to collapse
Same here on H815 ?!
My Bootloader ist Locked. Is that the reason ??? Do i have to unlock it ?

it´s for the G3 on 5.02 not lollipop 5.1

hytin said:
it´s for the G3 on 5.02 not lollipop 5.1
Click to expand...
Click to collapse
This is modified for g4

Masta_Gee81 said:
Same here on H815 ?!
My Bootloader ist Locked. Is that the reason ??? Do i have to unlock it ?
Click to expand...
Click to collapse
Try doing the command without dummy1

Hi macdaddie87
Thanks for your job! :good:

Looking forward to people with Verizon giving this a shot first!

macdaddie87 said:
Try doing the command without dummy1
Click to expand...
Click to collapse
Same result . Nothing happens ?
this is my input : sh /data/local/tmp/root_g4.sh/data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
it stays on # nothing more?!

looks like device is not attaching when connected to download mode even if adb.exe devices is executed

NXT-L29 Partitions

External storage path
1. TWRP : /external_sd
2. Boot to system : /storage/sdcard1
{
"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"
}
dd command for backup partitions except /system and /userdata
dd if=/dev/block/platform/hi_mci.0/by-name/vrl of=/external_sd/backup/vrl.img
dd if=/dev/block/platform/hi_mci.0/by-name/vrl_backup of=/external_sd/backup/vrl_backup.img
dd if=/dev/block/platform/hi_mci.0/by-name/fw_lpm3 of=/external_sd/backup/fw_lpm3.img
dd if=/dev/block/platform/hi_mci.0/by-name/frp of=/external_sd/backup/frp.img
dd if=/dev/block/platform/hi_mci.0/by-name/fastboot of=/external_sd/backup/fastboot.img
dd if=/dev/block/platform/hi_mci.0/by-name/modemnvm_factory of=/external_sd/backup/modemnvm_factory.img
dd if=/dev/block/platform/hi_mci.0/by-name/nvme of=/external_sd/backup/nvme.img
dd if=/dev/block/platform/hi_mci.0/by-name/oeminfo of=/external_sd/backup/oeminfo.img
dd if=/dev/block/platform/hi_mci.0/by-name/splash of=/external_sd/backup/splash.img
dd if=/dev/block/platform/hi_mci.0/by-name/modemnvm_backup of=/external_sd/backup/modemnvm_backup.img
dd if=/dev/block/platform/hi_mci.0/by-name/modemnvm_img of=/external_sd/backup/modemnvm_img.img
dd if=/dev/block/platform/hi_mci.0/by-name/modemnvm_system of=/external_sd/backup/modemnvm_system.img
dd if=/dev/block/platform/hi_mci.0/by-name/secure_storage of=/external_sd/backup/secure_storage.img
dd if=/dev/block/platform/hi_mci.0/by-name/3rdmodemnvm of=/external_sd/backup/3rdmodemnvm.img
dd if=/dev/block/platform/hi_mci.0/by-name/3rdmodemnvmbkp of=/external_sd/backup/3rdmodemnvmbkp.img
dd if=/dev/block/platform/hi_mci.0/by-name/persist of=/external_sd/backup/persist.img
dd if=/dev/block/platform/hi_mci.0/by-name/reserved1 of=/external_sd/backup/reserved1.img
dd if=/dev/block/platform/hi_mci.0/by-name/modem_om of=/external_sd/backup/modem_om.img
dd if=/dev/block/platform/hi_mci.0/by-name/splash2 of=/external_sd/backup/splash2.img
dd if=/dev/block/platform/hi_mci.0/by-name/misc of=/external_sd/backup/misc.img
dd if=/dev/block/platform/hi_mci.0/by-name/modemnvm_update of=/external_sd/backup/modemnvm_update.img
dd if=/dev/block/platform/hi_mci.0/by-name/recovery2 of=/external_sd/backup/recovery2.img
dd if=/dev/block/platform/hi_mci.0/by-name/reserved2 of=/external_sd/backup/reserved2.img
dd if=/dev/block/platform/hi_mci.0/by-name/teeos of=/external_sd/backup/teeos.img
dd if=/dev/block/platform/hi_mci.0/by-name/trustfirmware of=/external_sd/backup/trustfirmware.img
dd if=/dev/block/platform/hi_mci.0/by-name/sensorhub of=/external_sd/backup/sensorhub.img
dd if=/dev/block/platform/hi_mci.0/by-name/fw_hifi of=/external_sd/backup/fw_hifi.img
dd if=/dev/block/platform/hi_mci.0/by-name/boot of=/external_sd/backup/boot.img
dd if=/dev/block/platform/hi_mci.0/by-name/recovery of=/external_sd/backup/recovery.img
dd if=/dev/block/platform/hi_mci.0/by-name/dts of=/external_sd/backup/dts.img
dd if=/dev/block/platform/hi_mci.0/by-name/modem of=/external_sd/backup/modem.img
dd if=/dev/block/platform/hi_mci.0/by-name/modem_dsp of=/external_sd/backup/modem_dsp.img
dd if=/dev/block/platform/hi_mci.0/by-name/modem_dtb of=/external_sd/backup/modem_dtb.img
dd if=/dev/block/platform/hi_mci.0/by-name/dfx of=/external_sd/backup/dfx.img
dd if=/dev/block/platform/hi_mci.0/by-name/3rdmodem of=/external_sd/backup/3rdmodem.img
dd if=/dev/block/platform/hi_mci.0/by-name/cache of=/external_sd/backup/cache.img
dd if=/dev/block/platform/hi_mci.0/by-name/hisitest0 of=/external_sd/backup/hisitest0.img
dd if=/dev/block/platform/hi_mci.0/by-name/hisitest1 of=/external_sd/backup/hisitest1.img
dd if=/dev/block/platform/hi_mci.0/by-name/cust of=/external_sd/backup/cust.img
dd if=/dev/block/platform/hi_mci.0/by-name/hisitest2 of=/external_sd/backup/hisitest2.img
Click to expand...
Click to collapse

Cheers for that. I'm on the al10 and was thinking of force flashing all partitions from the international model just to see if it worked
Sent from my NEXT using Tapatalk

sure works

How would one force flash all partitions? I have the L29 OTA's and I am trying to get my L10 debranded with fastboot as I want to keep stock recovery/unrooted/etc.

u mean u have the AL10? theres YET no option to completely debrand it AND receive OTA updates for the "other" model ure trying to flash it to (in this case, L29)
supposedly, ud have to flash the oeminfo and make changes to build.prop and other system files, as well as flashing all partitions of a proper stock L29 firmware. people are still trying to figure things out.
in the meantime, its no biggie to crossflash roms to at least get the "other" experience manually

jbmc83 said:
u mean u have the AL10? theres YET no option to completely debrand it AND receive OTA updates for the "other" model ure trying to flash it to (in this case, L29)
supposedly, ud have to flash the oeminfo and make changes to build.prop and other system files, as well as flashing all partitions of a proper stock L29 firmware. people are still trying to figure things out.
in the meantime, its no biggie to crossflash roms to at least get the "other" experience manually
Click to expand...
Click to collapse
Yeah, thats what I have been doing. But there are so many .img files in the OTA's that I am not able to flash with fastboot, so I feel like I am missing stuff.

well the number of partitions shouldnt be a problem, it would just take a while to type all commands in fastboot

jbmc83 said:
well the number of partitions shouldnt be a problem, it would just take a while to type all commands in fastboot
Click to expand...
Click to collapse
I tried flashing them all once. Most of them failed with command not supported. The only ones that work are boot cust cache system modem recovery and a couple others.

hm and the erecovery option with update.app in dload folder probably shows u incompatible system , hm?

jbmc83 said:
hm and the erecovery option with update.app in dload folder probably shows u incompatible system , hm?
Click to expand...
Click to collapse
Yeah.

Hi
I try to put my mate 8 AL10 in full L29.
I have extracted all data from update and i have flashed cache, cust, system and oeminfo, all work perfectly.
The phone is recognized in L29 but when i plug it in usb mode developer, it's write Huawei NXT-AL10.
What i need, to pass it in full L29 version ?
Flash crc ? boot ? recovery2 ?trustfirmware ?
thanks for your help

jarod27 said:
Hi
I try to put my mate 8 AL10 in full L29.
I have extracted all data from update and i have flashed cache, cust, system and oeminfo, all work perfectly.
The phone is recognized in L29 but when i plug it in usb mode developer, it's write Huawei NXT-AL10.
What i need, to pass it in full L29 version ?
Flash crc ? boot ? recovery2 ?trustfirmware ?
thanks for your help
Click to expand...
Click to collapse
it could be an idea to get all partition from L29 with "dd if=/dev/block/partitonX of=partitionX.img" and flash it on L10?
can you chek yout custom.bin? is in /data partition. open it with root explorer as text file

no custom.bin in data folder

jarod27 said:
no custom.bin in data folder
Click to expand...
Click to collapse
ok.
do you think that clone all partition from l29 could be a good idea?

maybe
you can do this ?

no, I have not yet bought the mate 8. I 'm studying the situation because if I take it , I take al10 for the 64gb storage. But i prefer the international software because it has a reduced sar value.
the hardware is the same.
I have not bought it yet because I have a doubt about the size: I would not like it's too big to carry in pocket and to use it with only one hand
i thinking

ok

Did someone already tried to crossflash all the partitions?
How would you do that?
Fastboot ist not accepting all partitions.
Is it possible with dd comand from adb or twrp?
Btw. you should better not modify or crossflash NVME as it contains your SN, IMEI, MAC, ...

Backing up partitions
somboons said:
External storage path
1. TWRP : /external_sd
2. Boot to system : /storage/sdcard1
dd command for backup partitions except /system and /userdata
Click to expand...
Click to collapse
Would you mind to explain a noob (me) with a little more detail on how to locate this partitions from my computer and back some of them up?
I want to back up OEMinfo, CUST & NVME.
thanks a lot!

hi , like many other i haved a bricked mate 8 and after using dc phoenix to repair it . the phone work but no signial or network and i think because in start of flashing dc-phoenix erase this three partition modemnvm_backup/modemnvm_factory/modemnvm_system and don't reflash them only erase
so pls can you upload this three partition image if it's possible
thank you any way

G2 No Network ISSIUE

Hello everybody.
I am having a big issiue with my G2 right now so i thought that i can fix it asking here.
My problem is that recently i was loosing my mobile network connection and for this reason i decided to restore the stock firmware on my device ( I was using CloudyG2 ).
After i restored the stock firmware the mobile network is working great but after a simple restart or power off and boot again the network itself dissapears. After a couple of tryes i noticed that the fields called Baseband and IMEI are the right ones but after the reboot they both become Unknown. I also noticed that the firmware once installed the stock one is V30d-EUR-xx but after the reboot it is just V30d.
I wanted to ask what can i do to fix the problem? After the reboot i am seeing the ANDROID IS UPDATING screen but for less than 8 seconds. I think this is why the network dissapears and i loose connection and the firmware name changes. Can it be that android updates after it initializes all the applications and this shadow update make my phone unusable?
I wanted also to say that i tryed to use BlissPop or Cyanogen ROMS and the network work perfectly with those, it is not about 3G or LTE band being not compatible. But still i would like to know why i get this problems. I also want to say that i, one time, flashed the phone using the TOT flash method but that flash mode is only for US AT&T phones, so for this reason maybe i loose the network. I returned to stock using the KDZ firmware.
I am ataching the screenshot to explain my problem better, just in case, sorry but they are in italian.
{
"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"
}
Now i really don't know if it is better to send it in assistance or it is just a software problem that i can fix myself. What do you think? The phone itself worked great for almost two years now...
Thank you, if you have any questions please ask me

Maybe the only thing i can do is restore every single partition with a working D802 32GB european phone.
Can someone please run this scripts in a terminal ( phone needs root access ) and share them with mega? Thank you
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/backup/aboot.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/backup/boot.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/cache of=/sdcard/backup/cache.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/cust of=/sdcard/backup/cust.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/dbi of=/sdcard/backup/dbi.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/dbibak of=/sdcard/backup/dbibak.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/DDR of=/sdcard/backup/DDR.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/drm of=/sdcard/backup/drm.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/encrypt of=/sdcard/backup/encrypt.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/backup/fota.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/fsc of=/sdcard/backup/fsc.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/fsg of=/sdcard/backup/fsg.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/grow of=/sdcard/backup/grow.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/sdcard/backup/laf.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/misc of=/sdcard/backup/misc.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/sdcard/backup/modem.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst1 of=/sdcard/efs/modemst1.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst2 of=/sdcard/efs/modemst2.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/mpt of=/sdcard/backup/mpt.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/pad of=/sdcard/backup/pad.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/pad of=/sdcard/backup/pad1.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/pad of=/sdcard/backup/pad2.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/persist of=/sdcard/backup/persist.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/rct of=/sdcard/backup/rct.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/sdcard/backup/recovery.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/rpm of=/sdcard/backup/rpm.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/rpmbak of=/sdcard/backup/rpmbak.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/sbl1 of=/sdcard/backup/sbl1.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/sns of=/sdcard/backup/sns.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/spare of=/sdcard/backup/spare.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/ssd of=/sdcard/backup/ssd.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/sdcard/backup/system.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/tombstones of=/sdcard/backup/tombstones.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/tz of=/sdcard/backup/tz.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/tzbak of=/sdcard/backup/tzbak.img

im using lg g2 d802 .i have wifi connection problem.
when i switch on the wifi ,it stays for few second and off again
someone can help me to solve it,[email protected]

McSmoove said:
Hello everybody.
I am having a big issiue with my G2 right now so i thought that i can fix it asking here.
My problem is that recently i was loosing my mobile network connection and for this reason i decided to restore the stock firmware on my device ( I was using CloudyG2 ).
After i restored the stock firmware the mobile network is working great but after a simple restart or power off and boot again the network itself dissapears. After a couple of tryes i noticed that the fields called Baseband and IMEI are the right ones but after the reboot they both become Unknown. I also noticed that the firmware once installed the stock one is V30d-EUR-xx but after the reboot it is just V30d.
I wanted to ask what can i do to fix the problem? After the reboot i am seeing the ANDROID IS UPDATING screen but for less than 8 seconds. I think this is why the network dissapears and i loose connection and the firmware name changes. Can it be that android updates after it initializes all the applications and this shadow update make my phone unusable?
I wanted also to say that i tryed to use BlissPop or Cyanogen ROMS and the network work perfectly with those, it is not about 3G or LTE band being not compatible. But still i would like to know why i get this problems. I also want to say that i, one time, flashed the phone using the TOT flash method but that flash mode is only for US AT&T phones, so for this reason maybe i loose the network. I returned to stock using the KDZ firmware.
I am ataching the screenshot to explain my problem better, just in case, sorry but they are in italian.
Now i really don't know if it is better to send it in assistance or it is just a software problem that i can fix myself. What do you think? The phone itself worked great for almost two years now...
Thank you, if you have any questions please ask me
Click to expand...
Click to collapse
will this help read and see if it does.
http://forum.xda-developers.com/lg-g2/general/imei-baseband-unknown-refurbished-t3076993

[ROM][H818][5.1] Satan OS - Best custom rom with UX 5.0 framework

Note: This is not my work its from 4pda. Here is the link: http://4pda.ru/forum/index.php?showtopic=674632&st=4260#entry54442872
Disclaimer: I or xda will not be responsible for anything happens to your device.
Features:
firts lollipop rom with UX 5.0 framework so its like using nougat rom
rom runs on top of v10e software update
Its pre rooted
xposed and viper4android can be installed. Not pre installed
Dual Window for all apps
60fps FHD video recording
Slow Motion video recording
Mini view
and more
Download link:
https://drive.google.com/file/d/0B_qeVuuE99zhTlZ6clRmQmNTOFE/view?usp=sharing
Installation:
Extract the rar file
Move the downloading "system.img" file to the root of your phone's internal storage
Once this has been done, POWER OFF your phone normally and disconnect from PC. After LED stops blinking (OFF properly), Hold the UP VOLUME key and re-insert the USB cable from your PC to your phone. If done correctly, you should see DOWNLOAD MODE in small font in middle of the screen. it will then display another screen with text: FIRMWARE UPDATE (a USB logo) a warning to not unplug and a status bar at 0%.
On a windows PC, Start a command prompt (Start > Run > cmd) and navigate to the unzipped contents folder of LG Root (which is downloaded for LG g4 Root process). (On my PC, the command prompt line after navigation to my unzipped folder looks like C:\Users\star\Desktop\LG_Root\ ).
Let's verify the COM port your phone is connected to. double click the file "ports.bat" in LG_Root folder. Look for the COM number that corresponds to "DIAG1". **WRITE DOWN / REMEMBER THE COMM PORT NUMBER!** Let's assume it's COM3. Click any key/exit this window now...
copy/paste or type this command MAKING SURE THE RIGHT COMM NUMBER IS ENTERED: Send_Command.exe \\.\COM3
You should see Author: blog.lvu.kr and SPECIAL COMMAND : ENTER, LEAVE on 2 lines followed by a hashtag (#). If you are up to this point, type id and press ENTER
You should get back some text starting with "uid=(0)root gid=(0)root".
If it worked for you, from here run the command below (copy/paste next to the # and press ENTER)
dd if=/data/media/0/system.img bs=8192 seek=55296 count=529920 of=/dev/block/mmcblk0
If you've done this correctly, as soon as you've pressed ENTER, you'll see a blinking cursor, probably for a few minutes. Basically the pre-rooted system image you are FLASHING to your phone is being written, so it may take a few minutes. When complete, you should see #. If you see this, it's DONE! Type LEAVE (in CAPS)and press ENTER. Your phone should then restart... Here's mine, it worked like charm!
Overview of the ROM: https://youtu.be/0GZOYGbjFl4
Screenshot on 2nd post

Screenshot
{
"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"
}

h815?why only 818 dude

[email protected] said:
h815?why only 818 dude
Click to expand...
Click to collapse
only for the dual sim model. h815 got bootloader unlock and got lot of custom rom...

looks nice.
currently im (H818p)on Nougat stock.
if i want to try this rom, how i do it?

dark.blue said:
looks nice.
currently im (H818p)on Nougat stock.
if i want to try this rom, how i do it?
Click to expand...
Click to collapse
you need to flash the marshmallow rom in the nougat thread to revert back to marshmallow after that flash lollipop kdz and follow the above instruction

I am on stock MM V20h can I upload this rom? Do I need to downgrade to LP? Can I go back to stock MM after trying this rom?
thanks for the answers

LPK_CZ said:
I am on stock MM V20h can I upload this rom? Do I need to downgrade to LP? Can I go back to stock MM after trying this rom?
thanks for the answers
Click to expand...
Click to collapse
you need to downgrade to LP to try this rom. after trying you can revert back to marshmallow

safwan ck said:
Note: This is not my work its from 4pda. Here is the link: http://4pda.ru/forum/index.php?showtopic=674632&st=4260#entry54442872
Click to expand...
Click to collapse
Excellent rom for H818,great battery life normal usage about 14hrs

Just wondering do I need to upgrade my phone to v10e first?before installing this ROM?

[TOOL][SPLASH][QCOM]Change oppo/realme/oneplus boot splash image

This tool I called it opsplash.​This tool does not support mtk device, qualcomm only!​cause it can unpack/repack oppo splash format image.
{
"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"
}
pic from my cygwin terminal​If you like my tool, you can buy me a cofface.​Donate : https://paypal.me/affggh​
First get your splash image​​
How can I get my splash image.​
adb shell
# give root access
su
dd if=/dev/block/by-name/splash of=/sdcard/splash.img
# or
dd if=/dev/block/by-name/splash_a of=/sdcard/splash_a.img
exit
adb pull /sdcard/splash.img splash.img
# or
adb pull /sdcard/splash_a.img splash_a.img
Click to expand...
Click to collapse
Now we have splash image, unpack pics from splash image.​
# powershell​
.\opsplash.exe unpack -i splash.img -o pic
Click to expand...
Click to collapse
# linux bash​
./opsplash unpack -i splash.img -o pic
Click to expand...
Click to collapse
They are basicly same...
Notice : The pic which you replace must have same format and same width and height pixel​
After replace your bitmap image, repack and flash it back​
./opsplash repack -i splash.img -o new-splash.img
Click to expand...
Click to collapse
Here we success generated a new-splash.img, flash it back to your phone and test wether it work.
Source code : https://github.com/affggh/opsplash

reserved

affggh said:
This tool I called it opsplash.​This tool does not support mtk device, qualcomm only!​cause it can unpack/repack oppo splash format image.
View attachment 5721337
pic from my cygwin terminal​If you like my tool, you can buy me a cofface.​Donate : https://paypal.me/affggh​
​First get your splash image​
How can I get my splash image.​
Now we have splash image, unpack pics from splash image.​
# powershell​
# linux bash​
They are basicly same...
Notice : The pic which you replace must have same format and same width and height pixel​View attachment 5721339
View attachment 5721341
After replace your bitmap image, repack and flash it back​
View attachment 5721343
Here we success generated a new-splash.img, flash it back to your phone and test wether it work.
View attachment 5721345
Source code : https://github.com/affggh/opsplash
Click to expand...
Click to collapse
Will work on realme 5 sir?

Adamant12 said:
Will work on realme 5 sir?
Click to expand...
Click to collapse
You can just try it, I've test it on oneplus 8t ,realme gt2, realme gt neo2,oppo r11s

Some question about this tool to modify bootlogo on my OnePlus 8T with Android 13:
when launching command dd if=/dev/block/by-name/splash of=/sdcard/splash.img or dd if=/dev/block/by-name/splash_a of=/sdcard/splash_a.img I have as a result No such file or directory on my OnePlus 8T
which tool to download and use on Windows 64 to unpack and repack?
can you share adb commands to push the modded image file?
Thank you
EDIT: dd if=/dev/block/by-name/logo_a of=/sdcard/logo_a.img did the job
I need the command to flash modded logo_a, should be dd if=/sdcard/logo_a.img of=/dev/block/by-name/logo_a

Tool is unable to read splash for oneplus 8 (instantnoodle). which is logo partition
(i opened an issue on github)

I managed to change boot.bmp on a oneplus9 when it repacks the splash_a image the size difference was worrying.
But I chanced it and flashed it back
Code:
DD if=/sdcard/new-image.img of=/dev/block/by-name/splash_a
And rebooted, stupidly I was booting from slot b so I just repeated the step above but used b
Code:
DD if=/sdcard/new-image.img of=/dev/block/by-name/splash_b
Works fine, unsure if it would affect updating or reflashing so I will probably swap the old one back in before doing anything else.