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.
Hello wise people!
After a while struggling with the original o2 ROM on my Wallaby I decided to use the new ROM-kitchen at xda.weblink.net to cook a beter ROM. I'm deeply impressed how easy the process of cooking and installing the ROM is. ThanX to lumpistefan & to all the others!
After all there are two left-over problems:
The one thing is about autoconfig-setting for the GPRS:
I choosed the o2-Config, but what I do get instaled is an o2-loop setting.
The other thing has to do with the format of the MultiMedia-Card (I'm using a 128MB Dual MMCard): Before I started upgrading the wallaby I`ve done a backup oft the original ROM on my MMCard. After all was done I formated the card again as requested by the Wallaby. But for some strange reason my Win98 is able to read/write on it as well as the Wallaby itself but my Linux (SuSE 9.0) does not accept the card at all anymore. I'm not evebn able to reformat it using yast or knoppix...
Does anyone have an idea how to fix those minor problems?
I have lost the SD card backup before appling the 27 MB anakasy/MKS patch.
I tired to flash using the original clubimate downloaded 1.11 but after the same my STORAGE folder is missing.
Please help to slove this issue...
This is weird. I have twice done the Anansky and then installed another normal ROM on top of it, with no probles whatsoever. Maybe it's the I-mate ROM you are installing that's bad? Have you tried another ROM?
I have tried JAM 1.06 ROM and O2 1.11 ROM but no way get it work. Still same issue with storage.
One thing I noticed that before this issue I can flash the ROM after diabled the activesync and phone is normal mode. Now after this issue I have to switch the phone to boot loader for normal downloaded ROMs to start flashing.
Please help.....
Re: Lost rom SD card backup file-How to original downloaded
nishadks said:
I tired to flash using the original clubimate downloaded 1.11 but after the same my STORAGE folder is missing.
Click to expand...
Click to collapse
It sounds like you're only flashing the radio+ce. Can you verify that there's a file called ms_.nbf in folder you're updating from?
Yes it contain all the three files ms_.nbf, nk.nbf and radio_.nbf...
I don't think you even should get to a point, where you can see which files are included in the installer. Just download the right ROM for your Magician and run it. Too often we see ppl having problem running a hacked upgrade and instead of just reverting to the original thing, they try to hack some more! Well, not all hacks works...
Other than that, I see 3 options as it is right now...
1. Redo the whole thing! Try to flash the Anansky and see if you can get that going. If you can, try running the normal ROM update afterwards. If it doesn't work...
2. You can ask for a kind soul with the exact same original branding as yours (I-mate, Qtek or whatever and same country) to upload a backup of his ROM. Overwrite the first 416 bytes from your own ROM and try to install this new ROM. If that doesn't work either...
3. Get the ROM flashed in a service centre.
Well.. You have something like ten active threads about this flying all over the net, yet when someone takes the time to try help you, you don't reply. You just move on to the next thread. If you don't take those trying to help you seriously, then I for one won't waste any more time on this...
I have solved my JAM's problem. Backed-up my friend's JAM ROM and restored in my JAM. Now everything working fine. Thanks a lot for all help...
Friends.. please help me.
My XDA got totally off, when it happens.. I have to hard reset the device, so the application will be erased.
It happens several times, if I don't use mmc or SD, my XDA seems to be OK, but after I insert mmc or SD, my XDA couldn't bear 1 week to be totally off. At first, I think my MMC was damaged, so I buy a new one SD card to replace it, but the problem still occured.
After that, I borrow my friends' XDA which is healthy and I install the same application and insert same SD card.
The problem occured.
The motherboard has already changed but still same problem.
Is there any application that I supposed not to installed?
or maybe my data (outlook data) corrupt?
Thanks before..
Note: When my XDA is going to be totally off, the bluetooth lamp is suddenly turn on
i would upgrade the rom to a later version
1.72 works just fine for me 1.14 radio
1.66 had freezing issues for me
Many thanks bro.. but where could I find 1.72 and 1.14?
Thanks
try looking at the ftp look in the wiki pages how to get to the ftp if you dont know
thanks bro.. you rock
I've downloaded from wiki sites but there is no 1.72 ROM in English. Could anyone wonder where I could download it?
Btw I have upgraded the ROM to jojozx but still the problem occured, suddenly hard reset. Does anyone ever happened this situation?
cant you just take the 1.75 rom then ?
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?