Database Develop

[Tutorial] How To Root Nexus 5 Lollipop 5.0.1

Hi Everyone, I am Pushkar Dua just wanted to share a rooting guide for Nexus 5 Android 5.0.1
As many people Reported that Root has stopped working after the 5.0.1 Update or previous Binaries lead device to Boot Loop,
Please Download Latest Binaries That i am providing here: http://download.chainfire.eu/641/SuperSU/UPDATE-SuperSU-v2.40.zip
And flash it with TWRP recovery..
Please Use TWRP Version 2.8.1.0 as people reported some problems in latest 2.8.2.0 version.
Downlaload TWRP 2.8.1.0
Please note: if you're having a problem with twrp 2.8.1.0 asking for password..
Please use twrp 2.0.4.5
just reboot to system and you will have root access..
Watch the video for more info and Please Hit thanks or subscribe me on youtube to support me! every bit will be strongly appreciated!
Please Leave your questions BY QUOTING ME
Thanks
Thanks To @Chainfire for making this!
Original Thread for SuperSU : http://forum.xda-developers.com/showthread.php?t=1538053 Root Nexus 5 Lollipop 5.0.1

Hey!
Thanks a lot. Really helped solve my problem!

No problem

This doesn't belong in Development.

Actually i am not sure where should this be.. I'd request modders to please move it to the correct board!

Thanks man!

Delete

Since you've probably lost your custom recovery upgrading to 5.0.1, you can grab the TWRP images for Nexus 5 here: http://techerrata.com/browse/twrp2/hammerhead
I believe you need to use 2.8.1.0 since 2.8.2.0 either doesn't work or is causing problems for many users.

CF-Auto-root is still OK. I just tried

wondertx said:
CF-Auto-root is still OK. I just tried
Click to expand...
Click to collapse
Isn't CF-Auto root adding files from the 5.0 release over the 5.0.1 ? Isn't it safer to wait for a 5.0.1 autoroot?

wondertx said:
CF-Auto-root is still OK. I just tried
Click to expand...
Click to collapse
How did you update from a rooted (with CF-Auto Root) 5.0 to 5.0.1 you just received the OTA and installed it without any problems ?
I like to know because i am on 5.0 stock just rooted with CF_Auto root.

So no more need for CF-Auto?
Just flashing SuperSU zip with TWRP is enough?

I flashed a Custom Rom Using TWRP which doesn't have any root permission...

MrKaon said:
So no more need for CF-Auto?
Just flashing SuperSU zip with TWRP is enough?
Click to expand...
Click to collapse
Yes... Just Flashing with TWRP Is Enough!

Guys, i installed the 5.0.1 update by fastboot flashing system, boot and radio. I lost my custom recovery tho (CWR). I now tried to install TWRP, but after flashing the recovery image, the recovery still hasnt changed. Could i just flash CRW or should i use TWRP for this version?

Ubichinon said:
Guys, i installed the 5.0.1 update by fastboot flashing system, boot and radio. I lost my custom recovery tho (CWR). I now tried to install TWRP, but after flashing the recovery image, the recovery still hasnt changed. Could i just flash CRW or should i use TWRP for this version?
Click to expand...
Click to collapse
have you tried wugfresh's nexus toolkit to flash TWRP recovery???
maybe that works........ waiting for ur response... let me know..

pushkardua said:
have you tried wugfresh's nexus toolkit to flash TWRP recovery???
maybe that works........ waiting for ur response... let me know..
Click to expand...
Click to collapse
This. I flash with it here since 4.4.4 and it did everything just fine. Not only it is an app to automatically root, but it gives very good hints, and provides lots of others features like installing Apks, getting a adb prompt, and so much more. Greatest third party Android app I have tried. Highly recommended, didn't even had to wait they update it for 5.0.1, as soon I got the 5.0.1 OTA notification, Nexus Root Toolkit was already ready for it.

Ubichinon said:
Guys, i installed the 5.0.1 update by fastboot flashing system, boot and radio. I lost my custom recovery tho (CWR). I now tried to install TWRP, but after flashing the recovery image, the recovery still hasnt changed. Could i just flash CRW or should i use TWRP for this version?
Click to expand...
Click to collapse
This is lollipop security, custom recover wouldn't stick, after each reboot it will replaced with stock one, of course there is a way to make it sticky just search the forum.
Sent from my Nexus 5 using Tapatalk

