Related
Hi
Am newbie to the whole XDA thing (am just converting from BB), have managed to unlock my XDA Mini S and tried running K-JAM_WWE_216901_2169101_020721_ship.exe as i heard this would reflash the ROM to the latest (a friend of mine gave me this copy).
Got an error during this, and wondered if there was a specific XDA Mini S version (have searched on the site and it appears that there is on ftp://ftp.xda-developers.com/Wizard) and there are many different ROMS under the ROM directory, but i am unable to login to this site.
Am i just being thick here.
Any help gretaly appreciated.
That ROM upgrade worked ok on my xda-mini-s
When I upgraded my ROM I done the following.....
#unlock phone
with no SIM card in phone
copy EnableRapi.cab to phone
run EnableRapi.cab from phone
run lokiwiz.bat from PC
select option 'U' Unlock SIM
phone reboots
add SIM to backout bin file names on PC
run lokiwiz.bat from PC
select option 'C' unlock CID
phone reboots
add CID to backout bin file names on PC
#install new ROM
uncomress ROM file from zip
click ROM install file
follow instruction
takes 10 minutes
phone reboots
Hope this helps
Bilbo,
Hi. I ran through what you put but my Mini S does not auto reboot. I'm not sure the exact definition of a soft reboot is? - Put the stylus in the side or hold the power button for a few seconds?
Either way I cannot get the new KJAM rom on as invalid vendor ID is haunting me.
Any help would be appreciated.
Thank You
Ben
Dudes - I've done the same upgrade to my mini S. Not sure if it's worth the bother. No difference in speed/performance and my keyboard shifted symbols (@?£$) are out of sync. I think I'll go back to the Mini S rom without the customised stuff.
LLcoolJ:
I noticed lots of difference, speed and battery life.
To get the keyboard from US to UK symbols use the following:
Here are the registry changes ....
Keyboard language
Registry: HKCU\ControlPanel\Keybd
Key: Locale (string)
Value: 0809 English UK
0409 English US
0407 German
0419 Russian
040C French
0410 Italian
040A Spanish
benih007 said:
Bilbo,
Hi. I ran through what you put but my Mini S does not auto reboot. I'm not sure the exact definition of a soft reboot is? - Put the stylus in the side or hold the power button for a few seconds?
Either way I cannot get the new KJAM rom on as invalid vendor ID is haunting me.
Any help would be appreciated.
Thank You
Ben
Click to expand...
Click to collapse
The invalid vendor ID is the result of the ROM update..... to get rid of it make sure you run :
run lokiwiz.bat from PC
select option 'U' Unlock SIM
phone reboots
add SIM to backout bin file names on PC
A soft reboot is when you hit the reset button on the right hand side, its like rebooting a PC. A hard reset however is a re-install boot where you loose everything and the ROM is re-installed.
Cheers Bilbo - I've made the changes to the registry and the keyboard talks like me. Your right about battery power as well.
Bilbo.
Thank you for replying and helping.
Let me just go over what you said...
first I ran the loki cab file on the mini S.
run lokiwiz.bat from PC -- done.
select option 'U' Unlock SIM -- done (with sim card removed)
phone reboots -- not automatically though, but I will reboot it after the lokiwiz.bat finishes
add SIM to backout bin file names on PC -- what does this mean? this is not in the lokiwiz instructions and this is where i'm going wrong. Where is the bin file created btw, I can never find it?
I have tried so many combinations i'm starting to lose hope.
If you can help to get this damn thing working I promise to make a donation to this web site.
Thanks for all the good work.
Ben
i managed to get the unlock, but did not do the CID (so will try that).
So once i have done that will the K-JAM_WWE_216901_2169101_020721_ship.exe upgrade work?
Here's how I got mine working. - Remove the Sim card. Make sure you use Lockwiz02b. Select U to unlock from the options menu. The mini S should reboot automatically. Leave the device alone until its functional again and then start Lockwiz02b again. Select C (CID unlock) from the menu. It should reboot again and close down the Lockwiz box. The mini S should now be ready for a rom upgrade. On my first attempt I used the original Lockwiz prog which caused problems for me.
I'm about to do my rom update on my mini s....but this thread is so confusing!
Is there a step by step guide somewhere on the forum???
ROM Upgrade
Upgraded O2 XDA mini without any real problems:
I used the aWizard 1.3 Beta 2 tool which allowed me to carry out the CID Unlock and was pretty easy to understand. What it did not do was pick up the ROM from the rom folder but once I had completed the CID unlock I ran the rom normally and all was well.
So in essence: Connect Mini to PC via Activesync
Run the aWizard Bat file enabling RAPI (This is used to communicate with your XDA once it has done using Activesync). Then select the Unlock CID option. Once completed I then exited the wizard and followed the instructions as part of the rom upgrade and all worked well no hitches except the one mentioned above about the keyboard (now I have to find out how to modify the registry).
So what I used: aWizard 1.3 Beta 2 and QTEK Rom 2.17
186504-ruu_9100_2170702_21707102_20710_qtek_wwe_ship.exe
Mystery Solved!!!!
I finally figured out why its not working....
When I downloaded the loki zip file I opened it up in winzip and dragged the contents to a folder I created. Ran the batch file eveything seemed ok and the unlocker said it unlocked the device.
I have now realised that you have extract the files from the loki zip file and use the folder structure. If you don't, the utils directory is not created and the loki.bat cannot reference some files.
Found the answer on page 12/13 of the loki thread.
Thanks All
Ben
After doing the CID unlock the ROM install worked fine.
Just having the keyboard issue at the moment with symbols, went to:
Registry: HKCU\ControlPanel\Keybd
Key: Locale (string)
Value: 0809 English UK
but could not find the locale key to set to UK?
All i see is:
DefaultKeyLock
InitialDelay
MuteSwitch
RepeatRate
ShowWarningMsg
Am i looking in the right place or do i have to add this in (if so how)?
Cheers
Youv'e got to create a new registry key. Assuming you've got a registry editor. Go to HKEY_CURRENT_USER / Control Panel / Keybd.
Then create a new string value. Name it Locale and give it a value of 0809 for UK. Then reboot.
Just went in a created the new reg key as you mentioned.
Rebooted and it worked.
Many thanks for all your help on this, it is most appreciated.
I am now the converted!!!
So to sum up for anybody else:
Bought XDA Mini S from 02
use Lockwiz02b
Select U to unlock from the options menu
The mini S should reboot automatically
Start Lockwiz02b again
Select C (CID unlock) from the menu
It should reboot again and close down the Lockwiz box
The mini S should now be ready for a rom upgrade.
Then run
K-JAM_WWE_216901_2169101_020721_ship.exe
follow usual prompts.
Once phone is up and running, get a reg edit tool (i used PHMregedit) as the keyboard for a couple of the symbols is out of synch (think it is US style).
Using regedit tool
Go to HKEY_CURRENT_USER / Control Panel / Keybd
Then create a new string value
Name it Locale and give it a value of 0809 for UK
Then reboot.
Mini XDA should now work fine.
I have found that the new push technology for email is faster than Blackberry and more usueful.
Hope this is helpful to others.
Cheers great forum
quick question...
i am fed up with waiting for o2 to release their latest ROM so i am going to take the plunge with this ROM instead, my question is do i have to make any special changes once installed to make it work with O2 UK i.e. mms settings, GPRS settings etc.?
Also i noticed somebody has put together a T-Mobile USA customised ROM any chance that somebody will do this for O2 UK?
hyettd said:
Just went in a created the new reg key as you mentioned.
Rebooted and it worked.
Many thanks for all your help on this, it is most appreciated.
I am now the converted!!!
So to sum up for anybody else:
Bought XDA Mini S from 02
use Lockwiz02b
Select U to unlock from the options menu
The mini S should reboot automatically
Start Lockwiz02b again
Select C (CID unlock) from the menu
It should reboot again and close down the Lockwiz box
The mini S should now be ready for a rom upgrade.
Then run
K-JAM_WWE_216901_2169101_020721_ship.exe
follow usual prompts.
Once phone is up and running, get a reg edit tool (i used PHMregedit) as the keyboard for a couple of the symbols is out of synch (think it is US style).
Using regedit tool
Go to HKEY_CURRENT_USER / Control Panel / Keybd
Then create a new string value
Name it Locale and give it a value of 0809 for UK
Then reboot.
Mini XDA should now work fine.
I have found that the new push technology for email is faster than Blackberry and more usueful.
Hope this is helpful to others.
Cheers great forum
Click to expand...
Click to collapse
The Problem im having here is that once i have created the registry key, it deletes after a reboot. Is there something else i need to unlock to allow writing to the registry?
New Roms
Hi there - I'm sure this is your answer - I have read this on many forums.
WM05 takes a while to store the registry updates after you exit your editor. Make the registry change and wait a minute or so before performing the soft reset.
Hope this helps - we have all fell for this "improvement" to WM5 from the boys at MS.
Regards,
Chris.
:lol:
Thanks Bilbo . . . Spot on. First time to all this and followed it a treat
Thanks All
Hi there,...
what exactly does the application lock do???
steve
ok, found some infos...
Most WM5 phones only allow you to load applications that have an acceptable digital signature. If you try to edit the registry or load an application it will give you an error. Application Unlocking removes this barrier and allows you to install any application or edit the registry to your liking.
Click to expand...
Click to collapse
but this is not really significant ....
the MTeoR has an application lock!! but what limitations did you expect with it??
the only one i have found is while trying various of programms that on -> TinyGPS didn't worked ... ends with the message that the phone has application locked... after unlocking the MTeoR the program starts... (but hangs on license screen but i think thats a general problem with qvga and wm5-sp)
anyother troubles with the app-lock ???
I'm didn't have any troubles with application lock in MTeoR
I'm use complex method to remove this lock
In RegEditSTG: HKEY_LOCAL_MACHINE\Security\Policies\Policies\00001001 = 2
->from 2 to 1
HKEY_LOCAL_MACHINE\Security\Policies\Policies\00001005 = 16
-> from 16 to 40
HKEY_LOCAL_MACHINE\Security\Policies\Policies\00001017 = 128
-> from 128 to 144
HKEY_LOCAL_MACHINE \Security\Policies\Policies
-> create new "0000101b" (type Dword) = 1
<reset>
And as last i'm use SDA Application Unlock
May be some of this steps are unnecessary but it is work!
And other way to run exe without sign from MSP - create sign!
Read more about CodeSigningX86 from Microsoft. It works great, i'm use my sign for rather programs (because i didn't use app unlock in WM5 Emu for my PC)
Hi!
I've installed PHM RegEdit on my MTeor, but i can't change any values It always gives me a failure 'Unable to perform this operation'. I'm a noob in tweaking regs oder ppc/smartphones, so someone could help me, please? Until now I used a BlueAngel. A very good device, but to big for daily use, so I bought this MTeor. Now I've got the application problem. But why I can't change values in the registry?
@futureshock: Evtl. kannst Du mir auch über's ICQ helfen?
Ok, i made it. I found this post: http://forum.xda-developers.com/showpost.php?p=1038508&postcount=2
Hi, i'm new on this forum,and have a problem.When i try to install some wm5 software (autokeylock wm5 for exemple), on screen i got message:"Installation was unsuccessful.The program or setting cannot be installed because it does not have sufficient system permissons".So what to do?Sorry for my english.P.S.I use serbian mobile operator,no orange.Thank you.
So,nothing?
zikicz said:
So,nothing?
Click to expand...
Click to collapse
Find and download "regeditSTG2" and "SDA_Application_Unlocker".
Copy RegeditSTG2 to phone and execute.
Locate the key "HKEY_LOCAL_MACHINE\SECURITY\POLICIES\POLICIES" and select Values (left softkey).
Edit 00001001 to hold Value Data = 1
Edit 00001005 to hold Value Data = 40
Sync the phone and execute SDA_Application_Unlocker on the PC. Select "Unlock" and once succesful turn the 'phone off and then back on.
Now you are free to do what you like.
Tnak you man.
now i have a new problem.I copy regedit to phone (mem card) but when i try to execut them it look for COMMAND and PARAMETERS.So,what to type in thiese fileds?Sorry,but i am new in smartphone zone.
zikicz said:
now i have a new problem.I copy regedit to phone (mem card) but when i try to execut them it look for COMMAND and PARAMETERS.So,what to type in thiese fileds?Sorry,but i am new in smartphone zone.
Click to expand...
Click to collapse
No idea. Are you sure it was "REGEDITSTG2"?
yes.So i can't execute them on the phone.Meybe i do something wrong?Can i do first with unlocer?
I am not able to get my SPC /MSL from my new Sprint Diamond that I have been able to unlock, and flash Juicy 2.2 onto it. Since then I have performed a hard reset and gone back to the factory ROM.
I have tried the following:
1. Performed the instructions for getspc from
http://forum.ppcgeeks.com/showthread.php?t=36639
(Note I did use the PHex Esn and I did use caps on all hex numbers)
2. I was able to install QPST on a on WinXP box and get it to see the phone. I did this to verify that I had the correct hex esn. QPST did read the esn from the phone and display the same hex esn that I had in step 1.
3. I tried the general codes 000000, 123456,111111 and the last 6 digits of the phone number programmed in the phone 000-000-2743.
I am entering the number (6 digits) that getspc.exe tells me in the enter unlock code box that comes up after I enter ##778# and hit edit. It looks like it is working on something then tells me the code is wrong.
What is the way that I can get the SPC / MSL without calling?
The only answer I found
I hate to ask and answer my own questions but if anyone else runs into this problem I want them to have an answer.
I could not get getspc.exe to work in any way.
I found this registry hack somewhere so I am not taking credit for it but it works!!!!
Change the following registry entries in:
HKEY_LOCAL_MACHINE\SOFTWARE\HTC\ATDbgLog
Enable: 1
LogMode: 1
* Wait a reasonable amount of time and soft-reset (I have noticed that it seems to take longer for this value to take affect, so if you reboot and the registry values are not changed, then you need to do it again and wait longer)
* Check to see that the file \ATDbg0\ATDbg0.txt has been created.
* Return the values back to what they were (most likely 0) waiting the same amount of time as above.
* Look in the ATDbg0.txt file and you should see a log of commands sent to the CDMA radio and there should be something like this somewhere in the file:
|| Begin Code Sample ||
11:9:3 Tx:AT+HTC_RMSL=0\r
11:9:3 Rx:+HTC_RMSL: 354201\r\n0\r
11:9:3 Tx:AT+HTC_ROTKSL=0\r
11:9:3 Rx:+HTC_ROTKSL: 216112\r\n0\r
|| End Code Sample ||
The numbers next to the Rx: +HTC_RMSL line should be your MS
I used resco exploror to change my registry waited about 1 hour and did a soft reset twice during that time.
I found the directory with the output file in the root directory.
Yes, it works
the getspc.exe, don´t work, but the this process work very fine
Adding an explanation for starting this thread
I started this thread because when I search for ways to get more memory, all I find is how others have things like "Big Storage" etc., but somewhere it will say cannot be done on wizard. I do not find very much about what can be done or why it cannot be done. I have found things about unlocking and unhidng the Extended_ROM. I used that as a basis for my trials and trying to understand how memory works in the wizard.
I started this thread hoping someone with much more knowledge than me would be able to shed light on the issue and it would be on the forum for future users to understand the memory issues on the wizard.
-----------------------------------------------------------------------------------------------------------
In default.hv which I converted to rgu so I could read I saw the following:
Code:
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\PartitionTable][/FONT]
[FONT=Arial]"26"="BINARY"[/FONT]
[FONT=Arial]"25"="IMGFS"[/FONT]
[FONT=Arial]"23"="RAWFS"[/FONT]
[FONT=Arial]"22"="RAWFS"[/FONT]
[FONT=Arial]"21"="BINFS"[/FONT]
[FONT=Arial]"20"="BOOT"[/FONT]
[FONT=Arial]"0F"="FATFS"[/FONT]
[FONT=Arial]"0E"="FATFS"[/FONT]
[FONT=Arial]"0C"="FATFS"[/FONT]
[FONT=Arial]"0B"="FATFS"[/FONT]
[FONT=Arial]"07"="NTFS"[/FONT]
[FONT=Arial]"06"="FATFS"[/FONT]
[FONT=Arial]"04"="FATFS"[/FONT]
[FONT=Arial]"01"="FATFS"[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles][/FONT]
[FONT=Arial]"Folder"="Mounted Volume"[/FONT]
[FONT=Arial]"PartitionDriverName"="MSPART"[/FONT]
[FONT=Arial]"DefaultFileSystem"=""[/FONT]
[FONT=Arial]"MountFlags"=dword:0[/FONT]
[FONT=Arial]"AutoFormat"=dword:0[/FONT]
[FONT=Arial]"AutoPart"=dword:0[/FONT]
[FONT=Arial]"AutoMount"=dword:1[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FLASHDRV][/FONT]
[FONT=Arial]"BootPhase"=dword:0[/FONT]
[FONT=Arial]"MountFlags"=dword:11[/FONT]
[FONT=Arial]"Folder"="imgfs"[/FONT]
[FONT=Arial]"Name"="Microsoft Flash Disk"[/FONT]
[FONT=Arial]"PartitionDriver"="mspart.dll"[/FONT]
[FONT=Arial]"DefaultFileSystem"="IMGFS"[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FLASHDRV\IMGFS][/FONT]
[FONT=Arial]"XIP"=dword:0[/FONT]
[FONT=Arial]"MountFlags"=dword:11[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FLASHDRV\FATFS][/FONT]
[FONT=Arial]"FatCacheSize"=dword:100[/FONT]
[FONT=Arial]"DataCacheSize"=dword:800[/FONT]
[FONT=Arial]"EnableWriteBack"=dword:1[/FONT]
[FONT=Arial]"MountAsRoot"=dword:1[/FONT]
[FONT=Arial]"MountAsBootable"=dword:1[/FONT]
[FONT=Arial]"CheckForFormat"=dword:1[/FONT]
[FONT=Arial]"FormatTFAT"=dword:1[/FONT]
[FONT=Arial]"Flags"=dword:600014[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FLASHDRV\FATFS\Filters\fsreplxfilt][/FONT]
[FONT=Arial]"Order"=dword:1[/FONT]
[FONT=Arial]"Dll"="fsreplxfilt.dll"[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\MSFlash\Part00][/FONT]
[FONT=Arial]"CheckForFormat"=dword:1[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\MSFlash\FATFS][/FONT]
[FONT=Arial]"MountHidden"=dword:0[/FONT]
[FONT=Arial]"MountAsROM"=dword:0[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\MSPART][/FONT]
[FONT=Arial]"Dll"="mspart.dll"[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\IMGFS][/FONT]
[FONT=Arial]"ShadowROM"=dword:1[/FONT]
[FONT=Arial]"Paging"=dword:1[/FONT]
[FONT=Arial]"Dll"="imgfs.dll"[/FONT]
[FONT=Arial]"FriendlyName"="Image-Update Filesystem"[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\FATFS][/FONT]
[FONT=Arial]"CacheSize"=dword:2000[/FONT]
[FONT=Arial]"Flags"=dword:44[/FONT]
[FONT=Arial]"CacheDll"="diskcache.dll"[/FONT]
[FONT=Arial]"Util"="fatutil.dll"[/FONT]
[FONT=Arial]"EnableCache"=dword:1[/FONT]
[FONT=Arial]"Paging"=dword:1[/FONT]
[FONT=Arial]"Dll"="fatfsd.dll"[/FONT]
[FONT=Arial]"FriendlyName"="FAT FileSystem"[/FONT]
In boot.rgu I found
Code:
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager] [/FONT]
[FONT=Arial]"PNPUnloadDelay"=-[/FONT]
[FONT=Arial]"PNPUnloadDelay"=dword:5dc[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC\IMGFS][/FONT]
[FONT=Arial]"MountFlags"=dword:11[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC][/FONT]
[FONT=Arial]"Name"="DiskOnChip M-Systems"[/FONT]
[FONT=Arial]"Folder"="imgfs"[/FONT]
[FONT=Arial]"MountFlags"=dword:11[/FONT]
[FONT=Arial]"BootPhase"=dword:0[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\Drivers\BuiltIn\TrueFFS][/FONT]
[FONT=Arial]"Flags"=dword:1000[/FONT]
[FONT=Arial]"Index"=dword:1[/FONT]
[FONT=Arial]"Profile"="TRUEFFS_DOC"[/FONT]
[FONT=Arial]"Dll"="TrueFFS.dll"[/FONT]
[FONT=Arial]"Prefix"="DSK"[/FONT]
[FONT=Arial]"Order"=dword:0[/FONT]
[FONT=Arial]"WindowBase"=dword:0[/FONT]
[FONT=Arial]"IClass"=multi_sz:"{A4E7EDDA-E575-4252-9D6B-4195D48BB865}"[/FONT]
[FONT=Arial]"BootPhase"=dword:0[/FONT]
[FONT=Arial]"AutoDPDMode"=dword:1[/FONT]
[FONT=Arial]"SoftwareWriteProtect"=dword:1[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Autoload\TrueFFS][/FONT]
[FONT=Arial]"DriverPath"="Drivers\\BuiltIn\\TrueFFS"[/FONT]
[FONT=Arial]"LoadFlags"=dword:1[/FONT]
[FONT=Arial]"BootPhase"=dword:0[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC1][/FONT]
[FONT=Arial]"DefaultFileSystem"="FATFS"[/FONT]
[FONT=Arial]"Name"=""[/FONT]
[FONT=Arial]"PartitionDriver"=""[/FONT]
[FONT=Arial]"Folder"="Extended_ROM"[/FONT]
[FONT=Arial]"MountHidden"=dword:1[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC1\FATFS][/FONT]
[FONT=Arial]"Flags"=dword:14[/FONT]
[FONT=Arial]"FormatTfat"=dword:1[/FONT]
[FONT=Arial]"EnableWriteBack"=dword:1[/FONT]
[FONT=Arial]"DataCacheSize"=dword:00000080 ;128 sectors(128*512=64KB)[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\TRUEFFS_DOC1][/FONT]
[FONT=Arial]"DriverPath"="Drivers\\BuiltIn\\TrueFFS1"[/FONT]
[FONT=Arial]"LoadFlags"=dword:1[/FONT]
[FONT=Arial]"Order"=dword:1[/FONT]
[FONT=Arial]"Bootphase"=dword:1[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\Drivers\BuiltIn\TrueFFS1][/FONT]
[FONT=Arial]"Profile"="TRUEFFS_DOC1"[/FONT]
[FONT=Arial]"Index" = dword:2[/FONT]
[FONT=Arial]"Dll" = "TrueFFS.dll"[/FONT]
[FONT=Arial]"Prefix" = "DSK"[/FONT]
[FONT=Arial]"Order" = dword:1[/FONT]
[FONT=Arial]"Ioctl" = dword:4[/FONT]
[FONT=Arial]"Use8Bit" = dword:1[/FONT]
[FONT=Arial]"WindowBase" = dword:00000000[/FONT]
[FONT=Arial]"IClass"=multi_sz:"{A4E7EDDA-E575-4252-9D6B-4195D48BB865}"[/FONT]
[FONT=Arial]"AutoDPDMode" = dword:1[/FONT]
[FONT=Arial]"SoftwareWriteProtect"=dword:1[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\Comm][/FONT]
[FONT=Arial]"AutoRun"="\\Windows\\AutoRun.exe"[/FONT]
[FONT=Arial]"AutoRunCFG"=[URL="file://\\Extended_ROM\\Config.txt"]\\Extended_ROM\\Config.txt[/URL][/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC2][/FONT]
[FONT=Arial]"DefaultFileSystem"="FATFS"[/FONT]
[FONT=Arial]"Name"=""[/FONT]
[FONT=Arial]"PartitionDriver"=""[/FONT]
[FONT=Arial]"Folder"=""[/FONT]
[FONT=Arial]"MountFlags"=dword:6[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC2\FATFS][/FONT]
[FONT=Arial]"Flags"=dword:00600014[/FONT]
[FONT=Arial]"FormatTFAT"=dword:1[/FONT]
[FONT=Arial]"CheckForFormat"=dword:1[/FONT]
[FONT=Arial]"MountAsBootable"=dword:1[/FONT]
[FONT=Arial]"MountAsRoot"=dword:1[/FONT]
[FONT=Arial]"EnableWriteBack"=dword:1[/FONT]
[FONT=Arial]"DataCacheSize"=dword:00000080[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\Drivers\BuiltIn\TrueFFS2][/FONT]
[FONT=Arial]"Index"=dword:3[/FONT]
[FONT=Arial]"Profile"="TRUEFFS_DOC2"[/FONT]
[FONT=Arial]"Dll"="TrueFFS.dll"[/FONT]
[FONT=Arial]"Prefix"="DSK"[/FONT]
[FONT=Arial]"Order"=dword:0[/FONT]
[FONT=Arial]"Ioctl"=dword:4[/FONT]
[FONT=Arial]"Use8Bit"=dword:1[/FONT]
[FONT=Arial]"WindowBase"=dword:0[/FONT]
[FONT=Arial]"IClass"=multi_sz:"{A4E7EDDA-E575-4252-9D6B-4195D48BB865}"[/FONT]
[FONT=Arial]"AutoDPDMode"=dword:1[/FONT]
[FONT=Arial]"SoftwareWriteProtect"=dword:0[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Autoload\TrueFFS2][/FONT]
[FONT=Arial]"DriverPath"="Drivers\\BuiltIn\\TrueFFS2"[/FONT]
[FONT=Arial]"LoadFlags"=dword:1[/FONT]
[FONT=Arial]"Order"=dword:0[/FONT]
[FONT=Arial]"BootPhase"=dword:1[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC2\FATFS\Filters\fsreplxfilt][/FONT]
[FONT=Arial]"dll"="fsreplxfilt.dll"[/FONT]
[FONT=Arial]"order"=dword:1 ; must be loaded before other filters[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\FATFS][/FONT]
[FONT=Arial]"FriendlyName"="FAT FileSystem"[/FONT]
[FONT=Arial]"Dll"="fatfsd.dll"[/FONT]
[FONT=Arial]"Flags"=dword:00000024[/FONT]
[FONT=Arial]"Paging"=dword:1[/FONT]
[FONT=Arial]"EnableCache"=dword:1[/FONT]
[FONT=Arial]"CacheSize"=dword:0[/FONT]
[FONT=Arial]"Util"="fatutil.dll"[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\filters\HTCFSDSPY][/FONT]
[FONT=Arial]"Dll"="htcfsdspy.dll"[/FONT]
[FONT=Arial]"Order"=dword:0[/FONT]
Of course there is more than just the above in those files. What I wonder since I do not know enough to know what cannot be done is...
Can you change these settings to not define a region to be extended ROM?
Can you redefine the rest to use this left over space?
Can any of this space be used for program memory instead of storage memory?
I do not know if the dll files limit the size of the regions or is some of the settings determine the sizes.
As I said, I do not know enough to know the limitations, but the little boy saw all that was needed was to let the air out of the tires to get the truck unstuck from under the bridge.
Note: This work was done on my G4
Are you using LZX compression?
If not start reading form “HERE” post #877
I have been reading that and the Visual Kitchen Thread, but they leave me behind a little yet.
I am just now trying to go past using the HyperCore Kitchen and switch to CRBuilder 2. I am not sure what it does different. It seems to be less forgiving of my mistakes.
I also read the threads on porting XIP, etc. I am still trying to learn this stuff.
Since I am naturally lazy, I thought what if we could get more room by not defining ExtendedROM. Also, I did not know how program memory versus storage memory is set up and if it was possible to get more program memory available. This is going to become our limiting factor (M2D, WM6.5, etc.).
Everything i’ve read would suggest that we can’t use the extended ROM area for anything other then what it was designed for.
I don’t think you can gain any more memory without removing programs.
I have been doing a lot of reading. I have a G4 Wizard. I have edited my boot.rgu, boot.hv and default.hv to remove references to TRUEFFS_DOC1 (the extended ROM). As expected, I cannot see extended rom in total commander. I did not notice a jump in total memory on the phone. I am beginning to think extended rom is coded in the chip and not set by our flashes. Has anyone tried something like DiskOnChip TrueFFS Uilities package or similar to redefine the spaces on the chip to not have extended rom? I know so little, I imagine there is something more that prevents this, but I thought I would ask. I did not know if this path would lead to more program memory in addition to storage memory.
Delete references to TRUEFFS_DOC1
I decided to do a separate post for each trial.
I have edited my boot.rgu, boot.hv and default.hv to remove references to TRUEFFS_DOC1 (the extended ROM). As expected, I cannot see extended rom in total commander. I did not notice a jump in total memory on the phone. I did not notice a change in battery consumption.
Change TRUEFFS_DOC1 settings to be more like TRUEFFS_DOC2
I basically changed TRUEFFS_DOC1 (changed to call it StoROM) settings to match TRUEFFS_DOC2 (regular memory) except I did not set it as "root".
It shows up as removable storage with 4.9 MB of space.
I suspect something in TRUEFFS driver or I am missing a setting to tell it that is is not external memory.
I tried again, but named it "My Documents"
Word and excel would see the template files in My Documents\Templates twice. I could not set word's default file type. No choices showed in the option. I tried moving the templates, but then they could not be seen by word or excel.
Tried sync with my PC. What was already on the phone would not copy to the PC. I added things to the folder on the PC and they would add to the phone. If I deleted it off the phone, instead of deleting it off the PC it would put it back on the phone. If I copy a file from my phone to the my documents folder on the phone it would not show up on the PC. So it seems I have one-way sync capability.
I tried again, but named it "Program Files"
It works, but whatever gets written there stays so I had problems when I did a hard reset. I solved by deleting contents of folder before hard resetting.
Currently testing named to "FileSafe"
I can put files there and they do not get lost in a hard reset.
I am currently testing battery consumption on this latest format. First day, but after 5 hours only down to 91%. Will need to wait because I have noticed battery goes down faster as the level gets lower.
I did a soft reset and ended up with Storage card as a folder in root and storage card2 as the storage card. Cannot delete it since I have reg settings made to locate internet explorer files to storage card.
I'll have to keep tweaking settings.
More about Trueffs driver
I came across a package called "DiskOnChip(R) TrueFFS(R) Uilities package"
This Package includes the TrueFFS Version 6.3.2 Utilities Package
Reading the documentation gives me the impression that the chip is formatted at the factory and we cannot change the partitions. I suspect (stating again) that we only tell the software what to do with the partition. I tried to run the utility, but it could not find the chip to even do a read function.
It also looks like you have to have a password to gain access to parts. I do not fully understand this stuff, but I was reading about locking partitions with a password.
This may be why even though I have the format flag set in TRUEFFS_DOC1 it does not get formatted and as a result the things stored there are still there after a hard reset. Also, why it shows up as removable media even though I do not see where I tell it that it is such. I think anything other than the root is considered "external" and shows up as a storage card.
Explanation added
I added an explanation for this thread to the first post
Updated post #7 about FileSafe.
I have tried every which way I can think and can only create a folder that the phone considers a removable storage device. I keep getting the storage card2 problem so I have gone back to regular settings and installed a blank Ext_ROM.
I am fairly sure of my theory that the partitions are formated at the factory and we are only telling the software what to call them and how to access them. We cannot change what they have been set to at the factory.
I welcome any clarification from someone who knows more.
Hopefully this will help others like me who come in late in the game and wonder why we cannot get things like BigStorage, etc. other than just seeing people saying it cannot be done.
I read about hiding and unhiding the Ext-ROM, too. Unhiding and reading was no problem but writing didn't work.
Converting Ext-ROM to program-memory may not be possible, because AFAIK program-memory is SD-RAM and the Ext-ROM is Flash-MEMORY. But there are more ways the memory of the Ext-ROM could be usefull.
More space for the ROM (max. 57MB for OS.nb is not much when cooking a WM6.5 ROM) would be nice.
OR
A storage-partion like Ext-ROM but with write access!
Only unhiding the Ext-ROM didn't do the job! I could read from the Ext-ROM but couldn't write. After a write attempt the file list got corrupted and I had to hide and unhide again to get read access back.
If I understand the posting right, RoryB was already able to write to the Ext-ROM. How did you do that?
There is one more Problem! Not the MiniSD-Card but the Ext-ROM should get the name "StorageCard 2" (or any other name which comes alphabeticaly after StorageCard). Why? The Camera can save to different locations but you can only choose from 2: Main memory and the alphabeticaly first storage card.
My questions:
1. How do I get read, write and delete access to the Ext-ROM?
2. How can I rename this "Ext-ROM-Storagecard"? Something like "StorageCard 2" or "StorageMemory" or ...
Update:
Answer for question 2 might be:
AbuYahya said:
To Rename EXT-ROM
HKEY_LOCAL_MACHINE \System\StorageManager \Profiles\TRUEFFS_DOC1
"Folder"=string:Storage
--- can call it anything you like instead of "Storage"
Click to expand...
Click to collapse
I didn't check it yet.
I have stopped trying to get Extended_ROM as storage space. I did use it as a filesafe location. I could not get access to all of the space even though I installed an empty Extended_ROM. Here is the part of boot.rgu I changed (best as I can remember)
Code:
;[HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\TRUEFFS_DOC1]
; Does not seem right to me to be TRUEFFS_DOC1 when all others use the built in driver and not the profile
[HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\TRUEFFS1]
"DriverPath"="Drivers\\BuiltIn\\TrueFFS1"
"LoadFlags"=dword:1
"Order"=dword:1
"Bootphase"=dword:1
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\TrueFFS1]
"Profile"="TRUEFFS_DOC1"
"Index" = dword:2
"Dll" = "TrueFFS.dll"
"Prefix" = "DSK"
"Order" = dword:1
"Ioctl" = dword:4
"Use8Bit" = dword:1
"WindowBase" = dword:0
"IClass"=multi_sz:"{A4E7EDDA-E575-4252-9D6B-4195D48BB865}"
"AutoDPDMode" = dword:0
"SoftwareWriteProtect"=dword:0
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC1]
"DefaultFileSystem"="FATFS"
"Name"=""
"PartitionDriver"=""
"Folder"="FileSafe"
"MountHidden"=dword:0
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC1\FATFS]
"Flags"=dword:14
"FormatTfat"=dword:1
"EnableWriteBack"=dword:1
"DataCacheSize"=dword:00000080 ;128 sectors(128*512=64KB)
I think the "Storage Card 2" problem comes about from the order in which the Extended_ROM and SD Card get recognized and for some reason it sees the Extended_ROM as a storage card.
I now use Extended_ROM that way Cingular did. I have files in it in the form of cabs and zips. These files are things like Adobe Reader as a cab, Template files as a zip, etc. I use my customization mortscript to install those files. This way I get more room in the ROM for things that have to be in the ROM. Here is the format I have for my boot.rgu
Code:
;[HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\TRUEFFS_DOC1]
; Does not seem right to me to be TRUEFFS_DOC1 when all others use the built in driver and not the profile
[HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\TRUEFFS1]
"DriverPath"="Drivers\\BuiltIn\\TrueFFS1"
"LoadFlags"=dword:1
"Order"=dword:1
"Bootphase"=dword:1
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\TrueFFS1]
"Profile"="TRUEFFS_DOC1"
"Index" = dword:2
"Dll" = "TrueFFS.dll"
"Prefix" = "DSK"
"Order" = dword:1
"Ioctl" = dword:4
"Use8Bit" = dword:1
"WindowBase" = dword:0
"IClass"=multi_sz:"{A4E7EDDA-E575-4252-9D6B-4195D48BB865}"
"AutoDPDMode" = dword:1
"SoftwareWriteProtect"=dword:1
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC1]
"DefaultFileSystem"="FATFS"
"Name"=""
"PartitionDriver"=""
"Folder"="Extended_ROM"
"MountHidden"=dword:1
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC1\FATFS]
"Flags"=dword:14
"FormatTfat"=dword:1
"EnableWriteBack"=dword:1
"DataCacheSize"=dword:00000080 ;128 sectors(128*512=64KB)
I use winimage to change the contents of my Extended_ROM.nb file. Now when I run nb2nbf I pick the OS and the Extended_ROM as files to write to the nbf.
G4 processors do not allow you to flash a custom extended ROM (IIRC).
jwzg said:
G4 processors do not allow you to flash a custom extended ROM (IIRC).
Click to expand...
Click to collapse
That is just not true! In my WM6.5 ROM there is a custom Ext-ROM included and I have no problem flashing it to my G4 Wizard.
G4-Save means no IPL/SPL but Ext-ROM is not a problem.
@RoryB:
Thank you for the information. I will try it.
RoryB's latest ROM that uses ExtRom for cabs and such works fine on my G4.
Ham3r's experimental ROM that provides ExtRom as a read/write filesystem works on G3.
I even installed apps onto ExtRom, with no problems.
I don't know about its relative speed.
It is marked "G3 only" so I have not tried it on my G4.
If someone is brave enough to show that the Ham3r rom's method works on G4, that would be a great feature.
I think that making the most of extrom as a filesystem is the best we can do.
Cyberdyne said:
That is just not true! In my WM6.5 ROM there is a custom Ext-ROM included and I have no problem flashing it to my G4 Wizard.
G4-Save means no IPL/SPL but Ext-ROM is not a problem.
@RoryB:
Thank you for the information. I will try it.
Click to expand...
Click to collapse
For some reason I was thinking it wouldn't flash. I haven't touched my Wizard in a while, and my XP computer with my kitchen on it is dead. I'll have to upgrade my WM6 ROM again.
Mods ain't gods. I stand corrected.