Sorry for bad grammar or lack details
Hello this night I got a notification from magisk to update magisk manager to v22. When I install it, it says magisk unsupported ....... (I forgot what it says) magisk will act as its not downloaded. So I tried to uninstall it and downgrade to 8.0.4 and it required me to reboot. After automatically reboot I'm stuck on fastboot. So I go to TWRP and try to uninstall magisk and I got error 1 and I tried to install and it did the same message. ERROR 1. can someone help me as fast as possible? It's 8:51 PM at the moment and I have school at 6 AM
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Cocomug_ said:
Sorry for bad grammar or lack details
Hello this night I got a notification from magisk to update magisk manager to v22. When I install it, it says magisk unsupported ....... (I forgot what it says) magisk will act as its not downloaded. So I tried to uninstall it and downgrade to 8.0.4 and it required me to reboot. After automatically reboot I'm stuck on fastboot. So I go to TWRP and try to uninstall magisk and I got error 1 and I tried to install and it did the same message. ERROR 1. can someone help me as fast as possible? It's 8:51 PM at the moment and I have school at 6 AM
Click to expand...
Click to collapse
As the screenshot you provided implies, your boot partition seems corrupted.
Trying to figure out why can come at a later time, in the meantime try flashing a boot.img extracted from your current ROM (i.e a TWRP backup) or stock firmware (if you're on Stock). Using TWRP or fastboot should solve this issue.
Slim K said:
As the screenshot you provided implies, your boot partition seems corrupted.
Trying to figure out why can come at a later time, in the meantime try flashing a boot.img extracted from your current ROM (i.e a TWRP backup) or stock firmware (if you're on Stock). Using TWRP or fastboot should solve this issue.
Click to expand...
Click to collapse
Since I'm stuck on fastboot there's no way to extract it, so i just flashed the ROM zip file, and it worked. Thank You
Cocomug_ said:
Since I'm stuck on fastboot there's no way to extract it, so i just flashed the ROM zip file, and it worked. Thank You
Click to expand...
Click to collapse
how did you flashed it?
Related
So i am trying to update my phone for a few days with the latedt push OTA (6.0)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And when the system reboots, it brings me to the TWRP Bootloader screen.. even if i push the reboot to system button, the update failed to be applied.
Any tips?
(ElementalX Kernel, TWRP & SuperSU - Stock 6.0)
Edit: Sorry for the picture size, i have no idea how to resize)
SebLemery said:
So i am trying to update my phone for a few days with the latedt push OTA (6.0)
And when the system reboots, it brings me to the TWRP Bootloader screen.. even if i push the reboot to system button, the update failed to be applied.
Any tips?
(ElementalX Kernel, TWRP & SuperSU - Stock 6.0)
Edit: Sorry for the picture size, i have no idea how to resize)
Click to expand...
Click to collapse
You have to be stock to update OTA. No special recovery and no root
funnel71 said:
You have to be stock to update OTA. No special recovery and no root
Click to expand...
Click to collapse
So, how can i make sure this message does not appear anymore, or can i just flash the latest image from code.google.com with the update included somehow, and everything will restore like it does now?
(sorry for the uestions, im no pro just yet)
SebLemery said:
So, how can i make sure this message does not appear anymore, or can i just flash the latest image from code.google.com with the update included somehow, and everything will restore like it does now?
(sorry for the uestions, im no pro just yet)
Click to expand...
Click to collapse
You can't flash any official OTAs with TWRP. It's a known fact, nothing you can do about it. Reflash stock recovery, or just use a close to vanilla custom ROM that gets the monthly security updates.
Hey Guys,
hopefully its okay to post my request here.
I am stuck rooting my OP7 Pro.
As you can see on below screenshots this where I try to start:
I have a GM1913 and I am on Oxygen OS 10.0.5.GM21BA:
I folowd this guide including the video tutorial: https://www.xda-developers.com/unlock-bootloader-root-oneplus-7-pro/
Unfortunately I am unable to gain root.
Either I am ending up in a boot loop or I am able to boot into android but root is still missing and Wireless LAN isnt working.
These are the TWRP Files I was working with:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The Files 3.3.1-0 to 3.3.1-4 aren´t working anyway. after flashing them, I am just back at the bootloader. Only the unofficial 76 Version is working to get into TWRP.
If I am able to get into twrp, I´ll do the following:
1) flashing original boot.img to Slot A and Slot B (from here: https://androidfilehost.com/?w=files&flid=294300)
2) flashing the TWRP Zip File (only to the "active" Slot)
3) flashing Magisk 20.4 (also tried 20.1)
And then either I am stuck in a bootloop or in Android Wlan is missing and Magisk still not working.
Can please someone help me pointing at what I am doing wrong?
Wait a sec. If you have unlocked bootloader please boot to fastboot and do command: fastboot boot twrp_file_name.img on the latest TWRP that you can find: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Latest version and files you need are:
TWRP 3.3.1-79 Unified Unofficial Q by mauronofrio
TWRP 3.3.1-79 Unified Unofficial Installer by mauronofrio
after you boot to this recovery go and install recovery installer zip and later flash also package with Magisk 20.4
Voilla you have root + latest TWRP
Well.... just WTF?
Just done it as described by @SkubiDoo and it works...
So was the issue using old TWRP Files?
Anyway - Thank you very much for your help!
Looks like mate better to stick with this mauronofrio version.
I am offered a new OTA Rom from the updater - I download it and then in the Recover I am supposed to enter my password for the Encryption as my drive is encrypted from the factory.
Phone boots into recovery and after 1 second it boots back to normal. The message for entering the password does not appear
Who can help me?
Thanks Gordon
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Have you replaced your stock recovery with TWRP recovery?
Sathelp said:
Have you replaced your stock recovery with TWRP recovery?
Click to expand...
Click to collapse
No - its the original stock rom. i got the handy as christmas gift. which twrp ist the newest and is there an install documentation?
I take it that it is the original EU ROM? If it's stock Chinese, then ignore this post, stock recovery works ok but I know some sellers put on a copy of EU ROM before selling it, so please check your ROM details first.
There is a newer twrp but the one have been using is the original that says it's a mi 10 pro but it works fine. Here is a link to a word doc that wrote about installing ROMs for the ultra. https://mega.nz/file/6UAhXCxZ#Np2KwhMnl8obmOvp4b-2R9ajo0zrtz3vwefy-Ya3PLs
Just use the section on twrp installation through a PCs fastboot app, then reboot system and use the OTA or flash direct from twrp. Links are in the doc for twrp or use http://mifirm.net. Apparently the latest twrp works ok too but I have not installed it yet or put a link in the doc but here is a direct link from my mega folder https://mega.nz/file/TUh0mLAZ#0jYRCIeAiCJEMW1eIvWzPSWG2MuKJMG5V-wgxtWT80M
If you are on A11, you may need to disable your lock screen password before update but twrp will let you know.
Hope it helps.
Sathelp said:
I take it that it is the original EU ROM? If it's stock Chinese, then ignore this post, stock recovery works ok but I know some sellers put on a copy of EU ROM before selling it, so please check your ROM details first.
There is a newer twrp but the one have been using is the original that says it's a mi 10 pro but it works fine. Here is a link to a word doc that wrote about installing ROMs for the ultra. https://mega.nz/file/6UAhXCxZ#Np2KwhMnl8obmOvp4b-2R9ajo0zrtz3vwefy-Ya3PLs
Just use the section on twrp installation through a PCs fastboot app, then reboot system and use the OTA or flash direct from twrp. Links are in the doc for twrp or use http://mifirm.net. Apparently the latest twrp works ok too but I have not installed it yet or put a link in the doc but here is a direct link from my mega folder https://mega.nz/file/TUh0mLAZ#0jYRCIeAiCJEMW1eIvWzPSWG2MuKJMG5V-wgxtWT80M
If you are on A11, you may need to disable your lock screen password before update but twrp will let you know.
Hope it helps.
Click to expand...
Click to collapse
thank you ... will test it
I tried installing the twrp recovery for it, and it did work but it had no access for the sd card nor the external sd card for some reason, but after some time it did work with an otg
So i had the supersu zip file on a flash card and tried installing it
It everything goes fine, until it finish and reboots to the system
Then this happens
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And no matter how many times i click that reset, it happens, it's only gone when reinstalling the stock firmware, but then I'll need to install the recovery again......., sometimes after installing the TWRP recovery, it goes into a restart loop so i need any help please
If you are the getting the following error, "Verification Failed, unable to restart your device. The integrity verification has failed. You need to reset you device to factory default settings. This will erase all your data" on your Android Smartphone don't worry because together we can resolve the issue.
Anna Phillips said:
If you are the getting the following error, "Verification Failed, unable to restart your device. The integrity verification has failed. You need to reset you device to factory default settings. This will erase all your data" on your Android Smartphone don't worry because together we can resolve the issue.
Click to expand...
Click to collapse
I did, in fact, i even reinstalled the stock image of the firmware because clicking "reset" simply doesn't work, also if i just flashed the TWRP without a root zip, it will go bootloop, i just wanna install a custom rom but looks like i need to root the device to do so, so i can pass the verification thing, but hey, thanks for caring.
MazenGomaa said:
I did, in fact, i even reinstalled the stock image of the firmware because clicking "reset" simply doesn't work, also if i just flashed the TWRP without a root zip, it will go bootloop, i just wanna install a custom rom but looks like i need to root the device to do so, so i can pass the verification thing, but hey, thanks for caring.
Click to expand...
Click to collapse
If you can somehow get TWRP use Magisk to root, supersu does not work on new devices.
How to Install Magisk on your Android Phone
Magisk is a powerful tool that can help you customize some aspects of your phone or even grant you root access. Here's how you can install it!
www.xda-developers.com
Hey there,
I have a problem with my A52 (SM-A525F/DS): It doesn't boot anymore, as it is stuck in the Download mode, showing the error message: "Reason recovery: Error verifying vbmeta image: invalid vbmeta header (6)"
Steps that lead to this:
LineageOS is installed. After installation of a software update, Magisk lost its root. So I tried to install an alternative recovery (TWRP) with Odin. Odin said "Pass", but now this error message occurs.
What can I do now to make the phone work again? Install the Stock ROM?
Would you please help me with this issue? Thank you so much.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Once again, you need to properly follow all the instructions listed on the thread: https://forum.xda-developers.com/t/recovery-official-twrp-3-7-for-galaxy-a52-4g-and-a72-4g.4405751/
Thank you and please excuse my stupidity.
@Simon1511, it worked, thanks again.
As this was inititally my problem: Is there a way to use LineageOS with Magisk and install Updates without losing the root access?
fheba said:
@Simon1511, it worked, thanks again.
As this was inititally my problem: Is there a way to use LineageOS with Magisk and install Updates without losing the root access?
Click to expand...
Click to collapse
Not automatically. You would have to reflash magisk every time you install an OTA.
deleted
Simon1511 said:
Not automatically. You would have to reflash magisk every time you install an OTA.
Click to expand...
Click to collapse
Thanks for your answer. I'm curious: Why doesn't it work anymore? It works with older phones like the Samsung A5 2017.
fheba said:
Thanks for your answer. I'm curious: Why doesn't it work anymore? It works with older phones like the Samsung A5 2017.
Click to expand...
Click to collapse
The problem is encryption. On the A5 2017 the Magisk re-install script would run after installing an OTA and would install itself again. But since encryption is enabled by default on newer phones (such as the A52) it doesn't work/behave correctly.
I'm fairly sure though it's an issue with Magisk and not with the ROM.