Can I salvage my device? - Nexus 5X Q&A, Help & Troubleshooting

My rooted+bootloader unlocked LG Nexus 5x was not recognised by adb or fastboot in either Arch Linux or Windows (the latter with the proper drivers installed and the former with udev rules properly established). The device will also not show up in Windows' device manager or lsusb and the like in Arch. This was not too much of a problem until I accidentally deleted my SystemUI app from a new ROM.
The moment I realised what I had done I tried to reinstall from TitaniumBackup's restore function. That failed. I placed another copy of the apk within a folder in priv-app, assuming that I'd have no problems. I was very wrong.
On the next boot my SystemUI began crashing. My attempt to boot into TWRP required a password, which has never been the case before. I cancelled and tried to allow TWRP write access to /system. I then wiped data, cache, and dalvik during a factory reset. No luck.
Now it does not appear that my internal storage or system partitions are mounting properly, and I can't access the backup files on the sdcard. I can't sideload anything or adb push.
On a scale from one to screwed, how bad is my situation?

Not. If you have tried EVERYTHING else, download WugFresh tool kit, get into bootloader connect the USB and click the box under "unroot and return to stock" that states "device in bootloop" ,click on "unroot and return to stock" and follow the instructions. Make sure you manually select which device you are using first tho.
Edit: the tool kit has the option to install the ADB drivers, do that first (just in case). shouldnt have a problem pushing to ADB if you only messed with system files.

Boot up a live version of Linux Mint. You don't have to fart around with udev rules and adb and fastboot are packaged up and in the repos. You will have a functioning system in no time.
Sent from my SM-G930V using Tapatalk

