Develop Bugs

Downgrade from 7.1.1 to CM-13 (or root 7.1.1)

Hello
I have a Wileyfox Swift 1 (crackling) which has been updated to 7.1.1
It has been wiped because of plenty of bugs (random reboots, random crashes, it became randomly very slow...)
I want to remove lots of bloatware (Particularly this crapy phone app !), and mostly, I don't want to have to re-enable my custom keyboards after each reboot (which now occurs when I receive a SMS while listening to music) !
Can I :
- Downgrade to CM-13 ?
- Root this 7.1.1 ?
- Install Lineage OS 14 ?
I already have tried this without success :'(

Similar problem
I would love to know how to downgrade back to Cyanogen OS. I loved the phone prior to the Nougat update and now I hate it.
Could anyone provide instructions how to do this, it would be muchos appreciated.
mioux said:
Hello
I have a Wileyfox Swift 1 (crackling) which has been updated to 7.1.1
It has been wiped because of plenty of bugs (random reboots, random crashes, it became randomly very slow...)
I want to remove lots of bloatware (Particularly this crapy phone app !), and mostly, I don't want to have to re-enable my custom keyboards after each reboot (which now occurs when I receive a SMS while listening to music) !
Can I :
- Downgrade to CM-13 ?
- Root this 7.1.1 ?
- Install Lineage OS 14 ?
I already have tried this without success :'(
Click to expand...
Click to collapse

