Database Info

[HELP] MOTO G TURBO xt1557 6.0.1 Marshmallow Superuser

Successfully Done
✓ bootloader unlock
✓ TWRP Recovery twrp-merlin-2.8.7-r7.img
All most try all super user
{
"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"
}
but after flash super user zip phone stop work at bootloader warning

same thing happen to me too..plz someone answer.

Prior to flashing supersu.zip, open twrp>advanced>terminal and enter (without quotes) enter the command
Code:
"echo SYSTEMLESS=true>>/data/.supersu"
Now SuperSU would install in systemless mode. The latest betas automatically install in systemless mode (I am using 2.74). Check if now it works.
Broadcasted from Zeta Reticuli

@Gravemind2015 is correct, that is the command needed to make it work... note that since you already tried flashing several SuperSU versions the old way, if it continues to be a problem you may need to reflash the factory images and verify booting prior to trying the mentioned systemless method.

mindjek07 said:
...after flash super user zip phone stop work at bootloader warning
Click to expand...
Click to collapse
I had the exact same issue on my 16 GB xt1540, running stock, fresh 6.0. Trying to root with SuperSU's (over TWRP), several versions up to 2.74, earlier versions down to 2.4 ish... I'd freeze at boot logo every time, after what appeared to successful installs.
After reading somewhere about someone else's luck, I gave 2.65 a go, a version I must not have tried (and one I notice is not on your screen shot), and it worked. I certainly didn't expect it to, and obviously it could be completely coincidental. I'm pretty sure, however, that I did nothing differently on that install to what I had done other times.
HTH
Buena suerte

Love you!!!
You pacified my pain.

Software Update?

Hello!
I saw today that my Samsung Galaxy S6 has a new Software Update, when i try to install it, it downloads it, then asks me when i want to install it (like now or overnight)
when i install it now, it restarts the phone like it usually should, but when the Phone is rebooted, my S6 takes me to my TWRP Recovery Menu, so my question is, how do i install
the latest official software update without bricking my rooted S6?

First question. How did you manage to install twrp and still be able to download ota Updates?
Secondly: you only can install ota Updates over stock Recovery.

XxM4tzexX said:
First question. How did you manage to install twrp and still be able to download ota Updates?
Secondly: you only can install ota Updates over stock Recovery.
Click to expand...
Click to collapse
i dont really know, i just saw that my phone has an update, i clicked on it, it downloaded and then asked me to install it, and my phone is rooted and has TWRP, i dont even know if it would be a good idea to look for the software update and update it with odin or something, im completely new at this so i cant really answer that question. maybe it didnt even download the update. i wonder where it WOULD be saved if i really managed it to download...

I'm still to figure out what you did because technically speaking Samsung would have picked up you rooted and you would receive a message saying your system has been modified.
---------- Post added at 11:03 AM ---------- Previous post was at 11:01 AM ----------
If what you saying is true then when your phone reboots into TWRP to install...look at where the OTA is stored. Copy it to internal storage. Reboot TWRP then flash OTA and reflash root

weirdly this message doesnt pop up at all, and im running rooting, xposed etc. its very weird...

{
"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"
}
as you can see, it downloaded and after the installation, it asks me when the installation should begin, if i install, the phone reboots and puts me automatically to twrp, i reboot back to system and my phone says that the installation failed and if i want to send a report to samsung...

Unable to update oxygenOS after unbricking

So I have become member of the bricked-my-phone family. I have followed this tutorial https://www.getdroidtips.com/unbrick-oneplus-6/ and successfully unbricked it.
I have downloaded latest oxygen os (I tried two latest - one with android 11 and one with android 10), I have added the zip to the root directory and from system update I selected it, but in both cases I instantly get "System update installation failed" at 0%. It also says I am up do date from OTA (it it android 8.1 lol)
what should I do?
I want to install latest oxygenOS only for firmware, then I will be installing LineageOS again. I am afraid If I do it the other way around (LOS first than firmware) I will brick it again.
{
"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"
}

Download the latest OOS11 full version and install through Settings-- System Update -- Local Update.
Hope it helps.

mm_rajesh said:
Download the latest OOS11 full version and install through Settings-- System Update -- Local Update.
Hope it helps.
Click to expand...
Click to collapse
That's exactly what I did and the result, you see on screenshot..
But later in the evening, I found the solution here https://forums.oneplus.com/threads/oneplus-6-system-update-installation-is-failed.1314311/:
The OP6 must be on 9.0.9 before upgrading to Android 10.
You are still on Oreo/Android 8.
There is a link for 9.0.9 on this website:
https://www.getdroidtips.com/download-oxygenos-9-0-9-9-0-17-update-for-oneplus-6-and-6t/
Click to expand...
Click to collapse

If you are able to boot to Fastboot as well as able to unlock bootloader than do unlock the bootloader and flash this msm file
[ROM][STOCK][FASTBOOT][OP6] Stock Fastboot ROMs for OnePlus 6
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via stock recovery (with twrp is possible but not recommended). The updates will be done on the slot not used for example...
forum.xda-developers.com
And after that reboot to recovery stock and factory reset. This will fix your issue than after lock the bootloader(if it's unlock after flashing the file) and update to latest rom (download the rom from oneplus updater app with advance setting "on")

Question ROG 5s Update after Converting from CN to WW

I have been trying to update my phone for a while now but for some reason I am unable to, when I got the phone I followed this guide to convert it from CN to WW, and it worked well
But right now I am stuck at at version 18.1220.2109.126,
Every time I try to update to android 12 I am greeted with this
{
"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"
}
if anyone could help me with this I would be really grateful, no matter what version I use I am always getting the same message

Update incrementally up to the version you want to get to.

Andrologic said:
Update incrementally up to the version you want to get to.
Click to expand...
Click to collapse
its not working man, i almost tried every firmware

Flash RAW firmware (use the script / binary WITHOUT a wipe), then update normally.
If all else fails, you can perform the update with fastboot. It won't fix the issue and will have to be done for every future update, though.
Bypass "System update failed" - Update w/ Fastboot
Update notifications appeared, the update was recognized, but it failed instantly. I have since resolved the error by flashing a raw firmware without a wipe. This post is for archival purposes or simply an alternative installation method...
forum.xda-developers.com

twistedumbrella said:
Flash RAW firmware (use the script / binary WITHOUT a wipe), then update normally.
If all else fails, you can perform the update with fastboot. It won't fix the issue and will have to be done for every future update, though.
Bypass "System update failed" - Update w/ Fastboot
Update notifications appeared, the update was recognized, but it failed instantly. I have since resolved the error by flashing a raw firmware without a wipe. This post is for archival purposes or simply an alternative installation method...
forum.xda-developers.com
Click to expand...
Click to collapse
I tried both, but every time I try to run a script, be it flash raw or the flash_all, I keep getting waiting for devices, even though my phone is connected to my pc(through the side port) and is in fastboot/bootloader.

Question Stuck in Download Mode: Error verifying vbmeta image

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.