yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] Zacpod:
Ya. I think they just renamed Recovery to PKG. If Fastboot tries to boot to the MTD named "Recovery" instead of "Boot" when a certain key is held down then renaming the mtd back may be all that's required. I'm not having any luck finding out how to do that tho.

The only thing we'd really need it for is to take a live backup when we're on the road.

Yep, not a thing in there. I've actually been toying with the idea of using pkg and cache as more space. Cache could be mounted to /data/app and give us 60+mb of dedicated application space, leaving all of /data free for email etc. Dunno what we'd do with pkg. It's only ~5mb. Maybe mount it as /userbin or something, to hold a bunch of console commands or something... Busybox, Bash, and Nano would fill it to the brim and clear 5mb on System for more flashed-in apps that would survive a factory reset. (factory reset from the Eve's menu system, not a reflash from the LG util.)
[Upgrading, Modifying and Unlocking] Zacpod:
(Deleted double post.)
[Upgrading, Modifying and Unlocking] Zacpod:
Probably a good thing we can't mess with it, as it'd be waaay too easy to kill the phone... I bet that's where the unlock stuff lives tho.

secure-wallpaper! Lols! Now I wanna get in there and change it to ditch the Rogers bootup logo!

Interesting stuff... We never did figure out if we could rebuild the kdz and have it flash a modified image for us. Kind of moot with fastboot, unless we do end up needing to mess with the AMSS.
[Upgrading, Modifying and Unlocking] DJ_Spray:
excuse my "thickness", when I do a sudo cp 11-android.rules /etc/udev/rules.d/

it prompts for password, i just press <enter> and it doesn't copy....

It's the first time I use a VM with preconfigured linux (I always used to install it, hence know the root account....)

many thx

edit

ok, got it by typing sudo -s , then typing any pwd (I typed user) to enable the root account I guess (default root pwd was blank, so disabled)

edit2:

I did plug my phone, udev restart and now when I type the adb devices, it shows as follow:

root@ubuntu:~/android-sdk-linux_86/tools# ./adb devices

List of devices attached

????????????	no permissions

what's happening? do I need to have the LG modem driver installed on windows (really doubt it).

On my phone, I have entered the hidden menu and pressed the enable root, I have enabled the debugging mode also on setting.

Edit3:

tried isntalling under windows. I found the LG modem drivers, installed but I get an error on the VComm driver (!). adb doesn't see the device..... :cry:
[Upgrading, Modifying and Unlocking] Zacpod:
Wooot!

Now that I have a good backup system in place and can restore my phone to working order within a few mins I've started playing with 2.0 again. I've got it booting on the device, but also don't have the radio working.

I am able to mount the sd card, though it doesn't mount automatically.

Weeee! Sleep now, but I'll play with this more tomorrow. :)
[Upgrading, Modifying and Unlocking] routehero:
Post #32 for the instructions on how to get the radio to work on boot for about 2 seconds. :)

As for sdcard, just to get it to mount automatically just put in the old vold.conf in /system/etc.

There's also a wireless module that needs to go in /system/lib/modules/wireless.ko. I haven't worked on that part yet.
[Upgrading, Modifying and Unlocking] Dukeraoul911:
dj_spray,

if you have those ??? with adb devices. just reboot linux and make sure you FIRST launch adb devices with a sudo. i say first because if you first type the command without being root it launches the daemon with restrained permissions and then you have to kill it before trying again

hope this helps
[Upgrading, Modifying and Unlocking] DJ_Spray:
thank you so much for the sudo trick..... it now WORKS!:!!!

got the terminal installed.

I guess that this sounds good too?

Edit: this is from the adb, but not from the terminal on the phone itself.

on the terminal itself, I get a uid=10071 and gid=10071.

I did put your modified init.rc from page6 on the root directory.
[Upgrading, Modifying and Unlocking] enkoopa:
From terminal on the phone you have to type su first
[Upgrading, Modifying and Unlocking] Adam620:
Just one cheer for Zacpod and routehero, that I wish I could help (but I seem to lack time and most importantly expertise...), but instead only can thank wildly :D

Adam, dreaming about an Eclair Eve ;)
[Upgrading, Modifying and Unlocking] DJ_Spray:
PERMISSION DENIED..... sniff
[Upgrading, Modifying and Unlocking] Grank:
Question

