Develop Bugs

AlphaRevX creating issues in GB upgrade

I have a Dinc2 on Froyo. I had got S-off using AlphaRevX. No problems here. I got hold of Gingerbread 2.3.3 (PG32IMG_RUU_Vivo_W_VERIZON_WWE_2.18.605.4_Radio_1.09.01.0622_NV_VZW1.92_release_200325_signed)
Yesterday, when I flashed it it flashed Ok except that the Bootloader and TP were bypassed. Now I am unable to root it and if I reboot into recovery (the battery has to be pulled out and put back else it boots normally). If I select recovery it flashes one screen and then the second screen just hangs. The recovery screen is still Green (not orange). The phone is working fine in GB and the version is shown as 2.3.3. It is faster and the battery life also seems to be longer. I guess the Bootloader and TP were not installed since AlphaRevX had changed the version of HBOOT. I still have S-off.
Two questions:
1. Is there a way to fix this.
2. If I flash the Chinese ROM and go to 2.3.4 then will it fix the problem. Also, do all the files-ROM, Radio & GoogleApps (sequentially of course) have to be named PG32IMG?

You may have to find a new version of CWM, and flash via boot loader.
Although, I may be wrong. Hopefully you'll get more answers.
Sent from my Incredible 2 HD using Forum Runner

Ya load another recovery. Also try pressing the vol - and power when it goes to the second screen. I thought I bricked my of since and did that out of anger and the crappy normal recovery came up
Sent from my ADR6350 using xda premium

faehsemc said:
Ya load another recovery. Also try pressing the vol - and power when it goes to the second screen. I thought I bricked my of since and did that out of anger and the crappy normal recovery came up
Click to expand...
Click to collapse
No luck with <Vol> + <Power> from 2nd screen.
I was able to enter the HBOOT mode without having to pull the battery out. I took this chance to note the contents
----AlphaRevX----
VIVO_W XB SHIP S-OFF RL
HBOOT-6.13.1002
RADIO-1.09.01.0622
Apr 1 2011, 18:34:39
HBOOT
<normal three options>
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
HBOOT USB
IMAGE CRC
reload another recovery - sounds Greek + Latin to me.
@TYLERLAWOHN; where do I get the newer CWM.
It has been suggested that I do a factory reset and then reload. Seems that TP is the culprit. My query is that will a factory reset put paid to the prl and/or the crack (both CDMA and GSM).

http://forum.xda-developers.com/showthread.php?p=15981566
Choose one of these. It's cwm. Probably an older version but if it flashes the recovery then all you need to do is a restore

sgiitk said:
No luck with + from 2nd screen.
I was able to enter the HBOOT mode without having to pull the battery out. I took this
----AlphaRevX----
VIVO_W XB SHIP S-OFF RL
HBOOT-6.13.1002
RADIO-1.09.01.0622
Apr 1 2011, 18:34:39
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
HBOOT USB
IMAGE CRC
reload another recovery - sounds Greek + Latin to me.
@TYLERLAWOHN; where do I get the newer CWM.
It has been suggested that I do a factory reset and then reload. Seems that TP is the culprit. My query is that will a factory reset put paid to the prl and/or the crack (both CDMA and GSM).
Click to expand...
Click to collapse
Reply deleted

faehsemc said:
http://forum.xda-developers.com/showthread.php?p=15981566
Choose one of these. It's cwm. Probably an older version but if it flashes the recovery then all you need to do is a restore
Click to expand...
Click to collapse
Thanks for saving my bacon. Picked up the red. Installed recovery. Back to Froyo. Should I risk the Chinese 2.3.4, or will the AlphaRevX HBOOT again baulk me?

Don't know man, bit if it does you can re download the red and should be able to start over.
Sent from my ADR6350 using xda premium

