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.
I was curious. I've noticed people said that if you put the 4.00.16 ROM on, the only way you can downgrade it, is if you reprogram the ROM from the SD card and not by the EXE method.
I was curious as to WHY? What does that .16 ROM do to the XDA to prevent you from doing an EXE rom reprogram?
So far, we lacked time to look into this one. Tell us, and we'll see if we can fix it.
Downgrade unseccesful using SD method from 4.00.16 ver
Sorry if this is OOT: I'm a non techie person so please somebody explain me how to use the SD card reflash metod to downgrade from 4.00.16 bact to 4.00.11 version. If write the new rom to sd using XDAtools it's done. after it I put it back the SD card back to the XDA. I enter the wallaby 5.17 screen by pressing power+ soft reset button. It said wait and then GSM ok after that freezze.
What I'm missing?
The why, I can't say as I have not investigated in detail, I just said to heck with it and bought a SD writer.
What happens after you load 4.00.05 and 4.00.16 is when you try to run and upgrade/downgrade/re-install from Prgramme-A or the newer programmer that came with the 4.00.x installs it fails saying it can't connect to the device, please check to make sure it's plugged in (even though there is a active connection with Activesync).
Using the SD card there is no issue with running the upgrade.
-rich
but what is it that .16 has that .11 doesn't that stops you from changing ROMs via the EXE method?
Also, after putting on .16 and you go back to say .11 via the SD boot method, are you able to use the EXE method to change ROMs after that?
Currently I use the AT&T A20 radio stack and was thinking about trying out the Tmobile 6.24 to see how it works out. Haven't decided yet.
Investigating the no reflash .EXE method
Ok I have found a roundabout method to resolve this only using the .EXE method.
I used the rom kitchen to generate me a 4.00.11 ENG WM2003. After flashing my phone and wanting to make sure i could revert I tried my origonal o2 provided flash upgrader "Radio_Unit_Upgrade_v31413.exe" and the latest downloaded one from the o2 website "Radio_Unit_Upgrade_v31703.exe" neither of which would let me flash them - i get the error "this rom is not for this device" (or some such).
I went back to the rom kitchen and built myself a 3.17.03 ENG O2-Euro rom image and flashed that onto the phone. this suceeded where the o2 stock .EXE failed and I was nearly back where I started.
Now that I had my rom kitchen 3.17.03 back on I tried to install the latest "Radio_Unit_Upgrade_v31703.exe" file again and was greeted with sucess once more!
The question this begs is the same as the origonal however, ok we can get the stock provider rom back on - but why will it let me flash the rom kitchen 3.17.03 back on and not my o2 downloaded rom? Hopefully the developers will be able to spot whats going on and sort it out in the kitchen (hopefully removing what ever right protection the new rom installs).
Hope this helps, shout if you want me to test with a specific rom version (for uk / europe phones) and ill give it a whirl for ya
I think the "official" rom checks for versions, whereas the roms from the kitchen use a modified bit of code called "adaptrom" to fool the software. I wish I had a tenth of the capabilities of the guys on here that work out all this stuff.
cruisin-thru said:
I think the "official" rom checks for versions, whereas the roms from the kitchen use a modified bit of code called "adaptrom" to fool the software. I wish I had a tenth of the capabilities of the guys on here that work out all this stuff.
Click to expand...
Click to collapse
I'm not sure about this, but i will give you some hint, ok :?
The T-Mobile Rom has a protection to it that you can not upgrade any ROM except T-Mobile ROM's other than that if you have a version of rom that is not T-Mobile ROM you can use the adaptrom to normally update any kind of ROM because adaptrom ignores the Version like PW10A1:007, the explanation of this versioning is in this forum(some kind of country and GSM band 1800/900, 1900/900).
Now why we have to use SD card after we update T-mobile ROMs, if we want to change to another kind of ROM's, because if we use "exe" or sometimes we called it "Program A" it checks the version of the ROM's, since the adaptrom can ignore only the version of the ROM's it can ignore the Type of ROM's, if it is T-Mobile or other ROM's, now for SD card it doesn't check for any version or type, and it goes directly to updating the ROM's in the Bootloader way or we can call it forcely updating the ROM'
s.
Hop this help.
Hi Guys,
I need your help .
I've downloaded the 4.00.16 ROM by mistake, it really didn't tell the ROM number, so now I want to revert to a earlier one and I can't.
I've got the following message: "ERROR: GetDeviceData - An established connection was aborted by the software in your host machine.
error getting devicedata"
and then
"ERROR 011: EXECUTE REMOTE COMMUNICATION PROGRAM ERROR. Cannot execute the remote communication program. Please make sure that the USB/Serial cable is properly connected."
Stupidly, I haven't got a SD card. :evil:
PLEASE HELP ME, I'M REALLY STUCK NOW AND DON'T KNOW WHAT TO DO...
Read the above post that starts like:
"Ok I have found a roundabout method to resolve this only using the .EXE method"
HTH
Qman said:
Read the above post that starts like:
"Ok I have found a roundabout method to resolve this only using the .EXE method"
HTH
Click to expand...
Click to collapse
Hi Qman,
No matter which ROM I cook, when I try to install it using the .EXE it gives me the message I posted before.
Would you explain to me, idiots guide, how to flash not using a .EXE?
or, have you got any sugestions?
Can anybody, please, post me an idiots on how to flash a ROM, not using the .EXE version?
I've downloaded the 4.00.16 ROM by mistake, it really didn't tell the ROM number, so now I want to revert to a earlier one and I can't.
I've got the following message: "ERROR: GetDeviceData - An established connection was aborted by the software in your host machine.
error getting devicedata"
and then
"ERROR 011: EXECUTE REMOTE COMMUNICATION PROGRAM ERROR. Cannot execute the remote communication program. Please make sure that the USB/Serial cable is properly connected."
Stupidly, I haven't got a SD card. :evil:
PLEASE HELP ME, I'M REALLY STUCK NOW AND DON'T KNOW WHAT TO DO...
Hi ritmo-unido,
The another way to flash a ROM would be to use the bootloader method but requires a PC card reader and a SD card which you already stated that you don't have an SD card.
HiQman,
I supose I'll have to get them.
Will you post me the instructions, PLEASE?
:?
Qman said:
Hi ritmo-unido,
The another way to flash a ROM would be to use the bootloader method but requires a PC card reader and a SD card which you already stated that you don't have an SD card.
Click to expand...
Click to collapse
Qman,
Will a USB card reader be OK?
Please advise.
:lol:
Yes.
DISCLAIMERS:
============
NOTE NOTE NOTE NOTE NOTE NOTE
---------------------------------------
THESE INSTRUCTIONS WILL ERASE YOUR XDA!
ALL DATA WILL BE LOST (YES, ALL)
BACKUP YOUR XDA FIRST!
---------------------------------------
NOTE NOTE NOTE NOTE NOTE NOTE
The XDA I have performed this method on has the 5.14 bootloader.
I do not know if it works the same way for any other version.
If your XDA has a different bootloader version,
this may not work... and may leave you with an UNUSABLE XDA...
You have been warned.
Please see this article: http://www.xda-developers.com/bootloader/
XDATools, used below to burn ROM files onto
SD Cards will ERASE / FORMAT the SD Card where it writes the ROM.
========================================================================
========================================================================
Ok, with that out of the way, here goes...
If you are one to tinker with your XDA, and are going
to be loading ROMs, Please take this advice:
-- Invest in an SD Card Reader
USB, Serial, whatever, as long as
the SD Card Reader looks like a Removable Disk to Windows.
-- Invest in a 64MB SD Card that is used for
loading/reloading/re-reloading ROMs, it will be ERASED
whenever you write a ROM image to it.
I purchased a JumpDrive Trio (USB 2.0) for $20 from Wal-Mart. The 64MB SD Card was about $32.
Steps to reload your XDA using the SD-Card method
=================================================
1. Back up your XDA
2. Verify that Step 1 worked.
3. Download/Install XDATools,
http://xda-developers.com/XDAtools/XDAtools.exe
4. Obtain the .NBF or .NB1 file you wish to load on your XDA
These instructions will assume the ROM image file is in C:\ROMDirectory\
and is NK.NB1
5. Attach your SD Card Reader, with the Target SD CARD loaded.
These steps assume this device is X:.
6. Run XDATools Utility called OSImageTool.EXE.
C:\Program Files\XDAtools\binaries\OSImageTool.exe
7. Set the Parameters
Source: C:\ROMDirectory\NK.NBF or c:\ROMDirectory\NK.NB1 (use the ... button)
Target: X:\ [59.1 MB Disk Drive]
NOTE: the above paths are examples... please use the appropriate paths to your files
8. Click the 'Copy' button.
Watch the progress Bar, it will fill, and 'Time left:' will go to 00:00...
When Time Left is 00:00 the Copy is Complete.
9. Remove the SD Card from the Reader, insert it into your XDA
If your XDA is ON, it may ask you to FORMAT the SD Card, SAY NO!
NOTE: an SD Card with a ROM image is not recognized by PPC 2002/WM 2003
10. Soft-Reset your XDA while pressing the POWER button (top button)
This will boot into the Wallaby BootLoader utilities.
11. You should see a Prompt that says: ROM Image Found, Press 'Action' to Flash Rom.
Press the Action Button (thats the directional Pad, press it in the middle)
12. The Rom will be Flashed. It takes about 5 mins.
The numbers at the bottom will count up to 00200000 ( I think.)
13. Once the counting stops, you should be prompted to do a HARD RESET of the Device. Do this.
A hard reset is where you press the button in the very small hole near the earphone jack.
You need to use the small pin on the top of the stylus... you unscrew the 'eraser' end of
your stylus to expose this pin.
14. REMOVE the SD CARD from the SD Slot. Store it in a safe place.
15. Wait for 60 seconds.
16. Press the HARD RESET button again. Your Device should boot using the new ROM Image.
I really hope this helps you out of your jam!!
J
NOTES:
=====
I dont really have any advice for you if the above steps fail,
or if something other than the 'happy path' occurs (as outlined above)...
I once had a problem on Step 12. The XDA never started counting...
So, I just did another soft reset to the bootloader,
got prompted to load the ROM again, and that time it worked.
jta
Thanks for your notes.
I'll try very carefully! I'll let you know the results... :?
jta,
You are GOD! :lol:
IT DID WORK PERFECTLY! I'm back with my bubbled o2!!!
I owe you one!
What a great help!
You are supperb. 8) :lol:
<blush>
Thanks. I am glad I help!
J
jta,
My Bootloader 5.15 is that work for me too, because I can't get some software work on My T-Mobile after I upgrade to PPC 2003, and it keep hanging when I doing something, so I want to downgrade to PPC 2002, any suggest the stable one, and if possible the link pls.
Thanks you ver much,
Ray
uc98, yes, it should work for you.
If you want to downgrade to the original 2002 rom from T-Mobile, you can download the 'update' from their website, run the program, it will unzip files into a "c:\program files\ruu\" folder, and in there you can find the NK.NBF file.
The full path to that file would be :
Code:
C:\Program Files\RUU\english\NK.NBF
Here is the link.
http://www.t-mobileapps.com/downloadcenter/Software_Detail.cfm?ID=15
NOTE: This information is for use with the ENGLISH version of the T-Mobile system upgrade.
I hope this helps!
jta
uc98 said:
any suggest the stable one, and if possible the link pls.
Click to expand...
Click to collapse
HTTP://WWW.YORCH.NET ROM KITCHEN
ROM V. 3.17.03
A heartfelt thank you
thanks to you all, my xda breathes again.
I have very limited knowledge, nevertheless I was able to render my xda useless. However, this forum has helped me recover
thanks again, you're all lifesavers HAVE A MERRY XMAS XDA DEVELOPERS!
HANGS AT "GSM OK"
Hi,
I am trying to flash my ROM using an image NK.nb1 downloaded from Yorch's Kitchen. Using jta's steps, I start my wallaby bootloader,.. and after a while it just hangs at GSM OK?
I am using bootloader v5.15. Any help or suggestions??
Re: HANGS AT "GSM OK"
thePhoneGuy said:
after a while it just hangs at GSM OK?
Click to expand...
Click to collapse
The phone isn't recognizing that there's a ROM image on the SD card. Make sure you've used XDATools or XDArit to put the ROM image onto the card. You can't just use Windows to copy the file onto the card - it needs to be in the form of a "raw" ROM image.
thanks, pdhenry..
I was just copying the image file into the reader instead of writing to it
-k
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.
Hi, got some problems with one of my employes Herald (not simlocked or anything).
It ended up on my desk after complaints about it rebooting by itself every minute or so. I figured I could sort it out by upgrading to wm6. Wen to HTCs website and downloaded the official RUU (HTC_P4350_SVE_4.17.413.2_4.1.13.44_02.94.90_Ship.exe). Everything went along fine and I left it upgrading on my desk and went for lunch.
When I got back it said that the update had failed and I followed the recover function but without success.
Now Im stuck in bootloader mode, and when I try to update it again the current image version is listed as blank and I get to about 1-2 percent before it shuts down and gives "ERROR [244]: INVALID MODEL ID".
Any suggestions on what to do?
Further information...
IPL 4.17.0001
SPL 4.17.0000
When i do a hard reset, after it says format complete it boots up and freezes with a green gradient across the screen.
You can try using USPL or HARDSPL to flash.
The USPL will get around CID locks
This is from ivan's A Herald's Guide to Flashing Aserg, USPL and HARD-SPL - xda-developers
II. How do I flash an NBH file?
Warning: To use the NBH ways, you MUST have a SPL of 4.0 or higher. If you have a lower SPL, you WILL brick your phone.
a. USPL
Step 1. Download Herald-USPL-Beta3.
Step 2. UnZIP the file into a folder on your Desktop. Let's call it "MyFirstROM" for simplicity's sake. Notice that there is a folder called RUU within this folder now. Keep that in mind.
Step 3. Download your NBH file and unZIP or unRAR it into that RUU folder. Make sure that that NBH file ends up in the RUU folder, not within a folder inside the RUU folder.
Step 4. Place your phone into flightmode.
Step 5. Go back to the MyFirstROM folder and then run USPL.exe
Step 6. Follow the directions on the screen. EXACTLY.
Your screen on your cell phone will go white around the 75% part of the "second step" now.
ActiveSync will LOOSE its connection.
Step 7. One step 3 on that black window, the RUU flasher will pop up. Just follow the steps.
That's it. Welcome to the flasher's world.
Thanks for the reply,
First, I cant get activesync to find the phone, only evidence of contact in between the phone and PC is that its listed as [Windows CE USB Devices+PocketPC USB Sync] in device manager. I tried to uspl flash with ASERG.8, and it stops at "STEP 1/3...."
I downloaded mtty to see if it could connect, and it did.
Any further suggestions on what might work!
uninstall..reset.. clean install would probably get activesync to work w the phone..
Reinstalled activesync without any change. And soft/hard reseted everything…
Tried to flash via sd as per instructions in another thread, got to "checking SD contents" and then straight to triple-color bootloader.
Help me please! ;D
Cant help getting the feeling that Im completely screwed...
Cant get activesync to recognize it, only way to get it to light up is via bootloader (camera + reset button), everything ive tried to flash it with hangs almost instantly.
As a complete novice my guess is that the current rom is corrupted and I badly need advice on how to go on. The sd-flash seems quite logical but I cant get it to work. Ive tried to overwrite my sd with 00-values in winhex and then placing the original ruu [HERAIMG.nbh] (through windows, is there a way to write data with winhex?) on the card without any success.
Any suggestions on what to try is much appreciated.
Sounds like the SPL got corrupted or partially written only... sorry. Repair center time. You can also placing your Stock RUU's nbh file into your SD card and renaming it to... umm.. I forget... and then flashing FROM the phone.
facdemol said:
You can't simply place the rom file to the card and hope the device will read it in this way. In my time working for pda service, we used WINHex to format the card (to RAW-unformatted) and then we wrote the rom file in RAW format to the card. Your card looks like an endless stream of hexazecimal values. Only winhex recognises this format, if you insert the card to the computer, it will simply ask you to format it. After inserting this card into the pda, it will start the upgrade . The order of this operation was, as I remember, to fill the card with 0000 values (there is an option in WINHex, a kind of format) then write the rom file to the card in RAW mode. Then insert the card to the device.
Click to expand...
Click to collapse
Thanks for the reply, before giving up and sending it in for repair I would like to give the sd-flash a proper try... So far Ive managed to format the card with winhex but I cant really figure out how to write to the card in raw format. Could anyone point me in the right direction?
i managed to do the steps said above ... formated the card in RAW format etc but still the phone won't turn on ... it will only stay in bootloader ...
diabolic53 said:
i managed to do the steps said above ... formated the card in RAW format etc but still the phone won't turn on ... it will only stay in bootloader ...
Click to expand...
Click to collapse
Care to enlighten me on how you did that?
I've been reading a lot lately.. I wonder if the phones are savageble... something about flashing but bypassing the radio check... Also, the universal has an RUU that bypasses any checks before it flashes... this would be great for us to have... I'm asking around...
g4rwin said:
Care to enlighten me on how you did that?
Click to expand...
Click to collapse
whell i opened the mem card with winhex filled all the blocks with 00 and then i opened the nbf file also with winhex and copied the content in hex format on to the card ....but still no success ..
ivanmmj said:
I've been reading a lot lately.. I wonder if the phones are savageble... something about flashing but bypassing the radio check... Also, the universal has an RUU that bypasses any checks before it flashes... this would be great for us to have... I'm asking around...
Click to expand...
Click to collapse
if you find it please tell us about it cos a lot of phones are getting bricked ...
If I'm correct, you told us a few post above thisone you placed your SD card with the imghera.nbh and got "checking sd conents" and then it went to bootloader.
As far as i can recall you need to get your Herald into bootloader first and then place your SD card with the IMGHERA.nbh file on it. Then it should start reading the image from, your SD card.
Judging from your first post you haven't been using the asigned RUU from the HTC website if this was your first rom flash to WM6 and you got a vendor error. Try to convert and use that one when you flash from sd card.
jappo01 said:
If I'm correct, you told us a few post above thisone you placed your SD card with the imghera.nbh and got "checking sd conents" and then it went to bootloader.
As far as i can recall you need to get your Herald into bootloader first and then place your SD card with the IMGHERA.nbh file on it. Then it should start reading the image from, your SD card.
Click to expand...
Click to collapse
Ive tried all possible ways, if I pop the sd card in while already in bootloader, nothing happens at all.
jappo01 said:
Judging from your first post you haven't been using the asigned RUU from the HTC website if this was your first rom flash to WM6 and you got a vendor error. Try to convert and use that one when you flash from sd card.
Click to expand...
Click to collapse
Ive been trying to flash with the WM6 RUU I downloaded from HTC's site (the one that bricked it) since that is the only local (swedish) and official one I could find. Have I misinterpreted it all and the only thing that could do the trick for me is WM5.1?
Ive also been trying to contact the HTC service dept for over a weeks time ending up in a deadend overfilled voicemailbox - meanwhile my warrantyperiod ran out... Any suggestion on what to do?
duprade said:
You can try using USPL or HARDSPL to flash.
The USPL will get around CID locks
This is from ivan's A Herald's Guide to Flashing Aserg, USPL and HARD-SPL - xda-developers
II. How do I flash an NBH file?
Warning: To use the NBH ways, you MUST have a SPL of 4.0 or higher. If you have a lower SPL, you WILL brick your phone.
a. USPL
Step 1. Download Herald-USPL-Beta3.
Step 2. UnZIP the file into a folder on your Desktop. Let's call it "MyFirstROM" for simplicity's sake. Notice that there is a folder called RUU within this folder now. Keep that in mind.
Step 3. Download your NBH file and unZIP or unRAR it into that RUU folder. Make sure that that NBH file ends up in the RUU folder, not within a folder inside the RUU folder.
Step 4. Place your phone into flightmode.
Step 5. Go back to the MyFirstROM folder and then run USPL.exe
Step 6. Follow the directions on the screen. EXACTLY.
Your screen on your cell phone will go white around the 75% part of the "second step" now.
ActiveSync will LOOSE its connection.
Step 7. One step 3 on that black window, the RUU flasher will pop up. Just follow the steps.
That's it. Welcome to the flasher's world.
Click to expand...
Click to collapse
Hi I try tu patch IPL/SPL with hard spl but with error, now my herald stuck in boot mode. IPL/SPL 1.09.0001. He probbably is from some russia operator (rusian diacritics on keyboard).
How can I try to make him alive?