Related
Hi,
Samsung Galaxy J5 (2016) - SM-J510FN/DS
I have flashed the TWRP recovery (3.0.2) and then installed SU Root.
As I wanted to turn on "System UI Tuner" but it did not work, I turned off the "developer options" in the settings.
After restart my mobile is now in "Custom binary blocked by frp" [secure fail:kernel].
How can I solve that?
Winf2005 said:
Hi,
Samsung Galaxy J5 (2016) - SM-J510FN/DS
I have flashed the TWRP recovery (3.0.2) and then installed SU Root.
As I wanted to turn on "System UI Tuner" but it did not work, I turned off the "developer options" in the settings.
After restart my mobile is now in "Custom binary blocked by frp" [secure fail:kernel].
How can I solve that?
Click to expand...
Click to collapse
Please reflash the stock firmware. Alternatively I have read that flashing only the boot.img file ahould do the trick without erasing data but I can't really confirm this.
FRP lock is caused by the bootloader detecting that a change was made. To disable security detection you need to keep enabled OEM Unlock in Dev Settings. It gets deactivated always when you turn off dev options.
BTW Samsung removed the System UI tuner from Marshmallow so your best bet for that is an XPOSED module or a custom ROM based on android AOSP, roms that don't have that disabled. Samsung is stupid
Thank you!
The stock firmware was ~1.4GB. After flashing root has gone, but almost all configuration was still there. Either it was not overwritten or the backup of Samsung did the job...
Winf2005 said:
Thank you!
The stock firmware was ~1.4GB. After flashing root has gone, but almost all configuration was still there. Either it was not overwritten or the backup of Samsung did the job...
Click to expand...
Click to collapse
Oh well it did factory reset, right? Also the backup feature is mostly Gogle's that's how I manage to keep most of my information even tho I'm trying new ROMs every month.
The cool thing was, that the installed APPs have all been there. So yes, google maybe did a big part, but I think this was no complete factory reset. I did it completely after the official advice of Samsung's homepage.
When activating the oem unlock you can install Twrp, kernel or custom rom without the activation of FRP security that is activated when you establish a security pattern in the device
When the binary is blocked by the FRP you must install the factory firmware, then enter the recovery and do a factory reset since the FRP prevents external access to the system and data as prevention
You will be prompted for the email and password of the previously used account
Thanks a lot
Amarius1 said:
Please reflash the stock firmware. Alternatively I have read that flashing only the boot.img file ahould do the trick without erasing data but I can't really confirm this.
FRP lock is caused by the bootloader detecting that a change was made. To disable security detection you need to keep enabled OEM Unlock in Dev Settings. It gets deactivated always when you turn off dev options.
BTW Samsung removed the System UI tuner from Marshmallow so your best bet for that is an XPOSED module or a custom ROM based on android AOSP, roms that don't have that disabled. Samsung is stupid
Click to expand...
Click to collapse
I have saved my data on Galaxy J5 2016. You advice to reflash only original "boot.img" is excelent cure.
Hi guys, this is my first post here
I have a Moto G4 that I rooted recently and flashed with good ROMs for testing, but in all ROMs, Encryption doesn't work.
In all times that I tried, I go on Settings > Encrypt and start, but always remaining 00:00 for a lot or hours and when I restart phone, I enter with password and display this error.
Decryption unsuccessful. The password you entered is correct but unfortunately your data is corrupt
Click to expand...
Click to collapse
Then I have a question, encryption doesn't work on rooted Moto G4? If yes, have other option to protect my data on rooted device?
Thanks.
joubertredrat said:
Hi guys, this is my first post here
I have a Moto G4 that I rooted recently and flashed with good ROMs for testing, but in all ROMs, Encryption doesn't work.
In all times that I tried, I go on Settings > Encrypt and start, but always remaining 00:00 for a lot or hours and when I restart phone, I enter with password and display this error.
Then I have a question, encryption doesn't work on rooted Moto G4? If yes, have other option to protect my data on rooted device?
Thanks.
Click to expand...
Click to collapse
In my knowledge, encryption will not work on rooted phones. But there is a workaround for this. You can root your phone after the phone is fully encrypted. To root your phone after it is encrypted, you can click adb sideload on TWRP and through the terminal on your pc, you can sideload phh's superuser. Reboot your phone and you have a working, encrypted phone with root installed. I didn't try this, but I think, it will work.
@stkpxl thanks for the help, but I have a question.
Will be possible to make encryption with SD card as extended internal storage? Thanks
@stkpxl I'm trying to flash LineageOS after flash Magisk but response error 7. What wrong about this? Thanks.
stkpxl said:
You flash Lineage before flashing Magisk.
Click to expand...
Click to collapse
I really trying, but isn't working, look my steps.
- Flash Stock ROM like this post http://www.stechguide.com/download-stock-firmware-of-moto-g4-and-g4-plus/
- Run stock, setup first run, format sd and define as internal storage
- Flash recovery twrp-3.0.3-n4-athene_shreps.img
- Run twrp
- Install ElementalX-G4-1.04-LOS.zip
- Run stock, set password and encryption device
- Smartphone restart and stock encrypt device
- Run stock again, password working fine
- Run twrp, twrp ask for encrytion password, I put and enter on twrp normally
- Install lineage-14.1-20170313-nightly-athene-signed.zip without wipe
* Fail on this point
Code:
Installing zip file '/path/to/lineage-14.1-20170313-nightly-athene-signed.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Target: <a big number>
detected filesystem ext4 for /dev/block/bootdevice/by-name/system
Can't install this package on top of incompatible data. Please try another package or run a factory reset
Updata process ended with ERROR: 7
Error installing zip file /path/to/lineage-14.1-20170313-nightly-athene-signed.zip
Updating partition details...
...done
This problem display only If I encrypt device on stock ROM, when I flash without encrytion, twrp flash LineageOS normally.
Seems like full disc encryption is not working in general. Its reported https://jira.lineageos.org/browse/BUGBASH-253
I am also quite sure that this bug was already in cyanogenmod and also reported there.
tonymarschall- said:
Seems like full disc encryption is not working in general. Its reported https://jira.lineageos.org/browse/BUGBASH-253
I am also quite sure that this bug was already in cyanogenmod and also reported there.
Click to expand...
Click to collapse
Thanks for reply @tonymarschall
Are you know any custom ROM that encryption is working for me test here? Thanks
joubertredrat said:
Are you know any custom ROM that encryption is working for me test here? Thanks
Click to expand...
Click to collapse
No, I am sorry and searching by myself. I hope that one day it will be official supported. Maybe you can give the issue an upvote.
Hi guys.
A bug related about encryption fail was solved and encryption is working fine on lineage-14.1-20170501-nightly-athene-signed.zip
https://jira.lineageos.org/browse/BUGBASH-253
Disclaimer: I have done these steps multiple times and haven't come across any issues
Read All Step carefully. Any issues or damage to your phone that occurs while doing this I am not responsible.
If TWRP asks you for Password to decrypt data & maybe you have important data in you device, So you can't format data.
Follow these steps:
1. Download the OxygenOS full zip file (tested on 4.0.1 & above)
2. Open TWRP.
3. When It asks for password, cancel it.
4. Click "Read Only" button.
5. Install the OxygenOS zip file.
6. Reboot.
7. The OS may misbehave.
8. Open TWRP again. & Boom! No encryption password.
9. Connect to PC and copy the Important data.
10. Flash Any ROM now.
Thanks!
Recently I had to type in the password but I didn't know that it is possible to bypass it with this...
svandasek said:
Thanks!
Recently I had to type in the password but I didn't know that it is possible to bypass it with this...
Click to expand...
Click to collapse
Glad it helped you
ah.... if i only knew :crying:
That's good from a data recovery point of view... but it just sucks from a security point of view.
Not sure if I should be happy or concerned
TWRP Encryption ByPass
maddler said:
That's good from a data recovery point of view... but it just sucks from a security point of view.
Not sure if I should be happy or concerned
Click to expand...
Click to collapse
Agree .... that seems like a gaping security vulnerability. :-/
maddler said:
That's good from a data recovery point of view... but it just sucks from a security point of view.
Not sure if I should be happy or concerned
Click to expand...
Click to collapse
There's no need to be concerned (about this, specifically).
tk8lm6 said:
Agree .... that seems like a gaping security vulnerability. :-/
Click to expand...
Click to collapse
Actually, this is a case where this device is more secure than previous devices. The encryption key for your user data is divided into two parts. First is the part you type in when booting. The other half is stored in the "secure element" (TrustZone) inside the processor, and is unique to your phone. How the OP3 improves this is that it actually stores two versions of the device-specific key. One is used when the system is trusted (the kernel is signed and dm-verity passes), and the other is used when it is untrusted. This is part of what wipes your data when you unlock the bootloader. The security benefit comes from the SoC locking down the encryption keys when verification fails. Going back to the stock ROM causes all of the verification to pass, and the keys stored in the TrustZone are allowed to unlock your data partition.
On the other hand, if this allows you to bypass manually-enabled encryption, that would be a major security problem.
What interests me is that installing OOS should replace TWRP with the stock recovery image, but this appears not to have happened. Or did you have to flash TWRP again from fastboot after booting into OOS?
smaeul said:
There's no need to be concerned (about this, specifically).
Actually, this is a case where this device is more secure than previous devices. The encryption key for your user data is divided into two parts. First is the part you type in when booting. The other half is stored in the "secure element" (TrustZone) inside the processor, and is unique to your phone. How the OP3 improves this is that it actually stores two versions of the device-specific key. One is used when the system is trusted (the kernel is signed and dm-verity passes), and the other is used when it is untrusted. This is part of what wipes your data when you unlock the bootloader. The security benefit comes from the SoC locking down the encryption keys when verification fails. Going back to the stock ROM causes all of the verification to pass, and the keys stored in the TrustZone are allowed to unlock your data partition.
On the other hand, if this allows you to bypass manually-enabled encryption, that would be a major security problem.
What interests me is that installing OOS should replace TWRP with the stock recovery image, but this appears not to have happened. Or did you have to flash TWRP again from fastboot after booting into OOS?
Click to expand...
Click to collapse
No arguing that previous versions were less secure. But, still, as long as there's a way to bypass encryption that's a security failure.
Encrypted data shouldn't be made available unless proper key(s) or passwords have been provided.
If that's the way that's meant to work, then that's flawed by design.
smaeul said:
There's no need to be concerned (about this, specifically).
Actually, this is a case where this device is more secure than previous devices. The encryption key for your user data is divided into two parts. First is the part you type in when booting. The other half is stored in the "secure element" (TrustZone) inside the processor, and is unique to your phone. How the OP3 improves this is that it actually stores two versions of the device-specific key. One is used when the system is trusted (the kernel is signed and dm-verity passes), and the other is used when it is untrusted. This is part of what wipes your data when you unlock the bootloader. The security benefit comes from the SoC locking down the encryption keys when verification fails. Going back to the stock ROM causes all of the verification to pass, and the keys stored in the TrustZone are allowed to unlock your data partition.
On the other hand, if this allows you to bypass manually-enabled encryption, that would be a major security problem.
What interests me is that installing OOS should replace TWRP with the stock recovery image, but this appears not to have happened. Or did you have to flash TWRP again from fastboot after booting into OOS?
Click to expand...
Click to collapse
I've tried many times. OOS replaces TWRP only on CLEAN Instal for me.
hey guys, i tried to flash oos 5.0 zip, before that i was on another rom. wiped data, system, cache and flashed oos 5.0. and now internal storage is encrypted. how do i flash the zip in twrp now?
manchitro said:
hey guys, i tried to flash oos 5.0 zip, before that i was on another rom. wiped data, system, cache and flashed oos 5.0. and now internal storage is encrypted. how do i flash the zip in twrp now?
Click to expand...
Click to collapse
Just flash it.
Wait, are you saying by just installing a zip, the encrypion hardware pass is gone? WTF.. Is such "hack" available on other devices? Xiaomi redmi(s) for example?
hey i am not able to see any of my files or the zip itself within? is there anything to resolve that?
i can boot into os but for whatever reason cant get to twrp. i have the backup .imgs on my pc now too can i sideload a restore?
im stuck not able to get twrp to see any of my storage and i cant get into twrp twice in a row, so if i fastboot and flash twrp thru adb and then boot into twrp, it asks me for the password, if i hit cancel it just shows 0 storage. ive tried to go to adb sideload but it just sits there. I have the backup i made thru twrp before trying to update.
SourPower said:
hey i am not able to see any of my files or the zip itself within? is there anything to resolve that?
i can boot into os but for whatever reason cant get to twrp. i have the backup .imgs on my pc now too can i sideload a restore?
im stuck not able to get twrp to see any of my storage and i cant get into twrp twice in a row, so if i fastboot and flash twrp thru adb and then boot into twrp, it asks me for the password, if i hit cancel it just shows 0 storage. ive tried to go to adb sideload but it just sits there. I have the backup i made thru twrp before trying to update.
Click to expand...
Click to collapse
Yeah same issue here, as soon as I go in twrp and can't type the password, I can't access my files which is expected behavior, so I don't understand how you can access the file to flash from twrp.
Can someone detail please?
---------- Post added at 07:06 PM ---------- Previous post was at 06:40 PM ----------
Actually I just found a way out to get to previous twrp version, and all is back to normal
From your running ROM, you can download the application twrp (root needed oc)
Then you can use it to flash recovery.
I always keep former version file so I could revert to bluspark twrp that was working before. All worked as expected!
Still not solving the encryption password issue when flashing new recent twrp..
Android 10 Encryption / Security Issue - ADB Encryption Bypass?
rahulrs0029 said:
Disclaimer: I have done these steps multiple times and haven't come across any issues
Read All Step carefully. Any issues or damage to your phone that occurs while doing this I am not responsible.
If TWRP asks you for Password to decrypt data & maybe you have important data in you device, So you can't format data.
Follow these steps:
1. Download the OxygenOS full zip file (tested on 4.0.1 & above)
2. Open TWRP.
3. When It asks for password, cancel it.
4. Click "Read Only" button.
5. Install the OxygenOS zip file.
6. Reboot.
7. The OS may misbehave.
8. Open TWRP again. & Boom! No encryption password.
9. Connect to PC and copy the Important data.
10. Flash Any ROM now.
Click to expand...
Click to collapse
Does this only affect the TWRP -encryption, because when you set your lockscreen password (for the auto-encrypted userdata partition in Android 10, for example) the data can't be decrypted without this password..?
I have discovered another security issue however on a rooted device:
On my Magisk-rooted and encrypted Note 10+/Exynos (Android 10) I just found out, that the userdata (data/data ) partition is UNENCRYPTED and fully readable when viewed with an ADB viewer from my PC although the device is in lockscreen mode / locked!
This doesn't happen after reboot before the first unlock! After the device has been unlocked, accessed via ADB and re-locked (but not rebooted) it is (still) unencrypted, even after rebooting the PC!
Here the lockscreen password would not make much sense at every screenlock - it just unlocks the screen which can be bypassed and all data can be read via ADB anyway - it would only make sense once at boot. Is there a way to have two passwords (1 at boot and an easier one at screenlock) for example?
Is this issue related to Magisk? And can it be fixed?
monicaONxda said:
Does this only affect the TWRP -encryption, because when you set your lockscreen password (for the auto-encrypted userdata partition in Android 10, for example) the data can't be decrypted without this password..?
I have discovered another security issue however on a rooted device:
On my Magisk-rooted and encrypted Note 10+/Exynos (Android 10) I just found out, that the userdata (data/data ) partition is UNENCRYPTED and fully readable when viewed with an ADB viewer from my PC although the device is in lockscreen mode / locked!
This doesn't happen after reboot before the first unlock! After the device has been unlocked, accessed via ADB and re-locked (but not rebooted) it is (still) unencrypted, even after rebooting the PC!
Here the lockscreen password would not make much sense at every screenlock - it just unlocks the screen which can be bypassed and all data can be read via ADB anyway - it would only make sense once at boot. Is there a way to have two passwords (1 at boot and an easier one at screenlock) for example?
Is this issue related to Magisk? And can it be fixed?
Click to expand...
Click to collapse
Anyone with thoughts on this...?
monicaONxda said:
Anyone with thoughts on this...?
Click to expand...
Click to collapse
There are two, separate passwords. One for the encryption and one for the lock screen. And they don't have to be the same.
If you remove the encryption by formatting /data and then boot up on stock OOS, it will encrypt /data with a default password. TWRP can decrypt /data because it knows the default password that's used.
When you set the lock screen password you have the option to set the encryption password to be the same or not.
So, you could set the lock screen and encryption password to be something and then change the lock screen password only to be something different.
ADB can only access /data after it has been decrypted, ie the phone has booted up. But only if: 1. ADB is enabled, 2. You have given permission on your phone to trust the PC connecting to the phone.
So, there's no back doors here. If you have set an encryption password, you can't access the data without having entered the password. And you can't access the phone data without entering the lock screen password. And you can't access the data via ADB unless you have given the specific PC permission from your phone.
Of course, if you use the default encryption password and have TWRP installed, you might just as well not have a password at all. But that's up too you.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
When you set the lock screen password you have the option to set the encryption password to be the same or not.
So, you could set the lock screen and encryption password to be something and then change the lock screen password only to be something different.
Click to expand...
Click to collapse
For which roms is this working? I guess this behaviour is rom spefic. E.g. for all lineageos 15.1 and 16.0 roms and all roms based on tje same code base, the above procedure (setting the lockscreen passphrase without the boot passphrase checkbox set) will reset the boot passphrase to "default_password".
The only way I know of to get a seperate passphrase for boot and lockscreen on los15, los16 and roms based on these is this:
https://forum.xda-developers.com/on...eplus-3-3t-t3866517/post80390263#post80390263
nvertigo67 said:
For which roms is this working? I guess this behaviour is rom spefic. E.g. for all lineageos 15.1 and 16.0 roms and all roms based on tje same code base, the above procedure (setting the lockscreen passphrase without the boot passphrase checkbox set) will reset the boot passphrase to "default_password".
The only way I know of to get a seperate passphrase for boot and lockscreen on los15, los16 and roms based on these is this:
https://forum.xda-developers.com/on...eplus-3-3t-t3866517/post80390263#post80390263
Click to expand...
Click to collapse
'setting the lockscreen passphrase without the boot passphrase checkbox set) will reset the boot passphrase to "default_password"' - Ah, sorry, I didn't realise that. I was saying this based on what I had done on another phone.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
'setting the lockscreen passphrase without the boot passphrase checkbox set) will reset the boot passphrase to "default_password"' - Ah, sorry, I didn't realise that. I was saying this based on what I had done on another phone.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
I'm pretty sure this behavior is rom dependent and not device dependent. E.g.: in los14 and early los15 builds the user was able to set lockscreen passphrase and boot passphrase seperately from rom's settings. This has been removed from aosp (officially because of "security concerns"; but I guess these "concerns" has been too many users with too less knowledge have locked up the boot process).
For me the cryptfs cli is perfectly ok, for the average user the behaviour you've expirienced may feel more comfortable. But the longer I think about, the more I like the seperate setting... YMMV.
Ever since the day's I have been rooting my Android phones, security increased making it more secure against malware and hackers and protecting your personal data against theft. However the flipside of this is that it also complicates rooting your phone and flashing (custom) ROMS. It has been a while since I rooted my phone so some things are new to me, like LazyFlasher. It disables DM verity & optionally force encrypt.
DM verity, I know, prevents the phone to boot when the system image is modified, force encrypt is kinda new to me. Some people recommend installing LazyFlasher before installing a custom ROM, but do I need to Install LazyFlasher (or any of it's alternatives) to successfully flash ROMS to my phone? What does it actually? Does it make your phone less secure? And when I install LazyFlasher does it mean I don't have to format data after flashing twrp recovery?
Medeon said:
Ever since the day's I have been rooting my Android phones, security increased making it more secure against malware and hackers and protecting your personal data against theft. However the flipside of this is that it also complicates rooting your phone and flashing (custom) ROMS. It has been a while since I rooted my phone so some things are new to me, like LazyFlasher. It disables DM verity & optionally force encrypt.
DM verity, I know, prevents the phone to boot when the system image is modified, force encrypt is kinda new to me. Some people recommend installing LazyFlasher before installing a custom ROM, but do I need to Install LazyFlasher (or any of it's alternatives) to successfully flash ROMS to my phone? What does it actually? Does it make your phone less secure? And when I install LazyFlasher does it mean I don't have to format data after flashing twrp recovery?
Click to expand...
Click to collapse
What I can tell you from personal experience is this., You don't need to flash LazyFlasher on Mi 9t/twrp to flash zip roms, in fact if you tried to flash LazyFlasher it won't flash and you'll get an error (smth about unknown ramdisk compression format). however you'll most likely need to format data. With that said, it depends on the rom so you need to research the procedure before going through with it. I'm like you. My info in this regard is basically outdated and also it appears that when it comes to Xiaomi phones, things are a little different than what i was used to with Samsung, LG, HTC
Aserar said:
What I can tell you from personal experience is this., You don't need to flash LazyFlasher on Mi 9t/twrp to flash zip roms, in fact if you tried to flash LazyFlasher it won't flash and you'll get an error (smth about unknown ramdisk compression format). however you'll most likely need to format data. With that said, it depends on the rom so you need to research the procedure before going through with it. I'm like you. My info in this regard is basically outdated and also it appears that when it comes to Xiaomi phones, things are a little different than what i was used to with Samsung, LG, HTC
Click to expand...
Click to collapse
Thanks, indeed I have tried to flash LazyFlasher and got error 1, like you mentioned. In the 4PDA twrp recovery there is also an option in the 'Advanced options' menu to remove dm-verity and force encryption all the way, instead of disabling it. Wouldn't that be a potential security nightmare?
I've been using all my phones unencrypted and never faced any issue/error/problem.
I've installed this one https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389/amp/
It's the same one (older version) included in Russian and Chinese TWRP.
Medeon said:
Thanks, indeed I have tried to flash LazyFlasher and got error 1, like you mentioned. In the 4PDA twrp recovery there is also an option in the 'Advanced options' menu to remove dm-verity and force encryption all the way, instead of disabling it. Wouldn't that be a potential security nightmare?
Click to expand...
Click to collapse
I have to agree with Schnedi on this. I've been using my phones unencrypted for years with no problem.
Schnedi said:
I've been using all my phones unencrypted and never faced any issue/error/problem.
I've installed this one https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389/amp/
It's the same one (older version) included in Russian and Chinese TWRP.
Click to expand...
Click to collapse
Thanks, I've noticed this one also, good to know that I can flash this without errors. Do you know what this 'disc quota' thing is perhaps or is it just optional?
Medeon said:
Thanks, I've noticed this one also, good to know that I can flash this without errors. Do you know what this 'disc quota' thing is perhaps or is it just optional?
Click to expand...
Click to collapse
It's something related with the storage speed, since Oreo that's not needed.
It's disabled by default, so, no need to modify anything.
Medeon said:
Thanks, indeed I have tried to flash LazyFlasher and got error 1, like you mentioned. In the 4PDA twrp recovery there is also an option in the 'Advanced options' menu to remove dm-verity and force encryption all the way, instead of disabling it. Wouldn't that be a potential security nightmare?
Click to expand...
Click to collapse
I am also getting error 1 while i tried flasing LazyFlasher. Could you please let me know how you fixed it.
Ananthan_ said:
I am also getting error 1 while i tried flasing LazyFlasher. Could you please let me know how you fixed it.
Click to expand...
Click to collapse
I didn't fix anything, just decided to not to flash LazyFlasher, by following the advise given by Aserar in post #2 on this thread. I am currently on the Pixel Experience rom and I didn't need Lazyflasher to get it running on my phone.
Explanation and my thoughts:
There is official TWRP for Samsung Galaxy A20s, but it is not flasheable because doesn't allow it - hash mismatch.
Tried everything: empty vbmeta, google disable-verify vbmeta, some other vbmeta, nothing seems to stop it from mismatch error.
Are there any workaround for recovery partition? I know that you can flash null binaries to break binary checking but afaik it works only for system and vendor. Just some common sense - recovery gets overriden automatically and booting into the recovery on boot won't get anything because it is empty. Booting = overriden.
So there's my questions:
1) Is it possible to bypass that broken hash check?
2) Does Android 9 aboot + vaultkeeper bypass work?
I hope you gets an answer, bc i've gone trought the same issue i've tried every online method possible even before the official release of twrp for this device and after that too, and i still wasn't able to root or instal a custom rom
@
TheAirBlow
I'm working on it now I'll keep you updated
Qcmoff said:
@
TheAirBlow
I'm working on it now I'll keep you updated
Click to expand...
Click to collapse
ok
TheAirBlow said:
ok
Click to expand...
Click to collapse
Hello...
Something new about root a20s?
I have tried in many ways but I could not