strange CID - 8525, TyTN, MDA Vario II, JasJam Software Upgradin

hi.
i did te command "info 2" and I had back this strange CID:
HTCSF kEØ(HTCEUSB>
Is it strange or is it right?
thanks

Related

hermes crash

hi.
I was uploading my Herm to the rom 1.35.255.102 but my pc had a Fatal Error (blue screen like win98!!!!!!)
the updating process stops and the Herm is stucked in bootloader mode.
i tried to do what is on http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems, but without success.
pleas help me... i'm going mad!!!
i attach the usb monitor output
i can't attach...
why?
I tried also to flash the rom from SD, but i had an "not allow" error.
I tried again to upload the rom and I attach the USB monitor output.
PLEASE HELP ME!!!!!!!!
Is there anybody who could help me?
i did the command "info 2" and I had back this strange CID:
HTCSF kEØ(HTCEUSB>
Is it strange or is it right?
Corrupted CID and bootloader 1.09.
There's any chance you can fix it if you are able to boot into WM5.

Super CID Unlock HTCST-MOB005 ?

I have searched the forums and have found 1 post saying that the T-MOB005 cannot be CID unlocked ? is this still the case as the post was dated Nov2006 ?
I have tried the POF method twice (i.e. Herm CID Unlock v2a). and although it had updated the Radio to 1.16 when i enter the "info 2" command with mtty it brings back
HTCST-MOB005¼ôàŠHTCEUSB>
which means that it is not super cid unlocked.
SPL=1.04
IPL=1.01
I have also checked that the radio has been flashed correctly and it show in device id that the Radio Version is 1.16 so it certainly appears that all has worked apart from the SuperCid
When i put in a sim from another network i get a screen that " I have tried 10 times and to wait till timeout" both buttons are greyed out so i cannot input any numbers.
My T-Mobile sim still works fine.
mtty output
USB>
USB>info 2
HTCST-MOB005¼ôàŠHTCEUSB>
USB>
USB>rtask b
0
0
atvl
0
[email protected]?40
@SIMLOCK= 01
0
atel
0
USB>
USB>rtask b
0
0
[email protected]=0,1,22051978
4
[email protected]=0,2,22051978
4
[email protected]=0,4,22051978
4
[email protected]=0,8,22051978
4
[email protected]=0,16,22051978
4
[email protected]=0,32,22051978
4
Any info appreciated.
Thanks
Are you sure you didn't flash extracted radio 1.16 before and that's why it's showing 1.16 on radio version now?
If your SPL is 1.04 it should work. Try flashing the patched radio again, and capture the flashing process with USB monitor if nothing changes after flashing the radio. This should help to troubleshoot why it is not working on your device.
I will start from scratch again this evening and see if it still gives the same results. I had already flashed my other vario II and this worked with no problems.
Will post my results this evening.
Thanks for your help so far.
I have absolutely no idea how I got the 1.16 radio roms mixed up but when i re-downloaded the unlocker again and used this one, everything unlocked fine first time. info 2 shows supercid.
Lesson learnt i think, dont do anything when you have been working for the last 14 hours as you tend to miss the most obvious things.
Thanks for your help.

Possibly Bricked Hermes - Help Needed!

Hey Gang,
Got a Cingular 8525 with the following symptoms:
1) Was SuperCID + SIM Unlocked
2) Was on Cingular 1.35 + Radio 1.27; attempted upgrade to Cingular 2.06 (.exe, full rom). Upgrade failed at the 25% point.
3) Boot loader got updated to 1.09
4) On power-up, phone displays AT&T splash screen with "No GSM", then hangs at Windows Mobile splash screen.
5) When I attempt to try a new ROM .exe (or re-run the Cingular one), or downgrade the Boot Loader, or anything from the tri-colored screen, the (win32) software returns an "INVALID VENDER" error,
which makes me wonder if the SuperCID status somehow got corrupted.
6) 'info 8' from the MTTY USB serial console shows that all blocks are present and in good condition.
As this is my sole phone, this really leaves me in a bad spot. I'd like to see if there's anything I can do to salvage it before waiting potentially a couple of days for
Cingular to ship me a replacement -- and that's assuming they will.
Any advice would be greatly appreciated.
fyi: USB>info 2
CID: Wait interpreter timeout
HTCSF kEØ(HTCEUSB>
USB>info 2
HTCSF kEØ(HTCEUSB>
USB>
USB>info 2
CID: Wait interpreter timeout
HTCSF kEØ(HTCEUSB>
USB>info 2
HTCSF kEØ(HTCEUSB>
USB>
USB>info 1
USB>info 2
HTCSF kEØ(HTCEUSB>info 3
HTCSH
Is this phone salvageable or not?
Anybody out there? pof? sleuth225?
dolemite said:
fyi: USB>info 2
CID: Wait interpreter timeout
HTCSF kEØ(HTCEUSB>
USB>info 2
HTCSF kEØ(HTCEUSB>
USB>
USB>info 2
CID: Wait interpreter timeout
HTCSF kEØ(HTCEUSB>
USB>info 2
HTCSF kEØ(HTCEUSB>
USB>
USB>info 1
USB>info 2
HTCSF kEØ(HTCEUSB>info 3
HTCSH
Is this phone salvageable or not?
Click to expand...
Click to collapse
ME TOO...
who can help us?
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!
LegolasTheElf 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!
Click to expand...
Click to collapse
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.
Any brilliant ideas, or is my phone effectively bricked beyond repair?
Thanks...
the wiki that LegolasTheElf told you to review does in fact say what to do if you have bootloader 1.09 and can't boot into the OS to run SSPL...
8. If your bootloader version is different than 1.04 then Flash Bootloader version 1.04
on that page, you are told the following:
If no such rom is available for your device or your bootloader version is 1.09, you can buy the Imei-check unlocker to have bootloader 1.04. The HTC Hermes unlocker from imei-check is able to flash the 1.04 bootloader. It transfers the required files to the Hermes via ActiveSync before actually the unlocking key file with your IMEI is requested. The bootloader is flashed on the device after you enter the valid key file (you have to pay for that).
[edit: fixed incorrect bold formatting tags]
[edit 2: well, apparently i can't read. the text i linked definitely says it needs to transfer files via activesync, and of course you can't do that. sorry...been a long day. is it 5pm yet?]
Pretty much. No working OS, hence no ActiveSync. And the CID appears corrupt, so it's not like I can just downgrade to 1.01/1.04 from the boot loader.
Anybody want to drop some science on me? Cause it sounds as though I might be screwed...
yes, u are screwed! just like me! just get another one on ebay!
people keep saying DOWNGRADE to bootloader 1.04! but it' not possible if u have bootloader 1.09 and u stuck at the boot-up screen!
Sam case with me.

Radio Bootloader

Hi, does anyone know how to enter the radio bootloader with mtty? I found some instructions on the net but they dont work, is there any special issue on the nike?
My nike has HardSPL 1.22, radio 1.65.xx and super cid unloked.
You need a MFG SPL which includes the command "rtask"
Do a "rtask a" and you can talk to radio (no echo), to return to SPL type "retuoR".
You can also security unlock your device and enter bootloader directly by pressing send and power on at the same time, or do "rtask a" followed by "setboot 1". Next time device boots up in radio bootloader.
You can then use my FrankenKaiser SPL bootloader for fast loading and booting a ram image. In my opinion a nice way to test Android
jockyw2001 said:
You need a MFG SPL which includes the command "rtask"
Do a "rtask a" and you can talk to radio (no echo), to return to SPL type "retuoR".
You can also security unlock your device and enter bootloader directly by pressing send and power on at the same time, or do "rtask a" followed by "setboot 1". Next time device boots up in radio bootloader.
You can then use my FrankenKaiser SPL bootloader for fast loading and booting a ram image. In my opinion a nice way to test Android
Click to expand...
Click to collapse
Thanks, now i have installed Hard-SPL1.15 MFG, the rtask a is now accepted, and like you said i have no echo... setboot works, but when i type in other commands like help, h, ?, gpio, version i get no outputs... What am i doing wrong? is it still the wrong SPL???
m0rph3us said:
Thanks, now i have installed Hard-SPL1.15 MFG, the rtask a is now accepted, and like you said i have no echo... setboot works, but when i type in other commands like help, h, ?, gpio, version i get no outputs... What am i doing wrong? is it still the wrong SPL???
Click to expand...
Click to collapse
You have a very limted command set if your device is not security unlocked. You find my security unlocker in one of the stickies ..
(then you have echo_on etc, enter a ? for more cmds)
Thank you, finally i get it to work... I have one last question, is there any command to get debugging log or something like that, to see whats going on when wm boots, just like the commands for the diamond?i tried set 1a 0, but it does not work, on the diamond it enables debugging information

problem with cid

Hi
I have strange problem...
When I tried to find out my cid at the cmd its show me at the cmd cid 0202, with the cid getter app its show me cid HTC__001.
I tried to change my cid with cmd command and its don't change...
I don't know what to do :crying:

Categories

Resources