MrKaon said:
So no more need for CF-Auto?
Just flashing SuperSU zip with TWRP is enough?
Click to expand...
Click to collapse
That's always been enough. You can use Cf's auto root if you don't want to use a custom recovery.

Molitro said:
That's always been enough. You can use Cf's auto root if you don't want to use a custom recovery.
Click to expand...
Click to collapse
I had similar discussion with Chainfire:
MrKaon said:
So guys for rooting lollipop on Nexus 5 stock all I need is flashing latest zip with TWRP?
No more need to flash modified kernel?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Chainfire said:
Initial root requires using CFAR. You can update using TWRP afterwards.
Click to expand...
Click to collapse
Click to expand...
Click to collapse

[Q] 5.1.1 OTA while rooted?

I've been receiving the prompt to update my N6 to 5.1.1 for the past few days, but whenever I attempt to install it, it says it's rebooting and does nothing. Is this because I'm rooted? Besides being rooted, there's no modifications to the system (well, except for Franco Kernel and MCR I suppose...). Is it even possible to update this way? Any help would be much appreciated. Thanks!

greycobalt said:
I've been receiving the prompt to update my N6 to 5.1.1 for the past few days, but whenever I attempt to install it, it says it's rebooting and does nothing. Is this because I'm rooted? Besides being rooted, there's no modifications to the system (well, except for Franco Kernel and MCR I suppose...). Is it even possible to update this way? Any help would be much appreciated. Thanks!
Click to expand...
Click to collapse
Hi, no modifications to system (including recovery) or boot can be present for OTA to flash. Look here:
http://forum.xda-developers.com/showthread.php?t=2992919

Evolution_Tech said:
Hi, no modifications to system (including recovery) or boot can be present for OTA to flash. Look here:
http://forum.xda-developers.com/showthread.php?t=2992919
Click to expand...
Click to collapse
Well that's a bummer! Thanks for the link. It looks like sideloading will still work, is that correct? If so, is it possible to sideload an update without wiping my data or factory resetting?

greycobalt said:
Well that's a bummer! Thanks for the link. It looks like sideloading will still work, is that correct? If so, is it possible to sideload an update without wiping my data or factory resetting?
Click to expand...
Click to collapse
If your bootloader is unlocked, just do this:
Download the factory image for the new build you want.
Extract twice to end up with the bootloader, radio, boot, system, recovery, userdata, and cache images.
Flash each image individually with fastboot except for userdata.
You will be updated and won't lose data. Then, just flash TWRP again and then from TWRP, flash the superSU zip. You will be stock rooted, with TWRP recovery. All your data will remain.
If you try to flash official OTA via sideload, it will still fail because of root and custom recovery.

greycobalt said:
I've been receiving the prompt to update my N6 to 5.1.1 for the past few days, but whenever I attempt to install it, it says it's rebooting and does nothing. Is this because I'm rooted? Besides being rooted, there's no modifications to the system (well, except for Franco Kernel and MCR I suppose...). Is it even possible to update this way? Any help would be much appreciated. Thanks!
Click to expand...
Click to collapse
Hi hi. Made me smile. Thanks for that.

Evolution_Tech said:
If your bootloader is unlocked, just do this:
Download the factory image for the new build you want.
Extract twice to end up with the bootloader, radio, boot, system, recovery, userdata, and cache images.
Flash each image individually with fastboot except for userdata.
You will be updated and won't lose data. Then, just flash TWRP again and then from TWRP, flash the superSU zip. You will be stock rooted, with TWRP recovery. All your data will remain.
If you try to flash official OTA via sideload, it will still fail because of root and custom recovery.
Click to expand...
Click to collapse
I will definitely do this! Thanks. They haven't posted the Verizon 5.1.1 to the image site yet, so I'll have to wait a bit I guess. :-/ Thanks!
Didgeridoohan said:
Hi hi. Made me smile. Thanks for that.
Click to expand...
Click to collapse

LMY48I update error

