yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] LemurDroid:
So i spent the last day learning what drivers to install:

APX nvidia usb drivers, fastboot USB devices, LG device drivers

the software I was going to need:

The SDK, fastboot, adb, Linux (which i ended up bypassing)

and all the random commands. I got it all from this thread and I must dsy thanks. I'm rooted, running the newest 1.5GHz OC kernel (which so far seems to work great), and have made usb sticks automount.

This was even more of a challenge then rooting my G2 and G1 were (no walk in the park either.) Thanks everyone!

Now, with the advent of this 3.1 push, will rooted devices get the OTA? If so, is it going to break everything I just did?

Also, just wanted to say there is a REMARKABLE improvment in performance and boot time with the new kernel. Much snappier and smoother animation across the board and half the time to boot the device.
[Upgrading, Modifying and Unlocking] 3too:
L-06C Optimus Pad

Version UP 3.1 so can't root nvflash

Is it good when doing very?
[Upgrading, Modifying and Unlocking] LemurDroid:
Just wanted to note that even with the new Kernel from 8/7 the device still won't come back from sleep if wifi is on even though the notes say this was fixed. (is there a place you'd rather me post this information?)
[Upgrading, Modifying and Unlocking] aureole999:
when i try to root 3.1 (docomo version) , i got an error message:

Nvflash started

rcm version 0X4

Command send failed (usb write failed)

I searched it , it seems lots of pad have this issue.

But i still don't know how to solve it.

kernel version: 2.6.36.3+ OptimusPad@withGoogle #1

build version: HMJ37
[Upgrading, Modifying and Unlocking] xxliftsupxx:
device iss locked! no way!
[Upgrading, Modifying and Unlocking] deez1234:
We will be working on a rooted system.img as soon as some of us get 3.1! If you are rooted you will be able to receive the update. You will however be unrooted after the update but don't worry. We will have easier methods coming! Join us on IRC.
[Upgrading, Modifying and Unlocking] keawai:
This is great, I hope something comes of this for Windows soon. I did however notice their update to 3.1 finally! Thanks for your hard work!
[Upgrading, Modifying and Unlocking] deez1234:
It is available for Windows and Linux...visit our project page at http://code.google.com/p/lg-v909/ and look at our Wiki page. Enjoy.
[Upgrading, Modifying and Unlocking] dasunsrule32:
We now have the 3.1 update flashable and working. We just got root.

Join us:

http://code.google.com/p/lg-v909

irc:

irc.freenode.net #g-slate
[Upgrading, Modifying and Unlocking] tuananhnt:
Help: My gslate bricked !

hi everyone i have a major issue with my rooted LG Optimus Pad L-06C. If anyone can help it would be greatly appreciated. i downloaded CW from the market and when it askes you for compatibility i accedently chose the option (lg optimus 3d) thinking it was for my gslate and now after i turned off the gslate and go to turn it back on its stuck on LG blackscreen and says

[HasValidKernelImage] Magic value mismatch:

[DetectOperatingSystems]kernel image is invalid !!!

Starting Fastboot USB download protocol

