Database Info

question about unlocking bootloader on d2vzw sch-i535

Hello XDA Developers,
Okay so here is my unusual situation...
I have two phones. I have one Verizon (d2vzw) SGS3 that I run CM 11 on with CWM Touch installed on that phone. On my second phone which is also a Verizon (d2vzw) SGS3 i was running stock 4.1.2 ROM which was rooted with CWM recovery manager. The stock SGS3 was the baseband version that supported multi windows.
Okay so today i decided to go ahead and check for an OTA update on my stock (rooted) SGS3. I knew there had been an update available for some time but I never decided to update my phone because i figured with it being rooted and with CWM recovery manager installed there was no way that the OTA update would work...
So like an idiot i went ahead and tried the update. I figured what is the worst that could happen? I figured that at the worst it was just going to tell me that the update failed and i would just be stuck with Android 4.1.2 which isn't the end of the world. I really like the multi windows setup. Moving on...i downloaded the update and I hit the install update button. My phone booted into recovery manager and it installed the update. When the phone rebooted I saw the message "Android is upgrading" and i thought whoa! no way!. After android finished upgrading which i believe was the dalvik rebuilding I saw a message in notifications saying "upgrade installation failed", however when i went into settings it now told me that i was running Android 4.3. So to me it looked like the upgrade took but I think the problem was that when it asked me to flash the stock recovery there was an option in CWM to say no and i choose that to keep CWM recovery manager instead of the stock recovery manager. Maybe i should have let the update install the stock recovery manager...
Now i knew ahead of time that if this update worked I was going to loose root but again I didn't think it was that big of a deal since I could just re-root my phone and I would be on a newer Android version. I looked around for the best rooting option and I wanted to use Chainfire's CF-AutoRoot exploit but I know that if you do not have the bootloader unlocked that there is a chance of bricking your phone. So after some research (which i should have done before i updated my phone!) i saw that there was an exploit out called "saferoot.zip" and that you could root your phone running a windows.bat file or a shell script if you are in Linux. Even though the program is for SGS4 many users on XDA with SGS3 phones reported success with "saferoot". So i tried saferoot 2 times with no luck. Finally on the third attempt (3rd times a charm!) i was able to root my phone and SuperSU was able to "disable KNOX".
So i now had my Verizon SGS3 updated from Android 4.1.2 to Android 4.3 and I had successfully re-rooted my phone. I was feeling good...
Until I wanted to make sure that CWM Recovery Manager was still on my phone. I opened up the app "quickboot" and choose to boot into Recovery Manager this is where the trouble began...
When my phone booted into recovery mode i saw a big Yellow Triangle. Under this very scary yellow triangle it said that "Verizon has detected unauthorized software on this phone. Please turn off the phone and take it into your nearest verizon store". Other something along those lines...
I thought I was in big trouble...
I could not get the phone out of recovery mode. I tried pulling the battery but every time my phone rebooted it just kept going back into recovery mode. The trick to get out recovery mode was to hold down Volume Down + Home for a few seconds then press the power button. This brought me to a new menu and i was able to hit "cancel" on installing a new OS and it rebooted my phone back to its normal state.
So finally here is my questions...
Question 1: I know i need to unlock my bootloader again. After you apply an OTA update it re-locks your bootloader right? Does anyone know of a method of unlocking the bootloader with the Verizon (d2vzw) SGS3 baseband version I535VRUCML1 running on Android 4.3?
Before when my phone was running 4.1.2 I unlocked the bootloader with Odin and the app EZ-UNLOCK but i don't think EZ-UNLOCK is going to work with Android 4.3
Question 2: Is there a way to get rid of that message about Verizon has detected unauthorized software on this phone? Now I know that ChainFire has a Yellow Triangle Away app on the Google Play store and I will happily buy it but I know that in order for it to work you first must have your bootloader unlocked right? If i try to use that app with my bootloader in a locked state i could brick my phone permanently right?
Is there possibly any file or exploit i can flash with either Odin or the app "Flashify" so that I can unlock my bootloader. Has anyone here tried unlocking their bootloader on their SGS3 running 4.3 with the app "EZ-UNLOCK" ?
I am very concerned about damaging my phone which is a company work phone so if i mess it up i will be in deep trouble...
Oh, one last question...
Question 3: Since i got that yellow triangle message about unauthorized software when i tried to boot into recovery mode could it have possible been because CWM recovery was somehow deleted with the OTA update? After i was able to get out of recovery mode I used the app "ROM Manager" to install CWM Recovery Again hoping that I might have a recovery manager... Now ROM Manager says that CWM Touch was installed successfully but I am not sure since I am kind of scared to boot into recovery mode again until I unlock this bootloader.
If my recovery manager is being blocked until I get my bootloader unlocked could i use the app "flashify" if i need to flash any files?
I know my situation might be a bit unusual but I am really going to need some help on this and someones expertise advice.
I hope to hear from someone soon...
XDA Members, have a great New Years and make 2014 count!
I thank you all for your time and assistance.
-droidshadow

