Apologies if covered elsewhere but I didn't know which search terms to use to narrow it down. Yesterday I installed Villain 5.4 using the goldcard method posted elsewhere on this site.
I wasn't happy with the lag so decided to try 5.3 instead. Whilst attempting an install my phone lost USB connection to my PC. I left my phone for 20-25 minutes to see if anything happened but no joy. Took my battery out, replaced it and turned my phone back on to see this:
HERO CVT SHIP S-ON
HBOOT-1.76 0007 (HERO10000)
MICROP-010f
TOUCH PANEL-SYN0104
RADIO-6.35.09.26
Aug 4 2009, 19:43:30
RUU
Is there anything I can do to fix this? Or have I knackered my phone? Any help would be appreciated. Thanks in advance.
Hmmm,... I dont know what the problem is but maybe try this 1st,...
¿kernelpanic? said:
on my cdma hero, following the directions i found online everywhere(hold home and boot) i was getting a HBOOT screen with only an option to erase all settings until i:
1. pop battery
2. reboot while holding vol-down, back arrow and power button
3. this time at the HBOOT screen there is an option to enter recovery mode(i think with a home press) fastboot or simlock
Click to expand...
Click to collapse
This was taken from My Hero is stuck on HBOOT
If still no luck then all I can suggest is searching "Hero + Hboot" to see what else you may find.
Hope that helps
No joy unfortunately, but thanks anyway.
have you tried installing a ruu?
Yep. Unfortunately my phone will no longer connect to my pC.
can you not boot into fastboot and then run the ruu?
Won't allow me to. All I get when I turn the phone on is the following screen-
Do you have adb & fastboot installed on your PC? If so, boot to the bootloader & on the PC see if you get a response to the commandline: fastboot devices
If you do, you can try flashing a recovery image with: fastboot flash recovery <rec.img>
where <rec.img> is the path to the recovery image as stored on your PC. Alternatively, boot directly into said recovery image with: fastboot boot <rec.img>
and from within there, flash a new rom etc.
If fastboot devices gives you no output, look into checking your drivers are all installed correctly (there are a few threads concerning this which refer to setting up adb). Try different cables & PCs. If possible confirm the drivers & cable are ok using a different phone with your existing set up.
If you're still stuck at that point, I suspect you have bricked your phone, in which case best of luck with the supplier not realising you've voided your warrantee.
Hmmmm. Tried a different USB cable, ran RUU again and lo and behold it worked! Thanks for all your replies anyway.
Bricked??
I have the same problem. I have a G2 Touch (Hero on T-Mobile UK) trying to downgrade by using the Gold Card method from a thread on here t=645253 (can't post a link as a new user)
I got an error when running the Generic RUU and my screen is stuck on the following screen:
HERO CVT SHIP S-ON
HBOOT-1.76 0007 (HERO10000)
MICROP-010f
TOUCH PANEL-SYN0104
RADIO-6.35.07.08
Aug 4 2009, 19:43:30
RUU USB
(And 3 skate-boarding androids across the bottom of the screen)
There is no charging light and none of the buttons seem to do anything (tried holding the power down for ages but can't even switch it off)
I've seen threads saying to try re-running the RUU but I can't do this as it doesn't seem to see the phone (get error 170 IIRC) when I do adb devices I get no devices listed.
Can anyone help?? Pretty please....
Craig
I hate to say it but impatience got the better of me and I pulled the battery.
Lucky for me it rebooted straight back with everything intact as before.
Going to do more reading before trying again maybe from XP not W7 this time.
Noticed the battery had taken a major drop maybe 50% when reset. Have I got an iPhone4 battery status symbol???
Craig
CrAiGaT said:
I have the same problem. I have a G2 Touch (Hero on T-Mobile UK) trying to downgrade by using the Gold Card method from a thread on here t=645253 (can't post a link as a new user)
I got an error when running the Generic RUU and my screen is stuck on the following screen:
HERO CVT SHIP S-ON
HBOOT-1.76 0007 (HERO10000)
MICROP-010f
TOUCH PANEL-SYN0104
RADIO-6.35.07.08
Aug 4 2009, 19:43:30
RUU USB
(And 3 skate-boarding androids across the bottom of the screen)
There is no charging light and none of the buttons seem to do anything (tried holding the power down for ages but can't even switch it off)
I've seen threads saying to try re-running the RUU but I can't do this as it doesn't seem to see the phone (get error 170 IIRC) when I do adb devices I get no devices listed.
Can anyone help?? Pretty please....
Craig
Click to expand...
Click to collapse
How much more obvious can I make this, its in the FaQ section. Read my driver guide and follow the bootloader procedure. So simple...
Related
Hello, i updated my magic with the wrong ROM and now nothing works except FASTBOOT (vol down + power). everything else just freezes to the red vodafone screen. What can i do from here?
Here's the info:
Sapphire PVT 32A SHIP S-ON H
HBOOT-1.33.0010
CPLD-12
RADIO-3.22.20.17
Please please with anything on top help?
ok
let's make things interesting. mods feel free to sticky this...
i really need a solution this weekend. i'll send three bottles of the best local beer to whoever solves my problem.
go!
Do you have a Nandroid backup of your original ROM? If so - see here
http://code.google.com/p/android-roms/wiki/NANDROID_Fastboot
If not, I'm sure a quick search will show someone has posted a full backup somewhere on here.
Sorry...didn't notice before that you have the Perfect SPL. I suggest looking here instead -
http://forum.xda-developers.com/showthread.php?t=547133
alexdroid said:
Hello, i updated my magic with the wrong ROM and now nothing works except FASTBOOT (vol down + power). everything else just freezes to the red vodafone screen. What can i do from here?
Here's the info:
Sapphire PVT 32A SHIP S-ON H
HBOOT-1.33.0010
CPLD-12
RADIO-3.22.20.17
Please please with anything on top help?
Click to expand...
Click to collapse
Have done the same ..as you
I used adb get recovery to work again from fastboot
keepitnang said:
Sorry...didn't notice before that you have the Perfect SPL. I suggest looking here instead -
http://forum.xda-developers.com/showthread.php?t=547133
Click to expand...
Click to collapse
tried that, fastboot gives me the "remote: not allow" error.
alexdroid said:
tried that, fastboot gives me the "remote: not allow" error.
Click to expand...
Click to collapse
Yeah...that's because your phone has the Perfect SPL - it won't allow a fastboot connection. The article I linked to shows you how to change the SPL and enable this. Having said that, have you tried stian230's suggestion concerning connecting via adb to restore a recovery image?
Have a look at Amon_RA's thread for his excellent recovery image. This shows how to push the image to your phone and boot to it -
http://forum.xda-developers.com/showthread.php?t=530492
keepitnang said:
... have you tried stian230's suggestion concerning connecting via adb to restore a recovery image?
Have a look at Amon_RA's thread for his excellent recovery image. This shows how to push the image to your phone and boot to it -
http://forum.xda-developers.com/showthread.php?t=530492
Click to expand...
Click to collapse
adb does not recognize my phone (all the drivers are ok, fastboot can see it). all the guides dealing with this said to make sure i have USB debugging enabled, but i can't access my phone to do this.
changing the spl seems to permanently void the warranty (not sure about this)...
K...sorry...this is where my n00bness runs me into a brick wall. The only way I know of to recover in this instance based on what you have said is to go ahead and flash a 'friendlier' SPL. Perhaps someone infinitely cleverer than I knows of another method though?
alexdroid said:
adb does not recognize my phone (all the drivers are ok, fastboot can see it). all the guides dealing with this said to make sure i have USB debugging enabled, but i can't access my phone to do this.
changing the spl seems to permanently void the warranty (not sure about this)...
Click to expand...
Click to collapse
ADB will find your phone if you try a little while.
I promise
Just take it easy do not stress.
Try the phone off. or try recovery even if you do not get in recovery adb believe that it is the in recovery .
certainly sounds a bit strange but I did it that way
i just can't get adb to recognize my device. i tired on xp and 7, unistalled and reinstalled usb drivers and nothing.
all the guides mention tunring on USB debugging, but i can't get into android to do that. all i have is the damn fastboot. is there any other way to turn on usb debugging?
edit: apparently, adb isn't supposed to work in recovery mode. and since i can't use fastboot, because of my SPL, i'm locked out. any other ideas?
does not sound good. but I had the same problem a week ago. I had flashed a ROM and used the wrong port 32A. phone had a "semibriked" I only had access to fastboot and hboot.
I also have perfect spl. But after many attempts the adb found my phone.
I had an empty sdcard with only recovery-RA-sapphire-v1.5.2H.img on it.
is there any other method to change spl, or make fastboot work? the goldcard thing looks crazy hard...
Hi all,
I've got an original Hero, not rooted, still running stock HTC firmware. The recent OTA update that was sent out last week has screwed up my phone. It sits on the HERO boot screen and won't progress.
I figured I might be able to re-install the recovery ROM or something along those lines.
I tried following the instructions on this page:
http://forum.xda-developers.com/showthread.php?t=556038
I can get into the Fastboot screen on the phone fine. The details are:
Code:
HERO CVT SHIP S-ON
HBOOT-1.76.0007 (HERO10000)
MICROP-010f
TOUCH PANEL-SYN0104
RADIO-6.35.15.11
Aug 4 2009, 19:43:30
When I run fastboot devices on my computer it shows the serial number of my phone. However when I run fastboot boot recovery.img it fails with a remote: not allow error message.
Is there anything I can do to get my phone up and working again? I don't really want to ship it back to HTC in the UK (I'm in Australia) if I can do it here myself.
I think running RRU is Your best option.
Cheers!
brat.haneq
I can only get into the Fastboot mode. Trying to run RUU results in a 170 USB Connection Error.
reezyau said:
I can only get into the Fastboot mode. Trying to run RUU results in a 170 USB Connection Error.
Click to expand...
Click to collapse
See this post of mine
Or the entire thread
Hello,
I recently tried to update the spl/radio to use a new rom on my HTC Magic 32A and after updating the spl the phone just hangs on the "HTC Magic" screen. Fastboot or Recovery wont start if I hold the buttons. Was just wondering if it is bricked or if it is possible to fix via cmd or so? I read alittle on jtag but I think if it came down to that Ill just buy a new phone cause this phone is not worth that much trouble.
I rooted the phone a year or so ago. First I had cyanogen but they dropped support so I switched too gingeryoshi but the wifi stopped working. It still connected to tmobile hotspot but I couldnt tether or connect to my wifi. So I thought of putting on Froyodragon. I updated too HBOOT-1.76.2007 but then it just hanged on reboot.
Thanks for any input.
Turn phone off (if you have bootloop then remove battery and place it back after 10-20 sec)
Turn on by pressing Back + Power - it's fastboot-mode
Write first 5 rows of info (all symbols are important)
If you do not have Android Sdk Tools configured - do it
Additionaly search for fastboot.exe - this utility can be absent from sdk tools
Connect phone to pc when it in fastboot-mode
Run
Code:
fastboot getvar cid
fastboot getvar cidnum
fastboot getvar version-main
Sent from my A7-040 using Tapatalk
hello,
I tired back+power, power+vol down, and power+home, they all just sit at the "HTC Magic" screen.
Did you remove battery before try and placed it back? If yes and any combination did not help -> 'brick'. Only JTAG can help.
What ROM did you have before?
And what ROM did you update?
There are no bricked phones when 32A phone updating with 32A official ROM. I don'y understand how you bricked your device.
Even if hboot updated but radio did not - there are some chances to restore...
Tell us how it happened?
same problem
Sir im also facing the same problem like this person is facing:
I guess that I've bricked my HTC magic phone. actually it was working fine but after when i flash Hboot file named (ISO-8859-1__STOCK-HBOOT) on it.
my device stop functioning not any key is working phone its not coming up in hboot loader screen by pressing vol down key+power key, not even in recovery mode. by pressing home key+ power key.
but if i press vol down+power key its not showing any hboot loader screen but if i use command prompt after that and use fastboot devices command its shows the device like in machine language
just like this:
D:\adb\tools>fastboot devices
?╞ñ?¿╥§?4:¶♫ fastboot
here are the details of my mobile. is there any way to fix this issue?
HT03VPB03044
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013
CPLD-13
RADIO-2.22.28.25
OCT 21 2009, 22:33:27
android 2.2.1
baseband version
62.50sj.20.17u_2.22.28.25
kernal version
2.6.32.9-g94b855e
[email protected] #1
buid number
3.56.531.1 CL300801 realase-keys
Sir i've also created gold card on my htc magic phone when it was working properly i've the image of gold card and the same card 512MB micro SD card which i used to create the gold card before but i dont know how it will work on the phone as it is not going into bool loader or in recovery mode.
please help me. i heard that if i got correct RUU file for this device i can troubleshoot the problem but in stock rom no any RUU file is working on it.
I've already tried there RUU ROM on this device:
RUU_Sapphire_T-Mobile_US_2.10.531.3_release_signed_NoDriver
RUU_Sapphire_T-Mobile_US_2.10.531.4_release_signed_NoDriver
RUU_Sapphire_T-Mobile_US_3.12.531.1_FRG83D_release_signed
RUU_Sapphire_TMUS_1.94.531.1_DMD6_release_signed_N oDriver
i request all the XDA member to help and troubleshoot this problem.
regards
Sandeep Deol
5[Strogino] said:
Did you remove battery before try and placed it back? If yes and any combination did not help -> 'brick'. Only JTAG can help.
What ROM did you have before?
And what ROM did you update?
There are no bricked phones when 32A phone updating with 32A official ROM. I don'y understand how you bricked your device.
Even if hboot updated but radio did not - there are some chances to restore...
Tell us how it happened?
Click to expand...
Click to collapse
Yes I removed the battery (only way i could turn it off). I stated most of this info in the first post but Ill try and state specifically what versions I had. When I first rooted I used Cyanogen Rom. It worked fine but they dropped support so I switched too Gingeryoshi. I dont remember what version. I tried to update it too 1.5 first but it didnt work but fastboot and recovery still worked so I decided to switch to a new rom instead and tried Froyodragon but it needed radio 6.35.16.19 and HBOOT-1.76.2007. So I wiped it then I did the HBOOT-1.76.2007 and after installing and rebooting is when it stopped working.
Crap, I just did this too... got a yellow arrow coming from a box onto an Android. I flashed a mismatched 6.35 radio (I guess?).
Can't boot to fastboot--can only boot to blue light mode (trackball+power) and phone will charge if connected by USB--but is never recognized by ADB or fastboot.
jmdsdf said:
Crap, I just did this too... got a yellow arrow coming from a box onto an Android. I flashed a mismatched 6.35 radio (I guess?).
Can't boot to fastboot--can only boot to blue light mode (trackball+power) and phone will charge if connected by USB--but is never recognized by ADB or fastboot.
Click to expand...
Click to collapse
Wait 5-10 minutes, "yellow arrow coming from box" equals unpack and flash. Phone should finish this process.
Try to load into hboot-mode: turn phone off (remove battery and place it back if bootlooping), then turn on by pressing Volumedown + power
In this mode you can flash full official rom in sappimg.zip format (or sappimg.nbh if you have 32b magic)
If phone doesn't load into any mode (except trackball + power) - then you have brick and only jtag can help.
Sent from my A7-040 using Tapatalk
But, it goes to a black screen about ten seconds after that.. sadly I think it needs to be jtagged and i will just give it away for parts.
I also tried the sapphire image trick, no luck.
those all sound like bricks..
problem with 32b - looping after rom.
Believe me, I tried a lot here and on google before posting here.
I tried to install a ROM on my htc magic 32b and certainly was not what I should.
Information from my device:
SAPPHIRE PVT 32B SHIP S-ON G
Hboot-1.33.0013 (SAPP30000)
CPLD-10
RADIO-2.22.28.25
OCT 21 2009,22:33:27
I've read very, very much. I read that I have to change the SHIP for ENG.
Also read about ruu, but I found a will for my device, nor know how to run.
First of all, my phone is only on LOOP. I can normally access the fastboot USB.
But does not accept commands, I believe it because of S-ON.
I do not know how to install an img it to get S-OFF.
Could someone help me get back my life device?
Thank you and with the help of google translator.
huahua!!!!
No one post about my problem...
Hi.
I have an 32A HTC Magic.
I don't know what got wrong but I have NO working ROM on my device.
I have Amon Ra 1.6.2, SPL-OFF, Can get into recovery, can get into Fastboot mode.
Tried flashing some ROMs (they installed 100% completely) but when I reboot the logo just shows "htc MAGIC" and nothing happens.
Please what should I try to do?
Your help will be very much appreciated.
Best regards and sorry for not so great english.
Okay, the thing is:
I can get into the Fastboot screen, but cant get into Fastboot USB mode. So no way of sending ADB commands from my laptop.
Also, no way to get into HBOOT. Even from the Fastboot screen, pressing VOL DOWN doesn't do anything.
What the heck do I do? (
It can be caused by stucked buttons.
Tear down the phone
Clean parts
Assemble all back
p.s. Please post spl-info (first 5 rows in fastboot screen) to avoid software incompatability
5[Strogino] said:
It can be caused by stucked buttons.
Tear down the phone
Clean parts
Assemble all back
p.s. Please post spl-info (first 5 rows in fastboot screen) to avoid software incompatability
Click to expand...
Click to collapse
Thank you very much, here is the data:
SAPPHIRE PVT 32A ENG S-OFF H
HBOOT-1.76.2007 (SAPP10000)
CPLD-12
RADIO-6.35.10.18
Aug 21 2009, 18:19:15
Your help is very much appreciated. Im still stuck with the Magic.. Have tried everything all night
Best regards
Okay, got into HBOOT finally. I then tried flashed the sappimg.zip - but half way through it said invalid model id.
Now I don't have Amon Ra recover, and Fastboot looks like this now:
SAPPHIRE UNKNOWN 32A SHIP S-ON G
HBOOT-1.33.0006 (SAPP10000)
CPLD-12
RADIO-2.22.19.261
May 27 2009 19:06:41
I tried another sappimg.zip and then in HBOOT but HBOOT doesn't find the sappimg.zip anymore.
Any good advice?
OMG, why? Why you did it? You are successfully half-bricked your magic...
update:
1. Make goldcard
2. try to flash 2.53.707.2 SEA WWE test-signed
http://www.4shared.com/file/160198404/66d482a/RUU_Sapphire_HTC_Asia_WWE_2537.html
Cause Im a bit stupid I guess ...
One thing though, I can't even get my computer to recognize my Magic.
Nothing happens when I plug it to the USB port. Not showing up in Device Manager.
I have tried two mini USB cables, same thing.
Guess Im totally screwed?
It is driver-related issue.
You need explore Windows Device Manager (My computer (right click) / Manage / Device Manager)
There must be Android USB Devices in tree.
You can also install USBDEVIEW
32bit OS: http://www.nirsoft.net/utils/usbdeview.zip
64bit OS: http://www.nirsoft.net/utils/usbdeview-x64.zip
p.s.
1. adb must return serial number when phone in normal state after command "adb devies"
2. fastboot must return serial number only in fastboot-mode after command "fastboot devices"
If you see serial number - no problem with adb/fastboot
slkdk said:
Hi.
I have an 32A HTC Magic.
I don't know what got wrong but I have NO working ROM on my device.
I have Amon Ra 1.6.2, SPL-OFF, Can get into recovery, can get into Fastboot mode.
Tried flashing some ROMs (they installed 100% completely) but when I reboot the logo just shows "htc MAGIC" and nothing happens.
Please what should I try to do?
Your help will be very much appreciated.
Best regards and sorry for not so great english.
Click to expand...
Click to collapse
Hi, slkdk,
Have you ever tried the "RUU_Sapphire_HTC_Chunghwa"
(in Traditional Chinese/English)
You just need to connect your phone with PC, turn on the phone with back+power, and then execute the "RUU_Sapphire_HTC_Chunghwa" on PC.
I remember that Sapphire_HTC_Chunghwa will help you with all the radio/SPL/ROM directly back to the Android 1.5 stock.
Good luck!
yuanlin0823 said:
Hi, slkdk,
Have you ever tried the "RUU_Sapphire_HTC_Chunghwa"
(in Traditional Chinese/English)
You just need to connect your phone with PC, turn on the phone with back+power, and then execute the "RUU_Sapphire_HTC_Chunghwa" on PC.
I remember that Sapphire_HTC_Chunghwa will help you with all the radio/SPL/ROM directly back to the Android 1.5 stock.
Good luck!
Click to expand...
Click to collapse
Just note, but not all phones are Taiwanese Chungwa. Installing ROM for another region (mismatching by CID) will raise "cid error" and half-brick.
well, where to start...i bought my MT3G 1.2 brand new because my original decided to have antenna issues (only cell antenna and only inside a building). so fast forward about a year, after rooting my NEW MT3G, I end up letting a friend use it til he can get a replacement for his. I get the phone back (after his dog bit through the screen) and another MT3G that is broke to use as a donor for the screen. swap screens, salvage other parts to fix my original, and boot up the 1.2.
now here is where it gets...interesting...to say the least. unlike before, where it booted to the MyTouch 3g splash screen, it now thinks it is an HTC Magic...i have been looking and unsuccessfully flashing builds TRYING to get it to what it was so i can upgrade the radio and actually know what i have again.
what would cause the phone to think it is a Magic? was it something in clockworkmod? can it be reversed? and why, for the love of god, can i not flash anything but EZGingerbread to it?
Details from the bootloader
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO-2.22.23.02
Oct 21 2009,22:33:27
Any help would be greatly appreciated, cause im about to pull out what little hair i have left >_<
Sounds like fun!
If you haven't done yet: Download Android-SDK and install it (while installing choose Android SDK Tools, Android Platfrom-tools and Google USB Driver).
Connect your phone to usb and start it to bootloader (fastboot usb, back+power). Open a commandline on your computer and go to "...\android-sdk\platform-tools" depending on where you installed it. Then type
Code:
fastboot getvar cid
and
Code:
fastboot getvar version-main
and post the output here.
And please leave your hair where it belongs to! :laugh:
well....that wasnt too bad, i just get <waiting for device> and it hangs
even using CID Getter on the phone itself doesnt give me a CID like it does on my Glacier...i think something may be seriously messed up here >_<
Don't know why it may hang. Does the phone work properly? Maybe just the splash-screen was changed.
Have a look at this thread - there are all official roms for magic and so on. Having a look at your radio the stock-rom on your phone for now may be #56 or #57 (hboot 1.33.0013, radio 2.22.23.02). Only the OTA-update has newer versions.
I don't know if it's worth risking to brick the phone just for this update - only if it works properly at the moment.
It works properly as far as calls and texts and data, but I haven't been able to update the radio or hboot at all, it keeps giving a device id mismatch error
Sent from my HTC Glacier With Beats Audio using xda premium
What you can do:
- if you don't have a custom-recovery on your phone install one - try this guide without the optional stuff
- when done install the stock-rom for your phone (via custom-recovery) from official-rom-thread - i don't know if #56 or #57
- root and install custom-recovery again as shown above*
- then you may apply the OTA-update via custom-recovery (#58 from the official-rom-thread)
*I don't know if it's possible just to flash everything except recovery, then you wouldn't need to root it and install custom-recovery again.
That would be the newest versions for your phone.
I have ClockworkMod recovery already installed, and with this being my backup phone, I wouldn't be mad without root at all, though root is nice, I want it to be right lol
Sent from my Gingerbread on Sapphire
So you can flash your phone to official stock-rom and then update it to newest official-rom as i explained above. Or what should i tell you right now?
I tried to flash a stock rom, but with no success, when I get home I'll try again and post the error log
Sent from my HTC Glacier With Beats Audio using xda premium
SWEET!!! i got the fastboot commands to come through for me
fastboot getvar cid
cid: T-MOB010
fastboot getvar version-main
version-main: 2.53.707.2
And what happens when you try to flash "57) 2.10.531.4 T-Mobile USA DRD35" via custom-recovery (your recovery will be flashed too)?
That is a self installing executable file, when i try to run it, it tells me that it can not communicate with the device, and to make sure that the usb cable is connected and the phone is on, which it is both
so the 57) 2.10.531.4 T-Mobile USA DRD35 flash went finally, turns out, my phone didn't like it too much, because now, i am stuck at the HTC magic splash screen and i think it is bricked
I don't get it, that should have been the correct files for your phone. You're sure that it's a Mytouch 3g 1.2 and not the normal Mytouch 3g?
How did you flash the file?
If you search here you can find "tutorials" how to get the rom-files out of the RUU to flash it in hboot-mode.
Can you get into recovery-mode? What about hboot-mode?
It was a .exe file, so it ran from my computer, and I know it's a 1.2 because I couldn't afford the fender edition lol. Now it just hangs on the splash screen and won't let me do anything at all
Sent from my HTC Glacier using xda premium
I think it would have been better to extract the rom-file and flash it with hboot from sd-card... Then you should have been sure about what he flashed.
Maybe now you got some weird radio-system-whatever-mix and that's why it doesn't start.
Normaly you flashed the correct rom-file for your phone.
What you can try:
- remove battery for some time (5 minutes or whatever) and press power - then get the battery back in and try to start it again
- start the phone with Home+Back+Power or Menu+Back+Power (don't remember), in my case there was a menu to erase cache and so on, maybe this would work for you
- is your phone listed in "fastboot devices" when you power on your phone with Vol down+Power, Back+Power, Power, Home+Power or the combination from above? I read that some people are already in fastboot-mode and have text on their display when they see the logo, shown for example here (they had red text on red vodafone-logo):
http://www.android-hilfe.de/attachm...oter-vodafone-bildschirm-geloest-dsc00624.jpg
If not...
Does bluelight-mode work (i think it's trackball+power)? If so you can get it running with JTAG - you just need somebody who has the equipment and so on. Where are you from?