Related
Someone is testing LOS 16 on yours Shamu Phone? 15.1 Nightly is a stable build, is it 16 Nightly Build the same?
How should people know this? Lineage-16.0 is out since a few hours.
but since we have this https://github.com/LineageOS/charter/blob/master/device-support-requirements.md you can be shure of a certain quality
Any guidance on moving from 15.1 to 16.0? I assume a clean install is probably a good idea?
Thanks!
-C
First build isn't working properly for me. After flashing it gives me the "Decryption unsuccessful" message. Don't have encryption enabled, and my phone is formatted to ext4. Tried wiping multiple times in different ways. Had been running LOS 15.1 for months with no problems. Clean flash.
Update: Just to see, reinstalled LOS 15 and encrypted my device. Decryption still fails after flashing LOS 16 and trying to boot.
Quade321 said:
First build isn't working properly for me. After flashing it gives me the "Decryption unsuccessful" message. Don't have encryption enabled, and my phone is formatted to ext4. Tried wiping multiple times in different ways. Had been running LOS 15.1 for months with no problems. Clean flash.
Update: Just to see, reinstalled LOS 15 and encrypted my device. Decryption still fails after flashing LOS 16 and trying to boot.
Click to expand...
Click to collapse
I was thinking about flashing back to the last official google release (N6F27M), and then up to 16.0, but was going to wait to see if there was any official recommendation. Kind of a nuke the "site" from orbit approach - "it's the only way to be sure..."
-C
cdaly1970 said:
I was thinking about flashing back to the last official google release (N6F27M), and then up to 16.0, but was going to wait to see if there was any official recommendation. Kind of a nuke the "site" from orbit approach - "it's the only way to be sure..."
-C
Click to expand...
Click to collapse
Yeah, I was thinking about doing that, but just didn't feel like it, and can't imagine how it'd help. Probably just wait a week (probably more) or so for the builds to settle down. They're always pretty unstable at first anyway.
Quade321 said:
First build isn't working properly for me. After flashing it gives me the "Decryption unsuccessful" message. Don't have encryption enabled, and my phone is formatted to ext4. Tried wiping multiple times in different ways. Had been running LOS 15.1 for months with no problems. Clean flash.
Update: Just to see, reinstalled LOS 15 and encrypted my device. Decryption still fails after flashing LOS 16 and trying to boot.
Click to expand...
Click to collapse
Did you follow the instructions on the LOS site? I upgraded from LOS 15.1 to LOS 16 without issues. I wasn't encrypted on LOS 15.1 and still won't because right now that is a headache with TWRP being unable to decrypt.
https://lineageos.org/Changelog-22/
BootloopedMillennials said:
Did you follow the instructions on the LOS site? I upgraded from LOS 15.1 to LOS 16 without issues. I wasn't encrypted on LOS 15.1 and still won't because right now that is a headache with TWRP being unable to decrypt.
https://lineageos.org/Changelog-22/
Click to expand...
Click to collapse
I don't see anything that isn't normal in the instructions. Wipe, flash, done. And also don't know what you mean about TWRP being unable to decrypt. Newest TWRP (been for like 2 years) 3.2.3-0 works fine for me. That's interesting that it works for you though. No clue what's causing my problem.
Also when you say upgrade, do you mean you flashed 16 on top of 15.1? I did a clean flash, wiping everything.
The March 2 build is now booting for me. Noticed some changes to cryptfs in the logs, and sure enough. Now that it's booting, everything actually seems pretty stable.
I also got the "Decryption unsuccessful" on first boot of an upgrade from lineage 15.1
I was eventually able to boot, but had to do a bunch of random button pushing, and ended up nukeing the phone, but eventually got it to boot... But it has several other issues...
I did an "Advanced Wipe" in TWRP, and turned on every checkbox... Cleared every partition... Then did TWRP sideload of:
lineage-16.0-20190302-nightly-shamu-signed.zip
open_gapps-arm-9.0-nano-20190302.zip
Magisk-v18.1.zip
And it still asked for password on first boot... No way to put away the password entry keyboard BTW, preventing you from getting to the "Emergency Call" button... No 911 for you :'(
So I read somewhere that doing a "Format Data" under the TWRP wipe might help...
So I rebooted, did the above steps again, then tried "Format Data" before leaving TWRP... This failed to mount, and so no format... For some reason, I think on my phone I have TWRP on 2 partitions maybe? For some reason, rebooting from inside TWRP to "Recovery" (so yah, load recovery, then reboot directly to recovery) appeared to fix this unable to mount issue...
So now, I again wiped all paritions, sideloaded everything, got the "Format Data" to mount and work, then rebooted...
This booted and presented the initial setup (YAY!!) Went through that, and attempted to do a Google restore of the phone during setup... This looked like it worked, but NOTHING would download (Everything said it was trying to install, but nothing would...)
I am not super knowledgeable about this stuff, but one of my guess-timations of the issue was that it was a storage permission issue... Rebooted to TWRP again, and under Advanced I found something called "Fix Contents" that claimed it would attempt to repair the SELINUX model or something, which sounded permission issue related to me, so I tried that one...
And it booted, and things installed from Google Play (Double YAY!!)
I attempted to setup multiple users, and logging in a second user apparently seems to kill the Software Home Buttons for all users, and only rebooting brings them back for the primary user, and they disappear again when booting a secondary user... Other than this so far it is very fast, really quick, and looks like it has alot of potential as soon as they work out the kinks
P.S. Now I just wish they would un-discontinue Lineage support for the LG V20... Long live Removable Batteries paired with SDCard slot and IR-Blaster for the win!
Is there a way too root yet
I installed the "stock" version of Gapps that came with the pixel launcher. I can only use the Trebuchet launcher because the Pixel Launcher only crashes. Should I have installed a different Gapps version if it is unsupported? Or is this just a bug? Also, the Android Setup wizard keeps crashing when it is checking for an update at the beginning. It will not complete. Other than those issues, everything else seems to be working fine so far.
girkev said:
Is there a way too root yet
Click to expand...
Click to collapse
Yes. Magisk.
nhasian said:
I installed the "stock" version of Gapps that came with the pixel launcher. I can only use the Trebuchet launcher because the Pixel Launcher only crashes. Should I have installed a different Gapps version if it is unsupported? Or is this just a bug? Also, the Android Setup wizard keeps crashing when it is checking for an update at the beginning. It will not complete. Other than those issues, everything else seems to be working fine so far.
Click to expand...
Click to collapse
I am also seeing this problem, as are several others: https://forum.xda-developers.com/nexus-6/help/pixel-launcher-issue-lineage-16-nexus-6-t3906748
I am also facing the problem of the crash of pixel launcher. Does anybody know whether there is a recovery could decrypt the data of Android Pie?
1997cui said:
I am also facing the problem of the crash of pixel launcher. Does anybody know whether there is a recovery could decrypt the data of Android Pie?
Click to expand...
Click to collapse
Do you have a backup of your data? If you do, don't bother trying to decrypt it. Just wipe format your phone and start fresh.
wipe is not enough, must format encrypted partition
Just wanted to clarify that wiping is not sufficient to remove the encrypted partition. it must be formatted from the advanced wipe settings in TWRP.
David B. said:
Do you have a backup of your data? If you do, don't bother trying to decrypt it. Just wipe your phone and start fresh.
Click to expand...
Click to collapse
nhasian said:
Just wanted to clarify that wiping is not sufficient to remove the encrypted partition. it must be formatted from the advanced wipe settings in TWRP.
Click to expand...
Click to collapse
Yes. Sorry. I am aware of this, but used the incorrect terminology. Format was indeed what I had intended to say.
the 1st 16 release my camera did not work but it did on the 2nd nightly. i did today's [mar 6th] update and the camera does not work. info only.
dr1445 said:
the 1st 16 release my camera did not work but it did on the 2nd nightly. i did today's [mar 6th] update and the camera does not work. info only.
Click to expand...
Click to collapse
Usually, a reboot fixes the camera. It seems that on some boots it works and on some it doesn't.
https://forum.xda-developers.com/ne...geos-16-0-nexus-6-shamu-t3906045/post79053994
ok, i will give it a try.
The question probably sounds stupid but after almost a year of just forgetting about using root or unlocking bootlader i forgot many things.
I remember i used to have a mi 9 with encryption on and everytime i open twrp you will need to decrypt the data.
Now with the MI 9T Pro i had to format data in order to boot into Evolution X ROM that of course left me with a decrypted phone and i dont really like it in case my phone gets stole or something.
Do you guys know if i can use the option inside teh ROM to encrypt and what else i wuld need to do?
Thanks in advance to whoever takes the time to respond
PriPhaze said:
The question probably sounds stupid but after almost a year of just forgetting about using root or unlocking bootlader i forgot many things.
I remember i used to have a mi 9 with encryption on and everytime i open twrp you will need to decrypt the data.
Now with the MI 9T Pro i had to format data in order to boot into Evolution X ROM that of course left me with a decrypted phone and i dont really like it in case my phone gets stole or something.
Do you guys know if i can use the option inside teh ROM to encrypt and what else i wuld need to do?
Thanks in advance to whoever takes the time to respond
Click to expand...
Click to collapse
If all you did was format data, then encryption is still enabled. As soon as you setup lock-screen security, i.e. PIN, password, pattern, etc., for the first time your phone will automatically be encrypted.
Robbo.5000 said:
If all you did was format data, then encryption is still enabled. As soon as you setup lock-screen security, i.e. PIN, password, pattern, etc., for the first time your phone will automatically be encrypted.
Click to expand...
Click to collapse
No I couldn't boot until I flashed the DM verity.
So the encryption is now gone, but do you know if I can encrypt and then flash DM verity again with the force encryption on?.
PriPhaze said:
No I couldn't boot until I flashed the DM verity.
So the encryption is now gone, but do you know if I can encrypt and then glad DM verity again with the force encryption on?.
Click to expand...
Click to collapse
Ordinarily you shouldn't need to flash dm-verity. And as far as I'm aware, there is still no need to.
Normally it's just a case of formatting data to temporarily remove encryption, if flashing over MIUI.
As to your specific question, I couldn't say, as I've never needed to flash a dm-verity, disable force encrypt, or vbmeta file/script.
Personally, I would flash the latest fastboot MIUI ROM for the phone, then reinstall EvoX.
Before installing the ROM, in TWRP do the factory reset and then format data (There is no need to wipe anything else). Then reboot into TWRP to ensure the newly formatted data partition is properly mounted and flash as normal.
This has worked for me every time.
Yeah, some roms aren't booting without dfe.
to remove decrypt you can just wipe vendor and flash it again. you'll get encrypted. (however, some users confirm it puts them back into recovery, and they needed to reflash vendor+dfe for them.) Currently investigating if this is a RIN or RCN problem or for every device.
alternatively. If you are scared about having your device stolen. May I suggest you stay decrypted. Use ofox. and under ofox settings add a recovery password?
In the event you get stolen, they won't be able to access your recovery.
also, I'm looking for someone to test if wiping the data partition and not flashing dfe (after a rom has booted for the first time) and rebooting causes encyrption. (as you desired.) If you're willing to test. Try the above 3 methods?
Sandeeep Kiran said:
Yeah, some roms aren't booting without dfe.
to remove decrypt you can just wipe vendor and flash it again. you'll get encrypted. (however, some users confirm it puts them back into recovery, and they needed to reflash vendor+dfe for them.) Currently investigating if this is a RIN or RCN problem or for every device.
alternatively. If you are scared about having your device stolen. May I suggest you stay decrypted. Use ofox. and under ofox settings add a recovery password?
In the event you get stolen, they won't be able to access your recovery.
also, I'm looking for someone to test if wiping the data partition and not flashing dfe (after a rom has booted for the first time) and rebooting causes encyrption. (as you desired.) If you're willing to test. Try the above 3 methods?
Click to expand...
Click to collapse
BS. There is zero 'need' to flash dfe scripts. People are not formatting data when they need to, then when they cannot boot into a newly flashed ROM, they search and find solutions telling them to format data and flash dfe scripts. The thing is, people do not realise that it is the formatting data that fixes the problem, and they believe it is the dfe patch that is the fix. In all these cases formatting data alone would have been enough to fix the problem.
Also Orange Fox is only preferential if you stay with MIUI, as it's extra features are all about working with MIUI. If you are going with an AOSP ROM, stick with mauronofrio's latest TWRP, it is by far the best recovery for this phone.
As far as your 'test' is concerned, twice I have had bootloops after flashing a ROM, that have been fixed by formatting data alone.
The first time was when I first flashed an AOSP based ROM over MIUI before knowing that formatting data was required in this scenario. The second time was flashing AOSiP over LOS, when I still thought that going from one AOSP ROM to another never needed to format data when flashing.
Robbo.5000 said:
BS. There is zero 'need' to flash dfe scripts. People are not formatting data when they need to, then when they cannot boot into a newly flashed ROM, they search and find solutions telling them to format data and flash dfe scripts. The thing is, people do not realise that it is the formatting data that fixes the problem, and they believe it is the dfe patch that is the fix. In all these cases formatting data alone would have been enough to fix the problem.
Also Orange Fox is only preferential if you stay with MIUI, as it's extra features are all about working with MIUI. If you are going with an AOSP ROM, stick with mauronofrio's latest TWRP, it is by far the best recovery for this phone.
As far as your 'test' is concerned, twice I have had bootloops after flashing a ROM, that have been fixed by formatting data alone.
The first time was when I first flashed an AOSP based ROM over MIUI before knowing that formatting data was required in this scenario. The second time was flashing AOSiP over LOS, when I still thought that going from one AOSP ROM to another never needed to format data when flashing.
Click to expand...
Click to collapse
We've had numerous cases for specific devices not booting without dfe despite formatting for some roms. I believe they are aosp roms that face this. Some when using oss, I vaguely remember. or when moving from LOS fod to mi9 fod or which flashing a different kernel.
(Do note. There are over 50+ roms for our device. 6 variants of the phone. 7 vendors (and separate modified vendors). 2 kinds of fod implementations. and about 95% of the cases arent asked on xda. 25% of the roms aren't posted either. None of the experimental builds are provided on xda.
There are tons of combos users use.)
I have not seen you on telegram. Only on xda. Who are you btw?
twrp is great. Ofox has a better ui and more features. Also, mauronofrio doesn't own a k20p btw. Just FYI. But he has the experience to still update twrp.
updated twrp is still not official, and gives error 7 for some raphaelin users who haven't updated updater-script.
recoveries are subjective. I mean, we have like 6 different recoveries now so.
Sandeeep Kiran said:
We've had numerous cases for specific devices not booting without dfe despite formatting for some roms. I believe they are aosp roms that face this. Some when using oss, I vaguely remember. or when moving from LOS fod to mi9 fod or which flashing a different kernel.
(Do note. There are over 50+ roms for our device. 6 variants of the phone. 7 vendors (and separate modified vendors). 2 kinds of fod implementations. and about 95% of the cases arent asked on xda. 25% of the roms aren't posted either. None of the experimental builds are provided on xda.
There are tons of combos users use.)
I have not seen you on telegram. Only on xda. Who are you btw?
twrp is great. Ofox has a better ui and more features. Also, mauronofrio doesn't own a k20p btw. Just FYI. But he has the experience to still update twrp.
updated twrp is still not official, and gives error 7 for some raphaelin users who haven't updated updater-script.
recoveries are subjective. I mean, we have like 6 different recoveries now so.
Click to expand...
Click to collapse
Numerous cases? Who's we? What roms on what devices need dfe then? Only seen 2 roms ask for dfe, everything else it's as easy as 'going to and from miui, format data and reboot recovery' works every single time.
Sandeeep Kiran said:
We've had numerous cases for specific devices not booting without dfe despite formatting for some roms. I believe they are aosp roms that face this. Some when using oss, I vaguely remember. or when moving from LOS fod to mi9 fod or which flashing a different kernel.
(Do note. There are over 50+ roms for our device. 6 variants of the phone. 7 vendors (and separate modified vendors). 2 kinds of fod implementations. and about 95% of the cases arent asked on xda. 25% of the roms aren't posted either. None of the experimental builds are provided on xda.
There are tons of combos users use.)
I have not seen you on telegram. Only on xda. Who are you btw?
twrp is great. Ofox has a better ui and more features. Also, mauronofrio doesn't own a k20p btw. Just FYI. But he has the experience to still update twrp.
updated twrp is still not official, and gives error 7 for some raphaelin users who haven't updated updater-script.
recoveries are subjective. I mean, we have like 6 different recoveries now so.
Click to expand...
Click to collapse
Try this next time you see somebody saying they have tried may things and always get bootloops when trying to flash an AOSP ROM and you want to advise them to flash dfe.
Instead tell them to flash the latest MIUI fastboot ROM for their device, then install TWRP, in TWRP do a factory reset followed by format data, then reboot into TWRP and flash the ROM.
I bet they will come back and tell you it worked.
Again there should be zero need to flash dfe scripts.
If there are any AOSP ROMs out there that genuinely won't boot without flashing dfe (and here I'm talking about all users of such ROM), then the dev had done something stupid and everyone should seriously avoid the ROM.
At least half of the 50+ ROMs are no longer actively maintained.
The vast majority of Orange Fox extra features are specific to MIUI and so are redundant for AOSP ROMs. Mauronifrio's latest TWRP is the most stable for this phone, so if you're going with AOSP ROMs then the extra stability makes most sense.
I've been aware that mauronifrio does not own this phone ever since his initial build. I was also aware back then that he is also an official TWRP maintainer for other devices and so would mostly likely become the maintainer of the official version for this phone, which has now happened. If you go to the official TWRP site and download for this phone, it is by mauronifrio. You can also download the official version from the OP of his TWRP thread.
I would suggest that in most cases, people getting error 7 issues are not on the latest mauronofrio TWRP build.
Are you aware that all these different recoveries are just TWRP with a fancy dress. This is the great thing about TWRP. It was designed to be extensible, to allow others to build on it, in terms of functionality and design. So really there is only TWRP, just many different flavours.
I'm running the CrDroid 5 rom, and I dislike the force encryption, I've tried a force encryption disabler and hacking Magisk to disable force encryption even with encrypted data detected, but it hasn't fixed the issue. (I've found a disabler that works)
I also heard about the hidden 120Hz mode the phone has from here https://www.xda-developers.com/sony-xperia-xz-premium-hidden-120hz-screen-mode-razer-phone/
Under the update, it's mentioned that this phone also has it too, and I'm wondering if anyone has been able to enable it, and if it's possible, how
asdf2345 said:
I'm running the CrDroid 5 rom, and I dislike the force encryption, I've tried a force encryption disabler and hacking Magisk to disable force encryption even with encrypted data detected, but it hasn't fixed the issue.
I also heard about the hidden 120Hz mode the phone has from here https://www.xda-developers.com/sony-xperia-xz-premium-hidden-120hz-screen-mode-razer-phone/
Under the update, it's mentioned that this phone also has it too, and I'm wondering if anyone has been able to enable it, and if it's possible, how
Click to expand...
Click to collapse
What exactly is force encryption messing up on your phone?
MDomokos said:
What exactly is force encryption messing up on your phone?
Click to expand...
Click to collapse
I just don't like it, I also found a disabler that works, so I'm not worried about it anymore
I see its an older post now asdf2345 . But could you share the tool you used to disable the force encryption. I freakin hate it specially because its been "forced" Just replaced my xperia Z5 Compact with a 2nd hand XZ1 Compact after 6 years yes.... LOL Its rooted with magisk and installed twrp latest for xz1c. all works fine but i dont want the "forced encryption" at all . On my windows 10/11 laptops i already disabled these idiot features so the installer not even bother to set it up by default. My old z5c was on android 7 i really liked it, no additional wasted partitions for system ROM images and so forth. I tried many methods, in fact if i haven't reflashed this poor bugger 10x by now.... This was my main reason i longed as much on old system7, i am google less rooted . Forced encryption is messing up a lot of my things just being there.
AssimilatorX.System said:
I see its an older post now asdf2345 . But could you share the tool you used to disable the force encryption. I freakin hate it specially because its been "forced" Just replaced my xperia Z5 Compact with a 2nd hand XZ1 Compact after 6 years yes.... LOL Its rooted with magisk and installed twrp latest for xz1c. all works fine but i dont want the "forced encryption" at all . On my windows 10/11 laptops i already disabled these idiot features so the installer not even bother to set it up by default. My old z5c was on android 7 i really liked it, no additional wasted partitions for system ROM images and so forth. I tried many methods, in fact if i haven't reflashed this poor bugger 10x by now.... This was my main reason i longed as much on old system7, i am google less rooted . Forced encryption is messing up a lot of my things just being there.
Click to expand...
Click to collapse
I've forgotten where I got it from, but I still have the file.
asdf2345 said:
I've forgotten where I got it from, but I still have the file.
Click to expand...
Click to collapse
Very kind thank you. I was searched far n wide on the net. find lots of similar things, however they either wasnt for sony or specified strictly for xxxxx devices LG, ASUS,OPPO etc etc. You still have xz1c G8441? I tried out Havoc-OS 4.8 works really well but i missed sony camera, and my call recorder "ACR Pro" wasnt working properly. Than i had to find out that flashtoop always gives a null error while flashing roms and i had to find again new softwares "newflasher" to do the job. Thanks again will try it out. What i should kow about it? Flash wipe /data/ i assume, I am on TWRP 3.3.1.0
Forgot to mention that my device running on stock kernel with flashed drmfix. Update ... After a bit of messing around it worked. Its not encrypted now. Flashed factory UK stock 228 because it went to bootlooping than twrp 3310, and this time i flashed bliss rom 12.12 android 10 for lilac. Flashed the file you sent me and flashed magist 23. First boot went to recovery. So i assumed , it want a factory reset so i did one. than all fine. Now i just need to go in my bank to unlock my barclays banking app as i installed it about 25x in the last few days. Thank you again for the fast response and help asdf2345. Will se in a few days how this rom fares, but appears to be the best so far, even has sony camera app built in, and i am using it without google or gapp spyware.
AssimilatorX.System said:
Forgot to mention that my device running on stock kernel with flashed drmfix. Update ... After a bit of messing around it worked. Its not encrypted now. Flashed factory UK stock 228 because it went to bootlooping than twrp 3310, and this time i flashed bliss rom 12.12 android 10 for lilac. Flashed the file you sent me and flashed magist 23. First boot went to recovery. So i assumed , it want a factory reset so i did one. than all fine. Now i just need to go in my bank to unlock my barclays banking app as i installed it about 25x in the last few days. Thank you again for the fast response and help asdf2345. Will se in a few days how this rom fares, but appears to be the best so far, even has sony camera app built in, and i am using it without google or gapp spyware.
Click to expand...
Click to collapse
Yeah, I hate that because the device is treble, you gotta reinstall the original ROM to flash a new ROM, so you always gotta start fresh and unnecessarily wear out the flash. I currently use the Resurrection Remix Oreo ROM by hockeymikey.
Will try set fingerprint later as it makes it much easier to unlock and log-in to paypal and banking apps, but hope it would still unencrypted. Also would be nice to get rid of the [system image] 5000mb and [vendor image] 1500mb partitions that just a waste of storage. My old z5c didnt have these useless things on android 7.0
AssimilatorX.System said:
Will try set fingerprint later as it makes it much easier to unlock and log-in to paypal and banking apps, but hope it would still unencrypted. Also would be nice to get rid of the [system image] 5000mb and [vendor image] 1500mb partitions that just a waste of storage. My old z5c didnt have these useless things on android 7.0
Click to expand...
Click to collapse
Yeah, that's how I have it. I wish I we could get rid of the image partitions as well. I thought it was because of treble, but my non-treble XZ also has those as well, so I dunno.
AssimilatorX.System said:
Forgot to mention that my device running on stock kernel with flashed drmfix. Update ... After a bit of messing around it worked. Its not encrypted now. Flashed factory UK stock 228 because it went to bootlooping than twrp 3310, and this time i flashed bliss rom 12.12 android 10 for lilac. Flashed the file you sent me and flashed magist 23. First boot went to recovery. So i assumed , it want a factory reset so i did one. than all fine. Now i just need to go in my bank to unlock my barclays banking app as i installed it about 25x in the last few days. Thank you again for the fast response and help asdf2345. Will se in a few days how this rom fares, but appears to be the best so far, even has sony camera app built in, and i am using it without google or gapp spyware.
Click to expand...
Click to collapse
plz give me drmfix script?
Hiya. So, here's the story:
Xiaomi Mi 9T Pro EEA, bought from Amazon, not a shady reseller
I made a Google Backup of my apps, because I decided to try out some Android 11 roms.
After trying them out, I wanted to go back to Android 10, so I clean flashed my rom, GApps and disable force encrypt, the usual stuff. But the Google Backup, that I previously used on all the A11 roms was suddenly gone.
I thought, that wouldn't be a problem, since I still had my Android 10 TWRP Backup that I made, before I started experimenting with A11.
I restored that backup and couldn't unlock my phone. So I deleted /data/system/locksettings.db and finally my phone would unlock.
But: My sensors didn't work anymore. I searched the internet for info and found out, that my persist partition got corrupted.
tl; dr: I restored a TWRP backup and my Persist partition corrupted.
Until yesterday, I didn't even know, what the Persist partition was. I never touched it.
I know how to get my sensors working again. But I guess my Widevine L1 is gone now, isn't it?
Seki_ said:
Hiya. So, here's the story:
Xiaomi Mi 9T Pro EEA, bought from Amazon, not a shady reseller
I made a Google Backup of my apps, because I decided to try out some Android 11 roms.
After trying them out, I wanted to go back to Android 10, so I clean flashed my rom, GApps and disable force encrypt, the usual stuff. But the Google Backup, that I previously used on all the A11 roms was suddenly gone.
I thought, that wouldn't be a problem, since I still had my Android 10 TWRP Backup that I made, before I started experimenting with A11.
I restored that backup and couldn't unlock my phone. So I deleted /data/system/locksettings.db and finally my phone would unlock.
But: My sensors didn't work anymore. I searched the internet for info and found out, that my persist partition got corrupted.
tl; dr: I restored a TWRP backup and my Persist partition corrupted.
Until yesterday, I didn't even know, what the Persist partition was. I never touched it.
I know how to get my sensors working again. But I guess my Widevine L1 is gone now, isn't it?
Click to expand...
Click to collapse
Yes, it's gone. Share what you did to get the sensors working.
mauam said:
Yes, it's gone. Share what you did to get the sensors working.
Click to expand...
Click to collapse
Unfortunate. Oh well.
There's actually multiple ways. You could:
Flash persist from Xiaomi's full fastboot package
Flash persistbak to persist
Flash a working persist image from another Mi 9T Pro
All those things worked for me. In the end, I settled with the persistbak method.
Seki_ said:
Unfortunate. Oh well.
There's actually multiple ways. You could:
Flash persist from Xiaomi's full fastboot package
Flash persistbak to persist
Flash a working persist image from another Mi 9T Pro
All those things worked for me. In the end, I settled with the persistbak method.
Click to expand...
Click to collapse
could you tell me how you flashed and dumped persistbak?
wavychris said:
could you tell me how you flashed and dumped persistbak?
Click to expand...
Click to collapse
It's almost been a year, so I don't fully remember what I did exactly, but there's some tutorials around you can find pretty easily.
The only thing I remember is going into fastboot and dumping and flashing my partitions via command line, I think.
Seki_ said:
It's almost been a year, so I don't fully remember what I did exactly, but there's some tutorials around you can find pretty easily.
The only thing I remember is going into fastboot and dumping and flashing my partitions via command line, I think.
Click to expand...
Click to collapse
ive been searching for a month and im still not sure which tutorial to follow, all i want is to fix my sensors and get widevine l1 back in case it gets void when i flash persist, any help would be phenomenal!
wavychris said:
ive been searching for a month and im still not sure which tutorial to follow, all i want is to fix my sensors and get widevine l1 back in case it gets void when i flash persist, any help would be phenomenal!
Click to expand...
Click to collapse
Well if you didn't make a backup before, L1 is L Gone. I didn't get it back. Following any tutorial should get you your sensors back though.
And remember: The first thing to do when getting a new phone is to backup that persist partition, so you don't need to worry about something like this happening again.
Seki_ said:
Well if you didn't make a backup before, L1 is L Gone. I didn't get it back. Following any tutorial should get you your sensors back though.
And remember: The first thing to do when getting a new phone is to backup that persist partition, so you don't need to worry about something like this happening again.
Click to expand...
Click to collapse
if i remember correctly you can get widevine l1 back via a magisk module or flashing xiaomi.eu rom and you can download the certificate from there, try it out if you dont got nothing to lose, by the way, if i flash persist will the sensors work permanently or do i have to do this again every once in a while?
wavychris said:
if i remember correctly you can get widevine l1 back via a magisk module or flashing xiaomi.eu rom and you can download the certificate from there, try it out if you dont got nothing to lose, by the way, if i flash persist will the sensors work permanently or do i have to do this again every once in a while?
Click to expand...
Click to collapse
Oh, interesting. Definitely gotta try that, thanks. How do you download the certificate in MIUI? Does it happen automatically?
Since I flashed my persistbak, I didn't flash anything else and my sensors are still working, so I guess it sporadically happens... sometimes?
Btw, if you aren't already, you should use OrangeFox recovery instead of TWRP on Xiaomi devices. It usually doesn't kill itself by wiping partitions or flashing roms, especially when coming from MIUI. Also, you can make persist backups with it. For some reason they removed that feature from TWRP.
Seki_ said:
Oh, interesting. Definitely gotta try that, thanks. How do you download the certificate in MIUI? Does it happen automatically?
Since I flashed my persistbak, I didn't flash anything else and my sensors are still working, so I guess it sporadically happens... sometimes?
Btw, if you aren't already, you should use OrangeFox recovery instead of TWRP on Xiaomi devices. It usually doesn't kill itself by wiping partitions or flashing roms, especially when coming from MIUI. Also, you can make persist backups with it. For some reason they removed that feature from TWRP.
Click to expand...
Click to collapse
in case you got it wrong xiaomi.eu is a custom miui based rom, not official, just to clarify that, and to download the certificate you must enroll fingerprint then go to fingerprint payments and youll find widevine l1 there, then click on certificate in widevine l1, pretty easy stuff, also how do i install orangefox?
wavychris said:
in case you got it wrong xiaomi.eu is a custom miui based rom, not official, just to clarify that, and to download the certificate you must enroll fingerprint then go to fingerprint payments and youll find widevine l1 there, then click on certificate in widevine l1, pretty easy stuff, also how do i install orangefox?
Click to expand...
Click to collapse
Oh, I can't read. For some reason, I thought you said xiaomi.eu or stock, that's why I said MIUI. Anyway, thanks for telling me. I never heard of that.
To install OrangeFox, just download the zip, make backups if you want to be extra sure and flash the zip. Here's the thread: https://forum.xda-developers.com/t/recovery-official-orangefox-recovery-project-r11-1.4308019/
The UI is different, so it took me a little while to get used to it, but ultimately, OrangeFox is a smoother experience than TWRP, at least on Xiaomi.
wavychris said:
if i remember correctly you can get widevine l1 back via a magisk module or flashing xiaomi.eu rom and you can download the certificate from there, try it out if you dont got nothing to lose, by the way, if i flash persist will the sensors work permanently or do i have to do this again every once in a while?
Click to expand...
Click to collapse
No, you cannot get L1 through Magisk module - because you need a (paid) certificate for your hardware
To the contrary, there is a Magisk module that disables L1, dropping you to default L3.
Although I never understood who/why needs that
wavychris said:
could you tell me how you flashed and dumped persistbak?
Click to expand...
Click to collapse
See here how to backup and/or dump Persist and restore/flash it back.
Of course, if you didn't backup a working Persist on time, you have nothing to restore:
Extracting stock Boot, Recovery and Persist images
Talking here about how to extract the stock Boot, Recovery and Persist images, needed in case of e.g. bootloop upon flashing Magisk or TWRP, to reflash the stock image(s). Also, boot image is needed for patching from Magisk Manager (and flashing...
forum.xda-developers.com
Seki_ said:
Oh, I can't read. For some reason, I thought you said xiaomi.eu or stock, that's why I said MIUI. Anyway, thanks for telling me. I never heard of that.
To install OrangeFox, just download the zip, make backups if you want to be extra sure and flash the zip. Here's the thread: https://forum.xda-developers.com/t/recovery-official-orangefox-recovery-project-r11-1.4308019/
The UI is different, so it took me a little while to get used to it, but ultimately, OrangeFox is a smoother experience than TWRP, at least on Xiaomi.
Click to expand...
Click to collapse
its alright lol, thanks for your help btw have a nice day/night
zgfg said:
No, you cannot get L1 through Magisk module - because you need a (paid) certificate for your hardware
To the contrary, there is a Magisk module that disables L1, dropping you to default L3.
Although I never understood who/why needs that
Click to expand...
Click to collapse
that sucks man, thanks for the news anyway i might use xiaomi.eu rom to get it back that way at least
zgfg said:
See here how to backup and/or dump Persist and restore/flash it back.
Of course, if you didn't backup a working Persist on time, you have nothing to restore:
Extracting stock Boot, Recovery and Persist images
Talking here about how to extract the stock Boot, Recovery and Persist images, needed in case of e.g. bootloop upon flashing Magisk or TWRP, to reflash the stock image(s). Also, boot image is needed for patching from Magisk Manager (and flashing...
forum.xda-developers.com
Click to expand...
Click to collapse
alright thanks i might try it out tommorow ill update you on the process if you want
Hey guys, let me introduce myself, my name is Lisandro, I'm new and I'm from Venezuela.
I have a Redmi 7A I bought like 1 year ago.
Since 2 months ago, I've been experiencing an issue with Google login and some Google pages on Chrome (or almost every browser)
The problem is that every time I try to log in my account, "Google play services" gets instantly killed, I though it was a problem with Google Play Services, I deleted the update, tried again and same issue, tried the same with WebView, = same issue.
So I decided to unlock bootloader and change the ROM to DotOs ROM.
What was the surprise?
Exactly the same issue. I'm not able to find a fix.
So I would like to read your opinion or, if it's possible, your advice. In any case, thanks so much.
(- PD; My camera isn't working due to water damage, I'm not sure if it's what's causing this)
I have the same phone but i get 0 issues related to this
Kenora_I said:
I have the same phone but i get 0 issues related to this
Click to expand...
Click to collapse
I know, it's so weird. It's something I've never experienced in a phone before
Did you do anything to the phone before this issue?
Hmm have you tried flashing a full fastboot rom with MiFlash tool?
It would overwrite custom recovery but it could solve your issue.
Advice you to backup data if you do it
Also check Clean All checkbox in the tool
Kenora_I said:
Did you do anything to the phone before this issue?
Click to expand...
Click to collapse
Nothing, I used my phone normally. One day I started to have the issue with pages getting closed (but my Google account had being added before and I didn't know the problem was there too)
The pages getting closed issue was what obligated me to Reset my phone by factory reset, when my phone restarted, I knew a have a bigger issue, 'cuz I wasn't even able to log in.
DarkSoul-1 said:
Nothing, I used my phone normally. One day I started to have the issue with pages getting closed (but my Google account had being added before and I didn't know the problem was there too)
The pages getting closed issue was what obligated me to Reset my phone by factory reset, when my phone restarted, I knew a have a bigger issue, 'cuz I wasn't even able to log in.
Click to expand...
Click to collapse
Let us just wipe the whole partitions and flash the fastboot rom through miflash
Do you know how to wipe /system all manually?
scorpii said:
: I manually wiped each of /system, /cache, etc through fastboot in the bootloader, and I also (from adb in recovery) manually did mkdir /data and mkdir /data/media
Click to expand...
Click to collapse
After some digging I uncovered this post from someone who had the same crashing issue even when installing different roms.
Kenora_I said:
Do you know how to wipe /system all manually?
Click to expand...
Click to collapse
Via TWRP, right? That's what I did when installed DotOs Rom
Hmm, via fastboot and manually mkdir /data and /data/media in adb through twrp
Are you okay with reinstalling the base MIUI?
I think we should first just flash the stock fastboot rom, which will overwrite your old recovery but you can install it through bootloader again
Kenora_I said:
Hmm, via fastboot and manually mkdir /data and /data/media in adb through twrp
Click to expand...
Click to collapse
Kenora_I said:
Are you okay with reinstalling the base MIUI?
I think we should first just flash the stock fastboot rom, which will overwrite your old recovery but you can install it through bootloader again
Click to expand...
Click to collapse
I have no problem with reinstalling it if it's for a try to solve the problem.
I don't rlly know how to manually do that, is there any guide for that?
I'll do it tomorrow when I arrive home
DarkSoul-1 said:
I have no problem with reinstalling it if it's for a try to solve the problem.
I don't rlly know how to manually do that, is there any guide for that?
I'll do it tomorrow when I arrive home
Click to expand...
Click to collapse
Here,
MIFLASH[GUIDE]⚙ USE XIAOMI FLASH TOOL
FOR ALL XIAOMI BOOTLOADER MUST BE UNLOCKED https://new.c.mi.com/global/post/101245 https://en.miui.com/unlock/index.html ----------------------------------------------------------------------------------------------------------- All your data...
forum.xda-developers.com
Kenora_I said:
Here,
MIFLASH[GUIDE]⚙ USE XIAOMI FLASH TOOL
FOR ALL XIAOMI BOOTLOADER MUST BE UNLOCKED https://new.c.mi.com/global/post/101245 https://en.miui.com/unlock/index.html ----------------------------------------------------------------------------------------------------------- All your data...
forum.xda-developers.com
Click to expand...
Click to collapse
I really appreciate your help, thank you so much. I'll do it tomorrow, I'll be notifying you in any case. Thank you again
DarkSoul-1 said:
I really appreciate your help, thank you so much. I'll do it tomorrow, I'll be notifying you in any case. Thank you again
Click to expand...
Click to collapse
No problem, good luck see ya tomorrow!
what miui version you are on? if this is the latest Chinese MIUI 12.0.4... i haven't read of anyone successful of installing Google Apps on it.