Database Users

Unlock Bootloader without Moto Site

I made excite? jajajja .... no, I have no way to unlock just open this topic to see if anyone knows how to unlock the devices that do not have developers edition

From what I understand you have an XT926 which can't be unlocked. Only the XT925 & XT926 dev edition can be unlocked through Motorola
Sent from my XT925 using xda app-developers app

saloums7 said:
From what I understand you have an XT926 which can't be unlocked. Only the XT925 & XT926 dev edition can be unlocked through Motorola
Sent from my XT925 using xda app-developers app
Click to expand...
Click to collapse
I have xt925 but i think is not the dev edition

juan272 said:
I have xt925 but i think is not the dev edition
Click to expand...
Click to collapse
There is only 1 version of the XT925 and it can be unlocked through Moto the steps are detailed on the moto page
Sent from my XT925 using xda app-developers app

saloums7 said:
There is only 1 version of the XT925 and it can be unlocked through Moto the steps are detailed on the moto page
Sent from my XT925 using xda app-developers app
Click to expand...
Click to collapse
I put the fastboot code into moto page but they say that my device not support bootloader unlock

Is that the only restriction? If a code is it, you could just use a fake code, or hex exit in a new code to the unlocking program.
Sent from my DROID RAZR HD using Tapatalk 2

juan272 said:
I put the fastboot code into moto page but they say that my device not support bootloader unlock
Click to expand...
Click to collapse
Double check to make sure you entered the correct code its pretty big might be a typo in there
Sent from my XT925 using xda app-developers app

saloums7 said:
Double check to make sure you entered the correct code its pretty big might be a typo in there
Sent from my XT925 using xda app-developers app
Click to expand...
Click to collapse
I try about 20 times!!!!!!

If you have any apps frozen, unfreeze them and reboot and maybe that will work. If you've removed anything from withing /system, put it back and put the correct permissions and if you don't have those files (if there was anything deleted) then perhaps someone can provide them for upload, then give that a try.
Lastly, if you flashed a ROM that isn't from you carrier or your country, then perhaps using the appropriate tools (I haven't used them so can't point out what they are, other than to say they exist) to put the stock ROM back will allow you to unlock.
Last resort, you can try to get it replaced under warranty stating that you're a developer and need this feature, however if you're rooted I would guess that they'd would be a lot more inclined to check for that replacing a handset as rooting voids the warranty and unrooting, sadly, doesn't remove the info stored on the device that checks to see if the phone had been rooted in the past. You can unroot and if your countries laws are protective enough, though, you might be able to ask them to show how rooting the device caused the failure. In my case, the contract was signed with my carrier who has to be certified as a reseller and they never showed me any warranty documentation, so I was locked into the purchase of the handset over 24 months and am covered by the verbal details of the warranty, which were "everything but physical damage" since they unboxed it and handed it to me activated after I signed. It wouldn't be hard to cancel my contract and hand back the handset if I was refused a warranty repair on these grounds. That they opened the box without me asking is probably enough. That said, consumer protection is top notch in world here.
Short version of the last part though, you can always try a warranty replacement. You'd have to look into if there's a fee in the case that you weren't covered by the warranty. As long as the bootloader is unlocked (and you aren't rooted), you still have you're warranty since the code didn't activate, and I haven't read the page thoroughly enough, but if the page says receiving the code voids the warranty then you can still argue that it was defective prior to receiving it by citing that the code didn't work. If you can unroot, and you live somewhere that the issue of the evidence of your root, or whatever, can be easily turned over to a consumer protection body, then it might be worth the trouble.
Also, you can probably call and ask for a new code. Any way you go about doing any of the above though though, be persistently polite. It goes a long way over trying to be forceful.
I'm likely about to unlike my phone by the way, assuming I can find a ROM that looks appealing enough to try out. I'll try it with the multitude of frozen system apps and the handful of additional ones still in place, first, and see how it goes.

Would it be possible to root the droid razr maxx hd if it is not a the developers edition?? Please help.