Hey, just to clarify, the radio isn't working yet in this build is it?
[Upgrading, Modifying and Unlocking] Dukeraoul911:
look after page 6 to find the procedure by zacpod to allow applications to use root. youll need to install superuser apk i believe. then when you type su with connect bot you ll be notified your application needs root acces
[Upgrading, Modifying and Unlocking] Zacpod:
Yep - I'll be trying that stuff out later today. :)
[Upgrading, Modifying and Unlocking] Zacpod:
The radio isn't working in the 2.0 build yet. And in Nandroid (which I think is 1.5 based) it would be pointless. We don't even attempt to start the radio in the Nandroid system - There's only enough there to take a backup of your device.

e.g. I take a full backup of my original 1.5 image, then flash on 2.0 and mess around. When I'm ready for a functional phone again I simply restore the 1.5 image I backed up and it's back to new - complete with data. :)
[Upgrading, Modifying and Unlocking] Dukeraoul911:
Zacpod,

I didn't see any fastboot command in android sdk/tools.

do we need get it from somewhere else?
[Upgrading, Modifying and Unlocking] Zacpod:
If it's not in the SDK you may have to download it separately. I had to download it for windows, but it came automatically for mac and linux.

You can get from the first link here.
[Upgrading, Modifying and Unlocking] Dukeraoul911:
thks I also found it on htc website.

I managed to backup my phone and I have a few questions:

- during the backup I had this error: "mount: mounting /dev/block/mtdblock6 on /cache failed: Device or resource busy"

is that important? I rebooted the device and every time I got this.

- do you confirm once we've got a valid backup, we can do whatever we want, we'll always been able to unbrick it, restore?

I'm looking forward to flash with 2.0, I'd just like to make sure my phone will work again :)
[Upgrading, Modifying and Unlocking] Zacpod:
Nope, you can ignore that one, and the :dev error before it. Anything after "Copying tools to Cache" is serious though. I'll update the script within the next few days to get rid of those.

Well, no guarantees on my part. All I can say is that it works for me. I've gone back and forth between working on a 2.0 image and my day-to-day 1.5 image several times using the modified nandroid. After a restore my phone has all my data and apps on it, and works fine. I imaging it will do the same for everyone else, but don't come trying to sue me if it doesn't. ;)
[Upgrading, Modifying and Unlocking] Dukeraoul911:
Allright then, I'm ready to flash this baby :)
[Upgrading, Modifying and Unlocking] routehero:
LG's /system/bin/rild has a mod to it which requires a flag set in order to log.

echo 1 >/data/nv/QCRilLog_flag

Once this is done, you can view via logcat -b radio.
[Upgrading, Modifying and Unlocking] Grank:
One thing I haven't figured out:

If I wanted to continue using the LG Home screen, how the hell do I get rid of that stupid Rogers group? I've uninstalled all the crap that used to be in it but I can't delete it.
[Upgrading, Modifying and Unlocking] Zacpod:
I've been poking away at 2.0 off and on all day. I'm not having much luck with the radio, but I'm not concentrating on it too much - I figure it'd be duplicated effort from what Routehero is doing. Instead, I've been working on getting all the google apps (market, gmail, etc) back in to the 2.0 image. So far, I can get a version of maps with navigation to run - though it doesn't have a data connection. The other apps complain about not having the right odex for this version. I'm currently working on getting the built in apps de-odexed (i.e. get the classes moved back in to the jar files from the pre-compiled odex files.)

Once those are working I'll probably see if I can get sound working on 2.0. Right now it's just outputting to a stub driver, so the device makes no noise.
[Upgrading, Modifying and Unlocking] DJ_Spray:
thanks guys, now it works modifying the su app...

edit: do you know if tethering works? http://code.google.com/p/android-wifi-tether/downloads/list

I used it on my G1, just wondering......
[Upgrading, Modifying and Unlocking] Zacpod:
Routehero: Hey, I noticed this in the build.prop file in the AOSP system.img

rild.libpath=/system/lib/libreference-ril.so
rild.libargs=-d /dev/ttyS0

and this is the same lines from the orig:

rild.libpath=/system/lib/libril-qc-1.so
rild.libargs=-d /dev/smd0

Wonder if that has anything to do with it not working...
[Upgrading, Modifying and Unlocking] routehero:
yeah, after you change the rild stuff, you have to copy over the list of library requirements. You can see the list on page #32.

