Database Develop

How you like your Fried XDA 2? Sunny Side Up?

Hello,
I was today handed a fried XDA 2.
My boss had attemted to flash it and it failed for whatever reason.
Now i will say from the outset that i have only ever flashed my XDA1 with a XDA-Developers ROM and it was a breeze.
The ROM file HE flashed with was called.
Xda_II_Upgrade_v16050.exe
Now when you switch the thing on.. all you get is a a small amount of txt saying
'Serial'
'v1.06'
and nothing else..
What have i done? Well i have sifted through the articles on here.. and found this rom
XDA-developers-SER-v12.exe
I have installed this on an SD card using xdatools.. WHOLESALE.. i.e. no moding of the files...
I have looked at 'http://wiki.xda-developers.com/wiki/HimalayaRomFlashing'
but as i can boot into the device.. i cant get the info it requires.
I am open to any and all help. And I'll even buy you a pint!
I am really at a lose.
Thanks in advance Guys and Girls.

It may not be as bad as you think.
It is in bootloader mode - currently in Serial mode and if you put it in a cradle connected to a PC (with ActiveSync installed) the bootloader should change to USB v 1.06. From this point you should be able to load a normal ROM from the manufacturer.
I have an i-mate, so am not sure what the current ROM version for the XDA II is, but I'm sure others will chime in with this information.

I upgraded to this version, not knowing I already had this loaded. You need to check the extROM version before upgrading as this appears to be way the official upgrades seem to change.
I had no problems and it was done through the Active Sync process
The file can be found here if you haven't already got it... http://www.my-xda.com/downloads.html
Try it again. It does take about 90 mins.
Regards

Nope... Nadda... Zip... Zilch.
Roit...
When i dock the pesky thing in the USB craddle.. it does display USB and v.1.06.
Activesync shows NO sign of knowing the XDA is there.
The ROM found at http://www.my-xda.com/downloads.html as suggested by flintanis fails with a ERROR 100: MODEL ID ERROR.
BRosenow what do you mean by 'load a normal ROM form the manufacturer' is that not what i have just tried?
Once again a pint for all contributors.. and my first born to the dude with the solution.
Cheers.

ActriveSync won't activate because it's in Boot loader mode but you can download the latest ROM Update from the manufacturer or cellphone service provider and load that to flash the ROM and complete the process.
If it's a UK XDAII, get the update at www.my-xda.com .

It appears the previous user tried to flash it with a ROM from another manufacturer (Q-Tek/MDA II/i-mate). You are now receiving a Model/Country ID error. I have not experienced this myself, but I have read posts in this forum on how to fix it. Do a search and I bet you will find it.
- OR - any user who has experienced this and successfully flashed his ROM could chime in here and give jonathh some advice . . .

After much ado about nothing..
i have returned to again fix this XDA2 (the joys of pesky FT employment; make your minds up guys.. you want this XDA2 fixed or not?)
Right i *think* with quite a high level of certainty that the XDA2 currently in my grubby mitts was purchased in Malaysia/Sinapore.
Now.. am i correct in that flashing it Xda_II_Upgrade_v16050.exe from http://www.my-xda.com/downloads.html
Would cuase the problem i have now.. or at the very least wont go on on the XDA2 now because it is a UK ROM and a Malaysia XDA2?
I have flicked thru the pages on here.. and i cant seen to see how to solve this!!
PPllleeasseee help
*sobs, and gently rocks back and fourth*

I think there is a bit of confusion going on in this post!
The first ROM you tried (XDA-developers-SER-v12.exe) is for XDA1 - NOT XDA2.
The best place to get the latest UK XDA2 ROM is http://www.sourceo2.com/O2_Developers/Devices/O2_Xda_II/XdaIIRom.htm
and i *believe* that the place to download the Malaysia ROM is
http://www.myxda.com/XdaII/serviceandsupport/template/XdaIISoftwareUpgrade.vm (note the absence of the '-' between my and xda...this is the Asian O2 website)
See if the ROM from either of those sites will install
Hope that helps!

