[APP] kTool for the SGS3 - easiely backup/restore kernel, recovery, EFS - Galaxy S III Themes and Apps

Hey ho
kTool - a little helper app some might know from the S2 - is now fully compatible with the Galaxy S3
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
For those who don't know about it, here's a quick rundown of the features:
Dump current kernel and recovery
Flash kernel from /sdcard/zImage
Flash recovery from /sdcard/recovery.bin
Backup EFS
(as raw .IMG dump and as .TAR archive)
Check/Verify EFS backup (i.e. compare to "live" EFS)
Restore EFS from either .IMG or .TAR
Open stock update .TARs and flash from from it:
- Modem Firmware
- PARAM.LFS
- Kernel
- (Recovery to be added in a later update)
Reboot device
- normally
- to recovery
- to download mode
And here's the original release thread in the S2 section:
http://forum.xda-developers.com/showthread.php?p=18652863
Find more details (and screenshots) and answers in that thread, however if you got more questions or suggestions you can post them in this thread as well
You can grab the app from Google Play (free):
https://play.google.com/store/apps/details?id=net.hellcat.droiddev.ktool
Also, as there will be as many different variants of the S3 as there are for the S2, it might happen that you got an S3 but the app refuses to run.
In that case, please send me (via PM, email or posted in this thread) a screenshot of the "Incompatible Device" dialog and I'll update the app
Hope you like it.

Thanx M8.
How 'bout a new kernel. In Dev. Maybe.. lol
Seriously great work used it on my gs2.

Wow,
Great Job, thank you very much.
Now everything on air for SGS3,
Now I can test any Kernel, since I have backup of the stock kernel to go back:good::good::good:

Perfect
Sent from my Galaxy SIII

This doesn't work for the ATT Galaxy SIII. It goes through successfully but says the nv_data.bin is Not found in backup.

justinblaine23 said:
This doesn't work for the ATT Galaxy SIII. It goes through successfully but says the nv_data.bin is Not found in backup.
Click to expand...
Click to collapse
Hm.... that's weird....
Could you do me a favour and open a shell/terminal on the phone and paste me the output of the "mount" command?
Also what are the sizes of the created "efs.img" and "efs.tar.gz" files?
It's the i747, isn't it?

Yes the 747 will terminal emulator work?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Yes, will work perfectly
Just run "mount" and make a screenshot, that's the most easiest way, I think.

The file sizes are both real small..
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Sorry that's hated to read.. the tar.gz is only 29.00B
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

And also I'm rooted but no cwm or roms yet. Just info in case it helps.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Oooooh, I already spotted a few things!
OK, that helps a lot already, thanks!
I'll prep a testbuild and if you don't mind you can test it?
Did it fail the check for the .TAR as well, because as far as I can see, the .TAR backup schould have worked.
// EDIT
Hmm, the next big question is, is this for all US variants or only the AT&T one.... guess I'll need to wait till someone with one of the other variants shows up and will take them out again for now....
// EDIT 2
Ouch, and what about kernel, recovery, modem and all the other partitions.... gotta find a way to figure out those too....
// EDIT 3
And me again....
Could you please try the following command in the terminal as well:
Code:
su
ls -al /dev/block/platform/dw_mmc/by-name
If it gives a list of entries, please paste it to me Thanks!
// EDIT 4
OK, finding clues for more and more differences.... why Samsung, oh why do you do this....?
I could also use the output of
Code:
su
ls -al /efs
*sigh*

Can i flash zImage format file in sgs3?
This is the file backed up by kTool....
Sent from my Galaxy SIII

Size of efs backup on sgs3 int. is suspiciously small...
Sent from my Galaxy SIII

sebarkh said:
Van i flash zImage format rolę in sgs3.
This is the file backed up by kTool....
Click to expand...
Click to collapse
Uhm, sorry.... WHAT?

sebarkh said:
Size of efs backup on sgs3 int. is suspiciously small...
Click to expand...
Click to collapse
Those sizes are OK.

When I flash back stock backed up zImage kernel, on any custom kernel, the recovery flashed along with that custom kernel will be retained? can I use that recovey with stock kernel?

Yeah.
The S3 uses a seperate recovery this time (unlike the S2, where the recvoery was part of the main kernel).
So if you flash a kernel, the recovery will remain unchanged.

OK, I think I found a partition layout for the i747 - maybe someone can confirm this being correct?
http://forum.xda-developers.com/showpost.php?p=27937117&postcount=13

