“Decryption Unsuccessful” message - Xiaomi Mi A1 Questions & Answers

I attempted to apply the Oreo OTA using the guide here however it ended in a bootloop. I used fastboot to boot into TWRP (I don’t have it flashed) and switched to slot A and booted into it, where I got a message saying that decryption was unsuccessful (example). I used this to perform a reset, which worked so I guess this is a way to recover from a failed OTA, but does this reset both partitions and will I now be able to successfully apply the Oreo OTA? I have no interest in getting root back...
Thank you!

jglass071 said:
I attempted to apply the Oreo OTA using the guide here however it ended in a bootloop. I used fastboot to boot into TWRP (I don’t have it flashed) and switched to slot A and booted into it, where I got a message saying that decryption was unsuccessful (example). I used this to perform a reset, which worked so I guess this is a way to recover from a failed OTA, but does this reset both partitions and will I now be able to successfully apply the Oreo OTA? I have no interest in getting root back...
Thank you!
Click to expand...
Click to collapse
Same here. I am trying to solve this issue.

Mahbub Supriyo said:
Same here. I am trying to solve this issue.
Click to expand...
Click to collapse
After I got this message I reset the phone using the prompt on the "decryption unsuccessful" screen, then later I could apply Oreo OTA when it arrived. It seems to reset everything.

Related

[Q] Kitkat 4.4 OTA Update failed to install

