Develop Bugs

[Q] Help, Phone stuck on Bootloader Screen

Hi guys, need some help if possible.
My phone is stuck on the bootloader screen and the up and down buttons are not working so I can choose the option to reboot the phone.
1- I was running MIUI for a while now and I was just listening to Music and suddenly the phone just rebooted and got stuck on the bootloader screen, this is what I tried so far, any help will be appreciated.
2- I tried removing the battery and booting into recovery and the Up and Down button still don't work so I couldn't pick up the option to reboot phone.
3- I ran the PB31IMG Stock zip to go back to stock and after doing the update when is time for the phone to reboot, instead of rebooting it goes back to the bootloader.
Thanks in advance.
If anybody know the command for the SDK to reboot the phone, I think that'll help too.

If the +/- volume buttons don't work at all, I think you're screwed. I don't know of another way to navigate the fastboot screen
Do you have S-off?

Can you load an ruu thru the pc? Not sure if that will help or not.
________________________________
Unrevoked forever
SkyRaider Sense 3.5
Radio 2.15.00.09.01

Guys thanks, I took my phone to Verizon to get a replacement since the phone was Bricked but after I order my replacement the freaking phone turned on again, now I have a choice to make, keep my original phone or keep the Refurbished one they're sending me, thanks again.
I did have S-off.

Well most likely the one you got sent to you is an SLCD model, and you probably have an AMOLED. IMO I would keep the AMOLED, but i'm not sure that you can keep it. I think you have to send in your original.
And since you can turn it on, make sure to flash S-ON and flash it back to stock.

g00s3y said:
Well most likely the one you got sent to you is an SLCD model, and you probably have an AMOLED. IMO I would keep the AMOLED, but i'm not sure that you can keep it. I think you have to send in your original.
And since you can turn it on, make sure to flash S-ON and flash it back to stock.
Click to expand...
Click to collapse
Thanks, I already flash the phone back to stock, I think the rep said I'll be getting the same phone with the AMOLED screen since that's what I got, we'll see when I get the phone tomorrow.
In the mean I'm gonna play with the original one, rooted again and see what happens after I install another Rom.

[Q] Black screen of death please help!

ok so i flashed cynogenmod 7 today and i decided that i really wasnt that into it. I want to flash back to stock and when i did it the progress bar flashed red halfway through and the screen went to HTC black and silver with triangle with exclamation points in them. I tried getting tot he bootloader screen but when i push power and volume down button it just stays on the htc with triangles screen. Please help!

Bump. I can't help you but I feel so bad when people are desperate for help and don't get it. So here's a bump to get it noticed
Sent from my Optimus V

96camarors said:
ok so i flashed cynogenmod 7 today and i decided that i really wasnt that into it. I want to flash back to stock and when i did it the progress bar flashed red halfway through and the screen went to HTC black and silver with triangle with exclamation points in them. I tried getting tot he bootloader screen but when i push power and volume down button it just stays on the htc with triangles screen. Please help!
Click to expand...
Click to collapse
Were you running an RUU when thus happened? Was that how you were getting back to stock? How long has it been on that screen? If your sure its stuck, and is idle, I would do a battery pull, and then see if you can get to the bootloader. If you can, try running the RUU again, but put the phone in fastbood mode when you run the RUU. See if a second time gets it.
Sent from my PC36100 using XDA App

k2buckley said:
Were you running an RUU when thus happened? Was that how you were getting back to stock? How long has it been on that screen? If your sure its stuck, and is idle, I would do a battery pull, and then see if you can get to the bootloader. If you can, try running the RUU again, but put the phone in fastbood mode when you run the RUU. See if a second time gets it.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I was running ruu and it failed. i have tried several times since including battery pulls and no luck. I keep trying to get to the bootloader but its stuck at that screen. It does not show up in my computer either when i plug it in but using an ruu still works.

When trying to get to bootloader, did you push power / volume down after phone was off? If not, pull battery. Put back in and then power/volume down.
You probably already did this but it sort of sounded like you tried getting to bootloader from the screen you were stuck on.
J
Bump
Sent from my PC36100 using XDA Premium App

The error i get when ruu fails is error 110 file open error. The rom update utility cannot open the requested files or the files are damaged. the ruu cannot continue with the update. Please get a complete ruu package and try again.

