After the latest magisk update I can't even get into recovery, let alone boot Lineage.
Since is given me issues on my phone too, I'd rather just get rid of it at this point, but I can't even get into TWRP.
Guise, anyone tell me how I can just flash a clean rom? ODIN is a mystery to me.
Related
Hey guys i was hoping someone out there can help me out. My phone just got the message to update to 5.0.1, but when i tried to update it, it would reboot then load to around 40% of the update then say error with a little android on his back with a red triangle on his stomach. So i thought this was because of my phone being rooted and unlocked, so i unrooted it and locked it using Nexus Root kit, and when i tried to update the phone to 5.0.1 it still gives me that error message. Some things to note my phone was ATT and i did delete the ATT bootloader immage and all of there ringtones when my phone was rooted. Please help
You mean AT&T Boot animation image?
Thats exactly why your OTA failed because you did changes to your /system/.
This is why I say if someone is going to do changes to /system/, you may as well flash a custom ROM because when you get OTAs, you're going to end up in your current position. There are a number of ways to approach this issue,
1) Return back to stock by flashing factory images http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
2) Unlock your bootloader -> Flash TWRP -> Flash a custom rom, kernel (optional), gapps, supersu
Either or will get your phone booting again.
zephiK said:
You mean AT&T Boot animation image?
Thats exactly why your OTA failed because you did changes to your /system/.
This is why I say if someone is going to do changes to /system/, you may as well flash a custom ROM because when you get OTAs, you're going to end up in your current position. There are a number of ways to approach this issue,
1) Return back to stock by flashing factory images http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
2) Unlock your bootloader -> Flash TWRP -> Flash a custom rom, kernel (optional), gapps, supersu
Either or will get your phone booting again.
Click to expand...
Click to collapse
Will doing the first thing you say bring back the AT&T Boot animation image, because i think i need it to go get a new phone, i think my phone is defective because the speakers with make random popping noises and will have white noise coming out from them even when im not playing anything.
So I was in the middle of using Lineage OS 14.1 when it notified that there was a May 20th update. I allowed it to update, when for some reason it just took me straight to Recovery.
When I tried to reboot back to the system, for some reason it continued to boot straight to recovery.
I tried wiping everything and reinstalling Lineage, but the same thing happened. Same with AICP.
I figured it was an issue with the recovery, so I flashed the latest img from recovery (since I can't do it from fastboot) yet the problem continues to persist..
Can anybody help? I can't do anything with fastboot because it always fails, I can't flash anything, I'm just stuck on TWRP no matter what I do. I even checked the system and everything and despite TWRP saying I "successfully installed rom" or whatever, nothing gets installed into the system or anything, it just stays empty. How do I fix this?
I read somewhere that it may be because it's trying to update something, and since TWRP is installed instead of the actual LG recovery, it can't install it or whatever. I was previously on a stock rom before I installed Lineage. Could that be it? I figured I can fix it using THIS method, but I'm not sure. The link to the KZD is dead and the only download available for D415 is "old" so I don't want to risk bricking my device.
Help is appreciated ahead of time!
I also just realized that I can't really do anything about flashing the stock rom manually because the download mode is registered as fastboot and it doesn't seem to properly register in the Device Manager at all...
I've also just attempted to factory reset the device, but the only thing that does is also boot into TWRP..
Fivavoa said:
I've also just attempted to factory reset the device, but the only thing that does is also boot into TWRP..
Click to expand...
Click to collapse
In twrp there is a terminal so you might be able to get access to fastboot by removing download mode.
Look at the thread below.
https://forum.xda-developers.com/lg-l90/general/guide-fastboot-l90-d415-t2827825
Hi :3
Fivavoa said:
So I was in the middle of using Lineage OS 14.1 when it notified that there was a May 20th update. I allowed it to update, when for some reason it just took me straight to Recovery.
When I tried to reboot back to the system, for some reason it continued to boot straight to recovery.
I tried wiping everything and reinstalling Lineage, but the same thing happened. Same with AICP.
I figured it was an issue with the recovery, so I flashed the latest img from recovery (since I can't do it from fastboot) yet the problem continues to persist..
Can anybody help? I can't do anything with fastboot because it always fails, I can't flash anything, I'm just stuck on TWRP no matter what I do. I even checked the system and everything and despite TWRP saying I "successfully installed rom" or whatever, nothing gets installed into the system or anything, it just stays empty. How do I fix this?
I read somewhere that it may be because it's trying to update something, and since TWRP is installed instead of the actual LG recovery, it can't install it or whatever. I was previously on a stock rom before I installed Lineage. Could that be it? I figured I can fix it using THIS method, but I'm not sure. The link to the KZD is dead and the only download available for D415 is "old" so I don't want to risk bricking my device.
Help is appreciated ahead of time!
Click to expand...
Click to collapse
Hello, look at this page, this would solve the problem:
https://www.androidsis.com/solucionar-problema-bootloop-recovery-actualizacion-ota-linageos/
Rooting this moto x4 is a whole new learning curve. I've noticed that this is the only phone that doesn't let twrp recover stick. I can flash a rom and everything is fine phone works perfectly. But later on if I need to flash something else when I boot back into recovery I'm back at the stock recover. Never had this happen before. So what I do for now is flash the ROM gapps then reflash twrp installer till I find a more permanent solution
jmcandrews83 said:
Rooting this moto x4 is a whole new learning curve. I've noticed that this is the only phone that doesn't let twrp recover stick. I can flash a rom and everything is fine phone works perfectly. But later on if I need to flash something else when I boot back into recovery I'm back at the stock recover. Never had this happen before. So what I do for now is flash the ROM gapps then reflash twrp installer till I find a more permanent solution
Click to expand...
Click to collapse
Yes, that is what you have to do.
As recovery is no longer a separate partition, it gets replaced when the boot partition gets updated.
I believe this is the way it will be with any device with a/b partition.
Trying to flash TWRP to a smart watch. Found the correct version on TWRP.ME and flash it.
Everything good until I let the watch reboot into system and then try to boot back into TWRP.
Stock recovery has replaced TWRP. I know this is a known problem with some stock ROMS, but I DON'T
know how to get around it. This is an old Samsung Gear Live and I've seen threads where others have claimed to be
successful with this installation.
Anyone??
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