After accepting the 4.3 OTA, your bootloader is locked and there is no way to unlock it. My suggestion to you would be to grab the 4.3 ODIN file, reflash to 100% stock, root using saferoot, debloat as wanted, and hope for the best.
Probably not what you wanted to hear, but there is no way to unlock the bootloader once taking the 4.3 OTA. Attempting to do so will brick the phone.

well that stinks...
podspi said:
After accepting the 4.3 OTA, your bootloader is locked and there is no way to unlock it. My suggestion to you would be to grab the 4.3 ODIN file, reflash to 100% stock, root using saferoot, unbloat as wanted, and hope for the best.
Probably not what you wanted to hear, but there is no way to unlock the bootloader once taking the 4.3 OTA. Attempting to do so will brick the phone.
Click to expand...
Click to collapse
The only reason that I even attempted the upgrade is because next week I am going to purchasing the smart watch from the Samsung Galaxy Gear. For that watch (you can make calls from the watch) you need the upgrade to pair my SGS3 with my smartwatch when I get it next week.
Now this OTA update is quite new so that means that there still might be a chance to unlock the bootloader eventually when someone works it out right?
Big question:
Is it still possible to have CWM or TWRP with this 4.3 OTA update?
Thanks for the reply.
-droidshadow

droidshadow said:
The only reason that I even attempted the upgrade is because next week I am going to purchasing the smart watch from the Samsung Galaxy Gear. For that watch (you can make calls from the watch) you need the upgrade to pair my SGS3 with my smartwatch when I get it next week.
Now this OTA update is quite new so that means that there still might be a chance to unlock the bootloader eventually when someone works it out right?
Big question:
Is it still possible to have CWM or TWRP with this 4.3 OTA update?
Thanks for the reply.
-droidshadow
Click to expand...
Click to collapse
To bad you took the ota. There is a twrp flashable rom for stock 4.3. And no you can not have custom recovery.

droidshadow said:
Okay so today i decided to go ahead and check for an OTA update on my stock (rooted) SGS3...
Click to expand...
Click to collapse
There's no need to read any further than that.... Sorry to be another bearer of bad news, but if a phone is rooted and you want it to stay that way, "OTA" should be a term that you never, ever, ever even think about !

The S4 boot loader has been locked down with Knox longer than the S3 has, and no one has cracked it yet. I'd say the chances of this boot loader being cracked wide open are slim to none. If unlocking this boot loader were as simple as using EZ unlock 1.2, it would have been written about all over these and all forums.
Sent from the Shark Tank using XDA Premium 4 mobile app

so what entails for the future of samsung phones?
landshark68 said:
The S4 boot loader has been locked down with Knox longer than the S3 has, and no one has cracked it yet. I'd say the chances of this boot loader being cracked wide open are slim to none. If unlocking this boot loader were as simple as using EZ unlock 1.2, it would have been written about all over these and all forums.
Sent from the Shark Tank using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So what is the going to happen to the future of Samsung Phones? Are we no longer going to be able to put custom ROM's and custom Recovery Managers on Samsung Phones?
Will KitKat + SELinux + Knox no longer allow us to enjoy the true beauty of Android? I think that is major BS.
So what are our options now? Are we going to simply have to choose different phones like future Google Nexus phones? I love Samsung phones and I love having the options of flashing custom roms or reverting back to stock and I really really love CWM recovery or TWRP recovery.
These phones are our property...
I understand that the software and the code is Samsung's or Verizon's yet we should be able to do what we want to our property. Could you imagine if Toyota or Chevy said that after you purchased one of their cars you could never paint it a different color or add custom rims + wheels! That would be ridiculous... It is the same concept here really.
It is really sad that Samsung and Mobile carriers such as Verizon have resorted to this...
-droidshadow