I have finally managed. The full story is
1. Used the PG32IMG route for the Verizon version (PG32IMG_RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.4.zip) and the recovery (red). Of course had to disable fastboot etc..
2. Then installed the two superuser files. (su-bin-3.0.3.2-efghi-signed.zip and superuser-3.0.7-efghi-signed.zip) through recovery.
3. Had to get Astro file manager to get the apk installer going from SD Card.
4. Titanium Pro not installing, even with busybox installed it was the same.
5. Moved the Devanagri fonts to the system/fonts director, so obviously have ROOT.
6. Installed clockworkmod. It restored 26 apps. Only a few were missing.
Installed the latest freebie version of Titanium.
7. Ookla speedtest was not working so reinstalled it from Titanium.
System seems to be working fine. Faster and lower power consumption.
Still unable to save/restore contacts to from Google.

faehsemc said:
you have an Incredible S Hboot for the Inc 2... i think you need to look for a new RUU altogether and get the original Hboot back...
Click to expand...
Click to collapse
I have that same hboot and I never even smelled a DInc s ROM.
Are you sure that's a different one then yours?
I may be wrong but,
I think it's a Revolutionary hboot and unless you did the clip, it's the same as yours.

cac2us said:
I have that same hboot and I never even smelled a DInc s ROM.
Are you sure that's a different one then yours?
I may be wrong but,
I think it's a Revolutionary hboot and unless you did the clip, it's the same as yours.
Click to expand...
Click to collapse
You are right, It's the revolutionary... I was stupid and thinking that we need to downgrade from 98 to 97 and then thinking 97 was the hboot number...
Sent from my ADR6350 using xda premium

Yea watch vzw come up with a 1003 bootlocker.
Or try some kind or OTA AppHolized disabling of the SD card.

Constant bootloop

My Incredible is in a bootloop. I have gone back to stock. The phone will work for a few minutes then just reboot non-stop. I did a factory reset and that did not help.
I can't keep the phone on long enough to do anything. The irony in all of this is that it started to do this 2 weeks after I became eligable for an upgrade...
Smells fishy...now I either wait for Incredible 4G or get the Rezound.
[email protected] Verizon...

Do you have a recovery on the phone still or did you get rid of it when returning to stock? I'm not sure I've heard of this before but if you post the status of your hboot that might be able to help someone help you.
and personally between the two I would go with the Incredible 4G but that's just me being loyal to HTC i guess.

Recovery is gone/does not work. I'll post the HBOOT version later, don't have the phone atm.

binaryhat said:
Recovery is gone/does not work. I'll post the HBOOT version later, don't have the phone atm.
Click to expand...
Click to collapse
Post hboot version, s-on or off, and current android version.

cmlusco said:
Post hboot version, s-on or off, and current android version.
Click to expand...
Click to collapse
Will do tomorrow...left the phone at work.

S-off
HBOOT-0.92
Radio-2.15.00.07.28
Stock Android

I know it sounds very round-about but you may need to flash CWM back on to the phone so you can flash unrevoked's s-on tool, I don't know for sure that this is what is causing the problem but you want s-on when you are in stock, especially if you plan on giving the phone to Verizon- if it has been messed with they won't want to handle it because they will say it is not their problem. (I have heard that Verizon has admitted to not checking very carefully, but it can't hurt to be careful yourself)

How can I flash CWM if I can't keep the phone on for more than a minute?

sounds like your kinda having the same problem i am having. the difference is my is s-on. i can get to hboot but when i try to go to recovery from there it comes up with a bunch of errors. and mine just bootloops at the droid eye.

that is a very valid point. It still can't hurt to try, I remember when I rooted my phone, it didn't take all that long to flash CWM.
You also might want to consider booting into safe mode to see if that keeps in on longer, I am copying and pasting these instructions from technipages.com because xda won't let me post links until they trust me more or something:
Sometimes services and apps you install on your HTC Droid Incredible can interfere with its functionality. If you’ve reached a point where the phone freezes at startup or malfunctions in a way that you can’t remove the problem, Safe Mode is the answer. Booting in Safe Mode will load only software and drivers from factory defaults. This should allow you access to remove whatever ails your smartphone.
1. Turn the device off. If the power button doesn’t do the trick, remove and replace the battery.
2. Power the device on.
3. When the logo appears, press and hold the Menu button.
4. Continue holding the Menu button until you see the home screen.
The words Safe Mode should appear in the lower left corner if you performed the steps correctly.
Click to expand...
Click to collapse
I apologize if you don't have any luck, but I am only trying to help

