[Q] What to double check before confirming hardware issues? - Nexus 7 Q&A, Help & Troubleshooting

Hey guys,
I recently went to power on my Nexus 7 (2013) after a weekend of having it off, and it got stuck on the white Google start up screen with no further responses. Holding power the devices still turns off, and I am able to get into Bootloader and Recovery. From bootloader "start" just sends it back to the Google start up screen. I'm able to enter Recovery but the Android logo with the red warning triangle doesn't have the No Command script below it, Power and Vol. Up gets me into the Recovery menu. Entering recovery I get errors of : Can't open, failed to mount, can't mount etc which continues as I try to clear the cache, and wide the partition (I'd post pictures but I can't as a new poster). Moving on I tried some of the guides to flashing a new factory image with fastboot or Adb. Since I don't have normal access to the device I'm sure sure is USB debugging was enabled or not, but in bootloader that shouldn't matter correct? Anyways here is where I hit my snag, my device is still in LOCKED bootloader, and the fastboot oem unlock command gets me to the unlock bootloader screen, but after I select and confirm the option the device freezes and no progress is made. From that screen I am still able to turn it off by holding the power button down, so I'm somewhat confused about it becoming unresponsive to the unlock bootloader command. All of the other fastboot commands like fastboot erase cache come back with "Failed: Too many Links". From my knowledge I've checked through everything I can do software wise, and I was curious if you guys had any input before attributing this all to a hardware failure? I've got some experience rooting and flashing custom ROMS on my phone so I have somewhat of an understand of all this but its by no means vast. Thanks for the help, and I tried to provide you with as much info as possible but I'll attempt to answer additional questions to the best of my ability.
Stock Nexus 7 2013
Version : KTU84P
Bootloader: Locked, FLO-04.02

scbikep2 said:
Hey guys,
I recently went to power on my Nexus 7 (2013) after a weekend of having it off, and it got stuck on the white Google start up screen with no further responses. Holding power the devices still turns off, and I am able to get into Bootloader and Recovery. From bootloader "start" just sends it back to the Google start up screen. I'm able to enter Recovery but the Android logo with the red warning triangle doesn't have the No Command script below it, Power and Vol. Up gets me into the Recovery menu. Entering recovery I get errors of : Can't open, failed to mount, can't mount etc which continues as I try to clear the cache, and wide the partition (I'd post pictures but I can't as a new poster). Moving on I tried some of the guides to flashing a new factory image with fastboot or Adb. Since I don't have normal access to the device I'm sure sure is USB debugging was enabled or not, but in bootloader that shouldn't matter correct? Anyways here is where I hit my snag, my device is still in LOCKED bootloader, and the fastboot oem unlock command gets me to the unlock bootloader screen, but after I select and confirm the option the device freezes and no progress is made. From that screen I am still able to turn it off by holding the power button down, so I'm somewhat confused about it becoming unresponsive to the unlock bootloader command. All of the other fastboot commands like fastboot erase cache come back with "Failed: Too many Links". From my knowledge I've checked through everything I can do software wise, and I was curious if you guys had any input before attributing this all to a hardware failure? I've got some experience rooting and flashing custom ROMS on my phone so I have somewhat of an understand of all this but its by no means vast. Thanks for the help, and I tried to provide you with as much info as possible but I'll attempt to answer additional questions to the best of my ability.
Stock Nexus 7 2013
Version : KTU84P
Bootloader: Locked, FLO-04.02
Click to expand...
Click to collapse
A clear explanation of the problem alone with everything that you have tried will do for reporting hardware/software issues and also help others help you.
Sent from my Nexus 5 using Tapatalk

Related

[Q] Somewhat Broken Beta Streak