droidshadow said:
So what is the going to happen to the future of Samsung Phones? Are we no longer going to be able to put custom ROM's and custom Recovery Managers on Samsung Phones?
Will KitKat + SELinux + Knox no longer allow us to enjoy the true beauty of Android? I think that is major BS.
So what are our options now? Are we going to simply have to choose different phones like future Google Nexus phones? I love Samsung phones and I love having the options of flashing custom roms or reverting back to stock and I really really love CWM recovery or TWRP recovery.
These phones are our property...
I understand that the software and the code is Samsung's or Verizon's yet we should be able to do what we want to our property. Could you imagine if Toyota or Chevy said that after you purchased one of their cars you could never paint it a different color or add custom rims + wheels! That would be ridiculous... It is the same concept here really.
It is really sad that Samsung and Mobile carriers such as Verizon have resorted to this...
-droidshadow
Click to expand...
Click to collapse
Difference is though, if you were to somehow screw up your car by customizing it you wouldn't try to take it back to the dealership and get a new car under a warranty claim. I would have to think at least part of the reason phone manufacturers and mobile carriers are locking down phones is all the "warranty" claims people are submitting after screwing up while rooting and flashing their phones. Warranty claims are for inherent manufacturer defects, not a hard brick from flashing the wrong software. If more people took responsibility for their mistakes and bought a new phone instead of making the carriers or manufacturers pay for their mistakes, perhaps this wouldn't be happening. I'm not saying absolutely, just perhaps. OK, I'll get off my soapbox now. Happy New Year everyone.

Different animal. You own the hardware, but the providers have the right to control the firmware since it can change how the phone interacts with the network.
Just like the firmware in your cars computer. The manufacturer and the federal government have control over what went in. Modifying it can be done, but it is a violation of EPA emission laws.
Modifying the paint, tires, rims etc is like putting a different case, bling etc on your phone
Your phone needs to have the 4.3 odin tar installed to clean the recovery.
Sent from my SCH-I535 using xda app-developers app

droidshadow said:
So what is the going to happen to the future of Samsung Phones? Are we no longer going to be able to put custom ROM's and custom Recovery Managers on Samsung Phones?
These phones are our property...
It is really sad that Samsung and Mobile carriers such as Verizon have resorted to this...
-droidshadow
Click to expand...
Click to collapse
Its really Verizon, They have had many Moto and HTC phones with locked bootloaders , unless Verizon unlocks it, it won't be cracked.

http://forum.xda-developers.com/showthread.php?t=2586319
Sent from my SCH-I535 using xda app-developers app

DigitalMD said:
Its really Verizon, They have had many Moto and HTC phones with locked bootloaders , unless Verizon unlocks it, it won't be cracked.
Click to expand...
Click to collapse
I know but still i think it should be our choice! While there are millions of us out there that love to customize the software on our phone's by adding new recovery managers or custom rom's we are a small population to the rest of the stock phone using world...
Insurance companies make big bucks by all the people who never file a claim...but i won't get into that.
Many of you have made excellent points and i respect that. I especially liked the comparison of car rims to phone cases i thought that was great!
Hopefully someone will work it out soon or some how an unlocked bootloader will get leaked.
Come one Verizon developers! Leak it! We wont tell!
I was planning on getting the NOTE 3 but i doubt that phone comes with an unlocked bootloader so this d2vzw (sgs3) will most likely be my last samsung phone that I ever buy. I guess i will have to stick with the Nexus phones... I am going to miss micro sdcards!
-droidshadow

droidshadow said:
I know but still i think it should be our choice! While there are millions of us out there that love to customize the software on our phone's by adding new recovery managers or custom rom's we are a small population to the rest of the stock phone using world...
Click to expand...
Click to collapse
Having that debate at this site is kinda silly.... Fact is, "we" will lose the fight against the carriers and/or manufacturers as it stands. The only way to really impact them is to STOP giving them our money, but you know what ? The number of people who "hack" their phones is a tiny percentage in the grand scheme. We'd probably get a "good riddance" response from them anyway.

droidshadow said:
So what is the going to happen to the future of Samsung Phones? Are we no longer going to be able to put custom ROM's and custom Recovery Managers on Samsung Phones?
Click to expand...
Click to collapse
That's correct and.... read on.
So what are our options now? Are we going to simply have to choose different phones like future Google Nexus phones?
Click to expand...
Click to collapse
That could be the only solution. I believe the success that Samsung/Verizon have had with locking down their phones will soon result in ALL phones on ALL carriers being locked down with little or no possibility of rooting or flashing.
I suspect we've seen the end of modifying any phone on any network. I sure hope I'm wrong....

It would be a shame....
xs11e said:
I suspect we've seen the end of modifying any phone on any network. I sure hope I'm wrong....
Click to expand...
Click to collapse
I just rooted and got into CM in the last month. Got rid of all the bloat and installed some neat little apps. And now, just when I get hooked, it's possible that my drug of choice may be going away.

hey there guys, i know this post is a little old, but i just wanted to share my story real quickly with you and to reiterate that messing with the boot loader on an sch-i535 running 4.3 is a HORRIBLE idea.
this is the first phone i have ever tried to root. i successfully rooted the phone, immediately i tried to run cwm recovery. HARDBRICK. i was so proud for all of five minutes that i rooted a phone on my first try. The phone would not power on in ANY mode. i could only get a red light to come on by plugging my phone into my computer with the battery out of the phone. after three days and alot of reading and some help from xda i managed to (amazingly) debrick my phone. I am now very VERY cautious of what i do with my rooted sch-i535 with its HORRIBLE 4.3 crap.
If you are truly hardbricked, im told that jigs (despite what is all over the internet) will not work. (maybe they do but a shop in texas told me a hardbrick will not revive by jig).
JTAG is the most dependable repair.
I revived my phone via debrick image on an sd card.
Bottom line, do everything you can to avoid the situation in the first place.

