I followed the instructions at:
github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
All went well until I restarted after the update said it was completed. At first i was in a reboot loop, which I eventually was able to break by holding the power button. Now it hangs at the G logo with the little grey progress bar going back and forth perpetually.
I rooted it with the factory image and magisk 14.5 a week or so ago.
What is the best way to proceed?
--Bill
Update:
I switched slots with "fastboot --set-active=a" and that returned to the bootloop. Slot B produced the perpetual progress bar..
I extracted the boot.img from the 8.1.0 (OPM1.171019.011, Dec 2017) image (dl.google.com/dl/android/aosp/walleye-opm1.171019.011-factory-f74dd4fd.zip) and copied it to the device with:
"fastboot flash boot boot.img" and then rebooted with "fastboot reboot"
The phone rebooted just fine, and I thought I was in good shape. I knew I would have lost root, but I was hoping I could just re-root with magisk. No such luck.. It failed to patch the bootloader, and it also failed the security check.
Then I noticed a number of other device driver/hardware type issues... No wifi (would not turn on and detect networks, funky mac address), the fingerprint scanner complained of missing hardware.
You need to flash the whole image and clean this up.
I tried using the OTA and it wouldn't reboot, so I had to factory reset. Rebooted and 8.1 was installed. Went through installing magisk and trying to root. Failed, but was able to install TWRP, so rooted through that. Rebooted and had internal system error, so had to uninstall the manager and sideload the OTA dtbo.img which removed the message. Finally everything running as before, except unable to use Netflix
Sent from my [device_name] using XDA-Developers Legacy app
I did the factory reset as well, but mine went fine. It booted up as 8.1.0 (OPM1.171019.011, Dec 2017). I was able to restore apps and some settings from google's backup, but lots of manual reconfig was required. After I was confident my phone was stable, I attempted to re-root, which also went without incident.
Bootloader remained unlocked, so I just needed to enable developer mode and usb debugging.
In brief:
(pushed and installed) /Download/MagiskManager-v5.4.3.apk
adb push boot.img /sdcard/Download
(patched with magisk 14.5)
adb pull /storage/emulated/0/MagiskManager/patched_boot.img
adb reboot bootloader
fastboot flash boot patched_boot.img
fastboot reboot
I did get the "There's an internal problem with your device" message, but I didn't notice any bad behavior.
Magisk showed all green, SafetyNet check good, etc..
According to this thread: forum.xda-developers.com/pixel-2-xl/how-to/tut-fix-dtbo-message-theres-internal-t3715620, the "internal problem..." message is benign and can be ignored -- or fixed by reverting and preventing the automatic patch of dtbo.img by magisk.
So for now I'm all good (and have better backups ). I'll be considerably more careful about applying the next update.
wmb1001 said:
I did the factory reset as well, but mine went fine. It booted up as 8.1.0 (OPM1.171019.011, Dec 2017). I was able to restore apps and some settings from google's backup, but lots of manual reconfig was required. After I was confident my phone was stable, I attempted to re-root, which also went without incident.
Bootloader remained unlocked, so I just needed to enable developer mode and usb debugging.
In brief:
(pushed and installed) /Download/MagiskManager-v5.4.3.apk
adb push boot.img /sdcard/Download
(patched with magisk 14.5)
adb pull /storage/emulated/0/MagiskManager/patched_boot.img
adb reboot bootloader
fastboot flash boot patched_boot.img
fastboot reboot
I did get the "There's an internal problem with your device" message, but I didn't notice any bad behavior.
Magisk showed all green, SafetyNet check good, etc..
According to this thread: forum.xda-developers.com/pixel-2-xl/how-to/tut-fix-dtbo-message-theres-internal-t3715620, the "internal problem..." message is benign and can be ignored -- or fixed by reverting and preventing the automatic patch of dtbo.img by magisk.
So for now I'm all good (and have better backups ). I'll be considerably more careful about applying the next update.
Click to expand...
Click to collapse
Was this using boot image from the OTA or factory imgae?
Sent from my [device_name] using XDA-Developers Legacy app
gvsukids said:
Was this using boot image from the OTA or factory imgae?
Click to expand...
Click to collapse
The factory image -- both to get it to boot after the OTA update failed and then again wen rooting.
specifically:
walleye-opm1.171019.011-factory-f74dd4fd.zip\walleye-opm1.171019.011\image-walleye-opm1.171019.011.zip\boot.img
wmb1001 said:
The factory image -- both to get it to boot after the OTA update failed and then again wen rooting.
specifically:
walleye-opm1.171019.011-factory-f74dd4fd.zip\walleye-opm1.171019.011\image-walleye-opm1.171019.011.zip\boot.img
Click to expand...
Click to collapse
Does it pass safety check?
Sent from my [device_name] using XDA-Developers Legacy app
gvsukids said:
Does it pass safety check?
Click to expand...
Click to collapse
Yes, it passes the SafetyNet check in Magisk Manager.
It's been 7 days since I came back to stock already and OEM unlocking is still greyed out. Is there any way to force it true so I can relock bootloader? That happened when I first tried to unlock bootloader, but I could allow it in like 4 days
If you wanna know reasons I tried installing Custom ROMs, and on the one successful installation (AOSP Extended) it's bugged so I returned to stock and kept on trying to install CrDroid, but one day it just stopped recognizing SIMs. (After some time on stock being able to)
・It can't be a number block, since it still works on another Custom ROM+Magisk Phone
・And I'm not sure if an IMEI block would mess with a SIM from another carrier that's never touched a rooted phone. (I tested both SIMs on both slots)
・That same SIM (my original one) stopped working on an unrooted G7 Play too
・Also I can't check any of my 2 IMEIs on settings, though I could retrieve IMEI1 through "fastboot getvar all"
Hyoretsu said:
It's been 7 days since I came back to stock already and OEM unlocking is still greyed out. Is there any way to force it true so I can relock bootloader? That happened when I first tried to unlock bootloader, but I could allow it in like 4 days
If you wanna know reasons I tried installing Custom ROMs, and on the one successful installation (AOSP Extended) it's bugged so I returned to stock and kept on trying to install CrDroid, but one day it just stopped recognizing SIMs. (After some time on stock being able to)
・It can't be a number block, since it still works on another Custom ROM+Magisk Phone
・And I'm not sure if an IMEI block would mess with a SIM from another carrier that's never touched a rooted phone. (I tested both SIMs on both slots)
・That same SIM (my original one) stopped working on an unrooted G7 Play too
・Also I can't check any of my 2 IMEIs on settings, though I could retrieve IMEI1 through "fastboot getvar all"
Click to expand...
Click to collapse
What does getvar all say are the codename and software channel?
Sent from my perry_f using XDA Labs
sd_shadow said:
What does getvar all say are the codename and software channel?
Sent from my perry_f using XDA Labs
Click to expand...
Click to collapse
I didn't find those specifically, but it's ocean XT1955-1 and RETBR (product/board and sku, and ro.carrier) Tried reflashing NHLOS.bin, erasing modem and flashing FSG today, didn't work and I never ran "fastboot erase all" too (by not working I mean the phone doesn't recognize a SIM is in the tray, I don't even have the emergency calls only message)
Re-flashed stock around 4 times a week ago or so, the only thing I didn't do was relock bootloader since I'm unable to
Here's the full output of getvar all if needed. (that's not the actual IMEI that's output'd) Also between those tries I sometimes could get device ID to show up instead of bad key, no idea why though
Brazil also has a site from ANATEL, the organization that manages product quality, authenticity, restrictions, user things and such, (All devices need to pass through a check from them) that allows us to see if IMEI has any restrictions (It shows if the IMEI is blocked, at least "Informed IMEI is banned by loss or theft" on a video I saw), mine has "Until now, the IMEI has no restrictions on use"
Hyoretsu said:
I didn't find those specifically, but it's ocean XT1955-1 and RETBR (product/board and sku, and ro.carrier) Tried reflashing NHLOS.bin, erasing modem and flashing FSG today, didn't work and I never ran "fastboot erase all" too (by not working I mean the phone doesn't recognize a SIM is in the tray, I don't even have the emergency calls only message)
Re-flashed stock around 4 times a week ago or so, the only thing I didn't do was relock bootloader since I'm unable to
Here's the full output of getvar all if needed. (that's not the actual IMEI that's output'd) Also between those tries I sometimes could get device ID to show up instead of bad key, no idea why though
Brazil also has a site from ANATEL, the organization that manages product quality, authenticity, restrictions, user things and such, (All devices need to pass through a check from them) that allows us to see if IMEI has any restrictions (It shows if the IMEI is blocked, at least "Informed IMEI is banned by loss or theft" on a video I saw), mine has "Until now, the IMEI has no restrictions on use"
Click to expand...
Click to collapse
Did you check the flashfile.xml
For the official flash commands?
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
Did you check the flashfile.xml
For the official flash commands?
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
https://pastebin.com/X5TD77YS As far as I remember (just downloaded firmware file on phone) they're the same from the eraseandupdate.bat I was using
EDIT: Yeah, aside from it erasing modemst1 and modemst2 after flashing everything as opposed to after flashing FSG and reflashing FSG after that it's the same commands
Hyoretsu said:
OEM unlocking is still greyed out.
Click to expand...
Click to collapse
OEM unlock toggle is greyed out as long as your bootloader is unlocked, Magisk is not installed and you run the stock rom. That's quite normal. You must relock the bootloader to activate it. On my Moto g6 plus you find an info text there that this option is deactivated because the bootloader is already unlocked.
WoKoschekk said:
OEM unlock toggle is greyed out as long as your bootloader is unlocked, Magisk is not installed and you run the stock rom. That's quite normal. You must relock the bootloader to activate it. On my Moto g6 plus you find an info text there that this option is deactivated because the bootloader is already unlocked.
Click to expand...
Click to collapse
Though all my attempts at installing only Magisk lead to a bootloop and Custom ROMs either didn't work or I spent multiple days trying to install, only being successful once. I tried relocking the bootloader, but it says I gotta check that option to do it (mine says it's already unlocked too)
Hyoretsu said:
Though all my attempts at installing only Magisk lead to a bootloop and Custom ROMs either didn't work or I spent multiple days trying to install, only being successful once. I tried relocking the bootloader, but it says I gotta check that option to do it (mine says it's already unlocked too)
Click to expand...
Click to collapse
Usually that error is caused from using the wrong relocking commands
Are you using
Code:
fastboot oem lock begin
fastboot oem lock begin
fastboot oem lock
fastboot oem lock
fastboot oem lock
fastboot flash boot boot.img
fastboot oem lock
And mine is greyed out too
Hyoretsu said:
Though all my attempts at installing only Magisk lead to a bootloop and Custom ROMs either didn't work or I spent multiple days trying to install, only being successful once. I tried relocking the bootloader, but it says I gotta check that option to do it (mine says it's already unlocked too)
Click to expand...
Click to collapse
Did you try to install Magisk via TWRP? Maybe older versions will work like v19.3... On my Moto g6 v20.3 leads to a bootloop, too. But v19.3 runs without any problems. Maybe it's worth a try.
I red that it's necessary to run the oem lock command a few times to make it work.
sd_shadow said:
Usually that error is caused from using the wrong relocking commands
Are you using
Code:
fastboot oem lock begin
fastboot oem lock begin
fastboot oem lock
fastboot oem lock
fastboot oem lock
fastboot flash boot boot.img
fastboot oem lock
Click to expand...
Click to collapse
I actually thought this was it, but no, I was using this thread, which has the same commands, and still got the error (2x, then 3x, reflash boot.img and oem lock)
WoKoschekk said:
Did you try to install Magisk via TWRP? Maybe older versions will work like v19.3... On my Moto g6 v20.3 leads to a bootloop, too. But v19.3 runs without any problems. Maybe it's worth a try.
Click to expand...
Click to collapse
Installing Magisk on TWRP bootable, since installing TWRP would bootloop too. Didn't try older versions though, but I might try re-writing my IMEI first, who knows if that'll work. Being able to successfully relock bootloader without a working SIM wouldn't do much good, since I'd have to format the phone to try anything afterwards.
Hyoretsu said:
I actually thought this was it, but no, I was using this thread, which has the same commands, and still got the error (2x, then 3x, reflash boot.img and oem lock)
Installing Magisk on TWRP bootable, since installing TWRP would bootloop too. Didn't try older versions though, but I might try re-writing my IMEI first, who knows if that'll work. Being able to successfully relock bootloader without a working SIM wouldn't do much good, since I'd have to format the phone to try anything afterwards.
Click to expand...
Click to collapse
Did you try to install TWRP with the .zip provided by twrp.me? This .zip flashes the ramdisk inside the boot.img as Magisk does. So first you must install TWRP and after that you must install Magisk. Ignoring this order causes a bootloop because the twrp.zip overwrites Magisk! The twrp.zip flashes a complete new ramdisk while Magisk patches only some parts of it.
I loose my IMEI on my Moto g6 plus, too. You won't be able to overwrite it because it is linked with your device and encrypted by Motorola. The location of these files is /persist/rfs.
If your IMEI is broken or corrupt you won't be able to restore it. Except you have a backup of your persist partition.
---------- Post added at 09:31 PM ---------- Previous post was at 09:25 PM ----------
Try to relock your bootloader with the command provided in the screenshot (source: https://source.android.com/setup/build/running)
Screenshot
https://ibb.co/f2LzMzS
WoKoschekk said:
Did you try to install TWRP with the .zip provided by twrp.me? This .zip flashes the ramdisk inside the boot.img as Magisk does. So first you must install TWRP and after that you must install Magisk. Ignoring this order causes a bootloop because the twrp.zip overwrites Magisk! The twrp.zip flashes a complete new ramdisk while Magisk patches only some parts of it.
Click to expand...
Click to collapse
I get a bootloop when I install TWRP alone and when I install Magisk from bootable TWRP, been using the official one from twrp.me this whole time since the screen is bugged on unofficial one. I only ever installed both (in that order) when I was still trying to install Custom ROMs, but I kept getting bootloops for other reasons.
Do t even use twrp. Just install Magisk Manager and then patch a copy of the boot image from the firmware you installed.
So install Magisk Manager
Copy the boot image from the firmware that you installed to your phone.
Run Magisk Manager, click update Magisk and Select patch boot.img
Navigate to the folder on you phone that you copied the boot image to
Wait until Magisk Manager patches it
Copy Patched_boot.img to your adb folder on your PC
From your PC command prompt:
adb reboot bootloader
Then
fastboot devices
If your phone serial # shows, then:
fastboot flash boot patched_boot.img
fastboot reboot
You should now have root and the unlock bootloader option in developer settings will not be greyed out.
There is another thread with these same instructions. That is what allowed me to relock my bootloader.
Sent from my moto g(7) power using Tapatalk
Also,
Now that you are able to relock your bootloader, you could hold off until 10 is out.
If you don't like the unlocked bootloader message on startup, flash the attached logo.img fileView attachment BootLogo_mg7p.zip
Sent from my moto g(7) power using Tapatalk
MrCamby said:
Do t even use twrp. Just install Magisk Manager and then patch a copy of the boot image from the firmware you installed.
So install Magisk Manager
Copy the boot image from the firmware that you installed to your phone.
Run Magisk Manager, click update Magisk and Select patch boot.img
Navigate to the folder on you phone that you copied the boot image to
Wait until Magisk Manager patches it
Copy Patched_boot.img to your adb folder on your PC
From your PC command prompt:
adb reboot bootloader
Then
fastboot devices
If your phone serial # shows, then:
fastboot flash boot patched_boot.img
fastboot reboot
You should now have root and the unlock bootloader option in developer settings will not be greyed out.
There is another thread with these same instructions. That is what allowed me to relock my bootloader.
Sent from my moto g(7) power using Tapatalk
Click to expand...
Click to collapse
Ty, this was the only way in which I could get root in stock. Although the Allow OEM Unlock is still greyed out it now has the same message as before I unlocked the bootloader for the first time, though if it acts the same way it'll be available in a few days. IMEIs and SIMs still aren't working though, but eh. At least I can try testing the locking bootloader theory to get them working again (IMEI not working = can't even see any of them in settings)
MrCamby said:
Also, now that you are able to relock your bootloader, you could hold off until 10 is out.
Click to expand...
Click to collapse
Also Motorola still allows unlocked users to receive OTA for some reason, my device updated and it's still working
To repair your IMEI on a G7 power, this is what worked for me:
Remove your sim card.
Pull NON-HLOS.bin and fsg.mbn from the firmware that was flashed on the phone.
Startup in bootloader mode:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Reboot phone. Once it is back up, powerdown, put sim card back in and start back up.
Sent from my moto g(7) power using Tapatalk
MrCamby said:
To repair your IMEI on a G7 power, this is what worked for me:
Remove your sim card.
Pull NON-HLOS.bin and fsg.mbn from the firmware that was flashed on the phone.
Startup in bootloader mode:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Reboot phone. Once it is back up, powerdown, put sim card back in and start back up.
Click to expand...
Click to collapse
No luck unfortunately, still don't have IMEI/SIM. Once I can I'll try relocking bootloader and maybe sending it to warranty, since apparently using a tool to re-write IMEI won't work on this phone. (Followed to the T, unless unlocking it after flashing and waiting for microSD messes it up)
Did you try the LMSA software to try and fix it. There are two options: update and repair.
Sent from my moto g(7) power using Tapatalk
MrCamby said:
Did you try the LMSA software to try and fix it. There are two options: update and repair.
Click to expand...
Click to collapse
I tried using it back when I was trying to go back to stock "the right way" (to try and solve the lost IMEI, go back stock and re-lock bootloader) but it couldn't even recognize my phone so that I could download anything
hi guys,
my op6 is running stock oos with magisk as root. My phone worked fine for several months. Today I tried switching magisk from the stable version to canary by first upgrading the manager app and then hitting the direct install option. This failed several times and I got an error saying:
! Unable to unpack boot image
I thought this could be fixed by a reboot, but well... it wasn't. Now the phone only boots into the bootloader. I booted into twrp and tried to uninstall magisk via the uninstall.zip. This fails with error
-Unpacking boot image
! Unsupported/Unknown image format
- Unmounting partitions
cd /tmp/repackorig/ && /sbin/magiskboot unpack -h '/tmp/repackorig/boot.img' process ended with ERROR: 1
Error unpacking image
I don't really know what this means. I'm guessing my boot.img is corrupted?
Is there any way I can solve this problem without a factory reset? Can I just flash the stock boot.img via fastboot?
Do you have any idea what went wrong here, so that I can avoid the error next time?
Yesterday I broke op5 during the magisk update. The repair was simple, flash stock boot.img as boot partition.
I flashed it from TWRP.
Try dirty flashing your ROM without flashing magisk.
I'm also facing the same issues. Tried updating from the Magisk App. Didn't receive any error messages. After reboot I'm stuck in fastboot mode and I cannot access recovery. I do not have a backup of the data on this phone.
Is there any way I can still (temporarily) access the data? I'm panicking a little bit. My OOS is stock and rooted and hasn't been updated in about a year. I'm not sure if I can still figure out the specific OOS version that is installed.
EDIT:
Have been trying to flash the stock boot.img with fastboot. I've tried both 10.0.1 and 10.3.0 so far. Both resulted in the "BOOTLOADER UNLOCKED" warning and got stuck there. 10.3.1 is my last option, because I don't think I've updated this device since. Would it make a difference if I tried to do it from twrp?
EDIT2:
I do however have access to the recovery mode now. If I'm not mistaken this means I might be able to extract the data.
EDIT3:
The recovery mode is not asking me for my unlock pattern (which I think it should be doing) and is not showing up under 'adb devices'. I've tried flashing the boot.img of all OOS versions I can think of with fastboot, nothing will let me boot back in or let me access adb through the recovery. Am I ****ed?
MoresM said:
I'm also facing the same issues. Tried updating from the Magisk App. Didn't receive any error messages. After reboot I'm stuck in fastboot mode and I cannot access recovery. I do not have a backup of the data on this phone.
Is there any way I can still (temporarily) access the data? I'm panicking a little bit. My OOS is stock and rooted and hasn't been updated in about a year. I'm not sure if I can still figure out the specific OOS version that is installed.
EDIT:
Have been trying to flash the stock boot.img with fastboot. I've tried both 10.0.1 and 10.3.0 so far. Both resulted in the "BOOTLOADER UNLOCKED" warning and got stuck there. 10.3.1 is my last option, because I don't think I've updated this device since. Would it make a difference if I tried to do it from twrp?
EDIT2:
I do however have access to the recovery mode now. If I'm not mistaken this means I might be able to extract the data.
EDIT3:
The recovery mode is not asking me for my unlock pattern (which I think it should be doing) and is not showing up under 'adb devices'. I've tried flashing the boot.img of all OOS versions I can think of with fastboot, nothing will let me boot back in or let me access adb through the recovery. Am I ****ed?
Click to expand...
Click to collapse
Maybe it's worth trying change the slot and see if it will start? Of course from the fastboot level.
MoresM said:
I'm also facing the same issues. Tried updating from the Magisk App. Didn't receive any error messages. After reboot I'm stuck in fastboot mode and I cannot access recovery. I do not have a backup of the data on this phone.
Click to expand...
Click to collapse
I managed to fix it as well by flashing the stock boot.img for my software version to both slot_a and slot_b using fastboot. I left the active slot setting alone otherwise.
Afterwards I booted into twrp through fastboot and installed blu spark twrp and magisk 21.4 from there as a user suggested on the Magisk github: https://github.com/topjohnwu/Magisk/issues/3924
Note that github link also has a solution to flawlessly upgrade to latest Magisk without data loss but I haven't had the time to look at it.
I just bought this 8T (KB2005) and applied the latest OTA update and it seems not to have a Recovery installed. Is that possible? I have unlocked the bootloader.
If I try to boot into Recovery it gives me a screen that asks if I want to reboot into recovery or fastboot. If I choose recovery, it will reboot back to exactly the same place I just came from.
It will boot to fastboot if I choose it. Also the key combo with power off will take me to fastboot. From adb it will reboot to the same screen I mentioned above asking me to choose recovery or fastboot,
I am coming from a OP One that I bought new in 2015. It has TWRP, is rooted and running the latest LineageOS 18.1 nightly. I was not expecting to find no recovery for th 8T. It does not have the usual recovery basic options anywhere?
What am I missing here?
Slot B is active so I assume slot A had the original OEM OOS and the update went to slot B and it is now active. Is there any way to determine what is in the inactive slot?
zzjea said:
I just bought this 8T (KB2005) and applied the latest OTA update and it seems not to have a Recovery installed. Is that possible? I have unlocked the bootloader.
If I try to boot into Recovery it gives me a screen that asks if I want to reboot into recovery or fastboot. If I choose recovery, it will reboot back to exactly the same place I just came from.
It will boot to fastboot if I choose it. Also the key combo with power off will take me to fastboot. From adb it will reboot to the same screen I mentioned above asking me to choose recovery or fastboot,
I am coming from a OP One that I bought new in 2015. It has TWRP, is rooted and running the latest LineageOS 18.1 nightly. I was not expecting to find no recovery for th 8T. It does not have the usual recovery basic options anywhere?
What am I missing here?
Slot B is active so I assume slot A had the original OEM OOS and the update went to slot B and it is now active. Is there any way to determine what is in the inactive slot?
Click to expand...
Click to collapse
The OOS recovery it's basically useless and LineageOS is only marginally better (it allows ADB) but nothing like TWRP. There's no TWRP (yet) for the 8T.
You can find out the active slot by looking at getprop ro.boot.slot_suffix or, if you're in the bootloader by fastboot getvar current-slot.