Develop Bugs

Towelroot. Is it working on the G3?

Did someone try to root the G3 with Towelroot?
http://towelroot.com/

Yes, it will. Even on the S5 without tripping KNOX. Just try it yourself, no risk involved. I haven`t tried it myself but i`am absolutely sure it will get you root.

Good to know.
I should get my G3 next week so I will definitely use it.
Thanks.

liamR said:
Did someone try to root the G3 with Towelroot?
http://towelroot.com/
Click to expand...
Click to collapse
Just confirmed with my international D855 unit.
Works flawlessly. Tested with Root checker and Titanium backup.
Still dazed as to how this works... possibly the fastest root method ever! :good:

MasK said:
Just confirmed with my international D855 unit.
Works flawlessly. Tested with Root checker and Titanium backup.
Still dazed as to how this works... possibly the fastest root method ever! :good:
Click to expand...
Click to collapse
Appearently its a vulnurability in all android kernels that are build before june 3rd that lets the exploit do its work and install root during the boot sequence without beeing detected.

Yes. It's amazing. This guy have a great talent. He just left the iOS system and went for Android (He developed the iOS Jailbreak). Now Chainfire and other good developers here have competition

Working good

To unroot do u just need to do a reset? This works on uk model g3 with 2gb ram?
Sent from my LG-D855 using XDA Premium 4 mobile app

vimto25 said:
To unroot do u just need to do a reset? This works on uk model g3 with 2gb ram?
Sent from my LG-D855 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes, it works with all android devices atm and a data factory reset or flashing a factory image will unroot.

warranty still void tho I guess? I'm wanting to root really badly, but holding off as long as I can in case of problems as phone is litteraly hours old

557953 said:
warranty still void tho I guess? I'm wanting to root really badly, but holding off as long as I can in case of problems as phone is litteraly hours old
Click to expand...
Click to collapse
I've never worried about the 'warranty voided' stories. If software could physically damage a device then the device is poorly made. I had three different rooted Samsung that failed due to the 'sudden death syndrome'. They were all fixed under warranty. Never heard of anyone having problems with warranty on a rooted device - only urban myths!
Sent from my SM-9500N using Tapatalk Pro.
If you find my post useful, a click on the 'thanks' is appreciated.

557953 said:
warranty still void tho I guess? I'm wanting to root really badly, but holding off as long as I can in case of problems as phone is litteraly hours old
Click to expand...
Click to collapse
Rooting has always voided warranty. .. There were just ways to return it to stock like it was never rooted.
Sent from my SM-N900P using Xparent BlueTapatalk 2

Epix4G said:
Rooting has always voided warranty. .. There were just ways to return it to stock like it was never rooted.
Click to expand...
Click to collapse
Not with my rooted phones - any that died or had faults have always been fixed under warranty - going right back to the 'Hero'. If I buy a brand name Windows PC, wipe the hard disk and install Linux, the manufacturer still has to honour their hardware warranty under EU law. Same with mobiles/phones/tablets.
Maybe North American consumer protection laws are not as good as those here in Europe.
For instance, in the EU we can return anything we buy via mail order for a full refund within 14 days for any reason under the 'distance selling' regulations. Goods bought in shops or via mail order also have to be of 'merchantable quality'. As it currently stands, EU customers could obtain a full refund for the LG G3 as it does not work reliably with the Google Chromecast. This is probably why Samsung fixed a similar problem with a software patch when some of their devices had the same problem.
Sent from my SM-9500N using Tapatalk Pro.
If you find my post useful, a click on the 'thanks' is appreciated.

Sucessfully rooted my D855 using Towelroot as well.Tested with root checker and adblock to verify it's working.
One problem I had was when I installed SuperSU,it says need to have binary updated.However,when I clicked "Normal"..it says installation failed?

JxXxn said:
Sucessfully rooted my D855 using Towelroot as well.Tested with root checker and adblock to verify it's working.
One problem I had was when I installed SuperSU,it says need to have binary updated.However,when I clicked "Normal"..it says installation failed?
Click to expand...
Click to collapse
Yup.. likewise with SuperSU.
I uninstalled it and never bothered with it

To unroot, can somebody install SuperSu and try to uninstal root pls?
Sent from my LG-D855 using Tapatalk

qwerty1q said:
To unroot, can somebody install SuperSu and try to uninstal root pls?
Sent from my LG-D855 using Tapatalk
Click to expand...
Click to collapse
Doing so removes your root access (as you expect) but your device will still refuse to install OTA's
Sent from my LG G3

