Database Info

RC31 question

I am new to the Dream, I just got mine on Friday. I have now got root access. I want to know when the RC31 comes out, if I update via t-mobile will it kill root access, or will I need to hold off until a modded FW comes from JesusFreke.
Thanks
Tim

Yes,if you update via t-mobile,it will remove root. Its best if you wait for a modded FW if you want root.

Thats what I figured. thanks for the info.

otto888 said:
Yes,if you update via t-mobile,it will remove root. Its best if you wait for a modded FW if you want root.
Click to expand...
Click to collapse
While I agree that it would probably be best to not upgrade right away, we don't know anything about RC31 yet. The only thing I think that has been officially announce is that it would contain elements of cupcake. I'm not even sure how official that was either. Let's try not to speculate.

Echoing what's been said above, being that we know NOTHING about the next OTA update, it will likely (at the very least) remove root access from a JF RC30 device. It might even prevent you from backflashing to RC29 to get back to the modified JF RC30. So whatever you do, DON'T let your phone update until the new version is examined and tested by others, or you might find yourself with a permanently locked down G1.

If you're running any JF version of the firmware, you will not receive OTA updates. So, you have nothing to worry about unless you actually flash back to RC29 manually.

Iceucold said:
If you're running any JF version of the firmware, you will not receive OTA updates. So, you have nothing to worry about unless you actually flash back to RC29 manually.
Click to expand...
Click to collapse
Correct, or the update will fail, can't remember which one.

So I guess it would be safe to say....
STAY TUNED!!! Same XDA time, Same XDA channel

Iceucold said:
If you're running any JF version of the firmware, you will not receive OTA updates. So, you have nothing to worry about unless you actually flash back to RC29 manually.
Click to expand...
Click to collapse
I love when modders do that, keeps me from doing something stupid

Iceucold said:
If you're running any JF version of the firmware, you will not receive OTA updates. So, you have nothing to worry about unless you actually flash back to RC29 manually.
Click to expand...
Click to collapse
I am not entirely convinced of this.
I had a chat with a co-worker about this and he said "well no, between the engineering bootloader and the test keys, there is no way the modded rc30 can be OTA'd".
I tossed this at him.
What if tmo decided to setup something like this...
check what you are running.
check what keys you are running.
send an update that does something along the lines of...
if your image is equal to or less than rc30 and your keys are either ota or test then update.
There is nothing that keeps them from pushing a testkey signed rc31 and replacing everything on your phone; including the testkeys back to ota keys.
I imagine that anyone with ADP1 or ADP1.1 will be left alone as it would be a bad move to screw with your developer audience; but I could be wrong. They could go after anyone who doesn't have an official ADP image (non JF kernel)...
I have no idea what they are really planning but it does seem that this could be a "check mate" pivotal move if they wanted to play that card this early in the game.
Of course, it could be as simple as "let's leave everyone where they are and only focus on security moving forward" which is most likely going to be the case....

deprecate said:
There is nothing that keeps them from pushing a testkey signed rc31 and replacing everything on your phone; including the testkeys back to ota keys.
Click to expand...
Click to collapse
The running theory is that T-Mo will not do this because all devices with the standard ota-keys installed will also get the "targeted" test-key rc31, reboot, and then freak out because the update is signed with a mismatched key.
The way the update service works is the device periodically sends its Android build fingerprint to Google servers. If the fingerprint is of a supported device (in this case Dream) and the build number is lower than the most recent, then the server may push an update back to the device. Since JF modified builds report an official fingerprint, there is no way for the server to distinguish between a modified and unmodified RC30.
However, i've seen enough in information technology to know that very little is truly "impossible". Based on what is currently known though, it is highly unlikely that Google/T-Mo/HTC could forcibly reroot a modified RC30 G1 at this time.

I really don't see T-mobile doing this. Why would they? At this point people with root don't have any real advantage over normal phones other than techie stuff. We are not pirating software or getting free minutes. Unless it becomes an issue I think T-mobile will leave us alone.