96camarors said:
I was running ruu and it failed. i have tried several times since including battery pulls and no luck. I keep trying to get to the bootloader but its stuck at that screen. It does not show up in my computer either when i plug it in but using an ruu still works.
Click to expand...
Click to collapse
When you shut your Evo off, and plug it into a wall (AC) plug, do you get a charging led? If you can still run an RUU, it sounds like maybe the one you are using is corrupt, or the wrong one all together. Do you know your bootloader version, software version, and radio versions? Likely you need to download the RUU that matches (or is very close to) your current versions.
I'm on the app, but would otherwise link you to a thread. In the dev section, search for "supersonic shipped roms", thread started by Esp28
Sent from my PC36100 using XDA App

ferfy67 said:
When trying to get to bootloader, did you push power / volume down after phone was off? If not, pull battery. Put back in and then power/volume down.
You probably already did this but it sort of sounded like you tried getting to bootloader from the screen you were stuck on.
J
Bump
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
yeah i did that and nothing just stays at the screen

k2buckley said:
When you shut your Evo off, and plug it into a wall (AC) plug, do you get a charging led? If you can still run an RUU, it sounds like maybe the one you are using is corrupt, or the wrong one all together. Do you know your bootloader version, software version, and radio versions? Likely you need to download the RUU that matches (or is very close to) your current versions.
I'm on the app, but would otherwise link you to a thread. In the dev section, search for "supersonic shipped roms", thread started by Esp28
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
i am currently trying to download the 3.7 ruu but it keeps canceling itself. i do get a chargin led when plugged into wall. radio is 2.15

96camarors said:
i am currently trying to download the 3.7 ruu but it keeps canceling itself. i do get a chargin led when plugged into wall. radio is 2.15
Click to expand...
Click to collapse
Charging led is good. Find a good copy of the 3.70 RUU, make sure its a good download, and run again. When I get home ill link you to my RUU copy in my dropbox if you haven't found one yet.
Sent from my PC36100 using XDA App

k2buckley said:
Charging led is good. Find a good copy of the 3.70 RUU, make sure its a good download, and run again. When I get home ill link you to my RUU copy in my dropbox if you haven't found one yet.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
i found one that works and i have 46min to go. i found a good step-by-step fix for my problem http://androidforums.com/evo-4g-support-troubleshooting/254695-black-error-screen-when-updating-rooted-phone-supersonic-ruu.html and i am praying that it works for me. and thank you for your help so far!

96camarors said:
i found one that works and i have 46min to go. i found a good step-by-step fix for my problem http://androidforums.com/evo-4g-sup...hen-updating-rooted-phone-supersonic-ruu.html and i am praying that it works for me. and thank you for your help so far!
Click to expand...
Click to collapse
Cool, your welcome. I bet the good RUU will work. And yes, the other thread looked good. Did u run unrevoked forever? If so, did u flash the s on tool before running RUU?
Sent from my PC36100 using XDA App

k2buckley said:
Cool, your welcome. I bet the good RUU will work. And yes, the other thread looked good. Did u run unrevoked forever? If so, did u flash the s on tool before running RUU?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
i didnt flash s on tool. and that was my problem, i am new to the evo world (just got it sunday) and i had motorola before so the rooting i am used to is way different than htc haha

You get it fixed yet?
Sent from my PC36100 using Tapatalk

96camarors said:
i didnt flash s on tool. and that was my problem, i am new to the evo world (just got it sunday) and i had motorola before so the rooting i am used to is way different than htc haha
Click to expand...
Click to collapse
Yea, the rooting world between different manufacturers differs greatly, apparently. The state you're currently in, you probably have no choice but to run the RUU again. Once you get it to successfully run, and you boot up, back to stock, you'll most likely still be S-off. Now, that's not necessarily bad, unless you're going to take your evo into sprint for any reason. If you leave it S off, if you ever want to reroot, all you'd have to do is flash a PC36IMG of a custom recovery, using the bootloader. At that point, you could flash a ROM or whatever. Also, if you do want to return it to S on, once the RUU completes and you can boot, flash a PC36IMG of a recovery, using the bootloader. At that point, flash the unrevoked S on tool, using recovery. Once you confirm that S is back to ON, then run the RUU again. Then you'll be back to stock, unrooted, S on.