JxXxn said:
Sucessfully rooted my D855 using Towelroot as well.Tested with root checker and adblock to verify it's working.
One problem I had was when I installed SuperSU,it says need to have binary updated.However,when I clicked "Normal"..it says installation failed?
Click to expand...
Click to collapse
MasK said:
Yup.. likewise with SuperSU.
I uninstalled it and never bothered with it
Click to expand...
Click to collapse
Alright.. I decided to try it again and now SuperSU works flawlessly.
I think you need to reboot and run it again. This time for me, it didn't ask me for a binary update. Just started working. Try it.

Lennyuk said:
Doing so removes your root access (as you expect) but your device will still refuse to install OTA's
Sent from my LG G3
Click to expand...
Click to collapse
OK so I can unroot with SuperSu, the only disadvantage is no OTA, and to unroot with OTA I'd need to perform factory reset, right? How to do it?
After Factory reset,
Do LG backup app restore the whole rom with settings and apps, please?
Sent from my LG-D855 using Tapatalk

MasK said:
Alright.. I decided to try it again and now SuperSU works flawlessly.
I think you need to reboot and run it again. This time for me, it didn't ask me for a binary update. Just started working. Try it.
Click to expand...
Click to collapse
Yes..it works now!And Hello from yr fellow Singaporean!!

Android Marshmallow G4 Root

When android Marshmallow releases will we still be able to root our devices with the low effort root available now?

cmetzger93 said:
When android Marshmallow releases will we still be able to root our devices with the low effort root available now?
Click to expand...
Click to collapse
Sure will! But I hear it'll interfere with holographic display mode. That is, assuming President Trump doesn't veto the "Holographic Display Act."
.....oops, I've said too much!

joshw0000 said:
Sure will! But I hear it'll interfere with holographic display mode. That is, assuming President Trump doesn't veto the "Holographic Display Act."
.....oops, I've said too much!
Click to expand...
Click to collapse
So much sarcasm! I assume that is a no then? Lol

cmetzger93 said:
So much sarcasm! I assume that is a no then? Lol
Click to expand...
Click to collapse
Oops, my crystal ball was acting up. Sorry I couldn't be of more help.
Sent from my VS986 using Tapatalk

I'll be the serious guy...
Theoretically (meaning I take no responsibility for what might/might not happen, and of course have not seen confirmation of this working except over Lollipop)...yes you could root with the low effort root if you're on M.
All you're doing is flashing a rooted Lollipop image over the stock one, so yeah you'd be going back to Lollipop but yeah you'd also be rooted. It's a downgrade but I suppose it would do for the time being if you really wanted root and for some reason took the M upgrade without wanting to.

Cwey55 said:
I'll be the serious guy...
Theoretically (meaning I take no responsibility for what might/might not happen, and of course have not seen confirmation of this working except over Lollipop)...yes you could root with the low effort root if you're on M.
All you're doing is flashing a rooted Lollipop image over the stock one, so yeah you'd be going back to Lollipop but yeah you'd also be rooted. It's a downgrade but I suppose it would do for the time being if you really wanted root and for some reason took the M upgrade without wanting to.
Click to expand...
Click to collapse
I appreciate the serious answer very much. It was very insightful

Cwey55 said:
I'll be the serious guy...
Theoretically (meaning I take no responsibility for what might/might not happen, and of course have not seen confirmation of this working except over Lollipop)...yes you could root with the low effort root if you're on M.
All you're doing is flashing a rooted Lollipop image over the stock one, so yeah you'd be going back to Lollipop but yeah you'd also be rooted. It's a downgrade but I suppose it would do for the time being if you really wanted root and for some reason took the M upgrade without wanting to.
Click to expand...
Click to collapse
I don't think the Lollipop image would work. Root would need to be injected into a M image.
Sent from my VS986 using Tapatalk

The reason he was being sarcastic is because there is no way to know if we can root M until it actually comes out. It's like asking if the LG G5 will be rootable, no way to know until it's out.

hollywoodS14 said:
I don't think the Lollipop image would work. Root would need to be injected into a M image.
Sent from my VS986 using Tapatalk
Click to expand...
Click to collapse
I tend to agree, I was just saying in theory it would work...
People used to downgrade from LP to KK with pre-rooted images.
But yeah the 100% surefire answer at this point is who freakin knows. I'm sure a root will come along eventually, just gotta give the developers some time.

