Hi there.
As I promised, here is a full rom of YP-G70 8G INTERNATIONAL version. Based on G70ZSKP8. This is for recovery pruposes (ex. bricked device).
You will need:
- Odin.
- PIT file. Download here.
- ROM. Download here.
Flash it with odin. If you hard-bricked your device, make sure you hit re-partition and phone bootoader update.
What technique or program did you use specifically to identify and extract this partitions files.
The PIT file was pulled with Heimdall (doing a dd dump gets the same file but instead of 4k, you get a 256k file). Also, you can print the output to see which filename of the rom gets on every partition when Odin flashes it.
Also checked the partition table with fdisk and their size. Here is the output:
Code:
# partition table of /dev/mmcblk0
unit: sectors
/dev/mmcblk0p1 : start= 64, size= 15515584, Id= 5
/dev/mmcblk0p2 : start= 0, size= 0, Id= 0
/dev/mmcblk0p3 : start= 0, size= 0, Id= 0
/dev/mmcblk0p4 : start= 0, size= 0, Id= 0
/dev/mmcblk0p5 : start= 128, size= 512, Id=83
/dev/mmcblk0p6 : start= 704, size= 512, Id=83
/dev/mmcblk0p7 : start= 1280, size= 2560, Id=83
/dev/mmcblk0p8 : start= 3904, size= 2560, Id=83
/dev/mmcblk0p9 : start= 6528, size= 10240, Id=83
/dev/mmcblk0p10: start= 16832, size= 20480, Id=83
/dev/mmcblk0p11: start= 37376, size= 15360, Id=83
/dev/mmcblk0p12: start= 52800, size= 15360, Id=83
/dev/mmcblk0p13: start= 68224, size= 593920, Id=83
/dev/mmcblk0p14: start= 662208, size= 274432, Id=83
/dev/mmcblk0p15: start= 936704, size= 131072, Id=83
/dev/mmcblk0p16: start= 1067840, size= 3940352, Id=83
/dev/mmcblk0p17: start= 5008256, size= 10504192, Id=83
This output is useful for those have their partition table destroyed. I had to manually repartition my device.
Then, using dd, I dumped every partition of /dev/block/mmcblk0 and renamed they to match. Finally I packed the file.
In the pit file you linked to, there is a reference to a inand_8G.bin file how would you go about IDing that file and extracting it and of the partitions you listed above which one holds the inand_8G.bin file.
ishish9 said:
In the pit file you linked to, there is a reference to a inand_8G.bin file how would you go about IDing that file and extracting it and of the partitions you listed above which one holds the inand_8G.bin file.
Click to expand...
Click to collapse
In fact, no partition holds inand_8G.bin. Look at heimdall PIT output:
Code:
Beginning session...
Session begun with device of type: 0
Downloading device's PIT file...
PIT file download sucessful
Entry Count: 14
Unknown 1: 15718400
Unknown 2: 1
Unknown 3: 0
Unknown 4: 0
Unknown 5: 7703
Unknown 6: 237
Unknown 7: 62704
Unknown 8: 18
--- Entry #0 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 1
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 1
Unknown 2: 0
Unknown 3: 0
Partition Name: IBL+PBL
Filename: boot.bin
--- Entry #1 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 2
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 1
Unknown 2: 0
Unknown 3: 0
Partition Name: PIT
Filename: YPG70_8G-0304.pit
--- Entry #2 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 3
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 5
Unknown 2: 0
Unknown 3: 0
Partition Name: SBL
Filename: Sbl.bin
--- Entry #3 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 4
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 5
Unknown 2: 6226025
Unknown 3: 7143533
Partition Name: SBL2
Filename: Sbl.bin
--- Entry #4 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 5
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 20
Unknown 2: 0
Unknown 3: 0
Partition Name: PARAM
Filename: param.lfs
--- Entry #5 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 6
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 40
Unknown 2: 39021280
Unknown 3: 7143533
Partition Name: EFS
Filename: efs.rfs
--- Entry #6 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 7
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 30
Unknown 2: 36662408
Unknown 3: 0
Partition Name: KERNEL
Filename: zImage
--- Entry #7 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 8
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 30
Unknown 2: 6684793
Unknown 3: 3014771
Partition Name: RECOVERY
Filename: zImage
--- Entry #8 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 9
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 1160
Unknown 2: 0
Unknown 3: 0
Partition Name: FACTORYFS
Filename: factoryfs.rfs
--- Entry #9 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 10
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 536
Unknown 2: 6684780
Unknown 3: 115
Partition Name: DBDATAFS
Filename: dbdata.rfs
--- Entry #10 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 11
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 256
Unknown 2: 115
Unknown 3: 115
Partition Name: CACHE
Filename: cache.rfs
--- Entry #11 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 12
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 7696
Unknown 2: 0
Unknown 3: 0
Partition Name: DATAFS
Filename: datafs.rfs
--- Entry #12 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 13
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 20516
Unknown 2: 0
Unknown 3: 0
Partition Name: USERFS
Filename: userfs_8G.rfs
--- Entry #13 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 0
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name: GANG
Filename: inand_8G.bin
In the partition table I posted earlier, last partition is mmcblk0p17, which contains datafs.rfs. I think that reference is only to show that the PIT file is for 8G. The inand_8G.bin's partition size is 0 bytes.
I know it shows up there as having no information but I have a file from a GANG partition that does have information in it, about 100 Megabytes, now that maybe simply place holder information but it is a partition and it may contain some information how ever little it may actually be. Also looking at the file I got from a GANG partition in a Hex editor the first words that appear are "FATHEAD" this link here has some information about it.
ishish9 said:
I know it shows up there as having no information but I have a file from a GANG partition that does have information in it, about 100 Megabytes, now that maybe simply place holder information but it is a partition and it may contain some information how ever little it may actually be. Also looking at the file I got from a GANG partition in a Hex editor the first words that appear are "FATHEAD" this link here has some information about it.
Click to expand...
Click to collapse
I'll look into it.
When I recovered my galaxy player I did a full dd dump of the mmcblk0 contents. I know it's "hacky", but it worked.
Is there any way you could post the ROM again as it is no longer available via your link.
My YP-G70 turned to a black screen after running google play movies. And since the battery cannot be easilly pulled I feel a flash is in order
Update:
Nevermind I found that I can pull the battery so I just did
Could some one be so kind to repost til full recovery file please.
Update: used this http://forum.xda-developers.com/showpost.php?p=19840746&postcount=420
And som grat help from rumirand, and my player int. is running again.
ident
I've not bricked my device. I'm using Erygit Custom-Rom V3.0 and rj kernel ( I downgraded from PA).
I just want to go back to original factory setting, can I use your ROM and just use it with Odin, without using the PIT file as my device is not bricked.
jamaljan said:
I've not bricked my device. I'm using Erygit Custom-Rom V3.0 and rj kernel ( I downgraded from PA).
I just want to go back to original factory setting, can I use your ROM and just use it with Odin, without using the PIT file as my device is not bricked.
Click to expand...
Click to collapse
XXKPL is much newer, and the available Odin package for it will do exactly what you want.
Mevordel said:
XXKPL is much newer, and the available Odin package for it will do exactly what you want.
Click to expand...
Click to collapse
thanks. is this what you are referring to ?
http://androidromupdate.com/2012/05...-g70-international-to-android-2-3-6-firmware/
jamaljan said:
thanks. is this what you are referring to ?
http://androidromupdate.com/2012/05...-g70-international-to-android-2-3-6-firmware/
Click to expand...
Click to collapse
That looks like the right thing, yes.
Related
Hi fellas,
I was returning from miui to stock rom, but forgot to do wipe.
After doing a lot of things my phone is in this condition:
- able to get into donwload mode;
- in recovery mode (it shows failed to mount /efs and /system)
- the recovery mode has only few options (android system recovery <3e>) reboot / apply update from external storage / wipe data / wipe cache / apply update from cache
- odin recognizes it, but I always get stuck at "nand write..." step ( repartioning works, and I use the pit for 16gb units)
- heimdall is able to read all the partitions and lists it to me
- I'm not able to get it recognized by samsung s3 toolkit - adb
- I have another unit in white color, that is recognized by samsung s3 toolkit
I hope someone with advanced skills and patience could help me solve this issue
----edited----
I managed to install ClockWorkMod Touch, installed MIUI again from a zip file without error, cleaned the cache, fixed permissions, but it still not booting.
As I said, I have another unit of this in fully working condition, can I copy the efs content to the bricked one?
This is what I got when I use "read partition" from Heimdall
If this is a clue to what is happening please let me know
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 131072
Downloading device's PIT file...
PIT file download sucessful
Entry Count: 16
Unknown 1: 1598902083
Unknown 2: 1129139525
Unknown 3: 12365
Unknown 4: 17199
Unknown 5: 49
Unknown 6: 0
Unknown 7: 0
Unknown 8: 0
--- Entry #0 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 50
Partition Flags: 2 (R/W)
Unknown 1: 1
Partition Block Size: 0
Partition Block Count: 1734
Unknown 2: 0
Unknown 3: 0
Partition Name: BOOTLOADER
Filename: sboot.bin.md5
--- Entry #1 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 51
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 1734
Partition Block Count: 312
Unknown 2: 0
Unknown 3: 0
Partition Name: TZSW
Filename: tz.img.md5
--- Entry #2 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 70
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 34
Partition Block Count: 16
Unknown 2: 0
Unknown 3: 0
Partition Name: PIT
Filename: mx.pit.md5
--- Entry #3 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 71
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 50
Partition Block Count: 2048
Unknown 2: 0
Unknown 3: 0
Partition Name: SMDHDR
Filename: smdhdr.bin.md5
--- Entry #4 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 1
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 8192
Partition Block Count: 4096
Unknown 2: 0
Unknown 3: 0
Partition Name: BOTA1
Filename:
--- Entry #5 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 2
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 12288
Partition Block Count: 4096
Unknown 2: 0
Unknown 3: 0
Partition Name: BOTA2
Filename:
--- Entry #6 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 3
Partition Flags: 5 (R)
Unknown 1: 5
Partition Block Size: 16384
Partition Block Count: 40960
Unknown 2: 0
Unknown 3: 0
Partition Name: EFS
Filename: efs.img.md5
--- Entry #7 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 4
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 57344
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: PARAM
Filename: param.bin.md5
--- Entry #8 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 5
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 73728
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: BOOT
Filename: boot.img.md5
--- Entry #9 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 6
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 90112
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: RECOVERY
Filename: recovery.img.md5
--- Entry #10 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 7
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 106496
Partition Block Count: 65536
Unknown 2: 0
Unknown 3: 0
Partition Name: RADIO
Filename: modem.bin.md5
--- Entry #11 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 8
Partition Flags: 5 (R)
Unknown 1: 5
Partition Block Size: 172032
Partition Block Count: 1638400
Unknown 2: 0
Unknown 3: 0
Partition Name: CACHE
Filename: cache.img.md5
--- Entry #12 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 9
Partition Flags: 5 (R)
Unknown 1: 5
Partition Block Size: 1810432
Partition Block Count: 2867200
Unknown 2: 0
Unknown 3: 0
Partition Name: SYSTEM
Filename: system.img.md5
--- Entry #13 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 10
Partition Flags: 5 (R)
Unknown 1: 5
Partition Block Size: 4677632
Partition Block Count: 614400
Unknown 2: 0
Unknown 3: 0
Partition Name: HIDDEN
Filename: hidden.img.md5
--- Entry #14 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 11
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 5292032
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: OTA
Filename:
--- Entry #15 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 12
Partition Flags: 5 (R)
Unknown 1: 5
Partition Block Size: 5308416
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name: DATA
Filename: userdata.img.md5
Ending session...
Rebooting device...
Which recovery are you on?
Sent from my GT-I9300 using xda premium
g3oron said:
Which recovery are you on?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I managed to install ClockWork Touch 6.0.27, and also installed miui without error from a zip file at sdcard, but it still fails to boot.
I installed CW, tried to wipe, fix permissions, but this actions didn't solve.
Hi, I'm sorry if this is a really dumb question. I'm trying to flash the O2 specific modem onto my Galaxy S3 which currently has the stock XXEMG4 firmware (and modem on it)
I initially tried the following command:
Code:
heimdall flash --modem modem.bin
and it tells me that the Partition modem doesn't exist
okay, so I've printed the PIT and it tells me the partition is called radio. I found an issue where they said they added the flag --radio and so I tried:
Code:
heimdall flash --radio modem.bin
This is my result:
Code:
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
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:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
ERROR: Partition "radio" does not exist in the specified PIT.
Ending session...
Rebooting device...
Releasing device interface...
Print-pit gives the following:
Code:
Downloading device's PIT file...
PIT file download successful.
Entry Count: 16
Unknown 1: 1598902083
Unknown 2: 844251476
Unknown 3: 30797
Unknown 4: 0
Unknown 5: 0
Unknown 6: 0
Unknown 7: 0
Unknown 8: 0
--- Entry #0 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 80
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 0
Partition Block Count: 1734
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOTLOADER
Flash Filename: sboot.bin
FOTA Filename:
--- Entry #1 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 81
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 1734
Partition Block Count: 312
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: TZSW
Flash Filename: tz.img
FOTA Filename:
--- Entry #2 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 70
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 34
Partition Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PIT
Flash Filename: mx.pit
FOTA Filename:
--- Entry #3 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 71
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 50
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MD5HDR
Flash Filename: md5.img
FOTA Filename:
--- Entry #4 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 1
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 8192
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOTA0
Flash Filename: -
FOTA Filename:
--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 2
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 16384
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOTA1
Flash Filename: -
FOTA Filename:
--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 3
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 24576
Partition Block Count: 40960
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash Filename: efs.img
FOTA Filename:
--- Entry #7 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 4
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 65536
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash Filename: param.bin
FOTA Filename:
--- Entry #8 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 5
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 81920
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash Filename: boot.img
FOTA Filename:
--- Entry #9 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 6
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 98304
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash Filename: recovery.img
FOTA Filename:
--- Entry #10 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 7
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 114688
Partition Block Count: 65536
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RADIO
Flash Filename: modem.bin
FOTA Filename:
--- Entry #11 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 8
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 180224
Partition Block Count: 2097152
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHE
Flash Filename: cache.img
FOTA Filename:
--- Entry #12 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 9
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 2277376
Partition Block Count: 3145728
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SYSTEM
Flash Filename: system.img
FOTA Filename:
--- Entry #13 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 10
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 5423104
Partition Block Count: 1146880
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: HIDDEN
Flash Filename: hidden.img
FOTA Filename:
--- Entry #14 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 11
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 6569984
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: OTA
Flash Filename: -
FOTA Filename:
--- Entry #15 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 12
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 6586368
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: USERDATA
Flash Filename: userdata.img
FOTA Filename: remained
So entry 10 clearly says radio, any ideas what i'm doing wrong?
Also probably not the place to ask but while I'm here - is it okay to just flash a radio, I don't want to root or change anything else, just change the modem to try and improve the crap signal O2 give me
Modems can be changed see the modem thread .
jje
moviedrome said:
Hi, I'm sorry if this is a really dumb question. I'm trying to flash the O2 specific modem onto my Galaxy S3 which currently has the stock XXEMG4 firmware (and modem on it)
I initially tried the following command:
Code:
heimdall flash --modem modem.bin
and it tells me that the Partition modem doesn't exist
okay, so I've printed the PIT and it tells me the partition is called radio. I found an issue where they said they added the flag --radio and so I tried:
Code:
heimdall flash --radio modem.bin
This is my result:
Code:
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
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:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
ERROR: Partition "radio" does not exist in the specified PIT.
Ending session...
Rebooting device...
Releasing device interface...
Print-pit gives the following:
Code:
Downloading device's PIT file...
PIT file download successful.
Entry Count: 16
Unknown 1: 1598902083
Unknown 2: 844251476
Unknown 3: 30797
Unknown 4: 0
Unknown 5: 0
Unknown 6: 0
Unknown 7: 0
Unknown 8: 0
--- Entry #0 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 80
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 0
Partition Block Count: 1734
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOTLOADER
Flash Filename: sboot.bin
FOTA Filename:
--- Entry #1 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 81
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 1734
Partition Block Count: 312
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: TZSW
Flash Filename: tz.img
FOTA Filename:
--- Entry #2 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 70
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 34
Partition Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PIT
Flash Filename: mx.pit
FOTA Filename:
--- Entry #3 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 71
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 50
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MD5HDR
Flash Filename: md5.img
FOTA Filename:
--- Entry #4 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 1
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 8192
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOTA0
Flash Filename: -
FOTA Filename:
--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 2
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 16384
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOTA1
Flash Filename: -
FOTA Filename:
--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 3
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 24576
Partition Block Count: 40960
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash Filename: efs.img
FOTA Filename:
--- Entry #7 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 4
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 65536
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash Filename: param.bin
FOTA Filename:
--- Entry #8 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 5
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 81920
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash Filename: boot.img
FOTA Filename:
--- Entry #9 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 6
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 98304
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash Filename: recovery.img
FOTA Filename:
--- Entry #10 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 7
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 114688
Partition Block Count: 65536
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RADIO
Flash Filename: modem.bin
FOTA Filename:
--- Entry #11 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 8
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 180224
Partition Block Count: 2097152
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHE
Flash Filename: cache.img
FOTA Filename:
--- Entry #12 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 9
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 2277376
Partition Block Count: 3145728
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SYSTEM
Flash Filename: system.img
FOTA Filename:
--- Entry #13 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 10
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 5423104
Partition Block Count: 1146880
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: HIDDEN
Flash Filename: hidden.img
FOTA Filename:
--- Entry #14 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 11
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 6569984
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: OTA
Flash Filename: -
FOTA Filename:
--- Entry #15 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 12
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 6586368
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: USERDATA
Flash Filename: userdata.img
FOTA Filename: remained
So entry 10 clearly says radio, any ideas what i'm doing wrong?
Also probably not the place to ask but while I'm here - is it okay to just flash a radio, I don't want to root or change anything else, just change the modem to try and improve the crap signal O2 give me
Click to expand...
Click to collapse
You need to read the threads regarding the new modem set up, or you may end up losing your imei.......also the btu modem should be fine for you if your csc is set to btu
Hi guys!
A friend of mine has a I9100 16GB and tried rooting it in order to install a custom ROM. Somehow he failed, but he doesn't really know why. He asked me to try to fix it, but since I've never had a non-nexus Samsung device I feel kind of lost.
My goal is to revert to stock and then root it again or to go to a custom ROM directly.
The Recovery shows the symbol of a phone connect with a laptop and a warning sign.
I tried going back to stock JellyBean using many different versions of Odin on different computers but they all either failed or got stuck at "NAND write starts".
I don't know my way around pit files and as they seem to be very dangerous I want to avoid them as long as possible.
The last thing I did is to use Heimdall on my linux machine and print the devices pit (in case that helps). This is what it said
Code:
Entry Count: 15
Unknown 1: 0
Unknown 2: 0
Unknown 3: 0
Unknown 4: 0
Unknown 5: 0
Unknown 6: 0
Unknown 7: 0
Unknown 8: 0
--- Entry #0 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 0
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size: 0
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: GANG
Flash Filename: emmc.img
FOTA Filename:
--- Entry #1 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 1
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size: 0
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash Filename: boot.bin
FOTA Filename:
--- Entry #2 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 4
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size: 8192
Partition Block Count: 40960
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash Filename: efs.img
FOTA Filename:
--- Entry #3 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 2
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size: 49152
Partition Block Count: 2560
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBL1
Flash Filename: Sbl.bin
FOTA Filename:
--- Entry #4 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 3
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size: 53248
Partition Block Count: 2560
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBL2
Flash Filename:
FOTA Filename:
--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 5
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size: 57344
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash Filename: param.lfs
FOTA Filename:
--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 6
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size: 73728
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: KERNEL
Flash Filename: zImage
FOTA Filename:
--- Entry #7 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 7
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size: 90112
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash Filename:
FOTA Filename:
--- Entry #8 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 8
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size: 106496
Partition Block Count: 204800
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHE
Flash Filename: cache.img
FOTA Filename:
--- Entry #9 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 9
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size: 311296
Partition Block Count: 32768
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MODEM
Flash Filename: modem.bin
FOTA Filename:
--- Entry #10 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 10
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size: 344064
Partition Block Count: 1048576
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: FACTORYFS
Flash Filename: factoryfs.img
FOTA Filename:
--- Entry #11 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 11
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size: 1392640
Partition Block Count: 4194304
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: DATAFS
Flash Filename: data.img
FOTA Filename:
--- Entry #12 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 12
Attributes: 2 (STL Read-Only)
Update Attributes: 0
Partition Block Size: 5586944
Partition Block Count: 24133632
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: UMS
Flash Filename:
FOTA Filename:
--- Entry #13 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 13
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size: 29720576
Partition Block Count: 1048576
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: HIDDEN
Flash Filename: hidden.img
FOTA Filename:
--- Entry #14 ---
Binary Type: 1 (CP)
Device Type: 1 (File/FAT)
Identifier: 9
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size: 0
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name:
Flash Filename:
FOTA Filename:
What would be the best way for me to proceed now?
David.
Thread stickied near top of Q&A has instructions for flashing stock firmware, get a stock rom for country/carrier from Samfirmware if their files are up again, if not AndroidFirmwares.net or Samsung-Updates.com.
Edit: Pro tip - Given how few people here use Heimdall, the best bit of advice I can give you if you want to get this done quickly, use a Windoze machine/Odin. You might end up waiting a long time for the help you need with Heimdall.
Hello Everybody..
I Have an international SIII (GT-I9300) and I accidentally flashed it with SGH-I747 BOOTLOADER and PIT file. The phone can only boot to download mode showing PRODUCT NAME of SGH-i747 .
Full output :
Code:
PRODUCT NAME : SGH-I747
CUSTOM BINARY DOWNLOAD: Yes (18 counts)
CUSTOM BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 1
BOOTLOADER AP SWAEV: 2
I tried to flash low ship FACTORY Firmware with mx.pit also nand wipe and re-partition checked but odin fail to flash sboot.bin.
Full output :
Code:
ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9300XXALEF_611327_REV00_user_low_ship.tar.md 5 is valid.
<OSM> MODEM_I9300XXLEF_REV02_REV04_CL1147871.tar.md5 is valid.
<OSM> CSC_OXE_I9300OXEALE4_CL606160_REV00_user_low_ship. tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Also I tried heimdall and different odin visions with no luck.
And here is my pit :
Code:
sudo heimdall print-pit --verbose
output :
Code:
Heimdall v1.4.1
Copyright (c) 2010-2014 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/
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Entry Count: 27
Unknown 1: 1598902083
Unknown 2: 844251476
Unknown 3: 21325
Unknown 4: 14413
Unknown 5: 13881
Unknown 6: 48
Unknown 7: 0
Unknown 8: 0
--- Entry #0 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 1
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 8192
Partition Block Count: 122880
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MODEM
Flash Filename: NON-HLOS.bin
FOTA Filename:
--- Entry #1 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 2
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 131072
Partition Block Count: 256
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBL1
Flash Filename: sbl1.mbn
FOTA Filename:
--- Entry #2 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 3
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 131328
Partition Block Count: 512
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBL2
Flash Filename: sbl2.mbn
FOTA Filename:
--- Entry #3 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 4
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 131840
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBL3
Flash Filename: sbl3.mbn
FOTA Filename:
--- Entry #4 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 5
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 132864
Partition Block Count: 4096
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: ABOOT
Flash Filename: aboot.mbn
FOTA Filename:
--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 6
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 136960
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RPM
Flash Filename: rpm.mbn
FOTA Filename:
--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 7
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 137984
Partition Block Count: 20480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash Filename: boot.img
FOTA Filename:
--- Entry #7 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 8
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 158464
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: TZ
Flash Filename: tz.mbn
FOTA Filename:
--- Entry #8 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 9
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 159488
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PAD
Flash Filename:
FOTA Filename:
--- Entry #9 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 10
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 160512
Partition Block Count: 20480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash Filename:
FOTA Filename:
--- Entry #10 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 11
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 180992
Partition Block Count: 27904
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash Filename: efs.img.ext4
FOTA Filename:
--- Entry #11 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 12
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 208896
Partition Block Count: 6144
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MODEMST1
Flash Filename: nvrebuild1.bin
FOTA Filename:
--- Entry #12 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 13
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 215040
Partition Block Count: 6144
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MODEMST2
Flash Filename: nvrebuild2.bin
FOTA Filename:
--- Entry #13 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 14
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 221184
Partition Block Count: 3072000
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SYSTEM
Flash Filename: system.img.ext4
FOTA Filename:
--- Entry #14 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 15
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 3293184
Partition Block Count: 25665536
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: USERDATA
Flash Filename: userdata.img.ext4
FOTA Filename:
--- Entry #15 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 16
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 28958720
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PERSIST
Flash Filename: persist.img.ext4
FOTA Filename:
--- Entry #16 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 17
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 28975104
Partition Block Count: 1720320
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHE
Flash Filename: cache.img.ext4
FOTA Filename:
--- Entry #17 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 18
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 30695424
Partition Block Count: 20480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash Filename: recovery.img
FOTA Filename:
--- Entry #18 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 19
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 30715904
Partition Block Count: 20480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: FOTA
Flash Filename:
FOTA Filename:
--- Entry #19 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 20
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 30736384
Partition Block Count: 12288
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BACKUP
Flash Filename:
FOTA Filename:
--- Entry #20 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 21
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 30748672
Partition Block Count: 6144
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: FSG
Flash Filename:
FOTA Filename:
--- Entry #21 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 22
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 30754816
Partition Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SSD
Flash Filename:
FOTA Filename:
--- Entry #22 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 23
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 30754832
Partition Block Count: 10240
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: GROW
Flash Filename:
FOTA Filename:
--- Entry #23 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 70
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 0
Partition Block Count: 34
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PGPT
Flash Filename: pgpt.img
FOTA Filename:
--- Entry #24 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 71
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 34
Partition Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PIT
Flash Filename: MSM8960.pit
FOTA Filename:
--- Entry #25 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 72
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 50
Partition Block Count: 32
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MD5
Flash Filename: md5.img
FOTA Filename:
--- Entry #26 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 73
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 30777311
Partition Block Count: 33
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SGPT
Flash Filename: sgpt.img
FOTA Filename:
Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
Some points:
-Flashing recovery.img completes successfully but I can't boot to it.
-Flashing boot.img completes successfully and boot successfully.
Some solutions I tried :
-Flashing CWM recovery or CF root to access recovery then use busybox to flash sboot.bin, param.bin and tz.bin but I can't boot to recovery.
-Flashing BOATLOADER with PIT and re-partition enabled but did't work (same odin output).
-Flashing bootloader to sd card to boot from it (some say it really works but it didn't).
And some solutions I'm thinking of:
-Send it to JTAG service (but it's not available here)
-Flashing SGH-I747 recovery.img to restore bootloder.
-What?!
I need you help and your advise guys.
Sorry for my bad English
I've not heard a single case where a wrong flash was fixed by reflashing software alone. You'll need jtag at least, probably a new screen and/or motherboard.
Check out the 'dead boot solution' thread in general forum.
Hi, i bought an used galaxy s2 i777. It is stuck at Samsung logo, also for any unknown reason it doesn't charge the battery, if i try to enter in any charge mode (plug the phone to the charger for example) a gray battery icon appears with a circle in the middle (not moving) and stucks there forever.
Recovery doesn't work
Only download mode works
Stock binaries, nothing custom, i even think the phone is not even rooted
Tried flashing 3 different stock roms with odin, all of them fails at the beginning "Nand write start!" and then fail, it doesn't even start to write in the memory
Tried with heimdall, any partition that i want to flash stucks at 100%, and then after a long time, if i am lucky, i get a fail error, otherwise i have to unplug the phone
tried flashing Siyah kernel (idk for what, but just trying), still fails (upload 100% forever)
tried flashing a bootloader, still stuck at 100 (with heimdall) and then fails
tried with a .pit on Odin and it stucks on "Set pit file... DO NOT TURN OFF TARGET" forever, only tried with one pit found on a strange website, links here (dev-host) are dead
Here is what i got from Heimdall using "print-pit"
Code:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Entry Count: 15
Unknown 1: 18667528
Unknown 2: 1
Unknown 3: 0
Unknown 4: 0
Unknown 5: 7508
Unknown 6: 282
Unknown 7: 63520
Unknown 8: 37
--- Entry #0 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 0
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 0
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: GANG
Flash Filename: emmc.img
FOTA Filename:
--- Entry #1 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 1
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 0
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash Filename: boot.bin
FOTA Filename:
--- Entry #2 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 4
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 8192
Partition Block Count: 40960
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash Filename: efs.img
FOTA Filename:
--- Entry #3 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 2
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 49152
Partition Block Count: 2560
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBL1
Flash Filename: Sbl.bin
FOTA Filename:
--- Entry #4 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 3
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 53248
Partition Block Count: 2560
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBL2
Flash Filename:
FOTA Filename:
--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 5
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 57344
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash Filename: param.lfs
FOTA Filename:
--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 6
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 73728
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: KERNEL
Flash Filename: zImage
FOTA Filename:
--- Entry #7 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 7
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 90112
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash Filename:
FOTA Filename:
--- Entry #8 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 8
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 106496
Partition Block Count: 512000
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHE
Flash Filename: cache.img
FOTA Filename:
--- Entry #9 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 9
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 618496
Partition Block Count: 32768
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MODEM
Flash Filename: modem.bin
FOTA Filename:
--- Entry #10 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 10
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 651264
Partition Block Count: 1048576
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: FACTORYFS
Flash Filename: factoryfs.img
FOTA Filename:
--- Entry #11 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 11
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 1699840
Partition Block Count: 4194304
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: DATAFS
Flash Filename: data.img
FOTA Filename:
--- Entry #12 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 12
Attributes: 2 (STL Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 5894144
Partition Block Count: 23826432
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: UMS
Flash Filename:
FOTA Filename:
--- Entry #13 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 13
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 29720576
Partition Block Count: 1048576
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: HIDDEN
Flash Filename: hidden.img
FOTA Filename:
--- Entry #14 ---
Binary Type: 1 (CP)
Device Type: 1 (File/FAT)
Identifier: 9
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 0
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name:
Flash Filename:
FOTA Filename:
Ending session...
Do you think this can be solved? or is my phone totally dead? I would really appreciate your help
EDIT: right after posting this, i tried with a different pit file, which obviously failed and then my phone doesn't turn on, i guess that now is totally dead
Sounds like something is corrupt and you need to start over. Have you tried flashing the stock MD8 firmware .tar file in odin? You might also want to try using a different USB cable for ODIN. If all else fails then it might be a hardware issue.
Where can I download the stock UCMD8 file for the SGH-I777. I have a phone on UCKH7 I need to flash and it seems all the links are dead. I though I had it stored away on my computer but I can't find it anywhere. Any help would be appreciated.
Never mind. I downloaded it from SamMobile.