brian_199 said:
Would it be possible to root the droid razr maxx hd if it is not a the developers edition?? Please help.
Click to expand...
Click to collapse
If you're on JB then you need to downgrade to ICS using the appropriate ROM for your carrier, use a tool to root, download an app that will allow you to bakcup the root and unroot the device, then upgrade to ICS, then reinsert the root. The instructions are scattered because there's 2 differant models of the phone to deal with and there isn't any consolidated thread that involves all those steps. I haven't had to downgrade and have a differant model than what the maxx version is so that's really as much help as I can be, but the answer is supposedly "yes, you can do this" and its the prefered way for a lot of people from what I gather.
Be sure to backup any data on your sdcard before you begin. I didn't lose any since mine was just keeping root on an OTA upgrade from ICS to JB, but I don't know if you lose it or now when you downgrade.
Hopefully someone else can be more helpful that what I was. There are threads where various carrier versions for both ICS and Jellybean are hosted, as well, so you'lle need to find your carrier's ICS. If it isn't available in the thread then search my posts and someone linked me off to a download for a Telstra ROM and further back in the URL revelealed hosting a heap of ROMS though I wouldn't know which one you would need specifically.
The only issue I ran into, though my experience is possibly only covering half of what's involved for you, was that after I reinserted root, only apps that had permission prior to the upgrade had root permission; I couldn't add any. Other people have had a problem with superuser being inserted with wrong file permissions. The thing I did was to update the binary, this didn't work, then installed SuperSu and updated the binary which also didn't work, then I did a cleanup for installing another su app from the market from withing SuperSU... can't remember from this point, either installed another root app or uninstalled and reinstalled SuperSu (which scared the hell out of me I'd lose root at the time so I think this is what I did), then updated the binary and things were fine. Note that I never uninstalled the regular SU app that the injection tool for ICS put on the phone during this process though. At the end of it, I ended up with SuperSU and no normal su, which the injection tool installs. There hasn't been a huge issue with this though it has happened to some others.

Developer vs Normal

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.

Need help rooting Razr M

I want to root my Razr M and need assistance as I've never rooted a phone before. Could someone link me a safe guide that I can use? My phone is that "Not for sale. Motorola Mobility Confidential Restricted Property" version and it apparently can't seem to detect any kitkat update(even though razr m has the update). So I'm going to root it and update it to kitkat. I'm not a noob per say, just that I haven't ever rooted a phone and have least bit knowledge about cellphones.

ijx092 said:
I want to root my Razr M and need assistance as I've never rooted a phone before. Could someone link me a safe guide that I can use? My phone is that "Not for sale. Motorola Mobility Confidential Restricted Property" version and it apparently can't seem to detect any kitkat update(even though razr m has the update). So I'm going to root it and update it to kitkat. I'm not a noob per say, just that I haven't ever rooted a phone and have least bit knowledge about cellphones.
Click to expand...
Click to collapse
Update it first, root with Towel Root, then unlock the bootloader.
Sent from my HTC6525LVW using Tapatalk

RikRong said:
Update it first, root with Towel Root, then unlock the bootloader.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
He says his phone can not detect the update. He cannot update, is his point I believe. Does towelroot work on jellybean or is it just for the newer kernels and what not?
Sent from my DROID RAZR M using XDA Premium 4 mobile app

I got it to work on the .3 jb
Sent from my XT907 using XDA Premium 4 mobile app

ijx092 said:
I want to root my Razr M and need assistance as I've never rooted a phone before. Could someone link me a safe guide that I can use? My phone is that "Not for sale. Motorola Mobility Confidential Restricted Property" version and it apparently can't seem to detect any kitkat update(even though razr m has the update). So I'm going to root it and update it to kitkat. I'm not a noob per say, just that I haven't ever rooted a phone and have least bit knowledge about cellphones.
Click to expand...
Click to collapse
if towelroot doesnt work...I rooted my razr m (4.1.2....98.30.1) a couple months ago with this method http://forum.xda-developers.com/showthread.php?t=2565758 should give you clean and easy to follow instructions

I wonder if his boot loader is locked.
Fwiw kitkat killed my battery life.
Sent from my XT907 using XDA Free mobile app

poppers162 said:
He says his phone can not detect the update. He cannot update, is his point I believe. Does towelroot work on jellybean or is it just for the newer kernels and what not?
Sent from my DROID RAZR M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Update it the exact same way 90% of us did, with Samuri's tool on Droidrzr. ?
Sent from my HTC6525LVW using Tapatalk

how to check if bootloader is locked?
I don't want to deal with anything that is going to brick my phone. I cannot afford it. Please, make sure whatever you recommend doesn't do so.

ijx092 said:
how to check if bootloader is locked?
I don't want to deal with anything that is going to brick my phone. I cannot afford it. Please, make sure whatever you recommend doesn't do so.
Click to expand...
Click to collapse
power off phone...hold volume up+volume down+power button...when a menu comes up select apfastboot...if ait says status code:3 then your unlocked

