Related
I'm the creator of Heimdall the cross platform Galaxy S flashing tool. I was wondering if any one has attempted to flash a Galaxy Tab using my tool?
I suspect that the protocol for flashing the Galaxy Tab is identical. However, I don't have access to a Galaxy Tab so I'm unable to test myself. I would love to add the Galaxy Tab to the list of officially supported devices if someone can confirm it works.
EDIT: Just realised I never updated this post. Heimdall has officially supported the Galaxy Tab for a while now.
I might be able to do it if I find some better firmware to flash. Not sure yet.
Sent from my SCH-I800 using XDA App
I'll give it a try later today. I'm a Linux zealot.
Install notes for Linux + a question
sorry -- wrong thread. No clue how to delete, but I don't want to cross-post so just ignore this.
I compiled and tried using it to flash a modem.bin, but got an error. Heres the console output:
Code:
$ heimdall flash --pit P1_20100909.pit --modem modem.bin
Heimdall, Copyright (c) 2010, 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/
Claiming interface... Failed. Attempting to detach driver...
Claiming interface again... Success
Setting up interface... Success
Beginning session...
Handshaking with Loke... Success
Unexpected device info response!
Expected: 180 or 0
Received:3
Ending session...
Rebooting device...
Re-attaching kernel driver...
rotohammer, thanks for that. It seems as the initialisation process might be slightly different for the Galaxy Tab. Unfortunately the spot where it failed is the exact spot in the protocol that I have basically no clue about. The Galaxy S sends either 180 or 0, which is perhaps some sort of flags indicating the state of the device. Technically the flash could continue past there regardless of the value received but it's a bit of a safety net feature to stop right away.
I'll see if I can get my hands on a Galaxy Tab so I can get Heimdall working for Galaxy Tab users as well.
Works great
For those of you interested, I've modified the Heimdall source on Linux to accept the device info value of 3 and I have successfully flashed 2 different full firmwares on my T-Mobile Tab, as well as many individual files. It works much faster than Odin, and a lot less flaky. I let Benjamin know so he can include support in an upcoming release.
Thanks for the good work, Ben and Roto
Can Heimdall dump partititions from flash for backup?
Technomancer said:
Can Heimdall dump partititions from flash for backup?
Click to expand...
Click to collapse
It can dump, but the dumps, just like those from Odin, aren't very useful. Its a limitation on the exporting function of the phone software.
rotohammer said:
It can dump, but the dumps, just like those from Odin, aren't very useful. Its a limitation on the exporting function of the phone software.
Click to expand...
Click to collapse
I suppose the partitions are not mounted in the "downloading" mode, so any dumps from Heimdall should be better than dumps made using dd from the shell?
rotohammer said:
It can dump, but the dumps, just like those from Odin, aren't very useful. Its a limitation on the exporting function of the phone software.
Click to expand...
Click to collapse
Hi Rotohammer!
Great work again
What did you use as chip-type and chip-id for dumping? I.e.
Code:
heimdall dump --chip-type ??? --chip-id ??? --output <filename>
Volker1 said:
What did you use as chip-type and chip-id for dumping?
Click to expand...
Click to collapse
Code:
heimdall dump --chip-type NAND --chip-id 0 --output hdump.img
I wrote a simple too to display information about PIT files (attached). The factory-installed PIT (/dev/block/bml2) on my T-Mobile US tab is identical to the one known as P1_20100909.pit and reads:
Code:
$ ./PITinfo bml2.dump
Contents of PIT file:bml2.dump
---------------------------------------------------------------------------
file magic = 0x12349876 (expected value)
Unknown data: 0x135d800 0x1 0 0x1331e17 0x2cf560
Number of partitions = 14 (not the usual value)
Partition #1
Usual content: boot.bin, the primary boot loader (low-level hardware initialization)
partition entry type: 0 0 (normal partition)
ID = 0; flags = 0; unknown: 0
size = 1 blocks of 256 * 512 bytes = 131072 B = 128 kB = 0 MB
unknown string: [........]
partition name = [IBL+PBL.........................]
file name = [boot.bin........................................................]
Partition #2
Usual content: partition information table (PIT)
partition entry type: 0 0 (normal partition)
ID = 0x1; flags = 0; unknown: 0
size = 1 blocks of 256 * 512 bytes = 131072 B = 128 kB = 0 MB
unknown string: [........]
partition name = [PIT.............................]
file name = [................................................................]
Partition #3
Usual content: efs.rfs
partition entry type: 0 0 (normal partition)
ID = 0x14; flags = 0x2 (rfs file system); unknown: 0
size = 40 blocks of 256 * 512 bytes = 5242880 B = 5120 kB = 5 MB
unknown string: [........]
partition name = [EFS.............................]
file name = [efs.rfs.........................................................]
Partition #4
Usual content: Sbl.bin, the secondary boot loader (loads linux kernel)
partition entry type: 0 0 (normal partition)
ID = 0x3; flags = 0; unknown: 0
size = 5 blocks of 256 * 512 bytes = 655360 B = 640 kB = 0 MB
unknown string: [........]
partition name = [SBL.............................]
file name = [sbl.bin.........................................................]
Partition #5
Usual content: backup of secondary boot loader
partition entry type: 0 0 (normal partition)
ID = 0x4; flags = 0; unknown: 0
size = 5 blocks of 256 * 512 bytes = 655360 B = 640 kB = 0 MB
unknown string: [........]
partition name = [SBL2............................]
file name = [sbl.bin.........................................................]
Partition #6
Usual content: param.lfs /mnt/.lfs j4fs
partition entry type: 0 0 (normal partition)
ID = 0x15; flags = 0x2 (rfs file system); unknown: 0
size = 20 blocks of 256 * 512 bytes = 2621440 B = 2560 kB = 2 MB
unknown string: [........]
partition name = [PARAM...........................]
file name = [param.lfs.......................................................]
Partition #7
Usual content: zImage, the linux kernel
partition entry type: 0 0 (normal partition)
ID = 0x6; flags = 0; unknown: 0
size = 30 blocks of 256 * 512 bytes = 3932160 B = 3840 kB = 3 MB
unknown string: [........]
partition name = [KERNEL..........................]
file name = [zImage..........................................................]
Partition #8
Usual content: recovery.bin, the backup copy of zImage/initramfs
partition entry type: 0 0 (normal partition)
ID = 0x7; flags = 0; unknown: 0
size = 30 blocks of 256 * 512 bytes = 3932160 B = 3840 kB = 3 MB
unknown string: [........]
partition name = [RECOVERY........................]
file name = [zImage..........................................................]
Partition #9
Usual content: factoryfs.rfs
partition entry type: 0 0 (normal partition)
ID = 0x16; flags = 0x2 (rfs file system); unknown: 0
size = 1320 blocks of 256 * 512 bytes = 173015040 B = 168960 kB = 165 MB
unknown string: [........]
partition name = [FACTORYFS.......................]
file name = [factoryfs.rfs...................................................]
Partition #10
Usual content: dbdata.rfs
partition entry type: 0 0 (normal partition)
ID = 0x17; flags = 0x2 (rfs file system); unknown: 0
size = 348 blocks of 256 * 512 bytes = 45613056 B = 44544 kB = 43 MB
unknown string: [........]
partition name = [DBDATAFS........................]
file name = [dbdata.rfs......................................................]
Partition #11
Usual content: cache.rfs
partition entry type: 0 0 (normal partition)
ID = 0x18; flags = 0x2 (rfs file system); unknown: 0
size = 140 blocks of 256 * 512 bytes = 18350080 B = 17920 kB = 17 MB
unknown string: [........]
partition name = [CACHE...........................]
file name = [cache.rfs.......................................................]
Partition #12
Usual content: modem.bin
partition entry type: 0 0 (normal partition)
ID = 0x8; flags = 0; unknown: 0
size = 64 blocks of 256 * 512 bytes = 8388608 B = 8192 kB = 8 MB
unknown string: [........]
partition name = [MODEM...........................]
file name = [modem.bin.......................................................]
Partition #13
Usual content: Unknown
partition entry type: 0 2 (unknown value)
ID = 0; flags = 0x1; unknown: 0
size = 0 blocks of 0 * 512 bytes = 0 B = 0 kB = 0 MB
unknown string: [l.e. .(.]
partition name = [MOVINAND..)...*...p.i.t.........]
file name = [movinand.mst........D.:.\.2.4.....P.1.\.4... .S.M.D. .i.m.a.g.e.]
Partition #14
Usual content: Unknown
partition entry type: 1 1 (past-the-end marker)
ID = 0x8; flags = 0; unknown: 0
size = 0 blocks of 0 * 512 bytes = 0 B = 0 kB = 0 MB
unknown string: [........]
partition name = [................................]
file name = [................................................................]
I want to flash the Euro firmware (I'm back in Europe right now) by flashing P1000XWJJ4 (and then flash P1000XXJK5 on top). The P1_add_hidden.pit reads:
Code:
$ ./PITinfo P1_add_hidden.pit
Contents of PIT file:P1_add_hidden.pit
---------------------------------------------------------------------------
file magic = 0x12349876 (expected value)
Unknown data: 0x1 0 0x411e17 0x12fae0 0x43d800
Number of partitions = 15 (not the usual value)
Partition #1
Usual content: boot.bin, the primary boot loader (low-level hardware initialization)
partition entry type: 0 0 (normal partition)
ID = 0; flags = 0; unknown: 0
size = 1 blocks of 256 * 512 bytes = 131072 B = 128 kB = 0 MB
unknown string: [........]
partition name = [IBL+PBL.........................]
file name = [boot.bin........................................................]
Partition #2
Usual content: partition information table (PIT)
partition entry type: 0 0 (normal partition)
ID = 0x1; flags = 0; unknown: 0
size = 1 blocks of 256 * 512 bytes = 131072 B = 128 kB = 0 MB
unknown string: [........]
partition name = [PIT.............................]
file name = [................................................................]
Partition #3
Usual content: efs.rfs
partition entry type: 0 0 (normal partition)
ID = 0x14; flags = 0x2 (rfs file system); unknown: 0
size = 40 blocks of 256 * 512 bytes = 5242880 B = 5120 kB = 5 MB
unknown string: [........]
partition name = [EFS.............................]
file name = [efs.rfs.........................................................]
Partition #4
Usual content: Sbl.bin, the secondary boot loader (loads linux kernel)
partition entry type: 0 0 (normal partition)
ID = 0x3; flags = 0; unknown: 0
size = 5 blocks of 256 * 512 bytes = 655360 B = 640 kB = 0 MB
unknown string: [........]
partition name = [SBL.............................]
file name = [sbl.bin.........................................................]
Partition #5
Usual content: backup of secondary boot loader
partition entry type: 0 0 (normal partition)
ID = 0x4; flags = 0; unknown: 0
size = 5 blocks of 256 * 512 bytes = 655360 B = 640 kB = 0 MB
unknown string: [........]
partition name = [SBL2............................]
file name = [sbl.bin.........................................................]
Partition #6
Usual content: param.lfs /mnt/.lfs j4fs
partition entry type: 0 0 (normal partition)
ID = 0x15; flags = 0x2 (rfs file system); unknown: 0
size = 20 blocks of 256 * 512 bytes = 2621440 B = 2560 kB = 2 MB
unknown string: [........]
partition name = [PARAM...........................]
file name = [param.lfs.......................................................]
Partition #7
Usual content: zImage, the linux kernel
partition entry type: 0 0 (normal partition)
ID = 0x6; flags = 0; unknown: 0
size = 30 blocks of 256 * 512 bytes = 3932160 B = 3840 kB = 3 MB
unknown string: [........]
partition name = [KERNEL..........................]
file name = [zImage..........................................................]
Partition #8
Usual content: recovery.bin, the backup copy of zImage/initramfs
partition entry type: 0 0 (normal partition)
ID = 0x7; flags = 0; unknown: 0
size = 30 blocks of 256 * 512 bytes = 3932160 B = 3840 kB = 3 MB
unknown string: [........]
partition name = [RECOVERY........................]
file name = [zImage..........................................................]
Partition #9
Usual content: factoryfs.rfs
partition entry type: 0 0 (normal partition)
ID = 0x16; flags = 0x2 (rfs file system); unknown: 0
size = 1320 blocks of 256 * 512 bytes = 173015040 B = 168960 kB = 165 MB
unknown string: [........]
partition name = [FACTORYFS.......................]
file name = [factoryfs.rfs...................................................]
Partition #10
Usual content: dbdata.rfs
partition entry type: 0 0 (normal partition)
ID = 0x17; flags = 0x2 (rfs file system); unknown: 0
size = 348 blocks of 256 * 512 bytes = 45613056 B = 44544 kB = 43 MB
unknown string: [........]
partition name = [DBDATAFS........................]
file name = [dbdata.rfs......................................................]
Partition #11
Usual content: cache.rfs
partition entry type: 0 0 (normal partition)
ID = 0x18; flags = 0x2 (rfs file system); unknown: 0
size = 140 blocks of 256 * 512 bytes = 18350080 B = 17920 kB = 17 MB
unknown string: [........]
partition name = [CACHE...........................]
file name = [cache.rfs.......................................................]
Partition #12
Usual content: modem.bin
partition entry type: 0 0 (normal partition)
ID = 0x8; flags = 0; unknown: 0
size = 64 blocks of 256 * 512 bytes = 8388608 B = 8192 kB = 8 MB
unknown string: [........]
partition name = [MODEM...........................]
file name = [modem.bin.......................................................]
Partition #13
Usual content: Unknown
partition entry type: 0 2 (unknown value)
ID = 0x3; flags = 0x1; unknown: 0
size = 0 blocks of 0 * 512 bytes = 0 B = 0 kB = 0 MB
unknown string: [l.e. .(.]
partition name = [HIDDEN.D..)...*...p.i.t.........]
file name = [hidden.rfs.t........D.:.\.2.4.....P.1.\.4... .S.M.D. .i.m.a.g.e.]
Partition #14
Usual content: Unknown
partition entry type: 1 1 (past-the-end marker)
ID = 0x8; flags = 0; unknown: 0
size = 0 blocks of 0 * 512 bytes = 0 B = 0 kB = 0 MB
unknown string: [........]
partition name = [................................]
file name = [................................................................]
Partition #15
Usual content: Unknown
partition entry type: 0 2 (unknown value)
ID = 0; flags = 0x1; unknown: 0
size = 0 blocks of 0 * 512 bytes = 0 B = 0 kB = 0 MB
unknown string: [........]
partition name = [MOVINAND........................]
file name = [movinand.mst....................................................]
But it seems like I can't flash movinand.mst with heimdall. Note that it is present in the P1000XWJJ4 firmware file. So I guess I'm better off going the VirtualBox->Win32->Odin route?
Compile on Mac OS X
I've just successfully compiled libusb and Heimdall on Mac OS X.
I needed to set an environment variable by hand so that the "configure" of Heimdall detected libusb:
export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:$PKG_CONFIG_PATH
Oh, and of course this source code modification is necessary for the Galaxy Tab to be supported:
main.cpp line 252:
if (unknown != 180 && unknown != 0 && unknown != 3)
Disclaimer: I haven't had time to try flashing anything yet.
I finally found the courage to flash my T-Mo US tab to Euro version. I made my own Franken-rom by combining P1000XWJJ4 with P1000XXJK5. Specifically, I
1. decompressed P1000XWJJ4.rar
2. took boot.bin, Sbl.bin, and dbdata.rfs from P1000XWJJ4/P1000XWJJ4_SERJJ2_XXJID/P1000XWJJ4-REV03-ALL-CL639474.tar.md5 (a tar archive despite the wrong ending)
3. decompressed P1000XXJK5.rar
4. took zImage, cache.rfs, factoryfs.rfs, modem.bin, and param.lfs from P1000XXJK5/P1000OXAJK5.tar
5. P1_20100909.pit
Then I rebooted my tab in download mode, plugged it into my PC's USB, and then flashed
Code:
$ ./heimdall flash --pit P1_20100909.pit --factoryfs factoryfs.rfs --cache cache.rfs --dbdata dbdata.rfs --boot boot.bin --secondary Sbl.bin --param param.lfs --kernel zImage --modem modem.bin
Heimdall, Copyright (c) 2010, 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/
Claiming interface... Failed. Attempting to detach driver...
Claiming interface again... Success
Setting up interface... Success
Beginning session...
Handshaking with Loke... Success
Downloading device's PIT file...
PIT file download sucessful
Uploading factory filesytem
Factory filesytem upload successful
Uploading cache
Cache upload successful
Uploading data database
Data database upload successful
Uploading primary bootloader
Primary bootloader upload successful
Uploading secondary bootloader
Secondary bootloader upload successful
Uploading param.lfs
param.lfs upload successful
Uploading kernel
Kernel upload successful
Uploading modem
Modem upload successful
Ending session...
Rebooting device...
Re-attaching kernel driver...
I had my German SIM card in and after some booting I ended up with a perfectly working German-localized Euro tab. Switching the language back to US Englisch works fine, too.
Volker1 said:
But it seems like I can't flash movinand.mst with heimdall. Note that it is present in the P1000XWJJ4 firmware file.
Click to expand...
Click to collapse
It is also present in JK2. So I guess in the end you decided not to flash movinand.mst, right ? Unless you used Odin and Heimdall ?
daniel.weck said:
It is also present in JK2. So I guess in the end you decided not to flash movinand.mst, right ? Unless you used Odin and Heimdall ?
Click to expand...
Click to collapse
Alright it looks like you guys have found one more file that Heimdall is technically capable of flashing but doesn't implement. I presume I'm missing quite a few files that the protocol supports, at least that's what the following list of utilised file identifiers would seem to indicate:
Code:
enum
{
kFilePrimaryBootloader = 0x00,
kFileSecondaryBootloader = 0x03,
kFileKernel = 0x06,
kFileParamLfs = 0x15,
kFileFactoryFilesystem = 0x16,
kFileDatabaseData = 0x17,
kFileCache = 0x18
};
I can easily add support for movinand.mst if I can find out what file identifier it uses. Unfortunately I don't have a Galaxy Tab and I need access to one in order to find out.
It's zero, if we trust the output of the PIT reader utility:
http://forum.xda-developers.com/showpost.php?p=9471190&postcount=14
Benjamin Dobell said:
Alright it looks like you guys have found one more file that Heimdall is technically capable of flashing but doesn't implement. I presume I'm missing quite a few files that the protocol supports, at least that's what the following list of utilised file identifiers would seem to indicate:
Code:
enum
{
kFilePrimaryBootloader = 0x00,
kFileSecondaryBootloader = 0x03,
kFileKernel = 0x06,
kFileParamLfs = 0x15,
kFileFactoryFilesystem = 0x16,
kFileDatabaseData = 0x17,
kFileCache = 0x18
};
I can easily add support for movinand.mst if I can find out what file identifier it uses. Unfortunately I don't have a Galaxy Tab and I need access to one in order to find out.
Click to expand...
Click to collapse
Well 0 is the primary bootloader, so right now I'm not trusting it.
Does anyone have any idea what the contents of movinand.mst is? Because I just figured out how to flash the recovery partition directly.
EDIT: And the EFS.
NOTE: the log below pertains to KB5...I haven't had time yet to look into KB6.
http://www.samfirmware.com/WEBPROTECT-p1010.htm
ro.build.display.id=FROYO.XWKB5
ro.build.version.sdk=8
ro.build.version.release=2.2.1
ro.build.date=Thu Feb 17 19:34:43 KST 2011
I'm going to unpack the various RFS archives, to see what's new. I've got a GT-P1000 Galaxy Tab (wifi+3G), so I'm not going to flash with Heimdall (let alone Odin ).
I made backups for factoryfs.rfs / dbdata.rfs etc. using the usual bit-by-bit "dd" -based method, and I've got a trusty TitaniumBackup archive ready, just in case
I notice that TV-out seems to be gone, and FM radio appears to be available. Hardware DSP support seems more present too. (read content logs below for more information)
TAR contents:
Code:
p1wifi_20110128_r10_00.pit (4 KB) (see PIT-info dumped below)
GT-P1010-CSC-SERKB3/
cache.rfs (10.9 MB) (see content listing below)
movinand.mst (51MB) (can be extracted with [URL="http://movitool.ntd.homelinux.org/trac/movitool/"]MoviTool[/URL], based on [URL="http://forum.xda-developers.com/showpost.php?p=9481702&postcount=30"]Volker1's method[/URL])
P1010XWKB5-REV03-ALL-low-CL913814/
boot.bin (256 KB)
cache.rfs (672 KB)
normalboot.img (4.3 MB)
param.lfs (612 KB)
recovery.img (4.3 MB)
Sbl.bin (1.2 MB)
system.rfs (331 MB)
userdata.rfs (1.2 MB)
Output from Volker1's PIT-info utility:
Code:
Contents of PIT file: p1wifi_20110128_r10_00.pit
---------------------------------------------------------------------------
file magic = 0x12349876 (expected value)
Unknown data: 0 0 0 0 0
Number of partitions = 13 (usual value)
Partition #1
Usual content: boot.bin, the primary boot loader (low-level hardware initialization)
partition entry type: 0 0 (normal partition)
ID = 0; flags = 0; unknown: 0
size = 1 blocks of 256 * 512 bytes = 131072 B = 128 kB = 0 MB
unknown string: [........]
partition name = [IBL+PBL.........................]
file name = [boot.bin........................................................]
Partition #2
Usual content: partition information table (PIT)
partition entry type: 0 0 (normal partition)
ID = 0x1; flags = 0; unknown: 0
size = 1 blocks of 256 * 512 bytes = 131072 B = 128 kB = 0 MB
unknown string: [........]
partition name = [PIT.............................]
file name = [p1wifi.pit......................................................]
Partition #3
Usual content: efs.rfs
partition entry type: 0 0 (normal partition)
ID = 0x14; flags = 0x2 (rfs file system); unknown: 0
size = 40 blocks of 256 * 512 bytes = 5242880 B = 5120 kB = 5 MB
unknown string: [........]
partition name = [EFS.............................]
file name = [efs.rfs.........................................................]
Partition #4
Usual content: Sbl.bin, the secondary boot loader (loads linux kernel)
partition entry type: 0 0 (normal partition)
ID = 0x3; flags = 0; unknown: 0
size = 5 blocks of 256 * 512 bytes = 655360 B = 640 kB = 0 MB
unknown string: [........]
partition name = [SBL.............................]
file name = [sbl.bin.........................................................]
Partition #5
Usual content: backup of secondary boot loader
partition entry type: 0 0 (normal partition)
ID = 0x4; flags = 0; unknown: 0
size = 5 blocks of 256 * 512 bytes = 655360 B = 640 kB = 0 MB
unknown string: [........]
partition name = [SBL2............................]
file name = [sbl.bin.........................................................]
Partition #6
Usual content: param.lfs /mnt/.lfs j4fs
partition entry type: 0 0 (normal partition)
ID = 0x15; flags = 0x2 (rfs file system); unknown: 0
size = 20 blocks of 256 * 512 bytes = 2621440 B = 2560 kB = 2 MB
unknown string: [........]
partition name = [PARAM...........................]
file name = [param.lfs.......................................................]
Partition #7
Usual content: zImage, the linux kernel
partition entry type: 0 0 (normal partition)
ID = 0x5; flags = 0; unknown: 0
size = 30 blocks of 256 * 512 bytes = 3932160 B = 3840 kB = 3 MB
unknown string: [........]
partition name = [NORMALBOOT......................]
file name = [normalboot.img..................................................]
Partition #8
Usual content: recovery.bin, the backup copy of zImage/initramfs
partition entry type: 0 0 (normal partition)
ID = 0x8; flags = 0; unknown: 0
size = 30 blocks of 256 * 512 bytes = 3932160 B = 3840 kB = 3 MB
unknown string: [........]
partition name = [RECOVERY........................]
file name = [recovery.img....................................................]
Partition #9
Usual content: factoryfs.rfs
partition entry type: 0 0 (normal partition)
ID = 0x16; flags = 0x2 (rfs file system); unknown: 0
size = 1430 blocks of 256 * 512 bytes = 187432960 B = 183040 kB = 178 MB
unknown string: [........]
partition name = [SYSTEM..........................]
file name = [system.rfs......................................................]
Partition #10
Usual content: dbdata.rfs
partition entry type: 0 0 (normal partition)
ID = 0x17; flags = 0x2 (rfs file system); unknown: 0
size = 302 blocks of 256 * 512 bytes = 39583744 B = 38656 kB = 37 MB
unknown string: [........]
partition name = [USERDATA........................]
file name = [userdata.rfs....................................................]
Partition #11
Usual content: cache.rfs
partition entry type: 0 0 (normal partition)
ID = 0x18; flags = 0x2 (rfs file system); unknown: 0
size = 140 blocks of 256 * 512 bytes = 18350080 B = 17920 kB = 17 MB
unknown string: [........]
partition name = [CACHE...........................]
file name = [cache.rfs.......................................................]
Partition #12
Usual content: modem.bin
partition entry type: 0 2 (unknown value)
ID = 0x3; flags = 0x1; unknown: 0
size = 0 blocks of 0 * 512 bytes = 0 B = 0 kB = 0 MB
unknown string: [........]
partition name = [HIDDEN.D........................]
file name = [hidden.rfs.t....................................................]
Partition #13
Usual content: Unknown
partition entry type: 0 2 (unknown value)
ID = 0; flags = 0x1; unknown: 0
size = 0 blocks of 0 * 512 bytes = 0 B = 0 kB = 0 MB
unknown string: [........]
partition name = [MOVINAND........................]
file name = [movinand.mst....................................................]
The usual CSC cache.rfs content:
Code:
/dbdata/svox/de-DE_gl0_sg.bin
/dbdata/svox/de-DE_ta.bin
/dbdata/svox/en-GB_kh0_sg.bin
/dbdata/svox/en-GB_ta.bin
/dbdata/svox/en-US_lh0_sg.bin
/dbdata/svox/en-US_ta.bin
/dbdata/svox/es-ES_ta.bin
/dbdata/svox/es-ES_zl0_sg.bin
/dbdata/svox/fr-FR_nk0_sg.bin
/dbdata/svox/fr-FR_ta.bin
/dbdata/svox/it-IT_cm0_sg.bin
/dbdata/svox/it-IT_ta.bin
/system/csc/feature.xml
/system/csc/contents.db
/system/csc/others.xml
/system/csc/sales_code.dat
/system/csc/customer.xml
/system/app/MusicODC.apk
/system/T9DB/qwerty_fi.kdb
/system/T9DB/phonepad_cs.kdb
/system/T9DB/qwerty_da.kdb
/system/T9DB/Samsung_400_PLlsUN_xt9.ldb
/system/T9DB/phonepad_lt.kdb
/system/T9DB/Samsung_400_TRlsUN_xt9.ldb
/system/T9DB/Samsung_400_DEusUN_xt9.ldb
/system/T9DB/Samsung_400_ETlsUN_xt9.ldb
/system/T9DB/Samsung_400_ENubUN_xt9.ldb
/system/T9DB/Samsung_400_SVusUN_xt9.ldb
/system/T9DB/qwerty_sv.kdb
/system/T9DB/Samsung_400_DAlsUN.ldb
/system/T9DB/phonepad_uk.kdb
/system/T9DB/phonepad_it.kdb
/system/T9DB/phonepad_el.kdb
/system/T9DB/qwerty_hu.kdb
/system/T9DB/qwerty_es.kdb
/system/T9DB/Samsung_400_UKlsUN_xt9.ldb
/system/T9DB/qwerty_fr.kdb
/system/T9DB/qwerty_et.kdb
/system/T9DB/Samsung_400_SKlsUN_xt9.ldb
/system/T9DB/phonepad_no.kdb
/system/T9DB/qwerty_nl.kdb
/system/T9DB/qwerty_lt.kdb
/system/T9DB/Samsung_400_LVlsUN_xt9.ldb
/system/T9DB/Samsung_400_ITlsUN_xt9.ldb
/system/T9DB/Samsung_400_PTlsUN_xt9.ldb
/system/T9DB/phonepad_da.kdb
/system/T9DB/Samsung_400_HUlsUN_xt9.ldb
/system/T9DB/Samsung_400_ELlsUN_xt9.ldb
/system/T9DB/phonepad_et.kdb
/system/T9DB/Samsung_400_KKlsUN_xt9.ldb
/system/T9DB/phonepad_es.kdb
/system/T9DB/qwerty_sk.kdb
/system/T9DB/phonepad_nl.kdb
/system/T9DB/qwerty_pt.kdb
/system/T9DB/Samsung_400_ESlsUN_xt9.ldb
/system/T9DB/Samsung_400_CSlsUN_xt9.ldb
/system/T9DB/phonepad_ru.kdb
/system/T9DB/phonepad_tr.kdb
/system/T9DB/qwerty_tr.kdb
/system/T9DB/phonepad_de.kdb
/system/T9DB/Samsung_400_FIlsUN_xt9.ldb
/system/T9DB/phonepad_ko.kdb
/system/T9DB/phonepad_fr.kdb
/system/T9DB/phonepad_fi.kdb
/system/T9DB/qwerty_ru.kdb
/system/T9DB/phonepad_en.kdb
/system/T9DB/qwerty_en.kdb
/system/T9DB/qwerty_cs.kdb
/system/T9DB/qwerty_el.kdb
/system/T9DB/Samsung_400_NOlsUN.ldb
/system/T9DB/Samsung_400_RUlsUN_xt9.ldb
/system/T9DB/qwerty_kk.kdb
/system/T9DB/qwerty_no.kdb
/system/T9DB/qwerty_uk.kdb
/system/T9DB/phonepad_lv.kdb
/system/T9DB/phonepad_pl.kdb
/system/T9DB/Samsung_400_NLlsUN_xt9.ldb
/system/T9DB/phonepad_sv.kdb
/system/T9DB/phonepad_sk.kdb
/system/T9DB/Samsung_400_LTlsUN_xt9.ldb
/system/T9DB/qwerty_pl.kdb
/system/T9DB/qwerty_de.kdb
/system/T9DB/Samsung_400_FRlsUN_xt9s.ldb
/system/T9DB/qwerty_ko.kdb
/system/T9DB/qwerty_lv.kdb
/system/T9DB/phonepad_pt.kdb
/system/T9DB/qwerty_it.kdb
/system/T9DB/phonepad_hu.kdb
/system/CSCFiles.txt
/system/SW_Configuration.xml
Changes in /system/app/ :
Removed DailyBriefing, Ebook, Mms, MobileTrackerEngineTwo, MobileTrackerUI, OtaProvisioningService, SamsungWidget_WeatherClock, SoundRecorder, signin, syncmldm, wipereceiver, wssomacp
Added PhoneCrashNotifier, PopupuiReceiverf, qik, qikhelp, skype
Changes in /system/bin/ :
Too many to list, but here are some notable ones:
Removed BCM4329B1_002.002.023.0534.0590.hcd (the driver for the multi-function Broadcom BCM-4329 chipset, also removed in /etc/wifi/ etc.), akmd2 (the multi-sensor driver, now split into several sub-daemons: geomagnetic, gyroscope, temperature, light, orientation, pressure, proximity, etc.)
Notable changes in /system/etc/ :
Added audio/codec/FMRadioEar.ini, audio/codec/FMRadioSpk.ini, and FM-radio stuff in /etc/firmware/ and /lib/libfmradio_jni.so (the Texas Intruments BRF6350 chip supports FM radio...but I don't think that /system/app/ contains an FM tuner application).
Notable addition: /lib/dsp/ + /lib/libOMX*.so + /lib/libVendor_ti_OMX*.so + lib/libaomx_*.so (Texas Intruments OMX/DSP, hardware encoding/decoding of 720p AMR, WB-AMR, AAC, h264, WMA, WMV, MP3, MPEG4, Flac, AC3, S263, etc.)
Code:
720p_h264vdec_sn.dll64P
720p_mp4vdec_sn.dll64P
720p_mp4venc_sn.dll64P
baseimage.dof
baseimage.map
chromasuppress.l64p
conversions.dll64P
dctn_dyn.dll64P
ddspbase_tiomap3430.dof64P
dfgm.dll64P
dynbase_tiomap3430.dof64P
eenf_ti.l64P
h264vdec_sn.dll64P
h264venc_sn.dll64P
ipp_sn.dll64P
jpegdec_sn.dll64P
jpegenc_sn.dll64P
m4venc_sn.dll64P
monitor_tiomap3430.dof64P
mp3dec_sn.dll64P
mp4v720parcdec_sn.dll64P
mp4varcdec_sn.dll64P
mp4vdec_sn.dll64P
mpeg4aacdec_sn.dll64P
mpeg4aacenc_sn.dll64P
mpeg4aridec_sn.dll64P
nbamrdec_sn.dll64P
nbamrenc_sn.dll64P
postprocessor_dualout.dll64P
qosdyn_3430.dll64P
ringio.dll64P
star.l64P
usn.dll64P
vpp_sn.dll64P
wbamrdec_sn.dll64P
wbamrenc_sn.dll64P
wmadec_sn.dll64P
wmv9dec_sn.dll64P
yuvconvert.l64p
Wifi access point doesn't seem very well protected (/etc/wifi/softap/hostapd.conf):
SSID = AndroidAP (not broadcast)
IP = 192.168.43.1
PASS = "password" (WPA)
By the way, the Wifi interface is different than on the fully-featured Tab: tiwlan0 (the access point is tiap0)
Nice let us know what's new and how you make out
This is great news and I am looking forward to your project, thanks!!!
Heads-up: original post updated with PIT partition structure and TAR contents.
Original post updated with further information (FM radio, DSP, etc.). None of this is authoritative, obviously. I am just making plain observations. I haven't even seen the manufacturer's specifications yet for this device.
Splice/combine the ROM with a P1000 ROM?
Cool. Does this mean that your aim to splice/combine the ROM with a P1000 ROM to create a custom Android 2.2.1 ROM WITH 3G capabilities, that is compatible with P1000?
And in that case, it sure would be nice to keep most of what has been removed from /system/* in the P1010 ROM, of course.
Very interesting, thanks for posting the analysis.
I wonder whether GL drivers are any newer than from P1000 ROMs.
And GPS daemon?
Also, interesting about these split sensor drivers.
edit
hmm, interesting, the GL drivers are for SGX530 not 540 like in normal tab.
And the CPU in 1010 is OMAP3 not Hummingbird.
KB6 now online @ Samfirmware.
I'm too busy to look into it though.
Hi,
I just got the Wifi version. How can I check the ROM version?
does the P1010 still have a gps radio?
jackfrostn said:
does the P1010 still have a gps radio?
Click to expand...
Click to collapse
Yes. Only differences between 3g and wifi model:
- no 3G radio
- less powerful CPU/GPU on wifi model (thus can't play HD/Full HD video)
- and off course, wifi model is cheaper
could someone try getting the skype and qik files working
any update on the ROMs progress?
bthoven said:
Yes. Only differences between 3g and wifi model:
- no 3G radio
- less powerful CPU/GPU on wifi model (thus can't play HD/Full HD video)
- and off course, wifi model is cheaper
Click to expand...
Click to collapse
Actually it CAN play HD video. It can record 720p movies so it would only make sense it'd be able to play them. I watch 720p episodes of Breaking Bad on mine.
Sent from my GT-P1010 using XDA Premium App
himmelhauk said:
Actually it CAN play HD video. It can record 720p movies so it would only make sense it'd be able to play them. I watch 720p episodes of Breaking Bad on mine.
Sent from my GT-P1010 using XDA Premium App
Click to expand...
Click to collapse
Yes, it can play 720p lower bitrate whilst the 3G version can play higher bit rate, and also 1080p.
bthoven said:
Yes, it can play 720p lower bitrate whilst the 3G version can play higher bit rate, and also 1080p.
Click to expand...
Click to collapse
Actually it is worth making a correction here as well, it plays 1080 just fine as well, at least for me.
Out of curiousity, where did you see that the wifi has a different CPU/GPU than the GSM/CDMA versions? I'm not finding that info anywhere.
chrisliphart said:
Out of curiousity, where did you see that the wifi has a different CPU/GPU than the GSM/CDMA versions? I'm not finding that info anywhere.
Click to expand...
Click to collapse
In all the TI OMAP libraries and kernel in the ROM?
skype for p1010 wifi
Skype will work with regular rom.i used it all day today
Yes, it does have gps radio on there. Well mine does anyway (in the uk)
So I got this problem with Samsung GT-S8530 [WAVE 2] .
I was flashing the phone, did that successfully I guess, and after restarting, I cant get my phone start no mather what I do, the BLUESCREEN shows up, The page with the press the home button something like that ( By the way on the page there are 6 pages with some text ) and after I press the home button it goes "UPLOAD DATA TO PC" and I don't know how simply can I go into DOWNLOAD MODE to re-flash my phone again.
As I said, END KEY TO START, goes into blue screen than UPLOAD DATA TO PC.
When I go VOL DOWN-CAMERA-ENDKEY doesnt go into download mode but go the BLUE SCREN again and then I press the home and I get the UPLOAD DATA TO PC....
If anyone knows whats going on with this, please give me reply. Thanks very much !
If this isnt the right place for this thread move it to the right one, and let me know
http://forum.xda-developers.com/showpost.php?p=39658811&postcount=23
Download attached RAM Dump eXtractor.
Try to catch .txt file and copy info from this...
If you can not see something, then write text from Bluescreen...
Best Regards
Edit 1.
Simple attach your S8530 with cable to PC if you see Upload data to pc
- then start RDX_4.45.exe
Normally auto detect and you need only press Get It in the right upper corner...
If nothing, then remove cable, try again...
But I have also some combinations, where Upload to pc not more connect to PC...
Anyway... Bluescreen give few details what could be happen...
Please write what Wave "talk to you"...
Example from S8500...
Code:
S/W version:S8500+XX+LA1
Modem:Q6270B-KPRBL-1.5.45T
SHP:VPP R5 2.1.1
Build Host:S1-AGENT08
BuildAt:2012/01/05 19:21:46
App Debug Level : 0
ASSERTION_ASSERT:0 failed. (fi
le SysSecureBoot.c, line 4189)
BoAn4189
<Callstack information>
PC = 4031B42B OemDumpRegister
LR = 4031B42F OemDumpRegister
<Mocha Task Callstack>
_SysAssertReport
__SysSecBootReadNetLockInfoFro
mFile
Where do this DOWNLOADED files go, cant find them?
edit 1 / i found them, you will have them in 10 min
anyway i think my phone is dead ....
temp folder on C:
Code:
C:\temp
But you can also change path...
CH Dir
Change Directory...
Best Regards
Edit 1.
edit 1 / i found them, you will have them in 10 min
Click to expand...
Click to collapse
Only
RamDump_Information(Upload).txt
Code:
http://speedy.sh/77jxt/RamDump-Information-BS-Assertion.txt
there you have it.
Try to remove SIM Card... and maybe also remove SD Card...
Then try again to get into Download Mode...
Code:
Type : Unofficial Version
Number : 23
Builder : Administrator
Host : HP01
Date : 2012/04/05
Time : 15:56:44
Size : 42206592 bytes
CheckSum : 0xf3cd8ef9
View :
S/W version:S8530+BO+LD1
Modem:Q6270B-KPRBL-1.5.45T
SHP:VPP R5 2.1.1
Build Host:HP01
BuildAt:2012/04/05 15:56:44
App Debug Level : 1
ASSERTION_ASSERT:FALSE failed.
(file SysECOM.c, line 81)
Ecom V2 Assert : plz check if
ECOM table registerd for Modul
e(DevSIM),API(SimSupportPkcs15
RootCertificates), Id [26]
<Callstack information>
PC = 40317463 OemDumpRegister
LR = 40317467 OemDumpRegister
<Mocha Task Callstack>
_SysAssertReport
SysEcomV2Assert
__Convert2ContactInfo
NxAACFF_Close
ALL HW Information:
HW VERSION : S8200_UNIV_B5
IMEI VERSION : Not Active
RF CAL DATE : Not Active
Bad Block Information:
nNumBMPs : 0
nAge : 0
Run Time Bad Block Occurred :
Init BMPs = 2, Current BMPs =
0
Nucleus Task Information:
Running Task name = Mocha Slic
es = 0000001E Wait = 00000000
Signal = 00000000 Priority = 0
Pager Stat: Total Page(3280),
Total RAM page(1920), Total Di
sk Page(1360). One Page Size(6
5536)B
Pager Stat: Used RAM page(coun
t :328, 1312 KB), Used Disk Pa
ge(count :0, 0KB)
Pager Stat: Free Page(count :2
952, 188928 KB)
< Heap 0 of Process(0) Informa
tion Print Start >
MemPrintStat: Total heap size
= 251,658,240 (Bytes)
MemPrintStat: Allocated size
= 16,850,944 (Bytes)
MemPrintStat: Available size
= 193,462,272 (Bytes)
MemPrintStat: Peak allocated s
ize = 16,850,944 (Bytes)
__MemPoolPrtAllocInfo: freeMax
Size = 234790912
__MemPoolPrtAllocInfo : Huge A
llocated Chunks more then (163
8400)Bytes
"RsrcBitmap.c":line(105) allo
cated (2070016) Bytes
"RsrcBitmap.c":line(105) allo
cated (2070016) Bytes
__MemPoolPrtAllocInfo : Please
Check above chunks
< Kernel Heap(cache+no cache)
of Information Print Start >
MemPrintStat: Total heap size
= 79,691,776 (Bytes)
MemPrintStat: Allocated size
= 10,616,832 (Bytes) (13%)
MemPrintStat: Available size
= 56,623,104 (Bytes)
MemPrintStat: Peak allocated s
ize = 10,616,832 (Bytes) (13%)
MemPrintStat: Fragmentation le
vel = 1 (%)
< Kernel Heap(cache+no cache)
of Information Print Start >
MemPrintStat: Total heap size
= 79,691,776 (Bytes)
MemPrintStat: Allocated size
= 11,862,016 (Bytes) (14%)
MemPrintStat: Available size
= 56,623,104 (Bytes)
MemPrintStat: Peak allocated s
ize = 11,960,320 (Bytes) (15%)
MemPrintStat: Fragmentation le
vel = 1 (%)
< Kernel Heap 3 of Information
Print Start > (0)
MemPrintStat: Total heap size
= 40,763,392 (Bytes)
MemPrintStat: Allocated size
= 10,080,388 (Bytes) (24%)
MemPrintStat: Free size = 30,
683,004 (Bytes) (75%)
MemPrintStat: Peak allocated s
ize = 10,080,388 (Bytes) (24%)
MemPrintStat: Fragmentation le
vel = 0 (%)
< Kernel Heap 4 of Information
Print Start > (0)
MemPrintStat: Total heap size
= 32,374,784 (Bytes)
MemPrintStat: Allocated size
= 20,019,956 (Bytes) (61%)
MemPrintStat: Free size = 12,
354,828 (Bytes) (38%)
MemPrintStat: Peak allocated s
ize = 20,019,956 (Bytes) (61%)
MemPrintStat: Fragmentation le
vel = 0 (%)
< Kernel Heap 5 of Information
Print Start > (0)
MemPrintStat: Total heap size
= 10,354,688 (Bytes)
MemPrintStat: Allocated size
= 2,227,296 (Bytes) (21%)
MemPrintStat: Free size = 8,1
27,392 (Bytes) (78%)
MemPrintStat: Peak allocated s
ize = 2,227,296 (Bytes) (21%)
MemPrintStat: Fragmentation le
vel = 0 (%)
< Heap 7 of Process(0) Informa
tion Print Start >
MemPrintStat: Total heap size
= 41,943,040 (Bytes)
MemPrintStat: Allocated size
= 6,955,008 (Bytes)
MemPrintStat: Available size
= 34,848,768 (Bytes)
MemPrintStat: Peak allocated s
ize = 6,971,392 (Bytes)
There is no SIM card , neither SD CARD. Its empty.
There is no SIM card , neither SD CARD. Its empty.
Click to expand...
Click to collapse
Hmmm.
1.
But before S8530 alive and normal working ?
1.1.
And you have more then 1 time successfully flashed with Multiloader ?
Or Kies ?
Bluescreen shows this:
Code:
ASSERTION_ASSERT:FALSE failed.
(file SysECOM.c, line 81)
Ecom V2 Assert : plz check if
ECOM table registerd for Modul
e(Dev[B]SIM[/B]),API([B]Sim[/B]SupportPkcs15
RootCertificates), Id [26]
Maybe something Hardware damaged... or other idea.
S8530 Netlock or free for all SIM Cards ?
Best Regards
Edit 1.
Google for SysECOM.c leads to GT-S5230_S5233_S5600.zip
Maybe as background info usefull...
adfree said:
Hmmm.
1.
But before S8530 alive and normal working ?
1.1.
And you have more then 1 time successfully flashed with Multiloader ?
Or Kies ?
Bluescreen shows this:
Code:
ASSERTION_ASSERT:FALSE failed.
(file SysECOM.c, line 81)
Ecom V2 Assert : plz check if
ECOM table registerd for Modul
e(Dev[B]SIM[/B]),API([B]Sim[/B]SupportPkcs15
RootCertificates), Id [26]
Maybe something Hardware damaged... or other idea.
S8530 Netlock or free for all SIM Cards ?
Best Regards
Click to expand...
Click to collapse
1 .Yes I can say that it was normal working. ( Maybe sometimes it got the USB mass storage connected/disconnected. i dont think that has something to do with it.
1.1 Yes I have flashed it maybe 5/6 Times or more
Its fully UNLOCKED....
I think that its a HARDWARE problem.... :/ And that now its for trash....
1.
In theory it is possible to switch to Download Mode from Upload data to pc..
But I don't know how.
2.
There is modified cable solution, to put into DL Mode without pressing key...
Untested by me...
Maybe not working for your problem.
I will search for Link/Picture...
3.
JTAG... like RIFF Box...
Anyway. If Hardware is dead... Sometimes this could happen...
best Regards
3.
JTAG... like RIFF Box...
I dont know whats this Maybe the 1 or 2 method, but i doubt... i think if hardware was dead, the phone would get the bluescreen or into UPLOAD mode
try search, and post and yes ... thanks !
JTAG is this...
This is not impossible, but harder...
http://forum.xda-developers.com/showthread.php?t=898996
Maybe an friend of you have this...
Second idea... easier... Something like this:
http://forum.xda-developers.com/showthread.php?t=872476&highlight=jig
Anyway...
I think if your keys not damaged... maybe then same situation...
Best Regards
Huh this JIG will be hard for doing it .... last hope for me I guess is this so I must try it Thank you very much adfree ! If come up with something else from the .txt file feel free to post it here
Btw, will this method work with wave 2 ? Because I see for every phone is diff
http://www.mobilenations.de/firmware/topic806.html?hilit=bootloader
Here are few Pics about this special "JIG"...
I have NEVER tested such solution.
Few User sell such solution over Ebay for instance... for I9000...
Again. NOT tested by me... and you have special situation... because Hardware keys maybe okay...
Back to this special Upload Mode...
Upload data to PC
1.
In this Mode battery is charging...
2.
RDX_5.3.exe for instance, after dumping reset... so it leave Upload Mode via Command...
So I am 99,9 % sure... it exist Command to switch from Upload data to pc Mode to Download Mode...
Question is only how...
Next days maybe I have time to check, what Ram Dump send to handset to leave Upload Mode...
Best Regards
Somehow I don't know myself, I got into the DOWNLOAD MODE, and I think I did it on this way..
I tried VOL DOWN + HOME KEY + END CALL and it came up with something saying about connecting my phone with "kies" to repair firmware or something like that, then I pressed VOL DOWN + CAM + END KEY (without turning it out from the firmware version that my phone was showing to connect via "kies") and it went to DOWNLOAD MODE. I got happy, flashed it with Multiloader and I got my phone back ! Thanks anyways adfree for helping me, I guess I will know what to do in future with the phone (maybe use and build a usb jig)
:good:
Very nice info and thanx for not giving up.
Short tested:
Code:
VOL DOWN + CAM + END KEY
VOL UP + CAM + END KEY
Both starts Download Mode.
Best Regards
Solution..
vasilevsk1 said:
So I got this problem with Samsung GT-S8530 [WAVE 2] .
I was flashing the phone, did that successfully I guess, and after restarting, I cant get my phone start no mather what I do, the BLUESCREEN shows up, The page with the press the home button something like that ( By the way on the page there are 6 pages with some text ) and after I press the home button it goes "UPLOAD DATA TO PC" and I don't know how simply can I go into DOWNLOAD MODE to re-flash my phone again.
As I said, END KEY TO START, goes into blue screen than UPLOAD DATA TO PC.
When I go VOL DOWN-CAMERA-ENDKEY doesnt go into download mode but go the BLUE SCREN again and then I press the home and I get the UPLOAD DATA TO PC....
If anyone knows whats going on with this, please give me reply. Thanks very much !
If this isnt the right place for this thread move it to the right one, and let me know
Click to expand...
Click to collapse
If your phone is booting in bada OS (not in download mode) then you can fix it.
Just switch on your mobile and put your phone on USB debugging mode.
now download multiloader 5.65.
now connect your mobile. Open multiloader. click on port search.
You will see your phone screen will be in download mode.
Now flash your official firmware or any version that you want to flash...
now connect your mobile. Open multiloader. click on port search.
Click to expand...
Click to collapse
This is via AT Command... Multiloader send AT+FUS? ...
But this is ONLY working, if Wave boot 100 % without trouble...
But if you have problems, like Bootcycle or others, where apps_compressed.bin is not load... FOTA forgotten or other mistakes...
Then this AT Command is NOT working.
Best Regards
Wat if ur phone goes into download mode but screen stays blank?
Sent from my ST18i using xda app-developers app
Hi, my Wave 3 closes when I do random stuff, for example watching a video, sending messages, etc. and when I open it battery level is low. But when It's on charge it dosen't restarts. Anyone have any idea why is this happening? I use S4 style TurkoCWF rom. Thanks.
Phenomen.B said:
Hi, my Wave 3 closes when I do random stuff, for example watching a video, sending messages, etc. and when I open it battery level is low. But when It's on charge it dosen't restarts. Anyone have any idea why is this happening? I use S4 style TurkoCWF rom. Thanks.
Click to expand...
Click to collapse
i have the same problem
*#33284*#
Set Debug Level to:
High
Now Chance Blue Screen gives more info...
1 way is RDX Tool...
Or take picture with Cam...
or Copy and Paste...
Best Regards
---------- Post added at 03:31 PM ---------- Previous post was at 02:44 PM ----------
what blue screen? I dont get no blue screen, only keeps restarting till i put it on charge. Thanks
Click to expand...
Click to collapse
No idea, you enter this Code into your S8600?
Code:
*#33284*#
Yes or no?
RDX Tool is this...
http://forum.xda-developers.com/showpost.php?p=39658811&postcount=23
Sorry, my fault. Forgotten to insert Link.
If S8600 is in Debug Level High... Then Power down for instance should show you Blue Screen...
Now you know what Blue Screen means...
If "luck", this could help by some kind of Errors... to create Messages from handset...
Example... forgotten why or when, but it was my S8600...
Code:
Type : Unofficial Version
Number : 1096
Builder : superuser
Host : S1-AGENT05
Date : 2011/10/26
Time : 17:26:52
Size : 55050240 bytes
CheckSum : 0x0d3edb3f
View :
S/W version:S8600+XX+KJC
Modem:KYRZ213006_05A
SHP:VPP R5 2.1.1
Build Host:S1-AGENT05
BuildAt:2011/10/26 17:26:52
App Debug Level : 0
Data Abort!Page Translation Fa
ult for (0x743f5abc) Read Acce
ss Detection
<Callstack information>
PC = 00EB9E14 _printf_str
LR = 00EBA779 _printf_cs_commo
n
<Mocha Task Callstack>
_printf_cs_common
__printf
_printf_char_common
_printf_fp_hex_real
__MemPartitionGetNextUserAlloc
Ptr
_snprintf
0x002C7972+Dolfin.so
0x00256F6C+Dolfin.so
0x002C7972+Dolfin.so
0x00256F6C+Dolfin.so
OemBmShutdown
BootDestroy
Best Regards
It only shows "Upload data to PC" and that's all. And yes, I used the code u gaved me. Thanks
When I use camera flash it crashes all the times...
Phenomen.B said:
It only shows "Upload data to PC" and that's all. And yes, I used the code u gaved me. Thanks
When I use camera flash it crashes all the times...
Click to expand...
Click to collapse
yep. that happend to me to..
when want to use flash, just it restarts..
Upload data to PC
Click to expand...
Click to collapse
Simple start Tool RDX from here...
http://forum.xda-developers.com/showpost.php?p=39658811&postcount=23
It autodetect Wave...
But if RDX nothing detect in Upload data to PC...
RDX find something and shows something like on Screenshot?
Best Regards
Here:
Code:
Type : Unofficial Version
Number : 1117
Builder : dpi
Host : DELL44
Date : 2013/01/14
Time : 16:54:24
Size : 55050240 bytes
CheckSum : 0x0d284432
View :
S/W version:S8600+FR+MA2
Modem:KYRZ213006_05A
SHP:VPP R5 2.1.1
Build Host:DELL44
BuildAt:2013/01/14 16:54:24
App Debug Level : 0
Data Abort!Page Translation Fa
ult for (0x74543390) Read Acce
ss Detection
<Callstack information>
PC = 00EBAD60 _printf_str
LR = 00EBB6C5 _printf_cs_commo
n
<Mocha Task Callstack>
_printf_cs_common
__printf
_printf_char_common
_printf_fp_hex_real
__MemPartitionGetNextUserAlloc
Ptr
_snprintf
OemBmShutdown
BootDestroy
_WmCallEHFunction
__WmEventHandlerProc
__WmProcessEventInternal
rex_task_free
OemOsLeaveCriticalSection
OsLeaveCriticalSection
WmProcessEvent
OemOsLeaveCriticalSection
OsLeaveCriticalSection
OemOsReleaseMutex
WmExitEventHandler
__BootTimerCallback
__WmProcessTimerEvent
__WmProcessEventInternal
OsReceiveMessageInternal
__WmReceiveEventInternal
WmMainLoop
MochaTask
rex_thread_init
__thread_stub
Pager Stat: Total Page(4864),
Total RAM page(3584), Total Di
sk Page(1280). One Page Size(6
5536)B
Pager Stat: Used RAM page(coun
t :1295, 5180 KB), Used Disk P
age(count :0, 0KB)
Pager Stat: Free Page(count :3
569, 228416 KB)
< Heap 0 of Process(0) Informa
tion Print Start >
MemPrintStat: Total heap size
= 266,338,304 (Bytes)
MemPrintStat: Allocated size
= 50,159,616 (Bytes)
MemPrintStat: Available size
= 195,092,480 (Bytes)
MemPrintStat: Peak allocated s
ize = 77,725,696 (Bytes)
__MemPoolPrtAllocInfo: freeMax
Size = 195092480
__MemPoolPrtAllocInfo : Huge A
llocated Chunks more then (163
8400)Bytes
"RsrcBitmap.c":line(105) allo
cated (2070016) Bytes
"RsrcBitmap.c":line(105) allo
cated (2070016) Bytes
"..\..\..\..\ShpBrowser\Dolfi
n\Platform\Abstract\BAL\Src\Co
mmon\SFBalFontTTF.cpp":line(19
7) allocated (3505536) Bytes
__MemPoolPrtAllocInfo : Please
Check above chunks
< Kernel Heap(cache+no cache)
of Information Print Start >
MemPrintStat: Total heap size
= 83,886,080 (Bytes)
MemPrintStat: Allocated size
= 9,928,704 (Bytes) (11%)
MemPrintStat: Available size
= 43,016,192 (Bytes)
MemPrintStat: Peak allocated s
ize = 14,360,576 (Bytes) (17%)
MemPrintStat: Fragmentation le
vel = 18 (%)
< Kernel Heap(cache+no cache)
of Information Print Start >
MemPrintStat: Total heap size
= 83,886,080 (Bytes)
MemPrintStat: Allocated size
= 21,078,016 (Bytes) (25%)
MemPrintStat: Available size
= 43,016,192 (Bytes)
MemPrintStat: Peak allocated s
ize = 25,591,808 (Bytes) (30%)
MemPrintStat: Fragmentation le
vel = 18 (%)
< Kernel Heap 3 of Information
Print Start > (0)
MemPrintStat: Total heap size
= 10,354,688 (Bytes)
MemPrintStat: Allocated size
= 3,722,072 (Bytes) (35%)
MemPrintStat: Free size = 6,6
32,616 (Bytes) (64%)
MemPrintStat: Peak allocated s
ize = 4,619,988 (Bytes) (44%)
MemPrintStat: Fragmentation le
vel = 0 (%)
< Heap 4 of Process(0) Informa
tion Print Start >
MemPrintStat: Total heap size
= 134,217,728 (Bytes)
MemPrintStat: Allocated size
= 15,826,944 (Bytes)
MemPrintStat: Available size
= 117,112,832 (Bytes)
MemPrintStat: Peak allocated s
ize = 15,826,944 (Bytes)
< Heap 6 of Process(0) Informa
tion Print Start >
MemPrintStat: Total heap size
= 125,829,120 (Bytes)
MemPrintStat: Allocated size
= 8,290,304 (Bytes)
MemPrintStat: Available size
= 117,317,632 (Bytes)
MemPrintStat: Peak allocated s
ize = 8,290,304 (Bytes)
Thanks for your time
Code:
Type : Unofficial Version
Number : 1117
Builder : dpi
Host : DELL44
Date : 2013/01/14
Time : 16:54:24
Size : 55050240 bytes
CheckSum : 0x0d284432
View :
S/W version:[B]S8600+FR+MA2[/B]
Modem:KYRZ213006_05A
SHP:VPP R5 2.1.1
Build Host:DELL44
BuildAt:2013/01/14 16:54:24
@Galaxy3HELL
You use also same Firmware?
S8600+FR+MA2
I use S4 style TurkoCWF rom.
Click to expand...
Click to collapse
The custom Version?
@Phenomen.B
We should short wait for answer from Galaxy3HELL...
If both used same Firmware, then maybe Firmware issue...
Solution 1. in theory.
If your Firmware long runs without Errors... then flash again.
So you have clean Version...
Like "Format C:"...
Bad is, you have to Backup before... as you loose all your SMS, Pics etc.
Test 1.1 would be Stockfirmware... unmodified...
XXKJC for instance...
Clean Fullfimware... with Bootfiles...
So it could be easier to find out if Hardware damage... or really only Software issue...
Best Regards
I flashed again but problems are the same.
And I have no full official firmware...
S8600XXKJC_OXA.rar
Try Google...
Maybe you can download from here:
http://uploaded.net/file/qfls8t4d
Not tested by me... I mean exact this Link.
Here you can see, what files inside... + folder Bootfiles...
http://chomikuj.pl/krzak208/Samsung+Wawe3+(S8600)/XXKJC
Best Regards
Yes, i was using Turko FRMA2, but because of problem i flashed full firmware XXKJC and problem still active :victory:
okidoki...
XXKJC is not "latest"...
It is older...
Only good thing about XXKJC is, it is Full with all files + Boot...
Nearly all other available Firmware are only Update... without FFS and full SHP...
So update from XXKJC to XXLD1...
Maybe then more luck...
Best Regards
link for that software?
To find XXLD1 for S8600, please use Google...
Samfirmware/Sammobile...
But when It's on charge it dosen't restarts.
Click to expand...
Click to collapse
Same for you Galaxy3HELL
If USB or Charger attached?
Maybe this means some problems with Power... no constant Energy...
Remove battery... check contacts etc...
Is S8600 flying from... Any kind of scratches...
Check Label for Waterdamage...
Best Regards
adfree said:
If USB or Charger attached?
Click to expand...
Click to collapse
Same with both, it dosen't matter if USB or charger, it will not restart if one of those 2 is attached.
Hmm...
Phenomen.B said:
Same with both, it dosen't matter if USB or charger, it will not restart if one of those 2 is attached.
Click to expand...
Click to collapse
Then, I think that might be a battery problem, bro.
[ JUST A WHIRL : Try cleaning the contacts with a dry cloth, just as a last try. If possible, if anyone else you know has a wave 3, try checking it with his/her wave's battery. ]
TheBasterd said:
Then, I think that might be a battery problem, bro.
[ JUST A WHIRL : Try cleaning the contacts with a dry cloth, just as a last try. If possible, if anyone else you know has a wave 3, try checking it with his/her wave's battery. ]
Click to expand...
Click to collapse
Yup, it's a battery problem. Tommorow i'll go and buy new one. Thanks all for ur help.
Phenomen.B said:
Yup, it's a battery problem. Tommorow i'll go and buy new one. Thanks all for ur help.
Click to expand...
Click to collapse
@Phenomen.B please post you result with new battery. If it solve the problem, i will buy one to :good: Waiting for you answer :laugh:
did you buy new battery and did it solve you problem? :fingers-crossed:
yes it is battery problem :laugh:
i sold phone for 40$, and guy which buy it changed battery and said that it is working fine now
need help for grand duos i9082 clone
the phone is dead and i need rom for mt6577.
help me
Type = DRAM
Size = 0x20000000 (512MB/4096Mb)
NAND Flash:
ERROR: NAND Flash was not detected!
EMMC:
EMMC_PART_BOOT1 Size = 0x0000000000200000(2MB)
EMMC_PART_BOOT2 Size = 0x0000000000200000(2MB)
EMMC_PART_RPMB Size = 0x0000000000020000(0MB)
EMMC_PART_GP1 Size = 0x0000000000000000(0MB)
EMMC_PART_GP2 Size = 0x0000000000000000(0MB)
EMMC_PART_GP3 Size = 0x0000000000000000(0MB)
EMMC_PART_GP4 Size = 0x0000000000000000(0MB)
EMMC_PART_USER Size = 0x00000000e2c00000(3628MB)
CatHill said:
the phone is dead and i need rom for mt6577.
help me
Type = DRAM
Size = 0x20000000 (512MB/4096Mb)
NAND Flash:
ERROR: NAND Flash was not detected!
EMMC:
EMMC_PART_BOOT1 Size = 0x0000000000200000(2MB)
EMMC_PART_BOOT2 Size = 0x0000000000200000(2MB)
EMMC_PART_RPMB Size = 0x0000000000020000(0MB)
EMMC_PART_GP1 Size = 0x0000000000000000(0MB)
EMMC_PART_GP2 Size = 0x0000000000000000(0MB)
EMMC_PART_GP3 Size = 0x0000000000000000(0MB)
EMMC_PART_GP4 Size = 0x0000000000000000(0MB)
EMMC_PART_USER Size = 0x00000000e2c00000(3628MB)
Click to expand...
Click to collapse
Help me please.....