Hello folks,
Today I flashed with the ROM in thread 'T-Mobile USA 2.17 ROM (Custom)'. After it came up, I ran through the screen align and wizard. When it was all done installing extended rom etc it restarted on its own. After booting back up, everthing was really slow and there was no cell signal. The battery icon had an ! mark on it and when clicked, it says unknown battery. At this point everything keeps freezing and genrally not working including no activesync connection possible. I restarted into the bootloader and tried to flash again. It completed, but now I just get the tmobile boot screen, and eventually it restarts again, never completing the boot. This is when I notice that it doesnt seem to have a radio rom (GSM) version listed, but rather a gap where it should be. I ended up pulling the battery out and trying to get back into the boot loader again, and now I cant get it to power on in any way.
I guess that is enough said. The only other thing to note is that everything was working fine prior to the attempted update, I was merely hoping to get a performance boost, as I was using the original rom.
Any thoughts?
Thanks!
B. Ramsey
Fixed!
No other ROM would install, but in reading back through threads, I found a link to RUU_Prodigy_1081002_108_10910_TMO_US.exe. After installing this, I had my GSM rom back. Then everything worked. I think the not powering on issue had to do with the fact that it sat in the bootloader screen for several hours at one point. Since there was no standby, the battery was wasted. I am attempting to reflash it now to 2.17, we'll see.
No dice
After installing the 2.17 ROM, no more GSM, and same problems. I reflashed back to the previous and it works again..
Re: Fixed!
pterodyne said:
No other ROM would install, but in reading back through threads, I found a link to RUU_Prodigy_1081002_108_10910_TMO_US.exe. After installing this, I had my GSM rom back. Then everything worked. I think the not powering on issue had to do with the fact that it sat in the bootloader screen for several hours at one point. Since there was no standby, the battery was wasted. I am attempting to reflash it now to 2.17, we'll see.
Click to expand...
Click to collapse
THANK YOU SO MUCH for posting this! I also had a brick because of the same setup - trying to use the custom TMOBILE ROM. I had the same symptoms you did - basically non-responsive and no radio stack and no USB connection. I was not getting anywhere with any other ROM. Now, at least I have a working device.
Still no AKU2 though
Let me know if you manage to get an AKU2 ROM on your device!
That's worrisome. Do you know if the CID unlock was successful? (I think it's scripted into that custom upgrader)
If you're feeling adventurous, you could try intalling the custom 2.17 Cingular upgrader I made (it's on the FTP server). If that's successful, then the problem is with the T-MO upgrader. Based on all the folks having success with that T-MO upgrader though, I imagine the only issue might be a corrupt download. If the Cingular upgrader results in the same behavior, then the problem is either with the CID lock or some odd hardware problem.
I'm truly perplexed by the issue you're having..sure wish I knew how to help ya.
Thanks for the replies. My phone was already unlocked as it was purchased that way. I actually did get custom 2.17 tmo Rom to work, I just hadnt posted here yet. After flashing to the older rom, I flashed to the 2.16 Rom on clubimate.com. Then I had a working 2.16 with GSM. I figured what the hey and went ahead and tried the custom 2.17 Rom again. All is great, and FAST. I wish I could remember what custom Rom I was using before I think it must be the culprit. I cant remember, but it did have the extended rom free and open, total commander, and an unlocker.
Thanks
pterodyne said:
Thanks for the replies. My phone was already unlocked as it was purchased that way. I actually did get custom 2.17 tmo Rom to work, I just hadnt posted here yet. After flashing to the older rom, I flashed to the 2.16 Rom on clubimate.com. Then I had a working 2.16 with GSM. I figured what the hey and went ahead and tried the custom 2.17 Rom again. All is great, and FAST. I wish I could remember what custom Rom I was using before I think it must be the culprit. I cant remember, but it did have the extended rom free and open, total commander, and an unlocker.
Thanks
Click to expand...
Click to collapse
My device is a QTEK 9100. I was upgrading from the ROM on my device when I got it:
ROM 1.1.7.5 9/22/2005
Radio: 01.01.10
Protocol: 4.0.13.16
ExtROM: 1.1.7.105
My carrier is TMobile, so I figured the TMobile custom rom that was built off of the latest QTEK would be a good bet for me - but instead I ended up with no Radio.
I have the IMATE ROM you refer to - maybe I'll try to go to that as an interim step to get to the QTEK ROM I really want, since you had success with that method.
What I don't understand is why the Vanilla QTEK 2.17 (which is what I tried after the TMO Custom 2.17) gave me problems. I don't recall the exact error message, but basically it said it couldn't use that ROM on my device.
pterodyne said:
Thanks for the replies. My phone was already unlocked as it was purchased that way. I actually did get custom 2.17 tmo Rom to work, I just hadnt posted here yet. After flashing to the older rom, I flashed to the 2.16 Rom on clubimate.com. Then I had a working 2.16 with GSM. I figured what the hey and went ahead and tried the custom 2.17 Rom again. All is great, and FAST. I wish I could remember what custom Rom I was using before I think it must be the culprit. I cant remember, but it did have the extended rom free and open, total commander, and an unlocker.
Thanks
Click to expand...
Click to collapse
When you say it was already unlocked, don't you mean SIM unlocked? It would be unusual to buy a phone that is already CID unlocked.
I bought the unbranded k-jam from Simoncells.com. All I did was put my tmobile sim card in it and it worked. I guess I dont know the difference between SIM and CID unlocking.
Well theb that's where you went wrong, sim unlock refers to ur phone being able to use any world sim card...cid unlock refers to country Identification...if ur fone is not cid unlocked then wen u install foreign roms it will bugg up ur fone...dats wat happened to u and that other fellow pterodyne...I sim and cid unlocked my fone. ran the tmo 2.17 custom rom without a problem....plz do ur research on upgrading roms b4 u bash them...most factory fones don't come cid unlocked so I'd b surprised if urs did (tho it prolly came sim unlocked)...
Related
Okay, I have searched the forums, to no avail. I also no longer have the .bin files generated when I first ran lokiwiz, they were accidentally deleted by another individual who rebuilt a box before I had a chance to pull them off.
So basically, I am screwed, every command I try with lokiwiz or awizard results in the following errors
ps, I am trying to restore the original 8125 image, I have a functioning device, but I want to restore it.
...
CopyFileToTFFS(cidunlocked.bin:0, 0, 00010000)
ERROR: ITWriteDisk - An internal error occurred.
result=80072746
[19:15:05.84] Your phone is now CID unlocked....
Store the generated 'lock_backup.bin' file in a safe place. It can help to resto
re your device if anything goes wrong.
* Press [Enter] to continue
I'm having the same issue on a unit with the K-JAM_WWE_216901_2169101_020710_ship ROM....
I'm having the same issue on a unit with the K-JAM_WWE_216901_2169101_020710_ship ROM too.
lot's of people have that problem, whit that specific rom :S
me too, but there does not seem to be a solution yet...
for te topicstarter: flas another rom on your device and lokiwizard will work again
lokiwizard refuses to work, even after flashing the latest imate rom to it (although I am using the imate rom installer application), I guess I could try the ruu tool ..... ??
flash back to t-mobile rom, unlock it an flash back again to imate
I have no problems flashing to the imate rom, thats what I am running at the moment. Using the imate rom, I cannot run awizard or lokiwizard.
Johannus said:
flash back to t-mobile rom, unlock it an flash back again to imate
Click to expand...
Click to collapse
Is that possible?
From what I gathered, if you flash it to the iMate rom, the Extended rom portion becomes locked to the iMate Extended rom. You can't even reflash it back. Until someone comes out with a version of the full iMate rom with an unlocked Extended, or breaks up the iMate rom into GSM, OS, and Extended and you do it manually, I think it is impossible.
Or I could be totally wrong.
fuzzycuffs said:
I think it is impossible.
Or I could be totally wrong.
Click to expand...
Click to collapse
i think you are... cause i did it myself
and for the topicstarer: i know you cant use awizard nor lokiwiz, but if you flash your original T-mobile rom back, just like i did, then use awizard or lokiwiz to unlock the SIM and the CID. and after that flash the imate rom on your device again, your problem will also be solved!
Johannus said:
fuzzycuffs said:
I think it is impossible.
Or I could be totally wrong.
Click to expand...
Click to collapse
i think you are... cause i did it myself
and for the topicstarer: i know you cant use awizard nor lokiwiz, but if you flash your original T-mobile rom back, just like i did, then use awizard or lokiwiz to unlock the SIM and the CID. and after that flash the imate rom on your device again, your problem will also be solved!
Click to expand...
Click to collapse
Alright, then answer me this:
Can you take the iMate full rom, do that flash, and just then flash the TMO extended rom on top of that, so upon a hard reset it'll have the iMate GSM and OS roms, but then go through the stock TMO Extended rom updates (one of which will kill wifi)?
If so, that answers my question of going back to "bone stock." That's my concern with flashing to the iMate rom: 1) having a locked extended rom that I may or may not be able to revert back from, and 2) being able to go back to how the phone looked coming out of the box.
fuzzycuffs said:
Johannus said:
fuzzycuffs said:
I think it is impossible.
Or I could be totally wrong.
Click to expand...
Click to collapse
i think you are... cause i did it myself
and for the topicstarer: i know you cant use awizard nor lokiwiz, but if you flash your original T-mobile rom back, just like i did, then use awizard or lokiwiz to unlock the SIM and the CID. and after that flash the imate rom on your device again, your problem will also be solved!
Click to expand...
Click to collapse
Alright, then answer me this:
Can you take the iMate full rom, do that flash, and just then flash the TMO extended rom on top of that, so upon a hard reset it'll have the iMate GSM and OS roms, but then go through the stock TMO Extended rom updates (one of which will kill wifi)?
Click to expand...
Click to collapse
No, but you (1) don't have to and (2) DON'T WANT TO, as some of the T-Mobile CABs will kill things in the new release AND they're inferior anyway (the connection button is one of them!)
In fact, unless you want the OZIm client and the "SMS email triggers" you need to load only TWO of the T-Mo US CABs on top of the Imate ROM (by hand) to get full functionality. No problems with this approach at all (of course you don't get the T-Mo pukie home screen this way, but I don't want it anyway!)
I posted in one of the other threads where you asked this how to accomplish it.
If so, that answers my question of going back to "bone stock." That's my concern with flashing to the iMate rom: 1) having a locked extended rom that I may or may not be able to revert back from, and 2) being able to go back to how the phone looked coming out of the box.
Click to expand...
Click to collapse
Going back to how the phone looked out of the box is easy if you have an SD image of the original T-Mobile ROM and an SD card. No problem with that at all - as I've noted here repeatedly I have TESTED this and it works fine.
So let me get this straight, to get past the locked extended rom imate creates, I need to flash to tmobile to be able to flash bac the original cingular rom? Ah well, guess I gan stay with the imate rom till cingular releases an official rom release
I have never flashed this phone with any kind of alternate firmware, yet when I go to run the official one from HTC, I get this at 8-% exactly, on 2 diffrent phones:
_______________________________________________________________
ERROR [326]: INVALLID COMMAND
This NBF file cannot be used with for your PDA Phone. Please check you NBF file.
_______________________________________________________________
Then the phone turns into a brick. All it does is show the Tri-Color test looking screen untill try to flash again...
Any suggestions?
What phone do you have?
Whoops....
Sorry... I posted this in the wiz forum and didnt even think to put my phone model....
Cingular 8125
Thank you!
Re: Official Cingular 8125 2.25 Update ---Problem---
pittaman said:
I have never flashed this phone with any kind of alternate firmware, yet when I go to run the official one from HTC, I get this at 8-% exactly, on 2 diffrent phones:
_______________________________________________________________
ERROR [326]: INVALLID COMMAND
This NBF file cannot be used with for your PDA Phone. Please check you NBF file.
_______________________________________________________________
Then the phone turns into a brick. All it does is show the Tri-Color test looking screen untill try to flash again...
Any suggestions?
Click to expand...
Click to collapse
If you are attempting to flash the official ROM on an 8125 and getting this error, there's some bad juju goin on.
Just to be sure, you got the following ROM, correct?
http://www.htcamerica.net/support/software_downloads_8125.htm
I’ve downloaded that so many times my browser is upset at me. There must be a lot of bad JuJu... because It has tanked 2 different phones.....
I’ve taken your 2.3 update, and ran it... It went though... got to 98 and turned red on the phone... finally went to 100% and rebooted... but it was still at 1.8... but at least the phone works again... I really need the push e-mail though... and would prefer to use the official update... or a close derivative..
You should CID unlock first before you apply any ROM found in this forum.
If your phone is virgin, i.e. never been updated to a non official ROM, you will be fine going from 1.8 to this ROM and you would not need to CID unlock. I have gotten an nbf error before, but it was from an attempted downgrade to the stock 1.8 ROM from Summiter's 2.17 release.
Check your OS version and report back.
I know it says you have never upgraded before... If you're still having problems, just take it back to the store, we bricked a phone stuck on the 2.17 ROM and returned it with no problems. Apparently the 8125 does not like animated themes (not my idea, but it did have entertainment value).
Could there be something up with my PC if it bricked 2 seperate phones? WOuld it be possible to fix em with a diffrent PC? and do you think a Cingular store would update the firmware on the phone if it wasnt broken already?
pittaman said:
Could there be something up with my PC if it bricked 2 seperate phones? WOuld it be possible to fix em with a diffrent PC? and do you think a Cingular store would update the firmware on the phone if it wasnt broken already?
Click to expand...
Click to collapse
There's always the possibility of a virus causing issues, but it's exceedingly remote.
If the phone is working you should be able to bring it into any Cingular store and have them do the update for you.
pittaman said:
Could there be something up with my PC if it bricked 2 seperate phones? WOuld it be possible to fix em with a diffrent PC? and do you think a Cingular store would update the firmware on the phone if it wasnt broken already?
Click to expand...
Click to collapse
I concur with gamescan that it might be a virus, or some crappy spyware. I don't think however that you've "bricked" your phones as you WERE able to install sumitter's 2.23 OK. Of course since you didn't SID unlock you didn't get the full upgrade. I disagree with those who insist that you don't need to unlock. Mayhaps you don't need to but I know that sumitter and the other ROM gawds here have always suggested so. If I was you I'd downgrade to the 1.05, unlock, then upgrade. I'd also scan your PC with Spybot, maybe AdAware. Also I'd delete my temp files, in the c:\documents and settings\%username%\local settings\Temp. Also empty your temporary internet files. I've seen large temp folders on PC's create all kinds of grief. Just a suggestion.
Steven
chow
Well... I appriciate all your help thus far.
I called Cingular Yesterday ant they sent out 2 replacement phones for free, and I got them today... With the update already in place, so I dont think I'll be playing with unlocking again LOL... But this information is very helpful, as my Uncle has the same phone and needs the push email more than I do. If his phone gets toasted, Ill be here with the results...
Thank you all very much... this is my new favorite place!!!
Not A virus .... its the phone
Apparantly the newer phones have a new flash chipset G4 which is not compatable with the current crop of cooked roms on this site. I think summiter has one that will work but it didn't work for me. I returned my phone for a replacement hoping to get the g3 chipset but to no avail all the new ones are G4 and are unable to be flashed to the custom roms. also you should be able to sim unlock with no issues but to cid unlock you may need to look elsewhere
Re: Not A virus .... its the phone
alynch75 said:
Apparantly the newer phones have a new flash chipset G4 which is not compatable with the current crop of cooked roms on this site. I think summiter has one that will work but it didn't work for me. I returned my phone for a replacement hoping to get the g3 chipset but to no avail all the new ones are G4 and are unable to be flashed to the custom roms. also you should be able to sim unlock with no issues but to cid unlock you may need to look elsewhere
Click to expand...
Click to collapse
First, the OP was using the OFFICIAL CINGULAR UPDATE not a custom Rom.
Second, He was upgrading from 1.8 which is a 1.x Rom, this means his phone is indeed a G3 variant as the 1.x Roms only have G3 IPL/SPL.
I had this same experience from a virgin HTC 8125....
I had stop all apps running and recharge my battery. Then disable my sleep and screensaver then it worked.
I know there are others experiencing the 28% death wall while trying to flash WM6, but there doent seem to be any specific solutions to this.
I have a Dopod D810 and has already installed 1.30 olipro. Just trying to flash to the official WM6 ANZ Rom. No luck.
Any suggestions guys?
Should just be a very straight forward procedure. Flashing a Dopod with an official Rom.
should be, but it's not... mine is Dopod asia, and stuck at 28% when flashing. Not too sure, but really seemed to me that it was something related to hard-spl. After the 28% error, i reflashed an unofficial rom and tried the official again.
eventually it worked for me.
i guess you don't technically need to manually enter hard-spl first before flashing official ROM.. if anything went wrong i guess you could send it back to them..
safest is to use a modified RUU so it just flashes ROM without IPL + SPL.. i thiiiiiink problem is something to do with SPL
which unofficial rom did u reflash it to? I've been going back and forth with AX3L_OS v3.0.0.2 and the official ANZ dopod rom.
tried about 5 times now. still trying. each time it fails at 28% it's another 10 minutes to flash backto the unofficial rom.
maybe if i try to trce ur steps exactly it might work.
i was flashing to some pdaviet ROM, but i don't think that would make any difference from ax3l's...
have you tried flashing the official ROM with a modified RUU, or you really want the whole package...
If you're just trying to keep everything official i guess you could try to flash the official rom without manually entering bootloader and take your chances. Being that its an official ROM i guess it's safer, or at least covered in warranty..
One question, why don't you try to flash to official WM5 ROM, then to official WM6.. since technically it's supposed to work that way
seriously, i'm not sure why you'd want the official one though.. it's nothing special
Yeah I've tried flashing back to the official WM5 and then WM6, same story.
Tho I havent tried flashing the official WM6 through modified RUU, mainly coz i dont know how to.
Also, In the AX3L version of WM6, there doesnt seem to be a phonepad input method. only keyboard and block recongniser and one other one. Is that coz it's a modified rom, or does WM6 not have the phone pad input. if that's the case i can forget about flashing to WM6 all together.
can't remember if official wm6 has phonepad, but you can just install a cab for it, so it's not a big deal.
look on my site for a link to modified RUU official ROM... instructions are here
i had a lot of problems being stuck at 28%
what eventually i got it to flash to the aus rom was i used SPL 1.20 then it seemed to flash fine.
for some reason my phone doesnt like any other version of SPL besides the one on the latest aus rom either, i flashed to a cooked rom and couldnt flash back until i had put spl 1.20 back in then flashed back to the aus rom.
I have the same problem with 28% stucking
I try to reflash but I still have the same
do you have hard-spl? if so, which version? If you do, flash back a cooked ROM..
if not, you need to try to flash official ROM..
if neither is working, use splxploit. I think all links you need are in this thread already
I have a same problem.
I was upgraded from WM5 to Hong Kong Official WM6 chinese ROM, then I want to change to Official English ROM, I did the Hard-SPL 1.3 and get the SuperCID, but when upgrading the WM6 English officeial ROM, this was stuck at 28%.
Now I was able to flash back to WM5 rom, but I world like to Upgrade to WM6 official ROM, anyone help?
I had this problem when upgrading to the Australian WM6 official HTC Release. The way around it is to run the Trinity Service Provider & CID unlock program from the link below. Dont know why but to use either release, Dopod or HTC WM6 you must run this tool first.
ftp://xda:[email protected]/Trinity/Tools_and_Programs/HTC_Trinity_SIM_CID_Unlock_v1.zip
Hope this helps
you don't *have* to CID unlock your device to use these upgrades..
again, sometimes it gets stuck, sometimes it seems to work.. you can just keep trying.. mine magically worked after a while. the most sure method is to use a modified RUU, of which there's a few on the forums and a few threads regarding these issues..
racerx_ said:
you don't *have* to CID unlock your device to use these upgrades..
again, sometimes it gets stuck, sometimes it seems to work.. you can just keep trying.. mine magically worked after a while. the most sure method is to use a modified RUU, of which there's a few on the forums and a few threads regarding these issues..
Click to expand...
Click to collapse
HI, Thank for your reply, how can I do the modified RUU?
Hi all,
I have success to flash the WM6 official ROM.
this is my experience:
To flash the Radio ROM first, I has flash the 1.50.08.11 Radio ROM.
Then to download the Dutty NBH Tool to take off the Radio DOM of WM6 official ROM.
Then to flash the modify ROM.
Now, my phone is running WM6.
racerx_ said:
you don't *have* to CID unlock your device to use these upgrades..
again, sometimes it gets stuck, sometimes it seems to work.. you can just keep trying.. mine magically worked after a while. the most sure method is to use a modified RUU, of which there's a few on the forums and a few threads regarding these issues..
Click to expand...
Click to collapse
Learn something new everyday. Never knew that simply modifying the RUU would itself allow the updates. Just tried it, and yes it works also.
racerx_ said:
you don't *have* to CID unlock your device to use these upgrades..
again, sometimes it gets stuck, sometimes it seems to work.. you can just keep trying.. mine magically worked after a while. the most sure method is to use a modified RUU, of which there's a few on the forums and a few threads regarding these issues..
Click to expand...
Click to collapse
how do mofify the RUU? and what do I modify it to?
thanx walterjm
Can you share HK-CHT rom for noSPL noIPL noRadio ? Thanks!
WildsideUK said:
I had this problem when upgrading to the Australian WM6 official HTC Release. The way around it is to run the Trinity Service Provider & CID unlock program from the link below. Dont know why but to use either release, Dopod or HTC WM6 you must run this tool first.
ftp://xda:[email protected]/Trinity/Tools_and_Programs/HTC_Trinity_SIM_CID_Unlock_v1.zip
Hope this helps
Click to expand...
Click to collapse
Can you share HK-CHT rom for noSPL noIPL noRadio ? Thanks!
I had the same problem and I resolve it by extract the rom and re-build it ... look at the thread http://forum.xda-developers.com/showthread.php?t=327667
Good luck
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.
Alright, so i decided to finally get into my 8125's skin.. so i followed tutorials on this website.. started by using button's downgrader and then used the lokiwiz to unlock the CID and SIMLock.. after that i used the T-mobile 2.26 ROM and after that I installed Farias WM6 ROM.. the problem is that now I do not get any cell phone reception when I put in a T-mobile card or any other card and it just keeps on searching and searching.. also the flash light at the back of the phone is also half lit.. i checked by switching it on through the camera function in which it goes full strength but I would say its abt 20% right now.. does anybody know any remedy?
My easiest advice, since this happened directly after flashing then work on the principal that its the culprit. So just reflash it and make sure u first flash with a stock ( non custom made ) rom.
Hope it helps!
thanks for the reply.. i was beginning to think nobody would be able to help me.. anyways.. i tried to flash it with the OEM rom i got from the HTC website but that didnt help.. any other suggestions?