So I have had this US beta streak since around January, the one that says 'Dell Confidential' at boot up, but it's never really worked correctly. I purchased it from a person that I know that got it through some sort of beta testing; the details weren't provided and I didn't press him for them. Anyways, I am currently trying to get the clockwork recovery flashed and able to be booted into, although the streak is giving me every possible problem I can imagine. I'll try to provide as much background info as I possibly can.
Firmware: 1.5
Baseband Version AUS_090716_01_BOSS_EVT2_3135
Kernel Version 2.6.27
Build Number QTC_3135
OEM Version: AustinBuild_090724_03_boss_evt2_3135_FixTouchSuspend
Under About Phone > Status
IMEI 011954000020995
IMEI SV 00
Service Tag FF8R6K1 (which dell.com cannot find)
The Problems:
When I try to get into bootloader to get into fastboot, by holding the camera button down while hitting the power button, rather than going into the screen that is shown in all of the different tutorial threads, I instead go into some sort of a diagnostic menu that doesn't have an option for fastboot, as much as I have seen. There is a picture attached below.
I (think) that I can get the phone recognized by adb, although I am not totally positive. When in cmd in windows, and I type adb devices, instead of getting the proper serial number of my devices, it shows instead 0123456789ABCDE (I may not have that exact, but it does start at 0 and ends in hex at E or F, I can't remember right now and don't have it connected at the moment.)
There was one time where I was able to flash recovery.clockwork.img to where it said that it successfully flashed the img, but when I go to try and boot into recovery by holding both volume up and down at the same time, and then hitting power, the phone just hangs at a blank, black screen. It will stay there for 30 minutes and not do a thing, I can't see it via adb or fastboot.
So I then gave recovery.alt.img a shot, was able to successfully flash that, or so it told me that it was successful, but still the same problem: just a black screen.
The reason that I think that it actually was working was that after flashing the recovery image both times, I sent the command adb reboot recovery, and the phone reboots, but not into recovery, just into android. adb reboot-bootloader doesn't work at all and returns an error or nothing, I can't remember.
I then focused my attention on trying to get fastboot to work, assuming that adb was not working at all. This is where fastboot gets strange. The only way for me to get the command 'fastboot devices' to show anything at all is by holding the volume down button prior and then hitting the power button to start it. This puts the phone into essentially a 'soft brick', which my friend calls 'safe mode', where it gets totally stuck at the 'Dell Confidential' screen and will not progress past it no matter what.
So, once I am in 'safe mode', I am able to then issue a 'fastboot devices' command, which ... partially works? I hope that my totally unsure tone of voice was able to be conveyed through that message, because the info returned once that command is sent is totally confusing to me. Unlike before, where I feel as though the Streak is just lying to me by saying 0123...DEF for the device ID, for fastboot devices it just gives me a question mark .. yes, simply a ?
The weird thing is that it will follow commands. I was able to flash recovery.clockwork.img to the streak, it gave me a read out that said successful, and I got very excited. And then I pulled the battery, put it back in, held both the volume buttons, and .... the same result, the black screen. So, not allowing myself to be deterred, I got right back into fastboot, or at least my quasi working version of fastboot which may not be working at all, and flashed recovery.alt.img, which turned around and told me that it was successful as well. This time, not allowing myself to get excited, I pulled the battery and, with both volume buttons held down, hit power to try to get into recovery.
Again, I was let down and found only a blank screen. At this point, I have no idea what else to try. With the bootloader not being where it's suppose to be, not really being able to get into fastboot or adb (I think), I turn to xda to try and find some answers. Does anyone have a suggestion as to what I am doing wrong or might be missing. I am hoping that it is something that is really obvious that I feel very stupid, like I'm hitting the wrong set of volume buttons, but ... I don't think it's that easy.
Again, I feel as though the phone was getting the commands from fastboot because I sent fastboot reboot recovery, and the phone rebooted, just not into recovery but android. Same thing for bootloader, it just didn't work at all
Also, as for android 1.5 itself, almost nothing works. This appears to be running a very early edition of android where most apps just end up with: Sorry! No applicatons can perform this action, so the One touch root is kind of out of the question.
I was able to do the dialer unlock method to get EMList, but the similarities end there. I don't have the Unknown sources option or anything else after leaving dialer.
Any and all suggestions are appreciated and will be accepted and followed (within reason). I'm just at the point where I'm hoping that it's not totally broken and that with determination and hard work and some critical thinking I (we) will be able to get it working again. Hopefully it isn't a paperweight.
Thanks,
Thursday

