Database Develop

AT&T Galaxy S6 Active will not update

Hi I have a problem from going to 5.1.1 from 5.0.2. I have tried clearing cache,
I have 9gb free,
made sure everything is up to date and enabled,
and have factory reset my phone.
Still doesn't work.
Says something about "dm- verity verification fail" if I go into that developer screen when you hold power, home and volume up right after it tries to update again while loading.
Never has been rooted and have had it for a few months now. Also I was wondering if I could root this phone and just manually update it with custom firmware and forget about Ota updates anymore and be able to run the latest and greatest firmware. I have read in a few places that the new bootloader is un-cracked though and can't be rooted? Thanks.

DaMonsterMonster said:
Hi I have a problem from going to 5.1.1 from 5.0.2. I have tried clearing cache,
I have 9gb free,
made sure everything is up to date and enabled,
and have factory reset my phone.
Still doesn't work.
Says something about "dm- verity verification fail" if I go into that developer screen when you hold power, home and volume up right after it tries to update again while loading.
Never has been rooted and have had it for a few months now. Also I was wondering if I could root this phone and just manually update it with custom firmware and forget about Ota updates anymore and be able to run the latest and greatest firmware. I have read in a few places that the new bootloader is un-cracked though and can't be rooted? Thanks.
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist. To get you the specific help you need, I'm going to move this thread to your device's Q&A forum. Good luck!

The_Merovingian said:
Greetings,
Thank you for using XDA Assist. To get you the specific help you need, I'm going to move this thread to your device's Q&A forum. Good luck!
Click to expand...
Click to collapse
Awesome thanks!

Hi there! Have you tried options 1 & 2 in this HOWTO guide?
DaMonsterMonster said:
Awesome thanks!
Click to expand...
Click to collapse

lirex said:
Hi there! Have you tried options 1 & 2 in this HOWTO guide?
Click to expand...
Click to collapse
#1 didn't show any update but I did go to the samsung kiosk in best buy. He said he has had this problem with phones on other carriers too and he flashed it! Still would like to know if anyone is working on rooting these...

DaMonsterMonster said:
#1 didn't show any update but I did go to the samsung kiosk in best buy. He said he has had this problem with phones on other carriers too and he flashed it! Still would like to know if anyone is working on rooting these...
Click to expand...
Click to collapse
Would love a root, but if the rumors are true, that a new S7 Active version will be announced in Jan and released in Mar, and the new S7 Active (still likely only an AT&T exclusive...) has noticeable improvements, perhaps a root solution for this phone may fall to the way-side.
I'm on the fence about getting an S6, kinda waiting to see if I can get any confirmed specs for a new S7.
Argh... tough...

Nexus 6 shows 4,000% battery life after root?

I got my Nexus 6P for Christmas, and I decided to root my Motorola Nexus 6 from last year. I've been waiting to do this for a few months, and was excited to finally enable several of the options I couldn't otherwise enable (such as double tap to wake and auto rotate on the lock screen and Google Now launcher). About an hour ago I got around to rooting and done so with little issues. It's been a little under an hour since I rooted, and I just now noticed that the battery life is being displayed as having over 4,000% charge. I rooted following the steps in a YouTube video by DroidModderX and the device is running perfectly fine. The device hasn't died yet, and I'll be interested to see when it will die. The battery life seems to fluctuate between 4,001% and 4,204% (Those two figures being the highest and lowest figures respectively). Rebooting does not fix this error.
I know it's not a massive problem, but I'd like to know what's causing this issue and how to resolve it. I haven't flashed any custom OS's on my phone, I'm still running stock Android 6.0.1 Marshmallow with the latest December security patches. The device is carrier unlocked also. How can I fix this?
Thanks,
Eamonn.

sonic2kk said:
It's been a little under an hour since I rooted, and I just now noticed that the battery life is being displayed as having over 4,000% charge. being the highest and lowest figures respectively). Rebooting does not fix this error.
Click to expand...
Click to collapse
You need to use updated root files. The battery issue arises when you're on 6.0.1 but aren't using the right file version. Easily fixed not to worry, just re-root with updated files and it will resolve with no lasting harm.