ijx092 said:
how to check if bootloader is locked?
I don't want to deal with anything that is going to brick my phone. I cannot afford it. Please, make sure whatever you recommend doesn't do so.
Click to expand...
Click to collapse
Everything has the potential to go bad. So, if you're not willing to accept that, modifying is not for you. With that being said, Sam's update is easy to use if you follow the directions. Once updated, root and unlocking the bootloader are also easy.
Update tool: http://www.droidrzr.com/index.php/topic/45495-how-to-xt907-upgrade-to-kitkat-ota/
Root tool: http://www.droidrzr.com/index.php/topic/46155-rootunlock-razr-hdm-build-183-kitkat-towel-root/
Sent from my HTC6525LVW using Tapatalk

crazy4android said:
power off phone...hold volume up+volume down+power button...when a menu comes up select apfastboot...if ait says status code:3 then your unlocked
Click to expand...
Click to collapse
It says device is UNLOCKED, Status Code: 1

RikRong said:
Everything has the potential to go bad. So, if you're not willing to accept that, modifying is not for you. With that being said, Sam's update is easy to use if you follow the directions. Once updated, root and unlocking the bootloader are also easy.
Update tool: http://www.droidrzr.com/index.php/topic/45495-how-to-xt907-upgrade-to-kitkat-ota/
Root tool: http://www.droidrzr.com/index.php/topic/46155-rootunlock-razr-hdm-build-183-kitkat-towel-root/
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
ijx092 said:
It says device is UNLOCKED, Status Code: 1
Click to expand...
Click to collapse
follow @RikRong post instructions...that should be no problem...it takes time but it really not that difficult ..its more of a mind thing..you'll feel dumb for bein so hesitant to begin with...

crazy4android said:
follow @RikRong post instructions...that should be no problem...it takes time but it really not that difficult ..its more of a mind thing..you'll feel dumb for bein so hesitant to begin with...
Click to expand...
Click to collapse
My device is unlocked, right? I just have to root it?

ijx092 said:
My device is unlocked, right? I just have to root it?
Click to expand...
Click to collapse
If it says that then yes, yes it is. ..
Sent from my XT907 using XDA Premium 4 mobile app

[Request] Root for Z3C (D5803) -> Solved

HI @all,
now that we have a FW for the device - is root possible?
All known root methods are not working.
BR
UserX10
Edit:
Solved -> Thanks you DooMLoRD
http://forum.xda-developers.com/z3-...58xx-cwm-based-recovery-6-0-4-7-root-t2890231

Delete.

Jeez.
People haven't even got their hands on the phone yet...
Be patient

Anyone wanna try Framaroot?
http://framaroot.net/index.html

framaroot does not work ...

Ok because I saw it posted on this blog and thought it would work. Strange!

plisk3n said:
Ok because I saw it posted on this blog and thought it would work. Strange!
Click to expand...
Click to collapse
Well, it says "tested on device" and is from 9/4, before the device was even unavailable. I'd be careful that apk isn't something more.

CollinsJ said:
Well, it says "tested on device" and is from 9/4, before the device was even unavailable. I'd be careful that apk isn't something more.
Click to expand...
Click to collapse
Yeah that's also the reason why I decided not to download it, I'll just wait till someone @ XDA finds a way to root the device. It's not like we'll die because our device isn't rooted for x weeks/months.

Weeks/months?! I would die! It's been a day and the amount of things I can't do is driving me nuts!

If you have an unlocked boot loader see what I say at http://forum.xda-developers.com/showthread.php?p=55709585. If you don't I think you'll be waiting for a while - someone needs to find an exploit and write the app/code needed to exploit it. This has become increasingly hard as Android has become more secure - before Towelroot AFAIK the Z1/Z2 was not rootable for a long time. You'd probably be waiting a similar length of time for the next big root exploit.

tilal6991 said:
If you have an unlocked boot loader see what I say at http://forum.xda-developers.com/showthread.php?p=55709585. If you don't I think you'll be waiting for a while - someone needs to find an exploit and write the app/code needed to exploit it. This has become increasingly hard as Android has become more secure - before Towelroot AFAIK the Z1/Z2 was not rootable for a long time. You'd probably be waiting a similar length of time for the next big root exploit.
Click to expand...
Click to collapse
Would it not be helpful to contact Sony themselves? They're increasingly developer friendly, these days. Maybe they'd be willing to offer pointers to root app developers?

mudnightoil said:
Would it not be helpful to contact Sony themselves? They're increasingly developer friendly, these days. Maybe they'd be willing to offer pointers to root app developers?
Click to expand...
Click to collapse
Well I know people at Sony and long story short: if you want root unlock the boot loader. Its as simple as that. You have to understand that while a root exploit looks nice to tinkerers its also a serious security issue which must be fixed - that is why many root solutions also patch the exploit they use after using it.