Hello, I'm in a bit of a confusing situation so I hope that someone can shed light on it.
Last night I got a notification that my phone is ready to install the 4.4 update. I didn't have the time or the battery to install it then, so I just left my phone until today. Today, I happily pressed the update button, my phone restarted, it started to update and when the bar was a little more then a third full it stopped and said "Error!" (Thanks for a very informative error message Google! ) I restarted my phone, and now my phone reports that it's up to date?! I tried tapping the Check now, but it keeps saying it's up to date. I checked my cache folder, and there is a .zip file containing the update.
My phone is rooted, I used the Nexus 4 Rootkit, but I DIDN'T install a custom recovery or try to install any custom ROMs. (I'm happy with the stock one) I only installed SuperSU so I can grant root access to some apps and that's it. I didn't install any tweaks.
Now if I'm not mistaken, the OTA update should have worked on my phone, because everything is stock. So why did this happen and why I'm not receiving the update prompt again?
Also as a side note: When I went into the fastboot mode and tried to launch the Recovery mode, it said "No command!" and I had restart my phone.
No, you're wrong. You should've gone to SuperSU app and pressed the "full unroot" button before trying to OTAupdate. This would've replaced the modified bin files for root by the original files, allowing the OTA to be applied successfully.
This happens because the rooting process modifies some system files, so the OTA detects a non-stock scenario and aborts its installation. Also when the OTA fails, a flag marks this update as a "fail update" so your system will continue to show you that it's "updated" as he thinks the only update available isn't suitable for you. He is just waiting for the next OTA update.
Now you have to install the OTA via sideload / adb. I would recommend to make a full nandroid backup before everything else. Then fully unroot your phone and apply the OTA using adb.
This is exactly what happened to me when trying to update from 4.2.2 to 4.3. I was root (obtained with Nexus 4 Toolkit from WugFresh) with stock recovery. Just root, nothing else. Then I tried to install OTA, because with older versions to be root was not a problem. But now it is, and my OTA failed as it failed to you.
Then I managed to manually apply the OTA doing what I told you: first backup, then unroot, and finally using the sideload / adb process button present in the toolkit, following its advices at each pont (very VERY well explained for non-experts). You will need to manually download the OTA update to 4.4. Look for that in these forums.
Hope this helps!
LORD MJ said:
Hello, I'm in a bit of a confusing situation so I hope that someone can shed light on it.
Last night I got a notification that my phone is ready to install the 4.4 update. I didn't have the time or the battery to install it then, so I just left my phone until today. Today, I happily pressed the update button, my phone restarted, it started to update and when the bar was a little more then a third full it stopped and said "Error!" (Thanks for a very informative error message Google! ) I restarted my phone, and now my phone reports that it's up to date?! I tried tapping the Check now, but it keeps saying it's up to date. I checked my cache folder, and there is a .zip file containing the update.
My phone is rooted, I used the Nexus 4 Rootkit, but I DIDN'T install a custom recovery or try to install any custom ROMs. (I'm happy with the stock one) I only installed SuperSU so I can grant root access to some apps and that's it. I didn't install any tweaks.
Now if I'm not mistaken, the OTA update should have worked on my phone, because everything is stock. So why did this happen and why I'm not receiving the update prompt again?
Also as a side note: When I went into the fastboot mode and tried to launch the Recovery mode, it said "No command!" and I had restart my phone.
Click to expand...
Click to collapse
nyepo said:
No, you're wrong. You should've gone to SuperSU app and pressed the "full unroot" button before trying to OTAupdate. This would've replaced the modified bin files for root by the original files, allowing the OTA to be applied successfully.
This happens because the rooting process modifies some system files, so the OTA detects a non-stock scenario and aborts its installation. Also when the OTA fails, a flag marks this update as a "fail update" so your system will continue to show you that it's "updated" as he thinks the only update available isn't suitable for you. He is just waiting for the next OTA update.
Now you have to install the OTA via sideload / adb. I would recommend to make a full nandroid backup before everything else. Then fully unroot your phone and apply the OTA using adb.
This is exactly what happened to me when trying to update from 4.2.2 to 4.3. I was root (obtained with Nexus 4 Toolkit from WugFresh) with stock recovery. Just root, nothing else. Then I tried to install OTA, because with older versions to be root was not a problem. But now it is, and my OTA failed as it failed to you.
Then I managed to manually apply the OTA doing what I told you: first backup, then unroot, and finally using the sideload / adb process button present in the toolkit, following its advices at each pont (very VERY well explained for non-experts). You will need to manually download the OTA update to 4.4. Look for that in these forums.
Hope this helps!
Click to expand...
Click to collapse
Thanks. Unfortunetly the OTA update failed even when I tired ADB sideload, so I had to flash the factory image. Now it works like a charm.
LORD MJ said:
Thanks. Unfortunetly the OTA update failed even when I tired ADB sideload, so I had to flash the factory image. Now it works like a charm.
Click to expand...
Click to collapse
It failed because you have modified files in your system, such as modified gps.conf or build.prop, custom kernel and non-official radio will give errors too.
I did a "flash stock+unroot" and relocked my device via the Wug app and it still errors
eksasol said:
It failed because you have modified files in your system, such as modified gps.conf or build.prop, custom kernel and non-official radio will give errors too.
Click to expand...
Click to collapse
I really have no idea how did that happen. Maybe some app modified it or I messed some things up. I'm now going to make a full backup of my phone, so I can apply the next OTA with much less pain.
LORD MJ said:
I really have no idea how did that happen. Maybe some app modified it or I messed some things up. I'm now going to make a full backup of my phone, so I can apply the next OTA with much less pain.
Click to expand...
Click to collapse
The OTA update can fail for many reasons, it could be due to any changes to the /system partition which is what root does, such as changes to gps.conf file, changes in build.prop, different kernel or radio.
If you're going to make a full backup, what you should do is flash a full factory image (link in my signature, and provided you already backup your data.) Then boot into a custom recovery to make a full backup, (not flash the recovery, but: fastboot boot twrp.img) When you do the backup make sure the boot (kernel) and recovery partition are selected. However, you can't backup the radio partition, but that should be fine unless you intend to use the LTE radio.
I have a similar problem. I have ROOTED device with TWRP recovery and stock 4.3 android (obtained OTA before rooting), and I just got notification that my OTA update to 4.4 is ready to be installed.
So I clicked Restart and Install button and the phone restarts(as it should) but after that it went in TWRP recovery and waited for some instruction I suppose. I didn't know what to click exactly, so I clicked Reboot from TWPR menu and it went in fastboot mode. From fastboot I chose Start and phone turns on. Updating didn't even start..
So, were there something that I could do when I was in TWRP recovery that could initiate updating process, or I never had a chance?
What exactly I should do to get that update on my phone? Sorry for my English and if was unclear.

Latest Android N Update Bootlooped Me, Need ADB Sideload Help

