as far as I know, the coffec twrp is based on 3.0.0. which is an old twrp. I want to know, is there a twrp with auto miui image patching and all partition backup capability alongside f2fs support based on latest twrp 3.0.2-2??? if so, please provide a link. sorry for mh bad English
Only way is to use the Alka TWRP first, backup all partitions. Then flash F2FS TWRP for converting into F2FS filesystem.
Then return to Alka TWRP to restore your backup of all partitions.
You must have a PC(with all drivers installed) which is available to you whenever needed to flash the recoveries using fastboot command.
superboy123 said:
Only way is to use the Alka TWRP first, backup all partitions. Then flash F2FS TWRP for converting into F2FS filesystem.
Then return to Alka TWRP to restore your backup of all partitions.
You must have a PC(with all drivers installed) which is available to you whenever needed to flash the recoveries using fastboot command.
Click to expand...
Click to collapse
Read it here on XDA that Alka TWRP has some bug.. like errors in restoring firmware. true?
candiesdoodle said:
Read it here on XDA that Alka TWRP has some bug.. like errors in restoring firmware. true?
Click to expand...
Click to collapse
Yes, it gives some sort tarfork error in firmware partition as the firmware partition is read only.
You should uncheck the firmware partition while restoring.
Example: Assume that you have taken a backup of MIUI 8 Global stable (yes, all partition backup). After backup, you went to CM13 or any custom ROM and assume that you flashed the CM 13 radios/firmware zip. Now you want to go back to MIUI and you restored it. Now you will face issues in MIUI like no sound in calls where neither you nor the person on the other side will be able to hear any sound.
The above issues are caused due to firmware. MIUI's firmware and CM's firmware are not the same.
If you want to revert from CM or any custom ROM to MIUI, you must use MiFlash (EDL).
superboy123 said:
Yes, it gives some sort tarfork error in firmware partition as the firmware partition is read only.
You should uncheck the firmware partition while restoring.
Example: Assume that you have taken a backup of MIUI 8 Global stable (yes, all partition backup). After backup, you went to CM13 or any custom ROM and assume that you flashed the CM 13 radios/firmware zip. Now you want to go back to MIUI and you restored it. Now you will face issues in MIUI like no sound in calls where neither you nor the person on the other side will be able to hear any sound.
The above issues are caused due to firmware. MIUI's firmware and CM's firmware are not the same.
If you want to revert from CM or any custom ROM to MIUI, you must use MiFlash (EDL).
Click to expand...
Click to collapse
Thanks!! So a safe way to revert from CM to MIUI would be to:
- restore partitions, and assuming firmware gives error
- flash via EDL over this
Maybe i could directly flash through EDL..will that work? will the radios/modem get overwritten by the MIUI radios/modem?
candiesdoodle said:
Thanks!! So a safe way to revert from CM to MIUI would be to:
- restore partitions, and assuming firmware gives error
- flash via EDL over this
Maybe i could directly flash through EDL..will that work? will the radios/modem get overwritten by the MIUI radios/modem?
Click to expand...
Click to collapse
Yes, the radios/modem will get over-written.
No need to restore partitions. All the partitions will get flashed by the MiFlash.
I almost backup only the Boot, Data, Cache and System partitions leaving others.
If you want your Internal SD card, select Flash all except data and storage option at the bottom.
Enjoy with your device!:good::good:
I am using MIUI 8.0.1.0 and maybe someday I will try CM13/14. About twrp, what is the recommended twrp for our phone ?
Read this http://forum.xda-developers.com/redmi-note-3/how-to/zcx-twrp-install-twrp-flash-supersu-t3462448
---------- Post added at 12:57 PM ---------- Previous post was at 12:57 PM ----------
Sohan_Saymum said:
as far as I know, the coffec twrp is based on 3.0.0. which is an old twrp. I want to know, is there a twrp with auto miui image patching and all partition backup capability alongside f2fs support based on latest twrp 3.0.2-2??? if so, please provide a link. sorry for mh bad English
Click to expand...
Click to collapse
http://forum.xda-developers.com/redmi-note-3/how-to/zcx-twrp-install-twrp-flash-supersu-t3462448
Related
So i am on the new miui using the oficial flash thing (unlocked bootloader oficialy).
The thing is i always wanted to get root and use a kernel on xda here that gives more available memory and solves some of the heating problems when charging (but i know need TWRP ofc) .
So i went to here and checked a few guides however there are many twrp's versions some of them i can't flash miui oficial roms, some of them i need installl boot.img every single time or when i want to restore backup is not just select the backup and done, i need to do something else (is a bit confusing)... so instead i decided to ask you guys directly
The question is:
- If i wanted to use oficial miui but have root and install a kernel and in future just flash the new miui rom again without any stress (just twrp -> flash-> select rom and gapps and done), no boot.img bull****, no flash another twrp etc is it possible??
(before this phone i had moto g(1st gen) and was easy as to put ONE twrp and then would be always flash rom + gapps every single time, no boot.img no firmware, worked for CM12, 12.1 and 13)
Install Alka recovery and back up all the partitions before doing anything.
tigax said:
- If i wanted to use oficial miui but have root and install a kernel and in future just flash the new miui rom again without any stress (just twrp -> flash-> select rom and gapps and done), no boot.img bull****, no flash another twrp etc is it possible??
Click to expand...
Click to collapse
Although I haven't tried it personally, the TWRP explanation guide here says the Cofface TWRP (linked on that page) automatically patches the boot.img when you flash a new ROM, which I believe solves your problem.
harishmenace said:
Install Alka recovery and back up all the partitions before doing anything.
Click to expand...
Click to collapse
so this one allows me to flash new roms from Miui? without any boot.img and stuff?
tigax said:
so this one allows me to flash new roms from Miui? without any boot.img and stuff?
Click to expand...
Click to collapse
Yes, I was doing it all the time.
Sent from my Redmi Note 3 using Tapatalk
timberwolf60 said:
Yes, I was doing it all the time.
Click to expand...
Click to collapse
Thank you will use then
Hi,
I can finally unlock the bootloader - which AFAIK wipes user data. Now, since I've used the phone heavily over the waiting period, there's a lot to backup and reintegrate later on.
What's the quickest way to do so?
MTP-copy all of Internal Storage to PC -> unlock -> copy back?
(I am experienced with unlocking, rooting, flashing Roms and recoveries, but haven't had a non-rooted phone for about 8 years, so I am a bit out of the loop on non-root backup procedures)
TIA!
Using adb pull, you could probably get your internal storage.
Iirc the canonical dirs are:
/storage/emulated/0
/storage/emulated/legacyHelium should be sufficient for apps.
For me unlocking didn't wipe data.
Only wipe was when I installed developer rom to be able to unlock.
So the process should be unlock, flash twrp and then flash magisk to maintain twrp and avoid the bootloop. Then you can backup with root and clean flash if you want.
Twrp can't decrypt data but it's not needed to flash magisk. Anyway you can flash orangefox (latest version, beta 6) from twrp and it can decrypt data to access it from recovery.
omnomnomkimiiee said:
Using adb pull, you could probably get your internal storage.
Iirc the canonical dirs are:
/storage/emulated/0
/storage/emulated/legacyHelium should be sufficient for apps.
Click to expand...
Click to collapse
Thanks.
Any advantage of using adb vs. just mounting the device via mtp? Last I've used adb for file transfer it was slower than even mtp...
jes0411 said:
For me unlocking didn't wipe data.
Only wipe was when I installed developer rom to be able to unlock.
Click to expand...
Click to collapse
do you mean "to be able to root"? because otherwise I don't follow...
So the process should be unlock, flash twrp and then flash magisk to maintain twrp and avoid the bootloop. Then you can backup with root and clean flash if you want.
Twrp can't decrypt data but it's not needed to flash magisk. Anyway you can flash orangefox (latest version, beta 6) from twrp and it can decrypt data to access it from recovery.
Click to expand...
Click to collapse
Thanks. This is gonna sound very noob, but since I'm new to MIUI - is data already encrypted in stock MIUI? Otherwise I'll need orangefox only for switching between future custom ROMs, right?
santoo said:
do you mean "to be able to root"? because otherwise I don't follow...
Thanks. This is gonna sound very noob, but since I'm new to MIUI - is data already encrypted in stock MIUI? Otherwise I'll need orangefox only for switching between future custom ROMs, right?
Click to expand...
Click to collapse
I mean to unlock because I can't bind my mi account in stable and had to install developer rom to bind account.
Yes data is already encrypted on stock rom. If you need to access data partition in recovery you need orangefox. But it's not needed to flash magisk.
To use custom roms you don't need orangefox because you can format data from twrp and then flash the rom. I started using orangefox since I tried miui 10 oreo beta because I was unable to avoid encryption on that rom.
jes0411 said:
I mean to unlock because I can't bind my mi account in stable and had to install developer rom to bind account.
Yes data is already encrypted on stock rom. If you need to access data partition in recovery you need orangefox. But it's not needed to flash magisk.
To use custom roms you don't need orangefox because you can format data from twrp and then flash the rom. I started using orangefox since I tried miui 10 oreo beta because I was unable to avoid encryption on that rom.
Click to expand...
Click to collapse
Thanks for the explanations!
I plan on just unlocking bootloader, enabling cam2 and installing a current gcam today - I'll wait with flashing until miui10 stable is released in the next week or so, so I can do a "fair" comparison between Lineage and Miui (and possibly some others)
jes0411 said:
For me unlocking didn't wipe data.
Click to expand...
Click to collapse
A quick heads-up, just in case anyone stumbles upon this thread:
As of MIUI 9.5.17 global stable, using official MIUI unlock 3.3.525.23, unlocking the bootloader DOES WIPE user data & factory-resets the phone (to be more precise - it wipes the complete internal storage).
SD is, as expected, left alone.
santoo said:
A quick heads-up, just in case anyone stumbles upon this thread:
As of MIUI 9.5.17 global stable, using official MIUI unlock 3.3.525.23, unlocking the bootloader DOES WIPE user data & factory-resets the phone (to be more precise - it wipes the complete internal storage).
SD is, as expected, left alone.
Click to expand...
Click to collapse
I only shared my experience.
My data was wiped when I installed developer rom to bind account but when I unlocked bootloader after 360h data remained intact. When I flashed twrp phone didn't boot but I solved it flashing magisk.
jes0411 said:
I only shared my experience.
Click to expand...
Click to collapse
Yes, and I thank you for it.
I was not accusing you of anything - things may well have changed with different versions of MIUI or different versions of the unlock tool, or between chinese/global versions. Just a warning for others that, at least with the versions I posted, having a backup is reaaaaally nice :good:
I'm on MIUI10 8.9.13 Global beta, and i wish to flash EU ROM..
can someone verify if these are the correct steps in order?
Boot to recovery,wipe cache,dalvik,system,data then flash the eu rom,
Followed by force encryption disabler,magisk
Then reboot system.
And later,
Do i have to dirty flash manually via twrp for every update, or can i do it via miui updater app?
And
Will i face any problem if i restore the missing apps+system data in the eu rom via titanium backup (the backups were made when rom was global beta) or should i restore only missing apps.
Answers are very well appreciated
jaspad1710 said:
I'm on MIUI10 8.9.13 Global beta, and i wish to flash EU ROM..
can someone verify if these are the correct steps in order?
Boot to recovery,wipe cache,dalvik,system,data then flash the eu rom,
Followed by force encryption disabler,magisk
Then reboot system.
And later,
Do i have to dirty flash manually via twrp for every update, or can i do it via miui updater app?
And
Will i face any problem if i restore the missing apps+system data in the eu rom via titanium backup (the backups were made when rom was global beta) or should i restore only missing apps.
Answers are very well appreciated
Click to expand...
Click to collapse
1. Correct steps. You don't need Magisk as that zip provided by unofficial twrp thread includes it. Use that.
2. Yes, you can update (dirty flash) via twrp with full rom zips.
3. I always restore backup from Titanium backup even when I change roms (Miui/stock/EU roms) and never faced any issue.
Hi i have a problem with my poco f1
Status : UBL , NO OS , Orangefox recovery
Tried : flashing many roms and changed from twrp to orangefox but the problem persists. While trying to install the roms i wiped everything before.
Problem : Whenever i try installing a custom rom i get an error 7 message that says : xiaomi.verify_vendor() failed to read current vendor UTC build date: -2
I am not able to flash any custom rom and when i try i get this error.
The problem occurred when i tried to boot on my installed rom from multirom recovery. I had backed up everything but when i restore the backup (except the multiRom recovery) the phone is stuck on the pocophone logo.
If you need any more info i can provide please ask for it.
try clean flashing global stable fastboot rom using mi flash tool then flash twrp and flash any rom you want
https://mirror.akhilnarang.me/MIUI/beryllium/
take the latest vendor image 9.3.28 (dated 29-03-2019 17:11)
flash this via twrp and then flash rom
it should work
YasuHamed said:
https://mirror.akhilnarang.me/MIUI/beryllium/
take the latest vendor image 9.3.28 (dated 29-03-2019 17:11)
flash this via twrp and then flash rom
it should work
Click to expand...
Click to collapse
I will try this method first due to the smaller download size. I hope it works so i do not have to flash the stock rom again and go though the whole process.
It worked. I am now flashing a custom rom. My question is why did this happen ?
jackaros said:
It worked. I am now flashing a custom rom. My question is why did this happen ?
Click to expand...
Click to collapse
BRO WHENEVER you are trying to flash new rom be on latest vendor , firmware and vendor can be found on leanage os xda page 1 , updated rom requires latest vendor
jackaros said:
It worked. I am now flashing a custom rom. My question is why did this happen ?
Click to expand...
Click to collapse
I think you came from MIUI10.2.x
since, miui10 on android9, Xiaomi has started using MODIFIED version of VENDOR image*
so when you flash custom rom which works on standard vendor image, it gives your either error7 or hangs on splash screen
*android has following partitions /boot /recovery /system, /data, /internalstorage /persist /OEM
oem or VENDOR partition translates android
using modified oem (vendor) image in android 9, its xiaomi's attempt for speedy android updates (CGI) (treble)
YasuHamed said:
I think you came from MIUI10.2.x
since, miui10 on android9, Xiaomi has started using MODIFIED version of VENDOR image*
so when you flash custom rom which works on standard vendor image, it gives your either error7 or hangs on splash screen
*android has following partitions /boot /recovery /system, /data, /internalstorage /persist /OEM
oem or VENDOR partition translates android
using modified oem (vendor) image in android 9, its xiaomi's attempt for speedy android updates (CGI) (treble)
Click to expand...
Click to collapse
Just a follow up question..
So what will happen to my phone.. if its on miui 10.2.3.0 then i flashed the latest vendor img?? Will it cause bootloop?? Will it have a better performance?? Will it make games much smoother???
santiagoruel13 said:
Just a follow up question..
So what will happen to my phone.. if its on miui 10.2.3.0 then i flashed the latest vendor img?? Will it cause bootloop?? Will it have a better performance?? Will it make games much smoother???
Click to expand...
Click to collapse
miui10.2.x has its own modified vendor image,
to comeback on standard image, you must flash the image (which you did)
Hello
I am using MIUI global 11.0.8 stock rom. Recently just unlocked the bootloader and trying to figure out how to flash LineageOS in it.
Tried to followed this guide https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-unlock-bootloader-custom-t3839405
But it seems like it is pretty old and not updated. Should i follow this thread or there is something updated? Also feels like i'm missing various things like disabling encryption(!), needs to be on old stock rom for proper installation, customized TWRP recovery and specific Xiaomi programs to do it properly. Could someone identify the missing info/issues i'm having trouble with? TIA.
61zone said:
Hello
I am using MIUI global 11.0.8 stock rom. Recently just unlocked the bootloader and trying to figure out how to flash LineageOS in it.
Tried to followed this guide https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-unlock-bootloader-custom-t3839405
But it seems like it is pretty old and not updated. Should i follow this thread or there is something updated? Also feels like i'm missing various things like disabling encryption(!), needs to be on old stock rom for proper installation, customized TWRP recovery and specific Xiaomi programs to do it properly. Could someone identify the missing info/issues i'm having trouble with? TIA.
Click to expand...
Click to collapse
FIRST OF ALL BACKUP YOUR DATA. Go to fastboot mode and flash latest twrp recovery. Boot to recovery and wipe cache, system and data. Since this is the first time you are installing a custom rom you should format data in twrp. After formatting data reboot to twrp then transfer latest Lineage OS flashable zip in you phone's storage and flash it. Then flash gapps if you want. Then magisk if you want root and DFE if you don't want encryption. That's it. Now reboot to system.
And remember google is your friend.
callmebutcher101 said:
FIRST OF ALL BACKUP YOUR DATA. Go to fastboot mode and flash latest twrp recovery. Boot to recovery and wipe cache, system and data. Since this is the first time you are installing a custom rom you should format data in twrp. After formatting data reboot to twrp then transfer latest Lineage OS flashable zip in you phone's storage and flash it. Then flash gapps if you want. Then magisk if you want root and DFE if you don't want encryption. That's it. Now reboot to system.
And remember google is your friend.
Click to expand...
Click to collapse
Actually there is too much information to handle at once that's why i got confused lol. Thanks for the infos :good:
I'll try to do according to your info.