Galaxy Note 10.1 (2014 Edition) P-605 Official LineageOS - Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl
I downloaded and installed official LineageOS to my Galaxy Note 10.1 (2014 Edition) P-605 from
https://download.lineageos.org/lt03lte
Install TWRP Recovery
Install latest downloaded file from the link given above
Install open gapps (mini)
Everything working fine except
Usb MTP connection is not working
On boot Setting app closes
Less battry life than the stock rom
MTP connection issue is a huge problem for me. Do anyone know a fix? I searched everywhere and couldn't find anything
I confirm all the above issues with the nightly build 2018-02-22.
Let me add another (serious) one: if you encrypt the storage, every time you reboot a bunch of applications go in restart loop, until eventually the device restart. This is basically a bootloop. I will try to wipe cache and dalvik and restart to see if the problem persists.
I'm not used to rant just for the sake of, also considered the amazing work devs do, but this time I'm a bit pissed. I bought this tablet specifically because it is listed in the "Lineage OS supported devices" list. It would be nice to put a big disclaimer if the current build has so many crippling issues.
---------- Post added at 10:39 AM ---------- Previous post was at 10:16 AM ----------
That's annoying... TWRP does not manage to decrypt the storage partition... So I'm pretty much screwed.
I will try to format the storage to remove the encryption, and then re-install the latest Lineage nightly using either adb sideload or a micro-USB pendrive.
OK, kind of works. I started TWRP recovery and formatted all the device (removing encryption), then copied back the lineageOS (I used the last nightly, 2018-02-22) and addonsu zip files using a microUSB stick. Reinstalled everything. It works, the only annoying thing is that by formatting the sdcard I lost the backup I had previously done with TWRP of the original firmware, but that's fine, I was not planning of using it anyway.
- enabled USB debugging, root apps+ADB, enable third-party apps
- added F-Droid repo
- downloaded CryptFS from F-Droid
- Settings -> Security -> set up a temporary password for screen unlock
- Plugged in tablet, Settings -> Security -> encrypt device (using the temporary password above)
- reboot, this time seems to work (modulo the usual annoying "settings app has stopped working" one-time popup)
- changed encryption password with CryptFS (requires root of course)
- Settings -> Security -> changed screen unlock to a normal PIN
Everything seems to work so far: the device asks for the long decryption password at boot but only short PIN to unlock screen.
Planning to install WrongPINshutdown now, to complete anti-theft security setup.
So far so good, except ADB still doesn't work. Keeping a close eye on battery usage.
Coming next:
- testing whether TWRP can decrypt storage
- making sure at least LineageOS can mount USB drives... since MTP doesn't work it would be annoying having to use network or ADB to transfer large files...
---------- Post added at 01:17 PM ---------- Previous post was at 12:59 PM ----------
Babality!
- TWRP still cannot decrypt storage, does not even ask for the passphrase, just does not see the partition
- after trying the above, somehow the encrypted partition header got screwed: if I start Lineage OS, when I'm prompted for the passphrase. I always got "wrong password". Either using the "right" password, or using the old temporary password I used before, or the current device PIN, nothing: everything is "wrong password".
I'm reinstalling everything again and do a couple of final tests before giving up and forgetting about encryption.
I suspect this might be an issue of TWRP. I'm using version 3.0.2-0. I'm installing now the latest version (3.1.1-0) and see if things change.
Also, coming next MTP test.
---------- Post added at 01:37 PM ---------- Previous post was at 01:17 PM ----------
TWRP 3.1.1-0 bootloops tablet... I have to start from Odin again.
F**k all this s**t, my next device's gonna be an Apple :angryface:
I managed to make the double-encryption work: now when I boot the tablet it requests the passphrase, but to unlock the screen just a PIN (however, Wrong PIN Shutdown powers off the tablet after a few wrong PIN trials).
I'm not entirely sure how I did it to be honest, but I suspect the reason is the following: the encryption of the tablet can only be done by setting up a password for screen unlock at first.
Then you use Cryptfs to change the encryption password.
Then you change the screen protection option to "PIN" instead of password. If you are running one of the latest Lineage OS builds, when you are asked "do you want to require a PIN also at boot?", counterintuitively, answer "yes".
THEN you must run Cryptfs again and re-set the storage encryption password. This way it works.
I did not dare starting TWRP again in recovery mode , I'm afraid it would mess up with the encryption.
Keeping an eye on the battery: it's pretty bad to be honest. I was used to my beloved Lenovo tablet, I was using it only as a PDF reader (flight mode, uninstalled all the crap etc) and, with the stock firmware, it had pretty much the same battery life of a real Ebook reader, I could easily leave it in the closet for weeks and find it still charged when I needed it. This Galaxy Note 10.1 is not even close with Lineage 14.1, now I killed all the unnecessary processes and set battery mode to maximum span, let's see if it gets better.
After a few days of test I can confirm poor battery life. Less than two days in complete standby, flight mode, energy saving mode. That really sucks.
I have to add: SIM card not recognized, only WiFi works.
TL;DR: do not install this ROM.
Did anybody test the official LineageOS build for the SM-P605 (lt03lte) ?
Is it working by now?
Has anybody an old (Octobre or Septembre) version of the official LinageOS for SM-P605 (lte03lte)? Unfortunately after the decision to no longer maintain that ROM all older downloads have been deleted and I have some problems with the december version
Related
[Q] Prompted for Device storage encryption password after decryption
I had encrypted enforced through a company policy. Device worked fine no problems. Enter pin at boot and in we go. This policy was removed and I de-encrypted the device. Still no problems. The device clearly showed it was not encrypted and I had the option to encrypt - so all good so far. I rebooted the device and was asked for my device storage password. I entered my old pin and it booted ok. Bit strange I thought but device works so that's good right? So I did a factory reset. Same thing happened. prompted for a PIN I re flashed the phone back to the original carrier ROM - same thing. Still being prompted for PIN. I installed TWRP 2.6 and did a format - same thing. Does anyone have any idea how to get rid of the encryption? (Well the fact it keeps asking for the de-encryption PIN - as its actually not encrypted) thanks
backup password
wondering if there is a workaround for this,my tablet has given me no issues,up till now...this morning it was asking for a backup password(which i cant remember) i normally use pin or fingerprint for security...any help..kinda vexing
Did you setup a Samsung account? This worked for a coworker with a S5 - fingerprint scanner went wonky and she forgot her backup password as well. Try doing this: View attachment 3712498 Source: http://trendblog.net/how-to-bypass-android-phone-lock-screen-pattern-pin-password/
so im not the only one, this happened to me as well, no finger scanning option only backup password (which I cant remember) what I did is delete 2 files using TWRP file manager under data/system password.key and gesture.key. reboot your phone and you'll end up with a swipe to unlock go to settings and change your backup password (will prompt fingerprint) . you may activate your lockscreen with fingerprint again, it may ask you for the backup password but this time, you already know what it is and once you put it in, everythign should be back to normal let me know if you have question ---------- Post added at 11:44 AM ---------- Previous post was at 11:42 AM ---------- -- additional: the steps above is assuming that you got locked out and cant get past through your lockscreen.
Encryption not active... but it should
Hi Guys, My OnePlus 3 ist rooted, open Bootloader + TWRP. Oxygen OS 3.2.4 is running. First time I used the device, encryption was offered to me - so I set it up. I than used the phone for about 2 months, always had to enter a Passphrase when I rebootet. I noticed, that if I use TWRP I can browse through my personal files without entering any credentials. System-Preferences says: "Phone Encrypted". Do you have any suggestions for me?
I´ve found the solution by myself. Anyone who is having the same issue, read this thread: http://forum.xda-developers.com/oneplus-3/help/questions-encryption-unlocked-op3-t3427360/page2 You have to set up the display security again and activate the checkbox "PIN/Passphrase is needed to start the device".
Password protected phone
Ok, Ill admit I didnt research things fully, and went on my merry way flashing things mercilessly in hopes to find something I really liked. I ended up flashing a 7.0 rom and it wanted me to add a fingerprint, which meant I added a pattern. This put that damn pattern everyway, except fastboot/bootloader I wanted to remove it, a user suggested a delete userdata and rebuild - I did that, only I deleted everything, all partitions. Now, the code representation of my pattern doesnt work and recovery doesnt do much, doesnt mount anything. Where, Im currently at / things Ive tried to get going again: adb sideload: seems to work, says it serving the file, but nothing happens ( thought it was immediately supposed to start installing? ) Cant seem to find the file in sdcard or sideload. I suspect its because things are not being mounted. fastboot works as Ive tried reinstalling TWRP in efforts to remove the damn password. That seemed to have installed, but the password persists and my old one ( the pattern above ) does not work. Please tell me how to correct this password madness and get a working phone again.
same here +1
Ok so I flashed: cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J6-oneplus3-recovery.img from https://download.cyanogenmod.org?device=oneplus3 and did a factory reset and Im up and running again.
You can turn off PIN on boot/ boot into TWRP but it's enabled by default and it's not obvious how to do it. You have to turn off the pattern (set your security type to None), then re-enable a pattern. At that point it will ask you if you want a pattern on boot or not.
Follow the path.. What'd I do?!
Hey guys - Need some detective help. I did something to my 10, and I think I did something with the encryption, but I'm not sure how or what. Follow me here, since I'm not sure what caused it, I'll start at the beginning, and see if anything raises a red flag.. Got phone from HTC, US unlocked version. Got it in.. heck, this past June, I think. Unlocked bootloader. Got Sunshine, ran it, but never paid and never turned S-OFF. Never set PIN or Fingerprint. Installed Viper10 when it was out. Went to do fingerprint. Got screen saying that for backup, needed to set PIN. Set PIN, then taught it some fingerprints. Never had data issues, and as far as I know, never encrypted phone. TWRP, when run, did not need me to enter any password or key to access the phone. On bootup, would get PIN prompt, but AFTER Android loaded. Never got any RUUs, never upgraded Viper10. Installed CM13 today. Whohoo! Install went fine, no issues. Restored apps from TiBu, deleted unused bloatware, including the built-in Android keyboard. Set up other options, and finally got to enter in fingerprints. It gives me the same screen I got on Viper. This time, though (and I have no idea why), I back out back to Security settings, and enter in PIN there. Then train fingerprints! Now, when I reboot system, or boot to TWRP, I get a prompt asking for password (TWRP) or PIN (Android). HOWEVER.. I can enter my pin in TWRP just fine. But not Android. Apparently, since it hasn't booted, Swype doesn't work, and I get no keyboard. Can't enter PIN in at all. That is my mistake, however, as I removed the built-in Android keyboard. (Something I've done countless times before on other Android versions without issue..) So I restore Nandroid backup of Viper10. I still get the PIN entry, and STILL have no keyboard. I see reference in TWRP about PINs not working, so I delete that locksettings.db file (from memory, filename is likely wrong here..) Phone boots up. Yay. No PIN prompt. Yay. But now I do NOT have data - as in, it's acting like my phone is unencrypted now. So, what I'd like to know is - If NOW my phone is unencrypted, and I'm getting the 'No Data' issue, what was my phone doing BEFORE, when I didn't have to enter PIN, but was getting data? How can I get BACK to not having to enter PIN and still get data? (In my case, will the instructions for unencrypted work? Or is my phone now 'special'?) How did I set the PIN the first time on Viper10, and not have it encrypt my phone? I'd like to ultimately get back to THAT scenario - where the lockscreen asks for PIN, but nothing else does (TWRP, Bootup, etc). Thanks guys! -Mike
I may be pointing the obvious, but have you do a full wipe before restoring your nandroid? If so, did you try to clean flash your rom to see what happens? Maybe by removing stock keyboard something got messed up and keeps the keyboard in your nandroid from properly installing.
Yup, I tried restoring the Nandroid several times, some with wiping, some without. Also, I always clean-flash my new ROMs (i.e. ones not restored from nandroid backup, installed new, like going from Viper10 -> CM13) Going to try again today while at work, see what happens.
During setup in CM13, there should be option to require PIN at startup (It is usually checked by default). Uncheck it and your phone will remain encrypted without requiring a PIN to start.
jackebuehner said: During setup in CM13, there should be option to require PIN at startup (It is usually checked by default). Uncheck it and your phone will remain encrypted without requiring a PIN to start. Click to expand... Click to collapse Technically correct (encrypted) but effectively incorrect: encryption is moot if a password is not required to decrypt it. It would be like locking your door and leaving the key in it: it's locked but it's not secure. You need a system keyboard to be able to enter PIN on bootup; hence, the pre-installed keyboard (Google on vanilla, TouchPal on htc) isn't really 'bloatware' as it's necessary. Google makes a good keyboard; TouchPal, though, yeah, necessary bloatware in this case.
Rolo42 said: Technically correct (encrypted) but effectively incorrect: encryption is moot if a password is not required to decrypt it. It would be like locking your door and leaving the key in it: it's locked but it's not secure. Click to expand... Click to collapse Ah, so in previous ROMs (both OEM and Viper10, it technically WAS encrypted, I just never set the password? .. Huh. Rolo42 said: You need a system keyboard to be able to enter PIN on bootup; hence, the pre-installed keyboard (Google on vanilla, TouchPal on htc) isn't really 'bloatware' as it's necessary. Google makes a good keyboard; TouchPal, though, yeah, necessary bloatware in this case. Click to expand... Click to collapse Interesting, thanks for this; good to know. A shame, but good to know that's just how it is.
coyttl said: Ah, so in previous ROMs (both OEM and Viper10, it technically WAS encrypted, I just never set the password? .. Huh. Interesting, thanks for this; good to know. A shame, but good to know that's just how it is. Click to expand... Click to collapse Correct. The password is to get at the encryption key; it isn't the encryption key itself. Bitlocker/SED works the same way. Otherwise, a password change would mean re-encrypting everything. If you put in the wrong password, it'll look like you have no data.