I installed magisk on my tablet and after tablet restarted, it got stuck on this recovery screen. Reboot system now gets you back on this screen. Rebooting to bootloader gets you stuck on logo screen. Factory reset did nothing as well. Does anyone have any ideas how to get out of this?
That's just the standard Android recovery. Use fastboot to flash your unpatched boot image file and you should be up and running again.
Well, that would be a problem. I don't have this tablet's boot image backed up anywhere. Is there any other way?
How did you install Magisk? If you have access to TWRP there might be a backup in /data.
I didnt use TWRP. I installed magisk manager and then there were 2 options in menu to install, magisk and something else. I installed magisk. It restarted tablet after it finished and got me stuck in the recovery screen.
So your tablet was already rooted before you tried installing Magisk.
You most likely need to somehow install the unpatched boot image to get up and running again. If you do not have access to the device firmware to extract the boot image, or can install or boot TWRP (or any other custom recovery) to possibly get a hold of the backup boot image in /data there's probably not much you can do.
Not that I know of, at least. There might be someone that knows some way around it. What is your device?
This is what I am using: https://iiyama.com/gl_en/products/prolite-tw1023asc-b1p/
Since you were rooted previously, maybe try running adb as root (adb root) when you're in recovery and then use an adb shell to pull the backup file from /data (it's in a folder named magisk_backup_<sha1>). A remote possibility, but worth a shot.
You need to try to find the stock boot image file somehow...
I have more of these tablets, so I could maybe get this boot image from those? I just don't feel comfortable doing it if something could get messed up again.
Also why did this happen in the first place? Was I installing it wrong?
mistyright said:
I have more of these tablets, so I could maybe get this boot image from those? I just don't feel comfortable doing it if something could get messed up again.
Also why did this happen in the first place? Was I installing it wrong?
Click to expand...
Click to collapse
If they're the same firmware version you could probably use adb shell to extract the boot partition.
Very hard to say why it failed... Possibly because you were already rooted and there was a conflict. Or maybe the device just isn't compatible.
Related
I managed to brick my recovery by trying to install the TWRP_Fire_2.8.7.0_adb.img to the recovery partition. Does anyone have a stock recovery image? :angel:
I already have root permissions, so installing it should not be the problem, but a way to correctly install the recovery would also be nice...
agowa338 said:
I managed to brick my recovery by trying to install the TWRP_Fire_2.8.7.0_adb.img to the recovery partition. Does anyone have a stock recovery image? :angel:
I already have root permissions, so installing it should not be the problem, but a way to correctly install the recovery would also be nice...
Click to expand...
Click to collapse
Root is irrelevant. Without a signed image you are going nowhere. Have not seen any of those floating around.
Davey126 said:
Root is irrelevant. Without a signed image you are going nowhere. Have not seen any of those floating around.
Click to expand...
Click to collapse
Do you have a fire tablet?
Can't you simply dump that partition and write to another/my device?
Found a stock recovery by accident. There is one within the Supertool download. I flashed it and now the recovery is working again.
So may it is a bad idea to tamper with the recovery if the boot loader is locked...
agowa338 said:
Found a stock recovery by accident. There is one within the Supertool download. I flashed it and now the recovery is working again.
So may it is a bad idea to tamper with the recovery if the boot loader is locked...
Click to expand...
Click to collapse
Cool - thanks for sharing. Didn't know this was possible but thinking through it now makes sense. On some locked devices you can't touch the recovery partition but since you 'successfully' borked yours through intentional action it demonstrated some ability to manipulate the contents. Nice when it works out that way.
I don't know how the bootloader lockdown works, but I thought it is similar to uefi. So the boot process is verified by certificates or hashes. So the binaries that are loaded at boot cannot be changed.
In addition, the fastboot does not allow you to flash images.
So as by uefi if you have an booting system (live cds) you can tamper with the contents on the disk, but if you tamper with boot files, the system would not start.
So i did a dd (without backing up my current recovery...) and overwrote the recovery partition from the normal boot mode using my root access. But the recovery image didn't succeed the bootloader checks and didn't load therefore.
I guess, if you find an unprotected part of the recovery to overwrite from where a program would be called as root, it could modify the recovery on the fly...
But that's mostly unproved thoughts based on research and tampering on uefi...
Does anyone have the default OP3t recovery.img?
The device cannot boot into any recovery versions I have installed (TWRP or the stock recovery). The only way to access TWRP is from ADB on my computer by typing "fastboot boot [twrp.img]".
Ive tried installing TWRP through ADB to see if flashing it again will mount it properly, but nothing has worked. I can boot into the OS still, but the only way to access recovery is (as i said) through ADB.
Anyone know how to fix this? I was thinking that reflashing the default recovery.img would fix this problem, but not overly sure about even that.
I tried to install the latest OTA patch from TWRP that people have been saying fixes the bootloader issues, but that left with "updater error 7".
nicnaknic said:
Does anyone have the default OP3t recovery.img?
The device cannot boot into any recovery versions I have installed (TWRP or the stock recovery). The only way to access TWRP is from ADB on my computer by typing "fastboot boot [twrp.img]".
Ive tried installing TWRP through ADB to see if flashing it again will mount it properly, but nothing has worked. I can boot into the OS still, but the only way to access recovery is (as i said) through ADB.
Anyone know how to fix this? I was thinking that reflashing the default recovery.img would fix this problem, but not overly sure about even that.
I tried to install the latest OTA patch from TWRP that people have been saying fixes the bootloader issues, but that left with "updater error 7".
Click to expand...
Click to collapse
I have it here: https://drive.google.com/drive/folders/0B4tnYt16-NAUQm02dHhDaWlyQUE
nicnaknic said:
Does anyone have the default OP3t recovery.img?
The device cannot boot into any recovery versions I have installed (TWRP or the stock recovery). The only way to access TWRP is from ADB on my computer by typing "fastboot boot [twrp.img]".
Ive tried installing TWRP through ADB to see if flashing it again will mount it properly, but nothing has worked. I can boot into the OS still, but the only way to access recovery is (as i said) through ADB.
Anyone know how to fix this? I was thinking that reflashing the default recovery.img would fix this problem, but not overly sure about even that.
I tried to install the latest OTA patch from TWRP that people have been saying fixes the bootloader issues, but that left with "updater error 7".
Click to expand...
Click to collapse
I believe if you re-lock your phone, the phone can factory reset and get re-flash stock recovery itself. btw,have you check the OTA zip file and make sure it was not damage when you downloaded it.
can you help me man i need that file but seems to be that link in not correct, can you give me the correct link pls i am stuck
Can't you just download the stock firmware and flash through ODIN? Then you will have stock recovery and everything.
EDIT:
Cancel my suggestion. ODIN is only for Samsung phones. My bad!
nicnaknic said:
Does anyone have the default OP3t recovery.img?
The device cannot boot into any recovery versions I have installed (TWRP or the stock recovery). The only way to access TWRP is from ADB on my computer by typing "fastboot boot [twrp.img]".
Ive tried installing TWRP through ADB to see if flashing it again will mount it properly, but nothing has worked. I can boot into the OS still, but the only way to access recovery is (as i said) through ADB.
Anyone know how to fix this? I was thinking that reflashing the default recovery.img would fix this problem, but not overly sure about even that.
I tried to install the latest OTA patch from TWRP that people have been saying fixes the bootloader issues, but that left with "updater error 7".
Click to expand...
Click to collapse
http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_3.5.4/
Scroll right to the bottom and look for oxygen recovery.
manor7777 said:
http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_3.5.4/
Scroll right to the bottom and look for oxygen recovery.
Click to expand...
Click to collapse
that link doesnt work, when i try to download it states no file attatched
I was trying to root my phone and had already unlocked by bootloader, flashed TWRP, and made a NANDroid backup. I had the Magisk zip from Magisk Manager on my SD card. I booted into TWRP using the commands
Code:
adb reboot bootloader
Code:
fastboot flash recovery twrp-3.2.3-0-ali.img
and
Code:
fastboot boot twrp-3.2.3-0-ali.img
Once in TWRP, I mounted the cache, vendor and micro SD card partitions. I unmounted them immediately afterwards and then installed the Magisk zip file. The reason that I mounted and unmounted the SD card was because, based on me trying random things, it was the only way for TWRP to show the zip file. Afterwards, I rebooted the system, the "Your device has been unlocked and can't be trusted" screen came up as normal, except that where it said "bad key" before, it said "N/A". The device did not move past this screen and instead stayed at that screen. I managed to turn it off by holding the power button for far longer than normal. I then booted my phone into TWRP and restored a previous backup. Is there a potential cause for this? Is there an alternative method of rooting that I'm not aware of?
did you install the no verity boot for your variant?
The only thing I installed was the zip. If it wasn't in the zip, then I didn't install it. How would I install that and where would I get it?
lucror said:
The only thing I installed was the zip. If it wasn't in the zip, then I didn't install it. How would I install that and where would I get it?
Click to expand...
Click to collapse
Check this thread
https://forum.xda-developers.com/mo...oot-magisk-installation-t3816569/post77074751
Will the fact that I have already tried to install Magisk affect the process? I did flash my TWRP backup, so would that have any bearing on the process? Sorry if these are basic questions, I haven't rooted a phone before and I'm trying to be very cautious.
lucror said:
Will the fact that I have already tried to install Magisk affect the process? I did flash my TWRP backup, so would that have any bearing on the process? Sorry if these are basic questions, I haven't rooted a phone before and I'm trying to be very cautious.
Click to expand...
Click to collapse
Nope, you're overwriting the boot image when flashing no-verity so Magisk would be gone anyways.
Okay. Thank you for your help everyone. I'll try that when I get the chance.
Hi,
My memory issues and a hard week led me to forget I needed to uninstall magisk manager adn 'restore image'. I've never had a rooted phone before, so I'd never done it before. Got lost in the 'big pile of problems' and google kept nagging to 'update'. Sigh.
Last thing I want to do is try to figure out how to migrate all my data and apps (I'm expecting Google Recorder is likely to prove a PITA to get everything 'moved'). So I'm wondering, is there a simple/easy way to get magisk root back and active without wiping apps/data on my Pixel 4a 5g since it was already rooted prior to the OTA security update?
The only consequence with applying the OTA should be that you're know updated and rootless (since the boot image would have been overwritten in the update)... Just patch the new boot image, flash it and you should be up and running again.
Didgeridoohan said:
The only consequence with applying the OTA should be that you're know updated and rootless (since the boot image would have been overwritten in the update)... Just patch the new boot image, flash it and you should be up and running again.
Click to expand...
Click to collapse
Ah. Thanks. That's simple enough and sounds like I don't have the emergency I was dreading.
Didgeridoohan said:
The only consequence with applying the OTA should be that you're know updated and rootless (since the boot image would have been overwritten in the update)... Just patch the new boot image, flash it and you should be up and running again.
Click to expand...
Click to collapse
Well, I rebooted the Pixel 4a 5g, and then it would get stuck on G logo and wouldn't load the system.
So I couldn't use latest magisk manager to create a new patched boot img. So I tried to flash the patched boot img I still had on my PC from december as the Factory image firmware is still the same right now as it was then. Now when I try to boot I get a boot loop that doesn't get to the G logo even.
Wondering what to do now... I guess it wasn't so simple after all.
Edit: I tried flashing the original boot.img. No change. Near as I can tell next option would be to try to side load an OTA update, but the Pixel 4a 5g doesn't seem to work via ADB...
What's weird is that the pixel was working before I tried to reboot it initially. Now I can't get into recovery or rescue mode either. Just have a boot loop. Can get into fastboot still.
Edit 2:
I had the wrong factory image. Got the right one, for january. Flashed boot.img via fastboot. Back to 'stuck on G logo' like before.
Edit3:
Seems stuck in fastboot mode now. When selecting 'start' fastboot just loads up again.
I tried adb sideloading OTA update. Didn't work.
I tried flashing factory image removing "-w" modifier from flash-all.bat. Stuck in boot loop on googles "G" logo with the loading status bar underneath.
Hoping there's still a way to avoid a factory reset, but wondering what next steps there are.
Is there a subforum better suited to maybe getting this question answered?
Sounds like you've gotten to a point where it's better to ask for help in your device's forum, but I've seen you're doing that already.
Hope you get things sorted...
Edit: since it's always possible that modules mess up a system update, have you tried the adb command to remove modules (if boot reaches a point where adb is recognised), or booted to safe mode to disable all modules? You've got some details here:
https://www.didgeridoohan.com/magisk/Magisk#hn_Disablinguninstalling_modules_manually
Since I never had a problem with an update in years, and I'm also a very stupid person, I didn't backup my data before my latest custom rom (Pixel Experience Plus) update.
I got the notification for the November security patch updates, and I downloaded the zip as usual. For the actual installation I usually reboot my Mi 9T Pro into TWRP, flash both the OS update and Magisk, etc. and reboot. Everything seemed to go smoothly as usual: TWRP asked me to input my unlock sequence, then the usual stuff. Problem is, when I tapped 'Reboot system', it didn't reboot normally: it went into Recovery mode again, and from that moment on there's been no way to do otherwise. But now TWRP doesn't ask me the unlock sequence anymore and looks like there's no way to access the data. I tried injecting the recovery from fastboot, I wiped everything except internal storage (I don't give a damn about the OS anymore at this point); I also tried to reinstall the same old rom from OTG after wiping System, but nothing. Whatever I do, it always boots up in Recovery, and it doesn't ask me the unlock sequence. I know my stuff is still there, it's just that the contents of sdcard aren't accessible and look like random alphanumeric sequences from the TWRP file manager. And yes, that's the whole point of encryption, but I was used to TWRP asking me to unlock/decrypt so in the worst case scenario I would be able to access my data and copy via OTG. But now, with the system unable to boot and the recovery not decrypting my stuff, I'm starting to losing hope. I'm sure here on XDA there are much smarter / knowledgeable people than me, and I hope somebody can help me find a way to break the cycle and return in possession of the data that I stupidly didn't backup.
Any help would be greatly appreciated!
Try reflashing the boot image. Failing that, you should be able to ADB sideload the update via TWRP.
V0latyle said:
Try reflashing the boot image. Failing that, you should be able to ADB sideload the update via TWRP.
Click to expand...
Click to collapse
I think I tried both. I say 'I think' since my knowledge could fail here.
I tried re-flashing the TWRP img from OTG, nothing changed.
I successfully sideloaded the OS through ADB, but I'm still stuck.
Should I try both? (In which order)?
Thanks a lot.