Hi, Few questions here.. Havent flashed in a long time..
I want to enable Cam2api in stock rom.. Without losing OTA..
What is the way to go about it ??
The usual method as i understood after going through the forums is to
1) Unlock bootloader
2) Flash twrp
3) Enable cam2 api through adb(if u dont need root)
Questions as follows..
1) After flashing twrp is it necessary to flash lazy patcher or lazy patcher needed only if its rooted ??
2) Can i flash the subsequent ota update zip from mi websites through twrp ??
3) If cam2 api is enabled will the stock miui camera stop working ??
4) My previous phone Mi A1 had a method where we could enable camera2 api without losing ota updates.. Is there any such method for N5Pro ??
1. You will need lazy flasher for keeping twrp as recovery, even after booting, as miui removes twrp after booting. But there's a much simpler option, boot into twrp as normal via ADB, root, boot into system, install official twrp app from play store, install twrp from there, it'll keep twrp intact.
2. Yes, for beta, though it'll remove twrp again, bootloader will remain unlocked. For stable, I've not tried.
3. With camera2 API enabled, camcorder will be fixed focus. Probably the only bug.
4. Add camera2 with magisk modules, you'll still get OTAs
I have camera2api enabled and have no problem with automatic autofokus in camcorder (stock camera app). MIUI 9.5.19.0 rooted.
Ok.. So if i just boot into twrp without actually flashing it, enable cam2api & then boot the device.. There will be no issues with both the miui cam & ota updates, right ??
One more doubt will i have to do this step after every ota update or once i have enabled the cam2api, will it persist after each update ??
Bump
if enable camera2api, i will have bugs in miui camera?
affects the miui camera? thanks
Ota update failed after cam2api enabled any solution
Related
hello
i am new to this forums and my phone
is unlocking bootloader is same after anti rollback update in V9.1.6.0
i want to root my device for titanium backup and use miui for now
i watch video relating anti roll back update but still confused as how i am gonna to install custom rom in future
and rollback to miui without bricking my device
Thanks
Regards
I know, its confusing to many. You can start by checking these threads:
https://forum.xda-developers.com/redmi-note-5-pro/how-to/faq-questions-answered-t3816185
https://forum.xda-developers.com/redmi-note-5-pro/how-to/index-everything-anti-roll-t3816219
I am on 9.5.19, unlocked, rooted, TWRP installed and have received update notice for 9.6.3.0, but do not want to update via OTA because will lose root, recovery (and maybe unlock?)
I believe after rooting, unlocking, and TWRP install, you need to download a version of the MIUI ROM you want without the included firmware. see here:
https://forum.xda-developers.com/redmi-note-5-pro/how-to/index-redmi-note-5-pro-miui-roms-t3816343
They dont have 9.6.3 listed so need to ask about that. Also not sure which version of ARB your phone has so you need to ask in above threads or if you have ADB installed can enter fastboot command: fastboot getvar anti
I've updated to 9.6.3 and don't see any relevant change in daily use. The bootloader is still unlocked but I've lost the changes in build prop for gcam installation. I was unrooted with no twrp (or rwrp) recovery installed
Here is firmware-less 9.6.3 version download: https://mirror.akhilnarang.me/MIUI/Global/Stable/
Taken from this post in the fw-less ROMs thread: https://forum.xda-developers.com/showpost.php?p=77390404&postcount=266
taco9 said:
I know, its confusing to many. You can start by checking these threads:
https://forum.xda-developers.com/redmi-note-5-pro/how-to/faq-questions-answered-t3816185
https://forum.xda-developers.com/redmi-note-5-pro/how-to/index-everything-anti-roll-t3816219
I am on 9.5.19, unlocked, rooted, TWRP installed and have received update notice for 9.6.3.0, but do not want to update via OTA because will lose root, recovery (and maybe unlock?)
I believe after rooting, unlocking, and TWRP install, you need to download a version of the MIUI ROM you want without the included firmware. see here:
https://forum.xda-developers.com/redmi-note-5-pro/how-to/index-redmi-note-5-pro-miui-roms-t3816343
They dont have 9.6.3 listed so need to ask about that. Also not sure which version of ARB your phone has so you need to ask in above threads or if you have ADB installed can enter fastboot command: fastboot getvar anti
Click to expand...
Click to collapse
My RN5 Pro is unlocked, with twrp, magisk (rooted), and running MIUI 9.5.19. Xiaomi gave me 9.6.3 last night, and although I wasn't able to install the delta update that they gave me (twrp didn't do anything with it), after the reboot, it downloaded the full 9.6.3 ROM. I then told it to do the update and twrp successfully installed it. At that point, I ONLY lost twrp and I assume magisk. The bootloader was unaffected by the MIUI upgrade.
Easy enough to fix - boot to fastboot, and used 'fastboot boot twrp.img' to get the phone started in twrp recovery mode. Then I was able to use twrp to install itself permanently/properly into the recovery partition, install lazyflasher, flash magisk, reboot normal. Phone's back to rooting state using magisk, but now with MIUI 9.6.3. 5 minutes and done.
taco9 said:
I know, its confusing to many. You can start by checking these threads:
https://forum.xda-developers.com/redmi-note-5-pro/how-to/faq-questions-answered-t3816185
https://forum.xda-developers.com/redmi-note-5-pro/how-to/index-everything-anti-roll-t3816219
I am on 9.5.19, unlocked, rooted, TWRP installed and have received update notice for 9.6.3.0, but do not want to update via OTA because will lose root, recovery (and maybe unlock?)
I believe after rooting, unlocking, and TWRP install, you need to download a version of the MIUI ROM you want without the included firmware. see here:
https://forum.xda-developers.com/redmi-note-5-pro/how-to/index-redmi-note-5-pro-miui-roms-t3816343
They dont have 9.6.3 listed so need to ask about that. Also not sure which version of ARB your phone has so you need to ask in above threads or if you have ADB installed can enter fastboot command: fastboot getvar anti
Click to expand...
Click to collapse
ok thanks for helping
tajima69 said:
I've updated to 9.6.3 and don't see any relevant change in daily use. The bootloader is still unlocked but I've lost the changes in build prop for gcam installation. I was unrooted with no twrp (or rwrp) recovery installed
Click to expand...
Click to collapse
sorry what did you meant by build prop for gcam installation
tajima69 said:
I've updated to 9.6.3 and don't see any relevant change in daily use. The bootloader is still unlocked but I've lost the changes in build prop for gcam installation. I was unrooted with no twrp (or rwrp) recovery installed
Click to expand...
Click to collapse
No change ?? Let me listout some changes for you
1. New VoLTE icon
2. In lockscreen time and date displays in centre
3. Messaging app suggest new plan offer and etc (AI reply)
4. Updated security patch
5. Imporved Battery life
6. New Ringtone and notification sounds
Cannot boot twtp.img
After Installing update gcam was not workig so i was in fastboot and i put command fastboot boot twtp.img but it is stucked in downloading boot.img
tajima69 said:
I've updated to 9.6.3 and don't see any relevant change in daily use. The bootloader is still unlocked but I've lost the changes in build prop for gcam installation. I was unrooted with no twrp (or rwrp) recovery installed
Click to expand...
Click to collapse
Battery draining fast in this update
SunilSuni said:
No change ?? Let me listout some changes for you
1. New VoLTE icon
2. In lockscreen time and date displays in centre
3. Messaging app suggest new plan offer and etc (AI reply)
4. Updated security patch
5. Imporved Battery life
6. New Ringtone and notification sounds
Click to expand...
Click to collapse
you sayin improved battery backup??? other people complaining about battery backup getting lowers by updates ..??? sach kya hai
Sent from my Redmi Note 5 Pro using Tapatalk
I have a OnePlus 5T locked and unrooted phone having OxygenOS 5.1.7 installed. I am new to rooting and related kinds of stuff. Can someone help me to give some instructions to install Magisk in my device? I know the below steps, but at the same time, I am having some questions in my mind.
1. Unlock bootloader - I saw some commands here to unlock bootloader - https://forum.xda-developers.com/showpost.php?p=74504347&postcount=4 - looks like these are outdated, last updated on Dec 2017. Are those work today also?
2. Install TWRP recovery - I heard that, OxygenOS 5.1.7 is having Project Treble supported. Can I use the same TWRP recovery mentioned in the above link?
3. Root using Magisk or SuperSU. What is the difference? What is systemless root? Anyway, I need to install Magisk Manager finally - Please suggest a way.
4. And the last one, How do I unroot my device if something goes wrong? Or is that possible?
5. I don't want to install any custom ROMs, I am fine with OOS.
https://www.youtube.com/watch?v=bTpxvmwBruQ&t=193s
Most of your questions have been answered on xda, youtube, and reddit before. Please try searching before posting.
sarathsnair said:
I have a OnePlus 5T locked and unrooted phone having OxygenOS 5.1.7 installed. I am new to rooting and related kinds of stuff. Can someone help me to give some instructions to install Magisk in my device? I know the below steps, but at the same time, I am having some questions in my mind.
1. Unlock bootloader - I saw some commands here to unlock bootloader - https://forum.xda-developers.com/showpost.php?p=74504347&postcount=4 - looks like these are outdated, last updated on Dec 2017. Are those work today also?
2. Install TWRP recovery - I heard that, OxygenOS 5.1.7 is having Project Treble supported. Can I use the same TWRP recovery mentioned in the above link?
3. Root using Magisk or SuperSU. What is the difference? What is systemless root? Anyway, I need to install Magisk Manager finally - Please suggest a way.
4. And the last one, How do I unroot my device if something goes wrong? Or is that possible?
5. I don't want to install any custom ROMs, I am fine with OOS.
Click to expand...
Click to collapse
1. Yes the unlock commands remain the same till date.
2. Use the latest bluspark twrp which has the treble support, link mentioned is fine and if you need the direct link, its here
3. Use the latest Magisk as SU is a dead project now.
4. Whenever you want to unroot just dirty remove/uninstall all the mods, dirty flash the latest stock rom > Factory reset in recovery and lock the bootloader. I did a post here for the 6T and it should work the same way on 5T.
5. You can stay rooted on OOS no need of custom roms any more :good:
Let me know if you want to know anything else, Thanks.
PS: Thread moved to Q&A Section
Funk Wizard said:
4. Whenever you want to unroot just dirty remove/uninstall all the mods, dirty flash the latest stock rom > Factory reset in recovery and lock the bootloader. I did a post here for the 6T and it should work the same way on 5T.
Click to expand...
Click to collapse
What happens to the installed twrp recovery if I unroot?
sarathsnair said:
What happens to the installed twrp recovery if I unroot?
Click to expand...
Click to collapse
Its replaced by stock recovery :good:
I got some more question too.
1.will I get official update from oneplus after my magisk root??
2.can I root my 5t with beta room ?
3.can I switch from beta to official and from official to beta once I rooted my device.
4.can I use confidential app like banking app.???
alisrovi said:
I got some more question too.
1.will I get official update from oneplus after my magisk root??
2.can I root my 5t with beta room ?
3.can I switch from beta to official and from official to beta once I rooted my device.
4.can I use confidential app like banking app.???
Click to expand...
Click to collapse
1. Yes, but your phone will download the whole firmware at each update instead of the ota.
2. Yes
3. Yep you can.
4. Yes of course, but some apps will detect root. So you will have to use Magisk Hide (inside the Magisk Manager) to hide root from these apps.
Note : I didn't use OOS anymore but it seems to me that OOS overwrites root everytime you update, so keep in mind that you will have to reflash it everytime
alisrovi said:
I got some more question too.
1.will I get official update from oneplus after my magisk root??
2.can I root my 5t with beta room ?
3.can I switch from beta to official and from official to beta once I rooted my device.
4.can I use confidential app like banking app.???
Click to expand...
Click to collapse
1- Yes, but you will recieve full sized zip (1.5+)GB automatically in rooted OOS. Incremental small sized ota won't work in case of root, and don't bother with it.
The downside of updating full whole zip is that you will loose root & twrp recovery after the update. So keep in mind, you will re-install both of them later.
2- I haven't tried beta, but i am sure yes
3- any switch between those requires clean flash in TWRP (wiping dalvik cache, cache, data, vendor and system). So, make sure to have backup in safe place.
4- yes, as long as you passed the safety net in Magisk. Magisk has a feature to hide root on certain apps of your choice, so you can use banking apps later
All my magisk installed whether in oos stable or custom roms, passed the safety net out of the box. So I haven't faced issues there.
If I unlock bootloader and apply TeamWin Recovery Project will that disable the ability to receive OTA updates?
I really would like Viper4Android! Thanks
Yes TWRP disables OTA updates. All system partitions need to be @Stock for a successful update via OTA.
Our TWRP is quite crappy and at best a beta version anyways.
You can install V4A quite easy as a Magisk module. Just check a root guide in the Guides section. It's just a matter of seconds to disable root for taking an OTA and re-enabling it again afterwards.
Hello!
Device: Mi 10T Pro
Current ROM: miui_APOLLOEEAGlobal_V12.1.2.0.RJDEUXM_cff0da241e_11.0 (Stable)
Android version: 11 RKQ1.200826.002
Bootloader: Currently 15hrs left to unlock
If one wants to root, stick with the stock ROM and possibly get OTA updates (looking forward to MIUI 12.5), what is the best method/option for rooting?
A) Patch boot.img with Magisk and flash it to device using fastboot
B) Install TWRP for Mi 10T/10T Pro by Whyle (TWRP_apollo_3.5.0_10-beta_1_whyle) by flashing it to BOOT and install Magisk using TWRP
C) Install TWRP for Mi 10T/10T Pro by Whyle (TWRP_apollo_3.5.0_10-beta_1_whyle) by flashing it to RECOVERY and install Magisk using TWRP
Thank you.
-=ApA=- said:
Hello!
Device: Mi 10T Pro
Current ROM: miui_APOLLOEEAGlobal_V12.1.2.0.RJDEUXM_cff0da241e_11.0 (Stable)
Android version: 11 RKQ1.200826.002
Bootloader: Currently 15hrs left to unlock
If one wants to root, stick with the stock ROM and possibly get OTA updates (looking forward to MIUI 12.5), what is the best method/option for rooting?
A) Patch boot.img with Magisk and flash it to device using fastboot
B) Install TWRP for Mi 10T/10T Pro by Whyle (TWRP_apollo_3.5.0_10-beta_1_whyle) by flashing it to BOOT and install Magisk using TWRP
C) Install TWRP for Mi 10T/10T Pro by Whyle (TWRP_apollo_3.5.0_10-beta_1_whyle) by flashing it to RECOVERY and install Magisk using TWRP
Thank you.
Click to expand...
Click to collapse
A) is the only choice, and you'll have to UNROOT before ota by flashing stock boot partition. C wouldn't work as we do not yet have complete working twrp.
And never flash recovery to boot partition, you'll brick your device, so B) is out of the question. And fastboot boot recovery.img is not the same as fastboot flash option, so take good care...
I just rooted my Mi 10T Pro and yes, A is the way to go. That way, you preserve your stock recovery while still letting yourself root the phone. Everything works, only after an OTA upgrade to Android 11 came, my phone got stuck in a bootloop, recoverable only by wiping doing a factory reset.
Aldenar said:
I just rooted my Mi 10T Pro and yes, A is the way to go. That way, you preserve your stock recovery while still letting yourself root the phone. Everything works, only after an OTA upgrade to Android 11 came, my phone got stuck in a bootloop, recoverable only by wiping doing a factory reset.
Click to expand...
Click to collapse
You didn't have to factory reset - just have to return to stock before ota - that's required because boot partition is changed by rooting and ota fails... So basically fastest method is flashing stock boot image before ota, making new one with magisk after ota and returning with full root
calinorg said:
A) is the only choice, and you'll have to UNROOT before ota by flashing stock boot partition. C wouldn't work as we do not yet have complete working twrp.
And never flash recovery to boot partition, you'll brick your device, so B) is out of the question. And fastboot boot recovery.img is not the same as fastboot flash option, so take good care...
Click to expand...
Click to collapse
Yes, i understand. Thank you calinorg and Aldenar.
Just so you know, after rooting (even after just unlocking bootloader), your SafetyNet (CTS profile) will fail. Yes, even if you rename your Magisk app, use MagiskHide and MagiskHide Props Config module. Personally it doesn't impact me much, cause even my banking apps are working without issues and my bank does not support NFC payments anyway. Only few apps, including infamous McDonalds app complain and do not run. I guess fast food is alot more sensitive industry than banking then . IMHO there is no point in detecting root in apps anyway. If all of your data is in your servers (with tamper checks), manipulating it on device level (like memory manipulation with games) would be pointless. More and more apps and games nowadays are using the same method. I guess McDonalds and all others alike should just fix their apps instead of blocking out rooted users.
More info on SafetyNet CTS profile failure and possible workaround here. Universal SafetyNet Fix Magisk module.
Since i don't have TWRP installed, im not eager to test SafetyNet fix yet, cause several users are reporting bootloops and problems with banking app security mechanisms. I'm guessing that (problematic) Magisk modules can be uninstalled by other means than just TWRP but still, i will wait for the more stable solution.
-=ApA=- said:
Yes, i understand. Thank you calinorg and Aldenar.
Just so you know, after rooting (even after just unlocking bootloader), your SafetyNet (CTS profile) will fail. Yes, even if you rename your Magisk app, use MagiskHide and MagiskHide Props Config module. Personally it doesn't impact me much, cause even my banking apps are working without issues and my bank does not support NFC payments anyway. Only few apps, including infamous McDonalds app complain and do not run. I guess fast food is alot more sensitive industry than banking then . IMHO there is no point in detecting root in apps anyway. If all of your data is in your servers (with tamper checks), manipulating it on device level (like memory manipulation with games) would be pointless. More and more apps and games nowadays are using the same method. I guess McDonalds and all others alike should just fix their apps instead of blocking out rooted users.
More info on SafetyNet CTS profile failure and possible workaround here. Universal SafetyNet Fix Magisk module.
Since i don't have TWRP installed, im not eager to test SafetyNet fix yet, cause several users are reporting bootloops and problems with banking app security mechanisms. I'm guessing that (problematic) Magisk modules can be uninstalled by other means than just TWRP but still, i will wait for the more stable solution.
Click to expand...
Click to collapse
I am using that exact Magisk module and it works like a charm - The SafetyNet check got downgraded back to Basic that and together with Magisk Hide, works like a charm!
Aldenar said:
I am using that exact Magisk module and it works like a charm - The SafetyNet check got downgraded back to Basic that and together with Magisk Hide, works like a charm!
Click to expand...
Click to collapse
Nice, thanks! I'll give it a try. What version of the module are you using? Latest release is v1.1.1 on GitHub.
-=ApA=- said:
Nice, thanks! I'll give it a try. What version of the module are you using? Latest release is v1.1.1 on GitHub.
Click to expand...
Click to collapse
Latest, so 1.1.1. As proof, see screenshots
Aldenar said:
Latest, so 1.1.1. As proof, see screenshots
Click to expand...
Click to collapse
Awesome, thanks!
EDIT: Also working for me just fine.
Any luck on 12.1.5.x or even 12.5 beta?
Illuvitar said:
Any luck on 12.1.5.x or even 12.5 beta?
Click to expand...
Click to collapse
12.5.1.0 was fine, now trying with 12.5.5.0
12.5.5.0 needs Universal SafetyNet Fix module update (i'm using 2.1.1), otherwise SafetyNet check will fail! With 12.5.1.0 it's still working fine with Universal Safetynet Fix 1.1.1 tho.
You will also need to install Riru to use Universal SafetyNet fix 2.1.1
Update:
12.5.12.0 still working. Had to rename magisk.db tho and reinstall Magisk 23.0.
Make sure not to update Magisk beyond version 23!
TLDR
ok first and foremost
i am able to flash back to miui stable
but there are banking/finance apps that are showing that the device isnt compatible or something
tried pixel experience but miss the memc feature of miui
now on weekly eu,but seems like cod mobile doesnt have 90hz
and thats the only game i play
so how do i flash back to stock and still be able to use the banking apps?
ive read that relocking bootloader will cause more problems than not
zeusseuz said:
TLDR
ok first and foremost
i am able to flash back to miui stable
but there are banking/finance apps that are showing that the device isnt compatible or something
tried pixel experience but miss the memc feature of miui
now on weekly eu,but seems like cod mobile doesnt have 90hz
and thats the only game i play
so how do i flash back to stock and still be able to use the banking apps?
ive read that relocking bootloader will cause more problems than not
Click to expand...
Click to collapse
It happens because Google's SafetyNet is triggered by you having an unlocked bootloader.
You can hide the unlocked bootloader by using Magisk and enabling MagiskHide in the Settings!
Or you can lock the bootloader again, but installing Magisk is really easy. You just patch boot.img from the Xiaomi.eu ZIP file with the Magisk app. Then you can do "fastboot flash boot boot.img" (I think thats the command!).
Or in case of new Custom ROM Installation, you can patch the boot.img even before the Custom ROM is installed. You just put the patched boot.img into the ZIP file.
Or you can rename Magisk.apk into Magisk.zip and flash it in TWRP.
if you'd like to flash back to stock, find the latest stock rom file on https://xiaomifirmwareupdater.com/, and use mi flash tool to flash it while in fastboot. make sure to select "clean all" and not "clean all and lock". I've never had safetynet issues just by having an unlocked bootloader, it's always been a ROM issue. .eu does pass safetynet, so if you'd like you can try to reflash that and see if you have better luck.