Never take updates. I unlocked boot loader on 4.3 with ez-unlock app booted into recovery and hard bricked my phone... The fun is over after 4.3...Had to send it to Tampa fl. To get JTAG and it worked.

droidshadow said:
So what is the going to happen to the future of Samsung Phones? Are we no longer going to be able to put custom ROM's and custom Recovery Managers on Samsung Phones?
Click to expand...
Click to collapse
That's correct, given the amount of time the Devs have had to find a way to unlock the bootloader on the S3 and S4 w/o success, I believe it's hopeless.
Worse, I believe Samsung will share their technology and ALL cell phones will eventually have locked boot loaders and be un-rootable, un-flashable and, to me, at least, un-desirable!
I sincerely hope I'm wrong but I believe in a year or two any cellphone will be locked down to whatever software is installed at time of purchase.

xs11e said:
That's correct, given the amount of time the Devs have had to find a way to unlock the bootloader on the S3 and S4 w/o success, I believe it's hopeless.
Worse, I believe Samsung will share their technology and ALL cell phones will eventually have locked boot loaders and be un-rootable, un-flashable and, to me, at least, un-desirable!
I sincerely hope I'm wrong but I believe in a year or two any cellphone will be locked down to whatever software is installed at time of purchase.
Click to expand...
Click to collapse
How's the fun over??? Haha I've seen this same junk many times... I'm running 4.3 rooted. Safestrapped (cwmis garbage) alliance 23 build ROM CSC & build prop tweaks on sch-i535v on straightalk att side. Knox removed manually by me. All bands open except domestic 3g. (Working on it now).
So the funs over? I'm confused.. And how is that? Lol take your time. Research. Learn. Adapt. Achieve. If it can be locked. It can be unlocked. I've yet to run across a phone that I couldn't bring back from the supposed "hard brick" but I did find one I COULDNT brick on purpose. And I threw everything at it. Huwaei m8665 I think it was. I tried for two days to brick that little piece of junk, and not even wrong roots etc could. Lol

An0nYm0u5.bat said:
How's the fun over??? Haha I've seen this same junk many times... I'm running 4.3 rooted. Safestrapped (cwmis garbage) alliance 23 build ROM CSC & build prop tweaks on sch-i535v on straightalk att side. Knox removed manually by me. All bands open except domestic 3g. (Working on it now).
So the funs over? I'm confused.. And how is that? Lol take your time. Research. Learn. Adapt. Achieve. If it can be locked. It can be unlocked. I've yet to run across a phone that I couldn't bring back from the supposed "hard brick" but I did find one I COULDNT brick on purpose. And I threw everything at it. Huwaei m8665 I think it was. I tried for two days to brick that little piece of junk, and not even wrong roots etc could. Lol
Click to expand...
Click to collapse
I agree with you if there is a way to lock it there is a way to unlock it.
is just a matter of time some smart brain will figure it out how to and share LOL

Cricket(SM-G360AZ) Galaxy Core Development

I see posts for every other carrier model but Cricket.
Can anybody make some pre-rooted Roms and a recovery for this model? I'm also here to learn if anyone has time to teach.
I'm currently on G360AZTUU3AOH1 and don't want to attempt to flash other versions(Like G360H or G360P) and brick my device as this is my only phone at the moment.
I'm rooted now, but would like to get an upgrade as there's tons of app crashes on the current version.

How did you root? Was it just an app like Kingroot? I'm looking to get root but I'm afraid of bricking my phone after all the horror stories I read.

Latest version of Kingoroot works on this phone and I feel that the kingroot apk would work but I didn't try it yet and had trouble with the windows version of Kingroot.
It amazes me how there is alot of work done on the G360H yet hardly any on the G360AZ. With alot of people using coreprimelte references it is making it difficult to secure good leads on ways to work on this phone as it is rather special I guess.
I hope someone can follow up on a recovery and rom compatibility info. Bought this phone as a cheap play-a-round phone only to find there isn't much I can do with it atm.

I did manage to get a Nandroid backup of the phone to my pc. Working on doing some tests to make sure it can be made into a Odin file. If so I plan to get it posted.

I agree, I want to try Kingroot but don't want to eff up the phone for fear of not fixing it
Sent from my SGH-T399N using XDA-Developers mobile app

Bootloader Unlock and 6.0 Flashing Progress.