In all seriousness it most likely will not work. Android M will almost certainly come with upgraded boot.img, etc and most new phones with locked bootloaders are preventing downgrading and/or preventing of unsigned images so its quite likely we will not be able to downgrade. This is my first locked LG device so I could be wrong about the G4.
Sent from my VS986 using Tapatalk

Yea no one really knows. Lollipop really made rooting complicated. Phones like the G2 and G3 were able to use older partition firmwares that were still rootable but required KitKat parts. With the G4 having stock lollipop, it was more complicated.
I suspect that we will always be able to root similarly how we did already. The USB>COM>flash a custom rooted system image should still be an option. This method is how the LG updater tool works. If they block access to that, then everything will break.
I have faith that we will be ok but like everyone said above, we won't know until it is released.

joshw0000 said:
In all seriousness it most likely will not work. Android M will almost certainly come with upgraded boot.img, etc and most new phones with locked bootloaders are preventing downgrading and/or preventing of unsigned images so its quite likely we will not be able to downgrade. This is my first locked LG device so I could be wrong about the G4.
Sent from my VS986 using Tapatalk
Click to expand...
Click to collapse
Does anybody know if we can install the update while already rooted on the T-Mobile variant?

Toast67 said:
Does anybody know if we can install the update while already rooted on the T-Mobile variant?
Click to expand...
Click to collapse
If that bootloader is unlocked and the good ol' legendary Chain man has a nice, sweet, hot binary in SuperSU to shove up that there thang. Then, I don't see why not. You can root through TWRP or whatever custom recovery you choose to use to overwrite the partition when you're boot scootin' boogied.

Google is really trying to lock their OS down. They make it harder to root, and now Android Pay won't work on rooted phones and they have an API for developers now to restrict or prevent use if the OS is modified.

This is a stupid question that's why it was answered sarcatically. Its a new version, so when root is out it would be posted or if someone tries the old root and it worked they would post it. Otherwise you would ask if anyone is working on the root. You basically asked if a new phone coming out if it will be rootable.
Also why are people asking tmobile questions in a verizon thread.

No root possible on verizon MM. They plugged the hole so we are no longer able to pull and push the rooted system images like we were.
The V10 is facing a similar issue and they've been at it longer. So until then, I just disabled the System Update app in settings.

ARGGGHHH
Well, We will need to Find a way to Roll Back or Root M, Guess I'm Stuck For now. (Wife decided We both needed the OTA (Last Time I sleep later than her -EVER-))

Exerp said:
Well, We will need to Find a way to Roll Back or Root M, Guess I'm Stuck For now. (Wife decided We both needed the OTA (Last Time I sleep later than her -EVER-))
Click to expand...
Click to collapse
Someone in the general thread "6.0 marshmallow is out!!!" thread mentioned that he had success downgrading.
tulio25 said:
I just successfully downgraded from 24C to 13b with LGUP (version 1.14) tool.Used 'refurbished' mode on LGUP.So,now we know:This MM upgrade is downgradable to 13B Lollipop! By the way,what a relief,didn't like MM,but that's my feeling,anyway
Click to expand...
Click to collapse

Too good to be true ?
I wonder if this works:
How to root the LG G4 VS986 Marshmallow 6.0.1
https://www.search4roots.com/how-to-easily-root-lg-g4-vs986-marshmallow-6-0-1/
Seems too good to be true if I have not read about in on XDA VS986 forum yet
The VS986 does not show up on their rootable list: https://www.oneclickroot.com/rootable/ , so I guess that page is just a teasing advertisement .....
Gosh, talk about shameless advertising .... a YouTube video showing the VS986 MM 6.0.1 too

divineBliss said:
I wonder if this works:
How to root the LG G4 VS986 Marshmallow 6.0.1
https://www.search4roots.com/how-to-easily-root-lg-g4-vs986-marshmallow-6-0-1/
Seems too good to be true if I have not read about in on XDA VS986 forum yet
The VS986 does not show up on their rootable list: https://www.oneclickroot.com/rootable/ , so I guess that page is just a teasing advertisement .....
Gosh, talk about shameless advertising .... a YouTube video showing the VS986 MM 6.0.1 too
Click to expand...
Click to collapse
its fake, if it was real you know about it. good thing you did not do it or you end up with a paper weight

New HTC One M9 Verizon Update?

Anyone know what this is for?

Jrocker23 said:
Anyone know what this is for?
Click to expand...
Click to collapse
Hm. 612 megs. That could be....well let's see.
Sent from my Nexus 6 using Tapatalk