On 2.0.1 (broken):

E/QCRIL(MMGSDI)( 970): qcril_mmgsdi_command_callback, Null cmd_cb_params_ptr
E/QCRIL(MMGSDI)( 970): Unhandle file_type for GET_FILE_ATTR_CNF 0x4 in qcril_mm
gsdi_alloc_and_copy_mmgsdi_cnf!
E/QCRIL(MMGSDI)( 970): Potential Data Abort of invalid pointer access! Please
check!!!

1.5 (working):

D/RILJ ( 1174): 38: [69] QUERY_NETWORK_SELECTION_MODE

D/RILJ ( 1174): 39: [70] RIL_REQUEST_SET_STABILITY_TEST

D/RILJ ( 1174): [0031]< SIM_IO SimIoResponse sw1:0x90 sw2:0x0

D/RILC ( 1046): [QCRIL(MMGSDI) qcril_mmgsdi_common.c 1822] RIL --- UICC card: mmgsdi_get_file_attr() ---> AMSS []

Bit blind on this, though. No source code, and since I've copied all the relevant binaries in to 2.0.1.
[Upgrading, Modifying and Unlocking] Dukeraoul911:
hey guys,

could you tell me where i can find vanilla android 2.0 sources and some usefull links/docs to build it..

I didn't find that much stuff on the net yet...

thanks
[Upgrading, Modifying and Unlocking] mathieuc:
You can get the source at http://source.android.com/

Instructions on how to build it is available at: http://source.android.com/download (scroll down to the bottom of the page)

Basically when you have the source code fetched you only need to execute 'make' in the main directory where you put the source but of course there is more to it than that.

I built it for myself yesterday and have a valid nandroid backup of my phone (flashed to 2.0 and back to 1.5 a few times yesterday without any problems) so if you guys need someone to try some hypothesis out, just ask.
[Upgrading, Modifying and Unlocking] Dukeraoul911:
thanks for your help,

Now I'm fighting with git to get the sources from windows.

I'm pissed off about kubuntu which is not booting anymore....

This thing is driving me crazy, people are just saying windows is **** and not stable... look at kubuntu it's not even more stable.. (I mean kde not linux of course). I'm really starting to hate KDE....
[Upgrading, Modifying and Unlocking] DJ_Spray:
have you tried the divx support? I don't seem to be able to read divx movies. I did search on the web for free divx videos (10mB demo files, LEGAL), and I can't read them. am I supposed to have a special driver/program or just use the video player included by default? ( I always thought the divx support was hardware and needed absolutely no driver).

thanks.
[Upgrading, Modifying and Unlocking] routehero:
One particular function that simply doesn't exist in the 2.0.1 world that libril-qc-1.so uses is SimIoResult.

I dedexed the framework.odex from 1.5 and it was SimIoResult.java. I don't have it in my 2.0.1 tree.

So this means we'll have to write functions that perform the task with the new APIs or, alternatively, figure out what's blocking libreference.so from working against the QC radio in this unit.
[Upgrading, Modifying and Unlocking] Zacpod:
That doesn't sound like fun.

I'm going to write an email notifying the Software Freedom Law Center about LG not releasing their kernel modifications. If we can get those mods then we can just compile a vanilla kernel and be done with all this reverse-engineering bs.
[Upgrading, Modifying and Unlocking] Zacpod:
Actually, before I get the SFLC to go all legal on their asses I did a google search.

It seems LG has a specific email address to send GPL requests to since they lost a court case around one of their TVs earlier this year.

The address is bitbucket@lge.com

Lol, no, just kidding. ;)

It's opensource@lge.com

I've sent an email asking for the mods. After a week if I get no response I'll contact the SFLC.
[Upgrading, Modifying and Unlocking] Dukeraoul911:
actually i dont think LG really cares about 10 guys trying to tweak their phone.. but well see :)

after loosing my time with this kde thing i managed to have another linux working in vm. so i could retreive vanilla source which is far easier to do using linux tools than GIT under windows.

I also managed (finally) to have my drivers working on 7 and I confirm there is only way to do it: enkoopa's way! thanks by the way.
[Upgrading, Modifying and Unlocking] enkoopa:
That's who I emailed last week :) Apparently that email address is very rarely checked or at least they don't respond :(
[Upgrading, Modifying and Unlocking] Grank:
+1 / QFT :)
[Upgrading, Modifying and Unlocking] Zacpod:
Aw crap!