I'm sorry, I went to sleep, I'll try to tun the commands here real quick before work..give me a bit
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Related

[ROM][11/01/11] [1.1] The Fast and The Tabious

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello Guys!
This is my Custom ROM for the Galaxy Tab!
Its based on the european Firmware JME but i did the following changes:
- System and Framework completely deodexed
- System and Framework completely zipaligned
- Added Root and BusyBox
- LauncherPro as default Launcher
- build.prop Tweaks
- App Widget Picker
- Removed Maps and gMail (u can reinstall from market) more space on /system for the extra Apps
Thanks to this, you have now much more RAM available, and it runs pretty fast!
u can find the update in the attached files section
UPDATES:
1.1 - CAMERA FINALLY FIXED
1.0.1 - fixed missing camera app
1.0 - Release
Coming in further Releases (my plan ) when my bootloader gets unlocked:
- overclocking
- kernel optimisations
- custom theme
- EXT4
- Gingerbread???
apply the update by putting the files in the folder "updateX.X" (X.X stands for the version number and u need to create it) and then run the script via terminal emulator or adb shell (sh /sdcard/update/xxx_update.sh) xxx is replaced by version or update name
Currently known Bugs:
- camera app is missing but u can use camera apps from android market - fixed in newest release
THIS DOESN'T CONTAIN THE SIGNED BOOTLOADERS, just like Rotohammer's releases
it only contains a signed zImage but, as u know, u can revert this
Install with Heimdall or Odin, recommended from a JMx Firmware (JJx and JKx havnt been tested yet but u can try)
I'll update this rom, whenever there are bugs, stability issues and wishes from you!
|Download (Heimdall)|
Great. Downloading now. Will flash tomorrow.
Sounds great. But why add the signed zimage at all. Is there a way to load this without the zimage?
Can you install it with ODIN ?
Do you need a full wipe ?
P_
heythorp said:
Sounds great. But why add the signed zimage at all. Is there a way to load this without the zimage?
Click to expand...
Click to collapse
i dont know exactly, but i think u need the newer kernel for JMx Releases! But u can try to flash only the factoryfs.rfs file inside the 7z archive, but i dont guarantee that it will work!
@ guy above me
i can make an odin package tomorrow, if u want so!
Sent from my GT-P1000 using XDA App
What version will this work with? Sprint tmo att vzw or any and does it replace the modem.bin
Sent from my SPH-P100 using XDA App
+1 for Odin install.
+1 for Odin version , can you post some screen or a video to see your rom . Differences from Roto- JME? Works on generic EURO tab? Thank you
+1 for Odin pls
Sent from my GT-P1000 using Tapatalk
cant wait to try out this rom
i tried flashing with heimdall and it just fails every time.
edit:
got it to work. will post up results after i used it a lil. thanks again!
ayman07 said:
i tried flashing with heimdall and it just fails every time.
edit:
got it to work. will post up results after i used it a lil. thanks again!
Click to expand...
Click to collapse
Heh. Keep the updates flowing through Twitter on how you're finding it...
did you forget to include the camera app cuz its no longer there?
@htnprm definitely
Flashed on my T-Mobile Tab and am so happy to be rid of the Samsung Home.
Looks and works great so far!
Landroid said:
i can make an odin package tomorrow, if u want so!
Click to expand...
Click to collapse
what about a CWM zip? flash on the go!
ayman07 said:
did you forget to include the camera app cuz its no longer there?
@htnprm definitely
Click to expand...
Click to collapse
Just flashed and confirmed, missing camera app. And trying to select the camera in the Gallery app forces closes
great. heimdall is up. i picked the zimage but for what button / option do i select for the .rfs file?
in other words, is this right?
[edit] never-mind. figured it out by following steps on here: http://forum.xda-developers.com/showthread.php?t=878686
problem now is there isnt any arabic support in this rom. may hold back on flashing it.
Sod Odin and Haimdall. Any chance of an update.zip for flashing in recovery, given that we now have a usable, stable recovery (chainfire's).
Frustu said:
+1 for Odin version , can you post some screen or a video to see your rom . Differences from Roto- JME? Works on generic EURO tab? Thank you
Click to expand...
Click to collapse
Quote.
Thanks!
any screenshot's?

App2zip

Go check out this app in the market.
It creates a zip of your apps that you can flash in cwm when you wipe phone. I know for a fact it doesn't work on Eugene's cm7 but maybe it works on other Roms. Test it first
LINK: https://www.dropbox.com/sh/m2gpv44zoas0odp/ZIFjxPMHFU/scd.app2zip-1.apk
Sent from a badass galaxy.
nringwood SGS2 said:
Go check out this app in the market.
It creates a zip of your apps that you can flash in cwm when you wipe phone. I know for a fact it doesn't work on Eugene's cm7 but maybe it works on other Roms. Test it first
LINK: https://www.dropbox.com/sh/m2gpv44zoas0odp/ZIFjxPMHFU/scd.app2zip-1.apk
Sent from a badass galaxy.
Click to expand...
Click to collapse
GooglePlay direct link....
https://play.google.com/store/apps/details?id=scd.app2zip&feature=search_result#?t=W251bGwsMSwxLDEsInNjZC5hcHAyemlwIl0.
For addictive flashers like me, this application is a God send!!
There are some bugs but here's the way to fix it:
0. Install the APPS2ZIP application from the link above.
1. Get a root file browser
2. Copy the "update-binary" file found in any T989 roms ZIP file \meta-inf folder.
3. Paste/overwrite the file here: /data/data/scd.app2zip/files
and then run the APPS2ZIP to create the update.zip file.
I have tested this file and it works great!! Its like flashable Titanium Backup restore !!
Well looking here we can make it work. Ill be testing on my lunch break!
Sent from a badass galaxy.
It restore data and all?
Sent from my SGH-T989
Not to sure. Will give it a try and find out. If it doesn't titanium will restore app data way quicker once they installed.
Sent from a badass galaxy.
Hmm not finding app2zip where you specified? I'm on cm7.
Sent from a badass galaxy.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yes, it restores data as well. Infact its the bad thing, I wanted it to have the option of just restoring the app and no data.
Not sure how the folder structure for CM7 is, I tested it on BeastMod5. Can you look in /data location. It should be there.
virajss said:
Yes, it restores data as well. Infact its the bad thing, I wanted it to have the option of just restoring the app and no data.
Not sure how the folder structure for CM7 is, I tested it on BeastMod5. Can you look in /data location. It should be there.
Click to expand...
Click to collapse
You could always clear the apps data before creating the zip.
Sent from my SGH-T989 using Tapatalk 2 Beta-5
Output zip file already exists is what I get when trying to.create a zip after updating binary
Sent from a badass galaxy.
nringwood SGS2 said:
Output zip file already exists is what I get when trying to.create a zip after updating binary
Sent from a badass galaxy.
Click to expand...
Click to collapse
Delete the update.zip file located at the root of your internal memory space and then try again.
Works. Thanks guys
Sent from a badass galaxy.
Omg awesome, works great. Why wasn't this around forever? This should be integrated into cwm.
Sent from my SAMSUNG-SGH-I727 using xda premium
defconoi said:
Omg awesome, works great. Why wasn't this around forever? This should be integrated into cwm.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
+1,000,000
I can't count the hours I spent re-setting up all my apps after flashing. I never want to use Ti backup since I screwed it up once. This seems much easier for me.
EDIT - What's the difference between free and paid? Usually there is a change log. Or is it just a donation version?
Not to sure. All I know is that this thing is awesome haha. An integration with cwm would be cool
Sent from a badass galaxy.
Any of you guys hhaving the issue of when I install the zip and reboot. I Click on the app and it fc's?
Sent from a badass galaxy.
Run Fix Permissions.
See that's what I thought it was but I fixed them a couple times and it still fc's.
Sent from a badass galaxy.
Anyone know if this works with ics roms?
Sent from my SAMSUNG-SGH-I727 using xda premium
I used it to build a zip and also flashed the zip on ICS. So, I'd say it does work with ICS Roms. Way awesome!
Sent from my SGH-T989 using Tapatalk 2

clockwork mod...1970?

anyone know a workaround for this? the bad thign about it is I often will flash multiple roms/have different backups and forget which one is which...which is the most recent etc. Why does it date as 1970 even though my clock and everything is fine? Would manually setting the clock (vs from the network) resolve this issue?
I started using rom manager to initiate backups. The date comes out correct if you do that.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
heaiser said:
I started using rom manager to initiate backups. The date comes out correct if you do that.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I was using rom manager premium and my date want correct at all, cwm is just a huge waste of time and not to mention the latest version is as slow as molassis in the winter! Use twrp its full touch and you can set tell backup name for each backup
Sent from my SGH-I747M using xda premium
zetsui said:
anyone know a workaround for this? the bad thign about it is I often will flash multiple roms/have different backups and forget which one is which...which is the most recent etc. Why does it date as 1970 even though my clock and everything is fine? Would manually setting the clock (vs from the network) resolve this issue?
Click to expand...
Click to collapse
I haven't been able to find a version of CWM that doesn't do this for this phone. All I've been doing is just renaming the backup once it's complete, usually just to something like CM10_BACKUP_NOV16 or STOCK_BACKUP_NOV16. Can be renamed from your phone's file manager.
heaiser said:
I started using rom manager to initiate backups. The date comes out correct if you do that.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
As he said, you must initiate the backup in ROM Manager in order to have the correct date, or a custom name for your backup.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Galaxy S3
GladdBag said:
I haven't been able to find a version of CWM that doesn't do this for this phone. All I've been doing is just renaming the backup once it's complete, usually just to something like CM10_BACKUP_NOV16 or STOCK_BACKUP_NOV16. Can be renamed from your phone's file manager.
Click to expand...
Click to collapse
Have you tried to use the renamed backup , i have read and found i get incorrect md5 file , and it would not flash
Sent from my SGH-I747 using xda premium
zetsui said:
anyone know a workaround for this? the bad thign about it is I often will flash multiple roms/have different backups and forget which one is which...which is the most recent etc. Why does it date as 1970 even though my clock and everything is fine? Would manually setting the clock (vs from the network) resolve this issue?
Click to expand...
Click to collapse
lol your still using clockwork mod? hahah twrp is whats up man
ragzdincs said:
Have you tried to use the renamed backup , i have read and found i get incorrect md5 file , and it would not flash
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Be cautious of spaces in your file name. Use hyphens or periods rather than spaces.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
ragzdincs said:
Have you tried to use the renamed backup , i have read and found i get incorrect md5 file , and it would not flash
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
There is a tool somewhere which will regenerate the MD5 sum after you rename the folder. Maybe someone else, or a search, could point you in the right direction.
It might have been Rom Toolbox in the market by JRummy
amzi said:
lol your still using clockwork mod? hahah twrp is whats up man
Click to expand...
Click to collapse
I was using twrp 2.2 for a while and some roms had problems flashing, especially ones with graphical installers like Ariel. I updated to the latest clockwork mod recovery and things have been fine ever since. twrp updated since then so the issues might be resolved but I haven't seen any reason to switch back. I am a linux admin don't need a touch based interface on my recovery environment.
This is BETTER than a workaround:
Online Nandroid Backup
WHY?
- dates are correct
- no need to boot into recovery mode to perform backup
- fast and organized, and easy to rename backups
- it's under good steady development for new FEATURES.
- auto updating of script
(There is a script and a gui dev...make sure to thank them both)
(You don't need CWM to create backup, but you do need CWM to restore)
Date issue comes from device issue
According to the TWRP2 page for the AT&T GS3,
Date/time in recovery will always be wrong due to a device issue that cannot be fixed.
Click to expand...
Click to collapse
I assume that this is what is effecting my CWM backup names. Sounds like some to just live with and workaround....

Does anyone have a CWM Flashable version of the T999VVLDLL1 Jelly Bean Modem?

As you all know, the T999V variants and T999 can not flash the radio/modem files interchangeably between the two.
As such, does anyone have a copy of the Modem? I'm currently running an JB Rom with an ICS Modem and getting some really sad speeds. I checked the Sticky here:
http://forum.xda-developers.com/showthread.php?t=1880987
and it is currently not posted.
If anyone is using this Modem, I believe you could follow the steps in this guide to a certain extent:
http://forum.xda-developers.com/showthread.php?p=27584839#post27584839
Thanks in advance to all that reply!
after further googling, I think all I need is some kind soul to extract the modem.bin from their phones. Afterwards, I think I have enough tech savvy to repackage the Modem.bin into a CWM ZIP file for public consumption.
Please follow the steps using either ADB or Terminal on your phone to extract the modem and then post it here. Thank you!
Requirements:
1. CWM Recovery & root (Thanks Chainfire!)
2. ADB setup and know how to use it! or Terminal Emulator app
3. Samsung KIES drivers installed
4. Power on device, Enable USB debugging
**If you don’t how to do above, then XDA forum search and Google is your friend**
Steps:
1. Dump your current modem onto your internal sdcard
# Run Terminal Emulator app and input steps b -> e
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
OR
# Connect USB to PC & run PC Command Prompt (CMD) & input steps a -> e
a) adb shell
b) su
c) dd if=/dev/block/mmcblk0p7 of=/sdcard/modem.bin bs=4096
d) exit
e) exit
Nobody sent me anything, so I extracted the modem.bin file from a root66 kies odin file:
http://forum.xda-developers.com/showthread.php?t=1771687
then I created this zip file using information from this thread:
http://forum.xda-developers.com/showthread.php?t=1880987
and now...
here's the modem:
https://anonfiles.com/file/bb0622d45bd00877b80bc18ab8802ef5
Cheers!
MegaMan X said:
Nobody sent me anything, so I extracted the modem.bin file from a root66 kies odin file:
http://forum.xda-developers.com/showthread.php?t=1771687
then I created this zip file using information from this thread:
http://forum.xda-developers.com/showthread.php?t=1880987
and now...
here's the modem:
https://anonfiles.com/file/bb0622d45bd00877b80bc18ab8802ef5
Cheers!
Click to expand...
Click to collapse
Just wanted to say thanks for doing this. I offered a month ago to do this for the thread if someone could help me figure out how to export the modem and I see you just sat down and figured it out. Thanks for the taking the time to do this, Support Canada! T999V forever!
How does this compare to VLLH2 in terms of battery life and performance?
Sent from my Nexus 7 using Tapatalk HD
DgtHorse said:
How does this compare to VLLH2 in terms of battery life and performance?
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
For me it's the same as the previous version. Maybe better signal if you are far from the tower.
Anyone know why does the updater script and radio file still say VLLH2 for the baseband file name? I'm assuming that it is just a left-over from reusing the packaging from the previous baseband zip.
Has anyone tried this and confirmed that it is truly VLDLL1 via the About/Phone menu?
File sizes are different -- new version is quite a bit smaller...so they are not identical...
I'm getting mixed inputs here. I have a t999 T-Mobile Galaxy S III and every time I update my Cyanogenmod ROM (which I've been doing for years) everything goes smooth but when the device boots up, it says "unknown" for the baseband version. If I flash the UVDMD5 radio it goes back to normal. But every single time I flash a new nightly this happens. Just wondering if this is a fix for that or if there I no fix. I rooted with the stock root injected .tar file just like I've done 3 separate times. This is the only one of my 3 S3's that has done this. I confirmed that it was NOT a t999L model before anything. Is there a possibility that this device could be a non t999 without saying it is? Or is it possible that this is a t999L model without showing that it is? I'm very lost here. Nobody seems to have the same issue as me. I've searched through hundreds of thread pages to no avail. Help please somebody?
I've no idea why it would do that. Sounds like some sort of Rom issue maybe? If it was anything but a T999, the md5 modem would not work btw. But I've never heard of thus before, so it could be some sort of unknown corruption somewhere in another partition. Purely a guess on that though.
If you Odin back to the LJA, or any other build does it still do this? Does it happen when you flash any Rom? Or just cm? If it's only cm, then I'd ask in the Rom thread. What about other kinds of flashes, such as kernels, recoveries and mods?
Sent from my SCH-I535 using Tapatalk 4

