Nexus 7 WiFI 2013 (Razor, FLO) CyanogenMod Recovery only... - Nexus 7 (2013) Q&A

I have a nexus 7 WIFI 2013 (Razor, Flo):
I was trying to get a copy of Nethunter or Kali linux installed on here. I was running CyanogenMod nightly's
Well during one install, I must of wiped the whole tablet clean. It only had dad/media and then subs /0, /obb folders. I'm unable to find any images on the card and nothing else is displayed. I have tried number numerous drivers for my Samsung laptop but when i use my surface it shows nexus 7 and also when i go into bootloader mode it will also show the driver.
I installed droid SDK and also minimal adb and fast boot. I'm unable to push anything to this device. When i run adb devices it shows the device but says unauthorized. I try adb kill-server and adb start-server and still no dice.
I'm looking for any input as to how I can push and image onto this device. I realize I will have to go back to factory and I have all them images. I just cant get it adb authorized yet.
this will only go into recovery mode and boot loader mode. There is no OS if I let it boot it just shows the mod logo and will sit there until the battery dies.
Does anyone have any input on how to get this authorized so I can push files to it. I'm unable to get on the screen and ok the RSA fingerprint and I think that maybe part of my hold up or why it shows unauthorized.
Thanks in advance for all or any input or ideas.

Start TWRP and it will authorize you to push any files anywhere.

I'm unable to get TWRP on this tablet. The main issue is I only have cyodgen mod recovery on the tablet. It will not boot. It will only go into recovery mode/bootloader mode. I'm unable to verify any RSA fingerprints which is causing me an issue getting the tablet authorized for ADB pushes. Does anyone know a way I can get it authorized via ADB without being able to access anything other then recovery mode? I think the RSA fingerprint is whats actually causing me an issue.

cletisvandamm said:
I'm unable to get TWRP on this tablet.
....
I think the RSA fingerprint is whats actually causing me an issue.
Click to expand...
Click to collapse
No need to flash TWRP - just start it directly from RAM:
download twrp-3.0.2-0-flo.img to your folder with fastboot and adb apps
boot the Nexus in fastboot mode (when off press power+vol.dn), connect it to your PC
on PC run: fastboot boot twrp-3.0.2-0-flo.img
when TWRP is up, ADB-push your files, no RSA concerns

Related

[Q] Bricked KF2 - no OS, fastboot & TWRP available

