[ROM]RUU_Spark_W_VERIZON_WWE_0.82.605.02_Radio_1.25.00. 10.20_22.03W.85.00U, by ansar. - Trophy Windows Phone 7 Development

[ROM]RUU_Spark_W_VERIZON_WWE_0.82.605.02_Radio_1.25.00. 10.20_22.03W.85.00U, by ansar.
Hi,
A new ROM for the W_VERIZON (VZW__001) operator:
RUU_Spark_W_VERIZON_WWE_0.82.605.02_Radio_1.25.00.10.20_22.03W.85.00U_by_ansar
see also thread: Windows Phone 7 Branded ROMs for Spark
Till next version enjoy!!!
Regards, ansar.

hey bro
ansar.ath.gr said:
Hi,
A new ROM for the W_VERIZON (VZW__001) operator:
RUU_Spark_W_VERIZON_WWE_0.82.605.02_Radio_1.25.00.10.20_22.03W.85.00U_by_ansar
see also thread: Windows Phone 7 Branded ROMs for Spark
Till next version enjoy!!!
Regards, ansar.
Click to expand...
Click to collapse
no good gives a flash write error image is corrupted please fix thank you ??

leoiden said:
no good gives a flash write error image is corrupted please fix thank you ??
Click to expand...
Click to collapse
Hi,
can you specify firmware revision number? (Same reply to other thread)
Regards, ansar

In case you didnt see the other thread.. a few of us need some serious help here.
Are we stuck in with no options?
Original Version:
OS version: 7.0.7389.0
Firmware revision #:2305.06.10322.605
Hardware revision #: 0003
Radio software version: 1.52.00.03.28_23.15w.05.06U
Radio Hardware versiion: 3.2.3.D4
Bootloader version: 1.3.230506.23
Chip SOC version: 2.3.0.5.6
Then loaded this: With Error
RUU_Spark_W_VERIZON_WWE_0.82.605.02_Radio_1.25.00. 10.20_22.03W.85.00U_by_ansar
- Flash Write Error (#226) @ 12%
Then Tried this: Success, but unusable
RUU_Spark_W_VERIZON_WWE_1.03.605.20_2K_new_partiti on_RELEASE
Demo ROM, Not connect to Zune
Please help. Don't have backup.

Hi,
I will re-upload it to see if will fix this issue
Regards, ansar

Great! thank you.
Will you provide a new link or should we use the same one as above?

Looking for the new link please.
RUU_Spark_W_VERIZON_WWE_0.82.605.02_Radio_1.25.00. 10.20_22.03W.85.00U_by_ansar
= Flash Write Error (#226) @ 12%

Hi,
After dl and checking, ROM 0.82.605 found ok
Note that both are NoDo stock ROMs and:
> 0.82.605 is a 7309 platform based while
> 1.03.605 is a RELEASE, not a DEMO version
> 1.03.605 is a 7389 platform based
> 1.03.605 does not include SPL_signed.nbh
In case of 1.03 to sync zune must be updated to latest version
For 0.82.605 you can flash SPL_signed.nbh to test if it is successfull
If SPL_signed.nbh is flashed ok then flash 0.82.605 RUU_signed.nbh to test if it is successfull
Regards, ansar

Hi,
Here are steps I took:
Attempt #1
1) Extracted 0.82.605 .rar file
2) Removed the RUU_Signed.nbh from folder
3) ran ROMUpdateUtility.exe
4) Thereby flashing only SPL_signed.nbh from 0.82.605
5) Result = unsuccessfull - ERROR [226] : FLASH WRITE ERROR just after 100%
please check this file then.
Attempt #2
1) Extracted 0.82.605 .rar file
2) Removed the SPL_signed.nbh from folder
3) ran ROMUpdateUtility.exe
4) Thereby flashing only RUU_Signed.nbh from 0.82.605
5) Result = unsuccessfull - ERROR [226] : FLASH WRITE ERROR @ 12%
Attempt #3
1) Installed 1.03.605
2) Upon first boot, shows Windows Phone boot screen for long time, then shows default tiles
3) Attempt to use applications like 'calculator' etc, phone does nothing and returns to applications list, same with 'settings' etc.
4) After some time, Phone automatically reboots
5) Upon looking at the application list Slacker, Netflix etc apps are shown as installed. Applications work etc 'settings', 'calculator' etc.
6) Looking at email accounts section, a fake hotmail email address is shown, the 'me' section shows a photo of a male, 'people' section shows fake people.
7) When phone is idle Verizon/HTC screensaver, fake emails, fake text messages, fake calendar dates are shown when using phone.
Seems like a demo rom to me. Even if i shut the phone down before the first auto-reboot, it installes the demo information at some point anyway.
Attempt to upgrade to Mango takes me to 7401, then upon 7661 update, Zune states there is not enough room on the phone. Attempts to change the 'reserved space' settings have no affect. tried this update 10 times.
Are you too at a loss?
Stuck. Please advise. Unusable phone.
Should I send back for warranty?

anihilus said:
Hi,
Here are steps I took:
Attempt #1
1) Extracted 0.82.605 .rar file
2) Removed the RUU_Signed.nbh from folder
3) ran ROMUpdateUtility.exe
4) Thereby flashing only SPL_signed.nbh from 0.82.605
5) Result = unsuccessfull - ERROR [226] : FLASH WRITE ERROR just after 100%
please check this file then.
Click to expand...
Click to collapse
Hi,
I will check it, but flash write error in many cases means bad internal SD
But you flash 1.03 without Error
Is flashing of 1.03 fast or the usual 10 minutes and more?
Did you ever use y cable flash?
Regards, ansar

Hi ansar,
I renamed 0.82.605 SPL_Signed.nbh to RUU_Signed.nbh with same #226 error.
Upon reboot in bootloader, SPL shows 0.82.605
I can flash 1.03 without error and takes appx 8min from 0%-100%
SPLS shows 1.03
i've never used a y cable flash, not sure what that is
thanks

