How To Update OTA with Root And System Modified - Xiaomi Mi A2 / 6X Questions & Answers

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

Related

[Q] Error while installing 5.0.1 update

Hi I just got the 5.0.1 update, I downloaded it and the phone rebooted itself, I got the installation screen and after 5 seconds I just got the word "error" and I had to restart it manually; the device is rooted, have anyone else had this problem? I would appreciate your help
saman0suke1 said:
Hi I just got the 5.0.1 update, I downloaded it and the phone rebooted itself, I got the installation screen and after 5 seconds I just got the word "error" and I had to restart it manually; the device is rooted, have anyone else had this problem? I would appreciate your help
Click to expand...
Click to collapse
With lollipop you can't take an OTA if you are rooted or running just about anything else modified (custom kernels, like ones that have force decrypt disabled also will cause it to error out).
You can still flash it manually by flashing the images. If you don't want to wipe, don't flash the userdata.img . Also, if you aren't currently encrypted, booting up with the stock kernel will force encrypt your device, so don't flash that if you want to stay that way. You can then re-root. There are more in depth instructions for doing this out there if you search around for them.
My Nexus 6 took 5.0.1 just fine, but my Nexus 7 does this same thing, running stock ROM/Bootloader/Recovery/etc. The ONLY thing done to it is the Fastboot OEM unlock, but I doubt that alone would stop it. I'm curious to know what resolves this ( other than downloading the factory image and flashing it without wiping the userdata )
Just got same error. I didnt even root phone, bought it today, it installed apps from backup of my previous Nexus 4 and OTA is failing.
cupfulloflol said:
With lollipop you can't take an OTA if you are rooted or running just about anything else modified (custom kernels, like ones that have force decrypt disabled also will cause it to error out).
You can still flash it manually by flashing the images. If you don't want to wipe, don't flash the userdata.img . Also, if you aren't currently encrypted, booting up with the stock kernel will force encrypt your device, so don't flash that if you want to stay that way. You can then re-root. There are more in depth instructions for doing this out there if you search around for them.
Click to expand...
Click to collapse
So basically the only way is to flash the image manually? If I choose not to flash userdata.img my phone data (photos, contacts, apps, etc) won't be erased right? But I will lose root correct? Thanks!
saman0suke1 said:
So basically the only way is to flash the image manually? If I choose not to flash userdata.img my phone data (photos, contacts, apps, etc) won't be erased right? But I will lose root correct? Thanks!
Click to expand...
Click to collapse
Correct, with Lollipop if you modify things you basically are then forced to manually take the updates. Not that big of a deal as you would likely be needing a PC to reinstall your custom recovery or re-root anyhow after the update.
Flashing userdata.img isn't necessary to update. Neither is recovery.img if you want to keep a custom recovery.
Also as I mentioned before, if you have disabled encryption on your device, if you flash the stock kernel (boot.img) and boot up with it you will re-enable forced encryption. You will need to flash a kernel with force encryption disabled if you want to keep running without encryption. If you haven't disabled encryption, or don't care if your device re-encrypts (this doesn't erase anything, just may take a few minutes on first boot) then this doesn't matter.
cupfulloflol said:
Correct, with Lollipop if you modify things you basically are then forced to manually take the updates. Not that big of a deal as you would likely be needing a PC to reinstall your custom recovery or re-root anyhow after the update.
Flashing userdata.img isn't necessary to update. Neither is recovery.img if you want to keep a custom recovery.
Also as I mentioned before, if you have disabled encryption on your device, if you flash the stock kernel (boot.img) and boot up with it you will re-enable forced encryption. You will need to flash a kernel with force encryption disabled if you want to keep running without encryption. If you haven't disabled encryption, or don't care if your device re-encrypts (this doesn't erase anything, just may take a few minutes on first boot) then this doesn't matter.
Click to expand...
Click to collapse
Can I manually update without removing root first? Am I going to receive an error if I don't remove it? based on what you said, I will remove userdata.img and recovery.img and that will not wipe my data right? Do I have to decompress those files or the flash-all.bat will take care of that? Thanks!
saman0suke1 said:
Can I manually update without removing root first? Am I going to receive an error if I don't remove it? based on what you said, I will remove userdata.img and recovery.img and that will not wipe my data right? Do I have to decompress those files or the flash-all.bat will take care of that? Thanks!
Click to expand...
Click to collapse
I'm interested as well. Mine is rooted and I have encryption disabled, and I have TWRP on my phone. I tried to sideload the OTA update, but I can't get my phone to start sideload. I even flashed the stock recovery to get it to go, and no dice. What do I do next?
Anyone? I would appreciate the feedback, thanks!
sideload refers to adb as I understand it. thats NOT how you flash....you use fastboot to flash so you can do it all by hand or use one of the toolkits that script it for you.
cmh714 said:
sideload refers to adb as I understand it. thats NOT how you flash....you use fastboot to flash so you can do it all by hand or use one of the toolkits that script it for you.
Click to expand...
Click to collapse
Thanks, I get that, however I wanted to know if I need to remove the root before installing the update and if I need to decompress the .zip with the .img files or the batch will do that? thanks!
saman0suke1 said:
Thanks, I get that, however I wanted to know if I need to remove the root before installing the update and if I need to decompress the .zip with the .img files or the batch will do that? thanks!
Click to expand...
Click to collapse
If your doing from the PC you need to extract the zip file from within the image and then fastboot them. As for root, when you do it from fastboot I dont believe it matters as you will lose root anyway and need to re-root via flashing SuperSU.zip
Worked great! Thanks! Android 5.0.1 and root, no data deleted
Is it normal to not have received an update beyond 5.0? I have had a Nexus 6 since day one, no rooting of any kind and I have not received 5.0.1.
I have done the sideload method, but I really don't want to bother with it. I do however want some of these terrible bugs I am experiencing squashed. This phone is giving me lots of issues lately.
Thanks!
Can you receive and install OTA updates with an unlocked bootloader? Everything else is stock, no disabled encryption or anything just unlocked bootloader.
naulsballs said:
Can you receive and install OTA updates with an unlocked bootloader? Everything else is stock, no disabled encryption or anything just unlocked bootloader.
Click to expand...
Click to collapse
Yes
Sent from my Nexus 6 using XDA Free mobile app
saman0suke1 said:
Worked great! Thanks! Android 5.0.1 and root, no data deleted
Click to expand...
Click to collapse
Can you provide steps for this. I am in the same situation. I have the 5.0.1 image downloaded, just wondering what files and what order to flash. Thanks
TOCS88 said:
Is it normal to not have received an update beyond 5.0? I have had a Nexus 6 since day one, no rooting of any kind and I have not received 5.0.1.
I have done the sideload method, but I really don't want to bother with it. I do however want some of these terrible bugs I am experiencing squashed. This phone is giving me lots of issues lately.
Thanks!
Click to expand...
Click to collapse
Try pulling your Sim card out and rebooting.
scotbotmosh said:
Can you provide steps for this. I am in the same situation. I have the 5.0.1 image downloaded, just wondering what files and what order to flash. Thanks
Click to expand...
Click to collapse
If you're planning to stay rooted (meaning no OTA in future) system.img, boot.img and radio.img in any order.
scotbotmosh said:
Can you provide steps for this. I am in the same situation. I have the 5.0.1 image downloaded, just wondering what files and what order to flash. Thanks
Click to expand...
Click to collapse
If you use fastboot, just run these commands in terminal (I used windows, so in order to flash using fastboot, put the image that you downloaded for the update in the same folder where you have fastboot and open a terminal there) you can rename the .img files to whatever you like and replace those name in the commands below:
fastboot flash bootloader <bootloader file name here>.img
fastboot flash radio <radio file name here>.img
Then reboot it:
fastboot reboot-bootloader
Then flash these:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
And that's it. These commands are run while the phone is connected to the PC, you have to turn it on by pressing volume up + volume down + power.
Good luck.

Updating to 5.1 without losing root nor system settings

Is there a way to sideload the 5.1 update (downloaded from the google images page) without losing the CF root AND not losing any of my system settings and configurations?
Thanks in advance.
LordGrahf said:
Is there a way to sideload the 5.1 update (downloaded from the google images page) without losing the CF root AND not losing any of my system settings and configurations?
Thanks in advance.
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
Edit after rereading this http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 I would prob also do the reboot step after radio flash.
Maybe what your lookin for. If rooting is lost simply redo the cf root process and flash your custom recovery via fastboot. Most importantly this route will prevent data loss. I am going this route but will still backup because its safer and more responsible.
Without a modified img, and using the google provided stuff, you can't keep root. Just re-root, it's not hard.
Thanks guys. Few questions:
1. Do I need to unroot before sideloading the update?
2. Would I loose my currently installed and configured apps?
3. If I'm not losing my installed apps, what would happen to my root-required apps? For example I HAVE LMT pie control installed and configured. Would reinstalling root make it work as before without the need to reinstall and reconfigure LMT?
4. I'm still using stock recovery, would that affect what I'm trying to do in any way?
5. What is the minimal set of the update's images can I use to get this update? Like I think I should probably skip the user.img if I don't want my user settings to be wiped out, correct? What other images should I skip in order to not wipe out apps, apps settings, and system settings.
Thank you very much
LordGrahf said:
Thanks guys. Few questions:
1. Do I need to unroot before sideloading the update?
2. Would I loose my currently installed and configured apps?
3. If I'm not losing my installed apps, what would happen to my root-required apps? For example I HAVE LMT pie control installed and configured. Would reinstalling root make it work as before without the need to reinstall and reconfigure LMT?
4. I'm still using stock recovery, would that affect what I'm trying to do in any way?
5. What is the minimal set of the update's images can I use to get this update? Like I think I should probably skip the user.img if I don't want my user settings to be wiped out, correct? What other images should I skip in order to not wipe out apps, apps settings, and system settings.
Thank you very much
Click to expand...
Click to collapse
If doing the fastboot way like I linked (I have not read through the procedure for sideload, so I don't know)
1) no
2) no if you only flash some of the IMG files. For your purpose it seems (I'm also assuming you don't have custom kernel) these are the ones to not lose data. Make sure you follow the links in how to flash this correctly with the appropriate order and spots where to fastboot reboot.
Bootloader image
Radio image
Boot image (kernel)
Cache image
System image
Recovery image
Then reroot with the cf zip like before then reinstall the su app.
4) no we flash the new stock recovery too
5) minimal, to not overwrite the user data, above. Yup we skip the user data image
LordGrahf said:
Thanks guys. Few questions:
1. Do I need to unroot before sideloading the update?
2. Would I loose my currently installed and configured apps?
Click to expand...
Click to collapse
No.
LordGrahf said:
3. If I'm not losing my installed apps, what would happen to my root-required apps?
Click to expand...
Click to collapse
You'll have to install su since it was deleted by system.img but that's all. Note that last time I looked CF-Auto still said it was 5.0.1 but ...
LordGrahf said:
4. I'm still using stock recovery, would that affect what I'm trying to do in any way?
Click to expand...
Click to collapse
If you install a current TWRP it will install super-su for you when you request a reboot.
LordGrahf said:
5. What is the minimal set of the update's images can I use to get this update?
Click to expand...
Click to collapse
Everything except user.img. You can read or run flash-base to get the Google suggested initial ordering.
MunkinDrunky said:
http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
Edit after rereading this http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 I would prob also do the reboot step after radio flash.
Maybe what your lookin for. If rooting is lost simply redo the cf root process and flash your custom recovery via fastboot. Most importantly this route will prevent data loss. I am going this route but will still backup because its safer and more responsible.
Click to expand...
Click to collapse
I flashed the bootloader, but the command to flash the radio (fastboot flash radio radio-shamu-d4.0-9625-02.95.img) failed
Any idea?
Nikos2k said:
I flashed the bootloader, but the command to flash the radio (fastboot flash radio radio-shamu-d4.0-9625-02.95.img) failed
Any idea?
Click to expand...
Click to collapse
I don't really know. I usually just follow instructions. Did you fastboot reboot after flashing bootloader?
MunkinDrunky said:
I don't really know. I usually just follow instructions. Did you fastboot reboot after flashing bootloader?
Click to expand...
Click to collapse
Yes, I rebooted the boot loader (and it indeed showed the new boot loader version after the reboot)
After the fail message of the radio flash command, I rebooted to the system, it works, and from the baseband number in settings/about, it seems that the new radio has been flashed (besides the fail message)
Nikos2k said:
Yes, I rebooted the boot loader (and it indeed showed the new boot loader version after the reboot)
After the fail message of the radio flash command, I rebooted to the system, it works, and from the baseband number in settings/about, it seems that the new radio has been flashed (besides the fail message)
Click to expand...
Click to collapse
hmm yeah i really dont know why that happend. I guess as long as the new radio shows up as you say then it worked. I will actually be doing this shortly, since i am now at a computer
Just updated to 5.1
for those who will read later and more importantly in my same position.
I was on 5.0.1 BL unlocked, custom recovery+root, custom kernel- -wanting to go to->>5.1, root+custom recovery (cause flashing kernels is trivial) without any data loss (basically don't flash the userdata image) (also you could have left out the radio, I guess if you don't want newest radio, and the boot if you want to just keep your kernel--**not 100% about these two though)
I flashed via fastboot the: bootloader (then fastboot reboot-bootloader), the radio (then fastboot reboot-bootloader), then the boot (updated stock kernel), cache, system. Done, exit command prompt, then while in fastboot menu go into TWRP, whereby I choose system reboot and TWRP RE-ROOTS for me! Now I just kernel shop again
Thanks a lot gents. I followed the directions and upgraded/rerouted and none of my apps/settings got wiped. Yay!!
Can someone verify I'm on the latest versions for all components from my screenshot?
Thanks!
I also updated my Nexus 6 with 5.0.1, unlock and root, to 5.1 without losing data. I just had to re-root it afterwards.
I used Wugfresh Nexus root toolkit.
In short I used "Flash stock + unroot", in which I selected "Enable no-wipe" and "force-flash".
After this I rerooted the device from within NRT.
Worked like a charm!
---------- Post added at 03:23 PM ---------- Previous post was at 03:13 PM ----------
LordGrahf said:
Thanks a lot gents. I followed the directions and upgraded/rerouted and none of my apps/settings got wiped. Yay!!
Can someone verify I'm on the latest versions for all components from my screenshot?
Thanks!
Click to expand...
Click to collapse
That's all the latest versions yes...

