Related
For those of you who want to customize wm6.1, here it a simple ROM kitchen to do so. Beginners, please wait for my GUI release. It is much simpler to use. This isn't that hard, but it takes a little bit of time on your side.
The basics:
All software and regedits are contained in folders called OEM packages. These are in the OEM folder.
All operating system stuff is in the SYS folder. I've also moved the shadow drivers here so you don't have to mess with them.
To make OEM packages:
Download ervius's package creator 5.4 from XDA-developers. Use this to open the cab file to convert into a package.
Copy the OEM package to the OEM folder.
Do NOT delete the OEM packages you don't want. You will choose them later in a different way.
NOTE: You can always download premade OEM packages from XDA-Develoers. There are tons of options.
If you want to make a regedit.
Create a new folder in the OEM folder and convert it into a package using Package Creator 5.4.
Open the RGU file inside with notepad
Edit like following. Note that this isn't the way to comment in regedit files:
Code:
REGEDIT4 <-----Make sure this is always the first line
------Leave one line blank here-------
[HKEY_LOCAL_MACHINE\Software\Example Software\Example Key] <----- Navigate to keys like this
"Example String" = "test" <-------- Write values with quotes. Strings are given with quote after the equal sign.
"Example Directory" = "Windows\\test.jpg" <------ Use \\ to indicate a \ between directories. Otherwise, the ROM build will not work.
"Example Number" = dword: 5000 <----- use dword: to indicate a number or hex value.
<----- You can add more reg entries after the first one. Make sure to specify a different key when needed
-----leave 2 lines at the end of file------
For Sliding Panels:
Leave ROM as it is.
For Neo interface:
Replace Chome folders and bronze folders in SYS folder with the ones attached below.
Select Neo Interface in the buildos step.
Build ROM:
start buildos.bat
when it opens packagetools+buildos, click on the buildos tab.
Click load rom and navigate and select the kitchen folder
Select which oem packages you want and then click Go.
Once it is done, close out.
Sit back and relax for a while so the batch file can build the ROM.
Self-explanatory from here.
Post any questions/problems here.
link: http://www.sendspace.com/file/ap9n8w
NOTES: The inlcuded T-Mobile Edition Package is my beta version. Feel free to build on it. You might also notice the empty placeholder folder for my N33D4SP33D Edition rom that I haven't worked on yet.
To make OEM packages:
Download ervius's package creator 5.4 from XDA-developers. Use this to open the cab file to convert into a package.
Click to expand...
Click to collapse
I found the program but get many errors when I start it up on my computer.. Im currently running Vista Ultimate. I went into control panel and changed the enviroment to emulate WinXP when the program runs and still get many errors..
Is there a vista friendly program out there or alternative available?
I'm running Vista Ultimate too and it works perfectly for me.
Attached is the version I have.
ND4SPD said:
I'm running Vista Ultimate too and it works perfectly for me.
Attached is the version I have.
Click to expand...
Click to collapse
Great! yours works thanks alot now to get my feet wet in all this lol
I got this error
'Error building default.hv and user.hv! (see imto "BuildOsX-log.Txt")
i can't see anything in there. What now. Thanks
Do you mean there's nothing in the BuildOsX-lot.txt? There should be. A few lines from the last, or the last line, there should be the registry file that messed up and on which line it messed up on. The file is given by the GUID, or that long string of numbers and letters that you see.
no, there is nothing what tell me what to do. so what should i do with that error.
i will make stick this thread.Hope next times will see some roms with this kitchen
Thanks tom. I'll make sure to post my GUI kitchen soon to let more people create ROMs a lot easier.
kormanb1123 said:
no, there is nothing what tell me what to do. so what should i do with that error.
Click to expand...
Click to collapse
what kind of things did you modify or add? Maybe I can help based on that.
I get the same error for the following:
InitRegistry FAILED in file ".\Registry\fcbf420c-04fd-478f-bd29-e4ab55973337.rgu" within a few lines of line 359.
ImportFromPackageListStrict: (RGUComp) !ERROR failed importing ".\Registry\fcbf420c-04fd-478f-bd29-e4ab55973337.rgu"
wmain: (RGUComp) !ERROR failed building DEFAULT hives
Looked through each App in the OEM folder until I found the matching rgu number, which in my case is the HTC DirectShow. Took that out of my ROM build, ran again and it states that it completed.
I think there is a problem with the directshow package. I'll check the registry entries. Until then, I think you might need to go without that.
This may sound like a stupid question, but hear me out. I have used BuildOS in the past for an Apache from PPCGeeks\PPCKitchens. Once the ROM is finished creating in that version it auto prompts to update your device.
After the ROM is done in your version, I then selected the Package Tool tab and pointed it to the "temp" directory and it did it's thing. Now I am at a loss for what to do next. I see a .nb file temp\dump\ROM directory but i don't see a .nbh file. Do I use the NBHTool even though PHOEB is not listed?
ND4SPD said:
I think there is a problem with the directshow package. I'll check the registry entries. Until then, I think you might need to go without that.
Click to expand...
Click to collapse
I'm not too worried about the directshow, I just that maybe the other guy was getting the error for the same reason so figured I would pass on my resolution.
Sorry, I guess I didn't completely read you post. For the HTC Rom Tool, use the exacalibur settings. Those are the exact same as the Juno.
all I have is o4_osxip.nb.exe in the temp folder no nbh is this the right nb. file I use with
htc tool I put exacalibur settings but don't no what to put in firmware contents
do I put o4_osxip.nb.exe in system and none in the ipl spl and splash and 0x800 radio
ok i did this
Build ROM:
start buildos.bat
when it opens packagetools+buildos, click on the buildos tab.
Click load rom and navigate and select the kitchen folder
Select which oem packages you want and then click Go.
Once it is done, close out.
Sit back and relax for a while so the batch file can build the ROM.
ok where is the rom all i have is o4_osxip.nb.exe in the temp
i have no file imgfs-new.bin in the temp all i have is 04_OSXIP.nb.exe and cecompr_nt.dll and CECompressv4.dll
and where would i look for the batch file
Thank you for your works, ND4SPD
but i can not download your kitchen, it says reached the 4G limit.
because i want to know is there any wrong method i used.
My issue is :
when buildimgfs, the total sections can not bigger than 1B200.
when i put too many files into the imgfs file, the buildimgfs will quit without any info.
but the 71M imgfs.bin have about 22000 sections.
do you have issue too ?
Is it because my PC have only 1G RAM, not enough to do the building?
@Hikey: I have that same problem too. It's the way t-mobile packaged the rom. I'm going to try using the dopod rom for the base next. It might be the PC too. I only have 1GB of RAM, maybe it isn't enough.
@kron2:
run buildos
download this zip: http://www.sendspace.com/file/xuhlc5
copy the files from the zip archive to the temp directory.
open up the cmd that's now in the temp directory.
type the following:
Code:
ImgfsFromDump imgfs-old.bin imgfs-new.bin
Sit back and relax. If this finishes without crashing like Hikey said, do this:
Code:
ImgfsToNb imgfs-new.bin 04_OSXIPN.nb os.nb -conservative
Now you can run the htccert program in the main directory of the kitchen to build the rom. When you are done making the nbh, copy it to the RUU folder and run the update utility.
In relation to ROMs, what is a mirror? I see that on there a lot and don't know what they are and what purpose they serve.
Mirror is not a ROM term at all, but a web term. A mirror is a server that is hosting a file for download. The idea is that in order to either reduce load on the original server or expedite the download by allowing you to choose a server closer to you. The term mirror is derived from the idea that it is a remote server with an exact copy of the original file. Because of the mirror system being out of the original content provider's hands, a checksum of the download is usually provided to help ensure that the file has not been modified in any way.
lineman78 said:
Mirror is not a ROM term at all, but a web term. A mirror is a server that is hosting a file for download. The idea is that in order to either reduce load on the original server or expedite the download by allowing you to choose a server closer to you. The term mirror is derived from the idea that it is a remote server with an exact copy of the original file. Because of the mirror system being out of the original content provider's hands, a checksum of the download is usually provided to help ensure that the file has not been modified in any way.
Click to expand...
Click to collapse
Awesome. Thanks. Do you know how to check the 'checksum' or 'md5sum' as I've seen it? I'm working on the MacOS platform.
BTW - do you know how to get a term added to the glossary?
Not so sure about the "checksum" thingy, try searching the forums??
However, adding a word is as simple as going:
Settings > Language & Keyboard> Touch Input> User Dictionary> Add New OR you can just spell the word when you're texting (for example) and click the correct spelling instead of the suggested spelling, that adds it too.
Awesome. Thanks. Do you know how to check the 'checksum' or 'md5sum'
Click to expand...
Click to collapse
On linux and windows you go to file directory and type md5sum {file name}. Couldn't see it being different for mac, don't forget the .zip, .apk, etc. at the end of the file name.
Sent from my ADR6300 using Tapatalk
On mac the command is md5 (filepath)
HeroMeng said:
On mac the command is md5 (filepath)
Click to expand...
Click to collapse
I don't have my UNIX book in my office, but this sounds right. OSx is based on FreeBSD, so it has a md5 utility built in. Just open up the terminal and type the above command. On windows, you will need to download a project called unixutils, which can be found on sourceforge. The command is md5sum {filepath}. But in order to get this working you will either need to provide the location of md5sum.exe or add the wbin folder from unixutils to your path environment variable.
I have Mac and if I type for example this:
Code:
md5 /Users/kevinsimac/downloads/darchdroid-v265.zip
it returns
Code:
MD5 (/Users/kevinsimac/Downloads/darchdroid-v265.zip) = 9a7af785d5ba97bbbac1ea044c99b420
What's the whole purpose of the md5 in relation to our work here?
jerry43812 said:
What's the whole purpose of the md5 in relation to our work here?
Click to expand...
Click to collapse
As I explained above, the MD5 is usually included for files hosted on a server other than the content provider so that you can ensure that the file has not been modified. For example, I could volunteer to be a mirror for Fresh and if flipz didn't post the md5, I could add an apk into system that could do something like send me your location or a copy of all your e-mails or something else and you wouldn't know that I had modified the file since flipz handed it off to me.
i tried xUltimate to deodexing my XT860 and...... since then ו'm stuck in boot loop
Do you have a bootstrap/safestrap installed?
Sent from my DROID3 using xda premium
Endoroid said:
Do you have a bootstrap/safestrap installed?
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
i have Safestrap Recovery 1.08
when i:
Safestrap => backup and restore => restore => external SD => (appear)
nonsafe-2012-01-31 (the one i got)
run it, and
checking MD5 sums.....
MD5 mismatch!
boazal said:
i have Safestrap Recovery 1.08
when i:
Safestrap => backup and restore => restore => external SD => (appear)
nonsafe-2012-01-31 (the one i got)
run it, and
checking MD5 sums.....
MD5 mismatch!
Click to expand...
Click to collapse
****ty. I don't know if there is a way to fix that. Do you happen to have the tweaked safestrap that allows flashing the nonsafe
Sent from my XT860 using xda premium
If yes to my last question, just flash the stock bell 2.3.6 rom located in the dev forum. If no then you have 2 options. First it follow the steps in this thread http://forum.xda-developers.com/showthread.php?t=1404608
Or
Use motofastboot to flash a system.img, this will restore the /system, reroot, install bootstrap and then flash the already deodexed stock bell rom I previously mentioned to restore your /system, remove bootstrap, install safestrap and flash either that rom, or the rom of your choice into safe system and use safe system from now on.
Sent from my XT860 using xda premium
You can manually find the MD5s on a computer and edit the MD5 file manually to make it work, its dangerous but it works... I've done it before
DeadChex said:
You can manually find the MD5s on a computer and edit the MD5 file manually to make it work, its dangerous but it works... I've done it before
Click to expand...
Click to collapse
I've had that same problem in the past. How do you manually edit the md5 and how do you know what to change it to. Would I just run the md5 command in terminal and then unzip the backup and modify it?
Sent from my XT860 using xda premium
Endoroid said:
I've had that same problem in the past. How do you manually edit the md5 and how do you know what to change it to. Would I just run the md5 command in terminal and then unzip the backup and modify it?
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
The back up should just be a folder, open the folder, and run the MD5 Command in the Terminal on each of the backup archives (eg cache.ext3.tar, system.ext3.tar) and put them into nandroid.md5
The nandroid.md5 file should hopefully be laid out easily and just replace the hashes (random letters and numbers) with the ones you generated with the correct file's hash
And Restore away!
Endoroid said:
Do you happen to have the tweaked safestrap that allows flashing the nonsafe
Click to expand...
Click to collapse
don't know, how to find out?
boazal said:
don't know, how to find out?
Click to expand...
Click to collapse
V1.08d
Sent from my XT860 using xda premium
Endoroid said:
V1.08d
Click to expand...
Click to collapse
it's v1.08,
what can be done?
Either attempt to fix the md5sum as mentioned above, or restore your system through one of the options I mentioned in my previous post
Sent from my XT860 using xda premium
Endoroid said:
Either attempt to fix the md5sum as mentioned above, or restore your system through one of the options I mentioned in my previous post
Click to expand...
Click to collapse
sorry for bothering, i'm not familiar with the process, can you guide newbi? (preferred flash the rom methods)
people's, please i need assistance.....
boazal said:
people's, please i need assistance.....
Click to expand...
Click to collapse
Im at work but later tonight I will give more detailed instructions
Sent from my XT860 using xda premium
Method- Manually Altering MD5 Sums (Windows) (This guide might be off, Windows is not my home OS anymore...)
1. Plug your SD card into your computer.
2. Open up the directory where your back ups are should be /safestrap/backup/BACKUPNAME
3. Download this tool: http://www.pc-tools.net/win32/md5sums/
4. Drag system.ext3.tar and drop it on top of the applications icon
Write down that MD5
5. Drag data.ext3.tar and drop it on top of the applications icon
Write down that MD5
6. Drag cache.ext3.tar and drop it on top of the applications icon
Write down that MD5
7. open up nandroid.md5 with a text editor it should look something like this:
Code:
2ce2ec3c4beac74ba3fba94fb290ea21 cache.ext3.tar
12296836011615c7f2611e19c9390a78 data.ext3.tar
0589700a289739c448b6ff2e317d7951 system.ext3.tar
Replace the hash next to cache.ext3.tar with the one you generated, and repeat this for the other files...
IF nandroid.md5 does not exist, create it and do as mentioned above.
Then... Restore!
Sorry, I know this isn't the easy reflash you wanted but it's the only guide I can write at this time
(This guide was written going off of safestrap 1.08 you may have to change some titles of files)
Thanks and/or donate if I helped
Method- Manually Altering MD5 Sums (Linux-Ubuntu)
1. Plug your SD card into your computer.
2. Open up the directory where your back ups are should be /safestrap/backup/BACKUPNAME
4. Run md5sum on system.ext3.tar
Write down that MD5
5. Run md5sum on data.ext3.tar
Write down that MD5
6. Run md5sum on cache.ext3.tar
Write down that MD5
7. open up nandroid.md5 with a text editor it should look something like this:
Code:
2ce2ec3c4beac74ba3fba94fb290ea21 cache.ext3.tar
12296836011615c7f2611e19c9390a78 data.ext3.tar
0589700a289739c448b6ff2e317d7951 system.ext3.tar
Replace the hash next to cache.ext3.tar with the one you generated, and repeat this for the other files...
IF nandroid.md5 does not exist, create it and do as mentioned above.
Then... Restore!
You're gonna have to do the leg work to get the files and programs I mention because finding and linking while on my fine is a pita.
There is another option, the easiest of all, however it will remove you from the bell update path as we have no way currently of returning to the stock bell firmware. You can grab rsdlite and a fastboot package from the dev forum and flash that, it will fix it up but you are no longer on bell firmware. Up to you if you can live with that.
The other way is to grab motofastboot (google it) and a fastboot package from dev forum. Unzip the fastboot package into a folder and put motofasboot in the same folder. Motofastboot is a command line utility, it has no user interface. Open a cmd prompt (start button, run, cmd) and type cd C:\your\path\to\aforementioned\folder then run
moto-fastboot flash system system.img (I have the 32 bit version so mine is moto-fastboot32) I dont use windows, onlinux I have to precede the command with ./ so for me it would look like
./moto-fastboot32 flash system system.img
Your phone will now boot
Find zergrush easy root utility and follow the directions for it to root your phone, then install a bootstrap(or the tweaked safestrap that allows nonsafe flashing and then go grab the stock bell rom from dev forum and flash that. It is already deodexed.
this will keep you stock bell
Sent from my XT860 using xda premium
DeadChex said:
Method- Manually Altering MD5 Sums (Windows) (This guide might be off, Windows is not my home OS anymore...)
1. Plug your SD card into your computer.
2. Open up the directory where your back ups are should be /safestrap/backup/BACKUPNAME
3. Download this tool: http://www.pc-tools.net/win32/md5sums/
4. Drag system.ext3.tar and drop it on top of the applications icon
Write down that MD5
5. Drag data.ext3.tar and drop it on top of the applications icon
Write down that MD5
6. Drag cache.ext3.tar and drop it on top of the applications icon
Write down that MD5
7. open up nandroid.md5 with a text editor it should look something like this:
Code:
2ce2ec3c4beac74ba3fba94fb290ea21 cache.ext3.tar
12296836011615c7f2611e19c9390a78 data.ext3.tar
0589700a289739c448b6ff2e317d7951 system.ext3.tar
Replace the hash next to cache.ext3.tar with the one you generated, and repeat this for the other files...
IF nandroid.md5 does not exist, create it and do as mentioned above.
Then... Restore!
Sorry, I know this isn't the easy reflash you wanted but it's the only guide I can write at this time
(This guide was written going off of safestrap 1.08 you may have to change some titles of files)
Thanks and/or donate if I helped
Click to expand...
Click to collapse
First i 'ant to thank you
when i open my nandroid.md5 it was empty
i do the exact method, and create the 4 hash (cache, data, system, systemorig) on nandroid.md5 put it back on the phone, try to restore but ...no success. Still receive MD5 mismatch
when I return the SD carde to the pc, the nandroid.md5 empty again!
Endoroid said:
The other way is to grab motofastboot (google it) and a fastboot package from dev forum. Unzip the fastboot package into a folder and put motofasboot in the same folder. Motofastboot is a command line utility, it has no user interface. Open a cmd prompt (start button, run, cmd) and type cd C:\your\path\to\aforementioned\folder then run
moto-fastboot flash system system.img (I have the 32 bit version so mine is moto-fastboot32) I dont use windows, onlinux I have to precede the command with ./ so for me it would look like
./moto-fastboot32 flash system system.img
Your phone will now boot
Click to expand...
Click to collapse
C:\moto-fastboot-win32>moto-fastboot flash system system.img
sending 'system' (262144 KB)... OKAY [ 25.386s]
writing 'system'... OKAY [ 15.596s]
sending 'system' (175872 KB)... OKAY [ 17.214s]
writing 'system'... OKAY [ 9.043s]
but refuse to boot
boazal said:
First i 'ant to thank you
when i open my nandroid.md5 it was empty
i do the exact method, and create the 4 hash (cache, data, system, systemorig) on nandroid.md5 put it back on the phone, try to restore but ...no success. Still receive MD5 mismatch
when I return the SD carde to the pc, the nandroid.md5 empty again!
Click to expand...
Click to collapse
Linux or Windows? Esure you are safely ejecting (windows) or unmounting/ejecting (Linux) before removing the SDCard, I've noticed file changes sometimes don't stick if you don't safely eject.
I'm not sure if the method I'm giving is a soloution anymore with the reflash (That's not a bad thing!)
LG BIN/TOT Extractor
This is a tool for extracting LG Bin/Tot Firmware files.
I update the git a lot more than what I update the thread so check there for latest news.
Features
Split Bin file into relevant partitions
Split Tot file into relevant blocks and merge blocks into partitions
Display AP Header
Display GPT Header
Extract Header from Bin/Tot File
Features I like to implement (and probably won't get around to)
Extracting boot img (The tools currently available don't work in all cases and it's very easy to read the header since it's open source.)
Extracting ext4 partitions. So that it's easy to access the file. Theres already other tools that can do this so this isn't essential.
Mergeing tot partitions based on data from partitions itself and not GPT
Inject Alternate Data into partitions. I'll block access to X-loader,U-boot and GPT so that You can't kill your phone.
Source
https://github.com/Xonar/LGBinExtractor
Confirmed to work with
Quite a few phones.
I lost track of which ones work.
To check just run with -daph. You'll get file information if it works and either garbled data or an error message if it doesn't.
If your phones not supported follow the steps on git readme.
Thanks
SnowLeopardJB - for lots and lots of testing
navossoc - his tool that extracts kdz and wdb files
vim1 - D821 support
scotty755 - LGL22 support
tkawajir - L-04E and LG G Flex F340K support
If you feel I forgot to thank you, msg me and I'll add you.
If it can extract BIN files then yes. We believe the nandroid V30* of KU5900 that was supplied was incomplete. So If KDZ is converted to BIN and FLS (which we can), then extract contents of BIN, then you can have complete files without looking for Koreans and Chinese to relay that the nandroid was incomplete and can have untampered files.
xonar_ said:
Question to other Devs
Will you use a tool like this or am I wasting my time?
Is a tool like this allowed or would it be considered reverse engineering? (If its not allowed I'm going to stop IMMEDIATELY)
Click to expand...
Click to collapse
Yes I will. If I myself can build a program to extract this EFI partition..
It is reverse engineering, but I don't know if it's legal or not (in this case), but for me it's legal as I'm considered this to educational purpose
Many others tool was created to have purpose like this, for example http://psas.revskills.de/?q=node/5
-CMIIW-
I've attached an image of the system partition of the V20E_00 for you guys to see.
I am going to download the v30H_00.kdz today. So I'll keep you posted about how the extracting goes. I probably won't have time to check it out until the weekend so please don't hold your breath.
I've only recently managed to find the necessary information about the ext4 file system to integrate the functionality into my tool. For now Ext2Read can extract the ext4 file system just fine. I'll add that somewhere over the weekend (Provided something doesn't come up).
Could you as soon, as you are able to unpack it fully maybe upload a complete backup of the system partition and also system2, cause we think, that in the nandroid there are some files missing and we need those, to probably be able to boot that system. Great job btw
Thanks for the positive feedback.
I am getting the v30h_00.kdz in a few hours (I got a friend to download it for me, I don't have that much cap ).
There is no way I will be able to upload the file since it will be big but if it works I'll post the tool and how to do it.
GitHub is giving me an error : "Page did not respond in a timely fashion". I am going to try again tonight to post the source.
I already tried to extract the bin files, but I didn't see any pattern to know where start or ends a partition.
Some partitions you can identify by it's header and try to extract the file size from there (i did that with recovery.exe).
If you know for sure the partition name and the address, I can improve the recovery.exe to patch always the right partition.
So, what is the trick?
[]'s
navossoc said:
I already tried to extract the bin files, but I didn't see any pattern to know where start or ends a partition.
Some partitions you can identify by it's header and try to extract the file size from there (i did that with recovery.exe).
If you know for sure the partition name and the address, I can improve the recovery.exe to patch always the right partition.
So, what is the trick?
[]'s
Click to expand...
Click to collapse
The first meg of the file contains the names of the data blocks size on file,size on disk and where they start on file. I'll post exactly how it is set out later.
The data blocks aren't only partitions though for example the first one is the GPT header with it's corresponding entries and also some blocks are empty.
I recognized the start the two partitions from your tool.
Sent from my LG Optimus Black
xonar_ said:
The first meg of the file contains the names of the data blocks size on file,size on disk and where they start on file. I'll post exactly how it is set out later.
The data blocks aren't only partitions though for example the first one is the GPT header with it's corresponding entries and also some blocks are empty.
I recognized the start the two partitions from your tool.
Sent from my LG Optimus Black
Click to expand...
Click to collapse
You are talking about the first 1MB from BIN? right?
They are using little endian or big endian to represent the numbers?
The name of the sections I already knew, but never found the initial offset.
I will try to take a look later.
[]'s
navossoc said:
You are talking about the first 1MB from BIN? right?
They are using little endian or big endian to represent the numbers?
The name of the sections I already knew, but never found the initial offset.
I will try to take a look later.
[]'s
Click to expand...
Click to collapse
Yes the BIN. They are using little endian. All the offsets and sizes are in LBA's (512 bytes in this case) with LBA 0 starting at 0x100000.
Sent from my LG Optimus Black
Source of Bin Fls Extractor (So far)
GitHub isn't working out as planned. The client stopped downloading in the middle and I don't want to waste more cap so here is the source as an attachment.
This is still a work in progress and is only confirmed to work with v20E_00 South Africa.
Linux users can just mount the *.img file of system to access it. Windows users have to use a tool like Ext2Read. Mac users I'm not sure : Google it.
EDIT : I wont be able to get the v30 kdz for another day unfortunately. Feel free to try and change my tool to work with it.
EDIT2: These sources are old. I'll upload my fixed ones later. Reads in chunks and works on P970 and KU5900 ( I don't have any other files to test it with but it should work with almost all BIN files extracted from kdz files )
xonar_ said:
GitHub isn't working out as planned. The client stopped downloading in the middle and I don't want to waste more cap so here is the source as an attachment.
This is still a work in progress and is only confirmed to work with v20E_00 South Africa.
Linux users can just mount the *.img file of system to access it. Windows users have to use a tool like Ext2Read. Mac users I'm not sure : Google it.
EDIT : I wont be able to get the v30 kdz for another day unfortunately. Feel free to try and change my tool to work with it.
Click to expand...
Click to collapse
Nah! The damn trick was the 512 bytes + 0x100000 base.
I never thinked about it...
I take a look at your code, I understand the whole concept now.
I have successfully extracted the system.img and system2.img from the V30H_00.kdz
Nice, maybe later I can do some modifications on recovery.exe, so they can find always the correct partition for recovery.img. (without the user choose one)
[]'s
navossoc said:
Nah! The damn trick was the 512 bytes + 0x100000 base.
I never thinked about it...
I take a look at your code, I understand the whole concept now.
I have successfully extracted the system.img and system2.img from the V30H_00.kdz
Nice, maybe later I can do some modifications on recovery.exe, so they can find always the correct partition for recovery.img. (without the user choose one)
[]'s
Click to expand...
Click to collapse
Nice! Great job you guys. :good:
navossoc said:
Nah! The damn trick was the 512 bytes + 0x100000 base.
I never thinked about it...
I take a look at your code, I understand the whole concept now.
I have successfully extracted the system.img and system2.img from the V30H_00.kdz
Nice, maybe later I can do some modifications on recovery.exe, so they can find always the correct partition for recovery.img. (without the user choose one)
[]'s
Click to expand...
Click to collapse
can you upload system files asap?
George Jetson said:
can you upload system files asap?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=31443301&postcount=270
Thanks to navossoc there
navossoc said:
Nah! The damn trick was the 512 bytes + 0x100000 base.
I never thinked about it...
I take a look at your code, I understand the whole concept now.
I have successfully extracted the system.img and system2.img from the V30H_00.kdz
Nice, maybe later I can do some modifications on recovery.exe, so they can find always the correct partition for recovery.img. (without the user choose one)
[]'s
Click to expand...
Click to collapse
That's good news.
I won't be able to work on the program during the rest of this week. With the system files extracted there's nothing that needs to be urgently done.
Next Step is to to try and build the BIN from other files. I think I can improve on your recovery.exe to add su binary and apk aswel (Might take a bit longer since I need to extract the ext4 partition, add su then put it back together )
Well, it's just a beta, because it use too much ram to write the files.
I need to read the file in chunks, but, for now it's a good prototype, we can using it.
extract.7z
Code:
CRC32: 2199d10f
MD5: 5b8d8031ff5d66ec2832d182e98505be
SHA-1: b6d729a20d4370e25ebc4eddfc27e25673b1d2f2
To use the tool is just run...
Code:
extract.exe filename_AP.bin
It should work on any bin file, tested on P920, P970 and KU5900.
Please report any error.
[]'s
Thanks navossoc its working well on ginger p970 bin file.
Great stuff thanks alot! You to make a great team.
Sent from my LG-P920 using xda app-developers app
Now how can we make a new bin file with that img files?
Can those of you who have been successful rooting the Sprint LG G4 post the MD5 hash for LS991ZV5.tar.gz?
I can't finding it at the download site or the [Root] thread and would like to verify it with a know good.
Sorry for being redundant but I'm under a time crunch atm.
Well, out of time. I guess I'll be without root for a while more :crying:
Thanks
I'll get around to it when I can get back to a PC
http://forum.xda-developers.com/showthread.php?p=62062521
Sent from my LGLS991 using Tapatalk
Ok.... I'm lost and i apologize but copy the command where?
MDHarper said:
Can those of you who have been successful rooting the Sprint LG G4 post the MD5 hash for LS991ZV5.tar.gz?
I can't finding it at the download site or the [Root] thread and would like to verify it with a know good.
Sorry for being redundant but I'm under a time crunch atm.
Click to expand...
Click to collapse
Use my android file host
http://forum.xda-developers.com/showthread.php?p=62062521
Sent from my LGLS991 using Tapatalk
Shell after connecting to the appropriate COM port when your phone is in download mode
Jessooca said:
For Sprint... 53FAB3EF537C3917AB96AA219D1AC32C (be sure you extract the img file from the tgz file you downloaded before copying it to the root of your INTERNAL and do NOT rename it) After you've extracted it, (use 7zip, winrar, etc) you can verify your # using this http://onlinemd5.com/ select "choose file" at the top and select your IMG file that's extracted from that tgz file and you should have the same # as mine. It should take about 3 minutes
Click to expand...
Click to collapse
I'm not sure the md5 value you're showing is correct, because the checksum generator in the link you posted has a max file size of 4GB and the image file size is 4.565,499,904 bytes.
ES File Explorer shows an MD5 checksum of bba2f6e3342db0ca171ddfde8286c0da for that file on my phone.
Jessooca said:
The Sprint G4 ls991zv5.tar.gz file is less than 2gb.
Click to expand...
Click to collapse
We're not talking about the ls991zv5.tar.gz file, we're talking about the system.rooted.LS991ZV5.img file.
The MD5 checksum value you posted is the one generated for the system.rooted.LS991ZV5.img file by the MD5 & SHA1 Hash Generator found in your link. Go ahead and try it again with that same file and you'll get the same value you posted. What I'm saying is that value is wrong because the file is too big for that Hash Generator to handle.