Hey.
My N6 got an error after I tried to update. I saw somewhere that installing the update on a rooted device (stock everything, just root) would be successful but it would remove root. Tried and got the error message with the android guy and a warning sign or something like that just with the "error" text, no more. I unrooted and rebooted, after some time the update prompted again and tried, same result.
I did some searches and just a few people have commented this issue, no answers yet.
Any ideas?

OscarBrito said:
Hey.
My N6 got an error after I tried to update. I saw somewhere that installing the update on a rooted device (stock everything, just root) would be successful but it would remove root. Tried and got the error message with the android guy and a warning sign or something like that just with the "error" text, no more. I unrooted and rebooted, after some time the update prompted again and tried, same result.
I did some searches and just a few people have commented this issue, no answers yet.
Any ideas?
Click to expand...
Click to collapse
Has to be completely stock. No root, custom kernel or recovery. How did you unroot. Have to flash factory image to remove root. Can't just remove the app. Forget OTAs if you are gonna root. Have to reflash factory image anyway so might as well just flash the updated image.

KingRoot
prdog1 said:
Has to be completely stock. No root, custom kernel or recovery. How did you unroot. Have to flash factory image to remove root. Can't just remove the app. Forget OTAs if you are gonna root. Have to reflash factory image anyway so might as well just flash the updated image.
Click to expand...
Click to collapse
I did with King Root, that thing works like a charm, Here's the thread. It has an option to remove root, the root manager disappeared, I rebooted and checked with a root checker and it says that I'm not rooted, still I get the error message when trying to update.

OscarBrito said:
I did with King Root, that thing works like a charm, Here's the thread. It has an option to remove root, the root manager disappeared, I rebooted and checked with a root checker and it says that I'm not rooted, still I get the error message when trying to update.
Click to expand...
Click to collapse
Your system is still modified. Even if remove the files the partition has been modified. If you have custom recovery or kernel it also won't flash. Have to flash back to stock so might as well just fastboot the updated factory image.

OscarBrito said:
I did with King Root, that thing works like a charm, Here's the thread. It has an option to remove root, the root manager disappeared, I rebooted and checked with a root checker and it says that I'm not rooted, still I get the error message when trying to update.
Click to expand...
Click to collapse
None of the unroot options put things back to 100% stock. They just remove root. The only way to remove all traces is to fastboot flash the system.img
If you're going to run rooted, forget about OTA and learn about fastboot.
General > sticky roll-up > adb and fastboot

Reset
prdog1 said:
Your system is still modified. Even if remove the files the partition has been modified. If you have custom recovery or kernel it also won't flash. Have to flash back to stock so might as well just fastboot the updated factory image.
Click to expand...
Click to collapse
Can I backup, do a factory data reset and then do the update? Then root again and restore my stuff.

OscarBrito said:
Can I backup, do a factory data reset and then do the update? Then root again and restore my stuff.
Click to expand...
Click to collapse
Nope. Have to flash stock image as posted above.

prdog1 said:
Nope. Have to flash stock image as posted above.
Click to expand...
Click to collapse
Dang. I don't like to mess with flashing and custom recoveries but I guess now I most.
I'm looking at Flashify. Download the stock image with the patch already on it and flash it that way. Do you recommend doing it that way?
Another thing, Any good and simple backup tool? I just want to skip the part where I need to configure everything again.

OscarBrito said:
Dang. I don't like to mess with flashing and custom recoveries but I guess now I most.
I'm looking at Flashify. Download the stock image with the patch already on it and flash it that way. Do you recommend doing it that way?
Another thing, Any good and simple backup tool? I just want to skip the part where I need to configure everything again.
Click to expand...
Click to collapse
You can't flash the stock image with flashify. Use fastboot as I have already advised.
Titanium backup is a great backup app, but you won't wipe the device if you only flash the system.img, boot.img and radio.img

danarama said:
You can't flash the stock image with flashify. Use fastboot as I have already advised.
Titanium backup is a great backup app, but you won't wipe the device if you only flash the system.img, boot.img and radio.img
Click to expand...
Click to collapse
Sorry for so many questions mate, but I run linux and for reasons I try to avoid getting into my W8 partition.

OscarBrito said:
Sorry for so many questions mate, but I run linux and for reasons I try to avoid getting into my W8 partition.
Click to expand...
Click to collapse
Fastboot works with Linux also.

