DO NOT USE THIS TUTORIAL! USE THE OTHER ONE BY ME
P.S: Do not delete this thread, I'm currently trying to help someone.
P.S: Do not delete this thread, I'm currently trying to help someone.
Last edited:
Hi Casual_H4ck3r, thanks for the tutorial.
My LG Volt2 phone is bricked. I can access the phone on recovery and download mode.
Can you please post stock rom for this phone and a tutorial to apply it?
This is weird because I tried it on two phones with no problems.oddly, this actually bricked my device.
it's stuck at the boot logo, not the bootloader logo. tried a cache and factory reset, nothing.
any help highly appreciated.
I'll try again, also do you have the boost mobile version or virgin mobile? I know there's two variants but I don't know if the difference would change much.This is weird because I tried it on two phones with no problems.
Can you give me your firmware you were on? LS751ZV(firmware number)
Also in the tutorial at the line:
Again:
ls tmp
[Enter] (Confirm the files are in there)
where it says /tmp/busybox
that's not another command, it's part of the sh script, did you run it correctly? If you repeat this process you have a chance of fixing it.
That's why I put the enter lines.
Also, was on the latest firmware, v9.I'll try again, also do you have the boost mobile version or virgin mobile? I know there's two variants but I don't know if the difference would change much.
C:\Users\doob\Desktop\LG_Root>Push_File.exe \\.\COM3 busybox /tmp/busybox
Author : blog.lvu.kr
File : busybox
Path : /tmp/busybox
UNLK : FAIL
OPEN : OPEN
TOT FileSize : 1048328
SendStart
WRTE : WRTE1048328byte sent
CLSE: CLSE
C:\Users\doob\Desktop\LG_Root>Push_File.exe \\.\COM3 lg_root.sh /tmp/lg_root.sh
Author : blog.lvu.kr
File : lg_root.sh
Path : /tmp/lg_root.sh
UNLK : FAIL
OPEN : OPEN
TOT FileSize : 9319
SendStart
WRTE : WRTE9319byte sent
CLSE: CLSE
C:\Users\doob\Desktop\LG_Root>Push_File.exe \\.\COM3 UPDATE-SuperSU-v2.46.zip /tmp/UPDATE-SuperSU-v2.46
Author : blog.lvu.kr
File : UPDATE-SuperSU-v2.46.zip
Path : /tmp/UPDATE-SuperSU-v2.46
UNLK : FAIL
OPEN : OPEN
TOT FileSize : 4017098
SendStart
WRTE : WRTE4017098byte sent
CLSE: CLSE
C:\Users\doob\Desktop\LG_Root>Send_Command.exe \\.\COM3
Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
#ls tmp
FAIL
#ls tmp
UPDATE-SuperSU-v2.46
busybox
lg_root.sh
#sh /tmp/lg_root.sh dummy 1 /tmp/UPDATE-SuperSU-v2.46.zip /tmp/busybox
ui_print *****************
ui_print SuperSU installer
ui_print *****************
ui_print - Mounting /system, /data and rootfs
ui_print - Extracting files
ui_print - Disabling OTA survival
ui_print - Removing old files
ui_print - Placing files
ui_print - Post-installation script
ui_print - Unmounting /system and /data
ui_print - Done !
#LEAVE
Push_File.exe \\.\COM# location/of/downloaded/boot.img /tmp
[Enter]
(Normal to get a error that has the word FAIL in it, followed by a bunch of numbers. 2 to be exact.)
Send_Command.exe \\.\COM#
[Enter]
dd if=/tmp/boot.img of=/dev/block/[boot.img partition block number, posting tomorrow]
[Enter]
LEAVE
[Enter]
UNBRICKED!
I'm currently stuck on LS751ZV4 from rooting and messing with the system files to free up space. I rooted with Kingroot then used SuperSU Me to switch to SuperSU. Using Link2SD for storage management. I wouldnt mind helping in any way. I have worked on Cyanogenmod on other phones once the device tree was up. Let me know what I can do.
i do believe I just need the firmware and factory recovery and It should get me back up and running. Thanks for the repply
I tried couldn't get it to work but I'm sure I'm missing something. I've read read and read then I read some more gotta take a break from it for now I think. I didn't know what the boot partition number was from the above post. So I learned how to open a tot file and extract it to find the number but not sure which one to do what with. I will post results in the future. Thanks for your help.Just uploaded this using Flashify. It's the stock recovery and V4 firmware:
Stock Recovery: https://www.dropbox.com/s/6uail1lcn9izq4g/Stock Recovery.img?dl=0
Firmware: https://www.dropbox.com/s/ckbd64x10jp7u5w/LS751V4 Firmware.img?dl=0
Let me know if it helps.
Found this for Volt 2
http://opensource.lge.com/osSch/list?types=NAME&search=ls751
Source code for updates ZV3 to ZV9 for ls751
By bricked, you mean bootloop? Does it power on, then off rapidly? Does it hang at a boot logo. If so, which one? There is a bootloader logo (before animation) and a boot logo (the animation with sound) And what did you do to cause this? I could fix it with this information. I plan dumping all the partitions soon. So like: System.img, Data.img boot.img and aboot.img (Those partitions are usually the ones that cause a brick)
Waiting to hear back.
Thanks!
I need to know exactly what you did, Did you root using this method? Are you getting any errors? Besides the LG Logo? What apps did you install before experiencing this. Careful, some play store apps are infected and will, and can kill your device. Experience.Hi, thanks to you.
The phone is on a loop. When turn on it show the LG boot screen for some seconds, then it restart and show the screen again.
I bricked the phone deleting system app's after root the phone.
I tried to install an update from zip, but the phone says that the update I try to install is oldest than the phone have.
Want to try this, but, I need the partition block number.
Can you please post it?
Thanks.
I have a LG Volt 2.
Hangs on the boot screen, (lg logo screen).
There is a surprising lack of support for this phone. (Even on XDA).
If you are using this unbrick guide, your phone should say something like:Hello I went threw these steps fine everything done what it was suppose to but now on this line I am stuck dd if=/tmp/boot.img of=/dev/block/[boot.img ((((((((partition block number, posting tomorrow))))))
What do I put in place from partition block number and so on? I don't know coding very well but I think if I can figure that out it might fix my issue
Still looking for the block number? I'm sorry, I forgot all about it. I promise I'll get it up in 1-2 days.
Still need partition block number.
/dev/block/platform/msm_sdcc.1/by-name/
/dev/block/bootdevice/by-name/
dd if=/dev/block/bootdevice/by-name/boot of=/storage/external_SD/boot.img
shell@c90nas:/ $ ls -al /dev/block/bootdevice/by-name
lrwxrwxrwx root root 1970-01-31 08:39 DDR -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-31 08:39 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-31 08:39 abootbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-31 08:39 boot -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-31 08:39 cache -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-31 08:39 carrier -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-31 08:39 drm -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-31 08:39 eksst -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-31 08:39 encrypt -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-31 08:39 factory -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-31 08:39 fota -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-31 08:39 fsc -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-31 08:39 fsg -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-31 08:39 grow -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-31 08:39 hyp -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-31 08:39 hypbak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-31 08:39 laf -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-31 08:39 metadata -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-31 08:39 misc -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-31 08:39 modem -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-31 08:39 modemst1 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-31 08:39 modemst2 -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-31 08:39 mpt -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-31 08:39 pad -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-31 08:39 persist -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-31 08:39 persistent -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-31 08:39 rct -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-31 08:39 recovery -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-31 08:39 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-31 08:39 rpmbak -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-31 08:39 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-31 08:39 sbl1bak -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-31 08:39 sec -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-31 08:39 sns -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-31 08:39 ssd -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-31 08:39 system -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-31 08:39 tz -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-31 08:39 tzbak -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-31 08:39 userdata -> /dev/block/mmcblk0p38
We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.