then suddenly the device lock wouldnt respond.
After many attempts to re flash rom it kept getting stuck with the error [262]??
The flash just wont go beyond 11%
the roms i used were from the T-mobile website. The official ones for my fone fone and provider. (UK)
RUU_Hermes_TMO_UK_3.60.110.4_6275_1.50.00.00_108_Ship.exe
i just dont understand what caused this.. now i cant even flash my fone!!
the f**king official roms are f'd up.
I also tried downgrading to HER_TMUK_1211103_1050500_WWE_Ship.exe
that too is from the t-mob website.
can anyne help??
Many thanks.
Update
i got it too flash back wm6 but the fone is really slow and is stuck in airplane mode.
any suggestions ?
ok i updated the spl, i get the NO GSM and i can boot into the OS
what rom should i try??
ok also tried flashing different roms, however it just keeps stopping at 11% just like before.
Someone must be able to help!
Dude see the thread above on this issue. Read through the thread with patience as it has ALL the info you would need in there.
Hermes Unbricking Thread
Hi -
I have and i tried all of the things to get it working again....
the rom flashing always gets stuck around 11% maybe sometimes 16% if im lucky.
and thats any rom, not just t-mobiles. i've tried various roms from this site too. however all of them do not want to go past 11-16%.
Model: T-Mob (UK) Vario II
ROM Before Flash: WM 5 As shipped
Radio Before Flash: --
Bootloader Before Flash: 1.04
Flash failed at: 11% (sometimes 16%)
Flashing ROM: RUU_Hermes_TMO_UK_3.60.110.4_6275_1.50.00.00_108_Ship.exe, HER_TMUK_1211103_1050500_WWE_Ship.exe, RUU_Hermes_DOPODASIA_WWE_3.54.707.3_6275_1.47.00.10_108_Ship.exe
Flashing Radio: ???
Bootloader After Failure: 1.04
CID Before Failure Super CID: --
CID Corrupt: Yes
Radio Corrupt: Yes
GSM Error: Yes
Stuck In Bootloader: Yes
Stuck On Windows Mobile Splash: No
Can boot into OS: No
Tried mtty command set 14 0: no
Tried wiki problem number 5: Yes
mtty info 2 output: CID: ???
Current Device Status: unusable
d4vinder said:
Hi -
I have and i tried all of the things to get it working again....
the rom flashing always gets stuck around 11% maybe sometimes 16% if im lucky.
and thats any rom, not just t-mobiles. i've tried various roms from this site too. however all of them do not want to go past 11-16%.
Model: T-Mob (UK) Vario II
ROM Before Flash: WM 5 As shipped
Radio Before Flash: --
Bootloader Before Flash: 1.04
Flash failed at: 11% (sometimes 16%)
Flashing ROM: RUU_Hermes_TMO_UK_3.60.110.4_6275_1.50.00.00_108_Ship.exe, HER_TMUK_1211103_1050500_WWE_Ship.exe, RUU_Hermes_DOPODASIA_WWE_3.54.707.3_6275_1.47.00.10_108_Ship.exe
Flashing Radio: ???
Bootloader After Failure: 1.04
CID Before Failure Super CID: --
CID Corrupt: Yes
Radio Corrupt: Yes
GSM Error: Yes
Stuck In Bootloader: Yes
Stuck On Windows Mobile Splash: No
Can boot into OS: No
Tried mtty command set 14 0: no
Tried wiki problem number 5: Yes
mtty info 2 output: CID: ???
Current Device Status: unusable
Click to expand...
Click to collapse
Sorry dude, not a good thing to hear but your device has a corrupt CID, not alot we can do about that
Might wanna try looking for a cheap replacment hermes on ebay or something?
mrvanx
I want to know what exactly does a corrupt CID mean?
as you know i have the same problem. Is CID a chip or something?
and about the motherboard replacement issue
I wrote several emails to imate support and told them my problem (SPL 2.03 IPL 1.04 NO GSM stuck at subsplash screen KITL disabled) and told them that everyone tells me that i have to replace my motherboard. they replied me that you DON'T need to replace your motherboard. your device just need to install wm5 in our service center in dubai. unfortunately it is too dificult for me to send my device to dubai.
well, after all failed, i've handed to tMob to fix...
lets see how much they ask for a charge to fix it....
since it was their "official rom" that f**kd it up anyway, i feel like they should give me a new fone.. wishful thinking...
OK, so T-mobile must be reading this thread or something because they just gave me a new Vario II. I believe that they could not re-instate my phone because it had been corrupted so badly.
I am happy with the new phone, seeing as mine was quite scratched up, however, i cannot fathom the fact that tMo put out a corrupt ROM for all their customers.
let this be a lesson to everyone....
dnt f**k with the original ROM!
CASE CLOSED!
congrats on the new phone. score one for the little guy.
d4vinder said:
OK, so T-mobile must be reading this thread or something because they just gave me a new Vario II. I believe that they could not re-instate my phone because it had been corrupted so badly.
I am happy with the new phone, seeing as mine was quite scratched up, however, i cannot fathom the fact that tMo put out a corrupt ROM for all their customers.
let this be a lesson to everyone....
dnt f**k with the original ROM!
CASE CLOSED!
Click to expand...
Click to collapse
Sorry but it was a messed up flash which corrupted the CID on the device, nothing to do with a corrupted ROM image. Suggest a more creful approach to flashing, no running processes....not USB hubs nothing which could mess with the flash at all.
mrvanx said:
Sorry but it was a messed up flash which corrupted the CID on the device, nothing to do with a corrupted ROM image. Suggest a more creful approach to flashing, no running processes....not USB hubs nothing which could mess with the flash at all.
Click to expand...
Click to collapse
on the contrary, i upgraded to wm6 fine, all was good for about 2 days, then one evening went to put in my code to unlock device and it just wouldn't do it, so i decided to reflash after many attempts.
so i did have wm6 running for about 2 days. then it got corrupt. update was succeful.. however the o/s was not stable.
Related
Hello all,
I got a friend of mine who came to me with a device-password locked Hermes, which password he cannot recall (actually his girlfriend...). I said I would be willing to give him a hand to unbrick the device. The problem is that I cannot install any ROM on the device, coz I got an error connection right after the screen goes white and the percentage count should normally start.
So I put the Herm in Bootloader (spl-1.06) and try to flash the OliPro Bootloader. The procedure goes correctly until the step where the upgrade itself should begin, counting from 0%... here, I got:
ERROR [262]: Update error: communication error.
I also tried to flash a ROM directly, but since my Bootloader is 1.06, I didn't find a CID match ROM, so it also failed. The Herm is now not bricked, but it stays at the password input screen, so cannot enter windows properly.
Any help on this?
Thanks,
Ionutz
Interesting since you are trying to go around something HTC probably did not want for people to go around due to security....
agovinoveritas said:
Interesting since you are trying to go around something HTC probably did not want for people to go around due to security....
Click to expand...
Click to collapse
yes, i grih you,and normally i wouldnt even try to do such thing, if it hadnt been for a friend of mine which i know.
besides i would like to learn more stuff about my Herm and this is one thing I havent seen discussed here, although i keep reading xda forums for such info.
just found the solution: i flashed another ROM with same CID since my BL was 1.06, but with BL 1.04. After that, I managed to flash any other ROM and automatically upgrade the SPL to 1.10 or 2.10 Oli accordingly.
If any of you interested and dont get the short explanation, PM me.
cheers,
Io, owner of 2 kicking TyTn's
BL 1.06 didnt allow devices with a different CID to be flashed,
eg: my TyTN had the CID: QTEK001 so i couldnt flash a ROM destined for a device with CID: VODAP001
But BL 1.04 had a bug where you COULD flash any ROM to the device regardless of the CID, the first attempt shows a vendor ID error, then try again and it will flash no problem.
The simplest way I would have got past the device security problem would have been a hard reset.
mrvanx said:
BL 1.06 didnt allow devices with a different CID to be flashed,
eg: my TyTN had the CID: QTEK001 so i couldnt flash a ROM destined for a device with CID: VODAP001
But BL 1.04 had a bug where you COULD flash any ROM to the device regardless of the CID, the first attempt shows a vendor ID error, then try again and it will flash no problem.
The simplest way I would have got past the device security problem would have been a hard reset.
Click to expand...
Click to collapse
I know the details about BL 1.04 vs 1.06, thats why I flashed a BL 1.04 ROM, but with the same CID QTEK_001, or smth.
I have to admit though that I never ever thought about doing a simple hard-reset. I guess it would have been to easy, I jumped to more complicate scenarios. Thanks for the help anyway, i gotta learn that.
Thanks mrvanx, glad I read down the whole thread to the part about a simple hard reset working. I lent my 8525 to a friend, thinking he might be interested in buying it, then he didn't have the money, and after I listed it on ebay today, I charged it up to flash to ATT stock, found it password locked, called my friend a few times just getting his voicemail, so tried flashing, and it said the Hermes wasn't connected to the PC...
I figured there would be a solution here at XDA..and POOF, like magic here it is!
So yes, all I had to do was a hard reset, tested and it works, and it was simple, so thanks again mrvanx, although this thread is very old, glad I found it LOL!
Hi all,
First of all I want to let you know that I did search the forum for a solution. In fact, I found a lot of workarounds but none of them actually worked.
Let me give some details about my problem: My Hermes was working fine. I was running the official WM6 ROM supplied by HTC, so no customized ROM here.
It was going fine until the WM frozed. Then I soft reset the device and after that I never got cellular signal again.
While booting the device I got the message: "no GSM".
First thing I tried was to flash a new radio ROM. In all the attempts the progress bar never moved from 0% and after a while I got the communication problem error.
Then I tried flashing a whole ROM. This time the progress bar stopped at 81%. Apparently in the first 81% it flashes the OS and in the last 19% it writes the radio. Anyway, I tried this a few times and never finished.
In fact, after every communication error message I got stuck in the bootloader screen.
The only thing that works is to flash a ROM WITHOUT the radio!!
Is there anything I can do to save my phone or am I condemned to use my Hermes as a phone-less pda?
I tried everything I found in the wiki/forums, but I couldn't find a working solution.
I suspect that the blocks of memory where the radio data reside got corrupted, could that be possible?
PLEASE HELP!
thanks in advance!
Chris
A similar thing happen to me several months ago. While on a call my phone froze and when I soft-reset it the dreaded 'No GSM' issue appeared. I tried flashing radios/full roms/etc, but nothing worked. I ended up sending my phone to the htc repair facility and they fixed it at no cost. (Other than not having a phone for ~10 days)
Thanks dang, but I don't have a HTC service center where I live (Argentina, LATAM)
I'm faithful that the people of this wonderful community will be able to help me.
Just for curiosity, where did you send your device? Is it in the US?
cheers
sounds like a hardware problem to me...
Hi, there! I found that a lot of us who have bricked our Hermes, don't have a responsive radio bootloader, so when they try to flash a full rom, the progress bar hangs to 13%, or 81%. This is because at that time the flasher is trying to enter the radio bootloader, but because it's corrupted, it hangs. Till today there is no known solution to this one. I'm far away from England where I bought my Hermes, so I'm not thinking to send it back for repair. I'm a programmer, so my knowledge may be usefull here. The first thing I must know is if i can use the "lnb" command without being SuperCID. I mean if there is something like a Hard-SPL with an "lnb" command - (or renamed for security reasons). Maybe there is hope!
How can I try that?
windshearx said:
The first thing I must know is if i can use the "lnb" command without being SuperCID. I mean if there is something like a Hard-SPL with an "lnb" command - (or renamed for security reasons). Maybe there is hope!
Click to expand...
Click to collapse
You can use 'lnb' in HardSPL without having a real SuperCID; however you will not be able to flash a radio with 'lnb' command. The radio chipset has its own bootloader, the and the SPL just acts as a pass-through sending the data directly to radio chipset through the s2410 UART.
I had one device with non-responsive htc_boot and tried all kinds of SPL patches to flash htc_boot again on radio, without success. The only known method to fix this is to take the BGA chip out with hot air and reflash it with special hardware, as it is not common to have this equipment at home, your only option is to send it somewhere to do it for you.
However, I don't want to discourage you to research on it, maybe you find something i didn't
I have a similar problem
I also have a NO GSM and corrupted CID but I can access KITL and use it with PB 5.0. and I followed this steps here but the phone doesnt boot completely. It stops just after the two boot screens on Black WM6 ending on a white screen and the debug window on PB after loading all sort of things begin showing these lines over and over:
@@@@@@ HUB state changes now @@@@@@
[HDC]HubStatusChangeThreadPN TRUE
[HDC]HubStatusChangeThreadPN FALSE
Is there any hope for me? I have the cingular 8525
thanks
Gents, do you think the solution presented in http://forum.xda-developers.com/showthread.php?t=280425 could help me?
Please advise.
thanks again
chriscec said:
Just for curiosity, where did you send your device? Is it in the US?
Click to expand...
Click to collapse
I sent it to the HTC service center in Texas, US.
I just got my replacement from ATT.. Had the same problem. Its a hardware problem.. I wouldnt waste anymore of your time.
first, i'm sorry for my english
I've the same problem with a V1605 (french SFR), i've tried every solution but flash radio doesn't work.
I can flash cooked os without any problem, but it's impossible to put official
It's only a pda now, it's better than a brick
My hernes use to be the same as you 'NoGSM'.I tried to install the official rom,but it 's not work at all.I called to service center ask this problem,so they said that it must be only changed the mainboard. That 's terrible!!!
for ALL -that has NO GSM and stuck at OS boot,
please follow this link -
http://wiki.xda-developers.com/index.php?pagename=PB_KITL_HERMES
the link above help me to bring back my hermes alive (about four hours work).
otoro_315 said:
for ALL -that has NO GSM and stuck at OS boot,
please follow this link -
http://wiki.xda-developers.com/index.php?pagename=PB_KITL_HERMES
the link above help me to bring back my hermes alive (about four hours work).
Click to expand...
Click to collapse
That only works with phones with KITL...which I don't seem to have.
Sorry, how to config the phone with KITL and solve the no gsm problem.
No GSM but when sim inserted
Hi all, First sorry for my bad english.
I also have 2 bricked Tytn Hermes 200. Its not my personal ones Its my company's property, which pple were using this phones. So i'm facin with problem which many pple here having but with exception. both phones having no gsm error when sim inserted but without sim its fine. In other words , device info showing every info including IMEI when sim unavailable. And some times works with sim but after making few call and receiving phone hangs(not system) and goes off from network but anthena signal still showing few bars. I'm thinking maybe the radio hangs totally and goes off, and after soft restart NO GSM. I also tried many flashing upgrading those things nothing can really help me.
When im flashing original rom from HTC (the latest one HTC_TyTN_WWE_3.54.255.3_6275_1.48.00.10_108) its hanging on 12% and doing 3 or 4 times recovery , but its finishes succesfully. So what exactly happening in 12th%?. Maybe its started flashing radio and stopped on bad block ? But then why its finishes succesfully after few retry?. Ok so if any one wants to experiments on the phones except radio welcome. I'll help. And some can give me quick example of how to check bad blocks?.
Tnx.
@akarandomjames -
#1. have you try the comm button+reset button hold for 2-3 seconds
#2. OR try the comm button+OK button+reset button hold for 2-3 seconds
anyway, i'm not sure if KITL is dependend on the ROM version. because when my device was in NO GSM status, SPL is 1.04, HTC bootloader is 0108, and lost SuperCID. Because of my device is still has SPL 1.04, i was able to load WM5 full ROM upgrade using WWE HTC English QTEK_001 2.05.255.1 01/17/07 version (ROM available on this site under HERMES Upgrade link), run it twice. once you have successful load the WM5 ROM then try to do step #1 or #2 above to get KITL USB display on your screen device.
Note: i don't think KITL mode is not available once your device is in Production Mode. anyone here can verify this?
otoro_315 said:
@akarandomjames -
#1. have you try the comm button+reset button hold for 2-3 seconds
#2. OR try the comm button+OK button+reset button hold for 2-3 seconds
anyway, i'm not sure if KITL is dependend on the ROM version. because when my device was in NO GSM status, SPL is 1.04, HTC bootloader is 0108, and lost SuperCID. Because of my device is still has SPL 1.04, i was able to load WM5 full ROM upgrade using WWE HTC English QTEK_001 2.05.255.1 01/17/07 version (ROM available on this site under HERMES Upgrade link), run it twice. once you have successful load the WM5 ROM then try to do step #1 or #2 above to get KITL USB display on your screen device.
Note: i don't think KITL mode is not available once your device is in Production Mode. anyone here can verify this?
Click to expand...
Click to collapse
My device is still SuperCID and I know I don't have KITL...I have SPL 1.04 as well and HTC Bootloader is 0108. I can't install any ROMs with radios as they will hang at 11/12%. I will attempt this "overload" method where it seems some people have had luck with it...after a few recoveries it just finally installs...but I don't think that will be the case.
If I can't fix this in a few days, I will most likely use my warranty or just wait for the Kaiser.
My variation of No GSM
I feel like I have problem 1A...where I am able to boot into OS but no GSM.
I am still SuperCID, SPL 1.04, HTC Bootloader 0108. Last known radio before corruption was 1.48.00.00. ROM where this problem occured: VP3G 3.60.1.
I was not even in the middle of an upgrade...just a soft reset after my phone ALREADY lost GSM capabilities during a tether session. It was stuck with no signal in Phone Mode...I put it in Flight Mode...then tried to move it back to Phone Mode and it wouldn't do so. I soft reset...and the no GSM stuck.
I tried to reinstall radio...many errors...stuck on bootloader. At first, OS's only were not installing as well but I got past that. Now I am able to boot into OS's with limited capabilities...and they will NOT ACTIVESYNC at all. Regardless of how old or new the ROM is. I tried older OS's that I knew worked in the past for me...but they refused to activesync.
Due to that, I am not able to install latest HardSPL 2.10Oli via SSPL. That seems to be the only way to do it according to my knowledge and what I've read. Maybe mtty was capable but I'm not sure. HardSPL 1.40Oli wasn't giving me any problems though, but I just wanted to have the latest one so I can avoid IPL damage.
I can only install anything if I start the device in bootloader...and I'm only limited to the OS since my Radio Bootloader seems corrupted.
I'm not sure what caused the corruption in the first place...but I feel annoying now posting on different parts of the forum with a problem that seems to be growing in the community.
UnBrick the Bricked Hermes with "SPL 2.03 - IPL 1.04 - NO GSM - KITL Disabled"
There are many people have this kind of brick but still no solution for it.
I want to ask the mods to make this thread sticky so if anyone find a sulotion for this type of brick would post it Here.
Summary :
IPL: 1.04
SPL: 2.03
CID: NO CID (Request timeout on mtty.exe)
NO GSM
KITL Disabled
I have tested all the possible sulotions available in the wiki but none of the could help me unbrick my hermes.
P.S. : Please just post your sulotions here NOT your comments like "you should superCID your device first", "It's your fault to use telstra wm6",....
Has anyone found a sulotion for this???
You Pm-ed me asking what to do and i pointed you in the correct direction so why have you started this thread?!
Hermes Unbricking Thread
and
Wiki page: How to unbrick your bricked hermes
EVERYTHING you need is there, you just have to read.
Maybe You do not read my Pm!
I have read all the wiki and thread concerning my problem several times!
The simple truth is that some phones are unrecoverable and have to be sent off for repair. Yours is one of these situations and I very much doubt that this will change. More and more of the pioneering technical guys will have updated their Hermes to another phone and the much admired POF has not been seen since he was accused of stealing...
The tacit feeling is that there is enough information and utilities to prevent people bricking their phones (i.e HardSPL and Update from MicroSD card) so if you do find yourself in this unfortunate position and can not recover your phone then you have to bite the bullet, and be better informed the next time.
POF accused of stealing !!!!????
What's that all about?
I dunno if I have a the same problem, but a similar issue, and trust me I am "PC guys, AMD fanboy, A+ tech:"whatever you wanna call i, I am expanding my horizons and I got into the mobile PC world. Trust me I am NOT Google lazy, i have read and read and read and researched and cross-checked and tried literally everything. I am stuck, I know what is wrong with my Hermes, I know where it messes up, and I DO see threads in other sites with 99.9% the same problem I have and I see NO soultion or anyone who knows or Really wants to help, I feel for Koorosh we need help, I have come to terms if have to send it away to repair. That bugs me I got it Literally 3 days ago, and ONLY used the OFFICAL AT&T WM6 Rom to upgrade
on my bootloader all I see is this........
IPL: 1.04
SPL: 2.03
I have too see in my display
IPL: 1.04
SPL: 2.03
when i can flash radio 1% and restart device!
try it
i also had the same problem.i have resolved using rom update through memory card.look for it in wike section.all the best.try it with original rom that came with the phone.
this will not work in this site again no solution for bricked spl2.03 cid locked
biswajitghosh said:
i also had the same problem.i have resolved using rom update through memory card.look for it in wike section.all the best.try it with original rom that came with the phone.
Click to expand...
Click to collapse
Do you know to read micro sd flash not work when device is not superCID!!!
I maybe have the same issue.
From the HTC ROM I flashed my device to Shannix Grass rom, a few days later I flashed to Satin Black rom, so far so good. After that I want to flash back to Shannix Grass and my deviced crashed. While booting he stuck at the HTC screen.
I tried to hard reset, flash another rom (stuck and reset at 1%), flash the bootloader (stuck and reset at 7%). After the failed ROM flashing I get error 270 image is corrupted.
In mtty I tried to format the NAND, and tried the erase command, nothing worked.
How can I diagnose the problem further. Is it possible to see why the ROM update failed or why the OS won't boot? I did some monitoring with USB monitor but I didn't get results where I get some conclusions of.
---
HTC Integrated Re-Flash Utility, Common Base Version : 1.51d
Device Name: HERM100, Bootloader Version : 2.03
Built at: Jun 16 2007 01:57:22
Copyright (c) 1998-2006 High Tech Computer Corporation
(My device is Herm200)
wow , i have the problem too. i almost live in phoneless .
.
SOLVED !!!!!!!! my phone now works
If your device became inoperable like mine, because i had a failed ROM upgrade,and the device failed to power up i have good news for ya.
MY DEVICE info is as below.
Problem:
Phone does not boot up, and looks like a red brick.
IPL: 1.04
SPL: 2.03
(it always gave an error 206 at 1% of any ROM update i tried)
Solution:
I downloaded the official WM6 ROM from the HTC's website below,
http://www.america.htc.com/support/8525/software-downloads.html
Then reset my device to the bootloader screen.
(holding the 'ok' button and the 'power' button and then using my stylus to push the 'reset' button close to the USB port.
i then disconnect the USB cable from my phone, and the display showed 'serial'.
i then ran the downloaded file, and waited till the collecting information from phone window came up, then i connected the usb cable back to the phone.
it connected, and VOALLA!!!... it started the update.
at least its better to have a working phone(without all the custom stuff), than none.
I hope this was not booring( with all the detail and all), but i hope it will help anyone out there who's device wont bootup.
wow , congraution!
i will take the method. but i wonder should i have to get the "connecting time" in the right point, or the computer can't find my phone??
( hope u know what i mean?)
Um.... i cant say for sure
weyun0513 said:
wow , congraution!
i will take the method. but i wonder should i have to get the "connecting time" in the right point, or the computer can't find my phone??
( hope u know what i mean?)
Click to expand...
Click to collapse
Well.. i can't say you should wait 1 or 2 seconds, but just plug it in as soon as you get that screen. i hope it works for you tooo.
what was ur exact situation beforeu can unbrick ur phone???
IPL?
SPL?
KITL??
NO GSM ERROR?
what was the rom that has bricked ur device??
where did it stuck during the brick phase?
is that 1st splash,2nd splash,...??
This method did not work for me!!!!!
Try the Official Cingular ROM
koorosh_bsboys said:
This method did not work for me!!!!!
Click to expand...
Click to collapse
My Hermes "red hot brick" happened when i tried upgrading to aCRCs_PHKv12r8, from a Schaps_WM6Pro_Hermes_4.31_WWE_Full ROM.
My device is a Cingulat 8525.
The upgrade went to the tricolor screen, and after 1% , my phone magically went off. I tried powering on, but it went to the tricolor screen again showing
IPL 1.04
SPL 2.03
and underneath showed "serial".
me too i'm having the same problem....any experts out there that could help us?
hey, im new but have read many of the pages here. i have burnt roms to my first wiz (G3) unlocked it and everything went well. i came about a wiz (G4) last week wm5 bland rom locked and want to get wm6 on it so after my research i went to the IMEI unlock site and purchased the unlock for the g4
the unlock seemed to go well the first time but, it won't come out of boot loader mode
i ran hornet o.10 for g4 it runs and completed to 100 % and then on reboot it comes up with the boot screen again
IPL 2.21.0001
SPL 2.21
i ran the tnt 1933 rom this morning and it completed 100% but still i have a boot screen
i know im missing something the battery power is fine .
i downloaded the stock rom for cingular but it won't load it has error "(294) INVALID VENDOR"
any suggestions ...
thanks in advance for your input
Airborne_Pathogen said:
hey, im new but have read many of the pages here. i have burnt roms to my first wiz (G3) unlocked it and everything went well. i came about a wiz (G4) last week wm5 bland rom locked and want to get wm6 on it so after my research i went to the IMEI unlock site and purchased the unlock for the g4
the unlock seemed to go well the first time but, it won't come out of boot loader mode
i ran hornet o.10 for g4 it runs and completed to 100 % and then on reboot it comes up with the boot screen again
IPL 2.21.0001
SPL 2.21
i ran the tnt 1933 rom this morning and it completed 100% but still i have a boot screen
i know im missing something the battery power is fine .
i downloaded the stock rom for cingular but it won't load it has error "wrong update utility"
any suggestions ...
thanks in advance for your input
Click to expand...
Click to collapse
Are you sure SPL is 2.21 and not 2.21.0001 as IPL 2.21.0001 ?
Well,if its 2.21 only,the phone's got mixed Bootloaders (IPL/SPL),IPL 2.21.0001 are G4 and SPL 2.21 is G3,I don't know how you got it,but your phone is 'Bricked'
mmm it figures
so it appears there could be a problem with the imei program,
as i said it never came out of boot mode after the unlock
and no errors were shown ...
i could get another and replaced the main board, this one is in new condition
except for the custom bricked rom . in the future i will not play with a g4
thanks for the diagnosis, no way to flash a new spl / ipl ... i did read that if
it booted you could get it back in some chance cases .. i am curious as to how this happened (others not doing this for a hobby could brick there only phone)
step 1 - ran imei unlock
never came out of boot mode after
2- flashing the to above roms said to be G4 safe
i never look to see what the ipl / spl were before
i looked with the wizard tool but didn't save it
well you live and learn, it's good for parts now off to ebay for another crack at it ...
thanks everyone ... the best thing about this phone is everything you can do to it
with help from those who know ...
I recommend trying to flash back to original service provider ROM, then unlock again and try another. As long as you can get to bootloader (tri-color screen), there's still hope for your phone. When it's in this mode, and you plug in the USB, does it say USB at the bottom of the phone screen? If so, you are not dead yet.
Custom build wm6 roms like TNT etc... never Brick a G4 phone as no IPL/SPL is included in them,they are completely safe for G4 devices.What I can gather,it must be the wrong imei unlock code perhaps.
Well,like Myrddin Wyllt said,there's no harm in trying,so if it gets into Bootloaders,try to flash the official rom and if there's an error "wrong update utility" ,replace the RUU in the rom with this RUU and run this RUU,hope it might work.
Myrddin Wyllt said:
I recommend trying to flash back to original service provider ROM, then unlock again and try another. As long as you can get to bootloader (tri-color screen), there's still hope for your phone. When it's in this mode, and you plug in the USB, does it say USB at the bottom of the phone screen? If so, you are not dead yet.
Click to expand...
Click to collapse
yes sir i can talk to the phone from xp pro ..
USB does come up
so i can swap the RRU with the nbf file i need ...
no file name change required on the xxx.nbf file
thanks alot for the(schooling) advise ... i was going to need to brick another to make some book ends... this could save me that
stuck
Airborne_Pathogen said:
yes sir i can talk to the phone from xp pro ..
USB does come up
so i can swap the RRU with the nbf file i need ...
no file name change required on the xxx.nbf file
thanks alot for the(schooling) advise ... i was going to need to brick another to make some book ends... this could save me that
Click to expand...
Click to collapse
ok, i swapped out every RUU i could find i get errors from
read file
invalid vendor id
wrong update utility
im too new to figure this out ..can you extract a ipl / spl from an
official rom and then flash that to get the boot loader's back in sync
i found the att 8125 ipl /spl nbf when i flash, it runs to 100% reboots but no changes
anyone have a link to flashing just the ipl / spl on the g4
i am most thankful for any advise ..
try running the hardspl on phone, it might just work to revert it back to a G4 spl.
Link to HardSPL : http://forum.xda-developers.com/showthread.php?t=332320
and G4 ipl and spl here : http://forum.xda-developers.com/showthread.php?t=342744
Also I paid to the IMEI Check and I had to change the plate because the PDA died as yours. E had not returned to the money of the IMEI Check only reply to me was that it had to change of plate ..... It had the unblocked CID?
bastards
yes they won't return my money ... somehow they bricked my phone
i would use the hard /spl and not the imei those guys are assholes
hello! im not so god at English. so it can be hard to understand what im trying to explanie.
my htc stoped to work as phone a few mouht back. so i bought i new phone,
but now i want my htc back. and i have looked everywhere on this forum for a answer, and ever time i find something it dosent work for me.
in the device info it says that my radio version is None. so thats bad i think?
i tried to flash and put in a new SPL and all of that, but when the phone go to bootloader the connection between the computer and phone disperse. my OS on the computer is win7, and i have tried it on a computer whit xp whit the same results.
so what can i do to make the phone work again?
/Dreamcore
pleas, can somebody help me? i tried everting now, usb monitors and changed spl like a milion times now, what do you need to see my problem?
Model:HTC TYTN
ROM Before Flash:shiped wm6?
Radio Before Flash:??
Bootloader Before Flash: 1.04
Flash failed at:no
Flashing ROM:??
Flashing Radio: ??
Bootloader After Failure:??
CID Before Failure Super CID: ??
CID Corrupt: ??
Radio Corrupt: Yes
No GSM Error: Yes
Stuck In Bootloader: No
Stuck On Windows Mobile Splash:no
Can boot into OS: yes
Tried mtty command set 14 0:no, cant connect to it
Tried wiki problem number 5: Yes
mtty info 2 output: CID:??
Current Device Status: phone dead, but the rest works fine
if somebody wants a usbmonitor screener from my, so pleas help me understand how to do it..
been reading treads for 6 ours now. so pleas, help me
Phone needs...
The Phone needs a new system board! Radio hardware failed!
These phones are getting to be about 5 years old?? or more??
They need new boards!
$90 + shipping online. Or whatever method you can come up with to get one.
Good Luck.