I'll try safe mode (should have) and see if that works.

binaryhat said:
I'll try safe mode (should have) and see if that works.
Click to expand...
Click to collapse
Does the phone shut off when your in hboot too? You need to do as sugested and flash cwm thru hboot, and then see if you can access recovery long enough to wipe everything in mounts and storrage except sd and emmc, then flash superuser, and a rom.

scoobntaz1996 said:
sounds like your kinda having the same problem i am having. the difference is my is s-on. i can get to hboot but when i try to go to recovery from there it comes up with a bunch of errors. and mine just bootloops at the droid eye.
Click to expand...
Click to collapse
Whats your hboot and android version? Have you tried an ruu?
EDIT: Nevermind i forgot i was allready talking to you in the other thread.

[Q] HTC G2 stuck on boot screen! Help!

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

Not working camera, volume buttons and headphone slot with rooted dhd

i am new here and i am writing you guys to
please help me out in this matter. I got my HTC
DESIRE HD rooted from my friend and i was
playing with it by flashing different roms
through Clock-Work-Mod. One day i dont know
what went wrong when i was flashing a new
rom. A message was displayed on the CWM that
installation aborted and some error appreared.
At that moment i got panic and didnt wipe off
this rom data and flashed the other one i had.
Everything went perfectly fine and mobile
restarted. When i tried to work the volume
buttons they are not working, i tried camera out,
No response....I put headphones in its slot but
nothing is working.
GUYS mind you that i was having a backup for
my roms when everything was working fine. I
restored them but still the same problem. And
volume keys are not either working in
CLOCKWORKMOD. I tried different stuff means
wiping all the data and cache and whatsoever.
Nothing is happening for me.
PLEASE HELP ME OUTTTTTTTTT...HELPPPPPP
MEEEEE.... I LOST MY WARRANTY AND NOW I
DON WANA LOSE MY PHONE...PLEASE
HELPPPPP!!!!!!!!

Search for 4ext touch recovery, flash that, full wipe, flash rom, see if that helps.
Sent from a dream.

Teichopsia said:
Search for 4ext touch recovery, flash that, full wipe, flash rom, see if that helps.
Sent from a dream.
Click to expand...
Click to collapse
Dear Sir,
Thanks for your reply....I tried everything out but nothing is working. Even my friend rebooted receovery and bootloader. After that even i installed a stock ROM using ADB from HTC....still camera, volume buttons and earphone slot not working,
I request you to please give me detail answer and a way out except these i have mentioned as i am in real fix..
Thanks once again for your kind support.

adnanf said:
Dear Sir,
Thanks for your reply....I tried everything out but nothing is working. Even my friend rebooted receovery and bootloader. After that even i installed a stock ROM using ADB from HTC....still camera, volume buttons and earphone slot not working,
I request you to please give me detail answer and a way out except these i have mentioned as i am in real fix..
Thanks once again for your kind support.
Click to expand...
Click to collapse
If you used adb then you know more than I do.
The only thing I can think of is if you are full wiping.
Booting into recovery
Wipe data/factory reset
Wipe dalvik
Format all partitions except sd card.
I suggested to get 4ext touch becauee you can use the screen to navigate in the recovery section instead of the volume buttons to format and flash.
If you are having hardware issues, could it be a hardware problem? It happebed after you got nervous which leads to believe it may be software related. But if you flashed a stock rom using adb, did that fully wiped your phone? I don't know.
If it didn't, try a full wipe.
Read this only for informational purposes. Don't try anything until you are sure it's not software related.
http://forum.xda-developers.com/showthread.php?p=29603104
Sent from a dream.