speoples20 said:
I really don't see T-mobile doing this. Why would they? At this point people with root don't have any real advantage over normal phones other than techie stuff. We are not pirating software or getting free minutes. Unless it becomes an issue I think T-mobile will leave us alone.
Click to expand...
Click to collapse
There is no piracy because apps are free. Once support for paid apps arrives, piracy will start. (Someone in this forum started a thread wondering how to do that). It happens in all software platforms, and it's going to happen with Android also. Note that I don't endorse piracy (for some weird reason people think that developers are the only guys who should work for free), less in these environments where there are lots of applications than are made by individuals, not big companies, but this won't prevent piracy to come to Android.
Anyway, if I were TMob I would try to remove root from as many devices as I can (which obviusly does NOT include ADP1, as it has nothing to do with TMob),
not just for the piracy, but to keep users from breaking their devices due to doing stupid thing with a rooted phone.

T-Mobile motivation to wipe devices using test keys
T-Mobile could have a motivation to wipe devices by providing an update using test keys. Tethering is against the terms of service and can only be done if you have root. They could take the *IAA approach and say that any one who has root wants to be able to tether and break their TOS (since tethering is the biggest advantage to root right now). If enough people tethered it could cause a problem as they may not have the bandwidth to accommodate what people want to do when tethered. BTW, for all who tether use this addon for firefox and change your user string to match the android's browser (https://addons.mozilla.org/en-US/firefox/addon/59) so they can not tell.
Is there a way to make new keys that are different from the dev keys, or is google the only ones who can do that?

