Related
One man has successfully integrated WM6 modules into XIP of hx4700. The result: working WM5 with WM6 modules from "msxipkernel" package (taken from Universal)
Maybe his method can help us to port WM6 on Himalaya?
(Original thread: http://4pda.ru/forum/index.php?showtopic=44886)
Here is what he did (translate from russian):
1. Take "xipport". Modified one is attached.
2. dump xip & build maps for hx4700. Save "map.txt"
3. dump xip & build maps from wm6 xip (HTC Universal or any other device)
4. Just copy all modules and those ".txt" files from msxipkernel (wm6) except "cachefilt", "encfilt", "filesys".
5. "realloc P" & write maps (it works for hx4700). If not enough mem for realloc - then increase "physlast" in "romhdr.txt"
6. In new "map.txt" addresses of regions in section "first Dll... last Dll" for 4 files in "oemxipkernel" must stay unchanged, for example:
---
01fe1000 - 01fe2000 L00001000 actual of region_1 Fsdspy.dll
01fe2000 - 01fef000 L0000d000 actual of region_1 msflash.dll
01fef000 - 01ff0000 L00001000 actual of region_2 cecompr.dll
01ff0000 - 01ff1000 L00001000 actual of region_1 ceddk.dll
---
If they are not then fix in corresponding "imageinfo.txt" value of o32[1(2)].o32_realaddr
7. Repeat the same for all files in "msxipkernel". We need that "actual of region_1" correspond with "map.txt" (wm6). For files "pm.dll" and "regenum.dll" will be "!!!!!!!!!!!!!" symbols.
8. Edit "o32[1].o32_realaddr" for "pm.dll" and "regenum.dll" to make there regions exactly concur with regions of excepted "cachefilt", "encfilt". Such a replacement. After all this section must be:
---
01fa01fe - 01fa01fe L00000000 Start: first DLL address
01fa01fe - 01fe1000 L00040e02 NUL
01fe1000 - 01fe2000 L00001000 actual of region_1 Fsdspy.dll
01fe2000 - 01fef000 L0000d000 actual of region_1 msflash.dll
01fef000 - 01ff0000 L00001000 actual of region_2 cecompr.dll
01ff0000 - 01ff1000 L00001000 actual of region_1 ceddk.dll
01ff1000 - 01ff2000 L00001000 actual of region_1 mspart.dll
01ff2000 - 01ff3000 L00001000 actual of region_1 imgfs.dll
01ff3000 - 01ff4000 L00001000 actual of region_1 fsreplxfilt.dll
01ff4000 - 01ff5000 L00001000 actual of region_1 fsdmgr.dll
01ff5000 - 01ff6000 L00001000 actual of region_1 fatutil.dll
01ff6000 - 01ff7000 L00001000 actual of region_1 fatfsd.dll
01ff7000 - 01ff8000 L00001000 actual of region_1 regenum.dll
01ff8000 - 01ff9000 L00001000 actual of region_1 diskcache.dll
01ff9000 - 01ffa000 L00001000 actual of region_1 devmgr.dll
01ffa000 - 01ffc000 L00002000 actual of region_1 crypt32.dll
01ffc000 - 01ffd000 L00001000 actual of region_1 coredll.dll
01ffd000 - 01ffe000 L00001000 actual of region_1 certmod.dll
01ffe000 - 01fff000 L00001000 actual of region_1 pm.dll
01fff000 - 02000000 L00001000 actual of region_1 busenum.dll
02000000 - 02000000 L00000000 End: last DLL address
---
9. Look into "map.txt" (Universal) to find where was the first region of "regenum"
---
01fef000 - 01ff0000 L00001000 actual of region_1 regenum.dll
---
If it was "0x1FEF000", and we changed it to "01ff7000". So we have to patch file. Edit "S000" of "regenum.dll" and fix all dword-aligned values that looks like: XX XF FE 01 to XX X7 FF 01 (so we see them in "winhex"). It can be automated with a simple script
10. Do the same for "S000" in "pm.dll"
11. Set in all "imageinfo.txt" cvalue of "e32_subsysminor" to 1.
12. Write new placement of "ROMHDR" into "S000" of "nk.exe"
13. Make ROM, flash and Try!
hx4700 wm6
hx4700 wm6, frankinstein style. interesting development anyone upto trying it?
hey Avis. He did not mention in his steps when to introduce cachefilt, etc.
could you possibly ask him to post the original XIP.bin and the WM6 XIP.bin; so, we could study further. (sorry, I don't speak Russian)
This is promising...
Jiggs
Oh, I get it. He didn't include cachefilt and stuff because he's still using WM5 system files...
step 12 is vague. write new placement of "ROMHDR" into S000 of "NK.EXE" BUT I couldn't locate any instance of the address of ROMHDR in S000!
hx4700 wm6
jiggs, sounds like you got skillz. can anyone help develop this solution? need to get more people aware of this..
jiggs said:
step 12 is vague. write new placement of "ROMHDR" into S000 of "NK.EXE" BUT I couldn't locate any instance of the address of ROMHDR in S000!
Click to expand...
Click to collapse
okay I got it. there is rom_00 hdr in map.txt those addresses are the ones I can locate in S000 nk.exe. However, I have flashed my deviced three (3) times already, but it won't boot nor even show the boot screen.
What is not clear to me is step 6. what is my reference map.txt: hima? or uni?
lyger said:
jiggs, sounds like you got skillz. can anyone help develop this solution? need to get more people aware of this..
Click to expand...
Click to collapse
tell bepe and tofclock, they're more experienced in porting...
did you use a hx4700 or a different device? Shame it didn't start-up.. anyone provide any insight on how this works?
Avis,
Could you please request for sample xip.bin's so we can study further?
Thanks in advance.
Jiggs
This method will not work in our Himalaya because we need nk.exe that is compatible with the new CORE. Unfortunately, our very old nk.exe is not compatible with WM6 CORE.
I realize this is about the Himalaya,
But does this mean we might have a working WM6 for the hx4700?
There are like thousands of people waiting on that. we've even signed petitions to try and get hp to do it :/
well if anyone needs help in porting wm6 to a wm5 device that has no wm6 kernel, i can try and help.
i've already contributed to some such projects which have been successful.
i suspect that you and Avis are the only ones working on it
http://forum.xda-developers.com/showthread.php?t=293352&page=3
Rudegar said:
i suspect that you and Avis are the only ones working on it
http://forum.xda-developers.com/showthread.php?t=293352&page=3
Click to expand...
Click to collapse
i was on holiday....how is the hx4700 port right now?
edit: ok i checked it out
For ATOM EXEC Only!
UPDATED DECEMBER 19, 2007
NEVER ATTEMPT TO UPDATE YOUR DEVICE USING SD CARD FLASHING!!!
{
"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"
}
ROM: WM6.0 20071216A3WWE
DOWNLOAD 6MB PP (51.95 program memory) : rapidshare|mediafire
ROM: WM6.1 B19209 AKU 1.0.2 20080417A5WWE
DOWNLOAD 6MB PP (51.95 program memory) : see my signature
NOTE: IF YOU DON'T WANT TO DOWNLOAD AGAIN, YOU CAN CHANGE THE PAGEPOOL YOURSELF. INSTRUCTIONS HERE
BUG FIXES: OS 5.2.1938 (Build 18508.0.7b.0)
Features: WM6 Clean Edition
Camera Working Back.
Headset Working Back.
NETCF 3.5
New Device Software Update Utility - now you can choose what you want to update!! on this case mostly you only need either OS Only or OS + Extended ROM.
XIP Core Upgrade
Memory Boost Up to 20480 bytes.
Speed Improvement!!
Built-in SRS WOW HD
Built-in Power Management
Windows Live 10.6.33.0600
Extended ROM:
1. Fann Capture Screen Utility
2. Helmi Touch Dialer 2G
Bugs: A2DP is not 100% compatible. (some device working, some not)
Steps:
1. Uncompress the 7z file into C:\Windows\Temp
2. Verify the files, should be 6 files
3. Execute Device Software Update Utility.exe
4. Follow the rest steps.
Please charge your device after upgrade to 100% full before you comment the drain batteries on your device!!.
This UNOFFICIAL ROM is still under development and you can't expect support from it. If you can't afford to have a buggy phone, this is not for you. By flashing this TEST ROM, it means you are willing to take the risks, solve any bugs encountered yourself and report problems to this forum.
Like I had mentioned before in one of the ATOM thread, ATOM EXEC device can boost more memory. In order to do that we need to re adjust the memory address on nk.exe and giisr.dll like below (of course need to change S00x)
Code:
04000000 - 80500000 L7c500000 NUL
80500000 - 80500000 L00000000 Start: start of RAM
80500000 - 80506000 L00006000 uninitialized data of region_2 nk.exe
80506000 - 80561000 L0005b000 initialized data of region_3 nk.exe
80561000 - 80562000 L00001000 initialized data of region_1 giisr.dll
80562000 - 80562000 L00000000 ------ start of RAM free space
80562000 - 84000000 L03a9e000 NUL
84000000 - 84000000 L00000000 End: end of RAM
84000000 - 9ac00000 L16c00000 NUL
For ATOM EXEC WM6 Cooker, you may used my XIP as a reference. you may take nk.exe and giisr.dll and port into your own XIP (increase about 500 KB)
For ATOM WM6 Cooker, you also will still able to gain more memory (about 20480 byte) by using my giisr.dll
please note: don't forget credit to me when you used my nk.exe and giisr.dll
so never less, I saw quite many people know how to cook WM6 on ATOM device, well I'm happy to see that. keep working boys!!
reserved for 3rd party standard applications
Hi mate, very nice, cant wait to try it out!
homer285 said:
Hi mate, very nice, cant wait to try it out!
Click to expand...
Click to collapse
it's up now
you can update into your own xip
sad to hear that until now you wasn't able to fix the A2DP...
vickoy said:
sad to hear that until now you wasn't able to fix the A2DP...
Click to expand...
Click to collapse
I'm afraid so, till someone build/crack the new A2DP WM6 driver for ATOM/EXEC Device.
vickoy said:
sad to hear that until now you wasn't able to fix the A2DP...
Click to expand...
Click to collapse
I think someone is working on this, out of interest what's your headset brand and model #, thanks.
Woa... Nice Updated, bro! Very interesting. Will try, now!
i think the links are backwards i.e the 8mb pagepool link directs to the 6mb pagepool download and vice versa
homer285 said:
I think someone is working on this, out of interest what's your headset brand and model #, thanks.
Click to expand...
Click to collapse
I am currently using sony ericsson HBH-DS220. So far, I can still use the current driver with my headset, I just need to do some trick... like for example if I need to used it to listen to music I just need to turn it off, run iplay and then turn it back on... quite irritating but no choice.
btw, having a value of 0 in A2DP settings of JointStereo is a lot more better and giving true stereo compare to value of 1, that was being suggested from the other thread.
yung_vu said:
i think the links are backwards i.e the 8mb pagepool link directs to the 6mb pagepool download and vice versa
Click to expand...
Click to collapse
yeah right! I just downloaded the 8MB pagepool but I've got here 6MB...LoL
chartreux said:
Like I had mentioned before in one of the ATOM thread, ATOM EXEC device can boost more memory. In order to do that we need to re adjust the memory address on nk.exe and giisr.dll like below (of course need to change S00x)
Code:
04000000 - 80500000 L7c500000 NUL
80500000 - 80500000 L00000000 Start: start of RAM
80500000 - 80506000 L00006000 uninitialized data of region_2 nk.exe
80506000 - 80561000 L0005b000 initialized data of region_3 nk.exe
80561000 - 80562000 L00001000 initialized data of region_1 giisr.dll
80562000 - 80562000 L00000000 ------ start of RAM free space
80562000 - 84000000 L03a9e000 NUL
84000000 - 84000000 L00000000 End: end of RAM
84000000 - 9ac00000 L16c00000 NUL
For ATOM EXEC WM6 Cooker, you may used my XIP as a reference. you may take nk.exe and giisr.dll and port into your own XIP (increase about 500 KB)
For ATOM WM6 Cooker, you also will still able to gain more memory (about 20480 byte) by using my giisr.dll
please note: don't forget credit to me when you used my nk.exe and giisr.dll
so never less, I saw quite many people know how to cook WM6 on ATOM device, well I'm happy to see that. keep working boys!!
Click to expand...
Click to collapse
Thank you so much, downloading.......................
But it's better if you tell us how to do that ourself.
I replace my giisrd.dll by yours to my Atom, but nothing happens. what's the matter ? Do I need to change the nk.exe too ?
medkid said:
I replace my giisrd.dll by yours to my Atom, but nothing happens. what's the matter ? Do I need to change the nk.exe too ?
Click to expand...
Click to collapse
use xipport and click write map button.
chartreux said:
use xipport and click write map button.
Click to expand...
Click to collapse
I do write map but see that nothing changes
80500000 - 80500000 L00000000 Start: start of RAM
80500000 - 80506000 L00006000 uninitialized data of region_2 nk.exe
80506000 - 80561000 L0005b000 initialized data of region_3 nk.exe
80561000 - 80562000 L00001000 initialized data of region_1 giisr.dll
80562000 - 80567000 L00005000 NUL
80567000 - 80567000 L00000000 ------ start of RAM free space
80567000 - 84000000 L03a99000 NUL
84000000 - 84000000 L00000000 End: end of RAM
medkid said:
I do write map but see that nothing changes
80500000 - 80500000 L00000000 Start: start of RAM
80500000 - 80506000 L00006000 uninitialized data of region_2 nk.exe
80506000 - 80561000 L0005b000 initialized data of region_3 nk.exe
80561000 - 80562000 L00001000 initialized data of region_1 giisr.dll
80562000 - 80567000 L00005000 NUL
80567000 - 80567000 L00000000 ------ start of RAM free space
80567000 - 84000000 L03a99000 NUL
84000000 - 84000000 L00000000 End: end of RAM
Click to expand...
Click to collapse
your original XIP
Code:
04000000 - 80500000 L7c500000 NUL
80500000 - 80500000 L00000000 Start: start of RAM
80500000 - 80506000 L00006000 uninitialized data of region_2 nk.exe
80506000 - 80561000 L0005b000 initialized data of region_3 nk.exe
80561000 - 80566000 L00005000 NUL
80566000 - 80567000 L00001000 initialized data of region_1 giisr.dll
80567000 - 80567000 L00000000 ------ start of RAM free space
80567000 - 84000000 L03a99000 NUL
84000000 - 84000000 L00000000 End: end of RAM
84000000 - 9ac00000 L16c00000 NUL
and now after copy my giisr.dll, your giisr.dll address already re-adjust to 80561000 from 80566000. (save 20480 bytes)
the next step you will need to adjust start of RAM free space to 80562000 (inside ROMHDR.txt)
chartreux said:
your original XIP
Code:
04000000 - 80500000 L7c500000 NUL
80500000 - 80500000 L00000000 Start: start of RAM
80500000 - 80506000 L00006000 uninitialized data of region_2 nk.exe
80506000 - 80561000 L0005b000 initialized data of region_3 nk.exe
80561000 - 80566000 L00005000 NUL
80566000 - 80567000 L00001000 initialized data of region_1 giisr.dll
80567000 - 80567000 L00000000 ------ start of RAM free space
80567000 - 84000000 L03a99000 NUL
84000000 - 84000000 L00000000 End: end of RAM
84000000 - 9ac00000 L16c00000 NUL
and now after copy my giisr.dll, your giisr.dll address already re-adjust to 80561000 from 80566000. (save 20480 bytes)
the next step you will need to adjust start of RAM free space to 80562000 (inside ROMHDR.txt)
Click to expand...
Click to collapse
Thanks for enlightening me.
I do it and now flashing my Atom again
after flashed:it seems that I don't see any difference, although MAP.txt has changed:
80500000 - 80500000 L00000000 Start: start of RAM
80500000 - 80506000 L00006000 uninitialized data of region_2 nk.exe
80506000 - 80561000 L0005b000 initialized data of region_3 nk.exe
80561000 - 80562000 L00001000 initialized data of region_1 giisr.dll
80562000 - 80562000 L00000000 ------ start of RAM free space
80562000 - 84000000 L03a9e000 NUL
and the ROMHDR.txt:
Code:
dllfirst: D=01F901FD
dlllast: 02000000
physfirst: P=9AC00000
physlast: 9AFE2990
nummods: (00000018)
ulRAMStart: R=80500000
ulRAMFree: 80562000
ulRAMEnd: 84000000
ulCopyEntries: (00000002)
ulCopyOffset: P+00117FDC
ulProfileLen: 00000000
ulProfileOffset: 00000000
numfiles: (00000008)
ulKernelFlags: 00000002
ulFSRamPercent: 00000004
ulDrivglobStart: 00000000
ulDrivglobLen: 00000000
usCPUType: 000001C2
usMiscFlags: 00000002
pExtensions: P+0000271C
ulTrackingStart: 00000000
ulTrackingLen: 00000000
84000000 - 84000000 L00000000 End: end of RAM
downloading the 6mb pagepool and gonna try it a bit.
thnx for ur hard work chartreaux
hey man
Thanks!!!!BUT
why my camara doestn't work after the updated
nb: try it at your own risk,.
Okay, here i'll describe how to port XIP and SYS folder to build your fresh new ROM,.
- for a newbie, why do we need to port this? "its necessary to make a new OS and build"
ex: CE OS 5.2.2000 Build 20000.1.0.0
Then lets start working out,.
What do you need?
Atom WM6 Kitchen (see the usage and how to use HERE)
Hypercore Kitchen (see the usage and how to use HERE)
M'reloc (see the usage and how to use HERE)
Already have it all?
continue this step by step then,.
You have to extract the XIP from the source that usually came from OS.nb file (downloaded ROM that have a newer OS and build), here is the step by step,.
nb: The safest way, is to change the coredll.dll only, if you wish to change all of it, its up to you,.
1. Extract XIP.BIN from the source, by using XIP_Extract found in hypercore\tools\convert\XIP_extract,.
Code:
RomMaster.exe OS.nb. -w 5 -b 0x00310000 -x -o xip.bin
---------> There, you'll see a "command program", run it, then write like above,.
2. Run "XIPPort" then select "dump xip.bin", there, you'll have a new folder named "OUT" that contains with 2 folders inside, "FILES" and "MODULES",.
{
"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"
}
---------> What's inside the FILES folder? it is the XIP that needed for building imgfs, to create diskimage_Ver.nb0, and make your device booting,.
---------> What's inside the MODULES folder? it is the module, that your device performance and works, depend on, so becareful okay,.
3. Open M'reloc, choose module coredll.dll inside "MODULES" folder,.
---------> there, you have to change the V and D base, become atom V and D base (For Atom, V=03F4E000 , D=01FFC000)
---------> and, you have to change the V and D base, in the imageinfo.txt (inside the modules folder)
4. Copy coredll.dll and coredll.dll.txt and do the next step,.
Then, its time for you to change your diskimage_Ver.nb0 XIP, here's the step by step,.
1. Extract XIP.BIN from your diskimage_Ver.nb0, by run program "romtoolz" inside the TOOLS folder (Atom WM6 Kitchen),.
---------> Choose the source (diskimage_Ver.nb0),.
---------> Then choose where do you wan the xip.bin to be extracted,.
2. Run XIPPort (you could find it in the same folder), then select "Dump Xip.bin" , you'll see new folder created, named "OUT" that contains with 2 folders inside ("FILES" and "MODULES")
------------------- its just like step number 2 above ----------------
3. Copy the file that have been M'reloced (coredll.dll and coredll.dll.txt) into MODULES folder, then, select "Realloc P" then, select "Write Maps",.
---------> Open MAP Physical.txt, try to find, is there any "!!!!", if you have it, try to check, have you m'reloc the module correctly? and try to select "Realloc P" then "Write Maps" again,.
4. Select "build xip_out.bin" , you will have a new files named "xip.out.bin",.
------------------- Screenshot above (right) ----------------
5. Select "write xip_out.bin to:" then write like this,.
------------------- Screenshot above (right) ----------------
---------> 0018000C ----------> This is the default xip address for XDA ATOM
---------> diskimage_Ver.nb0 --> Means that the xip.out.bin will be written to the file named diskimage_Ver.nb0
nb: All this stuff must be located in one folder (diskimage, xipport, etc) or it wont work,.
----- finally, now you have a new OS ready to update your device ROM,. -----
GOOD LUCK,.
Happy ROM Cooking to all of you,.
- Kumara -
reserved,.
reserved too,.
Garmin said:
---------> 0018000C ----------> This is the default xip address for XDA ATOM
Click to expand...
Click to collapse
It's the same thing for Kaiser ?
Thanks Garmin , another STICKY! ,waiting for you to complete this btw i need the link to build 2000 too , PM me hehe
Many thx for this, looking forward to read the complete version Please upload the necessary apps or link to where to find aswell
regards
yass
MickyMax said:
It's the same thing for Kaiser ?
Click to expand...
Click to collapse
no no no no,.
its not the same,.
try to ask someone expeienced on it, try to ask the addres of OS.nb for kaiser,. is not that actually,.
but, the procedure was just same,.
thanks,.
Garmin said:
no no no no,.
its not the same,.
try to ask someone expeienced on it, try to ask the addres of OS.nb for kaiser,. is not that actually,.
but, the procedure was just same,.
thanks,.
Click to expand...
Click to collapse
Thank you
It's so nice to see this.
May I ask how to deal with in cooking the xip part of Atom XDA LIFE?
Thanks!
Thank you for the nice screenshots
Any one got a link to Jiggs's kitchen ?
Garmin, can you please upload Jigg's Kitchen?
regards
yass
lnks said:
It's so nice to see this.
May I ask how to deal with in cooking the xip part of Atom XDA LIFE?
Thanks!
Click to expand...
Click to collapse
I have posted this in the Atom Wiki: Disassembly of Other Device ROMs
http://wiki.xda-developers.com/index.php?pagename=Other_Device_ROM
BUT, as far as assembly is concerned, you have to ask an Atom Life user because there have been reports that assembly doesn't quite work.
JIGGS KITCHEN???
How many time i have reviewed that jiggs never release a kitchen in a public,.
be patient please,.
i'll upload it,.
thanks,.
ThanX bud , can you come on yahoo?
tjlabais said:
BUT, as far as assembly is concerned, you have to ask an Atom Life user because there have been reports that assembly doesn't quite work.
Click to expand...
Click to collapse
Oh no, it semms to work.
See the attached pictures. Both pictures are from Atom Life. The 1908 is from ferryboat's chinese ROM. The 1978 is the XIP from an other build by ferryboat, cooked in the original WWE build but with 4 MB PP.
scorpio16v said:
Oh no, it semms to work.
See the attached pictures. Both pictures are from Atom Life. The 1908 is from ferryboat's chinese ROM. The 1978 is the XIP from an other build by ferryboat, cooked in the original WWE build but with 4 MB PP.
Click to expand...
Click to collapse
Great job scorpio,.
New map for atom exec
Hi, bro... as we know on both atom/ exec rom we used some module from original wm5. like cecompr.dll
and i have using cecompr.dll from original wm6 hermes to my rom N-Touch. See my new map
Code:
00000000 - 01f901fd L01f901fd NUL
01f901fd - 01f901fd L00000000 Start: first DLL address
01f901fd - 01fd1000 L00040e03 NUL
01fd1000 - 01fd2000 L00001000 initialized data of region_1 ceddk.dll
01fd2000 - 01fe1000 L0000f000 initialized data of region_1 TrueFFS.dll
01fe1000 - 01fe2000 L00001000 initialized data of region_1 cecompr.dll
01fe2000 - 01fef000 L0000d000 initialized data of region_1 stratad_intel_l.dll
01fef000 - 01ff0000 L00001000 initialized data of region_1 regenum.dll
01ff0000 - 01ff1000 L00001000 initialized data of region_1 pm.dll
01ff1000 - 01ff2000 L00001000 initialized data of region_1 mspart.dll
01ff2000 - 01ff3000 L00001000 initialized data of region_1 imgfs.dll
01ff3000 - 01ff4000 L00001000 initialized data of region_1 fsreplxfilt.dll
01ff4000 - 01ff5000 L00001000 initialized data of region_1 fsdmgr.dll
01ff5000 - 01ff6000 L00001000 initialized data of region_1 fatutil.dll
01ff6000 - 01ff7000 L00001000 initialized data of region_1 fatfsd.dll
01ff7000 - 01ff8000 L00001000 initialized data of region_1 encfilt.dll
01ff8000 - 01ff9000 L00001000 initialized data of region_1 diskcache.dll
01ff9000 - 01ffa000 L00001000 initialized data of region_1 devmgr.dll
01ffa000 - 01ffc000 L00002000 initialized data of region_1 crypt32.dll
01ffc000 - 01ffd000 L00001000 initialized data of region_1 coredll.dll
01ffd000 - 01ffe000 L00001000 initialized data of region_1 certmod.dll
01ffe000 - 01fff000 L00001000 initialized data of region_1 cachefilt.dll
01fff000 - 02000000 L00001000 initialized data of region_1 busenum.dll
02000000 - 02000000 L00000000 End: last DLL address
02000000 - 03df2000 L01df2000 NUL
03df2000 - 03df8000 L00006000 Virtual base address of ceddk.dll
03df8000 - 03e44000 L0004c000 Virtual base address of TrueFFS.dll
03e44000 - 03e5a000 L00016000 Virtual base address of stratad_intel_l.dll
03e5a000 - 03e5e000 L00004000 Virtual base address of cecompr.dll
03e5e000 - 03e62000 L00004000 Virtual base address of regenum.dll
03e62000 - 03e71000 L0000f000 Virtual base address of pm.dll
03e71000 - 03e79000 L00008000 Virtual base address of mspart.dll
03e79000 - 03e83000 L0000a000 Virtual base address of imgfs.dll
03e83000 - 03e8d000 L0000a000 Virtual base address of fsreplxfilt.dll
03e8d000 - 03ea2000 L00015000 Virtual base address of fsdmgr.dll
03ea2000 - 03eab000 L00009000 Virtual base address of fatutil.dll
03eab000 - 03ebe000 L00013000 Virtual base address of fatfsd.dll
03ebe000 - 03eca000 L0000c000 Virtual base address of encfilt.dll
03eca000 - 03ed0000 L00006000 Virtual base address of diskcache.dll
03ed0000 - 03edc000 L0000c000 Virtual base address of devmgr.dll
03edc000 - 03f4e000 L00072000 Virtual base address of crypt32.dll
03f4e000 - 03fe4000 L00096000 Virtual base address of coredll.dll
03fe4000 - 03ff0000 L0000c000 Virtual base address of certmod.dll
03ff0000 - 03ffa000 L0000a000 Virtual base address of cachefilt.dll
03ffa000 - 04000000 L00006000 Virtual base address of busenum.dll
04000000 - 80580000 L7c580000 NUL
good point indeed since our ATOM imgfs only use XPR compression and no need to hanle LZX Decompress method, can save 8192 bytes for imgfs modules.
File struct error,
I try to "rommaster.exe os.nb ... from Hermes
but it have an error
[Error] File struct error, xip end offset is 0x7c90ee19, but file length
is 0x043aa800.
Please someone help
Hi,
ATPluginInstaller was a great idea-but we missed some things-and TICS can do it -especially installing a .plg in EACH .cpr!
TICS is short for Titanium Installator Controller Saver
TICS is upward-compatible to ATPluginInstaller in its Doing - but will do much more.
To introduce it, a little example to call TICS_installer, so you can already see, what's now possible:
TICS_installer.exe -addchange -plg:\\Internal Storage\\Sandbox\\default.plg -cpr:currentPortrait -silent
but also possible:
TICS_installer.exe -addchange -plg:\\Internal Storage\\Sandbox\\test.plg -cpr:\\Internal Storage\\Sandbox\\Titanium_480x640.cpr
and:
TICS_installer.exe -delete -plugin:Test -cpr:currentLandscape
Direct Download of TICS_installer - new RC3.1
Now, you have seen the "specials" of TICS - but the first question of te Plugin-Makers will be: "what about the setup.dll?"
And that's very easy: ATPluginInstaller installed or uninstalled only the default.plg in Titanium_<res>.cpr - so it was possible.
TICS has to much options for this - and so you need another interface -but you already have it:
The Setup.dll from Mortscript calls "install.mscr" after installing a cab - and "uninstall.mscr" before uninstalling a cab.
The only MUST is: the Mortscript.exe, TitaniumRefresh.exe and the both mscr-Files and TICS_installer.exe must be installed in your main Directory of your Plugin.
But so we can also be asure, that each Plugin has now its right MortScript-Version - and everybody of us has a simple-to-use interface.
I will post an example for an install.mscr in Post #2
But now the Syntax of TICS-installer(and 4 now it's changeable, after Release no more! It can only be expanded - but each Skinner, Themer, Plugin-Developer,... must rely on, that the Parameters from TICS_installer always be upward-compatible)
Usage:
Install/Change:
TICS_installer.exe -addchange -plg:<absolutePathToPlg> -cpr:currentPortrait|currentLandscape|<absolutePathToCpr> [-silent]
Uninstall:
TICS_installer.exe -delete -plugin:<PluginName> -cpr:currentPortrait|currentLandscape|<absolutePathToCpr> [-silent]
The Example in Post #2 will show the same thing as that was ATPluginInstaller did... almost... because "current" is the ative cpr - e.g. if you are using NeoTitanium - then TICS will install the .plg in NeoTitanium...
For whom it is needful to use TICS in future?
For the Users of course - no more problems to install Skins to whatever he uses in Titanium
For Developers of Plugins: their Plugins can now be used in each Titanium-Theme without adapting of the Theme-Makers - only depends from the ideas of the Skinners. Also they have a new interface after installing/before uninstalling a .cab - and Mortsript-knowledge would be enough
For Titanium-Theme-Makers: Now they can get help from the Skinners and the Plugin-Makers for a specific Plugin and no more for a whole cpr. Also the additional Parameters will help them, too
For Skinners: Much more possibilities to skin now Only by making that, what they can: Making great .plg's and Images!
TICS is free - like ATPluginInstaller - for each non-profit CHome-/Titanium-Plugin - so I'm only interested in enjoying this new possibilities of ech of you, too
Some important explanations:
- TICS_installer will only write in "ExtensibilityXML", "DefaultXML" and "Plugins" to CHome-Registry, if the Parameter for CPR is a "current..."-Parameter
- but then in "HKCU/Software/TICS" - with "newExtensibilityXML","new..."
- TICS uses "ExtensibilityXML" and "CPRFile" from CHome-Registry to identify the current CPR - it's automatically set by Windows-system because of ExtensibilityXML
- and you can use them by simple Registry-Copy in install.mscr or your Program like you need it for your Plugin
- You must set the <Position> in .plg - but if the Plugin already exists, then TICS ignores the Position in .plg - because it assumes, that the User has moved the Plugin to a better place for him (e.g. with CHome-Editor) - so it's more User-friendly
- TICS has definite Error-Messages and Number - which you can capture&handle while Installing a .plg - everything to find in "HKCU/Software/TICS"
- TICS recognizes your current resolution of your device - and only installs in the .cpr of this Resolution - no more in the other unused one
- Code optimization fast&small
- TICS makes a different between portrait and landscape in the .plg - so you have to call TICS twice if you want the same behaviour like ATPluginInstaller- but so you can also handle the different Sizes or can install different .plgs to Landscape and portrait... nice opportunity for Skinners
- it creates two temporary files direct in MainStorage "tempTitaniumLandscapeCpr.txt" and "tempTitaniumPortraitCpr.txt" which are the output files of - also a successful like a buggy call, too - of TICS - so you can handle it without need to copy something from Windows-Directory.
Of course will TICS change the current .cpr, too. And overwrite the temporary Files after next call of TICS
Everything else is already explained with ATPluginInstaller - but don't forget: CESetupDLL = "setup.dll" in TICS! :
http://forum.xda-developers.com/showthread.php?t=509492
Only a summary of the new advantages of TICS:
- fast - written in C with MSDN - nothing else! Needs only 20ms for a complete operation on a .cpr
- You can handle EACH .cpr now The most important of all
- .plg can be everywhere - you can also save the .plg in Internal Storage together with the Images to copy full Skins to your Plugins
- Post-Installation-Hook - you can handle everything which you need for yor Plugin now while installing the cab (install.mscr)
- Pre-Deinstallation-Hook - you can handle everything which you need for yor Plugin now before uninstalling the cab (uninstall.mscr)
- in pre- and post- un/installation you can handle everything also before calling TICS and also after calling TICS
-Detailed Error Messages and Numbers to handle them
- Special support-parameters for JMLToday & TitaniumRSS and some other Plugins
- Silent-Mode - TICS can suppress the Error-Messages and only write them to Registry - and you can handle them on your own
- Change View of Titanium to TitaniumListView or BronzeListView (disabled in Beta)
- Makes differences between portrait and landscape - and so the possibiity to have abolutely different Skins in this directions
- only installs in your Resolution - so it's fast and need less storage in your Windows-Directory
- User-friendly (e.g. Position - see above)
- Let you handle the both last calls of TICS by providing everything about them in Registry.
Download attached
Please: It's a RC: Before you try it - save your .cpr and the Values "ExtensibilityXML" and "Plugins" in Registry of CHome.
First File is Mortscript.exe (4.2-feel free to use,what you want) , TitaniumRefresh.exe, the setup.dll and an example for install.mscr and uninstall.mscr
Second File is TICS_installer.exe itself as zip
-------
last change 3.1:
- "-change" to TitaniumListView bugfix
*FULL CHANGELOG*
-------------
Thanx to Mort for providing the Setup.dll!!!
And AppStar for his great initial concept of ATPluginInstaller!!!
And I'm looking forward to new Themes & Skins, which are now much easier possible
Cheers & Thanxs
Micha
Like my work? For a new device to test, motivation, better developing environment and especially coffee - to spend much more nights, you can donate a cup of coffee for me.
Short Description: HowTo easily change your Plugin from ATPluginInstaller to TICS_installer (for Plugin-Developers) - needs only some minutes :
1. use the attached install.mscr and uninstall.mscr from Post #1 ("SetupDll_and_Mort.zip")
2. In install.mscr only put these Lines:
Code:
instPath = SystemPath( "ScriptPath" )
plgPath=instPath\"test.plg"
callParameter="-addchange -plg:"&plgPath&" -cpr:currentPortrait"
RunWait(instPath\"TICS_installer.exe", callParameter)
callParameter="-addchange -plg:"&plgPath&" -cpr:currentLandscape"
RunWait(instPath\"TICS_installer.exe", callParameter)
RunWait(instPath\"CHomeRefresh.exe","")
If you use another .plg - not default.plg - just change second line to the name of the .plg you want to install with .cab
3. In uninstall.mscr only put these Lines:
Code:
instPath = SystemPath( "ScriptPath" )
RunWait(instPath\"TICS_installer.exe", "-delete -plugin:[I]YourPlugin[/I] -cpr:currentLandscape")
RunWait(instPath\"TICS_installer.exe", "-delete -plugin:[I]YourPlugin[/I] -cpr:currentPortrait")
RunWait(instPath\"CHomeRefresh.exe","")
Only replace "YourPlugin" with the name of yourPlugin - e.g. "CNitrogen"
4. Put this install.mscr, uninstall.mscr, TICS_installer.exe, setup.dll, MortScript.exe (don't forget! use Version, you want) and CHomeRefresh.exe to your Main Directory of your Plugin. Delete "ATPluginInstaller.exe" and "CEsetupDLL.dll"
5. Add the new Files to your .inf-File
6. Change in [DefaultInstall]-Section of your inf the Line to: CESetupDLL = "setup.dll"
7. Cab your Plugin - ready - now your Plugin works with TICS - and therefore for all Themes
Longer Example MortScript:
Here's the Mortscript, what would almost do the same while installing a cab for a Titanium Pluing like ATPluginInstaller,
but with the difference: In the current (=active) CPR - it's also attached as example in Post #1 as download
Code:
### Sample: Installation for TICS - called by setup.dll
instPath = SystemPath( "ScriptPath" )
### Code before call of TICS_Installer ###
# empty
### TICS_Installer call portrait ###
plgPath=instPath\"test.plg"
callParameter="-addchange -plg:"&plgPath&" -cpr:currentPortrait"
message(callParameter)
RunWait(instPath\"TICS_installer.exe", callParameter)
### Handle here returned Error-Code: portrait ###
errorcode=RegRead("HKCU", "Software\TICS","ErrorNumber")
if (errorcode ne "0")
messagetext="Portrait Installation failed: "& RegRead("HKCU", "Software\TICS","ErrorDescription")
message(messagetext)
exit
endif
### TICS_Installer call landscape ###
plgPath=instPath\"test.plg"
callParameter="-addchange -plg:"&plgPath&" -cpr:currentLandscape"
RunWait(instPath\"TICS_installer.exe", callParameter)
### Handle here returned Error-Code: portrait ###
errorcode=RegRead("HKCU", "Software\TICS","ErrorNumber")
if (errorcode ne "0")
messagetext="Landscape Installation failed: "& RegRead("HKCU", "Software\TICS","ErrorDescription")
message(messagetext)
exit
endif
### Code after call of TICS_Installer ###
Sleep(500)
RunWait(instPath\"CHomeRefresh.exe","")
message("finished")
exit
An example for uninstallation (parly) - it will uninstall your Plugin with the Name "Test" - replace it with the Name of your Plugin and it will work
Code:
...
RunWait(instPath\"TICS_installer.exe", "-delete -plugin:Test -cpr:currentLandscape")
RunWait(instPath\"TICS_installer.exe", "-delete -plugin:Test -cpr:currentPortrait")
...
Some other possible calls - e.g. also from C-/C++/-C#-/Whatever-Program:
// LPCWSTR ganzPar= L"-addchange -plg:\\Interner Speicher\\Sandbox\\test.plg -cpr:\\Interner Speicher\\Sandbox\\Titanium_480x640.cpr" ;
// LPCWSTR ganzPar = L"-addchange -plg:\\Interner Speicher\\Sandbox\\test.plg -cpr:currentPortrait";
// LPCWSTR ganzPar = L"-addchange -plg:\\Interner Speicher\\Sandbox\\test.plg -cpr:currentLandscape -isTICSSystemCall";
// LPCWSTR ganzPar = L"-delete -plugin:JMLToday -cpr:\\Interner Speicher\\Sandbox\\Titanium2_480x640.cpr";
// LPCWSTR ganzPar = L"-delete -plugin:Test -cpr:currentPortrait";
// LPCWSTR ganzPar = L"-delete -plugin:Test -cpr:currentLandscape";
// LPCWSTR ganzPar = L"-delete -plugin:Testplugin -cpr:all";
// LPCWSTR ganzPar = L"-delete -plugin:Testplugin -cpr:\\Interner Speicher\\Sandbox\\Titanium_480x640.cpr";
And here the Listings of the Registry-Keys in HKCU/Software/TICS :
callAction: Last kind of Call, e.g. addchange
callCPR: full-qualified path of CPR which should be changed
callOrgDefaultXML/callOrgExtXML/callOrgPlugins: Saves the DefaultXML/ExtensibilityXML/Plugins before Changing
callOverall: All Parameters which were given to TICS_installer
callPLG: full-qualified path of PLG which should be injected
callTypeCPR: direct or current
ErrorDescription: Long description of Error Message
ErrorNumber: Number of the Error
last...: The same as above for the Call before
new...: The changes of TICS in Registry - with "current" also in your Titanium - otherwise only here, so you can copy it after installation e.g. in install.mscr
Nice day 4 U
Micha
Changelogs of former Versions:
changelog ReleaseCandidate 3.1:
- -change to TitaniumListView now works (not necessary to update from RC3.0 if you are a Plugin-Developers, who doesn't use "-change")
changelog ReleaseCandidate 3.0:
- Wrong Upload - therefore RC2.0 no more exists
- Bugfix: in seldom constallations other Plugins disappeared
- Added 2 more understandable Error Messages
changelog ReleaseCandidate 1.0
- added "ForbiddenList"
- added check of ExtensibilityXML to get the correct cpr-Name
- added possibility to change a cpr to TitaniumListView / BronzeListview
- increased speed - reduced filesize
Changelog Beta2:
- Made a Fix to Compiler-Options - in the optimization it made something wrong sometimes in .exe
- Some Bugfixes because of Feedback (now it's stable with changing the Windows-CPR)
- Implemented this to JMLToday-cab and tested it: All works - and if this works, so we can be very sure, that it works for all Plugins instead of ATPluginInstaller
- added Parameters:
-- The Version-Number of TICS will alway be transmitted to Registry HKCU/Software/TICS:Version
-- "-nochangechomereg" : Independent from -current..., TICS_installer won't change the Registry of CHome - only create the key in HKCU/Software/CHome, which you can copy or use afterwards.
-- "-nochangecpr" : Independent from -current..., TICS won't write back the cpr-File to the original and will only provide the temp-File, which you can use by your install-script
-- "-isTICSSystemCall": This will be a reserved Parameter for the whole TICS-System - and you can never rely on,what it does-so never use it - it's only for "C" and "S" of TICS - and can change its behaviour
- Some small optimizations in code
- Tested it very hard
-------
OK - I must go now for today - thanx for Feedback, how we can alltogether get it appropriate for each special wishes of the Themers, Skinners and Plugin-Developers.
Have Fun with TICS-Checking
Micha
Nice, now if someone wants a specific plugin for say my NeoTitanium or the Windows 7 Titanium or any other Titanium skin that uses custom named CPR's, the developer can make the layout or any skinner can make their own. Will make my job a lot easier, Thank you!!!
Enjoy your coffee, it's well earned.
Unique Transaction ID #4HH62607UX4580321
You have really outdone yourself Micha, that is great.
I am no skinner and also cannot program, but i will dig into this to understand it fully as it very interesting and opens a lot of possibilities.
Thank you! I'm looking forward to everything what the Skinners will do with your NeoTitanium
Thanx, too, Claus! You had so much effort increating and providing your cpr's for all resolutions and themes - I hope it's now much easier for you.
And hey - there's no need to programming - only using the Parameters
I hope some Plugins will test soon the changing of the files (setup.dll, TICS_installer.exe) - and the most of them can overtake almost blind (only changing the PluginName) the install.mscr and uninstall.mscr of the download (and shown in Post #2) - it would almost do the same as PluginInstaller before - but now for each Titanium-Theme - and I think that's interesting for all Plugin-Developers.
I will insert it also in JMLToday andsend it to JMHL afterwards - but there will be much more needed than only the Installation-Part.
The same later on with TitaniumRSS (because TitaniumRSS has already since the first Release TICS inside for changing to FullView and some more things- so I learned, what's important).
I want to explain some additional Parameters here - only to discuss, if they would be necessary for you:
- The Version-Number of TICS will alway be transmitted to Registry - better then a "-version"-Parameter - ok?
- There will be a "-change" - Parameter - e.g. then with "-cprchange:titaniumlistview|bronzelistview" - I don't think I have to explain, what it means
- Perhaps some Parameters there in "-change" which changes the Action-Areas and some more (proposals... we will see)
- "-nochangechomereg" : Independent from -current..., TICS_installer won't change the Registry of CHome - only create he key in HKCU/Software/CHome, which you can copy or use afterwards.
- "-nochangecpr" : Independent from -current..., TICS won't write back the cpr-File to the original and will only provide the temp-File, which you can use by your install-script
- "-isTICSSystemCall": This will be a reserved Parameter for the whole TICS-System - and you can never rely on,what it does-so never use it - it's only for "C" and "S" of TICS - and can change its behaviour
I didn't write this proposals of the Parameters to Post #1 (some of them are already implemented, but disabled in Beta) - not toconfuse to much - they would be seldom used - and the most important for Plugin-Developers,Skinners, Theme-Makers,... are in Post #1
But nevertheless: If you want something special of functionality for your Theme oder your Plugin or to help for skinning .plg's - it's the best now before Iwill open the Release-Thread of TICS.
Later on - I will add each Betas here - and the Releases with the official implemented and upward-compatible functionalities in the Release-Thread of the whole TICS-Suite.
Especially from Theme-Makers and Plugin-Developers: I hope you have a look at the Parameters of Post #1 - and can tell me, what you would like to have for your Plugin.
Cheers
Micha
Ok - thanx for the Feedbacks (better here in Thread as via PN - so I would see it much faster)
I have changed the things - and deleted Beta1 from Download and added Beta2 in Post #2
I have tested it hard - and I already integrated it in JMLToday.cab to see, if everything will work (JMLToday is very complex in installing and using .plg) - and it's stable with TICS Beta2 - so you can test it also with your Plugins.
Also I had to optimize the code a little bit and added some of the Parameters, I mentioned.
I only want to run it with some further informations - therefore the .exe is a little bit bigger now. But no bad effect on the speed.
I also have put each "Beta"-Status out of the Beta - no limitations and also no more messages and Silent-Mode is activated, if set.
The Message - if activated - are now also shown in Foreground
Works really stable to integrate it.
So - Beta2 is also Release Candidate 1
Please Feedback for wishes,...
Cheers
Micha
It would be nice to have a replacement for CHomeRefresh
After each CHomeRefresh, some keys I deleted from the registry get restored, amongst other things.
We could perhaps call it via:
TICS_Installer.exe -refresh
You now already have a replacement, adwin - because it's only called from the mortscripts
I did it on purpose So everybody can choose if he wants to handle the Return-Values before or make a Refresh.
So - TICS.exe will NEVER call a Refresh by itself - you can rely on
So you can use RedrawToday from Mortscript or RefreshToday.exe or nothing (or something else - there are some more programs). What's better for you (Therefore also the additional parameters, which only write to shadows)
Don't forget - now you have an Interface while installing/uninstalling the cab. So I had no reason to integrate the Refresh into the TICS-exe.
And because of the Restored Keys after Refresh - Beta2 also sets DefaultXML now - just uploaded some minutes before to Post #1
OK so?
Micha
mind realeasing the jmltoday version with this
n if possible have it take the red f the main clock in the bliss theme
Yes - but please: TICS is for all Plugins and Themes - and so please ask in the Plugins and Themes you use, if the could integrate TICS, so that everybody can enjoy each Plugin in each Theme.
I can only provide the Files - and it's simple to swap ATPluginInstaller.exe with TICS_installer.exe and also the cesetupdll.dll with setup.dll and add the 2 Scripts and only make a few simple modifications to them (which .plg - I set in Scripts still default.plg as example).
So each Plugin would automatically work with each themes - without anything more to do.
The Tests are fine - and ok - JMLToday - I'm involved and already made the new cab with TICS - but that must also be published according with JMHL. (and you were not the first who asked for JMLToday with TICS - I won't forget it, sure )
But it works for all Plugins & Themes - so please ask them also direct in their Thread.
OK?
Greetings
Micha
@Micha : You can publish your version of JMLToday5.4 with TICS (no problem).
I have lot of work (business-work, plugins in progress....) and i have not time to make all...
A++
OK - I've uploaded it meanwhile, until you have more Time:
JMLToday 5.4 installed by TICS as cab - Download-Post :
http://forum.xda-developers.com/showthread.php?p=4629986#post4629986
Then everybody can begin with making Skins for all the other Themes, like Bliss, NeoTitanium,...
Greetz
Micha
ok,thanx for the messages.I would only now need a feedback from somebody with QVGA or WQVGA-device. indifferent if you only inserts a single .plg or tried the link above from jmltoday.
But it's really an app for Developers,Theme-Makers to check it.
Like wished, I will add the "ForbiddenList" ((I will explain it) and then I will release TICS_installer as first app from the TICS-Suite.
Works fine so far
Micha
Thanx for the Feedbacks (I still don't understand, why you don't make it here in Thread...)
I added the wishes - I didn't changed the main features - so description is still the same to replace ATPluginInstaller with TICS_Installer - here are the adds of the First Release Candidate:
- added "ForbiddenList"
If you have a special .cpr - and you want to prevent it temporary from changes by Plugin-Installations - you only have to add the name of the cpr to /HKCU/Software/TICS -> "ForbiddenList" - enclosed with semicolons,
e.g. ForbiddenList=";TitaniumRSS;;Specialcpr;"
Then TICS would also if "currentPortrait" or "currentLandscape" is set for cpr - only make the temporary Files for this cpr and also the temporary Registry-Entries - but wouldn't change the Titanium system.
- added check of ExtensibilityXML to get the correct cpr-Name
TICS uses normally "CPRFile" in CHome to identify the current cpr - but now it also looks into ExtensibilityXML - and if there is another cpr-Name - then TICS uses this CPR-Name and also sets "CPRFile" this name (it's really better for TitaniumSystem- that both settings are switched, also if you think, that ExtensibilityXML would be enough)
- added possibility to change a cpr to TitaniumListView / BronzeListview
with
Code:
TICS_installer.exe -change -view:TitaniumListView -cpr:currentPortrait
the current protrait cpr would be change to TitaniumListView - so that e.g. JMLPanex would also work with Titanium7Project.
With:
Code:
TICS_installer.exe -change -view:BronzeListView -cpr:currentPortrait
it would be switched back
- increased speed - reduced filesize
you will see it .exe is now 35kb - and also for big cpr-Files very fast.
I don't want to add new functionalities for 1.0 now - but this Beta-Thread will remain also after Release - to add this things to next versions.
But the main-calls to -addchange and -delete, which are in 1.0 - will remain forever in each next update - so only expansions ae possible after Release.
So you can be sure, tht all Plugins, which are installed by TICS - remain upward-compatible for the future.
Please tell me, if you'd see any bug in RC1 - but it was good tested and has almost no differences to Beta2 in the MainStream (but faster &smaller) - so it's not necessary to wait too long until RC1 will be 1st Release.
Please report anything, what you see in trial.
Thanx & have fun with making your Plugins installable for all Titanium-Themes
Micha
BTW: If you need a further example how to use TICS RC1 - it's used inside this .cab :
http://forum.xda-developers.com/showpost.php?p=4683099&postcount=298
and still runs fine - otherwise just write it here (no more by PN please )
Micha
Thanx for the hint, Tb1502!
I wrote in Post #1 that:
CESetup.DLL = "setup.dll" should be the .inf-Entry for a Plugin, but it should be of course without the . :
CESetupDLL = "setup.dll"
in .inf to use the new setup.dll
Thanx again & Sorry
Micha
OK - after Feedback: RC1 is also first Release - all works fine.
I won't make a new Thread at the moment for the Release - think I will make this Thread after I have the most implemented "C" and "S" of TICS for the users.
I have added a short description to Post #2, how to change your Plugin from ATPluginInstaller to TICS_Installer. A few simple steps - takes only some minutes:
1. use the attached install.mscr and uninstall.mscr from Post #1 ("SetupDll_and_Mort.zip")
2. In install.mscr only put these Lines:
Code:
instPath = SystemPath( "ScriptPath" )
plgPath=instPath\"test.plg"
callParameter="-addchange -plg:"&plgPath&" -cpr:currentPortrait"
RunWait(instPath\"TICS_installer.exe", callParameter)
callParameter="-addchange -plg:"&plgPath&" -cpr:currentLandscape"
RunWait(instPath\"TICS_installer.exe", callParameter)
RunWait(instPath\"CHomeRefresh.exe","")
If you use another .plg - not default.plg - just change second line to the name of the .plg you want to install with .cab
3. In uninstall.mscr only put these Lines:
Code:
instPath = SystemPath( "ScriptPath" )
RunWait(instPath\"TICS_installer.exe", "-delete -plugin:[I]YourPlugin[/I] -cpr:currentLandscape")
RunWait(instPath\"TICS_installer.exe", "-delete -plugin:[I]YourPlugin[/I] -cpr:currentPortrait")
RunWait(instPath\"CHomeRefresh.exe","")
Only replace "YourPlugin" with the name of yourPlugin - e.g. "CNitrogen"
4. Put this install.mscr, uninstall.mscr, TICS_installer.exe, setup.dll, MortScript.exe (don't forget! use Version, you want) and CHomeRefresh.exe to your Main Directory of your Plugin. Delete "ATPluginInstaller.exe" and "CEsetupDLL.dll"
5. Add the new Files to your .inf-File
6. Change in [DefaultInstall]-Section of your inf the Line to: CESetupDLL = "setup.dll"
7. Cab your Plugin - ready - now your Plugin works with TICS - and therefore for all Themes
OK - the Tests were all ok - some Plugins use it meandwhile - and hey.. you are using Beta2 - But RC1 is the new one!
It's running faster and is smaller - I think I will make sooner a Release Thread,than I wanted
But in Release - it will be the same as RC1 - so please use this (Just compare the changelog - the main functions are the same, but there's some differences between older Beta2 and RC1 - for special use - if you need it)
And Beta2 is good tested, but RC1 is better tested, because it's already running in some Pugins
Greetings
Micha
What is MTYPE for GSmart S1205 .
(I need becouse i`m trying install Android, if anybody can give me some tips please reply it too)
Based on htt p:/ /ww w.arm.linux.org.uk/developer/machines/ the GSmart S1205 processor mach type is 2754 (the phone has a Mediatek MT6516 / 416MHz processor).
MTYPE = Mach Type = 2754 Meditek 65XX Series mt65xx Howard Chen
But it still hangs.
Code:
[B]This is my Haret default.txt:[/B]
# Display some greeting message
print "Welcome to Handheld Reverse Engineering Tool!"
print "Some basic info about your PDA:"
print "Processor Mach Type is %d" MTYPE
print "MMU L1 descriptor table address is %08x" MMU
# MMU L1 descriptor table address is 02650000
print "Video RAM address is %08x" VRAM
# Video RAM address is 0174b000
print "Current Process ID is %d" PID
# Current Process ID is 16
#print "CPU identification register (p15 r0) is %08x" CP(15,0)
# CPU identification register (p15 r0) is 00000075
# Fill top ten scan lines (the run bar) with some color
#vfh VRAM 240*10 0x0099
# EXCEPTION while writing 00000099 to address 0174B000
set RAMADDR 0xa0000000
set MTYPE 2754
set KERNEL zImage
set initrd initrd.gz
#
# The following kernel parameters are useful
# ppp.nostart - Set ppp.nostart=1 to disable starting the ppp connection on boot
# msm_sdcc.msmsdcc_fmax - The maximum frequency (in Hz) used by the SD controller
# pm.sleep_mode - The mode used when the phone is off
# 0=Power Collapse Suspend, 1=Power Collapse, 2=Apps Sleep,
# 3=Slow Clock and Wait for Interrupt 4=Wait for Interrupt
# Default is 3, use 0 for best power savings
# board-htcvogue.panel_type - Panel type used to power the panel off and on
# 1=Hitachi 2=Topoly 3=Samsung
# clock-7x00.mddi - MDDI clock (try 0xa51 or 0xe2c)
# clock-7x00.ahb_div - Advanced Host Bus divider, default is 4
# 2 is faster but uses more power
# clock-7x00.a11 - ARM11 clock speed in MHz, best to leave this alone
# lcd.density - Defaults to 160, 128 shows more on screen
# vogue-ts.XMIN - xmin value for the touchscreen calibration. Also YMIN, XMAX, YMAX, PMIN, PMAX.
#
# Probably the only one of these you will need to change is the panel type, NZ Vogues seem to all have type 1
# US Sprint vogues usually have type 2 or 3 I think.
# Make sure you add these between the quotes on the following line and that your editor hasn't split the line up.
set cmdline "ppp.nostart=0 mddi.width=240 mddi.height=400 pm.sleep_mode=0 no_console_suspend"
boot
This is my Haret log:
Code:
Running WSAStartup
Starting gui
In initdialog
Found machine Generic ARM 926
executing startup.txt
HaRET(2)# print "Welcome to Handheld Reverse Engineering Tool!"
Welcome to Handheld Reverse Engineering Tool!
HaRET(3)# print "Some basic info about your PDA:"
Some basic info about your PDA:
HaRET(4)# print "MMU L1 descriptor table address is %08x" MMU
MMU L1 descriptor table address is 02650000
HaRET(5)# print "Video RAM address is %08x" VRAM
Video RAM address is 0174b000
HaRET(6)# print "Current Process ID is %d" PID
Current Process ID is 16
HaRET(11)# set RAMADDR 0xa0000000
HaRET(12)# set MTYPE 2754
HaRET(13)# set KERNEL zImage
HaRET(14)# set initrd initrd.gz
HaRET(35)# set cmdline "ppp.nostart=0 mddi.width=240 mddi.height=400 pm.sleep_mode=0 no_console_suspend"
HaRET(36)# boot
boot KERNEL=zImage INITRD=initrd.gz
Opening file zImage
Opening file initrd.gz
boot params: RAMADDR=a0000000 RAMSIZE=06000000 MTYPE=2754 CMDLINE='ppp.nostart=0 mddi.width=240 mddi.height=400 pm.sleep_mode=0 no_console_suspend'
Boot FB feedback: 1
Built virtual to physical page mapping
Allocated 663 pages (tags=54000000/053ce000 kernel=54001000/053cd000 initrd=54168000/05630000 index=54293000/0575b000)
Built kernel tags area
Built page index
Video buffer at 4C600000 sx=240 sy=400 mx=60 my=66
Video Phys FB=0174b000 Fonts=0575d064
[email protected]/0575e000 sj=54296000 stack=54294000/0575c000 data=54295000/0575d000 exec=0575e128
Reading 1469884 bytes...
Read complete
Reading 1222150 bytes...
Read complete
Launching to physical address 0575e010
Trampoline setup ([email protected]/200255f4/034465f4)
MMU setup: mmu=A6650000/02650000
Go Go Go...
You using Gsmart S1205?
I used your default.txt and nothing happens . its wirting "Booting Linux" and when bar is filled it just "freezed" . So i need to Soft Reset phone
Like i said "But it still hangs.", mine isn't working too. I think i need to recompile e newer kernel to the zImage.
For Gigabyte GSmart S1205 we need to compile the android-2.6.36 version, because in arch/arm/tools/mach-types file the MT65xx with the MTYPE 2754 is only there, i will try to compile it this week, hope that will work.
And not only a newer kernel is necessary, but a new HaRET compiled from source that will recognise the machine (trying to make one now).
This is not yet implemented, help needing information about MT6516 processor (GPIO table, ecc.). I will work on it.
Here i founded info
pdadb*.*net/index*.*php?m=cpu&id=a6516&c=mediatek_mt6516
remove * and paste in URL bar
Thanks, found that page a while ago, too. But would be nice to find the MT6156 processors datasheet.
For now i managed to make a patch for Haret to recognize the machine, but still it freezes:
========================================================================
Code:
diff -Naur haret/include/arch-arm.h haret-new/include/arch-arm.h
--- haret/include/arch-arm.h 2010-11-23 18:23:03.000000000 +0200
+++ haret-new/include/arch-arm.h 2011-03-02 12:05:02.936418632 +0200
@@ -37,4 +37,7 @@
int detect();
};
+// Aliases
+class MachineMT6516 : public Machine926 {
+};
#endif // arch-arm.h
diff -Naur haret/Makefile haret-new/Makefile
--- haret/Makefile 2010-11-23 18:23:03.000000000 +0200
+++ haret-new/Makefile 2011-03-02 12:38:27.628418500 +0200
@@ -45,7 +45,7 @@
RC = $(BASE)/bin/arm-mingw32ce-windres
RCFLAGS = -r -l 0x409 -Iinclude
-CXX = $(BASE)/bin/arm-mingw32ce-g++
+CXX = $(BASE)/bin/arm-mingw32ce-gcc
STRIP = $(BASE)/bin/arm-mingw32ce-strip
DLLTOOL = $(BASE)/bin/arm-mingw32ce-dlltool
diff -Naur haret/src/l1trace.cpp haret-new/src/l1trace.cpp
--- haret/src/l1trace.cpp 2010-11-23 18:23:03.000000000 +0200
+++ haret-new/src/l1trace.cpp 2011-03-02 12:06:09.529418186 +0200
@@ -212,12 +212,12 @@
if (Bbit(insn)) {
addrsize = 1;
asm("swpb %0, %1, [%2]"
- : "=r" (readval)
+ : "=&r" (readval)
: "r" (writeval), "r" (newaddr));
} else {
addrsize = 4;
asm("swp %0, %1, [%2]"
- : "=r" (readval)
+ : "=&r" (readval)
: "r" (writeval), "r" (newaddr));
}
setReg(regs, mask_Rd(insn), readval);
diff -Naur haret/src/mach/arch-arm.cpp haret-new/src/mach/arch-arm.cpp
--- haret/src/mach/arch-arm.cpp 2010-11-23 18:23:03.000000000 +0200
+++ haret-new/src/mach/arch-arm.cpp 2011-03-02 11:59:31.285419224 +0200
@@ -35,6 +35,10 @@
{
name = "Generic ARM 926";
flushCache = cpuFlushCache_arm926;
+ arm6mmu = 0;
+ archname = "MT65XX";
+ CPUInfo[0] = L"MT6516";
+ //customStartFunc = ????;
}
int
diff -Naur haret/src/mach/arch-s3.cpp haret-new/src/mach/arch-s3.cpp
--- haret/src/mach/arch-s3.cpp 2010-11-23 18:23:03.000000000 +0200
+++ haret-new/src/mach/arch-s3.cpp 2011-03-02 12:18:06.349418721 +0200
@@ -307,7 +307,7 @@
if (SDMA_SEL) {
sdma_sel = SDMA_SEL[0];
fb_printf(fbi,"%s: SDMA_SEL=%x", __func__, sdma_sel);
- if (sdma_sel == 0xcfffffff)
+ if ((uint32)sdma_sel == 0xcfffffff)
//SDMA disabled
ctrl_count = 2;
diff -Naur haret/src/mach/machlist.txt haret-new/src/mach/machlist.txt
--- haret/src/mach/machlist.txt 2010-11-23 18:23:03.000000000 +0200
+++ haret-new/src/mach/machlist.txt 2011-03-02 12:32:53.729419070 +0200
@@ -108,6 +108,7 @@
DX900, S3c6400 ,DX900V040, DX900
X900, S3c6400 ,V900V050, ACER_ETEN_X900
M900, S3c6410 ,M900V030;GT-I8000, ACER_TEMPO_M900
+Cougar, MT6516 ,GIGABYTE gSmart, MT65XX
PLATFORM=Jupiter
Jornada820, SA ,"HP, Jornada 820", JORNADA820
diff -Naur haret/src/memcmds.cpp haret-new/src/memcmds.cpp
--- haret/src/memcmds.cpp 2010-11-23 18:23:03.000000000 +0200
+++ haret-new/src/memcmds.cpp 2011-03-02 12:39:37.785419504 +0200
@@ -241,11 +241,11 @@
TRY_EXCEPTION_HANDLER {
if (bitval)
{
- *(uint32*)vaddr |= (1 << bitnr - 1);
+ *(uint32*)vaddr |= ((1 << bitnr) - 1);
}
else
{
- *(uint32*)vaddr &= ~(1 << bitnr - 1);
+ *(uint32*)vaddr &= ~((1 << bitnr) - 1);
}
} CATCH_EXCEPTION_HANDLER {
Output(C_ERROR "EXCEPTION while writing bit %d at address %p",
diff -Naur haret/tools/buildmachs.py haret-new/tools/buildmachs.py
--- haret/tools/buildmachs.py 2010-11-23 18:23:03.000000000 +0200
+++ haret-new/tools/buildmachs.py 2011-03-02 12:04:38.641418478 +0200
@@ -58,6 +58,7 @@
#include "arch-imx.h"
#include "arch-sa.h"
#include "arch-msm.h"
+#include "arch-arm.h"
#include "mach-types.h"
#include "script.h" // runMemScript
========================================================================
And here is the Haret log:
Code:
===== HaRET pre-0.5.3-20110302_124009 =====
Setting KMode to true.
Old KMode was 0
Finished initializing output
Loading dynamically bound functions
Function 'AllocPhysMem' in library 'coredll' at 0x3f62364
Function 'FreePhysMem' in library 'coredll' at 0x3f623d0
Function '[email protected]@[email protected]@[email protected]' in library 'gx' at 0x2023a38
Function '[email protected]@YAHXZ' in library 'gx' at 0x2023e78
Function '[email protected]@YAPAXXZ' in library 'gx' at 0x20232f4
Function '[email protected]@YAHXZ' in library 'gx' at 0x20233b8
Function 'LoadLibraryExW' in library 'coredll' at 0x3f6250c
Function 'NLedSetDevice' in library 'coredll' at 0x3f89b2c
Function 'GetSystemPowerStatusEx2' in library 'coredll' at 0x3f68e90
Function 'SleepTillTick' in library 'coredll' at 0x3f6242c
Function 'CreateToolhelp32Snapshot' in library 'toolhelp' at 0x262605c
Function 'CloseToolhelp32Snapshot' in library 'toolhelp' at 0x262607c
Function 'Process32First' in library 'toolhelp' at 0x2626148
Function 'Process32Next' in library 'toolhelp' at 0x26261b4
Function 'Module32First' in library 'toolhelp' at 0x2626348
Function 'Module32Next' in library 'toolhelp' at 0x26263b8
Function 'Heap32ListFirst' in library 'toolhelp' at 0x2626454
Function 'Heap32ListNext' in library 'toolhelp' at 0x26264dc
Function 'Heap32First' in library 'toolhelp' at 0x2626574
Function 'Heap32Next' in library 'toolhelp' at 0x2626628
Unable to load library 'ace_ddi'
Unable to load library 'ace_ddi'
Unable to load library 'ace_ddi'
Unable to load library 'ace_ddi'
Unable to load library 'ace_ddi'
Unable to load library 'ace_ddi'
Unable to load library 'ace_ddi'
Unable to load library 'ace_ddi'
Unable to load library 'clkregim'
Detecting current machine
Trying to detect machine (Plat='PocketPC' OEM='GIGABYTE gSmart')
Wince reports processor: core=MediaTek name=MT6516 cat= vend=MediaTek Inc
Looking at machine Alpine
Looking at machine Apache
Looking at machine AximX50
Looking at machine AximX5
Looking at machine Beetles
Looking at machine Blueangel
Looking at machine Himalaya
Looking at machine Magician
Looking at machine Universal
Looking at machine H1910
Looking at machine H1940
Looking at machine RX1950
Looking at machine H2200
Looking at machine H3600b
Looking at machine H3700
Looking at machine H3800
Looking at machine H3900
Looking at machine H4000
Looking at machine H4300
Looking at machine H5000
Looking at machine H6340
Looking at machine HX2000
Looking at machine HX4700
Looking at machine Sable
Looking at machine Wizard
Looking at machine Hermes
Looking at machine Trinity
Looking at machine Athena
Looking at machine G500
Looking at machine Artemis
Looking at machine Herald
Looking at machine Prophet
Looking at machine RX3000
Looking at machine Treo700wx
Looking at machine Treo850w
Looking at machine Treo850e
Looking at machine e310
Looking at machine e740
Looking at machine Acer_n30
Looking at machine Mio_P550
Looking at machine Kaiser
Looking at machine Loox5xx
Looking at machine Loox400
Looking at machine MioA701
Looking at machine Wallaby
Looking at machine Raphael
Looking at machine SGH_i900
Looking at machine Leo
Looking at machine Topaz
Looking at machine Rhodium
Looking at machine Jornada9xx0
Looking at machine Acer_S200
Looking at machine M800
Looking at machine X800
Looking at machine DX900
Looking at machine X900
Looking at machine M900
Looking at machine Cougar
Detecting ram size
WinCE reports memory size 100663296 (phys=77144064 store=130306048)
Mapping mmu table
Build L1 reverse map
Found 397 uncached and 397 cached L1 mappings (ignored 1).
Not registering command IGPIO
Not registering command WG|PIO
Not registering command GPLR
Not registering command GPDR
Not registering command GAFR
Not registering command GPIO
Not registering command GPIOST
Registering command LOADLIBRARYEX
Registering command NLEDSET
Not registering command TRACE
Not registering command TRACEMASK
Not registering command TRACE2
Not registering command TRACETYPE
Not registering command TRACE2TYPE
Not registering command TRACEFORWATCH
Not registering command INSN
Not registering command INSNREENABLE
Not registering command INSNREG1
Not registering command INSNREG2
Not registering command INSN2
Not registering command INSN2REENABLE
Not registering command INSN2REG1
Not registering command INSN2REG2
Registering command KILL
Registering command PS
Registering command LSMOD
Registering command ADDR2MOD
Not registering command AC97
Not registering command ATIDBG
Not registering command EIM
Not registering command GPIO
Not registering command WB|ANK
Not registering command GPLR
Not registering command GPDR
Not registering command GPPUD
Not registering command GPSDR
Not registering command GPSPUD
Not registering command GPIOS
Not registering command GPIOSOUT
Not registering command GPIOST
Not registering command MSMCLKKHZ
Initializing for machine 'Cougar'
HaRET(1)# Welcome, this is HaRET pre-0.5.3-20110302_124009 running on WindowsCE v5.2
Minimal virtual address: 0x10000, maximal virtual address: 0x7fffffff
Detected machine Cougar/MT65XX (Plat='PocketPC' OEM='GIGABYTE gSmart')
CPU is ARM ARM arch 5TEJ stepping 5 running in system mode
Enter 'HELP' for a short command summary.
Running WSAStartup
Starting gui
In initdialog
Found machine Cougar
executing startup.txt
HaRET(1)# set RAMSIZE 0x08000000
HaRET(2)# set RAMADDR 0x08000000
HaRET(3)# set MTYPE 2754
HaRET(4)# set FBDURINGBOOT 0
HaRET(5)# set KERNEL zImage
HaRET(6)# set INITRD initrd.gz
HaRET(7)# set CMDLINE "debug rootdelay=10 root=/dev/ram0 console=tty0 mem=128M ppp.nostart=0 lcd.density=120 pm.sleep_mode=0 no_console_suspend"
HaRET(10)# print "Some basic info about your PDA:"
Some basic info about your PDA:
HaRET(11)# print "Processor Mach Type is %d" MTYPE
Processor Mach Type is 2754
HaRET(12)# print "MMU L1 descriptor table address is %08x" MMU
MMU L1 descriptor table address is 02650000
HaRET(13)# print "Video RAM address is %08x" VRAM
Video RAM address is 0174b000
HaRET(14)# print "Current Process ID is %d" PID
Current Process ID is 22
HaRET(18)# boot
boot KERNEL=zImage INITRD=initrd.gz
Opening file zImage
Opening file initrd.gz
boot params: RAMADDR=08000000 RAMSIZE=08000000 MTYPE=2754 CMDLINE='debug rootdelay=10 root=/dev/ram0 console=tty0 mem=128M ppp.nostart=0 lcd.density=120 pm.sleep_mode=0 no_console_suspend'
Boot FB feedback: 0
Built virtual to physical page mapping
Allocated 1109 pages (tags=0x54500000/0567d000 kernel=0x54501000/0567c000 initrd=0x54825000/05963000 index=0x54950000/05a8e000)
Built kernel tags area
Built page index
Tags will be at offset 0x00000100 (0xf00)
Kernel will be at offset 0x00008000 (0x323a48)
Initrd will be at offset 0x00508000 (0x12a606)
[email protected]/05a92000 sj=0x54954278 stack=0x54952000/05a90000 data=0x54953000/05a91000 exec=05a923b8
Reading 3291720 bytes...
Read complete
Reading 1222150 bytes...
Read complete
Launching to physical address 05a92288
Trampoline setup ([email protected]/2c02b994/02ccc994)
MMU setup: mmu=0xa6650000/02650000
Go Go Go...
So your Gsmart S1205 working propertly?
MrXLR8 said:
So your Gsmart S1205 working propertly?
Click to expand...
Click to collapse
Like I said "but still it freezes" . When it will work I will write it in bold, i put data here for other people to see and maybe help me in getting the needed data to build Haret for GSmart S1205 / MT6516/MTK6516 processor, the last Android Kernel (or at least the last Linux Kernel has drivers for this processor), but I need GPIO table and specific IRQs.
so? got anything working? its like month ago
), no, because the android kernel source code for the MT6516 processor is only in China, and I haven't found anyone that would share it (they don't care about license of the kernel), only found compiled kernel, i'm trying to create a source code from the processor's datasheet (more than 1500 pages) and from assembler code found in the compiled kernel. So, will take a long long time. Maybe it doesn't worth to run Android on this type of processor, who knows....
I managed to extract the make config of the kernel compilation and initramfs.cpio
can i help you with something , or can you leave your email or skype?
s1205 Android
Hello. I, too, on the s1205 was unable to run. If you can please let know about your successes. Thanks in advance.
I don't suppose you could point me in the direction of a copy of the datasheet? I'm trying to make some changes on a different MT6516-based device, and I reckon a look at that datasheet could help somewhat. But the only copies I've found are on chinese forums that require some kind of virtual currency to download...
jh3141 said:
I don't suppose you could point me in the direction of a copy of the datasheet? I'm trying to make some changes on a different MT6516-based device, and I reckon a look at that datasheet could help somewhat. But the only copies I've found are on chinese forums that require some kind of virtual currency to download...
Click to expand...
Click to collapse
If you need just datasheet, I've found some docs. Can send you if you need.
how about rom extraction
hi guys, how about figuring out how to extract the flash.bin for gsmart s1205? anyone?
http://forum.xda-developers.com/showthread.php?t=708746
i don't know if this can help you, but i found a PDA with MT6516 processor, and it has android, the link to the firmware/driver ht*tp://ww*w.vkam*obi.com/a5000_refresh.rar (remowe the *)
neocska said:
i don't know if this can help you, but i found a PDA with MT6516 processor, and it has android, the link to the firmware/driver ht*tp://ww*w.vkam*obi.com/a5000_refresh.rar (remowe the *)
Click to expand...
Click to collapse
Hello. I, too have s1205 but not unable to run. If you can please let know about your successes. Thanks in advance.
Rom extraction - only from spec cable:
1. Pinout special contacts under accu:
From left to right: 1- Gnd, 2- Tx, 3-Rx, next symmetric 4 - Rx, 5 - Tx, 6 - Gnd
{
"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"
}
Connect s1205 with Serial->USB to comp.
2. Flasher:
h..p://4pda.ru/forum/dl/post/1011438/SP_Flash_Tool_v1.1110.00_new_mcp.7z
3. run flasher
2. go to tab "Read back"
3. remove all task button "remove"
4. press button "Add"
5. 2 Click on stroke - select where save dump, press "save", in textbox "Length" - write 0х10000000
6. On tab "baudrate" select speed (std 115200 b/s, can 460?)
7. See in comp manag number of com port of cable and write this number in number port in flasher.
8. Press "Read back" and get rom(1) file without ext.
Do not start memory test in flasher!!! it's destroy you s1205.