[Tutorial] [10.0] Step-by-step guide to flash Aosp base Rom - Sony Xperia XZs Guides, News, & Discussion

I Don't own the project
Everything base on [10.0] Project Treble for Xperia XZs
By Sjll ​
Recently my G8232 brick , so i decide make a "CLEAN" fresh to my phone ,
After i flash Android 10 by Sjll , cause it needs Android 10 GSI,
i wonder, can i flash other team's GSI instead official? So, i started try many kind of GSI , this is result , a good news!
HavocOS/LineageOS/PixelExperience all can be daily use!!
Screenshots
Havoc-OS
lineage
PixelExperience
---------------------------------------------------------------------
How to flash:
Download file form [10.0] Project Treble for Xperia XZs By Sjll,
Donload Adb toolbox
hold [power] + [vol+] to get hard power down > hold [vol+] and plug to pc get into fastbootmode
fastboot format cache
fastboot format userdata
fastboot flash recovery twrp-3.3.1-0-kagura.img
hold [power] + [vol-] to get to TWRP and do full wipe
turn off device and hold [vol+] and plug to pc to get into fastbootmode
fastboot flash boot boot.img form Android 10 by Sjll
fastboot flash oem vendor.img form Android 10 by Sjll
fastboot format cache
fastboot format userdata
fastboot flash system [GSI.img] you want
*GSI should be A/B type, Never use A-Only!
LineageOS by AndyYan
Pixel Experience 10 & Havoc-OS by turbolukex5
------------------------------------------------
**** if you want gapps, after flashed system , you need immediately do the step ****
Download gapps pack form The Open GApps Project webiste
hold [power] + [vol+] to get hard power down > hold [power] + [vol-] to twrp > wipe > advance > system > resize system > repair system > resize system
after resize system , check free space of system AGAIN!
When you check down you are good to go!You can flash gapps now!
-----------------------------------------------
**** Magisk ****
Download modify boot.ing from here
hold [power] + [vol+] to get hard power down > hold [vol+] and plug to pc get into fastbootmode
> fastboot flash boot magisk_patched.img > unplug & reboot > install magisk manager like a normal app > Done!
-----------------------------------------------
**** Bug ****
For Havoc-OS , everything work fine,
but can't power off device normaly , need hold [power] + [vol+] to get hard power down
For LineageOS everything work fine , haven't see a bug yet
For PixelExperience everything work fine , but have some issue,
when you get a call first time, the voice seem muted, but actually its not , you need turn speaker output first , then turn it off ,
after that it works normally
---------------------------------------------------------
Thanks the Community make this HAPPEN
Also sorry for my poor English

Nice review bro, thank you, I will try as soon as possible

Need more GSIs

SOV35
Is it possible to use this tutorial on a SOV35 (XZs- au)?
I'm currently using with the global firmware ( G8231 )
Please help! :fingers-crossed:

havoc 3.4 gsi worksperfectly

I followed all the steps as you mentioned but. I can't get the second sim working and the phone restarts randomly. But when the phone runs without the SIM it works smoothly. Is there any fix for that?
I installed PixelExperience GSI

Anish Z1 said:
I followed all the steps as you mentioned but. I can't get the second sim working and the phone restarts randomly. But when the phone runs without the SIM it works smoothly. Is there any fix for that?
I installed PixelExperience GSI
Click to expand...
Click to collapse
Reference my post to fix the crashing and freezing: https://forum.xda-developers.com/xzs/development/treble-android-10-0-xperia-xzs-t3976367/page4
Install this to fix dual sim: https://sx.ix5.org/files/builds/sony/ ( https://forum.xda-developers.com/crossdevice-dev/sony/universal-sony-dualsim-patcher-t3930983 )

help
what should i do when it says "target reported max download size of 268435456 byte incvalid sparse file format at header magi . . . ..

pandjie24 said:
what should i do when it says "target reported max download size of 268435456 byte incvalid sparse file format at header magi . . . ..
Click to expand...
Click to collapse
Are you trying to root your GSI? If so, you need this version of TWRP : https://sx.ix5.org/files/builds/kagura/misc/twrp-kagura-oem-to-vendor.img
Try to be a bit more descriptive next time when asking a question as other's might not understand what you are asking or in which context the error was being encountered.

is it ok if i used any gsi rather than linage havoc and pixel

boot
Everything seamed to be working fine with Lineage OS, aside from random reboots. However I changed the setting "use alternative camera profile" and now I just get a loading screen.

Crash with fingerprint
With all 10 ROMS I have the problem that it crashes when it tries to read fingerprint when screen is off. It used to only scan for fingerprint when screen was on, but somehow (with android 10) if I touch the power button now, the fingerprint scanner is already reading and the phone crashes.
Anyone can help?

