Question What's the best way to install latest chinese beta? - Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40

Greetings!
I'm currently using the latest Stable rom for global (12.5.1), I'm rooted and I have TWRP, everything is working fine.
Don't ask me why lol, but I want to install the latest chinese beta (miui_ALIOTH_21.6.2_6d346564dd_11.0, https://xiaomifirmwareupdater.com/miui/alioth/weekly/21.6.2/), I copy the file to internal storage, boot into twrp, flash it, clean cache and reboot.
After those steps, the phone reboots and it enters in a semi-bootloop on the poco logo. The phone restarts a few times (like 5-6) and after that, it boots succesfully.
When it boots, it boots into the stable rom (12.5.1) and not the recently flashed chinese beta (21.6.2), does anyone knows why this happen? D=
Also as extra info, my device is global, so, there's no issue if I try to install a chinese beta, right?
Have an awesome day! =D

i'm probably not of much use here, but as no-one else has replied i'll tell you...!
i had the same issue but it was a while ago now, so i can't actually recall how i rectified it (sorry). but i think i either flashed the rom, then before booting to system, factory reset in twrp by typing 'yes'. then boot to system...
or, i flashed both slots, a and b with the rom zip. in twrp go to reboot, then you can see which slot is active. flash rom, then reboot to other slot in twrp. after changing to alternative slot i think i then, as i always do when changing slots in twrp, rebooted twrp itself to be sure alt slot is deffo active. then flash rom to alt slot. then, after both slots are flashed, factory reset typing 'yes' then boot to system...
like i say, sorry if that's a bit vague, i really can't recall the remedy. good luck

reg66 said:
i'm probably not of much use here, but as no-one else has replied i'll tell you...!
i had the same issue but it was a while ago now, so i can't actually recall how i rectified it (sorry). but i think i either flashed the rom, then before booting to system, factory reset in twrp by typing 'yes'. then boot to system...
or, i flashed both slots, a and b with the rom zip. in twrp go to reboot, then you can see which slot is active. flash rom, then reboot to other slot in twrp. after changing to alternative slot i think i then, as i always do when changing slots in twrp, rebooted twrp itself to be sure alt slot is deffo active. then flash rom to alt slot.
like i say, sorry if that's a bit vague, i really can't recall the remedy. good luck
Click to expand...
Click to collapse
Let me try that!
Also, and just to clarify, I want to flash the latest chinese beta because I want to use Arrow OS without any issues.
As I said, I'm currently running the latest stable MIUI, and If I flash Arrow OS on top of it, I face a looooooot of random crashes/reboots, to the point that I can't do anything on it.
Nothing fails when I use the stable beta, so I don't really know why this is happening. D=

Kimbaroth said:
Let me try that!
Also, and just to clarify, I want to flash the latest chinese beta because I want to use Arrow OS without any issues.
As I said, I'm currently running the latest stable MIUI, and If I flash Arrow OS on top of it, I face a looooooot of random crashes/reboots, to the point that I can't do anything on it.
Nothing fails when I use the stable beta, so I don't really know why this is happening. D=
Click to expand...
Click to collapse
i'm in that exact boat, running arrowOS with 21.6.2 XiaomiEU flashed before hand. i had my first and only rr today, not sure what caused it. no biggy though, i can live with one... but i have had a few audio issues. it's a bit weird, but audio over bluetooth cuts out every few seconds... until, and this is the odd part, i launch whatsapp and make a video call (found out by chance). after that bluetooth audio works fine. needs repeating after each reboot.
i didn't complain/report the rr or audio issue as i'm not using an early build of miui as a base ie 12.03 etc.

reg66 said:
i'm in that exact boat, running arrowOS with 21.6.2 XiaomiEU flashed before hand. i had my first and only rr today, not sure what caused it. no biggy though, i can live with one... but i have had a few audio issues. it's a bit weird, but audio over bluetooth cuts out every few seconds... until, and this is the odd part, i launch whatsapp and make a video call (found out by chance). after that bluetooth audio works fine. needs repeating after each reboot.
i didn't complain/report the rr or audio issue as i'm not using an early build of miui as a base ie 12.03 etc.
Click to expand...
Click to collapse
I'm gonna try flashing the latest firmware, as someone sugested on the Arrow OS thread, maybe (and hopefully) that'll fix bluetooth and proximity sensor issues.

Kimbaroth said:
I'm gonna try flashing the latest firmware, as someone sugested on the Arrow OS thread, maybe (and hopefully) that'll fix bluetooth and proximity sensor issues.
Click to expand...
Click to collapse
I'm interested in hearing your experiences.
I am still wondering if flashing a Chinese firmware on arrowos is really a good idea, even tho some ppl reported that it works fine.

4Style said:
I'm interested in hearing your experiences.
I am still wondering if flashing a Chinese firmware on arrowos is really a good idea, even tho some ppl reported that it works fine.
Click to expand...
Click to collapse
I flashed the pack for the lates fw, and I got some random reboots the first 2-3 times it booted, but after that it seems to be steady.
I can confirm that the proximity sensor issue is aaaaaaalmost gone, it stills fails but way less that before. The blutooth issues I still haven't tested em yet (I need to get into my car to do that).
So, yeah, it's safe to flash the latets fw: https://xiaomifirmwareupdater.com/firmware/alioth/weekly/21.6.2/
=)

Hello,
I am planning on getting the Chinese Rom as well, however, I am still waiting for my bootloader to unlock, about 72 hours left.
So what I got from the comments up there is you can flash the Chinese rom even if you are on Poco F3 and it is for Redmi k40 but you have to install the latest firmware first and that's it? Do you need to do something else first?
Not to mention the TWRP of course!
Apologies since I am kind of new to this thing
Thanks

sty2009 said:
Hello,
I am planning on getting the Chinese Rom as well, however, I am still waiting for my bootloader to unlock, about 72 hours left.
So what I got from the comments up there is you can flash the Chinese rom even if you are on Poco F3 and it is for Redmi k40 but you have to install the latest firmware first and that's it? Do you need to do something else first?
Not to mention the TWRP of course!
Apologies since I am kind of new to this thing
Thanks
Click to expand...
Click to collapse
You don't have to install the latest fw in order to get a working chinese rom install, but the latest fw always contains tweaks and stuff for many internal components (i.e. wifi, bluetooth, proximity sensors, etc), so yeah, that's recommended.
And yeah, you need to flash TWRP first, buuuuuut as reg66 said, you need to flash it on both of your phone slots (A and B), that way everything will work without issues. =)

hmm... just realised the weekly China (xiaomi EU) that i downloaded is different. didn't check your link in OP...
mine is xiaomi.eu_multi_HMK40_POCOF3_21.6.2_v12-11.zip from here
i usually check here xiaomi.eu for updates. if i were only flashing stock roms, i would only use the exact rom for my model/device ie poco f3 from here. other than that, for latest roms i would stick with xiaomi.eu roms...
anyway, i'll shut up now lol, i am a bit worse for wear and just waffling!!!

我使用的改名法,成功更新系统。
----------
MOD EDIT: English Translation Below
The name change method I used successfully updated the system.

丶铭丿昱 said:
我使用的改名法,成功更新系统。
----------
MOD EDIT: English Translation Below
The name change method I used successfully updated the system.
Click to expand...
Click to collapse
Does anyonw know what's the rename method?

Kimbaroth said:
Does anyonw know what's the rename method?
Click to expand...
Click to collapse
as a guess it's where you download the latest zip and rename it to 'update.zip' then put it in folder called 'downloaded_rom' and then update from settings or perhaps wait for prompt if set to auto update. can't say for sure though, haven't tried this method.
actually, just read, you can also rename the rom to update.zip and put in root of storage, then update via stock recovery... but again, i've not tried this method
EDIT: so there's no need to rename the zip. under settings, click on about phone/miui version and click the version multiple times until you get a message saying 'extra update features available' or something like that. click on the three dot menu on top right corner and click choose update package. navigate to your downloaded incremental update which from 12.0.3 global to 12.5.1 can be found here

