I have tested some unofficial recovery, but none of those worked.
issues :
1. Touch doesn't response.
2. Only in pitchblack recovery touch worked, but doesn't shows internal storage files, just shows unknown inaccessible files which I don't have in internal storage.
So, does anyone know about a recovery with which I can flash gapps?, or any other way to flash gapps without root, like with pc?
Similar problem here. Unoffical TWRP doesn't respond to touch inputs for me, PBRP does. The garbeled letters inside your storage is probably because of the encryption of the phone.
I don't know on which version you are, but I downgraded to MIUI 11, there you can access the files, sometimes I have to enter my phone password, sometimes not.
It's still encrypted with "FBE" (File Based Encryption) though... At least my console is giving me that output. I can reach the files anyways and flash them, a few of them are working, but often I get errors while trying to flash different types of zip files. The errors are often because of this "FBE" encryption, so the recovery can't mount some partitions or can't access some files (Permission denied)...
But by now, I did not find any way or flashable zipfile (LazyFlasher, etc.) in the web that works to turn the decryption off.
the only build where touch works is 0108. https://androidfilehost.com/?fid=17248734326145712658
iReebu said:
Similar problem here. Unoffical TWRP doesn't respond to touch inputs for me, PBRP does. The garbeled letters inside your storage is probably because of the encryption of the phone.
I don't know on which version you are, but I downgraded to MIUI 11, there you can access the files, sometimes I have to enter my phone password, sometimes not.
It's still encrypted with "FBE" (File Based Encryption) though... At least my console is giving me that output. I can reach the files anyways and flash them, a few of them are working, but often I get errors while trying to flash different types of zip files. The errors are often because of this "FBE" encryption, so the recovery can't mount some partitions or can't access some files (Permission denied)...
But by now, I did not find any way or flashable zipfile (LazyFlasher, etc.) in the web that works to turn the decryption off.
Click to expand...
Click to collapse
Thanks for the reply,
All the things are same for me too. But for most of the people unofficial twrp 3.4.2b works fine, i don't know the problem with my device, and i'm in miui 12.0.3
Related
Hello
This is TWRP v 2.8.1.0 for the S4 Mini. It works for the I9195 - I do not know if it works for similar devices.
The problem was that TWRP after version 2.7.1.0 did not boot up - the phone tried to enter recovery mode but eventually booted into android.
This is because of commit https://gerrit.omnirom.org/#/c/8471/ which does not seem to work nice with the S4 Mini.
DISCLAIMER : You apply this recovery at your own risk - if something breaks or bricks I am not responsible
IMPORTANT NOTE :
a) The attached file is NOT a flashable ZIP and I will not provide one. You have to unpack the attached file and use heimdall or dd. If someone wants to provide a flashable zip - I am fine with that.
b) There is no F2FS support.
c) I do not know if there are still problems with the recovery sometimes not booting up - I tried it a couple of times and it worked every time. Tell us if you experience booting problems.
d) I am no coder - so I cannot help with things like encryption, luks or similar wishes.
How to install:
a) Boot your phone to download mode
b) Connect phone to PC
c) Get root on your PC
d) Unzip attached ZIP file
e) Check md5sum
f) heimdall flash --RECOVERY recovery.img --no-reboot (dd should work as well - take care of the right partition)
Thanks goes to:
Teamwin
OliverG96
_that
Additional information:
If you want to build this by yourself from sources open file twrp-functions.cpp and search for line:
Code:
int TWFunc::Set_Brightness(std::string brightness_value)
You can change it like that:
Code:
int TWFunc::Set_Brightness(std::string brightness_value)
{
return 0;
std::string brightness_file = DataManager::GetStrValue("tw_brightness_file");;
This should fix the problem. According to one of the developers there should also be a flag for specifying a brightness file that one can probably set to /nobrightness.
It works great on my I9195 !
From your recovery, i created the Odin version and flashed it.
Thank you very much.
I attach the Odin version of your recovery (Instructions: unzip the .zip file, and flash the .tar.md5 file with Odin 3.09 into AP field)
Recovery flashable ZIP version of TWRP 2.8.1.0 attached.
Mounting both (Internal and External) doesnt work
mike_san said:
Mounting both (Internal and External) doesnt work
Click to expand...
Click to collapse
What do you mean? Mounting works for me - I can mount System and Micro SDCard and I can access the files there with the TWRP File Manager. So no problem here. Works also with adb - I got access to the full file system. Might be a problem with your phone/setup.
thomson.aa said:
What do you mean? Mounting works for me - I can mount System and Micro SDCard and I can access the files there with the TWRP File Manager. So no problem here. Works also with adb - I got access to the full file system. Might be a problem with your phone/setup.
Click to expand...
Click to collapse
I confirm this.
I tried to mount and unmount System, Data and micro Sdcard... all ok.
Will it work with f4k kernel ?
lars85destroyer: both CM 12 and f4k work fine with or. As the recovery used isn't kernel dependent anyway, it's not an issue.
Works great so far, noticed only one (minor) issue:
I need to use encryption for my phone and for its backups as well (I'm a sysadmin and my phone is fully equipped to access my datacenter). When using keyboard to type encryption/decryption passwords, somethimes I hit one key and completely another key gets pressed, can't be due to fat fingers because wrong key that gets pressed is usually very far from the original one. This was very iritating sometimes since I needed to type passwords for 3-4 times in a row for them to work. Figured out how to prevent this, I look at whole keyboard carefully on every keystroke and I'm usually able to see when it gets buggy and hits wrong key (keystroke animation is trigerred), but this isn't very fast or comfortable...
I think I had the same problem with early versions of TWRP 2.7 posted here but it has been resolved in newer ones. Otherwise, works as a charm, if someone added full F2FS support it would be totally perfect
PS If my memory serves me well, fix was build.prop related.
ericlnu said:
lars85destroyer: both CM 12 and f4k work fine with or. As the recovery used isn't kernel dependent anyway, it's not an issue.
Click to expand...
Click to collapse
works fine on aicp, Thanks
s.basketbuild.com/devs/F4k/twrp/serranoltexx
this one have F2FS
I just decided to move to CM12.1 on my Droid Turbo (XT1254) after the 1/27 Snapshot (YOG7DAO3J1) was posted. I am running this with TWRP 2.8.7.0, BHB27 Kernel, and OpenGAPPS 5.1. So far, almost everything has been fantastic and the performance of the device is like night and day compared to the Verizon software.
My problem is that the CM12.1 ROM has my device encrypted to begin with, which is nice but giving me trouble. I can't get into TWRP to install Xposed framework or other .zips via ADB. I have tried the following:
Disabling require password on startup
Changing the password in Android
Changing the password from root ADB shell
Using a pin
Trying "default_password"
Can anyone give me a solution or some advice? Any help is greatly appreciated!
Having same issue with TWRP not recognizing any decryption password given... Any ideas out there? Is TWRP incompatible with Droid Turbo HW Encryption, or ?
P_6 said:
Having same issue with TWRP not recognizing any decryption password given... Any ideas out there? Is TWRP incompatible with Droid Turbo HW Encryption, or ?
Click to expand...
Click to collapse
This thread is kinda old and I assumed nobody really knew what was going on with it either. I ended up just not using the encryption. The first time around mine was encrypted without me knowing, which was the issue. I just wiped all partitions and flashed the ROM again...
I am having a similar issue so i thought i would chime in, despite the older thread. I had a stock ROM that was encrypted and I was able to unlock and root with SunShine fine. Flashed on TWRP 2.8.7 and ran into a "Unable to mount storage. Failed to decrypt data" error. Updated to TWRP 3.0.0 and still have the same issue. Still working through a resolution as the phone is still functional if I just boot normally. When you mentioned you wiped all partitions, what process did you use? If i can just get access to the interal storage I can flash a ROM and be good to go.
Asyt said:
I am having a similar issue so i thought i would chime in, despite the older thread. I had a stock ROM that was encrypted and I was able to unlock and root with SunShine fine. Flashed on TWRP 2.8.7 and ran into a "Unable to mount storage. Failed to decrypt data" error. Updated to TWRP 3.0.0 and still have the same issue. Still working through a resolution as the phone is still functional if I just boot normally. When you mentioned you wiped all partitions, what process did you use? If i can just get access to the interal storage I can flash a ROM and be good to go.
Click to expand...
Click to collapse
So far, the only way I have been able to get encryption working with CM12.1 on the Droid Turbo is to do the folllowing (Note: This assumes you have bootloader unlocked and TWRP installed as your recovery):
Part 0: Make sure you have what you need
1. Stock Droid Turbo Firmware SU4TL for your device
2. The version of CyanogenMod 12.1 that you need. I recommend a Snapshot, but it's up to you.
3. TWRP 3.0.0 or later for your Droid Turbo.
Part 1: Final set up (Yes, we do this first)
1. Download CM12.1 & Download OpenGapps arm for 5.1
2. Wipe device (system, data, cache, internal storage), copy CM12 install zip and opengapps install zip via USB to device.
3. Flash CM12 and OpenGapps in TWRP
4. Set up device how you want it to be (install your apps, set up your accounts, etc).
5. Set whatever lock-screen PIN / Password / Pattern you are going to want on your phone in general!
6. Make a Nandroid backup of your 100% set up phone in TWRP
7. Copy your backup TWRP folder to your PC.
Part 2: Encrypt device and put everything back how we want it.
1. Flash stock Verizon firmware (SU4TL) via Fastboot. Do not flash stock Recovery, but put back TWRP if you did somehow (I use a simple bash script I have attached below).
2. Boot device, go through initial set up, don't download apps (we're going to be wiping the device soon).
3. Make sure your battery is 80%+ charged, and your device is plugged in.
4. Set a password or PIN on your phone.
5. Encrypt your device (this will be fairly fast, as /data is empty, but you should be asked for your encryption password on boot.)
6. Reboot to recovery. TWRP will ask you for your password to decrypt. It should work with no problem.
7. Copy your backed-up TWRP folder with your CM12 install to your device via USB. The TWRP folder goes in the Internal Storage root directory.
8. Still in TWRP (Do not reboot), go to Restore, and select the backup you just copied over. This will replace the stock rom with your CM12 backup.
9. Your CM12 install will be restored, but your device will remain Encrypted.
10. Reboot into CM12. Win.
You will need to decrypt your device every boot with the password that you selected when you initially encrypted your device. Your lock-screen password CAN BE DIFFERENT. That is why I do it this way. I have a fairly long password to decrypt my device on boot-up, but a pattern as my lock screen. That way I can quickly get into my phone during daily use without having to constantly type in a fairly complicated password.
I failed similar times to root my phone with twrp 3.2.xx and 3.1.xx. I used Odin 3 v3.13.1.
Any ideas or thread links for the young padawan?
I appreciate your advice masters :good:
Using Odin Flash TWRP latest from the note 8 TWRP thread here on XDA, one on their site is not latest.
Install magisk manager app from play store.
Download magisk from the app.
Reboot to TWRP and flash the magisk file just downloaded.
Reboot and check magisk manager for root and hide.
Should be good.
Nope. Not working and still ends in a bootloop and it's unable to mount the internal storage.
Something went wrong, so.. my phone is unable to boot the system after that!
The issue is the version of TWRP and Oreo, its not yet compatible on this device, it needs porting over
If you want MAGISK you need to do it all in one hit.
Flash TWRP
Select Read Only Option.
Format Data
Reboot Recovery
Flash the DM Verify Encrypt file
Reboot Recovery, You could be able to flash files wihtout a Data mount error.
Now flash the files you want, i..e MAGISK
Once you have booted the ROM and return back to TWRP you are unable to mount Data.
This can cause various issue when flashing files
Funny you.. How can I format if the internal storage isn't able to mount?
"Select Read Only Option.
Format Data" <-- seems like a contradiction to format a missing
partition.
I think we need to wait until someone will port the twrp for Oreo. cheerio!
Because it needs to be done when you first flash it.
Once you have flash Oreo, Then TWRP, You boot into TWRP and format. You then Flash the DM Verify.
Data is accessible, its empty but accessible, Flashing any files like MAGISK work without any errors.
I have it all working on mine without any issues, I do know if i need to flash any additional files it wont work properly due to Data no longer mountable.
There is a updated version of TWRP that fixes this, but its not been ported over.
Hello, I recently bought the Xiaomi MI 6X and I want to install Android to replace the MIUI since I have certain limitations.
I have problems to install the Android image through the TWRP, after passing the image of TWRP to the cell phone with the command "fastboot boot twrp-3.2.3-1-wayne.img" the TWRP screen appears asking for a password, apparently it is encrypted, the strange thing is that I do not have a password on the phone and still ask me for the password, I have the option to swipe and go to the TWRP options, but when I'm in the options to install the image I can not see all the files / folders to find the image of Android that I copy in the internal memory, in addition to this I mark "0 BM Internal Storage" when I am scanning the files.
I really need your help to solve this problem, it is becoming a headache for me, help please!
isaac.nunez said:
Hello, I recently bought the Xiaomi MI 6X and I want to install Android to replace the MIUI since I have certain limitations.
I have problems to install the Android image through the TWRP, after passing the image of TWRP to the cell phone with the command "fastboot boot twrp-3.2.3-1-wayne.img" the TWRP screen appears asking for a password, apparently it is encrypted, the strange thing is that I do not have a password on the phone and still ask me for the password, I have the option to swipe and go to the TWRP options, but when I'm in the options to install the image I can not see all the files / folders to find the image of Android that I copy in the internal memory, in addition to this I mark "0 BM Internal Storage" when I am scanning the files.
I really need your help to solve this problem, it is becoming a headache for me, help please!
Click to expand...
Click to collapse
Happened to me a lot of time, I had to format data (with a twrp with working mtp), but if someone have a better idea wait for a different solution
you have to wipe data thats all i know. thats the way twrp can encrypt the storage.
Oceansoul91 said:
Happened to me a lot of time, I had to format data (with a twrp with working mtp), but if someone have a better idea wait for a different solution
Click to expand...
Click to collapse
Ignore
Hi!
My only encounter with rooting was several years back when it used to be a simple affair (one click rooting app based on exploits like framaroot etc), so please bear with me.
I'm on Stock Oreo 8.1 (Patch 1 Aug 2019) Sanders 1804 (India) version. I've followed various guides and have been successful in flashing TWRP 3.4.0 (Official Sanders version) and Magisk 20.4. But everytime the phone is rebooted, TWRP can't mount internal storage and shows 0mb.
I tried all three methods I could find:
1. dm-verity zip flashing - Log said fstab not found. Searched and found that from Oreo, Android's encryption approach has been changed. I couldn't make much sense out of those, though.
2. Manually replacing the `forceencrypt` to `encryptable` then flash stock recovery and format data. Didn't work.
3. Formatting data right after TWRP is flashed. Didn't work either.
The maximum it works is for one time when I can connect the device to laptop to add some zips to it to flash. It doesn't make sense to wipe the data when it's the data only that we want to back!
My purpose is to make flashable zip (nandroid) to revert to if anything goes wrong. It was phone's wifi frequent disconnection (or connected but no internet) issue which forced me to try root. I'm not much interested in new ROMs and am fine with stock itself but need a backup of all apps with data etc. Also, I couldn't understand clearly the FAQ on TWRP website that says TWRP doesn't backup internal storage but backup data. As I don't use SdCard, the internal storage is mounted in /sdcard folder only
I'll really appreciate if someone can help me.
Thanks
Found solution from a helpful guy in a Telegram group.
1. Use ONLY attached zip/img files and follow exact same order.
2. Flash TWRP, reboot to recovery
3. In Wipe section, choose Format data, type YES and confirm. Reboot to recovery again.
4. Flash DM-Verity-ForceEncrypt.zip file. Flash Magisk.zip file. Reboot to recovery.
5. (Optional) Make a backup if you want or Reboot to system. Done!
https://drive.google.com/drive/folders/1h8wb78wLH5_VBmkhjpDjyPyDbUG9ZBV4?usp=sharing