I know the likelihood of the boot-loader ever being unlocked is less than nothing but is development for this phone dead? It doesn't seem that anyone is working on a root method for Oreo and we're locked and unable to downgrade to root. Should we all move forward thinking that root is dead?
TheDrizzwell said:
I know the likelihood of the boot-loader ever being unlocked is less than nothing but is development for this phone dead? It doesn't seem that anyone is working on a root method for Oreo and we're locked and unable to downgrade to root. Should we all move forward thinking that root is dead?
Click to expand...
Click to collapse
I'd say move forward at this point whatever dev's are left they're not going for any of that, they're just modding roms and not going for oreo root.
Related
Has anyone done the OTA update from verizon?
I expect that I will lose root, but can I get it back the same way I did with 10B?
Dont do it.
I got my G3 about 4 days ago, and i immediately updated it. I think i found a way to flash back to 10b so i can root. As of now, i am unable to root with stomproot, ioroot, and purpledrake (or whatever its called). I have no idea what would happen if a rooted g3 with 10b upgraded to 11c.
Maybe towel root would work
2SHAYNEZ
Towel root didn't work for 10b
blindguyinanorgy said:
Has anyone done the OTA update from verizon?
I expect that I will lose root, but can I get it back the same way I did with 10B?
Click to expand...
Click to collapse
blindguyinanorgy said:
Towel root didn't work for 10b
Click to expand...
Click to collapse
Please refer to your Verizon G3 forums - http://forum.xda-developers.com/verizon-lg-g3/general. There are several threads there that talk about the OTA update, why it is not good to take OTA updates, and luckily for you a method for getting back to 10b.
Consider yourself lucky. There is no guarantee that you will be able to downgrade after taking an OTA update. Blindly taking updates is a great way to loose root and bump in the future.
Almost every thread that shows you how to root and bump tells you to not take updates, c'mon guys they are telling you to protect your device.
sic0048 said:
Please refer to your Verizon G3 forums - http://forum.xda-developers.com/verizon-lg-g3/general. There are several threads there that talk about the OTA update, why it is not good to take OTA updates, and luckily for you a method for getting back to 10b.
Click to expand...
Click to collapse
I didn't think there was a verizon thread last time i looked (months ago). Someone please move this thread.
sic0048 said:
Consider yourself lucky. There is no guarantee that you will be able to downgrade after taking an OTA update. Blindly taking updates is a great way to loose root and bump in the future.
Click to expand...
Click to collapse
Not lucky, I know to ask first, hence this thread.
I didnt realize how for the community has come on custom flashing since I got my phone and rooted it. Definitely need to spend some time seeing what we got.
I did the update last night. I can confirm that the update did not remove my root and in fact the update only was to make the phone run more smoothly.
ToF_Itachi said:
I did the update last night. I can confirm that the update did not remove my root and in fact the update only was to make the phone run more smoothly.
Click to expand...
Click to collapse
It didn't remove root, but it is currently unrootable. This means that if you should loose root somehow, you will not be able to get it back. I HIGHLY suggest you go to the Verizon G3 forum and read all the threads there. You can get all the benefits of the update without loosing the root method via the methods there.
I don't know how many times this has been said, but apparently there are still a ton of dumb people out there.......
NEVER TAKE AN OTA UPDATE IF YOU LIKE BEING ROOTED OR IF YOU EXPECT TO RETAIN THE ABILITY TO BUMP
sic0048 said:
It didn't remove root, but it is currently unrootable. This means that if you should loose root somehow, you will not be able to get it back. I HIGHLY suggest you go to the Verizon G3 forum and read all the threads there. You can get all the benefits of the update without loosing the root method via the methods there.
I don't know how many times this has been said, but apparently there are still a ton of dumb people out there.......
NEVER TAKE AN OTA UPDATE IF YOU LIKE BEING ROOTED OR IF YOU EXPECT TO RETAIN THE ABILITY TO BUMP
Click to expand...
Click to collapse
Well luckily i still had root before the update.
I've got a new t807a from AT&T. According to the "about device" settings page, SE is "enforcing." My understanding is that this conclusively indicates that my bootloader is locked. It's currently running Android version 4.4.2, build number kot49h.T807aucu1ank1
I don't need a custom ROM and I don't care about tripping my knox counter (per se). I just want root. I've asked this in several relevant threads this week and gotten contradictory responses. Is there or is there not currently a method to root my tablet?
If not: is there hope? This is a great tablet but I can't live with the bloat for 18 months until I can afford a replacement. I CAN still return it and eat the 70-dollar "restocking" fee.
Thanks in advance.
Just because it is enforcing, does not mean it is locked.
The s6 shows enforcing and for the T-Mobile version can be rooted with autoroot and trip Knox.
TheArtiszan said:
Just because it is enforcing, does not mean it is locked.
The s6 shows enforcing and for the T-Mobile version can be rooted with autoroot and trip Knox.
Click to expand...
Click to collapse
So what does that mean for my t807a?
thorvindr said:
So what does that mean for my t807a?
Click to expand...
Click to collapse
Locked bootloader aside, root can be achieved. Check the Dev pages for specifics/updates but this is the auto page link. You'll see the 807 is being tested but check back there often to monitor progress.
skeeterpro said:
Locked bootloader aside, root can be achieved. Check the Dev pages for specifics/updates but this is the auto page link. You'll see the 807 is being tested but check back there often to monitor progress.
Click to expand...
Click to collapse
Thanks. I have been following that. Just hoping someone knows something I don't I suppose.
ATT=Locked Bootloader which there's not going to be root or anything. Same goes for Verizon. SE enforcing is Selinux. Most devices have that including my Tab S 10.5 WiFi with unlocked bootloader. SE is an protections or somesort (google it).
Since you have a locked bootloader, it will fail to flash modfied stuff to get root. It will only flash stock images. So you may have to return it. Just remember, don't buy from att or Verizon. Buy an unlocked model or Tmobile. Hope this helps!
DUHAsianSKILLZ said:
ATT=Locked Bootloader which there's not going to be root or anything. Same goes for Verizon. SE enforcing is Selinux. Most devices have that including my Tab S 10.5 WiFi with unlocked bootloader. SE is an protections or somesort (google it).
Since you have a locked bootloader, it will fail to flash modfied stuff to get root. It will only flash stock images. So you may have to return it. Just remember, don't buy from att or Verizon. Buy an unlocked model or Tmobile. Hope this helps!
Click to expand...
Click to collapse
I think you're telling me there's no way to unlock the bootloader and root is therefore completely unattainable. Is that right? If it's just a matter of "we haven't cracked it yet," I can be patient. But if you're saying there's really no hope, I'm going to be far less patient.
Is there no software solution (ie towelroot) that might help me get root without having to get past the bootloader?
thorvindr said:
I think you're telling me there's no way to unlock the bootloader and root is therefore completely unattainable. Is that right? If it's just a matter of "we haven't cracked it yet," I can be patient. But if you're saying there's really no hope, I'm going to be far less patient.
Is there no software solution (ie towelroot) that might help me get root without having to get past the bootloader?
Click to expand...
Click to collapse
Its a matter "we haven't cracked it" and no one is working on it. So basically almost to no hope and the odds of getting root or unlocking the Bootloader is really really low. There's no software solution like towel root that will get root or anything that doesn't mess with bootloader.
So there's no hope (unless some breakthrough happens).
DUHAsianSKILLZ said:
Its a matter "we haven't cracked it" and no one is working on it. So basically almost to no hope and the odds of getting root or unlocking the Bootloader is really really low. There's no software solution like towel root that will get root or anything that doesn't mess with bootloader.
So there's no hope (unless some breakthrough happens).
Click to expand...
Click to collapse
Well that blows. I guess that's what I get for buying off-the-rack.
Is this info outdated?
info outdated?
I've got an easy working root on my t807A with kingroot. And yet there seems to be no custom roms available for it.
Slightly out of topic, does anyone have a install to SDcard solution? Nothing I find seems to work
JMVPSlash said:
info outdated?
I've got an easy working root on my t807A with kingroot. And yet there seems to be no custom roms available for it.
Slightly out of topic, does anyone have a install to SDcard solution? Nothing I find seems to work
Click to expand...
Click to collapse
The built-in app manager lets you move apps to SD but I also have not found a solution to install directly to SD (without repartitioning the card). After several months of despair, I'm just now checking back to see if there's been any development on the bootloader front. It appears not. You can get root with Kingroot (also check out supersume, if that's still around, to replace kingroot's su app with supersu) but apparently the bootloader being locked prevents any non-official ROM from booting.
Just got the phone a few hours ago and want to root it and install Xposed. But I'm not sure what's the best path.
So far it seems like VS98610B is an old version nobody is using and that if I root it, I won't be able to upgrade in the future without breaking the phone, is that correct?
If I go to "Check for new system update" it asks if I want to update to 11A. From what I understand from this post http://forum.xda-developers.com/showpost.php?p=64116024&postcount=362 is that I want to take the update, then after it installs that update, it should ask to update again to 13B? And that it is this 13B version that I root?
Am I able to unlock the bootloader on any of these versions? Why does it ask me to go to 11A instead of straight to 13B?
All I can say is that you are damn lucky and DO NOT update or flash a non 10B image of you have any desire to unlock the bootloader and use custom ROMs and such
DerekZ10 said:
Just got the phone a few hours ago and want to root it and install Xposed. But I'm not sure what's the best path.
So far it seems like VS98610B is an old version nobody is using and that if I root it, I won't be able to upgrade in the future without breaking the phone, is that correct?
If I got to "Check for new system update" it asks if I want to update to 11A. From what I understand from this post http://forum.xda-developers.com/showpost.php?p=64116024&postcount=362 is that I want to take the update, then after it installs that update, it should ask to update again to 13B? And that it is this 13B version that I root?
Am I able to unlock the bootloader on any of these versions? Why does it ask me to go to 11A instead of straight to 13B?
Click to expand...
Click to collapse
Just my opinion but holding for a bootloader unlock is pointless and no you can't unlock it on any version. I waited for a year for the note 4 to get root or unlocked and never did. As days pass it's less likely we will ever see it unlocked on the g4.
To root take the OTA and get to 13b then follow the root guide in the forums....with root, xposed, and a little debloat this phone is awesome!
Awesome.that's what I was looking for. If it's already been since june and nobody has cracked it, that's not looking too good. My only worry now is why it's not taking me straight to 13b? It will take me to 13b after 11a right?
Also where is a good up-to-date root thread? There's nothing stickied.
If someone is on the verge of cracking the bootloader, how do I root this version so I can holdout, without killing my ability to upgrade in the future?
I'm also really interested in getting the fm radio working.that was one of the deciding factors when getting the phone. I did not know that Verizon crippled it.
EDIT: Also what's the benefit to upgrading? 10B is already android 5.1 so what is gained?
DerekZ10 said:
I'm also really interested in getting the fm radio working.that was one of the deciding factors when getting the phone. I did not know that Verizon crippled it.
EDIT: Also what's the benefit to upgrading? 10B is already android 5.1 so what is gained?
Click to expand...
Click to collapse
I never ran on 10B, so I don't know what benefits there were going to 11, however, 11 to 13b saw major improvements to touch responsiveness for most people (I never had touch issues on my phone, so I don't know on that count, but maybe I just never noticed); I also found that the phone performs a lot better and the battery lasts a bit more.
ericralph said:
All I can say is that you are damn lucky and DO NOT update or flash a non 10B image of you have any desire to unlock the bootloader and use custom ROMs and such
Click to expand...
Click to collapse
The rumored unlocked bootloader is vaporware. There has been no update on the status of it, especially for the Verizon variant. See here: http://forum.xda-developers.com/g4/general/unlock-unofficial-bootloader-unlock-t3222737
I've already considered of foregoing the mythical v0 unlock bootloader (VS98610B firmware, aka 10B) and move up to VS98613B rooted to enjoy all the fixes to the phone. No point of waiting any longer without any updates.
Just bought an AT&T Note 4 today, I was informed it had 4.4.4, but it instead had 5.1.1, and root had been a big part of all 3 previous Note phones I've owned, so I was looking for a way to do so, seems like nothing's been accomplished yet, until I stumbled upon this. Will this work on 5.1.1 even with that locked bootloader?
http://androidromupdate.com/att-galaxy-note-4-sm-n910a-stock-firmware/
Im bot aure exactly what you are asking but from what i gather you are either wondering about downgrade or root. Either way it is not possible once the phone is on 5.1.1 you are stuck with only one way to go and thats up when and if an update comes. As for root its looking highly impossible to get our bootloader unlocked as at&t never released a developer edition of our phone which makes a reliable root impossible. I would recomend if you have the cash yo do so sell the at&t note 4 and get a tmobile note 4 which is unlocked and rootable
Was the 4.4 bootloader unlocked? It's not possible to restore 4.4 in download mode with Odin or anything?
No it is not possible odin will fail because the 5.1.1 bootloader is secure and detects all attempts to overwrite or change it and stops the process. So basically you can not touch the bootloader downgrade or root or modify the system or kernel in any way unless the bootloader is hacked or unlocked period. Sorry
P.s. if it would have been that simple (boy do i wish it was) you would find a thread on here about downgrading to 4.x.x from 5.1.1 and not so many threads about root waiting room and things like that
partyboynx2 said:
Just bought an AT&T Note 4 today, I was informed it had 4.4.4, but it instead had 5.1.1, and root had been a big part of all 3 previous Note phones I've owned, so I was looking for a way to do so, seems like nothing's been accomplished yet, until I stumbled upon this. Will this work on 5.1.1 even with that locked bootloader?
http://androidromupdate.com/att-galaxy-note-4-sm-n910a-stock-firmware/
Click to expand...
Click to collapse
Well can't downgrade from lollipop back to kitkat, but look at my threads, and if it helps, just add a little thanks!
Sent from my SM-N910T3 using XDA-Developers mobile app
Hello. I'm pretty terrible at all this rooting stuff (or at least, I only do it once for each android phone I get, and then don't really look into it or stay up to date on all of it afterwards, I just use a few pluses that come along with being rooted).... Anyways, I really do need some help this time, as the confusion has really gotten to me, and I've lacked being able to find some simple answers (probably because they are just THAT simple) on google/reddit/on this forum.
Anyways, I've rooted my phone awhile back, lost it when my verizon pixel auto updated to 7.1.1 (idk how or why, pretty sure I had that disabled with root even, very frustrated) and even attempted to regain root by flashing SU with TWRP, but for some reason SU said I didn't have root still, and eventually just gave up in frustration. But now, my verizon pixel has been shutting off at ~40% battery power, and I read in the google forums that this was patched in the 7.1.2 update for pixels, and it was a software glitch rather than a malfunctioning/bad battery... So now I really want to upgrade to 7.1.2 from 7.1.1 not only to fix the battery/software issue, but also because I really want root.
I have an unlocked bootloader from when i first got my pixel and did this stuff, but now im unrooted on 7.1.1 because of that update awhile back, and want to update to 7.1.2 and root, but I've heard theres issues with rooting on the verizon because of bootloader, but that shoulden't be an issue since I unlocked it already (right? at least, I think? please let me know).
My only question (since i think i'll be able to follow this guide once I get the answer to this) is in the post he says: "Works with 7.1.2 (NJH47F, Aug 2017)".......... but since i have the verizon pixel (small version, not XL), should i be downloading this version: 7.1.2 (NHG47Q, Aug 2017, Verizon).... Or would it just be acceptable to allow my phone to auto download the update i have on it right now? Or must I download the NON verizon version as stated in the post and flash that one? Thanks for the help guys!
Thanks for any help!
-Synk
If your bootloader is actually unlocked then no update that you flash can lock it. The people that were having problems on Verizon had phones where the OEM Unlock option was there and then after a Verizon update was greyed out. But those people didn't have unlocked bootloaders. Once the bootloader on the phone is unlocked Verizon can't lock it again.
The Pixel phone isn't really a good one to root once and then forget about it because sometimes the instructions change--people needed to flash a boot signature file one month to maintain root but didn't need to do it anymore the following month. Sometimes a particular version of SU stops working after an update and you have to download a newer version. The Pixel isn't like a Nexus where flashing and rooting was simple and easy.
I don't know of any reason you wouldn't be able to root after flashing a Verizon image as long as your bootloader is unlocked but someone with experience rooting a Verizon phone would be better able to answer that.
jhs39 said:
If your bootloader is actually unlocked then no update that you flash can lock it. The people that were having problems on Verizon had phones where the OEM Unlock option was there and then after a Verizon update was greyed out. But those people didn't have unlocked bootloaders. Once the bootloader on the phone is unlocked Verizon can't lock it again.
The Pixel phone isn't really a good one to root once and then forget about it because sometimes the instructions change--people needed to flash a boot signature file one month to maintain root but didn't need to do it anymore the following month. Sometimes a particular version of SU stops working after an update and you have to download a newer version. The Pixel isn't like a Nexus where flashing and rooting was simple and easy.
I don't know of any reason you wouldn't be able to root after flashing a Verizon image as long as your bootloader is unlocked but someone with experience rooting a Verizon phone would be better able to answer that.
Click to expand...
Click to collapse
Thank you so much for the explanation. Truly, it's actually crazy how I was unable to find all of this neatly, nicely, and simply stated. Great to hear, I'm going to go on rooting, here's to hoping I don't blow it up.