[Q] Stuck in fastboot, cannot use controls, already flashed everything, any ideas?

So to answer the first question, yes I followed the stickied guide up top, and yes, it successfully flashed the bootloader, wiped all data, and flashed stock ROM all to success. It appears my case is unique. I was told that it could be the battery connection, so I've done no fewer than half a dozen times of taking the back off, resetting the battery connection, and closing back up. It does not appear to be the battery.
I am stuck on the fastboot screen, the one where the android is lying down and blue squares project from an body. It shows me the controls I can make with the volume switches and the selection choice of 'Start'... but I cannot do anything. Before I went to flash I could move through the selection with Vol Up ONLY, but now I cannot even do that. Here's all the mode says:
Code:
FASTBOOT MODE
product name - grouper
variant - grouper
hw version - er3
bootloader version - 4.23
baseband version - n/a
serial number - ###############
signing - not defined yet
LOCK STATE - UNLOCKED
I've pretty spent the past twenty four hours on google searching through all the threads I've seen. They are either all dead, or most of them found the sticky fixed their problem. Has anyone heard of it coming to this?! All I can do is access fastbook VIA a DOS prompt and do fastboot commands, and if I disconnect the tablet from my PC, it'll remain in this mode with the screen on until the battery dies. Charging appears to charge the tablet, but again, no controls work. And yes, the buttons were set properly when I closed my tablet.
Anyone?
1) what is it exactly that your trying to do?
2) can u boot into the OS?
3) your recovery may be corrupt re-flash the recovery via fastboot
...Awesome... said:
1) what is it exactly that your trying to do?
2) can u boot into the OS?
3) your recovery may be corrupt re-flash the recovery via fastboot
Click to expand...
Click to collapse
I'm just trying to boot up! I don't know what happened, but I haven't been able to use it for school all week!
I cannot boot into the OS. Any time I plug this device in it sends me to the fastboot screen with no controls.
OK I just flashed CWMR 6.0.4.3 and it did not fix the problem.
Any other ideas?
I just repeated all the steps again to see if any of them failed before, they have not worked. So recap:
Stuck in fastboot mode
Android will not boot
Loose battery connection is not the problem
I am able to access fastboot on my computer
I have followed everything from the sticky (wipe everything, flash bootloader, flash image)
I have flashed a new recovery
I am still stuck in fastboot
I cannot control options in fastboot with the volume and power buttons
I can only access fastboot by charging my tablet
The only way the tablet will power down is when it completely depletes it's battery
As far as I can tell, nothing was wrong with the tablet when it was functioning
This happened when I went to charge my tablet, presumably when the battery ran flat running android
If I charge too long the tablet gets fairly hot.
That's about all the information I can provide. Is there anything else I can try? Please, I need a tablet for school and I cannot afford a new one!

Nexus 6P black screen will not boot into OS

