Related
With the release of the Fascinate we will finally know who is responsible for the encrypted bootloaders on the Droid X/2...Motorola or Verizon
I certainly hope it is not encrypted but I wouldn't put it past Verizon as being the one responsible.
Sent from my DROIDX using XDA App
FSRBIKER said:
With the release of the Fascinate we will finally know who is responsible for the encrypted bootloaders on the Droid X/2...Motorola or Verizon
I certainly hope it is not encrypted but I wouldn't put it past Verizon as being the one responsible.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Well, do a little reading and you will see that motorola locked down the milestone, which came out overseas as the droid 1's cousin, and motorola has come out saying that they will not produce open android handsets like the droid 1 ever again. I dont think the BL will be locked down on the fascinate more so than the other galaxy s phones
Did plenty of reading/flashing/modding over the year+ about Android, it's phones, Rom's, etc so I am no rookie despite my post count at XDA. We all know Motorola's stance and their comments but the Fascinate is the only way we will really know Verizon's stance on bootloaders since the other three US variants have all been unlocked easily.
So WELL if you know the FACTS not speculation then let us hear your all worldly knowledge please.
If you've done enough reading you'll know that Verizon had nothing to do with the lockdown of the bootloader if they did then the Incredible would have been locked down as well as the ally both of which have achieved root. Not to mention Verizon doesn't have a factory where they say "Hey guys we developed this fancy eFuse and tricky bootloader that works in EVERY PHONE" because that would totally make sense a bootloader that's compatible with every chipset and every handset if that was the case someone would have developed an unlocked bootloader that works on every device. Listen to what you're saying, there is no possible way that Verizon distributes an eFuse and a custom encrypted bootloader to every manufacturer. Not trying to be rude or anything it's just common sense.
Achieving Root and Unlocking a Bootloader are two different things, try reading up on that first ok?
No one ever said Verizon is manufacturing phones, but they absolutely can tell the phone manufacturers to lock the bootloaders or Verizon will not offer the phone for sale. Also read up the bootloaders for the Incredible was locked but not digitally encrypted. Since this is the first phone Verizon is offering since the Motorola DroidX/2 which have digitally encrypted bootloaders we will know if Verizon had a hand in changing anything on the Fascinate if it is different at all from the other three US Galaxy phones. That was the only point to my post, why is this a pissing match on who searches, researches, etc more?
If you have Facts/Proof on the Fascinate and its bootloader post it, this other stuff is just crap and not getting anyone anywhere.
DigitalDementia said:
If you've done enough reading you'll know that Verizon had nothing to do with the lockdown of the bootloader if they did then the Incredible would have been locked down as well as the ally both of which have achieved root. Not to mention Verizon doesn't have a factory where they say "Hey guys we developed this fancy eFuse and tricky bootloader that works in EVERY PHONE" because that would totally make sense a bootloader that's compatible with every chipset and every handset if that was the case someone would have developed an unlocked bootloader that works on every device. Listen to what you're saying, there is no possible way that Verizon distributes an eFuse and a custom encrypted bootloader to every manufacturer. Not trying to be rude or anything it's just common sense.
Click to expand...
Click to collapse
"not to be rude or anything", but your post displays little "common sense". The Incredible was released before the latest droids, so obviously the Inc's bootloader is irrelevant in this situation. And who said (or inferred) anything about a verizon factory making a bootloader (and nobody even mentioned efuse)? Verizon didn't develop Bing, but they clearly have a hand in it being the only search offered on this Android phone. So it is not unreasonable to wonder if Verizon would try to exert its influence in other ways. While, I agree that it is unlikely that the Fascinate will have an encrypted bootloader, the OP asked a valid question. Not sure some people are so quick to hate. After all we are only dealing with smartphones.
There are quite people intruded interested in knowing the truth, lets keep the thread on topic PLEASE.
Sent from my DROIDX using XDA App
I have a fascinate on hand to check if someone can let me know what they need done...
Deleted: I was wrong and no need to spread bad info.
edit: deleted, nevermind, should read the newer posts when I've got a tab open for a long time.
sic4672 said:
I believe the bootloader is locked because the same root process for the captivate and vibrant don't work for the fascinate.
Click to expand...
Click to collapse
This is no indication that it is locked or not.
It is not locked.
Sent from my SCH-I500 using XDA App
ksizzle9 said:
It is not locked.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Thank you... Short sweet answer.
Ksizzle can you link a thread where it shows its not locked, thanks in advance.
Sent from my DROIDX
i actually cannot. however we can make changes to the kernel or will be able to which actually may not mean that it isnt locked but it is definetly not encrypted like the droid x. i dont have any proof but have no other galaxy s of the six different variants have a locked bootloader and if it were locked you would have read about it somewhere already or heard peopole trashing samsung and verizon. i dont have any proof but im pretty sure its not locked becasue if it were we would have to make all these workarounds for rooting and making changes to the kernel or loading roms. a guy has already made a ROM in the development section and we dont need a BOOTSTRAPP app or anything special. trust me its not locked or we wouldnt already have a custom ROM available.
ksizzle9 said:
i actually cannot. however we can make changes to the kernel or will be able to which actually may not mean that it isnt locked but it is definetly not encrypted like the droid x. i dont have any proof but have no other galaxy s of the six different variants have a locked bootloader and if it were locked you would have read about it somewhere already or heard peopole trashing samsung and verizon. i dont have any proof but im pretty sure its not locked becasue if it were we would have to make all these workarounds for rooting and making changes to the kernel or loading roms. a guy has already made a ROM in the development section and we dont need a BOOTSTRAPP app or anything special. trust me its not locked or we wouldnt already have a custom ROM available.
Click to expand...
Click to collapse
Lack of a locked bootloader is why I chose this phone over the X. Well, that and the better processor. The post indicating that it is not locked can be found HERE.
so why is there such a convoluted method for rooting? On the Galaxy S I900, Vibrant, and Captivate you just throw an update.zip on the phones internal memory, reboot into recovery, and hit apply update. theres your root, no adb required, no shell commands. If its not locked then why is it this bad over here.
I believe because they have different types of internal memory. Cud b wrong. But the bootloader is why I chose this phone as well.
Sent from my SCH-I500 using XDA App
chaoscentral said:
so why is there such a convoluted method for rooting? On the Galaxy S I900, Vibrant, and Captivate you just throw an update.zip on the phones internal memory, reboot into recovery, and hit apply update. theres your root, no adb required, no shell commands. If its not locked then why is it this bad over here.
Click to expand...
Click to collapse
The same method would work if someone compiled it for our hardware.
Hop to it someone.
chaoscentral said:
so why is there such a convoluted method for rooting? On the Galaxy S I900, Vibrant, and Captivate you just throw an update.zip on the phones internal memory, reboot into recovery, and hit apply update. theres your root, no adb required, no shell commands. If its not locked then why is it this bad over here.
Click to expand...
Click to collapse
i dont have many posts here but i do a bunch of help at other sites. iv rooted the d1. the devour, the inc, the d2 and now the gal s....everytime the adb way comes first. it does not mean in anyway that the bootloader is locked. sammy gave us the codes and ina few days we will see clockwork and then a few weeks after that the real fun starts. the boot loader is not locked.
As a long time basic phone owner I am finally decided to make the switch to android. I have done my research and have come to the conclusion that i would like to purchase the Samsung galaxy S III. However, money is always an issue and I am trying to spend as little as possible but get the most of out my phone.
With Verizon, my current service, the additional 720$ for the 2 year data contract is scary, but the phone, only 200$ is nice. My major question about Verizon is, is it possible to root the Verizon SGSIII. I have read multiple posts from outraged customers who bricked their phones due to the locked bootloader on the Verizon SGSIII. Also, from what i have read from this thread: http://forum.xda-developers.com/showthread.php?t=1756885 it is possible to root the verizon version of this phone although it is more complicated.
My second option is to purchase the Samsung Galaxy Nexus and root this phone through verizon. I would love to run Android 4.1 Jelly Bean on my device which is why i would like to root the device and flash something that would give me this enhancement. However, if i purchase the Galaxy Nexus, i am locked into a 2 year contract with a phone that came out 6 months ago and could soon be outdated by its "older brother" said to be released this december.
Which is my best option and if someone could please clear up the Root problems with the Verizon SGSIII it would be extremely helpful. Thanks for any response!
Best Regards
JSMessick
What are you guys talking about...10 seconds in the Verizon forum would turn up a root tutorial thread. So yes, root is available and there are workarounds that permit custom kernels.
Edit: there's a sticky thread in this very forum of how to obtain root on the Verizon gs3. http://forum.xda-developers.com/showthread.php?t=1762709
Sent from my SCH-I535 using xda premium
From what I understand Verizon Galaxy S3 owners will be able to root but not be able to flash kernels or use aosp roms like CM9/10 since you guys can't flash a kernel.
Unless you buy the bootloader unlocked Verizon Galaxy S3 from Samsung directly, you won't be able to flash kernels.
Again that is inaccurate. Using kexec we can boot custom kernels. We have an early version of cm9 running too. The real hold up is the ril which prevents the cm9 build from having mobile data
Sent from my SCH-I535 using xda premium
To my understanding, they released a developer version that's boot loader unlocked.
Sent from my SGH-T989
Avelnan said:
To my understanding, they released a developer version that's boot loader unlocked.
Sent from my SGH-T989
Click to expand...
Click to collapse
They are, with the release date undisclosed, however it is 600$ which is a little outrageous.
bobloblaw1 said:
Again that is inaccurate. Using kexec we can boot custom kernels. We have an early version of cm9 running too. The real hold up is the ril which prevents the cm9 build from having mobile data
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
So if i purchase the verizon version of the phone and i root it and flash CM9/10 using kexec will the phone still work? what do you mean by the RIL preventing cm9 from having mobile data? just want to clarify thanks for the help.
JSMessick said:
So if i purchase the verizon version of the phone and i root it and flash CM9/10 using kexec will the phone still work? what do you mean by the RIL preventing cm9 from having mobile data? just want to clarify thanks for the help.
Click to expand...
Click to collapse
To clarify some things, since half of the users on these boards are misinformed:
The Verizon (and pretty much every) Galaxy S3 has had root since virtually their release date.
The Verizon version does have a locked bootloader (see #3), and there is going to be a "Developer Edition" released directly from Samsung with pretty much no warranty, and it will be completely unsubsidized.
The bootloader lock has not stopped us from flashing custom ROMs or custom kernels. See below.
Here's some source links for you, in rough chronological order:
The "Root66" method for easily obtaining root
Original proof-of-concept showing custom kernels can be booted
Standard install of CyanogenMod 9 via kexec demonstrated
Functioning 3G/4G data on CyanogenMod 9 demonstrated
Unofficial guide to installing CyanogenMod 9
CVPCS states locked bootloader is a non-issue
Ongoing research & development on the locked bootloader
I could go on and on, but as you can see, development of custom ROMs (both TouchWiz and AOSP based) has not been hindered by the locked bootloader.
The community has pulled together on this, and developers from non-Verizon carriers have been tons of help in all the progress that has been made so far.
Many people, including myself, do not support the idea of the Developer Edition SGS3, and I personally doubt it will have even a tiny fraction of the community the consumer version has.
wifi hot spot on verizon galaxy iii
My question is. Even though the bootloader is locked am I still able to get root access and use the existing rom that cane with the phone originally and add the wifi hot spot feature. If so where do I find the wifi hotspot software? Sorry if it is a noob question but this is my first post.
Thanks in advance
ExodusC said:
To clarify some things, since half of the users on these boards are misinformed:
The Verizon (and pretty much every) Galaxy S3 has had root since virtually their release date.
The Verizon version does have a locked bootloader (see #3), and there is going to be a "Developer Edition" released directly from Samsung with pretty much no warranty, and it will be completely unsubsidized.
The bootloader lock has not stopped us from flashing custom ROMs or custom kernels. See below.
Here's some source links for you, in rough chronological order:
The "Root66" method for easily obtaining root
Original proof-of-concept showing custom kernels can be booted
Standard install of CyanogenMod 9 via kexec demonstrated
Functioning 3G/4G data on CyanogenMod 9 demonstrated
Unofficial guide to installing CyanogenMod 9
CVPCS states locked bootloader is a non-issue
Ongoing research & development on the locked bootloader
I could go on and on, but as you can see, development of custom ROMs (both TouchWiz and AOSP based) has not been hindered by the locked bootloader.
The community has pulled together on this, and developers from non-Verizon carriers have been tons of help in all the progress that has been made so far.
Many people, including myself, do not support the idea of the Developer Edition SGS3, and I personally doubt it will have even a tiny fraction of the community the consumer version has.
Click to expand...
Click to collapse
saedhamad said:
My question is. Even though the bootloader is locked am I still able to get root access and use the existing rom that cane with the phone originally and add the wifi hot spot feature. If so where do I find the wifi hotspot software? Sorry if it is a noob question but this is my first post.
Thanks in advance
Click to expand...
Click to collapse
Please visit the Verizon SGS3 development forum, all of your questions can be answered with a little browsing.
In short: yes you can root your phone very easily. You can install Free Wifi Tether from the Google Play store, and it works fine on a rooted phone. Finally, rooting involves installing a "stock" ROM (i.e. the one that came with your phone), the only difference being root access.
I have done all of this, so has my totally noob roommate.
saedhamad said:
My question is. Even though the bootloader is locked am I still able to get root access and use the existing rom that cane with the phone originally and add the wifi hot spot feature. If so where do I find the wifi hotspot software? Sorry if it is a noob question but this is my first post.
Thanks in advance
Click to expand...
Click to collapse
I thought my post was pretty clear that you can easily gain root access with the current ROM.
I don't know about using the built-in wifi hotspot feature, but I know apps from the Play Store like FoxFi work just fine, even without root.
The Kexec method is a bandaid solution that can easily be patched by Verizon in the future.
JSMessick said:
As a long time basic phone owner I am finally decided to make the switch to android. I have done my research and have come to the conclusion that i would like to purchase the Samsung galaxy S III. However, money is always an issue and I am trying to spend as little as possible but get the most of out my phone.
With Verizon, my current service, the additional 720$ for the 2 year data contract is scary, but the phone, only 200$ is nice. My major question about Verizon is, is it possible to root the Verizon SGSIII. I have read multiple posts from outraged customers who bricked their phones due to the locked bootloader on the Verizon SGSIII. Also, from what i have read from this thread: http://forum.xda-developers.com/showthread.php?t=1756885 it is possible to root the verizon version of this phone although it is more complicated.
My second option is to purchase the Samsung Galaxy Nexus and root this phone through verizon. I would love to run Android 4.1 Jelly Bean on my device which is why i would like to root the device and flash something that would give me this enhancement. However, if i purchase the Galaxy Nexus, i am locked into a 2 year contract with a phone that came out 6 months ago and could soon be outdated by its "older brother" said to be released this december.
Which is my best option and if someone could please clear up the Root problems with the Verizon SGSIII it would be extremely helpful. Thanks for any response!
Best Regards
JSMessick
Click to expand...
Click to collapse
Going from basic phone (I'm assuming by that u mean a NON smartphone).... And already thinking of modifying. Wow lol.... Just get the gs3 my guess is u will be amazed at its capabilities right out of the box. Welcome to android btw.
Sent str8 from my half eaten Banilla Ice Cream Samich
Just one final question, i know there are many people working on getting 4.1 Jellybean onto the SGSIII for the other versions (at&t sprint international etc.) is there a way i can get it onto the verizon one even with the locked bootloader? Like it is possible to get CM10 alpha on my phone and possible use that? or has this not been figured out yet. sorry for all the questions i just wanna try to learn as much as possible before i make a purchase.
JSMessick said:
Just one final question, i know there are many people working on getting 4.1 Jellybean onto the SGSIII for the other versions (at&t sprint international etc.) is there a way i can get it onto the verizon one even with the locked bootloader? Like it is possible to get CM10 alpha on my phone and possible use that? or has this not been figured out yet. sorry for all the questions i just wanna try to learn as much as possible before i make a purchase.
Click to expand...
Click to collapse
Idk about that BUT I do know that we should be getting the official JB pushed to our devices in Q4 of this year. I've been reading late aug-sep.
Sent str8 from my half eaten Banilla Ice Cream Samich
I rooted my Verizon S4, froze all of the bloatware with ROM Toolbox Pro, and now it's fast as hell. The battery lasts 2 days with moderate use, FoxFi hotspot works, and I don't get any security warnings (froze your ass KNOX). I've installed SafeStrap 3.71, and I've tried installing HypderDrive, but it hasn't been able to stick. The bootloader is totally locked down, so Hashcode's SafeStrap seems to be the only thing keeping any hope alive for something that will work.
I guess the real frustrating thing is that there is no real unity between developers here, and that no one can decide on a route to go with. This leaves a lot of us who just got the S4 with fewer, or no ROM options. Is it time we accepted that a bootloader solution might not be the way to go, and attack it using something like SafeStrap? I've been using SafeStrap on my Droid 4 for a long time, and it is the best alternative, and in many ways, superior to unlocking a bootloader. Sure you get issues regarding space for more than one ROM install, but having your stock ROM intact is an excellent fail safe. There are some other constrictions, but the manpower potential could really bring results to a dual-boot system like SafeStrap.
My deal here is, let's get behind HashCode on this, and maybe he can share his work with the rest of the developer community, and we can all contribute some funds to make something like SafeStrap work, which it most definitely can. Imagine if we could get Cyanogenmod developers working on SafeStrap with HashCode to come up with ROMs that would actually work like they do with an unlocked bootloader. There is a somewhat steep learning curve with SafeStrap, but with resources comes better documentation. People are too quick to jump on a 1-click rooting method, and leave the rest of us behind. If SafeStrap got enough attention, maybe it could someday be a one-click solution that no one at Samsung, Motorola, or HTC could ever lock down.
Let me know what you think.
RueTheDayTrebek said:
I've been using SafeStrap on my Droid 4 for a long time, and it is the best alternative, and in many ways, superior to unlocking a bootloader. Sure you get issues regarding space for more than one ROM install, but having your stock ROM intact is an excellent fail safe. There are some other constrictions, but the manpower potential could really bring results to a dual-boot system like SafeStrap.
Click to expand...
Click to collapse
I Love Hashcode and that he designed SafeStrap as i have used it on my Droid Bionic prior to getting the S4 (im still on MDK). But I would never say it's superior to unlocking a bootloader in any sense. I can say maybe convenient for quicker swapping of roms but I can't see SS being better then an unlocked Bootloader.
But the rest of you post im totally on board with. Id rather an unlocked Bootloader and be able to get OTA's with the correct kernels then a port where some things won't work since were still on the original or a previous kernel.
RueTheDayTrebek said:
I rooted my Verizon S4, froze all of the bloatware with ROM Toolbox Pro, and now it's fast as hell. The battery lasts 2 days with moderate use, FoxFi hotspot works, and I don't get any security warnings (froze your ass KNOX). I've installed SafeStrap 3.71, and I've tried installing HypderDrive, but it hasn't been able to stick. The bootloader is totally locked down, so Hashcode's SafeStrap seems to be the only thing keeping any hope alive for something that will work.
I guess the real frustrating thing is that there is no real unity between developers here, and that no one can decide on a route to go with. This leaves a lot of us who just got the S4 with fewer, or no ROM options. Is it time we accepted that a bootloader solution might not be the way to go, and attack it using something like SafeStrap? I've been using SafeStrap on my Droid 4 for a long time, and it is the best alternative, and in many ways, superior to unlocking a bootloader. Sure you get issues regarding space for more than one ROM install, but having your stock ROM intact is an excellent fail safe. There are some other constrictions, but the manpower potential could really bring results to a dual-boot system like SafeStrap.
My deal here is, let's get behind HashCode on this, and maybe he can share his work with the rest of the developer community, and we can all contribute some funds to make something like SafeStrap work, which it most definitely can. Imagine if we could get Cyanogenmod developers working on SafeStrap with HashCode to come up with ROMs that would actually work like they do with an unlocked bootloader. There is a somewhat steep learning curve with SafeStrap, but with resources comes better documentation. People are too quick to jump on a 1-click rooting method, and leave the rest of us behind. If SafeStrap got enough attention, maybe it could someday be a one-click solution that no one at Samsung, Motorola, or HTC could ever lock down.
Let me know what you think.
Click to expand...
Click to collapse
HD 12 is about as flawless as one would expect for a custom rom. Im happy with it and honestly if there were more options, I doubt I would move away from it. Thats just my opinion though. What do you mean it didnt stick?
Sent from my SCH-I545 using XDA Premium HD app
The development community on the S4 took a pretty big hit with the whole boot loader thing. Hopefully hash can figure out Kexec and hopefully we can get more dev support...
But until then safestrap IS here, it does have roms and it works great. Not sure exactly what your looking for?
Can you detail what your doing to advance the community, and how you want us to help you?
scryan said:
The development community on the S4 took a pretty big hit with the whole boot loader thing. Hopefully hash can figure out Kexec and hopefully we can get more dev support...
But until then safestrap IS here, it does have roms and it works great. Not sure exactly what your looking for?
Can you detail what your doing to advance the community, and how you want us to help you?
Click to expand...
Click to collapse
What are you talking about? Did you get my post mixed up with the op's?
Sent from my SCH-I545 using Tapatalk
Bradh024 said:
What are you talking about? Did you get my post mixed up with the op's?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Yup. lol sorry just hit the "Reply" button with out noticing its the same as most forums Quote button.... Just meant to reply.
scryan said:
Yup. lol sorry just hit the "Reply" button with out noticing its the same as most forums Quote button.... Just meant to reply.
Click to expand...
Click to collapse
Ahh I gotcha. Had me confused for a minute there. lol
Sent from my SCH-I545 using Tapatalk
RueTheDayTrebek said:
I rooted my Verizon S4, froze all of the bloatware with ROM Toolbox Pro, and now it's fast as hell. The battery lasts 2 days with moderate use, FoxFi hotspot works, and I don't get any security warnings (froze your ass KNOX). I've installed SafeStrap 3.71, and I've tried installing HypderDrive, but it hasn't been able to stick. The bootloader is totally locked down, so Hashcode's SafeStrap seems to be the only thing keeping any hope alive for something that will work.
I guess the real frustrating thing is that there is no real unity between developers here, and that no one can decide on a route to go with. This leaves a lot of us who just got the S4 with fewer, or no ROM options. Is it time we accepted that a bootloader solution might not be the way to go, and attack it using something like SafeStrap? I've been using SafeStrap on my Droid 4 for a long time, and it is the best alternative, and in many ways, superior to unlocking a bootloader. Sure you get issues regarding space for more than one ROM install, but having your stock ROM intact is an excellent fail safe. There are some other constrictions, but the manpower potential could really bring results to a dual-boot system like SafeStrap.
My deal here is, let's get behind HashCode on this, and maybe he can share his work with the rest of the developer community, and we can all contribute some funds to make something like SafeStrap work, which it most definitely can. Imagine if we could get Cyanogenmod developers working on SafeStrap with HashCode to come up with ROMs that would actually work like they do with an unlocked bootloader. There is a somewhat steep learning curve with SafeStrap, but with resources comes better documentation. People are too quick to jump on a 1-click rooting method, and leave the rest of us behind. If SafeStrap got enough attention, maybe it could someday be a one-click solution that no one at Samsung, Motorola, or HTC could ever lock down.
Let me know what you think.
Click to expand...
Click to collapse
what makes you think there is no unity or communication between devs on this issue? The fact of the matter is, the security lockdown is pretty steep and in the end, no work around can be possible.
decaturbob said:
what makes you think there is no unity or communication between devs on this issue? The fact of the matter is, the security lockdown is pretty steep and in the end, no work around can be possible.
Click to expand...
Click to collapse
That's my point about the bootloader, that in time, every carrier is going to put their phones on lockdown. It just makes sense to move to a newer concept than trying to unlock the bootloader. Is hijacking the boot order, what SafeStrap does, the right way to go? What about overwriting the kernel and bypassing the bootloader altogether? I remember Hashcode was working with kexec, and for those of you who were there a couple of years ago when SafeStrap was first there for the Motorla RZR, D4, and Bionic, might remember this. It executes a live kernel overwrite, before the bootloader can even come up to verify the signed stock rom/firmware/bootloader.
I've read a couple of people mentioning this, but I'm not sure if its feasible. My point, SafeStrap and KEXEC are two options that need some blockbuster support. Hashcode is the Zeus of Mt. SafeStrape, but where is the God of War and the rest of the bunch to kick ass? Can we pick a direction?
Maybe I'm going about this the wrong way, maybe my message isn't the one that needs to be heard? I haven't posted much over the last couple of years, but I've done a lot of reading over the last few weeks, and I'm just curious if there is a Bat Signal they can use to summon the Justice League and put their collective boots up the ass of Lex Luthor (Verizon and co.)?
RueTheDayTrebek said:
That's my point about the bootloader, that in time, every carrier is going to put their phones on lockdown. It just makes sense to move to a newer concept than trying to unlock the bootloader. Is hijacking the boot order, what SafeStrap does, the right way to go? What about overwriting the kernel and bypassing the bootloader altogether? I remember Hashcode was working with kexec, and for those of you who were there a couple of years ago when SafeStrap was first there for the Motorla RZR, D4, and Bionic, might remember this. It executes a live kernel overwrite, before the bootloader can even come up to verify the signed stock rom/firmware/bootloader.
I've read a couple of people mentioning this, but I'm not sure if its feasible. My point, SafeStrap and KEXEC are two options that need some blockbuster support. Hashcode is the Zeus of Mt. SafeStrape, but where is the God of War and the rest of the bunch to kick ass? Can we pick a direction?
Maybe I'm going about this the wrong way, maybe my message isn't the one that needs to be heard? I haven't posted much over the last couple of years, but I've done a lot of reading over the last few weeks, and I'm just curious if there is a Bat Signal they can use to summon the Justice League and put their collective boots up the ass of Lex Luthor (Verizon and co.)?
Click to expand...
Click to collapse
Put it this way:
I'm with you 100%... WHAT DO YOU WANT ME TO DO?
Because right now, your basically saying "DEVELOP MORE STUFF FOR ME SO I DON'T HAVE TO, LOLZ".
You just saying we should do things better is not a plan, what are you actually doing here to move this thing forwards?
BTW:
forum.xda-developers.com/showthread.php?t=2578566
http://forum.xda-developers.com/showthread.php?t=2500826
Its not just like "BOOM! Here is Kexec!"
Its not like the people you are suggesting should put together a software package for you phone for free are not working on it... Its just hard.
RueTheDayTrebek said:
That's my point about the bootloader, that in time, every carrier is going to put their phones on lockdown. It just makes sense to move to a newer concept than trying to unlock the bootloader. Is hijacking the boot order, what SafeStrap does, the right way to go? What about overwriting the kernel and bypassing the bootloader altogether? I remember Hashcode was working with kexec, and for those of you who were there a couple of years ago when SafeStrap was first there for the Motorla RZR, D4, and Bionic, might remember this. It executes a live kernel overwrite, before the bootloader can even come up to verify the signed stock rom/firmware/bootloader.
I've read a couple of people mentioning this, but I'm not sure if its feasible. My point, SafeStrap and KEXEC are two options that need some blockbuster support. Hashcode is the Zeus of Mt. SafeStrape, but where is the God of War and the rest of the bunch to kick ass? Can we pick a direction?
Maybe I'm going about this the wrong way, maybe my message isn't the one that needs to be heard? I haven't posted much over the last couple of years, but I've done a lot of reading over the last few weeks, and I'm just curious if there is a Bat Signal they can use to summon the Justice League and put their collective boots up the ass of Lex Luthor (Verizon and co.)?
Click to expand...
Click to collapse
Dude. There are people working on this, believe me. And people who arent developers or cant contribute directly have posted a bounty to reward whoever can get a workaround. Safestrap does work, regardless of whether you are able to get it to work on your device. I'm guessing its user error. Not really sure what more you expect the community or Hashcode or any other dev to do that they arent already doing...
So after attempting the goomanager method of unlocking my Galaxy S4 and after getting stuck in odin mode, and after a little more limited research, I have read in a few forums that you CANNOT unlock the bootloader of this particular model. Can some please verify or repudiate this for me, and if this is not the case, can someone guide me to a forum that can help me, because I haven't read a forum that specifies whether or not their method will work on this model of the Galaxy S4.
Thanks for any and all help...
First off I'm guessing you didn't read any of the stickies on this forum about rooting and or unlocking this device. Secondly, it depends on which bootloader version you have as to if you can unlock it.
Sent from my SCH-I545 using Tapatalk
Idk exactly what you're talking about, but this phone is rooted and what are you talking about "bootloader version?" Are you making things up? If you're talking about my build number I am MK2. I'm not sure what you're talking about lol. Help me out here.
JACKc2402 said:
Idk exactly what you're talking about, but this phone is rooted and what are you talking about "bootloader version?" Are you making things up? If you're talking about my build number I am MK2. I'm not sure what you're talking about lol. Help me out here.
Click to expand...
Click to collapse
dude you cant unlock bootloader. Only if you were on mdk.... So you need to full wipe odin the factory mk2. then root and then use safestrap. Please read the forums dude
Marshmellow92 said:
dude you cant unlock bootloader. Only if you were on mdk.... So you need to full wipe odin the factory mk2. then root and then use safestrap. Please read the forums dude
Click to expand...
Click to collapse
Lol, I promise you I have searched up and down for a clear answer and I haven't seen it yet. Besides, most of these forums are several months old and I wasn't sure if anything has changed since the next version of this phone is about to be released. I didn't know if, perhaps, Verizon themselves had released an unlocked bootloader like HTC initially did with the DNA.... And I don't need to odin factory mk2, all I needed was a battery pull. I already have Safestrap installed. I'm way ahead of you. I'm not looking for a work-around. I want this damn bootloader unlocked so I can flash Cyanogemod. If that is still impossible I understand, but you people need to chill out. This is the QUESTION AND ANSWERING forum.
JACKc2402 said:
Lol, I promise you I have searched up and down for a clear answer and I haven't seen it yet. Besides, most of these forums are several months old and I wasn't sure if anything has changed since the next version of this phone is about to be released. I didn't know if, perhaps, Verizon themselves had released an unlocked bootloader like HTC initially did with the DNA.... And I don't need to odin factory mk2, all I needed was a battery pull. I already have Safestrap installed. I'm way ahead of you. I'm not looking for a work-around. I want this damn bootloader unlocked so I can flash Cyanogemod. If that is still impossible I understand, but you people need to chill out. This is the QUESTION AND ANSWERING forum.
Click to expand...
Click to collapse
XDA is actually one of the sites that most for the most part is updated daily. There are multiple threads on here stating how the retail version of the Verizon S4 after MDK build ( the 1st release ) cannot have a custom recovery enabling you to flash any aosp ROMs.
Just takes some getting used to when someone is new on here that's all. Browse to the Verizon S4 forums and you'll see a ton of Stickies created addressing these kind of things.
Go to Swappa and get an MDK S4 if you really want CM.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
XDA is actually one of the sites that most for the most part is updated daily. There are multiple threads on here stating how the retail version of the Verizon S4 after MDK build ( the 1st release ) cannot have a custom recovery enabling you to flash any aosp ROMs.
Just takes some getting used to when someone is new on here that's all. Browse to the Verizon S4 forums and you'll see a ton of Stickies created addressing these kind of things.
Go to Swappa and get an MDK S4 if you really want CM.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
See, that's actually helpful. Nice and concise. Believe it or not, I'm not new to XDA. I've been flashing ROMs since my O.G. A855. That phone was a beast! No locked bootloader b.s., one-click-root, simple clockworkmod installation... Those were the good ole days! I simply rarely post because I usually know what I'm doing. My last phone (Droid DNA, wouldn't recommend that phone to anyone) almost kicked my ass. I literally just purchased this Galaxy S4 today and couldn't believe the bootloader is still locked. But alas, Verizon are jerks and you'd probably need 100 years to crack their encryptions on windows 8 64-bit lol. Thanks for the input guys. I suppose I'll settle for Hyperdrive.
JACKc2402 said:
See, that's actually helpful. Nice and concise. Believe it or not, I'm not new to XDA. I've been flashing ROMs since my O.G. A855. That phone was a beast! No locked bootloader b.s., one-click-root, simple clockworkmod installation... Those were the good ole days! I simply rarely post because I usually know what I'm doing. My last phone (Droid DNA, wouldn't recommend that phone to anyone) almost kicked my ass. I literally just purchased this Galaxy S4 today and couldn't believe the bootloader is still locked. But alas, Verizon are jerks and you'd probably need 100 years to crack their encryptions on windows 8 64-bit lol. Thanks for the input guys. I suppose I'll settle for Hyperdrive.
Click to expand...
Click to collapse
LOL. "Settle" for Hyperdrive? I am on the developer edition S4 and can flash any of the ROM's for it, including the ASOP, Cyanogen, whatever. I still come back to Hyperdrive. Simply the best (IMHO). Easy to forget that it's TouchWiz based. All the customization one could want. As stable as any. Don't know exactly what limits safestrap may impose but HD is my DD.
wtherrell said:
LOL. "Settle" for Hyperdrive? I am on the developer edition S4 and can flash any of the ROM's for it, including the ASOP, Cyanogen, whatever. I still come back to Hyperdrive. Simply the best (IMHO). Easy to forget that it's TouchWiz based. All the customization one could want. As stable as any. Don't know exactly what limits safestrap may impose but HD is my DD.
Click to expand...
Click to collapse
I'll trade you my non dev S4... I'm missing CM so bad. HyperDrive isn't bad, it's Just not CM.
ericerk said:
I'll trade you my non dev S4... I'm missing CM so bad. HyperDrive isn't bad, it's Just not CM.
Click to expand...
Click to collapse
Thanks, but I'm hanging on to my DEV Edition. Hope you can find one, or at least an MDK.
wtherrell said:
Thanks, but I'm hanging on to my DEV Edition. Hope you can find one, or at least an MDK.
Click to expand...
Click to collapse
Meh... If the S4 doesn't get unlocked soon, I'll sell it.
JACKc2402 said:
Idk exactly what you're talking about, but this phone is rooted and what are you talking about "bootloader version?" Are you making things up? If you're talking about my build number I am MK2. I'm not sure what you're talking about lol. Help me out here.
Click to expand...
Click to collapse
Making things up? No. Apparently you seem to be missing the forest for the trees.
Start with reading this: http://forum.xda-developers.com/showthread.php?t=2606501
Then read this: http://forum.xda-developers.com/showthread.php?t=2578569
The important thing to know is NOT the build number, it's the bootloader version. You can run whatever build you want if you have the MDK bootloader, and can't if you don't have that bootloader. So, that's the important question, whether or not you understand it.
k1mu said:
Making things up? No. Apparently you seem to be missing the forest for the trees.
Start with reading this: http://forum.xda-developers.com/showthread.php?t=2606501
Then read this: http://forum.xda-developers.com/showthread.php?t=2578569
The important thing to know is NOT the build number, it's the bootloader version. You can run whatever build you want if you have the MDK bootloader, and can't if you don't have that bootloader. So, that's the important question, whether or not you understand it.
Click to expand...
Click to collapse
I see, I apologize to the commenter. But this is why I'm here, to get help with what I am not familiar with. I was a hardcore Moto fan for years, all the way from the A855 until they ruined the experience with the Bionic. That was a terrible device. My first non-Moto phone was the HTC DNA. I had that about 8 months before I just got this Samsung yesterday. They all work by the same basic principles but I am finding quirky little differences that throw me off a little. It seems that with every phone I get flashing gets a little more difficult and I am forced to learn more and more about this OS then I ever intended lol. I honestly appreciate the help guys.
wtherrell said:
LOL. "Settle" for Hyperdrive? I am on the developer edition S4 and can flash any of the ROM's for it, including the ASOP, Cyanogen, whatever. I still come back to Hyperdrive. Simply the best (IMHO). Easy to forget that it's TouchWiz based. All the customization one could want. As stable as any. Don't know exactly what limits safestrap may impose but HD is my DD.
Click to expand...
Click to collapse
HyperDrive is a quirky and clumsy version of CM with mediocre animations. It isn't up to par with a several ROMs, including Eclipse and especially not CM or Paranoid Android. That's my opinion. In fact, I'm about to flash to Eclipse from HD.
wtherrell said:
LOL. "Settle" for Hyperdrive? I am on the developer edition S4 and can flash any of the ROM's for it, including the ASOP, Cyanogen, whatever. I still come back to Hyperdrive. Simply the best (IMHO). Easy to forget that it's TouchWiz based. All the customization one could want. As stable as any. Don't know exactly what limits safestrap may impose but HD is my DD.
Click to expand...
Click to collapse
ericerk said:
I'll trade you my non dev S4... I'm missing CM so bad. HyperDrive isn't bad, it's Just not CM.
Click to expand...
Click to collapse
Agreed, I'd cut off my left nut to get CM on this device.
JACKc2402 said:
Agreed, I'd cut off my left nut to get CM on this device.
Click to expand...
Click to collapse
I'd just buy a dev edition... Save your left nut.
Hey, I am about to upgrade and I will likely hold out for the new Motorola phone, but if it is a disappointment then the G3 is a very interesting option.
Curious what to look for as far as custom ROMs are concerned. I am addicted to running custom ROMs however I have had a Nexus phone lately so the whole unlocking/rooting/hackability has never been an issue. I see the the G3 has root, but I presume something else must be done before a custom recovery can be installed...thus no custom ROMs.
I love the G3s hardware, but I will never love OEM software. I want stock Android and I am hoping that will be possible with the Moto X+1 and/or the G3.
Thanks guys and gals
I'm pretty sure once someone can find an exploit to unlock the boot loader, we'll see a custom recovery as well as a few roms shortly after. I don't think there will be stock android until CM adds G3 support
I have faith in the devs that they'll eventually unlock this phone. It's been said in a few places that the security isn't as tough as say in the S4 for example.
That said though... This phones stock experience really isn't bad IMO. Best stock I've ever had. Being rooted and with xposed it's quite tolerable.
I'm a crack flasher though so believe me the itch is there!
- Sent From My G3
Mistertac said:
I have faith in the devs that they'll eventually unlock this phone. It's been said in a few places that the security isn't as tough as say in the S4 for example.
That said though... This phones stock experience really isn't bad IMO. Best stock I've ever had. Being rooted and with xposed it's quite tolerable.
I'm a crack flasher though so believe me the itch is there!
- Sent From My G3
Click to expand...
Click to collapse
Agree totally
If you want a flagship phone that will definitely run custom roms, I believe the htc one m8 is it for now. I agree with the other posters that the G3 will likely get a bootloader unlock at some point, but there are no guarantees. That said, the stock rom has a similar look and feel to the cm 11 rom I was running on my galaxy s3. While not AOSP, it doesn't annoy me the way touchwiz did and I won't have buyer's remorse if the bootloader stays locked.
Robshr said:
Agree totally
Click to expand...
Click to collapse
+2
better be soon or mine is gone.
oneandroidnut said:
better be soon or mine is gone.
Click to expand...
Click to collapse
You know as soon as you get rid of yours like the following day or week they'll unlock it lol
... So get rid of it quick!
- Sent From My G3
Mistertac said:
You know as soon as you get rid of yours like the following day or week they'll unlock it lol
... So get rid of it quick!
- Sent From My G3
Click to expand...
Click to collapse
haha ok i will throw in my desk drawer then and hope it gets unlocked!!!
This thread is pointless! Asking will there ever be custom ROMs? Of course there will be. But what you and many others fail to remember is that these phones are harder and harder to crack each time. Only reason the M8 had root and S-Off so quickly is jcase had a 3yr old vuln that wasnt patched yet. They patched it and then he had to spend more time and money cracking it again and he made a new version, which he charged for since it was such a PITA. Look how long it took the S5 to get it. Just be happy we have root.
If you are so worried about not having an unlocked bootloader, you should get rid of Verizon and get AT&T or Tmo that supports devices that are unlocked right from the manufacture. They will always have Nexus devices and other cool ones Verizon will never see since they dont allow none Verizon devices on their network.
droidkevlar said:
This thread is pointless! Asking will there ever be custom ROMs? Of course there will be. But what you and many others fail to remember is that these phones are harder and harder to crack each time. Only reason the M8 had root and S-Off so quickly is jcase had a 3yr old vuln that wasnt patched yet. They patched it and then he had to spend more time and money cracking it again and he made a new version, which he charged for since it was such a PITA. Look how long it took the S5 to get it. Just be happy we have root.
If you are so worried about not having an unlocked bootloader, you should get rid of Verizon and get AT&T or Tmo that supports devices that are unlocked right from the manufacture. They will always have Nexus devices and other cool ones Verizon will never see since they dont allow none Verizon devices on their network.
Click to expand...
Click to collapse
I don't believe it is a "pointless" thread or question. GS5 doesn't have an unlocked bootloader and who knows if they ever will. They have an exploit to run essentially stripped down versions of the stock ROM but that is it. I have not intentions on switching carriers I was simply asking what the status of the G3 was as far as unlocking was concerned.
Thank you to everyone else that responded, I think the G3 is still a viable option for me. I am going to wait to see what Motorola puts out there, but if I don't like it I'll pull the trigger on the G3.
I think it is pointless because you're asking people to predict the future. Nobody can answer the question. Therefore, the question is pointless.
This thread has outlived it's usefulness.
The progress of this device's development can be followed by reading the threads in it's forum.
When progress is made it will be reported in either the general or development sections.
If there are any questions please PM me.
Thread closed