• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Root

redjama said:
I havent tested this myself but heres a link for Root on the LG Volt

Root for LG Volt
Click to expand...

This didn't work. The phone has a locked bootloader. Doesn't seem we'll get anywhere until someone figures out how to get past that...

One of the comments I saw on xda-developers said they rooted their device by formatting the microSD card as ext4 filesystem instead of ext2. That did NOT work for me.

Another posting talked about putting the handset in download mode...I am able to confirm I could get my handset into download mode by powering the phone off, and holding the vol up button down while plugging the USB cable into the computer. My mac did not recognize the device, so I didn't get any further...

Anyone else get theirs rooted?
 
I have an LG F3, and at least on it they say you have to have a Windows PC to be able to communicate with the phone for tweaking etc. So maybe you are not having any luck because you are on a Mac.
 
I got as far as trying to load the zip file. There is a couple of things the article misses.

1. you have to use adb reboot recovery. The method they have listed doesn't make the phone "stick" in recovery.

2. Make sure you have the partition set as a primary partition. There is a way to do it with the program listed in the article, but not sure how. On linux (which is what I use), use fdisk to create the empty partition (make sure to set it as primary) then format it.

Those being said, the zip file is not signed correctly and the recovery won't load it. It is progress, but not fully there yet
 
Murf1 said:
I have an LG F3, and at least on it they say you have to have a Windows PC to be able to communicate with the phone for tweaking etc. So maybe you are not having any luck because you are on a Mac.
Click to expand...

Here's what I've figured out...

The Mac is able to connect to phone with adb. It is able to "adb reboot recovery" from the Mac. When I select "load update with ADB", the phone changes the USB mode.

I had the same things happen with Linux. The Linux kernel USB messages confirm that something definitely changes when selecting the "load update with ADB" on the phone...

Code: 
---------- Linux kernel messages when connecting LG Volt ----------
[  254.862371] usb 3-6.4: new high-speed USB device number 7 using xhci_hcd
[  254.874117] usb 3-6.4: New USB device found, idVendor=1004, idProduct=631f
[  254.874120] usb 3-6.4: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[  254.874122] usb 3-6.4: Product: LGE Android Phone
[  254.874124] usb 3-6.4: Manufacturer: LG Electronics Inc.
[  254.874125] usb 3-6.4: SerialNumber: 00d68_______70e2 <redacted>
[  254.874239] usb 3-6.4: ep 0x81 - rounding interval to 32768 microframes, ep
desc says 0 microframes
[  254.874244] usb 3-6.4: ep 0x1 - rounding interval to 32768 microframes, ep
desc says 0 microframes
--------------------------------------------------------------------
# ./adb devices
List of devices attached 
00d6________70e2    device (serial # redacted)

# ./adb reboot recovery
#
----The phone reboots to recovery.  When I select "apply update with ADB", the phone says
----"Now send the package you want to apply to the device with 
----'adb sideload <filename>'..."

# ./adb devices
List of devices attached 

# ./adb sideload kk_root.zip
error: device not found

#

---The Linux kernel messages appear after selecting "apply update with ADB" option:
[  553.593965] usb 3-6.4: USB disconnect, device number 7
[  724.272424] usb 3-6.4: new high-speed USB device number 8 using xhci_hcd
[  724.283370] usb 3-6.4: no configurations
[  724.283372] usb 3-6.4: can't read configurations, error -22
[  724.345212] usb 3-6.4: new high-speed USB device number 9 using xhci_hcd
[  724.356158] usb 3-6.4: no configurations
[  724.356159] usb 3-6.4: can't read configurations, error -22
[  724.418000] usb 3-6.4: new high-speed USB device number 10 using xhci_hcd
[  724.428933] usb 3-6.4: no configurations
[  724.428935] usb 3-6.4: can't read configurations, error -22
[  724.490790] usb 3-6.4: new high-speed USB device number 11 using xhci_hcd
[  724.501722] usb 3-6.4: no configurations
[  724.501724] usb 3-6.4: can't read configurations, error -22
The thread I read about putting the phone in download mode...(power down the handset, and hold the volume UP button down while plugging into the computer USB)...I was curious what happens with that...I didn't save the output...basically everything was the SAME, only the idProduct field CHANGES...seems like it changed from 631f to 6330. In any event, with the phone in this download mode, adb is not able to connect to the phone...

I have no windows systems, so I hope a "generic" root method can be found...
 
I just checked out TowelRoot myself. It worked, according to root checker. I'm just having problems with any superuser apps downloading their binaries. Most of our root discussion is over in the LG F90 forum, since it's essentially the same device (we just have more ram) and it was available before this forum was.

EDIT: It seems that even with the binary issues, SuperSu allows me to grant root permissions just fine. A few comments on the Towelroot thread on XDA point out that we may not need to download a super user app at all.
 
I can confirm the SuperSU from the xda-developers thread worked. I downloaded the flashable zip file, extracted the Superuser.apk file from that & used my file browser to run by hand. It worked fine on my Boost Volt...

UPDATE-SuperSU-v1.99r4.zip was the file I used...
 
You must log in or register to reply here.
Back
Top Bottom