Hello all,
I got the latest update OTA and it appears to have bricked my phone. It looks like it is stuck on the boot screen and won't go further. I went into Recovery and tried to clear cache, but no dice. I also tried to factory reset and no dice either. Now, I'm stuck. I don't have an unlocked bootloader to flash factory images, nor did I ever enable OEM unlocking.
When sideloading the OTA from Google's site, the Android N OTAs don't work, so I tried Marshmallow. Those do work, however, I hit a roadblock and have no idea how to solve it. It starts installing the update when I get the following:
Warning: No file_contextsThis package is for "angler" devices; this is a " ".
E:Error in /sideload/package.zip
(Status 7)
Installation aborted.
How do I fix this? Anyone?!
UserDemos said:
Hello all,
I got the latest update OTA and it appears to have bricked my phone. It looks like it is stuck on the boot screen and won't go further. I went into Recovery and tried to clear cache, but no dice. I also tried to factory reset and no dice either. Now, I'm stuck. I don't have an unlocked bootloader to flash factory images, nor did I ever enable OEM unlocking.
When sideloading the OTA from Google's site, the Android N OTAs don't work, so I tried Marshmallow. Those do work, however, I hit a roadblock and have no idea how to solve it. It starts installing the update when I get the following:
Warning: No file_contextsThis package is for "angler" devices; this is a " ".
E:Error in /sideload/package.zip
(Status 7)
Installation aborted.
How do I fix this? Anyone?!
Click to expand...
Click to collapse
Try this out.
1. Download TOOL ALL IN ONE
2. Download Drives
3. Check if device is recognize
4. Then UNLOCK to unlock bootloader
5. Verify if Bootloader is unlock
6. Flash a stock firmware.
If for some reason that application doesnt work do it manually
1. Install Minimal ADB and Fastboot
To get CMD working just click on the Minimal ADB and Fastboot application program
To flash a .img file place the files inside the Minimal ADB and Fastboot folder located in your program folder
2. Unlock Bootloader ( follow this guide)
3. Then follow the section [ How To Flash The Factory Images]
UserDemos said:
Hello all,
I got the latest update OTA and it appears to have bricked my phone. It looks like it is stuck on the boot screen and won't go further. I went into Recovery and tried to clear cache, but no dice. I also tried to factory reset and no dice either. Now, I'm stuck. I don't have an unlocked bootloader to flash factory images, nor did I ever enable OEM unlocking.
When sideloading the OTA from Google's site, the Android N OTAs don't work, so I tried Marshmallow. Those do work, however, I hit a roadblock and have no idea how to solve it. It starts installing the update when I get the following:
Warning: No file_contextsThis package is for "angler" devices; this is a " ".
E:Error in /sideload/package.zip
(Status 7)
Installation aborted.
How do I fix this? Anyone?!
Click to expand...
Click to collapse
Having the exact same problem this OTA has also bricked my phone.. It just shows boot animation forever. I've tried factory resetting, clearing cache and side-loading the OTA which succeeded but still didn't change anything. I didn't have OEM unlocking enabled so I can't even flash stock again I think I'm screwed
peaconut, I never selected the OEM unlock option whenever I had the N Preview. Just didn't expect to have it get totally messed up from an OTA.
Any additional thoughts based on my errors produced?
I had the bootloop issue as well. I fixed it by:
booting into recovery
wiping cache
wiping data
wiping cache
reboot
Booted into N just fine. Sucks I lost data, but was a quick fix.
Note: I never unlocked bootloader ever with phone. Was a bone stock 6 install with May security patch that was OTA updated that broke.
major97702 said:
I had the bootloop issue as well. I fixed it by:
booting into recovery
wiping cache
wiping data
wiping cache
reboot
Booted into N just fine. Sucks I lost data, but was a quick fix.
Note: I never unlocked bootloader ever with phone. Was a bone stock 6 install with May security patch that was OTA updated that broke.
Click to expand...
Click to collapse
Or, you can let it bootloop for about 15 mins, and it fixes itself...that's what mine did, scared the crap out of me at first, thank goodness I've learned patience....
You don't need it unlock. I was just explain the process to unbrick it in case you had a soft brick
---------- Post added at 10:05 PM ---------- Previous post was at 10:04 PM ----------
UserDemos said:
peaconut, I never selected the OEM unlock option whenever I had the N Preview. Just didn't expect to have it get totally messed up from an OTA.
Any additional thoughts based on my errors produced?
Click to expand...
Click to collapse
I'm in the same boat. Took the OTA and it bootlooped for at least an hour or 2. I did the adb sideload ota and still bootlooping. Tried factory reset and cache wipe and has been trying to boot for 10 mins without any luck. Hoping it just boots because I have no other ideas.
Imacellist said:
I'm in the same boat. Took the OTA and it bootlooped for at least an hour or 2. I did the adb sideload ota and still bootlooping. Tried factory reset and cache wipe and has been trying to boot for 10 mins without any luck. Hoping it just boots because I have no other ideas.
Click to expand...
Click to collapse
I'm in the exact same position as you! Let me know if anything changes
can anyone help me please? i did the ota update and i am stuck on the boot animation. i dont even have access to adb sideload since i didnt enable usb debugging and i also didnt enable oem unlocking
Ame123 said:
can anyone help me please? i did the ota update and i am stuck on the boot animation. i dont even have access to adb sideload since i didnt enable usb debugging and i also didnt enable oem unlocking
Click to expand...
Click to collapse
You didn't need to do that, and side load will still work. Just boot into recovery, and choose update from adb. You may just need to install drivers on your PC but it should work.
I was unable to resolve my issue, and got on chat with Google support. They are replacing it for me, so if you can't fix it try chatting with them.
Imacellist said:
You didn't need to do that, and side load will still work. Just boot into recovery, and choose update from adb. You may just need to install drivers on your PC but it should work.
I was unable to resolve my issue, and got on chat with Google support. They are replacing it for me, so if you can't fix it try chatting with them.
Click to expand...
Click to collapse
my nexus 6p is connecting via fast boot but its not connecting via adb can you help me? and where should i go to chat with google? can you give the link?
Imacellist said:
You didn't need to do that, and side load will still work. Just boot into recovery, and choose update from adb. You may just need to install drivers on your PC but it should work.
I was unable to resolve my issue, and got on chat with Google support. They are replacing it for me, so if you can't fix it try chatting with them.
Click to expand...
Click to collapse
Did you buy your phone through Google? I'm still having the issue however I bought my phone through Carphone Warehouse in the UK, gonna go down this weekend and see what they say
For Google chat just go to the play store on your PC and click help. As for adb, did you choose recovery, then update from adb? If so adb should be working fine. If not then it's a driver issue on your PC.
---------- Post added at 01:06 PM ---------- Previous post was at 01:04 PM ----------
AlfexOmega said:
Did you buy your phone through Google? I'm still having the issue however I bought my phone through Carphone Warehouse in the UK, gonna go down this weekend and see what they say
Click to expand...
Click to collapse
Yes I bought it through Google. This has always provided the best customer service from my experience. Did you at least get Nexus protect? If so at least you can pay to replace it.
Mine got in a bootloop. I entered recovery mode and performed a reset/wipe and it worked.
Sent from my Nexus 6P using Tapatalk
mkouk said:
Mine got in a bootloop. I entered recovery mode and performed a reset/wipe and it worked.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
you are lucky mate i have wiped so many times but it still gets stuck on the boot animation forever. also adb isnt working the since i never connected it to the pc. now i dont have a phone :crying::crying::crying:
UserDemos said:
Hello all,
I got the latest update OTA and it appears to have bricked my phone. It looks like it is stuck on the boot screen and won't go further. I went into Recovery and tried to clear cache, but no dice. I also tried to factory reset and no dice either. Now, I'm stuck. I don't have an unlocked bootloader to flash factory images, nor did I ever enable OEM unlocking.
When sideloading the OTA from Google's site, the Android N OTAs don't work, so I tried Marshmallow. Those do work, however, I hit a roadblock and have no idea how to solve it. It starts installing the update when I get the following:
Warning: No file_contextsThis package is for "angler" devices; this is a " ".
E:Error in /sideload/package.zip
(Status 7)
Installation aborted.
How do I fix this? Anyone?!
Click to expand...
Click to collapse
checkout my thread http://forum.xda-developers.com/nexus-6p/help/help-unbricking-nexus-6p-t3382895
Ame123 said:
checkout my thread http://forum.xda-developers.com/nexus-6p/help/help-unbricking-nexus-6p-t3382895
Click to expand...
Click to collapse
You are a life-saver my friend! I'm going to post this thread in so many places for other people who are having the same issues as I did. You literally saved me a $500 headache. Amazing!
So here's an interesting change. So after reading the advice of others to flash the ota that you receive to revert from N, I was able to get M to boot normally. I unlocked the bootloader, and then tried updating back to the N beta. Didn't work. No problem, I'll just flash the factory image, still nope. Basically I can consistently get it to boot to M, but once I try to upgrade it to N, I get nothing. I've had it on N before, but moved off it due to stability. Any thoughts?
hey all, i was on developer preview 4 when this happened. however, I never flashed manually, always OTA. I cannot access recovery. any option besides "barcodes" results in a bootloop. I can fastboot and unlock, push an image, and relock, but it still bootloops. any thoughts?

