Database Users

Help with datafs.rfs

Hi i want to first convert datafs.rfs to ext2 and then obtain it from for using this command dd if=/dev/block/stl7 of=/sdcard/datafs.rfs but whenever i do this i got datafs.rfs of 148mb when i flash this datafs.rfs, my fon memory goes 0.0B. Actual datafs.rfs is only 4.1mb. where i m doing wrong. How to obtain correct datafs.rfs?

[Q] help me to restore build.prop to fix my phone

hello xda-developers i have a big problem with my phone (samsung galaxy young GT-s5360) every time i turn it on display the samsung logo and never go on it happened after i made my phone root and edit build.prop to install incompitble apps, i modified the line "ro.product.model=GT-s5360" to "ro.product.model=Nexus" and i reboot the phone and it never come back...i have a backup from build.prop file but i can't fix the phone , i tried to use adb to push build.prop but my phone doesn't appear on adb dveices and display "List of devices attached " empty i tried that on windows 7 and on linux ubuntu so i don't konw how can i fix this , is there another way to fix it inested of adb and why it display "List of devices attached " blank? .. please help me..

A. Where the hell did you get the idea that modifying your build.prop would root your device? There is literally no explanation for that.
B. You need to flash a factory image for your device.

How were you able to edit your build.prop without rooting??
Fawkes...

Fawkes... said:
How were you able to edit your build.prop without rooting??
Fawkes...
Click to expand...
Click to collapse
That's easy.. copy file to sdcard using es file explorer or such file browser.. now edit it..
The hard part is... how did he managed to put the edited build.prop file back without root..
I see conspiracy here..
-------------------------------------------------------------------------
★Nothing is True.. Everything is Permitted★
Muffins..? Yummy!©

Thats what I meant.
Fawkes...

Deadly. said:
That's easy.. copy file to sdcard using es file explorer or such file browser.. now edit it..
The hard part is... how did he managed to put the edited build.prop file back without root..
I see conspiracy here..
-------------------------------------------------------------------------
★Nothing is True.. Everything is Permitted★
Muffins..? Yummy!©
Click to expand...
Click to collapse
i already made my phone root with update.zip file i got from internet and after that i modified build.prop and the problem appeared.
this is the tutorial that i followed to edit build.prop to install incompatible apps .
howtogeek.c o m/116456/how-to-install-incompatible-android-apps-from-google-play/

063_XOBX said:
A. Where the hell did you get the idea that modifying your build.prop would root your device? There is literally no explanation for that.
B. You need to flash a factory image for your device.
Click to expand...
Click to collapse
where can i get the flash factory image ? and how to use it?

iori.x4ever said:
where can i get the flash factory image ? and how to use it?
Click to expand...
Click to collapse
See my guide.. link in my signature... there see post with stock / firmware installation through Odin... and follow it properly... you will be fine ...
-------------------------------------------------------------------------
★Nothing is True.. Everything is Permitted©★
Have you seen a Muffin..?

Deadly. said:
See my guide.. link in my signature... there see post with stock / firmware installation through Odin... and follow it properly... you will be fine ...
-------------------------------------------------------------------------
★Nothing is True.. Everything is Permitted©★
Have you seen a Muffin..?
Click to expand...
Click to collapse
i tried many times and every time odin display to me "<ID:0/011> SetupConnection.." and nothing go on ..!!
image preview => img13.imageshack.us/img13/7725/62931903.jpg

iori.x4ever said:
i tried many times and every time odin display to me "<ID:0/011> SetupConnection.." and nothing go on ..!!
image preview => img13.imageshack.us/img13/7725/62931903.jpg
Click to expand...
Click to collapse
There is a note in my guide if you get stuck like you are saying... reboot both phone and oc that part... or try latest version of Odin 3.. Odin 1.87 versions seems to be having problems sometimes..
-------------------------------------------------------------------------
★Nothing is True.. Everything is Permitted©★
Have you seen a Muffin..?

