In all the excitement of the hacked ROM coming out - I need to ask one question. Why should I upgrade my BA to the WM5 ROM? What benefits does it offer over the existing WM2003SE ROMS?
I'm tempted like everyone else just to bung it on and update it every day for the next few weeks until it's working properly - I'm also tempted to wait for the official O2 1.4 ROM that works properly.
I must admit that I'm going to wait before upgrading to WM5. I see no compelling reason to upgrade other than "beacuse I can". I wouldn't necessarily wait for the official O2 1.40 ROMs though, you might be waiting forever. I use the imate 1.40 ROMs with no problems.
Having said that, I hope to get hold of a "spare" Blue Angel this week & might experiment with WM5 on it
The existing 1.4 ROMs are annoying for me because I have problems with GPRS and disconnections and a few other niggles that are hard to live with - whereas tghe O2 ROMs have these niggles fixed - hence the wait for the O2 1.4 ROM.
I was thinking of tinkering with the WM5 ROM, but not for a little while until a few things are sorted out, just to see what the interface was like but if it's too much hassle.....
I've got my heart set on an O2 Exec which looks like it might be out soon.
I use it and apart from lack of camera function and a longer boot up time, I MUCH prefer it over 2003SE. First it has a revamped design and it makes 2k3se looks boring.
OK, there are some stability issues but what can you expect for a leaked rom?
If you don't vitally depend on your BA i'd give it a try, and if you don't like it, get activesync 4 and flash back.
Now, seeing how we came accross WM5, is there reason to believe we will be getting the FINAL version of the WM5 firmware for the BA??
In other words, is Mamaich's patched WM5 version the best we're going to get??
What do y'all think?
man(darkblak) is askins simple...if someone knows what benefits gets with wm5...if someone had experience should tell us...im interested in that to... will be blueangel with wm5 faster or slower how will be in performances and itc...
10x in advance
WM5 on SX66 (Blue Angel)
I updated my SX66 to WM5 before the ROM was patched (by Mamaich)... and then spent the next few days working on the issues of performance/sound.
With sound disabled (prior to patch), the device was undoubtedly faster. I made registry changes to increase cache size, disable animations, etc. but I had made those changes in 2003SE as well... and WM5 still outperformed it by a significant margin.
As for the areas not dealing with speed/performance, the new OS requires some getting used to. Hardware buttons that are unassignable (old Windows and OK buttons are softkeys now) and a few other issues (such as GPRS on only when activated by Internet Explorer and Bluetooth shutdown on power off) were a little unnerving, but nothing that would make the OS unusable.
What makes WM5 indispensable is PERSISTENT STORAGE. This is the Holy Grail for all Windows Mobile devices prior to this OS. When your battery dies and your backup battery dies, you must re-load all of your aftermarket software and PIM info. Software such as Sprite Backup made this process easy... but what if you're mid-flight to another country without a laptop and your PDA crashes? This is not an issue with WM5. All after-market software and PIM data is stored to ROM (software install location is optional)... which means that it is stored in non-volatile memory. It is not lost during power/system failure. What this means in terms of device security is that the person that finds your PDA on your desk at work cannot simply "hard reset" it to remove all of your info and use it themselves... Your password/PIM data and software will still be secure/in place and only downgrading the device to 2003 and repartitioning the ROM will clear it.
At the moment, I have no issues with WM5 on my SX66. Editing the camera keys in the registry solved the issues with sound and there are plenty of patches available to reconfigure the hardware buttons, etc. But I'm learning to like the OS as shipped...
I've been using Windows Mobile for more than three years and this iteration is undoubtedly worth the upgrade. If you have the time and patience to read through these forums, make an installation checklist and then follow it to do the upgrade.
My checklist would read:
-Download patched WM2005 ROM
-Download MaUpgradeUT_NoID.exe
-Download all patch CABS
-Download DOC tool (Disk On Chip partition tool)
-Run DOC tool (if successful, the ROM size is now ~63MB in control panel)
-Copy and rename the HTCRUU.dll and HTCRUU.conf files to RUU.dll and RUU.conf
-Run MaUpgradeUT_NoID.exe (if the first try is unsuccessful, put device into bootloader mode. Rec/Media/Power/Reset all at once)
-After upgrade check functionality BEFORE applying any patches, there are as many differences between just SX66's as there are between all of the Blue Angel devices... some patches may NOT be required.
-Apply patch CAB's
-Apply registry edits suggested in the forums for performance improvement
I hope this enlightens those waiting to see the efficacy of this ROM upgrade. I have had a good experience with WM5, in spite of the initial problems. I'm happy with its performance and will not downgrade to 2003SE unless I screw up WM5 bad enough to make it necessary to re-partition the ROM... then I'll go right back to WM5.
Cheers all...
MRwheeler2: Where is the edited rom on the FTP site? I cannot find it where it says it was, BA/test or something like that. Where can I get it from
Also, I have noticed that using the standard rom I cannot change bootup images. It is constantly the stupid colour thing (how about that for a name!) and it's more like a TV test screen.
Download locations for patched ROM
Sorry for the delay... I was out.
You can download the patched ROM from: ftp://xda-developers.com/Uploads/Blueangel/WM5Pack/
There currentyly isn't a fix for the boot screen... I'm looking right now at the MSDN site for CE5.0 and searching their registry settings for Bluetooth and boot screen. Nothing yet... I'll post a new thread if I figure it out.
Hope this helps...
any reason that I'm getting permission denied errors?
I'm logged in but can't do it withe IE or FF, and firewall on or off.
One says permission denied, the other says can't find.
Download locations for patched ROM... continued.
Looks as if it was moved... Try the BlueAngel/BA_WM5/Shipped_Extracted_Updates folder and look for WM5_pack_v1.rar
That should do it...
Good luck.
Still says 530 permission denied. I tried looking in some of the higher level folders and still no joy.
Download locations for patched ROM... continued.
A 530 error is an incorrect login... Go to the "File" pull-down in Internet Explorer and click on "Log In" then when prompted, enter xda for both user name and password.
The default setting for Internet Explorer is to log in anonymously... most non-public FTP sites require some type of non-anonymous log in to ensure that the user has been referred from a site and not someone searching FTP servers.
Once you've logged in, you should be able to see a list of folders/files. You can use the "Folders" button if you would like to see a directory tree in the left panel.
Post a reply if you're successful (or if you're not)...
Later,
Mick...
10x mwheeler2 i will hawe that what u write in my mind...but 530 error i hawe still in ftp ... hope that will solve soon...
Download locations for patched ROM... continued.
For those still looking for the patched ROM...
try this:
ftp://xda:[email protected]/BlueAngel/BA_WM5/Shipped_Extracted_Updates/WM5_pack_V1.rar
The above link is on the wiki page for the upgrade:
http://wiki.xda-developers.com/index.php?pagename=BA_5.1.1700_build_14343_Upgrade
There is a walkthrough on the site and some helpful information...
Later,
mick...
Well - after reading all the stories about persistent storage and speed I was about to go ahead with the install until I found out that my main application TomTom 5 would not install - a quick search later found a workaround - seems like everyone is pulling together on this.
So I'm now running WM5 on my O2 XDA IIs and it's not too bad - it's no worse that O2's existing "beta/official" ROM (1.31) and there is very little reason not to go for the upgrade as it's easy to install - just a little hairy with the funny screens at the start.
I can't say that the I have noticed much difference with the speed issues once all my baggage is loaded on the machine. I'll keep checking the reg fixes etc from time to time.
The interface is much the same as the old interface apart from a few nice touches - but as someone said earlier the ability to re-map certain keys is a pain - until you become used to the context sensitive buttons.
All in all - probably worth the upgrade - you just have to get used to the new ways that some things work.
Where can I download the files to update my SX66 to WM5
I did try to search the fourm but can someone please send me the web link to where I can down load the files to upgrade my Cingular/Siemens SX66 to WM5?
Thank you and I have donate to BA***
mwheeler2 said:
I updated my SX66 to WM5 before the ROM was patched (by Mamaich)... and then spent the next few days working on the issues of performance/sound.
With sound disabled (prior to patch), the device was undoubtedly faster. I made registry changes to increase cache size, disable animations, etc. but I had made those changes in 2003SE as well... and WM5 still outperformed it by a significant margin.
As for the areas not dealing with speed/performance, the new OS requires some getting used to. Hardware buttons that are unassignable (old Windows and OK buttons are softkeys now) and a few other issues (such as GPRS on only when activated by Internet Explorer and Bluetooth shutdown on power off) were a little unnerving, but nothing that would make the OS unusable.
What makes WM5 indispensable is PERSISTENT STORAGE. This is the Holy Grail for all Windows Mobile devices prior to this OS. When your battery dies and your backup battery dies, you must re-load all of your aftermarket software and PIM info. Software such as Sprite Backup made this process easy... but what if you're mid-flight to another country without a laptop and your PDA crashes? This is not an issue with WM5. All after-market software and PIM data is stored to ROM (software install location is optional)... which means that it is stored in non-volatile memory. It is not lost during power/system failure. What this means in terms of device security is that the person that finds your PDA on your desk at work cannot simply "hard reset" it to remove all of your info and use it themselves... Your password/PIM data and software will still be secure/in place and only downgrading the device to 2003 and repartitioning the ROM will clear it.
At the moment, I have no issues with WM5 on my SX66. Editing the camera keys in the registry solved the issues with sound and there are plenty of patches available to reconfigure the hardware buttons, etc. But I'm learning to like the OS as shipped...
I've been using Windows Mobile for more than three years and this iteration is undoubtedly worth the upgrade. If you have the time and patience to read through these forums, make an installation checklist and then follow it to do the upgrade.
My checklist would read:
-Download patched WM2005 ROM
-Download MaUpgradeUT_NoID.exe
-Download all patch CABS
-Download DOC tool (Disk On Chip partition tool)
-Run DOC tool (if successful, the ROM size is now ~63MB in control panel)
-Copy and rename the HTCRUU.dll and HTCRUU.conf files to RUU.dll and RUU.conf
-Run MaUpgradeUT_NoID.exe (if the first try is unsuccessful, put device into bootloader mode. Rec/Media/Power/Reset all at once)
-After upgrade check functionality BEFORE applying any patches, there are as many differences between just SX66's as there are between all of the Blue Angel devices... some patches may NOT be required.
-Apply patch CAB's
-Apply registry edits suggested in the forums for performance improvement
I hope this enlightens those waiting to see the efficacy of this ROM upgrade. I have had a good experience with WM5, in spite of the initial problems. I'm happy with its performance and will not downgrade to 2003SE unless I screw up WM5 bad enough to make it necessary to re-partition the ROM... then I'll go right back to WM5.
Cheers all...
Click to expand...
Click to collapse
Related
What you need
A stable radio rom, and id recommend that you skip using the
extended rom for now since there might be programs that is incompatible
with Windows Mobile 2005. So, get a blank extended rom for installing.
Id recommend using the new radio rom from WM2003SE that seems
to be the most stable so far.
To install this, you also need nk.nbf, Patch1.exe to patch nk.nbf to work
with your XDA II (whateverbrand). And you need the update utility.
Summary of files:
Actice Sync 4.0 beta.exe
HimaUpgradeUt.exe
nk.nbf
patch1.exe
"empty" extended rom. ms_nbf
1. Installing Activesync 4 Beta.
- Install ActiveSync 4. Make shure that you can sync with your XDA II
just like it is, with the current Windows Mobile.
- If you run into problems, remove ActiveSync and reinstall.
- If it still wont work, try removing the device driver in windows control
panel - system - device manager. Look for the driver on the error messege.
(have not tested this, but should work if you have driver problems)
2. Going to boot mode.
- Put your XDA II in boot mode, by pressing the direction key left while
holding the off button and then pressing reset button with your stylus.
- It should go black, displaying only a version Nr. Like V 1.03 or V 1.06.
3. Patching nk.nbf.
- Run the Patch1.exe to fix the nk.nbf for your XDA II.
- Now run the WM2005 update program (HimaUpgradeUt.exe) and follow
onscreen instructions. If it complains about Country ID, download
the tool ER2003Edit.
Link: http://wiki.xda-developers.com/index.php?pagename=ER2003Edit
Make shure you do as it says on the info page on this, so that you wont
change anything you shouldnt change!
When in boot mode, the thing to edit should normally be the brand name.
So set it to the brand on your XDA II.
4. Finishing up!
-When it is done, just reset your device and you all set.
5. About WM2005 bugs and stops.
- The new operating system handles memory differently, so you cant
install the programs in the default directory because of low memory install
it to the Storage Card (SD), in Active Sync 4.0 you can not chose this, but
you will be prompted on the device after install of a program.
- Some programs that have _not_ been rewritten into WM2003SE does
not work, and will likely to crash on WM2005.
That is mainly directed to programs that have heavy multimedia demands,
or rewrites the screen graphics.
- Be aware that bad SD card may slow down the system
extremely! But if that is the problem, i promise you will notice!
Skinning programs is to forget directly, i have not found a single program
that works.
- Pocketbreeze have problems updating on the Today screen, i do not
know if that is because of the new database system or if it is a new today
screen code. Also, contactbreeze does not work at all, seems like the
database for handling contacts is all new.
Good news!
Bluetooth works perfecly, and syncing is flawless, its faster and seems
more stable. (i will write more good things later, have to go eat now)
Hi folks, sorry for this question, but I couldn't find what I was looking for ...:
I upgraded my BA PH20B to 1.42 WWE and the Radio to 1.15.00.
But I struggled with the upload of the EXT_ROM - the ms.nbf file, because at this time I didn't probably format a reasonable size for the Extended Rom (at least, this is my understanding of the situation as of now).
But since a couple of weeks I work fine with my MDAIII/BA.
There are only minor concerns, for example with the mail client from WebIS, Flexmail I'm running in an issue, which is a k.o. for using Flexmail: After having connected once via GPRS to the Internet, there is no way to reestablish the GPRS connection an other time.
I got an answer/hint from a member of the webis community, I should use an other caller id program, which is part of the Extended ROM.
Because I didn't install the EXT_ROM, I'm sceptical about the outcome, my device seems to be reasonable stable (but very often I can't answer a call, which happened also before rather frequently!) and I would prefer not to touch it at all. Never touch a running system worked for me very well ;-)
Therefor three questions:
1) Because I don't use the EXT_ROM so far I'm now curious, whether I should follow his advice and if yes,
2) how to upload it, so using the format utility of the extended room toolkit and unhiding/unlocking the directory - is this all I need to do to succeed - or I would prefer just to install this callerid.exe file, but I don't know how to do that and
3) which EXT-ROM should I use?
Thanks,
Alexander
Hello, everyone, I hope no piss anyone about this old OS, but I have no choice on my iPAQ Rx3115 'cause HP never releases an OS update for this pda, since it has decent features and mine is in perfect shape and it's a shame that a lot of programs cant be installed in this OS.
So, that's why i want to edit the ROM of this PDA, made a custom one with new programs and delete the old ones and the ones that are obsolete (like the MPG player, since tcmp and coreplayer cant play everything).
This forum is big, i was searching for hour about resources and "how to do that", I use EM2003 and when i try to open the rom file it tells me that enter a password to unlock the ROM.
So pleasse guys, help me out, I want to guive a full new life to this PDA and keep using it, and of course I will release the ROM for everyone to use it as I made stable ROMs.
Thanks and regards.
c'mon guys, help me a little, a need something to start with, a tool, program, anything?
thanks
I know this is old but I'd just like to second this, if anyone has any info on how to upgrade this device that would be great as I just sort of "stumbled upon" one of these and would like to put it to good use.
I've done a lot of searching and can't find any roms for rx3115 IPAC. I have one of these too and would love to fiddle with it again!! I even found on forum that said that it would not support WM 5 or 6 so I don't now if there is much hope. But if there was a program or instructions on how to make our own ROM I would sure like to try!!! I believe it has WM 2003 CE on it now...
Me too!!! I too have one of those...
rx3115
I have an rx3115 also. I am following this thread.
This will be quite difficult and complicated, first of all, what do you want to do with stock ROM? If some apps can't be installed on WM2003SE, then adding them to ROM won't change anything. However, I'm willing to help, send me a PM with stock ROM and changes you want, I'll try to develop somethin' good .
Thanks tomcug!!!
I'll also PM you the links from this post.
I too have an rx3115 and have been searching all over for ways to upgrade it: cooked ROMs, Linux, Unix... SOMEthing. LOL
So far you're the only cook who's wanted to take a swing at this. There are no easy answers for rx3115 that I can find anywhere on the net.
Here's the last official rx3115 update of WM2003 (1.01.11) complete with installer
http://www.mediafire.com/file/i6k0935chhkgzlh/iPAQ rx3115 ROM 1_01_11.exe
I'd hate to lose the Nevo (IrDA universal remote control) from it, but would sacrifice that if I could upgrade the OS...
Better yet - maybe you could work with this WM 6.1 Classic ROM that was cooked for the rx1950. It supports the ARMv4T instruction set used by the rx3115. Here is just the .nbf file
http://www.mediafire.com/file/iu9p815w3yjpy6h/CEOS.nbf
At 27.82mb it would just fit on rx3115. Maybe a slimmed down version??? I would leave it to you to decide what to remove. LOL who am I to tell a cook how to season his offering???
And the WM 6.1 install cab for Mobile Office
http://www.mediafire.com/file/nmz3sbyuxan7c4e/office_wpc_WM6.CAB
Of course - any help would be greatly appreciated by many rx3115 owners.
And here's my thread of what I've been trying to accomplish with my rx3115.
http://forum.xda-developers.com/showthread.php?t=981868
Thanks Again,
RumoredNow
All right, then I'll try to do something good . I don't know if this will work and that's why I need to ask you one more thing. Is it possible to flash this phone when it's not booting? I mean windows hangs.
It's a straight Pocket PC with no Phone capability. Full specs are here:
http://www.pdadb.net/index.php?m=specs&id=122&view=1&c=hewlett-packard_ipaq_rx3115
Short answer: yes, the ROM is user flashable up to 28mb of 32mb total.
Long Answer...
The HP update I sent you will flash the ROM under Win XP with ActiveSync installed. The RUU (ROM Update Utility) needs RAPI.dll from ActiveSync in order to run. It won't function under Win 7 for me - it generates a comm error.
Theoretically it is possible to flash any (size appropriate) ROM to the device with this Universal iPAQ Bootloader:
http://sourceforge.net/projects/ubl/files/ubl/Binaries/
My system flagged the UBL as having a Worm in the Vista Drivers though. I can't tell if it is a false positive (I'm not qualified for that) so I didn't use it under Win 7.
Instead, I stripped out the infected(?) bits and tried it on an XP box. Here's that file:
http://www.mediafire.com/file/7anraar1tkc3lz1/BootLoader.rar
It fails to put rx3115 into bootloader mode even though it connects via USB.
There is a manual way to put rx3115 into Bootloader mode: MultiMedia (button 1) + iTask (button 4) + Power + Reset. But every time I put it in Bootloader mode manually, that seems to kill the rx3115's USB port. It becomes invisible to PC... I don't know if there is another step to manually enable USB mode under Bootloader. I haven't been able to find the right button(s) for that so far...
And manually entering Bootloader mode hasn't allowed me to flash from SD card either. I always get a "Wrong Image" error, even with .nbf file from the last official update!!!
I know it's not the device - I can reflash the last update over USB on a Win XP box if I use the official update package.
LOL - an executable which uses HP's RUU would be preferable for technologically deficient users such as myself.
Feel free to PM me or post back here if you have any more questions.
Thanks again.
Well, no progress at the moment and probably there's won't be any progress at all. I don't know how to extract CEOS.nbf, all tools I've tried can't do it.
By extract, do you mean view and edit???
uedit32 (hex editor???) will open it and allow changes to be saved. It even keeps the original version as a backup...
http://www.mediafire.com/file/6r8ffn1fq3bh9mu/uedit32.exe
Making ROM with hex editor ? That would take hundreds of years or even more . What I need is a tool or set of tools that can extract XIP and IMGFS from CEOS.nbf, that's the way you make ROM's. And tools I've tried doesn't work for this phone, however they work for HTC and i-mate phones I own.
EDIT:
I've also tried rx1950 kitchen, but it's a fail too. There are tools there but only for making CEOS.nbf from XIP and IMGFS images, nothing what I need .
Looking for the 802.11g mod for rx3115
I saw an experimental mod somewhere to enable the rx3115 to use 802.11g. If anyone knows where it is, please share. I lost the link. I was looking up the embedded chips at the time I saw it, so I think it was a forum.
All right, making a little update here. After long time of hard work I need to say that it's impossible to make WM 6.5.3 ROM for this device, drives and OEM stuff from WM 2003 SE simply won't work with any newer OS. Sorry for that but there's nothing we can do .
Well, school is out for the summer, so I can focus on putting out roms again. With this release, I made another WM6.5 rom to test a new compression type that I'm working with. With the original stock compression type (XPR), I didn't have enough space to fit all the goodness of WM6.5, so I switched to a new compression type (LZX) that lets me pack in more. I'm curious to know how the new compression type performs in comparison to the old one. Does anyone notice things are faster or slower?
Thanks to Makuu (for helping to get me started), Lenny, AstainHellbring (thank you for all the nightly help sessions), the creators of the tools I used to make this rom, and anyone else that I failed to mention in name who gave me the knowledge to complete this rom.
Asus Mypal A6x6 WM6.5 version 2
Windows CE version 5.2.21892 (Build 21892.5.0.89)
This was tested on an Asus Mypal A626 (and works). It should work with the A686/A696, but the other models were not tested. Any other models not metioned above WILL NOT WORK.
Updates
1. new compression type
2. os build
3. bug fixes
Additions
1. Windows Marketplace
2. File Dialogue Changer
3. MS Office Mobile
4. Remote Desktop Mobile (has been added again)
Removals (you can reinstall these via windows marketplace)
1. Windows Live
Removals (non-Windows Marketplace)
1. PsShutXP
download: http://www.easy-share.com/1910266747/Asus_A6x6_WM65_2.rar
At this time, this will be the only download link. Mirrors will be created in the future (after I give permission).
Instructions (I have included a txt file with same instructions for offline convenience)
Before you do anything, make sure you have at least a 256mb SD card and a card reader (you can get one at a place like Radio Shack or Office Depot). You also need to install winrar (found at http://www.win-rar.com/download.html). Your SD card must be formatted with the FAT16 file system.
To format your SD Card with the FAT16 file system
Step 1: To do this insert the SD Card into the reader and go to "My Computer".
Step 1a: BACKUP YOUR FILES before you start!!
Step 2: Right-click the drive letter of the SD Card reader (differs for each computer, probably either E:\ or F:\ or G:\) and click "Format".
Step 2a: Don't worry about any of the options except for file system, choose "FAT"
Step 3: Click "Start" and wait until it is done
Step 1: Get (OS) rom image
Step 2: Extract files to any folder on hard drive using Winrar
Step 3: Go to the folder where you extracted the files in the RAR archive
Step 4: Make sure that the filename is "CANNES_A_WM6.img"
Step 4a: if the img file it's not exactly "CANNES_A_WM6.img", rename it to that
Step 5: Format the SD card if you haven't already done so using the instructions above
Step 6: Copy the img file to the SD card, see step 6a
Step 6a: Make sure that the img file is the ONLY file on the SD card after formatting
Step 7: Take SD Card out of SD Card reader and put it in the a6x6
Step 8: Make sure that the a6x6 is plugged in via ac adapter before doing the next few steps
Step 9: activate SD Loader using the following instructions {
Step 9a: Hold down the power button and enter button (that's the button in the center of the d-pad)
Step 9b: Double tap the soft reset button while holding the other 2 buttons
Step 9c: After double tapping the soft reset button, keep the other 2 buttons held until a blue screen comes up that says something like Asus Cannes flashing utility
Step 9d: Wait until the process is finished (it's near the end when it says "writing private")
}
Step 10: At this point, your a6x6 should reboot on its own
Step 11: enjoy your updated rom
If you have any questions, feel free to just post or PM me.
As I release new roms, if you have a support question, please give me the rom version so I know what rom you are working with. You can get the rom version from the filename of the rom pack.
Example: Asus_A626_WM614_1
A626 = device (most often it will be A626, will rarely be different), WM614 = os version, 1 = release #
I only added MS Office Mobile this time because the new MS Office Mobile 2010 had not been released yet. For my next release, I am not including MS Office Mobile due to the fact that you can download the new version free from Marketplace.
My work is free for everyone's use, but if you feel compelled to give a donation towards my work (I am a full-time college student working on this in what little spare time I have), my paypal e-mail is "[email protected]"
Steven855 said:
I only added MS Office Mobile this time because the new MS Office Mobile 2010 had not been released yet. For my next release, I am not including MS Office Mobile due to the fact that you can download the new version free from Marketplace.
Click to expand...
Click to collapse
Some indication about free memory after 6.5 rom installation?
If something wrong, is possible to reinstall the official 6.1 rom?
Thanks
Massimo
maxambro said:
Some indication about free memory after 6.5 rom installation?
If something wrong, is possible to reinstall the official 6.1 rom?
Thanks
Massimo
Click to expand...
Click to collapse
Nothing is wrong with the rom. I would just like to find out if people notice a performance impact (good or bad) with the new compression type (that is supposed to give you more storage space) that I'm trying out with this rom. Iif there was something very wrong with this rom, I would never release it to the public (ok, perhaps I jumped the gun with the 1st WM6.5 rom, but I did put out warnings and a bug-fix rom to remedy some issues with the 1st rom). And yes, it's possible to downgrade to WM6.1 (just a note, Asus never put out an official WM6.1 stock rom, so I had to make it). The latest stock rom is WM6.
Appropriate to glorify
Steven855 said:
Nothing is wrong with the rom. I would just like to find out if people notice a performance impact (good or bad) with the new compression type (that is supposed to give you more storage space) that I'm trying out with this rom. Iif there was something very wrong with this rom, I would never release it to the public (ok, perhaps I jumped the gun with the 1st WM6.5 rom, but I did put out warnings and a bug-fix rom to remedy some issues with the 1st rom). And yes, it's possible to downgrade to WM6.1 (just a note, Asus never put out an official WM6.1 stock rom, so I had to make it). The latest stock rom is WM6.
Click to expand...
Click to collapse
Thank you so much for extraordinary job on rom ver. 2 !!!
I was intalled this on my ASUS 696 and it went smoothly without any problems.
In addition, it looks more faster as you mentioned beside rom ver. 1.
The current rom taking the sum of 29.53MB from a total of 53.35MB memory (what let us 23.82MB free at the program memory section).
Again you made a really holiness work due to the fact our mypals still relevant...
Steven855 said:
Nothing is wrong with the rom. I would just like to find out if people notice a performance impact (good or bad) with the new compression type (that is supposed to give you more storage space) that I'm trying out with this rom. Iif there was something very wrong with this rom, I would never release it to the public (ok, perhaps I jumped the gun with the 1st WM6.5 rom, but I did put out warnings and a bug-fix rom to remedy some issues with the 1st rom). And yes, it's possible to downgrade to WM6.1 (just a note, Asus never put out an official WM6.1 stock rom, so I had to make it). The latest stock rom is WM6.
Click to expand...
Click to collapse
Installed this ROM today, and performance on my A696 is not so good...
First – after reboot it was stuck on Windows startup screen for 4-5 minutes. I thought the flashing process went wrong, but eventually it booted up.
I haven't tested it thoroughly yet, but the first things I noticed – reaction to any user event (tapping, scrolling, etc.) is MUCH slower than on the WM6.1 I'd had before. Haven't tested the application performance yet.
Also, when I tap on the battery indicator nothing happens.
v.real said:
Installed this ROM today, and performance on my A696 is not so good...
First – after reboot it was stuck on Windows startup screen for 4-5 minutes. I thought the flashing process went wrong, but eventually it booted up.
I haven't tested it thoroughly yet, but the first things I noticed – reaction to any user event (tapping, scrolling, etc.) is MUCH slower than on the WM6.1 I'd had before. Haven't tested the application performance yet.
Also, when I tap on the battery indicator nothing happens.
Click to expand...
Click to collapse
Yeah, I forgot to mention that 1st boot time has increased with this rom. This is due to the new compression type. For the power icon, I just noticed your concern. Unfortunately, I don't have a fix for it right now. You can still view battery information by going into the settings.
If anyone knows how to flash a rom in a different language, please enlighten me. I have made an attempt at making an international rom (this time was German), but I can't get it to boot (I have an English version A626). I think the reason it won't boot is because I didn't configure the firmware right (the os is right though).
ROM working very good so far on my Asus A696. Looking forward to a German version but I could live with the US ROM. Thanks for your hard work.
You could also see battery level by using the ASUS Manager Icon on the Today Screen.
Good job
I would donate, for a Portuguese language rom. Thanks!
Problem with rom 2
Hi Steven,
I noticed in a one small problem of rom 2 after flashed on my asus 696.
The problem is that whenever i push the power button shortly and alternatively i'm trying to push it again to power on, it failes to succeed what leaves me to make an another resets for several times.
Can you resolve this issue during upcoming next rom?
Thanks for your good job!
Was a little slow and less responsive on the first startup, but after a soft reset it worked GREAT!
Once again beautiful work Steven, thank you very much!!!!!
dj.brudo said:
Hi Steven,
I noticed in a one small problem of rom 2 after flashed on my asus 696.
The problem is that whenever i push the power button shortly and alternatively i'm trying to push it again to power on, it failes to succeed what leaves me to make an another resets for several times.
Can you resolve this issue during upcoming next rom?
Thanks for your good job!
Click to expand...
Click to collapse
Same problem.
And a second issue: my A696 freezes if I work with the BT module (handsfree, file transfer)
Thanks for the ROM.
When I was making the rom, I was looking for a way to delete the MS Bluetooth stack to free up some space (which is perfectly fine). I'm not sure, but I think the problem could be caused by me deleting some dll file packages related to bluetooth that are shared between the MS Bluetooth stack and the stock Broadcom stack (which is better).
Finally got around to flashing the new ROM. It appears to be working fine. I mostly use the A626 as a music player so I've had no issues so far. There is one thing that I'm not sure if its just my A626 or if anybody else has the problem but when I plug in the external AC adapter it doesn't seem to recognize the external power source... it will charge the battery it doesn't use the screen brightness and timeout settings, it will stay using the settings as if it is running on battery. Anybody else notice this?
*******
Actually after playing around for a couple hours I have an issue where once the device blanks the screen out I cant wake it up by pushing on the screen or the power button. If I connect power and disconnect it and reconnect it I still can't wake it. I have to reset the device to get it back to functional. I've tried reflashing and still have the same issue.
*******
I switched to a different mini usb charger and now it is recgonizing that the external power is hooked up... must have a weird usb charger. I've also gone back to using 6.5 1a to see if I have the same stand by/blank screen issues.
Bluetooth handsfree
I found some registry entries in a french site, with these settings we can enable the bluetooth handsfree service. I attach this file, maybe Steven will integrate in the next ROM (this service can be disabled in the bluetooth settings like any other service if you don't use). The application (which is from asus \windows\bthandsfreedevice.exe) has a little bug: can't do the synchronization of the phonebook and calllog from the phone (I tried with nokia 6233). If anybody know about a newer version of bthandsfreedevice.exe or know another (better) bthandsfree application, maybe we can make a working handsfree device from A696.
brgds,
imre00
bmasephol said:
Finally got around to flashing the new ROM. It appears to be working fine. I mostly use the A626 as a music player so I've had no issues so far. There is one thing that I'm not sure if its just my A626 or if anybody else has the problem but when I plug in the external AC adapter it doesn't seem to recognize the external power source... it will charge the battery it doesn't use the screen brightness and timeout settings, it will stay using the settings as if it is running on battery. Anybody else notice this?
*******
Actually after playing around for a couple hours I have an issue where once the device blanks the screen out I cant wake it up by pushing on the screen or the power button. If I connect power and disconnect it and reconnect it I still can't wake it. I have to reset the device to get it back to functional. I've tried reflashing and still have the same issue.
*******
I switched to a different mini usb charger and now it is recgonizing that the external power is hooked up... must have a weird usb charger. I've also gone back to using 6.5 1a to see if I have the same stand by/blank screen issues.
Click to expand...
Click to collapse
I noticed these today as well, and re-flashed but wasn't able to resolve the problem. Will continue testing the ROM.
While I don't need the Microsoft entries (since they pertain to the MS bluetooth stack), but I will definitely take a look at the widcomm entries. I won't be able to work on rom building until the weekend, but I will take some time to test it (to tell you all the truth, I didn't really test bluetooth as much as I should have with this release).
bmasephol said:
*******
Actually after playing around for a couple hours I have an issue where once the device blanks the screen out I cant wake it up by pushing on the screen or the power button. If I connect power and disconnect it and reconnect it I still can't wake it. I have to reset the device to get it back to functional. I've tried reflashing and still have the same issue.
*******
Click to expand...
Click to collapse
It seems that the device can't wake up only when goes in standby after applying the screen lock. Without locking, it can be powered on with the power button.
Downgrading to rom version 1
Hi steven,
After several times i tried to discover what's appear to make the battery totally empty (due the fact i couldn't start my 696 on every time i shut it down or just pushed shortly the "power on" button just to make it sleeping mode) i figured that something in the rom version 2 caused the problem.
I alreasy noticed (my last reply) that even the battery still ok, during trying to make the 696 go to sleeping mode it's refuse after that to power on and forced me to make couple of resets (because even after some resets the 696 still stuck without any responding).
Finally i downgraded the 696 to rom version 1.
UPDATE 274/2012
Okay. So, Nokser's FFUPartTool extracts the IMGFS partition from the FFU.
Barin's OSBuilder (here) can be used to dump the contents of the IMGFS.
The registry files can then be edited in HVEdit (link), and the IMGFS can be recreated using OSBuilder.
FFUPartTool can then be used to replace the IMGFS partition in the FFU.
This FFU now needs a Mazaa to be flashed on.
If anyone out here is brave enough to flash their phone, please report the results!
UPDATE 17/4/2012
So, as we all know we have a stock mango FFU for the Mazaa (see here if you don't).
And due to recent developments, we also have this: FFUPart Tool v1.3.1
What this means is, we can create a custom FFU for the Mazaa. Now, personally, I have never created WP7 CFW before, but Nokser, the creator of the tool above assures me the creating CFW with this tool is quite possible.
So, what are you guys waiting for? Race to the finish line?
My list of things to be done starts and ends with this: get htc connection setup to run.
That's literally all we need to kickstart the Mazaa scene. Once we have that, we can do the whole shebang.
We need a ROM image for the Mazaa before anything at all can happen.
-------------------------------------------------------------
Here are the ROMs being used by people:
7.1.7649 - Test Rom. Has lots of interesting Microsoft applications (the zApps). But lacks quite a few features and stability.
7.1.7661.wp7_5_trial(mojobld).20110607-1657 - Similar Test Rom.
7.1.7720.68 - Locked bootloader. Phone is recognized as an HTC Device, but Connection Setup doesn't run.
7.1.7720.500 - Is basically the same as .68 but with an unlocked bootloader. Phone is not recognized as an HTC Device.
7.1.7740.16 - Updated via the official CAB [WP7 Cab sender tool]
7.1.8107.79 - via the official CAB [WP7 Cab Sender Tool]
7.10.8773.98 - via the official CAB [WP7 Cab Sender Tool] - 28/06/2012
Firmware revision number: 1600.1502.7720.68
Hardware revision number: 112.1410.2.0
Radio software version: 1.6.00.15.02
Radio hardware version: 8655/DDR2
Bootloader version: 7.27.00
Chip SOC version: 0.75.2.1
If anyone has different details, please post them.
-------------------------------------------------------------
The major problem with all ROMs is the lack of drivers.
1) LED lights don't function
2) SD Card slot
3) Connection Setup drivers
4) Internet Sharing doesn't work
Secondarily, because of the lack of connection setup drivers, there's no interop unlock. Which means no homebrew. Which means this device is pretty much what a technophobe buying a smartphone for the first time needs.
-------------------------------------------------------------
Does anyone know how to edit FFU (full flash update) files? They seem to be .cab files with a signed xml .blob in them.
Is there any way to edit these files?
Alternately, has anyone been successful at obtaining a stock ROM for the Mazaa? Because otherwise the device is extremely crippled.
Once we obtain a stock ROM, it's merely the point of identifying what drivers are missing, appealing to the DFT team to test the Mazaa to check whether HSPL/RSPL works, testing whether HTC Trophy drivers (and maybe other phones' drivers) work, cooking a rom, and flashing it. Once we get the ball rolling, it should all materialise.
-------------------------------------------------------------
Finally, what other problems are people having with their Mazaas?
Here's a list of problems I've noticed across the net:
Low battery life (4 - 6 hours at most).
Inability to connect to CDMA networks
Can't use HTC Connection Setup - hence no 3g/mms on certain networks
Inability to connect to certain GSM networks - lack of a valid IMEI
Frequent restarts/hangs [2 - 3 per day in some cases]
Each of these are frustrating faults.
Here' to hoping that the hundreds of DEVELOPERS with Mazaas can put in a concerted, collective effort and get this going. EVERY other phone has been unlocked/tweaked/improved upon, so why not a limited edition developer-exclusive device?
Thanks for summarizing the various versions. As developers, with a concerted effort, we should be able to resolve the issues and make it work for us.
I think most people sold the device, even if this wasn't allowed, at least for the first batch (not those won, but those requested for mango/gyro dev)
I had hopes battery problems where in a faulty battery...
even if they're sold, someone's still using them!
And the battery problems were too widespread (more than half a dozen cases) for me to discount.
the IMEI problem on the other hand was in a single case - mine.
abhilaksh said:
even if they're sold, someone's still using them!
And the battery problems were too widespread (more than half a dozen cases) for me to discount.
the IMEI problem on the other hand was in a single case - mine.
Click to expand...
Click to collapse
That's right, but they're probably not in dev hands anymore, so chances are not very helpful hands at this, especially since there's no more access to official updates.
All summed up, since not even the gyro works correctly on mine, it's a paper weight for which I'm still waiting for import taxes refunding
As far as issues, in addition to the above:
- I cannot send/receive MMS (SMS works, though)
- No 3G (DO or 2x only)
- 2-3 crashes per day
My build is 7.1.7720.68
Sent from my Mazaa using XDA Windows Phone 7 App
I have HTC Mazaa
I have the HTC Mazaa device that exactly matches all the details given in the original post in this thread.
For me, its working perfectly, no battery problems (works for 2-3 days), no crashes at all, I can't say about 3G support problems because we don't have that in our country. The phone works perfectly fine.
I have dev unlocked the device from App Hub but would love to remove the interop lock as well...in fact thats what I came here for.
Please guide me.
Thanks.
When I first got my cdma provisioned Mazaa, it had a 7.1.7600_Main build on it. This was like the test ROM - it had the zApps. Looked to be the internal Microsoft beta for employees. I think everything worked on that, just Mango was crippled.
Does anyone have this? I flashed the ffu and the backups can't restore. It would be an interesting starting point if the oem bits are all there.
Sent from my Mazaa using XDA Windows Phone 7 App
Please guide me on I can interop-UNlock the device.
How can I update my Mazaa to 7.1.7740.16 build?
Mike48236 said:
When I first got my cdma provisioned Mazaa, it had a 7.1.7600_Main build on it. This was like the test ROM - it had the zApps. Looked to be the internal Microsoft beta for employees. I think everything worked on that, just Mango was crippled.
Does anyone have this? I flashed the ffu and the backups can't restore. It would be an interesting starting point if the oem bits are all there.
Sent from my Mazaa using XDA Windows Phone 7 App
Click to expand...
Click to collapse
Hello there,
Currently I'm using a Mazaa sent from MS with the 7720.500 fw, It has all the zApps and the internal MS apps like FindSomeone, it has battery issues (but it's not worse than an Omnia 7 with Mango), and there are four annoying things experienced:
- volume is always a bit too loud and MP3 playback is sometimes faltering
- when you press the ON/OFF button, sometimes the screen comes back immediately after turning it off
- when you place a call, sometimes the screen turns off immediately, which can be brought back using the proximity sensor (hold close to head, then move it away)
- cannot receive MMS messages
Exact details:
OS: 7720.WM7_Main(mojobld).20110723-1640
FW: 1600.1502.7720.500
HW rev: 112.1410.2.0
Radio SW: 1.6.00.15.02
Radio HW: 8655/DDR2
Bootloader: 7.27.0.0
Chip SOC: 0.75.2.1
I'm no expert in messing with phones (only using homebrews once they become 99.999999999% safe) but if I can help in any ways I'm not breaking this phone, I can surely do my part provided I'm given step by step instructions.
To update to 7740/8701:
Use the WP7 update cab sender tool here
Okay. So, let's get this sorted: We need a ROM. MSFT has said ROM. We need MSFT to give us the ROM. So, I'm requesting everyone: Send a message to whoever your contact is in Microsoft and let them know of the many problems that everyone is facing. At the very least, ask them to provide new radios to get rid of the hardware glitches. Granted it's a test rom, all the more reason that they should actually be working on it. A phone that doesn't work as intended is more a burden than not.
abhilaksh said:
To update to 7740/8701:
Use the WP7 update cab sender tool here
Okay. So, let's get this sorted: We need a ROM. MSFT has said ROM. We need MSFT to give us the ROM. So, I'm requesting everyone: Send a message to whoever your contact is in Microsoft and let them know of the many problems that everyone is facing. At the very least, ask them to provide new radios to get rid of the hardware glitches. Granted it's a test rom, all the more reason that they should actually be working on it. A phone that doesn't work as intended is more a burden than not.
Click to expand...
Click to collapse
I'm sorry but I'm not going to be of any help in getting an updated ROM, since we are low on the supply chain. Also, the way we get each new build is by getting a new phone. (Send back old one, get one with newer software.)
I have an HTC Mazaa, running 7720. Everything is ok for a dev phone, I have no serious problems with it, except EDGE/GPRS not working and speaker emitting a loud tone when I'm calling a number outside my network. I'm thinking of installing the new updated build. How should I proceed exactly? Should I use the cab sender tool? I also want to mention that the phone is not dev unlocked, I'm still waiting for a student unlock. Thanks.
download the cab sender.
download the cab.
place the cab in the same folder as the cab sender.
run the cab sender.
send the cabs to the phone.
you're done.
I tried to update my HTC Mazaa and I got an error at the first restart. But, after that I typed *#06# on the Phone hub and I get this IMEI: 00A100000794C***.
I did it again, but this time, with my SIM card inside the phone. Unfortunately, I got the old IMEI message: Failed.
***
Even after all could not update my smartphone:
Verificando o status do telefone: Completed in 2,01 seconds
Verificando requisitos do sistema: Completed in 0,11 seconds
Fazendo o download de atualizações: Completed in 2,87 seconds
Verificando requisitos do sistema: Completed in 0,01 seconds
Transferindo atualizações: Completed in 24,65 seconds
Preparando para instalar: Completed in 46,16 seconds
Reiniciando o telefone: Completed in 231,04 seconds
Instalando atualizações: Completed in 70,15 seconds
Verificando o status do telefone: Completed in 0 seconds
Reiniciando o telefone: Completed in 34,28 seconds
Concluindo atualizações: Completed in 20,04 seconds
Error:
Update device 53d261df - cd29c761 - 4fe43c2f - 733020be Complete with error code
: 80180048, error message: Falha ao instalar IU (Image Update) devido a um erro.
■
╚══════» Done
Is there anyone on xda-devs to help us update our HTC Mazaa and also do the interop-unlock?
Mazaa ROM
Hmm...
Here.
http://hotfile.com/dl/135477621/ed2186c/FlashClean.zip.html
That's an FFU.
Which cab should I use? Or which is the recommended one? Thanks.
Thankyou for that FFU
@abhilaksh Thankyou for that FFU file it saved me from alot of messing around. So happy to get my Mazaa back in working order. It broke on me a few months ago and ive been though hell trying to get the bugger fixed. It just got stuck on the mobile operator screen.
imgur(dot)com/oBH9M
Even had it sent off to UK repair center for them to send it back in the same condition (Idiots). I was just about to send it off to a US repair center when i did some more searching. It worked a treat, really straightforward as well.
If anyone else is a noob in the same situation as i way id recommend these simple instructions:
1. Install Zune Beta Client (beta includes the UpdateWP tool)
2. Install the SetupUpdateWp.exe to get the tool
3. Follow these instructions to flash your phone
mobilitydigest(dot)com/ms-instructions-on-how-to-flash-a-windows-phone-7-device/
Thanks again, Rob