My T-Mobile HTC G2 gets stuck on the HTC white & green boot screen..
I read some forums and apparently I'm not bricked. I can get the the HBOOT screen.
I want to make this phone useable again, so if anyone has any methods at all, help me out please. I am a noob with andriod.
I will need step-by-steps!
VISION PVT SHIP "S-OFF"
ClockworkMod Recovery v3.0.2.4
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Click to expand...
Click to collapse
Thanks
-Kagen
notKagen said:
My T-Mobile HTC G2 gets stuck on the HTC white & green boot screen..
I read some forums and apparently I'm not bricked. I can get the the HBOOT screen.
I want to make this phone useable again, so if anyone has any methods at all, help me out please. I am a noob with andriod.
I will need step-by-steps!
VISION PVT SHIP "S-OFF"
Thanks
-Kagen
Click to expand...
Click to collapse
How did u get it bricked?
xudsa II USERT said:
How did u get it bricked?
Click to expand...
Click to collapse
A friend rooted it over a year ago.
Everything worked fine, so we flashed a ROM. (don't remember which one)
That worked fine, then few days later things on the phone started to fail. Slowly more and more things failed. Then I was forced to reboot the phone.
When I rebooted It stuck on boot screen. now I get those logs in recovered that I originally posted.
To say the worse, it sounds like a corrupted file system acutally . You can get to HBOOT screen right? (Vol + Power On)
xudsa II USERT said:
To say the worse, it sounds like a corrupted file system acutally . You can get to HBOOT screen right? (Vol + Power On)
Click to expand...
Click to collapse
Yes, I can get there very easily.
Is a corrupt file system irreversible? That sounds like something where I could just replace the files with non-corrupt ones...maybe? haha as you can see I know nothing.
notKagen said:
Yes, I can get there very easily.
Yes, I can get there very easily.
Is a corrupt file system irreversible? That sounds like something where I could just replace the files with non-corrupt ones...maybe? haha as you can see I know nothing.
Click to expand...
Click to collapse
EDITED: GAVE EXPLAINATION
notKagen said:
Yes, I can get there very easily.
Is a corrupt file system irreversible? That sounds like something where I could just replace the files with non-corrupt ones...maybe? haha as you can see I know nothing.
Click to expand...
Click to collapse
Erm.. I'm not too sure, it could be just maybe a small error fixable by 'replacing', but then again it could be a physical damage (bad sectors, but those are usually very very rare).
If your bootloader does function fine, it could be the former (though not being able to mount in recovery sounds like a bad sector). It is possible that you can load a rom through ur sd card and restore it through the bootloader. (I'm still learning that part). Be very very very careful! You can actually make your phone not work! Do a lot of research, and don't rush! Hopefully someone with much more experience can help from here on.
I'll explain here: if your phone does not boot, usually it could mean that some files cannot be read or are missing, so the phone will not boot android. The fact that the recovery states that it cannot mount the filesystem could mean that there is a possibility that your memory filesystem may be corrupted. But, since it can boot the bootloader without problems, there is a high possibility that the problem lies in the recovery files being problematic themselves. In that case, you can load a original rom (BE VERY CAREFUL BEFORE YOU DO SO, I ASKED HERE, so this could be a jumping board for you.). A mention, u must be careful, loading a full ROM includes loading the bootloader as well, so it may cause your phone to not even load the bootloader.
I really think someone with better experience should help from here on, i dont want to brick your phone :/
xudsa II USERT said:
EDITED: GAVE EXPLAINATION
Erm.. I'm not too sure, it could be just maybe a small error fixable by 'replacing', but then again it could be a physical damage (bad sectors, but those are usually very very rare).
If your bootloader does function fine, it could be the former (though not being able to mount in recovery sounds like a bad sector). It is possible that you can load a rom through ur sd card and restore it through the bootloader. (I'm still learning that part). Be very very very careful! You can actually make your phone not work! Do a lot of research, and don't rush! Hopefully someone with much more experience can help from here on.
I'll explain here: if your phone does not boot, usually it could mean that some files cannot be read or are missing, so the phone will not boot android. The fact that the recovery states that it cannot mount the filesystem could mean that there is a possibility that your memory filesystem may be corrupted. But, since it can boot the bootloader without problems, there is a high possibility that the problem lies in the recovery files being problematic themselves. In that case, you can load a original rom (BE VERY CAREFUL BEFORE YOU DO SO, I ASKED HERE, so this could be a jumping board for you.). A mention, u must be careful, loading a full ROM includes loading the bootloader as well, so it may cause your phone to not even load the bootloader.
I really think someone with better experience should help from here on, i dont want to brick your phone :/
Click to expand...
Click to collapse
Alright man, I'll follow the link but I don't know if this will help you. Some things when I am in HBOOT and I hit them they do nothing. Just freeze the phone. I don't know if that changes things.
notKagen said:
Alright man, I'll follow the link but I don't know if this will help you. Some things when I am in HBOOT and I hit them they do nothing. Just freeze the phone. I don't know if that changes things.
Click to expand...
Click to collapse
Okay, I tried what you said but no success. My ClockworkMod seems to not be mounting. Because of the Errors I posted previously in my first post. So this way I can't flash anything from recovery because it will just stay on that screen with the top hat and the orange circle with the arrow. Nothing happens. If I tap the power button, it just goes back to the menu.
Should I be updating clockwork somehow?
Is there another way to flash?
Could there be a problem with my SD's? (i've tried on 2 different ones)
Do you have any ideas?
This is an educated guess, but you might want to try flashing the stock firmware back onto the phone and trying again, and ensure the MD5s match. You could even follow the instructions in the wiki to give CyanogenMod ROM a try; that's what I'm using now and is the more widely developed and recognizable ROM that I know of.
http://wiki.cyanogenmod.com/wiki/TMobile_G2:_Firmware_Downgrade_(Gingerbread)
Firstly, don't select stuff with power button in clockwork, use the camera or trackpad.
Secondly, those errors may indicate a bad emmc, which is a hardware defect, and cannot be fixed. More info here
You can either go for a warranty replacement, or you can boot cm7.1 from your sdcard, using Catherall's instructions
-Nipqer
EdWaRdW818 said:
This is an educated guess, but you might want to try flashing the stock firmware back onto the phone and trying again, and ensure the MD5s match. You could even follow the instructions in the wiki to give CyanogenMod ROM a try; that's what I'm using now and is the more widely developed and recognizable ROM that I know of.
http://wiki.cyanogenmod.com/wiki/TMobile_G2:_Firmware_Downgrade_(Gingerbread)
Click to expand...
Click to collapse
Sure, I can try that. Is there a step by step....don't really know what im doing.
Almost 100% you have a bad emmc, there is no fix for this, nipqer sent you a guide to run an os off your sdcard and this may be your only 'fix'
You can try and flash a new recovery via fastboot and a rom as well. But my best guess is your sol, try to warranty it if possible, run os off sd, or sell it for parts and get a new one
Sent from my HTC Vision using xda premium
demkantor said:
Almost 100% you have a bad emmc, there is no fix for this, nipqer sent you a guide to run an os off your sdcard and this may be your only 'fix'
You can try and flash a new recovery via fastboot and a rom as well. But my best guess is your sol, try to warranty it if possible, run os off sd, or sell it for parts and get a new one
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Alrighty! Thanks for your help!
reflash a new ROM
notKagen said:
My T-Mobile HTC G2 gets stuck on the HTC white & green boot screen..
I read some forums and apparently I'm not bricked. I can get the the HBOOT screen.
I want to make this phone useable again, so if anyone has any methods at all, help me out please. I am a noob with andriod.
I will need step-by-steps!
VISION PVT SHIP "S-OFF"
Thanks
-Kagen
Click to expand...
Click to collapse
Dude This happened to me too first if you downgraded to froyo and if you kept a nandroid backup of it restore to the froyo nandroid backup BE SURE THE NANDROID BAKUP OF THE FROYO VERSION IS A ROOTED ONE OR ELSE YOU'LL BRICK YOUR PHONE OR SCREW UP THE ROOT!! then after that flash another ROM using fastboot in bootloader mode
okay heres what to do
1.Open A CMD window in windows
2.Navigate to the folder where you have fastboot for example cd...
cd...
cd /
C:\Android SDK\Platform Tools
then you should also have ADB at the same folder together with Fastboot
then plug your phone while it fastboot mode in Bootloader
it should say "FASTBOOT USB"
3.Then verify that your computer recognizes your Phone by typing "fastboot devices" without (" ")
4.put the ROM.zip on the same folder where you have Fastboot and ADB
5. type in fastboot clear cache (I don't know the exact command but you need to clear cache)
6. AFTER CLEARING CACHE TYPE IN "fastboot flash zip ROM.zip (REPLACE "ROM" with the right ROM name it ahould be like ICS.zip or whatever your gonna flash
7. just let it do its job
8.Celebrate if it worked =))
PM me if you need more help
SOMEONE PLEASE CORRECT ME IF I DID SOMETHING WRONG
-goodluck
Related
Hello.
I'm pretty sure i bricked my HTC desire yesterday when trying to flash LeeDroids Mod. My phone hangs at the three green HTC letters and it has been like this the whole night. I've tried taking out the battery and things like that but it still hangs. Even when triyng to do a recovery. So i searched the forum to find out how to unbrick the phone and i found a nice thread that explains how to get acces to the SD again and then how to unbrick the USB connection. But I havent been able to try this out yet since i cannot find out how to enter commands when in fastboot. I know I need to be connected with a USB-cable to the PC, but what else do I have to do?
Hope someone can help 'cause I would really love to have my HTC Desire working again so that i can try out more cool FroYo mods from this lovely forum.
- Czepluch
czepluch said:
Hello.
I'm pretty sure i bricked my HTC desire yesterday when trying to flash LeeDroids Mod. My phone hangs at the three green HTC letters and it has been like this the whole night. I've tried taking out the battery and things like that but it still hangs. Even when triyng to do a recovery. So i searched the forum to find out how to unbrick the phone and i found a nice thread that explains how to get acces to the SD again and then how to unbrick the USB connection. But I havent been able to try this out yet since i cannot find out how to enter commands when in fastboot. I know I need to be connected with a USB-cable to the PC, but what else do I have to do?
Hope someone can help 'cause I would really love to have my HTC Desire working again so that i can try out more cool FroYo mods from this lovely forum.
- Czepluch
Click to expand...
Click to collapse
you have to use adb, google the android sdk and start there
All you need to do is boot into FASTBOOT, plug in your USB and run an RUU to get back to stock (assumg one is available for your phone) and then root again, had to do it myself the other day
you do not have to do ANY of this
if you are using clockworkmod or any custom recovery then there is the option to mount USB storage in which you can put on a backup or any other rom onto your sd card, unmount usb storage, and flash it, all in one.
cgrec92 said:
you do not have to do ANY of this
if you are using clockworkmod or any custom recovery then there is the option to mount USB storage in which you can put on a backup or any other rom onto your sd card, unmount usb storage, and flash it, all in one.
Click to expand...
Click to collapse
How do I do that when my phone doesnt boot? As i wrote in the first post it is stock at the 3 green HTC letters. I was using clockworkmod to flash, but as I wrote i cannot boot into andoid atm.
@AndroHero: Can you please give me a link or something? I have tried a lot of things, but i doesnt seem to work, so I would like to be certain that the link and guide im using is right.
czepluch said:
How do I do that when my phone doesnt boot? As i wrote in the first post it is stock at the 3 green HTC letters. I was using clockworkmod to flash, but as I wrote i cannot boot into andoid atm.
@AndroHero: Can you please give me a link or something? I have tried a lot of things, but i doesnt seem to work, so I would like to be certain that the link and guide im using is right.
Click to expand...
Click to collapse
Do you have the fake-flash zip file renamed as update.zip and at the root of your SDCard?
dnlgee said:
Do you have the fake-flash zip file renamed as update.zip and at the root of your SDCard?
Click to expand...
Click to collapse
yes i do
czepluch said:
yes i do
Click to expand...
Click to collapse
Have you booted the phone while holding the volume down and then selecting recovery, then when recovery boots, press volume up and power then select "apply update.zip" ?
The problem is that when i choose recovery it freezes aswell. The screen with the phone and the little red triangle freezes, so i cannot choose recovery.
EddyOS said:
All you need to do is boot into FASTBOOT, plug in your USB and run an RUU to get back to stock (assumg one is available for your phone) and then root again, had to do it myself the other day
Click to expand...
Click to collapse
So do what I said here...to get into FASTBOOT hold back and power it on
What is RUU?
Edit: Maybe I need someone to make a step by step noob guide? Im totally lost. Ive flashed my Desire lots of times before and ive never had a single problem, but right now i really dont know what to do and how to do?
If you're asking questions about RUU's then maybe rooting wasn't for you. It's basic stuff. You need a grasp of the basics before trying something advanced!
Basically it's the official ROM file from HTC/your phone vendor...
Okay. Thanks. I thought that RUU was something like that but I just couldnt see how i should be able to acces any files right now. As i wrote before the phone freezes at the picture of a phone with the red triangle, and i am not able to get any further that that. I would really appreciate if anyone could tell me how and what to do next?
I had the same problem a few days ago. For me it worked to just go through the rooting process again, you can find the steps on modaco (just step 1 of r6), I can't link them at the moment I'm at work and it seems I can't open modaco from here.
Anyways if you follow step 1 you can access the recovery again and the phone will boot past the HTC logo screen.
Also these steps are well documented on modaco.
Try this first since it will save you the step of running the RUU, which I wasn't able to (somehow the software complained my battery was below 30%, which it wasn't)
Good luck hope this solves it for you.
czepluch said:
Okay. Thanks. I thought that RUU was something like that but I just couldnt see how i should be able to acces any files right now. As i wrote before the phone freezes at the picture of a phone with the red triangle, and i am not able to get any further that that. I would really appreciate if anyone could tell me how and what to do next?
Click to expand...
Click to collapse
You don't need to go into recovery! boot into FASTBOOT and then leave it at that. Plug the phone in and it will then say FASTBOOT USB. Then run the RUU your phone came with originally. You don't need to go anywhere near Recovery
I am pretty certain that ive found a solution now. I deserve a fist in the nuts for being so stupid not to press volume up + power when trying to get into recovery mode. But fortunately dnlgee asked if i had remembered this. Now that ive gotten this far i should be able to solve the rest. I will however return if im still unable to solve it.
czepluch said:
I am pretty certain that ive found a solution now. I deserve a fist in the nuts for being so stupid not to press volume up + power when trying to get into recovery mode. But fortunately dnlgee asked if i had remembered this. Now that ive gotten this far i should be able to solve the rest. I will however return if im still unable to solve it.
Click to expand...
Click to collapse
Ah I missed that part, I couldn't access recovery either. Only thing left working was fastboot for me. All other options would hang on the HTC logo screen.
Let me preface this by saying yes I know there are dozens if not more threads on boot loop problems. I have recovered from boot loops before. This is very different.
I rooted my incredible with unrevokedForever and had cyanogen 6 on it. Everything was fine until yesterday I woke up to it in a boot loop, but not the cyanogen boot animation, the white HTC Incredible screen. I can only get to HBOOT, once I try to enter recovery, use an update.zip, or anything after the HBOOT page it goes into its loop. Should I pursue the RUU and find a windows computer or will that not help me?
I think I may have to bite the bullet and buy a new phone. As obviously they will not replace an S-OFF phone. Any help is appreciated.
jenic said:
Let me preface this by saying yes I know there are dozens if not more threads on boot loop problems. I have recovered from boot loops before. This is very different.
I rooted my incredible with unrevokedForever and had cyanogen 6 on it. Everything was fine until yesterday I woke up to it in a boot loop, but not the cyanogen boot animation, the white HTC Incredible screen. I can only get to HBOOT, once I try to enter recovery, use an update.zip, or anything after the HBOOT page it goes into its loop. Should I pursue the RUU and find a windows computer or will that not help me?
I think I may have to bite the bullet and buy a new phone. As obviously they will not replace an S-OFF phone. Any help is appreciated.
Click to expand...
Click to collapse
As long as you can still get into HBOOT and Recovery, you should be okay. Your best bet is to get the RUU and go back to stock/s-on, then re-root/s-off (if you want). I had to do this once, and it's pretty straight forward. Just do a search for Bezerker7's Ultimate Get Back to Stock Thread. It has all the info you'll need on how to do it.
RMarkwald said:
As long as you can still get into HBOOT and Recovery, you should be okay. Your best bet is to get the RUU and go back to stock/s-on, then re-root/s-off (if you want). I had to do this once, and it's pretty straight forward. Just do a search for Bezerker7's Ultimate Get Back to Stock Thread. It has all the info you'll need on how to do it.
Click to expand...
Click to collapse
The problem is I can only get into HBOOT, not recovery. It would be a fairly simple matter if I had access to recovery features. Would RUU work without access to recovery?
jenic said:
The problem is I can only get into HBOOT, not recovery. It would be a fairly simple matter if I had access to recovery features. Would RUU work without access to recovery?
Click to expand...
Click to collapse
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
RMarkwald said:
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
Click to expand...
Click to collapse
Your concise post is most appreciated. I will do as you instruct and post results back here when finished.
RMarkwald said:
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
Click to expand...
Click to collapse
Hit an unfortunate snag right away. fastboot (nor adb) is detecting the device. Screen is showing XC SHIP S-OFF as it should, it is in FASTBOOT USB mode and my computer detects the USB itself just fine.
dmesg output:
[346853.772041] usb 2-6: new high speed USB device using ehci_hcd and address 17
[346853.922917] usb 2-6: configuration #1 chosen from 1 choice
Click to expand...
Click to collapse
Thank you though that was a great suggestion! (Was very hopeful for a second there
I've never used the fastboot command before, but I seem to recall that sometimes my PC's don't report connection from ADB, but I haven't checked recently... Hmmm...
Just checked and it does report a device using ADB. Did you try typing the fastboot command to flash the recovery image file: fastboot flash recovery /path/to/<recovery.img file> anyways to see what happens? I am assuming if it isn't detecting the connection, it may fail...
EDIT: Did you pull the battery out, put it back in and try to get into recovery again? If you, try doing a user/factory reset + dalvik cache before trying to install a ROM from your SD card.
This may or may not help, but I had a similar issue of not having the phone recognized by fastboot while playing with a friends EVO Shift. I was able to use the program described in this thread to uninstall all HTC drivers. Then, when the phone was recognized and new drivers installed automatically, fastboot worked as expected.
http://forum.xda-developers.com/showthread.php?t=532719
RMarkwald said:
I've never used the fastboot command before, but I seem to recall that sometimes my PC's don't report connection from ADB, but I haven't checked recently... Hmmm...
Just checked and it does report a device using ADB. Did you try typing the fastboot command to flash the recovery image file: fastboot flash recovery /path/to/<recovery.img file> anyways to see what happens? I am assuming if it isn't detecting the connection, it may fail...
Click to expand...
Click to collapse
My ADB daemon would always recognize it in the past, when the phone was working. Yes I tried the command anyway, even though fastboot devices did not return anything. It hung there waiting for the device to be connected.
RMarkwald said:
EDIT: Did you pull the battery out, put it back in and try to get into recovery again? If you, try doing a user/factory reset + dalvik cache before trying to install a ROM from your SD card.
Click to expand...
Click to collapse
Yes, I pulled battery out multiple times, and when installing the rom I factory reset, cleared dalvik and normal cache through Clockwork. Cyanogen was working fine for weeks, this is a freak concurrence that happened without warning. I woke up to find it this way, or rather, it woke me up with its constant rebooting. lol.
cf9182 said:
This may or may not help, but I had a similar issue of not having the phone recognized by fastboot while playing with a friends EVO Shift. I was able to use the program described in this thread to uninstall all HTC drivers. Then, when the phone was recognized and new drivers installed automatically, fastboot worked as expected.
http://forum.xda-developers.com/showthread.php?t=532719
Click to expand...
Click to collapse
I appreciate the help however I am using Linux, and that seems to be a windows issue. I have not had issue detecting the device until this problem arouse. The sentiment is of course appreciated though, please do not feel that I am ungrateful! You have both been very supportive. I think I have just about resigned to dump money on a new phone. This time I will leave it stock for awhile and see if this occurs a third time.
jenic said:
My ADB daemon would always recognize it in the past, when the phone was working. Yes I tried the command anyway, even though fastboot devices did not return anything. It hung there waiting for the device to be connected.
Yes, I pulled battery out multiple times, and when installing the rom I factory reset, cleared dalvik and normal cache through Clockwork. Cyanogen was working fine for weeks, this is a freak concurrence that happened without warning. I woke up to find it this way, or rather, it woke me up with its constant rebooting. lol.
I appreciate the help however I am using Linux, and that seems to be a windows issue. I have not had issue detecting the device until this problem arouse. The sentiment is of course appreciated though, please do not feel that I am ungrateful! You have both been very supportive. I think I have just about resigned to dump money on a new phone. This time I will leave it stock for awhile and see if this occurs a third time.
Click to expand...
Click to collapse
This happened to me and many other people. It has nothing to do with the fact that you rooted as my replacement from verizon did the same thing even before I rooted. Finally on my 2nd replacement (my 3rd DINC), it has stopped happening.
You're going to have to take it to the store. The guy who looked at my phone looked right at the HBOOT (where it says s-OFF) and then said "we're going to have to send you another one."
So you may get lucky. Your other option (if you're nervous about the store seeing the s-OFF) is just to call Verizon and ask them to send you a replacement. My experience has been that the folks in the Verizon store have no idea what the f they're doing, and you'll probably be just fine taking it in.
jaba14 said:
This happened to me and many other people. It has nothing to do with the fact that you rooted as my replacement from verizon did the same thing even before I rooted. Finally on my 2nd replacement (my 3rd DINC), it has stopped happening.
You're going to have to take it to the store. The guy who looked at my phone looked right at the HBOOT (where it says s-OFF) and then said "we're going to have to send you another one."
So you may get lucky. Your other option (if you're nervous about the store seeing the s-OFF) is just to call Verizon and ask them to send you a replacement. My experience has been that the folks in the Verizon store have no idea what the f they're doing, and you'll probably be just fine taking it in.
Click to expand...
Click to collapse
That was definitely a laugh. Thank you I will see if I can get it replaced! I've been kinda just ignoring the fact that I do not have a phone all this time... Thankfully I had setup the phone to forward calls to google voice. It has been a lifesaver.
Sounds like there weren't any ideas in Q&A for this one, and I haven't seen much in terms of not being able to access recovery, so here goes...
I was happily using CM7, and while reading through a Diablo III news page (hopefully it comes out soon ), my phone rebooted into a boot loop. Weird, but I figured at worst I would wipe data and reinstall a ROM. Unfortunately, I can't get into recovery any longer.
If I boot the phone normally, I see the white HTC splash screen for a few seconds, then it reboots. I can use HBOOT fine, but as soon as I try to reboot normally / boot into recovery / boot into Restore Factory Defaults, my phone will reset. Let me clarify...
Pull and replace battery
Boot into HBOOT (volume down + power)
Select Recovery
Phone reboots and reaches CWM Recovery 3 for about 1/2 second, not long enough for me to click anything
Phone reboots into boot loop
I've used HBOOT to flash to CWM Recovery 3.0.0.8, downgraded to the stock radio, run the 2.2 RUU. I'm still running up against the same boot loop problem.
I wouldn't be surprised if it was a hardware problem, but I'm anxious to hear if anyone has ideas to try first. Additionally, is there any way to restore to S-ON through HBOOT in case I need to bring this into a Verizon store? I have fastboot.exe that can recognize the device over USB while the device is in HBOOT, maybe this will help?
Thanks!
Current state: Ran 2.2 RUU, S-OFF, HBOOT-0.92.0000, AMOLED, 2.15.00.07.28 radio
Thanks again.
Had this exact issue while running cm7. First couple of from when it was crackflashers. I couldn't find anything to help or fix it. I got a new dinc because I can't afford to be without for long.
Good luck dude.
Sent from my ADR6300 using Tapatalk
Thanks for the note. Maybe my fate will be the same. Did you get any sympathy from Verizon?
Doesn't sound like there are even any suggestions using fastboot, lol. [crickets chirping]
Can you flash cwm 2.5.x and try? Not sure if it will help but worth a shot?
sent from a phone
Yeah take out battery, then pull out sd card put it into a adapter and insert it to ur pc. Then find the file that was shipped specifically for ur device it looks something like this PC130mg.zip or some crap like that anyways put that on the root of your sd card. load ur card back to your phone now into hboot(volume down plus power) mode. Your phone will auto detect that file and start to ask if u want to install update say yes boom it will flash back to stock.....however my only concern would be if u need to turn s-ON before u do this.
I did this for a evo 4g and it worked but I turned s-ON first as it was in the instructions I was following. I think maybe the update file checks to see if ur S-off or on. But don't quote me on that.
Sent from my PG06100 using Tapatalk
popasmurfn23 said:
Yeah take out battery, then pull out sd card put it into a adapter and insert it to ur pc. Then find the file that was shipped specifically for ur device it looks something like this PC130mg.zip or some crap like that anyways put that on the root of your sd card. load ur card back to your phone now into bootloader (volume down plus power) mode. Your phone will auto detect that file and start to ask if u want to install update say yes boom it will flash back to stock.....however my only concern would be if u need to turn s-ON before u do this.
I did this for a evo 4g and it worked but I turned s-ON first as it was in the instructions I was following. I think maybe the update file checks to see if ur S-off or on. But don't quote me on that.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
Yeah, I agree with popasmurf. Put the PB31IMG.zip on your sdcard. Then let hboot discover and update it. It'll be back to stock and youll have to reroot but better than a paperweight.
You can find the image here -----> http://dougpiston.com/?page_id=108
I'm assuming you have a dinc.
sent by carrier pigeon
hope that helps
@phazeone let's say he just does that. Now his phone reboots and is on stock and looses his root, now he can root it again and then turn the S-on by the single file flash from recovery mode, and then use the update file again to flash the phone back to normal stock without root ( if he was taking it back) so whenever u want to manipulate the S security u must be rooted correct?
Sent from my PG06100 using Tapatalk
popasmurfn23 said:
@phazeone let's say he just does that. Now his phone reboots and is on stock and looses his root, now he can root it again and then turn the S-on by the single file flash from recovery mode, and then use the update file again to flash the phone back to normal stock without root ( if he was taking it back) so whenever u want to manipulate the S security u must be rooted correct?
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
You are correct.
popasmurfn23 said:
Yeah take out battery, then pull out sd card put it into a adapter and insert it to ur pc. Then find the file that was shipped specifically for ur device it looks something like this PC130mg.zip or some crap like that anyways put that on the root of your sd card. load ur card back to your phone now into hboot(volume down plus power) mode. Your phone will auto detect that file and start to ask if u want to install update say yes boom it will flash back to stock.....however my only concern would be if u need to turn s-ON before u do this.
I did this for a evo 4g and it worked but I turned s-ON first as it was in the instructions I was following. I think maybe the update file checks to see if ur S-off or on. But don't quote me on that.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
phaze one said:
Yeah, I agree with popasmurf. Put the PB31IMG.zip on your sdcard. Then let hboot discover and update it. It'll be back to stock and youll have to reroot but better than a paperweight.
You can find the image here -----> http://dougpiston.com/?page_id=108
I'm assuming you have a dinc.
sent by carrier pigeon
Click to expand...
Click to collapse
Thanks for the replies.
I tried this method to flash back to the stock 2.2 image before I started this thread. That's what I meant by "I've used HBOOT to ... run the 2.2 RUU." The stock image seemed to install properly in HBOOT. I have evidence that it successfully went back to stock, since I get the original ! triangle graphic instead of CWM when I try to enter recovery from HBOOT. However, I only see the graphic pop up for a brief second before it reboots again. Trying to boot into recovery or the ROM itself still result in a reboot.
I cannot achieve S-ON without having access to recovery, at least there's no way that I've found to do it through HBOOT.
Any other thoughts? I think it's a hardware problem. It appears the phone is back to stock (except it's still S-OFF), but everything outside of HBOOT causes a boot loop. I stopped in at Verizon this afternoon and they'll be sending a new phone to arrive by Tuesday. At this point, it'd be nice to try all avenues of repair for the future benefit of others that run into this problem.
Probably bad memory chips on the phone. Since it happened all of a sudden during normal use it usually indicates hardware failure.
That is pretty much what I determined. Bad hardware. Sorry for your trouble but is nice to know I'm not the only person to ever have this. Also nice to know I didn't miss something that could've brought it back to life.
I filed an insurance claim. Figured since I have had it for years and never used it I'd take advantage.
Sent from my ADR6300 using Tapatalk
You can boot your phone like regular right? Just let it launch up or do you get loops?
Nevermind i see what ur saying. when i was flashing incorrect kernals i would get the same behavior from my phone. So i suggest you take phazeones link and try that file.Because u might have the incorrect file. There might be more than meets the eye make sure u got the right file.
When i searched for my zip file for my evo there was like 4 of them. They had to match what was said in the upper left corner of my hboot screen. So let me knoe if it worked
I wonder if he could just wipe that SD card, place a new Rom etc on it and reinstall. Bricking displays no response you've got a better shot at recovering course your SD card/battery could be bad
Since you're trying to flash the 3.x.x.x version of CWM, that may be your issue. Here's a zip for 2.5.0.5, one of the most stable earlier Recoveries. Flash through hboot as per usual.
If that doesn't work, (I'm assuming that you can boot the phone normally at this point) try re-rooting with the Unrevoked tool.
Then use Rom Manager to flash a newer Recovery (be sure to check Erase Previous Recovery under Settings). If that still doesn't work, I'll see about packaging an RUU in a PB31IMG.zip with a valid version of CWM as the recovery.img within that zip. I'm not sure about the practicality of this final option, but if it comes down to it, I'll attempt to package that up for you.
This sounds incredibly frustrating. Thus my interest in the matter.
There's gotta be a way to fix this... even if it's just long enough to get S-On and keep your warranty valid.
Sent via my Incredible CM7 Gingerbread sorcery.
Crans said:
I wonder if he could just wipe that SD card, place a new Rom etc on it and reinstall. Bricking displays no response you've got a better shot at recovering course your SD card/battery could be bad
Click to expand...
Click to collapse
This would work if he could access CWM Recovery, but he can't, thus the issue.
I wonder if he could mount something from within hboot and replace the binary code for the recovery image with a bunch of zeroes and then try flashing another through hboot again.
Sent via my Incredible CM7 Gingerbread sorcery.
I was JUST about to post the same topic when I came across this. I have done the stock image restore, restored BACK to hboot 0.92, back to the most current INC radio, and have tried flashing CW3.0 and Amon_RA. Everything flashes fine but the boot loop continues and if I try to enter recovery, it lasts maybe one full second before rebooting again. The only thing that I can think of that would create this situation for me was that earlier I was trying to update the PRL via *228 on MIUI but the dialpad never popped up so I hung up.
popasmurfn23 said:
So i suggest you take phazeones link and try that file.Because u might have the incorrect file. There might be more than meets the eye make sure u got the right file.
When i searched for my zip file for my evo there was like 4 of them. They had to match what was said in the upper left corner of my hboot screen. So let me knoe if it worked
Click to expand...
Click to collapse
I'll take another crack at it, but I don't think I had gotten the wrong image. No worries though, it's easy enough to try again using the link on page 1 directly. Can't hurt, right ;-)
RegnierD said:
Since you're trying to flash the 3.x.x.x version of CWM, that may be your issue. Here's a zip for 2.5.0.5, one of the most stable earlier Recoveries. Flash through hboot as per usual.
Click to expand...
Click to collapse
Sure. Once again, worth a shot.
RegnierD said:
This sounds incredibly frustrating. Thus my interest in the matter.
There's gotta be a way to fix this... even if it's just long enough to get S-On and keep your warranty valid.
Click to expand...
Click to collapse
Thanks for the sympathy . Like I mentioned, I visited the Verizon store and a new one is on its way... doesn't that mean that it doesn't matter (other than for science sake) whether this gets S-On or even fixed?
[waiting for flash of build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip]
It just seems unlikely that this is a problem with flashing the wrong recovery, or the wrong stock image, since booting into recovery and booting normally both exhibit the same behavior. If I could boot normally into recovery but not boot into a stock image, I would suspect that I had flashed the wrong image. Since both have the same problem, I think it might be something else.
[finished flashing build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip]
Same behavior. White htc Incredible splash screen -> darkness for a second (presumably while the ROM tries to boot) -> reboot.
Alternatively, HBOOT -> Recovery -> White htc Incredible screen -> Triangle / ! error screen for a half second -> reboot.
[finished flashing CWM 2.5.0.5]
Same behavior:
HBOOT -> Recovery -> White htc Incredible screen -> CWM recovery 2.5.0.5 for a half second (this confirms that it flashed properly) -> reboot.
First, Sorry for my poor English, and thank you for reading this.
Please help me to escape from bricked phone!
At this point of time, I cannot determine the symptom wheter H/W related or S/W.
At HTC service center, they refuse to repair my DHD unless I restore bootscreen & S-off. However, my DHD is almost bricked (now stuck in first HTC logo) so I couldn't follow most of kindful guides in here.
Please let me determine the symptom, then I can give up if the problem is H/W related (and should pay almost $200 for fee), or I can continue to study in the case of S/W related problem.(Also I need some hints from you for finding solutions..)
Here are follow-up measures history.
Status of DHD at the accident
As-is Froyo
Rooted
S-OFF (eng off?)
ClockworkMod Recovery v3.0.2.5 installed
No more tuning except Camera and bootscreen.
Never applied OTA (in Korea, not yet released)
Click to expand...
Click to collapse
Recent suspected events:
1. Accidental battery remove during last drinking before 4 hours.
2. Waiting phone to turn off under 2% due to Battery calibration before 30 minutes
Click to expand...
Click to collapse
Just before outbreak:
1. I excuted two browsers (FF4, Dolphin). Using Recent apps,I switched from Dolpin to FF4.
Then suddenly reboot loop started
Click to expand...
Click to collapse
Bootloader information
ACE PVT ENG-OFF
HBOOT-0.85.2007 (PD9815000)
MICROP-0438
RADIO-26.03.02.26_M
eMMC-boot
Oct 11 2010, 12:44:14
Click to expand...
Click to collapse
Symptom 1
Endless reboot after showing bootscreen.
Measure 1-1
Using ClockworkMod recovery, I tried to restore /system from lastest backup many times.
= It gave me an error "Error while formatting /system"
Measure 1-2
Using ClockworkMod recovery, I tried to format /system many times.
= It gave me an error "Error while formatting /system"
Measure 1-3 (HTC service man)
He tried to update (overwrite) ROM using microSD card (maybe PD98IMG.zip method)
=Reboot loop continues
=tunned bootscreen and S-off was unchanged.
He refused to repair (M/B replacement) my DHD unless I restore bootscreen & S-off.
Click to expand...
Click to collapse
Measure 1-4
installing RUU by myself using USB Cable
(RUU_Ace_KT_KR_1.43.1010.2_Radio_12.28b.60.140e_26.03.02.26_M_release_158060_signed)
= failed. It couldn't find phone (I cannot enter android UI!).
installing RUU by myself using USB Cable
RUU_Ace_HTC_WWE_1.15.405.1_Radio_12.21.60.12_26.02.00.09_M_test_148662
= failed. It couldn't find phone (I cannot enter android UI!).
Measure 1-5
Wipe Dalvik Cache = no effect
Fix Permissionts = no effect
Wipe datafactory reset=no effect
Symptom 2
Now DHD is stuck in HTC logo.
Click to expand...
Click to collapse
Please help me to determine the problem!
Is it H/W related error?
If then, maybe no one can be fix my DHD except HTC service man.
Is it S/W related error?
If then, here are two questions.
Why "Error while formatting /system" occurs?
Can this be fixed without entering android UI?
(Becasue I can't enter..)
Or
Modified screen and S-off can be restored without entering android UI?
(Becasue I can't enter..) If done, service man will replace M/B.
Thank you for reading this long thread!
Hi,
Your English is perfectly understandable.
Firstly, did you try to partition your SDcard using ROM Manager or ClockworkMod recovery before all this occurred?
Ok, turn your phone off and head into the bootloader, then into fastboot.
Ensure you have the Android SDK installed as you need fastboot.exe
Plug in your phone to your PC and watch your phone's screen, FASTBOOT should now say FASTBOOT USB.
Open command prompt, and cd into your SDK\tools folder.
Now execute
Code:
fastboot devices
It should return
Code:
[B]HT~string of text~[/B]
Now download the PD98IMG.zip from THIS post.
Once downloaded. Unzip the archive to any folder. Open this folder and copy system.img, boot.img, data.img to your SDK\tools folder.
Now execute
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash data data.img
Wait for each one to complete before progressing to the next.
Now reboot your phone.
Hiya
I have exactly the same problem as the OP. While running the above fastboot commands on system.img i get the error FAILED <Remote:data length is too large>
I have tried flashing system, boot and userdata from a nandroid backup i have, which have all successfully flashed, but the phone still will not boot past the HTC screen
might sound daft, but have you considered reflashing with an RRU to see if that fix's your issue? once its up & running just re-root.
this post its duplicated... its the same that in general Q&A and i answered you the same that @andyharney sayd to you man.... read before post
SERGI.3210 said:
this post its duplicated... its the same that in general Q&A and i answered you the same that @andyharney sayd to you man.... read before post
Click to expand...
Click to collapse
sergi.3210?? the same sergi that its in htcmania.es????A few hours ago we have spoken there jajjaaja its strange see you speaking english
and u bro´ really really graceful for your help this afternoon i did it and my desire hd was gone out the bootloop... adb parameters are complicated for to me... but finally get it
now i´m reading for flash another radio... you have reason XDA is the most completly web for android lovers.. see you here "compadre"
aidan257 said:
might sound daft, but have you considered reflashing with an RRU to see if that fix's your issue? once its up & running just re-root.
Click to expand...
Click to collapse
My phone wont recognise the SD card, i have tried to flash a new rom by pushing it to /cache/ and pushing a command.txt file to /cache/recovery containing the command --update_package=CACHE:romname.zip, then rebooting into recovery, as i believe the phone should then unpack the rom and install it?
Needless to say it hasnt worked.
spike_14 said:
sergi.3210?? the same sergi that its in htcmania.es????A few hours ago we have spoken there jajjaaja its strange see you speaking english
and u bro´ really really graceful for your help this afternoon i did it and my desire hd was gone out the bootloop... adb parameters are complicated for to me... but finally get it
now i´m reading for flash another radio... you have reason XDA is the most completly web for android lovers.. see you here "compadre"
Click to expand...
Click to collapse
O...M...G...!!!! u again!!!!! LOL
welcome buddy..
you consummed 2 hours of my time to solve your bootloop and i see you here again
bnsonear said:
At HTC service center, they refuse to repair my DHD unless I restore bootscreen & S-off. However, my DHD is almost bricked (now stuck in first HTC logo) so I couldn't follow most of kindful guides in here.
Please let me determine the symptom, then I can give up if the problem is H/W related (and should pay almost $200 for fee), or I can continue to study in the case of S/W related problem.(Also I need some hints from you for finding solutions..)
Modified screen and S-off can be restored without entering android UI?
(Becasue I can't enter..) If done, service man will replace M/B.
Thank you for reading this long thread!
Click to expand...
Click to collapse
Tell him you will do that, if he can prove the software is under warranty, otherwise tell him to sod off.
So, if the RUU can't install, it is hardware related, and they should fix that regardless of the software if the phone is still under warranty (which it will be).
Thank you for your kindful response, andyharney.
Before start to follow your solution, I felt that I need to extend my understanding on android becasue I'm just a newbie and not developer. Therefore, I have some questions about the solution.
I would appreciate it if you could give answers.
Firstly, did you try to partition your SD card using ROM Manager or ClockworkMod recovery before all this occurred?
Click to expand...
Click to collapse
I heard that action above can cause some problems reading SD card. Dose my symptom related to SD card? I check my DHD couldn't boot even without SD card.
Click to expand...
Click to collapse
What a relief! I have never used that function.
Now download the PD98IMG.zip from THIS post.
Click to expand...
Click to collapse
1. Can I use original as-is image I wrote instead of that you recommanded? (Carrier is KT in Korea.) Why I have to downgrade? (I cannot understand version 1.7 or 1.3. What do they indicating?)
Or
2. Version change due to downgrade can be reversible? I'm very afraid of loss of warranty. I heard that Radio-OFF(I don't know well) is unreversible.
If you have the correct ROM/RUU for your carrier use that, otherwise the PD98IMG.zip I kinked to will have to do.
As you have already tried the PD98IMG.zip on its own to no avail, you have very few options remaining. One is to flash each component separately via fastboot.
You cannot restore S-ON unless your phone boots normally, which at the minute, doesn't
bnsonear said:
1. Can I use original as-is image I wrote instead of that you recommanded? (Carrier is KT in Korea.) Why I have to downgrade? (I cannot understand version 1.7 or 1.3. What do they indicating?)
Or
2. Version change due to downgrade can be reversible? I'm very afraid of loss of warranty. I heard that Radio-OFF(I don't know well) is unreversible.
Click to expand...
Click to collapse
hei @bnsonear! i just received your PM!
but i seen the all the thread and @andyharney answered all that you need to know
forget to downgrade nothing now okay.? downgrade its for another thing... andy was sent to you the link for take the pd98img.zip fine nothing more...
remember:
-you need to have sdk installed and drivers of htc sync.
-put your device in fastboot mode
-need the pd98img.zip for restore the rom (concretly 1.32xxx (then you can flash another rom)or
-you can flash your carrier official rom
-introduce the parameters that andy was provided to you avobe from the correctly folder of the sdk(IMPORTANT)not in the adb folder! are in another folder...
Hi,
I just installed the the Revolution ROM on my desire HD and then when i rebooted it it went straight to the revolution reboot menu....
As i am a NOOB i downloaded the Clockwork recovery, reinstalled the revolution rom but same thing happens...
When i reboot the system it starts up (HTC screen) turns off starts back up again and goes straight to "clockworkmod recovery" menu...
I cant even go to the original boot menu...
To make things worst i can only connect usb as storage...
Can anyone please identify my problem and make a step by step solution, as my knowlege on android phones is close to nothing :crying:
madskor said:
Hi,
I just installed the the Revolution ROM on my desire HD and then when i rebooted it it went straight to the revolution reboot menu....
As i am a NOOB i downloaded the Clockwork recovery, reinstalled the revolution rom but same thing happens...
When i reboot the system it starts up (HTC screen) turns off starts back up again and goes straight to "clockworkmod recovery" menu...
I cant even go to the original boot menu...
To make things worst i can only connect usb as storage...
Can anyone please identify my problem and make a step by step solution, as my knowlege on android phones is close to nothing :crying:
Click to expand...
Click to collapse
Did you do a full wipe (system, data, and cache) before flashing? Are you S-Off with AAHK or S-On with unlocked bootloader?
bananagranola said:
Did you do a full wipe (system, data, and cache) before flashing? Are you S-Off with AAHK or S-On with unlocked bootloader?
Click to expand...
Click to collapse
Yes, i did a full wipe before flashing...
I cant see if i´m S-ON or Off because i can´t go to the original boot menu, but i think its S-Off because the Rom that was in the phone before i messed with it was not the original
madskor said:
Yes, i did a full wipe before flashing...
I cant see if i´m S-ON or Off because i can´t go to the original boot menu, but i think its S-Off because the Rom that was in the phone before i messed with it was not the original
Click to expand...
Click to collapse
An unlocked bootloader with S-On still permits flashing of custom ROMs. Is your recovery updated? If not, do that.
bananagranola said:
An unlocked bootloader with S-On still permits flashing of custom ROMs. Is your recovery updated?
Click to expand...
Click to collapse
i dont know as i said i´m a huge noob when it comes to tecnology
isn´t there a way to do everythig again, but the right way ?
i already installed revolution 3 or 4 times and it installs just fine but wont start up the right way.... always comes back to this menu....
madskor said:
i dont know as i said i´m a huge noob when it comes to tecnology
isn´t there a way to do everythig again, but the right way ?
i already installed revolution 3 or 4 times and it installs just fine but wont start up the right way.... always comes back to this menu....
Click to expand...
Click to collapse
The guide in post #7 of the guide in my signature is pretty clear. Read that. What is important to know is whether your phone is S-On bootloader unlocked or S-Off. Since you didn't hang on the boot splash when you flashed ARHD, I'm guessing S-Off. But just to be safe: to find this information, reboot while holding power and volume-down. That is your bootloader, known as hboot. What does it say? Finally, my hunch is that you need to update your recovery. The guide has instructions for that, but basically, download the image to your computer and flash it from fastboot.
Oh, and you may need to install your drivers on your computer. Install HTC Sync from the HTC website.
bananagranola said:
The guide in post #7 of the guide in my signature is pretty clear. Read that. What is important to know is whether your phone is S-On bootloader unlocked or S-Off. Since you didn't hang on the boot splash when you flashed ARHD, I'm guessing S-Off. But just to be safe: to find this information, reboot while holding power and volume-down. That is your bootloader, known as hboot. What does it say? Finally, my hunch is that you need to update your recovery. The guide has instructions for that, but basically, download the image to your computer and flash it from fastboot.
Oh, and you may need to install your drivers on your computer. Install HTC Sync from the HTC website.
Click to expand...
Click to collapse
I´ve tried to turn the phone on wli holding power + volume, but the result is the same.... powers up then down then up again straight to clockwork...
can you give me the link to the instruction? i cant find them
What image do i have to download?
Sorry for all the questions..... and thanks for your patience
madskor said:
I´ve tried to turn the phone on wli holding power + volume, but the result is the same.... powers up then down then up again straight to clockwork...
can you give me the link to the instruction? i cant find them
What image do i have to download?
Sorry for all the questions..... and thanks for your patience
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1824379. But if power and volume-down (you're using down, not up, right?) boot into CWM, sounds like a problem with your volume buttons.
bananagranola said:
http://forum.xda-developers.com/showthread.php?t=1824379. But if power and volume-down (you're using down, not up, right?) boot into CWM, sounds like a problem with your volume buttons.
Click to expand...
Click to collapse
OMG.... huge noob mistake.... i was using the volume-up button.... you must be so mad at me right now
I can see it now.... on the top of the boot menu says: *** UNLOCKED *** ACE PUT SHIP S-ON...
so i guess you were right.... whats the best ting to do then?
I think it may something to do with the boot image but dont know how to fix it
Update recovery. Guide has instructions.
bananagranola said:
Update recovery. Guide has instructions.
Click to expand...
Click to collapse
Thank you for your patience... i´ll give it a try...
I´ve been trying to solve it by myself for the past 12 hours... i´m exausted
Hope this will fix it....
madskor said:
Thank you for your patience... i´ll give it a try...
I´ve been trying to solve it by myself for the past 12 hours... i´m exausted
Hope this will fix it....
Click to expand...
Click to collapse
When you're tired, it's best to get some sleep. Most mistakes happen when sleepy and tired (been there!) so I'd suggest a little shut-eye and continue then
Sounds to me like the problem will get solved pretty soon, just read the guides and don't rush things. If unsure, read the guide (for what-ever you are doing) a second or a third time and don't try doing many things at the same time (ie.don't try updating your radio, rom, & recovery all at the same time ).
Pretty much anything can be fixed as long as you got recovery working so don't stress too much. Best of luck and hope you get your phone working soon :good:
Still havn´t found a solution for my problem, but i think i´m on to something....
I think the problem with my phone is the boot.img.... i can´t flash it correctly...
Dont know what program to use or what file to download.... i tried openning a command list but i and type "fastboot flash boot boot.img" as i´ve seen on other posts but i always get "this is not known as an internal or external command, etc...."
What can i doooooooooooooo?!!!! going crazy with this
Hey buddy, stay calm haha. I had the exact same problem. The problem is that although you tried to flash it, you nee to have the boot.img and some files including fastboot.exe. All of the files you need and how to flash the rom are in a guide by glevitan. You can just google it.
Sent from my HTC Desire HD using xda app-developers app
TheJurgenp1 said:
Hey buddy, stay calm haha. I had the exact same problem. The problem is that although you tried to flash it, you nee to have the boot.img and some files including fastboot.exe. All of the files you need and how to flash the rom are in a guide by glevitan. You can just google it.
Sent from my HTC Desire HD using xda app-developers app
Click to expand...
Click to collapse
I´m trying to keep my cool .... hehehe
the problem is just that... i already googled so many solutions an tried so many things i´m starting to loose hope...
I´m a noob when it comes to these things...
and the fact that english is not my native thong doesnt help either... there are some expressions i dont understand...
Do you still have the link to that solution you mentioned?
You need drivers. Install HTC Sync from the HTC website.
bananagranola said:
You need drivers. Install HTC Sync from the HTC website.
Click to expand...
Click to collapse
already done that... on clockwork recovery mode i can mount usb storage and have access to sd card... that means the drivers are ok... right?
also tried to instal fastboot on my pc but when i clic on the application it doesnt open the cmd window....
what else should i do?
You need to type fastboot from the cmd.
bananagranola said:
You need to type fastboot from the cmd.
Click to expand...
Click to collapse
already did but it wont recognize the command
Then your drivers aren't working. Uninstall and reinstall with the phone unplugged.