Related
I have upgraded from 'RUU_Prodigy_2080707_107_11310_QTEK_DAN_Test.exe' to 'RUU_Prodigy_2180705_21807105_20710_QTEK_DAN_Ship.exe'
I wish I did'nt, now I cannot use my Motorola HT820 stereo bluetooth headset.
Please carve it out in big letters how to downgrade to 'RUU_Prodigy_2080707_107_11310_QTEK_DAN_Test.exe'. (It says "ERROR [296] : UPGRADE ONLY"
Please help...
is the 2.18 rom in english?
Maybe I'm wrong here, but shouldn't you just be able to load the original test ruu again by running the exe? CID lock won't be an issue since both roms are Qtek roms.
Nope, it says "ERROR [296] : UPGRADE ONLY"
I even have a confirmation from the vendor saying it is suposed to be this way...
Is this something for you ?
jbendsen said:
Nope, it says "ERROR [296] : UPGRADE ONLY"
I even have a confirmation from the vendor saying it is suposed to be this way...
Click to expand...
Click to collapse
Enter Bootloader, - hold the "camera" and shortly press the reset button, don't release "camera" until you can see color screen, connect USB cable, and start to flash any ROM you like
It has to be a shipped version not only a sepperate rom.
something like:'RUU_Prodigy_2080707_107_11310_QTEK_DAN_Test.exe'
Thanks, I will try this when I get back home from work...
But first a little clarification...
Bootloader? How do I start bootloader, on the PC or on the Qtek 9100?
If this works you are my new guru...
jbendsen said:
Thanks, I will try this when I get back home from work...
But first a little clarification...
Bootloader? How do I start bootloader, on the PC or on the Qtek 9100?
If this works you are my new guru...
Click to expand...
Click to collapse
with the bootloader i mean the bootscreen of youre Qtek during a reset
the logo with os versions.
@reejmond:
But of course! From the bootloader, the RUU has no idea of what the current ROM level is (it actually displays blank info for the original version), so any "upgrade only" code won't work. I've done this myself on a device that got "bricked" by a remote wipe test. Does it even check for CID lock when started in this manner?
Sleuth255 said:
@reejmond:
But of course! From the bootloader, the RUU has no idea of what the current ROM level is (it actually displays blank info for the original version), so any "upgrade only" code won't work. I've done this myself on a device that got "bricked" by a remote wipe test. Does it even check for CID lock when started in this manner?
Click to expand...
Click to collapse
It just work! nothing else
Sorry same error????
Did not work, same error message as usual. What to do????
spl and ipl
spl is 2.18 and ipl is 2.18 don't know if this helps, anyone???
Re: spl and ipl
jbendsen said:
spl is 2.18 and ipl is 2.18 don't know if this helps, anyone???
Click to expand...
Click to collapse
Is youre Qtek9100 cid unlocked ?
you can do it with lokiwiz
How do u check if the cid is unlocked?
Yes, I used some program to set it to '11111111', but I do not know how to validate...?
I am exactly in the same situation and can not downgrade. I want to downgrade to an earlier ROM as my companys email application for PDAs(www.good.com) do not run under the new 2.18.7.5 DAN.
I have also tried the bootloader trick without success.
Any suggestions on how to downgrade from the new ROMs?
I found the solution in http://forum.xda-developers.com/viewtopic.php?t=46608. This worked for me. See also http://forum.xda-developers.com/viewtopic.php?t=47848
/JP
Cid Unlock
'ftp://xda:[email protected]/Uploads/HTC Wizard/Misc/aWizard-v1_2.zip'
Cid Unlock
Hi all, i am stuck, i need the help of the experts in either saying my 2 Qtek 9100s are bricked - chuck them or, they are retreivable.
Here goes:
2 X Qtek 9100 made by T-mobile - emei if needed.
Both devices stuck on the boot screen, but will both go in to Tri colour screen for flashing, but fail flashing (with several roms), i think they have button rom, its a beer glass.
GSM: - 01.12.10
OS: - 1.5.4.2
ipl 1.01 and spl 2.24
Can these be revived?
Thanks.
A Wizard by T-Mobile is a "MDA Vario", you can't have a Qtek9100 by T-Mobile. Anyway..
Have you tried flashing official ROM while they are in bootloader mode (tri colour)? Does the flashing process went smoothly? Does the IPL/SPL change when you flash the latest ROM? Give more info.
More info
At present both of them are stuck on the info below, i cant reflash them with anything else now.
Official T-mob rom 2.26 will not work...think the error was [239] or something.
Thanks.
lokidan said:
At present both of them are stuck on the info below, i cant reflash them with anything else now.
Official T-mob rom 2.26 will not work...think the error was [239] or something.
Thanks.
Click to expand...
Click to collapse
sounds like u didn't accomplish step 16 of 'the definitive guide to unlocking & rom upgrading G3 wizards' by Dr Puttingham.
both IPL AND SPL need to be the same
lokidan said:
At present both of them are stuck on the info below, i cant reflash them with anything else now.
Official T-mob rom 2.26 will not work...think the error was [239] or something.
Thanks.
Click to expand...
Click to collapse
what was the exact error.. post the code and error msg.
i got the same problem
ipl/spl 1.01
i tried "CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE"
many many time but nothing
please help
bigfatjack said:
i got the same problem
ipl/spl 1.01
i tried "CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE"
many many time but nothing
please help
Click to expand...
Click to collapse
Since your ipl/spl are 1.xx just follow the sticky by Dr. P at the top of this forum. You will start at the step running lokiwiz as you don't have to downgrade. Then upgrade to an official 2.xx rom. After that you can flash a custom rom.
errors
Various error messages with various roms.
Invalid vendor
Invalid nkbf file
Upgrade only
I believe that these devices were upgraded by a user who perhaps did not fully unlock them.
Is it possible these devices would exhibit these error if they were flashed with a G4 rom, or would they just not boot if that was the case?
Thanks ALL
lokidan said:
Various error messages with various roms.
Invalid vendor
Invalid nkbf file
Upgrade only
I believe that these devices were upgraded by a user who perhaps did not fully unlock them.
Is it possible these devices would exhibit these error if they were flashed with a G4 rom, or would they just not boot if that was the case?
Thanks ALL
Click to expand...
Click to collapse
Well, the only difference between a G4 and a G3 rom is that the G4 rom will not contain IPL/SPL. If you flashed a G4 rom in a G3 device you are fine. If you flashed a G3 rom into a G4 device then you have bricked your devices.
In your case you haven't finished the unlock/downgrade process. like mentioned above you seem to have missed step 16.
You need to re-flash the button rom to get both the IPL and SPL to 1.01. Once that is done then flash an OFFICIAL carrier rom (T-Mobile 2.26 suggested). When you have completed that then your IPL/SPL will both be 2.26. From THIS point you will be able to flash a custom rom, you will have no success until then. The unlocking guide that is stickied contains everything you need to recover from your situation.
The 2 steps that most newbies forget is to downgrade a second time to get IPL/SPL to 1.01 and after you are completely unlocked then upgrade to an official carrier rom that includes IPL/SPL (note this unlocking procedure is not for G4 devices -- doing this will brick them) Once your IPL/SPL are 2.xx THEN you can flash custom roms.
Unlocking them
Thanks ZZan, i think though i have actually blown the rom with button, but it does not bring the ipl/spl down to 1.01, it appears to blow the rom and complete 100% reboots and comes up with button Beer glass and goes no further.....
Err help?
lokidan said:
Thanks ZZan, i think though i have actually blown the rom with button, but it does not bring the ipl/spl down to 1.01, it appears to blow the rom and complete 100% reboots and comes up with button Beer glass and goes no further.....
Err help?
Click to expand...
Click to collapse
Have you tried booting into bootloader and putting your carrier's latest rom back into it? I would suggest this. If all works and you can get completely back into the phone, you could try to unlock again starting from the beginning.
The only way you could have really hurt your device is if it was a G4 before you started, or interrupted the flash process while the bootloaders were being written. I don't think it would even boot up to that screen, or flash to 100% if this were the case though. It sounds like a bad flash from the first button attempt. I would suggest using a carrier rom from the carrier that the phone is locked to to get it back to working status. Once there then you can try to downgrade and unlock again.
Are they G3 or G4
How do i tell again, something to do with the ipl/spl revisions?
You can also try re-downloading the button rom and performing the downgrade again. I have the button rom in my sig. it's possible the rom may be damaged in some way.
G3 or G4.. from the wiki
A G3 Wizard will have the following
IPL: 1.xx or 2.xx or 2.xx.00x (Note that this version only has TWO 0's.).
SPL: 1.xx or 2.xx or 2.xx.00x (Note that this version only has TWO 0's.)
A G4 Wizard will have the following
IPL: 2.xx.000x (Note that this version has THREE 0's.)
SPL: 2.xx.000x (Note that this version has THREE 0's.)
button rom
Any ideas where i can get this rom from?
thanks.
Ignore me
just seen it on your footer
It flashes but....
it goes all the way through 100%, reboots and sits on rom boot screen exibiting:
IPL 1:01
SPL 2.24
GSM 01.12.10
os 1.5.4.2
And a nice picture of a beer glass....
Help, should i reflash again? i Have done it 3 times and it still sits on boot....
Thanks.
lokidan said:
it goes all the way through 100%, reboots and sits on rom boot screen exibiting:
IPL 1:01
SPL 2.24
GSM 01.12.10
os 1.5.4.2
And a nice picture of a beer glass....
Help, should i reflash again? i Have done it 3 times and it still sits on boot....
Thanks.
Click to expand...
Click to collapse
You said your phone was a T-Mobile phone. Flash the T-Mobile 2.26 rom and see if you can get it to finish booting. If so THEN you can retry the button rom. You are in a corrupt state right now. Whatever caused it, it doesn't look like the button rom is going to recover you from it. Flash the official carrier rom for your phone and get it back to working status first. Once you can use the device and phone then you can go back and start from the beginning of the unlocking thread.
T-mob original
I have tried T-mob original (RUU_Prodigy_2210206_22102109_021911_TMO_UK_WWE_Ship.exe)
[294] invalid vendor ID
I have tried t-mob (RUU_Prodigy_1060204_105_11210_TMO_UK_Ship.exe) using NoVendorID and nk.nbf from above rom - Flashed 100% complete - rebooted - stuck on Button boot screen (beer Glass) and not booting.
Button itself will flash, with the same result, looks like its doing it then reboot, halt on beer glass.
I have i trully bricked these two? i cant have they flash and go to boot loader surely they would not do this if i had totally bricked them???
Help....
T-mob
Weird, it has upgraded the IPL to 1.06 (from 1.04) though, does this mean anything to anyone?
Qtek 9100 had molski 2.26 build and tried to flash ROM to XDA mobile 6. Now it sits at boot loader three colour screen showing IPL/SPL 2.26 and won't update further than 99%.
Any ideas how to resurrect this one?
UPDATED: I take it the lack of response means I've got me a brick then?
Go To This link http://forum.xda-developers.com/showthread.php?t=285435
Then Go Download the T-Mobile 2.26 ROM which is in Step 17.
After That run it install the rom and everything should be back to normal.
that keeps happening to me while Upgrading to WM6. I Still Can't Get it to Work Right.
Have you tried to upgrade to a WM5 with AKU3 before jumping to WM6? Molski has a WM5 AKU3 2.26 ROM
I'm having similar trouble and feeling like an idiot. I've done ROM flashes before but have since had my MDA returned a couple times for warranty exchange and I'm afraid the CID unlock didn't "take"...when trying to flash to WM6 it got to 99% and then returned error 302...No problem, I'll just start over with an official ROM, right? Well, I can't seem to get through a ROM update now because the Tri-color screen is flashing on and off at various intervals and that is interrupting the connection.
Does a flashing bootloader mean I've officially bricked it or is there something I can do about this?
Help please! I love my MDA and want it back!
i already had the same problem, the simple solution which is that you have to make unlock your phone i mean both the sim unlock and cid unlock otherwise your phone will not do wm6
fixed
Got mine fixed by using the Xda_MiniS_LaunchROM_v154102.exe from the link in the definitive guide sticky.
Many thanks for your responses.
hello.
i had problem with wizard. i tried to upgrade rom, but i cant. it stuck on 99% and gives an error. i think it had cidlock, but i cant unlock it from bootloader.
Please help...
Piechcio said:
hello.
i had problem with wizard. i tried to upgrade rom, but i cant. it stuck on 99% and gives an error. i think it had cidlock, but i cant unlock it from bootloader.
Please help...
Click to expand...
Click to collapse
Download official stock rom of your carrier and flash it in bootloaders to recover back to its default working status,then if its a G3 phone, downgrade to ipl/spl 1.xx by flashing Button's Rom and SIM/CID unlock with lokiwiz02b,but if its a G4 ,it cannot be CID unlocked but can be upgraded to wm6 through 'SoftSPL' or 'HardSPL'.
HI
I have a same problem – I have a qtek 9100 G3
ipl-spl 2.17
GSM 02.07.10
OS 2.17.7.2
I can update my rom completely but after restart freeze on ipl-spl screen
And I can’t warm reset it says FORMAT PARTITION FAIL
I try to downgrade my rom but spl freeze on 2.17 – I try button rom and Xda_MiniS_LaunchROM_v154102
I can’t find any official qtek rom for test
And I also try R2SD all with romupdate115 it not work
help please
jalalkarimi said:
HI
I have a same problem – I have a qtek 9100 G3
ipl-spl 2.17
GSM 02.07.10
OS 2.17.7.2
I can update my rom completely but after restart freeze on ipl-spl screen
And I can’t warm reset it says FORMAT PARTITION FAIL
I try to downgrade my rom but spl freeze on 2.17 – I try button rom and Xda_MiniS_LaunchROM_v154102
I can’t find any official qtek rom for test
And I also try R2SD all with romupdate115 it not work
help please
Click to expand...
Click to collapse
You got to have a CID unlocked phone to upgrade to any wm6 Rom.Sometimes SPL do get stuck up at 2.xx while downgrading with Button's Rom,it takes a couple of tries to get it downgraded to 1.xx.Flash the button's rom a few times more till it gets downgraded.You can only CID unlock your phone,if it has IPL/SPL 1.xx.
Download the official stock Qtek Rom from this link:-
http://forum.xda-developers.com/showthread.php?t=342744
zabardast_1 said:
You got to have a CID unlocked phone to upgrade to any wm6 Rom.Sometimes SPL do get stuck up at 2.xx while downgrading with Button's Rom,it takes a couple of tries to get it downgraded to 1.xx.Flash the button's rom a few times more till it gets downgraded.You can only CID unlock your phone,if it has IPL/SPL 1.xx.
Download the official stock Qtek Rom from this link:-
http://forum.xda-developers.com/showthread.php?t=342744
Click to expand...
Click to collapse
Don't use those ROMs as they are for G4!!!
If flashing original ROM doesn't solve the case then you'll have to buy the unlock program from IMEI-check company.
Many thanks
Can you give me some advice what is the best version for qtek 9100 I can’t find any original qtek rom please give me a link
And if I buy IMEI Program after apply that my device starts normally?
I don’t want WM6 only back to normal
And serious problem is
I have FORMAT FAT FAIL for warm reset. In this case its possible hardware (disk on chip) has a hardware problem?
Thank you all
jalalkarimi said:
Many thanks
Can you give me some advice what is the best version for qtek 9100 I can’t find any original qtek rom please give me a link
And if I buy IMEI Program after apply that my device starts normally?
I don’t want WM6 only back to normal
And serious problem is
I have FORMAT FAT FAIL for warm reset. In this case its possible hardware (disk on chip) has a hardware problem?
Thank you all
Click to expand...
Click to collapse
No. the problem is simply of messed up firmware. I believe that the SPL tries to load the OS but it must be at a different address and never starts to load.
The IMEI-check tool will simply CID unlock your device. You still have to do the "r2sd all" procedure...
good luck
Needed
1.an BREEZE device[The phone must be able to enter bootloader (3color screen)]
2.TerraTermPro http://rapidshare.de/files/39206549/TeraTermPro.rar.html
3.An rom matching to your device
GUIDE
1.Disable active sync - uncheck
file->connection settings->allow usb connection
2.Put the phone in bootloader mode
power the phone pressing power and camera keys
read and note all displayed info
3.Launch TerraTermPro on the pc
un the connection window check serial and choose USB
in the new open window type
info 2
and note the information
RIGHT - HTCSQTEK_A07„§m»HTCE
WRONG - HTCSF kEØ(HTCE
close terra term
4.Figure out wich rom you need
till now i have roms for
Russian Rom
QTEK_A07
HTC__A07
http://rapidshare.com/files/109782599/RUU_BREE100_1.34.261.1_1.38.00.10_HTCRUS_SHIP.rar.html
WWE Rom (QTEK,HTC,Dopod,OCH)
QTEK_Z12
HTC__Z12
http://rapidshare.de/files/39206931/RUU_MTeoR_1.34.251.1_1.38.00.10_HTCEUR_SHIP.rar.html
DOPOD001 - Chinese Rom
http://www.megaupload.com/se/?d=YD49L7JD
5.
Flash the rom corresponding to your CID
6.
Boot the phone and application unlock it
7.
Run SSPL and UPGRADE to 6.1 rom and latest radio version
8.
Save the rom that saved you for latter - it colud help you again
IF YOU CANT FIND THE CID AND ROM HERE WAIT TILL SOMEBODY POSTS IT.
IN CASE OF "HTCSF kEØ(HTCE" IN TERRATERM IS VERY HARD TO REPAIR DUE TO DAMAGED BOOTLOADER
you can repair it using this guide
http://wiki.xda-developers.com/index.php?pagename=PB_KITL_HERMES
wich requires some advanced skills
OTHER ROMS - wich i dont have
i_mate_SP_JAS_1.15.301.0.exe
RUU_BREE100_1.15.71.6_1.06.00.00_OCH_Ship.exe
ruu_bree100_1.15.707.3_dopodwwe_ship.exe
ruu_bree100_1.15.709.3_dopodcht_ship.exe
Please help me to improve this list sending me CID's and ROM's
this is what i get
iinfo 2
CID: Wait interpreter timeout
HTCSF kEØ(HTCE
Cmd>
what do you mean by very hard to repair? it's impossible?
this is the ROM i flashed back to my phone (although the flashing is 100% completed successfully, it is still stuck at 2nd boot WM logo screen)
RUU_BREE100_1.15.707.3_DopodWWE_SHIP.exe
i just uploaded th dopod rom in case anyone needs it
http://rapidshare.com/files/109798242/RUU_BREE100_1.15.707.3_DopodWWE_SHIP.exe
alexnvidia said:
this is what i get
iinfo 2
CID: Wait interpreter timeout
HTCSF kEØ(HTCE
Cmd>
what do you mean by very hard to repair? it's impossible?
this is the ROM i flashed back to my phone (although the flashing is 100% completed successfully, it is still stuck at 2nd boot WM logo screen)
RUU_BREE100_1.15.707.3_DopodWWE_SHIP.exe
i just uploaded th dopod rom in case anyone needs it
http://rapidshare.com/files/109798242/RUU_BREE100_1.15.707.3_DopodWWE_SHIP.exe
Click to expand...
Click to collapse
http://wiki.xda-developers.com/index.php?pagename=PB_KITL_HERMES
use this wisely
jerpelea said:
http://wiki.xda-developers.com/index.php?pagename=PB_KITL_HERMES
use this wisely
Click to expand...
Click to collapse
how do i put breeze into KITL Mode? is it the camera+power button tri-colour thing?
reads what stands on hermes wiki page...
maybe i'm talking ****, but i think too enter kitl mode you must have a running windows mobile...
just find the kitl mode "reset" on hermes its "now for your Hermes: hold the Comm button and soft reset and wait for the KITL dialog to appear, now is the CRITICALLY missed step; you need to press the small OK button on the LEFT of the device to activate USB KITL. "
futureshock said:
reads what stands on hermes wiki page...
maybe i'm talking ****, but i think too enter kitl mode you must have a running windows mobile...
just find the kitl mode "reset" on hermes its "now for your Hermes: hold the Comm button and soft reset and wait for the KITL dialog to appear, now is the CRITICALLY missed step; you need to press the small OK button on the LEFT of the device to activate USB KITL. "
Click to expand...
Click to collapse
exactly.. that's the worrying part for me now. i have no idea how do i enter KITL mode in breeze. any ideas?
alexnvidia said:
exactly.. that's the worrying part for me now. i have no idea how do i enter KITL mode in breeze. any ideas?
Click to expand...
Click to collapse
no
i did this on my hermes once
having the same problem as you have on breeze
hermes and breeze share the same platform
we have to find the answer
How did you manage to screw the bootloader
can you provide us a list of what you have flashed on the device?
what is the brand,model(herm 100/herm160),vendor,region of your device
i am triing to figure an solution
all others upgraded succesfully to 1.34 rus getting HTC__A07 CID and after that radio and wm 6.1
what did you do ?
BR
jerpelea said:
no
i did this on my hermes once
having the same problem as you have on breeze
hermes and breeze share the same platform
we have to find the answer
How did you manage to screw the bootloader
can you provide us a list of what you have flashed on the device?
what is the brand,model(herm 100/herm160),vendor,region of your device
i am triing to figure an solution
all others upgraded succesfully to 1.34 rus getting HTC__A07 CID and after that radio and wm 6.1
what did you do ?
BR
Click to expand...
Click to collapse
ok. i have no idea hoiw i screwed up the bootloader too. this is what happens.
i have a dopod 595 device, the breeze with forward facing video call camera, so it's a breeze 160. it's a Qtek_Z12 device and the region is WWE.
before you posted the new herm radio, i successfully updated to your beta WM6.1 using your unlocking SSPL guide. i never upgraded the SPL though. the original phone's IPL and SPL are IPL0.9 and SPL2.05.
so what i did was first to upgrade to the latest WWE 1.38 using your unlocking/SSPL guide, then upgrade to your WM6.1 beta. everything worked fine. i do notice that only the IPL has been upgraded, and the SPL remains 2.05. so i ignored it.
it was when you posted the new herm radio upgrade i then decided to update my SPL as well. so as per your instructions in the unlocking guide, i first unlock the phone (WM6.1), perform the SPL1.09 update. it was successful. phone booted up just fine. then i run the official WWE 1.38 (the same one i used before upgrading to WM6.1 beta). and this time i did not run the DES soft SPL ( i must have forgotten and thought the phone is unlocked anyway). the RUU started, and the flashing failed at 1% giving an invalid vendor ID error message (as expected because my phone is not superCID and i forgot to run DES SSPL). after this little incident, i canot boot my phone anymore.
so i tried to recover it using various methods. and i successfully flashed back the original WM5 WWE dopod 595 ROM by using the latest RUU from 1.38 with old WWE WM5 nbh. the flashing completed 100%, the phone reboots, and still stuck at the second boot screen. IPL has been downgraded to 0.9 and SPL remains 1.09.
what should i do now? i really appreciate you/anyone taking the time to look into this issue. thank you.
have you tryed a hardreset??
and did you cid is now screwed up??
alexnvidia said:
ok. i have no idea hoiw i screwed up the bootloader too. this is what happens.
i have a dopod 595 device, the breeze with forward facing video call camera, so it's a breeze 160. it's a Qtek_Z12 device and the region is WWE.
before you posted the new herm radio, i successfully updated to your beta WM6.1 using your unlocking SSPL guide. i never upgraded the SPL though. the original phone's IPL and SPL are IPL0.9 and SPL2.05.
so what i did was first to upgrade to the latest WWE 1.38 using your unlocking/SSPL guide, then upgrade to your WM6.1 beta. everything worked fine. i do notice that only the IPL has been upgraded, and the SPL remains 2.05. so i ignored it.
it was when you posted the new herm radio upgrade i then decided to update my SPL as well. so as per your instructions in the unlocking guide, i first unlock the phone (WM6.1), perform the SPL1.09 update. it was successful. phone booted up just fine.
Click to expand...
Click to collapse
here you needed the sspl to flash official rom
i think that i have this im my tread
then i run the official WWE 1.38 (the same one i used before upgrading to WM6.1 beta). and this time i did not run the DES soft SPL ( i must have forgotten and thought the phone is unlocked anyway). the RUU started, and the flashing failed at 1% giving an invalid vendor ID error message (as expected because my phone is not superCID and i forgot to run DES SSPL). after this little incident, i canot boot my phone anymore.
Click to expand...
Click to collapse
here you screwed the botloader
now you have an older ipl that does not know how to load the new SPL
so i tried to recover it using various methods. and i successfully flashed back the original WM5 WWE dopod 595 ROM by using the latest RUU from 1.38 with old WWE WM5 nbh. the flashing completed 100%, the phone reboots, and still stuck at the second boot screen. IPL has been downgraded to 0.9 and SPL remains 1.09.
what should i do now? i really appreciate you/anyone taking the time to look into this issue. thank you.
Click to expand...
Click to collapse
did you try to hard reset?
the two "-" keys and power
???
futureshock said:
have you tryed a hardreset??
and did you cid is now screwed up??
Click to expand...
Click to collapse
yes. i tried hard reset (two soft keys+power then press 0) many times. doesnt work. tried the mtty to format the phone, doesnt work.
here you screwed the botloader
now you have an older ipl that does not know how to load the new SPL
ok, firstly, when i loaded up the SPL1.09, the phone boots up fine. it only got stuck when the flashing to WWE1.38 failed. at this point i still have the new IPL.
the old IPL was flashed in during the recovery attempt when i tried to flash the old official WM5 ROM back hoping it would also downgrade the SPL, but it didnt. it only downgrade the IPL to 0.9. SPL remains 1.09
alexnvidia said:
here you screwed the botloader
now you have an older ipl that does not know how to load the new SPL
ok, firstly, when i loaded up the SPL1.09, the phone boots up fine. it only got stuck when the flashing to WWE1.38 failed. at this point i still have the new IPL.
the old IPL was flashed in during the recovery attempt when i tried to flash the old official WM5 ROM back hoping it would also downgrade the SPL, but it didnt. it only downgrade the IPL to 0.9. SPL remains 1.09
Click to expand...
Click to collapse
im my guide i wrote to use sspl
if you use sspl you finish the 1.34 upgrade from spl 1.09 and is everything fine
if not no
from here you had spl A07 so you could flash ONLY original htc Rus rom
you flashed an older ipl instead
an older ipl that does not load correctly the new spl
the spl can not be downgraded from 1.10(1.09) to 2.05
here is the problem
and as long as you dont have an rom with your CID od HARDSPL the phone can only be flashed using my hermes guide if we find the buton combination on breeze
BR
jerpelea said:
im my guide i wrote to use sspl
if you use sspl you finish the 1.34 upgrade from spl 1.09 and is everything fine
if not no
from here you had spl A07 so you could flash ONLY original htc Rus rom
you flashed an older ipl instead
an older ipl that does not load correctly the new spl
the spl can not be downgraded from 1.10(1.09) to 2.05
here is the problem
and as long as you dont have an rom with your CID od HARDSPL the phone can only be flashed using my hermes guide if we find the buton combination on breeze
BR
Click to expand...
Click to collapse
so what you mean now is my IPL 0.9 is WWE and my SPL is 1.09 Qtek A07? and this is causing the problem? so can i flash the IPL on the phone to the lastest one in tri-colour mode so that it can read the 1.09 SPL? can u please provide me with the SPL upgrade file and utility?
any solutions so far? guys?
alexnvidia said:
so what you mean now is my IPL 0.9 is WWE and my SPL is 1.09 Qtek A07? and this is causing the problem? so can i flash the IPL on the phone to the lastest one in tri-colour mode so that it can read the 1.09 SPL? can u please provide me with the SPL upgrade file and utility?
Click to expand...
Click to collapse
no
your problem is that ipl 0.9 cant load spl 1.09
the memory load address differs and it cant load it correctly
i havent found an solution
you need an valid spl loaded to flash
you can try all the original roms (don't edit them)
and see if any one of them tries to push ipl and spl before actualy flashing
also try the official 1.09 spl flash
BR
nowaday, I found this thread useful. thanks
what happened? I was upgrading to futureshock ver. 4 and during phone'd swiched off ... I was looking for original ROM posted here in Breeze forum, but I didn't find it ... after read this 1st post I recoginze, that Czech ROM official is RUS .. that news for me (of course good ).
KITL Hermes
I had ROM 6.1 from Futureshock...still problem with radio (my phone couldn´t accessble but signal icon shows good signal, radio version 1.38.0000), so I decided flash some original ROM. Aftet that my booting stuck on HTC logo or Windows Mobile logo. So I can´t use normal way to flashing. Only from SD card or first turn on phone to boot loader mode and than attach usb cable and start flashing. From SD card (where is renamed ROM BREEIMG.NBH) after enter into bootloader mode start loading and than just turn to trhreecolour menu where is BREE100 - IPL-0.90 and BREE100-1.10.0000 and doesn´t want continue. If I flash ROM via USB cable (first go to threecolour mode, than attach cable) than run ROMUpdateUtility.exe and flash process is being started but always die on 2%, than autoreboot and again stuck on HTC logo.
I tried hard reset, I tried lot of ROM versions HTCRUS, HTCEUR, QTEKEUR, FUTURESHOCK but still same problem during flash ROM stop on 2%...
I tried KITL Hermes unbrick method but same problems like had others on this forum, I don´t know how to turn my MTeoR to KITL debug mode because device is different like Hermes so key combination doesn´t matches with Breeze. MTTY - info 2 command show me CID: waiting interpreter failed...
Any ideas how to back life to my MTeoR?
Can I use application like MTTY? Could me help this program?
Thanks for any help...
DOPOD601
which RUS update rom can i use?thanks
HTCSDOPOD601in眘HTCE
which rom?
can somebody email to : [email protected] or [email protected] ?
thank you