anihilus said:
Hi ansar,
I renamed 0.82.605 SPL_Signed.nbh to RUU_Signed.nbh with same #226 error.
Upon reboot in bootloader, SPL shows 0.82.605
I can flash 1.03 without error and takes appx 8min from 0%-100%
SPLS shows 1.03
i've never used a y cable flash, not sure what that is
thanks
Click to expand...
Click to collapse
Hi,
I propose an approach that worked in other Trophy brands but need to test it also to Verizon
You see Verizon is a different device from hardware point of view
It requires hTC Connection Setup
If is not available you can deploy RegistryEditor 1.1.0.0.xap and TouchXplorer.xap
This approach is completely safe with the following steps:
- flash 1.03 ROM
- chevron unlock
- use this Platform.rgu:
Code:
[HKEY_LOCAL_MACHINE\System\Platform\DeviceTargetingInfo]
"BootloaderVersion"="1.3.230506.23"
"RadioSoftwareRevision"="1.52.00.03.28_23.15w.05.06U"
"FirmwareRevision"="2305.06.10322.605"
"ROMVersion"="1.03.605.22"
- create CustClear.provxml
- insert it in HTC-ProvXml-Deploy0.0.1.xap
- deploy HTC-ProvXml-Deploy0.0.1.xap
- run HTC-ProvXml-Deploy and press green circle
- then unistall HTC-ProvXml-Deploy
- alternatively create XBMOD.Files.Deployer.xap
- deploy XBMOD.Files.Deployer.xap
- run XBMOD.Files.Deployer
- uninstall XBMOD.Files.Deployer
- deploy TouchXplorer.xap
- from TouchXplorer from \My Documents\My Ringtones copy CustClear.provxml
- paste it to Windows folder
- let TouchXplorer installed
- in case of missing Connection Setup insert above code with RegistryEditor
- in all cases power off and power on to ensure application of settings
- with RegistryEditor confirm settings
- now upgrade to NoDo if any and then to MangoB2
Just give it a try and report findings
Let me know if a problem occurs during application of platform settings
Regards, ansar

Hi ansar,
Not sure if you read my previous post. 1.03 installs additional demo stuff (ie - fake hotmail email address, fake contacts, fake appointments, fake sms messages, a demo screen-saver, etc).
I'm not sure how i can remove this by going to mango?
Besides, I've been able to get to 7401 using 1.03, then upon step 8-9 of 7661, i get error 80180031 not enough space on phone using unlock bypass script.
Additionally, I tried your steps above. Installed Chevron.cer on phone, rebooted, connected to Zune 4.7 & 4.8 beta, ran ChevronWP7.exe. (Win7x32). Chevron says cannot communicate with phone. Can't get passed this step to unlock. I assume 7389 blocks it.
thanks.

anihilus said:
Hi ansar,
Not sure if you read my previous post. 1.03 installs additional demo stuff (ie - fake hotmail email address, fake contacts, fake appointments, fake sms messages, a demo screen-saver, etc).
I'm not sure how i can remove this by going to mango?
Besides, I've been able to get to 7401 using 1.03, then upon step 8-9 of 7661, i get error 80180031 not enough space on phone using unlock bypass script.
Additionally, I tried your steps above. Installed Chevron.cer on phone, rebooted, connected to Zune 4.7 & 4.8 beta, ran ChevronWP7.exe. (Win7x32). Chevron says cannot communicate with phone. Can't get passed this step to unlock. I assume 7389 blocks it.
thanks.
Click to expand...
Click to collapse
Hi,
I think there is no way out and must wait for a new ROM to be created
Verizon is using different partitioning and signing is also unkown yet
I will try to see iwhy 0.82 can not be 100% flashed but will not be easy
Regards, ansar

Hi ansar,
yeah this is really frustrating. I appreciate your help. hopefully you will figure out 0.82.
Do you think if another verizon user zipped up thier restore files and shared it, we could use that to get back to stock?
btw - with 1.03, when clicking update in Zune, it states "Can't check for updates...an error has occured. 80070002". Unless of course i force update too 7401 via hack.
thanks & keep us posted.

anihilus said:
Hi ansar,
yeah this is really frustrating. I appreciate your help. hopefully you will figure out 0.82.
Do you think if another verizon user zipped up thier restore files and shared it, we could use that to get back to stock?
btw - with 1.03, when clicking update in Zune, it states "Can't check for updates...an error has occured. 80070002". Unless of course i force update too 7401 via hack.
thanks & keep us posted.
Click to expand...
Click to collapse
Hi,
In any case there will be a notice
Regards, ansar

I've been asked to help make a ROM? I can get yall the stock ROM my phone shipped with this weekend if that helps.
Scott

