I am completely new to the xiaomi ecosystem. I used the Lenovo ZUK Z2 before I switched to the Poco F1. I have an issue. For starters, whenever I flash the MIUI stable/developer via TWRP, it automatically reverts to the stock recovery, and I have to keep flashing TWRP via adb. Secondly, whenever I flash a new zip, the sdcard folder contents are gone all the time and I have to manually copy all of them back again. Is this an issue with TWRP or is it a Xiaomi specific thing? I've never encountered this with the Z2 plus, and I know that the TWRP that we currently have is unofficial and doesn't have the full capability as a stable release. But could someone clarify my doubt?
You haven't flashed decryption disable zip which means you haven't read guide saying that you have to do that bcoz twrp is bugged and cannot decrypt data without it
Wysłane z mojego POCOPHONE F1 przy użyciu Tapatalka
uremytoy said:
You haven't flashed decryption disable zip which means you haven't read guide saying that you have to do that bcoz twrp is bugged and cannot decrypt data without it
Wysłane z mojego POCOPHONE F1 przy użyciu Tapatalka
Click to expand...
Click to collapse
There was this zip file that flashes both encryption disabler and magisk 17.2. Is there some other zip file I need to flash? Also, is it a one time thing only? Or do I have to flash it every time I flash a ROM or some mod?
For now you have to flash it every time you flash stock miui ROM, don't know others
Wysłane z mojego POCOPHONE F1 przy użyciu Tapatalka
I have another issue. Why does my internal storage partition get wiped too? That never happens. Is it again because of stock ROM?
That's because twrp can't decrypt data, so you have to format them and then flash decryption disable zip after that everything is ok. So kinda yes it's stock miui fault as it's encrypt data if you don't flash this zip
Wysłane z mojego POCOPHONE F1 przy użyciu Tapatalka
Related
How i can reboot my phone via terminal/adb to cwm and flash zip or run some script? Are there any parameters to flash zip automatically after booting to cwm?
Wysłane z mojego LG-P990 przy użyciu Tapatalk 4
bartekDPL said:
How i can reboot my phone via terminal/adb to cwm and flash zip or run some script? Are there any parameters to flash zip automatically after booting to cwm?
Wysłane z mojego LG-P990 przy użyciu Tapatalk 4
Click to expand...
Click to collapse
you must need to connect it computer and install cwm .. there is not any auto cwm recovery as apk format ...
Yes, but i want any script or something which rebooting phone into cwm recovery and automatically starts flashing a update.zip or something else (for e.g. wipe data etc)
Wysłane z mojego LG-P990 przy użyciu Tapatalk 4
Try finding a kernel that has CWM built like the CyanogenMod's default kernel. There is an option in the reboot menu (of CyanogenMod) to go to recovery/download.
Sent from my GT-I9100
I was rooting the S3 until the app(one click root) didn't work for , it changed the kernel with a one with root access, though it i dont have root :/
So it basically F*D the phone firmware tho it works fine.
So to root it again, should i flash stock S3 rom via Odin or CF Auto Root with the wrong kernels currently applied?
Eliminate007 said:
I was rooting the S3 until the app(one click root) didn't work for , it changed the kernel with a one with root access, though it i dont have root :/
So it basically F*D the phone firmware tho it works fine.
So to root it again, should i flash stock S3 rom via Odin or CF Auto Root with the wrong kernels currently applied?
Click to expand...
Click to collapse
Try using odin, with the correct files.
Enviado de meu Nexus 5 usando Tapatalk
I think the best way to root is to flash custom recovery via Odin and then SuperSU package. If you want to keep stock recovery (don't know why) then you need to flash newest stock firmware with corresponding CF Auto.
Wysłane z mojego GT-I9300 przy użyciu Tapatalka
SirKunon said:
I think the best way to root is to flash custom recovery via Odin and then SuperSU package. If you want to keep stock recovery (don't know why) then you need to flash newest stock firmware with corresponding CF Auto.
Wysłane z mojego GT-I9300 przy użyciu Tapatalka
Click to expand...
Click to collapse
But wont i need root for the Custom Recovery?
Root means super user rights in currently used system. Recovery mode is system independent (not quite but you should think about it as some kind of presystem toolkit.) S3 has different partition for kernel and another for recovery. That's why you can and you should flash custom recovery to be able to backup your efs, system, data etc. and flash whatever you like: roms, kernels, su binaries...
Of course flashing unsigned by Samsung data will trigger flash counter, but this can be fixed by Triangle Away. In my opinion custom recovery is even more important than root itself because if you've got it you can forget about any PC operations. You don't need Odin, drivers, Kies and another tools.
TWRP, SuperSU, Mobile Odin, Titanium Backup - it is all you need. Until custom recovery works you can do almost everything.
But I'm not sure what do you want. Stock firmware with root only? CF Auto Root inject su binaries and shouldn't change stock kernel. That's why it should be enough if you have any arguments to use outdated stock firmware.
Wysłane z mojego GT-I9300 przy użyciu Tapatalka
SirKunon said:
I think the best way to root is to flash custom recovery via Odin and then SuperSU package. If you want to keep stock recovery (don't know why) then you need to flash newest stock firmware with corresponding CF Auto.
Wysłane z mojego GT-I9300 przy użyciu Tapatalka
Click to expand...
Click to collapse
SirKunon said:
Root means super user rights in currently used system. Recovery mode is system independent (not quite but you should think about it as some kind of presystem toolkit.) S3 has different partition for kernel and another for recovery. That's why you can and you should flash custom recovery to be able to backup your efs, system, data etc. and flash whatever you like: roms, kernels, su binaries...
Of course flashing unsigned by Samsung data will trigger flash counter, but this can be fixed by Triangle Away. In my opinion custom recovery is even more important than root itself because if you've got it you can forget about any PC operations. You don't need Odin, drivers, Kies and another tools.
TWRP, SuperSU, Mobile Odin, Titanium Backup - it is all you need. Until custom recovery works you can do almost everything.
But I'm not sure what do you want. Stock firmware with root only? CF Auto Root inject su binaries and shouldn't change stock kernel. That's why it should be enough if you have any arguments to use outdated stock firmware.
Wysłane z mojego GT-I9300 przy użyciu Tapatalka
Click to expand...
Click to collapse
I just want to run Custom Rom and use apps that require root access.
Can i flash SuperSU to give me root access if i have custom recovery?
Sure, you can flash anything you like.
Wysłane z mojego GT-I9300 przy użyciu Tapatalka
SirKunon said:
Sure, you can flash anything you like.
Wysłane z mojego GT-I9300 przy użyciu Tapatalka
Click to expand...
Click to collapse
Wait so rooting is basically if i want to stick to Stock ROM, but if i have a custom recovery like TWRP, i can get the SuperSU zip and flash it? Will it work if i get it off Playstore?
Custom roms are usually prerooted. Root means you've got super user binaries installed on your system partition in scripts folder. SuperSU is only an application which grants access to super user 'account' rights for certain apps.
You can install SuperSU from PlayStore but without those binaries installed you will not have rooted phone.
Don't know how can I explain this simpler.
Wysłane z mojego GT-I9300 przy użyciu Tapatalka
SirKunon said:
Custom roms are usually prerooted. Root means you've got super user binaries installed on your system partition in scripts folder. SuperSU is only an application which grants access to super user 'account' rights for certain apps.
You can install SuperSU from PlayStore but without those binaries installed you will not have rooted phone.
Don't know how can I explain this simpler.
Wysłane z mojego GT-I9300 przy użyciu Tapatalka
Click to expand...
Click to collapse
So basically S3 AOSP roms have the su binaries and i only need to either flash SuperSU or download it off Playstore(On Custom Rom)?
No, you need do nothing on an AOSP rom as it already contains everything needed for granting root access.
Can you help with this? http://forum.xda-developers.com/galaxy-s3/help/wifi-flashing-rom-t3020438
Hi,
I have tried many TWRP versions (eg: Official, @TheStrix , ZCX, Alka,...) and all brings the same results - after flashing and booting directly to TWRP (which works) and then rebooting to system I got bootloop.
I have tried most clean way to try:
- flash via fastboot whole system - even with userdata
- turn on usb debugging
- reboot to fastboot
- flash twrp
- boot in to recovery (power+VolUp)
- cancel decription
- reboot to system
- boot loop
So do we have any working TWRP for latest developer global rom?
Btw, I have unlocked bootloader - official way. In the past TWRP was working for me with CM14.1. Now I want have it with official rom.
Try Alka twrp
Wysłane z mojego Elephone P8000 przy użyciu Tapatalka
mar.ur said:
Try Alka twrp
Click to expand...
Click to collapse
This also do not work for me - boot loop.
After this problems, I have to reflash whole system in order to have it bootable.
The latest ZCX-TWRP_REDMI_NOTE3-PRO_Kenzo_20161230.zip works for me. Thread can be closed.
When you start TWRP for the first time, you have to select "Keep Read Only"
Flash twrp without unlock bootloader ?
you need to format all data and reboot once to twrp recovery before flashing custom ROM
i'm on the latesr global rom and zcx works for me. maybe downgrade to an earlier version of global rom then flash zcx then upgrade to miui 8.
Hi,
I have a question about TWRP 3.1.1-0.
Whenever i try to recover a previously made backup it tells me that it's not succesful because the system partition is write protected.
Can someone help?
Problem solved. After installing TWRP 3.2.0 all went fine. No write protection anymore.
StefanV3
Gesendet von meinem XT1650-03 mit Tapatalk
Hi everyone,
My Mi 8 was on miui_MI8Global_V10.0.3.0.OEAMIFH,rooted with Magisk
version 17.3.
Received Ota notification from the builtin updater app,then itself updated
to miui_MI8Global_V10.1.1.0.PEAMIFI(with boot.img patched by Magisk).
After update,everything works fine,except root is lost,so I use Magisk(version
18.0) patch the boot.img again and rooted again,still everything works fine till now.
Anti rollback value = 1
This is my report.
Updated to miui_MI8Global_V10.1.2.0.PEAMIFI_e42df0352a_9.0,lost root again.
Follow steps mention above , Rooted again.
Anti rollback value , still = 1
sm1232 said:
Hi everyone,
My Mi 8 was on miui_MI8Global_V10.0.3.0.OEAMIFH,rooted with Magisk
version 17.3.
Received Ota notification from the builtin updater app,then itself updated
to miui_MI8Global_V10.1.1.0.PEAMIFI(with boot.img patched by Magisk).
After update,everything works fine,except root is lost,so I use Magisk(version
18.0) patch the boot.img again and rooted again,still everything works fine till now.
Anti rollback value = 1
This is my report.
Click to expand...
Click to collapse
I read somewhere we need arb=4 to downgrade to Oreo. Can any one can confirm this info
Wysłane z mojego MI 8 przy użyciu Tapatalka
sm1232 said:
Hi everyone,
My Mi 8 was on miui_MI8Global_V10.0.3.0.OEAMIFH,rooted with Magisk
version 17.3.
Received Ota notification from the builtin updater app,then itself updated
to miui_MI8Global_V10.1.1.0.PEAMIFI(with boot.img patched by Magisk).
After update,everything works fine,except root is lost,so I use Magisk(version
18.0) patch the boot.img again and rooted again,still everything works fine till now.
Anti rollback value = 1
This is my report.
Click to expand...
Click to collapse
How to root with patch the boot.img.
I try this but when i install patched_boot.img via fastboot. Device will bootloop to MI recovery.
MaxMedia said:
How to root with patch the boot.img.
I try this but when i install patched_boot.img via fastboot. Device will bootloop to MI recovery.
Click to expand...
Click to collapse
1.bootloader unlocked
2.use Magisk manager to patch the boot.img
3.in fastbootmode exercute this command in command prompt from Windows of your PC - fastboot flash boot patch_boot.img
patch_boot.img = your Magisk patched boot.img name
this is what I have done.
sm1232 said:
1.bootloader unlocked
2.use Magisk manager to patch the boot.img
3.in fastbootmode exercute this command in command prompt from Windows of your PC - fastboot flash boot patch_boot.img
patch_boot.img = your Magisk patched boot.img name
this is what I have done.
Click to expand...
Click to collapse
When patched the boot.img, are you tick in
Preserve AVB 2.0/dm-verity
Preserve force encryption
thanks!
MaxMedia said:
When patched the boot.img, are you tick in
Preserve AVB 2.0/dm-verity
Preserve force encryption
thanks!
Click to expand...
Click to collapse
only tick in Preserve force encryption
sm1232 said:
Hi everyone,
My Mi 8 was on miui_MI8Global_V10.0.3.0.OEAMIFH,rooted with Magisk
version 17.3.
Received Ota notification from the builtin updater app,then itself updated
to miui_MI8Global_V10.1.1.0.PEAMIFI(with boot.img patched by Magisk).
After update,everything works fine,except root is lost,so I use Magisk(version
18.0) patch the boot.img again and rooted again,still everything works fine till now.
Anti rollback value = 1
This is my report.
Click to expand...
Click to collapse
Thanks for your report mate. Have you done the update to the latest 10.1.2?
My phone updated itself even I had not to do so and now I am on pie with lost root.
I have the latest update over the air and wondering how to update and get root again.
I have unlocked bootloader
Twrp
And unfortunately android pie 10.1.1 with ARB. :/
Successfully updated to 10.1.2 with stock updater. /it rebooted to twrp and istalled the update/
I had bootloop into twrp
I flashed magisk 17.1 and Disable_Dm-Verity_FEC_v1.1.zip with wipe dalvic and cach. Booted into system and in magiks manager updated to the latest v. 18.
Got the system booted and works. Annoyingly auto brightness ? jumping all the time. Battery life is a joke. Notch CANNOTBE HIDDEN!!!
chudy_85 said:
I read somewhere we need arb=4 to downgrade to Oreo. Can any one can confirm this info
Wysłane z mojego MI 8 przy użyciu Tapatalka
Click to expand...
Click to collapse
ARB 4 is anti rollback enabled.
Check here
sisqoboy said:
Successfully updated to 10.1.2 with stock updater. /it rebooted to twrp and istalled the update/
I had bootloop into twrp
I flashed magisk 17.1 and Disable_Dm-Verity_FEC_v1.1.zip with wipe dalvic and cach. Booted into system and in magiks manager updated to the latest v. 18.
Click to expand...
Click to collapse
today updated to 10.1.2.0 ,used methode I mention ,rooted again.
I do not use twrp recovery ,so after update everything works fine, no bootloop.
sm1232 said:
......I do not use twrp recovery ,so after update everything works fine, ..........
Click to expand...
Click to collapse
Does Region retain your locality or does it revert to China after every reBoot ?
Chi Am said:
Does Region retain your locality or does it revert to China after every reBoot ?
Click to expand...
Click to collapse
I have a Global version of Mi 8 , region remain the same after every reboot.
sm1232 said:
I have a Global version of Mi 8 , region remain the same after every reboot.
Click to expand...
Click to collapse
Thank you.
Now I can discount unmodified Global ROM to be the cause of the Region issue.