Maybe we should extract all the email addresses from the init.eve.rc file and send them a message about their GPL violation?

I think the version of WPA_Suplicant has some modifications to it as well - when I tried to start it from command line it horked out a bunch of messages about being unable to contact the LGDRM service - I don't have the specific messages as I've got my "working" 1.5 image on the phone now, but I'll post it next time I throw 2.0 on there again.
[Upgrading, Modifying and Unlocking] Zacpod:
Not having much luck on the 2.0 front. I've pulled in a bunch of libs, and a pile of other stuff from the original system.img, but along with the radio not working I can't get wifi or sound either.

Logcat *:e horks out tonnes of these too:

E/copybit ( 1000): copyBits failed mfd(27) err no(-1) (Operation not permitted)
E/libagl ( 1000): copybit failed (Unknown error: -1)

On another note, does the system name specified in the build.prop control which init.rc gets run? I've tried a build of system.img where I used the original build.prop instead of the one generated by make, and the poor device goes in to a boot-loop with tonnes of this:

E/QCRIL ( 979): GSDI RPC calls are not working!
E/QCRIL ( 979): CM RPC calls are not working!
E/QCRIL ( 979): MMGSDI RPC calls are not working!
E/QCRIL ( 979): GSTK RPC calls are not working!
E/QCRIL ( 979): WMS RPC calls are not working!
E/QCRIL ( 979): NV RPC calls are not working!
E/QCRIL ( 979): SND RPC calls are not working!
E/QCRIL ( 979): lgeat_null !
E/QCRIL ( 979): lgeat_null returned FALSE!
E/QCRIL ( 979): LGEAT RPC calls are not working!

Sleep now. Work out my frustrations tomorrow. :)
[Upgrading, Modifying and Unlocking] enkoopa:
OMG! LG WROTE ME BACK! Sent them some information, I should have an account in a week or two.
[Upgrading, Modifying and Unlocking] Grank:
...WOW.

I don't think anyone saw that coming :D
[Upgrading, Modifying and Unlocking] enkoopa:
Well, he said they only provide source code for the parts listed in the manual.. but the manual doesn't say anything at all about GPL lol.

Hopefully we luck in and there's enough source code to get 2.0 working.

Free upgrades for LG, I don't see why they'd be against it! :)
[Upgrading, Modifying and Unlocking] Grank:
The main reason would be if the network lock is software or circumventable by software. That would weaken the commercial viability of their product because carriers would drop it like a hot potato. It's not that popular of a phone, against the Droid and the Nexus One and things like that it would just disappear from the marketplace.

It definitely already weakens them that it's so easy for us to delete the stupid bundled carrier crap.

On the other hand, if the community is able to mod it easily and make those modifications available to a less technical subset of the community (as in "here's an image that you don't need to mess around with the android SDK too much to install"), it could make it a fairly popular phone amongst hobbyists.

None of that really matters because LG is under legal obligation to release all of the source to any modifications to anything covered under GPL, which it looks like is the bulk of their customizations. As you guys pointed out, they seem to have recently been intimidated by licensing issues so hopefully that means they'll comply.
[Upgrading, Modifying and Unlocking] enkoopa:
Well, I'm sure anyone wanting an unlock would sooner pay 6$ to get an unlock code then root and custom flash their phone.. also, as we can see, I bet the hardware lock is implemented behind the scenes where we can't get at it..

Anyways, yup, excited, we'll see what they do! Hopefully everything is complete!
[Upgrading, Modifying and Unlocking] routehero:
Hardware lock is in AMSS. We can access it, but it's not well documented or particularly safe.

