Related
I've read elsewhere that the new S4 bootloader has locked.
Can someone verify this?
How does it affect the usage of the device?(i.e CM,AOSP etc)
So far only on the AT&T and Verizon models.
They'll have root for now but no custom recovery/roms.
ChronoReverse said:
So far only on the AT&T and Verizon models.
They'll have root for now but no custom recovery/roms.
Click to expand...
Click to collapse
I just want to know a bit more about it...I've got the I9505 model,which is definately not AT&T or Verizon.
But it's not confirmed yet,isn't it?
hunhool said:
I just want to know a bit more about it...I've got the I9505 model,which is definately not AT&T or Verizon.
Click to expand...
Click to collapse
The AT&T and Verizon bootloader is locked, which will restrict flashing roms and kernels but not root for those devices until the bootloader is unlocked. The international versions seem to be not locked so that does apply to all the octa versions.
Sent from my SPH-L720 using xda app-developers app
short story: the international isn't the carriers are
effect on dev gives them a extra work to do
inlineboy said:
The AT&T and Verizon bootloader is locked, which will restrict flashing roms and kernels but not root for those devices until the bootloader is unlocked. The international versions seem to be not locked so that does apply to all the octa versions.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Is there any simple way to find out whether is locked or not?
hunhool said:
Is there any simple way to find out whether is locked or not?
Click to expand...
Click to collapse
There isn't sadly. People were saying if you boot into download mode and it said Write Protection: Enabled that the bootloader was locked, as is the case for atnt and verizon, but the it says the same thing for sprint and our bootloader does not seem to be locked- it's a bit more complicated to actually know and I don't have the tech knowledge to explain it as well as someone else probably could. Probably should find others with your exact phone in the forum and just read what they have said cause this has been a huge topic over the last few days that everyone has been asking.
Sent from my SPH-L720 using xda app-developers app
Canadians are starting to get their phones shipped and in hand. What is required to determine if the bootloader is locked? Anything in download or recovery mode? Does an attempt to use Odin need to be made? If so, just connecting to it or actually flashing something?
Any help would be great so I can pass it on and ask others. I'd like to figure it out before my phone ships and to also save others from ordering if it is locked. Thanks.
tietherope said:
Canadians are starting to get their phones shipped and in hand. What is required to determine if the bootloader is locked? Anything in download or recovery mode? Does an attempt to use Odin need to be made? If so, just connecting to it or actually flashing something?
Any help would be great so I can pass it on and ask others. I'd like to figure it out before my phone ships and to also save others from ordering if it is locked. Thanks.
Click to expand...
Click to collapse
If you try CF-Auto-Root (http://forum.xda-developers.com/showthread.php?t=2219803) it'll simply fail and do nothing if your bootloader is locked.
The real way is to goto Odin Mode and look for "CSB-OEM_CONFIG_LSB: 0x30" which means you're locked.
[edit]It may work even with this line[/edit]
ChronoReverse said:
If you try CF-Auto-Root (http://forum.xda-developers.com/showthread.php?t=2219803) it'll simply fail and do nothing if your bootloader is locked.
The real way is to goto Odin Mode and look for "CSB-OEM_CONFIG_LSB: 0x30" which means you're locked.
Click to expand...
Click to collapse
so that means,if CF-root works on my i9505 then the bootloader isn't locked?
EDIT:
CF-auto-root(http://forum.xda-developers.com/showthread.php?t=2219803) works on my phone,however if I go to download mode I've got this line there "CSB-OEM_CONFIG_LSB: 0x30".
Any idea??
hunhool said:
so that means,if CF-root works on my i9505 then the bootloader isn't locked?
EDIT:
CF-auto-root(http://forum.xda-developers.com/showthread.php?t=2219803) works on my phone,however if I go to download mode I've got this line there "CSB-OEM_CONFIG_LSB: 0x30".
Any idea??
Click to expand...
Click to collapse
You ran it and it really worked? Did you test to see if root was actually enabled? If your phone is locked, root isn't available after trying CF-Auto-root
ChronoReverse said:
You ran it and it really worked? Did you test to see if root was actually enabled? If your phone is locked, root isn't available after trying CF-Auto-root
Click to expand...
Click to collapse
well,titanium backup,root explorer,setcpu,terminal emulator needs root privileges and all of them working fine.
I've got superSU app as well.
So,yes my phone has definately rooted.
(how can I make a screen shot with S4?)I'll prove it,if you want:silly:
here you go:
hunhool said:
well,titanium backup,root explorer,setcpu,terminal emulator needs root privileges and all of them working fine.
I've got superSU app as well.
So,yes my phone has definately rooted.
(how can I make a screen shot with S4?)I'll prove it,if you want:silly:
Click to expand...
Click to collapse
If you have an i9505 then you're definitely unlocked anyway =)
I thought you were the thread OP who has the i337m
hunhool said:
well,titanium backup,root explorer,setcpu,terminal emulator needs root privileges and all of them working fine.
I've got superSU app as well.
So,yes my phone has definately rooted.
(how can I make a screen shot with S4?)I'll prove it,if you want:silly:
Click to expand...
Click to collapse
What carrier s4 you have?
Sent from my GT-N7105 using Tapatalk 2
turilo said:
What carrier s4 you have?
Sent from my GT-N7105 using Tapatalk 2
Click to expand...
Click to collapse
I9505 sim free,on EE network.
hunhool said:
I9505 sim free,on EE network.
Click to expand...
Click to collapse
Ah OK that's non lte also
Sent from my GT-N7105 using Tapatalk 2
turilo said:
Ah OK that's non lte also
Sent from my GT-N7105 using Tapatalk 2
Click to expand...
Click to collapse
...qualcomm lte version
ChronoReverse said:
If you try CF-Auto-Root (http://forum.xda-developers.com/showthread.php?t=2219803) it'll simply fail and do nothing if your bootloader is locked.
The real way is to goto Odin Mode and look for "CSB-OEM_CONFIG_LSB: 0x30" which means you're locked.
Click to expand...
Click to collapse
I can unfortunately officially confirm that the "CSB...:0x30" is present on Rogers/Fido GS4's.
mickliq said:
I can unfortunately officially confirm that the "CSB...:0x30" is present on Rogers/Fido GS4's.
Click to expand...
Click to collapse
Actually I should recant that. Someone else had that line AND he got root.
So you have to try CF-Auto-Root and see if it does anything.
CSB-OEM_CONFIG_LSB: 0x30 does not mean that the bootloader is locked, in fact the lock status does not appear anywhere in the download mode and is defined by a gpio state triggered from a Qfuse. None of which are visible through any interfaces available to the user.
Keep in mind however that even though your bootloader may be unlocked, the bootloader itself PBL, SBL... needs to be signed, otherwise it will not be overwritten. The kernel's signature however will not be verified by an unlocked bootloader. So far all consumer GT-I9505 appear to feature an unlocked bootloader, with the exception of few engineering and review devices.
hunhool said:
...qualcomm lte version
Click to expand...
Click to collapse
Will that model work in Canada with rogers or bell in lte?
Sent from my GT-N7105 using Tapatalk 2
This person says that they use CF-Auto Root on their I337M.
mine worked too
tietherope said:
This person says that they use CF-Auto Root on their I337M.
Click to expand...
Click to collapse
I have s4 i337m and I just tried CF-Auto-Root-jfltecan-jfltevl-sghi337m and it worked. by the way I am on mg1 4.2.2
and in download mode it was written "Write Protection Enabled".
Is there any word on whether or not the bootloader is encrypted? If so does anyone have any idea on what the chances of it being unlocked is, as this is the only thing stopping me from buying this phone.
Sent from my SCH-I535 using Tapatalk 4
I suspect we will end up with loki. At least i hope so.
Sent from my LG-D800 using Tapatalk 4
I'm ready for the complete package so I can start flashing
Sent from my VS980 4G using Tapatalk 4
bri315317 said:
I suspect we will end up with loki. At least i hope so.
Sent from my LG-D800 using Tapatalk 4
Click to expand...
Click to collapse
I'm unfamiliar with loki, what is that?
Sent from my SCH-I535 using Tapatalk 4
soapinmouth said:
I'm unfamiliar with loki, what is that?
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Basically it is an exploit to bypass the bootloader to flash roms and kernels. DJRBLISS found it for the S4 and it is working with the G pro. Read more about it here
Other options would be Hash's safety strap or if they can figure out flash gordon for roms. But I still hope for a full unlock sometime...
Is there a way to check if the bootloader is locked? I'm getting a T-mobile version and am curious if they have it locked as well.
bri315317 said:
I suspect we will end up with loki. At least i hope so.
Sent from my LG-D800 using Tapatalk 4
Click to expand...
Click to collapse
Loki is old. Most manufactures stopped using as soon as Dan Bliss posted how he exploited it.
I am fairly confident this is not going to be Loki. I hope I am wrong but...
Its easy to test if you are rooted.
Pull a system dump, mod the boot.img (Decompile it, maybe just put a simple line in the default.prop then recompile), then run it through loki. After loki just DD it back in place.
If you phone boots then its loki! And I run to AT&T to buy one no questions asked...
If your phone doesnt boot... you bricked it but did so for a noble cause! And for that I would salute you!
All of the above is true and accurate... But with a grain of angry sarcasm... Im pretty sure this is not going to be Loki. If so it would have recovery and ROMS by now.
joshuadjohnson22 said:
Basically it is an exploit to bypass the bootloader to flash roms and kernels. DJRBLISS found it for the S4 and it is working with the G pro. Read more about it here
Other options would be Hash's safety strap or if they can figure out flash gordon for roms. But I still hope for a full unlock sometime...
Click to expand...
Click to collapse
You mean WAS working with the S4...
Samsung changed the method 100% and no longer works with ANY Samsung device that is up to date.
Sorry guys, not trying to be a downer... I really want this phone... Very angry with the games carriers play.
scrosler said:
Loki is old. Most manufactures stopped using as soon as Dan Bliss posted how he exploited it.
I am fairly confident this is not going to be Loki. I hope I am wrong but...
Its easy to test if you are rooted.
Pull a system dump, mod the boot.img (Decompile it, maybe just put a simple line in the default.prop then recompile), then run it through loki. After loki just DD it back in place.
If you phone boots then its loki! And I run to AT&T to buy one no questions asked...
If your phone doesnt boot... you bricked it but did so for a noble cause! And for that I would salute you!
All of the above is true and accurate... But with a grain of angry sarcasm... Im pretty sure this is not going to be Loki. If so it would have recovery and ROMS by now.
Click to expand...
Click to collapse
I think it's aboot.img that gets modded for Loki on this phone.
Sent from my LG-D800 using Tapatalk 4
djkinetic said:
I think it's aboot.img that gets modded for Loki on this phone.
Sent from my LG-D800 using Tapatalk 4
Click to expand...
Click to collapse
No, thats not correct.
When the system boots, it looks at aboot and verifies its signed. Then from there, it verifies that boot.img is signed, then on...
aboot is just first in the chain, and if hacked appropriately, would eliminate the need for any and all loki methods...
However, hacking the aboot is not something I recommend anyone trying to do... Unless of course they have done it before...
Didint you just brick your phone because of a hack attempt at aboot?
scrosler said:
No, thats not correct.
When the system boots, it looks at aboot and verifies its signed. Then from there, it verifies that boot.img is signed, then on...
aboot is just first in the chain, and if hacked appropriately, would eliminate the need for any and all loki methods...
However, hacking the aboot is not something I recomend anyone trying to do...
Didint you just brick your phone because of a hack attempt at aboot?
Click to expand...
Click to collapse
Ah ic
Sent from my GT-I9505G using Tapatalk 4
---------- Post added at 12:43 PM ---------- Previous post was at 12:43 PM ----------
scrosler said:
No, thats not correct.
When the system boots, it looks at aboot and verifies its signed. Then from there, it verifies that boot.img is signed, then on...
aboot is just first in the chain, and if hacked appropriately, would eliminate the need for any and all loki methods...
However, hacking the aboot is not something I recommend anyone trying to do... Unless of course they have done it before...
Didint you just brick your phone because of a hack attempt at aboot?
Click to expand...
Click to collapse
Yup the devs on irc have me testing various aboots
Sent from my GT-I9505G using Tapatalk 4
djkinetic said:
Ah ic
Sent from my GT-I9505G using Tapatalk 4
Click to expand...
Click to collapse
Trust me man, I played this game on Samsung... Then quit it and went back to HTC.
With Samsung they dropped the loki method of kernels. So now, they have yet to have an unlocked bootloader...
I can only SUSPECT this phone is using the same method the Samsungs are now using...
Otherwise we would have lokied the ***** and we would all be crack flashing :highfive: :angel:
djkinetic said:
Yup the devs on irc have me testing various aboots
Sent from my GT-I9505G using Tapatalk 4
Click to expand...
Click to collapse
Yeah, they are going one route to unlock... Which would be the most optimal, yet most risky...
Although on other Samsung devices they closed this loop hold...
Unless someone has an aboot that has been leaked by LG for the device that does not have the checks involved this may prove as impossible as it does for the Samsung devices..
I hope I am wrong...
scrosler said:
Yeah, they are going one route to unlock... Which would be the most optimal, yet most risky...
Although on other Samsung devices they closed this loop hold...
Unless someone has an aboot that has been leaked by LG for the device that does not have the checks involved this may prove as impossible as it does for the Samsung devices..
I hope I am wrong...
Click to expand...
Click to collapse
Yeah... swapping for an HTC One is looking better and better as time goes on. I know it's only been a few days since launch, FYI.
DeaconBoogie said:
Yeah... swapping for an HTC One is looking better and better as time goes on. I know it's only been a few days since launch, FYI.
Click to expand...
Click to collapse
Sad isnt it?
I will only be buying international phones going forward.
No more carrier subsidies for me :good:
scrosler said:
Sad isnt it?
I will only be buying international phones going forward.
No more carrier subsidies for me :good:
Click to expand...
Click to collapse
My problem is that VZW is the only LTE carrier in my area that doesn't completely suck. Their coverage is just too good...
DeaconBoogie said:
My problem is that VZW is the only LTE carrier in my area that doesn't completely suck. Their coverage is just too good...
Click to expand...
Click to collapse
Yeah, AT&T Finally got LTE turned on a couple weeks ago.
I said, If I have to I will go back to Sprint 2G to have an unlocked phone.
And if you buy Int phones you cant run them on Verizon.
THEY rule they air
scrosler said:
Yeah, they are going one route to unlock... Which would be the most optimal, yet most risky...
Although on other Samsung devices they closed this loop hold...
Unless someone has an aboot that has been leaked by LG for the device that does not have the checks involved this may prove as impossible as it does for the Samsung devices..
I hope I am wrong...
Click to expand...
Click to collapse
Yea hope so too, but its a shame that its locked down, the device itself is awesome, Sadly ill prolly get a nexus 5 for my crack flash addiction lol
scrosler said:
Yeah, AT&T Finally got LTE turned on a couple weeks ago.
I said, If I have to I will go back to Sprint 2G to have an unlocked phone.
And if you buy Int phones you cant run them on Verizon.
THEY rule they air
Click to expand...
Click to collapse
Think we'll have a definitive answer in a week as to the prospects of unlocking?
DeaconBoogie said:
Think we'll have a definitive answer in a week as to the prospects of unlocking?
Click to expand...
Click to collapse
Once again... On pure speculation...
Impossible to know!
I just know the S4 has been re-locked for a couple months and no one has made any posted progress. I am "assuming" this phone uses the same method as Samsung. LG has always tended to play "follow Samsung."
So with that said... I would be watching the S4 forums for an answer...
It appears that real soon we may have root for locked bootloader devices running Lollipop.
Read here for more info.
zoid_99 said:
It appears that real soon we may have root for locked bootloader devices running Lollipop.
Read here for more info.
Click to expand...
Click to collapse
One thing has nothing to do with the other.
Lollipop requires some changes to have root access and that was only possible with a modified kernel.
Now Chainfire managed to root the Lollipop without a custom kernel.
But installing ZIP file of root need a custom recovery , so still need to have the device with unlocked bootloader .
I've done the root Lollipop using this new root method of Chainfire.
Junior Passos said:
One thing has nothing to do with the other.
Lollipop requires some changes to have root access and that was only possible with a modified kernel.
Now Chainfire managed to root the Lollipop without a custom kernel.
But installing ZIP file of root need a custom recovery , so still need to have the device with unlocked bootloader .
I've done the root Lollipop using this new root method of Chainfire.
Click to expand...
Click to collapse
If you read the article it appears that there is no need to install a zip in a custom recovery to get root with this method.
" the need for ramdisk modifications was concerning for many users of bootloader-locked devices for which no unlock is available (yes, they do unfortunately exist). The answer to their prayers is now here"
zoid_99 said:
If you read the article it appears that there is no need to install a zip in a custom recovery to get root with this method.
" the need for ramdisk modifications was concerning for many users of bootloader-locked devices for which no unlock is available (yes, they do unfortunately exist). The answer to their prayers is now here"
Click to expand...
Click to collapse
Hmmm interesting.
Then the process should be with CF-Auto-Root .
I used one of those before when I first root in Lollipop.
But thought the command "mfastboot boot cf-auto-root.img" only work with unlocked bootloader and not the locked too.
Amazing.
Me excite!
You can only flash signed zips, so this only makes it easier because you dont need a device specific package for rooting
godutch said:
You can only flash signed zips, so this only makes it easier because you dont need a device specific package for rooting
Click to expand...
Click to collapse
Translated... Will it work on moto x vzw?
GatorsUF said:
Translated... Will it work on moto x vzw?
Click to expand...
Click to collapse
No.
cam30era said:
No.
Click to expand...
Click to collapse
OF course
This revelation means that Android 5.0 users*no longer need to run a modified kernel to gain root access via SuperSU (or other root solutions). While not a huge problem on Nexus devices with unlockable bootloaders, the need for ramdisk modifications was concerning for many users of bootloader-locked devices for which no unlock is available (yes, they do unfortunately exist). The answer to their prayers is now here, and we can present an exclusive explanation of the changes needed. At least for now (until/unless Google patch this), it is possible to gain root access and then install and use SuperSU on a stock Android 5.0 device, without any kernel ramdisk tweaking. The reason for this is the need for SuperSU to run a service as root, to allow for unconstrained root access on SELinux-protected devices.
Bump. We need root. Can't believe nobody seems to be working on a workaround. No safestrap? No kexec? No root? What happened to our glorious hackers?
neh4pres said:
Bump. We need root. Can't believe nobody seems to be working on a workaround. No safestrap? No kexec? No root? What happened to our glorious hackers?
Click to expand...
Click to collapse
The glorious hackers are/have tried. Security continues to be more and more difficult to break. Jump in the pool and get it done if you want it sooner. Otherwise, buy a pure edition so you can unlock the boot loader
neh4pres said:
Bump. We need root. Can't believe nobody seems to be working on a workaround. No safestrap? No kexec? No root? What happened to our glorious hackers?
Click to expand...
Click to collapse
Thanks Motorola -_-
Buy a nexus 6. That's what I did. Still have the moto x for my wife so I can play with it
Can't afford it right now. If I knew programming, you bet I would be working on it. God I hate Verizon, but been here so long it's my cheapest option.
matt99017d said:
The glorious hackers are/have tried. Security continues to be more and more difficult to break. Jump in the pool and get it done if you want it sooner. Otherwise, buy a pure edition so you can unlock the boot loader
Click to expand...
Click to collapse
Will the pure edition work on Verizon?
GrandMstrBud said:
Will the pure edition work on Verizon?
Click to expand...
Click to collapse
From what I understand, if you pop an activated Verizon SIM card into it, it'll work. Read that it'll work on the unlocked Nexus 6 too.
GreenMunky said:
From what I understand, if you pop an activated Verizon SIM card into it, it'll work. Read that it'll work on the unlocked Nexus 6 too.
Click to expand...
Click to collapse
LTE should work but what about CDMA side of it?
GreenMunky said:
From what I understand, if you pop an activated Verizon SIM card into it, it'll work. Read that it'll work on the unlocked Nexus 6 too.
Click to expand...
Click to collapse
GrandMstrBud said:
LTE should work but what about CDMA side of it?
Click to expand...
Click to collapse
No, CDMA will not work, nor 3G. So you will be confined only to LTE service and Google Voice (or similar).
matt99017d said:
The glorious hackers are/have tried. Security continues to be more and more difficult to break. Jump in the pool and get it done if you want it sooner. Otherwise, buy a pure edition so you can unlock the boot loader
Click to expand...
Click to collapse
Looks like your idea will not work and maybe that's the reason for this thread? Pure Edition won't work on VZW
Welp, looks like it's about to be tmo for me!
freeza said:
Welp, looks like it's about to be tmo for me!
Click to expand...
Click to collapse
Be good to have ya here homeslice, you need a tester for anything hit me up!
Sent from my LG-H918 using XDA-Developers mobile app
He will be joining us in 2019
Sent from my LG-H918 using Tapatalk
I am unable to boot into bootloader on ATT model :/
Lol as expected from Sprint and AT&T. Dont get me wrong, i wish they had bootloader unlocked because the more bootloaders unlocked for different carriers, the more chances to duplicate the amount of developments/roma/mosa/kernels etc.... Now, having only Tmobile as the only one with unlocked bootloader, well, devs who use carrier such as AT&T and Sprint might get further away from developments on LG V20. (I'm a LG V20 Tmobile variant owner)
im not to familiar with LG, but the correct way is to power off the device, hold volume down, insert USB cable?
one would think even if locked, it could still enter the bootloader. adb works, and when i reboot recovery, i get to recovery, but when selecting reboot bootloader, the device starts. interestingly enough, it will enter in adb sideload mode
With Google obviously not wanting unlocked handsets or rooted handsets to be common... This kind of thing is going to be the norm. Best to adapt, in the long term. The days of modding are being ended by Google
Skripka said:
With Google obviously not wanting unlocked handsets or rooted handsets to be common... This kind of thing is going to be the norm. Best to adapt, in the long term. The days of modding are being ended by Google
Click to expand...
Click to collapse
I would agree if not for the fact that the pixel phones can be unlocked
freeza said:
I would agree if not for the fact that the pixel phones can be unlocked
Click to expand...
Click to collapse
For the time being. As SafetyNet gets more common, Google will quit making them unlockable.
Granted i preordered my v20 expecting to run it unrooted stock.
Skripka said:
For the time being. As SafetyNet gets more common, Google will quit making them unlockable.
Granted i preordered my v20 expecting to run it unrooted stock.
Click to expand...
Click to collapse
Well, it's really only sprint, at&t, and more than likely Verizon. Fastboot mode doesn't even exist on the phone through the production software. T-Mobile is completely unlockable...
freeza said:
Well, it's really only sprint, at&t, and more than likely Verizon. Fastboot mode doesn't even exist on the phone through the production software. T-Mobile is completely unlockable...
Click to expand...
Click to collapse
So this means no recovery for sprint variants, but is there still a possibility of systemless root using the LG up or bridge programs?
rickberg said:
So this means no recovery for sprint variants, but is there still a possibility of systemless root using the LG up or bridge programs?
Click to expand...
Click to collapse
I would also like to know this
+1
sjr19 said:
I would also like to know this
Click to expand...
Click to collapse
According to twitter there is a root being worked on by chainfire unsure of whether or not it will be for all variants or just unlocked bootloaders
rickberg said:
According to twitter there is a root being worked on by chainfire unsure of whether or not it will be for all variants or just unlocked bootloaders
Click to expand...
Click to collapse
T-Mobile is rooted because of bootloader unlock v.v not the other variants.
shadowxaero said:
T-Mobile is rooted because of bootloader unlock v.v not the other variants.
Click to expand...
Click to collapse
So the root chainfire has established will be tmobile only?
rickberg said:
According to twitter there is a root being worked on by chainfire unsure of whether or not it will be for all variants or just unlocked bootloaders
Click to expand...
Click to collapse
rickberg said:
So the root chainfire has established will be tmobile only?
Click to expand...
Click to collapse
He said it was based on jcadduono's work and if jcadduono has a thread on here about getting root shell to push recovery on the TMobile variant after unlocking the bootloader.
time to return it!
Just a thought. A method over use getting around big red in the past . I purchased unlock able version of the the phone I wanted the note 5 . Umocked it rooted it . Then got my carriers Sim card and called to get it activated. It can be a pain but it can be done
shadowxaero said:
T-Mobile is rooted because of bootloader unlock v.v not the other variants.
Click to expand...
Click to collapse
I thought since we had the "enable OEM unlock" option like T-Mobile we would be good to go.. smh