[Q] Bricked Nexus 7 only recognized by ADB when sideloaded - Nexus 7 Q&A, Help & Troubleshooting

My Nexus 7 has had a hard time ever since it went out of warranty, both getting stuck in boot loops and encrypting itself, thus requiring multiple hard resets.
The most recent time it got stuck in a boot loop was after the Kit Kat OTA update. It never gets past the Google logo (in previous times, it would make it to the X or colored dots). Performing a factory reset from the Bootloader > Recovery Mode menu never succeeds and still gets stuck at the Google logo.
I downloaded the Android SDK and was trying to attempt to reimage the tablet with the 4.2.2 image directly from Google and clear out/replace the corrupted factory restore files. I'm running into an odd issue right at the beginning - the only way I can get adb to recognize my device is when I go to Recovery Mode > Apply Update from ADB, at which time it sideloads my tablet. Otherwise, I cannot get my tablet to show up when executing "adb devices". Problem is, when it is sideloaded, I cannot execute any commands to the device. I manually installed the drivers directly from \android-sdk\extras\google (which allowed for the successful sideload).
Anyone know how to get my device to be properly recognized, when I can't boot it to enable USB debugging, etc? Or, is there a better way for me to get a clean image on my tablet? Can I do it via a sideload update and still clear out/replace the corrupted factory restore files?
Also, I was working off the following guide, but I'm not sure if it is exactly what I should be using, since I want to replace everything so that if I need to do a factory reset in the future, I can successfully do so via Bootloader > Recovery Mode without having to go through this process again!
I am new to Android debugging and images/flashing/etc, so I'm not fluent in the terminology and any help would be greatly appreciated.
Thank you!

Related

[Q] N10 *seriously* bricked after CF-Auto-Root and OTA

Since I'm a newbie here I can't post this problem to "[N10] CF-Auto-Root". If some kind person with permissions could alert the people there to this problem I'd really appreciate it.
I installed CF-Auto-Root on my Nexus 10, and after an OTA upgrade to 4.3 the tablet is seriously bricked. The sequence was as follows:
* Started from stock 4.2.2
* Downloaded the latest CF-Root (July 29)
* Manually re-rooted (as instructed on first page)
* Everything is peachy. su in adb shell works, get root prompt, etc. Browsed directories but made no changes.
* Attempted an OTA upgrade to 4.3 (Forgot to re-lock the bootloader). Upgrade failed, giving some generic (as in uninformative) error message. I think it was something about file check failed,
Now the tablet boot-up doesn't get past the colored X. I can get into bootloader/fastboot mode (robot on back with panel open). The device information is as follows:
Product Name: manta
Variant: wifi
H/W Version: 8
Bootloader Version: MANTALJ12
Carrier Info: NONE
Serial Number: <looks okay>
Lock State: UNLOCKED
Reboot Mode Flag: NONE
This is where I was when I first loaded CF-Root. However, now "adb devices" on the PC (Arch Linux) gives a blank list of devices. When I try to load the factory 4.3 image with "fastboot -w flashall" the PC prints the message:
< waiting for device >
and sits there. Not surprising since adb can't see the device.
I can get into recovery mode (robot on back with red triangle), and can access the menu. Performing wipe data / factory reset hasn't helped. From my PC "adb devices" still shows a blank list of devices.
When I start the "Apply update from ADB" utility from recovery mode, "adb devices" on the PC shows:
???????????? no permissions
If I then enter "adb sideload <file>" on the PC as the prompt on the tablet suggests (the file I used was an Android 4.3 upgrade zip file), the PC responds with:
error: insufficient permissions for device
Does anyone have any idea how I can get my tablet out of this mess? Right now all I want is to get my tablet working again. Any ideas are most welcome.
There's no point in running CF-Autoroot -before- updating to 4.3. You lose root after the update.
Also, just because you don't know what the error message means, doesn't mean it's not informative. What exactly was the error? Try fastboot mode and use the Nexus 10 toolkit located here: http://forum.xda-developers.com/showthread.php?t=2001868 to do a full flash. At this point it sounds like you've manually flashed a bunch of stuff so the regular update zip file is probably insufficient and you should be using the full factory image.
Solved
Got it solved (whew!). Had to run fastboot as root on the PC.
plastikowl said:
There's no point in running CF-Autoroot -before- updating to 4.3. You lose root after the update.
Also, just because you don't know what the error message means, doesn't mean it's not informative. What exactly was the error? Try fastboot mode and use the Nexus 10 toolkit located here: http://forum.xda-developers.com/showthread.php?t=2001868 to do a full flash. At this point it sounds like you've manually flashed a bunch of stuff so the regular update zip file is probably insufficient and you should be using the full factory image.
Click to expand...
Click to collapse
Yeah, I knew I'd lose root, but I'd already installed CF-Autoroot. Figured it would be easy to root again after. Foolish me!
Afraid I forgot to write down the error so it's lost. I was trying to do a full flash but failing (see my "solved post"). The update attempt was desperation, trying to get to the tablet somehow.
Anyway, I managed to do a full flash to the 4.3 factory image, so my tablet is no longer an expensive paperweight.
Thanks very much for yout input.

