Related
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.
I got MDA from T Mobile with:
ROM : 3.04.00 GER
Radio Version : T302
Protocol Version : 32S54
Pocket PC 2002
The Operating system is in German , I need to change the same to English .
Can someone guide me please .
I am not a techie guy and hence request someone's Help.
I would be exteremly thankful .
Thanks and regards
I do my ROM updates using the XDA's bootloader and an SD card. This seems to work a little better with less chance of things getting messed up. There's also a way to run an installer program on your PC but my observation is that a lot of people who have had problems have used this other method.
a few questions first:
Who is your carrier now?
Do you have an SD card 32MB or larger? (If you don't you'll need one.)
Does the phone/Internet work satisfactorily (even though it's in German)?
DISCLAIMER: I am an idiot. I've probably forgotten some crucial detail or two here. It's up to you to figure out where I'm full of sh*t before starting.
Spend an evening or two reading all of the threads in this 'ROM Updates' forum. It's good to understand the ways something can go wrong and how to avoid making that happen.
Back up all of the data on your XDA before starting. This includes your contact/calendar/task data (normaly these sync with Outlook on your desktop PC when you run Activvesync) as well as any documents that you have saved to device RAM.
Some people do a full backup of their XDA, but it's tricky to restore from this backup when you're not restoring to the same OS version that you backed up from. So I don't bother - I just make sure my outlook data and documents are stored away somewhere safe on my PC.
Back up any data that you've stored on your SD card. You'll end up erasing the SD card as part of the process.
Go here:
http://www.xda-developers.com/XDAtools/
and download XDA tools. You'll use this program to move ROM images to the SD card in your XDA to update the ROM.
Go here:
http://www.romanweb.com/yorch/
and in the "ROM Kitchen" section choose the elements you want to have installed in your XDA along with the OS. The XDA has leftover space in the available ROM memory after the basic Operating System is in there, and the kitchen allows you to put other stuff in here (so it won't take up RAM unless you're actually using it). You can choose a European O2 image or a US T-Mobile image. As long as the bar at the top of the page doesn't read "Overload" you can make a ROM image with what you have selected. Make sure that "Zipped NK.nb1 (SD-Card flashing)" is checked, and press "Build ROM Now" The kitchen will go work for a few minutes and finally will indicate that it's ready to download. Make a note of what your choices were for this image (this is more important after you've been playing and you have downloaded a few different ones), and download the ZIP file to your PC.
You need some software like WinZIP to extract the nb1 file from the ZIP file. If your version of Windows (XP, 98Plus, etc understands "compressed folders" this will work. Use whatever method to extract the .nb1 file from the ZIP file that you've downloaded.
(NOTE: You CAN'T just rename the extension of the file to .nb1 if it's something else like .zip or .exe. Sounds obvious that this won't work but people try it anyway)
Put your SD card into your XDA (you've backed up the SD card, right?) and press the soft reset button on the bottom while holding down the power switch. This will put you into the "Wallaby Bootloader" of the XDA. Read about it here: http://www.xda-developers.com/bootloader/ Press the Contacts button on the upper left of the front to the XDA, and use the joypad to highlight CE+BOOT TO SD. Then press the middle of the joypad to start the copying of your machine's Rom to the SD Card. The screen will count up the progress until it indicates that it's done. Remove the SD card and reset your XDA again.
Put the SD card back into the XDA - it will detect that the SD card is no longer formatted (the ROM image overwrites the formatting) and will ask to reformat the card. Select Nein (German for No). Put the XDA in the sync cradle, and use XDA tools to move the ROM and Boot files from the SD card to your PC for safe keeping. IF you've backed up both the ROM and boot files there should be an .nb1 (ROM) and an .nb0 (boot) file to transfer
Now use XDATools to move the new ROM image .nb1 file that you cooked up in the kitchen onto the SD card. When this is done, remove the XDA from the cradle.
Make sure your battery is fully charged. Don't want to run out of juice during the next step.
You might want to turn off the phone part of the XDA next. I haven't, but people always wonder what will happen if someone calls you while you're in the middle of an upgrade.
With the new ROM image on the SD card in the XDA, soft boot the XDA with the power switch held down. This time the XDA will recognize that there is a ROM image on the card and will offer to install this image.
If you don't get the screen offering to install the image, make sure that you installed the ROM image to the SD card using XDATools. Just copying the file to the SD card using activesync or Windows file copy won't work.
When you do get the offer to dowload the ROM image, press the "Action" button to do so. Again the counter will count up, and when it is done the system will do a checksum (to make sure it got loaded right). If the checksum is OK, it will tell you to Hard reset the XDA. Remove the SD card, and press the button inside the tiny hole on the right bottom. This will turn the XDA all the way off. Wait a couple of seconds, and then press it again to Cold Boot the XDA.
If you've been good, the XDA will boot up with a new, English ROM version installed.
***
Some other notes:
If your bootloader is Version 5.17 the above process won't work (the bootloader version is shown on the first bootloader screen). Read the xda-developers page about the bootloader for info on what to do if this applies.
Need help
THanks for a very explained reply .
Infact since I did not had SD card and I tried to run the upgrade utility and guess I had screwed up .
Now when i power up i only see a progress Bar and try to connect the cradle to laptop it does not sense the device as well .I tried soft and hard reset couple of time .
Bootloader is working and its v5.15 .
I am totally helpless .
Is there anyway out from here .
I would be thankful . Please help
Hi ...
Seems the upgrade files have been corrupted. Whenever you make a soft or hard reset it trys to flash the ROM. The safest option here since the bootloader is working fine is to get a ROM backup on SD card from any other working device (it doesn't matter what ROM version), but it should be the ROM only. Make sure it's NOT the RSU backup.
Insert the SD card into the device and go to the bootloader screen. It should sense the ROM backup and will flash your XDA.
Good luck ...
Thanks to Cooperative people !
THanks !! ,
Thanks for your help .Especially to Qman and Ronin !, who went out of the way to help me fix my XDA problem .
People like them make this world a little better !
Cheers to them .
Finally after lot of struggle with Ericsson Parallet MP3 Burner which had glitch with windows XP and then XDRIT problem with windows 98 ( XDRIT does not work with 98 ) and then when i used XDRIT with windows XP thru a parallelt port ROM burner it read but declined to write . Even ROM image tool when wrote to the ROM , XDA refused to accept it a CE Rom .
Finally with right leads , I got my XDA working again !!
Thanks for your help and lead to right threads !!
Have a nice weekend and thanks for your timely help .to all who have contributed to this place called XDA forum ...
cheers to all of you ! and keep it up !!
I suppose this is not a new topic, I looked through previous posts but I was not able to find exhausting hints.
I'm in this situation:
1/ I recently updated to O2 official ROM 4.01.12
2/ I updated from 3.16.x official IT TIM ROM
3/ I'm not satisfied and I confirm what I read about drained battery, SD corruption, strange phone behaviour
4/ I have a new rom 3.18.04 but I'm not abled to flash using the remote flash: version is previous than the installed one
5/ I have a file backup of original ROM
6/ I don't have a SD with flashed the original ROM
7/ It's not clear to me how write on SD WITHOUT XDA
a/ Is it possibile to flash a previous rom?
b/ could someone address me to a suitable link?
Every kind of blame will be "supported"!
Thanks in advance
Alex
http://lumpistefan.dyndns.org/
1/ Downloaded last qtek 3.18
2/ well read documentation
3/ used xdatool
4/ created sd
5/ boot from sd
6/ GREAT, I had what I wanted
... for the moment, I'm happy
Thanks!
I have a
Dopod 818 Pro, and i would like to upgrade it using imate JAMIN's ROM.
does this void my orignal dopod warranty ? and if yes how do i overcome it ?
can someone please provide me with the steps needed to upgrade.
thanks
Don't know about the warranty but you could always resume back your original Dopod ROM if you have done a ROM backup before upgrading to a new ROM.
There is a Thai website that describes how to backup your original ROM and to upgrade to Imate JAMin ROM. Unfortunately, it's in Thai language but the pictures may help.
http://www.pdamobiz.com/forum/forum_posts.asp?TID=52433&PN=1
The most important part is at the end of the post and this is in English:
Steps to Up Rom:
1. Unlock CID (follow this link)
2. Backup original 818Pro Rom (follow the link to backup ROM to SD)
3. Enter Boot Loader (follow this link)
4. Run file JAMin_WWE_1000925_10009114_11420_ship.exe then Next, and next until finish.
Hope this helps.
thanks it worked
i used awizard to backup my rom instead
then ran the exe file and it upgraded with no problems at all
but one concern, there are pre-installed apps there that cannot be run, i get an error message saying "can not run on this device", does this mean i need a genuine imate to run it on ? , anyone knows how to fix this ?
I didn't see that problem when I ran the ROM update last week.
i used the arabic rom version, it comes with 7 apps for arabic
maybe it only works for imate, not the dopod
Khuanchai said:
There is a Thai website that describes how to backup your original ROM and to upgrade to Imate JAMin ROM. Unfortunately, it's in Thai language but the pictures may help.
http://www.pdamobiz.com/forum/forum_posts.asp?TID=52433&PN=1
Click to expand...
Click to collapse
@Khuanchai
I'm also trying to switch my Chinese system to English. So I tried the Jamin version but no success since i think i'm missing a lot of info for the right process.
I went to the Thai website you mention but I don't get a word of it...!
The short english version you give doesn't have active links so not enough information for me (its all pretty new for me...)
Any help welcome. Thanks !
Please try again:
1. Unlock CID: http://forum.xda-developers.com/viewtopic.php?t=33796&postdays=0&postorder=asc&start=0
2. Backup original 818Pro Rom: http://www.pdamobiz.com/show_news.asp?NewsID=47377
3. Enter Boot Loader: press Camera + Reset, hold camera button until you see 3-colors bands on the dopod screen
4. Run file JAMin_WWE_1000925_10009114_11420_ship.exe then Next, and next until finish.
Good luck!
Khuanchai,
I understand that flashing the Dopod 818 Pro with IMate's rom will overwrite the extended rom with IMate's version. Does following the procedures to backup the Dopod rom to sd card and then restoring from it restore Dopod's extended rom back into the unit as well?
linux2001 said:
Khuanchai,
I understand that flashing the Dopod 818 Pro with IMate's rom will overwrite the extended rom with IMate's version. Does following the procedures to backup the Dopod rom to sd card and then restoring from it restore Dopod's extended rom back into the unit as well?
Click to expand...
Click to collapse
Yes, but with the procedures described in that link, you will have the whole ROM backup. If you use that backup file to restore ROM, it will restore everything back not only the Extended_rom. However, you can backup each part of the ROM separately, for examples, use os option to backup OS ROM only, use gsm option to backup radio ROM only, or use extrom option to backup Extended_rom only. You will then have separate ROM backup files and you can restore back any part separately.
So how did it work?
What were your thoughts on performance, stability?
no that much speed difference