Related
I have the T-Mobile ROM 1.60 currently installed on my I-Mate. Now I am trying to install the latest I-Mate update, I keep getting Country ID Error 120. Anyone know a solution? It seems we need some kind of AdaptROM...
The same for me yesterday ERROR 120, I try anyway but no results
I think that new ROM only for I- mate Device with special IMEI Number :evil:
Any ideas? :?:
I upgrade to i-mate update and I try to upgrade to T-Mobile I get the same error!!
anyone can help?
try to hard way...
unzip the ruu15283wwe_cdl.exe file,
you'll find there the *.nbf files.
Use the files to flash with SD card.
I'm not sure if this also works with the XDA II, but try XDATools:
http://www.xda-developers.com/XDAtools/
tomerbn said:
try to hard way...
unzip the ruu15283wwe_cdl.exe file,
you'll find there the *.nbf files.
Use the files to flash with SD card.
I'm not sure if this also works with the XDA II, but try XDATools:
http://www.xda-developers.com/XDAtools/
Click to expand...
Click to collapse
It seems not possible by writing just writing the nbf to SD card and flash to the XDA 2 anymore.
Because the bootloader will check the first 412 bytes (i believe it is the code on the last line of the 412 bytes, somthing like HTCSA00400000XXXXXXXX.............) of the rom on the SD card match with your machine or not. Therefore without any modification, only the ROM dump from the Machine itself can be flashed.
Moreover, nbf is encoded, you can't just edit it by HEX editor, you have to get the rom in nb1 format.
I think XDA developers have to develop new tools to
1. Get the first 412 byte of the rom from your machine in an easier way. Now we have to use Multiport / USB TTY get into bootloader console, dump the rom to SD card , and use ntrw read the SD Raw data to the computer to get this 412 byte. You need a HEX Editor to do so. (Please correct me if I said something wrong).
We can
a) develop an APP to get the 412bytes from SD to harddisk without using a HEX editor
b) directly read this 412 bytes from the XDA2 if possible.
2. A Rom tools that can add your machine's own first 412bytes (or the code) , combine it with a .nb1 or .nbf and write it to a SD card.
By the way , I think a new adoptrom support XDA2 will be the best solution 8)
note added by itsme: this will very likely break your devie!! - better look at sdtool
same problem
i'm having the same problem, installed imate update, now i cant install the t-mobile update.
nobody seems to know how to fix this
HEEEEEEEEEEEEELLLLLLLLPPPPPP
try this
Hi,
another idea... :idea:
try to unzip (using winrar i.e.) the file ruu15283wwe_cdl.exe,
and run the HimaUpgradeUt.exe
It might work!
I got error, the device is not connected, or something like that, while trying to use the original file, but with the HimaUpgradeUt it works!
Tomer
Check this out http://forum.xda-developers.com/viewtopic.php?t=4785
First it was a Phone, then it became a computer phone, now it is camera computer phone... what will be the next?
Click to expand...
Click to collapse
A camera computer phone with a stable, reliable OS? Oh well, we can dream....
i have a O2 XDA II . it came loaded with 1.66WWE. i wanted to put 1.60. i downloaded it from sourceo2.com
then double clicked the installable. it started the downgrade . it said it will take 30mins & started deleted the rom image.. i then went for lunch & came back in 15mins.. the phones now totally dead.
If i dock it , the screen says USB V1.06
if i remove it the screen says Serial V1.06. I cant hard rest it nor can i soft reset it. i huess cause there no rom image in it.
What do i do.. please help with as many links software as one can..
Please...
ive got 1.72, but when i try that. it says country error.??
can that be resolved.. i dont mind loading 1.72.
the good news is that it seems you still have the boot loader working ... use ER2003 tool to modify the country code of the 1.72 ROM file ... or you can use the xda2nbftool.exe if you like the command line mode
thakns, but i have the 1.72 as an exe file. can i use er2003 to edit the file ??
hyper said:
thakns, but i have the 1.72 as an exe file. can i use er2003 to edit the file ??
Click to expand...
Click to collapse
Unpack the .exe file with winrar/winzip. And you're good to go.
Edit this file: ms_.nbf
managed to unpack it... now when i try to load 1.60 it says model id error & if i try to load 1.72 it says country id error.
what do i change in the ms_.nbf file ????
do i only change this file fields or all three??
i even removed the battery & checked the model ID. on my phone it says PH10B
i changed all the three files to PH10B ..
Now i get Connection Error.....
Now what???
now the error is ERROR 101... connection error.
(i'm loading 1.60)
also is it possible for me to do it via my emory card (i have a MMC32MB & 128MB)
if so, what file do i need to copy & then whats the procedure??
i got 1.03.00 rom on mine. my xda 2 is 2 days old now dunno wht rom to load it up with now. whts the best & safe rom now. i have no apps or nething to back up so its oki. the phone was bought from u.k. and was locked on O2 network. now its unlocked and being used in India. plz advise wht ROM to d/n and use. if possible the d/n link as well. thx
Question?
Why do you want to downgrade your phone? :shock:
For upgrade to 1.72:
1. Download i-mate 1.72 update and xda2nbftool
2. unpack that update to any directory on your harddrive
3. download script from this post to created directory (unpack it too)
4. copy xda2nbftool.exe to that directory
5. run provided script
6. insert XDA2 to cradle and then HimaUpgradeUt.exe
You will i-mate splash screen from i-mate though, but working device.
thanks for all the help. but im yet getting country ID error even after running the process .
this process basically converts the id to O2, in a batch dos mode... right??
then y is the problem yet there.
i wonder... most O2 XDA II come with 1.6 rom version. mine came with 1.66. could that mean its not O2 even though its written O2 on my phone? could it mean its T-Mobile or something??
can someone post a link or software that i need to put onto my MMC card & then use that to install the rom from the card inserted in the phone??
hyper said:
thanks for all the help. but im yet getting country ID error even after running the process .
this process basically converts the id to O2, in a batch dos mode... right??
then y is the problem yet there.
Click to expand...
Click to collapse
So, what's that problem? Can you run it?
Try to run it in command prompt... And if it writes any error, post it here...
Can you access the file system of your XDA2 from ActiveSync -> Explore?
now i managed to get the problem of Country error out of the way , but now im getting the ERROR 101 - Connection Error.
no i cannot browse any files & my active sync does not show connected.
what files do i need to copy paste onto my MMC card so that i can flash it by executing the files with the camera button & the MMC Card inserted??
im dowloading the NTRW & 1.72 NK.nb1 file. do i just copy & paste it on the mmc card & then instert the card into the phone & then press the camera button.. should this do the trick??
this is all that i have tried so far... yet no luck.
my phones originally from malaysia , its an O2 XDA II
i have the following rom with me. my bootloader is V1.06
1. RUU172800WWE_CDL_SKU1
2. XDA_IIupgrade_v16050
3. RUU172104wwe-t-mobile-uk
1. i removed the battery , dcoked the phone, connected the charger to the docking bay at the back...the red light on the phone lights up.... the bootloader screen shows up ina slightly distorted manner.
i then ran all the three roms as it is..without editing anthing. The error i get in all the three times is ERROR 101. CONNECTION ERROR. it tells me to check is usb is connected, charger is connected usb port is conencted & the phone is on. .......... everythings connected but obviously phone can only be in bootloader mode.
2. i put the battery back in dock the phone, the charger is yet connected to the back of the docking bay. .. i try all three installations withour extracting or editing as they are exe files..... now, all the three times i get COUNTRY ID ERROR OR MODEL ID ERROR.
3. when i edit the ones that give me model id error then i get CONNECTION ERROR AGAIN. (this is again with the battery in & charger plugged in)
i downloaded the NTRW & 1.72 NK.nb1 file. but the one that is available on this forum is corrupted. so i cannot extract it.
NTRW ive downloaded seperately. i need the nb1 file now. can someone post a working, no-corrupted image rom image file?
once i get the correct Rom.nb1 file... all i have to do it copy & paste the correct rom.nb1 & ntrw.exe file onto my MMC card & keep the battery in the phone & insert the MMC card & press the Camera button .... is that correct? i'm guessing that this will run the ntrw exe file & load (dump) the Rom.nb1 file onto the phone. is that correct?
please do let me know what else i can try & dowload a newer RUU or something. i think the best way is to SD flash the phone.
i dont even mind flashing it to a PPC2002 version & then upgrading it from there. if thats possible.
As far as the connection between the USB Docking Bay is concerned,...everytim i connect or disconnect the phone, i hear the familiar XP "TING" which shows that some USB thing is connected, but my active sync does not show that the phones connected, i guess that cause it got no rom in it.
Also when i edit the ms_ / NK / Rom files er2003 i get an error everytime i start the software, but i just press IGNORE & continue. i always get ROM successfully written & then the error pops up again but i keep pressing ignore. this works... but whats up with the CONNECTION ERROR. IF ITS NOT CONNECTING TO THE PHONE, HOW DOES IT KNOW THAT THE MODEL ID OR COUNTRY ID WRONG ???
Ok.
If any ROM update can detect your device (as we can see error messages COUNTRY ID ERROR or MODEL ID ERROR), there is hope, you can update your device.
If it's 1.72 ROM (that writes COUNTRY ID ERROR or MODEL ID ERROR), use the solution I send you few posts ago (unpacking, running batch script etc.)
When you updating, keep battery in your device and charger of device connected to cradle! Don't remove anything.
BTW: Don't use RUU172800WWE_CDL_SKU1 update, it just update only part of your device (ExtROM)!
BTW2: Read this: http://wiki.xda-developers.com/wiki/HimalayaRomFlashing
thanks againa beecher. the problem is that once i use the patch & then run it. it does not show me the country id or model id error (for which i thank you) but then it says error connecting.
i have a USB to serial connector. should i try serial connection?? or maybe try it on another computer.
can anyone please tell me how do to a SD flash step by step with the Rom.nb1 file attachment of link.
Firstly, forgive me if this has been covered - I tried searching for this but didn't find an answer...
I'm trying to upgrade my Orange M1000 to WM5 and am worried that I'll totally destroy my machine, so I'm treading as carefully as possible.
I've been following the instructions from xda2jojo but came across something very quickly:
The instructions say to search for nb.nbf. I guessed this might be a typo (?) so I downloaded nk.nbf instead.
I went to patch it but I get an error: "Sorry, this file cannot be patched!"
Also, when in the ROM editor, there is no option for Orange - which should I use instead?
Am I being really dumb or is this a real problem?
Thanks
MkS
The Same Problem in TSM500
I also have the same problem
I tried to patch NK.nbf but it fails, showing the message "Sorry, this file cannot be patched"
I also tried to update my TSM500 without editing this file, but it doesn't seem to connect. And when it connects, it shows a message saying that tuere is a language error.
I used HimaGetDeviceData to get the language configuration, but un file "Devicedata.txt" there is only a "U" and nothing else. There isn´t language nor version number, nothing...
copy the file Devicedata.txt to your pc and open it there.
Use this Himaupgrade file that bypases country and telco identity
ftp://xda:[email protected]/Himalaya_SEs/HimaFiles/himaupgradeut_197.exe
I hope that this help...
Does that also get around the fact that the patch1.exe program claims that nk.nbf cannot be patched?
What this patch for ?
Sorry for question . What this patch for ?
I have no idea, but the instructions for upgrading to WM5 say you've got to patch nk.nbf.
I had the same problem
:arrow: I had the same problem ... so I did upgrade without patching .
By the way Sprite Back Up is not working .
Pocket Informant impossible to install .
Hi - get the same problem with the patch. Am treading carefully too to ensure i don't have an expensive paperweight.
Anyone know if the patch is mandatory or is the file linked via the wiki for w2k05 ROM already patched and ready to go and therefore need to skip this step according to the FAQ
Thanks
Finally updated
Finally I got my xdaII updated. I didn't patch nk.nbf, I only uploaded the file.
The xda started correctly, and after an hour since I updated it, I only saw that the buttons "camera" and "recording" (left side of tha xda) doesn't seem to work.
I think that the memory is too low. Maybe I chose a wrong version of WM2005.
Storage
Total: 14.57 MB
In use: 1.74 MB
Free: 12.83 MB
Program
Total: 24.35 MB
In use: 14.94 MB
Free: 9.41 MB
Anybody else have the same memory problem?
Thx
(Pd: Voice recording key only works when display is off)
patch NK.nbf but it fails
hi guys
I also have the same problem
I tried to patch NK.nbf but it fails, showing the message "Sorry, this file cannot be patched"
Can any one help us
tKS
Upgrade successful
I had the same problem. I did not patch and performed the upgrade. Everything works fine except the record and camera buttons. Vito Button mapper does not help either, but it does allow you to make the contact & calendar buttons multi-functional so they can replace the for-now missing buttons.
Good luck.
Who else to ask ?
I did PM to xda2jojo and I have no answer ? probably he is busy .
sorry to edit this....give me time to edit the procedure---xda2jojo
if you received the "Sorry, this file cannot be patched" error message ..
there are only two reason .. maybe you downloaded a corrupted nk.nbf ..
exact size of nk.nbf
1.50f.00WWE
is 33,554,496 bytes(32,769kb)
1.50f.blWWE (BuzzMobile 2005)
is also 33,554,496 bytes(32,769kb)
but if you think you downloaded it right and still receive this error ..
it only means that you downloaded a already patched ROM and no need to patch it anymore ..
just skip the procedures about patching the rom
and go directly to upgrading
now if you receive a country id Error .. just use modified Himaupgradeut.exe
read the wiki
http://wiki.xda-developers.com/index.php?pagename=Himalaya_2005
to know where you can get the file
Thanks
Thanks
That's cool - thanks!
Bugger - I had to go back down to 2003SE.
No MMS, no Messenger, and no working Activesync. It looked so great too. It was the MMS and Activesync issues that were key for me though. Will wait till a definitive fix is found and try again.
Thanks for your help, though, guys. If I hadn't tried, I'd never know.
Messenger works OK on mine. Activesync works OK on my laptop, but not my Desktop. MMS doesn't work though, yet.
same problem
hey ppl i 2 have the sameproblem my file size of nk.nbf is 32,769 kb is that ok i also do not ahve active sync 4 installe dnither do i have service pack 2 isntalled is it sensible 2 insatall or will it screw up myprecious xda2?plz let me kno asap
thanx
This is how i did it, works to the T 4 me (I Have A Zipped NK.NBF)
Step 1
Unzip From First Part, (It Should Automatically Unzip Second Part)
(Ignore this if you already have unzipped NK.NBF)
Step 2
Using WM2005patch1.exe Patch The NK.NBF File
Step 3
Using ER2003Edit Change The Country Code 2, O2 WWE
Step 4
Run HimaUpgradeUt.exe
Step 5
Once All Installed Reboot Fone And Run ExtROM_WM2005.cab,
ExtROMUnlocker(for_WM2005Only).cab And BuzzWM2005RAMDisk-Full.cab
2 unlock hidden memory!
(Shows 124mb Ramdisk & 15mb Storage formaly known as ExtRom)
Not sure if there is updated ramdisk or not...
My activesync 4 works flawlessy With Win XP Service Pack 2,
MMS Doesn't Work For Me Either,
I have downgraded back 2 wm2003se for this reason...
Well just untill Someone gets it running again...
Good Luck, & Ave Fun! The general layout onWM2005 is great.
Hi all, i normally make custom roms for our devices but am having issues with this one, its about to be the 1st Hermes in space [coz i am gonna strap it to a firework and send it skyward ]. I have the ExtROM unhider, i remove all the rubbish, i add my custom read-only cab's [all signed btw] edit my config.txt, then hard reset the device. All looks ok on the loading stage, you see my cabs being called and run, but they move on to the next file far to fast, and when i check the programs installed after, its not there, so its skipping the cab files. No errors on load, nothing, if u run the files manually they work but i did noticed they say "Unknown Publisher" on the certificate part of the install. Does anyone have any suggestions on how to overcome this please.
Thank you in advance
EViLOPTiC
Hermes startup is full security mode. Your CABS need to be signed by a trusted root CA and you might even need the more secure provider level signature (although I'm not sure of this).
V1605
Hey EViLOPTiC,
IK see you are having the same problem as I'm having with my V1605.
I had a Qtek 9000 before did the ext Rom modification had no problem, I had a Signed disable security cab which I run in the cab first then all the another after no problem.
Now with this pda the signed cab still says it is not signed I've tryed anothe 3 another disable security cab but with the same issue.
All we need is a signed cab file that well modify the register 0000101a from 1 to 0 put that in the Extended Rom followed by all the another cab file we want to install.
Where can we find this cab.
PLEASE SOMEONE HELP US PLEASEEEEEEEEEEEEEE
Thanks
Gigino
Hi all
If I want to be able to acces OrangeWorld and TV (wap portal and mobile TV from my provider) I must use a branded device or provide an authorized UserAgent. Yes it's like most of people...
Usualy I use NetFront but today I've decided to make it big and patching browser.dll to use pocketIE. After 3-4 hour googling I finally succeeded on extracting browser.dll off of the nk.nbf provided by Prophet ShadoW 1.0 (rom that I currently use). I've patched it with a hex edit program and tried to put it in the Windows directory.
I simply can't put anything who already exists in the windows folder. How can I do to use this patched version of the dll ?
If someone can help it would be nice
AnarX