OscarBrito said:
Sorry for so many questions mate, but I run linux and for reasons I try to avoid getting into my W8 partition.
Click to expand...
Click to collapse
No worries. Linux is even easier. You just stick the fastboot binaries in /usr/bin
Note, you'll probably need to use sudo / su to call fastboot.

danarama said:
No worries. Linux is even easier. You just stick the fastboot binaries in /usr/bin
Note, you'll probably need to use sudo / su to call fastboot.
Click to expand...
Click to collapse
If all this stuff is needed I better go all in and get AOSiP.
Gonna do it with Nexus Root Toolkit, get TWRP and flash the ROM.
I'm kinda new to this kind of stuff, I use ArchLinux and mess with my computer like there's no tomorrow but doing stuff with a phone can brick it. So, any last advice?
Thanks both in advance.

OscarBrito said:
If all this stuff is needed I better go all in and get AOSiP.
Gonna do it with Nexus Root Toolkit, get TWRP and flash the ROM.
I'm kinda new to this kind of stuff, I use ArchLinux and mess with my computer like there's no tomorrow but doing stuff with a phone can brick it. So, any last advice?
Thanks both in advance.
Click to expand...
Click to collapse
Better chance of bricking it with ToolKit than with manual fastboot. I run stock rooted with TWRP also. Takes 2-3 minutes to update with fastboot. If toolkit fails will most likely need fastboot to fix it anyway.

OscarBrito said:
If all this stuff is needed I better go all in and get AOSiP.
Gonna do it with Nexus Root Toolkit, get TWRP and flash the ROM.
I'm kinda new to this kind of stuff, I use ArchLinux and mess with my computer like there's no tomorrow but doing stuff with a phone can brick it. So, any last advice?
Thanks both in advance.
Click to expand...
Click to collapse
Don't use toolkits unless you can use fastboot..so just use fastboot. I'm not saying this for fun you know...if anything, its quite boring having to say this to everyone on a daily basis
Use fastboot please. Read my fastboot thread. You understand that fastboot is Googles method for flashing Google android on the google nexus? It should be pretty clear that this is the best tool for the job.

danarama said:
Don't use toolkits unless you can use fastboot..so just use fastboot. I'm not saying this for fun you know...if anything, its quite boring having to say this to everyone on a daily basis
Use fastboot please. Read my fastboot thread. You understand that fastboot is Googles method for flashing Google android on the google nexus? It should be pretty clear that this is the best tool for the job.
Click to expand...
Click to collapse
Don't get me wrong, I'm not afraid of a terminal, but well, you are right going with a terminal rather than a tool.
I'm finishing my backup and then doing all this manually, thanks a lot, both.

OscarBrito said:
Don't get me wrong, I'm not afraid of a terminal, but well, you are right going with a terminal rather than a tool.
I'm finishing my backup and then doing all this manually, thanks a lot, both.
Click to expand...
Click to collapse
I can't see how any Linux user would be afraid of terminals

Yeap, just tried to Flash my Super Awesome Nexus 5 with the LMY48I Update Zip file (10mb), via TWRP, while Rooted and I got the Nice Red Error... So I guess I have to download the Factory image LMY48I and via fastboot just flash the system.img if nothing else has been modified since LMY48B... In case I loose Root Access I might just reflash the script via TWRP... I will post update if anyone interested...

imor said:
Yeap, just tried to Flash my Super Awesome Nexus 5 with the LMY48I Update Zip file (10mb), via TWRP, while Rooted and I got the Nice Red Error... So I guess I have to download the Factory image LMY48I and via fastboot just flash the system.img if nothing else has been modified since LMY48B... In case I loose Root Access I might just reflash the script via TWRP... I will post update if anyone interested...
Click to expand...
Click to collapse
You will lose root. Flash supersu from recovery before first boot

Ok, just confirming here before I mess up. I have an international N6 rooted with stock recovery running LMY47Z. I can't update OTA. So I should flash the full stock image and then run cf-auto-root before rebooting.
Is this correct? Will I lose my user data when I do this? If so, what's the easiest way to backup and restore? Can't I flash the 25MB update .zip instead?
Thanks!

Can't seem to root 6.0.1