ansar,
Can you confirm we will this is a viable solution? Will we be able to use 'frishmans92' restore files from his Verizon Trophy on our devices? I assume we will have to make some modes to the xml and the folder name (as its the serial# of the device).
thanks.

anihilus said:
ansar,
Can you confirm we will this is a viable solution? Will we be able to use 'frishmans92' restore files from his Verizon Trophy on our devices? I assume we will have to make some modes to the xml and the folder name (as its the serial# of the device).
thanks.
Click to expand...
Click to collapse
Hi,
I am working on restoring between same brands but not a work arround yet
Regards, ansar

ansar.ath.gr said:
Hi,
I am working on restoring between same brands but not a work arround yet
Regards, ansar
Click to expand...
Click to collapse
Any luck on this ? I need an option soon....

Related

How to get a Kaiser to display Chinese ?

Hi everyone, I just got my first smartphone, an AT&T Tilt (HTC 8925) a couple of days ago. I'm happy with it except that I wish it to display Chinese when browsing webpages. I don't need the interface to be Chinese, nor do I need to input Chinese. I just wish when I visit a Chinese website, I'm not seeing blocks.
Don't know if this makes a difference, but either traditional or simplified Chinese would work (I read both).
Searching the whole forum didn't give me much. Probably people had some discussions before, just I didn't find them yet.
I'm totally new on smartphones. Any help is very much appreciated.
info on the phone:
ROM version: 3.57.502.2 WWE (since shipped I didn't flash the ROM)
ROM date: 07/17/08
Radio version: 1.65.21.18
Protocol version: 25.88.40.05H
I just flashed the SPL to Kaiser-HardSPL-3.56 following instructions. BTW, which version should I use, 3.56 or 3.29/28?
I did not flash the ROM, b/c I'd like to find out more on Chinese language support.
Install this cab and it will perfectly display Chinese. It is suitable for almost any WM5,6,6.1 rom :http://www.51spsoft.com/DownInfoEn/info26059.html
Or direct download link: http://www.51spsoft.com/Download.asp?ID=26760
Miraco said:
Install this cab and it will perfectly display Chinese. It is suitable for almost any WM5,6,6.1 rom :http://www.51spsoft.com/DownInfoEn/info26059.html
Or direct download link: http://www.51spsoft.com/Download.asp?ID=26760
Click to expand...
Click to collapse
Be sure to backup your device before you try. I am not responsible for any data lost. Your might need a hard reset if it failed... But it is the cab that I have been using for English roms for many devices and it will likely work for you too
you shoud find a chinese font file'ttf',and repair reg
try this websit
www.ioicn.com.cn
well.. this is what i use only...
http://www.studiokuma.com/wm/?section=support
1. CE Star chinese
2. Monster chinese
3. Many font + wince.nls + registry mentioned above.
4. My rom (see signature below)
Thank you very much.
I'm now downloading and trying the ways you pointed out.
Miraco said:
Install this cab and it will perfectly display Chinese. It is suitable for almost any WM5,6,6.1 rom :http://www.51spsoft.com/DownInfoEn/info26059.html
Or direct download link: http://www.51spsoft.com/Download.asp?ID=26760
Click to expand...
Click to collapse
Thank you for the suggestion. I just installed it on my official ATT ROM (WM 6.1). It showed installation successfull. It also said it may not display properly b/c it's designed for a previous version of Windows Mobile.
Anyway, then I visited mitbbs.com and www.sina.com.cn as a test (using Internet Explorer). Both did not show Chinese. I also tried changing encoding to Unicode UTF-8 and it didn't work either. under system settings, I looked at regional settings and didn't find anything Chinese.
Is there any configuration that needs to be done? Do you happen to know what ROM floating in this forum for WM6.1 can indeed incorporate this O2 Chinese support?
Thanks again
ctrc said:
Thank you for the suggestion. I just installed it on my official ATT ROM (WM 6.1). It showed installation successfull. It also said it may not display properly b/c it's designed for a previous version of Windows Mobile.
Anyway, then I visited mitbbs.com and www.sina.com.cn as a test (using Internet Explorer). Both did not show Chinese. I also tried changing encoding to Unicode UTF-8 and it didn't work either. under system settings, I looked at regional settings and didn't find anything Chinese.
Is there any configuration that needs to be done? Do you happen to know what ROM floating in this forum for WM6.1 can indeed incorporate this O2 Chinese support?
Thanks again
Click to expand...
Click to collapse
For regional setting, check the size of your wince.nls make sure it's > 1mb in size (typical English only is only 300 - 400k in size). But if you already planning to change yr rom, I highly recommand your try my rom. It's pre-configure for Tradition Chinese (HK, mostly), but will work on simplified chinese as well.
jackleung said:
For regional setting, check the size of your wince.nls make sure it's > 1mb in size (typical English only is only 300 - 400k in size). But if you already planning to change yr rom, I highly recommand your try my rom. It's pre-configure for Tradition Chinese (HK, mostly), but will work on simplified chinese as well.
Click to expand...
Click to collapse
I'm downloading your ROM, will try. Thanks for all the work!
just curious, where can I find wince.nls? I can't find any search function for the File Explorer on Tilt.
This is what I use to read Chinese website
http://forum.xda-developers.com/attachment.php?attachmentid=37342&d=1176792242
This is what I use to type Chinese
http://www.a4user.com/\A4_down_sip.asp
It doesnt support chinese hand writing input though. If you know of an SIP that supports hand writing input please post here
ctrc said:
I'm downloading your ROM, will try. Thanks for all the work!
just curious, where can I find wince.nls? I can't find any search function for the File Explorer on Tilt.
Click to expand...
Click to collapse
It's hidden file under \Windows. Therefore, must use "show all file" in order to display it.
cproaudio, all listed below support Chinese writing
http://www.studiokuma.com/wm/?section=support
CE star
Monster
I tried installing CE-Star 2.8 Chinese support on the shipped ROM and it worked.
I then flashed the ROM to Jack's cooked ROM and it works great now. Thank you, Jack.
Thank everyone. This forum is great.
Instructions to migrate ATT WM6.1 to Jack 2.6 confirmation
Dear All:
I just got the same phone as" CTRC above" but to ensure that I dont make any mistake on updating ROM using Jack's V2.6 from ATT Tilt WM6.1:
ROM version: 3.57.502.2 WWE (since shipped I didn't flash the ROM)
ROM date: 07/17/08
Radio version: 1.65.21.18
Protocol version: 25.88.40.05H
I read all of the above . However, to ensure that I dont run into wall,
Can someone post the step by step instructions including any potential "landmine" on how to migrate from the
ATT ROM above to Jack 2.6 ROM including the instructions if I need to install
those pre-requisites (Soft and Hard SPL ?)and proper Radio ?
Many Thx
mmtea said:
Dear All:
I just got the same phone as" CTRC above" but to ensure that I dont make any mistake on updating ROM using Jack's V2.6 from ATT Tilt WM6.1:
ROM version: 3.57.502.2 WWE (since shipped I didn't flash the ROM)
ROM date: 07/17/08
Radio version: 1.65.21.18
Protocol version: 25.88.40.05H
I read all of the above . However, to ensure that I dont run into wall,
Can someone post the step by step instructions including any potential "landmine" on how to migrate from the
ATT ROM above to Jack 2.6 ROM including the instructions if I need to install
those pre-requisites (Soft and Hard SPL ?)and proper Radio ?
Many Thx
Click to expand...
Click to collapse
Wiki is your good friend here: http://wiki.xda-developers.com/index.php?pagename=KaiserIntroductionToROM_Flashing
Hi Jack:
I had already unlock the ATT tilt using unlock code ...Do I still need to run step one below?
1. CID-unlock your device by following the instructions at pof's HTC Kaiser Hard-SPL v1 - CID Unlock & Flash any ROM to your device (4 free)-thread
BTW, I did get the "white screen" on this phone ... and follow the instructions to :
- 1a. download the 5 attached files
1b. pull out the battery, REMOVE SIM and SD CARDS !! and reinsert battery (this step *is* important)
1c. connect your PC to phone with a USB cable
2. copy JumpSPL1.56-KAIS.exe to your device and run it (make sure the USB cable is still connected). If you still get a white screen then reset your device and now try JumpSPL1.93-KAIS.exe ...
The step (2) above , copy the JumpSPL1.56-KAIS.exe to the device ...Pls advise which folder and how to run it after taking the SIM OUT ?
Thx
White Screen Issue
Hi Jack:
JumpSPL1.56-KAIS.exe to your device and run it (make sure the USB cable is still connected). If you still get a white screen then reset your device and now try JumpSPL1.93-KAIS.exe ...
Are these JumpSPL1.56 or JumpSPL1.93 run from PC or the terminal device itself ? How do I run these two ".exe" files in the device ?
Why am I getting White Screen and others devices dont get white screen ?
Thx
mmtea said:
The step (2) above , copy the JumpSPL1.56-KAIS.exe to the device ...Pls advise which folder and how to run it after taking the SIM OUT ?
Click to expand...
Click to collapse
Anywhere. I would copy it to the top level (\). Even if you took your sim out, you can close the phone page (which complaints about sim) by tapping the top right corner or the hardware red button (hang up). Then use "File Explorer", locate the exe files that you copied and click on it.
Hi Jack,
I am new to the Tilt. How do I get to "File Explorer" ? I dont see it on the menu when I open either the "setting" or "programs" ?
BTW, when I run the JumpSPL1.56-KAIS.exe, do I also need to run the Kaiser Hard-SPL v1 again ? what's the right sequence ?
Thx
RESET
Hi Jack:
Is the rest pwer+camera+ "navigation" at the same time to get Tri-colour ?
if NOT, which three at the same time can "reset" ?
Thx

[ROM] Official HTC Upgrade - Windows Mobile 6.5

HTC Snap:
ROM: 2.03.405.2
Radio: 3.47.25.29
Windows Mobile Standard (Build 5.2.21854)
http://rapidshare.com/files/2919947...igned_MAPLE_61.36t.25.29H_3.47.25.29_Ship.exe
Have fun!
For those stuck in Tricolour boot loader:
Original post: http://forum.xda-developers.com/showpost.php?p=4872255&postcount=78
Solution is as folllows
1. Downloaded rom from above (or other source if dont have a serial number to DL from HTC - although the serial number is a good check for the correct rom)
2. Run RUU_Captain_S_HTC_WWE_2.03.405.2_Radio_Signed_MAPL E_61.36t.25.29H_3.47.25.29_Ship.exe
3. Select Next so that package extracts
4. Select Start | Run | and type %TEMP%, and hit enter to open temp folder
5. Sort explorer by Date so that newest date at top
6. Locate the newest folder (eg just created), should be something like pftXXXX.tmp
7. Double click to open
8. Rename RUU_signed.NBH to MAPLIMG.nbh
9. Copy to a FAT32 microsd
10. Insert SD into handset and power on (remove battery an reinsert if required).
11. Screen will initially display tri-colour, then change to grey screen with loading
12. Screen will then show progress as initial components flashed
13. Phone will reboot at about 10% - DONT PANIC - Let phone boot to Tri-Colour, then into grey screen
14. Leave for a few minutes, loader will confirm initial components flashed ok, then continue to flash OS image
15. Once complete (progress bar reaches 100% and displays complete (or something similar)
16. Remove battery
17. Remove MicroSD
18. Reinstall battery, and power on phone
19. WM6.5 initial setup will begin, and phone should be all happy now!!
20. Ensure you rename or delete MAPLIMG.nbh from SD before reinstalling into phone.
21. Flash HardSPL!!!!!
22. Flash custom rom of your choice (ookba's look pretty good to me!!!).
Will this work on any European Snap? Downloading it now...
would this work with my x1
bad file
tried several times to use this..stops at 21% each time. downloaded a couple times thinking it might have been a bad file..in any case. doesn't work. fortunatley was able to flash stock image after
Whether it can provide the parameters of ROM production orders and related software.
Intentionally ask. Thanks.
I know it says "Maple", but does it work on the Ozone (Cedar)?
jonwold said:
tried several times to use this..stops at 21% each time. downloaded a couple times thinking it might have been a bad file..in any case. doesn't work. fortunatley was able to flash stock image after
Click to expand...
Click to collapse
sorry I don't undestand. you download the ROM and it doesn't work?
Is this the official HTC Snap ROM upgrade for certain? No Hard-SPL needed?
And which country is this for?
Same here on a MAPL100. 23% and freezes.
netnut said:
Same here on a MAPL100. 23% and freezes.
Click to expand...
Click to collapse
doesn't work?
The flash does not work on MY MAPL100. The flash freezes and then walks you through recovery, which fails.
I was able to flash back to the 1.17.531.6.
Genna77 said:
doesn't work?
Click to expand...
Click to collapse
23% != 100%
Therefore <FLASH> Failed
well, after reading through the thread I feel it's necessary to give a big
FACE = PALM
to all contributers
obededom said:
well, after reading through the thread I feel it's necessary to give a big
FACE = PALM
to all contributers
Click to expand...
Click to collapse
explain face - palm
Looks like it's designed for a European SNAP S521 (MAPL110). If the ROM doesn't see that CID, it will fail. To install it on a different Maple device, you need HardSPL or a Goldcard from QMAT.
wm 6.5
can someone post this another way i could download it instead of rapidshare my computer wont let me download from rapidshare
udK said:
HTC Snap:
ROM: 2.03.405.2
Radio: 3.47.25.29
Windows Mobile Standard (Build 5.2.21854)
http://rapidshare.com/files/2919947...igned_MAPLE_61.36t.25.29H_3.47.25.29_Ship.exe
Have fun!
Click to expand...
Click to collapse
ikando2on2 said:
can someone post this another way i could download it instead of rapidshare my computer wont let me download from rapidshare
Click to expand...
Click to collapse
No becuase it does not work. WHo uploaded this and why does it not work? Mine is CID unlocked, app unlocked, etc.
Failed at 23%
ookba said:
Looks like it's designed for a European SNAP S521 (MAPL110). If the ROM doesn't see that CID, it will fail. To install it on a different Maple device, you need HardSPL or a Goldcard from QMAT.
Click to expand...
Click to collapse
I buy my device in an european country and it's not branded that means I can use the ROM uploaded here?
thx
jonwold said:
explain face - palm
Click to expand...
Click to collapse
the specifics of where, what and why all the errors were a bit frustrating
but, alas...some clarity
ookba said:
Looks like it's designed for a European SNAP S521 (MAPL110). If the ROM doesn't see that CID, it will fail. To install it on a different Maple device, you need HardSPL or a Goldcard from QMAT.
Click to expand...
Click to collapse
obededom said:
the specifics of where, what and why all the errors were a bit frustrating
but, alas...some clarity
Click to expand...
Click to collapse
More than that, it looks like it's still not an official release. Hence, why we don't see it on HTC's website yet. I managed to cook from it and testing now. Core feels snappy and solid so far. Flashed the new radio and will be testing reception as well.

How to flash latest android version on Polaris

For some reason I can't get my Polaris to run the latest Android version (i.e. Froyo).
1. Downloaded latest kernel (polaimg-panel3-320-froyo-07-07-10.nbh)
2. Downloaded last build (Incubus26Jc's Super FroYo RLS10)
3. Put last build (.tar or .tgz file) on SD card in directory /andboot
4. Flashed by using NBH file together with RUU Update Utility
Now it gets tricky:
a) or the system reboots, vibrates twice, I see a red and blue line and then a black screen and nothing;
b) or the system reboots, I get the Android installation menu after pressing middle button, install, but after soft reset I get a "No such file found" kind of system error
Can someone help me getting Android on my old Polaris? Thanks!
SnoopThaDoctor said:
For some reason I can't get my Polaris to run the latest Android version (i.e. Froyo).
1. Downloaded latest kernel (polaimg-panel3-320-froyo-07-07-10.nbh)
2. Downloaded last build (Incubus26Jc's Super FroYo RLS10)
3. Put last build (.tar or .tgz file) on SD card in directory /andboot
4. Flashed by using NBH file together with RUU Update Utility
Now it gets tricky:
a) or the system reboots, vibrates twice, I see a red and blue line and then a black screen and nothing;
b) or the system reboots, I get the Android installation menu after pressing middle button, install, but after soft reset I get a "No such file found" kind of system error
Can someone help me getting Android on my old Polaris? Thanks!
Click to expand...
Click to collapse
Same for me with polaimg-panel3-320, but it works great with polaimg-panel1-320-24-05-10.nbh
Thanks! Got it working with the older NBH file. Not completely flawless, but it works!
Don't use the old polaris panel 1 nbh, instead download the latest and then use this utility to change it to panel 1.
http://forum.xda-developers.com/showthread.php?t=689812
Thanks!!! Got it working with the latest NBH files! Great!!!
Hey, Could anybody unswer me on two questions.
1. why we have to change from panel3 to panel1 in this nbh file?
2. what is that mean panel3 or 1? why DZO do this type of the nbh (with panel3 i mean)?
thanks a lot, ithin it will helps not only me but everyone in future who didn't know about this modification
skydemon said:
Hey, Could anybody unswer me on two questions.
1. why we have to change from panel3 to panel1 in this nbh file?
2. what is that mean panel3 or 1? why DZO do this type of the nbh (with panel3 i mean)?
thanks a lot, ithin it will helps not only me but everyone in future who didn't know about this modification
Click to expand...
Click to collapse
The panel type depends on revision of your polaris, more specifically the make of the lcd panel, see here. I just tried every panel until I found one that works, I use panel 1.
Thanks a lot, but could you please answer me again. How i will know what kind of LCD panel in my Polaris and which number i should use?
these parameters is placed in my start-up file for the haret launcher
#alloctest 0x2000
set RAMSIZE 0x08000000
set MTYPE 1723
set KERNEL zImage
set initrd initrd.gz
set cmdline "board-htcpolaris.panel_type=1 pm.sleep_mode=1 mddi.width=240 mddi.height=320 no_console_suspend clock-7x00.mddi=0xa51 hw3d.version=1"
boot
can i use panel type from here?
i have opened this polaimg-panel3-320-froyo-07-07-10.nbh file in NBH editor and saw that the HW3D is set in Eclair. Should i change this to Froyo or left as is?
Thanks a lot for the conception)))
pannel type 1...
Did I brick my Polaris?
Well, it makes me laugh looking at the last post dated back July 2010 but I decide to post anyway because I feel somebody might have passed through my problems and might help.
Following indications on this forum:
1. I downloaded:
- Kernel: polaimg-panel3-240x320-2.6.32-froyo-09-09-10_21.nbh
- Last build: Incubus26Jc's Super FroYo RLS16 All Languages
2. Put last build (androidinstall.tgz) on SD card in directory /andboot
3. Used RUU Update Utility to flash the nbh file
Everything when smoothly. When it reboots, it vibrates, "Smart Mobility" message shows up, vibrates twice and then a blank screen is displayed.
Going through this forum I think I might have used the wrong type of panel and should have used Panel 1 instead of 3. So I downloaded Windows NBH Editor and managed to change the nbh into Panel 1. Then I shall try again.
This time my Windows 7 is unable to recognize my Polaris and all it can see is a new Disk Drive with no ADB device displayed. So I installed PdaNet302.exe to implement the USB driver for HTC Android Phone but it still cannot see my device and the process aborted.
What worries me is that one step of the process requested to change a setting on the Polaris (On your phone, click Settings > Applications > Development and make sure USB Debugging is on.). Obviously I can't do that as the screen is completely white!
I believe if I can manage to have my PC talking with my device then the problem will be fixed with the panel1-based flash. But every attempt to install the USB driver for Android Phone regularly fails on my PC.
All that time the Polaris remains with the lighted blank screen and there is no way to turn it off as the on/off switch refuses to work.
Shall I buy a new phone? Thanks for your help.
Did you try flashing the phone with a regular oficial HTC rom? just try it. Put the phone in the boot mode (press camera button and another one, dont recall which one) It will change to the tri color screen. Then connect it and try it.
Also there is a modified nbh rom which includes nothing, just the tool to recover your rom. Do a search to the forum.
I recently tried to install on my Polaris and it went really wrong. And finally could recover. The file is called ROMUpdateUtility_task29. I will erase everything on the phone but later you will be able to recover it
Form that point no more experiments. Polaris was made to work with Windows Mobile. It's really unstable, video camera is useless. And so on.
PC Carvalhon rom and I can use my phone as I want.
regards.
---------- Post added at 08:16 PM ---------- Previous post was at 07:57 PM ----------
With this you can recover your phone: http://forum.xda-developers.com/showpost.php?p=6227425&postcount=7160
A second life for my Polaris
Kafkacell,
1. Following your suggestions, I successfully started the bootloader (camera touch while reset), the 3-colour screen appeared, Windows 7 recognised the device. I then flashed the offcicial RUU_Polaris_HKCSL_WWE_3.19.831.3_radio_sign_25.85.30.07_1.59.42.15_Ship and everything successfully completed. With enormous pleasure I see again my Polaris back to activity. Thanks for giving my Polaris a second life.
2. Back to Feb 2009, I flashed a pcarvalho eXtreme ROM. I don't recall any longer the version of this ROM but it was very stable and never ever crashed. Recently I downloaded and flashed most recent ROMs. From that moment on, I have no peace. It crashed 2, 3 times a week. Now I wish I could go back to the old version but couldn't find it. Perhaps pcarvalho removed them to save space? May I ask you which pcarvalho eXtreme ROM version do you currently run. Thanks.
Im currently running 29022 version (latest update from PCCarvalho).
Notes:
UPDATE:
29022 is up
this is a fix release...sound issues should be gone...had to remove htc volume control is it still has issues...fixes minor gfx glitches...updated to lastest and probably final leak version of wm6.5.3 (29022)...will from now on work on unresolved issues and finalize rom...this will still take some time due to work...
updated physics engine and utask app by ultrashot...my thanks to him...
patched htc album to novsync, faster scrolling once cache is made...
removed no longer supported apps (my phone and marketplace)...if u need them install via cab...
Here is the link for the rom: http://forum.xda-developers.com/showpost.php?p=15707730&postcount=8079
it was posted on July of this year, and so far it runs great. The trick is to not install a lot of apps in your main memory. Do it on your SD card. Also a hard reset is a must to avoid all kind of problems.
regards and glad you have your phone back to life

[NoDo ROM]Spark_Vodafone_SPA_1.20.401.00_Radio_5.54.09.21_22 .33b.50.10_NoDo by ansar

Dear forum members,
In the following A, B, C and D sections is described the flashing process
of the NoDo unbranded ROM: RUU_Spark_Vodafone_SPA_1.20.401.00_Radio_5.54.09.21_22.33b.50.10U_NoDo
A. Pre-Requisites
If your Tropy 7 is flashed with the ROM of the following release:
1. RUU_Spark_Vodafone_SPA_1.10.164.01_Radio_5.51.09.29_22.32.50.10U
then you can flash the following NoDo unbranded ROM and when you like you can comeback to your previous ROM
In case your Tropy 7 is flashed with a different of the above 1 ROM but your Firmware version at your phone settings>about>more information
is of the form xxxx.yy.zzzzz.164 i.e. with characteristic value 164
then you can also flash the following NoDo unbranded ROM, but you can comeback only to one of the above 1 ROM
B. Downloading
You must download the following 2 ROMs:
1. Download this zip ROM file: RUU_Spark_Vodafone_SPA_1.20.401.00_Radio_5.54.09.21_22.33b.50.10U_NoDo_by_ansar
2. Download this zip ROM file: RUU_Spark_Vodafone_SPA_1.20.401.00_Radio_5.54.09.21_22.33b.50.10U_NoDo_Signed_by_ansar
Extract the downloaded zip ROM files with an unzip / 7zip utility in separate folders of your choice
C. Flashing Process
In order to successfully flash the provided ROMs you must follow these steps:
1. Flash the ROM of the above (B.1.) extracted zip ROM file
2. After flashing Tropy 7 will automatically enter again in bootloader mode
3. In the screen of your computer the ROMUpdateUtility will report an ERROR
4. Ignore it and exit from ROMUpdateUtility
5. Now flash the ROM of the above (B.2.) extracted zip ROM file
6. After flashing your Tropy 7 will boot normally
7. Exit from ROMUpdateUtility and proceed with your brand new ROM
If you do not want them you can delete all operator apps, in order to have more free RAM
Beware, in WP7 deleting an application means it is deleted from ROM
D. ROM Flashing Instructions
In order to flash a ROM follow these steps:
1. Press and hold power-on/off button to power-off the phone
2. Press and hold volume-down button and then press power-on/off button to enter bootloader mode
3. When your phone enters the tricolor screen bootloader mode, release volume-down button
4. Connect your phone to your windows 7/vista/xp pc/laptop with a usb cable
5. Verify that your phone will be identified and relevant drivers will be installed by windows os of your pc/laptop
6. After completion of (D.5.) above, check the usb message connection on your phone screen
7. To flash the ROM go to your pc/laptop folder where the downloaded zip ROM file is extracted
8. Double click on the ROMUpdateUtility.exe file and strictly follow the instructions on your pc/laptop screen
Till next version enjoy!!!
Regards, ansar
I've installed this, but instead of Vodafone_SPA_1.20.401.00, I ended with Generic ROM 1.10.401.04
Links
The first link is death... The second is OK! (only 14,1MB?).
Endeavour1934 said:
I've installed this, but instead of Vodafone_SPA_1.20.401.00, I ended with Generic ROM 1.10.401.04
Click to expand...
Click to collapse
cchobbes said:
The first link is death... The second is OK! (only 14,1MB?).
Click to expand...
Click to collapse
Hi,
B.1. download link fixed
Let me know if all is ok
Regards, ansar
Update
It works perfect Ansar! A lot of thanks. My terminal is manufacture by Vodafone, but "free" (my operator is Yoigo). And it was very annoid all the branding by Vodafone. Now it desapeared... Thanks again.
Works perfectly, now it's 7.0.7389.0 without Vodafone customization (Edit: MS Zune updated it to 7.0.7390.0)
BUT like the previously posted Vodafone_SPA_1.10 version, display is still 16bit without dithering. The original ROM (Vodafone_SPA_1.09.164.06) was 32bit or maybe it had dithering everywhere except on IE.
My updated Trophy (Vodafone SPA) info:
OS: 7.0.7390.0
Firmware: 2250.09.12000.401
Hardware: 0003
Radio SW: 5.52.09.16_22.33a.50.10U
Radio HW: A.102.0.D4
Bootloader: 1.10.2250.1 (112663)
SOC: 2.2.5.0
Original version was:
OS: 7.0.7004.0
Firmware: 2250.09.10906.164
Hardware: 0003
Radio SW: 5.50.09.15_22.23.50.09U
Radio HW: A.102.0.D4
Bootloader: 1.9.2250.6
Any possibility to get the original version (1.09.164.06) to see if the problem with the display goes away?
Endeavour1934 said:
Works perfectly, now it's 7.0.7389.0 without Vodafone customization (Edit: MS Zune updated it to 7.0.7390.0)
BUT like the previously posted Vodafone_SPA_1.10 version, display is still 16bit without dithering. The original ROM (Vodafone_SPA_1.09.164.06) was 32bit or maybe it had dithering everywhere except on IE.
Any possibility to get the original version (1.09.164.06) to see if the problem with the display goes away?
Click to expand...
Click to collapse
Hi,
> Glad you also got MS NoDo update
> Display hardware is 24 bit per pixel in both models, Verizon (newer) and Spark
> Only a previous to 1.10 version of 1.08.164.02_Radio_5.50.09.18_22.24.50.09U
Regards, ansar
It don't work with my Trophy:
7.0.7008.0
2250.09.10906.166
5.50.09.15_22.23.50.09U
A.102.0.D4
1.9.2250.6(111329
2.2.5.0
Can you help me? Must i've installed before HSPL? Must it be unlocked? (If it's unlocked or not, it don't work with my trophy! )
wmplayer15 said:
It don't work with my Trophy:
7.0.7008.0
2250.09.10906.166
5.50.09.15_22.23.50.09U
A.102.0.D4
1.9.2250.6(111329
2.2.5.0
Can you help me? Must i've installed before HSPL? Must it be unlocked? (If it's unlocked or not, it don't work with my trophy! )
Click to expand...
Click to collapse
Hi,
Read more carefully section A of post #1
This is only for phones of Vodafone_SPA, Spanish operator, with characteristic value (CV) 164
Your ROM version is of CV 166, probably for a Vodafone_CH_DE operator (Austrian or Suiss Vodafone)
Regards, ansar
ansar.ath.gr said:
Hi,
> Glad you also got MS NoDo update
> Display hardware is 24 bit per pixel in both models, Verizon (newer) and Spark
> Only a previous to 1.10 version of 1.08.164.02_Radio_5.50.09.18_22.24.50.09U
Regards, ansar
Click to expand...
Click to collapse
First of all, big thanks for all these ROMs, I really appreciate your work.
Second, yes, the display is 24bit, however the images & menus are displayed in 16bit without dithering on those ROMs, except in IE which applies a dithering filter on websites.
However, ROM 1.09 and maybe previous ones, shows everything in 24bit (or maybe 16bit with dithering) everywhere except in IE, just the opposite of the newer versions.
I guess this was done on purpose to increase the overall speed of the OS (scrolling on 3rd party apps is much faster on 16bit-menus ROMs), but I'm not sure that I like giving up image quality in exchange for more speed.
I'm sorry for all the inconvenience I'm causing here, but could you post or send me a link to the Voda_SPA_1.08 version to compare?
Endeavour1934 said:
First of all, big thanks for all these ROMs, I really appreciate your work.
Second, yes, the display is 24bit, however the images & menus are displayed in 16bit without dithering on those ROMs, except in IE which applies a dithering filter on websites.
However, ROM 1.09 and maybe previous ones, shows everything in 24bit (or maybe 16bit with dithering) everywhere except in IE, just the opposite of the newer versions.
I guess this was done on purpose to increase the overall speed of the OS (scrolling on 3rd party apps is much faster on 16bit-menus ROMs), but I'm not sure that I like giving up image quality in exchange for more speed.
I'm sorry for all the inconvenience I'm causing here, but could you post or send me a link to the Voda_SPA_1.08 version to compare?
Click to expand...
Click to collapse
Hi,
It will be prepared and uploaded maybe today
Thnx for supporting
Regards, ansar
ansar.ath.gr said:
Hi,
Read more carefully section A of post #1
This is only for phones of Vodafone_SPA, Spanish operator, with characteristic value (CV) 164
Your ROM version is of CV 166, probably for a Vodafone_CH_DE operator (Austrian or Suiss Vodafone)
Regards, ansar
Click to expand...
Click to collapse
okay! Thank you! Can you send me a link with my download? i can't found it PN or here?
Sorry for my bad english, i've just 1 jear had english in my school..
wmplayer15 said:
okay! Thank you! Can you send me a link with my download? i can't found it PN or here?
Sorry for my bad english, i've just 1 jear had english in my school..
Click to expand...
Click to collapse
No NoDo available for Vodafone DE or Vodafone CH at the moment, you have to wait, and/or ask on a Vodafone_DE post, not in a Spanish one
Sorry, i don't found one for CH.. My Trophy is from swisscom.. (swisscom is operator)
i found the rom for difficult languages, but not for switzerland..
wmplayer15 said:
Sorry, i don't found one for CH.. My Trophy is from swisscom.. (swisscom is operator)
i found the rom for difficult languages, but not for switzerland..
Click to expand...
Click to collapse
Hi,
A Vodafone CH-DE ROM will be prepared and uploaded
Regards, ansar

[Q] Adding languages to unbranded HTC radar

Hi there,
This my first post, so I'll try to be short and to the point.
I just bought an sim-free HTC Radar (7720) from Expansys Japan, hoping to make a present to my Spanish mother. To my surprise, although my Japanese IS12T WP7 had several languages including Spanish, the HongKong market Radar Expansys sold me only has English and Chinese.
Since then I've been desperately trying to get a way to add Spanish display language. Found this thread on xda and thought I was saved.
Being a noob I did read every single post in the 85 pages before trying anything, unfortunately I still can't get Spanish display menu...
Here is what I did:
1) Checked I had latest Zune software (I'm running W8 CP 64bit)
2) Updated the radar up to 8107 through Zune (first 7740, then 8107).
3) Downloaded and installed WP7_update_tool
4) Downloaded and extracted WP7_Update_Cab_Sender
5) Downloaded all the Spanish language update cab files (1 for Nodo, 2 for Mango), and added them to the WP7_Update_Cab_Sender folder
6) Run the bat file, then choose "B" for backup+update
7) After a while, and a few restarts both the Update utility and the phone showed the message "Update successful".
I then went to change my display settings and found out that I still only had English and Chinese available...
Is there something I missed? Do you have any suggestions?
Right now the only thing I can think about is that maybe I shouldn't have used Zune to update. Should I try to roll back to 7740 with Zune, then update to 8107 using the Cab_Sender instead?
Thanks in advance.
Well, I got impatient so just tried to restore to the previous version using Zune...
Tried already 3 times, no particular error messages and everything seems to go fine. Yet at the end I always end up where I was, at 8107...
Am I stucked in here or is there something else I can try?
Any way of getting my phone back to 7720, or any idea of whether that would help me solve my problem ?
Having Spanish support is much more important than getting future updates... so that's not an issue...
CAB-sender takes a backup (technically "restore point") using the same mechanism that Zune does. If you didn't back up your older restore points, they were overwritten.
I'd suggest just flashing a European stock ROM. Here's a nice list of the ROMs for Radar phones: http://forum.xda-developers.com/wiki/HTC_Radar/Shipped_Roms. Make sure the device version matches (i.e. the TMoUS one probably won't work, though I don't know what hardware a Radar purchased by way of Japan will use).
GoodDayToDie said:
CAB-sender takes a backup (technically "restore point") using the same mechanism that Zune does. If you didn't back up your older restore points, they were overwritten.
I'd suggest just flashing a European stock ROM. Here's a nice list of the ROMs for Radar phones: http://forum.xda-developers.com/wiki/HTC_Radar/Shipped_Roms. Make sure the device version matches (i.e. the TMoUS one probably won't work, though I don't know what hardware a Radar purchased by way of Japan will use).
Click to expand...
Click to collapse
Thank you so much for your reply; now:
- I understood what I did wrong (over-write my previous backups when I run CAB-sender...
- Have some hope to get it done.
My hardware is: HTC Radar C110e, but unfortunately I found no file matching my current Firmware/Bootloader:
- Firmware: 1600.2200.20301.708
- RadioSofware: 16.23.03.17_16.27.00.23
- Bootloader: 2.3.160015.3(134621)
So additional questions:
- If I get one of these European ROM's, will I get also the language packs delivered by default in the European region (which include the one I want, Spanish)?
- Will my phone be updatable through the regular Zune channel afterwards?
- Should I rather get the newest, oldest, or it doesn't matter? (assuming I'll get the updates normally)
Your questions, in order:
1. Yes. These are the ROMs which are distributed on retail phones, and should include the standard language set for Windows Phones (which I'm pretty certain includes Spanish for the European phones, although I've never checked).
2. Yes. Flashing a stock ROM will make the phone behave exactly as though you'd bought it with that ROM, and it should work with Zune like any other Windows phone (including being updatable).
3. I suggest going with the newest ROM on that list, because it has the same major version number for its bootloader (2) and same revision version number for its radio (03). This reduces the risk of it not flashing correctly for some reason. That ROM is also 7740, so it will need fewer updates after flashing.
Do keep your restore point handy, in case the flash fails for whatever reason, but it shouldn't be needed. You can try recovering older restore points using the "Previous Versions" feature of Windows (requires Volume Shadow Copy service to not be disabled, and System Restore to be enabled for you user-profile disk and set to backup user files as well as system files).
Flashing a European ROM really seems like the best bet, though. You'll need to start the phone into SPL (bootloader) mode, which I believe requires turning off the phone, pressing and holding the Volume Down button, and turning it on again. You should see a screen with bands of color and info about your SPL in yellow text. At the bottom will be black text saying "Serial". Plug the phone into the computer. It will install some drivers (automatically, on Vista or later; on XP you may need to do this manually) and then the text at the bottom of the phone's screen should change to "USB". At that point, you can run the ROM Update Utility (RUU) that should have come packaged with the ROM image.
Thanks again for your precious help. It seems that's exactly what I need.
Now, sorry for asking again, but after a few hours I still couldn't find a suitable RUU... The links you gave me previously pointed to the ROM images only, any idea of where can I find "the RUU packed with those images"? Or "how to pack them myself"?
I did find a few threads in xda with a link to a RUU (here) , but it's only for the oldest version. Then they provide additional ROM images (.nbh), but it's not clear to me how can I pack those into a RUU.
Finally, I did find this other thread where someone was kind of explaining how to do it, but it seems the OP didn't even get it to work to begin with, so it doesn't feel reassuring...
Any further guidance would be appreciated.
I'm afraid you've reached the limits of my knowledge of such things. The only time I've manually flashed anything, the download came as a packaged RUU "installer" (basically just a self-unpacking archive, so far as I can tell) and included simple instructions for using it. If you tell me what file(s) your download contained, I could try to tell you how to lay them out like my phone has it, but I'm hesitant because I really don't know the intricacies of RUU.
I'm guessing you already checked the Radar forums? Alternatively, if you look at the threads for the other ROM downloads, at least some of them start with RUU and end with .EXE (which is how my download came) instead of starting with IMG and ending with .NBH (my download included some NBH files, though). Maybe grab one of the RUU bundles, run it, watch what files it extracts, and then replace the NBH file with the one you already downloaded? I can't promise this will work, but it's worth a shot.
GoodDayToDie said:
I'm afraid you've reached the limits of my knowledge of such things. The only time I've manually flashed anything, the download came as a packaged RUU "installer" (basically just a self-unpacking archive, so far as I can tell) and included simple instructions for using it. If you tell me what file(s) your download contained, I could try to tell you how to lay them out like my phone has it, but I'm hesitant because I really don't know the intricacies of RUU.
I'm guessing you already checked the Radar forums? Alternatively, if you look at the threads for the other ROM downloads, at least some of them start with RUU and end with .EXE (which is how my download came) instead of starting with IMG and ending with .NBH (my download included some NBH files, though). Maybe grab one of the RUU bundles, run it, watch what files it extracts, and then replace the NBH file with the one you already downloaded? I can't promise this will work, but it's worth a shot.
Click to expand...
Click to collapse
Well, thank you in any case for your kindness and having taken me here.
I think I'm ready to try … Just made up my mind to go in the following order:
1) Give a shot to the original RUU file (even though it has an old build of my phone); then hope that Zune updates come as you said they would (my phone unbranded phone came out of the box with Mango 7720 and it took only a few minutes to get the latest version).
2) If updates don't come, try to modify the RUU file with the newer ROM to see if I have better chance...
I'll be back to report what happened.
Well, I tried both the old and the newer ROMs, and:
- on the good side: my phone didn't get killed in the process
- on the bad side: I get an error message saying "ERROR [294] : INVALID VENDER ID" no matter what...
The ReadMe file says:
One of these error messages will appear when you use the wrong RUU to do the upgrade. RUU will check if the Model ID and Language ID are compatible with the device. Make sure you use the appropriate RUU tool to upgrade.​
So I guess I'm slowly reaching a dead end... Someone has any further suggestions???
any updates here ?

Categories

Resources