Database Users

Why one should never unlock the Motorola Razr HD bootloader (xt925) !

The pro & cons of unlocking the bootloader:
Pro: Install customs ROMS with custom kernels (basically that's it)
Cons: - Loosing warranty from Motorola & your carrier
- No more firmware upgrades (your IMEI is dropped out of Motorola databank)
- Little verity of quality custom ROMs or development (close to none) exist for the Razr HD
- Future upgrade to JB & KLP will never happened (this phone is listed as a potential candidate for KLP update)
- Keeping your xt925 beyond your 1 year warranty will still guaranty, a steady upgrades of firmware
- Can root a phone with bootloader locked (without loosing warranty - root is reversible)
- Legally (Motorola binding Bootloader unlock contract), you can't sell a BL unlock Motorola Razr HD phone !
If someone can add some Pro's to an unlock bootloader please do it..

Are you sure about the firmware upgrades? I read somewhere that's not the case.

I wish I had known all this before I unlocked my phone.

Are you sure about the firmware upgrades? I read somewhere that's not the case.
Click to expand...
Click to collapse
I spoke to Motorola & my carrier services, also read the warning details before the unlock process begins.
I wish I had known all this before I unlocked my phone
Click to expand...
Click to collapse
Same here..(I learned all that after the fact)

I'd add this to Pro:
If you're stuck on Rogers 49003 ICS because you flashed the ROM trying to get root, your best option to get anything above 4.0.4 is to unlock bootloader?

Perhaps a CWM install will be possible for those with unlocked bootloaders when updates come.
It seems that in one form or another an unlocked bootloader means being able to push all the new files in doesn't it? Is there any limitation on this phone, for example flashing a new modem or kernel?

Cons one by one:
itzik_man said:
- Loosing warranty from Motorola & your carrier
Click to expand...
Click to collapse
True, but obvious.
itzik_man said:
- No more firmware upgrades (your IMEI is dropped out of Motorola databank)
Click to expand...
Click to collapse
Nope. Even if you were not to receive OTA, which by the way is not true as I've observed on my Photon Q, you can still freely flash the new firmwares yourself ^^
itzik_man said:
- Little verity of quality custom ROMs or development (close to none) exist for the Razr HD
Click to expand...
Click to collapse
Depends on ones point of view. Usually a CM port means you get newer Android sooner.
itzik_man said:
- Future upgrade to JB & KLP will never happened (this phone is listed as a potential candidate for KLP update)
Click to expand...
Click to collapse
Why it wouldn't? Unlocking BLs has no impact on upgrade schedule.
itzik_man said:
- Keeping your xt925 beyond your 1 year warranty will still guaranty, a steady upgrades of firmware
Click to expand...
Click to collapse
No. That's solely on Moto / Google decision. They don't have to update it at all. (See Droid 3, Milestone 3, Motorola XT720 etc.)
itzik_man said:
- Can root a phone with bootloader locked (without loosing warranty - root is reversible)
Click to expand...
Click to collapse
Yes, although you have to be careful, because there are scirpts checking if you're rooted.
itzik_man said:
- Legally (Motorola binding Bootloader unlock contract), you can't sell a BL unlock Motorola Razr HD phone !
Click to expand...
Click to collapse
You can sue Moto for breaking laws. They can't forbid you doing that (don't know honestly how is that in US / Canada, but I doubt that seeing how it works with computer games).
So please, while for normal user not willing to flash custom ROMs it's true that they should not unlock the bootloader, don't spill nonsenses around that. It's just that when you unlock your bootloader, you're on your own when playing with the firmware. But when you have stock firmware back on it, nothing prevents you from getting the OTA.

don't spill nonsenses around that. It's just that when you unlock your bootloader, you're on your own when playing with the firmware. But when you have stock firmware back on it, nothing prevents you from getting the OTA.
Click to expand...
Click to collapse
Possible 90% of your response represent just false theories..
OTA is goneforever once you unlock your bootloader ! If & when you be able manually to install JB, still your IMEI (not registered with Motorola) wont OTA.
You can sue nobody ! it's a contractual agreement you "sign" when you agree to unlock BL !
And if you can't OTA, No future auto upgrades.
So, before you use a statement "don't spill nonsense" make sure you are talking sense...