sansnil said:
You need to use updated root files. The battery issue arises when you're on 6.0.1 but aren't using the right file version. Easily fixed not to worry, just re-root with updated files and it will resolve with no lasting harm.
Click to expand...
Click to collapse
Ah, thank goodness. I'll re-root tomorrow and post back if I have any problems. Thanks!

Thanks, that fixed the issue. I re-rooted and everything is working fine. I flashed the ElementalX kernel. However on boot I now get a warning with a red triangle saying "Your device is corrupt. It cannot be trusted and may not work properly". This warning goes away, and the phone proceeds to boot up successfully. Everything on the device works perfectly fine with no issues. I am successfully rooted running Android Marshmallow 6.0.1, but this screen scares me somewhat. I rooted my Galaxy SII and I have a yellow triangle on boot but only on the Samsung splash screen. Is this something new in Android M or something unique to Nexus devices? I researched this a bit and found one post on Reddit that said this happened in the M previews, and that it was nothing to be concerned about. Is there a way to remove this screen, or is it just like the yellow triangle on the SII? Should I even be concerned with this, or is it something to just dismiss? Is my device at risk any more than normal when rooting, and have I done something wrong? I'm a bit of a newbie at the rooting stuff, but I intend to use my Nexus 6 and SII to learn more about it (and my 6P way into the future, once I get a new phone).
Thanks in advance.

Why did you need root for the Google now launcher?

mikeprius said:
Why did you need root for the Google now launcher?
Click to expand...
Click to collapse
What do you mean? I can run the Google Now launcher perfectly fine. Root works fine as well. The problem isn't with the Google Now launcher but with the warning on boot. I didn't need to root, I chose to. Am I misunderstanding?

Your original post made it seem like you need root for double tap to wake and Google now launcher.

sonic2kk said:
Thanks, that fixed the issue. I re-rooted and everything is working fine. I flashed the ElementalX kernel. However on boot I now get a warning with a red triangle saying "Your device is corrupt. It cannot be trusted and may not work properly". This warning goes away, and the phone proceeds to boot up successfully. Everything on the device works perfectly fine with no issues. I am successfully rooted running Android Marshmallow 6.0.1, but this screen scares me somewhat. I rooted my Galaxy SII and I have a yellow triangle on boot but only on the Samsung splash screen. Is this something new in Android M or something unique to Nexus devices? I researched this a bit and found one post on Reddit that said this happened in the M previews, and that it was nothing to be concerned about. Is there a way to remove this screen, or is it just like the yellow triangle on the SII? Should I even be concerned with this, or is it something to just dismiss? Is my device at risk any more than normal when rooting, and have I done something wrong? I'm a bit of a newbie at the rooting stuff, but I intend to use my Nexus 6 and SII to learn more about it (and my 6P way into the future, once I get a new phone).
Thanks in advance.
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=24269982087021512 gives you 6.0.1 bootstack for Nexus 6 (shamu). Flash this in TWRP. This should fix your corrupted boot splash screen. It's new in Android M when you've installed custom kernel and/or roms. It does not hurt anything except Android Pay is unlikely to work once rooted.
EDIT: I forgot to included mmb29k, non-encrypt boot.img made by GerardF: https://www.androidfilehost.com/?fid=24340319927534323 (flash this also after you flash the bootstack).

HueyT said:
(removed url) gives you 6.0.1 bootstack for Nexus 6 (shamu). Flash this in TWRP. This should fix your corrupted boot splash screen. It's new in Android M when you've installed custom kernel and/or roms. It does not hurt anything except Android Pay is unlikely to work once rooted.
EDIT: I forgot to included mmb29k, non-encrypt boot.img made by GerardF: (removed url) (flash this also after you flash the bootstack).
Click to expand...
Click to collapse
Worked perfect. That got rid of the corrupt message. One last question: (This is the last one, I swear! ) Are you saying that Android Pay won't work at all after rooting or that it wouldn't have worked if that screen had have appeared on boot? I hope to use the service if and when it comes to the UK.
mikeprius said:
Your original post made it seem like you need root for double tap to wake and Google now launcher.
Click to expand...
Click to collapse
Ah, sorry for the confusion my friend ?

I would have kept it at 4,000% - that's like 2 weeks of battery life with no charge...