Hehe, I was using a third party cable. Jiggled it around a bit and "adb devices" eventually returned the device's information. I just had to hold down the cable and I was able to start flashing. I'll buy a good cable soon (or wait and buy a laptop with Type C as I've been planning so that I can use the cable that came with the device).

PiArc said:
Hehe, I was using a third party cable. Jiggled it around a bit and "adb devices" eventually returned the device's information. I just had to hold down the cable and I was able to start flashing. I'll buy a good cable soon (or wait and buy a laptop with Type C as I've been planning so that I can use the cable that came with the device).
Click to expand...
Click to collapse
Glad you got it working. Test each side of the cables. Mine work better on one side than the other. The one side needs to be held in like you described but simply flipping the cable around it has a sold connection.

Related

"usb device not recognised"??

long story short, i was manually going into fastboot for root through adb and right after i said adb reboot "buh bing"! now it says whats stated in the title i have no adb or fastboot access im willing to take the back off but i cant find that thread and i dont have access or the materials for a factory cable, so what are my choices???
Kole_Ackerson said:
long story short, i was manually going into fastboot for root through adb and right after i said adb reboot "buh bing"! now it says whats stated in the title i have no adb or fastboot access im willing to take the back off but i cant find that thread and i dont have access or the materials for a factory cable, so what are my choices???
Click to expand...
Click to collapse
pm me later I have some solutions most of it is likely your drivers and are you perhaps using a 3.0 usb port please only use 2.0 . a live usb with linux can sort out your driver issues. I can help you work out that part
Thank you for your response but I fixed it. Found out my USB cable was wonky you'd barely touch it and it would disconnect and reconnect. So I ordered a new one and the USB pin short trick while holding my wonky USB cable in a certain place,
Sent from my Amazon Kindle Fire using xda app-developers app
just to let you know the shorting trick is not required to complete this task in fact its completely unnecessary simply power off your device while connect and windows will restore the drivers to thier correct form if everything goes well

[Q] Nexus 7 won't boot, need to recover data...HELP!!!!

Ok, so, this is a two part question.
I've got a 32GB Nexus 7, and I'm having some issues with it. This tablet is completely stock. I haven't rooted it, I haven't unlocked the bootloader, installed a custom ROM or anything. All I've done with it was install OTA updates from Google, download some apps/games, and take some pictures.
About two days after I bought the thing and set it up, I got an error that said "System UIDs inconsistent" or something to that effect. I'd never seen it before, but a Google search revealed that the easiest way to fix it was to do a wipe/factory reset, so I did.
Fast forward to a couple of days ago...I'm from Canada, and while driving down to the States, I was bored, so I took out my shiny new Nexus 7, and turned it on. It was stuck at the 'X' screen, and wouldn't boot. I was frustrated, but because I was still in Canada, I was able to run a search on my phone. Factory reset. Ugh. So I did...once it finished, I used my data plan to download a few essential apps, and it was good to go.
Fast forward to today. I'm going to be returning home later today, but yesterday I decided to try out the GPS functions, because the TomTom GPS I've got isn't the greatest, and I much prefer Google Maps Navigation. A friend with a Nexus 4 was able to use the wifi where we were staying to get directions to various places, and then he'd shut off the wifi, and his N4 would still maintain the GPS signal and navigate him for the whole trip, even with no data, and for a lot of the time, no cell signal at all. I wanted to try the same with my N7, not knowing that many users are experiencing issues with the GPS.
So yesterday I was trying to use the Sygic GPS app, which apparently does offline navigation. And I guess because the N7 location capabilities are iffy right now, it wasn't working. So I, in my infinite wisdom, decided to reboot the tablet, thinking that would fix the GPS. This was after I had taken LOTS and LOTS of photos during the trip.
The tablet reboots, and gets stuck on the 'X' screen again. I was ready to bash my head through the car window at that point.
Long story short, the tablet doesn't boot. I'm a software developer for a living, so I had (keyword.. HAD) USB debugging turned on, but since I had to wipe the thing at the start of the trip, I never re-enabled USB debugging, but I don't recall if you actually have to or not...I'm assuming that it loses that setting when you wipe it.
So USB debugging, I can only assume, is not enabled. I can boot into recovery mode, but all I get is the Android icon with a red exclamation mark, and a message that says "No command". I know that you can press the power and volume up buttons to get the menu in recovery mode.
But what I was hoping to be able to do was use ADB to pull a full backup of the device, to at least salvage all the photos I took. I don't care about the apps, I can always reinstall those. I did not have a chance to set up an auto-sync (either Dropbox or Google+) of the photos, unfortunately.
I downloaded the Google USB drivers, and the Android Platform Tools (the wifi at this hotel sucks, so I didn't get the full SDK), and I'm using my brother's laptop, which is running Windows 8. I can get the tablet into recovery mode, and the laptop recognizes the tablet when I try to power it up, or when its in the fastboot menu.
But I can't get ADB to recognize the Nexus at all, it doesn't appear in adb devices whatsoever. And right now, the laptop doesn't seem to react when I plug the tablet in after booting into recovery mode. I also tried plugging in the USB cord, then booting into recovery mode, same thing.
I can only get ADB to recognize the tablet if I hit the "Apply update from ADB" option in the recovery menu. It shows up in adb devices, but it says "sideload" next to it, and if I try any other adb command (shell, backup, pull, etc) it just says "error: closed". I tried adb kill-server and adb start-server, then adb backup again, no dice.
I stayed up till 1AM last night fiddling with this thing, and I have a feeling that I might need to wait till I get home, or maybe when I get to work, as I believe I've got the full Android SDK installed there.
So, my two questions on this are...
1) What the hell am I doing wrong? Is there any way for me to recover the photos from the device? I'm sure that adb backup will work, if I could just get this damn laptop to recognize the device.
I've done quite a few Google searches already, and found a few results. I can't post links apparently, but there's a certain thread posted on StackExchange about how to perform a full backup of non-rooted Android devices. While it was helpful, I can't do that backup because this laptop won't recognize the tablet.
But I'm just spinning my wheels here, and could really use some help. Are there different drivers I should be using? Is there a way to run ADB from the bootloader rather than recovery mode? How do I get Device Manager (Windows) to even recognize the tablet when its in recovery mode?
2) So this will be the third time (after I get these photos recovered, hopefully) that I'll be doing a wipe on this tablet. I've got a two year replacement warranty on it. Should I be taking it back for a new one? Would it be a bad app thats causing these issues? Most of the apps I have are "official" ones anyway, aside from a couple of games, but they're all popular ones. After the wipe, should I re-flash it with Google's latest stock ROM?
Thanks in advance!!
Woops, I just realized you haven't unlocked the tablet. Sorry, everything I wrote below won't work because the bootloader won't let you boot into an unsigned recovery image and if you try to unlock now the process will force a wipe. The only thing I can suggest is try booting into safe mode. Sometimes you can get the MTP device to show up even if the system isn't totally started. There is a link in the stuff below for that. I guess you could also try the adb backup again, now knowing what is going on with adb and recovery.
[Info] Guide to entering safe mode, bootloader, stock recovery
[GUIDE] Full Phone Backup without Unlock or Root
====
Almost TLDR.
Anyway, I don't know why you get the System UIDs inconsistent. Probably some corruption somewhere, but who knows the cause. There are sporadic reports of it on this tablet and actually other brand tablets as well, but it doesn't seem like the more widespread issues. Personally I think it would be worth it to exchange it to see if that helps.
Regarding your ADB issues, there are multiple:
First, in stock recovery, adb isn't running until you select sideload, that is why you don't see it under adb devices.
Second, the adb in stock recovery (ie adb sideload option) is restricted in its functions. It basically only supports sideloading.
You don't seem to have this issue, but the regular Google USB drivers won't work for adb under recovery because the USB IDs change and the device usually shows up as an unknown device "Flo". If you are afflicted by that issue, see this post for drivers that will work under both android and recovery:
[FIX] MTP with USB debugging / ADB within Recovery (windows/nexus7)
Hope is not lost though, you can boot into TWRP recovery, which does support a full adb and you should be able to "adb pull" all your files off the sdcard. Just don't do any wipes or formats by accident until you get the files off.
Download TWRP from here: http://techerrata.com/browse/twrp2/flo
Place the file in the same directory as your adb/fastboot executables
Boot into bootloader using Power+VolDown, see this post if you have trouble
[Info] Guide to entering safe mode, bootloader, stock recovery
connect the USB cable to a USB2.0 port on your computer
you should see some indication that the android bootloader device got recognized
in your adb directory enter (I renamed the downloaded TWRP image for convenience)
fastboot boot twrp.img​after maybe 5 seconds of seemingly nothing going on, TWRP will start up
your PC may ask you for drivers, if so, see the link above where I provided drivers
after that you should have full adb available to pull your files
After you are sure you have everything pulled off, try the factory image restore from google.
1. This may or may not help you but have you manually installed the adb drivers on the laptop? If not, check here. It also includes instructions on how to disable driver signature enforcement on your brother's Window 8 laptop. Now, I'm not sure if he updated that driver for flo, or if he even has to, but if that driver doesn't work, download the sdk. A driver comes in it that'll work. I know it'll be painful to wait for the whole thing to download, but it might be your best option. It's in ...\sdk\extras\google\usb_driver\
2. It's up to you whether to return it or not. I, personally, hate dealing with the return process, even if it's in-store, so I usually make-do until a fix is found, or in this situation with a Nexus device, I would try to troubleshoot it. I, too am a software developer by profession (mainly .NET; I develop on Android as kind of a hobby) and I enjoy working out issues myself. But that's just my opinion, it's completely up to you. I doubt it's any apps, I doubt it's any games. I would probably try installing factory images back onto the device and see if that helps.
Thanks for the replies, guys.
I just got home late last night, and while I was too exhausted yesterday to do anything with it, I brought the Nexus 7 with me to work today, so I'll see what I can do with it here. I thought I had the Android SDK installed on my work computer, but I don't. Fortunately, now that I'm back from holidays, I have access to fast internet connections.
My regular desktop at home and my work computer are both running Windows 7, so I shouldn't run into the driver enforcement issues that people experience with Windows 8.
I tried booting it into safe mode once, but I didn't have the USB connected. Even with safe mode, it was just frozen at the 'X' screen, but I'll try it again with the USB connected.
I'm a bit confused though. The tablet hasn't been unlocked, sfhub, so like you said, I won't be able to boot into TWRP. So aside from booting into safe mode, there's nothing I can do to get the adb pull or adb backup commands to work?
If someone can clear that up for me, that'd be appreciated. I'm going to try safe mode now, but as far as I'm aware, all I can do is boot the tablet into recovery mode. So is there a driver that would allow me to use the shell, pull, or backup commands from either stock recovery or the bootloader menu?
Update...
So, safe mode doesn't work as far as booting the device goes; it just hangs at the 'X' screen.
However, something named "Nexus 7" shows up in Device Manager, and when I told it to look for a driver in the folder containing the USB drivers from Google, it installed a driver, and called it "MTP USB Device".
Unfortunately, the device doesn't show up under My Computer (damn it, wishful thinking!!), and then after about 15 seconds, a yellow exclamation mark shows up on the device icon in Device Manager, and it generates an error saying "This device cannot start. (Code 10)".
Does this at least seem like progress?
Stealth22 said:
Update...
So, safe mode doesn't work as far as booting the device goes; it just hangs at the 'X' screen.
However, something named "Nexus 7" shows up in Device Manager, and when I told it to look for a driver in the folder containing the USB drivers from Google, it installed a driver, and called it "MTP USB Device".
Unfortunately, the device doesn't show up under My Computer (damn it, wishful thinking!!), and then after about 15 seconds, a yellow exclamation mark shows up on the device icon in Device Manager, and it generates an error saying "This device cannot start. (Code 10)".
Does this at least seem like progress?
Click to expand...
Click to collapse
It does look like progress. Try booting your phone up into recovery mode, connecting it to the computer, then installing those drivers for the phone again. Mine comes up as "Google Galaxy Nexus ADB Interface" in recovery after installing the drivers, but I think if you can get it to come up as "MTP USB Device", you might be able to use adb commands. I'm not 100% sure, but if you can get it back to recognized as an MTP device again, try quickly switching over to the command prompt and trying the "adb devices" command and see if it shows up. Of course, if you install the drivers and it comes up as an ADB interface device, you should just be able to run adb commands and not need to see if MTP will work.
The computer doesn't recognize the device at all when I start Recovery Mode. On the tablet, all I see is an Android laying down with a red exclamation mark saying "No command."
The only way I can get it to even pop up in Device Manager is if I hit "Apply update from ADB", which enables the adb sideload command, but NOTHING ELSE. If I try to run ANY other ADB command, I get "error: closed".
Remember, the device is COMPLETELY stock, not rooted, and the bootloader is locked. I had to do a wipe the last time this happened, driving down to the States at the beginning of my vacation. So even though I had USB debugging enabled before, I never re-enabled it after doing the wipe. Then I took a bunch of photos, and after rebooting the device for the first time after that one wipe, it again no longer boots up.
I would love to fix the damn thing by just doing another factory reset. But I don't want to do that, because I need to recover the photos that I've taken this past weekend.
I might call Google support and see if they know of any solution.
Stealth22 said:
I'm a bit confused though. The tablet hasn't been unlocked, sfhub, so like you said, I won't be able to boot into TWRP. So aside from booting into safe mode, there's nothing I can do to get the adb pull or adb backup commands to work?
If someone can clear that up for me, that'd be appreciated. I'm going to try safe mode now, but as far as I'm aware, all I can do is boot the tablet into recovery mode. So is there a driver that would allow me to use the shell, pull, or backup commands from either stock recovery or the bootloader menu?
Click to expand...
Click to collapse
With stock recovery and locked bootloader with Android that won't boot, and not being to factory reset because you want to save your data, you won't be able to do any normal adb commands.
The only thing you might want to try is the adb backup command, which I've never tried from stock recovery, so there is a remote possibilty it might work, but probably not.
---------- Post added at 09:56 AM ---------- Previous post was at 09:54 AM ----------
Stealth22 said:
Update...
So, safe mode doesn't work as far as booting the device goes; it just hangs at the 'X' screen.
However, something named "Nexus 7" shows up in Device Manager, and when I told it to look for a driver in the folder containing the USB drivers from Google, it installed a driver, and called it "MTP USB Device".
Unfortunately, the device doesn't show up under My Computer (damn it, wishful thinking!!), and then after about 15 seconds, a yellow exclamation mark shows up on the device icon in Device Manager, and it generates an error saying "This device cannot start. (Code 10)".
Does this at least seem like progress?
Click to expand...
Click to collapse
It would have been huge progress if you got the MTP device recognized as you could drag and drop files.
You can try spending some time figuring out whether it is a driver issue or the unit hasn't booted up far enough to response to MTP requests by removing drivers and let it reinstall with known good ones.
The ADB backup command was the first thing that I tried, it didn't work. I can't do ANYTHING with ADB in recovery mode because the computer doesn't even recognize that the tablet is connected until I select "Apply update from ADB", at which point I can only run the sideload command. Any other ADB command (backup included) brings up "error: closed".
I guess my last hope will be the MTP option, if I can get the driver working. I think I'm going to have to call Google on this one.
Stealth22 said:
Ok, so, this is a two part question.
I've got a 32GB Nexus 7, and I'm having some issues with it. This tablet is completely stock. I haven't rooted it, I haven't unlocked the bootloader, installed a custom ROM or anything. All I've done with it was install OTA updates from Google, download some apps/games, and take some pictures.
About two days after I bought the thing and set it up, I got an error that said "System UIDs inconsistent" or something to that effect. I'd never seen it before, but a Google search revealed that the easiest way to fix it was to do a wipe/factory reset, so I did.
Fast forward to a couple of days ago...I'm from Canada, and while driving down to the States, I was bored, so I took out my shiny new Nexus 7, and turned it on. It was stuck at the 'X' screen, and wouldn't boot. I was frustrated, but because I was still in Canada, I was able to run a search on my phone. Factory reset. Ugh. So I did...once it finished, I used my data plan to download a few essential apps, and it was good to go.
Fast forward to today. I'm going to be returning home later today, but yesterday I decided to try out the GPS functions, because the TomTom GPS I've got isn't the greatest, and I much prefer Google Maps Navigation. A friend with a Nexus 4 was able to use the wifi where we were staying to get directions to various places, and then he'd shut off the wifi, and his N4 would still maintain the GPS signal and navigate him for the whole trip, even with no data, and for a lot of the time, no cell signal at all. I wanted to try the same with my N7, not knowing that many users are experiencing issues with the GPS.
So yesterday I was trying to use the Sygic GPS app, which apparently does offline navigation. And I guess because the N7 location capabilities are iffy right now, it wasn't working. So I, in my infinite wisdom, decided to reboot the tablet, thinking that would fix the GPS. This was after I had taken LOTS and LOTS of photos during the trip.
The tablet reboots, and gets stuck on the 'X' screen again. I was ready to bash my head through the car window at that point.
Long story short, the tablet doesn't boot. I'm a software developer for a living, so I had (keyword.. HAD) USB debugging turned on, but since I had to wipe the thing at the start of the trip, I never re-enabled USB debugging, but I don't recall if you actually have to or not...I'm assuming that it loses that setting when you wipe it.
So USB debugging, I can only assume, is not enabled. I can boot into recovery mode, but all I get is the Android icon with a red exclamation mark, and a message that says "No command". I know that you can press the power and volume up buttons to get the menu in recovery mode.
But what I was hoping to be able to do was use ADB to pull a full backup of the device, to at least salvage all the photos I took. I don't care about the apps, I can always reinstall those. I did not have a chance to set up an auto-sync (either Dropbox or Google+) of the photos, unfortunately.
I downloaded the Google USB drivers, and the Android Platform Tools (the wifi at this hotel sucks, so I didn't get the full SDK), and I'm using my brother's laptop, which is running Windows 8. I can get the tablet into recovery mode, and the laptop recognizes the tablet when I try to power it up, or when its in the fastboot menu.
But I can't get ADB to recognize the Nexus at all, it doesn't appear in adb devices whatsoever. And right now, the laptop doesn't seem to react when I plug the tablet in after booting into recovery mode. I also tried plugging in the USB cord, then booting into recovery mode, same thing.
I can only get ADB to recognize the tablet if I hit the "Apply update from ADB" option in the recovery menu. It shows up in adb devices, but it says "sideload" next to it, and if I try any other adb command (shell, backup, pull, etc) it just says "error: closed". I tried adb kill-server and adb start-server, then adb backup again, no dice.
I stayed up till 1AM last night fiddling with this thing, and I have a feeling that I might need to wait till I get home, or maybe when I get to work, as I believe I've got the full Android SDK installed there.
So, my two questions on this are...
1) What the hell am I doing wrong? Is there any way for me to recover the photos from the device? I'm sure that adb backup will work, if I could just get this damn laptop to recognize the device.
I've done quite a few Google searches already, and found a few results. I can't post links apparently, but there's a certain thread posted on StackExchange about how to perform a full backup of non-rooted Android devices. While it was helpful, I can't do that backup because this laptop won't recognize the tablet.
But I'm just spinning my wheels here, and could really use some help. Are there different drivers I should be using? Is there a way to run ADB from the bootloader rather than recovery mode? How do I get Device Manager (Windows) to even recognize the tablet when its in recovery mode?
2) So this will be the third time (after I get these photos recovered, hopefully) that I'll be doing a wipe on this tablet. I've got a two year replacement warranty on it. Should I be taking it back for a new one? Would it be a bad app thats causing these issues? Most of the apps I have are "official" ones anyway, aside from a couple of games, but they're all popular ones. After the wipe, should I re-flash it with Google's latest stock ROM?
Thanks in advance!!
Click to expand...
Click to collapse
I would take it back, if you haven't rooted it, unlocked the bootloader then you probably got a lemon. Just return it, not worth the hassle. Even if you fix it yourself you shouldn't have too. My recommendation is to return it.
sfhub said:
With stock recovery and locked bootloader with Android that won't boot, and not being to factory reset because you want to save your data, you won't be able to do any normal adb commands.
Click to expand...
Click to collapse
Ah, I stand corrected. I don't have much experience with the stock recovery; one of the first things I did when I got this phone was install CWM, and I haven't flashed a stock recovery image since.
So, back to OP:
Try getting MTP to work in recovery, then you can manually bring the files over through Explorer.
Wait, why not install a custom recovery? go here, download the fastboot file, and put it in your platform-tools folder. Might want to rename it to "recovery.img" if it isn't already named that. Now:
1. Boot into the bootloader (power off, hold Power and Volume down until it vibrates and goes to a screen with an Android on his back and his chest open)
2. Once there, see if adb will recognize your device. If not, try installing the drivers again.
3. If adb sees your device, issue this command (assuming the CWM recovery.img file is in your platform-tools folder)
Code:
fastboot flash recovery recovery.img
Once that's done, boot up into your new custom recovery. From there, make a nandroid (optional, that nandroid will contain your pictures if you want to do a factory reset or accidentally hit something). Now if you can get adb to recognize your phone while in this recovery, you can issue adb commands such as adb pull. I would do:
Code:
adb pull /sdcard/ \sdcard\
That will pull the entire contents of your sdcard to a folder called \sdcard\ under platform-tools.
EDIT:
Slight revision to the command I gave you to pull your pictures. If you just want the pictures taken by your camera, run
Code:
adb pull /sdcard/DCIM/Camera/ camera\
That will pull the pictures and place it into a folder called 'camera' inside of your platform-tools folder. The previous code I gave you would put the entire contents of you sdcard in a folder called 'sdcard' on the root of the C:\ drive because I put a back-slash ahead of the folder name. My mistake.
I'll give it a try, but I'm 99.9% sure that I can't flash a recovery image unless the bootloader is unlocked, which wipes all of the data.
I'm just downloading a factory image now...I've pretty much accepted the fact that the photos are gone.
Stealth22 said:
I'll give it a try, but I'm 99.9% sure that I can't flash a recovery image unless the bootloader is unlocked, which wipes all of the data.
I'm just downloading a factory image now...I've pretty much accepted the fact that the photos are gone.
Click to expand...
Click to collapse
Oh yeah, I'm sorry. I keep forgetting you have your bootloader locked, whoops.
Hey, I just thought of something else. Are you planning on flashing those images one by one, following a guide similar to this one? If so, if you don't flash userdata.img, it should preserve your data, including contents of /sdcard/. He touches on it a bit in the guide:
10) Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked. See note 2 below.
Click to expand...
Click to collapse
2) This note is NOT for n00bs. There has been a lot of uncertainty and questions around stock ROMs and losing/wiping data. You CAN flash a stock ROM WITHOUT losing the data stored in /sdcard (and possibly even all apps and app data, although this depends on which apps you have installed). This can be done by skipping step 10 in part D. However, if your device goes into a boot loop, you will need to boot CWM, and wipe data <-- this will wipe your apps and app data, but not /sdcard.
Click to expand...
Click to collapse
Might want to note that the guide I posted was for the Nexus 4, but the process should be the same. Try not flashing userdata.img when flashing the stock image.
If the bootloader was unlocked to begin with, yeah, that would work. The guide for the N7 has a similar note about preserving user data.
I've gone ahead with the factory reset. Next time, I'll be sure to have automatic backups to Dropbox or Google+.
I'm going through the same thing right now.
Photos from vacation in Italy. I did back up half of the trip but wifi was so slow at the hotels that I couldn't get everything.
Now Stuck on X at boot.
Boot loader locked.
USB debugging off.
I installed the Nexus 7 Toolkit.
I too was only able to get my computer to recognize the nexus only in sideload mode.
I was able to load an update to the nexus through sideload and it did install.
I was hopeful that the update would have fix it but it did not.
I poked around in the update zip file and say a script called install-recovery.sh.
I was wondering if this script or another one that runs during the update process could be edited to run something like and adb pull or backup.
Does anyone know if this is possible?
I don't know much about adb or messing around with ROMs, etc. I don't even know what language this sh file is written in. Could someone tell me?
Thanks.
joecap5 said:
I'm going through the same thing right now.
Photos from vacation in Italy. I did back up half of the trip but wifi was so slow at the hotels that I couldn't get everything.
Now Stuck on X at boot.
Boot loader locked.
USB debugging off.
I installed the Nexus 7 Toolkit.
I too was only able to get my computer to recognize the nexus only in sideload mode.
I was able to load an update to the nexus through sideload and it did install.
I was hopeful that the update would have fix it but it did not.
I poked around in the update zip file and say a script called install-recovery.sh.
I was wondering if this script or another one that runs during the update process could be edited to run something like and adb pull or backup.
Does anyone know if this is possible?
I don't know much about adb or messing around with ROMs, etc. I don't even know what language this sh file is written in. Could someone tell me?
Thanks.
Click to expand...
Click to collapse
I don't know if you can edit that script to pull a backup, I'm not really an expert on that subject. But from the amount of time and effort I spent, my guess would be that you (like I was) are unfortunately SOL.
I know it's been 3 weeks since you posted, but I thought I'd reply anyway, in case this ever happens to anyone else. Long story short, I was never able to recover anything, and was forced to do a reset.
I had called Google and tried to see if they could work out a solution. I was willing to ship the tablet to them, have them pull the data off, do a reset, and ship it back, but obviously, they said they couldn't do that.
In the end, I accepted that the photos were gone, and did a factory reset. Then I downloaded the stock image from Google, and reinstalled the stock OS from scratch, because of the issues I was having. I just figured that because this was the third time I was doing a factory reset, that something was screwed up with the factory image that was on the device, and that it wouldn't hurt to do a fresh install.
The very first thing I did was install Dropbox and set up the automatic sync function for photos.
I haven't rebooted my N7 very much since then (for fear of this happening again!), but whenever I've had to, it's started up with no issues. Now, I'm careful about what apps I install from Google Play, and any time I have to do a reboot or if Google sends out an update, I do a full backup first. In fact, I hadn't done a backup in a while, so I just pulled a backup, and restarted the tablet because my BT keyboard wouldn't connect. No issues this time either.
From now on though, any time I go on vacation, I don't care if I'm using a real camera or if I forget the camera and have to use my phone or N7. The laptop comes with me on the trip, and photos/videos taken get backed up at the end of each day. Copied to the laptop, to my USB passport drive, Dropbox, the whole 9 yards. I learned that lesson the hard way, and I'm a programmer for a living, so I definitely should have known better.
Moral of the story...if it's important to you, don't be lazy like I was. BACK IT UP.
Try this:
Stealth22 said:
Ok, so, this is a two part question.
I've got a 32GB Nexus 7, and I'm having some issues with it. This tablet is completely stock. I haven't rooted it, I haven't unlocked the bootloader, installed a custom ROM or anything. All I've done with it was install OTA updates from Google, download some apps/games, and take some pictures.
About two days after I bought the thing and set it up, I got an error that said "System UIDs inconsistent" or something to that effect. I'd never seen it before, but a Google search revealed that the easiest way to fix it was to do a wipe/factory reset, so I did.
Fast forward to a couple of days ago...I'm from Canada, and while driving down to the States, I was bored, so I took out my shiny new Nexus 7, and turned it on. It was stuck at the 'X' screen, and wouldn't boot. I was frustrated, but because I was still in Canada, I was able to run a search on my phone. Factory reset. Ugh. So I did...once it finished, I used my data plan to download a few essential apps, and it was good to go.
Fast forward to today. I'm going to be returning home later today, but yesterday I decided to try out the GPS functions, because the TomTom GPS I've got isn't the greatest, and I much prefer Google Maps Navigation. A friend with a Nexus 4 was able to use the wifi where we were staying to get directions to various places, and then he'd shut off the wifi, and his N4 would still maintain the GPS signal and navigate him for the whole trip, even with no data, and for a lot of the time, no cell signal at all. I wanted to try the same with my N7, not knowing that many users are experiencing issues with the GPS.
So yesterday I was trying to use the Sygic GPS app, which apparently does offline navigation. And I guess because the N7 location capabilities are iffy right now, it wasn't working. So I, in my infinite wisdom, decided to reboot the tablet, thinking that would fix the GPS. This was after I had taken LOTS and LOTS of photos during the trip.
The tablet reboots, and gets stuck on the 'X' screen again. I was ready to bash my head through the car window at that point.
Long story short, the tablet doesn't boot. I'm a software developer for a living, so I had (keyword.. HAD) USB debugging turned on, but since I had to wipe the thing at the start of the trip, I never re-enabled USB debugging, but I don't recall if you actually have to or not...I'm assuming that it loses that setting when you wipe it.
So USB debugging, I can only assume, is not enabled. I can boot into recovery mode, but all I get is the Android icon with a red exclamation mark, and a message that says "No command". I know that you can press the power and volume up buttons to get the menu in recovery mode.
But what I was hoping to be able to do was use ADB to pull a full backup of the device, to at least salvage all the photos I took. I don't care about the apps, I can always reinstall those. I did not have a chance to set up an auto-sync (either Dropbox or Google+) of the photos, unfortunately.
I downloaded the Google USB drivers, and the Android Platform Tools (the wifi at this hotel sucks, so I didn't get the full SDK), and I'm using my brother's laptop, which is running Windows 8. I can get the tablet into recovery mode, and the laptop recognizes the tablet when I try to power it up, or when its in the fastboot menu.
But I can't get ADB to recognize the Nexus at all, it doesn't appear in adb devices whatsoever. And right now, the laptop doesn't seem to react when I plug the tablet in after booting into recovery mode. I also tried plugging in the USB cord, then booting into recovery mode, same thing.
I can only get ADB to recognize the tablet if I hit the "Apply update from ADB" option in the recovery menu. It shows up in adb devices, but it says "sideload" next to it, and if I try any other adb command (shell, backup, pull, etc) it just says "error: closed". I tried adb kill-server and adb start-server, then adb backup again, no dice.
I stayed up till 1AM last night fiddling with this thing, and I have a feeling that I might need to wait till I get home, or maybe when I get to work, as I believe I've got the full Android SDK installed there.
So, my two questions on this are...
1) What the hell am I doing wrong? Is there any way for me to recover the photos from the device? I'm sure that adb backup will work, if I could just get this damn laptop to recognize the device.
I've done quite a few Google searches already, and found a few results. I can't post links apparently, but there's a certain thread posted on StackExchange about how to perform a full backup of non-rooted Android devices. While it was helpful, I can't do that backup because this laptop won't recognize the tablet.
But I'm just spinning my wheels here, and could really use some help. Are there different drivers I should be using? Is there a way to run ADB from the bootloader rather than recovery mode? How do I get Device Manager (Windows) to even recognize the tablet when its in recovery mode?
2) So this will be the third time (after I get these photos recovered, hopefully) that I'll be doing a wipe on this tablet. I've got a two year replacement warranty on it. Should I be taking it back for a new one? Would it be a bad app thats causing these issues? Most of the apps I have are "official" ones anyway, aside from a couple of games, but they're all popular ones. After the wipe, should I re-flash it with Google's latest stock ROM?
Thanks in advance‼
Click to expand...
Click to collapse
Ok, first of all, have you tried to - simply let it on the Charger!??
Then press and hold the power button
If it doesn't work: Has the device ever taken a kind of damage because of heat/water/drop/whatever?
Try to replace the battery.
Try to hold the so►called „KEÝ4" inside of the device- for exactly 16.0 to 16.2 seconds. Then you smoehow can manage and check the hardware health+status+whatever. Efficient application. Also works with 0,1% battery charge.☺☻☺
I'm so sorry for you.
Which Nexus is it? (2012/2013? How many GB? Which Android Version? Because KitKat is bogus.))
I know a Galaxy S3 Mini, fell into water for 3 Seconds.
Then everything worked perfectly fine but... even if the device was turned off and connected to the charger: the device actually did recogniƶe the Charger but then:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
►Turned into►►→→
‼‼
I hope, that i could help.
All the best for you and your Nexus.

