Related
Unofficial TWRP for Moto G5S Plus (Sanders)
Additional Features over Official TWRP:
Supports flashing of both 32bit and 64bit ROMs and Kernels.
OREO Images/ROMs support.
Decryption and Encryption support.
No SuperSU by default.
No TWRP app.
No HTC Dumlock cruft.
Updated pigz compressor (slightly faster and more tolerant of corruption).
NTFS support(Both Read and Write).
Covers more partitions for nandroid backup (OEM, FSG and FSC).
Experimental support for SD cards that are partitioned for partial adopted storage and partial removable storage.
Faster I/O performance.
Fixed Gapps/aroma freeze issues.
IMPORTANT!!! : READ INSTRUCTIONS CAREFULLY BEFORE PROCEEDING TO FLASHING PROCESS..!!
At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either Magisk or flash any of the verity disabler zips available on xda.
Force encryption is enabled by default in stock OS and twrp will successfully decrypt /data at first boot if all goes well
If in case decryption doesn't go fine, twrp will popup a dialog box asking for password and that means decryption went wrong and you would need to wipe data once via twrp wipe options and reboot back to twrp for functioning of /data
Flashing Instructions:
Using Existing TWRP:
Reboot to recovery > Click on Install > Install Image > recovery > select recovery image and flash > reboot to recovery
Other Methods(Fastboot) :
Make sure you have unlocked bootloader
Reboot to bootloader
Enter following command in terminal: fastboot flash recovery twrp-****.img (if you want permanent flash) or fastboot boot twrp-****.img (if you want temporary boot)
Incase your device is encrypted (while coming from stock rom), Follow these steps to decrypt:
Reboot to recovery > cancel the password prompt > mount all partitions > Format Data/Userdata (on f2fs) > Reboot Recovery > Mount all partitions again > Flash Magisk > Reboot
Now you are free to use Stock ROM (Decrypted) or Flash any custom rom you want.
Download Links: https://www.androidfilehost.com/?w=files&flid=216298
TWRP Themes: Check 3rd post
Known Issues: None || Report if you find any.
XDA:DevDB Information
[RECOVERY][UNOFFICIAL][Sanders] TWRP-3.2.1-r20 (64bit Supported!), Tool/Utility for the Moto G5S Plus
Contributors
CheckYourScreen
Source Code: https://github.com/CheckYourScreen/twrp_device_motorola_sanders
Version Information
Status: Stable
Current Stable Version: r20
Stable Release Date: 2018-04-04
Created 2017-10-26
Last Updated 2018-04-04
|| Changelog ||
r20:
Fixed Encryption support on custom roms.
Updated kernel
Updated build fingerprint for latest bootloader support.
Reverted pigz changes.
Switched back to original twrp themes. (TWRP Themes can be found in 3rd post )
Various bug fixes and improvements.
r16:
Fixed compatibility with New Bootloader (C2.07-December patch)
Merged october patches in kernel.
Various twrp upstream patches and fixes.
Fixed remote wipe process (Earlier remote wipe issued from play account wasnt processed due to twrp)
r15:
Added 64bit Support (You can flash both 32bit/64bit roms or kernels with it).
Fixed Encryption Support! (No need to format data to decrypt and mount).
Updated to 3.2.1 upstream changes with full oreo support.
Remove android reboot during password check on multiple wrong inputs.
r9:
Fixed F2FS mount issues(You can flash magisk modules or SuperSu now).
Enabled NTFS Write Support (You can make backups on sdcard/pendrives formatted on NTFS).
Fixed size of various partitions.
Switched to LZMA compression to decrease size.
r7: Initial Public Release
|| Themes ||
Here are some of the twrp themes:
Preview images: https://photos.app.goo.gl/DLrfDseGzfxE8Uq93
Download link: https://androidfilehost.com/?w=files&flid=233551
:good:
Only one that has actually be working for me ever since I got the phone. Thank you for your efforts.
this seems to suffer from the same thing the stock rom/kernel suffers from, the weird f2fs bug that makes certain mounts fail. geneticengineer has shared a kernel that fixes this in stock rom , maybe you could get in touch with him about how he updated f2fs
Thank you for your work, this seems to work well on my device. If you would like to swap the kernel, I posted a newer firmware NPS26.116-45 here:https://forum.xda-developers.com/showpost.php?p=74325160&postcount=33
revengineer said:
Thank you for your work, this seems to work well on my device. If you would like to swap the kernel, I posted a newer firmware NPS26.116-45 here:https://forum.xda-developers.com/showpost.php?p=74325160&postcount=33
Click to expand...
Click to collapse
But its for xt1806 only i think. Not real help. The most user here are outside usa.
Schrotty35 said:
But its for xt1806 only i think. Not real help. The most user here are outside usa.
Click to expand...
Click to collapse
Well my guess is that the kernel in the present twrp is from the -26 firmware posted in the other thread. That firmware was US Retail also. The OP in the other thread states in can be used on other models. But I am not going to tell you that because I do not know. I have not found any other firmware for the sanders model.
Ae3NerdGod said:
this seems to suffer from the same thing the stock rom/kernel suffers from, the weird f2fs bug that makes certain mounts fail. geneticengineer has shared a kernel that fixes this in stock rom , maybe you could get in touch with him about how he updated f2fs
Click to expand...
Click to collapse
Afaik it doesnt affect TWRP, you just need to be on a custom kernel if you are running stock rom.
Twrp has nothing to do with it.
If you face any problem flashing anything then post a screenshot or log.
revengineer said:
Thank you for your work, this seems to work well on my device. If you would like to swap the kernel, I posted a newer firmware NPS26.116-45 here:https://forum.xda-developers.com/showpost.php?p=74325160&postcount=33
Click to expand...
Click to collapse
Schrotty35 said:
But its for xt1806 only i think. Not real help. The most user here are outside usa.
Click to expand...
Click to collapse
Stock kernel is same in both the firmwares.
-45 is just for US variant, i dont recommend you to even flash that firmware on other variants.
CheckYourScreen said:
Afaik it doesnt affect TWRP, you just need to be on a custom kernel if you are running stock rom.
Twrp has nothing to do with it.
If you face any problem flashing anything then post a screenshot or log.
Click to expand...
Click to collapse
but i have a custom stock kernel, and things that fail in TWRP work in flashfire or magiskmanager
its mostly magisk modules im having problems with, ill reproduce an error when i get the chance
Ae3NerdGod said:
but i have a custom stock kernel, and things that fail in TWRP work in flashfire or magiskmanager
its mostly magisk modules im having problems with, ill reproduce an error when i get the chance
Click to expand...
Click to collapse
Flash the magisk module via twrp > take screenshot when flashing completes > go to advance section of twrp and take recovery log > reboot system > send that screenshot and recovery log here.
CheckYourScreen said:
Flash the magisk module via twrp > take screenshot when flashing completes > go to advance section of twrp and take recovery log > reboot system > send that screenshot and recovery log here.
Click to expand...
Click to collapse
will do, it happens with every magisk package i try. they used to fail in stock too till i used geneticengineers kernel from telegram now they work
didnt know you could screenshot in recovery, i assume its the same buttons
Ae3NerdGod said:
will do, it happens with every magisk package i try. they used to fail in stock too till i used geneticengineers kernel from telegram now they work
didnt know you could screenshot in recovery, i assume its the same buttons
Click to expand...
Click to collapse
Yes, same buttons to take a screenshot in TWRP
TWRP backup is frozen at 13% completed. The progress bar is still showing its animation.
I unlocked the bootloader, and then rebooted. Android came up with the language selection screen. I powered off, connected the phone to the PC, and booted into TWRP (not flashed yet):
Code:
fastboot boot twrp-3.1.1-sanders-r7.img
I did not let TWRP format /data.
Then I started a backup, selecting all partitions, so that I could always go back after flashing TWRP and Magisk.
Does anyone know why backup is stuck at 13%? Last log line says "Backing up System..."
I tapped "Cancel" after two hours. That stopped the progress bar animation, but not the backup itself.
BTW: I used TWRP from this thread, the one in another thread freezes at the TWRP boot logo.
Edit: after two hours I killed the backup by powering down (the only way it seemed). On retry it froze at 21%.
Edit 2: Retried, this time backing up everything except system. No problem. I then tried to backup system. Frozen at 1%. What is the problem here?
Edit 3: Finally, a complete backup of system! Only one to go: system_image. But unfortunately that froze at 0%. Every subsequent try freezes at 1666MB (40%). The card has over 30GB free. I tried backup to USB-OTG, but that also froze.
gewe said:
TWRP backup is frozen at 13% completed. The progress bar is still showing its animation.
I unlocked the bootloader, and then rebooted. Android came up with the language selection screen. I powered off, connected the phone to the PC, and booted into TWRP (not flashed yet):
Code:
fastboot boot twrp-3.1.1-sanders-r7.img
I did not let TWRP format /data.
Then I started a backup, selecting all partitions, so that I could always go back after flashing TWRP and Magisk.
Does anyone know why backup is stuck at 13%? Last log line says "Backing up System..."
I tapped "Cancel" after two hours. That stopped the progress bar animation, but not the backup itself.
BTW: I used TWRP from this thread, the one in another thread freezes at the TWRP boot logo.
Edit: after two hours I killed the backup by powering down (the only way it seemed). On retry it froze at 21%.
Edit 2: Retried, this time backing up everything except system. No problem. I then tried to backup system. Frozen at 1%. What is the problem here?
Edit 3: Finally, a complete backup of system! Only one to go: system_image. But unfortunately that froze at 0%. Every subsequent try freezes at 1666MB (40%). The card has over 30GB free. I tried backup to USB-OTG, but that also froze.
Click to expand...
Click to collapse
Might be due to data partition being encrypted, you cant write anything in it without decrypting it first.
Format data and reboot recovery, then make the backup. You can flash magisk after taking the backup.
Btw r9 new release on its way with some really important changes
CheckYourScreen said:
Might be due to data partition being encrypted, you cant write anything in it without decrypting it first.
Format data and reboot recovery, then make the backup. You can flash magisk after taking the backup.
Btw r9 new release on its way with some really important changes
Click to expand...
Click to collapse
I was not trying to write the backup to the data partition, but to external SD card (tried OTG-USB as well without success).
I have flashed TWRP, formatted the data partition, and flashed Magisk. I have not tried to create a new backup yet. First I want to find out why Magisk does not pass the Safetynet check.
Can't wait to see what r9 brings. Thanks for your efforts. :good:
gewe said:
I was not trying to write the backup to the data partition, but to external SD card (tried OTG-USB as well without success).
I have flashed TWRP, formatted the data partition, and flashed Magisk. I have not tried to create a new backup yet. First I want to find out why Magisk does not pass the Safetynet check.
Can't wait to see what r9 brings. Thanks for your efforts. :good:
Click to expand...
Click to collapse
Magisk won't pass safety net with stock boot.img (kernel). Here is a modified kernel.
https://forum.xda-developers.com/showthread.php?p=73930507
After flashing new kernel Magisk passes no problem.
Sent by way of magic
lilcdroid said:
Magisk won't pass safety net with stock boot.img (kernel). Here is a modified kernel.
https://forum.xda-developers.com/showthread.php?p=73930507
After flashing new kernel Magisk passes no problem.
Sent by way of magic
Click to expand...
Click to collapse
When I flash this my WiFi stops working completely. I'm running aosp extended rom. I'm not sure if I can achieve battery life as good as I can on the stock ROM as I can on this one so im not sure what I should do about that..
Brycearuuni said:
When I flash this my WiFi stops working completely. I'm running aosp extended rom. I'm not sure if I can achieve battery life as good as I can on the stock ROM as I can on this one so im not sure what I should do about that..
Click to expand...
Click to collapse
Sorry I wasn't aware you weren't still on stock. That kernel will only work on stock. I would verify with the maintainer of AOSP extended ROM that the kernel is patched to work with Magisk.
Sent by way of magic
Guys, as all are aware of GSI images available but cannot flash, then follow the steps....
A. Clean Install :-
1. install modified redwolf(link= https://drive.google.com/uc?authuser=5&id=1H7znKopLAL2u0JJEIPb8ANayAhtTB-xz&export=download) or modified TWRP(link= https://sourceforge.net/projects/te...Treble/TWRP-3.2.1-0-land(Treble).img/download)...
2. go to settings in recovery and enable treble mode...
3. install any treble ROM of your want...
4. go to wipe-> swipe to factory reset...
5. go to install-> select images->select the file-> flash type - system image...
6. wait for flashing system...
7. reboot...
8. set up device...
9. go to recovery and flash magisk and other stuffs you want(Magisk treble link= https://androidfilehost.com/?fid=962187416754478287)
B. Dirty Install:-
1. go to recovery->wipe->advanced wipe-> system, cache , dalvik
2. follow steps from A.5 to A.9..
Non-TWRP flash:-
1. go to fastboot mode...
2. in adb, type fastboot devices and check if it's showing...
3. type fastboot flash system <.img> type the link of the file in your computer...
4. type fastboot reboot...
Tell if it worked...I've did this flashed crdroid treble then flashed pixel experience GSI...
Hit thanks if it worked....
Reserved
Is VoLTE working with GSI image?
Falcon_fan said:
Is VoLTE working with GSI image?
Click to expand...
Click to collapse
Pixel experience didn't work for me... Not even adding ims working... Alas...
What does Dirty Install mean? Does it mean i wont lose any app installed in my phone?
Do we need to go setting in recovery and enable Treble mode just like clean install?
I am currently running official stock rom
---------- Post added at 04:48 PM ---------- Previous post was at 04:47 PM ----------
What does Dirty Install mean? Does it mean i wont lose any app installed in my phone?
Do we need to go setting in recovery and enable Treble mode just like clean install?
I am currently running official stock rom. Btw my phone is unlocked bootloader
Trovies said:
What does Dirty Install mean? Does it mean i wont lose any app installed in my phone?
Do we need to go setting in recovery and enable Treble mode just like clean install?
I am currently running official stock rom
---------- Post added at 04:48 PM ---------- Previous post was at 04:47 PM ----------
What does Dirty Install mean? Does it mean i wont lose any app installed in my phone?
Do we need to go setting in recovery and enable Treble mode just like clean install?
I am currently running official stock rom. Btw my phone is unlocked bootloader
Click to expand...
Click to collapse
Dirty install means you can install ROM without losing data... It is only available if you want to upgrade your ROM not changing the ROM...
Yes enabling treble mode is mandatory...
First time you need clean install...
So first install the twrp, then format data... It'll erase your internal storage... Mandatory if you are coming from miui otherwise you'll face encryption problem...
Format data then install any treble ROM no matters but keep in mind that it must be either GSI or any treble or non treble ROM for our device...
SKA97 said:
Dirty install means you can install ROM without losing data... It is only available if you want to upgrade your ROM not changing the ROM...
Yes enabling treble mode is mandatory...
First time you need clean install...
So first install the twrp, then format data... It'll erase your internal storage... Mandatory if you are coming from miui otherwise you'll face encryption problem...
Format data then install any treble ROM no matters but keep in mind that it must be either GSI or any treble or non treble ROM for our device...
Click to expand...
Click to collapse
After install TWRP,do i need to disable dm verity? And format data means wipe system, vendor, data, cache, dalvik? Also after flash new rom, some guides tell to flash lazy flasher, is it still necessary?
What's the different between GSI and Treble rom? I know pixel experience is treble rom. But GSI? Any example?
Trovies said:
After install TWRP,do i need to disable dm verity? And format data means wipe system, vendor, data, cache, dalvik? Also after flash new rom, some guides tell to flash lazy flasher, is it still necessary?
What's the different between GSI and Treble rom? I know pixel experience is treble rom. But GSI? Any example?
Click to expand...
Click to collapse
dm verity is for flashing miui recovery ROMs, not required for custom ROMs...
format data means like formatting a pendrive... it'll wipe everything in it... excluding some root system core files and recovery stuffs...
lazy flasher is dm verity flasher... as said its always for miui ROMs... some says to flash after installing xposed which is wrong...
you can keep it... just in case you see bootlloop which is a dream...:laugh:
Treble=ROM containing vendor files for a device(for flashing GSI)
GSI= generic system image which is a universal file which doesnt contain vendor files, so you need to flash a treble ROM before flashing a GSI so that it boots up...
there's pixel experience gsi image available which you can only flash if there's any treble ROM pre installed...
Hi, I tried asop gsi over pixel experience treble rom, just for fun ?
Phone boot, but no GSM network, no Sim card found... All the rest looks to be OK...
What I've done wrong?
Any idea?
lcarolo said:
Hi, I tried asop gsi over pixel experience treble rom, just for fun
Phone boot, but no GSM network, no Sim card found... All the rest looks to be OK...
What I've done wrong?
Any idea?
Click to expand...
Click to collapse
Have you factory data reset before installing ROM??? Then it should work... Just in case of you still face issue then use lineage as base...
SKA97 said:
Have you factory data reset before installing ROM??? Then it should work... Just in case of you still face issue then use lineage as base...
Click to expand...
Click to collapse
Tried resurrection remix and network works, but home don't... Need clean data maybe, no time to try... Maybe later, I think when full whipe it should work.
By the way, as we have good compiled up to date rom, it is not really useful for now...
Thanks for the guide. I have some doubts.
1.My device is currently running on los15.1(Rooted with magisk), can i do dirty flash?
2.Will Google release gsi for official oreo-treble devices?
3.Assume my device is running on RR-gsi now i want to flash another gsi, do i have to perform a clean flash or dirty flash?
Hello, I am newbie yet so I am asking if anyone can explain the vendor's use, and what do I get from installing them.
Thank you for your time
Now almost roms here includes custom vendor. So you need firmware only.
https://xiaomifirmwareupdater.com/vendor/beryllium/
And here's custom rom installation process
Flash rom
Flash firmware
Gapps(optional)
Dfe(if you don't want it to be encrypted)
Magisk(optional)
That's it. No need to know more.
nasos_Gr said:
Hello, I am newbie yet so I am asking if anyone can explain the vendor's use, and what do I get from installing them.
Thank you for your time
Click to expand...
Click to collapse
Miui decided to use MODIFIED VENDOR IMAGE hence POCO F1 gets a modified vendor image for Android Pie-based Project Treble GSIs
what was the impact?
custom roms couldn't be flashed (booted) if you don't flash the modified vendor image from twrp
even today when most of the roms have their own vendor you still need to flash the vendor+firmware (atleast)
Developer Akhil Narang started collecting all releases at
https://mirror.akhilnarang.me/MIUI/beryllium/
currently I am using 9.6.27-9.0 which is working best for me, 10.3.6 image made my batter drainage high (atleast i noticed)
I am on HAVOC2.8 and this is how i did it
1. flashed TWRP 3.3.1 unofficial (download it from HERE ) ref Reference - as official twrp has TOUCH driver issues. this one worked with me very well
2. I wiped /data, /system then
3. flashed VENDOR.zip from HERE
4. FLASHED CUSTOM ROM (i use HAVOC2.8)
5. FLASHED DFE HERE - REFERENCE
6. FLASHED GOOGLE APPS ( GAPPS.ORG) ( ARM64>9.0MicroPackage)
7. Flash Kernel ( OPTIONAL- havoc uses shadow kernel , i feel optimus drunk kernel is better, battery and 4g connectivity) even Franco Kernel is very good
8. FLASHING MAGISK19.3
9. when i was on havoc2.7, by using MIGRATE, it made flashable zip of my APPS+DATA, stored in internalStorage, and now I will FLASH that file., Mine size goes to 2gb you can get it from HERE
10. WIPE CACHE/DELVIK
11. REBOOT
fire reboot may go in to bootloop and then second reboot may take a while and finally you should see Pixel Setup asking google accounts and info etc
-----------------------
extraa
once after you finish setup! don't RESTORE APPS from PLAYSTORE, (download only license apk, in my case I have purchases many apps from playstore and saperate license info is always appear in intial setup! SELECT THOSE ONLY)
ONCE playstore is DONE downloading all your selected (fewer) apps, and MAGISK ROOT is working...... put device on AIRPLANE MODE
FROM DROP DOWN Notification panel, CLICK MIGRATE, and it will prompt you what do you wana restore from your previouce ROM to newly flashed HAVOC ..APPS+SETTINGS+PERMISSION+DATA etc - migrate restoration may take upto 30 mins,
once done, uninstall from system and reboot device!
REMEMBER I DONOT RECOMEND MIGRATE TRICK FOR WHATSAPP, it doesn't work properly and NOTIFICATION ISSUES with BLANK DP observed by me whenever I forcely re-instated whatsapp by migrate!
Martensite said:
Now almost roms here includes custom vendor. So you need firmware only.
https://xiaomifirmwareupdater.com/vendor/beryllium/
And here's custom rom installation process
Flash rom
Flash firmware
Gapps(optional)
Dfe(if you don't want it to be encrypted)
Magisk(optional)
That's it. No need to know more.
Click to expand...
Click to collapse
I understand but I have installed some custom Roms without finding vendor image and still it works perfect.
And do I need to install this image every time I flash a new ROM?
Thanks
nasos_Gr said:
I understand but I have installed some custom Roms without finding vendor image and still it works perfect.
And do I need to install this image every time I flash a new ROM?
Thanks
Click to expand...
Click to collapse
Flashing custom roms will not wipe anything, so the vendor is still there. And firmwares too.
I flashed Mi 10 Indian with Xiaomi.eu Miui 12 beta. Now i want to back to Stock Miui 11 but when i use Mi Flash Tool Its give
'antirollback check error'. there is any way to back Miui 11 stock
rashmi0733 said:
I flashed Mi 10 Indian with Xiaomi.eu Miui 12 beta. Now i want to back to Stock Miui 11 but when i use Mi Flash Tool Its give
'antirollback check error'. there is any way to back Miui 11 stock
Click to expand...
Click to collapse
https://www.xda-developers.com/xiaomi-anti-rollback-protection-brick-phone/
Format phone viai TWRP, install any ROM you want!
head_djmusic said:
Format phone viai TWRP, install any ROM you want!
Click to expand...
Click to collapse
thank but i read some ware :if you have anti rollback protection than you should not install stock rom viai TWRP its hard brick your phone"
so i want to know you try this before and its 100% safe use TWRP
how to install xiaomi.eu on Indian Mi 10
rashmi0733 said:
thank but i read some ware :if you have anti rollback protection than you should not install stock rom viai TWRP its hard brick your phone"
so i want to know you try this before and its 100% safe use TWRP
Click to expand...
Click to collapse
Hi rashmi0733, can u explain me how to install xiaomi.eu on Indian Mi 10
How to install xiaomi.eu on Indian Mi 10
rashmi0733 said:
I flashed Mi 10 Indian with Xiaomi.eu Miui 12 beta. Now i want to back to Stock Miui 11 but when i use Mi Flash Tool Its give
'antirollback check error'. there is any way to back Miui 11 stock
Click to expand...
Click to collapse
How to install xiaomi.eu on Indian Mi 10
rashmi0733 said:
thank but i read some ware :if you have anti rollback protection than you should not install stock rom viai TWRP its hard brick your phone"
so i want to know you try this before and its 100% safe use TWRP
Click to expand...
Click to collapse
Hi.
Do it like this, install TWRP and then the operating system of your choice. There is also the question of how you could install the ROM without TWRP.
Hardbrick with TWRP, never, I don't think so.
I have now easily shot my device 20 times and put it on again and again, definitely shot 100 devices over 10,000 times over the years and never suffered a hard brick.
You can do it, otherwise the heroes will help you here. :highfive:
sudhakar.ksvn said:
Hi rashmi0733, can u explain me how to install xiaomi.eu on Indian Mi 10
Click to expand...
Click to collapse
Unlock Bootloader
flash TWRP
boot Twrp
format Data
copy rom on phone
install rom
reboot and enjoy new rom
Thank For all suggestion i found one way to back stock Miui 11 without twrp
its working now i installed miui 11 and lock bootloader again.
rashmi0733 said:
Thank For all suggestion i found one way to back stock Miui 11 without twrp
its working now i installed miui 11 and lock bootloader again.
Click to expand...
Click to collapse
Oh really nice!
Do you mind to share your solution?
I don't need it but it's the purpose of forum ....
Greetings
Failed to mount '/system_root'
rashmi0733 said:
Unlock Bootloader
flash TWRP
boot Twrp
format Data
copy rom on phone
install rom
reboot and enjoy new rom
Click to expand...
Click to collapse
thanks for ur reply, bur i am getting .....
Updater process ended with ERROR: 7
Failed to mount '/system_root' ( No such file or directory)
can u help me regarding this, what twrp version have u used
sudhakar.ksvn said:
thanks for ur reply, bur i am getting .....
Updater process ended with ERROR: 7
Failed to mount '/system_root' ( No such file or directory)
can u help me regarding this, what twrp version have u used
Click to expand...
Click to collapse
i Used this TWRP
https://androidfilehost.com/?fid=4349826312261728614
https://gsmhostingfiles.com/index.php?a=downloads&b=file&id=14217
sudhakar.ksvn said:
thanks for ur reply, bur i am getting .....
Updater process ended with ERROR: 7
Failed to mount '/system_root' ( No such file or directory)
can u help me regarding this, what twrp version have u used
Click to expand...
Click to collapse
Hi,
this happens because your system partition is "broken".
If you go to "Wipe" and select "Format Data" there it will delete all partitions and the system of your device.
Then you start again in the TWRP and connect the device via USB to a PC or via OTG to a stick on which you have the operating system of your choice and drag it to your device.
Then select the ZIP / OS in the TWRP under "Install" and have it installed. It also creates the new partitions that he could not find with you.
I wish you success:fingers-crossed:
Ner0o1 said:
Hi,
this happens because your system partition is "broken".
If you go to "Wipe" and select "Format Data" there it will delete all partitions and the system of your device.
Then you start again in the TWRP and connect the device via USB to a PC or via OTG to a stick on which you have the operating system of your choice and drag it to your device.
Then select the ZIP / OS in the TWRP under "Install" and have it installed. It also creates the new partitions that he could not find with you.
I wish you success:fingers-crossed:
Click to expand...
Click to collapse
Don't think format data wipes the system partition does it?
Unless Xiaomi have really changed things, data should be completely separate. Format data should wipe the internal storage only which includes cache partition.
Twrp can wipe system, but shouldn't do unless specifically chosen to do so via several steps, not a single button press.
fards said:
Don't think format data wipes the system partition does it?
Unless Xiaomi have really changed things, data should be completely separate. Format data should wipe the internal storage only which includes cache partition.
Twrp can wipe system, but shouldn't do unless specifically chosen to do so via several steps, not a single button press.
Click to expand...
Click to collapse
no data format dont touch system
Yes, of course not the whole system partition, sorry.
From German into English is sometimes not that easy.?
In this case, TWRP will of course only delete the data as it stands there.
Otherwise everyone will find a step by step guide for almost every device a thousand times, thanks to you. So it should be also possible for everyone here.
Best regards and thank you two.:highfive:
rashmi0733 said:
Unlock Bootloader
flash TWRP
boot Twrp
format Data
copy rom on phone
install rom
reboot and enjoy new rom
Click to expand...
Click to collapse
Thanks for ur reply .. now i am able to successfully install the .eu ROM on my Indian Mi10
rashmi0733 said:
Thank For all suggestion i found one way to back stock Miui 11 without twrp
its working now i installed miui 11 and lock bootloader again.
Click to expand...
Click to collapse
Hello rashmi0733 I am also stuck in the same situation can you help me how u rolled back the beta update. Please help
Arif shaikh said:
Hello rashmi0733 I am also stuck in the same situation can you help me how u rolled back the beta update. Please help
Click to expand...
Click to collapse
I also want to go back to stable ROM
Its very simple to bypass the Anti rollback on miflash, just download the fastboot version of the ROM you want to install, unzip it and you'll have to edit this file (flash_all.bat), with for instance note++. And you remove 5 or 6 lines that does not begin by FASTBOOT. You can't miss it.
You can close and save.
Afterwards, just flash that same file that you just edited, and no more anti rollback error!
A second tip that I have when you just can't install custom firmwares on the mi 10, just flash stock firmware with miflash, reboot and flash TWRP. Transfer your custom firmware to your phone, flash it and ONLY format data afterwards! It was the only way to get a custom firmware on my mi10. It's my 5th xiaomi device and never experienced something like this...tried all TWRP available for the mi 10, but only by doing this way, I was able to succesfully install xiaomi.eu.
Good luck!
Custom ROMs are one of the best things about Android. One of the best things about the openness of the Android platform is that if you're unhappy with the stock OS, you can install one of many modified versions of Android (called ROMs) on your device. A new ROM can bring you the latest version of Android before your manufacturer does, or it can replace your manufacturer-modded version of Android with a clean, stock version. But with the introduction of the dynamic partition flashing Custom ROMs are a bit tricky. In this post, I will run you through the steps of flashing Custom ROMs on your Poco X3.
Pre-requisites:
Unlocked Bootloader
Custom Recovery
Note:- Always create a backup of your important files before flashing.
Steps:-
From MIUI to Custom ROM
Encrypted
Copy the Custom ROMs zip to your sdcard or your OTG flash drive.
Boot to the recovery.
Flash the required firmware mentioned for the ROM.
Reboot your recovery.
Flash the Custom ROM.
And then format data [**This will wipe your internal storage**]
Reboot (Flash magisk if you want root after the first boot)
Decrypted
Flash this decrypted vendor
Flash the custom rom
Format data and reboot
From Custom ROMs to Another Custom ROM
Encrypted
**Backup your internal storage, incase something gets wrong**
Remove your lockscreen password
Boot to the recovery
Wipe Data, Cache and Dalvik Cache
Flash Custom ROM
Reboot
** If the device bootloops Format Data **
Decrypted
*If your device is encrypted*
Flash the decrypted vendor
Flash the custom rom
Format data and reboot
*If your device is already decrypted*
Wipe data and cache
Flash rom
Reboot
Notes:-
For encrypted people
Always create a backup of your internal storage.
Format data while upgrading from one android version to another.
Downgrading firmware may also require data format
Moving from Gapps build to non-gapps build or vice versa also requires fata format
For decrypted people
You don't need to flash the decrypted vendor everytime unless you come from miui
The vendor will not work on miui
All credits to POCO X3 Developers & Custom ROM Community.
Regards,
Polvolt
You saved me. I had properly unlocked bootloader, flashed OrangeFox but then I did the wipes and also mistakely formated data, so I couldn't send files from PC to phone to flash the custom rom.
Guess I could've just used the usb otg at this point, but I reflashed MIUI with a script, and reflashed OrangeFox and now I'm good to go.
I thought current custom recoveries don't check for rollback protection (yet)?
It's probably safe to be flashing stock firmwares via custom recovery if you are sure you know what you're doing. But this guide seem to appeal to new comers. Should we suggest they stick to using Mi Flash tool for flashing stock firmwares as it has rollback protection checks?
Or am I just out of the loop and this is no longer the case with custom recoveries for surya/karna?
Thanks for the guide btw. Greatly appreciated.
I miss manually flashing each partition files via fastboot like when I was on my Nexus devices and my Essential PH-1. I have not seen a guide that recommends or even teaches us to flash partitions manually.
payas0 said:
I thought current custom recoveries don't check for rollback protection (yet)?
It's probably safe to be flashing stock firmwares via custom recovery if you are sure you know what you're doing. But this guide seem to appeal to new comers. Should we suggest they stick to using Mi Flash tool for flashing stock firmwares as it has rollback protection checks?
Or am I just out of the loop and this is no longer the case with custom recoveries for surya/karna?
Thanks for the guide btw. Greatly appreciated.
I miss manually flashing each partition files via fastboot like when I was on my Nexus devices and my Essential PH-1. I have not seen a guide that recommends or even teaches us to flash partitions manually.
Click to expand...
Click to collapse
Yes it is safe to flash stock fw via custom recovery. ARB hasn't been implemented on surya yet.
Well manual flashing each partition using fastboot on surya is much more complicated. Dynamic partition work differently. In short one have to boot to fastboot than boot to fastbootd than you can flash rom
Are you sure it's not enabled? After running fastboot getvar anti, I get anti: 2 and I just bought the phone without doing any upgrades. Unless this alone doesn't mean that ARB is enabled?
Mckol said:
Are you sure it's not enabled? After running fastboot getvar anti, I get anti: 2 and I just bought the phone without doing any upgrades. Unless this alone doesn't mean that ARB is enabled?
Click to expand...
Click to collapse
No only if you get "anti:4" itmeans ARB is enabled, otherwise feel free to downgrade via fastboot.
Kineceleran said:
No only if you get "anti:4" itmeans ARB is enabled, otherwise feel free to downgrade via fastboot.
Click to expand...
Click to collapse
Seems you're wrong. This XDA article states other way:
"
How to find current rollback index
Reboot to fastboot mode
Enter the following command: fastboot getvar anti
If the output is blank, then anti-rollback has not yet been enabled. If you get a number in the output, then that’s your current rollback index."
Xiaomi's Anti-Rollback Protection Explained: How to avoid bricking your phone
All Xiaomi smartphones and tablets will have anti-rollback protection enabled. What is it and how do you avoid bricking your device because of it?
www.xda-developers.com
How about from MIUI Global to MIUI EU ? I've found a 12.0.7.0, not sure but it seems to be EU rom, right?
Hello
I'm new to Xiaomi phones! For the love of God someone tell me how do I flash roms on my poco x3 nfc Note ( I've been flashing roms for years but not Xiaomi phones ). What ever I flash it works but after I attempt to flash another rom files in sd card get corrupt and I format data that doesn't gonna do anything! So please someone tell me how do I flash roms on this phone. My phone is encrypted I was on MIUI global
ayad.phonex said:
Hello
I'm new to Xiaomi phones! For the love of God someone tell me how do I flash roms on my poco x3 nfc Note ( I've been flashing roms for years but not Xiaomi phones ). What ever I flash it works but after I attempt to flash another rom files in sd card get corrupt and I format data that doesn't gonna do anything! So please someone tell me how do I flash roms on this phone. My phone is encrypted I was on MIUI global
Click to expand...
Click to collapse
I suppose you do have already unlocked bootloader and installed recovery? if no, please do, if yes try this guide or read this post
I'm having trouble because I flashed the vendor and it does not work in my version (QJGMIXM) and 4g internet does not work. I need help to fix because I can't find original vendor file or return to MIUI. HELP!!!!!
biliterror said:
I'm having trouble because I flashed the vendor and it does not work in my version (QJGMIXM) and 4g internet does not work. I need help to fix because I can't find original vendor file or return to MIUI. HELP!!!!!
Click to expand...
Click to collapse
Use any fastboot stock ROM and MiFlash tool to restore your phone...or flash any custom recovery and use it to flash any recovery stock ROM to restore your phone.
I have 6 days to wait for unlocking the device. I can't wait to get rid of the Mi UI mess and bloat. I haven't had to do a complicated (for me) phone flash process like this since a Motorola phone in 2014. I have a a few questions:
1- Do I need to add/install adb drivers to my WIN10 PC? I came across win adb drivers for the POCO in my search for Windows PC drivers. Which version of adb is needed for Win10? I currently have abd my laptop, but I can't determine the version.
2- Installing the recovery - I see the steps some have posted with TWRP versions, but I'm not really clear on this. Do I go to the folder with TWRP in it and then use a command prompt from there? TWRP or Orange Fox and what version? The posts are confusing.
3- I'd like to have the easiest rom flash for my first go at this phone. I would appreciate a recommendation for which rom might be the best one to start with. I will be want gapps as part of the process, but could flash afterwards if its better that way. Is Arrow OS or Havoc a good choice?
Sorry for all the questions.
Thanks
If i flash a newer Firmware (.7) over the decrypted vendor (.5), is my phone encrypted again?
Grusel said:
If i flash a newer Firmware (.7) over the decrypted vendor (.5), is my phone encrypted again?
Click to expand...
Click to collapse
if you'll flash 12.0.7 vendor from this thread, then no
Is this the right way?
Flash the CustomRom and after flash format Data?
Not first format Data and than flash Customrom?
My plan after bootloader Wait time is flash the Miui Eu Rom.
What ist the right way?
trutta said:
Is this the right way?
Flash the CustomRom and after flash format Data?
Not first format Data and than flash Customrom?
My plan after bootloader Wait time is flash the Miui Eu Rom.
What ist the right way?
Click to expand...
Click to collapse
Flashing ROM and Format data is the usual way....
I now. But the chronologie was another. First Format data, then flash Rom.
Usually in all my old device while flashing roms I have to wipe system data cache then I just flashed the rom, it's my first Xiaomi device I am confused as hell , should i never have to wipe system partition ? , Is flashing firmware necessary everytime ? Are there any risks associated with decrypted vendor ?please guide me I am not noob but these things are completely new to me
Device storage partition schemes have changed and are now dynamic, so previous procedures don't apply anymore. Closely follow your ROM developer instructions in order to avoid bricking your device.
Dynamic Partitions | Android Open Source Project
source.android.com
Brother, i have Karna (Indian) one with me. I got update to latest MIUI 12.0.8, after updating i unlocked the bootloader and flashed twrp, but it dint wrok, then had to flash OFox. RN i am on latest lineageOS 17.1. I am having network issues. Someone at the telegram group told me to flash the firmware along with the vendor of 12.0.5 MiUi as he also suffered the same kind of network issue i am having.
but the problem is i am unable to find the Vendor n firmware of 12.0.5. Can you please help me ?