Related
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.
I bought a used Evo on craigslist for a crazy great price. The screen was alleged to not work, but does. There's a pattern lock that the original owner doesn't remember. Any way around this? Other than doing a reset through the bootloader? I was able to get into the bootloader screen, using the volume keys, but they are unresponsive using within the menu. Am I completely out of luck? I would really love any advice you have. Thanks in advance.
We're not going to help you hack into a phone, especially when you only have one post here. If you want to get into the phone, do the right thing and contact the seller and ask what their pattern is.
Sorry. I didn't even think of how my post could be interpreted. I contacted the seller. They suggested trying N and reverse N shapes, to no avail. I wouldn't even be thinking about the pattern, if I could use the boot menu properly. I guess my question is: Is this a hard ware problem stemming from the alleged water damage? If so, why does the volume button work to launch the menu, but not within it?
You won't be able to bypass the pattern lock. You'll have to do what the seller should have and do a full factory reset...
Try the Supersonic 4.67 RUU in .exe form.
On some roms if you input the wrong pattern a certain number of times it will reset the phone and let you in after it has erased all info on the phone, if the volume buttons aren't working in the bootloader(hboot) what are your options in the menu is the first option bootloader or fast boot? If it says bootloader first fast boot maybe enables and selecting bootloader with the power button should activate the remaining options, if you have a power menu mod from lockscreen press and hold power button select reboot and 4 options will appear select recovery and from recovery wipe all/ data factory reset and reboot and you will have a completely stock phone, however with the seller not knowing their own lock pattern I'd say seller=thief and esn=blacklisted which will require a bit of shady tactics to get you activated on any carrier be it sprint boost metropcs etc
We are legion, for we are many
Sent from my Anonymous DeathStar in the depths of GalaXy S2
I know it's not much in the way of proof, but it's what I have to show I didn't steal the phone.
In any case, I'm being impatient as I'm still waiting for the USB cable I ordered to come in. I'm no stranger to rooting or custom roms. However, is it possible to wipe the phone without being able to use the vol keys to manipulate the hboot menu?
Also, the rom seems to be the stock rom, nothing custom, so the only option I get is to enter the google account credentials. That would be too convenient.
Thanks for addressing my concern that the vol key isn't working.
HBOOT
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
HBOOT USB
I can't do anything from this menu, except pull the battery.
jfiek said:
I know it's not much in the way of proof, but it's what I have to show I didn't steal the phone.
In any case, I'm being impatient as I'm still waiting for the USB cable I ordered to come in. I'm no stranger to rooting or custom roms. However, is it possible to wipe the phone without being able to use the vol keys to manipulate the hboot menu?
Also, the rom seems to be the stock rom, nothing custom, so the only option I get is to enter the google account credentials. That would be too convenient.
Thanks for addressing my concern that the vol key isn't working.
HBOOT
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
HBOOT USB
I can't do anything from this menu, except pull the battery.
Click to expand...
Click to collapse
Ur alright, u don't have to prove urself to anyone here. Just run a ruu.
Sent from my PC36100 using xda premium
USB cable arrived...
I was so excited when the USB cable arrived, until I found out it's in charge only mode, meaning my computer won't recognize the phone to properly run the RUU.
I'm lost.
jfiek said:
I was so excited when the USB cable arrived, until I found out it's in charge only mode, meaning my computer won't recognize the phone to properly run the RUU.
I'm lost.
Click to expand...
Click to collapse
Then put it in disk drive mode.
I can't; it's locked by the pattern lock that the seller doesn't remember. [see above]
Use one of the ruu.zip(pc36img) I think its named likke that from the bootloader ... Make sure the file(pc36img) is on the root of the sdcard and go into bootloader and it will ask you if you want to updTe and follow the instructions
Sent from my PC36100 using Tapatalk
I tried that with a bunch of different files, including this one. I get no image or wrong image errors.
Thanks though.
am having issues with htc touch pro 2, i have a custom rom install on it working fine then surfing the net on xda forum when i came across an article saying how to enable fm radio in htc touch pro 2 so was impress by this information then i decided to give it a try if it really works. when i go through it i was ask to download a file and install on my htc touch pro 2 and i think the file was a radio file after installing the file on htc touch pro 2 instruction came in to reboot my htc touch pro 2, when i reboot my htc touch pro 2 the phone refuse to power on i checked the battery still not powering on try soft and hard reset still not powering on but when i plug in charger into it either usb or wall charger it only indicate amber led light and won't power on when i press the power button and if remove the charger the amber led light goes off. pls can somebody help me with a solution because here in nigeria there is no service center for windows mobile or htc phones. i will be really greatfull if there is a solution to this problem.
flexxys said:
am having issues with htc touch pro 2, i have a custom rom install on it working fine then surfing the net on xda forum when i came across an article saying how to enable fm radio in htc touch pro 2 so was impress by this information then i decided to give it a try if it really works. when i go through it i was ask to download a file and install on my htc touch pro 2 and i think the file was a radio file after installing the file on htc touch pro 2 instruction came in to reboot my htc touch pro 2, when i reboot my htc touch pro 2 the phone refuse to power on i checked the battery still not powering on try soft and hard reset still not powering on but when i plug in charger into it either usb or wall charger it only indicate amber led light and won't power on when i press the power button and if remove the charger the amber led light goes off. pls can somebody help me with a solution because here in nigeria there is no service center for windows mobile or htc phones. i will be really greatfull if there is a solution to this problem.
Click to expand...
Click to collapse
First, I suggest you remove the battery for a few seconds. Then replace it and immediately push and hold the Send and End hardware keys on the front of your device then while holding those down push and hold the power button until the message shows on the screen saying to factory reset your device and follow the instructions to factory reset/hard reset.
If your device won't boot after that you probably need to run task29 then reflash your rom.
mr.horndoctor said:
First, I suggest you remove the battery for a few seconds. Then replace it and immediately push and hold the Send and End hardware keys on the front of your device then while holding those down push and hold the power button until the message shows on the screen saying to factory reset your device and follow the instructions to factory reset/hard reset.
If your device won't boot after that you probably need to run task29 then reflash your rom.
Click to expand...
Click to collapse
I have a question related to this device. I had put some sort of device lock on my touchpro 2. This was a long time ago, and I am now on an EVO 4G. However, I decided to keep the touchpro 2 as a backup device. I know i was running a non stock rom (as I flash pretty much all phones i get). The question is, will the method used above work in my case? Can I get past the lockscreen by using the steps above? Please let me know, as I just want to have the phone usable for the furture. I would as sprint, but as it is not activated and has a non stock rom on it, i doubt highly that they will be of any help. Please assist, as almost all forums on this model seem dead.
Thanks,
Andrew
thestick00 said:
I have a question related to this device. I had put some sort of device lock on my touchpro 2. This was a long time ago, and I am now on an EVO 4G. However, I decided to keep the touchpro 2 as a backup device. I know i was running a non stock rom (as I flash pretty much all phones i get). The question is, will the method used above work in my case? Can I get past the lockscreen by using the steps above? Please let me know, as I just want to have the phone usable for the furture. I would as sprint, but as it is not activated and has a non stock rom on it, i doubt highly that they will be of any help. Please assist, as almost all forums on this model seem dead.
Thanks,
Andrew
Click to expand...
Click to collapse
The hardware sequences are the same whether you're on stock or not... Good luck.
arrrghhh said:
The hardware sequences are the same whether you're on stock or not... Good luck.
Click to expand...
Click to collapse
I guess my question is not so much geared at if the button combination will initiate a hard reset, but more on the effect of the hard reset itself. What I mean, is will it revert to stock if I have another rom flashed? I only ask this because in other instances where I had a non stock rom, and i wanted to revert to stock to take into sprint, I always had to flash a stock rom and never even thought a hard reset would return to fresh out the box state. Unless I am missing something, I am guessing that a hard reset resets the device to whatever it was initially flashed to. For example, if in flashing rom B you made backup of rom A (which would include its settings), then if you chose to restore to the backup you created, I am thinking that that restore point becomes your point at which the hard reset will bring you to. (if that makes sense). In other words, you will never go back to stock off a hard reset, but you can go to a fresh version of the rom you flashed, or in my case, probably a backup i created which has the damn security pin already enabled. I will give the hard reset a shot once i get back home, but i am thinking that it may be a lost cause do to system backups created and restored to.
thestick00 said:
I guess my question is not so much geared at if the button combination will initiate a hard reset, but more on the effect of the hard reset itself. What I mean, is will it revert to stock if I have another rom flashed?
Click to expand...
Click to collapse
Oh, ok. No, it will go back to a fresh flash of whatever ROM you're on. It will NOT flash you back to stock, unless of course you're already on a stock ROM.
Like I said, it just wipes the phone and starts back from when you initially flashed that device. If you want it to go back to stock, you have to reflash stock. If you want to relock the device (undo hSPL) then you have to relock it - but be warned, you won't be able to unlock it again.
thestick00 said:
I guess my question is not so much geared at if the button combination will initiate a hard reset, but more on the effect of the hard reset itself. What I mean, is will it revert to stock if I have another rom flashed? I only ask this because in other instances where I had a non stock rom, and i wanted to revert to stock to take into sprint, I always had to flash a stock rom and never even thought a hard reset would return to fresh out the box state. Unless I am missing something, I am guessing that a hard reset resets the device to whatever it was initially flashed to. For example, if in flashing rom B you made backup of rom A (which would include its settings), then if you chose to restore to the backup you created, I am thinking that that restore point becomes your point at which the hard reset will bring you to. (if that makes sense). In other words, you will never go back to stock off a hard reset, but you can go to a fresh version of the rom you flashed, or in my case, probably a backup i created which has the damn security pin already enabled. I will give the hard reset a shot once i get back home, but i am thinking that it may be a lost cause do to system backups created and restored to.
Click to expand...
Click to collapse
As said, when you hard reset/clear storage your device all changes since the device was flashed are cleared and everything is reset to the clean condition right after the currently loaded rom had been flashed so basically everything is reset back to the way it was immediately after you flashed your current rom.
To revert back to the shipped state you have to flash the shipped rom.
This is my last ditch effort. Small back story: I somehow wiped EVERYTHING on my G2. EFS partition, ESN, data, SIM info., everything with dialer codes. All of my network information reads "unknown". I tried many methods from here on the forums to get this data back and it turns out I have lost my EFS partition- DNA for the network? I sent it to LG to get it fixed, having done a hard reset and leaving no trace of root. They sent it back without even asking and did no repairs. The note said "board bent". WTF?? How does the user bend the main board, especially when I never opened it? They voided my warranty and ripped off my IMEI/MEID sticker from the back of the phone.
Anyways, I am here with a brick. No network still. Here is what I have done:
1) .tot method to ZVC. Several more times... once to ZV7 where I lost touch capability. Luckily saved my arse with a micro->usb cable and a mouse.
2) attempted to root with ioroot25. Failed because the phone WILL NOT find recovery mode. adb, voldown+pwr then again from power off, and apps are unable to force the phone into recovery mode. I assume it is possible that my recovery mode is deleted?
3) Would have tried all of these "rewrite your efs/imei/etc" things but I can't do any without root. Can't root without recovery, can I?
4) Spent the last two weeks scouring the internet for a fix and going back to my Epic 4G temporarily.
Please help me, has anyone seen this before? Can anyone help me fix it? I am to the point where I would pay to have it fixed. Any experts out there? XDA has yet to let me down... I just need to know if I can fix it or if it is a brick so I can go searching for an old Sprint GS3.
Thanks all,
baublitz
what exactly happens when you tot back to ZVC? even thought the data is borked, can you still use the phone normally? Then proceed with ioroot ? what happens with ioroot when you running it after flashing tot? so if u can tot, that means u have download mode right? Sometimes i have a lot of issues getting into recovery, other times its really easy. Try again to get intro recovery. There really is a timing that needs to be precise. From experience, hold down vol down and power as soon as you see the LG logo, dont have the buttons pressed be4 the logo, only instantly after. good luck.
Device is fine and can be used via bluetooth mouse / keyboard - however, touchscreen went completly dead
formatted it - changed image, same result
anyone have any idea how to fix it , like a link to a video - part needed - or even a UK store
thanks
I have a similar issue.
I've had my Pixel C for around 11 Months, purchased direct from the google store in November 2017.
Last week I opened the tablet and the screen was totally unresponsive. The physical buttons were working so after several forced reboots which did not help I went for the Nuclear option and restored the device to factory defaults. This didn't work either and I was still unable to interact with the screen so logged a call with Google. I was about to invoke the warranty when suddenly the device responded again after a further reboot. I agreed with the support person that I would keep it for the time being, hoping it was just a glitch
Unfortunately the problem has recurred twice again and the only way to recover seems to be to power the device off, leave it for a "while" and power on.. not exactly scientific.
Has anyone else experienced similar issues? The device received a security update mid last week so I wonder if this is more than coincidence.
Any road, in this state the device is completely unreliable so I'll be looking to return it. I'm assuming google will not have any new replacements so I need to find an alternative android tablet
touch screen pixel c unreliable
owens2000 said:
I have a similar issue.
Has anyone else experienced similar issues? The device received a security update mid last week so I wonder if this is more than coincidence.
Any road, in this state the device is completely unreliable so I'll be looking to return it. I'm assuming google will not have any new replacements so I need to find an alternative android tablet
Click to expand...
Click to collapse
Same for me. The touchscreen is unresponsive, thought it would be hardware damaged, but did a couple of restarts, and all of a sudden I was able to type ten letters, then unresponsive again. Were you able to resolve this issue? Thanks!
after the last few updates the screen would respond less and less. This last update last night killed the screen completely. Zero response! I honestly think this is an error on their part but even if they fixed it in an update I cant get in to install the update!
I wanted to root and install a custom rom to see if that would fix it but honestly Ive been out of the loop for so long and without going into dev mode Im not sure I can at all.
tevil said:
I wanted to root and install a custom rom to see if that would fix it but honestly Ive been out of the loop for so long and without going into dev mode Im not sure I can at all.
Click to expand...
Click to collapse
I know how you feel. Same here, touchscreen became unresponsive before I could do any settings to flash anything else e.g twrp. Please share your next steps. Thanks
milgrave said:
I know how you feel. Same here, touchscreen became unresponsive before I could do any settings to flash anything else e.g twrp. Please share your next steps. Thanks
Click to expand...
Click to collapse
Im working on trying to unlock the bootloader right now. I tried the toolkit but its giving me a syntax error on trying to flash in fastboot since thats the only thing I can get to. Whats crazy is even the android recovery option is corrupt and this is a stock tablet. I really think google did this to these devices on purpose or unintentionally but has no intention on fixing them. I couldnt even run the update any since there is no way for me to get to anything.
Im looking for instructions on how to do everything from fastboot and ADB but everything is so outdated.
milgrave said:
I know how you feel. Same here, touchscreen became unresponsive before I could do any settings to flash anything else e.g twrp. Please share your next steps. Thanks
Click to expand...
Click to collapse
Hey sorry to post twice but try these. I just tried these steps and got my tablet fully wiped (do caches first) and working. Im enabling USB debugging and bootloader unlock and doing it all now. This was proven to be a google update issue to me.
Perform a master reset
https://thedroidguy.com/2019/08/how...3-xl-touchscreen-not-responding-issue-1094388
To factory reset your Google Pixel 3 XL:
Turn off your Google Pixel 3 XL.
Press and hold the Power+Volume Down buttons until bootloader mode (image of an Android with Start above it) appears, then release.
Select Recovery mode. You can use the Volume buttons to cycle through the available options and the Power button to select. The device will flash the Google start screen momentarily and then restarts in Recovery mode.
If presented with an image of a broken Android with “No Command” printed on the screen, press and hold the Power button. Press the Volume Up button once. Then release the Power button.
From the Android Recovery screen, select Wipe data/factory reset.
Select Yes. Wait for several minutes for the factory data reset process to complete.
Select Reboot system now. Allow several minutes for the factory data reset and reboot processes to complete.
Set the phone up again.
from there I just now used wugfreshs tool kit to unlock the bootloader and Im going to install TWRP and probably a custom rom to avoid updating again.
Update: def a software issue. I worked fine with this tablet for a few hours. Installed 1 app then it locked again. Opera browser. I've had my suspicions of the app for a while which is why I tested this app first. I'm using those same steps again to wipe and seeing if the touchscreen works again. I had trouble getting twrp and a room loaded due to encryption. There is apparently a decrypt file you need to install recovery and root. I can't seem to locate the correct one but wugs toolbox sees the device fine once the drivers are installed.
Ill keep this running and updated with results.
Full wipe and reset again and the screens not working again. What stinks is I once again can't get it into dev mode. I guess maybe it is a hardware issue. Sad, this thing has always been in a case and babied. I still think tho it's a bug with newer releases and the hardware in certain C's. It's beyond warranty though so what can we say to Google at this point. It's not even an old tablet and was pretty pricey. My Nexus 9 still runs perfectly!