Related
hey
i am trying the whole day to fix my phone. but i guess it is almost imposible :/
i can't get in recovery mode (nothing happens) and can't turn in on (only vibrates once, black screen)
i have been told to download to download
OTA_Bravo_Froyo_HTC_WWE_2.29.405.5-2.29.405.2_releasedauhl6jhok5cmdm6.zip
and rename it to PB99IMG.zip and put it on sd, which i did, but how can i flash it if my recovery mod can't start up?
please help?
ANY suggestions???? please heeelp! :/
It would be helpful it you told us what you did to get your phone into this state.
Can you get into fastboot? (power on while pressing back-button)
Tillus said:
It would be helpful it you told us what you did to get your phone into this state.
Click to expand...
Click to collapse
i installed
RUU_Bravo_HTC_Europe_1.15.405.1_Radio_32.30.00.28U _4.05.00.11_release_121684.exe
via fastbooth
do you know what to do... please say yes
Tillus said:
It would be helpful it you told us what you did to get your phone into this state.
Can you get into fastboot? (power on while pressing back-button)
Click to expand...
Click to collapse
no i can't get into fast boot... ://
I suggest you read the notice from jcase... I'm guessing you were runiing gb?
Sent from my ADR6400L using XDA Premium App
you ruu was too old - this version doesn't have the required drivers for SLCD.
That means, you phone probably does work, but the screen is black.
I don't know how to solve this (probably by flashing the newer RUU, Version 2.29....) exactly, but hopefully this gives you a clue where to look for a fix.
There were many people experiencing this after Froyo was available. They did the ota-update, then noticed, that it wasn't possible to root with the new bootloader (Version 0.93ish) at that time, which was installed along with the froyo-ota, so they tried to downgrade back to 2.1 and ended up where you are. (bootoader .80 instead of .83ish).
Richpopski123 said:
I suggest you read the notice from jcase... I'm guessing you were runiing gb?
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
jcase??
i had this rom
http://forum.xda-developers.com/showthread.php?t=1040121
which didn't work and because of it i couldn't restore any of my previous roms. that is why i had to flash a rom from my computer fastbooth
have u any suggestions what should i do?
Tillus said:
you ruu was too old - this version doesn't have the required drivers for SLCD.
That means, you phone probably does work, but the screen is black.
I don't know how to solve this (probably by flashing the newer RUU, Version 2.21....) exactly, but hopefully this gives you a clue where to look for a fix.
There where many people experiencing this after Froyo was available. They did the ota-update, then noticed, that it wasn't possible to root with the new bootloader (Version 0.93ish) at that time, which was installed along with the froyo-ota, so they tried to downgrade back to 2.1 and ended up where you are. (bootoader .80 instead of .83ish).
Click to expand...
Click to collapse
yes... that makes sense. but does really no one have any clue what to do?? i worked the whole summer for this phone and now is gone
http://forum.xda-developers.com/showthread.php?t=748498
Probably the easiest and safest way ist to boot into fastboot although you don't see it and flash the newsest ruu,
so:
1) make sure, phone is off (i.e. pull battery and put back in)
2) push and hold "back" and hit power.
3) wait 30 seconds or so, to be on the safe side
4) connect phone to pc via usb
5) run RUU on PC, version 2.29.405... (RUU, not OTA!)
And make sure to have some juice in your battery
Here you can get the RUU:
RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe
Its on >>Shipped Roms<< , 7th from top.
btw. am I assuming correctly that your phone is unbranded?
btw2: Do it all on your own risk. I'm trying to help, but I dont want to be held resposible, if something goes wrong, so maybe wait for someone else to confirm
Tillus said:
Here you can get the RUU:
RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe
Its on >>Shipped Roms<< , 7th from top.
btw. am I assuming correctly that your phone is unbranded?
btw2: Do it all on your own risk. I'm trying to help, but I dont want to be held resposible, if something goes wrong, so maybe wait for someone else to confirm
Click to expand...
Click to collapse
how do i know that?
can u please stick with me... i will try to do that now
i apriciate your help... i think that nothink worse can be done to my phone, so i will try
did you see any provider logo during startup? Or any preinstalled apps or bookmarks which point into a provider's direction? Where did you buy it? And did you need a goldcard for rooting?
if you answer is no on every question, you're probably not branded.
Did you write down the version number before you did anything to your phone (when you have a .405. in your version number, your phone is definitely not branded).
Edit: but I really recommend to read the linked thread. My device is unbranded amoled so I never did any of this myself (apart from running a RUU), so always think twice before following my steps
Tillus said:
did you see any provider logo during startup? Or any preinstalled apps or bookmarks which point into a provider's direction? Where did you buy it? And did you need a goldcard for rooting?
if you answer is no on every question, you're probably not branded.
Did you write down the version number before you did anything to your phone (when you have a .405. in your version number, your phone is definitely not branded).
Edit: but I really recommend to read the linked thread. My device is unbranded amoled so I never did any of this myself (apart from running a RUU), so always think twice before following my steps
Click to expand...
Click to collapse
i hope its not branded
do i need to click od hold power button?
like you do, when you power on. The important part is to hold "back" while powering on
Tillus said:
like you do, when you power on. The important part is to hold "back" while powering on
Click to expand...
Click to collapse
do i have to hold down like 30 sec? no right?
i think this won't work
if i go to the sotre and give the device back... what would be a good excuse for phone not working?
jann32 said:
do i have to hold down like 30 sec? no right?
Click to expand...
Click to collapse
no. You have booted into recovery before, didn't you? Now you do the same but use "back" instead of vol- , because you want to boot into fastboot.
All I wanted to say with this 30 seconds is to give it some time to boot into fastboot, thats all. Press and hold "back", press "power", release power, wait 3 seconds, release "back", wait 10 seconds and plug in usb, start ruu.
Thats all I wanted to say with my previous post. Sry, if it was confusing
Tillus said:
no. You have booted into recovery before, didn't you? Now you do the same but use "back" instead of vol- , because you want to boot into fastboot.
All I wanted to say with this 30 seconds is to give it some time to boot into fastboot, thats all.
Click to expand...
Click to collapse
will try again
will the phone vibrate?
YES YES YES its upadatinjg.... hope this works
...my screen is back... but hopefully it finishes correctly... and doesn't go black again
what will happen if the phone is branded?
can i unbrand it?posebly not? cause its bricked ight? :/
no.
10charrrrr
If it is branded, you get a cid-error, so ruu wont finish. But your phone probably isn't branded, otherwise you would have come across problems during flashing custom roms or/or radios (-->goldcard). And because this doesn't seem to be the case, your device is not branded.
When the RUU is done, you phone is completely back to stock and you can do whatever you like to it...
Tillus said:
no.
10charrrrr
Click to expand...
Click to collapse
my phone works!!
i can not tell u how greatfull i am
THANK U
thank u for sticking with me again
Thanks to Calkulin, Dougpiston, and bwthor20 for this fix. It was too late for me, but hopefully not for you. My situation was, after flashing a rom, I was suddenly S-On without recovery. DO NOT FLASH THE RUU!!!!! Just follow this guide and you'll be good:
Thanks bwthor20 for telling me about this guide:
http://forum.xda-developers.com/showthread.php?t=695243
Now, go to the incredible version of this guide, thanks to Dougpiston:
http://pvillecomp.com/?page_id=33
These guides should get you fixed!
Cheers,
dmeadows013
That sucks man very interested in how that happened though, never seen a phone reset it self to s-on before. I think you would have to ruu to get s-off again, that is if you can ruu back to froyo. What rom are you on? Hope you figure something out.
cmlusco said:
That sucks man very interested in how that happened though, never seen a phone reset it self to s-on before. I think you would have to ruu to get s-off again, that is if you can ruu back to froyo. What rom are you on? Hope you figure something out.
Click to expand...
Click to collapse
Was attempting to run my very experimental port of the Vigor RUU. Strange because it showed the splash on my last test, but after moving /system/customize to /data/syscustomize, it did this. I'll try the Froyo RUU. I should've thought of that one. Thanks!
Why not flash an old RUU?
Could someone post the Froyo or Eclair PB31IMG? I can't seem to find it...
Official froyo 2.2 PB31IMG.zip
http://dinc.does-it.net/stock_froyo/PB31IMG.zip
cmlusco said:
Official froyo 2.2 PB31IMG.zip
http://dinc.does-it.net/stock_froyo/PB31IMG.zip
Click to expand...
Click to collapse
Thanks! Your the man!
There is another thread on here where a guy had the same thing happen to him. Tried to flash a rom then the black screen and 5 vibes. He also lost s-off. I wonder whats going on.
cmlusco said:
There is another thread on here where a guy had the same thing happen to him. Tried to flash a rom then the black screen and 5 vibes. He also lost s-off. I wonder whats going on.
Click to expand...
Click to collapse
Hmmmm... That might be it. I'll try to port it again, and see if I get the same result. If I do, that's probably the problem lol
Alright, got the PB31IMG flashed. Problem is, after flashing, it just did the 5 vibe again... Back in HBOOT
dmeadows013 said:
Alright, got the PB31IMG flashed. Problem is, after flashing, it just did the 5 vibe again... Back in HBOOT
Click to expand...
Click to collapse
Very strange not sure, if you cant get an ruu to work my guess is some sort of hardware failure.
I would try an ruu exe from your pc.
cmlusco said:
Very strange not sure, if you cant get an ruu to work my guess is some sort of hardware failure.
I would try an ruu exe from your pc.
Click to expand...
Click to collapse
Yeah. I'm probably gonna just take it into the Verizon store. There is no way they'll find out I was rooted, as I am now S-ON. I'll see what they say.
Here is the fix!
This happened to me yesterday after installing MIUI. All was working, but when I tried to switch the camera to store on the SD card, it said it wasn't available. Tried to mount/unmount with no luck. Rebooted, and I had the same thing, five vibrations, then just a flashing green LED. A battery pull and either the charger or USB plugged in a PC, and it would boot to recovery. Still couldn't read the SD Card, so no restore. Lots of Googles later I found the fix...right here on XDA. Found a LOT of threads that pretty much said that there is no recovery.
Read On...
http://forum.xda-developers.com/showthread.php?t=695243
LEAVE THE USB CABLE PLUGGED IN TO YOUR PC FOR ALL OF THIS!
After the SD fix, I could use CWM to restore a known good backup, then copied the two files over to my SD Card and used a terminal app on the phone to run the commands listed in the link. A reboot, and I was back in business. S-OFF was back too. Odd...
dmeadows013 said:
Yeah. I'm probably gonna just take it into the Verizon store. There is no way they'll find out I was rooted, as I am now S-ON. I'll see what they say.
Click to expand...
Click to collapse
Worth a try, you might get lucky.
dmeadows013 said:
Yeah. I'm probably gonna just take it into the Verizon store. There is no way they'll find out I was rooted, as I am now S-ON. I'll see what they say.
Click to expand...
Click to collapse
I wouldn't. With a USB cable plugged in to the phone and PC, you can get into hboot with a battery pull and powering on while holding volume down. This doesn't seem to work every time, so unplug, remove the battery, then try again. After getting into hboot, you can go to recovery and see CWM if you have it installed.
bwthor20 said:
I wouldn't. With a USB cable plugged in to the phone and PC, you can get into hboot with a battery pull and powering on while holding volume down. This doesn't seem to work every time, so unplug, remove the battery, then try again. After getting into hboot, you can go to recovery and see CWM if you have it installed.
Click to expand...
Click to collapse
I can get into HBOOT without being plugged in, just using the normal way. Clicked recovery, booted to the splash and then the black screen and 5 vibes. Anyway, I have installed the RUU, so it would have the stock recovery anyway.
CWM Version
dmeadows013 said:
I can get into HBOOT without being plugged in, just using the normal way. Clicked recovery, booted to the splash and then the black screen and 5 vibes. Anyway, I have installed the RUU, so it would have the stock recovery anyway.
Click to expand...
Click to collapse
Try booting with it plugged in to the PC. I could boot that way, and use it, but as soon as I unplugged the USB, it would go to a black screen and 5 vibrations.
bwthor20 said:
Try booting with it plugged in to the PC. I could boot that way, and use it, but as soon as I unplugged the USB, it would go to a black screen and 5 vibrations.
Click to expand...
Click to collapse
Well that seemed to work... I plugged it in, and it booted up to the DROID Screen. Then, I unplugged, and black screen vibes. I think I had the same thing as you, but I just had the stock recovery instead because of the RUU. How did you end up fixing the plugged in problem? I'll check out the thread you posted. Thanks man, your a lifesaver.
dmeadows013 said:
Well that seemed to work... I plugged it in, and it booted up to the DROID Screen. Then, I unplugged, and black screen vibes. I think I had the same thing as you, but I just had the stock recovery instead because of the RUU. How did you end up fixing the plugged in problem? I'll check out the thread you posted. Thanks man, your a lifesaver.
Click to expand...
Click to collapse
It is the second part of the sequence in the link I posted in the previous thread. Check to see if you can mount your SD Card. If not, you will need to do the first part so you can load the two files on it used in the second part.
bwthor20 said:
It is the second part of the sequence in the link I posted in the previous thread. Check to see if you can mount your SD Card. If not, you will need to do the first part so you can load the two files on it used in the second part.
Click to expand...
Click to collapse
Alright, got the SD fixed. Not sure how I will get the USB fix, as I do not have root. Also, for some reason, unRevoked cannot find my phone. Neither will ADB
I've seen a couple of threads such as this with no real solution.
I've been happily using my Desire for months without changing roms or whatever (CM7 and s-off) until last night I opened my Dolphin browser and before it loaded the homepage it froze, totally un-responsive. I took the battery out, and to my horror, it was still totally un-responsive. Wouldn't respond to pressing the power button, pressing volume down+power, charger, or usb.
The battery at the time was about 50%, I've had the battery in and out about 100 times now, trying things like leaving the battery out and then trying again, keeping it on 'charge' for a while and trying to get it booted, with no response at all.
This was until an hour ago, I hopefully tried to boot the phone after the battery, sim and sd card had been out for a while and I got a vibration, and then it hung on the flash screen. I had to remove the battery, then tried to boot again with no response, so I left it a while again, put the battery in and got to the bootloader, thought I'd get into recovery and try a nandroid or something, only when I selected recovery it hung on the slash screen again.
Does anyone have any ideas what this is, or how this could be fixed? Damn I hate not being able to use my previously awesome phone!
I apologise for the long post, I'm just trying to give a good explanation of things. I just couldn't see the problem being my battery, only the day before the problem I was telling my friend how great the battery life on my phone is, and that he should give rooting a go and use CM7, this probably hasn't swayed his decision to root his phone.
stevoh84 said:
I've seen a couple of threads such as this with no real solution.
I've been happily using my Desire for months without changing roms or whatever (CM7 and s-off) until last night I opened my Dolphin browser and before it loaded the homepage it froze, totally un-responsive. I took the battery out, and to my horror, it was still totally un-responsive. Wouldn't respond to pressing the power button, pressing volume down+power, charger, or usb.
The battery at the time was about 50%, I've had the battery in and out about 100 times now, trying things like leaving the battery out and then trying again, keeping it on 'charge' for a while and trying to get it booted, with no response at all.
This was until an hour ago, I hopefully tried to boot the phone after the battery, sim and sd card had been out for a while and I got a vibration, and then it hung on the flash screen. I had to remove the battery, then tried to boot again with no response, so I left it a while again, put the battery in and got to the bootloader, thought I'd get into recovery and try a nandroid or something, only when I selected recovery it hung on the slash screen again.
Does anyone have any ideas what this is, or how this could be fixed? Damn I hate not being able to use my previously awesome phone!
I apologise for the long post, I'm just trying to give a good explanation of things. I just couldn't see the problem being my battery, only the day before the problem I was telling my friend how great the battery life on my phone is, and that he should give rooting a go and use CM7, this probably hasn't swayed his decision to root his phone.
Click to expand...
Click to collapse
did you try rebooting it without sdcard?
If you manage to get it running , try to flash a shipped ROM - it should unroot you and fix any software problems . Try taking it back to your carrier as that sounds more like a hardware problem.
you are stuck on HTC screen are you not? Then this is the exact same situation is it not?
bortak's Troubleshooting Guide said:
S-ON
"I'm S-ON, I can't boot recovery, and my phone doesn't boot "
This is a bit of a worse situation, as you cannot flash system critical parts such as the recovery image and just restore a backup. This unfortunately means that you will lose all of your data when you attempt to fix the phone.
[STEP1]- Make sure that you have a goldcard. If not, create one from the tutorial.
[STEP2]- Battery pull. Hold the BACK button and the POWER button to boot into FASTBOOT mode.
[STEP3]- Download the latest WWE RUU from here
[STEP4]- Run the RUU and wait for completion WARNING: DO NOT, BY ANY CIRCUMSTANCES INTERRUPT THE PROCESS - THIS WILL MORE THAN LIKELY END UP WITH A BRICKED PHONE - NOT EVEN IF GOD HIMSELF TELLS YOU TO DO SO, OR IF THE US PRESIDENT THREATENS YOU WITH THERMO-NUCLEAR WAR
[STEP5]- Once the phone is booted, you are now returned completely to stock. You will need to re-root again, and I'd recommend S-OFF
Click to expand...
Click to collapse
P.S. Remember to read disclaimer on the thread.
kmaq said:
did you try rebooting it without sdcard?
Click to expand...
Click to collapse
I have tried booting without sdcard with no luck.
Walter1115 said:
If you manage to get it running , try to flash a shipped ROM - it should unroot you and fix any software problems . Try taking it back to your carrier as that sounds more like a hardware problem.
Click to expand...
Click to collapse
I would love to try that, only I can't boot the phone at all, not even into recovery.
bortak said:
you are stuck on HTC screen are you not? Then this is the exact same situation is it not?
P.S. Remember to read disclaimer on the thread.
Click to expand...
Click to collapse
I've changed the HTC screen to a Google one, but yes, formally the HTC screen.
I will try and get to the bootloader/fastbootagain, only I have not been able to get to that today. I'm going to download an RUU, and try and flash it, although I'm not sure how if I can't get into recovery? Any help there?
stevoh84 said:
I would love to try that, only I can't boot the phone at all, not even into recovery.
I've changed the HTC screen to a Google one, but yes, formally the HTC screen.
I will try and get to the bootloader/fastbootagain, only I have not been able to get to that today. I'm going to download an RUU, and try and flash it, although I'm not sure how if I can't get into recovery? Any help there?
Click to expand...
Click to collapse
[STEP2]- Battery pull. Hold the BACK button and the POWER button to boot into FASTBOOT mode.
Click to expand...
Click to collapse
you don't need recovery
bortak said:
you don't need recovery
Click to expand...
Click to collapse
Made a noob error there and didn't have the udb plugged in. Got fastboot up, and downloading an RUU, will let you know how I get on, thanks for the help.
Would you advise, running my previous nandroid, once I get up and running again?
stevoh84 said:
Made a noob error there and didn't have the udb plugged in. Got fastboot up, and downloading an RUU, will let you know how I get on, thanks for the help.
Would you advise, running my previous nandroid, once I get up and running again?
Click to expand...
Click to collapse
up to you, doesn't make a difference
Thanks for the help, unfortunately when I got the RUU downloaded and the bootloader downgrader I now can't get the phone into fastboot! Rather gutted, as I could get it there the other day, now I may have to accept defeat!
What happens when you try to get to fastboot mode? How do you do it? Try to boot into hboot, then press power button and you should be in fastboot mode.
stevoh84 said:
Thanks for the help, unfortunately when I got the RUU downloaded and the bootloader downgrader I now can't get the phone into fastboot! Rather gutted, as I could get it there the other day, now I may have to accept defeat!
Click to expand...
Click to collapse
NEVER accept defeat with Android. Try my guide for help.
MatDrOiD said:
What happens when you try to get to fastboot mode? How do you do it? Try to boot into hboot, then press power button and you should be in fastboot mode.
Click to expand...
Click to collapse
I can't get into any sort of boot mode, I've tried leaving it for days and trying the button sequences, I've tried having it plugged in for a day, and then trying, with no luck!
bortak said:
NEVER accept defeat with Android. Try my guide for help.
Click to expand...
Click to collapse
I will have a look, I will try anything really! just need some more ideas....
bortak said:
NEVER accept defeat with Android. Try my guide for help.
Click to expand...
Click to collapse
I may have to accept defeat, but I don't think I will be blaming Android, more than likely a drop of the phone in the past that has taken it's toll or something.
Sadly nothing in the contents of your quite excellent guide jumped out at me as relating to my problem.
But, thanks for helping and your advice.
stevoh84 said:
I may have to accept defeat, but I don't think I will be blaming Android, more than likely a drop of the phone in the past that has taken it's toll or something.
Sadly nothing in the contents of your quite excellent guide jumped out at me as relating to my problem.
But, thanks for helping and your advice.
Click to expand...
Click to collapse
Ahh well that's a shame, get HTC to fix it for you
bortak said:
Ahh well that's a shame, get HTC to fix it for you
Click to expand...
Click to collapse
I have been onto them. The response from HTC was amazing, after detailing in an email my phone is dead, won't respond and won't turn on.
I was told, 'while the phone is on, remove the battery and sim and perform a soft reset, if this fails, perform a factory reset, through settings'
I replied asking them how much it will be for them to fix it, they haven't replied! Maybe they don't do weekend!
So if I send it off to them, are they going to frown upon me for fiddling with the phone and rooting etc?
Long story short my friend gave me a T mobile HTC G2 because it didn't turn on. I opened the phone to find the part where the battery connects to the phone came off the mother board so i solder it back on put the phone back together and turned it on. It booted up normal and came to the lock screen nothing worked the touch wasn't responding so i push power button to turn screen off and then again to turn it back on and the screen worked. I tried guessing his pattern five time and it didnt work it asked me to sign in to my Google account when the screen came up the phone rebooted and it kept doing it every time i turned it on. So i looked on xda how to restore it tried it and im not sure if it restored or not but it strated boot looping. I tried the flashing the pc10img.zip from the root of the sd card it usually says something like version to new or to old or something it didn't work. My phone is not rooted and i don't think usb debugging is on. Any info you guys want just ask. What can i do? How can i fix it? Please help
I'm going to take a guess, that if the battery connection to the motherboard 'broke off', then it's possible you have other physical issues such as the ribbon cable connecting the screen/digitizer to the rest of the phone.
If it were me I would have sent the phone into HTC for hardware warranty (which you can't do now since you soldered it.).
Can you provide some specific information about the phone, can you get into the boot loader, and if so what exact information do you have there? (USB debugging would be easily turned on under system settings, if you can get into it via the screen).
kbeezie said:
I'm going to take a guess, that if the battery connection to the motherboard 'broke off', then it's possible you have other physical issues such as the ribbon cable connecting the screen/digitizer to the rest of the phone.
If it were me I would have sent the phone into HTC for hardware warranty (which you can't do now since you soldered it.).
Can you provide some specific information about the phone, can you get into the boot loader, and if so what exact information do you have there? (USB debugging would be easily turned on under system settings, if you can get into it via the screen).
Click to expand...
Click to collapse
Thanks for replying i don't think anything else is wrong with the phone all the cables were fine. To begin with warranty was already finished. "Yes", i can get into the boot loader/H boot. I can turn on usb debugging because the phone doesn't boot all the way in to android. When you say information what exactly are you looking for?
helstonrampersad said:
Thanks for replying i don't think anything else is wrong with the phone all the cables were fine. To begin with warranty was already finished. "Yes", i can get into the boot loader/H boot. I can turn on usb debugging because the phone doesn't boot all the way in to android. When you say information what exactly are you looking for?
Click to expand...
Click to collapse
Mainly the info that shows up on hboot, and which recovery you have (or 'had') so that might be able to advise some additional steps.
helstonrampersad said:
Long story short my friend gave me a T mobile HTC G2 because it didn't turn on. I opened the phone to find the part where the battery connects to the phone came off the mother board so i solder it back on put the phone back together and turned it on. It booted up normal and came to the lock screen nothing worked the touch wasn't responding so i push power button to turn screen off and then again to turn it back on and the screen worked. I tried guessing his pattern five time and it didnt work it asked me to sign in to my Google account when the screen came up the phone rebooted and it kept doing it every time i turned it on. So i looked on xda how to restore it tried it and im not sure if it restored or not but it strated boot looping. I tried the flashing the pc10img.zip from the root of the sd card it usually says something like version to new or to old or something it didn't work. My phone is not rooted and i don't think usb debugging is on. Any info you guys want just ask. What can i do? How can i fix it? Please help
Click to expand...
Click to collapse
when you first had the phone it won't boot right? but when you tried fixing the battery connection thingy (sorry I don't know whats it called )
it booted and ran again?
have you tried doing a factory reset?
Power button+volume rocker down (volume down button) to boot into bootloader mode then do a factory reset maybe that would work ?
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
OR
or sending the phone to HTC would help bud but you have to pay them for that if they get to fix it you got yourself a new toy!
kbeezie said:
Mainly the info that shows up on hboot, and which recovery you have (or 'had') so that might be able to advise some additional steps.
Click to expand...
Click to collapse
This is the boot loader screen that i see
VISION PVT SHIP S-ON
HBOOT-0.82.0000
MICROP-26.13.04.19_M
eMMC-boot
Apr 13 211, 14:51:54
Im pretty sure the phone was never rootded before
The Android Manual said:
when you first had the phone it won't boot right? but when you tried fixing the battery connection thingy (sorry I don't know whats it called )
it booted and ran again?
have you tried doing a factory reset?
Power button+volume rocker down (volume down button) to boot into bootloader mode then do a factory reset maybe that would work ?
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
OR
or sending the phone to HTC would help bud but you have to pay them for that if they get to fix it you got yourself a new toy!
Click to expand...
Click to collapse
Its ok im not certain of what its called either but just to be sure its the part where the battery touches and it has metal prongs like. As for trying to restore it, i already tried didnt work it boot loops when i try that.
I don;t know what to do
helstonrampersad said:
Its ok im not certain of what its called either but just to be sure its the part where the battery touches and it has metal prongs like. As for trying to restore it, i already tried didnt work it boot loops when i try that.
Click to expand...
Click to collapse
ryin
sorry bro I'm no dev so I don't know that much when you were tryin to flash the "stock rom" did you flash the one for the G2 or the Desire Z?
The Android Manual said:
ryin
sorry bro I'm no dev so I don't know that much when you were tryin to flash the "stock rom" did you flash the one for the G2 or the Desire Z?
Click to expand...
Click to collapse
I still appreciate your help bro and i was trying to flash the stock rom for the g2, i made sure of it.
helstonrampersad said:
I still appreciate your help bro and i was trying to flash the stock rom for the g2, i made sure of it.
Click to expand...
Click to collapse
Would probably have to stick to the original Stock RUU update since you're S-ON (would need S-OFF for any kind of custom recovery, kernel, unsigned packages, etc), so would have to use a signed full package from T-Mobile, I don't know much bout that because I usually have my phones rooted and away from stock as fast as I can.
What stock rom did you find before? links?
kbeezie said:
Would probably have to stick to the original Stock RUU update since you're S-ON (would need S-OFF for any kind of custom recovery, kernel, unsigned packages, etc), so would have to use a signed full package from T-Mobile, I don't know much bout that because I usually have my phones rooted and away from stock as fast as I can.
What stock rom did you find before? links?
Click to expand...
Click to collapse
http://shipped-roms.com/index.php?category=android&model=Vision
Thats is the above link i used and i used all the ones that start with "PC10" I rename them to PC10IMG.zip so the phone can recognize it and it did. The only problem is that after it tries to install is say something along the lines of version is older or newer since i tried multiple packages. One package was going through the process and after that it didn't do anything, it didnt say failed or reboot or anything like that. Ive been trying to fix this for like a week and a half now. Ive even flashed custom PC10IMG.zip to see if it could help but nothing the furthest ive gotten is the phone boots for like 2 seconds the screen is blurry and the shuts off and there is an orange light in top right that wasn't lighting up before. Here are the links for the custom packages
http://forum.xda-developers.com/showpost.php?p=10583834&postcount=33
http://forum.xda-developers.com/showpost.php?p=10966727&postcount=63
Cant thank you enough for helping me this is really frustrating
kbeezie said:
Would probably have to stick to the original Stock RUU update since you're S-ON (would need S-OFF for any kind of custom recovery, kernel, unsigned packages, etc), so would have to use a signed full package from T-Mobile, I don't know much bout that because I usually have my phones rooted and away from stock as fast as I can.
What stock rom did you find before? links?
Click to expand...
Click to collapse
If what i explained above is not what you were referring to then let me know your way
helstonrampersad said:
If what i explained above is not what you were referring to then let me know your way
Click to expand...
Click to collapse
You would have to much it to your exact carrier/phone, Just flashing whatever you get your hands on can be very very risky.
For example for me being on T-Mobile with a T-Mobile branded G2, I would grab PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip from http://forum.xda-developers.com/showthread.php?t=971109
(noting the *.15 is the original radio my device was shipped with, though I've upgraded to the newer *.19)
I of course have no intention to returning to complete stock, but it's usually the only course of action for most people stuck with S-ON (and then would look into exploiting/unlocking/rooting again from there).
kbeezie said:
You would have to much it to your exact carrier/phone, Just flashing whatever you get your hands on can be very very risky.
For example for me being on T-Mobile with a T-Mobile branded G2, I would grab PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip from http://forum.xda-developers.com/showthread.php?t=971109
(noting the *.15 is the original radio my device was shipped with, though I've upgraded to the newer *.19)
I of course have no intention to returning to complete stock, but it's usually the only course of action for most people stuck with S-ON (and then would look into exploiting/unlocking/rooting again from there).
Click to expand...
Click to collapse
I know it can be risky but im desperate for a fix. Ill try the package you linked. I download it and rename it to PC10IMG.zip? Ill get back after im done if you have any other suggestion please let me know.
kbeezie said:
You would have to much it to your exact carrier/phone, Just flashing whatever you get your hands on can be very very risky.
For example for me being on T-Mobile with a T-Mobile branded G2, I would grab PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip from http://forum.xda-developers.com/showthread.php?t=971109
(noting the *.15 is the original radio my device was shipped with, though I've upgraded to the newer *.19)
I of course have no intention to returning to complete stock, but it's usually the only course of action for most people stuck with S-ON (and then would look into exploiting/unlocking/rooting again from there).
Click to expand...
Click to collapse
Im confused on which one to flash I have a T-Mobile HTC G2 which one will i flash?
choose the latest one for the g2, reading your thread I feel you will have little luck with this. try logging onto freenode #g2root, you'll get real time help here
Sent from my HTC Vision using xda premium
demkantor said:
choose the latest one for the g2, reading your thread I feel you will have little luck with this. try logging onto freenode #g2root, you'll get real time help here
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
I am new to XDA how can i do that?
helstonrampersad said:
I am new to XDA how can i do that?
Click to expand...
Click to collapse
I'm new so I can't post links, but copy and paste this url: http://webchat.freenode.net/?channels=g2root
EDIT - Oh, I can post links.
eboy_gb said:
I'm new so I can't post links, but copy and paste this url: http://webchat.freenode.net/?channels=g2root
EDIT - Oh, I can post links.
Click to expand...
Click to collapse
Though ideally using an actual IRC client will work much nicer than a web chat one.
Same problem, but desire z S-ON
Hey guys.
I have the same problem with the boot loop /semi brick. Expect I never had any problem before, with the phone. I have tried taking out the sd card, starting it agian. I have tried without simcard. I have tried to flash the ROM with RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.2_Radio_12.56.60.25_26.10.04.03_M_release_199043_signed
via Hboot Fastboot USB PLUG mode (which was the only mode the aplication was progressing in until it want to restart the phone in bootloader), but the phone frezzes and the aplication on the computer just keep working, without progress.
The factory reset just frezzes the phone.
The only thing reali seem to not frezze the phone is the revocery option. Here the phone react with restart showing a image of a phone with two green arrows bent around, over the phone. then it turns off the display and vibrate 4-5 times, og stays turn off not reacting to anything other then taking out the battery and you can start the phone once again.
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MICROP-26.10.04.19_M
eMMC-boot
Apr 11 2011, 23:36:27
Have no idea but the version of android. I know that usb debugging is NOT on Any hjelp is a big help. I'm a noob, And I have been searching for 3 days for a solution, so I just hope you can help my, otherwise it is going for a repair at the place I bought it.
Thanks
Hey everyone,
I have read the various topics with a similar title but none helped.
Here is my problem, I bought a used HTC Desire on eBay. It booted just fine on the first start, then I did a factory reset (from within the Android system menu).
Since then, I'm stuck at the white screen with the green HTC logo. I have tried to get into bootloader mode by removing the battery, holding vol down and power, but it just goes straight to the white screen again.
Also connected the phone to the pc, but adb isn't picking up anything...
Any ideas?
Try Power+Back button.
just got one step further:
I can get into fastboot mode with BACK + POWER. But volume keys doesn't work, is that a known issue that I can solve somehow?
Goddchen said:
just got one step further:
I can get into fastboot mode with BACK + POWER. But volume keys doesn't work, is that a known issue that I can solve somehow?
Click to expand...
Click to collapse
So you bought a Desire with broken volume keys.
Are you s-off?
abaaaabbbb63 said:
So you bought a Desire with broken volume keys.
Are you s-off?
Click to expand...
Click to collapse
looks like...
in fastboot mode it shows that it is s-on.
Goddchen said:
looks like...
in fastboot mode it shows that it is s-on.
Click to expand...
Click to collapse
Then you'll have to flash a RUU to make it work.
http://forum.xda-developers.com/showthread.php?t=1772499
It's official HTC Firmware. Your phone will boot after this.
So:
1. Install HTC Sync.
2. Download and extract the RUU.exe from the zip (It's somewhere in there)
3. Run the exe while you connect your phone in fastboot (Power+Back)
4. Wait for it to install
5. Boot
abaaaabbbb63 said:
Then you'll have to flash a RUU to make it work.
http://forum.xda-developers.com/showthread.php?t=1772499
It's official HTC Firmware. Your phone will boot after this.
So:
1. Install HTC Sync.
2. Download and extract the RUU.exe from the zip (It's somewhere in there)
3. Run the exe while you connect your phone in fastboot (Power+Back)
4. Wait for it to install
5. Boot
Click to expand...
Click to collapse
Thanks for the advice, I downloaded the 2.3 RUU and it starts the process, sais
rebooting to bootloader
erasing data
sending...
and after ~30 seconds it just shows me a screen that sais "ERROR_UNKNOWN"
On the phone I see a black screen with a silver HTC logo during the process and when I unplug the USB cable after the error it shows the hboot screen that now sais "update failed".
right before the error is shown it display "updating signature"
Goddchen said:
right before the error is shown it display "updating signature"
Click to expand...
Click to collapse
It only says "Error_Unknown"? No error number, anything?
Weird.
This may be the reason:
Now, that may not sound too bad to some of you, but there's more: the 2.3 RUU update is limited regionally, as well. It's not available to users in Germany, North America, South America, South Korea, or Japan.
Click to expand...
Click to collapse
You live in Germany, right?
Use this guide then:
Section 2, S-on
http://forum.xda-developers.com/showthread.php?t=1275632
yes I am in Germany,
made some progress (or not?)
I noticed that the device was "unlocked", so I did "fastboot oem lock" and it was "relocked".
Then the RUU update went through - nearly. At the very end if failed again and now I am stuck at a black screen with the silver HTC logo and triangles in every corner.
AW: Unable to get into bootloader or recovery mode, stuck at white HTC logo screen
Sent from my Nexus 4 using xda app-developers app
wtf... tried again flashing the 2.3 RUU, this time it worked, YEAY
But now I have a bootloop, device starts, vibrates 1 time, waits for 3 seconds, and then vibrates 7 times. And restarts...
Ok. Tests are done.
According to the screenshot above and the 7 vibrations, you have a radio brick. It's a brick that can hardly be overcome.
The only solution is flashing the RUU and hoping that the phone will eventually boot.
That's why I don't buy second hand phones.
This thread might help:
http://forum.xda-developers.com/showthread.php?t=1793369
abaaaabbbb63 said:
Ok. Tests are done.
According to the screenshot above and the 7 vibrations, you have a radio brick. It's a brick that can hardly be overcome.
The only solution is flashing the RUU and hoping that the phone will eventually boot.
That's why I don't buy second hand phones.
This thread might help:
http://forum.xda-developers.com/showthread.php?t=1793369
Click to expand...
Click to collapse
freecer did it, was able to flash the 2.3 RUU again successfully. But now I'm back at the bootloop, but now, it simply does vibrate once (no more 7 vibrations) and reboots after some seconds.
So what can I do now? RUU flashed successfully, I'm running out of ideas...
and again the freezer did it, put it in, normally started via POWER button, it booted right through into Android.
Well, let's see if it keeps running now or if this overheating issue also exists in normal operation mode...
Thanks so much for you help so far, the freezer hint saved this device and hopefully will make my gf very happy tomorrow
Hold on I thought it was some pvt1 devices that had overheating issues.
Thought it was fixed on your newer ones. Then again I've never had a problem with my pvt1 desire flashed both hboot and find countless times.
Sent from my GT-I9100 using xda app-developers app
dethrat said:
Hold on I thought it was some pvt1 devices that had overheating issues.
Thought it was fixed on your newer ones. Then again I've never had a problem with my pvt1 desire flashed both hboot and find countless times.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
it is a PCT3 device.
but the overheating-reboot issue is rendering it useless. I can use it just fine outside (-2° currently) but as soon as I'm inside, boot-loop...
Anything I can do from a hardware perspective to fix that? Sending it in for repair/replacement is not an option, it's simply not worth the cost.
do you think installing a custom rom of any kind might help?
Goddchen said:
it is a PCT3 device.
but the overheating-reboot issue is rendering it useless. I can use it just fine outside (-2° currently) but as soon as I'm inside, boot-loop...
Anything I can do from a hardware perspective to fix that? Sending it in for repair/replacement is not an option, it's simply not worth the cost.
Click to expand...
Click to collapse
It's a motherboard fault. If you don't send it to repair, you just got yourself an "Ice-Phone", or a very complex paper holder.
i think a custom rom would help a small bit, like the rom in abaaaabbbb63 sig (mildwild redux) because its small and lite unlike a sense rom. therefor it mite not overheat as quick or as often. but thats only a guess. the only dodgy thing is trying to get ur phone s-off or rooted because if ur phone overheats in the middle of the s-off/rooting progress u could brick ur phone. plus charge ur phone using ur computer coz it uses less power and the phone does'nt heat up as much as plugging into the wall.