I have Galaxy S5 (G900H) and made custom splash screen mod for G900H in this thread:
http://forum.xda-developers.com/galaxy-s5/themes-apps/redesigned-galaxy-s5-splash-screen-t3325025
And there are many requests to make it works for G900F
And here is the file (untested because I dont have G900F)
Flash it via custom recovery
And thanks to @amtra for his flashable zip
Please report me if you have problems
DO AT YOUR OWN RISK
And thanks for your time and your attention
Please wait for the new updated zip because I did something wrong to the zip
Note: This mod is only for G900F and the zip is untested. I really need testers and I really appreciate feedbacks
@amtra @willysusilo I've found 2 errors..
First I've tried to excecute your commands by shell.. obviously system mounted as rw, 777 perm recursive..
But when I try "tar xf /tmp/param.bin" nothing appens because G900F param isn't a tar (maybe for G900H it is..) and so in /tmp there will be only param.bin because tar xf command doesn't work.
2nd error: the S5 LOGO IN THE ZIP IS S5 STOCK ONE so if the method would work fine, users couldn't see anything changed! So please put MODIFIED logo into zip[emoji28]
Anyway thanks for your work. Above lines can seem criticism but they are not! I only want to report what I've noticed.. and really you haven't done any error in script. The only thing is that this method doesn't work (also using busybox sh..)..
I really appreciate your work and I hope this info can be useful.
If you want I can share my param.bin..
Sent from my SM-G900F using DeoXPer Pure MM
lucadalba said:
@amtra @willysusilo I've found 2 errors..
First I've tried to excecute your commands by shell.. obviously system mounted as rw, 777 perm recursive..
But when I try "tar xf /tmp/param.bin" nothing appens because G900F param isn't a tar (maybe for G900H it is..) and so in /tmp there will be only param.bin because tar xf command doesn't work.
2nd error: the S5 LOGO IN THE ZIP IS S5 STOCK ONE so if the method would work fine, users couldn't see anything changed! So please put MODIFIED logo into zip[emoji28]
Anyway thanks for your work. Above lines can seem criticism but they are not! I only want to report what I've noticed.. and really you haven't done any error in script. The only thing is that this method doesn't work (also using busybox sh..)..
I really appreciate your work and I hope this info can be useful.
If you want I can share my param.bin..
Sent from my SM-G900F using DeoXPer Pure MM
Click to expand...
Click to collapse
Oh i'm sorry, I forgot to change the logo. Can you tell me how you can extract param.bin from your G900F?
willysusilo said:
Oh i'm sorry, I forgot to change the logo. Can you tell me how you can extract param.bin from your G900F?
Click to expand...
Click to collapse
This is the problem and I don't know (how to extract).. else I would have said it in precedent post..
If you refers to param dump, the commands
Code:
su
mount -o rw,remount /
mkdir /tmp
chmod -R 777 /tmp
dd if=/dev/block/mmcblk0p11 of=/tmp/param.bin
work very well..
But dumping param.bin isn't a problem for now
The problem is extracting it.. and I don't know how to do..
I hope someone can found a way..
Sent from my SM-G900F using DeoXPer Pure MM
lucadalba said:
This is the problem and I don't know (how to extract).. else I would have said it in precedent post..
If you refers to param dump, the commands
Code:
su
mount -o rw,remount /
mkdir /tmp
chmod -R 777 /tmp
dd if=/dev/block/mmcblk0p11 of=/tmp/param.bin
works very well..
But dumping param.bin isn't a problem for now
The problem is extracting it.. and I don't know how to do..
Sent from my SM-G900F using DeoXPer Pure MM
Click to expand...
Click to collapse
That's okay, the important thing is the param.bin
I will do some research to extract it
Can you give me your param.bin?
willysusilo said:
That's okay, the important thing is the param.bin
I will do some research to extract it
Can you give me your param.bin?
Click to expand...
Click to collapse
Sure[emoji6]
Param.bin is param extracted with bs=4096, param2.bin without..
They should be the same but I prefere to give you both..http://cloud.tapatalk.com/s/57507c5e34498/param.zip
Sent from my SM-G900F using DeoXPer Pure MM
lucadalba said:
@amtra @willysusilo I've found 2 errors..
First I've tried to excecute your commands by shell.. obviously system mounted as rw, 777 perm recursive..
But when I try "tar xf /tmp/param.bin" nothing appens because G900F param isn't a tar (maybe for G900H it is..) and so in /tmp there will be only param.bin because tar xf command doesn't work.
2nd error: the S5 LOGO IN THE ZIP IS S5 STOCK ONE so if the method would work fine, users couldn't see anything changed! So please put MODIFIED logo into zip[emoji28]
Anyway thanks for your work. Above lines can seem criticism but they are not! I only want to report what I've noticed.. and really you haven't done any error in script. The only thing is that this method doesn't work (also using busybox sh..)..
I really appreciate your work and I hope this info can be useful.
If you want I can share my param.bin..
Sent from my SM-G900F using DeoXPer Pure MM
Click to expand...
Click to collapse
I forgot to change the zip with modified logo as I have tested it in many device and it must work on G900H device. Regarding G900F the splash image is binary encoded into bootloader and there is nothing in param.bin and I was scared that there is no param.bin on any partition of G900F. May be I was wrong but I have digged it further and found the bootloader was in mbn format I think.
amtra said:
I forgot to change the zip with modified logo as I have tested it in many device and it must work on G900H device. Regarding G900F the splash image is binary encoded into bootloader and there is nothing in param.bin and I was scared that there is no param.bin on any partition of G900F. May be I was wrong but I have digged it further and found the bootloader was in mbn format I think.
Click to expand...
Click to collapse
Bootloader is frammented in more than 1 file (.bin and .mbn ones)..
Here are a lot of bootloaders extracted and corrected compiled in .tar.md5 from _alexndr and flashable via Odin..
https://www.androidfilehost.com/?w=files&flid=18030
If you download a bootloader from _alexndr's repository and you rename .tar.md5 in .tar you can open it and into this tar you sholud found a lot of files (param.bin, sbl1.mbn ...)
All these files are parts of bootloader..
So extract it and have fun to found the way to extract bin and mbn files[emoji28]
Sent from my SM-G900F using DeoXPer Pure MM
It will never work on F model because it's Snapdragon and param.bin can't be edited (different format from Exynos one)
lucadalba said:
Bootloader is frammented in more than 1 file (.bin and .mbn ones)..
Here are a lot of bootloaders extracted and corrected compiled in .tar.md5 from _alexndr and flashable via Odin..
https://www.androidfilehost.com/?w=files&flid=18030
If you download a bootloader from _alexndr's repository and you rename .tar.md5 in .tar you can open it and into this tar you sholud found a lot of files (param.bin, sbl1.mbn ...)
All these files are parts of bootloader..
So extract it and have fun to found the way to extract bin and mbn files[emoji28]
Sent from my SM-G900F using DeoXPer Pure MM
Click to expand...
Click to collapse
So, to modify splash screen which one should I mod? Thanks for the feedbacks. I'm interested with this G900F splash screen. I will extract them from CPC8 BL, okay?
willysusilo said:
So, to modify splash screen which one should I mod? Thanks for the feedbacks. I'm interested with this G900F splash screen. I will extract them from CPC8 BL, okay?
Click to expand...
Click to collapse
Yeah 1CPC8 is good..
I can't help you anymore because I don't know how to read bin or mbn files..
So TRY with your knowledge.. I haven't other suggestions..
Sent from my SM-G900F using DeoXPer Pure MM
Moderator, please close this thread because my work isn't finished
I'm sorry guys
Hope I can find the solution for the splash screen in my free time
Thanks for your attention, participation, appreciation and thanks for testing
If I succeed, I promise I will post in new thread
Thread closed by OP request.
Related
[Update-Download KE8 Kernel & firmware]Dump System Image of SGS2 w/o Root Permission?
Hi,
Is there any way to dump system image and then extract Kernel files(zimage) from the current rom running on my Indian version SGS2?( which Samsung is claiming to have put the NFC chip in, but none have found it/or a way to find it yet! ) I don't have root permission ( and i know i can root using CF root but that would overwrite the kernel! ) As, you might be knowing the Indian version of SGS2 came pre-installed with KE8 firmware and we don't have a kernel repository of it yet.
The HIDSWVER on my phone is
I9100XWKE8/I9100ODDKE2/I9100DDKE2/I9100XWKE8
& *#1234# gives me,
PDA-I9100XWKE8
Phone-I9100DDKE2
CSC-I9100DDKE2
Build Info - Wed May 18 13:55:45 KST 2011
I tried to pull the /system using adb but that is not much of a help i guess. I can't use "dd if=/dev/block/*** of=/sdcard/system bs=4096" unless m rooted and i don't know the location of kernel and system images in /dev/block/? either.
Doing this in adb shell,
dd if=/dev/block/mmcblk0p9 of=/sdcard/system.img bs=4096 ( For System Image )
dd if=/dev/block/mmcblk0p5 of=/sdcard/zImage bs=4096 ( For Recovery + Kernel Image )
Click to expand...
Click to collapse
gives error that can't open /dev/block/mmcblk0p9 for read. Permission Denied.
Can you guys please help me to dump my Rom when it's not rooted? It will also make you guys upgrade it to the latest firmware. Although KE7 & KE8 are packaged on the same date and we seem to find not a single difference for now.
Update 1 :
Odia is having Samsung AnySVC access and he said he will try to put up a link to the KE8 System dump. He will also try to make an insecure KE8 kernel.
Update 2 :
For now we are trying to work on this idea as suggested by sgstwo
- Dump Rom with overwritten KE7 kernel ( We need it! )
- Extract Rooted factoryfs.img
- Flash factoryfs.img in another SGS2 with KE8 kernel
- Extract zImage
- Make a full rom dump from previous system.Img ( one we got from rooted KE7 Kernel Indian SGS2 ) and zImage from the other SGS2.
Hope this works out.
Anyone who has a Indian SGS2 and rooted with CF Root can post the whole system dump. We need it! Drop me a PM if you are unsure on how to dump your rom.
Update 3 :
XWKE8 Kernel : Download
Update 4 : So, now when we have the Full System Dump and it's also available in Samfirmware Repo.
Untouched Copy of KE8 firmware direct from Samsung Servers : Download KE8 Firmware Part 1 Part 2 Part 3
Interchangeable Links on Uploaded.to
Part 1 Part 2 Part 3
Password : gadgets.apnafundaz.com
I'm also interested about what dev/block/xxx is for Kernel zImage.
Another question i tried to dump my system image by doing this procedure:
Code:
adb shell
rootsh
dd if=/dev/block/mmcblk0p9 of=/sdcard/factoryfs.rfs bs=4096
tar -H ustar -c factoryfs.rfs > package_name.tar
md5sum -t package_name.tar >> package_name.tar
mv package_name.tar package_name.tar.md5
However i can't flash it through Odin because i got error while flashing. The Md5 check is ok, but i don't know what i am missing!
Thanks in advance!
Ghostbustersin said:
Hi,
Is there any way to dump system image and then extract Kernel files(zimage) from the current rom running on my Indian version SGS2?( which Samsung is claiming to have put the NFC chip in, but none have found it/or a way to find it yet! ) I don't have root permission ( and i know i can root using CF root but that would overwrite the kernel! ) As, you might be knowing the Indian version of SGS2 came pre-installed with KE8 firmware and we don't have a kernel repository of it yet.
The HIDSWVER on my phone is
I9100XWKE8/I9100ODDKE2/I9100DDKE2/I9100XWKE8
& *#1234# gives me,
PDA-I9100XWKE8
Phone-I9100DDKE2
CSC-I9100DDKE2
Build Info - Wed May 18 13:55:45 KST 2011
I tried to pull the /system using adb but that is not much of a help i guess. I can't use "dd if=/dev/block/*** of=/sdcard/system bs=4096" unless m rooted and i don't know the location of kernel and system images in /dev/block/? either.
I can't run #cat /proc/mtd either.
Can you guys please help me to dump my Rom when it's not rooted? It will also make you guys upgrade it to the latest firmware. Although KE7 & KE8 are packaged on the same date and we seem to find not a single difference for now. You won't be able to find KE8 even in the Sam firmware collections.
Click to expand...
Click to collapse
$ cat /proc/partitions gives you a list of all partitions, $ mount should give you the system partition. I haven't found the recovery partition yet.
Thijs96 said:
$ cat /proc/partitions gives you a list of all partitions, $ mount should give you the system partition. I haven't found the recovery partition yet.
Click to expand...
Click to collapse
There is no recovery partition. It's in the kernel, which is /dev/block/mmcblk0p5
You can't get near it without root
pulser_g2 said:
There is no recovery partition. It's in the kernel, which is /dev/block/mmcblk0p5
You can't get near it without root
Click to expand...
Click to collapse
First of all thanks a lot for your prompt reply.
However, I can't create a Custom ODIN Images for Backup/Restore...
Here is what i did so far
Code:
dd if=/dev/block/mmcblk0p9 of=/sdcard/factoryfs.rfs bs=4096
dd if=/dev/block/mmcblk0p5 of=/sdcard/zImage bs=4096
tar -H ustar -c factoryfs.rfs zImage > my_temp_package.tar
md5sum -t my_temp_package.tar >> my_temp_package.tar
mv my_temp_package.tar my_temp_package.tar.md5
At this point when i flash this through Odin by selecting my_temp_package.tar.md5 in PDA, it fail and i got the following output:
Code:
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> factoryfs.rfs
<ID:0/011> NAND Write Start!!
<ID:0/011>
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This is driving my crazy!!!
Any clues?
LeoMar75 said:
I'm also interested about what dev/block/xxx is for Kernel zImage.
Another question i tried to dump my system image by doing this procedure:
Code:
adb shell
rootsh
dd if=/dev/block/mmcblk0p9 of=/sdcard/factoryfs.rfs bs=4096
tar -H ustar -c factoryfs.rfs > package_name.tar
md5sum -t package_name.tar >> package_name.tar
mv package_name.tar package_name.tar.md5
However i can't flash it through Odin because i got error while flashing. The Md5 check is ok, but i don't know what i am missing!
Thanks in advance!
Click to expand...
Click to collapse
Galaxy s II uses .img not .rfs i think
coldflid said:
Galaxy s II uses .img not .rfs i think
Click to expand...
Click to collapse
Yep, but i even tried with .img and still it doesn't work
pulser_g2 said:
There is no recovery partition. It's in the kernel, which is /dev/block/mmcblk0p5
You can't get near it without root
Click to expand...
Click to collapse
I meant the kernel, it was a typo.
It doesn't matter which extension you give the output file, because dd transfers raw data. Heck, you could even make the output file an mp3
If you're working with Linux, you should run the command 'file' on whateveryounamedit.img : 'file system.img' It will say: 'raw data' or something like that. What you could do as well (Again, you must be running Linux), is mount the file.
Code:
sudo bash
mkdir /media/sgs2
mount -t ext4 system.img /media/sgs2
[code]
If it says it isn't a block device, try adding '-o loop' after '-t ext4'
Sent from my GT-I9100 using XDA App
You can't dump the kernel or any other partition from Android unless you have root access.
If you have access to two indian SGS2s (eg. another friend) with the same firmware, one of you could flash a rooted factoryfs.img and the other could flash an insecure zImage file. The 1st user dumps zImage, the 2nd user dumps /system.
sgstwo said:
You can't dump the kernel or any other partition from Android unless you have root access.
If you have access to two indian SGS2s (eg. another friend) with the same firmware, one of you could flash a rooted factoryfs.img and the other could flash an insecure zImage file. The 1st user dumps zImage, the 2nd user dumps /system.
Click to expand...
Click to collapse
I have a rooted indian sgs2..
PDA : I9100XWKE8
PHONE : I9100ODDKE2
CSC : I9100ODDKE2
i can help in dumping system folder..
I dont know how to..
can I copy the whole system folder frm rootexplorer and upload it?
I am not good with commands and stuff..
plz help..
sumeshd said:
I have a rooted indian sgs2..
PDA : I9100XWKE8
PHONE : I9100ODDKE2
CSC : I9100ODDKE2
i can help in dumping system folder..
I dont know how to..
can I copy the whole system folder frm rootexplorer and upload it?
I am not good with commands and stuff..
plz help..
Click to expand...
Click to collapse
How did you root it?
by cf-root 3.6..
so m now on ke7 kernel so need ke8 kernel..
can help you in pulling /system..only if I knew how
KE8 Kernel
Hi All Devs,
Can anybody Help porting KE8 Kernels (Secure & insecure) for rooting Indian Galaxy S 2.
suman_pal78 said:
Hi All Devs,
Can anybody Help porting KE8 Kernels (Secure & insecure) for rooting Indian Galaxy S 2.
Click to expand...
Click to collapse
Please read the thread. You need to get a dump of the kernel first
sgstwo said:
You can't dump the kernel or any other partition from Android unless you have root access.
If you have access to two indian SGS2s (eg. another friend) with the same firmware, one of you could flash a rooted factoryfs.img and the other could flash an insecure zImage file. The 1st user dumps zImage, the 2nd user dumps /system.
Click to expand...
Click to collapse
Thats seems to plausible idea. Well, I have access to more than 2 Indian SGS2 for that matter. Can you please upload rooted factoryfs.img?
sumeshd said:
I have a rooted indian sgs2..
PDA : I9100XWKE8
PHONE : I9100ODDKE2
CSC : I9100ODDKE2
i can help in dumping system folder..
I dont know how to..
can I copy the whole system folder frm rootexplorer and upload it?
I am not good with commands and stuff..
plz help..
Click to expand...
Click to collapse
And you can dump your system.img using this command in adb shell,
dd if=/dev/block/mmcblk0p9 of=/sdcard/system.img bs=4096
Ghostbustersin said:
Thats seems to plausible idea. Well, I have access to more than 2 Indian SGS2 for that matter. Can you please upload rooted factoryfs.img?
Click to expand...
Click to collapse
We would need a dump of the ROM first to do that...
pulser_g2 said:
We would need a dump of the ROM first to do that...
Click to expand...
Click to collapse
Would it matter if i upload the dump of rooted ROM with overwritten KE7 Kernel? We just need factoryfs.img, right? Or the overwritten kernel makes a difference there?
Ghostbustersin said:
Would it matter if i upload the dump of rooted ROM with overwritten KE7 Kernel? We just need factoryfs.img, right? Or the overwritten kernel makes a difference there?
Click to expand...
Click to collapse
I does make a difference since the xwke8 kernel would have been pretty interesting (better power management??). But having factoryfs.img isn't bad either. With the patched ke7 kernel you should be able to dump factoryfs - but you will not be able to get the ke8 kernel back. I guess gingerbreak does not work?
gladiac said:
I does make a difference since the xwke8 kernel would have been pretty interesting (better power management??). But having factoryfs.img isn't bad either. With the patched ke7 kernel you should be able to dump factoryfs - but you will not be able to get the ke8 kernel back. I guess gingerbreak does not work?
Click to expand...
Click to collapse
No Gingerbreak doesn't work. And, yes the KE8 kernel seems to have better Power management plus banding issue seems to be improved as well.( Although, i haven't used the KE7 Kernel but there is no Android System Resource power hogging in my SGS2 with KE8 kernel ). And People with Indian SGS2 who rooted using KE7 kernel is experiencing the android system ( or whatever it is! ) bug!
Well the whole idea is a bit complex, let me explain
- Dump Rom with overwritten KE7 kernel
- Extract Rooted factoryfs.img
- Flash factoryfs.img in another SGS2 with KE8 kernel
- Extract zImage
- Make a full rom dump from previous system.Img ( one we got from rooted KE7 Kernel Indian SGS2 ) and zImage from the other SGS2.
Hope this works out.
Ghostbustersin said:
Well the whole idea is a bit complex, let me explain
- Dump Rom with overwritten KE7 kernel
- Extract Rooted factoryfs.img
- Flash factoryfs.img in another SGS2 with KE8 kernel
- Extract zImage
- Make a full rom dump from previous system.Img ( one we got from rooted KE7 Kernel Indian SGS2 ) and zImage from the other SGS2.
Hope this works out.
Click to expand...
Click to collapse
Sounds good to me...
I downloaded roms from samfirmware, after I unrar it, these are the file list
boot.img bootloader.bin cache.img hidden.img modem.bin recovery.img system.img
So How can I extract some files from system.img? I've tried unyaffs, but it segfaulted.
another stupid question is , how I can flash these files using odin? just select *.img in
pda and start?
yo
hi darren.hoo, i faced the same problem as yours and i realised that we should actually boot our tab to the downloading mode before we launch Odin3,pda.Turn on the usb debugging too(i dont know if this is necessary or not).Anyway happy flashing!
*Odin can only read .tar / .md5 extension ,you dont have to extract everything.
Kruel
Hi Darren.hoo,
To read the image files - It depends.
boot.img and recovery.img requires potentially a script to seperate the ramdisk and also the kernel. There are many good article on many wikis that explains which hex point is the seperator between the two.
system.img - I haven't really played with this too much as I don't usually create ROMS or anything - have you tried to mount it normally on a linux system? as if the system.img is just a ISO? (e.g. mount -o loop system.img /mnt). To rebuild this to become "flashable" is a different story (i believe you need the unayffs2 tools).
bootloader.bin - you'll need a hexeditor of some sort. This is as is a bin file (data file)
Not sure about the others. (cache - i'd assume you can recreate anyway and the modem i guess is another binary that requires a hexeditor.)
In terms of flashing the IMG - you need to tar up the *.img files, then do something like md5sum -t #name of tar# >> #name of tar#. Basically, it just appends the hash in md5 format to the tar. rename the file to something like *.tar.md5, and use that to flash as PDA.
Hope this helps.
Really great tips!
frankus0512 said:
system.img - I haven't really played with this too much as I don't usually create ROMS or anything - have you tried to mount it normally on a linux system? as if the system.img is just a ISO? (e.g. mount -o loop system.img /mnt). To rebuild this to become "flashable" is a different story (i believe you need the unayffs2 tools).
Click to expand...
Click to collapse
no luck with this:
debian:/home/darren/gtab/rom/EUR/P7500XWKG9# mount -oloop system.img /mnt
mount: you must specify the filesystem type
But from what I've got from searching xda a lot, maybe it's RFS filesystem?
frankus0512 said:
In terms of flashing the IMG - you need to tar up the *.img files, then do something like md5sum -t #name of tar# >> #name of tar#. Basically, it just appends the hash in md5 format to the tar. rename the file to something like *.tar.md5, and use that to flash as PDA.
Click to expand...
Click to collapse
this tip just really solved my problem.
I've got a tar.md5 file with three files in it: boot.img, system.img, recovery.img, but I don't
want to flash recovery.img coz I've already flashed CWM, yesterday I tried delete recovery.img from the tar ball and then flash it, then ODIN tells me that the files is invalid by
md5sum. I didn't know earlier that it records md5 checksum at the end of the tarball file.
It seems the OP got his answer but I'm having problems figuring out what to do.
I also have a system.img that i unzipped from a tar.md5 package by first editing the file extension to only say tar and then untarring it. When I try to mount the system.img with:
sudo mount -o loop system.img /media/systemimg
I get the filesystem type error:
mount: you must specify the filesystem type
Could someone who knows this please comment on how to mount the system.img to gain access to the files so I can explore system, that would be awesome.
span_01 said:
It seems the OP got his answer but I'm having problems figuring out what to do.
I also have a system.img that i unzipped from a tar.md5 package by first editing the file extension to only say tar and then untarring it. When I try to mount the system.img with:
sudo mount -o loop system.img /media/systemimg
I get the filesystem type error:
mount: you must specify the filesystem type
Could someone who knows this please comment on how to mount the system.img to gain access to the files so I can explore system, that would be awesome.
Click to expand...
Click to collapse
samsung firmwares should have -t rfs but you have to have a linux kernel on your dev machine that has a rfs modules
http://forum.xda-developers.com/showthread.php?t=1081239
darren.hoo said:
I downloaded roms from samfirmware, after I unrar it, these are the file list
boot.img bootloader.bin cache.img hidden.img modem.bin recovery.img system.img
So How can I extract some files from system.img? I've tried unyaffs, but it segfaulted.
another stupid question is , how I can flash these files using odin? just select *.img in
pda and start?[/QUOTE,
........................................
hello,
you can extract system.img by android kitchen but it is long process to setup kitchen.
you make it .tar file to flash as pda in odin.
if you want to extract system.img, contact me by email, [email protected]
I will tell you .
Click to expand...
Click to collapse
I know this has been posted but since it was long ago and *nobody replied*, here it is:
There are no FULL rom for the 4.0US. Of course you can use the bootloaders from the international version and the factory image that has been posted here, but both don't go without issues. The only stock image we have is the kernel from package2.3.5.
So to fix those issues, I am asking if one of you with stock rom could be so kind as to post a factory.rfs file and (this is including everybody) the other files (sbl, param, boot etc)
I don't think it matters if it is rooted or not (factory.rfs), I am looking at something that is *fully* functional. I'll provide you with tutorials, just ask for it
Thank you!
I'll be happy to post it but where do I look for the files so I can post it. And fyi I am running root stock atm
Sent from my YP-G70 using xda premium
Ben456 said:
I know this has been posted but since it was long ago and *nobody replied*, here it is:
There are no FULL rom for the 4.0US. Of course you can use the bootloaders from the international version and the factory image that has been posted here, but both don't go without issues. The only stock image we have is the kernel from package2.3.5.
So to fix those issues, I am asking if one of you with stock rom could be so kind as to post a factory.rfs file and (this is including everybody) the other files (sbl, param, boot etc)
I don't think it matters if it is rooted or not (factory.rfs), I am looking at something that is *fully* functional. I'll provide you with tutorials, just ask for it
Thank you!
Click to expand...
Click to collapse
You have a US YP-G1 no? You can make a dump of your partitions to make a recovery solution!
Ok, first, I was wrong, you have to be rooted. Then, either from adb from your computer or from a terminal emulator in your device, you have to type:
dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096
No personal data is on this backup. This file can be flashed with heimdall so you can stop there or if you have linux, you can make a tar+md5 file to flash wth odin:
tar -H ustar -c factoryfs.rfs > package_name.tar
md5sum -t package_name.tar >> package_name.tar
mv package_name.tar package_name.tar.md5
if you don't have linux, just post factoryfs.rfs and i'll make it to a tar file.
Note: There may be other ways to do a an image without being rooted, I'll check if you are not rooted.
A HUGE THANKS!!
You have a US YP-G1 no? You can make a dump of your partitions to make a recovery solution!
Click to expand...
Click to collapse
No I can't since I have flashed my device with package2.3.5.tar that was posted here some time ago, which is the only working image we have to date, but there are some issues with this. I also can't post my boot loaders since I have flashed them with the international version. They work, but I can't enter recovery mode or download mode without a jig or access to an adb shell. All those flashes were made in the process of unbricking my device.
Hi Ben,
I had made a backup of my ROM before trying to install Steve's kernel. I used the same 'dd' command you mention in your instructions. The kernel install went OK, but when I ran CWM backup, I got into a boot loop and had to restore to the package_us2.3.5.tar.md5 that's been circulated around. This was a few weeks ago.
I've tried using the steps to run tar and md5sum on two separate Linux installs using my backup and have created what appears to be a valid .tar.md5 file, according to ODIN. But when I try to flash the .tar.md5 file, it passes MD5 checksum OK, ODIN reports NAND write start, but then fails immediately and I'm left with having to reflash package_us2.3.5.tar.md5 to get it to work again. Looking at my factory.rfs binary and comparing it to the factory.rfs in package_us2.3.5.tar.md5 seems to indicate that it's mostly similar, but there are binary differences. Headers look similar though.
So I'm not sure what I've done wrong in either (a) creating the backup image, or (b) creating the .tar.md5 file, or (c) flashing the .tar.md5 file. But the net result is that it won't flash successfully. So I don't think sharing my factory.rfs as it is will help you.
Here are some tips that my help troubleshoot issues.
1. The MD5 sum part is not neccessary, you can just put the factoryfs.rfs in a tarball and flash it.
2. You can loop mount a factoryfs.rfs in linux by creating an empty dir and running "mount -o loop -t auto factoryfs.rfs empty_dir"
3. It should be possible to reverse the dd command to restore the partition. ie "dd if=/sdcard/factoryfs.rfs of=/dev/block/stl9 bs=4096" (if I were going to do this I would use adb in recovery mode and root is required )
4. If you have a CWM backup, you should be able to to pull files out of the backup if you need to restore files manually. Files should be located on external sdcard in "clockworkmod/backup/"somedatestuff"/system.rfs.tar
It seems to me that what Ben456 wrote up there should have worked. Hope this helps.
I just learned how to dump my factoryfs.rfs file. This is dumped from my brand new Samsung Galaxy Player 4.0 (YP-G1CWY/XAA) right after I opened it from the box. It should be 100% clean.
I uploaded it here. Let me know if it works.
http://www.sendspace.com/file/6fzfdg
Here is the recovery rom I just uploaded. I really hope this works.
http://www.sendspace.com/file/1y2ogi
I created a thread for it here.
I have gpt solution to my mistake I accidentally checked NAND Erase All option which caused the p
mounting problem It can be recovered by the flashing of pit file
Please i want is ASAP.
EDIT : got solution
If anyone accidentally check nand erase all then just follow this steps
1. flash oudhs rrcovery
2. go to cwm and then format (sumthing like dis) in that unmount all and format sdcard/media it will take time 2 to 3 mins and then wipe cache dalvik cache data factory reset
3. restart tada
4. no need for pit file
http://forum.xda-developers.com/showthread.php?t=1916936
this could help u
I gone through the post but i dont get it how to make for mega 5.8 Can any one create it .. ??
Please someone provide me or do this as i am on xp and computer lags very much
Its very easy to get it, just run this from a root
shell (adb or terminal emulator):
dd if= /dev/ block / mmcblk0 of = /sdcard/ out. pit bs = 8 count = 481 skip= 2176
(Doesn't matter what ROM you are running)
Then just get me a copy of /sdcard/out.pit
These can be useful later and should be handy to
have.
Thanks in advance!
no one to help device now also bricked only
hardik190 said:
no one to help device now also bricked only
Click to expand...
Click to collapse
Well i know were a pit file is but they want you to buy an accont and the cheapest they have is you can get 5 files for $15.00 US, if you like I could put up the link..it is a samsung link I believe.
Edit: I have to find the link again as I thought I saved it on my phone..I will check my pc as I might have the link on there.
Sent from my SGH-I527M Mega 6.3
starmaster10 said:
Well i know were a pit file is but they want you to buy an accont and the cheapest they have is you can get 5 files for $15.00 US, if you like I could put up the link..it is a samsung link I believe.
Edit: I have to find the link again as I thought I saved it on my phone..I will check my pc as I might have the link on there.
Sent from my SGH-I527M Mega 6.3
Click to expand...
Click to collapse
Oh please can you give it fast i am just 1 step below to unbrick my phone
hardik190 said:
Oh please can you give it fast i am just 1 step below to unbrick my phone
Click to expand...
Click to collapse
Okay here is the link below for you and just go down the list a bit and you will find the i9152 pit file. :good:
http://www.samsung-file.com/index.php?dir=/SAMSUNG_PIT_FILE
starmaster10 said:
Okay here is the link below for you and just go down the list a bit and you will find the i9152 pit file. :good:
http://www.samsung-file.com/index.php?dir=/SAMSUNG_PIT_FILE
Click to expand...
Click to collapse
I dont have any paypal account and I m from india no usd can you give me the file please i need it badly
[B said:
hardik190[/B];48715041]
On terminal emulator type:
su -c 'dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=481 skip=2176'
Then just get me a copy of /sdcard/out.pit [End of QUOTE]
==============================================================
Sorry but I don't understand. You must pay to have a pit.file when all people can make it easy whit that command dd? (Whithout some spaces and corrected)????????
I'm surprised, astonish.
Hey People, own from a I9152, there aren't one from Yours that can make this and send to OP???
PS: This command is only for devices until 16 GB, not for 32 GB.
Click to expand...
Click to collapse
ValenteL said:
Sorry but I don't understand. You must pay to have a pit.file when all people can make it easy whit that command dd (whithout spaces)????????
I'm surprised, astonish.
Hey People, own from a I9152, there aren't one from Yours that can make this and send to OP???
Click to expand...
Click to collapse
I agree they should not even charge for a pit file, with this command is it suppose to be like this
suddif=/dev/block/mmcblk0of=/sdcard/out.pitbs=8count=481skip=2176 is this correct without spaces, if not could it be posted actually as it should be as it is not working for me, even though i don't have the mega 5.8 myself.
starmaster10 said:
I agree they should not even charge for a pit file, with this command is it suppose to be like this
suddif=/dev/block/mmcblk0of=/sdcard/out.pitbs=8count=481skip=2176 is this correct without spaces, if not could it be posted actually as it should be as it is not working for me, even though i don't have the mega 5.8 myself.
Click to expand...
Click to collapse
Not good. Is corrected on my post before.
ValenteL said:
Not good. Is corrected on my post before.
Click to expand...
Click to collapse
Mine is the 16gb version..but I was leaving spaces were it was showing in the post..so I still am not sure if I have to leave spaces were it shows in the command or leave no spaces.
And were does it save the file as I could never find it.
Sent from my SGH-I527M Mega 6.3
starmaster10 said:
Mine is the 16gb version..but I was leaving spaces were it was showing in the post..so I still am not sure if I have to leave spaces were it shows in the command or leave no spaces.
And were does it save the file as I could never find it.
Click to expand...
Click to collapse
Type this:
su -c 'dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=481 skip=2176'
And control the out.pit whit PIT_Magic.exe on one Pc if it is good. Attached:
You can create a analyzed file and see all contents from Pit file.
Have also attached a analyze from a I9205 out.pit to compare.
ValenteL said:
Type this:
su -c 'dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=481 skip=2176'
And control the out.pit whit PIT_Magic.exe on one Pc if it is good. Attached:
You can create a analyzed file and see all contents from Pit file.
Click to expand...
Click to collapse
Okay will do and I have the Pitmagic already on the pc..thanks for this and will give it a whirl.
Sent from my SGH-I527M Mega 6.3
ValenteL said:
Type this:
su -c 'dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=481 skip=2176'
And control the out.pit whit PIT_Magic.exe on one Pc if it is good. Attached:
You can create a analyzed file and see all contents from Pit file.
Have also attached a analyze from a I9205 out.pit to compare.
Click to expand...
Click to collapse
Okay it seem to work with this command and this is the file i got of the text file out of the pit file, looks correct i believe and is for the i527m Canadian version of the mega 6.3.
starmaster10 said:
Okay it seem to work with this command and this is the file i got of the text file out of the pit file, looks correct i believe and is for the i527m Canadian version of the mega 6.3.
Click to expand...
Click to collapse
This PIT Analizes is from out.pit of Your i527M. Compared whit out.pit from I9205 mega 6.3 International (from post #14) have some differences from partition 20 to 24. Your have more one partition called Persdata that I9205 not have.
Now we need someone that make the same from I9152 to compare whit mine I9205 and to Yours i527M.
ValenteL said:
This PIT Analizes is from out.pit of Your i527M. Compared whit out.pit from I9205 mega 6.3 International (from post #14) have some differences from partition 20 to 24. Your have more one partition called Persdata that I9205 not have.
Now we need someone that make the same from I9152 to compare whit mine I9205 and to Yours i527M.
Click to expand...
Click to collapse
Forsure as they are different a bit, as mine has 3 partitions on it i believe.
starmaster10 said:
Forsure as they are different a bit, as mine has 3 partitions on it i believe.
Click to expand...
Click to collapse
3 partitions? I don't understand. Your have different partition from 20 to 24. The 20 is persdata and on i9205 is system. I9205 not have partition 24.
(On analyzes file, "identifier:" is the partition number)
ValenteL said:
3 partitions? I don't understand. Your have different partition from 20 to 24. The 20 is persdata and on i9205 is system. I9205 not have partition 24.
(On analyzes file, "identifier:" is the partition number)
Click to expand...
Click to collapse
Well when I use TWRP to backup my stuff I think it says backing up no. of partitions 3..I will check this out again as this is why I said I believe it might have 3 partitions but I may be incorrect on this.
Edit: I just did a backup with TWRP recovery and it does say "Total number of partitions to backup: 3" so i must have 3 partitions. :silly:
Sorry that I have gone off topic here abit as this is for the i9152 pit file thread and if someone withi this version of the phone could make a pit file this would be awesome.
Sent from my SGH-I527M Mega 6.3
From Sammobile new 4.4.2 P5210XXUBNH1
Luxor said:
From Sammobile new 4.4.2 P5210XXUBNH1
Click to expand...
Click to collapse
http://samsung-updates.com/device/
there is the download link i am downloading it right now.
will it work on my dutch tab 3 10.1?
damian312 said:
http://samsung-updates.com/device
there is the download link i am downloading it right now.
will it work on my dutch tab 3 10.1?
Click to expand...
Click to collapse
downloading now too, please report!
Downloading.
nowo said:
downloading now too, please report!
Click to expand...
Click to collapse
I am a little afraid to test it.
Do i have to flash through odin?
hey,
if you guys are hesitant, i'll test it. give me a couple of hours to get it and do the usual
@Restl3ss - dude OP look !
m
moonbutt74 said:
hey,
if you guys are hesitant, i'll test it. give me a couple of hours to get it and do the usual
@Restl3ss - dude OP look !
m
Click to expand...
Click to collapse
You are the man.
i wait for it
dead link bud!
RoninTPD said:
dead link bud!
Click to expand...
Click to collapse
http://samsung-updates.com/device/
not that hard to fix it:good:
Installing. can't wait to pull it apart.
CAG-man said:
Installing. can't wait to pull it apart.
Click to expand...
Click to collapse
cag,
when you are go can you pull the /system/vendor directory and post it?
also /system/bin/toolbox ?
my download just started , i can't wait !!
m
M,
I will do so.
Holy crap, finally!
damian312 said:
http://samsung-updates.com/device/
not that hard to fix it:good:
Click to expand...
Click to collapse
thanks!!:good:
CAG-man said:
Installing. can't wait to pull it apart.
Click to expand...
Click to collapse
Does it work?
The firmware works, but two things are proving to be very difficult.
one is extracting system.img, i dont know what's different, but the method i used for the 4.2 firmwares just crashes now.
two, and this is a big one
rooting it..
working on it
edit: super SU 1.9.4 zip from chainfire worked. No other method works though, the superuser apk will install but the binary doesn't stick
edit 2: successfully extracted the system image
notes
hey,
if the update with the t211 was any indication, be sure to only write boot.img and system.img
i am making a flashable zip and will post after i get it right and debloated and get the script correct.
realistically, sometime tomorrow, will update.
@Restl3ss okay so iam laughing at myself right now becuase i can not get the damned thing to write. i don't use windows
so no odin. i have tried dd writing the images but on boot i hang at logo and with no adb i can't get a visual on the problem.
i have a .zip put together to do the same and get the same. i have another zip set up ota style but can't script worth a damn.
can you whip up a script and post it?
an interesting note- in /sbin is a binary file named partlink. thoughts?
Restl3ss
@Restl3ss
okay so this is the joke
i am too poor to upload a large file to devhost. :laugh:
solution - i going to upload the otapackge for the firmware WITHOUT the system folder.
the package has the modified to unsecure boot.img and the updater script which just happens to be the
same one i am using for cm11 :laugh: :victory:
these are the instructions for converting, mounting and pulling the system image into an cwm flashable zip
to convert and mount sparse .img in terminal
simg2img system.img system.img.ext4
mount -o loop system.img.ext4 /a/directory
then nav to that directory in file browser, copy the contents of /system and insert in to package.
there is also a second step to correct issues with symlinks in vendor. drop that package into ota second
sorry for the inconvenience. it's in your folder with the patches.
but hey, i'm poor.
m
i'm running it right now and it seems very kitkatty
If i flash 4.4 can i still flash back to 4.2.2?
moonbutt74 said:
@Restl3ss
okay so this is the joke
i am too poor to upload a large file to devhost. :laugh:
solution - i going to upload the otapackge for the firmware WITHOUT the system folder.
the package has the modified to unsecure boot.img and the updater script which just happens to be the
same one i am using for cm11 :laugh: :victory:
these are the instructions for converting, mounting and pulling the system image into an cwm flashable zip
to convert and mount sparse .img in terminal
simg2img system.img system.img.ext4
mount -o loop system.img.ext4 /a/directory
then nav to that directory in file browser, copy the contents of /system and insert in to package.
there is also a second step to correct issues with symlinks in vendor. drop that package into ota second
sorry for the inconvenience. it's in your folder with the patches.
but hey, i'm poor.
m
i'm running it right now and it seems very kitkatty
Click to expand...
Click to collapse
got it system folder is properly extracted and what not, trying to deodex. About 10 apks are failing on every deodex attempt, can't figure out why. Gonna upload a 100% stock to xda anyway, deodexed + rooted will just have to come a bit later.