I haven't been able to decrypt the Razer Phone yet, I want viper4android to work on it but it refuses because of encryption.
I've tried these things directly after a fresh flash without booting in to the system:
1. Formatting Data in Twrp (causes bootloop)
2. Trying to get rid of it via Magisk flashing tricks. (No success, still encrypted)
3. Modified .fstab files from "forceencrypt=" to "encryptable". (No success, still encrypted)
Anyone got any ideas on how to get rid of encryption? I'm out of ideas for now.
Thanks in advance
Fastboot erase data
RUNNERX said:
Fastboot erase data
Click to expand...
Click to collapse
Totally forgot about fastboot. However, it doesn't seem to work, it throws me a error message.
I tried these commands:
fastboot erase data (Doesn't work like I said.)
fastboot format data (Doesn't work)
fastboot erase userdata (Doesn't work)
fastboot format userdata (Command works, but bootloops after reboot)
(Edit1: Can't remember what it was, but I do know it said FAILED.)
(Edit2: My drivers are properly installed btw)
Sorry for double post but have anyone successfully decrypted it yet?
I tried the things that worked for me in the past but still haven't managed to get anywhere. Now that more time has gone by have you had any luck?
In magisk there is a "preserve force encryption". I'm so afraid of losing data that I have not tried this option.
Munk0 said:
I tried the things that worked for me in the past but still haven't managed to get anywhere. Now that more time has gone by have you had any luck?
In magisk there is a "preserve force encryption". I'm so afraid of losing data that I have not tried this option.
Click to expand...
Click to collapse
I've been looking at the kernel source for the Razer Phone, it seems like during the first boot the kernel encrypts data. So for the past month I've been learning how to build kernels and succeded quite a bit with different phones (Galaxy S5/S7/S8 and Pixel 2), however the Razer Phone I've not had much success with yet, still working out build errors and other stuff.
So the kernel might be what encrypts data and a custom kernel with encryption deactivated might help, but it would be nice if anyone have the solution to decrypt WITHOUT a custom kernel.
However I'm not 100% sure if it really is the kernel doing it, so take my post with a grain of salt.
If you find something else about decryption, please tell me aswell.
Best regards,
Nao
Related
Hi folks,
For some stupid reason, I tried to encrypt my phone from within TouchWiz Security Settings. I entered a password for the encryption, and as soon as I clicked start, the process stopped and an error saying "com.android.systemui has stopped" has appeared. If I click OK it pops up again. Restarting the phone gives the same error, and I can't actually use the phone at all, as the error message keeps popping up even if I try to enter the correct password.
I tried reflashing the rom, wiping data, cache and so on, and the same error message pops up as soon as TouchWiz loads up. I don't know how to transfer another rom from my computer to the phone from within CWM (I don't see my phone's storage from within windows).
I thought I'd do a complete unroot, but the stock firmware available for this device is older than 4.4 (which is what I have because I'm using Enewman's SRx 4.0). Everywhere I read it says "DO NOT DOWNGRADE".
I'm not sure what to do, and I have very limited expertise in this matter.
Thank you for all your help folks!
Were you rooted with cwm when you to encrypt? I did this with my s3. I was fortunate that process failed but I was still able to boot the phone.
Since you have cwm, did you try formatting the system before installing a new rom?
audit13 said:
Were you rooted with cwm when you to encrypt? I did this with my s3. I was fortunate that process failed but I was still able to boot the phone.
Since you have cwm, did you try formatting the system before installing a new rom?
Click to expand...
Click to collapse
Yep, I was rooted and using CWM. The phone still boots to TouchWiz, but then the error comes up and I can't use the phone at all. I tried formatting the system before installing a new rom too...
So I used adb to sideload CyanogenMod, and flashed it. That seems to have helped the problem
So the in call volume in AOSP ROMs (tries carbon, quantum, cm11) is way too high. Tried reflashing any other kitkat based touchwiz ROM but immediately upon first boot I get prompted to insert the encryption password. When I do, it asks it again. Is there any way to somehow get a touchwiz ROM to work on my phone now? I alwaya do clean installs. Thanks guys
It is my understanding that encryption requires stock recovery.
What bootloader is on your phone?
Looks like I'm on the UCUFNE4. every touchwiz ROM I install asks for decryption, and all the other ROMs are installing OK..
Have you tried using Odin to flash a stock ATT KK ROM?
Edit: nevermind, looks like there is no 4.4.2 ATT ROM on sammobile.com. I assume you already tried wiping cache, dalvik, and data.
Yes I have tried to wipe everything. Even internal storage. So then I had to sideload a ROM using adb. I really appreciate your input!
It sounds to me like the data portion is still encrypted. Were you able to use fastboot commands to erase cache, data, and system before flashing a new ROM?
Well I used TWRP to erase data, cache and dalvik and system. Would that be equivalent to fastboot?
tequilaboom said:
Well I used TWRP to erase data, cache and dalvik and system. Would that be equivalent to fastboot?
Click to expand...
Click to collapse
It might be but I have never compared the two methods.
Are you able to issue fastboot commands to your phone?
I have never done fastboot but I could try using it. What should I do with fastboot?
tequilaboom said:
I have never done fastboot but I could try using it. What should I do with fastboot?
Click to expand...
Click to collapse
Boot the phone into download mode, connect the phone to the computer via USD, let it install the Samsung drivers. You will also need the necessary ADB/fastboot files from here: http://dottech.org/26188/usb-adb-and-fastboot-drivers-for-windows-for-all-android-phones/
Boot to an command prompt in Win7 or Win8. Navigate to the directory where you installed the ADB/fastboot files and type this: fastboot devices and press enter. Hopefully, your device will appear.
OK, and once I'm in fastboot, by formatting the data partition, and attempting to install a TW rom, you think it'll fix the problem? Is there something else I have to do in fastboot (what is the sequence of commands?)?
tequilaboom said:
OK, and once I'm in fastboot, by formatting the data partition, and attempting to install a TW rom, you think it'll fix the problem? Is there something else I have to do in fastboot (what is the sequence of commands?)?
Click to expand...
Click to collapse
Here's a good guide:
http://forum.xda-developers.com/showthread.php?t=2225405
alright I followed the guide, but still no effect
Did the fastboot commands work?
Did you try erasing the userdata partition? Did you try formatting the userdata partition?
I apologize, I should have said that I had no success even after trying to follow the guide. I attempted to use fastboot but when trying to detect my device, nothing showed up in that command window. ADB works no problem (detects device). Again after several tries of formatting the data partition (and everything else), every touchwiz rom asks for the encryption password. However, now when I enter it, the green android with gear appears, and then the device restarts. touchwiz now asks for the decryption password once again....
So typing fastboot devices didn't list anything? Were you in download mode?
Hello,
Whenever i encrypt my phone on DU, when i set the lock screen Password it asks me if i want the phone to ask it to be able to boot, but then, the phone refuses to boot and says that the Password is wrong.
But when i boot into twrp the Password works and i can decrypt the data partition.
I already had the issue but with the phone accepting the boot pin but twrp not.
This is on a fresh DU install with previously formated data partition.
DO NOT encrypt via custom roms: it's cause of troubles and compatibility issues, especially when returning to OxygenOS.
So:
1) Put device in bootloader mode, plug it to computer, type fastboot format userdata via ADB terminal.
2) Go in TWRP and wipe all the partitions (be sure to have /cache formatted in ext4, otherwise change its filesystem):
3) Always from TWRP, flash latest OOS firmware (4.1.6 or OB19);
3) Reboot and configure setup with your PIN required at bootup;
4) After completing wizard, reboot in TWRP;
5) Now you can wipe anything and flash your rom.
Now device should require your PIN even at first boot of DU.
Ps until doing another fastboot format userdata, device will keep encryption.
Simone98RC said:
DO NOT encrypt via custom roms: it's cause of troubles and compatibility issues, especially when returning to OxygenOS.
So:
1) Put device in bootloader mode, plug it to computer, type fastboot format userdata via ADB terminal.
2) Go in TWRP and wipe all the partitions (be sure to have /cache formatted in ext4, otherwise change its filesystem):
3) Always from TWRP, flash latest OOS firmware (4.1.6 or OB19);
3) Reboot and configure setup with your PIN required at bootup;
4) After completing wizard, reboot in TWRP;
5) Now you can wipe anything and flash your rom.
Now device should require your PIN even at first boot of DU.
Ps until doing another fastboot format userdata, device will keep encryption.
Click to expand...
Click to collapse
Thanks for the answer, do you know why custom rom encryption doesnt work ? I used to to this on my old s5 and it worked perfectly
nikexv2 said:
Thanks for the answer, do you know why custom rom encryption doesnt work ? I used to to this on my old s5 and it worked perfectly
Click to expand...
Click to collapse
Maybe if you give his post a thumbs up he might continue helping you out , I mean that's the least you could do ......
Xceeder said:
Maybe if you give his post a thumbs up he might continue helping you out , I mean that's the least you could do ......
Click to expand...
Click to collapse
If members had to wait for thumbs up before they answer to someone's post then they wouldn't answer most of them.
What kind of **** philosophy is this, i hope for you that's not your way of thinking everyday.
And even, that's none of your business, maybe i forgot to like his post ?
Come on, do not vent on XDA, do not make useless quarrels ?
@nikexv2 sorry, but technically speaking, I don't know the reason of problematic encryption on custom roms.
Just enable encryption with official firmware and there's no other compatibility issue.
Encryption still remains when you full wipe device via recovery.
Have a good day.
nikexv2 said:
If members had to wait for thumbs up before they answer to someone's post then they wouldn't answer most of them.
What kind of **** philosophy is this, i hope for you that's not your way of thinking everyday.
And even, that's none of your business, maybe i forgot to like his post ?
Click to expand...
Click to collapse
It works like this - you ask for help and if someone gives you good advice or helps you out in any way then a quick thumbs up is appreciated , it's just courtesy but anyway I hope you get your phone sorted out ...
nikexv2 said:
Hello,
Whenever i encrypt my phone on DU, when i set the lock screen Password it asks me if i want the phone to ask it to be able to boot, but then, the phone refuses to boot and says that the Password is wrong.
But when i boot into twrp the Password works and i can decrypt the data partition.
I already had the issue but with the phone accepting the boot pin but twrp not.
This is on a fresh DU install with previously formated data partition.
Click to expand...
Click to collapse
Not sure what's wrong with your set up but I came from OOS OB19 to DU, wiped userdata to switch data to ext4, flashed DU + beans gapps (recommended for DU) then booted up, encrypted my phone via Settings > Security and set ask pin on booting device, same pin has worked on all ROMs, even tried some OOS based ones like Freedom OS CE, now on Omni + open gapps, I'm using blu spark latest recovery.
Bought new OP5t
Update OOS 5.1.5 latest
Unlock bootloader
Flash TWRP recovery
Wipe everything except otg format
Install lingue os 15.1 gapps 8.1 pico
Boot normally
Then try to install red flare kenel, magisk zip boot to fatboot menu can't boot make nandroid backup twrp then try to restore also boot on bootloader menu try to download magisk apk download but it's blank can't install notification bar have strange one
Discover trust "get to know to assure how your device is safe"
I don't know what happened if someone could help me if I didn't something wrong please
Hello. Need help is exactly what I need right now. Basically, I just tried flashing Oxygen OS from LineageOS, as I was just getting a little annoyed about how the updates were getting stupid and apps kept crashing. However, when I did this, it got stuck on just a sec when I was setting up. I then tore through the internet looking for how to wipe /data and /data/media with twrp command line. I found out about fastboot erase userdata. I used that. However, it wasn't just the casual wiping of the data where everything goes except the critical files. I mean every single little god damn thing got removed. I tried pulling /data and it said 0 files pulled. I was not happy. I managed to flash the rom but the phone won't boot. the worst part, I tried mounting /data on twrp and it said failed to mount data, invalid argument. So that was that. I then formatted to the original using the twrp format, (needed sighted help for that...) And it succeeded. Now however, I try mounting and it says no such device. 1, how can I mount data? And 2, how can I get a data partition that actually works with setting up and even the booting up of my phone. Yes, it won't boot.
Please help me, you don't believe how annoying it is to have a virtually useless phone.
tobias
PS, I was using stock bootloader and twrp recovery. Also, please give the answer of fixing in a command line method, I'm blind so getting sighted help would be rather annoying.
Tobias101 said:
Hello. Need help is exactly what I need right now. Basically, I just tried flashing Oxygen OS from LineageOS, as I was just getting a little annoyed about how the updates were getting stupid and apps kept crashing. However, when I did this, it got stuck on just a sec when I was setting up. I then tore through the internet looking for how to wipe /data and /data/media with twrp command line. I found out about fastboot erase userdata. I used that. However, it wasn't just the casual wiping of the data where everything goes except the critical files. I mean every single little god damn thing got removed. I tried pulling /data and it said 0 files pulled. I was not happy. I managed to flash the rom but the phone won't boot. the worst part, I tried mounting /data on twrp and it said failed to mount data, invalid argument. So that was that. I then formatted to the original using the twrp format, (needed sighted help for that...) And it succeeded. Now however, I try mounting and it says no such device. 1, how can I mount data? And 2, how can I get a data partition that actually works with setting up and even the booting up of my phone. Yes, it won't boot.
Please help me, you don't believe how annoying it is to have a virtually useless phone.
tobias
PS, I was using stock bootloader and twrp recovery. Also, please give the answer of fixing in a command line method, I'm blind so getting sighted help would be rather annoying.
Click to expand...
Click to collapse
Flash this solve your proplem
https://drive.google.com/file/d/14QnXJH9TWMZnYI9RItIPv8ivGUjz1q5S/view
Not being rude, but do you really think no verity is going to help? I mean it usually doesn't fix stuff. Besides, thanks but it's not that it is encrypted, I can flash things if I know their directery, it's just that data can't be mounted. But thanks, I'll try flashing no verity and see what happens.
Many thanks
Tobias101 said:
Not being rude, but do you really think no verity is going to help? I mean it usually doesn't fix stuff. Besides, thanks but it's not that it is encrypted, I can flash things if I know their directery, it's just that data can't be mounted. But thanks, I'll try flashing no verity and see what happens.
Many thanks
Click to expand...
Click to collapse
That's all I can help with I'm not professional sorry.
Tobias101 said:
Hello. Need help is exactly what I need right now. Basically, I just tried flashing Oxygen OS from LineageOS, as I was just getting a little annoyed about how the updates were getting stupid and apps kept crashing. However, when I did this, it got stuck on just a sec when I was setting up. I then tore through the internet looking for how to wipe /data and /data/media with twrp command line. I found out about fastboot erase userdata. I used that. However, it wasn't just the casual wiping of the data where everything goes except the critical files. I mean every single little god damn thing got removed. I tried pulling /data and it said 0 files pulled. I was not happy. I managed to flash the rom but the phone won't boot. the worst part, I tried mounting /data on twrp and it said failed to mount data, invalid argument. So that was that. I then formatted to the original using the twrp format, (needed sighted help for that...) And it succeeded. Now however, I try mounting and it says no such device. 1, how can I mount data? And 2, how can I get a data partition that actually works with setting up and even the booting up of my phone. Yes, it won't boot.
Please help me, you don't believe how annoying it is to have a virtually useless phone.
tobias
PS, I was using stock bootloader and twrp recovery. Also, please give the answer of fixing in a command line method, I'm blind so getting sighted help would be rather annoying.
Click to expand...
Click to collapse
brad:
It won't mount data for many reasons but just installing stock recovery and installing OOS would fix everything.
https://forum.xda-developers.com/on...-revert-to-oos-oreo-8-1-t3730952/post75096633
Hi everyone, I was usually providing help on this forum, now i'm the one desperate for help after some unforeseen consequences.
Bear in mind I'm kind of a noob anyway.
I have seen the message on the telegram groups for our device regarding solving the los 17 problems with the ril and camera. So i have followed the steps. I flashed the last twrp 3.4 by jarl using the official twrp app and then rebooted to recovery, wiped everything beside the internal storage and tried flashing the last los 16 zip.
And then the disaster happened. firstly the log returned error 7 so i've rebooted to recovery again and attempted to flash the same zip again without wiping anything. well the flashing worked apparently but i couldnt boot into it as it showed me an infinite boot animation.
Then i rebooted to recovery and it prompted me with a decryption key request which i didn't set before. I cancelled the prompt and I moved forward and proceeded wiping everything including the internal storage thinking that was the problem. Maybe it was maybe it wasnt, now I'm no longer prompted by any decryption key, but I was hoping i could connect to my pc through mtp, transfer some zips and flash some functional rom. Even though I enable mtp and my pc detects the phone I can't access any storage nor the internal, nor the sd card.
I tried going through multiple versions of twrp as i can still access my bootloader and i can still flash recoveries through fastboot but i feel that i'm stuck and I dont know what i should try anymore.
Before trying all this I was on an older build of los16 with the oreo firmware.
First of all, use this TWRP: https://build.twrp.me/twrp-3.4.0-0-montana.img
Second of all, do not flash TWRPSARer (if you did). Make sure the LOS16 zip isn't corrupted (which normally causes error 7), then format system, data, cache, vendor and dalvik. Reflash LOS16 and boot
JarlPenguin said:
First of all, use this TWRP: https://build.twrp.me/twrp-3.4.0-0-montana.img
Second of all, do not flash TWRPSARer (if you did). Make sure the LOS16 zip isn't corrupted (which normally causes error 7), then format system, data, cache, vendor and dalvik. Reflash LOS16 and boot
Click to expand...
Click to collapse
I wasnt using the twrp sar, i was using the exact version you linked. And I can't flash any rom because i cant get the zip inside my internal memory.
You can try using adb sideload. adb sideload path/to/zip
worked like a charm. thanks a lot, Jarl.
And this, is the story of someone who didn't want to wait long enough for the ROM to boot
Nah JK, but long boot-times normally = Force Encrypt Enabled
Some random said:
And this, is the story of someone who didn't want to wait long enough for the ROM to boot
Nah JK, but long boot-times normally = Force Encrypt Enabled
Click to expand...
Click to collapse
it might have been the problem, but if it is it should be a disclaimer for that on the los16 page. the boot time is way longer than the usual.
Aythriel said:
it might have been the problem, but if it is it should be a disclaimer for that on the los16 page. the boot time is way longer than the usual.
Click to expand...
Click to collapse
Yes, I'll make sure to note that
Dear XDA-Developers, after installing August 2020 update for my Pixel 2 XL and possibly applying incorrect Magisk bootloader version, my phone doesn't boot anymore and is constantly stuck in bootscreen animation.
What I have tried so far to no result:
- Re-flashing both May 2020 (previous working version) and August 2020 without -w flag to preserve my data that I would ideally like to recover.
- Side-loading May 2020 and August 2020 OTA versions through TWRP
- Creating and booting from Magisk-core only image as per guide called "How to Create & Boot from a Magisk Core-Only Image to Fix a Bootloop Without Custom Recovery" (since I cannot post links in here).
While unpacking and repacking Magisk-core image I noticed that "BOARD_OS_PATCH_LEVEL 2020-05" indicating that I might have had the wrong version applied to it.
So looks like my only hope is finding magisk_patched.img file for August 2020 Pixel 2 XL (image-taimen-qq3a.200805.001) and trying to patch it to disable Magisk upon startup. Would anybody be so kind to post one here?
I have also tried to make data backup using TWRP, but it fails mounting /data partition and shows that it's 0 Mb.
Any other ideas to how to save the phone without wiping all the data would be greatly appreciated.
Thank you all very much for whatever suggestions you might have to help me!
hencrow said:
So looks like my only hope is finding magisk_patched.img file for August 2020 Pixel 2 XL (image-taimen-qq3a.200805.001) and trying to patch it to disable Magisk upon startup. Would anybody be so kind to post one here?
Click to expand...
Click to collapse
Magisk doesn't touch the bootloader, only modifying the boot image. Given your description of the issue, I don't believe Magisk to be the culprit here. Based upon personal experience, flashing a stock image using flash-all.bat, whether the -w flag is present or absent, totally removes Magisk as the stock boot image overwrites the modified version created by Magisk.
It's clear though that you have an issue, but how much of it is brought about by misconceptions and incorrect knowledge is unknown and at this point irrelevant. So what do you do now? Try backing up your data using the instructions here. But be prepared for the very real possibility that you have already lost all your data, and only a stock ROM install with the -w flag present will restore the device to working order.
Strephon Alkhalikoi said:
So what do you do now? Try backing up your data using the instructions URL. But be prepared for the very real possibility that you have already lost all your data, and only a stock ROM install with the -w flag present will restore the device to working order.
Click to expand...
Click to collapse
Thanks for getting back. I'm a little confused how can adb backup can work though if the only thing I can boot into is TWRP and even it fails to decrypt /data partition (it just shows "Could not mount /data and unable to find crypto footer" upon startup).
And with my very limited Android debugging experience wondering if things are really that hopeless that it's not possible to simply copy and decrypt user data partition or there aren't even any logs from failed Android boot attempts that can be looked at to at least diagnose the issue.
hencrow said:
Thanks for getting back. I'm a little confused how can adb backup can work though if the only thing I can boot into is TWRP and even it fails to decrypt /data partition (it just shows "Could not mount /data and unable to find crypto footer" upon startup).
And with my very limited Android debugging experience wondering if things are really that hopeless that it's not possible to simply copy and decrypt user data partition or there aren't even any logs from failed Android boot attempts that can be looked at to at least diagnose the issue.
Click to expand...
Click to collapse
It may not work, and in fact it probably won't, especially if TWRP can't mount the data partition. That's why I said you should be prepared for the very real possibility that you have lost all your data. As for getting logs to diagnose the issue, the only certain way to get a catlog is to record the logcat from the device on your PC as you boot it, via USB Debugging. Something that likely will not be of much help now, given what you have tried doing to resolve the issue.
At this point, in your position I would simply cut my losses and install a factory image and let it wipe the data. Once you are back up and running, you want to get into the habit of backing up app data. There are many apps that can do this, but regardless of the app used, backing up the app data to internal storage or to a location like Mega or Dropbox will make life easier if you ever encounter this again.
An update if anybody is wondering what happened - flashing Android 11 Beta 3 brought the phone back to life with all the data intact. All versions of Android 10 haven't even reached the booting stage where adbd was started and showed no logs.