How about scrambled?
Ok, thanks 'pope'
*none* of the roms suggest work..
Xda_II_Upgrade_v16050.exe reports unknown country code..
and the recently suggested
Xda_II_LaunchROM_v10311.exe just sticks on the 'checking for information' left it for over an hour! BUT doesn't report unknown country code like the other one.
I cant get the XDA2 rom from the Asia site, as after i registerd my XDA2 it reports i dont need the damn update... anyone got it already?
I have extracted the core files from both these exe's and tried to copy them to an SD card(the NBF fille) using XDAtools.. and xdatools report the files are invalid.
I am lost and clueless!
HHHEEELLLPPPPP

Well that didn't work...
I got my grimmy grits on another XDA2 and using XDAtools sucked the ROM off of that.. and then.. again using XDAtools squirtted it out onto an SD card..
But i am unsure what i have to do then? is this latest approach possible??
Comments welcome![/code]

Love to help… but
My UK O2 XDA II has exactly the same problem. I died whilst flashing the UK O2 1.60 ROM, and now I can't do anything with it. Identical symptoms. Identical complete lack of success (eight hours and counting).
How can I find out the country ID of my device when my XDAII is dead?

mark8barnes said:
Love to help… but
My UK O2 XDA II has exactly the same problem. I died whilst flashing the UK O2 1.60 ROM, and now I can't do anything with it. Identical symptoms. Identical complete lack of success (eight hours and counting).
How can I find out the country ID of my device when my XDAII is dead?
Click to expand...
Click to collapse
O2 will fix this for you if it happened as a result of flashing with their rom.

By they way, in case anyone was concerned when I said " I died whilst flashing the UK ROM", I did of course mean "it died..." ;-)
But I have solved my own problem! How come you can spend hours trying to find a solution, and as soon as you ask for help, you sort it out straight away??!!
I hope this works for you if you're still struggling.
1) Download the latest i_Mate ROM from http://www.clubimate.com/Support/RUU172126WWE_imate.exe
2) Download the XDAII Rom Editor from http://wiki.xda-developers.com/uploads/ER2003Edit_1_2_20.msi
3) Extract the files from the IMate ROM, and use the ROM Editor to change the Operator to 02. Get the instructions here and the password here
4) Flash the ROM as normal. It worked for me You could experiment with using the O2 extended ROM files rather than the T-Mobile ones, but I was just glad to get the thing working. Perhaps I'll feel braver later.

I did feel braver, and copied the O2 Cabs into the IMate Extended ROM file. Then I deleted the IMate cabs I didn't want, modified config.txt and prayed! Everything seems to have gone fine, and I'm now re-installing all the software. Already there seems to be a significant speed increase over 1.60.
I'd recommend taking this step before you flash the ROM, rather than doing it twice like I did.

mark8barnes is the man!
I didn't do the mods.. just as per your original post.. and it worked!! Yay
Thanks mate you da man!
Now i do have a query tho.. if i did suck the rom off using XDATools.. how would i get it bck on again?
Cheers all you guys..

Fried XDA
Hello Mark
Me too, I flashed my ROM with the UK version with the same result.
The link to the iMate ROM no longer exists, can you help me please. I'm a real novice at this.
Thank you
Ben (Aust)
mark8barnes said:
By they way, in case anyone was concerned when I said " I died whilst flashing the UK ROM", I did of course mean "it died..." ;-)
But I have solved my own problem! How come you can spend hours trying to find a solution, and as soon as you ask for help, you sort it out straight away??!!
I hope this works for you if you're still struggling.
1) Download the latest i_Mate ROM from http://www.clubimate.com/Support/RUU172126WWE_imate.exe
2) Download the XDAII Rom Editor from http://wiki.xda-developers.com/uploads/ER2003Edit_1_2_20.msi
3) Extract the files from the IMate ROM, and use the ROM Editor to change the Operator to 02. Get the instructions here and the password here
4) Flash the ROM as normal. It worked for me You could experiment with using the O2 extended ROM files rather than the T-Mobile ones, but I was just glad to get the thing working. Perhaps I'll feel braver later.
Click to expand...
Click to collapse

