Related
Hi all after upgrading to win 2k5 my device worked for 6 hr and while installing software it hanged resting didnt open it i cant get it to connect to activ sync is there a way to get windows agine on this device please advice
regards
Do a hard reset, it will solve your problems
nothing works no hard reset nothing is working it stand on the colored window nothig else i cant even get the boot lodar screen only the 4 colores screen and the blue tooth led working and the phone is working but no rings isnt there a way i can flash with sd card like in wallaby please help me
try doing a soft reset "power+reset" then right afterwards press "record+camera".. use the record and camera to set the bottom two options to yes and press your mail button.. maybe this will get it going again.. if not do the normal 05 bootloader "power+record+camera+reset" and dock it and hopefully you will see the USB and can reflash it again or back to 2k3
THx a lot Black6spdZ it's working now :lol:
what fixed it?
i just did as you told me (try doing a soft reset "power+reset" then right afterwards press "record+camera".. use the record and camera to set the bottom two options to yes and press your mail button.. ) then the windows opend correctly and i could get it connected to active sync i instaled another ver. of windows TuMa_v1.4 but the camera didnt work i'm looking now for a way to make it work if u can help me
PS i recive this message each time i rest the device (the file camera_Detect cannot be opend. either its not sined ....)
are you flashing an ext rom with the main rom? If not it may be trying to load the old 2k3 ext rom programs on top of your newly installed 05 main rom. if that is your only problem look with the files that came with the 05 zip, I believe there is a compatible Camera app included with it that you can load and should hopefully overwrite the older version. You can keep that message from appearing by going into your Windows/Startup folder and deleting the camera detect startup program until you get the new camera app loaded. What I did was use the ext rom tools to unlock and then format the ext rom so that there were no programs on it. From then on I only flash the main rom when needed and load just the programs that I need to keep it nice and fast. Hope this info gets you going.
yah this is a good information now it's working fine thx a lot :lol: i found the application on the ext rom htc one and everything is gr8
hi,
i'm a newbie, and yes i have screwed up.. performed (or should i say.. almost performed) my rom update on my desktop (which is kinda slow PC...) i had no applications or unwanted services running, my computer. The Progress on the Rom update (the desktop couterpart) had incremented and had become full (the progress bar i mean..) and it was nicely sitting there for about two hours with no indication of any further progress (yeah just wanted to make sure it wasnt me being hyperactive or in a hurry )
On the PDA it was a different story.. the screen indicated a 100% copy of some image file and then it was stuck at "Reset Hermon" stage. )for the record, i feel like a parrot now, these words dont really make sense to me.. )
So i removed the cable, battery and booted up my phone after about ten minutes... yup, just like i had expected it got stuck at the bootloader screen.
Now obvisously, my Rom update wizard wont work, as the very first step is to check for a existing Active Sync Connection. and Activesync is not a application tht recognizes phones connected in their bootloader mode...
Now i have no idea about trying to flash thru the memory card, i tried copy pasting all the files that the Rom update file had generated in the desktop folder it was run in(about 4 exe files that are supposedly 'not a valid 32-bit application' and two .abi files.. one of the abi file is 85 mb, so i guess that was the image file.. but when i copied these files into the memory card and re booted my PDA, it didnt show any change, as in it still asked me to connect the USB cable and was trying to get the image from there..
I have a o2 xda zinc. yeah, with no Operating system ..
to say that help would be appreciated is a understatement
damn, contacted the o2 support guys, but i have this feeling that this (forum ) would be a faster way to know if i have to drop my phone at the 'collection center' or not. i am still optimistic as the phones under warranty and its just a software glitch. Please enlighten me. what are my options?
hi
my o2 zinc has the same problem just like yours
if your zinc fixed or any thing new pleas tell me
tnx
go to this post
http://forum.xda-developers.com/showthread.php?p=1512766#post1512766
hi mazi_v, i have problem when upgrading my XDA II.now it just displaying
USB and V 1.02
what i have todo?
thank's
"what i have todo?"
connect it to usb and rerun the flash
Hi guys.
I was using the installed the FInixNOver 3.0.1 ROM onto my SPV M700 and it was great. I've had it for about 2 weeks without any problems.
Last night I looked at my phone, only to realise that it was completley dead. This didnt shock me to much because the battery was running low, and i decided to let it die completley before recharging it again.
I charged my phone overnight and switched it on this morning, but the phone would freeze at the 'FInixNOver' splash screen (the numbers at the bottom of the screen would appear overlaying the splash, but the phone wouldnt go pass this point).
The only way to turn off the phone from this state is to eject the battery. I have tried removing the sim card, turning it back on in as many ways as possible but to no avail. I am able to get to the TriColor test screen (im running IPL-0.50 / SPL-1.30.Olipro) but with all the custom roms available, they all use the ROMUpdateUtility which requires the phone to have established an activesync connection initially (but this would mean my phone would have to be 'on completley' - so this is catch 22.)
For the record, my phone/battery died while my wired handsfree was attached (dunno if thats of any interest to anyone or the rom baker).
But it looks like the only way i'll be able to flash my phone is by finding a way to install the .nbh file without using the RUU method. Because I can put my phone into test mode manually.... any help or guidence would be very much appriciated.
Thanks.
Ok can you get it into bootloader? power/camera buttons and reset?
sorry didnt read fully.
right get your device into bootloader first,
then open active sync (are you using xp)
then open connection settings and disable usb connection,
put your device into bootloader mode, then run any rom upgrade, i prefer the WM6.1 pdaviets from HERE (Username: PDAVIET / Password: pdaviet)
Your pda does not need active sync with ruu's, so no catch 22. if you turn off usb connection in active sync, you can still run ruu and it will be recognised, unless you are using vista, where you need to change your HTC SYNC drivers.
Thanks for your quick response...
Yes I can get into boot loader using the power and camera buttons (or holding the power and camera buttons when resetting the phone)...
When the phone is in boot loader mode, active sync doesnt even detect the phone anyway, but nevertheless, I have followed your instructions and disabled the USB Connection. (BTW, yes i am using XP)
The phone is still in boot loader mode, so now i try and execute the ROMUpdateUtility.exe and go through the steps, at the 1st step i tick the tickbox and click next, and the 2nd step i tick the tickbox and click next. (this step says DO NOT enter the bootloader manually? - but i have havent i?) anyway, when i click next, it says... "Verifying the information on your Trinity... Please Wait..." for about 10 seconds, and then i get a message "ERROR [260] : CONNECTION"
What am i doing wrong?
Huumm.. why dont you flash your phone throw the sd card??
Read this link:
http://wiki.xda-developers.com/index.php?pagename=Trinity_SDCardFlashing
try to flash your phone with some official rom and after that flash it with any other you want!
manos_23 said:
try to flash your phone with some official rom and after that flash it with any other you want!
Click to expand...
Click to collapse
I would recommend this option above, to be safe, i usually get them error messages when the battery is below 50% or sometimes i try it again and it works. it does state do not manually enter bootloader but i always do it this way.
also make sure active sync is not still running in taskmanager under the alais: wcescomm.exe and WCESMGR.exe, end them both.
I've just tried using an official ROM, but the problem still occurs with the 'connecting'. It doesnt seem that the computer picks up a connection to the phone whatsoever.
Should i be concerned that at the bottom of the bootloader screen it says "serial", is this correct?
Im starting to get annoyed now.
Bye,
the bottom of the sreen mast say "usb" not serial.
it seems there is a problem, if it states serial. as it should say usb. try THIS
Seems like the problem was that my USB lead was loose and made a bad connection, hence why the bootloader showed 'serial' and not 'usb'... as soon as i wiggled it and heard the 'connection noise' in windows, i knew i was good to go, and so using the RUU worked fine to reupdate my phones ROM.
Thanks for your help.
My only question is that why did it happen in the first plave?
WIZZKID - I just saw your post here now. I have to tell you that I also saw "SERIAL" at the bottom of the bootloader screen and not "USB". As I said I returned it to get another phone but maybe I will try something else for now instead of a P3600i. I will monitor your thread to see how it turns out for your phone, because it seems that we have the same problem.
if you see "serial" instead "usb" your problem is in the usb cable, usb port from your computer or in the usb connector from your trinity!!!!!
I was having the same problem that you have!! my problem was from my usb from mine trinity!! see if the conector is at good conditions !!!
Well as some of you may know, I got my Trinity replaced for sticking at the WM splash screen after a few days. This second one - I have had it ONE night - and the same thing has happened with incomplete booting. This time I have been trying all night to flash the phone to an official ROM, but I cannot do it (apparently) because I can't establish a connection via ActiveSync. When I stick the data cable in while in bootloader I see SERIAL replaced by USB and when I try the flash I get a "270" error (cannot connect to phone) and the phone re-boots to the sticking plash screen. What should I do now?
ladies and gentlemen...
we've got a lot of mixed messages in this thread.. please make sure you're posting the right thing. no need to disable USB when manually going in to bootloader to flash (at least in xp).. Also, you can ignore the part of the RUU that says 'do not manually enter bootloader' (you should really read the guide on my site)
foxuniform- can you please give some details..
1) are you running xp or vista
2) have you flashed hard-spl? if so what version?
in the mean time, try a couple of things.. first, flash hard-spl (even if you already have it, but from the sound of it i think you don't have it on your device).. if that works, try to flash an official ROM. Can also try to use splxploit, then flash hard-spl, and then flash official ROM (there's a guide on my site if you're unsure)
please post your results
*edit*
here are the steps for SD card upgrade, but i HIGHLY recommend flashing Hard-spl first..
try to do it from SD card. how?
Extract the .NBH file from your prefered ROM upgrade: In windows use winrar (right click) to extract the contents of the exe file. In Linux / MacOS use cabextract (http://www.cabextract.org.uk/) .
Rename the .NBH file to TRINIMG.nbh and copy it to the root folder of your miniSD card.
With miniSD card inserted on the phone, start the bootloader (hold Power button on right side and Camera button at same time and stick with stylus in RESET on bottom).
You should see the screen pictured on the left, confirm flashing on screen by pressing the power button.
Flashing might hang after some time but this is normal. Just wait. Complete flash takes about 30 minutes, so check your battery or connect to charger before the flashing process starts.
When flashing completes soft-reset your device.
Make sure your SD has FAT32 and has no label. There have been reports that if SD has a label the bootloader can not access the TRINIMG.nbh
racerx_ I have carefully read your response and suggestions, and thanks for your expertise input on the matter. I am fairly new to this stuff so read below carefully as you may find errors in the way I tried to go about doing what I was hoping to accomplish.
First let me answer your questions. I am running Windows XP. The phone is in it's completely natural state in that I have not flashed it in any way. The ROM I was TRYING to flash to the phone while it was not starting properly (this is where I manually entered bootloader) is an official ROM from the HTC website (please note everyone that when I registered my P3600i on the HTC website it came up as the Dopod 810). Anyway, that never worked. ActiveSync never detected the phone (and I guess that's the reason I could not do anything as far as flashing goes). I HARD-RESET my P3600i and it booted normally. I re-installed all the stuff I had on it, from memory card to various .cab files, and the phone is working beautifully thus far. I will report if anything funny happens again.
I have to ask you racerx_, if I CAN flash hard-SPL on the P3600i according to the lovely guide on www.trinityguides.info. I have been of the opinion that things don't work for the P3600i as they did for the P3600, and that has been echoed by many P3600i users on this forum who are ready and waiting to try out some cooked ROMs (myself included).
For the sake of record, my phone is running rom version 3.00.707.17 and radio version 1.46.00.11. I patiently await your response.
woaaahhh..
i didn't notice the 'i' in your previous post... yeah, as far as i know, these ROMs are not flashable on your p3600i.. sorry..
**correct me if i'm wrong somebody**
Yeah I kinda thought that would be your response. By the way - do you think that this phenomenon of sticking at the Windows Mobile splash screen (both the P3600 and P3600i models apparently) has anything to do with something users do with the devices, or you figure it's an inherent software glitch of some sort? I am wondering if I should try a different model or hold on to my P3600i? Hope it's not something that'll happen again - I fly for a living and it's not gonna be good to have the thing screw up on me away from base - I really count on it for everything from casual keeping in touch on Messenger to viewing my work schedule. I love the Trinity though - it's one of my all-time favourite HTC phones.
hmm... i don't think its inherent in the Trinity.. (not a hardware issue.. in my opinion)
its been a while since i followed the posts on it, but always seems to be software related.. sometimes ROM-specific problem. Personally, i've probably flashed as many ROMs as anyone and the only time i ever encountered problems was with the official HTC WM6 ha.. go figure.. I think ppl did find that hard resets before and after flashing are helpful as well..
i love my trinity, and there's not much else on the market to make me want to trade it in (is it just me, or have pda's kind of stopped getting cooler).. i'd stick with it..
Important - Read First!
First of all you must know that everything you do is on your own risk. Your device was not designed to run GNU/Linux or Android and that's why you shouldn't expect everything to be perfectly safe. If you don't want any troubles then simply don't tamper with your phone. On the other hand, installing Rhobuntu is probably less dangerous than installing alternative ROM's, because it doesn't touch your ROM and runs completely from the SD card. If something goes wrong and the system would hang up, you always can remove the battery and boot into Windows Mobile. Still, we can't guarantee you anything and we won't be liable for any damage that might happen to your device. If you don't accept this, don't install Rhobuntu.
At the moment two problems are known to occur when using Rhobuntu. They are, however, not Rhobuntu specific and may also occur when using Android.
1- After booting back into WinMo, you can't install or run unsigned apps. This problem probably has something to do with the way haret kicks WinMo out of the RAM. It also seems to occur only in combination with the use of Exchange Server. The only known solution at the moment is Hard Reset. Some users also reported that it can be fixed by using Visual Studio 2008. Check out this threads:
o Not digitally signed with a Trusted certificate/ Activesync keeps UNINSTALLING!
o Program... is not digitally signed with trusted certificate. HELP!
2- Since we still have no proper battery charge indicator working, you might not notice that your battery is completely drained. Deep discharge is, however, not good for batteries and may in some cases even damage them. Here is a thread dealing with this problem when running Android
o Android killed my USB connection, please help
The majority of Rhobuntu users doesn't face these problems, but just in case, you've been warned.
WIKI http://wiki.xda-developers.com/index.php?pagename=RhodiumUbuntu
WEBSITE https://sites.google.com/site/rhobuntu/
This build by Walter79 and the Rhobuntu team:
Rhobuntu 9.04 19.09.2010
changelog:
- zimage update (Xandroid Build 16/09)
- sphone 0.04 (thanks AmiPro)
- 3G scripts update (thanks AmiPro)
- sound works partial (thanks to phhuson) !!! run /sdcard/ubuntu/playwav2 after boot !!!
- alsaplayer added
Download:
Link1: http://www.megaupload.com/?f=RWDJWUN0
Link2: http://rhobuntu.4shared.com
Debian Squeeze Test 19.09.2010
For more information please look at this post http://forum.xda-developers.com/showpost.php?p=8186181&postcount=1208
Download:
link1: http://www.4shared.com/dir/n-2ObqP_/pro2-debian.html
Old Build (27/06/2010)
*http://www.megaupload.com/?f=RWDJWUN0
*http://rhobuntu.4shared.com
Old Build (13/05/2010)
*http://www.megaupload.com/?f=RWDJWUN0
*http://rhobuntu.4shared.com
Old Build (14/04/2010)
*part one:http://rapidshare.com/files/375930803/Jaunty_14_04_2010.7z.001 MD5 77430e728bb17277e671cc55ae03161f and part two: http://rapidshare.com/files/375939439/Jaunty_14_04_2010.7z.002 MD5 523589000dcd5d1dcea668bbe51253af
* http://rhobuntu.4shared.com
* http://www.megaupload.com/?f=RWDJWUN0
Old Build (11/04/2010)
* http://rs427.rapidshare.com/files/374730149/Jaunty_11_04_2010.7z
* http://rhobuntu.4shared.com
* http://www.megaupload.com/?f=RWDJWUN0
Old Build (10/04/2010)
*http://rapidshare.com/files/374138895/Jaunty_10_04_2010.7z
*http://rhobuntu.4shared.com
Pretty cool idea, keep us posted!
Definitely an awesome idea, and one I had been thinking about myself since my original Touch Pro days. An embedded version of Linux should run great on these devices. Hopefully momentum will grow surrounding this.
thats very interesting. any pictures of this running? maybe things can be pulled from android.
THANKS!!!! downloading now!
tried it on my Touch Pro 2 (AT&T Tilt2), No luck. Started to boot, Complained about /etc/init then poof reboot after 7 seconds. Am I missing something.
aq3e said:
tried it on my Touch Pro 2 (AT&T Tilt2), No luck. Started to boot, Complained about /etc/init then poof reboot after 7 seconds. Am I missing something.
Click to expand...
Click to collapse
Did you change the mtype in the sartup script to the tilt2, the one i used is set for the rhod100, i hope that helps. Is anyone else's not working btw?
Help!
I extracted all the files on to a newly formatted 2GB card.
Ran haret and everything ran fine. Bit 'interesting' navigating round the screen but got there in the end.
However, since rebooting my phone back into WM I cannot run any unsigned programs such as haret that worked fine before.
The error says "The file blah cannot be opened either it is not signed with a trusted certificate..."
Any idea what's changed and how I can get my phone back to how it was?
R.
dicko99 said:
I extracted all the files on to a newly formatted 2GB card.
Ran haret and everything ran fine. Bit 'interesting' navigating round the screen but got there in the end.
However, since rebooting my phone back into WM I cannot run any unsigned programs such as haret that worked fine before.
The error says "The file blah cannot be opened either it is not signed with a trusted certificate..."
Any idea what's changed and how I can get my phone back to how it was?
R.
Click to expand...
Click to collapse
Wierd, my winmo works find, minus the calibration issue, it's brilliant, we need some linux Devs to look into this. as a windows user, i have no idea on what to do
Thanks (All we need now is win XP )
Badwolve1
I think something got corrupted/overwritten on my phone...
I cannot run any unsigned apps whether they are installed on the storage card or internal memory.
I cannot even install new apps! When I run the cab file, I get the usual "This program is from an unknown publisher..." and when I select yes for continue it immediately comes up with "Installation of blah was unsuccessful."
Time for a hard reset? I'd really prefer not to if anyone can suggest a better way of getting back to how it was.
R.
dicko99 said:
I think something got corrupted/overwritten on my phone...
I cannot run any unsigned apps whether they are installed on the storage card or internal memory.
I cannot even install new apps! When I run the cab file, I get the usual "This program is from an unknown publisher..." and when I select yes for continue it immediately comes up with "Installation of blah was unsuccessful."
Time for a hard reset? I'd really prefer not to if anyone can suggest a better way of getting back to how it was.
R.
Click to expand...
Click to collapse
did you install anything recently, could try uninstalling it
dicko99 said:
I think something got corrupted/overwritten on my phone...
I cannot run any unsigned apps whether they are installed on the storage card or internal memory.
I cannot even install new apps! When I run the cab file, I get the usual "This program is from an unknown publisher..." and when I select yes for continue it immediately comes up with "Installation of blah was unsuccessful."
Time for a hard reset? I'd really prefer not to if anyone can suggest a better way of getting back to how it was.
R.
Click to expand...
Click to collapse
try installing SdkCerts.cab
http://forum.xda-developers.com/showthread.php?t=554240
the cab is included with the rhodium keymapper zip file. (keymapper app is worth installing as well )
sdkcerts won't install. It has the same problem as other cabs where it prompts to say the program is from an unknown publisher and when I tap Yes to continue it still fails with "Installation of SdkCerts.CAB was unsuccessful."
Tried booting it up on my Verizon TP2 and all it does is run haret and then freeze.
Thanks for putting this together, sebbo90. It boots nicely, and actually performs quite well on my Tilt2. I hope some of the developers take notice of this project and consider fixing the major usability issues like the front keys and the display calibration.
After the first boot I cant get the GUI to run anymore. Removing the directory from the SD and uploading a fresh copy fixes it for one boot only. After that it just hangs at command line.
spdweb said:
After the first boot I cant get the GUI to run anymore. Removing the directory from the SD and uploading a fresh copy fixes it for one boot only. After that it just hangs at command line.
Click to expand...
Click to collapse
How did you even get it to boot?
EDIT: Do you think it will not boot for me since you all are using GSM and i am using a CDMA phone? Some settings may need to be changed i guess. I have been messing around but no luck.
spdweb said:
After the first boot I cant get the GUI to run anymore. Removing the directory from the SD and uploading a fresh copy fixes it for one boot only. After that it just hangs at command line.
Click to expand...
Click to collapse
I had this problem what i did to fix it was to was to do a full reformat on my sd card (not a quick one) this then helped and now it boots everytime. Hope this helps
sebbo90 said:
Did you change the mtype in the sartup script to the tilt2, the one i used is set for the rhod100, i hope that helps. Is anyone else's not working btw?
Click to expand...
Click to collapse
If the mtype needs to be changed, what should it be instead of the default 2292, forgive my ignorance.
EDIT: must be a fluke, it booted now, did not change a thing. Re-extracted the ubuntu rar and shoved it back on the SD and booted. Great Job. All we need now is calibration to get started.
sebbo90 said:
I had this problem what i did to fix it was to was to do a full reformat on my sd card (not a quick one) this then helped and now it boots everytime. Hope this helps
Click to expand...
Click to collapse
I got it working now. It was the directory structure I was using. I spent about 2 hours last night working on the calibration issue. If I could get that working it would be sweet. Tried a newer version of haret and tweaked the startup.txt a bit but the calibration still goes out of range.
On a brighter note, the calibration works fine when booting xdandroid with haret though it is a manual calibration there is hope anyway.
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.