Related
Hi All,
After a LOT of reading and mucking about, I've been able to update my ROM, get full use of GPRS and revert back to the manufacturer's ROM. There are a number of instructions, some of which are pretty dangerous. The following forum topic is the invaluable guide you need to read if you wish to revert back from a T-Mobile installation :
http://xda-developers.com/forum/viewtopic.php?t=3274
The place to get your ROM's is http://www.yorch.net, from the ROM Kitchen. Use the XDA Tools from the above forum link to burn ROM's you download from Yorch's onto your beloved XDA (use the .nb1 format, NOT the .exe method and burn using XDA Tools through your USB cradle).
I happen to have the 5.17 Wallaby bootloader which means that it will not let you simply whack in an SD card with a new O/S and burn off a backup ROM, it won't happen. Don't try to upgrade your Wallaby bootloader. The safest method is to use the Wallaby bootloader patch which can be downloaded from a link at the top of the forum topic link I posted above. That allows you to do a simple O/S restore from your SD card, providing you have an SD reader which presents your SD card as a new drive on your computer. The instructions are simple, just use xdrit as per the instructions in the forum topic link above.
So, from my experience I backed up my original ROM using XDA Tools and stored it on my hard disk in .nb1 format. I then downloaded the .nb1 for 4.00.16 and installed it using XDA Tools without a hitch. Everything worked fine, but I wasn't comfortable until I knew I could revert back to my original ROM. So my next step was to write the Wallaby Patch tool onto my SD card using xdrit using the instructions as laid out in the forum topic link above (take note, use the 1K header option in xdrit). The SD card reader I used was an X-Drive that you normally use for digital camera style stuff. Once written, I put the SD card in the XDA and did the bootloader boot (hold the power button whilst pressing the reset button), and was then given the option to press the Action key to go into the diagnostic mode which is where the patch program resides.
I then took the SD card out, leaving the diagnostic screen still open, put the card back into the X-Drive, formatted it using default options in Windows XP, then wrote the ROM backup I had (you can use any ROM here) onto the SD using xdrit, selecting the 3.5K header option (because we are still using Wallaby 5.17 regardless of patching). The last major step was to place the SD card back into the XDA and select Restore SD and accepted the risk notices. The restore appeared to go fine, but at the end it said Incorrect CRC. That in itself is a worry, but I had at least restored to a point where I could burn whatever ROM I like using the simple XDA Tools method, which is exactly what I did after reviewing the connection info (once more), going to 4.00.05.
Before I originally went to 4.00.16 I recorded all my connection details, including proxy info. When I went to 4.00.16 and re-entered all the gprs info, I found that the internet worked, but MSN Messenger would not connect, stating that the proxy info was incorrect - even though the values were exactly as originally setup. That was one major reason for wanting to go to another ROM. However when I ultimately got 4.00.05 on, I kept getting exactly the same error message with MSN Messenger. The answer came from a hint in another forum topic where someone (with AT&T I think it was) said not to put anything in the proxy info. That did the trick. Un-ticking the proxy option allowed the internet and MSN Messenger to work perfectly.
For Telstra GPRS (I think this is universal) the access point name is : telstra.wap.mnc001.mcc505.gprs
GPRS Authentication method is PAP authentication.
Hopefully this info might help someone out there, because I spent close on 8 hours sweating over trying to get my original ROM back up and running.
Oh yeah, thanks to the XDA Developers, Yorch and the whole XDA community. ROM updating really is easy when you've got the right info, and I can tell you it's really worth upgrading to PPC 2003 (WM2003?), it seems so much more stable, my GPRS has never stayed on as long and it's fun! You can get creative in the ROM kitchens (such as http://www.yorch.net), adding the software you like.
Just a piece of advice, search the threads for problems with any ROM you want to try out first so that you know the traps before it's having a party on your XDA at your sanity's expense.
I have some more observations now that I'm getting more comfortable with doing ROM updates. There are some advantages in going from the 4.00.05 ROM to 4.00.21, such as button lockout while off.
When I initially did the 4.00.21 upgrade I happened to go into the "band" option in phone settings and left the options unselected. Unfortunately setting this to nothing defaults to USA which is totally incompatible with Australia. The result was the phone would not synchronize and I could no longer go into phone settings. The fix for this scenario can be found in this thread : http://xda-developers.com/phpBB/viewtopic.php?t=2893&sid=1e7be62705d2831332c7f0bd5a75e364. It's standard stuff to the die-hards, the scariest thing in the world for us newbies.
Once you set the band for Australia (same as Europe - 900/1800 I think it is) you then get a signal, can synchronize and start customizing your settings. You can get rid of most of the T-Mobile garbage, so far everything is working fine.
Thanks for that buddy, i'm about to do the same downgrade tonight (once Yorch's kitchen is back working properly). You saved me many many hours of pain!
Thanks to all who add to these wonderful forums.
Steve
Just to keep this info updated for the Aussies (and same applies for Asians, and Europe too I think), basically the same applies for 4.01.00 as I explained for 4.00.21 further back. 4.01.00 seems much the same as 4.00.21 at the moment.
Hi guys,
I have a similar set-up as yours, ie I am in Australia nd I upgraded my rom to a 4.00.16. I would like to downgrade it to the original O2 one as I have to return the phone to my company (I am being made redundant).
I tried the method you described but I failed. Basically, I can write the patch on the SD card and when I put it back into the device nothing changes...
Could you please be more specific as to what you did ? Typically, did you switch off the device then put the card then stop/soft-reset or else ?
As well, I only have the NBF version of the O2 rom that I got from the update on their site. Do you think it works or should I try to find a "pure" NB1 rom (I think there's one on Yorch's website).
Thanks a lot in advance for your help.
Bob.
Hi Bob,
Sorry to hear you have to give up your XDA, hope you have replacement work for your redundancy.
Once you have written the Wallaby Patch onto the SD card using XDRIT you reset the device using the stylus and hold down the power button at the same time (with the SD card with the patch in place). That will load into bootload mode, and you press the action button at that point to actually go into the patch.
Once the patch has loaded you leave the device on, and remove the SD card, write your ROM image onto it using XDRIT, and place the SD card back into the phone. On the patch screen select "Restore from SD" using the little directional arrows button below the phone screen. It will then ask you to confirm, then you will see the progress - it takes about 5-7 minutes.
The details on how to write the patch and write ROM's are further up in this thread. I think you can use the NBF file but I am not certain. If you don't want to risk using an NBF you can use the same method above, but revert to the 3.17 ROM from Yorch, then you should be able to use the ROM upgrade from O2 to get a clean install of the manufacturer's ROM.
Let us know if you have any problems.
Thanks Mate.
I have tried once again to patch my Wallaby 5.17 (funny name, isn't it...). It failed. Once I go into the bootloader and press the OK button, I get to the diagnostics screen and nothing else is happening.
Could you shed some light on this ?
Thx.
Bob.
Re-reading your posts...
Would it be possible for you to send me the wallaby patch tool you used ? I tried the one from here (http://xda-developers.com/XDArit/wallaby-patch-tool.nb2), as is and renamed to nb0, but it seems to be the key.
Basically, even though I get the following message : "Successfully copied image of 514 blocks", after having chosen the 1k header, as it's explained in the very detailed post you mention, I still get to the diagnostics screen instead of the patch one...
Thx again in advance for any help.
Bob.[/img]
I tried the one from here (http://xda-developers.com/XDArit/wallaby-patch-tool.nb2), as is and renamed to nb0, but it seems to be the key
Click to expand...
Click to collapse
Hmm, I had no problem at all with the bootloader... one thing though is that you don't rename the .nb2 to .nb0, you use the file as-is. In XDARIT you should be able to select the .nb2 file to write to SD.
It is a diagnostics screen that you get to, that is the purpose of the patch. In that diagnostics screen should be options such as backup ROM to SD and restore ROM from SD. If it still doesn't work for you then maybe I should send you the versions of the patch and XDARIT that worked for me.
Hi,
I am using the O2 3.20.06 ENG ROM and 4.21.00 Radio. Do you think I can upgrade to 4.00.21 ROM directly?
Should I just run the exe file from the Yorch.net? Is it that simple?
What about the radio? Do I have to install a new one or is the 4.00.21 ROM included the radio?
Also, why people need to upgrade bootloader to higher version? I am using bootloader 5.15.
Thanks very much in advanced.
Well, I wouldn't use an exe for upgrading, and I wouldn't try upgrading the radio unless it's an official one posted by your supplier.
Use a .nb1 ROM from yorch and use XDA-TOOLS to do the ROM upgrade. Remember that if you go to a T-Mobile ROM you will need to use the SD card method to change to a different ROM.
Don't try upgrading your bootloader, 5.15 is fine. It's the higher versions that can be problematic and require the patch.
Thanks very much for your reply.
I am about to upgrade my device.
Just a few more questions,
1. Is this 4.00.21 ROM worked okay with the 4.21 Radio in Asia?
2. Also, other encounter a problem with SD card with this new 4.00.21 ROM, have you find any? (every 48 hrs the device wipe out the data in the SD card!)
3. It seems to me when using SD card method to change ROM with bootloader 5.15, the procedure is the same as upgrading or downgrading, isn't it?
4. The file from Yorch.net "upgrade" is only nbf file. It's not nb1. Is it the same?
Cheers,
Hi Chris
1. Yes, 4.00.21 does work fine with the 4.21 radio. I've touched on moving from 900/1900 to 900/1800 band if you should strike that problem.
2. Funny thing that, but I just checked and my SD card is erased after some 3 weeks of no problems.
3. Yes.
4. I do know that if you make a ROM in Yorch's kitchen you can choose .nb1. If you download an 'upgrade' I'm not quite sure what you get.
Not successful with the upgrade
Thanks so much for your reply.
From Yorch.net "upgrade", I can only get the 4.00.21 nbf file which is not nb1.
I can't use xdarit to burn that rom to SD card, an error occurred. But when I use the new OSImagetool, I can burn the ROM to the SD card and I can even change the name to nb1 file.
For both cases (nbf or nb1 file), I put the SD card in my device and press to the bootloading mode, nothing happen!
The device can't detect there is a ROM upgrade there. How can I do that?
Chris,
You need to download the .nb1 from the Rom Kitchen link on Yorch, not from the upgrades link, if all you are getting is a .nbf. With .nb1 you can use the osimage tool or xdrit with the sd method.
The bootloader will not restore from sd unless you have a correctly written image. In Yorch's kitchen you will see that .nbf is tagged for advanced users, that's a strong hint that different methods need to be used to install those.
I see....
Thanks v much.
Sorry for the delay in reply but I had gone back to Europe for Christmas.
I would be happy to use your wallaby patch file as mine doesn't seem to work. You can mail it to me on [email protected].
Thanks in advance for your help,
Bob.
Ok Bob, I'll send it in a few days when I get back to a PC. But I can guarantee it's the same patch that I linked back to in this thread.
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.
I am trying to upgrade my Siemens SX56 to ROM 3.17 from Yorch.net,
I did the following:
1. Backed up the current ROM using OSImageTool.exe
2. Downloaded ROM 3.17 from Yorch.net in a .exe file format
3. Clicked on the downloaded .exe and I get the following error message:
Cannot find the ROM image to upgrade your Pocket PC. Please download and try again.
Please help, I am a newbie!
1st mistake...DONT USE AN EXE to upgrade. Use the sd card method. Otherwise you will be screwed.
When I select zipped NK.nb1 (SD-card flashing) I get the following error:
./mkrom.sh: ../../kitchen.local/mkrom-inc.sh: No such file or directoryno files for configid 26220739Cannot fit files in given sectionsError splitting files
:shock:
From what you posted it appears theres a problem within the Kitchen,
try back later!
HTH
Where else can I get 3.17 , the only kitchen I found was Yorch.net
Now the log shows:
adding: NK.nb1zip I/O error: No space left on device
zip error: Output file write failure (write error on zip file)
Click to expand...
Click to collapse
I'm guessing that the kitchen needs to have old results purged occasionally (possibly manually?).
Strange I used it earlier to get stock ROMs and I did all of them with no problem. Hmmm
jgalindo said:
Where else can I get 3.17 , the only kitchen I found was Yorch.net
Click to expand...
Click to collapse
You can use the XDA developers Special Edition ROM v1.2 its based on the same ROM.
XDA developers Special Edition ROM v1.2 can be found at:
http://cuba.calyx.nl/~jsummers/XDA/XDA-developers-SER-v12.exe
HTH
Ignore my last post. I went back and was able to cook a 4.00.16 ROM, so it's not a server disk space issue (like the error message made me think).
And I just cooked a 3.17.03 ROM. Guess it might be back.
Thanks a lot guys, I'm still trying with no success. :x
I just realized Vallerhum has the setup I want, I also have a Siemens SX56 on ATT. Where did you get your ROM?
I got it from Jeff's kitchen before it went south. I am trying to get my own up for I have all of the ROMs to date.
Is your phone also unlocked?
How can I get your ROM? I am going to another country on Friday and need to unlock it before then so I can show off to my friends
No my phone is not unlocked. I am not planning on changing companies anytime soon but if you want to unlock it...just load the 3.17 rom or if you have ppc2002 just install the xda unlocker and then install the ppc2003 rom of your choice. However, always use the sd card method, dont use an .exe.
I was able to cook a ROM! This site is great: http://www.zensay.com/qtek/ceupgrade.html
Thanks all for your help!
Now, I'm playing around with other stuff and seeing If my unlock was successfull.
That site is not a kitchen. It is for teaching how to do an SD card ROM upgrade. Where did you cook (or download) your ROM? Cooking is the customization of ROMs with other softwares.
I love this forum! (first off)
HOWEVER, there is certainly a whole lot of info here. Too much to effectively sift through; I know becuase I keep trying. I have a T-mobile Pocket PC 2002, and it works fine. I do however want to be up to date screwing around with new progs and stuff. SO, my question is this..... What is the latest OEM ROM update for Tmobile USA, does it have problems, and is it worth the upgrade? Also, what is this warning about not being able to change your rom to any other rom after updating to 4.x.x? Thanks!
AND how does lumpistephan's kitchen know if you are trying to burn for an MDA I or II? Is it the same image for both? Thanks..... AGIAN!!!! :mrgreen:
Lumpis kitchen is for xda 1.
The warning about not being able to change your rom to any other rom after updating to 4.x.x is partially true.
I made a WM2003 ROM for my XDA I in LumpiStefan's kitchen.
When I upgraded to WM2003, I could not use the SER 1.2, also on this site, to revert back to PocketPC 2002.
I had to use the SD card flash methode to flash back my original XDA OS.
So flashing the ROM the cradle way is not possible, flashing the SD way is
HTH.
i once found this guide in this forum it explain it all in laymans terms
Ok here you go, its a little outdated but its what I still use:
Qman's how to use XDArit to write nk.nb1 or nk.nbf to your SD card aka the Bootloader Method!
1. Place XDArit and the nk.nb1 or nk.nbf file in the same folder and start XDArit.
2. Select your SD card (disk drive) from the drop down menu.
3. Select Write to SD
Notice that the Windows CE box is already checked so just click the browse button at the end of that window.
4. Select your (nk.nb1 or nk.nbf) image and then Open
Notice by default XDArit will open looking for a *.nb1 file but if you're going to use a .nbf file you'll have to manually change the "Files of Type" to *.nbf
Notice that nk.nbo / nk.nbo was automatically added as your boot-loader and its check box is unchecked so leave it that way and click OK. XDArit should start writing to the card.
When XDArit has finished writing the image put the SD-card into the XDA and hold the power button and soft reset. You'll be taken to the below screen:
SD DOWNLOAD
Card Type:
CE OS & BOOT
Press action to Download
Or
Press REC to Exit
Press action to download and it will start the download/restore from the SD card.
Follow the on screen instructions once its "Completed" which will consist of a "Soft Boot/Reset".
Click to expand...
Click to collapse
You guys (ladies too) are the best! So, I can change my rom after an upgrade to 4.x.x, but not with the cradle; I would have to use the SD method.
One more question?????
Can I back up my existing ROM using my PC/ActiveSync, and leave the image on my PC??? Just in case I need it? I have no idea how to do any of the cradle flashing/backing up, but i'm sure I remember seeing some good threads about it.
THANKS YA"LL
interestingfellow said:
One more question?????
Can I back up my existing ROM using my PC/ActiveSync, and leave the image on my PC??? Just in case I need it? I have no idea how to do any of the cradle flashing/backing up, but i'm sure I remember seeing some good threads about it.
Click to expand...
Click to collapse
Yes, use XDAtools to generate NK.nbf file of your current ROM stored on your PC and later you can use it to re-flash your ROM in case needed ... but if you use 4.xx ROMs you will have to use SD card
So, I've been looking around the web for user reviews of the 2003 Rom from T-Mobile. Apparently it sucks for a lot of people. I wanted to know....
Has anyone had a personal experience with it?
Does someone have a copy I could get from them, if need be?
Does anyone know if the radiostack is good/bad to upgrade to latest version? (I konw it is dangerous, but specificly the latest update)
What would be thought of if I go to the Tmobile store and backup the rom from a PPC 2003 off the shelf, and flash my device with it's image?
Was the malfunctions with the upgrade released by T-mobile related to serial #/ batch, or just Idiot error?
Anything else you can think of?
Thanks again!
about radiostacks then if you dont have any issues with the gsm part dont mess with it
it's a bit sensitiv imho
i used to run the 4.01.00 beta back when i had a xda1 and i never had any issues with it with sd card erasures or anything else
but then nor did i with the 2002 rom i had before
What about grabbing an image off of a 2003 at the store?????
Do you actually know of a store that has a WORKING model for you to get a hold of? The T-Mobile stores here only have empty cases out where the public can see them (and potentially steal them or mess them up). Getting them to allow you to actually touch a working model requires a credit card - of course then you can do whatever you want with it . . . because you own it!
I sell cell phones. I know all the T-Mobile people in this area (the important ones at least). So actually getting my hands on an operational model in a retail store wouldn't be too hard. Even then, Comp USA let me play with a unit once or twice already. SO THERE! But in reality, for most people, in most places, what you said does apply.
I'll let the forum know if I get the image.
Hi all,
I uploaded all roms + extended roms I have for our beloved HTC Wizard.
You can find them here:
ftp://xda:[email protected]/Uploads/HTC_Wizard/
Maybe a (FTP) administrator can move them to the main FTP index so we have a folder like all other HTC phones.
Any new roms can ofcourse be uploaded to the same folder.
Have fun!
Hey
why you don't have an german rom ?
regards, Peter
Because I dont have any German roms myself.
I uploaded all roms I found myself...
If you can provide me any links than I can download it and upload to the XDA FTP.
Has anyone managed to make a ROM dump of the UK T-Mobile ROM?
I would be interested in an o2 UK rom also.
Would be nice.
Yeah, would be good to get an archive of all the roms, good work on getting this started.
If i wasn't in such a hurry to flash my Rom i would have waited until i got a Mini SD card and backed my UK T-Mobile ROM up first, im just too impatient! :lol: Wish i had waited now, as now i am after it again!!
Anyone?... :?
Thanks Panja
can anyone upload the TW_Chinese ROM? Thanks
mattstroud said:
If i wasn't in such a hurry to flash my Rom i would have waited until i got a Mini SD card and backed my UK T-Mobile ROM up first, im just too impatient!
Click to expand...
Click to collapse
How i can do this? Is there any proggy which backup the rom?
To backup your rom you need to do the folowing...
First:
Your phone needs to have the bootloaded unlocked ,so use the following unlock tool lokiwiz - HTC Wizard Unlocker UPDATE Version 0.2a created by machinagod which can be found here, and when you run the PC app choose 'C' for SuperCID (this will unlock the bootloader) Version 0.2a is the latest and it worked great on my phone, instructins are on the page - Thank you machinagod for all your work here, its a great tool!
Second:
To backup the ROM, download the two files attached to This Post written by arnoldl - Thanks for this info arnoldl, very helpful. Follow the instructions in the post.
Third:
Which ROM is it by the way? T-Mobile? O2? is it a UK ROM?
When you have it saved can you upload it to The FTP area and post here to tell us what it's called and where it is so it can be catalogued with others to help build a good archive of them.
Cheers and Hope this info helps
Second:
To backup the ROM, download the two files attached to This Post written by arnoldl - Thanks for this info arnoldl, very helpful. Follow the instructions in the post.
Click to expand...
Click to collapse
you can restore the image only, when you leave the image on the sd-card.
when you write it on your harddisk with ntrw and write it back to sd-card with ntrw the restore won't work!
Nobody here has confirmed, that the image (here on ftp) are working!
regards,
Peter
Update: The image "germany in qtek.rar" (size 50mb) was deleted from ftp
you can restore the image only, when you leave the image on the sd-card.
when you write it on your harddisk with ntrw and write it back to sd-card with ntrw the restore won't work!
Nobody here has confirmed, that the image (here on ftp) are working!
Click to expand...
Click to collapse
Cheers greddy - i was just about to post that!!
Can the image on the SD card be coppied to a Zip or Rar file directly and NOT using NTRW? Maybe this can be tried and extracted back onto a mini SD card by someone else, im very willing to try it, then we will all know if this works.
So for now bill_viper - Backup your ROM to MiniSD card but do not use NTRW!! Just keep that Mini SD card safe and do not delete it until a safe way of backing up the image to a distributable file or archive has been found.
I've just done a bit more reading and it looks like you can use NTRW to create a backup file of the ROM from the SD card image.
The problem experienced is with loading ANY rom onto the device using the 1.06 bootloader (the one with the K-JAM rom) so in order to put a Rom onto a device with the 1.06 K-Jam rom - the 1.06 bootloader) you first have to put the prodigy rom on or something like this using the *.exe file as it has a different bootloader (1.01)
So bill_viper please do use NTRW to backup the ROM image on your MiniSD card, and please post it on the FTP for archiving.
Cheers
First of all i would like thanq mattstroud for your time.
The info u've posted are very helpful. I have a Qtek 9100 English Version.
I will read the thread u specified above and i'll backup my rom and upload it.
Hello mattstroud
i have try Booloader 1.01, 1.03 and 1.06!
No luck and not the reason, why ntrw makes **** when read and
wrote images.
We will see 8)
regards, Peter
..
Hi greddy,
did you not have a damaged image file wasn't that the reason for your problems?
----------EDIT----------
Seeing sun75's post proves that the problem does lie with the 1.06 Bootloader and not the NTRW image, so greddy i think your image file was damaged which caused problems regardless of which bootloader was being used.
Cheers for this info sun75, good to get some definite proof after all.
Hey mattstroud,
did you not have a damaged image file wasn't that the reason for your problems?
Click to expand...
Click to collapse
at the moment i am not sure. Since 2 hours i am testing with
backup/restore from sd-card and it works, also with 1.06, all bootloader
versions are working, but nothing with restored ntrw images.
I am using ntrw 2.00 from here, is this right ?
regards
Hi greddy,
Hey mattstroud,
did you not have a damaged image file wasn't that the reason for your problems?
Click to expand...
Click to collapse
at the moment i am not sure. Since 2 hours i am testing with
backup/restore from sd-card and it works, also with 1.06, all bootloader
versions are working, but nothing with restored ntrw images.
I am using ntrw 2.00 from here, is this right ?
Click to expand...
Click to collapse
Ok, i didn't know this. Looking at sun75's post it worked fine for him when he loaded a rom with the 1.03 bootloader. Maybe this problem is specific to your device? :?
2 new roms added:
K-JAM_Italian_1030902_102_ship.exe
K-JAM_Norwegian_1040902_104_10910_ship.exe
Excellent, nice one.
Any one able to add a T-Mobile UK ROM?