Related
Is there any known way of cracking the NAND protection on this phone yet?
Or if not, does anyone know where I should look for the latest news on rooting this Japanese-only phone?
I've been looking all over the internet for months and turned up nothing. I could really do with some help here please guys!
I am also interested in an answer to this question. I have been in talks with a few of the Japanese users currently trying to figure out the phone, and I would like to post a bit about what we know, what progress has been achieved and why this is important for other people outside of Japan.
First and foremost, Sharp has every intention of getting their 3D phones into the hands of overseas users. Now, I could be patient and wait for this to launch, and then for the teams to get to work and crack the bootloader open properly. But why not get an early jump on the work so that the phone can arrive, on the Western shores, fully ready for custom roms and root permissions? The three major 3D phones Sharp currently is pimping (the IS03, the 003SH and the SH-03C) are essentially the same phone with minor tweaks. Serious progress on one could lead to a bit step forward for all! And as the Lynx is currently stuck at 2.1 (and won't be 2.2 till "summer"), it's in the greatest need for an upgrade (the 003SH is already 2.2, and the IS03 goes to 2.2 this week). I know that I'm being a little selfish in this endeavor, but I also know I'm not the only one with this phone, and not the only one interested. Perhaps I'm just the most vocal.
Now, for a quick rundown:
rageagainstthecage: doesn't work, freezes up, phone must be hard rebooted with battery removal.
psneuter: offers root access, but cannot modify /system due to NAND protection/locked bootloader.
SuperOneClick: see above.
Z4root: see above.
Universal Androot: doesn't work. Attempts to root, gets the "no good fuu~~" response.
Visionary: crashes when attempting soft root.
Unrevoked apk: fails immediately. No harm to the phone, but no success either.
gfree: No luck, can't toggle S-off but that may be due to the fact that the phone is definitely not the G2.
Unrevoked app: can't recognize the phone.
I'm hoping that someone in the UnrEVOked community is willing to try and work with me/us on this. We're not a large group by any means (and a majority of the users don't have an expansive English grasp) but we are dedicated, and I'm trying something new everyday. Sharp has even released the kernel as open source, so, if an exploit can be found, work can begin immediately. This could be something big, something wonderful. If anyone could please contact me and let me know, I'm really hopeful.
And sorry for hijacking your thread Eliott.
Sent from my SH-03C using Tapatalk
Sharpen3d said:
I am also interested in an answer to this question. I have been in talks with a few of the Japanese users currently trying to figure out the phone, and I would like to post a bit about what we know, what progress has been achieved and why this is important for other people outside of Japan.
First and foremost, Sharp has every intention of getting their 3D phones into the hands of overseas users. Now, I could be patient and wait for this to launch, and then for the teams to get to work and crack the bootloader open properly. But why not get an early jump on the work so that the phone can arrive, on the Western shores, fully ready for custom roms and root permissions? The three major 3D phones Sharp currently is pimping (the IS03, the 003SH and the SH-03C) are essentially the same phone with minor tweaks. Serious progress on one could lead to a bit step forward for all! And as the Lynx is currently stuck at 2.1 (and won't be 2.2 till "summer"), it's in the greatest need for an upgrade (the 003SH is already 2.2, and the IS03 goes to 2.2 this week). I know that I'm being a little selfish in this endeavor, but I also know I'm not the only one with this phone, and not the only one interested. Perhaps I'm just the most vocal.
Now, for a quick rundown:
rageagainstthecage: doesn't work, freezes up, phone must be hard rebooted with battery removal.
psneuter: offers root access, but cannot modify /system due to NAND protection/locked bootloader.
SuperOneClick: see above.
Z4root: see above.
Universal Androot: doesn't work. Attempts to root, gets the "no good fuu~~" response.
Visionary: crashes when attempting soft root.
Unrevoked apk: fails immediately. No harm to the phone, but no success either.
gfree: No luck, can't toggle S-off but that may be due to the fact that the phone is definitely not the G2.
Unrevoked app: can't recognize the phone.
I'm hoping that someone in the UnrEVOked community is willing to try and work with me/us on this. We're not a large group by any means (and a majority of the users don't have an expansive English grasp) but we are dedicated, and I'm trying something new everyday. Sharp has even released the kernel as open source, so, if an exploit can be found, work can begin immediately. This could be something big, something wonderful. If anyone could please contact me and let me know, I'm really hopeful.
And sorry for hijacking your thread Eliott.
Click to expand...
Click to collapse
Not at all, thanks for the great info!
As crazy as it might sound, one thing I recommend doing is to continue monitoring other roofing methods that aren't exactly for the sh-03c and seeing what happens. Recently a new method for the Thunderbolt has been unveiled, and I have every intention to try it out. Obviously the likelihood of it working is slim, but it's a ton better than running z4root over and over and hoping for different results.
Sharpen3d said:
As crazy as it might sound, one thing I recommend doing is to continue monitoring other roofing methods that aren't exactly for the sh-03c and seeing what happens. Recently a new method for the Thunderbolt has been unveiled, and I have every intention to try it out. Obviously the likelihood of it working is slim, but it's a ton better than running z4root over and over and hoping for different results.
Click to expand...
Click to collapse
I'm a bit hesitant to use untested methods. This is my first Android phone and I have never rooted a phone before so it would be wise for me to wait for someone else to find a reliable way first.
I have flashed many older phones and PSPs in the past but this scene is quite new to me.
I am still checking many Japanese sites daily for news of a root. I will send you a PM if I find anything
figured to bump the thread as I`m also a Lynx3D owner looking for root access and a way around the NAND protection. I would be nice to free up this phone .
I'm still searching daily but it seems to be impossible, I'm not sure if it will ever be rooted.
Never mind though, at least we get android 2.2 this month
Recently there's been some success for the IS03 since receiving their 2.2 update. A new process labelled is03break has apparently been great for soft rooting. It hasn't worked on the SH-03 due to it still being on 2.1, but perhaps there will be a breakthrough after our update drops in June (July?).
Additionally, certain other blogs (specifically the Japanese blog Androot) has reported a failure in attempting all conventional root methods, confirming that the Japanese teams are on the same page we are. Both good and bad, as it does give us a baseline, but I refuse to accept there isn't a solution yet.
Sharpen3d said:
Recently there's been some success for the IS03 since receiving their 2.2 update. A new process labelled is03break has apparently been great for soft rooting. It hasn't worked on the SH-03 due to it still being on 2.1, but perhaps there will be a breakthrough after our update drops in June (July?).
Additionally, certain other blogs (specifically the Japanese blog Androot) has reported a failure in attempting all conventional root methods, confirming that the Japanese teams are on the same page we are. Both good and bad, as it does give us a baseline, but I refuse to accept there isn't a solution yet.
Click to expand...
Click to collapse
That certainly gives me hope, looking forward to 2.2 even more now!
And Docomo have announced that 2.2 is coming this month (May). It has been widely reported and they confirmed it in the Docomo shop this morning for me
Despite my better judgement, I went ahead and ran the is03break on my phone yesterday. Not only was it not successful (ran until it timed out) but it managed to adjust my settings enough that my phone wasn't able to see the cellular network, effectively destroying it's "phone" capabilities. I was able to hard reset it through psneuter/adb and now it's back to normal, but it was definitely a bit of a scare.
When 2.2 comes out, I may give it another go, but in the meantime I'll just play nice. Docomo staff confirmed 2.2 is coming before the end of May, and there's a chance we'll need to do it through the PC like the AU folk had to.
Looks like the update may well have been delayed until next month -
http://translate.googleusercontent.com/translate_c?hl=en&prev=/search%3Fq%3Dlynx%2B3d%2B2.2%26hl%3Den%26client%3Dfirefox-a%26hs%3DG75%26sa%3DX%26rlz%3D1R1GGHP_en-GB___JP427%26tbs%3Dqdr:d%26prmd%3Divns&rurl=translate.google.com&sl=ja&twu=1&u=http://juggly.cn/androidrumors&usg=ALkJrhgmfYRu8El9AjAHz_UeNb1s85EhZw
This is getting a bit much now. 6 months I've been waiting for them to update this phone. I'm considering taking it back and demanding a refund.
For what it's worth, even if there's a delay, at least it's a bit more definitive than things have been. Way back in March when the Quake hit, we were told it was being delayed from March to "Summer." Then they really brought it forward for May, which I don't really consider summer. That rumor blog (and remember, the key word there is rumor) suggests it will be delayed until early June. Worst case scenario, that means that, instead of getting it this week, we receive it in two weeks. I agree it's a pain in the ass, and the fact remains that, stuck at 2.1, we can't use a lot of conventional rooting tools (not to mention run flash, do App2SD, JIT, etc). But returning the phone at this point accomplishes next to nothing. The summer Docomo lineup is a bit underwhelming, in my opinion. You're paying for the camera, and the phone is attached to that. Even if you get the Galaxy S (a really nice phone, no doubt) it's starting to become a bit older. IF we can hold on till SH-03C receives 2.2, I honestly believe a world of possibilities open up. This community may not be large, but we can still tout a 3D phone proudly, and getting 2.2 really legitimizes its abilities.
Just be patient man.
Yeah, you are right.
I'm just getting frustrated at having to keep deleting applications. I'm really looking forward to using flash, bumping up the CPU and trying out that new Tegra app for playing Tegra games!
I'm just really hoping for App2SD. This is getting severely limiting. Additionally, I'm pretty sure that rooting will become significantly more likely once we're up on 2.2. I'm confident that, once we get to Froyo, our phones might be able to piggyback on methods utilitized by other NAND locked phones (example: EVO) that have been successfully rooted.
I just want to uninstall that stupid 3D golf game. It takes up so much memory it's insane.
This sounds promising -
"May 27, 2011
The previous model, LYNX 3D SH-03C in Android 2.2 update seems to be out soon. The details will be announced separately, "there is no update, that will never" Yes."
http://translate.googleusercontent.com/translate_c?hl=en&prev=/search%3Fq%3Dlynx%2B3d%2B2.2%26hl%3Den%26safe%3Doff%26client%3Dfirefox-a%26hs%3D5Ye%26sa%3DX%26rlz%3D1R1GGHP_en-GB___JP427%26biw%3D1120%26bih%3D927%26tbs%3Dqdr:d%26prmd%3Divns&rurl=translate.google.com&sl=ja&twu=1&u=http://ch00288.kitaguni.tv/e1805281.html&usg=ALkJrhgPutM5T2orqoipGRQTi3kSISqnlg
The woman at the Docomo helpline, having started to recognize my voice, totally leveled with me. The update was planned for the end of this month, and they got screwed in timing. They hope for the first weeks of June, but it may be even later than that. Truth be told, I bought my SH-03c aftermarket, so I can't return it even if I wanted to. But I'm not bailing. I'm confident we will see the update before the 15th, and, really, as long as it doesn't start malfunctioning, I can wait.
More rumors, looks like July 7th is the day -
"NTT DoCoMo's "Galaxy S SC-02B", "Galaxy Tab Sc-01C", "LYNX 3D SH-03C" on the OS version is effective from June 7, "will" is a rumor.
According to rumors, the version of June 07, Galaxy S Tab and the Android 2.3 (Gingerbread) to, LYNX 3D SH-03C is Android 2.2 (Froyo) is going to be provided.
LYNX 3D SH-03C
Changes as part of the Android 2.2
-Flash Player 10.1 or later for
- Micro SD card can move the app (the app only support)
- Respond to voice the character input
- Application for Automatic Updates to bulk update
- The application "search" and "News and Weather," in some of the sharp changes in their own additional
- Launch applications list "end all" button added
- Power management notification bar menu (Wi-Fi or BT) is added
- Supports multi-line display in the profile email address and telephone chat
- Added ability to integrate similar contacts in the phone book
- Added the ability to transmit infrared applications infrared receiver
- Change the background color
- Change display Antenapikuto
- Text resize cursor display
- Improved slightly phenomenon events
How to update, download the update tool from the site WEB Sharp, PC and USB connection seems the only way to do. "
http://translate.google.com/translate?hl=en&sl=ja&u=http://maruta.be/news_japan_2100/828&ei=Pq7jTdb4DYuSuwP4x_D0Bg&sa=X&oi=translate&ct=result&resnum=8&ved=0CG4Q7gEwBw&prev=/search%3Fq%3Dlynx%2B3d%2B2.2%26hl%3Den%26safe%3Doff%26client%3Dfirefox-a%26hs%3Dvf4%26sa%3DX%26rlz%3D1R1GGHP_en-GB___JP427%26biw%3D1120%26bih%3D927%26tbs%3Dqdr:d%26prmd%3Divns
That makes a ton of sense. June 7th is when Nintendo is launching a huge update for their platforms as well, and Japan seems to like to do a ton of updates all together.
I want this so badly, I can't believe it's going to be another week.
The product page for the SH-03C over at nttDOCOMO just went 404. I really hope it's because they're busy updating with new information, and not because I'm going to be furiously angry.
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.
Okay, we got the 4.3 update we all been waiting for. Now comes the magic question - WHY.
I'm not trying to troll here, I think I have a valid question. It's got features taken out, a lot of stuff is different now, some things work, some things don't. It looks different, but - is it better? I am yet to find what is it that it does better than original 4.1 firmware.
I guess what I'm trying to ask is : "give me a reason not to revert back to where it was"
galets said:
Okay, we got the 4.3 update we all been waiting for. Now comes the magic question - WHY.
I'm not trying to troll here, I think I have a valid question. It's got features taken out, a lot of stuff is different now, some things work, some things don't. It looks different, but - is it better? I am yet to find what is it that it does better than original 4.1 firmware.
I guess what I'm trying to ask is : "give me a reason not to revert back to where it was"
Click to expand...
Click to collapse
Because you can't. Once you take the 4.3 OTA, you're stuck with it.
McDastardly said:
Because you can't. Once you take the 4.3 OTA, you're stuck with it.
Click to expand...
Click to collapse
I have to say, it was incredibly disappointing that Samsung decided to sneak device lock-down disguised as a software update. Very lame. I was under impression that Samsung does value community building mods for its overpriced phones, understands the value of such community. Apparently, they don't. I agree with someone who said it will be the last Samsung device he purchased, I think it's time for me to join the boycott.
But coming back to the issue at hand: lets imagine I was lucky enough not to trust Samsung to deliver me an update and instead took a hacked one. Is there any reason whatsoever to stay on 4.3? And by that I mean:
- does 4.3 solve some problem in original firmware, that anyone should care about?
- does 4.3 implement some new feature, which was not in original 4.1 firmware that I should be excited about?
galets said:
Okay, we got the 4.3 update we all been waiting for. Now comes the magic question - WHY.
I'm not trying to troll here, I think I have a valid question. It's got features taken out, a lot of stuff is different now, some things work, some things don't. It looks different, but - is it better? I am yet to find what is it that it does better than original 4.1 firmware.
I guess what I'm trying to ask is : "give me a reason not to revert back to where it was"
Click to expand...
Click to collapse
What features were taken out? Anything that can be replaced with better apps on the market shouldnt count. In my opinion the new stock task manager makes it worth it.
---------- Post added at 01:17 PM ---------- Previous post was at 01:11 PM ----------
Well if I could go back in time I would have just waited for a custom 4.3 tw rom. But at least I don't feel the need to flash a new rom every day now.
ThePagel said:
What features were taken out?
Click to expand...
Click to collapse
At this time, my biggest issue is that codes do not work, and i cannot get into hidden menu, so no QPST. I'm on PagePlus, so updating PRL is a manual process, and without putting phone into modem mode I cannot do that.
There are a few other annoying things, such as: can't turn off warning against increasing volume on headphones (i think there's some add-ons which let you do it though)
galets said:
At this time, my biggest issue is that codes do not work, and i cannot get into hidden menu, so no QPST. I'm on PagePlus, so updating PRL is a manual process, and without putting phone into modem mode I cannot do that.
There are a few other annoying things, such as: can't turn off warning against increasing volume on headphones (i think there's some add-ons which let you do it though)
Click to expand...
Click to collapse
I can understand your annoyance with the hidden menu being gone. But that wasn't a "feature" it was a "hidden menu" after all and with root there are ways to get rid of the volume warning. That bugs the crap out of me as well but not to the point to change it yet.... YET!
galets said:
I have to say, it was incredibly disappointing that Samsung decided to sneak device lock-down disguised as a software update. Very lame. I was under impression that Samsung does value community building mods for its overpriced phones, understands the value of such community. Apparently, they don't. I agree with someone who said it will be the last Samsung device he purchased, I think it's time for me to join the boycott.
Click to expand...
Click to collapse
Nah, Samsung hasn't been overwhelmingly developer friendly for awhile. There's a bit of dislike for them due to Exynos processors.
Additionally, it wasn't that sneaky. The phone was intended to have a locked bootloader from the beginning. It was expected that the update would patch the loophole we found from the leaked aboot step. That's why it was mentioned multiple times to not accept the 4.3 update in case it locked the bootloader.
Samsung hasn't been developer friendly for a long time. Anytime you take an OTA update you can expect it to prevent the use of custom firmware unless a trusted source says it doesn't.
Sent from my SCH-I535 using Tapatalk 2
Hi folks,
My Shield 32 GB just arrived and is charged up. I've signed on with a google account and done nothing else.
I will eventually root it but want to put it through its paces for a month or so first.
It arrived with KK 4.4.2 (wow! so old!) on it. It offers an OTA update from October 2014. Says it is OTA 1.21. I've seen LOTS of other OTA numbers much later around these forums. Do I have to take the 1.21 OTA before I can get to the more recent ones?
And, by taking the OTA, am I doing anything irreversible that I probably shouldn't do, since I'm eventually a rooting and maybe ROMing kind of guy?
Thanks. I've read up and it looks like I probably want to go all the way to the 5.1 release, once they sort out the speaker-killing bug. But for the moment I'd like to make sure I'm not missing anything before taking the OTA.
Thanks!
Marc
I decided to download the update after I successfully activated the device on AT&T's cellular network.
That was a bit of a hassle... couldn't do it from the device (the ATT app said something about incompatibility with the SIM card), the PC online web registration wouldn't accept it because NVidia Shield wasn't listed in the device types, and it took the efforts of 3 ATT folks to get me activated. First one passed me to the second one when he found out it was a device not purchased from ATT (but... dude... here's the SIM and IMEI number that's all you need...), the second one set me up and told me to call another number to accept terms and conditions. Did that, still no joy, found the default APN isn't set up right. Fixed that, still no joy, eventually talked to person 3 that found out they didn't attach a data plan to the device when they set it up... as part of my family shared data account. Duh.
Anyway, I applied the 1.21 and then it prompted me to download the 2.1 update to Android 5.01. It has downloaded. I think I want to copy it over to my PC before I let it apply.
Marc
Hmmm. Poked around and found the 1.21 update but not the 2.1 full LTE OTA. Perhaps I'd need root to get at the files. Oh well. I can always download it if I need it. Applying the 2.1 update now.
And I've made it all the way to the 2.2.1 hotfix. Seems stable enough for the moment.
I understand OTA 3.0 got pulled; so I guess I'll be staying on Lollipop 5.01 until they release the fix.
It's a bit surprising that I had to do all the updates sequentially and that there wasn't any direct-to-the-latest. But it didn't take long. I wonder if all these OTAs are clogging up my memory somewhere?
OK, on to exploration!
Marc
the update got pulled indeed, caused all kind of problems, including blown speakers
nvidia employee told us on nvidia forum they would release a new OTA 3.1, targeted end of june
lastest news: it's now targeted end of july....
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?