At least on my O2 Germany xt925 I got the update OTA from ICS to JB after unlocking. Had to return to the stock bootloader because the OTA relies on it after rebooting though.

itzik_man said:
Possible 90% of your response represent just false theories..
OTA is goneforever once you unlock your bootloader ! If & when you be able manually to install JB, still your IMEI (not registered with Motorola) wont OTA.
You can sue nobody ! it's a contractual agreement you "sign" when you agree to unlock BL !
And if you can't OTA, No future auto upgrades.
So, before you use a statement "don't spill nonsense" make sure you are talking sense...
Click to expand...
Click to collapse
Once again.
A) The reason why the page says "no updates" is beacuse OTA updates only work when you're on stock firmware, which is unlikely when you have the bootloader unlocked. That's all.
B) There are things that such "agreement" cannot contain. Being unable to sell the phone is one of them in most countries.

I disagree from the op.
Every change to device firmware compromises the warranty, not just bootloader, read the agreements ... If you exploit a bug to have root access, you will have to fool everyone who will have contact with your phone so they don't see what you have done. Even if you try to "reverse" the root, you(or the program you use) will always leave a trace.

We should be promoting "unlock the world"
This is not to imply everything should be free, however if I own something it should be mine in every regard, that includes breaking it.
Sent from my Galaxy Nexus using Tapatalk 2
---------- Post added at 03:13 PM ---------- Previous post was at 03:12 PM ----------
@skrilax thanks for you work on the a500.
Sent from my Galaxy Nexus using Tapatalk 2

I have xt925, first thing I did was unlock boot loader. Then I updated ota to Telstra JB. OP is misleading people.

Once again.
A) The reason why the page says "no updates" is beacuse OTA updates only work when you're on stock firmware, which is unlikely when you have the bootloader unlocked. That's all.
B) There are things that such "agreement" cannot contain. Being unable to sell the phone is one of them in most countries.
Click to expand...
Click to collapse
To end my part in this discussion: The limitations, restrictions & disadvantages of unlocking the bootloader are much greater then any benefit or gain under the current availability of development !

Darbness said:
I have xt925, first thing I did was unlock boot loader. Then I updated ota to Telstra JB. OP is misleading people.
Click to expand...
Click to collapse
Have you tried out lte tethering? It doesn't work on Rogers.

To epinter -
I disagree from the op.
Every change to device firmware compromises the warranty, not just bootloader, read the agreements ... If you exploit a bug to have root access, you will have to fool everyone who will have contact with your phone so they don't see what you have done. Even if you try to "reverse" the root, you(or the program you use) will always leave a trace.http://www.linuxmobile
Click to expand...
Click to collapse
I did not notice your response at first, now to the point -
Without any disrespect to the work, time & effort invested, the main point is being ignored by the developers: All comments I got on this OP didn't touched the number one reason of my suggestion to not unlock the bootloader: There in not really enough of a variety of development options today to justification the bootloader unlocked of the xt925.