Teichopsia said:
If you used adb then you know more than I do.
The only thing I can think of is if you are full wiping.
Booting into recovery
Wipe data/factory reset
Wipe dalvik
Format all partitions except sd card.
I suggested to get 4ext touch becauee you can use the screen to navigate in the recovery section instead of the volume buttons to format and flash.
If you are having hardware issues, could it be a hardware problem? It happebed after you got nervous which leads to believe it may be software related. But if you flashed a stock rom using adb, did that fully wiped your phone? I don't know.
If it didn't, try a full wipe.
Read this only for informational purposes. Don't try anything until you are sure it's not software related.
http://forum.xda-developers.com/showthread.php?p=29603104
Sent from a dream.
Click to expand...
Click to collapse
It is all software related, well i tried everything but the same...it is not a harware problem. I think the rom that had an error when i was flashing it had a bad impact on my media driver. I don't know how to fix this crap now....please keep posting and keep in touch...and do ask your friends to fix this issue if you could please.
Thanks once again

adnanf said:
It is all software related, well i tried everything but the same...it is not a harware problem. I think the rom that had an error when i was flashing it had a bad impact on my media driver. I don't know how to fix this crap now....please keep posting and keep in touch...and do ask your friends to fix this issue if you could please.
Thanks once again
Click to expand...
Click to collapse
Could you post what you did when it went bad and what you have done so far step by step? Just want to make sure what has been done.and as concise as possible please. If you don't mention something I/we will assume you didn't do it and we will tell you to do it again.
Sent from a dream.

Teichopsia said:
Could you post what you did when it went bad and what you have done so far step by step? Just want to make sure what has been done.and as concise as possible please. If you don't mention something I/we will assume you didn't do it and we will tell you to do it again.
Sent from a dream.
Click to expand...
Click to collapse
when i was flashing a new ROM through CWM then an error appeared stating installation aborted...I got panic and when this error appeared....i just flashed the other ROM...but i didn't wipe the data of the Error making ROM...I think that is why this problem happened...but new ROM was flashed successfully and when i tried to work volume keys in the ROM and in CWM they were not working, Camera and Earphone slot wasn't working as well....After that i tried 4EXT Recovery to wipe everything and flashed the ROM once again but same problem for every ROM..Even i Recently flashed an RUU Stock HTC ROM VIA ADB but same....Please help!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

I can't help your problem, but if everything is really down and you're back on stock ROM, without root, go and complain to HTC and whatever your service provider is. Pretend like you don't know what happened. If you have a good provider, or if your phone warranty hasn't expired yet, then they should fix it for you.

xxkid123 said:
I can't help your problem, but if everything is really down and you're back on stock ROM, without root, go and complain to HTC and whatever your service provider is. Pretend like you don't know what happened. If you have a good provider, or if your phone warranty hasn't expired yet, then they should fix it for you.
Click to expand...
Click to collapse
As i have told you.....I dowloaded one ROM from XDA-Developers website...I wanted to flash it...I flashed it with CLOCKWORKMOD after going into recovery....while flashing i got an error that installation aborted...i didn't reboot my phone as i knew that this ROM will not work as it gave an error..I went to the folder where i kept other ROMS and flashed one of them but i didn't wipe out the data, Cache etc of this ERROR ROM this time and flashed other one..After that this problem happened...
I used 4EXT Recovery after that to wipe data again and flash another ROM...I flashed many ROMS after that but same....camera, Volume keys and earphone slot is not working....
Someone told me to flash an RUU that will overwrite all the previous data by using ADB....i did it as well...Everything went fine again....ROM was flashed....but F**king problem remains the same....