[Q] Can't flash stock firmware!

I rooted my Nexus 6 a while ago, bootloader is also unlocked (obviously) and I flashed a custom recovery, the rest remained stock. Now I got the update for 5.1.1 ota but it wouldn't let me install it, not even with the stock recovery (which I flashed later again) because it said something like it expected something different in some system-file. So I backed everything up and tried flashing the whole firmware from the google servers using the flash-all.bat. It flases the bootloader and also the radio, but then it says:
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778975696 bytes
error: update package missing system.img
Press any key to exit...
Click to expand...
Click to collapse
I understand that I can flash everything manually and it also works, but what if I get another ota update someday? I won't be able to install it ota, will I? I'll need to flash it manually again then, right? Is there any other way to kinda 'force-flash' the stock firmware?
Thanks in advance for yout help!
Cheetah1024
Cheetah1024 said:
I rooted my Nexus 6 a while ago, bootloader is also unlocked (obviously) and I flashed a custom recovery, the rest remained stock. Now I got the update for 5.1.1 ota but it wouldn't let me install it, not even with the stock recovery (which I flashed later again) because it said something like it expected something different in some system-file. So I backed everything up and tried flashing the whole firmware from the google servers using the flash-all.bat. It flases the bootloader and also the radio, but then it says:
I understand that I can flash everything manually and it also works, but what if I get another ota update someday? I won't be able to install it ota, will I? I'll need to flash it manually again then, right? Is there any other way to kinda 'force-flash' the stock firmware?
Thanks in advance for yout help!
Cheetah1024
Click to expand...
Click to collapse
Flash-all doesn't work. All you need to do is flash the system image and boot image if you've unencrypted or switched kernels. You won't lose your data this way.
Evolution_Tech said:
Flash-all doesn't work. All you need to do is flash the system image and boot image if you've unencrypted or switched kernels. You won't lose your data this way.
Click to expand...
Click to collapse
Oh, so it's normal that flash-all doesn't work?
Cheetah1024 said:
Oh, so it's normal that flash-all doesn't work?
Click to expand...
Click to collapse
Yes.
Evolution_Tech said:
Yes.
Click to expand...
Click to collapse
Alright, that' good news ... at least somehow xD
So if i flash every single image via fastboot it would be stock and I would be able to install ota's again?
Cheetah1024 said:
Alright, that' good news ... at least somehow xD
So if i flash every single image via fastboot it would be stock and I would be able to install ota's again?
Click to expand...
Click to collapse
Yes, but why? Just flash the system and boot images of the latest version also if an updated bootloader and radio, flash those too. No need for OTA's on a Nexus.
Evolution_Tech said:
Yes, but why? Just flash the system and boot images of the latest version also if an updated bootloader and radio, flash those too. No need for OTA's on a Nexus.
Click to expand...
Click to collapse
You're right... So personal stuff and app data will only be deleted, if I wipe it or if I flas userdata.img, right?
Cheetah1024 said:
You're right... So personal stuff and app data will only be deleted, if I wipe it or if I flas userdata.img, right?
Click to expand...
Click to collapse
Yes.
Evolution_Tech said:
Yes.
Click to expand...
Click to collapse
Alright, you helped me big time mate! Thank You! :laugh:

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!