RileyGrant said:
You get it fixed yet?
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
not fixed yet 5min left on download
k2buckley said:
Yea, the rooting world between different manufacturers differs greatly, apparently. The state you're currently in, you probably have no choice but to run the RUU again. Once you get it to successfully run, and you boot up, back to stock, you'll most likely still be S-off. Now, that's not necessarily bad, unless you're going to take your evo into sprint for any reason. If you leave it S off, if you ever want to reroot, all you'd have to do is flash a PC36IMG of a custom recovery, using the bootloader. At that point, you could flash a ROM or whatever. Also, if you do want to return it to S on, once the RUU completes and you can boot, flash a PC36IMG of a recovery, using the bootloader. At that point, flash the unrevoked S on tool, using recovery. Once you confirm that S is back to ON, then run the RUU again. Then you'll be back to stock, unrooted, S on.
Click to expand...
Click to collapse
ok thanks for the advice. ill probly go back to stock for awhile until i get used to the phone. so if i leave s off then nothing bad while happen with the ruu while im sleeping? i really need to get to sleep asap, got a full day of classes tomorrow haha.

96camarors said:
not fixed yet 5min left on download
ok thanks for the advice. ill probly go back to stock for awhile until i get used to the phone. so if i leave s off then nothing bad while happen with the ruu while im sleeping? i really need to get to sleep asap, got a full day of classes tomorrow haha.
Click to expand...
Click to collapse
I'm confused, haha. Nothing bad will happen with the RUU when you're sleeping? I think you do need some sleep brotha! Once you successfully run the RUU, and return to stock, you'll most likely still be S off, since you didn't flash the S on tool. This mean's you'll be on a stock ROM, with S off, and no recovery. Nothing bad will happen by leaving it like this, so long as you don't take it to Sprint with S off. Now, if you do just plan on staying stock for a while, you may want to return to S-on, just in case any unpredictable catastrophic events occur, you're better off having S-on, in case you need to take it back to Sprint. You can always root again rather easily. So I guess my suggestion is to flash a recovery once you're up and running, flash the S on tool, and then run the RUU again. Just to be safe. If you want to root again, you know how
Edit: ^^^^All that is providing you get the RUU to run successfully, which I think you will. You just need a good copy of the right version. If that doesn't work, don't forget you have other options. Such as flashing an RUU as a PC36IMG from the bootloader. Also, you can run an RUU with fastboot. So there is a plan B and C if that doesn't work.

k2buckley said:
I'm confused, haha. Nothing bad will happen with the RUU when you're sleeping? I think you do need some sleep brotha! Once you successfully run the RUU, and return to stock, you'll most likely still be S off, since you didn't flash the S on tool. This mean's you'll be on a stock ROM, with S off, and no recovery. Nothing bad will happen by leaving it like this, so long as you don't take it to Sprint with S off. Now, if you do just plan on staying stock for a while, you may want to return to S-on, just in case any unpredictable catastrophic events occur, you're better off having S-on, in case you need to take it back to Sprint. You can always root again rather easily. So I guess my suggestion is to flash a recovery once you're up and running, flash the S on tool, and then run the RUU again. Just to be safe. If you want to root again, you know how
Edit: ^^^^All that is providing you get the RUU to run successfully, which I think you will. You just need a good copy of the right version. If that doesn't work, don't forget you have other options. Such as flashing an RUU as a PC36IMG from the bootloader. Also, you can run an RUU with fastboot. So there is a plan B and C if that doesn't work.
Click to expand...
Click to collapse
ok thank you very much. it worked. thanks for all your help!

96camarors said:
ok thank you very much. it worked. thanks for all your help!
Click to expand...
Click to collapse
Sweet, glad to hear it worked. Take care.
Oh yea, are you S on or S off? My guess is S off, if you did use unrevoked forever before.

k2buckley said:
Sweet, glad to hear it worked. Take care.
Oh yea, are you S on or S off? My guess is S off, if you did use unrevoked forever before.
Click to expand...
Click to collapse
Yes I am currently s off

[Q] Screen freezing if goes into sleep, never turns back on

Having an issue with my HOX today. It was in my pocket all day at work, pulled it out to make a phone call and afterwards when I went to hang up, the screen would not turn back on. It is still responsive to touch input and I can still unlock while the screen is black, but it still does not turn on. I can however hard restart it and the screen comes back on and I can still enter fastboot/recovery. But if I let the phone stand-by the issue repeats itself. I was on BinDroid v2 without any kernel when this happened, I got the phone into recovery and flashed both Energy and franco.Kernel and this issue is still happening. Is my best option to try and flash the original RUU and a stock rom?

I've had this issue since flashing the bricked kernel. I think the best option would be to go back to stock.
Sent from my HTC One X using XDA

