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
Hello,
I`m trying to get latest lvsw wm6 to the device.
I own the phone since today.
I made the following steps:
Execute ROMUpdateUltility (Hard-SPL)
->Next->Next->Update
From: Image Version 1.16.407.2
to: Image Version 1.20
->Next -> Next
On the phone:
Enterbotloader.exe
"blabla"
YES
On the computer:
ERROR[246]: Device not responding
On the phone:
IPL-SSPL by Des
SPL-1.07.ds
ok,
trying to run ROMUPdateUltility again...
next next next... he shows me the progress bar --> finished! YES!
Rebooting the phone --> same software version as before the update?
trying to update for 2 hours... just to use gps as advertised
please help, i tried the official Update from HTC -> successfull but effects! programs, contacts etc still there, same version number!
messiah said:
please help, i tried the official Update from HTC -> successfull but effects! programs, contacts etc still there, same version number!
Click to expand...
Click to collapse
I've the same problem [246] upgrading unofficial roms like
GSM_1.41.00.11
and
ROM_ING_WM6_2.27
The only upgrade I make successfully is original
htcp3600-RUU_Trinity_HTC_ITA_1-23-408-2_103_6275_1-38-00-11_108
what's wrong ?
P.S.
I test it using activeSync 4.2 & 4.5
Messiah..... Have you read the very first post in the LVSW ROM thread?
I am NOT having ago, just checking, seems you may have miss-understood.
Grab ALL 3 downloads listed there.
Apply first one, and yes there IS NO real visible change to the phone apart from it has been hard SPL'd
Now apply Second one, will go through the same process BUT the Radio ROM is changed and updated
Now Apply the Third and WM6 is installed
The failure you describe is the computer dropping Activ Sync and then "seeing" the phone in Bootloader mode, which is why it take 2 bites of the first cherry, after that all "should " be ok.
I managed to get mine on the first attempt so it is "Me Proof"[TM] and "Just Works" (c)..... however report back if this hasnt helped
yeah, the process you described tells me that you've loaded hard-spl on your phone.. that's all. No WM6 yet...
I have the same problem.
I have Hard-SPL'ed my Orange M700
Then reboot and reestablish Active Sync
Then I have updated the Radio Rom
Then reboot and reestablish Active Sync
and now it's 1.41.00.11 in settings/system/device information
but when i apply
20070527_Trinity_WM6_v2.0.1.1 it uploads then i power on my device and it's still WM5 ?
What am I doing wrong??
Any help appreciated.
This may be a stupid question but have you SuperCID your device before running the updates?
If you go:
Start -> Settings
System
Device Information
What does it say under Radio version? (Just checks the second step has been completed successfully).
Also when you enter the bootloader what does it say on the screen?
akirainblack said:
This may be a stupid question but have you SuperCID your device before running the updates?
If you go:
Start -> Settings
System
Device Information
What does it say under Radio version? (Just checks the second step has been completed successfully).
Also when you enter the bootloader what does it say on the screen?
Click to expand...
Click to collapse
I thought you didn't need to SuperCID the device (http://forum.xda-developers.com/showpost.php?p=1245390&postcount=70)
My radio Rom shows 1.41.00.11
TBH I don't know. But it can't hurt to try it, I SuperCID mine and it flashes perfectly each and every time.
I'm merely trying to make suggestions that may get a result.
Oh, you didn't tell me what the bootscreen said and what version of Activesync do you have on your PC?
While doing the SuperCID upgrade i was wondering: After flashing any of the ROMs do I reboot or power On manually or wait for the device to reboot itself as the message in the SupoerCID tool suggests:
If radio upgrade went fine, wait until your phone reboots and make sure
ActiveSync is enabled again (you should see green icon in system tray)
Click to expand...
Click to collapse
Stupid Q: How can i make the boot screen stay long enough so i can write it down?
My ActiveSync is 4.5 on WinXP
Rummage around in Start--> Setting --> device ID, and version and stuff...... they are there and you get the same info as on the boot screen... and it stay on longer ;-)
Sorry if a little vague but away from phone at the moment......... erkkkkkkkk
/me runs off to find it so this may get edited
akirainblack said:
TBH I don't know. But it can't hurt to try it, I SuperCID mine and it flashes perfectly each and every time.
I'm merely trying to make suggestions that may get a result.
Oh, you didn't tell me what the bootscreen said and what version of Activesync do you have on your PC?
Click to expand...
Click to collapse
I didnt Super CID just followed the instructions in LVSW 's first thread, applied each DL in order and "it just works" (c)
Thanks. That's where i got the infroramtion from b4. I just thought it might be different in the boot screen.
I now did the SuperCID unlocking and did the 3 upgrades again. after the 3rd upgrade i still have:
- WM5.1.342 Build 15096.3.0.0
- ROM 1.23.61.5
- Radio 1.41.00.11
Q again: Do I need to wait after the flashing or do i immidiately press power
(that's what i do when it says finish) or do i soft reset? Or what else?
Thanks for your help.
Hmmmmm just got me phone....... dont ask
Right CE OS 5.2.1413 build 17745.0.2.3
ROM 2.0.1.1
Radio 1.41.00.11
Sooooo.......
a) are you using LVSW (just to be sure)
b) have you grabbed the latest version posted on page 1 of the upgrading thread?
c) I let it restart it self after it finished flashing, it then reclibrates the screen etc etc
Also looks like you havent upgraded anything just yet ... follow the instructions to the letter and it "should" be fine
a) yes
b) yes
c) there might be the problem i waited 2 mins ans as it wasn't rebooting i just used the power button. How long should i wait aftr the WM6 install?
I soft reset mine directly after the screen goes black. So that should be fine.
Maybe it has to do with my boot loader:
When i go to bootloader i see:
IPL-0.50
SPL-1.07.0000
then it starts fading quickly. is this normal? I have the same fading effect when i install ste 2 the radio ROM. but i still have the new radio rom on as it displays as 1.41.00.11
I again tried to use the 2.0.1.1 it uploads very quickly (maybe 2min) and then it's still the "orange" screen and WM5 on reboot and i still have all my data.
What a I doing wrong?
No. Mine stays there right up until the upload to the phone starts.
Then I get a grey background with a blue progress bar.
What happens if you run Enterbootloader on the phone. Then connect it to the PC.
Then run the install program on the PC.
The first process didn't work.
You should have:
TRIN100
IPL-SSPL by Des
TRIN100
SPL-1.07.ds
Hmmmmm if all else fails try a hard reset on your phone and see what versions of what you have after that.
Did you use ANY form of unlocking prior to using LVSW rom?
/me suspects this might be casuing issues
The radio rom zoooooomed up to my phone and likewise the WM6
I cannt remember reseting the phone after flashing.... IIRC it just worked as in it finished then re-started and way hey off it went.
Also FWIW I just used the DL's in the thread without bothering with anyother boot loaders etc... ie extract flies in first DL into 1 folders, run them, ditto DL's 2 and 3.
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.
Back again with another question.
I managed to flash another working rom on my phone but,..... (there's always a but )
My phone worked great for a couple of hours and then i froze.
Rebooted the phone and 9 out of 10 times it freezes upon boot (t-mobile screen) So i figured re flash... but once i tried the following problem came up.
It even freezes in the bootloader. Most time when it starts and shows the bootloader screen you see a small short line of colors showing up at the top center of the screen.
So now my question is whether its possible that the bootloader itself is damaged/corrupt and if so is there a way to fix it?
Its prob a stupid question because i have read some treads about that on the forum but I could not find any specific to the Tm Wing / Herald.
And i wanna make sure before i can arrange a funeral for the phone
Thx
Phone info,
Device Name: HTC_p4350
Rom version: 4.12.405.1 WWE
Rom date: 04/09/07
Radio version: 02.83.90
Protocol: 4.1.13.37
ExtRom version: 4.12.405.101
Model No: HERA120
IPL 4.10.0002
SPL 4.10.0000
try to flash to a different rom
cookiemonster55 said:
try to flash to a different rom
Click to expand...
Click to collapse
Thx,
I tried but most rom's won't work in my case.
For some reason only the original t-mobile rom make my WLAN work.
RUU_Atlas_TMO_US_4[1].10.531.3_4.1.13.37_02.83.90_Ship
And the other one that works is
HERALD.ASerg.12.WM61R.WWE but then my WLAN does not work for some reason.
Most other ROM I cannot get to work because it keep saying either image file corrupt or incorrect hardware ID
But even the bootloader keep crashing lots. So i was wondering if the bootloader is a separate piece of software from the ROM that you can flash and possibly also damage.
I have tried lots of solutions but 99% (of what i can find) has to be done with Active Sync working. Mine does not boot 9 out of 10 times so no Active Sync. When it does it crashes pretty fast. (most time when i slide the keyboard out or when i wanna flash it )
But i'm not ready to give up
Hi guys,
I have a weird problem.
As of recently two days ago, my tilt won't take any flashes anymore. I believe with was caused by an action of mine which I tried flashing android from SD to NAND.
Here are the symptoms:
1) After a failed attempt at loading the Android Kernel, I installed the stock HTC ROM (Kaiser_HTC_ASIA_HK_WWE_3.34.721.2)
2) The stock rom flash worked, but any subsequent flash do not work
3) When trying to flash (either from Active Sync or SD Card) it gets stuck at 0%
Current state is as follows:
1) Phone boots up normally with stock rom
2) I can get into Bootloader mode no problem
3) When trying to flash it doesn't work
I have tried several steps in order to recover.
1) Tried to flash Stock rom again (Faillure)
2) Tried to flash HardSPL again (Faillure)
3) Tried MTTY 1.42 (Don't know if Success or Faillure) - I have attached the screenshot below
I have been successful in flashing multiple custom ROMs before, but idiot me wanted to try the android and now I messed my phone up. I guess it's true what they say: "If it ain't broke, don't fix it!"
Anyways...
So it seems to me, the connection is getting done but nothing wants to be pushed.
Here are my credentials:
PC:
XP Service Pack 2
Phone:
ROM Version: 3.34.721.2WWE
ROM Date: 09/30/08
Radio Version: 1.70.19.09
Protocol Version: 25.83.40.02H
HardSPL 3.34
So my question is, do you guys know how to get my Kaiser working again?
Do you recommend in attempting Android on Kaiser again or leave it be?
Any help is greatly appreciated in clarifying this out.
Dave.
Sorry for some reason I cannot post link to images. Does anyone know how to do this as well?
tsiftis21 said:
Sorry for some reason I cannot post link to images. Does anyone know how to do this as well?
Click to expand...
Click to collapse
You can just dont put http or wrap it in code and it's due to limitation on accounts to prohibit spam untill you reach a ceratain ammount of posts.
Screenshots
Thank you for the tip!
Code:
[IMG]http://a.imageshack.us/img806/7494/clipboard01ytn.jpg[/IMG]
[IMG]http://a.imageshack.us/img412/3866/clipboard02ml.jpg[/IMG]
[IMG]http://a.imageshack.us/img192/6405/clipboard03bx.jpg[/IMG]
[IMG]http://a.imageshack.us/img809/4079/clipboard04r.jpg[/IMG]
[IMG]http://a.imageshack.us/img835/3858/clipboard05nr.jpg[/IMG]
tsiftis21 said:
Thank you for the tip!
Code:
[IMG]http://a.imageshack.us/img806/7494/clipboard01ytn.jpg[/IMG]
[IMG]http://a.imageshack.us/img412/3866/clipboard02ml.jpg[/IMG]
[IMG]http://a.imageshack.us/img192/6405/clipboard03bx.jpg[/IMG]
[IMG]http://a.imageshack.us/img809/4079/clipboard04r.jpg[/IMG]
[IMG]http://a.imageshack.us/img835/3858/clipboard05nr.jpg[/IMG]
Click to expand...
Click to collapse
remember to take out your sim and sd card while flashing.
Mr. Clown said:
remember to take out your sim and sd card while flashing.
Click to expand...
Click to collapse
I had tried without the sd card, but I had forgotten to take out the sim card.
I tried without the SIM card and the same result is present. Won't go past 0%.
Any other ideas?
Does any one have any ideas how I can get my tilt up and running again? Any help would be greatly appreciated.
Thank you
I get the same issue...
Word for word, the same as this.
Operator 24.328.1.610
ROM Version 3.28.61.0 WWE
Date 05/02/08
Radio 1.55.16.25
Protocol 25.83.40.02
I've tried several PCs, ActiveSync doesn't work at all, Windows Mobile Device does.
SPL 3-27 is on the phone but I've tried running the others without success. I get up to 17% on any ROM if using JumpSPL1.93-KAIS.exe but that's about it.
This is a work phone which is on the Orange UK network (corporate contract), it's playing silly beggars (not ringing when someone phones, but helpfully telling me I've had a missed call).
According to Orange the only thing they'll do is swap it like for like... but I'm 99% certain the problem is down to the ANCIENT firmware on the phone and Orange have confirmed they've got no plans to update it.
tstaddon said:
Word for word, the same as this.
Operator 24.328.1.610
ROM Version 3.28.61.0 WWE
Date 05/02/08
Radio 1.55.16.25
Protocol 25.83.40.02
I've tried several PCs, ActiveSync doesn't work at all, Windows Mobile Device does.
SPL 3-27 is on the phone but I've tried running the others without success. I get up to 17% on any ROM if using JumpSPL1.93-KAIS.exe but that's about it.
This is a work phone which is on the Orange UK network (corporate contract), it's playing silly beggars (not ringing when someone phones, but helpfully telling me I've had a missed call).
According to Orange the only thing they'll do is swap it like for like... but I'm 99% certain the problem is down to the ANCIENT firmware on the phone and Orange have confirmed they've got no plans to update it.
Click to expand...
Click to collapse
I had this on my tp.
My usb was dying out, i ended up switching my tp with the one of my brother cuz my brother got a galaxy S.
Try if active sync works properly and keeps connected for 15 mins or more.
My connection kept getting lost untill eventually no pc would be able to reconize my phone.