Does unlocking the bootloader require wiping the phone? I know this is required on the nexus phones. If it requires wipe then its the very first thing I'm doing once I get the phone out of the box.
Sent from my Nexus 5 using Tapatalk

tilal6991 said:
Well I know people at Sony and long story short: if you want root unlock the boot loader. Its as simple as that. You have to understand that while a root exploit looks nice to tinkerers its also a serious security issue which must be fixed - that is why many root solutions also patch the exploit they use after using it.
Click to expand...
Click to collapse
I'm aware of this ... but on the one hand being one of the few if only manufacturers to provide official unlocking for the bootloaders (with the obvious intention of spurring development etc), but on the other actively closing non-simple (i.e. ones requiring a dedicated program) root 'exploits' would seem a little at odds. Is it really that black and white? You'd think it might be in their interests to provide an official complex / secure rooting method.

sublimnl said:
Does unlocking the bootloader require wiping the phone? I know this is required on the nexus phones. If it requires wipe then its the very first thing I'm doing once I get the phone out of the box.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes. It will wipe everything AFAIK - double check with the website.
mudnightoil said:
I'm aware of this ... but on the one hand being one of the few if only manufacturers to provide official unlocking for the bootloaders (with the obvious intention of spurring development etc), but on the other actively closing non-simple (i.e. ones requiring a dedicated program) root 'exploits' would seem a little at odds. Is it really that black and white? You'd think it might be in their interests to provide an official complex / secure rooting method.
Click to expand...
Click to collapse
Your statements contradict themselves. Rooting without unlocking the bootloader needs a security flaw. How can any method which leaves a security hole be secure?
Bootloader unlocking gets around this by letting you control the boot partition of the device so you can disable the "security barrier" that android provides. This is a choice you are explicitly making which is why it is the only "secure" way to root.

Does towelroot work?

MrOeyta said:
Does towelroot work?
Click to expand...
Click to collapse
Unfortunately Towelroot does not work.

I've read some people saying that unlocking the bootloader causes you to lose your DRM keys which apparently would affect software/ camera issues?
Can anyone verify this?

tacocats said:
I've read some people saying that unlocking the bootloader causes you to lose your DRM keys which apparently would affect software/ camera issues?
Can anyone verify this?
Click to expand...
Click to collapse
This is very true. On the z1c I neglected to back up the TA partition. And apparently lost native mirror cast and some camera features when I rolled the device back to stock.
Back up your TA partition before unlocking BL.

dillalade said:
This is very true. On the z1c I neglected to back up the TA partition. And apparently lost native mirror cast and some camera features when I rolled the device back to stock.
Back up your TA partition before unlocking BL.
Click to expand...
Click to collapse
Any idea how this could be done?

ALL THINGS ROOT, BOOTLOADER, ETC

Good day all,
I noticed several cluttered threads in Q&A that are becoming more of a discussion than question and answer format.
I wanted to make this thread as a one stop shop for all things Root and Bootloader related for the G-930T (Tmobile Galaxy Note 7).
Please discuss root, bootloader and work with each other in here.
Please do not discuss the bounty in here, and do not clutter the bounty thread with casual conversation about root.
Cheers,
Baja
Sent from my SM-N930T using XDA-Developers mobile app

