Related
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)...
well, it had been awhile since i upgraded my phone, since i havent been using it as much because the signal was too weak at home, so i switched phones. now i wanna switch back and forth as needed. so, i downloaded to the button rom, then upgraded to faria's 3.3. as you see, i missed a step. upgraded after buttons to something else. so, this is what i have now...
IPL 1.01
SPL 1.01
GSM 1.12.10.0
OS 3.3.0.0
i think i missed the step since finding the roms are harder since they've been pulled from the ftp, and rapidshare sucks if you dont have a premium account.
so, what i need to know is the best/easiest way to fix this. do i need to roll everything back and start over, or do i just need a certain rom to fix it. if there is a recommended one, can i get the full name so i can google for it. i'm not looking for someone to hold my hand, just let me know the file names so that i can find them.
thanks.
btw, my service is att in case it matters.
I believe you just need to flash an official ROM such as T-Mobiles 2.26 and it will upgrade your IPL/SPL for you and then you can flash whatever ROM you want to.
Yes, just upgrade to a ROM that is with IPL, SPL and Radio, or just get a updater that only have IPL, SPL and Radio then flash in bootloader mode.
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
So I been trying to upgrade my OS to the tnt 1437, however every time I try my old OS keeps popping up (OS: 5.1.xxx (Build 15671FARIA.3.5)) ... so for the last 3 days I been trying to search this site for any answers, however all I get is that only happens if the CID is locked, but my phone isn't 1) I unlocked it before to upgrade it in the first place to the above mentioned OS and 2) I checked its status with the Wizard Service Tool (which is AWESOME). So i'm at a lose here as to why every time I either upgrade or downgrade the ROM the same OS keeps showing up. BTW Everything else I can upgrade except the OS. Any help is appreciated. thanks!
I've had this.. flash the original rom (or wizard_love rom or something) and then reflash your WM6 ROM.
Don't forget to hard-reset when you're using the ShellTool to flash
Yea I forgot to mention I've done that. I've downgraded to both button ROM and love ROM however I get the same results, the IPL and SPL are downgraded but not the OS. The only thing I have NOT done is the hard rest, is that the missing link here?
Ok, here's what i did:
I'm sending my xperia back to vodafone, so i need to restore stock rom and spl. I flashed a NL Vodafone R3AA rom (found here) to my phone yesterday, which worked perfectly. Did a hard reset, and went on with restoring stock spl.I tried using the special RUU with a replaced stock spl .nbh (the method described in one of the topics here), but the RUU couldnt find my phone. Since i didnt have another PC here, i tried to flash the .nbh to my phone via the micro SD method.
This went well, the progress bar filled up and disappeared, followed by 10+ minutes of "loading". Advised by a friend, i pulled out the battery, put it back in the device and powered it on. The phone instantly booted, showing the bootloader-screen and saying it's going to resume flashing the device. Followed by another endless "loading" screen.
But, since i got a chance to look in the bootloader-screen, I saw the SPL version was now 0.72.000 (or something like that, at least the OliNex text was gone). Afaik, this means the stock spl is back. I tried replacing the stock spl Kovsimg.nbh with the default one provided with the custom RUU (which is OliNex HardSPL, right?), but it showed the same "loading" screen. I havent tried flashing the rom again, since the bootloader says it's on stock spl at the moment...
What can i do? I guess they dont accept bricks over at vodafone...
Thanks in Advance,
Sorbo
using the usb cable and the ROM flashing Custom_RUU.exe
flash the R3A Rom again. that should fix it not booting!
You also need to flash the radio back to stock (not sure what version it is, but it's around here somewhere) otherwise you'll face flash issues. This means flashing HardSPL flashing the radio, flashing StockSPL again and return. Also, best flash R2A. Not sure if R3A was ever properly released.
Ok guys, thanks for the replies
Jonny4911 said:
using the usb cable and the ROM flashing Custom_RUU.exe
flash the R3A Rom again. that should fix it not booting!
Click to expand...
Click to collapse
The phone is back on stock spl, is it possible to flash a rom? Or only stock roms? (Sorry for my dumb question, havent been into flashing for a few months now)
aethelbert said:
You also need to flash the radio back to stock (not sure what version it is, but it's around here somewhere) otherwise you'll face flash issues. This means flashing HardSPL flashing the radio, flashing StockSPL again and return. Also, best flash R2A. Not sure if R3A was ever properly released.
Click to expand...
Click to collapse
Ok, thanks for the tip R2AA it is!
When flashing the rom the radio was also updated, but i'll try this
R3AA was properly released!
if you want to be cure of complete stock why not just use SEUS?
and there is no need to flash radio with stock ROMs as they're included, all your doing is flashing a radio extracted from a stock rom anyway! this means you don't have to hardspl
Jonny4911 said:
using the usb cable and the ROM flashing Custom_RUU.exe
flash the R3A Rom again. that should fix it not booting!
Click to expand...
Click to collapse
And this was the winning tip. Just flashed back the R3AA rom (vfone NL), even though i doubted if it would work (since the bootloader said it was back on stock spl), but it did.
Phone works again. Bootloader now says 0.78.000 (or something like that, no OliNex), so i guess it's ok now. RUU still isnt able to flash the phone, tried on 3 different pc's ( win7 x64, vista x86, xp x86), but i cant flash the phone...
Ah well, i'll try to send it back, see what they come up with. Thanks a bunch!