Hi, I'm a total ignorant in terms of android rom development so, please be patient!
I have a MDF file (AP_G531FXXU1AOH1_CL693190_QB5886620_REV00_user_low_ship.tar.md5) obtainded using Samsung KIES. I've been using this file with ODIN to restore my stock ROM, everytime some ROOT method is unsuccessful!
My question is: can I somehow edit the contents of this file so I can ROOT my phone? If I remove the md5 extension and leave the .tar extension I can unzip the file; these are the contents of the file:
boot.img
NVM.img
recovery.img
system.img
Any ideias?
Phone Model: SM-G531F
Baseband version: G531FXXU1AOG3
Build number: LMY48B.G531FXXU1AOH1
Related
I've read that the latest 4.0.4 release (XWLPO) still has MMC_CAP_ERASE enabled in it's kernel.
Am I correct in thinking if I replace the zImage file in XWLPO's tar.md5 file with Siyah 3.4.1's zImage file, then flash the firmware through Odin then:
1. I will eliminate the possible brick bug
2. Device will be automatically rooted
I might replace the new bootloader (Sbl.bin) with the old one while I'm at it.
I know I'll have to install Tungstwenty's 4.0.4 camera/video fix after flashing.
Is there anything else I should consider if tweaking the official SamMobile tar file?
Cheers
...
I've tried updating the .tar.md5 archive but I have the following problems/questions:
1. When I open the XWLPO .zip file, as well as the .tar.md5 file, there is an SS_DL.dll file. What is this?
2. When I open the .tar.md5 archive with 7Zip it says "no correct record at the end of the archive"
3. Probably because of this error, if I try to update the archive 7Zip then says "not implemented"
Does anyone know how I can add/replace files in a SamMobile .zip file please?
Thanks
1-Ignore this file. Not needed for nothing.
2-Remove .md5 from the the end of extension .tar.md5 and 7zip open file without problem.
3-7zip does not update tar file. You have to unpack the whole archive and recreate the tar file
Hi guys, I could successfully unpacked and repacked system.img on 4.0.4 for my Galaxy S III by learning from xda, add root files, delete unnecessary system apps, etc, and using "tar -cvf ...." to make an tar pack to flash with ODIN, thx to all xda developpers.
But when I did this again on new GSIII 4.1.1 firmwares like DI2, My phone jammed in the 2nd screen, could someone help me?
Here is what I did on 4.1.1 firmwares in Ubutu, just like what I did on 4.0.4
1. unpack system.img from tar files
2. exchange system.img to system.img.ext4 in Ubutu
3. unpack system.img.ext4 with
Code:
mkdir systest; mount -o rw,loop system.img.ext4 systest
oh just forget the folder name.
4. modify the files in systest folder blablabla
5. repack system.img from systest folder using
Code:
sudo mkuserimg.sh -s systest systest-new.img ext4 temp 1536M
6. then make a new tar file to flash with recovery.img, hidden.img etc.
This tar file could be flashed with ODIN successfully, but like I said above, my phone didn't response in the 2nd screen with Samsung logos, I've wiped userdata in stock recovery but it didn't work.
Then I didn't modify any files, just unpack and repack system.img, flash it with ODIN, my phone remains the same
Could someone kindly to figure it out what I did wrong on new 4.1.1 firmwares? Is it about Samsung file format in 4.1.1?
Oh no replies until now...:crying:
I tested other 4.1.1 firmwares, unpack and repack system.img, then zip into new tar file, flash it, also stuck on the Samsung Logo with vibration
but it worked on all 4.0.4 firmwares
I'm trying to change the stock firmware on my unlocked unrooted international S3: I9300 to an official Samsung ROM downloaded from sammobile. The file I downloaded is called I9300XXDLJ4_I9300OXADLJ4_BTU. It's the UK unbranded firmware. The current firmware is on the phone is:
AP: I9300XXBLH3
CP: I9300XXLH1
CSC: I9300OPSBLH3
I have unzipped the file downloaded from Sammobile, which then gave me a tar.md5 file. So I change the file to just .tar, then unzipped that file. Inside that file I have:
boot.img
cache.img
hidden.img
modem.img
recovery.img
system.img
I then tried to use this tutorial on youtube called: How to Use Heimdall on Mac OSX to Install Kernels and ROMs!
When I open Heimdall on my MacBook, I plug my phone in (in download mode) and go to utilities, detect device, which it does. Then I save the PIT file on my desktop. I then go to the flash tab and browse for the PIT file, load that. Then when I go to add the files I don't have any files listed above called zimage or factoryfs etc, but also the Heimdell options doesn't have anything called kernal or the other ones anyway. My options in the partition name drop down box are:
Bootloader
Userdata
OTA
Hidden
System
Cache
Radio
Recovery
Boot
Param
EFS
BOTA1
BOTA0
MD5HDR
TZSW
The video says to match the files, but mine seems to have different names for things.
I have searched and read many forum posts on here and other sites. Can anyone tell me what I am doing wrong with either the unzipping or with Heimdall?
Thanks
Samsung hate apple....thats probably your problem
Sent from my GT-I9300 using xda premium
Thanks, but I only have access to a Mac. I did try my work computer, but it won't let me install any programs like Odin and drivers without Admin privileges.
Hello,
I want to make a custom ROM based on a stock i9001 ROM. However when I extracted the tar file there were IMG and ext4 files. I know how to make a rom via cygwin when i have: 1) system folder
2) META-INF folder
And 3) boot.img
I don't know what to do to the stock ROM
(.tar) to be like this
*** sorry for my bad english
Sent from my Galaxy Nexus using xda premium
Hi,
Tablet version:
Galaxy Tab 4 SM-T530
I am searching for the fastest way to batch flash a group of tablets.
I've wrote an android app, and this app needs to be in the rom.
So i need to modify a rom, and add my app to it.
What i've tried:
http://forum.xda-developers.com/tab-4/development/rom-slimrom-5-0-1-alpha-0-7-t2963906
Downloaded the rom above
Unzipped it to a folder
Downloaded the tool below:
http://forum.xda-developers.com/and...tool-tool-unpack-repack-dat-img-v2-0-t3284806
Extracted the system.new.DAT and added my app to it
Repacked the rom, to system.img
Extracted boot.img from the cyanogenmodrom
Extracted the kernel : boot_matisselte.img
Created .TAR's from those .img's using:
http://forum.xda-developers.com/showthread.php?t=2446269
Flash with odin.
Odin does accept all of the .TAR files, but when i turn on my tablet, it is stuck on the 'Samsung screen'.
Who can help me out, or point my in a good direction?