adnanf said:
As i have told you.....I dowloaded one ROM from XDA-Developers website...I wanted to flash it...I flashed it with CLOCKWORKMOD after going into recovery....while flashing i got an error that installation aborted...i didn't reboot my phone as i knew that this ROM will not work as it gave an error..I went to the folder where i kept other ROMS and flashed one of them but i didn't wipe out the data, Cache etc of this ERROR ROM this time and flashed other one..After that this problem happened...
I used 4EXT Recovery after that to wipe data again and flash another ROM...I flashed many ROMS after that but same....camera, Volume keys and earphone slot is not working....
Someone told me to flash an RUU that will overwrite all the previous data by using ADB....i did it as well...Everything went fine again....ROM was flashed....but F**king problem remains the same....
Click to expand...
Click to collapse
I tried re rooting my desire HD when it was already rooted and S-OFF...Now it got stuck on white screen....with green HTC logo...I can go into the boot loader....i tried flashing recovery Clockwork...With great difficulty i flashed recovery via ADB commands..by watching on internet...Now same volume keys are not working in Recovery..I want to flash 4EXT recovery...Please tell me how to do it while i am in bootloader....plzzz plzzzzz i am in a great FIXXXXXXXX....

adnanf said:
I tried re rooting my desire HD when it was already rooted and S-OFF...Now it got stuck on white screen....with green HTC logo...I can go into the boot loader....i tried flashing recovery Clockwork...With great difficulty i flashed recovery via ADB commands..by watching on internet...Now same volume keys are not working in Recovery..I want to flash 4EXT recovery...Please tell me how to do it while i am in bootloader....plzzz plzzzzz i am in a great FIXXXXXXXX....
Click to expand...
Click to collapse
flash it used fastboot (adb tools)
1.Turn off your phone
2. Hold the volume down button + power until you boot to a white screen.
3. Use the volume rocker to select FASTBOOT then press the power button to select it.
4. Connect your phone.
5. Open up a windows command prompt and navigate to your sdk tools or platform tools folder. tools (c:\android-sdk-windows\tools) or platform-tools (c:\android-sdk-windows\platform-tools) (ore where you have the adb)
6. Type FASTBOOT DEVICES to make sure your computer "sees" your phone and is ready to flash the recovery. You should get a serial number and then the word fastboot as the output.
7. Type fastboot flash recovery recovery.img and press enter. Give it a minute to do it's thing. You should get a message that says writing recovery and success.
(you must have the recovery.img on the same place as fastboot)
8. Unplug your phone and use the volume rocker to select BOOTLOADER and then again to select RECOVERY and you should be booted into the 4ext recovery

gurby1 said:
flash it used fastboot (adb tools)
1.Turn off your phone
2. Hold the volume down button + power until you boot to a white screen.
3. Use the volume rocker to select FASTBOOT then press the power button to select it.
4. Connect your phone.
5. Open up a windows command prompt and navigate to your sdk tools or platform tools folder. tools (c:\android-sdk-windows\tools) or platform-tools (c:\android-sdk-windows\platform-tools) (ore where you have the adb)
6. Type FASTBOOT DEVICES to make sure your computer "sees" your phone and is ready to flash the recovery. You should get a serial number and then the word fastboot as the output.
7. Type fastboot flash recovery recovery.img and press enter. Give it a minute to do it's thing. You should get a message that says writing recovery and success.
(you must have the recovery.img on the same place as fastboot)
8. Unplug your phone and use the volume rocker to select BOOTLOADER and then again to select RECOVERY and you should be booted into the 4ext recovery
Click to expand...
Click to collapse
I loved the way you told me brother...and i successfully flashed my ROM....I really loved the way step by step....I am really thankful to you....Can you help me in fixing my camera, volume buttons and earphone slots as they are still not working....PLEASE..I messed my mobile UP...HELP me brother

adnanf said:
I loved the way you told me brother...and i successfully flashed my ROM....I really loved the way step by step....I am really thankful to you....Can you help me in fixing my camera, volume buttons and earphone slots as they are still not working....PLEASE..I messed my mobile UP...HELP me brother
Click to expand...
Click to collapse
Are you eng-off it can be your kernel

