Related
Is there some way i can make a backup of my firmware?? Tried using Clockworkmod and the sorts but seems it isn't compatible
You'll need to root your device.
and use dd to pull from the /dev/block/bml* devices and copy them to an SD card.. The main ones you'd want are the zImage, and factoryfs ones. The bootloader ones aren't so necessary.
bml5 = zImage
bml6 = factoryfs
bml7 = datafs
I'm pretty sure..
precurse said:
You'll need to root your device.
and use dd to pull from the /dev/block/bml* devices and copy them to an SD card.. The main ones you'd want are the zImage, and factoryfs ones. The bootloader ones aren't so necessary.
bml5 = zImage
bml6 = factoryfs
bml7 = datafs
I'm pretty sure..
Click to expand...
Click to collapse
and...for recovery would be adb push?
For recovery you can use ODIN. You put those files into a single tar file, and tell it to flash. Lots of documentation on this on the forums.
File names would be:
zImage
factoryfs.rfs
datafs.rfs
what exact commands i should use to back up everything from my phone? so that i could restore it if something happens...
#cat /dev/block/* > /sdcard/*.img
* for stl4, bml4, bml5, bml6, bml7 ??? more? how about imei/efs folder?
Any noob-friendly instructions for this? I'd like to flash 2.2 to my i5800 but would like to make a backup first. What commands should I use?
I've got terminal emulator and busybox installed, do they do any help?
Is this method of NAND Backup for i5800 really working?
Hi,
I just want to check if this method of NAND Backup for i5800 is really working?
I would like to save my ROM before I upgrade to JPF.
Is this way of saving safe?
And is the ODIN restore of these savings safe?
I wouldn't like to make my phone brick.
I made that backup, weight something about 400MB
I had an bootloop, and want to restore this. Putted zImage, factoryfs.rfs and datafs.rfs to one .tar file and choosed One Package option.
But it was uploading Datafs for about 10 minutes, and nothing.
The progress bar in download mode, was taking second round, and stopped at ~160% D)
Now I have only 5 apps installed because I am messing with editing system apps, and flashing my phone every hour haha
How can I upload this?
Lots of documentation on this - Where?
precurse said:
For recovery you can use ODIN. You put those files into a single tar file, and tell it to flash. Lots of documentation on this on the forums.
File names would be:
zImage
factoryfs.rfs
datafs.rfs
Click to expand...
Click to collapse
Please, help! I googled a lot and still do not know which partitions to save, how to make the tar, and how to restore it using ODIN.
If someone knows these info, share with me. Please!
Edit:
I was not able to save stl5:
# dd if=/dev/block/stl5 of=/sdcard/zImage
dd if=/dev/block/stl5 of=/sdcard/zImage
/dev/block/stl5: cannot open for read: Invalid argument
JoHnNy08PL said:
I made that backup, weight something about 400MB
I had an bootloop, and want to restore this. Putted zImage, factoryfs.rfs and datafs.rfs to one .tar file and choosed One Package option.
But it was uploading Datafs for about 10 minutes, and nothing.
The progress bar in download mode, was taking second round, and stopped at ~160% D)
Now I have only 5 apps installed because I am messing with editing system apps, and flashing my phone every hour haha
How can I upload this?
Click to expand...
Click to collapse
Im noob in this but i heard that 200 MB is maximum.
Sent from my GT-I5800
I edited a ROM (JPA-Stock AOSP Theme 0.1), and I try to change the apps into factoryfs.rfs with MagicISO in Windows seven! I can do it, I changed and added many apps that I like! I save the factoryfs, but when I tried to flash my phone with that ROM, the ODIN shows me this fail:
"Big partition size!!"
And the ODIN starts to charge the factoryfs but never finish! =(
WHY?
Thank you for all!
UP! Help please!
"I changed and added many apps that I like"
You added too many apps and your factoryfs is just too big...
pff... Ok, I supose it... THANKS!
fersago said:
pff... Ok, I supose it... THANKS!
Click to expand...
Click to collapse
sorry buddy. I have no idea. Perhaps you can try to PM GSAM or others who post ROMS. They might be able to help you
Looks like you have added too many apps and size of the factoryfs.rfs is over 200MB. /system mount point is only 200MB. So you can not flash more than that.
OK, a lot of thanks for all!
I am trying make a ROM with a Factoryfs 200 MB below!
Of new, thanks
EDIT: I tried to make a factoryfs below 200mb, but ODIN shows me the same error! =(
Did u wipe dalvik cache and partition??
hold on! you said "I try to change the apps into factoryfs.rfs with MagicISO in Windows seven!" ??? how can you change apps into factoryfs.rfs??
this is the command you should use to dump factoryfs.rfs : "dd if=/dev/block/stl6 of=/sdcard/factory.rfs"
I don't understand why you need "MagicISO"...
J.Purungrit said:
hold on! you said "I try to change the apps into factoryfs.rfs with MagicISO in Windows seven!" ??? how can you change apps into factoryfs.rfs??
this is the command you should use to dump factoryfs.rfs : "dd if=/dev/block/stl6 of=/sdcard/factory.rfs"
I don't understand why you need "MagicISO"...
Click to expand...
Click to collapse
+1
JP mentioned the correct way.
Just copy as much apps your phone has space via adb command or qtadb or whatever a programm / app to your /system/app directory
When its full, its full.
Use the command mentioned above to dump your phone. The correct (and usable!) factory.rfs is found on your sdcard.
Take this file and a one package TAR file of any firmware flash file, echange the file in the TAR package and have fun with flashing via ODIN.
-> dont forget to exchange the kernel you need, too
OH...
this thread is some days old... maybe another user finds this thread via the search function and has use of the answers.
Cheers
qaysed
Hello everyone,
I have an I5800 and tried to make a simply custom rom deleting some apps and adding others. I did:
- mount with loop device the factorsfs.rfs from PDA.tar
- delete / add some apps
- unmount
- repackaged factoryfs.rfs cache.rfs datafs.rfs zImage to PDA.tar
- md5 singned the tar package
- with ODIN flashed (PHONE, CSC and the new PDA)
Now the phone boots nomore and got stuck at GT-5800 logo.
What should I do? Can anyone help?
best regards
[Resolved ] I5800XXJPF - Custom ROM not booting
Hello eveyone,
It worked before I did a "Factory data reset" with the command
*#*#7780#*#*
best regards,
nsdroid said:
Hello everyone,
I have an I5800 and tried to make a simply custom rom deleting some apps and adding others. I did:
- mount with loop device the factorsfs.rfs from PDA.tar
- delete / add some apps
- unmount
- repackaged factoryfs.rfs cache.rfs datafs.rfs zImage to PDA.tar
- md5 singned the tar package
- with ODIN flashed (PHONE, CSC and the new PDA)
Now the phone boots nomore and got stuck at GT-5800 logo.
What should I do? Can anyone help?
best regards
Click to expand...
Click to collapse
Two questions.
How do you repackage the factoryfs.rfs?
How do you md5 sign the tar package?
The Dark Lestat said:
Two questions.
How do you repackage the factoryfs.rfs?
How do you md5 sign the tar package?
Click to expand...
Click to collapse
1. Pack to tar "PDA.tar" all the file from factoryfs.rfs (system):
tar -H ustar -c cache.rfs datafs.rfs factoryfs.rfs zImage > PDA.tar
where the factoryfs.rfs is the modified one and other three are the same as in the original JPF's PDA file.
2. Sign the tar (the same name):
md5sum -t PDA.tar >> PDA.tar
3. Rename the tar as a file with extention tar.md5
mv PDA.tar PDA.tar.md5
best regards
When you mounted the rfs, it was mounted as vfat, yes? I doubt that if you modify it as vfat, it will still be a valid rfs. After all, it never was a real vfat file system, as a fsck.vfat will point out (it will throw a lot of errors if you run it on any rfs image). So the result of your modifications will probably be some file system which is neither a valid vfat nor a valid rfs.
Hi,
Thank you. You're right. It's more simple:root the phone, modify all you want, with
dd make an rfs image of the /dev/block/stl6 (system) and pack into pda.tar...
This way the files are not corrupted anymore.
best regards
Looking for the old bootloader of N8000 (sboot.bin) I also found what appears to be a rarity for our N8000: the Pit file (Partition Information Table)
1) N8000 - N8013 - PIT file
I examined it with a exheditor and I also found in what block of memory is in the N8000, and that is a small portion in /dev/block/mmcblk0 and exactly after 34 sectors of 512 bytes each, with a length of 2396 bytes,
Don't seems instead, like other cell or samsung devices, there is a dev \ block dedicated.
So now not only we have Pit file but you can also save the file pit of your N8000 and also of 8013
I was able to verify that the pit file I found is exactly the same pit file of my N8000!
I made (based on other examples) a batch file (I tested, but try it for yourself) that save your PIT file in the sdcard automatically by ADB commands; need to have super user rights .
Here the bat file for N8000:View attachment N8000_SaveMyPitFile.zip
Here batch file for N8013 View attachment N8013_SaveMyPitFile.zip
This is the adb commands used:
shell
su
dd if=/dev/block/mmcblk0 of=/sdcard/My-N8000.pit bs=1 skip=17408 count=2396
Here instead the file pit found in a Russian site: View attachment Note10_PIT.zip
I hope this will be usefull for those have bricked the N8000, even with the help of the bootloader file sboot.bin.
Here pit file of 8013 View attachment My-N8013.zip
2) N8020 - PIT file
For N8020 start address is the same of pit file of N8000, but has more lenght
This is the command dd for N8020
dd if=/dev/block/mmcblk0 of=/sdcard/My-N8020.pit bs=1 skip=17408 count=2924
This the pit file of N8020 View attachment My-N8020.zip
This the bat file for extract Pit file View attachment N8020_SaveMyPitFile.zip
Edit:
Here can found firmware with every file for Odin (incluse old bootloader ) for bricked note (russian language) http://narod.ru/disk/63365822001.6b115b2c7e18ce43c43f68567fe4d915/GT-N8000_mgt.zip.html
Another thing: If you have last blocked samsung bootloader (sboot.bin), you must make downgrade of bootloader if you want that Triangle away reset count to 0 and not to 1; i have tested it!
Thanks for this (and the warning about the new bootloader and the flash counter!)
My N8000 was working normally on the latest official not rooted rom (N8000XXCMD1_N8000RBTCMD1_DBT) and all of a sudden on a normal restart it hang on the samsung screen & when i tried to put it in the downloading mode it gave me the following lines
ODIN MODE
PRODUCT NAME:
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
i connected it to my laptop & the ODIN discovered it but when i tried to flash a rom it gave me an error related to the partition. Any idea how this can be solved please.
how can i use this 5 files rom to fix this problem...should i just flash all the files at once through ODIN (and should i include the bootloader)...i really need help here please
dool2002 said:
My N8000 was working normally on the latest official not rooted rom (N8000XXCMD1_N8000RBTCMD1_DBT) and all of a sudden on a normal restart it hang on the samsung screen & when i tried to put it in the downloading mode it gave me the following lines
ODIN MODE
PRODUCT NAME:
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
i connected it to my laptop & the ODIN discovered it but when i tried to flash a rom it gave me an error related to the partition. Any idea how this can be solved please.
how can i use this 5 files rom to fix this problem...should i just flash all the files at once through ODIN (and should i include the bootloader)...i really need help here please
Click to expand...
Click to collapse
Can you post the report of Odin?
Added in the first post PIT file of N8020
ghibli3 said:
Can you post the report of Odin?
Click to expand...
Click to collapse
here it is
<ID:0/021> Added!!
<ID:0/021> Odin v.3 engine (ID:21)..
<ID:0/021> File analysis..
<ID:0/021> SetupConnection..
<ID:0/021> Can't open the serial(COM) port.
<ID:0/021> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/021> Removed!!
Can you put pit file to n8010
dool2002 said:
here it is
<ID:0/021> Added!!
<ID:0/021> Odin v.3 engine (ID:21)..
<ID:0/021> File analysis..
<ID:0/021> SetupConnection..
<ID:0/021> Can't open the serial(COM) port.
<ID:0/021> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/021> Removed!!
Click to expand...
Click to collapse
I would try this:
downloaded the file that the link at the end of my first post
You have all in that file: the file pit, modem, bootloader and csc ECCC ... you need to enter in odin each file in the right place; the language is Russian; check repartition so you save the file pit on your N8000
See if you can flash so...
If you have a locked bootloader,It may be that you are unable to flash it; in which case you will need to downgrade the booloader via adb
Ok?
bilal.23 said:
Can you put pit file to n8010
Click to expand...
Click to collapse
You can do by yourself.
Use Framaroot for simple and quick root: with framaroot: you can root and unroot in one click; no new recovery need, your status is always official!
If you have recent firmware framaroot works with the last two options
With your N8010 rooted you can use the bat file in the first post of N8000 and send me
I can look it with an exheditor and tell you if is good and completed, so i can add in the first post your pit file of 8010!
ghibli3 said:
I would try this:
downloaded the file that the link at the end of my first post
You have all in that file: the file pit, modem, bootloader and csc ECCC ... you need to enter in odin each file in the right place; the language is Russian; check repartition so you save the file pit on your N8000
See if you can flash so...
If you have a locked bootloader,It may be that you are unable to flash it; in which case you will need to downgrade the booloader via adb
Ok?
Click to expand...
Click to collapse
i tried to flash them but it still fails...how can i downgrade the bootloader via adb?
dool2002 said:
i tried to flash them but it still fails...how can i downgrade the bootloader via adb?
Click to expand...
Click to collapse
You can use this batch file View attachment 1971542 that write via adb only theold bootloader sboot.bin (german bootloader)
These are the command via adb (thank to Odia xda-user) for all three file sboot.bin tz.img and param.bin
you can look in this post for S3 http://forum.xda-developers.com/showthread.php?t=2081748
> adb push sboot.bin /sdcard/sboot.bin
> adb push tz.img /sdcard/tz.img
> adb push param.bin /sdcard/param.bin
> adb shell
$ su
# dd if=/sdcard/sboot.bin of=/dev/block/mmcblk0p1
# dd if=/sdcard/tz.img of=/dev/block/mmcblk0p2
# dd if=/sdcard/param.bin of=/dev/block/mmcblk0p4
# rm /sdcard/sboot.bin
# rm /sdcard/tz.img
# rm /sdcard/param.bin
# reboot fota_bl
Can i save my .pit file on Galaxy S2 (GT-i9100G)?
Why this and are different?
N8000
dd if=/dev/block/mmcblk0 of=/sdcard/My-N8000.pit bs=1 skip=17408 count=2396
N8020
dd if=/dev/block/mmcblk0 of=/sdcard/My-N8020.pit bs=1 skip=17408 count=2924
Which command i should use?
Honestly, in our case I'd save the entirety of /dev/block/mmcblk0 somewhere, just-in-case. You can pick out the PIT later, but this way you're covered all ways.
8010 PIT
ghibli3 said:
You can do by yourself.
Use Framaroot for simple and quick root: with framaroot: you can root and unroot in one click; no new recovery need, your status is always official!
If you have recent firmware framaroot works with the last two options
With your N8010 rooted you can use the bat file in the first post of N8000 and send me
I can look it with an exheditor and tell you if is good and completed, so i can add in the first post your pit file of 8010!
Click to expand...
Click to collapse
Here my N8010 16GB PIT file. Can you check it and it to the first post then.
Thx
GeeKey said:
Here my N8010 16GB PIT file. Can you check it and it to the first post then.
Thx
Click to expand...
Click to collapse
Your file is too much big
Looking your pit it seems have the same size of N8000 so you must use the same command for N8000
dd if=/dev/block/mmcblk0 of=/sdcard/My-N8000.pit bs=1 skip=17408 count=2396
Please use this command and repost your pit file to confirm it
ghibli3 said:
Your file is too much big
Looking your pit it seems have the same size of N8000 so you must use the same command for N8000
dd if=/dev/block/mmcblk0 of=/sdcard/My-N8000.pit bs=1 skip=17408 count=2396
Please use this command and repost your pit file to confirm it
Click to expand...
Click to collapse
Anyone got a PIT file for the 8013? I've looked everywhere. My tablet gets into Odin and nothing else. Won't flash any rom, keeps saying that there's no PIT partition. I even tried flashing a 8010 PIT file out of desperation, but it failed with the same message.
Help?
Dileas said:
Anyone got a PIT file for the 8013? I've looked everywhere. My tablet gets into Odin and nothing else. Won't flash any rom, keeps saying that there's no PIT partition. I even tried flashing a 8010 PIT file out of desperation, but it failed with the same message.
Help?
Click to expand...
Click to collapse
How have you tried flashing pit file? By Odin?
ghibli3 said:
How have you tried flashing pit file? By Odin?
Click to expand...
Click to collapse
Yep, with Odin. And I tried all the usual steps. Made sure the port was USB2, installed a 32 bit version of windows, tried different ports, etc. At this point I think either I need the 8013 pit file, or the MMC might be completely screwed.
in serious need of the n8013 pit if anyone has it
Have Your Pit file on Terminal Emulator. Type this:
su -c 'dd if=/dev/block/mmcblk0 of=/sdcard/N80xx-out.pit bs=8 count=481 skip=2176'
This only to devices from 8 and 16GB. Not to 32 GB.
Attached the Pit analyzes from PIT Magic:
Hello All
I just start to work with Android files unpack and repack jobs, So I needed to extract the CSC file for I9500 model.
- I download the CSC tar file and then extract it using 7zip tool, Inside it i got two files cache.img and hidden.img
- I run this command :
/home/tools/simg2img /home/CSC/hidden.img system_.img
- After that i did this command to mount the img:
mount -o loop system_.img /mnt/system
- After that all is ok and i can check what is inside the img and add apk files or remove them.
- After I did what i needed I wanted to repack it to make it hidden.img again, So i run this command:
mkdir temp
/home/tools/mkuserimg.sh -s /mnt/system hidden.img temp 542xxxx (I puthere the original size of the system_.img using ll command)
- I got the hidden.img
- After that i repack it with the cache.img and get the CSC.tar file.
THE Problem is:
When I try to flash the repacked CSC.tar file it flashed the cache.img, but stop and failed at hidden.img
I looked here on the forum and found many post about i9500 repack steps, but all were talking about system.img or so, I only need to know the Right steps or order to repack the hidden.img of i9500 to be able to flash it via Odin flasher.
Notice: I use the same steps to unpack and repack hidden.img of S7582, S7562, and other models too, All were flashed ok with np.
I hope that someone can help me here.