There's a tool called QMAT that helps you manipulate the lower level stuff on a Qualcomm-chip phone.
[Upgrading, Modifying and Unlocking] Grank:
Well yeah, but my impression was that in the US, getting an unlock code if you're not a qualified certified professional authorized to be doing the work is considered illegal under DMCA. They would probably dislike having another vector into that, since it's a lot easier to prosecute people selling unlock codes (especially since they're making a profit on it) than it is to somehow find out people are doing things with open source code and access they enabled. ;)

But yeah... I hope they don't make us wait a really long time; I don't really get the whole thing of "I sent them information and should have an account in a week or two." What's going on there?
[Upgrading, Modifying and Unlocking] enkoopa:
They requested some information - contacts details, address, etc. Then they'll create an account on their site (guessing they have some site to manage the code and what products code I have access to) and send me the information once the account is made.
[Upgrading, Modifying and Unlocking] Zacpod:
Amazing! They actually do talk in the whitepaper available on the GW620 website about the linux kernel being gpl open source. Fingers crossed that we get the drivers we need! W00t!!!

I think we'll still have a bit of a chore getting Market/Gmail/etc working on AOSP, but that should be way easier than what we're doing now!

Plus, we'll be able to build kernels with iptables etc included so we can do wifi tethering, firewalling, and all kinds of other ip magic! :D

Ya, I played a little with QMAT back when I was trying to decode the kdz/dz/etc. It seemed like a real easy way to perma-brick, lol.

But, ya, the unlock stuff is in an area that we can't easily mess up with a simple flash. The way LG has this phone rigged up we can't even get directly to the bootloader, which is kind of nice... I nuked every partition on the MTD and was still able to flash on a new image. :D
[Upgrading, Modifying and Unlocking] enkoopa:
Here's the thing.. isn't every other phone going to have the same issues with AOSP and the Google apps? Can't we share the information some how on getting these to work?
[Upgrading, Modifying and Unlocking] Grank:
Well I kinda get that, although I don't know why they need more than your name and your email address, nor why it's a manual process to create an account that could take a couple weeks. That's all I'm wondering, as it seems kinda weird on their part.

Yes, at least they're complying with GPL, which is great and an awesome lifesaver for this project, but at the same time it just seems to me that even companies that do so make it difficult. Why do they need a private area on their site at all, that they need your contact details and address to provide you with? They should just be able to link you to the source code in question at a publically available URL or it's not particularly compliant. It just seems silly, since the license should fully allow for you to turn around and plop that code somewhere more accessible for everyone to consume (like this forum for example, which I would assume you're probably going to do), so why put us through the hassle.

I don't think it should be a matter of products codes to which one has access; if the code is by law supposed to be public then it's no different than every hardware manufacturer's site where you go through a narrowing menu of choices until you find the driver you want for your device. Just toss it out there for compliance and stop stalling?

(/soapbox)
[Upgrading, Modifying and Unlocking] enkoopa:
Actually the source doesn't have to be public. They only have to provide it to owners of the product. So someone who does not own a GW620 in theory has no legal grounds to request it.
[Upgrading, Modifying and Unlocking] Zacpod:
Yep. It'll be waaay easier. For the apk apps we'll just need to:

dedex their odex files

recompile them in to a classes.dex

reinsert the classes.dex in to the apk

resign the apk with the test keys

I think the process will be similar for the [framework].jar files, but I've not looked in to those yet.
[Upgrading, Modifying and Unlocking] enkoopa:
What is the ODEX file? I thought it was just some precompiled dalvik stuff that. Could be regenerated?
[Upgrading, Modifying and Unlocking] Zacpod:
That's exactly what it is, except it can't be regenerated from the APK. Once the classes are compiled in to the odex the classes.dex is removed from the APK to save space, so just pulling the APK off the phone wouldn't work as it's missing the classes.

edit: That's just for the built in apps - apps that you install, or apps in /system/app on engineering builds, have their odexes created on the fly. They're cached somewhere in /data and the classes.dex is NOT removed from the APK. It's just the preinstalled apps that have the classes.dex removed when they're odexed during the build of /system.
[Upgrading, Modifying and Unlocking] Grank:
Orly? didn't know that. makes a lot of sense! thanks :)
[Upgrading, Modifying and Unlocking] enkoopa:
Ahh okay it's becoming clear then. That would explain why the Rogers apps wouldn't work without the ODEX. I figured it would just get rebuilt, but it didn't work.. had to copy the backup ODEX file as well before it would launch.

OMG. So this might explain why my Contacts.APK wasn't working? I'll check if it had a classes.dex inside the classfile?
[Upgrading, Modifying and Unlocking] Zacpod:
If you were copying contacts.apk from another production build then yes - that could certainly be the problem. If you were compiling it yourself it would still have the classes.dex in the apk though, so that wouldn't be the issue.