Related
Has anyone managed to encrypt this device? When I try it just sits at the Droid screen and nothing happens.
The following message is displayed in the log:
I/Timeline( 580): Timeline: Activity_windows_visible id: ActivityRecord{42559a68 u0 com.android.settings/.CryptKeeperConfirm$Blank t16} time:6294032
E/Cryptfs ( 168): Orig filesystem overlaps crypto footer region. Cannot encrypt in place.
This is with CM11 latest nightly. It seems this problem is not unique to this device.
Is there a recent Android ROM where this works?
pilux_han said:
Has anyone managed to encrypt this device? When I try it just sits at the Droid screen and nothing happens.
The following message is displayed in the log:
I/Timeline( 580): Timeline: Activity_windows_visible id: ActivityRecord{42559a68 u0 com.android.settings/.CryptKeeperConfirm$Blank t16} time:6294032
E/Cryptfs ( 168): Orig filesystem overlaps crypto footer region. Cannot encrypt in place.
This is with CM11 latest nightly. It seems this problem is not unique to this device.
Is there a recent Android ROM where this works?
Click to expand...
Click to collapse
It got fixed today so wait for 21-9-2014 nightly and then it should work.
SuperLamic said:
It got fixed today so wait for 21-9-2014 nightly and then it should work.
Click to expand...
Click to collapse
Ah, great!
Do you know whether a simple update to the nightly will be enough or will the file systems have to be recreated (since some of the articles on this topic mention that the file system needs to leave some space on the partition unused)?
Note that once you encrypt the phone you wont be able to access internal sdcard in recovery -> cant use cm updater and you have to copy and flash manually new roms from external sd
Do we actualy gain something from this encryphting thing or it is just for "paranoid " people ?
dimi89 said:
Do we actualy gain something from this encryphting thing or it is just for "paranoid " people ?
Click to expand...
Click to collapse
For me it is a work requirement. I've lost access to work mail and calendar while my phone is not encrypted.
I know the updates will be more difficult and cumbersome after the phone is encrypted. I've already switched from CWM to TWRP for this reason (even though that switch is only half working).
I apologize but I don't know much althoug i am quite interested,
what does this mean? how is the phone encripted?
Does it need a pw in adb?
From demetris' post
I already flash everything from ecternal sd
I don't need internal within recovery
I don't use cm updater (i'm on lsmooth)
Other downsides?'
Rudjgaard said:
I apologize but I don't know much althoug i am quite interested,
what does this mean? how is the phone encripted?
Does it need a pw in adb?
From demetris' post
I already flash everything from ecternal sd
I don't need internal within recovery
I don't use cm updater (i'm on lsmooth)
Other downsides?'
Click to expand...
Click to collapse
It does indeed work with yesterday's nightly. I looked at the changelog and didn't see anything that matched, but it does work. Thanks!
Supposedly there is a small performance impact, but I haven't noticed it at this point. It uses your default unlock PIN to encrypt the data on the phone. After it is encrypted you can apparently change this to a different PIN or password. You only need to enter this PIN when the phone is rebooted.
My newly encrypted phone appears to work as normal. Next challenge will be the next CM11 upgrade.
pilux_han said:
It does indeed work with yesterday's nightly. I looked at the changelog and didn't see anything that matched, but it does work. Thanks!
Supposedly there is a small performance impact, but I haven't noticed it at this point. It uses your default unlock PIN to encrypt the data on the phone. After it is encrypted you can apparently change this to a different PIN or password. You only need to enter this PIN when the phone is rebooted.
My newly encrypted phone appears to work as normal. Next challenge will be the next CM11 upgrade.
Click to expand...
Click to collapse
If you want to see REAL changes, you have to take a look at Cyanogenmod repos:
kernel
https://github.com/CyanogenMod/lge-kernel-p880/commits/cm-11.0
AND device repo
https://github.com/CyanogenMod/android_device_lge_p880/commits/cm-11.0
also there is a chance to nightly will not include fixes from same day because build started before developer commited the change, so you can look at jenkins: http://jenkins.cyanogenmod.org/view/All/builds (there you can see builds and it's build times)
BlankBlackDroid said:
So that means if i encrypt now my LG 4X HD (i have 2014-09-26 nightly installed) the internal CM updater and the update from the internal sd didn't work anymore and only from the external sd will work?
Click to expand...
Click to collapse
that means you will be able to write/read from android but not in recovery. So if you want to flash anything you have to move it to external sd which is not encrypted..
BlankBlackDroid said:
Okay use the external sd card is not the problem. But how flash then if not from recovery mode?
Thanks for you fast response!
Click to expand...
Click to collapse
I haven't said you can't use recovery (if yes i'm so sorry, my english skills are just terrible) I wanted to say you can't use internal sdcard from recovery.
It's slightly off-topic, but now that it should be possible to encrypt my device, does someone know a way to let the device reboot after some failed attempts to unlock the screen?
ddorian said:
It's slightly off-topic, but now that it should be possible to encrypt my device, does someone know a way to let the device reboot after some failed attempts to unlock the screen?
Click to expand...
Click to collapse
I believe this is governed by the installed device administrator. If you sync to workplace Exchange server, then you probably already have it. However, the device won't just reboot, it will be a remote wipe.
What's the size of system, data and cache partitions for the Xiaomi Mi8?
Could you please show the sizes of its partitions, please?
I haven't bought the mobile yet.
I've had problems with older mobiles because these partitions are too small and many apps complain, specially Google services.
There are some complex tutorials to modify partition sizes with adb commands but are specific to each phone.
What's the best/easiest way to achieve it with the Xiaomi Mi8?
skanskan said:
What's the size of system, data and cache partitions for the Xiaomi Mi8?
Could you please show the sizes of its partitions, please?
I haven't bought the mobile yet.
I've had problems with older mobiles because these partitions are too small and many apps complain, specially Google services.
There are some complex tutorials to modify partition sizes with adb commands but are specific to each phone.
What's the best/easiest way to achieve it with the Xiaomi Mi8?
Click to expand...
Click to collapse
What you're talking about is issues with old budget phones.
Even the modern budget phones have partitions big enough to fit files in without issues.
And the Mi 8 is a flagship so you have nothing to worry about when it comes to partition sizes.
The Marionette said:
What you're talking about is issues with old budget phones.
Even the modern budget phones have partitions big enough to fit files in without issues.
And the Mi 8 is a flagship so you have nothing to worry about when it comes to partition sizes.
Click to expand...
Click to collapse
Anyway, could you please tell me the size of its partitions, please?
Just to know the information.
Thanks
The Marionette said:
What you're talking about is issues with old budget phones.
Even the modern budget phones have partitions big enough to fit files in without issues.
And the Mi 8 is a flagship so you have nothing to worry about when it comes to partition sizes.
Click to expand...
Click to collapse
In another forum somebody has just told me his mobile has this partitions (diskinfo):
Data 52.5 G 3.9 used 48.4GB free
System 2.9G 2.1G used 872MB free
Ram 5.5. GB 2.9GB used 1.6GB free
As you can see the System partition is quite small and almost full, even if the phone is a new model the problem is still there.
We need a method to easily enlarge that system partition, and maybe other not shown there.
skanskan said:
In another forum somebody has just told me his mobile has this partitions (diskinfo):
Data 52.5 G 3.9 used 48.4GB free
System 2.9G 2.1G used 872MB free
Ram 5.5. GB 2.9GB used 1.6GB free
As you can see the System partition is quite small and almost full, even if the phone is a new model the problem is still there.
We need a method to easily enlarge that system partition, and maybe other not shown there.
Click to expand...
Click to collapse
You're the only one who thinks that. Try repartitioning yourself but don't complain when you brick your phone.
skanskan said:
We need a method to easily enlarge that system partition, and maybe other not shown there.
Click to expand...
Click to collapse
I've done this job, in the past, with my Oppo Find 7 (see here - https://forum.xda-developers.com/fi...st-custom-storage-partitions-v1-oppo-t2930576).
I discourage all of you to repeat a job like this - unless you have a tool (usually a MS Windows tool) that recreates all the storage's internal partitions (jn the same way as done in factory) and only if you have a very high-level know-how to face and solve all possible issues and matters - be even ready to say good-bye to your phone !!!
italianquadcore said:
I've done this job, in the past, with my Oppo Find 7 (see here - https://forum.xda-developers.com/fi...st-custom-storage-partitions-v1-oppo-t2930576).
I discourage all of you to repeat a job like this - unless you have a tool (usually a MS Windows tool) that recreates all the storage's internal partitions (jn the same way as done in factory) and only if you have a very high-level know-how to face and solve all possible issues and matters - be even ready to say good-bye to your phone !!!
Click to expand...
Click to collapse
This is the kind of tutorial I've already seen before.
The problem is almost always the same, the rely on a script designed specifically for a phone model.
I could try to translate that script to my phone using generic adb and linux commands but it will be dangerous.
I've also heard that some versions of TWRP can resize the partitions easily. It would be great to get it on the Mi8.
What is the worst thing that can happen if all goes wrong?
Wouldn't I solve it by just wiping everything from a fastboot and resintalling a ROM?
Regards.
skanskan said:
This is the kind of tutorial I've already seen before.
The problem is almost always the same, the rely on a script designed specifically for a phone model.
I could try to translate that script to my phone using generic adb and linux commands but it will be dangerous.
I've also heard that some versions of TWRP can resize the partitions easily. It would be great to get it on the Mi8.
What is the worst thing that can happen if all goes wrong?
Wouldn't I solve it by just wiping everything from a fastboot and resintalling a ROM?
Regards.
Click to expand...
Click to collapse
There is no reason to touch the partitions of modern smartphones, all the most important partitions are big enough to contain all binary codes for the operating system and personal data we need.
Whenever we unlock the bootloader, we have full access of the emmc, so we can even delete/resize/create partitions. The first con is that we could not start the phone anymore, due to the fact that android, recovery and fastboot, reside in three different partitions. If we delete these partitions, there is no way to access the smartphone. In this case an external application for Windows or Linux (created by the manufacturer) must be used to rewrite all the emmc again, recreating the partitions and rewriting them, in the same way as done in factory. This application is the most important piece of software we must have if we want to mod our smartphone.
Hello @milouk @khusika @oipr @Twisted Prime,
I have an encrypted USB SSD disk with veracrypt, which supports Windows and Linux. Unfortunately, the android does not have this disc without the possibility of decrypting on the cell completely loses meaning. I found a link where it can be implemented but I can not do it. Would you be able to do it?
https://forum.xda-developers.com/android/software/utils-data-recovery-tools-testdisk-t3709380
SpiderSGS6 said:
Hello @milouk @khusika @oipr @Twisted Prime,
I have an encrypted USB SSD disk with veracrypt, which supports Windows and Linux. Unfortunately, the android does not have this disc without the possibility of decrypting on the cell completely loses meaning. I found a link where it can be implemented but I can not do it. Would you be able to do it?
https://forum.xda-developers.com/android/software/utils-data-recovery-tools-testdisk-t3709380
Click to expand...
Click to collapse
Do you not have a windows computer or one you could borrow to decrypt it??
oipr said:
Do you not have a windows computer or one you could borrow to decrypt it??
Click to expand...
Click to collapse
I have, but the problem is that most of the time I'm out and my computer is stationary. It would be great if there was the possibility of encrypting and decrypting the disk on the cell.
I decided to start dabbling in AOSP and got a nice setup with Ubuntu.
However it will be impossible for me to actually flash the ROM to my phone without the vendor drivers.
Anyone know where I can find these (and do I just plop them into the source folder or should I run a script)?
1creeperbomb said:
I decided to start dabbling in AOSP and got a nice setup with Ubuntu.
However it will be impossible for me to actually flash the ROM to my phone without the vendor drivers.
Anyone know where I can find these (and do I just plop them into the source folder or should I run a script)?
Click to expand...
Click to collapse
I have treble twrp recovery.
hello everyone, i have a problem with the wifi and bluetooth. My wifi mac address was shown as 02:00:00:00:00:00. wifi and bluetooth are not turning on. then i saw the files on the persist partition. some file was corrupted. so i wiped the persist partition (mke2fs command) and flashed 9.0.5 fw+modem and 9.0.5 full rom and now the corrupted files gone ( there is no file like wlan_mac.bin). mac address is shown as unknown.
can you help me for my problem? thank you and have nice day.
hajking said:
hello everyone, i have a problem with the wifi and bluetooth. My wifi mac address was shown as 02:00:00:00:00:00. wifi and bluetooth are not turning on. then i saw the files on the persist partition. some file was corrupted.
Click to expand...
Click to collapse
Which file was corrupted? What do you mean by corrupted? How did you tell?
hajking said:
so i wiped the persist partition (mke2fs command) and flashed 9.0.5 fw+modem and 9.0.5 full rom and now the corrupted files gone ( there is no file like wlan_mac.bin). mac address is shown as unknown.
can you help me for my problem? thank you and have nice day.
Click to expand...
Click to collapse
You need wlan_mac.bin in order to use wifi and bluetooth/.bt_nv.bin in order to run bt. If you don't have a backup of the persist partition, I'd give a try to the unbrick tool, though I'm not really sure if persist is restored...
nvertigo67 said:
Which file was corrupted? What do you mean by corrupted? How did you tell?
You need wlan_mac.bin in order to use wifi and bluetooth/.bt_nv.bin in order to run bt. If you don't have a backup of the persist partition, I'd give a try to the unbrick tool, though I'm not really sure if persist is restored...
Click to expand...
Click to collapse
i looked at the vendor and persist partitions and i saw that half of the data was writen in some files ( if normaly must be writen "bla bla bla", i saw "bla b"). i flash nougat via unbrick tool but no luck. may you send vendor and persist partitions backup? if you do, ill be happiest person.
hajking said:
i looked at the vendor and persist partitions and i saw that half of the data was writen in some files ( if normaly must be writen "bla bla bla", i saw "bla b"). i flash nougat via unbrick tool but no luck. may you send vendor and persist partitions backup? if you do, ill be happiest person.
Click to expand...
Click to collapse
Sent you a pm.
If you have an image file of the persist partition, eg /sdcard/sda2.img then you can write it using this command:
Code:
dd if=/sdcard/sda2.img of=/dev/block/sda2
Sent from my OnePlus 3T using XDA Labs
hajking said:
i looked at the vendor and persist partitions and i saw that half of the data was writen in some files ( if normaly must be writen "bla bla bla", i saw "bla b"). i flash nougat via unbrick tool but no luck. may you send vendor and persist partitions backup? if you do, ill be happiest person.
Click to expand...
Click to collapse
If the unbrick tool doesn't restore the persist partition, it's most probably because it's individualy (like efs) and not interchangeble between devices (makes sense for hw addresses!).
BTW: op3/t does not ship with vendor partion. /vendor is a symlink to /system/vendor. If you say files on the vendor partition were corrupted, the system partition is corrupted. Since system is mounted rw, there's a probability the hw is broken.
Perhaps, the best choice is to get your device RMAed to omeplus.
@BillGoss: this
Code:
[email protected] /usr/local/src/oxygenos $ adb shell su -c "cat /mnt/vendor/persist/wlan_mac.bin"
Intf0MacAddress=C0EEFBEF26C0
Intf1MacAddress=C2EEFBEF26C0
Intf3MacAddress=000AF58989FD
Intf4MacAddress=000AF58989FC
END
[email protected] /usr/local/src/oxygenos $
is my device's wlan_mac.bin. Is it different from yours? If not, I maybe wrong, and it is possible to interchange persist partitions.
nvertigo67 said:
@BillGoss: this
is my device's wlan_mac.bin. Is it different from yours? If not, I maybe wrong, and it is possible to interchange persist partitions.
Click to expand...
Click to collapse
Oops!
I didn't know you could do that. The cat command shows my phone's MAC address. I did a search of the persist partition for the address but searched for the hex value instead of the string, so I didn't see it.
My bad!
Sorry, @hajking, so don't use the file I shared with you.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
Oops!
I didn't know you could do that. The cat command shows my phone's MAC address. I did a search of the persist partition for the address but searched for the hex value instead of the string, so I didn't see it.
My bad!
Sorry, @hajking, so don't use the file I shared with you.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
I was surprised, too. I havn't expected this from a file ending on .bin:
Code:
adb shell su -c "file /mnt/vendor/persist/wlan_mac.bin"
/mnt/vendor/persist/wlan_mac.bin: ASCII text
Anyway, comparing the content of wlan_mac.bin seemed the easiest way to me to check weather persist is unique (like efs), or not.
Lesson learned: always keep a bakup of efs and persist partion - efs alone isn't sufficient...
I had problems with sensors (accidently deleted sensors dir from persist partition), its different issue then yours but it has one in common, the persist partition - it contains sensors calibration, wifi and bt hw address.
So i used latest unbrick tool (9.0.5), but it didnt solve my issues, then i used the oldest unbrick tool i could find (Marshmallow) and sensors started to work but could not enable wifi, so i made local upgrade to 9.0.5, after that all my issues got resolved - sensors and wifi works again.
Try what i did, maybe it will sovlve your issue too.
nvertigo67 said:
If the unbrick tool doesn't restore the persist partition, it's most probably because it's individualy (like efs) and not interchangeble between devices (makes sense for hw addresses!).
BTW: op3/t does not ship with vendor partion. /vendor is a symlink to /system/vendor. If you say files on the vendor partition were corrupted, the system partition is corrupted. Since system is mounted rw, there's a probability the hw is broken.
Perhaps, the best choice is to get your device RMAed to omeplus.
@BillGoss: this
Code:
[email protected] /usr/local/src/oxygenos $ adb shell su -c "cat /mnt/vendor/persist/wlan_mac.bin"
Intf0MacAddress=C0EEFBEF26C0
Intf1MacAddress=C2EEFBEF26C0
Intf3MacAddress=000AF58989FD
Intf4MacAddress=000AF58989FC
END
[email protected] /usr/local/src/oxygenos $
is my device's wlan_mac.bin. Is it different from yours? If not, I maybe wrong, and it is possible to interchange persist partitions.
Click to expand...
Click to collapse
dude im sorry but there is no wlan_mac.bin now. i wiped the partition using mke2fs and it gone. thats why i need a backup of persist. i you send me via pm ill change the address after restore.
ppajdek said:
I had problems with sensors (accidently deleted sensors dir from persist partition), its different issue then yours but it has one in common, the persist partition - it contains sensors calibration, wifi and bt hw address.
So i used latest unbrick tool (9.0.5), but it didnt solve my issues, then i used the oldest unbrick tool i could find (Marshmallow) and sensors started to work but could not enable wifi, so i made local upgrade to 9.0.5, after that all my issues got resolved - sensors and wifi works again.
Try what i did, maybe it will sovlve your issue too.
Click to expand...
Click to collapse
thanx dude ill try tonight. ?
hajking said:
dude im sorry but there is no wlan_mac.bin now. i wiped the partition using mke2fs and it gone. thats why i need a backup of persist. i you send me via pm ill change the address after restore.
Click to expand...
Click to collapse
No.
We've just proofed by the wifi mac addresses, that the persist partitions are unique for each device. We havn't proofed, that the wlan mac address is the only difference. In deed I'm pretty sure, that bluetooth/.bt_nv.bin is different, too.
Code:
[email protected] /usr/local/src/oxygenos $ adb shell su -c "file /mnt/vendor/persist/bluetooth/.bt_nv.bin"
/mnt/vendor/persist/bluetooth/.bt_nv.bin: data
[email protected] /usr/local/src/oxygenos $ adb shell su -c "strings /mnt/vendor/persist/bluetooth/.bt_nv.bin"
[email protected] /usr/local/src/oxygenos $
As you can see, bluetooth/.bt_nv.bin is really a binary file, and you can't change the address like in wlan_mac.bin.
If https://forum.xda-developers.com/showpost.php?p=80704325&postcount=8 isn't working for you, either, your last resort is rmaing the device.
nvertigo67 said:
No.
We've just proofed by the wifi mac addresses, that the persist partitions are unique for each device. We havn't proofed, that the wlan mac address is the only difference. In deed I'm pretty sure, that bluetooth/.bt_nv.bin is different, too.
Code:
[email protected] /usr/local/src/oxygenos $ adb shell su -c "file /mnt/vendor/persist/bluetooth/.bt_nv.bin"
/mnt/vendor/persist/bluetooth/.bt_nv.bin: data
[email protected] /usr/local/src/oxygenos $ adb shell su -c "strings /mnt/vendor/persist/bluetooth/.bt_nv.bin"
[email protected] /usr/local/src/oxygenos $
As you can see, bluetooth/.bt_nv.bin is really a binary file, and you can't change the address like in wlan_mac.bin.
If https://forum.xda-developers.com/showpost.php?p=80704325&postcount=8 isn't working for you, either, your last resort is rmaing the device.
Click to expand...
Click to collapse
so it seems unbrick tool is the only way. thanx guys.
hajking said:
so it seems unbrick tool is the only way. thanx guys.
Click to expand...
Click to collapse
No. If that fails you can rma the device. As already stated, I strongly recommend to rma the device, because broken hw is the most probable reason for the coruppted files.
hajking said:
...
@BillGoss: this
dude im sorry but there is no wlan_mac.bin now. i wiped the partition using mke2fs and it gone. thats why i need a backup of persist. i you send me via pm ill change the address after restore.
Click to expand...
Click to collapse
Sent you another pm
Sent from my OnePlus 3T using XDA Labs
nvertigo67 said:
No. If that fails you can rma the device. As already stated, I strongly recommend to rma the device, because broken hw is the most probable reason for the coruppted files.
Click to expand...
Click to collapse
i beg your indulgence. what is rma?
oh i understand but i cannot rma the device because ive bought a used op3t and the seller is not answering to my calls. so i have to fix that issue.
hajking said:
i beg your indulgence. what is rma?
oh i understand but i cannot rma the device because ive bought a used op3t and the seller is not answering to my calls. so i have to fix that issue.
Click to expand...
Click to collapse
Crossing my fingers you can fix it. Crossing my fingers you havn't been sold a broken, stolen or otherwise compromised device!!!
A friend of mine has bought (without his knowledge) a stolen and broken device on ebay. When rmaing it, some days later the prosecuting attorney wants to talk... If buying used devices, always get the original shipping, warranty and invoice documents! As always: easy to claim - afterwards!
Good luck!