Database Users

[Q] A call out to the Galaxy S ROM delevopers, help needed!

Well hello everyone.
I am an application development student from Belgium.
I am proficient in Java, VB.NET, some c/c++ and also PHP/JS/HTML/CSS
Anyways, my recent interest has been going out to creating custom roms for the galaxy S!
The problem now is though, I was able to find some guides and such, but most were incomplete, and for HTC(and other) devices.
I have no idea what is different between making a ROM for galaxy S or a ROM for an HTC device.
If anyone would like to link me to some good resources that can help me on my way, or would like to collaborate (and in the meanwhile teach me a bit) I would be more than happy! (I am open for collaboration as I am pretty proficient in Java and I'm always happy to code and learn more about coding!)

I think the question is really want you want to do!
Custom ROMs for Android are as simple as using recovery console to replace files on the system with your own versions.
ie. Replace the framework.apk which contains all theme images with your own modified one, which you can use to skin the device. Same for replacing other system apps.
Unfortunately, most of these apps are closed source, so modifying them is difficult. The stock android system has open source versions of most of them though, and you can modify those and build them, and then replace the ones on the device. I'm not entirely sure how to build them up though, but it probably isn't too hard.
Then there are custom kernels, which let you actually change the underlying linux system underneath android - Samsung has an open source version of the kernel available that you can compile, and then flash to your phone using Odin or other tools. Compiling the kernel is pretty tricky though.

Well i'm really talking about stuff like SamSet, MoDaCo, Doc's ROM and others.
I'm not saying I want to create a pro ROM in a day or anything, but i'd really love to learn more to get better (always looking for more stuff to put on the resume, I guess?!)
Thanks a lot,
Kenny

Bump for some help
(sorry for the double post but i'm really eager to learn)

I don't have time to give a detailed response right now. However you will want to read up on yaffs (file system) and odexing/deodexing ROMs.

Thank you I will definately do that,
I am following a guide now to start out creating custom ROMs for android, however it was written for Motorola Droid and I have no idea what you have to do different for a samsung galaxy s.
I am a good coder, even though I say so myself, with a lot of experience. I also have a lot of linux experience, you name it
Only the problem is the old, and much known "where do I get started?"
So if anyone can point me out in the right direction on that, tell me how/where you started out, I would appreciate it greatly!
Thanks!

Very sorry to bump again
I set up my environment in ubuntu today to get started (just gotta fix a few errors, didn't know android wouldn't compile on java 1.6, only on 1.5)
Anyways, still need some help here! thanks!

Again I am awefully sorry for the bump here but i'd really like some help.
Note that i'm not a newbie at coding whatsoever and i'm not unfamiliar with some hardcore java, c/c++ and other languages, I'm just having trouble getting started when it comes to modding an existing android release (there are tutorials on HTC and other devices but some methods do not apply to the galaxy S)

If you're trying to create a ROM from scratch then unfortunately you're out of luck at the moment. No one has really managed to do so yet. By "from scratch" I mean the Android Open Source Project (i.e. official Android git repository).
What you can do is grab an existing firmware. Extract the contents, de-odex the apks, modify them or add new apks, optionally you can also compile a custom SGS kernel using Samsung's kernel source. Then you can re-odex the ROM, pack it back up and distribute it.
There's no real "starting place" as such and you won't yet find any tutorials about how to create SGS ROMs. Just give it a go and see where you get.

Yes, I do mean creating a ROM from stock samsung firmware, of course.
So my next logical question would be now:
How do I go over extracting contents from the existing samsung firmware, de-odexing and so on?
Any links/guides/tips are greatly appreciated, as long as they are applicable to this cell phone and not totally crap, thanks!

Samsung uses rfs, I think you should know. There is a thread somewhere in this forum regarding extracting .rfs file. Understood you need Debian though.
For some readup, go search for a famous guy named JesusFreke. Tons of materials...
Hope that from here onwards, this can lead you on, and to find out more. Google is your friend too...

I'm afraid my biggest problems already occur in setting up the environment, so it's really the very beginning that gets me stuck, i'm sure coding would be a bikeride compared to setting up the environment for me (i'm no hero in linux,not at all, i'm afraid)
How the hell do I get from point A (being downloading the full source) to point B (starting to create a custom ROM?)
thanks
of course if anyone has the time, and wants to, you can PM me your msn or something, if anyone is up to it

Raykoid666 said:
I'm afraid my biggest problems already occur in setting up the environment, so it's really the very beginning that gets me stuck, i'm sure coding would be a bikeride compared to setting up the environment for me (i'm no hero in linux,not at all, i'm afraid)
How the hell do I get from point A (being downloading the full source) to point B (starting to create a custom ROM?)
thanks
of course if anyone has the time, and wants to, you can PM me your msn or something, if anyone is up to it
Click to expand...
Click to collapse
Agreed completely! Getting a full cross-compilation to Samsung's Android going is seriously difficult! There have been some promises for tutorials and guides for setting things up though, but none have appeared yet. Probably because it's hard!

Well thank you for agreeing with me on that.
I am really hoping for anyone that can help me out here, either on here or in private, and give some detailed instructions on how to get started.
Hell there is enough information on creating roms alread, deodexing, adding/removing apps etc etc etc... The real problem lies in setting everything up properly.
I think I have gotten to the point where I'm compiling the android source (without samsung specific files)
note i'm saying "i think i am compiling" because i'm hoping it won't error out on me again after an hour of compiling!
But once that is done... I have no idea where to go next, where to get the samsung specific files, or what to do with them whatsoever once i have them
thanks!

Android generic source won't actually help you much. Samsung has made a huge number of changes to it, and while it is all open source, backporting their changes to get your stock source running on the phone is a major undertaking. I believe cyanogenmod was actually working on this, but it seems without much success so far.
What the other rom makers you see are doing is taking a snapshot of a running rom, copying over all of the APKs and the files on a running device, and then tweaking those. ie. Opening up framework-res.apk and changing the image files inside.
The update.zip roms that are what most people are doing are really just using the Android recovery to replace files on the phone with their own versions. Since the underlying system is linux, and everything is a file, this actually works pretty well.
The kernel development effort is completely separate from the rest of the system though, and Samsung has provided the entire source tree that just has to be compiled. I'm a bit stumped myself on all the details of setting it up, but I have seen some threads on this forum about it, and it didn't seem too bad to set up. Apparently you shouldn't use the codesourcery toolchain though, or something. Not too clued up on it, sorry. Hopefully someone with the details can chime in, or give us a link to the old post on it (I'm failing to find it using the search function! )

Alright sounds good!
So these recovery files you are talking about (the contents of /system) how do i retrieve those from a base ROM such as JM7 or the likes after a clean flash?)