reg66 said:
EDIT: so there's no need to rename the zip. under settings, click on about phone/miui version and click the version multiple times until you get a message saying 'extra update features available' or something like that. click on the three dot menu on top right corner and click choose update package. navigate to your downloaded incremental update which from 12.0.3 global to 12.5.1 can be found here
Click to expand...
Click to collapse
This is how I updated from 12.0.3 to 12.5.1, but only works from global to global (or same region to same region), if you try global to chinese, it doesn't work. =(

If CN ROM has a fastboot version u can use MiFlash tool (for safeness). Or TWRP for recovery ROM.

Kimbaroth said:
You don't have to install the latest fw in order to get a working chinese rom install, but the latest fw always contains tweaks and stuff for many internal components (i.e. wifi, bluetooth, proximity sensors, etc), so yeah, that's recommended.
And yeah, you need to flash TWRP first, buuuuuut as reg66 said, you need to flash it on both of your phone slots (A and B), that way everything will work without issues. =)
Click to expand...
Click to collapse
can you please guide how to flash latest chinese beta 21.7.13 here through TWRP and which TWRP is recommended and how to flash it on both of phone slots (A and B)?

Just intall Xiaomi.eu weekly ?
Why bother with an ad- and "analytics" infested unmodified china rom ?

The "Semi-bootloop" happened, because the bootloader detected that after a few trials Slot A is simply not bootable, so it switched to Slot B.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Related

[ROM][Lineage 16.0 Unofficial][Pixel 2 XL/Taimen][06-09-19]

Hi all. Since I haven't gotten any word as to when there will be official support, I wanted to go ahead and share a build of Lineage OS 16.0 for our Pixel 2 XL/Taimen. It's a completely stock build. If it's working for enough people, then I'll continue to provide builds until/unless we get official support. If you find an error, please try to post logs via logcat to aid in fixing it (better yet to submit it to the Lineage OS team directly as well).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Steps for First Install:
Flash latest google image
Boot using the latest version of TWRP: https://dl.twrp.me/taimen/twrp-3.2.3-1-taimen.img.html
Wipe cache and data
Flash latest ROM .zip file
Flash the TWRP installer: https://dl.twrp.me/taimen/twrp-pixel2-installer-taimen-3.2.3-1.zip.html
Reboot to recovery
Flash OpenGapps (Android 9.0, ARM 64, probably nano): https://opengapps.org/ or MindTheGapps: https://androidfilehost.com/?fid=3700668719832237178
If desired, flash a custom kernel
If desired, flash Magisk
Reboot and hopefully enjoy
Steps for Updates:
Follow steps 4- 10 above. You can skip steps 1 - 3 (latest Google image, booting with TWRP .img, wiping) and optionally 7 (flashing Gapps).
Latest ROM, 06-09-19:
Download
Old Releases:
Old Download
I usually like to provide updates every ~2 weeks or month to keep up with security updates and/or anything else important. Thanks for trying and God bless .
Special thanks to @draymond1987, @RaymanFX, and all the other developers for their continued hard work.
View changelog up to build date
/.repo/local_manifests/roomservice.xml is attached
A quick note: If you seem to get stuck on the Gapps setup wizard, you can touch each corner of the screen, going clockwise, starting in the top left corner, to skip it. I've seen the data transfer tool have issues lately. You can uninstall it and continue afterwards.
Any known bugs?
pimpdaddy00 said:
Any known bugs?
Click to expand...
Click to collapse
I had an issue at some point where it would shut off when unplugged, but I don't know if it was just something about how my phone is setup. The other thing I encountered was the setup wizard getting stuck before (but fixed after removing the data transfer tool manually later). I'm hoping to see someone else have it working as I know at some point I was able to boot without issue, other than Magisk possibly not working without flashing another custom kernel. Getting any feedback from logs would helpfully tell me what changed and possibly where to fix it at that point.
I checked the channelog and noticed a few minor changes that seemed nice. Overall, I just hope Active Edge gets working in future ROMs lol. Though I know it's difficult. Good job on this!
Can't even get this to boot.
LLStarks said:
Can't even get this to boot.
Click to expand...
Click to collapse
Do you see the lineage OS logo and then blank screen or very shortly after? I've been facing an issue where it looks like com.qualcomm.qti.telephonyservice stops due to not loading a reference properly if I'm not charging. Thanks for letting me know you've had issues.
I could never get past the Lineage logo. Initial boots are usually long, but it would just crap out and reboot to whatever recovery I put in.
LLStarks said:
I could never get past the Lineage logo. Initial boots are usually long, but it would just crap out and reboot to whatever recovery I put in.
Click to expand...
Click to collapse
Good news all! It looks like the boot issue and modem service failure is fixed. I installed it on my phone and it seems to be stable. Sorry for any/all frustration with the previous build. Hopefully all who have been waiting can use it now:
https://androidfilehost.com/?fid=11410963190603877722
calsurferpunk said:
Good news all! It looks like the boot issue and modem service failure is fixed. I installed it on my phone and it seems to be stable. Sorry for any/all frustration with the previous build. Hopefully all who have been waiting can use it now:
https://androidfilehost.com/?fid=11410963190603877722
Click to expand...
Click to collapse
Thanks a bunch! Flashing now!
Currently using a Pixel 2 XL, can't seem to complete the Android Setup. The app keeps crashing after I connect to WiFi and click continue, does anyone have some advice?
tranna said:
Currently using a Pixel 2 XL, can't seem to complete the Android Setup. The app keeps crashing after I connect to WiFi and click continue, does anyone have some advice?
Click to expand...
Click to collapse
Could try flashing a different gapps package. I always used the mini
tranna said:
Currently using a Pixel 2 XL, can't seem to complete the Android Setup. The app keeps crashing after I connect to WiFi and click continue, does anyone have some advice?
Click to expand...
Click to collapse
I think I went to app info and told it to force stop. If it's on the data transfer utility, I just told it to uninstall (as it seemed to be the culprit for me). I think I either reset/restarted or continued with the pixel setup after that. Either way, just getting to the data transfer utility from within setup or on the apps list and uninstalling it was the trick for me.
Trying this out today for the first time. WiFi calling isn't working, UK EE. Got google apps nano working but had to force quit the setup a few times. Otherwise its looking really nice, thanks!
Hi again all. I just wanted to let all of you who are using this ROM know that I'm planning on updating it very soon. I've been waiting for Google to release security patches for this month, but if I don't see them soon then I'll build with the latest Lineage OS changes anyhow.
On the 2nt or 3rd post is said to tap all for corners of the screen clockwise from top left and it will skip setup, then go into apps and uninstall the data transfer tool. When you do that it will let you move forward with the setup and still let you transfer anyway you want. Hope this helps.
It's amazing! I like it! Thank you so much
Hi again. Here's the latest build of the sources as of today:
https://androidfilehost.com/?fid=11410963190603892886
Something to note is that when I installed it, I simply went to recovery, flashed the new ROM .zip, then flashed the TWRP installation zip again. After that, I rebooted to recovery and installed Magisk again.
For some reason once I booted, the google play store was missing (even though previously having installed OpenGapps along with the previous ROM version). I went back to recovery, reflashed OpenGapps, and it was back again (along with having to go through setup once again, including removing the data transfer tool). Some of the apps (mostly Google's) wouldn't open correctly until I uninstalled and reinstalled them again). My Google account also wasn't present, so I had to add it back as well.
If you come across that same problem, these steps should work, otherwise you might want to just try a fresh install (wiping the old cache and data while in recovery). For anyone who comes up with an easier solution, could you please be sure to share what you did? Everything is still working fine afterwards, but it was just annoying to have to uninstall and add things back. I didn't use the latest OpenGapps, so that might have just been my problem.
I'm unable to complete the setup, since the setup always crashes after adding a google account. It will ask me if I want to select a backup from the cloud or skip, and any option I pick will crash the setup. As a result, Pixel Launcher will not work (maybe that's another issue entirely?) other than that, rom works.
Was wondering if anyone had had any problems with the now playing? I get a pixel ambient services keeps stopping when I ask the assistant but it will tell me the song name. But now playing seams to not work at all. I did try uninstalling the ambient services and reinstall it with no change.

