Related
I recently rooted my kindle fire and installed twrp along with cm7, but I accidently did a factory reset inside cm7 and was stuck on the firefirefire logo, I used an unbrick tool, but that erased all my user data and did not help. I managed to get my boot back to 4000 and install twrp again, but it won't let me mount sd card and will only allow me to mount system.
Sorry Im a noob
Im having the same issue, trying to moun it, but I keep getting
Error mounting /sdcard!
Is there a way to fix it? Im stuck on recovery (CW)
Heres a great idea get off of the discontinued recovery and switch to touch screen clockworkmod recovery its way better when it comes to things like that
Link: http://forum.xda-developers.com/showthread.php?t=1454241
guys this has nothing to do with twrp - it's working fine
just do following:
- boot to twrp
- test adb with "adb devices"
- open shell -> "adb shell"
- issue "echo /dev/block/mmcblk0p12 > /sys/devices/platform/usb_mass_storage/lun0/file"
- now the sdcard should mount to the computer
- windows will probably respond that the volume/device needs formatted before using it
- choose quick format and let it format it as fat32 block size 4096
Thanks b63 for the fast reply. I dont have twrp I have CWM recovery, im trying to install TWRP but I get an error:
error: device not found
Is there another way to install TWRP?
Thanks
i don't know about cwm but i would try to boot to it and test if adb is working
then it should be the same - you only need adb root access
if you have this access with cwm also then there is no need to install twrp
Well if I boot into CWM
I can do adb shell
But then nothing happens
If I let Kindle boot normally (after the Yellow triangle) the screen goes black and I cant adb shell anymore
What im doing wrong or what im missing.
Thanks again
BTW
When I boot int CWM I get this message
E:Can't Mount /cache/recovery/command
stay in your recovery
after the command the sdcard should mount to your computer
check your device manger
follow the first desciption
if you can't get it gimme a pm ...
Wooooot!
Thank you so much b63!!!!I couldnt sleep for this damn problem
In the end this one help me out
echo /dev/block/mmcblk0p12 >> /sys/devices/platform/usb_mass_storage/lun0/file
I dont know why it worked with >> its the same (for this case) but I could finally mount it on windows
Now im back to CM7, really thanks!!!!!
really glad that it worked ...
b63 needs a medal lol.
Sent from my HTC Glacier using xda premium
Thanks b63 I got twrp to mount the sd card, with this:
echo /dev/block/mmcblk0p12 >> /sys/devices/platform/usb_mass_storage/lun0/file
But, when trying to install cm7 I get an error:
E:Cannot load volume /misc!
ignore it - the kf don't have a volume "misc"
Stuck in twrp!!!!
b63 said:
guys this has nothing to do with twrp - it's working fine
just do following:
- boot to twrp
- test adb with "adb devices"
- open shell -> "adb shell"
- issue "echo /dev/block/mmcblk0p12 > /sys/devices/platform/usb_mass_storage/lun0/file"
- now the sdcard should mount to the computer
- windows will probably respond that the volume/device needs formatted before using it
- choose quick format and let it format it as fat32 block size 4096
Click to expand...
Click to collapse
I can get into TWRP, but when I type in ADB DEVICES in command prompt, it says the standard daemon not running, then daemon started successfully. This is followed by List of Devices attached, but it's blank after that.
I used the Kindle Fire Utility to install drivers, and when I use ADB DEVICES Command Prompt with my T-Mo Vibrant, I can get into ADB Shell.
Any advice?
Please note, this isn't mine. I've never owned a Kindle Fire, so I'm banging myself raw with information overload on this type of device. I'm trying to help a co-worker out with his Fire that he borked. I've owned three android phones/tablets and rooted/ROMed all of them, so I follow instructions. So far, I've tried the Kindle Fire Utility and the Kindle Fire Unbrick Utility found in these forums. My co-worker didn't get to the point of making a back-up or installing the Stock Image as an Update.zip. I have the stock image downloaded, and have renamed it, but I can't get it onto the tablet at all. Selecting Mount in TWRP always locks everything up, and there is nothing to Install or Restore. So, like I said, I'm getting bloody here, but no joy.
Any help would be appreciated!
what's the status of the kf ? -> you can get into twrp - that is good - do that
what's the status of the drivers in device manager ? -> which driver loaded ?
what have you/he done/tried to get to this point?
i'm asking to give you the right method ...
b63 said:
what's the status of the kf ? -> you can get into twrp - that is good - do that
what's the status of the drivers in device manager ? -> which driver loaded ?
what have you/he done/tried to get to this point?
i'm asking to give you the right method ...
Click to expand...
Click to collapse
He says he rooted it, installed FireFireFire, and the ICS-ish launcher (name eludes me at this point). Then, it basically boot-looped (Yellow Triangle, then Kindle Fire, back to Yellow Triangle).
My first thought was ADB Shell, but the KF is apparently a stranger animal than most of the other Androids I've dealt with, so it didn't automatically pop up. I installed KFU (Kindle Fire Utility, most recent version), installed the windows drivers (I have Win7 Pro 64-bit) that came with the KFU, and attempted to get it to boot normally, recovery, or anything. Note - A couple of times (like 4 or 5 out of 100), it did make it to a full boot for a few seconds, but would crash within seconds. TWRP was not installed at that point, so I successfully pushed that with the KFU. I also downloaded the stock image, and renamed it. TWRP won't mount the SD card so that my computer can see it, so I'm losing that battle. Also, at some point along the way, the KF started attempting to connect to the PC when plugged in, with the typical USB device connected sound, but two seconds later, it acts like it is unplugged, with that sound. If the KF is visible in the Device Manager, it must be hidden, cuz I can't see it. This was not the case at first, with an Unmount icon for the Kindle being displayed in the notification (right) side of the Windows toolbar. This is in conjunction with the device now booting straight to TWRP, and not even attempting to go the normal boot route. I've also tried a Kindle Fire Unbrick Utility to restore it, with no luck. It wipes the User Data, wipes cache, downloads the update.zip, but can't mount the unit to push the data. I've never been able to get ADB to find the unit.
If I can get the update.zip to the SD root, or if I can ADB shell it, I think I've won. But I'm being blocked on both those counts.
Thanks for being willing to look into this for me!
the problem is the ics launcher - it simply don't work
would recommend to use go launcher instead, for the future
now to the problem:
one solution is to boot to twrp - there is adb root access available
maybe check and update drivers - look here:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
then delete the ics launcher .apk (don't know the exact name) with adb commands
this should make the kf startable again and nothing is lost
an other solution is to flash a new rom but i don't think that this is necessary
and never ever flash the original rom from amazon unless you want to return the device - there is a risk of bricking it and you will loose fff,twrp and root
there are prerooted stock images available for returning to stock rom:
http://forum.xda-developers.com/showpost.php?p=22393194&postcount=20
if you need closer help gimme a pm ...
b63 said:
the problem is the ics launcher - it simply don't work
would recommend to use go launcher instead, for the future
now to the problem:
one solution is to boot to twrp - there is adb root access available
maybe check and update drivers - look here:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
then delete the ics launcher .apk (don't know the exact name) with adb commands
this should make the kf startable again and nothing is lost
an other solution is to flash a new rom but i don't think that this is necessary
and never ever flash the original rom from amazon unless you want to return the device - there is a risk of bricking it and you will loose fff,twrp and root
there are prerooted stock images available for returning to stock rom:
http://forum.xda-developers.com/showpost.php?p=22393194&postcount=20
if you need closer help gimme a pm ...
Click to expand...
Click to collapse
You're giving me a lot of hope. I'll give this a try when I get home tonight, and I'll contact you with any other hurdles. THANK YOU SO MUCH!
halfway there
Ok so I have run the command under the adb shell after adb did detect the device, however when I run the command it says that "non existent directory" What am I missing?
echo /dev/block/mmcblk1p1 > /sys/devices/platform/usb_mass_storage/lun0/file
/sbin/sh: can't create /sys/devices/platform/usb_mass_storage/lun0/file: nonexis
tent directory
Getting that when i try to issue the command,
Any hint?
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
hi people,i wanna share a fix solution for any smartwatch 3 with working fastboot mode...
so,presuming u already have adb drivers installed lets proceed
https://drive.google.com/open?id=0B14BmzmcIZ4cVDBjRnliUDVXU1k is link to a shared folder with all needed files,inside folder are :
repacked rom 5.0.1 - swr50.zip
stock recovery image - swr50.img
twrp recovery image for old rom version - twrp.img
twrp recovery image for new rom version - twrpnew.img
update packages that can also be sideloaded if watch dosent update itself after first flash
updatep-k.zip -its from verison lwx48p tp lwx48k
then k to d and d to lca43(5.1.1)
so,boot into fastboot and fastboot boot twrp.img (that will boot twrp image on watch).then,adb push swr50.zip /sdcard/swr50.zip
in twrp push install and select the newly copied swr50.zip flashable rom...flash it,then adb reboot
let watch reboot,presuming all went fine,ull watch will boot in 5.0.1 rom,let it connect to phone.inside settings,open options/about,and push built version until u get dev mode...in dev mode enable usb debug,confirm also on phone
so right now u have watch connected to pc with usb debug on....write adb reboot bootloader ,so watch goes in fastboot again
now,flash stock recovery...fastboot flash recovery swr50.img (watch will get the stock recovery),after u can fastboot continue
right now u can update watch,connected to phone,via own update ota service,settings/about/system update,it will download and install next version,the update again and again.if u dont wanna wait thatu can adb sideload files i provided,its actualy stock ota update
so....
adb reboot recovery,select adb sideload,and adb sideload updatep-k.zip,reboot watch and let update,then sideload again updatek-d.zip,reboot and let it update,then again last update
AFTER THIS UPDATE TWRP.IMG NO LONGER WORK,DONT BOOT IT,WATCH WILL ENTER BOOT LOOP,WE WILL BOOT TWRPNEW.IMG.....becouse 5.1.1 updated also boot image,so fastboot twrpnew.img if u wanna use twrp in some way.....
i hope its was helpfull,any questions fell free to leave,im no developer,i just like to play with things
BIG thanx to those who packed,repacked flashes and recovery images!!!!
l
alex_SW said:
hi people,i wanna share a fix solution for any smartwatch 3 with working fastboot mode...
so,presuming u already have adb drivers installed lets proceed
https://drive.google.com/open?id=0B14BmzmcIZ4cVDBjRnliUDVXU1k is link to a shared folder with all needed files,inside folder are :
repacked rom 5.0.1 - swr50.zip
stock recovery image - swr50.img
twrp recovery image for old rom version - twrp.img
twrp recovery image for new rom version - twrpnew.img
update packages that can also be sideloaded if watch dosent update itself after first flash
updatep-k.zip -its from verison lwx48p tp lwx48k
then k to d and d to lca43(5.1.1)
so,boot into fastboot and fastboot boot twrp.img (that will boot twrp image on watch).then,adb push swr50.zip /sdcard/swr50.zip
in twrp push install and select the newly copied swr50.zip flashable rom...flash it,then adb reboot
let watch reboot,presuming all went fine,ull watch will boot in 5.0.1 rom,let it connect to phone.inside settings,open options/about,and push built version until u get dev mode...in dev mode enable usb debug,confirm also on phone
so right now u have watch connected to pc with usb debug on....write adb reboot bootloader ,so watch goes in fastboot again
now,flash stock recovery...fastboot flash recovery swr50.img (watch will get the stock recovery),after u can fastboot continue
right now u can update watch,connected to phone,via own update ota service,settings/about/system update,it will download and install next version,the update again and again.if u dont wanna wait thatu can adb sideload files i provided,its actualy stock ota update
so....
adb reboot recovery,select adb sideload,and adb sideload updatep-k.zip,reboot watch and let update,then sideload again updatek-d.zip,reboot and let it update,then again last update
AFTER THIS UPDATE TWRP.IMG NO LONGER WORK,DONT BOOT IT,WATCH WILL ENTER BOOT LOOP,WE WILL BOOT TWRPNEW.IMG.....becouse 5.1.1 updated also boot image,so fastboot twrpnew.img if u wanna use twrp in some way.....
i hope its was helpfull,any questions fell free to leave,im no developer,i just like to play with things
BIG thanx to those who packed,repacked flashes and recovery images!!!!
l
Click to expand...
Click to collapse
Thanks for putting this together. My sw3 has been stuck on the MM dots / symbols for some time. After several attempts of running various roms, img, simg, XC, etc, I could get no further than the original software issue. With your post, I was able to get it to the LCA43 update. Although, for some reason I could not use the twrp.img in your file list (I found another one) and I could not adb the recovery file (I had to flash it), nevertheless, it provided a way for me to update the sw3. I did not flash the updates, but just let the watch do it. While that was a slow process, it was working so I continued...until.
I could not get the MM update to work though. It downloaded and installed on the sw3. But when booting up, I got the dreaded 4 dots / symbols again. If you are still around and have any ideas of updating this procedure to include the MM updates, it would be much appreciated. Again, the XC does not work for me even though both the repair and update options in the software said they were successfully installed.
Hi!
I really need to do this for activate the NFC and use to check glicemia on the watch.
But i'm stuck almost at the first point.
I already activate the adb on the watch and put him "runnig fastboot".
On the pc I write on command prompt "adb reboot bootloader" and returns: "error: device '(null)' not found"
Anyone can helps?
Regards,
Same position as Moitas
Realy would appreciate if somebody could help me and at the same time moitas. I run windows10 and have the same problem. The device is called Tetra when it shows up in fastboot and I can´t get any driver to work with it. Have tried several differet ones but none seem to fit. Any clever one with a solution I would salute you
@moitas @tobas70 you need to install the correct drivers - http://forum.xda-developers.com/attachment.php?attachmentid=2480396
ajolly said:
@moitas @tobas70 you need to install the correct drivers - http://forum.xda-developers.com/attachment.php?attachmentid=2480396
Click to expand...
Click to collapse
Thanks Ajolly! I finally managed to get it done. As new to this rooting buisness there were a lot of steps that where more complicated than the manual I followed applied
Hi! i have problem after downgrade...
After I push SWR50.zip and reboot, my devices is unauthorized. When i enter in fastboot manually there's any devices (null). I install drivers like You said, and form adb, google. If somebody can help me this i will be very grateful
any one can help me. After failed up SW3 by sideload, they ignored PC conncetion. Try "adb devices", fastboot mode, recovery mode, MTP, - anything happend in device manager.
ajolly said:
@moitas @tobas70 you need to install the correct drivers - http://forum.xda-developers.com/attachment.php?attachmentid=2480396
Click to expand...
Click to collapse
I just got a new SWR50 for the sole purpose of using NFC (with FreeStyle Libre).
On the Win10 PC I don't have "Android Device" as a hardware type. -- I'm not sure if this is causing the problem that in Fastboot (white background) I cannot communicate with the watch from the PC anymore.
Also, when turned on for the first time watch automatically upgrades to M1D64T and I don't seem to be able to stop that and don't seem to be able to downgrade to be able to use this package.
Any suggestions? Thanks
Restore to the latest firmware
After downgrading to LCA43, what would be the easiest way to restore the watch to the latest firmware, is there a real factory reset?
Not pair after downgrade
I have downgraded from version M1D64T to LWX48P and now my phone do not see the watch in bluetooth devices. I tried few things to start BT working like:
- remove Android Wear from phone
- clear Google Play Services
- send few intent through adb like bluetooth.REQUEST_DISCOVERABLE
- return to M1D64T by Sony PC Companion
Bluetooth still not works and I cannot connect to any phone.
Maybe somebody have an idea how to repair my watch?
Ok, I've got another issue when downgrading the watch.
When I get to the Install the swr50.zip it starts to complain.
It says, Unable to mount /cache, Unable to mount data and so on. So clearly something is not going right at this point (or earlier more likely).
What's going wrong and how do I fix it?
Same thing here - /data can't be mounted read/write
I'm seeing the same thing. I can use "adb shell" and "mount -r /data" (readonly) which works, but when I try to mount it normally ("mount /data") I get an error about a bad argument. This is certainly related to the errors re. not being able to mount /data, which I see when I try using twrpnew.img to install the SWR50.zip image.
I'm stuck!
Maybe a solution...
(I'm still going through applying updates, but this looks hopeful!)
I found that apparently the "unable to mount data" seems to have to do with the /data partition (in my case, "/dev/block/mmcblk0p32") having some internal flag which seemed to not allow it to be mounted read/write. I could do "adb shell" to get to the watch and then to "mount -r /data" and that worked just fine. I decided to rebuild the entire /data partition. Use "adb shell" to get a shell prompt on the watch, do "mount" to make sure /data is NOT mounted. If it is, do "umount /data", which should unmount it. you can see what's being mounted where via "cat /etc/fstab". You want to rebuild the disk partition which will be mounted on /data. On my watch this was "/dev/block/mmcblk0p32", so "/sbin/make_ext4fs /dev/block/mmcblk0p32". Then "exit" to get back to your system where you're running adb.
So, I followed the "How to install NFC on Sony Smartwatch3" instructions (I'm not allowed to post a link or else I would, but you probably have these instructions already.)
(I'm doing the "downgrade" part of the instructions, which is where the "install" failed.)
Just after "fastboot boot twrpnew.img", I inserted the above work to rebuild the /data partition. DO NOT mount /data after having rebuilt it! You should also should see that /cache is NOT mounted at this time. Do "exit" to get back to your adb system and continue following instructions at "adb push SWR50.zip /sdcard/", and the "install" worked for me after this!
frippegubben said:
Ok, I've got another issue when downgrading the watch.
When I get to the Install the swr50.zip it starts to complain.
It says, Unable to mount /cache, Unable to mount data and so on. So clearly something is not going right at this point (or earlier more likely).
What's going wrong and how do I fix it?
Click to expand...
Click to collapse
Sony Smartwatch SWR50 unable to install SWR50.zip
Hello Friends,
Iam trying to configure NFC on my Sony Smart Watch 3. After command adb push SWR50.zip /sdcard/, I try to intall SWR50.zip, It's not flashing.
It says Failed with message " UNABLE TO MOUNT" etc
Can you kindly help please
KIR71 said:
Hello Friends,
Iam trying to configure NFC on my Sony Smart Watch 3. After command adb push SWR50.zip /sdcard/, I try to intall SWR50.zip, It's not flashing.
It says Failed with message " UNABLE TO MOUNT" etc
Can you kindly help please
Click to expand...
Click to collapse
I was working with a Sony Smartwatch 3 a few years ago (using the NFC to read a Blood Glucose sensor) and encountered this same error during installation of some of the code. Here are my notes on the solution, in case it helps:
I found that apparently the "unable to mount data" seems to have to do with the /data partition (in my case, "/dev/block/mmcblk0p32") having some internal flag which seemed to not allow it to be mounted read/write. I could do "adb shell" to get to the watch and then to "mount -r /data" and that worked just fine. I decided to rebuild the entire /data partition. Use "adb shell" to get a shell prompt on the watch, do "mount" to make sure /data is NOT mounted. If it is, do "umount /data", which should unmount it. you can see what's being mounted where via "cat /etc/fstab". You want to rebuild the disk partition which will be mounted on /data. On my watch this was "/dev/block/mmcblk0p32", so "/sbin/make_ext4fs /dev/block/mmcblk0p32". Then "exit" to get back to your system where you're running adb.
Hope this helps! Good luck!
Thank you for this tutorial, I'm having the same problem. My swr50 stuck on the dots screen after battery replacement. I tried to follow the steps above but my system does not see the device at all.
I tried to add legacy device drivers but it come back with code 10.
After connecting swr50 device manager don't detect any device and I can't install drivers. So when I run ADB I get message "device null" Did someone had the same problem? Is there any solution?
Help please, When I plug in my watch to the charger sometimes it gets stuck on sony logo and sometimes doesn't display anything also tried connecting to pc but it keeps on booting also tried pressing the power key to get into the fastboot mode but doesn't work.
When I boot to twrp in recovery, I am unable to accomplish anything -- wipe or install. When I try to do either I get an error about "unable to mount sdcard". I have seen this thread, but cannot find the zip mentioned anywhere. I am able to run "adb push" to /sdcard and then to actually see the file pushed there in twrp recovery. I'm just not able to do anything with the pushed file in the install function.
Tried mounting with adb shell, but kept getting error of "Invalid argument". Did discover that /sdcard is /dev/block/mmcblk0p36, and using fdisk in adb shell found that it "doesn't contain a valid partition table". I'm not concerned about losing data. Everything was backed up, but anybody know how to create the correct partition table so I can install a ROM?
Original post:
So I screwed up. I rooted my phone according to this post. Unfortunately I then did something stupid when trying to flash a new recovery and get actual SU privileges to remove bloatware. Instead of going back to the first page in that thread and seeing the links to use there, I followed this guide. Unfortunately, when I ran the script, install-insecure-linux.sh, it flashed the boot.insecure.img and then spit out errors related to incompatibility with the ncurses version on my laptop. It seems difficult if not impossible to downgrade the ncurses without causing a ton of other headaches. It went to reboot and just stayed dead.
Thought I was hosed, but then after charging for a while I got signs of life. Managed to boot to fastboot. Connected back up to the laptop and decided to follow the cyanogenmod guide for installing CM11. Flashed the CM recovery img file successfully but after rebooting I can't do anything.
I still occasionally get into the fastboot on the phone. Running fastboot devices on the laptop lists the phone. Running adb devices does not. Running any other fastboot command sticks at either nothing or <waiting for device>. Running any adb command gives "error: Device not found". I added a udev rule and adb_usb.ini with the device id "0bb4" and mode 0666, but no joy.
I only have a linux machine available at the moment, so I'd prefer suggestions for working in linux. If someone knows of a good Windows solution, I can probably try that in a few days. Thanks in advance.
EDIT: Progress
Noticed that for a second when I first connect to the laptop USB the fastboot menu showed in red FASTBOOT USB before going back to just FASTBOOT. Managed to tee up the command for flashing the twrp recovery img and ran it immediately upon plugging in. Was then able to boot to recovery. Not sure what my next step to getting a working phone is though. Help still appreciated.
My last post got swallowed by the ether I guess. I was able to fix it by formatting the sdcard using mkdosfs -F 32 -n INT_SD -s 64 /dev/block/mmcblk0p36. Then rebooting, wiping, and installing CM11. All is good again.
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