Database Develop

[Q] Just some newbie questions

Hello,
I know, that professionals usually don't like these questions but I really want to know sth:
I recently installed Froyo 2.2.1 with Kies Reg Patcher and it works GREAT! The only thing that matters is the old RFS file System.
So I decided to install the Voodoo lagfix.
I put the update.zip in my root/sdcard and tried the following:
1. I started the DOWNLOAD Mode - but only the yellow shield appeared - nothing happened as expected (maybe nothing to download?)
2. I started the RECOVERY Mode and selected "Apply update.zip". ==> It was telling me after 2 seconds "Error ... unsigned ..."
==> I knew this is caused by the new recovery assistent. After all I rebootet my phone and every thing works like it was before.
Now the questions:
1. Is my system unchanged? I mean has the update.zip file copied some files until it aborded?
2. Is it bad when I turn my phone in Download mode? I mean it didn't flash/download anything - so does it really damage my phone when I press the power key 5 sec and restart my phone (ONLY IN THIS SITUATION - I know that pressing it during an update process/by appearance of the status bar can damage the phone).
Please give me some answears!
PS: By the way, on woodoo-project.org it is written that the update.zip mode "...works with clockworkmod" - what is this for a mod? I googled but I only found variations about it - not a documentation and their website seems o be down.
Has this mod automatically been installed before the "Unsigned Error" came?
LG,
Dennis

