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
It seems that my I9000T from Claro Guatemala has managed to brick itself. I had it in download mode, connected to my Ubuntu computer running Heimdall Frontend. I clicked the Print PIT button under Utilities and received an error saying that heimdall had crashed.
Now the phone is stuck between the infamous BSOD or, if I hold down the magic 3 key combo long enough, download mode.
I did not attempt to flash any files, the phone still has (had?) the stock 2.1 firmware.
It seems like my only option at this point is to go ahead and try to flash a different ROM. Is that correct?
Ok, I am up and running with an update from Claro CR.
I grabbed the file from here: http://forum.xda-developers.com/showpost.php?p=25480021&postcount=33
Unpacked everything into a single folder, put the brick into download mode, and ran the following command:
~/Descargas/Gt I9000t Galaxy 2.3$ sudo heimdall flash --repartition --pit s1_odin_20100512.pit --factoryfs factoryfs.rfs --cache cache.rfs --dbdata dbdata.rfs --primary-boot boot.bin --secondary-boot Sbl.bin --param param.lfs --kernel zImage --modem modem.bin --verbose
So now I am running an updated firmware, and the phone appears to fully functional. I say appears because i am in an area with limited cell coverage, it will have to wait for the morning to test everything fully.
apater said:
I clicked the Print PIT button under Utilities and received an error saying that heimdall had crashed.
Click to expand...
Click to collapse
What heimdall version You use? I use v1.3.1 and its work
-----------------------------------------------------------------------
Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
.
.
.
--- Entry #12 ---
Unused: Yes
Partition Type: 1 (Unknown)
Partition Identifier: 11
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name:
Filename:
Ending session...
Rebooting device...
Re-attaching kernel driver...
The Heimdall-Frontend is version 1.3.2
It may be that my phone is from Claro/Telcel and they have some funky bootloaders that other I9000's don't have.
I was able to un-brick the phone by flashing (via the heimdall cli) firmware from Claro PR.
Well i dumped my own rom and did this:
Code:
tar -H ustar -c zImage boot.bin modem.bin Sbl.bin cache.img data.img factoryfs.img hidden.img param.lfs > odin.tar
md5sum -t odin.tar >> odin.tar
mv odin.tar odin.tar.md5
It does create a valid flashable image for Odin... but the problem is that it increases the binary counter!
Anyone know how can i create a tar image without increasing it?
Since no one replied and in case anyone is wondering: to make a repack just use the stock kernel because a custom recovery increases the binary.. As simples as that
Sent from my GT-N7000 using Tapatalk 2
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?
I bricked my phone by flashing the wrong zip in FlashFire. It hung at the ATT logo or powered off after the Samsung logo. The following method allowed me to restore it back to factory I537UCUCNE3 (4.4.2):
Boot into Odin Dowload Mode:
http://forum.xda-developers.com/wiki/Odin_mode#Entering_Odin_mode
Code:
$ unzip SGH-I537UCUCNE3_v4.4.2_ATT_ALL.zip
$ tar -xf AP_I537UCUCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5
$ tar -xf BL_I537UCUCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5
$ tar -xf CP_I537UCUCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5
$ tar -xf CSC_ATT_I537ATTCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5
$ heimdall flash --pit JACTIVELTE_USA_ATT.pit --APNHLOS NON-HLOS.bin --MDM modem.bin --SBL1 sbl1.mbn --SBL2 sbl2.mbn --SBL3 sbl3.mbn --ABOOT aboot.mbn --RPM rpm.mbn --TZ tz.mbn --PERSDATA persdata.img.ext4 --SYSTEM system.img.ext4 --CACHE cache.img.ext4 --BOOT boot.img --RECOVERY recovery.img
zip obtained here:
http://forum.xda-developers.com/showthread.php?t=2629093
heimdall obtained here:
http://ftp.us.debian.org/debian/pool/main/h/heimdall-flash/heimdall-flash_1.4.0-2_amd64.deb
I hope this is able to help others who have locked bootloaders but rooted ROMs on SGS4A and have corrupted their ROMs as a result of a bad flash or similar. ENjoy!
Thanks ... and small typo.
First of all, many thanks for the post. It saved me! Second, I think you have a typo -- I believe JACTIVELTE_USA_ATT_16G.pit should be JACTIVELTE_USA_ATT.pit. Or at least, that's what I had to change to get everything to work.
z_thompsonpa said:
I bricked my phone by flashing the wrong zip in Flash Gordon. It hung at the ATT logo or powered off after the Samsung logo. The following method allowed me to restore it back to factory I537UCUCNE3 (4.4.2):
Boot into Odin Dowload Mode:
http://forum.xda-developers.com/wiki/Odin_mode#Entering_Odin_mode
Code:
$ unzip SGH-I537UCUCNE3_v4.4.2_ATT_ALL.zip
$ tar -xf AP_I537UCUCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5
$ tar -xf BL_I537UCUCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5
$ tar -xf CP_I537UCUCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5
$ tar -xf CSC_ATT_I537ATTCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5
$ heimdall flash --pit JACTIVELTE_USA_ATT_16G.pit --APNHLOS NON-HLOS.bin --MDM modem.bin --SBL1 sbl1.mbn --SBL2 sbl2.mbn --SBL3 sbl3.mbn --ABOOT aboot.mbn --RPM rpm.mbn --TZ tz.mbn --PERSDATA persdata.img.ext4 --SYSTEM system.img.ext4 --CACHE cache.img.ext4 --BOOT boot.img --RECOVERY recovery.img
zip obtained here:
http://forum.xda-developers.com/showthread.php?t=2629093
heimdall obtained here:
http://ftp.us.debian.org/debian/pool/main/h/heimdall-flash/heimdall-flash_1.4.0-2_amd64.deb
I hope this is able to help others who have locked bootloaders but rooted ROMs on SGS4A and have corrupted their ROMs as a result of a bad flash or similar. ENjoy!
Click to expand...
Click to collapse
fbshapiro said:
First of all, many thanks for the post. It saved me! Second, I think you have a typo -- I believe JACTIVELTE_USA_ATT_16G.pit should be JACTIVELTE_USA_ATT.pit. Or at least, that's what I had to change to get everything to work.
Click to expand...
Click to collapse
You are right. I had to revisit these steps recently when I upgraded to OC7.
If reflashing ML2, that rom uses pit file named, JACTIVELTE_USA_ATT_16G.pit
If reflashing NE3, that rom uses pit file named, JACTIVELTE_USA_ATT.pit
When following the Lollipop Root Method mentioned here:
Once the flash is complete and the device reboots into "Download" mode, flash the I537_OC7_Bootloader using Odin's PDA/AP slot.
Click to expand...
Click to collapse
If you want to use Linux just substitute the following for the Odin step mentioned above:
Code:
tar -xf I537_OC7_Bootloader.tar.md5
heimdall flash --SBL2 sbl2.mbn --SBL3 sbl3.mbn --ABOOT aboot.mbn --RPM rpm.mbn --TZ tz.mbn