Database Info

Error updating my CM12S OTA

Everytime i get this error in TWRP once my device restarts to update a newly downloaded OTA.
http://dl-1.va.us.xda-developers.co....png?key=Cwhmi0kMAXNX0fvd0_AFMQ&ts=1431660495
Tried Cyan delta, did not work.
Help please

in_core said:
Everytime i get this error in TWRP once my device restarts to update a newly downloaded OTA.
http://dl-1.va.us.xda-developers.co....png?key=Cwhmi0kMAXNX0fvd0_AFMQ&ts=1431660495
Tried Cyan delta, did not work.
Help please
Click to expand...
Click to collapse
Can't see the screenshot...

SimonTS said:
Can't see the screenshot...
Click to expand...
Click to collapse
{
"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"
}

Running the latest TWRP?
You can always flash the OTA manually from the OTA Download folder if you wish.

SimonTS said:
Running the latest TWRP?
You can always flash the OTA manually from the OTA Download folder if you wish.
Click to expand...
Click to collapse
I installed the TWRP around 3 months back. At that time it was the latest version. I assume its not the latest anymore.
And regarding flashing manually: Should i just "Install"? Or do I need to wipe and what not? And will I lose data?

in_core said:
I installed the TWRP around 3 months back. At that time it was the latest version. I assume its not the latest anymore.
And regarding flashing manually: Should i just "Install"? Or do I need to wipe and what not? And will I lose data?
Click to expand...
Click to collapse
The latest TWRP is 2.8.6.0
You should be able to install the OTA without any issues at all - but it may be worth wiping the caches anyway.
Previous threads if you'd searched "OTA TWRP"
http://forum.xda-developers.com/oneplus-one/help/problem-update-cm12-t3091501
http://forum.xda-developers.com/oneplus-one/help/official-ota-file-placed-t3090903
and
http://forum.xda-developers.com/oneplus-one/help/ota-t3072467 - which is your own previous thread

SimonTS said:
The latest TWRP is 2.8.6.0
You should be able to install the OTA without any issues at all - but it may be worth wiping the caches anyway.
Previous threads if you'd searched "OTA TWRP"
http://forum.xda-developers.com/oneplus-one/help/problem-update-cm12-t3091501
http://forum.xda-developers.com/oneplus-one/help/official-ota-file-placed-t3090903
and
http://forum.xda-developers.com/oneplus-one/help/ota-t3072467 - which is your own previous thread
Click to expand...
Click to collapse
Its worked like a charm. Thanks. By the way mu current TWRP version is 2.8.5.1. How can i update it to the latest?

in_core said:
Its worked like a charm. Thanks. By the way mu current TWRP version is 2.8.5.1. How can i update it to the latest?
Click to expand...
Click to collapse
Install it?

SimonTS said:
Install it?
Click to expand...
Click to collapse
Just downloaded the .img file from twrp's website for my device.
So how to instal .img file?
Sorry if I am being noobish here, but I am not sure thats why i am asking.

Nevermind. Found it already. Used TWRP Manager from Playstore to update

Unable to mount /data

Hi all! 2 weeks ago I got the S7.
First thing I did was installing root and xposed.
Then I followed this guide to install root and recovery. At the beginning it was all good, despite some errors (described below). When I rebooted the phone SuperSU was working and root was granted.
Today I initiated titanium backup and root failed. When I tried to start SuperSU I got a messsage saying SuperSU is not installed and can't be installed. Quite confusing.
After that I started TWRP. Trying to install SuperSU again gave me the error message in the image below.
Do any of you know where the problem could be? I Googled for a while and found some older Galaxies have a corrupt memory issue that could be similar. Could this be my problem? Any guidance for solving it?
The device is working for now but I don't dare to reinstall any ROM or touching anything. I'm scared it'll die on me and I really like this phone.
Thanks a lot guys!
G930FXXU1APB4
{
"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"
}

I saw my phone is encrypted, but there's no option to change it
I skiped 10 step in the twrp guide, colud this be the problem? but... why was root working some days ago and not anymore?

Had the security policy updated, right? That destroys SU. There are plenty threads about that one already.

