Related
I am fairly new to rooting, but thanks to this great website and all your inputs I have learned so much over the past month.
I first rooted my G1 using the 1-click method which was great, but now my earpiece has blown I will be receiving a new handset next week. So I learned how to properly downgrade and install stock firmware for my old handset.
When I receive my new handset, I decided to take the plunge and root the traditional way for 2 reasons.. 1- to learn a different way and 2- its possible the security hole may be patched by then rendering the 1-click useless.
Anyway, after reading all the varying posts on how to downgrade/root/flash custom rom I am still left with a little confusion so hopefully someone can clear this up for me.
When actually rooting, I have seen methods to type various things in the telnet window, and another method to just rerun the .apk and select "protect root". What is the difference between these two methods? Do they both accomplish the same task of making a permanent root? One method actually said to download the JFreke rom to fix permissions to root, bo no other method mentioned that. Is that even necessary?
Also, I know that with Cyanogen Roms I do not really need to flash to "hard spl" if I decide to stay with cm roms, and cm recovery also allows the use of nandroid backup as well. The only other argument I have seen is that a hard spl would potentially allow someone to "unbrick" a bricked phone, but from everything I have read, most people have bricked trying to flash the hard spl.
If I am going to stay with cm roms, is there any real benefit to a hard spl other than increasing the brick chance? If I do upgrade the spl, am I correct that it would be done last, after a potential radio update (assuming my replacement handset does not come with the latest radio)?
Sorry for all the questions, and thanks in advance for your help.
This is the best guide I found.
I have done 4 phones using this method with only 2 minor differences.
1) I format the sd card using a microsd card reader instead of the phone.
2) when it says What To Do Now That You Have Root don't download any of the builds listed there, just download the latest cyan stable rom.
This is the guide hehe forgot to link
http://forum.xda-developers.com/showthread.php?t=442480
Oh and don't worry about swap or apps2sd partitions until after you root and verify that the rom is working with no problems, this will limit the number of variables in case you have troubles.
Thanks for the input.
So do you install hard spl according to that guide or do you skip that and just install the cm rom?
I love the auto apps2sd of cm roms. My phone is currently back on stock cupcake and I miss having all my apps on my 500mb ext 3 partition!
yea you need HardSPL. and use the recovery linked in the guide. Install cyan's recovery later.
This to me is the easiest step by step visual rooting process have done 3 G1 with full success. The newest G1 I had would not let me do the 1 click rooting method.
http://www.youtube.com/watch?v=xOo2V9qCauc&feature=related
maybeoneday said:
This to me is the easiest step by step visual rooting process have done 3 G1 with full success. The newest G1 I had would not let me do the 1 click rooting method.
http://www.youtube.com/watch?v=xOo2V9qCauc&feature=related
Click to expand...
Click to collapse
Yeah I figured the new handset would most likely be patched. What was the result when you tried the 1-click. Would the new phone just not let you install the 1-click apk?
One thing I might add is you can't brick your phone by flashing Hardspl. It's the "danger" spl that has the potential of bricking your phone. Just follow the traditional guide that fingerlickin provided and your good to go.
Thanks for the help!
Anytime.......
Nope sure wouldn't just kept telling me install aborted. I don't no why. It could be some kind of patch. But I went to old faithfull step by step you tube install. Its really a nice video. You can pause the video and root your phone right along with guy doing the video. he also gives you links on the side bar to all files needed in the rooting process.
oh I'm sorry, I actually have one more question.
After flashing the HardSPl, would there ever be a reason to revert back to the original g1 spl? For instance if I had to send a phone back to t-mo, would they know that I am using the hardspl if all I did was reload the dreaimg.rbh rc-29 downgrade, or does that also reflash the spl back to the original?
Yes you would want to unroot phone before sending it to Tmobile, they do not warrenty a rooted phone
Unrooting
http://forum.xda-developers.com/showthread.php?t=491350
dcorrea said:
oh I'm sorry, I actually have one more question.
After flashing the HardSPl, would there ever be a reason to revert back to the original g1 spl? For instance if I had to send a phone back to t-mo, would they know that I am using the hardspl if all I did was reload the dreaimg.rbh rc-29 downgrade, or does that also reflash the spl back to the original?
Click to expand...
Click to collapse
You shouldn't ever have to go back. T-mo would prolly never check it. Many people have sent there phones in with root access and different things installed. But if you do get paranoid and ever have to do it, just flash RC29 and it will put everything back to stock.
maybeoneday said:
Yes you would want to unroot phone before sending it to Tmobile, they do not warrenty a rooted phone
Unrooting
http://forum.xda-developers.com/showthread.php?t=491350
Click to expand...
Click to collapse
I turned my phone in with root access and custom splash screen and they didn't say anything. You don't want to make it known that you have done anything to it, but they won't check. When they are sent in they just hook it up with jtag and reflash everything.
supremeteam256 said:
You shouldn't ever have to go back. T-mo would prolly never check it. Many people have sent there phones in with root access and different things installed. But if you do get paranoid and ever have to do it, just flash RC29 and it will put everything back to stock.
Click to expand...
Click to collapse
Ok thanks that is what I figured. I actually just unrooted my phone yesterday from cyanogens rom, but I never flashed the SPL (did the 1-click thing originally), but now that I am going to do the original method I wanted to be sure.
I can't wait for my replacement phone to get here next week, because using the stock cupcake rom sux!
Anyway, thanks to everyone who gave their input and helped me learn even more about the process! You all rock!
supremeteam256 said:
I turned my phone in with root access and custom splash screen and they didn't say anything. You don't want to make it known that you have done anything to it, but they won't check. When they are sent in they just hook it up with jtag and reflash everything.
Click to expand...
Click to collapse
Really, thats music to my ears. I have often thought it would be a pain if something broke on the phone and I had to try to unroot it before I sent it in. uhhhh like a bricked phone
I work in an electronics repair company and I agree with supremeteam256 about sending your phone in rooted. Our techs don't check for tampering, they just plug it in and use the programs my department writes to test and reflash the devices. Of course our devices are much more complicated but the same NON-Communication between customer service and technicians still exist.
I think the biggest reason for this is because the techs just aren't interested in explaining the technical details to a customer service rep because all they ever get is "huh? wtf is a bootloader?"
Disclaimer:
I'm not claiming that HTC or TMobile will not check or notice that you have rooted your phone. Just illustrating that the repair techs don't want to talk to customer service anymore than you do and would rather just fix the phone and move on to the next one.
Fingerlickin said:
I work in an electronics repair company and I agree with supremeteam256 about sending your phone in rooted. Our techs don't check for tampering, they just plug it in and use the programs my department writes to test and reflash the devices. Of course our devices are much more complicated but the same NON-Communication between customer service and technicians still exist.
I think the biggest reason for this is because the techs just aren't interested in explaining the technical details to a customer service rep because all they ever get is "huh? wtf is a bootloader?"
Click to expand...
Click to collapse
Nice breakdown.
Since we got the new official 4.3 update, that means we got a new bootloader with the update right? If so, does anyone know if anyone has tried to get this unlocked even though we had no success with 4.2.2? I don't know if I can help get it done or not cause I don't have much background with actually unlocking it but I'm willing to help if possible. :fingers-crossed: Might run into problems with KNOX though.. idk.
Samsung GS4 locked bootloader. HELP
xAjCx said:
Since we got the new official 4.3 update, that means we got a new bootloader with the update right? If so, does anyone know if anyone has tried to get this unlocked even though we had no success with 4.2.2? I don't know if I can help get it done or not cause I don't have much background with actually unlocking it but I'm willing to help if possible. :fingers-crossed: Might run into problems with KNOX though.. idk.
Click to expand...
Click to collapse
Hello,
I bought an unlocked Samsung S4 Active I537 from ATT, but I use it in Canada.
I have tried to use Goomanager, TWRP manager, safestrap, quickboot; but the phone goes back to the normal bootloader.
When I try to install a ROM from my SD card (by normal bootloader) it does not do anything at all; just stays on the same screen for a minute then reboots normally.
I am guessing the bootloader isnt unlocked.
What tips you got?
Thanks!
drakul123 said:
Hello,
I bought an unlocked Samsung S4 Active I537 from ATT, but I use it in Canada.
I have tried to use Goomanager, TWRP manager, safestrap, quickboot; but the phone goes back to the normal bootloader.
When I try to install a ROM from my SD card (by normal bootloader) it does not do anything at all; just stays on the same screen for a minute then reboots normally.
I am guessing the bootloader isnt unlocked.
What tips you got?
Thanks!
Click to expand...
Click to collapse
The bootloader is still locked and currently there's nothing you can do about it. If you want to follow the progress read through this thread.
I learned that the hard way
Devo7v said:
The bootloader is still locked and currently there's nothing you can do about it. If you want to follow the progress read through this thread.
Click to expand...
Click to collapse
In advance: sorry to sound bitter; but wasn't fun how useless can be a device with a locked bootloader.
So the google apps stopped working and the whole thing is pretty much gone to hell/
IF samsung hadnt locked it so good (in a non-compliment kind of way) I could just install a new ROM and done, even better than with their weird touch wiz. But they locked it well so the phone is pretty much an average control remote in present time.
All samsung devices are locked like this one?
or that's their only garbage version ?
If that's the way they roll... no more Samsung phones ever for me.
There is a reason I stopped buying apple stuff... I dont like buying a device that is limited not because of its hardware, but because of the useless things a brand adds to make it useless. (like locking the bootloader)
Anyways... I am considering buying another phone for now.:silly:
drakul123 said:
In advance: sorry to sound bitter; but wasn't fun how useless can be a device with a locked bootloader.
So the google apps stopped working and the whole thing is pretty much gone to hell/
IF samsung hadnt locked it so good (in a non-compliment kind of way) I could just install a new ROM and done, even better than with their weird touch wiz. But they locked it well so the phone is pretty much an average control remote in present time.
All samsung devices are locked like this one?
or that's their only garbage version ?
If that's the way they roll... no more Samsung phones ever for me.
There is a reason I stopped buying apple stuff... I dont like buying a device that is limited not because of its hardware, but because of the useless things a brand adds to make it useless. (like locking the bootloader)
Anyways... I am considering buying another phone for now.:silly:
Click to expand...
Click to collapse
The device is far from useless, you can still root and flash custom ROMs, just not CM or AOSP based ROMs. I've posted all the stock ROMs and instructions on how to flash them, so if you do mess up your phone you can always start from scratch.
To answer your question about all Samsung phones, pretty much all Samsung phones from the GS3 an later that were sold by AT&T and Verizon have locked bootloaders. Nearly all the international versions as well as T-Mobile versions are sold with an unlocked bootloader, so you don't necessarily need to boycott Samsung, you just need to be more careful when purchasing a Samsung phone in the future.
Devo7v said:
The device is far from useless, you can still root and flash custom ROMs, just not CM or AOSP based ROMs. I've posted all the stock ROMs and instructions on how to flash them, so if you do mess up your phone you can always start from scratch.
To answer your question about all Samsung phones, pretty much all Samsung phones from the GS3 an later that were sold by AT&T and Verizon have locked bootloaders. Nearly all the international versions as well as T-Mobile versions are sold with an unlocked bootloader, so you don't necessarily need to boycott Samsung, you just need to be more careful when purchasing a Samsung phone in the future.
Click to expand...
Click to collapse
Hey there
Where did you post these ways of re installing all?
I saw many posts around here about reinstalling but I couldnt move on after they required the Samsung to do something through the bootloader.
Also there was a post to uninstall using Odin, but the post had missing files so couldnt do it.
Keep me posted!
drakul123 said:
Hey there
Where did you post these ways of re installing all?
I saw many posts around here about reinstalling but I couldnt move on after they required the Samsung to do something through the bootloader.
Also there was a post to uninstall using Odin, but the post had missing files so couldnt do it.
Keep me posted!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2835481
I am returning my phone back to stock so I can trade it in. I found a few threads on here that have ways to unroot but some seem questionable. Can anyone point me in the right direction to unroot an official Kit Kat updated device?
Thanks
Assuming you have supersu, uninstall all of your apps that have root access (for safestrap, busybox, etc make sure to uninstall the in-app stuff first), i would reboot here but that may not be necessary...then open up supersu and choose "full unroot". Then factory reset and double check status is official ☺
If you get a custom screen after that try rerooting then full unroot with supersu again
Edit: I stand corrected - flashing NC2 with Odin is easiest
Yeah I have su. So before I do this should I restore my stock rom I have backed up via safestrap? I am currently running dynamic kat 5.0
You can also reinstall factory firmware with Odin, then factory reset.
http://forum.xda-developers.com/showthread.php?t=2703006
Awesome, I will give that a try when my upgrade is closer. Thank you
440bro said:
You can also reinstall factory firmware with Odin, then factory reset.
http://forum.xda-developers.com/showthread.php?t=2703006
Click to expand...
Click to collapse
konaman said:
Awesome, I will give that a try when my upgrade is closer. Thank you
Click to expand...
Click to collapse
Yea @440bro 's suggestion is way easier since Odin removes all of that! unroot with SuperSU does work but it's a long way around for just returning to stock
please help
440bro said:
You can also reinstall factory firmware with Odin, then factory reset.
http://forum.xda-developers.com/showthread.php?t=2703006[/QUOTE
]I have similar situation except I have an iMac running OS X Mavericks. Could anyone tell me if it's possible to unroot my AT&T Note 3 to stock ROM to sell? I installed stock custom rom using safestrap but when I reboot or turn device on, I get a safestrap enabled cartoon thing asking to continue or recover. I don't think people will want to buy phone if they saw this sick looking robot thing when they switch it on. Please help...Phone too big for my hands. Thank you
Click to expand...
Click to collapse
braddy66 said:
440bro said:
You can also reinstall factory firmware with Odin, then factory reset.
http://forum.xda-developers.com/showthread.php?t=2703006[/QUOTE
]I have similar situation except I have an iMac running OS X Mavericks. Could anyone tell me if it's possible to unroot my AT&T Note 3 to stock ROM to sell? I installed stock custom rom using safestrap but when I reboot or turn device on, I get a safestrap enabled cartoon thing asking to continue or recover. I don't think people will want to buy phone if they saw this sick looking robot thing when they switch it on. Please help...Phone too big for my hands. Thank you
Click to expand...
Click to collapse
Did you backup stock rom before you flashed the custom rom in safestrap? if yes, reflash your backup in safestrap then the steps in post #2 should work. If no, I'm really not sure how going through that unroot process with SuperSU while still on a custom rom would work out...Odin is much easier and more reliable so if there's any way you can get to a PC you might want to go that route.
Also if you're selling online you might find some people who do want to buy a rooted Note 3...I sold a phone on swappa a few months ago and there were people looking specifically for rooted phones. The 'cartoon thing' is safestrap and is exactly what you want to see when you turn on a rooted AT&T Note 3
Click to expand...
Click to collapse
thank you
braddy66 said:
440bro said:
You can also reinstall factory firmware with Odin, then factory reset.
http://forum.xda-developers.com/showthread.php?t=2703006[/QUOTE
]I have similar situation except I have an iMac running OS X Mavericks. Could anyone tell me if it's possible to unroot my AT&T Note 3 to stock ROM to sell? I installed stock custom rom using safestrap but when I reboot or turn device on, I get a safestrap enabled cartoon thing asking to continue or recover. I don't think people will want to buy phone if they saw this sick looking robot thing when they switch it on. Please help...Phone too big for my hands. Thank you
Click to expand...
Click to collapse
brisinger08 said:
braddy66 said:
Did you backup stock rom before you flashed the custom rom in safestrap? if yes, reflash your backup in safestrap then the steps in post #2 should work. If no, I'm really not sure how going through that unroot process with SuperSU while still on a custom rom would work out...Odin is much easier and more reliable so if there's any way you can get to a PC you might want to go that route.
Also if you're selling online you might find some people who do want to buy a rooted Note 3...I sold a phone on swappa a few months ago and there were people looking specifically for rooted phones. The 'cartoon thing' is safestrap and is exactly what you want to see when you turn on a rooted AT&T Note 3
Click to expand...
Click to collapse
Thanks for your feel good message...made my day. I thought I backed up stock rom however being an obviously root virgin...When I went to factory reset, everything was gone except for my ugly cartoony friend. Luckily I am able to read in small doses so I was able to do whatever it was I did to get her running factory...still rooted and unlocked. When you mentioned that people on swappa might be interested in a rooted device WITH my lonely friend at startup? I felt all fuzzy. I will post an ad on swappa later today in your honor my mysterious phoneguardian angel. Thanks again.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Looks like I'll need to go the long route to unroot. I have a Mac book and I can't find Odin for it
I just bought a G4 yesterday, so I'm still learning all about what is possible with it. It has the latest stock firmware, ZV9 / Marshmallow, installed.
I'm wondering if it's rootable, and if so if somebody can point me in the right direction.
I've seen people mention that the bootloader is still locked, and honestly I'm not real sure what that means.
So is there any way to root the Sprint G4? Possibly if I downgrade to an earlier firmware?
Thank you!
You can downgrade and root that way, and then just flash a marshmallow rom. So far it seems there won't be a root option for MM on this phone.
Sent from my LGLS991 using XDA Free mobile app
Dustin7892 said:
You can downgrade and root that way, and then just flash a marshmallow rom. So far it seems there won't be a root option for MM on this phone.
Sent from my LGLS991 using XDA Free mobile app
Click to expand...
Click to collapse
That would work if we had a marshmallow rom lol...was trying to get the 2 devs that's done roms for sprint to help port some over but nothing
Yeah it feels like even though this phone is pretty new... Dev for this phone is pretty much dead... Kind of sucks. Root is so useful...
Is there a safe way to downgrade to ZV6 and then root that? Can I just follow this guide? http://forum.xda-developers.com/g4/orig-development/root-tmo-vzw-intl-variants-soon-root-lg-t3164765
imekul said:
Is there a safe way to downgrade to ZV6 and then root that? Can I just follow this guide? http://forum.xda-developers.com/g4/orig-development/root-tmo-vzw-intl-variants-soon-root-lg-t3164765
Click to expand...
Click to collapse
Yes, after downgrading you can follow that guide and use the ZV6 root. You will probably have to factory reset after downgrading as it probably won't boot initially.
Okay, thank you! So I guess right now it's pretty much a choice of rooted Lollipop (and Lollipop ROMs) or unrooted Marshmallow?
imekul said:
Okay, thank you! So I guess right now it's pretty much a choice of rooted Lollipop (and Lollipop ROMs) or unrooted Marshmallow?
Click to expand...
Click to collapse
Yes.
Thanks!
Just wanted to ask real quick, the guide (link above) includes the downgrade?
I've been looking around and waiting, but unfortunately I don't think I can wait for the 6.0 root, and I'm even more disappointed I can't help in any way possible due do lack of experience, but back to topic; could you link the downgrade tutorial?
Also, since you've been on zv9, when you go back to zv6 can you reply back with how the battery life handles?
So far I've been getting poor times and I've heard that the battery should preform somewhere for 6+ even on heavy usage.
xCasper said:
Just wanted to ask real quick, the guide (link above) includes the downgrade?
I've been looking around and waiting, but unfortunately I don't think I can wait for the 6.0 root, and I'm even more disappointed I can't help in any way possible due do lack of experience, but back to topic; could you link the downgrade tutorial?
Also, since you've been on zv9, when you go back to zv6 can you reply back with how the battery life handles?
So far I've been getting poor times and I've heard that the battery should preform somewhere for 6+ even on heavy usage.
Click to expand...
Click to collapse
Here's what I found on the downgrade.
http://forum.xda-developers.com/sprint-g4/development/howto-downgrade-to-zv6-upgrade-to-t3265976
I'm assuming if a root method is found for the other US carriers, Sprint variants would follow suit very shortly after?
misteroh said:
I'm assuming if a root method is found for the other US carriers, Sprint variants would follow suit very shortly after?
Click to expand...
Click to collapse
As far as I know, they already had root methods.
Sprints issue was the fact their bootloader wasn't unlocked and seemingly didn't have plans to be.
-=This is in no way intended to be a root method I am suggesting.=-
So, before I was tuning into this thread, I had found this (screenshots) in the playstore, now I haven't tested it and don't plan to, but it did catch my interest.
I just wanted to know if anyone has heard / tried this, and if so, how did it go?
Again, I can't stress enough that this is not me answering the question of "Is MM rootable on Sprint LG G4. " I do not know what will happen to your device if you do try it.
Also, even though it lists a method, you can see the Sprint variation of this phone is not in the device list.
Hi All,
I see the development kernel is now out, but we still have the locked boot loader problem. Has there ever been a time that AT&T has allowed access/unlocked the boot loader before? Even if we do gain root access at this point (with the S8 coming out in a few months), would we get any custom ROM development or other things that are out for other phones?
I guess, at this point, what is the best case scenario?
Thanks!
WWWhaat said:
Hi All,
I see the development kernel is now out, but we still have the locked boot loader problem. Has there ever been a time that AT&T has allowed access/unlocked the boot loader before? Even if we do gain root access at this point (with the S8 coming out in a few months), would we get any custom ROM development or other things that are out for other phones?
I guess, at this point, what is the best case scenario?
Thanks!
Click to expand...
Click to collapse
Because of the obscurity of the S6 Active, along with the very few number of developers attempting a root (I am not actually sure if anyone is trying anymore.), the best case scenario is we might get a rudimentary root method for anything higher than 5.0.2. Marshmallow is looking even more bleak. As for a custom ROM, it is highly unlikely, if at all, that the bootloader will ever be unlocked.
FevenKitsune said:
Because of the obscurity of the S6 Active, along with the very few number of developers attempting a root (I am not actually sure if anyone is trying anymore.), the best case scenario is we might get a rudimentary root method for anything higher than 5.0.2. Marshmallow is looking even more bleak. As for a custom ROM, it is highly unlikely, if at all, that the bootloader will ever be unlocked.
Click to expand...
Click to collapse
Thanks for the response....maybe we can get ahold of someone who was trying to crack it and ask them to possibly to try again with the released kernel?
Or is there somewhere / someone we can reach out to... I dont know how to dev find lol.
I am still pledging 50$, plus the other people pledging should encourage some people.. I just dont want to lose hope. This is such a great phone still..
DefiledL said:
Thanks for the response....maybe we can get ahold of someone who was trying to crack it and ask them to possibly to try again with the released kernel?
Or is there somewhere / someone we can reach out to... I dont know how to dev find lol.
I am still pledging 50$, plus the other people pledging should encourage some people.. I just dont want to lose hope. This is such a great phone still..
Click to expand...
Click to collapse
I could be wrong, but I don't think the released kernel means much. We've already had released kernels for 5.1.1, and as far as I know there's been no root for 5.1.1.
FevenKitsune said:
I could be wrong, but I don't think the released kernel means much. We've already had released kernels for 5.1.1, and as far as I know there's been no root for 5.1.1.
Click to expand...
Click to collapse
yeaa...maybe we need to spam at&t for them to unlock it lol..
DefiledL said:
yeaa...maybe we need to spam at&t for them to unlock it lol..
Click to expand...
Click to collapse
AT&T probably has received death threats to have some of their devices unlocked. I can assure you AT&T will just give you their whole PR crap about how "it's unsafe to do and can damage your device" as if we don't already know that. Also from a legal standpoint, owning a carrier device doesn't mean you actually own the device, you just are "borrowing" it. It's in the small text of the crap they make you sign. They aren't legally obliged to do anything.
FevenKitsune said:
AT&T probably has received death threats to have some of their devices unlocked. I can assure you AT&T will just give you their whole PR crap about how "it's unsafe to do and can damage your device" as if we don't already know that. Also from a legal standpoint, owning a carrier device doesn't mean you actually own the device, you just are "borrowing" it. It's in the small text of the crap they make you sign. They aren't legally obliged to do anything.
Click to expand...
Click to collapse
Yea... sadly :/ Wish the laws were a bit different.
DefiledL said:
Yea... sadly :/ Wish the laws were a bit different.
Click to expand...
Click to collapse
The best solution is to get an unlocked phone from the start. There's not many phones like the S6 Active, but any phone with a case and screen protector gets pretty damn close.
This sucks I've been searching for weeks on methods to root it everybody seems to think it can be rooted but it can't I'm frustrated at the thought of att locking the bootloader anybody got any good news yet about root for the S6A
Diesel Guy said:
This sucks I've been searching for weeks on methods to root it everybody seems to think it can be rooted but it can't I'm frustrated at the thought of att locking the bootloader anybody got any good news yet about root for the S6A
Click to expand...
Click to collapse
Until they can figure out how to change the status of SELinux to allow for root via. Dirty Cow, there is no current hope for a root method. Not unless a much more experienced developer comes on the scene. However, from what I've seen, even the standard S6 has hardly had much luck with a root method.
WWWhaat said:
Hi All,
I see the development kernel is now out, but we still have the locked boot loader problem. Has there ever been a time that AT&T has allowed access/unlocked the boot loader before?
Thanks!
Click to expand...
Click to collapse
Yes. The at&t variants of the galaxy s2 and galaxy s3 have factory unlocked bootloaders. When the s4 came out, at&t decided then to start locking bootloaders. However, the early s4 firmware (the MDL firmware) had a flaw in the bootloader which allowed a tool called "Loki doki" to bypass the lock and boot custom ROM and kernels. Later firmware updates fixed this hole.
WWWhaat said:
Hi All,
I see the development kernel is now out, but we still have the locked boot loader problem. Has there ever been a time that AT&T has allowed access/unlocked the boot loader before? Even if we do gain root access at this point (with the S8 coming out in a few months), would we get any custom ROM development or other things that are out for other phones?
I guess, at this point, what is the best case scenario?
Thanks!
Click to expand...
Click to collapse
I posted Crom.apk link in another thread...i am using the J3 running MM 6.0.1....so it should be compatible ...its under the bounty page. Unlocks bootloaders for samsung devices
Anyone come up with a solution to get root access?