[Q] What"s the word on dev support for note 3 (verizon)?

bossei

Senior Member
Oct 31, 2007
857
91
0
S-Off is a HTC thing. If we can get root, best chance for ROMs is going to be a safestrap method on the Note 3.
Ah didn't know about the HTC thing; that's the phone I'm on currently so I was aware of that feature. Good to know. Safestrap was also what I was looking for; thanks for the reminder. I'll be happy with just that. I just need a little flexibility with the phone however I can get it.
 
  • Like
Reactions: asianflavor

Banggugyangu

Senior Member
May 24, 2010
258
106
0
Correct me if I'm wrong but can't Custom Roms still be made and installed without the BL being unlocked? I thought there was a way to bypass it (S-OFF vs S-ON).
Bootsrapped recoveries allow the installation of custom ROMs, though you're stuck with not replacing the kernel.

Hashcode's Safestrap (a multi-boot capable bootstrap recovery) allows the use of kexec, which will execute a different kernel.

The 2 key differences with this and a full custom recovery on an unlocked bootloader are this:

1: Safestrap takes up a lot of room on internal storage (on my bionic I have about half of normal)

2: Kernel source code isn't usually released on locked bootloader phones leaving the devs to have to reverse engineer the device modules (drivers) for all the hardware in the phone.

That being said, T-mo's note 3 is unlocked. That means the source code for their kernel is probably going to be released. The only real difference should be the radios in the phone, so that same source code should mainly work for the kernel in ours. That would leave the only hardware needing a custom made module to be the radios, which other phones wouldn't work on kexec kernels without... so we know that the devs have done that before.

It's definitely a bigger monster for any dev to take on, but when they do, I don't see there being a dramatic difference in the capabilities of the phones based on locked or unlocked bootloaders. As I mentioned before, a side benefit of the locked bootloader is less chance to trip the knox warranty status.
 

bossei

Senior Member
Oct 31, 2007
857
91
0
Bootsrapped recoveries allow the installation of custom ROMs, though you're stuck with not replacing the kernel.

Hashcode's Safestrap (a multi-boot capable bootstrap recovery) allows the use of kexec, which will execute a different kernel.

The 2 key differences with this and a full custom recovery on an unlocked bootloader are this:

1: Safestrap takes up a lot of room on internal storage (on my bionic I have about half of normal)

2: Kernel source code isn't usually released on locked bootloader phones leaving the devs to have to reverse engineer the device modules (drivers) for all the hardware in the phone.

That being said, T-mo's note 3 is unlocked. That means the source code for their kernel is probably going to be released. The only real difference should be the radios in the phone, so that same source code should mainly work for the kernel in ours. That would leave the only hardware needing a custom made module to be the radios, which other phones wouldn't work on kexec kernels without... so we know that the devs have done that before.

It's definitely a bigger monster for any dev to take on, but when they do, I don't see there being a dramatic difference in the capabilities of the phones based on locked or unlocked bootloaders. As I mentioned before, a side benefit of the locked bootloader is less chance to trip the knox warranty status.
Thank you for the explanation. :good:
 

asianflavor

Senior Member
Oct 15, 2009
1,227
2,058
0
Momence
Ah didn't know about the HTC thing; that's the phone I'm on currently so I was aware of that feature. Good to know. Safestrap was also what I was looking for; thanks for the reminder. I'll be happy with just that. I just need a little flexibility with the phone however I can get it.
Not a problem. Been keeping an eye on this board to see what happens with the N3 since I'm not sure if I'm going to get this or the HTC One Maxx. If we get root and some form of recovery, I'm jumping to this phone.
 

bossei

Senior Member
Oct 31, 2007
857
91
0
Not a problem. Been keeping an eye on this board to see what happens with the N3 since I'm not sure if I'm going to get this or the HTC One Maxx. If we get root and some form of recovery, I'm jumping to this phone.
If this turns out to be too crazy I'll probably jump on the Maxx when it's released too.
 
  • Like
Reactions: asianflavor

DutchDogg54

Retired Forum Moderator
Aug 16, 2011
2,472
2,866
0
Des Moines, IA
2: Kernel source code isn't usually released on locked bootloader phones leaving the devs to have to reverse engineer the device modules (drivers) for all the hardware in the phone.

That being said, T-mo's note 3 is unlocked. That means the source code for their kernel is probably going to be released. The only real difference should be the radios in the phone, so that same source code should mainly work for the kernel in ours. That would leave the only hardware needing a custom made module to be the radios, which other phones wouldn't work on kexec kernels without... so we know that the devs have done that before.

It's definitely a bigger monster for any dev to take on, but when they do, I don't see there being a dramatic difference in the capabilities of the phones based on locked or unlocked bootloaders. As I mentioned before, a side benefit of the locked bootloader is less chance to trip the knox warranty status.
Good explanation here man, but thought I'd share this good news from Android Police:

Samsung Releases Kernel Source Files For The Verizon Galaxy Note 3 (SM-N900V)
 

chefb

Senior Member
Dec 29, 2010
180
17
0
I've been reading about Knox...supposedly it won't stop root! But records that the phone has been rooted. Now ....why is this new?? Haven't root allways killed warrenties...whyb should we care?
 

DutchDogg54

Retired Forum Moderator
Aug 16, 2011
2,472
2,866
0
Des Moines, IA
I've been reading about Knox...supposedly it won't stop root! But records that the phone has been rooted. Now ....why is this new?? Haven't root allways killed warrenties...whyb should we care?
Root has not always killed warranties, maybe very early on in the smartphone scene...like 2007 early. It's quite a detailed situation though with different policies among nearly all the carriers. It'd be best to google it and be prepared to read for a few hours to know where everyone stands.