gurby1 said:
Are you eng-off it can be your kernel
Click to expand...
Click to collapse
I don't know about eng off but yes I think I am....I am s off by the way...I ll paste here all the info in the bootloader shortly...please help brother
My bootloader says this
******AAHK*******
ACE XA ENG S-OFF RL
HBOOT-0.85.2425
MICROP-0438
RADIO-26.03.02.26_M
eMMC-boot
Now suggest...whatelse can i do to get them working..Voume buttons,a camera and earphone slots are not working for any of the ROM i flash...
HELP!!

adnanf said:
I don't know about eng off but yes I think I am....I am s off by the way...I ll paste here all the info in the bootloader shortly...please help brother
My bootloader says this
******AAHK*******
ACE XA ENG S-OFF RL
HBOOT-0.85.2425
MICROP-0438
RADIO-26.03.02.26_M
eMMC-boot
Now suggest...whatelse can i do to get them working..Voume buttons,a camera and earphone slots are not working for any of the ROM i flash...
HELP!!
Click to expand...
Click to collapse
Uhm if you go to the thread of android revolution. On the buttom of the page is a program superwipe trie that.
If that not help than can you replace the boot loader I will explain how you do that (your hboot is very old I have 2.xx. xxxx think that's you problem)

gurby1 said:
Uhm if you go to the thread of android revolution. On the buttom of the page is a program superwipe trie that.
If that not help than can you replace the boot loader I will explain how you do that (your hboot is very old I have 2.xx. xxxx think that's you problem)
Click to expand...
Click to collapse
I downloaded that and flashed it via 4EXT recovery...It wiped all the stuff.....after that now i flashed the rom....but the same problem......I don't know what is going on...
HTC workshop are saying that they will have to change the motherboard, camera, volume keys and all that...I dont think they know this problem...
Does it cause any problem if i download any ROM not for DHD and try to flash it?...This is why problem happened i guess...the ROM i flashed was not for DHD....
If you could please provide me your yahoo or hotmail ID..so that i could chat with you to clarify issues...Please give me a reasonable time if you could come online....
I would really be grateful to you...

Please reply reply to my questions above....i really am in a FIX....please help brother....

Replacement Battery, Or broken phone?
Looking to replace this naff ass broken "replacement HTC Desire HD" battery. Any suggestions? Are these High Capacity Gold battierys any use?
This battery if I turn the phone on it then powers off as dead. Unless I have it connected to a charger first. Then I can see the battery is actually got a charge in it.
Is this the battery of perhaps an issue with the phone?

[Q] One M8 Stuck on Logo...Period

I am in need of some serious help. My AT&T M8 won't boot past the HTC logo screen and won't allow me to go into recovery or the hboot screen. I believe I may have wiped the OS on it; this is the only thing I can think of that makes sense. Furthermore, when I try to power down the device by long pressing the power button, it doesn't respond at all. It just stays on the logo screen. It was so bad that I just left it plugged in overnight and I don't have a clue as to how long it took to power off because I fell asleep before it did. If there's a video tutorial out there that someone has or simply a link that can show me how to install something via backdoor on this device, that would be great!

alpinesun said:
I believe I may have wiped the OS on it; this is the only thing I can think of that makes sense. !
Click to expand...
Click to collapse
Recount as best you can, all the steps that got the phone to this point.
What were you trying to do when this happened?
Also, need much more info in order to help:
1) bootloader unlocked?
2) custom or stock recovery
3) custom ROM?
4) what hboot number?
5) s-on or s-off
6) did you make a nandroid with custom recovery?
alpinesun said:
Furthermore, when I try to power down the device by long pressing the power button, it doesn't respond at all. It just stays on the logo screen.
Click to expand...
Click to collapse
Hold power and vol up for several seconds to force a reboot. The moment the screen goes dark to reboot, let go of those buttons, and just hold vol down. Don't let go until the hboot screen appears.