Raykoid666 said:
Alright sounds good!
So these recovery files you are talking about (the contents of /system) how do i retrieve those from a base ROM such as JM7 or the likes after a clean flash?)
Click to expand...
Click to collapse
Root your phone, zip them up onto the sdcard, and then copy them off.
There are probably better methods, but this works fine.
Also, with credits to Unhelpful, he has told me that the correct toolchain to be using is 'uClibc or eglibc toolchain with ct-ng'. I have no idea what to do with that yet, but it's a start.

RyanZA said:
Root your phone, zip them up onto the sdcard, and then copy them off.
There are probably better methods, but this works fine.
Also, with credits to Unhelpful, he has told me that the correct toolchain to be using is 'uClibc or eglibc toolchain with ct-ng'. I have no idea what to do with that yet, but it's a start.
Click to expand...
Click to collapse
You don't even need to root your phone to pull /system Ryan
adb pull /system <random folder>
is all you need ^^

Alright thank you, I managed to get all the /system files using abd pull /system
now next thing up would be de-odexing right, before I go editing stuff?
Now before I go de-odexing. Can anyone tell me what exactly de-odexing is and why I need it?
and what do I need to do to create an update.zip again?
thanks a lot all!

Tayutama said:
You don't even need to root your phone to pull /system Ryan
adb pull /system <random folder>
is all you need ^^
Click to expand...
Click to collapse
Haha cool, didn't know you could pull whole folders!
Raykoid666 said:
Alright thank you, I managed to get all the /system files using abd pull /system
now next thing up would be de-odexing right, before I go editing stuff?
Now before I go de-odexing. Can anyone tell me what exactly de-odexing is and why I need it?
and what do I need to do to create an update.zip again?
thanks a lot all!
Click to expand...
Click to collapse
The apk files in Android are odexed - that means they have a special index applied for dalvik that speeds them up somehow! I don't know how, I haven't checked how it actually works.
The important point is though:
odexed is faster, but you can't edit it because of signatures or something technical
deodexed means you can change it however you want
More useful info can be found from google - lots of it!
update.zip is easy - it's a zip file in a special format that can be understood by Android's recovery console. The easiest way to do it is to grab an existing update.zip and modify it as needed. Tayutama has millions of em around, so use his!
Then you need to sign it once you're finished with it so that the SGS will accept it. Samsung made a boo-boo and didn't disable the test keys for the 2.1 SGS firmwares. That makes it easy!
http://www.londatiga.net/it/how-to-sign-apk-zip-files/
Just use the test keys to sign it, and then copy it to /sdcard/update.zip and reboot into recovery and it'll work.

