According to the firewater twitter account (the same one that showed off the vzw s5 bootloader unlock) there is a vulnerability in the TrustZone kernel/snapdragon 805 devices. While the s5 doesn't have an 805 it does appear to have TrustZone, which, according to beaups, once again the same person who showed off the bl unlock, there is probably a way to unlock the bl on the s5. Apparently it's similar to how the droid turbo was unlocked, and it lists other devices that use the 805 that could benefit. Although the s5 isn't listed, I'm assuming this is similar (if not the same) method he used to unlock the s5 previously. The only problem is he left off before the exploit can be completed, so people will have to work off of his research. Anyone who can understand what this means and perhaps develop something, take a look here at some documentation he released on the subject.
I looked at the PDF and I wouldn't bank on it. If the exploit is in our device I would be surprised.
Sent from my SM-G900V using XDA Free mobile app
@jcase can someone who knows a thing or two about this get in here and see if this is a possibility?
mrjiggywiggy said:
According to the firewater twitter account (the same one that showed off the vzw s5 bootloader unlock) there is a vulnerability in the TrustZone kernel/snapdragon 805 devices. While the s5 doesn't have an 805 it does appear to have TrustZone, which, according to beaups, once again the same person who showed off the bl unlock, there is probably a way to unlock the bl on the s5. Apparently it's similar to how the droid turbo was unlocked, and it lists other devices that use the 805 that could benefit. Although the s5 isn't listed, I'm assuming this is similar (if not the same) method he used to unlock the s5 previously. The only problem is he left off before the exploit can be completed, so people will have to work off of his research. Anyone who can understand what this means and perhaps develop something, take a look here at some documentation he released on the subject.
Click to expand...
Click to collapse
Hariiiii said:
@jcase can someone who knows a thing or two about this get in here and see if this is a possibility?
Click to expand...
Click to collapse
I work closely with beaups, we are the authors of SunShine, the app that unlocks the droid turbo. I find it VERY hard to believe beaups told you there is a route to unlock the s5 through the Trustzone, I call bullpoop on that.
This vulnerability will never lead to an unlock on the S5, nor are we actively looking into it.
jcase said:
I work closely with beaups, we are the authors of SunShine, the app that unlocks the droid turbo. I find it VERY hard to believe beaups told you there is a route to unlock the s5 through the Trustzone, I call bullpoop on that.
This vulnerability will never lead to an unlock on the S5, nor are we actively looking into it.
Click to expand...
Click to collapse
Well it was nice to dream for a bit anyways. Thanks for clearing things up jcase.
jcase said:
I work closely with beaups, we are the authors of SunShine, the app that unlocks the droid turbo. I find it VERY hard to believe beaups told you there is a route to unlock the s5 through the Trustzone, I call bullpoop on that.
This vulnerability will never lead to an unlock on the S5, nor are we actively looking into it.
Click to expand...
Click to collapse
Ok so based on the video I've seen of him unlocking a VZW S5 bootloader can you tell us if an unlock has been discovered or on its way?
Sent from my SM-G900V using Tapatalk
I think the video answers the question about if an unlock "has been discovered". No plans for release at this time.
Sent from my XT1254 using Tapatalk
beaups said:
I think the video answers the question about if an unlock "has been discovered". No plans for release at this time.
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
Makes sense. But if you don't mind me asking, whatever exploit that you are using, is that S5 specific or have you tried on other Sammy devices such as N3?
Walter.White said:
Makes sense. But if you don't mind me asking, whatever exploit that you are using, is that S5 specific or have you tried on other Sammy devices such as N3?
Click to expand...
Click to collapse
It might work on other models; I don't own any other Samsung devices, so I didn't really research it much further.
--beaups
beaups said:
It might work on other models; I don't own any other Samsung devices, so I didn't really research it much further.
--beaups
Click to expand...
Click to collapse
just out of curiosity what would happen if you flashed another boot loader or whatever it was that unlocked the boot loader on other phones? would it hard brick our phone? or is this something you go into your phone manually to do?
Veid71 said:
just out of curiosity what would happen if you flashed another boot loader or whatever it was that unlocked the boot loader on other phones? would it hard brick our phone? or is this something you go into your phone manually to do?
Click to expand...
Click to collapse
I can verify that it will hard brick the phone. At least it did when I accidentally attempted on a Galaxy S4.
Why isn't the method used to unlock the VZW S5 being released? Or was that just a faked video?
Thorkle said:
Why isn't the method used to unlock the VZW S5 being released? Or was that just a faked video?
Click to expand...
Click to collapse
I'm thinking it was faked since they won't release it.
jjdavis699 said:
I'm thinking it was faked since they won't release it.
Click to expand...
Click to collapse
Of course it wasn't faked. Beaups is beyond reproach in this regard.
Sent from my XT1254 using Tapatalk
jjdavis699 said:
I'm thinking it was faked since they won't release it.
Click to expand...
Click to collapse
Give me a break.
jjdavis699 said:
I'm thinking it was faked since they won't release it.
Click to expand...
Click to collapse
i really dont think its faked but i am quite curious as to why it hasnt been released maybe he doesnt want them to patch it and hes waiting for the next big version update to release it or like everyones said maybe its illegal im not sure yet
Veid71 said:
i really dont think its faked but i am quite curious as to why it hasnt been released maybe he doesnt want them to patch it and hes waiting for the next big version update to release it or like everyones said maybe its illegal im not sure yet
Click to expand...
Click to collapse
There could be a few things. Fear of a lawsuit, they may want to test it further, they may want to see if it can be used on other devices, they may want to see if anyone else can figure it out, etc. Sure they could sell unlocks on a per device basis but if big red wants to sue them, no amount of money made from selling the bootloader unlocks will pay for a court case or what verizon would want in "damages" even though we should be allowed to unlock the devices we paid for, which in turn would be a good argument for their defense in court which they might win with.
Who knows?
jjdavis699 said:
I'm thinking it was faked since they won't release it.
Click to expand...
Click to collapse
OK look, I regret saying that. I was really tired. Beaups, if I offended you in some way, forgive me. I just got this phone and just want to get root.
gmerdude said:
Why is this still being talked about.......?
Sent from my SM-G900V
Click to expand...
Click to collapse
Because the community still wants it.
---------- Post added at 06:29 PM ---------- Previous post was at 06:05 PM ----------
jjdavis699 said:
Because the community still wants it.
Click to expand...
Click to collapse
Anyway, @beaups, I'm asking you as a fellow XDA member, who has been around for a long time, to please, give us the tools we need to make our device a playground. I'd love to be able to get a custom rom on my new phone, but without a bl unlock, I can't! My old Moto G, I went so as far as paying for your wonderful SunShine tool. I'm asking you, as a fellow nerd, to give us the keys to the kingdom. If you want someone to test the unlock, I'm ready and willing. I'm not afraid of Odin. If you want to keep it private, I respect that. Just release it to those who want it, maybe in a PM.
jjdavis699 said:
Because the community still wants it.
---------- Post added at 06:29 PM ---------- Previous post was at 06:05 PM ----------
Anyway, @beaups, I'm asking you as a fellow XDA member, who has been around for a long time, to please, give us the tools we need to make our device a playground. I'd love to be able to get a custom rom on my new phone, but without a bl unlock, I can't! My old Moto G, I went so as far as paying for your wonderful SunShine tool. I'm asking you, as a fellow nerd, to give us the keys to the kingdom. If you want someone to test the unlock, I'm ready and willing. I'm not afraid of Odin. If you want to keep it private, I respect that. Just release it to those who want it, maybe in a PM.
Click to expand...
Click to collapse
I do not know the persons involved, or see the video, but if they did unlock the BL damn right!! :thumbup::thumbup::beer::beer:
Goes to show there's always a way and makes me happy to know it was done. Where's that bounty $$ at??
Anyway - if it's not being released there's a reason as I'm sure it wasn't a cake walk. I for one when I make a music track after some hard work need to enjoy it a bit before I serve the dish.
Don't worry S5 fam --
Nice work beaups / crew!
Sent from my still locked down SM-G900V running PHX V10!
Related
Not taking away anything from the work Adam has done on this, we all appreciate it. But:
do you think Verizon had someone leak this after seeing everything they were trying to prevent was being accomplished with rooting and kexec?
No reason to keep getting bad publicity around this and lose customers that actually buy new phones becaus of it, right? It just makes sense, no?
No way...it was unlocked by the hard work of our devs! /Thread
droidstyle said:
No way...it was unlocked by the hard work of our devs! /Thread
Click to expand...
Click to collapse
I thought they said that an unsecured bootloader was leaked that helped do this.
http://rootzwiki.com/news/_/articles/general/verizons-sgs3-unlocked-thanks-to-leaked-unsecured-bootloader-r1054
The bootloader is from VRALE6. It's older than the first firmware (VRALEC) Samsung gave Verizon.
LLStarks said:
The bootloader is from VRALE6. It's older than the first firmware (VRALEC) Samsung gave Verizon.
Click to expand...
Click to collapse
samsung leak?
I think that sammy didn't want to spend all that money making a developer version for verizon and instead sammy had someone leak the bootloader instead.
Ya I have a feeling it was from Samsung also.
Sent from my SCH-I535 using xda premium
Devs had the leak since launch... They were just waiting for the bounty to riseeeee up!!!
VERIZON GALAXY S 3 (CM10)
Wow thats crazy...
DROID3R said:
Devs had the leak since launch... They were just waiting for the bounty to riseeeee up!!!
VERIZON GALAXY S 3 (CM10)
Click to expand...
Click to collapse
Wtf?
Sent from my unlocked Galaxy S3! We win, Verizon!
Inous said:
I think that sammy didn't want to spend all that money making a developer version for verizon and instead sammy had someone leak the bootloader instead.
Click to expand...
Click to collapse
I agree more with this statement. Samsung probably didn't want to lock it in the first place, gave it some time and then leaked it out and avoid more bad press.
If Verizon wanted good publicity... they'd just unlock it them self and soak it all in.
loveubuntu said:
Not taking away anything from the work Adam has done on this, we all appreciate it. But:
do you think Verizon had someone leak this after seeing everything they were trying to prevent was being accomplished with rooting and kexec?
No reason to keep getting bad publicity around this and lose customers that actually buy new phones becaus of it, right? It just makes sense, no?
Click to expand...
Click to collapse
nah.
stand back while i put on my tin foil hat
Karl said:
stand back while i put on my tin foil hat
Click to expand...
Click to collapse
You're gong to need to use the heavy duty foil for this one.
That really wouldn't surprise me if Samsung leaked it. Figure all their other phones already have the unlocked bootloader, and even a number of non GS3s from samsung have an unlocked bootloader, they seem to enjoy freedom as much as we do. I feel like they were forced to lock it down because of the big red... they didn't really have much of a choice. It was probably "lock it down or we don't sell it" meaning they would miss sales from the biggest US carrier.
Also, I remember someone mentioning that Samsung sometimes comes to the devs on these forums for help, it was funny because the guy who wrote the article had mentioned how every minute the devs had to spend trying to unlock the bootloader is one more they could have spent helping sammy. Kinda makes sense they would leak it, and in all honesty, we make up such a small part of verizons sales, I don't think they'd really even care that much... at least most of us understand what we're doing before we flash.
It very well could have been samsung that leaked just enough to make the unlock happen. We will never know and its best to just enjoy it and not point any fingers. Dont forget it was our very smart devs and our great community of people that turned that silver into gold.
Sent from my SCH-I535 using xda app-developers app
Or maybe they just got tired of people bothering their reps with questions about the bootloader... Haha.
Sent from my SCH-I535 using xda app-developers app
I personally think Sammy handed over the keys and the DEV's made sure it would run. Sammy doesn't want any bad publicity for any reason right now with all the constant battles with the stupid fruit company. I am not taking away any credit towards the DEV's that made this all possible, I am EXTREMELY thankful that they did this for the entire community.
you crazy people all act like "Samsung" is behind this, like the Samsung executives gathered around in a meeting and decided how they would release the unlocked bootloader to take down evil Big Red.
a leak like this is just some low level employee that was just as annoyed as us about the bootloader who is probably gonna get fired for leaking it.
there's no conspiracy.
Sent from my SCH-R530U using Tapatalk 2
Is it silly to hope this update will provide a pathway to re-unlocking the boot loader?
If so, I'll update, if not, I'll hold off. *le sigh*
It has been stated over and over again that the security hole was patched. 4.4 is even more secure. People need to stop asking about unlocking, it's getting old.
Sent from my HTC6525LVW using Tapatalk
RikRong said:
It has been stated over and over again that the security hole was patched. 4.4 is even more secure. People need to stop asking about unlocking, it's getting old.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
So, thanks for your asinine, non responsive reply. The question was whether the update could provide a pathway to unlocking. I assure you I am more familiar with the situation of the boot loader than you are. Acceptable answers would include
1. Yes
2. Yes because blah blah blah
3. No
4. No because blah blah blah
It has already been debated that the update could possibly include a change to the boot loader that could be exploited. Since there are those that are more knowledgeable than me and are able to give actual answers, I shall ask you to have a good day, sir.
brownrt said:
So, thanks for your asinine, non responsive reply. The question was whether the update could provide a pathway to unlocking. I assure you I am more familiar with the situation of the boot loader than you are. Acceptable answers would include
1. Yes
2. Yes because blah blah blah
3. No
4. No because blah blah blah
It has already been debated that the update could possibly include a change to the boot loader that could be exploited. Since there are those that are more knowledgeable than me and are able to give actual answers, I shall ask you to have a good day, sir.
Click to expand...
Click to collapse
It's just because this question gets asked over and over and over again. A little bit of searching will pretty much explain how this was an exploit, not an actual path to unlocking the bootloader. Once this was patched and fixed, the hopes of finding another exploit to unlock the bootloader on a phone that was not meant to have it's bootloader unlocked, were pretty much gone. Dan, who found the exploit, had done a LOT of exploring that took a lot of time, trial and error, etc. It wasn't an easy exploit that just showed up all of a sudden. The same goes for getting root. It's not an easy thing to get. As each patch comes out for Android, more and more exploits are patched. it's just part of the business to make the OS more secure.
Going to KK, as explained in the previous posters comments, pretty much makes it possible only if pigs fly. KK is more secure than JB and as each iteration of Android comes to being, it means it becomes more and more secure, which means less exploits to find to gain root. This also means, unless they reintroduce a new exploit (highly unlikely), then don't hold your breath for an unlocked bootloader as well.
If you're more aware of the situation than I, why did you ask about it? I meant no disrespect, but it has been frustrating seeing many people come in and asking about the BL, almost a year after the OTA was released to lock it back up. If you think KK will offer you a path to unlocking, then I invite you to go through the Moto X and S5 forums and see how much trouble they're having even attaining root.
iBolski said:
It's just because this question gets asked over and over and over again. A little bit of searching will pretty much explain how this was an exploit, not an actual path to unlocking the bootloader. Once this was patched and fixed, the hopes of finding another exploit to unlock the bootloader on a phone that was not meant to have it's bootloader unlocked, were pretty much gone. Dan, who found the exploit, had done a LOT of exploring that took a lot of time, trial and error, etc. It wasn't an easy exploit that just showed up all of a sudden. The same goes for getting root. It's not an easy thing to get. As each patch comes out for Android, more and more exploits are patched. it's just part of the business to make the OS more secure.
Going to KK, as explained in the previous posters comments, pretty much makes it possible only if pigs fly. KK is more secure than JB and as each iteration of Android comes to being, it means it becomes more and more secure, which means less exploits to find to gain root. This also means, unless they reintroduce a new exploit (highly unlikely), then don't hold your breath for an unlocked bootloader as well.
Click to expand...
Click to collapse
I don't see no pigs flying.
RikRong said:
It has been stated over and over again that the security hole was patched. 4.4 is even more secure. People need to stop asking about unlocking, it's getting old.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
See how asinine you were now?
brownrt said:
See how asinine you were now?
Click to expand...
Click to collapse
just run and do it they were helping you to the best of there knowledge at the time
billycar11 said:
just run and do it they were helping you to the best of there knowledge at the time
Click to expand...
Click to collapse
Feel free to explain to me what was helpful about their replies to the OP?
brownrt said:
Feel free to explain to me what was helpful about their replies to the OP?
Click to expand...
Click to collapse
they were right at the time and now things have changed the community as a whole was just really annoyed about getting the same question so much so they were frustrated and i know users who missed out were even more frustrated with not being able to do what they want with there phones so don't take your frustration out on people who were trying to tell you the right answer at the time , take it out on your boot loader and unlock it yayayayay
brownrt said:
Feel free to explain to me what was helpful about their replies to the OP?
Click to expand...
Click to collapse
Feel free to explain to me what was helpful about your posts?
brownrt said:
I don't see no pigs flying.
Click to expand...
Click to collapse
brownrt said:
See how asinine you were now?
Click to expand...
Click to collapse
Past has shown that as old as these phones are, a new root exploit, when all others have been patched, never occurs.
What just happened was luck:
Someone was working on a root exploit not specific to this phone AND you got lucky that it worked for the RAZR HD/MAXX/M.
You got REAL lucky with Motorola basically screwing up and re-introducing the bootloader unlock exploit. This was patched with version 9.18 last year and has been unavailable since then. THIS was dumb luck, period. Well, dumb on the part of Motorola for somehow falling back to the old code that is located on a protected zone of the phone. This was the ONLY way it could have be re-introduced and this RARELY happens, so again, dumb luck.
However, there is another OTA coming (I was just emailed asking to participate in it yesterday). I'm pretty sure it will fix the Towelroot exploit (all 2013 phones running 4.4.2 as well as any 4.4.2 kernel whose date is >= 6/3/2014 disallow the Towelroot exploit) as well as the bootloader exploit.
So, now is your chance to root and unlock the bootloader and it's high time everyone takes advantage of this because we will get the same questions, over and over again when the next OTA comes out.
Our main point, as has been stated, was if people would just search and read, rather than being lazy and just asking the same question that has already been asked a hundred times before, they would find their answer a lot quicker and the rest of us who have been helping so many other people would not feel we would have to rehash the same answer again. It's like being in class, the teacher explains something, and then 10 other people raise their hand and ask the teacher about the exact thing the teacher just went over, so now the teacher has to stop class, explain it again, and then 10 more kids raise their hands and ask the same, exact question. It pollutes the forums with the same questions and then the same answers.
We weren't being mean about saying no root, but what just happened was pure luck, especially with the bootloader unlock.
BTW, I think I did see a pig fly in Minecraft yesterday, so I guess they did fly which makes sense. :laugh:
In the end, we are all very happy for those that have locked bootloaders because now, they can root and then unlock this phone. But, they need to do it NOW before the next OTA comes out. And I can guarantee you that those who fail to do it will be back on here asking the same question over and over again. So, let's spread the word and beg and plead that these people root their phones now and unlock the bootloader so that when the next OTA comes out in the next couple of weeks, they won't have to worry about another root exploit, if at all.
Again, those with locked bootloaders got real lucky.
As far as warranty goes, who cares. The phone is old (18+ months) and most people who have turned in their locked phones for warranty have gotten their replacement without having to pay anything, so the company will accept them and they don't charge for it. Besides, would you rather have an unlocked phone knowing you can have root no matter what the next OTA does or do you want to wait and have to do an exploit? Sideloading is SO much easier and just requires a reboot into a custom recovery (like TWRP) and then you do an "adb sideload" and you reboot and your done. Pretty easy, no muss, no fuss.
billycar11 said:
they were right at the time and now things have changed the community as a whole was just really annoyed about getting the same question so much so they were frustrated and i know users who missed out were even more frustrated with not being able to do what they want with there phones so don't take your frustration out on people who were trying to tell you the right answer at the time , take it out on your boot loader and unlock it yayayayay
Click to expand...
Click to collapse
Being annoyed by the question is not the same as the quest. In fact the question had not been asked before.
killrhythm09 said:
Feel free to explain to me what was helpful about your posts?
Click to expand...
Click to collapse
It wasn't a post. It was a question. Questions are not meant to help anyone but the asker. Being that I was the asker and people that had no idea about actual development decided to answer, I am in fact the best person do judge whether or not they were helpful.
iBolski said:
Past has shown that as old as these phones are, a new root exploit, when all others have been patched, never occurs.
What just happened was luck:
Someone was working on a root exploit not specific to this phone AND you got lucky that it worked for the RAZR HD/MAXX/M.
You got REAL lucky with Motorola basically screwing up and re-introducing the bootloader unlock exploit. This was patched with version 9.18 last year and has been unavailable since then. THIS was dumb luck, period. Well, dumb on the part of Motorola for somehow falling back to the old code that is located on a protected zone of the phone. This was the ONLY way it could have be re-introduced and this RARELY happens, so again, dumb luck.
However, there is another OTA coming (I was just emailed asking to participate in it yesterday). I'm pretty sure it will fix the Towelroot exploit (all 2013 phones running 4.4.2 as well as any 4.4.2 kernel whose date is >= 6/3/2014 disallow the Towelroot exploit) as well as the bootloader exploit.
So, now is your chance to root and unlock the bootloader and it's high time everyone takes advantage of this because we will get the same questions, over and over again when the next OTA comes out.
Our main point, as has been stated, was if people would just search and read, rather than being lazy and just asking the same question that has already been asked a hundred times before, they would find their answer a lot quicker and the rest of us who have been helping so many other people would not feel we would have to rehash the same answer again. It's like being in class, the teacher explains something, and then 10 other people raise their hand and ask the teacher about the exact thing the teacher just went over, so now the teacher has to stop class, explain it again, and then 10 more kids raise their hands and ask the same, exact question. It pollutes the forums with the same questions and then the same answers.
We weren't being mean about saying no root, but what just happened was pure luck, especially with the bootloader unlock.
BTW, I think I did see a pig fly in Minecraft yesterday, so I guess they did fly which makes sense. :laugh:
In the end, we are all very happy for those that have locked bootloaders because now, they can root and then unlock this phone. But, they need to do it NOW before the next OTA comes out. And I can guarantee you that those who fail to do it will be back on here asking the same question over and over again. So, let's spread the word and beg and plead that these people root their phones now and unlock the bootloader so that when the next OTA comes out in the next couple of weeks, they won't have to worry about another root exploit, if at all.
Again, those with locked bootloaders got real lucky.
As far as warranty goes, who cares. The phone is old (18+ months) and most people who have turned in their locked phones for warranty have gotten their replacement without having to pay anything, so the company will accept them and they don't charge for it. Besides, would you rather have an unlocked phone knowing you can have root no matter what the next OTA does or do you want to wait and have to do an exploit? Sideloading is SO much easier and just requires a reboot into a custom recovery (like TWRP) and then you do an "adb sideload" and you reboot and your done. Pretty easy, no muss, no fuss.
Click to expand...
Click to collapse
First off, my phone was an insurance replacement, not a **** up "oops I accidentally updated"
But I have to ask you, when you decided to answer originally, did you actual contemplate the question? Or did you assume that it was the same that had been asked before? I assure you that if you had thought about it, you would have considered the plausibility of an answer other than no. (yes and maybe being the alternatives). The post didn't ask you how to do it. And also, EXACTLY what would the OP search for to find an answer. KitKat was still in Soak Test at the time of the OP, but the all knowing non developers seemed to have the answer (this seems unacceptable). I think if the question had been pondered by the respondents they would have realized the question had not been asked before.
1. Historically, new root an boot loader exploits have been found AFTER an update has been released.
2. Historically there has not been a phone that jumped an entire cycle of updates to a new release. And that is hundreds of phones over many OSs over many iterations.
3. The idea that it was plausible should have been at the forefront of peoples minds, because the boot loader was required to be changed. There have been many posts about the nature of root being changed in kitkat. So the jump would absolutely open up risk to exploit.
4. Google wants devices to be open. Did no one think it was plausible that the exploit would be reintroduced after the hand off to Lenovo?
So I ask again, the present situation not withstanding, do you honestly think that anyone answered my question? A bunch of people tired of reading a similar question, giving the answer to a different question. As a member and contributor to the xda community for quite a while now, I've learned that it's important to actually answer the question that's actually asked and not assume the OP is not fully aware of the question they are asking. Especially if the qualify the question in the first place to differentiate it from the question he knows responders are going to assume the OP is asking. Cheers.
P.S. The idea that any of you were actually being "helpful" is cockypop.
brownrt said:
P.S. The idea that any of you were actually being "helpful" is cockypop.
Click to expand...
Click to collapse
I apologize if it came off gruff, but we have been helpful before, it just gets aggravating when it appears as if someone didn't do their due diligence in doing actual research, especially if when we've answered the same question numerous times.
In the future, I'll work at being more helpful and if it's the same question that I've already answered, maybe instead of going off, I can just wait for someone else to answer, especially if I've already typed the same answer numerous times to other people.
In any case, whether you think it's poppycock or not, we are genuinely happy for everyone that has now had a second chance at unlocking the bootloader with this "mistake" from Motorola. I just hope everyone takes advantage of it.
^^^I won't apologize for appearing "gruff."
brownrt said:
See how asinine you were now?
Click to expand...
Click to collapse
I don't feel asinine, in the least bit. What happened was pure, dumb luck (or someone at Moto "accidentally" putting the TZ back into the KK update). You all also got lucky when someone decided to try out Motopocalypse just for the hell of it. At the time, there was no "path" to the unlock and every experienced dev (I'm no dev) was under the notion this would never happen. Thanks for bringing this up, I always enjoy a good discussion. I was wrong, the devs were wrong, the experts were wrong.
ill just leave this here
im not getting involved in this bickering, ill just say this:
-it took Dan (a security expert by trade) a long time to find the BL unlock. so when he says "it will never happen again", i tend to belive him. therefore "the never going to happen" post by others.
-i highly doubt moto forgot on purpose to apply the known exploit patches, or let us have it back on purpose, so someone over there is probably fired right about now.
-had geohot not found a blanket root, something that is quite rare, there still would be no root as no one is actively trying.
so, however it may have not been worded in the best manner, the assumptions at the time of the op were accurate.
that will be all, as you were....
Hello all,
There was asimilar thread to this (which was short lived because it turned into nothing but a few little d-bags fighting like little girls) in the M8 non-specific carrier forum for conversation and information regarding potential other projects in progress for rooting the VZW M8 that is running 4.4.4 considering there is absolutely no options as of now... I for one have already decided to leave Verizon for this very reason, and if t_mobile is floating the bill for early termination...awesome! However I'm still stuck with the phone,which i love,but have never had a phone i couldn't root after one day of googling. So i want to know if anyone else is privvy to any info that I am not, it looks as though susunshine will be at least another 3 months. It seems there is easy too many geniuses out there to have jcase being the only one that has enough knowledge to do this, don't get me wrong, he is brilliant and very generous with his work but crap! This is aa pretty popular phone and lots of folks using VZW even though they suck for this kind thing, some have no choice and go to who offers the best reception in there area. Please post your thoughts.....
P.s. - as mentioned iam going to be having this VZW branded M8 AND I HAD heard there was a law passed stating that the carriers had to unlock the phones if the customer requested?? Anyone know about this, if so what do ineed to do?
As far as I know there is no progress on unlocking/s-off'ing 4.4.4 except for sunshine. It currently only works on 4.4.3 and below but it has been alluded to that future updates may support 4.4.4. You'll just have to wait and see.
Regarding the unlocking law, that's a different kind of "unlock". You're asking about unlocking your bootloader to allow you access to deeper levels of the phone's memory. That law was about being able to "carrier unlock" a phone to take it to another carrier which uses he same or overlapping frequencies.
It's unfortunate, but as far I can tell no new root method is working, and it might be a while until one is, as basically all other methods have been completely "fixed".
No one would be willing to burn an exploit right now knowing l is so close. Doing so right now would allow them to patch before l drops. We don't want or need that.
dottat said:
No one would be willing to burn an exploit right now knowing l is so close. Doing so right now would allow them to patch before l drops. We don't want or need that.
Click to expand...
Click to collapse
That completely makes sense, with L coming so soon they would be wasting their time and effort, as they may have one now but they do not want to release it because it would more than likely still work on L when its out and it would probably be a good while before an update after L so by waiting they are just being using good business sense.
But then again another dev or team could beat them to a crack, that is the good thing about a free society there is competition and no one owns the market at least not for long. I say bring on the competition lol.
M9guy said:
That completely makes sense, with L coming so soon they would be wasting their time and effort, as they may have one now but they do not want to release it because it would more than likely still work on L when its out and it would probably be a good while before an update after L so by waiting they are just being using good business sense.
But then again another dev or team could beat them to a crack, that is the good thing about a free society there is competition and no one owns the market at least not for long. I say bring on the competition lol.
Click to expand...
Click to collapse
Competition could lead to everyone who gets this phone with L being locked out if that's the case.
dottat said:
Competition could lead to everyone who gets this phone with L being locked out if that's the case.
Click to expand...
Click to collapse
I really doubt that because there are a lot of devs out there that all they want is the recognition for being the one to crack it and are not looking for financial gain.
M9guy said:
I really doubt that because there are a lot of devs out there that all they want is the recognition for being the one to crack it and are not looking for financial gain.
Click to expand...
Click to collapse
Once an exploit is burned its burned. If it is burned before L and it gets patched in L it means L gets delayed and everyone else gets locked out. It's a matter of the few versus the many. The fact they are NOT burning the exploit now because of this should tell you it's not about $.
dottat said:
Once an exploit is burned its burned. If it is burned before L and it gets patched in L it means L gets delayed and everyone else gets locked out. It's a matter of the few versus the many. The fact they are NOT burning the exploit now because of this should tell you it's not about $.
Click to expand...
Click to collapse
That does NOT mean it has nothing to do with $ because it would not be smart to release it now because there would be no gain giving away the crack then they would not make much $ because yes L would most likely patch it. The most financial gain would be to wait till after L because the next update would be a lot farther away, giving more time to collect.
M9guy said:
That does NOT mean it has nothing to do with $ because it would not be smart to release it now because there would be no gain giving away the crack then they would not make much $ because yes L would most likely patch it. The most financial gain would be to wait till after L because the next update would be a lot farther away, giving more time to collect.
Click to expand...
Click to collapse
Couple weeks of use versus couple months of use.
dottat said:
Couple weeks of use versus couple months of use.
This thread is no longer serving a purpose. You are upset after being locked out which I understand. Unless you come up with a method and exploit of your own I would suggest you cease this conversation as there won't be a happy ending.
Click to expand...
Click to collapse
I"am already unlocked I only responded to the posts already made, and I did not make this thread. No Iam not upset at all you stated your opinion and I did mine and we dont need to agree. I"am more than happy to cease the conversation that you started. I was only replying to the comments you posted replying to mine. I think we can both agree and both agree to disagree, after all we dont have to agree.
Thank you for your opinion and have a good day.
M9guy said:
I"am already unlocked I only responded to the posts already made, and I did not make this thread. No Iam not upset at all you stated your opinion and I did mine and we dont need to agree. I"am more than happy to cease the conversation that you started. I was only replying to the comments you posted replying to mine. I think we can both agree and both agree to disagree, after all we dont have to agree.
Thank you for your opinion and have a good day.
Click to expand...
Click to collapse
Agreed. Hopefully the wait for L isn't that long...and the issue becomes moot.
dottat said:
Agreed. Hopefully the wait for L isn't that long...and the issue becomes moot.
Click to expand...
Click to collapse
Sorry I apologize I forgot I did first reply to your post my bad. I respect everyone opinion and I"am not looking to get in to anything with anyone I think two people can have a difference of opinion and debate it without it being anything more.
M9guy said:
Sorry I apologize I forgot I did first reply to your post my bad. I respect everyone opinion and I"am not looking to get in to anything with anyone I think two people can have a difference of opinion and debate it without it being anything more.
Click to expand...
Click to collapse
I appreciate that. Nothing personal here either man.
M9guy said:
Sorry I apologize I forgot I did first reply to your post my bad. I respect everyone opinion and I"am not looking to get in to anything with anyone I think two people can have a difference of opinion and debate it without it being anything more.
Click to expand...
Click to collapse
Oh and for the record actually I have used your fixes on here quite a few times so I appreciate the things you put on here. I can respect someone and still debate with them and have a difference of opinion and as you can see if I make a mistake in something I do my best to correct it.
heck yes
There can always be a fruitful discussion without people agreeing, that is the way our forefathers did it, and as far as I know, they didn't kill one another, good thread.
Cheers
Except for that little incident 1861 - 1865.......
Deleted...
Leaving Verizon.
Sharpie603 said:
Recently Verizon has shown their true colors. They do NOT want to give us control of a device that we bought and paid for. (That's like buying a radio that only plays Country).
In my eyes. If we pay you monthly then why do you care what we do with our device? We own it right?
However, after days of researching and very knowledgeable co-workers..... The solution is here.
ODIN 3.10. That's Correct. ODIN 3.10 has the ability to look past the locked bootloader and grant access to roll back. This was not made to be public but (Thank GOD) was leaked on Aug 26th.
You can download ODIN 3.10 here: http://www.theandroidsoul.com/download/download-odin-3-10-6/
I have not yet tried to root after rolling back to the BOA8 Kernel. Anyone want to test this out and let me know if you were able to root after downgrading?
Click to expand...
Click to collapse
So you were able to downgrade from OG5 to OA8, just by using the 3.10 version of ODIN? Has anybody else tried this yet?
scadilla said:
So you were able to downgrade from OG5 to OA8, just by using the 3.10 version of ODIN? Has anybody else tried this yet?
Click to expand...
Click to collapse
Just the Kernel, not the firmware. Which in reality.... Serves no purpose.... The bootloader still remains locked and prevents from downgrading the firmware. However, this method works for downgrading kernels...
I'm still looking into ways to obtain root with a downgraded kernel. Not saying it's possible, but I'm not giving up just yet.
Sharpie603 said:
Just the Kernel, not the firmware. Which in reality.... Serves no purpose.... The bootloader still remains locked and prevents from downgrading the firmware. However, this method works for downgrading kernels...
I'm still looking into ways to obtain root with a downgraded kernel. Not saying it's possible, but I'm not giving up just yet.
Click to expand...
Click to collapse
I'm definitely following this thread!!! Thanks for the info Sharpie603!!! Man... I really hope you're successful!!! I'm ROOTing for you! (Pun intended! Damn I'm funny! No?!?! Anyone???) LOL
Sharpie603 said:
Just the Kernel, not the firmware. Which in reality.... Serves no purpose.... The bootloader still remains locked and prevents from downgrading the firmware. However, this method works for downgrading kernels...
I'm still looking into ways to obtain root with a downgraded kernel. Not saying it's possible, but I'm not giving up just yet.
Click to expand...
Click to collapse
Ah, OK, that makes sense so the thinking is if you are on OG5 with the locked bootloader that you could downgrade the kernel and then root. I'll be following closely as well.
scadilla said:
Ah, OK, that makes sense so the thinking is if you are on OG5 with the locked bootloader that you could downgrade the kernel and then root. I'll be following closely as well.
Click to expand...
Click to collapse
Not looking very promising.
Can you downgrade APNHLOS?
Terribly misleading title. OE1 and OG5 didn't do anything about locking the kernel, they were bootloader locks. As you said, unless you can downgrade which you can't. The only way this would be useful is if we could get root by only downgrading the kernel, which we cannot. We could access safestrap if we HAD root access, because we could flash the NI2 kernel to get access, but no root = no safestrap.
I don't think you made a discovery, I think you just came across what wasn't stated bluntly, simply because it wasn't necessary information to tell people. As for your quest to find a way to root.... I'm just going to say, have fun.
In regards to the OP's statement - Verizon could care less about the rooting community and allowing you to do what you want with your "owned" devices. Verizon and AT&T locked the phones down tight as they should because this is a portable personal computer with all your financial information being transferred back and forth. Tightening the security of the phone against hackers trying to steal all your information and identity had the unfortunate side effect of making root near impossible currently. The device performs exactly as advertised on the box and in the specifications. Your analogy of a radio stuck on country is a poor one. Think more like you bought a car and it will not go 200 miles an hour. There is nothing preventing you from purchasing a car that can, or replacing the engine to do so which would have other downfalls such as gas mileage going to crap. In the same analogy you can purchase a T-Mobile motherboard, swap it out, be able to root, but not get certain LTE bands. Verizon has not targeted you at all...you can blame the hackers constantly trying to get information off the phones. Verizon and AT&T took steps to try to prevent that and of course increase profits by being rated the most secure phones out there. Verizon never gave you the keys to root...ever! So they are not keeping this info from you. Just like every device that took a little time to find root, it is up to you and the developers to find away around it.
This is the same as saying Acme safe company is trying to keep you from being rich because they made their safes more secure.
Spartan117H3 said:
Terribly misleading title. OE1 and OG5 didn't do anything about locking the kernel, they were bootloader locks. As you said, unless you can downgrade which you can't. The only way this would be useful is if we could get root by only downgrading the kernel, which we cannot. We could access safestrap if we HAD root access, because we could flash the NI2 kernel to get access, but no root = no safestrap.
I don't think you made a discovery, I think you just came across what wasn't stated bluntly, simply because it wasn't necessary information to tell people. As for your quest to find a way to root.... I'm just going to say, have fun.
Click to expand...
Click to collapse
The title is not misleading at all. It does exactly what I described. Gives you the ability to downgrade the Kernel. and the Kernel only. I clearly mentioned this in post #3 that this still leaves the bootloader locked. then in later posts went on to mention that it looks like we are still SOL. Take it how you want, sorry for actively trying to find a solution...
KennyG123 said:
In regards to the OP's statement - Verizon could care less about the rooting community and allowing you to do what you want with your "owned" devices. Verizon and AT&T locked the phones down tight as they should because this is a portable personal computer with all your financial information being transferred back and forth. Tightening the security of the phone against hackers trying to steal all your information and identity had the unfortunate side effect of making root near impossible currently. The device performs exactly as advertised on the box and in the specifications. Your analogy of a radio stuck on country is a poor one. Think more like you bought a car and it will not go 200 miles an hour. There is nothing preventing you from purchasing a car that can, or replacing the engine to do so which would have other downfalls such as gas mileage going to crap. In the same analogy you can purchase a T-Mobile motherboard, swap it out, be able to root, but not get certain LTE bands. Verizon has not targeted you at all...you can blame the hackers constantly trying to get information off the phones. Verizon and AT&T took steps to try to prevent that and of course increase profits by being rated the most secure phones out there. Verizon never gave you the keys to root...ever! So they are not keeping this info from you. Just like every device that took a little time to find root, it is up to you and the developers to find away around it.
This is the same as saying Acme safe company is trying to keep you from being rich because they made their safes more secure.
Click to expand...
Click to collapse
I'm not worried about my phone being hacked. I have nothing to hide. I do not bank online or make purchases online. If there is fraudulent activity on my bank account, my credit union will inform me. This is besides the fact. I could care less if I made a "bad" analogy. I'm not sitting here thinking "Hmmm I wonder if anyone will have a problem with this statement" when writing up a comment. Your paragraph is nothing but slander "Something XDA strongly discourages". A simple "I don't think this will work, and here's why" would of been suffice.
On a side note. I'm leaving Verizon so you won't have to worry about me trying to find root and help you guys out anymore.
Sharpie603 said:
The title is not misleading at all. It does exactly what I described. Gives you the ability to downgrade the Kernel. and the Kernel only. I clearly mentioned this in post #3 that this still leaves the bootloader locked. then in later posts went on to mention that it looks like we are still SOL. Take it how you want, sorry for actively trying to find a solution...
Click to expand...
Click to collapse
It is misleading because you mark it as solved as if it was a puzzle that nobody else can figured out, like you had new information to provide. If I'm not mistaken, the kernel was never locked, and you can use any Odin to push a different kernel. It was never a question if the kernel was locked. So you didn't do anything except state what was redundant. The people who confirm that the bootloader is locked say so because it means you can't downgrade. They didn't say you can still downgrade the kernel because it's absolutely meaningless. That's like saying, the bootloader is locked, but you can still Odin and flash any file you want even if it doesn't work.
There are countless people like you in other threads who claim they're trying to find a way to root. Neither you nor I are smart enough to come up with an exploit, as I have detailed countless times before. So why don't we leave that up to the developers?
Sharpie603 said:
I'm not worried about my phone being hacked. I have nothing to hide. I do not bank online or make purchases online. If there is fraudulent activity on my bank account, my credit union will inform me. This is besides the fact. I could care less if I made a "bad" analogy. I'm not sitting here thinking "Hmmm I wonder if anyone will have a problem with this statement" when writing up a comment. Your paragraph is nothing but slander "Something XDA strongly discourages". A simple "I don't think this will work, and here's why" would of been suffice.
On a side note. I'm leaving Verizon so you won't have to worry about me trying to find root and help you guys out anymore.
Click to expand...
Click to collapse
It doesn't matter if you don't care yourself, because you are not everyone. You are a single person. If you were everyone, obviously Verizon wouldn't make money off you, and wouldn't secure their phones. But this is flawed reasoning yet again.
A bad analogy shows you have flawed reasoning. It doesn't matter if you care or not, you don't have a problem with stating things that don't make sense, then by all means, continue (which I don't even have to say, because you do indeed continue).
Slander? Are you serious? You acknowledge the reason for his post, which claims you have a bad analogy, and explains why Verizon does what it does. Then you make an insane, baseless claim that says xda discourages root. Yet XDA was where the original root method was released in detail, with the newsworthy 18k bouty.
Why does he need to explain why it wouldn't work, when you yourself have already done that? It's the same when you responded to me. You answer your own question but then argue against people when they confirm with your latter findings that it doesn't work?
I don't understand why people like you are so happy to see 1 posters support you, but then immediately get hostile when anyone with any knowledge comes in to speak. You running from Verizon doesn't solve any problems and shows you weren't invested to begin with, which is fine, since you wouldn't have accomplished anything anyway. Unless you're claiming to be smarter than those who found the original root.
You want to know why it won't work? All these people have similar ideas to yours, they either want root, or want to "try" with little to no knowledge at all about what they are doing.
http://forum.xda-developers.com/showpost.php?p=62378933&postcount=19
http://forum.xda-developers.com/showpost.php?p=62380538&postcount=23
http://forum.xda-developers.com/verizon-galaxy-s5/help/vz-replacement-s5-oe1-t3190365
http://forum.xda-developers.com/ver...g5-verizon-t3192598/post62746265#post62746265
Spartan117H3 said:
It is misleading because you mark it as solved as if it was a puzzle that nobody else can figured out, like you had new information to provide. If I'm not mistaken, the kernel was never locked, and you can use any Odin to push a different kernel. It was never a question if the kernel was locked. So you didn't do anything except state what was redundant. The people who confirm that the bootloader is locked say so because it means you can't downgrade. They didn't say you can still downgrade the kernel because it's absolutely meaningless. That's like saying, the bootloader is locked, but you can still Odin and flash any file you want even if it doesn't work.
There are countless people like you in other threads who claim they're trying to find a way to root. Neither you nor I are smart enough to come up with an exploit, as I have detailed countless times before. So why don't we leave that up to the developers?
It doesn't matter if you don't care yourself, because you are not everyone. You are a single person. If you were everyone, obviously Verizon wouldn't make money off you, and wouldn't secure their phones. But this is flawed reasoning yet again.
A bad analogy shows you have flawed reasoning. It doesn't matter if you care or not, you don't have a problem with stating things that don't make sense, then by all means, continue (which I don't even have to say, because you do indeed continue).
Slander? Are you serious? You acknowledge the reason for his post, which claims you have a bad analogy, and explains why Verizon does what it does. Then you make an insane, baseless claim that says xda discourages root. Yet XDA was where the original root method was released in detail, with the newsworthy 18k bouty.
Why does he need to explain why it wouldn't work, when you yourself have already done that? It's the same when you responded to me. You answer your own question but then argue against people when they confirm with your latter findings that it doesn't work?
I don't understand why people like you are so happy to see 1 posters support you, but then immediately get hostile when anyone with any knowledge comes in to speak. You running from Verizon doesn't solve any problems and shows you weren't invested to begin with, which is fine, since you wouldn't have accomplished anything anyway. Unless you're claiming to be smarter than those who found the original root.
You want to know why it won't work? All these people have similar ideas to yours, they either want root, or want to "try" with little to no knowledge at all about what they are doing.
http://forum.xda-developers.com/showpost.php?p=62378933&postcount=19
http://forum.xda-developers.com/showpost.php?p=62380538&postcount=23
http://forum.xda-developers.com/verizon-galaxy-s5/help/vz-replacement-s5-oe1-t3190365
http://forum.xda-developers.com/ver...g5-verizon-t3192598/post62746265#post62746265
Click to expand...
Click to collapse
Listen I came here thinking I found a way. In no way was trying to start a war among like minded individuals. All you are doing is trying to ream me out for what? For a mistake I made, thinking I had a solution? Way to be professional. Sorry for cluttering the forum. Sorry for everything I have done thus far. Sorry for bothering you sir. Sorry for not being as knowledgeable as you are. I'm sorry for everything! F*ck
Sharpie603 said:
Listen I came here thinking I found a way. In no way was trying to start a war among like minded individuals. All you are doing is trying to ream me out for what? For a mistake I made, thinking I had a solution? Way to be professional. Sorry for cluttering the forum. Sorry for everything I have done thus far. Sorry for bothering you sir. Sorry for not being as knowledgeable as you are. I'm sorry for everything! F*ck
Click to expand...
Click to collapse
The problem is, you just assume things without actually comprehending what people say. That's why you believe this is apparently a war. Ream you out? You miss the entire point, repeatedly. All it is is people telling you why your statements don't make any sense.
Sharpie603 said:
I'm not worried about my phone being hacked. I have nothing to hide. I do not bank online or make purchases online. If there is fraudulent activity on my bank account, my credit union will inform me. This is besides the fact. I could care less if I made a "bad" analogy. I'm not sitting here thinking "Hmmm I wonder if anyone will have a problem with this statement" when writing up a comment. Your paragraph is nothing but slander "Something XDA strongly discourages". A simple "I don't think this will work, and here's why" would of been suffice.
On a side note. I'm leaving Verizon so you won't have to worry about me trying to find root and help you guys out anymore.
Click to expand...
Click to collapse
As stated that is just YOU. 99.9% of people do not want their phone hacked or their identity stolen.
How is stating the facts slander? And I think I would know best what is encouraged here and what isn't. Now you are just lashing out for no reason and making no sense.
I guess we can close this as you wished. Thanks for trying.
where is groot?
ahem.
so in advance, I'd like to say that there is no root yet before people start asking.
still won't stop them but hey, I tried.
apparently the exynos variant was rooted. which confirms the below statement.(was to be expected. nothing new here) read all about here:
https://forum.xda-developers.com/galaxy-note-10+/how-to/guide-how-to-root-note-10-t3960031
Also if there is root, then it's going to be for international models such as(model numbers are not confirmed yet)root confirmed and models aswell:
n970 n971 n975 n976 f/ds/b -exynos
n970 n971 n975 n976 n -exynos
n9700 n9710 n9750 n9760 /ds -snapdragon (international)
*North American snapdragon models will not have root before a very long time...if ever: (regardless of carriers, its all the same hardware/limitations)(*unless they decide to source some of devices from the internation family of SD devices like Sprint had from the s10 5g or even Exynos devices like it is rumored.)
n970 n971 n975 n976 u -snapdragon
n970 n971 n975 n976 u1 -snapdragon
n970 n971 n975 n976 w -snapdragon
North American Snapdragon devices might never have a functional stock root exploit at all. (thus being described as the wrong phone for your rooting needs)
so again please dont ask about rooting( looking at you north Americans .... )
so do yourselves and the rest of the xda community a favor and DONT BUY THE WRONG PHONE. Do your homework in advance and get the appropriate model.
one might ask: "what's the wrong phone?"
the answer would be: its the one that isint going to be rootable for a very long time...(if ever).
so if you buy the wrong phone and wonder why no root then i dont know what to say anymore...apart from "you bought the wrong phone!"
for years and years now North American snapdragon devices have locked bootloaders that render them crippled when it comes to rooting.... that's if they ever get root. So this is ongoing and just because the note 10 is a new device, this dosen't change the fact that NA SD's bootloader are locked and are NOT unlockable.
Please also for the love of god read up about a device that is carrier unlocked. this means what it means. its not tied to be used on a single carrier. In now way or sense does this mean the bootloader is unlockable.
now for the pipe dreams:
down the line( can be months and months or even a year or never), NA snapdragon devices just might have an exploit workout for a bit. What this susualy means is that they either have a partial root or a full working root. Usually when a full root method is made available, you have to stay on a specific bootloader revision and never update the device again...or till the exploit is updated to match new firmware revision. this is often a cat and mouse situation and new security patches are likely to patch rhe exploit.so yeah.. talk about crippling a device.
so i wouldn't keep my hopes up if you plan in going all in on a N. american device and pray the android gods for root as it might never happen!( look at the note 9, there is a proof of concept/WIP but never has the stock note 9 firmware been rooted On NA devices yet ( we are about 1 month shy of a full year with absolutely 0 root) )
so again please dont come asking how to root your north american device when you start seeing the international version threads popping up about root guides, recoveries and roms.
Lol...i like it. Preemptive strike.
But yes the ignorant will ask anyway just like every single time a new device launches but now we can refer them to this thread :good:
force70 said:
Lol...i like it. Preemptive strike.
But yes the ignorant will ask anyway just like every single time a new device launches but now we can refer them to this thread :good:
Click to expand...
Click to collapse
What's dissapointing is that ignorance dosent choose the individual nor the time of said affliction.
It's a man made convergance towards slouch and spoon feeding. but it IS a choice. A subconscious one or not, that we may not know but a reason to not dare venture and search for the truth is a guilt I do not share but sure hope more and more feel. Sometimes, new comers might find our words and ways harsh but harsh it what it is when asking other people to do the work for you.
annnnnnyways that said, we can expect the same questions for years to come.
Will T-Mobile version get root?..... I'll be the first hope this hurts
mlock420 said:
Will T-Mobile version get root?..... I'll be the first hope this hurts
Click to expand...
Click to collapse
please inform yourself on the devices that North American carriers resell. then your question will answer it self.
( simple retorical question can also lead to an answer....ie:
is my carrier a north American carrier?
once you have the answer go re read OP)
bober10113 said:
please inform yourself on the devices that North American carriers resell. then your question will answer it self.
( simple retorical question can also lead to an answer....ie:
is my carrier a north American carrier?
once you have the answer go re read OP)
Click to expand...
Click to collapse
Just jokes let's all breathe for a second lol
mlock420 said:
Just jokes let's all breathe for a second lol
Click to expand...
Click to collapse
the problem is this isint a joke. people will actualy come and ask this very question.
they are the very same who complain why the forums arent split into carrier sections instead of SoC.
Always love the "I couldn't be bothered to actually search or try to read the thread/OP/or even a few pages back so can you answer my question" responses. Some of the people on here have come up with marvelous (and entertaining) responses to them.
RedsonRising said:
Always love the "I couldn't be bothered to actually search or try to read the thread/OP/or even a few pages back so can you answer my question" responses. Some of the people on here have come up with marvelous (and entertaining) responses to them.
Click to expand...
Click to collapse
and now we have the ammunition to confront them without the need to repeat ourselves endlessly.(well the url link to OP might get repeated alot down the line but efforts in writing words to them non readers wont...lol)
so i hope my OP can be referred to for years to come.
Yeah and also don't come here asking where the led notification has gone.
Sent from my SM-G975U using Tapatalk
Limeybastard said:
Yeah and also don't come here asking where the led notification has gone.
Click to expand...
Click to collapse
where did it go?!
bober10113 said:
where did it go?!
Click to expand...
Click to collapse
It defected to North Korea.
Sent from my SM-G975U using Tapatalk
first time i have heard about the root on mobile
morphlinqq said:
first time i have heard about the root on mobile
Click to expand...
Click to collapse
i usually use/install root on android.
bober10113 said:
i usually use/install root on android.
Click to expand...
Click to collapse
Did you try on another system?
morphlinqq said:
Did you try on another system?
Click to expand...
Click to collapse
i tried windows and i right clicked.
i tried linux once and sudo"ed.
Not to mention, the Note 10 seems to be coming on a whole different SoC altogether. So the methods are still going to be different regardless I imagine. If we could just repurpose some of that BA malware always going around into a new superuser app with better intentions, maybe we could do something.
Well at least I know to return it now. That was simple enough.
What sucks is North America has an unlocked version of the phone. I have that version, and it still can't be rooted. I think locked bootloader should be only on US carrier models since those are the companies wanting to lock it to prevent dummies from bricking their ****. Mine however is the unlocked n975u1.
I'm waiting to see tho. There's a website giving instructions to root the US model via flashing rooted fw in Odin. So I await to see how many people brick their phones.
Herox said:
What sucks is North America has an unlocked version of the phone. I have that version, and it still can't be rooted. I think locked bootloader should be only on US carrier models since those are the companies wanting to lock it to prevent dummies from bricking their ****. Mine however is the unlocked n975u1.
I'm waiting to see tho. There's a website giving instructions to root the US model via flashing rooted fw in Odin. So I await to see how many people brick their phones.
Click to expand...
Click to collapse
u and u1 are identical devices.
dont mix carrier unlocked and bootloader unlockable. the wording is similar but that's where the similarities stop.
please reread OP if you need clarification on any of this.