Would this procedure work? (install magisk and twrp on 10.0.3.0)

First, let me say I have been using rooted phones with twrp for several years and never had the slightest problem with them, so I generally know what I am doing, but the Mi A2 Lite is just a disaster area for me, not with Magisk, that works fine, but twrp seems impossible for me to install on 10.0.3.0 without soft bricking ( I had twrp installed on 10.0.2.0 and 10.0.1.0 so I am not unfamiliar with the method, but on 10.0.3.0 - no way). I have done so many factory resets now I have my own parking space at the factory! (That is humour btw).
So I wondered if a different approach to the problem might work. I am not a coder or phone guru, so what I propose might be nonsense, if it is I am sure somebody will tell me.
We are all used to the concept of the 'patched_boot.img' created by Magisk and if you don't want to produce your own version the forum usually has a link to it. Magisk though is not the problem, twrp is, so what I am proposing is that somebody provides a link to a 'double_patched_boot.img' ie a flashable boot image that contains both twrp and magisk and that can directly replace the stock boot via fastboot.
Apparently there are some folks that have managed to install both twrp and magisk on 10.0.3.0, so if one of them could extract the 'double_patched_boot.img' from their phone it might help out a lot. How do you achieve that? Well there is probably more than one way, but the way that I would choose (if I could manage to install them both in the first place) is to boot into twrp, connect to pc, take a miflash backup of the phone and then unzip it with the following command (this is a linux command I am sure someone can provide a windows equivalent):
Code:
tar -xzf ********.tgz
where ********.tgz is the name of your miflash backup.
Then extract the boot.img from the resulting folder, rename it to something like 'double_patched_boot_10.0.3.0.img' and provide a link to it on the forum. Then some brave soul could try it out (probably not me as I am sick of doing factory resets and don't have any backups because I don't have any recovery to make them from).
OTOH this might just not be practical, I don't know enough to be sure.
i was having similar issues. replaced my mi a2 lite and followed the guide for the aosp 109 gsi here in the forum replacing the fstab and one other file i forgot they name but it's instructed. i have twrp zero the fixed one, magisk, and I'm running the RR PIE ROM with zero issues and I've been back and forth in and out of recovery no problem. I'm pretty sure it will work for you too.
12:121390 said:
i was having similar issues. replaced my mi a2 lite and followed the guide for the aosp 109 gsi here in the forum replacing the fstab and one other file i forgot they name but it's instructed. i have twrp zero the fixed one, magisk, and I'm running the RR PIE ROM with zero issues and I've been back and forth in and out of recovery no problem. I'm pretty sure it will work for you too.
Click to expand...
Click to collapse
Interesting. I have certainly thought of jumping ship to a custom rom, but I would like to wait a little before I do so, ideally until someone fires up a Lineage rom for the A2 Lite. But if things continue as badly as they have done so far with stock roms then I might well join you on RR.
viking777 said:
Interesting. I have certainly thought of jumping ship to a custom rom, but I would like to wait a little before I do so, ideally until someone fires up a Lineage rom for the A2 Lite. But if things continue as badly as they have done so far with stock roms then I might well join you on RR.
Click to expand...
Click to collapse
also because of the new ARB thing, custom is much safer, i think i bricked my last device rolling back from ota 9.0 software to ota 8.1. that's a non-issue with custom. just something to be wary of. the current RR pie gsi is near flawless for he so far. hope that helps a little
12:121390 said:
also because of the new ARB thing, custom is much safer, i think i bricked my last device rolling back from ota 9.0 software to ota 8.1. that's a non-issue with custom. just something to be wary of. the current RR pie gsi is near flawless for he so far. hope that helps a little
Click to expand...
Click to collapse
Anti roll back is disabled and not an issue if bootloader is unlocked
Nice thread. Tried it as well but no chance 10.0.3.00 + twrp + magisk. And you are right the problem is twrp.
Sent from my Phh-Treble vanilla using Tapatalk
12:121390 said:
i was having similar issues. replaced my mi a2 lite and followed the guide for the aosp 109 gsi here in the forum replacing the fstab and one other file i forgot they name but it's instructed. i have twrp zero the fixed one, magisk, and I'm running the RR PIE ROM with zero issues and I've been back and forth in and out of recovery no problem. I'm pretty sure it will work for you too.
Click to expand...
Click to collapse
Does RR Pie have any issues on Mi A2 Lite? Whichever GSI I'd tried, I had lags :/
12:121390 said:
i was having similar issues. replaced my mi a2 lite and followed the guide for the aosp 109 gsi here in the forum replacing the fstab and one other file i forgot they name but it's instructed. i have twrp zero the fixed one, magisk, and I'm running the RR PIE ROM with zero issues and I've been back and forth in and out of recovery no problem. I'm pretty sure it will work for you too.
Click to expand...
Click to collapse
brother i also want to install RR PIE Rom can you please give me the guide link?
hossman said:
Anti roll back is disabled and not an issue if bootloader is unlocked
Click to expand...
Click to collapse
correct it is not. what happened was.. lol. i thought i was crafty and did some file swapping and made miflash setups that would flash so the stock files as usual , but with gsi's like RR and/or bootleggers for the system image. and it works, up until i flashed from RR to bootleggers with those setups described previously . there is where my genius was flawed. lol. lesson learned
---------- Post added at 06:43 AM ---------- Previous post was at 06:38 AM ----------
marstonpear said:
Does RR Pie have any issues on Mi A2 Lite? Whichever GSI I'd tried, I had lags :/
Click to expand...
Click to collapse
for me, i have not come across anything caused by the GSI. any issues I've faced are purely self inflicted.
I don´t get your problems... Just boot twrp, and install it as described in original thread.
After that flash back aboot from 9.6.11.0 and the message "your system got destroyed" will disappear!
Voodoojonny said:
I don´t get your problems... Just boot twrp, and install it as described in original thread.
After that flash back aboot from 9.6.11.0 and the message "your system got destroyed" will disappear!
Click to expand...
Click to collapse
You might not get my problem, but likewise I don't get your solution. Firstly aboot has never been touched during the attempted twrp install so why flash it at all, it has not been changed, and secondly you suggest I flash it with something that is how many versions old 4?, 5?, I'm not sure, when just about every post you ever read stresses that you should not mix old and new partitions at the same time.
I hope you forgive my scepticism, but can you actually suggest the slightest reason why this might work?
Or is it all just voodoo johnny (sorry, couldn't resist that).
viking777 said:
You might not get my problem, but likewise I don't get your solution. Firstly aboot has never been touched during the attempted twrp install so why flash it at all, it has not been changed, and secondly you suggest I flash it with something that is how many versions old 4?, 5?, I'm not sure, when just about every post you ever read stresses that you should not mix old and new partitions at the same time.
I hope you forgive my scepticism, but can you actually suggest the slightest reason why this might work?
Or is it all just voodoo johnny (sorry, couldn't resist that).
Click to expand...
Click to collapse
Aboot is the bootloader. Since Pie the aboot was modified to check wheather there are modification on your boot.img. So everytime you modify something (like installing twrp), you get the message "your system got destroyed".
9.6.11.0 is the last version of Oreo. Here the bootloader didn´t check boot.img.
That´s why you need to flash 9.6.11.0 - maybe the older verstions will work too. Didn´t check. But I guess only 9.6.11.0 will work becouse it was the latest oreo version and it had to have a bootloader which can boot up pie (to have ota working).
Here you can find the aboot.img I use... and which works without any problem on pie - right now I´m running 10.0.3.0...
Just flash it via fastboot.
Voodoojonny said:
Aboot is the bootloader. Since Pie the aboot was modified to check wheather there are modification on your boot.img. So everytime you modify something (like installing twrp), you get the message "your system got destroyed".
9.6.11.0 is the last version of Oreo. Here the bootloader didn´t check boot.img.
That´s why you need to flash 9.6.11.0 - maybe the older verstions will work too. Didn´t check. But I guess only 9.6.11.0 will work becouse it was the latest oreo version and it had to have a bootloader which can boot up pie (to have ota working).
Here you can find the aboot.img I use... and which works without any problem on pie - right now I´m running 10.0.3.0...
Just flash it via fastboot.
Click to expand...
Click to collapse
OK that makes sense now - thank you for the explanation. I will probably give that a try sometime, but not right now as I have a stable working phone for the first time in ages and I don't want to jeopardise that.
Just one question though. When I had twrp installed on 10.0.2.0, it was fine at doing backups, but on the two occasions I tried to restore with them they failed, by which I don't mean that the restore didn't repair the phone, but that it was impossible to even carry out the restore, it started but did not complete - just ended with 'Restore Failed' message.
Have you tried any restores with twrp installed in the manner you suggest and if so did they work? No point in installing it otherwise.
viking777 said:
OK that makes sense now - thank you for the explanation. I will probably give that a try sometime, but not right now as I have a stable working phone for the first time in ages and I don't want to jeopardise that.
Just one question though. When I had twrp installed on 10.0.2.0, it was fine at doing backups, but on the two occasions I tried to restore with them they failed, by which I don't mean that the restore didn't repair the phone, but that it was impossible to even carry out the restore, it started but did not complete - just ended with 'Restore Failed' message.
Have you tried any restores with twrp installed in the manner you suggest and if so did they work? No point in installing it otherwise.
Click to expand...
Click to collapse
There seems to be some bugs restoring system and vendor... Some users talked about... I usually only save and restore the data and boot partition and I never had any problems with that. For all other partitions you can use miflash or fastboot...
Yeah all my twrp full backups don't work after a fresh stock installment either, that's very annoying.
The twrp version for daisy is bugged. Backups are not working, the wifi with GSI Roms on pie stock is not working anymore as soon as twrp is installed as well.
Sent from my Phh-Treble vanilla using Tapatalk
Thanks for the replies above. @voodoojohnny
In my case it was the data partition that caused the restore to fail, vendor and system and boot all seemed to go through normally. @cd492
Based on what you say along with my own experiences and those of voovoojohnny, it looks like twrp is more trouble than it is worth at the moment. I think I will make do without it for now and hope for a better version in the future.
viking777 said:
First, let me say I have been using rooted phones with twrp for several years and never had the slightest problem with them, so I generally know what I am doing, but the Mi A2 Lite is just a disaster area for me, not with Magisk, that works fine, but twrp seems impossible for me to install on 10.0.3.0 without soft bricking ( I had twrp installed on 10.0.2.0 and 10.0.1.0 so I am not unfamiliar with the method, but on 10.0.3.0 - no way). I have done so many factory resets now I have my own parking space at the factory! (That is humour btw).
So I wondered if a different approach to the problem might work. I am not a coder or phone guru, so what I propose might be nonsense, if it is I am sure somebody will tell me.
We are all used to the concept of the 'patched_boot.img' created by Magisk and if you don't want to produce your own version the forum usually has a link to it. Magisk though is not the problem, twrp is, so what I am proposing is that somebody provides a link to a 'double_patched_boot.img' ie a flashable boot image that contains both twrp and magisk and that can directly replace the stock boot via fastboot.
Apparently there are some folks that have managed to install both twrp and magisk on 10.0.3.0, so if one of them could extract the 'double_patched_boot.img' from their phone it might help out a lot. How do you achieve that? Well there is probably more than one way, but the way that I would choose (if I could manage to install them both in the first place) is to boot into twrp, connect to pc, take a miflash backup of the phone and then unzip it with the following command (this is a linux command I am sure someone can provide a windows equivalent):
where ********.tgz is the name of your miflash backup.
Then extract the boot.img from the resulting folder, rename it to something like 'double_patched_boot_10.0.3.0.img' and provide a link to it on the forum. Then some brave soul could try it out (probably not me as I am sick of doing factory resets and don't have any backups because I don't have any recovery to make them from).
OTOH this might just not be practical, I don't know enough to be sure.
Click to expand...
Click to collapse
THIS HAS NOT BEEN TESTED ON GSI'S YET
I'm currently in the process of RR with TWRP but having extreme Encryption errors
Grab these two files (Big Thanks to Zerovoid, Seryioo, and mac12m99)
Fixed SDCard Support TWRP Image File (Put this on your SDCard and Computer)-
https://forum.xda-developers.com/mi...unofficial-twrp-daisy-mount-sd-fixed-t3889390
Fixed SDCard Support TWRP Installer Zip (Put this on your SDCard)-
https://androidfilehost.com/?fid=11410963190603893418
But I got TWRP on 10.0.3.0 with magisk, and Justic Kernel.
THIS WILL WIPE YOUR DEVICE I'M DEFINITELY NOT RESPONSIBLE FOR LOST DATA
Start with the phone being on with USB Debugging enabled correctly
Type adb reboot bootloader
So flash the 10.0.3.0 ROM through MiFlash using the flash_all.bat, this process has to be done so backup your data before erasing.
After it is done flashing it restarts, go ahead and hold power and volume down right back to the Bootloader
Type: fastboot boot twrp-3.2.3-0-daisy_zero.img
It would boot into TWRP, if you see something about decryption hit cancel this may mean you haven't followed directions so far
Tap install and find your SD Card, find the fixed-twrp-installer-daisy.zip where ever you put it on your SD Card and install it, this process takes a few minutes when finished DO NOT HIT REBOOT SYSTEM!
Hit the home button back to TWRP home screen and tap reboot >>> bootloader
Download this to your computer - https://androidfilehost.com/?fid=11410963190603884024
Type: fastboot flash aboot aboot_9.6.4.img
Then type: fastboot reboot
Afterwards your phone shall boot up to Android if it does hold power and volume up and release power and keep hold volume up when the screen turns back on to go-to recovery, if TWRP boots up you have successfully completed the task.
Now flash Magisk zip (optional)
Hopefully this helped kind of my first tutorial, this was my process.
InfinityXDA said:
THIS HAS NOT BEEN TESTED ON GSI'S YET
I'm currently in the process of RR with TWRP but having extreme Encryption errors
Grab these two files (Big Thanks to Zerovoid, Seryioo, and mac12m99)
Fixed SDCard Support TWRP Image File (Put this on your SDCard and Computer)-
https://forum.xda-developers.com/mi...unofficial-twrp-daisy-mount-sd-fixed-t3889390
Fixed SDCard Support TWRP Installer Zip (Put this on your SDCard)-
https://androidfilehost.com/?fid=11410963190603893418
But I got TWRP on 10.0.3.0 with magisk, and Justic Kernel.
THIS WILL WIPE YOUR DEVICE I'M DEFINITELY NOT RESPONSIBLE FOR LOST DATA
Start with the phone being on with USB Debugging enabled correctly
Type adb reboot bootloader
So flash the 10.0.3.0 ROM through MiFlash using the flash_all.bat, this process has to be done so backup your data before erasing.
After it is done flashing it restarts, go ahead and hold power and volume down right back to the Bootloader
Type: fastboot boot twrp-3.2.3-0-daisy_zero.img
It would boot into TWRP, if you see something about decryption hit cancel this may mean you haven't followed directions so far
Tap install and find your SD Card, find the fixed-twrp-installer-daisy.zip where ever you put it on your SD Card and install it, this process takes a few minutes when finished DO NOT HIT REBOOT SYSTEM!
Hit the home button back to TWRP home screen and tap reboot >>> bootloader
Download this to your computer - https://androidfilehost.com/?fid=11410963190603884024
Type: fastboot flash aboot aboot_9.6.4.img
Then type: fastboot reboot
Afterwards your phone shall boot up to Android if it does hold power and volume up and release power and keep hold volume up when the screen turns back on to go-to recovery, if TWRP boots up you have successfully completed the task.
Now flash Magisk zip (optional)
Hopefully this helped kind of my first tutorial, this was my process.
Click to expand...
Click to collapse
Thank you very much for posting this process in such detail, unfortunately I think you must have missed my last post where I said:
it looks like twrp is more trouble than it is worth at the moment. I think I will make do without it for now and hope for a better version in the future.
Click to expand...
Click to collapse
I meant it, at least for now, but maybe your post will help somebody else.
viking777 said:
Thank you very much for posting this process in such detail, unfortunately I think you must have missed my last post where I said:
I meant it, at least for now, but maybe your post will help somebody else.
Click to expand...
Click to collapse
Yes I didn't see that post but understand I didn't give you links to the official TWRP, I gave you the unofficial fixed TWRP which actually features SD Card Support and trust me it works completely fine I haven't had a problem yet. This took me hours upon hours to figure out what I was doing wrong.
The only specific reason you are not successfully getting TWRP is because you didn't flash the aboot.img after installing the zip.
I hope this helps you in the future!
thanks InfinityXDA for the tutorial, you should create a post just for it~

[OFFICIAL] LineageOS 18.1 for the Moto G7

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Moto G7
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 18.1 thread for the Moto G7.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
river
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
None.
Find any? Report them according to this guide.
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
Kernel Source: https://github.com/LineageOS/android_kernel_motorola_sdm632

			
				
I've heard that some people, including myself, have had issues with upgrading to 18.1 on some devices because it results in a broken lock screen. Is this an issue with 18.1 on the G7? I just want to make sure before I upgrade.
NTGDeveloper said:
I've heard that some people, including myself, have had issues with upgrading to 18.1 on some devices because it results in a broken lock screen. Is this an issue with 18.1 on the G7? I just want to make sure before I upgrade.
Click to expand...
Click to collapse
In my case, at the moment it is working well, I am still testing it.
You should try to report the bug:
"Find any? Report them according to this guide"
NTGDeveloper said:
I've heard that some people, including myself, have had issues with upgrading to 18.1 on some devices because it results in a broken lock screen. Is this an issue with 18.1 on the G7? I just want to make sure before I upgrade.
Click to expand...
Click to collapse
Only on really really old devices like bacon , etc.
npjohnson said:
Only on really really old devices like bacon , etc.
Click to expand...
Click to collapse
Thanks for letting me know. I decided to go with a clean flash anyway just because I think my encryption on my data partition was preventing boot and restoring from a 17.1 nandroid backup broke the system completely. So far, the ROM is very good and I'm happy that I'm now on Android 11!
I flashed this the other night and the ROM seems to be working well. I have a question about updating the Lineage OS recovery though. I am used to flashing via TWRP, but decided to go with the Lineage OS recovery this time. In TWRP if I want to update TWRP itself, I would download the twrp-XYZ-123.img to the device, and flash the image in TWRP. I cannot see this option anywhere in the Lineage Recovery UI. Do I have to do it in ADB like the initial install of the ROM? Is there another way to update the recovery? Is it even necessary to do the recovery update (I can't find a changelog for the Lineage OS Recovery on the lineage site), I don't want to bother with an ADB recovery flash every week if nothing is actually changing in the recovery image.
PMDPhD said:
I flashed this the other night and the ROM seems to be working well. I have a question about updating the Lineage OS recovery though. I am used to flashing via TWRP, but decided to go with the Lineage OS recovery this time. In TWRP if I want to update TWRP itself, I would download the twrp-XYZ-123.img to the device, and flash the image in TWRP. I cannot see this option anywhere in the Lineage Recovery UI. Do I have to do it in ADB like the initial install of the ROM? Is there another way to update the recovery? Is it even necessary to do the recovery update (I can't find a changelog for the Lineage OS Recovery on the lineage site), I don't want to bother with an ADB recovery flash every week if nothing is actually changing in the recovery image.
Click to expand...
Click to collapse
Why aren't you using the .zip? Because the linage recovery doesn't do .IMG files I would guess. The .zip is on the twrp , also the .zip can be flashed with magisk
One thing I'm starting to hate about 18.1 is they dropped the option to Kill App by holding back button in developer settings. This may actually be a deal breaker for me, I dont think I can make it without this feature.. Shiat!
Droid4200 said:
Why aren't you using the .zip? Because the linage recovery doesn't do .IMG files I would guess. The .zip is on the twrp , also the .zip can be flashed with magisk
Click to expand...
Click to collapse
I am very new to Lineage OS Recovery. Always used the .IMG files with TWRP. I don't know how to flash a recovery in Lineage Recovery at all, and could not find any instructions anywhere. I did not know I could flash a recovery as a .Zip. I also just realized that my initial question is kind of moot because there is an option in the built in updater in Lineage OS 18.1 to flash both the update and recovery, so my Lineage OS Recovery is already the latest version from 4-4-21, and I won't have to figure out how to flash it. Though it would be useful to know in general.
PMDPhD said:
I am very new to Lineage OS Recovery. Always used the .IMG files with TWRP. I don't know how to flash a recovery in Lineage Recovery at all, and could not find any instructions anywhere. I did not know I could flash a recovery as a .Zip. I also just realized that my initial question is kind of moot because there is an option in the built in updater in Lineage OS 18.1 to flash both the update and recovery, so my Lineage OS Recovery is already the latest version from 4-4-21, and I won't have to figure out how to flash it. Though it would be useful to know in general.
Click to expand...
Click to collapse
Yes the zip makes it so much easier now. If you use the lineageos built in update process you will lose TWRP, download the zip and you can very quicky just reboot to recovery after a lineageos update, then install the twrp.zip . you will lose root so you just reinstall majisk(if you use majisk, it'll keep your modules and settings). There may be a twrp retain script, but I haven't messed with them yet, the reinstall of twrp and majisk is pretty fast (plus I'm used to doing it the old way, sort of like you with the .IMG)
Mostly seems pretty good. Broke "LawnChair2" launcher, but, that seems to be a problem of LawnChair going dormant; Hyperion is working o-k so far as a replacement, with some hassles converting. The OK Google voice activation for Assistant still doesn't work and I can't find any fixes, but that was true on 17.1 also. I *hate* the zooming wallpaper effect, makes it very hard to exactly position wallpaper vs. icons. That is an Android 11 "feature" though, so no getting around it...
Hi there. I upgraded 17.1 to 18.1 recently. Seems working fine on first day until I installed vanced app (i think).
Now, every time the screen go off and when it back on, i see glitches and bad palette color. And can't fix it without a reboot (and then when the screen go off the screen glitches comes back)
Maybe is related with Vanced and microG, any one has this issue too?
TomOehser said:
Mostly seems pretty good. Broke "LawnChair2" launcher, but, that seems to be a problem of LawnChair going dormant; Hyperion is working o-k so far as a replacement, with some hassles converting. The OK Google voice activation for Assistant still doesn't work and I can't find any fixes, but that was true on 17.1 also. I *hate* the zooming wallpaper effect, makes it very hard to exactly position wallpaper vs. icons. That is an Android 11 "feature" though, so no getting around it...
Click to expand...
Click to collapse
New issue - seems I get into a situation where the notification light and a notification sound are coming without any notifications - even if "use notification light" is disabled... mystified at what is doing this so far, trying to figure it out. Also, Lawnchair mysteriously seems to be working...
FoxShadow said:
Hi there. I upgraded 17.1 to 18.1 recently. Seems working fine on first day until I installed vanced app (i think).
Now, every time the screen go off and when it back on, i see glitches and bad palette color. And can't fix it without a reboot (and then when the screen go off the screen glitches comes back)
Maybe is related with Vanced and microG, any one has this issue too?
Click to expand...
Click to collapse
The display glitches with the messed up color palette might be the same bug from 17.1. To fix that I had to change the Color mode from Saturated to Boosted and it stopped.
Settings > Display > Advanced > Color
Might be a different path in Android 11, though.
Basically if the inverted color thing happens again, going to that setting and switch it to a different Color type will reset the colors back to normal without restarting. After doing that once or twice it hasn't happened after. Again, on 17.1, can't speak to 18.1 yet.
Working fine after a week of daily use. Upgrade from 17.1 was simple by following the instructions.
The only issue I had was with Magisk. When I installed version 22.0 after upgrading successfully to 18.1, the device would get stuck on the LineageOS boot logo. After removing all modules using adb ("adb wait-for-device shell magisk --remove-modules", then boot the device), things got back to normal. Reinstalling the modules in Magisk did not create any more issues.
Overall, a very good ROM. Thanks for the effort of creating and maintaining it.
I have an issue with "Do Not Disturb" schedules not turning off. They turn on fine but are still running the following day after the supposed end-time. I'm getting round it with Tasker, so it's not a big deal.
Thanks for maintaining the ROM and updating to version 11.
PMDPhD said:
I flashed this the other night and the ROM seems to be working well. I have a question about updating the Lineage OS recovery though. I am used to flashing via TWRP, but decided to go with the Lineage OS recovery this time. In TWRP if I want to update TWRP itself, I would download the twrp-XYZ-123.img to the device, and flash the image in TWRP. I cannot see this option anywhere in the Lineage Recovery UI. Do I have to do it in ADB like the initial install of the ROM? Is there another way to update the recovery? Is it even necessary to do the recovery update (I can't find a changelog for the Lineage OS Recovery on the lineage site), I don't want to bother with an ADB recovery flash every week if nothing is actually changing in the recovery image.
Click to expand...
Click to collapse
much easier - Updater app in Settings, three dot menu, "Update recovery alongside OS"
kelue said:
The display glitches with the messed up color palette might be the same bug from 17.1. To fix that I had to change the Color mode from Saturated to Boosted and it stopped.
Settings > Display > Advanced > Color
Might be a different path in Android 11, though.
Basically if the inverted color thing happens again, going to that setting and switch it to a different Color type will reset the colors back to normal without restarting. After doing that once or twice it hasn't happened after. Again, on 17.1, can't speak to 18.1 yet.
Click to expand...
Click to collapse
Thank you! I will try that next time. I had to go back to 17.1 by now, that never happend to me on 17.1
FoxShadow said:
Thank you! I will try that next time. I had to go back to 17.1 by now, that never happend to me on 17.1
Click to expand...
Click to collapse
For me, if it happens, it happens shortly after booting, then a quick reset by changing the color setting will fix it, and it won't happen again until the next reboot. I noticed it happen once after plugging the charger in a minute or so after boot so maybe it's hardware related, I don't know.

Messed up TWRP - stuck on decrypting

So, recently, my Magisk stopped working. I thought I fixed it with seveal steps, including updating Magisk and TWRP, and it worked fine at first, but after one of restarts TWRP started requesting encryption password and doesn't boot into system. Entering system pass/pin doesn't let me into TWRP either, it's stuck on "Attempting to decrypt FBE for User 0".
I haven't done anything related to flashing in 1.5 year so I'm kind of lost now. What would be the best way to recover from this without losing any data? I assume some ADB actions, but what do I need to do exactly?
One more note that I thought was irrelevant: I installed Viper in Magisk. Didn't expect such patch could do this, but after some googling I found 2 people having simila issue afte installing that. Please help! Would replacing boot image to MIUI's help in that case?
Try flashing stock boot image then. Google it
That does not help. If it was as easy as googling I'd have it fixed a long time ago. I don't want to lose any data, to remind. But tried flashing original boot.img as it doesn't mes with data and it didn't halp. Any othe ideas?
EDIT: ok, after desperately flashing back both TWRP and boot.img repeatedly and trying to get into TWRP it somehow did something and I got into the system at least to do some fresh backups with Titanium and potentially other apps. I have no clue how to proceed though as I need Magisk to work. Well, the first thing will be to ty to uninstall Viper. But not sure it was the cause in the first place and I'm too afraid to restart. Any clues on what may be the culpit and how to poceed in the safest way?
EDIT2: nvm, ofc I can't really do a full backup using Titanium since Magisk got disabled after flashing original boot.img. Neither uninstall the Viper module. So even more not sure what to do now. Would temporarily disabling the password help?
EDIT3: "google it" type of advice forced me to brick even further as trying to install Magisk/dm-verity now ended up with bootloop. Also, interestingly, older TWRP doesn't have this decyption issue, more info: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1610
"Decryption issue", eh. I bet you are using 12.0.7/12.0.8/12.5.1. Some folk at Xiaomi decides to do a different approach on encryption, rendering encryption issue. This issue has been solved in a newer version of TWRP except for 12.5.1. But do tell me your current MIUI version.
Use MiFlash to flash your CURRENT version of MIUI (or something above or below, I don't care. Just don't downgrade from 12.0.7, you'll face even more headaches) with "Flash all except data" command. Your device will fine, your data will also intact. I've done this dozen of times.
Another piece of advice: don't carry over your magisk module if you're planning to install a stock boot. Install everything freshly.
Destroy666x said:
That does not help. If it was as easy as googling I'd have it fixed a long time ago. I don't want to lose any data, to remind. But tried flashing original boot.img as it doesn't mes with data and it didn't halp. Any othe ideas?
EDIT: ok, after desperately flashing back both TWRP and boot.img repeatedly and trying to get into TWRP it somehow did something and I got into the system at least to do some fresh backups with Titanium and potentially other apps. I have no clue how to proceed though as I need Magisk to work. Well, the first thing will be to ty to uninstall Viper. But not sure it was the cause in the first place and I'm too afraid to restart. Any clues on what may be the culpit and how to poceed in the safest way?
EDIT2: nvm, ofc I can't really do a full backup using Titanium since Magisk got disabled after flashing original boot.img. Neither uninstall the Viper module. So even more not sure what to do now. Would temporarily disabling the password help?
EDIT3: "google it" type of advice forced me to brick even further as trying to install Magisk/dm-verity now ended up with bootloop. Also, interestingly, older TWRP doesn't have this decyption issue, more info: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1610
Click to expand...
Click to collapse
Sorry, I apologize for that
kekesed97 said:
"Decryption issue", eh. I bet you are using 12.0.7/12.0.8/12.5.1. Some folk at Xiaomi decides to do a different approach on encryption, rendering encryption issue. This issue has been solved in a newer version of TWRP except for 12.5.1. But do tell me your current MIUI version.
Use MiFlash to flash your CURRENT version of MIUI (or something above or below, I don't care. Just don't downgrade from 12.0.7, you'll face even more headaches) with "Flash all except data" command. Your device will fine, your data will also intact. I've done this dozen of times.
Another piece of advice: don't carry over your magisk module if you're planning to install a stock boot. Install everything freshly.
Click to expand...
Click to collapse
Thanks for reply. MIUI 11.0.6.0. Thinking about upgrading to 12 but won't that lose data? I read that flashing ROMs in general results in data loss, does flashing current one differ because it's basically the same system? And I guess because of that option. Do I need MiFlash for it or is that also available in any othe tool?
Also, to make sure we undestand data in the same way, by data I mean the following:
- app data, obvious
- app permissions, annoying to set up if lost as I have lots of apps
- notification settings, similarly as above
- other system settings, not as annoying but still some work
Would love to keep all of these.
Destroy666x said:
Thanks for reply. MIUI 11.0.6.0. Thinking about upgrading to 12 but won't that lose data? I read that flashing ROMs in general results in data loss, does flashing current one differ because it's basically the same system? And I guess because of that option. Do I need MiFlash for it or is that also available in any othe tool?
Click to expand...
Click to collapse
Official upgrades won't lose your data (dirty flashable, as the name suggest "update"). In that case, use fastboot upgrade. I will recommend to hold to somewhere in 12.0.5 or 12.0.6, because if you messed up something, you can still downgrade to many versions, maybe up to initial version?
I did many downgrades before because I have tripped AVB many times, something like <newer A10 version available> -> installed magisk and TWRP -> AVB tripped -> <some A9 MIUI via miflash> -> fastboot update via mi flash pro to <same newer A10 version available> -> rinse and repeat until I got a stable system. Without costing any data. But with headaches, indeed.
Mi Flash is also another option. Make sure you choose the "flash_all_except_data". Or else, more unnecessary headaches.
Destroy666x said:
Also, to make sure we undestand data in the same way, by data I mean the following:
- app data, obvious
- app permissions, annoying to set up if lost as I have lots of apps
- notification settings, similarly as above
- other system settings, not as annoying but still some work
Would love to keep all of these.
Click to expand...
Click to collapse
1. App and app data will stay
2. I guess app permission is also stay. But do confirm, since I never had any issue except when I enable/disable MIUI optimizations
3. Personalization will stay
kekesed97 said:
fastboot upgrade
Click to expand...
Click to collapse
Could you be more specific what this exactly means and how to do it without reflashing data? Googling this results in many unrelated to eachother things.
Asking because I had poblems wih Mi Flash before, so would be great to have a reliable alternative just in case.
Destroy666x said:
Could you be more specific what this exactly means and how to do it without reflashing data? Googling this results in many unrelated to eachother things.
Asking because I had poblems wih Mi Flash before, so would be great to have a reliable alternative just in case.
Click to expand...
Click to collapse
Oopsie! Swapped fastboot with recovery rom, ehehe.
Use recovery rom (the 2 gb one). This will require stock boot, stock recovery, mi account, and internet connection. Flashing is done via MiFlash Pro (Just click that "Flash in Recovery" botton or go to recovery tab).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Figure 1: Mi Flash Pro main interface
Or use Mi Flash by loading fastboot rom (the 4gb one) to Mi Flash, and select "flash_all_except_data".
Figure 2: Mi Flash with "flash_all_except_data" enabled
Oh ok, I see, recovery ROM, downloadable easily from MIUI website, is something you upload though recovery and fastboot ROM through fastboot/MiFlash. Found them here https://c.mi.com/oc/miuidownload/detail?guide=2 along with MiFlash 2020 version (is this the latest version?) but how do I find older ROM versions, e.g. my 11.0.6.0? The MIUI website seems to be a total mess, honestly. And I don't trust random Google results, bunch of them seem like virus traps redirecing to Mediafire and similar upload websites.
Is this also the official MiFlash Pro website? https://miflashpro.com/
EDIT: yes, it seems, also found https://xiaomiflashtool.com/ for the other app's latest version
Here for a streamlined versions or here if you need betas
Mi flash is included in mi flash pro if you want all in one solution. It also have miui downloader embedded
Ok thanks. Now I wanted to backup data through older TWRP 3.3.1 that decrypts correctly, just in case, but it fails because it can't copy `/data/misc_ce/10`:
Code:
I:Error adding file '/data/misc_ce/10' to '/external_sd/TWRP/BACKUPS/mfaajbdu5s79pfhy/2021-07-28--04-07-40_PPR1180610011/data.ext4.win007'
Error creating backup.
I:ERROR tarList for thread ID 0
Any clue what this folder is about and how to get around this? Any other way to backup with this level of access?
From what I see it's something about additional user, maybe from the MIUI functionality, but 0 clue if deleting this is safe.
Destroy666x said:
Ok thanks. Now I wanted to backup data through older TWRP 3.3.1 that decrypts correctly, just in case, but it fails because it can't copy `/data/misc_ce/10`:
Code:
I:Error adding file '/data/misc_ce/10' to '/external_sd/TWRP/BACKUPS/mfaajbdu5s79pfhy/2021-07-28--04-07-40_PPR1180610011/data.ext4.win007'
Error creating backup.
I:ERROR tarList for thread ID 0
Any clue what this folder is about and how to get around this? Any other way to backup with this level of access?
From what I see it's something about additional user, maybe from the MIUI functionality, but 0 clue if deleting this is safe.
Click to expand...
Click to collapse
No idea.
SP Flash tools have low level access to your device, including read back in the correct memory region.
kekesed97 said:
No idea.
SP Flash tools have low level access to your device, including read back in the correct memory region.
Click to expand...
Click to collapse
Fixed that: https://forum.xda-developers.com/t/...ils-because-of-data-misc_ce-10-error.4311899/ and have a backup.
Unfortunately, flashing the recovery ROM = still bootloop. Would flashing the fastboot one be any different if I choose to keep data? Would it flash someting extra?
I read that reading these logs may also help with debugging, but not sue what to look for.
Kernel log (/proc/lastkmsg): https://pastebin.com/T2xBBRvi - some error looking lines at the end, but non-comprehensible. Can I use them somehow futher?
dmesg log: https://ghostbin.com/paste/vyBDk - don't really see anything here, but it's quite long and not sure what to look for
logcat: https://ghostbin.com/paste/PSh7f - lots of "avc" errors
EDIT: well, I tried the fastboot one too, recovery got replaced with stock is the only diffeence I noticed, So I guess that means the data is 100% corrupt and the culprit. How would installing Magisk and the dm-verity/forceencypt zip corrupt the data though? Since that's the only thing I did before he bootloop started happening. Does dm-verity/forceencrypt even affect data? I think Magisk does, but this is really weird anyways. Maybe when I tried to install it on the TWRP with broken encryption it caused some file system failure? Does anyone know which /data dirs does the Magisk zip mess with? Maybe deleting those would help
EDIT2: ran Magisk as uninstall.zip in back installed TWRP 3.3.1, which apparently deletes its data files, but nope, didn't do anything.
I'm sorry I don't have the knowledge to go deeper.

Development [ROM][UNOFFICIAL][raven/oriole/bluejay] LineageOS 20.0 for the Pixel 6 Pro/6/6a

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS 20.0 for the Pixel 6 Pro (raven), Pixel 6 (oriole), and Pixel 6a (bluejay).
Known issues:
NOTE: This is an early-stage build, and may not be the most stable. It's more stable than it was when I starting building.
The status bar is mis-aligned to the left by a few pixels, but this does not cause any usability issues, fortunately.
If you have issues receiving calls (i.e. calls go to voicemail often), flash stock, lock the bootloader, unlock it, and then flash my ROM. Relocking and unlocking usually fixes a corrupted baseband.
If you wish to pass SafetyNet, you may need MagiskHidePropsConfig with a stock fingerprint for your device. MHPC has the raven/oriole 12 (not 12L/13) fingerprints which may or may not work. Read updated section below
You tell me.
Passing SafetyNet/Play Integrity:
As an update, for some reason, this ROM only needs the Displax SafetyNet Fix and Shamiko (or DenyList) on top of Magisk in order to pass SafetyNet/Play Integrity, which is a nice bonus. While I daily drive a Pixel 7 (running my P7 Lineage build), Netflix shows in the Play Store with DSNF/Shamiko on oriole.
Flashing instructions:
Spoiler
Be sure you're on the latest stock 13 and have an unlocked bootloader. You may also be able to flash from GrapheneOS, CalyxOS, or another ROM.
Go into fastboot mode (turn off phone and then Power + Volume down)
Make sure you have the adb/fastboot tools
Run fastboot flash --slot all boot boot.img
Run fastboot flash --slot all vendor_boot vendor_boot.img
Boot into recovery
Press Factory Reset and confirm
Go to Apply Update -> Apply from ADB
Run adb sideload LOS_BUILD (Replace LOS_BUILD with your LOS ZIP file)
To add GApps, go to Advanced -> Reboot to Recovery -> Apply Update -> Apply from ADB
Run adb sideload GAPPS_BUILD (Replace GAPPS_BUILD with your GApps ZIP file, repeat this step if you want Magisk)
Press Reboot System Now
Download:
Pixel 6 Pro (raven)
Pixel 6 (oriole)
Pixel 6a (bluejay)
MindTheGApps
Sources:
Kernel
Device trees
Vendor
ChangeLog:
2022/11/18:
Yet again, new builds.
Update SafetyNet/Play Integrity section, apparently it's super easy to pass this check with my ROM, and I did nothing.
2022/11/10:
Long time, no see. I have a new build for oriole. Will upload raven and bluejay shortly. UPDATE: raven and bluejay are also uploaded.
A lot of stability issues are fixed, at least on oriole. Mainline LOS has made huge differences.
It should be usable as a daily driver, although I daily drive a Pixel 7 (which I will also build for, in another thread).
2022/10/23:
Okay, sorry for flip flopping, this ROM is not discontinued. The main reboot issue is gone. If you have issues coming from stock, try flashing GrapheneOS and then this LOS build.
New builds for oriole, raven and bluejay.
I am discontinuing this ROM, a lot of people had issues, so I decided to not continue public builds further. When LOS becomes more stable on raviole/bluejay, I may restart builds unless LOS becomes official by then.
2022/10/20:
New build, yay!
2022/10/14:
Rebuilt for bluejay/oriole/raven on a fresh tree. Some people have reported issues on the 20221013 build. If you had issues try my new 20221014 build. If you still have issues, I will probably "discontinue" this build.
2022/10/13:
Re-built, mainly for Pixel 6 Pro (raven) flashing issues)
Move from AFH to self-hosted mirror. AFH sucks, but I fortunately have symmetrical Gigabit at home.
2022/10/12:
Initial build
Reserved 2.
Reserved 3.
hey mate, unable to access the file to download it, screenshot below
Cheers
spyderr said:
hey mate, unable to access the file to download it, screenshot below
Cheers
View attachment 5733339
Click to expand...
Click to collapse
Try the new links. I accidentally gave the links for my use instead of public use. Sorry for this.
neelchauhan said:
Try the new links. I accidentally gave the links for my use instead of public use. Sorry for this.
Click to expand...
Click to collapse
No Dramas, thanks for your work.
The 20121012 zip will not open. The previous zips open.
taisau said:
The 20121012 zip will not open. The previous zips open.
Click to expand...
Click to collapse
Which one, raven, oriole, or bluejay?
neelchauhan said:
Which one, raven, oriole, or bluejay?
Click to expand...
Click to collapse
raven. the same problem from multiple download locations. also, the boot files result in boot loops, where the previous worked.
getting "adb sideload lineage-20.0-20221012-UNOFFICIAL-raven.zip
serving: 'lineage-20.0-20221012-UNOFFICIAL-raven.zip' (~0%) adb: failed to read command: No error" after getting the verification signature failure option.
Sorry for that. Try my new downloads.
They're not on AFH, since AFH is garbage. I am using my home Gigabit connection for the new downloads.
Also, if a USB 3.0 port is giving issues, try a USB 2.0 port on your computer
neelchauhan said:
Sorry for that. Try my new downloads.
They're not on AFH, since AFH is garbage. I am using my home Gigabit connection for the new downloads.
Also, if a USB 3.0 port is giving issues, try a USB 2.0 port on your computer
Click to expand...
Click to collapse
I usually go directly for the 2.0 port because 3.0 for whatever reason gives me an issue. And where are you hosting them? I can't see anything other than AFH
Edit: nvm I see it was updated will try again.
edit EDIT: Can confirm it is now flashing, AFH didn't have the 20221013 build and thats why i was having issues. thank you so much for bringing lineage 20! I feel giddy like a school girl flashing this! Brings me back to the days of cyanogenmod RIP.
EDIT EDIT EDIT: Can confirm device is boot looping, actually says device is corrupt and the recovery cant mount system for gapps so gapps fails. Thus upon just flashing with your steps and you keep pressing the power button, the device just hangs at the white google screen.
okay tried boot and vendor boot from rice droid and it did NOT says device was corrupted. however flashing gapps with lineage build 20222013 says cant mount system and fails to flash and then bootloops.
Twiggy000b said:
okay tried boot and vendor boot from rice droid and it did NOT says device was corrupted. however flashing gapps with lineage build 20222013 says cant mount system and fails to flash and then bootloops.
Click to expand...
Click to collapse
I've been here before.
First, go back to stock, upgrade to a beta build, and then back to the public build.
Then try flashing my ROM. You need my boot.img and vendor_boot.img, don't use the RiceDroid boot/vendor_boot since each ROM may be different.
Apparently multiple people are having issues, will ingestivate
I noticed a few people are having issues. Can you try going back to stock, flashing my boot.img and vendor_boot.img, a factory reset, and then flashing the ROM?
I forgot the factory reset step, my bad.
If that doesn't work, there is some help here on Reddit:
https://www.reddit.com/r/LineageOS/comments/u6g2w2
Basically what Reddit said is after booting LOS but before GApps, boot once, then go back to recovery, factory reset and flash GApps.
neelchauhan said:
I noticed a few people are having issues. Can you try going back to stock, flashing my boot.img and vendor_boot.img, a factory reset, and then flashing the ROM?
I forgot the factory reset step, my bad.
If that doesn't work, there is some help here on Reddit:
https://www.reddit.com/r/LineageOS/comments/u6g2w2
Basically what Reddit said is after booting LOS but before GApps, boot once, then go back to recovery, factory reset and flash GApps.
Click to expand...
Click to collapse
i have tried all the steps and still having the same issue.
Glad to see Lineage 20 on the 6 Pro. Will definitely flash when I am home from work Saturday and report back on how it goes. Hopefully these little glitches with flashing are ironed out by then. Thank you for this neelchauhan.
On the oriole build everything boots and sets up fine as long as I'm plugged to the computer. As soon as I unplug the phone reboots to recovery saying corrupt data and can't start system. This happened on the 12th and 13th builds
Sadly,
This site can’t be reached​mirror.neelc.org took too long to respond.

Categories

Resources