I've had my htc panache (canadian mytouch 4g) for just one day, and it blew its fuse at me. When I went to sleep, it worked fine, but when I woke up, the screen was black and nothing was working. I pulled the battery out and plugged it back in, and now the phone is stuck at the HTC boot screen. I can get into hboot, but some options just don't work, and hangs the phone:
-REBOOT BOOTLOADER (from FASTBOOT menu)
-FACTORY RESET
-IMAGE CRC (hangs on "Calculating... please wait")
-RECOVERY (shows an image of two curved arrows with a regular arrow within, over a tilted cellphone, then the image is reversed, and the screen goes black and the phone vibrates exactly 7 times.)
I tried using the RUU, but my computer won't detect my phone either in hboot or recovery (not that it has the time to detect my phone in recovery). Perhaps I am missing drivers? the device manager shows the phone as a generic "USB Device".
I've tried to get into download mode, but the only other button combination aside from volume down + power that did anything was power + back button, and that brought me to hboot into the fastboot menu.
I tried to update the phone by putting the latest pd15img file from the wiki onto the sd card but after it scans the file, the phone doesn't ask me if I want to update. it just goes back to hboot, and rebooting hboot does the same thing.
How can I get into download mode, anyway?
EDIT: just found hboot drivers. something that works, for once.
Adb maby?
Sent from my LG-P970 using xda premium
wouldn't have been able to use adb if the phone wasn't detected, now was it?
anyway, I found some hboot drivers that seem to work. I'll try the ruu first.
Correct me if I'm wrong, but if I remember correctly the 7 vibrations while trying to enter recovery signifies hardware failure...
Sent from my myTouch 4G using XDA Premium HD app
Ok so... I managed to get the phone charged, and yet RUU still tells me my phone battery is charged at less than 30%, and I can only exit. what gives? Is there a way to bypass that?
(By the way, the hboot drivers I used were from a website called unrEVOked. perhaps these were for another model? where could I get hboot drivers for my phone?)
As for the hardware failure thing, I'm not buying it. at least not yet. If it trully were a hardware failure, the phone wouldn't boot, eh? I can get to hboot and fastboot and fiddle around for a bit, and recovery works for around 10 seconds before it goes blank at me.
So ADB doesn't see my phone but fastboot does. seeing how switching my phone to the fastboot menu installed htc's own drivers right away, I'm not surprised.
Where are the adb drivers for the glacier/panache/mytouch 4g? the only ones I could find are for motorola phones.
EDIT: "C:\sdk-tools>fastboot -p SH16KRM01484 -w
erasing 'userdata'... FAILED (status malformed (1 bytes))
finished. total time: 0.016s"
Try this thread for adb setup:
http://forum.xda-developers.com/showthread.php?t=928370
Also, did you have (flash) a recovery installed? If I remember right, a triangle around a phone when you enter recovery from hboot means you didn't have one installed/flashed. I also remember reading that 7 vibrates mean hardware failure. There are lots of phones that had failed emmc's and would still boot but get stuck at the splash screen. Are you verifying the md5 when downloading ruu?
http://www.htc.com/us/support/htc-mytouch-4g-tmobile/software-updates
That link is to the HTC drivers you're looking for. Once you get it set, you should be able to flash the RUU and I would suggest making sure you have a recovery flashed as well...would help a lot right now if you could at least get there.
Chomanator said:
http://www.htc.com/us/support/htc-mytouch-4g-tmobile/software-updates
That link is to the HTC drivers you're looking for. Once you get it set, you should be able to flash the RUU and I would suggest making sure you have a recovery flashed as well...would help a lot right now if you could at least get there.
Click to expand...
Click to collapse
It's the third driver I download, one was called htcdriver.exe, the second one was the same with a version number, and the third, this one, and none work. nothing happens when I click on them. on the task manager I see the process starting and just quitting for no reason.
I'm starting to think technology as a whole is against me.
I'm gonna try the drivers included with pdanet.
So after getting the right adb drivers...
"C:\sdk-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\sdk-tools>"
nothing.
anyone?
(EDIT: fastboot started working. here's what getvar all gave me: )
C:\sdk-tools>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 0.89.0005
INFOversion-baseband: 26.09.04.26_M
INFOversion-cpld: None
INFOversion-microp: 0429
INFOversion-main: 2.10.1530.1
INFOserialno: SH16KRM01484
INFOimei: 357935045141682
INFOproduct: glacier
INFOplatform: HBOOT-7230
INFOmodelid: PD1510000
INFOcidnum: VIDEO001
INFObattery-status: good
INFObattery-voltage: 4183mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 6a4abc53
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.047s
I'm not sure if this can be helpful or not, but here.
It don't appear to be bricked...try flashing 4ext recovery.
Sent from my HTC Glacier
I tried to flash the phone using one of the pd15img.zip files, but I got the following error: "CID Incorrect!"
Does CID stand for Carrier ID?
So it shows you have s=on and latest gb hboot, so assuming you were running the stock rom. What was the last thing or things you did before plugging out in to go to sleep? Have you tried to select factory reset? If you only had the phone for 1 day, why don't you take it back to where you bought it?
ronin178 said:
So it shows you have s=on and latest gb hboot, so assuming you were running the stock rom. What was the last thing or things you did before plugging out in to go to sleep? Have you tried to select factory reset? If you only had the phone for 1 day, why don't you take it back to where you bought it?
Click to expand...
Click to collapse
Nothing. two hours before I went to sleep, I installed a few games and widgets, and everything went fine. I just quit what I was playing (some 3d racing game), put the phone on charge and went to bed.
Factory reset does nothing (the phone just hangs), and I can't return it because I got the phone from someone else (I doubt he's somehow responsible for this seeing how it's not the kind of defect you can just hide like that) and there was no warranty anymore on the phone, so I can't have it exchanged.
If I really can't do anything with that phone, I'll just sell it for parts on ebay I guess. but for now, I'm not giving up. I'm downloading the videotron ruu again, and will just put the zip file it extracts onto my sd card and rename it accordingly. Hopefully that will work.
I've downloaded the ruu, copied the rom.zip file from the temporary folder into my sd card, renamed it to pd15img.zip, and let it load in hboot. it asked me if I wanted to update, said yes, and it's stuck. I think it IS bricked, after all.
Parsing... [SD ZIP]
[1] BOOTLOADER -Updating
[2] BOOT
[3] RECOVERY
[4] SYSTEM
[5] SPLASH1
[6] USERDATA
[7] TP
[8] TP
[9] RADIO_VZ
[10] RADIO_CUST
Do you want to start update?
<VOL UP> Yes
<VOL DOWN> No
Update is in progress...
Do not power off the device!
Click to expand...
Click to collapse
It's stuck at where -Updating is, next to BOOTLOADER. I've left it there for 20 minutes now, and it hasn't budged. and I know that bootloaders aren't that big, unless the update is doing something fancy that makes it super slow, so... ****.
Is there a way to switch the phone to download mode? not hboot or recovery, but download mode.
adb just won't detect my phone :c
will somebody tell me how to put that phone into download mode?
Which RUU are you using?
Sent from my myTouch 4G using XDA Premium HD app
Related
Hey all. My friend gave me her HTC Magic (Vodafone) today asking if I could fix it. I took a look, and the problem is that it always boots up in recovery mode (white screen, skating androids, etc). Usually this isn't a problem as I can use fastboot to push a new image onto it, however this time I can't.
It tells me to press Back to go into fastboot mode, but nothing happens.
I've spent the past day using various SAPPIMG.ZIP files to try and fix this, but as you can guess, they haven't worked.
Plugging in USB does nothing (PC doesn't see it either), and I can only load SAPPIMG files. It was running the stock build supplied by Vodafone when I got it.
Is there any other way I could get either to fastboot, or is there a suitable image for me to load?
Sorry for the noobish post, but any help would be appreciated.
Regards,
Brett
Just to add: I've created a goldcard that works, and when I apply SAPPIMG files, it asks me to reboot the device. I do so, but I end up back in recovery with the same problem.
Are the fastboot drivers installed corrctly?
Sent from my SpeedTeam Magic using XDA App
You realize fastboit looks virtually the same ss the hboot/ how you load a sappimg correct? Only difference is a red rectangle saying fastboot. When you gret to fastboot open up your cmd prompt. Type this:
Cd\
Cd\nameofyourandroidsdkfolder\tools
Fastboot devices
Sent from my SpeedTeam Magic using XDA App
I can use fastboot on my Hero. I use the Back button to select fastboot and it comes up in red, and it works, and it also changes when I plug in the USB.
With the Magic, it gives me the option but it won't change when I press the button. Plugging in the USB doesn't work either, as neither device detects it. I've tried installing the Magic on my own PC, but without it detecting the hardware, there is very little I can do.
Unless there is a way to fully recover the phone (inc OS) with the HBOOT option, it is beginning to look like I'm holding a very expensive paper weight.
Thanks for the reply.
Hello everyone...
I have a newly bought HTC MT4G
Really need some help..
My phone got stuck with the tmob welcome logo after successfully temproot and permaroot...it does not seem to continue through the phones interface...I removed the battery and attempted to load factory reset and recovery reset..no luck at all..still got stuck...this is how my bootloader looks like:
GLACIER PVT ENG S-off
HBOOT-0.85.2007
MICROP-0429
RADIO-26.03.02.26_M
emmC-boot
OCT 11 2010 12:44:14
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
SYSTEM INFO
IMG CRC
I dont know what to do with the phone now...been reading a lot but it seems i get more confused..tnks really appreciate it
You must have the adb and fastboot binaries for this to work. There are several threads on xda to get those to work. Once you have that working, go to the clockwork recovery thread and download clockworkmod recovery 2.5.x.x. Then copy that to your /AndroidSDK/tools folder. Boot your phone into HBOOT mode. Select Fastboot. Plug your phone into your computer. Let it load the drivers. Open up a command window (DOS) by pressing the window button + R and typing cmd and press run. Change the directory to your /AndroidSDK/tools folder (cd /AndroidSDK/tools). Then type:
fastboot devices
It should return your phone's serial number. Then type:
fastboot flash recovery
DO NOT HIT ENTER YET! Put a space after recovery, then drag and drop the recovery file from your tools folder onto the command screen window. Now press enter.
It should say sending recovery....Okay. Then writing recovery.....Okay.
After that select bootloader from the fastboot screen. Then once it changes to HBOOT mode, just select recovery and it'll boot you into clockworkmod recovery where you can flash any rom you need to.
ok Im gonna try this step by step...hopefully I my phone aint bricked.. tnks so much!
Don't worry, your phone is far from bricked! As long as HBOOT mode is available to you you're fine! I'll try to find the link to the original ROM so that way you can just flash that through HBOOT if this process doesn't work. This process will allow you to keep your engineering bootloader (0.85.2007). Flashing the original ROM will make you have to go back through the rooting process. I really hope you get this to work! Good Luck! And by all means you can PM me with any questions you have. That way I can get back you faster. If you include your email, I can respond right away.
EDIT: Here is the link to the Stock 2.2.1 update. This will undo root. So use that as a last resort. But it will definitely work!
You want to download the PD15img.zip
http://forum.xda-developers.com/showpost.php?p=10781618&postcount=3
HI again!! so far so good...I do manage to understand and execute the process of adb flash recovery...but as soon as I choose recovery from HBOOT mode...my phone seems to freeze immediately to tmobMyT4g logo...and it seems to stay a while from there...1st question is..do I need to unplug my usb connection from pc then press recovery?! or do i keep it plugged in...for now...Im gonna try the original recovery.img for it...I'll just have to start all over again to permaroot the phone...
paolocab2000 said:
HI again!! so far so good...I do manage to understand and execute the process of adb flash recovery...but as soon as I choose recovery from HBOOT mode...my phone seems to freeze immediately to tmobMyT4g logo...and it seems to stay a while from there...1st question is..do I need to unplug my usb connection from pc then press recovery?! or do i keep it plugged in...for now...Im gonna try the original recovery.img for it...I'll just have to start all over again to permaroot the phone...
Click to expand...
Click to collapse
to reboot the phone while in fastboot just type
# fastboot reboot
Click to expand...
Click to collapse
same results still...ends up with the logo...BTW with the original ROM PD15... do I use it as an image file or follow the instructions on this thread?http://forum.xda-developers.com/showpost.php?p=10781618&postcount=3
can you show me exactly what the command window is telling you? From what I understand, you typed
fastboot devices
and got back your phone's serial. then typed
fastboot flash recovery C:/what/ever/the/path/is/to/recovery.img
and got back
sending recovery...okay
writing recovery...okay
and then went to bootloader
and attempted to reboot to recovery
if this is the exact process you used, i'm not sure what could be the issue.
and the pd15img.zip, you will follow the instructions in the post
Iriscience said:
can you show me exactly what the command window is telling you? From what I understand, you typed
fastboot devices
and got back your phone's serial. then typed
fastboot flash recovery C:/what/ever/the/path/is/to/recovery.img
and got back
sending recovery...okay
writing recovery...okay
and then went to bootloader
and attempted to reboot to recovery
if this is the exact process you used, i'm not sure what could be the issue.
and the pd15img.zip, you will follow the instructions in the post
Click to expand...
Click to collapse
no.1
Yup exactly what I did...seems frustrating...any method i use goes to the same logo freeze...but before this happened...in the first place...I tried to replace the (system/bin) folder on the root...coz i haD this issue of placing back my original WPA_supplicant becoz it seems that it wasnt detecting WIFI networks at all...then as soon as I restarted goes stuck with the logo...I was hoping that I could flash it back with the original ROM...then now its this...
no.2
Also when i try to use the older recovery.img, it goes to that red triangle with a exclamation mark angle...
no.3
I also tried to restore to factory settings from the HBOOT menu...it goes after wards to the logo after having that cellphone green cycling icon and a status bar...
No.4 as soon as try the steps on the PD15img.zip methods... I dont see any phone detect options or begin update options...it all ends up with the tmobile logo
paolocab2000 said:
No.4 as soon as try the steps on the PD15img.zip methods... I dont see any phone detect options or begin update options...it all ends up with the tmobile logo
Click to expand...
Click to collapse
When you do the PD15IMG method you store the PD15IMG on the root of the SD card and turn the phone on holding the power and volume down button. It should never get to the boot image.
neidlinger said:
When you do the PD15IMG method you store the PD15IMG on the root of the SD card and turn the phone on holding the power and volume down button. It should never get to the boot image.
Click to expand...
Click to collapse
Well like what the method instructed...as soon as I press the power+volume down..it goes straight ahead to my Hboot menu...THe options mentioned on the above method doesnt seem to appear.
paolocab2000 said:
Well like what the method instructed...as soon as I press the power+volume down..it goes straight ahead to my Hboot menu...THe options mentioned on the above method doesnt seem to appear.
Click to expand...
Click to collapse
as soon as you boot into the bootloader does the system check for the PD15IMG?
neidlinger said:
as soon as you boot into the bootloader does the system check for the PD15IMG?
Click to expand...
Click to collapse
yup it does check for it very quickly then after that...HBOOT menu...then as soon as I choose one from the menu..i get stuck with the Mytmob logo...
paolocab2000 said:
yup it does check for it very quickly then after that...HBOOT menu...then as soon as I choose one from the menu..i get stuck with the Mytmob logo...
Click to expand...
Click to collapse
when it searches for the image is it telling you "image not found", and did you extract the stuff to the SD card or leave it compressed?
neidlinger said:
when it searches for the image is it telling you "image not found", and did you extract the stuff to the SD card or leave it compressed?
Click to expand...
Click to collapse
I dont get to received any error message such as image not found...and yes I leave the PD15img.zip file as it is uncompressed..
AAAhhhh at last!>!! something worked!!! I followed this link/thread http://forum.xda-developers.com/showthread.php?t=919834
The only clockmod that worked for me is 3.0.0.0. reinstalling stock rom as of now...I guess I have to restore to defaults for now...and attempt to install custom roms some other day!! Tnks to all who helped...!! For now...
Just to let you know, you'll only be able to flash Gingerbread ROMs with ClockworkMod 3.0.x.x. You have to use CWM 2.5.x.x to use Froyo ROMs. Just wanted to make sure you knew that, so you don't get into another "brick" kind of situation.
Iriscience said:
Just to let you know, you'll only be able to flash Gingerbread ROMs with ClockworkMod 3.0.x.x. You have to use CWM 2.5.x.x to use Froyo ROMs. Just wanted to make sure you knew that, so you don't get into another "brick" kind of situation.
Click to expand...
Click to collapse
I do believe you are correct...it so happened that i have tried loading Clockworkmod
2.x.x.x and 3.0.0.5 and the only thing that passed through the logo and showed the menu is 3.0.0.0...
I also made a mistake in placing the PD15img.zip file on my SDCARD as "PD15img.zip.zip" because the extensions are already associated and it its these small things that one has to be really careful about the certainty of the process step by step.
Anyways as soon as I corrected the file name...my HBOOT loader automatically did the job..but I am back to square one...but this time IM gonna use the older clockwork MOD to install Froyo roms...which my main problem in the first place was losing my WPA_supplicant file..in which I lost the WIFI connection capabilities of the phone..in which it made it difficult for me to access key files to reflash and boot the phone again as a default factory phone...
Hi
I had a problem with my htc magic after trying to flash the RA-sapphire-v1.0.0 recovery image into the phone. Before the problem occurred I rooted my phone and flashed RA-sapphire-v1.6.5, but because I had an issue with it I tried to flash an old version " RA-sapphire-v1.0.0".
Now my phone keeps rebooting endlessly and I can not access recovery mode, fastboot or anything else?
Is it bricked? Can I fix this issue?
The phone is 32A
Radio is 6.35 (I can not access fastboot so this is from my memory)
If you have no access to fastboot nor recovery, then you are pretty bricked!!!
Are you sure you can't get into fastboot? Pull the batter, press and hold down the back button, and put the battery back in. See if it goes into fastboot then. Do the same thing again, but holding the home button instead to see if you can get into recovery. I dunno why you used an old one and not the new one.
DonJuan692006 said:
Are you sure you can't get into fastboot? Pull the batter, press and hold down the back button, and put the battery back in. See if it goes into fastboot then. Do the same thing again, but holding the home button instead to see if you can get into recovery. I dunno why you used an old one and not the new one.
Click to expand...
Click to collapse
I tried both method and it did not work. The phone is still rebooting endlessly. I used the old recovery since the new one kept restarting the phone to the actual system after I go into recovery mode after 2-3 seconds.
1.6.5 isn't the new one. The newest version is 1.7.0. Well if that didn't work, then year your bricked.
so is there anything i can do to fix it?
JTAG is your only option.
Where are you from ?
usernome said:
Where are you from ?
Click to expand...
Click to collapse
I am from Australia
I have HTC Magic Vodafone (32B) and have a similar issue with phone in a reboot loop, however, i can get into fastboot but not sure what next to do. Is there a guide anywhere on what to recover my phone.
Depends, what is your current fastboot information?
Not sure what info you want from Fastboot screen so this is everything i can see
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.0013 (SAPP10000)
CPLD-10
RADIO-2.22.28.25
Oct 21 2009,22:33:27
Is this the right kind of information?
Two options. Downgrade to 1.5, then update to 1.6, then root, flash a custom ROM, reinstall the 1.33.0013 SPL and 2.22.28.25 radio, and then flash a new custom ROM. Optionally, you can downgrade to 1.5 and upgrade back up to 2.2.1. Either way just let me know and I can assist.
Thanks for you help with regards to the approach, is one easier than the other? If they are both roughly the same then would go for the Downgrade to 1.5 and upgrade back up to 2.2.1. route as it may be easier to sell in a few weeks when the Galaxy S2 out.
So, here we go, please read through all the steps before starting and then reading each step as you go along:
1. Go here and download "sappimg.nbh" and "update1-5.zip".
2. Put all of them on your SD card. I would suggest downloading to a folder on your computer, then copying them over. Have had issues in the pass with people downloading files directly to their SD card and it corrupting the file.
3. With the phone turn off and the SD card in it, boot holding (volume down+power) to get into hboot. The phone should detect the sappimg.nbh, check the file (you'll see a progress bar in the upper right-hand corner), and then ask you to hit "ACTION" to continue. (ACTION being pressing the trackball)
4. The phone will start flashing the different parts of the phones partitions. You'll see the progress bar in the upper right-hand corner a few more times, then after about 5 minutes, it'll ask you to hit "ACTION" again to reboot.
5. Let the phone boot all the way up (this may take a few minutes) and then turn it off without signing in.
NOTE: Unless you need the phone to access the SD card from the computer, in that case sign in and do the next step.
6. Access the SD card, find "update1.zip" and rename it to "update.zip".
7. With the phone off turn it back on by holding (home+power) to get into recovery. You'll see a triangle with an ! in it, press (home+power) again to bring up the menu.
8. Using the trackball, scroll to the "wipe data/factory reset" option and press the trackball to select it. After it completes, scroll to "apply update.zip from SD card" and select it. It should pickup the update file on the SD card and flash it, then reboot.
9. When you get to the login screen again, turn the phone off.
Note: Again, as before, you can optionally login to get into the ROM for access to the SD card from your computer.
10. Repeat steps 6-9 for the "update2-update5.zip" files. You will need to remove the old "update.zip" before renaming the next update file. When you get to the login screen the last time (after flashing "update5.zip") you can sign in and use the phone.
Thanks for the guide but I've hit a problem. The phone recognise the sappimg.nbh and starts to flash itself but when then a message:
model ID incorrect!
Update Fail!
appears and the flash has failed. I've tried this a few times now downloading the file again, formating the SD card etc but to no avail. Do you have any suggestion on how to get round this issue?
Geffen22 said:
Thanks for the guide but I've hit a problem. The phone recognise the sappimg.nbh and starts to flash itself but when then a message:
model ID incorrect!
Update Fail!
appears and the flash has failed. I've tried this a few times now downloading the file again, formating the SD card etc but to no avail. Do you have any suggestion on how to get round this issue?
Click to expand...
Click to collapse
Crap gave you the wrong sappimg. What country did you get the phone from?
Sent from my LG-P500 using Tapatalk
I got phone from Vodafone in the UK.
Geffen22 said:
I got phone from Vodafone in the UK.
Click to expand...
Click to collapse
Need the specific country.
United Kingdom or England to be exact.
i was trying to install carz12's Gingerbread ROM for the mytouch3g 32B (http://forum.xda-developers.com/showthread.php?t=956280) and was having numerous issues..."status 7" error for the most part (which i couldnt figure out for the life of me what that means...and yes i searched). so i upgraded my hboot to 1.33.0013d and the radio to 2.22.27.08, which didnt help any (via the recovery ra 1.5.2)...still the "status 7" error. so i un-rooted, and re-rooted with the orignal sapphire.nbh rom i have...still didnt work. i even flashed the 614MHz kernal before flashing the GB ROM, which made the system tell me carz12's ROM installed correctly...when in all actuality it didnt after i decided to stop looking at the green mytouch splash screen after 1 hour and nothing happening.
so i did some more reading...including every post on the roms forum link...posted above. no one was having my issue. so instead of asking for help (the smart thing) because i wanted to hurry it up and go play poker, i noticed that my hboot may be the issue as per something i read while trying to figure it out. so i grabbed the 1.76.0007 file and flashed it via recovery, and then reset my device...thats where it all went wrong...
it showed the HTC logo for a split second, then it shut off. i cant get it back on. i have tried unplugging the battery and hitting the power button for a few minutes...no luck...i tried plugging it into the usb wall charger...even the led charging light wont turn on.
how do/can i fix this? i cant believe im so stupid.
?!?!
First for future note and to help people not do what you did.
1) on a 32b devices you should not install 1.76.* SPLs
2) on a 32b devices you should not install 6.x radios
3) carz12's rom is a re-compile of my ezGingerbread for 1.76.* SPL with the 6.x radio for the classic 32a phones w/o audio jack.
So the correct way to install it was to install ezGingerbread with the 2708+ kerenl you presumably already had installed since you had 1.33.0013d. (optionally I guess if there was some differences besides that to make the older kernel + alternative kernel work you could force carz12's rom to install then flash a 2708+ kerenl on top of it to allow it to boot on your hardware, this is done by updating the checks on the rom *NOT* updating the system to match the checks)
---
Ok.. So now that you are stuck.. enter fastboot (power on holding volume down) and lets look at the damage:
Hopefully you see:
1.76.2007 with S=OFF .. if S=ON I think there is a command you can run (check pinned topics to focrce S=OFF)
IF you see this we can recovery but careful:
If your current radio starts with a "6" you will want to flash 2.22.25.28 via 'fastboot flash radio RADIO-2.22.28.25.img' then run 'fastboot reboot-bootloader'
(You can unzip the radio file form the update on http://forum.xda-developers.com/showthread.php?t=831139 all other mentioned files are also available on that op post)
Now your radio ought to start with 2.22: (either because you didn't have the 6.x or just downgraded to it..) now by fastboot flash:
'fastboot flash recovery recovery-RA-dream-v1.7.0-cyan.img' and
'fastboot flash hboot hboot-1.33.0013d.img'
'fastboot reboot-bootloader'
If all is well you will have 2.22.25.28 and 1.33.0013d and can boot to recovery and install a rom
If all is mostly well you will have another 2.22.* radio and 1.33.0013d and can boot to recovery and install the 2.22.25.28 updater.zip
If all is not well... you will see something else.
ezterry said:
?!?!
First for future note and to help people not do what you did.
1) on a 32b devices you should not install 1.76.* SPLs
2) on a 32b devices you should not install 6.x radios
3) carz12's rom is a re-compile of my ezGingerbread for 1.76.* SPL with the 6.x radio for the classic 32a phones w/o audio jack.
So the correct way to install it was to install ezGingerbread with the 2708+ kerenl you presumably already had installed since you had 1.33.0013d. (optionally I guess if there was some differences besides that to make the older kernel + alternative kernel work you could force carz12's rom to install then flash a 2708+ kerenl on top of it to allow it to boot on your hardware, this is done by updating the checks on the rom *NOT* updating the system to match the checks)
---
Ok.. So now that you are stuck.. enter fastboot (power on holding volume down) and lets look at the damage:
Hopefully you see:
1.76.2007 with S=OFF .. if S=ON I think there is a command you can run (check pinned topics to focrce S=OFF)
IF you see this we can recovery but careful:
If your current radio starts with a "6" you will want to flash 2.22.25.28 via 'fastboot flash radio RADIO-2.22.28.25.img' then run 'fastboot reboot-bootloader'
(You can unzip the radio file form the update on http://forum.xda-developers.com/showthread.php?t=831139 all other mentioned files are also available on that op post)
Now your radio ought to start with 2.22: (either because you didn't have the 6.x or just downgraded to it..) now by fastboot flash:
'fastboot flash recovery recovery-RA-dream-v1.7.0-cyan.img' and
'fastboot flash hboot hboot-1.33.0013d.img'
'fastboot reboot-bootloader'
If all is well you will have 2.22.25.28 and 1.33.0013d and can boot to recovery and install a rom
If all is mostly well you will have another 2.22.* radio and 1.33.0013d and can boot to recovery and install the 2.22.25.28 updater.zip
If all is not well... you will see something else.
Click to expand...
Click to collapse
You realise the OPs head will probably explode from reading this? LOL
Sent from my LG-P500 using Tapatalk
my head did explode...but im savvy enough to understand most of it...my lack of understanding only comes in from the whole ADB push issue...I have tried, but never really got into the whole ADB software...i was always just able to do it on my phone so figured why would I need it from my computer...ludicrous...i know
my main issue now is that i cant see anything on my screen. when i hit the power button, nothing happens...no vibrate, no LED lights, no splashscreen....nothing. and i cant get into fastboot since the screen wont turn on.
before (a few minutes ago), when i plugged in my charger to the phone, i couldnt even get the LED light to show up to say it was charging...but i just found out a few minute ago that if i yank out the battery and put it back in without hitting any buttons the charging light comes on (so it acts just like it went into the fastboot or recovery mode where the LED light wont come on when plugged in). as soon as i try to power it on, it turns off. im hoping that it is trying to turn on, and actually does, but the screen just wont turn on since the new software wasnt designed to turn on my screen. so what im going to try to do is go off of pictures of the recovery, and do it very carefully to attempt to install a new hboot...without a GUI or a screen...completely blind...we will see if it works..i hope it does...
i am unable to do anything with the phone at this point except experiment...i cant even get my computer to recognize the device...it says that there was a problem with the installation of the device drivers so I wont be able to use ADB to push anything to it...
wish me luck...ill repost as soon as i give up on my hopes that the screen just wont work but is actually working behind the scenes..
i am sorry if i repeated myself alot in this post...i read it and retyped it a few times...but didnt really delete anything...hopefully it makes sense.
it doesnt look like my idea of the screen just not turning on but everything running in the background is working... im trying to find the usb drivers for the mytouch, but HTC doesnt have them on their website, and google only has the SDK for the nexus1...im gonna try it anyways...please respond if you have anything to say...im desperate.
ezterry said:
now by fastboot flash:
'fastboot flash recovery recovery-RA-dream-v1.7.0-cyan.img' and
'fastboot flash hboot hboot-1.33.0013d.img'
'fastboot reboot-bootloader'
Click to expand...
Click to collapse
EDIT: i figured this out...but i still dont see how i can get into fastboot mode...
when i do an "adb devices" is comes up emptyhanded...how can i get it so it recognizes my phone so i can push a good hboot to it?
EDIT #2: Ok...so i have decided to give up, because after being up till 4AM refusing to admit defeat, i finally accept the fact that this is a full brick and needs jtag'd. EZTERRY: I have sent you a PM. If what i sent you in the PM is no good, could you teach me and i can do it myself? i am a quick learner when it comes to hardware.
Thanks
other symptoms of my issue just for future reference if someone stumbles upon this post:
1: no fastboot via volume down+power
2: no recovery via home+power
3: scrollball+power=Blue LED
4: unplugging battery, plugging battery back in+wallcharger plugged in after battery back in = orange LED
5: if i hit the power button while orange LED is on = orange LED turns off and have to take out and put back in battery to get it back
6: ADB software does not recognize the device, therefore no way to push any fixes to the phone
7: JTAG seems to be the only fix...if you are crafty and can google search, and have a linux box, you could probably fix it yourself for the cost of some wires and cables.
this sucks....
I swear I've gone through almost every thread and googled almost everything I could to try to get this phone out of the "HTC" boot up screen. It just stays there forever. It's my friend's G2 (I have a G2 as well) and I have no idea what happened but I've tried everything.
Initially, I was going to go into recovery and just restore a backup of mine but when I got into recovery, it showed an loading bar and an image. I have a feeling that clockwork recovery isn't in the phone anymore or well, it's obvious that I can't get into recovery. I've tried fastboot via adb and tried flashing a new one but the thing is that adb can't even detect the phone and I tried to flash it anyway cause it was detected in hboot but it still cease to work.
I've tried this method as well http://forum.xda-developers.com/showpost.php?p=10583834&postcount=33 , and I got nothing. Tried put several different PC10IMG.zip but when it gets to 7/8th of the bar, it just stays there forever. I'm starting to believe that this phone is gg.
VISION PVT SHIP S-OFF
HBOOT-0.82.0000
MICROP-0425
RADIO-26.02.01.15_M2
Sep 2 2010, 17:59:38
does anyone have an answer or help ? : ( suggestions??
are you using the touchpad to select in recovery? Do not use the Power button to select...
xjaynee said:
I swear I've gone through almost every thread and googled almost everything I could to try to get this phone out of the "HTC" boot up screen. It just stays there forever. It's my friend's G2 (I have a G2 as well) and I have no idea what happened but I've tried everything.
Initially, I was going to go into recovery and just restore a backup of mine but when I got into recovery, it showed an loading bar and an image. I have a feeling that clockwork recovery isn't in the phone anymore or well, it's obvious that I can't get into recovery. I've tried fastboot via adb and tried flashing a new one but the thing is that adb can't even detect the phone and I tried to flash it anyway cause it was detected in hboot but it still cease to work.
I've tried this method as well http://forum.xda-developers.com/showpost.php?p=10583834&postcount=33 , and I got nothing. Tried put several different PC10IMG.zip but when it gets to 7/8th of the bar, it just stays there forever. I'm starting to believe that this phone is gg.
VISION PVT SHIP S-OFF
HBOOT-0.82.0000
MICROP-0425
RADIO-26.02.01.15_M2
Sep 2 2010, 17:59:38
Click to expand...
Click to collapse
adb and fastboot are two different programs- adb won't work in fastboot mode.
Do you have fastboot on your pc? You could just flash directly from there, although it's generally considered riskier. Also, I think there are at least two versions of fastboot floating around. HTC provided one, the second one gets compiled as a host binary when you build a CM ROM, and possibly a third gets compiled with the ASOP ROM. The CM version is more versatile because it will flash yaffs images, such as the ones that CWM makes when it backups your data.
You are also on the shipped (non-engineering) hboot, so I don't know if that will let you flash a new recovery.
xjaynee said:
I swear I've gone through almost every thread and googled almost everything I could to try to get this phone out of the "HTC" boot up screen. It just stays there forever. It's my friend's G2 (I have a G2 as well) and I have no idea what happened but I've tried everything.
Initially, I was going to go into recovery and just restore a backup of mine but when I got into recovery, it showed an loading bar and an image. I have a feeling that clockwork recovery isn't in the phone anymore or well, it's obvious that I can't get into recovery. I've tried fastboot via adb and tried flashing a new one but the thing is that adb can't even detect the phone and I tried to flash it anyway cause it was detected in hboot but it still cease to work.
I've tried this method as well http://forum.xda-developers.com/showpost.php?p=10583834&postcount=33 , and I got nothing. Tried put several different PC10IMG.zip but when it gets to 7/8th of the bar, it just stays there forever. I'm starting to believe that this phone is gg.
VISION PVT SHIP S-OFF
HBOOT-0.82.0000
MICROP-0425
RADIO-26.02.01.15_M2
Sep 2 2010, 17:59:38
Click to expand...
Click to collapse
I wonder if this is a case of faulty eMMC?
Whgat version of Recovery did you have flashed? What version did you attempt to flash?
FYI, I sent my phone back to HTC when it was doing something similar to this and they fixed it for me. I think it was a bad eMMC or something else internal because I noticed some signs that the phone had been physically opened.