My partner just bought a brand new 5X, 16gb white. Serial no. 602.
She was booted up the phone today, fine, started syncing stuff what have you. Started updating to the Jan update etc until the latest March update installed. Now, the touch screen doesn't respond. You have to turn the screen off and on a few times for you to be able to use the screen for a few seconds before it does it again.
I have;
1. Gone into settings to ensure magnification gesture or something is turned off, and it was.
2. Wiped cache in bootloader, factory reset
What's causing the issue? Is it hardware? It was fine before the March update.
Flash factory images
Sent from my Nexus 5X using Tapatalk
nazmul.rr said:
Flash factory images
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Which one? I've never flashed ROMs before. Will this void any warranty?
No unlocked bootloader flash factory images thn lock again
Sent from my Nexus 5X using Tapatalk
nazmul.rr said:
No unlocked bootloader flash factory images thn lock again
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Tried it, problem still there. Flashed to the January Rom.
Anyone? I also now get a "There is an internal error on your android device" message when booting up
Related
I searched and searched not only here, but other forums as well and did not find a solution to my problem. I've been a long time lurker and know how things go around here, so I made sure I covered my bases. I've been rooting and flashing phones since 2009 and this is the first time I've had a problem I couldn't fix myself.
The phone:
Verizon Galaxy Nexus -- LiquidSmooth 4.1.2 rom -- Latest Franco Kernel
Here's what happened:
I was getting into my car and my phone didn't pair with my stereo like it usually does. I tried turning BT on and off, but not dice. So I hold the power button and select reboot. It pops up with the Google logo as per usual, then the boot animation for about 10 seconds until the animation freezes, the screen goes blank, then the phone vibrates and displays the Google logo again and the cycle continues until I pull the battery.
What I've tried so far:
I tried restoring a nandroid first, no luck. Then I did a factory reset and wiped the cache, no luck. I tried re-flashing other ROMs I had on the device, no luck. I tried doing a factory reset via the WugFresh ToolKit, but the USB drivers don't see it while it's in recovery. Every time the same, although the boot animation changes depending on the ROM.
Anyone have any ideas? Or is this an excuse for me to order a Nexus 4 once they become available again?
Thank you
Have you tried fastboot? You could try re locking the bootloader to format the device.
Try reloading the factory image. Could repair everything, then you can flash your ROM again. I have one up if you need it in the marketplace. Unless you plan on switching to a gsm carrier, you won't be using the nexus 4 on vzw. Why I recently jumped ship.
Sent from my SGH-I747 using xda premium
063_XOBX said:
Have you tried fastboot? You could try re locking the bootloader to format the device.
Click to expand...
Click to collapse
How do I format the device if not from a PC? I can't get my computer to recognize it. I did format from recovery for /system, /cache, and /data. Again, no luck.
gunz.jones said:
Try reloading the factory image. Could repair everything, then you can flash your ROM again. I have one up if you need it in the marketplace. Unless you plan on switching to a gsm carrier, you won't be using the nexus 4 on vzw. Why I recently jumped ship.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Luckily I had a factory image on there before this happened, but it didn't work. Same issue.
I had the same issue a while back.
Hold down both volume keys along with the power button (loads up into fastboot.) From there you should be able to use adb to lock/unlock the bootloader.
Sent from my Galaxy Nexus using xda premium
TomBall718 said:
I had the same issue a while back.
Hold down both volume keys along with the power button (load up the bootloader.) From there you should be able to use adb to lock/unlock the bootloader.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Did it. No change.
Thanks for the replies.
Well if you've relocked/unlocked the bootloader and it still won't boot up then you could always lock it again and bring it to vzw and have them get you a new one.
Or wait for someone smarter to post
Sent from my Galaxy Nexus using xda premium
Try this...
Try using the Rootkit from MSKIP- http://forum.xda-developers.com/showthread.php?t=1400871
While you have your phone in FASTBOOT, try to push a file to your phone. Try and push the SUPERWIPE.zip for the Galaxy Nexus.
After you push the file to the phone, try to push the factory rom to your phone.
If that does not work the, simply install CWM from the toolkit. This will allow you to boot up to CWM recovery by holding the Volume up & down at the same time, then push the power. This will allow you to do the superwipe.zip and then try to reinstall the rom you want.
Dear community,
i have a reboot problem with my gnex gsm for several weeks now. The phone seems to be rebooting randomly after freezing. The only situation where no reboot occurs is when it is attached to the pc via usb docking station in developer mode.
Ususally, i had cyanogenmod nightlies installed, but i also tried stock 4.2.2 and 4.3 images. Moreover i tried several full wipes using cwm and twp recovery. After the last wipe, I did not recover anything using titanium backup. At the moment i am running on 4.3 stock image and stock recovery with no root. Bootloader is still unlocked. The phone keeps rebooting...
Has anybody an idea where to locate the problem (probably some certain log files) ?
My GNex had that problem. It started with random reboots. Then got into a boot loop from which it never recovered.
Good luck. Hope you don't have the same fate that I had.
Try flashing back to stock and lock and unlock bootloader. If that doesn't stop the reboots, IMO, time to look for a new phone.
Edit : You might want to send it to Samsung for repair, if you are still under warranty.
Sent from my Micromax A116 using Tapatalk 2
Check battery connections, replace battery
Update us later
viskon said:
My GNex had that problem. It started with random reboots. Then got into a boot loop from which it never recovered.
Good luck. Hope you don't have the same fate that I had.
Try flashing back to stock and lock and unlock bootloader. If that doesn't stop the reboots, IMO, time to look for a new phone.
Edit : You might want to send it to Samsung for repair, if you are still under warranty.
Sent from my Micromax A116 using Tapatalk 2
Click to expand...
Click to collapse
I've already tried your suggestion, but it didn't help.
Actually, I'm still under warranty, but i was hoping to solve the problem by myself to avoid being without phone for a few weeks.
beekay201 said:
Check battery connections, replace battery
Update us later
Click to expand...
Click to collapse
Already tried that, i have a replacement battery. By the way, the reboot problem also occurs when charging from the normal power supply. Only the usb connection with debug mode avoids rebooting.
Thank you for your advice.
CStauch said:
Already tried that, i have a replacement battery. By the way, the reboot problem also occurs when charging from the normal power supply. Only the usb connection with debug mode avoids rebooting.
Thank you for your advice.
Click to expand...
Click to collapse
Okay, so what do you think you can do next? That replacement battery, is it a stock battery?
beekay201 said:
Okay, so what do you think you can do next? That replacement battery, is it a stock battery?
Click to expand...
Click to collapse
Yes, it is not distiguishable from the original one.
I was hoping, that there can be any hint in some sort of log file or something.
Have you tried booting into safe mode to see if it is an app issue?
http://www.talkandroid.com/guides/b...or-tablet-into-safe-mode-for-troubleshooting/
Sent from my Micromax A116 using Tapatalk 2
viskon said:
Have you tried booting into safe mode to see if it is an app issue?
Sent from my Micromax A116 using Tapatalk 2
Click to expand...
Click to collapse
Just tried that, also no difference
Are you using the original cable to charge it? I've had problems where using cheap ebay cables made the touchscreen all jumpy and needed a reboot to fix. I changed to the original cable and it never happened again. Dont know if you could have a similar problem but with random reboot.
AzNxJoHnNy said:
Are you using the original cable to charge it? I've had problems where using cheap ebay cables made the touchscreen all jumpy and needed a reboot to fix. I changed to the original cable and it never happened again. Dont know if you could have a similar problem but with random reboot.
Click to expand...
Click to collapse
I'm using both the original cable and two docking stations from amazon, one with ac/dc adaptor and one with usb. The phone always reboots no matter if it is charging or not. Only when connected to usb in debug mode, there is no reboot.
CStauch said:
Just tried that, also no difference
Click to expand...
Click to collapse
I strongly suspect a hardware issue. You might be better off sending it for warranty repair.
Sent from my Micromax A116 using Tapatalk 2
SAME PROBLEM!
Tried with several ROMs and Kernels, also stock, disabling proximity sensor (there is someone with this sensor issue...) but nothing changed.
Now I made a fuuuul hard deep wipe, and installed AOKP ROM with Nexus Toolkit. I have to check if it will be working, if not I'm going to restore phone to stock (locked unrooted etc) and then try...
Same problem here.
This happened also to me on August... was an hardware issue for me
TKPL said:
SAME PROBLEM!
Tried with several ROMs and Kernels, also stock, disabling proximity sensor (there is someone with this sensor issue...) but nothing changed.
Now I made a fuuuul hard deep wipe, and installed AOKP ROM with Nexus Toolkit. I have to check if it will be working, if not I'm going to restore phone to stock (locked unrooted etc) and then try...
Click to expand...
Click to collapse
Still not working... I wiped everything and restored phone to stock locked, and got, in one day, "only" one reboot and two super-lag (it's better than before but it's not good). I gonna send it back to assistance...
TKPL said:
Still not working... I wiped everything and restored phone to stock locked, and got, in one day, "only" one reboot and two super-lag (it's better than before but it's not good). I gonna send it back to assistance...
Click to expand...
Click to collapse
I had the same problems... i've tried to make a clean installation of the stock factory image ... sent to assistance.. it was an hardware issue...
Have You tried to use the flash-all.bat to restore the factory image, the executable inside the factory image archive that flash the stock image automatically... try it
enricocid said:
I had the same problems... i've tried to make a clean installation of the stock factory image ... sent to assistance.. it was an hardware issue...
Have You tried to use the flash-all.bat to restore the factory image, the executable inside the factory image archive that flash the stock image automatically... try it
Click to expand...
Click to collapse
I reflashed with the Nexus Root Toolkit the factory image, so I guess it made automatically the flash-all.bat.
Tomorrow I'm sending the phone to assistance
enricocid said:
This happened also to me on August... was an hardware issue for me
Click to expand...
Click to collapse
So What was the hardware issue because i have the same problem and out of warranty..... And I would like to repair the phone.
If the costs aren't to high.
It is happening to my gnex since yesterday.
I was on shiny Rom and all of a sudden it began rebooting randomly.
Looking at the last_kmsg I found a kernel panic related to I/o error of the ext4-fs (or something similar).
I performed several wipe, thinking of a kernel issue.
It continued rebooting randomly so I completely reset to stock 4.3 including format of sdcard.
I have the feeling that reboots began when the sdcard began to fill.
I also re_locked the bootloader, but reboots still occur.
It is probably a faulty Emmc chip, I will go to the store for warranty.
Lionhe
Inviato dal mio Galaxy Nexus utilizzando Tapatalk
So I just bought a nexus 7 off of amazon(used). When I first turned it on, I got the google logo, and it stayed on until I held the power button. It then was blank, and then the google logo showed for about 10 seconds, and then it goes blank, 10 seconds, then blank, ect. unless I go into the bootloader.(it might be worth mentioning that the little unlocked lock icon appears under the google logo.) After I got into the bootloader, I shut the device down and waited for a while(maybe 15 minutes). Then i tried to reboot, and it successfully booted. However, before i could get into the settings to check what version of android it was running, it reboot and got stuck at the google logo again. Is it possible to fix this, or is there a hardware problem? Thanks.
Ultra_Saucy said:
So I just bought a nexus 7 off of amazon(used). When I first turned it on, I got the google logo, and it stayed on until I held the power button. It then was blank, and then the google logo showed for about 10 seconds, and then it goes blank, 10 seconds, then blank, ect. unless I go into the bootloader.(it might be worth mentioning that the little unlocked lock icon appears under the google logo.) After I got into the bootloader, I shut the device down and waited for a while(maybe 15 minutes). Then i tried to reboot, and it successfully booted. However, before i could get into the settings to check what version of android it was running, it reboot and got stuck at the google logo again. Is it possible to fix this, or is there a hardware problem? Thanks.
Click to expand...
Click to collapse
Have you tried flashing the factory image yet? If I ever bought a used Nexus device, even if it were functional, flashing the factory image would be the very first thing I would do. You never know what the previous owner may have flashed onto it, which is evident by the fact that he/she had already unlocked it. I would say since it's already unlocked, just flash the latest factory image and to make double sure, boot into recovery after flashing and "wipe data/factory data reset." It's a good sign that it at least boots, but you won't know until flashing the factory image.
OK, so what is the best way to flash the new image?
Sent from my Nexus 7 using XDA Free mobile app
Ultra_Saucy said:
OK, so what is the best way to flash the new image?
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
Check out the OP in this thread from the Nexus 5 forums: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701. Although it's for the N5, it is pretty much the exact same procedure for the the Nexus 7 (2013) (and Nexus 10). Basically, you'll need to install the ADB/Fastboot drivers to make sure your device is detected properly while in the Bootloader. Then, you can just flash the factory image. You can use Method 1 in the OP of that thread. MAKE SURE YOU DOWNLOAD THE CORRECT FACTORY IMAGE. You can find the latest factory image here: https://developers.google.com/android/nexus/images. The WiFi only model is "razor," while the LTE model is "razorg."
Ok so I flashed version 4.4.4 onto my device, and it seems to be working perfectly, but how can I root it to intsall other roms? I couldnt find anything on rooting 4.4.4, so is it too new?
Ultra_Saucy said:
Ok so I flashed version 4.4.4 onto my device, and it seems to be working perfectly, but how can I root it to intsall other roms? I couldnt find anything on rooting 4.4.4, so is it too new?
Click to expand...
Click to collapse
http://m.youtube.com/watch?v=6k4rCaMPSQ8
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Ok so I have Ben using my nexus 7 for about a fday after I flashed the stock ROM, and it started acting up again ( I didn't root it). It crashed, and then would not boot. Should I try to reflash the stock ROM again, or is there a hardware problem?
Sent from my Nexus 7 using XDA Free mobile app
Ultra_Saucy said:
Ok so I have Ben using my nexus 7 for about a fday after I flashed the stock ROM, and it started acting up again ( I didn't root it). It crashed, and then would not boot. Should I try to reflash the stock ROM again, or is there a hardware problem?
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
Confirm you have the right image and try flashing again. Make sure to wipe dalvik and cache too.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
How do I wipe the dalvik cache? Also, I used the image from googles Dev site, and I am sure it is the right one.
Sent from my Nexus 7 using XDA Free mobile app
Ok soo. i left the thing with my grandma for a month and it comes back to me in a bootloop. I tried unlocking the bootloader in adb with fastboot oem unlock but when i select yes the thing just freezes. i even left it on and plugged in the whole night. I cant flash anything until i unlock the bootloader. and one last thing is i cant delete stuff for example i type fastboot format/erase system it just stays there erasing system...
pls help!
BUMP
BUMP
BUMP
Do more research before you tinker with your toys. Even your xperia.
Sent from my LG-H810 using Tapatalk
'back to me in a bootloop' Hard Factory Reset in recovery won't work? 'I cant flash anything until i unlock the bootloader.' No **** sherlock...
Suhkoi said:
'back to me in a bootloop' Hard Factory Reset in recovery won't work? 'I cant flash anything until i unlock the bootloader.' No **** sherlock...
Click to expand...
Click to collapse
i am having the same issues.
Unit went flat (nexus 7 2013) due to moving house
boot loader locked (cannot unlock)
Nexus Root Toolkit v2.0.5 | WugFresh no help due to locked boot loader and cannot un lock (get screen options but does nothing when selected)
software can see unit and send commands fine.
out of ideas
i have has nexus 4,5,7 and 7 (2013)
they have all been rooted even ubuntu installed on some in the past
but looks like the 7 2013 is stuck due to licked boot loader that will not unlock.
thanks
Oliver
Got the same problem on my girlfriends Nexus 7 2013. Just like a brick. Bought a Nexus 9 for me and gave her mine. As far as I know, if its in 2 years of getting bought, it should be on guarantee, so if you are lucky to be in that time frame just send it to Asus for repair. My guess is a replacement.
Sent from my Nexus 5 using Tapatalk
So I came across a Nexus 5x where the previous owner has not rooted or unlocked the bootloader and it has stock recovery. It is on constant bootloop. As it's bootloader locked and stock recovery is there any way to resolve the issue or am I toast?
Be advised I have not purchased this phone yet. Merely communicating with the current owner.
Any advice would be greatly appreciated. Thank you in advance
Edit. Owner says it does not get past Google logo and he guessed it bootloop a around every 10-15 seconds. He does state it can go to stock recovery but will not stay....It bootloops from that after a minute or so.
Is this phone completely screwed?
Sent from my Nexus 6 using XDA-Developers Legacy app
ozzmanj1 said:
So I came across a Nexus 5x where the previous owner has not rooted or unlocked the bootloader and it has stock recovery. It is on constant bootloop. As it's bootloader locked and stock recovery is there any way to resolve the issue or am I toast?
Be advised I have not purchased this phone yet. Merely communicating with the current owner.
Any advice would be greatly appreciated. Thank you in advance
Edit. Owner says it does not get past Google logo and he guessed it bootloop a around every 10-15 seconds. He does state it can go to stock recovery but will not stay....It bootloops from that after a minute or so.
Is this phone completely screwed?
Sent from my Nexus 6 using XDA-Developers Legacy app
Click to expand...
Click to collapse
I'd ask the owner if he boots into fastboot, if it still t reboots on its own. They are known to have a defect that causes this though. So if he's done no modding to have soft bricked it, chances are it's a broken device you can't fix
Sent from my Nexus 5X using Tapatalk