Soo after spending hours doing a lot of research i seem to be stuck trying to retrieve some files and data from my nexus 6p (my screen is broken and unresponsive soo i cannot click usb mass storage or fully unlock or i guess decrypt) . My bootloader is unlocked and I am running twrp recovery menu. Its rooted with supersu and I am currently trying to mount my internal storage or sdcard (same thing) using adb and adb shell. From my understanding my internal data should be in /sdcard, data, or in the partition /dev/block/mmcblk0 . I am never able to mount it since it seems to be busy. adb seems to be running in root and the shell seems to be running in root as well but i can't seem to access my internal storage. Any more help or advice would be greatly appreciated. I also apologize in advance if this isn't the right place for this post .
Do your buttons still work? Can you boot into recovery, and mount that way?
My buttons still works. Im able to boot into fastboot mode and im pretty sure recovery as well if im able to connect to my device with adb.
edit: Im pretty sure im getting stuck somehow by the default encryption of the nexus 6p and i can't think of a way that i will be able to decrypt . i don't even think i will be able to enable ums.
This may not be what you're looking for but you could try using dd if available and pull the system, data, and sdcard partitions off of your device.
Then you could theoretically flash those onto another 6p, decrypt, and retrieve you files.
I have to say be careful when using dd because its a powerful tool that can easily brick you device.
Thinking about it a bit more made me realize you need a otg cable and some sort of USB drive for that to work. And I'm not sure if twrp auto mounts USB otg drives
Sent from my Nexus 6P using Tapatalk
superchilpil said:
This may not be what you're looking for but you could try using dd if available and pull the system, data, and sdcard partitions off of your device.
Then you could theoretically flash those onto another 6p, decrypt, and retrieve you files.
I have to say be careful when using dd because its a powerful tool that can easily brick you device.
Thinking about it a bit more made me realize you need a otg cable and some sort of USB drive for that to work. And I'm not sure if twrp auto mounts USB otg drives
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Soo far every attempt at getting Ums to pop up or to gain access to any form of data trough usb (otg cable) have seem to fail and trying to use the adb pull command ends with the error (0 files pulled and 0 files skipped) which i would assume is because I don't have the right permissions for those directories which is odd since im rooted and I am running everything in root has well. Since i can't see the screen i can only assume that i am in some form of recovery mode and not just the twrp one if i am able to connect to it trough adb but not UMS( pops up on my windows pc has mtp).
If you're booted into recovery and twrp successfully decrypted it then you should have no issues.
Try to get to the bootloader and flash the latest twrp then boot back into twrp and see if it let's you.
Sent from my Nexus 6P using Tapatalk
superchilpil said:
If you're booted into recovery and twrp successfully decrypted it then you should have no issues.
Try to get to the bootloader and flash the latest twrp then boot back into twrp and see if it let's you.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I have the latest twrp recovery (3.0.2-0) and im able to adb pull the default.prop but I still can't seem to mount any of the internal storage directories. I retrieve the error failed invalid argument when trying to run the adb shell command "mount /dev/block/mmcblk0p44 /emmc" btw emmc is a random dir i made. Same think happens when I try to mount /sdcard or /data/media. Right now I'm trying to Use DD if of has you suggested but the data partition would be to big to create on my device so i would need a way to write it directly to my windows system . I've been trying to follow this guide https://www.packtpub.com/books/content/extracting-data-physically-dd
Once you boot into recovery, doesn't the phone show up on you computer as a drive? Just grab the files that way.
spotmark said:
Once you boot into recovery, doesn't the phone show up on you computer as a drive? Just grab the files that way.
Click to expand...
Click to collapse
No It does not show as a drive. I remember having to swiping my passcode on my device in twrp recovery or even on any initial boots in order to decrypt my drive. I am assuming this is the reason why I cannot see the contents of these directories trough the adb shell. I can see see and adb pull from system and most other directories.
You know what I think my internal drive got wiped somehow and that is why nothing is popping up it is the only explanation i can come up with. I give up.
Edit: So I just got my replacement unit , same make and model nexus 6p with the same set up, rooted ,twrp, and encryption. And it turns out If you do not decrypt your disk, you will not be able to mount or access any data on the internal sdcard. So now my question is, is there a method where Ill be able to send a command or modify a file to decrypt the data on the fly since my screen doesnt work nor respond to be able to mount the disk ?
Is it possible to send commands or modify the command "cryptfs checkpw" to "vold" true adb or would i need to write some app or script? Cause i would be able to do any of the above if the action is actually feasible. Also i apologize if double posting is not allowed.
edit: source of information on encryption can be found here https://source.android.com/security/encryption/
Plug it into a tv to see the screen, and try to use a wired mouse to toggle what you need. It may take some tinkering
Sent from my Nexus 6P using Tapatalk
kyuubie said:
No It does not show as a drive. I remember having to swiping my passcode on my device in twrp recovery or even on any initial boots in order to decrypt my drive. I am assuming this is the reason why I cannot see the contents of these directories trough the adb shell. I can see see and adb pull from system and most other directories.
You know what I think my internal drive got wiped somehow and that is why nothing is popping up it is the only explanation i can come up with. I give up.
Edit: So I just got my replacement unit , same make and model nexus 6p with the same set up, rooted ,twrp, and encryption. And it turns out If you do not decrypt your disk, you will not be able to mount or access any data on the internal sdcard. So now my question is, is there a method where Ill be able to send a command or modify a file to decrypt the data on the fly since my screen doesnt work nor respond to be able to mount the disk ?
Click to expand...
Click to collapse
There's a method of removing pins/patterns/passcode from the device, but I do not know if this would allow TWRP to decrypt the internal storage partition automatically. If I remember correctly from my last nandroid restore where I didn't remove the security, after using this method, when Android boots it goes directly to the unlocked homescreen. Whether or not this is decrypted, or whether ADB can access it, is another matter entirely.
Use at your own risk. I'm not responsible for you breaking your stuff. http://www.howtogeek.com/240657/how-to-fix-pin-errors-after-restoring-from-twrp-android-backups/
tcollum said:
Plug it into a tv to see the screen, and try to use a wired mouse to toggle what you need. It may take some tinkering
Click to expand...
Click to collapse
Probably you already know that it's not possible to connect 6p to TV with HDMI cable (I've tested this myself in the past).
My 6p dropped on the ground smashing screen and then spent few weeks in the drawer. Now I'm trying to recover files from internal memory using external wired keyboard via OTG to type in password (I've set fingerprint protection on, which always requires password after each reboot), but when I connect my phone to PC then it doesn't show any content on it (Nexus 6p appears in Windows Explorer, but doesn't show any files). It looks like my Nexus is still locked. I can't really remember now if password prompt appears straight after rebooting (so I could simply connect keyboard, type in password and press ENTER) or it requires to press something first (slide the screen or so)? Can someone please check and describe full sequence, best with connected external keyboard?
Related
I really need some help please! I think I may have done something very bad. I have a tmobile mytouch 3g. I was trying to update from cyanogenmod 4.2.1.9. I was using a darkstar theme from ringer nation.
Here’s where I think i screwed myself. I am fairly new to all this stuff so I was trying to find a guide on how to update the mod and instead of doing it properly by adding the files to the sd card, doing a wipe, and then installing everything. I instead messed up and did an install of sapping.nbh and basically followed all the directions to originally root the phone. Including formatting the sd card and everything. When I realized that i was doing this all wrong I was still able to load my os and everything seemed ok. I was getting a sd card error that said that the card was blank or had an unsupported file system, but I was able to mount it so, I erased everything off the card and then put the cyanogen update and the drc83_base file and attempted to load into recovery and do the update.
I loaded into and did a wipe. I attempted to follow the instructions on upgrading from the cyogen page. (God I wish I had found that page first) But after I did the wipe and I attempt to Apply any from SD I get “error: sd card is not mounted”
When I attempt to reboot the phone it goes to the tmobile mytouch logo, THEN it goes to my them logo from Ringer Nation, then it just goes to a black screen I let it sit there for like 5 minutes to see what would happen, but nothing. So I took out the battery and sim. I can get into recovery though so I hope that someone can help me figure out where to go from there.I thought that since I had done a wipe that the theme would have been deleted as well? This is weird.
I did do a nandroid backup before. Hopefully that will prove to be helpful. Sorry for the long post, but I wanted to dump as much useful information about this problem so that hopefully someone will be able to help! BTW I'm using a mac with the latest snow leopard software.
As I am desperate for help, please reach out to me via aim – icolinirie or via email
Thank you in advance for everything. This is a great community, and all of Cyanogen’s work is greatly appreciated!!
EDIT: I really need some help! Here's some more information. I have a Magic 32B. Its running Cyanogenmod v1.4 + JF Recovery.
From what I have gathered I need to adp into my phone in order to get it to mount. Anyone know how to do this on a mac. I am trying, but I don't fully understand. I have created the .bash_profile from terminal and typed the following "export PATH=${PATH}:/Users/itunes/Documents/android-sdk-mac_86/tools" which is the path to the tools file in the sdk. I am just stuck at this point. I don't know what to do from here.
Hi I quote.
Install SDK utilities you need to connect your PC to your phone
You can download the full SDK from the Android Developer website for your platform
http://developer.android.com/sdk/index.html
You'll need to download the SDK appropriate for your platform and extract it into a directory somewhere. I'm going to assume you're using Windows here and suggest you extract it into a folder called
C:\AndroidSDK\
on your hard disk. You can put it anywhere you like really, but if you do you'll need to substitute it for the folder above.
Add the tools directory to your system path for easy access
In Windows it's easy to add the Android SDK Tools directory to your system path. Doing this lets you use the Android SDK tools anywhere and makes it easier for you.
On Windows XP: Go to Control Panel->System, Choose the 'Advanced' tab and then click 'Environment Variables' To do this on Vista/Windows7: Simply go to Control Panel->System and choose 'Advanced System Settings' and then 'Environment Variables'
Now that you've got here locate Path under System Variables and click Edit, then add the following to the end of the string displayed:
;C:\AndroidSDK\tools\
Then click OK until you get out of the menus.
Now that you've done this you should be able to bring up a command shell and type 'adb' and it should run straight away without needing to change path.
Please note that you can skip this step completely if you find it too complicated - however you will need to CD to the ?AndroidSDK\tools every time you open up a command prompt so it's worthwhile doing. I'm going to assume you have made the change above in all further examples as it gets too complicated really. If you're not confident in a DOS shell, I'd suggest you do a little bit of reading up on basic navigation in DOS first.
Enable Debugging mode on the phone before connecting to PC and installing the ADB driver
Menu > Settings > Applications > Developement > USB Debugging
Install the USB drivers correctly - check using "adb devices".
If you have already connected your phone to your computer before then the USB drivers are probably already loaded. If you're lucky then typing 'adb devices' in a command prompt will produce something like:
C:\AndroidSDK>adb devices
List of devices attached
XXXXXXXXXXXX device
Where XXXXXXXXXXXX is the serial number of your phone. If it doesn't produce that line, then you need to check Device Manager and ensure the device drivers for your phone were installed correctly.
If you are having issues installing the ADB driver, you need to connect your phone then go into Device Manager and check the ADB device properties. Check the following property and it'll look something like:
Device Instance Id: USB\VID_0BB4&PID_0C02&MI_01\7&293A7D0D&0&0001
To fix the driver installation problem, you need to edit the driver's .ini file and change all the references of 0C03 to 0C02, or 0C02 to 0C03 if your device property states your Device Id is 0C03.
Note: After flashing a new ROM, your Device Id may change again to either 0C03 or remain as 0C02. So you need to update the .ini file again as above to refelect the change and re-install the driver. Another known way to fix the above issue is to download and install HTC Sync - this seems to install the correct drivers.
How to use ADB
ADB stands for Android Debugging Bridge - it's a useful way of talking to your handset while it's running. ADB provides commands for copying files to and from your phone, installing packages and debugging your Android applications.
Useful commands include:
adb devices - lists which devices are currently attached to your computer
adb install <packagename.apk> - lets you install an Android application on your phone
adb remount - Remounts your system in write mode - this lets you alter system files on your phone using ADB
adb push <localfile> <location on your phone> - lets you upload files to your phones filesystem
adb pull <location on your phone> <localfile> - lets you download files off your phones filesystem
adb logcat - starts dumping debugging information from your handset to the console - useful for debugging your apps
adb shell <command> - drops you into a basic linux command shell on your phone with no parameters, or lets you run commands directly
How to use Fastboot
Fastboot is another boot method and is used to drop the phone into a safe mode to load/flash alternate roms. You need USB debugging turned on before you can use Fastboot mode - so I'd recommend you do this first (under Settings->Applications->Development->USB Debugging). You will also need to power off your phone first (hold down Power and select Power Off) and then hold down the Back+Power Buttons to start the phone in Fastboot mode. You will need your USB cable connected to be able to issue any commands and assuming your drivers are correct you should be able to issue:
C:\AndroidSDK>fastboot devices
List of devices attached
XXXXXXXXXXXX fastboot
Other commands in this mode include - we'll cover these below in subsequent sections.
fastboot boot <filename> - boots a rom stored on your pc specified by the filename
fastboot flash <partition> <filename> - flashes a rom stored on your pc, partition can be one of {boot, recovery, system, userdata}
fastboot binaries for mac and linux can be found here.
3. Learn how to use fastboot and boot a recovery rom
Download a recovery rom for your device
There are several different recovery roms available for the HTC Magic devices.
Amon_RA has created several nice recovery roms available from http://forum.xda-developers.com/showthread.php?t=530492 and get the Recovery Rom appropriate for your device - these recovery roms have Nandroid Backup and Nandroid Restore and are perfect for the average user.
You can also use Cyanogen's 1.3.1 Recovery ROM available for: PVT32A devices and PVT32B devices - this rom has some additional options for partitioning your SD card for ?Apps2SD/Swapper/etc.
Fastboot the recovery rom
Fastbooting a rom doesn't write anything to your device - it just loads it directly from your PC - so it's a completely safe way of fixing/recovering/backing up your existing rom. To fastboot a rom you need to first drop your phone into Fastboot mode and check that it's working. Now drop into a command shell and make sure the recovery image you're wanting to load is in the same directory that you're running this in. If it's called something other than recovery-rom.img then substitute that instead.
C:\AndroidSDK> fastboot boot recovery-rom.img
If you are having problems changing the directory in the command prompt, just make a copy of the command prompt .exe itself, and place it in the folder that contains the recovery rom, then run the above command.
And once again, if you have a perfected SPL which does not allow remote fastboot, you will have to fix it first.
Use the Recovery Rom to Backup your current ROM with Nandroid
Once you've booted to a recovery rom - you can use the Nandroid Backup option. If you get a 'cannot mount /dev/mkblkxxx error' when you do this then check your microSD card is inserted correctly and if so, wait a few seconds for it to register to the recovery rom correctly. If at first you don't succeed, try, try again (sdcard can take a few seconds to mount!)
You do not need to be a rocket scientist to do this.
you can use the ADB to put in recovery again by fast boot
http://forum.xda-developers.com/showthread.php?t=530492
Hey! First off Thanks for the reply! I really appreciate someone chiming in to throw some advice my way! But while reading your thread you described the instructions for windows. In this case I have a macbook pro running snow leopard.
I did download the android sdk to my documents folder and I understand that I need to execute some scripts from the terminal on my mac to get things running. But I really dont know what those scripts are or what exactly to do.
I can get into the recovery mode on the MyTouch by holding power and home when powering on. So do I open the console from the recovery screen on the mytouch and then run the scripts on the terminal from my macbook? And which scripts should I run to get the sd card mounted onto my desktop (that is what I'm trying to do). Im not too sure what to do from there either. I want to get the phone back to stock android 1.5 os so that I can root again. My sd card has to be corrupted because it keeps giving me an error saying that it wont mount when I try to do a fix file systems or try anything from that menu. What to do??
What!
can you get in the recovery?
Yeah I can get into cyanogen v1.4 recovery. I'm just stuck from there.
Ok ok If I understand this correctly then you are not briced. you do not have any imag on your phone.
if you do not have anything nadroid recovery on sdcard you must enter a new ROM on the sdcard and flash it
remember full wipe.!
Yes this is what I believe I must do. But I need to either find a way to mount my SD card from the phone while it is in recovery mode (cyanogen v1.4). That's my problem.. I wish there was an easier way to get it mounted onto my mac from the recovery screen. I think I'm just going to go to best buy tomorrow and get a micro sd card reader and maybe another sd card just in case.
Once I have done that though. What files should I put onto the sd card in order to flash it back to original factory android 1.5.
What do you think?
Good idea
I have never used cyanogen v1.4 recovery
I use the recovery-RA-sapphire-v1.5.2H.img and ther you can use USB togle in recovery mode, You must go to the store to buy the adapter that fits on your Mac, I have two adapters for your Mac, you can borrow
Yeah that's the plan for tomorrow. Thanks for the offer man. But I'm in Los Angeles, Ca LOL!! Where are you?
icolinirie said:
Yeah that's the plan for tomorrow. Thanks for the offer man. But I'm in Los Angeles, Ca LOL!! Where are you?
Click to expand...
Click to collapse
Bergen . norway.
http://maps.google.no/maps?f=s&utm_...o-google-gm&utm_medium=ha&utm_term=google map
OMG! WOW! Looks like a beautiful place! LA is a concrete jungle but beautiful in its own respects. Bergen looks like a very comfortable place! I enjoy finding out about these things. Maybe someday I'll visit. I'd definitely love to!
icolinirie said:
OMG! WOW! Looks like a beautiful place! LA is a concrete jungle but beautiful in its own respects. Bergen looks like a very comfortable place! I enjoy finding out about these things. Maybe someday I'll visit. I'd definitely love to!
Click to expand...
Click to collapse
it is sick cold. I'll take one picture out the window
We now know that the new vibrant phones have the hardware key disabled to enter recovery mode. But these phones are not defective. The hardware key has been purposefully disabled as part of a misplaced strategy to secure a phone that has basically no security built into it.
Therefore it is really easy to gain root access to these phones. However the process requires the use of the adb program that is part of the google android sdk. This program likes to run on a 32-bit linux distribution. Since it will not run on a 64 bit system, here is how I managed to gain root access to my phone:
1. Download the sdk from google.
2. Boot into linux on a 32 bit machine. (I used ubuntu live cd on an old Toshiba laptop with an available linux partition to mount on the hd. Your mileage may vary.)
3. If you are not using ubuntu make sure that your c library is compatible.
4. Install the google android sdk on the hd linux partition, e.g. /home/android.
5. Plug your Samsung vibrant into the usb port on the linux machine.
The following steps are specific to ubuntu. The important thing to remember is that the adb program must run its server as root to gain the access we desire.
6. Start the terminal app: Applications > Accessories > Terminal
7. Mount the partition and change to the sdk directory:
sudo mount /dev/sda2 /media
cd /media/*/home/android/tools
7. Start the adb server:
sudo ./adb start-server
8. Make sure your device is recognized:
./adb devices
If you do not see your device connected you have some troubleshooting to do.
9. Reboot your phone into recovery mode:
./adb reboot recovery
Congratulations! You just gained root access to your hardware locked vibrant.
This message has been posted by my old g4 laptop while tethered through t-mobile 3g using wireless tether on my brand new Samsung vibrant.
M_T_M said:
Hmmmm..good enough to stick!
Click to expand...
Click to collapse
Yeah it's good, but you should move this thread to Samsung Vibrant forum.
This works on any android phone.
Although the method was inspired by the desire to use my vibrant as a g3 modem, the adb program is a general android maintenance tool that runs on linux. So it really doesn't matter what kind of phone you have. Once you have started the adb-server as root the reboot command will boot any android phone plugged into the linux box.
Spiaatie said:
Yeah it's good, but you should move this thread to Samsung Vibrant forum.
Click to expand...
Click to collapse
I know, I know mate .....I'll do it later...
r2d4 said:
Although the method was inspired by the desire to use my vibrant as a g3 modem, the adb program is a general android maintenance tool that runs on linux. So it really doesn't matter what kind of phone you have. Once you have started the adb-server as root the reboot command will boot any android phone plugged into the linux box.
Click to expand...
Click to collapse
Would this also work for the new T-mobile G2 4G ?
I'm sure we will be seeing more locked phones besides the vibrant and g2. This fix should work for them all. The adb-server gives you root access to your phone provided that you have root access to the machine upon which it runs.
r2d4 said:
I'm sure we will be seeing more locked phones besides the vibrant and g2. This fix should work for them all. The adb-server gives you root access to your phone provided that you have root access to the machine upon which it runs.
Click to expand...
Click to collapse
Keep in mind that no matter what you do on the G2, it'll be wiped on reboot. You can gain root temporarily, but when you reboot, it's gone
Installing the root update
tjhart85 said:
Keep in mind that no matter what you do on the G2, it'll be wiped on reboot. You can gain root temporarily, but when you reboot, it's gone
Click to expand...
Click to collapse
If you want to keep root after your next reboot, you need to update your filesystem. The first step is to install the programs busybox and su.
Before you boot into recovery mode, make sure you have the update.zip file downloaded onto your phone's internal memory card. Whatever is on this card will be left alone even upon a factory reset. But the phone's internal memory will be wiped. The update.zip file merely installs those two programs to the internal memory and doesn't wipe anything.
1. Download the root update for your phone. Rename the file update.zip and place it on the root directory of your device's internal flash memory.
2. Once you are in recovery mode, use the volume keys to scroll and the power key to select "reinstall packages". (This works on the vibrant. The g2 may be slightly different.)
3. Your phone will reboot and you will find the Superuser app has been installed. This app lets you grant root access to applications that need it.
Now you can download powerful apps from the market to gain even more control over your phone.
I hope this helps.
Does boot with a live CD of 32 bit ubuntu on my AMD64 work?? or do i need to boot on a computer with a 32bit processor as well?
i just recently dropped my first generation Samsung Galaxy S Vibrant on the ground. most of the screen went black and i am unable to login into the phone. i am trying to figure out how to retrieve my photos off of the phone's on-board hard drive
i installed the Android SDK on my mac (running 10.6.8) and then installed ADB
i am able to put my phone in recovery mode by plugging it onto my mac and using ADB by running "./adb reboot recovery"
but when i run "./adb devices" it does not recognize my device
usb debugging is enabled on my phone.
i also do not have EasyTetherUSBEthernet installed on my mac
any help getting this to work would be much appreciated.
Does "can't log in" mean that you have to enter a pin, and can't because the screen doesn't work? If that's the case, then one option would be to reflash your rom (since Recovery is available) which would remove your pin and then allow you to access the phone sdcard through usb.
I'm just making this up as I go, so hopefully someone will correct if the idea is hopelessly flawed.
If you can get an adb shell running, or if you can manage to get the recovery to make the sdcard available for mounting, it can be done. Failing that, maybe the Odin dump command?
JJMT said:
Does "can't log in" mean that you have to enter a pin, and can't because the screen doesn't work? If that's the case, then one option would be to reflash your rom (since Recovery is available) which would remove your pin and then allow you to access the phone sdcard through usb.
Click to expand...
Click to collapse
"can't log in" means i am unable to unlock my phone via the unlock pattern i set on it.
the data i care about is in the on-board hd and not the sdcard. would reflashing also wipe the on-board hd?
nm... somehow i was able to get it to work. after trying it again i was able to get adb to recognize my device, plus i now realize the difference between "sdcard" and an sd card
You should be all set. You can add an external SD card, then, using adb shell, mount it and do something like
cp -a /mnt/sdcard /<wherever you mount external sd>
You could also use adb pull on the host, but it may be tedious.
Reflashing has never wiped an sd card for me. You could reflash to get what's left of the device sort of usable.
Hi I broke my nexus 7 3g. I wanted to reinstall paranoid android and make everything fresh. Checking wipe data with goo manager didn't completely make everything stock so I figured maybe PA saved something to the "sd card", so I tried to wipe external data in twrp and I got unable to wipe /usb-otg, then I figured maybe if I wiped all the other options that might fix it and that just got rid of the OS completely.
I get unable to mount /usb-otg when trying to mount it to my desktop to copy a copy of the rom over because it seems my sd card did manage to get formatted. Unless I'm not choosing the right thing I don't know somebody help please before I throw this thing in the garbage.
I can't get it to show up in the nexus 7 toolkit but I have the donate version of that if by some chance that'll make the process easier. God damn please help me.
I've installed I think every program ever made for windows (gonna have to reformat windows again weeeeeeeee) trying to fix this and they all seem to want my nexus in adb mode but I don't think there's an adb mode when there's no OS installed. I'm willing to pay if that'll get me some help faster.
"mount /usb-otg" is for putting a usb storage device (flash memory key or USB Hard Drive) on a OTG cable attached to the N7 when booted into TWRP recovery.
It is NOT for making the N7 look like a USB mass storage device to an attached PC.
So put your ROM file on a USB key drive (VFAT formatted, not NTFS formatted), and flash it from TWRP "external storage". You don't need ADB to be working if you do that.
If you don't have a big enough flash key or a USB Hard Drive to do this with, then you have two remaining options:
1) Get adb working
2) Get fastboot working (and fastboot flash a stock ROM, and then proceed from there)
good luck
bftb0 said:
"mount /usb-otg" is for putting a usb storage device (flash memory key or USB Hard Drive) on a OTG cable attached to the N7 when booted into TWRP recovery.
It is NOT for making the N7 look like a USB mass storage device to an attached PC.
So put your ROM file on a USB key drive (VFAT formatted, not NTFS formatted), and flash it from TWRP "external storage". You don't need ADB to be working if you do that.
If you don't have a big enough flash key or a USB Hard Drive to do this with, then you have two remaining options:
1) Get adb working
2) Get fastboot working (and fastboot flash a stock ROM, and then proceed from there)
good luck
Click to expand...
Click to collapse
Holy crap I kinda thought the otg thing was because I flashed the kernel for using a charging otg cable. You know what I googled everything under the sun except the error itself. I was serious about the money if you want like $5 or $10 let me know if you got a donate link.
I'm pretty curious to know how to get adb working without an os installed. I'm pretty curious again about using fastboot because I have fastboot and it wouldn't show up on the nexus 7 toolkit etc etc etc. If you don't want to explain them that's fine because I'm pretty sure I'm not gonna mess up this bad ever again and I'm gonna buy a second usb flash drive now that I know I might finally have a reason to have even a single one haha.
Thank you thank you thank you thank you thank you thank you thank you thank you I guess I can throw out my tape and floppy drives now that it's 2013 and we're in the future.
The custom recoveries also run ADB... so you don't need an OS installed to use adb - just a custom recovery.
But there is a catch: ADB from the custom recoveries (either CWM or TWRP) show up on a different USB IDs than what the N7 (Android) OS uses
This little tiny detail effs up just about every newb Windoze user because they get an ADB driver installed for one or the other (either the OS flavor - using Google or Asus drivers, or the custom recovery flavor - using the "Universal Naked Driver")... and then they can't understand "why ADB doesn't work" in the other mode.
Sorry but I'm not going to rehash a tutorial on Windows drivers. I put up a gory long winded story somewhere, wait here it is. Feel free to ignore it. Woe to you if you are using Windows 8.
Rather than profuse "thank you"s, click on the Thanks button. At the end of the year I'm going to trade them in for some brownie points.
Well I clicked the thanks buttons but I just have to type it once more thanks there it is, I'll read that link soon too and I'll click the thanks button on that see ya in the future
The process is very simple. You need an unlocked bootloader and TWRP. You also need to edit the file, build.prop and add this following tweak below:
#Enable ADB Debugging By Default & Disable USB Debugging Popup
persist.adb.notify=0
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
Then go ahead pair your Fire TV remote upon setup wizard, plug in your Fire TV 4K into your computer and allow adb prompt. After you've done those things type in adb shell monkey -p com.amazon.tv.oobe -v 1000. BE sure your out of the pause and play to continue and it'll bypass the checking for updates screen!
Doesn't work for me on mantis, I've tried it several times. Installed 6.2.7.6, added options to build.prop on TWRP. Rebooted, paired remote and powered off the stick. Connected to computer, received adb authorization window and accepted. Pushed play/pause to start and on language selection screen, entered adb shell monkey command. Then what I assume are very fast auto button presses pass the screen, leaving me at network selection (green or yellow rectangles on item selections are shown). After I connect, the stick starts searching for updates normally. What am I doing wrong? Cheers.
gabardal said:
Doesn't work for me on mantis, I've tried it several times. Installed 6.2.7.6, added options to build.prop on TWRP. Rebooted, paired remote and powered off the stick. Connected to computer, received adb authorization window and accepted. Pushed play/pause to start and on language selection screen, entered adb shell monkey command. Then what I assume are very fast auto button presses pass the screen, leaving me at network selection (green or yellow rectangles on item selections are shown). After I connect, the stick starts searching for updates normally. What am I doing wrong? Cheers.
Click to expand...
Click to collapse
That's normal for it to show the network selections and green/yellow boxes. You'd have to keep inputting the command really fast. It'll force the updates screen and go back to it. Try putting the monkey command 3-4 times until it goes to the device registration screen. It takes a few tries to bypass
So, what screen would I be watching to know it has worked?
Edit: It eventually worked, but it's hit and miss I guess . You just have to keep trying, thank you very much for this.
Skel40 said:
The process is very simple. You need an unlocked bootloader and TWRP. You also need to edit the file, build.prop and add this following tweak below:
#Enable ADB Debugging By Default & Disable USB Debugging Popup
persist.adb.notify=0
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
Then go ahead pair your Fire TV remote upon setup wizard, plug in your Fire TV 4K into your computer and allow adb prompt. After you've done those things type in adb shell monkey -p com.amazon.tv.oobe -v 1000. BE sure your out of the pause and play to continue and it'll bypass the checking for updates screen!
Click to expand...
Click to collapse
This seems like an easier method:
How to block updates on a rooted Fire TV or Fire TV Stick by setting a custom Fire OS version number
This is a new method of blocking software updates on a rooted Fire TV or Fire TV Stick. It involves setting a custom software version number in the device's build.prop configuration file. Rbox came up with this idea and asked me to test if it works.
www.aftvnews.com
Just boost the build number to 9..., and it should think it's already upgraded.
It doesn't work for me because the stick won't show up in adb devices. I've tried diffrent cables, PCs and even FireOS (6.2.7.7 and 6.2.7.6) versions but it simply won't show up as an adb device. Any idea what's wrong here?
Ungeskriptet said:
It doesn't work for me because the stick won't show up in adb devices. I've tried diffrent cables, PCs and even FireOS (6.2.7.7 and 6.2.7.6) versions but it simply won't show up as an adb device. Any idea what's wrong here?
Click to expand...
Click to collapse
Did you add the tweaks through your computer and adb them back to your 4K? Try adding the tweaks in the build.prop file and try again. If that doesn't work I'd be nice enough to post a rom containing the tweak for adb to work
Skel40 said:
Did you add the tweaks through your computer and adb them back to your 4K? Try adding the tweaks in the build.prop file and try again. If that doesn't work I'd be nice enough to post a rom containing the tweak for adb to work
Click to expand...
Click to collapse
No, I added them manually on the stick itself inside TWRP (I checked for typos), since I can't reboot it to recovery whilst connected to my PC. I'm updating it right now to the latest firmware where I can enable ADB so I can reboot to recovery and then downgrade to 6.2.7.7 and see if that works.
EDIT: It works now, I had to be on 6.2.8.0 so I can reboot to recovery and from the recovery I wiped 6.2.8.0, flashed 6.2.7.7, Magisk and edited the build.prop all without disconnecting the FireTV from my PC. After that it showed up as an ADB device.
Hey so. I don't know if I'm missing something here or but whenever I connect my stick to my PC, I really don't know how to boot into twrp and keep twrp on while connected to my PC
The prompt lasts only but 5 seconds and without any external otg keyboard or mouse connected I can't manage to hold the stick in recovery as it directly boots to system after when disconnected and connected again.
If there's any chance someone can guide me to a way that would help me enable adb and keep the stick in twrp while connected to the PC I'll be thankful.
If the initial Setup is done, you can enable adb in the Settings.
If not , it can only be done by rerooting with unlock script ( if you have no otg adapter).
0815hoffi said:
If the initial Setup is done, you can enable adb in the Settings.
If not , it can only be done by rerooting with unlock script ( if you have no otg adapter).
Click to expand...
Click to collapse
I'm looking to bypass the updates at the initial setup screen actually. I don't get ADB enabled at the setup screen even after replacing the edited build.prop file through the twrp file manager and using an otg usb stick to copy it over in the system directory.
What other way is there I can use to do that? If I disconnect the power it only shows the twrp prompt which I can't access because there's no otg adapter connected.
Edit: Forgot to mention I have to remove the OTG because the PC doesn't recognize the firestick when I connect it through that. If I connect it directly it works absolutely fine.
nagi_007pk said:
I'm looking to bypass the updates at the initial setup screen actually. I don't get ADB enabled at the setup screen even after replacing the edited build.prop file through the twrp file manager and using an otg usb stick to copy it over in the system directory.
What other way is there I can use to do that? If I disconnect the power it only shows the twrp prompt which I can't access because there's no otg adapter connected.
Edit: Forgot to mention I have to remove the OTG because the PC doesn't recognize the firestick when I connect it through that. If I connect it directly it works absolutely fine.
Click to expand...
Click to collapse
Go to this post, it will bypass setup screen enable accessibility and app widget also, Skel40 removed some things also but i may upload a clean 6.2.8.1 setup later.
if you are in fastboot/recovery/system you can use the following command to open twrp when you are connected via pc
Code:
adb reboot recovery
for system and twrp
Code:
fastboot reboot recovery
to launch twrp from fastboot
now if you can start your stick and can access adb (i know you can't otherwise you already should have bypassed OOBE) then you can open twrp from the adb and you can use adb sideload also
if you have a usb otg + hub then put the zip in pendrive connect it to hub along with mouse and install it from there.
if you dont have a hub then you will have to use kamakiri again, after bootrom-step it will open hacked bl, you can use fastboot-step.sh to flash twrp again, when TWRP is open you can sideload the file to the twrp.
it will bypass the OOBE and also block system update natively.
SweenWolf said:
Go to this post, it will bypass setup screen enable accessibility and app widget also, Skel40 removed some things also but i may upload a clean 6.2.8.1 setup later.
if you are in fastboot/recovery/system you can use the following command to open twrp when you are connected via pc
Code:
adb reboot recovery
for system and twrp
Code:
fastboot reboot recovery
to launch twrp from fastboot
now if you can start your stick and can access adb (i know you can't otherwise you already should have bypassed OOBE) then you can open twrp from the adb and you can use adb sideload also
if you have a usb otg + hub then put the zip in pendrive connect it to hub along with mouse and install it from there.
if you dont have a hub then you will have to use kamakiri again, after bootrom-step it will open hacked bl, you can use fastboot-step.sh to flash twrp again, when TWRP is open you can sideload the file to the twrp.
it will bypass the OOBE and also block system update natively.
Click to expand...
Click to collapse
What if i'm trying to install 6.2.7.7 and not 6.2.8.1?
Edit: Also because of the kodi passthrough and otg mounting script developed by pretorian as I want to stay and set this firmware up without it looking for updates in the beginning.
nagi_007pk said:
What if i'm trying to install 6.2.7.7 and not 6.2.8.1?
Edit: Also because of the kodi passthrough and otg mounting script developed by pretorian as I want to stay and set this firmware up without it looking for updates in the beginning.
Click to expand...
Click to collapse
I'm assuming you can use TWRP and have 6.2.7.7 installed with pretorianos kernel
Flash this along with Pretorianos kernel
clear data and cache
then just boot.
it will skip it, you may have to set IR twice but it will go through, tell me how many times it asked to setup IR
SweenWolf said:
I'm assuming you can use TWRP and have 6.2.7.7 installed with pretorianos kernel
Flash this along with Pretorianos kernel
clear data and cache
then just boot.
it will skip it, you may have to set IR twice but it will go through, tell me how many times it asked to setup IR
Click to expand...
Click to collapse
does this zip work for any build ? or just for 6.2.7.7 ?
tokoam said:
does this zip work for any build ? or just for 6.2.7.7 ?
Click to expand...
Click to collapse
This zip is fully compatible with 8.0 and 8.1 because its pulled from 6.2.8.1
It will certainly bypass any build that is 6.2.7.7 or greater
It will not run on older builds like 7.1 or 7.3
SweenWolf said:
This zip is fully compatible with 8.0 and 8.1 because its pulled from 6.2.8.1
It will certainly bypass any build that is 6.2.7.7 or greater
It will not run on older builds like 7.1 or 7.3
Click to expand...
Click to collapse
I do have another question if you have TWRP installed and installed a custom rom isnt twrp suppose to prevent it from effecting efuse by default ? even if an update is done within the os ? this is unclear to me as I heard it suppose to . Also is there any other easy way to check the status of an efuse other than taking it apart and connecting it to kamakir and running lsusb command to check for bootrom-step ?
tokoam said:
I do have another question if you have TWRP installed and installed a custom rom isnt twrp suppose to prevent it from effecting efuse by default ? even if an update is done within the os ? this is unclear to me as I heard it suppose to . Also is there any other easy way to check the status of an efuse other than taking it apart and connecting it to kamakir and running lsusb command to check for bootrom-step ?
Click to expand...
Click to collapse
TWRP cannot prevent efuse burning, efuse is burnt by the system while booting to prevent a system downgrade (mostly for security purposes, samsung also does this).
The file responsible for burning efuse is present in /system/bin partition which can be accessed by the system to check the status of the fuse.
You don't have to worry about efuse if you never flashed 6.2.8.0 or higher.
The system will blow efuse only if there is a change in the critical partitions.
6.2.7.7 does have efuse files present in the system but because there were no updates to the critical partitions so it didn't blew anything. It will blow only if you flash stock >8.0
If you were on 6.2.7.7 and used my method to upgrade then
it upgraded your system
then updated TZ then removed the efuse writer
so it never got to know that an update was performed, so your fuse is intact.
There is nothing on your system which will blow your efuse.
SweenWolf said:
TWRP cannot prevent efuse burning, efuse is burnt by the system while booting to prevent a system downgrade (mostly for security purposes, samsung also does this).
The file responsible for burning efuse is present in /system/bin partition which can be accessed by the system to check the status of the fuse.
You don't have to worry about efuse if you never flashed 6.2.8.0 or higher.
The system will blow efuse only if there is a change in the critical partitions.
6.2.7.7 does have efuse files present in the system but because there were no updates to the critical partitions so it didn't blew anything. It will blow only if you flash stock >8.0
If you were on 6.2.7.7 and used my method to upgrade then
it upgraded your system
then updated TZ then removed the efuse writer
so it never got to know that an update was performed, so your fuse is intact.
There is nothing on your system which will blow your efuse.
Click to expand...
Click to collapse
well in my case I flashed rbox version of from first being rooted 8.0 then upgraaded to 8.1 with the version skel40 posted
tokoam said:
well in my case I flashed rbox version of from first being rooted 8.0 then upgraaded to 8.1 with the version skel40 posted
Click to expand...
Click to collapse
Then you're safe