Paid service to Flash New ROM?

Hi Everyone,
I have spent hours trying to root, get S-Off and back up my HTC Desire Z.
It's the first time I have done it and I'm a complete newbie to all of this and it's way out of my level of proficiency.
Even though the guides have been written very well this whole thing is really beyond me.
Is there a paid service or is there someone on here who has done this before a few times that could do this for me remotely? I'd be happy to pay and sit here while you work your magic.
Hopefully someone can steer me in the right direction.
Thanks!
Jason

umm, its often not the best idea to give someone access to your computer remotely, but your choice. id suggest trying to find someone local to help you. but there is always more options, often free
first of all there is little expertise needed to do it yourself, and I suggest learning how to root and why the rooting process itself works, as in the future you are bound to run into issues and not understand them, this could lead you to inadvertently brick your phone. for the most part having a rooted phone allows you to do anything to it, meaning a brick is much more possible.
I suggest reading up a bit on the process, finding out what benifits it has, and if you really need this. my guess is you want custom roms and the ablitity to use rooted apps, great, we all do. so do a little reasearch on the pros and cons and you will feel much better about it.
use google, its helpfull, search "cyanogen wiki g2 root" and "xda wiki vision root" and similar terms to find the proper rooting guides. also "reasons to root android"
read through the guides, log onto freenode irc #g2root (google it) and there will be many helpful people there that can explain what to do and why it works.
you'll be much happier and much more well informed. this will help you understand the process so future devices won't be overly complicated to you and lessen the chance for a brick, good luck!
Sent from my HTC Vision using xda premium

You get good at it the same way you get to Carnegie Hall: practice.
Sent from Spaceball One.

jason.choy said:
Hopefully someone can steer me in the right direction.
Click to expand...
Click to collapse
Hi mate,
I'm kinda in the same boat as you but I agree with the others, just stick at practising and you'll get better at it. You've managed to get root right? So that is the hardest part over and you did it. Flashing new ROM should be the easy part.
You can get real time help from the more experience members of this forum by going to this chat site:
Or you could join the irc channel, #G2ROOT on http://webchat.freenode.net/
Click to expand...
Click to collapse
where the likes of Nipqer and Setherio will be able to assist providing you ask nicely.
Go to this thread: http://forum.xda-developers.com/showthread.php?t=1178912&page=65 and ask away.

There aren't many guides here that actually work. Trust me, I've had trouble with other G2 phones. The process of downgrading and then rooting the phone is still difficult. The only guide I've ever found to work is this one. Just go down where it says "Rooting the Vision (G2/DZ) and DHD ". It explains how to downgrade, root, and install custom recovery onto your phone.
I can give you a few pointers from the guide.
#1 Get the Android SDK kit. You'll need it just to be able to do anything.
#2 Know some DOS. You may need to get yourself into the Android SDK directory or other directories. For example, cd "" is a great command. All you do is browse to where you need to go in Windows Explorer and right click the bar on top and select "copy address". Just paste that address between the quotations and you would have done half the work in modifying your phone. Also, you can paste stuff right into DOS by right clicking and selecting paste.
#3 Know some Terminal commands. Using "ADB shell" starts a terminal like shell that isn't dos, but is done through dos. Some commands need to be done in pure dos and some through ADB shell. The $ in adb shell means no root, and # means root.

