Related
Root twrp For Xiaomi Mi 5C-
Note-
Code:
I am Not Responsible for any Damage,Bootloop Dead SD-card, etc,
Must unlock Bootloader before Processing-
Instructions-
Download Default Version of S Droid toolkit From Here http://www.mediafire.com/file/dtss5boicvvws2b/S-Droid_toolkit_2.5.rar
Then Download S-droid Toolkit Mi 5c update Here http://www.mediafire.com/file/355e48p2ukizaoi/s-droid_toolkit_mi_5c_update.rar
Extract Default version inside a Folder, then Extract Mi 5c version in Default Version Folder, Must Overwrite All File,
Run S-Droid Toolkit exe file from It, And Then Select Your option, use Mi 5C [Not available in above screen short bcz it old] option to Install twrp, Root etc,
flash this to Root-
magisk manager and supersu
https://forum.xda-developers.com/attachment.php?attachmentid=4082450&d=1490043181
then Flash this ZIP [no-verity-opt-encrypt-5.1.zip] -
https://www.androidfilehost.com/?fid=673368273298927206
EU Rom Nougat-
try with this if Root Not Work with Official Rom,
http://miui.celogeek.com/7.4.6/xiaomi.eu_multi_MI5c_7.4.6_v8-7.1.zip
hit a thanks,
Interested in Donation Option Available in toolkit,
Visit My Blog For Other help or Different Way
Credit- Me
Xiaomi.eu
Make a Small Donation to Support me-
https://paypal.me/droiddeveloper
Rom installation and Fixes-
2 - Unlock the Bootloader
3 - Install the English TWRP in Fastboot mode[ Completed in above step]
4 - Install the EU ROM via TWRP
5- *#*#1#*#* --> TEL_Assistant --> Telephony --> Radio Acces Tec --> change to 5 Mode
6 - * # * # 4636 # * # * II Sim 1 and choose LTE /TD- SCMDA / WCMDA
Hi,
Tried rooting version multirom_MI5C_7.4.13_v7.1.1_b14 and it didn't work - just boots to fastboot. Also, when I change the settings to LTE /TD- SCMDA / WCMDA, they aren't stored and they revert back to the old settings. Any ideas why?
Stewart
this setting is only For EU Nougat Rom Not For Stock Rom, I means, First of all all unlock bootloader, then use toolkit to install twrp, and then create a nandroid backup using twrp, then flash superuser. Flash Eu Rom via twrp, again flash superuser ,This Recovery and Rom is only For 'Song' Not tested on 'Meri' you can also backup fastboot Rom using toolkit,
I'll try another ROM
Nothings! I have twrp song from EU forum and ROM 7.4.13, last EU rom.. But after flash root device go on fastboot mode!
How I can do for root this phone?!
Thanks
I rooted mine using this method
http://www.theandroidsoul.com/systemless-root-magisk-android/
Thanks... Work for me!
Only for global or also for Miui ITA?
stewc said:
I rooted mine using this method
http://www.theandroidsoul.com/systemless-root-magisk-android/
Click to expand...
Click to collapse
Wich Rom? And wich android version? I try to flash magisk v12 to nougat Miui ita, but only fastboot
Can you help me? Could you explain the procedure? Thanks in advance
I'm using multirom_MI5C_7.4.27_v7.1.2_b16_946a918689 from here https://mirror.byteturtle.eu/multirom/7.4.27/multirom_MI5C_7.4.27_v7.1.2_b16_946a918689.zip but I think you can use any ROM.
1. Flash TWRP from here https://www.androidfilehost.com/?fid=457095661767152790 using fastboot
2. Flash ROM using TWRP
3. Download Magisk v9 (.zip) from http://downloadmirror.co/Usj/Magisk-v9.zip
4. And phh’s SuperUser from here http://downloadmirror.co/Usk/phh-superuser-magisk-r266-2.zip
5. Put both files on your phone and boot into recovery.
6. Flash Magisk, then flash phh’s SuperUser then reboot.
7. Install phh’s SuperUser app from the Play Store.
Great!!!!
stewc said:
I'm using multirom_MI5C_7.4.27_v7.1.2_b16_946a918689 from here https://mirror.byteturtle.eu/multirom/7.4.27/multirom_MI5C_7.4.27_v7.1.2_b16_946a918689.zip but I think you can use any ROM.
1. Flash TWRP from here https://www.androidfilehost.com/?fid=457095661767152790 using fastboot
2. Flash ROM using TWRP
3. Download Magisk v9 (.zip) from http://downloadmirror.co/Usj/Magisk-v9.zip
4. And phh’s SuperUser from here http://downloadmirror.co/Usk/phh-superuser-magisk-r266-2.zip
5. Put both files on your phone and boot into recovery.
6. Flash Magisk, then flash phh’s SuperUser then reboot.
7. Install phh’s SuperUser app from the Play Store.
Click to expand...
Click to collapse
Thanks works!! But i don't understand why the latest Magisk v12 cause bootloop, anyway thank you so much Stew
Hi!
I have two questions in connection with it!
1. Formerly I flashed Xiaomi.eu ROM (Android N) which cannot guarantee ROOT for the phone, so I don't have it in the Permissions Menu.
Here comes the question, if I follow the described steps, will it turn up among the Permissions?
2. I use my phone in Hungary, accordingly only 4G network is available, 3G band is very weak or it is not available at all.
I read that the following setup can solve my problem if I do it in the Dialer menu:
* # * # 4636 # * # * II Sim 1 and choose LTE /TD- SCMDA / WCMDA
My current installation is not fit for it, because it reset itself back automatically to the default factory settings - LTE/UMTS auto (PRL)
Can you please check it for mer whether the Magisk and phh's SuperUser installation can solve this problem and I can use the LTE /TD- SCMDA / WCMDA setting?
Thanks in advance for your effort!
1. You won't see anything in the permissions menu for root so I don't understand the question.
2. Its a bug on the phone. It looks like it resets but reboot the phone and it will show LTE /TD- SCMDA / WCMDA. Rooting won't solve this or affect it.
Thanks for the quick response!
1. I have a Redmi Note 2 as well, after I installed the SuperSu, a new menu pont turned up in the Permissions, it's called Root permissions. Therefore I asked that it works the same way in case of Mi5c or not.
2. Are you sure? After the reboot it shows the same LTE/UMTS as previously... Does the bug mean that works correctly but shows wrong settings or how do you mean?
1. Just checked and I don't have an extra menu in permissions so it must depend on the ROM/phone. Yeah looks like it's not on the Mi5C.
2. I think you're right. I rebooted my phone and it's showing LTE/UMTS auto. But I get 4G OK. Not sure if it's actually changed or a bug.
developers 7.1.1?
stewc said:
1. Just checked and I don't have an extra menu in permissions so it must depend on the ROM/phone. Yeah looks like it's not on the Mi5C.
2. I think you're right. I rebooted my phone and it's showing LTE/UMTS auto. But I get 4G OK. Not sure if it's actually changed or a bug.
Click to expand...
Click to collapse
developers 7.1.1?
---------- Post added at 12:39 AM ---------- Previous post was at 12:38 AM ----------
Brunaldo77 said:
Thanks works!! But i don't understand why the latest Magisk v12 cause bootloop, anyway thank you so much Stew
Click to expand...
Click to collapse
How to install rom developers 7.1.1
Root is Perfect Working Just flash magisk 12.0....
gari1226 said:
developers 7.1.1?
---------- Post added at 12:39 AM ---------- Previous post was at 12:38 AM ----------
How to install rom developers 7.1.1
Click to expand...
Click to collapse
I have Rom Xiaomi.eu ToughBook can download it and flash. Simply
password
i used password stupdroid and always fail, what the pasword who must input ?
farzero said:
i used password stupdroid and always fail, what the pasword who must input ?
Click to expand...
Click to collapse
turn of caps Lock.....
is Right
Hi,
I'm a happy new owner of the redmi note 4 and I've already unlocked the bootloader.
I would like to use google camera, and eventually adblock.
I've seen there are various way to
- install bootloaders (and it seems there are also various boatloaders)
- root the phone
- enable camera2 api, with and without root
- ...
Actually I like to keep the stock rom and the phone as vanilla as possible, as I've read there are redundant issue with custom rom. I also do like the idea of being able to update the phone "normally", which seems to be what you call OTA update . Also, I've seen that some app may not work if some verification fails ?
So basically the question could you explain me a bit the broad picture and what would you recommend ?
Thank's
PS : sorry I'm not super acurate, I rooted my LG G2 years ago and things seems to have evolved a lot since then.
jbonlinea said:
Hi,
I'm a happy new owner of the redmi note 4 and I've already unlocked the bootloader.
I would like to use google camera, and eventually adblock.
I've seen there are various way to
- install bootloaders (and it seems there are also various boatloaders)
- root the phone
- enable camera2 api, with and without root
- ...
Actually I like to keep the stock rom and the phone as vanilla as possible, as I've read there are redundant issue with custom rom. I also do like the idea of being able to update the phone "normally", which seems to be what you call OTA update . Also, I've seen that some app may not work if some verification fails ?
So basically the question could you explain me a bit the broad picture and what would you recommend ?
Thank's
PS : sorry I'm not super acurate, I rooted my LG G2 years ago and things seems to have evolved a lot since then.
Click to expand...
Click to collapse
So, you want root and GCam working on your MIUI without breaking OTA updates, is that right?
• Unlock bootloader, flash RedWolf recovery then through Redwolf recovery flash LazyFlasher.
• In Redwolf enable OTA survival.
• Flash Magisk through recovery for root.
• For GCam to work, you need to enable Camera2API in your build.prop. This can be done through a simple Magisk module too. But I must warn you enabling Camera2API on MIUI might break some functionalities of your MIUI stock camera app.
I am using pixel experience 8.1 oreo rom in my redmi notr 4.and i have also install google canera mod.mgcmod5.i have done all the settings but ehen i am trying to take puctures its force closing and lagging..need solution..
ArK96 said:
So, you want root and GCam working on your MIUI without breaking OTA updates, is that right?
• Unlock bootloader, flash RedWolf recovery then through Redwolf recovery flash LazyFlasher.
• In Redwolf enable OTA survival.
• Flash Magisk through recovery for root.
• For GCam to work, you need to enable Camera2API in your build.prop. This can be done through a simple Magisk module too. But I must warn you enabling Camera2API on MIUI might break some functionalities of your MIUI stock camera app.
Click to expand...
Click to collapse
After every OTA update do I need to re-flash everything?
ÀnkanKoley said:
After every OTA update do I need to re-flash everything?
Click to expand...
Click to collapse
If RedWolf succeeds OTA survival, then there is no need. But after OTA if RedWolf is replaced by stock recovery, then yes you'll have to flash everything once again. Refer RedWolf thread for more details on OTA survival.
ArK96 said:
So, you want root and GCam working on your MIUI without breaking OTA updates, is that right?
• Unlock bootloader, flash RedWolf recovery then through Redwolf recovery flash LazyFlasher.
• In Redwolf enable OTA survival.
• Flash Magisk through recovery for root.
• For GCam to work, you need to enable Camera2API in your build.prop. This can be done through a simple Magisk module too. But I must warn you enabling Camera2API on MIUI might break some functionalities of your MIUI stock camera app.
Click to expand...
Click to collapse
Sounds right and great, thank's !
Two question.
- I've read somewhere that some custom recovery and/or root may cause some app to fail, notably banking app.
Well I used to use such app on my rooted G2 , but will it remain posible after folowing the process you suggest above ?
about redwolf, there is quite a lot of explainations in theses two links 1 and 2, however I can figure out how to install redwolf ?! what am I suppose to do with the .iso image available for download ? isn't there a step by step install guide somewhere ?
Thank's
jbonlinea said:
Sounds right and great, thank's !
Two question.
- I've read somewhere that some custom recovery and/or root may cause some app to fail, notably banking app.
Well I used to use such app on my rooted G2 , but will it remain posible after folowing the process you suggest above ?
about redwolf, there is quite a lot of explainations in theses two links 1 and 2, however I can figure out how to install redwolf ?! what am I suppose to do with the .iso image available for download ? isn't there a step by step install guide somewhere ?
Thank's
Click to expand...
Click to collapse
Use Magisk for root and once Magisk is installed enable Magisk hide for the banking app, this will hide root from that particular app.
Installing a custom recovery like redwolf :
1. Unlock your phone's bootloader.
2. Download the recovery image file, rename it to "recovery.img" and place in a folder on your computer. Make sure you have working ADB and fastboot drivers installed on this computer.
3. Connect your phone in fastboot mode (Volume Down + Power button)
4. Open command prompt in the folder containing the downloaded recovery. (Shift + Mouse right click)
5. Type the below command into the command prompt
fastboot flash recovery recovery.img
fastboot boot recovery.img
Once inside recovery flash ROM, Magisk, if ROM is MiUI flash lazyflasher too, or phone won't boot. If custom ROM ignore lazyflasher and flash GApps instead.
If recovery installation instructions confuse you there are infinite number of YouTube videos that will help you.
ArK96 said:
So, you want root and GCam working on your MIUI without breaking OTA updates, is that right?
• Unlock bootloader, flash RedWolf recovery then through Redwolf recovery flash LazyFlasher.
• In Redwolf enable OTA survival.
• Flash Magisk through recovery for root.
• For GCam to work, you need to enable Camera2API in your build.prop. This can be done through a simple Magisk module too. But I must warn you enabling Camera2API on MIUI might break some functionalities of your MIUI stock camera app.
Click to expand...
Click to collapse
What would broke on miui camera?
amnher said:
What would broke on miui camera?
Click to expand...
Click to collapse
The HDR mode.
ArK96 said:
Use Magisk for root and once Magisk is installed enable Magisk hide for the banking app, this will hide root from that particular app.
Installing a custom recovery like redwolf :
1. Unlock your phone's bootloader.
2. Download the recovery image file, rename it to "recovery.img" and place in a folder on your computer. Make sure you have working ADB and fastboot drivers installed on this computer.
3. Connect your phone in fastboot mode (Volume Down + Power button)
4. Open command prompt in the folder containing the downloaded recovery. (Shift + Mouse right click)
5. Type the below command into the command prompt
fastboot flash recovery recovery.img
fastboot boot recovery.img
Once inside recovery flash ROM, Magisk, if ROM is MiUI flash lazyflasher too, or phone won't boot. If custom ROM ignore lazyflasher and flash GApps instead.
If recovery installation instructions confuse you there are infinite number of YouTube videos that will help you.
Click to expand...
Click to collapse
Thank's again , that's awesome!
Maybe a few more question
FIRST
at step 2) how do I make sure I have a working ADB and Fastboot drivers ?
As far as I understand, fastboot drivers should already be installed ; however I suspect ADB not to be installed.
Indeed, I've already unlocked the bootloader with this tutorial, and I can confirm the phone is unlocked from settings > more settings > developper options > Mi locking status.
So basically I've already installed MiUSBDrivers and ran miflashunlock. There are fastboot.exe, fastboot_unlock.exe and AdbWinApi.dll files in the miflash_unlock folder I downloaded and used to unlock, but I haven't used any of these later 3 files.
I have found this post to install ADB
SECOND
at step 4), the best would be to place the recovery image downladed from here into the folder containing ADB downloaded just above right ?
Then, go on with step 5)
THIRD
If everything went well, my phone is supposed to reboot in redwolf recovery, ok.
but whart do you mean by "Once inside recovery flash ROM" ?
Why am I suposed to flash a rom ?
To my understanding, I already have a rom, miui, and do not want to change for the moment.
Should I download the "Full Rom" from here, or the "Redmi Note 4 Qualcomm Latest Global Stable Version Fastboot File" rom from here ? If so, what souhld I do with the rom; where sould I place it, on the computer, on the phone ?
Or do I need to flash ROM only if I want to change/upgrade my rom ?
FOURTH
To flash Magisk and Lazyflasher.
I understood that redwolf recovery comes with Magisk, so I assume I'll only have to go to "install" tab of redwolf, and I'll find the Magisk file to flash.
Ok what about Lazyflasher ? is it also provided with redwolf ?
Or should I download it ? and if so where should I place the file ?
FIFTH (and last)
I assume once installed from recovery, Magisk will show himself as an app/icon on the "desktop", and I'll be able to selectively enable Magisk hide for the banking app.
Thank's again for your help.
Sorry if I have too many questions, I'm a little rusted, and prefer having a comprehensive picture of the porcess before jumping into it, and avoid one more post entitled helpppp pleeeeeese I bricked my phone
jbonlinea said:
Thank's again , that's awesome!
Maybe a few more question
FIRST
at step 2) how do I make sure I have a working ADB and Fastboot drivers ?
As far as I understand, fastboot drivers should already be installed ; however I suspect ADB not to be installed.
Indeed, I've already unlocked the bootloader with this tutorial, and I can confirm the phone is unlocked from settings > more settings > developper options > Mi locking status.
So basically I've already installed MiUSBDrivers and ran miflashunlock. There are fastboot.exe, fastboot_unlock.exe and AdbWinApi.dll files in the miflash_unlock folder I downloaded and used to unlock, but I haven't used any of these later 3 files.
I have found this post to install ADB
SECOND
at step 4), the best would be to place the recovery image downladed from here into the folder containing ADB downloaded just above right ?
Then, go on with step 5)
THIRD
If everything went well, my phone is supposed to reboot in redwolf recovery, ok.
but whart do you mean by "Once inside recovery flash ROM" ?
Why am I suposed to flash a rom ?
To my understanding, I already have a rom, miui, and do not want to change for the moment.
Should I download the "Full Rom" from here, or the "Redmi Note 4 Qualcomm Latest Global Stable Version Fastboot File" rom from here ? If so, what souhld I do with the rom; where sould I place it, on the computer, on the phone ?
Or do I need to flash ROM only if I want to change/upgrade my rom ?
FOURTH
To flash Magisk and Lazyflasher.
I understood that redwolf recovery comes with Magisk, so I assume I'll only have to go to "install" tab of redwolf, and I'll find the Magisk file to flash.
Ok what about Lazyflasher ? is it also provided with redwolf ?
Or should I download it ? and if so where should I place the file ?
FIFTH (and last)
I assume once installed from recovery, Magisk will show himself as an app/icon on the "desktop", and I'll be able to selectively enable Magisk hide for the banking app.
Thank's again for your help.
Sorry if I have too many questions, I'm a little rusted, and prefer having a comprehensive picture of the porcess before jumping into it, and avoid one more post entitled helpppp pleeeeeese I bricked my phone pen
Click to expand...
Click to collapse
ADB/Fastboot Drivers
Looks like you don't have ADB/Fastboot installed system wide. Although it is completely fine to use adb/fastboot in a folder, installing it system wide is much more convenient because you can open a command window in any folder and execute ADB/Fastboot commands. [URL="https://forum.xda-developers.com/showthread.php?t=2588979”]Here's the link[/URL] to download the system wide installer. Install it and REBOOT your PC.
Flashing RedWolf
Once drivers are installed and PC rebooted, connect phone in Fastboot mode and follow my previous instructions. Also now you can open command prompt in any folder and execute the commands since ADB/Fastboot is installed system wide.
Flashing ROM
Sorry if I confused you there in the previous post. If you wish to stick with your current MIUI ROM then you don't need to flash any ROM file.
Flashing Lazyflasher
You MUST flash lazyflasher since you want to stay with MIUI. If you install a custom recovery on MIUI without flashing lazyflasher, the phone will not boot and will be stuck at the MI logo. I've attached the file.
Flashing Magisk
Flash Magisk after lazyflasher. You may download the latest package from Magisk thread or use RedWolf's built in Magisk package as you said and update it later through the Magisk manager app. And yes, you can select which apps can be Magisk hidden.
ArK96 said:
ADB/Fastboot Drivers
Looks like you don't have ADB/Fastboot installed system wide. Although it is completely fine to use adb/fastboot in a folder, installing it system wide is much more convenient because you can open a command window in any folder and execute ADB/Fastboot commands. [URL="https://forum.xda-developers.com/showthread.php?t=2588979”]Here's the link[/URL] to download the system wide installer. Install it and REBOOT your PC.
Flashing RedWolf
Once drivers are installed and PC rebooted, connect phone in Fastboot mode and follow my previous instructions. Also now you can open command prompt in any folder and execute the commands since ADB/Fastboot is installed system wide.
Flashing ROM
Sorry if I confused you there in the previous post. If you wish to stick with your current MIUI ROM then you don't need to flash any ROM file.
Flashing Lazyflasher
You MUST flash lazyflasher since you want to stay with MIUI. If you install a custom recovery on MIUI without flashing lazyflasher, the phone will not boot and will be stuck at the MI logo. I've attached the file.
Flashing Magisk
Flash Magisk after lazyflasher. You may download the latest package from Magisk thread or use RedWolf's built in Magisk package as you said and update it later through the Magisk manager app. And yes, you can select which apps can be Magisk hidden.
Click to expand...
Click to collapse
Awesome !
Great to know that I should fisrt flash lazyflasher and then magisk.
Stupid, probably last question
Should I do everything up to and incliding flashing lazyflsher, rebot normally, and then reboot again in redwolf and flash magisk ?
of is this extra zealous ?
Thanks
jbonlinea said:
Awesome !
Great to know that I should fisrt flash lazyflasher and then magisk.
Stupid, probably last question
Should I do everything up to and incliding flashing lazyflsher, rebot normally, and then reboot again in redwolf and flash magisk ?
of is this extra zealous ?
Thanks
Click to expand...
Click to collapse
While it can all be flashed at one go, I suggest you to flash LF and once boot your device successfully and reboot to redwolf and flash Magisk afterwards.
ArK96 said:
While it can all be flashed at one go, I suggest you to flash LF and once boot your device successfully and reboot to redwolf and flash Magisk afterwards.
Click to expand...
Click to collapse
Thank you very much !
jbonlinea said:
Thank you very much !
Click to expand...
Click to collapse
No problem.
ArK96 said:
No problem.
Click to expand...
Click to collapse
hum, :silly:
the link you sent for adb do not work
jbonlinea said:
hum, :silly:
the link you sent for adb do not work
Click to expand...
Click to collapse
Here,
https://www.dropbox.com/s/mcxw0yy3jvydupd/adb-setup-1.4.3.exe?dl=0
ArK96 said:
Here,
https://www.dropbox.com/s/mcxw0yy3jvydupd/adb-setup-1.4.3.exe?dl=0
Click to expand...
Click to collapse
Excellent !
so
- I did installed redwolf recovery - changed settings as advised here
- flashed lazyflasher
- reboot -> wokrs I'm back on miui
- reboot in redwolf and flashed magisk
- reboot into android, installed rootchek, I'm rooted
- hide magisk from magisk manager for my apps --> working
Everything works
Further questions :
- Am I suppose to clean cache at some stage ? I can still do it now ?
- Is there some recomended module for magisk ? (not sure what they are for)
- as for everything else, I've seen many options to enable camera2api. Which one would you recomend ? is "persist.camera.HAL3.enabled=1" the only needed change or this treat rises something this
- is there a recomended version/release of google camera to use with miui9 global, latest update (not developper) (I've seen various reported issues depending on version/release)
- any other must/nice/interesting hacks to fully enjoy this phone ?
- any security recomendation ? (re-locking the bootloader ? instally some utilities... ?)
thanks
after that, I'll be done
jbonlinea said:
Excellent !
so
- I did installed redwolf recovery - changed settings as advised here
- flashed lazyflasher
- reboot -> wokrs I'm back on miui
- reboot in redwolf and flashed magisk
- reboot into android, installed rootchek, I'm rooted
- hide magisk from magisk manager for my apps --> working
Everything works
Further questions :
- Am I suppose to clean cache at some stage ? I can still do it now ?
- Is there some recomended module for magisk ? (not sure what they are for)
- as for everything else, I've seen many options to enable camera2api. Which one would you recomend ? is "persist.camera.HAL3.enabled=1" the only needed change or this treat rises something this
- is there a recomended version/release of google camera to use with miui9 global, latest update (not developper) (I've seen various reported issues depending on version/release)
- any other must/nice/interesting hacks to fully enjoy this phone ?
- any security recomendation ? (re-locking the bootloader ? instally some utilities... ?)
thanks
after that, I'll be done
Click to expand...
Click to collapse
Clean cache not required.
Magisk modules are MODs for your system but they are done without tampering your system. (Systemless MODs).
Try Dolby atmos ZTE Axon 7 audio MOD module, YouTube vanced module (100% Adfree, background play)..etc
Use Arnova's GCam.
Never ever relock bootloader with a custom recovery or custom ROM. Else irreversible brick.
I've repeated too much stuff that has been posted in the forum already, if you have any further doubts search the forum or use Google.
Flash through redwolf the attached file to enable camera2api. If you want to uninstall it later go to magisk manager and delete it.
Cheers.
ArK96 said:
Clean cache not required.
Magisk modules are MODs for your system but they are done without tampering your system. (Systemless MODs).
Try Dolby atmos ZTE Axon 7 audio MOD module, YouTube vanced module (100% Adfree, background play)..etc
Use Arnova's GCam.
Never ever relock bootloader with a custom recovery or custom ROM. Else irreversible brick.
I've repeated too much stuff that has been posted in the forum already, if you have any further doubts search the forum or use Google.
Flash through redwolf the attached file to enable camera2api. If you want to uninstall it later go to magisk manager and delete it.
Cheers.
Click to expand...
Click to collapse
Hi dude
I'm almost done but back to square 0, with blinking black screen at boot !
No crisis, I can still go to redwolf recovery, as well as fastboot.
How it happend ?
In magisk manager (on miui) I checked what modules were available in the download panel, and tried "Google Pixel 2 Experience" or something similar.
On reboot, the mi logo is displayed, then I have a black screen blinking on and off, without mi logo, just black, on and off
I thus wanted to unistal the mod with magisk module uninstaller, but the install fails and return that "magisk is not installed" and "magisk is required for this mod"
So I obviously couldn't try to uninstall the supposed failing module
I thus rebooted in redwold and installed magisk from redwolf (the included release), things went well
However, I still cant install magisk module uninstaller, getting the same error as above.
I took my chance and try to re-install magisk from the zip filed I downloaded, the install process was successfull, but I still can't install magisk mod uninstaller, and the black screen issue persist.
Lastly, I took my chance and try to re-install lazy flasher, the install process was successfull, but the black-screen issue persist.
To be honest, I'm a bit sctuck now.
What may be the right procedure to solve this problem ?
Am I screwed and do I have to reflash a whole rom ?
If so Should I do it from redwolf, and how ?
Or should I do it from the pc with fastboot, and how ?
Thanks for your directions
ps: i was interested by pixel 2 experience module as at it was written that it was compatible with mido and provides camera2api, which might have been a nice combo.
ps 2 : I also did installed dolby as you suggested, it worked but the demo crashed to app
ps 3 : I also did installed youtube vaccant, but I couldn't see any new app and my original youtube still had add and couldn't play in the back... not sure it reveals something on the effectiveness of magisk...
this guide help you to root k20/mi9t by using magisk patched boot img
this guide is for users who likes to be on stock with magisks modules customisation
advantage
[no data loss in whole process]
[safety passes okk]
[install modules like dolby,viper4android after root to improve sound quality]
REQUIREMENTS
.unlocked bootloader( its one time requirement)
.magisk patched boot img
patched boot img is created using stock boot img that is different for every miui version,so create your own patched boot img according to your miui version by this easy process https://forum.xda-developers.com/mi...dian-rom-v10-3-6-0-twrp-t3958566/post80163818
just to be on safe side remove all types of lock, u can use lock after all steps completed
NOW FOLLOW THE STEPS
install latest magisk manager apk
place the downloaded magisk patched boot img to adb folder or platform tool folder whatever u call in pc
1.boot your phone into fastboot by holding power menu &volume down button togethor
2.connect your phone to pc using original cable
3.Go to adb folder & open command window by clicking shift+control+right key on the blank space (command window appear in option)
4.now check your devices by if its properly connected by typing
code: fastboot devices
if it shows attached devices then proceed
5.now flash patched img by typing command
code: fastboot flash boot magisk_patched.img
finally boot your phone to system by typing command
code: fastboot reboot
6.now open magisk manager it show some recommendation just reject that option(important steps)
7.click on install in magisk manager then select direct install recommended option
let it install &reboot [step 7 is neccessary otherwise you cant install module in magisk)
this is 100% tested method
need any help or confused comment down below before attempting this
hit THANKS BUTTON IF U LIKE
Is bootloader unlock is required because you didn't mentioned that....
if u debloat xioami apps in miui roms & do some customization with magisk module .its become quite useful rom for a while now until stable custom rom available for use
RSM10 said:
Is bootloader unlock is required because you didn't mentioned that....
Click to expand...
Click to collapse
yes bootloder unlocked is required this is basic
u can do very little customisation like debloating with locked bootloader
Thanks I knew that bl unlock is required but since you didn't mentioned it here I thought you found a way out without unlocking bl. This patched boot.img is for 10.3.6.0 What if there is new update, then we will lost root.
i will try to provide patched boot img for future updates
rkview37 said:
this guide help you to root k20 by using magisk patched boot img
this guide is for users who likes to be on stock with magisks modules customisation
advantage
[no data loss in whole process]
[safety passes okk]
[install modules like dolby,viper4android after root to improve sound quality]
REQUIREMENTS
.unlocked bootloader
.magisk patched boot img (download from link below)
.must be on miui v10.3.6.0
just to be on safe side remove all types of lock, u can use lock after all steps completed
download magisk patched boot img provided by me
https://mega.nz/#!CpUz3KwB!76fE3z30gngG282mA9DzS05AZyjG6RuQFs5-STg2kXE
now follow steps carefully
install latest magisk manager apk
place the downloaded magisk patched boot img to adb folder or platform tool folder whatever u call in pc
1.boot your phone into fastboot by holding power menu &volume down button togethor
2.connect your phone to pc using original cable
3.Go to adb folder & open command window by clicking shift+control+right key on the black space (command window appear in option)
4.now check your devices by if its properly connected by typing
code: adb devices
if it shows attached devices then proceed
5.now flash patched img by typing command
code: fastboot flash boot magisk_patched.img
finally boot your phone to system by typing command
code: fastboot reboot
6.now open magisk manager it show some recommendation just reject that option(important steps)
7.click on install in magisk manager then select direct install recommended option
let it install &reboot [steps 7 is neccessary otherwise you cant install module in magisk)
this is 100% tested method
need any help or confused comment down below before attempting this
hit THANKS BUTTON IF U LIKE
Click to expand...
Click to collapse
Thank you keep updating as and when stock updates are received.
Sent from my [device_name] using XDA-Developers Legacy app
If we receive ota update. How should we install? Will magisk stay?
Sent from my [device_name] using XDA-Developers Legacy app
Can i do magisk update regularly?
manan001 said:
If we receive ota update. How should we install? Will magisk stay?
Sent from my [device_name] using XDA-Developers Legacy app
Can i do magisk update regularly?
Click to expand...
Click to collapse
1)as we all know k20 is single partition device.so we cannot perform ota whiile preserving magisk,i will update op with all info once i figured out a way to save effort of installing all modules all over again
2)magisk can be updated regularly,no issues at all
Finally installed magisk. Thanks for the detail steps. It works well.
Sent from my [device_name] using XDA-Developers Legacy app
10.3.8 OTA update available.
Patched boot.
https://drive.google.com/folderview?id=1-3QhAjIH5JmrlZaYgsCjr92XjcUv90nN
Sent from my [device_name] using XDA-Developers Legacy app
manan001 said:
10.3.8 OTA update available.
Patched boot.
https://drive.google.com/folderview?id=1-3QhAjIH5JmrlZaYgsCjr92XjcUv90nN
Click to expand...
Click to collapse
from where did you extracted stock boot img
afaik latest 10.3.8.0 stock rom not available on any site yet
manan001 said:
10.3.8 OTA update available.
Patched boot.
Do you have the stock recovery.img ?
How to update via OTA when i am on twrp ?
Can you confirm if root working after flashing your patched boot image ?
Click to expand...
Click to collapse
rkview37 said:
from where did you extracted stock boot img
afaik latest 10.3.8.0 stock rom not available on any site yet
Click to expand...
Click to collapse
In phone update we get option to download full rom ota. I downloaded and extracted boot.img, rest you know the process.
If you like my work do hit like button.
Dear Rkview31
If the flash install of the patched image fails, can we reinstall de rom with miflash? Or, is enough to reflash by fastboot command line the original fastboot rom image?
Can any one provide stock recovery (10.3.6) please.
neek619 said:
Can any one provide stock recovery (10.3.6) please.
Click to expand...
Click to collapse
go here
download from my mega account
https://mega.nz/#!Ok8yBYaB!N9CnTLSfpvoakHiQGDyyIxDvEL0MUmUsxAQqj3nhSu0
Guys
This procedure wokrs with eea device?
mauriciocardoso said:
Guys
This procedure wokrs with eea device?
Click to expand...
Click to collapse
guide is okk but stock boot img of every rom is different so patched boot img in this thread will not work for u
rkview37 said:
go here
download from my mega account
https://mega.nz/#!Ok8yBYaB!N9CnTLSfpvoakHiQGDyyIxDvEL0MUmUsxAQqj3nhSu0
Click to expand...
Click to collapse
Thanks for the file, was able to update to 10.3.8
Patched boot image by @manan001 in the link above do not work and reboots phone in recovery mode.
Patched my own boot image works fine with 10.3.8
https://drive.google.com/file/d/1-odNizuv4HlEw92O8tl_X13aQxdFwbGe/view?usp=drivesdk
Ah, So You've rooted your 6.1 Plus/X6 but don't know how to Install stock or having troubles with it? I'm here to help!
*All of the instructions and procedures below requires an unlocked bootloader. If you do not have an unlocked bootloader, Please refrain from asking about it here.
*Not having an unlocked bootloader and following this will definitely brick your phone. You have been warned.
Installing Stock ROM - Method 1A(Nost) --
1. Get NOST from here - NOST
2. NOST ONLY SUPPORT OREO FIRMWARE, USE OST LA FOR PIE(Not sharing cause its a patched app, Search on Google and get it from TechMesto)
3. Download unpacked oreo firmware, You can get it from - Here
4. Extract the zip on your PC
5. Put your phone in bootloader mode, Power off - Press Volume Down+Power Button.
6. Now connect it to your PC
7. Open NOST, Select the .mlf file from the folder where you extracted the Firmware
8. Now select, Normal download and Erase User data option.
9. Now click on next and wait for NOST to flash the phone. (It takes 258 seconds or 2.3 - 2.5 minutes on my laptop)
Installing Stock ROM - Method 1B(OST LA) --
Same as NOST, It has the same UI.
Except You might have to change some values in the .mlf file.
An appropriate guide for the same - Here
Installing Stock ROM - Method 2(Hikary's Generic Flashing Script) --
I recommend this method more than NOST and OST LA.
1. Get Hikary's script from - Here
2. Get unpacked Firmware from - Here
3. Extract the Firmware
4. Put the .exe file you got from Github into the folder where you Extracted the firmware
5. Run the script
6. Follow instructions on screen
7. Profit!
Thanks alot to member - Hikary for this easy to use scipt!
You've installed Stock, Now let's add some magisk to it !
*Please disable Automatic System Updates through developer options to make taking OTA .zips easier.
Installing Magisk - Method 1A(Fastboot method) -
You will need Google's ADB drivers, Which you can get - Here/
1. Extract ADB to a Folder
2. Get Magisk patched boot images from - Here Don't worry, Boot images for Nokia 7 Plus will work on DRG(6.1 Plus/X6) and PL2(6.1)
3. Open adb(Type cmd in the address bar of the folder where you extracted adb)
4. Put your device on Download mode
5. type the command
Code:
fastboot boot 'nameofbootimage'.img
6. Now your phone will boot
7. Install Latest Magisk Manger from - [https://www.github.com/topjohnwu/magisk/releases]Here[/url]
8. Open Magisk Manger, You will see Magisk is installed, But there will also be an Install Button next to it. Tap on Install.
9. Let Magisk Install and re-boot the phone
10. Viola Magisk is now permenantly available
Installing Magisk - Method 1B(TWRP method) -
You will need Google's ADB drivers, Which you can get - Here/
1. Get the latest TWRP for 6.1 Plus
2. Get the Latest Magisk Installer from - [https://www.github.com/topjohnwu/magisk/releases]Here[/url]
3. Put the .zip file to your Internal Storage/SD Card
4. Open adb and pass the command
Code:
fastboot boot "nameofrecoveryfile.img"
5. Now TWRP will open on your phone
6. Install Magisk through TWRP
7. Wipe Dalvik
8. Reboot
9. Profit
Now you've got magisk. Follow the next post to see how to take an OTA update with Magisk Installed.
Nokia 6.1 Plus is an Android One certified device. Nokia is no slouch either when it comes to issuing updates. Learn how to take OTA without losing root.
1. Turn of Auto System updates through Developer options
2. Open Magisk Manager
3. Restore Stock Images but don't reboot.
4. Download and install, Let both the steps finish i.e applying update and apps, but don't reboot.
5. Go to magisk manager and select install to inactive slot option
6. Re-boot device.
7. You've not lost root, But have root access.
Done
CarbonGTR said:
Nokia 6.1 Plus is an Android One certified device. Nokia is no slouch either when it comes to issuing updates. Learn how to take OTA without losing root.
1. Turn of Auto System updates through Developer options
2. Open Magisk Manager
3. Restore Stock Images but don't reboot.
4. Download and install, Let both the steps finish i.e applying update and apps, but don't reboot.
5. Go to magisk manager and select install to inactive slot option
6. Re-boot device.
7. You've not lost root, But have root access.
Done
Click to expand...
Click to collapse
I don't see any option to restore stock images or install to inactive slot in Magisk. Am I missing something?
Hymix said:
I don't see any option to restore stock images or install to inactive slot in Magisk. Am I missing something?
Click to expand...
Click to collapse
Open Magisk Manager, Tap on Uninstall. You will see 2 options, Complete Uninstall and restore stock images.
*Nevar tap on the complete uninstall option, It will throw your phone into bootloop
To install to inactive slot, Tap on install, You will get 2 options, Release Notes and Install. Tap on Install again and select install to inactive slot, Reboot from within Magisk Manager.
The simplest way I've found to install Stock Rom is just using adb sideload.
Boot into TWRP and wipe as you would with any custom rom.
Go to advanced and adb sideload.
Send the adb sideload command from your computer with the relevant zip file.
Doesn't require any additional softward like NOST or OST....
Hymix said:
The simplest way I've found to install Stock Rom is just using adb sideload.
Boot into TWRP and wipe as you would with any custom rom.
Go to advanced and adb sideload.
Send the adb sideload command from your computer with the relevant zip file.
Doesn't require any additional softward like NOST or OST....
Click to expand...
Click to collapse
But does it also install the bootloader and stock recovery back? If yes then I'll add it to the post above.
CarbonGTR said:
But does it also install the bootloader and stock recovery back? If yes then I'll add it to the post above.
Click to expand...
Click to collapse
That's a good question. I've just been using stock and hadn't considered it. How would one check that?
Sent from my Nokia 6.1 Plus using Tapatalk
Bluebriz said:
That's a good question. I've just been using stock and hadn't considered it. How would one check that?
Sent from my Nokia 6.1 Plus using Tapatalk
Click to expand...
Click to collapse
It's easy. Get an OTA .zip file, Re-Boot to recovery and flash it. Or Use the ADB Sideload method.
Most likely installing the OTA would fail if the device is rooted because, Magisk will patch the boot.img.
Then I'll need to wait for another update, the September one, right? Because I installed it with ADB and have Magisk installed so I don't really want to mess with it until I have to.
Sent from my Nokia 6.1 Plus using Tapatalk
Bluebriz said:
Then I'll need to wait for another update, the September one, right? Because I installed it with ADB and have Magisk installed so I don't really want to mess with it until I have to.
Click to expand...
Click to collapse
I just took an OTA with Magisk installed it went fine. (September patch)
OK, then it doesn't seem to work. Trying to follow the steps, the system update gives an installation error. I'm guessing that somewhere along the road I've messed something up, so it seems stock rom and Magisk isn't an option for me.
Hymix said:
OK, then it doesn't seem to work. Trying to follow the steps, the system update gives an installation error. I'm guessing that somewhere along the road I've messed something up, so it seems stock rom and Magisk isn't an option for me.
Click to expand...
Click to collapse
Restore images before you do anything, If installation fails keep trying again. It happens to me to.
CarbonGTR said:
Restore images before you do anything, If installation fails keep trying again. It happens to me to.
Click to expand...
Click to collapse
Really? I did the restore via Magisk and that seemed fine, but then the update part didn't work. It downloaded then gave the error so I quit and started again with a fresh installation, minus Magisk.
Sent from my Nokia 6.1 Plus using Tapatalk
Have you guys modified the system/vendor partition in any way? If you did, Then it will obviously fail.
@Bluebriz and @Hymix I agree. It's the september security patch causing the installation issue.
It fails for me no matter what, Unless I completely un-root. But this method works perfectly fine on the August update.
Lets see for the October patch.
Okay, I can specifically narrow this down to way the September patch. The september patch requires the August security patch as a precondition to install. And that's where something funky is happening.
Guys a quick update. October update has been released but it also fails to install. This time I've managed to find the cause, Apparently some service that needs to be used for the update is being blocked/used by Magisk. (I could be wrong here)
The error code according to the recovery is 20(kDownloadStateInitializationError)
Is there any update to this issue?
Tried removing Magisk, didn't help.
Yesterday I got November security update ..iam using magisk...so it is showing installation problem...I tried in recovery and ADB method both didn't work.. finally I ended in bootloop ...so I again installed stock ROM...any solution is there without resetting each time how to install security updates..coz each time my data balance was wasted??
Sony's bootloader unlock page added the xperia 10 II to the list.
It's wrongly listed as "Xperia X10 II", so it's near the middle of the list, but gives the code with the IMEI
Edit:
Can't post link yet, the unlock page is: https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/
I've done it but i'm facing a problem with rooting could you help me with that ?
hq8aus said:
I've done it but i'm facing a problem with rooting could you help me with that ?
Click to expand...
Click to collapse
As long as BL is unlocked, you may be able to root your device using XperiFirm, UnSIN and Magisk.
- XperiFirm > Download fw
- UnSIN > Get the boot_XXXX.sin file from the downloaded fw folder, and drop it over unsin.exe (you'll get boot_XXXX.img file).
- Move the boot_XXXX.img file to the device's internal storage (or sdcard).
- Install Magisk Manager app
- Magisk Manager app > Install > Uncheck 'Keep AVB 2.0/dm-verity' > Next > Select and patch a file > Choose the boot_XXXX.img (you'll get /Download/magisk_patched.img)
- Flash magisk_patched.img with fastboot with command:
Code:
fastboot flash boot magisk_patched.img
- Reboot
If something goes wrong, you'll need to flash original stock boot img file (boot_XXXX.img) with fastboot (or even flash whole fw again).
Try it at your own risk.
serajr said:
As long as BL is unlocked, you may be able to root your device using XperiFirm, UnSIN and Magisk.
- XperiFirm > Download fw
- UnSIN > Get the boot_XXXX.sin file from the downloaded fw folder, and drop it over unsin.exe (you'll get boot_XXXX.img file).
- Move the boot_XXXX.img file to the device's internal storage (or sdcard).
- Install Magisk Manager app
- Magisk Manager app > Install > Uncheck 'Keep AVB 2.0/dm-verity' > Next > Select and patch a file > Choose the boot_XXXX.img (you'll get /Download/magisk_patched.img)
- Flash magisk_patched.img with fastboot with command:
Code:
fastboot flash boot magisk_patched.img
- Reboot
If something goes wrong, you'll need to flash original stock boot img file (boot_XXXX.img) with fastboot (or even flash whole fw again).
Try it at your own risk.
Click to expand...
Click to collapse
Thank you for the tutorial i will try it after few hour
I have one question : my phone refuse to enter recovery mode once the recovery mode boot the phone restart and start normally so i'm surprised do u know if this a common problem?
hq8aus said:
Thank you for the tutorial i will try it after few hour
I have one question : my phone refuse to enter recovery mode once the recovery mode boot the phone restart and start normally so i'm surprised do u know if this a common problem?
Click to expand...
Click to collapse
You're welcome. Xperia devices are not provided with a recovery, you need a custom one (by the way not yet available for this model).
serajr said:
You're welcome. Xperia devices are not provided with a recovery, you need a custom one (by the way not yet available for this model).
Click to expand...
Click to collapse
Thank you very much the method u wrote worked
now i'm free to install mods ? " i know it's stupid question but i'm beginner in rooting"
hq8aus said:
Thank you very much the method u wrote worked
now i'm free to install mods ? " i know it's stupid question but i'm beginner in rooting"
Click to expand...
Click to collapse
Glad to know that.
Sure you are! You can flash EdExposed and, for e.g., install my xposed modules ( Home Xposed for Q and Call Recording ).
Also any other hack you want to (my debloat script >> here << may also work).
Just a warning: due the lack of a recovery, if you face a bootloop after mess with something, you'll need to disable all the installed magisk modules to be able to boot up device, and to do so, you'll need to create a Core Mode Only magisk (google it) and fastboot it.
sorry to bother you .. but is there anyway to mount the "/system" to r/w ? because i'm having problem in moving file into it
hq8aus said:
sorry to bother you .. but is there anyway to mount the "/system" to r/w ? because i'm having problem in moving file into it
Click to expand...
Click to collapse
First of all ensure all your installed magisk modules are disabled (disable them all and reboot).
Magisk bind-mounts /system/* (specific modules folders) to do its initial mount logic, so changes into those system folders at runtime won't be allowed (if that specific system folder is used by a magisk module).
I don't know if this is your case, but I drop here this warning.
adb commands to mount system (rootfs)
rw:
Code:
mount -orw,remount /
ro:
Code:
mount -oro,remount /
You could try also to disable the vbmeta params by fastbooting vbmeta*_.img (vbmeta_*.sin > unsin.exe > vbmeta*_.img) with command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta*_.img
hi everyone,
after rooting with the boot.img patch method is there a good way to de-google the stock rom? i've seen twrp scripts for this but obviously those don't apply here, and i'm not exactly sure what is safe to remove and what is not, as a few days ago when i did this (via the /d/gapps app from f-droid) the system got stuck in a bootloop.
any ideas?
Ber7az said:
Sony's bootloader unlock page added the xperia 10 II to the list.
It's wrongly listed as "Xperia X10 II", so it's near the middle of the list, but gives the code with the IMEI
Edit:
Can't post link yet, the unlock page is: https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/
Click to expand...
Click to collapse
Hi, is it possible to relock the bootloader?
Supercharlie25 said:
Hi, is it possible to relock the bootloader?
Click to expand...
Click to collapse
You could try and confirm. Xperia 1 and Xperia 5 are lockable but is not the Xperia 10, maybe the Xperia 10 II could be lockable, try on your own risk
serajr said:
As long as BL is unlocked, you may be able to root your device using XperiFirm, UnSIN and Magisk.
- XperiFirm > Download fw
- UnSIN > Get the boot_XXXX.sin file from the downloaded fw folder, and drop it over unsin.exe (you'll get boot_XXXX.img file).
- Move the boot_XXXX.img file to the device's internal storage (or sdcard).
- Install Magisk Manager app
- Magisk Manager app > Install > Uncheck 'Keep AVB 2.0/dm-verity' > Next > Select and patch a file > Choose the boot_XXXX.img (you'll get /Download/magisk_patched.img)
- Flash magisk_patched.img with fastboot with command:
Code:
fastboot flash boot magisk_patched.img
- Reboot
If something goes wrong, you'll need to flash original stock boot img file (boot_XXXX.img) with fastboot (or even flash whole fw again).
Try it at your own risk.
Click to expand...
Click to collapse
Hi, is possible flash custom Rom without recovery? I saw that it is already available for download Pixel Experience for our device. Thanks for replay.
Thapsus-cz said:
Hi, is possible flash custom Rom without recovery? I saw that it is already available for download Pixel Experience for our device. Thanks for replay.
Click to expand...
Click to collapse
I have no idea (I've never played with custom roms - stock only).
Pay attention to the 2020/08/19 build, it has a recovery image file available (as per I could see).
serajr said:
I have no idea (I've never played with custom roms - stock only).
Pay attention to the 2020/08/19 build, it has a recovery image file available (as per I could see).
Click to expand...
Click to collapse
Thank you, I'd rather wait, maybe we'll see TWRP soon.
Has anyone installed LineageOS on this?
xdauserart said:
Has anyone installed LineageOS on this?
Click to expand...
Click to collapse
The only custom ROM for our device I found Pixel Experience here https://download.pixelexperience.org/xqau52 But unfortunately I failed to flash the their recovery and twrp is not yet.
Thapsus-cz said:
The only custom ROM for our device I found Pixel Experience here ... But unfortunately I failed to flash the their recovery and twrp is not yet.
Click to expand...
Click to collapse
That doesn't sound great. I'm looking for ways to de-google it, remove tracking apps, etc. Looks like now only way is to remove apps manually via `adb`. But I'm not sure what apps to remove.
Will installing AOSP for Android 11 with Sony image be without Google apps (like Google Play and other bloat)? Did anyone try installing this? Sony has added Xperia 10 II to Open devices program recently.
@xdauserart, @Thapsus-cz, Do you know if after Unlock BL of xperia 10 II, boots with the message "Your device can't be checked by corruption. Please lock the bootloader '? And if its available some method to backup TA before, for this model? Thanks......