I tried (for a 30th time or so) to upgrade my unlocked 3G MDA to another ROM.
In first instance it started up correctly and installed the customization. Then it rebooted, and since that moment it keeps on rebooting every 3 minutes or so, but it doesn't go any further.
go to bootloader "RGB Colors" then reflash
It has to be Both SIM unlocked and CID unlocked aka Super CID. Make sure it is both.
I unlocked it everything already a year (or so) ago.
I also removed both SIM- and miniSD card before flashing.
I am now flashing in 'RGB-bootloader' mode...it is flashing now, i'll let you now if it will work out!
It worked marvelously! Thanx!
I pressed the Camera-button while resetting, got to the RGB-bootloader and it all worked like a charm!
good to here that..
just post again when ever you have a problem..
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)...
hi there,
After I have successfully done the SIM & CID unlock on my Orange M700, the clock on the Orange theme just freezes all the time, only if i restart it, then it goes back to the right time, but one minute later it freezes again..
thanks for your advice.
shawn
Mine did that all the time without unlocking it (either SIM or CID), however after flashing to LVSW's WM6 it's been fine.
I would suspect the Orange extended ROM / pluging (not sure which is which but you know what I mean!)
Flash a shiny new ROM is my 2pence worth
Hi all,
I have been visiting these forums for 2 years now and have downloaded some great tools and ROMs to enhance my Trinity, however something all of a sudden has gone very wrong!
I upgraded to WM6.1 Elegance edition about 3/4 months ago, CID unlocked the phone about a month ago and everything has been working like a dream.
However just today, I attempted to turn the volume down on my phone during a meeting (I always forget to normally!) and there was no display. After few battery resets, again no display. It starts up, loads the the Elegance splash screens and then hangs on the screen before when the OS should appear.
My decision was to flash the ROM again. I cant flash using Activesync as it wont pick up on the hung screen, so I started the bootloader and got as far as 1% of the flash and it will restart. So I tried the SD Card method when resulted in a "loading" screen appearing for a few seconds and then it goes back to the standard bootloader and displayed a 00068002 error.
I am out of ideas, I hear mtty.exe is a good program for this kind of thing, but what I want to know is if this is fixable or if I should give up!
I have been working on this since 2pm today none stop!
Can any of you guys give me any suggestions please?!?!?
Kind regards,
Jonathan
Should be a cinch
Did you SPL the Phone before flashing roms?
If you put the phone into the bootloader mode The RGB screen and kill of activesync you should be able to run one of the flash update programs.
If I have flashing problems its usually Active sync so I kill it then run the flash program.
I've got a sneaky suspision your battery might be causing the problem.
Hi there, thanks for the reply. As I was new to upgrading I havent used SPL on the phone before flashing the ROMS. I did use an unlock tool recently as i wanted to try a different network SIM to see if it worked when I was in South America, so the phone is unlocked to all networks. Are you saying if I SPL now it should sort the problem out? If so how do I do this withour ActiveSync working - can you use SD?
Another thing I failed to mention was that when I start an upgrade and it follows all the steps, it doesnt say the current ROM on the screen where you press update ROM. It just gives the name of the new ROM and the current one is left blank.
I have disabled Active Sync before attempting the update. It seems to go through fine and then the phone restarts wafter 1% of the update.
What makes you think it is the battery? I am happy to spend under 20 pound on ebay if you think it will fix the issue!
try unbrick.bat.......my trinity was also stuck.......unbrick.bat save my day....
The same happened to me several time....I could not find a solution other than this one:
1. Flash the official HTC ROM.
2. Flash the required ROM then.
it works for my TrinTy.
Hi guys,
Please forgive me for asking the question, I've spent the last two hours searching for someone with a similar issue and can't find anything.
Basically I'm wanting to sim unlock my UK Orange TyTn II (Kaiser). I've read through the unlock thread and know that I need to install HardSPL. I've installed v1 - it all goes through fine but I don't seem to be able to get into bootloader mode.
I've flashed the radio image as per step 5 (step 1 folder) and this went through okay and changed the radio image. I reflashed it to 1.27.12.17 and during the flash process where it takes the phone into bootloader mode as part of the ROM update utility I could see it said SPL-1.0.OliPoF on the 2nd line of the bootloader (which means HardSPL is installed doesn't it?)
No matter what combination of buttons I've tried - holding the camera button firmly, holding the camera and power button and reset I just can't get the thing to go into bootloader mode using either a soft reset or from a clean power on. I've tried it with and without sim card and sd card to no avail.
My original rom versions were:
r 1.27.12.29
g 22.45.88.07h
d 1.81.00.00
Obviously the radio version is now different but the other two remain the same.
I'm confident that HardSPL is installed, I just can't get to the bootloader!
Any help would be much appreciated.
Oh dear.
I've just put my orange sim card back in and I'm still getting the network locked please input unlock code that I got with the "strange" sim card even when I've overwritten the radio rom with a newer version.
Balls
--update--
Tried another radio version and still it says network locked with original orange sim card, so I've got no choice but to try to get the bootloader thing sorted as I can't use my original sim now. Ever wish you'd not started something?
--update--
Paid £20 to IMEI-Check.
--final update--
Updated to Dutty's latest ROM, everything is fine, still unable to make the phone go into bootloader mode so no idea whats going on there. HardSPL is definately installed. This new ROM is so much nicer than the orange factory setup.
Serves me right for being stupid
the same here but with hermes.. from SPL 1.09 tried to install hardSPL v7, done it NOT in bootloader mode, processed to 'finished' page, WM is working, but can't get to bootloader anyhow.. installed drifferent ROM, succeeded, but can't get to bootloader either.. any ideas what is going on??
Hello there,
I messed up my just acquired used HTC Breeze. Isn't too bad, as it wasn't so expensive and it had SIM lock anyway. So hadn't I done anything, then I wouldn't have been able to used it as well.
My question: The info 2 - command returned "HTCSF kEØ(HTCE", so as far as I understand the bootloader has been bricked. But why can I still get to the three-color-screen? I always thought, this is only possible, if the bootloader is not bricked. I'm very sure I read about that regarding a HTC Canary.Or isn't that the case anymore with never devices?
In case anyone's interested, the whole story:
I tried the Hermes unlocker-method, but couldn't get it to work. The first problem was, that SSPL didn't work, because my phone was app-locked. Well removing the app-lock wasn't that hard.
I eventually managed to find out, how exactly this SSPL-stuff works. However, I still couldn't use the Hermes-unlocker. Flashing with SD-card wouldn't work - and using the RUU would only cause the phone to reboot, hence leaving the SPPL and being stuck with the normal bootloader, which wasn't unlocked (sorry if that sounded too untechnical - you probably know, what I mean).
So my last hope was the thread "Application UNLOCK/SSPL/HARDSPL" . First I upgraded to SPL 1.09 (might have been a bad choice, as I didn't think it through). Phone would still work then. Then I tried RUU_MTeoR_1.34.251.1_1.38.00.10_HTCEUR_SHIP , which is where I probably broke my bootloader, as it wouldn't start the OS after successfully flashing. (although it was IPL 1.00 and SPL 1.09, if I remember correctly).
Then I flashed RUU_BREE100_1.13.251.2_1.06.00.10_QtekEUR_Ship_R3 via SD-Card, cause it's said to have SPL 2.05. With that I wanted to do the final step in the said posting - flashing hardspl, so that I'd get SPL 7.77 anytime, without SSPL. I thought, the Hermes unlocker might work then. Only it was a dead end. After flashing to RUU_BREE100_1.13.251.2_1.06.00.10_QtekEUR_Ship_R3, I couldn't get anything to work anymore. And now I'm stuck with IPL 0.90 and SPL 1.09. End of the Story
If you can see three color screen (bootloader) that's mean it's ok Try flash with shipped ROM from the bootloader mode. I can upload it to you, but I have to know your device brand (CID lock)...