unlock Extended rom for XDA IIs

HI anyone
I have used the extend rom unlock software download which works for XDAII before but not work for my XDA IIs - saying somekind of errors...
Can anyone teach me how to unlock it?
Thanks

this was my answer yesterday :
http://forum.xda-developers.com/viewtopic.php?t=15502[/url]

HI M4io
Thanks for your file. Do I need to reset everytime unlock and lock? (this is the case I noted)

reset is only necessary after unhide/hide.
Not after lock/unlock
at least in my experience on Himalaya

Unlocking XDA iis UK version
Your program doesn't seem to work on mine. Still asks me for a network simlock code!
:-(

this is about unlocking Extended Rom , not Simlock

Shame really.
Thanks anyway.

I have tested twice, you need to reset for lock and unlock. Different from XDA II.
May be you can try this see if it works. The program from M4io work great.

I think i got confused. I wanted to unlock my XDA iis so I can use a non-O2 sim.
It seems this tool is for something else and I have no idea what it's for. I just got excited that it could unlock my precious XDA iis!
Cheers.

Hi anyone
Have you unlocked XDAIIs extended rom and tailor maded with config file amended? I have done this but when hard reset, it did not install the additional program such as the new version of caller ID and extended rom unlocker

Hi anyone
Have you unlocked XDAIIs extended rom and tailor maded with config file amended? I have done this but when hard reset, it did not install the additional program such as the new version of caller ID and extended rom unlocker

2.21 IPL/SPL observation

Dear All,
I would like to share a bit more information on what I found regarding 2.21 IPL/SPL behaviour.
1. Now it is impossible to backup the rom from another machine with pre-2.21 ROM and then try to flash it into the machine by SD Card (i.e. use console mode to connect to the pre-2.21 ROM machine, execute r2sd, then push the SD card to the 2.21 machine w/o CID unlock and boot into flash mode (camera button), it will say 'Not allow update' in the status bar)
2. Now it is also impossible to backup the rom from 2.21 machine using console mode (i.e. r2sd), thus I got no way to extract 2.21 IPL/SPL from my machine. Again this is assumed the machine is not CID unlocked. Machine will say 'not enough security level blah blah....'
3. So what I want to know is- If a machine which is pre-CID unlocked, upgraded to ship rom 2.21+
a. is that still possible to dump the firmware out with r2sd?
b. Also will it accept rom flash in SD card dumped out from other pre 2.21 machine?
Hope we could sort out a solution to free all 2.21+ guys

Someone says its also related to the G3/G4 chip (version # 2.21.0001 means G4, .0000 means G3??) I have no clue on what is that though- anyone can provide us some enlightment?

William Yeung said:
Someone says its also related to the G3/G4 chip (version # 2.21.0001 means G4, .0000 means G3??) I have no clue on what is that though- anyone can provide us some enlightment?
Click to expand...
Click to collapse
No, they are just the software version and dont have any relation with the Chip.

Result from JAFWM
Open nk.nbf file with JAFWM v2.2 (Dopod Official Rom)
here is the result.

William Yeung said:
Dear All,
I would like to share a bit more information on what I found regarding 2.21 IPL/SPL behaviour.
1. Now it is impossible to backup the rom from another machine with pre-2.21 ROM and then try to flash it into the machine by SD Card (i.e. use console mode to connect to the pre-2.21 ROM machine, execute r2sd, then push the SD card to the 2.21 machine w/o CID unlock and boot into flash mode (camera button), it will say 'Not allow update' in the status bar)
2. Now it is also impossible to backup the rom from 2.21 machine using console mode (i.e. r2sd), thus I got no way to extract 2.21 IPL/SPL from my machine. Again this is assumed the machine is not CID unlocked. Machine will say 'not enough security level blah blah....'
3. So what I want to know is- If a machine which is pre-CID unlocked, upgraded to ship rom 2.21+
a. is that still possible to dump the firmware out with r2sd?
b. Also will it accept rom flash in SD card dumped out from other pre 2.21 machine?
Hope we could sort out a solution to free all 2.21+ guys
Click to expand...
Click to collapse
the anser to your question on point 3.a is yes.done it myself.now reflashing your device with another ones dump it may cause problems because it also flashes back the cid [whatever state it is] and since every device has a unique cid code that is related to the imei it may cause problems like the dreaded DATA CRASH one,but in other hand it could work.u just have to try to find out.if you need a unlocked dump let me know a got one ready to install.

How about the bootloader mode test result? anyone could provide?

Well I think there is a way and may be summitter can tell better.
one use typhoon nbf tools and remove the CID and save the nk.nbf and flash it to device.
secondly dump the rom parts with typho5 and just make a custom ROM with the same IPL/SPL with a new CE ROM...
I hope I am correct

That wont work, you have to try it out yourself. The main issue is if you got a machine comes with 2.21.0001+, then r2sd would not work. This is the essential step for any rom dump operation so far.
Typhoon NBF is even worse because since 2.0 (AKU 2) rom its not able to read by Typhoon NBF.
*faria: Is that mean you can still use r2sd to dump your rom even after your machine upgraded to 2.21+ ROM? Then if there is an O2 Mini S with such config updated, dump rom out, use typho5 to rebuild a new ROM without CID, chance is that we could use that to patch the unit with other rom versions.

William Yeung said:
That wont work, you have to try it out yourself. The main issue is if you got a machine comes with 2.21.0001+, then r2sd would not work. This is the essential step for any rom dump operation so far.
Typhoon NBF is even worse because since 2.0 (AKU 2) rom its not able to read by Typhoon NBF.
*faria: Is that mean you can still use r2sd to dump your rom even after your machine upgraded to 2.21+ ROM? Then if there is an O2 Mini S with such config updated, dump rom out, use typho5 to rebuild a new ROM without CID, chance is that we could use that to patch the unit with other rom versions.
Click to expand...
Click to collapse
yes you can still use r2sd in any rom above 2xxxx,but i do not use r2sd for my backups/restores, i use [wizBackup] because it bacups to sd and pc without any conversion required unlike r2sd.
i just made a sd backup of rom 2.23 and restore with out any problems.
rebuilding any rom will not work in a machine cidlocked because when we build the roms it requires the cid field to be blank,if it was that easy any modified rom like [sumiters] would do because all of those roms have the cid field blank when they are converted with nbf connverter.
to be clear about the part of the cid lock that every one is trying to unlock is not in the rom ,it is in the machine in a diferent adress [place if you like] itself so until someone cracks the cid area of the new roms there not much you can do.the problem is noone has the tools for the new roms to bypass cid.
the lokiwiz tool patches the cid area of the device only it doe nothing to yor rom.
so if you try to install a patched rom the machine will compare the cid code in the rom with the one in the machine if it does not match it does not install.1 way arround it to buid you own rom and put the machine cid code on the rom ,the it will install .but that means u cannot create a universal rom, it has to be 1 rom per singe machine with matching cid number.
and yes u can use typho5 to decode/incode 2.xxx roms with any problems,i have been using it i my roms without problems.

Wizard is not such a big problem but for the hermes it is even more interesting. Hard times are coming :roll:

raskal said:
Wizard is not such a big problem but for the hermes it is even more interesting. Hard times are coming :roll:
Click to expand...
Click to collapse
Hi Raskal,
If "Wizard is not such a big problem", why don't you keep with the spirit of xda-dev and share your observations and results on the G4 issues with the board?
There are two major areas where I think you have an opportunity to contribute to the community:
1 - Can you assist in the modification of the nb2nbf tool so that both G3 and G4 bootloaders can be rebuilt into an image?
2 - We need some guidance on CID unlocking 2.xx. What have you found in the BL that has made the usual process ineffective?
I'm assuming that since you are a member here, you're willing to give as much as take like the rest of us. I have a great respect for what you have done with various phones of the years, and appreciate that you are in business. However I hope that while you're here you will contribute to the free flow of information.

summiter said:
raskal said:
Wizard is not such a big problem but for the hermes it is even more interesting. Hard times are coming :roll:
Click to expand...
Click to collapse
Hi Raskal,
If "Wizard is not such a big problem", why don't you keep with the spirit of xda-dev and share your observations and results on the G4 issues with the board?
There are two major areas where I think you have an opportunity to contribute to the community:
1 - Can you assist in the modification of the nb2nbf tool so that both G3 and G4 bootloaders can be rebuilt into an image?
2 - We need some guidance on CID unlocking 2.xx. What have you found in the BL that has made the usual process ineffective?
I'm assuming that since you are a member here, you're willing to give as much as take like the rest of us. I have a great respect for what you have done with various phones of the years, and appreciate that you are in business. However I hope that while you're here you will contribute to the free flow of information.
Click to expand...
Click to collapse
I am reading this forum and i learned a lot from it. This is the reason i donate and will continue to donate as long as this forum is helpfull because the guys are handling this forum simply deserve it, webspace cost money, traffic costs money and they also spend a lot of time for the mainatance of the forum, time is money. This is my contribution sofar.
On other way, i am not a lover of freeware. My devices costs money because i also spend my time developing it, and i also have a company with 30 employees and i am responsable every moth at 30 to pay them their salary and assure them the salary for their next month. Also my partner is dealing with phones, do you not think i would be very sad when i see that our competition unlocking/debranding phones with OUR FREE SOFTWARE ?
All i want to say, i am willing share information, but i am not willing share any information regarding unlocking/debranding since it will affect my own buiness.

raskal said:
summiter said:
raskal said:
Wizard is not such a big problem but for the hermes it is even more interesting. Hard times are coming :roll:
Click to expand...
Click to collapse
Hi Raskal,
If "Wizard is not such a big problem", why don't you keep with the spirit of xda-dev and share your observations and results on the G4 issues with the board?
There are two major areas where I think you have an opportunity to contribute to the community:
1 - Can you assist in the modification of the nb2nbf tool so that both G3 and G4 bootloaders can be rebuilt into an image?
2 - We need some guidance on CID unlocking 2.xx. What have you found in the BL that has made the usual process ineffective?
I'm assuming that since you are a member here, you're willing to give as much as take like the rest of us. I have a great respect for what you have done with various phones of the years, and appreciate that you are in business. However I hope that while you're here you will contribute to the free flow of information.
Click to expand...
Click to collapse
I am reading this forum and i learned a lot from it. This is the reason i donate and will continue to donate as long as this forum is helpfull because the guys are handling this forum simply deserve it, webspace cost money, traffic costs money and they also spend a lot of time for the mainatance of the forum, time is money. This is my contribution sofar.
On other way, i am not a lover of freeware. My devices costs money because i also spend my time developing it, and i also have a company with 30 employees and i am responsable every moth at 30 to pay them their salary and assure them the salary for their next month. Also my partner is dealing with phones, do you not think i would be very sad when i see that our competition unlocking/debranding phones with OUR FREE SOFTWARE ?
All i want to say, i am willing share information, but i am not willing share any information regarding unlocking/debranding since it will affect my own buiness.
Click to expand...
Click to collapse
I'm pretty sure that nowhere in my message was there a request for free software.
We'll continue our efforts here as a community to share ideas and create working and free solutions for all.
Quick question - does your ROM collection include any of the custom ROMs created by and for folks here on xda-dev?

well, at least he donates a fair bit to the site... machinagod!! When can we see Lokiwiz 3.x with CID Unlocking!!?

i guess if machinegod and others, did not post is tools and info here,some companys would have a dent in their revenue. and then one would think....
why do i bother?!!!!

hjkl;' why no delete?

Trinity (P3600) extended rom writing protection

Hi.
First of all...sorry for my poor english
I have a problem with my
HTC P3600 (Trinity)(RUU_Trinity_HTC_ITA_1.23.408.1_6275_1.38 .00.11_108 _Test upgraded)
about the UNLOCK process of the extended rom.
With HTweakC i've made it readable so,now,i'm able to view the content.
After this i've tried with registry hacks i've found in various topics to make it writable with no success.
I used also HERMES_..rom.cab but the ext_rom itsn't writable yet.
If someone knows a solution or a simple advice i'll be glad.
Have a nice day.

spook2099 said:
Hi.
First of all...sorry for my poor english
I have a problem with my
HTC P3600 (Trinity)(RUU_Trinity_HTC_ITA_1.23.408.1_6275_1.38 .00.11_108 _Test upgraded)
about the UNLOCK process of the extended rom.
With HTweakC i've made it readable so,now,i'm able to view the content.
After this i've tried with registry hacks i've found in various topics to make it writable with no success.
I used also HERMES_..rom.cab but the ext_rom itsn't writable yet.
If someone knows a solution or a simple advice i'll be glad.
Have a nice day.
Click to expand...
Click to collapse
There is a solution by OLIPRO which is supposed to unlock the ExRombut it does't always work,on the other hand if you use the SIM/CID unlocker by POF you will get a super CID device with an unlocked ExRom but with issues about your warranty.
If i were you i'd wait a bit especially if your device is new .

write problem ext_rom p3600 (trinity)
ok,tx a lot for ur useful tech info...i've searched for Olipro post and the SIM/CID unlocker and i've found it...about the warranty problem,i thank u for the advice,in effect my device is new...but curiosity...
In the meanwhile i'm going to try with registry hacks again and i hope i'll solve the problem without the unlock process.
If someone will found new tricks about this problem...i'll be glad to read it here
nice day at all

Olipro's extrom writeable unlocker isn't working.
At least it didn't work for anyone so far when we tried it a short while ago.

Mass Flash

Evenin' all.
Might be a long shot, and I think I walready know the answer but thought I would just double check quickly.
I have about 100 HTC TyTnII phones that are on windows mobile 6.1 and need be downgraded to windows mobile 6.0 due to incompatible software.
Each day i am also having to do the same with a small handful of other TyTnII phones.
I have flashed a load of them with no problems using USB. Yesterday i tried to use an SD card which also worked fine on a test phone that we use for development, but it wont work on phones arriving direct from the factory.
Im pretty certain that its because i ened to unlock the CID (???) or flash the SPL (???) but this is time consuming and tedious.
Is there anyway of doing this part using an SD card? If not, what is the fastest way to do it on the road or on site when i dont have access to my computer?
Any ideas that you can bounce at me would be appreciated, and also it would be a good help if you can verify if what i have said is correct.
Cheers guys.
-AJ

Moved as not ROM Development.
As long as you use the original carrier ROM then CID won't be an issue.

Sorry about posting in the wrong place, was searching the forum for an answer and see a post in this area regarding a similar issue.
When you say original carrier ROM, do you meant the extaxt same rom that came with the phone, or a ROM from the same network provider ect?
They are English Orange WM6.1, so would I need any other English Orange WM6.0 rom? Or am i (probably) mistaken?

Your correct CID checks the vendor ID so you have Orange WM6.1 you will want Orange WM6 ROM as then vendor ID matches.
The other option is to just hard-spl them all wouldn't take long with laptop 5 mins each then you can bypass vendor ID check. "may be easier as don't know if Orange WM6 easily available?"

Would I be able to use WinRar to extract the NBH file from here and use that to flash the phone via SD Card without modifying or touching anything else on the phone?
RUU_Kaiser_ORANGE_UK_1.81.61.2_radio_sign_22.45.88.07_1.27.12.29R_Ship.exe

Just wondering if anyone has got any more info on this?

avisonjohn said:
Just wondering if anyone has got any more info on this?
Click to expand...
Click to collapse
Well if they branded Orange it will work, lol you got so many i thought you would have tried it by now