Dukenukemx said:
The only guide I've ever found to work is this one.
Click to expand...
Click to collapse
That's the same guide that I used last night to root and it worked perfectly for me. I did have issues with the temp-root to backup but Nipqer helped me out in IRC. It didn't end up working (the backup) but we decided that it didn't matter too much (I just used a different backup utility that did not require root).

I suggest you not to look for a payment method but to try it your self, use a guide or ask help to a friend (or here on xda), it's not so hard.

Errors while booting Rootfs.img?

Hey guys!
I have spent the past 2 days getting this one error and after hours of reading up and trying to get all the facts straight, I just can't figure this one out!
I have cyanogen mod 10
I have Skrillax unlocked bootloader v8
and then I have all the files necessary for Ubuntu and Bodhi. Plus recoveries.
Mostly, I have been trying to follow
HTML:
http://forum.xda-developers.com/showpost.php?p=22201465&postcount=351
single post, which works great up until the point of booting! I seem to get an error that says:
"busybox: 'busybox' is not an absolute path Could not find /dev/mmcblk0p7! Dropping to a shell.
sh can't access tty; job control turned off"
(there's more after that but it doesn't seem to pertain to anything of importance that I can tell)
I just can't get over that error! I read about, but it seems like there is some dialog between other users that happened, and the conversation got changed way too fast that I couldn't understand what was going on!
If I am in the wrong area just let me know and I can move, or repost my question on a different thread. I just can't seem to find the direct answer through google, forum search, or even *shiver* Bing.
Thanks for the views, thanks for the help (if you can!).
:angel:

The odd one out!
Looks like you are one of the unlucky owners of A500 with a different file system than most A500. You will probably only be able to use the external card method for now. If some one compiles a new Kernel (recovery) then you will be able to use internel card method. Check the Dual Boot thread in the General section I made a more detailed explanation. Hope that helps

Thanks!
themechaniac said:
Looks like you are one of the unlucky owners of A500 with a different file system than most A500.
Click to expand...
Click to collapse
Thanks for the reply! I guess that answers all of my questions! Hopefully I can get something setup .

calebcoverdale said:
Thanks for the reply! I guess that answers all of my questions! Hopefully I can get something setup .
Click to expand...
Click to collapse
Ill try to compile a new recovery.img to point to 08 but no promises :-\

[Guide] Building AOSP & Adding Features

First off I'd like to apologize if this is in the wrong place or if it is perceived as advertising, I simply want to contribute to the dev community and this site, and in particular the Nexus 9 forum that has been the centre of my learning as I took up the hobby of AOSP.
I have been back and forth with AOSP, I've contributed a little bit here and there on the Android development forums but would like to properly document how to build AOSP and more importantly (because it is even less well documented) how to add features, change existing features and generally customize the operating system to your liking. I am by no means an expert but I feel I have enough knowledge that I can share it with others who may be in the position I was a number of months ago. I always found it very difficult to find a centralized location for the information I needed.
To this end I have started a site to do just that. I am using a Nexus 9 for my AOSP development but most (if not all) of the tutorials and information should be applicable to basically any AOSP/Nexus device. I have started things off by creating a tutorial on how to build AOSP from 'scratch' so to speak and a tutorial on how to add items to the power menu such as 'reboot', 'airplane mode' etc.
If anybody would like certain topics covered or just have any feedback or comments please reply here or leave them on the articles themselves. I'll do my best to accommodate / respond.
The link is: http://littlelostandroid.wordpress.com
From tomorrow the following (nicer) link should also work: www.alittlelostandroid.com
I should also add that the blog will be ongoing about all things android device but this initial series will be about also and implementing features.

wow this is a real good guide/blog u put together please do continue

Dreamlogix said:
wow this is a real good guide/blog u put together please do continue
Click to expand...
Click to collapse
Thanks! The next post should be up in a day or two, its been a busy week.

New post up about flashing the build to a device!
www.alittlelostandroid.com