Installed and currently on the Android is upgrading/Optimizing apps screen...... Hopefully won't take too much longer.

software repair patch for 5.1 as told by vzw customer service. what it is repairing i dont know
3.10.605.7 / Base: 2.12.C1144073

Nothing different.... Seems just like a security patch.
http://www.verizonwireless.com/support/htc-one-m9-update/

SnoStorm said:
Nothing different.... Seems just like a security patch.
http://www.verizonwireless.com/support/htc-one-m9-update/
Click to expand...
Click to collapse
One can only wonder what the heck verizon does to their software such that it requires a 612meg security patch huh?
Anyhow.. Time to use that nandroid i posed in the dev section to accept the OTA.. -or- I will post an updated one later this evening.

Probably 600mb of updated NFL bloatware included and the rest just the security update.

Any word yet on whether this is really just a 612Meg security patch?

jtommyj said:
Any word yet on whether this is really just a 612Meg security patch?
Click to expand...
Click to collapse
yup, nothing special

Anyone know if letting this thing run and update will break root? I'm stock, rooted. Don't want to lose that and not be able to get it back myself.

baune7 said:
Anyone know if letting this thing run and update will break root? I'm stock, rooted. Don't want to lose that and not be able to get it back myself.
Click to expand...
Click to collapse
are you SOFF? if so, you will be fine

Yes.. I'm s-off and unlocked. So after it updates, will it still be rooted? Or would I havery to re-root it? I'm just worried because my cable Internet isn't working for a few days and I need my wifi tether. Thanks

Ran into an issue with this update. It failed to install on 11/3 with a error code 409, but when I try to download it again by selecting "Check for new system updates" it says I have the latest update. I've rebooted a number of times and it shows up every time. From what little information I can find online, I have to reset my phone to factory then attempt to update again. I want to avoid this so here I am.
I'm on my phone so I can't properly upload the screenshots. I posted Google Drive links for now
https://drive.google.com/file/d/0B__V8WYcxeW8dkVxOXktZXZHcVU/view?usp=sharing
https://drive.google.com/file/d/0B__V8WYcxeW8YWdsU1kyMmZOcFk/view?usp=sharing

gumbyx84 said:
Ran into an issue with this update. It failed to install on 11/3 with a error code 409, but when I try to download it again by selecting "Check for new system updates" it says I have the latest update. I've rebooted a number of times and it shows up every time. From what little information I can find online, I have to reset my phone to factory then attempt to update again. I want to avoid this so here I am.
I'm on my phone so I can't properly upload the screenshots. I posted Google Drive links for now
https://drive.google.com/file/d/0B__V8WYcxeW8YWdsU1kyMmZOcFk/view?usp=docslist_api
https://drive.google.com/file/d/0B__V8WYcxeW8dkVxOXktZXZHcVU/view?usp=docslist_api
Click to expand...
Click to collapse
Flash the custom firmware zip and restore the nandroid I posted of the update. Then wipe data for the app htcdm. Flash supersu.zip and you're done.
Sent from my Nexus 6 using Tapatalk

dottat said:
Flash the custom firmware zip and restore the nandroid I posted of the update. Then wipe data for the app htcdm. Flash supersu.zip and you're done.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I'm not rooted.
Update: I decided to just to a factory reset. Thankfully it worked and I am at the latest firmware.

So I've tried letting this update run a couple times. Downloading for the third time as I write this. When it tries to install, it just reboots into TWRP recovery and does nothing. Then I restart the phone and basically start the process all over again. Any guidance on how to get this squared away?? I met one of the members here with a card who S-offed, unlocked, rooted, my phone which I'm thankful for. Just want to be stock rooted is all. Don't really do much with custom roms on this phone. Thanks.

baune7 said:
So I've tried letting this update run a couple times. Downloading for the third time as I write this. When it tries to install, it just reboots into TWRP recovery and does nothing. Then I restart the phone and basically start the process all over again. Any guidance on how to get this squared away?? I met one of the members here with a card who S-offed, unlocked, rooted, my phone which I'm thankful for. Just want to be stock rooted is all. Don't really do much with custom roms on this phone. Thanks.
Click to expand...
Click to collapse
I'm pretty sure you need stock recovery to take an OTA.

SigLover21 said:
I'm pretty sure you need stock recovery to take an OTA.
Click to expand...
Click to collapse
Ok.. Thanks.. I'll have to check into that

