Database Develop

Tried installing LOS, couldn't do it and now i have permanent dm-verity error

Here's an attempted TLR of what has happened
Tried installing LineageOS. Got Error 7. Tried a bunch of things to make it work like editing the updater-script and things like that but it didn't work.
Then I simply wanted my phone to work again. Installed Clean Stock ROM + Stock Recovery straight out of OnePlus webpage. Now I have permanent dm-verity error (tried going back to 4.0.2, disabling dm-verity via fastboot commands and restoring 4.0.3) and still appears.
So yeah, basically that.
I messed up like a month ago too, bricked the OP3T and managed to revive it with a chinese program.
Any ideas on why I can never manage to install LineageOS?
EDIT: After the last factory reset, the phone wouldn't find any wifi network. After an hour or so, it found my wifi and got a 92mb update that fixed the dm-verity error

What firmware are you running and what's your Android version? If you're running 7.1.1 on 4.1.0 you should be good to go just by flashing all the latest LOS files

sakumaxp said:
What firmware are you running and what's your Android version? If you're running 7.1.1 on 4.1.0 you should be good to go just by flashing all the latest LOS files
Click to expand...
Click to collapse
I just received the 4.1.0, going to try again tonight. Hope it works

I have the 8.1 soak test, but want a custom ROM instead...

So here's the deal, I had lost my LTE awhile back with something and saw the opportunity to fix it by taking the 8.1 soak OTA. Works wonderfully. But I do want to possibly go back a custom ROM, and have tried a few already that all work fine, except the lack of the fingerprint scanner working properly. This isn't really a big deal for now, but I'm starting a convo just to brainstorm.
Any ideas as to what's causing this, or possible solutions?

You may have to wait till the official hits the streets and the devs here tear it apart to bring that sensor up to date with the Bootloader I'm guessing. But hell, if you don't mind it. Dig in playa.
Sent from my Moto G (5S) Plus using Tapatalk

treyweez11 said:
You may have to wait till the official hits the streets and the devs here tear it apart to bring that sensor up to date with the Bootloader I'm guessing. But hell, if you don't mind it. Dig in playa.
Click to expand...
Click to collapse
That's kinda what I'm thinking, which again, I'm not worried or in a hurry, just curious.

Only whit a custom kernel
mrchman said:
That's kinda what I'm thinking, which again, I'm not worried or in a hurry, just curious.
Click to expand...
Click to collapse
In the stock version, it will only work with a custom kernel, just like in 7.1, it only works with custom kernel

guineks said:
In the stock version, it will only work with a custom kernel, just like in 7.1, it only works with custom kernel
Click to expand...
Click to collapse
Would you think any of the current custom kernels here would do the job with a custom ROM?

mrchman said:
Would you think any of the current custom kernels here would do the job with a custom ROM?
Click to expand...
Click to collapse
Using custom roms, all of which I tested, all worked using the xposed framework material, and using the magisk module corresponding to the version of android used (8.0 - 8.1)
As for stock rom 8.1, I do not know compatible kernel, for version 7.1, there is custom kernel available, and you should proceed xposed in the same way.
sorry for my english from google translate

1>Take EFS backup from oreo soak test {with 4G and VOLTE working}
2>Flash Stock NPSS26.116-61-8 in full
3>Install TWRP and custom ROM
4>Restore EFS from oreo backup
This is working perfectly for me; fingerprint (incl gestures), VOLTE both work; I'm using AOSP Extended ROM

guineks said:
Using custom roms, all of which I tested, all worked using the xposed framework material, and using the magisk module corresponding to the version of android used (8.0 - 8.1)
As for stock rom 8.1, I do not know compatible kernel, for version 7.1, there is custom kernel available, and you should proceed xposed in the same way.
sorry for my english from google translate
Click to expand...
Click to collapse
Yes, this is what I thought, but I tried several custom ROMs hoping for one to work like you say, and none did.

febin92 said:
1>Take EFS backup from oreo soak test {with 4G and VOLTE working}
2>Flash Stock NPSS26.116-61-8 in full
3>Install TWRP and custom ROM
4>Restore EFS from oreo backup
This is working perfectly for me; fingerprint (incl gestures), VOLTE both work; I'm using AOSP Extended ROM
Click to expand...
Click to collapse
Perfect! I do have a question, how can I move my twrp backup to my desktop or so, and move it back to the phone after the firmware flash so I can restore my efs?
I tried something like that before and my backup was corrupted or unrecognizable.