orangekid said:
I would have kept it at 4,000% - that's like 2 weeks of battery life with no charge...
Click to expand...
Click to collapse
Haha if it wasn't a display error I might have (Though it would have only been like 3 days on the Nexus 6 )

Stupid question but where do I get updated files. I followed the method on root junky for the Nexus 6

Dalek Caan said:
Stupid question but where do I get updated files. I followed the method on root junky for the Nexus 6
Click to expand...
Click to collapse
Sorry, I don't remember where I got the updated files now. I do remember sticking to looking on XDA and not just searching randomly online, maybe you could try searching the forums?

is it possible to root with chainfire root files. I did a clean install of the January security update, then flashed the latest boot.img from chainfire then flashed SuperSU 2.66.zip through TWRP, but im still getting this. I received this same issue with the last patch. Im at the point where it isnt worth rooting. Any help would be appreciated.

Xposed Issue

- FIXED -
I keep trying to install an alternate version of xposed by wanam on my phone. i've flashed it multiple times today and always the same thing, I never progress from the "samsung galaxy note 4" screen after I reboot. Or sometimes, I do end up on the tmobile screen, but still my phone doesn't go anywhere from there.
I'm on MM.
any help?
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960 flashed this version of xposed
I think I read somewhere that my selinux had to be set to permissive, but I'm not sure how to do that. I've checked multiple threads and tried a lot of things but I just cant seem to get it to work.

I'm having this same issue.

joelle_sin said:
I keep trying to install an alternate version of xposed by wanam on my phone. i've flashed it multiple times today and always the same thing, I never progress from the "samsung galaxy note 4" screen after I reboot. Or sometimes, I do end up on the tmobile screen, but still my phone doesn't go anywhere from there.
I'm on MM.
any help?
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960 flashed this version of xposed
I think I read somewhere that my selinux had to be set to permissive, but I'm not sure how to do that. I've checked multiple threads and tried a lot of things but I just cant seem to get it to work.
Click to expand...
Click to collapse
Sorry things aren't working so good for you. I personally am running a clean odined MM FW with the 1st exposed listed on the thread you linked. SE Enforcing. Verifying checksums are a must. Also full wipes are pretty much mandatory prior to flashing FW upgrades
I am rooted and running TWRP 3.0.2. Everything is working superb. I came from a custom LL rom. Maybe if you could give some details about your flashes to MM prior to exposed it would be easier to help out.

ganns1980 said:
I'm having this same issue.
Click to expand...
Click to collapse
someone on another thread helped me. if you have note 4 with marshmallow, and the normal arm build doesn't work for you, download the alternative that's in the downloads. it worked for me.

Installing Custom Recovery on Rooted ATT Galaxy Note 3 with Lollipop 5.0

Disclaimer: I am not an expert in this field by any means and am just figuring a lot of this out for the first time. I need some help but will appreciate your patience! : )
I recently completed the Step by step tutorial to upgrade my ATT Galaxy Note 3 to Lollipop and Root it, provided here: droidviews.com/update-att-note-3-with-lollipop-ota-and-root-it
Everything seems to have worked out, despite a few errors on my behalf (forgot to back up and boot loop forced me to factory reset and start over. Oops), but now I'm stuck trying to figure out how to get Xposed Framework installed. Since I'm now upgraded to Lollipop, I no longer have access to Safestrap, so I tried to install the Xposed Framework in the stock recovery, which failed. Also, I did confirm that I have Root.
Everything I've read states I need to use custom recovery, such as TWRP, but I can't find a way to install it on my device.
Can somebody please help me out here?

Anyone have any idea if Xposed Framework can be installed on Note 3 w/ Lollipop 5.0 using FlashFire?

MJohnson2k8 said:
Anyone have any idea if Xposed Framework can be installed on Note 3 w/ Lollipop 5.0 using FlashFire?
Click to expand...
Click to collapse
It can, I've done it before. Worked perfectly.

Magisk is not installed 20.4