Successful Root - Samsung Galaxy Note 4, Just one drawback...

Hello all,
I was testing and fooling around with my Note 4 SM-910A when I tried rooting my phone again. (Manually) and I did something different giving me root and the bootloader now shows the Custom (unlocked) symbol. Meaning, that I got root and my bootloader was unlocked. Here is some proof:
imgur (DOT) com/2qjJmWs
But there is one catch to it.
You get bricked. AT&T sees that you are rooted and you cannot use your phone unless you restore it to stock or you take it to AT&T store and they will do it for you.
Also you get a : SECURE = FAIL on your scree.
When I got this root, I made an account quickly and then I posted. This is the biggest day for me. I'm gonna try and see if I can bypass the SECURE = FAIL and make it into SECURE = I DON'T EVEN CARE!
--Sarmad Wahab
--Android Rootivist

Hahahahahahahaa
Sent from my SM-N910T using Tapatalk

No kidding
getyroks said:
Hahahahahahahaa
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
Dude, no kidding this just happened to me like 10 minutes ago. I'll be going to AT&T store, like the phone said. I will see what they do.

If you look into the root progress forum, a couple of us has had the same thing happen. I am hoping that some devs are looking into this. I know how to do this every time now and have to unbrick my phone every time.
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app

http://forum.xda-developers.com/showthread.php?p=65784783
Look into this here.
I have done this more than 10 times trying various root procedures to stick on reboot. I'm sure there are A LOT of other that have had this happen also. It's not new.

What a troll. New user sign up, 1st post said ROOTED. LOL

getyroks said:
Hahahahahahahaa
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
sweetboy02125 said:
What a troll. New user sign up, 1st post said ROOTED. LOL
Click to expand...
Click to collapse
Bro, not a troll. My note 4 is now permanently bricked. The os was deleted by the bootloader. I took it to Att and they say that it is permanently bricked. Hard-bricked. Gonna send it to samsung or go to another att store to see wut happenes.

No. No. No. Nonononono
I hope you didn't send it in yet.
Go here-> http://forum.xda-developers.com/showthread.php?p=63431559
Download needed files and don't forget about Odin program.
As I stated earlier, I have done this over 10 times trying various root methods to stick. If you weren't so noobish in thinking AT&T was going to help you...maybe you could read around on these awesome forums and figure it out for yourself... but alas, you can lead a horse to water, blah blah blah...

Walt
I had the same thing happen to me. King root app popped & asked me to try again so I did. (Stupid me) I tried everything I know how to fix this.. In recovery mode I told phone to wipe data factory reset. Still pops up after reboot stating kernal is not seaddroid enforcing then says secure fail kernel and had large yellow triangle saying system software not authorized by at&t has been found etc. Turn off and take to at&t store.
Anyone know how to fix this or have I ruined the phone?

getyroks said:
No. No. No. Nonononono
I hope you didn't send it in yet.
Go here-> http://forum.xda-developers.com/showthread.php?p=63431559
Download needed files and don't forget about Odin program.
As I stated earlier, I have done this over 10 times trying various root methods to stick. If you weren't so noobish in thinking AT&T was going to help you...maybe you could read around on these awesome forums and figure it out for yourself... but alas, you can lead a horse to water, blah blah blah...
Click to expand...
Click to collapse
cboysfan said:
I had the same thing happen to me. King root app popped & asked me to try again so I did. (Stupid me) I tried everything I know how to fix this.. In recovery mode I told phone to wipe data factory reset. Still pops up after reboot stating kernal is not seaddroid enforcing then says secure fail kernel and had large yellow triangle saying system software not authorized by at&t has been found etc. Turn off and take to at&t store.
Anyone know how to fix this or have I ruined the phone?
Click to expand...
Click to collapse
use the link @getyroks posted, it unbricked my phone!

---------- Post added at 03:11 PM ---------- Previous post was at 03:08 PM ----------
[/COLOR]
cboysfan said:
I had the same thing happen to me. King root app popped & asked me to try again so I did. (Stupid me) I tried everything I know how to fix this.. In recovery mode I told phone to wipe data factory reset. Still pops up after reboot stating kernal is not seaddroid enforcing then says secure fail kernel and had large yellow triangle saying system software not authorized by at&t has been found etc. Turn off and take to at&t store.
Anyone know how to fix this or have I ruined the phone?
Click to expand...
Click to collapse
Please read the whole thread instead of asking to be spoon-fed, don't be lazy. READ, SEARCH,and RESEARCH!!!
Sent from my SM-N910T using Tapatalk