mrchman said:
Perfect! I do have a question, how can I move my twrp backup to my desktop or so, and move it back to the phone after the firmware flash so I can restore my efs?
I tried something like that before and my backup was corrupted or unrecognizable.
Click to expand...
Click to collapse
Just copy the entire TWRP folder from sdcard/internal memory

febin92 said:
1>Take EFS backup from oreo soak test {with 4G and VOLTE working}
2>Flash Stock NPSS26.116-61-8 in full
3>Install TWRP and custom ROM
4>Restore EFS from oreo backup
This is working perfectly for me; fingerprint (incl gestures), VOLTE both work; I'm using AOSP Extended ROM
Click to expand...
Click to collapse
It's safe to flash nougat bootloader image to oreo soak 8.1 bootloader (downgrade)?

arni664 said:
It's safe to flash nougat bootloader image to oreo soak 8.1 bootloader (downgrade)?
Click to expand...
Click to collapse
I was wondering this same thing, it doesn't give some kind of error message when downgrading?

mrchman said:
I was wondering this same thing, it doesn't give some kind of error message when downgrading?
Click to expand...
Click to collapse
Hmm, flashing the April 2018 7.1.1 firmware should give a security version downgrade if you've downgraded to Nougat from Oreo (though like yourself, I await some confirmation).
If you do see that error, I would advise against flashing or installing the June 2018 7.1.1 security update OTA, I do not know if flashing the 7.1.1 June 2018 OTA onto a device previously updated with the Oreo soak test would result in a hard brick (as the June 2018 OTA may or may not corrupt the Oreo bootloader). Be careful.

So if I were to attempt to flash it via fastboot, it would give me an error and ask for confirmation before proceeding, correct?
And if I see said error, stay away.

mrchman said:
So if I were to attempt to flash it via fastboot, it would give me an error and ask for confirmation before proceeding, correct?
And if I see said error, stay away.
Click to expand...
Click to collapse
If you flash a stock firmware, you'll see the error, but it won't ask you for confirmation. It'll just display 'security version downgrade' if your bootloader is actually newer than the firmware you're flashing. Thus, fastboot should block you from downgrading the bootloader and GPT, so you'd likely still have the Oreo bootloader on your device (unless something's changed with Motorola's enforcement of bootloader versions).
The only time you may be okay is if the subsequent OTA is the same as the newest firmware that you had on your device. E.g. if you applied the soak test OTA (OPS28.49-2), then downgraded to the April 2018 firmware, if the next OTA you use is OPS28.49-2 or a newer Oreo OTA (as you have an Oreo bootloader), then you should be okay. If you however get a Nougat OTA (like the June 2018 security patch), I'd honestly stay away unless you want to risk it. Again, I do not know if the June 2018 7.1.1 would brick your device, but you've got no way of recovering your device besides paying for an expensive motherboard replacement. If you're on the soak test, try to stay on the soak test please.

mrchman said:
Yes, this is what I thought, but I tried several custom ROMs hoping for one to work like you say, and none did.
Click to expand...
Click to collapse
After installation of the xposed framework using magisk, it may be necessary to wipe cache dalvik, and cache

guineks said:
After installation of the xposed framework using magisk, it may be necessary to wipe cache dalvik, and cache
Click to expand...
Click to collapse
I don't use xposed. I use magisk only, and I wipe cache/dalvik, and data every time I flash something.

febin92 said:
1>Take EFS backup from oreo soak test {with 4G and VOLTE working}
2>Flash Stock NPSS26.116-61-8 in full
3>Install TWRP and custom ROM
4>Restore EFS from oreo backup
This is working perfectly for me; fingerprint (incl gestures), VOLTE both work; I'm using AOSP Extended ROM
Click to expand...
Click to collapse
Question. I've restored efs before after downgrading and it's worked. I would flash the custom rom of choice and if finger print and volte didn't work I would go back and restore efs from soaktest. I'm returning from soaktest again and that method doesn't seem to work. My question is, do you restore efs before you flash custom rom or do you wait till after the rom has flashed and reboot to check first?
Sent from my XT1806 using Tapatalk
NVM clearly I can't read cause you put it all there. Thanks

Data security and phone encryption. Miui custom rom