Iv started this thread to get talking about unlocking the bootloader and a proven flashing method for 6.0. @LGMONO and @ZVNexus are working on root for a 6.0 tot, if it its authenticated. But, we still need a method for unlocking the bootloader, aswell as a stable way to flash the tot so we can back up and gain root. So for these cases, anyone have a clue where we are at with them?
UPDATE: 3-27-17
So no way for root has been found yet, but its not over. Android 7.0 Nougat has been confirmed for the LGV10 and we are supposed to have it by the end of this month so realistically, I say sometime next month. Now hopefully they will ease up on the restrictions in 7.0. But i have found something interesting with 6.0 on the v10. I tried to install Stump.apk (a root-kit app) and android warned me that the app contains code that tried to alter android or something like that. Anyways, so my guess that a new way might be possible to gain root access. If you can force an app to change its code after being installed, that might work... If it can even work like that. They have over hauled the security on the v10, so atleast your stuff is relatively safe if you do your part.
For now, im gonna start talking to people to see if maybe lg or at&t would consider removing their block once a phone has gone out of warranty. Im on lease for mine so I can kinda understand why they dont want it modified, but if i pay it off or out right, i should have the right to do as i wish for it, so im gonna try to talk with them about that.

UPDATE:
After looking around, some people found success of downgrading to 5.0 or 5.1 with LGUP on the g4. Now it didnt say it was carrier specific, but, if its not, then im beginning to wonder where the problem of just flashing a tot really is on the v10.

Shadow Assassin said:
Iv started this thread to get talking about unlocking the bootloader and a proven flashing method for 6.0. @LGMONO and @ZVNexus are working on root for a 6.0 tot, if it its authenticated. But, we still need a method for unlocking the bootloader, aswell as a stable way to flash the tot so we can back up and gain root. So for these cases, anyone have a clue where we are at with them?
Click to expand...
Click to collapse
We are pretty close. This is pretty weird though, when I open boot.img on the Marshmallow TOT, it refuses to open the archive, and fails. The boot.img on the 5.1.1 TOT does not have this problem however and opens just fine. This is strange and it is risky to flash not knowing if it might work. If only I had extra phones to test this lol

ZVNexus said:
We are pretty close. This is pretty weird though, when I open boot.img on the Marshmallow TOT, it refuses to open the archive, and fails. The boot.img on the 5.1.1 TOT does not have this problem however and opens just fine. This is strange and it is risky to flash not knowing if it might work. If only I had extra phones to test this lol
Click to expand...
Click to collapse
It might be as simple as just a broken boot.img. im not 100%, but i dont think there is any signitures of authenticity in the boot.img, so you might could use a different one. I have a copy of the 6.0 TOT. Later ill go try to unpack the boot.img and see what i can find.

Shadow Assassin said:
It might be as simple as just a broken boot.img. im not 100%, but i dont think there is any signitures of authenticity in the boot.img, so you might could use a different one. I have a copy of the 6.0 TOT. Later ill go try to unpack the boot.img and see what i can find.
Click to expand...
Click to collapse
We would have to use the boot.img from a 6.0 AT&T LG V10 Though, because of Anti-TOT Rollback. Changing the boot.img with one from 5.1..1 would screw that up I think.

I'll pay for mm root, please keep the effort alive. This is the best phone with a removable battery - so best phone I can own - and since I'm stuck with it... I'll pay to improve it, as we all should.
Sent from my LG-H900 using Tapatalk

shepcontracting said:
I'll pay for mm root, please keep the effort alive. This is the best phone with a removable battery - so best phone I can own - and since I'm stuck with it... I'll pay to improve it, as we all should.
Sent from my LG-H900 using Tapatalk
Click to expand...
Click to collapse
A petition has been started for universal unlocking on the v10.
As far as donations, talk to @LGMONO and @ZVNexus
Petition: http://forum.xda-developers.com/lg-v10/general/petition-bootloader-unlock-rights-lg-v10-t3412069

This may be a dumb question but is it possible to use quadrooter to gain root access on 6.0 and then use the exploit to install super su?

lol i gave up on this phone and got myself a nexus 6, ita hopeless with stingy at&t

shadowcreeper_1 said:
lol i gave up on this phone and got myself a nexus 6, ita hopeless with stingy at&t
Click to expand...
Click to collapse

[SIGH].....
This phone is dead. Time to start saving for a "Pixel".

P05TMAN said:
[SIGH].....
This phone is dead. Time to start saving for a "Pixel".
Click to expand...
Click to collapse
Its not that the phone is dead, its just that the majority of the people who bought this phone did not buy it to root or anything. They bought it because of the camera. Anyone else would have bought a LG G4, G5, or a Samsung Note. All of those are VERY good options if you want to root.