Thanks already. I didn't realize I had to hold down the volume down button after it goes dark. It got me into twrp. I believe I should be good from here after I download a new rom to sideload. But to give you a run down, I was prepping the phone to sell it by wiping the data and installing the rom the guy said he wanted on it. When I was going thru the normal procedure to install the rom (wipe, flash, etc) that's when the phone started sticking on the logo screen. My assumption was that I downloaded a bad rom, so since then I've been trying to get back into twrp so I can load a new rom and finally was able to after you told me this. I'll report back if a new rom actually didn't help the situation. I only thought I wiped the OS because something similar happened with my Note when I was tinkering and that was the result.

alpinesun said:
I'll report back if a new rom actually didn't help the situation.
Click to expand...
Click to collapse
If you need any further help, please answer all the questions I previously asked.
Good luck.

redpoint73 said:
Recount as best you can, all the steps that got the phone to this point.
What were you trying to do when this happened?
Also, need much more info in order to help:
1) bootloader unlocked?
2) custom or stock recovery
3) custom ROM?
4) what hboot number?
5) s-on or s-off
6) did you make a nandroid with custom recovery?
Hold power and vol up for several seconds to force a reboot. The moment the screen goes dark to reboot, let go of those buttons, and just hold vol down. Don't let go until the hboot screen appears.
Click to expand...
Click to collapse
So, it seems I'm still having the problem, even while trying to install cyanogen. Here are the answers to those questions...
1) bootloader unlocked?... YES
2) custom or stock recovery... TWRP
3) custom ROM?... It was a custom AOSP Rom
4) what hboot number?... 3.16.0.0000
5) s-on or s-off... S-OFF
6) did you make a nandroid with custom recovery?... It was erased
Any help you can give from this point would be awesome. Thanks again!

alpinesun said:
So, it seems I'm still having the problem, even while trying to install cyanogen.
Click to expand...
Click to collapse
Failure to flash ROMs can often be solved with fastboot erase cache, then install TWRP by fastboot again. Update TWRP version, if you are using an outdated one.
Also, if you try to flash any ROMs based on Sense software beyond version 1.x (huge majority of them are past 1.x at this point) you will likely experience extremely long boot times (10 minutes or more) and broken WiFi due to outdated firmware. But CM should be okay.
alpinesun said:
6) did you make a nandroid with custom recovery?... It was erased
Click to expand...
Click to collapse
It was erased, or you wiped it?

Okay. Do you suggest trying an older sense rom to see if it works? The last time touched the phone was when I picked up my Note 4, so I will look for something that predates that.
As for the nandroid being erased, I can only assume it was my actions that caused it to be deleted, but I don't recall intentionally doing it.

alpinesun said:
Okay. Do you suggest trying an older sense rom to see if it works?
Click to expand...
Click to collapse
Sure, it couldn't hurt. With your current firmware, you will need a ROM based on 1.x software. There aren't a heck of a lot of those left. But there are a few. GoldenEye is one I can personally vouch for, since I was running it for a while back in the day:
http://forum.xda-developers.com/showthread.php?t=2705640
But I would definitely recommend just trying fastboot erase cache and re-install TWRP first. I've lost count how many times suggesting this simple fix has helped other users here on XDA, when ROMs fail to flash.
alpinesun said:
As for the nandroid being erased, I can only assume it was my actions that caused it to be deleted, but I don't recall intentionally doing it.
Click to expand...
Click to collapse
Fair enough. Just FYI, don't do a factory reset in bootloader (in the OS settings or recovery is OK). On modded phones this may cause the internal storage to become corrupted. Nandroids have sometimes been lost this way. This may or may not be what happened to you. Just wanted to throw that out there.
Also, there has been the occasional occurrence of internal storage being corrupted, possibly by TWRP. It may not even have been something you caused.