Deadly. said:
There is a note in my guide if you get stuck like you are saying... reboot both phone and oc that part... or try latest version of Odin 3.. Odin 1.87 versions seems to be having problems sometimes..
-------------------------------------------------------------------------
★Nothing is True.. Everything is Permitted©★
Have you seen a Muffin..?
Click to expand...
Click to collapse
ok .. i tried Odin3 v3.04 and now i got different problem Odin says
("
<ID:0/011> Added!!
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Complete(Write) operation failed.
<ID:0/011> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
")
image preview => img842.imageshack.us/img842/423/94840236.jpg
sorry and thanks for your attention..

iori.x4ever said:
ok .. i tried Odin3 v3.04 and now i got different problem Odin says
("
Added!!
Odin v.3 engine (ID:11)..
File analysis..
SetupConnection..
Complete(Write) operation failed.
Added!!
All threads completed. (succeed 0 / failed 1)
")
image preview => img842.imageshack.us/img842/423/94840236.jpg
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
sorry and thanks for your attention..
Click to expand...
Click to collapse
Sorting out the image.. I think you have wrong files... because files should end with .md5 extension... open tar file and see if it has files inside with .md5.. if you renamed them to .tar.... rename it back to .tar.md5
-------------------------------------------------------------------------
★Nothing is True.. Everything is Permitted©★
Have you seen a Muffin..?

Deadly. said:
Sorting out the image.. I think you have wrong files... because files should end with .md5 extension... open tar file and see if it has files inside with .md5.. if you renamed them to .tar.... rename it back to .tar.md5
-------------------------------------------------------------------------
★Nothing is True.. Everything is Permitted©★
Have you seen a Muffin..?
Click to expand...
Click to collapse
i didin't renemed them i downloaded them as .tar extension but i renamed them to .tar.md5 as you said and i got this error
("
<ID:0/011> Removed!!
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> PDA_S5360_JPLA1.tar.md5 is invalid.
<OSM> End...
")
i downloaded the FIRMWARE files from the link in your guide topic , i downloaded "MIDDLE EAST and AFRICA" => "S5360_JPLA1_OJPLA1_XXLA2"
the archicve file that i downloaded include 4 files
("
MODEM_S5360_XXLA2.tar
CSC_S5360_OJPLA1.tar
PDA_S5360_JPLA1.tar
readme.txt
")
doesn't include any file with .md5 extension.

iori.x4ever said:
i didin't renemed them i downloaded them as .tar extension but i renamed them to .tar.md5 as you said and i got this error
("
<ID:0/011> Removed!!
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> PDA_S5360_JPLA1.tar.md5 is invalid.
<OSM> End...
")
i downloaded the FIRMWARE files from the link in your guide topic , i downloaded "MIDDLE EAST and AFRICA" => "S5360_JPLA1_OJPLA1_XXLA2"
the archicve file that i downloaded include 4 files
("
MODEM_S5360_XXLA2.tar
CSC_S5360_OJPLA1.tar
PDA_S5360_JPLA1.tar
readme.txt
")
doesn't include any file with .md5 extension.
Click to expand...
Click to collapse
OK... see the read me file... what does it say?
-------------------------------------------------------------------------
★Nothing is True.. Everything is Permitted©★
Have you seen a Muffin..?
---------- Post added at 12:44 AM ---------- Previous post was at 12:38 AM ----------
Also check the md5sum of the files... you may have incomplete downloaded files..
-------------------------------------------------------------------------
★Nothing is True.. Everything is Permitted©★
Have you seen a Muffin..?

Deadly. said:
OK... see the read me file... what does it say?
-------------------------------------------------------------------------
★Nothing is True.. Everything is Permitted©★
Have you seen a Muffin..?
Click to expand...
Click to collapse
it says
("
Unofficial Odin firmware package for Samsung GT-S5360
S5360BPJPLA1/S5360BOJPLA1/S5360BXXLA2
Sliced from the Kies package by Doky
Use at your own risk!
Do not use pit file, and do not tick repartition!
Included regions:
ABS AFG BTC EGY JED KSA MAT MED MID MMC MRT MWD OTU PAK THR TMC TUN WAN XSG XSS
see more at XDA:
http://forum.xda-developers.com/showthread.php?t=1465800
")

anybody have original build.prop for galaxy y
iori.x4ever said:
hello xda-developers i have a big problem with my phone (samsung galaxy young GT-s5360) every time i turn it on display the samsung logo and never go on it happened after i made my phone root and edit build.prop to install incompitble apps, i modified the line "ro.product.model=GT-s5360" to "ro.product.model=Nexus" and i reboot the phone and it never come back...i have a backup from build.prop file but i can't fix the phone , i tried to use adb to push build.prop but my phone doesn't appear on adb dveices and display "List of devices attached " empty i tried that on windows 7 and on linux ubuntu so i don't konw how can i fix this , is there another way to fix it inested of adb and why it display "List of devices attached " blank? .. please help me..
Click to expand...
Click to collapse
Hey anybody have original build.prop file plz send me at [email protected]
plz :crying:

Ptekale said:
Hey anybody have original build.prop file plz send me at [email protected]
plz :crying:
Click to expand...
Click to collapse
in attachment - unzip it

Did you managed to boot up in Safe Mode or flashing AROMA File Manager from CWM?
Sent from my GT-P3110 using XDA Premium 4 mobile app

N8000 PIT File - How to save your PIT file

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:

Dumping system.img.ext4?

I've managed to patch to MF3 without flashing bootloaders, modems, rpm, and without losing TWRP. All without rooting the device. What this means is, I now have a 100% stock MF3 system partition that I would like to dump into an odin-flashable tarball. To do that, I need to dump my system (while in recovery) to a system.img.ext4, using whatever method is normally used to create an odin-flashable file.
I found this guide: http://forum.xda-developers.com/showthread.php?t=2277127
I wanted to get some feedback from Devs working on the I337, specifically. It appears that the command I want is this:
Code:
make_ext4fs -s -l 2760M -a system /sdcard/system.img.ext4 /system
But... where do I determine what size I need?
Many thanks.

Aou said:
I've managed to patch to MF3 without flashing bootloaders, modems, rpm, and without losing TWRP. All without rooting the device. What this means is, I now have a 100% stock MF3 system partition that I would like to dump into an odin-flashable tarball. To do that, I need to dump my system (while in recovery) to a system.img.ext4, using whatever method is normally used to create an odin-flashable file.
I found this guide: http://forum.xda-developers.com/showthread.php?t=2277127
I wanted to get some feedback from Devs working on the I337, specifically. It appears that the command I want is this:
Code:
make_ext4fs -s -l 2760M -a system /sdcard/system.img.ext4 /system
But... where do I determine what size I need?
Many thanks.
Click to expand...
Click to collapse
I might have found my own answer:
Code:
fdisk -l /dev/block/mmcblk0p16
Disk /dev/block/mmcblk0p16: 2894 MB, 2894069760 bytes
4 heads, 16 sectors/track, 88320 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p16 doesn't contain a valid partition table

No go. Perhaps I'm packaging it wrong? Perhaps I'm not pulling the image correctly?
Here's Odin's log:
Code:
<ID:0/020> Added!!
<ID:0/020> Odin v.3 engine (ID:20)..
<ID:0/020> File analysis..
<ID:0/020> SetupConnection..
<ID:0/020> Initialzation..
<ID:0/020> Get PIT for mapping..
<ID:0/020> Firmware update start..
<ID:0/020> system.img.ext4
<ID:0/020> NAND Write Start!!
<ID:0/020> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Here's what the screen said:
SECURE CHECK FAIL : system
Here's how I dumped the system (in adb shell while in recovery with /system and /cache mounted):
Code:
make_ext4fs -s -l 2894069760 -a system /sdcard/system.img.ext4 /system
make_ext4fs -s -l 2170552320 -a cache /sdcard/cache.img.ext4 /cache
(the above number of bytes were obtained using fdisk against the partitions)
And here's how I packed them into the Odin-flashable tarball:
Code:
tar -H ustar -c system.img.ext4 cache.img.ext4 > mf3.tar
md5sum -t mf3.tar >> mf3.tar
mv mf3.tar mf3.tar.md5
Does anyone see anything wrong with this method? Odin Mode currently shows:
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
- Root was never applied, kept the stock MF3 kernel, nothing's been touched in /system - everything 100% absolutely stock...

Check out this article:
http://androidforums.com/continuum-all-things-root/263953-how-make-custom-odin-images.html
Change the partition info to match that of i337

Craptain Krunch said:
Check out this article:
http://androidforums.com/continuum-all-things-root/263953-how-make-custom-odin-images.html
Change the partition info to match that of i337
Click to expand...
Click to collapse
That post is scary-old, though. Doesn't even mention ext4

Aou said:
That post is scary-old, though. Doesn't even mention ext4
Click to expand...
Click to collapse
I mainly linked it because the packaging commands are slightly different.

Craptain Krunch said:
I mainly linked it because the packaging commands are slightly different.
Click to expand...
Click to collapse
I see. I researched it a bit, and the "dd" method stopped working with the S3 and beyond. I tried it anyway, and Odin (on phone) failed, saying:
Unsupport dev_type
I am looking into this: https://github.com/Chainfire/sgs4ext4fs
But not sure if it applies.

Aou said:
I see. I researched it a bit, and the "dd" method stopped working with the S3 and beyond. I tried it anyway, and Odin (on phone) failed, saying:
Unsupport dev_type
I am looking into this: https://github.com/Chainfire/sgs4ext4fs
But not sure if it applies.
Click to expand...
Click to collapse
Check your PM sir.

I have never done this before, so I can't be of much help. The part I don't understand is why the size of the partition must be specified. My first question would be, does it need to specified accurately?
Even though this is for the Epic 4G, it may help
http://forum.xda-developers.com/showthread.php?t=2154762
It may allow you to do what you want without knowing the partition size since you would use a system dump as your source (see post #2).

upndwn4par said:
I have never done this before, so I can't be of much help. The part I don't understand is why the size of the partition must be specified. My first question would be, does it need to specified accurately?
Even though this is for the Epic 4G, it may help
http://forum.xda-developers.com/showthread.php?t=2154762
It may allow you to do what you want without knowing the partition size since you would use a system dump as your source (see post #2).
Click to expand...
Click to collapse
Thanks. Looking into this now.
By the way, the "sgs4ext4fs" program by chainfire seemed to do what it advertised, but still doesn't flash.
UPDATE/EDIT:
Code:
error: file_write: write: File too large
It seems that I can't use their method to create an ext4 file to add to the tarball... Still looking into it though...

Aou said:
Thanks. Looking into this now.
By the way, the "sgs4ext4fs" program by chainfire seemed to do what it advertised, but still doesn't flash.
UPDATE/EDIT:
Code:
error: file_write: write: File too large
It seems that I can't use their method to create an ext4 file to add to the tarball... Still looking into it though...
Click to expand...
Click to collapse
Sorry for lifting up an old thread, but did you eventually get it working? Thanks in advance.

Also would like to know
Sent from my ATT S4 MF3 using Tapatalk

jball said:
Also would like to know
Sent from my ATT S4 MF3 using Tapatalk
Click to expand...
Click to collapse
The best I can remember it did not work. It resulted in an ODIN flash-able TAR that wouldn't flash due to the bootloader not being signed. It really doesn't matter anymore because there is a ODIN flash-able MF3 file available now.

Sorry I thought you were trying to push a version of TWRP.of course I use Safestrap but I would love to be able to use a straight up custom recovery.thank you for a reply
Sent from my ATT S4 MF3 using Tapatalk

tys0n said:
Sorry for lifting up an old thread, but did you eventually get it working? Thanks in advance.
Click to expand...
Click to collapse
scott14719 said:
The best I can remember it did not work. It resulted in an ODIN flash-able TAR that wouldn't flash due to the bootloader not being signed. It really doesn't matter anymore because there is a ODIN flash-able MF3 file available now.
Click to expand...
Click to collapse
scott14719 is correct - the only images I was ever able to create were not accepted by the device due to signatures.
So there's an MF3 odin out there now? I haven't been paying attention. That's awesome.

Aou said:
scott14719 is correct - the only images I was ever able to create were not accepted by the device due to signatures.
So there's an MF3 odin out there now? I haven't been paying attention. That's awesome.
Click to expand...
Click to collapse
Ok, thanks. I was just asking because sm-g730a is also without official firmware. Trying to find a way to make one

tys0n said:
Ok, thanks. I was just asking because sm-g730a is also without official firmware. Trying to find a way to make one
Click to expand...
Click to collapse
Gotcha. Check out my other thread here: http://forum.xda-developers.com/showthread.php?t=2378946
Look at File #5 and File #6. Might guide you in the right direction. These "Odin-flashable" files don't actually work on the I337 because of the signature verification that's built-in the bootloader, but perhaps you might have better luck on the other device. As always, be careful doing any of this stuff.

[Q] system.img.ext4 not found while doing the URDLV method.

I got my firmware from sammobile and extracted this
N9005ZHUBMI7_N9005ZZHBMI7_N9005XXUBMI5_HOME.tar.md5
Using this method:
http://forum.xda-developers.com/showthread.php?t=2498850&highlight=n9005zhubmi7&page=84
Since it was a huge file it took hours for me to download and I got all the other necessary prerequisites ( Sammmobile firmware, URDLV, Cygwin and Odin) and as I opened up cygwin started to do the full method and things go smoothly. then when I execute the URDLV.sh this happens
Code:
Mode: full
Filename: N9005ZHUBMI7_N9005ZZHBMI7_N9005XXUBMI5_HOME
Extension: md5
Extracting Firmware...
system.img.ext4 NOT found!
Using the CSC method I get this error
Code:
Mode: csc
Filename: N9005ZHUBMI7_N9005ZZHBMI7_N9005XXUBMI5_HOME
Extension: md5
Extracting Firmware...
cache.img.ext4 NOT found!
So, I'm stuck. I don't know what I did wrong.
I checked the MD5 file(opened with winamp) and the files were there

Hi Mathmango, wondering if you managed to figure this out? I'm getting exactly the same error.
Cheers
Anthony
mathmango said:
I opened up cygwin started to do the full method and things go smoothly. then when I execute the URDLV.sh this happens
Code:
Mode: full
Filename: N9005ZHUBMI7_N9005ZZHBMI7_N9005XXUBMI5_HOME
Extension: md5
Extracting Firmware...
system.img.ext4 NOT found!
Using the CSC method I get this error
Code:
Mode: csc
Filename: N9005ZHUBMI7_N9005ZZHBMI7_N9005XXUBMI5_HOME
Extension: md5
Extracting Firmware...
cache.img.ext4 NOT found!
So, I'm stuck. I don't know what I did wrong.
I checked the MD5 file(opened with winamp) and the files were there
Click to expand...
Click to collapse

You have to place the image in the same folder where you have URDLV.sh;
For example C:/Root/Universal-RDLV_v0.5/
Output dir
tools dir
License.txt
N9005XXUENB3_N9005OXXENB1_N9005XXUENB1_HOME.tar
SS_DL.dll
URDLV.sh
this worked for me . First i had the same error but after i copied the firmware in the same director fixed the problem.