Kingroot? Anyone? - Xperia Z5 Q&A, Help & Troubleshooting

I have the Z5 coming in a couple of days and want to get familiar with it before it arrives.
I've previously had the Samsung Note 2, which was a pleasure and easy to root and flash roms, but had horrible burn issues dues to AMOLED display. I've also owned two LG phones (the Optimus G Pro and the G2) both of which sucked due to easily being bricked.
Is the root app Kingroot a good way to go? Or should I opt to do the headache-causing fastboot adb method?
I'm probably just going to keep the stock rom that is on the phone, I believe it will be 5.1 or 5.1.1 as I've heard that MM takes away the Stamina mode.
Seeing that I will probably keep stock rom, all I want to do is root the phone so that I can remove bloatware and install Titanium and Philz One Touch or TWRP if the Philz is not available for this phone.
So, having searched, I found no threads on the Kingroot app. is there anyone here with experience with this?
DISCLAIMER: I AM VERY WELL AWARE OF THE HOUSE TROLLS WHO COME ALONG AND CHANT THINGS LIKE "SEARCH FIRST BEFORE ASKING QUESTIONS" AND I'M WELL AWARE OF THOSE WHO WOULD RATHER POST A LINK TO ANOTHER TOPIC. PLEASE! DO NOT DO EITHER OF THESE. I AM SIMPLY LOOKING TO DISCUSS THIS WITHIN THIS THREAD.
THANK YOU AND COME AGAIN.

