Related
Hi guys,
I want to share my experiences about having ROOT + Encryption. This case of mine may pose as example for anyone who want to root their phones while want to have their device encrypted at the same time.
My phone is Samsung Note 3, Stock Lollipop 5.0, rooted with KingRoot 4.85 (kingroot.net). I think you can also have your phones to be rooted regardless of rooting mechanism. I picked KingRoot because it was the one successfully rooted my device without installing any custom recoveries, which is really IMPORTANT if we want to apply device encryption..:fingers-crossed:
Previously I posted question here : http://forum.xda-developers.com/showpost.php?p=66643426&postcount=4538
No answer there so I keep tinkering and googling then found this thread : http://forum.xda-developers.com/z3-...-device-encryption-root-t3338691/post66615860
On my case, my Note 3 was not encrypted (also have unencrypted external 32GB MicroSD), then I rooted it successully via exploit. I then started device encryption without any problems. I also have frozen Knox and many other Samsung bloatwares before started the encryption.
The conclusion is, as long as your rooting process didnt involve custom recoveries then you are good to go with device encryption, whether root first later encrypt or encrypt first then root later.
I am not expert and hoping this small info can help other non experts who want to taste rooting privileges while preserving device encryption.
Cheers
I am using CM12.1 (Android 5.1.1) custom ROM, IdleKernel 7.1.0 custom kernel, TWRP 3.0.2 custom recovery and my encryption works just fine.
What's performance like with encryption?
I haven't noticed any difference with my day-to-day usage.
Hello,
good for you, I got my Galaxy Note 3 yesterday. I went first of all to have it encrypted and it's not booting after the encryption It's not rooted, basically I launched the encryption as one of the first operations :-/
Hi,
very interesting thread. I rooted as well my S7 but installed TWRP - so the bootloader is unlocked and it seems, that an encryption doesnt make much sense.
If I got you right, an installation of a cfw with the described procedure isnt possible.
Is there a way, if you have already installed a custom recovery to get a S7 encrypted and rooted?
Today I tried 3 different strategies for getting my phone encrypted - none of them worked
Each time the phone reboots within 2-3 minutes and nothing gets encrypted. @tefole - I was only successful with the ROM of the polish guy (artas...), his ROM is excellent, but I can't see the SD card when I connect the phone to my laptop, so it's again a NO-GO
darkman088 said:
Today I tried 3 different strategies for getting my phone encrypted - none of them worked
Each time the phone reboots within 2-3 minutes and nothing gets encrypted. @tefole - I was only successful with the ROM of the polish guy (artas...), his ROM is excellent, but I can't see the SD card when I connect the phone to my laptop, so it's again a NO-GO
Click to expand...
Click to collapse
Till now, i were also not able to get it run.
In other threads i see people, which were successfull - with restrictions.
I am shocked a bit, why this "encryption on rooted phones" topic is not treated very much, because you dont get much information.
It seems, or this means that most of the guys are dont care with their data, if they lost their phone.
Imagine, you lose phone or get it stolen and you dont figure it out immediately:
whatsapp/threema chat history and the corresponding meda (in my case: 5 years old)
contacts
all emails!
photos / DCIM
social media account: instagram, twitter, etc..
google drive
downloads and documents
connection to my homenetwork (openvpn)
An encrypted phone is a important but imho is rooting a must-have too, to get your phone debloated and for using xposed, adaway, xprivacy, etc...
I guess, a conflict of interests.
@Galactus described me a way here.
From what I understand is the way:
-flash stock firmware (stock firmware is delivered with already encrypted partitions)
-root with CF-autoroot
-you can flash TWRP as well
-restore or flashing of any CFW is not possible with TWRP
quite a lot compromises - if you want to encrypt ur phone.
I renounce on features and comfort, before i risk to share my life with a thief
tefole said:
Till now, i were also not able to get it run.
In other threads i see people, which were successfull - with restrictions.
I am shocked a bit, why this "encryption on rooted phones" topic is not treated very much, because you dont get much information.
It seems, or this means that most of the guys are dont care with their data, if they lost their phone.
Imagine, you lose phone or get it stolen and you dont figure it out immediately:
whatsapp/threema chat history and the corresponding meda (in my case: 5 years old)
contacts
all emails!
photos / DCIM
social media account: instagram, twitter, etc..
google drive
downloads and documents
connection to my homenetwork (openvpn)
An encrypted phone is a important but imho is rooting a must-have too, to get your phone debloated and for using xposed, adaway, xprivacy, etc...
I guess, a conflict of interests.
@Galactus described me a way here.
From what I understand is the way:
-flash stock firmware (stock firmware is delivered with already encrypted partitions)
-root with CF-autoroot
-you can flash TWRP as well
-restore or flashing of any CFW is not possible with TWRP
quite a lot compromises - if you want to encrypt ur phone.
I renounce on features and comfort, before i risk to share my life with a thief
Click to expand...
Click to collapse
Yes, I am very worried about the situation you describe, and I don't even have half of the things you describe! And I'm so glad that you are using Threema. I couldn't convince any of my friends to install it - they use WhatsApp and Viber and when I mention privacy, they always keep saying - I have no secrets, I have nothing to hide and nothing to be afraid of. No comment...
And about encryption - the funny thing is, that I couldn't encrypt it with the stock ROM, this is why I rooted it - to be able to install a custom ROM. and now it's such a hassle to get it encrypted when it's been rooted! What an irony!
So I think that the only option for me is to use the Artas ROM, as it can encrypt the phone itself. But with it, I don't see the SD card when I connect the phone to my laptop - it means that I can copy a lot of data only to the phone and will then need to move it to the SD card - quite uncomfortable.
And also it's not possible to encrypt the SD card - but let's say, I'll put only mp3s and movies on it, so nothing really secret. Then another possibility is to return the phone and get another one, but I don't really have an alternative - maybe LG G4, but I think that the Note is much sweeter...
Or get an iPhone out of frustration
OK, so that's it ? No help, no support, no suggestions ?
I had expected more interest in this...
Hello, sorry for late replies on my thread as if my replies would even help though.
I still have the Galaxy Note 3 (Rooted) with Stock 5.0 Lollipop as described on this post. Please be reminded I was not using any custom recoveries.
Recently this phone came into this situation :
Previously working external 32 GB Samsung Evo Micro-SD is no longer capable to be used in encrypted form. First I though failed cards but then tried with other cards came with same problems, they all can be used in "unencrypted form".. so weird. If I try to encrypt it it says "Unable To Mount SD Card" which is weird since it can be mounted and used properly while in unencrypted form. This situation happened while internal device still in encrypted form. I then tried to decrypt all of them, both external and internal storage, weirdly it is succeed. At this point then my device really naked, non of storages are in encrypted form.
I then tried again to encrypt my internal storage (device encryption) with external SD card detached from device, with more than 10 failed trials resulted only as regular restarts then at 11th or so trials it then came into proper reboot and properly start encrypting my device (external storage was detached before process).
Right now the device is only have internal storage encrypted with external storage UN-encrypted. Maybe some days in future I will try again to re-encrypt the external sd card but so far internal storage encypted is enough while stays rooted. For anyone of you outthere who face regular restart without result when trying to encrypt via settings, dont give up! They tend to do stupid restarts but at some point they will sober and do proper encryption process. I was successfull re-encrypting internal storage after 11th or so reboots. Going with some cool drinks and listen to jazzy music before doing encyption helped much to the soul.
Hi guys,
is it possible to gain a temp root through adb?
after upgrading from Android 4 to 6, there are some applications that has been removed.
For example, Microsoft Account application which provide you the 2-step authentication for your accounts.
I can't install it anymore, i keep getting error code: -505
which is probably related to some data already present on the device which it cannot erase.
right now, that there's permission management for application, i don't see any real reason to be rooted.
therefore, my question is if i can remove this specific application data from the data partition without being rooted?
Thanks
I've read since day one of my Android experience that when you upgrade a full version (as opposed to small incrementals) such as Kitkat to Lollipop, or Lollipop to Marshmallow, you should back up, do a full wipe, and reinstall all your apps from scratch. You have upgraded two full versions, so it's not surprising that you're having problems. Rather than messing around with temporary root and deleting from partitions you should be doing it right as I've stated above.
Thanks dahawthrone,
This might work indeed but will take too much time to accomplish.
not really worth it.
Really? You prefer to put up with a broken phone? This is just one symptom of corruption. Who knows how many others there may be? And particularly with something as important as 2-factor authentication...
root ur phone do wht ever u need to do then unroot through super user
and yes u can delete data from data partition using es explorer and after everything is done unroot ur device through super user!
not broken.. just having a difficulties with his specific app
I just solved it.
root was not needed, although, usb debugging mode was mandatory.
through adb:
1. adb uninstall com.microsoft.msa.authenticator
2. adb install com.microsoft.msa.authenticator-2.apk
and we're done, works like a charm!
thanks for all the advice's.
Guys, apologies if the question is silly / already asked somewhere i wasn't able to locate.
As per thread title, what is that all about? 1. It's an expected behaviour / feature of TWRP, or is it kind of a bug? 2. Is there any way to avoid / disable it?
It's quite annoying during these days of frequent flashing as development is speeding up fast for this little beast.
If you have a pin or pattern set up it will always ask you for it.
sting5566 said:
If you have a pin or pattern set up it will always ask you for it.
Click to expand...
Click to collapse
Well, thanks for pointing that out.
I've been outside of the flashing world for a while with my old phone (OP2), but i'm pretty sure to recall that i was using TWRP 3.X and the pin was setup (due to fingerprint usage for unlocking) and the recovery was not asking for any decryption pwd.
Maybe the OP2 was not encrypted and that's the point. So wondering if future development will change this (are custom ROMs usually decrypted?)
It's something completely outside of my knowledge, so i could just be trashtalking here.
ca110475 said:
Well, thanks for pointing that out.
I've been outside of the flashing world for a while with my old phone (OP2), but i'm pretty sure to recall that i was using TWRP 3.X and the pin was setup (due to fingerprint usage for unlocking) and the recovery was not asking for any decryption pwd.
Maybe the OP2 was not encrypted and that's the point. So wondering if future development will change this (are custom ROMs usually decrypted?)
It's something completely outside of my knowledge, so i could just be trashtalking here.
Click to expand...
Click to collapse
If you don't want to enter anything when twrp starts under security , screen lock change that to none and you shouldn't have to put anything in when twrp starts.
ca110475 said:
Guys, apologies if the question is silly / already asked somewhere i wasn't able to locate.
As per thread title, what is that all about? 1. It's an expected behaviour / feature of TWRP, or is it kind of a bug? 2. Is there any way to avoid / disable it?
It's quite annoying during these days of frequent flashing as development is speeding up fast for this little beast.
Click to expand...
Click to collapse
It is a security issue. If you need pass/pin/pattern to keep your phone secure then logically you should have it required in twrp to prevent unauthorized access to your phone through twrp. You can disable pass/pin/pattern from the twrp file manager
Sent from my OnePlus6 using XDA Labs
Just decrypt your phones storage. You want be asked for a pattern / pin anymore in twrp
matze19999 said:
Just decrypt your phones storage. You want be asked for a pattern / pin anymore in twrp
Click to expand...
Click to collapse
How?
mikex8593 said:
How?
Click to expand...
Click to collapse
I'm not so sure you can actually decrypt the phone's storage and the reason I believe this to be so is the day I received my phone I was going through all of the settings. If you go into security and lock screen and scroll to the bottom you will see that your phone is encrypted. My phone was like this from day one without entering any fingerprint or PIN code. I may be wrong about decrypting the storage however the OnePlus 6 does have an EFS (encrypted file system) which stores meid, imei, serial number, config, diag settings and radio settings, etc in an encrypted format at the file system level.
If you do manage to decrypt your storage your phone will most certainly be vulnerable
dgunn said:
I'm not so sure you can actually decrypt the phone's storage and the reason I believe this to be so is the day I received my phone I was going through all of the settings. If you go into security and lock screen and scroll to the bottom you will see that your phone is encrypted. My phone was like this from day one without entering any fingerprint or PIN code. I may be wrong about decrypting the storage however the OnePlus 6 does have an EFS (encrypted file system) which stores meid, imei, serial number, config, diag settings and radio settings, etc in an encrypted format at the file system level.
If you do manage to decrypt your storage your phone will most certainly be vulnerable
Click to expand...
Click to collapse
I've always been decrypt with previous phones. There is no decryption method with the 6 yet because of the a/b partitioning. You need to flash a modified boot img.
mikex8593 said:
I've always been decrypt with previous phones. There is no decryption method with the 6 yet because of the a/b partitioning. You need to flash a modified boot img.
Click to expand...
Click to collapse
If you were to decrypt your data (and you can through either adb or fastboot - but I,m not going into that here), you would wipe it at the same time.
There's no way around this.
carlos67 said:
If you were to decrypt your data (and you can through either adb or fastboot - but I,m not going into that here), you would wipe it at the same time.
There's no way around this.
Click to expand...
Click to collapse
With that, I am aware of the wipe, but it would be a prepared and willing wipe, but you are right, this is not the place for the discussion.
Hey all,
I unlocked bootloader, installed TWRP and installed Magisk just fine.
As far as I was aware, I had disabled encryption on the sdcard, and this makes sense as I flashed Magisk from its installation zip in my sdcard.
However, I just rebooted to recovery in order to make a backup
It prompts me to input password in order to decrypt data.
I don't need to input password, I can click cancel and get to TWRP, but then, using its file manager, I see that all file names are in gibberish. Obviously the personal data Partition is also read only
I don't know how it got encrypted, and it was after I installed Magisk from sdcard, showing it was not encrypted at some point.
Well I can't make a TWRP back in this state.
Anyone know how it got encrypted again and how to undo that so I can make backups?
for decryption you have to do fastboot format userdata . and till the time you have stock rom you will have encrption coz it comes with encryption enabled.
Ajaykumar21066 said:
for decryption you have to do fastboot format userdata . and till the time you have stock rom you will have encrption coz it comes with encryption enabled.
Click to expand...
Click to collapse
Thanks for replying!
That's sounds very "destroy all settings". I wish I knew that before I really moved into the phone. ?
But then, I am confused as to how I could install from sdcard before. It included a manual system update zip, twrp and magisk. There was a point when I could read the sdcard content in twrp. At what point did it change?
I don't suppose anyone knows a way to backup while twrp can't access sdcard? Adb sideload probably only allows flashing a zip, and probably can't transfer data in the opposite direction. USB otg could be an option I suppose!
Sent from my OnePlus 6 using XDA Labs
drakenabarion said:
Thanks for replying!
That's sounds very "destroy all settings". I wish I knew that before I really moved into the phone.
But then, I am confused as to how I could install from sdcard before. It included a manual system update zip, twrp and magisk. There was a point when I could read the sdcard content in twrp. At what point did it change?
I don't suppose anyone knows a way to backup while twrp can't access sdcard? Adb sideload probably only allows flashing a zip, and probably can't transfer data in the opposite direction. USB otg could be an option I suppose!
Sent from my OnePlus 6 using XDA Labs
Click to expand...
Click to collapse
only change was you didnt have any lockscreen pin setup on your phone, And now you have one i think. its the same pin twrp is asking for.
Ajaykumar21066 said:
only change was you didnt have any lockscreen pin setup on your phone, And you have one i think. its the same pin twrp is asking for.
Click to expand...
Click to collapse
Oh right! That's great. I guess I come from phones where the encryption was not so user friendly. Huawei phones have encrption keys that they never share with the user because they have no desire to help with modding or customisation. So if it asks for a password, there was almost no way a user could know it.
OnePlus feels so so open in comparison! ??
Sent from my OnePlus 6 using XDA Labs
drakenabarion said:
Oh right! That's great. I guess I come from phones where the encryption was not so user friendly. Huawei phones have encrption keys that they never share with the user because they have no desire to help with modding or customisation. So if it asks for a password, there was almost no way a user could know it.
OnePlus feels so so open in comparison!
Sent from my OnePlus 6 using XDA Labs
Click to expand...
Click to collapse
Yeah , things have changed quite a bit, we can decyrypt the device with the command i mentioned , and twrp wont ask for the password. but the only problem is we dont have any other stable rom to flash after that , and if flash stock rom it encrypts the data again.
For now thats the thing, but it will change once we have new roms that are not based on stock or a flashable zip can be used on top of stock to prevent encryption, but all this development will take time since we have Treble A/B partitions now.
Ajaykumar21066 said:
Yeah , things have changed quite a bit, we can decyrypt the device with the command i mentioned , and twrp wont ask for the password. but the only problem is we dont have any other stable rom to flash after that , and if flash stock rom it encrypts the data again.
For now thats the thing, but it will change once we have new roms that are not based on stock or a flashable zip can be used on top of stock to prevent encryption, but all this development will take time since we have Treble A/B partitions now.
Click to expand...
Click to collapse
The important thing for me now is that I have a stable backup. It can take me days to setup a new phone to my comfortable default setting, so now I feel secure that I have a saved image of my idea of a good install. So thank you for helping with that!
But it will be interesting to see how custom roms not based on OOS will be.
Up until my last phone (Honor 6x - proprietary soc, therefore limited rom support), I would flash a custom rom ASAP (typically LineageOS or before that, CyanogenMod). But I already get that kind of experience (with good historical reasons I guess) from OOS. It would take a bit to tempt to flash something else. ?
Sent from my OnePlus 6 using XDA Labs
And might I just say that woohoo for large storage! My previous 32gb phone took 10 gb for firmware and left me struggling after installing a normal set of apps, typically leaving me about 10gb to put music etc into. My backup that I just made took 18gb, because I installed alot of games I couldn't before, is bigger in general than base free space before!
Hi, first of all, thank you for reading me.
I think i messed up big time.
I had Havoc OS 4.1 installed since more than a year and it was kinda messy e.g. the sim card card wasnt recognized anymore so wasnt able to make calls because i played to much in the settings.
Having some stupid but incredibly addictive games on this smartphone i decided to keep it like this and since i'm a complete n00bs and being afraid of security risk of rooting my device i never rooted it.
Big mistake.
So, recently, one games needed an update (like they all do at least once a week) and since i'm anti-google/f***book (no comment please) i nvever saved my progress in the cloud and "that" game required absolutely an update.
I installed the update from an alternative apk source and , (applause if you want and laugh), it screwed up the game.
Now the nightmare begin.
Since the device isnt rooted i made a backup of /data partition. Gone crazy and before i might explode in an uncontrollable fury and madness i used LMSA to rescue the phone. And myself, lol.
Now i have stock android and i am googled to the bone. My butt hurts. My head too.
THE (first) simple question is : how can i restore this backup because i have the error 255?
Notes and observations; logically i would say because the device is back with stock rom and doesnt have the same os/rom installed and/or the partition and whatever is not the same wich may explain the error 255.
SECOND QUESTION: can i extract/uncompress this backup and take the precious data wich is my games progresses and restore it somehow?
I know i have to give as much information possible but i dont what else to give. If you need logs, or everything else just say it nicely and i will give it to you with immense pleasure.
Oh yeah, model : XT2113-2 5g Kiev RETCA 128gb a/b type and maybe was crypted before because twrp asked me the password to make backup or else.
Thank you in advance and i really hope somebody would help, if not i just loosed 1.5 years of stupid gaming because i messed up like an idiot. (A lesson well learned, the hard way...)
Thank you so much for not answering this simple question.
Kerplunk83 said:
Thank you so much for not answering this simple question.
Click to expand...
Click to collapse
The problem is it's a Motorola with a Qualcomm chip.
If you find a solution I would love to see it.
Finally a sign of life from someone here.
Thank you sd_shadow
sd_shadow said:
The problem is it's a Motorola with a Qualcomm chip.
If you find a solution I would love to see it.
Click to expand...
Click to collapse
These precious brief and concise 2 lines of a simple answer is immensely welcomed.
Wich point me to reply that to my knowledge i interpret it as a security chip with big chances that its in relation to the knox technology.
It also point me to ask WHY, if i cant back up because of that, why/how is it possible to install a custom rom or gsi (sorry i still dont make the difference because i dont understand it) on this very protected smartphone?
That must explain why i had problems trying to root it and fail each time.
Finally i think that i should use another device for android gaming since i dont want to depend on f***book and google.
Thanks again sd_shadow. Even if it was a very simple answer it enlightens me alot.
Note: sorry for my bad english.
Kerplunk83 said:
how can i restore this backup because i have the error 255?
Click to expand...
Click to collapse
This error code means that at some point your backup of /data could not be extracted further. But for more detailed infos you must provide a recovery.log which will be generated when doing a backup of e.g. /boot.
>>> Please DO NOT copy+paste it here!! <<<​Rename it (recovery.log > recovery.log.txt) to be able to upload it within "Attach files".
Kerplunk83 said:
can i extract/uncompress this backup and take the precious data wich is my games progresses and restore it somehow?
Click to expand...
Click to collapse
Yes, use Titanium Backup (TB). Although it's very outdated it still features a restore of single apps out of a TWRP backup. Here's how you do it:
1. IMPORTANT: TB will only search for TWRP backup files on internal storage!! Use the default path created by TWRP, e.g.: /sdcard/TWRP/BACKUPS/ZY322V8K28/2023-04-08--06-53-20/
2. Install and open Titanium Backup.
3. In the upper right corner tap
MENU > scroll down to "Extract from Nandroid backup" > choose your backup folder
##############
Notes:
- Usually a TWRP backup of /data consists of several parts (data.ext4.win000, ~win001, ~win002 etc). TB requires all of them (or at least those ones with the /data/data/ path inside).
- If you are facing this error message:
Could not find any data in this TWRP backup
then your TWRP backup is compressed with gzip. To decompress it you must rename the file
data.ext4.win001 > data.ext4.win001.gz
and extract it with any archiver tool, e.g.:
- ZArchiver (Android)
- 7zip (Windows)
- Problems finding any TWRP backup data with Titanium Backup? Then please check your path!! (see above section)
Good luck!!
Thank you very much WoKoschekk i'll do it as soon i'll have the time for since i'm working today.
Thank you so much again, i'll keep you posted with logs and such.
I'm sorry i didnt gave news since, i'm not doing very well.
there's those 2 question i still have in my head;
1-With all the instructions you gave me is it worthy to continue because when i did the backup i wasnt rooted?
2- i'm sure i read many time to use Titanium Backup (wich is a paid app?) i have to be rooted or have root access.
Ultimately, how can i be rooted if there's a chip preventing me to do so?
I'll keep you posted when i'll be of better health, thank you.
Kerplunk83 said:
-With all the instructions you gave me is it worthy to continue because when i did the backup i wasnt rooted?
Click to expand...
Click to collapse
TWRP backup = *.tar archive
TB unpacks the needed app's data and nothing else. You must be rooted to have access on /data for restoring your apps. But for the backup process it doesn't matter if you were rooted. Root is part of your boot.img.
Kerplunk83 said:
2- i'm sure i read many time to use Titanium Backup (wich is a paid app?) i have to be rooted or have root access.
Click to expand...
Click to collapse
TB is for free. But a paid version unlocks additional features (not related to the TWRP restoring feature).
And yes... root is mandatory for TB. As I said before you must have r/w access on /data/*.
Kerplunk83 said:
if there's a chip preventing me to do so?
Click to expand...
Click to collapse
Which chip?? You already have root access via TWRP. Magisk is only needed in system and just a patched boot.img (custom kernel).
Get well soon!
WoKoschekk thank you for this insanely fast reply.
All those answers and infos have now a gigantic value for me, if only i knew that before.
To describe a bit more my situation i slept only few hours since 5 days, vomiting, heavy coughs and fever.
I'm sure i'm not supposed to but i will anyway, i engage myself and promise to reward you (in particular) and others for the help you're bringing me. It wont be much but very important to me.
I'll go try to get (again) some rest. Just before i go, why was there a mention about my device;
"
The problem is it's a Motorola with a Qualcomm chip.
If you find a solution I would love to see it.
"
I dont ask you (WoKoschekk) or other to explain in the most explicit and endless details of what is exactly this "chip" and all the history that goes with it cause i dont want to be a pain but just why it was mentionned. Only, why?, it has ben mentionned.
I cant wait to get better since i finally see possibilities to get back those files.
Have a nice week-end and thanks again.
@Kerplunk83 To reveal the mystery behind "the chip": Motorola released two variants (Snapdragon/Mediatek CPU) of this model. Since the CPU largely determines the system structure, building a functional TWRP for both of them is very challenging. It seems that TWRP for the SD's variant got some bugs while the MT's variant runs more smooth. Due to this fact the error 255 is caused by something that you weren't be able to fix.
Regarding your problem: To restore an app and its specific app data you need the proper permissions to write in /data/data and /data/app. For this permissions you either need TWRP or Magisk installed. TWRP seems to be unable to write in that specific directory. On the other hand you don't want to install Magisk. I'm sorry but with this setup your problem can't be fixed.
Just out of curiosity, could you provide me a recovery.log showing error 255 during the restore process?
Please DO NOT copy/paste the whole log and post it here!! Instead of this you should rename the file (recovery.log => recovery.txt) because a file called *.log isn't allowed for upload. But a *.txt file is.
Options to create a recovery.log:
1. adb pull /tmp/recovery.log
=> copies a recovery.log into your ADB/fastboot folder
2. Do a backup of sth. like "boot" because the backup process will create a recovery.log by default
3. TWRP mainscreen > advanced > create log (kernel log isn't needed here)
=> log is stored on the default storage (internal or external) that you have choosen for backups etc.