This is a great website. Lol i'm gonna have to learn to use ubuntu(was gonna do it anyway on my old computer but motherboard died and i got lazy). Can you make this in chronological order? or better add each section to a sitemap? Just a suggestion:cyclops:

whowatchlist said:
This is a great website. Lol i'm gonna have to learn to use ubuntu(was gonna do it anyway on my old computer but motherboard died and i got lazy). Can you make this in chronological order? or better add each section to a sitemap? Just a suggestion:cyclops:
Click to expand...
Click to collapse
So I changed the theme so that you can see the most recent posts on the side and work from that. I'm still getting to grips with WordPress to be honest but hopefully that's better now.

Another post about setting up and storing your code on GIT repos:
https://littlelostandroid.wordpress...-open-source-project-part-4-git-repositories/

Thanks for this
Do you have any insight to share on your site about building the LTE variants at all?

THX for your work !
There are plans to continue this great guide?

scoobydu said:
Thanks for this
Do you have any insight to share on your site about building the LTE variants at all?
Click to expand...
Click to collapse
Sadly I won't be able to do any work around the LTE version as I don't have the hardware to test it on. I don't want to release advice I haven't tested and potentially end up inadvertently damaging someones tablet for example
Topse said:
THX for your work !
There are plans to continue this great guide?
Click to expand...
Click to collapse
Sorry for the late reply, I don't get any emails when someone posts on this thread, I need to subscribe to it. I do plan on doing more, in fact I think I may have some written already, just a matter of getting time to do it. I'll get to work on the next section of the tutorials and post here when it's up. Is there anything in particular you would like covered?

seanashmore said:
Sadly I won't be able to do any work around the LTE version as I don't have the hardware to test it on. I don't want to release advice I haven't tested and potentially end up inadvertently damaging someones tablet for example
Sorry for the late reply, I don't get any emails when someone posts on this thread, I need to subscribe to it. I do plan on doing more, in fact I think I may have some written already, just a matter of getting time to do it. I'll get to work on the next section of the tutorials and post here when it's up. Is there anything in particular you would like covered?
Click to expand...
Click to collapse
I m actually try to make my own little aosp rom.
I have some probs with gapps flashing.
Wrong api level error.
I tried different commits.
With pure nexus gapps it works .I need to flash it twice.
I do "make otapackage", this is different to your guide.
When I flash a custom kernel I don't have this gapps problems.?
Next thing I will integrate is that reboot option.
But with reboot recovery.
Once after flashing I was surprised with stock recovery..
How can I disable that?
At the moment I build only for my bullhead.
But if that recovery and gapps problem is solved.
I will try for my flounder and shamu too.
Actually I use n7 r 15 as source. But will will switch to 7.1*
When it is evaluable.

Topse said:
I m actually try to make my own little aosp rom.
I have some probs with gapps flashing.
Wrong api level error.
I tried different commits.
With pure nexus gapps it works .I need to flash it twice.
I do "make otapackage", this is different to your guide.
When I flash a custom kernel I don't have this gapps problems.?
Next thing I will integrate is that reboot option.
But with reboot recovery.
Once after flashing I was surprised with stock recovery..
How can I disable that?
At the moment I build only for my bullhead.
But if that recovery and gapps problem is solved.
I will try for my flounder and shamu too.
Actually I use n7 r 15 as source. But will will switch to 7.1*
When it is evaluable.
Click to expand...
Click to collapse
I'm not 100% sure about the GAPPS issue, maybe try http://opengapps.org/, it lets you choose your android version, architecture etc.
In terms of the recovery; You'll see in my tutorials that I am using the stock Google factory images as a base. In that image is a recovery.img file; You should be able to replace this file with TWRP or any other custom recovery and flash it as part of your ROM.
Hope this helps.

seanashmore said:
I'm not 100% sure about the GAPPS issue, maybe try http://opengapps.org/, it lets you choose your android version, architecture etc.
In terms of the recovery; You'll see in my tutorials that I am using the stock Google factory images as a base. In that image is a recovery.img file; You should be able to replace this file with TWRP or any other custom recovery and flash it as part of your ROM.
Hope this helps.
Click to expand...
Click to collapse
I tried opengapps. But i run in an error. Opengapps say my ROM has the wrong api level.
I tried this commit (and other like that)
https://github.com/Cardinal-AOSP/frameworks_base/commit/6c8322f3ad221ea2092e82b99ece537b85ec996f
And with pure nexus dynamic gapps . it works when I flash the gapps two times. First I get the error and the second try works.
Change recovery to twrp sounds good. But with more devices its a dangers thing. Cause ever device needs special twrp.
I think there is a way to disable this flashing recovery.
But till now I didn't find it.

