Hi All
I have a SPV M2000.One day the phone stopped working. Everything was all right, it did ask for pin but then didn't even looked for network,was immediately saying NO SERVICE. I tried few sim cards - the same.
So then I wanted to reinstall the ROM, I downloaded the official from Orange UK , tried to install it,and it shows ERROR 114, Radio Rom Upgrade Error.
And the phone now is in bootloader mode and I can't do anything!
I downloaded different ROM from xda-developers ,at the beggining with a country error, but i managed to fix it and now with this ROM it's the same thing. ERROR 114. I tried everything, hard,soft reset, Pc reset etc. Nothing works!PPC still in bootloader mode!
Please tell me if you know what else can I try!
Guys,come on,really noone knows???
Have you read WIKI? Follow the first method to flash your ROM. Have you remembered to plug in your power supply to your cradle when you flash your device?
Heres another thread on NO SERVICE Plz help... No Service after radio upgrade. Happened to me. Read it and see the advise by MDAIIIUser and TheLastOne. If all else fails, bring it to the shop.
I had a very similar problem....
First I tried to update a whole package that means rom, extended rom and radio
The radio update is always the first one and there always upgrade error 114 occured.
So I updated every part seperately and it works except the radio. So I tried alot but it just didn't work..even downgrading was impossible. MDAIIIuser and happy goat tried to help me as well as they could but nothing had an effect.
So I read in another forum that asus mainboards have some problemes with these radio updates....I thought they were joking...but I tried the radio pdate at another pc and it worked!
I know it sounds a bit stupid but I was desperate and at last it worked!
You can read it here :
http://forum.xda-developers.com/viewtopic.php?p=89657#89657
TRied that method.Doesn't work
Any other ideas?
One more thing.Is it normal that in bootloader mode when I plug the power cable in the charging LED is not working?it was working before.
The battery is charged ,but shouldn't it show that the power is connected anyway?
EDIT: this is a reply to the first answer.
So you think I should try on another PC?I will today!Hopefully it will work.
So I managed to install new rom on a different computer! I think that there was a problem with active sync.I used the one that was installed from my old XDAII.Could that be the reason?Now i installed the one provided with a M2000.
But it doesn't work anyway
Still NO SERVICE message.
ANy other ideas different than taking it to Orange?
Hi rottie,
No Service could mean anything. Could your SIM card be faulty? Device SIM locked? Or hardware faulty? You cannot just use any ROMs you find at ftp. Try to flash your device with full shipped rom at http://wiki.xda-developers.com/index.php?pagename=BA_1.40.00_Upgrade. Use the first method and upgrade using MaUpgradeUt_noID.exe to bypass the Country code error. Remember that you'd need to run MaUpgradeUt_noID.exe twice.
Read wiki carefully, it has alot of precious information. Cheers ^^
Before you update any version you should be sure that your radio is
compatible with your device. Usually all radio upgrades should be
independent off the language of the device but as I understood (could be
wrong) there are differences because of the servicenetwork frequency.
So you must be sure that the chosen radio is compatible and that your
device is not simlocked.
So perhabs you should chose an upgrade of your provider.
But perhabs itis better not to risk your guarantee of your provider by
using updates or components of other providers! Because there could be
the possibility that your device is damaged and you should bring it back!
Good luck!
Guys, you get me wrong.I'm not trying anything what I'll find.
1)One of the ROMs that I tried and the one that I left now is a ROM downloaded from orange.co.uk for SPV M2000. So there can't be any incompatibility, don't you think?
2)I have 2 sim cards,both from Orange,I was using both of them before in my M2000 which is sold only through Orange so there can't be any simlock problem,don't you think?
3)I used only that orange ROM, original and the I-Mate one.None of them were working good,always NO SERVICE.
I bought the phone second hand,with box,all accessories etc. But I don't have a receipt :? And of course have lost the guy's number.That's why I want to try everything before going to the service.
I think this phone is network blocked, probably been reported damaged or stolen, once the insurance or replacement is issued a block is put on the imei of the phone that was subject to claim.
Related
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
Dear friendly XDA-Developer,
Three days back, I tried to upgrade my ASIA IIs radio from 1.02 to 1.12. It all went smoothly, but however, my IIs had been without signal and all it says is No Service. I've tried to search through the forums, but to no avail. Kindly please help... I'm at my wits end.
Thank you all!!!
Not sure were or what files you used, if they were type I or II, so I would just sugesst that you Reflash using the files of wiki.
Hi, thanks! I practically tried all the other radio roms for BA thats available on the ftp://xda-developers, but all give same results... Is it something to do with the radio rom or my phone?
You can't try all roms of the download site for they wont work unless you know what you are doing, (correct rom type ect).
Just make your life easy and go over wiki, download, read and install, its worked for many before you.
Read below this
Dear MDAIIIUser,
Like what you've said, I've read through the wiki BA guide, over and over again. I've followed throught the tutorial carefully and still, it didn't solve my problem.
I've some queries here:-
Firstly, if I use an incompatible radio version, would it affect my XDA IIs? I mean, I've successfully upgraded my CE Rom to 1.40 WWE previously and it worked flawless with cooked 1.40 Ext Rom, however, the moment I upgraded my radio rom, my phone feature cannot be utilised. It just says No Service. I've seen on the forum Asian users using Qtec 1.08 radio rom.
Secondly, my understanding on the Oper and WWE is that by setting them correctly with XDA3tools, I can then upgrade them to my XDA without facing any country code errors or such. But would it affect my XDA functionality?
Lastly, can you make any recommendations on which is the most appropriate CE/Radio ROM version I should use for my XDA IIs based on WWE & O2ASI001?
THanks a millions! Believe me, I've really tried very hard to get my IIs to work and have throughly read through the guide, but to no avail...
I recommend that you just download a FULL, fresh, 1.40 Shipped EXE (I recommend the I-Mate one) and upgrade with it.
Use the first method described here to upgrade.
Dear TheLastOne,
I'll try that now! I'll post the results after that.
Thanks a millions!
I've successfully flashed my XDA IIs with I-Mate shipped exe. All went smoothly, but the same problem persist. No service. I guess I can pronounce my IIs official dead... Sob Sob
khngaroo
Could it be that your device is sim locked or that your sim card is no good?
Dear MDAIIIUser,
I believe that my SIM is not locked as I can make calls using the same SIM with another phone. When I insert my SIM card into my XDA, there wasn't any prompt or indication of my device being locked... Is there another way to verify that?
Thanks!
khngaroo said:
I've successfully flashed my XDA IIs with I-Mate shipped exe. All went smoothly, but the same problem persist. No service. I guess I can pronounce my IIs official dead... Sob Sob
Click to expand...
Click to collapse
Hi KHNGAROO... I am not an expers as TLO and MDAUser..but you can give a try downloading the 1.10 radio and downgrading your 1.40 istallation thet contains 1.12 radio to 1.10... I experienced a lot of problems on my device ( low signal or no signal) with the 1.40+1.12 radio combination..and I solved with hios trick..Dont know if can work for you..but maybe you can try..byez
khngaroo
The fact that you have no service would or could indercate that it is beining rejected by your network operator.
Alas, I have no Idea what message you get when a BA is locked to a sim.
(as in the provider has SIM locked your device so that you can only use it with that sim on his network).
The fact that you can use your sim in a different phone proves that the sim is not faulty however that does not verify if the Phone is sim locked.
Thus can you insert a sim from another device that you know that works into your BA and use it.
I have no idea what you had on the phone before you upgraded it nor if it worked, nor if you have also changed your sim so its just a bit hard to work out your probem.
At the moment it could be a locked device or a faulty instaltion of the radio rom.
You might have to go back to your Shipped version to verify if the device still works.
Then upgrade the OS only and check again
Then cook the Extromn to make sure you are not downgrading anything with the new 1.40 OS
Then upgrade the radio to a higher version 1.10 to verify if it works
The upgrade to 1.12 to prove or disprove vicer's very good suggestion.
Have fun
Be careful with the files that you use as you can't use Type I upgrade files to upgrade a Type II rom. Thus you will need to always download the files based on wiki and not reuse the old ones.
Dear MDAIIIUser,
I've flashed my original shipped asian rom back to my device. Got the SD bootable from my pal holding the same phone. Didn't work, still says No Service. I guess either my device is locked or the hardware is screwed.
Is there anything I can do to unlock my SIM on my XDA, should it be my XDA being locked. Or do I really have to bring it down to the service center to get the whole thing fixed?
Thanks a millions for all your help... Appreciated...
You still have not asnswerd the question of the sim. So I still dont know if it is the original sim or if you are using another on on a locked device.
So based on what I do know:
If you flashed the original Rom and have the correct sim and it does not work then your device needs to be sent back to the shop (which will be no problem as you have the original rom in it).
Wiki has a how to unlock (but like I said I dont know if that is your problem)
To all whom had helped me along the way (esp. MDAIIIUser & TheLastOne & vicer)
Brought my XDA IIs to Accord Dist and got it fixed. Now its back. I was told by the customer service operator that they had replaced the whole mainboard altogether. They didn't tell me what was the exact problem. Guess it was the hardware all along. But I was wondering, how on earth can flashing a ROM cause so much damage?
Therefore, here is a warning to those who wish to flash their XDAs, please do so only f you know what exactly you are doing. Please read wiki carefully before you try anything, or you might end up just like me, hee...
Well glad you solved your problem. There are a lot and I mean a lot of people that have been able to falsh thier device via this forum. But as you said you need to read and understand what you are doing.
So what rom do you have now and are you going to keep it?
(Not sure based on your sig)
Dear MDAIIIUser,
Weel, I've upgraded my CE rom to 1.40. However, I've decided to maintain my radio rom as it is (1.02), its kinda like once bitten twice shy. Quite sceptical that my IIs might end up in heaps again, lol.
Thanks again for all your help and concern.
khngaroo, I'm glad all your problems have been fixed. If it is indeed a hardware problem, then you should not hesitate to upgrade your rom.
(Besides, if the problem returns, you know they'll fix it )
TheLastOne said:
khngaroo, I'm glad all your problems have been fixed. If it is indeed a hardware problem, then you should not hesitate to upgrade your rom.
(Besides, if the problem returns, you know they'll fix it )
Click to expand...
Click to collapse
Dear TheLastOne,
I took your word for it and gave it another shot! Followed all the instructions found at WIKI and presto, it worked and now my IIs is running on 1.40 CE and 1.12 Radio.
Many, many, thanks to all of you who had helped along the way!
khngaroo
Great, Happy for you.
The 1.40 rom has a few issues that can be found on the wiki Upgrade page that you need to be aware of.
I recently attempted to update the ROM in my Cingular 8125. The process stopped at 95% and I received an "Internal Error". Now, when I turn on the phone, it gets as far as the color RUU screen, and nothing else.
How can I find out if I can repair this situation myself or if I need to take it back to Cingular.
Hopefully you'll give Cingular a little more info regarding this than you gave us.
My psychic advisor is STILL on vacation so I can be of very little help to you, sorry!
What ROM were you running before and what ROM were you trying to flash it with? Did you CID unlock before you flashed?
Sorry - When I posted the 1st message, I was in a hurry...
I am not sure what ROM version was on the device before I attempted to update (I know, I should have paid attention, but I was not). The phone was new from Cingular and I had not done anything else to it besides load a couple of apps (Skype & Agile).
I attempted to run the file RUU_Wizard_225111_22511102_022511_CWS_WWE_Ship.exe that I downloaded from the HTC site. The update go to 95% and I received the error "ERROR [326]: INVALID COMMAND" - This NBF file cannot be used for your PDA Phone. Please check your NBF file." (I have attached a screenshot of the error to this post).
I am not sure what to do at this point.
Thanks,
Chris
Some folks at the Cingular forum are having the same issue with no solution offered.
I'd suggest putting the device into bootloader mode (Holding Record and Camera buttons while soft reseting) and then reflashing. Make sure not to launch any programs while flashing. I also don't touch the device at all as I've noticed the USB connection might slightly disconnect.
Good luck and let us know what happens.
I just tried reloading from the bootloader screen - no luck. Exact same error at 95%. Would it work to try to reload an original earlier ROM? If so, how would I go about trying that?
Chris
I had this same problem.....I went to the cingular site after having the problem. Before installing I stopped all applications then soft reset.
THen after it boots up install the file from cingular. It worked from their site. Not sure what changed but I am not having any problems now with the new ROM.
I had this same problem.....I went to the cingular site after having the problem. Before installing I stopped all applications then soft reset.
THen after it boots up install the file from cingular. It worked from their site. Not sure what changed but I am not having any problems now with the new ROM.
I have re-downloaded the ROM file from the Cingular site (actually it just redirects to the HTC site). Same problem. I cannot get to the point to even shut down any programs because the phone OS does not even load at this point. When I do a soft reset, I get the following (sorry for the blurry image - as you can see my good phone with the good camera is dead...)
I had a similar problem. I posted the fix on another thread and ppl said i was wrong, this wasnt it...but heres what worked for me.
Are you using a usb port on the front of the computer? if so, try pluggin into the ports on the back of your computer. I tried flashing the official rom from cingular a few times using front port and it stopped at the exact same % each time. got the same thing as you, colored bars.
Someone had mentioned to me that front usb ports don't work as well as back ones. give it a try. good luck
from the picture, it looks you have the G4 chip(u can see 2.25 0001)
Thanks to everyone for their input. From the suggestions above, I have tried various USB ports on my laptop and I always get to the same point. I have also called HTC tech support and they are pretty sure I have bricked my phone. I talked to Cingular and they have agreed to replace it. I have also researched the G4 chip issues (looked at the post: http://forum.xda-developers.com/viewtopic.php?t=56408).
Now I have the following question - When I get my new phone (which I will assume will have the G4 chip as well), the Cingular rep told me that it will already have the latest 2.25.0001 ROM on it. What are my options at that point to SIM unlock my phone. Will I be able to? From the post I referenced above, it sounds like I may not be able to with the G4 chip.
Chris
xtreme23 said:
from the picture, it looks you have the G4 chip(u can see 2.25 0001)
Click to expand...
Click to collapse
I second this observation! :shock:
This makes a major difference on wether or not you can even upgrade.
Search for G4 issues.
The .0001 in the IPS/SPL number will tell you which one you have.
The way I understand it is:
2.25 - G3
2.25.0001 - G4
I think this is the proper way to identify it.
slapper said:
Now I have the following question - When I get my new phone (which I will assume will have the G4 chip as well), the Cingular rep told me that it will already have the latest 2.25.0001 ROM on it. What are my options at that point to SIM unlock my phone. Will I be able to? From the post I referenced above, it sounds like I may not be able to with the G4 chip.
Chris
Click to expand...
Click to collapse
Chris, LokiwizMSL ( http://forum.xda-developers.com/viewtopic.php?t=50768 ) can SIM Unlock your device. Be sure to read the instructions.
Well - Now I have a new problem. So far, Cingular is refusing to replace my phone - saying that the ROM upgrade voided the warantee. I am still fighting that, but just in case I loose, is there any way to get my phone fixed once it has been "bricked"?
slapper said:
Well - Now I have a new problem. So far, Cingular is refusing to replace my phone - saying that the ROM upgrade voided the warantee. I am still fighting that, but just in case I loose, is there any way to get my phone fixed once it has been "bricked"?
Click to expand...
Click to collapse
If you installed an unofficial ROM then they are correct. You should never admit that you used a ROM that was not provided by HTC.
There are warnings all over this site about VOIDing your warranty.
Since you used the Official Update they are wrong.
Same problem with official Cingular 8125 ROM
I tried to flash the official Cingular ROM from the HTC site here:
http://www.htcamerica.net/docs/RUU_Wizard_225111_22511102_022511_CWS_WWE_Ship.exe
I got the same error at 95%:
"Error [326]: INVALID COMMAND This NBF file cannot be used for your PDA Phone. Please check your NBF file."
When I reset the phone I get the RGB bootloader screen and nothing else.
My phone is a G4 and was running ROM version 2.25.11.1 WWE before. The reason I tried to apply this ROM is because there was apparently no Extended ROM. None of the customization cabs executed on a hard reset. Also, in Device Information, there was no "ExtROM" listed.
This is the second phone that this has happened on. I thought the first time was just a fluke thing and I had a bad phone. But now I think there is an issue with this ROM.
Anyone have any idea what is going on here with this ROM? Does the fact that there was no Extended ROM have anything to do with this ROM not flashing properly?
Is there anything else to try or do I need to try to return the phone (AGAIN)?
how to fix the problem
read this thread carefully. The upgrade problem seems to be occuring on G4 chipped Wizards with the most current IPL/SPL.
http://forum.xda-developers.com/viewtopic.php?t=56088
take the official update. run it, when it finishes extracting look for the extracted NBF file in your
C:\Documents and Settings\yourusernamehere\Local Settings\Temp\the newest directory just made
find the NK.NBF file
extract it using the tutorial in the post above you will be flashing with the official cingular components sans IPL/SPL.
flash it and your are back up and running
I would have posted this earlier but i had to make sure it worked and was repeatable.
I think the problem with the new update is the new IPL/SPL version checking. It seems that if the patcher sees the same version already running it will give you that error at 95%. I've seen it on 3 phones already and I have been able to fix them by doing what i've told you above. You are already in bootloader mode and your phone is ready to accept a new rom anyways. My solution may not be the best for your phone and take no responsibilites but you are already desperate and need a fix. Good Luck!
Thanks for the reply, evilito. Since I hadn't gotten any replies for a few days, I decided to go ahead and try to exchange the phone at the Cingular store. They were baffled that this was the second phone I had returned for the exact same problem, but gave me a new phone anyway. I wish now that I had waited so that I could try evilito's solution to see if it works. As it is now, I am too scared to try any flashing on this new phone after my results with the first two. I would really hate to have to try to return a third phone
Can anyone else verify that there is a problem with the latest Cingular ROM when flashing a G4? Or did I really have two bad phones?
slapper said:
Now I have the following question - When I get my new phone (which I will assume will have the G4 chip as well), the Cingular rep told me that it will already have the latest 2.25.0001 ROM on it. What are my options at that point to SIM unlock my phone. Will I be able to? From the post I referenced above, it sounds like I may not be able to with the G4 chip.
Chris
Click to expand...
Click to collapse
Thats good to know, I thought that when we unlocked it and updated the ROM we lost Warentee Support. Where can you get the official Cingular 2.25 ROM. I am still on 2.17.
Hello Everyone,
I know that is a very noob question, but I don't know anymore what to do.
I recently move to Germany and I bring my wizard (bought in Brazil) with me.
My device is CID and SIM unlocked and its running WM 6.1
The problem is, I never get signal!!
I already try all the available radios (2.19, 2.25, 2.69, 2.71 and etc..) and nothing happen!
someone knows if there anything to do for work?
I appreciate all the help.
Thanks in advanced.
no one? no ideias =/
None of the radios you list are from any of the O2 ROMs in the wiki.
Have you tried an O2 Radio?
-MyHTC- said:
None of the radios you list are from any of the O2 ROMs in the wiki.
Have you tried an O2 Radio?
Click to expand...
Click to collapse
i was not able to find it,
could you please send me a link, or tell me where i can find?
hope that work.
This Radio is from the O2 Xda Minis
And here is link to the ROM
danken schön!
i will try and report!
That is very strange!
i flash the radio and nothing happen.
I start to think that my device is SIM unlock again.
But the most strange is:
-I put a diferent SIM and my phone start normaly look for signal but couldn't find it.
-The Invalid SIM screen for type code don't show anymore
-When i read my device on Wizard service tool its show SIM LOCKED.
-But in Brazil i test other operator SIM a long time ago and works.
Any ideia?????
damed! i cannot find a solution...
anyone? any ideia?
I had the same Problem, I live in Germany and have the XDA mini S too, but it's a Vodafone SIM-Card inside. When I installed WM6 the Phone always got a bad connection to the network, and it took much longer even to connect than with the original GERMAN ROM from O2. I downloaded the original ROM from O2s german Website and flashed it with the tool which was in the downloaded file, I didn't extract it from the installer because my Phone was CID-locked. Then the Phone had very good connection again. Then I CID-unlocked it and flashed the newest release of TNT. I expected bad connection again but NO, the Phone behaves like with the original ROM.
XDA mini S german ROM:
http://www.o2online.de/nw/support/downloads/software/xda/older/xdaminis/index.html
My Phone is a G4, so I used this tool to unlock:
http://forum.xda-developers.com/showthread.php?t=332320
Then I flashed this ROM (Professional Edition):
http://forum.xda-developers.com/showthread.php?t=414518
I used ROMUpdateUtility_Wizard_NoID.zip for that:
http://forum.xda-developers.com/showthread.php?t=291215
Everything seems to be normal again. I described every detail because I am not really sure what the EXACT problem was because there are so many ways to do the same thing, but i don't know if every method REALLY DOES EXACTLY the same thing, if you know what i mean
wow! thats really strange! but i will try it!
i cannot beleave but works!!
thank you!
So my problem is - I put android on my htc tytn II and it worked (well kinda) but anyway I decided to switch back to Windows Mobile...
I installed 1.27.x.x radio , found a Windows Mobile 6 ROM and put (Like in the instructions ) Kaisimg.nbh(renamed from ruu_signed.nbh) and Kaisdiag.nbh to my SD card and then started flashing... It flashed smth,rebooted automatically and started booting android again...
Then I hold again camera button + power+ reset and since then when I put EVERY .nbh file on my sd card and try to flash it it STUCK on "Loading.." If I try to flash it with USB It stays at 0%.
The only exeption is if I try to flash from USB the rom that I tried to flash before from my sd card.. then it starts 0%..1% and reboot the phone...
P.S: Please help me...I think my device is not Broken but I dont know what should I do to fix it...
To flash back to WM from android put your kaiser into bootloader (multi colored screen) Then connect to usb. Download any WM build that is recent (I suggest Phoenix 3 for this, you can flash whatever you want later). After you download it open and run the included RUU that came with it and it will flash it on there.
hmm, I also had experienced the similar problem on my 1st time flashing back to WinMo.
When you are trying to flash via USB cable and the process stopped at 1% I guess there is also a message about "Invalid vender ID" right?
and if the text in your bootloader (tricolor screen) doesn't mention anything about hard such as "3.29.0000" (not "3.29.hard")
then
you've lost your hard SPL that's why you cant flash any .nbh to your phone.
I had managed to solve this problem by flashing stock WM rom for kaiser. The rom also has to be suitable for your phone, I mean if your kaiser is originally from France, then use French kaiser stock rom. Or if you are using AT&T Tilt use kaiser cingular stock rom.
you can find the list of shipped roms for kaiser here :
http://shipped-roms.com/shipped/Kaiser/
If you still have the "invalid vender ID" error message, try another stock ROM.
Thanks man you're my hero! I though I lost my phone.. anyway i bought new one - Nokia 2730 Classic but Ill sell the kaiser...
Thanks Anyway ... you're god!
Have the same problem...
Firstly, I'd like to point that the reason for the hard SPL getting overwritten by an original SPL is NOT HAVING UPDATED HARDSPL to a newer version that prevents accidental overwrite. This is instructed in the previous steps before actually installing Android. That was my mistake (I had HardSPL 1.0 OliPof), and now I can't flash no rom to my Kaiser (which thankfully works quite well in Android).
What happens (please correct me if I'm wrong) is that "KAISDIAG.NBH" is a modified, standalone hardSPL that will flash to the phone the SPL that comes with the "KAISIMG.NBH" you put in your SD card with "KAISDIAG.NBH"). In my case, I used the WinMo 6.1 spanish version 3.29.412.0, which, resulted in my phone being flashed with the original SPL 3.29.
Now, it seems many users have fixed this locating the correct stock rom and flashing it in their Kaisers. But to others, like myself, nothing seems to work. I believe that this is because we not only need a stock rom for our specific Kaiser model, but also it has to be compatible with the SPL that accidentally got installed in the phone. The problem is what if such rom doesn't even exists?
I'm really thankfull for all I learned by reading the forums (and from my mistakes ) and I know I'm in no position to make requests, but here goes what I think could help the users like myself to fix this, if posible:
1) Guide to identify what model of Kaiser we have (maybe it's already there, I just couldn't find it)
2) Complete list (or lists) of stock roms (There are some around, those are easy to find I think, but it doesn't hurt to share different sources)
3) Something like a JumpSPL for Android would be more than awesome...
Thanks in advance to everybody, sorry for my own stupidity . Any idea or help would be much appreciated,
Daniel
hmm, I'm not sure if it has to be compatible with the SPL.
In my case, I was flashing a very old WWE stock rom which has original SPL 1.56.
I also had been very desperate because any stock rom I found seems doesn't work and I even didn't know where originally my kaiser came from because I get it from my uncle. So I tried to flash any WWE stock rom I could found but nothing works. I read from Wikipedia that based on my phone model (Kais100), this model was only sold as AT&T tilt for US. But the problem is my phone is HTC branded, not AT&T tilt. Well, based on this information I also tried to flash some cingular stock rom but the result was just the same.
After contacting HTC Customer care, I know more info about my phone. They told me that based on my phone product ID, my kaiser was originally shipped for US, but unfortunately they can't provide me stock rom for my phone model. So I searched myself but this time I had better objective : to search HTC branded rom but for US.
finally, after days of search. I've found the rom that is suitable for my phone. Its called HTC WWE Brightpoint US which has original SPL 3.29 at the bottom of the list on the website I told you on my previous post.
few weeks ago I also accidentally overwrite my HardSPL again, but this time I did it with the stock ROM which has original SPL 3.29. But this problem also solved by flashing the stock ROM I've found before via USB cable.
So, I guess it has nothing to do with spl version.
Keep tying don't give up.
Update: Step 1 completed! YAY
Using the serial number and some obscure google searching, I came to the conclusion my KAIS130 is australian. Cheers, mate!
I verified this by being able to download stock roms from the australian HTC site with my Kaiser serial number. But at the moment of writing this, have downloaded two roms and no luck yet. 5 minutes remaining for the third one... Wish me luck...
Daniel.
Well... Now what?
Tried all four rom-like thingies I could download on the HTC page, all of them returning error 294...
Now what? try to somehow extract the .nbhs from the exes and and use customRUU.exe? Try to flash from SD card?
Please help... Any ideas... I really want to get rid from that original SPL3.29.0000 It's evil!!! I think it won't never let me flash again.
Thanks,
Daniel
cuartetoraro said:
Tried all four rom-like thingies I could download on the HTC page, all of them returning error 294...
Now what? try to somehow extract the .nbhs from the exes and and use customRUU.exe? Try to flash from SD card?
Please help... Any ideas... I really want to get rid from that original SPL3.29.0000 It's evil!!! I think it won't never let me flash again.
Thanks,
Daniel
Click to expand...
Click to collapse
sorry to hear that..
well, extract the .nbh from exe and flash it via sd card is the method that made me overwrite my hard SPL in the first place.
hmm, did your phone comes with operator brand, such as three or something?
-Rif- said:
sorry to hear that..
hmm, did your phone comes with operator brand, such as three or something?
Click to expand...
Click to collapse
No, it's HTC unbranded. Now, something strange here: the label behind the battery has the serial number: HT830GB06075 and the P/N (guess it's part number) :99HCY194-00, but to the left of the camera, another label with the part number: 36H00563-00M and below says DATE:061107(TB02)/US.
I don't know if that's normal, but it caught my atention because my phone seems to have been dissasembled (little label over screw is teared). Maybe my Kaiser isn't Australian after all...