centroi said:
I saw my phone is encrypted, but there's no option to change it
I skiped 10 step in the twrp guide, colud this be the problem? but... why was root working some days ago and not anymore?
Click to expand...
Click to collapse
To remove Samsung encryption you must format your data in twrp, otherwise root will not work.

TheSproker said:
To remove Samsung encryption you must format your data in twrp, otherwise root will not work.
Click to expand...
Click to collapse
Will it work? in twrp the data partition show 0mb in all parts, cant read data partition. Should I format anyway?
Thank you!

centroi said:
Will it work? in twrp the data partition show 0mb in all parts, cant read data partition. Should I format anyway?
Thank you!
Click to expand...
Click to collapse
Yes, it worked for me. Just follow the 10.th step of this guide: http://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770

TheSproker said:
Yes, it worked for me. Just follow the 10.th step of this guide: http://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770
Click to expand...
Click to collapse
IT's solved.
Thank you!!

centroi said:
IT's solved.
Thank you!!
Click to expand...
Click to collapse
You're welcome

TheSproker said:
Yes, it worked for me. Just follow the 10.th step of this guide: http://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770
Click to expand...
Click to collapse
will this method work on HTC 820G+ am experiencing the same problem.

Recent root problems on my L04 Marshmallow B820

I had the problem, I couldn't root my phone after the update from B521 to the latest B820 version.
I tried out SuperSu versions 2.65 till 2.74.
After rooting through TWRP, I always got bootloops and after unrooting the system starts normally.
As a last try, I looked into the install script and set the "SYSTEMLESS" var to "true".
Now I've got a rooted and starting phone.
So I think there must be a problem, at least for me, with automatically detecting a systemless installable Android version in SuperSu from chainfire at Honor 6, as I understand.
Did anyone else have that problem?
I added SYSTEMLESS=true in /META-INF/com/google/android/update-binary within SuperSu-v2.65.zip, just as described there, but it should defaults to true after proper detecting without this.
At my B521 system, I used SuperSu version 2.52, which worked there and wasn't booting at Marshmallow, too.

Install 2.62
{
"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"
}
Sent from my H60-L04 using Tapatalk

What Tools did you use? The multi tool doesn't have emui 4 on L04 yet

gammaanimal said:
What Tools did you use? The multi tool doesn't have emui 4 on L04 yet
Click to expand...
Click to collapse
Flash it using TWRP recovery...
Sent from my H60-L04 using Tapatalk

The Multi Tool says for TWRP L02 and L12, can I also install it on L04?

I've installed SuperSu 2.74 via fastboot/TWRP, but as I wrote, only with an modified updater-script, the system boots up. (for me, not sure why and maybe this can help others)

Machredsch said:
I've installed SuperSu 2.74 via fastboot/TWRP, but as I wrote, only with an modified updater-script, the system boots up. (for me, not sure why and maybe this can help others)
Click to expand...
Click to collapse
I think I have exactly the same issue, could you upload your modified supersu.zip for me or walk me through the modifications?
That'd be swell.