[Q] KF2 Empty and not recognized on windows

So I was trying to change my son's Fire 2 over to the new Kit Kat OS, and as I was downloading the necessary files to my computer, I thought I would wipe everything, since he had managed to pretty much fill it with junk, (he's 8). I have TWRP, (2.3.3.0) installed, and used that to wipe everything, including the internal storage and the format data wipe. I have done this with my Fire 1 with no issues, but this time I ran into a problem. TWRP works fine, but now windows won't recognize the tablet. When I go to mount the usb storage to copy the os files over, windows 7 cant load the device drives, and in my device manager it shows the Amazon Kindle fire 2 with the yellow exclamation mark next to it, saying that the drivers for this device are not installed. I have the SDK installed, and I have gone through and re installed the device drivers several times, and also uninstalled the kindle from the device list in manager. Nothing is working. I have attempted fastboot, but when I do try, it gets stuck at the "press the button menu" for TWRP, and after running the fastboot -i 0x1949 getvar product command, it tells me it sees an Otter2-Prod-04.
Does anybody have any ideas or suggestions on how I can get into the usb storage so I can load the OS info? Thanks for any help.
Dead?
Well, I rebooted from TWRP and it just went black. No light when the cable is plugged in, (factory cable), no twenty second reset working, nothing. IS it safe to assume I now have a pretty paperweight, and I should be looking into getting my son another tablet?
xanthian23 said:
Well, I rebooted from TWRP and it just went black. No light when the cable is plugged in, (factory cable), no twenty second reset working, nothing. IS it safe to assume I now have a pretty paperweight, and I should be looking into getting my son another tablet?
Click to expand...
Click to collapse
Leave it on the charger overnight. Keep trying 20 second reboot. If you can get back into recovery you can adb sideload a rom into the device.
You've never been able to USB Mount this device from recovery.
Good luck. No reason it should be bricked....
How did you try to get into fast boot? You need a fastboot cable. This device is NOTHING LIKE the kf1.
Edit: also need to be sure exactly which kf2 you have.
--》Sent from my mind to your screen
mindmajick said:
Leave it on the charger overnight. Keep trying 20 second reboot. If you can get back into recovery you can adb sideload a rom into the device.
You've never been able to USB Mount this device from recovery.
Good luck. No reason it should be bricked....
How did you try to get into fast boot? You need a fastboot cable. This device is NOTHING LIKE the kf1.
Edit: also need to be sure exactly which kf2 you have.
--》Sent from my mind to your screen
Click to expand...
Click to collapse
I have the standard cheap Kf2, no HD, just the upgrade from the first from last year, (2012), they were selling around Christmas last year. I have tried getting it to start back up, but with no success. I don't even understand why it shut down like that. I hadn't done anything to it other than reboot, which I had done successfully several times before. As for the fastboot, I may be incorrect. I ran the adb command: fastboot -i 0x1949 getvar product in CMD, and then plugged the kindle in and booted up. It showed it was an otter4 or something like that, which I thought meant it was in fastboot. At that time I was using my S4 usb cable. I'm sure I can sort out ho to sideload a rom via adb if I can ever get it started back up again. I had thought about opening it up and unplugging the battery and then re-plugging it back it to try to reset it, but I doubt it will help. Would getting a fastboot cable possibly make it start back up? If anyone has any suggestions on how I can get this thing started up again I would greatly appreciate it. I fell like crap for bricking my kids kindle, he's 8, so it's really important to him. It'll take me several months to save up to buy another one, so if I can get it running again, that would be awesome.
Here's a bit of an oddity, and maybe this spells some hope for me yet. So I plug the KF2 into the computer with the factory cable, hold down the power button for twenty seconds, let go, and then hit the power button again, for about a second, and windows makes the usb device plugged in sound, followed by a usb rejected or not recognized sound. It repeats this over and over for about thirty seconds or so and then stops. So there is something going on with the kindle, and its not flat out dead, or at least it seems. Is this a good sign? Does this help anyone to figure out what I might need to do?
So just to be sure that I was using a fastboot cable, even though I believe that my samsung s4 cable is fastboot capable, and I'm pretty sure I am using the factory cable, (it's not marked so I can't be 100% sure), I built my own fastboot cable, via instructions on how to do so on xda. (found HERE) It's doing the same thing with windows making the usb device inserted / recognized sound, followed by the usb device error sound. I'm guessing that this is a bad thing, am I correct?
One more bit of information to add to the list. I attempted to do the fastboot mode again,and decided to watch my device manager. Whenever windows chimes off that it detects a usb device, something called OMAP 4430 pops up for about a second before disappearing when the error sound comes on. I'm going to try and get a driver for that, just to see what happens. Maybe it'll help. I doubt it, but you never know until you try...
This just keeps getting weirder and weirder. So I installed the omap driver for windows and android, and now windows recognizes the device, but only for about a second. It just keeps cycling through the usb connected sound, recognizing the omap device, and then the usb disconnected sound, as though the device were being plugged in and then unplugged about every second for roughly thirty seconds. I'm starting to think there is something seriously wrong, which bites. If anyone has any suggestions, I'm all ears.
That's a hard brick' we can't use the usboot/aboot utility to fix the device like you can on other omap devices because we need a certain signed file to fix the boot loader. Only amazon has that file and they aren't giving it out. There is a way to recover your device from a hard brick but you need to be good with a soldering iron and have a USB sdcard reader, the kind that kinda is like a flashdrive rather than the multi type readers and some really small wire. Kurohyou wrote a tutorial on how to fix it in the kf2 dev section, not sure if he ever added the part in on how to reflash the boot loader from Linux, but if you take this route and try to fix it I wouldn't mind helping.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
That's a hard brick' we can't use the usboot/aboot utility to fix the device like you can on other omap devices because we need a certain signed file to fix the boot loader. Only amazon has that file and they aren't giving it out. There is a way to recover your device from a hard brick but you need to be good with a soldering iron and have a USB sdcard reader, the kind that kinda is like a flashdrive rather than the multi type readers and some really small wire. Kurohyou wrote a tutorial on how to fix it in the kf2 dev section, not sure if he ever added the part in on how to reflash the boot loader from Linux, but if you take this route and try to fix it I wouldn't mind helping.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
OK, I have both a tf - micro sd card usb card reader, and a full sd card usb card reader. I'll have to go digging for them in the morning, but I think I can find them. I'm also really good with a soldering iron, (used to be a vcr / tv repair technician), It took me roughly two minutes to do the homemade factory cable. So I am game, especially since at this point I really have nothing to loose by trying. Would you mind posting a link to where the tutorial is? I'm going to go looking for it, but just in case I can't find it, a link would help. And thank you so much for this suggestion!
OK, I found the tutorial on how to wire everything up and what's needed. I'll have to go get some small wire and a better tip for my iron, but aside form that, the wiring and soldering seems simple enough. My problem is going to be dealing with linux. I know Windows backwards and forwards, but I have a pretty limited knowledge of linux, aside from a few things we did in school to cover general PC repair. I can get it up an running, which I will do tomorrow, but I may need some help sorting out what to do with it once I have the board lined up and ready to roll, which will have to wait till next week when I get back from a work trip. Do you know if kurohyou offers repairs? If it's not too expensive, I would be willing to pay for the fix.
He might repair it, he just made a solderless repair tool to repair them. But like I said I'm more than willing to help with the Linux side, I'm a PC tech myself and use Linux primarily, you can basically burn an ubuntu live CD or put it on a USB stick and boot into the entire os without having to install it, from there's its as simple as plugging the device into the PC, and seeing what device path it assigned to the kindle's emmc, and running a dd command to flash the boot loader back onto the device.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
... you can basically burn an ubuntu live CD or put it on a USB stick and boot into the entire os without having to install it, from there's its as simple as plugging the device into the PC, and seeing what device path it assigned to the kindle's emmc, and running a dd command to flash the boot loader back onto the device.
Click to expand...
Click to collapse
Yeah, I've ran a live usb version of unbuntu a few times, and in the past I have had the full version on my system, but I rarely ever used it, so I got rid of it. I have an extra 600 gig's of space just sitting around on my laptop, so I will install a full version, and get off my lazy rear and start learning linux. This should be a good first lesson. I can't do any of this until next week though, so I will be pm'ing you once I've gotten everythig hooked up and ready to go. Thanks again for the help.
I had a question about the repair though. I went through the discussion, and I may have just missed it, but did he ever figure out how to get the OS up and running? From what I could tell, he was still working on it, and hadn't managed to get a working rom loaded. I probably just either missed it, or didn't understand one of the post's.

