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
Related
Edit: Delete me
The Player 5.0 uses RFS and not ext4?
yuck...
BTW, you should be able to identify a kernel zImage by looking at the first few hundred bytes of the partition. I forget the exact thing you should be looking for at the moment.
Kernel is confimed. So is pbl,sbl, and factoryfs.rfs.
I used a hex editor and found the copyright info for the pbl and sbl. The kernel and factoryfs are in a flash I created that has been confirmed to work.
Oh yes, pit confirmed as well. Opened with hex edit.
dbdata, cache, data, and efs are confimed too. Mounted in linux and contents confirmed.
param.lfs is just a guess. It contains images mostly. The images are ones that you would see before android boot such as warning symbols and samsung logo.
Any others are not confirmed.
Sent from my YP-G70 using Tapatalk
If you want, i have
dd if=/dev/block/mmcblk0p10
dd if=/dev/block/mmcblk0p11
dd if=/dev/block/mmcblk0p12
dd if=/dev/block/mmcblk0p13
dd if=/dev/block/mmcblk0p14
dd if=/dev/block/mmcblk0p15
dd if=/dev/block/mmcblk0p16
dd if=/dev/block/mmcblk0p17
dd if=/dev/block/mmcblk0p1
dumps, and I can post them to my ftp server. I believe that p17 is the /sdcard partition, but I may be wrong.
apapousek,
I appreciate the offer and I'll keep it in mind, but I don't see how anything could be gained by having your copies of the dumps. I also wanted to remind you that some of those partitions may have personal data in them. If you want to upload them and put up a link to them, it may help someone, so I would invite you to do so...
Also I believe that you are correct about p17 which I show to be 1.35gb
There is no personal data on them, at all. I used a completely wiped device. The only thing changed in it was the time zone, and that it was rooted. The images could be used for recovery purposes, and seeing the differences between the devices.
Oh I see, with this map and those files, a complete recovery( or very close to it) could be created. I would love to have these files! Is the model the same? YP-G70CWY/XAA?
Meticulus said:
Oh I see, with this map and those files, a complete recovery( or very close to it) could be created. I would love to have these files! Is the model the same? YP-G70CWY/XAA?
Click to expand...
Click to collapse
My device says it is a YP-G70, no numbers following it. The partition layout could be the same. If you have a copy of your pit file, I could use diff to see if there are any real differences. If you want, I'll allocate you some room on my server and give you an ftp account to work with.
Here is an easy way to check if you have XAA version (may need root). Browse to /efs and open the "buyer_code.dat" file as text. The only thing in there should be "XAA". You can also open "/system/build.prop" as text and find "ro.csc.sales_code" and it should = "XAA". It's important to know which one this is. The US version that I have has capacitive buttons on the botton while the international ones have a hardware button in the middle. So the firmwares are not interchangeable between these models. The partition tables may be the same but I suspect that the capacitive buttons driver is simply not included with the international ones.
I do have the pit file included in the firmware I created and posted at samfirmware.com . Last link in original post above. There are 3 links in the samfirmware.com thread. 2nd and 3rd both have pit.
Thank you for the ftp space. May I use this as a mirror for my files pertaining to the YP-G70? Can I count on this space to remain active within reason?
Meticulus said:
Here is an easy way to check if you have XAA version (may need root). Browse to /efs and open the "buyer_code.dat" file as text. The only in there should be "XAA". You can also open "/system/build.prop" as text and find "ro.csc.sales_code" and it should = "XAA". It's important to know which one this is. The US version that I have has capacitive buttons on the botton while the international ones have a hardware button in the middle. So the firmwares are not interchangeable between these models. The partition tables may be the same but I suspect that the capacitive buttons driver is simply not included with the international ones.
I do have the pit file included in the firmware I created and posted at samfirmware.com . Last link in original post above. There are 3 links in the thread. 2nd and 3rd both have pit.
Thank you for the ftp space. May I use this as a mirror for my files pertaining to the YP-G70? Can I count on this space to remain active within reason?
Click to expand...
Click to collapse
Yes, I'm running with the XAA model. I do have capacitive buttons. I'll PM you with your ftp credentials. You may use this as a mirror for the YP-G70, and for any Galaxy Player you feel like. It should stay active for a year or so, I'm renewing it today, actually.
apapousek said:
Yes, I'm running with the XAA model. I do have capacitive buttons. I'll PM you with your ftp credentials. You may use this as a mirror for the YP-G70, and for any Galaxy Player you feel like. It should stay active for a year or so, I'm renewing it today, actually.
Click to expand...
Click to collapse
Hey, I have the same model XAA, do you have some rom for this device…??? I can’t find anything…
If you have some, could you send me a PM with a link …???
Thanks…
Link to ROM file
The link to the ROM file doesn't work, is there any updated URL list?
Thanks
Hi everyone,
I made this guide for users of a Galaxy Player 4.0 USA or INTL who want to get backups of every partition in case they completely brick their device. This will be very useful if you have somehow screwed up your partitions beyond just /system, which is what most ROMs only include. It even backs up /efs, which contains the serial numbers unique to every player and other things that even complete restore ROMs and nandroid backups don't include. It's also good to just have a backup of your partitions stored somewhere safe, because you never know when you might need them. Also, if you're reverting from CM7 (the second release or later) you will need to use this with a PIT file because CM7 uses MTD partitions. Basically, flashing this backup will allow you to completely return to how your device was before, including all your personal data and apps. Hopefully soon we'll begin to have less "bricked my player help" threads clogging up the General (and sometimes Dev) sections. Enjoy
This backup does not back up bootloaders, which can increase your chances of a hard-brick and are almost never needed. Also, this is for the YP-G1 / Player 4.0 USA or INTL only, not for 5.0 users.
Disclaimer: I am not responsible for your device if anything happens blah blah blah
*Pre-requisites*
- Rooted device or ROM
- Busybox (Most rooted ROMs have this, but you can still download Busybox Installer from the Play Store and update to the latest busybox version just to make sure)
- ADB properly set up
- Some space on your internal SD card (about 1-2 GBs should be fine)
- Player set to "USB Debugging Mode" found in Settings
Alright, let's begin. First we will need to make a dump of every partition on the device. However, dumping the PIT is not needed because Adamoutler has a thread with a master list of PITs. Open a Command Prompt (or Terminal if you're using Linux), make sure your device is connected and type:
Code:
adb remount
adb shell
su
Now, to back up EFS:
Code:
dd if=/dev/block/stl3 of=/sdcard/efs.rfs bs=4096
PARAM
Code:
dd if=/dev/block/stl6 of=/sdcard/param.lfs bs=4096
KERNEL
Code:
dd if=/dev/block/bml7 of=/sdcard/zImage bs=4096
SYSTEM
Code:
dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096
DBDATA
Code:
dd if=/dev/block/stl10 of=/sdcard/dbdata.rfs bs=4096
CACHE
Code:
dd if=/dev/block/stl11 of=/sdcard/cache.rfs bs=4096
DATA (Optional if you want your apps)
Code:
tar -czvf /sdcard/data.tar.gz /data
You can exit out of the current window and open a new one once all the processes above are completed.
Now to pull all of the backups to your computer:
Code:
adb remount
adb pull /sdcard/efs.rfs
adb pull /sdcard/param.lfs
adb pull /sdcard/zImage
adb pull /sdcard/factoryfs.rfs
adb pull /sdcard/dbdata.rfs
adb pull /sdcard/cache.rfs
adb pull /sdcard/data.tar.gz
I recommend keeping these files in a safe place on your hard drive for when you need to use them. Feel free to delete them from your player now to save space.
How to Flash
First grab the correct PIT for your device here
For Heimdall, just load the PIT, click "Re-Partition", and select the correct files for each partition. Then click flash.
For ODIN, you have to tar the files together first.
Using Cygwin or Terminal, browse to the directory where all your backup files are. Then, type in:
Code:
tar -H ustar -c efs.rfs param.lfs zImage factoryfs.rfs dbdata.rfs cache.rfs > backup_package.tar
Now load the PIT, click "Re-Partition", and under the PDA section browse to your backup_package.tar (or whatever you named it to). Click flash.
After it is done flashing, here's how to restore your apps. Open Terminal or Command Prompt to the directory of data.tar.gz on your computer:
Code:
adb remount
adb push data.tar.gz /sdcard/
adb shell su -c "tar -zxvf /sdcard/data.tar.gz"
And you're done! If all goes well you should have completely restored your device, with a perfectly safe method and no bootloaders! I hope that this will be helpful to people.
Reserved for future use....
I did this, and i believe that AdamOutlers .pit is what messed up my device. Can you please give me a copy of your or another copy?
Tcollins412 said:
I did this, and i believe that AdamOutlers .pit is what messed up my device. Can you please give me a copy of your or another copy?
Click to expand...
Click to collapse
AdamOutler's pit is not messed up... I used it to repartition my player and it worked perfectly with the right partitions.
Sent using Tapatalk
when i tried it, it messed up my player. do you know how i could fix it?
Hey klin1344, not sure if you still watch this thread, but I was wondering if anyone has had success using heimdall 1.3.2 with the 4.0? I see it says it broke compatibility with some devices.
iJimaniac said:
Hey klin1344, not sure if you still watch this thread, but I was wondering if anyone has had success using heimdall 1.3.2 with the 4.0? I see it says it broke compatibility with some devices.
Click to expand...
Click to collapse
No problem for me
i wanted to use this method to backup my /efs (like daniel advicd me to do ) but i cant seem to do it. It says Can't open 'sdcard/efs.rfs': Read only file system
pls answer
crancpiti said:
i wanted to use this method to backup my /efs (like daniel advicd me to do ) but i cant seem to do it. It says Can't open 'sdcard/efs.rfs': Read only file system
pls answer
Click to expand...
Click to collapse
You have to be rooted to do this.
Sent from my A500 using xda app-developers app
klin1344 said:
You have to be rooted to do this.
Sent from my A500 using xda app-developers app
Click to expand...
Click to collapse
i think either i hadnt BuSY box installed(my device was rooted before) or it was bcause i connected my device to the PC / i mounted my sdcards
now i have a efs.rfs file and that should do it i hope
thanks . i have problem with heimdall to download my wifi 4 int PIt file
is there any ADB command for downloading pit file from device?
aminking2005 said:
thanks . i have problem with heimdall to download my wifi 4 int PIt file
is there any ADB command for downloading pit file from device?
Click to expand...
Click to collapse
I do remember that there is the dd command from the adb shell in order to get your pit, but it's not the recommended way to get it.
You can download the pit files right here:
http://forum.xda-developers.com/showthread.php?t=1531850
zaclimon said:
I do remember that there is the dd command from the adb shell in order to get your pit, but it's not the recommended way to get it.
You can download the pit files right here:
http://forum.xda-developers.com/showthread.php?t=1531850
Click to expand...
Click to collapse
most pit file are represented for wifi4 8GB . but mine is 16GB.
so im not sure about pit files in forum.
if i install a custom rom and it faild can i recover my yp-g1 by having above backups?
aminking2005 said:
most pit file are represented for wifi4 8GB . but mine is 16GB.
so im not sure about pit files in forum.
if i install a custom rom and it faild can i recover my yp-g1 by having above backups?
Click to expand...
Click to collapse
Sorry for the long reply time, and yeah you should be able to restore with those backups.
Envoyé de mon Nexus 4 en utilisant Tapatalk
I know not a lot of people have their MJ7 rooted at this point but for those who did it can you upload an unbrick image archived using the following code
Code:
su
dd if=/dev/block/mmcblk0 of=/sdcard/backup.bin bs=1024 count=131072
I am trying the SD card unbrick method to see if I can unbrick my hard bricked (bootloader flashed) phone.
this is one of the many guides for the method: http://forum.xda-developers.com/showthread.php?t=2369125
the img file size should be 128mb, so please zip/compress before upload.
Thanks in advance!
Ah I see you requested me to upload one in the other thread. Sorry I didnt see your message. But bootloader version does matter. That being said I would upload one if I had an MJ7 debrick image. C'mon people upload this, it would also help development because we'd be able to experiment knowing we could unbrick. OP let me know if you need help creating it after someone hopefully uploads one.
Sent from my SCH-I545 using XDA Premium 4 mobile app
I am a complete noob, but my MJ7 S4 is rooted. Can you help me figure out where I'm supposed to put this code?
TheOnlyChicken said:
I am a complete noob, but my MJ7 S4 is rooted. Can you help me figure out where I'm supposed to put this code?
Click to expand...
Click to collapse
Yes if launch any command shell apps like Busybox and type in
Code:
su
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0.img bs=1M count=100
It would copy the debrick img file from your phone onto your SD card and then if you don't mind please upload that file. Thanks!
Oops I have to have 10 posts for some reason... What should I do? Can I private message you or something? BTW the file is 100b, did I do something wrong?
I have a rooted S4 on mj7, let me know if you still need this
Sent from my SCH-I545 using xda app-developers app
Here's mine.
Maybe itll help someone let me know what else i can do.
I'm on MJ7 rooted.
arrowproof said:
Yes if launch any command shell apps like Busybox and type in
Code:
su
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0.img bs=1M count=100
It would copy the debrick img file from your phone onto your SD card and then if you don't mind please upload that file. Thanks!
Click to expand...
Click to collapse
Let me know if that's what you were looking for.
Verizon Galaxy S4
# MJ7 #
ALL Knoxed Up!
Mistertac said:
Let me know if that's what you were looking for.
Verizon Galaxy S4
# MJ7 #
ALL Knoxed Up!
Click to expand...
Click to collapse
hmm I guess 1M doesn't register on the phone... can you try again with this
Code:
su
dd if=/dev/block/mmcblk0 of=/sdcard/backup.bin bs=1024 count=131072
the file size should be 128mb and then please zip/compress before upload. thanks
Here you go, I verified it was 128mb. It exceeds upload limit, so added to my dropbox.
https://www.dropbox.com/s/nsjor6ida1132cw/backup.zip
arrowproof said:
hmm I guess 1M doesn't register on the phone... can you try again with this
Code:
su
dd if=/dev/block/mmcblk0 of=/sdcard/backup.bin bs=1024 count=131072
the file size should be 128mb and then please zip/compress before upload. thanks
Click to expand...
Click to collapse
Here's mine as well. Verified 128mb.
https://www.dropbox.com/s/0yjgduyqg5ecgyd/backup.zip
Verizon Galaxy S4
# MJ7 #
ALL Knoxed Up!
Let us know if it works OP. I couldnt get MDK or ME7 to go reliably.
Sent from my SCH-I545 using XDA Premium 4 mobile app
failed
tried 3 different debrick file all failed to even get the phone turn on
arrowproof said:
tried 3 different debrick file all failed to even get the phone turn on
Click to expand...
Click to collapse
Try win32 disk imager on a class 10 sdcard mTching phone internal storage
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.
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.