For anyone who get boot loop, missing wifi, root lost after January boot image patch, here solution for that.
I did the following steps and did not find any problems with my MI A1 until now.
- You must reflashing rom again with xiaomi flash tools, and must choice clean flashing and lock, remember your data will be wipe.
here's link download N2G47H.7.12.29 (Android O) 1084 MB (28 Desember 2017 Patch) ;
http://bigota.d.miui.com/7.12.29/tis...c9a6ea979b.tgz Update : Miui was delete this rom
- After flash finished, wait to update January security patch from OTA, then update until finish and restart your device.
you must see your firmware now is OPR1.170623.026.8.1.10 with 01 Jan 2018 security patch
- Install latest version of magisk manager , you can get it at official magisk page, if finished reboot your device to fastboot mode.
- Now you can unlock you device and root with patched_boot.img as explained earlier in this thread :
https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654
- After restart, open magisk manager, install with direct install then reboot your device.
Now you have root and to prove root is not lost after reboot, you can try to reboot your devices several times.
Related
UPDATE: SOLVED! Flash snoke R10 kernel in TWRP, reboot back into TWRP, flash Magisk 15.2 zip. Had to do this as manually attempting to patch system.img wasn't working.
I was successfully unlocked and rooted on the November 8.0 factory image. I have a Pixel 2 directly from Google and using it on Verizon.
I just wiped and went clean to the latest Jan 2018 factory image.
I grabbed the latest Magisk, 5.5.2, and installed the apk. So far so good.
Magisk opens fine, and I've tried changing the update stream to Beta. I have the system.img to patch on my sdcard. Whenever I tell Magisk to patch the image, it looks like it processes for a bit. But then Magisk crashes. I've repeated this several times and have even tried rebooting. No go.
Any ideas? My understanding is that you don't *need* snoke kernel. I'm not sure if with the latest images you must do this in TWRP. For the November update I didn't need to go into TWRP at all. You'd simply patch system.img, boot into fastboot and fastboot flash boot <image_name>
You may try to install Magisk without having a manual patch and let it do everything on it's own. I updated to the Jan patch, reflashed TWRP, custom kernel, booted normally. Uninstalled old Magisk Manager, reinstall magisk manager (latest) and allow it to do whatever it needs with the automatic methods and I didn't have any issues after that.
Update. I got it working. Flashed Snoke 10 kernel in TWRP. Then rebooted back into TWRP and flashed the Magisk 15.2 zip. All good
Friday I have received the official 9.0.0 Pie update. I have started the download and install process and go to sleep.
The next morning day - 4AM, the view 10 was on the EMUI recovery screen (wipe, shutdown, reboot,...). I choosed shutdown because it was 4AM.
At 9AM, booting the device and it is not booting anyway, just the black screen "your device is booting now" and after some minutes the emui recovery screen.
- I have wipe factory reset
- Tried to install the official 9.0.0 Pie update or 8.0.0-432-141 update : FAILURE
- Installed TWRP and restore old twrp backup: no android boot
- Flash old/new SYSTEM.IMG via TWRP: no android boot
- Tried eRecovery download: DOWNLOAD PACKAGE INFO FAILED
- Use HiSuite in fastboot mode : FAILURE
- Tried the dload process with update.zip/UPDATE.APP : SOFTWARE installation FAILED
Weird thing, the official Pie update does not have RAMDISK.IMG.
And if I tried to restore Official 8.0.0 C432 141, I can flash recovery_ramdisk, kernel and system but failed on RAMDISK due to error partition length.
I cannot flash any ramdisk.
Any ideas? (My bootloader is unlocked, I can flash and boot TWRP, boot erecovery...)
elfabio said:
Friday I have received the official 9.0.0 Pie update. I have started the download and install process and go to sleep.
The next morning day - 4AM, the view 10 was on the EMUI recovery screen (wipe, shutdown, reboot,...). I choosed shutdown because it was 4AM.
At 9AM, booting the device and it is not booting anyway, just the black screen "your device is booting now" and after some minutes the emui recovery screen.
- I have wipe factory reset
- Tried to install the official 9.0.0 Pie update or 8.0.0-432-141 update : FAILURE
- Installed TWRP and restore old twrp backup: no android boot
- Flash old/new SYSTEM.IMG via TWRP: no android boot
- Tried eRecovery download: DOWNLOAD PACKAGE INFO FAILED
- Use HiSuite in fastboot mode : FAILURE
- Tried the dload process with update.zip/UPDATE.APP : SOFTWARE installation FAILED
Weird thing, the official Pie update does not have RAMDISK.IMG.
And if I tried to restore Official 8.0.0 C432 141, I can flash recovery_ramdisk, kernel and system but failed on RAMDISK due to error partition length.
I cannot flash any ramdisk.
Any ideas? (My bootloader is unlocked, I can flash and boot TWRP, boot erecovery...)
Click to expand...
Click to collapse
Hey, how is twrp working for you on pie? I have been searching for ways to root my device after the pie update.
ankan1993 said:
Hey, how is twrp working for you on pie? I have been searching for ways to root my device after the pie update.
Click to expand...
Click to collapse
Solved my issue using https://forum.xda-developers.com/showpost.php?p=78662167&postcount=13
SYSTEM.img, RECOVERY_RAMDIS.img from this update.
My device was booting again but with a software loop on Google Assistant wizard.
I'm booting to erecovery which working this time to recover from the full update (same as link but applied via erecovery)
I'm not ready to apply another flash.
Too waste time this last few days to recover my device
Try edl flash
Flashing magisk patched boot img to gain root access isn't working on OxygenOS 9.5.6. After flashing magisk patched boot and rebooting to the system, the message" Your phone was restarted and needs to be unlocked" is shown on the lock screen and the system restarts immediately. Then the lock screen password is requested and then goes to OnePlus recovery. If I reboot from the recovery to the system, the message mentioned above is shown and reboot to the recovery again. How can I fix the issue without wiping any data?
Is the patched boot img from 9.5.6 ?
Yes. I extracted it from OTA zip and patched it via Magisk.
Have you tried this or this? Still waiting for 9.5.6 to land.
moi123 said:
Have you tried this or this? Still waiting for 9.5.6 to land.
Click to expand...
Click to collapse
EDIT : Tried getting the OTA thru Oxygen Updater and applying via System > Updates. However, the update always fails at 11%. Anyone experienced this?
EDIT2 : The 9.5.6 incremental OTA is ~120MB, however Oxygen Updater says that if the phone is rooted then it only supports a FULL update (~2GB). Is this the problem? Can I still do the incremental OTA update despite being rooted, as per this post ?
YeHtetAg.92 said:
Flashing magisk patched boot img to gain root access isn't working on OxygenOS 9.5.6. After flashing magisk patched boot and rebooting to the system, the message" Your phone was restarted and needs to be unlocked" is shown on the lock screen and the system restarts immediately. Then the lock screen password is requested and then goes to OnePlus recovery. If I reboot from the recovery to the system, the message mentioned above is shown and reboot to the recovery again. How can I fix the issue without wiping any data?
Click to expand...
Click to collapse
These would be the basic steps to install magisk:
1. Boot to fastboot
2. Boot to twrp (get it from the official twrp page)
Code:
fastboot boot recoveryname.img
3. Flash twrp installer (it'll be a zip, you can find it in the twrp official page)
4. Reboot to recovery (twrp)
5. Flash Magisk
But since you effed up with the patched boot image, perform upto steps 4, then
5. Flash OOS (latest or whichever you like)
6. Flash twrp installer
7. Reboot to recovery (twrp)
8. Flash Magisk
9. Reboot to system
10. Profit.
---------- Post added at 03:27 PM ---------- Previous post was at 03:23 PM ----------
moi123 said:
EDIT : Tried getting the OTA thru Oxygen Updater and applying via System > Updates. However, the update always fails at 11%. Anyone experienced this?
EDIT2 : The 9.5.6 incremental OTA is ~120MB, however Oxygen Updater says that if the phone is rooted then it only supports a FULL update (~2GB). Is this the problem? Can I still do the incremental OTA update despite being rooted, as per this post ?
Click to expand...
Click to collapse
Just download the full rom and flash it using twrp. Without rebooting, flash twrp installer so as to keep twrp. Now reboot to twrp, flash magisk. And then reboot to system. Voila!
dewri21 said:
Just download the full rom and flash it using twrp. Without rebooting, flash twrp installer so as to keep twrp. Now reboot to twrp, flash magisk. And then reboot to system. Voila!
Click to expand...
Click to collapse
Thanks! Will try!
Got it. On OOS 9.5.5, I used a magisk module "OOS native call recorder" and may be it blocks the OOS booting into system ui. Now I factory reset my 1+7 and root successfully via patched boot.
After I'd upgrade to beta 25, I can't install Magisk. Any ideas how can I get my root back?
rrubio999 said:
After I'd upgrade to beta 25, I can't install Magisk. Any ideas how can I get my root back?
Click to expand...
Click to collapse
I'm also facing the same issues. Whenever I install Magisk,phone boots into recovery and will only boot into system when I flash the Magisk uninstaller.
Same thing happens when I flash the patched boot image via fastboot.
Edit: Did a fresh OB25 install via TWRP followed by Magisk 19.3. System booted up smoothly
I have also faced this issue
1.install twrp
2.flash ob25 again & twrp.zip
3.reboot to twrp again & install magisk then reboot to system May be there are some changes in os because of upcoming Q update
Hi all,
update: I made update at the end.
My OP7 version is GM1900, so far I was on build 10.0.6GM57BA with Magisk 20.4, but for some time I had 10.0.8 update notification.
Today I decided to update build.
I consider myself as medium experienced user the type that is using rather step by step guides.
But this time I thought I don't need guide cause I should remember how I did update last time. In the meantime I help my son to make homework what was an additional distraction.
I always download full OTA from oneplus.com support but it turned out there was no 10.0.8 (instead there was/is 10.0.7). So I tried to search for 10.0.8 and I found this xda news. As there is a mess with versions and links and I was doing it on mobile Chrome I accidentally tapped Global/India Full OTA
Steps I made:
1.1. Downloading file OnePlus7Oxygen_14.P.29_OTA_029_all_2009152124_ba2424a.zip
1.2. Downloading official TWRP twrp-installer-3.4.0-0-guacamole.zip
1.3. Boot into TWRP.
1.4. Flash twrp-installer-3.4.0-0-guacamole.zip
1.5. Restart to TWRP
1.6. Flash magisk uninstall
1.7. Flash 10.3.5 (India & Global) - OnePlus7Oxygen_14.P.29_OTA_029_all_2009152124_ba2424a.zip
1.8. Flash magisk 20.1 (but forgot to reboot after flashing TWRP it was first mistake I think)
1.9. Ended with 10.3.5 (India & Global) build with stock recovery and without Magisk.
Next I tried to return to GM57BA.
Then the steps I made:
2.1. Downloading official build 10.0.7.GM57BA from oneplus support site.
2.2. Downloading Mauronofrio's TWRP twrp-3.4.0-0-guacamole-unified-Q-mauronofrio.img and twrp-3.4.0-0-guacamole-unified-installer-mauronofrio.zip
2.3. Boot OP7 into fastboot then command "fastboot boot twrp-3.4.0-0-guacamole-unified-Q-mauronofrio.img"
2.4. After phone booted into TWRP I flashed twrp-3.4.0-0-guacamole-unified-installer-mauronofrio.zip
2.5. Restart to TWRP
2.6. Flashed magisk uninstall.
2.7. Flashed 10.0.7.GM57BA
2.8. Flashed magisk 20.4
2.9. Only then I rebooted to TWRP (I think it was mistake).
2.10. Then I saw first problem - there was no lockscreen security with TWRP (unlock pattern).
2.11. Restarted to TWRP again - the same no unlock pattern screen, no access to data partition
2.12. I started to panic and restarted into system.
2.13. I ended with hard bootloop - I mean I can't even do force reset (force reboot) by pressing and holding the Power and Volume down buttons at the same time :crying:
I'm sorry for this long description but I thought it will be helpful to diagnose what I messed up.
Questions and my thoughts:
1. Did I messed up by not restarting after last magisk flash?
2. What to do now? Do I need to wait for battery discharge? Then unbrick using MSM tool?
3. Is there any chance to repair and preserve personal data? I have TWRP backup about 3 months old. Maybe after battery discharge I should go to TWRP and then sideload this backup? Maybe magisk uninstall or stock boot image flash?
Please help
Update:
After battery discharge I managed to boot into TWRP recovery (Mauronofrio's 3.4.0.0)
Then couldn't access /data
But when I switched to Slot B and reboot to recovery situation is back to normal (I guess).
I'm still in recovery scared to boot into system.
What to do now?
kold11 said:
Hi all,
update: I made update at the end.
My OP7 version is GM1900, so far I was on build 10.0.6GM57BA with Magisk 20.4, but for some time I had 10.0.8 update notification.
Today I decided to update build.
I consider myself as medium experienced user the type that is using rather step by step guides.
But this time I thought I don't need guide cause I should remember how I did update last time. In the meantime I help my son to make homework what was an additional distraction.
I always download full OTA from oneplus.com support but it turned out there was no 10.0.8 (instead there was/is 10.0.7). So I tried to search for 10.0.8 and I found this xda news. As there is a mess with versions and links and I was doing it on mobile Chrome I accidentally tapped Global/India Full OTA
Steps I made:
1.1. Downloading file OnePlus7Oxygen_14.P.29_OTA_029_all_2009152124_ba2424a.zip
1.2. Downloading official TWRP twrp-installer-3.4.0-0-guacamole.zip
1.3. Boot into TWRP.
1.4. Flash twrp-installer-3.4.0-0-guacamole.zip
1.5. Restart to TWRP
1.6. Flash magisk uninstall
1.7. Flash 10.3.5 (India & Global) - OnePlus7Oxygen_14.P.29_OTA_029_all_2009152124_ba2424a.zip
1.8. Flash magisk 20.1 (but forgot to reboot after flashing TWRP it was first mistake I think)
1.9. Ended with 10.3.5 (India & Global) build with stock recovery and without Magisk.
Next I tried to return to GM57BA.
Then the steps I made:
2.1. Downloading official build 10.0.7.GM57BA from oneplus support site.
2.2. Downloading Mauronofrio's TWRP twrp-3.4.0-0-guacamole-unified-Q-mauronofrio.img and twrp-3.4.0-0-guacamole-unified-installer-mauronofrio.zip
2.3. Boot OP7 into fastboot then command "fastboot boot twrp-3.4.0-0-guacamole-unified-Q-mauronofrio.img"
2.4. After phone booted into TWRP I flashed twrp-3.4.0-0-guacamole-unified-installer-mauronofrio.zip
2.5. Restart to TWRP
2.6. Flashed magisk uninstall.
2.7. Flashed 10.0.7.GM57BA
2.8. Flashed magisk 20.4
2.9. Only then I rebooted to TWRP (I think it was mistake).
2.10. Then I saw first problem - there was no lockscreen security with TWRP (unlock pattern).
2.11. Restarted to TWRP again - the same no unlock pattern screen, no access to data partition
2.12. I started to panic and restarted into system.
2.13. I ended with hard bootloop - I mean I can't even do force reset (force reboot) by pressing and holding the Power and Volume down buttons at the same time :crying:
I'm sorry for this long description but I thought it will be helpful to diagnose what I messed up.
Questions and my thoughts:
1. Did I messed up by not restarting after last magisk flash?
2. What to do now? Do I need to wait for battery discharge? Then unbrick using MSM tool?
3. Is there any chance to repair and preserve personal data? I have TWRP backup about 3 months old. Maybe after battery discharge I should go to TWRP and then sideload this backup? Maybe magisk uninstall or stock boot image flash?
Please help
Update:
After battery discharge I managed to boot into TWRP recovery (Mauronofrio's 3.4.0.0)
Then couldn't access /data
But when I switched to Slot B and reboot to recovery situation is back to normal (I guess).
I'm still in recovery scared to boot into system.
What to do now?
Click to expand...
Click to collapse
To force restart I need to use power button and both volume keys..
To keep TWRP you need to flash rom, then without restart flash TWRP again, then restart TWRP, then flash Magisk.
Likely the r reason why your system doesn't boot is because it can't decrypt your data.
Why this happens I don't know, maybe in the upgrade they changed something related to the exception and then by downgrading again it isn't able to read it anymore.
I would suggest to:
Flash the latest rom.
Flash TWRP
Reboot TWRP
If TWRP then doesn't ask for PIN or password, then I'm afraid you have lost your data. I hope you have a backup.
I'm that case format (not just clear) data -> yes
Reboot TWRP
Then flash Magisk.
Thanks for reply.
Like I wrote in update after changing slot to b I managed to run TWRP with decrypted data, made even new new backup.
I also restarted into system and it occurs I'm still 10.3.5 (India & Global) GM57AA, so everything I flashed in with build 10.0.7.GM57BA was unsuccessful.
I think I messed with changing inactive slot procedure. Noob mistake I need to read about it.
kold11 said:
Thanks for reply.
Like I wrote in update after changing slot to b I managed to run TWRP with decrypted data, made even new new backup.
I also restarted into system and it occurs I'm still 10.3.5 (India & Global) GM57AA, so everything I flashed in with build 10.0.7.GM57BA was unsuccessful.
I think I messed with changing inactive slot procedure. Noob mistake I need to read about it.
Click to expand...
Click to collapse
I would suggest do restore your device with msm unbrick tool.
1. From recovery, turn off (i noticed, that when tried to turn off from somewhere else, the device would auto reboot later in downlaod mode)
2. In windows, turn off the connection & open device manager: Get this driver http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab
3. Press volume/down + volume/up, after about 5s connect to pc
4. Your device should show up in device manager, open it and install the driver manuell from step 2 (keep device options open... if fail you need to uninstall the driver before trying again)
5. Now wait for about 40s, if your device stays in download mode, you can open & start the msm tool (leave the options in msm as they are)
6. It will take about 280s, then the device will reboot.... (its normal that it stays longer at the oneplus logo at first start)
MSM Thread: https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325
I've also uploaded the 10.0.5OOS Unbrick tool on mega, because android file hosted downloads are so terrible: https://mega.nz/file/ArZFkYpS#Z_rOIwZeYN27IG6L8rOi-yfw8wXGiwvK-uWVDlsmvTI