I've read through hundreds of similar threads and haven't been able to find a solution - I'll gladly give up my firstborn (and/or make a paypal donation) to anyone who is able to help solve my issue!!
From my research, I seem to have no OS installed on the Kindle, and as far as I can tell, I'm booting into fastboot mode (screen hangs on the blue/white Kindle Fire logo, screen does not ever dim). I AM able to access TWRP Recovery, but don't have any backup to load from, am unable to successfully flash the ROM that I have saved to my SD card. My device manager recognizes the Kindle as a Kindle Fire (Android ADB Interface), no yellow triangles. Typing ADB Devices into Command Prompt gets me: [device number ] offline. Typing fastboot devices into Command Prompt gets me nothing (blank line).
Background/How I 'Bricked' It: I have a Kindle Fire 2 and was able to successfully unroot/flash Cyanogenmod 10 onto it. Worked perfectly for about 6 months, when I decided that it would be a good idea to flash back to stock so that I could give it to a relative. I have TWRP 2.3.3.0, so I used a guide on xda to do the following:
I used a guide from xda and followed these instructions
-Download latest KF2 stock software from amazon. Re-name the file to update.zip
-Moved it to the root of the SD card
-Booted in to TWRP
-Factory Wipe/Restore
-Wiped Cache
-Wiped Dalvik Cache
-Wiped System
-Installed the "update.zip"
-Wiped cache/dalvik again
-Rebooted
Unfortunately, wiping the system seems to have wiped the CM10 OS (ROM) that I had installed, and there was a failure in installing the amazon stock:
Installing '/sdcard/download/update.zip...
assert failed: is_substring ("Otter2 , file_getstring("/proc/product_name"))
E: Error in /sdcard/download/update.zip
(Status 7)
Error flashing zip '/sdcard/download/update.zip'
Updating partition details...
Trying to reboot the system from TWRP results in a message that states: "No OS installed! Are you sure you wish to reboot?"
Investigating using ADB: So it looks like I have no OS on the Kindle Fire 2. This seems to be a problem because without an OS, I am unable to use adb (from what I've read, no OS = no way to accept/authenticate the computer RSA fingerprint to whitelist the kindle and allow adb to function). Trying to use KFU, KFFirstAide, or the Kindle UnBrick Utility results in Error: Device offline or Error: Device not found types of messages (I am assuming due to the fact that I can't "turn" adb on by accepting the RSA fingerprint prompt)
What does Device Manager tell me? My computer can 'see' the Kindle Fire in device manager [as I stated earlier: My device manager recognizes the Kindle as a Kindle Fire (Android ADB Interface), no yellow triangles] but going to My Computer and looking under mass storage devices, the computer doesn't seem to recognize the device as a USB storage device, which is a problem because I can't drag/drop or push/pull files to the SD card so I can't try to flash anything *other* than the original file that failed.
Fastboot Mode...? From what I can tell (http://forum.xda-developers.com/showthread.php?t=1668159), my device is in fastboot mode. My Kindle screen hangs on the blue/white Kindle Fire logo screen, which from what I understand is hashcode's bootloader/fastboot screen. However, when I look at the Hardware IDs in the device manager, it tells me that my hardware IDs are:
USB\VID_1949&PID_0006&REV_0216
USB\VID_1949&PID_0006
So...my kindle seems to be stuck on the blue/white fastboot screen, but register on my computer as the stock kindle fastboot? I'm not really sure what's going on there, and couldn't find too many people with the same discrepancy that I have...
I tried plugging in my cord (making sure to use a USB 2.0 port), going into Command Prompt and using some fastboot commands. (ie: fastboot flash bootloader \path\update.zip) but all I get is a <waiting for device> for a LONG time. As in, a few hours. Some basic googling/investigation seems to indicate that I don't have fastboot drivers installed, OR that I wasn't running fastboot in an 'elevated mode' but I haven't been able to find too many details about how to fix those, IF that is the problem.
TWRP 2.3.3.0: I can get into TWRP recovery just fine, although I can't seem to figure out how to get files onto my device. So I've tried re-installing the original update.zip file that failed the first time several times, with no success. trying to 'Mount' the device doesn't seem to do anything (at least, my computer doesn't see the device as USB storage regardless of whether it's mounted or not) I tried using Advanced --> ADB Sideload, but trying to send the file in Command Prompt using the adb sideload <filename> command just gets me an Error: Device not Found message. I thought maybe I could try Advanced --> Terminal Command, but have no idea how to do that or what it does, and most sites are very vague about the step-by-step details, so I didn't really touch it.
Not sure if this is relevant or not, but when my KF2 is plugged into (attached) to my computer with the cord and is in TWRP, device manager shows the device under 'Other Devices' --> Amazon Kindle Fire2, and there is a yellow triangle on it. Not sure why...going back to 'fastboot' mode gets rid of yellow triangles and is recognized as a Kindle Fire again.
At this point - I'm pretty much stumped and have (hopefully) demonstrated that I've done my best to do my own research/read through threads/done due diligence. Is there anyone out there that might have any suggestions? Or do I now have a very large paperweight?
ANY input/suggestions/encouragement is welcome! I absolutely and sincerely appreciate your time in reading through this thread and trying to help noobs like me!
Use fast boot mode to recover to stock: http://forum.xda-developers.com/showthread.php?t=2096888
Or
If you have access to twrp. Use the ADb sideload feature to push CyanogenMod or another ROM over.
One thing though- if you can boot into TWRP you didn't wipe the system partition. Twrp for kf2 requires a file named stack to be there.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
...tried those, but maybe am doing them incorrectly?
mindmajick said:
Use fast boot mode to recover to stock: http://forum.xda-developers.com/showthread.php?t=2096888
Or
If you have access to twrp. Use the ADb sideload feature to push CyanogenMod or another ROM over.
One thing though- if you can boot into TWRP you didn't wipe the system partition. Twrp for kf2 requires a file named stack to be there.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Trying to use the ADB sideload feature to push CM or another ROM over doesn't seem to be working for me (unless I'm doing it wrong?)
I tried using Advanced --> ADB Sideload, but trying to send the file in Command Prompt using the "adb sideload C:\users\Name\update.zip command just gets me an Error: Device not Found message". Could I be using the command incorrectly?
Trying to use any fastboot command in Windows Command Prompt results in <waiting for device> to hang for hours, with no changes to command prompt and no changes to the kindle (still sits at the blue/white boot logo).
Ah. Sorry. Missed that in the OP.
Sounds like you probably need the drivers installed.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Fastboot Drivers
mindmajick said:
Ah. Sorry. Missed that in the OP.
Sounds like you probably need the drivers installed.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Are there difference drivers for fastboot and adb? I don't get a 'yellow triangle' and my device manager identifies the device as a Kindle Fire [Android ADB Interface], so I thought I was okay.
Should I be looking for fastboot drivers?
And btw, thanks so much for your willingness to help and input!
ME TOO
Just purchased a KF from someone...thay had rooted it...I tried to unroot...got stuck...now mine is doing the same as yours. I hope someone has a fix for you as I too have a large paperweight.
Follow Up
tessa33 said:
I've read through hundreds of similar threads and haven't been able to find a solution - I'll gladly give up my firstborn (and/or make a paypal donation) to anyone who is able to help solve my issue!!
From my research, I seem to have no OS installed on the Kindle, and as far as I can tell, I'm booting into fastboot mode (screen hangs on the blue/white Kindle Fire logo, screen does not ever dim). I AM able to access TWRP Recovery, but don't have any backup to load from, am unable to successfully flash the ROM that I have saved to my SD card. My device manager recognizes the Kindle as a Kindle Fire (Android ADB Interface), no yellow triangles. Typing ADB Devices into Command Prompt gets me: [device number ] offline. Typing fastboot devices into Command Prompt gets me nothing (blank line).
Click to expand...
Click to collapse
tessa33,
I just sent you a response. Call me at 707-774-5923 when you have a moment.
Solution?
I figured I could post in this thread before staring my own because I am having a very similar issue trying to revert my Kindle Fire 2 back to stock from cyanogen so I can sell it. I downloaded the official software from Amazon but every time I try to flash it through TWRP I get the exact same error you were getting. Did anyone ever figure out how to resolve the issue for you?
Had the same problem, so I chatted with an Amazon associate, told him I turned it on one day and it showed the grey triangle and he sent me a new Kindle Fire 2nd Gen for free. Try that...
Sent from my iPhone using Tapatalk
Hello
I have rooted KF2 and I did factory reset I lost TWRP&Os I can see the device as ADB device, Howeverm when the device in fastboot the pc not recognize it.
issuing fastboot devices command return nothing.
I used ubuntu and windows still the same issue. any idea?

How to transfer a zip on my sdcard without adbsideload

I everyone,
I need your help, I tried to install a new rom (AICP : this one) , and somehow forgot to do a backup.
When I boot I only get the swirling logo, never get to fully load.
The phone is not bricked, I can still access the bootloader / fastboot and my recovery, so I could simply flash another rom... but I can't figure how to get the zip file on the /sdcard.
I can't use adb sideload or push, I have HTC sync and android sdk installed, I have no problem to use fastboot commands, so I guess I don't have any driver problem, but adb devices never shows my phone (Tried while off, booted on bootloader, on fastboot, and on recovery, never shows up when I try adb devices)
On windows I get a driver error when plugging my phone while in recovery, but I don't find how to install it.
So... is there a way to mount the /sdcard/ as an external drive in windows or ubuntu ? Or do you have a workaround for adb ?
Thanks a lot !
Vincent

V810 Bricked - ADB unauthorized - sideload only

So I thought TWRP was not right for CM so as a dumbass I got a cm-12.1-20160228-NIGHTLY-v500-recovery.img
Wiped the device completely and executed:
dd if=/sdcard/cm.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Now, all I can do is boot to CM recovery.
Adb is unauthorized so can't push pull or adb shell
Cant load bootloader (just stuck on LG)
LG Mobile Tool won't recognize ****
From CM recovery, the system cant mount anything...
Only Apply Update from ADB, takes adb to sideload mode
Tried to sideload anything, it wont work as system cant mount anything.
Please HELP!!!!
In Windows Device Manager, does it list your device as QHSUSB_BULK? If so, Google that and you should find directions to recover.
Might be in the modern or ports section.
If not, I don't know what else to suggest.

Unbootable Nexus 7

I bought a used nexus 7 off Amazon for a decent price. It's in great condition, looks brand new. The problem is I can't get it to boot up. It goes to a black screen after the boot animation and stays frozen until I reboot. The bootloader was already unlocked when I got it which leads me to believe whoever had it before me was either trying to fix it or screwed it up.
I've tried flashing several different stock os of varying versions via nexus root toolkit v2.1.4 by WugFresh. I can get custom recovery installed, boot into fastboot, and the flashing process seems to work fine until it tries booting up.
It is the 2013 wifi Nexus 7, built in May 2015 which means it's original os and build are 5.1.1 and LMY48G. Not sure that matters too much but I did some research.
Some people with similar issues are saying it's a bad logic board and isn't worth repair but I'd like to explore all other options before giving up.
Any suggestions? Thanks in advance.
Sent from my SCH-I545 using Tapatalk
Let's see the hardware log:
download twrp-3.0.2-0-flo.img from https://dl.twrp.me/flo/ to your folder with fastboot and adb apps
boot the Nexus in fastboot mode, connect it to your PC
PC run: fastboot boot twrp-3.0.2-0-flo.img
when TWRP is up, run: adb shell dmesg > dmesg.txt
you will find dmesg.txt in your adb folder, zip and attach it to your next post
k23m said:
Let's see the hardware log:
download twrp-3.0.2-0-flo.img from https://dl.twrp.me/flo/ to your folder with fastboot and adb apps
boot the Nexus in fastboot mode, connect it to your PC
PC run: fastboot boot twrp-3.0.2-0-flo.img
when TWRP is up, run: adb shell dmesg > dmesg.txt
you will find dmesg.txt in your adb folder, zip and attach it to your next post
Click to expand...
Click to collapse
It says
error: device 'null' not found
My device is booted into twrp via the method you said and is plugged into my pc
dduncan55330 said:
It says
error: device 'null' not found
My device is booted into twrp via the method you said and is plugged into my pc
Click to expand...
Click to collapse
Check the driver and verify PC connection. As you use WugFresh, then run the commands from WugFresh/data folder.
Option #2
download data.zip to a flash drive
connect the flash drive to your N7 with OTG adapter
boot twrp
go: install/select-storage/usb-otg/data.zip/flash
data.tgz will be saved on the flash drive
attach data.tgz here
Flash by recovery: https://www.apkmirror.com/apk/chainfire/supersu/supersu-2-65-release/supersu-2-65-android-apk-download/

LG Nexus 5X V7.1.2 B/N: N2G47Z ( No Command No Custom Recovery )

Files Installed:
1.) Android SDK ( Android Studio ) for ADB Purposes
2.) SR3-SuperSU-v2.79-SR3-20170114223742 ( Which I have not been able to drop into root directory. Just the Internal Shared Storage
3.) twrp-3.1.1-0-bullhead.img ( Click Link For Source Download )
Alright,
I have tried flashing TWRP onto my Nexus 5X and can't seem to make this happen.
When I open up ADB from right clicking in my "platform-tools" folder and selecting "Open command window here", I start by putting my phone into the bootloader mode by typing the command, "adb reboot bootlader". I have to do this due to my volume down button not responding anymore. This should NOT prevent me from navigating any menus located inside the TWRP recovery menu as well as the default recovery screen. If I just use the Volume Up to go through the menus, it loops.
Ok, now, if I am in the bootloader, I want to type the following command into my ADB. That command would be the following:
fastboot flash reboot twrp-3.1.1-0-bullhead.img and/or
fastboot flash twrp-3.1.1-0-bullhead.img
When I do this, the only response I get from the ADB is, <Waiting for any device>...
So yeah..It just sits there and doesn't do anything.
When I am booted into the phone and I type the following command:
adb devices
I get the appropriate response back which is the hex output of the device. I can also make this output happen via, "Recovery Mode ( ADB Sideload )
I understand that ADB and Fastboot are 2 different territories when it comes to inputting/outputting data. On the ADB side, things seem to work as they should. On the Fastboot side, I don't have any recognition from the device itself.
CWM is not available from my understanding when it comes to the Nexus 5X on 7.1.2. I have looked and looked and could not figure out how to make that happen. However, I did see that TWRP works just fine one numerous Nexus devices so there really shouldn't be any issues flashing my device.
I have unlocked the bootloader and it is ready to be flashed with the TWRP custom recovery. I just can't seem to get it to flash as of right now and the recovery menu gives me a message saying, . I have been able to get past this, "No Command" error by simply holding the power button while simultaneously pressing the volume up button to enter the default recovery screen.
There is no option that says Flash from SD Card. Speaking of SD Card, this Nexus 5X doesn't even have a spot for an SD card so therefore a SD Card does not exist for this phone. How do you tell a phone to mount a drive that doesn't exist? Still confused about this as I have also tried to access the root folder so I can drop the SuperSU file into.
That should wrap up the issues I am having. Once again, I'm simply just trying to root this Nexus 5X on the latest android version 7.1.2. Any help to get this moving along would be greatly appreciated!
Thanks guys!
DarkXShadowX21 said:
Files Installed:
1.) Android SDK ( Android Studio ) for ADB Purposes
2.) SR3-SuperSU-v2.79-SR3-20170114223742 ( Which I have not been able to drop into root directory. Just the Internal Shared Storage
3.) twrp-3.1.1-0-bullhead.img ( Click Link For Source Download )
Alright,
I have tried flashing TWRP onto my Nexus 5X and can't seem to make this happen.
When I open up ADB from right clicking in my "platform-tools" folder and selecting "Open command window here", I start by putting my phone into the bootloader mode by typing the command, "adb reboot bootlader". I have to do this due to my volume down button not responding anymore. This should NOT prevent me from navigating any menus located inside the TWRP recovery menu as well as the default recovery screen. If I just use the Volume Up to go through the menus, it loops.
Ok, now, if I am in the bootloader, I want to type the following command into my ADB. That command would be the following:
fastboot flash reboot twrp-3.1.1-0-bullhead.img and/or
fastboot flash twrp-3.1.1-0-bullhead.img
When I do this, the only response I get from the ADB is, <Waiting for any device>...
So yeah..It just sits there and doesn't do anything.
When I am booted into the phone and I type the following command:
adb devices
I get the appropriate response back which is the hex output of the device. I can also make this output happen via, "Recovery Mode ( ADB Sideload )
I understand that ADB and Fastboot are 2 different territories when it comes to inputting/outputting data. On the ADB side, things seem to work as they should. On the Fastboot side, I don't have any recognition from the device itself.
CWM is not available from my understanding when it comes to the Nexus 5X on 7.1.2. I have looked and looked and could not figure out how to make that happen. However, I did see that TWRP works just fine one numerous Nexus devices so there really shouldn't be any issues flashing my device.
I have unlocked the bootloader and it is ready to be flashed with the TWRP custom recovery. I just can't seem to get it to flash as of right now and the recovery menu gives me a message saying, . I have been able to get past this, "No Command" error by simply holding the power button while simultaneously pressing the volume up button to enter the default recovery screen.
There is no option that says Flash from SD Card. Speaking of SD Card, this Nexus 5X doesn't even have a spot for an SD card so therefore a SD Card does not exist for this phone. How do you tell a phone to mount a drive that doesn't exist? Still confused about this as I have also tried to access the root folder so I can drop the SuperSU file into.
That should wrap up the issues I am having. Once again, I'm simply just trying to root this Nexus 5X on the latest android version 7.1.2. Any help to get this moving along would be greatly appreciated!
Thanks guys!
Click to expand...
Click to collapse
That's because you are entering commands that do not exist.
To temporarily live boot TWRP, enter the following. TWRP resets back to stock recovery after a reboot:
fastboot boot twrp-3.1.1-0-bullhead.img
To actually flash TWRP, enter the following. Flash root to keep TWRP if desired:
fastboot flash recovery twrp-3.1.1-0-bullhead.img
I use "ADB push" to transfer files from my MacBook to my 5X. You should be able to do this in TWRP. FYI, I transfer files to /sdcard since I usually intend to use it on the device. If I were using Windows, I believe this is the exact command to transfer files:
adb push filename /sdcard/Download
Sent from my Nexus 5X using Tapatalk
In you shoes, I would try Wugsfresh NRT. That thing helped me several times in the past. Its very straightforward and user-friendly and everything is well explained there. Take your time.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
That's because you are entering commands that do not exist.
To temporarily live boot TWRP, enter the following. TWRP resets back to stock recovery after a reboot:
fastboot boot twrp-3.1.1-0-bullhead.img
To actually flash TWRP, enter the following. Flash root to keep TWRP if desired:
fastboot flash recovery twrp-3.1.1-0-bullhead.img
I use "ADB push" to transfer files from my MacBook to my 5X. You should be able to do this in TWRP. FYI, I transfer files to /sdcard since I usually intend to use it on the device. If I were using Windows, I believe this is the exact command to transfer files:
adb push filename /sdcard/Download
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
jugoslavpetrovic said:
In you shoes, I would try Wugsfresh NRT. That thing helped me several times in the past. Its very straightforward and user-friendly and everything is well explained there. Take your time.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thank you guys for the help! I successfully rooted my Nexus 5X! It's time to go exploring into the roots! :good:

Categories

Resources