Anyone know of any word on these two roms making a appearance here soon?
Sent from my SM-N900V using Tapatalk
There's like 8 of these threads already but long story short, no.
Sent from my SM-N900V using xda app-developers app
akellar said:
There's like 8 of these threads already but long story short, no.
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
Link me to the long story please
Sent from my Nexus 7 using Tapatalk 4
Jeremiah_1988 said:
Link me to the long story please
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Here's your long story short:
Until we get the bootloader unlocked, NONE of those ROMs will make it to this phone. Period.
carlz28 said:
Here's your long story short:
Until we get the bootloader unlocked, NONE of those ROMs will make it to this phone. Period.
Click to expand...
Click to collapse
Why do people keep saying this? I came from Droid Razr MAXX, locked bootloader. and officially supported by CM and AOKP.
If you dont believe me go here and select Razr Maxx and see. This is CM official download site. Not trying to argue, just sayin'. Dont be so sure we will not see that type of development.
http://wiki.cyanogenmod.org/index.php?title=Devices#vendor=;
willjohnson said:
Why do people keep saying this? I came from Droid Razr MAXX, locked bootloader. and officially supported by CM and AOKP.
If you dont believe me go here and select Razr Maxx and see. This is CM official download site. Not trying to argue, just sayin'. Dont be so sure we will not see that type of development.
http://wiki.cyanogenmod.org/index.php?title=Devices#vendor=;
Click to expand...
Click to collapse
Kind of what I thought, just going to try and wait patiently for more development
Sent from my Nexus 7 using Tapatalk 4
Again, they all use kexec or loki and neither will work on this device. Please read the other threads about this. They are all the same.
Sent from my SM-N900V using xda app-developers app
akellar said:
Again, they all use kexec or loki and neither will work on this device. Please read the other threads about this. They are all the same.
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
This.
Safestrap (at least at the moment) doesn't support kexec or Loki for this device, which is the way those other devices manage to run custom kernels. Not saying its impossible, but likely improbable.
carlz28 said:
This.
Safestrap (at least at the moment) doesn't support kexec or Loki for this device, which is the way those other devices manage to run custom kernels. Not saying its impossible, but likely improbable.
Click to expand...
Click to collapse
All i was saying, is that our device is way to new to be saying what it will or wont have development on in the future. Thats just my opinion.
i have an unlocked developer edition where is my cm/aosp then haha
oneandroidnut said:
i have an unlocked developer edition where is my cm/aosp then haha
Click to expand...
Click to collapse
Apparently there are a lot of problems getting it working on this device. If you will notice, none of the note 3's have it, not even the international. I think part of it is knox, part of it is the bootloader, part of it is the hardware on the device. Samsung went above and beyond to keep this phone running their system.
shiftr182 said:
Apparently there are a lot of problems getting it working on this device. If you will notice, none of the note 3's have it, not even the international. I think part of it is knox, part of it is the bootloader, part of it is the hardware on the device. Samsung went above and beyond to keep this phone running their system.
Click to expand...
Click to collapse
i dont know what the issue could be. tmobile and dev editions are unlocked bootloaders and you dont have to run knox so idk unless knox is baked in somewhere where you cant get around it
oneandroidnut said:
i dont know what the issue could be. tmobile and dev editions are unlocked bootloaders and you dont have to run knox so idk unless knox is baked in somewhere where you cant get around it
Click to expand...
Click to collapse
Unlocked does not equal aosp, at least functioning. Ril is likely an issue.
Sent from my SM-N900V using xda app-developers app
Sbrissen said he'd make it happen if he were to obtain a device...... Dev Edition....
TechSavvy2 said:
Sbrissen said he'd make it happen if he were to obtain a device...... Dev Edition....
Click to expand...
Click to collapse
i have a friends bricked note 3 he can get haha
Related
I am running 4.2.2 with amf3. Is this rootable yet? Sorry for the dumb question. Haven't been on in a while
gwell1 said:
I am running 4.2.2 with amf3. Is this rootable yet? Sorry for the dumb question. Haven't been on in a while
Click to expand...
Click to collapse
Yep look in the general section.
Sent from my SAMSUNG-SGH-I337 using xda premium
It's rootable but you won't be able to flash ROMS, yet.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
r8revealed said:
It's rootable but you won't be able to flash ROMS, yet.
Click to expand...
Click to collapse
n00b here...
Then what is the point of rooting?
I want to get 4.3. :crying:
You will be able to install root access apps and certain mods. I personally don't find if useful at the moment, so I'll be waiting for a bootloader unlock. (Which is what is actually needed for flashing ROMS).
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
r8revealed said:
You will be able to install root access apps and certain mods. I personally don't find if useful at the moment, so I'll be waiting for a bootloader unlock. (Which is what is actually needed for flashing ROMS).
Click to expand...
Click to collapse
That was my thought too.
John D'oh said:
n00b here...
Then what is the point of rooting?
I want to get 4.3. :crying:
Click to expand...
Click to collapse
With Root (and a locked bootloader) you can do TONS of stuff.
- Install and use TiBu
- Change framework for unlocking many neat customizations
- Remove/disable bloatware
- Allow for wifi tethering
- Disable ads
- Change startup/shutdown/system sounds
- Change bootup animations
- etc..
Just because you have a locked bootloader does not mean you have no use for root.
John D'oh said:
n00b here...
Then what is the point of rooting?
I want to get 4.3. :crying:
Click to expand...
Click to collapse
You can install the Xposed Framework and add a multitude of various mods to your setup. I used it when waiting for the original boot loader work around. Its quite nice actually. The amount of options have only expanded since that time. Check it out.
Here: http://forum.xda-developers.com/showthread.php?t=2285074
Sent from my AT&T Galaxy S4 I337
Mike said:
You can install the Xposed Framework and add a multitude of various mods to your setup. I used it when waiting for the original boot loader work around. Its quite nice actually. The amount of options have only expanded since that time. Check it out.
Click to expand...
Click to collapse
Thanks!
BTW, is there a way to get this phone to check for updates from G instead of ATT so we can get 4.3 that way?
John D'oh said:
Thanks!
BTW, is there a way to get this phone to check for updates from G instead of ATT so we can get 4.3 that way?
Click to expand...
Click to collapse
No
joeybear23 said:
With Root (and a locked bootloader) you can do TONS of stuff.
- Install and use TiBu
- Change framework for unlocking many neat customizations
- Remove/disable bloatware
- Allow for wifi tethering
- Disable ads
- Change startup/shutdown/system sounds
- Change bootup animations
- etc..
Just because you have a locked bootloader does not mean you have no use for root.
Click to expand...
Click to collapse
But every time I boot up my phone it has an unlocked logo under the word Samsung. Why is that ?
Sent from my SAMSUNG-SGH-I337 using xda premium
vividblu2020 said:
But every time I boot up my phone it has an unlocked logo under the word Samsung. Why is that ?
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
Use the search function and search the forums for "sysscope" or "custom" or visually search for threads that have that subject in the title. You should find tons of information about it within the first page or two of the "general" and "Q&A" sub forums.
vividblu2020 said:
But every time I boot up my phone it has an unlocked logo under the word Samsung. Why is that ? Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
There are several threads about it here on XDA. It's the Samsung screen notice that you've changed their OS. Sort of like the old triangle on the S2 when you trip the rom-flash counter.
I was able to eliminate the unlocked lock symbol using Chainfire's Triangle away (might be on XDA, but I bought it on Play).
Read the caveats and decide if you want to use it. . . worked for me on my i337 running SHOstock2.1!
Good Luck!
joeybear23 said:
With Root (and a locked bootloader) you can do TONS of stuff.
- Install and use TiBu
- Change framework for unlocking many neat customizations
- Remove/disable bloatware
- Allow for wifi tethering
- Disable ads
- Change startup/shutdown/system sounds
- Change bootup animations
- etc..
Just because you have a locked bootloader does not mean you have no use for root.
Click to expand...
Click to collapse
Perfect answer.
People around me always ask for root their phone for non of above
markbc01 said:
There are several threads about it here on XDA. It's the Samsung screen notice that you've changed their OS. Sort of like the old triangle on the S2 when you trip the rom-flash counter.
I was able to eliminate the unlocked lock symbol using Chainfire's Triangle away (might be on XDA, but I bought it on Play).
Read the caveats and decide if you want to use it. . . worked for me on my i337 running SHOstock2.1!
Good Luck!
Click to expand...
Click to collapse
So are you saying since I did this I may be able to flash something?
Sent from my SAMSUNG-SGH-I337 using xda premium
vividblu2020 said:
So are you saying since I did this I may be able to flash something?
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
If you are on mf3 you can't flash anything...you have no custom recovery as there is no way to get a custom recovery for mf3 at the moment
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
vividblu2020 said:
So are you saying since I did this I may be able to flash something?
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
The answer is "yes," UNLESS your stock rom is version is MF3, in which case the answer is "NO...for now," as mg2195 just mentioned and explained in the preceding post. . .
markbc01 said:
The answer is "yes," UNLESS your stock rom is version is MF3, in which case the answer is "NO...for now," as mg2195 just mentioned and explained in the preceding post. . .
Click to expand...
Click to collapse
That sucks. Well hopefully the developers will be able to figure out a way
Sent from my SAMSUNG-SGH-I337 using xda premium
mg2195 said:
If you are on mf3 you can't flash anything...you have no custom recovery as there is no way to get a custom recovery for mf3 at the moment
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
There's a post in the general section talking about flashing carrier Roms. So if I rooted and say installed a twrp using ROM toolbox to flash these Roms, including "loki'd" and my carrier kernel wouldn't that work ?
Sent from my SAMSUNG-SGH-I337 using xda premium
vividblu2020 said:
There's a post in the general section talking about flashing carrier Roms. So if I rooted and say installed a twrp using ROM toolbox to flash these Roms, including "loki'd" and my carrier kernel wouldn't that work ?
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
If you're on the mf3 firmware you can't install twrp. And don't try as you will probably brick your phone. Do you know what firmware you're on?
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...
So I have been restoring to stock every time I flash a new rom, even when updating, and for some reason, after going to stock with odin, my phone usually doesn't boot up, so I go to the samsung recovery and the little android guy is dead and the front door hatch thing is open with a red triangle and exclamation mark, I usually just wipe data from here and it boots, but I have always seen this and I am not sure why. Anyone know why?
Thanks
Joe
Edit* I might add that when I go to wipe, the guy stands up and it looks fine but then he goes back down.
Have you tried doing a factory reset directly after using ODIN?
scott14719 said:
Have you tried doing a factory reset directly after using ODIN?
Click to expand...
Click to collapse
Yes, infact I usually have to just to have it not hang at the samsung screen after the stock boot animation
Are you MF3 or AMDL?
Sent from my SGH-I337 using XDA Premium 4 mobile app
joeym11 said:
Yes, infact I usually have to just to have it not hang at the samsung screen after the stock boot animation
Click to expand...
Click to collapse
That's normal, you almost always have to do a factory reset after Odin. Otherwise you'll get a boot loop.
Br4nd3n said:
Are you MF3 or AMDL?
This makes no sense to ask. He clearly states that he flashes custom ROMs and uses Odin to flash back to stock.
Sent from my SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my SGH-I337 using Xparent Green Tapatalk 2
Br4nd3n said:
Are you MF3 or AMDL?
Sent from my SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Not sure what that means
joeym11 said:
Not sure what that means
Click to expand...
Click to collapse
If you don't know what that means than you sure as hell shouldn't be flashing Roms or anything like that because if you dont know the basics than you sure don't need to be stepping up on a course from the basics. Take your time to read before messing with your phone and end up with a $600 paperweight.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
I have been rooting and flashing for 2 years now, across 3 different phones, and I have never heard those words. How about you just reply with what they actually mean instead of stuff like that?
joeym11 said:
I have been rooting and flashing for 2 years now, across 3 different phones, and I have never heard those words. How about you just reply with what they actually mean instead of stuff like that?
Click to expand...
Click to collapse
Do you know what firmware you're on?
herbzilla said:
This makes no sense to ask. He clearly states that he flashes custom ROMs and uses Odin to flash back to stock.
Click to expand...
Click to collapse
There are ODIN files available for both MDL and MF3 and with Safestrap, custom ROMS can be flashed to MF3. So it is a fair question considering the OP didn't specify. However, it appears that the OP has a Canadian variant (Canadian carrier) which means my advice about the factory reset still stands.
joeym11 said:
I have been rooting and flashing for 2 years now, across 3 different phones, and I have never heard those words.
Click to expand...
Click to collapse
None of that matters. It doesn't matter what you knew about other phones, it matters what you know about THIS phone. Thinking previous knowledge of other phones is all you need will guarantee a brick with this one.
joeym11 said:
I have been rooting and flashing for 2 years now, across 3 different phones, and I have never heard those words. How about you just reply with what they actually mean instead of stuff like that?
Click to expand...
Click to collapse
How about you read instead of someone holding your hand and telling you what it is. If you haven't heard of them than by all means I'm glad something weird happened to your stock recovery because it doesn't matter what other phones you flashed Roms on all that matters is THIS phone and if you don't know anything about this phone especially KNOX than I suggest you read.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
[email protected] said:
How about you read instead of someone holding your hand and telling you what it is. If you haven't heard of them than by all means I'm glad something weird happened to your stock recovery because it doesn't matter what other phones you flashed Roms on all that matters is THIS phone and if you don't know anything about this phone especially KNOX than I suggest you read.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
It appears he's not asking about the meaning of, "what firmware are you on", but rather about the screwed up quote (post #6) herbzilla attempted asking, "This makes no sense to ask. He clearly states that he flashes custom ROMs and uses Odin to flash back to stock.".
Plus, he is on a Canadian carrier so "MDL" or "MF3" would mean nothing to him.
There is a lot of misunderstanding in this thread.
If I might add,he still needs to read all about his model phone .it gets tiring for some to see another thread about anything thats been covered already or is basic knowledge.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
jball said:
If I might add,he still needs to read all about his model phone .it gets tiring for some to see another thread about anything thats been covered already or is basic knowledge.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I completely agree. This hand-holding BS is getting old. People that don't read and at least try to learn should be banned for their own good. It is a development site after all. But unfortunately, that's not my decision.
The Verizon Note 3 variant N900V has had it's bootloader bypassed by @Hashcode and custom recovery has now been achieved on that device. I talked to @bajasur who is running their bounty thread and he believes that the same safestrap method could possibly be used on the N900A (our version). If @Hashcode can get this to work on the N900A I am sure development will move quickly so get over to our bounty thread and make your bounty pledges now!!! http://forum.xda-developers.com/showthread.php?t=2493369
See @bajasur's N900V Bounty Thread here...
http://forum.xda-developers.com/showthread.php?t=2473918
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Awesome!
Sent from my SAMSUNG-SM-N900A using Tapatalk
slidesear said:
Awesome!
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
Definitely great news!!!
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
I don't mean to be a downer, but I'm still on the fence whether I can get this working on the AT&T variant.
So let's hold off on any specific donations. :/
Fingers crossed! this would be great news!!!
Hashcode said:
I don't mean to be a downer, but I'm still on the fence whether I can get this working on the AT&T variant.
So let's hold off on any specific donations. :/
Click to expand...
Click to collapse
Pledges....meant pledges. Will update the OP...sorry @Hashcode.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
That would be pretty sweet
Sent from my SAMSUNG-SM-N900A using Tapatalk
Does this trip knox
Sent from my SM-N900W8 using Tapatalk
Canadoc said:
Does this trip knox
Sent from my SM-N900W8 using Tapatalk
Click to expand...
Click to collapse
At this point we will just have to wait and see what happens. I would imagine it doesn't but since it is currently being worked on and not confirmed we will have to just be patient...which I clearly wasn't with this thread.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Isn't this the same thing that happened with the s4? Bootloader exploited on verizon variant, didnt know if it would work for anyone else and it did?
Sent from my VS980 4G using Tapatalk
MrPlNK said:
Isn't this the same thing that happened with the s4? Bootloader exploited on verizon variant, didnt know if it would work for anyone else and it did?
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
The difference is ATT in addition to a locked bootloader made SELinux Enforcing. The VZW has permissive from what I've read.
mircury said:
The difference is ATT in addition to a locked bootloader made SELinux Enforcing. The VZW has permissive from what I've read.
Click to expand...
Click to collapse
I am probably completely wrong as Android is a different beast than regular Linux but, in the Linux OS world SELinux has little to do with the bootloader. It is a set of modules that load once the OS begins to boot up as part of the kernel in runlevel 1. So by the time the SELinux modules are loading you are already "booted". I hope this is the case for Android as well as I am past my 14 days on this phone and love the hardware I just would really like to be able to run some custom kernels and load AOSP based roms if I choose to. This is certainly the last phone I will be buying from AT&T regardless, so disappointed.
kennonk said:
I am probably completely wrong as Android is a different beast than regular Linux but, in the Linux OS world SELinux has little to do with the bootloader. It is a set of modules that load once the OS begins to boot up as part of the kernel in runlevel 1. So by the time the SELinux modules are loading you are already "booted". I hope this is the case for Android as well as I am past my 14 days on this phone and love the hardware I just would really like to be able to run some custom kernels and load AOSP based roms if I choose to. This is certainly the last phone I will be buying from AT&T regardless, so disappointed.
Click to expand...
Click to collapse
Normally it doesn't have anything to do with the bootloader but in this case since we can't crack or modify the bootloader we have to hijack the real /system into loading a recovery on a special partition along with a fake /system located on the internal sdcard. Whether or not SELinux enforcement policies prevent this or causes problems later if it does boot, we don't know yet. What it does do for sure is make it more difficult.
Same
kennonk said:
I am probably completely wrong as Android is a different beast than regular Linux but, in the Linux OS world SELinux has little to do with the bootloader. It is a set of modules that load once the OS begins to boot up as part of the kernel in runlevel 1. So by the time the SELinux modules are loading you are already "booted". I hope this is the case for Android as well as I am past my 14 days on this phone and love the hardware I just would really like to be able to run some custom kernels and load AOSP based roms if I choose to. This is certainly the last phone I will be buying from AT&T regardless, so disappointed.
Click to expand...
Click to collapse
Same here. I hate that AT&T is doing this. It's crazy how the tables have turned, as it used to be (As with the S4) we would get a way to flash a recovery before the VZW variant, but now it seems that has changed. Is the Knox option only on our variant or is it on VZW too?
I got super excited when I first saw this but then depressed when I found out that it hasn't fully been achieved... what is the difference from the way that the s4 was cracked? It had knox too didn't it?
Sent from my SAMSUNG-SM-N900A using Tapatalk HD
I have verizon and no it doesn't trip knox
tropazr said:
The Verizon Note 3 variant N900V has had it's bootloader bypassed by @Hashcode and custom recovery has now been achieved on that device. I talked to @bajasur who is running their bounty thread and he believes that the same safestrap method could possibly be used on the N900A (our version). If @Hashcode can get this to work on the N900A I am sure development will move quickly so get over to our bounty thread and make your bounty pledges now!!! http://forum.xda-developers.com/showthread.php?t=2493369
See @bajasur's N900V Bounty Thread here...
http://forum.xda-developers.com/showthread.php?t=2473918
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Any progress on unlocking bootloader of N900A?
We highly expect this.
Thank you.
SunnyOK said:
Any progress on unlocking bootloader of N900A?
We highly expect this.
Thank you.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=48555170
We have Safestrap now. Read up on it!
Sent from my SAMSUNG-SM-N900A using Tapatalk
SunnyOK said:
Any progress on unlocking bootloader of N900A?
We highly expect this.
Thank you.
Click to expand...
Click to collapse
Have you not looked in the development forums?
Sent from my SAMSUNG-SGH-I467 using Tapatalk 4
Agent said:
Have you not looked in the development forums?
Sent from my SAMSUNG-SGH-I467 using Tapatalk 4
Click to expand...
Click to collapse
Unfortunately the bootloader is still locked and hasn't been bypassed. What safestrap does is hijack the boot process once it reaches the /system partition. That is after the bootloader. It then runs a modified recovery. This is why you can't run custom kernels on it yet. The /boot partition is still protected. Don't get me wrong though it's a huge step in the right direction.
Haven't spent much time researching but time is short before Monday' sale/
Why would I want the developer edition over a standard designed phone. I'm just not quite understanding what the advantage of the developer version is. I do want to root if that's a factor.
Thanks.
homemadehitshow said:
Haven't spent much time researching but time is short before Monday' sale/
Why would I want the developer edition over a standard designed phone. I'm just not quite understanding what the advantage of the developer version is. I do want to root if that's a factor.
Thanks.
Click to expand...
Click to collapse
Two things:
1. You get to keep your warranty if you unlock the bootloader
2. You don't have to worry about root exploits for FUTURE OTA releases; current software already has root.
Other than that, they are identical devices except that you can customize the regular version.
chaoslimits said:
Two things:
1. You get to keep your warranty if you unlock the bootloader
2. You don't have to worry about root exploits for FUTURE OTA releases; current software already has root.
Other than that, they are identical devices except that you can customize the regular version.
Click to expand...
Click to collapse
Developer edition has root by default out of the box?
d14gvn said:
Developer edition has root by default out of the box?
Click to expand...
Click to collapse
No you don't have root out of the box. With developer edition, you can unlock the bootloader, flash a new recovery, and install su (root) using fastboot. You can do it at any time.
For the regular version, you need to root using Jcase's exploit (in the Development forum) which is also relatively easy to do.
chaoslimits said:
No you don't have root out of the box. With developer edition, you can unlock the bootloader, flash a new recovery, and install su (root) using fastboot. You can do it at any time.
For the regular version, you need to root using Jcase's exploit (in the Development forum) which is also relatively easy to do.
Click to expand...
Click to collapse
But with regular version you can flash TWRP recovery too and get SU with that, I see no difference in there.
I think the difference is in when you unlock your bootloader, developer edition doesn't lost its warranty
d14gvn said:
But with regular version you can flash TWRP recovery too and get SU with that, I see no difference in there.
I think the difference is in when you unlock your bootloader, developer edition doesn't lost its warranty
Click to expand...
Click to collapse
For now yes. If we get another OTA and no one makes a root exploit, the regular version may be stuck without root. If you care that much about having root, the dev edition is most likely the better choice. If you're not too worried about not having root in future OTAs (who knows if we'll actually get another major OS bump) the I guess the custom versions are going to be more interesting to you.
chaoslimits said:
For now yes. If we get another OTA and no one makes a root exploit, the regular version may be stuck without root. If you care that much about having root, the dev edition is most likely the better choice. If you're not too worried about not having root in future OTAs (who knows if we'll actually get another major OS bump) the I guess the custom versions are going to be more interesting to you.
Click to expand...
Click to collapse
Thank you for that information. :good:
Dev edition is also more "figure proof" whereas after motorola stop supporting the phone you can still get android updayes so long as there are devs building them.
Thanks for the info guys. I'm really considering upgrading from my Nexus 4. I would have preferred a different color but I think I'd go with the developer edition. I'm getting ready to go through the forums but how do you guys feel the developer support is compared to the Nexus 4? I use CWM recovery and like CM and AOSPA a lot. Does performance take a hit on custom ROMs compared to stock which is from my understanding highly optimized?
Sent from my Nexus 4 using XDA Premium 4 mobile app
homemadehitshow said:
Haven't spent much time researching but time is short before Monday' sale/
Why would I want the developer edition over a standard designed phone. I'm just not quite understanding what the advantage of the developer version is. I do want to root if that's a factor.
Thanks.
Click to expand...
Click to collapse
If you don't know why you need the developer edition, then you don't need the developer edition.
Sent from my XT1060 using Tapatalk
Can anyone speak to the LTE bands for ATT on DE? It looks like it has 17 covered but ATT can also use 4(?) and I think Wikipedia says 29 in the future. I'd hate to get it and stop getting LTE in areas I'm getting it in now.
1ManWolfePack said:
If you don't know why you need the developer edition, then you don't need the developer edition.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Says the guy with the Tapatalk sig.
homemadehitshow said:
Says the guy with the Tapatalk sig.
Click to expand...
Click to collapse
Lol.
I do use tapatalk. And I don't put an obnoxious signature. I leave it default.
That was a HARD DISS YO
Sent from my XT1060 using Tapatalk
1ManWolfePack said:
Lol.
I do use tapatalk. And I don't put an obnoxious signature. I leave it default.
That was a HARD DISS YO
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
I agree pretty harsh.....
Sent from my Nexus 7 using Tapatalk
mcsqwizzys98 said:
I agree pretty harsh.....
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
He just ripped on 87% of this community and doesn't even know it. Lol.
Anyways, for $400 - get the Dev. A true custom recovery and no root exploits needed.
SENT FROM MY TAPPED OUT CYAN PURPLE BUBBLE GUM TRANSPARENT WITH A CUSTOM KERNEL AND A CUSTOM ROM THAT I PAID FOR WITH MY OWN MONEY MOTOROLA MOBILITY MOTO X WITH SILVER HIGHLIGHTS AND NAVY BACK ON THE BIG RED NETWORK KNOWN AS VZW SENT FROM YOUR AUNTS HOUSE GO OBAMA
Sent from my XT1060 using Tapatalk
Oh I know it.
Sent from my electrical device.