Problems with unroot need stock boot image april 2019 - Xiaomi Mi A1 Questions & Answers

I wanted to update my phone to june 2019 patch and tryed to unroot it
After some flash attempts I ended up flashing full stock - apparently april 2019.
Now only back soft button works and I can't open the full menu from the top
I'd like to try to flash stock boot.img from april or may 2019 - pie, but can't find it

Related

How to update the 2016 February OTA with systemless root?

I have TWRP, but I'm still on android 6.0, security patch November 1, 2015, system version 24.11.18.clark_retus and no xposed. I have systemless root, so does full remove root in SuperSU then flashing the right recovery.img work to take all the OTA's till now? The February TWRP flashable OTA thread no longer has a live link.
HelpMeXDA said:
I have TWRP, but I'm still on android 6.0, security patch November 1, 2015, system version 24.11.18.clark_retus and no xposed. I have systemless root, so does full remove root in SuperSU then flashing the right recovery.img work to take all the OTA's till now? The February TWRP flashable OTA thread no longer has a live link.
Click to expand...
Click to collapse
This question is hard to answer... will it work? Maybe, we don't know. The problem is if you are rooted, you did it for a reason (or I would assume so) and you have made some changes to the /system partition over time. Doing a full unroot will not undo those changes. So if you do a full unroot, and fastboot the correct recovery image, then accept the OTA, the recovery is going start the OTA's installation script attempt to process it where it will start a checklist of items to verify, bootloader, boot image, system image, etc... the problem is we don't know what changes will cause the update to error out and which will allow it to apply.
To be honest, I don't think I have heard anyone say they have been able to successfully take this update without going back to pure stock, but ymmv.
The best thing to do would be to return to pure stock via the factory firmware images, we have a known good one of the May 2016 security update.

Safetynet fails on clean Nougat install

I just updated to Nougat and safetynet fails. I have not even rooted or put TWRP back on.
I'm using the EU ROM.
Previously I updated from 6.0 Sept to 6.0 Dec patch by flashing the boot and recovery image (from the Sept. firmware) on the device, then taking the update. And then flashing TWRP and magisk again.
6.0 Dec. to Nougat didn't go as well. I flashed the boot and recovery but the phone didn't boot... I used the Sept firmware as I do not have the Dec. firmware (I'm very adamant about getting the latest stock ROM for flashing purposes..). Anyways, so I had to flash the entire 6.0 Sept ROM again (I did not wipe my data) and then update to the December patch and then to Nougat. Would have been so much easier if I had the December patch ROM to flash...
I actually uninstalled magisk before all of this. But actually, magisk/root would be gone after flashing the boot image anyway.
After updating to Nougat I have not done any modding, but safetynet fails... Why is this? And I can only start from scratch from the 6.0 September patch...so starting over is not sounding good.
Possibly due to the unlocked bootloader from reading other threads...
d.casper.b said:
I just updated to Nougat and safetynet fails. I have not even rooted or put TWRP back on.
I'm using the EU ROM.
Previously I updated from 6.0 Sept to 6.0 Dec patch by flashing the boot and recovery image (from the Sept. firmware) on the device, then taking the update. And then flashing TWRP and magisk again.
6.0 Dec. to Nougat didn't go as well. I flashed the boot and recovery but the phone didn't boot... I used the Sept firmware as I do not have the Dec. firmware (I'm very adamant about getting the latest stock ROM for flashing purposes..). Anyways, so I had to flash the entire 6.0 Sept ROM again (I did not wipe my data) and then update to the December patch and then to Nougat. Would have been so much easier if I had the December patch ROM to flash...
I actually uninstalled magisk before all of this. But actually, magisk/root would be gone after flashing the boot image anyway.
After updating to Nougat I have not done any modding, but safetynet fails... Why is this? And I can only start from scratch from the 6.0 September patch...so starting over is not sounding good.
Possibly due to the unlocked bootloader from reading other threads...
Click to expand...
Click to collapse
I have the same issue with safetynet, I could only fix it while flashing this: Universal SafetyNet Fix v2 beta 4 !
https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431
An unlocked bootloader will cause SafetyNet to fail in Nougat, at least in some devices (Pixel/Nexus, HTC 10/U11, OP3/3T too), could well be the reason it is failing.

Stock Boot Image of Arpil 2018 Security Patch Needed

I will be thankful if someone can provide me with Stock Boot Image with April 2018 Security Patch.
Actually I installed some incompatible modules from magisk and my phone is on bootloop now. I want to flash stock boot image to fix the issue without losing data.
Any help is much appreciated.

help regarding fishy update!!!

so today as of regular cleaning and restoring my g4 plus to stock...i restored and think i updated it to the the february security path xml zip via fastboot using (ATHENE_NPJS25.93-14-10_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml) file...the problem was that i was scared to hell when the security patch downgraded itself to september 2017 even on using feb'18 file and the stock recovery returned "no command" error on startup and "error" on updating so...
can please anyone tell me...
1.what's the current version of the bootloader on the latest april/feb'18 build?
2.can i flash apr'18 build over the the one flashed before with all the commands safely(im too worried about hard bricking it!!!!!)?
thank you so much in advance!
1)The NPJS25.93-14-10 firmware is the September 2017 security patch firmware, so flashing that would flash the Sept 2017 security patch to your device. You'd have likely received the December 2017 NPJS25.93-14-13 update then the NPJS25.93-14-15 Feb 2018 update. I'm not entirely sure which update you tried to flash then...
2)The NPJS25.93-14-18 firmware is currently the latest April 2018 security patch firmware, available from here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 I've seen it flashed on Indian, Brazilian, EU and UK devices, not sure about other territories. Current bootloader version on the April 2018 firmware is B1:07.
3)You should be able to flash the April 2018 firmware over whatever you flashed, and as it's the latest firmware, it should not hard brick your device. Please avoid flashing older firmwares or if you do, be very careful with OTA updates.
4)The 'no command' screen is the normal screen for stock recovery. If I recall, if you're on that screen, hold down power then tap the volume up key, then release both to access the stock recovery.

Root latest patch

How to root this latest build number P-SMR6-RC001-RZR-201022.3201 November security patch...
Looks like it's not possible?
Never mind. Razer posted the November system image. I was able to use Magisk Manager to patch the boot.img and then flash it using fastboot.

Categories

Resources