My new MI8 SE is not my daily use, so I got time to check all available MIUI custom rom (eu,Globe,MiRum,Miuipro,Ros,MS and Masik 1.8.)
At this point no problem, they install very well and they answer my needs.
BUT:
AS EVERYBODY should know that it is very easy to delete the central Password and finger print by the mean of our sophisticated tool (I mean TWRP).
In order to be safe '(without turning back to stock rom) I tried to encrypt the phone WITHOUT success...
Process failed every time with different results (full reset, logo loop for hours, partial encrypt for data only). But was always the point that minimum security can't be reached!
Question:
-Can you well sleep If you mind that you are having all your precious data available in the wind as soon your phone is lost or stolen or even worst let in some bad friends hands...? It takes 1 mn to delete the file without any computer.
I see a partial solution by installing afterward a stock recovery that does allow to trick the system file.
(If somebody has it, I am available to test this option, but don't tell me to flash a stock rom as solution!!)
Your comments/solutions are welcome.

You can have encryption with custom ROM, if the corresponding kernel enabled built-in force encryption.
I'm currently running phh treble 9.0 encrypted, with stock kernel patched by this script:
https://forum.xda-developers.com/an...rceencrypt-t3817389/post77572812#post77572812

NexusRunner said:
You can have encryption with custom ROM, if the corresponding kernel enabled built-in force encryption.
I'm currently running phh treble 9.0 encrypted, with stock kernel patched by this script:
https://forum.xda-developers.com/an...rceencrypt-t3817389/post77572812#post77572812
Click to expand...
Click to collapse
Thanks for taking care of my post.
This is old now.
I've investigated a bit more and found ways to get MIUI custom ROM encrypted. (for now I want to stay with MIUI stuff!)
I know that almost all AOSP like rom may well encrypt from first install.
My aim was and is still to warn people that without encrypt their phone are open like a lost book.
Thanks for the very interesting and documented thread (link) you directed me to.

lolo9393 said:
Thanks for taking care of my post.
This is old now.
I've investigated a bit more and found ways to get MIUI custom ROM encrypted. (for now I want to stay with MIUI stuff!)
I know that almost all AOSP like rom may well encrypt from first install.
My aim was and is still to warn people that without encrypt their phone are open like a lost book.
Thanks for the very interesting and documented thread (link) you directed me to.
Click to expand...
Click to collapse
If you don't mind could you post a detailed guide to flash our Mi 8 Se. I tried once and got mine hard bricked and i'm scared to try again.
Our forum lacks detailed instruction and it's all hit and trial. And since you have had your hands dirty, could you do that?

me_death said:
If you don't mind could you post a detailed guide to flash our Mi 8 Se. I tried once and got mine hard bricked and i'm scared to try again.
Our forum lacks detailed instruction and it's all hit and trial. And since you have had your hands dirty, could you do that?
Click to expand...
Click to collapse
The process do not differ from other XIAOMI phone and is available at main forums.
Exemple:
https://xiaomi.eu/community/threads/9-1-24-26.48919/
or here
http://en.miui.com/search.php?mod=f...hsubmit=yes&kw=how+to+flash+custom+rom&month=
If you have specific issue with flashing process you are allowed to post in order to get support.

lolo9393 said:
The process do not differ from other XIAOMI phone and is available at main forums.
Exemple:
https://xiaomi.eu/community/threads/9-1-24-26.48919/
or here
http://en.miui.com/search.php?mod=f...hsubmit=yes&kw=how+to+flash+custom+rom&month=
If you have specific issue with flashing process you are allowed to post in order to get support.
Click to expand...
Click to collapse
Thanks Could you just point me the recovery you're using? that would be great, like exact recovery. I backed up my rom and then while restoring my device, it got hard bricked. :silly:

me_death said:
Thanks Could you just point me the recovery you're using? that would be great, like exact recovery. I backed up my rom and then while restoring my device, it got hard bricked. :silly:
Click to expand...
Click to collapse
Available MI8 SE are located here:
https://drive.google.com/drive/folders/1IeCtb6vRO4CRe76s0BD_5TQiSnymPBTT
Just take care to flash latest 1227 version after EU rom older than 8.12.20 date.
In my view it's a mistake to backup anything with TWRP because as of today nothing is stable. Better to stay with MIUI backup and computer duplication.

lolo9393 said:
Available MI8 SE are located here:
https://drive.google.com/drive/folders/1IeCtb6vRO4CRe76s0BD_5TQiSnymPBTT
Just take care to flash latest 1227 version after EU rom older than 8.12.20 date.
In my view it's a mistake to backup anything with TWRP because as of today nothing is stable. Better to stay with MIUI backup and computer duplication.
Click to expand...
Click to collapse
Thank you so much for all the help.

lolo9393 said:
Available MI8 SE are located here:
https://drive.google.com/drive/folders/1IeCtb6vRO4CRe76s0BD_5TQiSnymPBTT
Just take care to flash latest 1227 version after EU rom older than 8.12.20 date.
In my view it's a mistake to backup anything with TWRP because as of today nothing is stable. Better to stay with MIUI backup and computer duplication.
Click to expand...
Click to collapse
I tried EU rom again. This time i flashed TWRP 1227, then cleared my data, flashed rom and then flashed TWRP again and still i'm stuck at fastboot. I got my phone up running using MiFlash but i can't seem to run EU rom :crying:

me_death said:
I tried EU rom again. This time i flashed TWRP 1227, then cleared my data, flashed rom and then flashed TWRP again and still i'm stuck at fastboot. I got my phone up running using MiFlash but i can't seem to run EU rom :crying:
Click to expand...
Click to collapse
What EU rom did you install?
This doesn't work with STABLE version. Only DEV EU rom
like latest 9.2.24/25

me_death said:
I tried EU rom again. This time i flashed TWRP 1227, then cleared my data, flashed rom and then flashed TWRP again and still i'm stuck at fastboot. I got my phone up running using MiFlash but i can't seem to run EU rom :crying:
Click to expand...
Click to collapse
9. What EU rom did you install?
This doesn't work with STABLE version. Only DEV EU rom
like latest 9.2.14

lolo9393 said:
What EU rom did you install?
This doesn't work with STABLE version. Only DEV EU rom
like latest 9.2.24/25
Click to expand...
Click to collapse
I tried installing
https://xiaomi.eu/community/threads/9-2-14-15.49206/
Version: WEEKLY 9.2.15

me_death said:
I tried installing
https://xiaomi.eu/community/threads/9-2-14-15.49206/
Version: WEEKLY 9.2.15
Click to expand...
Click to collapse
That's OK!
you flash 9.2.15 with TWRP 1102 or 1217.
YOU DON't REBOOT THE ROM.
you flash twrp 1227 and THEN you reboot the rom and wait install finish, take some time be partient.
simple!

lolo9393 said:
That's OK!
you flash 9.2.15 with TWRP 1102 or 1217.
YOU DON't REBOOT THE ROM.
you flash twrp 1227 and THEN you reboot the rom and wait install finish, take some time be partient.
simple!
Click to expand...
Click to collapse
Finally i got it working following your instructions on the MIUI EU forum. Thanks a bunch. :victory: :highfive:
To others for reference. Following are the procedures that i followed to boot up Miui Eu :silly:
- Flash official 8.12.13 (Dev Fastboot Rom) through MiFlash.
- Flash TWRP 1102
- Clean Data
- Push/ Copy and Flash 8.12.20( EU Rom), it booted up finally without redirecting to Fastboot.
- Update 8.12.20 to latest available from system updater.
- Now there won't be any recovery or we aren't able to enter into available recovery even though the system boots.
- Flash TWRP 1227.

Xiaomi Mi Mix 2 Pie Update released

Finally. Open Beta, but running without Problems here! :good:
https://xiaomi.eu/community/threads/9-5-9.50450/

ARB
is possible install aosp Roms ?? no brik

miui pie?

adliradzif said:
miui pie?
Click to expand...
Click to collapse
Yes

Bluezzy said:
Yes
Click to expand...
Click to collapse
alright.I gonna test..thanks for the reply.

Just to let u know guys,Anti rollback system is enabled on pie ,so once u flash it,u cant downgrade to oreo 8.x

I got bootloop.I using custom ROM pie before and flash using twrp official

adliradzif said:
I got bootloop.I using custom ROM pie before and flash using twrp official
Click to expand...
Click to collapse
Its bootloop because your device is encrypted and cant boot,look in other threads there is a decrytption script and step by step how to flash this pie

I can't recommend a flash without Data formatting since it is a Major Android Update. If You want to face a bugfree and clean Device start from scratch by backing Up Your Internal Storage, flash Orange Fox and do a complete wipe followed by "format Data" and the flashing of the System. Every System has Problems with Updates, that will never Change but A/B Treble was a step in the right direction since its almost failsafe on Updates. We don't have A/B Support on the Mi Mix 2 so it will be the best to do clean Updates before You will loose Your Personal Data...
Flashing Scripts to avoid encryption is Just a dirty workaround btw. If You want a save and secure Device just do what i wrote before... Otherwise can everyone steal Your Device and get Access to EVERYTHING.

I've written a short tutorial how to use encrypted data on latest Mi MIX2 MIUI Android 9 Pie ROM
read here: https://forum.xda-developers.com/mi-mix-2/how-to/xiaomi-mi-mix2-encryption-android-9-pie-t3929322

Can I flash with miui recovery?

Which is Miui TWRP? Teamwin or Orangefox. I suggest the latter
Tapatalkkal Mi MIX 2

As soon as I install latest xiaomi eu pie and magisk 19.1 I get a message that find device storage corrupted your device is unsafe now. Everything except adding/removing fingerprints seems to work correctly. Then even if I clean data I still get this message. the only way to fix it is clean install latest Oreo (9.4.25). Then I can update to pie and it is ok until magisk. Anyone has experienced this behavior or can help?

cineq said:
As soon as I install latest xiaomi eu pie and magisk 19.1 I get a message that find device storage corrupted your device is unsafe now. Everything except adding/removing fingerprints seems to work correctly. Then even if I clean data I still get this message. the only way to fix it is clean install latest Oreo (9.4.25). Then I can update to pie and it is ok until magisk. Anyone has experienced this behavior or can help?
Click to expand...
Click to collapse
Same here, think/hope 18.1 will do the trick...
BR

Dirty flash with Xiaomi.eu Rom works great

Clean installed xiaomi.eu 9.5.9 Pie with magisk 19.1. It seems bluetooth paired devices are lost after each restart. Anyone experienced the same problem?
EDIT:
I've just pairted two bluetooth devices and changed their names. After two phone restarts both devices remain, so something helped.

So Im on global stable,only thing i need to do before flashing this pie is wiping internal strogae + data? I got so confused these days

Bluezzy said:
So Im on global stable,only thing i need to do before flashing this pie is wiping internal strogae + data? I got so confused these days
Click to expand...
Click to collapse
That's the failsafe way I'd always say: Better save Your Data BEFORE loosing them on a bricked or locked Device :silly:

Miustone said:
That's the failsafe way I'd always say: Better save Your Data BEFORE loosing them on a bricked or locked Device :silly:
Click to expand...
Click to collapse
So whats the right way to flash it since my phone is encrypted... flashing those scripts right?

Miustone said:
Same here, think/hope 18.1 will do the trick...
BR
Click to expand...
Click to collapse
Write an answer when/if you trie.

(LineageOS 18.1) Mobile data no longer working

I flashed LineageOS 18.1 with no GApps (I'm using microG), and I haven't been able to use mobile data at all. No additional mods installed, and WiFi/Bluetooth work properly. Anything that I missed when flashing the ROM, or are there any other fixes I could try? Thanks.

KingSpammerNerd said:
I flashed LineageOS 18.1 with no GApps (I'm using microG), and I haven't been able to use mobile data at all. No additional mods installed, and WiFi/Bluetooth work properly. Anything that I missed when flashing the ROM, or are there any other fixes I could try? Thanks.
Click to expand...
Click to collapse
May be try downgrading the updated version to an lower version i.e "lineage-18.1-20210417-nightly-chef " or even lower , since newer versions sometimes come with an unexpected bug. The Android 11 ie LOS 18.1 has been around for around a month , so I expect them to have these smaller bugs, try contacting the Dev may be ?
Also did you flash your device as mentioned in the LOS webpage ? Reddit seems to recommend Mindthegapps (I might be wrong on this one) , and did you clean flash the device ?

I formatted data, cache and system, then clean flashed using TWRP. Strangely, I've also tried LOS 17.1 and had the exact same problem. Maybe I should clean flash again, but I want to try other solutions first.

KingSpammerNerd said:
I formatted data, cache and system, then clean flashed using TWRP. Strangely, I've also tried LOS 17.1 and had the exact same problem. Maybe I should clean flash again, but I want to try other solutions first.
Click to expand...
Click to collapse
Have you tried may be following the exact instructions on the LOS website ? Using LOS recovery and using the right Gapps ? clean install ? Maybe try installing LOS18.1 without Gapps.
If the issue persists try contacting the developer ,he usually responds.
Im on LOS17.1 February patch , no issue so far.

redbuck007 said:
Have you tried may be following the exact instructions on the LOS website ? Using LOS recovery and using the right Gapps ? clean install ? Maybe try installing LOS18.1 without Gapps.
If the issue persists try contacting the developer ,he usually responds.
Im on LOS17.1 February patch , no issue so far.
Click to expand...
Click to collapse
I'm currently using LOS 18.1 without GApps. LOS recovery hangs when I try to flash it, so I had to use TWRP. Followed the exact instructions, and everything besides data (calls, SMS) works without an issue. Dialling *#*#4636#*#* and checking IMS status gives me "IMS registration: Not registered", and my current "preferred network type" is LTE/WCDMA.
Maybe I should contact the devs, do they have an account on XDA?

Did you ever find a solution for this?