I have tried by myself, even if I have read multiple times that this downgade regularly leads to a brick :
WARNING : All data will be lost during process
Prequisite :
- fastboot and adb installed on your system
- find fastboot files of cm-13.1
6b2b09c40f1a2b85ee5335823640536d cm-13.1.2-ZNH2KAS3LG-crackling-signed-fastboot-84f0d5200b.zip
Click to expand...
Click to collapse
- if you want LineagoOS
-> lineageos file (/!\ don't take last version ! when I have installed this one, my touchscreen was not working /!\ take the image with this date 2017-06-26 10:44:39)
-> twrp file
-> unlocked bootloader
-> lineageos image on external sd card (recommended) or in internal memory AFTER you have restored CM13
Unzip the file, go in the directory and launch these commands
#!/bin/bash
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash aboot emmc_appsboot.mbn
fastboot flash hyp hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot reboot
Click to expand...
Click to collapse
To install lineageos
- you MUST have started CM13 at last one time... I had a bootloop without booting first CM13
- reboot in fastboot mode
- flash twrp :
fastboot flash recovery twrp-<version>.img
fastboot boot twrp-<version>.img
Click to expand...
Click to collapse
- in twrp go to wipe -> advanced wipe and wipe all but internal storage and external storage
- install lineageos from twrp
You can update to last version, it does not breack your touchpad
I'll correct the scripts and add shasums and filename of CM-13.1 tonight

Did you succeed in downgrading? Any news on this?

Where do you experience trouble by following this:
mioux said:
[...]
I already have tried this without success :'(
Click to expand...
Click to collapse

Lurkos said:
Did you succeed in downgrading? Any news on this?
Click to expand...
Click to collapse
Yes, just look at the previous post
kabu83 said:
Where do you experience trouble by following this:
Click to expand...
Click to collapse
I have flashed the aboot, abootbak and boot, then tried to install lineageos from twrp, even after formating all partitions. Each time, it has rebooted to 7.1.1 with 7.1.1 recovery (twrp was not persistent).
I really had to fully reinstall CM13, and booting it, before updating to lineageos.

Hi all,
I've managed to successfully move from stock 7.1.2 (TOS212D) to LineageOS 14 (2017-09-11) without an intermediate downgrade to an old CM13 build
To do so, I rebooted the phone from stock 7.1.2 into the bootloader (adb reboot-bootloader)
I then booted into TWRP 3.1.1.0 (fastboot boot twrp-3.1.1-0-crackling.img)
I said no to the prompt for mounting /system read-write
I went to Wipe -> Advanced Wipe -> Ticked System and chose Repair or Change Filesystem.
I changed /system to EXT4
At this point, I then wiped all partitions except for my MicroSD card
Next, I flashed the latest LineageOS nightly (lineage-14.1-20170911-nightly-crackling-signed.zip), followed by OpenGApps (I chose 7.1, ARM64, pico)
At this point, if you reboot, it will loop back to the bootloader
As my final steps, I flashed Foxy Kernel 2.6 and Magisk 14, and rebooted
I believe the "magic" here is Magisk's patching of the boot loader to allow it to work, I believe that patches out some of the checks that are causing the phone to go back into the bootloader after installing LineageOS via TWRP over stock 7.1.X

anticoralian said:
Hi all,
I've managed to successfully move from stock 7.1.2 (TOS212D) to LineageOS 14 (2017-09-11) without an intermediate downgrade to an old CM13 build
To do so, I rebooted the phone from stock 7.1.2 into the bootloader (adb reboot-bootloader)
I then booted into TWRP 3.1.1.0 (fastboot boot twrp-3.1.1-0-crackling.img)
I said no to the prompt for mounting /system read-write
I went to Wipe -> Advanced Wipe -> Ticked System and chose Repair or Change Filesystem.
I changed /system to EXT4
At this point, I then wiped all partitions except for my MicroSD card
Next, I flashed the latest LineageOS nightly (lineage-14.1-20170911-nightly-crackling-signed.zip), followed by OpenGApps (I chose 7.1, ARM64, pico)
At this point, if you reboot, it will loop back to the bootloader
As my final steps, I flashed Foxy Kernel 2.6 and Magisk 14, and rebooted
I believe the "magic" here is Magisk's patching of the boot loader to allow it to work, I believe that patches out some of the checks that are causing the phone to go back into the bootloader after installing LineageOS via TWRP over stock 7.1.X
Click to expand...
Click to collapse
anyone confirm please if above still works on TOS373K? or was updating the phone first a mistake?

Smiff3 said:
anyone confirm please if above still works on TOS373K? or was updating the phone first a mistake?
Click to expand...
Click to collapse
Yes it does still work.
It's even easier nowadays if you just want Oreo.
Flash or boot TWRP, reformat system as ext4 (so you don't have the 0MB problem) and then you can flash the Oreo crDroid zip file and it will boot instantly:
https://forum.xda-developers.com/wileyfox-swift/development/rom-crdroid-android-4-0-beta-1-t3688253

schmatzler said:
Yes it does still work.
It's even easier nowadays if you just want Oreo.
Flash or boot TWRP, reformat system as ext4 (so you don't have the 0MB problem) and then you can flash the Oreo crDroid zip file and it will boot instantly:
https://forum.xda-developers.com/wileyfox-swift/development/rom-crdroid-android-4-0-beta-1-t3688253
Click to expand...
Click to collapse
thanks, i missed this reply before sorry.
not sure if i want oreo.. how is it on this phone? do you use Gravitybox.. i'll ask over there! thanks.

where can i get ADB USB DRIVERS for Windows 8.1 64bit for my WileyFox Swift 1 ?

How to go back to stock EMUI 5.0 after flashing TWRP/Custom roms (Guide)

Tested Devices:
Huawei GR5 BLL-L22.
Hello all,
I just wanted to put this guide out there for anyone struggling with restoring stock after flashing a custom nougat rom/TWRP. It took me several days to figure out this method, which has never failed to get me back to stock after screwing with my phone. You can also use this if you accidentally wiped data without removing your fingerprint.
Prerequisites:
- Stock firmware for your device. If you were using a BLL-L22, you need the firmware which matches your phone's model and it has only been tested with the same firmware version. You can use the Huawei firmware update finder to get it.
- You'll need HuaweiUpdateExtractor, find it here: https://forum.xda-developers.com/showthread.php?t=2433454 . All credit goes to the original creator of the tool, @worstenbrood .
- You also need a Micro SD card in your phone, along with a micro SD card reader/ SD card reader (if you have a micro SD to SD card converter).
- You need a functioning computer with ADB commands installed system wide.
Anyways, here goes:
1. Unzip the update zip file, and ensure you have the update.app .
2. Using Huawei Update Extractor, extract only the boot.img, recovery.img, system.img, and vendor.img from the update.app . Those are the only files you need.
3. Boot into TWRP and format data. then wipe ALL partitions.
HINT: If you had your Micro SD card merged with internal storage, MAKE SURE you partition your micro SD card in TWRP via the partition SD card functionality, using EXT3/4.
4. Reboot into TWRP, and flash the vendor.img using the install image functionality in TWRP.
5. Wipe all partitions and format data as well, and reboot into the bootloader (fastboot).
6. Flash the BOOT, RECOVERY, and SYSTEM images, in that order, using fastboot.
7. Reboot into fastboot, and remove your micro SD card.
8. Create a folder called dload in the folder where the update.app file is located, and place the update.app file inside the dload folder.
9. Copy the dload folder to the micro SD card you have connected to your PC via a card reader.
10. Place the micro SD card back inside the phone, and then hold power + volume up + volume down.
11. This should begin the flashing process, wait till it finishes flashing and reboots.
12. Boot into the stock recovery, and factory reset and also clear data.
13. Reboot.
14. PROFIT! You should be back on EMUI 5.0 with a fully functional phone once more.
If you have any questions at all, feel free to ask. Also, if the guide worked for you, please let me know and I'll compile a list of devices it has been tested on. Thanks guys!
DISCLAIMER: This method works flawlessly for me, and I have used it countless times with my Huawei GR5 2017 (BLL-L22). I am not responsible for any damage done to your phone, nor can I guarantee this will work on every single variant of the Honor 6X. Do to this at your own discretion.
Hit thanks if I helped.

Nice guide dude!

Awesome job bro keep it up

very nicely put together mate. nice work.

I backed up my stock emui 5 boot,system,vendor but after restoring backup I stucked on boot animation what i can do now
Sent from my HONOR-6X using Tapatalk

arshilhonor6x said:
I backed up my stock emui 5 boot,system,vendor but after restoring backup I stucked on boot animation what i can do now
Click to expand...
Click to collapse
This guide concerns rolling back via dload, not via TWRP. You'd be better off asking in the TWRP thread, or asking the OpenKirin team.

I haven’t follow this guide
I just used dload directly with the same firmware (i was only rooted)
Phone doesn’t enter fastboot using volume down and power
But i can go to fastboot using adb command (adb reboot bootloader)

I am actually exactly doing this right now. Honor was not able to help me, after the BETA UEMI 5.0 put the system into a non-upgradable state. I tried to upgrade it/rollback etc. but that made it worse.
So- my current problem is, I don't have TWRP (It is installed, but won't start because I am in the rollback-version of the firmware). what can I do to actually go on with it?
When you say: 3. Boot into TWRP and format data. then wipe ALL partitions.
So - I used the recovery from HAWEI to format the data partition (That should do it).
As I said - I only have fastboot at hand right now.
Also - the vendor image flash returns this:
Code:
$ fastboot flash vendor VENDOR.img
target reported max download size of 471859200 bytes
sending 'vendor' (419273 KB)...
OKAY [ 11.443s]
writing 'vendor'...
FAILED (remote: Command not allowed)
finished. total time: 11.448s
Any hints?

Use dload method to flash full latest firmware from firmware finder
Sent from my BLN-L22 using Tapatalk
---------- Post added at 09:33 AM ---------- Previous post was at 09:32 AM ----------
If u are unable to boot any recovery then go to service centre they will replace your mobo
Sent from my BLN-L22 using Tapatalk

arshilhonor6x said:
Use dload method to flash full latest firmware from firmware finder
Sent from my BLN-L22 using Tapatalk
---------- Post added at 09:33 AM ---------- Previous post was at 09:32 AM ----------
If u are unable to boot any recovery then go to service centre they will replace your mobo
Click to expand...
Click to collapse
No, it just won't allow me to write the vendor image.
I can go into the regular recovery etc., but I can' t do anything. Not even reset the system etc.

xda_jm said:
No, it just won't allow me to write the vendor image.
I can go into the regular recovery etc., but I can' t do anything. Not even reset the system etc.
Click to expand...
Click to collapse
Flash twrp using fastboot or use dload method
Sent from my BLN-L22 using Tapatalk

arshilhonor6x said:
Flash twrp using fastboot or use dload method
Click to expand...
Click to collapse
I have the BLN-L21C432 device (Berlin). You know which TWRP I have to flash?
Using the twrp from https://dl.twrp.me/berlin/ ->
twrp-3.1.1-0-berlin.img
That twrp won't show up. Probably because I don't have the right Vendor-image or so. No logs available etc. A real bummer ... :crying:
Stuck here:
Code:
You're device has been unlocked and can't be trusted.
To learn more, visit:
Blabla UYRL ...
Your device is booting now...
My assumption is that I have a mismatch between Vendor/recovery/system and boot.img files. Only, how do I look into these images (I could mount them as loopback device under linux? Linux only here, no windows). And I need to identify the verison of these images/build to flash the right versions for the dload to actually handle the right upgrade.

xda_jm said:
You know which TWRP I have to flash?
Using the twrp from https://dl.twrp.me/berlin/ ->
twrp-3.1.1-0-berlin.img
That twrp won't show up. Probably because I don't have the right Vendor-image or so. No logs available etc. A real bummer ... :crying:
Click to expand...
Click to collapse
That TWRP won't work, sadly even if hosted on official site it never worked. Grab the TWRP from here https://forum.xda-developers.com/honor-6x/development/twrp-t3583413 and flash via fastboot, it'll surely works. Vendor partition is separated from recovery one, so don't worry because even with an incorrect vendor.img it'll works anyway

RedSkull23 said:
That TWRP won't work, sadly even if hosted on official site it never worked. Grab the TWRP from here https://forum.xda-developers.com/honor-6x/development/twrp-t3583413 and flash via fastboot, it'll surely works. Vendor partition is separated from recovery one, so don't worry because even with an incorrect vendor.img it'll works anyway
Click to expand...
Click to collapse
Yeah. That was it.
So I am able to actually get into the TWRP recovery. Nice
Now - following your guide, I am unable to format data partition:
Code:
Full SELinux support is present
MTP Enabled
Formating data using mkfs.f2fs
mkfs.f2fs -t 0 /dev/block/mmcblk0p49 process ended with ERROR: 255
unabel to wipe data
unable to format to remove encryption
Any idea?
Shall I continue with the process?
I could change the filesystem of data to ext4 or so for testing?
UPDATE: Actually changing data to ext4, formating it as ext4 + rebooting into recovery and changing back to f2fs and formating f2fs worked in the end. What a crap.
I'll write down exactly what I do!
So - everything worked, except the factory reset showed a red exclamation mark.
It is now rebooting. And - no. I still have the BETA EMUI 5.0 showing, BuildNr. BLN-L21C900B300
Opening a new post for the next steps...

So - the cleaning has not worked.
After checking the imags in the update package, I noticed they are all different.
Why did the system-reset fail at all? Where does that come from?
Here the file-checksums:
Code:
$ cat BLN-L21C432B360-FullOTA-MF-PV/md5sums.txt
cbc1a5b85deb8caca46d7ed691f1d5d7 BOOT.img
78ccf0ff58d189284293e219f2aa8ce2 CACHE.img
eef4f7d2c4187b7cd195df1c1139950e CRC.img
f6594819938b923bccf075349b250347 CURVER.img
a181b39b6095f221ffb207268d10d540 DTS.img
aa3a0518794c16bb22849676c13ba55c EFI.img
0f1fcd32afb2db5183d86e527510c6b4 FASTBOOT.img
8379cfc96d5ddd57993da668c0e68da7 FW_HIFI.img
d60eb96f274cab285fe1bc5cb8ac874c FW_LPM3.img
afd9223813961adfbf71b0a51c310f66 MODEM_FW.img
176c0d4b0489a639f5bd371b5445a466 MODEMNVM_UPDATE.img
f07fcca53b5337e003e9894ec4b231e6 PRODUCT.img
40c8ce310fb8dde705c6b29ce316a215 RECOVERY2.img
a3883873ca0054ec12fb8d0a71835ca9 RECOVERY.img
cd22975bcc99a3436a74d6123e9c2796 SENSORHUB.img
2c4fab4df4b00c7dcb08fd8a47c0228f SHA256RSA.img
0565a9f075122ebf46c9f623eb6b22d2 TEEOS.img
e6a5b518daa00ea67a2a360408534dd9 TRUSTFIRMWARE.img
09e9dcef68ffddce4c1a41f1bbeae435 UPDATE.APP
19324f9cd1351119b4efdfa5c235200e VENDOR.img
9219d25ed7eb999fb08c03bf493929a3 VERLIST.img
83c5d8c7866c34f4ff901e17536ad3b4 XLOADER.img
Code:
$ cat RollBack_DE/md5sum.txt
6682ebf3c4c59b58e27cac42bc0a5760 BOOT.img
c9026aa21284a5c6575573bad6c67531 CACHE.img
643062216ba9a1a9c43091a56407b4e4 CRC.img
e665793d69c041c1a67ce25e342bb665 CURVER.img
862d05d2ac39567d48db9d4a996698e8 CUST.img
0c66cff221dd1adade7060d93f9f14db DTS.img
997a84cac4901d8d47a13d03a41645c1 EFI.img
cfdb3c574a4e22e6918021eb551af744 FASTBOOT.img
6534c81facf064c61fbe838a844bcf53 FW_HIFI.img
2c6cf6c896c17ed938563779d4bc015d FW_LPM3.img
330f6c5fe86c9c716ba675ade522a4c4 MODEM_FW.img
77ca34a576955b1aa7b09adcc43183aa MODEMNVM_UPDATE.img
bf696a2a9eb149bf3d409ab3fab8da1b RECOVERY2.img
ba1a5ef8d2d77dd03a4e5a3fb8be724b RECOVERY.img
e73ae0c33807474e61caaf2f5864bd93 SENSORHUB.img
53d8a3d3afcfd61a73d4446d37602249 SHA256RSA.img
713c288402f5d540efc722e442218fc0 SYSTEM.img
29a07ee1454ece337416b595101a016f TEEOS.img
15a226f7741aee2d026d760f755d6991 TRUSTFIRMWARE.img
b8100f45c08c2b54ec089e52d945fae9 VERLIST.img
7eb918861de29526259611fe95365e90 XLOADER.img
The rollback one is supposed to be an intermediate entry - C900B300 - which was supposed to make a rollback to EMUI 4.x (Tried that route, because I couldn't update any EMUI 5 releases).
Any idea what to do?
Reloaded twrp. When I chec the internal storqage, I see:
Cache
Data
System
Vendor
Product
Micro SDCard
USB OTG
Could it be the Product partition? What's inside?

xda_jm said:
Reloaded twrp. When I check the internal storage, I see:
Cache
Data
System
Vendor
Product
Micro SDCard
USB OTG
Could it be the Product partition? What's inside?
Click to expand...
Click to collapse
Actually, there are 48 Partitions *lol* Amazing.
And - to write an image manually using adb shell in twrp (That's where it works), the extracted images from UPDATE.APP need to be uncompressed first with:
Code:
/external_sd # simg2img PRODUCT.img PRODUCT.raw
/external_sd # dd if=PRODUCT.raw of=/dev/block/mmcblk0p48
393216+0 records in
393216+0 records out
201326592 bytes (192.0MB) copied, 7.405686 seconds, 25.9MB/s
Alas, the images are identical. So no changes.
Still debugging under the hood.
If anyone has an idea, let me know :}

So - last post from me probably. It has not worked.
My wife decided to stay with the beta EMUI 5.0.0.1 until a decent Lineage OS 14.1 version is there (Stable). I'll then put it on the Honor 6x.
It is amazing to see that actually 8GB of space from the disk is reserved for HUAWEI and GOOGLE tools, dispersed in 48 partitions, all to prevent people from using the device freely.
And I bet in future it will get worse and worse. Anyway - have learned a lot regarding the tools and how to use these, and what to take into account when doing things with phones.
I personally still use an old BQ E4.5 Aquaris Ubuntu phone which does most of what I need very nicely IO know why I hate Apple devices, and not so much Android devices.

in 5% i get failed
software install failed
my build is NRD90M test-keys
after write system recovery boot but faild in dload mode
bootloader is unlock

dark_boy99 said:
in 5% i get failed
software install failed
my build is NRD90M test-keys
after write system recovery boot but faild in dload mode
bootloader is unlock
Click to expand...
Click to collapse
I'll PM you the files. Certain update.app files fail to write, I don't know why. Give me a few hours to get the files to you.

Can someone please help me link to Stock firmware for my device? I honestly don't know what's my model number
What do I download?

[Recovery] [Unofficial] [MI 8] TWRP 3.3.1-1031

I'm not the Author, the author is wzsx150 from LR.TEAM
WZSX’s TWRP is well-known as the Chinese version of TWRP due to the language default is in Chinese. However, you can switch to English within TWRP user settings it's easily. switched. You can follow the instructions on this link to change the language to English: https://miui.blog/any-devices/lr-tea...inese-english/
Xiaomi 8's LR.Team customized version of Twrp
Automatically decrypts data, Includes root functionality, clear the power-on password, multi-function restart.
Disclaimer: I have installed it and for me it works fine. However, it is not guaranteed to work for you especially if you currently have encryption. Use at your own risk
If you need help flashing TWRP : Follow instructions here: https://miui.blog/mi-8/flash-twrp-root-mi-8/
Downloads
Latest
Version for Miui 11 Android 10/Q : https://www.androidfilehost.com/?fid...26312261636230
MD5: 2f5f2e7dc8f32b5a999828c9370b7de2
Version for Miui 10 or 11 Android 9/P : https://www.androidfilehost.com/?fid...26312261636232
MD5: 4681f9bd6367f934218da71fd528e39b
Old Versions
TWRP-3.2.3.1-FireDance-Edition (English) ( img)
TWRP 3.2.3-1208 (English) ( zip - img )
TWRP 3.2.3-1110 (English) ( zip - img )
TWRP 3.2.3-1110 ( zip - fastboot - img )
TWRP 3.2.3-0918 (zip - fastboot - img)
TWRP 3.2.3-0908 (zip - fastboot - img)
TWRP 3.2.2-0703 (zip - fastboot - img)
TWRP 3.2.2-0611 (zip - fastboot - img)
TWRP 3.2.2-0609 (zip - fastboot - img)
Changelog (Google Translated)
2018.11.10 update Contents:
1. Update the new rom that supports the official Android 9.
2. Update and optimize some functions
3. Increase the option to restart after the automatic upgrade is completed. In the twrp setting, the default is automatic restart. Uncheck the box and you can not restart. After the automatic upgrade, some operations are performed to prevent twrp from being overwritten, etc.
4. Update the built-in root to magisk 17.1, and fix the problem that the module cannot be brushed. Other features are also updated and optimized
5. After the new version of the system root, restarting the system requires manual installation of the magisk app, the official system problem, this can only be so
. 6. If Kami may need the root system or remove the dm check operation.
7. Prevent the functions covered by the official rec: root system, signature boot, remove dm check, cancel forced encryption, etc.
2018.9.8 update:
1. Support the official Android 9.0 system, including automatic decryption data
2. About data decryption, this may not be particularly stable now, sometimes need to reboot into the system and then restart Twrp can be decrypted.
If the new version of twrp is not supported, you can try to use the old version of
2018.8.6 update:
1. Update twrp 3.2.3 source code
2. Built-in magisk16.7, temporarily build this version first
3. Optimize data decryption problem, fix some problems
4 Support the new version of miui10 data decryption
5. Decrypt the plaintext display input password, easy to check whether the password input is correct
6. Update to try to repair the decryption data scheme, set the lock screen password to the machine, enter twrp need to enter the lock screen Password, otherwise you cannot temporarily decrypt data.
7. After brushing in twrp, the first time you enter twrp may restart once. This is normal. If you restart repeatedly, or you can't decrypt data, please give me feedback on Weibo.
8. Regarding data decryption, this may not be particularly stable now. Sometimes you need to reboot into the system and restart into twrp to decrypt.
If the new version of twrp is not supported, you can try to use the old version of

Thanks. I was already using the EN version you posted in the Dogsly(that may be wrong) thread.
Great job

arifqur said:
Thanks. I was already using the EN version you posted in the Dogsly(that may be wrong) thread.
Great job
Click to expand...
Click to collapse
@gulp79 is to thank for the English version

mikefallen said:
@gulp79 is to thank for the English version
Click to expand...
Click to collapse
if you want to add to op, this is the img version of TWRP-3.2.3-1110-XIAOMI8-EN-wzsx150
(with a minor modifications of prop.default, and also with chinese language, in previous version chinese was removed, btw english is set as default).
https://mega.nz/#!MwQn3IgR!UmuuBk1OScPrHi_HUO1zA_Da0df3nexfrrWGEBGjJPg

gulp79 said:
if you want to add to op, this is the img version of TWRP-3.2.3-1110-XIAOMI8-EN-wzsx150
(with a minor modifications of prop.default, and also with chinese language, in previous version chinese was removed, btw english is set as default).
https://mega.nz/fm/M4oDgLxA
Click to expand...
Click to collapse
that link doesn't seem to work for me, just redirects to the home page of mega

mikefallen said:
that link doesn't seem to work for me, just redirects to the home page of mega
Click to expand...
Click to collapse
try this
https://mega.nz/#!MwQn3IgR!UmuuBk1OScPrHi_HUO1zA_Da0df3nexfrrWGEBGjJPg

gulp79 said:
try this
https://mega.nz/#!MwQn3IgR!UmuuBk1OScPrHi_HUO1zA_Da0df3nexfrrWGEBGjJPg
Click to expand...
Click to collapse
yup added to OP Thanks!

Help!!!
It works for mi 8 miui 10.0.3.0 global?, i cant figure out how install the eu rom, in the twrp show me only folders encrypted :C, somebody knows how ?

Looks like you will have to format Dara partition in recovery by typing yes

So, boot the img and then flash the zip for TWRP to stick permanently?

Can't use gapps Aroma installer using twrp .. any ideas ?

could this twrp support amora installer
could this twrp support amora installer?

On my MI 8, i restored a previous backup made with twrp, now the device does not accept my 4-digit password so I can't login to my phone!
please help!

cyaneo said:
On my MI 8, i restored a previous backup made with twrp, now the device does not accept my 4-digit password so I can't login to my phone!
please help!
Click to expand...
Click to collapse
in twrp go to file manager, data, system and delete locksettings file. reboot and you're good to go again

Hi!
Help me, please!
I can't exit from recovery mode on MI8

cyaneo said:
On my MI 8, i restored a previous backup made with twrp, now the device does not accept my 4-digit password so I can't login to my phone!
please help!
Click to expand...
Click to collapse
Go into recovery mode, format internal memory.
---------- Post added at 06:24 AM ---------- Previous post was at 06:22 AM ----------
Coolesha said:
Hi!
Help me, please!
I can't exit from recovery mode on MI8
Click to expand...
Click to collapse
You need to format your device.

bahuy2003 said:
Go into recovery mode, format internal memory.
Click to expand...
Click to collapse
ok, but doesn't this delete all my settings & personal files (aka reset to default)?
Thank you!

cyaneo said:
ok, but doesn't this delete all my settings & personal files (aka reset to default)?
Thank you!
Click to expand...
Click to collapse
If you device can't reboot, you can flash eu or global rom, format again and reboot system.

bahuy2003 said:
If you device can't reboot, you can flash eu or global rom, format again and reboot system.
Click to expand...
Click to collapse
Hu? never wrote it doesn't reboot etc. - It reboots, everything seems to be OK - I "just" can't login after restore a backup....
so, again: does "format internal memory" reset my phone, delete setting or personal files? If so, how does this solve the problem? After a fresh EU ROM install, everything works fine like a new install does.

cyaneo said:
Hu? never wrote it doesn't reboot etc. - It reboots, everything seems to be OK - I "just" can't login after restore a backup....
so, again: does "format internal memory" reset my phone, delete setting or personal files? If so, how does this solve the problem? After a fresh EU ROM install, everything works fine like a new install does.
Click to expand...
Click to collapse
Flash this zip in TWRP and your login password would be deleted, which by the way gets jumbled up after a restore.

Problems enabling encryption on Xiaomi.EU ROM

During the last days I tried to enable encryption on my Mi Mix 2 without success.
I tried the following:
- boot to TWRP
- format data
- install latest Xiaomi.EU ROM
- flash forceencrypt.zip
- reboot to system
Result: No encryption. Enabling encryption in Miui options results in unbootable phone.
Then I tried to edit the fstab.qcom file under /system/vendor/etc. Here I failed, because I was not able to replace the original file with the TWRP file manager. Somehow, the system partition stayed read only.
Can someone here lend me a hand and tell me what I did wrong?

Gandhi70 said:
During the last days I tried to enable encryption on my Mi Mix 2 without success.
I tried the following:
- boot to TWRP
- format data
- install latest Xiaomi.EU ROM
- flash forceencrypt.zip
- reboot to system
Result: No encryption. Enabling encryption in Miui options results in unbootable phone.
Then I tried to edit the fstab.qcom file under /system/vendor/etc. Here I failed, because I was not able to replace the original file with the TWRP file manager. Somehow, the system partition stayed read only.
Can someone here lend me a hand and tell me what I did wrong?
Click to expand...
Click to collapse
MAY be You only did wrong becauser FCencrypt.zip you attached is , as what I can see, empty. Miss your modified Fstab file to be inside it (etc folder).
Without using the zip, as for test, in TWRP you drop your modified Fstab into sdcard folder and copy it to vendor/etc folder . Very easy manipulation.
Then reboot and that should perfectly give encryption with your own PW pin.
I did it and worked for me. Noob..
Now I make use of the zip tool after every rom update because system is replaced hence fstab reset-ted.

Got it working now! Mounting Vendor did the trick!

Twrp can't decrypt data

Hey everyone,
After updating to the last stable version of xiaomi.eu I wanted to reflash magisk but when I boot into recovery I'm not asked for any password yet my data is still encrypted.
I tried running #twrp decrypt password in the terminal but it fails.
Has anyone here encounter the same problem?

Tom403 said:
Hey everyone,
After updating to the last stable version of xiaomi.eu I wanted to reflash magisk but when I boot into recovery I'm not asked for any password yet my data is still encrypted.
I tried running #twrp decrypt password in the terminal but it fails.
Has anyone here encounter the same problem?
Click to expand...
Click to collapse
Why don't you install Magisk by patching Boot image from Magisk Manager and flashing the patched image from Fastboot.
Just for Magisk, you don't need (to bother with) TWRP

zgfg said:
Why don't you install Magisk by patching Boot image from Magisk Manager and flashing the patched image from Fastboot.
Just for Magisk, you don't need (to bother with) TWRP
Click to expand...
Click to collapse
Won't that replace my recovery with the stock one?
I'd like to keep twrp

Tom403 said:
Won't that replace my recovery with the stock one?
I'd like to keep twrp
Click to expand...
Click to collapse
You flash the patched Boot image from Fastboot, so Recovery (and other partitions) remains the one you have currently installed.
Also, just patching in Magisk Manager does not affect either Recovery, Boot (Vendor, etc)
When patching Boot image by Magisk Manager make sure you take the options:
-Preserve ADM dm-verity: YES
-Preserve force encryption: YES
-Recovery mode: NO

zgfg said:
You flash the patched Boot image from Fastboot, so Recovery (and other partitions) remains the one you have currently installed.
Also, just patching in Magisk Manager does not affect either Recovery, Boot (Vendor, etc)
When patching Boot image by Magisk Manager make sure you take the options:
-Preserve ADM dm-verity: YES
-Preserve force encryption: YES
-Recovery mode: NO
Click to expand...
Click to collapse
Ok, I'll do that then
Thanks for the help ?

Tom403 said:
Ok, I'll do that then
Thanks for the help ?
Click to expand...
Click to collapse
For the Boot image you have to patch boot.img extracted from zip/recovery package of your stock ROM
But you can also backup Boot partition by TWRP and then let Magisk Manager patch the backup boot.emmc.win file

Is it safe to assume that Tom403 didn't find any love at the end of the encrypted rainblow? I JUST WANT to verify, This IS the same situation that used to be remedied by deleting locksettings.db and a files with .key extension?? No such luck for anymore, wow, what a setup for future-screwing your users Google!! Dicks

goo. said:
Is it safe to assume that Tom403 didn't find any love at the end of the encrypted rainblow? I JUST WANT to verify, This IS the same situation that used to be remedied by deleting locksettings.db and a files with .key extension?? No such luck for anymore, wow, what a setup for future-screwing your users Google!! Dicks
Click to expand...
Click to collapse
Okay, I may have found a lightbulb somewhere in the tunnel that may be whats required for others as well to unencrypt when deleting .keyfiles is no longer an option having version greater than PIE. It's in the form of in a recovery log from a recent, perhaps backup attempt, that states the version of Orange Fox recovery I had (11.0) and also says fbe encryption in use and info like the following that looks very promising... I'd really appreciate if someone that knows more than me to let me know if I'm on the right path and guide me in if so... heres part of the LOG that gives me hope --
ased Encryption is present
e4crypt_initialize_global_de
Determining wrapped-key support for /data
fbe.data.wrappedkey = false
calling retrieveAndInstallKey
Key exists, using: /data/unencrypted/key
Using SoftwareWrappedKeymaster1Device from Google for encryption. Security level: TRUSTED_ENVIRONMENT, HAL: [email protected]::IKeymasterDevice/default
Determining wrapped-key support for /data
fbe.data.wrappedkey = false
Added key 90117251 (ext4:72f7ca8ad834ad5d) to keyring 322439018 in process 546
Added key 866183642 (f2fs:72f7ca8ad834ad5d) to keyring 322439018 in process 546
Added key 321684719 (fscrypt:72f7ca8ad834ad5d) to keyring 322439018 in process 546
contents mode 'aes-256-xts' filenames 'aes-256-heh'
Wrote system DE key reference to:/data/unencrypted/ref
e4crypt_ini
Thanks in advance for any help with this

Tom403 said:
Hey everyone,
After updating to the last stable version of xiaomi.eu I wanted to reflash magisk but when I boot into recovery I'm not asked for any password yet my data is still encrypted.
I tried running #twrp decrypt password in the terminal but it fails.
Has anyone here encounter the same problem?
Click to expand...
Click to collapse
thanks for the terminal command