Doing an update using test-keys sounds a bit desperate to me.
Moreover, as jashsu said, it seems that there is no way that currently TMob could know if you were using a G1 with an stock R30 or JF's one, so if they offered the update with testing keys, stock R30 phones would reject it.
They could try some tricks as offering the update with test keys for a while, then switch to another with official keys, then came back to test keys, etc...
But as I said, this sounds desperate and sloppy.
Mi bet is that they would try to fix the downgrade issue, and will use the official keys, so anyone with JF will be safe.
Anyway (I have an ADP1, so I've not receive any update from now), I though that, when an update was available, the user was asked whether to update or not.

clarke.hackworth said:
If enough people tethered it could cause a problem as they may not have the bandwidth to accommodate what people want to do when tethered.
Click to expand...
Click to collapse
This is not a problem. They will simply throttle you down to EDGE if they consider you are using up too much bandwidth (tethering or otherwise).
Is there a way to make new keys that are different from the dev keys, or is google the only ones who can do that?
Click to expand...
Click to collapse
Anyone can create signing keys. Not sure what you're getting at though.

clarke.hackworth said:
Tethering is against the terms of service and can only be done if you have root.
Click to expand...
Click to collapse
It is? Where? Last I remember I saw the CEO say it wasn't and it is allowed. And that they wouldn't stop it or prevent it in anyway.

deprecate said:
I tossed this at him.
What if tmo decided to setup something like this...
check what you are running.
check what keys you are running.
send an update that does something along the lines of...
if your image is equal to or less than rc30 and your keys are either ota or test then update.
There is nothing that keeps them from pushing a testkey signed rc31 and replacing everything on your phone; including the testkeys back to ota keys.
Click to expand...
Click to collapse
It still wouldn't apply the update, even if they sent out an OTA signed with test keys. The OTAs are verified against the certificate present in /system/etc/security/otacerts.zip.
Since that file has been deleted, it wouldn't be able to verify the OTA, no matter how it was signed.

JesusFreke said:
It still wouldn't apply the update, even if they sent out an OTA signed with test keys. The OTAs are verified against the certificate present in /system/etc/security/otacerts.zip.
Since that file has been deleted, it wouldn't be able to verify the OTA, no matter how it was signed.
Click to expand...
Click to collapse
Good point. That completely escaped me. But wouldn't it be entertaining to see an official rc31 sent out with your certs as the target

deprecate said:
Good point. That completely escaped me. But wouldn't it be entertaining to see an official rc31 sent out with your certs as the target
Click to expand...
Click to collapse
Very entertaining

Adding rooted features without rooting.

Side loading
Apparently there is an update that has to be pushed to your phone from AT&T, but hardly anyone has received it yet. People in this thread are working on adding this feature without the update. This method will allow you to install non android market apps, but so far it disables your mms capability.
http://forum.xda-developers.com/showthread.php?t=1111278
Free tethering/wifi hotspot
http://forum.xda-developers.com/showthread.php?t=980591
By changing a few settings, you can have tethering/use wifi hotspot without adding a tethering plan from AT&T.
Maybe we could add future developments to this thread as they become available. I like the idea of leaving my phone stock so that it will automatically update.

Are you talking about the "silent" OTA that enables side-loading?
If so, and if by hardly anyone, you mean "hardly anyone here on XDA," it may be because they are rooted or otherwise running a custom ROM that will prevent them from getting OTA updates.
If you mean hardly anyone here on XDA that is bone stock, well, that might be true. And it also might be true that the recently discovered method of enabling sideloading will help some people, who don't mind their mms broken until some workaround fixes it.
Or they can root, and be done with it. There's nothing that will ever be OTA that I would want to get OTA anyway -- it will be available here shortly after.
The only excuse people have to not root is that it *appears* to be difficult. It really isn't. You can enjoy the same exact phone with a stock ROM, but with the added perks that rooting brings. Yes, that includes sideloading. And SIM unlock. And no more bloatware.
However, if this sideloading trick can be perfected, and it will keep people who otherwise don't have the patience to root their phones and as a result would just screw them up, causing them to further not spend the time to read and search, instead firing off 1000's of redundant "Halp Me!" posts, then that's a good thing.

ehh I would just rather use adb.... (if I was stock)

mudknot2005 said:
ehh I would just rather use adb.... (if I was stock)
Click to expand...
Click to collapse
Or that. My friggin' rant post from hell was long winded enough for me to forgo mentioning much more.

mudknot2005 said:
ehh I would just rather use adb.... (if I was stock)
Click to expand...
Click to collapse
Yeah, OP, you should definitely include a link to the adb method, or the Sideload Wonder Machine method.
I used SWM to install Swype weeks before I got the AT&T non market option (which was a week before I rooted).

ST3ALTHPSYCH0 said:
Yeah, OP, you should definitely include a link to the adb method, or the Sideload Wonder Machine method.
I used SWM to install Swype weeks before I got the AT&T non market option (which was a week before I rooted).
Click to expand...
Click to collapse
The adb method for sideloading an app is already discussed in mudknot's stickied guide.

Supposedly there is still an update floating around for unknown sources. If I happen to get my hands on it I will post it.
That's the only reason I haven't updated the side loading part of the guide. If the update gets pushed to every phone with in the month then it would be obsolete quick. I might add it just to have the most information possible... Though I will not put this method on there, because there is no reason you should have to give something up to gain something (captivate anyone?)..

Still stock here, without the non-market update.
No issues at all using the SWM. I didn't like that whole stupid "dropbox" method mentioned. It's easier and faster to just to use "disk drive" mode to copy the apk files onto the PC.

mudknot2005 said:
Supposedly there is still an update floating around for unknown sources. If I happen to get my hands on it I will post it.
That's the only reason I haven't updated the side loading part of the guide. If the update gets pushed to every phone with in the month then it would be obsolete quick. I might add it just to have the most information possible... Though I will not put this method on there, because there is no reason you should have to give something up to gain something (captivate anyone?)..
Click to expand...
Click to collapse
Absolutely agreed. Your guide should be reserved for known methods that provide the desired result without sacrificing other functionality.
I really don't see what all the excitement is about, regarding this new method. I mean, side loading has been a non-issue for rooted devices from the start, now it's *officially* a non-issue, even for bone stock devices.
This new method might have been a useful workaround for stock phones before ATT changed course on sideloading, now not so much.

[Q] Will Updates Affect Ability to Interop-unlock in HTC 2nd Gen Devices?

Searched and looked around in a few threads, but couldn't find a definitive/clear answer.
Recently bought an HTC Radar. Phone prompted that an update was available (I believe it's an OS update).
My question is should I be updating my phone at all if I'm hoping for an interop unlock?
From reading, am I right to assume OS updates should not affect future abilities to interop, but firmware/baseband updates would? Is there an easy way to figure that out?
I'm coming from an iPhone, so I still have this mindset of "to update or not to update..." when it comes to homebrew.
Thanks all!

Usually HTC updates disable the unlock but beware that it is also possible for updates to disable hacks and mods too. Do some research first. What update is it, does it say?

OS updates shouldn't affect the ability to unlock, correct. On the other hand, we can't currently interop-unlock HTC gen2 phones anyhow, so at this point it doesn't matter much. I suppose firmware updates might make it harder to do so in the future, but if nothing else we can always tell people to roll back too. I suggest you keep your backups around (move or copy them to a folder with a different name so they don't get overwritten; they're stored in "%localappdata%\Microsoft\Windows Phone Update").

sinister1 said:
Usually HTC updates disable the unlock but beware that it is also possible for updates to disable hacks and mods too. Do some research first. What update is it, does it say?
Click to expand...
Click to collapse
Thanks. The phone came with stock 7.5, and the update prompted is 7.10.8107.79. I went ahead and updated regardless because the keyboard issue was driving me nuts.
GoodDayToDie said:
OS updates shouldn't affect the ability to unlock, correct. On the other hand, we can't currently interop-unlock HTC gen2 phones anyhow, so at this point it doesn't matter much. I suppose firmware updates might make it harder to do so in the future, but if nothing else we can always tell people to roll back too. I suggest you keep your backups around (move or copy them to a folder with a different name so they don't get overwritten; they're stored in "%localappdata%\Microsoft\Windows Phone Update").
Click to expand...
Click to collapse
Thanks. Done and done.

[Q] Verizon OTA Update - 5/30/13

I read on cnet last night that Verizon would be sending an update for all GS3 users and, sure enough, I was prompted for the update for an update morning. (5/30/2013)
I am running stock 4.1.2 rooted.
Does anyone know if this is safe for me to apply? Will I lose root?
Thanks!

yep
You will lose root and if you have a custom recovery (twrp for instance) it will be overwritten. You will also get a "update failed" message. However, the update actually will succeed. You can reroot the same way you did before (unlock bootloader, root, install custom recovery if desired). I was surprised that the OTA was even available for rooted/custom folks. There will be a couple new apps installed, one dealing with CallerID which will force your 4G and WiFi to both be on - freezing that new app will fix that issue too, search the forums for details.
Goddrick said:
I read on cnet last night that Verizon would be sending an update for all GS3 users and, sure enough, I was prompted for the update for an update morning. (5/30/2013)
I am running stock 4.1.2 rooted.
Does anyone know if this is safe for me to apply? Will I lose root?
Thanks!
Click to expand...
Click to collapse

gozirra said:
You will lose root and if you have a custom recovery (twrp for instance) it will be overwritten. You will also get a "update failed" message. However, the update actually will succeed. You can reroot the same way you did before (unlock bootloader, root, install custom recovery if desired). I was surprised that the OTA was even available for rooted/custom folks. There will be a couple new apps installed, one dealing with CallerID which will force your 4G and WiFi to both be on - freezing that new app will fix that issue too, search the forums for details.
Click to expand...
Click to collapse
How are you surprised about the OTA being available for rooted phones? You don't make any sense with that comment as the update is just that an update. Verizon doesn't know which customers have rooted their device just that you have a device that needed to be updated.

Because thats the way it always was back when I had my original Incredible? A lot of people were surprised that the update was available to them, I'm not a minority here. No reason to be rude.
jmxc23 said:
How are you surprised about the OTA being available for rooted phones? You don't make any sense with that comment as the update is just that an update. Verizon doesn't know which customers have rooted their device just that you have a device that needed to be updated.
Click to expand...
Click to collapse

gozirra said:
Because thats the way it always was back when I had my original Incredible? A lot of people were surprised that the update was available to them, I'm not a minority here. No reason to be rude.
Click to expand...
Click to collapse
I am not being rude just stating the fact that Verizon doesn't know your phone is rooted in fact all companies don't know what you did to your phones until something bad happens to it. I will also add that the update will be pushed regardless if you're rooted or not the only time it won't get pushed is with a custom ROM made by someone who knows how to block Verizon updates.

jmxc23 said:
I am not being rude just stating the fact that Verizon doesn't know your phone is rooted in fact all companies don't know what you did to your phones until something bad happens to it. I will also add that the update will be pushed regardless if you're rooted or not the only time it won't get pushed is with a custom ROM made by someone who knows how to block Verizon updates.
Click to expand...
Click to collapse
Funny I did not see him mention anywhere that Verizon knew anything. His experience with a previous phone was that for some reason after rooting etc. his phone did not receive OTA updates. Whatever the reason, instead of being rude, you could have simply helped him understand like you finally did : "... the only time it won't get pushed is with a custom ROM made by someone who knows how to block Verizon updates.".

ghostboa said:
Funny I did not see him mention anywhere that Verizon knew anything. His experience with a previous phone was that for some reason after rooting etc. his phone did not receive OTA updates. Whatever the reason, instead of being rude, you could have simply helped him understand like you finally did : "... the only time it won't get pushed is with a custom ROM made by someone who knows how to block Verizon updates.".
Click to expand...
Click to collapse
Okay I have corrected myself like you have so eloquently posted I don't see the need to defend him if I already like you stated told him finally the reason. I already know that I should have done it sooner and like I normally do correctly fall back and respond in a normal tone. I unlike others am self aware of what I do and make an effort to correct any wrongs that I have caused. I don't filter myself when I post my thoughts so they can come across
as rude depending on your sensitivity level the difference is that I don't insult people nor belittle them in any way. I can only imagine how you or anyone will react if I was a total jackass.

ok then
Thanks for the explanation. follow-up question - if Verizon doesn't "know" then what is with the "unauthorized software discovered, call Verizon" popup that so many people have reported? Or the infamous yellow triangle? I assumed (yeah I know the cliche) that Verizon in fact DID "know" otherwise that wouldn't have happened. Simple mistake based on past experience, sorry.

As a side note.. If you have Titanium you can freeze SDM 1.0 and you won't get those updates

gozirra said:
Thanks for the explanation. follow-up question - if Verizon doesn't "know" then what is with the "unauthorized software discovered, call Verizon" popup that so many people have reported? Or the infamous yellow triangle? I assumed (yeah I know the cliche) that Verizon in fact DID "know" otherwise that wouldn't have happened. Simple mistake based on past experience, sorry.
Click to expand...
Click to collapse
This is completely unrelated to OTAs though. That warning is solely because of the secure bootloader on the Verizon GSIII. That warning is built into the system to pop up whenever you try installing software to the phone without having the prerelease bootloader in place. Verizon and Samsung intentionally made this model GSIII more difficult to install custom software onto or to make it a more secure device, depending on how you look at it. It's a business decision at the end of the day.
Sent from my SCH-I535 using Tapatalk 4 Beta

Probably business related as they don't want to be the first company to have an worldwide malware problem on their devices.

ghostboa said:
...you could have simply helped him understand like you finally did : "... the only time it won't get pushed is with a custom ROM made by someone who knows how to block Verizon updates.".
Click to expand...
Click to collapse
That's the key (at least in my experience with HTC phones). I can't remember the name of the file, but it was one file that you could rename and the phone would not check or ignore OTA updates that were pushed by the carrier.

i downloaded the update the other day by mistake as it bricked my phone. im rooted only and stock. i know its going to keep forcing the update thru, is there anyway i can get the update to go thru successfully without bricking my phone again?

You didn't brick your phone at least not a hardware brick.

YA 4.4.2 Bootloader Discussion

Hey there remaining Verizon S3 users!
Coming from my favorite device the T959V this has been quite a trip. This device's bootloader is seemingly impossible to unlock on the 4.4.2 NE1 firmware.
I've got a slightly modified Superlite rom rolling with SafeStrap already strapped. And it is great to say the least. Added some initd and utilities. Evie launcher is pretty nice btw- recommend a try :good:
However. I still really want this thing to be unlocked. The T959V has multiple working Fro, GB, ICS, JB, KK, L, M, AND Nougat ROMS. Totally different devices yes but-- even the newer S4-S6 have cracked loaders now.
There has to be a special way to change this things firmware.
Right now I have 2 ideas to throw out to the wind-
1- Would be that there could be a way to trick the device into thinking it is receiving a new update. Maybe somehow with CSC or something. Also I saw a file named authorized.xml and was reading through to find traces of knox. Would unauthorizing knox strings somehow render it useless?
2- I was reading a suggested post about AVB boots and how they can be resigned on devices such as the Google Pixel and allows the newer patches to still install. Including what was described as a forced re-sign method.
--- Could we somehow resign the bootloader on our device so as to gain control of it? Has anybody tried anything like this since around 2015?
I'll gladly talk about all of this more whenever I feel like popping on- and atm I have no web besides this service. :silly: so no DOS updates and no shiny linux for now.
Gladly tell me that it is "impossible" but I'm not asking that. I'm trying to add some ideas to possibly do the impossible.
Edit: This seems to be an interesting lead on emmc cracking this device. It's probably why people in other threads were in search of a "dev" edition.
http://forum.gsmhosting.com/vbb/f777/unlock-samsung-devices-bootloader-emmc-backdoor-2142981/

graycow9 said:
Hey there remaining Verizon S3 users!
Coming from my favorite device the T959V this has been quite a trip. This device's bootloader is seemingly impossible to unlock on the 4.4.2 NE1 firmware.
I've got a slightly modified Superlite rom rolling with SafeStrap already strapped. And it is great to say the least. Added some initd and utilities. Evie launcher is pretty nice btw- recommend a try :good:
However. I still really want this thing to be unlocked. The T959V has multiple working Fro, GB, ICS, JB, KK, L, M, AND Nougat ROMS. Totally different devices yes but-- even the newer S4-S6 have cracked loaders now.
There has to be a special way to change this things firmware.
Right now I have 2 ideas to throw out to the wind-
1- Would be that there could be a way to trick the device into thinking it is receiving a new update. Maybe somehow with CSC or something. Also I saw a file named authorized.xml and was reading through to find traces of knox. Would unauthorizing knox strings somehow render it useless?
2- I was reading a suggested post about AVB boots and how they can be resigned on devices such as the Google Pixel and allows the newer patches to still install. Including what was described as a forced re-sign method.
--- Could we somehow resign the bootloader on our device so as to gain control of it? Has anybody tried anything like this since around 2015?
I'll gladly talk about all of this more whenever I feel like popping on- and atm I have no web besides this service. :silly: so no DOS updates and no shiny linux for now.
Gladly tell me that it is "impossible" but I'm not asking that. I'm trying to add some ideas to possibly do the impossible.
Edit: This seems to be an interesting lead on emmc cracking this device. It's probably why people in other threads were in search of a "dev" edition.
http://forum.gsmhosting.com/vbb/f777/unlock-samsung-devices-bootloader-emmc-backdoor-2142981/
Click to expand...
Click to collapse
I've been around this and many many other forums for years now. If there was an unlock method it would of been found years ago. Devs have long moved on from the old S3. I still have my S3 lying around, bootloader unlocked but I really haven't messed around with it for quite a long time now
And yes the dev edition would of been nice had someone actually had one, it would of of course made it easier to crack the bootloader option maybe. I don't know much about the ins and outs of the device but I know many are permanently locked and will probably never be unlocked.
As far as certain other Samsung devices being unlocked those are far and few between. VZW got smart and started just locking them from the start. This is a huge reason why I left Verizon. The S3 was my last device on big red. I since have had a Nexus 5 and 6 and now a oneplus 3t. I really don't like locked devices and the ability to unlock them and customize them just intrigues me to no end. Good luck however in finding something that may work, but I highly doubt it will ever be cracked
Sent from my OnePlus 3T

Ya I expected your negatude Shapes. Already seen that you have been searching but it isn't just some application you run. It's an unknown exploit that I'm sure exists. There are exploits right now that can be considered viral potentially exploiting my device as we speak. Maybe not granted my semi-precautious take on things.
Quadrooter and dirty cow could be used to exploit the S3 and gain access to a quoted "all" physical memory. So I find it hard to believe that things can't work in our favor.
Being open minded here. After all, this is technically hacking your own device. Which--
Got me thinking the other day, becausr I was setting up my laptop proper- could we run a nix distro and poke through the bootloader's parameters via exploitation tools? Referencing Kali or it's elder BTrack. But I think it is possible and I just haven't gotten around this loop mounting issue.
To be clear, running a distro ON the device. My flat is already running square.
Sent from my SCH-I535 using XDA-Developers Legacy app

Also a purposely separate post- I'm building a ROM for this locked firmware and the goal is to have some specific updated apps and yet trim it nicely so as to save space and RAM it's mostly stock style-wise but it'd be cool to re-theme it. I haven't gotten things deodexed yet- being I haven't gotten my apktools working proper yet.
Is there anybody left to be interested in this? I haven't posted anything I've made before- usually just keep them lying around for emergency flashes.
Sent from my SCH-I535 using XDA-Developers Legacy app

graycow9 said:
Ya I expected your negatude Shapes. Already seen that you have been searching but it isn't just some application you run. It's an unknown exploit that I'm sure exists. There are exploits right now that can be considered viral potentially exploiting my device as we speak. Maybe not granted my semi-precautious take on things.
Quadrooter and dirty cow could be used to exploit the S3 and gain access to a quoted "all" physical memory. So I find it hard to believe that things can't work in our favor.
Being open minded here. After all, this is technically hacking your own device. Which--
Got me thinking the other day, becausr I was setting up my laptop proper- could we run a nix distro and poke through the bootloader's parameters via exploitation tools? Referencing Kali or it's elder BTrack. But I think it is possible and I just haven't gotten around this loop mounting issue.
To be clear, running a distro ON the device. My flat is already running square.
Click to expand...
Click to collapse
I don't think shapes was trying to act negative at all, just stating the obvious. Nobody is going to try to unlock the Verizon S3, it's pretty much a dead end.
The unlock method used on the S5 will most likely work on this phone, but we need a developer CID to rewrite to the emmc as the series chip used on the S3 likely has the same vulnerability. This is what happened on the S5.
If you read some of the other posts (sounds like you have), we looked for an S3 developer edition but had no luck in tracking one down. For one, it's an incredibly old device. Secondly, you'd have to be semi retarded to purchase one as the original unlock method was around before the developer edition was released.
So yes, if you can find a developer S3 this will likely be an unlock method. It tricks the S3 into thinking it's a developer phone and unlocks the bootloader if the method to write it works the same as in the S5.
As for your questions,
1. I think you're underestimating the amount of security that goes into the bootloader itself. If you want to learn a lot about Android security in general, in the Android security discussion section located under general forums, there's tons of info regarding how complex this all is. But basically, in order to send an update patch, it needs to be signed (you can't just fake the signature) and it must agree with the current bootloader. The way the bootloader is written, it simply won't allow a reversion back to earlier versions or it'll abort the boot.
An easier way to think of this is understanding that the changes made are preinstalled before the actual boot. There's no way for us to change this through normal methods as the emmc has to be written to directly. There is no way to do this from download or recovery mode. Wouldn't matter if you flashed it or used and update package, they are essentially the same thing.
So the only way to actually change the bootloader is to write to the emmc directly through use of the JTAG port. This changes the code of the entire bootloader before the boot and the phone will boot up with any version of the S3 bootloader you write.
2. I think I kind of answered that?
Hope it's clear.

BadUsername said:
I don't think shapes was trying to act negative at all, just stating the obvious. Nobody is going to try to unlock the Verizon S3, it's pretty much a dead end.
The unlock method used on the S5 will most likely work on this phone, but we need a developer CID to rewrite to the emmc as the series chip used on the S3 likely has the same vulnerability. This is what happened on the S5.
If you read some of the other posts (sounds like you have), we looked for an S3 developer edition but had no luck in tracking one down. For one, it's an incredibly old device. Secondly, you'd have to be semi retarded to purchase one as the original unlock method was around before the developer edition was released.
So yes, if you can find a developer S3 this will likely be an unlock method. It tricks the S3 into thinking it's a developer phone and unlocks the bootloader if the method to write it works the same as in the S5.
As for your questions,
1. I think you're underestimating the amount of security that goes into the bootloader itself. If you want to learn a lot about Android security in general, in the Android security discussion section located under general forums, there's tons of info regarding how complex this all is. But basically, in order to send an update patch, it needs to be signed (you can't just fake the signature) and it must agree with the current bootloader. The way the bootloader is written, it simply won't allow a reversion back to earlier versions or it'll abort the boot.
An easier way to think of this is understanding that the changes made are preinstalled before the actual boot. There's no way for us to change this through normal methods as the emmc has to be written to directly. There is no way to do this from download or recovery mode. Wouldn't matter if you flashed it or used and update package, they are essentially the same thing.
So the only way to actually change the bootloader is to write to the emmc directly through use of the JTAG port. This changes the code of the entire bootloader before the boot and the phone will boot up with any version of the S3 bootloader you write.
2. I think I kind of answered that?
Hope it's clear.
Click to expand...
Click to collapse
Truthfully after being around the forums for as long as I have I'm really surprised there is any interest in unlocking this device at this point in time. There are just so many other options and unlocked vzw s3s are not that hard to come by.
And I wasn't being negative it's about being realistic. Thanks for sticking up for me brother
Sent from my OnePlus 3T

Are there any updates to this by any chance, I am interested :C

any hope?