Hello everybody! I just got my SGS4 a couple of days ago... I handed my SGS3 down to my wife (running beans 18 what a monster!) and headed for the forum to see how to root and unlock this puppy... When I saw that Beans was rolling out his rom for s4 I knew I did the right thing... If i only knew... While I was tinkering with my phone a new update notification came up and without thinking I just accepted it (being used to accepting updates on my nexus 7 unrooted and never worrying about otas for my phone) as it turns out I had an MDK phone, now no more... and the more I read on the forums the more I wanna kick myself in the face for being so naive... Especially because I used to be a moto owner!
Well after my sad story I got a couple of questions... I rooted my me7 what app do I freeze to avoid otas?
And another trickier question can any knowledgeable user explain (dumbing it down a little) why some phone's boot loader cannot be unlocked ever? Just out of curiosity...
Thanks!
Sent from my SCH-I545 using XDA Premium 4 mobile app
Roland_D said:
Hello everybody! I just got my SGS4 a couple of days ago... I handed my SGS3 down to my wife (running beans 18 what a monster!) and headed for the forum to see how to root and unlock this puppy... When I saw that Beans was rolling out his rom for s4 I knew I did the right thing... If i only knew... While I was tinkering with my phone a new update notification came up and without thinking I just accepted it (being used to accepting updates on my nexus 7 unrooted and never worrying about otas for my phone) as it turns out I had an MDK phone, now no more... and the more I read on the forums the more I wanna kick myself in the face for being so naive... Especially because I used to be a moto owner!
Well after my sad story I got a couple of questions... I rooted my me7 what app do I freeze to avoid otas?
And another trickier question can any knowledgeable user explain (dumbing it down a little) why some phone's boot loader cannot be unlocked ever? Just out of curiosity...
Thanks!
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Never really did pay much attention to this me7 but I never took the update, does this mean my bootloader is unlocked???
As for having a locked bootloader its probably just a matter of time before someone finds a way to unlock it.. Let's hope
Roland_D said:
Hello everybody! I just got my SGS4 a couple of days ago... I handed my SGS3 down to my wife (running beans 18 what a monster!) and headed for the forum to see how to root and unlock this puppy... When I saw that Beans was rolling out his rom for s4 I knew I did the right thing... If i only knew... While I was tinkering with my phone a new update notification came up and without thinking I just accepted it (being used to accepting updates on my nexus 7 unrooted and never worrying about otas for my phone) as it turns out I had an MDK phone, now no more... and the more I read on the forums the more I wanna kick myself in the face for being so naive... Especially because I used to be a moto owner!
Well after my sad story I got a couple of questions... I rooted my me7 what app do I freeze to avoid otas?
And another trickier question can any knowledgeable user explain (dumbing it down a little) why some phone's boot loader cannot be unlocked ever? Just out of curiosity...
Thanks!
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
There's a lot of talk about this ME7 disappointment. So much so, that it has it's own thread for all things related to it.
That being said; freeze SDM.apk, FWupdate.apk, and I think someone mentioned Keychain.apk.
templton said:
Never really did pay much attention to this me7 but I never took the update, does this mean my bootloader is unlocked???
As for having a locked bootloader its probably just a matter of time before someone finds a way to unlock it.. Let's hope
Click to expand...
Click to collapse
Your bootloader is still locked, but there is an exploit that allows you to install ROM's and Kernels just like if it was unlocked, as long as you are on the mdk build.
Have it Jtagged back to MDK or wait for safestrap. I used safestrap on the bionic, it's an excellent app that will allow ME7 peeps to run custom roms.
Don't worry, you have options.
Sent from my SCH-I545 using xda app-developers app
I did the exact same as you my friend, I feel your pain...
jtagged?
trook said:
Have it Jtagged back to MDK or wait for safestrap. I used safestrap on the bionic, it's an excellent app that will allow ME7 peeps to run custom roms.
Don't worry, you have options.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
How is this accomplished, jtagged?
thunderbls said:
How is this accomplished, jtagged?
Click to expand...
Click to collapse
Jtagging involved taking the phone apart and jumpering two points on your board. This has been used on HTC to achieve s-off on some devices. It's very risky as you have to solder them. I have not heard of anyone doing it on the s4. Or any Sammy device.
Sent from my HTC6500LVW using Tapatalk 4
Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
I am in your same boat man... Got my phone a week ago and just carelessly did the update and found out later that day I shouldn't of... Oh well, liv and learn I guess.
There is a guy on here who said he can Jtagg the S4 ME7 back to MDK, but at the moment he is only doing it for devs in order for them to keep working towards unlocking the boot loader.
Related
im looking for a factory based holo blue themed rom for a buddy.... also looking up what else i need to do before flashing anything on it... its bone stock
Jelly Beans is the ROM to go to.
But make sure your buddies phone is already unlocked. If he didn't unlock his bootloader and install a custom recovery by now he's probably screwed. That OTA has destroyed any current working methods of getting custom recovery capabilities.
If he didn't get the OTA then have him read the Unlocking the Bootloader thread under the Original Development sub forum for the Verizon Galaxy Note 2.
Quick question. If I haven't updated am I still good to use the old unlock?
Sent from my SCH-I605 using xda premium
DJ1994 said:
Quick question. If I haven't updated am I still good to use the old unlock?
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
Yes do it asap.
He just updated yesterday! Dang. I thought samsung didnt lock down anything? Didnt with my e4gt
Sent from an Apple killing JellyBean
moparfreak426 said:
He just updated yesterday! Dang. I thought samsung didnt lock down anything? Didnt with my e4gt
Sent from an Apple killing JellyBean
Click to expand...
Click to collapse
Samsung doesn't, Verizon does. I can't tell you what their real reasons are for locking bootloaders but I believe their public statement is that they feel by locking these phones down securely they can provide a better network experience for everyone.
Yeah, bull****. It's so they can force bloatware down our throats and prevent people from using root required workarounds to things they keep locked on us. See Google Wallet vs Isis for further study.
Dang. Verizon sucks balls. Hope theres a workaround soon
Sent from an Apple killing JellyBean
If you were me, what would you do in this situation? I had to get a replacement Note 2 and the replacement thankfully came with the VRALJB software installed. I deferred the update to L4 for 5 days.
Would you just root and unlock the bootloader now the easy way, or take the L4 update and do it the harder way? Would either way be beneficial or does it not really matter?
Thanks!
Go ahead and unlock/root. You don't have to do anything further if you don't want to and you never know how difficult it would be to unlock in the future.
When I purchased mine outright it had the older software. I used the jailbreak method and that worked like a charm.
Sent from my SCH-I605 using xda app-developers app
Either way. Just do it on the current software and save a step. Same end result.
Sent from my SCH-I605 using xda premium
As others said doesn't matter. Once you flash aROM you could just flash the LL4 radio and it would be the same as the OTA.
So I guess Odin didn't fix your last one?
Sent from the dark on a Note 2
kintwofan said:
As others said doesn't matter. Once you flash aROM you could just flash the LL4 radio and it would be the same as the OTA.
So I guess Odin didn't fix your last one?
Sent from the dark on a Note 2
Click to expand...
Click to collapse
im guessing it had a emmc failure that some have reported.
Well if you were me you wouldnt think about it and just root when I got my phone I didnt even sign into google first I skipped all that and was rooted within half an hour of owning my phone...Lol so root away mang
mine came with the ota last Saturday night, i waited til Monday to root just because I've always had htc phones, had to get familiar with touchwiz. took me 10mins to root after i couldn't take all the bloatware anymore
sent from my rooted SAMSUNG GALAXY NOTE 2...
droidstyle said:
im guessing it had a emmc failure that some have reported.
Click to expand...
Click to collapse
Good idea. I thought with that failure it went black with no signs of life, but haven't read up on it. It was a strange that Odin of stock didn't fix it for him.... That's usually a guarantee unbrick
Sent from the dark on a Note 2
Yeah guys, odin didn't fix it. I consider myself somewhat of a veteran with phones, rooting, etc. This time it stumped the hell out of me. Absolutely nothing that I did worked.
I want to thank you all for the help, info, etc. I will be back in business soon!
Sent from my SCH-I605 using xda premium
WizeGuyDezignz said:
Yeah guys, odin didn't fix it. I consider myself somewhat of a veteran with phones, rooting, etc. This time it stumped the hell out of me. Absolutely nothing that I did worked.
I want to thank you all for the help, info, etc. I will be back in business soon!
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
Ya man I've seen you around, I think from the s3 also. I knew you actually knew what you were doing that's why it was so strange Odin didn't fix it. Guess with this beast of a phone we get beast of bugs
Sent from the dark on a Note 2
kintwofan said:
Ya man I've seen you around, I think from the s3 also. I knew you actually knew what you were doing that's why it was so strange Odin didn't fix it. Guess with this beast of a phone we get beast of bugs
Sent from the dark on a Note 2
Click to expand...
Click to collapse
Yup, I had the S3 for a while and was over there. Yeah man, I was chatting to the developer of the Jedi ROM and I sent him the meta folder of the ROM that I flashed for beta testing and he saw some problems. He said it was touching some partitions that it shouldn't be touching.
Anyhow, I guess I learned the hard way to be careful of testing ROMs from devs that I don't really recognize.
Time to root this bad boy and get back in business lol.
Sent from my SCH-I605 using xda premium
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
kintwofan said:
Good idea. I thought with that failure it went black with no signs of life, but haven't read up on it. It was a strange that Odin of stock didn't fix it for him.... That's usually a guarantee unbrick
Sent from the dark on a Note 2
Click to expand...
Click to collapse
normally yes...i was just throwing that out there. something was corrupted since recovery was borked.
I hate to ask this, but, I am curious as to the status of the VRUAME7 bootloader unlocking. I haven't seen any status updates since the bounty thread was closed. I'm aware root has been achieved, but seeing as I just got my S4, I'd like to experiment with different roms a bit.
Thanks.
Agree
Yeah I was wondering the same thing. If anyone has any information about this that would be awesome!
I hope soon - with over $5k in bounty, it shouldn't take long. LOL
It better be soon because I'm so sick of not having TWRP lol. 5k bounty should be more than enough!
Sent from my SCH-I545 using xda app-developers app
Agreed.
I'm debating whether or not to return this for an MDK version, because I really don't want to wait for shipping, and I've been really impressed with the S4 coming from an iPhone.
I think I'll just wait.
Ownage. said:
I'm debating whether or not to return this for an MDK version, because I really don't want to wait for shipping, and I've been really impressed with the S4 coming from an iPhone.
I think I'll just wait.
Click to expand...
Click to collapse
I came from an iPhone 5 too and tbh I'm glad I did I love this phone and I was on MDK when I got it but I updated like a dumbass. Not knowing that I had just sealed my fate for ever having custom ROMs and recovery. Oh well.
Sent from my SCH-I545 using xda app-developers app
Hi im new to the forums and pretty knew to modding phones, but i was wondering the status of this as well? and when any of the developers here on the forum think that maybe the bootloader will be unlocked? A family member passed away so i kinda of inherited the phone and i want to use it since its newer and better than mine but they had updated it to ME7 so im stuck now i guess until they can crack it Also i wanted to ask if since that might take a while, if its possible to like reset the phone to factory settings and would it put it back to MDK maybe? or is there a way to like flash it back to MDK or something so i would be able to root/unlock the bootloader then? If not its fine i guess ill have to wait. But i had cynogen on my old phone (the original droid lolz) and it was awesome so i was hoping i could put that on the S4 as well and get rid of all this crap bloatware on it too. Well thanks a lot for all your work nice to be part of the community now, so i hope they keep working on this and keep us updated ^_^
Squall516 said:
Hi im new to the forums and pretty knew to modding phones, but i was wondering the status of this as well? and when any of the developers here on the forum think that maybe the bootloader will be unlocked? A family member passed away so i kinda of inherited the phone and i want to use it since its newer and better than mine but they had updated it to ME7 so im stuck now i guess until they can crack it Also i wanted to ask if since that might take a while, if its possible to like reset the phone to factory settings and would it put it back to MDK maybe? or is there a way to like flash it back to MDK or something so i would be able to root/unlock the bootloader then? If not its fine i guess ill have to wait. But i had cynogen on my old phone (the original droid lolz) and it was awesome so i was hoping i could put that on the S4 as well and get rid of all this crap bloatware on it too. Well thanks a lot for all your work nice to be part of the community now, so i hope they keep working on this and keep us updated ^_^
Click to expand...
Click to collapse
I tried to flash it back thinking it might work but it didn't all it did was fail and leave me without a phone until I flashed ME7 again.
Sent from my SCH-I545 using xda app-developers app
blackra1n said:
I tried to flash it back thinking it might work but it didn't all it did was fail and leave me without a phone until I flashed ME7 again.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
ahh damn that sux sry that happend lol. soo much for that idea i guess lol T_T what about restoring it to factory settings like through the option on the phone itself? Will it just like reset and wipe everything but not rollback the version? Thanks for your response and with the bounty being so high and they managed to get a root for it pretty quickly i really hope they can unlock the bootloader so we can put custom roms on it soon :/
Useless thread...
Don't you think the news will be all over XDA if anyone does unlock the bootloader of the S4?
Hint: It's not because they haven't managed to unlock it yet and probably never will.
xs11e said:
Don't you think the news will be all over XDA if anyone does unlock the bootloader of the S4?
Hint: It's not because they haven't managed to unlock it yet and probably never will.
Click to expand...
Click to collapse
You do realize an exploit similar to Loki would do the same thing an unlocked bootloader can do?
Sent from my SCH-I545 using xda app-developers app
Is it possible a future update may unpatch it?
Sent from my SCH-I545 using xda app-developers app
Ownage. said:
I hate to ask this, but, I am curious as to the status of the VRUAME7 bootloader unlocking. I haven't seen any status updates since the bounty thread was closed. I'm aware root has been achieved, but seeing as I just got my S4, I'd like to experiment with different roms a bit.
Thanks.
Click to expand...
Click to collapse
In an attempt to answer the question, I've been following this thread (http://forum.xda-developers.com/showthread.php?t=2384222&page=23), but I haven't seen any updates on the last few pages.
Ownage. said:
Is it possible a future update may unpatch it?
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
It's just as likely as the oceans completely evaporating overnight.
Sent from my SCH-I545 using Tapatalk 4
The best we can hope for out of future updates is that they have a vulnerability that's easier to find than whatever's still waiting to be discovered in ME7 (if any such vulnerability is hiding there).
richii0207 said:
You do realize an exploit similar to Loki would do the same thing an unlocked bootloader can do?
Click to expand...
Click to collapse
Yes and you do realize me winning the Powerball 25 consecutive weeks is more likely?
I believe in the devs here, many are working on it and too much time has passed w/o results, I believe if some exploit were possible it would have been found by now.
Sorry to be pessimistic but I think Samsung got it locked permanently and forever and, sorry to say it, but this probably means all future devices will arrive permanently locked down. :crying:
I'd sure love to be wrong about this.....
xs11e said:
Yes and you do realize me winning the Powerball 25 consecutive weeks is more likely?
I believe in the devs here, many are working on it and too much time has passed w/o results, I believe if some exploit were possible it would have been found by now.
Sorry to be pessimistic but I think Samsung got it locked permanently and forever and, sorry to say it, but this probably means all future devices will arrive permanently locked down. :crying:
I'd sure love to be wrong about this.....
Click to expand...
Click to collapse
the motos got unlocked over 6 months after release, and that was considered by many to be completely impossible. Seeing this phone is more popular I think the chances are better, just will take time!
I put in an RMA with Negri electronics, and they're going to exchange mine for an MDK phone. Really should have done my research before updating...
So had to turn my 32 gig S3 in on insurance. Assurion said they couldn't replace it, no 32 gig models in S3 available, so they bumped me up to a brand new S4 in 32 gigs.
Kudos to them, because they offered it, I didn't ask for it, but gladly accepted.
Just wanted to say Hi, since it just got here I have some required reading to catch up on.
Blue6IX said:
So had to turn my 32 gig S3 in on insurance. Assurion said they couldn't replace it, no 32 gig models in S3 available, so they bumped me up to a brand new S4 in 32 gigs.
Kudos to them, because they offered it, I didn't ask for it, but gladly accepted.
Just wanted to say Hi, since it just got here I have some required reading to catch up on.
Click to expand...
Click to collapse
Don't take the update
Check your build number and see if you are on MDK or ME7. If you are on MDK DO NOT TAKE UPDATE TO ME7. MDK you are able to unlock bootloader and free your phone to flash roms etc.. ME7 only has root at this time and can not downgrade to MDK. If you are already on ME7 then there is a thread where Hashcode is working on safestrap but it is still a WIP.
http://forum.xda-developers.com/showthread.php?t=2381382
Thanks for the quick replies in warning.
I am charging the battery for first use, have not turned it on yet. Have no intentions of until I get a handle on everything. In the time since I posted i've been reading up on it, and have come to the conclusion already you have just warned me about.
As curious as I am to see what version of software it is running, I am also not informed enough (yet) to press that power button. I figure until I know what I want to do about handling the various choices that will either be presented to me, or are available to me (but may not know about unless I read first) that device is not doing anything more then charging its battery.
The one constant about an insurance replacement is you get to decide when it first powers on, not some store rep.
...and it looks like all my luck on this front was used up by having the 32 gig s4 offered to replace my 32 gig s3.
ME7
So looks like i'm off to dd a copy of my partitions and start by combing them with a hex editor like the rest of you looking for a solution.
So sorry to hear about the pre loaded ME7. I would keep an eye on this thread
http://forum.xda-developers.com/showthread.php?t=2441441
Still a WIP but Hashcode is making good progress.
Yea. Thanks for the link!
I am just thankful I basically got offered an upgrade without having to wait for or pay for one, still had 6 months before I came due for one on verizon.
The hardware is really what's important, it's not really feasable to upgrade the internal memory or add in ir blaster - software problems are literally just a matter of time. We'll get it eventually, the more people pitching in to help just moves the timeline more in our favor.
Travisdroidx2 said:
Check your build number and see if you are on MDK or ME7. If you are on MDK DO NOT TAKE UPDATE TO ME7. MDK you are able to unlock bootloader and free your phone to flash roms etc.. ME7 only has root at this time and can not downgrade to MDK. If you are already on ME7 then there is a thread where Hashcode is working on safestrap but it is still a WIP.
http://forum.xda-developers.com/showthread.php?t=2381382
Click to expand...
Click to collapse
So you're about to unlock the bootloader eh?? please link me the process of unlocking it...
Sent from my SCH-I545 using xda app-developers app
richii0207 said:
So you're about to unlock the bootloader eh?? please link me the process of unlocking it...
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Did you read what I posted? MDK can be unlocked not ME7. Or sorry MDK you can use a unsecured Loki kernel. Still get custom recovery and flash Roms etc...
From what i've read so far - and bear with me as i've only just started looking into anything about the S4 within the last few hours - it would seem that Loki is a process whereby the bootloader isn't unlocked, as much as bypassed.
That is correct. The bootloader is not truly unlocked like a nexus. However the Loki does allow a custom recovery to flash Roms,kernels,radios, etc.. Unlike ME7.
I don't think any 32gb phones have mdk since it was released later. I could be wrong tho
Sent from my SCH-I545 using Tapatalk 4
justinisloco said:
I don't think any 32gb phones have mdk since it was released later. I could be wrong tho
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
i've had my s4 from them for around a month, replaced due to them also not having an s3 32gb, and it came with mdk installed. stupid me should've read you couldn't just odin mdk :crying:
So....
Do you know if your insurance is still for the S3? Lets say your phone breaks and you take it in again. Are they going to give you an S3 if they have it in stock or just another S4?
dunno what would happen automatically. i am operating without insurance on the s4. long and complicated story which i wish not to relate here. good point for anyone in a similar situation who kept their policy.
iLuvMudkips said:
Do you know if your insurance is still for the S3? Lets say your phone breaks and you take it in again. Are they going to give you an S3 if they have it in stock or just another S4?
Click to expand...
Click to collapse
Asurion will cover the s4
Sent from my SCH-I545 using XDA Premium 4 mobile app
rlatjs17 said:
Asurion will cover the s4
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That is dope!
Just found this thread that confirms root for the vzw and att s5.
http://forum.xda-developers.com/showthread.php?t=2780319
Would this vulnerability work on the s4 with kitkat?
Here's info on the exploit (CVE-2014-3153):
http://seclists.org/oss-sec/2014/q2/467
http://www.reddit.com/r/netsec/comments/27fl04/another_linux_kernel_exploit_this_time_reachable/
http://www.securelist.com/en/advisories/59029
Edit @geohot has made a root method that works. All you have to do is go to http://towelroot.com and click the icon in the center to download tr.apk . Install the tr.apk after allowing installation from unknown sources. The click the button to root and the phone will reboot and you will have root. I recommend you download the updatesupersu1.99 zip and install the supersu from the common folder after extracting.
joshuabg said:
Just found this thread that confirms root for the vzw and att s5.
http://forum.xda-developers.com/showthread.php?t=2780319
Would this vulnerability work on the s4 with kitkat
Here's info on the exploit.
http://seclists.org/oss-sec/2014/q2/467
http://www.reddit.com/r/netsec/comments/27fl04/another_linux_kernel_exploit_this_time_reachable/
http://www.securelist.com/en/advisories/59029
Click to expand...
Click to collapse
That vulnerability is going to be like Cube's getroot - it's going to work on a huge number of devices.
I've been looking on how to exploit it but haven't had much time to devote to it, but apparently it's been cracked for at least one phone.
We'll have native root on the S4/S5 and who knows what else pretty soon if I'm not mistaken. Good news.
Any devs willing to work on this? @k1mu @Surge1223 @ryanbg
Sent from my SCH-I545 using Tapatalk
After reading the linked post it seems this is more a "nah-na-nah-na boo-boo" thing. It's not released, but it does give me hope that we can get a native root method like JB had.
My question is, to what end? Surge's pre - rooted functions well and is effectively stock, would this make any functionality differences vs a pre rooted rom?
Sent from Tapatalk on my rooted Verizon NC5 Galaxy S4
ffchampmt said:
After reading the linked post it seems this is more a "nah-na-nah-na boo-boo" thing. It's not released, but it does give me hope that we can get a native root method like JB had.
My question is, to what end? Surge's pre - rooted functions well and is effectively stock, would this make any functionality differences vs a pre rooted rom?
Sent from Tapatalk on my rooted Verizon NC5 Galaxy S4
Click to expand...
Click to collapse
It would be easier to do, and for example, if you dont flash SuperSu before a reboot after installing a rom, you will lose root and have to start the downgrade and upgrade process all over again. If there was a native root method all you would have to do would be to probably run a script on your computer with your phone plugged in and you will have root back. I'd imagine it would be safer and have less chance of bricking.
I actually prefer the more difficult hacks...less likely to be exploited for malware. Not saying this one will be or even could be, but easy root is not necessarily good. I'm sure jcase is shaking his finger at everyone somewhere, lol.
Sent from my SCH-I545 using Tapatalk
brizey said:
I actually prefer the more difficult hacks...less likely to be exploited for malware. Not saying this one will be or even could be, but easy root is not necessarily good. I'm sure jcase is shaking his finger at everyone somewhere, lol.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I think jcase liked that a guy got root from this on the att s5. But jcase isn't working on this because he is on break.
Sent from my OtterX running SlimKat 4.4.3 using Tapatalk
joshuabg said:
Any devs willing to work on this? @k1mu @Surge1223 @ryanbg
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
As I said above, I'm already working on it. Been on travel all week and very busy, but I do intend to try to exploit this.
k1mu said:
As I said above, I'm already working on it. Been on travel all week and very busy, but I do intend to try to exploit this.
Click to expand...
Click to collapse
I for one would love this as I have had zero ability to use any of the other ways for rooting my s4...I have had every problem trying every method so I have just given up and would love this...thanks anyone for working on it...
It's already worked out question is how the bounty is going to be paid and or split. It's not just one persons work but a bunch of contribute used info being used and who will get full credit. The bounty is what's holding up release because now yall want to pay
Sent from my SAMSUNG-SM-N900A using Tapatalk
joshuabg said:
Any devs willing to work on this? @k1mu @Surge1223 @ryanbg
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
@joshuabg @k1mu @Surge1223 @ryanbg
count me in for testing....[emoji41][emoji106]
☆Swyped From California Chrome Custom☆
Cod3L1ne said:
It's already worked out question is how the bounty is going to be paid and or split. It's not just one persons work but a bunch of contribute used info being used and who will get full credit. The bounty is what's holding up release because now yall want to pay
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
As I've said before, bounties aren't my motivation. I post what I find and make it public.
This particular vulnerability is an interesting one, with a good potential for exploit. It is not going to be easy to exploit across a large number of phones.
Cod3L1ne said:
It's already worked out question is how the bounty is going to be paid and or split. It's not just one persons work but a bunch of contribute used info being used and who will get full credit. The bounty is what's holding up release because now yall want to pay
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
Easy first one to post the root or a stock rooted image... if someone has it but another puts it up for public use, then they should get the whole bounty not one who shows it but does not share... JMO.
Sent from my SAMSUNG-SM-G900A
k1mu said:
As I've said before, bounties aren't my motivation. I post what I find and make it public.
This particular vulnerability is an interesting one, with a good potential for exploit. It is not going to be easy to exploit across a large number of phones.
Click to expand...
Click to collapse
I was told by someone on another forum that's been looking at it for the RAZR HD/M that it needs to be able to directly access memory, which as we know, can't be done in Java. Are you looking at doing it in C? Just a curiosity is all.
Would this method allow custom kernels? Or just root?
Sent from my SCH-I545 using Tapatalk
sherdog16 said:
Would this method allow custom kernels? Or just root?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Just root. Unlocked bootkoader is needed for custom kernels.
Sent from my white SM G900V on XDA Premium 4
Probably Safestrap recovery by @Hashcode just like ATT S4 and Note 3..... per my buddy @Surge1223 we might able to use Note3 Kitkat Safestrap Recovery v3.72.... time would tell.
☆Swyped From California Chrome Custom☆
I couldn't care or less if they release this root method. We already have several pre rooted ROMs with kitkat. I understand the exploit could be easier to root but I don't care how long it takes to root. I just want an unlocked bootloader. If anything we need to get more people to add to the bounty to maybe attract attention. And get as many devs working on it as possible. I am sure surge is probally getting tired of working on this for so long. It's been close to a year and nothing since loki. I bought my s4 because I thought it could be unlocked but I bought it just around the time Verizon patched loki which sucks
Sent from my SCH-I545 using XDA Free mobile app
Im just curious. Will this exploit trip the Knox counter?
Sent from my white SM G900V on XDA Premium 4
I hate to burst everyone's bubble, but this vulnerability is very difficult to exploit, and even if done correctly, will not be stable on the majority of devices. @jcase has already taken a look at this since the day it came out, and if he says it's not worth the time, it's not worth the time. Geohot may have been able to exploit it, but you only have access to a root shell for 15-20 seconds before the device becomes unstable and shuts down. SEAndroid is also an obstacle after the vulnerability has been exploited. While it's certainly possible, it's a bit far out of the ballpark to be feasible at this point in time.