[TOT] LGE980 (ATT) Value Pack firmware

Howdy everyone!
Here's the latest firmware straight from LGE...
http://downloads.codefi.re/thecubed...IN_LGE980AT-01-V10k-310-410-JUN-07-2013-0.zip
Code:
$ md5sum BIN_LGE980AT-01-V10k-310-410-JUN-07-2013-0.zip
2044d4a4c3159cd0537caefdf1f6ee13 BIN_LGE980AT-01-V10k-310-410-JUN-07-2013-0.zip
It would seem that the zip file doesn't extract with some extractors. I'll re-zip it again here shortly and release a 'fixed' copy.
I have yet to test this file yet, so flash at your own risk!
It does appear that the bootloader is indeed different between the old and new firmware versions, however the difference is just the signature. The actual content of the bootloader's code sections has not changed.
There does indeed appear to be a different (newer?) kernel in the boot.img that's included:
Per the img file header:
Code:
NEW: 0x0066b5c0
OLD: 0x0066a058
Just a heads up in case anyone's wondering.
Also, turning this into a TWRP flashable image is going to be.. interesting.
do i use the same .dll as the old tot
phillip_viado said:
do i use the same .dll as the old tot
Click to expand...
Click to collapse
Yes, indeed.
Has anyone tried flashing this yet?
Sent from my LG-E980 using Tapatalk 2
Do I just flash this like I would a normal rom?
Timisone said:
Do I just flash this like I would a normal rom?
Click to expand...
Click to collapse
You flash it like your flashing the stock firmware using LG flash tool and DLL file
Sent from my LG-E980 using Tapatalk 2
I was looking at the features for the value pack. I think I will stick to what I have. I will wait for someone to port 4.2.2 over to this device. My birthday is tomorrow, maybe their will be some good news for me!!!!!
thecubed said:
Also, turning this into a TWRP flashable image is going to be.. interesting.
Click to expand...
Click to collapse
I managed to extract the system.img content using BinExtractor and some extra handling to put the different ??-system.img pieces back together into a 2.5GB partition.
turilo said:
You flash it like your flashing the stock firmware using LG flash tool and DLL file
Sent from my LG-E980 using Tapatalk 2
Click to expand...
Click to collapse
does we have to load the dll file separatly or it is include in the bin rom??
madmack said:
I managed to extract the system.img content using BinExtractor and some extra handling to put the different ??-system.img pieces back together into a 2.5GB partition.
Click to expand...
Click to collapse
Yeah, I catted them all together with:
Code:
cat *-system.img > system.img
truncate -s +500MB system.img
mount -o loop system.img /mnt/phonesystem
However, strangely enough there's nothing in /bin or /etc ... and I get lots of EXT4 errors in my kernel dmesg.
I believe it's possible that the LGBinExtractor doesn't like this TOT.. I'll extract it manually later today.
I've only compared the bootloader (ABOOT) to make sure nothing has changed, but I've yet to do that for rpm, tz, modem, and the SBL stack.
Once I've figured out what has changed (and what we should change) I'll put it all into an update.zip that we can flash from recovery.
thecubed said:
Yeah, I catted them all together with:
Code:
cat *-system.img > system.img
truncate -s +500MB system.img
mount -o loop system.img /mnt/phonesystem
However, strangely enough there's nothing in /bin or /etc ... and I get lots of EXT4 errors in my kernel dmesg.
I believe it's possible that the LGBinExtractor doesn't like this TOT.. I'll extract it manually later today.
I've only compared the bootloader (ABOOT) to make sure nothing has changed, but I've yet to do that for rpm, tz, modem, and the SBL stack.
Once I've figured out what has changed (and what we should change) I'll put it all into an update.zip that we can flash from recovery.
Click to expand...
Click to collapse
Hey thecubed I know your a busy man but thought I'd ask. Is it best to wait for your update zip or can we still flash the TOT in OP and root still should still apply I'm hoping?
Sent from my LG-E980 using Tapatalk 2
turilo said:
Hey thecubed I know your a busy man but thought I'd ask. Is it best to wait for your update zip or can we still flash the TOT in OP and root still should still apply I'm hoping?
Sent from my LG-E980 using Tapatalk 2
Click to expand...
Click to collapse
I'm fairly certain you can flash this TOT with LGFlash and still root... if it doesn't work, just grab the other TOT file and revert
I honestly didnt see enough features to update... anytine you update u take a risk of not being able to root or if they get smart and patch loki
Sent from my LG-E980 using xda premium
I took the OTA and rooted without issues.
I made a mirror to this file on my server, Download Link:
http://storagecow.tk/index.php?dir=Xda/LG+Optimus+G+Pro/Value+Pack+Firmware/ Server in USA (slower but cheaper)
http://storagecow.eu/index.php?dir=Xda/LG+Optimus+G+Pro/ATT+Value+Pack+Firmware/ Server In Canada (Fastest)
Here is a screenshot of the speed from the server I downloaded it from :/ and I have a GB connection.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
have flashed the update with lg flashtool.....everything went well except you will lose all date...so make a back-up wich i"ve done before......have rooted,went well too...
So once you finish people like me that are having a hard time with making the update cause im rooted. And haven't been able to use the flashtool due to the dam keys & unknown knowledge teritorry for it.
I'll be able to just put it on my external sd and use clockwork? And flash it.
Sent from my LG-E980 using xda app-developers app
WOW
InaruMejil said:
So once you finish people like me that are having a hard time with making the update cause im rooted. And haven't been able to use the flashtool due to the dam keys & unknown knowledge teritorry for it.
I'll be able to just put it on my external sd and use clockwork? And flash it.
Sent from my LG-E980 using xda app-developers app
Click to expand...
Click to collapse
flashtool dont work for you because you dont have a proper "megalock" by the way i had hard time too since its my first lg and was my first flash!! read read read.......its the secrete!!!

Categories

Resources