On the FTP site I see Helmi_APACHE_AKU3.5_nk.nba_built3.rar - but there is no discussion of this ROM in the forums.
Is it real and working? Or still in development and not yet released?
I've been wondering this myself. Bored at work, guess I'll see if I can flash it now.
xda3nbftool says I've got the wrong password when trying to convert the nba to nbf *sigh*
edit: Found HTC64 Extended ROM Tool and used this instead. I managed to flash the ROM onto my phone, got a Telecom carrier logo and was given a new green splash screen that said "Windows Mobile - Direct Push Technology"...I was excited!
It asked me to calibrate my screen, go through the training crap. It then asked if I wanted to setup an e-mail account, which is definitely a sign of a new AKU and not something bogus. I clicked next (instead of skip) and it froze. I soft reset and skipped the email step, then when it asked me to tap anywhere on the screen, it froze. Probably a driver issue, but I'm new here I don't know if this means we're close, but it was looking good for a minute
hmm... this rom is for rom maker only, It still under development, and It seems Big is busy right now... btw To make AKU3.5 work with Apache, I need a beta tester...
Apache beta tester
If you need a beta tester, I'd be glad to help. I don't keep anything on my phone that can't be easily replaced/reinstalled.
I'd also be willing to help with sending ext_rom, files, or anything else that would help.
helmi_c I don't know if you got my pm's from the other day, but if you need someone to test I would be more than happy. Also I tried the copied the gwes.exe.0409.mui from your awesome uni 3.5 rom to my apache to change the status circle screen to the glass one and had no luck with that. After a soft reset it stayed the same. I am using the Telecom aku 2.2 rom.
Thanks,
Mike
I can be a beta tester...please email me at [email protected] if you need me...thanks.
I've been looking for AKU3.x for apache everywhere, will be glad to test.
i would be glad to test it too,
You can count me in for beta testing also
pgdeaner said:
If you need a beta tester, I'd be glad to help. I don't keep anything on my phone that can't be easily replaced/reinstalled.
I'd also be willing to help with sending ext_rom, files, or anything else that would help.
Click to expand...
Click to collapse
I would also be willing to help as a beta tester.
I've only done offical ROM updates myself but done my fair share of messing with registry and and extended_rom hacking. I have a Sprint PPC6700 w/ Build 14847.2.0.0 loaded on it.
I do quite a bit of traveling but I'd be glad to help if I can. Feel free to email me.
Thanks for all the hard work.
Beta tester
Ooooh me me me!! [email protected]
id also be willing to help..... pm me for email address if needed.....
Now how did yall get Helmi on our Apaches side? lol Anyways Im here to help, that was my next step to get it to work on my device after I get my custom 2.2 released today. So if you need any help, and/or wanna share some info on whats needed, Im here to help. I have got a good idea where to start, just havent had the time.
~Mike
Lvballer06 said:
Now how did yall get Helmi on our Apaches side? lol Anyways Im here to help, that was my next step to get it to work on my device after I get my custom 2.2 released today. So if you need any help, and/or wanna share some info on whats needed, Im here to help. I have got a good idea where to start, just havent had the time.
~Mike
Click to expand...
Click to collapse
Mike, can u look at built3 and mod both boot.hv/rgu at xip and change:
[HKEY_LOCAL_MACHINE\init\BootVars]
"RequireCertMod"=dword:1
and also in the default.hv, I've mod to many of stuff with this apache rom, this rom should faster then any other built exist... but it seems RequireCertMod=dword:1 is needed for some driver to make it load with apache device.
regard,
helmi_c said:
Mike, can u look at built3 and mod both boot.hv/rgu at xip and change:
[HKEY_LOCAL_MACHINE\init\BootVars]
"RequireCertMod"=dword:1
and also in the default.hv, I've mod to many of stuff with this apache rom, this rom should faster then any other built exist... but it seems RequireCertMod=dword:1 is needed for some driver to make it load with apache device.
regard,
Click to expand...
Click to collapse
Thank you sir, and I will have to change them later. Its about my bedtime. Been working all night. If ya wanna contact me directly for anything. My direct push email addy is admin [at] ppcgeeks dot com.
~Mike
For some reason I cant seem to find that file on the ftp site, can anyone point me to it by any chance? TIA...
~Mike
Mike,
It's in Uploads/Apache (or at least, it was).
Best of luck!
Keith
Thanks, gonna see what I can do now.
Success!!!
I managed to get it onto my device and get it up a running with a few major issues. I changed the value u posted, flashed it. Got the new splash screen, but it didnt go to the welcome tutorial. It kindof froze for a few secs then loaded. It now loads fine, but when I had tried to use it, the stylus couldnt be used. Due to not being able to calibrate the screen. So I named welcome.exe to autorun and put on my SD, loaded it and calibrated the screen. I can confirm my phone is working, but the start menu has only today and coldinit on it. I think this may be due to the intiflashfiles.dat. But Im not sure, Im still a novice. I see you added the last entries in.... And do u think that is the issue with the start menu? Also after a little messing with things, it freezes and locks up needing a soft reset to fix the issue. This happens, incall, trying to go to the text message box with poutlook, and well just about any other app I have tried. Works fine at first then freezes.....dunno why. Any ideas? I plan on playing with it until I can hopefully get some progress. But THANK YOU SO MUCH for getting us this far.
Regards,
Mike
Edit: Got to looking at the replacing of the boot.rgu and when it trys to delete and replace it isnt, but it is successfully replacing the boot.hv.....this is the error I get...... Any ideas? Could this be the cause of my issues? TIA
C:\Documents and Settings\Wideawake\Desktop\ApacheChangeBootXIP>ROMMASTER -d b
t.rgu -w 5 nk.fat -o nk.fat -v 5
[Info] It is a common ROM.
[Warning] o32_rom(0x907539bc)'s o32_data at 0x00000000 is zero.
[Warning] Found dif-referenced region [OLD] Address=0x90690128 Length=0x
000e00 ObjectType=0x00200000
[Warning] Found dif-referenced region [New] Address=0x90690128 Length=0x
000e00 ObjectType=0x00008000
[Warning] Found dif-referenced region [OLD] Address=0x90657560 Length=0x
000600 ObjectType=0x00200000
[Warning] Found dif-referenced region [New] Address=0x90657560 Length=0x
000600 ObjectType=0x00008000
[Warning] Found dif-referenced region [OLD] Address=0x9065d310 Length=0x
000a00 ObjectType=0x00200000
[Warning] Found dif-referenced region [New] Address=0x9065d310 Length=0x
000a00 ObjectType=0x00008000
[Warning] Memory Block(0x90541000,0x905caba0) overlap with Block(0x90542
4,0x90542f20).
[Error] Could not delete file 'boot.rgu'.
C:\Documents and Settings\Wideawake\Desktop\ApacheChangeBootXIP>ROMMASTER -a b
t.rgu -w 5 nk.fat -o nk.fat -v 5
[Info] It is a common ROM.
[Warning] o32_rom(0x907539bc)'s o32_data at 0x00000000 is zero.
[Warning] Found dif-referenced region [OLD] Address=0x90690128 Length=0x
000e00 ObjectType=0x00200000
[Warning] Found dif-referenced region [New] Address=0x90690128 Length=0x
000e00 ObjectType=0x00008000
[Warning] Found dif-referenced region [OLD] Address=0x90657560 Length=0x
000600 ObjectType=0x00200000
[Warning] Found dif-referenced region [New] Address=0x90657560 Length=0x
000600 ObjectType=0x00008000
[Warning] Found dif-referenced region [OLD] Address=0x9065d310 Length=0x
000a00 ObjectType=0x00200000
[Warning] Found dif-referenced region [New] Address=0x9065d310 Length=0x
000a00 ObjectType=0x00008000
[Warning] Memory Block(0x90541000,0x905caba0) overlap with Block(0x90542
4,0x90542f20).
[Warning] Memory Block(0x90541000,0x905caba0) overlap with Block(0x90542
4,0x90542f20).
[Warning] Memory Block(0x90541000,0x905caba0) overlap with Block(0x90542
4,0x90542f20).
[Error] Could not find free space to insert file 'boot.rgu'.
[Error] Can't add file 'boot.rgu' into ROM.
Click to expand...
Click to collapse
Lvballer06 said:
Edit: Got to looking at the replacing of the boot.rgu and when it trys to delete and replace it isnt, but it is successfully replacing the boot.hv.....this is the error I get...... Any ideas? Could this be the cause of my issues? TIA
Click to expand...
Click to collapse
U thinking what am I thinkin, It might be, since i delete the boot.rgu, system will not update the boot.rgu contains to registry after first boot, and does also might include its certification update...
try this pack, extract to where buildimgfs exist...
and also, did Certificate Applet on setting empty?
Related
this afternoon i found an update on the swedish qtek site.
http://www.qtek.se/default.asp?nc=4484&id=127&element=0
wonder if it could be used by english speaking users? it says WWE, so i guess it is in english?
i'm uploading the unpacked installation folder to FTP now. maybe someone who knows his thing, could magic a .bat file with the correct checksum to change the carrier and language? [pinoo? ;-)]
the file is called: MA_Qtek(BrPt)_10600_116_10500_SHIP.zip
Hi there..
I will take a look... But my device is with PocketPcTechs at the moment... Getting 128MB RAM ... WOOOOOOOOOOOT
:lol:
Cheers
has anybody yet found out what the passwords for the rom files are?
btw, have the last ones (the imate rom for example) been cracked or did anyone blurt out the right keys?
cu
A bad traduction :
Click on the links below in order to update your Qtek S100. Follows installationsguiden careful in order to few a correct updating.
ROM 1.06.116WWE
(updating from ROM 1.03.148WWE to ROM 1.06.116WWE)
The updating is only for Swedish sold Qtek S100 with software version 1.03.148WWE. In order to check which version you have pressures Start>Settings>System>Device information, you find the information on ExtROM version. If you try to update with another version of software can the to damage your Qtek S100.
The updating ROM 1.06.116WWE contains:
GSM-radio software
MMS client (2.0.0.20)
Caller IDS
Phone PAD Swedish T9
Updated Blåtandsmjukvara
Installationsguide ROM 1.06.116
actually it was pretty clear that qtek only offers their support to their respective customers. Nevertheless it should be quite possible to gain advantages out of an alien fw ;-)
...so it could not be used for I-mate JAM and other models.... :roll: If someone has updated the firmware pls report the "improvements"...
Regards,
Primoz
Yes and please send us (or push it on the FTP) the content of ExtROM.
Thanks !
taron said:
Yes and please send us (or push it on the FTP) the content of ExtROM.
Thanks !
Click to expand...
Click to collapse
That would be very nice!
Regards,
Primoz
Anyone upgraded yet?
Hi, has anybody yet tried out the new QTEK ROM 1.06? If so, could you be so kind to make a ROM image and put it onto the ftp? Guess that'll be way easier than finding out some passwords to change the update-files?
thank you!
Why couldnt this be installed on non-swedish qtek s100?
Seems like an normal english rom-update
Wonder what it is with the bluetooth.
Cause the stack that is installed now is way to slow.
We need the passwords so xda3nbftool can be used to change operator id. Then we get past the Country id error...
So if anybody know the passwords that would be nice...
it cant be used out-of-the-box because the upgrade tools checks for your device-id, the carrier-id (which must be the one of qtek), the language (which, as you've said would fit) and the rom versions.
Thus, at least the carrier id would be different which is enough for the upgrade prog to abort. So there are 2 work-arounds:
1.) using xda3nbf-tool which requires the rom-passwords to decode the rom, change the parameters which are checked and re-encode the rom. Unfortunately anybody knows the passwords yet
2.) do a rom backup of a succesfully upgraded qtek-device with the bootloader-method which gives you *one* file that contains all the radio, the ext-rom and the os rom. This file needs to be modified by a hex-editor (which actually means to replace the first 412 bytes from the qtek-backup with the first byte of your own backup) --> restore the edited file et voilà: it should work. Unfortunatly anybody has posted such a backup yet...
conclusion:
way 2) is easier (at least we dont need any passkeys) nevertheless we still need that backup...
regards,
André
sorry, my upload was broken... should be ok now. the file is called MA_Qtek(BrPt)_10600_116_10500_SHIP.zip and you can find it in the Magician folder on the xda-ftp. it's basically just the unpacked installer.
could anybody tell me how to write a proper .bat file, like the one pinoo did for the i-mate rom? i suppose i need to change the 0x20040522... numbers to stop the installer giving the "invalid checksum" error?
...and reading the last post these numbers seems to be the passwords Guest was talking about...
any chance of getting them?
Be careful with this ROM. I tried to install it and now my Compact is dead . I can't reflash it anymore even from SD card. Tried everything and now it is in service-center. They are triing to fix it but still with no success ((
BTW you can install Radio ROM without any passwords and xda3nbf. Just remove all other .nbf files from directory and run update - and everything is OK without any mistakes. Problems appears after other upgrades (nb and mk_).
landau said:
BTW you can install Radio ROM without any passwords and xda3nbf. Just remove all other .nbf files from directory and run update - and everything is OK without any mistakes. Problems appears after other upgrades (nb and mk_).
Click to expand...
Click to collapse
Just upgraded my Imate Jam radio stack to this one and seems that it improved phone sound quality a lot or am I just hoping so ?!
However no problems with upgrading the radio stack only!
Hello,
landau said:
Be careful with this ROM. I tried to install it and now my Compact is dead . I can't reflash it anymore even from SD card. Tried everything and now it is in service-center. They are triing to fix it but still with no success ((
Click to expand...
Click to collapse
Hope you can solve your Magician problem. Which file did you use to upgrade your PPC: MA_Qtek(BrPt)_10600_116_10500_SHIP.exe or MA_DANG_WWE_10600_115_10500_SHIP.exe.
Thanks
macrinus said:
Hope you can solve your Magician problem. Which file did you use to upgrade your PPC: MA_Qtek(BrPt)_10600_116_10500_SHIP.exe or MA_DANG_WWE_10600_115_10500_SHIP.exe.
Thanks
Click to expand...
Click to collapse
MA_Qtek(BrPt)_10600_116_10500_SHIP.exe
Seems like T-Mobile have brought out their second maintanance release, supposedly including blackberry (jumps up and down, then realises blackberry is overhyped and overpriced).
Downloading it now from
http://t-mobile.iris-global.com/download_manager_mda_com.html
From the filename it appears the radio stack is still at 1.12, but I'll check once it's on.
Apologies if this is old news but I couldn't find any reference to it so far.
Technology hates me
Computer decided to reboot during ROM flash, feck knows why. Luckily it seems the TMO upgrade utility can restart its flashing procedure even though connection was lost.
Don't mind computer problems if they got some kind of sense to them, but randomly just restarting for the first time since I built it during the most ackward time just proves to me that computers are both evil and have a since of twisted irony.
Any improvement
Any improvement in this release?
I have been using the May update (BigStorage applied) since July fairly successfully.
I don't want to go through this if it's not worth it, so would appreciate advice from anyone who has applied it first.
Thanks
Well it's now got Blackberry support, whoopty f***in do. Also the radio version is still 1.12 so that has to be updated seperatly. In the 15min its been alive I havn't noticed any major changes but never really expected to.
Will post if I experience any problems or notice anything lifechangingly amazing about this new ROM. Would be nice if people using this ROM could do the same.
BTW anybody got a list of the ExtROM files and their comparitve uselessness? I went through the 1.12 ROM with a CAB manager but really can't be arsed this time round. Probably just install the whole lot through shear laziness. On second thoughts the BB client takes up 1.3Mb, so like f**k am i letting that onto my baby.
Hi Herman,
Why not go for BigStorage as you're not using the ext-rom. In the upgrade to radio 1.13 you can find how to do it from the shipped rom & on the ftp there's a bs 1.13 rom present, based on the Dutch TMO version so WWE, but use your own ext-rom files for specific UK settings.
Cheers, M
Cheers
Sorry, didn't really put it right. Already had the 1.13 radio downloaded and just installed it after, was no worries there. As for the BigStorage ROM, I've never particularly liked the idea, especially after reading problems people have had reverting back to the old storage configuration. I'm quite happy with my 512Mb SD card, wouldn't really use the extra space in storage anyway.
Cheers for your thoughts though mate
Ps had the new ROM up and running for few hours now, not noticed any glaring issues apart from that damn lack of BT serial ports issue but thats the radio not the OS ROM.
BigStorage
Finally gave in and overcame my fears. Applied the BigStorage hack to the latest TMO ROM as I read on here that it's reversible. Well seemed to have gone smoothly, although the increased hard reset time at the begining nearly made my heart stop.
If anyone wants I can upload the latest TMO official ship (1.13) with BigStorage hack, which doesn't need the SD card flashing method. Can do straight over USB.
Just post a msg if you want me to upload.
herman3101 said:
Seems like T-Mobile have brought out their second maintanance release, supposedly including blackberry (jumps up and down, then realises blackberry is overhyped and overpriced).
Downloading it now from
http://t-mobile.iris-global.com/download_manager_mda_com.html
From the filename it appears the radio stack is still at 1.12, but I'll check once it's on.
Apologies if this is old news but I couldn't find any reference to it so far.
Click to expand...
Click to collapse
that doesn't work with my jam ... i still can't figure out how to update my ROM.
Re: BigStorage
herman3101 said:
Finally gave in and overcame my fears. Applied the BigStorage hack to the latest TMO ROM as I read on here that it's reversible. Well seemed to have gone smoothly, although the increased hard reset time at the begining nearly made my heart stop.
If anyone wants I can upload the latest TMO official ship (1.13) with BigStorage hack, which doesn't need the SD card flashing method. Can do straight over USB.
Just post a msg if you want me to upload.
Click to expand...
Click to collapse
i would love to have that...right now im experimenting some of the roms thats available. i would like to give it a try. please upload it here or on the ftp. thanks mate.
One thing, this EXT ROM is 1.13 128 while NL EXT 113 ROM is 131. Which one we should use??
Re: BigStorage
parklife said:
i would love to have that...right now im experimenting some of the roms thats available. i would like to give it a try. please upload it here or on the ftp. thanks mate.
Click to expand...
Click to collapse
Hi parklife,
Still strugling to get it done? I gues herman3101 will upload a modified nk.nbf. Hope you succeed with it. At least I did with a patched nk.nbf. Can't upload myself for a few days as I'm not in the neighborhood of my PC. It's just me & my magician and I'm not complaining.
Cheers, M
Uploading now
Well I'm uploading the ROM up to the ftp now. I've included the updated nk.nbf as well as all the files needed to do a USB install. The files were small enough for me to think well why not. Once that's been uploaded I'll check the download section and find a link for you all.
Further to the guy who couldn't update his ROM, being kinda vague there buddy but I'll see what I can do. If you would be so kind as to follow these instructions pretty much to the letter then we should be OK:
- Hard Reset your MDA (press power button at same time as reset)
- After the selecting your time zone do a soft reset to avoid the customization process
- Plug your fresh MDA into your USB and wait for ActiveSync to bring up the connection wizard, select Guest partnership
- With your MDA still plugged in but in Guest mode just double click on the file you downloaded of T-Mobile and follow the onscreen instructions.
If you still have problems after following those steps then don't hesitate to reply but please be more specific so we don't have to guess what your issue is.
Will post a message when the BS ROM is up on the ftp
PS Well with the BigStorage ROM it obviously doesn't matter which ExtROM, but I would always go for the one from your provider so if you are with T-Mobile UK then go for their ExtROM because your guarenteed compatibility
Link to the ROM
ftp://xda:[email protected]/Uploads/Magician/WWE_TMO_1.13 Official Release with BS.zip
ftp://xda:[email protected]/Uploads/Magician/
The first is a direct link which probably won't wok because of the way I named the file and the second is a link to the folder which it is in.
I have to be honest I have no idea how to move this ROM into it's appropriate folder under Magician/BigStorage ROMs but o well. You'll find it where I've specified.
BTW the file attached is a list of my interpretations of what the 1.13 ExtROM files do. By no means conclusive or correct, its just what I've noticed them do during a stage by stage install and looking for clues inside the cabs.
herman3101,
Album & camera are bundled in the cab. That's the only flaw I noticed in your nice description.
Probably a moderator will move your file to the download section. Guess that's what happened to my BS rom as well. Thanks for uploading your files. It takes me ages to upload those files with my magician.
Good work & seems you're right on my track with decisions making for BS. Only I messed my first try completely and that's something I'm not wishing to anyone. Just waiting for the first hard-reset to finish is enough I think.
Regards, M
Re: BigStorage
oltp said:
Hi parklife,
Still strugling to get it done? I gues herman3101 will upload a modified nk.nbf. Hope you succeed with it. At least I did with a patched nk.nbf. Can't upload myself for a few days as I'm not in the neighborhood of my PC. It's just me & my magician and I'm not complaining.
Cheers, M
Click to expand...
Click to collapse
oltp, i tried your ROM, everything works fine, but it seems the clock stuck on 24 hour format, usually i can change it into 12 format just like i want it, but the Dutch ROM seems did not offer 12 hour format. But i trully appriciate your time and effort fot uploading the ROM
thanks oltp.
Re: Uploading now
herman3101 said:
- Hard Reset your MDA (press power button at same time as reset)
- After the selecting your time zone do a soft reset to avoid the customization process
- Plug your fresh MDA into your USB and wait for ActiveSync to bring up the connection wizard, select Guest partnership
- With your MDA still plugged in but in Guest mode just double click on the file you downloaded of T-Mobile and follow the onscreen instructions.
Click to expand...
Click to collapse
hey herman, thanks for the upload, i got it to work on my M500. But i would like to add something on the set up. You need to do some extra steps to avoid the the ID ERROR 120. Ok here ya go:
-Extract the rom
-edit the RUU.conf with notepad, add [CHECKCEID_TYPE]=1 on the top
-copy MaUpgradeUt_noID.exe from ftp to the extract folder
-press power, camera and rest on your magician
-plug the magician to the USB
-AND execute the MaUpgradeUt_noID.exe
-follow instuction
I waited for 4 minutes till i got my welcome mode.
for more info go check on the ampda how to's pdf file
thanks for herman3101, oltp, and ampda, now i have the perfect rom that i will keep for some time.
Hey Parklife,
Glad you finally made it. Don't think the Dutch rom is any different from the UK rom, both are 1.13 WWE TMO. Except for the ext-rom ofcourse. Managed to get my time on 'h:mm am' too with the english (us) region.
Good thing is that everyone can choose of three methods, to get this BS rom, whichever way they're feeling most comfortable ith and that has been different before.
Cheers to all of you.
Re: Uploading now
parklife said:
hey herman, thanks for the upload, i got it to work on my M500. But i would like to add something on the set up. You need to do some extra steps to avoid the the ID ERROR 120. Ok here ya go:
Click to expand...
Click to collapse
Cheers for complementing the post, didn't include it because my MDA is from TMO UK so I don't need to do that step.
PS I've been running the ROM for a little while now and it seems as stable as ever
hey, one more question for you guys...after i install the Camera_Wizard_Magician_T-Mobile_WWE_RC28_Customize.CAB, my magician clock changed into 24 hours clock format. I tried to change it into 12 hours format on regional setting - date like oltp said, but could not change it back to the 12 hours format...have you guys had the same problem? no biggies, i just not use to the format.
Parklife,
I noticed that the clock changes only after I alter the 'time style' on the time tab (sample changes immediately) go to another tab and then touch the clock on my programbar. Changing the region seems not necessary. Yesterday I fiddled a bit with the settings, now I used a more structural approach.
Cheers, M
... since this problem is bugging us with aku3.x and crossbow roms.
Especially with the crossbow rom, this seems to be the only problem. The other issues are already fixed, or are easy to get fixed (since they have already been fixed in earlier roms).
In addition to this, I think that if we work together we have greater chances of solving this frustrating issue.
So this is what I have tried (with no success):
1) replace the battdrv.dll with one from a prophet
I get the common result where the device will charge only when you softreset with the cable inserted. You also get a square in the "Model No" in device information (Module address conflict?) Someone solved the square issue in an aku 3.x rom. I would like to know how it was fixed.
2) replace the battdrv.dll with one from an HTC artemis
No charging/status indication. Model No is reported as "WIZA200"
3) I unloaded camera and keyboard driver to see if there are any conflicts with them - no difference
andrew_sh said:
... since this problem is bugging us with aku3.x and crossbow roms.
Click to expand...
Click to collapse
A possible way is to write a wrapper for the batterydriver, which logs information and try finding the differences in pnp, etc.. between a working rom and a non working rom with the prophet-driver.
You could try following too:
- don't touch the batterydriver in original aku3-rom
- do following while device finished boot and os is running:
- copy battdrvr.dll from prophet and rename it to \windows\battdrvr_New.dll (into the new rom)
- change the registry-value HKLM\Drivers\BuiltIn\Battery\Dll = battdrvr_New.dll
- wait some minutes and do a softreset
-->it will not survive a hard-reset, but i guess this could solve module-overlapps..
hope this helps,
ikarus
ikarus said:
A possible way is to write a wrapper for the batterydriver, which logs information and try finding the differences in pnp, etc.. between a working rom and a non working rom with the prophet-driver.
You could try following too:
- don't touch the batterydriver in original aku3-rom
- do following while device finished boot and os is running:
- copy battdrvr.dll from prophet and rename it to \windows\battdrvr_New.dll (into the new rom)
- change the registry-value HKLM\Drivers\BuiltIn\Battery\Dll = battdrvr_New.dll
- wait some minutes and do a softreset
-->it will not survive a hard-reset, but i guess this could solve module-overlapps..
hope this helps,
ikarus
Click to expand...
Click to collapse
Thanks for the info.
I just tried it.
Result:
I get the square in the device info.
No charging/no battery status.
Strange isn't it? I wonder why the model no gets f**d up.
To my knowledge, "usbfn.dll" is involved as well, so maybe you gotta play around with that one as well...
MusicMike said:
To my knowledge, "usbfn.dll" is involved as well, so maybe you gotta play around with that one as well...
Click to expand...
Click to collapse
I tried replacing this file. The result is that activesync stops working completely.
MusicMike said:
To my knowledge, "usbfn.dll" is involved as well, so maybe you gotta play around with that one as well...
Click to expand...
Click to collapse
i do agree.. don't know which dll's, but maybe there are more dll's used for battery..
There is a tool called depends or similar, which can figure this out..
depends is part of free eVC++ (\Program Files\Microsoft eMbedded C++ 4.0\Common\Tools\depends.exe)
ikarus
ikarus said:
i do agree.. don't know which dll's, but maybe there are more dll's used for battery..
There is a tool called depends or similar, which can figure this out..
depends is part of free eVC++ (\Program Files\Microsoft eMbedded C++ 4.0\Common\Tools\depends.exe)
ikarus
Click to expand...
Click to collapse
ahh, thats a handy tool, thanks for the tip !
attached is a cab which could fix this issue.
my contribution to the great work of our rom-cooker
ikarus
ikarus said:
attached is a cab which could fix this issue.
my contribution to the great work of our rom-cooker
ikarus
Click to expand...
Click to collapse
Thanks ikarus, i'll try tomorrow.
So have you tried this? Did you find out what was causing the problem?
andrew_sh said:
So have you tried this?
Click to expand...
Click to collapse
MusicMike tested it, but it needs more testing hehe
andrew_sh said:
Did you find out what was causing the problem?
Click to expand...
Click to collapse
not yet... in part yes, but i don't want to write explanations which could turn out to be wrong...
I'm back, testing it now
Jesterz said:
I'm back, testing it now
Click to expand...
Click to collapse
Welcome back! hehe damn it's been a long time
HELP
okay i have the japnease wm6 rc7 both files its all in jap appantly the battrey issue is fixed and all the other problems can someone help me to convert the language into english and then i can test on my prophet we may have a fully working wm6 rom here guys please need help for final stages.
WM6 100% working on prophet
Hi i just installed wm6 rc7 and i can confirm usb charging and sound all works on prophet flawlesly i need a hero to covert the language into english please can someone help
c3l5o said:
so I was just wondering what does the app change in my phone to make it work... I didn't eve have to soft reset it once...
Click to expand...
Click to collapse
jutley said:
Hi i just installed wm6 rc7 and i can confirm usb charging and sound all works on prophet flawlesly...
Click to expand...
Click to collapse
great. i have some thoughts about the cause, but i don't have an verified explanation for the cause.
Actually i don't have enough time to do more investigation for... So i can explain what the cab is doing.
It's a very slight solution.
The cab creates a notification for the "Notification Broker", which in turn starts XDADev_BatFix.exe each time usb gets connected.
(That is there is no extra thread running, there is no dll loaded, there is no system service running and no extra resource needed. It is almost like before.)
XDADev_BatFix.exe does only set a PowerEvent and exits afterwards.
that's it.
Best regards,
ikarus
anyone sucess pls post...
i'll try tomorrow
ikarus said:
great. i have some thoughts about the cause, but i don't have an verified explanation for the cause.
Actually i don't have enough time to do more investigation for... So i can explain what the cab is doing.
It's a very slight solution.
The cab creates a notification for the "Notification Broker", which in turn starts XDADev_BatFix.exe each time usb gets connected.
(That is there is no extra thread running, there is no dll loaded, there is no system service running and no extra resource needed. It is almost like before.)
XDADev_BatFix.exe does only set a PowerEvent and exits afterwards.
that's it.
Best regards,
ikarus
Click to expand...
Click to collapse
Ok thanks ikarus! Really is a smart and slight solution
guitarz said:
anyone sucess pls post...
i'll try tomorrow
Click to expand...
Click to collapse
It IS working indeed
This fix tested and working on Qtek S200! Its one of the 2,2 clean roms from a few months ago. The battery problem has been my biggest annoyance! Thanks!
I also tried XDADev_BatFix on my 818Pro with AKU3.3-Jester-b1 ROM.
Looks like it really solve the battery charge problem.
Thanks ikarus!
Worked
It Worked on I-mate JamIn, Thanks.
some times the device do not wake up after it sleeps
helloooo,everybody
i used ImgfsTools 2.1rc1 and followed bro Tadzio's introduction to cook my rom based on helmi_c's rom~
everything goes well
after NBMerge, i used dutty's tool to generate the os-new.nbh
and flashed it with pof's KaiserCustomRUUv1
but just 1%,my device rebooted and the KaiserCustomRUUv1 tells:
error 244: INVALID MODEL ID
it was still though i didnt modify anything in 'dump' directory
if i flash helmi_c's rom directly,that would be successful
what's wrong i have done? any tips?
forgive my broken Englsh pls...
REGARDS
Sheng
did you flash HardSPL to your Kaiser first?
heh... I had the exact same problem as yours (invalid model id). Using HTC Rom tool, I forgot to set Kaiser as the target ID for the nbh & it defaulted to hermes (I've since edited the ini file to change this).
yea.
i've got HSPL already and i have flashed the other roms many times, thats no problem.
fortunately that error just made my tytnII reboot and i can enter today screen,nothing change at all.
regards
Sheng
i believe your question was just answerd above and i also take it as SLEUTH getting a kaiser? thats cool man welcome to the new club house
woohyuksheng said:
helloooo,everybody
i used ImgfsTools 2.1rc1 and followed bro Tadzio's introduction to cook my rom based on helmi_c's rom~
everything goes well
after NBMerge, i used dutty's tool to generate the os-new.nbh
and flashed it with pof's KaiserCustomRUUv1
but just 1%,my device rebooted and the KaiserCustomRUUv1 tells:
error 244: INVALID MODEL ID
it was still though i didnt modify anything in 'dump' directory
if i flash helmi_c's rom directly,that would be successful
what's wrong i have done? any tips?
forgive my broken Englsh pls...
REGARDS
Sheng
Click to expand...
Click to collapse
Better than dutty's NBH tool, get the Dark Simpsons tool here with Kaiser support...
http://forum.xda-developers.com/showthread.php?t=311909
Cheers.
austinsnyc said:
i believe your question was just answerd above and i also take it as SLEUTH getting a kaiser? thats cool man welcome to the new club house
Click to expand...
Click to collapse
Thanks.... the Hermes was getting too reliable (boring)
Seems thats also now the case with the Kaisers lol... Tazdio's tools work great now after about 2 weeks of flashing roms that didnt work lol...
Oh I dunno... that pesky gps acquisition bug needs fixing and the PIE scroll freeze issue is a cooked in only patch so far. Tadzio is going to send me an updated toolset too itnf hopefully.... I'm itching to flash up a quick personal version with reghacks/PIE fix & maybe a different External GPS app. I may even adapt the hermes GPS RIL shim to express the Kaiser GPS on COM7 so the hermes external GPS applet can handle it.
so that scroll freeze issue in PIE doesn't just happen to me?! what a freakin relief!!!!
It's a real PITA for sure.... I've tried to make a cab to fix it but my initial attempt trashed my phone's RIL for some reason. I'll look at the dependencies more soon...
I have extracted and packed the ezinput files from WWE Asia ROM, which has Chinese input support. I did this in preparation for my custom ROM flash, since most, if not all, of the cooked ROM are based on Europe/UK WWE and therefore the cooked ezinput would not have the Chinese support.
I've yet to try this on any cooked ROM, so if anybody can try and see if this works I would be most appreciated
NOTE: I've taken down the CAB because it's not working so it's back to drawing board for me.
http://www.4shared.com/file/188803152/4fc9335c/dZenKinZ_ezInput__with_Chinese.html
zenkinz said:
I have extracted and packed the ezinput files from WWE Asia ROM, which has Chinese input support. I did this in preparation for my custom ROM flash, since most, if not all, of the cooked ROM are based on Europe/UK WWE and therefore the cooked ezinput would not have the Chinese support.
I've yet to try this on any cooked ROM, so if anybody can try and see if this works I would be most appreciated
NOTE: I've taken down the CAB because it's not working so it's back to drawing board for me.
http://www.4shared.com/file/188803152/4fc9335c/dZenKinZ_ezInput__with_Chinese.html
Click to expand...
Click to collapse
Bro , i hope you can make this work , cause i think most of the ppl will be much appreciate !!! Keep it up .
buddy, i need it.
hope we can figure out and make a CAB for it.
good luck lol
zenkinz, no hurry.
Being waiting for it.
zenkinz said:
I have extracted and packed the ezinput files from WWE Asia ROM, which has Chinese input support. I did this in preparation for my custom ROM flash, since most, if not all, of the cooked ROM are based on Europe/UK WWE and therefore the cooked ezinput would not have the Chinese support.
I've yet to try this on any cooked ROM, so if anybody can try and see if this works I would be most appreciated
NOTE: I've taken down the CAB because it's not working so it's back to drawing board for me.
http://www.4shared.com/file/188803152/4fc9335c/dZenKinZ_ezInput__with_Chinese.html
Click to expand...
Click to collapse
I've just looking for this! Can anyone please help!
zenkinz said:
I have extracted and packed the ezinput files from WWE Asia ROM, which has Chinese input support. I did this in preparation for my custom ROM flash, since most, if not all, of the cooked ROM are based on Europe/UK WWE and therefore the cooked ezinput would not have the Chinese support.
I've yet to try this on any cooked ROM, so if anybody can try and see if this works I would be most appreciated
NOTE: I've taken down the CAB because it's not working so it's back to drawing board for me.
http://www.4shared.com/file/188803152/4fc9335c/dZenKinZ_ezInput__with_Chinese.html
Click to expand...
Click to collapse
I've been looking for it for a long long time ago...
but i cant find any workable CAB of it.
so thats why i still keep my LEO as default 1.48 ROM..
and now, Thanks for your hard working,
I can try the newest 2.01 ROM.
I *think* I might have found the problem but I need to flash a custom ROM to test it. If anybody is game to try it on their custom ROM, please pm me your email address and I'll send you the CAB. The reason why I'm not publishing it here is because it might cause you to hard reset your phone if it didn't work out (as happen to one of the 'early adopter' user)
zenkinz said:
I *think* I might have found the problem but I need to flash a custom ROM to test it. If anybody is game to try it on their custom ROM, please pm me your email address and I'll send you the CAB. The reason why I'm not publishing it here is because it might cause you to hard reset your phone if it didn't work out (as happen to one of the 'early adopter' user)
Click to expand...
Click to collapse
I'm looking for a RIGHT ROM to try.
I'll let your know when i'm ready.
ok, I'm trying a second time. The CAB can be downloaded from here
WARNING: uniinstalling this CAB might require your device to be hard reset. I suspect it's because of the default SIP being removed when the CAB is being uninstalled. But I don't have a custom ROM to test, so if you don't mind the risk, I would appreciate your help in testing.
zenkinz said:
ok, I'm trying a second time. The CAB can be downloaded from here
WARNING: uniinstalling this CAB might require your device to be hard reset. I suspect it's because of the default SIP being removed when the CAB is being uninstalled. But I don't have a custom ROM to test, so if you don't mind the risk, I would appreciate your help in testing.
Click to expand...
Click to collapse
I volunteer to try your cab, and report back soon!
I've tried it, but it didn't work. when inputting sms contact names, no name suggestions available. and the Pin Yin didn't work at all. And when I tried to uninstall and reset the device, the whole device couldn't boot, I was forced to hard reset my HD2.
precsmo said:
I've tried it, but it didn't work. when inputting sms contact names, no name suggestions available. and the Pin Yin didn't work at all. And when I tried to uninstall and reset the device, the whole device couldn't boot, I was forced to hard reset my HD2.
Click to expand...
Click to collapse
I was having the same problem as well . Hope there will be a refine version .
zenkinz said:
ok, I'm trying a second time. The CAB can be downloaded from here
WARNING: uniinstalling this CAB might require your device to be hard reset. I suspect it's because of the default SIP being removed when the CAB is being uninstalled. But I don't have a custom ROM to test, so if you don't mind the risk, I would appreciate your help in testing.
Click to expand...
Click to collapse
I tried it on PDAVIET V05 28014
I can call it out but the hand writing does not show the line when you draw on the screen, when using the 筆畫 it just show the E T U D G instead of chinese.
ok so it looks like I really have to use a custom ROM to test myself, as my fear is that the existing registry in the pure english rom conflicts with the CAB.
this will take awhile unless somebody adventurous could trace the original ezinput registry and identify any potential conflict to the chinese input. (but doing so will also mean you will need to hard reset ur device after the troubleshooting)
Hi, zenkinz
Thanks for your effort.
Can you create a tutial or CAB for LEO custom ROMs (like Dutty's, Xanny's ......) to add Asia support? (just capable of viewing, not UI localized)
You can try to analyse the cabs from Lingvosoft, as they offer asia input keyboards.
I am using their Japanese Keyboard. This will show up the keyboard.
But the keyboard alone is not enough, you need copy a chinese font from your desktop windows to the windows\fonts folder on your Leo.
Then you will have to change the standard font in HTC manilla or Windows 6.5 if you want to be able to display the characters in the main applications (unless that application offers font selection).
I have attached the Chinese and Japanese keyboard cabs, as well as the Chinese font (ming true type font). Those are from the trial version of their translation suit, but I think the keyboards don't require a license (except for use in the translation application, then they get barred).
zenkinz said:
ok so it looks like I really have to use a custom ROM to test myself, as my fear is that the existing registry in the pure english rom conflicts with the CAB.
this will take awhile unless somebody adventurous could trace the original ezinput registry and identify any potential conflict to the chinese input. (but doing so will also mean you will need to hard reset ur device after the troubleshooting)
Click to expand...
Click to collapse
sorry to say that my voluntary offer ends there. The problem is if there is a problem, I cannot uninstall it and revert to previous state, and also, worse is, the entire rom couldn't start. I can't take too much trouble to try it unless it can be reverted easily.
precsmo said:
sorry to say that my voluntary offer ends there. The problem is if there is a problem, I cannot uninstall it and revert to previous state, and also, worse is, the entire rom couldn't start. I can't take too much trouble to try it unless it can be reverted easily.
Click to expand...
Click to collapse
the following file is come from one Taiwan WM site,
anyone if have interest, can try it out.
seem that someone work fine with the file.
http://www.badongo.com/file/18581778
if you can read chinese, you can check with the following link,
also discussing about the Touch Input 2.0
http://www.mobile01.com/topicdetail.php?f=129&t=1317192&last=16027178
cmant said:
the following file is come from one Taiwan WM site,
anyone if have interest, can try it out.
seem that someone work fine with the file.
http://www.badongo.com/file/18581778
if you can read chinese, you can check with the following link,
also discussing about the Touch Input 2.0
http://www.mobile01.com/topicdetail.php?f=129&t=1317192&last=16027178
Click to expand...
Click to collapse
thanks for the link. From the thread, it looks like the thread start has the same problem as us, I will read further to see what's the missing dll/registry.