[Q] Recovering pictures from unrooted, locked, boot looping Nexus 4

Hi, after researching for the 3rd day straight I'm ready to make a post about this. Hopefully someone has some information I may have overlooked that can help me.
I have a completely stock, not rooted, boot loader locked Nexus 4 that was on the latest 4.4 OTA update (received OTA from Google). It was completely stock until I decided to enable the ART java runtime in developer options. The phone then updated my applications, rebooted and now displays the KitKat four circles boot animation for an unlimited amount of time (I've let it run for up to 30 minutes so far).
My question is: Is there any way to recover my pictures?
Every method I've looked into involves a step that requires wiping the phone and deleting my pictures. I've researched the ADB pull command and it appears that I can't run it successfully without being rooted, and I can't root without unlocking the boot loader, and unlocking the boot loader always wipes the phone (which deletes my pictures).
-USB debugging is not enabled
-I can boot into fastboot and I can load stock recovery.
-I downloaded the latest 4.4 full OTA zip file and sideloaded it ("adb sideload update.zip") but my phone still will not continue beyond the KitKat loading animation.
-I have tried wiping the cache and had no improvements.
-When I boot into recovery and use the command "adb devices" it reports my phone's serial number with the message "sideload" next to it.
I am uncertain about exactly how to use adb pull but the following attempts result in the message, "error: closed"
adb pull /data/media c:\android\backup
adb pull /data/media c:/android/backup
I have Wug's Nexus Root Toolkit v1.7.9 but it says that in order to use the "backup data/media" tool on Android 4.4 my boot loader must be unlocked (which will wipe my pictures).
Does anyone have any suggestions or advice? The pictures were recently taken and I delayed a little too long on backing them up.
Thanks for your time!
Android-SV650 said:
Hi, after researching for the 3rd day straight I'm ready to make a post about this. Hopefully someone has some information I may have overlooked that can help me.
I have a completely stock, not rooted, boot loader locked Nexus 4 that was on the latest 4.4 OTA update (received OTA from Google). It was completely stock until I decided to enable the ART java runtime in developer options. The phone then updated my applications, rebooted and now displays the KitKat four circles boot animation for an unlimited amount of time (I've let it run for up to 30 minutes so far).
My question is: Is there any way to recover my pictures?
Every method I've looked into involves a step that requires wiping the phone and deleting my pictures. I've researched the ADB pull command and it appears that I can't run it successfully without being rooted, and I can't root without unlocking the boot loader, and unlocking the boot loader always wipes the phone (which deletes my pictures).
-USB debugging is not enabled
-I can boot into fastboot and I can load stock recovery.
-I downloaded the latest 4.4 full OTA zip file and sideloaded it ("adb sideload update.zip") but my phone still will not continue beyond the KitKat loading animation.
-I have tried wiping the cache and had no improvements.
-When I boot into recovery and use the command "adb devices" it reports my phone's serial number with the message "sideload" next to it.
I am uncertain about exactly how to use adb pull but the following attempts result in the message, "error: closed"
adb pull /data/media c:\android\backup
adb pull /data/media c:/android/backup
I have Wug's Nexus Root Toolkit v1.7.9 but it says that in order to use the "backup data/media" tool on Android 4.4 my boot loader must be unlocked (which will wipe my pictures).
Does anyone have any suggestions or advice? The pictures were recently taken and I delayed a little too long on backing them up.
Thanks for your time!
Click to expand...
Click to collapse
u can use adb while unrooted, but the error: closed is because the device is in fastboot mode. u can try to backup /data/media while on stock recovery.if it dosent work, then just sending to jtag, so they dump the nand.
Your adb command is right but that's only for custom recovery. ABD is not allowed in stock recovery for good reasons, otherwise it's a huge security risk.
There really isn't a way to back up your data of you have stock recovery and locked bootloader. You'll have factory reset to lose everything and see of it boot or unlock and install factory image.
Next time sync your photos with Google or DropBox, or leave the bootloader unlocked so you can not into recovery and retrieve the data.
sent via tapatalk
hey, there is jtag dump BUT, some ppl say that if u clear cache on stock recovery,then restart and connect to pc u can backup your things because of adb being enabled.other says that on boot with cleared cache it will mount on pc as normal.u can try that.

Need help!!! Cannot boot into twrp

Ok, I'm going to start by explaining everything I did up to this point to eliminate any troubleshooting sugggestions i may have already done.
I rooted and installed recovery the same way everyone else did. After a couple of days, I tried to install a ROM but im assuming i was encrypted because i was stuck in a loop that would only boot me into TWRP. Did my research and took the necessary steps to get around that and decrypt and boot into the new ROM.. FINALLY!!! Only one problem, this rom doesn't have Super SU installed, Alright... so i download the proper Super SU build and put it on my Micro SD card and try to boot into TWRP to flash....
This is where the problem begins. I never get the prompt to authorize my PC from my phone to allow anything, and i never did each time i reset. I'm almost certain the adb on this rom is messed up, i've wiped about 4-5 times to re-enable usb debugging from scratch in order to adb or fastboot into recovery via command prompt, however when i try adb, i get that unauthorized error an there's no option on the LG V20 to revoke under developer settings. Fastboot i just get the same "waiting for device" message. Also keep in mind that i set it to photo mode, every mode that was available and nothing. Tried different USB Cords and did this on both my laptop and my PC at work
I've tried uninstalling and reinstalling all of the drivers, re-installed the latest version of adb and fastboot to my PC, that didn't work either. Tried deleting the adbkeys file in the .android folder and still nothing.
When i try to boot in recovery manually, i just get the wipe data option and when i click yes to everything, it actually wipes my data. I'm unable to reflash TWRP because I can't access ADB or Fastboot due to the unauthorized error.
Someone, PLEASE HELP!!!!
any luck?
ahq1216 said:
Ok, I'm going to start by explaining everything I did up to this point to eliminate any troubleshooting sugggestions i may have already done.
I rooted and installed recovery the same way everyone else did. After a couple of days, I tried to install a ROM but im assuming i was encrypted because i was stuck in a loop that would only boot me into TWRP. Did my research and took the necessary steps to get around that and decrypt and boot into the new ROM.. FINALLY!!! Only one problem, this rom doesn't have Super SU installed, Alright... so i download the proper Super SU build and put it on my Micro SD card and try to boot into TWRP to flash....
This is where the problem begins. I never get the prompt to authorize my PC from my phone to allow anything, and i never did each time i reset. I'm almost certain the adb on this rom is messed up, i've wiped about 4-5 times to re-enable usb debugging from scratch in order to adb or fastboot into recovery via command prompt, however when i try adb, i get that unauthorized error an there's no option on the LG V20 to revoke under developer settings. Fastboot i just get the same "waiting for device" message. Also keep in mind that i set it to photo mode, every mode that was available and nothing. Tried different USB Cords and did this on both my laptop and my PC at work
I've tried uninstalling and reinstalling all of the drivers, re-installed the latest version of adb and fastboot to my PC, that didn't work either. Tried deleting the adbkeys file in the .android folder and still nothing.
When i try to boot in recovery manually, i just get the wipe data option and when i click yes to everything, it actually wipes my data. I'm unable to reflash TWRP because I can't access ADB or Fastboot due to the unauthorized error.
Someone, PLEASE HELP!!!!
Click to expand...
Click to collapse
different route but im in the same boat. any luck?
I fixed this shortly after. Wanted to avoid returning to stock as. The only option was you and I was on 10d. I had to go back to stock but luckily the recovery method still works.

nexus 6p updated to android 8.0 stuck in recovery mode reboot cycle

Hello,
Today I got a prompt to update Android to 8.0.0. Not sure why this came for the first time only now, I've been on version 6 for over a year.
After updating I got a notice that data was corrupt, and I must either retry recovery mode boot or factory reset.
Needless to say I don't want to reset and lose all data.
I have downloaded ADB and rebooted into Bootloader but cannot get the device to show up in my PC in order to backup data.
while in bootloader adb devices returns no results
fastboot devices returns my devices serial ## fastboot
however, when I try to enter recovery mode I just get the data corrupt loop again and ADP can't see anything.
d I'm not sure what the correct fastboot command is to backup or create an image that will allow device to boot.
If I use fastboot to load a flash will it wipe my user and app data? are there any other options to make a backup?
Thanks!
UPDATE:
After holding down power button for 15-20 seconds got a longer boot cycle. then going into boot loader and selecting Recovery Mode twice in a row I was able to get into normal recovery mode with full options. now trying to wipe cache and sideload using ADB but no resolution yet.
Note ADB NEVER showed my device when queried, even though it showed up in fastboot, but if I unplugged and plugged the USB and then just ran the ADB sideload command it is working.
https://productforums.google.com/forum/#!topic/nexus/cwyTP3gr10s;context-place=topicsearchin/nexus/nexus$206p$20can$27t$20load$20android
OPR6.170623.019 does not work
OPR5.170623.014 does not work
Tried OPM6.171019.030.E1 based on above link. IT WORKED!!
suggestion: go with latest build not your current which is causing issues.

1050F Bricked - Will not start in anything but DNX mode. Help!

Hi all,
I made a series of mistakes that got me to where I am now. All I intended on doing was repairing my dad's tablet which was running atrociously slowly. I tried to follow some steps, but improvised as I was getting errors and ended up making things a lot worse...
Now tuning on the tablet will directly go to a command line interface with a long series of errors and these are the last 2 lines:
Rich (BB code):
blkD :HardDisk - Alias (null)
PciRoot (0x0) /Pci (0x17,0x0) Ctrl (0x0) /HD(14,GPT,80868086-8086-8086-8086-000000000008,0x646828,0x16D47D8)
blkE :BlockDevice - Alias (null)
PciRoot (0x0) /Pci (0x17,0x0) Ctrl (0x0)
Press ESC in 1 seconds to skip startup.nsh, any other key to continue.
Shell> _
In this state it cannot be interacted with and won't be detected by my PC over USB.
This happens for normal, recovery and bootloader modes. The only mode that I can access is DNX mode but attempting to boot droidboot will result in the same command line UI described above, including when trying to restore the BIOS using the PC executable (which I assume needs to enter fastboot mode, which it can't do...).
What can I do now? Any way to get anything working in the above screen or through DNX?
I'm thinking that a partition was corrupt in addition to me wiping the ESP is causing this. Maybe it's possible to completely format and setup all the partitions and start from scratch again? How can I flash esp.img when all I have access to on the tablet is DNX mode?
Detailed history below...:
HISTORY
1)
The tablet is a Lenovo Yoga Tab 2 1050F. It was running very slowly to the point where my dad just didn't bother to use it. I thought it would be wise to factory reset it as a first step. There is no option to do so within the Lenovo skin of Android so I started by going into recovery mode and performed a factory reset from there.
After it rebooted, the Android UI would loop back to the language selection after connecting to a WiFi network and I would get "Unfortunately Google Play Services has stopped." error message. It would just loop through the Language Selection > Connect to WiFi network pages over and over.
2)
Having installed CM on my old S3 back in the day, I thought I could go about the same process and flash a gapps ZIP file in recovery mode. That didn't work, I got an error because the zip was unsigned.
I thought I could install TWRP to flash unsigned zips, reinstall Gapps and get the tablet passed the Android UI loop.
3)
I followed this guide on XDA to install an unofficial TWRP (which involved unlocking the bootloader). It didn't work because I couldn't flash over ADB (because the tablet couldn't allow Developer Mode since it was stuck in the Android UI loop). So I flashed as many files as I could in fastboot.
I eventually flashed the TWRP recovery.img but that didn't work : when turning on to Recovery mode it would just go back to the bootloader screen.
4)
I thought I must have screwed up something up so I tried to restore the BIOS using an executable I found but I realized the tablet was already upgraded to Lollipop and the only BIOS restoration exe was for Kitkat. Sure enough it got even worse and I could no longer boot Android.
5)
I still had bootloader and fastboot though so I followed a guide to restore the tablet to the original OS (which ironically I already downloaded before trying to get TWRP but forgot about and didn't unpack). I set up Intel Platform Tools but the flash process didn't work because it went to droidboot and then lost USB connection. On the Intel program it would just stay stuck at 20% Wiping ESP. It would time out twice and then give me a final error message.
6)
So I thought to explore the flash.xml file provided to see if I could do the steps manually. I knew it was stuck at wipe ESP because in droidboot it couldn't get commands from PC. So I went into fastboot and wiped ESP manually myself! Little did I know how foolish this was to do because I was simply unable to flash the provided ESP.img again. Following this I lost access to the bootloader.
7)
I found a guide to restore a bricked 1050F here on XDA but it needs droidboot which now goes to the command line UI described at the top of this post. When attempting to restore the kitkat BIOS again, droidboot is also needed which results in the same cmd UI.
8)
Which leads me to where I am now which is that the tablet doesn't boot to: normal, recovery, bootloader/fastboot or droidboot. Which is why I am now asking for help. What can I do?
I'm thinking that a partition was corrupt in addition to me wiping the ESP is causing this. Maybe it's possible to completely format and setup all the partitions and start from scratch again? How can I flash esp when all I can get access to is DNX mode?
Thanks for reading this far and if you have any more ideas, please let me know, thanks in advance.
Any help please?
Hi, any help please?
Hi all, would anyone like to chime in?
It would seem an update (I think from 2020)has been floating around the net for a while.
I recently decided to revisit my 1050f after I found a replacement screen to change my original one as it was cracked.
At first everything worked Okay but then the tablet decided to do this update,which has totally messed my pad up.
As I have all the old files on my computer from years back,I thought go the the re-install of everything,no matter what I do from Command lines to using "bios restore tool " and intel lite tool with both the original "kitkat" roms and modified roms,nothing will make my pad work again.
I think Lenovo have deliberately released software to break our pads.
I know all my files are good as I have reloaded them before when I was not happy with some things I did.

Categories

Resources