Related
Hello,
I bought a T-Mobile G1(it was originally donated for testing of a Open-Source project ) for tying to reverse engineer an unlock code calculator.
Since those scam sites did it i may able to it to.
So i am here to asking it if bought some codes ( and it worked of course ) if you can paste it here and the respective IMEI to help me get some relations whit it.
If you that someone did a calculator before ( and is Open-Source of course please tell me ). Also another ways of passing the unlock will be welcome.
I will keep you informed of my study.
Regards,
Alfredo Palhares
i had a code about a year ago, cant find it, but u can get one by calling tmobile if u have a g1 or mt3g for 3 or more months
IMEI: removed
Unlock Code: removed
Moderator edit: you should not be posting this information publicly, for your own protection I have removed it - Chainfire
If you want to share your code and imei with him, I suggest doing so in private. This is personal information that should not be shared in public.
Also be certain that you TRUST him with this information.
Unlock codes bought online come from HTC's database. There is no algorithm, as they are randomly generated and assigned. So these efforts will not get you anywhere, I'm afraid.
And don't post IMEIs in public - someone can easily block your phone with it, certainly in the UK...
a question comes to mind, how were the old htc unlockers created e.g. for the hermes and the kaiser? they must have used algorithms otherwise how else would they have been possible? if thats true, could there be an algorithm that cracks the random generation of the unlock codes for the HTC android phones?
warsng said:
a question comes to mind, how were the old htc unlockers created e.g. for the hermes and the kaiser? they must have used algorithms otherwise how else would they have been possible? if thats true, could there be an algorithm that cracks the random generation of the unlock codes for the HTC android phones?
Click to expand...
Click to collapse
If you are referring to the free apps that unlocked the phones, as far as I know (so maybe not completely correct) they actually crack the phone to make it think it is not locked, they don't calculate the code.
i was going to post mine. i would have loved to contribute but why not make the info public.. it cannot hurt anything
IMEI's are actually open to abuse. I'm not saying the thread starter isn't trustworthy, but I don't know for sure that he is. If you want to cooperate with the opening poster, that's fine, and it's your risk - private message him the information. In that case, the info isn't public for potential abusers either (who can just Google for these numbers).
Would be nice but not possible
Chainfire said:
If you are referring to the free apps that unlocked the phones, as far as I know (so maybe not completely correct) they actually crack the phone to make it think it is not locked, they don't calculate the code.
Click to expand...
Click to collapse
do you think a similar thing is possible on g1/other htc android phones?
warsng said:
do you think a similar thing is possible on g1/other htc android phones?
Click to expand...
Click to collapse
Probably, but I'm not an expert on this subject, so my opinion doesn't really count
warsng said:
do you think a similar thing is possible on g1/other htc android phones?
Click to expand...
Click to collapse
Everything is in flash.
It is a matter of figuring out WHERE in flash, and being able to read/write to those addresses. The JTAG thread is a good starting point.
It would be just as easy to call HTC and beg.
Otherwise call TMobile and wait patiently for them to get around to call HTC, for HTC to get around to find it and sent it to TMobile, for Tmobile to get around to e-mail you the code.
I just thought it was funny people publishing their codes and the Mods running in to delete them, for their own good.
Mods "To Protect, serve, lecture and admonish"
itsjefflol said:
IMEI: removed
Unlock Code: removed
Moderator edit: you should not be posting this information publicly, for your own protection I have removed it - Chainfire
Click to expand...
Click to collapse
Ahh I didn't realize anyone could do anything with your imei, anyhow that was my old phone's imei and unlock code, the phone's in a million pieces anyway so no harm done I guess
Older phones used an algorithm to calculate an unlock code. The algorithms got cracked and the unlockers appeared.
HTC took a different approach of assigning a random lock code to each phone and retaining a private database of the IMEI/unlock codes which they could tightly control.
So a software solution is unlikely, but as you can get the unlock code through normal channels, it's not really necessary.
28 days
it took 28 days for my unlock code to come through from t-mob, but have an orange sim in it now and i am just plucking up the courage to root and put froyo on.
hello, i need to unlock my kaiser 100 at&t, can yuo help me? imei is 354384015858756
giosixa said:
hello, i need to unlock my kaiser 100 at&t, can yuo help me? imei is 354384015858756
Click to expand...
Click to collapse
Did you not read the rest of the forum lol, posting your IMEI is bad...
especially if you are in the UK... Plus, wrong section -_-
Just buy a code off ebay for about 7 USD, not too hard and you receive it instantly.
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....
I made this thread to try and get the get the flame burning again on this topic. It seems since we've achieved safestrap people don't seem too interested in pursuing an unlocked bootloader. I understand that if i want AOSP i should try trading my phone for one with an unlocked bootloader (knowing that somebody is going to comment saying that). But what does that do for the community? Nothing productive. Speaking theoretically here, how is a bootloader unlock achieved with the bootloader lock key? Is there some way of inputting it to unlock the bootloader? What happens if you have the wrong key? Is there a way to create script a keygen that goes through every possibility of however many digit of a code the bootloader lock key is? Or can it only be done via exploit?
Thank you very much for taking the time to read this. Let the discussion begin.
Travisholt92 said:
I made this thread to try and get the get the flame burning again on this topic. It seems since we've achieved safestrap people don't seem too interested in pursuing an unlocked bootloader. I understand that if i want AOSP i should try trading my phone for one with an unlocked bootloader (knowing that somebody is going to comment saying that). But what does that do for the community? Nothing productive. Speaking theoretically here, how is a bootloader unlock achieved with the bootloader lock key? Is there some way of inputting it to unlock the bootloader? What happens if you have the wrong key? Is there a way to create script a keygen that goes through every possibility of however many digit of a code the bootloader lock key is? Or can it only be done via exploit?
Thank you very much for taking the time to read this. Let the discussion begin.
Click to expand...
Click to collapse
If you took the time to read the numerous discussions on this you'd know the answers. People are dropping the unlocked bootloader since even the S4's hasn't been unlocked (since MDK baseband). Regarding the five key questions, it would take a super computer thousands of years to try every possibility. Wrong one would equal bricked phone. Exploit would be only way, and now that Geohot works for Google, he's out of the picture and I'm sure the other Devs aren't going to bother. SS is fine for now, you can always switch carriers if you care that much.
So the community on this device will never progress. Awesome.
Travisholt92 said:
So the community on this device will never progress. Awesome.
Click to expand...
Click to collapse
That is a real possibility. Now with this lesson learned, look for a carrier or device next time that does not lock the bootloader. HTC locks their bootloader but is good enough to provide us users with a way to unlock it. As mentioned, bootloaders are WAY different than obtaining root and there is a very real chance of killing the device in the trial and error process.
I feel where you are coming from i felt the same way. Switched for an HTC One m8 and besides the fact that the bootloader can be unlocked, it's just a much better phone. Should give it a shot! A GS5 is an equal trade for an m8 on craigslist so it shouldn't be too hard. It does seem the general consensus is that the dev's have given up on even trying to unlock it so i would just accept it and move on unfortunately.
What's legal and illegal when it comes to hacking android (in USA)? I want to unlock the bootloader on my Verizon gs3. Is that illegal?
If you can point me to some definitive or authoritative resources, I would appreciate that. I have been googling this topic for a couple weeks, and as far as I can tell, it's currently legal to unlock your phone for use on another wireless carrier, but it is technically illegal to root or unlock bootloaders (by hacking). But what doesn't fit with that are the bounties I see offered for these activities, so I'm very uncertain either way.
bump
Its legal to do anything to your own device.
You can unlock the bootloader, root the phone, install custom firmwares, or break it to pieces with a hammer as long as it's yours...
Worst case scenario you can always start a new life in Mexico
ishaang said:
Worst case scenario you can always start a new life in Mexico
Click to expand...
Click to collapse
That just made my day.
ishaang said:
Its legal to do anything to your own device.
You can unlock the bootloader, root the phone, install custom firmwares, or break it to pieces with a hammer as long as it's yours...
Worst case scenario you can always start a new life in Mexico
Click to expand...
Click to collapse
Are you allowed to post the info of how to do it?
squebler said:
What's legal and illegal when it comes to hacking android (in USA)? I want to unlock the bootloader on my Verizon gs3. Is that illegal?
If you can point me to some definitive or authoritative resources, I would appreciate that. I have been googling this topic for a couple weeks, and as far as I can tell, it's currently legal to unlock your phone for use on another wireless carrier, but it is technically illegal to root or unlock bootloaders (by hacking). But what doesn't fit with that are the bounties I see offered for these activities, so I'm very uncertain either way.
Click to expand...
Click to collapse
The real issue is with the contract you sign with your carrier. As long as you are in the subsidised portion of your contract (generally 2yrs), the phone technically still belongs to them, not you.
Are they going to look for you to make an issue of it, no. If you need to make a warranty claim though, and they find out it's modified, they have the right to not honor the warranty if they choose (happens occasionally, but not widespread).
I mod my phones all the time, but I do it without any expectation of help from vzw if I break something and can't fix it.
Jmo, hope that helps
squebler said:
What's legal and illegal when it comes to hacking android (in USA)? I want to unlock the bootloader on my Verizon gs3. Is that illegal?
If you can point me to some definitive or authoritative resources, I would appreciate that. I have been googling this topic for a couple weeks, and as far as I can tell, it's currently legal to unlock your phone for use on another wireless carrier, but it is technically illegal to root or unlock bootloaders (by hacking). But what doesn't fit with that are the bounties I see offered for these activities, so I'm very uncertain either way.
Click to expand...
Click to collapse
In my opinion, as long as you have warranty, don't root your phone because it will void the warranty.
Its legal, but can void your warranty with the manufacturer or if you have bought your phone through a carrier they may have a clause in the agreement related to this.
Sony as a manufacturer is cool with you unlocking your bootloader, and they offer the instructions and code on their own website officially, here -http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
So that's an example of it being legal.
Very helpful info, thanks! Now I think I'll switch to Sony instead of Samsung.
No problem, and good idea!
I've been a Sony user for a very long time, and generally their devices have never failed to deliver. On top of that they are very developer friendly and support the open source community a lot. This has been referenced in XDA also, many times. Besides that I do feel the build quality of Sony products is superior, and in phones their hardware specs and stock UI is also pretty decent.
oh it's good:highfive:
ite's legal to do anything on your phones of course (like unlock bootloader),
but if you want to test(hack) on other's phones, make sure you get their permission ^^
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.