Related
I am writing this because the previous posts were very confusing to me and I think, made it seem more complicated than it needed to be. Probably because there are so many variables to this puzzle and it sucks having a potential $300 paper weight.
My apologies if step on anyones toes by reposting this. It seemed like a very pressing issue that A LOT of people are having.
It's not that big a deal, if you have the key.
The problem:
After an unsuccessful radio stack upgrade my XDA had the white screen. Then the unsuccessful upgrade due to the 1% problem.
The situation:
I purchased an unlocked T-mobile, upgraded to the ppcpe2003 4.00.05 off the Yorch site. I am using an AT&T sim card I was experiencing some dropped calls so I thought I would upgrade to the latest AT&T radio stack. I mistakenly ran the upgrade while connected to my Active Sync/cradle connection. Needless to say, the upgrade did not take and I had a dead XDA.
After reading various forum posts I decided to go back to my original t-mobile ROM, luckily, I had saved the nb1 file to my computer using the XDA developers latest tool. After using the bootloader to install from the sd card (holding the power button during a soft reset), I got the perenial white screen. during reboot I saw only the 3.56 (I think) with the radio version indicators coming up blank.
Without that original ROM file I don't think I could have pulled off this save.
Tools:
Hardware:
(1) SD reader
(1) SD Card
(1) Direct Power cable
(1) Syncing Cradle
Software:
1. Your original ROM (I think, it might work with an upgraded one)
2. Radio Stack Upgrade Files (monitor, RSUpgrade, etc.)
The Solution: (long version)
1. I had the White Screen of death.
2. through a series of soft resets, pressing the volume button ( read that in one of the forum posts) I finally got the Today screen to appear. During the boot process I still received empty radio stack info.
3. I had obtained the REPAIR files from this website and prepared those onto an SD card, which was in the unit. The xda immediately went into T-Mobile Upgrade process. I am not sure if the unit went into repair mode because of the sd card or because it was in the start up menu (read further for explaination). DO NOT OVERWRITE THE CARD!
4. the upgrade finally started its process and I got the 1% stoppage problem. After numerous trials and tribulations I was given the solution by MrDollyMaker from this forum.
!!!! THE KEY IS THE FACT THAT YOU CAN USE THE START MENU WHILE ITS IN 1% HANG !!!!
5. While the 1% hang is on the XDA, I clicked the start menu, and got into file explorer. I navigated to the /Windows/Start up/ menu on the device. I CUT/PASTED the T-mobile upgrade program into my documents (just to be safe). And soft reset the device. Sure enough, no upgrade.
6. I put the device into the Sync Cradle and performed a Guest Partnership. Using this partnership, I was able to Explore the device from my PC.
7. Using the PC, I copied the RSUpgrade files from the new AT&T radio Stack A.20.10 from my computer to the devices Windows directory: monitor_ul_bs.m0, monitor_ul_bs.map, RSUpgrade.cp64, RSUPgrade.exe
I tried to put these files on the storage card and do the compying in the device itself but I got an access error. It would not let me overwrite one of the monitor files. That's why the Sync connection to the PC is so critical.
8. I took the device off the Cradle and connected the Direct Power Cord and ran the new RSUpgrade.exe file from the device's Windows directory. Everything went swimmingly.
9. Next I re-ran the ppcpe2003 upgrade from Yorch, and I'm golden.
The Solution : simplified
Simplified Steps from White Screen:
1. get to the automatic upgrade screen by soft resetting / pressing volume button.
2. let it get to the 1% error.
3. use Start menu and file explorer and remove the upgrade from the windows start folder (I'm not sure this is required, but it worked).
4. soft reset the device and connect to sync cradle.
5. establish guest partnership.
6. copy your radio stack upgrade files to the devices Windows directory.
7. take device off cradle and connect direct power cord.
8. run RSUpgrade.exe
9. Upgrade PPC OS
Enjoy.
Comments:
- I AM NO EXPERT, just a guy with a newly fixed $300 ex-paperweight.
- You may not have to delete the Upgrade program in the startup menu. I think it makes things easier because you aren't dealing with the 1% error if your device never gets to that point.
- You may not have to go back to your original ROM
- This is my experience with my T-Mobile device purchased in the US. Your results may vary
remember the key: at the 1% error, your device is NOT LOCKED, you can use file explorer.
I would just like to thank everybody at XDA-developers, Yorch, and especially MrDollyMaker who gave me the key to unlock the puzzle.
I hope this helps simplify the matter.
Regards,
Matt
one happy guy...again.
Personally I think this one should get the sticky as it is so oftenly run into by new upgraders!
And not just because I came up with the menu function still working even with the 1% error death bit... 8)
And thanks, Matt for noting that. My instructions were given both from learning on here what to do (the RSU upgrade copying bit) and figuring out how to get past that damn 1% error bit when I forgot to copy one file over of the 4.
Something I found after testing out this method last night several times by causing a bad RSU install and getting the 1% screen of death....
As long as the ROM installed fine, don't re-install a new rom. Simply when you get the 1% error, go to the menu and get in to your file manager.
From there go to your Start folder inside the Windows folder. From there find the link to the RSUpgrade file and delete it. (Don't worry about deleting a file, this is just a link to it and we will re-install a good copy of this file)
Now, restart your PDA. It should return to your normal desktop but with no phone connection as the Radio Stack is not installed. From here, place it back on it's cradle/usb connection.
Just as stated above by Matt, you need a copy of the RSUpgade installation or a ROM upgrade insallation that includes the RSUpgrade. Unpack this, I used Winzip to do this. Find these files:
monitor_ul_bs.m0
monitor_ul_bs.map
RSUpgrade.cp64
RSUPgrade.exe
Now, using Activesync, explore to your Windows folder on your XDA and copy those files from your Computer to there. They must over write all the old files.
Disconnect from your PC and run the RSUPgrade.exe file from file manager. It worked 10 for 10 when I did it this way so it should work for you also.
The key is like Matt stated to remove the RSUPgrade.lnk file from the Start folder in Windows when you get the 1% death screen than manually copy these 4 files over. What I found was happening when you did the upgrade and got that 1% error, one or more of those 4 files corrupted or were not copied to your device. Once it has upgraded the rom, it seems to delete these files automatically also.
Goodluck and thanks for posting all of your experiance Matt. I'm quite sure it will help others A Lot!
MrDollyMaker
I only have two things to add:
1. RSUpgrade _fails_ much more often without SIM card inside the phone;
2. Your battery should be fully charged (100%) before you start the upgrade, since if it does fail, the battery will stop charging, and the next time you attempt to upgrade, you may not be able to get past 1%, even if you have power adapter plugged in. If you happen to have another XDA, you could swap batteries, or use an extended battery, if you have one.
Good luck...
lbazil said:
I only have two things to add:
1. RSUpgrade _fails_ much more often without SIM card inside the phone;
2. Your battery should be fully charged (100%) before you start the upgrade, since if it does fail, the battery will stop charging, and the next time you attempt to upgrade, you may not be able to get past 1%, even if you have power adapter plugged in. If you happen to have another XDA, you could swap batteries, or use an extended battery, if you have one.
Good luck...
Click to expand...
Click to collapse
:shock:
I never do the RSUpgrade with a sim in my phone.... Never failed unless I tried to do it with the EXE thing. But I do agree to make sure you have a full battery, but since it already is at the 1% error, you can charge it with the charger if you do not do anything when the error comes up. just let it sit and charge.
MrDollyMaker
Strange, because at some point I've had consistent failures at 13%, 16% or 21% until I put the SIM card in. Then it worked twice in a row. Maybe just a coincidence.
Also, are you sure the battery charges when the error message is up? The led stays off, and after a while the phone won't even turn on without external power.
Не помог способ с заменой батареи.
The way with replacement of the battery has not helped.
lbazil said:
Strange, because at some point I've had consistent failures at 13%, 16% or 21% until I put the SIM card in. Then it worked twice in a row. Maybe just a coincidence.
Also, are you sure the battery charges when the error message is up? The led stays off, and after a while the phone won't even turn on without external power.
Click to expand...
Click to collapse
Hmmm, every time I plugged it in or sat it on the cradle(USB power modified as listed in this website) the LED turned yellow...
But as for the SIM, yeah, that needs to be in. I was thinking SD card. I never leave my SD card in but as for the SIM, that I never take out.
MrDollyMaker
I have same 1% flash error but no succes
Thank you guys for your effort.
I have followed all the instructions step by step and I still cannot flash the radio part. It's hanging at the 1% even the files required for flash are in the windows device folder.
I have tryed to charge the baterry from the special connector on the back cause it seems not charhing trough the normal connector but I am not sure how long and what should ne the final voltage.
Please advice what should I have to do before I declare my XDA a normal pocket PC( radio part is not working )
Thanks
Silciu C.
I am now in the same boat. I tried every step as per the instruction in this forum, but had no luck at all.'It seemed I also had more problems as I tried to flash the ROM and always got an ERROR message saying that the system could not determine the data connectivity type (this messsage was in the DOS black screen, wheneever you run the Programme A/ xdatools). However, I could back up the device and the Active sync seemed to be working fine ...
I hope someone could help us ...thanks a lot in advance..
cheers...
Re: I have same 1% flash error but no succes
codectelecom said:
Thank you guys for your effort.
I have followed all the instructions step by step and I still cannot flash the radio part. It's hanging at the 1% even the files required for flash are in the windows device folder.
I have tryed to charge the baterry from the special connector on the back cause it seems not charhing trough the normal connector but I am not sure how long and what should ne the final voltage.
Please advice what should I have to do before I declare my XDA a normal pocket PC( radio part is not working )
Thanks
Silciu C.
Click to expand...
Click to collapse
Ok, first thing you need to do is turn your unit on and let the 1% screen of death come on than stop and do not do anything!
Next click in the upper left corner where the menu comes down. It will still drop down. Find your File Explorer program and launch it.
Now, browse over the the Startup folder located in your Windows folder. Inside the startup folder you should find some file refering to install or upgrade like "RSUgrade.lnk" or something like that. DELETE IT. Now let your unit reboot.
Now it should return to your normal desktop. go in and find those 4 files that caused all this hell and delete them. They are as follows:
monitor_ul_bs.m0
monitor_ul_bs.map
RSUpgrade.cp64
RSUpgrade.exe
Now that you have deleted those files, just to make sure they are cleared from memory restart the unit again.
Download a good copy of a radiostack that works with your location from yorch.net. If you wish to get the latest one, I would suggest that unless you are with T-Mobile, stay clear of it. You can also extract these 4 files from an upgrade patch file from your provider using WinZip.
Once you have a good copy of those 4 files copy them directly from your PC to your unit through active sink and into your Windows directory.
Restart your unit to clear any programs out, plug the unit in to your ac charger (not the cradle and not connected to your pc) than using File Explorer locate RSUpgrade.exe and run it. This will restart you unit but should have no problems upgrading your unit.
If you prefer, after you get it back to desktop, stop and charge it than copy the files over.
MrDollyMaker
andhy said:
I am now in the same boat. I tried every step as per the instruction in this forum, but had no luck at all.'It seemed I also had more problems as I tried to flash the ROM and always got an ERROR message saying that the system could not determine the data connectivity type (this messsage was in the DOS black screen, wheneever you run the Programme A/ xdatools). However, I could back up the device and the Active sync seemed to be working fine ...
I hope someone could help us ...thanks a lot in advance..
cheers...
Click to expand...
Click to collapse
Safest way to upgrade the ROM is using the SD card method. It is more reliable and doesn't get Errors caused by activesync.
MrDollyMaker
MrDollyMaker:
SD method has not worked for me so far...
I am not able to patch 5.17 nor downgrade to 5.15.
I used xdarit and osimagetool to write to the SD card without any luck.
Could please share some light in this matter?
Cheers...
andhy said:
MrDollyMaker:
SD method has not worked for me so far...
I am not able to patch 5.17 nor downgrade to 5.15.
I used xdarit and osimagetool to write to the SD card without any luck.
Could please share some light in this matter?
Cheers...
Click to expand...
Click to collapse
Have you tried using the OS Image Tool to write directly to the ROM?
Also, when you used XDArit, did you select that it was 5.16+ image you were writing? (when you used/didn't use the patch)
MrDollyMaker
MrDollyMaker:
Thanks again.
Yes, I selected the 5.15 ROM image to write to the SD card.
The OSImage file only accepted nb1/ nbf file types. I was not able to write the wallaby patch tool nb2 file nor wallaby 5.15 ROM image nb0 file through Osimagetool.
As you might remember, I always got an ERROR message about activesync connection whenever I tried to flash directly to the device ROM.
The first step I believed is to patch the 5.17 then either downgrade to 5.15 or go straight with the nk.nbf flash.
Is this correct?
1% ERROR PERSIST
lbazil said:
I only have two things to add:
1. RSUpgrade _fails_ much more often without SIM card inside the phone;
2. Your battery should be fully charged (100%) before you start the upgrade, since if it does fail, the battery will stop charging, and the next time you attempt to upgrade, you may not be able to get past 1%, even if you have power adapter plugged in. If you happen to have another XDA, you could swap batteries, or use an extended battery, if you have one.
Good luck...
Click to expand...
Click to collapse
I am in situation that I still have the 1% error even I have followed all the instructions from the forum.
The power led is not lightning and I can confirm that is not charging the batery. I have tryed to charge the battery using the special hole from behind but still no success.
Do you have an oppinion?
Thanks in advance,
Silviu C.
Re: 1% ERROR PERSIST
codectelecom said:
I am in situation that I still have the 1% error even I have followed all the instructions from the forum.
The power led is not lightning and I can confirm that is not charging the batery. I have tryed to charge the battery using the special hole from behind but still no success.
Do you have an oppinion?
Thanks in advance,
Silviu C.
Click to expand...
Click to collapse
One question..... What "special" hole are you talking about?
MrDollyMaker
andhy said:
MrDollyMaker:
Thanks again.
Yes, I selected the 5.15 ROM image to write to the SD card.
The OSImage file only accepted nb1/ nbf file types. I was not able to write the wallaby patch tool nb2 file nor wallaby 5.15 ROM image nb0 file through Osimagetool.
As you might remember, I always got an ERROR message about activesync connection whenever I tried to flash directly to the device ROM.
The first step I believed is to patch the 5.17 then either downgrade to 5.15 or go straight with the nk.nbf flash.
Is this correct?
Click to expand...
Click to collapse
Ok, since you have a 5.17 BootLoader, you can't use the 5.15 image write. You have to use the 5.16+ due to it is coded differently. When you write the SD card, include the patch for the 5.17 BootLoader as well with the rom so it can bypass the security feature.
MrDollyMaker
T-Mobile/MDA/O2/yadda yadda....
You know, I feel like I should be getting paid for all this advice! 8)
(J/K!)
MrDollyMaker
thanks for the advice again.
I am getting confused, really. Just repeated the same thing over again and again the past 3 days and suddenly I managed to patch the 5.17 for the second time (after over 50 tries). THis time I kept the SD with the patch tool and got another SD card to try to write 5.15 in it. After 4 hours, I managed to got it written then eventually downgraded the wallaby to 5.15. Now, the challange is the device is stuck in the wallaby screen everytime we turned it on. I had about 10 different ROMs originals as well as cooked ones from the kitchen, but had not been able to "write" one in the SD card. I used all OS image tool as well as xdarit, without any luck. the device wont recognized the ROM in the SD. I think the Wallaby 5.15 is working fine as I tested with the other SD card with the patch tool in it, the device still recognized the card as a diagnostic card.
I cant think of any mistake that I might have made in the procedure as I had (I think) followed every step of the procedures and had read different postings over and over again. :?
(mods i would appreciate if you could make this a sticky for people... ive worked long and hard trying to get this thing working again)
Ok so heres what happened to my XDA which proberly happened to yours.
I went onto the 02 site and got the latest radio stack upgrade for my xda, but i didnt have the sim in my device so once it finshed and restarted the xda it crashed because there was no sim in it. So i hard reset it.
Causing it to hang on the boot screen showing the G & U letters on the side for about 4 minutes before booting to a blank screen with the keyboard icon in the corner.
*** Please remember at the moment my status LED isnt working showing there is no battery (but still booting etc - P.S i have installed a new battery - no diffrence) ***
Heres how to get it working...... remember that everything takes longer because the XDA lags like mad.
Ive created this guide myself ive took nothing from anyone else info ive done this from scratch, it will need to be done everytime the machine runs out of power (hard resets).
---------------------------------------------------------------------------------
* when i put " + " it means AT THE SAME TIME e.g button1 + button2 = keep pressing them at the same time.
** I refer to the directional keypad centre button as the "OK" button.
Make sure you have the correct RSU Version from here :>
http://wiki.xda-developers.com/index.php?pagename=Wallaby_HT_GSMError
Download it and put the files onto an SD card.
1. Boot up the device
2. keep pressing the OK button + volume button until it shows the today screen, please note there will be no titles on the screens, HENCE NO START BUTTON.
3. Then press the contacts button + THEN OK a few times, then press the OK button this should bring up the start menu
4. CLICK programs, file explorer, select the SD Card. Then Copy RSUPGRAD.exe to : my device > windows>start up.
5. Copy the remaining 3 files to the : my device > windows
6. Soft Reset Device
7. Click on start (on the upgrade util) it will then restart the device because theres no LED for the battery (hence the 1% then fail).
8. Once started it should then start up as it did when it came out the box giving you the windows setup screen.
9. Go into file explorer and delete tha flas util file from the startup.
Thats it!
- Remember if you hard re-set the device again it will need to be re-done, i dont know how to solve this problem LONG TERM, im giving my XDA to 02 to fix it...... been as its there screw up.
----------------------------------------------------------------------
Thanks Everyone
James
Does this actually flash the gsm radio? If it does then why does it need reflashing following a hard reset?
No it doesnt re-flash it.............
All i know is that it fixes it and many people have had the same problem but had no replys so id thought id help them out :roll:
Where are he diffreneces to the instrucions on wiki????
Stefan
huh? so your saying someone has already written the instructions?
Do you have a link? it will be intresting to find out how i can get my LED working again so the system will be able to work once more.
EDIT: IF THE BATTERY LED/STATUS IS UNKOWN (as in my case)
"Maybe the upgrade will stop again at 1%, this may occur when you have an empty battery. "
Does not apply to you............... hence why my guide overcomes the one on wiki.
If you have had the situation happen to you, then you would undertsand.
would it be possible to use the xda developers 1.2 special edition ROM instead of the 1.1 version for this procedure?thats the only rom i seem to have found.
Boogie, I think you need only the radio stack not the rom if I read the post correctly. The special edition rom contains NO RADIO STACK.
That´s not 100% correct. I´ve noticed, that some ROMs wouldn´t boot up so that you can follow the procedure.....
Stefan
hey guys this is my 1st post to this forum, but for the last year or so I've found it very helpful.
I was experiencing this same issue it would just boot up and hang on the welcome screen for what seemed like an eternity. I gave up and just left it booting up and finally the today screen came up. This is what I tried and it worked. All of this was after a hard reset when I tried to upgrade the radio stack and it fell into this infinite loop of 1% and fail and reboot. I had read a couple of the procedures for doing a radio stack upgrade but here is some of what I did.
In one of the procedures it says to copy the files to ur ppc windows directory and to copy the exe file to ur windows startup directory. I figured I would bypass that in some way. After I finally got to the today screen and used my pc to copy the files to the sd card, I copied all the files to the windows directory on the device and ran the exe file from the windows directory. It worked like a charm and my ppc was back to life. It no longer took for ever to get passed the welcome screen. I hope this helps some of you that have this issue
I have a Mogul. That was Running 2.17 Official, tried to install DCD 2.1.0SPRINT, Said it installed successfully, on reboot it GETS STUCK IN HTC BLACK SCREEN. I tried to run RUU, GET ERROR 260. I can't connect through activesync either, Then I read To try to flash through SDCARD the official 2.17 renamed To TITAIMG. IT GET STUCK IN LOADING SCREEN, WHICH I LEFT RUNNING FOR OVER A HOUR, I ran out of ideas, and I hope I didn't brick My month old phone PLEEEEEEEEEEAAAAAAAAASE HELP ME
Did you not read any directions or other posts?
You need to make sure you have the new radio, otherwise any rom that is 3.16 based will do this.
Flash original 3.16 to get the radio on the phone then do DCD's rom.
Also, try not to post retarded type like that makes it really hard to understand what your trying to say.
THANKS
Well thanks I guess, and I ll will try
Go into bootloader mode before flashing to ensure a good flash.
That has to be a .nbh renamed To TITAIMG right, and if so do you have a link. For some reason mine is a .exe
JonnyBoy313 said:
That has to be a .nbh renamed To TITAIMG right, and if so do you have a link. For some reason mine is a .exe
Click to expand...
Click to collapse
Open it up with winrar (or similar) to get the nbh file. Dude this is all pretty obvious stuff remember to do some more research into the device and its quirks before doing anything else
Man I looked In the winrar, And only 1 thing is in there and it was
3.16.651.0.exe. That is why I asked for a link to the right one, and I reaserched this and other sites for four days before I tried this.
It was the best I can do without hands on, Sorry to be such a burdan.
But I though this site would help me.
JonnyBoy313 said:
Man I looked In the winrar, And only 1 thing is in there and it was
3.16.651.0.exe. That is why I asked for a link to the right one, and I reaserched this and other sites for four days before I tried this.
It was the best I can do without hands on, Sorry to be such a burdan.
But I though this site would help me.
Click to expand...
Click to collapse
Extract the exe then take a look inside that one?? We aim to help all users but it is a two way process dude
Not sure if I have A good version of 3.16
sorry I dont know tried to open but a little black screen flashed.
Should i look for a different 3.16 rom.
Every other rom I have Has a .nbh
yea my 3.16 must not be real. Might be a dumb question, but I just want to ask. Can you flash a .exe on your phone
Sorry for any confusion, Can flash .exe through sc card
Your making it harder than it is.
1) Extract the exe via winrar.
2) Manually enter bootloader mode
3) Run the upgrade from a Windows XP Machine to be safe (just run the exe).
4) Let the device start
Fixed your phone in 4 steps.
cohowap said:
Your making it harder than it is.
1) Extract the exe via winrar.
2) Manually enter bootloader mode
3) Run the upgrade from a Windows XP Machine to be safe (just run the exe).
4) Let the device start
Fixed your phone in 4 steps.
Click to expand...
Click to collapse
Don't forget step 1.5: Connect the phone to the USB port on the Windows XP machine.
hi i recently came across the new RUU_Schubert_S_HTC_Europe_4.05.401.02_Radio_5.69.09.29a_22.50.50.21_Signed_SCHUBERT_RELEASE rom which is the europe unbranded mango rom i successfully flashed my o2 uk rom to this update without using any of the hspl flashing techniques so this way will remain updateable even through zune so here goes
Step 1- download this rom http://www39.multiupload.com:81/fil..._5.52.09.16_22.33a.50.10U_Signed_by_ansar.zip
Step 2- extract this rom 2 a folder and name it something like update part 1
Step 3-download this file http://api.viglink.com/api/click?fo.../ModelID.fig&jsonp=vglnk_jsonp_13155707623901
Step 4- download this mango rom http://api.viglink.com/api/click?fo..._RELEASE.exe&jsonp=vglnk_jsonp_13155708495051
Step 5 extract the rom you downloaded in step 4 to a folder named update part 2 then drag the modeid file you downloaded in step 3 into your update part 2 folder
Step 6 flash your phone using the romupdateutility exe file in your 1st update folder at the end of this u will receive an error 270 dont panic as this is supposed to happen
Step 7 now time to flash again go to your update part 2 folder this time and click on the romupdateutility exe file and allow it to flash at the end of this you will have a fully unbranded mango 2 rom on your phone with all the updated radios
would also like to think ansar and petbede as parts of there discoveries was used in this guide hope this helps
Trying now, it worked for me to go to NoDo thnks to Petbed. I tried the oter methods to get Mango Final on mine by kept saying invalid vender ID so here goes....
Yes seems to work this way tx...daryld
no probs swanny78 glad i could help
daryld said:
no probs swanny78 glad i could help
Click to expand...
Click to collapse
Great Guide Daryld, Just thought id point out that anyone who is happy to have the HSPL can download DFT's new 7720 build, it is completely unbranded (have an O2 HD7 myself)
Great and simple way to also unbrand your phone
hi guys! quick question - the 2nd one is an application, so where does it extract to? I cant find a way - unless I need a rom extraction utility?
hi jragar if you have winrar just right clight on it and click open wif winrar it will show you all the files then drag them 2 a new folder hope this helps
daryld said:
hi jragar if you have winrar just right clight on it and click open wif winrar it will show you all the files then drag them 2 a new folder hope this helps
Click to expand...
Click to collapse
you learn something new everyday - brilliant mate, never knew about winrar opening exes!
how strange, now I get device not found error 260.
May try rebooting laptop
r u sure u r putting ur phone in bootloader mode u need to do this before flashing and u can do this by turning ur phone completely off then holding the the volume down button only while pressing the power button on u shud see a tricolour screen then when you go to flash it should recognise ur phone let me know if this helps
There may be a misunderstanding occurred.
Try to rename filename and extension from "ModelID.fig" to "ModelID.bmp" (quote not include).
You will see a real file of ModelID.fig..
It's just image not hardware id.
The real hardware id was specific into the Rom in the offset 0x0220.
Quite painless and looks good - installed no issues so far.
does this method require y device to be unlocked ?
I guess doing this way you lose all your side-loaded apps including chevron unlock?
Future Updates?
Does this allow standard updating via Zune? Or will we have to put on the original mango carrier roms when and if they become available?
I followed this and it worked a treat top post
only problem I have is some of my app purchases seem to be lost.....e.g. I paid for PES2011 and now it shows up with the BUY which I am reluctant to click in case I pay twice....any ideas?
I can't find the Modeid file?
When I open up the file in step 3 the files in there are as follows:
RomUpdateutility.exe
Enterbootloader.exe
RUUgetinfo.exe
Rapitool.exe
RUUresource.dll
Readme.doc
RUU_signed.nbh
SPL_Signed.nbh
Enterusb.fig
Enterbattery.fg
Romupdateutlity.cfg
Thanks
EDIT: Sorry ignore my post, about 10 seconds after posting my computer decided to work so got it now thanks
WasStoNed said:
I followed this and it worked a treat top post
only problem I have is some of my app purchases seem to be lost.....e.g. I paid for PES2011 and now it shows up with the BUY which I am reluctant to click in case I pay twice....any ideas?
Click to expand...
Click to collapse
Its fine just click buy and it says its already purchased and then download. The real pain is as you would expect flashing the rom you wont have any saved games but its a small price to pay. Your xbox achievements remain
bing voice stopped working
Guys I now have an issue using Bing voice and speaking and out loud. Keeps saying server not available right now...or words to that effect. Any ideas?
Yeah having the same issue here
I've loaded Pentaj#&$& (can't remember how its spelled) latest Rom on my phone, however I couldn't task29 or anything with the hd2 toolkit because it always timed out after 10 minutes and got a communication error and the HTC screen on the phone stayed at 0%. Any ideas why? I've tried two windows 7 pcs with the same results.
Secondly I want to push a sound fix cab to the phone but the only tutorial u can find for cab sender doesn't give enough info. Is there a better method and if not could someone explain to me how to set this up?
truckfreak69 said:
I've loaded Pentaj#&$& (can't remember how its spelled) latest Rom on my phone, however I couldn't task29 or anything with the hd2 toolkit because it always timed out after 10 minutes and got a communication error and the HTC screen on the phone stayed at 0%. Any ideas why? I've tried two windows 7 pcs with the same results.
Secondly I want to push a sound fix cab to the phone but the only tutorial u can find for cab sender doesn't give enough info. Is there a better method and if not could someone explain to me how to set this up?
Click to expand...
Click to collapse
you should be reading all you can about flashing and etc before you actually do it & know where to find info resources. check out the link in my signature to flashing wp7.
and there really isn't a tutorial on cab sender.
I've flashed many roms, but always came from the original WM 6.5 yadda yadda... It said to task 29 this time, but for some reason, despite seeing the phone and initializing it would never get past 0%. I've heard it may have something to do with the wrong version HSPL?
The CAB deal, I've downloaded the program and done the suggested push with backup, but it doesn't see the file... where do you have to post the CAB file to?
Anyways, even without the task 29, coming from ICS it seems to work fine.