Topse said:
I tried opengapps. But i run in an error. Opengapps say my ROM has the wrong api level.
I tried this commit (and other like that)
https://github.com/Cardinal-AOSP/frameworks_base/commit/6c8322f3ad221ea2092e82b99ece537b85ec996f
And with pure nexus dynamic gapps . it works when I flash the gapps two times. First I get the error and the second try works.
Change recovery to twrp sounds good. But with more devices its a dangers thing. Cause ever device needs special twrp.
I think there is a way to disable this flashing recovery.
But till now I didn't find it.
Click to expand...
Click to collapse
If it's just the case of not flashing the recovery img then just remove that line/command from the script. However you will have to assume that the device already has a recovery img (which to be honest is a fairly safe assumption).

[/STRIKE]
seanashmore said:
If it's just the case of not flashing the recovery img then just remove that line/command from the script. However you will have to assume that the device already has a recovery img (which to be honest is a fairly safe assumption).
Click to expand...
Click to collapse
I try this for recovery https://github.com/peteralfonso/platform_build/commit/9b3a020058b84fb1f9cfba600f4a958572a805c3
edit: i think this is to old...

seanashmore said:
I'm not 100% sure about the GAPPS issue, maybe try http://opengapps.org/, it lets you choose your android version, architecture etc.
In terms of the recovery; You'll see in my tutorials that I am using the stock Google factory images as a base. In that image is a recovery.img file; You should be able to replace this file with TWRP or any other custom recovery and flash it as part of your ROM.
Hope this helps.
Click to expand...
Click to collapse
I use this way to build:
cd ~/aosp/kernel/lge/bullhead
make clean
export ARCH=arm64
export CROSS_COMPILE=~/aosp/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-
export USE_CCACHE=1
make bullhead_defconfig
make -j6
cd ~/aosp
mkdir ~/aosp/device/lge/bullhead-kernel
rm ~/aosp/device/lge/bullhead-kernel/Image.gz-dtb
cp ~/aosp/kernel/lge/bullhead/arch/arm64/boot/Image.gz-dtb ~/aosp/device/lge/bullhead-kernel
source build/envsetup.sh
make clobber
lunch aosp_bullhead-userdebug
export USE_CCACHE=1
make -j6 otapackage

Topse said:
I use this way to build:
cd ~/aosp/kernel/lge/bullhead
make clean
export ARCH=arm64
export CROSS_COMPILE=~/aosp/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-
export USE_CCACHE=1
make bullhead_defconfig
make -j6
cd ~/aosp
mkdir ~/aosp/device/lge/bullhead-kernel
rm ~/aosp/device/lge/bullhead-kernel/Image.gz-dtb
cp ~/aosp/kernel/lge/bullhead/arch/arm64/boot/Image.gz-dtb ~/aosp/device/lge/bullhead-kernel
source build/envsetup.sh
make clobber
lunch aosp_bullhead-userdebug
export USE_CCACHE=1
make -j6 otapackage
Click to expand...
Click to collapse
Ah ok, see the way I build gives me separate .img files, and I write a script similar to the flash-all script you get with the factory images. This allows me to pretty easily change what i want to do and what i want to flash or not.

seanashmore said:
Ah ok, see the way I build gives me separate .img files, and I write a script similar to the flash-all script you get with the factory images. This allows me to pretty easily change what i want to do and what i want to flash or not.
Click to expand...
Click to collapse
Year , but zip is easier to use/share.

Topse said:
Year , but zip is easier to use/share.
Click to expand...
Click to collapse
Definitely, though you can always put your script and .img files inside a zip just like the factory images. so users would download your zip, unzip it and run your script. Its all down to personal taste i guess, there are many ways to skin a cat.