Tbh I don't think kingroot is supported as there is no root method.
There is however a kingroot thread maybe a search
I for one would use it to root then change to supersu not caring about my details being shared all we all want is root what ever method
http://bfy.tw/4plb
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Since there is another thread dedicated why is there need to discuss it here?
After reading your "disclaimer" [emoji14]
(sorry couldn't resist lol)
Sent from my Xperia™ Z5 using Tapatalk

Kingroot won't work. At this time. Because of bootloader protection Sony created. Not root for Locked Bootloader at this point, maybe but maybe in future...

bubimir13 said:
Kingroot won't work. At this time. Because of bootloader protection Sony created. Not root for Locked Bootloader at this point, maybe but maybe in future...
Click to expand...
Click to collapse
It's due to dm-verity that has been available on Linux for some time and that Google and Sony and others implemented. That however maybe possible to be patched using some sort of exploit which is what root apps use to root in the first place for many years
Sent from my Xperia™ Z5 using Tapatalk

I didn't see the other thread for Kingroot. And that thread you posted was about Kingroot in general. I was looking for Kingroot germane to the Z5.
(I've been coming here for almost three years and have found the search function to be as much of a headache and the web version of this site. Ever notice how many awful ads there are and other things that cause the page to load like it was 1997?)
Any how, thanks all for your input. I figured Kingroot was too good to be true. LOL
So if I'm understanding correctly, after unlocking the bootloader, the only way to root is through fastboot ADB? (ugh)

Perry2547 said:
I didn't see the other thread for Kingroot. And that thread you posted was about Kingroot in general. I was looking for Kingroot germane to the Z5.
(I've been coming here for almost three years and have found the search function to be as much of a headache and the web version of this site. Ever notice how many awful ads there are and other things that cause the page to load like it was 1997?)
Any how, thanks all for your input. I figured Kingroot was too good to be true. LOL
So if I'm understanding correctly, after unlocking the bootloader, the only way to root is through fastboot ADB? (ugh)
Click to expand...
Click to collapse
I understand that's why I use Google with XDA at the end of the search term instead of XDA search. in fact I don't even use the XDA site anymore because the ads and tracking slows the pages right down.
Yeah I wouldn't actually unlock my bootloader anymore even if I could.
The process is to install a custom kernel with fastboot
Sent from my Sony Xperia Z5 using XDA Labs

So in order to root, first would have to unlock the bootloader, and you wouldn't recommend that?
It's not that big of a deal right now to me as with Lollipop many of the bloatware apps can be disabled.
One of the things I'm really wanting to do is figure out what way to tweak this device (when it gets here) so that there won't be over heating issues. I did my research before buying this phone and I think it's going to be a good one. I've seen some posts about the camera not being that great but I still have hopes that the camera will be one of the best parts of it.
At the moment, since my G2 is nothing more than a paperweight, (due to my attempt at replacing the non-removable battery) I'm using a $49 Kyocera from Walmart. So just about anything will be better than the camera on this phone, LOL

Currently yes. Not unlocking the bootloader is my personal opinion.
I don't have any overheating issues and camera is great. Trouble with research is people only write the bad they have. People also write the bad without properly debugging the issue I think most the issues are due to user with a small percentage being faulty units.
Sent from my Xperia™ Z5 using Tapatalk

Related

What is the likelihood of a 2.2 root?

Hey guys,
I know there are plenty of people working on finding a method for root, it's difficult, not trying to ask when it's going to be or why it's taking so long. I'm just wondering if it will even be possible, given HTC doesn't ever unlock the phone themselves. I love the One X, just got it and I think it's great, but I know that I'm going to eventually want to install MIUI or CM, and since my phone has 2.2 there's basically no way to do that right now.
Reading through some of the dev/think tank threads, I've read a couple of comments alluding to the idea that it might be impossible unless HTC unlocks it, and that they might not. Seems contrary to what I've seen in the past, pretty much every phone I or my friends have had got cracked at some point. Still, if it's not going to be possible ever, I might want to return my phone and switch it out for the SGS3 or some other.
I tried to Google for unrootable android phones and couldn't find any. However the percentage of devices using ics is very small and the only ones that have root as far as I can tell all have unlocked bootloaders.
It's very difficult to remain positive but I'm trying.
gunnyman said:
I tried to Google for unrootable android phones and couldn't find any. However the percentage of devices using ics is very small and the only ones that have root as far as I can tell all have unlocked bootloaders.
It's very difficult to remain positive but I'm trying.
Click to expand...
Click to collapse
Y'all are so impatient!
Like any security, it just takes enough careful effort and determination to defeat. As great as the One X is, I have no doubt there will be enough of both to get this done. :good:
pzuraq said:
I've read a couple of comments alluding to the idea that it might be impossible unless HTC unlocks it
Click to expand...
Click to collapse
I don't have the technical expertise to really say. But just from experience, I can say that HTC has been desperately trying to lock down their phones for over 2 years (maybe longer, that is justs when I jumped into the Android game) with some pretty sophisticated safeguards, and the phones have still been rooted, often very quickly. I don't think HTC has magically gotten better at securing their devices, to the point that the phone is now impossible to root. In particular, our device was rooted (1.73 firmware) something like 3 days after it was released, even with the locked bootloader and all the security that HTC could throw on it at the time. Its just my feeling that its really doubtful that HTC can go from that point, to making the device impossible to root in the matter of a few months..
Seen this new root method here on xda, any idea if compatible with our 1X?
http://forum.xda-developers.com/showthread.php?t=1870652
from my HTC One XL using Tapatalk 2
C3RGIOSE1 said:
Seen this new root method here on xda, any idea if compatible with our 1X?
http://forum.xda-developers.com/showthread.php?t=1870652
Click to expand...
Click to collapse
Apparently not: http://forum.xda-developers.com/showthread.php?p=31435583#post31435583

[Q] Getting Ready For my T-Mobile G2

Hello Fellow XDA Members,
I am about to purchase my T-Mobile LG G2 as of tomorrow. Coming over from a Nexus 4 rooted / stock / Xposed. I am very excited about. This phone really caught my eye from beginning against the advice of my friends to wait for the Galaxy S5. This is the one I want. Of course there are tons of perks to being rooted and it's usually the first thing I do when I get a new phone. One thing I noticed about this phone is there doesn't seem to be an inclusive *ROOT* thread and I am not sure where to start other than the regular stuff; ADB enabled, drivers installed, etc. Also I know this phone is in sort of a transitional update to Android 4.0 presently (although this doesn't apply to T-Mobile as of this writing). So, I guess what I am looking for is.
1. Can someone link me a solid thread to ROOT instructions for the T-Mobile variant or is it carrier specific? Does it even matter?
2. Are there any special things I should know about like ( I recently helped a friend fix his LG Optimus due to the fact that he did not have an unlocked bootloader, rooted it and uninstalled system apps and got himself in a bootloop / soft brick) because the phone had some special *EVIL* software that would do that without first unlocking the bootloader.
3. Is there any "going back" from root on the LG G2? I mean I was reading something about root detecting, warranty voiding software. So, in other words if I get the device tomorrow and have it rooted by tomorrow night, then over the weekend I notice a weird glitch that would be covered under warranty, am I S.O.L. because I rooted it or can I flash back to stock and unroot and RMA the device?
4. Anything else I should know about that is an issue for the LG G2 during the root / romming process or otherwise.
Also I would like to thank everyone again. Going on my 4th device using only XDA as my source of info and help and still 100% HARD brick free and I plan to keep it that way. IMHO I don't see how people use phones unrooted. Thanks for the help! See you around the forums.
jcnbama said:
Hello Fellow XDA Members,
I am about to purchase my T-Mobile LG G2 as of tomorrow. Coming over from a Nexus 4 rooted / stock / Xposed. I am very excited about. This phone really caught my eye from beginning against the advice of my friends to wait for the Galaxy S5. This is the one I want. Of course there are tons of perks to being rooted and it's usually the first thing I do when I get a new phone. One thing I noticed about this phone is there doesn't seem to be an inclusive *ROOT* thread and I am not sure where to start other than the regular stuff; ADB enabled, drivers installed, etc. Also I know this phone is in sort of a transitional update to Android 4.0 presently (although this doesn't apply to T-Mobile as of this writing). So, I guess what I am looking for is.
1. Can someone link me a solid thread to ROOT instructions for the T-Mobile variant or is it carrier specific? Does it even matter?
2. Are there any special things I should know about like ( I recently helped a friend fix his LG Optimus due to the fact that he did not have an unlocked bootloader, rooted it and uninstalled system apps and got himself in a bootloop / soft brick) because the phone had some special *EVIL* software that would do that without first unlocking the bootloader.
3. Is there any "going back" from root on the LG G2? I mean I was reading something about root detecting, warranty voiding software. So, in other words if I get the device tomorrow and have it rooted by tomorrow night, then over the weekend I notice a weird glitch that would be covered under warranty, am I S.O.L. because I rooted it or can I flash back to stock and unroot and RMA the device?
4. Anything else I should know about that is an issue for the LG G2 during the root / romming process or otherwise.
Also I would like to thank everyone again. Going on my 4th device using only XDA as my source of info and help and still 100% HARD brick free and I plan to keep it that way. IMHO I don't see how people use phones unrooted. Thanks for the help! See you around the forums.
Click to expand...
Click to collapse
Awesome phone and great choice I totally agree.
Proceed with caution though, I have extensive experience with android phones and this one has turned into a flourishing source of nightmares for me and is seeming to head towards a total "paperweight" story. This all stems from rooting and recovery installation and such obviously, I am sure if you leave it untouched it is fantastic.
Just make sure you follow things EXACTLY as told. :good:
zprovo said:
Awesome phone and great choice I totally agree.
Proceed with caution though, I have extensive experience with android phones and this one has turned into a flourishing source of nightmares for me and is seeming to head towards a total "paperweight" story. This all stems from rooting and recovery installation and such obviously, I am sure if you leave it untouched it is fantastic.
Just make sure you follow things EXACTLY as told. :good:
Click to expand...
Click to collapse
Well, I'm not one to ever leave anything untouched. What has been the main issue? Finding credible threads? Roms, etc? One thing confusing for me is I've been kinda used to the T-Mobile thread or the AT&T thread. Seems like this is mostly compiled into one with the development section being separated.
Sent from my Nexus 4 using xda app-developers app
jcnbama said:
Well, I'm not one to ever leave anything untouched. What has been the main issue? Finding credible threads? Roms, etc? One thing confusing for me is I've been kinda used to the T-Mobile thread or the AT&T thread. Seems like this is mostly compiled into one with the development section being separated.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Neither am I trust me. i would never sport a locked/crippled/stock device.
There is a lot of info out there honestly. Search for Ioroot and read about that, it's pretty awesome basically an automated rooting software.
Hardest thing for me has been all kind of compatibility/driver issues. Had to use multiple computers, x64 and x86 architectures.
But there are obviously loads of people out there enjoying this phone. I am just part of the select few who had issues.
You should go for it seriously, the display is breathtaking, I have pretty large hands and this is the first time I have had one that feels just perfect in one hand which is huge to me. Can't comment much on the using of it since it only worked for about a day and a half before i wrecked it apparently .
It seems very intuitive though, the camera is really awesome too. Being a photographer I was really impressed by the menu flow and the amount of options you have. Its really amazing that they include cameras like these at the price the phone sells for.
Is it dangerous to uninstall system apps or LG apps once rooted? On my friends Optimus that's what jacked him up. If you didn't have an unlocked bootloader and you just simply rooted and removed system apps then you would get a soft brick. Is there any similar issues here?
Sent from my Nexus 4 using xda app-developers app

[Q] Rooting or not the Z5

Hi folks,
I've been reading a lot about rooting android phones and now that I have a Z5 Dual, I would like help to define if it is pertinent or not to root my Z5.
Context: I haven't bought mine through a carrier, I do not have bloatware (but Sony's).
And with recent Android releases and the M forthcoming, why should I be rooting my Z5.
I've seen posts here about people doing so with their Z5. I would like to know why also.
Is looking to use orbot and orbweb for increased anonymity a sufficient motivation?
Thanks for your advices.
Eric
The only way to root the device -as of today- is to open the unlocked bootloader of your device. This means losing permanently your DRM Keys which reduces photograph quality and access to PlayStation services (PSN app, Remote Play, among others).
If you plan on reselling your Z5 for maximum profit, losing your DRM keys will significantly lower the value of your device.
I would recommend remaining unrooted for a couple of months and wait for more refined rooting methods to emerge.
Thanks for this answer, it gives me a good "cons" - as of today - like you say.
But considering that one day a proper rooting method is found, what would be the "pros" of rooting, regarding all the options already in stock android.
What would I be getting more ?
Have a good day
Eric
Nothing if you don't what to use root access for, I would say it's for more advanced users that really want to maximise their device's potential and customise it to their likes
Lambo16 said:
Nothing if you don't what to use root access for, I would say it's for more advanced users that really want to maximise their device's potential and customise it to their likes
Click to expand...
Click to collapse
Thank you.
I understand your answer and it does make sense. I won't consider myself as an advanced user indeed, but I would like to know what I would have access to doing so.
I am interested in diving into rooting and as my readings went I understand that I can (most of the time) increase the efficency of the phone and this is what I am looking for. (i.e battery usage, reception, etc...).
However I am also interested in more secure ways to communicate and is rooting an answer to that ? I am curious.
Thanks.
EricLeRouge said:
Thank you.
I understand your answer and it does make sense. I won't consider myself as an advanced user indeed, but I would like to know what I would have access to doing so.
I am interested in diving into rooting and as my readings went I understand that I can (most of the time) increase the efficency of the phone and this is what I am looking for. (i.e battery usage, reception, etc...).
However I am also interested in more secure ways to communicate and is rooting an answer to that ? I am curious.
Thanks.
Click to expand...
Click to collapse
What do you mean more secure ways to communicate? And as another user said rooting is not worth it at the moment as you loose DRM key. I would wait for a better root exploit and also if I were you I would also wait for your device's warranty to run out.
At this point, there is not much I would root my device for apart from trying to get extra battery life. I used to have a rooted Xperia Z1 mainly so I could over clock it and install camera mods, which I don't need anymore.
tl;dr I would wait till your warranty runs out (1 year for me) and wait for a better root exploit.
Sent from my E6653 using Tapatalk
dont do it. it will void warranty... And stock is not bad i guess.
Eventually you'll be able to root with no consequences; DRM keys will be left untouched and dependant apps will perform as always. Just not yet.
Regarding the abstract benefits of rooting the Z5? Better control of OS components and a general feeling of self realization.
Specifically, after rooting, you could install the xposed framework and tinker with every minutia imaginable. My Z3 lasts 3 days with no charge. While I can barely make it through the day with my Z5. To paraphrase The Martian, I'm gonna science the **** out of it.
Sent from my SGP611 using Tapatalk
Hobbes2099 said:
Eventually you'll be able to root with no consequences; DRM keys will be left untouched and dependant apps will perform as always. Just not yet.
Regarding the abstract benefits of rooting the Z5? Better control of OS components and a general feeling of self realization.
Specifically, after rooting, you could install the xposed framework and tinker with every minutia imaginable. My Z3 lasts 3 days with no charge. While I can barely make it through the day with my Z5. To paraphrase The Martian, I'm gonna science the **** out of it.
Sent from my SGP611 using Tapatalk
Click to expand...
Click to collapse
Did this happen for the Z3?
I'm about to upgrade from a Nexus 5, I've always rooted my phones, ran a stock rom and then used xposed to customise the look.
I'm hoping I can eventually do this with the Z5, but I guess its a waiting game, will just have to get used to non root
Sent from my Nexus 5 using Tapatalk
Hobbes2099 said:
Eventually you'll be able to root with no consequences; DRM keys will be left untouched and dependant apps will perform as always. Just not yet.
Regarding the abstract benefits of rooting the Z5? Better control of OS components and a general feeling of self realization.
Specifically, after rooting, you could install the xposed framework and tinker with every minutia imaginable. My Z3 lasts 3 days with no charge. While I can barely make it through the day with my Z5. To paraphrase The Martian, I'm gonna science the **** out of it.
Sent from my SGP611 using Tapatalk
Click to expand...
Click to collapse
Thanks for your answer, it gives much more visibility on what I should be able to tinker with after root - when available in a proper form.
As for Lambo16, I was reading about being able to get more security after rooting as you get more control over kernel and so. Then I was wonderring how much of a difference it would do with actual android stock rom.
EricLeRouge said:
As for Lambo16, I was reading about being able to get more security after rooting as you get more control over kernel and so. Then I was wonderring how much of a difference it would do with actual android stock rom.
Click to expand...
Click to collapse
You still need to know what to do. I wouldn't know how to change any of that stuff.
I will probably root my device as soon as I loose warranty and when there is a better exploit.
Sent from my E6653 using Tapatalk
mrbubba999 said:
Did this happen for the Z3?
I'm about to upgrade from a Nexus 5, I've always rooted my phones, ran a stock rom and then used xposed to customise the look.
I'm hoping I can eventually do this with the Z5, but I guess its a waiting game, will just have to get used to non root
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Eventually it did. Rooting for locked bootloader was available for the Z3 by the time I got my Z3. I was able to get my Z5 much earlier this time.
Through a combination of Prime Launcher and disabling specific apps and disabling app notifications, I was was able to mask bloat ware (Xperia care, Xperia lounge, what's new, others).
Unfortunately, this superficial tweaking kept the battery untouched. So I wait. Meanwhile, I enjoy my Sony Xperia Z3, rooted, hibernated and xposed.
Sent from my D6603 using Tapatalk

Is the CAT S60 (Snapdragon 617) Rootable?

Morning all,
I have recently received my CAT S60 and I have to say, I am extremely pleased with the device out of the box. It is solid, extremely well built, battery life is amazing and camera quality is far better than the reviews led me to believe. Call quality is also the best I have ever had on any handset.
Unfortunately, I have never before owned a device without root. I have rooted most of my phones + installed a custom rom within a couple of days of opening the box. Sadly, this time round I've bought a less-popular device which is quite new and there is no existing support.
I am able to do most of the root-requiring functions with this phone (flashlight via button from locked, skip tracks with volume etc) using software workarounds, but I am already butting up against things that are pissing me off because I don't have system access, and I am so used to having it.
I've read horror stories about the lockdown function Qualcomm have applied to the 617 chips, but I now see that some phones with this chip have already been rooted (Motorola) so I am wondering, what are the chances that I will see root or a root exploit for this phone in the near future?
I'm not sure that I would sell the device over not being able to gain root, but it is really really annoying me.
I would be interested too. I couldnt even figure out how to set the s60 to downloadmode (If there is such a mode at all) to flash a custom recovery like twrp. Recoverymode is the usual volume up before poweron.
heinzherbert said:
I would be interested too. I couldnt even figure out how to set the s60 to downloadmode (If there is such a mode at all) to flash a custom recovery like twrp. Recoverymode is the usual volume up before poweron.
Click to expand...
Click to collapse
Recovery mode is volume up and power button together for 3 to 4 seconds
There is a switch in developer options to allow bootloader to be unlocked. Maybe this, combined with factory recovery menu will set us free? Flash a modified factory rom with root enabled? The stock ROM is very clean.
bandario said:
There is a switch in developer options to allow bootloader to be unlocked. Maybe this, combined with factory recovery menu will set us free? Flash a modified factory rom with root enabled? The stock ROM is very clean.
Click to expand...
Click to collapse
There is an option to unlock bootloader. It's called OEM unlocking
So, flicking this switch should unlock the bootloader???
That gives me a bit of hope for some development on this handset. None of the previous cat phones have seen any real development.
bandario said:
So, flicking this switch should unlock the bootloader???
That gives me a bit of hope for some development on this handset. None of the previous cat phones have seen any real development.
Click to expand...
Click to collapse
To be honest flicking that switch does nothing for me. I am unsure how to unlock the bootloader
On S60 bootloader is locked.
No fastboot, but you will be able to select recovery mode.
bump. I'd like to see this phone rooted.
Any progress on this or has anyone tried yet?
My SONY Z1C died on me the other day and I'd need to know if there's at least a chance to root this one.
I'm considering getting the S60 but only if I'm able to root it. An unrooted phone is barely usable to me...
Greetz and thanks in advance,
Unr3aL67
haven't tried rooting mine yet. Not felt the need to yet TBH
Mine is working pretty good without root. Only reason I'd want root honestly is to make backups, and perhaps uninstall a couple apps, but the bloatware is minimal.
Sent from my S60 using Tapatalk
Since the original question was "Is this rootable?" and lately answers have come in the form of "I haven't tried rooting mine" .... which doesn't seem much like an answer at all, to be honest .... I want to join the OP in asking this question. For those of us who have grown accustomed to the freedom and flexibility of having root access to our devices, it would be really nice to know (before making a decision to purchase) whether it is possible to obtain root on the CAT S60.
Does anyone know where to get a zip of the ROM?
After the Arstechnica review this may be my next phone. However, I really require a way to root it so that I can use iptables.
Anyone had any luck?
In response to your query we regret to inform you that we do not offer any assistance or tools to root our devices.
Click to expand...
Click to collapse
I tried contacting support about help to root, got the above back. It's a work phone so maybe it's better that I don't mess with it.
If anyone is going to root or make a custom recovery, it'll need to be without any support from the manufacturer. I mostly miss Xposed Framework for adblocking, less frequent notifications and the ability to longpress the back key to enable/disable screen rotation, the ROM itself is 99% "stock" otherwise and I have no complaints on that front.
In response to your query we regret to inform you that we do not offer any assistance or tools to root our devices.
Click to expand...
Click to collapse
This is, of course, their right, and buyer beware if you wanted a rootable phone. Still, I can't keep from being annoyed at this attitude; if I'm paying them good money for my devices, I want the freedom to do with it everything that I want, including modifying it and knowingly voiding my warranty, or even breaking it outright, if that's what makes me happy. Especially now that rooting/jailbreaking is a thing. Wanting to keep on controlling and limiting how people are able to use your product after you've sold it to them always sticks in my craw.
I guess I'll be passing on what otherwise looks like a perfect phone for me, unless some shining hero (or heroine) manages to figure out how to root a CAT S60 anyway, despite what the manufacturer might wish.
Tangib1e said:
This is, of course, their right, and buyer beware if you wanted a rootable phone. Still, I can't keep from being annoyed at this attitude; if I'm paying them good money for my devices, I want the freedom to do with it everything that I want, including modifying it and knowingly voiding my warranty, or even breaking it outright, if that's what makes me happy. Especially now that rooting/jailbreaking is a thing. Wanting to keep on controlling and limiting how people are able to use your product after you've sold it to them always sticks in my craw.
I guess I'll be passing on what otherwise looks like a perfect phone for me, unless some shining hero (or heroine) manages to figure out how to root a CAT S60 anyway, despite what the manufacturer might wish.
Click to expand...
Click to collapse
It is indeed a great phone, but the camera is sub-par. The focus takes an age compared to my Z5 Compact. I would wait for the second-generation version unless you critically need FLIR as a feature.
I've done a bit of poking around. I suspect that the bootloader could be unlocked with the commands "adb reboot bootloader" followed by "fastboot oem unlock-go".
I'm not going to do that at this point because without a custom ROM to flash there is no point in me voiding my warranty, but I believe it should be possible with USB debugging enabled, and the bootloader confirmed as unlockable.
I think this is how root will arrive on this device: by way of modifying a flashable ROM and flashing it to the device using QFIL as you would any other Qualcomm device.
The tools are all there in front of us, we just need someone with the knowledge to create that modified rom file....at this point I can't even find a factory rom to flash.
Given the recent speed and quality enhancements made available through the stock camera app, I also suspect that doing this will send us backwards to a much ****tier camera as has been the case with many sony handsets in the past.
bandario said:
There is a switch in developer options to allow bootloader to be unlocked. Maybe this, combined with factory recovery menu will set us free? Flash a modified factory rom with root enabled? The stock ROM is very clean.
Click to expand...
Click to collapse
Chuggers said:
There is an option to unlock bootloader. It's called OEM unlocking
Click to expand...
Click to collapse
bandario said:
So, flicking this switch should unlock the bootloader???
That gives me a bit of hope for some development on this handset. None of the previous cat phones have seen any real development.
Click to expand...
Click to collapse
That switch is available in a lot of devices and does nothing on a lot of them
Sent from my Lenovo A7010a48 using XDA Labs

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?

Categories

Resources