i have the same problem but in my case the phone is just suck at a black screen. am not able to do anything at all, am just sitting now waiting for my battery to die so that i may be able to reboot it. if you any suggestions to solve this, please do tell as i am in a dire situation.

Can't you restart the phone by holding the power button in?
If not then that's a strange one.
Sent from my HTC One X using XDA

IPS1989 said:
i have the same problem but in my case the phone is just suck at a black screen. am not able to do anything at all, am just sitting now waiting for my battery to die so that i may be able to reboot it. if you any suggestions to solve this, please do tell as i am in a dire situation.
Click to expand...
Click to collapse
This is what I'm doing as well. I tried using a nandroid to go back to stock and that still doesn't work. It's almost impossible to get the phone into the bootloader but it's do able. One thing I'm noticing though, is that if the screen does manage to turn on when I boot it up, it wants to send an error report to HTC about it. Also, once the screen goes off and won't come back on, it's very laggy to other inputs. Example, pressing the power like you want to wake it and then pressing to volume keys has a very noticeable delay.
Thankfully, HTC is already doing a warranty call on it for the yellow spots on my screen (now like dark orange spots now)
Update: HTC said that the screen issue I'm having is unlikely able to be fixed by a software repair and that I have to send it in for a repair. 7-10 business days.... great.

Also with an untouched phone
Guys, I am afraid this is a hardware problem. My phone is UNROOTED with the last upgrade and I am having the same issue.
Take it back to the assistance. OOPS, you rooted it ;-)

lisophorm said:
Guys, I am afraid this is a hardware problem. My phone is UNROOTED with the last upgrade and I am having the same issue.
Take it back to the assistance. OOPS, you rooted it
Click to expand...
Click to collapse
Hi.. I'm also facing the same issue ... however this didn't start till few days ago. I have had this phone for six months now and was on stock most of the times.
But since this week , I started getting issues where once the screen goes black , it doesn't come back on. Although , I can reboot the phone with long press power button and also go back to bootloader/recovery without any issues.
Can u confirm its the hardware issue ? If yes, did the techinicians told you anything about what is causing this and it can be corrected easily ? I want to try my hands on it before going to customer care as I have void my warranty and will have to pay for repairs.
Cheers !

its kernels issue.
you should flash orginal kernel or flash a rom with irginal kernel to fix this issue.
Sent from my HTC One X using Tapatalk 2

shadow fiend said:
its kernels issue.
you should flash orginal kernel or flash a rom with irginal kernel to fix this issue.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
First time I started facing the issue, I was on stock 4.0.4 rom with stock kernels unrooted and locked bootloader.
So not sure if the issue was related to kernel. Anyways I'l try to get stock kernel and use it.
Cheers

OK.. so I did tried to get the stock 4.0.4 rom with stock kerne but same issue.
Also in the meanwhile I tried all other prominent HOX roms , bot AOSP and sense.
I have found that the issue is more severe and frequent on Sense roms (confirmed on all JB roms Ondroid, Maximus and ADHD as well as VenomX) but its very much stable on AOKP ICJ and CM10 roms. However still sometimes screen doesn't come on in ICJ too.
Now I'm starting to think there might be some issue with HBoot 1.28. My CID is 001 so there shouldn't be any issue, but if I remember correctly when I installed the Hboot, there was a 'Failed' message , but the process did completed.
Should I try to again flash Hboot 1.28 as I can't apparantely go back to older ones ? anything else I should try.
I'd really like to hear from some ppl who have faced this issue and mentioned in posts above on how they managed to solve it.
Cheerio

dev997 said:
OK.. so I did tried to get the stock 4.0.4 rom with stock kerne but same issue.
Also in the meanwhile I tried all other prominent HOX roms , bot AOSP and sense.
I have found that the issue is more severe and frequent on Sense roms (confirmed on all JB roms Ondroid, Maximus and ADHD as well as VenomX) but its very much stable on AOKP ICJ and CM10 roms. However still sometimes screen doesn't come on in ICJ too.
Now I'm starting to think there might be some issue with HBoot 1.28. My CID is 001 so there shouldn't be any issue, but if I remember correctly when I installed the Hboot, there was a 'Failed' message , but the process did completed.
Should I try to again flash Hboot 1.28 as I can't apparantely go back to older ones ? anything else I should try.
I'd really like to hear from some ppl who have faced this issue and mentioned in posts above on how they managed to solve it.
Cheerio
Click to expand...
Click to collapse
have you solve this issue?