I'm having an issue rooting my Nexus 6. I rooted it easily enough a couple months ago with the NRT. I recently used the Flash stock + Unroot options to upgrade to 6.01. However, when I tried rooting it again I ran into problems. I plugged it up, selected the root option, it tested ADB connectivity, booted into TWRP and that's when I ran into an issue. It told me then that ADB device was not found. I rebooted my phone and though I can boot into it, I now get a "your phone is corrupt" message when I turn it on. I tried again and has the same issue.
I followed the instructions it gave me about checking my drivers and they're fine. Anyone have any idea what's going on and how I can get around it? Also help removing the "your phone is corrupt message"would be cool too, but it's not a priority since it seems harmless and I'm sure I could find it easily enough with a little Googling, the other problem I have not been able to find an answer to though.

Rentom said:
I'm having an issue rooting my Nexus 6. I rooted it easily enough a couple months ago with the NRT. I recently used the Flash stock + Unroot options to upgrade to 6.01. However, when I tried rooting it again I ran into problems. I plugged it up, selected the root option, it tested ADB connectivity, booted into TWRP and that's when I ran into an issue. It told me then that ADB device was not found. I rebooted my phone and though I can boot into it, I now get a "your phone is corrupt" message when I turn it on. I tried again and has the same issue.
I followed the instructions it gave me about checking my drivers and they're fine. Anyone have any idea what's going on and how I can get around it? Also help removing the "your phone is corrupt message"would be cool too, but it's not a priority since it seems harmless and I'm sure I could find it easily enough with a little Googling, the other problem I have not been able to find an answer to though.
Click to expand...
Click to collapse
flash any custom kernel to get rid of that message

simms22 said:
flash any custom kernel to get rid of that message
Click to expand...
Click to collapse
Don't really have any desire to use a custom kernel, but I'll keep it in mind. I just don't know why it popped up now when nothing happened, but when I actually rooted the device I never saw that message.

Rentom said:
Don't really have any desire to use a custom kernel, but I'll keep it in mind. I just don't know why it popped up now when nothing happened, but when I actually rooted the device I never saw that message.
Click to expand...
Click to collapse
because google put it there, it is new.

It was rooted with an older version of su. You probably said yes when twrp asked if you wanted to root it. Flash it back to stock, if you use nrt again select the no wipe option to save your data. And make sure your net is current. If you do it by hand skip the user partition.
When you root it male sure you use a newer su. 2.67 is the current version I believe.
Sent from my Nexus 6 using XDA Labs

TonikJDK said:
It was rooted with an older version of su. You probably said yes when twrp asked if you wanted to root it. Flash it back to stock, if you use nrt again select the no wipe option to save your data. And make sure your net is current. If you do it by hand skip the user partition.
When you root it male sure you use a newer su. 2.67 is the current version I believe.
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
Yeah I let twrp root it when it asked when I did it two months ago. Was that a bad thing? I thought I read that it was if you were rooting 6.0.1, but I was rooting 6.0 so I decided to see what would happen, and it went smoothly.

That is what is causing the corrupted message. It was an old version of su and it modified the system.
Sent from my Nexus 6 using XDA Labs

TonikJDK said:
That is what is causing the corrupted message. It was an old version of su and it modified the system.
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
I see. Makes sense. Alright, thanks. I already did flash it back to stock to update to 6.0.1, so I'm not sure why you told me to flash it back to stock and then install su 2.67.

I am also having this problem. Twrp will not let me flash a kernel or SuperSU. I went back to stock recovery and tried to root using cf auto root. But no luck. Phone runs fine, I upgraded to 6.01 with adb and did not flash user data. Any help would be greatly appreciated.

Mongo23ny said:
I am also having this problem. Twrp will not let me flash a kernel or SuperSU. I went back to stock recovery and tried to root using cf auto root. But no luck. Phone runs fine, I upgraded to 6.01 with adb and did not flash user data. Any help would be greatly appreciated.
Click to expand...
Click to collapse
flash twrp again, pick the kernel and SuperSU, then flash in twrp. if you can't pick them, make sure that twrp is mounted. and you DID NOT use adb to boot 6.0.1, you used fastboot, that is different than adb.