ZVNexus said:
Its not that the phone is dead, its just that the majority of the people who bought this phone did not buy it to root or anything. They bought it because of the camera. Anyone else would have bought a LG G4, G5, or a Samsung Note. All of those are VERY good options if you want to root.
Click to expand...
Click to collapse
I got it because of the removable battery and micro SD support... and yeah the camera too, but at the time it had root, so I wasn't really too worried about it. Guess I'm SOL now.

P05TMAN said:
I got it because of the removable battery and micro SD support... and yeah the camera too, but at the time it had root, so I wasn't really too worried about it. Guess I'm SOL now.
Click to expand...
Click to collapse
I mean, its not that bad. Right now without root you can still customize your phone to a extent. You can use a program to disable (NOT REMOVE) any programs you want, so all AT&T bloat doesn't show on my app drawer anymore, same with any LG apps. A nice wallpaper, Nova, a icon pack, and it looks pretty fine and dandy! Right now I have about 4 months left and then I can get a new phone. Not too bad. Was thinking about the new Nexus lineup.

ZVNexus said:
I mean, its not that bad. Right now without root you can still customize your phone to a extent. You can use a program to disable (NOT REMOVE) any programs you want, so all AT&T bloat doesn't show on my app drawer anymore, same with any LG apps. A nice wallpaper, Nova, a icon pack, and it looks pretty fine and dandy! Right now I have about 4 months left and then I can get a new phone. Not too bad. Was thinking about the new Nexus lineup.
Click to expand...
Click to collapse
Yeah I still have some time, but I'm going to just save to pay for the new "Nexus" out-right (I think you have to anyways). This is really too bad. I've never owned a phone that was so locked down that we can't unlock the bootloader, root or anything. It's maddening. I should have done better research; if I had, I would have found that the "root" we had for 5.1.1 was only temporary and there was no unlocked bootloader.

Hey all! Good news! A 9-year-old bug called the "Dirty Cow" exploit still exists in the Linux/Android kernel can easily grant root on any Android phone!!! See the video below.
http://www.xda-developers.com/9-year...on-of-android/
So there's another bug to exploit for root and even possibly unlocking the bootloader! The bug has been fixed recently in Linux but hasn't been rolled into Android yet. If anyone can get this working on my AT&T LG V10 (running Marshmallow) I'll give a reward of $50! Plus you'll be my hero! Now get crackin!

Finally LG has released a new software update (Build H90021w) for the AT&T LG V10 H900 phone.
Maybe root is nearby
http://www.mylgphones.com/att-lg-v10...-download.html
http://lg-phone-firmware.com/index.php?id_mod=459

ronallica said:
Finally LG has released a new software update (Build H90021w) for the AT&T LG V10 H900 phone.
Maybe root is nearby
http://www.mylgphones.com/att-lg-v10...-download.html
http://lg-phone-firmware.com/index.php?id_mod=459
Click to expand...
Click to collapse
Its possible. The kdz they released could give us a custom TOT. The we just have to figure out how to flash it.

Update
You can view the update in the original post.

I like this phone but need root. This phone on At&T seems dead for development after a year. Just bought an OnePlus 3t 128g with delivery today. That phone has development. ROOT! Goodbye V10.

Explanation: LG V10: Reasons why I vanished:

Some time ago, in the middle of the night I woke up to see my V10 bootlooping, and it was next to almost stock. and I never mess with my v10 cause my htc10 is my daily Driver....
after talking to T-Mobile and and then LG, I got LG to pay for everything including shipping. because my device was babied to death, it was like mint condition, so instead of making me wait for a new board
and so on, They sent me a whole new V10, that was manufactured only a few months prior, which came with updated everything.. So to make a long story short. I have no ROOT.. and no way to get ROOT..
I have Android N on my device...........
Now if I ever figure out how to get root again, I will then pick up where I left off on this device.................
I am one of the owners of the new Project that I personally started some time ago, called PureFusionOS..... we are on 5 devices. officially on HTC10 and OP3 and OP5................
and some how a mediatek device which I still cant figure out how he did that........
anyhow.. With my new found knowledge of ROMs and so on, I am sure of I ever get this device rooted again, I can get a custom rom working on this device with Camera working.........
my knowlege with camera has increased much do to the fact of the issues I went through on the HTC10 to get 4k recording working.........
But will any of this truely happen, as I said, it all depends on if I get ROOT again on this device........... I am running 100% stock Android N ....................
But I wanted to let you know what happen to me.. and why I havent been able to do anything.........................
I do have some ideas on getting root, but I highly doubt they will work.. What I prob need is a rooted TOT file with latest ROM.........

What are the options of downgrading? Acquiring root and then updating?

