run this command: cat /proc/L*/bmlinfo
then post your result:
mine runs RFS
Code:
FSR VERSION: FSR_1.2.1p1_b139_RTM
minor position size units id
1: 0x00000000-0x00040000 0x00040000 1 0
2: 0x00040000-0x00080000 0x00040000 1 1
3: 0x00080000-0x00a80000 0x00a00000 40 20
4: 0x00a80000-0x00bc0000 0x00140000 5 3
5: 0x00bc0000-0x00d00000 0x00140000 5 4
6: 0x00d00000-0x01200000 0x00500000 20 21
7: 0x01200000-0x01980000 0x00780000 30 6
8: 0x01980000-0x02100000 0x00780000 30 7
9: 0x02100000-0x12d80000 0x10c80000 1074 22
10: 0x12d80000-0x32f80000 0x20200000 2056 23
11: 0x32f80000-0x3de80000 0x0af00000 700 24
12: 0x3de80000-0x3eb00000 0x00c80000 50 11
(0)(0) bad mapping information
No BadUnit RsvUnit
0: 208 4090
1: 919 4089
2: 1023 4088
i have only 3 bad blocks
I am doing research and no flaming!
I don't think we would see results of bad sectors that fast as most people had it for a week max..but I guess for the sake of research
Rfs _ had epic since sept 20th around
$ export PATH=/data/local/bin:$PATH
$cat /proc/L*/bmlinfo
FSR VERSION: FSR_1.2.1p1_b139_RTM
minor position size units id
1: 0x00000000-0x00040000 0x00040000 1 0
2: 0x00040000-0x00080000 0x00040000 1 1
3: 0x00080000-0x00a80000 0x00a00000 40 20
4: 0x00a80000-0x00bc0000 0x00140000 5 3
5: 0x00bc0000-0x00d00000 0x00140000 5 4
6: 0x00d00000-0x01200000 0x00500000 20 21
7: 0x01200000-0x01980000 0x00780000 30 6
8: 0x01980000-0x02100000 0x00780000 30 7
9: 0x02100000-0x12d80000 0x10c80000 1074 22
10: 0x12d80000-0x32f80000 0x20200000 2056 23
11: 0x32f80000-0x3de80000 0x0af00000 700 24
12: 0x3de80000-0x3eb00000 0x00c80000 50 11
(0)(0) bad mapping information
No BadUnit RsvUnit
0: 1628 4090
1: 2812 4089
2: 3002 4088
3: 3584 4087
4: 3646 4086
5: 3838 4085
export PATH=/data/local/bin:$PATH
# cat /proc/L*/bmlinfo
FSR VERSION: FSR_1.2.1p1_b139_RTM
minor position size units id
1: 0x00000000-0x00040000 0x00040000 1 0
2: 0x00040000-0x00080000 0x00040000 1 1
3: 0x00080000-0x00a80000 0x00a00000 40 20
4: 0x00a80000-0x00bc0000 0x00140000 5 3
5: 0x00bc0000-0x00d00000 0x00140000 5 4
6: 0x00d00000-0x01200000 0x00500000 20 21
7: 0x01200000-0x01980000 0x00780000 30 6
8: 0x01980000-0x02100000 0x00780000 30 7
9: 0x02100000-0x12d80000 0x10c80000 1074 22
10: 0x12d80000-0x32f80000 0x20200000 2056 23
11: 0x32f80000-0x3de80000 0x0af00000 700 24
12: 0x3de80000-0x3eb00000 0x00c80000 50 11
(0)(0) bad mapping information
No BadUnit RsvUnit
0: 100 4090
1: 1068 4089
2: 2584 4088
3: 3540 4087
#
Now lucky me I get my first bad within the first 100 units. Had the Epic since mid October
I bought my Epic when it came out(sept 1st I think).
Running Ext4 sinse it came out(3 days I think).
Is this good?How long my Epic got to live?lol.
export PATH=/data/local/bin:$PATH
$ $su
# cat /proc/L*/bmlinfo
FSR VERSION: FSR_1.2.1p1_b139_RTM
minor position size units id
1: 0x00000000-0x00040000 0x00040000 1 0
2: 0x00040000-0x00080000 0x00040000 1 1
3: 0x00080000-0x00a80000 0x00a00000 40 20
4: 0x00a80000-0x00bc0000 0x00140000 5 3
5: 0x00bc0000-0x00d00000 0x00140000 5 4
6: 0x00d00000-0x01200000 0x00500000 20 21
7: 0x01200000-0x01980000 0x00780000 30 6
8: 0x01980000-0x02100000 0x00780000 30 7
9: 0x02100000-0x12d80000 0x10c80000 1074 22
10: 0x12d80000-0x32f80000 0x20200000 2056 23
11: 0x32f80000-0x3de80000 0x0af00000 700 24
12: 0x3de80000-0x3eb00000 0x00c80000 50 11
(0)(0) bad mapping information
No BadUnit RsvUnit
0: 912 4090
1: 937 4089
2: 1027 4088
3: 3701 4087
#
Been running ext4 since a few days after its port.
export PATH=/data/local/bin:$PATH
$ $su
# cat /proc/L*/bmlinfo
FSR VERSION: FSR_1.2.1p1_b139_RTM
minor position size units id
1: 0x00000000-0x00040000 0x00040000 1 0
2: 0x00040000-0x00080000 0x00040000 1 1
3: 0x00080000-0x00a80000 0x00a00000 40 20
4: 0x00a80000-0x00bc0000 0x00140000 5 3
5: 0x00bc0000-0x00d00000 0x00140000 5 4
6: 0x00d00000-0x01200000 0x00500000 20 21
7: 0x01200000-0x01980000 0x00780000 30 6
8: 0x01980000-0x02100000 0x00780000 30 7
9: 0x02100000-0x12d80000 0x10c80000 1074 22
10: 0x12d80000-0x32f80000 0x20200000 2056 23
11: 0x32f80000-0x3de80000 0x0af00000 700 24
12: 0x3de80000-0x3eb00000 0x00c80000 50 11
(0)(0) bad mapping information
No BadUnit RsvUnit
0: 1023 4090
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
hope this can be read
running "twin jets" launch day unit
When I type this in terminal it says not found.
I'm a little concerned about mine when compared to the others so far... Though I must admit that I've flashed mine more times than I can count just testing:
I've yet to ever flash ext4 on my phone. This phone I've had since early October.
FSR VERSION: FSR_1.2.1p1_b139_RTM
minor position size units id
1: 0x00000000-0x00040000 0x00040000 1 0
2: 0x00040000-0x00080000 0x00040000 1 1
3: 0x00080000-0x00a80000 0x00a00000 40 20
4: 0x00a80000-0x00bc0000 0x00140000 5 3
5: 0x00bc0000-0x00d00000 0x00140000 5 4
6: 0x00d00000-0x01200000 0x00500000 20 21
7: 0x01200000-0x01980000 0x00780000 30 6
8: 0x01980000-0x02100000 0x00780000 30 7
9: 0x02100000-0x12d80000 0x10c80000 1074 22
10: 0x12d80000-0x32f80000 0x20200000 2056 23
11: 0x32f80000-0x3de80000 0x0af00000 700 24
12: 0x3de80000-0x3eb00000 0x00c80000 50 11
(0)(0) bad mapping information
No BadUnit RsvUnit
0: 821 4090
1: 1821 4089
2: 2119 4088
3: 2215 4087
4: 2261 4086
5: 2936 4085
6: 2950 4084
7: 2968 4083
8: 3158 4081
9: 3236 4080
10: 3479 4079
11: 3486 4078
12: 3510 4077
13: 3780 4076
14: 3820 4075
15: 3980 4074
Sent from my SPH-D700 using Tapatalk
konaman said:
When I type this in terminal it says not found.
Click to expand...
Click to collapse
Type it exactly as it is wrtten!
sent from deez
If this is the entirety of my output does that mean no bad blocks yet?
Code:
FSR VERSION: FSR_1.2.1p1_b139_RTM
minor position size units id
1: 0x00000000-0x00040000 0x00040000 1 0
2: 0x00040000-0x00080000 0x00040000 1 1
3: 0x00080000-0x00a80000 0x00a00000 40 20
4: 0x00a80000-0x00bc0000 0x00140000 5 3
5: 0x00bc0000-0x00d00000 0x00140000 5 4
6: 0x00d00000-0x01200000 0x00500000 20 21
7: 0x01200000-0x01980000 0x00780000 30 6
8: 0x01980000-0x02100000 0x00780000 30 7
9: 0x02100000-0x12d80000 0x10c80000 1074 22
10: 0x12d80000-0x32f80000 0x20200000 2056 23
11: 0x32f80000-0x3de80000 0x0af00000 700 24
12: 0x3de80000-0x3eb00000 0x00c80000 50 11
(0)(0) bad mapping information
No BadUnit RsvUnit
Have had my epic since 9/03/10, flashed a new ROM or revision about 4 or 5 times only. Been on ext4 for about 4 days only.
Running rfs had the phone since release day
$cat /proc/L*/bmlinfo
FSR VERSION: FSR_1.2.1p1_b139_RTM
minor position size units id
1: 0x00000000-0x00040000 0x00040000 1 0
2: 0x00040000-0x00080000 0x00040000 1 1
3: 0x00080000-0x00a80000 0x00a00000 40 20
4: 0x00a80000-0x00bc0000 0x00140000 5 3
5: 0x00bc0000-0x00d00000 0x00140000 5 4
6: 0x00d00000-0x01200000 0x00500000 20 21
7: 0x01200000-0x01980000 0x00780000 30 6
8: 0x01980000-0x02100000 0x00780000 30 7
9: 0x02100000-0x12d80000 0x10c80000 1074 22
10: 0x12d80000-0x32f80000 0x20200000 2056 23
11: 0x32f80000-0x3de80000 0x0af00000 700 24
12: 0x3de80000-0x3eb00000 0x00c80000 50 11
(0)(0) bad mapping information
No BadUnit RsvUnit
0: 324 4090
1: 1864 4089
2: 2567 4088
3: 2789 4087
4: 2830 4086
5: 2985 4085
$
Sent from my SPH-D700 using XDA App
I bought my Epic end of Sept.
Running Ext4 since release
minor position size units id
1: 0x00000000-0x00040000 0x00040000 1 0
2: 0x00040000-0x00080000 0x00040000 1 1
3: 0x00080000-0x00a80000 0x00a00000 40 20
4: 0x00a80000-0x00bc0000 0x00140000 5 3
5: 0x00bc0000-0x00d00000 0x00140000 5 4
6: 0x00d00000-0x01200000 0x00500000 20 21
7: 0x01200000-0x01980000 0x00780000 30 6
8: 0x01980000-0x02100000 0x00780000 30 7
9: 0x02100000-0x12d80000 0x10c80000 1074 22
10: 0x12d80000-0x32f80000 0x20200000 2056 23
11: 0x32f80000-0x3de80000 0x0af00000 700 24
12: 0x3de80000-0x3eb00000 0x00c80000 50 11
(0)(0) bad mapping information
No BadUnit RsvUnit
0: 3475 4090
1: 3779 4089
2: 3442 4088
Seems as though we all have the same info up top, the (0)(0) bad mapping information is what seems different among devices..
I only have 3 bad blocks.. not sure how many block I have though LOL
Hope this helps
export PATH=/data/local/bin:$PATH
$ $cat /proc/L*/bmlinfo
FSR VERSION: FSR_1.2.1p1_b139_RTM
minor position size units id
1: 0x00000000-0x00040000 0x00040000 1 0
2: 0x00040000-0x00080000 0x00040000 1 1
3: 0x00080000-0x00a80000 0x00a00000 40 20
4: 0x00a80000-0x00bc0000 0x00140000 5 3
5: 0x00bc0000-0x00d00000 0x00140000 5 4
6: 0x00d00000-0x01200000 0x00500000 20 21
7: 0x01200000-0x01980000 0x00780000 30 6
8: 0x01980000-0x02100000 0x00780000 30 7
9: 0x02100000-0x12d80000 0x10c80000 1074 22
10: 0x12d80000-0x32f80000 0x20200000 2056 23
11: 0x32f80000-0x3de80000 0x0af00000 700 24
12: 0x3de80000-0x3eb00000 0x00c80000 50 11
(0)(0) bad mapping information
No BadUnit RsvUnit
0: 84 4090
1: 1398 4089
2: 3418 4088
Had my epic since a week after launch. Had ext4 for 2 days now. Personally, I see no correlation so far between people running ext4 and a higher number of dead blocks.
Sent from my ext4 Epic 4G running Bonsai4all 1.1.3!
Can this be done from terminal emulator?
Sent from my SPH-D700 using Tapatalk
adamw1101 said:
Can this be done from terminal emulator?
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Yes paste this
cat /proc/L*/bmlinfo
Into your terminal emulator
Sent from my ext4 Epic 4G running Bonsai4all 1.1.3!
Im lost it keeps saying it isn't found is there a prior command I have to insert first?
Sent from my SPH-D700 using Tapatalk
Oct 27th 2010 -- ext4 since it released, flashed new 2.2 roms almost weekly since nov
$ export PATH=/data/local/bin:$PATH
# cat /proc/L*/bmlinfo
FSR VERSION: FSR_1.2.1p1_b139_RTM
minor position size units id
1: 0x00000000-0x00040000 0x00040000 1 0
2: 0x00040000-0x00080000 0x00040000 1 1
3: 0x00080000-0x00a80000 0x00a00000 40 20
4: 0x00a80000-0x00bc0000 0x00140000 5 3
5: 0x00bc0000-0x00d00000 0x00140000 5 4
6: 0x00d00000-0x01200000 0x00500000 20 21
7: 0x01200000-0x01980000 0x00780000 30 6
8: 0x01980000-0x02100000 0x00780000 30 7
9: 0x02100000-0x12d80000 0x10c80000 1074 22
10: 0x12d80000-0x32f80000 0x20200000 2056 23
11: 0x32f80000-0x3de80000 0x0af00000 700 24
12: 0x3de80000-0x3eb00000 0x00c80000 50 11
(0)(0) bad mapping information
No BadUnit RsvUnit
#
(on a side note I have two epic. Mine on EXT4 and my Wife's as close to stock as i can (rooted though so i can run terminal)) so I can randomly run compares over the next 2 years (unless sprint allows early upgrades after the first year) I feel doing this is the only way we can truly due a real life compare and end the which is better argument.
Had my phone for 3 months,flashed more ROMs than I can count,more than 100 Im sure,running EXT4 for 3 days,only got 7 bad blocks,Im using connect bot and cant copy the text right now.
chadit said:
(on a side note I have two epic. Mine on EXT4 and my Wife's as close to stock as i can (rooted though so i can run terminal)) so I can randomly run compares over the next 2 years (unless sprint allows early upgrades after the first year) I feel doing this is the only way we can truly due a real life compare and end the which is better argument.
Click to expand...
Click to collapse
You sir would be a valuable tool in testing the file-system effects and helping put any misconceptions to rest.
export PATH=/data/local/bin:$PATH
$ $ cat/proc/L*/bmlinfo
cat/proc/L*/bmlinfo: not found
$su
# cat/proc/L*/bmlinfo
cat/proc/L*/bmlinfo: not found
#cat /proc/L*/bmlinfo
FSR VERSION: FSR_1.2.1p1_b139_RTM
minor position size units id
1: 0x00000000-0x00040000 0x00040000 1 0
2: 0x00040000-0x00080000 0x00040000 1 1
3: 0x00080000-0x00a80000 0x00a00000 40 20
4: 0x00a80000-0x00bc0000 0x00140000 5 3
5: 0x00bc0000-0x00d00000 0x00140000 5 4
6: 0x00d00000-0x01200000 0x00500000 20 21
7: 0x01200000-0x01980000 0x00780000 30 6
8: 0x01980000-0x02100000 0x00780000 30 7
9: 0x02100000-0x12d80000 0x10c80000 1074 22
10: 0x12d80000-0x32f80000 0x20200000 2056 23
11: 0x32f80000-0x3de80000 0x0af00000 700 24
12: 0x3de80000-0x3eb00000 0x00c80000 50 11
(0)(0) bad mapping information
No BadUnit RsvUnit
0: 3698 4090
#
Have flashed pretty much every rom released have set up ext4 twice on my phone odined like 30 times
Sent from my SPH-D700 using Tapatalk
Related
Can someone tell me why I keep getting the directory error at the bottom on my linux box? Sorry am learning linux as i go. I created a zip directory under bin so not sure why I am still getting this error?
no files for configid 26220739write xip block starting at 81800000, with 3 fileswrite xip block starting at 81980000, with 0 filesthis rom seems to be 3.17.03 ENG 2003-05-15 o2eurothis bootloader seems to be V5.22 2003-05-15 17:46:5580000000 - 80040000 -- bootloader 0 files 1 modules80040000 - 8026a804 -- kernel 13 files 11 modules802c2000 - 8057d330 9 OS 15 files 32 modules80580000 - 8075a69c 8 SHELL 79 files 27 modules80780000 - 80a13b04 7 BROWSING 9 files 14 modules80a40000 - 80d8a33c 6 COREAPPS 46 files 30 modules80dc0000 - 80ebd150 5 SYNC 12 files 22 modules80ec0000 - 810388e0 4 24MAPPS 13 files 13 modules81080000 - 81348248 3 24MCONSUMER 69 files 1 modules81400000 - 814019a4 -- xip chain 10 xip entries81440000 - 817f6f14 1 MISC 209 files 40 modules81800000 - 8184ac20 10 XDA_DEVELOPERS1 3 files 0 modules81900000 - 81925800 -- bitmap : 101a301a .. beb6fc8d81940000 - 81960278 -- operator rom 10 files81980000 - 81981054 11 XDA_DEVELOPERS2 0 files 0 modules./mkrom.sh: /bin/zip: No such file or directory
It looks as though you do not have an appropriate ZIP program...
You may want to see if bzip2 will work instead of zip, or get the linux version of RAR.
The issue though, is you do not have /bin/zip, which is an executable file, not a directory.
Maybe someone can verify what compression executable to use instead of /bin/zip...
J
Ok got that resolved but now when doing zip it gets permission denied. Any other assistance is greatly appreciated. Then should be able to have yorch and company's kitchen running
I would verify that the user that is executing the shell (mkrom) has execute permissions to the zip program...
you can run (as root)
Code:
chmod 755 /usr/bin/bzip2
to change permissions on the bzip2 executable file.
That will give root all access, and everyone else read/execute access.
Also, if the zip program uses any temp directories, make sure the same user has read/write permissions to those directories as well (Probably not your problem, though)
J
Ok got that resolved....now here's what i get....is this a safe error or something I need to worry about? How can I correct it?
./mkrom.sh: ./tounicode: Permission deniedwrite xip block starting at 81720000, with 6 fileswrite xip block starting at 81cb0000, with 72 filesCan't exec "./dumprom": Permission denied at drparse.pl line 22.readline() on closed filehandle FH at drparse.pl line 24.Can't exec "./dumprom": Permission denied at drparse.pl line 22.readline() on closed filehandle FH at drparse.pl line 24.Can't exec "./dumprom": Permission denied at drparse.pl line 22.readline() on closed filehandle FH at drparse.pl line 24.!!! your rom is not known to me: md5: dad2e3cad6095282bf1d58ccf12171e8this bootloader seems to be V5.22 2003-05-15 17:46:55no operator rom found80000000 - 80040000 -- bootloader 0 files 1 modules80040000 - 8015df78 9 XIPKERNEL 5 files 5 modules80180000 - 80376f10 8 KERNEL 10 files 14 modules80380000 - 8064306c 7 OS 20 files 36 modules80670000 - 80be66a8 6 SHELL 107 files 88 modules80c00000 - 8102ce98 5 BROWSING 11 files 36 modules81050000 - 813ef114 4 COREAPPS 95 files 44 modules81400000 - 815d2238 3 EXAPPS 34 files 7 modules815f0000 - 8171bc7c 2 PHONE 56 files 19 modules81720000 - 8177ffe0 10 XDA_DEVELOPERS1 6 files 0 modules81780000 - 81781c34 -- xip chain 11 xip entries817c0000 - 81ca1b44 1 MISC 225 files 42 modules81cb0000 - 81d4eb7c 11 XDA_DEVELOPERS2 72 files 0 modules81ec0000 - 81ee5800 -- bitmap : ffffffff .. ffffffff../rom.exe: found a preamble of 35328 bytes adding: English/NK.nbf (deflated 44%)Archive: rom.exe;The comment below contains SFX script commandsSetup=start.batTempModeSilent=1Overwrite=1 Length Method Size Ratio Date Time CRC-32 Name-------- ------ ------- ----- ---- ---- ------ ---- 0 Stored 0 0% 07-28-03 15:28 00000000 English/ 262144 Defl:N 11018 96% 05-20-02 18:27 f4419bea English/CLoader_serial.nb 262144 Defl:N 12683 95% 05-20-02 18:17 d576b33c English/CLoader_usb.nb 4608 Defl:N 1094 76% 07-17-02 17:22 578b9c86 English/GetConnectionType.dll 18432 Defl:N 7650 59% 04-24-02 15:44 e4ed8f0a English/remote_flash.exe 3584 Defl:N 856 76% 08-21-01 16:43 da38a539 English/SetSystemTime.dll 73728 Defl:N 36119 51% 07-09-03 07:09 95cf7c18 adaptrom.exe 155648 Defl:N 50839 67% 08-28-02 15:23 f5a4ac25 PROGRAMME A.exe 3548 Defl:N 1078 70% 08-28-02 15:25 65d98105 readme.rtf 25 Stored 25 0% 07-28-03 15:28 ecfe543d start.bat32505888 Defl:N 18306975 44% 10-11-03 21:28 34cc9720 English/NK.nbf-------- ------- --- -------33289749 18428337 45% 11 files
Looks like you have the same execute permission problem with the tounicode exe.
Try to fix that.
About the drparse.pl, I have to look at that file, to see what it is trying to do...
Ok, here is the line:
Code:
open FH, "./dumprom $romfile|";
Looks like it is trying to open (as a file) the output of the dumprom executable.
So, dumprom is failing, probably ... yes, I see it now..
Verify the permissions on dumprom as well...
In fact, all *.pl and *.sh files should have execute permissions, use the same command as above to set them.
This reply is a rambling one, I know, but I wrote is as I was doing the research.
Let me know if it helps you.
J
Here's what is weird. I have changed those permissions as you said previously and still get the same error. What's strange to me though is I can run the kitchen with rom ver 3 something, but all of the ver 4 roms come back with the error. Any idea as to what the cause of that might be?
btw jta thanks for all the help. If you have time and would like to look at the box for me I will get access to it for you. Thanks.
I got it all working now. Thank you thank you thank you very much for the help.
Ah, good to hear that you have it all working now!
So, when do we get to try it out?? (wink wink)
J
Very soon....we are now putting finishing touches with other software installs....so will be very very soon.....
type:
cd /usr/local/bin
# ln -s /usr/bin/zip zip
I was wondering what each CAB in the extended ROM does?? I didn't install all of them (I soft reseted before they were auto-installed), and only installed the camera app for now, the device works just fine, can someone complete this description list? :
The device is Imate with 1.52.00WWE
Default_Broadcast.CAB -
Default_Caller.CAB - IA Caller ID (doesn't really work since it dies all the time)
Default_Camera.CAB - Camera Application
Default_Driver.CAB -
Default_Imate.cab -
Default_MIDI.CAB -
Default_MMS.CAB - MMS composer
Default_OEM5.CAB -
Default_Version.CAB -
Hi,
I posted a desricption of the T-Mobile NL ext ROM in this thread:
http://forum.xda-developers.com/viewtopic.php?t=5522
It's easy to guess from the names which cabs correspond to the ones I mention.
I wrote a perl script to decode the contents of a cab file.
first you have to extract the files using a decompression utility that understands cab files.
then run
perl cabdump.pl custom~1.000
( where custom~1.000 is the name of the first file in the cab file )
updated the cabdump script a bit, now directly processes cab files.
here is the result on all cabs in the extended rom ( don't know which version, some t-mobile )
Processing file VideoMMS.sa.CAB
processor=0 versions: 3.00 .. 4.20
application=Tools provider=Customization
platforms: JUPITER, HPC
unknown: 0 0 1 0 0
[files]
1: 1 2 0000 0CESetup.001 %CE1%\Tools\CESetup.dll
2: 6 2 0000 CHECKF~1.002 Windows\CheckFile.exe
3: 5 2 0000 PLATFO~1.003 Windows\Platformxxx.reg
4: 4 2 0000 CUSTOM~1.004 Windows\Customize.lst
5: 2 2 0000 VIDEOM~1.005 Windows\Video MMS.exe
6: 3 2 0000 VIDEOM~1.006 %CE11%\Video MMS.lnk
[registry]
1: 0 [HKCU\Software\HTC\Customize] Ver='1.0'
[shortcuts]
Processing file Broadcast_WWE.sa.CAB
processor=0 versions: 3.00 .. 4.20
application=Tools provider=Customization
platforms: JUPITER, HPC
unknown: 0 0 1 0 0
[files]
1: 1 2 0000 0CESetup.001 %CE1%\Tools\CESetup.dll
2: 4 2 0000 CHECKF~1.002 Windows\CheckFile.exe
3: 3 2 0000 PLATFO~1.003 Windows\Platformxxx.reg
4: 2 2 0000 CUSTOM~1.004 Windows\Customize.lst
[registry]
1: 0 [HKCU\Software\HTC\Customize] Ver='1.0'
[shortcuts]
Processing file CameraRC131_WWE_1.5.sa.CAB
processor=0 versions: 3.00 .. 4.20
application=Tools provider=Customization
platforms: JUPITER, HPC
unknown: 0 0 1 0 0
[files]
1: 1 2 0000 0CESetup.001 %CE1%\Tools\CESetup.dll
2: 50 2 0000 CHECKF~1.002 Windows\CheckFile.exe
3: 49 2 0000 PLATFO~1.003 Windows\Platformxxx.reg
4: 48 2 0000 CUSTOM~1.004 Windows\Customize.lst
5: 47 2 0000 STRMPL~1.005 Windows\strmplayer_middlelayer.dll
6: 46 2 0000 RTSP_S~1.006 Windows\rtsp_stack.dll
7: 45 2 0000 RTP_ST~1.007 Windows\rtp_stack.dll
8: 44 2 0000 ABSTRA~1.008 Windows\abstraction.dll
9: 41 2 0000 CAMERA~1.009 Windows\CameraWizard_(ht).htm
10: 40 2 0000 00000tma.010 Windows\tma.exe
11: 39 2 0000 ZOOM-I~1.011 Windows\Zoom-Indicator.bmp
12: 38 2 0000 VIDEO-~1.012 Windows\Video-Capture.bmp
13: 37 2 0000 THUMBN~1.013 Windows\Thumbnail-view.bmp
14: 36 2 0000 REMAIN~2.014 Windows\Remaining-video-time.bmp
15: 35 2 0000 REMAIN~1.015 Windows\Remaining-images.bmp
16: 34 2 0000 IMAGE-~1.016 Windows\Image-Capture.bmp
17: 33 2 0000 CONFIR~4.017 Windows\Confirm-Send.bmp
18: 32 2 0000 CONFIR~3.018 Windows\Confirm-Detailed-View.bmp
19: 31 2 0000 CONFIR~2.019 Windows\Confirm-Delete.bmp
20: 30 2 0000 CONFIR~1.020 Windows\Confirm-Back.bmp
21: 29 2 0000 COMPOS~1.021 Windows\Composition-Capture.bmp
22: 28 2 0000 CAPTUR~2.022 Windows\Capture-Size.bmp
23: 27 2 0000 CAPTUR~1.023 Windows\Capture-Indicator.bmp
24: 26 2 0000 CAMERA~1.024 Windows\Camera-Settings.bmp
25: 25 2 0000 AMBIEN~3.025 Windows\Ambience-Incandescent.bmp
26: 24 2 0000 AMBIEN~2.026 Windows\Ambience-Fluorescent.bmp
27: 23 2 0000 AMBIEN~1.027 Windows\Ambience-Daylight.bmp
28: 22 2 0000 POCKET~1.028 Windows\Pocket-PC-buttons.bmp
29: 17 2 0000 00ptspat.029 Windows\ptspat
30: 16 2 0000 00ptsdat.030 Windows\ptsdat
31: 15 2 0000 00amedat.031 Windows\amedat
32: 14 2 0000 00pwipat.032 Windows\pwipat.dat
33: 13 2 0000 0MidiLib.033 Windows\MidiLib.dll
34: 12 2 0000 MPEG4S~1.034 Windows\MPEG4SPVIDEOENC.dll
35: 11 2 0000 MP4WRI~1.035 Windows\MP4Writer.dll
36: 10 2 0000 0mp4spvd.036 Windows\mp4spvd.dll
37: 9 2 0000 MP4_RE~1.037 Windows\MP4_READER.dll
38: 8 2 0000 H263VI~1.038 Windows\H263VIDEOENC.dll
39: 7 2 0000 GSMAMR~2.039 Windows\gsmamrenc.dll
40: 6 2 0000 GSMAMR~1.040 Windows\GSMAMRDLL.dll
41: 5 2 0000 COLORC~1.041 Windows\colorConvScaling.dll
42: 4 2 0000 00AACDLL.042 Windows\AACDLL.dll
43: 3 2 0000 000Album.043 Windows\Album.exe
44: 2 2 0000 00Camera.044 Windows\Camera.exe
45: 19 2 0000 00Camera.045 %CE11%\Camera.lnk
46: 18 2 0000 000Album.046 %CE11%\Album.lnk
47: 20 2 0000 00Camera.047 Windows\AppButtons\Camera.lnk
48: 21 2 0000 00Camera.048 Windows\Help\Camera.lnk
49: 43 2 0000 000Totem.049 My Documents\Templates\Totem.gif
50: 42 2 0000 magazine.050 My Documents\Templates\magazine.gif
[registry]
1: 0 [HKCU\Software\HTC\Customize] Ver='1.0'
[shortcuts]
Processing file CallerIDRC11_WWE_1.5.sa.CAB
processor=0 versions: 3.00 .. 4.20
application=Tools provider=Customization
platforms: JUPITER, HPC
unknown: 0 0 1 0 0
[files]
1: 1 2 0000 0CESetup.001 %CE1%\Tools\CESetup.dll
2: 24 2 0000 CHECKF~1.002 Windows\CheckFile.exe
3: 23 2 0000 PLATFO~1.003 Windows\Platformxxx.reg
4: 22 2 0000 CUSTOM~1.004 Windows\Customize.lst
5: 21 2 0000 CALLER~1.005 Windows\Caller_ID_(ht).htm
6: 8 2 0000 IA_P_A~1.006 Windows\IA_P_AssignP.dll
7: 7 2 0000 IA_P_P~2.007 Windows\IA_P_PhotoV.dll
8: 6 2 0000 IA_P_P~1.008 Windows\IA_P_PhotoC.dll
9: 5 2 0000 IA_P_D~1.009 Windows\IA_P_DspCID.dll
10: 4 2 0000 IA_P_C~1.010 Windows\IA_P_Contacts.exe
11: 3 2 0000 IA_P_C~1.011 Windows\IA_P_Contacts.dll
12: 2 2 0000 IA_CAL~1.012 Windows\IA_Caller_ID.exe
13: 9 2 0000 PHOTOC~1.013 %CE11%\Photo Contacts.lnk
14: 10 2 0000 PHOTOC~1.014 Windows\Help\Photo Contacts.lnk
15: 16 2 0000 P-ABST~1.015 My Documents\Templates\P-Abstraction.pit
16: 15 2 0000 L-Soccer.016 My Documents\Templates\L-Soccer.pit
17: 14 2 0000 L-Heart2.017 My Documents\Templates\L-Heart2.pit
18: 13 2 0000 L-FRUI~2.018 My Documents\Templates\L-Fruit05.pit
19: 12 2 0000 L-FRUI~1.019 My Documents\Templates\L-Fruit04.pit
20: 11 2 0000 L-Dancer.020 My Documents\Templates\L-Dancer.pit
21: 19 2 0000 0unknown.021 My Documents\IA Caller ID Photos\unknown.DEF
22: 18 2 0000 notfound.022 My Documents\IA Caller ID Photos\notfound.DEF
23: 17 2 0000 CONTACTS.023 My Documents\IA Caller ID Photos\CONTACTS.DEF
24: 20 2 0000 IA_CAL~1.024 %CE4%\IA_Caller_ID.lnk
[registry]
1: 0 [HKCU\Software\HTC\Customize] Ver='1.0'
[shortcuts]
Processing file ClearVue_WWE.sa.CAB
processor=0 versions: 3.00 .. 4.20
application=Tools provider=Customization
platforms: JUPITER, HPC
unknown: 0 0 1 0 0
[files]
1: 1 2 0000 0CESetup.001 %CE1%\Tools\CESetup.dll
2: 4 2 0000 PPTVIE~1.002 %CE11%\ClearVue PPT.lnk
3: 2 2 0000 PDFVIE~1.003 %CE11%\ClearVue PDF.lnk
4: 5 2 0000 PPTVIE~1.004 Windows\Help\ClearVue PPT.lnk
5: 3 2 0000 PDFVIE~1.005 Windows\Help\ClearVue PDF.lnk
6: 38 2 0000 CHECKF~1.006 Windows\CheckFile.exe
7: 37 2 0000 PLATFO~1.007 Windows\Platformxxx.reg
8: 36 2 0000 CUSTOM~1.008 Windows\Customize.lst
9: 33 2 0000 00WTZlib.009 Windows\WTZlib.dll
10: 32 2 0000 WTXLSUtl.010 Windows\WTXLSUtl.dll
11: 31 2 0000 WTWDSExe.011 Windows\WTWDSExe.exe
12: 30 2 0000 0WTUImgr.012 Windows\WTUImgr.dll
13: 29 2 0000 000WTSho.013 Windows\WTSho.dll
14: 28 2 0000 WTRtfRdr.014 Windows\WTRtfRdr.dll
15: 27 2 0000 WTPPView.015 Windows\WTPPView.dll
16: 26 2 0000 WTPPUtil.016 Windows\WTPPUtil.dll
17: 25 2 0000 000WTPng.017 Windows\WTPng.dll
18: 24 2 0000 WTPicStm.018 Windows\WTPicStm.dll
19: 23 2 0000 WTPDFRdr.019 Windows\WTPDFRdr.dll
20: 22 2 0000 0WTMfdll.020 Windows\WTMfdll.dll
21: 21 2 0000 00WTJpeg.021 Windows\WTJpeg.dll
22: 20 2 0000 0WTImage.022 Windows\WTImage.dll
23: 19 2 0000 WTEcdJpg.023 Windows\WTEcdJpg.dll
24: 18 2 0000 00WTDraw.024 Windows\WTDraw.dll
25: 17 2 0000 WTDocUtl.025 Windows\WTDocUtl.dll
26: 16 2 0000 WTDocRdr.026 Windows\WTDocRdr.dll
27: 15 2 0000 WTDcdPng.027 Windows\WTDcdPng.dll
28: 14 2 0000 0WTdcdmz.028 Windows\WTdcdmz.dll
29: 13 2 0000 WTDcdJpg.029 Windows\WTDcdJpg.dll
30: 12 2 0000 0WTCVRes.030 Windows\WTCVRes.dll
31: 11 2 0000 WTCVPres.031 Windows\WTCVPres.htm
32: 10 2 0000 WTCVPres.032 Windows\WTCVPres.exe
33: 9 2 0000 WTCVPDFV.033 Windows\WTCVPDFV.htm
34: 8 2 0000 WTCVPDFV.034 Windows\WTCVPDFV.exe
35: 7 2 0000 0WTChart.035 Windows\WTChart.dll
36: 6 2 0000 WTAutoSh.036 Windows\WTAutoSh.dll
37: 35 2 0000 WESTTE~1.037 My Documents\WESTTEK Native Office Viewers.ppt
38: 34 2 0000 WESTTE~1.038 My Documents\WESTTEK-Product Info.pdf
[registry]
1: 0 [HKCU\Software\HTC\Customize] Ver='1.0'
[shortcuts]
Processing file GPRSMonitor_WWE.sa.CAB
processor=0 versions: 3.00 .. 4.20
application=Tools provider=Customization
platforms: JUPITER, HPC
unknown: 0 0 1 0 0
[files]
1: 1 2 0000 0CESetup.001 %CE1%\Tools\CESetup.dll
2: 8 2 0000 GPRSTO~1.002 Program files\GPRSMonitor\GPRSToday_en.txt
3: 7 2 0000 GPRSNO~1.003 Program files\GPRSMonitor\GPRSNotify_en.txt
4: 6 2 0000 GPRSMO~1.004 Program files\GPRSMonitor\GPRSMonitor_en.txt
5: 5 2 0000 0000skin.005 Program files\GPRSMonitor\skin.gif
6: 4 2 0000 GPRSTO~1.006 Program files\GPRSMonitor\GPRSToday.dll
7: 3 2 0000 GPRSNO~1.007 Program files\GPRSMonitor\GPRSNotify.exe
8: 2 2 0000 GPRSMO~1.008 Program files\GPRSMonitor\GPRSMonitor.exe
9: 22 2 0000 CHECKF~1.009 Windows\CheckFile.exe
10: 21 2 0000 PLATFO~1.010 Windows\Platformxxx.reg
11: 20 2 0000 CUSTOM~1.011 Windows\Customize.lst
12: 19 2 0000 000Setup.012 Windows\Setup.dll
13: 15 2 0000 GPRSMO~1.013 Windows\gprsmonitor_icon.2bp
14: 14 2 0000 CH280A~1.014 Windows\chart_traffic_monthly.2bp
15: 13 2 0000 CHART_~4.015 Windows\chart_traffic_hourly.2bp
16: 12 2 0000 CHART_~3.016 Windows\chart_traffic_daily.2bp
17: 11 2 0000 CHART_~2.017 Windows\chart_traffic.2bp
18: 10 2 0000 CHART_~1.018 Windows\chart_money.2bp
19: 9 2 0000 GPRSMO~1.019 Windows\gprsmonitor.htm
20: 16 2 0000 GPRSMO~1.020 Windows\Help\GPRS Monitor.lnk
21: 17 2 0000 GPRSNO~1.021 %CE4%\GPRS Notify.lnk
22: 18 2 0000 GPRSMO~1.022 %CE11%\GPRS Monitor.lnk
[registry]
1: 0 [HKCU\Software\HTC\Customize] Ver='1.0'
[shortcuts]
Processing file MIDI56.sa.CAB
processor=0 versions: 3.00 .. 4.20
application=Tools provider=Customization
platforms: JUPITER, HPC
unknown: 0 0 1 0 0
[files]
1: 1 2 0000 0CESetup.001 %CE1%\Tools\CESetup.dll
2: 5 2 0000 CHECKF~1.002 Windows\CheckFile.exe
3: 4 2 0000 PLATFO~1.003 Windows\Platformxxx.reg
4: 3 2 0000 CUSTOM~1.004 Windows\Customize.lst
5: 2 2 0000 RTPlugIn.005 Windows\RTPlugIn.dll
[registry]
1: 0 [HKCU\Software\HTC\Customize] Ver='1.0'
[shortcuts]
Processing file MMS1507_WWE.sa.CAB
processor=0 versions: 3.00 .. 4.20
application=Tools provider=Customization
platforms: JUPITER, HPC
unknown: 0 0 1 0 0
[files]
1: 1 2 0000 0CESetup.001 %CE1%\Tools\CESetup.dll
2: 8 2 0000 RECBKM~1.002 Program files\ArcSoft\ArcSoft MMS UA\RecBkMusic.wav
3: 7 2 0000 000RcDll.003 Program files\ArcSoft\ArcSoft MMS UA\RcDll.dll
4: 6 2 0000 MMSCOM~1.004 Program files\ArcSoft\ArcSoft MMS UA\MMS Composer.exe
5: 5 2 0000 000MMReg.005 Program files\ArcSoft\ArcSoft MMS UA\MMReg.exe
6: 4 2 0000 CANNED~1.006 Program files\ArcSoft\ArcSoft MMS UA\CannedText.txt
7: 3 2 0000 00000Amr.007 Program files\ArcSoft\ArcSoft MMS UA\Amr.enc
8: 2 2 0000 00000Amr.008 Program files\ArcSoft\ArcSoft MMS UA\Amr.dec
9: 11 2 0000 0Dogbark.009 My Documents\Dogbark.wav
10: 10 2 0000 0000ding.010 My Documents\ding.amr
11: 9 2 0000 Alouette.011 My Documents\Alouette.mid
12: 25 2 0000 CHECKF~1.012 Windows\CheckFile.exe
13: 24 2 0000 PLATFO~1.013 Windows\Platformxxx.reg
14: 23 2 0000 CUSTOM~1.014 Windows\Customize.lst
15: 22 2 0000 PLAYER~1.015 Windows\player_middlelayer.dll
16: 16 2 0000 MMSCOM~1.016 Windows\MMS Composer.htm
17: 12 2 0000 ARCSOF~1.017 Windows\ArcSoftTodayScreen.dll
18: 13 2 0000 MMSCOM~1.018 Windows\Help\MMS Composer.lnk
19: 14 2 0000 000MMReg.019 %CE4%\MMReg.lnk
20: 15 2 0000 MMSCOM~1.020 %CE11%\MMS Composer.lnk
21: 21 2 0000 0000Utah.021 My Documents\My Pictures\Utah.png
22: 20 2 0000 0000Pond.022 My Documents\My Pictures\Pond.jpg
23: 19 2 0000 000Photo.023 My Documents\My Pictures\Photo.gif
24: 18 2 0000 000Heart.024 My Documents\My Pictures\Heart.gif
25: 17 2 0000 BIRTHD~1.025 My Documents\My Pictures\Birthday_gift.gif
[registry]
1: 0 [HKCU\Software\HTC\Customize] Ver='1.0'
[shortcuts]
Processing file OEM_AKU1_WWE_4AP.sa.CAB
processor=0 versions: 3.00 .. 4.20
application=Tools provider=Customization
platforms: JUPITER, HPC
unknown: 0 0 1 0 0
[files]
1: 1 2 0000 0CESetup.001 %CE1%\Tools\CESetup.dll
2: 5 2 0000 GPRSAU~1.002 Temp\_GPRSAuthentication.exe
3: 4 2 0000 BTSETT~1.003 Temp\_BTSetting.exe
4: 3 2 0000 00000STK.004 Temp\_STK.exe
5: 2 2 0000 00WModem.005 Temp\_WModem.exe
6: 9 2 0000 CHECKF~1.006 Windows\CheckFile.exe
7: 8 2 0000 PLATFO~1.007 Windows\Platformxxx.reg
8: 7 2 0000 CUSTOM~1.008 Windows\Customize.lst
9: 6 2 0000 _MOVEF~1.009 Windows\_MoveFileList.txt
[registry]
1: 0 [HKCU\Software\HTC\Customize] Ver='1.0'
[shortcuts]
Processing file OEM_WWE_03120301.sa.CAB
processor=0 versions: 3.00 .. 4.20
application=Tools provider=Customization
platforms: JUPITER, HPC
unknown: 0 0 1 0 0
[files]
1: 1 2 0000 0CESetup.001 %CE1%\Tools\CESetup.dll
2: 6 2 0000 0Wavedev.002 temp\_Wavedev.dll
3: 5 2 0000 0Serial3.003 temp\_Serial3.dll
4: 4 2 0000 00rilgsm.004 temp\_rilgsm.dll
5: 3 2 0000 BTHASP~1.005 temp\_BthASPlugIn.dll
6: 2 2 0000 0AudioGW.006 temp\_AudioGW.dll
7: 10 2 0000 CHECKF~1.007 Windows\CheckFile.exe
8: 9 2 0000 PLATFO~1.008 Windows\Platformxxx.reg
9: 8 2 0000 CUSTOM~1.009 Windows\Customize.lst
10: 7 2 0000 _MOVEF~1.010 Windows\_MoveFileList.txt
[registry]
1: 0 [HKCU\Software\HTC\Customize] Ver='1.0'
[shortcuts]
Processing file TM_phone_class10.CAB
processor=0 versions: 3.00 .. 4.20
application=Tools provider=Customization
platforms: JUPITER, HPC
unknown: 0 0 1 0 0
[files]
1: 1 2 0000 0CESetup.001 %CE1%\Tools\CESetup.dll
2: 4 2 0000 CHECKF~1.002 Windows\CheckFile.exe
3: 3 2 0000 PLATFO~1.003 Windows\Platformxxx.reg
4: 2 2 0000 CUSTOM~1.004 Windows\Customize.lst
[registry]
1: 0 [HKCU\Software\HTC\Customize] Ver='1.0'
[shortcuts]
Processing file TMCOMREG.sa.CAB
processor=0 versions: 3.00 .. 4.20
application=Tools provider=Customization
platforms: JUPITER, HPC
unknown: 0 0 1 0 0
[files]
1: 1 2 0000 0CESetup.001 %CE1%\Tools\CESetup.dll
2: 4 2 0000 CHECKF~1.002 Windows\CheckFile.exe
3: 3 2 0000 PLATFO~1.003 Windows\Platformxxx.reg
4: 2 2 0000 CUSTOM~1.004 Windows\Customize.lst
[registry]
1: 0 [HKCU\Software\HTC\Customize] Ver='1.0'
[shortcuts]
Processing file TMD_AP_NL.sa.CAB
processor=0 versions: 3.00 .. 4.20
application=Tools provider=Customization
platforms: JUPITER, HPC
unknown: 0 0 1 0 0
[files]
1: 1 2 0000 0CESetup.001 %CE1%\Tools\CESetup.dll
2: 2 2 0000 0000skin.002 Program files\GPRSMonitor\skin.gif
3: 5 2 0000 CHECKF~1.003 Windows\CheckFile.exe
4: 4 2 0000 PLATFO~1.004 Windows\Platformxxx.reg
5: 3 2 0000 CUSTOM~1.005 Windows\Customize.lst
[registry]
1: 0 [HKCU\Software\HTC\Customize] Ver='1.0'
[shortcuts]
Processing file TMD_NL.sa.CAB
processor=0 versions: 3.00 .. 4.20
application=Tools provider=Customization
platforms: JUPITER, HPC
unknown: 0 0 1 0 0
[files]
1: 1 2 0000 0CESetup.001 %CE1%\Tools\CESetup.dll
2: 4 2 0000 CHECKF~1.002 Windows\CheckFile.exe
3: 3 2 0000 PLATFO~1.003 Windows\Platformxxx.reg
4: 2 2 0000 CUSTOM~1.004 Windows\Customize.lst
[registry]
1: 0 [HKCU\Software\HTC\Customize] Ver='1.0'
[shortcuts]
Processing file TMDNLCustomize.sa.CAB
processor=0 versions: 3.00 .. 4.20
application=Tools provider=Customization
platforms: JUPITER, HPC
unknown: 0 0 1 0 0
[files]
1: 1 2 0000 0CESetup.001 %CE1%\Tools\CESetup.dll
2: 32 2 0000 CHECKF~1.002 Windows\CheckFile.exe
3: 31 2 0000 PLATFO~1.003 Windows\Platformxxx.reg
4: 30 2 0000 CUSTOM~1.004 Windows\Customize.lst
5: 10 2 0000 _MOVEF~1.005 Windows\_MoveFileList.txt
6: 7 2 0000 0default.006 Windows\_default.htm
7: 6 2 0000 CM_ENT~1.007 Windows\CM_Entries.xml
8: 4 2 0000 T-MOBI~1.008 Windows\T-Mobile_Theme.tsk
9: 3 2 0000 0Splash2.009 Windows\Splash2.nb
10: 2 2 0000 0Splash1.010 Windows\Splash1.nb
11: 5 2 0000 RINGTO~1.011 Windows\Rings\RINGTONE 2.wav
12: 8 2 0000 T-MOBI~1.012 Windows\Favorites\T-Mobile PDA portal.url
13: 29 2 0000 0TapRes1.013 Temp\_TapRes1.dll
14: 28 2 0000 0default.014 Temp\_default.htm
15: 27 2 0000 0spd_lst.015 Temp\_spd_lst.gif
16: 26 2 0000 SPD_DL~1.016 Temp\_spd_dlrbtn.gif
17: 25 2 0000 SND_DL~2.017 Temp\_snd_dlrbtnd.gif
18: 24 2 0000 SND_DL~1.018 Temp\_snd_dlrbtn.gif
19: 23 2 0000 HLD_DL~2.019 Temp\_hld_dlrbtnd.gif
20: 22 2 0000 HLD_DL~1.020 Temp\_hld_dlrbtn.gif
21: 21 2 0000 ENDING~1.021 Temp\_ending_dlrbtn.gif
22: 20 2 0000 END_DL~2.022 Temp\_end_dlrbtnd.gif
23: 19 2 0000 END_DL~1.023 Temp\_end_dlrbtn.gif
24: 18 2 0000 0dlrclrd.024 Temp\_dlrclrd.gif
25: 17 2 0000 00dlrclr.025 Temp\_dlrclr.gif
26: 16 2 0000 00000dlr.026 Temp\_dlr.gif
27: 15 2 0000 0clg_out.027 Temp\_clg_out.gif
28: 14 2 0000 clg_miss.028 Temp\_clg_miss.gif
29: 13 2 0000 00clg_in.029 Temp\_clg_in.gif
30: 12 2 0000 CLG_DL~2.030 Temp\_clg_dlrbtnd.gif
31: 11 2 0000 CLG_DL~1.031 Temp\_clg_dlrbtn.gif
32: 9 2 0000 T-MOBI~1.032 Temp\_T-Mobile_banner.gif
[registry]
1: 0 [HKCU\Software\HTC\Customize] Ver='1.0'
[shortcuts]
Processing file Version_AKU1.sa.CAB
processor=0 versions: 3.00 .. 4.20
application=Tools provider=Customization
platforms: JUPITER, HPC
unknown: 0 0 1 0 0
[files]
1: 1 2 0000 0CESetup.001 %CE1%\Tools\CESetup.dll
2: 4 2 0000 CHECKF~1.002 Windows\CheckFile.exe
3: 3 2 0000 PLATFO~1.003 Windows\Platformxxx.reg
4: 2 2 0000 CUSTOM~1.004 Windows\Customize.lst
[registry]
1: 0 [HKCU\Software\HTC\Customize] Ver='1.0'
[shortcuts]
Processing file t-mobile_shortcuts_only(UK).PPC2002_ARM.CAB
processor=2577 versions: 3.00 .. 100.00
application=Web Enhancement provider=T-Mobile
platforms: HPC, JUPITER, PALM PC2
unknown: 0 0 1 0 0
[files]
1: 1 0 1000 TMOBIL~2.001 %CE2%\TMobileWebToday.dll
2: 2 0 0000 T-MOBI~1.002 %CE2%\T-Mobile Setup.dll
3: 3 0 0000 T-MOBI~2.003 %CE2%\T-Mobile PIE Launcher.exe
4: 4 0 0000 T-MOBI~3.004 %CE2%\T-Mobile Resetter.exe
[registry]
1: 0 [HKLM\Software\Microsoft\Today\Items\T-Mobile Homepage Plugin] Type=dword:00000004
2: 0 [HKLM\Software\Microsoft\Today\Items\T-Mobile Homepage Plugin] Enabled=dword:00000001
3: 0 [HKLM\Software\Microsoft\Today\Items\T-Mobile Homepage Plugin] Options=dword:00000000
4: 0 [HKLM\Software\Microsoft\Today\Items\T-Mobile Homepage Plugin] DLL=multisz:'\Windows\TMobileWebToday.dll'
5: 0 [HKLM\Software\DAT Enterprises Ltd.\TMobile Today Web] WebDisplayText='t-zones'
6: 0 [HKLM\Software\DAT Enterprises Ltd.\TMobile Today Web] WebURL='www.t-zones.co.uk'
[shortcuts]
1: 0 1 2 %CE17%\t-zones.lnk = %CE2%\T-Mobile PIE Launcher.exe
Itsme rulezzz !!
Ok, so with the new 2.2 update being pushed out, I've been really excited. Someone tossed me the official update.zip, I tried to flash it with the stock recovery. When I do this, it says something about a Virgin_Mobile.apk file and 2 hashcodes that don't match, as well as Status 7, after it gets to the 'verifying system' stage.
I've not modified the phone much outside of using rageagainstthecage to remove crapware apps and to remove the bootup and shutdown sounds. Now, a guy by the name of David was helping me figure this out. He had me snag z4root (which is much nicer than rage ) and flash_image for samsung moment eclair to install a 2.1 kernel to try and fix this issue. I did a chmod 777 on flash_image and when I tried running the command:
Code:
/data/local/tmp/flash_image kernel /sdcard/system/zImage
I get this big-ol' error here:
Code:
XSR VERSION: 1.5.2-p4
minor position size blocks id
1: 0x00000000-0x00020000 0x00020000 1 0
2: 0x00020000-0x00160000 0x00140000 10 1
3: 0x00160000-0x001c0000 0x00060000 3 2
4: 0x001c0000-0x00800000 0x00640000 50 3
5: 0x00800000-0x0d000000 0x0c800000 1600 4
6: 0x0d000000-0x18b00000 0x0bb00000 1496 5
7: 0x18b00000-0x1ef00000 0x06400000 800 6
8: 0x1ef00000-0x1f540000 0x00640000 50 7
(0) bad mapping information
No BadBlock RsvBlock
0: 3904 4014
can't find kernel partition
1: 20000 1 boot12: 140000 10 boot23: 60000 3 boot34:
640000 50 boot5: c800000 1600 system6: bb00000 1496 data7: 6
400000 800 cache8: 640000 50 recovery
What do I do? How do I fix this?
Hi guys,
My HD2 was the official HTC for repair because my USB broke
They exchanged the board, now I can not flashing to the CWR for android, even WM7
I did the following:
- HD2 came om SPL 3.3 (I think)
- I put in version 2.08 and did a HSPL task29
- Installed the radio 2.15.50.14
- And installed MAGLDR 1:13
So far so good
Now go to "usb flash" and run the DAF.exe but after me the following error:
"An error has ocurred
Read below for more information
Error Description: Partition data send failed:
Info: \ RSPL \ RSPL.cpp (815)
Error Description: Flash Write Failed.
Info: \ RSPL \ RSPL.cpp (599) "
And at mobile phone shows me
"Layout ... PC = 6, ASI = 5, 5 = OASI
Erease ...
0: Total = 8, extra = 2
k = 21 -> 21 221 241, 1000
1: part = 33, part2 = 33
k = 28 -> 28 242 269, 1000
2: part1 = 40, part2 = 40
3: total = 1600, Extra = 80
4: total = 40, extra = 2
[ASIZE] START: 8D2 END: F40 SIZE: 66E
PARITITON NEW LAYOUT
0: 0219 0221 50 01
1: 0221 0242 62 0D
2: 0242 026A 61 09
3: 026A 08AA 50 01
4: 08AA 08D2 50 01
5: 08D2 0F40 50 51
Erease ...
D S: 0 E: 219
D S: 1 E: 221
D S: 2 E: 242
D S: 3 E: 26A
D S: 4 E: 8AA
D S: 5 E: 8D2
Save EMBR
Default OS is Ad NAND...
Empty 0 Partition ... OK
Flashing 1 Partition...1 [221-242] M0 "
And stops with the white bar below + / - 10%
what's happens with my phone??
inside the file 'flash.cfg' (can open with notepad) what does it say?
Ok i found the solution and calls Windows Mobile Center... after install that i can do all stuf...
Hi, I had recently flashed the jellybean leak Ota for my tab(it's p3100), I had then flashed cwm. Now I tried resetting my flash counter but after rebooting it still stuck at 1 count. What should I do?
Sent from my GT-P3100 using XDA Premium HD app
Help anyone?
Sent from my GT-P3100 using XDA Premium HD app
Maybe flash back to ics. And reset the counter
Sent from my GT-I9100 using Tapatalk 2
Aditya16 said:
Hi, I had recently flashed the jellybean leak Ota for my tab(it's p3100), I had then flashed cwm. Now I tried resetting my flash counter but after rebooting it still stuck at 1 count. What should I do?
Sent from my GT-P3100 using XDA Premium HD app
Click to expand...
Click to collapse
have you tried "Triangule Away" ?
you can installed it from google play
but you need to root your device first
sapiterbang said:
have you tried "Triangle Away" ?
you can installed it from google play
but you need to root your device first
Click to expand...
Click to collapse
I resetted it with that only. Is it some bug in jb?
Sent from my GT-P3100 using XDA Premium HD app
Alvin Lai said:
Maybe flash back to ics. And reset the counter
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Will try that.
Sent from my GT-P3100 using XDA Premium HD app
May be try installing supersu ( not superuser) from google play and give permissions to triangle away
Install latest version 1.95 of triangle away
Sent from Galaxy S2 or Galaxy Tab2
I confirm Triangle Away and SuperSU combination still work in JB.
So after rebooting and going to the download mode, even for me it is zero, but after exiting and booting back it goes back to 1 count.
Sent from my GT-P3100 using XDA Premium HD app
Aditya16 said:
So after rebooting and going to the download mode, even for me it is zero, but after exiting and booting back it goes back to 1 count.
Sent from my GT-P3100 using XDA Premium HD app
Click to expand...
Click to collapse
Post your issue in Triangle Away thread. Maybe someone can help you...
---------- Post added at 05:06 PM ---------- Previous post was at 05:06 PM ----------
Aditya16 said:
So after rebooting and going to the download mode, even for me it is zero, but after exiting and booting back it goes back to 1 count.
Sent from my GT-P3100 using XDA Premium HD app
Click to expand...
Click to collapse
Post your issue in Triangle Away thread. Maybe someone could help you
Waw... Back from recovery I got +1. This is not because JB but Sbl.bin updated (download mode in potrait position now). The second boot loader checkbit RECOVERY partition:
Code:
Secondary Bootloader v3.1 version.
Copyright (C) 2011 System S/W Group. Samsung Electronics Co., Ltd.
Board: GT-P3100 REV 04-REAL / Sep 17 2012 13:37:57
booting code=0x0
===== PARTITION INFORMATION =====
ID : X-loader (0x1)
DEVICE : MMC
FIRST UNIT : 0
NO. UNITS : 0
=================================
ID : EFS (0x4)
DEVICE : MMC
FIRST UNIT : 8192
NO. UNITS : 40960
=================================
ID : SBL1 (0x2)
DEVICE : MMC
FIRST UNIT : 49152
NO. UNITS : 4096
=================================
ID : SBL2 (0x3)
DEVICE : MMC
FIRST UNIT : 53248
NO. UNITS : 4096
=================================
ID : PARAM (0x5)
DEVICE : MMC
FIRST UNIT : 57344
NO. UNITS : 16384
=================================
ID : KERNEL (0x6)
DEVICE : MMC
FIRST UNIT : 73728
NO. UNITS : 16384
=================================
ID : RECOVERY (0x7)
DEVICE : MMC
FIRST UNIT : 90112
NO. UNITS : 16384
=================================
ID : CACHE (0x8)
DEVICE : MMC
FIRST UNIT : 106496
NO. UNITS : 1433600
=================================
ID : MODEM (0x9)
DEVICE : MMC
FIRST UNIT : 1540096
NO. UNITS : 40960
=================================
ID : FACTORYFS (0xa)
DEVICE : MMC
FIRST UNIT : 1581056
NO. UNITS : 2867200
=================================
ID : DATAFS (0xb)
DEVICE : MMC
FIRST UNIT : 4448256
NO. UNITS : 25280478
=================================
ID : HIDDEN (0xd)
DEVICE : MMC
FIRST UNIT : 29728734
NO. UNITS : 1048576
=================================
ID : GANG (0x0)
DEVICE : MMC
FIRST UNIT : 0
NO. UNITS : 0
=================================
loke_init: j4fs_open..success
<start_checksum:310>CHECKSUM_HEADER_SECTOR :42
<start_checksum:313>offset:42, size:1024
Not Need Movinand Checksum
load_lfs_parameters valid magic code and version.
switch_sel_str='1'
switch_sel_int='1'
load_debug_level: read debug level successfully(0x574f4c44)...LOW
init_ddi_data: usable ddi data.
Set charging current TA
omap_max17042_read_temp: FG Temp raw_data : 0x2723
read_temp_adc:adc_data : 772
read_temp_adc:adc_data : 763
read_temp_adc:adc_data : 765
read_temp_adc:adc_data : 759
read_temp_adc:adc_data : 758
check_battery_type: fg temp : 39136, adc_temp : 420
check_battery_type: Set BATTERY_TYPE_SDI
omap_max17042_set_model_data : Already fuel gauge initialized !!
max17042_compensate_soc: vcell(3840), rep_soc(43)
calculate_table_soc: charging status : 2, vcell(3840), table_soc(52)
[SBL] VFOCV MSB : 0xc0, LSB : 0x7
[SBL_CHARGER] SOC : 43, VCELL : 3840, VFSOC : 42, VFOCV : 3840
save param.blk, size: 5268
save param.blk successfully.
save switch_sel(1)...ok
reading nps status file is successfully!.
nps status=0x504d4f43
g_nRebootReason = 0x1
set_lcd_panel_id: panel_adc=142
*** ltn070nl01_power_on ***
lcd_pannel_id=2
Autoboot (1 seconds) in progress, press any key to stop .
boot_kernel: debug level low!
checkbit: find RECOVERY
checkbit (f55f0aa0)
Kernel @ 81808000 (0x3f715c bytes)
Ramdisk @ 82800000 (0x880aa bytes)
Starting kernel at 0x81808000...
Now I need Sbl.bin backup from ICS!
ketut.kumajaya said:
Waw... Back from recovery I got +1. This is not because JB but Sbl.bin updated (download mode in potrait position now). The second boot loader checkbit RECOVERY partition:
Code:
Secondary Bootloader v3.1 version.
Copyright (C) 2011 System S/W Group. Samsung Electronics Co., Ltd.
Board: GT-P3100 REV 04-REAL / Sep 17 2012 13:37:57
booting code=0x0
===== PARTITION INFORMATION =====
ID : X-loader (0x1)
DEVICE : MMC
FIRST UNIT : 0
NO. UNITS : 0
=================================
ID : EFS (0x4)
DEVICE : MMC
FIRST UNIT : 8192
NO. UNITS : 40960
=================================
ID : SBL1 (0x2)
DEVICE : MMC
FIRST UNIT : 49152
NO. UNITS : 4096
=================================
ID : SBL2 (0x3)
DEVICE : MMC
FIRST UNIT : 53248
NO. UNITS : 4096
=================================
ID : PARAM (0x5)
DEVICE : MMC
FIRST UNIT : 57344
NO. UNITS : 16384
=================================
ID : KERNEL (0x6)
DEVICE : MMC
FIRST UNIT : 73728
NO. UNITS : 16384
=================================
ID : RECOVERY (0x7)
DEVICE : MMC
FIRST UNIT : 90112
NO. UNITS : 16384
=================================
ID : CACHE (0x8)
DEVICE : MMC
FIRST UNIT : 106496
NO. UNITS : 1433600
=================================
ID : MODEM (0x9)
DEVICE : MMC
FIRST UNIT : 1540096
NO. UNITS : 40960
=================================
ID : FACTORYFS (0xa)
DEVICE : MMC
FIRST UNIT : 1581056
NO. UNITS : 2867200
=================================
ID : DATAFS (0xb)
DEVICE : MMC
FIRST UNIT : 4448256
NO. UNITS : 25280478
=================================
ID : HIDDEN (0xd)
DEVICE : MMC
FIRST UNIT : 29728734
NO. UNITS : 1048576
=================================
ID : GANG (0x0)
DEVICE : MMC
FIRST UNIT : 0
NO. UNITS : 0
=================================
loke_init: j4fs_open..success
<start_checksum:310>CHECKSUM_HEADER_SECTOR :42
<start_checksum:313>offset:42, size:1024
Not Need Movinand Checksum
load_lfs_parameters valid magic code and version.
switch_sel_str='1'
switch_sel_int='1'
load_debug_level: read debug level successfully(0x574f4c44)...LOW
init_ddi_data: usable ddi data.
Set charging current TA
omap_max17042_read_temp: FG Temp raw_data : 0x2723
read_temp_adc:adc_data : 772
read_temp_adc:adc_data : 763
read_temp_adc:adc_data : 765
read_temp_adc:adc_data : 759
read_temp_adc:adc_data : 758
check_battery_type: fg temp : 39136, adc_temp : 420
check_battery_type: Set BATTERY_TYPE_SDI
omap_max17042_set_model_data : Already fuel gauge initialized !!
max17042_compensate_soc: vcell(3840), rep_soc(43)
calculate_table_soc: charging status : 2, vcell(3840), table_soc(52)
[SBL] VFOCV MSB : 0xc0, LSB : 0x7
[SBL_CHARGER] SOC : 43, VCELL : 3840, VFSOC : 42, VFOCV : 3840
save param.blk, size: 5268
save param.blk successfully.
save switch_sel(1)...ok
reading nps status file is successfully!.
nps status=0x504d4f43
g_nRebootReason = 0x1
set_lcd_panel_id: panel_adc=142
*** ltn070nl01_power_on ***
lcd_pannel_id=2
Autoboot (1 seconds) in progress, press any key to stop .
boot_kernel: debug level low!
checkbit: find RECOVERY
checkbit (f55f0aa0)
Kernel @ 81808000 (0x3f715c bytes)
Ramdisk @ 82800000 (0x880aa bytes)
Starting kernel at 0x81808000...
Now I need Sbl.bin backup from ICS!
Click to expand...
Click to collapse
How will i get this sbl.bin file from?
Aditya16 said:
How will i get this sbl.bin file from?
Click to expand...
Click to collapse
From /dev/block/mmcblk0p2 and /dev/block/mmcblk0p3. Be careful, this is a critical part of boot process.
I really do not not know how to do it advice please?
Sent from my GT-P3100 using XDA Premium HD app
News update guy's. Chainfire pm'ed me saying that he will look into the matter. Now all we can do is cross our finger and wait.
Oh and also this download mode does not show +1 when I replaced CWM with stock recovery. I wonder why?
Sent from my GT-P3100 using XDA Premium HD app
UPDATE:
No warning when boot to stock JB XXCLI5 recovery:
Code:
g_nRebootReason = 0x2
set_lcd_panel_id: panel_adc=143
*** ltn070nl01_power_on ***
lcd_pannel_id=2
Autoboot (1 seconds) in progress, press any key to stop .
boot_kernel: debug level low!
checkbit: find RECOVERY
checkbit (f55f0aa0)
Kernel @ 81808000 (0x3f715c bytes)
Ramdisk @ 82800000 (0x135b4d bytes)
save param.blk, size: 5268
save param.blk successfully.
save switch_sel(1)...ok
Starting kernel at 0x81808000...
More investigation needed, when boot to unofficial recovery:
Code:
g_nRebootReason = 0x2
set_lcd_panel_id: panel_adc=143
*** ltn070nl01_power_on ***
lcd_pannel_id=2
Autoboot (1 seconds) in progress, press any key to stop .
boot_kernel: debug level low!
checkbit: find RECOVERY
checkbit (f55f0aa0)
Kernel @ 81808000 (0x39a7b0 bytes)
Ramdisk @ 82800000 (0x1e4fc6 bytes)
[WARNING] Current kernel is NOT official binary!!!
save param.blk, size: 5268
save param.blk successfully.
save switch_sel(1)...ok
Starting kernel at 0x81808000...
Normal boot to stock JB XXCLI5 kernel:
Code:
g_nRebootReason = 0x1
set_lcd_panel_id: panel_adc=142
*** ltn070nl01_power_on ***
lcd_pannel_id=2
Autoboot (1 seconds) in progress, press any key to stop .
boot_kernel: debug level low!
checkbit: find RECOVERY
checkbit (f55f0aa0)
Kernel @ 81808000 (0x3f715c bytes)
Ramdisk @ 82800000 (0x880aa bytes)
Starting kernel at 0x81808000...
Parsed above value from /proc/last_kmsg. From last_kmsg value (second boot loader message?), I can confirm my boot logo hack is safe. Sbl successfuly mount param.lfs:
Code:
loke_init: j4fs_open..success
<start_checksum:310>CHECKSUM_HEADER_SECTOR :42
<start_checksum:313>offset:42, size:1024
Not Need Movinand Checksum
load_lfs_parameters valid magic code and version.