Good day all,
I noticed several cluttered threads in Q&A that are becoming more of a discussion than question and answer format.
I wanted to make this thread as a one stop shop for all things Root and Bootloader related for the G-930T (Tmobile Galaxy Note 7).
Please discuss root, bootloader and work with each other in here.
Please do not discuss the bounty in here, and do not clutter the bounty thread with casual conversation about root.
Cheers,
Baja
Sent from my SM-N930T using XDA-Developers mobile app
Well we know the Bootloader is locked and can only be unlocked by Samsung( That's not gonna happen).
Based on what happened and is continuing to happen with the S7 there is a possibility of achieving Root on the N7(ENG) which I will not be a guinea pig and try. I'm sure others will if and when it's available.
SBERG117 said:
Well we know the Bootloader is locked and can only be unlocked by Samsung( That's not gonna happen).
Based on what happened and is continuing to happen with the S7 there is a possibility of achieving Root on the N7(ENG) which I will not be a guinea pig and try. I'm sure others will if and when it's available.
Click to expand...
Click to collapse
I second this. Just wish we could keep samsung pay after root. Not gonna happen but wishful thinking.
Sent from my SM-N910T3 using Tapatalk
Just want to note that you may not want to take any updates if you plan on rooting in the future (if an exploit is available).
dirtymindedx said:
I second this. Just wish we could keep samsung pay after root. Not gonna happen but wishful thinking.
Sent from my SM-N910T3 using Tapatalk
Click to expand...
Click to collapse
Not true on my Nexus 6 we could not use Android pay with root. But someone came up with a walk around systemless root and it worked.
Sent from my SM-N930T using Tapatalk
jason504 said:
Not true on my Nexus 6 we could not use Android pay with root. But someone came up with a walk around systemless root and it worked.
Sent from my SM-N930T using Tapatalk
Click to expand...
Click to collapse
he said Samsung pay...two separate paying system
Chord_Hugo87 said:
he said Samsung pay...two separate paying system
Click to expand...
Click to collapse
No I know what he said but if there can be a walk around for one (should) be able to do one for the other.
Sent from my SM-N930T using Tapatalk
jason504 said:
No I know what he said but if there can be a walk around for one (should) be able to do one for the other.
Sent from my SM-N930T using Tapatalk
Click to expand...
Click to collapse
not possible if you trip knox and in order to get root you need to trip knox.
jason504 said:
No I know what he said but if there can be a walk around for one (should) be able to do one for the other.
Sent from my SM-N930T using Tapatalk
Click to expand...
Click to collapse
One of them is from Google and doesn't care about Knoxx and the other is from Samsung and does care about Knoxx. Two completely different things. The Samsung Pay not working after Knoxx is tripped has been going on for a year as of tomorrow. The systemless root that doesn't trip Knoxx is one thing but as soon as you start flashing, kiss Samsung Pay goodbye.
Yep, and worst of all. Once it's tripped, Samsung pay will never work again on that device
Sent from my SM-N930T using XDA-Developers mobile app
Luckily for me, if root becomes available its a no-brainer. Samsung pay doesn't support my bank, and I won't have a credit card. Even if Samsung Pay would work for me, it would still be an easy choice to have root instead. I would like to play around with altering the speaker volume, deleting bloatware, making tweaks, ad blocking, etc.
Did anyone ever get the files that Beans asked for over to him?
Why can't those of us with t variants just flash the unlocked w8 bootloader? Seems like we've been left an out? Yes?
Sent from my SM-N920T using Tapatalk
Rx8Driver said:
Why can't those of us with t variants just flash the unlocked w8 bootloader? Seems like we've been left an out? Yes?
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
In order for you to flash anything to any bootloader, it needs to be unlocked. With it locked Odin says it can't. So till the note 7 gets unlocked (in time) we have to wait. Phone only few days old, be work around soon.
drum747 said:
Did anyone ever get the files that Beans asked for over to him?
Click to expand...
Click to collapse
Good question
@BeansTown106 did you ever get a Tar?
Sent from my SM-N930T using XDA-Developers mobile app
It appears this guy is in the process of getting the stock firmware uploaded
http://forum.xda-developers.com/showthread.php?t=3444003
Sent from my SM-N930T using XDA-Developers mobile app
ethanscooter said:
Just want to note that you may not want to take any updates if you plan on rooting in the future (if an exploit is available).
Click to expand...
Click to collapse
That is true. Android 7 Nougat will have more security features that Samsung is going to take advantage of with the Galaxy Note 7. That may make unlocking bootloader and rooting even more difficult.
-
It looks like the sprint guys have obtained an engineering bootloader/kernel. Someone may be able to do something with this for us..
Sent from my SM-N930T using XDA-Developers mobile app
I got the stock n930t boot.img but im wondering is how would i go by making a kernel "engboot". I also removed dm-verity but that didn't work. All i get is a failed message through odin. Another testing i have done is I even just modified one simple thing in the stock kernel say in default.prop ro.secure=1 to =0 and i still get a failed messsge. Once i flashed the stock unmodified version of the kernel i would get a success message and works which means any modification to the kernel will cause it to fail i just have to see what in the kernel checks for md5 changes or it may be something else if more devs can help together, then we can get this working.
jovy23 said:
I got the stock n930t boot.img but im wondering is how would i go by making a kernel "engboot". I also removed dm-verity but that didn't work. All i get is a failed message through odin. Another testing i have done is I even just modified one simple thing in the stock kernel say in default.prop ro.secure=1 to =0 and i still get a failed messsge. Once i flashed the stock unmodified version of the kernel i would get a success message and works which means any modification to the kernel will cause it to fail i just have to see what in the kernel checks for md5 changes or it may be something else if more devs can help together, then we can get this working.
Click to expand...
Click to collapse
Bro, please stop trying. This is obviously far above your skill level.
1. There is no way to convert a kernel to an "engboot."
2. The bootloader is LOCKED, so anything you do to the kernel's ramdisk will obviously not work because the whole point of dm-verity and a locked bootloader, among other things, is to stop the modification of system images, including the kernel ramdisk. Surely you didn't think it would be as easy as unpacking the boot.img, changing the ro.secure value from 1 to 0, then repacking..... did you?
3. The kernel doesn't "check" for anything MD5 related.
4. The bootloader is rejecting your changes, not the kernel.
5. Nothing you do to the boot.img, no matter how many devs you have, will do any good.
Hang tight, guys. We're trying everything we can.
Related
Is there any word on whether or not the bootloader is encrypted? If so does anyone have any idea on what the chances of it being unlocked is, as this is the only thing stopping me from buying this phone.
Sent from my SCH-I535 using Tapatalk 4
I suspect we will end up with loki. At least i hope so.
Sent from my LG-D800 using Tapatalk 4
I'm ready for the complete package so I can start flashing
Sent from my VS980 4G using Tapatalk 4
bri315317 said:
I suspect we will end up with loki. At least i hope so.
Sent from my LG-D800 using Tapatalk 4
Click to expand...
Click to collapse
I'm unfamiliar with loki, what is that?
Sent from my SCH-I535 using Tapatalk 4
soapinmouth said:
I'm unfamiliar with loki, what is that?
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Basically it is an exploit to bypass the bootloader to flash roms and kernels. DJRBLISS found it for the S4 and it is working with the G pro. Read more about it here
Other options would be Hash's safety strap or if they can figure out flash gordon for roms. But I still hope for a full unlock sometime...
Is there a way to check if the bootloader is locked? I'm getting a T-mobile version and am curious if they have it locked as well.
bri315317 said:
I suspect we will end up with loki. At least i hope so.
Sent from my LG-D800 using Tapatalk 4
Click to expand...
Click to collapse
Loki is old. Most manufactures stopped using as soon as Dan Bliss posted how he exploited it.
I am fairly confident this is not going to be Loki. I hope I am wrong but...
Its easy to test if you are rooted.
Pull a system dump, mod the boot.img (Decompile it, maybe just put a simple line in the default.prop then recompile), then run it through loki. After loki just DD it back in place.
If you phone boots then its loki! And I run to AT&T to buy one no questions asked...
If your phone doesnt boot... you bricked it but did so for a noble cause! And for that I would salute you!
All of the above is true and accurate... But with a grain of angry sarcasm... Im pretty sure this is not going to be Loki. If so it would have recovery and ROMS by now.
joshuadjohnson22 said:
Basically it is an exploit to bypass the bootloader to flash roms and kernels. DJRBLISS found it for the S4 and it is working with the G pro. Read more about it here
Other options would be Hash's safety strap or if they can figure out flash gordon for roms. But I still hope for a full unlock sometime...
Click to expand...
Click to collapse
You mean WAS working with the S4...
Samsung changed the method 100% and no longer works with ANY Samsung device that is up to date.
Sorry guys, not trying to be a downer... I really want this phone... Very angry with the games carriers play.
scrosler said:
Loki is old. Most manufactures stopped using as soon as Dan Bliss posted how he exploited it.
I am fairly confident this is not going to be Loki. I hope I am wrong but...
Its easy to test if you are rooted.
Pull a system dump, mod the boot.img (Decompile it, maybe just put a simple line in the default.prop then recompile), then run it through loki. After loki just DD it back in place.
If you phone boots then its loki! And I run to AT&T to buy one no questions asked...
If your phone doesnt boot... you bricked it but did so for a noble cause! And for that I would salute you!
All of the above is true and accurate... But with a grain of angry sarcasm... Im pretty sure this is not going to be Loki. If so it would have recovery and ROMS by now.
Click to expand...
Click to collapse
I think it's aboot.img that gets modded for Loki on this phone.
Sent from my LG-D800 using Tapatalk 4
djkinetic said:
I think it's aboot.img that gets modded for Loki on this phone.
Sent from my LG-D800 using Tapatalk 4
Click to expand...
Click to collapse
No, thats not correct.
When the system boots, it looks at aboot and verifies its signed. Then from there, it verifies that boot.img is signed, then on...
aboot is just first in the chain, and if hacked appropriately, would eliminate the need for any and all loki methods...
However, hacking the aboot is not something I recommend anyone trying to do... Unless of course they have done it before...
Didint you just brick your phone because of a hack attempt at aboot?
scrosler said:
No, thats not correct.
When the system boots, it looks at aboot and verifies its signed. Then from there, it verifies that boot.img is signed, then on...
aboot is just first in the chain, and if hacked appropriately, would eliminate the need for any and all loki methods...
However, hacking the aboot is not something I recomend anyone trying to do...
Didint you just brick your phone because of a hack attempt at aboot?
Click to expand...
Click to collapse
Ah ic
Sent from my GT-I9505G using Tapatalk 4
---------- Post added at 12:43 PM ---------- Previous post was at 12:43 PM ----------
scrosler said:
No, thats not correct.
When the system boots, it looks at aboot and verifies its signed. Then from there, it verifies that boot.img is signed, then on...
aboot is just first in the chain, and if hacked appropriately, would eliminate the need for any and all loki methods...
However, hacking the aboot is not something I recommend anyone trying to do... Unless of course they have done it before...
Didint you just brick your phone because of a hack attempt at aboot?
Click to expand...
Click to collapse
Yup the devs on irc have me testing various aboots
Sent from my GT-I9505G using Tapatalk 4
djkinetic said:
Ah ic
Sent from my GT-I9505G using Tapatalk 4
Click to expand...
Click to collapse
Trust me man, I played this game on Samsung... Then quit it and went back to HTC.
With Samsung they dropped the loki method of kernels. So now, they have yet to have an unlocked bootloader...
I can only SUSPECT this phone is using the same method the Samsungs are now using...
Otherwise we would have lokied the ***** and we would all be crack flashing :highfive: :angel:
djkinetic said:
Yup the devs on irc have me testing various aboots
Sent from my GT-I9505G using Tapatalk 4
Click to expand...
Click to collapse
Yeah, they are going one route to unlock... Which would be the most optimal, yet most risky...
Although on other Samsung devices they closed this loop hold...
Unless someone has an aboot that has been leaked by LG for the device that does not have the checks involved this may prove as impossible as it does for the Samsung devices..
I hope I am wrong...
scrosler said:
Yeah, they are going one route to unlock... Which would be the most optimal, yet most risky...
Although on other Samsung devices they closed this loop hold...
Unless someone has an aboot that has been leaked by LG for the device that does not have the checks involved this may prove as impossible as it does for the Samsung devices..
I hope I am wrong...
Click to expand...
Click to collapse
Yeah... swapping for an HTC One is looking better and better as time goes on. I know it's only been a few days since launch, FYI.
DeaconBoogie said:
Yeah... swapping for an HTC One is looking better and better as time goes on. I know it's only been a few days since launch, FYI.
Click to expand...
Click to collapse
Sad isnt it?
I will only be buying international phones going forward.
No more carrier subsidies for me :good:
scrosler said:
Sad isnt it?
I will only be buying international phones going forward.
No more carrier subsidies for me :good:
Click to expand...
Click to collapse
My problem is that VZW is the only LTE carrier in my area that doesn't completely suck. Their coverage is just too good...
DeaconBoogie said:
My problem is that VZW is the only LTE carrier in my area that doesn't completely suck. Their coverage is just too good...
Click to expand...
Click to collapse
Yeah, AT&T Finally got LTE turned on a couple weeks ago.
I said, If I have to I will go back to Sprint 2G to have an unlocked phone.
And if you buy Int phones you cant run them on Verizon.
THEY rule they air
scrosler said:
Yeah, they are going one route to unlock... Which would be the most optimal, yet most risky...
Although on other Samsung devices they closed this loop hold...
Unless someone has an aboot that has been leaked by LG for the device that does not have the checks involved this may prove as impossible as it does for the Samsung devices..
I hope I am wrong...
Click to expand...
Click to collapse
Yea hope so too, but its a shame that its locked down, the device itself is awesome, Sadly ill prolly get a nexus 5 for my crack flash addiction lol
scrosler said:
Yeah, AT&T Finally got LTE turned on a couple weeks ago.
I said, If I have to I will go back to Sprint 2G to have an unlocked phone.
And if you buy Int phones you cant run them on Verizon.
THEY rule they air
Click to expand...
Click to collapse
Think we'll have a definitive answer in a week as to the prospects of unlocking?
DeaconBoogie said:
Think we'll have a definitive answer in a week as to the prospects of unlocking?
Click to expand...
Click to collapse
Once again... On pure speculation...
Impossible to know!
I just know the S4 has been re-locked for a couple months and no one has made any posted progress. I am "assuming" this phone uses the same method as Samsung. LG has always tended to play "follow Samsung."
So with that said... I would be watching the S4 forums for an answer...
The Verizon Note 3 variant N900V has had it's bootloader bypassed by @Hashcode and custom recovery has now been achieved on that device. I talked to @bajasur who is running their bounty thread and he believes that the same safestrap method could possibly be used on the N900A (our version). If @Hashcode can get this to work on the N900A I am sure development will move quickly so get over to our bounty thread and make your bounty pledges now!!! http://forum.xda-developers.com/showthread.php?t=2493369
See @bajasur's N900V Bounty Thread here...
http://forum.xda-developers.com/showthread.php?t=2473918
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Awesome!
Sent from my SAMSUNG-SM-N900A using Tapatalk
slidesear said:
Awesome!
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
Definitely great news!!!
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
I don't mean to be a downer, but I'm still on the fence whether I can get this working on the AT&T variant.
So let's hold off on any specific donations. :/
Fingers crossed! this would be great news!!!
Hashcode said:
I don't mean to be a downer, but I'm still on the fence whether I can get this working on the AT&T variant.
So let's hold off on any specific donations. :/
Click to expand...
Click to collapse
Pledges....meant pledges. Will update the OP...sorry @Hashcode.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
That would be pretty sweet
Sent from my SAMSUNG-SM-N900A using Tapatalk
Does this trip knox
Sent from my SM-N900W8 using Tapatalk
Canadoc said:
Does this trip knox
Sent from my SM-N900W8 using Tapatalk
Click to expand...
Click to collapse
At this point we will just have to wait and see what happens. I would imagine it doesn't but since it is currently being worked on and not confirmed we will have to just be patient...which I clearly wasn't with this thread.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Isn't this the same thing that happened with the s4? Bootloader exploited on verizon variant, didnt know if it would work for anyone else and it did?
Sent from my VS980 4G using Tapatalk
MrPlNK said:
Isn't this the same thing that happened with the s4? Bootloader exploited on verizon variant, didnt know if it would work for anyone else and it did?
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
The difference is ATT in addition to a locked bootloader made SELinux Enforcing. The VZW has permissive from what I've read.
mircury said:
The difference is ATT in addition to a locked bootloader made SELinux Enforcing. The VZW has permissive from what I've read.
Click to expand...
Click to collapse
I am probably completely wrong as Android is a different beast than regular Linux but, in the Linux OS world SELinux has little to do with the bootloader. It is a set of modules that load once the OS begins to boot up as part of the kernel in runlevel 1. So by the time the SELinux modules are loading you are already "booted". I hope this is the case for Android as well as I am past my 14 days on this phone and love the hardware I just would really like to be able to run some custom kernels and load AOSP based roms if I choose to. This is certainly the last phone I will be buying from AT&T regardless, so disappointed.
kennonk said:
I am probably completely wrong as Android is a different beast than regular Linux but, in the Linux OS world SELinux has little to do with the bootloader. It is a set of modules that load once the OS begins to boot up as part of the kernel in runlevel 1. So by the time the SELinux modules are loading you are already "booted". I hope this is the case for Android as well as I am past my 14 days on this phone and love the hardware I just would really like to be able to run some custom kernels and load AOSP based roms if I choose to. This is certainly the last phone I will be buying from AT&T regardless, so disappointed.
Click to expand...
Click to collapse
Normally it doesn't have anything to do with the bootloader but in this case since we can't crack or modify the bootloader we have to hijack the real /system into loading a recovery on a special partition along with a fake /system located on the internal sdcard. Whether or not SELinux enforcement policies prevent this or causes problems later if it does boot, we don't know yet. What it does do for sure is make it more difficult.
Same
kennonk said:
I am probably completely wrong as Android is a different beast than regular Linux but, in the Linux OS world SELinux has little to do with the bootloader. It is a set of modules that load once the OS begins to boot up as part of the kernel in runlevel 1. So by the time the SELinux modules are loading you are already "booted". I hope this is the case for Android as well as I am past my 14 days on this phone and love the hardware I just would really like to be able to run some custom kernels and load AOSP based roms if I choose to. This is certainly the last phone I will be buying from AT&T regardless, so disappointed.
Click to expand...
Click to collapse
Same here. I hate that AT&T is doing this. It's crazy how the tables have turned, as it used to be (As with the S4) we would get a way to flash a recovery before the VZW variant, but now it seems that has changed. Is the Knox option only on our variant or is it on VZW too?
I got super excited when I first saw this but then depressed when I found out that it hasn't fully been achieved... what is the difference from the way that the s4 was cracked? It had knox too didn't it?
Sent from my SAMSUNG-SM-N900A using Tapatalk HD
I have verizon and no it doesn't trip knox
tropazr said:
The Verizon Note 3 variant N900V has had it's bootloader bypassed by @Hashcode and custom recovery has now been achieved on that device. I talked to @bajasur who is running their bounty thread and he believes that the same safestrap method could possibly be used on the N900A (our version). If @Hashcode can get this to work on the N900A I am sure development will move quickly so get over to our bounty thread and make your bounty pledges now!!! http://forum.xda-developers.com/showthread.php?t=2493369
See @bajasur's N900V Bounty Thread here...
http://forum.xda-developers.com/showthread.php?t=2473918
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Any progress on unlocking bootloader of N900A?
We highly expect this.
Thank you.
SunnyOK said:
Any progress on unlocking bootloader of N900A?
We highly expect this.
Thank you.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=48555170
We have Safestrap now. Read up on it!
Sent from my SAMSUNG-SM-N900A using Tapatalk
SunnyOK said:
Any progress on unlocking bootloader of N900A?
We highly expect this.
Thank you.
Click to expand...
Click to collapse
Have you not looked in the development forums?
Sent from my SAMSUNG-SGH-I467 using Tapatalk 4
Agent said:
Have you not looked in the development forums?
Sent from my SAMSUNG-SGH-I467 using Tapatalk 4
Click to expand...
Click to collapse
Unfortunately the bootloader is still locked and hasn't been bypassed. What safestrap does is hijack the boot process once it reaches the /system partition. That is after the bootloader. It then runs a modified recovery. This is why you can't run custom kernels on it yet. The /boot partition is still protected. Don't get me wrong though it's a huge step in the right direction.
Is there any way to root my phone.
The system version is 183.46.15.
If your boot loader is locked, no.
Sent from my HTC6525LVW using Tapatalk
Nope. Sorry. Both bootloader and root are patched.
RikRong said:
If your boot loader is locked, no.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Is there any guru working on the root? thinking about selling the phone if no hope
everseen said:
Is there any guru working on the root? thinking about selling the phone if no hope
Click to expand...
Click to collapse
Not gonna come as far as I can see from now. Just go ahead and sell it. Plenty of alternatives on the market.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
There are some RAZR M that are unlocked on Swappa as well.
tianor said:
Is there any way to root my phone.
The system version is 183.46.15.
Click to expand...
Click to collapse
Did u get unlocked, i am also stricken with it
Love Cyaan said:
Did u get unlocked, i am also stricken with it
Click to expand...
Click to collapse
No luck yet.
root and unlock 183.46.15
everseen said:
No luck yet.
Click to expand...
Click to collapse
Me too, me too!
Googleing this search daily " unlock 183.46.15 site:forum[.]xda-developers[.]com"
Checked ever corner of XDA, alas no solution on how to root and unlock 183.46.15
Devs @ XDA, come on champs gave us something, so can we also enjoy the privilege of CM12. Many are waiting for it fingers crossed
Mods/all, its only a humble request to Dev & not that if being annoyed.
Qualcomm patched the second layer (sbl2) of the second-stage bootloader, to take care of possible exploitation, effectively making it impenetrable. So for some individuals, we're pretty much out of luck. I wouldn't be sure of the possible exploits (the problem is, after that patch, it makes it even harder, although not impossible). Previous Kit Kat rooting exploitation relies on the permission requestion layer (futex) of the Linux kernel, as discovered by the former PS3 hacker, GeoHot, while it's patched by now. It's possible there is already a new rooting exploit by now, just don't hold the breath.
It's possible there is already a new rooting exploit by now, just don't hold the breath.
Click to expand...
Click to collapse
Can you please be more concretely?
I may not be up to date, been out of town for a bit, and figuring out a way to unbrick a few RAZR Ms.
However, the reason I said not to hold the breath is because of Verizon demanding a hard fix for rooting so that way almost any root exploits simply fail on arrival. This phone company also WANTS locked BIOS so no one can install custom recovery and OS "just because it put customer services in jeopardy".
That's really bad, can't believe that there is no chance to root or bootunlock this device.
By the way, do you know any way to disable/delete/freeze modem fast dormancy service without rooting phone? Or to made some changes in build.prop file?
Simply force close Modem fastdormancy first then disable it in app manager, it will then quit. And, editing build.prop requires root (write protection).
Force close works but disable button is inactive.
Sent from my XT907 using XDA Free mobile app
Ah, right.... I wonder why Verizon would disable some app manager features.
I'm outside of us, my carrier operates in gsm network and does not support fast dormancy, therefore phone reboots and can't wake up on power button when using h+. Thats why I need to edit build.prop and to dothis I need root access to file system.
Sent from my XT907 using XDA Free mobile app
Makes sense. However, I may look for new exploit, but since Futex is removed, it is not so simple.
Dr. Mario, are you developer?
Sent from my XT907 using XDA Free mobile app
Not officially, yet. But I know how the software works underneath the pretty UI, even down to the machine codes. I have been modding Android for 3 years.
I have been out of the loop for at least a year running my s5 on a custom stable rom on KitKat. My charging port is starting to act up and thinking about getting a replacement from square insurance. But do t want it if I can't get the tether hack. Also I might ask if they will upgrade me to a s6
cell128 said:
I have been out of the loop for at least a year running my s5 on a custom stable rom on KitKat. My charging port is starting to act up and thinking about getting a replacement from square insurance. But do t want it if I can't get the tether hack. Also I might ask if they will upgrade me to a s6
Click to expand...
Click to collapse
If you have OD5 or earlier as your OTA update, you can still downgrade and root. If you have OE1 or later as your OTA, you are stuck and cannot downgrade for root.
Is anyone even trying to root OE1??
Sent from my SM-G900V using Tapatalk
gerland said:
Is anyone even trying to root OE1??
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
No stop asking
??? Why would I not ask?
Sent from my SM-G900V using Tapatalk
gerland said:
??? Why would I not ask?
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
because it's been done a thousand times. No one has openly admitted to trying to crack it, no matter how many people insist they are doing it. It's not happening.
Someone needs to try to root the dam thing.
sideball8 said:
Someone needs to try to root the dam thing.
Click to expand...
Click to collapse
We are waiting for you to figure it out and achieve root.
I'm just trying to find root package so I can downgrade my active and root it. But I'm having trouble finding it. Can you give me any help please?
S5 Active
shadavis08 said:
I'm just trying to find root package so I can downgrade my active and root it. But I'm having trouble finding it. Can you give me any help please?
S5 Active
Click to expand...
Click to collapse
I'm guessing this is impossible?
S5 active is non rootable not enough demand
Sent from my VS986 using Tapatalk
shadavis08 said:
S5 active is non rootable not enough demand
Click to expand...
Click to collapse
The demand is not the issue.
Sent from my Galaxy S5 using XDA Labs
Hmm you think. Because if this particular phone sold millions and there were lots more people who wanted to root it there would be an root option for certain.
Sent from my VS986 using Tapatalk
shadavis08 said:
Hmm you think. Because if this particular phone sold millions and there were lots more people who wanted to root it there would be an root option for certain.
Click to expand...
Click to collapse
Demand doesn't make exploits pop up.
Sent from my Galaxy S5 using XDA Labs
The more demand there is for exploits the more people you will have looking for exploits. There is no demand at this point
Sent from my VS986 using Tapatalk
I think I bricked my Galaxy S5 Active G870A Lollipop 5.1.1
So I tried to downgrade my phone to Kit Kat and thought I had followed the instructions. I installed Odin and ran it the way I was instructed and it passed. I tried to flash the updates needed via external SD card and the updates seemed to be going well. Yet just before its done I see this red error "sideload install/*something* error (Status 7). My friend and have tried presumably everything but it won't flash the stock or any other ROM. If I'm in boot mode and try to use Odin it will fail with Fail Auth Success 0/Failed 1. Not sure what I can do. Any help would be great. Again Odin does not seem to work. Also, if I can't fix it would AT&T replace it with the insurance I have.
you CAN NOT downgrade, take it to at&t dealer and pray