z.coniglietti said:
What are the options of downgrading? Acquiring root and then updating?
Click to expand...
Click to collapse
It is bnot possible to downgrade from Nougat to MM on rhe H901, i've tried and it does'nt work. The bootloader can be unlocked but that is as far as it goes at the moment. As stated by Eliminator there is no root yet for this phone.
Sent from my LG-H870 using Tapatalk

Hi i'm new to the V10 h901 game, i have been reading a lot lately this forum ,can you explain more the situation? what Eliminator is saying means no twrp of the ones posted here will work for the H901 in nougat?, mine came with Mashmallow but i flashed Nougat with lg bridge before reading, i guess im stuck now? i unlocked the bootloader today hoping to flash one of those recoveries but "fastboot boot twrp.img" didnt work so i didnt flashed it hoping to get more information on the subject here.

So I was on a rooted MM Rom, maybe even yours, and used this thread https://forum.xda-developers.com/showthread.php?t=3638750 to update to N and kept root. Are there any files I could pull from mine that would help?
Sent from my LG-H901 using XDA-Developers Legacy app

bobbylx said:
So I was on a rooted MM Rom, maybe even yours, and used this thread https://forum.xda-developers.com/showthread.php?t=3638750 to update to N and kept root. Are there any files I could pull from mine that would help?
Sent from my LG-H901 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Not a single thing.. Problem is my device came back with N already on it.. so there is no way to ROOT it at this time.. and its not really high on my list to worry about it.
if I dont root it, no big deal......

No root for N so far. I soft bricked my device, and the only way to get it back was with LG Bridge, and now I'm stuck with stock N firmware. So, we need to hope and wait for someone clever than us to find a way to root V10 with stock N.

If it helps, we can trade devices. Mine is on the latest, rooted and I am going to sell mine. Not much extra value in selling a rooted device. So pm me and we can cross ship. Your device for mine. I'll sell yours on swappa....and you have a rooted device to Dev for the community moving forward. It would be awesome if you could put your new OS on the V10

Amd4life said:
If it helps, we can trade devices. Mine is on the latest, rooted and I am going to sell mine. Not much extra value in selling a rooted device. So pm me and we can cross ship. Your device for mine. I'll sell yours on swappa....and you have a rooted device to Dev for the community moving forward. It would be awesome if you could put your new OS on the V10
Click to expand...
Click to collapse
I would be down for a swap. Yes, please!
I got the terrible Green Screen Of Death. My replacement came Nougat out of the box. Sadness.
What do you recommend? Should I make a post here? In General thread? At Swappa? Ebay?

