Hey guys
so initially i rooted partition B using magisk now i got the new update of 75mb. I switched to partition A where it was still on august security patch and i made update of 1gb followed by 75mb update.
So i switched back to partition B and it was unrooted but the update did not install on this partition and told me to make update of 75mb again but i tired to update and it gave me an error but safetynet was not passed ctsproilfe:false
can someone help me? i tried to flash boot.img of stock but same result.
faddys123 said:
Hey guys
so initially i rooted partition B using magisk now i got the new update of 75mb. I switched to partition A where it was still on august security patch and i made update of 1gb followed by 75mb update.
So i switched back to partition B and it was unrooted but the update did not install on this partition and told me to make update of 75mb again but i tired to update and it gave me an error but safetynet was not passed ctsproilfe:false
can someone help me? i tried to flash boot.img of stock but same result.
Click to expand...
Click to collapse
I ended up having to flash the previous Oct (7.10.14) fastboot ROM using MiFlash, rebooted back into the stock ROM and then took the single 1GB OTA update which has the Oct 30 kernel and build number. Booted into TWRP and reflashed Magisk 14.4 and Safetynet passed.
BTW, did you try booting into partition A and check whether the Oct 30 kernel and build OTA (75MB) update was installed? Just thinking this might be the case since you took 2 OTA updates.
cmk7128 said:
I ended up having to flash the previous Oct (7.10.14) fastboot ROM using MiFlash, rebooted back into the stock ROM and then took the single 1GB OTA update which has the Oct 30 kernel and build number. Booted into TWRP and reflashed Magisk 14.4 and Safetynet passed.
BTW, did you try booting into partition A and check whether the Oct 30 kernel and build OTA (75MB) update was installed? Just thinking this might be the case since you took 2 OTA updates.
Click to expand...
Click to collapse
using miflash did you do this without the data being wiped?
faddys123 said:
using miflash did you do this without the data being wiped?
Click to expand...
Click to collapse
I selected the "save user data" option before flashing in MiFlash but somehow all my data was erased when the phone rebooted. Not sure why that happened.
cmk7128 said:
I selected the "save user data" option before flashing in MiFlash but somehow all my data was erased when the phone rebooted. Not sure why that happened.
Click to expand...
Click to collapse
if i just download the stock rom extract boot.img and system.img and flash manually via fastboot it should return to stock? with my app data etc still intact then i can run the update and then flash magisk for root?
faddys123 said:
if i just download the stock rom extract boot.img and system.img and flash manually via fastboot it should return to stock? with my app data etc still intact then i can run the update and then flash magisk for root?
Click to expand...
Click to collapse
Not sure, but worth a try. What about booting from partition A?
cmk7128 said:
Not sure, but worth a try. What about booting from partition A?
Click to expand...
Click to collapse
i booted into A and it is updated with build 30 oct not rooted, but if i root this using new magisk 14.4 for future updates i won't be able to update and partition b is still on update from 14 oct
faddys123 said:
i booted into A and it is updated with build 30 oct not rooted, but if i root this using new magisk 14.4 for future updates i won't be able to update and partition b is still on update from 14 oct
Click to expand...
Click to collapse
If I am not mistaken, you can boot into partition B (which is unrooted) for future OTA updates. Being on 7.10.14 updates would just mean the OTA files will be bigger in size compared to the OTA file for updates from 30 Oct?
Yesterday, I run into problems updating my phone to 30 oct version too. At the end I stuck into bootloops. This is how I solved it:
- boot into fastbootmode
- flash 14 oct Image with MiFlash (option: save user data)
- reboot
- download and install update 30 oct
- reboot into fastbootmode
- fastboot oem unlock
- fastboot boot recovery.img
- flash Magisk 14.4
- reboot Phone
cmk7128 said:
If I am not mistaken, you can boot into partition B (which is unrooted) for future OTA updates. Being on 7.10.14 updates would just mean the OTA files will be bigger in size compared to the OTA file for updates from 30 Oct?
Click to expand...
Click to collapse
well partition B was the one originally rooted, but i could not install the new update, so switched partition to A and did the update but booting into partition b still has build of 14th oct whereas partition A (unrooted) is on 30th oct build. so both partitions are not getting updated together
Related
Hello,
Today I received a Motorola Android system update. I did not expect this to happen, because my device has an unlocked bootloader and is rooted, and I have TWRP installed. I never received a system update before in the 1,5 years that I have it.
After the update was downloaded, it started installing by verifying the update and then initiated a reboot. The reboot however ended up in TWRP.
What should I do now? Just reboot? Will that cancel the update or break anything?
Is there any way that I can manually complete the installation of the update?
if you are rooted with twrp installed, just copy update file from /cache to your internal storage. Then unroot your device (discard any changes in /system partition via flashing stock system.img), flash stock recovery and apply update from recovery.
I suppose, file you have being downloaded is just security update.
Please pm me, if this file large than 500MB ;
The update file is named Blur_Version.24.61.52.lux_reteu.reteu.en.EU.zip. It is 69,5 MB (69514015 bytes).
This is the first time I receive a system update (I unlocked the bootloader and rooted my phone right at the start). Strange thing is that the contents of the file all have a timestamp of 14 februari 2014 17:43. I can't believe I received a three year old update. The Moto X Play did not even exist three years ago.
I installed the update. It was 24.201.5.en.EU, containing the security patches of october 2016. So your assumption was right. Still strange that this is the first update I received in 1,5 year.
gewe said:
I installed the update. It was 24.201.5.en.EU, containing the security patches of october 2016. So your assumption was right. Still strange that this is the first update I received in 1,5 year.
Click to expand...
Click to collapse
Hello there, could you let me know how you installed the update (step-by-step if possible), I am having the same problem while updating as my moto x play tries to reboot during the install and I get the TWRP interface. Thanks
gamoraw said:
Hello there, could you let me know how you installed the update (step-by-step if possible), I am having the same problem while updating as my moto x play tries to reboot during the install and I get the TWRP interface. Thanks
Click to expand...
Click to collapse
I followed the instructions I found here, with the following changes:
skip flashing bootloader.img and logo.bin (unlocked bootloader);
skip flashing recovery.img (you want to keep TWRP);
skip erase userdata (keep your data).
Some people advise against not erasing useradata, but I never had a problem skipping that step.
Received security update notification from Moto, and installed.
Moto G4+ XT1644 (4GB/64GB)
TWRP 3110, ElementalX kernel, Magisk rooted, custom logo
bootloader unlocked
Latest TWRP backup on 08/31/17
After install:
Phone now always reboots to TWRP
tried wiping data, cache, Dalvik but no difference
tried restore backup but still reboots to TWRP
Can only shut phone off via power button
Any advice to get my phone back to normal will be greatly appreciated. Thanks.
mel2000 said:
Received security update notification from Moto, and installed.
Moto G4+ XT1644 (4GB/64GB)
TWRP 3110, ElementalX kernel, Magisk rooted, custom logo
bootloader unlocked
Latest TWRP backup on 08/31/17
After install:
Phone now always reboots to TWRP
tried wiping data, cache, Dalvik but no difference
tried restore backup but still reboots to TWRP
Can only shut phone off via power button
Any advice to get my phone back to normal will be greatly appreciated. Thanks.
Click to expand...
Click to collapse
You messed up your rom by installing official update on custom kernel. Can you boot from twrp to system? What happens if you do that? Which stock rom you have exactly? Otherwise you can flash stock rom with fastboot, but never downgrade!
strongst said:
Can you boot from twrp to system? What happens if you do that? Which stock rom you have exactly? Otherwise you can flash stock rom with fastboot, but never downgrade!
Click to expand...
Click to collapse
Thank you for your reply, strongst. When I press the Reboot->System buttons in TWRP, the phone boots back to TWRP recovery.
Here are the stats I recorded before things went sideways:
Original stock firmware Build Number - NPJS25.93-14-4
Original OS version - 7.0
Original Kernel - 3.10.84-gb9596e1 [email protected] #1 Fri Mar 3 02:04:02 CST 2017
Original Baseband version - M8952_70030.25.03.62RATHENE_RETUSA_CUST
Updated Kernel - 3.10.84-ElementalX-G4-1.04 [email protected] #1 Sat Mar 11 14:16:55 EST 2017
Note: I found NPJS25.93-14-4 firmware at
https://www.getdroidtips.com/npjs25-93-14-4-march-security-moto-g4-plus
but it's titled as "March 2017 security patch" OTA update. I'm not sure if that is full replacement firmware or not.
If necessary, should I simply flash NPJS25.93-14 (full firmware) via fastboot and allow Moto to finish the updates via OTA?
mel2000 said:
Thank you for your reply, strongst. When I press the Reboot->System buttons in TWRP, the phone boots back to TWRP recovery.
Here are the stats I recorded before things went sideways:
Original stock firmware Build Number - NPJS25.93-14-4
Original OS version - 7.0
Original Kernel - 3.10.84-gb9596e1 [email protected] #1 Fri Mar 3 02:04:02 CST 2017
Original Baseband version - M8952_70030.25.03.62RATHENE_RETUSA_CUST
Updated Kernel - 3.10.84-ElementalX-G4-1.04 [email protected] #1 Sat Mar 11 14:16:55 EST 2017
Note: I found NPJS25.93-14-4 firmware at
https://www.getdroidtips.com/npjs25-93-14-4-march-security-moto-g4-plus
but it's titled as "March 2017 security patch" OTA update. I'm not sure if that is full replacement firmware or not.
If necessary, should I simply flash NPJS25.93-14 (full firmware) via fastboot and allow Moto to finish the updates via OTA?
Click to expand...
Click to collapse
You can also flash the latest available for your device with June security patch. After that you can root again with ex kernel if you want https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Make sure to mount storage within twrp first and save your internal memory before flashing stock rom!
In future, if that happens, you could try booting to the bootloader, then on the bootloader screen, press 'Start' and try to get your device to boot normally. Credit to: https://forum.xda-developers.com/showpost.php?p=72114657&postcount=170
Personally, I'd go with strongst's suggestion to flash the June 2017 stock fastboot ROM - you'd have to revert to stock (completely) anyway to accept the OTA - as you've found out, OTAs will only successfully flash onto a device with stock recovery, kernel, and unmodified system including no root. You may as well update at the same time to the same patch level that the OTA would have brought you up to.
echo92 said:
In future, if that happens, you could try booting to the bootloader, then on the bootloader screen, press 'Start' and try to get your device to boot normally. Credit to: https://forum.xda-developers.com/showpost.php?p=72114657&postcount=170
Personally, I'd go with strongst's suggestion to flash the June 2017 stock fastboot ROM - you'd have to revert to stock (completely) anyway to accept the OTA - as you've found out, OTAs will only successfully flash onto a device with stock recovery, kernel, and unmodified system including no root. You may as well update at the same time to the same patch level that the OTA would have brought you up to.
Click to expand...
Click to collapse
This 100%. Boot into bootloader and choose start from there. I ran into the same issue last night whilst trying to update my XT1644 and figure this out through trial and error. Once I got it back up though, flashing many stock recoveries that I found online couldn't get the update to work either. It would error out a few seconds after booting into the stock recovery and starting the update. I finally resigned to re-flashing a stock image of marshmallow and updating it all again from there. I wanted to pull the stock recovery before I replaced it with TWRP again but I couldn't find a way to do that. Any method I found required having root access already, and of course I can't get root access without flashing a custom recovery first.
echo92 said:
In future, if that happens, you could try booting to the bootloader, then on the bootloader screen, press 'Start' and try to get your device to boot normally.[/url]
Click to expand...
Click to collapse
Thanks for all replies. Rebooting from the bootloader screen brought my phone back to normal. Same March 2017 patch, as well as the same TWRP and ElementalX kernel and build number. Unlocked bootloader logo.bin remains intact. Magisk is still at v13.3 and it passes SafetyNet. Internal memory intact. I'm relieved.
Settings->System Updates->New version NPJ25.93-14.5
However, I'm now contemplating whether it'll be worthwhile to patch my phone to the NPJ25.93-14.5, June 2017 update.
Can I assume that the June 2017 1.1 GB "patch" contains the full NPJ25.93-14.5 firmware for XT1644?
( https://www.androidfilehost.com/?fid=889764386195918175 )
Is there a way to flash the June 2017 ROM via TWRP, and without having to reinstall ElementalX kernel, etc.?
mel2000 said:
Thanks for all replies. Rebooting from the bootloader screen brought my phone back to normal. Same March 2017 patch, as well as the same TWRP and ElementalX kernel and build number. Unlocked bootloader logo.bin remains intact. Magisk is still at v13.3 and it passes SafetyNet. Internal memory intact. I'm relieved.
Settings->System Updates->New version NPJ25.93-14.5
However, I'm now contemplating whether it'll be worthwhile to patch my phone to the NPJ25.93-14.5, June 2017 update.
Can I assume that the June 2017 1.1 GB "patch" contains the full NPJ25.93-14.5 firmware for XT1644?
( https://www.androidfilehost.com/?fid=889764386195918175 )
Is there a way to flash the June 2017 ROM via TWRP, and without having to reinstall ElementalX kernel, etc.?
Click to expand...
Click to collapse
Yes it's the full rom. And no, you need to flash kernel and magisk after every rom flash, stock twrp, fastboot or custom rom doesn't matter(otherwise it's already included).
strongst said:
Yes it's the full rom. And no, you need to flash kernel and magisk after every rom flash, stock twrp, fastboot or custom rom doesn't matter(otherwise it's already included).
Click to expand...
Click to collapse
Thanks again strongst. I'm still contemplating because of the complexity. However, the constant phone notification to update is weakening my resistance. Not sure I want to have to look at that for days on end.
Just to clarify, are you stating that I won't have to reinstall TWRP? That would be a relief.
Would it suffice to copy my internal SD to my PC and restore it later? Do I need to copy everything? Will my Nandroid backup save my Magisk settings?
I did make a TWRP backup of the XT1644 updated to NPJ25.93-14.5. I could share it with you if you'd like. However, you'd still need to flash ElementalX and root after.
mel2000 said:
Thanks again strongst. I'm still contemplating because of the complexity. However, the constant phone notification to update is weakening my resistance. Not sure I want to have to look at that for days on end.
Just to clarify, are you stating that I won't have to reinstall TWRP? That would be a relief.
Would it suffice to copy my internal SD to my PC and restore it later? Do I need to copy everything? Will my Nandroid backup save my Magisk settings?
Click to expand...
Click to collapse
You need to flash twrp after you flashed the stock rom cause the stock rom flash the stock recovery. Copy the whole internal memory, better to save everything when you don't know exactly what you need
Restore the whole internal memory isn't good, just restore what's missing if you recognize it. Your magisk settings will be saved with nandroid, that's true, but don't restore your partitions from nandroid backup from your prior rom version to the new, that cause trouble. Make backup of your apps with titanium backup instead.
Just to clarify - are you on the Amazon software channel (amz) or do you have the Amazon Prime edition of the XT1644 (with the ads on the lockscreen)? I'm just curious as whether this NPJ25.93-14.5 update is exclusive to Amazon or if it's more widespread.
EDIT - seen a couple of users reporting they've received it on the retus channel, so maybe more widespread to US users, maybe to include the Verizon emergency calling patch that the G5 Plus got too?
tmp000 said:
I did make a TWRP backup of the XT1644 updated to NPJ25.93-14.5. I could share it with you if you'd like. However, you'd still need to flash ElementalX and root after.
Click to expand...
Click to collapse
That sounds great tmp000. I'd definitely like you to share it. How would I go about flashing it? Any particular precautions? Thanks.
mel2000 said:
That sounds great tmp000. I'd definitely like you to share it. How would I go about flashing it? Any particular precautions? Thanks.
Click to expand...
Click to collapse
Sorry, I'm not an expert, so I can't say much about precautions. What I will do is tell you what I did to get my phone to its current state now is:
Backup my data
After failing to apply the NPJ25.93-14.5 update many times through a bunch of different stock recoveries that I found online (including versions extracted from full stock ROMs), I found a way to downgrade back to the stock ROM of Marshmallow for the XT1644. I applied all the OTA updates, all the way to NPJ25.93-14.5.
At this point, I flashed TWRP recovery again. At the same time, right after running the command to flash TWRP with fastboot, I also flashed logo.bin to get rid of that unlocked bootloader message. I then booted into TWRP and then backed up the system and boot partition as it was (so stock kernel and no root).
In TWRP, I flashed ElementalX, and then SuperSU after that (I know you are using a different root method so flash yours).
Then I restored the data (data partition only) of the backup I made.
After that, I rebooted into system and everything booted up just fine. I had root access and all of my data was intact. Your steps 2 and 3 would be:
Put my backup with your other backups in the TWRP folder
Do an wipe in TWRP to wipe dalvik cache, cache, system, and boot. DO NOT WIPE INTERNAL STORAGE
Then continue on with step 4 from above. And of course, I can't emphasize enough to back up your data. Not just through TWRP, but any photos, etc that you can copy onto your computer first. I'll PM you a link to my backup.
strongst said:
Your magisk settings will be saved with nandroid, that's true, but don't restore your partitions from nandroid backup from your prior rom version to the new, that cause trouble.
Click to expand...
Click to collapse
Thanks for the advice. However, I'm having trouble determining exactly what I need to backup before the firmware flash.
Which folders from the Root dir of internal memory need to be saved?
Do I need to save the SDCARD directory?
Can I use TWRP to restore individual apps within the Nandroid backup instead of the whole archive?
Just trying to be extra careful to preempt things from going sideways. Thanks.
echo92 said:
I'm just curious as whether this NPJ25.93-14.5 update is exclusive to Amazon or if it's more widespread.
Click to expand...
Click to collapse
I have the retail version of xt1644 and hope that NPJ25.93-14.5 is intended for or compatible with that.
tmp000 said:
I'm ready to do the NPJ25.93-14..5 update. For clarity, I reordered your steps for the update:
Backup my data
Put my backup with your other backups in the TWRP folder
Do an wipe in TWRP to wipe dalvik cache, cache, system, and boot.DO NOT WIPE INTERNAL STORAGE
In TWRP, I flashed ElementalX, and then SuperSU after that (I know you are using a different root method so flash yours).
Then I restored the data (data partition only) of the backup I made.
Click to expand...
Click to collapse
Am I to assume that after step 2 or 3, the actual updating consists of doing a TWRP Restore using the NPJ25.93-14.5 folder that I downloaded? Do I do the wipes before the Restore update? Thanks again for all your help.
mel2000 said:
Am I to assume that after step 2 or 3, the actual updating consists of doing a TWRP Restore using the NPJ25.93-14.5 folder that I downloaded? Do I do the wipes before the Restore update? Thanks again for all your help.
Click to expand...
Click to collapse
Yes, wipe then restore the backup. Sorry for the terrible instructions with missing steps.
mel2000 said:
Received security update notification from Moto, and installed.
Moto G4+ XT1644 (4GB/64GB)
TWRP 3110, ElementalX kernel, Magisk rooted, custom logo
bootloader unlocked
Latest TWRP backup on 08/31/17
After install:
Phone now always reboots to TWRP
tried wiping data, cache, Dalvik but no difference
tried restore backup but still reboots to TWRP
Can only shut phone off via power button
Any advice to get my phone back to normal will be greatly appreciated. Thanks.
Click to expand...
Click to collapse
When you are booted in twrp, reboot to bootloader of system (obviously). Then press power button when it displays start. Like this the phone will boot into system and not in recovery
Or
Just reboot to bootloader and read the thread attached with it.
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Be sure to turn on usb debugging and oem unlock mode
DgnrtnX said:
When you are booted in twrp, reboot to bootloader of system (obviously). Then press power button when it displays start. Like this the phone will boot into system and not in recovery
Or
Just reboot to bootloader and read the thread attached with it.
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Be sure to turn on usb debugging and oem unlock mode
Click to expand...
Click to collapse
Thank you for your reply DgnrtnX. It matches the successful solution I received from exho92 on 09/01/17. The only issue is that I need to boot via that method each time. I no longer boot directly into my system. However I plan to update to NPJ25.93-14.5 shortly so I'm hoping the reboot issue will go away if that upgrade goes well.
USB debugging and OEM unlock were already enabled and remain so.
I wanted to relock my Mi A1 but forgot to backup the stock boot image. Searched the monthly ROM update thread but it's not there yet.
Anyone got it?
Thanks!
Edit:
My bad, it was June patch (OPM1.171019.019.V9.6.3.0.ODHMIFE)
https://forum.xda-developers.com/mi-a1/how-to/ota-xiaomi-mi-a1-ota-links-t3718542
i need stock boot image for july patch to
I want to update to August but I have already rooted Magisk and I uninstalled it first which happened to be uncommand, because it might boot. img patch has overwritten boot.img default.
for the link above I do not understand why it is so large in size even though the img boot that has been patched is less than 5MB.
please help
nirvanarahadian said:
I want to update to August but I have already rooted Magisk and I uninstalled it first which happened to be uncommand, because it might boot. img patch has overwritten boot.img default.
for the link above I do not understand why it is so large in size even though the img boot that has been patched is less than 5MB.
please help
Click to expand...
Click to collapse
it's the entire rom, not only the boot image, that's why it is so large in size
Done
smsporto said:
it's the entire rom, not only the boot image, that's why it is so large in size
Click to expand...
Click to collapse
Done i downloaded fastboot in here https://forum.xda-developers.com/mi...-ota-links-t3718542/post74828108#post74828108, i download Android 8.1.0 [OPM1.171019.026.V9.6.4.0.ODHMIFE] (fastboot image) and i do flash with cmd boot.img. its work , not uncommand anymore, and i did an experiment with restarting my phone and stock boot img is only temporary and returns uncommand. how to fix it?,is it safe if i immediately update to the latest patch from OTA, the thing that is feared if booting will return like that and i'm confused looking for boot.img for august patch
nirvanarahadian said:
Done i downloaded fastboot in here https://forum.xda-developers.com/mi...ota-links-t3718542/post74828108#post74828108, i download Android 8.1.0 [OPM1.171019.026.V9.6.4.0.ODHMIFE] (fastboot image) and i do flash with cmd boot.img. its work , not uncommand anymore, and i did an experiment with restarting my phone and stock boot img is only temporary and returns uncommand. how to fix it?,is it safe if i immediately update to the latest patch from OTA, the thing that is feared if booting will return like that and i'm confused looking for boot.img for august patch
Click to expand...
Click to collapse
If u are sure that u haven't touched the system partition then u can try to update via OTA. Make sure u flashed and not only booted the downloaded boot.img from V9.6.4.0 ROM. I guess it's better to download the latest version from here:
https://drive.google.com/drive/mobile/folders/1dw87qgRNGxfj7UZduHK91LE6X1Xs7CWL
Then do a clean flash and install the entire ROM with fastboot.
"'*"*"
I've done flashing while on the way and I'm waiting. My cellphone suddenly turns on and it looks like it's doing a factory format. and I just updated it to August. all my data is lost even though the user data has been secured and the flashing process has not finished
Yesterday i flashed stock rom which was released few days back android v8.1 and today i received a notification of update july security patch of size 467.3MB. After downloading it shows an error "installation error" what should i do now....i tried two times no help!!....i was using havoc os with moun kernel...but I've flashed the stock rom then whats the matter... attaching the system information available in setting
Azeemkwow said:
Yesterday i flashed stock rom which was released few days back android v8.1 and today i received a notification of update july security patch of size 467.3MB. After downloading it shows an error "installation error" what should i do now....i tried two times no help!!....i was using havoc os with moun kernel...but I've flashed the stock rom then whats the matter... attaching the system information available in setting
Click to expand...
Click to collapse
That's no is the official fastboot version bro, it's the twrp version converted for install for fastboot, you need use miflash and flash the may path.
My July update was 1.1gb. I am very happy with it.. It is noticeably quicker and the bluetooth battery percentage is very useful.
Azeemkwow said:
Yesterday i flashed stock rom which was released few days back android v8.1 and today i received a notification of update july security patch of size 467.3MB. After downloading it shows an error "installation error" what should i do now....i tried two times no help!!....i was using havoc os with moun kernel...but I've flashed the stock rom then whats the matter... attaching the system information available in setting
Click to expand...
Click to collapse
Reflash this stock ROM (July update) http://bigota.d.miui.com/V9.6.4.0.O...0.ODHMIFE_20180712.0000.00_8.0_735823083f.tgz
Don't forget to remove "oem lock" command from the flashing script file.
Azeemkwow said:
Yesterday i flashed stock rom which was released few days back android v8.1 and today i received a notification of update july security patch of size 467.3MB. After downloading it shows an error "installation error" what should i do now....i tried two times no help!!....i was using havoc os with moun kernel...but I've flashed the stock rom then whats the matter... attaching the system information available in setting
Click to expand...
Click to collapse
Try reflashing stock boot.img. You can easily do it with twrp (flash, flash image, boot). You can extract boot img from here:
https://drive.google.com/drive/folders/1dw87qgRNGxfj7UZduHK91LE6X1Xs7CWL
(Credits: https://forum.xda-developers.com/mi...-ota-links-t3718542/post77093962#post77093962 )
You should download: tissot-T-OPM1.171019.019.V9.6.3.0.ODHMIFE.zip
Disclaimer: I'm not responsible of any bootloop or brick.
_mysiak_ said:
Reflash this stock ROM (July update) http://bigota.d.miui.com/V9.6.4.0.O...0.ODHMIFE_20180712.0000.00_8.0_735823083f.tgz
Don't forget to remove "oem lock" command from the flashing script file.
Click to expand...
Click to collapse
Today i will flash the July update but can you please that where is that "oem lock"?
And is it necessary to clean and lock?
Save user data option is fine or not?
Azeemkwow said:
Today i will flash the July update but can you please that where is that "oem lock"?
And is it necessary to clean and lock?
Save user data option is fine or not?
Click to expand...
Click to collapse
"oem lock" command is in batch script files (.bat), particularly "flash_all_except_storage.bat". If you want to return to stock and lose your data, you can clean and lock. Save user data - I suppose this is in MiFlash app - I don't use it, as it does nothing else than wrap existing bat files in GUI.
Hello everyone
Someone in the russian forum (4pda) shared this patched boot from january ota
I flashed it and the device booted correctly without facing any problem, now magisk works again
Link to download : https://mega.nz/#!R5NAgQKJ!yfm886jSAA_x1raUzxRlq-t53AFjaFvU7Q_AH-fXRlY
Tested and it works. Thanks
help
guyz my adb cant load the patched boot img even when it is in the same folder any help plss
veddeomi said:
guyz my adb cant load the patched boot img even when it is in the same folder any help plss
Click to expand...
Click to collapse
Put the patched boot in adb folder
Reboot your phone into fastboot mode
Then open cmd : fastboot flash boot patched_boot_3.0.img
you can save ur time by using the below toolkit
https://forum.xda-developers.com/mi-a2/development/tool-mi-a2-xtrem-toolkit-t3879660
and just download Magisk from XDA and use the tool to install it using the ADB Sideload.
that is what i did and worked perfectly on Pie after Jan Update.
Does it work with v10.2 ?
Or i must update to v10.3 to flash this patch ?
beny ms said:
Does it work with v10.2 ?
Or i must update to v10.3 to flash this patch ?
Click to expand...
Click to collapse
U have to update first
Abrilabr said:
U have to update first
Click to expand...
Click to collapse
Okay ,thanks mate
i flashed it successfully but i get bootloop. this patch not working my phone
Oline1032 said:
i flashed it successfully but i get bootloop. this patch not working my phone
Click to expand...
Click to collapse
You should unlock your phone's bootloader first
And update to 10.0.3.0
medkim said:
You should unlock your phone's bootloader first
And update to 10.0.3.0
Click to expand...
Click to collapse
dude bootloader is unlocked
Oline1032 said:
dude bootloader is unlocked
Click to expand...
Click to collapse
are you in january patch ?
it's weird, your phone should boot normally, maybe you missed something
i was on 10.0.2.0.PDIMIFJ with unlocked bootloader and patched boot.img. when OTA update is avaiable, i restored boot.img using Magisk and installed the update, then patched boot.img again using Magisk.
After reboot, phone keeps restarting while showing Android One screen.
Then I flashed this patched 10.0.3.0, but phone is stuck at Android One screen (there should be moving color bar)
Now I'm trying to downgrade to 10.0.2.0.PDIMIFJ using MiFlash without erasing user data
Edit: still boot loop at Android One screen after flashing 10.0.2.0.PDIMIFJ without erasing user data. Phone shows the Android recovery screen with error message "can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device"
HRSE said:
i was on 10.0.2.0.PDIMIFJ with unlocked bootloader and patched boot.img. when OTA update is avaiable, i restored boot.img using Magisk and installed the update, then patched boot.img again using Magisk.
After reboot, phone keeps restarting while showing Android One screen.
Then I flashed this patched 10.0.3.0, but phone is stuck at Android One screen (there should be moving color bar)
Now I'm trying to downgrade to 10.0.2.0.PDIMIFJ using MiFlash without erasing user data
Click to expand...
Click to collapse
I have encountered the same problem.
It seems like there is something wrong with the encryption of the phone because I need to format the userdata partition to stop the bootloop.
Fulva said:
I have encountered the same problem.
It seems like there is something wrong with the encryption of the phone because I need to format the userdata partition to stop the bootloop.
Click to expand...
Click to collapse
Good for you that you are still on 10.0.3.0
Now my phone is wiped, and back to 10.0.2.0. I gained nothing and lost too much.
HRSE said:
i was on 10.0.2.0.PDIMIFJ... Edit: still boot loop at Android One screen after flashing 10.0.2.0.PDIMIFJ...
Click to expand...
Click to collapse
My jasmine 6/128 was on 10.0.2.0.PDIMIFJ, unlocked, rooted - Magisk with Modules, /system partition changed, automatic .Updates disabled
Thus, checking for January OTA and seeing that it is ready, I made these steps:
1. downloaded stock 10.0.2.0.PDIMIFJ http://en.miui.com/download-353.html (actually, I made it much earlier);
2. flashed it in fastboot preserving /data (there is "flash_all_except_data.bat" in unpacked ROM directory);
3. rebooted, downloaded OTA 10.0.3.0, installed OTA, rebooted without bootloop;
4. used phone for a while (root gone, all user applications, except for 1 rather specific, working - including Nova, phone calls, SMS, etc, OK);
5. Took patched boot image from 4pda, and booted it into phone in fastboot ("fastboot boot pached_boot.img"); NOTE: not flashed, but booted for safety!
6, As phone was working OK with booted patch, I started Magisk and "installed" it; thus Magisk patched my stock 10.0.3.0 boot in phone, and saved original stock in /data partition.
7. after reboot I had everything restored - Magisk modules and su, root permitions for applications, etc.
P.S. Seems like 10.0.3.0 PDIMIXM OTA is withdrawn by Xiaomi due to numerous bootloops in stock phones.
So if you already updated to this OTA, use these attachments at your own risk, or better wait for 10.0.4.0
Aerobatic said:
My jasmine 6/128 was on 10.0.2.0.PDIMIFJ, unlocked, rooted - Magisk with Modules, /system partition changed, automatic .Updates disabled
Thus, checking for January OTA and seeing that it is ready, I made these steps:
1. downloaded stock 10.0.2.0.PDIMIFJ http://en.miui.com/download-353.html (actually, I made it much earlier);
2. flashed it in fastboot preserving /data (there is "flash_all_except_data.bat" in unpacked ROM directory);
3. rebooted, downloaded OTA 10.0.3.0, installed OTA, rebooted without bootloop;
4. used phone for a while (root gone, all user applications, except for 1 rather specific, working - including Nova, phone calls, SMS, etc, OK);
5. Took patched boot image from 4pda, and booted it into phone in fastboot ("fastboot boot pached_boot.img"); NOTE: not flashed, but booted for safety!
6, As phone was working OK with booted patch, I started Magisk and "installed" it; thus Magisk patched my stock 10.0.3.0 boot in phone, and saved original stock in /data partition.
7. after reboot I had everything restored - Magisk modules and su, root permitions for applications, etc.
Click to expand...
Click to collapse
somehow my phone doesn't show the january OTA update anymore (it was still there a few hours ago!)
Hey guys if i root using patched boot image will i still be able to install updates?
one08 said:
Hey guys if i root using patched boot image will i still be able to install updates?
Click to expand...
Click to collapse
No you should restore stock boot first
one08 said:
Hey guys if i root using patched boot image will i still be able to install updates?
Click to expand...
Click to collapse
Yes you can receive updates, but only if you did not made any changes to system files !