Skrilax_CZ said:
Cons one by one:
Yes, although you have to be careful, because there are scirpts checking if you're rooted.
Click to expand...
Click to collapse
Can someone elaborate on this point; I read in another thread that when you remove all rooted apps and data, clear out the files left in /system, that there is still info stored stated if the device has ever been rooted, and that this can be cleared using an app on a PC (don't remember which) however when I looked at the app it was specific to the XT926 and thus I wouldn't be able to use it.
After a thorough clean of every rooted app and everything left behind by rooted apps, is there a known way (or assumed to be working way) on XT925 to erase the record of the root.
Also, assuming I was to get my phone back to that state and remove proof of root, what specifically do I need to do in order to be careful as stated... or is epinter correct in saying that there is always a trace left behind, and if so, is this a blatant trace or something that hasn't been of much concern for Motorola in the past when servicing phones?
Tombs1234 said:
At least on my O2 Germany xt925 I got the update OTA from ICS to JB after unlocking. Had to return to the stock bootloader because the OTA relies on it after rebooting though.
Click to expand...
Click to collapse
How would I return to a stock bootloader if I were to unlock mine and an OTA didn't work? How did you do it?

itzik_man said:
The limitations, restrictions & disadvantages of unlocking the bootloader are much greater then any benefit or gain under the current availability of development !
Click to expand...
Click to collapse
It's your decision whether to unlock the bootloader or not. I'm just saying (for other users) that many of the cons you wrote were absolutely incorrect.
PantsDownJedi said:
Can someone elaborate on this point; I read in another thread that when you remove all rooted apps and data, clear out the files left in /system, that there is still info stored stated if the device has ever been rooted, and that this can be cleared using an app on a PC (don't remember which) however when I looked at the app it was specific to the XT926 and thus I wouldn't be able to use it.
After a thorough clean of every rooted app and everything left behind by rooted apps, is there a known way (or assumed to be working way) on XT925 to erase the record of the root.
Also, assuming I was to get my phone back to that state and remove proof of root, what specifically do I need to do in order to be careful as stated... or is epinter correct in saying that there is always a trace left behind, and if so, is this a blatant trace or something that hasn't been of much concern for Motorola in the past when servicing phones?
Click to expand...
Click to collapse
I believe there is something stored in the pds partition. Or at least it is that way on Droid RAZR XT912 and you had to fix it to remove the remaining traces. Flashing FXZ is also a way how to get a clean stock firmware, but pds partition is not affected that way.
PantsDownJedi said:
How would I return to a stock bootloader if I were to unlock mine and an OTA didn't work? How did you do it?
Click to expand...
Click to collapse
I think he meant "stock firmware" instead of "stock bootloader"

So if that were the case on this phone, I wonder if doing a dd backup of the pds partition before rooting at ICS, for restoring after downgrade, would be the way to go. Assuming it restores properly, it would be a good thing to add to the sticky thread about rooting. I did a dd of all my partitions except for /data last night, but I'm already rooted.
hmm... I'm wondering if there's something inaccessable in /system or even the sdcard since they get mounted with fuse. My only other Android phone was the Galaxy S II which was pretty straightforward and dead simple to root and unroot. I was surprised to see the fuse module being used to mount anything when I got this one.

The original topic is here: http://forum.xda-developers.com/showthread.php?t=1857558
I don't know if there was a proper fix developed (haven't checked) on the RAZR.

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.

[BootLoader/Root Discussion] No Bounty, Just plain discussion

Okay we have a Bounty thread... Leave that for just plain Bounty pledges..
In here feel free to talk about BootLoader discusions, Root discussions..

Nice thread. Would be nice to discuss about Moto Maxx root as well. Since it has unlockable bootloader, I believe root is pretty doable, but I have no idea how to, since there's no custom recovery yet.

Nice thread.... looking forward
[ ]'s

some one knows how can we help to find a exploit or something that will make our Turbo able to get root??

When lollipop gets released for the Turbo, I'm going to have a tough decision. I really want that sweet new lollipop, but I also know that the chances of rooting it will go down significantly. So, the question is, should we stay on KitKat in hopes of getting root? It's going to be really hard to resist 5.0. And since the 2014 Moto X just got it, I think we're not far behind.

There's a vulnerability in KitKat, we just have to figure out how to exploit it. CVE-2014-7911. More info can be found at http://seclists.org/fulldisclosure/2014/Nov/51.

Your chances of getting root with LP and a locked bootloader depend on an exploit which has yet to be found and that may be some time and on some phones has never happened on previous operating systems. You would be much better off if the phone was released for unrestricted world wide sales but being CDMA and a Verizon exclusive is guaranteed to prevent the large scale adoption that would have made it more attractive to developers. Realistically no one here knows better than you whether root is more important than getting LP are for you. For my purposes I consider root a must have while having no issues with kk which I like just fine which would make it an easy choice.

Correct me if I'm wrong, but can't we just revert to kitkat if an exploit is found?
http://forum.xda-developers.com/showthread.php?t=2929737
That's the factory firmware we could flash if need be.

madeiracam said:
Correct me if I'm wrong, but can't we just revert to kitkat if an exploit is found?
http://forum.xda-developers.com/showthread.php?t=2929737
That's the factory firmware we could flash if need be.
Click to expand...
Click to collapse
Maybe. With Qualcomm chips, it's possible to make reverting to an older version result in a hard brick. With Big Red's knowledge of what they can do, unfortunately, they might implement this "feature". Plus, a vulnerability has already been found. We just need to figure out how to exploit it.

madeiracam said:
Correct me if I'm wrong, but can't we just revert to kitkat if an exploit is found?
http://forum.xda-developers.com/showthread.php?t=2929737
That's the factory firmware we could flash if need be.
Click to expand...
Click to collapse
At least with my Motorola RAZR M, every time they had a big version upgrade they also upgraded the security partition (which would be incompatible with prior firmwares), making it impossible to downgrade without an unlocked bootloader.
Sent from my Droid Turbo.

I think I have an idea on how to obtain a bootloader unlock. It most likely will not work, though, as I highly doubt it would be this stupid simple. As I do not yet have a Turbo, could someone send me the result of "fastboot oem get_unlock_data"? PM it to me and I'll test my theory. I'll also need one from some other (model doesn't matter) Motorola device, too, that actually is eligible for official bootloader unlocking.

r3pwn said:
I think I have an idea on how to obtain a bootloader unlock. It most likely will not work, though, as I highly doubt it would be this stupid simple. As I do not yet have a Turbo, could someone send me the result of "fastboot oem get_unlock_data"? PM it to me and I'll test my theory. I'll also need one from some other (model doesn't matter) Motorola device, too, that actually is eligible for official bootloader unlocking.
Click to expand...
Click to collapse
I have both a Droid Turbo and a Motorola device that is eligible for bootloader unlocking, but I don't know if I can trust to give my oem unlock data if that is in any kind "dangerous" for me or my guarantee. Can you just give me a hint and I check it out?

josebama said:
I have both a Droid Turbo and a Motorola device that is eligible for bootloader unlocking, but I don't know if I can trust to give my oem unlock data if that is in any kind "dangerous" for me or my guarantee. Can you just give me a hint and I check it out?
Click to expand...
Click to collapse
Yeah, sure. I'll send I sent you a PM.

Do you still need this? I have a Turbo with a cracked screen um about to send back.

greekstile said:
Do you still need this? I have a Turbo with a cracked screen um about to send back.
Click to expand...
Click to collapse
Yes, but not if you're about to send it back. I'll get another one. I wouldn't be able to test if the unlock worked.

When I say send it back, I don't have to send it right away. If the unlock does work, I assume I could lock it back down before sending back?

greekstile said:
When I say send it back, I don't have to send it right away. If the unlock does work, I assume I could lock it back down before sending back?
Click to expand...
Click to collapse
With Motorola devices, I don't think it's possible. I think the qfuse gets permanently blown. I would send it back if I were you. This method probably won't work anyways.
EDIT: qfuse, stupid autocorrect

I'm willing to give it a shot. Just let me know.

r3pwn said:
With Motorola devices, I don't think it's possible. I think the cause gets permanently blown. I would send it back if I were you. This method probably won't work anyways.
Click to expand...
Click to collapse
i will help u too if needed
got a Droid turbo

danger2u said:
i will help u too if needed
got a Droid turbo
Click to expand...
Click to collapse
How does one have a Turbo that is eligible for unlocked bootloader? This sounds like candy covered in gold to me.

Root/bootloader thread ?

With the initial root thread being shut down, could someone with specific news or ideas start up a new thread?
There are lot of frustrated people with the locked bootloader like me that would really welcome some news or progress on this, and it is difficult to imagine this happening without a specific thread on the subject.

PM the forum moderator and request the original thread be cleaned and reopened. Duplicate threads are not permitted.

Get over it.. locked bootloader means no root, nobody has found a way around this on any of the recent locked loaders
Sent from my SM-G935T using Tapatalk

jgodfrey82 said:
Get over it.. locked bootloader means no root, nobody has found a way around this on any of the recent locked loaders
Sent from my SM-G935T using Tapatalk
Click to expand...
Click to collapse
I could tell you are talking without no knowledge no wonder you have no thanks for helping out this community at all, ROOT COULD STILL BE ACHIEVED with a locked bootloader

Let's be careful with the comments - that is one reason the other thread got closed - especially after it gets reopened.

My bad with the get over it post. I struggled through never having root on N4 on att and just have accepted no root on s7e.. I know I'm an xda noob so no offense meant, I do actually have 8 thanks tho! ?
Sent from my SM-G935T using Tapatalk

This thread is going to get locked just like the last two.

v8dreaming said:
This thread is going to get locked just like the last two.
Click to expand...
Click to collapse
While nothing happening here - did some searches and if you want to be even more frustrated about the bootloader and root, look at the below from an Asian forum (translated by Google - not perfectly lol):
RECOMMENDATION
- SAMSUNGVN liability risks unlucky to
- Only applies to version Snapdragon Galaxy S7 Edge SM-G9350 code
- Loss of warranty when Unlock Bootloader to Root.
- No guarantee of confidentiality issues, personal information
- Knox will jump into 0x1
Files needed
- Odin 3.10.7: Fshare - Odin3_v3.10.7.zip
- Driver Samsung: Technical Documentation | SAMSUNG Developers
Download and install.
- CF-Root: Fshare - cf-root-g9350.zip
Proceed:
- In the Galaxy Apps -> Search software "CROM Service" -> Settings and proceed to unlock the bootloader.
- Shutdown. Boot into Download Mode by pressing hard (Vol Down + Home + Power)
- Check CROM Service line. If it can gauge lock, press Down + Home + Power Vol until the machine off completely and then unlock the normal boot as the first step. If it continues to unlock offline.
- Launch Odin 3.10.7, cable plug, extract the zip file is the file cf-root cf-root-g9350.zip-g9350.tar. Under PDA cf-root-file select g9350.tar
- Click Start -> PC reboot when done.
- Congratulations on your machine successfully root.
That is also a snapdragon model, Hope somehow we can get there with out 975T sometime.

I heard The lg g5 has a unlocked bootlader
Sent from my SM-G935T using XDA-Developers mobile app

will6316 said:
I heard The lg g5 has a unlocked bootlader
Sent from my SM-G935T using XDA-Developers mobile app
Click to expand...
Click to collapse
I have heard that too, but like many others, I have a 935T which we would like to make customizable.
Related to this - another casualty of the locked root thread is the activity of getting into TMo and Samsung's face through twitter and other avenues. Hopefully it is still going on, but without any means of communication on the matter in this forum - it may have just died.

Here are my two cents for those that have lost or are in the process of losing faith.
This is a very popular device. That goes without question.
This is a very popular forum. That too goes without question.
The T-Mobile forum is not the only forum with hopes of having an unlocked bootloader. Thus we can hope that there is someone out there (or perhaps even a team) that will stumble upon a solution. We all know that there are people experimenting with their own devices with known exploits and also using creativity and ingenuity in efforts of finding a new one. How many devices have been released with little hope of having root access? This is not the first. So many of you are doubtful and acting like you've been wronged by someone. I've been reading about members wanting to start class action lawsuits against Samsung for locking the bootloaders. But much of this is just talk until somebody does it. We have people stepping up to the plate constantly on trying to give you all what you want. Yet threads keep popping up which are no different from the ones that get closed for the same reasons yet all of which yield little to no results or even influence. The same tweets get sent, same calls get made, same e-mails sent, etc. Samsung, T-Mobile, Verizon, AT&T, etc all heard you! I heard you, you all have heard each other. For crap sake let it go already and just be patient! When somebody discovers a way then we can celebrate, look back on this day and remember at just how pathetic we were whining about not having root and some will even be kicking themselves in the butt for returning their phones. But then what? Oh... I know. The Galaxy S8 Edge will come out next year. Who wants to take bets that this all won't happen again? Honestly, I really don't care anymore. I just don't. I don't have root but I do have a damn good phone on a good network. Someday (hopefully soon) when I check this forum and see that root was discovered then I'll probably do it. No doubt that most of us will! But in the meanwhile, this isn't a forum for development anymore. This has turned into a group therapy session for those that feel victimized by Samsung (or whoever you want to point your fingers at.) Now... let me take my step off my soapbox and await all of the responses about how I'm wrong and a hypocrite or how I'm insensitive by hurting someone's feelings or even how my words are counterproductive to finding a resolution that you all seem to be losing sleep over. Guess what... I don't care about that either. I'm more frustrated about how everybody in this forum seem to be whining and crying about not having root than I am about having root access now. I can't log on without shaking my head at some of the comments that I read. Yet somehow, just like a horrible accident on the freeway, I can't help but gawk at the amazement of what I see which inevitably brings me back. I'll soon be at the point where when the time comes that I read "WE HAVE ROOT!!!" my first reaction will be cheerfully saying to myself, "Finally! People can stop whining and crying over it!" instead of the appropriate action of actually rooting.
I'll step down now. Thank you all for your time.

There is a lot of wining and complaining, but there were some hopeful pieces here and there.
I was hoping the Chinese 9350 Snapdragon was a path that might be followed. The specifics are beyond my skill set, but an am hoping if it is not a dead end that those for which it is not beyond theirs will be able to do something with it. I had tried the CROM system that had been posted over there but not surprisingly it would not work on this similar but different device.
So hoping the tread gets going again - and hopefully without the drama that get it shut down.

will6316 said:
I heard The lg g5 has a unlocked bootlader
Sent from my SM-G935T using XDA-Developers mobile app
Click to expand...
Click to collapse
Yeah. But the reviews are rolling in. Subpar seems to be the consensus so far.
Sent from my SM-G935T using XDA-Developers mobile app

gaww said:
- No guarantee of confidentiality issues, personal information
Click to expand...
Click to collapse
Wait a second. This implies there was a guarantee of personal information before. FU Samsung.

Quote:
Originally Posted by gaww View Post
- No guarantee of confidentiality issues, personal information
@rbiter said:
Wait a second. This implies there was a guarantee of personal information before. FU Samsung.
Click to expand...
Click to collapse
Funny - don't remember that quote above. - lol?

gaww said:
Quote:
Originally Posted by gaww View Post
- No guarantee of confidentiality issues, personal information
Funny - don't remember that quote above. - lol?
Click to expand...
Click to collapse
I think you misunderstood. I was being sarcastic. With unlocked bootloader was Samsung guaranteeing security? Doubt it.

s7 edge root
I have a hong kong g9350 and find it very difficult to find good info about root,,,,, i got some stuff from baidu forums but the barrier is its not english and even with translate,its hard work, i believe that they have rooted successfully i have the root file and apparently the bootloader is not locked..... presume is the word. but until i can find info after rooting i dont want to risk it yet... theres no follow up dont even know if theres a recovery included like twrp or cm one any one else know anything thanx

gaww said:
There is a lot of wining and complaining, but there were some hopeful pieces here and there.
I was hoping the Chinese 9350 Snapdragon was a path that might be followed. The specifics are beyond my skill set, but an am hoping if it is not a dead end that those for which it is not beyond theirs will be able to do something with it. I had tried the CROM system that had been posted over there but not surprisingly it would not work on this similar but different device.
So hoping the tread gets going again - and hopefully without the drama that get it shut down.
Click to expand...
Click to collapse
May be of help in Downloaded crom. Service off Chinese site. And it tells me I can install roms and bootloader unlocked I'll put it up on mega soon. Also have the CF auto root off same site but I'm apprehension because of language barrier and post root details
https://mega.nz/#!zYUWkTAA
Try that
Sent from my SM-G9350 using XDA-Developers mobile app

xmanz said:
May be of help in Downloaded crom. Service off Chinese site. And it tells me I can install roms and bootloader unlocked I'll put it up on mega soon. Also have the CF auto root off same site but I'm apprehension because of language barrier and post root details
https://mega.nz/#!zYUWkTAA
Try that
Sent from my SM-G9350 using XDA-Developers mobile app
Click to expand...
Click to collapse
The CROM lock does not exist on non-Chinese bootloaders
Samsung's Chinese handsets bootloaders have in 3 types of bootloader locks, the carrier lock, the CROM lock (which is enabled if the Chinese bootloader does not find the "KIWIBIRD" string written in the STEADY partition), and the reactivation lock, they are not carrier locked.
U.S. variants only have the Carrier and reactivation locks, there is no CROM lock to unlock on these devices (or any international variants either), U.S. variants are however carrier locked, the lock is hardcoded in the bootloader code (there is just no execution path to load an unsigned kernel on the consumer carrier locked variant bootloaders, there is no "lock" Qfuse anymore, the bootloader itself just has no carrier unlocking/locking support, it is always locked by design) and the bootloader is tied to the device ID, for example SM-G935F (which is One Time Programmable) and will refuse to run on anything but the device id that is hardcoded within it, obviously the bootloader is signed so you can't modify it, there is also a revocation mechanism involving Qfuses to make sure you can't downgrade to a vulnerable version (should one exist).
There are presumably Engineering versions of the bootloader that allow running unsigned kernels but those have not been leaked and they probably won't run on devices for which the production mode Qfuse has been blown (the device is in Engineering mode when that Qfuse is not set).

mathieulh said:
The CROM lock does not exist on non-Chinese bootloaders
Samsung's Chinese handsets bootloaders have in 3 types of bootloader locks, the carrier lock, the CROM lock (which is enabled if the Chinese bootloader does not find the "KIWIBIRD" string written in the STEADY partition), and the reactivation lock, they are not carrier locked.
U.S. variants only have the Carrier and reactivation locks, there is no CROM lock to unlock on these devices (or any international variants either), U.S. variants are however carrier locked, the lock is hardcoded in the bootloader code (there is just no execution path to load an unsigned kernel on the consumer carrier locked variant bootloaders, there is no "lock" Qfuse anymore, the bootloader itself just has no carrier unlocking/locking support, it is always locked by design) and the bootloader is tied to the device ID, for example SM-G935F (which is One Time Programmable) and will refuse to run on anything but the device id that is hardcoded within it, obviously the bootloader is signed so you can't modify it, there is also a revocation mechanism involving Qfuses to make sure you can't downgrade to a vulnerable version (should one exist).
There are presumably Engineering versions of the bootloader that allow running unsigned kernels but those have not been leaked and they probably won't run on devices for which the production mode Qfuse has been blown (the device is in Engineering mode when that Qfuse is not set).
Click to expand...
Click to collapse
Thank you I don't understand too much of the tech stuff. But mine isn't carrier locked as I'm in New Zealand. Crom tool says not locked….. And the baidu website has supposedly CF autoroot for g9350.. As I said I'm apprehensive to flash till better data comes available…. Shall I link the site and if you can be bothered have a look-see please. Cheers
Sent from my SM-G9350 using XDA-Developers mobile app

Droid Maxx 2 Root

I've wanted to know if rooting the Droid Maxx 2 has become possible yet. I currently own a Droid Maxx 2, which is a Verizon one. It did come with the OEM unlock option, but even with it enabled, the bootloader isn't unlocked. I tried the Motorola Bootloader Unlock service, but it does not support this phone. I have tried several rooting apps, and just about none had worked. Is there any other way to do this? Thanks!

This forum is so dead, ugh. If you're on MM, then that would be a definite no as of right now, LP and lower have a better chance of being rooted, but none exist at the moment. This new quadrooter app has exposed some vulnerabilities that could lead to root escalation in most, if not all, vulnerable devices, but we would need to wait on someone to develop a tool/method for exploiting those vulnerabilities. That is the basket I'm putting all my eggs in at the moment, because this phone is far too unpopular for somebody to come along and put effort into a standalone rooting method.
Cross your fingers on the quadrooter exploits, it's likely our only hope for root.

MidnightLocke said:
It did come with the OEM unlock option
Click to expand...
Click to collapse
What's the OEM unlock option? Can I use it to remove the bloatware?