Well we know the Bootloader is locked and can only be unlocked by Samsung( That's not gonna happen).
Based on what happened and is continuing to happen with the S7 there is a possibility of achieving Root on the N7(ENG) which I will not be a guinea pig and try. I'm sure others will if and when it's available.

SBERG117 said:
Well we know the Bootloader is locked and can only be unlocked by Samsung( That's not gonna happen).
Based on what happened and is continuing to happen with the S7 there is a possibility of achieving Root on the N7(ENG) which I will not be a guinea pig and try. I'm sure others will if and when it's available.
Click to expand...
Click to collapse
I second this. Just wish we could keep samsung pay after root. Not gonna happen but wishful thinking.
Sent from my SM-N910T3 using Tapatalk

Just want to note that you may not want to take any updates if you plan on rooting in the future (if an exploit is available).

dirtymindedx said:
I second this. Just wish we could keep samsung pay after root. Not gonna happen but wishful thinking.
Sent from my SM-N910T3 using Tapatalk
Click to expand...
Click to collapse
Not true on my Nexus 6 we could not use Android pay with root. But someone came up with a walk around systemless root and it worked.
Sent from my SM-N930T using Tapatalk

jason504 said:
Not true on my Nexus 6 we could not use Android pay with root. But someone came up with a walk around systemless root and it worked.
Sent from my SM-N930T using Tapatalk
Click to expand...
Click to collapse
he said Samsung pay...two separate paying system

Chord_Hugo87 said:
he said Samsung pay...two separate paying system
Click to expand...
Click to collapse
No I know what he said but if there can be a walk around for one (should) be able to do one for the other.
Sent from my SM-N930T using Tapatalk

jason504 said:
No I know what he said but if there can be a walk around for one (should) be able to do one for the other.
Sent from my SM-N930T using Tapatalk
Click to expand...
Click to collapse
not possible if you trip knox and in order to get root you need to trip knox.

jason504 said:
No I know what he said but if there can be a walk around for one (should) be able to do one for the other.
Sent from my SM-N930T using Tapatalk
Click to expand...
Click to collapse
One of them is from Google and doesn't care about Knoxx and the other is from Samsung and does care about Knoxx. Two completely different things. The Samsung Pay not working after Knoxx is tripped has been going on for a year as of tomorrow. The systemless root that doesn't trip Knoxx is one thing but as soon as you start flashing, kiss Samsung Pay goodbye.

Yep, and worst of all. Once it's tripped, Samsung pay will never work again on that device
Sent from my SM-N930T using XDA-Developers mobile app

Luckily for me, if root becomes available its a no-brainer. Samsung pay doesn't support my bank, and I won't have a credit card. Even if Samsung Pay would work for me, it would still be an easy choice to have root instead. I would like to play around with altering the speaker volume, deleting bloatware, making tweaks, ad blocking, etc.

Did anyone ever get the files that Beans asked for over to him?

Why can't those of us with t variants just flash the unlocked w8 bootloader? Seems like we've been left an out? Yes?
Sent from my SM-N920T using Tapatalk

Rx8Driver said:
Why can't those of us with t variants just flash the unlocked w8 bootloader? Seems like we've been left an out? Yes?
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
In order for you to flash anything to any bootloader, it needs to be unlocked. With it locked Odin says it can't. So till the note 7 gets unlocked (in time) we have to wait. Phone only few days old, be work around soon.

drum747 said:
Did anyone ever get the files that Beans asked for over to him?
Click to expand...
Click to collapse
Good question
@BeansTown106 did you ever get a Tar?
Sent from my SM-N930T using XDA-Developers mobile app

It appears this guy is in the process of getting the stock firmware uploaded
http://forum.xda-developers.com/showthread.php?t=3444003
Sent from my SM-N930T using XDA-Developers mobile app

ethanscooter said:
Just want to note that you may not want to take any updates if you plan on rooting in the future (if an exploit is available).
Click to expand...
Click to collapse
That is true. Android 7 Nougat will have more security features that Samsung is going to take advantage of with the Galaxy Note 7. That may make unlocking bootloader and rooting even more difficult.
-

It looks like the sprint guys have obtained an engineering bootloader/kernel. Someone may be able to do something with this for us..
Sent from my SM-N930T using XDA-Developers mobile app

I got the stock n930t boot.img but im wondering is how would i go by making a kernel "engboot". I also removed dm-verity but that didn't work. All i get is a failed message through odin. Another testing i have done is I even just modified one simple thing in the stock kernel say in default.prop ro.secure=1 to =0 and i still get a failed messsge. Once i flashed the stock unmodified version of the kernel i would get a success message and works which means any modification to the kernel will cause it to fail i just have to see what in the kernel checks for md5 changes or it may be something else if more devs can help together, then we can get this working.

jovy23 said:
I got the stock n930t boot.img but im wondering is how would i go by making a kernel "engboot". I also removed dm-verity but that didn't work. All i get is a failed message through odin. Another testing i have done is I even just modified one simple thing in the stock kernel say in default.prop ro.secure=1 to =0 and i still get a failed messsge. Once i flashed the stock unmodified version of the kernel i would get a success message and works which means any modification to the kernel will cause it to fail i just have to see what in the kernel checks for md5 changes or it may be something else if more devs can help together, then we can get this working.
Click to expand...
Click to collapse
Bro, please stop trying. This is obviously far above your skill level.
1. There is no way to convert a kernel to an "engboot."
2. The bootloader is LOCKED, so anything you do to the kernel's ramdisk will obviously not work because the whole point of dm-verity and a locked bootloader, among other things, is to stop the modification of system images, including the kernel ramdisk. Surely you didn't think it would be as easy as unpacking the boot.img, changing the ro.secure value from 1 to 0, then repacking..... did you?
3. The kernel doesn't "check" for anything MD5 related.
4. The bootloader is rejecting your changes, not the kernel.
5. Nothing you do to the boot.img, no matter how many devs you have, will do any good.
Hang tight, guys. We're trying everything we can.