getyroks said:
No. No. No. Nonononono
I hope you didn't send it in yet.
Go here-> http://forum.xda-developers.com/showthread.php?p=63431559
Download needed files and don't forget about Odin program.
As I stated earlier, I have done this over 10 times trying various root methods to stick. If you weren't so noobish in thinking AT&T was going to help you...maybe you could read around on these awesome forums and figure it out for yourself... but alas, you can lead a horse to water, blah blah blah...
Click to expand...
Click to collapse
Dude thank you soo much, I got my phone fixed, and also I got my note 3 fixed using files from the same person

getyroks said:
---------- Post added at 03:11 PM ---------- Previous post was at 03:08 PM ----------
[/COLOR]
Please read the whole thread instead of asking to be spoon-fed, don't be lazy. READ, SEARCH,and RESEARCH!!!
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
Wow. Don't be lazy. Not cool dude. I did read the whole post and I am trying what was listed. Anyway I wanted to add that my phone has never been rooted. I have tried Kingroot many times with no success. I am running Lollipop 5.1.1 which is locked by AT&T so I am curious if bootloader is locked how this happened or how I will be able to fix this. I will continue to read as I have been doing prior to being called lazy. I have yet to see anyone else state they were running the same OS I am.

cboysfan said:
Wow. Don't be lazy. Not cool dude. I did read the whole post and I am trying what was listed. Anyway I wanted to add that my phone has never been rooted. I have tried Kingroot many times with no success. [bold]I am running Lollipop 5.1.1 which is locked by AT&T so I am curious if bootloader is locked how this happened [\bold]or how I will be able to fix this. I will continue to read as I have been doing prior to being called lazy. I have yet to see anyone else state they were running the same OS I am.
Click to expand...
Click to collapse
The files mentioned in my previous post are the 5.1.1 OS files. I have used them multiple times to recover from a soft-brick. So, YES, I have the same OS Lollipop as you should have. AT&T has locked the bootloader on the Note 4 from the beginning. But in 4.4.4 you could temp-root in order to get rid of some files. But results are so different from phone to phone that a temp-root scenario is complicated to explain. Some work some dont. KINGROOT is also in the same boat, might or not work. You might be able to keep your phone from rebooting or it might freeze and you HAVE to pull the battery. When the battery gets pulled and reboots SOMETIMES you can reboot to a temp-rooted phone, MOST OF THE TIME it soft bricks. All of this information is in either of the posts I linked earlier, so either you're lazy, or you don't understand what you're reading. If you don't understand, then please READ, SEARCH, and RESEARCH.
Sent from my SM-N910T using Tapatalk
Start at the beginning of this here->----->>>http://forum.xda-developers.com/showthread.php?t=2961974

Thank you getyroks.
I was concerned to load the files because I did not see anyone who was not rooted and running my OS. I installed them and all is well. Thank you again.
getyroks said:
The files mentioned in my previous post are the 5.1.1 OS files. I have used them multiple times to recover from a soft-brick. So, YES, I have the same OS Lollipop as you should have. AT&T has locked the bootloader on the Note 4 from the beginning. But in 4.4.4 you could temp-root in order to get rid of some files. But results are so different from phone to phone that a temp-root scenario is complicated to explain. Some work some dont. KINGROOT is also in the same boat, might or not work. You might be able to keep your phone from rebooting or it might freeze and you HAVE to pull the battery. When the battery gets pulled and reboots SOMETIMES you can reboot to a temp-rooted phone, MOST OF THE TIME it soft bricks. All of this information is in either of the posts I linked earlier, so either you're lazy, or you don't understand what you're reading. If you don't understand, then please READ, SEARCH, and RESEARCH.
Sent from my SM-N910T using Tapatalk
Start at the beginning of this here->----->>>http://forum.xda-developers.com/showthread.php?t=2961974
Click to expand...
Click to collapse

cboysfan said:
Thank you getyroks.
I was concerned to load the files because I did not see anyone who was not rooted and running my OS. I installed them and all is well. Thank you again.
Click to expand...
Click to collapse
The sad part is that it cleans the whole system. So starting from scratch everytime is a drag.
Sent from my SM-N910T using Tapatalk