Hello, i hope i'm posting this in the right place. I'll try to be as short and descriptive as i can about my situation.
I tried to root a phone first time ever and i have no skill in this type of thing whatsoever. I followed a video for instructions and ended up with "Magisk is not installed."
The phone i tried this on is a Galaxy Note 9, model number SM-N960F. Android version 10.
I used Odin3 v3.13.1, twrp-3.2.3-0-crownlte_UNOFFICIAL and N9_S9_Root_for_OEM_issue_devices_V3.
I also uninstalled/reinstalled MagiskManager and tried a newer version.
Currently i'm stuck and in a pit of despair without a clue what to do next. Any help is greatly appreciated.
*EDIT i'm currently looking at 1 click rooting methods, but this might be a bad idea.

plan3tgreen said:
Hello, i hope i'm posting this in the right place. I'll try to be as short and descriptive as i can about my situation.
I tried to root a phone first time ever and i have no skill in this type of thing whatsoever. I followed a video for instructions and ended up with "Magisk is not installed."
The phone i tried this on is a Galaxy Note 9, model number SM-N960F. Android version 10.
I used Odin3 v3.13.1, twrp-3.2.3-0-crownlte_UNOFFICIAL and N9_S9_Root_for_OEM_issue_devices_V3.
I also uninstalled/reinstalled MagiskManager and tried a newer version.
Currently i'm stuck and in a pit of despair without a clue what to do next. Any help is greatly appreciated.
*EDIT i'm currently looking at 1 click rooting methods, but this might be a bad idea.
Click to expand...
Click to collapse
I've done so many factory resets and wipes(somewhere in the 20s.) I have finally given up on this. Because now i've ended up stuck, impossible to get past ODIN. I get this wonderful little message: "Only official released binaries are allowed to be flashed."

plan3tgreen said:
I've done so many factory resets and wipes(somewhere in the 20s.) I have finally given up on this. Because now i've ended up stuck, impossible to get past ODIN. I get this wonderful little message: "Only official released binaries are allowed to be flashed."
Click to expand...
Click to collapse
I'm downloading a stock and will attempt it later in odin.

plan3tgreen said:
I'm downloading a stock and will attempt it later in odin.
Click to expand...
Click to collapse
Still getting "Only official released binaries are allowed to be flashed(RECOVERY)."
By the way thanks for helping, i'll be sure to voice my opinion about how helpful this place is.

plan3tgreen said:
Still getting "Only official released binaries are allowed to be flashed(RECOVERY)."
By the way thanks for helping, i'll be sure to voice my opinion about how helpful this place is.
Click to expand...
Click to collapse
Give it time for someone to be able to help.
Not everyone has a note 9 and should be posted on note 9 forums.
The reasons why you are getting official binary error is OEM is locked and/or you have KG and/or Rmm state being in prenornal state.

plan3tgreen said:
Hello, i hope i'm posting this in the right place. I'll try to be as short and descriptive as i can about my situation.
I tried to root a phone first time ever and i have no skill in this type of thing whatsoever. I followed a video for instructions and ended up with "Magisk is not installed."
The phone i tried this on is a Galaxy Note 9, model number SM-N960F. Android version 10.
I used Odin3 v3.13.1, twrp-3.2.3-0-crownlte_UNOFFICIAL and N9_S9_Root_for_OEM_issue_devices_V3.
I also uninstalled/reinstalled MagiskManager and tried a newer version.
Currently i'm stuck and in a pit of despair without a clue what to do next. Any help is greatly appreciated.
*EDIT i'm currently looking at 1 click rooting methods, but this might be a bad idea.
Click to expand...
Click to collapse
With those phones I'm pretty sure you have to power the phone on by pressing vol up and power, then release the two when you see the bootloader warning screen. This boots the phone into root mode. Just pressing power normally boots them into normal mode.

GeeAyeZee said:
With those phones I'm pretty sure you have to power the phone on by pressing vol up and power, then release the two when you see the bootloader warning screen. This boots the phone into root mode. Just pressing power normally boots them into normal mode.
Click to expand...
Click to collapse
this was just my issue.
after following {awebsite}topjohnwu.github.io/Magisk/install.html, to the letter and going round in circles, it was this simple bit that i was missing.
once magisk has gone through the process once, it seems that the root is applied automatically going on.
as a hint, if you install titanium backup *root required* from the play store, then you can check very quickly if you presently have root or not.