Database Develop

[Q] [HELP] Samsung Galaxy S Anycall M110S Nandroid Backup/ Soft Brick

Good Day Folks.
So yesterday I was flashing my Samsung Galaxy S M110S (Korean Version)
with a stock rom
(M110S-Gingerbread-HOME-IMAGE-REV03-VG26-1812-USER.tar) and installing
Tegrak Kernel V29.
Everything works smoothly until I flashed a ClockworkMOD Recovery not
intended for my phone(sorry I was foolish and flash a CWM meant for
other device) then when I open my device I am always brought to this
(Samsung Stock Recovery)
Samsung utils blah. blah.
# MANUAL MODE #
E:failed to mount /cache (Invalid Argument)
E:Can't mount /cache/recovery/recovery_kernel_log
E:copy kernel file :: Can't open /cache/recovery/recovery_kernel_log
E:failed to mount /cache (Invalid Argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
blah.blah
Click to expand...
Click to collapse
I am only allowed to navigate with 3 options; Reboot, Wipe Data, Wipe
Partition. Rebooting only brings me to the recovery, both wipes
provides the same error.
So I try to flash again with the same stock rom and ODIN keeps on
throwing me this:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> modem.bin
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Left with no idea, I flashed an iCarus SpeedMod kernel(via ODIN) to see
what will happen. Luckily the recovery is now CWM and I was entitled
with so many options. One of this is the Backup/Restore option so I
think that if I have the right backup files stated below, I can put it
into the internal SD card(I have access) and launch the Restore
option to bring my phone back to life.
cache.img
data.img
dbdata.img
nandroid.md5
and all the other files you get when backup-ing files using CWM.
I am asking for your full help. Please be noted that my device:
Can access Download Mode
Can access Recovery Mode(no function)
Can be recognized by ODIN and be flashed.
...and is in need for a very big help!
So for those of you who has a nandroid backup(if my terms are correct)
of a Samsung Galaxy S M110S or has an idea to resurrect my device I
will be very thankful.
And If I can add I can also select Apply Update Via ZIP. Does that mean
I can also apply zip updates? If yes, where can I find those?

please help me with this one.

gertnilo said:
please help me with this one.
Click to expand...
Click to collapse
Seems an old post (just came across this ....anyway
You need to flash files from the repair kit, download from links below

[Q] Problem booting - Please help

Hi, I've searched for something similar to this for reference but to no avail. I desperately need some help.
My Galaxy Note was running ICS, the German stock version which was downloaded from odin at time of release. A couple of days ago, I rooted my phone using CWM.zip and SU-Busybox-Installer.zip which were downloaded from here, though I'm not sure that's what's causing the problem.
First thing this morning, my phone wouldn't get past the logo screen when trying to switch it on, so I went into recovery mode where I saw the following text
# MANUAL MODE #
-- Appling Multi-CSC...
E:failed to mount /system (Invalid argument)
can't mount '/system' (Invalid argument)
E:failed to mount /system (Invalid argument)
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_install
I was unable to find someone else with this problem so I unrooted the phone using CWM.zip and SU-Uninstaller-signed.zip, but it still wouldn't boot, then I had a look in the advanced options of CWM and the top option there was 'Reboot Recovery' so I thought I would give that a try as it seemed safe enough, but it's still running after several hours, this is what I've now got on my screen
ClockworkMod Recovery v5.0.1.5
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
87000
The 87000 figure started at 1, and is still rising. Is there any intelligent person who could help me, I would be very grateful.

Okay, well, I ended up just switching the phone off to get out of 'Reboot Recovery', but I've still got the same text on my recovery screen
# MANUAL MODE #
-- Appling Multi-CSC...
E:failed to mount /system (Invalid argument)
can't mount '/system' (Invalid argument)
E:failed to mount /system (Invalid argument)
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_install
Does anyone know what should be done?

Why dont you try and flash a stock rom from gb using pc Odin. And then go from there

Belfia said:
Why dont you try and flash a stock rom from gb using pc Odin. And then go from there
Click to expand...
Click to collapse
Thank you for that suggestion, I should have thought to try that myself, unfortunately, it didn't work.
Odin seems to have stuck at this:
<ID:0/018> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLPY_N7000OXALPY_N7000XXLPT_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/018> Odin v.3 engine (ID:18)..
<ID:0/018> File analysis..
<ID:0/018> SetupConnection..
<ID:0/018> Initialzation..
<ID:0/018> Get PIT for mapping..
<ID:0/018> Firmware update start..
<ID:0/018> factoryfs.img
<ID:0/018> NAND Write Start!!
Actually, I've just noticed you said
flash a stock rom from gb
Click to expand...
Click to collapse
so should I try to find/install a gb rom first, then reinstall the ICS rom?

Yes thats what I meant.

I've tried to flash a stock gingerbread rom, and still no success, slightly different to how it previously stopped though
<ID:0/019> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLA6_N7000XXLA4_N7000XEULA1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/019> Odin v.3 engine (ID:19)..
<ID:0/019> File analysis..
<ID:0/019> SetupConnection..
<ID:0/019> Initialzation..
<ID:0/019> Get PIT for mapping..
<ID:0/019> Firmware update start..
<ID:0/019> cache.img
<ID:0/019> NAND Write Start!!
I am feeling so down right now, I need my phone, and there's a lot of non backed-up data on it.

Does anybody have any suggestions?

I'm sorry but it looks like you managed to brick your phone. There are several threads on how to recover from that. Try them, thats the best tip I can give you.

StewB said:
Does anybody have any suggestions?
Click to expand...
Click to collapse
Well, you can try to search the correct .pit file for your note (16 or 32 gb) and then flash again a stock ROM using pit you've downloaded and selecting re-partition option also.
Sent from my n7000 using tapatalk 2

[XIX]Secutor said:
Well, you can try to search the correct .pit file for your note (16 or 32 gb) and then flash again a stock ROM using pit you've downloaded and selecting re-partition option also.
Sent from my n7000 using tapatalk 2
Click to expand...
Click to collapse
Last night I tried this, and shortly after starting, progress stopped, with the top left box of odin showing 'Set Partition'. I decided to leave it overnight, during which, the phone battery had died. I tried it again with a full battery, and it's stopped in the same place as before
<ID:0/019> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLPY_N7000OXALPY_N7000XXLPT_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/019> Odin v.3 engine (ID:19)..
<ID:0/019> File analysis..
<ID:0/019> SetupConnection..
<ID:0/019> Initialzation..
<ID:0/019> Set PIT file..
<ID:0/019> DO NOT TURN OFF TARGET!!
I'm running out of hope as I really thought this would work

I would recommend you try flashing back to Abyss 3.9 Kernel, as per Rocket ROM OP. Follow instructions carefully and ensure flash into Recovery before flashing ICS. I am on RR 4.1 using this method (twice) and all ok.

TempusFudgeIt said:
try flashing back to Abyss 3.9 Kernel, as per Rocket ROM OP. Follow instructions carefully and ensure flash into Recovery before flashing ICS.
Click to expand...
Click to collapse
I've been searching for a while for the instructions which you mention, could you please post a link.

Thank you to all who offered advise, however, nothing which I tried worked, so my phone is now with a Samsung Service Centre and I'll hopefully get it back soon without have all my data wiped.
I'm not going to be a one thread member though, I will stick around in this forum, even if it's just an occasional post.

StewB said:
Okay, well, I ended up just switching the phone off to get out of 'Reboot Recovery', but I've still got the same text on my recovery screen
# MANUAL MODE #
-- Appling Multi-CSC...
E:failed to mount /system (Invalid argument)
can't mount '/system' (Invalid argument)
E:failed to mount /system (Invalid argument)
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_install
Does anyone know what should be done?
Click to expand...
Click to collapse
I have exactly the same problem and i need help too

Stevoxda said:
I have exactly the same problem and i need help too
Click to expand...
Click to collapse
It seems like you are using stock recovery. What ROM you are on ? Is your device rooted ? Do you have CWM installed ?
If you have CWM installed
Go To Recovery
Mounts and Storage
Format System
Format Data
Format Cache
Reboot Recovery
Now flash Abyss
Wipe Cache/Dalvik
Wipe Data
Flash Rom
Reboot System

Stevoxda said:
I have exactly the same problem and i need help too
Click to expand...
Click to collapse
Did you try the advice posted by sahilarora2003?
When I got my phone back from the Samsung Service Centre, everything was gone, it was like having a new phone again (not what I wanted). I did manage to get some things back using a 'MyBackup Pro' backup, but I did lose quite a bit. I hope you're luckier than I was :fingers-crossed:

Help internal mmc block !! galaxytab P1000

recently my galaxy tab keep crashing till it suck in the startup in a flashing logo of samsung
i tried odin never works then i went to samsung maintenance they say u hav to change the motherboard !!
i really dont think the problem from the board i really hope it can be fixed by using some kind of software
here is the text that i got from the recovery mode
--verfing internal mmc block
E: failed to mount mmc : open file
internal mmc checksum verify failed.
#MANUAL MODE#
--updating application ...
E: failed to mount /preload (no such file or directory)
E: install_application_for_customer:cant mount / preload
your storgare not prepare yet , please use UI menu for for format and reboot actions .
--Appling multi-csc...
installing multi -csc
multicsc : scan access to ojxcom .
multicsc : opera mini[lib] reset .
appliedthe CSC-code 'xss'.
successfully applied multi-csc .
Click to expand...
Click to collapse

I think the problem should be solved if you restock to stable gingerbread.. .
Sent from my GT-P1000 using xda app-developers app

tnx for the reply
i tried gingerbread it never works :/ kies cant open the tab my rom was froyo 2.2

He meant you should flash GB using Odin, not upgrade via Kies.
Follow my signature, download Overcome's PDF guide, and GB-Stock-Safe-v5 (it has all the tools you need in it).
Open the guide, jump to page 7, put tab to download mode, and flash according to that guide.

so no need to kies. cuz when it happen i tried other tut required kies i couldn't pass the first stage in oden then it bricked
i'll try it hope it will work tnx guys

sorry guys same result
it failed in the end of first stage
i got this message in odin
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.bin
<ID:0/004> cache.rfs
<ID:0/004> dbdata.rfs
<ID:0/004> factoryfs.rfs
<ID:0/004> movinand.mst
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse

Looks like a bad internal sd chip.

Follow ChrisCTX's guide...search for it
Sent from my GT-P1000 using xda app-developers app

[GUIDE] EFS/NV_DATA full backup and restore manually -- Extract / Post your pit file

Here i will show you how to backup & restore EFS and NV_data manually for some variants of Galaxy S5 without a third party app or tool.
Sure a third party app or tool will do the job, but it is good to learn something.....
Backuping efs partition is an essential step to keep it safe after rooting since a bad flashing/modding of your S5 may result in a corruption of that partition. so it is better to be safe than sorry, so any disturbance in the EFS data might result in null IMEI and baseband version.
This will backup data like device specific essential information such as the IMEI (International Mobile Station Equipment Identity), wireless device MAC address, baseband version, product code, system ID and NV data.
You must have a proper root access in addition to busybox installed (preferred)
you can dump these partitions also using adb shell command. but here i will show you how to backup using a terminal emulator.
{
"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"
}
How to do it ​
Backup EFS/NV_data for SM-G900F/T/P/A/I/M/W8 variants:
Download "terminal emulator" app from play store and install it.
Open the app and type:
Code:
su
Grant permission
Code:
dd if=/dev/block/mmcblk0p12 of=/mnt/sdcard/efs.img.ext4
dd if=/dev/block/mmcblk0p13 of=/mnt/sdcard/modemst1.bin
dd if=/dev/block/mmcblk0p14 of=/mnt/sdcard/modemst2.bin
copy images from internal sdcard to a safe place such as pc.
Note that the size of .img and .bin must be as follow: efs (14MB) modemst1/2 (3MB each)
Restore EFS/NV_data for SM-900F/T/P/A/I/M/W8 variants:
Make sure Backuped images are in your internal sdcard (not in any folder).
open terminal emulator and type (HERE DONT MAKE MISTAKES!) :
Code:
su
dd if=/mnt/sdcard/efs.img.ext4 of=/dev/block/mmcblk0p12
dd if=/mnt/sdcard/modemst1.bin of=/dev/block/mmcblk0p13
dd if=/mnt/sdcard/modemst2.bin of=/dev/block/mmcblk0p14
​Backup EFS/NV_data for SG-900H variant:
Download "terminal emulator" app from play store and install it.
Open the app and type:
Code:
su
Grant permission
Code:
dd if=/dev/block/mmcblk0p3 of=/mnt/sdcard/efs.img.ext4
dd if=/dev/block/mmcblk0p4 of=/mnt/sdcard/m9kefs1.bin
dd if=/dev/block/mmcblk0p5 of=/mnt/sdcard/m9kefs2.bin
dd if=/dev/block/mmcblk0p6 of=/mnt/sdcard/m9kefs3.bin
copy images from internal sdcard to a safe place such as pc.
Note that sizes of .img and .bin must be as follow: efs (20MB) m9kefs1/2/3 (4MB each)
Restore EFS/NV_data for SG-G900H variant:
Make sure Backuped images are in your internal sdcard (not in any folder).
open terminal emulator and type (HERE DONT MAKE MISTAKES!):
Code:
su
dd if=/mnt/sdcard/efs.img.ext4 of=/dev/block/mmcblk0p3
dd if=/mnt/sdcard/m9kefs1.bin of=/dev/block/mmcblk0p4
dd if=/mnt/sdcard/m9kefs2.bin of=/dev/block/mmcblk0p5
dd if=/mnt/sdcard/m9kefs3.bin of=/dev/block/mmcblk0p6
​

pit files
Extract / Post your pit file​
Pit file is needed to be flashed when the partition table of your device is corrupted due to some reason such as a wrong flash of your variant.
When partition table is corrupted or missed from your device, odin will tell you when flashing firmware that there is "no pit partition" or "Re-Partition operation failed", in this case pit file must be flashed along with the stock firmware (or alone) with "re-partition" ticked in odin.
--DO NOT flash pit file if there is no need for it--
There is some ways to extract pit file from your device such as using "heimdall" or some tools.
Here i will show you how to extract the pit file manually with a simple way using terminal emulator or adb shell command.
your phone must have a proper root access, with busybox installed (preferred).​
how to do it​
With terminal emulator:
Download and install terminal emulator from play store.
Open it and type:
Code:
su
Grant permission
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=580 skip=2176
See the pit file in your internal sdcard, move it to pc
With adb shell:
You must have android sdk installed in your pc.
Enable "usb debugging" in "developer options", connect your phone to pc, open a cmd window (shift+right mouse click) and type:
Code:
adb devices
adb shell
su
Grant permission
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=580 skip=2176
See your pit file in your internal sdcard and move it to pc.
​Please attach the extracted pit file in a zip in this thread and mention your S5 variant name and storage (16/32GB) that other users can benefit from it
THX to
@linty
@xtechx
@fffft
@jeffreylin_
@tdunham
@ratatouille
@LoSt180
@babygau
@felstar
@born4trance
@demdix
@qwerty22
@/ofAllEvil
@Max One
@hawst
 @androidrouen

reserved

attachment and content removed, can delete post if desired.

xtechx said:
thanks! I've attached a PIT from my phone, if anyone needs it
Click to expand...
Click to collapse
hmm... can not open it with pit magic tool
there is something wrong.
can you post outcome of
Code:
cat /proc/partitions

attachment and content removed, can delete post if desired.

xtechx said:
weird. I'm running it from Ubuntu 14.04, x64, but I don't think that should matter. I have a couple Windows systems here too... I'm suspect of this cable, it seemed to damage a zip file I tried to flash once (was supposed to be 570MB< but it only copied 70MB)...but everything else has copied fine, including that file when I did it a second time...so not sure...
I re-ran the command, just in case. I've also included the output from /proc/partitions
addition: this time I zipped it on my computer, where as last time I zipped it with root explorer
Click to expand...
Click to collapse
ok, try with this command
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=580 skip=2176

samersh72 said:
ok, try with this command
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=580 skip=2176
Click to expand...
Click to collapse
Done

xtechx said:
Done
Click to expand...
Click to collapse
:good: yes it worked!
thank you
i will add it to second post

samersh72 said:
:good: yes it worked!
thank you
i will add it to second post
Click to expand...
Click to collapse
You're welcome! I'll edit my posts to remove the bad zip files, so that no one downloads them by mistake.

SM-G900F pit file added.

Looking for someone rooted that is willing to create an SM-G900T (Tmobile) PIT that can be used with Heimdall or JOdin. No Windows machines in my house.
Thanks!

i have this error msg with SM-G900F pit
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1ANCE_G900FAUT1ANC7_G900FXXU1ANCE_HOME.tar .md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse

joeknoob said:
i have this error msg with SM-G900F pit
Click to expand...
Click to collapse
I see problem in connection at first flash
But in second step Pit is set properly.
Odin troubleshooting: If Odin accidentally gives you "fail" try the following:
- Repeat procedure.
- Make sure that all actions of Kies are disabled from task manager.
- Change usb port.
- Try another usb cable (make sure it is the original).
- Try another Odin version.
- Uninstall and re-install driver.
- Try another computer
Why you are flashing with pit?
Sent from my N91

It seems that certain G900F S5 had a different partition layout that could cause flashing to fail on the "size" of Hidden.img. (as Note 3 phone)
I need some users from different countries with a SM-G900F (16GB) to extract pit file from their rooted phones (follow second post of this thread).
thanks in advance

..

samersh72 said:
It seems that certain G900F S5 had a different partition layout that could cause flashing to fail on the "size" of Hidden.img. (as Note 3 phone)
I need some users from different countries with a SM-G900F (16GB) to extract pit file from their rooted phones (follow second post of this thread).
thanks in advance
Click to expand...
Click to collapse
i need pit for my G900F - 16GB AUT (Switzerland)
this is reason for my flashfail
(sorry for my bad english)

jeffreylin_ said:
.pit file for the SM-G900H 16 GB variant.
Click to expand...
Click to collapse
thank you, but the zip is empty!?

jeffreylin_ said:
Huh, that was weird. Let me try that again.
Click to expand...
Click to collapse
Pit Zip added! thank you :good:

samersh72 said:
It seems that certain G900F S5 had a different partition layout that could cause flashing to fail on the "size" of Hidden.img. (as Note 3 phone)
I need some users from different countries with a SM-G900F (16GB) to extract pit file from their rooted phones (follow second post of this thread).
thanks in advance
Click to expand...
Click to collapse
Hi.
I have this problem too. I`m searching pit file g900f for firmware (SER) region Russia. Maybe you have this file?

Help with extracting AT&T S5 G900A Stock Rom and change Language

hi guys i need your help
my phone S5 G900A AT&T Rom 5.1.1 With no root and can't downgrade or add custom recovery
i need unpack to change my phone language and delete AT&T Programs in lollipop ROM 5.1.1 stock ROM
I made the next steps.. if could clarify the wrongs in those steps .. thank you very much
i am using ubuntu 16.04 LTS
first : i have stock ROM with 4 files AP - BL - CP - CSC
G900AUCU4COI5_CL5869384_QB6398515_REV00_user_low_s hip_MULTI_CERT
i need to extract AP_G900AUCU4COI5_CL5869384_QB6398515_REV00_user_lo w_ship_MULTI_CERT.tar.md5
and edit system.img.ext4
by right click on file system.img.ext4 and open with ARK and extract it
now i have those files boot.img - persist.img.ext4 - recovery.img - system.img.ext4
I've downloaded "img-tools" to change ext4 to img
i take a system.img.ext4 file and but it in img-tools folder in my home and do this commands
right click and chose Open in Terminal in img-tools folder
sudo su
enter password
simg2img system.img.ext4 system.img
makdir system
mount -t ext4 -o loop system.img system/
Click to expand...
Click to collapse
now i have mounted system.. i well open it with this command
sudo nautilus
enter password
Click to expand...
Click to collapse
and delete APK files >
Code:
system/APP/*.APK
system/framework/framework-res.apk
system/framework/twframework-res.apk from the same ROM
and replace it with the same files from other ROM S5 G900H lollipop 5.1.1 with national language
when finished i need to repack files with this command
tune2fs -l system.img | grep "Block size"
Block size: 4096
tune2fs -l system.img | grep "Block count"
Block count: 656384
ech $((4096 * 656384))
2688548864
make_ext4fs -s -l 2688548864 -a system system.img.ext4 system
Click to expand...
Click to collapse
now i have my edited sysytem.img.ext4
i need to but it back in the same folder with the next files to repack it in "tar.md5" file to flash it
Code:
boot.img
persist.img.ext4
recovery.img
this commands well do it
tar -H ustar -c boot.img persist.img.ext4 recovery.img system.img.ext4 > my_final_packeg.tar
md5sum -t my_final_packeg.tar >> my_final_packeg.tar
mv my_final_packeg.tar my_final_packeg.tar.md5
Click to expand...
Click to collapse
finally i have the last file to flash it ((my_final_packeg.tar.md5))
the problem is when i flash it by odin3 v3.11 i have this massage
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1101)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> persist.img.ext4
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL (auth)!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
i need your help and Sorry about my bad language