ejectedmatrix said:
use the link @getyroks posted, it unbricked my phone!
Click to expand...
Click to collapse
It helped me as well. Just download the package and use ODIN and you are back in buisness. Btw, all your personal data is gone bye bye though, I will be like a having a brand new phone again.
Take care.
Sent from my SAMSUNG-SM-T537A using XDA Free mobile app

ejectedmatrix said:
Bro, not a troll. My note 4 is now permanently bricked. The os was deleted by the bootloader. I took it to Att and they say that it is permanently bricked. Hard-bricked. Gonna send it to samsung or go to another att store to see wut happenes.
Click to expand...
Click to collapse
1) Not a troll. Just someone not knowing what they're doing.
2) ATT reps don't even know the difference between a locked sim and locked bootloader, so they wouldn't know the difference between a hard and soft brick.
3) All you had to do was use Odin to fix the phone. You just traded your phone for a factory refurbished one. Good job!
4) Read the latest forum posts before doing things.
Sent from my SAMSUNG-SM-N910A using Tapatalk

Hey guys. Thought I'd chime in with a little insight here. Had someone call me the other day that tried to root one, and ended up with the same unauthorized software error. Couldn't get to download mode, couldn't get to recovery, couldn't get phone to boot. He took it to AT&T, where they of course told him the phone was "hard bricked". I just used a usb jig and restored it with odin. Did just fine.
This is the jig I used. It was $4.92 on eBay
http://www.ebay.com/itm/NEW-Samsung...SB-jig-EXCLUSIVELY-US-MADE-SOLD-/141351359584

strabo231 said:
Hey guys. Thought I'd chime in with a little insight here. Had someone call me the other day that tried to root one, and ended up with the same unauthorized software error. Couldn't get to download mode, couldn't get to recovery, couldn't get phone to boot. He took it to AT&T, where they of course told him the phone was "hard bricked". I just used a usb jig and restored it with odin. Did just fine.
This is the jig I used. It was $4.92 on eBay
You wasted $4.92 on ebay, All you got to do is download USB Driver for your phone and install it on your computer. Once this is done, your computer we recognize your soft bricked phone and you can use Odin to reload the firmware.
Click to expand...
Click to collapse

Pixel XL 2 - "Your device is corrupt" after OTA.

Took an OTA and now whenever I turn the device on it says in red letters: "Your device is corrupt. It can't be trusted and may not work properly". I can still boot into the OS normally. I can still access fastboot. I can still access recovery. I have done many searches and people keep saying to relock the bootloader or unlock the bootloader and flash stock firmware. There's no way to do either because this Verizon variant is locked down like Fort Knox. I don't understand why the bootloader has to be unlocked to flash STOCK firmware straight from Verizon. Smh. Anyways, does anyone have any ideas. about how to get rid of this message?

ClassickWORLD said:
Took an OTA and now whenever I turn the device on it says in red letters: "Your device is corrupt. It can't be trusted and may not work properly". I can still boot into the OS normally. I can still access fastboot. I can still access recovery. I have done many searches and people keep saying to relock the bootloader or unlock the bootloader and flash stock firmware. There's no way to do either because this Verizon variant is locked down like Fort Knox. I don't understand why the bootloader has to be unlocked to flash STOCK firmware straight from Verizon. Smh. Anyways, does anyone have any ideas. about how to get rid of this message?
Click to expand...
Click to collapse
You could side load the Google OTA image and see if that fixes it. Or just wait until next week and see if the March OTA fixes it. If your device is working properly, I wouldn't worry too much about it.

Badger50 said:
You could side load the Google OTA image and see if that fixes it. Or just wait until next week and see if the March OTA fixes it. If your device is working properly, I wouldn't worry too much about it.
Click to expand...
Click to collapse
I have moved on to the iPhone 8 Plus. I sold the device and had it returned because of that message... and now I want to sell it again. I just need to get rid of it. So you are saying that I can sideload via adb even on a Verizon device with a locked bootloader?

ClassickWORLD said:
I have moved on to the iPhone 8 Plus. I sold the device and had it returned because of that message... and now I want to sell it again. I just need to get rid of it. So you are saying that I can sideload via adb even on a Verizon device with a locked bootloader?
Click to expand...
Click to collapse
While I haven't done it personally, I've seen several people do just that from stock recovery. At worst, the install will fail and nothing will be changed. Unlocking the bootloader is mainly for flashing factory images and rooting, not OTA's. Just follow the instructions from Google and see what happens. In your current situation, you really have nothing to lose.
https://developers.google.com/android/ota