How to fix DM-VERITY issue for 7.0 flashed updates

Here is how you fix it.
Step 1. download OnePlus3t toolkit (note: don't attach the phone to PC yet)
step 2. reboot your phone into bootloader (if in twrp hit restart -> bootloader) if not in twrp try turning phone on and as you see the oem unlock screen hit volume up and down and choose fastboot (or bootloader)
step 3. open oneplus3t toolkit
step 4. choose option 8 (flash stock recovery)
step 5. hit enter and when it says waiting 4 devices attach your device to pc
step 6. let it finish
step 7. when recovery comes up, hold power button for 10 seconds or hit exit (if you can choose it) and reboot into system
step 8. if it keeps rebooting into a stock recovery and you cant decrypt... then when your phone first boots and goes into oem-unlock error hit volume up and click restart.
step 9. Reflash TWRP and SuperSU if needed
Step 10. Enjoy!
Did not work for me. Stock recovery, stock nougat, locked bootloader and I still have dm-verity error.
Skwerl23 said:
Here is how you fix it.
Step 1. download OnePlus3t toolkit (note: don't attach the phone to PC yet)
step 2. reboot your phone into bootloader (if in twrp hit restart -> bootloader) if not in twrp try turning phone on and as you see the oem unlock screen hit volume up and down and choose fastboot (or bootloader)
step 3. open oneplus3t toolkit
step 4. choose option 8 (flash stock recovery)
step 5. hit enter and when it says waiting 4 devices attach your device to pc
step 6. let it finish
step 7. when recovery comes up, hold power button for 10 seconds or hit exit (if you can choose it) and reboot into system
step 8. if it keeps rebooting into a stock recovery and you cant decrypt... then when your phone first boots and goes into oem-unlock error hit volume up and click restart.
step 9. enjoy!
Click to expand...
Click to collapse
Can TWRP be installed afterwards or will it come back when TWRP is installed?
Michalko5896 said:
Did not work for me. Stock recovery, stock nougat, locked bootloader and I still have dm-verity error.
Click to expand...
Click to collapse
Try flashing TWRP and back to stock recovery.
If all keeps happening you may need to follow the guide to unbrick the phone.
I'd personally keep flashing different things if data is important. Sorry to hear this happened. Sounds like dm-verity should never have been a thing. So frustrating. Please update us on what you find. You can always erase system and all then reflash image.
Skwerl23 said:
Try flashing TWRP and back to stock recovery.
If all keeps happening you may need to follow the guide to unbrick the phone.
I'd personally keep flashing different things if data is important. Sorry to hear this happened. Sounds like dm-verity should never have been a thing. So frustrating. Please update us on what you find. You can always erase system and all then reflash image.
Click to expand...
Click to collapse
I have tried everything. DM-verity error every fricking time.. Tbh, I really hate oneplus. They are not releasing factory images, with factory images I could fix every issue in 5 minutes.
I feel your frustration. There is this forum
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Michalko5896 said:
I have tried everything. DM-verity error every fricking time.. Tbh, I really hate oneplus. They are not releasing factory images, with factory images I could fix every issue in 5 minutes.
Click to expand...
Click to collapse
Go to TWRP>Wipe>Advanced Wipe>Select system>Repair or change file system>Change filesystem>EXT4>Flash your ROM
That fixed it for me
Michalko5896 said:
I have tried everything. DM-verity error every fricking time.. Tbh, I really hate oneplus. They are not releasing factory images, with factory images I could fix every issue in 5 minutes.
Click to expand...
Click to collapse
I used the hard brick fix to go back to 3.5.1? I let the system update to 3.5.4. Go into developer settings and check allow oem unlock. Went into bootloader and oem unlocked. It will erase everything. Downloaded and put the OTA patch(940gb~not full) and supersu 2.79 on the device somewhere and did a local update with the patch through stock recovery. Went into bootloader and flashed TWRP 3.0.2.0(not 3.0.3.0). Do not exit bootloader. In bootloader I fastboot BOOT the 3.0.2.0 TWRP(3.0.3.0 would not boot up and screwed the dm-verity). If it(3.0.2.0) doesn't want to boot then quickly hold the power button in and wait till it starts rebooting and go into recovery menu option). Swipe to allow modifications and flash the supersu 2.79 that was placed on the device somewhere. This worked for me and no dm-verity error with f2fs.
Long process but it worked.
does dm-verity error mean anything? I have it also currently but nougat seems to be running fine...
PaKii94 said:
does dm-verity error mean anything? I have it also currently but nougat seems to be running fine...
Click to expand...
Click to collapse
https://source.android.com/security/verifiedboot/
In a nutshell, extra security on the boot partition to "ensure chain of trust" one of the possible requirements for Android Pay backend.
********EDIT***********
This method didn't work on the newest beta, and the OP3T ToolKit way has never worked for me on any version of OOS.
card13 said:
https://source.android.com/security/verifiedboot/
In a nutshell, extra security on the boot partition to "ensure chain of trust" one of the possible requirements for Android Pay backend.
********EDIT***********
This method didn't work on the newest beta, and the OP3T ToolKit way has never worked for me on any version of OOS.
Click to expand...
Click to collapse
I see thanks. I guess it doesn't matter to me cause I haven't started using android Pay and since I'm rooted currently
What causes the dm-verity issue in the first place?
guys if my device is unlocked will i still get the ota updates?
how about root ? if my device rooted willi still get ota updates?
saberzaid said:
guys if my device is unlocked will i still get the ota updates?
how about root ? if my device rooted willi still get ota updates?
Click to expand...
Click to collapse
Yes to first. No to second, It will try but will fail.
Sent from my ONEPLUS A3000 using Tapatalk
Mine is unlocked and rooted. The update failed. Then it redownloaded the full 1.4gb. That's how I found the URL. Then it flashed fine but brought recovery to stock and wiped root. Had to use the toolkit to get TWRP and root back.
So yes, even rooted gets the update
noahvt said:
Go to TWRP>Wipe>Advanced Wipe>Select system>Repair or change file system>Change filesystem>EXT4>Flash your ROM
That fixed it for me
Click to expand...
Click to collapse
I did a system restore previously and it set system to ext4. Maybe that's why I didn't have issues.
This dm-verity issue could be showing the instability of f2fs. Hmmm
Hello, just reset original rom under 6.0.1 and the problems and then twrp then flash rom custom
jejemc said:
Hello, just reset original rom under 6.0.1 and the problems and then twrp then flash rom custom
Click to expand...
Click to collapse
Hi guy, I followed your instruction, however, it still has the problem.
When I use the stock recovery to flash the beta1 package, it could not be flashed in.
lanbingxuanyi said:
Hi guy, I followed your instruction, however, it still has the problem.
When I use the stock recovery to flash the beta1 package, it could not be flashed in.
Click to expand...
Click to collapse
Hello, I am going under the beta with the message in red dm-verity for the removed I returned under original rom then I handed twrp then rom custom
card13 said:
https://source.android.com/security/verifiedboot/
In a nutshell, extra security on the boot partition to "ensure chain of trust" one of the possible requirements for Android Pay backend.
********EDIT***********
This method didn't work on the newest beta, and the OP3T ToolKit way has never worked for me on any version of OOS.
Click to expand...
Click to collapse
PaKii94 said:
I see thanks. I guess it doesn't matter to me cause I haven't started using android Pay and since I'm rooted currently
Click to expand...
Click to collapse
I'm running 7.0 stable, unlocked bootloader and dm-verity warning. Android Pay still functions with the workaround.

Flashfire OTA caused phone to no longer boot?

I received the May OTA update earlier today, and since I'm rooted I decided to flash it with Flashfire. As soon as I opened Flashfire I was prompted to click a button to install the OTA. However, I then recieved a warning message "warning: it has been detected that you may be trying to flash a block-level ota, but your /system, /vendor, or /oem partition has been modified. This will likely cause the flash to fail!"
However, I clicked "ignore" and continued anyways, since I interpreted "flash to fail" to mean "will either not update (abort and stay the same) or update correctly." However, now my phone is stuck on the booting screen. I should at least still have TWRP installed, since I believe the "preserve recovery" box was automatically checked.
What can I do to fix the issue? I'm thinking if I download the full OTA and flash in recovery, maybe that will work?
If you can still boot into the bootloader (not recovery), do that and run through the manual install of the factory image (via the fastboot command - see the install instructions in the general forum). Again, do this manually (which requires downloading the factory image, extracting the files out, and manually flashing each file (bootloader, boot, etc.)) as that's really the only way you're going to get back to normal. You will have to re-root, etc., but that isn't that much work and saves the pain of going through what you just went through.
jeffrey123987 said:
I received the May OTA update earlier today, and since I'm rooted I decided to flash it with Flashfire. As soon as I opened Flashfire I was prompted to click a button to install the OTA. However, I then recieved a warning message "warning: it has been detected that you may be trying to flash a block-level ota, but your /system, /vendor, or /oem partition has been modified. This will likely cause the flash to fail!"
However, I clicked "ignore" and continued anyways, since I interpreted "flash to fail" to mean "will either not update (abort and stay the same) or update correctly." However, now my phone is stuck on the booting screen. I should at least still have TWRP installed, since I believe the "preserve recovery" box was automatically checked.
What can I do to fix the issue? I'm thinking if I download the full OTA and flash in recovery, maybe that will work?
Click to expand...
Click to collapse
Fixed
johnhazelwood said:
If you can still boot into the bootloader (not recovery), do that and run through the manual install of the factory image (via the fastboot command - see the install instructions in the general forum). Again, do this manually (which requires downloading the factory image, extracting the files out, and manually flashing each file (bootloader, boot, etc.)) as that's really the only way you're going to get back to normal. You will have to re-root, etc., but that isn't that much work and saves the pain of going through what you just went through.
Click to expand...
Click to collapse
Thanks, I actually just flashed the full factory OTA and now everything is working fine once again. I did lose root access though, so I have to reflash superSU as well. Thank you for trying to help though! If flashing the full OTA in TWRP had also failed, my Plan B was to just flash the factory image as you suggested.
jeffrey123987 said:
Thanks, I actually just flashed the full factory OTA and now everything is working fine once again. I did lose root access though, so I have to reflash superSU as well. Thank you for trying to help though! If flashing the full OTA in TWRP had also failed, my Plan B was to just flash the factory image as you suggested.
Click to expand...
Click to collapse
Or next time just use the full image (not OTA) with FF (with select flash firmware package). You won't have any issues plus will retain root/recovery. You'll be back up and running in one minute.
Glad you got it back up and running. Also, as mentioned, you could flash the full package via flashfire, just don't flash the bootloader using it.

Unable to update A1 OTA error "Installation problem"

Hello everyone. I am trying to update to October 2017 OTA. Everytime it returns error "Installation problem".
Is this because my phone has a modified bootloader? Perhaps its because I have rooted it? How can I get OTA updates again?
I'm having the same issue. Thought it was because of root but I restored the stock boot.img and no longer rooted but still getting 'Installation Problem' whenever i try to update.
jhorner said:
I'm having the same issue. Thought it was because of root but I restored the stock boot.img and no longer rooted but still getting 'Installation Problem' whenever i try to update.
Click to expand...
Click to collapse
you should also lock the bootloader for ota to work, i dont have mi a1 yet, but on nexus 6 it worked that way
Note to self, re-locking the bootloader will brick your phone
jhorner said:
Note to self, re-locking the bootloader will brick your phone
Click to expand...
Click to collapse
Not on this device... Done many times
Need to be unrooted and stock recovery. Unlocked BL is fine. Switch partition and start device for ota. Then reroot
Chris_Cheekyz said:
Not on this device... Done many times
Click to expand...
Click to collapse
Hmm. I just did 'fastboot oem lock' and after rebooting it says 'The system has been destroyed'
jhorner said:
Hmm. I just did 'fastboot oem lock' and after rebooting it says 'The system has been destroyed'
Click to expand...
Click to collapse
If you are rooted, your phone won't work if you try to lock bootloader. Unroot first and try again
First install stock ROM via MiFlashTool and then update..
It'll definitely work!
matcho13579 said:
If you are rooted, your phone won't work if you try to lock bootloader. Unroot first and try again
Click to expand...
Click to collapse
Just for context, this was the process
1. Tried to update w/o any changes, it failed
2. Unrooted, confirmed w/ SuperSU and tried to update, it failed
3. Locked bootloader via 'fastboot oem lock' and when the device rebooted, it gave the 'system destroyed' message
jhorner said:
Note to self, re-locking the bootloader will brick your phone
Click to expand...
Click to collapse
relocking bootloader dons'nt brick my phone
i have done this using this cmd - fastboot oem lock
and its works perfact
but do this at your own risk
:good::good::good:
Most ota installations failed is because system partition has been compromised. Even if you just mount it rw. You'll need to reflash system img for both system_a and system_b partition.
Restore stock boot.img if your using root (I'm using magisk) install ota and reroot. For magisk, starting from 14.4,you can follow the ota instructions for magisk, basically mi a1 the same as the pixel but not as strict. Locking and unlocking bootloader will not brick or wipe data for mi a1.
jhorner said:
Just for context, this was the process
1. Tried to update w/o any changes, it failed
2. Unrooted, confirmed w/ SuperSU and tried to update, it failed
3. Locked bootloader via 'fastboot oem lock' and when the device rebooted, it gave the 'system destroyed' message
Click to expand...
Click to collapse
Damn.
I've tried to remove root. Removed SuperSu. Flashed stock bootloader - but update continues to fail.
I'll just wait for Oreo then do a full flash
Even i got the same error
What i did was,
Removed Magisk
Flashed latest rom by mi flash with save user data option
Then update ur device, it will work for sure!
Monthly security updates installation problem,how to fix that? Please throw some lights
GSAA RAIN said:
Monthly security updates installation problem,how to fix that? Please throw some lights
Click to expand...
Click to collapse
You should post some information on your phone. Is it stock/rooted? Did you unlock bootloader and install TWRP? What modifications have you done to the phone (if any?)
cheesekun27 said:
Damn.
I've tried to remove root. Removed SuperSu. Flashed stock bootloader - but update continues to fail.
I'll just wait for Oreo then do a full flash
Click to expand...
Click to collapse
You can use miflash and flash the full rom so you are back at stock, just make sure you select the option to save user data so it does not wipe your phone clean.
I have the same problem...what i did was unlocking the bootloader and tried to install themes via substratum and andromeda...but that didn't worked so i uninstalled both and relocked the bootloader. I didn't even rooted the phone but getting the same error. Is this because somehow partition was compromised and can someone please provide me a brief description of rooting this phone and usage of magisk?
Angelictears said:
Most ota installations failed is because system partition has been compromised. Even if you just mount it rw. You'll need to reflash system img for both system_a and system_b partition.
Restore stock boot.img if your using root (I'm using magisk) install ota and reroot. For magisk, starting from 14.4,you can follow the ota instructions for magisk, basically mi a1 the same as the pixel but not as strict. Locking and unlocking bootloader will not brick or wipe data for mi a1.
Click to expand...
Click to collapse
In short one needs to flash the stock rom using mi flash tool right?
---------- Post added at 06:43 AM ---------- Previous post was at 06:42 AM ----------
Angelictears said:
Most ota installations failed is because system partition has been compromised. Even if you just mount it rw. You'll need to reflash system img for both system_a and system_b partition.
Restore stock boot.img if your using root (I'm using magisk) install ota and reroot. For magisk, starting from 14.4,you can follow the ota instructions for magisk, basically mi a1 the same as the pixel but not as strict. Locking and unlocking bootloader will not brick or wipe data for mi a1.
Click to expand...
Click to collapse
thakurvishwendra said:
I have the same problem...what i did was unlocking the bootloader and tried to install themes via substratum and andromeda...but that didn't worked so i uninstalled both and relocked the bootloader. I didn't even rooted the phone but getting the same error. Is this because somehow partition was compromised and can someone please provide me a brief description of rooting this phone and usage of magisk?
Click to expand...
Click to collapse
Were you able to solve your problem?
Couldn't update Installation problem
Rohit Surya said:
Even i got the same error
What i did was,
Removed Magisk
Flashed latest rom by mi flash with save user data option
Then update ur device, it will work for sure!
Click to expand...
Click to collapse
I did thi but problem is still same installation problem
---------- Post added at 04:23 PM ---------- Previous post was at 04:20 PM ----------
goofball2k said:
You should post some information on your phone. Is it stock/rooted? Did you unlock bootloader and install TWRP? What modifications have you done to the phone (if any?)
Click to expand...
Click to collapse
Nothing yet I am facing the installation problem

Categories

Resources