Related
Hello,
So a couple of months ago I cracked the screen of my Nexus 7 2013 (32Gb), I requested a quote of a repair shop that wanted me to pay 200€ to repair it. That's about 70€ less than the price for a new one.
Instead I ordered a replacement screen from Ebay and did the repair myself which costed me about 71€. The screen was a genuine one, same type and all.
Now last week, I hadn't used the tablet for a while, I tried to turn it on but it refused. After booting it into recovery I noticed that my cache partition was corrupted. Wiping it didn't help, doing a factory reset didn't do it either.
After googling a bit I found forum threads saying the only thing you can do is having it repaired by Asus under warranty. Is this really so?
Although I didn't leave a scratch on the tablet, the two seals on the screws inside the tablet have been removed while I was repairing the screen.
So most probably I'm out of luck then? No JTAG or anything else I can try?
My tablet was running stock Android, non rooted, no unlocked bootloader, ADB was not enabled.
Best regards,
Jan
I suggest that you flash the factory image following the instructions in the sticky threads.
You flash it from you computer and I think there is a good chance that it will fix your tablet.
Yes, flashing the stock factory image is your best bet. I do believe that you must be unlocked, and that's very simple to do. Getting the Nexus drivers is more annoying that getting fastboot access.
Sent from my 831C using XDA Free mobile app
misteragony said:
Hello,
So a couple of months ago I cracked the screen of my Nexus 7 2013 (32Gb), I requested a quote of a repair shop that wanted me to pay 200€ to repair it. That's about 70€ less than the price for a new one.
Instead I ordered a replacement screen from Ebay and did the repair myself which costed me about 71€. The screen was a genuine one, same type and all.
Now last week, I hadn't used the tablet for a while, I tried to turn it on but it refused. After booting it into recovery I noticed that my cache partition was corrupted. Wiping it didn't help, doing a factory reset didn't do it either.
After googling a bit I found forum threads saying the only thing you can do is having it repaired by Asus under warranty. Is this really so?
Although I didn't leave a scratch on the tablet, the two seals on the screws inside the tablet have been removed while I was repairing the screen.
So most probably I'm out of luck then? No JTAG or anything else I can try?
My tablet was running stock Android, non rooted, no unlocked bootloader, ADB was not enabled.
Best regards,
Jan
Click to expand...
Click to collapse
Unlock your bootloader through ADB and than flash the factory image, make sure you flash the right one..
This LINK is a great guide that'll show you how to unlock the bootloader and flash a factory image through ADB (post 2).
Everything should get restored with a factory image flash, but if not you probably have a permanently bricked device because ASUS will most likely turn the device down if they notice any signs of the device being taken apart.
AarSyl said:
Yes, flashing the stock factory image is your best bet. I do believe that you must be unlocked, and that's very simple to do. Getting the Nexus drivers is more annoying that getting fastboot access.
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
All I had to do was download the Google Driver from SDK and install it. ADB was able to recognize my device without a problem.
Well, I first installed SDK when rooting my HTC Evo, and boy did I have a grand time getting the right drivers! [/sarcarsm] By the time I was using my next HTC phone, I was using Ubuntu, and it doesn't require any device specific drivers.
USB debugging
Well the thing is: USB debugging was not enabled before I couldn't boot my Nexus anymore. Since I can't boot it, I can't enable USB debugging if I'm not mistaken.
So I boot into the bootloader (volume down + powerbutton), then select recovery mode and press the powerbutton.
Next I press the powerbutton and volume up and I'm in the recovery mode.
There I can see the error messages about my cache partition being corrupted, wiping/formatting it there does not help.
I can put the tablet in 'adb sideload' mode, but I guess since the tablet is not in debugging mode that won't do much good?
Using the Nexus 7 toolkit I always see the message: waiting for ADB mode but it detects the device though (it lists a serial number as well).
I tried to boot the tablet by holding up and down volume and then the powerbutton (this is supposed to be 'fastmode' no?).
The screen of the tablet remains black/ not active, my PC (under Win7) detects a new device at this point but it fails to load a driver.
When I try this under Linux I see a 'qualcom device when I do 'lsusb', and under /dev I see: /dev/ttyUSB0 appear.
I tried "fastboot oem unlock" but that doesn't work.
Well I found this thread:
http://forum.xda-developers.com/showthread.php?t=2602638&page=3
Seems some people have had the same issue with not being able to mount/format the cache partition.
So my only option would be a RMA, but since I repaired the screen myself that's a no-go as well (the warranty seals/stickers on the two screws on the inside are gone).
A new Nexus 7 it is then I guess...
misteragony said:
Well I found this thread:
http://forum.xda-developers.com/showthread.php?t=2602638&page=3
Seems some people have had the same issue with not being able to mount/format the cache partition.
So my only option would be a RMA, but since I repaired the screen myself that's a no-go as well (the warranty seals/stickers on the two screws on the inside are gone).
A new Nexus 7 it is then I guess...
Click to expand...
Click to collapse
You flash a stock image in fastboot. You hold volume down + power to enter it.
I tried to unlock: I chose yes using the vol buttons and pressed the powerbutton.
At that point the screen freezes on my tablet, and in the command line it gets stuck at this:
Device detected in FASTBOOT MODE
Device Serial Number is: 0xxxxx
...
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
OK,
So a friend of mine asked me to help him fix his Nexus 7 2013 FLO (WiFi only).
According to him he hasn't even unlocked the bootloader (and the info displayed while in fastboot mode confirms this). Apparently what happened, a few months ago, he downloaded an OFFICIAL KitKat OTA, clicked OK to upgrade, and since then, the tablet will not get past the screen that says Google. I can get it into fastboot mode but cannot flash anything, and when I attempted to use The Nexus Root Toolkit by WugFresh to unlock the bootloader at the very least, I can get it to display the screen that says "please use the arrow key to navigate Yes or No. Unlocking your bootloader allows you to load a custom OS, but may void your warranty, etc. etc. etc."
I tried using CMD to erase the cache and userdata and after giving it upwards of 20 minutes, during which the window (in CMD) simply said "erasing cache" and never actually made any progress whatsoever...
Any idea what (if anything) can be done?
Sound off in the comments!
Thanks a million!
Stephen Spigelman
I can't help... but am in the same boat as of last night with the 5.0 update.
Were you able to unlock the bootloader? You did say that you were able to get to the screen to unlock it. If not, i dont think much of anything can be done.
Bricked
Virgin N7 2013... No hacking... Bootloader locked... started acting weird and I attempted a system restore. It now gets stuck at the Google screen. Fastboot gets stuck at erasing userdata. I have tried multiple USB cables on Win7, OSX, and Ubuntu. Help!!!
im wondering how this happens?, I already unlocked my bootloader just cause of this.. maybe the chip just dies?
When my 2013 was stuck at the Google screen, I RMAed and they had to replace the motherboard. Unfortunately, I think this is a hardware issue.
ariesgodofwar said:
When my 2013 was stuck at the Google screen, I RMAed and they had to replace the motherboard. Unfortunately, I think this is a hardware issue.
Click to expand...
Click to collapse
Too many of us with the exact same problem after trying to to flash Lollipop. Cant believe we re all having hardware problems at the same time.
tigerdim said:
Too many of us with the exact same problem after trying to to flash Lollipop. Cant believe we re all having hardware problems at the same time.
Click to expand...
Click to collapse
Mine did not occur after flashing any firmware, but the symptom was the same in that I could get into the bootloader, attempt to flash new system images, appear as if all would be well, and then on reboot would stick at the Google screen. Not sure if folks are seeing the same thing here, but when I tried to get into Recovery from the Bootloader menu, it would reboot as if going there, but still never make it past the Google screen. It happened within 18 hours of unboxing a remanufactured N7 G2. Asus advised on the packing slip that is was a LED (Indicator) Error (whatever that is), and they they subsequently had to replace the board to fix it.
I hope it is a software issue, but not sure to tell you how to go about correcting it if you cannot flash new images via ADB or the bootloader and get it to boot successfully.
When i boot to recovery i get the TWRP startup screen but stays stuck.
Bump
bump.. any ideas?
i have the same :/
kobi_shalom said:
i have the same :/
Click to expand...
Click to collapse
Its driving me nuts.
I have found though that if I try a "Erase Boot" or similar and pull the cable after a second or so I do get a "OK" instead of being stuck with "Erasing boot..." Seems to work for Boot, Cache etc..
The problem is that when I try OEM Unlock it needs to perform 5 different erases, so pulling the cable wont work for this. I just stay stuck on "Erasing userdata...r..."
tigerdim said:
Its driving me nuts.
I have found though that if I try a "Erase Boot" or similar and pull the cable after a second or so I do get a "OK" instead of being stuck with "Erasing boot..." Seems to work for Boot, Cache etc..
The problem is that when I try OEM Unlock it needs to perform 5 different erases, so pulling the cable wont work for this. I just stay stuck on "Erasing userdata...r..."
Click to expand...
Click to collapse
So you success?
NO success because I cannot unlock the bootloader.
Sorry if the thread is not in the right place and not fancy written, I don't use forums a lot..
So I've had that phone for about 3 years now. I've never rooted the device, never installed any custom roms, nothing. Only did a factory reset/wiped data couple of times.
One day I woke up (on 2nd of January), looked at my phone (it was charging whole night) and it was showing the "Google" logo. After that it switched to "colorful X", then it turns off, vibrates and all over again.
I was doing it until I took out the battery for a half an hour. Plugged it back in, turned on... Same thing was happening.
I've removed the battery again and plugged it back in. Pressed the power + vol up + vol down buttons in order to get into the bootloader. Got to the "recovery" and wiped the data/factory reset, and wiped the cache.
Restarted, didn't work.
Got mad here and decided to first time to attempt installing a rom. I've got to the google developer website where there are factory images. There were a couple of versions of the Galaxy Nexus. I didn't know which one to pick, so I've picked the first one (GSM with google wallet latest version). (I've already had Android SDK) so I've followed the instructions by using the "fastboot oem unlock"
then "flash-all". It failed. And the reason is when it rebooted, the bootloader locked again and the script couldn't continue installing/flashing.
So every time I unlock the bootloader and reboot, it locks it again.
I've decided to flash every img individually. By using this pattern:
fastboot oem unlock
fastboot flash bootloader bootloaderblabla.img
fastboot reboot-bootloader
fastboot flash...... and every single image including the radio, boot system, etc....
basically every time I flash and reboot, I unlock the bootloader.
That however didn't fix the problem, it was still remaining in the bootloop.
So I am not sure which version of the galaxy nexus I have, I've tried doing that will few versions of the factory images with no success.
So I came here, in a chance to get it fixed by some magic!
Please help?
Corrupted EMMC (internal memory chip).
Currently no solution to this, unfortunately.
Basically the firmware of the internal Memory Chip screwed up. The firmware on the memory thinks your data might be in danger and switches to read only mode (these firmwares are similar to SSDs for PCs, so thats a good thing in general). So if you unlocked your bootloader, you could retrieve your data.
This is however solveable by reflashing the chips firmware, but it's unshure if this even could be done while the chip is soldered onto the motherboard.
Check the latest pages of the CM12.1 thread, there was some discussion about this topic. If you find a good phone repair place they might have a JTAG flashbox and could reflash the EMMC.
Other soultion would be to replace the board.
Same thing happened to me and I changed my motherboard
Sent from my Galaxy Nexus using XDA Free mobile app
playitlouder said:
Corrupted EMMC (internal memory chip).
Currently no solution to this, unfortunately.
Basically the firmware of the internal Memory Chip screwed up. The firmware on the memory thinks your data might be in danger and switches to read only mode (these firmwares are similar to SSDs for PCs, so thats a good thing in general). So if you unlocked your bootloader, you could retrieve your data.
This is however solveable by reflashing the chips firmware, but it's unshure if this even could be done while the chip is soldered onto the motherboard.
Check the latest pages of the CM12.1 thread, there was some discussion about this topic. If you find a good phone repair place they might have a JTAG flashbox and could reflash the EMMC.
Other soultion would be to replace the board.
Click to expand...
Click to collapse
Ahh that's unfortunate, I think it's better to upgrade to a new phone.. It became laggy anyway.
Thanks!
Hello, please for help, I will not create new thead.
I have a problem, I'm tring to start phone and stucks on bootloop.
The solution should be start recovery, but my second problem is volume down doesn't work.
Is any chance to get to recovery throught ADB while phone is turned off?
Thanks.
Hi,after i wiped all data in twrp my nexus 5x stucked in bootloader mode(when you have to choice between recovery,power off,reboot etc.) and my bootloader is locked,before i had an android 7.0 rom, what can i do?
Please help me ,i've got any idea.
Can you still boot to twrp? You can sideload a custom Rom zip from you pc if you can.
Sent from my Nexus 9 using XDA-Developers mobile app
Any chance OEM Unlock was already enabled to run bootloader unlock command? Long shot I guess.
Otherwise use TWRP if you can get it.
If you ever Unlock you bootloader. Never lock it.
Sent from my Nexus 5X using Tapatalk
I can't go to twrp and i've got no chances to unlock oem bootloader.
I think i will try to flash the .tot file from pc.
Any idea?
I have the same problem now. Bootloader Locked, OEM and USB debugging not enabled in developers mode.
A few hours after android 7 update, phone booted itself and getting stuck at google dot animation.
I have tried adb sideloading stock image, it would finish successful but will get stuck at same google dot animation on reboot.
Please help. I'm out of ideas.
Have you found any solution?
vmchakka said:
Have you found any solution?
Click to expand...
Click to collapse
It appears to be a common issue, but I don't see any resolution other than having the phone replaced:
Yes, for some reason, a number of N5X devices are having an issue after recent updates where they subsequently will not boot and it is not possible to boot to Recovery Mode - in effect when they try the system continues trying to complete the system reboot that occurs at the end of the update. It would appear this happens because the update reboot didn't finish properly and did not clear a well defined in memory post box. I have raised this issue with the Community Manager for escalation to the development team as something is wrong (hardware or software still to be determined). In the meantime, if this occurs all that can be done is return the device for warranty replacement.
Click to expand...
Click to collapse
I just got this phone, too...
Things I have tried, so you don't have to try them too:
Flashing LGH790AT-00-V10f-NXS-XXX-OCT-03-2015-32G-MDA89E-US.tot
Flashing LGH791AT-00-V10f-NXS-XXX-OCT-03-2015-32G-MDA89E-US.tot
Flashing bullhead-mda89e-factory-29247942.tgz
Flashing bullhead-nrd90m-factory-d215f148.tgz
Sideloading bullhead-ota-mhc19q-8fe67a2b.zip
Sideloading bullhead-ota-mtc19t-4ea6522b.zip
Sideloading bullhead-ota-mtc20f-6303e5cd.zip
Sideloading bullhead-ota-nrd90m-fdb8250a.zip
And I tried them in all kinds of different orders, too, as well as changing USB drivers, cables, computers. I have been doing nothing but this since I got home from work yesterday. I didn't sleep. I have to go to work in a bit but I fear that there may not be a fix other than having the phone replaced.
Huskehn said:
It appears to be a common issue, but I don't see any resolution other than having the phone replaced:
I just got this phone, too...
Things I have tried, so you don't have to try them too:
Flashing LGH790AT-00-V10f-NXS-XXX-OCT-03-2015-32G-MDA89E-US.tot
Flashing LGH791AT-00-V10f-NXS-XXX-OCT-03-2015-32G-MDA89E-US.tot
Flashing bullhead-mda89e-factory-29247942.tgz
Flashing bullhead-nrd90m-factory-d215f148.tgz
Sideloading bullhead-ota-mhc19q-8fe67a2b.zip
Sideloading bullhead-ota-mtc19t-4ea6522b.zip
Sideloading bullhead-ota-mtc20f-6303e5cd.zip
Sideloading bullhead-ota-nrd90m-fdb8250a.zip
And I tried them in all kinds of different orders, too, as well as changing USB drivers, cables, computers. I have been doing nothing but this since I got home from work yesterday. I didn't sleep. I have to go to work in a bit but I fear that there may not be a fix other than having the phone replaced.
Click to expand...
Click to collapse
I have exactly same problem like you Huskehn.
So far I tried with all OTA's with a successful installation, yet wouldn't stop it get stuck at dot animation.
I also mailed back my seller for warranty replacement. Turn's out the seller disappeared from ebay and the office contact is unreachable. Talked to ebay helpline and the passed it on to paypal 180 days money back guarantee. Paypal asked me to chargeback from bank as the seller is out of reach. I have managed to talk to bank and get chargeback.
I am not sure if I want to risk buying same 5x now also it is constantly bugging me that I wasn't able to get a success fixing this device. Waiting for a Solution, If you can get yours to work, let me know. cheers
Hello. I am having some issues with Nexus 5X and was hoping someone could help possibly fix it, if it's even fixable.
I bought the phone from a used store for pretty cheap On march 5th this year.
Tuesday night i was surfing on google chrome app and all of a sudden the entire thing froze up on screen couldn't get it to do anything what so ever so i tried powering it down and rebooting it. Well i got it to power down but then it went into a constant boot loop where it just kept rebooting to the "Google" screen and then it wouldnt get any further. Eventually it ceased doing that after about 5-10 minutes and then i was unable to get the device to do anything, couldn't even get into the bootloader menu. Battery was at 55% when this all started and phone had been working very good prior. Last night i tried to get it to turn on again and this time i noticed a red flashing light on the bottom speaker. I have seen this one before on other nexus devices so i plugged it in and got the charging screen to come up, i let it charge full and then went to try and start it with no luck of getting it to do anything. Today i have managed to get it to simple Boot to the Google screen but it remains their for a few momments then shuts off and does nothing else, sometimes it goes into a constant repeat of that, i hear it's called a boot loop.
I am not sure what the issue is. What i wanna know is if it's an easy fix or not.
Thanks
**Update***
i was able to get it to finally go into to the bootloader screen, but have no clue what to do here, clicking restart just goes back to the same problems.
If you haven't already tried you could try doing a search for Nexus 5x BLOD or Nexus 5x bootloop of death, this may not be the issue but it will give you something to compare the symptoms your device has. There should also be plenty of info on any workarounds there are available to try and get your device back up and running.
Hope that helps
Ok will do thank you
Following thread https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199
installed 4Coreoreo fix, but am having issues getting to to flash boot
Command window stays stuck on < waiting for device > and the phone is doing nothing, just sitting in the Bootloader menu
says fastboot mode
secure boot enabled
device state locked
am i missing something? Am thinking the bootloader is locked
unable to do an oem unlock because i can't get it to boot into the os.
Yep your bootloader is locked and sounds like USB debugging needs to be enabled also if ADB is not finding your device using commands 'adb devices' or 'fastboot devices'.
Have another look through the BLOD threads as from what I remember you may need to cool the device right down to get it to boot to system fully to be able to enable OEM unlocking and USB debugging.
Keep searching, and good luck
Edit: I see you posted in the 4 core thread and got it to boot temporarily and OEM unlocked, just try again and enable usb debugging and you should be on to a winner.
junglism93 said:
Yep your bootloader is locked and sounds like USB debugging needs to be enabled also if ADB is not finding your device using commands 'adb devices' or 'fastboot devices'.
Have another look through the BLOD threads as from what I remember you may need to cool the device right down to get it to boot to system fully to be able to enable OEM unlocking and USB debugging.
Keep searching, and good luck
Edit: I see you posted in the 4 core thread and got it to boot temporarily and OEM unlocked, just try again and enable usb debugging and you should be on to a winner.
Click to expand...
Click to collapse
Ty for the reply, unfortunately even after enabling everything i still can't get fastboot to do anything but < waiting for device >
I think she done, sadly. My nexus 4 has lasted longer then this one, even that phone has its issues tho, like to randomally reboot itself sometimes, others the screen suddenly won't come on (lots of battery life) and it is hard to reboot but usually does. And it's 6 years old lol
Gibson295 said:
Ty for the reply, unfortunately even after enabling everything i still can't get fastboot to do anything but < waiting for device >
I think she done, sadly. My nexus 4 has lasted longer then this one, even that phone has its issues tho, like to randomally reboot itself sometimes, others the screen suddenly won't come on (lots of battery life) and it is hard to reboot but usually does. And it's 6 years old lol
Click to expand...
Click to collapse
No problem, other than trying a different usb port, cables or updating your ADB and fastboot if you haven't already it sounds like it's the end of the road for your 5x.
Leave it in a cupboard for a few days and give it a go another time, you never know. I've still got my Nexus 4, new battery time for mine but it still runs like a charm lol.