Okay, so there is no screen protector or anything. Not rooted or unlocked or tampered in any way. I've had the phone for 26 hours and then the following happened:
EDIT: YouTube video added https://youtu.be/yAVmTz7MQbQ
I pulled the phone out of my pocket to unlock it. I see the lock screen and put in my pin (yes, I see the actual screen and stuff on it. Let me make that clear.) after I enter my pin successfully the screen locks itself. I contacted Google support and they said to factory reset it. I did the full factory data reset in the recovery mode (again, the screen works. I can see everything to do a FDR and I can see the boot animation) and it starts to boot up. Once I see the "welcome" screen it instantly locks itself. I can hear the audible "latch" locking sound that it makes when you press the power button. I know the buttons are not malfunctioning because they work perfectly fine in bootloader / recovery mode to scroll up and down and select things. I've tried multiple things but nothing seems to work. The problem here is that I want to try and do a factory image but my computer will NOT recognize my Nexus 6P when in recovery mode / bootloader mode. I have all the drivers installed but since I can't access the OS and enable OEM UNLOCKING there is no way to factory flash a factory image is there? Can someone maybe help point me in the right direction? Again, I can NOT access the OS at all whatsoever.
You just need the bootloader unlocked to flash a factory image, you can't enable that from settings o.0 so I guess your down to RMA now.
The command is now "fastboot flashing unlock"
Hey downloading a tool kit from this devices tools sections. Install the latest adb / fastboot binarys and try again
Good luck !
hutzdani said:
You just need the bootloader unlocked to flash a factory image, you can't enable that from settings o.0 so I guess your down to RMA now.
The command is now "fastboot flashing unlock"
Hey downloading a tool kit from this devices tools sections. Install the latest adb / fastboot binarys and try again
Good luck !
Click to expand...
Click to collapse
Hi Hutzdani, when I try to run the command it says "remote: oem unlock is not allowed". I have the RMA in progress but 3-5 days with no phone is going to become grueling unfortunately and I want to try everything I can. :S
xandr00 said:
Hi Hutzdani, when I try to run the command it says "remote: oem unlock is not allowed". I have the RMA in progress but 3-5 days with no phone is going to become grueling unfortunately and I want to try everything I can. :S
Click to expand...
Click to collapse
Can you run fastboot format cache and format user data? Then will anything happen ?
Sounds like you need to edit the partition that holds the data change for allow OEM unlock - there's a few threads about this on XDA for the N9 and N6 as far as I can remember.
It would seem the ability to flash a fresh system.img would solve this

help! need to factory reset and screen is not responsive

I shattered the screen of my 2015 X pure.
I am sending it back to Motorola for screen replacement.
I want to factory reset, but the screen is not responsive. I can see the screen.. well the lock screen, as touching anywhere on the screen does nothing.
i have tried to hold power button 10 seconds to turn off... from there i can hold power and down volume until enter bootloader mode.. or whatever that is.... I cannot see anyway to factory reset from there either!!
It is bad enough that i cannot get the files off the phone because, thanks to Marshmellow, you can no longer just hook up to computer and have it open a folder.. it goes in in a different mode now, and you have to change it on hte phone.... which i can't do... lucky me.. .isn't progress great?
Anyway, if someone can help me, it'd be appreciated.
thanks.
TWRP custom recovery enables adb and mtp without any touches, so you could recover your files via usb if you have TWRP. Was your bootloader unlocked? It has to be to run TWRP, and you have to enable a setting with the touchscreen to allow bootloader unlocking. If your bootloader is unlocked and you have, or are willing to install TWRP then I think you can get at your files. If your bootloader is locked I think your stuck.
Fastboot will work to factory reset with no touchscreen if you must. While in that bootloader mode plug it into a PC and use the following commands:
Code:
fastboot erase userdata
fastboot erase cache
Pretty much same thing as a factory reset, no touchscreen required. Now those lenovo techs won't be able to check out all your funny cat pictures.
Don't have a working fastboot/adb PC? Check out Heisenberg's guide for how to set that up.

Phone stuck on Bootloader [soft brick]

