Hi
I have installed a number of different roms on my Phone before(molski roms) and the latest was FARIA/Molski aku 3.2.
Now i want to upgrade to Faria 3.3 ROM and the updater gives me an error. My phone switches off, but nothing seems to happen.
I tryed the older aku2.3 aswell and the same thing happens, i also tryed my orignal t-mobile rom.
Can anybody Help.
My phone should be unlocked as i did install molski roms and faria roms before.
What error message does it gives you?
Related
Hello,
I seem to be having a weird error when I try to unlock the ext rom or unhide it. I can see the folder in my programs folder, but when I click on unhide, nothing happens and when I click on unlock I get a debug error which says "FL_IOCTL_BDTL_HW_PROTECTION - The parameter is incorrect" . I dont know why it keeps doing it. I have tried to upgrade to the latest rom version but after getting in the bootloader mode, in the utility screen it does not show me the new version of the rom, the only thing it shows me is that my device will be upgraded to 5.3.2, which is what i currently have.
Any idea why its doing what its doing?????
Thanks,
Sam
sameer25 said:
Hello,
I seem to be having a weird error when I try to unlock the ext rom or unhide it. I can see the folder in my programs folder, but when I click on unhide, nothing happens and when I click on unlock I get a debug error which says "FL_IOCTL_BDTL_HW_PROTECTION - The parameter is incorrect" . I dont know why it keeps doing it. I have tried to upgrade to the latest rom version but after getting in the bootloader mode, in the utility screen it does not show me the new version of the rom, the only thing it shows me is that my device will be upgraded to 5.3.2, which is what i currently have.
Any idea why its doing what its doing?????
Thanks,
Sam
Click to expand...
Click to collapse
If I remember correctly, Extended ROM unlocker is not working under WM5.
Not able to upgrade to 5.1.1700
As you say aybe the unlocker does not work with WM5, so I downgraded to the original factory version of 1.42. At this point the unlocker worked fine. So I tried to upgrade it to the latest version of 5.1.1700, but as soon as the utility screen comes up, it shows me that my rom will be upgraded to 5.03.02 which is what i have had all this while. So I upgraded it back to the same version and just upgraded to the latest radio version. When I try to use the unlocker again in this 5.03.02 version I still get that same error.
Can anyone please help me to upgrade to the latest rom version 5.1.1700 and tell me what this error means.
Thanks in advance,
Sam
Re: Not able to upgrade to 5.1.1700
sameer25 said:
As you say aybe the unlocker does not work with WM5, so I downgraded to the original factory version of 1.42. At this point the unlocker worked fine. So I tried to upgrade it to the latest version of 5.1.1700, but as soon as the utility screen comes up, it shows me that my rom will be upgraded to 5.03.02 which is what i have had all this while. So I upgraded it back to the same version and just upgraded to the latest radio version. When I try to use the unlocker again in this 5.03.02 version I still get that same error.
Can anyone please help me to upgrade to the latest rom version 5.1.1700 and tell me what this error means.
Thanks in advance,
Sam
Click to expand...
Click to collapse
I think we have a slight misunderstanding here. 5.03.02 and 5.1.1700, here are exactly the same. 5.03.02 is the ROM version, while 5.1.1700 is the OS version of the ROM. So 5.03.02 IS 5.1.1700 actually.
So, one prob solved, how about this one....
First of all, thank you KTamas for helping me out on this one and clearing out this problem of Rom versions.
I have another question though, what is this wizard rom? and how different is it from the one that I just installed? I was trying to install the wizard rom before I installed the one that I have right now, but got stuck in the middle when I had to create the EXTROM folder and transfer the contents after editing the edit.bat file. I was not able to transfer the getdeviceid.txt file from my phone to my pc for some odd reason and so was not able to do much on that.
Can you please help me?
Thanks,
Sameer
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)...
ok im having problems uploading this rom... i keep getting error 260 on every rom. i tried to change it from 3.3 v1...it seems that the only thing its alowing me to do Is degrade every rom... i went from 3.3 to 2.24(moliski's version) succesfully. From 2.24 i tried to up date to 3.3 v2 unsucessfull. Then i tried to update from 2.24 to 2.26(moliski's version) unsucessfull. Then went from 2.24 to 1.05 and it work successfully. From there i went from 1.05 to faria's 3.3 v2 and it didnt work, i kept getting error 260 on the computer when its in the IPL SPL with the 3 colored screen on my phone. and now im stuck on 1.05... i dont know whats going on and i asked for help b4 but no one helped. Every flash procedure i did was right (including cid unlock etc) PLEASE CAN ANYONE HELP MY POOR WIZARD ;-;
1.05 to 2.X to 3.3
You need to upgrade from 1.05 to a 2.X before going to 3.3
have you considered that you may have a corrupted rom?
download again.
and please try to title your problems accordingly. ...lets not spread rumours[farias 3.3 v2 problems.... ]
you are having trouble upgrading your device...not problems with the rom itself.
thanks.
here is your new title
unable to upgrade to faria 3.3 v2...help welcome.
Hello!
I tried to flash my Charmer with the new german Aku 3.3. At first everything seems to be ok, but at 95% it stops and i got the Message: update error- there is an comunication problem! So what can i do? I tried to flash the old rom back but there comes also at 95% a message: invalid command - nfb file cannot be used for your pda!
Please help me !
Greetings Musna!
Ps: can somebody upload a sd image for the mda compact II !
Go to bootloader mode, then try to flash RUU rom (1.x). You can find it on Charmer wiki.
It doesn`t work too, it always stops at 95% has anyone another idea?
did you try hard reset?
Yes i tried hard reset, but it is always in bootloader!
I have also the same problem. Tried to upgrade to version 3.3. Everytime it stops at 80%. I don't know why?! I can repair it with the software and re-run it. But it has the same effect.
Now i will try to downgrade to 2.6 again. I really don't understand what causes the problem. I hope i will get this thing running again....
EDIT: I reflashed the device with the older 2.6 ROM and it is working right now. However I didn't really get why it gets stuck at 80% with 3.3 ?!?!
nitrane said:
I have also the same problem. Tried to upgrade to version 3.3. Everytime it stops at 80%. I don't know why?! I can repair it with the software and re-run it. But it has the same effect.
Now i will try to downgrade to 2.6 again. I really don't understand what causes the problem. I hope i will get this thing running again....
EDIT: I reflashed the device with the older 2.6 ROM and it is working right now. However I didn't really get why it gets stuck at 80% with 3.3 ?!?!
Click to expand...
Click to collapse
The aku3.3 is up to date the bootloader version!!!
IPL and ISP version now is 3.00.
http://www.windowsceportal.hu/forum/viewtopic.php?t=1079
Sorry but i do not speak hungarian. What do you want to tell me ?
I´ve got the same: My charmer is in Bootloader IPL 2.06.0001 SPL 3.08.0001
I can´t downgrade to AKU 2: Please order a newer Version.
Every try to upgrade to AKU 3.3 failed at 95% with Error 326.
Is there any help for my charmer???
oh.**** !!!! I got the same problem with them and my first pda uk rom already empty screen and then i try with my scrond pda German rom it the same problem and now just only show in bootloader screen.Have i ask someone who knowage about this he told me that if SLP in you PDA have chang it be hard to repair.So,I think I lose 2 PDA did I try to flash in T-Mobile Official Rom de that i hope to develop it but i hve to kill 2 Charmer.Who take responsibilities,T-Mobile right ???
Ok no problem you can repair it! At first you have to brand your device with the rom you want to! After 95% the Problem will come again! When it stops you have to go with a reset to bootloader again.When your device is in bootloader you have to install the Radio Rom from this thread:
http://forum.xda-developers.com/showthread.php?t=302768
After that your device will be able to boot again and it should work!- But the Problem during the installation will stay,so you have always to use this way to flash your Mda compact II!
In the new rom there must be a problem with the radio rom and this causes the broken device.
I`m sorry for my bad english but i`m not used to talk very much! So i hope you understand what i mean!
Greetings from Austria Musna!
that link is broken
Then try this one:
ftp://xda:[email protected]/Prophet/Radio_Roms/Prophet_G4_RadioRom_v2.47.11.exe
You can find the radio rom also on the ftp server. Prophet> Radio Roms>Prophet_G4_RadioRom_v2.47.11.exe
You can try different Radio Rom versions, i have flashed the v.247.11 and it worked.
Normaly it should work!
Thank u so much !!! My Charmer secrond PDA come back have life again and it can working.So,my Charmer first PDA UK rom still empty screen and notthing working when i press any button.Who can slove this problem !!
Musna do you have any massage such as msn
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?