simms22 said:
flash twrp again, pick the kernel and SuperSU, then flash in twrp. if you can't pick them, make sure that twrp is mounted. and you DID NOT use adb to boot 6.0.1, you used fastboot, that is different than adb.
Click to expand...
Click to collapse
I can pick them both, when I swipe to flash it just goes back to the teamwin start up screen. Tried many, many times.

Mongo23ny said:
I can pick them both, when I swipe to flash it just goes back to the teamwin start up screen. Tried many, many times.
Click to expand...
Click to collapse
OK, try flashing twrp again, maybe it just errored. flash twrp version 3.0

simms22 said:
OK, try flashing twrp again, maybe it just errored. flash twrp version 3.0
Click to expand...
Click to collapse
Tried flashing twrp a couple of times, went back to stock recovery and then twrp. No luck. Also, phone will not boot with custom recovery only with stock. Not sure if I tried 3.0.0.0

simms22 said:
OK, try flashing twrp again, maybe it just errored. flash twrp version 3.0
Click to expand...
Click to collapse
Do I keep system read only in twrp 3.0?

Mongo23ny said:
Do I keep system read only in twrp 3.0?
Click to expand...
Click to collapse
no, do not keep system read only, ever.

simms22 said:
no, do not keep system read only, ever.
Click to expand...
Click to collapse
Thanks for all your help, did a clean install, fastboot flashed 6.01. I had gotten that corrupt phone message when I rebooted again but I took some security update and that got rid of the message. I flashed twrp 3.0.0.0 and SuperSU 2.67 and got root back. No worries, thx again.

Mongo23ny said:
Do I keep system read only in twrp 3.0?
Click to expand...
Click to collapse
simms22 said:
no, do not keep system read only, ever.
Click to expand...
Click to collapse
If you are using the systemless root method then yes, you do want to keep system read only.

alryder said:
If you are using the systemless root method then yes, you do want to keep system read only.
Click to expand...
Click to collapse
I kept it in read only, installed SuperSU 2.67 in twrp.

How To Update OTA with Root And System Modified

Hey, i've my mi A2 in August Patch (v9.6.10.0 ODIMIFE)
And
1. Bootloader Unlocked
2.Rooted
3.HAL3 Enabled
4.System Modified
What shoud i do to update to the latest(September) security patch.
I'm having serious wifi issue so that i'm desperate to update the latest OTA

Uinstall magisk, install ota use patched boot with magisk, ez.

T4Ump said:
Uinstall magisk, install ota use patched boot with magisk, ez.
Click to expand...
Click to collapse
This won't help him as he also modified the system partition
---------- Post added at 03:47 PM ---------- Previous post was at 03:46 PM ----------
rafihasan710 said:
Hey, i've my mi A2 in August Patch (v9.6.10.0 ODIMIFE)
And
1. Bootloader Unlocked
2.Rooted
3.HAL3 Enabled
4.System Modified
What shoud i do to update to the latest(September) security patch.
I'm having serious wifi issue so that i'm desperate to update the latest OTA
Click to expand...
Click to collapse
Next to putting stock boot you need to flash system partition again. Backup your data first just to be sure you have it before you might need to flash the complete August image

Benjamin_L said:
This won't help him as he also modified the system partition
---------- Post added at 03:47 PM ---------- Previous post was at 03:46 PM ----------
Next to putting stock boot you need to flash system partition again. Backup your data first just to be sure you have it before you might need to flash the complete August image
Click to expand...
Click to collapse
Im idiot, i was wrong Yea, put stock boot and install ota then patched boot

T4Ump said:
Im idiot, i was wrong Yea, put stock boot and install ota then patched boot
Click to expand...
Click to collapse
This won't be enough if he mounted or modified system partition as he said. Ota will still fail even with stock boot.

Benjamin_L said:
This won't be enough if he mounted or modified system partition as he said. Ota will still fail even with stock boot.
Click to expand...
Click to collapse
I disabled all magisk plugins, camera api, ios emoji, etc ****s after this i flash stock boot and install ota works.

T4Ump said:
I disabled all magisk plugins, camera api, ios emoji, etc ****s after this i flash stock boot and install ota works.
Click to expand...
Click to collapse
Depends on what you do. I used AdBlock and restoring stock boot was not enough for me that time

