What dev's have it or are planning to get one. Will keep adding names to the OP
- digitalhigh
Sent from my HTC6525LVW using XDA Premium 4 mobile app
I've got one and I plan on developing for it...just as soon as we get proper root/bootloader access.
this might not be the best place to ask, but im thinking of getting this phone and dropping my galaxy s4. Im just hoping this thing doesnt have a locked down bootloader and what not. Is the M8 likely to get a cyanogenmod rom?
lygris said:
this might not be the best place to ask, but im thinking of getting this phone and dropping my galaxy s4. Im just hoping this thing doesnt have a locked down bootloader and what not. Is the M8 likely to get a cyanogenmod rom?
Click to expand...
Click to collapse
Yep, not the best place to ask. That being said, until the bootloader gets unlocked or we get S-OFF, there will be zero development, to the best of my knowledge.
Related
Ok, so I'm not a dev and I don't get most of the terms being thrown around here (although I think I've actually picked up a decent amount). Basically, what I'd like to do with my phone is to root and then upgrade to JB as soon as possible (and to Key Lime Pie as soon as possible once it comes out too). With how the bootloader stuff stands right now, will I be able to do that safely once ROMs start coming out or would I have to wait for Verizon's OTA's?
Which phone would that be, sgs3? The bootloader is encrypted but I believe you can flash roms with stock kernels as its been rooted. But there are several threads explaining the options... Get a gnex!
Sent from my Galaxy Nexus using xda app-developers app
ttahatt said:
Which phone would that be, sgs3? The bootloader is encrypted but I believe you can flash roms with stock kernels as its been rooted. But there are several threads explaining the options... Get a gnex!
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Yeah I was leaning towards the GNex but if I can get custom roms on an S3 then why not get that (as long as I'm ok with stock kernels)?
Yeh that's what I'm not sure of...especially with this 'developer' sgs3 from Samsung. I have given up on skins from oems who won't give into Verizon's ridiculous demands. I'd be very cautious attempting to flash anything yet as its very new.
Sent from my Galaxy Nexus using xda app-developers app
Hey guys! I see that verizon has decided to release a pre paid version of the Moto G on their pre paid network. Is there by chance any way to root this? Rooting guides? Custom ROMs? Custom Recoveries? Anything of the sort? I can't seem to find anything, or perhaps the same rooting steps and/or ROMs for the real Verizon version still work? Thanks guys! Oh, and how to unlock it's bootloader, lets not forget that! THANKS!
H4X0R46 said:
Hey guys! I see that verizon has decided to release a pre paid version of the Moto G on their pre paid network. Is there by chance any way to root this? Rooting guides? Custom ROMs? Custom Recoveries? Anything of the sort? I can't seem to find anything, or perhaps the same rooting steps and/or ROMs for the real Verizon version still work? Thanks guys! Oh, and how to unlock it's bootloader, lets not forget that! THANKS!
Click to expand...
Click to collapse
Unfortunately, the verizon variant of the Moto G has a locked bootloader. I picked this phone up and have been using it for a good month now. Its a really great phone, but would be much much better with custom roms and such. There is a thread where some guys are trying to unlock the bootloader with a keygen. you can check the thread out here
I hope someday we will have an unlocked bootloader
Or at least root. I know with other phones it was possible without bootloader unlock, so if we could just get root, that'd be awesome. Been on this phone for a week, and while it's a decent phone without root, I definitely miss it.
Sent from my XT1028 using Tapatalk
lightningdude said:
Or at least root. I know with other phones it was possible without bootloader unlock, so if we could just get root, that'd be awesome. Been on this phone for a week, and while it's a decent phone without root, I definitely miss it.
Sent from my XT1028 using Tapatalk
Click to expand...
Click to collapse
oh no doubt, i came from an sgs2 and i can tell a very noticeable difference with smoothness and overall performance.. root is definitely missed!
So the boot loader is the issue here? Always hated how Verizon Locke's their boot loaders, god forbid one of us doesn't like that build of android! Haha well thanks for clearing that up guys! When this is unlocked, will there more than likely be specific ROMs for this phone? Or just any Moto G Verizon ROM? Probably a dumb question lol
Sent from my SGH-T889 using xda app-developers app
Hey! So I have a Verizon Version of the Straight Talk S3. (SCH-S968C). It is identical to the Verzion version, just no LTE or Wifi Thether capabilities. It also has no sim, etc. I was wanting to test a few roms on it, and I was wondering, how to unlock the bottloader on it without bricking the phone? Any help? Thanks. :silly:
im wondering the same thing.
im in the same boat and have the same model s968c on straight talk. ive got it rooted and want to install roms but im concerned about the bootloader being locked and bricking my phone. but i made it this far so im doing pretty good lol considering ive never messed with rooting or such lol. if someone could enlighten us that would be awesome. ive been researching and reading for about two days so i could learn as much as possible about this phone model and i know straight talk is no fun trying to mess with.
Fokkusu said:
Hey! So I have a Verizon Version of the Straight Talk S3. (SCH-S968C). It is identical to the Verzion version, just no LTE or Wifi Thether capabilities. It also has no sim, etc. I was wanting to test a few roms on it, and I was wondering, how to unlock the bottloader on it without bricking the phone? Any help? Thanks. :silly:
Click to expand...
Click to collapse
chrisrich1 said:
im in the same boat and have the same model s968c on straight talk. ive got it rooted and want to install roms but im concerned about the bootloader being locked and bricking my phone. but i made it this far so im doing pretty good lol considering ive never messed with rooting or such lol. if someone could enlighten us that would be awesome. ive been researching and reading for about two days so i could learn as much as possible about this phone model and i know straight talk is no fun trying to mess with.
Click to expand...
Click to collapse
From what I've been reading it seems to be that this is pretty legit, I tried it myself. Although if your on 4.3 ML1 or 4.4.2 NE1 your locked down
If you power off the device, then power it back on, you should see the words "Samsung" first. If they stay on the screen for more than 2 seconds, then it's locked down. If it flashes by almost instantly, then you're unlocked
Click to expand...
Click to collapse
From my S3 on Wicked 4.3
I not positive about it being locked down with the sch-968c) because that's a verizon boot loader issue and this is a straight talk phone. I've been researching as well and from what I've learned, it can be rooted very quickly using cydia impactor and then flashing cwm recovery for roms and such. The apn settings may need some tweaking. I'm planning to do this to my friends phone this weekend and putting liquid smooth rom on it.
Sent from my SCH-I535 using xda app-developers app
DiSiD said:
I not positive about it being locked down with the sch-968c) because that's a verizon boot loader issue and this is a straight talk phone. I've been researching as well and from what I've learned, it can be rooted very quickly using cydia impactor and then flashing cwm recovery for roms and such. The apn settings may need some tweaking. I'm planning to do this to my friends phone this weekend and putting liquid smooth rom on it.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
As far as I know any d2lte ROM will work. So far I've tried CM, PA and Pac-Man. All installed fine but they all suffer from the no APN issue which can be bypassed by using 8sms from the play store and changing the APN settings by adding Http://mms.vtext.com/servlets/mms. Handcent should also work.
ShapesBlue said:
From what I've been reading it seems to be that this is pretty legit, I tried it myself. Although if your on 4.3 ML1 or 4.4.2 NE1 your locked down
From my S3 on Wicked 4.3
Click to expand...
Click to collapse
Is that my quote?
Sent from my SCH-I535 using XDA Free mobile app
poppers162 said:
Is that my quote?
Sent from my SCH-I535 using XDA Free mobile app
Click to expand...
Click to collapse
You got it man. Pulled it from another thread.
From my S3 on Wicked 4.3
i dont think straight talk updated the s3 to 4.3 or 4.4.2 i dont think i might be wrong but straight talk really dont push otas much.
Timothy08 said:
i dont think straight talk updated the s3 to 4.3 or 4.4.2 i dont think i might be wrong but straight talk really dont push otas much.
Click to expand...
Click to collapse
In that case that's a good thing. I don't know myself as I own the vzw variant
From my S3 on Wicked 4.3
I suggest using towelroot. Its much faster and does not require a pc to root your phone.
Yes towel root works great actually the best out of the non pc methods for this device (out of my experience anyway) the phone runs on 4.1.2 and I have no access to a pc so I'm guessing that there's not a very safe or efficient way to install custom roms...
Sent from my SCH-S968C using XDA Premium 4 mobile app
Is it just me or has development waned for the S5 due to the locked bootloader? There's just so much you can do with safestrap and modifying Touchwiz. In reality, the odds of a bootloader unlock being discovered is rather slim. Look at the S4, the newest firmware releases are still not unlocked and you're forced to use safestrap. I realize we rely on a talented hacker out there to find an exploit that lets us replace the bootloader with a custom one OR the carrier allowing the bootloader to be unlocked. I've read somewhere that the S5 is approved for use by the U.S. Government so the likelihood of Verizon making the phone insecure by allowing people to unlock the bootloader is close to nil. I just really really want to see this phone not slip into XDA obscurity.
terrigan said:
Is it just me or has development waned for the S5 due to the locked bootloader? There's just so much you can do with safestrap and modifying Touchwiz. In reality, the odds of a bootloader unlock being discovered is rather slim. Look at the S4, the newest firmware releases are still not unlocked and you're forced to use safestrap. I realize we rely on a talented hacker out there to find an exploit that lets us replace the bootloader with a custom one OR the carrier allowing the bootloader to be unlocked. I've read somewhere that the S5 is approved for use by the U.S. Government so the likelihood of Verizon making the phone insecure by allowing people to unlock the bootloader is close to nil. I just really really want to see this phone not slip into XDA obscurity.
Click to expand...
Click to collapse
it is slipping away, but not because of the bootloader being locked. Not as many people (devs included) bought the phone as early adopters, so i'm guessing there's just not enough interest or intent in the phone.
terrigan said:
There's just so much you can do with safestrap and modifying Touchwiz.
Click to expand...
Click to collapse
That right there is why development is slow. There's only so much one can do with a stock system to work with. Expect to see development have a boost after each OTA until all mods are worked in, then the same downward slope until the next OTA. Repeat. :good:
MrHyde03 said:
That right there is why development is slow. There's only so much one can do with a stock system to work with. Expect to see development have a boost after each OTA until all mods are worked in, then the same downward slope until the next OTA. Repeat. :good:
Click to expand...
Click to collapse
There may be hope for that. Over in the Verizon S4 forums, they got kexec working. No aosp yet, and its very unstable, but they found it. It should work on the S5 with a little more work. Hopefully this happens this month.
Sent from my SM-G900V using XDA Premium 4 mobile app
eragon5779 said:
There may be hope for that. Over in the Verizon S4 forums, they got kexec working. No aosp yet, and its very unstable, but they found it. It should work on the S5 with a little more work. Hopefully this happens this month.
Sent from my SM-G900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This would be good. kexec was the savior of my previous phone.
eragon5779 said:
There may be hope for that. Over in the Verizon S4 forums, they got kexec working. No aosp yet, and its very unstable, but they found it. It should work on the S5 with a little more work. Hopefully this happens this month.
Sent from my SM-G900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm not sure if kexec is possible without having a SELinux permissive kernel. I believe the Galaxy s5 is enforcing unfortunately (not vulnerable).
jal3223 said:
I'm not sure if kexec is possible without having a SELinux permissive kernel. I believe the Galaxy s5 is enforcing unfortunately (not vulnerable).
Click to expand...
Click to collapse
That is being worked on already. There is a thread about it.
Sent from my SM-G900V using XDA Premium 4 mobile app
I really hope they are successful.
eragon5779 said:
There may be hope for that. Over in the Verizon S4 forums, they got kexec working. No aosp yet, and its very unstable, but they found it. It should work on the S5 with a little more work. Hopefully this happens this month.
Sent from my SM-G900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Actually I'm running a GPE ROM on my Verizon S4 right now. It's SafeStrap compatible. I love AOSP vs TouchWiz.
Being pessimistic it does seem like the beginning of the end for s5. By this I mean to say that safestrap just doesn't cut it as I do not like stock kernel. But everyone's done an amazing job thus far so haven't completely given up but I think nexus devices are the route I will take.
jal3223 said:
I'm not sure if kexec is possible without having a SELinux permissive kernel. I believe the Galaxy s5 is enforcing unfortunately (not vulnerable).
Click to expand...
Click to collapse
to my knowledge it is in the kernel. on vzw s4 mdk devicds were unlocked allowing you to flash custom kernals that were modded by devs like ktoons to make it permissive..
The later firmware builds (cant go back to mdk if took ota to a newer firmware) are in the same boat as the s5 so if they have it on later kernal builds for the s4 then it might b possible.. then again, they have it on the note 3 but doesnt work on the s5 so that concept isnt always possible
Not slipping away. Just at a road block. Everyone has done all the modding they can do on the device. I think everyone is waiting on 5.0.
elliwigy said:
to my knowledge it is in the kernel. on vzw s4 mdk devicds were unlocked allowing you to flash custom kernals that were modded by devs like ktoons to make it permissive..
The later firmware builds (cant go back to mdk if took ota to a newer firmware) are in the same boat as the s5 so if they have it on later kernal builds for the s4 then it might b possible.. then again, they have it on the note 3 but doesnt work on the s5 so that concept isnt always possible
Click to expand...
Click to collapse
I'm working on it. It's rather difficult. It appears the kernel was compiled with no /dev/mem(kmem) character devices in the config. After going through the kernel source, it looks like SELinux was set to always enforce. This is where ro.build.selinux.enforce=1 comes from. The bootloader checks the boot.img hash and for a special cookie
Code:
SEANDROIDENFORCE
which appears before the hash. If this cookie/magic isn't present, the warranty bit will blow. Since I can't access memory directly, and the methods I could use are significantly limited because of the Enforcing status, some sort of vulnerability in the kernel will need to be present. As soon as we can get Permissive, I can get us kernel modules, and hopefully kexec with the help of a few other great devs @Surge1223 @CalcProgrammer1
Your efforts are truly appreciated!
Sent from my SM-G900V using Tapatalk
The OP is originally from September something. I just seen this post and was interested in it, it is now November and if you ask me, yes it has slipped away, technology moves on quickly, i6+ is out and now we will start seeing things about a s6 in the works and it is what it is.
I blame the locked bootloader on a ton of stuff not being created. You have to grab ahold of technology in the moment and use it fast or else its gone before you know it.
It is certainly nothing like the S3 forums. That place is still kicking.
From what I understand they're close to kexec on it and the S4, since they only need KK-compatible kernels and they previously had unlocked bootloaders. That isn't the case here.
Samsung really screwed up with this one. If the N6 wasn't assured to be a failure on Verizon and it didn't have a massive footprint I'd be all over it.
Everybody panic.
Wish we can get some good news soon.
Dead is all I'm seeing, except for the few amazing devs we have now. Those still building, thank you
Galaxy 6s Os 6.2.8▪Ss° Pen
Hey community! I am currently and sadly a GS4 user with AT&T. Have had to deal with safestrap which im thankful for, never a full unlock. Just purchased a G3 off swappa. Definitely looking forward to having full control over my device without restrictions.
Read around and rooting is obviously easy. Custom recovery is what im going to be looking into next. Whats your current rom if running custom? If your still on stock, why?
Cheers
dankify said:
Hey community! I am currently and sadly a GS4 user with AT&T. Have had to deal with safestrap which im thankful for, never a full unlock. Just purchased a G3 off swappa. Definitely looking forward to having full control over my device without restrictions.
Read around and rooting is obviously easy. Custom recovery is what im going to be looking into next. Whats your current rom if running custom? If your still on stock, why?
Cheers
Click to expand...
Click to collapse
Hello and welcome! I think you'll find the G3 to be a great device, especially now that there is development for it. I am running my Candy5 ROM. It's based on CM12 with some goodies added. Give it a shot once you get TWRP flashed. You won't regret it :good:
timmytim said:
Hello and welcome! I think you'll find the G3 to be a great device, especially now that there is development for it. I am running my Candy5 ROM. It's based on CM12 with some goodies added. Give it a shot once you get TWRP flashed. You won't regret it :good:
Click to expand...
Click to collapse
Awesome. I did check that one out. And is already downloaded. I will be playing around with that one and of of course cm12.
Thanks
I'm still using cloudy ROM from the international thread. It is based off of the international stock kit Kat build. Everything works perfectly.
Sent from my LG-D850 using XDA Premium HD app
I was exactly like you except still had my s4 on mf3 firmware (which I passed down to my gramps): I got my g3 a lil after black Friday and love it. I'm running on pa 4.4.4 still since the battery life is phenomenal and basically no bugs. I do plan on going onto cm12 in the near future I think since its gone 'official' a few days ago. Btw I rooted mine with purpledrake
LG D-850
I'm a little confused. Wasn't the whole bumping thing website removed? Can development still happen if roms and kernels can't be bumped?
waiters said:
I'm a little confused. Wasn't the whole bumping thing website removed? Can development still happen if roms and kernels can't be bumped?
Click to expand...
Click to collapse
the website was removed because someone open sourced it so things can still be bumped
dankify said:
Hey community! I am currently and sadly a GS4 user with AT&T. Have had to deal with safestrap which im thankful for, never a full unlock. Just purchased a G3 off swappa. Definitely looking forward to having full control over my device without restrictions.
Read around and rooting is obviously easy. Custom recovery is what im going to be looking into next. Whats your current rom if running custom? If your still on stock, why?
Cheers
Click to expand...
Click to collapse
[Apologies for the piggyback]
I just got an LG G3 a couple of days ago and still using my first Note (i717) as a tablet. I cannot believe how smooth and fast this thing is, originally I was going to get the Note 4 but I'd rather spend $1.09 than $249.99+tax. So here I am an LG G3 member and it's good to be back on the forums with a fresh device.
Until At&T stop acting like a little-baby-b***h and locking their devices, you can try the available tools and tricks to get by.
Intub8 said:
I'm still using cloudy ROM from the international thread. It is based off of the international stock kit Kat build. Everything works perfectly.
Sent from my LG-D850 using XDA Premium HD app
Click to expand...
Click to collapse
Do you mind sharing a link.... I tried to install the 1.2 version of Cloudy and it just boot looped....
Coldheat1906 said:
Do you mind sharing a link.... I tried to install the 1.2 version of Cloudy and it just boot looped....
Click to expand...
Click to collapse
http://forum.xda-developers.com/devdb/project/?id=6315#downloads
I also just got this phone and all I can say is wow. I had a S5 for a little white but I must say I honestly think this phone blows Samsung's flagship out of the water in all ways. Best phone I had to date.
Sent from my LG-D850 using XDA Free mobile app