After, I did with Ubuntu to wipe paritions with nvflash (N = partition #, use table above to prefix):

Code:

./nvflash --bl bootloader.bin --getpartitiontable ptable.txt

./nvflash -r --format_partition N: (I'd this from 1 to 8(eight) :-( )

Code:

0 /tmp ramdisk (null) (null) 0

1 /system ext4 /dev/block/mmcblk0p1 (null) 0

2 /cache ext4 /dev/block/mmcblk0p2 (null) 0

3 /misc emmc /dev/block/mmcblk0p3 (null) 0

4 /data ext4 /dev/block/mmcblk0p4 (null) 0

5 /recovery emmc /dev/block/mmcblk0p5 (null) 0

6 /boot emmc /dev/block/mmcblk0p6 (null) 0

7 /radio emmc /dev/block/mmcblk0p9 (null) 0

8 /oemboot emmc /dev/block/mmcblk0p10 (null) 0

= My pad can't turn on, just connect to computer with APX mode

Ive looked all over the internet and cant find anything to help me out so please can someone help me.

Maybe a way to nvflash all partitions back. Who one else having Stock_Restore (Docomo L-06C) which sent me plz !
[Upgrading, Modifying and Unlocking] dasunsrule32:
No, it's not locked He probably wasn't running as root when he ran that or his udev rules are screwed up. ;)
[Upgrading, Modifying and Unlocking] tuananhnt:
Who one else having Stock_Restore (Docomo L-06C / Honeycomb 3.0) which sent me plz !

I wanna partition 3 to 7 backup

nvflash --bl bootloader.bin --getpartitiontable ptable.txt

nvflash -r --read 3 part3-orig.img

...

nvflash -r --read 7 part7-orig.img

0 /tmp ramdisk (null) (null) 0

1 /system ext4 /dev/block/mmcblk0p1 (null) 0

2 /cache ext4 /dev/block/mmcblk0p2 (null) 0

3 /misc emmc /dev/block/mmcblk0p3 (null) 0

4 /data ext4 /dev/block/mmcblk0p4 (null) 0

5 /recovery emmc /dev/block/mmcblk0p5 (null) 0

6 /boot emmc /dev/block/mmcblk0p6 (null) 0

7 /radio emmc /dev/block/mmcblk0p9 (null) 0

8 /oemboot emmc /dev/block/mmcblk0p10 (null) 0
[Upgrading, Modifying and Unlocking] datlink:
unroot LG-Slate

How to unroot
[Upgrading, Modifying and Unlocking] Gigamaster89:
Got my OTA today, NYC.
[Upgrading, Modifying and Unlocking] buckbullstallion:
OTA TODAY 8/15/11 4am ish

received OTA 3.1 today, I installed it as I was eagerly awaiting this update. I am confident the scene will pull of a root so I can have full control over my device. Keep up the good work people. THank you for the first root as well. West Coast Portland Service area.
[Upgrading, Modifying and Unlocking] LemurDroid:
If I am trying to push the 3.1 update manually, in addition to resetting it to stock, do I have to revert to the old kernel?

I pushed (and enjoyed) the most recent one.
[Upgrading, Modifying and Unlocking] knut150:
Got the OTA today, LA
[Upgrading, Modifying and Unlocking] LemurDroid:
Does the root on the code.google page work on 3.1? Is the rooted system image on there the right one for the 3.1 update already?

Also since pushing 3.1 my WiFi will not work ... any advice?

edit: nm... it started working on a reboot.
[Upgrading, Modifying and Unlocking] drtechy:
Got my OTA yesterday
[Upgrading, Modifying and Unlocking] khtims:
Hey guys, looking for a little extra help. i have searched all over and have spent a couple hours working on this root and getting nowhere. I am stuck at entering ./nvflash -- bl bootloader.bin --getpartitiontable ptable.txt i get the error: Nvflash started

usb read error (108): Cannot send after transport endpoint shutdown

miniloader download failed (response read failed)

rcm version 0X0

When i run lsusb it can see the device just fine and i've tried this command with and without sudo in front. Please any suggestions would be awesome! Thanks!! Oh, also I am on 3.1 if that makes a difference in this process.
[Upgrading, Modifying and Unlocking] deez1234:
You need to root using CWR and flashing our root.zip on our project page here.... http://goo.gl/IcbhQ

The instructions are on our Wiki.
[Upgrading, Modifying and Unlocking] deez1234:
And to anyone on 3.1 our bootloader is now locked due to LG. We have people working on fixing it now. Until then there will be no custom kernels, ROMs, themes, etc... We are not able to write files to the system with a locked bootloader.
[Upgrading, Modifying and Unlocking] drtechy:
I was able to root using this process on 3.1 today, thanks guys!
[Upgrading, Modifying and Unlocking] khtims:
So there is hope at least that this can be done. When you rooted your 3.1 using the CWR method were you using windows? I am just not having luck getting anything to happen with "fastboot oem unlock". The steps in the wiki look simple enough but i can't get it to happen. I am doing this connected ADB, is that correct? What can I be missing? Thanks for your help!!
[Upgrading, Modifying and Unlocking] drtechy:
I did use the CWR method, however I had to manually put it into APX mode, and then I could run the fastboot commands. Otherwsie my windows machine would not put it into apx mode automatically. Once I did that though piece of cake, was the same as the instructions said. Oh also don't forget to install those APX drivers.
[Upgrading, Modifying and Unlocking] khtims:
Great! I did not try putting into APX mode. I do have the drivers so it should be easy from here. thank you for the extra input. I would never have figured that out on my own!
[Upgrading, Modifying and Unlocking] drtechy:
No problem, it was complete luck that I figured that out. Also they say that APX mode won't show anything on the screen, but mine sure did once I got it into that mode. It showed downloading something, but it wasn't actually downloading anything, so I just connected it and tried the commands and they worked.
[Upgrading, Modifying and Unlocking] deez1234:
It is best to run the commands straight from fastboot. You hold Volume Up + Power while your Slate is powered down. Just a little tip so there are no accidents!
[Upgrading, Modifying and Unlocking] khtims:
okay, so i apologize if i'm a little slow but I've spent hours on this with no luck... So I just boot into fastboot mode with the yellow lettering at the top, then run the command fastboot oem unlock and proceed from there, correct?
[Upgrading, Modifying and Unlocking] drtechy:
Yup that's correct, except make sure the root.zip file is on the tablet before booting into apx.
[Upgrading, Modifying and Unlocking] deez1234:
There is NO need to get into APX mode! The only reason you would need to is so you can flash images to recover your tablet or to make a backup of your partitions!
[Upgrading, Modifying and Unlocking] drtechy:
I'm just saying what worked for me. I spent a few hours trying to get it to work, and that was the only way that worked. Otherwise it wasn't reading it correctly.
[Upgrading, Modifying and Unlocking] Darnell_Chat_TN:
Have you tried a reboot since getting root after the 3.1 update? To ensure it sticks...
[Upgrading, Modifying and Unlocking] Chandon:
It's worse than that. You don't just have to mount an ext4 filesystem, you have to mount a *file* as an ext4 filesystem.

The only reasonable approach I can think of for Windows would be to get nvflash working and then have someone give you a modified system.img to flash.

It'd be way easier to reboot to Ubuntu, install xchat, and then come onto Freenet #g-slate in the next hour or so and let me see your next four silly error messages as you try to do it on Linux.
[Upgrading, Modifying and Unlocking] buckbullstallion:
issue is >> ./nvflash: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory

please help!!
[Upgrading, Modifying and Unlocking] Chandon:
Apparently there are some libraries that existing users of Ubuntu manage to install by mistake but don't come with a fresh Wubi install.

If you're on 32-bit Ubuntu, do this:

For 64-bit Ubuntu, do this instead:

If there are any other missing libraries, do something like this to try to figure out which package to install:
[Upgrading, Modifying and Unlocking] Bling_Diggity:
True, that would be easier, if I hadn't just gotten the linux method to work :)

Do what Chandon said, and try it again. If you get a permission denied error, make sure to enter "sudo" in front of it. I had to enter "sudo" in front of damn near every command besides mkdir in order to get it to work.
[Upgrading, Modifying and Unlocking] buckbullstallion:
connection failed NvError 0x30010

now i get that after the second command

the nflash says started then this happens i will erase ubuntu and reinstall it..

probably fix this ... as i see issues with it installing other programs.
[Upgrading, Modifying and Unlocking] buckbullstallion:
second phase going now

a strange conflict on my windows 7 machine with installing WUBI so i installed VMware player and the latest 11.04 install of Ubuntu. I proceeded to plug usb cable in and from an off device held both the volume up and volume down and then powered immediately VMware stated the nvidia vdx could be found in my mountable usb i went there it doesn't show vdx but does show nvidia so mounted then proceeded.

opened up a root terminal :su. things are moving step 1 took seconds to display the nvidia chip information.. I am now halfway through step 2, providing you are using usb 2.0 port should take about 3 to 5 minutes on this step coping the system and you will see activity numbers xxx/xxx bytes received. step 3 cp system-orig.img, system.img took about 30 seconds to a minute. every thing from that point to copying back to system is instant. then it takes a bit to copy back over looks like its not going as fast as copying to flash memory I would think takes a bit longer. last step is about 3 seconds and now rebooting device,

Installed ran root checker and my device has been liberated from the corporate prison it was in thank you for the info and the wonderful tutorial. i was just adding this for people that want to know about vmplayer and yes it did work for me using vmplayer with the 11.04 ubuntu image installed.

YES!!!! LOVE IT I AM ROOTED AND LOVING IT.
[Upgrading, Modifying and Unlocking] buckbullstallion:
It Had not erased anything from my device that I can tell, just a nice vanilla root. woot.
[Upgrading, Modifying and Unlocking] deez1234:
Yes I applaud Chandon for taking the time to find this!
[Upgrading, Modifying and Unlocking] Bling_Diggity:
Glad you got it to work. Just to confirm, you said you did get it to work using vmware? Thats interesting, because I tried it with virtualbox but couldnt get it to recognize the device. Like lsusb came back with nada. Thats why i had to go with a wubi install.

Cool, so now we have 2 confirmed sub-methods that will work for non-linux users.
[Upgrading, Modifying and Unlocking] Jaffer1979:
Not getting past lsusb

My g-slate is the DoCoMo Optimus pad

So I am trying this on a fresh Wubi install,

When I do a lsusb while my device is powered on i get a "Bus 001 Device 005: ID 1004:61f1 LG Electronics, Inc." However when I turn it off and plug in the usb It powers back on. This time I power it off already connected to usb. When I hold both volume buttons and press power it goes into a state where it acts like it is dead like we want but a lsusb in term nets me nothing. The LG entry is gone and no sign of an Nvidia one.... Any help would be greatly appreciated.
[Upgrading, Modifying and Unlocking] Jaffer1979:
Not getting past lsusb

PS plugging in the usb after it is in the seems dead state nets me nothing as well.
[Upgrading, Modifying and Unlocking] Chandon:
Jaffer1979 -

That's not a good sign. If you can't get the Nvidia USB device to show up then it's possible that LG disabled APX mode for the DoCoMo version.

What do you get when you boot with just volume up held? Just volume down?
[Upgrading, Modifying and Unlocking] Jaffer1979:
Not getting past lsusb

vol + plus power equals "Starting fastbootusb download protocol"

and "Bus 001 Device 006: ID 18d1:d00d Google Inc." in lsusb

vol - = entering lg mdp mode do not power down downloading now

and "Bus 001 Device 007: ID 1004:6000 LG Electronics, Inc. VX4400/VX6000 Cellphone" in lsusb

sorry will only let me post every 5 mins
[Upgrading, Modifying and Unlocking] Chandon:
That's the same as what I get, so no good news there.

Unless you have better luck with fastboot than I did or you can find some way to take advantage of the LG loader, it looks like you're stuck with a device that's locked down pretty hard.
[Upgrading, Modifying and Unlocking] Jaffer1979:
deep sigh.

Fudge.... Why does DoCoMo have to be jerks????

By better luck with fastboot what do you mean?

And lastly says do not power down....... ok to power down???
[Upgrading, Modifying and Unlocking] Chandon:
Yea, resetting from the LG "do not power down" screen is fine (as long as you haven't found a way to actually send it a ROM to write).

When you power up with volume + and get the fastboot screen, it's *claiming* to give you pretty complete access to the system. And on my device it's lying hard. But it might be worth grabbing a fastboot binary and playing with it a bit - try to boot a rescue image or something - in case that's different on your device too.
[Upgrading, Modifying and Unlocking] Jaffer1979:
deep sigh.

Well this is poop.... Thanks a million for attempting to help me.

I am super bummed as there is nothing worse than being on a device stuck on the japanese android store.
[Upgrading, Modifying and Unlocking] Jaffer1979:
deep sigh.

Think you could direct me to a thread or insturctions that I could follow to see if my fastboot behaves differently than yours?
[Upgrading, Modifying and Unlocking] Chandon:
You can use the tools for a Xoom root to see if your Fastboot is working.

Whatever you do, *do not* run any commands starting with "fastboot flash" - if you install a Xoom kernel there's a good chance you'll brick your device. Instead see if you can get "fastboot boot whatever.img" to work (or give an interesting error on the device screen) with either a Xoom boot.img or rescue.img file.

http://xdaforums.com/showthread.php?t=1010568
[Upgrading, Modifying and Unlocking] Jaffer1979:
No Joy

Fast boot Pretends to accept my commands going to the next prompt waiting for me not giving me error one to indicate it is not doing what I tell it.

That said nothing seems to happen at all......................
[Upgrading, Modifying and Unlocking] drtechy:
Yes, a couple of times. No issue, still have root access.
[Upgrading, Modifying and Unlocking] deez1234:
Rooting the Slate on 3.1 is definitely going to stick if you followed the directions on the Wiki. Just make sure it is flashed through CWR and you run the correct ADB commands. I haven't had an issue yet.
[Upgrading, Modifying and Unlocking] Trevnerdio:
Everything seems to be ok up until the boot hacky recovery...and Windows command prompt shows everything completed normally, except that it doesn't reboot into CWR. It says booting...OKAY [0.000s] What now?

EDIT: So it went into CWR this time...and I flashed root.zip. Rebooted, no root. I'm already running the OTA 3.1 is that a problem??
[Upgrading, Modifying and Unlocking] DarkShim:
Just a tad confused here. If 3.1 brought us a locked bootloader, yet root works anyway, there is still no way to flash custom roms?
[Upgrading, Modifying and Unlocking] deez1234:
Not until all the bugs are worked out of CWR. Plus we need the bootloader to be unlocked to be able to flash CWR and have it stick. Right now it can be booted but not flashed with fastboot. The devs are more focused on the bigger issues first. Technically you could flash ROMs but no one is going to make any until all the kinks are worked out. I hope that summed it up.
[Upgrading, Modifying and Unlocking] deez1234:
Try it again but mount the system partition in CWR prior to flashing. Let me know if it helps.
[Upgrading, Modifying and Unlocking] tuananhnt:
PLEASE FOR HELPS !

HOW TO UNBRICKED LG DOCOMO L-06C

(Now ! My pad just only connect to PC on APX mode )

hi everyone i have a major issue with my rooted LG Optimus Pad L-06C. If anyone can help it would be greatly appreciated. i downloaded CW from the market and when it askes you for compatibility i accedently chose the option (lg optimus 3d) thinking it was for my gslate and now after i turned off the gslate and go to turn it back on its stuck on LG blackscreen and says

[HasValidKernelImage] Magic value mismatch:

[DetectOperatingSystems]kernel image is invalid !!!

Starting Fastboot USB download protocol

After, I did with Ubuntu to wipe paritions with nvflash (N = partition #, use table above to prefix):

Code:

./nvflash --bl bootloader.bin --getpartitiontable ptable.txt

./nvflash -r --format_partition N: (I'd this from 1 to 8(eight) :-( )
[Upgrading, Modifying and Unlocking] Trevnerdio:
No dice :( any more suggestions?
[Upgrading, Modifying and Unlocking] 141park:
Thanks. I figured it out and am rooted now. Thanks
[Upgrading, Modifying and Unlocking] tuananhnt:
How can i use files backup of Docomo L-06C Honeycomb 3.1 to restore my pad ???

With Code:

dd if=/sdcard/misc.img of=/dev/block/mmcblk0p3

dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p5

dd if=/sdcard/boot.img of=/dev/block/mmcblk0p6

dd if=/sdcard/oemboot.img of=/dev/block/mmcblk0p10
[Upgrading, Modifying and Unlocking] guyinyoureye:
Wiki Instructions

I feel like a douche for not grasping the instructions but I downloaded all drivers and files to my computer but what does this mean?

•Untar the CR-hacky-recovery-v909.tgz, use an app like 7zip or WinRar or tar or...

•Boot the recovery:

fastboot oem unlock Then:

fastboot boot CR-hacky-recovery-v909.img

I am unpacking the tgz on my computer right?

How do I "boot the recovery?"

Putting the Slate in "download mode" or fastboot mode is doing nothing.

Someone point me in the right direction. Im all wound up but hitting the wall.
[Upgrading, Modifying and Unlocking] drtechy:
I'm not trying to be a jerk even though of course this will sound like it, but if you are unsure on what these terms mean perhaps you should not be attempting this. You should go back and read up on ADB for Android, as well read how other devices are being rooted.

As for "un-tar" essentially a tar file is exactly like a zip file. You have to extract the files from there before you can use them. The commands for fastboot should be entered into your command prompt. This depends of course on whether you are using linux or windows for this process.

Also fastboot mode does not show anything, it will be a blank screen.
[Upgrading, Modifying and Unlocking] Darnell_Chat_TN:
Actually, post 3.1 update the fastboot screen shows the LG logo and a message at the top of the screen mentioning fastboot mode. At least that's what was there when I rooted mine.

I do agree that if someone does not understand the terms. It may be in their best interests to read up a bit more before engaging in this endeavor.

But I did post some additional details for those who may need them in this thread on the T-Mobile forum.
[Upgrading, Modifying and Unlocking] guyinyoureye:
Ummm..a jerk, kinda. But i know my way around adb, recoveries, tgz,tar, hboot, fastboot, bootstrap, s-on and so on. But thank you for your concern. But instructions say unpack OR boot the recovery. Kinda confusing for me.

So i just put slate in fastboot and send commands and that is pushing img to slate and

I should be adding in my own locations to commands right?
[Upgrading, Modifying and Unlocking] drtechy:
My bad, it did sound like I was a jerk lol. But anyway, yes that should be it, as long as you get it into fastboot and you run "adb devices" and it shows it then your good to start running your commands by adding your locations.
[Upgrading, Modifying and Unlocking] dasunsrule32:
That is the directions to "boot" the recovery. :) If you read the prerequisites, you'd see that you'd need the fastboot binary. :) Read, and re-read the documentation, it's very clear. It tells you what you need to do, by telling you what to do. ;) I purposely made the directions, step-by-step.
[Upgrading, Modifying and Unlocking] mizmellyjelly:
sigh...I hate to be the newb asking the dumb questions here but this is only my second Android device and my first one was a lot easier to root (without the one-click method) in which a LOT more information was provided (plus video tutorials) thus making me feel more comfortable doing it.....

So the newbie question is...this means I can't use this root method for my Optimus Pad (LG v905r)? I was looking at the wiki site (http://code.google.com/p/lg-v909/wiki/Rooting) and I know it clearly states for the v909 only but I keep getting confused because I'm reading others are successfully rooting their "Optimus Pad" (not G-Slate). For those who have done this, did you follow these same steps? Also has anyone else with the v905r been successful in rooting their device?

Sorry again >.<
[Upgrading, Modifying and Unlocking] Trevnerdio:
Hi everyone, I've tried the hacky root multiple times and it hasn't worked. I've been able to get into Clockwork recovery but once I'm there, I mount system partition and reboot and I have no root access. I tried it again without mounting the system partition but obviously that went no differently. What do I do?
[Upgrading, Modifying and Unlocking] fivestar0234:
Anyone have the the 3.1 kernel , so i can flash and unbrick my g slate ?