It has been doing this since LoliPop and it drives me nuts. When I do a complete wipe, it will stop for a while, but starts again. I don't have it enabled in developers options and it is not turned on in screen record. What you see is what I see constantly. How do I make it stop? Does it on completely stock Rom rooted, BB stock deodex and this is now BB
I do not think anyone really knows what you are talking about? Do you mean while in Swype you see a visual image of where you touching the screen? That is a feature of Swype and many apps even stock apps show you a visual of where you are touching the screen.
jpwhre said:
It has been doing this since LoliPop and it drives me nuts. When I do a complete wipe, it will stop for a while, but starts again. I don't have it enabled in developers options and it is not turned on in screen record. What you see is what I see constantly. How do I make it stop? Does it on completely stock Rom rooted, BB stock deodex and this is now BB 3.2 Rom.
https://youtu.be/D_9f5ZG1FLM
Click to expand...
Click to collapse
you need to disable show touch points under dev options.
deakelem said:
you need to disable show touch points under dev options.
Click to expand...
Click to collapse
this bottom option.. show touches
deakelem said:
you need to disable show touch points under dev options.
Click to expand...
Click to collapse
schmeggy929 said:
I do not think anyone really knows what you are talking about? Do you mean while in Swype you see a visual image of where you touching the screen? That is a feature of Swype and many apps even stock apps show you a visual of where you are touching the screen.
Click to expand...
Click to collapse
deakelem said:
this bottom option.. show touches
Click to expand...
Click to collapse
https://youtu.be/tM0X5XOIvkw
bump
i'm done with it. i just don't care, it can just keep showing.
couple weeks ago i flashed bone stock via sd card in download mode 5 times in a row. Lasted about a week, still stock (s-off and unlocked bootloader) with stock recovery and no SU installed.
Sunday I flashed the ruu.exe from laptop twice in a row, and screen showing touches as soon as device reboots and goes thru startup/setup.
I really have no clue why it keeps doing it.
Further details:
No matter what roms i flash, status always shows official in bootloader even after installing twrp and selecting "allow mods"
either from ruu.exe or doing stock flash of ruu via sd card and download mode, bootloader never locks back up
s-off
jpwhre said:
i'm done with it. i just don't care, it can just keep showing.
couple weeks ago i flashed bone stock via sd card in download mode 5 times in a row. Lasted about a week, still stock (s-off and unlocked bootloader) with stock recovery and no SU installed.
Sunday I flashed the ruu.exe from laptop twice in a row, and screen showing touches as soon as device reboots and goes thru startup/setup.
I really have no clue why it keeps doing it.
Further details:
No matter what roms i flash, status always shows official in bootloader even after installing twrp and selecting "allow mods"
either from ruu.exe or doing stock flash of ruu via sd card and download mode, bootloader never locks back up
s-off
Click to expand...
Click to collapse
I don't know why, but it was glove mode that was causing the issue. I just make sure it is never on.
Related
Recently I updated my 'non-rooted' HTC Hero (Orange) to 2.73.61.66 from my previous version (2.73.61.5). I got this ROM from the Orange site.
The problem I am facing is that once I restart it and slide down the lock screen, it just shows me the HTC logo. It's very frustrating, however, I can receive phone calls and SMS (for SMS, I can just see the preview in the lock screen). After fiddling around with it a bit, once I move the slider to get in the home screen (which is just the HTC logo), I press HOME button for a while and it brings up my Recent Applications (which is empty). After this if I press the call button, it even gives me access to the dialer screen and I can make calls. But alas, so far I have found no way to get to the main GUI, it keeps on showing only the HTC logo!
So far I re-installed the new and previous firmware a couple of times each, but the problem remains. I have also tried a hard reset and a memory clear and that has also not helped.
Just want to point out here that when I first got the Hero I updated to the .5 version in exactly the same manner and it worked just fine (now when I run the ROM Update Utility and take it back to that same version, I face the same issue).
I will highly appreciate any help in this regard as you can imagine how frustrating this is - I love my Hero!
full wipe, reflash, boot w/o sdcard, logcat...
kendong2 said:
full wipe, reflash, boot w/o sdcard, logcat...
Click to expand...
Click to collapse
Thanks for trying to help kendong2, as I'm pretty desperate here. I would further appreciate it if you could just elaborate on those terms a little more.
I'm not sure what you mean by 'full wipe' and 'logcat'.
Also, my phone is not rooted. I looked up logcat and it seems I need to run ADB for it. I'm a total newbie on this but from what I understood; my phone needs to be rooted to run ADB (would be glad to be corrected here).
consider your users manual and find out how to "restore factory settings". i believe there is a button combination you can press to do this. all your settings will be lost afterwards.
logcat needs adb, although no root AFAIK. but i am not sure if you can use it on a stock rom at all.
kendong2 said:
consider your users manual and find out how to "restore factory settings". i believe there is a button combination you can press to do this. all your settings will be lost afterwards.
logcat needs adb, although no root AFAIK. but i am not sure if you can use it on a stock rom at all.
Click to expand...
Click to collapse
Thanks again. Did the Restore Factory Settings, flashed it and booted without the SD card but still facing the same problem. I'm checking if there is a way to get that logcat somehow.
you flashed it via ruu? or what?
kendong2 said:
you flashed it via ruu? or what?
Click to expand...
Click to collapse
That's right, I used the RUU and it completed successfully (as it has been doing all the times I have flashed it lately), but with the same results. Is there any other way to flash it?
I've also had no luck to get ADB/logcat running either.
you can flash roms through a custom recovery image. but if you don't have any luck by flashing an ruu update the custom recovery probably won't help either. thought about returning the hero for a refund? sounds like a defective device to me...
Returning it would be a major hassle as I live in Kuwait and got it sent to me from the UK through some 3rd party supplier.
I'm also not so sure about the device being defective because when I first did the upgrade to the .5 version (back in Sept 2009, when I got the phone), it worked like a charm. So I'm not sure what went wrong between then and now, when I made the latest .66 update a few days ago.
It's weird, I can make calls, send/receive SMS, but I just can't get to the main home-screen GUI. Keep seeing that HTC logo!
Thanks for trying though.
i'd say try some other roms, but for that you need to install the custom recovery image, and for that you need to create a goldcard and downgrade, so it's kind of a hassle as well... good luck with what ever you go for.
Ok so a couple days ago in preperation of selling my evo 3d , i flashed a new rom of which i cant remember , i also beleive i flashed silverneedle kernel through the gpl tool app. Ever since no matter what i do , i cant get past the white HTC screen , it just reboots from there . Ive tried the superwipe tool and it seemed like it was going to work , but nothing . Ive also looked over several threads on here and no one seemed to have had an answer, thus im making my own thread. Im currently trying to flash warm 2.3 rom. I even thought maybe it was a bad transfer to the sd card because the sd card was acting funky when the rom was being transfered to it in my galaxy s2 so then i just downloaded it dirtectly from dolphin browers to the root of the sd card right from the galaxy to see if that was the problem. Still nothing , just the htc screen. Anybody have any idea how to fix this? I just want the phone back to stock so i can sell it , ugh. O and im on HBOOT 1.5 with the official HTC unlock and S-on.
I'm in the same boat. Fairly new evo 3d with hboot 1.5 rooted through htc. I've been flashing several roms over the last few days all with success, found I like Xplod XE from team nocturnal the best, nice and fast. What i found was that the kernel never changed, as I had read would happen with s-on. After doing some reseach and trying a few things I ran into your problem. Now no matter what or how i flash i'm stuck in a boot loop at the white HTC screen. The last kernels I've attempted to push were Tiamat_E3D-v1.1.0-Sense and silverneedle-test5. I've tried various combinations of wiping both caches with and without factory reset/system wipe as well as flashing several roms with success, still stuck with the boot loop. Flashed all roms through TeamWin Recovery and pushed kernels through clockwork recovery via fastboot/cmd promt.
Darthdaddy said:
.... and pushed kernels through clockwork recovery via fastboot/cmd promt.
Click to expand...
Click to collapse
Not sure about this.
But when flashing kernels, it happens through fastboot. You shouldnt see clockwork anything.
I dont quite understand adb or how to push things through command prompt so im not even going there but i have tried the RUU method and i keep getting an unknown error at the end of things and then nothing happens. Through all of this i still have recovery , which is good , but its becoming useless because nothing is sticking. Previously the gpl app let me flash kernels flawelessly. I had a cracked screen and a replacment put on. I take it home , power up the evo and notice that its acting really buggy and funny , so i flash a new rom and kernel and am now in the never ending bootloop mode. Its getting really frusuturating. Im about to try re locking it and see if that works. I dont even care if i lose root , just want to go back to a fresh phone.
carnivalrejectq said:
I dont quite understand adb or how to push things through command prompt so im not even going there but i have tried the RUU method and i keep getting an unknown error at the end of things and then nothing happens. Through all of this i still have recovery , which is good , but its becoming useless because nothing is sticking. Previously the gpl app let me flash kernels flawelessly. I had a cracked screen and a replacment put on. I take it home , power up the evo and notice that its acting really buggy and funny , so i flash a new rom and kernel and am now in the never ending bootloop mode. Its getting really frusuturating. Im about to try re locking it and see if that works. I dont even care if i lose root , just want to go back to a fresh phone.
Click to expand...
Click to collapse
The info here should fix you up. Lock the phone before you run the RUU.
Edit: Also, I never found the need to push files from adb. I just put them in my c:\android-sdk-windows\tools folder. If they need to be on the sdcard, I just drag and drop.
Followed directions from another site to work through command prompt and get into recovery, pm me for the link. Made sure i had my rom file on my sd card, did a factory reset then manual install of rom via clockwork then rebooted. Went through fine.
tailsthecat3 said:
The info here should fix you up. Lock the phone before you run the RUU.
Edit: Also, I never found the need to push files from adb. I just put them in my c:\android-sdk-windows\tools folder. If they need to be on the sdcard, I just drag and drop.
Click to expand...
Click to collapse
Do i have to have adb setup to relock? i typed the fastboot oem lock into command prompt and nothing happened. i am on a different new computer than i was when i unlocked the phone in the first place.
carnivalrejectq said:
Do i have to have adb setup to relock? i typed the fastboot oem lock into command prompt and nothing happened. i am on a different new computer than i was when i unlocked the phone in the first place.
Click to expand...
Click to collapse
Youll need to have all the necessary files/programs which I imagine are fastboot, adb, device/android drivers...
Ok ive relocked the phone but RUU is not working , i still keep getting an error, and then when it gos back to the bootloader it says "Hboot version is Older!" and "Update Failed!" This time though RUU makes it a little further about a quarter of the way in where it says "sending" , before it does this , though. I never end up actually getting a progress bar on the phone or the little exclamation points. Im totally lost lol.
carnivalrejectq said:
Ok ive relocked the phone but RUU is not working , i still keep getting an error, and then when it gos back to the bootloader it says "Hboot version is Older!" and "Update Failed!" This time though RUU makes it a little further about a quarter of the way in where it says "sending" , before it does this , though. I never end up actually getting a progress bar on the phone or the little exclamation points. Im totally lost lol.
Click to expand...
Click to collapse
Try this. Watch the vid, download the files.
Frankly, you should be able to run the RUU, so long as youre 'relocked'. Thats how Ive done it, multiple times. Hopefully we can get you back to stock.(Which we can)
Whew , i finally got it! The last part there was my erorr for using an older RUU , i didnt look close enough and i thought i was using 2.08. So i dled the 2.08 one and now its all good to go. Haha literally been doing this since 930 am. Thanks for the help guys , btw.
The phone was working great, other than the noise cancelling mic cancelling out my voice, but I thought since the update was available, I might as well do it. Once I got on ICS I was having quite a few issues: overall slower, delay in the screen turning on, hotter battery, longer time to charge, wallpaper would flash on before the HTC screen when booting up, there were more just can't remember right now.
I hear about the Global update and think it may fix some of the problems I was having, but they got worse. Now I still have everything I did before (except maybe the hot battery) Also have 3 new issues now: the screen doesn't come back on when I take it away from my ear during a call, browser goes white when going to a new page and I have to reload the page, can't post on any forums in the browser.
Here's the process I went through getting the Global (copied from another forum that I was updating as I was going)
I downloaded it from android police, got to step 6 of the directions, looked away from the phone to see what step 7 was. The phone vibrated and is now on the screen with the green down arrow and 2 in a circle around it. Says "Updating Software from Verizon Wireless" with a green progress bar. Hope I did it right.
That went through rebooted to HBOOT, pressed vol. up twice. It checked everything. Rebooted. Pressed. Vol. up to install. Upadated everything. Pressed power to reboot.
Took a little while on the white HTC screen, now says "Andoid is upgrading..." "Optimizing application [some number] of 77." I think I did it right.
Just checked and everything is right. Woo-Hoo! Not that I'll ever use global, I was hoping it may have fixed some of the bugs I was having, but no
Also of note, I didn't pull the battery. My case is hard to get off, so I just turned off fast boot and that worked.
Click to expand...
Click to collapse
What do I do at this point? My phone is getting less usable by the day as I keep noticing all these bugs.
Wipe your phone clean and use the RUU that android police posted today to install the latest patched OTA clean. That's what I'd try anyway.
I'll try that in the morning, thanks. Hopefully all goes smoothly. Still learning how to do things (afraid of rooting, but that's another thread)
VooDooCC said:
I'll try that in the morning, thanks. Hopefully all goes smoothly. Still learning how to do things (afraid of rooting, but that's another thread)
Click to expand...
Click to collapse
There are plenty of knowledgeable members here to walk you through it if you just shoot someone a pm. It's all very simple.
As for your problem, try the ruu hopefully that works I'm not sure about the mic canceling out your voice that might be a hardware problem let's hope not
Sent from my ADR6425LVW using xda app-developers app
Stupid person time (I don't believe there are stupid questions)
By "wipe phone clean" then flash the RUU. I get the flashing part, but what do you mean by wipe clean. Is there another step in there or does it automatically happen when flashing? I've only been in recovery once, so I didn't really study the options. On my D2, there was a wipe option.
VooDooCC said:
Stupid person time (I don't believe there are stupid questions)
By "wipe phone clean" then flash the RUU. I get the flashing part, but what do you mean by wipe clean. Is there another step in there or does it automatically happen when flashing? I've only been in recovery once, so I didn't really study the options. On my D2, there was a wipe option.
Click to expand...
Click to collapse
The RUU should wipe it but you can go into recovery and wipe /data and /system to remove the current rom.
Making sure I got all this right, but won't be trying until tomorrow afternoon. Only at 40% charge and going out of town in the morning and need the phone.
1. Rename the Android Police download to PH98IMG.zip and copy to sd card (don't have to extract anything out like I did on the .1)
2. Boot into recovery (vol. down and power)
3. Let it start flashing (If it starts automatically, how do I get to the wipe /data and /cache options?) I know it should be wiped auto. but I want to do it myself to make sure.
4. Pray to Andy that there's no bugs this time.
You need to boot into bootloader, not recovery, that will happen when you do the battery pull then start it volume down + power. I'm pretty sure the RUU will wipe everything so you should be good.
Problem with newest ICS
The new ICS has a problem with the browser. Links are squirrelly when touched; sometimes
no reaction, sometimes checks every box on the page. Just does not feel right when moving
around on web pages.
Seems ok to me, I'd recommend Chrome over stock unless you need Flash support anyway.
Sorry, I got the terms confused on the terms. I knew it was vol. down and power though
I finally got around to flashing the RUU, all is well so far, will report back if anything changes.
I'm s-off but my bootloader is unlocked. Do I need to relock the bootloader before flashing the RUU.
Sent from my ADR6425LVW using xda app-developers app
There is a tradition on rezounds to always install an RUU two times in a row, then let it boot up normally before installing custom things like hboots, recoveries, or ROMs.
I used to read posts of people saying that it must be done twice to assure everything gets installed right, and to avoid problems.
So, I recommend doing the ruu twice in a row, especially if your phone was not stock beforehand.
Howard
p.s. my favorite browser is opera mobile.
If s-off and unlocked, there is no need to relock to install an RUU.
Turns out I got a little too anxious. I thought stuff was working, but that was just because I was thankful that I installed the RUU right, still new to this. Still having all the same problems though
When you say install twice in a row, should I just try installing it once again tomorrow or twice since I downloaded an app or two?
Also, you say twice, then boot up normally, when I installed this it just booted up after the install was finished. Is there a way to install it again before it boots for the first time?
method
Make sure the Android Police 3.14.605.12 renamed PH98IMG.zip on your sdCard.
Boot up with Volume down, Power to get into hboot. It will ask your permission with a
Volume up and then run the update. I think they mean after 1st boot, answer English,
and get out of setup with No and default until steady. Do a factory reset in Settings,
Storage and boot up again. Then shut her off again and restart as previously to run that
PH98IMG.zip again.
After the next boot up, insert actual information like Google etc. to start Google Play
and fetch your favorite apps. Then you're running 100% stock.
noticed the same thing with in calls. Pull the phone away from your ear and the screen should come back on, but it seems delayed. I usually have to tap the power button twice to get the screen back on.
Running simplistic 3.0 which is based on the newest leak, after flashing the leak.
FWIW I have the issue with the screen not coming back on after pulling the phone away form your ear as well, however I'm on the ICS OTA, not the global.
I never had the problem on the ICS OTA, but I also only had that for a couple of days before getting the global (.1) from Android Police.
In the process of doing the second flash. As per michaels instructions.
I went to Verizon yesterday and tried seeing about exchanging the phone, since it's having all these problems, and was told no. That it's so common and pretty much every phone has the same things, so it's considered to be working and I just have to wait on a patch. He then told me that if I wanted I could void my warranty and s-off it to go back to GB. I found that kind of odd. Then he tried pushing the Razr on me, I said no I like HTC so then he told me that the Droid 4's are having the same problems too.
Hi,
I'm a bit new here and running a good old-fashioned stock Inc 4G LTE, never rooted or flashed to new ROM. It DOES have the latest OTA update from Verizon a couple months ago.
This morning my phone suddenly went off after working OK. Then when trying to restart, I get an infinite boot loop and it won't get past the red Droid screen. I've searched various threads and tried what I think are the most obvious things, and nothing seems to help. But I want to make sure there are no other options before I throw it in the trash.
Here's what I tried:
- Tried entering Safe Mode by holding down volume key after HTC screen comes on. Makes no difference, does not enter Safe Mode.
- Get to HBOOT OK. Says 'LOCKED' and I am running HBOOT v.1.15.0000.
- - In HBOOT, I've tried running Recovery a couple times. Seems to go OK, but just starts looping when restarting.
- - In HBOOT, tried running Recovery > Wipe Cache Partition. Says cache is cleared.
- - In HBOOT, tried running Recovery > Wipe data/factory reset. Seem to go through OK.
- - In HBOOT, tried running Factory Reset.
- - In HBOOT, tried running Clear Storage.
- Pulled battery and tried spare.
- Removed SD card.
Some history - this phone has always been very sluggish. A few months ago started shutting down when doing camera intensive things (would jump to battery at critical level). So I did a factory reset a couple weeks ago and was slowly adding some of the essential apps back in. It crashed trying to upload photos to Facebook. Last night I had just moved some apps to the Phone storage and set my Sound Profile app to change profiles in the morning. This is about the time the phone crashed.
Anything else I should try before giving up?
Can I try to root and install a custom ROM to fix when in this state? Is this now possible with latest OTA update?
If custom ROM is last chance, is there a really solid one running 4.3 and Sense?
THANKS! May be time to get a HTC One or iPhoney, as I'm just not into huge phones that are coming out...
iRunNaked said:
If your on bootloader 1.15.0000 and now 1.16.0000, try using the stock Ruu and restoring the phone. If not, try rebooting in bootloader and factory reset.
If that doesn't work, gain root (if you haven't) and get s-off/unlock bootloader/CID set to 111111, and try a custom rom. If all else fails, take it back to stock and unroot/s-on/CID back to VZW/Relocked.
Call Verizon and tell them you need a replacement. The phone randomly gets real hot and reboots. They should send you a new one no problem.
I girlfriend had the random reboots, ending up getting it replaced. Now shes on her 4th or 5th incredible lte. (data Issues & random reboots)
Click to expand...
Click to collapse
I tried running a stock 2.17.. RUU, but got a "Failed" message because the software was too old. I'm guessing that is because I'm on the newer 2.19.. OTA update?!? Anyone know where to get a RUU file for the latest 2.19 version? I've been searching with no luck.
I'll have to research how to root/unlock the phone when it won't boot. Any specific threads that have fairly detailed instructions would be appreciated.
Thanks!
jethrodesign said:
I tried running a stock 2.17.. RUU, but got a "Failed" message because the software was too old. I'm guessing that is because I'm on the newer 2.19.. OTA update?!? Anyone know where to get a RUU file for the latest 2.19 version? I've been searching with no luck.
I'll have to research how to root/unlock the phone when it won't boot. Any specific threads that have fairly detailed instructions would be appreciated.
Thanks!
Click to expand...
Click to collapse
I looked at the thread about how to successfully root & flash the phone when it has the Verizon OTA update (2.19.xx) found here: http://forum.xda-developers.com/showthread.php?t=2664460.
But it appears at first glance that to do it the phone needs to be booted up and connected to the computer via USB. I can only get my phone to the HBOOT screen, nothing else.
- Can anyone confirm that to unlock and/or flash a new ROM on this phone that it has to be able to boot up? No way to do it on my phone with the 2.19 software and constant rebooting?
Thanks. It's cosmetically perfect, so I feel bad about throwing it away. If I can get it back up somehow I could at least sell it or give it to someone in need.
jethrodesign said:
I looked at the thread about how to successfully root & flash the phone when it has the Verizon OTA update (2.19.xx) found here: http://forum.xda-developers.com/showthread.php?t=2664460.
But it appears at first glance that to do it the phone needs to be booted up and connected to the computer via USB. I can only get my phone to the HBOOT screen, nothing else.
- Can anyone confirm that to unlock and/or flash a new ROM on this phone that it has to be able to boot up? No way to do it on my phone with the 2.19 software and constant rebooting?
Thanks. It's cosmetically perfect, so I feel bad about throwing it away. If I can get it back up somehow I could at least sell it or give it to someone in need.
Click to expand...
Click to collapse
If you want to use mdmower's "temp-root" trick, then you'll need to be able to access the device through Android Debug Bridge. Can you see the device if you type
Code:
adb devices
after booting up past the bootloader?
stringedonbass said:
If you want to use mdmower's "temp-root" trick, then you'll need to be able to access the device through Android Debug Bridge. Can you see the device if you type
Code:
adb devices
after booting up past the bootloader?
Click to expand...
Click to collapse
Hi. I've never tried running ADB. Not very familiar with it at all. But my phone will not boot past the HBOOT option. No matter what I've tried, it will just go into a rebooting loop. I'm assuming it needs to be fully booted up to work with ADB?!?
- Is there an RUU for the latest software update (2.19.xx) somewhere that I can try running to see if it will help it fully boot?
- Any other options?
Thanks!
jethrodesign said:
Hi. I've never tried running ADB. Not very familiar with it at all. But my phone will not boot past the HBOOT option. No matter what I've tried, it will just go into a rebooting loop. I'm assuming it needs to be fully booted up to work with ADB?!?
- Is there an RUU for the latest software update (2.19.xx) somewhere that I can try running to see if it will help it fully boot?
- Any other options?
Thanks!
Click to expand...
Click to collapse
Yes, my understanding is that to use adb, you need to be able to boot into the OS with usb debugging turned on. Hopefully someone will come along with a worthwhile response!
Is anyone aware of more current RUU's than are menteioned here?
http://forum.xda-developers.com/showthread.php?t=1770978
---------- Post added at 05:19 PM ---------- Previous post was at 05:07 PM ----------
If the phone failed as a completely stocked phone, why not try returning as opposed to figuring out how to root a broken phone?
Hello all, and thanks in advance for your help. I don't know if all of this is relevant to what happened, but I'm including it in case there's some small clue.
My phone was an S-OFF running HBOOT 2.09. I have been running Deck's CM builds for a while now with no issues. Last week, I decided to update to the new firmware which included the new partition layout.
HTC's RUU executable did not work, so I used the two zip method in this post. I first renamed rom_01 to PJ75IMG.zip, placed it on the SD card, rebooted and installed, then did the same with rom_02. Loaded everything up, seemed great with the stock image. After verifying everything was working fine, I flashed a new recovery (2.7.0.0b, via PJ75IMG.zip as well), and installed the latest OmniROM (3/31) via recovery. I had some issues with the PA 0-Day GAPPs that were recommended (force close errors with Google Keyboard) so after reflashing Omni switched back to the 12/09 GAPPs in Deck's thread. Everything seemed great.
A few days later, after having the phone in my pocket, my screen turned into a rainbow of pixels. Here is what it looks like: http://imgur.com/9ef6F8z It still seemed to work, just the screen was always that rainbow.
Thinking it was an issue with the firmware, I tried to RUU back to a somewhat earlier stock by using ViperRUU 3.16.651.3. However, after going through the RUU process, it had gone about 30-40 minutes with no updates, so I thought it had crashed. I checked to see if that was normal, and saw that it was not and they recommended restarting the process. I restarted both the ViperRUU (couldn't find phone anymore) and the phone, and now I think my phone might be totally bricked.
When I turn it on, there is nothing on the screen. It vibrates once, like it's trying to start, but nothing happens and the phone is otherwise unresponsive. I can try to boot into the bootloader (volume down + power) and that SEEMS to work, but the screen doesn't turn on then either. Occasionally, it will display the same rainbow pixels after "selecting" an option on the bootloader menu (I'm assuming). I've also pulled the SD card to insure it's not trying to read any PJ75IMG.zip.
I can't seem to get it to go into fastboot mode (single power button click after thinking I'm in the bootloader) and adb only shows the device as OFFLINE when I can get it to detect. It's hard to know what's going on without the screen.
Has anyone heard of this before? I probably ****ed something up but other than ending the ViperRUU early, not sure what. Thanks in advance, I very much appreciate it.
matt135353 said:
Hello all, and thanks in advance for your help. I don't know if all of this is relevant to what happened, but I'm including it in case there's some small clue.
My phone was an S-OFF running HBOOT 2.09. I have been running Deck's CM builds for a while now with no issues. Last week, I decided to update to the new firmware which included the new partition layout.
HTC's RUU executable did not work, so I used the two zip method in this post. I first renamed rom_01 to PJ75IMG.zip, placed it on the SD card, rebooted and installed, then did the same with rom_02. Loaded everything up, seemed great with the stock image. After verifying everything was working fine, I flashed a new recovery (2.7.0.0b, via PJ75IMG.zip as well), and installed the latest OmniROM (3/31) via recovery. I had some issues with the PA 0-Day GAPPs that were recommended (force close errors with Google Keyboard) so after reflashing Omni switched back to the 12/09 GAPPs in Deck's thread. Everything seemed great.
A few days later, after having the phone in my pocket, my screen turned into a rainbow of pixels. Here is what it looks like: http://imgur.com/9ef6F8z It still seemed to work, just the screen was always that rainbow.
Thinking it was an issue with the firmware, I tried to RUU back to a somewhat earlier stock by using ViperRUU 3.16.651.3. However, after going through the RUU process, it had gone about 30-40 minutes with no updates, so I thought it had crashed. I checked to see if that was normal, and saw that it was not and they recommended restarting the process. I restarted both the ViperRUU (couldn't find phone anymore) and the phone, and now I think my phone might be totally bricked.
When I turn it on, there is nothing on the screen. It vibrates once, like it's trying to start, but nothing happens and the phone is otherwise unresponsive. I can try to boot into the bootloader (volume down + power) and that SEEMS to work, but the screen doesn't turn on then either. Occasionally, it will display the same rainbow pixels after "selecting" an option on the bootloader menu (I'm assuming). I've also pulled the SD card to insure it's not trying to read any PJ75IMG.zip.
I can't seem to get it to go into fastboot mode (single power button click after thinking I'm in the bootloader) and adb only shows the device as OFFLINE when I can get it to detect. It's hard to know what's going on without the screen.
Has anyone heard of this before? I probably ****ed something up but other than ending the ViperRUU early, not sure what. Thanks in advance, I very much appreciate it.
Click to expand...
Click to collapse
This is a known hardware issue. Look here:
http://forum.xda-developers.com/showthread.php?t=2470296
It happened to me as well. I called Sprint and they replaced my phone for no charge.
Sent from my EVO using XDA Premium 4 mobile app
Ah, thanks for the link. I don't have TEP and it's out of warranty but I'll give Sprint repair a shot. Thanks!
Evolution_Freak said:
This is a known hardware issue. Look here:
http://forum.xda-developers.com/showthread.php?t=2470296
It happened to me as well. I called Sprint and they replaced my phone for no charge.
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hmm...I bought mine secondhand and am going to be running it on Ting, you think they would do that for me if it happens? :laugh:
matt135353 said:
Ah, thanks for the link. I don't have TEP and it's out of warranty but I'll give Sprint repair a shot. Thanks!
Click to expand...
Click to collapse
I have TEP but that never even came up. I never filed a claim. They originally wanted me to go to a Sprint store to have a tech look at it but I complained that the nearest store is an hour away. So they took my word, after explaining what was happening, and sent me a new (refurbished) EVO and then I sent them the old one in the package they provided with the new one. This was back in November of 2013 and I never heard anything else about it.
Sent from my Nexus 5 using XDA Premium 4 mobile app