In order to have your phone lag fixed, you need to root the phone (root: complete system access of your phone).
1. In download mode the phone wont update anything on its own. You need to use odin for flashing (installing) through the computer.
2. In froyo 2.2.1 you have a 3e recovery (which only updates with signed apk's) - your update.zip file is custom hence its unsigned.
about your q's
1. Your system has not been changed as the process was aborted (no files are copied or changed)
2. Its completely safe to restart you phone in download mode if you aren't flashing anything.
Note: In order to use voodoo lagfix you need to get 2e recovery for flashing custom unsigned apk's. This can be done by using CF root method (this will root your phone and also install ClockWorkMod - CWM). CWM will allow you to install the update.zip.
*For more info. just check the thread about rooting/lagfix etc. to get step by step instructions.

Thank You very much! Now I get it!

Development of New Hardbrick-Saving App?

Hey folks! :victory:
So I know you're all going to say, "oh, it's some xda noob", but I've got some big ideas for the future. So I had this great idea for an app that I'd like to share with all of you. I recently had my phone (HTC One m7ul) hardbricked by a slip of my fingers while clean-installing Omnirom. Fastboot and adb could not detect it, and therefore, my computer couldn't be used in the process of attempting to restore it. However, I could still access my recovery; and this is where I came up with the idea for this app I think everybody should have installed:
STASIS
This app would be the savior of all those people out there with hardbricked phones.
HOW IT WORKS
The app installs itself into the preexisting legacy partition of your phone, where it lies dormant and safe until needed
The app then recognizes the installation process to be complete and prompts the user to clone their phone into "stasis"
The way it clones the phone into "stasis" works as follows:
It copies the system partition exactly as it is
It then prompts the user for which files/apps it should back up as well
It saves all the selected files and apps in an archive that it names as "Stasis.zip" and then compresses and encrypts the archive with a password of the user's choice
Once complete, the phone reboots itself
Your phone is now INVINCIBLE!
The phone can now be saved from a complete internal storage wipe via commands from the recovery menu.
HERE IS THE TRICKY PART
The only way that this archive can be installed from the recovery partition would be by somehow force loading an extra option in the recovery "advanced" menu or by making it mounted via a series of hardware button presses in the install menu of recovery or a command line. This is ALOT HARDER than it actually sounds.
Prior to your internal storage wipe, your phone can restore via recovery by entering the series of commands and/or hardware button presses to mount the TWRP partition, and therefore flash the stasis.zip.
POSSIBLE OPTIONS?
The stasis.zip could be stored in it's own partition private from the rest of the system and/or recovery.
NOTE THAT I HAVE NO EXPERIENCE IN ANDROID DEVELOPMENT
I just want to see this damn thing made so everybody can have their phone hardbrick and live to tell the tale.
:fingers-crossed:
--flq of xda
P.S. If anybody thinks this app is a good idea, please feel free to join up on it's github!

doesnt a nandroid backup works the same way ?
or similar?

_flq said:
Hey folks! :victory:
So I know you're all going to say, "oh, it's some xda noob", but I've got some big ideas for the future. So I had this great idea for an app that I'd like to share with all of you. I recently had my phone (HTC One m7ul) hardbricked by a slip of my fingers while clean-installing Omnirom. Fastboot and adb could not detect it, and therefore, my computer couldn't be used in the process of attempting to restore it. However, I could still access my recovery; and this is where I came up with the idea for this app I think everybody should have installed:
STASIS
This app would be the savior of all those people out there with hardbricked phones.
HOW IT WORKS
The app installs itself into the preexisting legacy partition of your phone, where it lies dormant and safe until needed
The app then recognizes the installation process to be complete and prompts the user to clone their phone into "stasis"
The way it clones the phone into "stasis" works as follows:
It copies the system partition exactly as it is
It then prompts the user for which files/apps it should back up as well
It saves all the selected files and apps in an archive that it names as "Stasis.zip" and then compresses and encrypts the archive with a password of the user's choice
Once complete, the phone reboots itself
Your phone is now INVINCIBLE!
The phone can now be saved from a complete internal storage wipe via commands from the recovery menu.
HERE IS THE TRICKY PART
The only way that this archive can be installed from the recovery partition would be by somehow force loading an extra option in the recovery "advanced" menu or by making it mounted via a series of hardware button presses in the install menu of recovery or a command line. This is ALOT HARDER than it actually sounds.
Prior to your internal storage wipe, your phone can restore via recovery by entering the series of commands and/or hardware button presses to mount the TWRP partition, and therefore flash the stasis.zip.
POSSIBLE OPTIONS?
The stasis.zip could be stored in it's own partition private from the rest of the system and/or recovery.
NOTE THAT I HAVE NO EXPERIENCE IN ANDROID DEVELOPMENT
I just want to see this damn thing made so everybody can have their phone hardbrick and live to tell the tale.
:fingers-crossed:
--flq of xda
P.S. If anybody thinks this app is a good idea, please feel free to join up on it's github!
Click to expand...
Click to collapse
Your phone wasn't even close to being hard bricked, you wiped your system partition and internal storage at the same time. Leaving you no Rom to install or Backups to restore. This is a soft-brick at best.
In the process your Windows drivers failed stopping you from pushing a Rom which I still don't know weather you sorted or not because you haven't replied in your other thread.
The app you describe would do nothing a Nandroid doesn't do already. And regardless of where you store the Stasis.zip/Nandroid if you wipe the phone it will be gone. There are only 3 flash partitions on the HTC One System, Data and Cache all the other partitions are RAW partitions that require a direct dump.
If you want a separate partition to keep a backup on that can be accessed without the need for a pc, get your self an USB OTG device. Then you can keep a backup or rom on a usb stick and copy it or restore it to your phone using OTG without the need for a pc.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

What Danny said.
A hard-brick state is where you cannot access the kernel or even the bootloader. I'm not so sure if you still can access download or APX mode if you were hard-bricked, probably can still access either of them because it is most likely detached from the boot loader (again, not so sure, but from experience download mode *MAY* become inaccessable).
If your device was really hard-bricked and does not or cannot access any of those modes (I imagine fastboot being inaccessible as well) then all you can really do is JTag it. Problem is that devices like the Sony Tablet S has files which disables JTagging so I believe you have to directly JTag to the flash memory or something for it to work.
I think there is this other connector which can be used to also restore it, but I have forgot since I have not looked into it for a long time now.
I've forgot to mention, the recovery is also inaccessible in a hard-brick as it relies on the boot loader to change the boot path to the recovery or something (recoveries use a kernel as well).

Recovery Mode after Encryption

Hello
after i rooted my z3 compact and stuff i thought "hey, encrypting the data would be nice and safe" and did so.
after this i wanted to install some zip via recovery-mode and there are just errors telling me "cannot mount sdcard" and smth like that
i assume this is because the sdcard is encrypted.. .
did anyone know how i can use recoverymode again without flashing the whole firmware back again? oO
thank you

I have the same situation. Can't even enter recovery. You can copy paste files from the zip in the system with for example root explorer, set the correct permissions and reboot.
A working recovery would be better.

I'm on 6.0.1, rooted, locked bootloader and encrypted phone. Can't seem to enter recovery either. There's no green LED on phone reboot. Tried Power + vol up/down, no luck. Also volume up/down during boot, also nothing.
Is there no way to access recovery now?

sil_el_mot said:
did anyone know how i can use recoverymode again without flashing the whole firmware back again? oO
Click to expand...
Click to collapse
There is a TWRP 3.0.2.0 for Z3c available here
Apparently it does work with encrypted partitions, but you will probably have to encrypt the phone after installing TWRP, so this won't help you out of your situation.
Edit: there is a manual install of TWRP compatible with MM, once in recovery you could flash the 3.0.2.0 version and restart to recovery, but I haven't tried this and you may well end up in a bootloop with an unreadbale encrypted partition.

sil_el_mot said:
after i rooted my z3 compact and stuff i thought "hey, encrypting the data would be nice and safe" and did so.
after this i wanted to install some zip via recovery-mode and there are just errors telling me "cannot mount sdcard" and smth like that
i assume this is because the sdcard is encrypted.. .
did anyone know how i can use recoverymode again without flashing the whole firmware back again?
Click to expand...
Click to collapse
for those of you who have a working recovery and encrypted data partition and SDcard, there are two ways of using it:
1. VIA ADB SIDELOAD: TWRP have a ADB sideload feature. it means you can flash .zips directly from your computer, connected to your phone wia USB cable. steps: 1. go to TWRP, search for ADB sideload feature and turn it ON, 2. connect your phone to your computer, 3. open terminal on your computer and type:
Code:
ADB sideload "path/to/your/file.zip"
. bingo!
2. VIA USB OTG: Z3c support USB OTG (On The Go) so you can connect your USB key to your phone via USB OTG cable. you put .zips you want to flash to your USB, connect it to your phone when in TWRP and flash them from USB instead of encrypted partitions.

Decrypt OxygenOS without losing data

Hello there!
Today, after a bit of tinkering around I managed to get my OnePlus 3 in a decrypted state without losing data!
However, this is NOT a method where your data will remain on the phone, it requires you to copy a backup to your PC and then copy everything back + fix permissions. In this guide you'll completely wipe/reset your phone prior to restoring everything.
FAQ:
Q: Why do I need an undecrypted phone?
A: So far (as of today, 06.07.2016) multiboot will not work on encrypted phones. That's probably the only reason why you'll ever want to decrypt your phone.
Q: Will updating the ROM force encryption again?
A: If you're using OxygenOS (or another encryption forcing ROM), yes. However if you flash the Full ROM ZIP and immediately after that SuperSU (DO NOT USE SYSTEMLESS OR IT WILL ENCRYPT AGAIN!!!) WITHOUT REBOOTING it'll not encrypt the device again. (Thanks to @JumboMan)
Q: I've followed your guide but my phone got encrypted again!
A: You've probably used the Systemless SuperSU version which does indeed not prevent your device from being encrypted again. Use the normal version available HERE.
You'll need:
A PC (obviously)
Unlocked OnePlus 3 (will probably work on other OnePlus phones, not tested!)
TWRP Recovery (follow THIS LINK for a guide)
About 50 GB of free space on your PC (depends on how much data you have on the phone)
ADB and Fastboot drivers installed on your PC (to get those connect your OP3 to your PC, as storage choose MTP, open the emulated OnePlus CD-Drive and install those drivers)
(Optional) 15 Seconds ADB Installer
A bit of time, roughly 30 minutes to 1 hour
!!!DISCLAIMER!!!
I'M NOT RESPONSIBLE FOR ANYTHING YOU'RE ABOUT TO DO HERE, THIS GUIDE IS PURELY WRITTEN "OUT OF MY HEAD" AND I CANNOT CONFIRM ANY OF THE FOLLOWING STEPS ANYMORE!!!!
ONLY DO THIS IF YOU KNOW HOW TO RECOVER FROM A HALF-INSTALLED OR COMPLETELY WIPED SYSTEM!!!​
How To:
READ AND ACKNOWLEDGE THE DISCLAIMER ABOVE!
Done? Are you really sure? ... Okay!
If you don't need your data backed up simply start at Step 10 and ignore the restore parts after that.
Still on OxygenOS (or any other ROM) make sure you've enabled ADB in Developer Options and connected + allowed your PC at least one time, else ADB in TWRP will not work.
If you have Titanium Backup, create a backup of all your apps before starting. Just in case, you never know...
Once done boot into TWRP (see above for an installation guide)
Create a normal TWRP backup
Type in "adb devices" to check if you're allowed to use ADB inside TWRP. If it says "unauthorized" refer to Step 1 again.
Once done open up a CMD on your PC and cd to the directory you want all your backup-files to be (or navigate via Windows Explorer to the folder, hold "Shift", right-click and choose "Open command window here...")
Type in "adb pull /data/media" and wait. Depending on the size this can take a few minutes.
After that's done make sure all your files are here and ADB is not reporting any skipped files.
Checked all your files? Okay!
In TWRP choose "Reboot" and "Bootloader". This will put your phone into Fatboot mode.
Type in "fastboot devices" to check if your phone is recognized. If not go into device manager, find the Google Bootloader drivers and install those.
NOW IS YOUR LAST CHANCE TO MAKE SURE EVERYTHING'S BACKED UP AND THERE!
Next type in "fastboot format userdata" and hit enter. This will completely wipe your device.
Boot back into TWRP by using the volume rocker and the Power Button.
ADB is probably not working now (will only report "unauthorized"), MTP however still works. Copy the TWRP folder we backed up earlier onto the device again.
Once copying finished restore the backup and reboot into recovery again. You're now able to use ADB due to the adbpub.key being present again. (You could've done this earlier but it's easier that way.)
Copy the rest back onto the device with "adb push / /data/media". (I'm not really sure if this command is right, beware!)
Now type "adb shell chown -R media_rw:media_rw /data/media" to fix issues later in the ROM.
You're basically finished now! Simply reboot and wait till it boots up again. If you're getting stuck at a "Wrong PIN" or "Wrong Pattern" screen SEE THIS COMMENT I made in another thread.
Finished!
As said, I'm not sure if I forgot something here or not. However I think I got everything covered

Thank you. This was a much needed guide for all of us
Sent from my ONEPLUS A3003 using Tapatalk

Nice

Noob questions: is the decrypted OS faster? Performances of the phone are the same? What about updates (any update will crypt it again?
Thanks for any feedback!
Sent from my OnePlus3 using XDA Labs

IlD4nX said:
Noob questions: is the decrypted OS faster? Performances of the phone are the same? What about updates (any update will crypt it again?
Thanks for any feedback!
Sent from my OnePlus3 using XDA Labs
Click to expand...
Click to collapse
Performance is about the same.
I have no idea if updates will crypt it again, I think not tho? Not sure.

ota updates might encrypt it again if you're on stock. depending if there's a new kernel. the kernel I think forces encryption. so we need a modified boot img to disable forced encryptions. or use a custom kernel that disables force encryption.
If you're on a custom rom based on aosp/cm. most of them doesn't force encryption. so there's no need to worry.
Sent from the moon and back

Thanks for the guide, will this wipe my internal storage?

daavid1995 said:
Thanks for the guide, will this wipe my internal storage?
Click to expand...
Click to collapse
Yes, however the guide shows you how to get a backup of ALL your files before anything gets wiped.
Ajo, und servus aus Österreich

IlD4nX said:
Noob questions: is the decrypted OS faster? Performances of the phone are the same? What about updates (any update will crypt it again?
Thanks for any feedback!
Sent from my OnePlus3 using XDA Labs
Click to expand...
Click to collapse
Yes. updates will encrypt data again.
if you want to remain non encrypted after update then following procedure.
1. download full rom zip (not ota zip)
2.flash full update zip
3.without rebooting after flashing update just flash SuperSU zip. SuperSU will patch your boot img to remain in non encrypted state.
Proof- myself tried it on 3.2.0 update and it works without any problem

JumboMan said:
Yes. updates will encrypt data again.
if you want to remain non encrypted after update then following procedure.
1. download full rom zip (not ota zip)
2.flash full update zip
3.without rebooting after flashing update just flash SuperSU zip. SuperSU will patch your boot img to remain in non encrypted state.
Proof- myself tried it on 3.2.0 update and it works without any problem
Click to expand...
Click to collapse
Added to the OP Thanks for testing!

Thanks, i will try
Dere haha :fingers-crossed::good:
EpicLPer said:
Yes, however the guide shows you how to get a backup of ALL your files before anything gets wiped.
Ajo, und servus aus Österreich
Click to expand...
Click to collapse

maybe stupid questions, but not clear for me:
is there a negative point decrypting the phone or are there any risks?
will decrypting have an effect on the security of the phone?

odooo said:
maybe stupid questions, but not clear for me:
is there a negative point decrypting the phone or are there any risks?
will decrypting have an effect on the security of the phone?
Click to expand...
Click to collapse
As long as you're not an "international searched criminal" where the FBI tries to break into your phone then, no
I'd say it is a bit less secure but who cares, anyone who wants access to your phone somehow gets it anyways, TWRP isn't helping here either since anyone can simply boot into recovery and recover all files from there nonetheless.
Decryption risks are only when you're not good at backing up your data, else there are no risks of doing so.

@EpicLPer:
17. Copy the rest back onto the device with "adb push / /data/media". (I'm not really sure if this command is right, beware!)
Click to expand...
Click to collapse
"adb push / /data/media" doesnt work for me. Can somebody help? I restored the TWRP-Backup and only need to copy the rest on the device.
Edit: I did it in another way, copied all files manually.

Can someons dcrypt this
IzpG+nubzE2m3krvbos0lVDLANkIkiekZt209MYU12Vzny8WNOS7o4JGNoVAm41e/44IYPHmh
0Y7NnLW1JghbWJwbzL1WIpQw7nkzQoH9dEwvTiloTg5BI1u9TYRExzLGQEDUqN2hjq1G5cn
CqDmYoQnMs2bMiuajZweq9ZDC7gLruq6dse0L96gzZFoC/33lF0h1mEh7SBgW3FrcsjhRQ==
Sent from my SM-N910P using XDA-Developers mobile app

Worked, Thanks

How can I check if my device is decrypted or encrypted?

odooo said:
How can I check if my device is decrypted or encrypted?
Click to expand...
Click to collapse
Go to Settings > Device Security and check if it says encrypted or if it gives you the option to encrypt. If second, you know it's decrypted.

Can somebody do some benchmarks? I am really curious whether it makes a difference or not.
from what I've heard it makes a big difference in sequential rw speeds, which are actually pretty important on android.

Will it wipe my rom too?? Or just internal storage??
---------- Post added at 04:03 PM ---------- Previous post was at 03:31 PM ----------
EpicLPer said:
Hello there!
Today, after a bit of tinkering around I managed to get my OnePlus 3 in a decrypted state without losing data!
However, this is NOT a method where your data will remain on the phone, it requires you to copy a backup to your PC and then copy everything back + fix permissions. In this guide you'll completely wipe/reset your phone prior to restoring everything.
FAQ:
Q: Why do I need an undecrypted phone?
A: So far (as of today, 06.07.2016) multiboot will not work on encrypted phones. That's probably the only reason why you'll ever want to decrypt your phone.
Q: Will updating the ROM force encryption again?
A: If you're using OxygenOS (or another encryption forcing ROM), yes. However if you flash the Full ROM ZIP and immediately after that SuperSU WITHOUT REBOOTING it'll not encrypt the device again. (Thanks to @JumboMan)
You'll need:
A PC (obviously)
Unlocked OnePlus 3 (will probably work on other OnePlus phones, not tested!)
TWRP Recovery (follow THIS LINK for a guide)
About 50 GB of free space on your PC (depends on how much data you have on the phone)
ADB and Fastboot drivers installed on your PC (to get those connect your OP3 to your PC, as storage choose MTP, open the emulated OnePlus CD-Drive and install those drivers)
(Optional) 15 Seconds ADB Installer
A bit of time, roughly 30 minutes to 1 hour
!!!DISCLAIMER!!!
I'M NOT RESPONSIBLE FOR ANYTHING YOU'RE ABOUT TO DO HERE, THIS GUIDE IS PURELY WRITTEN "OUT OF MY HEAD" AND I CANNOT CONFIRM ANY OF THE FOLLOWING STEPS ANYMORE!!!!
ONLY DO THIS IF YOU KNOW HOW TO RECOVER FROM A HALF-INSTALLED OR COMPLETELY WIPED SYSTEM!!!
How To:
READ AND ACKNOWLEDGE THE DISCLAIMER ABOVE!
Done? Are you really sure? ... Okay!
If you don't need your data backed up simply start at Step 10 and ignore the restore parts after that.
Still on OxygenOS (or any other ROM) make sure you've enabled ADB in Developer Options and connected + allowed your PC at least one time, else ADB in TWRP will not work.
If you have Titanium Backup, create a backup of all your apps before starting. Just in case, you never know...
Once done boot into TWRP (see above for an installation guide)
Create a normal TWRP backup
Type in "adb devices" to check if you're allowed to use ADB inside TWRP. If it says "unauthorized" refer to Step 1 again.
Once done open up a CMD on your PC and cd to the directory you want all your backup-files to be (or navigate via Windows Explorer to the folder, hold "Shift", right-click and choose "Open command window here...")
Type in "adb pull /data/media" and wait. Depending on the size this can take a few minutes.
After that's done make sure all your files are here and ADB is not reporting any skipped files.
Checked all your files? Okay!
In TWRP choose "Reboot" and "Bootloader". This will put your phone into Fatboot mode.
Type in "fastboot devices" to check if your phone is recognized. If not go into device manager, find the Google Bootloader drivers and install those.
NOW IS YOUR LAST CHANCE TO MAKE SURE EVERYTHING'S BACKED UP AND THERE!
Next type in "fastboot format userdata" and hit enter. This will completely wipe your device.
Boot back into TWRP by using the volume rocker and the Power Button.
ADB is probably not working now (will only report "unauthorized"), MTP however still works. Copy the TWRP folder we backed up earlier onto the device again.
Once copying finished restore the backup and reboot into recovery again. You're now able to use ADB due to the adbpub.key being present again. (You could've done this earlier but it's easier that way.)
Copy the rest back onto the device with "adb push / /data/media". (I'm not really sure if this command is right, beware!)
Now type "adb shell chown -R media_rw:media_rw /data/media" to fix issues later in the ROM.
You're basically finished now! Simply reboot and wait till it boots up again. If you're getting stuck at a "Wrong PIN" or "Wrong Pattern" screen SEE THIS COMMENT I made in another thread.
Finished!
As said, I'm not sure if I forgot something here or not. However I think I got everything covered
Click to expand...
Click to collapse
Will it wipe my rom too?? Or just internal storage??

Need workaround for flashing custom to my quirky N6

One of my N6s has a little trouble doing ADB.
When it's in stock, the phone will only accept ADB commands and show up in ADB Devices when the USB mode is set to MIDI. It doesn't work with ADB in MTP mode. But in MTP mode, I can drop files to the phone from Windows File Manager, but no ADB. In TWRP recovery mode, with MTP on I can't drop files to the phone. In TWRP, if I disable MTP, the phone no longer shows up in Windows. That's the background on this phone.
I'm trying to flash Pure Nexus, GApps, Magisk, and Franco Kernel to this phone without encrypting it.
As a starter step, I have flashed stock and TWRP to it without rebooting to the stock ROM (which would encrypt the phone).
(Note I know many people say encryption doesn't matter for better performance. Let's not get distracted by that discussion here. I'm trying to see if I can flash this custom setup without encrypting.)
I now need to get the Zips for PN, GApps, Magisk, and Franco onto the phone but am unable to use adb push command or Windows File Manager to drop those files.
So it has fresh stock and TWRP on it. Now when the phone is in TWRP, and I try to "adb push ROM.zip" I get an error: failed to get feature set: no devices/emulators found If I try adb devices it returns a blank list.
So while TWRP is on the phone i don't know other ways to push the Zips over to a folder on the phone.
In Windows File Manager I can see the device Nexus 6 and inside of that is Internal Storage. If I try to drop files to Internal Storage using Windows, it processes for a long time and hangs.
In Windows File Manager I cannot create a new folder on the phone when it's in TWRP mode.
In TWRP, Mount, the default boxes checked are Data and Cache. Others aren't checked.
Is there some other trick to getting those Zips onto the phone without booting the phone into Stock, thus encrypting the data? Thanks

wittier said:
One of my N6s has a little trouble doing ADB.
When it's in stock, the phone will only accept ADB commands and show up in ADB Devices when the USB mode is set to MIDI. It doesn't work with ADB in MTP mode. But in MTP mode, I can drop files to the phone from Windows File Manager, but no ADB. In TWRP recovery mode, with MTP on I can't drop files to the phone. In TWRP, if I disable MTP, the phone no longer shows up in Windows. That's the background on this phone.
I'm trying to flash Pure Nexus, GApps, Magisk, and Franco Kernel to this phone without encrypting it.
As a starter step, I have flashed stock and TWRP to it without rebooting to the stock ROM (which would encrypt the phone).
(Note I know many people say encryption doesn't matter for better performance. Let's not get distracted by that discussion here. I'm trying to see if I can flash this custom setup without encrypting.)
I now need to get the Zips for PN, GApps, Magisk, and Franco onto the phone but am unable to use adb push command or Windows File Manager to drop those files.
So it has fresh stock and TWRP on it. Now when the phone is in TWRP, and I try to "adb push ROM.zip" I get an error: failed to get feature set: no devices/emulators found If I try adb devices it returns a blank list.
So while TWRP is on the phone i don't know other ways to push the Zips over to a folder on the phone.
In Windows File Manager I can see the device Nexus 6 and inside of that is Internal Storage. If I try to drop files to Internal Storage using Windows, it processes for a long time and hangs.
In Windows File Manager I cannot create a new folder on the phone when it's in TWRP mode.
In TWRP, Mount, the default boxes checked are Data and Cache. Others aren't checked.
Is there some other trick to getting those Zips onto the phone without booting the phone into Stock, thus encrypting the data? Thanks
Click to expand...
Click to collapse
SUCCESS
Update: with some manipulation in TWRP, I was able to get a file system I could see and drop files to from Windows.
After flashing stock, and TWRP, and booting to TWRP (without ever booting to system/stock, which would have encrypted phone) i did the following.
I'm trying to remember all the steps but I think that Wiping the data and cache partitions via TWRP was the key, and required before I could move zips over to the phone.
I dropped the Pure Nexus, GApps, and Magisk onto the phone and then flashed them in that order via TWRP
Rebooted to system.
It installed and set up under Pure Nexus. It's reloading my apps from my Google account.
I checked Settings, Security and the phone is not encrypted.
I haven't yet checked on the GApps and Magisk. I assume I can install Franco Kernel from the Franco Manager app that I bought.

When you can't transfer files from PC to the N6:
Remove the drivers of the PC and let Windows search for the latest drivers.
Check on https://dl.twrp.me if you have the latest version of TWRP.

NLBeev said:
When you can't transfer files from PC to the N6:
Remove the drivers of the PC and let Windows search for the latest drivers.
Check on https://dl.twrp.me if you have the latest version of TWRP.
Click to expand...
Click to collapse
thanks. it is the latest TWRP.
I fixed it, see above, it wasn't the drivers on the PC.
The PC works with my other N6. This N6 has issues.
The workaround of wiping in TWRP fixed it. I don't know yet if I'd have to do the same wipe with my better N6. Will find out soon.

wittier said:
... I don't know yet if I'd have to do the same wipe with my better N6. Will find out soon.
Click to expand...
Click to collapse
Updating TWRP to the latest version is a good practice.

wittier said:
SUCCESS
Update: with some manipulation in TWRP, I was able to get a file system I could see and drop files to from Windows.
After flashing stock, and TWRP, and booting to TWRP (without ever booting to system/stock, which would have encrypted phone) i did the following.
I'm trying to remember all the steps but I think that Wiping the data and cache partitions via TWRP was the key, and required before I could move zips over to the phone.
I dropped the Pure Nexus, GApps, and Magisk onto the phone and then flashed them in that order via TWRP
Rebooted to system.
It installed and set up under Pure Nexus. It's reloading my apps from my Google account.
I checked Settings, Security and the phone is not encrypted.
I haven't yet checked on the GApps and Magisk. I assume I can install Franco Kernel from the Franco Manager app that I bought.
Click to expand...
Click to collapse
I updated my other N6 last night.
After flashing stock ROM and TWRP and booting to TWRP only, I didn't have to wipe before I could push files to the phone.
The other phone is more difficult.