DAANDAV said:
With all 10 ROMS I have the problem that it crashes when it tries to read fingerprint when screen is off. It used to only scan for fingerprint when screen was on, but somehow (with android 10) if I touch the power button now, the fingerprint scanner is already reading and the phone crashes.
Anyone can help?
Click to expand...
Click to collapse
Encryption on your data partition is still being enforced and/or it has something to do with dm-verity. First, make sure you install this optimized recovery for XZ & XZs ( https://sx.ix5.org/files/builds/kagura/twrp-kagura-oem-to-vendor.img ), then boot into it and wipe everything (dalvik, cache, data, internal storage, system); second, follow the steps to treble ready the device (boot, oem) through either fastboot or recovery; third, install this ( https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389 ) after you have flashed your system of choice and before first boot. Now you can enjoy a mostly crash free ROM when using the fingerprint unlocking; keep in mind, there are still other bugs that can be logically removed depending on the ROM you chose. Experiment and figure out what works best.

pandjie24 said:
help
what should i do when it says "target reported max download size of 268435456 byte incvalid sparse file format at header magi . . . ..
Click to expand...
Click to collapse
Are you sure you really extracted GSI to .img?

Related

Data Factory Reset on OnePlus 2 through pc (cmd) and fastboot

Hello guys ,
Today I rooted my OPT with WinDroid Toolkit / OnePlus 2 ToolBox and after installing TWRP I installed the last OxygenOS 3.0 (yeah I know , I didn't to do it but I wanted to install cm13 and after a quick check I was convinced that OxygenOS is better .)
I installed the latest OxygenOS and gapps , removed dalvik cache and rebooted my phone .
After about 2 hours of loading (I see the OnePlus logo and "powered by android" under it) I saw that nothing happens .
I couldn't load my recovery and I can only open fastboot .
I know that it was stupid , trust me , but is there any way to factory reset my OPT through fastboot and pc ?
Thanks a lot ! have an awesome day !
lidorb98 said:
Hello guys ,
Today I rooted my OPT with WinDroid Toolkit / OnePlus 2 ToolBox and after installing TWRP I installed the last OxygenOS 3.0 (yeah I know , I didn't to do it but I wanted to install cm13 and after a quick check I was convinced that OxygenOS is better .)
I installed the latest OxygenOS and gapps , removed dalvik cache and rebooted my phone .
After about 2 hours of loading (I see the OnePlus logo and "powered by android" under it) I saw that nothing happens .
I couldn't load my recovery and I can only open fastboot .
I know that it was stupid , trust me , but is there any way to factory reset my OPT through fastboot and pc ?
Thanks a lot ! have an awesome day !
Click to expand...
Click to collapse
Go to this thread: https://forums.oneplus.net/threads/...rts-oos-3-0-oos-2-x-x-h2os-mm-lp-cm-13.443032.
Download the TWRP 3.0.2 Hybrid v.X.
Reboot into fastboot mode: fully power off the phone, press and keep power up and power button together: you should be in fastboot mode. I'll assume you have installed fastboot / adb / drivers.
Now, open CMD / terminal, and type, in the folder where you've download the recovery:
Code:
fastboot boot <recovery_name>.img
You should be in TWRP.
In TWRP, go to Wipe, Advanced Wipe: Data, Cache, Dalvik Cahe and System.
If you want to flash the latest CM 13 ROM (the Official one which you can find here: https://download.cyanogenmod.org/?device=oneplus2) go to this thread : http://forum.xda-developers.com/oneplus-2/general/switch-firmware-twrp-t3371583 and download:
Switch_tOS3_H2OSMM: New Firmware + TWRP Hybrid
Use for CM13 with new Kernel(since 3rd June), OxygenOS 3.0.0/3.0.1, HydrogenOS MM
For use with OFFICIAL CyanogenMod 13 NIGHTLY
Link v1: https://www.androidfilehost.com/?fid=24533103863138121
Link v2:https://www.androidfilehost.com/?fid=24533103863141745
Link v3: https://www.androidfilehost.com/?fid=24566466246344728
Click to expand...
Click to collapse
You're device should reboot by itself in TWRP.
Now, flash CM 13 Official, GAPPS, etc, etc.
Voila, you don't wipe your device .
casual_kikoo said:
Go to this thread: https://forums.oneplus.net/threads/...rts-oos-3-0-oos-2-x-x-h2os-mm-lp-cm-13.443032.
Download the TWRP 3.0.2 Hybrid v.X.
Reboot into fastboot mode: fully power off the phone, press and keep power up and power button together: you should be in fastboot mode. I'll assume you have installed fastboot / adb / drivers.
Now, open CMD / terminal, and type, in the folder where you've download the recovery:
Code:
fastboot boot <recovery_name>.img
You should be in TWRP.
In TWRP, go to Wipe, Advanced Wipe: Data, Cache, Dalvik Cahe and System.
If you want to flash the latest CM 13 ROM (the Official one which you can find here: https://download.cyanogenmod.org/?device=oneplus2) go to this thread : http://forum.xda-developers.com/oneplus-2/general/switch-firmware-twrp-t3371583 and download:
You're device should reboot by itself in TWRP.
Now, flash CM 13 Official, GAPPS, etc, etc.
Voila, you don't wipe your device .
Click to expand...
Click to collapse
First of all , thanks a lot for the fast reply, I do really appreciate it .
Any way , my phone doesn't go to TWRP. When I finished installing the TWRP it just turned off and when I try to move to TWRP (lock key + volume down) it doesn't work, the phone just try to reboot to the android system and if I press them too long it shuts off again .
Do you know how can I do all that process through the command ?
lidorb98 said:
First of all , thanks a lot for the fast reply, I do really appreciate it .
Any way , my phone doesn't go to TWRP. When I finished installing the TWRP it just turned off and when I try to move to TWRP (lock key + volume down) it doesn't work, the phone just try to reboot to the android system and if I press them too long it shuts off again .
Do you know how can I do all that process through the command ?
Click to expand...
Click to collapse
Go check this out -> http://forum.xda-developers.com/oneplus-2/general/guide-return-op2-to-100-stock-unbrick-t3229606 (this will not wipe your data).
casual_kikoo said:
Go check this out -> http://forum.xda-developers.com/oneplus-2/general/guide-return-op2-to-100-stock-unbrick-t3229606 (this will not wipe your data).
Click to expand...
Click to collapse
DAMNNN I love you so muchhh !!!
thanks a lot bro , really .
lidorb98 said:
DAMNNN I love you so muchhh !!!
thanks a lot bro , really .
Click to expand...
Click to collapse
Your welcome !
Don't forget to hit thanks button !

AOSP N for DOOGEE X30

ROM is still under development.
Downloads
20180427-1610
20181006-1451
XDA:DevDB Information
DOOGEE_X30_AOSP, ROM for all devices (see above for details)
Contributors
ttomovcik, VeteranoX, SoaringLake
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
Based On: AOSP
Version Information
Status: Beta
Current Beta Version: 20181127-1452
Beta Release Date: 2018-11-27
Created 2018-05-24
Last Updated 2018-11-28
Reserved
Reserved
Due to some bugs in TWRP, we recommend to charge your device to AT LEAST 70% and keep the device plugged in. I'm still waiting for DOOGEE to respond (emailed them if they can send the kernel source). So In the meantime, enjoy overheating and quick battery discharge in TWRP.
New build out! This addresses the following bugs:
Camera FC when opening settings
Camera slow-mo not working
Perfrmance issues
Enabled on-screen navbar - hardware buttons will remain enabled, however, changing Generic.kl will result in HW buttons not working
Changelog
20181018-1337 (Created by SoaringLake)
[FIX] Missing launcher
[ADDED] Face recognition
20181006
Removed Gallery2 - caused problems, needs to be replaced with GApps
Added sqlite3
Taking screenshots now works
20180427-1610
Initial release
Features / what's working
GPS
Phone calls / mobile data
Wi-Fi
DuraSpeed
Brightness (can be adjusted lower than stock)
Volume changing works (stock ROM doesn't have this for some reason)
Youtube supports VR
MiraVision
Bugs / feature requests
Settings > about phone is showing some random indian guy as maintainer. This is due to the fact that this ROM is ported from another device to X30. Will fix that later, probably
When quickboot is active, phone will charge when off without the charging screen animation
NVRAM ERROR is showing in Wi-Fi networks
Google Play services not updating automatically
Unable to open Google Assistant, opens up multitasking view instead
Split screen buggy
No mediatek gestures
Instagram videos rendering incorrectly (SoaringLake)
Camera FC when going to settings
FM Radio volume issues
Camera slow-mo not working
Installation
Unlock bootloader and flash TWRP/CWM (1)
Flash ROM and GApps in one go. DO NOT REBOOT BETWEEN ZIP FLASHING (2)
Wipe cache
Reboot
(1) - Installing TWRP
Enable OEM unlocking in developer options
Download TWRP from here
Reboot into bootloader (Power off and then power on while holding volumeUp)
On your PC, flash it with: "fastboot flash recovery <filename>.img"
Reboot into recovery (Power off, then Power on while holding VolumeUp and select Recovery)
(2) - Flashing ZIP images
Make sure to wipe device
Flash the ROM from device or SD card. Sideload will result in no OS installed error
(Optional) Flash any variant of openGapps - ARM/7.1.1
thread closed until the download links will be available @ttomovcik pm us when you`re ready to share the links
-=-=-
thread re-opened
How can I root?
Hey can you publish the instructions about to root and install Twrp?
And thanks for your work.
mediafire.com/file/3zifgay1h0c334g/TWRP%20dogee%20x30.rar
install via fastboot "fastboot flash recovery recovery.img", only remember to unlock bootloader 1. in developer options> allow OEM unlock 2. In fastboot "fastboot OEM unlock"
the first result on google after entering doogee x30 root
I'm Stuck!
I followed the steps but I got stuck in TWRP with the ROM and without the ROM that I do?
VeteranoX said:
I followed the steps but I got stuck in TWRP with the ROM and without the ROM that I do?
Click to expand...
Click to collapse
When it comes to our Rom you have to do wipe all and then install it because otherwise it likes to make mistakes, I have no problem.
PS. You can enter the twrp and use the recovery, because some img recovery that I liked liked to brick the phone
PS2. At the time of bootloader unblocking, Start the phone again because it has to restore the phone to the factory, Sam so zeged the phone because I did not read the messages on it and immediately uploaded twrp by which he had a bootloop
SoaringLake said:
When it comes to our Rom you have to do wipe all and then install it because otherwise it likes to make mistakes, I have no problem.
PS. You can enter the twrp and use the recovery, because some img recovery that I liked liked to brick the phone
PS2. At the time of bootloader unblocking, Start the phone again because it has to restore the phone to the factory, Sam so zeged the phone because I did not read the messages on it and immediately uploaded twrp by which he had a bootloop
Click to expand...
Click to collapse
Hey can you send me a copy of your stock recovery? Because now i can't turn it on just flastboot.
VeteranoX said:
Hey can you send me a copy of your stock recovery? Because now i can't turn it on just flastboot.
Click to expand...
Click to collapse
Shutdown device, press vol+ and power Button , you will see the menu, vol + you choose the option and vol-approve
and stock recovery I will send it later
recovery: mega.nz/#!raBW3CBC!LLQYl5tZEFyttQg8LWYeqdqu7sKusOUZXxEsHJthNdo
Phliz Touch recovery 6.59.0
for those willing to give a link to philz touch recovery in version 6.59.0, I worked on ClockWokMod but can not see the external sd card
mega.nz/#!PbpHlbjR!VfIomQYwPQQ6f5-1mT7tIF3x66X692rcBiYUQeusLto
I got it!
It was not necessary at the end I downloaded the stock and it was only discharged , but could you repeat the installation of the TWRP in more detail? I'm also not a natural English speaker.
---------- Post added at 04:38 PM ---------- Previous post was at 04:25 PM ----------
SoaringLake said:
Shutdown device, press vol+ and power Button , you will see the menu, vol + you choose the option and vol-approve
and stock recovery I will send it later
recovery: mega.nz/#!raBW3CBC!LLQYl5tZEFyttQg8LWYeqdqu7sKusOUZXxEsHJthNdo
Click to expand...
Click to collapse
It was not necessary at the end I downloaded the stock and it was only discharged, but could you repeat the installation of the TWRP in more detail? I'm also not a natural English speaker.
VeteranoX said:
It was not necessary at the end I downloaded the stock and it was only discharged , but could you repeat the installation of the TWRP in more detail? I'm also not a natural English speaker.
---------- Post added at 04:38 PM ---------- Previous post was at 04:25 PM ----------
It was not necessary at the end I downloaded the stock and it was only discharged, but could you repeat the installation of the TWRP in more detail? I'm also not a natural English speaker.
Click to expand...
Click to collapse
1. go to the developer options in the system, select allow OEM unlock and debug usb.
2, issue the command in ADB "adb reboot-bootloader"
3. issue the command "fastboot oem unlock"
4. restart the "Fastboot reboot" phone
5. allow for wipe data,
6. go to fastboot,
7. issue the command "fastboot flash recovery $ image"
$ image = name with the extension image recovery
I got it!
Hey now is workin (rom and root) i'm testing now and i will send a feedback later but now just i can say
Faster!
Thank you!
Does anyone know how to fix the error: NVRAM WARRNING: Err 0x02

[GUIDE] Convert Mi A2 to Mi 6X [MIUI 10 Oreo] [MIUI 10 Pie]

Code:
/*
* Your warranty is... still valid?
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Hey guys, Today I am creating a Guide on How to Convert Mi A2 to Mi 6X without triggering ARB.
This guide is based on Guide by @yunusasik(Telegram : @dejavutr ) so All credit goes to Him.
First of All Download the Convert.zip from here
All files needed to be replaced have already been replaced in convert.zip.
Then, Follow the Following Steps to Flash Mi 6X Firmware on your A2
First Make Sure you already unlocked bootloader flashing and flashing critical ("fastboot flashing unlock" and "fastboot flashing unlock_critical")
1) Install Qualcomm Driver (next next next) (Also Windows update can do this trick when you plug )
2) Install QPST (use setup from the QPST Alternative folder. )
(find QFİLL on start menu or qpst installed directory), open QFİLL from start menu or opst installed folder.
3) Select Flat Build Mode
Select Programmer File prog_emmc_firehose_Sdm660_ddr.elf ( already changed no arb risk )
Select XML files rawprogram0 and patch0.xml
4) Put the phone on the edl mode
navigate to ADB Folder and Open tikla.bat, it will open command windows in that directory.
Use "fastboot oem edl" command to Enter "Emergency Download Mode ( EDL )"
Press Download
When install finish. Power up the phone.
MIUI 9 Ready to BOOT (First boot may take time you can hard reset via pressing vol up - down and power together )
5) You dont need to setup miui 9 just go fastboot again (vol down + power ( when phone closed ) )
From this section you can either install MIUI 10 (OREO) or Custom ROM ( Which one you want )
Guide will be Resume about flashing MIUI 10 ( OREO )
Flash TWRP
" fastboot flash recovery twrpwayne.img "
" fastboot boot twrpwayne.img "
If twrp start chinese you can set language on that screen
6) Wipe / Advanced Wipe
7) System + Dalvik + Cache + Data + Internal
8) Flash MIUI 10(no arb).zip via adb sideload (put file into adb folder and use adb sideload MIUI 10 (no arb).zip) or put file on the
storage via mtp, if its works
" No need for gapps "
If you want root Flash Magisk.
Welcome to MIUI 10 without arb
You can use MiFlash Tool 2016 64Bit only this one works good others may stuck sometimes and risky because if you unplug when installing you have to use test point method for saving phone.
You can enable camera2api with "Camera2api enabler" on play store (ONLY MIUI 10 OREO)
If qfill installation somehow corrupt use "QPST Alternative" folder or Miflash from above
You can Download Newer MIUI Releases from here
Just make sure to delete the "firmware-update folder" using winrar etc.
-------
UPDATİNG TO MIUI 10 PIE
Download MIUI 10 PIE from here (if you are in mobile press "try download anyway" )
Open zip file and delete "Firmware Upgrade" folder from the zip (Most İmportant)
Boot into TWRP
Go Wipe / Advanced Wipe
Wipe "System + Dalvik + Cache + Data"
(Make sure you are using ext4 file system on Cache and Data partition)
Flash MIUI 10 Pie zip
Flash Hex Kernel download from here (We need this because we are not using fw update folder for updating kernel etc (because its trigger arb 4))
Flash Magisk if you want root
Reboot to system
Welcome to MIUI 10 Pie
You can check new mıuı eu updates from here.
For enabling camera2api on MIUI 10 Pie you have to edit build prop download this application from play store
Give root permissions
Search for HAL3 then change boot of them 0 to 1
Restart the phone.
For stable gcam use this
------
Converted Mi6X Indian Variant Camera FİX
1. Flash any custom ROM or MIUI 10 ROM firmware-update folder deleted.
2. Flash the zip from here via TWRP.
3. Reboot
------
Convert Back to A2
Download latest a2 stock rom.
Put phone to edl mode again (fastboot oem edl)
Flash stock rom via QFİLL with same method (Select .ddr and xml files from stock rom folder) and power up.
Done.
(If you have wifi camera or splash screen problems. Flash stockrom with miflash on fastboot (vol down + power ) again.)
(Alternative) You can use MiFlash Tool 2016 64Bit to convert back.
Select A2 stock rom folder.
Put phone to edl mode (fastboot oem edl).
Flash Rom when its done, power up the phone to fastboot (vol down + power ) and flash rom again. (for solving any camera wifi etc issue)
FAQ
Is there any alternative to this twrp ?
- Yes you can use alternatives, this one my fav.
Is there any alternative to this kernel ?
- Yes you can use NeonKernel, Reign Kernel or this EAS kernel from @rcstar6696
I got triggered ARB4 can I go back to A2 ? ( Unlocked Bootloader )
- Yes you can convert back to A2 with test point here is the guide for that. Thanks @powar19
If you have any questions feel free to ask.
Credits :-
1) @yunusasik Telegram : @dejavutr
2) @akshayakakat
For Support :-
1) https://t.me/mia26xBr
2) https://t.me/mia2official
3) https://t.me/mia2turkiye
Just converted 2 days ago using this guide. Works like a charm. Thanks
Guide works flawless no one should hesitate to do it.
Used this 2 days ago. Working perfectly without problems.
stuck at adb sideload in twrp,what to do bro?
Why would I want to do that?
Will it fix the A2 bugs?
Can i Install wayne aosp roms after applying this?
Sent from my Xiaomi MI A2 using XDA Labs
lsd95 said:
Why would I want to do that?
Will it fix the A2 bugs?
Click to expand...
Click to collapse
What bugs? For me it did solve an issue from A2, the slow micron storage.
Thanks for this guide!
stridedesu said:
What bugs? For me it did solve an issue from A2, the slow micron storage.
Thanks for this guide!
Click to expand...
Click to collapse
Like the proximity sensor bug, unlocking phone lag, gps with Google accuracy turned on...
dr460nf1r3 said:
Can i Install wayne aosp roms after applying this?
Click to expand...
Click to collapse
akshayakakat said:
You dont need to setup just go fastboot again
From this section u can either install miui 10 or custom rom guide will be resume about flashing miui 10
Click to expand...
Click to collapse
Seems like you can
I'm curious, how long does it take for QFIL to process MIUI9 stuff? I pressed download button and it's stuck or something for like an hour now.
alveola666 said:
Seems like you can
I'm curious, how long does it take for QFIL to process MIUI9 stuff? I pressed download button and it's stuck or something for like an hour now.
Click to expand...
Click to collapse
It does take a long time than Mi Flash. I check from time to time where it stopped and it does move a bit, like a snail's pace kind of slow.
lsd95 said:
Like the proximity sensor bug, unlocking phone lag, gps with Google accuracy turned on...
Click to expand...
Click to collapse
I do not have those bugs before I converted, so I can't help, sorry >_<
akshayakakat said:
Hey guys, Today I am creating a Guide on How to Convert Mi A2 to Mi 6X without triggering ARB.
This guide is based on Guide by @yunusasik so All credit goes to Him.
First of All Download the convert.zip from here
All the files needed to be replaced have already been replaced in convert.zip.
Then, Follow the Following Steps to Flash Mi 6X Firmware on your A2
1) Install Qualcomm Driver (next next next)
2) Install qpst (find qfill on start menu or qpst installsd directory)
3) Select Flat Build Mode
Select Programmer File prog_emmc_firehose_Sdm660_ddr.elf (already changed no arb)
Select XML files rawprogram0 and patch0 xml
4) Put the phone on the edl mode
navigate to ADB Folder and Open tikla.bat, it will open command windows in that directory.
"fastboot oem edl" make sure u have unlocked flashing and critical (check via fastboot oem device-info)
Press download
MIUI 9 Ready
5) You dont need to setup just go fastboot again
From this section u can either install miui 10 or custom rom guide will be resume about flashing miui 10
Flash Twrp
fastboot flash recovery twrpwayne.img
fastboot boot twrpwayne.img
If twrp start chinese you can set language there
6) Wipe / Advanced Wipe
7) System + Dalvik + Cache + Data + Internal
8) Flash MIUI 10(no arb).zip via adb sideload (put file into adb folder and use adb sideload filename.zip) or put file on the
storage via mtp if its works
" No need for gapps "
If you want root Flash Magisk.
Welcome to MIUI 10 without arb
If u wanna come back to Mi A2 just flash latest stock rom via qfill again.
U can use miflash but its stuck sometimes and risky because if u unplug when installing u have to use test point method for saving phone.
U can enable camera2api with "Camera2api enabler" on play store
If QFIL Does not work try QPST Alternative
You can Download Newer MIUI Releases from here
Just make sure to delete the firmware-update using winrar.
Credits :-
1) @yunusasik
2) @akshayakakat
For Support :-
1) https://t.me/mia26xBr
2) https://t.me/mia2official
3) https://t.me/indiamia2
Click to expand...
Click to collapse
stridedesu said:
It does take a long time than Mi Flash. I check from time to time where it stopped and it does move a bit, like a snail's pace kind of slow.
I do not have those bugs before I converted, so I can't help, sorry >_<
Click to expand...
Click to collapse
I remember reading a thread related to sensor issue. There is already a post regarding this sensor issue in this forum. probably u need to re-flash the persist .img from fastboot but dont do it just blindly. rather search the forum and refer to that thread before proceeding.
very goo guide, simple and easy... but i reverted to mi A2 because MIUI did not have some featured i needed and now i have a "problem"... i dont have fastboot image and boot image sometimes is a black screen or the Mu logo and then starts the android one bootanimation, how can i fix that? thx
jesan9 said:
very goo guide, simple and easy... but i reverted to mi A2 because MIUI did not have some featured i needed and now i have a "problem"... i dont have fastboot image and boot image sometimes is a black screen or the Mu logo and then starts the android one bootanimation, how can i fix that? thx
Click to expand...
Click to collapse
Reflash rom with fastboot, not use edl.
Use miflasher or qfil
Enviado desde mi MI 6X mediante Tapatalk
What about the cameras? Do we need to flash the camera fix ?
akshayakakat said:
Hey guys, Today I am creating a Guide on How to Convert Mi A2 to Mi 6X without triggering ARB.
This guide is based on Guide by @yunusasik so All credit goes to Him.
First of All Download the convert.zip from here
All the files needed to be replaced have already been replaced in convert.zip.
Then, Follow the Following Steps to Flash Mi 6X Firmware on your A2
1) Install Qualcomm Driver (next next next)
2) Install qpst (find qfill on start menu or qpst installsd directory)
3) Select Flat Build Mode
Select Programmer File prog_emmc_firehose_Sdm660_ddr.elf (already changed no arb)
Select XML files rawprogram0 and patch0 xml
4) Put the phone on the edl mode
navigate to ADB Folder and Open tikla.bat, it will open command windows in that directory.
"fastboot oem edl" make sure u have unlocked flashing and critical (check via fastboot oem device-info)
Press download
MIUI 9 Ready
5) You dont need to setup just go fastboot again
From this section u can either install miui 10 or custom rom guide will be resume about flashing miui 10
Flash Twrp
fastboot flash recovery twrpwayne.img
fastboot boot twrpwayne.img
If twrp start chinese you can set language there
6) Wipe / Advanced Wipe
7) System + Dalvik + Cache + Data + Internal
8) Flash MIUI 10(no arb).zip via adb sideload (put file into adb folder and use adb sideload filename.zip) or put file on the
storage via mtp if its works
" No need for gapps "
If you want root Flash Magisk.
Welcome to MIUI 10 without arb
If u wanna come back to Mi A2 just flash latest stock rom via qfill again.
U can use miflash but its stuck sometimes and risky because if u unplug when installing u have to use test point method for saving phone.
U can enable camera2api with "Camera2api enabler" on play store
If QFIL Does not work try QPST Alternative
You can Download Newer MIUI Releases from here
Just make sure to delete the firmware-update using winrar.
Credits :-
1) @yunusasik
2) @akshayakakat
For Support :-
1) https://t.me/mia26xBr
2) https://t.me/mia2official
3) https://t.me/indiamia2
Click to expand...
Click to collapse
Does the camera work for indian user???plez reply
megaxp said:
Reflash rom with fastboot, not use edl.
Use miflasher or qfil
Enviado desde mi MI 6X mediante Tapatalk
Click to expand...
Click to collapse
oh ok! well i used qfill, i will try to flash it with fastboot
i'll try it tomorrow.
in advance, if we can enable camera2api we can install gcam without problems, right?
Can this guide be followed on stock pie?
EDIT:
Nevermind, the method works on pie
But I am not able to use camera. Any tips?
EDIT2:
Nvm, I figured it out. Enabled camera2api, and flashed whyred miui camera in magisk.

5S/5G Roms and Root Mega thread [Updated November 2022]

Nubia Red Magic 5G and 5S Roms and Root support Thread
Second post for TWRP and Magisk installation. Mirror for all roms and tools at end of post
Latest Official Rom updates
Android 11
US/Asia - V8.70 Nubia Link MD%: will update soon
EU - V7.70 Nubia Link MD5: will update soon
China - V9.50 Nubia Link MD5: 361AC13CA52AB83C239783FBAB088CEA
Android 10
US/Asia - V8.12 Nubia Link MD5: 6e930fc2431b3daeae2d94145926a6c1
EU - V7.15 Nubia Link MD5: bb9e3153716851e87f196ae6b4f44a2e
China - V6.23 Nubia Link MD5: BD447840ACA4D48F9443B94D2EAD890F
Change Log - 8.70 / 7.70 Android 11
- Security Patch October 2022
- Game Space enhancements
- Game space Gyro sensitivity menu
- game space touch sample rate improvement
- Fixed: corner of screen non-touchable in some cases
- Fixed: issue where game would fail to close
- Fixed: location of caller display
-Fixed: screen tearing when using 144hz
-
Bugs -
in Testing
- Always on display notification not showing
- memory leak in nubia launcher (requires forced close often to stop phone from lagging)
- small window mode for telegram and discord have wrong zoom/ aspect levels.
_____________________________________________________________________________________________________________
UNBRICK TOOL for 5S - Courtesy of @johnny886
Use this tool, with directions on the thread to restore your device to USA/Asia 8.07
you can then install TWRP and after flash any region rom after creating a somewhat universal unbrick tool for those in different regions.
Follow directions on the thread. but here is a link to the Thread. A Mirror for the tool is in my Personal Mirror at the bottom of this thread post.
Link to Thread
Confirmed working with 5G devices - but its recommended to update as soon as you unbrick.
_____________________________________________________________________________________________________________
For unlocked bootloader
Fix your fingerprint sensor.
here Link
--------------------------------
Update Instructions.
Note
for Android 11 do not flash through TWRP you will softbrick.
____________________________________________________________________
For Stock devices without root
- disable security. No pin, no face unlock, no finger print, no pattern. remove all security.
-download zip file
-go to system update tap three dots and select local update
-Navigate to update.zip and select.
-your phone will reboot and install new rom
- you phone will reboot once more and you will be greeted with your lock screen
- setup Phone with security options as before flash.
For devices with "LOCKED bootloader" Root / TWRP (not tested on A11)
- take backup of vbmeta and recovery partitions in TWRP
- change the name of both files to vbmeta.img and recovery.img
(VBmeta is often 64kb big and Recovery is often 90+mb big.)
- copy and paste these new img files into the update zip.
- flash through TWRP
- go back to main menu, select advanced, then select option
"disable replace TWRP" to keep TWRP as your recovery.
for devices with "Unlocked bootloader" (not tested on A11)
-make full backup
-download zip
-install zip through TWRP
-reboot
__________________________________________________________________________________
Custom Roms and Kernels
Kernel
Mattofthedead's Redmagic 5S kernel for LOS and Stock roms LINK
Roms
Rom Builder Ra's Custom Roms - Please post any bugs or issues in the related threads.
Pixel Experience Plus
Ressurection Remix
NOTE : to boot any Custom rom on the 5S device. Flash the Rom following the directions. then flash Matts LOS kernel Version 3
__________________________________________________________________________________
------------------------------
Old roms
Android 11
V8.65 Nubia Link MD5: 3d52e18c66366d3d23744184425d3926
V8.64 Nubia Link MD5: a7e61f5e2f7c377a6850cf6ac3a62aa7
V7.65 Nubia Link MD5: 746dad5b6145dfba1108355095a6ad46
V7.64 Nubia Link MD5: 55371ee8e5728aee2bc7df5b3a7d6585
V9.42 Nubia Link MD5: D492B92DD83B366508CDD74DE7D152A3
V9.40 Nubia Link MD5: D28F26289A9B75F771EF4F623F0BB367
V8.57 Nubia Link MD5: 266819d4b09c2c52aadb39e948dc84bc
V8.59 Nubia Link MD5: d7e32b7a3e833adc57fcf734aa47f5a3
V7.57 Nubia Link MD5: 81ee71869f660a28b631d871ffb59524
V7.60 Nubia Link MD5:
V9.26 Nubia Link MD5: 8997375CD97D8F7F261F21121FC8EFAA
Android 10
v6.18 Link MD5: 9AC5EA5F64835C1995E4A81D4973FB71
V6.13 Link MD5: F38ED2D7CB58252D308B29D1D4517DB9
V7.07 Link MD5: ffc3fdaf4afc522aa3a084d9275f2cb6
V7.14 Link MD5: 0f879160fbf8b556de5303207b93d0d1
V8.07 Link MD5: b30dab221be73292c5da7884afc0363f
V8.11 Link MD5: 85d9366a3017112cb68d66041e725ce6
________________________________________________________
Personal Mirror - Located in Eastern Canada
________________________________________________________
TWRP and root guide for 5S and 5G on Android 10 only - (these steps will NOT unlock your bootloader) - these steps use a bypass method to install a recovery without unlocking bootloader. the command below is to allow flashing of partitions. bootloader status is still locked during and after process is complete.
Note. if you already have ADB and fastboot drivers installed, this folder will work as is. if not I put an installer in the folder too to install a mini adb fastboot setup. which needs windows driver signing turned off (windows 8-10) this can be done by going to advanced startup and choosing to boot without driver signing.
1. Download zip file found at the end of this post
2. Extract to root of C: drive
3. open CMD prompt with admin privileges
4. CD to the ADB folder you extracted. (CD = Change Directory)
5. Connect your device in Fastboot mode (power off. hold volume down +Power until it vibrates. then release power but continue to hold volume down)
6. Once in fastboot mode, with cable connected to the computer run these commands
7. fastboot oem nubia_unlock NUBIA_NX659J (this allows you to flash the device partitions)
8. fastboot flash recovery TWRP-xxx.img (xxx being the version number of the TWRP image you choose to install)
9. fastboot flash vbmeta vbmeta_skip.img
10. reboot to recovery (from the fastboot menu) it should load TWRP
11. if TWRP does not ask you to keep recovery from being over written, go to advanced and choose disable replace TWRP. to keep TWRP as your recovery, and stop the system from re writing the stock recovery.
12. Reboot to system for the first time and complete the initial setup. this is to create the user space partitions data/media ( preferably do not make a pin or pattern at this stage)
13. once in the rom, connect to PC and copy over the Magisk zip to the internal memory. then reboot holding Volume up
14. once back into TWRP (if you created a pin during setup TWRP will ask you for your pin to access data) go into install and flash the Magisk.zip you moved in step 13 then reboot. once back into the rom, you will see a Magisk app, tap it and allow to update, the APK will install latest version of the manager.
More NOTES.
this must be done on a clean system. you need to wipe all data partitions to boot to system. re writing VBMETA causes encryption to break. until you reboot. so you lose everything Make a backup of your data partition on to your PC before doing anything.
its also recommended to have an update.zip of your current rom (which you can download from the post above), incase you need to reinstall the rom after flashing the new recovery or VBmeta.
OEM unlocking in the developer options is NOT needed. since you are not unlocking your bootloader. this step can be ignored.
I'll update this tutorial with newer steps if needed.
Thanks to those that created all these great tools.
@wzsx150 - for their version of TWRP
John Wu - for Magisk
@mslezak vbmeta_skip
If i've helped you root your device, please hit thanks.
Link ADBmini - zip updated with Magisk 21.4 zip
MD5 for ADBfastbootmini.zip: 0ad97a9ae1539b26ef78c849b169e807
I'm working on a process that will update to Android 11, through TWRP and root, without losing data. Much like a stock update.
I will update the thread once my tests are complete.
Hello. I can not flash (i cant even copy) the zip via TWRP. I see the storage device on my windows laptop. I have wipe data cache and dalvik, but it does not copy it and i can not restore my device. Help will be appreciated
josehdx said:
Hello. I can not flash (i cant even copy) the zip via TWRP. I see the storage device on my windows laptop. I have wipe data cache and dalvik, but it does not copy it and i can not restore my device. Help will be appreciated
Click to expand...
Click to collapse
Try putting update zip on a USB key and connect via OTG and flash this way. Moving files with TWRP for some reason corrupts or does not complete transfer.
Make sure to factory reset. If you're coming from a used update, backup your data partition and wipe everything. Then check to see if the partition is in fact empty. ( I noticed sometime my data partition did not erase)
Patrick Morgan said:
Try putting update zip on a USB key and connect via OTG and flash this way. Moving files with TWRP for some reason corrupts or does not complete transfer.
Make sure to factory reset. If you're coming from a used update, backup your data partition and wipe everything. Then check to see if the partition is in fact empty. ( I noticed sometime my data partition did not erase)
Click to expand...
Click to collapse
Thanks
Working fine after full data partition wipe.
I have an additioal question regarding further updates, and i would not want to open a new topic. so, after flashing the zip, i "lost" TWRP but i already have root access. I wonder if is possible to flash upcoming updates with the default recovery built in on the phone, if not, i would assume i need to install TWRP again.in any case, will side loading update make any problem with the current system? i hope my question and context is clear
As these are official ROMs, they will replace the recovery and remove root from the phone.
If you do not have root, flashing these zips from the system menu local update should work. But if you have root or TWRP it's better to flash through TWRP.
You could just flash TWRP again after flash, but I personally modify the zip and add the recovery to it to save me going into fastboot after each update.
Is it possible to install the US rom on a device with EU rom?
in the EU version I can't set the frame rate to 144 hz.
Darkvenum79 said:
Is it possible to install the US rom on a device with EU rom?
in the EU version I can't set the frame rate to 144 hz.
Click to expand...
Click to collapse
I've spoken with another EU rom user, that has the same issue before. it seems it was an error in the stock rom.
reinstalling 7.07 from the links above should fix your problem.
both 7.07 (the EU rom) and 8.07 (the US rom) are exactly the same. the only difference is the languages from what I can tell.
I have a silly question. Unfortunately i unlocked bootloader and i lost the fingerprint capability. I have tried many times to do the calibration without success. I wonder if a factory flash (EDM or any nubia tool) can restore the capability and then use this guide to do the rooting? Thanks
josehdx said:
I have a silly question. Unfortunately i unlocked bootloader and i lost the fingerprint capability. I have tried many times to do the calibration without success. I wonder if a factory flash (EDM or any nubia tool) can restore the capability and then use this guide to do the rooting? Thanks
Click to expand...
Click to collapse
No it wont.
There is a specific step by step that is required to get it functioning again. And it only survives until your next full wipe, which i assume you will do more often flashing non official roms.
I can grab the steps and edit this post for you.
Edit -
Prep.
have a black / very dark brown leather. (belt, wallet, etc)
a soft gel plaster / Bandaid
(something skin textured and in a pink / light beige colour) texture and colour are important.
First step is clear data in the infingerprint app in app info and remove permissionfor data memory - (you need to show system apps to find it)
- digit in call phone code:
*#9959#
(android 11 use Activity launcher (playstore) to enter fingerprint menu)
- uncheck performance checkbox , check only calibration checkbox
Steps -
1. Press start then wait.
2.Press next and with plaster / bandaid press on circle
3.Press next and use wallet / belt ( the display becomes black for black calibration)
4.Press next and use gel plaster / bandaid again but pinch it in so only the part with your finger touches the circle.
If you are lucky see success alert in green color
In system app in setting In-Display-Fingerprint allow access to data memory then reboot device.
Enjoy your Finger Print once more!
P.S. = do this procedure in a very dark room to improve the chances of it succeeding.
Thanks to qtr1st (Salem) and mikekrunk (Mike) for the steps and information.
josehdx said:
I have a silly question. Unfortunately i unlocked bootloader and i lost the fingerprint capability. I have tried many times to do the calibration without success. I wonder if a factory flash (EDM or any nubia tool) can restore the capability and then use this guide to do the rooting? Thanks
Click to expand...
Click to collapse
esy re-lock bootloader fingrperint work fine without calibration
---------- Post added at 12:13 PM ---------- Previous post was at 12:08 PM ----------
Patrick Morgan said:
TWRP and root guide for 5S - (these steps will NOT unlock your bootloader) - these steps use a bypass method to install a recovery without unlocking bootloader. the command below is to allow flashing of partitions. bootloader status is still locked after process is complete.
Pretty short step by step to get twrp and Magisk if you want, on your phone. (Red Magic 5S)
Note. if you already have ADB and fastboot drivers installed, this folder will work as is. if not I put a installer in the folder too to install a mini adb fastboot setup. which needs windows driver signing turned off (windows 8-10) this can be done by going to advanced startup and choosing to boot without driver signing.
1. Download zip file attached or mirrored
2. Extract to root of C: drive
3. open CMD prompt with admin privileges
4. CD to the ADB folder you extracted.
5. Connect your device in Fastboot mode (power off. hold volume down +Power until it vibrates. then release power but continue to hold volume down)
6. Once in fastboot mode, with cable connected to the computer run these commands
7. fastboot oem nubia_unlock NUBIA_NX659J (this allows you to flash the device partitions)
8. fastboot flash recovery TWRP-xxx.img (xxx being the version number of the TWRP image you choose to install)
9. fastboot flash vbmeta vbmeta_skip.img
10. reboot to recovery (from the fastboot menu) it should load TWRP
11. if TWRP does not ask you to keep recovery from being over written, go to advanced and choose disable overwrite TWRP. to keep TWRP as your recovery, and stop the system from re writing the stock recovery.
12. Magisk zips files are in the folder. copy to device and flash through twrp. and install the apk after boot. done twrp and root.
More NOTES.
this must be done on a clean system. you need to wipe all data partitions to boot to system. re writing VBMETA causes encryption to break. until you reboot. so you lose everything Make a backup of your data partition on to your PC before doing anything.
its also recommended to have a update.zip of your current rom (which you can download from the post above), incase you need to reinstall the rom after flashing the new recovery or VBmeta.
OEM unlocking in the developer options is NOT needed. since you are not unlocking your bootloader. this step can be ignored.
I'll update this tutorial with newer steps if needed.
Thanks to those that created all these great tools.
@wzsx150 - for their version of TWRP
John Wu - for Magisk
@mslezak vbmeta_skip
If i've helped you root your device, please hit thanks.
Link ADBmini
MD5 for ADBfastbootmini.zip: e49f162080c6a2124c243716546ad710
Click to expand...
Click to collapse
where is the link of twrp.img
sansha1211 said:
where is the link of twrp.img
Click to expand...
Click to collapse
Patrick Morgan said:
Link ADBmini
MD5 for ADBfastbootmini.zip: e49f162080c6a2124c243716546ad710
Click to expand...
Click to collapse
that file called Link ADBmini has all you need
Is it ok to flash Eu rom to my NA/asia rom?
After reboot it ask me for verify pin and now I can't load the TWRP.img Partition volume Full error help me please
Rai972 said:
After reboot it ask me for verify pin and now I can't load the TWRP.img Partition volume Full error help me please
Click to expand...
Click to collapse
reboot to bootloader by... power off device -> press and hold volume down and power button until you see the logo -> connect device to your computer then do the steps 7 to 12
also once you are in TWRP make sure you ... this must be done on a clean system. you need to wipe all data partitions to boot to system. re writing VBMETA causes encryption to break. until you reboot. so you lose everything Make a backup of your data partition on to your PC before doing anything.
7. fastboot oem nubia_unlock NUBIA_NX659J (this allows you to flash the device partitions)
8. fastboot flash recovery TWRP-xxx.img (xxx being the version number of the TWRP image you choose to install)
9. fastboot flash vbmeta vbmeta_skip.img
10. reboot to recovery (from the fastboot menu) it should load TWRP
11. if TWRP does not ask you to keep recovery from being over written, go to advanced and choose disable overwrite TWRP. to keep TWRP as your recovery, and stop the system from re writing the stock recovery.
12. Magisk zips files are in the folder. copy to device and flash through twrp. and install the apk after boot. done twrp and root.
Rai972 said:
After reboot it ask me for verify pin and now I can't load the TWRP.img Partition volume Full error help me please
Click to expand...
Click to collapse
if you have not removed your pin before flashing any of the roms. it asks you for YOUR own pin that you made when you setup the phone. so use your own pin.
the process of rooting your device, clears a security partition. (the VBmeta partiton)
this deletes the encryption you had on your phone. so the devices partitions are unaccessable and need to be wiped before you can boot to system.
you need to clear data. all data. then check in TWRP file browser if your data partition is clear. .. if you see folders with random letters its not been formatted correctly.
so, in the wipe menu on TWRP you should go into advanced and change the partition type to ext4 then back to f2fs to clear the partition of data.
once your phone is clear you should be able to wipe cache and davik then reboot to system for it to start like a factory reset.
sansha1211 said:
esy re-lock bootloader fingrperint work fine without calibration
---------- Post added at 12:13 PM ---------- Previous post was at 12:08 PM ----------
where is the link of twrp.img
Click to expand...
Click to collapse
How should i relock the bootloader? Via cmd, command doesn't work. Should i lock also via developer options?
josehdx said:
How should i relock the bootloader? Via cmd, command doesn't work. Should i lock also via developer options?
Click to expand...
Click to collapse
adb devices
adb reboot bootloader
fastboot devices
fastboot flashing lock
josehdx said:
How should i relock the bootloader? Via cmd, command doesn't work. Should i lock also via developer options?
Click to expand...
Click to collapse
via cmd -- fastboot flashing lock
After i reboot in TWRP and disable replace TWRP, i install magisk from a USB otg, and then i wipe all data, then i reboot system but it keeps opening TWRP in every reboot, i had to install Stock Rom to have my phone back but without root, what im doing wrong?? thanks
Edit: now it worked, tried a few times and worked don't know what failed

[HOWTO]/[ROM] [UNOFFCIAL] How to Flash Lineage OS 19.0

Here is a quick how-to guide to flash LineageOS 19.0 to the A51​
Disclaimer: I am not the maintainer of any of the files I link to here. I just wanted to share my experience to make the process of Flashing los19 to the a51 easier for others.
Prerequisites:
1. Unlocked Bootloader
This step is crucial. You need to unlock the bootloader of the A51 before trying any of this. If not, you are likely to brick your device.​1.1. Unlock developer mode by standard procedure: Settings > Info > Tab 7 times on build number​1.2. Enable USB debugging in Developer Options​1.3. Enable OEM unlocking in Developer Options -> To see OEM unlock option I needed to connect to my WIFI, then set the phone date manually to March 7th 2019. Only then the OEM unlock option became visible in Developer Options. Yes, this is super dumb and inconvenient...​1.4 After triggering OEM unlock option shutdown your phone.​1.5 Enter Download mode by: Pressing Volume+ and Volume - while at the same time plugging in the USB cable that is already in your PC.​1.6. To finally unlock bootloader, you will see a green screen on which you need to press Vol + for some time. THIS WILL VOID YOUR WARRANTY. It will also erase all data on your phone!​1.7 After reboot repeat steps 1.1. - 1.5. again. This time you can actually enter download mode by pressing Vol + shortly on the green screen.​
2. Flash Twrp
You can now flash TWRP via Odin. The TWRP img I used is here: https://www.mediafire.com/file/0h14t0263oujhna/TWRP-11-3.6.1-a51-20220321-1406-hotfix.tar/file. I flashed it as AP. Make sure to uncheck Auto reboot before flashing.​When flashing is complete hold Vol - and Power until reboot.​Immediately when rebooting hold Vol + and Power until Samsung logo appears, then let Power go but hold Vol + to enter TWRP.​
3. Actual Flashing:
3.1. Necessary Files:​Make sure to load all files necessary to your SD before flashing:​ChonDoe_Flasher, Disable_Dm_Verity, Multidisabler, LOS-Imagefile, Magisk(optional)​​As for the LOS Image I used this file here, which already includes gapps:​lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img​​If you don't want gapps pick an image that says "BvS" instead of "bgs"​​3.2. You need to move your LOS-Image to the same folder as ChonDoe_Flasher and rename the file to "system.img"​
3.3 Flashing Sequence:
In TWRP Follow this sequence:
3.3.1. Wipe data, dalvik, cache​3.3.2. flash disable_dm_verity​3.3.3. flash multidisabler​3.3.4. Wipe internal storage (Backup might be advisable, if you didn't format data anyways)​3.3.5. reboot recovery​3.3.6. flash chondone with lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img in the same folder renamed to system.mg​3.3.7. Wipe data​3.3.8. Reboot​
That should be it. First startup takes some time, your phone should boot to LOS 19.
4. Anger Management
If you softbrick your device you can try to go back to stock rom by accessing download mode and flashing it via Odin. Will take some fiddling around with the button combinations.
If you hardbrick your device don't hold me responsible and good luck to you!
Thanks to
Kyau Sana, Vadim Kupriyanov, Knoyan GTR-X and Sara Lins and other, from the telegram-group, who helped me figure out the process.
Reserved 1
Reserved 2
Lineage 19 flash worked but after flashing my TWRP recovery bootloops (flashing twrp logo).
TWRP that loops is twrp-a51-3.5.0_10-1_ianmacd.
Do you have a working TWRP for this version of Lineage ?
Tried TWRP v3.6.1 A51 tree but it doesn't work and boots into download mode with "DT Entry not found / DT Load Failed / VB Meta sign errors"
exault said:
Lineage 19 flash worked but after flashing my TWRP recovery bootloops (flashing twrp logo).
TWRP that loops is twrp-a51-3.5.0_10-1_ianmacd.
Do you have a working TWRP for this version of Lineage ?
Tried TWRP v3.6.1 A51 tree but it doesn't work and boots into download mode with "DT Entry not found / DT Load Failed / VB Meta sign errors"
Click to expand...
Click to collapse
I added a download link to the TWRP img I used to my initial post. Let me know if it works.
cheers
DerTopher said:
I added a download link to the TWRP img I used to my initial post. Let me know if it works.
cheers
Click to expand...
Click to collapse
Nope TWRP does not work. When using the one you linked (as all other 3.6.1 ones) it just jumps back to download mode with DT Entry not found & VBMeta not signed errors.
ALL sensors ok ?
Fingerprint ok ? In this ROM
exault said:
Nope TWRP does not work. When using the one you linked (as all other 3.6.1 ones) it just jumps back to download mode with DT Entry not found & VBMeta not signed errors.
Click to expand...
Click to collapse
Sorry to hear mate. Unfortunately I cannot hell you solve this issue. There is a telegram channel for custom roms on the A51 with many motivated people. One of them might have the answer you need!
See: https://t.me/samsunga51
If you find it, please post it, so others can profit from it. With your agreement I would also like to add info about the solution - should you find it - to my initial post.
hacker812c said:
ALL sensors ok ?
Fingerprint ok ? In this ROM
Click to expand...
Click to collapse
Don't know about fingerprint as I do not want to provide biometric data to my phone. Maybe someone else using the ROM can answer this; Or you, if you decide to flash it post your results.
Apart from that I have not had any problems with the ROM apart from the following:
-The resulotion of the native lineage camera app is not satisfactory. When I find an app that works better, I'll let you know.
- Restarting the phone after empty battery requires a soft reset sometimes (power+vol -)
-> A solution to this problem might be given in this post. Will try it later.
Thank you, @DerTopher , but unfortunately the link to your LOS file does not work any more. How do I get the file now?
THIS GUIDE ONLY WORKS ON ANDROID 12!!!
sunnyy15 said:
I have concluded all my experiments, and now I can confirm that the "twrp-a51-3.5.0_10-1_ianmacd.tar" on this website only works for Android 10 as instructed by Admin. This does not for Android 11. For Android 11 you have to flash a different file called "Twrp+vbmeta_A11.tar". Details are given in the following link: https://forum.xda-developers.com/t/...-sm-a515f-one-ui-3-0-dub1-android-11.4231543/
Click to expand...
Click to collapse
@DerTopher , please change your OP to specify that this guide ONLY works for Android 12. I just bootlooped my device when trying this on Android 10 stock firmware
See this excelent post for more info: https://forum.xda-developers.com/t/...-ui-2-5-ctj1-android-10.4213443/post-84750027
Anyone knows how to remove the native SU, so that magisk doesn't complain about "abnormal state" su file ?
when i flash something in twrp i have an error failed to mount '/odm4 no such file or directory Can some help me please i am stuck here
DerTopher said:
Here is a quick how-to guide to flash LineageOS 19.0 to the A51​
Disclaimer: I am not the maintainer of any of the files I link to here. I just wanted to share my experience to make the process of Flashing los19 to the a51 easier for others.
Prerequisites:
1. Unlocked Bootloader
This step is crucial. You need to unlock the bootloader of the A51 before trying any of this. If not, you are likely to brick your device.​1.1. Unlock developer mode by standard procedure: Settings > Info > Tab 7 times on build number​1.2. Enable USB debugging in Developer Options​1.3. Enable OEM unlocking in Developer Options -> To see OEM unlock option I needed to connect to my WIFI, then set the phone date manually to March 7th 2019. Only then the OEM unlock option became visible in Developer Options. Yes, this is super dumb and inconvenient...​1.4 After triggering OEM unlock option shutdown your phone.​1.5 Enter Download mode by: Pressing Volume+ and Volume - while at the same time plugging in the USB cable that is already in your PC.​1.6. To finally unlock bootloader, you will see a green screen on which you need to press Vol + for some time. THIS WILL VOID YOUR WARRANTY. It will also erase all data on your phone!​1.7 After reboot repeat steps 1.1. - 1.5. again. This time you can actually enter download mode by pressing Vol + shortly on the green screen.​
2. Flash Twrp
You can now flash TWRP via Odin. The TWRP img I used is here: https://www.mediafire.com/file/0h14t0263oujhna/TWRP-11-3.6.1-a51-20220321-1406-hotfix.tar/file. I flashed it as AP. Make sure to uncheck Auto reboot before flashing.​When flashing is complete hold Vol - and Power until reboot.​Immediately when rebooting hold Vol + and Power until Samsung logo appears, then let Power go but hold Vol + to enter TWRP.​
3. Actual Flashing:
3.1. Necessary Files:​Make sure to load all files necessary to your SD before flashing:​ChonDoe_Flasher, Disable_Dm_Verity, Multidisabler, LOS-Imagefile, Magisk(optional)​​As for the LOS Image I used this file here, which already includes gapps:​lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img​​If you don't want gapps pick an image that says "BvS" instead of "bgs"​​3.2. You need to move your LOS-Image to the same folder as ChonDoe_Flasher and rename the file to "system.img"​
3.3 Flashing Sequence:
In TWRP Follow this sequence:
3.3.1. Wipe data, dalvik, cache​3.3.2. flash disable_dm_verity​3.3.3. flash multidisabler​3.3.4. Wipe internal storage (Backup might be advisable, if you didn't format data anyways)​3.3.5. reboot recovery​3.3.6. flash chondone with lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img in the same folder renamed to system.mg​3.3.7. Wipe data​3.3.8. Reboot​
That should be it. First startup takes some time, your phone should boot to LOS 19.
4. Anger Management
If you softbrick your device you can try to go back to stock rom by accessing download mode and flashing it via Odin. Will take some fiddling around with the button combinations.
If you hardbrick your device don't hold me responsible and good luck to you!
Thanks to
Kyau Sana, Vadim Kupriyanov, Knoyan GTR-X and Sara Lins and other, from the telegram-group, who helped me figure out the process.
Click to expand...
Click to collapse
Hello friends, how are you? Could someone post the ROM link again, the link is broken.
lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS
dmudo said:
Hello friends, how are you? Could someone post the ROM link again, the link is broken.
lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS
Click to expand...
Click to collapse
Andy Yan's personal builds // GSI
Download Andy Yan's personal builds // GSI for free. None
sourceforge.net
i have a question
in step 3.3.6. flash chondone with lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img in the same folder renamed to system.mg
i try to flash chondoe and i tried to add de system.img, and it prompt me to what partition
This are the partitions that apears to me
- Boot
- DTBO Image
- Optics Image
- Prism Image
- Recovery
- Param
- VBmeta Samsung
- VBMeta Samsung
- Super (system vendor product odm)
Does anyone know where ?
DerTopher said:
Here is a quick how-to guide to flash LineageOS 19.0 to the A51​
Disclaimer: I am not the maintainer of any of the files I link to here. I just wanted to share my experience to make the process of Flashing los19 to the a51 easier for others.
Prerequisites:
1. Unlocked Bootloader
This step is crucial. You need to unlock the bootloader of the A51 before trying any of this. If not, you are likely to brick your device.​1.1. Unlock developer mode by standard procedure: Settings > Info > Tab 7 times on build number​1.2. Enable USB debugging in Developer Options​1.3. Enable OEM unlocking in Developer Options -> To see OEM unlock option I needed to connect to my WIFI, then set the phone date manually to March 7th 2019. Only then the OEM unlock option became visible in Developer Options. Yes, this is super dumb and inconvenient...​1.4 After triggering OEM unlock option shutdown your phone.​1.5 Enter Download mode by: Pressing Volume+ and Volume - while at the same time plugging in the USB cable that is already in your PC.​1.6. To finally unlock bootloader, you will see a green screen on which you need to press Vol + for some time. THIS WILL VOID YOUR WARRANTY. It will also erase all data on your phone!​1.7 After reboot repeat steps 1.1. - 1.5. again. This time you can actually enter download mode by pressing Vol + shortly on the green screen.​
2. Flash Twrp
You can now flash TWRP via Odin. The TWRP img I used is here: https://www.mediafire.com/file/0h14t0263oujhna/TWRP-11-3.6.1-a51-20220321-1406-hotfix.tar/file. I flashed it as AP. Make sure to uncheck Auto reboot before flashing.​When flashing is complete hold Vol - and Power until reboot.​Immediately when rebooting hold Vol + and Power until Samsung logo appears, then let Power go but hold Vol + to enter TWRP.​
3. Actual Flashing:
3.1. Necessary Files:​Make sure to load all files necessary to your SD before flashing:​ChonDoe_Flasher, Disable_Dm_Verity, Multidisabler, LOS-Imagefile, Magisk(optional)​​As for the LOS Image I used this file here, which already includes gapps:​lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img​​If you don't want gapps pick an image that says "BvS" instead of "bgs"​​3.2. You need to move your LOS-Image to the same folder as ChonDoe_Flasher and rename the file to "system.img"​
3.3 Flashing Sequence:
In TWRP Follow this sequence:
3.3.1. Wipe data, dalvik, cache​3.3.2. flash disable_dm_verity​3.3.3. flash multidisabler​3.3.4. Wipe internal storage (Backup might be advisable, if you didn't format data anyways)​3.3.5. reboot recovery​3.3.6. flash chondone with lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img in the same folder renamed to system.mg​3.3.7. Wipe data​3.3.8. Reboot​
That should be it. First startup takes some time, your phone should boot to LOS 19.
4. Anger Management
If you softbrick your device you can try to go back to stock rom by accessing download mode and flashing it via Odin. Will take some fiddling around with the button combinations.
If you hardbrick your device don't hold me responsible and good luck to you!
Thanks to
Kyau Sana, Vadim Kupriyanov, Knoyan GTR-X and Sara Lins and other, from the telegram-group, who helped me figure out the process.
Click to expand...
Click to collapse
3.3.7 format data or wipe?

Categories

Resources