[q] htc g2 not rooted semi bricked boot looping please help

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

new problem?

okay guys ill make this quick.
my one x had no problems at all since I got it, few days ago htc launcher starts to crash and i realize a bit of battery drain and some lag, so I pressed the power botton for 10 sec for a full restart. after boot(ONEX logo) comes a black screen and i cant do anything, i press power button nothing happens just the buttons at the bottom will light up.
i posted my problem here at XDA and i was told to do a factory rest which i did and it erased all my pics and data .
anyway, today i pressed the power botton and same problem happend so can anyone tell me whats rong with the phone?
things you may need to know.
fast boot mode is on
android version 4.0.3
htc sense 4.0
software 1.26.401.2 (I didnt update software because im hoping to get S-off.)
PLEASE GUYS HELP
i really dont want to factory rest my phone every day.

mr.dj26 said:
okay guys ill make this quick.
my one x had no problems at all since I got it, few days ago htc launcher starts to crash and i realize a bit of battery drain and some lag, so I pressed the power botton for 10 sec for a full restart. after boot(ONEX logo) comes a black screen and i cant do anything, i press power button nothing happens just the buttons at the bottom will light up.
i posted my problem here at XDA and i was told to do a factory rest which i did and it erased all my pics and data .
anyway, today i pressed the power botton and same problem happend so can anyone tell me whats rong with the phone?
things you may need to know.
fast boot mode is on
android version 4.0.3
htc sense 4.0
software 1.26.401.2 (I didnt update software because im hoping to get S-off.)
PLEASE GUYS HELP
i really dont want to factory rest my phone every day.
Click to expand...
Click to collapse
Why do you have fastboot on?
And why you didn't update? Where did you find out that you will get S-OFF on that firmware?

PAGOT said:
Why do you have fastboot on?
And why you didn't update? Where did you find out that you will get S-OFF on that firmware?
Click to expand...
Click to collapse
software update will update hboot, and fast boot is on because when i shut off the off and turn it on it starts up in seconds.
anyway, any idea about the problem?

mr.dj26 said:
software update will update hboot, and fast boot is on because when i shut off the off and turn it on it starts up in seconds.
anyway, any idea about the problem?
Click to expand...
Click to collapse
Well try to use your phone without the fast boot on?
And okay I still do not get the point? Have you asked in the S-OFF thread and they said, that S-OFF will come only for the old hboot and everyone who updated wont get S-OFF?
If that would be the case, there would be many many unhappy ppl.
So you rather will be on a half year old bug filled fw as to update and use your phone properly?

Turn off fast-boot. And then do a reboot. Elimination my friend.

PAGOT said:
Well try to use your phone without the fast boot on?
And okay I still do not get the point? Have you asked in the S-OFF thread and they said, that S-OFF will come only for the old hboot and everyone who updated wont get S-OFF?
If that would be the case, there would be many many unhappy ppl.
So you rather will be on a half year old bug filled fw as to update and use your phone properly?
Click to expand...
Click to collapse
i tried hard reset with both fast boot on and off both work; i just dono why im having this problem.
and about the update, i didnt have any issues with my phone so I didnt update and I have read somewhere that after update it would be difficult to s-off i dont remember.
thank for your help

oliseo said:
Turn off fast-boot. And then do a reboot. Elimination my friend.
Click to expand...
Click to collapse
so you think this is the reason of the problem?
thanks

mr.dj26 said:
i tried hard reset with both fast boot on and off both work; i just dono why im having this problem.
and about the update, i didnt have any issues with my phone so I didnt update and I have read somewhere that after update it would be difficult to s-off i dont remember.
thank for your help
Click to expand...
Click to collapse
To be rude, you think you have no issues with 1.26 doesn't means that the firmware is stable. And yes, everyone here knew 1.29 is the ways much better than 1.26 with a bunches of fixes and tweaks.
For the s-off progress, as far as I know those developers who are working on it do not stayed tight on 1.26 hboot (correct me if I'm wrong), though some of them has s-off devices. The main barriers on s-off path was not a newer hboot patching holes (there is no big hole found yet) but was the HTC hardworks to barricaded us to have a talk with tegra. On my guess, even there is a solution reveal it will be less likely to be achieve through an old hboot only.
To be honest, you are the only here i had seen that are stayed on 1.26 for s-off..

mr.dj26 said:
so you think this is the reason of the problem?
thanks
Click to expand...
Click to collapse
With bugs like this, it's a process of elimination. Unless it's specifically ruled out (ie, you still suffer the same bug regardless of fast-boot being on or off), then you can only assume that may be.
See what happens if you turn it off. If it works, you know that was causing the issue. If it doesn't, then repeat the process until you eliminate all possibilities. (ie, does it crash after you've transferred files via USB, switched WiFi on/off).
Once all possibilities (within your remit of course) have been exhausted then it's time to send it off, as it's nothing you can solve and it could be a hardware issues (bad memory perhaps??)
Anyway, let's go for the easy fix first, and I keep my fingers crossed that turning off fast-boot helps.

