Hey folks,
XDA is down, so I can't tell how much has been done, development wise, but its looking bleak. I'd like to help out, even though I do not have the device.
First, we need to get some Odin images going. This is BEST done with somebody who has a stock, but rooted, Samsung Continuum.
This has been adapted from here:
Creating Custom ROMs/Backups for Odin - Android Forums
First, you need to root, via either one of the one click methods, or z4root.
Then, you must setup adb, if you haven't already. Alternatively, you could be a masochist and use the terminal on the device, downloaded from the market.
As root (#)
To backup kernel parition:
Code:
dd if=/dev/block/bml7 of=/sdcard/kernel bs=4096
To backup recovery partition (probably the same as the kernel):
Code:
dd if=/dev/block/bml8 of=/sdcard/kernel bs=4096
To backup system:
Code:
dd if=/dev/block/stl9 of=/sdcard/system bs=4096
Backup the kernel, system, and recovery images from your sdcard to your computer. Make backups!
Rename kernel to: zImage
Rename recovery to recovery.bin
Rename system to factoryfs.rfs
The next part requires linux, OS X, or cygwin.
Cygwin
If you are using heimdall, the above images are ready for flashing.
If using Odin, we must still package them.
Code:
$ tar -H ustar -c image_1 [image_2 ...] > your_odin_package.tar
If you want an all in one package, put each image name in. if not, make one image per tar file.
Example: tar -H ustar -c zImage > zImage.tar
This would give us a zImage.tar file. Now we will turn it into a tar.md5 file, so that Odin can make sure its not corrupt before flashing.
Code:
$ md5sum -t your_odin_package.tar >> your_odin_package.tar
$ mv your_odin_package.tar your_odin_package.tar.md5
using the above example, your final file would be zImage.tar.md5.
This gets used with Odin3 v.1.30, in the PDA section. You need to install Samsung usb drivers prior to, of course, and the phone must be in download mode.
ALWAYS USE THE PDA SECTION IN ODIN.
Odin can be found here:
http://adrynalyne.us/files/odin/Odin3v1.3.exe
Download mode (on the Fascinate anyway), can be achieved by powering off device, holding DOWN volume, and plugging in the usb cable, or hitting power.
I plan on posting some other stuff here, so PLEASE, someone make these images for everyone! Its essential to have a fall back. I do not own the device, so I cannot.
I have the images and they have been restored onyo 3 devices without flaw. Ill release them tomorrow.
Sent from my SCH-I400 using XDA App
It's not my intention to resurrect such an old thread, but here's a little more info about this method.
If you're using Mac OS, the commands are a bit different.
Instead of:
tar -H ustar -c image_1 [image_2 ...] > your_odin_package.tar
tar --format ustar -c image_1 [image_2 ...] > your_odin_package.tar
Instead of:
md5sum -t your_odin_package.tar >> your_odin_package.tar
md5 -r your_odin_package.tar >> your_odin_package.tar
Pastor! thanks for the info, how do i convert the rom cwm zip i have to a flashable tar?
joshkoss said:
Pastor! thanks for the info, how do i convert the rom cwm zip i have to a flashable tar?
Click to expand...
Click to collapse
put boot.img in that tar. it is said to flash like a charm.
If you want to create flashhable kernel tar file, then download the attached tar template, and using Total Commander, copy your kernel into it. This file is OK with Odin Attached Files
{
"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"
}
kernel_base.tar
mai77 said:
put boot.img in that tar. it is said to flash like a charm.
Click to expand...
Click to collapse
Put boot.img into the odin, and it will almost certainly fail. And way to bump a dead thread
Lol, ^
Well since this thread is bumped anyways, I guess it's as good as place as any to ask; Imnuts, do you think there is a possibility you could work your kernel magic and maybe make us one now that we have source? thanks in advance, lol
Sent from my SCH-I400 using xda premium
Peanut butter jelly time!
Sent from my ADR6425LVW using Tapatalk
trailblazer101 said:
Lol, ^
Well since this thread is bumped anyways, I guess it's as good as place as any to ask; Imnuts, do you think there is a possibility you could work your kernel magic and maybe make us one now that we have source? thanks in advance, lol
Sent from my SCH-I400 using xda premium
Click to expand...
Click to collapse
now i only downloaded sources and took a look at txt files. kernel sources state "HOW TO BUILD KERNEL 2.6.35 FOR SCH-I400" now i looked at imnuts kernel building guide and seen that we would need the correct initramfs for it to boot correctly? and isnt 2.6.35 a GB kernel so maybe we can do something. I will be working on BRICKYOURPHONE.tars when i get my pc back in the same town as i. I might just rent a laptop if it doesnt happen soon lol
pretty sure imnuts knows something about this... (what we would need for custom kernel and GB ASOP?)
update on me:
PC still packed, finals over, and should be grabbing my pc in a week or so before spring quarter starts ive been missing thememing and posting more relevant things lol.
Related
Anyway this is final version of command line samsung stock zImage Splitter
THIS TOOL CAN SPLIT STOCK IMAGES ONLY!
aZuZu Samsung Mobile Stock zImage Splitter, v1.02.3f. Final. (c) aZuZu. 2011.
{
"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"
}
If this is not usefull please report to mod..
it is useful!!! thanks for ur work!
Thanks! Will test it later today!!
dupe post.....
i have problems with upload on server but new version can handle tegrak / chainfire..
Hi, thanks for your job
for my information, what is the purpose of a zImage splitter ?
Sent from my GT-I9100 using XDA Premium App
ok what is this thing?
Very helpful for DEVs in breaking ROMs down, kinda like "unzipping".
Thanks,
working on stock zImage KF2. (just to try it )
Is it possible to do the reverse process (on windows ) ?
I believe it's a bit more complicated (or impossible ?)
Noob question : Why decompiling a kernel when sources are free ?
i tried it but after extracting using the tool i only get empty folders ... am i doing it wrongly?
cruzzmz said:
i tried it but after extracting using the tool i only get empty folders ... am i doing it wrongly?
Click to expand...
Click to collapse
For the moment, it's working on stock zImage only
ok. folks! new version is up.. still in alpha but now supports all three formats
stock, tegrak, and chainfire are now supported.
WARNING: i have issuses with cygwin so there is special exe file run_cpio.exe in application folder which you can run manualy to unpack chainfire ramdisk.
enjoy!
sicopat said:
For the moment, it's working on stock zImage only
Click to expand...
Click to collapse
i am trying to extract the stock XXKF2 kernel
this is what i did
1. extract the .tar file
2. extract ur tool
3. copy the zImage to to ur tool folder
4. use cmd and use
Code:
asmzis zImage
all the zImage is extracted but inside all the folders are empty
cruzzmz said:
i am trying to extract the stock XXKF2 kernel
this is what i did
1. extract the .tar file
2. extract ur tool
3. copy the zImage to to ur tool folder
4. use cmd and use
Code:
asmzis zImage
all the zImage is extracted but inside all the folders are empty
Click to expand...
Click to collapse
by agrument is see you are using old version...
today i have upload new version. which can handle all three formats..
for now it is using additional argument..
so to unpack stock zImage command goes
asmzis zImage stock
so to unpack chainfire zImage command goes
asmzis zImage chainfire
so to unpack tegrak zImage command goes
asmzis zImage tegrak
old version could unpack only stock.
p.s next version will be back to old asmzip zimage becouse i will add detection for types..
plus fix for zimages w/o ramdisk.
Not to complain, but what could possibly be the use of dumping my kernels, aside from ripping my hard work off ? I mean, they are just the stock kernels + my modifications.
got error when extracting the ram disk ... 7z exe come out with error
i extract only stock zImage
cruzzmz said:
got error when extracting the ram disk ... 7z exe come out with error
i extract only stock zImage
Click to expand...
Click to collapse
i downloaded stock XXKF2 kernel what ever from here.. http://forum.xda-developers.com/showthread.php?t=1101671
also fixed error in 7z call procedure and reupload all now should be ok ...
Chainfire said:
Not to complain, but what could possibly be the use of dumping my kernels, aside from ripping my hard work off ? I mean, they are just the stock kernels + my modifications.
Click to expand...
Click to collapse
Well if they are stock kernels and somebody wanted to test cf-root with for example tegrak kernel? Shouldn't that be allowed to him / her? If not say a word and i will remove application from server. Sorry if i offended you in any way. I just thought that this appliction could be usefull.
damn server.. now patched version should be uploaded...
Thanks, will wait for the recompiling solution
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
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
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!!!
Q&A for [BOOT LOGO] Samsung Galaxy Tab 3 8.0 Boot Logo
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [BOOT LOGO] Samsung Galaxy Tab 3 8.0 Boot Logo. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
.thank you...
ketut.kumajaya said:
By extracting attached flashable zip, you'll know how to change Galaxy Tab 3 8.0 boot logo.
WARNING: Don't use any image created or edited by Linux image editor (i.e. Gimp, Gwenview, Krita), you'll got a black screen of death! A simple, powerfull, nice, and free Paint.NET - but Windows - image editor worked!
A pdn file (Paint.NET multi layer image) attached here as a template for your convenience.
BACKUP: If something goes wrong, flash param-samsung-t311.tar.md5 using Odin as PDA or Heimdall v1.4.0: "sudo heimdall flash --PARAM param.bin".
Some technical explanations:
There is a script inside my CWM flashable zip. This script will flash a logo.jpg overwrite the original one. I called this in-place flashing because only logo.jpg is replaced, the other files in the param partition untouched. Attached boot logo CWM flashable zip should be compatible for all T31x family but I only test it on T311.
Code:
#!/sbin/busybox sh
# Galaxy Tab 3 8.0 boot logo changer script
# Ketut P. Kumajaya, Nov 2013
# Extract device param.bin
dd if=/dev/block/platform/dw_mmc/by-name/PARAM of=/tmp/param.bin bs=4096
mkdir /tmp/param
cd /tmp/param
tar xf /tmp/param.bin
# Replace logo.jpg, repack param.bin
cp -f /tmp/logo.jpg /tmp/param/logo.jpg
rm -f /tmp/param.bin
tar cf - `ls | sort -t.` > /tmp/param.bin
dd if=/tmp/param.bin of=/dev/block/platform/dw_mmc/by-name/PARAM bs=4096
cd /tmp
rm -rf /tmp/param
rm -f /tmp/param.bin
Yes, Galaxy Tab 3 8.0 param.bin is a plain tar file but you have to use a correct command to repack it.
Flash attached CWM flashable boot logo at your own risk! I only test it using PhilZ Touch recovery. Please reboot into recovery before performing a normal reboot!
{
"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"
}
Images courtesy of http://www.imagesweb.org/ and http://www.wallpaperscraft.com/ .
Click to expand...
Click to collapse
I'm using sky boot...thank you...
Hello friend excellent contribution.
Friend please help with the following problem with my tablet sansung galaxy tab 3 GT-P5200 model, which mistakenly param.bin you change the original file with a file param.bin sanusng Galaxy SIII and my tablet does not start stays affixed to the boot logo sansung SIII. Cooperation could help me I attached the file reference GT-P5200. Thank You!.
Can I use this on the Samsung Galaxy tab 3 T210R and brilliant work dude and thanks in advance regardless of I I can use
Hello... I have the sm-t315t and accidently flashed "param-samsung-t311.tar.md5", I can and have used odin to restore the tab3 back to stock, but I have noticed on initial start up it did not have data option in settings, yet when I tap on the quick setting data toggle it starts as normal. My main problem with all this is I really want to go back to lollipop (cm12.1)... But the only version I can get to work is cm12.1-20150609 but it says no sim which is why I went back to stock. All other versions are boot-looping for me? Any help would be great as I'm still learning. Would like help to figure it out... thanks in advance to those who help or respond...
I'm sorry, but the thread is confusing.
If I want to flash a zip in twrp for my t310, which file can I use (starry sky, for example)?
nabril15 said:
I'm sorry, but the thread is confusing.
If I want to flash a zip in twrp for my t310, which file can I use (starry sky, for example)?
Click to expand...
Click to collapse
I have flashesd it using twrp,it is working successfully.i have tested it in twrpv2.8.7.1 and also in v3.0.0-1
U can flash any of the zip[emoji2]
Sent from my 2013023 using Tapatalk