LG Volt 2 Forum

Root [ROOT] [UNBRICK] All-In-One Volt 2 Thread

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.
 

Related:

#1 Casual_H4ck3r, May 11, 2017 Last edited: Nov 14, 2017
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?
 
#2 StrifeSephiroth, May 13, 2017
@Casual_H4ck3r Hey man could you check out my post about my volt 2?
 
#3 FootballFan141, May 16, 2017
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!
 
#4 Casual_H4ck3r, May 18, 2017
Awesome tutorial, defiantly gonna try this tomorrow morning.
 
#5 Zenixa, May 22, 2017
oddly, this actually bricked my device.
it's stuck at the boot logo, not the bootloader logo. tried a cache and factory reset, nothing. :thinking:
any help highly appreciated.
 
#6 Zenixa, May 22, 2017 Last edited: May 22, 2017
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.
 
#7 Casual_H4ck3r, May 22, 2017 Last edited: May 22, 2017
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.
 
#8 Zenixa, May 22, 2017
Also, was on the latest firmware, v9.

did everything again. here's the console log
Code (Text):
  1. C:\Users\doob\Desktop\LG_Root>Push_File.exe \\.\COM3 busybox /tmp/busybox
  2. Author : blog.lvu.kr
  3. File : busybox
  4. Path : /tmp/busybox
  5.  
  6. UNLK : FAIL
  7. OPEN : OPEN
  8. TOT FileSize : 1048328
  9.  
  10. SendStart
  11. WRTE : WRTE1048328byte sent
  12.  
  13. CLSE: CLSE
  14. C:\Users\doob\Desktop\LG_Root>Push_File.exe \\.\COM3 lg_root.sh /tmp/lg_root.sh
  15. Author : blog.lvu.kr
  16. File : lg_root.sh
  17. Path : /tmp/lg_root.sh
  18.  
  19. UNLK : FAIL
  20. OPEN : OPEN
  21. TOT FileSize : 9319
  22.  
  23. SendStart
  24. WRTE : WRTE9319byte sent
  25.  
  26. CLSE: CLSE
  27. C:\Users\doob\Desktop\LG_Root>Push_File.exe \\.\COM3 UPDATE-SuperSU-v2.46.zip /tmp/UPDATE-SuperSU-v2.46
  28. Author : blog.lvu.kr
  29. File : UPDATE-SuperSU-v2.46.zip
  30. Path : /tmp/UPDATE-SuperSU-v2.46
  31.  
  32. UNLK : FAIL
  33. OPEN : OPEN
  34. TOT FileSize : 4017098
  35.  
  36. SendStart
  37. WRTE : WRTE4017098byte sent
  38.  
  39. CLSE: CLSE
  40. C:\Users\doob\Desktop\LG_Root>Send_Command.exe \\.\COM3
  41. Author : blog.lvu.kr
  42. SPECIAL COMMAND : ENTER, LEAVE
  43.  
  44. #ls tmp
  45. FAIL
  46. #ls tmp
  47. UPDATE-SuperSU-v2.46
  48. busybox
  49. lg_root.sh
  50. #sh /tmp/lg_root.sh dummy 1 /tmp/UPDATE-SuperSU-v2.46.zip /tmp/busybox
  51. ui_print *****************
  52. ui_print SuperSU installer
  53. ui_print *****************
  54. ui_print - Mounting /system, /data and rootfs
  55. ui_print - Extracting files
  56. ui_print - Disabling OTA survival
  57. ui_print - Removing old files
  58. ui_print - Placing files
  59. ui_print - Post-installation script
  60. ui_print - Unmounting /system and /data
  61. ui_print - Done !
  62. #LEAVE
phone restarts, still stuck on the boot screen. :(
 
#9 Zenixa, May 22, 2017 Last edited: May 22, 2017
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).
 
#10 Plus9dB996, Jun 16, 2017
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
 
#11 bobdcollins74, Jun 22, 2017
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.
 
#12 cornaljoe, Jun 24, 2017

i do believe I just need the firmware and factory recovery and It should get me back up and running. Thanks for the repply
 
#13 bobdcollins74, Jun 24, 2017
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.
 
#14 cornaljoe, Jun 24, 2017
Found this for Volt 2

http://opensource.lge.com/osSch/list?types=NAME&search=ls751

Source code for updates ZV3 to ZV9 for ls751
 
#15 Plus9dB996, Jun 27, 2017
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.
 
#16 bobdcollins74, Jun 29, 2017
I also found this: https://www.phonearena.com/phones/compare/LG-Volt-2,Motorola-Moto-G4-Play/phones/9489,10056

The Moto G4 Play has almost the exact same specs as the Volt 2 except more RAM and Memory. Theres a repo for Lineage OS for the G4 so it should be a good place to start on building it for the Volt 2.
 
#17 cornaljoe, Jul 6, 2017
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.
 
#18 StrifeSephiroth, Jul 27, 2017
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.
 
#19 Casual_H4ck3r, Jul 28, 2017
If you are using this unbrick guide, your phone should say something like:

-----------------
SECURE BOOT ERROR: boot
-----------------

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.
 