Well this seemed really promising and then ironically the person I suspected would drop either a LineageOS build (which I would love, just plain old LineageOS with no major changes or frills for the V10, second screen I don't even give a damn about really, a kernel with a lot of governor support/options would be great too, and here's a Nougat from the factory device he can't even work with, great.
And with nobody really giving a damn about the V10 overall we are probably just going to be stuck at this point from now on, sadly.
Maybe we'll get a small miracle at some point, I'll keep my fingers crossed. Thank you, Eliminater74, for at least letting the community know you're still around and might still be able to provide some magic if things work out.

Try modified LG up as a path to downgrade.... I'm on nougat flashed with TWRP so I never went through the steps to modify LG up. I really think it can work to get back down to 6.0 use dirtycow get TWRP then install the nougat update zip..... I know another person interested in the root of the 7.0 locked firmware going back to 6 had pointed in this direction.....

Help rooting Samsung galaxy j3 (sm-J337a)

It seems everywhere I go there is no root for this phone (sm-J337a) it's an at&t phone. I used kingoroot, kingroot and basically any root out there. nothing has worked. So this seems that it has no root made for it yet? is there any possibility for someone to do this? Sorry, I'm not too good at rooting as a whole. But I've used Odin and things like that before.
there doesn't even seem to be CWM or TWRP for this phone either.
it's running Android 8.0 and was made in 2018.

Right?
I'm having the same issue. I can't figure out how to root mine either and I've got the same phone and carrier.

nickthekid said:
It seems everywhere I go there is no root for this phone (sm-J337a) it's an at&t phone. I used kingoroot, kingroot and basically any root out there. nothing has worked. So this seems that it has no root made for it yet? is there any possibility for someone to do this? Sorry, I'm not too good at rooting as a whole. But I've used Odin and things like that before.
there doesn't even seem to be CWM or TWRP for this phone either.
it's running Android 8.0 and was made in 2018.
Click to expand...
Click to collapse
Details of your current ROM Please..?
Build number etc...

Hi all.. I know this thread is a little old but thought id add this.. As of this date Ive found no ROOT solution for the SM-J337A - AT&T variant either.. I have found a lot of other software and such and as soon as I can get it all sorted, cataloged, and uploaded to the cloud I will see about placing some links here somewhere to all of them.. Not sure how long it will be..Stay tuned...
I happen to inherit a J337A with a cracked screen but was working fine until I updated it and tryed ROOTing it.. Im still Playing with it to see if I can revive it.
Having issues finding a UB compatible Firmware set that I dont have to pay for.
Am needing "J337AUCSBBTI1" or maybe "J337AUCSABTE1" to see if I can bring it back to life.. I may end up pitching it tho...
My Device:: SM-J337A
FCC-ID : A3LSMJ337A
Samsung/j3toplteuc/j3toplteatt
CURRENTLY STUCK ON COMBINATION ROM : (8.0.0/R16NW/J337AUCUBATH1/user/release-keys)
BINARY/BOOTLOADER : UB

iamoz said:
Hi all.. I know this thread is a little old but thought id add this.. As of this date Ive found no ROOT solution for the SM-J337A - AT&T variant either.. I have found a lot of other software and such and as soon as I can get it all sorted, cataloged, and uploaded to the cloud I will see about placing some links here somewhere to all of them.. Not sure how long it will be..Stay tuned...
I happen to inherit a J337A with a cracked screen but was working fine until I updated it and tryed ROOTing it.. Im still Playing with it to see if I can revive it.
Having issues finding a UB compatible Firmware set that I dont have to pay for.
Am needing "J337AUCSBBTI1" or maybe "J337AUCSABTE1" to see if I can bring it back to life.. I may end up pitching it tho...
My Device:: SM-J337A
FCC-ID : A3LSMJ337A
Samsung/j3toplteuc/j3toplteatt
CURRENTLY STUCK ON COMBINATION ROM : (8.0.0/R16NW/J337AUCUBATH1/user/release-keys)
BINARY/BOOTLOADER : UB
Click to expand...
Click to collapse
I can help you with that if you still need it. I have my j3 rooted with magisk, although there is no twrp or any custom recovery for that matter..
I can give you the exact files along with the patched magisk file and you'll have to flash it with patched odin and you should be good. Let me know.

rip21skinz said:
I can help you with that if you still need it. I have my j3 rooted with magisk, although there is no twrp or any custom recovery for that matter..
I can give you the exact files along with the patched magisk file and you'll have to flash it with patched odin and you should be good. Let me know.
Click to expand...
Click to collapse
Yes I would be interested in having those files please... Either upload them here or I can give you an email if you prefer... Let me know..

rip21skinz said:
I can help you with that if you still need it. I have my j3 rooted with magisk, although there is no twrp or any custom recovery for that matter..
I can give you the exact files along with the patched magisk file and you'll have to flash it with patched odin and you should be good. Let me know.
Click to expand...
Click to collapse
Instead of sending a patched magisk file would you mind sending over the method you used to root? If you did what I think you did I'm very confused. The phone is OEM locked although this hasn't stopped others from accessing root before. If you can confirm you have the phone we have, the SM-J337A ATT then you can pull out the boot and recovery images using a root app. Then I could develop a working TWRP for our device. But ofc this is only possible if you explain how you went about rooting the device. Thanks in advance.

NonStickAtom785 said:
Instead of sending a patched magisk file would you mind sending over the method you used to root? If you did what I think you did I'm very confused. The phone is OEM locked although this hasn't stopped others from accessing root before. If you can confirm you have the phone we have, the SM-J337A ATT then you can pull out the boot and recovery images using a root app. Then I could develop a working TWRP for our device. But ofc this is only possible if you explain how you went about rooting the device. Thanks in advance.
Click to expand...
Click to collapse
I have both SM-J337P/A and it works the same on both. I'm not sure why you wouldn't be able to be oem unlocked? You mean greyed out? Or does it not show up at all or what? If I go into developer options I have the oem unlock option, which then allows me to unlock the bootloader. If yours is greyed out I saw a solution on XDA a long time ago, maybe a year ago. I'd have to look for it in my files, I know I saved it somewhere. Let me know what you meant by that and we can go from there

rip21skinz said:
I have both SM-J337P/A and it works the same on both. I'm not sure why you wouldn't be able to be oem unlocked? You mean greyed out? Or does it not show up at all or what? If I go into developer options I have the oem unlock option, which then allows me to unlock the bootloader. If yours is greyed out I saw a solution on XDA a long time ago, maybe a year ago. I'd have to look for it in my files, I know I saved it somewhere. Let me know what you meant by that and we can go from there
Click to expand...
Click to collapse
I do not have the option to OEM Unlock the phone period. It is not in my developer options unfortunately. If you do find something of that nature please do contact me. Also if you would like a TWRP for your device I'd be up to developing it, although I wouldn't be able to maintain bugs... All I need is the kernel and I can get it done.

Any updates on this?