seanashmore said:
Definitely, though you can always put your script and .img files inside a zip just like the factory images. so users would download your zip, unzip it and run your script. Its all down to personal taste i guess, there are many ways to skin a cat.
Click to expand...
Click to collapse
:good:
I like it to try different ways.Good for learning and deeper understanding.
For my personal use is this way no problem.
But for sharing with other people is a flashable zip file the most used way.

I found a tool that can lock anything

Delete
I was warned to delete this thread because of the Xda rule.
Bye.
Close the thread!

I think it's just the common adb fastboot bootloader lock command

ExtraDan said:
I think it's just the common adb fastboot bootloader lock command
Click to expand...
Click to collapse
Maybe, but I don't know the principle.
China user

andy_zhang said:
Maybe, but I don't know the principle.
China user
Click to expand...
Click to collapse
Whats the tool? I would like to check it out.

TheMadScientist said:
Whats the tool? I would like to check it out.
Click to expand...
Click to collapse
I've been warned. I'm sorry, I cann't answer.
China user

andy_zhang said:
I've been warned. I'm sorry, I cann't answer.
China user
Click to expand...
Click to collapse
Sounds fair enough

@andy_zhang Why have you been warned by someone? The useage of the tool is completely legal, like other such tools IF you use it for legal reasons only and not things related to theft and so on. The way how they do it as far as I know on the LG is "nuking" the laf as how we called it back in the days, so the removal of the LG Download mode as it results in the access to the fastboot mode. After the reboot in the bootloader they execute the fastboot erase config command on their devices to remove the google account. And so on. The tool is just a collection of those methods and firmware flashing/restore tools. I believe that for that software you needed some kind of box though.
Btw @andy_zhang if you want to keep it secret I would suggest to remove the image.

wulsic said:
@andy_zhang Why have you been warned by someone? The useage of the tool is completely legal, like other such tools IF you use it for legal reasons only and not things related to theft and so on. The way how they do it as far as I know on the LG is "nuking" the laf as how we called it back in the days, so the removal of the LG Download mode as it results in the access to the fastboot mode. After the reboot in the bootloader they execute the fastboot erase config command on their devices to remove the google account. And so on. The tool is just a collection of those methods and firmware flashing/restore tools. I believe that for that software you needed some kind of box though.
Btw @andy_zhang if you want to keep it secret I would suggest to remove the image.
Click to expand...
Click to collapse
Well the name of the program is censored so they should be safe.
Also don't be pressured to tell the name of the software not even in PM, it doesn't worth your well being and safety, we don't have as many developers or hackers around this forum anyway so we wouldn't be able to discover how to reverse whatever the program doing anyway

@ExtraDan don't worry I won't be pressured by people. And the tool isn't some tool really meant to be secret or so. It's just not as popular in the public. And there's no need to reverse engineer anything, just seeing it function makes you realise how it works (if you have some more then basic knowledge on certain topics like fastboot and lg related things in this case). It's just that the tool is using methods that are already available publically on the internet, the only thing that the tool does is combining all those things and instead of typing just pressing a button more like. Even if the G5 doesn't have many developers, enough people still visit the G5 forums with basic android and searching knowledge.
And it isn't so safe even though the censoring but it also doesn't has to be kept safe either as it's nothing illegal if the program isn't used for illegal reasons.
Sent from my LG-H850 using Tapatalk

also I am not associated with the sources so I most likely dont think I break any law, but i found this
https://www.clangsm.com/forum/index.php?showtopic=434367&st=40&p=1717691&#entry1717691
Making an account will reveal the full name of the program on comment #49
Looking up the name brings up this thread
http://forum.gsmhosting.com/vbb/f453/lg-2-3g-tool-9-36-a-2228171/
And this is the download they provided in the last comment
https://mega.nz/#!nw4QRBII!JYvpldxFfTOiJ-EWjx-hq5C1F6Q6_L9kPy_DFvg7wE0
I havent downloaded it nor tested it, so its on your own risks, remember to scan your stuff on VirusTotal before doing anything
Seems like searching the name also shows up a lot of videos of the program being cracked, im not entirely sure what it does, but from my assumption I think its related to unlocking and locking devices to carriers, but it might be much more

this version requires the smart cards and zx3 box nothing bad here other than pricey