Related
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.
[SOLVED! See page 4]
I have a Cingular 8125, which I hadn't used for a while (got a Trinity
I am trying to set it up for my wife, so I attempted to unlock it and upgrade to WM6. It is a G3 (it had 2.26). I had upgraded it several times before. but was never able to bring it down to 1.xx in order to unlock it.
So, I started trying to downgrade it, but basically, every time it entered bootloader, it seemed to lose connection and it just timed out on the PC, without ever going to the update bar on the bootloader screen.
I ran IPL_SPL_3.08, and it upgraded fine. But still no go on downgrading.
Finally, I ran Shelltool (bug fixed) and managed to flash to OS 1.5.4.2. But, after the hard reset, it just stays on the blue Cingular screen (showing IPL 3.08; SPL 3.08; GSM 02.47.11; OS 1.5.4.2.)
I have tried flashing again with an original Cingular WWE ROM (RUU_Wizard_225111_22511102_022511_CWS_WWE_Ship_1.exe), with the 1.5.4.2 ROM, even with a WM6 ROM (again, through Shelltool.) I have placed it in a powered cradle, have tried both Shelltool and RUU flashes, both while in the blue Cingular screen, and while in Bootloader mode. I have disconnected and reconnected each time, and rebooted many times (both the Wizard and the PC.) I have hard-reset. I have also tried both with USB selected and unselected in Activesync.
The Shelltool seems to freeze. The official RUU gives "ERROR [296]: UPGRADE ONLY. The NBF file cannot be used for your PDA Phone. Please get another NBF file." Or, alternately, it gives "ERROR [264]: CONNECTION."
Any ideas if this is repairable?
(Or should I cry (or take a hammer to the Wizard:-((
Mine is a 2.25 and it's a G4.. Isnt 2.26 a G4?
I think it was 2.26 (it may have been something like 2.27....), but it definitely didn't have the .000 at the end. I thought that the Wizards without the .000 were G3. Did I screw up?
Madcap180 said:
Mine is a 2.25 and it's a G4.. Isnt 2.26 a G4?
Click to expand...
Click to collapse
2.25.0001 or 2.26.0001 would be a G4
2.25 or 2.26 would be a G3
MacGuy2006 said:
I have a Cingular 8125, which I hadn't used for a while (got a Trinity
I am trying to set it up for my wife, so I attempted to unlock it and upgrade to WM6. It is a G3 (it had 2.26). I had upgraded it several times before. but was never able to bring it down to 1.xx in order to unlock it.
So, I started trying to downgrade it, but basically, every time it entered bootloader, it seemed to lose connection and it just timed out on the PC, without ever going to the update bar on the bootloader screen.
I ran IPL_SPL_3.08, and it upgraded fine. But still no go on downgrading.
Finally, I ran Shelltool (bug fixed) and managed to flash to OS 1.5.4.2. But, after the hard reset, it just stays on the blue Cingular screen (showing IPL 3.08; SPL 3.08; GSM 02.47.11; OS 1.5.4.2.)
I have tried flashing again with an original Cingular WWE ROM (RUU_Wizard_225111_22511102_022511_CWS_WWE_Ship_1.exe), with the 1.5.4.2 ROM, even with a WM6 ROM (again, through Shelltool.) I have placed it in a powered cradle, have tried both Shelltool and RUU flashes, both while in the blue Cingular screen, and while in Bootloader mode. I have disconnected and reconnected each time, and rebooted many times (both the Wizard and the PC.) I have hard-reset. I have also tried both with USB selected and unselected in Activesync.
The Shelltool seems to freeze. The official RUU gives "ERROR [296]: UPGRADE ONLY. The NBF file cannot be used for your PDA Phone. Please get another NBF file." Or, alternately, it gives "ERROR [264]: CONNECTION."
Any ideas if this is repairable?
(Or should I cry (or take a hammer to the Wizard:-((
Click to expand...
Click to collapse
I thought I read somewhere that IPL/SPL 3.08 was a bad convert from a Charmer? If this is true and the Charmer bootloaders are different than the Wizard bootloaders then you may have put yourself in a bind.
The fact that you can still get past bootloader is promising even though the phone doesn't finish booting.
Try flashing from the bootloader (tricolor IPL/SPL screen with USB in the corner)
Thanks. I've been trying to flash in both bootloader or "blue" screen, but no go so far. I just tried the official Cingular .nbf through shelltool: it spent about 30 minutes (in bootloader,) then it stopped responding. It's been doing this forever now.
Any other options left?
MacGuy2006 said:
Thanks. I've been trying to flash in both bootloader or "blue" screen, but no go so far. I just tried the official Cingular .nbf through shelltool: it spent about 30 minutes (in bootloader,) then it stopped responding. It's been doing this forever now.
Any other options left?
Click to expand...
Click to collapse
You CAN'T use shelltool in boot loader mode! it needs the OS and the TRUFFS to read and write to the phone.
Any phone that doesn't go past the boot loader must be fixed with mtty, RUU or SD card...
Thanks for the info. I've been reading about mmty and just downloaded it. But I only have a 4GB card handy (from my Trinity.) I might be able to find my old 2GB one at home.
Edit: Well, this is what I just found: http://forum.xda-developers.com/showthread.php?t=308772&highlight=mtty+wizard
It seems that the IPL_SPL 3.08 might be a real problem. I'll try the card flash, but based on the above thread, I am not holding my breath.
If anyone has a suggestion or a solution, please let me know.
Thanks!
BTW, if the problem is indeed with the IPL_SPL 3.08, then perhaps the suggestion that we upgrade to it (in red) here http://forum.xda-developers.com/showthread.php?t=285435 should be removed, so that we don't get more expensive bricks.
Just to clear up the question about 3.08 IPL/SPL, it isn't an issue at all. It's been tested thoroughly to work well, better than 2.26.
TaurusBullba said:
Just to clear up the question about 3.08 IPL/SPL, it isn't an issue at all. It's been tested thoroughly to work well, better than 2.26.
Click to expand...
Click to collapse
After I unlocked my wizard and before I try any new ROM, I always burn the latest German wizard ROM with 3.08 IPL/SPL "ruu_vario_aku3.3_3822_382120_026911_tmo_de_ger_ship". Then I downgrade the Radio ROM to Cingular 2.25.11. Then I burn my ROM of choice. I've found it works best for me. I've never had a problem with 3.08.
TaurusBullba said:
Just to clear up the question about 3.08 IPL/SPL, it isn't an issue at all. It's been tested thoroughly to work well, better than 2.26.
Click to expand...
Click to collapse
What are the grounds for such a comparison? How to tell that an SPL works better than another? As far as i know the SPL is there to initialise the hardware and to apply security restrictions.
What i'd like to know is if anyone has been successful in downgrading IPL/SPL from 3.xx to 2.xx as itsme once said that there was a security in newer SPL's preventing downgrading (i must look for it...)
cheers
O.K., so maybe it's not 3.08, but something has sure gone bad.
I am trying to use mtty 1.1.42.538, but see only Port 1, Port 2 and USB. When I type in \\.\WSCUSBSH001 I get a message that it cannot open the \\.\WSCUSBSH001 port.
I tried resetting as described in message #7 here http://forum.xda-developers.com/showthread.php?t=264652&highlight=mtty1.42, but nothing happened.
I also tried choosing USB, then typed in r2sd all and again, nothing happened - I just get CMD> again....
So, can anyone think of anything else I can do, or should I just drop it from the 4th floor?
What IPL/SPL values you have at this moment?
mestrini said:
What IPL/SPL values you have at this moment?
Click to expand...
Click to collapse
Both ar 3.08, and I have the feeling that this is why I cannot flash the official Cingular ROM over what I have now. Which makes me wonder: is there an official Wizard ROM file combined with the IPL/SPL 3.08? This may at leas allow me to flash.
MacGuy2006 said:
Both ar 3.08, and I have the feeling that this is why I cannot flash the official Cingular ROM over what I have now. Which makes me wonder: is there an official Wizard ROM file combined with the IPL/SPL 3.08? This may at leas allow me to flash.
Click to expand...
Click to collapse
I had also upgraded my IPL/SPL to 3.08 -- up from the 2.25 on the newest Cingular ROM.
Anytime I've flashed to a WM6 ROM, I've been able to downgrade to the T-Mobile 2.26 ROM -- which changes the IPL/SPL to 2.26 -- with no problems before upgrading to a WM6 ROM. After flashing the WM6, I then go back in and upgrade the IPL/SPL once again to 3.08. It's not failed me yet.
O.K., I've spent the weekend screwing around with this:
If I run any of the original 2.xx ROMs, I get "you need an updated utility" message and then the utility goes to the "Exit" screen. (I am assuming this is because of the 3.08 IPL/SPL.)
mtty tells me I don't have permissions when I tried to load the ROM on a SD card (remember, the 8125 is not SuperCD-ed.). It also does nothing when I type "set 14 0" or "task 28."
But, I found that I can run the XDA Mobile 6 ROM (http://forum.xda-developers.com/showthread.php?t=310954) and it actually starts updating, but when it gets to 99%, the bar on the 8125 turns red and after a while the Update Utility tells me that the Wizard is not connected anymore.
Got very excited when I tried mattk_r's InGeNeTiCs' ROM(http://forum.xda-developers.com/showthread.php?t=311144): it started updating, went all the way to 100%, at which point the bar on the 8125 did turn red, however after a period of time the utility gave me the "Congratulations" message and told me I've successfully upgraded. But then, the 8125 reboots, and unfortunately, it still hangs on the boot screen, and it still gives the OS as 1.5.4.2. Have tried a number of times, always the same:-(
Oh, I tried upgrading the Radio only, and it worked: I was able to upgrade to 02.61.11.
So, does it seem like there is hope, and can anyone think of what else I can do?
MacGuy2006 said:
O.K., I've spent the weekend screwing around with this:
If I run any of the original 2.xx ROMs, I get "you need an updated utility" message and then the utility goes to the "Exit" screen. (I am assuming this is because of the 3.08 IPL/SPL.)
mtty tells me I don't have permissions when I tried to load the ROM on a SD card (remember, the 8125 is not SuperCD-ed.). It also does nothing when I type "set 14 0" or "task 28."
But, I found that I can run the XDA Mobile 6 ROM (http://forum.xda-developers.com/showthread.php?t=310954) and it actually starts updating, but when it gets to 99%, the bar on the 8125 turns red and after a while the Update Utility tells me that the Wizard is not connected anymore.
Got very excited when I tried mattk_r's InGeNeTiCs' ROM(http://forum.xda-developers.com/showthread.php?t=311144): it started updating, went all the way to 100%, at which point the bar on the 8125 did turn red, however after a period of time the utility gave me the "Congratulations" message and told me I've successfully upgraded. But then, the 8125 reboots, and unfortunately, it still hangs on the boot screen, and it still gives the OS as 1.5.4.2. Have tried a number of times, always the same:-(
Oh, I tried upgrading the Radio only, and it worked: I was able to upgrade to 02.61.11.
So, does it seem like there is hope, and can anyone think of what else I can do?
Click to expand...
Click to collapse
If I were you I might be talking to IMEI unlockers. Their process works from bootloader and might be able to get you CID unlocked and fix your corrupted CID area, which seems to be your major problem atm. In any case I would contact them and explain your situation and see if they think their software will unlock your phone. If so then you should be good to go once you CID is "uncorrupted" and unlocked.
one question: can You HARD RESET your device?
Do you have "format failed" message?
if so, you have 50/50 per cent for resurrection.
3.08 is not direct problem here anyway..., version is not exactly matter of problem...
(imei? now? lol)...
Thanks!
Yes, I can hard-reset fine and it claims to reformat fine.
Tx for the suggestion - I will contact IMEI (they unlocked my Trinity before the free unlockers were available
So, what's it mean when you run GetDeviceData.Exe and all you get in your ../windows/devicedata.txt file is "PH20B" ?
Strange, huh? I've tried it a couple of times. Always the same... Nothing but "PH20B". I'm also having the "No GSM" in the boot screen problem, and can't upgrade (well, load AT ALL!) my radio stack. In my device info screen the OS and Extended info are right, but Protocal and Radio are both blank now. This has all happened after trying to do a ROM upgrade tonight.
1. What (exactly) device you own? What was DeviceData BEFORE first upgrade?
2. What ROM you had, and which one you tried to load?
3. How did you do that (what procedure)? Have you omitted any steps?
Lets say you really own PH20B (Blueangel) then if the radio is inactive the devicedata.txt will not output the info from it. Reflash radio only
Also this may happen if you have flashed PH20A (Harrier) and you flashed WM5, go back to WM2003 and all will work fine
jakubd said:
1. What (exactly) device you own? What was DeviceData BEFORE first upgrade?
2. What ROM you had, and which one you tried to load?
3. How did you do that (what procedure)? Have you omitted any steps?
Click to expand...
Click to collapse
Answers:
1: It is a HTC BlueAngel. It's one of those with just "PocketPC" on the front. No cell provider branding. I bought it off ebay last year. Don't know what the file showed before. Never had a problem, so I never looked.
2: Was running a I-Mate ROM since I bought it. But the radio was really old. The radio version was like .9xx . Don't remember exactly what. SHould have written it down. But it was less than 1.00, I know that for sure. I was upgrading to the Siemens 1.33 ROM with the 1.15 radio added on.
3: Used MaUpgradUt_NoID. Never been able to use BaUpgradeUt. It's always given a country ID error, but Ma..NoID has always worked before.
xplode said:
Lets say you really own PH20B (Blueangel) then if the radio is inactive the devicedata.txt will not output the info from it. Reflash radio only
Also this may happen if you have flashed PH20A (Harrier) and you flashed WM5, go back to WM2003 and all will work fine
Click to expand...
Click to collapse
Yes. It is a blue angel for sure. See my reply above.
It's always been WM2003, and all I get when I try to flash ANY radio rom version to it now is a country ID error.
flash with noid app
maupgradeut_noid.exe
Yep. Already tried that. In fact, that's the ONLY way I've been able to do any upgrades at all since I bought the phone. Never have found a ROM that would work with BAupgradeUt.exe. Strange thing is, I can load the OS and EXT ROM's no problem using Ma..NoID.exe... Just not the Radio ROM. Even using NoID when I try to load a Radio ROM, it dies with a country code error. I believe the error is N-N-50-50-50 if that means anything to anyone. Any more ideas? I've tried all the obvious things I could think of. I wonder if maybe I could use a null data field in editfix.bat? That is, instead of using real data values from devicedata.txt like you normally would, replace the "???" in the .bat file with " ". Anyone know if that's even possible? Or should I just try taking it up to WM5, then back to 2003?
Thanks for all the thought and effort so far folks.
Have a G3 unlocked Wizard (Cingular 8125).
Have been running different ROMS to see which one I like.
Recently stayed with NBD 8.0 for a while.
Last week battery went to heck, apparantly during a reflashing.
Probably due to the battery, I could never reflash and would always get
stuck in bootscreen @ 98%, no matter how long I charged the battery
(using stock charger and battery in-phone.)
I purchased a cradle battery charger and a new battery from ebay (which works great BTW).
Now I can flash... I think.
I managed to flash in "Xda_MiniS_LaunchROM_v154102" and my phone works.
I even got caught up on my voicemails. But every time I try to
upgrade to stock Cingular or T-Mobile, the RUU says incorrect ?nk.nbf? file.
(The actual ROM file).........What gives?
This is what comes up upon bootup.
ipl-1.01
spl-1.01
gsm-1.12.10.0
os-1.5.4.2
I'm using an XP machine with ActiveSync 4.5. Never had a problem
re-flashing before. I tried looking through the threads without success.
Any help would be appreciated.
i was going to say try that xda mini rom. thats what fixed my problem , then i was able to flash a tmobile rom. then tne wm6.
http://forum.xda-developers.com/showthread.php?t=298613 I used this thread. try the tmobile rom on g3.7
joihan777 said:
Have a G3 unlocked Wizard (Cingular 8125).
Have been running different ROMS to see which one I like.
Recently stayed with NBD 8.0 for a while.
Last week battery went to heck, apparantly during a reflashing.
Probably due to the battery, I could never reflash and would always get
stuck in bootscreen @ 98%, no matter how long I charged the battery
(using stock charger and battery in-phone.)
I purchased a cradle battery charger and a new battery from ebay (which works great BTW).
Now I can flash... I think.
I managed to flash in "Xda_MiniS_LaunchROM_v154102" and my phone works.
I even got caught up on my voicemails. But every time I try to
upgrade to stock Cingular or T-Mobile, the RUU says incorrect ?nk.nbf? file.
(The actual ROM file).........What gives?
This is what comes up upon bootup.
ipl-1.01
spl-1.01
gsm-1.12.10.0
os-1.5.4.2
I'm using an XP machine with ActiveSync 4.5. Never had a problem
re-flashing before. I tried looking through the threads without success.
Any help would be appreciated.
Click to expand...
Click to collapse
It may be the RUU you are using. Try flashing the Cingular rom using one of the RUUs I attached below. I personally have never had this problem before so this is my best suggestion.
Is it possible that somehow it got re-locked????
Also, evrytime I try to upgrade out of 1.05 ROM the RUU process stops at 85% and then says nk.nbf not for this PDA.
No, except you didn't have a successful CID-unlock (e.g. Unlock when IPL and SPL is 2.xx, and flashed to WM6 using ShellTool, then you think that you have been unlocked, which is actually not)
Update: Even though I haven't been able to load the official Cingular ROM or
the T-Mobile 2.26 ROM, I HAVE been successful in loading NBD 8.0.
I DON'T GET IT!!!!! Why would NBD load but official carrier ROMs get stuck at 85%?
Although my G3 is is currently working again, I'll still do some more experimenting.
I don't know what an extended ROM is, but I wonder if mine was corrupted
during the power failure when attempting to downgrade last week from NBD to Cingular?
I'll post my results hoping this will help others.
Edit: An hour later- I tried another official WM5 ROM form HTC, no dice. Froze @ 85%
just like the other WM5 Official ROMs. On a hunch, I tried to install the newest NBD 9.2.
IT WORKED! WHY can I install NBD ROMS but not Official WM5 ROMs?
Now the first splash screen is the *dated* green stepped graduated green from 1.05. The current info:
IPL- 2.25
SPL- 2.25
GSM- 02.25.11
OS- 6.0.0.0
Itai! This is tough!
EDIT: OK, it's now 4am and I'm seeing double....
Tried Wizard Service Tool, a very efficient program by mestrini.
Apparantly, my extended ROM was hidden. So the WST unhid it. Now we'll see what this does.
According to WST, there was no pagepool found in WM6 or WM5 location.
Could this be why WM5 updates didn't work?
4:22am, even cat gave up on me...
Sorry if I missed something here, but if you have a CID Unlocked phone and you downgrade back to a 1.xx IPL/SPL, then you will be CID Locked again when you upgrade. Anytime you downgrade to 1.xx you have to redo the CID Unlock process while you are down there before going back to IPL/SPL 2.xx or higher.
So redo going back to the Button rom, do the lokiwiz unlock, make sure both IPL/SPL are 1.xx (so you may have to flash button a couple of times) then upgrade to Cingular, T-Mo or whatever official 2.xx rom.
joihan777 said:
According to WST, there was no pagepool found in WM6 or WM5 location.
Could this be why WM5 updates didn't work?
4:22am, even cat gave up on me...
Click to expand...
Click to collapse
Page Pool is set in ROM image, not hard-coded in hardware.
mfrazzz said:
Sorry if I missed something here, but if you have a CID Unlocked phone and you downgrade back to a 1.xx IPL/SPL, then you will be CID Locked again when you upgrade. Anytime you downgrade to 1.xx you have to redo the CID Unlock process while you are down there before going back to IPL/SPL 2.xx or higher.
So redo going back to the Button rom, do the lokiwiz unlock, make sure both IPL/SPL are 1.xx (so you may have to flash button a couple of times) then upgrade to Cingular, T-Mo or whatever official 2.xx rom.
Click to expand...
Click to collapse
Didn't work. I'm certain I'm unlocked, both by lokiwiz program saying so and
Wizard Service Tool saying so. After the unlock I was successfully able to
load NBD 8.0 & NBD 9.2 ROMs, but not the official T-Mo/Cingular WM5 ROMs.
WST found the pagepool completely missing in both WM5 & WM6 sectors.
The extended ROM was also hidden. Both of those items have been corrected
so later today I'll redo the entire process just to make sure all is well.
starkwong said:
Page Pool is set in ROM image, not hard-coded in hardware.
Click to expand...
Click to collapse
Thanks. More clues to this puzzle!
Try flashing the empty extented rom. Most new roms don't have extended roms, so if your extended rom is corrupt it may be keeping wm5 to load. Which explains why NBD roms work.
goofeyass said:
Try flashing the empty extented rom. Most new roms don't have extended roms, so if your extended rom is corrupt it may be keeping wm5 to load. Which explains why NBD roms work.
Click to expand...
Click to collapse
Thanks, I just now tried this approach. I used mestrini's Wizard Service Tool to 'format' the extended rom. As of this moment I've just downgraded to Button 1.05 ROM and going to use lokiwiz's unlocker.
There is a rom out that will flash an empty extended rom without changing anything else.
http://forum.xda-developers.com/attachment.php?attachmentid=42076&d=1182515673
I have formatted the extended rom.
Then I tried to redo the Button-->Unlock-->T-Mo 2.26.
Still process stops at 85% when installing T-Mo ROM!!!
Also, the splash screen doesn't seem to be working?
goofeyass said:
There is a rom out that will flash an empty extended rom without changing anything else.
http://forum.xda-developers.com/attachment.php?attachmentid=42076&d=1182515673
Click to expand...
Click to collapse
How long are you waiting when its at 85%. I've had them stay at 85 % for over 5 minutes before.
I would recommend flashing ---->http://forum.xda-developers.com/attachment.php?attachmentid=42076&d=1182515673
???
in my opinion it is a waste of time to downgrade to flash a new/original rom...i've flashed about 100 or so roms since late 2005, multiple devices, jumping from carrier rom to latest wm5/6 builds..never had an error.
Do what you like of course, im just saying save 10 mins and flash straight to whatever you're wanting to try. goodluck and happy flashing
BTW like I said before... for those of you with dual/quad core procs, try putting the romupdateutility.exe on real-time priority and check it, I flash in roms in less than 3 mins, everytime, no errors
goofeyass said:
How long are you waiting when its at 85%. I've had them stay at 85 % for over 5 minutes before.
I would recommend flashing ---->http://forum.xda-developers.com/attachment.php?attachmentid=42076&d=1182515673
Click to expand...
Click to collapse
Is there a correct method for using those files? I installed them to the Wizard's Windows/ Startup directory & rebooted. They sorta ran, but when I checked the extended ROM with WST, it reported the extended ROM was empty =)
Now I'll go around again Button 1.04-->Lokiwiz Unlock-->T-Mo 2.26
goofeyass said:
How long are you waiting when its at 85%. I've had them stay at 85 % for over 5 minutes before.
Click to expand...
Click to collapse
Good point... HOW long are you waiting. If you are doing an RUU, you should just let it run. Official roms will "Hang" at 85%, and I've had them hang for over 5mins before also, but they always finish.
As someone used to post, you should start the RUu, then head to the kitchen, go get coffee, a snack, whatever. Just ignore the flashing process until its done...
mfrazzz said:
As someone used to post, you should start the RUu, then head to the kitchen, go get coffee, a snack, whatever. Just ignore the flashing process until its done...
Click to expand...
Click to collapse
Very well said. Lol. It's true though. If you just ignore it, it will seem to go faster. I noticed the same thing too. If you are flashing an official rom, it will almost always stop at 85%, sometimes for a long time... Just let it go and it should eventually finish.
Hi everyone.. First post and I think this is a great site. I've managed to flash a wm6 rom to my Orange SPV m700, and although it worked great for a while, I decided to flash my radio rom (initially 1.16.00.00) to 1.50.08.11 not a great idea it would seem, as after a successfull (so it seemed) flash and a reboot, the I now appear to be missing both a radio rom and a gps rom!?!
Can anyone help? I've tried flashing back to a 'orangeuk' WM5 backup (created by someone on this this forum) and I'm having no luck what so ever. The downgrade to WM5 stalls at 82%. My gut suspicion is that it's failing at the radio rom, and I can (sort of) prove this when trying to flash the radio rom - it fails at 0%
PLEASE HELP
Update on this.
Downgraded from 1.30 Hard SPL to 1.20, tried flashing Radio Rom, again no joy. Have also attempted upgrade from SD card - again no joy.
Anyone?, Anyone?... Bueller?.. Anyone?
Just to add, there's no Radio/GPS or IMEI number.. I've seen other people with the same problem but no 'real' guide to fixing..
Just tried (on a whim) to downgrade the radio software down to to 1.16.00.00 using the SD card (basically trying to use Pof's unlocker radio rom) but still no joy, using the SD card just get's about 10% of the way along the progress bar and stops..
I'm struggling here folks
k0pp0 said:
Just tried (on a whim) to downgrade the radio software down to to 1.16.00.00 using the SD card (basically trying to use Pof's unlocker radio rom) but still no joy, using the SD card just get's about 10% of the way along the progress bar and stops..
I'm struggling here folks
Click to expand...
Click to collapse
Try Des' Crash Proof SPL in my signature.
i have same problem .... can't find a solution if you manage to fix it please post
Never did get this working, ended up having to get a replacement phone.. Just debating trying it again, as my current (white) Orange SPV M700 hangs nearly every saturday (bizarre).