Database Develop

Compcache Problems On xROM 1.5r4

Why do i get this output when testing? What the heck am i doing wrong.
I want some compcache with backing swap love too!!!!!!!!!
=== CompCache status ===
CompCache version 0.6+
Compcache enabled
CompCache: MemLimit 16384(system) 8192(user)
CompCache: BackingSwap /dev/block/mmcblk0p3(system) /dev/block/mmcblk0p3(user)
!!! Unable to set compcache cc_swappiness to user specific "60"
Current system value is "28"
=== CompCache status output ===
BackingSwap: /dev/block/mmcblk0p3
DiskSize: 100564 kB
MemLimit: 16384 kB
NumReads: 1
NumWrites: 0
FailedReads: 0
FailedWrites: 0
InvalidIO: 0
NotifyFree: 0
PagesDiscard: 0
ZeroPages: 0
GoodCompress: 0 %
NoCompress: 0 %
PagesStored: 0
PagesUsed: 0
OrigDataSize: 0 kB
ComprDataSize: 0 kB
MemUsedTotal: 0 kB
BDevNumReads: 0
BDevNumWrites: 0
find: /system/app/*.odex: No such file or directory
find: /data/app/*.odex: No such file or directory
#

anybody????????????

I think xROM is ignoring my userinit.sh and user.conf, because when I type "free" in to the terminal it shows the size of my swap partition under swap, rather than my compcache size :-S What command are you using to retrieve those values?

Which blocks are present in our SGA`s FW?

Does anyone have information about which blocks are present in our SGA?
For example: bml5 - it's core(?), stl12 - this system, stl13 - data and so on.
I would like to know them all.

I could be wrong, from size analysis of "cat /proc/partitions" and "cat /proc/mounts" info:
bml1: mibib (APBOOT)
bml2: qcsbl (APBOOT)
bml3: oemsbl (APBOOT)
bml4: amss (MODEM) - confirmed
bml5: efs - confirmed very dangerous, don't touch it
bml6:
bml7: arm11boot (APBOOT)
bml8: boot.img (CODE) - confirmed
bml9: recovery.img (CODE) - confirmed
bml10: param partition - info from init.rc
bml11: fota partition - info from init.rc
stl12: /system (CODE) - confirmed
stl13: /data (CODE) - confirmed
stl14: /cache (CSC) - confirmed

Does anyone have information about which blocks are present in gt-s5830i?

problem partitions
I have a problem with these corrupt partitions I have them and I can not restore a backup

ketut.kumajaya said:
I could be wrong, from size analysis of "cat /proc/partitions" and "cat /proc/mounts" info:
bml1: mibib (APBOOT)
bml2: qcsbl (APBOOT)
bml3: oemsbl (APBOOT)
bml4: amss (MODEM) - confirmed
bml5: efs - confirmed very dangerous, don't touch it
bml6:
bml7: arm11boot (APBOOT)
bml8: boot.img (CODE) - confirmed
bml9: recovery.img (CODE) - confirmed
bml10: param partition - info from init.rc
bml11: fota partition - info from init.rc
stl12: /system (CODE) - confirmed
stl13: /data (CODE) - confirmed
stl14: /cache (CSC) - confirmed
Click to expand...
Click to collapse
how to get information like you? I used the two commands cat /proc/partitions" and "cat /proc/mounts
results
Code:
# cat /proc/partitions
cat /proc/partitions
major minor #blocks name
7 0 2111 loop0
179 0 1954816 mmcblk0
179 1 1954751 mmcblk0p1
137 0 513024 bml0/c
137 1 1536 bml1
137 2 512 bml2
137 3 768 bml3
137 4 25600 bml4
137 5 9216 bml5
137 6 5120 bml6
137 7 2048 bml7
137 8 8192 bml8
137 9 8192 bml9
137 10 768 bml10
137 11 6144 bml11
137 12 222464 bml12
137 13 186624 bml13
137 14 29696 bml14
137 15 6144 bml15
138 12 214784 stl12
138 13 179968 stl13
138 14 25856 stl14
138 15 2304 stl15
254 0 2110 dm-0
#
Code:
# cat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/stl14 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,ioc
harset=utf8 0 0
/dev/stl13 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,ioch
arset=utf8 0 0
/dev/stl12 /system rfs rw,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8
0 0
/dev/stl15 /secure rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,io
charset=utf8 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,u
id=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset
=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,ioch
arset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.speedsoftware.rootexplorer-1 vfat ro,dirsync,nosui
d,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=
iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
#
please help me to get the information you thankssssss:good:

please help me .................................................

Try running this:
ls -al /dev/block/platform/msm_sdcc.1/by-name
That works on my GS3, on AT&T....
~Ibrahim~

bad efs particion !!!!

i m going to show you my mount :
Code:
# mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/stl14 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,ioc
harset=utf8 0 0
/dev/stl13 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,ioch
arset=utf8 0 0
/dev/stl12 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=u
tf8 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,u
id=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset
=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch
arset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.speedsoftware.rootexplorer-1 vfat ro,dirsync,nosui
d,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859
-1,shortname=mixed,utf8,errors=remount-ro 0 0
#
i try to recover my efs partitions with odin but nothing to work ,
i transform my backup stl5.rfs > efs.rfs > efs.tar
for using with odin : make a error invalid binary model
so i don t know how to repair this issue
thank you to help me !!!!

There's no way to restore the efs to this device
This was sent from a Galaxy Ace. Problem?

so how i can repair that ?
just with box?

You cannot repair the efs partition
Sent from my GT-S5830 using xda premium

i dont think is not posible to repair this issue ...
if i have one backup ? like stl5.rfs
i try with terminal but no working ...
may be just only with box like z3x i can to repair ...
or someone can to tell me how to recover like 000000 imei ?
thank you

celica7 said:
i dont think is not posible to repair this issue ...
if i have one backup ? like stl5.rfs
i try with terminal but no working ...
may be just only with box like z3x i can to repair ...
or someone can to tell me how to recover like 000000 imei ?
thank you
Click to expand...
Click to collapse
The Galaxy Ace has a closed up efs partition that until the best of devs do not know how to recover . It's useless to ask , just send it for repair .
This was sent from a Galaxy Ace. Problem?

mods please close thread

closed

How to compile TWRP recovery?
I followed the guide here http://rootzwiki.com/topic/23903-how-to-compile-twrp-from-source/
To summarize...
1. Install Linux
2. Set up CM10 build environment - this is sssssooooo easy and there are loads of guides available with just a simple google search.
3. Repo sync
4. Build standard cm10 from source
5. Delete the contents of the ~/android/system/bootable/recovery and replace with https://github.com/TeamWin/Team-Win-Recovery-Project/ - i just clicked on the download zip button on the top left and unzipped into the folder but am sure there is a proper way of doing this... zip clone???
6. gedit ~/android/system/device/samsung/galaxys2-common/recovery.rc and add: export LD_LIBRARY_PATH .:/sbin
7. gedit ~/android/system/device/samsung/n7000/BoardConfig.mk and add the following to the bottom of the file
#twrp
DEVICE_RESOLUTION := 800x1280
8. cd ~/android/system
9. make -j3 bootimage (if you have a quad core processor make -j5 bootimage)
10. you can find your boot.img at ~/android/system/out/target/product/n7000
11. Copy to SDCARD and flash with mobile odin
12. Done!!!!!

good work. appreciate the effort you have put in.
looking into it now.

Finally here, good work. Will try it as i'm already using TWRP in my N7.
Enviat des d'es meu Nexus 7 amb so Tapatalk2

im using TWRP to flash rom for N8013 and work great.Thanks

nice to see u
subscribed.

You Should pm entropy
Sent from my GT-N7000 using Tapatalk 2

I have sent him a PM
Sent from my GT-N7000 using XDA Premium HD app

timstanley1985 said:
Team Win Recovery Project 2.3 for Galaxy Note (CM10 only)
If you do not know what TWRP is, click here first...... now you know what TWRP is (and how very cool it is!!!) we can continue.
Foreword:
I have looked at those with devices with TWRP with envy for the entire time i have owned a Galaxy Note and have been waiting patiently for an experienced Dev to compile a version for the N7000. After a year of ownership this has not happened so i have decided to go ahead and do it myself!!
Why have you called this a proof on concept?
For a few reasons:
1. I am not an experienced Dev... i have built CM6, 7 and 10 from source and done all the usual tweaks to my android devices but that is where my experience ends. This in itself is no big deal in its self but leads me to point 2...
2. This recovery may have MMC_CAP_ERASE / Brick Bug! I do not know how to check if it is present or not! Until an experienced Dev confirms MMC_CAP_ERASE has been fully suppressed you should assume this recovery is dangerous. As soon as an experienced Dev confirms the recovery is safe i will update this post. If it is confirmed it is not safe i will remove all links
3. I unfortunately to do not have time to maintain this recovery. As Samsung recoveries are included in the boot.img (kernel) it will mean the recovery will need recompiling every time a change is merged to the kernel in CM10. As development is still very active on the N7000 kernel i cannot make the commitment to recompile this that often
4. I am not a kernel Dev therefore i can only compile stock kernel with TWRP recovery. We all love (me included) a custom kernel with all the normal tweaks, OC etc. etc. I will never be able to achieve this so want to use this as the seed for somebody else to take and use to build there own custom kernel with TWRP recovery
5. It needs more extensive testing.... I have been playing with it for an hour this morning and everything seems to work fine but needs more testing.
I have included how to compile TWRP in post two... did i hear someone say enough talking, i want to try this out!!!
How to install
I have attached the boot.img at the bottom of this post.
1. Download
2. Copy to SDCARD
3. Flash with Mobile Odin
4. Enjoy!!
Please remember: This recovery may contain MMC_CAP_ERASE / Brick Bug! I do not known how to check! It is built from CM10 sources and there are TWRP ports for other devices so should be safe but i cannopt be positive! Use at your own risk!
Experienced Dev's: Any feedback on whether this recovery is safe would be VERY gratefully received!
As soon as any confirmation of this recovery being unsafe i will remove link immediately!
Click to expand...
Click to collapse
Based on item #4 (this is using a stock kernel repacked with a new recovery) - it will not be safe for flashing things.
For wipes and backups, it depends on exactly how you built it. Run strings on the binary...
Code:
strings recovery |grep MMC
If you see
Code:
warning: %s: Wipe via secure discard suppressed due to bug in EMMC firmware
The recovery binary is safe to do wipes/backups with, but as said above, if you used a stock kernel, it will be dangerous to flash ZIPs.
Also, of course, as this is a galaxys2-family device, the moment you flash anything containing a new kernel, TWRP will be gone.

Sorry, I should have been clearer. When I say stock kernel I mean stock CM10 kernel. This recovery is built by deleting the /bootable/recovery/ folder and replacing it with TWRP recovery. The rest of the build is standard CM10.
Sent from my GT-N7000 using XDA Premium HD app

Some usage feedback: I found it quite hard navigating through a folder filled with many sub-folders and files to select what I want to flash...quite jerky UI and a lot different from the experience I get on my TWRP-recoveried tablet.
But great initial release dev - really, well done!

And is this Heimdall flashable or do you strictly recommend Odin only? I have never used Odin since it is blackbox and everyone I knew has been recommending Heimdall. I know the former is designed to best-case mimic the latter, but just want to cover all my bases.

Heimdall will work
Sent from my GT-N7000 using XDA Premium HD app

timstanley1985 said:
Heimdall will work
Sent from my GT-N7000 using XDA Premium HD app
Click to expand...
Click to collapse
Alright will give it a go. Thanks for the quick reply.

alharaka said:
Alright will give it a go. Thanks for the quick reply.
Click to expand...
Click to collapse
Yeah, so maybe I did not understand entirely but when I flashed I got a success with Heimdall 1.3.1 CLI on OS X (10.6.8).
Code:
my-bacbook-pro:~ root# heimdall flash --recovery /Users/myusername/Downloads/boot.img --verbose
Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Manufacturer: "SAMSUNG"
Product: "Gadget Serial"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 021B
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 83
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 02
max packet size: 0200
polling interval: 00
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
Uploading RECOVERY
0%File Part #0... Response: 0 0 0 0 0 0 0 0
2%
File Part #1... Response: 0 0 0 0 1 0 0 0
5%
File Part #2... Response: 0 0 0 0 2 0 0 0
7%
File Part #3... Response: 0 0 0 0 3 0 0 0
10%
File Part #4... Response: 0 0 0 0 4 0 0 0
12%
File Part #5... Response: 0 0 0 0 5 0 0 0
15%
File Part #6... Response: 0 0 0 0 6 0 0 0
18%
File Part #7... Response: 0 0 0 0 7 0 0 0
20%
File Part #8... Response: 0 0 0 0 8 0 0 0
23%
File Part #9... Response: 0 0 0 0 9 0 0 0
25%
File Part #10... Response: 0 0 0 0 A 0 0 0
28%
File Part #11... Response: 0 0 0 0 B 0 0 0
31%
File Part #12... Response: 0 0 0 0 C 0 0 0
33%
File Part #13... Response: 0 0 0 0 D 0 0 0
36%
File Part #14... Response: 0 0 0 0 E 0 0 0
38%
File Part #15... Response: 0 0 0 0 F 0 0 0
41%
File Part #16... Response: 0 0 0 0 10 0 0 0
44%
File Part #17... Response: 0 0 0 0 11 0 0 0
46%
File Part #18... Response: 0 0 0 0 12 0 0 0
49%
File Part #19... Response: 0 0 0 0 13 0 0 0
51%
File Part #20... Response: 0 0 0 0 14 0 0 0
54%
File Part #21... Response: 0 0 0 0 15 0 0 0
57%
File Part #22... Response: 0 0 0 0 16 0 0 0
59%
File Part #23... Response: 0 0 0 0 17 0 0 0
62%
File Part #24... Response: 0 0 0 0 18 0 0 0
64%
File Part #25... Response: 0 0 0 0 19 0 0 0
67%
File Part #26... Response: 0 0 0 0 1A 0 0 0
70%
File Part #27... Response: 0 0 0 0 1B 0 0 0
72%
File Part #28... Response: 0 0 0 0 1C 0 0 0
75%
File Part #29... Response: 0 0 0 0 1D 0 0 0
77%
File Part #30... Response: 0 0 0 0 1E 0 0 0
80%
File Part #31... Response: 0 0 0 0 1F 0 0 0
83%
File Part #32... Response: 0 0 0 0 20 0 0 0
85%
File Part #33... Response: 0 0 0 0 21 0 0 0
88%
File Part #34... Response: 0 0 0 0 22 0 0 0
90%
File Part #35... Response: 0 0 0 0 23 0 0 0
93%
File Part #36... Response: 0 0 0 0 24 0 0 0
96%
File Part #37... Response: 0 0 0 0 25 0 0 0
98%
File Part #38... Response: 0 0 0 0 26 0 0 0
100%
RECOVERY upload successful
Ending session...
Rebooting device...
But I rebooted and was back in ClockwordModRecovery 6.1.2. Did I misunderstand the directions? Sorry, my first time using Heimdall to write to my device; last few times I just detect'n'dump-ed to avoid destroying my phone because it was unnecessary.

If I was you just download mobile Odin lite from xda and flash with that. It's very easy that way
Sent from my GT-N7000 using XDA Premium HD app

timstanley1985 said:
If I was you just download mobile Odin lite from xda and flash with that. It's very easy that way
Sent from my GT-N7000 using XDA Premium HD app
Click to expand...
Click to collapse
I'll give that a try. Who knows what the deal is then.

alharaka said:
I'll give that a try. Who knows what the deal is then.
Click to expand...
Click to collapse
Ok, so I configured Mobile ODIN Lite (thanks for the pointer, by the way, amazing app I thought I had to pay for when I saw it a few weeks ago; had no idea I could test a lite version on XDA, sweet). So, installed it and got the N7000 add-on. What partition do I work with: Hidden?

Just click open file, select the boot.img and then scroll down and click flash image.
You click yes to confirm and then it will flash and reboot
Sent from my GT-N7000 using XDA Premium HD app

timstanley1985 said:
Just click open file, select the boot.img and then scroll down and click flash image.
You click yes to confirm and then it will flash and reboot
Sent from my GT-N7000 using XDA Premium HD app
Click to expand...
Click to collapse
Sorry for all the silly questions, and thanks again. I just wanna be sure since the recovery, well, makes mistakes less serious and I rely on it heavily. Once that is broken fixing my phone will get much more technical than I have time for.

[Q] [modem.bin]upgrade to leak rom by heimdall

I am trying to upgrade from GC100ZSALJ6 rom but failed when flashing the modem.bin. I have tried odin and heimdallv1.3.1.
The output of the heimdall is,
Heimdall v1.3.1, Copyright (c) 2010-2011, 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...
Manufacturer: "SAMSUNG"
Product: "Gadget Serial"
length: 18
device class: 2
S/N: 0
VIDID: 04E8:685D
bcdDevice: 021B
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 83
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 02
max packet size: 0200
polling interval: 00
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
Uploading RADIO
0%File Part #0... Response: 0 0 0 0 0 0 0 0
1%
File Part #1... Response: 0 0 0 0 1 0 0 0
2%
File Part #2... Response: 0 0 0 0 2 0 0 0
3%
File Part #3... Response: 0 0 0 0 3 0 0 0
4%
File Part #4... Response: 0 0 0 0 4 0 0 0
5%
File Part #5... Response: 0 0 0 0 5 0 0 0
6%
File Part #6... Response: 0 0 0 0 6 0 0 0
7%
File Part #7... Response: 0 0 0 0 7 0 0 0
8%
File Part #8... Response: 0 0 0 0 8 0 0 0
9%
File Part #9... Response: 0 0 0 0 9 0 0 0
10%
File Part #10... Response: 0 0 0 0 A 0 0 0
11%
File Part #11... Response: 0 0 0 0 B 0 0 0
12%
File Part #12... Response: 0 0 0 0 C 0 0 0
13%
File Part #13... Response: 0 0 0 0 D 0 0 0
14%
File Part #14... Response: 0 0 0 0 E 0 0 0
15%
File Part #15... Response: 0 0 0 0 F 0 0 0
16%
File Part #16... Response: 0 0 0 0 10 0 0 0
17%
File Part #17... Response: 0 0 0 0 11 0 0 0
18%
File Part #18... Response: 0 0 0 0 12 0 0 0
19%
File Part #19... Response: 0 0 0 0 13 0 0 0
20%
File Part #20... Response: 0 0 0 0 14 0 0 0
21%
File Part #21... Response: 0 0 0 0 15 0 0 0
22%
File Part #22... Response: 0 0 0 0 16 0 0 0
23%
File Part #23... Response: 0 0 0 0 17 0 0 0
24%
File Part #24... Response: 0 0 0 0 18 0 0 0
26%
File Part #25... Response: 0 0 0 0 19 0 0 0
27%
File Part #26... Response: 0 0 0 0 1A 0 0 0
28%
File Part #27... Response: 0 0 0 0 1B 0 0 0
29%
File Part #28... Response: 0 0 0 0 1C 0 0 0
30%
File Part #29... Response: 0 0 0 0 1D 0 0 0
31%
File Part #30... Response: 0 0 0 0 1E 0 0 0
32%
File Part #31... Response: 0 0 0 0 1F 0 0 0
33%
File Part #32... Response: 0 0 0 0 20 0 0 0
34%
File Part #33... Response: 0 0 0 0 21 0 0 0
35%
File Part #34... Response: 0 0 0 0 22 0 0 0
36%
File Part #35... Response: 0 0 0 0 23 0 0 0
37%
File Part #36... Response: 0 0 0 0 24 0 0 0
38%
File Part #37... Response: 0 0 0 0 25 0 0 0
39%
File Part #38... Response: 0 0 0 0 26 0 0 0
40%
File Part #39... Response: 0 0 0 0 27 0 0 0
41%
File Part #40... Response: 0 0 0 0 28 0 0 0
42%
File Part #41... Response: 0 0 0 0 29 0 0 0
43%
File Part #42... Response: 0 0 0 0 2A 0 0 0
44%
File Part #43... Response: 0 0 0 0 2B 0 0 0
45%
File Part #44... Response: 0 0 0 0 2C 0 0 0
46%
File Part #45... Response: 0 0 0 0 2D 0 0 0
47%
File Part #46... Response: 0 0 0 0 2E 0 0 0
48%
File Part #47... Response: 0 0 0 0 2F 0 0 0
49%
File Part #48... Response: 0 0 0 0 30 0 0 0
51%
File Part #49... Response: 0 0 0 0 31 0 0 0
52%
File Part #50... Response: 0 0 0 0 32 0 0 0
53%
File Part #51... Response: 0 0 0 0 33 0 0 0
54%
File Part #52... Response: 0 0 0 0 34 0 0 0
55%
File Part #53... Response: 0 0 0 0 35 0 0 0
56%
File Part #54... Response: 0 0 0 0 36 0 0 0
57%
File Part #55... Response: 0 0 0 0 37 0 0 0
58%
File Part #56... Response: 0 0 0 0 38 0 0 0
59%
File Part #57... Response: 0 0 0 0 39 0 0 0
60%
File Part #58... Response: 0 0 0 0 3A 0 0 0
61%
File Part #59... Response: 0 0 0 0 3B 0 0 0
62%
File Part #60... Response: 0 0 0 0 3C 0 0 0
63%
File Part #61... Response: 0 0 0 0 3D 0 0 0
64%
File Part #62... Response: 0 0 0 0 3E 0 0 0
65%
File Part #63... Response: 0 0 0 0 3F 0 0 0
66%
File Part #64... Response: 0 0 0 0 40 0 0 0
67%
File Part #65... Response: 0 0 0 0 41 0 0 0
68%
File Part #66... Response: 0 0 0 0 42 0 0 0
69%
File Part #67... Response: 0 0 0 0 43 0 0 0
70%
File Part #68... Response: 0 0 0 0 44 0 0 0
71%
File Part #69... Response: 0 0 0 0 45 0 0 0
72%
File Part #70... Response: 0 0 0 0 46 0 0 0
73%
File Part #71... Response: 0 0 0 0 47 0 0 0
74%
File Part #72... Response: 0 0 0 0 48 0 0 0
76%
File Part #73... Response: 0 0 0 0 49 0 0 0
77%
File Part #74... Response: 0 0 0 0 4A 0 0 0
78%
File Part #75... Response: 0 0 0 0 4B 0 0 0
79%
File Part #76... Response: 0 0 0 0 4C 0 0 0
80%
File Part #77... Response: 0 0 0 0 4D 0 0 0
81%
File Part #78... Response: 0 0 0 0 4E 0 0 0
82%
File Part #79... Response: 0 0 0 0 4F 0 0 0
83%
File Part #80... Response: 0 0 0 0 50 0 0 0
84%
File Part #81... Response: 0 0 0 0 51 0 0 0
85%
File Part #82... Response: 0 0 0 0 52 0 0 0
86%
File Part #83... Response: 0 0 0 0 53 0 0 0
87%
File Part #84... Response: 0 0 0 0 54 0 0 0
88%
File Part #85... Response: 0 0 0 0 55 0 0 0
89%
File Part #86... Response: 0 0 0 0 56 0 0 0
90%
File Part #87... Response: 0 0 0 0 57 0 0 0
91%
File Part #88... Response: 0 0 0 0 58 0 0 0
92%
File Part #89... Response: 0 0 0 0 59 0 0 0
93%
File Part #90... Response: 0 0 0 0 5A 0 0 0
94%
File Part #91... Response: 0 0 0 0 5B 0 0 0
95%
File Part #92... Response: 0 0 0 0 5C 0 0 0
96%
File Part #93... Response: 0 0 0 0 5D 0 0 0
97%
File Part #94... Response: 0 0 0 0 5E 0 0 0
98%
File Part #95... Response: 0 0 0 0 5F 0 0 0
99%
File Part #96... Response: 0 0 0 0 60 0 0 0
100%
RADIO upload failed!
Ending session...
ERROR: Failed to confirm end of file transfer sequence!
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet.
ERROR: Failed to send end session packet!
Are there anyone has done this type of work successfully?
Is it related to the flash tools hasn't support this device yet?

not sure if it makes a diff.. but have you rooted your device ?

pileiba said:
not sure if it makes a diff.. but have you rooted your device ?
Click to expand...
Click to collapse
Thanks for your reply.
Yes I have rooted the device. But as this procedure is in the download mode, is it related to rooted/non-rooted?
I just want to try another rom.
I have tried another way without modem.bin included and seems all the file could be uploaded to the device now.
But I still not sure about why the modem.bin couldn't been flashed

some other solutions I came across where here.. https://github.com/Benjamin-Dobell/Heimdall/issues/43 i.e. to try different versions of heimdell, try a 32bit operating system as opposed to 64 bit, and reinstall the samsung drivers. There is apparently a Heimdell 1.4 . http://www.glassechidna.com.au/2012/devblogs/heimdall-1-4-release-candidate-1/ . Lastly you could try a different usb cable and a different usb port. I think powered hubs sometimes work better.