Related
ok...i got the error from upgrading from 2.17 hacked rom to the 2.26 official rom. tried to read whatever i can but looks like solutions were given for cingular ipl etc...
can someone help me out? when i run the official rom, it updates to 1% and then i get the nbf error. i tried to run loki but mda not recognized by my usb connection.
stuck now...please help!!!
actually, tried to run machinagod's RAPI unlocker..but MDA not recognized as connected...this was part of xelencin's 2.24 rom updater.
please help!!!
Hi,
you must provide more information if you want someone to help you.
First and most important: what does it mean your phone is stuck? Stuck where? Does the screen come on? Can you get the bootloader screen? (for the bootloader screen: hold the two keys on the right side of the device and press shortly the reset hole; if you see the three colors screen then you have the bootloader!)
bye
i get the screen with the 3 colors, and usb at bottom left. when i run the official t-mobile 2.26 update, the screen goes gray and there is a bar with % done. when that kicks in, i get 1% done then it stops. on my computer screen, i get the nbk error, saying the nbk file that i have is not for my phone.
i looked for fixes but all the fixes require activesync connections which i am unable to connect with. just fyi, when i plug in the usb cable to my laptop, i hear the *ding* for usb noting it is connected but the activesync connection is not available.
thanks in advance for your help.
-mike
m3m3 said:
i get the screen with the 3 colors, and usb at bottom left. when i run the official t-mobile 2.26 update, the screen goes gray and there is a bar with % done. when that kicks in, i get 1% done then it stops. on my computer screen, i get the nbk error, saying the nbk file that i have is not for my phone.
i looked for fixes but all the fixes require activesync connections which i am unable to connect with. just fyi, when i plug in the usb cable to my laptop, i hear the *ding* for usb noting it is connected but the activesync connection is not available.
thanks in advance for your help.
-mike
Click to expand...
Click to collapse
Before your battery goes flat i suggest you to re-install your old rom. Don't know why 2.26 is not working, maybe you downloaded a corrupted archive. To install your old rom it is not required that activesync sees your phone. Go in bootloader mode and flash your old rom back.
i dont think i downloaded a corrupted rom file because i downloaded it from 2 different places, one from Tmobile site directly from my tmobile account.
what bootloader program should i use? please advise and location to download...
thanks,
mike
m3m3 said:
i dont think i downloaded a corrupted rom file because i downloaded it from 2 different places, one from Tmobile site directly from my tmobile account.
what bootloader program should i use? please advise and location to download...
thanks,
mike
Click to expand...
Click to collapse
bootloader program??? There's no bootloader program!
What i'm trying to tell you is:
- Your phone is stuck for unknown reasons. In this state you cannot recharge your battery!
- Before the remaining battery charge becomes too few, reinstall your old rom (the one you had before trying 2.26)
- When your phone -with the old rom- will be working again, then you'll have all the time to investigate on the causes of this failure.
- Now hurry up and install the old rom before it's too late (unless you have a second wizard that you can use to recharge the batteries)
To install the old rom you must go to the three-colors screen (the bootloader), connect to USB (but activesync won't start!) and start the rom installer.
bye
risi,
sorry...how do i get to bootloader screen? is it the tricolor screen? has anyone had the same problem that i'm having, going from 2.17 hack to 2.26 official?
what program can i use to load my original rom with?
sorry for the semi-newbie questions...desperate to revive my MDA...
again, thanks.
-mike
m3m3 said:
risi,
sorry...how do i get to bootloader screen? is it the tricolor screen? has anyone had the same problem that i'm having, going from 2.17 hack to 2.26 official?
what program can i use to load my original rom with?
sorry for the semi-newbie questions...desperate to revive my MDA...
again, thanks.
-mike
Click to expand...
Click to collapse
to go to the bootloader screen you must keep pressed the two keys on the right side of the device and, while keeping them pressed, shortly press the reset button. the bootloader screen IS the three colors screen. when you get the bootloader screen, reinstall your previous rom (2.17).
i plugged the phone in the wall charger and the battery charged up all last night so i am not worried about the battery...
i just cannot figure out how to load the old rom i had.
i didnt bring the phone with me to work...i will try to reflash with old rom...for now...i am using my old hp 6315 (yikes! - remember the probs with this phone?? lol
m3m3 said:
i plugged the phone in the wall charger and the battery charged up all last night so i am not worried about the battery...
i just cannot figure out how to load the old rom i had.
Click to expand...
Click to collapse
to load the old rom you must:
- get to the bootloader screen (the three colors one)
- download the 2.17 rom's ,exe archive (download it from the same place you took it last time)
- connect the phone to USB (don't worry if activesync doesn't see it)
- start the rom .exe file
thanks risi...
hope i can get it back man...
m3m3 said:
thanks risi...
hope i can get it back man...
Click to expand...
Click to collapse
I hope so! About the problem you had with 2.26, i don't know why it happened. Is your phone a T-mob USA MDA? If it is not then you must CID unlock it before flashing a different operator's rom.
Bye
yes, it is a tmo usa mda...or i would think so since i bought it from a factory store (not an authorized dealer). anyway man...i will keep you posted...for now, using my trusty hp 6315. lol
Hello,
I have a similar problem. I updated my QTEK 9100
with a T- Mobile 2.24 ROM. Now I need to go back to the original QTEK Rom, namely RUU_Prodigy_2170702_21707102_20710_QTEK_WWE_Ship.exe, but after starting the upgrade process the program refuses to downgrade the device and says get a newer nbf file.
Is there a way to force a downgrade?
Many thanks in advance
Anais said:
Hello,
I have a similar problem. I updated my QTEK 9100
with a T- Mobile 2.24 ROM. Now I need to go back to the original QTEK Rom, namely RUU_Prodigy_2170702_21707102_20710_QTEK_WWE_Ship.exe, but after starting the upgrade process the program refuses to downgrade the device and says get a newer nbf file.
Is there a way to force a downgrade?
Many thanks in advance
Click to expand...
Click to collapse
Is your phone CID unlocked? If so, then you must download the wizard_upgrade_noid tool from the ftp server and use it to install the 'down'grade.
In details:
- be sure your phone has been CID unlocked (and is not a G4)
- download the wizard_upgrade_noid (i don't remember the name exactly) tool
- use winrar to extract the original qtek rom .exe archive
- copy the noid tool to the folder where you extracted the qtek rom
- run it
bye
Hello Risidoro,
At first thanks for your fast answer. Since I have a QTEK I don't beleve it's CID locked. How can I verify if the phone is CID locked? Is there a tool to check this?
I proceeded exactly as you advised. I used Winrar to extract the files and used the Wizard_RomUpgradeUtility_noid I downloaded from the ftp site.
Then I copied the nk.nbf file to the respective folder but the utility after having completed the initial 2 screens says:
ERROR [238] : FILE READ
The update utility cannot open the requested file. Please check your update utility.....
any ideas
Greetings
Hello,
Just some small updates: My phone has currently the Mr Clean 2.3 firmware loaded : IPL 2.24 SPL 2.24 GSM 02.25.11 and OS 2.24.10.1.
Previously I was using RUU_Prodigy_2170702_21707102_20710_QTEK_WWE_Ship.exe and had no problems. After upgrading to xelencin t-mobile based US rom I had trouble when making data transfers over GPRS. Then I decided to test Mr clean. Altough I data transmission has improved a bit it's still not so good as with my original RUU 2.17 release.
Unfortunately I am unable to revert to this version. Also having tried to downgrade using Faria's Custom downngrade file only the IPL was downgraded to 1.05 and the SPL file stayed to 2.24.
I tried then to reapply RUU_Prodigy_2170702_21707102_20710_QTEK_WWE_Ship.exe but I recieved the error message UPGRADE only.
Since apparently this is unstable I decided to reapply Mr Clean and now I have again IPL 2.24 SPL 2.24 GSM 02.25.11 and OS 2.24.10.1.
I suspect that the data problems are due to the fact that these new radio versions are not compatible with our provider. I live in Luxembourg so we use LUXGSM.
Is there a way how I can revert to my old 2.17 software.
Any coments are highly appreciated.
Greetings
Anais said:
Hello Risidoro,
At first thanks for your fast answer. Since I have a QTEK I don't beleve it's CID locked. How can I verify if the phone is CID locked? Is there a tool to check this?
I proceeded exactly as you advised. I used Winrar to extract the files and used the Wizard_RomUpgradeUtility_noid I downloaded from the ftp site.
Then I copied the nk.nbf file to the respective folder but the utility after having completed the initial 2 screens says:
ERROR [238] : FILE READ
The update utility cannot open the requested file. Please check your update utility.....
any ideas
Greetings
Click to expand...
Click to collapse
Hi Anais,
try flashing with the RUU (Rom Upgrade Utility) tools that you find in this thread: http://forum.xda-developers.com/viewtopic.php?t=56088
Download the archive RUU.rar and extract its content somewhere in your PC. Copy in the same location the nk.nbf from the rom and run the .exe.
bye
My wife has a pda2k that the phone quit working on, the pda functions are fine. I was able to upgrade the rom and ext rom but when I try to upgrade the radio it always fails. I have been all over this site and the web nothing has worked to flash the radio. When the flash progarm runs I can see the rom and ext rom versions but nothing is displayed for the radio. I have tried all versions of the roms I have found. Always the same the radio fails, I had to remove the radio rom from the dir. to get the others to update, I then tried the radio alone several times, several different waysand it always fails with various errors.
Thanks for any help.
Husband with a ticked wife please help!
hey,
put ruu.dll, radio_.nbf and MaUpgradeUt_noID in a folder, and run the maupgradeut.exe file...this should upgrade the radio rom only, that is the gsm part.
let me knw whether it workd...
Did you follow the wiki radio upgrade only instructions ? if so what is the error?
I have tried both options listed above, the upgrade starts sits at 0% for several minutes then fails. I do not remember the exact error, this is what happens every time.
put ruu.dll, ruu.conf, radio_.nbf and MaUpgradeUt_noID in a folder, then put your device into bootloader mode by pressing power, reset, and record buttons at the same time, this combination of buttons will show "Serial" and bootloader version on your screen, then place it on the cradle, the "Serial" should change to "USB" then kill activesync (open task manager and kill rapimgr.exe and wcescomm.exe) then start MaUpgradeUt_noID.exe and all should be fine
if an error pops up please let us know
xplode said:
put ruu.dll, ruu.conf, radio_.nbf and MaUpgradeUt_noID in a folder, then put your device into bootloader mode by pressing power, reset, and record buttons at the same time, this combination of buttons will show "Serial" and bootloader version on your screen, then place it on the cradle, the "Serial" should change to "USB" then kill activesync (open task manager and kill rapimgr.exe and wcescomm.exe) then start MaUpgradeUt_noID.exe and all should be fine
if an error pops up please let us know
Click to expand...
Click to collapse
This not working. I Has the same problem. It seems like HW problem. Can't update radio. Then BT address 00:00:00... And now it freez at startup always.
IMHO. This is bad Flash which died.
I am waiting for answer about a month an still haven't one.
SoftService is right, if this type of upgrade fails it may be a hardware issue
I created a directory with the files listed and this is the error message I recieved:
error 114: radio rom update error
Any Ideas?
Thanks
do you have a sx66?
Anybody here has Full flash from PH20B device?
I think fullflash will help us from that problem. But it will the question how to unlock device after this procedure.
And anybody know how to repair IMEI?
Is there hardware specialists?
MDAIIIUser,
Mine is labeled PDA2K. It has quit syncing now. It just seems to be dying a slow agonizing death, and it's taking me with it! I need my electronic brain back.
I have tried all the suggested steps repeatedly. I am getting nowhere. It seems to want to work, it just keeps erroring out.
Thanks.
I had yesterday some problems regarding radio upgrades, which can not be solved by WIKI, so :
my radio rom was TYPEII and the files for upgrade are TYPEI => It can not upgrade
Tryed radio 1.13 TYPEI with TYPEI files and NOID => error
then tryed radio 1.13.1 TYPEII with its TYPEII files and just copied into that dyrectory the NOID APP and it worked (i have just learned that MAUpgradeUT_NOID.exe works with TYPEII RUU.dll and RUU.conf)
I was surprised because i use NOID for upgrading my roms and the files are TYPEI
[SOLVED! See page 4]
I have a Cingular 8125, which I hadn't used for a while (got a Trinity
I am trying to set it up for my wife, so I attempted to unlock it and upgrade to WM6. It is a G3 (it had 2.26). I had upgraded it several times before. but was never able to bring it down to 1.xx in order to unlock it.
So, I started trying to downgrade it, but basically, every time it entered bootloader, it seemed to lose connection and it just timed out on the PC, without ever going to the update bar on the bootloader screen.
I ran IPL_SPL_3.08, and it upgraded fine. But still no go on downgrading.
Finally, I ran Shelltool (bug fixed) and managed to flash to OS 1.5.4.2. But, after the hard reset, it just stays on the blue Cingular screen (showing IPL 3.08; SPL 3.08; GSM 02.47.11; OS 1.5.4.2.)
I have tried flashing again with an original Cingular WWE ROM (RUU_Wizard_225111_22511102_022511_CWS_WWE_Ship_1.exe), with the 1.5.4.2 ROM, even with a WM6 ROM (again, through Shelltool.) I have placed it in a powered cradle, have tried both Shelltool and RUU flashes, both while in the blue Cingular screen, and while in Bootloader mode. I have disconnected and reconnected each time, and rebooted many times (both the Wizard and the PC.) I have hard-reset. I have also tried both with USB selected and unselected in Activesync.
The Shelltool seems to freeze. The official RUU gives "ERROR [296]: UPGRADE ONLY. The NBF file cannot be used for your PDA Phone. Please get another NBF file." Or, alternately, it gives "ERROR [264]: CONNECTION."
Any ideas if this is repairable?
(Or should I cry (or take a hammer to the Wizard:-((
Mine is a 2.25 and it's a G4.. Isnt 2.26 a G4?
I think it was 2.26 (it may have been something like 2.27....), but it definitely didn't have the .000 at the end. I thought that the Wizards without the .000 were G3. Did I screw up?
Madcap180 said:
Mine is a 2.25 and it's a G4.. Isnt 2.26 a G4?
Click to expand...
Click to collapse
2.25.0001 or 2.26.0001 would be a G4
2.25 or 2.26 would be a G3
MacGuy2006 said:
I have a Cingular 8125, which I hadn't used for a while (got a Trinity
I am trying to set it up for my wife, so I attempted to unlock it and upgrade to WM6. It is a G3 (it had 2.26). I had upgraded it several times before. but was never able to bring it down to 1.xx in order to unlock it.
So, I started trying to downgrade it, but basically, every time it entered bootloader, it seemed to lose connection and it just timed out on the PC, without ever going to the update bar on the bootloader screen.
I ran IPL_SPL_3.08, and it upgraded fine. But still no go on downgrading.
Finally, I ran Shelltool (bug fixed) and managed to flash to OS 1.5.4.2. But, after the hard reset, it just stays on the blue Cingular screen (showing IPL 3.08; SPL 3.08; GSM 02.47.11; OS 1.5.4.2.)
I have tried flashing again with an original Cingular WWE ROM (RUU_Wizard_225111_22511102_022511_CWS_WWE_Ship_1.exe), with the 1.5.4.2 ROM, even with a WM6 ROM (again, through Shelltool.) I have placed it in a powered cradle, have tried both Shelltool and RUU flashes, both while in the blue Cingular screen, and while in Bootloader mode. I have disconnected and reconnected each time, and rebooted many times (both the Wizard and the PC.) I have hard-reset. I have also tried both with USB selected and unselected in Activesync.
The Shelltool seems to freeze. The official RUU gives "ERROR [296]: UPGRADE ONLY. The NBF file cannot be used for your PDA Phone. Please get another NBF file." Or, alternately, it gives "ERROR [264]: CONNECTION."
Any ideas if this is repairable?
(Or should I cry (or take a hammer to the Wizard:-((
Click to expand...
Click to collapse
I thought I read somewhere that IPL/SPL 3.08 was a bad convert from a Charmer? If this is true and the Charmer bootloaders are different than the Wizard bootloaders then you may have put yourself in a bind.
The fact that you can still get past bootloader is promising even though the phone doesn't finish booting.
Try flashing from the bootloader (tricolor IPL/SPL screen with USB in the corner)
Thanks. I've been trying to flash in both bootloader or "blue" screen, but no go so far. I just tried the official Cingular .nbf through shelltool: it spent about 30 minutes (in bootloader,) then it stopped responding. It's been doing this forever now.
Any other options left?
MacGuy2006 said:
Thanks. I've been trying to flash in both bootloader or "blue" screen, but no go so far. I just tried the official Cingular .nbf through shelltool: it spent about 30 minutes (in bootloader,) then it stopped responding. It's been doing this forever now.
Any other options left?
Click to expand...
Click to collapse
You CAN'T use shelltool in boot loader mode! it needs the OS and the TRUFFS to read and write to the phone.
Any phone that doesn't go past the boot loader must be fixed with mtty, RUU or SD card...
Thanks for the info. I've been reading about mmty and just downloaded it. But I only have a 4GB card handy (from my Trinity.) I might be able to find my old 2GB one at home.
Edit: Well, this is what I just found: http://forum.xda-developers.com/showthread.php?t=308772&highlight=mtty+wizard
It seems that the IPL_SPL 3.08 might be a real problem. I'll try the card flash, but based on the above thread, I am not holding my breath.
If anyone has a suggestion or a solution, please let me know.
Thanks!
BTW, if the problem is indeed with the IPL_SPL 3.08, then perhaps the suggestion that we upgrade to it (in red) here http://forum.xda-developers.com/showthread.php?t=285435 should be removed, so that we don't get more expensive bricks.
Just to clear up the question about 3.08 IPL/SPL, it isn't an issue at all. It's been tested thoroughly to work well, better than 2.26.
TaurusBullba said:
Just to clear up the question about 3.08 IPL/SPL, it isn't an issue at all. It's been tested thoroughly to work well, better than 2.26.
Click to expand...
Click to collapse
After I unlocked my wizard and before I try any new ROM, I always burn the latest German wizard ROM with 3.08 IPL/SPL "ruu_vario_aku3.3_3822_382120_026911_tmo_de_ger_ship". Then I downgrade the Radio ROM to Cingular 2.25.11. Then I burn my ROM of choice. I've found it works best for me. I've never had a problem with 3.08.
TaurusBullba said:
Just to clear up the question about 3.08 IPL/SPL, it isn't an issue at all. It's been tested thoroughly to work well, better than 2.26.
Click to expand...
Click to collapse
What are the grounds for such a comparison? How to tell that an SPL works better than another? As far as i know the SPL is there to initialise the hardware and to apply security restrictions.
What i'd like to know is if anyone has been successful in downgrading IPL/SPL from 3.xx to 2.xx as itsme once said that there was a security in newer SPL's preventing downgrading (i must look for it...)
cheers
O.K., so maybe it's not 3.08, but something has sure gone bad.
I am trying to use mtty 1.1.42.538, but see only Port 1, Port 2 and USB. When I type in \\.\WSCUSBSH001 I get a message that it cannot open the \\.\WSCUSBSH001 port.
I tried resetting as described in message #7 here http://forum.xda-developers.com/showthread.php?t=264652&highlight=mtty1.42, but nothing happened.
I also tried choosing USB, then typed in r2sd all and again, nothing happened - I just get CMD> again....
So, can anyone think of anything else I can do, or should I just drop it from the 4th floor?
What IPL/SPL values you have at this moment?
mestrini said:
What IPL/SPL values you have at this moment?
Click to expand...
Click to collapse
Both ar 3.08, and I have the feeling that this is why I cannot flash the official Cingular ROM over what I have now. Which makes me wonder: is there an official Wizard ROM file combined with the IPL/SPL 3.08? This may at leas allow me to flash.
MacGuy2006 said:
Both ar 3.08, and I have the feeling that this is why I cannot flash the official Cingular ROM over what I have now. Which makes me wonder: is there an official Wizard ROM file combined with the IPL/SPL 3.08? This may at leas allow me to flash.
Click to expand...
Click to collapse
I had also upgraded my IPL/SPL to 3.08 -- up from the 2.25 on the newest Cingular ROM.
Anytime I've flashed to a WM6 ROM, I've been able to downgrade to the T-Mobile 2.26 ROM -- which changes the IPL/SPL to 2.26 -- with no problems before upgrading to a WM6 ROM. After flashing the WM6, I then go back in and upgrade the IPL/SPL once again to 3.08. It's not failed me yet.
O.K., I've spent the weekend screwing around with this:
If I run any of the original 2.xx ROMs, I get "you need an updated utility" message and then the utility goes to the "Exit" screen. (I am assuming this is because of the 3.08 IPL/SPL.)
mtty tells me I don't have permissions when I tried to load the ROM on a SD card (remember, the 8125 is not SuperCD-ed.). It also does nothing when I type "set 14 0" or "task 28."
But, I found that I can run the XDA Mobile 6 ROM (http://forum.xda-developers.com/showthread.php?t=310954) and it actually starts updating, but when it gets to 99%, the bar on the 8125 turns red and after a while the Update Utility tells me that the Wizard is not connected anymore.
Got very excited when I tried mattk_r's InGeNeTiCs' ROM(http://forum.xda-developers.com/showthread.php?t=311144): it started updating, went all the way to 100%, at which point the bar on the 8125 did turn red, however after a period of time the utility gave me the "Congratulations" message and told me I've successfully upgraded. But then, the 8125 reboots, and unfortunately, it still hangs on the boot screen, and it still gives the OS as 1.5.4.2. Have tried a number of times, always the same:-(
Oh, I tried upgrading the Radio only, and it worked: I was able to upgrade to 02.61.11.
So, does it seem like there is hope, and can anyone think of what else I can do?
MacGuy2006 said:
O.K., I've spent the weekend screwing around with this:
If I run any of the original 2.xx ROMs, I get "you need an updated utility" message and then the utility goes to the "Exit" screen. (I am assuming this is because of the 3.08 IPL/SPL.)
mtty tells me I don't have permissions when I tried to load the ROM on a SD card (remember, the 8125 is not SuperCD-ed.). It also does nothing when I type "set 14 0" or "task 28."
But, I found that I can run the XDA Mobile 6 ROM (http://forum.xda-developers.com/showthread.php?t=310954) and it actually starts updating, but when it gets to 99%, the bar on the 8125 turns red and after a while the Update Utility tells me that the Wizard is not connected anymore.
Got very excited when I tried mattk_r's InGeNeTiCs' ROM(http://forum.xda-developers.com/showthread.php?t=311144): it started updating, went all the way to 100%, at which point the bar on the 8125 did turn red, however after a period of time the utility gave me the "Congratulations" message and told me I've successfully upgraded. But then, the 8125 reboots, and unfortunately, it still hangs on the boot screen, and it still gives the OS as 1.5.4.2. Have tried a number of times, always the same:-(
Oh, I tried upgrading the Radio only, and it worked: I was able to upgrade to 02.61.11.
So, does it seem like there is hope, and can anyone think of what else I can do?
Click to expand...
Click to collapse
If I were you I might be talking to IMEI unlockers. Their process works from bootloader and might be able to get you CID unlocked and fix your corrupted CID area, which seems to be your major problem atm. In any case I would contact them and explain your situation and see if they think their software will unlock your phone. If so then you should be good to go once you CID is "uncorrupted" and unlocked.
one question: can You HARD RESET your device?
Do you have "format failed" message?
if so, you have 50/50 per cent for resurrection.
3.08 is not direct problem here anyway..., version is not exactly matter of problem...
(imei? now? lol)...
Thanks!
Yes, I can hard-reset fine and it claims to reformat fine.
Tx for the suggestion - I will contact IMEI (they unlocked my Trinity before the free unlockers were available
hi guys,
i was excited about the new Radio upgrade, so i tried to flash it. i got an error, because my SPL is 2.05. so i tried to unlock the phone using jerpelea's guide, flash to 1.09 -->success, then WWE (1.10) but an error occured saying invalid vendor ID during WWE flash. now i have SPL 1.09 on my phone and my phone is stuck on the 2nd boot screen of jerpelea's WM6.1 beta 4 ROM. my phone is fully unlocked using jerpelea's unlock guide, that's how i got to install SPL 1.09 successfully. how can i recover my phone? please help.
Update 1: i tried to flash back the original dopod 595 WM5 ROM. i mixed the RUU updater from the latest official ROM with the nbh from dopod WM5 ROM. the flashing works. when it's 100%, the phone reboots and, i got back to the same problem. stuck at 2nd/3rd boot screen. i now have IPL-0.90 and SPL 1.09 on my phone. Please help me to recover my phone. i've tried to hard SPL shown in the wiki guide, doesnt work. says invalid vendor ID crap. i really dont know what to do now.
Update 2: when the device boots, it stucks on the 2nd/3rd boot screen and if the USB cable is attached, for a brief moment, windows can detect the phone and i can even browse the content of the phone from my PC. but after that, the device disconnects itself and just remain stuck at the 2nd/3rd boot screen. the device appears to be totally freezed/hang. even the LED charging indicator will not turn off when i unplug the device from computer
i believe what i need to do now is to make a nbh image that is signed to i dont get any corrupted image message when trying to flash. i used HTC ROM editor to mix and match the SPL and IPL file so that i can downgrade the SPL to 2.05 and upgrade it again later. but i dont know how to sign nbh files.
If i were you I'd use this one =)
futureshock said:
ok i found it i didn't read further the 1st page on sspl thread
edit:
have repacked it with runme.bat and 77.7er SSPL ...
Radinly_1.54.30.10
Click to expand...
Click to collapse
At least I did and it worked =)
and then I'll highly recommend this WIM6.1 release by FutureShock: http://forum.xda-developers.com/showthread.php?p=2094056#post2094056
GL =)
I've GOT IT!!! using various mix and match method, im flashing the phone now!!! fingers crossed it'll boot later
UPDATE: DOESNT WORK! PLEASE HELP
It sure will.. Even I got it to work really fine
crap!. doesnt work. it's still SPL 1.09 and stuck at 2nd boot screen.
is there a ROM editor that works for meteor? can someone please suggest one that can be used to sign the nbh file.
jerpelea, or futureshock, please help
not good news
I think I know what do you mean. My device was in very same state like yours few mnonths ago.
Try to run mtty and the command "info 2" without quotes.
Do not forget to disable USB on activesync settings before running mtty.
You will get an answer which includes the CID of your device.
If not (this was my case), you have to send it to the repair center probably.
My device CID was Qtek_A07 (RUS) and I have tried to instal the first official WWE 1.34 ROM update (combined from SPL.nbh and ROM.nbh) and it replaced only the SPL, and the ROM update crashed.
There was not way out so I sent it to the repair center.
The WWE images are expecting the device with CID Qtek_Z12.
PiGeonCZ said:
I think I know what do you mean. My device was in very same state like yours few mnonths ago.
Try to run mtty and the command "info 2" without quotes.
Do not forget to disable USB on activesync settings before running mtty.
You will get an answer which includes the CID of your device.
If not (this was my case), you have to send it to the repair center probably.
My device CID was Qtek_A07 (RUS) and I have tried to instal the first official WWE 1.34 ROM update (combined from SPL.nbh and ROM.nbh) and it replaced only the SPL, and the ROM update crashed.
There was not way out so I sent it to the repair center.
The WWE images are expecting the device with CID Qtek_Z12.
Click to expand...
Click to collapse
this is what i get with mtty
Cmd>info 2
CID: Wait interpreter timeout
HTCSF kEØ(HTCE
what's the meaning of this? is there any hope?
i ran the format command anyway. device reboots and still stuck at the windows mobile logo screen. what should i do next?
alexnvidia said:
this is what i get with mtty
Cmd>info 2
CID: Wait interpreter timeout
HTCSF kEØ(HTCE
what's the meaning of this? is there any hope?
i ran the format command anyway. device reboots and still stuck at the windows mobile logo screen. what should i do next?
Click to expand...
Click to collapse
why did you format ?
try to reflash 1.09 spl
and after this wwe one of 1.34 roms to get 1.10 spl
If you bothered to read the Wiki, you would have seen this:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems#problem5
If you can't bother to read the wiki, don't play with roms!
Actually, I did read that, and a couple of problems:
1) Boot Loader is 1.09
2) OS won't load, so can't use any of the ActiveSync-based methods for downgrading to an older version, such as 1.04.
3) CID appears to be corrupted, as per the earlier output pasted.
from other forum ...... so read wiki
http://wiki.xda-developers.com/index.php?pagename=PB_KITL_HERMES
but i dont know if you have the knowledge
jerpelea said:
If you bothered to read the Wiki, you would have seen this:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems#problem5
If you can't bother to read the wiki, don't play with roms!
Actually, I did read that, and a couple of problems:
1) Boot Loader is 1.09
2) OS won't load, so can't use any of the ActiveSync-based methods for downgrading to an older version, such as 1.04.
3) CID appears to be corrupted, as per the earlier output pasted.
from other forum ...... so read wiki
http://wiki.xda-developers.com/index.php?pagename=PB_KITL_HERMES
Click to expand...
Click to collapse
jerpelea: First of all I will say thank you for taking all that time you do spend on the ROM cooking/building/making/what-ever-is-the-right-name and I/we really appreciate it!
jerpelea said:
but i dont know if you have the knowledge
Click to expand...
Click to collapse
I think that comment was really unnecessary!
As a n00b I know how hard it is to understand what’s happening. I did read the wiki’s and still I didn’t get HOW TO upgrade a ROM until I found a great post in FutureShock’s thread
darkDirk said:
First of all:
It's fantastic what you are doing with wm6.1 and the Breeze, Futureshock !
I am new and trying to upgrade it myself, but at first I didn't have any luck.
Here is a simple newby step-by-step manual:
- Download and extract a MTeoR-FutureShock-WM61-xxxx.x.rar
- Check your Mteor battery in more then 50 % full
- connect the Mteor to the computer via usb and check if Activesync works
- go with DOS (cmd line) to the directory and start runme.bat
- On the Mteor press camera and powerbutton at the same time.
- then immediately press any key on the computer to continue the batch script.
- now you should see the 3-color bootscreen
- press any key to start the rom-update program and follow its directions.
When the update is finished (in less then 5 minutes), then wait untill the first boot is complete.
If you don't get the 3-color bootscreen or you the update on the Mteor stays on 0 % and the rom-updater displays an error, try testing this:
On the Mteor start the explorer and in the root directory (press UP once) find SSPL.EXE en start it.
If the Mteor won't start the program and there is an error like "insufficient trustlevel".
You need to remove the application lock on your Mteor.
Run SDA_ApplicationUnlock.exe on your PC with Activesync working and then install SP_AllowCertificateInstall.cab on the Mteor.
You will find those two in the .rar in ".\opt Software\Unlock Tools"
Then redo from the start.
Then, Have fun !! (Futureshock & DarkDirk)
P.S. works on a BREE100 with IPL-0.90 and SPL-2.05.
Click to expand...
Click to collapse
But I still do not know what SSPL, SPL, IPL or whatever there is does to me or/and the phone.
Anyway. Thanks for all the work.
if someone has a corrupt CID just send me an pm...
jerpelea said:
If you bothered to read the Wiki, you would have seen this:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems#problem5
If you can't bother to read the wiki, don't play with roms!
Actually, I did read that, and a couple of problems:
1) Boot Loader is 1.09
2) OS won't load, so can't use any of the ActiveSync-based methods for downgrading to an older version, such as 1.04.
3) CID appears to be corrupted, as per the earlier output pasted.
from other forum ...... so read wiki
http://wiki.xda-developers.com/index.php?pagename=PB_KITL_HERMES
but i dont know if you have the knowledge
Click to expand...
Click to collapse
with all the respect what you do for this community, isn't taht you who advice us to update the SPL before trying your images?
in this thread http://forum.xda-developers.com/showthread.php?t=384398 you should probably higlight that the update should be done only on WWE devices.
jerpelea said:
If you bothered to read the Wiki, you would have seen this:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems#problem5
If you can't bother to read the wiki, don't play with roms!
Actually, I did read that, and a couple of problems:
1) Boot Loader is 1.09
2) OS won't load, so can't use any of the ActiveSync-based methods for downgrading to an older version, such as 1.04.
3) CID appears to be corrupted, as per the earlier output pasted.
from other forum ...... so read wiki
http://wiki.xda-developers.com/index.php?pagename=PB_KITL_HERMES
but i dont know if you have the knowledge
Click to expand...
Click to collapse
i did try to read as much as i could but apparently i didnt come across that. when i flashed to SPL 1.09, the device booted up just fine. it is when i try to update to WWE 1.10, the update process failed and bricked my phone. for your information, i was following the exact steps described by you in your unlocking/SSPL guide. you mentioned upgrade to SPL 1.09, then WWE 1.10. this is exactly what i did. i dont know what went wrong. im sure if im as knowlegable as you are, i wouldnt have screwed up my phone. my bad.
just to be fair, your method did work when i updated my dopod 595 (WWE device) to your WM6.1 beta 4 ROM. but i never upgraded my SPL to 1.10. i only thought of upgrading SPL when you posted the new radio release and that's where i screwed up.
anyway, what is important here is, is my phone unrecoverable? im reading the links you posted as i type, and i'll give the methods. maybe based on your experience, you could suggest some ways to do it. thanks.
alexnvidia said:
hi guys,
i was excited about the new Radio upgrade, so i tried to flash it. i got an error, because my SPL is 2.05. so i tried to unlock the phone using jerpelea's guide, flash to 1.09 -->success, then WWE (1.10) but an error occured saying invalid vendor ID during WWE flash. now i have SPL 1.09 on my phone and my phone is stuck on the 2nd boot screen of jerpelea's WM6.1 beta 4 ROM. my phone is fully unlocked using jerpelea's unlock guide, that's how i got to install SPL 1.09 successfully. how can i recover my phone? please help.
Update 1: i tried to flash back the original dopod 595 WM5 ROM. i mixed the RUU updater from the latest official ROM with the nbh from dopod WM5 ROM. the flashing works. when it's 100%, the phone reboots and, i got back to the same problem. stuck at 2nd/3rd boot screen. i now have IPL-0.90 and SPL 1.09 on my phone. Please help me to recover my phone. i've tried to hard SPL shown in the wiki guide, doesnt work. says invalid vendor ID crap. i really dont know what to do now.
Update 2: when the device boots, it stucks on the 2nd/3rd boot screen and if the USB cable is attached, for a brief moment, windows can detect the phone and i can even browse the content of the phone from my PC. but after that, the device disconnects itself and just remain stuck at the 2nd/3rd boot screen. the device appears to be totally freezed/hang. even the LED charging indicator will not turn off when i unplug the device from computer
i believe what i need to do now is to make a nbh image that is signed to i dont get any corrupted image message when trying to flash. i used HTC ROM editor to mix and match the SPL and IPL file so that i can downgrade the SPL to 2.05 and upgrade it again later. but i dont know how to sign nbh files.
Click to expand...
Click to collapse
run terratem
type info2
if it sais A07 then just flash rusian 1.34 rom and enerithing will be fine
application unlock it
run sspl 77.7
flash wm6.1
if it says enithing else you need to locate your original rom
till now i found that it sais a07 in most cases
BR
alexnvidia said:
i did try to read as much as i could but apparently i didnt come across that. when i flashed to SPL 1.09, the device booted up just fine. it is when i try to update to WWE 1.10, the update process failed and bricked my phone. for your information, i was following the exact steps described by you in your unlocking/SSPL guide. you mentioned upgrade to SPL 1.09, then WWE 1.10. this is exactly what i did. i dont know what went wrong. im sure if im as knowlegable as you are, i wouldnt have screwed up my phone. my bad.
just to be fair, your method did work when i updated my dopod 595 (WWE device) to your WM6.1 beta 4 ROM. but i never upgraded my SPL to 1.10. i only thought of upgrading SPL when you posted the new radio release and that's where i screwed up.
anyway, what is important here is, is my phone unrecoverable? im reading the links you posted as i type, and i'll give the methods. maybe based on your experience, you could suggest some ways to do it. thanks.
Click to expand...
Click to collapse
it depends on the info displayed on terraterm
for A07 you can use the russian rom to recover
this is what i got from terraterm. same as mtty.
Cmd>info 2
CID: Wait interpreter timeout
HTCSF kEØ(HTCE
Cmd>
i did flashed back to my original ROM after the first stuck in WM screen incident. and amazingly the flashing process works after several mix and match. after the original (WM5) ROM completed flashing, my IPL is downgraded back to 0.9 and SPL is still 1.09, and im still stuck at the WM logo screen (this time WM5 logo).
terraterm is a tool like mtty
what is your orignal rom??
just try to flash over sdcard... (look in wiki4more infos about that)
futureshock said:
terraterm is a tool like mtty
what is your orignal rom??
just try to flash over sdcard... (look in wiki4more infos about that)
Click to expand...
Click to collapse
i tried SD card flashing too yesterday. it says not allowed. i have already flashed over the original dopod 595 ROM and my phone is now WM5. the flashing is 100% successful, but it is still stuck at the second boot WM screen.
i think im in a really screw up position now. i have SPL 1.09 and IPL 0.9. i dont know what is corrupted now. is it the CID? SPL?
cid you can check with mtty and info 2...
if that so... just do what i have wroted in pm...
you could also just try the old htc rom (w. SPL 2.05)
futureshock said:
cid you can check with mtty and info 2...
if that so... just do what i have wroted in pm...
you could also just try the old htc rom (w. SPL 2.05)
Click to expand...
Click to collapse
both mtty and terraterm give me the same msg when i type info 2. it says time out (refer above for exact error message).
the original dopod 595 rom has SPL2.05. and it was successfully flashed into the phone. when the phone reboots, it is still stuck at 2nd boot screen (WM logo). i checked, the SPL is still 1.09, but IPL has been downgraded to 0.9.
Hello.
First, sorry for my bad English (French guy).
I make a SD flash with a Rom, and something strange occurs: my radio rom version change to 1.16.00.00. I try (always SD flash) to change it with a newer, the process looks good (the download bar increase, the device reboot) but the radio rom version always the same. I try to change OS rom, no problem. I try to change SPL version, impossible: all process executed without error but at the next load of SPL (power-camera-reset) the version is always the same (1.30 Olipro).
I try with another computer (Win XP pro SP2) and with activSync, the problem was the same !
And I try with several rom version, idem.
So to be quick
OS ROM change: no problem
SPL change: impossible
Radio ROM change: impossible
If someone have an idea, I will be very happy
Bye
I find the solution !
Usually, I toogle in SPL mode manually.
The soluce for me was to downgrade the SPL (1.30 to 1.20 olipro) but let the RUU launch is own SPL.
And after, the SPL version was 1.20 and I can change ROM, Radio ROM etc...
[Mode happy ON]
Bye
Hi, can you post the procedure please? I have the same problem!!!
But your pda statup?
Thx
Roby
i don't understand how that is accomplished.
i have read through the trinity guide and that is what they recommended
My trinity has been flashed with 1.3oli and a custom rom but it hangs at the start up page.This makes the device disconnect from the USB.
so how do i let the RUU launch its own SPL?
It is supposed to make the device go into bootloader right? i cant access that since it is hanged
Advice please
Hi bigrockshow,
it is impossible, in this condition that rru launch its SSPL, and it is ipossible to use the method sspl.exe ....
I think that the only way is the splxploit but I don't find a sspl file to load on p3600 with splxploit
anyone have it?
I've exactly the same problem, oli 1.30, I can flash OS roms with no problem but I can't get a radio rom to go past 0%.
I've tried the spl exploit to boot into spl 1.07, I've tried going into the bootloader manually and I've tried letting the RUU load the SPL, no matter what I do I can't shift the radio from 1.16?
Any ideas?
mine is just wierd...
i used SPLxploit and the spl jumps to 3.03...
tried to flash hard SPL and its has error 270...
so i did SPLxploit again...
shows SPL 1.20 now
Tried to flash another rom and it still doesnt work..
did i miss something or is my dopod screwed...
You can't upgrade to the 1.56.70.11 Radio with Olipro 1.3. It looks like it's worked and gets to 100% on mine but doesn't actually change anything. I ended up using another HardSPL (can't remember the name now) to get the 1.56.70.11 Radio on there.
I looked for ages for a version of Olipro 1.2 but couldn't find one anywhere. Apparently it works ok with that version.
Sometimes these threads are really hard to follow when they get massive and the author updates the first posts and over writes stuff. I think they should all keep old stuff in there and just add too it instead of replacing information.