Hello
I would like my Android device encrypted, as it contains sensitive data. I'm currently on cm-9.0.0-rc1-tinystream-hephappy-p500 (RC1-Rev.B). Now, here is what happened:
- To encrypt internal
I went to Security in System Settings and touched "Encrypt Device". It gave some confirmations and I've accepted them however, now I'm kind of stuck on this screen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My first thought was "it is encrypting". But after hours of waiting, I wanted to check if it's done already. So I clicked the power-button once (just to unlock) and it asked for my password. I've entered it and it just went into my normal launcher. I've checked if anything had changed and no, my device has not been encrypted. Any logs somewhere? Any ideas what could have caused the problem?
- To encrypt SDcard
I did some research and didn't find something perfectly for my needs. Anyone has any idea on how to encrypt an SD card to properly work together with Android?
Note: I am using LINK2SD.
Thanks for your help
Another question that actually has nothing to do with my previous post that I post here because it's not worth a new thread: every time I plug in my phone into the charger, it boots automaticly. I don't want that, my previous build of CM9 did just recharge without booting, something I prefer. Any way to configure that?
Another question I want to add to the this thread: is it possible to combine a password lock and a slide lockscreen? Like when I encrypt the phone to enter a password to decrypt it again and then just use the normal slide lockscreen to unlock it each time after the decryption?
One last question: is there any way to encrypt the SQL database in Android? As it contains sensitive data... I've read something about SQLCipher but it doesn't get to work (any help would be appreciated).
Thread can be removed. Problems already solved. Discussion about security here: http://forum.xda-developers.com/showthread.php?t=1790964
And for the charging problem: http://forum.xda-developers.com/showpost.php?p=29217540&postcount=1787
Related
Hello
I am complete new to the "custom ROM for mobile phones" business.
But i am familiar with Linux based Satellite Receivers where you
also can flash custom ROMS to enhance the functionality.
Or in other words - i know what bricked means.
Anyway what i have done so far:
I have an unlocked Bootloader on my Mi A3.
1st time (non permanent) flash of TWRP-3.3.1-2 into recovery for
a full backup of my phone to Sd-Card.
An encounter with Bootloop made
Now i want to make TWRP permament on both partitions.
But, after flashing TWRP into recovery again, i recognizing that
the "Unmodified System Partition" screen is not apearing anymore.
After my 1st twrp flash, twrp showed me a screen where something
about "Keep System Read only" was explained.
With a slider "Swipe to Allow Modifications".
This screen is not more apearing anymore.
Is this mandatory to go on ?
My goal is to have twrp, magisk and lineageos on my phone.
Last but not least i want to say:
A fantastic source of informations here but overwhelming btw. *g*
* Edit *
32 Views but no answers this could mean that my concern is not clear ?
After entering to twrp on my phone for the first time i saw this screen here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As i explained above, i only wanted to make a backup from my phone
as a fallback if something goes wrong afterwards.
Due to this i pressed ´Keep Read Only´
Don´t know if the ´Never show this...´ was flaged
My thoughts was:
Keep Read Only is okay for now/backup.
And if necessary i can Swipe for modification next time.
My concern is the screen will not showing again.
In case of i HAVE to swipe to make modifications for the next steps,
what i have to do now that this screen will show up again
that i can make the f*ckn swipe ? :angel:
Thank you
Open twrp, goto mount, there's an option for mount read-only system.
m.h.mahadi said:
Open twrp, goto mount, there's an option for mount read-only system.
Click to expand...
Click to collapse
Thank you.
Hi,
using the Hisense A5. A family member was using the phone and put in a passcode that they forgot.
I am unable to get far enough into the phone to enable USB Debugging.
I am able to get the phone into recovery mode (using power-on, volume down). which is the "Vision" recovery system.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I cannot speak or read simplified chinese. Because the Hisense A5 has an eInk screen, I was able to scan the screens and upload it to an OCR site that could convert the image into characters. Then I could use google translate.
Anyway. I chose the first option which is "Recovery".
The screen I get is the following.
Using google translate. I can make out that the first choice is "Reboot", second choice is "Delete user data" and the third choice is "Update system".
I have tried the "Delete user data", and I can seem to make it work. But after the phone reboots, the passcode is still there.
The only other possibility I have is the third option which is "Update System". If I choose that I get the following option.
As you can see, the only thing I am able to do is to get the recovery system to to somehow load the file "update.zip".
I have tried the commercial passcode remover iMyPhone, but it didn't work.
If someone had some ideas, I would really appreaciate them. I am very much stuck right now.
If you don't mind losing data then you can simply reflash your device.
Download the actual chinese Firmware from here
https://forum.xda-developers.com/showpost.php?p=82583733&postcount=28
Follow this guide to re-flash the downloaded Firmware from a microSD
https://forum.xda-developers.com/showpost.php?p=82575517&postcount=21
Hi JLowe, a very big thank you.
I was able to download the firmware. (Took a few attempts, but I got there in the end), and have it installed.
Right now, I'm trying to work out how to put the phone into debugging and put on some other ROMS. Similar to what others have done.
Well, it's a bit of a long story, so I'll try to be as short as possible.
Last year, and after hours of searching on the internet, I found the solution for "Custom binary blocked by frp lock" on this forum (here and here). Both methods promised to fix the lock without erasing my data, but I decided to try the second one (it consists of reinstalling only the boot image with Odin).
Fortunately it worked for me on the first try, and since this method was not well known on the internet, I decided to make a video tutorial to help those who had the same problem and wanted to keep their data.
The fact is that, unfortunately, this method didn't work for everyone, and in many cases it generated bootloops or black screens of death.
And my question is: does anyone know what could be the cause of this?
I tested it on SM-J710MN and SM-G532M, both running Android Marshmallow, and the bootloops/black screens occurred on devices running Android 6, 7, 8 and (I guess) 9 and 10.
Starting with Android 6 FRP on any such Android device is automatically enabled once a Google account is logged in to a device. The only way to get rid of it is by removing the account from the device into which it has been synced.
jwoegerbauer said:
Starting with Android 6 FRP on any such Android device is automatically enabled once a Google account is logged in to a device. The only way to get rid of it is by removing the account from the device into which it has been synced.
Click to expand...
Click to collapse
Thanks for answering.
Maybe I did not express myself in the correct way, but actually I was referring to the block that does not even allow to boot the device and only shows words in red, as seen in this image.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But beyond that my question is about why does the bootloop or black screen happen after flashing the boot.img file? Does it have to do with a different/incompatible version of Android/binary/csc or something like that?
I am properly pissed off now.
I suffered from a bug where my phone ran out of charge and switched off and my Pixel 6 forgot all the stored fingerprints and locked the sensor. Whenever i try to add a new fingerprint i see the below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now i really hoped the December update will solve it so i just installed it and nope, it's exactly the same.
I know a factory reset fixes it, but i sold my Pixel 5 so can't transfer backups across any more and i don't want to lose all my settings and app data again. Is cloud backup as good for that as copying across devices? The backup size is only 71MB so i expect to lose pretty much everything. Did anyone else manage to find a solution to this bug without needing to reset?
sysak said:
I am properly pissed off now.
I suffered from a bug where my phone ran out of charge and switched off and my Pixel 6 forgot all the stored fingerprints and locked the sensor. Whenever i try to add a new fingerprint i see the below:
View attachment 5482091
Now i really hoped the December update will solve it so i just installed it and nope, it's exactly the same.
I know a factory reset fixes it, but i sold my Pixel 5 so can't transfer backups across any more and i don't want to lose all my settings and app data again. Is cloud backup as good for that as copying across devices? The backup size is only 71MB so i expect to lose pretty much everything. Did anyone else manage to find a solution to this bug without needing to reset?
Click to expand...
Click to collapse
Only root backups can save your app data (logins), Google's non root / other non root backups are still ****.
Ok, so i got this random Huawei P20Lite right?
Back isnt pealed off, works fine, no damages.
BUT WAIT... About Works Fine... It Wont really boot up into The OS!!!
Somethimes shows this really weired Image when pluged in and charging the phone, or randomly:
A green Screen with a Red Square on Top and a Blue one Down.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Not My Picture
It will then boot up and greed you with A:
Again, not my Picture.
Acording to Huawei, You have to Use HiSuite to recover it.
1. Put the Phone into Fast Boot. AND conect to PC
2. Open HiSuite on Your PC and click on Recovery mode or whatever its called.
3. i donk know i forgot.
anyways, i get this nice little message
(In translated, this means That: Your Device doesnt support System Recovery.
Bro wth
Anyways, our phone story doesnt end there...
I tried doing it without the Computer.
using eRecovery!!! not surprising i know...
Still, it was stuck on booting animation trying to enter eRecovery.
According to Huawei, "this message is displayed when a system file is replaced or modified, or the system is manually updated to an unofficial version". They were responding to another user with the same issue as mine.
I think that this is the Issue. Still, the instructions to fix it, dont work. (as tested above.)
Tutorials show the eRecovery method without the PC.
Here are some info i found:
Another Guy having the same issue:
i forgot the link but someone else on XDA Had the same issue.
please help!!!
hello sir did you have any luck resolving this issue (I've purity much looked every were but I had no chance)