ClassickWORLD said:
I have moved on to the iPhone 8 Plus. I sold the device and had it returned because of that message... and now I want to sell it again. I just need to get rid of it. So you are saying that I can sideload via adb even on a Verizon device with a locked bootloader?
Click to expand...
Click to collapse
Yes, I have a Verizon version of the Pix2-XL, and I have run 4 or 5 times on it.
https://developers.google.com/android/ota
Use these instructions exactly, and be sure you have the newest Android Tools.
This should take care of your error message.

michaelbsheldon said:
Yes, I have a Verizon version of the Pix2-XL, and I have run 4 or 5 times on it.
https://developers.google.com/android/ota
Use these instructions exactly, and be sure you have the newest Android Tools.
This should take care of your error message.
Click to expand...
Click to collapse
Thanks for the conformation my friend. I kinda feel sorry for that poor guy, he went to an iphone!!.....oh the horror! ??????

michaelbsheldon said:
Yes, I have a Verizon version of the Pix2-XL, and I have run 4 or 5 times on it.
https://developers.google.com/android/ota
Use these instructions exactly, and be sure you have the newest Android Tools.
This should take care of your error message.
Click to expand...
Click to collapse
Hey thanks for that. The latest image I see for the Verizon Pixel XL 2 is for 8.0.0 from Nov 2017. I am on 8.1. So I have to downgrade? Is that even possible?

ClassickWORLD said:
Hey thanks for that. The latest image I see for the Verizon Pixel XL 2 is for 8.0.0 from Nov 2017. I am on 8.1. So I have to downgrade? Is that even possible?
Click to expand...
Click to collapse
Huh?? You have a P2XL right?? It's right there at the bottom of the P2XL section.
What build month are you currently on?

ClassickWORLD said:
Hey thanks for that. The latest image I see for the Verizon Pixel XL 2 is for 8.0.0 from Nov 2017. I am on 8.1. So I have to downgrade? Is that even possible?
Click to expand...
Click to collapse
You do want the February one. It's for all phones including Verizon.

Badger50 said:
Huh?? You have a P2XL right?? It's right there at the bottom of the P2XL section.
What build month are you currently on?
Click to expand...
Click to collapse
So I can flash that with no radio issues? I thought OPM1 is google, OPM2 is Telus only, and OPD3 is Verizon only? I have a Verizon P2XL
Edit: I think I've found my issue. The person who had the device before me must have sideloaded 8.1.0 (OPM1.171019.018, Feb 2018)" to this device and that may be the reason for the error. I am thinking because that's not the Verizon P2XL firmware but the Google P2XL device firmware.

michaelbsheldon said:
You do want the February one. It's for all phones including Verizon.
Click to expand...
Click to collapse
Ok gotcha. Downloading now as we speak.

Badger50 said:
Thanks for the conformation my friend. I kinda feel sorry for that poor guy, he went to an iphone!!.....oh the horror! ??
Click to expand...
Click to collapse
Lol I still have my trusty ol' Nexus 6P as my secondary device.

WoW this download link is really slow. Downloading at 50 KB/s. Says 9 hours left. I have fiber speeds for my internet. Anyone know of any alternative download locations for this OTA?
Edit: Rebooted my router and that fixed it. It downloaded in 2 minutes.

ClassickWORLD said:
WoW this download link is really slow. Downloading at 50 KB/s. Says 9 hours left. I have fiber speeds for my internet. Anyone know of any alternative download locations for this OTA?
Edit: Rebooted my router and that fixed it. It downloaded in 2 minutes.
Click to expand...
Click to collapse
Fixed and you're a happy camper, right?
P.S. try a factory reset to complete this

You guys are great. The sideload fixed the problem! I truly appreciate you guys. Thanks a lot.

ClassickWORLD said:
Lol I still have my trusty ol' Nexus 6P as my secondary device.
Click to expand...
Click to collapse
Ok bruh, your forgiven :laugh: Did you get your problem fixed?
Oooops....never mind. I see that you did :good:

Is this the method for unlocking a Verizon Pixel 2 XL? Or just to fix the message this person was receiving. I want to buy a verizon Pixel 2 XL today in the store and do this vs waiting on google to deliver it.

tradermatt said:
Is this the method for unlocking a Verizon Pixel 2 XL? Or just to fix the message this person was receiving. I want to buy a verizon Pixel 2 XL today in the store and do this vs waiting on google to deliver it.
Click to expand...
Click to collapse
There is no method to unlock the Verizon P2XL!!