Database Develop

Rogers V20C KDZ, Megatron root exploit, torrent file HERE !

Most of you should probably know how to use torrent files I would assume, so here are a couple of links. Everything I found on stock roms for thrill were dead links......This is Not ! Will be alive for a long time...
This link is a very large file....It has all flash tools, drivers, V20C kdz, V18E.fls, V10E.fls, Super 1 click, Megatron, thrill recovery manager, Froyo_GB file....Instructions, links, etc..
File size is about 862.8 MB
http://extratorrent.com/torrent/2635438/
This link is for V20C KDZ file, GB Root exploit, Drivers and Instructions ONLY !!
File size is 429.75mb
http://extratorrent.com/torrent/2633977/
Thank You and Please Seed after downloading
Dman

SUPER quick question.
Why would a torrent be needed for this? :?
A typical .kdz file is about 300 - 450 MB.
The flashing tools I provide are less than 50 MB as well...
Also, this is the wrong section. :?

Super long answer
No reason that a torrent is needed i guess.....
Except for the fact that there are so many dead links
to all of these files... Mediafire, megaupload etc... are so
unreliable. Even in these forums there are links to the V20C kdz
that are "dead". Stock Froyo rom/baseband was almost impossible
for me to find.
This to me is just an easy reliable way to have everything in 1
package. Alot of the upload sites that I found also had limits
to the package size, torrents do not. Torrent files download
much faster than direct downloads if the file is healthy and
people seed as they should !! The second torrent has been
downloaded about 40 times already ! So apparently it is being
used and is necessary. Granted, the first file is rather large
and should probably be redone as i left Compressed and
un-compressed duplicate folders in the torrent, and it is probably
7-800 Mb larger than it needs to be.....
If you still see no reason for this, I will take them down.. LMK
Thanks,
Dwayne

I understand it, however, my Mediafire is a payed account, so files will stay up.
You can keep the files up if you'd like. I just don't think the 1.8GB file is a reasonable download, when the tools I provide and download .kdz file is about 4 times smaller.

You are correct, I am going to modify the first link, as it is an unnecessary file size. but, does not include just 1 Kdz, it includes stock Froyo, V20C Kdz, recovery manager, Flash Tools, Megatron, Super 1 click, links etc.... But yes I doubled the filesize by not deleting all of the Zip files first.... should be bout' 900 MB
Also, props on your biohazard Rom, I am running this on the V20C, and it is so fast and stable it is not even funny. Battery lasts me 18 hours of heavy use...WI-Fi, Angry birds, texting and phone calls... A+++ for Lestat
As well, I am not really talking about your account, as I found all links worked.
Mostly links like this http://forum.xda-developers.com/showthread.php?t=1270832 were hard to use because everything is dead and should be modified or taken down. Please check it out !!
Thanks again,
Dwayne

dwaynedman said:
You are correct, I am going to modify the first link, as it is an unnecessary file size. but, does not include just 1 Kdz, it includes stock Froyo, V20C Kdz, recovery manager, Flash Tools, Megatron, Super 1 click, links etc.... But yes I doubled the filesize by not deleting all of the Zip files first.... should be bout' 900 MB
Also, props on your biohazard Rom, I am running this on the V20C, and it is so fast and stable it is not even funny. Battery lasts me 18 hours of heavy use...WI-Fi, Angry birds, texting and phone calls... A+++ for Lestat
As well, I am not really talking about your account, as I found all links worked.
Mostly links like this http://forum.xda-developers.com/showthread.php?t=1270832 were hard to use because everything is dead and should be modified or taken down. Please check it out !!
Thanks again,
Dwayne
Click to expand...
Click to collapse
Now that sounds about right. Is the stock Froyo a .kdz file, .bin file, or a ClockworkMod .zip?
Thank you! I spent forever on it. Haha.
Oh! I have that file hosted as well. I suppose I should add that to my Guides/Tools thread.

Stock Froyo is A .bin .FLS file..
I also have one that says "stock froyo update rooted" and
has some kind if an .IMG file in it... so you know what that is ??
Thanks,
Dwayne

dwaynedman said:
Stock Froyo is A .bin .FLS file..
I also have one that says "stock froyo update rooted" and
has some kind if an .IMG file in it... so you know what that is ??
Thanks,
Dwayne
Click to expand...
Click to collapse
Ahh. I have no idea how to use a .bin & .fls file.
I like .kdz files a lot better.
The boot.img file contains the kernel.

links don't work... for me at least...

Yeah, something happened at Extratorrent this afternoon. There server went down or something to that affect. All links should be back up by tomorrow.
Thanks,
Dman

dwaynedman said:
Most of you should probably know how to use torrent files I would assume, so here are a couple of links. Everything I found on stock roms for thrill were dead links......This is Not ! Will be alive for a long time...
This link is a very large file....It has all flash tools, drivers, V20C kdz, V18E.fls, V10E.fls, Super 1 click, Megatron, thrill recovery manager, Froyo_GB file....Instructions, links, etc..
File size is about 862.8 MB
http://extratorrent.com/torrent/2635438/
This link is for V20C KDZ file, GB Root exploit, Drivers and Instructions ONLY !!
File size is 429.75mb
http://extratorrent.com/torrent/2633977/
Thank You and Please Seed after downloading
Dman
Click to expand...
Click to collapse
The main problem I see with using a torrent file is that not many people seed them. I personally will not seed a torrent file as I will not use my bandwidth to allow others to download. I prefer Direct Download links myself

