Hello all,
I bought my asus nexus 7 (second edition) in 2014. i had no issues until recently. whenever i press the power button to turn it on the google logo comes on and then it goes black. I took it to a tablet repair place and the guy could not fix it. He said its "hard bricked." he said he was able to get to the bootloader page and unroot it ??? but he could not fix the issue of it timing out and turning off.
I was wondering if anyone has come across this issue and can my nexus 7 be saved/salvaged. As i told him i do not not care if its factory resetted.
He told me to post in a forum as it was developer issue and maybe a developer can fix it.
Any information would be greatly appreciated. I have only used this tablet for travel. so its virtually brand new. I would prefer not to waste money on another one.
darlinho said:
I was wondering if anyone has come across this issue and can my nexus 7 be saved/salvaged.
Click to expand...
Click to collapse
Hi, connect external power and start again. OK?
yes - replace the battery
no - read on...Do Fastboot Diagnostics. OK?
yes - flash factory image
no - check "Repair Options"
darlinho said:
Hello all,
I bought my asus nexus 7 (second edition) in 2014. i had no issues until recently. whenever i press the power button to turn it on the google logo comes on and then it goes black. I took it to a tablet repair place and the guy could not fix it. He said its "hard bricked." he said he was able to get to the bootloader page and unroot it ??? but he could not fix the issue of it timing out and turning off.
I was wondering if anyone has come across this issue and can my nexus 7 be saved/salvaged. As i told him i do not not care if its factory resetted.
He told me to post in a forum as it was developer issue and maybe a developer can fix it.
Any information would be greatly appreciated. I have only used this tablet for travel. so its virtually brand new. I would prefer not to waste money on another one.
Click to expand...
Click to collapse
is it going in fastboot mode? if yes then install adb fastboot drivers and then try to format partitions and reinstall factory imag.e
Related
Hi all,
I tried doing a search on this before posting this thread. No luck. I just got my TP2 on sunday. I let it charge and flashed HardSPL and a few roms. I noticed my phone would turn completely off when I open and close the screen. At first, I thought it was the display turning off to save power, but the phone is actually turning completely off and I need to hit the power button and boot it back up again. Is this a setting I need to change? Or could there be something wrong with my phone? I also tried going back to the stock rom to eliminate that as a cause and the same thing happens.
Any help is appreciated.
I have posted an almost similar question here with no reply.
http://forum.xda-developers.com/showthread.php?t=553378
Not sure what the problem is. In my case the solution is not to close the keyboard when OneNote Mobile is still open!
My colleague is having the same prob, from what he is experiencing, i would suggest a hardware fault, probably just a loose ribbon cable... but best send it back to HTC to avoid voiding your warranty
palatkik said:
I have posted an almost similar question here with no reply.
http://forum.xda-developers.com/showthread.php?t=553378
Not sure what the problem is. In my case the solution is not to close the keyboard when OneNote Mobile is still open!
Click to expand...
Click to collapse
I don't OneNote is my problem. Since I don't use it.
rosebud said:
My colleague is having the same prob, from what he is experiencing, i would suggest a hardware fault, probably just a loose ribbon cable... but best send it back to HTC to avoid voiding your warranty
Click to expand...
Click to collapse
I guess it's time to give TMO a call. Just need to flash everything back to stock.
Thanks for the suggestions guys. I was hoping to avoid having to send it back, but i might as well.
Albaholic said:
Hi all,
I tried doing a search on this before posting this thread. No luck. I just got my TP2 on sunday. I let it charge and flashed HardSPL and a few roms. I noticed my phone would turn completely off when I open and close the screen. At first, I thought it was the display turning off to save power, but the phone is actually turning completely off and I need to hit the power button and boot it back up again. Is this a setting I need to change? Or could there be something wrong with my phone? I also tried going back to the stock rom to eliminate that as a cause and the same thing happens.
Any help is appreciated.
Click to expand...
Click to collapse
Hi,
I had this issue to and send the phone in for repair. The said that it was a problem with the mainboard - replaced it and send it back. It now works perfect.
REMEMBER!!! If you want to send the TP2 in for repair you must reflash the SPL back to the original one, I think it is 0.79.0000 (see http://forum.xda-developers.com/showthread.php?t=550131 for how to restore to the original HardSPL)
discoverd the same issue, happened to me about a week ago for a few times, when i slide in/out the keyboard. It just habbend about 4 times, but didn't happend again since this time ... i will have a eye on it...
Same here. The screen turns off completely but the phone actually works and I can receive or place calls. Called the HTC support and they advised to try if a hard reset will fix it before sending the phone in. The tricky part here is that this issue can not be recreated easy in their service as it happens randomly with me (sometimes it works fine for days). I am still trying to find out what causes this issue on first place. I think it started right after I installed IGO 8 and changed some power settings in the ini file but it kept doing this after I removed it. I also tried to disable the light sensor (the one that turns the screen off when you place the handset to your ear during a call) because it looks exactly like this - screen turns off but the phone works. So, I will give it another week and I will try the hard reset.
What roms do you guys have this issue with? I am using the stock T-Mobile US with HardSPL.
wejergang said:
Hi,
I had this issue to and send the phone in for repair. The said that it was a problem with the mainboard - replaced it and send it back. It now works perfect.
REMEMBER!!! If you want to send the TP2 in for repair you must reflash the SPL back to the original one, I think it is 0.79.0000 (see http://forum.xda-developers.com/showthread.php?t=550131 for how to restore to the original HardSPL)
Click to expand...
Click to collapse
Did they replace the entire phone or just the mainboard?
ma6inista said:
Same here. The screen turns off completely but the phone actually works and I can receive or place calls. Called the HTC support and they advised to try if a hard reset will fix it before sending the phone in. The tricky part here is that this issue can not be recreated easy in their service as it happens randomly with me (sometimes it works fine for days). I am still trying to find out what causes this issue on first place. I think it started right after I installed IGO 8 and changed some power settings in the ini file but it kept doing this after I removed it. I also tried to disable the light sensor (the one that turns the screen off when you place the handset to your ear during a call) because it looks exactly like this - screen turns off but the phone works. So, I will give it another week and I will try the hard reset.
What roms do you guys have this issue with? I am using the stock T-Mobile US with HardSPL.
Click to expand...
Click to collapse
Did you ever resolve your issue? i ask because I am having he same problem on a Sprint Touch Pro 2
coppertop24 said:
Did you ever resolve your issue? i ask because I am having he same problem on a Sprint Touch Pro 2
Click to expand...
Click to collapse
Sorry, forgot to update this thread. I ended up getting a replacement from TMO. I am much happier now that my phone doesn't turn off whenever I close the screen. Get a replacement while you can and ask them nicely if they can overnight it to you. I did.
Actually, this was a software problem in my case - I did the hard reset 2 weeks ago and since then I have not experienced the issue. I am going to start installing my previous programs one by one to find out what caused the problem.
Same
I have the same problem,
The hard reset solve the problem?
please heeeeelp
Hi there,
I would need your assistant before sending for RMA. My newly bought GNex won't startup, won't go in recovery mode, won't go in to fastboot and not even manage to charge it too. It simply went dead.
It is SC-04D Docomo GNex and just a day before, it started to asked for Network PIN for unlock and within a day, it went dead.
Anyone have this similar problem and do we have a way to solve this?
Thanks.
no one could help on this?
Hi all.
I have a seemingly unique problem with my nexus, one day it got stuck in the boot logo. I gave the phone to a friend to fix, he used the galaxy nexus tool kit and halfway through solving the problem the phone crashed and now wont boot. At all. I am locked out of fastboot nothing at all is displayed on the screen, the tool kit wont detect the handset. There is no response when I push any of the buttons. I tried opening the phone and shorted out the power button. the only response I get from the phone it when I plug it in to windows 8 it get the sound on my pc to know it found hardware, then immediately followed by the disconnecting sound, and a little notification flashes from the system tray, If I am fast enough I can click on it and I get this message:
(I cant post a link as this is a new account) i.imgur.com/fmkE9Ki.png
I found on another thread that someone had a similar problem, they fixed it by getting a new battery, I did this and it still didn't work. i checked with a multimeter and they're both fine anyway. I am about to use my last resort and send it in to a paid service. Is there anything else i can try? or do you think a repair shop would have a better chance?
Thanks in advance for your time.
You're internal memory might be fried, happened to my first GN, was downloading something via a torrent app and all of a sudden the screen went black, had to pull battery and restart, first time it nearly got through the boot sequence but then froze up again, pull battery again to reboot but the second time it just started with major graphic errors and did not leave to Google logo screen.. Had to be replaced, good thing was that there was no way for service center to tell it was rooted ;P
Sent from my Galaxy Nexus using xda premium
Have you tried omap flash?
Beamed from my Grouper
All of the sudden the screen of my new Nexus 7 does not respond to touch.
I was looking to my emails, then stopped using the tablet for 10 mins and, when I tried to use it again, the lock screen did not recognize my swipe motion. I then tried to reboot it: pressed the power button, touched the Power Off option and nothing, also here it did not register my touch.
I was able to enter into recovery mode (using power and volume keys) and perform a factory reset but that did not solve the problem.
I am stuck at the lock screen and I cannot unlock it.
Any suggestion?
Thanks!
i think its just a 4.3 software bug. i love the tablet but the new update isn't very good IMO. google needs to get this right.
luigig said:
All of the sudden the screen of my new Nexus 7 does not respond to touch.
I was looking to my emails, then stopped using the tablet for 10 mins and, when I tried to use it again, the lock screen did not recognize my swipe motion. I then tried to reboot it: pressed the power button, touched the Power Off option and nothing, also here it did register my touch.
I was able to enter into recovery mode (using power and volume keys) and perform a factory reset but that did not solve the problem.
I am stuck at the lock screen and I cannot unlock it.
Any suggestion?
Thanks!
Click to expand...
Click to collapse
Since it has to be new I'd recommend just trading it in for another if a reboot or reset didn't fix it. I'd hate to see a fellow get stuck with an unreliable device. It could be many things though such as a bad digitizer or loose LCD ribbon flex cable or just a software glitch. To check the flex cable you would have to disassemble the unit which of course could potentially cause problems when trading it in. I dropped a tab one time though and it Jared my charge flex cable loose and just reinserting it fixed it. Good luck
fix-this! said:
i think its just a 4.3 software bug. i love the tablet but the new update isn't very good IMO. google needs to get this right.
Click to expand...
Click to collapse
Thanks.
Any idea about how to fix the problem (factory reset did not work) other then sending it back for a replacement?
Wait for Google to release official image then return to stock to see if it fixes it.
conan1600 said:
Since it has to be new I'd recommend just trading it in for another if a reboot or reset didn't fix it. I'd hate to see a fellow get stuck with an unreliable device. It could be many things though such as a bad digitizer or loose LCD ribbon flex cable or just a software glitch. To check the flex cable you would have to disassemble the unit which of course could potentially cause problems when trading it in. I dropped a tab one time though and it Jared my charge flex cable loose and just reinserting it fixed it. Good luck
Click to expand...
Click to collapse
Thanks.
I have a feeling it is a software problem. It was perfectly working and few minutes after it was not. Nothing, hardware-wise happened in the middle.
Software-wise, I noticed, on the top of the screen, the notification that a keyboard update was installed. Could have it broken something?
I thought a factory reset would have handled that possible problem but it did not.
luigig said:
All of the sudden the screen of my new Nexus 7 does not respond to touch.
I was looking to my emails, then stopped using the tablet for 10 mins and, when I tried to use it again, the lock screen did not recognize my swipe motion. I then tried to reboot it: pressed the power button, touched the Power Off option and nothing, also here it did not register my touch.
I was able to enter into recovery mode (using power and volume keys) and perform a factory reset but that did not solve the problem.
I am stuck at the lock screen and I cannot unlock it.
Any suggestion?
Thanks!
Click to expand...
Click to collapse
I had the problem last night and a reboot fixed it. Haven't seen the problem since.
mi7chy said:
Wait for Google to release official image then return to stock to see if it fixes it.
Click to expand...
Click to collapse
Mi7chy,
thanks.
A question: I started reading this guide (http://forum.xda-developers.com/showthread.php?t=1907796) to understand how to flash the factory image and I am worried I cannot perform step 1 of the Driver Installation section (I am unable to unlock the lock screen...).
Any suggestion?
Contemplating of returning this back for a replacement...
Thanks!
luigig said:
All of the sudden the screen of my new Nexus 7 does not respond to touch.
I was looking to my emails, then stopped using the tablet for 10 mins and, when I tried to use it again, the lock screen did not recognize my swipe motion. I then tried to reboot it: pressed the power button, touched the Power Off option and nothing, also here it did not register my touch.
I was able to enter into recovery mode (using power and volume keys) and perform a factory reset but that did not solve the problem.
I am stuck at the lock screen and I cannot unlock it.
Any suggestion?
Thanks!
Click to expand...
Click to collapse
I was in staples and their floor model had the same problem, I tried to fix it but it just sat there in a frozen state.
Hi all,
My Zenwatch had issues with a recent update basically it failed mid-update, the watch rebooted & seems to have partially loaded the OS.
The screen is not responding to touch but works on tilt, notifications etc all were working ok too.
Unfortunately i didn't turn ADB debugging on so i can't access it via PC/ADB either, now its lost my phone pairing too and as mentioned i cant access the swipe to do anything helpful on the watch.
As i bought the watch on holiday Asus UK aren't entertaining any help under warranty & can't suggest a repair shop either (though as i cant turn on ADB im not sure what they can do anyway!).
Have i now got a paperweight or is there a way of reflashing the Zenwatch without ADB turned on on the watch?
James
I got the same problem with touchscreen so i send it back to asus
Would love to but got the watch on holiday in the usa and now back in the UK..
Asus are saying return it to where you bought it.
Not much of a warranty if that's the case :-S
Sent from my D6603 using XDA mobile app
call Asus us
If you can get into recovery mode, you might be able to re-flash the update zip. It shouldn't matter that you don't have debugging turned on to do that, I think. There's some information on how to get to recovery mode here:
http://www.tomsguide.com/faq/id-2411652/reset-android-wear-watch-factory-settings.html
darn - got exited reading that until i saw that was for the LG!
I think im going to have to send it to a friend of mine in the US & get them to return it for me.
Thanks all
James
Jamesb4uk said:
darn - got exited reading that until i saw that was for the LG!
Click to expand...
Click to collapse
I don't think that matters. It should work the same on the Asus. I've used recovery mode to sideload updates on mine in the past.
Don't send your watch across the pond!
Jamesb4uk said:
darn - got exited reading that until i saw that was for the LG!
I think im going to have to send it to a friend of mine in the US & get them to return it for me.
Thanks all
James
Click to expand...
Click to collapse
You can get to fastboot by turning the watch on and swiping from the top left to the bottom right as soon as you see the Asus logo. I don't know if there is a similar method to boot directly to recovery, but fastboot should be all you need.
Edit: To boot to recovery swipe from the top right to the bottom left when you see the Asus logo.
-Andy
Sent from my Speak & Spell.
Doc Ames said:
You can get to fastboot by turning the watch on and swiping from the top left to the bottom right as soon as you see the Asus logo. I don't know if there is a similar method to boot directly to recovery, but fastboot should be all you need.
Edit: To boot to recovery swipe from the top right to the bottom left when you see the Asus logo.
-Andy
Sent from my Speak & Spell.
Click to expand...
Click to collapse
Tried to get to Fastboot, sadly didn't notice any difference in bootup - might indicate more of a hardware issue than software.
is it like phone based fastboot where you plug the USB lead in before fastboot? If so that could be difficult with the Zenwatch cradle!
James
Jamesb4uk said:
is it like phone based fastboot where you plug the USB lead in before fastboot? If so that could be difficult with the Zenwatch cradle!
James
Click to expand...
Click to collapse
No need to mess with a cable. The timing isn't picky either. I think you just have to do it between the time that the logo displays and the watch vibrates. You probably have some misnatched firmware due to the failed update. Maybe thats why the touch screen is borked. I wonder if there is a way to enter fastboot by jumping two of the pogo pins together. If not you're SOL.
-Andy
Sent from my Blendtec Total Blender.
Doc Ames said:
No need to mess with a cable. The timing isn't picky either. I think you just have to do it between the time that the logo displays and the watch vibrates. You probably have some misnatched firmware due to the failed update. Maybe thats why the touch screen is borked. I wonder if there is a way to enter fastboot by jumping two of the pogo pins together. If not you're SOL.
-Andy
Sent from my Blendtec Total Blender.
Click to expand...
Click to collapse
Yep firmware mismatch sounds about right. Sadly no luck with the fastboot at all.
Might give the jumping a go - got nothing else to loose, then i'll ask a friend of mine to return it.
Thanks for your help here Andy.
James
When you get the new one I bet I know the first thing that you're going to do
again, why not call Asus us? I had an issue with mine and they quickly sent me an rma label