HebeGuess said:
To be rude, you think you have no issues with 1.26 doesn't means that the firmware is stable. And yes, everyone here knew 1.29 is the ways much better than 1.26 with a bunches of fixes and tweaks.
For the s-off progress, as far as I know those developers who are working on it do not stayed tight on 1.26 hboot (correct me if I'm wrong), though some of them has s-off devices. The main barriers on s-off path was not a newer hboot patching holes (there is no big hole found yet) but was the HTC hardworks to barricaded us to have a talk with tegra. On my guess, even there is a solution reveal it will be less likely to be achieve through an old hboot only.
To be honest, you are the only here i had seen that are stayed on 1.26 for s-off..
Click to expand...
Click to collapse
lol
thanks for your help

oliseo said:
With bugs like this, it's a process of elimination. Unless it's specifically ruled out (ie, you still suffer the same bug regardless of fast-boot being on or off), then you can only assume that may be.
See what happens if you turn it off. If it works, you know that was causing the issue. If it doesn't, then repeat the process until you eliminate all possibilities. (ie, does it crash after you've transferred files via USB, switched WiFi on/off).
Once all possibilities (within your remit of course) have been exhausted then it's time to send it off, as it's nothing you can solve and it could be a hardware issues (bad memory perhaps??)
Anyway, let's go for the easy fix first, and I keep my fingers crossed that turning off fast-boot helps.
Click to expand...
Click to collapse
i really appreciate ur help guys
i just had the problem again, fast boot was off.. just did a factory reset
theres no crashs when transferring file or turning wifi on or off.
this is really weird.
do you think flashing RUU may help or its the ame as factory reset?
thanks..

Worth trying.

BenPope said:
Worth trying.
Click to expand...
Click to collapse
I have never flashed an ruu before.
can you tell me how that work and from where I can get it? my cid is J_15
and im useing mac, will it work?
thanks m8

There is a sticky Endeavor shipped ROM collection thread in dev section.
You can't easily do it from Mac, if at all.

BenPope said:
There is a sticky Endeavor shipped ROM collection thread in dev section.
You can't easily do it from Mac, if at all.
Click to expand...
Click to collapse
theres no guide on how this works..
my cid is J_15, which file should i download ?:S
i really hope this would do it, htc support at my place isn't that good and i really dont want to send it back and wait for ages

,,
i rebooted the phone now more than 10 times with now problems,
the phone now has no apps or anything brand new.
could it be a cause of apps or something?

Just look at your software version, then find the RUU in the link from the first page in the sticky thread.
Then borrow a Windows machine and run the RUU with your phone connected.

BenPope said:
Just look at your software version, then find the RUU in the link from the first page in the sticky thread.
Then borrow a Windows machine and run the RUU with your phone connected.
Click to expand...
Click to collapse
okay here it is 1.26.401.2
now when i want to download it it requires premium account WT* ?!

.
dose flashing the RUU require adb or only htc driver?

I'm in the same position. Woke up yesterday, booted phone, black screen after "HTC One" screen. Oddly I could change the volume and the volume changer would display on a black screen. Restarted, same thing. Factory reset, no problems. All the while fast-boot is off.
Same thing happened this morning, cold boot, "HTC One" screen then black screen. Factory reset and immediately rebooted - same thing again! is this a hardware issue or a corrupt software issue?
Will go and join the incredibly long and slow moving at the HTC service centre after work.
---------- Post added at 12:34 PM ---------- Previous post was at 11:50 AM ----------
I've spoken with HTC customer services and they recommend taking the phone in to get it flashed - basically they think that there is a problem with the software. They claim it is a quick job.
They offered to come out to my office and collect my phone and return it tomorrow - I'm impressed with that level of service... pending they can fix it with a simple flash of the firmware!