Related
I have totally hosed my TMobile device and I am looking to rebuild straight to the 1.1 build instead of going back to TMobile first (although that may be an option)...
If I can reflash with the TMobile ROM (256k or so), which files and how would I load the system up with the 1.1 build???
Or would I be better off rebuilding to TMobile original and then running the executable to load the 1.1 build???
Any help would be appreciated...
Todd
OldManTodd said:
If I can reflash with the TMobile ROM (256k or so), which files and how would I load the system up with the 1.1 build???
Or would I be better off rebuilding to TMobile original and then running the executable to load the 1.1 build???
Click to expand...
Click to collapse
Not sure I understand. The 256 k you're referring to is the size of the bootloader, maybe? You don't need to change the bootloader, it's fine the way it is.
Unless it's a 5.17 bootloader, in which case you may want to replace it with something more 'userfriendly', so to speak (5.17 has a feature to prevent you from easily flashing the device, we hacked said mechanism, but it's still a hassle)..
Anyway: your goal is to replace the OS. If your device still talks to ActiveSync, just run Jeff's exe file that installs our Special Edition ROM v1.1 and you're all set. If it does not, get an SD-acrd reader/writer for your PC, and use XDArit and the bootloader method to flash your ROM.
Got the card reader....
I am back at ground zero.. The 256 is the actual baseline from what I understand....
Basically the first step to upgrade is to backup the ROM and that is what is toast...
At this point I can't get to activesync, the device just resets it self over and over again (albeit it slowly)...
I have a version 5.15 bootloader, I am ok there...
I am going to search around in here to use XDARit (downloaded already) and try to find the bootloader method to flash my ROM (I am trying to find a good copy of the TMobile ROM now)..
Thanks for any assistance you can lend...
Todd
update - I can't seem to locate the Bootloader Method you are referring to?? - Todd
If you drag to winzip, you'll see the v1.1 Special Edition ROM nbf-file in there. You can just read that to SD-card using XDArit, and you'll be all set. No need to first install T-Mobile's ROM.
I downloaded the exe already...
basically at this point I formatted my only backup due to the only card avail is 128meg...
I will run the XDArit now....
After I write to the card, what do I do on the phone to load the software from the card???
Re: I downloaded the exe already...
OldManTod said:
After I write to the card, what do I do on the phone to load the software from the card???
Click to expand...
Click to collapse
Simply insert the card and boot into bootloader (pressing power while resetting), and it will ask you to press the action button if you want to flash the contents of the card. The action button is the center of the big rocker key.
man alive!!! I can't win....
XDARite is blowing off when trying to write to the SD card...
To use XDARite you just use the Fat format??? I am rebooting with card in writer so that the volume will show on startup...
I have a Lexar Card reader and trying to run XDARite from XP and selecting the ~32 meg .nbf file from Jeff's update....
Thanks again for any thoughts...
Todd
p.s. You are a busy poster today
Re: man alive!!! I can't win....
OldManTod said:
XDARite is blowing off when trying to write to the SD card...
Click to expand...
Click to collapse
Blowing off ?? I'm afraid I'm not familiar with this terminology.
To use XDARite you just use the Fat format??? I am rebooting with card in writer so that the volume will show on startup...
Click to expand...
Click to collapse
No, the card is written to in RAW mode by XDArit, so XDArit destroys any file-system present on the card when it writes to it. It says so on the page, just read...
p.s. You are a busy poster today
Click to expand...
Click to collapse
Look who's talking!
XDArit not writing to USB device....
that is where I am stuck at... for some reason, I can read/write to the card, but XDARit cannot....
Has anybody experienced this before with XP and an External USB device????
T
mine was fine. i used xdairt to load the image. actually for me my activestink disconnected while i was loading the rom image and i had to use sd card.
alex
hi there, oldmantodd,
my usb sd-card reader is also not working, but i managed to rebuild my xda in the following way:
first thing you need is another xda/mda whatever
second you boot this device in bootloader mode, press the rec-button ( the one on the side) and choose backup ce
once you backupped this devices operating system, just boot your wrecked device in bootloader mode with the sd-card containing the backup
now it asks you if you want to download teh ce from sd card,
just confirm this and after a while your device is fine again..
jope this helps!!
best regards tim
not work if using 5.17 bootloader, i have 2 xda (1 damage) and 256m sd card, any suggest how to solve this problem?
i dont have card reader, getting frustasion,plsss help
thz
USB Lost connection during upgrade
For those who noticed this "Lost USB COnnection" problem during the installation of the ROM. I found that as long as you don't resit the unit, just carefully disconnect it from the usb, move the mouse over the active sync icon by your clock so it dissapears or you only have 1 left. (restart if needed if none are there) and than reconnect the update program will resume the upgrade or restart it. I noticed this problem on 2 rom updates. On one of the times I actually had to re-run the update program after I reconnected the usb sync cable (cradle)
Flished perfictly well!
I have bootloader 5.15
If someone has the ORIGINAL (any version is good to me) of T-Mobile's Rom's as mine got screwed before I could back them up... Hence the reason for my upgrades... I would love it if you could leave me a note as I really could use the originals to re-install.
Hey Tim...
Is that the same as going to boot mode and the pressing contacts and writing ce+boot???
I am at the point where I have probably got to start from the very beginning...
I tried the method of writing ce+boot from another device and then flashing mine and no luck...
I am starting to get desperate....
Thanks for any help...
Todd
yeah, it is the same as pressing contacts and write boot+ce, after that is written ob the sd-card just put that sd-card in your damaged device and boot it in bootloader mode.
it will then say something like sd-card contains boot+ce, do you want to download, the press the action button and there you go - your damaged device is being flashed and everything should be ok..
good luck
I tried that this morning....
is it possible I hosed my device beyond recognition???
T
I can get to usb flash mode...
would that do me any good???
Right now... the device comes up with unrecognized card and then sits for a while with the keyboard and the error screen to enter a name for the card... and after a bit it soft resets and goes through the same thing...
T
Ok, sounds like you didn't boot to the bootloader... If you do a hard reset (the little button with the battery indicator above it) and hold the power button (the button on the top left) while you turn it back on it will start the boot loader. Make sure your card with the Boot+CE writen to it is in the expansion slot before you do this and it will automatically start in the Autoload screen. Just push the action button (the control pad straight in) to start.
Hope that bit helped.
You can get to the bootloader from the soft reset button...
as well...
When I do that of course I get to GSM error....
Can anyone verify to rebuild from the ground up from another device I would follow these steps:
Boot Good device from power+soft reset
At menu press contacts button
at the flash tools menu select CD+Boot to SD
Let the software write to the SD then remove card
On my device (which needs rebuilt)
Press Power and Boot
Unit will detect info on card
and just press action button
That is my understanding, however, there are other options on the flash tools menu that I have not investigated...
Any help as always would be appreciated...
Todd
Re: You can get to the bootloader from the soft reset button
OldManTod said:
Boot Good device from power+soft reset
At menu press contacts button
at the flash tools menu select CD+Boot to SD
Let the software write to the SD then remove card
On my device (which needs rebuilt)
Press Power and Boot
Unit will detect info on card
and just press action button
Click to expand...
Click to collapse
The sequence above should work (I assume you know 'press power and boot' means keeping the power button pressed while soft-resetting).
You could write only CE to SD-card, no need to transfer the bootloader. If the above works, it means the receiving device has a functioning bootloader, if it doesn't then it won't be able to take the new bootloader.
hi folks tried to update special rom and upon where the XDa comes up with upgrading takes 5mins the software crashed out telling me to remove from cradle and do soft reset well did all that but cant get active sync to recongnise the XDA and the XDA is still on that upgraing 5 minute screen HELP
If it will not resume when you restart the upgrade program on the PC, then it's time to upgrade via the bootloader method. You need (access to)an SD-card reader/writer for the PC, and to read around on this forum a bit.
thanxs I guess thats the conclusion I came to however just to make sure do u know the steps involved in installing the special rom I have the download exe file someones put on the forum
****. I cooked a second ROM (based on testing the first one - and removing utils I didn't need)
Flashing started - but this time, ActiveSync dropped out and I was left with the 5 minutes screen.
I have tried hard reset but only the "upgrading' screen appears. Now I'm wishing I had never messed with it.
I can get the Wallaby Boot loader screen to come up (GSM OK) it says.
But I have no clue about this other "bootloader" method mentioned on this page. Can anyone please advise where can I find details of the fix? Is the ROM really wiped out and no longer recoverable?
I have the same problem as the first person who posted.
Then you will need to restore the OS using an SD card. (Min 64mb).
Probably easiest to cook a ROM at Jeffs Kitchen to your taste:
http://cuba.calyx.nl/~jsummers/ROMkitchen/
Save it as .nb1 type (bottom of that page).
Then get XDA Tools (yes I know its starting to sound complicated but its not really). http://xda-developers.com/XDAtools/
That program allows you to copy the .nb1 file you cooked to be loaded onto the SD card.
Once you have transferred the OS (.nb1) file to the SD, stick it in your XDA.
Turn on the XDA pressing simultaneously the on switch and sticking the stylus in the SOFT reset hole.
You should get a white screen saying something like flash ROM from SD. Press the JOG (navigator) big switch at the bottom to start the process.
Make sure you have mains power to XDA during this process.
When it finishes, REMOVE the SD card and press HARD reset.
Should be back to normal!
p.s. It goes without saying that you need an SD card reader !!
p.p.s I hope yours is better than mine. Try to get the latest version with drivers that can deal with big SD card sizes...
It does not say hard reset it say cold reboot to reset. So I did a soft reset and it worked after about 7 tries.
I really like what they did with this ROM Kitchen. I would think that if they can get this really stable then they should offer a service to create your own ROM's allowing the user to select what programs they want to include in the ROM.
Er, if you read other areas on this site you will notice that this is run by enthusiasts, who are making their work available to others.
So a little please and thank you will ease your way.
Rather than... "they should" maybe "it would be nice if...."
:idea: If you really want to DIY - then follow all the instructions, get yourself a Unix platform and MKROM.
Bye
ps sorry I got one detail wrong.
pps Sorry I bothered actually
Ariel said:
Er, if you read other areas on this site you will notice that this is run by enthusiasts, who are making their work available to others.
Click to expand...
Click to collapse
Believe me as the owner of www.pocketpcminds.com I understand this. Back in the days of carrying a Palm OS device there a program that allowed you to add and delete things in your ROM.
What I was suggestion is a service that users could pay for that would inlude a list of Pocket PC programs that the users could choose what programs they want loaded in the ROM. From what I have seen of Pocket PC users each person has a list of programs that they find useful and use regularly.
I onlt suggest this because the people running this need to cover thier cost. Otherwise they may use intrest and stop it all together.
We're all too busy with other things to turn the ROMkitchen into a commercial thing. But if anyone else wants to do so, please contact us.
Pro:
- It would be a great sales platform for software (spb gprs monitor, PIMs, etc.)
Con:
- Available space shrinks as OS grows
- No idea how this works out on XDA II yet
Can't burn the Wallaby Patch to the SD
When I try to burn Wallaby Patch to SD the following error appears
Failed to open device \\.\PhysicalDrive8
Anyone help with this.
hi I did all that but when the XDA is being flashed it finishes but comes with achecksum error now I know I am doing everything right as I managed to reload O2 original .nb1 file and my xda is still as was however I want the forums version rom so can unlock many thanx for the previous how 2 instructions
SD card flash - 5 min screen
Ariel said:
Then you will need to restore the OS using an SD card. (Min 64mb).
Probably easiest to cook a ROM at Jeffs Kitchen to your taste:
http://cuba.calyx.nl/~jsummers/ROMkitchen/
Save it as .nb1 type (bottom of that page).
Then get XDA Tools (yes I know its starting to sound complicated but its not really). http://xda-developers.com/XDAtools/
That program allows you to copy the .nb1 file you cooked to be loaded onto the SD card.
Once you have transferred the OS (.nb1) file to the SD, stick it in your XDA.
Turn on the XDA pressing simultaneously the on switch and sticking the stylus in the SOFT reset hole.
You should get a white screen saying something like flash ROM from SD. Press the JOG (navigator) big switch at the bottom to start the process.
Make sure you have mains power to XDA during this process.
When it finishes, REMOVE the SD card and press HARD reset.
Should be back to normal!
Click to expand...
Click to collapse
I have a similar 5 min screen, and I tried as told, that is bought a card reader, cooked ROM, downloaded and transferred the nk.nb1 file to sd card using xda-tools, and entered into bootloader. But all I get is WAIT and then GSM OK message. Not the one that gives me option of flashing the ROM. How exactly to transfer the ROM image to SD card?
Rom Flash Crash
Just in case
I found that getting the XDA going initially by putting across the O2 installer programmeA onto the SD card rebootting with soft reset which installs the standard O2 locked phone system however this allows your XDA to be seen by the PC
all I did then was using the Kitchen Rom is double clicked it then goes into install mode through Programme A and does a PC to phone install.
I found I reinstalled twice and the phone now is working unlocked as required
I tried many times to do the soft reset install as instructed on the forum but it just crashed everytime
I guess the WBL version 5.15 does not identify nk.nb1 file as a rom image. it needs the rom image in raw form, the same as it is copied by bootloader that is WinCE to SD. I think the old XDArit writes it in the required format. dont know how the XDA-Tools does it.
ROM flash crash - solved!
It finally worked. With help from ntabikha, a member of this forum, I got it going. I plugged it in the cradle after hard reset. Activesync kept announcing that it can not connect to the device, and I kept clicking "Retry" (perhaps "disconnect com port" might as well have been all right, but I didn't do it. I thought it might disconnect the com port and stop the Program A from connecting to the device).
I then ran the Original Qtek Upgrade installer, and it did not connect on the first attempt. But it asked me to soft reset the device and run the program again. I did so, and whoa! it worked! It worked great! However, I don't understand why the cooked version 3.17 from Jeff's kitchen was installed instead of Qtek Upgrade Version 3.16.52. I care the least though, since I now have a working xda! Thanks to the guidance from ntabikha.
I wanted to install one of the ROMs from www.yorch.net. But before doing so I have some questions:
1. If I choose to build ROM as an installer.exe, is installing it to my device as simple as running the .exe file? (of course with the device connected thru Activesync)
2. Is my present ROM (see specs below) supported?
3. If Murphy comes to visit and I screw up, will my phone be completely unusable or can I just reinstall old ROM, do hard reset and everything will be back to how it was?
My specs:
OS: Pocket PC ver 3.0.12039
ROM:3.20.06 ENG( 07/30/03) (O2 Asia I think since I bought it here in the Philippines)
Radio: 4.21.00.
Thanks
1 as far as i know yes havent don it to my own device yet though
2 a rom dont have to support a rom since it'll overwrite it
3 of cause merphy can also show his ugly face
but if all fails a sd flash reader writer can save many a tears
also if your phone is working ok then i would not mess with the
radio stack and beware because some roms include the radio stack
and if you try to update your radio stack to a US (900/1900) and you network is 900/1800 you could be in for a world of pain
ROM upgrade step by step
OK I'm really dying to give it a go but I'm just a overly cautious bloke. So I'm gonna outline what I interpreted (after reading lots of posts I think I'm getting it but not sure) to be the way do the upgrade. Please correct me if i'm wrong:
Equipment I have:
1. My notebook (Windows XP, Activesynch 3.7)
2. O2 XDAI
3. Cradle and USB connection.
Steps that I think I should take:
1. Place XDA on cradle and make sure it's connected with PC.
2. Backup?? (not so sure what to back up since contacts, calendar, notes are synched with outlook, docs are also synched, I have copies of cab and program files since I download them to PC before installing them to XDA.) If i'm missing something please slam a frying pan (this is a kitchen right?) on my head.
3. Go to www.yorch.net, check mark on all appropriate options, then (since I have to Unix box and dont know Unix at all) just go for the easy option of cooking the .exe install file.
4. Assuming, the .exe is downloaded to my PC. This time I just run it. I expect this to be just like installing PPC apps. If not, throw a tomato on my face
5. Assuming everything worked and Murphy's in the Arctic freezing his A**e off, then all I do now is hard reset.
6. I have a new ROM and I'm singing happy-happy-joy-joy.
To the wonderful people at xda-developers, am I in the right direction or am I as lost as Bill and Ted? If I'm lost, is there a step-by-step guide for non-unix programmers? (Sorry, there was a sticky but I thought it was for people with Unix boxes)
Once again, thanks for all your help and your patience.
2. Backup?? (not so sure what to back up since contacts, calendar, notes are synched with outlook, docs are also synched, I have copies of cab and program files since I download them to PC before installing them to XDA.) If i'm missing something please slam a frying pan (this is a kitchen right?) on my head.
Click to expand...
Click to collapse
well i can think of one thing to backup and thats your current rom
so if you dont like the new rom you are getting you have the option to go back
of cause if the rom you have now is downloadble from a place you know like your isp then maybe it dont matter
Thanks for the reply. That's a good point. Question: When you back up old ROM, is it just the ROM that gets backed up or is it the whole content of the device, like how you do in PCs?
Also, since no one, besides you, has made any comments regarding the steps that I outlined, is it safe to say that they are the correct steps?
Thanks
When you backup your ROM, no stuff that you customised will be in the backup - the backed up ROM will be the same as when you received it from your retail shop, or if you upgraded, it will be the upgraded ROM without any of your stuff. Do a backup and store it on your hard disk.
DON'T use the .exe cooked ROM, use a .nb1 or .nbf, and use XDA Tools from this site to do the upgrade. It's very easy that way, and less dangerous. Don't upgrade your radio stack unless you know exactly what you're doing, or your phone supplier has made an update available just for you.
If you use a T-Mobile ROM above version 4.00.05 it blocks the XDA-Tools from updating the ROM. At that point you need to use XDARIT (from this site) to low-level write the ROM image you have onto your SD card using an SD card reader which shows the card as another drive on your computer. Once you do that you need to boot into the boot-loader (press the reset button while holding the power button) and follow the prompts to restore from an SD card. If you're unlucky and are running bootloader 5.17 (or above I think) you need to write the bootloader diagnostics patch (wallaby patch from this site) onto your SD card first before doing the boot into the bootloader thing. You can then remove the SD card, write the O/S ROM onto it with XDRIT, and put it back into your phone while it's still sitting on in diagnostics mode. Then you can restore from the SD.
It sounds complicated, but it's easy, as long as you have an SD card reader, and as long as you don't mess with trying to update the bootloader or do an unknown radio update. There's lots of info in these forums if you get stuck.
I made a thread that summarised all the steps using the new tools and ROM's at this address : http://xda-developers.com/phpBB/viewtopic.php?t=3860. It's for Asian/European users, but if you are in the US the instructions are the same, except instead of using European 900/1800 radio you use 900/1900.
Further questions on ROM update
Thanks. It's becoming clearer and clearer. Have more clarifying questions:
1. How do you know whether or not you're including the radio stack with the ROM upgrade at yorch.net. I did not see any options there.
2. At www. yorch.net, nothing happens when I press the "Build ROM Now" command button. Is the download supposed to happen in the background or is there something wrong with my PC or the site?
3. I dont think I'm using the T-mobile ROM but how do I know if I'm runing bootloader 5.17? Is bootloader 5.17 only for T-Mobile users or all?
Once again, thanks for the help and bearing with a newbie.
2. At www. yorch.net, nothing happens when I press the "Build ROM Now" command button. Is the download supposed to happen in the background or is there something wrong with my PC or the site?
Click to expand...
Click to collapse
it should start to write some text about the progress of making the rom
and when it's finished then it should init a std download dialog
The meter down at the status bar does move, same as when you're loading a webpage, then it says Done. That's about it. Didnt see any other messages or dialogue boxes.
Can anyone confirm if it's up today or has it been down?
Thanks
PS. Tried to email using the email utility at the website but getting errors there as well.
OK, firstly to answer your question about Yorch's site... well it worked for me in getting all the ROM's I wanted, then when I went back again the download didn't work. I guess it's just on and off, so unless Yorch finishes getting married or someone else makes another kitchen it's a matter of pot luck. You can get away without using the kitchen if you can find another download source for ROM's, whether it be FTP or whatever. Just remember if you get an exe you can usually pull it apart with winzip to get the .nb1 or .nbf out of it.
Now, for Q1 :
An operating system ROM is generally just under 32MB, but when zipped from Yorch it's usually about 14 or 15MB - the operating system ROM will NEVER be smaller than that. I'm not sure about the exact radio stack size but I know it's a lot less than that. Also, doing some homework about the operating system ROM helps. eg. reading about the 4.01.00 ROM tells you that it's not a radio stack upgrade, it's an operating system upgrade - and the filename and the size of the file you receive reflects that.
Q2:
answered above...
Q3:
I think the bootloader is just pot-luck depending on when you phone was released. To check your bootloader it will reset your device completely, but I read somewhere that if you turn the radio (phone) off it doesn't hard reset. If you're worried, do a full backup first. But basically when you're ready to look, reset your phone while holding the power button and it will tell you the bootloader version. Don't be too turned off by that, I have read that SD card readers can be picked up very cheap if you look around, and that's all you need to get you out of trouble regardless of the bootloader version.
There's no real risk (but I won't guarantee anything), just make sure your phone is fully charged before mucking about with SD upgrades. Also make sure the radio (phone) is switched off before upgrading... using the bootloader/sd card method you shouldn't need to be concerned. I'm not sure what effect having your phone on and receiving a call while using XDA-Tools can have, but someone did mention it somewhere.
I'm a newbie too, but there's really not much you need to know, just a few caveats.
Yorch's Kitchen has been working OK for me the last couple of days. It takes maybe about 5 mins to "cook" before telling me that the ROM is ready. The 4.00.05 ROM gave me a lot of ActiveSync problems, so I went to the 4.00.16 ROM tonight and it looks like it's behaving better.
My SD reader is a Microtech Zio. It appears as a disk drive in windows, but the newer XDArit can't initialize a connection to write to the SD card. I used the "dangerous" older version of XDArit instead (available on Yorch's site), and it's worked OK for me (so far?).
One thing I wish I had realized before I started playing - going into the bootloader will reset your phone most (some?) (all?) of the time.
While I was flashing the ROM tonight I could see the GSM light flashing - I had the same "hope no one calls" feeling tht others must have had. Note that this was while I was flashing from an SD card in the bootloader - so apparently the process doesn't deactivate the phone while it's ongoing.
Muchas Gracias!
Ebswift, if ur a newbie then ur the god of the newbies. Thanks for all the help and for making me see the light. Much appreciated...
A quick Q:
Is the process for installing an .nbf file the same as that for installing an .nb1 file?
I have cooked a few ROMS to an .nb1 format and installed those OK, but now I have one in .nbf that I'd like to install.
So what I'd plan to do is put the nbf onto an SD card using XDArit, and then stick the card in the PPCPE and reboot to the loader. Is that it?
So what I'd plan to do is put the nbf onto an SD card using XDArit, and then stick the card in the PPCPE and reboot to the loader. Is that it?
Click to expand...
Click to collapse
You can do it that way (onto the SD card), or if you're not already using a T-Mobile ROM you can use XDA Tools which is easier. Basically the capabilities are spelled out for you with the available file types in the drop downs when you select a source.
(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
Hi Guys
Just after a bit of help with a touch HD I bought, its running win 6.5 professional running HTC Sense. I would like to take the system back to OEM HTC spec with win 6.1, before posting I have sent time trawling the site but cannot see the wood for the trees so to speak. Would appreciate it if someone could point me in the right direction
Cheers
Paul
hi and welcome to the forum (as an active user ).
i can understand that all the information here seems a lot at first and there are abbreviations and big words and beginners have trouble finding tutorials for the tutorials. so let's keep this simple:
enter bootloader mode. this is done by completely shutting off the device, then pressing volume down while tapping the power button. you should see a 4 colored screen with some basic information about your device.
post here, what the 2nd line says. for flashing the device it should be 1.56Olinex. then we'll continue the process from there.
p.s. to exit bootloader mode, just soft reset the device using the red pin on the back. that way, you can still use your phone.
Hi Tony
Thanks alot, you're a great help.
Here you go second line is "SPL-1.56.01iNex
Hope this helps.
My PDA has win 6.5 and HTC sense and it all makes it run rather slow so want to either delete or turn off sense or return the whole running system back to OEM standard Win 6.1.
Whilst I'm here it would also be great to be able to get microsoft reader to work. have loads of books and cannot activate the bl***dy think, tried FActivation and all the other tweaks I've found and nothing works . + cannot find another reader to support purchased .lit files.
With much appreciation
Paul
we should deal with the microsoft reader later, because flashing another rom comes with a mandatory hard reset, which will format your entire storage, thereby removing all installed apps, pim data and files.
your spl is 1.56 olinex, which means hspl is installed in your device. that way, your device is always ready to be flashed with any rom or radio, which is great, because the hardest step is already done.
to get back to a stock rom, all you need to do, is:
1. create a backup of your device:
1.a. backup your pim data (contacts, appointments...), using one of the following methods:
1.a.1. outlook sync (will not backup call logs, sms or mail from other accounts than outlook e-mail)
1.a.2. ms myphone (will backup everything, including your my documents folder and location, but no call logs)
1.a.3. pimbackup (will by default, backup everything, including mail, but to backup the my documents folder, you need to set it up to do so), put the program and the backup to the sd card, it is not affected by flashing or a hard reset.
1.b. backup my documents folder, if necessary and not yet done in step 1.a.
1.c. make sure, the cabs for all the apps you currently use are present
2. the rom(s) and necessary tools
2.a download advancedRuu from here
2.b. download a stock rom of your choice, either here on the wiki or on shipped-roms.com, from your carrier or from htc.com (if you have an s/n that qualifies)
2.c. depending on your pc's windows operating system, either install activesync 4.5 (xp) or windows mobile device center 6.1 (vista/windows 7) if not already done and set it up to connect to your device. in case you have windows vista or 7, please post again before attempting to flash, there is another step to do.
3. flash the rom
3.a. extract the rom you downloaded (even if it is an .exe file) until you see a bunch of files like EnterBootloader.exe, RomUpdateUtility.exe and RUU_signed.nbh.
3.b. take said ruu_signed.nbh (the rom) and put it in the same folder, where you put advanced ruu.
3.c. put your device into bootloader mode and connect it to the pc, make sure the bottom line changes from Serial to USB and wait for windows to recognize the device.
3.d. start advanced ruu and perform a task 29 (follow the steps)
3.e. put your device into bootloader mode again, start advanced ruu again, if it quit
3.f. select regular ruu (task 28). in select nbh file, it should show your RUU_signed.nbh, click next and follow the wizard
3.g. when finished, disconnect from the pc and perform a hard reset by pressing Volume Up and Down and power and follow the steps on the display.
4. to get your backups back, sync with outlook (or ms myphone respectively) or restore your pim backup
ok, this was the very detailed description of every single step there is to do while flashing, for the worst case scenario. but basically, it is very simple. here, the short version:
backup
bootloader mode
task 29
flash ruu_signed using advanced ruu
hard reset
restore backup
for future reference: there is also an easier way to flash, but it comes with a downside:
in the rom you downloaded, there is the file RUU_signed.nbh (the rom file), you can rename it to BLACIMG.nbh and put it in the root of the sd card and just enter bootloader to flash it. now you'll say, "but why bother with all the long steps above, if it can be so easy?" the reason is: the blackstone sometimes is a *****. it is always recommended to perform a task 29 before flashing, which will format and wipe your rom partition, so the old rom is removed before the new one is flashed. also i always perform several two or three hard resets to make sure it really wiped all old data. and by just flashing a BLACIMG using the sd card, you don't have the opportunity to perform a task 29. leftover data or data fragments might slow down your device, so you should make sure to get rid of them.
and remember: in case you use windows vista or 7 and have no access to a windows xp pc, please post before attempting to flash.
Tony, you're a star. Great explaination in easy understandable terms which I am sure will help loads of others besides myself. Thanks. I am running windows vista so if you can supply the missing step that would be wonderful, in the meantime I,ll go and look at the link.
Cheers
Paul
i left out the vista and 7 instructions, as they are a lot of work and don't apply to everyone. here is the link to the tutorial: http://forum.xda-developers.com/showthread.php?t=524619
for vista and 7 refer to post 3 of that thread. it can be really tough to make windows actually replace the driver, instead of keeping its own. also, on 64bit versions you need to enable test mode, so you can install unsigned drivers.
the good thing is: once you dealt with the driver issue, you never have to do it again, that modified driver is good for flashing and syncing and works for any windows mobile device.
Hi Tony
Right, I have a laptop with XP so will use that to follow your steps. I have been on your link and found
RUU_BlackStone_HTC_Europe_1.14.401.2_Radio_52.49a.25.26_1.09.25.14_Ship.exe
which appears to be 6.1 so will try that. I ,ll let you know how I get on tomorrow and then to be a real pain can we have a crack at Microsft reader as that has been driving me bonkers, activated it many times and still cannot read my purchased books, sort that and i,ll be a very happy bunny
Once again, thanks alot. You are appreicated !!
Well after much care and following Tonys instructions I have managed to return the PDA to Win6.1 . Thanks once again for all your help and replying to my post.
All I need now is to get Microsoft reader to actually activate so I can use my books.
Any ideas What ever I do including using Factivation does not work