If you modified anything directly in system then your only option is to download the full rom and flash it with fastboot
http://bigota.d.miui.com/V9.6.13.0....0.ODIMIFE_20180913.0000.00_8.1_fbd1120565.tgz
Backup your data first and be careful, it will will wipe your data by default

I updated the toolkit to force update using fastboot. just run the unbrick option. Make sure to make a backup first, just in case
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585
Edit: Also, if you have any bugs please let me know, I can fix it today.

Nebrassy said:
If you modified anything directly in system then your only option is to download the full rom and flash it with fastboot
http://bigota.d.miui.com/V9.6.13.0....0.ODIMIFE_20180913.0000.00_8.1_fbd1120565.tgz
Backup your data first and be careful, it will will wipe your data by default
Click to expand...
Click to collapse
Is there any way i can do this without wiping my data?

rafihasan710 said:
Is there any way i can do this without wiping my data?
Click to expand...
Click to collapse
I guess you can, choose clean all, and flash_all_except_data.bat in the corner in miflash, careful not to choose lock
but you should take a backup anyway, you never know

Nebrassy said:
I guess you can, choose clean all, and flash_all_except_data.bat in the corner in miflash, careful not to choose lock
but you should take a backup anyway, you never know
Click to expand...
Click to collapse
Can You Please Explain the whole procedure step by step....
Sorry...i'm a noob

rafihasan710 said:
Can You Please Explain the whole procedure step by step....
Sorry...i'm a noob
Click to expand...
Click to collapse
http://en.miui.com/a-232.html

rafihasan710 said:
Is there any way i can do this without wiping my data?
Click to expand...
Click to collapse
You do not need to flash all. Yesterday I have updated my unlocked and rooted phone with changed system partition without any trouble, and all my apps and data are still with me. Just flash stock system and boot images via fastboot, then make OTA update. Then copy new stock boot.img to your phone, open Magisk Manager, click Install, patch boot.img, copy patched_boot.img back to PC and flash it via fastboot. That is all. For me the most difficult part was to wait for downloading 3 Gb of data from terribly slow miui.com.

drauger said:
You do not need to flash all. Yesterday I have updated my unlocked and rooted phone with changed system partition without any trouble, and all my apps and data are still with me. Just flash stock system and boot images via fastboot, then make OTA update. Then copy new stock boot.img to your phone, open Magisk Manager, click Install, patch boot.img, copy patched_boot.img back to PC and flash it via fastboot. That is all. For me the most difficult part was to wait for downloading 3 Gb of data from terribly slow miui.com.
Click to expand...
Click to collapse
Can You Provide me the necessary file links.
By the way, Thank You Very Much.

drauger said:
You do not need to flash all. Yesterday I have updated my unlocked and rooted phone with changed system partition without any trouble, and all my apps and data are still with me. Just flash stock system and boot images via fastboot, then make OTA update. Then copy new stock boot.img to your phone, open Magisk Manager, click Install, patch boot.img, copy patched_boot.img back to PC and flash it via fastboot. That is all. For me the most difficult part was to wait for downloading 3 Gb of data from terribly slow miui.com.
Click to expand...
Click to collapse
And please provide the fastboot commands for flashing all of those.

rafihasan710 said:
And please provide the fastboot commands for flashing all of those.
Click to expand...
Click to collapse
Did you do some research by yourself or are you expecting others to do the work for you? It's really not that hard..

Benjamin_L said:
Did you do some research by yourself or are you expecting others to do the work for you? It's really not that hard..
Click to expand...
Click to collapse
I'm sorry for that.
But as you've done this before so i just want to follow your proceedure strictly.
I don't want my phone to be bricked.
If you can help please do...

rafihasan710 said:
I'm sorry for that.
But as you've done this before so i just want to follow your proceedure strictly.
I don't want my phone to be bricked.
If you can help please do...
Click to expand...
Click to collapse
I understand your fear but try looking for commands and procedures yourself in the first place and then ask if this is right. Will help you more than just copy pasting stuff, you don't understand. This way you will become knowledgeable yourself but it takes time of course. Don't fear!

Benjamin_L said:
I understand your fear but try looking for commands and procedures yourself in the first place and then ask if this is right. Will help you more than just copy pasting stuff, you don't understand. This way you will become knowledgeable yourself but it takes time of course. Don't fear!
Click to expand...
Click to collapse
Thank You