[Q] cant enable usb debugging, fastboot doesnt work

I have a Nexus 7 2013 that wont boot. USB Debugging was not enabled. At this point, I am just trying to wipe the machine with a stock image, but I am having trouble.
I have installed the sdk and drivers (so many drivers!)
Recovery mode fastboot does not recognize the device.
ADB recognizes the Nexus, but I cant seem to get it to do anything with it.
e: failed to mount anything.
I have read through so many forum threads that I'm just overwhelmed, and they all seem to require the machine being in USB debugging mode before any changes can be made.
Please help or tell me what pertinent information I have omitted.
Thank you
I think USB debugging only matters in ADB, which is when the device is actually booted into Android OS. You probably want fastboot, which is a different "application" and set of commands in a command prompt.
Code:
fastboot devices
Does that give you anything when the tablet is in fastboot mode? It should list the serial number of the device, similar to "adb devices" does. If not, it could be drivers, or another issue with the device.
Have you tried unlocking the bootloader? This will induce a factory reset of the current firmware version, which may allow you at least boot normally and take any available OTA updates.
Hello,
fastboot devices lists nothing, while adb does show the serial number.
I have used so many tutorials and a couple of toolkits that now I have no idea what is happening with my drivers.
Unlocking the bootloader to force a factory reset sounds amazing, but all the information I can find says I need to have USB debugging enabled to do so. I can not boot into the system to enable it.
Is there a way to force a reset without USB debugging?
Thank you
Usb debugging is irrelevant. Forget about it, it's only used when the system is booted.
You need to get fastboot devices to recognize the tablet.
Uninstall any and all toolkits and drivers. Redownload the sdk. Boot to the bootloader and plug it in, the drivers should install automatically. If not install the google usb drivers from the sdk manager in the sdk.
Try fastboot devices again. If it doesn't work try a different usb cord/port/computer.
You are in the bootloader when running this command right? Not the recovery? I think with the tablet off it's volume down and power. The screen that says start in big green letters at the top and has device info in the bottom left is what you want.
Edit: Did you boot to recovery and select the options to wipe data and cache? Sometimes thats all thats needed.
Also booting to recovery and performing a factory reset may be sufficient.
ADB will indeed function in recovery. I don't think you have to enable USB debugging to get this to work though.
Are you typing fastboot devices while booted in recovery? Typing fastboot devices while in recovery or booted into Android will do nothing.
hello, thank you for your advice. I now get the nexus seen by fastboot (and win 7) but have hit a wall. The last time I had my computer and the nexus together was weeks ago, when I my computer BSOD during what I thought was a simple flashing of the the stock image, but turned out to be hours of the nexus saying it was erasing personal data ... and then crash. I have replaced and added fans so my cpu wont overheat again, so please offer ideas why "fastboot flashall" or "fastboot flash image-razor-kot49h" wont work.
I appreciate all responses, and believe the answer is either very simple or a catastrophic hardware failure. I base this belief on what is left in my head after smashing it into the wall so many times over the last month when my wife asks me, "have you fixed my nexus yet, or do I need to figure out a way to buy a new one next month?"
I am stuck at unlocking the bootloader. I have highlighted "yes" on the nexus and pressed power and my command window says "erasing user data." It has said this for the last 18 hours. This is the second computer I have tried this on, using 3 different usb cables. What am I missing?
helpmynexus said:
hello, thank you for your advice. I now get the nexus seen by fastboot (and win 7) but have hit a wall. The last time I had my computer and the nexus together was weeks ago, when I my computer BSOD during what I thought was a simple flashing of the the stock image, but turned out to be hours of the nexus saying it was erasing personal data ... and then crash. I have replaced and added fans so my cpu wont overheat again, so please offer ideas why "fastboot flashall" or "fastboot flash image-razor-kot49h" wont work.
I appreciate all responses, and believe the answer is either very simple or a catastrophic hardware failure. I base this belief on what is left in my head after smashing it into the wall so many times over the last month when my wife asks me, "have you fixed my nexus yet, or do I need to figure out a way to buy a new one next month?"
I am stuck at unlocking the bootloader. I have highlighted "yes" on the nexus and pressed power and my command window says "erasing user data." It has said this for the last 18 hours. This is the second computer I have tried this on, using 3 different usb cables. What am I missing?
Click to expand...
Click to collapse
I have the same problem .. Have You reslove it?
bikicviki said:
I have the same problem .. Have You reslove it?
Click to expand...
Click to collapse
This may help...it may not. But I was having issues getting my bootloader unlocked also when I started on mine. My remedy was to
1 plug in the nexus into the usb
2 I run Linux so it gives me choices on what to do with newly plugged in usb device. I noticed two identical choices to mount device. Choosing one just mounted the camera for some strange reason. I closed that window, then chose the other choice to mount device, the window opened and my full internals were there in the window
3 from a terminal I just wrote a prompt: fastboot oem unlock
and for some reason, it unlocked.
To sum it up I'm convinced it has something to do with how the device gets mounted. At least on mine anyway.
As for activating developer from a terminal I read it could be done but never tried it myself, if you want here's the link for the info, read the second answer down.
https://stackoverflow.com/questions/47510232/is-there-any-adb-command-to-enable-developer-options
Also check out the fastboot manual for some other things to try, you never know some may work in your situation at a terminal prompt
man fastboot
---------- Post added at 07:12 PM ---------- Previous post was at 06:57 PM ----------
Troops42 said:
This may help...it may not. But I was having issues getting my bootloader unlocked also when I started on mine. My remedy was to
1 plug in the nexus into the usb
2 I run Linux so it gives me choices on what to do with newly plugged in usb device. I noticed two identical choices to mount device. Choosing one just mounted the camera for some strange reason. I closed that window, then chose the other choice to mount device, the window opened and my full internals were there in the window
3 from a terminal I just wrote a prompt: fastboot oem unlock
and for some reason, it unlocked.
To sum it up I'm convinced it has something to do with how the device gets mounted. At least on mine anyway.
As for activating developer from a terminal I read it could be done but never tried it myself, if you want here's the link for the info, read the second answer down.
https://stackoverflow.com/questions/47510232/is-there-any-adb-command-to-enable-developer-options
Also check out the fastboot manual for some other things to try, you never know some may work in your situation at a terminal prompt
man fastboot
Click to expand...
Click to collapse
Tried to edit but anyway:
After re..re, rereading your post, and responces. Have you tried the old fashioned way
Hold down the (down volume) button at the same time the (power) key.."Together" If you get anything that pops on your screen let go of the keys, one tap at a time tap the volume up or down key ONLY, until it says (START), its in green type. if you get there you should be ok, to move along

