Related
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"
}
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.
Dear
I have a old tab 3 tablet, I can't get it update from 4.4.2 to latest available.
Is there also a method to backup the originel android version?
any steps how to to this and also how to upgrade? it will be my first time.
I googled first, found how to enable development settings, but I don't see the OEM unlock .
So I did not want to continue.
I hope to get some info.
Hi there,
So, I don't know about the backup, bc the apps wont run on LineageOS. Just save your data and flash it to a custom rom.
The tablet is years out of date, therefore no updates for the tab3.
The only option is to flash a custom ROM.
I just flashed my 5210 (tab3 10.1 WiFi Santos) with this version of LineageOS (latest available)
[ROM][GT-P52XX][UNOFFICIAL][7.1.2] LineageOS 14.1
Unofficial LineageOS 14.1 for Samsung Galaxy Tab 3 10.1 LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your...
forum.xda-developers.com
her this is just the manual for flashing your phone with Lineage OS
Before you need to do 2 other things.
1. First of all, unlock the bootloader
2. Then flash TWRP.
3. Then flash LineageOS
4. Root with magisk.
Before you start, save your data, everything will be wiped.
1. Unlock bootloader..... its easy. Go to settings-phone info, and tab 10 times onto BUILDNUMBER, to unlock DEVELOPER TOOLS.
Then go back to settings - developer tools, and activate USB DEBUGGING.
Then turn off the tab, and start it with
POWER & MINUS & HOME
THATS IT, YOU UNLOCKED THE BOOTLOADER.
You need this (unlock bootloader), to flash TWRP onto the phone, its like a BIOS, from where you are able to flash/wipe/mount etc .
The manual for "2. Flash TWRP" for the tab3 is here: http://forum.xda-developers.com/gal...covery-twrp-3-x-samsung-galaxy-tab-3-t3340938
After you managed to install TWRP, you can finally flash LineageOS & gapps&magisk. Just follow the step by step instructions in the first thread I linked.
A little advice from me.... Before you start anything doing on your phone, read all steps in the instructions, and download all files needed into a folder.
Also... read some of the pages after page1 and read also several of the last pages in both (!) threads (TWRP and LineageOS), to be aware of mistakes others have already done .
After being confident in which order to to things, and that you have all the files, you can give it a try.
its not a 30min run, if its your first time. Take your time, if you struggle, just repeat the last step, or watch out on XDA forum for the same mistake, and the workaround for the solution.
Sometimes its just, BC you forgot to wipe things in the exact order.
Its very important, that you have the correct LineageOS file (3 available for the tab3). If you are not sure, which model is yours, just install an info app like "Device Info HW". You will find the info there.
godspeed
edit: before I forget: if you managed this, have a look at the SWAP FILE thread. For me it was a little performance booster, even if the LineageOS is already much more fluid than the stock ROM.
Swap for Samsung Galaxy Tab 3 10.1 (GT-P5210)
DISCLAIMER: I AM NOT RESPONSIBLE FOR YOUR DEVICE OR ANYTHING THAT MIGHT OCCUR WHILE USING THIS TUTORIAL. TRY AT YOUR OWN RISK! Credits: [mbm] for teaching me this dd terminal method. As we all know, for what ever reason, Samsung decided to...
forum.xda-developers.com
Dear Karl
Thanks for quick reply.
About the backup I mean : If the upgrade fails , or if I want to go back to 4.4.2 original OS, bc I miss some functionality, I want to be able to put back the original OS.
I don’t need apps or data to work with upgraded version .
I have read very fast all you have send me , it seems I have to put some preparation in it.
I will plan this for another time.
So to understand : only possible to upgrade to android 7 using the lineageOs?
"So to understand : only possible to upgrade to android 7 using the lineageOs?"
Yes, because google stopped the update support for this model.
in other words, if you dont flash it with a newer rom than yours, you wont be able to use it, at least for surfing or movies, bc most apps wont run on android 4.
cheers
For the backup thing, just use the search funtction in the subforum of the tab3.
2. Then flash TWRP.
as I need this first, after tablet is in donwload mode,, I have read all the messages in this post
Can I use latest version twrp 3.4.0.3 ? as some have used this and works for them, I assume they also had a samsung tab 3 GT-P5210.
As in the second post, the version is still 3.0.2-0.
If I undertood correcly, I can choose how to flash TWRP, reading , googling, I think Odin will be easy for me on my windows laptop.
I hope I'm correct in undestanding so far?
I stil have to check the posts about things as sideload, , whatever that is, Gapps "X86 "or "arm"
and about what to do after flasing TWRP.
I understnd that : once TWRP is installed on my tablet, I have to prepare the custom rom using Odin, too, and connect tablet in downloadmode ? wil this not erase TWRP? hmm
Can I use latest version twrp 3.4.0.3 ? as some have used this and works for them, I assume they also had a samsung tab 3 GT-P5210.
--> nope. First install the TWRP from the thread (3.0.2-0 )
After you succesfully flashed the twrp, you can upgrade TWRP. I dont know why, but thats the way...
Yes, i flashed twrp via odin on win7. Win10 may be buggy, i have read it in some threads.
You dont really need sideload, you just need to copy all things you want ro flash/install on a sdCard and plug into tab. You just "install" the OS and Gapps (and magisk) via TWRP.
The "x86" and "arm" thing is just a warning, to choose the correct hardware-version of Gapps (GoogleApps - its the google in several different variants, just choose the version you like/need....i dont want google, so i didnt install)
In one post, i mentioned a hardware info app. in this app, you can see which exactly hardware you have. if you know which hardware, you can choose the correct Gapps.
yes, after installing TWRP, you install LineageCustomRom and GAPPs, but not via odin, just via TWRP.
when flashing TWRP is succesfull via ODIN, the mobile restarts automatically. You need to be fast, for pressing (power & plus & home).
With this combo you will finally enter into twrp
{
"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"
}
Ah, before i forget, first time in TWRP, you can make your backup . Just be sure, your sdCard iS big enough.
In twrp you need to wipe+format ( please look in the lineageOS thread.)
DONT reboot after wiping. You just deleted and formated old data/OS.
After the wipe you install LineageOS, and without reboot you install gapps directly after.
after flashing/installing OS+Gapps you start the first time into LineageOS....This will need some time .
And then, power up the first time, you will see if you did it properly.... it can happen, that you'll have a bootloop. Dont worry then, you just messed up the order for the wiping, or forgot Gaps. if you have a bootloop, just go into TWRP, and restart by the first step
gl&hf
For the backup:.... first time booting to TWRP, you can/should make your backup.
just choose the all boxes, for your full backup...I made a screenshot....
And just fir your info:
my little reminder, that wiping in TWRP is a bit wired
deleted
Xiaomi 11 Lite 5G NE (Lisa)
Stock 12.5.8 EEA
Bootloader unlocked, Orange Fox recovery and Magisk Canary 25.2
I was running the same set-up for a couple of months, by only updating when newer Magisk was released or some module.
I never had any problem
Used to reboot like twice a week. On Sunday I wanted to reboot for a benign reason, since I installed a new weather widget
But instead of rebooting, the phone immediately went to Fastboot.
Tried couple more times, always rebooting to Fastboot
By Vol+, I rebooted to Orange Fox, wiped Dalwik and Cache and /data/system/package_cache but it didn't help
Then, from Orange Fox I flashed the boot img without Magisk, but no help, Lisa still rebooting to Fastboot.
I flashed even stock Recovery back, no help
---
Downloaded fastboot/tgz MIUI 13.0.9.0 EEA, un-gzipped, un-tared, ran flash_all.bat script (incl. wiping Data but not relocking Bootloader) through Fastboot - all partitions were flashed OKAY but Lisa still rebooted to Fastboot
From stock Recovery I performed Factory reset, but again no help
---
At that time I was pretty desperate. I was thinking about re-locking Bootloader and going to service shop, to claim for Warranty
But I decided to try Xiaomi.eu 13.0.2.0 Stable - also a Fastboot ROM
(Actually, few days before, I finally made my mind that I would go for Xiaomi.eu Weeklies - they are now Recovery ROMs
For preparation, I did all kinds of backups, planning to switch that same Sunday evening - therefore, I had one trouble less, although the phone was not operational, I didn't loose any photos, WA chats, etc and I already had a second/another/old Xiaomi phone prepared to serve for personal and work activities while I would be setting, rooting, etc Xiaomi.eu on Lisa)
Hence I ran windows_fastboot_first_install_with_data_format.bat through Fastboot - flashing was longer (few more partitions than when I flashed the stock) and again, all partitions flashed with OKAY
---
TG, the phone now rebooted to MIUI - but there was a blocking alert that For security reason, my phone was locked (see the screenshot)
I had to enable WiFi and activate/unlock by logging to my Mi Account
Still there was a catch - I forgot my Mi Account password. But I used my old/second Xiaomi (Mi 9T) phone, opened Mi Account there in Settings, and found the Change password option
Although not knowing my old password, I was allowed to set the new password by authorizing myself through an SMS code received to my pre-configured phone number associated with my Mi Account
Then I entered that new Mi Account password on Lisa, and I was finally allowed to enter and set the new MIUI 13
---
I don't know was all that related to my extensive playing with Find My Device (Google) and Find Device (Xiaomi) from the browser. Over the last week's I was testing from time to time how fast they can locate both my phones
But I can swear that I never pushed Secure or Lock my phone(s) remotely. Btw, if I did, Lisa would be locked/blocked immediately, not on the next reboot (by ambush)
Hence I don't know what was the cause
But although flashing the stock Fastboot ROM did not help, flashing Xiaomi.eu Fastboot ROM successfully unblocked/revived my phone
This is a Xiaomi Mi account security feature. If your device is linked to a Mi account, this feature is enabled.
I don't know how it works but I has happened to me with several devices.
If you unlink your Mi account from a device, then this alert is not shown.
raulci said:
This is a Xiaomi Mi account security feature. If your device is linked to a Mi account, this feature is enabled.
I don't know how it works but I has happened to me with several devices.
If you unlink your Mi account from a device, then this alert is not shown.
Click to expand...
Click to collapse
That's all ok. And I want Mi Account bcs I use it Mi Cloud backup
However, I'm surprised why that same alert (same MIUI feature), did not show upon flashing stock MIUI Fastboot ROM (instead, it was immediately dieing to Fastboot)
zgfg said:
But instead of rebooting, the phone immediately went to Fastboot.
Tried couple more times, always rebooting to Fastboot
Click to expand...
Click to collapse
I'm curious now, I had to try:
fastboot continue
zgfg said:
but Lisa still rebooted to Fastboot
---
At that time I was pretty desperate.
Click to expand...
Click to collapse
I'm pretty much stuck at this point after following the guide to flash lineage failed.
zgfg said:
But I decided to try Xiaomi.eu 13.0.2.0 Stable - also a Fastboot ROM
(Actually, few days before, I finally made my mind that I would go for Xiaomi.eu Weeklies - they are now Recovery ROMs
Hence I ran windows_fastboot_first_install_with_data_format.bat through Fastboot - flashing was longer (few more partitions than when I flashed the stock) and again, all partitions flashed with OKAY
But although flashing the stock Fastboot ROM did not help, flashing Xiaomi.eu Fastboot ROM successfully unblocked/revived my phone
Click to expand...
Click to collapse
Currently downloading the latest Eu Weekly to see if that will help. My phone is the global version, I had OTA updated it to the latest ROM, turned on developer mode, allowed USB debugging, and unlocked the bootloader before the failed flash of lineage.
Hopefully it works.
Old_Mil said:
I'm pretty much stuck at this point after following the guide to flash lineage failed.
Currently downloading the latest Eu Weekly to see if that will help. My phone is the global version, I had OTA updated it to the latest ROM, turned on developer mode, allowed USB debugging, and unlocked the bootloader before the failed flash of lineage.
Hopefully it works.
Click to expand...
Click to collapse
I intentionally used Fastboot Xiaomi.eu ROM since it seems it flashes more partitions then Recovery type, but maybe I'm wrong
Btw, did you try to connect to PC, and when your phone unsuccessfully reboots to Fastboot (instead of to the system) that you command:
fastboot continue
I didn't try myself, I later came across that suggestion by someone
zgfg said:
I intentionally used Fastboot Xiaomi.eu ROM since it seems it flashes more partitions then Recovery type, but maybe I'm wrong
Btw, did you try to connect to PC, and when your phone unsuccessfully reboots to Fastboot (instead of to the system) that you command:
fastboot continue
I didn't try myself, I later came across that suggestion by someone
Click to expand...
Click to collapse
I tried the fastboot continue command, but it failed saying there was no image on the partition.
After downloading the weekly ROM from the eu community site, I unzipped it, only to find that the .bat files they reference in the fastboot installation instructions weren't included in the .zip...?
Old_Mil said:
I tried the fastboot continue command, but it failed saying there was no image on the partition.
After downloading the weekly ROM from the eu community site, I unzipped it, only to find that the .bat files they reference in the fastboot installation instructions weren't included in the .zip...?
Click to expand...
Click to collapse
That's the point. Recovery type ROM must be installed from the custom Recovery
Therefore I used Fastboot type ROM...
zgfg said:
Therefore I used Fastboot type ROM...
Click to expand...
Click to collapse
However, there are no fastboot ROMs listed for the Mi 11 Lite 5G NE under either the Weekly tab or Stable tab...both list them as recovery ROMs now, and I have no working recovery so this is probably a dead end.
Old_Mil said:
However, there are no fastboot ROMs listed for the Mi 11 Lite 5G NE under either the Weekly tab or Stable tab...both list them as recovery ROMs now, and I have no working recovery so this is probably a dead end.
Click to expand...
Click to collapse
There is Stable, but not the latest
zgfg said:
There is Stable, but not the latest
Click to expand...
Click to collapse
I'm guessing that since it's not the latest, if I try and flash it that the antirollback protection will brick the handset...?
Old_Mil said:
I'm guessing that since it's not the latest, if I try and flash it that the antirollback protection will brick the handset...?
Click to expand...
Click to collapse
There is no anti-rollnack protection in Xiaomi.eu scripts
In the Xiaomi.eu Forum, Stable MIUI 13 thread, post #1 there is a link to AFH:
MIUI 13 - MIUI 13 STABLE RELEASE
Status: RELEASED RULES WHEN POSTING 1. If a ROM is not published DONT ASK ABOUT ITS ETA 2. If a ROM is not published DONT ASK why! 3. If a ROM is available, download it and use it 4. If a ROM has bugs, post the bug to the bug section if the BUG is not already listed 5. If you use any form of...
xiaomi.eu
Scroll there to find the zip for 5G Lite NE that has Fastboot in the name. There are two (third is the newest, no fastboot in the name, it's recovery type ROM) and take the newer fastboot
And please read instructions in that thread, same post #1, how to install. EVERYTHING is explained there (read about Fastboot installation part), do not ask me how to install or so, I will no more help you with additional info or so, because everything explained there (I will really not waste my time for writing the same things
All of us were able to install by properly following that same guide - hence for those who want to concentrate and read, the guide is enough
Good luck
zgfg said:
There is no anti-rollnack protection in Xiaomi.eu scripts
In the Xiaomi.eu Forum, Stable MIUI 13 thread, post #1 there is a link to AFH:
MIUI 13 - MIUI 13 STABLE RELEASE
Status: RELEASED RULES WHEN POSTING 1. If a ROM is not published DONT ASK ABOUT ITS ETA 2. If a ROM is not published DONT ASK why! 3. If a ROM is available, download it and use it 4. If a ROM has bugs, post the bug to the bug section if the BUG is not already listed 5. If you use any form of...
xiaomi.eu
Scroll there to find the zip for 5G Lite NE that has Fastboot in the name. There are two (third is the newest, no fastboot in the name, it's recovery type ROM) and take the newer fastboot
Click to expand...
Click to collapse
Thanks! This worked perfectly, flashed the EU Rom and the phone booted - initially into Mi Recovery and then into the full Mi13/A12 OS.
The problem I was having is I was trying this on my 2-1 with a 7 inch screen, and the filenames on Sourceforge were truncated so I couldn't see that any had fastboot in the name. I hovered over the files with 5GNE in the filename and then found the one you describe.
Thanks again, it's working.
Now I just have to supress the urge to try flasing Pixel Experience and breaking it again.
Old_Mil said:
Thanks! This worked perfectly, flashed the EU Rom and the phone booted - initially into Mi Recovery and then into the full Mi13/A12 OS.
The problem I was having is I was trying this on my 2-1 with a 7 inch screen, and the filenames on Sourceforge were truncated so I couldn't see that any had fastboot in the name. I hovered over the files with 5GNE in the filename and then found the one you describe.
Thanks again, it's working.
Now I just have to supress the urge to try flasing Pixel Experience and breaking it again.
Click to expand...
Click to collapse
Now, you can update to the latest Xiaomi eu Stable (that third, latest ROM for Lisa without the fastboot in the name), released Sep 10
You will need Orange Fox (OF, custom recovery). Open the following thread, in the post #1 there is a link to AFH, find Lisa and download OrangeFox-R11.1_2-Unofficial-lisa:
[TWRP][RECOVERY] List of relevant recovery in one place
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/ I have compiled a list of relevant recovery in one place, i think it will be useful. Updates are monitored each day. Welcome, friends! How to install TWRP https://xiaomi.eu/community/threads/installing-a-custom-recovery.67841/
xiaomi.eu
Download and unzip, take the img file. DO NOT FLASH, just boot:
fastboot boot <OF img file>
and then from Orange Fox flash that Xiaomi.eu Stable zip (without Formatting or Wiping since you are now updating Xiaomi.eu)
Stable (being now Recovery type) will permanently install OF and for the next Xiaomi.eu update you will already have Orange Fox on your Lisa
---
I didn't try that latest Stable since I had already switched to Xiaomi.eu Weeklies (Betas) - they are also Recovery type ROMs, hence the procedure is the same
This worked as well, flashed the latest Stable ROM, flashed Magisk 25, and rooted the phone. I can delete some of the stock apps with a PC based debloater but still looking for an android app that will ..
Old_Mil said:
This worked as well, flashed the latest Stable ROM, flashed Magisk 25, and rooted the phone. I can delete some of the stock apps with a PC based debloater but still looking for an android app that will ..
Click to expand...
Click to collapse
You can not hard debloat because your SAR is read-only. Not even with custom recovery
However, you can systemlessly debloat by:
GitHub - Magisk-Modules-Alt-Repo/SystemlessDebloater: Select and systemlessly debloat preinstalled system apps. Supporting up to System As Root (SAR), Dynamic partitions and Android 13. Module must be installed through Magisk app, not TWRP
Select and systemlessly debloat preinstalled system apps. Supporting up to System As Root (SAR), Dynamic partitions and Android 13. Module must be installed through Magisk app, not TWRP - GitHub - ...
github.com
{
"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 reachedmirror.neelc.org took too long to respond.