#20 Casual_H4ck3r, Jul 28, 2017
[QUOTE="Casual_H4ck3r, post: 7583925, member: 2008]
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.[/QUOTE]

Still need partition block number.
 
#21 Plus9dB996, Aug 4, 2017
For the LG Volt 2 instead of using the standard:
Code (Text):
  1. /dev/block/platform/msm_sdcc.1/by-name/
use
Code (Text):
  1. /dev/block/bootdevice/by-name/
So to pull the boot file and save to SD use:
Code (Text):
  1. dd if=/dev/block/bootdevice/by-name/boot of=/storage/external_SD/boot.img
Writing should work the same just swap the input file (if) and output file (of).

Here is the partition layout:
Code (Text):
  1.  
  2. shell@c90nas:/ $ ls -al /dev/block/bootdevice/by-name      
  3. lrwxrwxrwx root     root              1970-01-31 08:39 DDR -> /dev/block/mmcblk0p23
  4. lrwxrwxrwx root     root              1970-01-31 08:39 aboot -> /dev/block/mmcblk0p5
  5. lrwxrwxrwx root     root              1970-01-31 08:39 abootbak -> /dev/block/mmcblk0p11
  6. lrwxrwxrwx root     root              1970-01-31 08:39 boot -> /dev/block/mmcblk0p18
  7. lrwxrwxrwx root     root              1970-01-31 08:39 cache -> /dev/block/mmcblk0p37
  8. lrwxrwxrwx root     root              1970-01-31 08:39 carrier -> /dev/block/mmcblk0p35
  9. lrwxrwxrwx root     root              1970-01-31 08:39 drm -> /dev/block/mmcblk0p31
  10. lrwxrwxrwx root     root              1970-01-31 08:39 eksst -> /dev/block/mmcblk0p26
  11. lrwxrwxrwx root     root              1970-01-31 08:39 encrypt -> /dev/block/mmcblk0p25
  12. lrwxrwxrwx root     root              1970-01-31 08:39 factory -> /dev/block/mmcblk0p29
  13. lrwxrwxrwx root     root              1970-01-31 08:39 fota -> /dev/block/mmcblk0p30
  14. lrwxrwxrwx root     root              1970-01-31 08:39 fsc -> /dev/block/mmcblk0p21
  15. lrwxrwxrwx root     root              1970-01-31 08:39 fsg -> /dev/block/mmcblk0p20
  16. lrwxrwxrwx root     root              1970-01-31 08:39 grow -> /dev/block/mmcblk0p39
  17. lrwxrwxrwx root     root              1970-01-31 08:39 hyp -> /dev/block/mmcblk0p3
  18. lrwxrwxrwx root     root              1970-01-31 08:39 hypbak -> /dev/block/mmcblk0p9
  19. lrwxrwxrwx root     root              1970-01-31 08:39 laf -> /dev/block/mmcblk0p17
  20. lrwxrwxrwx root     root              1970-01-31 08:39 metadata -> /dev/block/mmcblk0p14
  21. lrwxrwxrwx root     root              1970-01-31 08:39 misc -> /dev/block/mmcblk0p12
  22. lrwxrwxrwx root     root              1970-01-31 08:39 modem -> /dev/block/mmcblk0p33
  23. lrwxrwxrwx root     root              1970-01-31 08:39 modemst1 -> /dev/block/mmcblk0p15
  24. lrwxrwxrwx root     root              1970-01-31 08:39 modemst2 -> /dev/block/mmcblk0p16
  25. lrwxrwxrwx root     root              1970-01-31 08:39 mpt -> /dev/block/mmcblk0p32
  26. lrwxrwxrwx root     root              1970-01-31 08:39 pad -> /dev/block/mmcblk0p6
  27. lrwxrwxrwx root     root              1970-01-31 08:39 persist -> /dev/block/mmcblk0p13
  28. lrwxrwxrwx root     root              1970-01-31 08:39 persistent -> /dev/block/mmcblk0p34
  29. lrwxrwxrwx root     root              1970-01-31 08:39 rct -> /dev/block/mmcblk0p27
  30. lrwxrwxrwx root     root              1970-01-31 08:39 recovery -> /dev/block/mmcblk0p19
  31. lrwxrwxrwx root     root              1970-01-31 08:39 rpm -> /dev/block/mmcblk0p4
  32. lrwxrwxrwx root     root              1970-01-31 08:39 rpmbak -> /dev/block/mmcblk0p10
  33. lrwxrwxrwx root     root              1970-01-31 08:39 sbl1 -> /dev/block/mmcblk0p1
  34. lrwxrwxrwx root     root              1970-01-31 08:39 sbl1bak -> /dev/block/mmcblk0p7
  35. lrwxrwxrwx root     root              1970-01-31 08:39 sec -> /dev/block/mmcblk0p24
  36. lrwxrwxrwx root     root              1970-01-31 08:39 sns -> /dev/block/mmcblk0p28
  37. lrwxrwxrwx root     root              1970-01-31 08:39 ssd -> /dev/block/mmcblk0p22
  38. lrwxrwxrwx root     root              1970-01-31 08:39 system -> /dev/block/mmcblk0p36
  39. lrwxrwxrwx root     root              1970-01-31 08:39 tz -> /dev/block/mmcblk0p2
  40. lrwxrwxrwx root     root              1970-01-31 08:39 tzbak -> /dev/block/mmcblk0p8
  41. lrwxrwxrwx root     root              1970-01-31 08:39 userdata -> /dev/block/mmcblk0p38
 
#22 cornaljoe, Aug 5, 2017 Last edited: Aug 5, 2017
My LG Volt 2 is stuck in a loop, it says [Authentication Error #9], can anyone help me with this?
 
#23 joeabshner, Sep 28, 2017
Is there really still no fix for the issue with it being stuck at animated booting logo?
 
#24 syz, Oct 4, 2017
Hey can you include in the OP that following these instructions will brick the device and following the (UNFINISHED) unbrick instructions won't save it? This result shows up high in google searches and you bricked my device, so maybe edit the post.
 
#25 bh861430, Oct 17, 2017