Question Lost root with latest OTA...

Phone updated from 13.0.2.0 to 13.0.4.0 accidentally or by itself, not sure, received the latest OTA and after reboot root is gone...
How can i get root back without loosing data or formatting?
You need to reinstall it using adb method, remember: everytime you update you loose the root
xNAPx said:
You need to reinstall it using adb method, remember: everytime you update you loose the root
Click to expand...
Click to collapse
Will i use data/settings if i reinstall magisk via adb?
You mean lose? Nope you won't as you are not formatting anything
xNAPx said:
You mean lose? Nope you won't as you are not formatting anything
Click to expand...
Click to collapse
Sorry, i meant loose data... And last question, which adb method should i use? I don't have twrp installed either as it wasn't available while i was rooting 13.0.2.0... Not sure if it's available now...?
GODSPD said:
Sorry, i meant loose data... And last question, which adb method should i use? I don't have twrp installed either as it wasn't available while i was rooting 13.0.2.0... Not sure if it's available now...?
Click to expand...
Click to collapse
Adb method doesn't need twrp, it is a bit more difficult to inject the root but you don't need to go through twrp. Just search on Google you will find several guides, I can tell you that you need the boot.img of the installed ROM in order to complete the process. You usually find this file into the fastboot ROM zip package
xNAPx said:
Adb method doesn't need twrp, it is a bit more difficult to inject the root but you don't need to go through twrp. Just search on Google you will find several guides, I can tell you that you need the boot.img of the installed ROM in order to complete the process. You usually find this file into the fastboot ROM zip package
Click to expand...
Click to collapse
So I'm guessing it's the same process as last time, the required boot.img will need to be from the updated 13.0.4.0 version? I barely remember how i did it initially, if you have any guides that work id really appreciate it
For the version 13.0.2.0 I used tge boot.img of the same fastboot ROM, I don't know if it would work with another boot.img honestly
I cannot seem to find the boot.img for the latest ota...
xNAPx said:
For the version 13.0.2.0 I used tge boot.img of the same fastboot ROM, I don't know if it would work with another boot.img honestly
Click to expand...
Click to collapse
cannot find a boot.img for 13.0.4, cannot extract it from payload.bin either via python, nothing seems to be working
xNAPx said:
For the version 13.0.2.0 I used tge boot.img of the same fastboot ROM, I don't know if it would work with another boot.img honestly
Click to expand...
Click to collapse
I tried it and boot looped to the bootloader...try at your own risk
tensux said:
I tried it and boot looped to the bootloader...try at your own risk
Click to expand...
Click to collapse
Did you manage to get it done? Apparently you can extract the 13.0.4 boot.img from the roms payload.bin file but i couldn't get it done myself... Did you manage to root yours?
GODSPD said:
Did you manage to get it done? Apparently you can extract the 13.0.4 boot.img from the roms payload.bin file but i couldn't get it done myself... Did you manage to root yours?
Click to expand...
Click to collapse
no in fact I had to switch to xiaomi.eu. i couldnt get anything else to flash. it kept failing at the same spot, i dont quite remember but had the name "super" in it
Just wait for the fastboot ROM guys
xNAPx said:
Just wait for the fastboot ROM guys
Click to expand...
Click to collapse
if we only knew when and where that will be released
Usually a week or two after the recovery release

Categories

Resources