hagehagen said:
I think I have exactly the same issue, could you upload your modified supersu.zip for me or walk me through the modifications?
That'd be swell.
Click to expand...
Click to collapse
Have tested it today with latest stable SuperSu, which is v2.76-20160630161323.
-> open the archive with an archive-manager
-> go to /META-INF/com/google/android/ directory
-> edit update-binary with a text editor (your text editor should respect linux line breaks (LF), so if you're on windows, you have to make sure this, I think)
-> after the commented section(all lines with a # beginning), where you can read about possible system vars and beyond,
you have to set the SYSTEMLESS variable to true like in the following example of code:
Code:
...
# if needed. It must replace the input file and return a 0 exit code.
[COLOR="Red"]SYSTEMLESS=true[/COLOR]
OUTFD=$2
...
Line 2, you have to insert to achieve an systemless installation, which seems to be the only way for you and me to make it work.
Please make sure to pay attention to upper/lower case, because otherwise it will fail.
-> save the updated zip and install it via TWRP, e.g. via sideload
Hope, this was usefully.
Note: This is only usefull for Marshmallow as described in the file, because it will not work below.
If you leave TWRP afterwards, e.g. for reboot and it asks you for installing root, click on "Do not install".

Pixel 3 rooted with Magisk - OTA is being downloaded?

My Pixel 3 is rooted with Magisk, but I did not install TWRP.
Root is available:
{
"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"
}
Yet, the phone is offering an update:
Since I took this screenshot, the download has completed, and it is offering to install it.
My understanding is that OTA would not happen if the phone is bootloader unlocked and rooted.
Should I let it install this update? How can I find out exactly which update it is? I'm assuming it would be (PQ3A.190605.003, Jun 2019), but how can I confirm?
Where is this 1.2 Gb file stored on the phone once it downloads? I found posts saying it was at root level in folder /cache, but it is not there. Maybe it moved for Android 9? I tried to use Solid Explorer to find files > 1 Gb, but it did not find anything.

I was also surprised today, but let it install. Lost the root afterwards.

moldovanos said:
Lost the root afterwards.
Click to expand...
Click to collapse
Did you have any issues re-establishing root with Magisk after installing the update?
Which version of Magisk? Latest 19.3?

timg11 said:
Did you have any issues re-establishing root with Magisk after installing the update?
Which version of Magisk? Latest 19.3?
Click to expand...
Click to collapse
Rebooted into bootloader, fastboot TWRP, flashed latest 19.3 and that's it. Everything is back to normal

timg11 said:
My Pixel 3 is rooted with Magisk, but I did not install TWRP.
Root is available:
Yet, the phone is offering an update:
Since I took this screenshot, the download has completed, and it is offering to install it.
My understanding is that OTA would not happen if the phone is bootloader unlocked and rooted.
Should I let it install this update? How can I find out exactly which update it is? I'm assuming it would be (PQ3A.190605.003, Jun 2019), but how can I confirm?
Where is this 1.2 Gb file stored on the phone once it downloads? I found posts saying it was at root level in folder /cache, but it is not there. Maybe it moved for Android 9? I tried to use Solid Explorer to find files > 1 Gb, but it did not find anything.
Click to expand...
Click to collapse
Disable auto update in developer options and profit!

Android 10 root issues?

I updated my pixel 2 to the Android 10 stable release this evening .
First thing I did afterwards was root with magisk .
I pulled the boot file, patched it and flashed it.
I opened magisk everything is checked , used Root check app. That came back positive.
However when I try to modify my host file and install my custom host file I get error messages saying " Can't delete file" .
I tried both root explorer and solid explorer both apps have root access . But can't modify the system files.
I'm starting to thing that I'm getting a false positive on root or something has changed in Android 10 and we can no longer modify system files.
I tried both the stable version and canary version builds of magisk . Both say that I'm rooted but the issue persists .
{
"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"
}
Sent from my Pixel 2 using Tapatalk

I saw on another thread after you boot twrp in adb, mount everything as read only and then reinstall twrp and magisk zips thru the recovery. I used most recent versions of twrp and magisk and didn't need to alter the zips in any way. I'll see if I can find the thread....

Couldn't link the thread, so here's a ss

donlu30 said:
Couldn't link the thread, so here's a ss
Click to expand...
Click to collapse
Thanks for the quick reply I don't have. Install a custom recovery in a 2 years lol but it thats what's required to get root to work on the pixel 2 with Android 10 then I'll have to do it
Sent from my Pixel 2

I'm having no problem with IanMacd Magisk repo, link below, check readme on bottom of page for instructions on how to configure Magisk for a custom repo.
https://github.com/ianmacd/MagiskBuilds/

ACHILLES R32 said:
Thanks for the quick reply I don't have. Install a custom recovery in a 2 years lol but it thats what's required to get root to work on the pixel 2 with Android 10 then I'll have to do it
Sent from my Pixel 2
Click to expand...
Click to collapse
You can just boot the recovery if you don't want to install it permanently.
Sent from my Pixel 2 using Tapatalk

Thank you for all the replies, turns out I was rooted but I just couldn't write to system. I ended up installing energized pro module for magisk to modify my host file. No more ads lol
Sent from my Pixel 2

I could also root my pixel 2 with canary_magisk but, although its says rooted, some apps say couldn't find the root binary's. Going back to Android 9

So I seem to have an issue with solid explorer. I go in and remove gmail and other google stuff I don't use typically. Solid gets permissions and when I go to delete the gmail folder it errors out. Not certain if this is a root issue with Magisk or perhaps more likely an issue with apps that need root...