Hi, just bought a phone for my son secondhand, it's going to be sold again if I can't fix this! The phone was sold cheap as it had software issues (of course) so I figured I could fix these and get it going (install custom recovery, ROM etc). I'm slightly stumped at the moment, so maybe you can help me.
The phone's defaulting to the bootloader screen, lots of info on this but the key thing I noticed was that it says 'the device is locked status code: 2'.
Clicking 'start' takes me a 'warning unlocked bootloader screen' then it runs through the 'hello moto' startup screen and back to bootloader
Clicking 'recovery' - there is definitely no working recovery on it, I just a get the dead robot with 'no command' underneath.
Clicking 'Factory Mode' allows me so far through the startup (after the bootloader unlocked warning), and you can get so far through setting it up, but because the battery is so low (it's permanently on with the bootloader when plugged in) it never seems to charge up enough, and either way the screen freezes at or around the final setup steps and then it reverts back to bootloader. I thought if I got into developer options and security, I could enable the USB debugging, OEM unlock etc, but no go there.
I've installed Motorola USB drivers but it doesn't seem to be registering on the PC (Windows 10).
There is some suggestion on other forums (less reputable!) that the locked status code may mean the bootloader has been relocked, but this seems contrary to what the phone is telling me.
Any ideas welcome, thanks - it's a lovely phone, just not much use at the moment.
GitManMatt said:
Hi, just bought a phone for my son secondhand, it's going to be sold again if I can't fix this! The phone was sold cheap as it had software issues (of course) so I figured I could fix these and get it going (install custom recovery, ROM etc). I'm slightly stumped at the moment, so maybe you can help me.
The phone's defaulting to the bootloader screen, lots of info on this but the key thing I noticed was that it says 'the device is locked status code: 2'.
Clicking 'start' takes me a 'warning unlocked bootloader screen' then it runs through the 'hello moto' startup screen and back to bootloader
Clicking 'recovery' - there is definitely no working recovery on it, I just a get the dead robot with 'no command' underneath.
Clicking 'Factory Mode' allows me so far through the startup (after the bootloader unlocked warning), and you can get so far through setting it up, but because the battery is so low (it's permanently on with the bootloader when plugged in) it never seems to charge up enough, and either way the screen freezes at or around the final setup steps and then it reverts back to bootloader. I thought if I got into developer options and security, I could enable the USB debugging, OEM unlock etc, but no go there.
I've installed Motorola USB drivers but it doesn't seem to be registering on the PC (Windows 10).
There is some suggestion on other forums (less reputable!) that the locked status code may mean the bootloader has been relocked, but this seems contrary to what the phone is telling me.
Any ideas welcome, thanks - it's a lovely phone, just not much use at the moment.
Click to expand...
Click to collapse
OK, some progress, I have now unlocked the bootloader, so have the UNLOCKED Status Code:3 which is good, unfortunately has not yet helped with my issues. I can't use ADB, but MFastboot tool is working, so can run commands from that (hence me getting to that stage). Tried reinstalling firmware, may try and do this again now bootloader unlocked....
slightly further along...
GitManMatt said:
OK, some progress, I have now unlocked the bootloader, so have the UNLOCKED Status Code:3 which is good, unfortunately has not yet helped with my issues. I can't use ADB, but MFastboot tool is working, so can run commands from that (hence me getting to that stage). Tried reinstalling firmware, may try and do this again now bootloader unlocked....
Click to expand...
Click to collapse
I have now managed to flash stock firmwares using Mfastboot tool, but hasn't unfortunately fixed the boot up issues. However, I have now worked out how to access the recovery, by reading other posts on different Motorola phones:
boot to bootloader, power+vol down
in bootloader select recovery using the volume up/down buttons, press power button to select
phone boots into 'recovery,' showing the dead android with no command
at this point hold down the power and volume up, then release volume up but keep power held down
phones boots, by magic, into android recovery, where you can factory reset, wipe cache adb sideload and install from SD card
I now need to try and get a flashable recovery to sideload, as the attempts to flash it don't work for me. The OS I seem to be on is reteu 7.1.1, so I will try and go for a lower version, and see if that allows me to flash the custom recovery I desperately need.
But....things are improving slowly....:laugh:
GitManMatt said:
I have now managed to flash stock firmwares using Mfastboot tool, but hasn't unfortunately fixed the boot up issues. However, I have now worked out how to access the recovery, by reading other posts on different Motorola phones:
boot to bootloader, power+vol down
in bootloader select recovery using the volume up/down buttons, press power button to select
phone boots into 'recovery,' showing the dead android with no command
at this point hold down the power and volume up, then release volume up but keep power held down
phones boots, by magic, into android recovery, where you can factory reset, wipe cache adb sideload and install from SD card
I now need to try and get a flashable recovery to sideload, as the attempts to flash it don't work for me. The OS I seem to be on is reteu 7.1.1, so I will try and go for a lower version, and see if that allows me to flash the custom recovery I desperately need.
But....things are improving slowly....:laugh:
Click to expand...
Click to collapse
Never try to downgrade using stock firmware.
tyamamoto said:
Never try to downgrade using stock firmware.
Click to expand...
Click to collapse
OK thanks, I read that, but didn't realise it was a thing....should I be able to sideload a custom rom using ADB?

Categories

Resources