That is a good point, but I did put these up around a time when alot of direct download links were not working. People were asking where to download them so I decided to help.
On a large file, it takes forever unless you pay for direct download services.
On a torrent file you do not have to be a premium member to take advantage of
full download speed capabilities.
Just a matter of preference I guess, as I can seed out at almost 1 Mbps and not be punished for using bandwidth.
Thanks,
dwayne

The Dark Lestat said:
Ahh. I have no idea how to use a .bin & .fls file.
I like .kdz files a lot better.
The boot.img file contains the kernel.
Click to expand...
Click to collapse
The .bin and .fls files have to be flashed using SmartFlash. .kdz files are just the .bin and .fls packaged together and encrypted. Since the .bin and .fls files are unencrypted, you can modify the firmware as you see fit using WinHex and flash it using the Smartflash tool.

dwaynedman said:
That is a good point, but I did put these up around a time when alot of direct download links were not working. People were asking where to download them so I decided to help.
On a large file, it takes forever unless you pay for direct download services.
On a torrent file you do not have to be a premium member to take advantage of
full download speed capabilities.
Just a matter of preference I guess, as I can seed out at almost 1 Mbps and not be punished for using bandwidth.
Thanks,
dwayne
Click to expand...
Click to collapse
That's great that you have that kind of bandwidth available. I'm supposed to have up to 1Mbps up but only see 512Kbps at most uploading. I can download like a rocket but up is really slow for me. I like to use Dropbox for posting Direct Downloads. You can download pretty quick without having to pay.

Thanks,
Never heard of Dropbox. I will have to check it out.
Peace

[TOOL]LG Bin Firmware Extractor

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?

checksum for ovation downloads

I'm experiencing the set_perm error 7 while trying to install CM 10.1 on my brand new Nook HD+. Others have indicated that this is caused by file corruption.
I've used HashTab to verify that the file was correctly copied onto the microSD, but I don't have any server-side hashes to check the download.
I've downloaded 0605 once and 0612 several times. Unfortunately I didn't keep the older download to compare hashes, I'm in the process of yet another download.
But it would be really nice if someone could post the MD5 or SHA1 or other common hash of these large ROMs.
http://forum.xda-developers.com/showthread.php?t=2263553
BTW, for 0612 I have two downloads with these identical hashes:
CRC32: 76BDACB5
MD5: 1BBB78B46234098034E5827B1103B424
SHA-1: 43AF5C88BC32488646629549B1FAE8D3107F5586
(A mirror not hosted in Russia would be nice too, but hashes are essential)

Request : XZ1 Settings apk

Hey,
Could someone please upload the apk file for system settings. It can be found in system/priv-app/settings/

korom42 said:
Hey,
Could someone please upload the apk file for system settings. It can be found in system/priv-app/settings/
Click to expand...
Click to collapse
The XZ1c version is 40MB in size deodexed. Once zipped, it's about 14MB so I can attach it to a post if you want.
It's the XZ1c version from FW 47.1.A.2.324.
You can also get it yourself by downloading the firmware you want with XperiFirm, then extracting the system sin file with UnSIN, then opening the resulting ext4 image with 7zip.

pbarrette said:
The XZ1c version is 40MB in size deodexed. Once zipped, it's about 14MB so I can attach it to a post if you want.
It's the XZ1c version from FW 47.1.A.2.324.
You can also get it yourself by downloading the firmware you want with XperiFirm, then extracting the system sin file with UnSIN, then opening the resulting ext4 image with 7zip.
Click to expand...
Click to collapse
I know how to extract it from firmware if I were home but, with my current limited and super slow data plan downloading +2gb file is no big deal .. so I appreciate if you can zip it and share it

korom42 said:
I know how to extract it from firmware if I were home but, with my current limited and super slow data plan downloading +2gb file is no big deal .. so I appreciate if you can zip it and share it
Click to expand...
Click to collapse
Attached as requested.

Is this an OTA update?

I've been trying to find the URL for the failing update for my rooted Moto G7 plus.
I've taken a log and did find a large file but it is a lot smaller than a normal rom, about 100 Mb.
Could this still be an OTA update?
Screenshot of the contents attached.
Can I just go ahead and install this with twrp?

a ota is usually .zip where did you get those file?

This is a zip, it is just not named ".zip" , I took the screenshot of the contents of the zip.
For reference, here is the line where I found the download
Code:
12-06 14:19:06.869 5831 14719 D OtaApp : UpdaterEngineHelper:applyPayload, applying payload with downloadUrl = [url]https://dlmgr.gtm.svcmot.com/dl/dlws/1/download/*lots-of-stuff*%3D[/url] offsetvalue = 9258 fileSize = 107713236
(I took a part of the letters out as it was super long)

SvenHee said:
This is a zip, it is just not named ".zip" , I took the screenshot of the contents of the zip.
For reference, here is the line where I found the download
(I took a part of the letters out as it was super long)
Click to expand...
Click to collapse
I think you would be better off just flashing the full firmware
https://mirrors.lolinet.com/firmware/moto/ocean/official/
Sent from my mata using XDA Labs

Thanks for that mirror, I had not found it yet!
It seems that I am on the latest firmware that is available there (my phone is lake, not ocean)