unbricked Fire TV gen 1 boots to Amazon setup but no Ethernet, no WIFI network

my previously rooted Gen 1 AFTV started to have issues so I tried to update the rather old OS build - and bricked the device. no LED light, nothing.
using an A-A cable I successfully followed rbox' instructions in https://forum.xda-developers.com/showpost.php?p=66961740&postcount=676 writing the contents of update-kindle-bueller-51.6.3.2_user_632552020.bin to the respective partitions and wohoo, the box booted again, although without rbox' bootloader which I didn't care for too much then.
worse problem was there was also no network connection - neither Ethernet (no link) nor WIFI (just kept scanning forever) worked. not really knowledgeable about the boot process of Android devices I resorted to a factory reset, which seemed to work but now I'm stuck at the Amazon setup (just after language selection) still without network and no other way to go. tried the alt-prtscr-i route but that only got me to a screen with red text saying the device would enter recovery which never happened no matter how long the wait.
thinking the bin file may have been corrupted next I attempted to dd-write the partitions again with contents from another bin file but couldn't even "see" the partitions anymore. hooked up to a knoppix box nothing shows those sdcX partitions anymore: df -h, mount, fdisk -l, cat /proc/partitions. only command - briefly - showing a Qualcomm device was lsusb.
same on a W10 machine where the booting AFTV would briefly show up as a USB mass storage class device (of course without access to it) but would then disappear again with the corresponding sound. the box still boots to the amazon setup however.
now I'm stuck and don't know what to try next. previously ADB debugging was active and I sometimes used the interface to push packages to it but now I don't even have an IP connection anymore to dig into the config files :crying:
thanks for any ideas ! would love to get the box back to life again
bikernzrh said:
my previously rooted Gen 1 AFTV started to have issues so I tried to update the rather old OS build - and bricked the device. no LED light, nothing.
using an A-A cable I successfully followed rbox' instructions in https://forum.xda-developers.com/showpost.php?p=66961740&postcount=676 writing the contents of update-kindle-bueller-51.6.3.2_user_632552020.bin to the respective partitions and wohoo, the box booted again, although without rbox' bootloader which I didn't care for too much then.
worse problem was there was also no network connection - neither Ethernet (no link) nor WIFI (just kept scanning forever) worked. not really knowledgeable about the boot process of Android devices I resorted to a factory reset, which seemed to work but now I'm stuck at the Amazon setup (just after language selection) still without network and no other way to go. tried the alt-prtscr-i route but that only got me to a screen with red text saying the device would enter recovery which never happened no matter how long the wait.
thinking the bin file may have been corrupted next I attempted to dd-write the partitions again with contents from another bin file but couldn't even "see" the partitions anymore. hooked up to a knoppix box nothing shows those sdcX partitions anymore: df -h, mount, fdisk -l, cat /proc/partitions. only command - briefly - showing a Qualcomm device was lsusb.
same on a W10 machine where the booting AFTV would briefly show up as a USB mass storage class device (of course without access to it) but would then disappear again with the corresponding sound. the box still boots to the amazon setup however.
now I'm stuck and don't know what to try next. previously ADB debugging was active and I sometimes used the interface to push packages to it but now I don't even have an IP connection anymore to dig into the config files :crying:
thanks for any ideas ! would love to get the box back to life again
Click to expand...
Click to collapse
Only the unlocked bootloader is able to read/write to the emmc via the a-a usb cable. Adb debugging is gone due the factory reset.
What is installed on system? A prerooted rom? Then the solution is probably to boot into TWRP and wipe cache, dalvik, data, internalsd.
In case the TWRP bootmenu is gone too, there isn't much (maybe nothing) you can do...
Sus_i said:
Only the unlocked bootloader is able to read/write to the emmc via the a-a usb cable. Adb debugging is gone due the factory reset.
What is installed on system? A prerooted rom? Then the solution is probably to boot into TWRP and wipe cache, dalvik, data, internalsd.
In case the TWRP bootmenu is gone too, there isn't much (maybe nothing) you can do...
Click to expand...
Click to collapse
being a newbie to Android I'm not exactly sure. I believe it was a prerooted rom. it showed RBOX's BOOT MENU at startup and I did have root access.
according to "how-to-factory-reset-a-rooted-fire-tv-using-twrp-custom-recovery" on aftvnews the reset to factory defaults should not have removed root or TWRP, however there is no menu when booting the device and pressing right-arrow won't bring one up either. it just boots to the amazon setup
does that mean that I'll have to toss it?
bikernzrh said:
being a newbie to Android I'm not exactly sure. I believe it was a prerooted rom. it showed RBOX's BOOT MENU at startup and I did have root access.
according to "how-to-factory-reset-a-rooted-fire-tv-using-twrp-custom-recovery" on aftvnews the reset to factory defaults should not have removed root or TWRP, however there is no menu when booting the device and pressing right-arrow won't bring one up either. it just boots to the amazon setup
does that mean that I'll have to toss it?
Click to expand...
Click to collapse
Idk. If the bootmenu doesn't show, its probably gone.
About the network problem, maybe a router reset is worth a shot?
Sus_i said:
Idk. If the bootmenu doesn't show, its probably gone.
About the network problem, maybe a router reset is worth a shot?
Click to expand...
Click to collapse
thanks for your thoughts!
what has me curious still is the fact, that I no longer can access the box from Linux as I did before. wonder if the new OS is hiding TWRP info normally visible and if there is any secret way to invoke it?
the router is fine. always in use with various WIFI clients and also just successfully tested a cable connection to it with a laptop.
bikernzrh said:
thanks for your thoughts!
what has me curious still is the fact, that I no longer can access the box from Linux as I did before. wonder if the new OS is hiding TWRP info normally visible and if there is any secret way to invoke it?
the router is fine. always in use with various WIFI clients and also just successfully tested a cable connection to it with a laptop.
Click to expand...
Click to collapse
In case you are good with a solder iron, there is always the hardware option, in order to read/write to the EMMC partitions. Take a look here and here. But aside from the soldering skills, it cost some bucks to buy hardware...
Sus_i said:
In case you are good with a solder iron, there is always the hardware option, in order to read/write to the EMMC partitions. Take a look here and here. But aside from the soldering skills, it cost some bucks to buy hardware...
Click to expand...
Click to collapse
I fear my soldering expertise is not sufficient to attempt that guess I'll have to shop around for another used device instead as I need TOSLink and would also like to retain an Ethernet connection.
thank you so much for your help!

Categories

Resources