I need some help. I have a T-Mobile US HTC Hd7 from official NODO to the "leaked Mango" early update- then updated via zune to "official Mango" when prompted it was available.
Current SW version says 7.10.7720.68 is this an "official" release?
Firmware Revision 2250.21.40503.531
Hardware Revision 0002
Bootloader Version 4.5.2250.0(129966)
Now the phone is having some hardware issues, and is authorized for a warranty exchange from T-mobile.
Before I send it back to them, I'll want it to look like it's on an official firmware.
I'm not sure if it's all the new firmwawre versions or just the unofficial update, but since upgrading the WP7 Boot logo is the red square, and factory reset defaults to the red color scheme. I'd hate to have them void the warranty over it.
There is no premangostate folder on my hard drive, so I'm assuming restoring to a backup is out of the question unless theres a way to trick zune into installing an older stock rom. Then the trick will be finding one officialy branded.
Thanks for the help folks!
that should be official OTA update for Mango.
if you are not a hundred percent sure, though...
you could always just flash a TMOUS Shipped ROM. here.
sh4d0w86.
So the red is normal?
I'm downloading a Pre No-do TMOUS rom right now, since that's how I bought the phone in the first place. Does it matter which version I chose? There seem to be 3 to choose from. I opted for the latest.
Then I should be able to connect to zune, and it will update all the way up to mango, is that corect?
Off topic, but the download just finished. Norton 360 was quick to identify the file as a threat, and quarantined. Any ideas there? I figure a false-positive.
BTW- I've been reading a bit on your intrinsicROM. Excited to give it a whirl when my new HD7 is shipped. I applaud your giant leap in the right direction.
Update: Norton is just being over-protective. All is good.
I can't post a link, but google ws.reputation.1 Silly norton.
hoopdaddy6 said:
So the red is normal?
I'm downloading a Pre No-do TMOUS rom right now, since that's how I bought the phone in the first place. Does it matter which version I chose? There seem to be 3 to choose from. I opted for the latest.
Then I should be able to connect to zune, and it will update all the way up to mango, is that corect?
Off topic, but the download just finished. Norton 360 was quick to identify the file as a threat, and quarantined. Any ideas there? I figure a false-positive.
BTW- I've been reading a bit on your intrinsicROM. Excited to give it a whirl when my new HD7 is shipped. I applaud your giant leap in the right direction.
Click to expand...
Click to collapse
the Dark theme with Red accent is normal for TMOUS Mango.
unsure why Norton would detect as a threat.
i would actually go for 1.20, which was uploaded by Football.
i am not a fan of ansar's ROMs.
and thank you for the compliment on my intrinsicROM.
and definitely looking forward to any feedback you might have when you try it out.
sh4d0w86.
So you think I might be ok to send this thing back for exchange as it is? I just thought the red was a beta thing.
Unfortunately, I cant post in the intrinsic thread yet, but I'm interested in seeing some screenshots of the new black and htc accents if any are handy.
hoopdaddy6 said:
So you think I might be ok to send this thing back for exchange as it is? I just thought the red was a beta thing.
Unfortunately, I cant post in the intrinsic thread yet, but I'm interested in seeing some screenshots of the new black and htc accents if any are handy.
Click to expand...
Click to collapse
it should be yes.
but as i said, if worried, maybe just flash the TMOUS Mango ROM, just in case?
better safe, then sorry, right?
i haven't figured out how to take screenshots, yet, unfortunately.
but if you look at any Nokia WP7 due out...
they use the Light theme with Black accent.
sh4d0w86.
Getting off topic here, but I thought I'd give intrinsic a shot on this junk phone before I send it back.
I'm using 7zip. It gives me an arror message when I extract the beta 3 NBH.
Unsupported compression method.
hoopdaddy6 said:
Getting off topic here, but I thought I'd give intrinsic a shot on this junk phone before I send it back.
I'm using 7zip. It gives me an arror message when I extract the beta 3 NBH.
Unsupported compression method.
Click to expand...
Click to collapse
what are you using to extract it?
it extracted fine, for me, with 7-zip.
sh4d0w86.
Winzip 15.5 (9579) and 7Zip 4.65 both report the same error message: "unsupported compression method" I tried the beta 2 with the same result.
No issues with other Zip files. No problem installing dotcompt's Deep Shining ROM.
hoopdaddy6 said:
Winzip 15.5 (9579) and 7Zip 4.65 both report the same error message: "unsupported compression method" I tried the beta 2 with the same result.
No issues with other Zip files. No problem installing dotcompt's Deep Shining ROM.
Click to expand...
Click to collapse
i can extract the 7-zip...
worked with 7-zip 9.22 beta and ExtractNow.
sh4d0w86.
That worked. Updated my 7-zip.
hoopdaddy6 said:
That worked. Updated my 7-zip.
Click to expand...
Click to collapse
yeah. good thing. just noticed how old of a version you were using. haha.
sh4d0w86.
Related
Good evening everyone,
I didn't want to drop this in development yet, as it's more speculation and inquiry.
I was in discussion with an HTC rep tonight after having issues (more of course) with my Rogers Post-911 update 1.89.631.1 SPL 1.33.0010.
Here is the conversation:
Sam: Hello Bryan, I understand that you would like to reflash the latest update available for your Rogers Dream. This can be downloaded here: http://www.htc.com/ca/support/dream-rogers/downloads/. Instructions on (re)installing the update are provided after you click More.
Me: Thank you for providing the details. I was unaware that the RUU would allow a user to re-install the current version. If I continue to receive the same issues, is it possible to resort to the old firmware at my own risk?
Sam: Hello, Unfortunately, after the device has been updated, we have no way for you to go back to the previous ROM, since we only host the latest updates on our website. Some of our users may host these ROMs on forums and other websites, but we cannot sanction you going back to previous versions. To answer your question, if you were able to find the previous ROM for your device, you could flash your device back at your own risk. Sincerely, Sam HTC Tech Support
Me: Hello again Sam, I have no issue acquiring the previous ROM. I was curious if the HTC update utility will support an older ROM than the one located on the phone. Thanks!
Sam: Hello Bryan, The phone doesn’t have anything to do with the update process, other than that the phone receives the new (or older in this case) software. ROM Update Utility packages work by placing the phone into bootloader mode, removing the previous ROM, and installing a new one. Software-wise, there is little to no risk in changing ROM versions. The reason that we don’t suggest going to older versions of the operating system after updating is because the RUUs also update the radio version on the device. After the radio version has been updated, it cannot be downgraded. This is likely to render the phone unusable. Sincerely, Sam HTC Tech Support
Me: Hello again Sam, Thank you for explaining the forced update of the radio. I was unsure if I could downgrade, given my SPL version. Thanks again for the great support!
Click to expand...
Click to collapse
That was fun to play along with ^-^. Now, either he's completely wrong, or he has a point: Although you cannot backtrack on a radio, you can backtrack on the firmware and the SPL.
If you desire, I have the extracted updater in zip format if you wish to tinker with it. I will be contacting Haykuro to work with him to ensure that he has a test subject.
I know the JTAG project is making progress, but I'd rather do a softmod without disassembly.
In regards to my primary question:
If I have a ROM with a mismatched radio, will the phone still boot?
A step forward??
Hey XBRAV,
Nice to see you on here too. So, I got the 1.86.631.1 Rogers Dream Update and obviously the update process failed saying that it was an older version. However, the phone remains in RUU USB mode until you close the HTC updater, and this is where things got interesting.
You can still interact with the phone through fastboot at this point, and sending commands like fastboot flash recovery/hboot/etc is not met with the usual "remote: not allow" but rather fails an INFOsignature test. I tried flashing a custom recovery and all available G1/Dream SPLs but with no luck, citing the same error every time. My question, then, is how do we determine what signature it wants and can we sign SPLs ourselves? Thank you for your thoughts and suggestions.
EDIT
Oops, I see now that this has been discussed on a number of threads as it is the fastboot oem rebootRUU function. It's a shame that a lot of the functionality is reduced even in this mode. Looks like it's back to waiting for another softmod solution or going the JTAG route.
As for XBRAV's question, I think a newer radio with an older ROM would still work fine. Many update their radios as newer ones become available, and this can be done safely through fastboot as lbcoder discovered. However, I think the only problem would arise when going from the EBI1 3x series radios to the EBI0 2x ones while having a rom that is not properly ported for that specific radio. I imagine this would not be the case if you're changing between newer and older Rogers roms as they have only ever been EBI1. I hope that makes sense. Anyone may feel free to correct me as I'm still quite new to all this.
Cheers.
Hi
I've try different build of Android the last week and I always get some error when I do some messaging. Half of the message I receive are in chinese instead of English or French.
I have try
Scoot_CyanogenMod_7_alpha_RLS1_All_Language
myn-WarmDonut-04-24-2010-240x320-110
Incubus26Jc's Super FroYo RLS16 All Languages
I have done some reading in the forum but didn't find the answer about this.
Please help.
Thanks
Le_MaiTre
change radio firmware.
What do you call radio firmware ??
got othe windows section and search radio...
What is the latest version I should have ??? Some threat are old and I can't figure out what is the latest version ...
Thanks
I've done a lot of research but didn't find the right answer for me. I have install the rom with the stepby step instruction in this page ...
http://forum.xda-developers.com/showthread.php?t=636024
I have also download the file from here that I have rename it and put it in the folder with the RUU Update Utility. I have try the file lastest-vogue.nbh
http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
Everything work perfectly except the text message. I have also notice that in the setting when I go to about phone. The baseband version is unknown. I think that it's the problem but I don't know what to do to solve the problem.
Can someone help me ???
Thanks
the files in http://it029000.massey.ac.nz/vogue/files/?C=M;O=D are outdated
Ok do you know where I can find the file that are the most up to date ???
Le_Maitre said:
Ok do you know where I can find the file that are the most up to date ???
Click to expand...
Click to collapse
You could try here: http://www.androidonhtc.com/wiki/Latest_Builds_(Vogue) or here: http://sourceforge.net/projects/androidhtc/files/. Hope this helps.
theonew said:
You could try here: http://www.androidonhtc.com/wiki/Latest_Builds_(Vogue) or here: http://sourceforge.net/projects/androidhtc/files/. Hope this helps.
Click to expand...
Click to collapse
The first link doesn't work and the second give me some file but I don't know what to do with this ... There's no explanation on the website ...
Le_Maitre said:
The first link doesn't work and the second give me some file but I don't know what to do with this ... There's no explanation on the website ...
Click to expand...
Click to collapse
Here's how to change the radio
http://forum.xda-developers.com/showpost.php?p=5057656&postcount=6
here's the whole thread
http://forum.xda-developers.com/showthread.php?p=5057656#post5057656
And you need to find the latest radio for your phone possibly one that worked with windows mobile 6.51. Before you ask which one ..I have to say that I won't be able to help you as I don't own a vogue. I guess you could make a new thread and ask users which radios work best for them on vogue.
Le_Maitre said:
The first link doesn't work and the second give me some file but I don't know what to do with this ... There's no explanation on the website ...
Click to expand...
Click to collapse
The link has been fixed and go here for instructions: http://techf1.blogspot.com/2010/04/coming-soon-installing-android-21-on.html. I would advise you to use the gingerbread image.
theonew said:
The link has been fixed and go here for instructions: http://techf1.blogspot.com/2010/04/coming-soon-installing-android-21-on.html. I would advise you to use the gingerbread image.
Click to expand...
Click to collapse
I have forgot to say that my installation is on NAND so I can't use haret.
-Arturo- said:
Here's how to change the radio
http://forum.xda-developers.com/showpost.php?p=5057656&postcount=6
here's the whole thread
http://forum.xda-developers.com/showthread.php?p=5057656#post5057656
And you need to find the latest radio for your phone possibly one that worked with windows mobile 6.51. Before you ask which one ..I have to say that I won't be able to help you as I don't own a vogue. I guess you could make a new thread and ask users which radios work best for them on vogue.
Click to expand...
Click to collapse
I have download the files for the radio 3.42.50 on the tread that you gave. I rename the .nbh in RUU_signed.nbh and put it on the Rom Update utility and start the update.
It gave me the right radio and I click on update. I load to 8 % and after gave me an error
Error 328 Invalid Command
I have to exit the update process and the phone reboot to the old Scoot CyanogenMod that is already install with the old radio. I think I miss something but can't find it.
Can someone help me ??
Le_Maitre said:
I have forgot to say that my installation is on NAND so I can't use haret.Can someone help me ??
Click to expand...
Click to collapse
Go here for the step by step instruction guide for NAND installation and links to some files: http://forum.xda-developers.com/showthread.php?t=636024. I hope this helps.
Le_Maitre said:
I've done a lot of research but didn't find the right answer for me. I have install the rom with the stepby step instruction in this page ...
http://forum.xda-developers.com/showthread.php?t=636024
I have also download the file from here that I have rename it and put it in the folder with the RUU Update Utility. I have try the file lastest-vogue.nbh
http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
Everything work perfectly except the text message. I have also notice that in the setting when I go to about phone. The baseband version is unknown. I think that it's the problem but I don't know what to do to solve the problem.
Can someone help me ???
Thanks
Click to expand...
Click to collapse
theonew said:
Go here for the step by step instruction guide for NAND installation and links to some files: http://forum.xda-developers.com/showthread.php?t=636024. I hope this helps.
Click to expand...
Click to collapse
Like I already said. I've follow the step by step on your post but someone tell me that my messaging error are from the outdated radio on the step by step instruction. He found link from an other forum that give me the latest radio but when I try to re-install it I get an error and I do not know what to do .... I'm lost .....
Le_Maitre said:
Like I already said. I've follow the step by step on your post but someone tell me that my messaging error are from the outdated radio on the step by step instruction. He found link from an other forum that give me the latest radio but when I try to re-install it I get an error and I do not know what to do .... I'm lost .....
Click to expand...
Click to collapse
The only other thing I can think of is to have the latest radio from Windows Mobile. When you were using windows mobile, did you ever flash a custom rom? If you did then that may have fixed your problem if you were using the latest radio version. If you weren't, then I guess if you want to fix your problem, you're gonna have to flash a windows mobile 6.5.x rom with the latest radio and then flash android.
theonew said:
The only other thing I can think of is to have the latest radio from Windows Mobile. When you were using windows mobile, did you ever flash a custom rom? If you did then that may have fixed your problem if you wre using the latest radio version. If you weren't, then I guess if you want to fix your problem, you're gonna have to flash a windows mobile 6.5.x rom with the latest radio and then flash android.
Click to expand...
Click to collapse
Yes I have flash my phone with WinMo before. I was using NFSFAN Rom before switching to Android 2 months ago ...
Le_Maitre said:
Yes I have flash my phone with WinMo before. I was using NFSFAN Rom before switching to Android 2 months ago ...
Click to expand...
Click to collapse
When you were using it, what was your radio version? If it was the latest, then it should have been 3.42.50. I read that for "Bell" users like you, the radio 3.42.50 is recommended for this installation.
Le_Maitre said:
I have forgot to say that my installation is on NAND so I can't use haret.
I have download the files for the radio 3.42.50 on the tread that you gave. I rename the .nbh in RUU_signed.nbh and put it on the Rom Update utility and start the update.
It gave me the right radio and I click on update. I load to 8 % and after gave me an error
Error 328 Invalid Command
I have to exit the update process and the phone reboot to the old Scoot CyanogenMod that is already install with the old radio. I think I miss something but can't find it.
Can someone help me ??
Click to expand...
Click to collapse
did you read the whole post that i had provided before??? there isasolution to yourproblem there.
Way 3 (I know I said two ways...): There are a few
stock roms that come with new radios. One of
them can be downloaded directly from HTC and it
is for the Sprint Touch. This one comes with Radio
3.42.30
The other one is for Bell Mobility and this one
comes with Radio 3.42.50.
Why am I giving "Way 3" if the other two options
seem much easier?? I have run into the problem
where my device would not let me flash other
radios than the one that I had. SD card method
did not work and the RUU started out fine but
quits at 8% rebooting my phone and displaying
Error 328 in the RUU on the PC. Anyway, here are
the links...
-Arturo- said:
did you read the whole post that i had provided before??? there isasolution to yourproblem there.
Way 3 (I know I said two ways...): There are a few
stock roms that come with new radios. One of
them can be downloaded directly from HTC and it
is for the Sprint Touch. This one comes with Radio
3.42.30
The other one is for Bell Mobility and this one
comes with Radio 3.42.50.
Why am I giving "Way 3" if the other two options
seem much easier?? I have run into the problem
where my device would not let me flash other
radios than the one that I had. SD card method
did not work and the RUU started out fine but
quits at 8% rebooting my phone and displaying
Error 328 in the RUU on the PC. Anyway, here are
the links...
Click to expand...
Click to collapse
I've read the whole post but I don't understand the 3rd way. If I click on the Bell rom with radio 3.42.50 it bring me to the HTC site and there nothing to download.
I've try to download the All Above Radios zipped. It gave me 3 files in a zip. I rename the file 3.42.50 in RUU_signed.nbh and put it in the folder of the ROMUtilityUpdate. Maybe is there I do something wrong ...
Did I miss something ???
Ok,
So all of us HD7s owners know that the Mango update for our device has not been released via Zune yet. Or so we thought. I discovered something yesterday completely by accident.
I had my device on the RTM 7720 up until last weekend. I have other phones and decided to restore my HD7s to stock (i.e. NoDo) and wait for the update. Well, I was missing my WP7 Mango so I tried to reinstall the RTM using the procedure found here on XDA. So, I start doing the following steps:
1) I uninstalled my current version of Zune.
2) I installed the version of Zune that comes with the download for the RTM method.
3) I install the updatewp tool from the Zune version in the last step.
4) I have a dev account and I unlocked my HD7s with the appropriate tool.
5) I perform the first step of the RTM method, which is to run the provision tool included in the download.
6) Start Zune and check for an update. This is where it gets good.
So, everything is moving along at this stage. I see Zune giving me the 7403 update. Zune then proceeds to start updating my phone. After the first update, Zune updates itself. It then begins installing the beta cleanup update. I think to myself, that is strange. The next thing I see is Zune installing 7720 Final version. It never even updated the device to 7712. It went from 7390 to 7403 to beta cleanup to 7720 Final. From what I can tell, I have the final release for the HD7s. I do not have a stock device to compare version numbers though.
I should also point out that I was now able to install the Connected Media app. I was not able to do this with the RTM 7720 version. I am getting an error when trying to use it though, saying "Sorry, your phone is not supported by this application." All other Mango apps I have tried are working though.
Just thought I would share this little tid bit for those of us that are impatient.
naplesbill said:
Ok,
So all of us HD7s owners know that the Mango update for our device has not been released via Zune yet. Or so we thought. I discovered something yesterday completely by accident.
I had my device on the RTM 7720 up until last weekend. I have other phones and decided to restore my HD7s to stock (i.e. NoDo) and wait for the update. Well, I was missing my WP7 Mango so I tried to reinstall the RTM using the procedure found here on XDA. So, I start doing the following steps:
1) I uninstalled my current version of Zune.
2) I installed the version of Zune that comes with the download for the RTM method.
3) I install the updatewp tool from the Zune version in the last step.
4) I have a dev account and I unlocked my HD7s with the appropriate tool.
5) I perform the first step of the RTM method, which is to run the provision tool included in the download.
6) Start Zune and check for an update. This is where it gets good.
So, everything is moving along at this stage. I see Zune giving me the 7403 update. Zune then proceeds to start updating my phone. After the first update, Zune updates itself. It then begins installing the beta cleanup update. I think to myself, that is strange. The next thing I see is Zune installing 7720 Final version. It never even updated the device to 7712. It went from 7390 to 7403 to beta cleanup to 7720 Final. From what I can tell, I have the final release for the HD7s. I do not have a stock device to compare version numbers though.
I should also point out that I was now able to install the Connected Media app. I was not able to do this with the RTM 7720 version. I am getting an error when trying to use it though, saying "Sorry, your phone is not supported by this application." All other Mango apps I have tried are working though.
Just thought I would share this little tid bit for those of us that are impatient.
Click to expand...
Click to collapse
Very nice - I was wondering about that. Now if only it can be done w/out dev unlocking...
I imagine this procedure might work with a chevron unlock.
This post is reserved for future use
naplesbill said:
I imagine this procedure might work with a chevron unlock.
Click to expand...
Click to collapse
This post is reserved for future use
Mango for AT&T HD7s
eknutson said:
Very nice - I was wondering about that. Now if only it can be done w/out dev unlocking...
Click to expand...
Click to collapse
I faxed AT&T a copy of my receipt and my IMEI number and they sent me an unlock code. My phone updated to mango once it was carrier unlocked
digioia2001 said:
I faxed AT&T a copy of my receipt and my IMEI number and they sent me an unlock code. My phone updated to mango once it was carrier unlocked
Click to expand...
Click to collapse
And everything worked fine? No issues with it being an HD7s vs. an HD7? So close to the actual update now... I did try flashing to the Mango beta, but it got messed up along the way and I just re-flashed to my stock backup after a Sunday morning of messing around with the thing.
digioia2001 said:
I faxed AT&T a copy of my receipt and my IMEI number and they sent me an unlock code. My phone updated to mango once it was carrier unlocked
Click to expand...
Click to collapse
I think when you say "unlock" in this sense, you mean carrier unlock. From my understanding, the carrier can unlock the hd7s so you can use it on other carriers using sim cards (ex t-mobile in the us, 3 or china mobile in asia). I dont think that will dev-unlock, though. Let me know if that's not the case, because I will definitely be all over it!
Well, we'll see if Mango comes out today for the HD7s, as WPCentral is reporting here: http://www.wpcentral.com/ATT-hd7s-mango-update-starting-today-rumor
I have an AT&T branded HD7 (it says HTC T9295 in Zune) which I'm trying to update. I think the phone was originally a pre-release handset and the OS version is 7.0.7348. I can copy and paste so perhaps this is pre-NoDo build? Anyway, trying to update to NoDo and beyond - the phone plus Zune is telling me that an update (7392) is available. Zune is allowing me to get right to the last step of the update process before giving me a 80180048 error. I've tried the Windows Phone Support tool but get "The tool cannot recover this phone. Please contact technical support." Any help would be greatly appreciated!
you could 'start from scratch' and just flash the stock Shipped ROM...
the stock Shipped ROM is already NoDo. Shipped ROM link in my signature.
sh4d0w86.
Ah many thanks I'll give it a go now!
dedhandi said:
Ah many thanks I'll give it a go now!
Click to expand...
Click to collapse
welcome.
sh4d0w86.
Worked like a dream, cheers!
Both a Q and a warning, as this was a new update.
I've had Mango for about 2 / 3 weeks (delivered through Zune)- yesterday received a notification of an update by HTC (There is chatter that this is the Wifi hotspot update?), which Zune failed to restart my HD7, giving me a bricked device.
Right now the device is powering on, giving one vibration to say hello, and then proceeding to give me 7 vibrations. I can reach both the bootloader and the recovery menu, but neither have been of any help.
This is what my bootloader screen looks like:
Code:
PD29100 SS-BC (4k)
SPL-5.0.2250.1(121000) MNG
MicroP(LED) 0x07
Touch S1(v2.B#1625)
SD SANDISK 15193MB
Partition Info v211v413
CRC is
Code:
BL CRC-0x7E63640E
OS(SI) CRC-0xB7077908
My warning is that I haven't done any ROMing on this device (it's unlocked and unbranded) so far, this was pure OTA- so if anyone gets this update in the next day or so, just be warned.
My concern is these flashing tools don't appear to support SPL v5. Does anyone have any ideas on how to get this show on the road? Downgrade the ROM and go from there?
have you tried recovering with Zune back-up?
have you tried flashing a stock Shipped ROM?
sh4d0w86 said:
have you tried recovering with Zune back-up?
have you tried flashing a stock Shipped ROM?
Click to expand...
Click to collapse
Cheers for the reply.
Zune backup recquires to be able to go into the mode that Windows Phone Support tools needs, my phone gives the 7 vibrations before then.
Can I flash a stock shipped ROM without using HSPL / RSPL?
wint3rmute said:
Cheers for the reply.
Zune backup recquires to be able to go into the mode that Windows Phone Support tools needs, my phone gives the 7 vibrations before then.
Can I flash a stock shipped ROM without using HSPL / RSPL?
Click to expand...
Click to collapse
yes, you can flash a stock Shipped ROM specific to your phone without XSPL.
check my signature for a link to all Shipped ROMs for the HTC Schubert.
On trying to put on the SEA ROM it seems to connect OK, comes up with the progress bar to 0% on the device, and then errors out to this:
http ://img13.imageshack. us/img13/2425/flashwrite .jpg
Any ideas?
wint3rmute said:
On trying to put on the SEA ROM it seems to connect OK, comes up with the progress bar to 0% on the device, and then errors out to this:
http ://img13.imageshack. us/img13/2425/flashwrite .jpg
Any ideas?
Click to expand...
Click to collapse
error 226? unsure of what exactly that is.
had you tried reflashing?
No, this is the first time I've tried anything other than the OTA updates provided by Zune
Should I put the call through to HTC, or is there a way of taking back my SPL version so I can get a ROM on here? I've got SPL 5, which I can't find anywhere on XDA :S
Holy hell...was just about to get this update yesterday and just like that, decided against it...
Thanx a ton man...its been 2/3 weeks for me too with the Mango update.
Also, have U tried contacting the WP7 support on Twitter, which from my personal experience is quite hopeless and abject. But its also your best bet right now...
I've put the call out on twitter, I'll let you know how it goes.
wint3rmute said:
I've put the call out on twitter, I'll let you know how it goes.
Click to expand...
Click to collapse
In my honest opinion they are quite hopeless. They will answer as if they are obliged to you and they owe you something. Anyways, its a personal experience.
Any luck? Did u hear anything from the (abject) Twitter support team ?
BTW, my update went fine. Finger crossing does help
No reply on anyone from twitter. HTC email support sent me through hard reset instructions, which I've already tried. Should be on the phone with them tomorrow with regards to the issue, will update this thread if there is a way of fixing this.
Had two mates at work whose updates went through fine as well :| Probably worth noting my phone and PC (Zune) region is set to US whilst my ROM is most certainly the SEA one. Maybe something's messed up there.
would out what Error 226 is...
it is a 'file write' error, suggesting the image (.nbh) is bad.
i suggest a redownload.
also, that ROM is now publicly available.
perhaps try flashing that?
link in my signature, as usual.
Thanks for your reply, getting an error similar to this:
http://forum.xda-developers.com/showthread.php?t=1263315
Except that makes sense, as my device is actually an SEA one, not a European one. Any idea when the shipped ROM for SEA will be available?
wint3rmute said:
Thanks for your reply, getting an error similar to this:
http://forum.xda-developers.com/showthread.php?t=1263315
Except that makes sense, as my device is actually an SEA one, not a European one. Any idea when the shipped ROM for SEA will be available?
Click to expand...
Click to collapse
i do not know when or if it will, sorry.
hopefully, DFT releases a new version of XSPL soon.
sh4d0w86 said:
i do not know when or if it will, sorry.
hopefully, DFT releases a new version of XSPL soon.
Click to expand...
Click to collapse
Okay. Do you have any insight into how these ROMs are released? Is it a matter of capturing it off another device that has the update?
I might be able to help in this regard, have a few mates with HD7 phones (Mine is personal but it's also the standard company-issue phone)
wint3rmute said:
Okay. Do you have any insight into how these ROMs are released? Is it a matter of capturing it off another device that has the update?
I might be able to help in this regard, have a few mates with HD7 phones (Mine is personal but it's also the standard company-issue phone)
Click to expand...
Click to collapse
i don't, no. i know you can dump a ROM from a device with JTag.
but i don't know how to do that because it dumps as a 'bunch of mess.'