So the screen of my g2 is all black, and Tmobile has allowed me to do a warranty exchange of the phone, it is s off and clock work recovery with a OTA non rooted file system (did a factory reset in clock work so my personal info wouldnt still be there, but did a back up before so i can still restore. i dont believe i had usb debugging enabled). Can someone help me to get it back to s-on with normal recovery... I have been trying to think how to do it, but cant figure it out. I have another g2 that i do all the same steps with. Any help is appreciated.
Dont worry about it. If your screen is broken they cant see it either! They will wipe the phone replace the screen and give it to someone with a loose hinge. If you still want help did you try to use adb? Does it connect?
Sent from my HTC Vision using XDA App
shortlived said:
Dont worry about it. If your screen is broken they cant see it either! They will wipe the phone replace the screen and give it to someone with a loose hinge. If you still want help did you try to use adb? Does it connect?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
That's stupid. They can tell by diagnosing the phone when they plug it in. They are going to see whether or not you have the factory rom
Sent from my T-Mobile G2 using XDA App
It is not looking like it is going to connect, but if you are pretty sure that they arent gonna look, i wont even sweat it.
I think this thread might work:
http://forum.xda-developers.com/showthread.php?t=835971
But it might be tricky getting past the first step without a screen... but fastboot and adb usually solve most problems...
What hboot do you have installed? Did you install the hboot-eng.img when you rooted?
My theory is that you can use fastboot to flash the parts of the rom, in the right order. Again, this is just my theory and I've never tried this.
http://forum.xda-developers.com/showthread.php?t=838484
The stock ROM has all the parts on it, but it flashes hboot first, which does version checking and will fail when it tries to install the later parts. If you extract the system, recovery, boot images out of the stock rom, you can use fastboot flash {partition} to restore these, then use fastboot flash hboot {hboot} to restore the bootloader. I don't think there will be any way to verify that this works without a screen*.
*While you are at it, you might be able to use the new G2 to backup a rom with debugging enabled and then flash the system.img (and maybe userdata.img) to the broken one, so that you can verify that everything worked.
Hopefully, someone who knows more about flashing that I do can verify if this has a shot at working or not.
Disclaimer: I have no idea if this will work or not. Flash at your own peril.
i have the s-off eng hboot. clock work recovery and i have stock rom installed, i was kind of thinking i could use something to restore the recovery to stock, and somehow flash original hboot, but i really have no idea to actualy do this.
is there any way that i can hex edit the partition on the other phone do a nandroid, then restore the nandroid on the broken phone, then use hboot to flash the ota update and get the hboot and recovery back to original?
Throw it against the wall until it doesn't connect anymore or turn on. Problem solved.
I'm not sure if this will work anymore... I tried to flash the .img parts from a nandroid backup and it seems to get hung up. My terminal has been "sending system.img" for the last 10 minutes. I wonder if this has something to do with how the bootloader was patched to get root?
DJAeroX26 said:
That's stupid. They can tell by diagnosing the phone when they plug it in. They are going to see whether or not you have the factory rom
Click to expand...
Click to collapse
You really think T-Mobile are going to plug in and do diagnosis on a phone with a broken screen ? We're talking about a phone carrier, not HTC themselves
use screencast, its simple to use and puts your screen on your pc..I have used it several times for issues such as this.
how do i install it if i dont have usb debugging enabled.
bobsfoot said:
how do i install it if i dont have usb debugging enabled.
Click to expand...
Click to collapse
hmmm...wait 1, will research it
Of course they can tell if its rooted my point is they wont care to take the time. I am no authority for sure but i will ask this... have you seen one single person who has been denied because they rooted they're phone?
Sent from my HTC Vision using XDA App
I was in a similar situation as you but with a Desire Z, Somehow the screen decided to give up on me so have sent it back to where I bought it from in the UK.
I am fairly sure the RUU changes it to s-on doesn't it? I just ran the RUU and sent it back after screencasting to do a backup of my rom. Still unsure as to what the end result will be with my phone however.
so today the new phone comes, should i just fastboot a new recovery then do a ruu update to put s on, and leave the phone broke and be like no idea, or is there a way to edit the partition version in fast boot?
or do i leave it alone, and just hope they dont care.
They wont care.
steviewevie said:
You really think T-Mobile are going to plug in and do diagnosis on a phone with a broken screen ? We're talking about a phone carrier, not HTC themselves
Click to expand...
Click to collapse
I'm just saying, I work in retail and usually when someone brings something back to exchange when there is a problem...I thouroughly check to make sure if the problem was the user's fault, then i deny the return. They do lose money even if it is a warranty exchange
Sent from my T-Mobile G2 using XDA App
Related
Let me preface this by saying yes I know there are dozens if not more threads on boot loop problems. I have recovered from boot loops before. This is very different.
I rooted my incredible with unrevokedForever and had cyanogen 6 on it. Everything was fine until yesterday I woke up to it in a boot loop, but not the cyanogen boot animation, the white HTC Incredible screen. I can only get to HBOOT, once I try to enter recovery, use an update.zip, or anything after the HBOOT page it goes into its loop. Should I pursue the RUU and find a windows computer or will that not help me?
I think I may have to bite the bullet and buy a new phone. As obviously they will not replace an S-OFF phone. Any help is appreciated.
jenic said:
Let me preface this by saying yes I know there are dozens if not more threads on boot loop problems. I have recovered from boot loops before. This is very different.
I rooted my incredible with unrevokedForever and had cyanogen 6 on it. Everything was fine until yesterday I woke up to it in a boot loop, but not the cyanogen boot animation, the white HTC Incredible screen. I can only get to HBOOT, once I try to enter recovery, use an update.zip, or anything after the HBOOT page it goes into its loop. Should I pursue the RUU and find a windows computer or will that not help me?
I think I may have to bite the bullet and buy a new phone. As obviously they will not replace an S-OFF phone. Any help is appreciated.
Click to expand...
Click to collapse
As long as you can still get into HBOOT and Recovery, you should be okay. Your best bet is to get the RUU and go back to stock/s-on, then re-root/s-off (if you want). I had to do this once, and it's pretty straight forward. Just do a search for Bezerker7's Ultimate Get Back to Stock Thread. It has all the info you'll need on how to do it.
RMarkwald said:
As long as you can still get into HBOOT and Recovery, you should be okay. Your best bet is to get the RUU and go back to stock/s-on, then re-root/s-off (if you want). I had to do this once, and it's pretty straight forward. Just do a search for Bezerker7's Ultimate Get Back to Stock Thread. It has all the info you'll need on how to do it.
Click to expand...
Click to collapse
The problem is I can only get into HBOOT, not recovery. It would be a fairly simple matter if I had access to recovery features. Would RUU work without access to recovery?
jenic said:
The problem is I can only get into HBOOT, not recovery. It would be a fairly simple matter if I had access to recovery features. Would RUU work without access to recovery?
Click to expand...
Click to collapse
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
RMarkwald said:
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
Click to expand...
Click to collapse
Your concise post is most appreciated. I will do as you instruct and post results back here when finished.
RMarkwald said:
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
Click to expand...
Click to collapse
Hit an unfortunate snag right away. fastboot (nor adb) is detecting the device. Screen is showing XC SHIP S-OFF as it should, it is in FASTBOOT USB mode and my computer detects the USB itself just fine.
dmesg output:
[346853.772041] usb 2-6: new high speed USB device using ehci_hcd and address 17
[346853.922917] usb 2-6: configuration #1 chosen from 1 choice
Click to expand...
Click to collapse
Thank you though that was a great suggestion! (Was very hopeful for a second there
I've never used the fastboot command before, but I seem to recall that sometimes my PC's don't report connection from ADB, but I haven't checked recently... Hmmm...
Just checked and it does report a device using ADB. Did you try typing the fastboot command to flash the recovery image file: fastboot flash recovery /path/to/<recovery.img file> anyways to see what happens? I am assuming if it isn't detecting the connection, it may fail...
EDIT: Did you pull the battery out, put it back in and try to get into recovery again? If you, try doing a user/factory reset + dalvik cache before trying to install a ROM from your SD card.
This may or may not help, but I had a similar issue of not having the phone recognized by fastboot while playing with a friends EVO Shift. I was able to use the program described in this thread to uninstall all HTC drivers. Then, when the phone was recognized and new drivers installed automatically, fastboot worked as expected.
http://forum.xda-developers.com/showthread.php?t=532719
RMarkwald said:
I've never used the fastboot command before, but I seem to recall that sometimes my PC's don't report connection from ADB, but I haven't checked recently... Hmmm...
Just checked and it does report a device using ADB. Did you try typing the fastboot command to flash the recovery image file: fastboot flash recovery /path/to/<recovery.img file> anyways to see what happens? I am assuming if it isn't detecting the connection, it may fail...
Click to expand...
Click to collapse
My ADB daemon would always recognize it in the past, when the phone was working. Yes I tried the command anyway, even though fastboot devices did not return anything. It hung there waiting for the device to be connected.
RMarkwald said:
EDIT: Did you pull the battery out, put it back in and try to get into recovery again? If you, try doing a user/factory reset + dalvik cache before trying to install a ROM from your SD card.
Click to expand...
Click to collapse
Yes, I pulled battery out multiple times, and when installing the rom I factory reset, cleared dalvik and normal cache through Clockwork. Cyanogen was working fine for weeks, this is a freak concurrence that happened without warning. I woke up to find it this way, or rather, it woke me up with its constant rebooting. lol.
cf9182 said:
This may or may not help, but I had a similar issue of not having the phone recognized by fastboot while playing with a friends EVO Shift. I was able to use the program described in this thread to uninstall all HTC drivers. Then, when the phone was recognized and new drivers installed automatically, fastboot worked as expected.
http://forum.xda-developers.com/showthread.php?t=532719
Click to expand...
Click to collapse
I appreciate the help however I am using Linux, and that seems to be a windows issue. I have not had issue detecting the device until this problem arouse. The sentiment is of course appreciated though, please do not feel that I am ungrateful! You have both been very supportive. I think I have just about resigned to dump money on a new phone. This time I will leave it stock for awhile and see if this occurs a third time.
jenic said:
My ADB daemon would always recognize it in the past, when the phone was working. Yes I tried the command anyway, even though fastboot devices did not return anything. It hung there waiting for the device to be connected.
Yes, I pulled battery out multiple times, and when installing the rom I factory reset, cleared dalvik and normal cache through Clockwork. Cyanogen was working fine for weeks, this is a freak concurrence that happened without warning. I woke up to find it this way, or rather, it woke me up with its constant rebooting. lol.
I appreciate the help however I am using Linux, and that seems to be a windows issue. I have not had issue detecting the device until this problem arouse. The sentiment is of course appreciated though, please do not feel that I am ungrateful! You have both been very supportive. I think I have just about resigned to dump money on a new phone. This time I will leave it stock for awhile and see if this occurs a third time.
Click to expand...
Click to collapse
This happened to me and many other people. It has nothing to do with the fact that you rooted as my replacement from verizon did the same thing even before I rooted. Finally on my 2nd replacement (my 3rd DINC), it has stopped happening.
You're going to have to take it to the store. The guy who looked at my phone looked right at the HBOOT (where it says s-OFF) and then said "we're going to have to send you another one."
So you may get lucky. Your other option (if you're nervous about the store seeing the s-OFF) is just to call Verizon and ask them to send you a replacement. My experience has been that the folks in the Verizon store have no idea what the f they're doing, and you'll probably be just fine taking it in.
jaba14 said:
This happened to me and many other people. It has nothing to do with the fact that you rooted as my replacement from verizon did the same thing even before I rooted. Finally on my 2nd replacement (my 3rd DINC), it has stopped happening.
You're going to have to take it to the store. The guy who looked at my phone looked right at the HBOOT (where it says s-OFF) and then said "we're going to have to send you another one."
So you may get lucky. Your other option (if you're nervous about the store seeing the s-OFF) is just to call Verizon and ask them to send you a replacement. My experience has been that the folks in the Verizon store have no idea what the f they're doing, and you'll probably be just fine taking it in.
Click to expand...
Click to collapse
That was definitely a laugh. Thank you I will see if I can get it replaced! I've been kinda just ignoring the fact that I do not have a phone all this time... Thankfully I had setup the phone to forward calls to google voice. It has been a lifesaver.
Sounds like there weren't any ideas in Q&A for this one, and I haven't seen much in terms of not being able to access recovery, so here goes...
I was happily using CM7, and while reading through a Diablo III news page (hopefully it comes out soon ), my phone rebooted into a boot loop. Weird, but I figured at worst I would wipe data and reinstall a ROM. Unfortunately, I can't get into recovery any longer.
If I boot the phone normally, I see the white HTC splash screen for a few seconds, then it reboots. I can use HBOOT fine, but as soon as I try to reboot normally / boot into recovery / boot into Restore Factory Defaults, my phone will reset. Let me clarify...
Pull and replace battery
Boot into HBOOT (volume down + power)
Select Recovery
Phone reboots and reaches CWM Recovery 3 for about 1/2 second, not long enough for me to click anything
Phone reboots into boot loop
I've used HBOOT to flash to CWM Recovery 3.0.0.8, downgraded to the stock radio, run the 2.2 RUU. I'm still running up against the same boot loop problem.
I wouldn't be surprised if it was a hardware problem, but I'm anxious to hear if anyone has ideas to try first. Additionally, is there any way to restore to S-ON through HBOOT in case I need to bring this into a Verizon store? I have fastboot.exe that can recognize the device over USB while the device is in HBOOT, maybe this will help?
Thanks!
Current state: Ran 2.2 RUU, S-OFF, HBOOT-0.92.0000, AMOLED, 2.15.00.07.28 radio
Thanks again.
Had this exact issue while running cm7. First couple of from when it was crackflashers. I couldn't find anything to help or fix it. I got a new dinc because I can't afford to be without for long.
Good luck dude.
Sent from my ADR6300 using Tapatalk
Thanks for the note. Maybe my fate will be the same. Did you get any sympathy from Verizon?
Doesn't sound like there are even any suggestions using fastboot, lol. [crickets chirping]
Can you flash cwm 2.5.x and try? Not sure if it will help but worth a shot?
sent from a phone
Yeah take out battery, then pull out sd card put it into a adapter and insert it to ur pc. Then find the file that was shipped specifically for ur device it looks something like this PC130mg.zip or some crap like that anyways put that on the root of your sd card. load ur card back to your phone now into hboot(volume down plus power) mode. Your phone will auto detect that file and start to ask if u want to install update say yes boom it will flash back to stock.....however my only concern would be if u need to turn s-ON before u do this.
I did this for a evo 4g and it worked but I turned s-ON first as it was in the instructions I was following. I think maybe the update file checks to see if ur S-off or on. But don't quote me on that.
Sent from my PG06100 using Tapatalk
popasmurfn23 said:
Yeah take out battery, then pull out sd card put it into a adapter and insert it to ur pc. Then find the file that was shipped specifically for ur device it looks something like this PC130mg.zip or some crap like that anyways put that on the root of your sd card. load ur card back to your phone now into bootloader (volume down plus power) mode. Your phone will auto detect that file and start to ask if u want to install update say yes boom it will flash back to stock.....however my only concern would be if u need to turn s-ON before u do this.
I did this for a evo 4g and it worked but I turned s-ON first as it was in the instructions I was following. I think maybe the update file checks to see if ur S-off or on. But don't quote me on that.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
Yeah, I agree with popasmurf. Put the PB31IMG.zip on your sdcard. Then let hboot discover and update it. It'll be back to stock and youll have to reroot but better than a paperweight.
You can find the image here -----> http://dougpiston.com/?page_id=108
I'm assuming you have a dinc.
sent by carrier pigeon
hope that helps
@phazeone let's say he just does that. Now his phone reboots and is on stock and looses his root, now he can root it again and then turn the S-on by the single file flash from recovery mode, and then use the update file again to flash the phone back to normal stock without root ( if he was taking it back) so whenever u want to manipulate the S security u must be rooted correct?
Sent from my PG06100 using Tapatalk
popasmurfn23 said:
@phazeone let's say he just does that. Now his phone reboots and is on stock and looses his root, now he can root it again and then turn the S-on by the single file flash from recovery mode, and then use the update file again to flash the phone back to normal stock without root ( if he was taking it back) so whenever u want to manipulate the S security u must be rooted correct?
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
You are correct.
popasmurfn23 said:
Yeah take out battery, then pull out sd card put it into a adapter and insert it to ur pc. Then find the file that was shipped specifically for ur device it looks something like this PC130mg.zip or some crap like that anyways put that on the root of your sd card. load ur card back to your phone now into hboot(volume down plus power) mode. Your phone will auto detect that file and start to ask if u want to install update say yes boom it will flash back to stock.....however my only concern would be if u need to turn s-ON before u do this.
I did this for a evo 4g and it worked but I turned s-ON first as it was in the instructions I was following. I think maybe the update file checks to see if ur S-off or on. But don't quote me on that.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
phaze one said:
Yeah, I agree with popasmurf. Put the PB31IMG.zip on your sdcard. Then let hboot discover and update it. It'll be back to stock and youll have to reroot but better than a paperweight.
You can find the image here -----> http://dougpiston.com/?page_id=108
I'm assuming you have a dinc.
sent by carrier pigeon
Click to expand...
Click to collapse
Thanks for the replies.
I tried this method to flash back to the stock 2.2 image before I started this thread. That's what I meant by "I've used HBOOT to ... run the 2.2 RUU." The stock image seemed to install properly in HBOOT. I have evidence that it successfully went back to stock, since I get the original ! triangle graphic instead of CWM when I try to enter recovery from HBOOT. However, I only see the graphic pop up for a brief second before it reboots again. Trying to boot into recovery or the ROM itself still result in a reboot.
I cannot achieve S-ON without having access to recovery, at least there's no way that I've found to do it through HBOOT.
Any other thoughts? I think it's a hardware problem. It appears the phone is back to stock (except it's still S-OFF), but everything outside of HBOOT causes a boot loop. I stopped in at Verizon this afternoon and they'll be sending a new phone to arrive by Tuesday. At this point, it'd be nice to try all avenues of repair for the future benefit of others that run into this problem.
Probably bad memory chips on the phone. Since it happened all of a sudden during normal use it usually indicates hardware failure.
That is pretty much what I determined. Bad hardware. Sorry for your trouble but is nice to know I'm not the only person to ever have this. Also nice to know I didn't miss something that could've brought it back to life.
I filed an insurance claim. Figured since I have had it for years and never used it I'd take advantage.
Sent from my ADR6300 using Tapatalk
You can boot your phone like regular right? Just let it launch up or do you get loops?
Nevermind i see what ur saying. when i was flashing incorrect kernals i would get the same behavior from my phone. So i suggest you take phazeones link and try that file.Because u might have the incorrect file. There might be more than meets the eye make sure u got the right file.
When i searched for my zip file for my evo there was like 4 of them. They had to match what was said in the upper left corner of my hboot screen. So let me knoe if it worked
I wonder if he could just wipe that SD card, place a new Rom etc on it and reinstall. Bricking displays no response you've got a better shot at recovering course your SD card/battery could be bad
Since you're trying to flash the 3.x.x.x version of CWM, that may be your issue. Here's a zip for 2.5.0.5, one of the most stable earlier Recoveries. Flash through hboot as per usual.
If that doesn't work, (I'm assuming that you can boot the phone normally at this point) try re-rooting with the Unrevoked tool.
Then use Rom Manager to flash a newer Recovery (be sure to check Erase Previous Recovery under Settings). If that still doesn't work, I'll see about packaging an RUU in a PB31IMG.zip with a valid version of CWM as the recovery.img within that zip. I'm not sure about the practicality of this final option, but if it comes down to it, I'll attempt to package that up for you.
This sounds incredibly frustrating. Thus my interest in the matter.
There's gotta be a way to fix this... even if it's just long enough to get S-On and keep your warranty valid.
Sent via my Incredible CM7 Gingerbread sorcery.
Crans said:
I wonder if he could just wipe that SD card, place a new Rom etc on it and reinstall. Bricking displays no response you've got a better shot at recovering course your SD card/battery could be bad
Click to expand...
Click to collapse
This would work if he could access CWM Recovery, but he can't, thus the issue.
I wonder if he could mount something from within hboot and replace the binary code for the recovery image with a bunch of zeroes and then try flashing another through hboot again.
Sent via my Incredible CM7 Gingerbread sorcery.
I was JUST about to post the same topic when I came across this. I have done the stock image restore, restored BACK to hboot 0.92, back to the most current INC radio, and have tried flashing CW3.0 and Amon_RA. Everything flashes fine but the boot loop continues and if I try to enter recovery, it lasts maybe one full second before rebooting again. The only thing that I can think of that would create this situation for me was that earlier I was trying to update the PRL via *228 on MIUI but the dialpad never popped up so I hung up.
popasmurfn23 said:
So i suggest you take phazeones link and try that file.Because u might have the incorrect file. There might be more than meets the eye make sure u got the right file.
When i searched for my zip file for my evo there was like 4 of them. They had to match what was said in the upper left corner of my hboot screen. So let me knoe if it worked
Click to expand...
Click to collapse
I'll take another crack at it, but I don't think I had gotten the wrong image. No worries though, it's easy enough to try again using the link on page 1 directly. Can't hurt, right ;-)
RegnierD said:
Since you're trying to flash the 3.x.x.x version of CWM, that may be your issue. Here's a zip for 2.5.0.5, one of the most stable earlier Recoveries. Flash through hboot as per usual.
Click to expand...
Click to collapse
Sure. Once again, worth a shot.
RegnierD said:
This sounds incredibly frustrating. Thus my interest in the matter.
There's gotta be a way to fix this... even if it's just long enough to get S-On and keep your warranty valid.
Click to expand...
Click to collapse
Thanks for the sympathy . Like I mentioned, I visited the Verizon store and a new one is on its way... doesn't that mean that it doesn't matter (other than for science sake) whether this gets S-On or even fixed?
[waiting for flash of build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip]
It just seems unlikely that this is a problem with flashing the wrong recovery, or the wrong stock image, since booting into recovery and booting normally both exhibit the same behavior. If I could boot normally into recovery but not boot into a stock image, I would suspect that I had flashed the wrong image. Since both have the same problem, I think it might be something else.
[finished flashing build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip]
Same behavior. White htc Incredible splash screen -> darkness for a second (presumably while the ROM tries to boot) -> reboot.
Alternatively, HBOOT -> Recovery -> White htc Incredible screen -> Triangle / ! error screen for a half second -> reboot.
[finished flashing CWM 2.5.0.5]
Same behavior:
HBOOT -> Recovery -> White htc Incredible screen -> CWM recovery 2.5.0.5 for a half second (this confirms that it flashed properly) -> reboot.
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
Few days ago, my G2's screen just went blank (dark blueish if I press any buttons on it). I live in Canada, so can't send it back to Tmobile since I'm not with them. But, I can send it back to HTC since it's still under warranty. Only problem is that I rooted the phone and s-off and then flashed Virtous Rom on it couple of months ago.
With the help of a senior member (eunkipark92), i was able to install ADB, and using that I can see that it recognizes my device when connected with PC. Now, I don't know whether the problem is with my phone's software or with the hardware (screen) itself.
I say that because I had a pattern set up to unlock the code before the screen went blank and even now I can swipe my finger on the screen in the specific manner that I used to before and it would unlock the phone. The screen still remains blank (dark blue) ofcourse, but I can change the phone's profile from vibration to loud etc after unlocking the screen by pressing the volume key up or down.
I was told by another member (PaganAng31) that if I can totally brick the phone using a command in ADB something like "dd = /dev/block/mmblk1p3" there will be noway for HTC people to figure out whether or not the phone was rooted before. But he wasn't sure and asked me to post here.
Now my first attempt will be to fix it somehow or unroot the phone and put the stock rom back in using ADB and then send it back to HTC. If I can't do that, then I would totally brick it (only if it's 100% sure that HTC won't figure out that this phone was rooted before) so that they can totally flash it or change the screen or send me a replacement. Also what's the exact command that is used in ADB and how do you use it for totally bricking the phone?
Any kind of help will be appreciated. Thanks
Its probably hardware issue. I heard that g2 screen will just stop working...display failure..
I read this somewhere before I purchased g2 but I still bought it anyway.
Anyways..
Have you downloaded the hboot engineer and recovery.img?
I would like to give you step by step instruction but I haven't used adb since I got rid of my nexus one...so I don't really rememebr the commands to flash stuffs:/ sorry.
If it is software issue you can fix it since you were able to get adb working
But if it doesn't work flashing a new hboot,recovery and a new rom its mostly lcd failure or ribbon is damaged.
U can use hboot pc10img method to put ur stock rom and radio. But I don't know a way to unroot it if you can't see the screen.
When I had nexus one and when I had to send it for repair.
(My bootloader was unlocked with stock rom)
They didn't charge me for rooting. Just my experience with htc.
If there is anything I can help pm me.
Sent from my HTC Desire Z using Tapatalk
eunkipark92 said:
Its probably hardware issue. I heard that g2 screen will just stop working...display failure..
I read this somewhere before I purchased g2 but I still bought it anyway.
Anyways..
Have you downloaded the hboot engineer and recovery.img?
I would like to give you step by step instruction but I haven't used adb since I got rid of my nexus one...so I don't really rememebr the commands to flash stuffs:/ sorry.
If it is software issue you can fix it since you were able to get adb working
But if it doesn't work flashing a new hboot,recovery and a new rom its mostly lcd failure or ribbon is damaged.
U can use hboot pc10img method to put ur stock rom and radio. But I don't know a way to unroot it if you can't see the screen.
When I had nexus one and when I had to send it for repair.
(My bootloader was unlocked with stock rom)
They didn't charge me for rooting. Just my experience with htc.
If there is anything I can help pm me.
Sent from my HTC Desire Z using Tapatalk
Click to expand...
Click to collapse
Ok. So what's the first step now? Do we reflash hboot and recovery? I flashed it 3 months ago using this method:
http://forum.xda-developers.com/showthread.php?t=833965
Now to reflash it, do we use this method on the wiki and just follow it. It looks pretty straight forward?
http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
If that's the one, then the link to Engineering hboot for Tmobile G2 is broken. Any alternative?
Also do you know the command to completely brick the phone in ADB in case we are unable to fix it?
I am interested as well. Coincidentally my screen just went completely black 3 hours ago. I think the lcd is dead. Last thing I did earlier today was that I flashed from the ..04.30 radio to the ..02.26 while troubleshooting HSDPA issues.
I think I could settle for adb shell commands to flash the roms if anyone can point me to a link. Closest i've found is a link to the G1 forums (I used to have one) but that shows how to a manual nandriod restore which is a bit different.
Last resort as the OP is asking, will creating a typo while following a rooting guild do the trick?
icruisin said:
I am interested as well. Coincidentally my screen just went completely black 3 hours ago. I think the lcd is dead. Last thing I did earlier today was that I flashed from the ..04.30 radio to the ..02.26 while troubleshooting HSDPA issues.
I think I could settle for adb shell commands to flash the roms if anyone can point me to a link. Closest i've found is a link to the G1 forums (I used to have one) but that shows how to a manual nandriod restore which is a bit different.
Last resort as the OP is asking, will creating a typo while following a rooting guild do the trick?
Click to expand...
Click to collapse
Good luck buddy. Let me know if you find a way to get it fixed or brick it. From another thread I found the command is something like:
dd if=/dev/zero of=/dev/block/mmcblk0p*
Where * = the partition number.
But I just don't know how to apply it.
Did you guys get this going? Op sent me a pm for help a few days back and I just got this. I had the same thing happen.
You can brick using the dd= command. You would follow the OLD eng hboot root guide except instead of having the real hboot.img you would have a random text file named hboot.img inplace of it. HOWEVER, YOU DO NOT WANT TO DO THAT.
You can put back to stock. Make sure phone has a good charge or it won't flash properly.
First things first. If there is anything you want to save off the phone first, ie good (bad) pic mess from your gf or similar , then search on googl.code or xda for screencast. It allows you to see the phones screen on your comp screen (requires adb installed and working). It works in the os, and in recovery, but unfortunatly doesn't work in fastboot.
After everything you want is saved, backup your sdcard to your comp, and clean off sdcard. If you are rooted per gfree use it to revert back to s-on (if you are old eng hboot only method, skip that step). Replace the misc.img as per the unroot guide. Then put the stock shipped PC10IMG on the root of your sdcard. Boot into fastboot by holding down vol and power. Give it few mins to read and load pcimg, let's say 5 mins to be safe. Press vol up to confirm to reflash ( I know u can't see screen, but have faith). It will reboot in the middle of process to flash radio, then will finish flashing. It should only take 10 mins, but leave it for like 30 to be safe. Then press power button to reboot.
At this time it should boot into stock os. Remember first boot take awhile, so give it a min. To confirm it worked, do 2 things. On comp type adb remount and should say not allowed. Also try using screencast should not work since usb debugging is required for it, and its turned off by default on stock os.
Goodluck, hope this helps. If anyone finds this usefull of needs any help, let me know.
fastludeh22 said:
Did you guys get this going? Op sent me a pm for help a few days back and I just got this. I had the same thing happen.
You can brick using the dd= command. You would follow the OLD eng hboot root guide except instead of having the real hboot.img you would have a random text file named hboot.img inplace of it. HOWEVER, YOU DO NOT WANT TO DO THAT.
You can put back to stock. Make sure phone has a good charge or it won't flash properly.
First things first. If there is anything you want to save off the phone first, ie good (bad) pic mess from your gf or similar , then search on googl.code or xda for screencast. It allows you to see the phones screen on your comp screen (requires adb installed and working). It works in the os, and in recovery, but unfortunatly doesn't work in fastboot.
After everything you want is saved, backup your sdcard to your comp, and clean off sdcard. If you are rooted per gfree use it to revert back to s-on (if you are old eng hboot only method, skip that step). Replace the misc.img as per the unroot guide. Then put the stock shipped PC10IMG on the root of your sdcard. Boot into fastboot by holding down vol and power. Give it few mins to read and load pcimg, let's say 5 mins to be safe. Press vol up to confirm to reflash ( I know u can't see screen, but have faith). It will reboot in the middle of process to flash radio, then will finish flashing. It should only take 10 mins, but leave it for like 30 to be safe. Then press power button to reboot.
At this time it should boot into stock os. Remember first boot take awhile, so give it a min. To confirm it worked, do 2 things. On comp type adb remount and should say not allowed. Also try using screencast should not work since usb debugging is required for it, and its turned off by default on stock os.
Goodluck, hope this helps. If anyone finds this usefull of needs any help, let me know.
Click to expand...
Click to collapse
Thanks. I know what to do next time if my G2 is messed up But I already bricked my phone last week and sent it back for repair, since I couldn't find any other to way fix it.
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