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.

[Q] My Razr M is not rootable, is there a way to downgrade to a lower version?

Ok so my whole problem is that im on system version 183.46.15.XT907 when its supposed to be 183.46.10.XT907. My question is that is there a way to get to 183.46.10.XT907. again? I've been at this for hours and i'm in desperate need for help.
If you would like to see a picture of exactly please PM it will not let me place a picture as i am a new user

rockketman123 said:
Ok so my whole problem is that im on system version 183.46.15.XT907 when its supposed to be 183.46.10.XT907. My question is that is there a way to get to 183.46.10.XT907. again? I've been at this for hours and i'm in desperate need for help.
If you would like to see a picture of exactly please PM it will not let me place a picture as i am a new user
Click to expand...
Click to collapse
As of now there is no way of rooting or downgrading with a locked bootloader.
Sent from my Scorpion Mini

That's a bummer, but for root part, maybe or maybe not. I don't think it's possible as Motorola took out some vital codes from Kit Kat ROM which allows root.

ATTACK said:
As of now there is no way of rooting or downgrading with a locked bootloader.
Sent from my Scorpion Mini[/QUOTEO
I was able to flash it down to .10 but my kernel was after June 3rd, something like July 27th or whatever and yeah this doesnt allow it to work. Oh well, I'm switching to an S3 In less than a month.
Click to expand...
Click to collapse

rockketman123 said:
ATTACK said:
As of now there is no way of rooting or downgrading with a locked bootloader.
Sent from my Scorpion Mini[/QUOTEO
I was able to flash it down to .10 but my kernel was after June 3rd, something like July 27th or whatever and yeah this doesnt allow it to work. Oh well, I'm switching to an S3 In less than a month.
Click to expand...
Click to collapse
Unlocked or locked? Kernel date and screenshot as proof please, including the AP Fastboot screen.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
Click to expand...
Click to collapse

I suspect it's already unlocked as it's impossible to downgrade the kernel on a locked RAZR M (OEM signatures, you know).

AndyYan said:
rockketman123 said:
Unlocked or locked? Kernel date and screenshot as proof please, including the AP Fastboot screen.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
Click to expand...
Click to collapse
as I'm a new user I cant post a screen shot but the imgur link is i(.)imgur(.)com/xiZuIyq(.)jpg and i(.)imgur(.)com/cA6W6Oi(.)jpg
I went from 4.1.2 Rooted and was never able to unlock the bootloader then flashed to 4.4.2 on the .15 then flashed to .10
Click to expand...
Click to collapse

You're outta luck. You ahould have flashed .10 first and unlocked the bootloader before you hop between the ROM version... .15 version permanently lock the bootloader.
EDIT: I looked at the pictures, however, I am suspicious of the claim. The reason being, the bootloader will check the kernel version, and if it's not agreed with the bootloader security key file (tz.mbn), the bootloader will refuse to touch it. If anyone else with the locked phone tries this harebrained experiment and come out without a softbrick, I may have to eat my sock.

Dr. Mario said:
You're outta luck. You ahould have flashed .10 first and unlocked the bootloader before you hop between the ROM version... .15 version permanently lock the bootloader.
Click to expand...
Click to collapse
yeah when i flashed over i "accidentally" did the wrong version (tut linked me to a wrong version I suppose) and now im piss out of luck, but like i said im not worrying about it since s3 within a few weeks or so. Hopefully one day it's able to Root though B)
EDIT: what exactly are you suspicious of? The claim that I went from 4.1.2 flashed to 4.4.2 but on .15 then down to .10?

If the eventual RAZR M update gets screwed up like the first one, it may get unlocked but I have grave doubt because Verizon have learned their lesson on this one: root = bootloader unlock, at least in the case of early Kit Kat update.

fellas i have received two moto M today and seems like this cant either root because this stupid 9mb of .15 update, since the kernal is after jun 3
towelroot
well any new exploit around the coner to try?

No root exploits right now, unfortunately. It's getting harder and harder to exploit the Kit Kat.

These are my only unlocking options?

OK, I just come across an S4 SGH-i337M running 5.0.1 locked to Bell. Searching Google is fairly mind boggling as everyone has their own method. In my situation, I'm pretty sure I have come to this solid conclusion. Two options only,,
1. Buy unlock code or
2. Downgrade to at least 4.4.2 and use the hidden codes method.
Can #2 be done safely? Some sites say if you do try downgrade from Lollipop to KK, it will brick. What would a safe procedure be if possible.
Thanks

http://forum.xda-developers.com/showpost.php?p=64978235&postcount=713
Substitute Bell firmware for Fido firmware.

audit13 said:
http://forum.xda-developers.com/showpost.php?p=64978235&postcount=713
Substitute Bell firmware for Fido firmware.
Click to expand...
Click to collapse
Thanks, seen this but wasn't sure. I assume that flashing back to Lollipop isn't necessary if one chooses to stay at 4.4.2 for a while. Heard some comments about increased battery drainage etc. on Lollipop.
Will try this once the new charge port shows up and I can replace.

The hidden codes method won't work, unfortunately. Let me know if you are successful.
Thanks.

audit13 said:
http://forum.xda-developers.com/showpost.php?p=64978235&postcount=713
Substitute Bell firmware for Fido firmware.
Click to expand...
Click to collapse
audit13 said:
The hidden codes method won't work, unfortunately. Let me know if you are successful.
Thanks.
Click to expand...
Click to collapse
Thanks, will do. Hopefully will be getting to it tonight. Here's one of the confusing things I was talking about. Been doing alot of reading, and in your instructions, you install TWRP to flash SuperSU and such. Then, reading elsewhere, I see this "SAFESTRAP IS THE ONLY RECOVERY WE CAN USE!
Don't even try flashing another one.", posted in a thread about AT&T SGH-I337 model. Well, here it is, halfway down in the second post, bolded in red. http://forum.xda-developers.com/showthread.php?t=2616221 Just trying to get things figured out, it's been a couple years since I last played with the Galaxy, just getting back into it now.

The AT&T version of the s4 is the Sgh-i337 and, if it was running stock 5.01, the bootloader would be locked and twrp cannot be used.
The Canadian version of the s4 has the letter "m" at the end of the model number and the bootloader is not locked which allows the installation of twrp and custom ROMs that are not based on a tw kernel.

audit13 said:
The hidden codes method won't work, unfortunately. Let me know if you are successful.
Thanks.
Click to expand...
Click to collapse
Thanks, this method seemed to work,,just one problem I overlooked, but I just assumed this phone would work on AWS1700,,wrong lol. I was reading the 141 page thread and there seems to be a few different methods for doing this. With my S3, I only had to flash the NV and run a script on every boot as the nv rewrite would not stick. Is this so as well with the s4 too,,or is there a method to make it a permanent stay. I didn't plan on updating to 5.0.1 quite yet,,but will do if needed. Do you no of a recommended/preferred method for this?

Did you test the phone with another sim card? Hopefully, you will not be prompted to enter a network unlock code.
For AWS, I'm not sure what needs to be done as I am using a Telus s4 on Bell.

audit13 said:
Did you test the phone with another sim card? Hopefully, you will not be prompted to enter a network unlock code.
For AWS, I'm not sure what needs to be done as I am using a Telus s4 on Bell.
Click to expand...
Click to collapse
It was locked with Bell, my provider is Eastlink,,I finally got the AWS1700 band working, but kept losing it when the phone went to sleep. Updated to the NE1 modem, then had to flash the AWS again and all seems to be working fine. Hopefully it holds up. Thanks for everything.

Glad it is all working. We're all here to help and learn from each other.

Does 11 Toshiba eMMC matter if already unlocked

I think that my phone is already unlocked. To be honest I'm not 100% sure. I am running a deodexed rooted version of lollipop right now, but I did all this stuff almost 2 years ago and haven't messed with any of it since. I do have an icon of unlocked padlock when booting up my phone. I think that means the bootloader is unlocked, but I'm not sure if that is what it means or not. Someone on reddit shared a link to an article by jdrch (Sorry can't link to it, still new here) about unlocking the bootloader and installing CyanogenMod 13 for G900V. The first thing he has you do is check your eMMC, but the article says this:
"As of this writing, it does not work for S5s with 11 Toshiba eMMCs. Due to the possibility of the bootloader unlock exploit being patched in the Marshmallow update, I’d highly suggest doing this BEFORE updating to any stock Marshmallow OTA."​But if I intend to go straight to CM13 (if that is possible) does it even matter that I don't have correct eMMC?
EDIT: Nevermind. I see now that my bootloader is not unlocked and after doing some more searching through the forums. I have found that it is not possible for the Toshiba eMMC chip. :crying: I need a new phone.

thetillmiester said:
I think that my phone is already unlocked. To be honest I'm not 100% sure. I am running a deodexed rooted version of lollipop right now, but I did all this stuff almost 2 years ago and haven't messed with any of it since. I do have an icon of unlocked padlock when booting up my phone. I think that means the bootloader is unlocked, but I'm not sure if that is what it means or not. Someone on reddit shared a link to an article by jdrch (Sorry can't link to it, still new here) about unlocking the bootloader and installing CyanogenMod 13 for G900V. The first thing he has you do is check your eMMC, but the article says this:
"As of this writing, it does not work for S5s with 11 Toshiba eMMCs. Due to the possibility of the bootloader unlock exploit being patched in the Marshmallow update, I’d highly suggest doing this BEFORE updating to any stock Marshmallow OTA."​But if I intend to go straight to CM13 (if that is possible) does it even matter that I don't have correct eMMC?
Click to expand...
Click to collapse
You are NOT unlocked and do not pretend you are.
You cannot flash CM13. The unlock icon when you boot is simply a result of having a custom binary installed.

Nandr0idC0nsumer said:
You are NOT unlocked and do not pretend you are.
You cannot flash CM13. The unlock icon when you boot is simply a result of having a custom binary installed.
Click to expand...
Click to collapse
Nobody is PRETENDing anything. I already said I wasn't sure if I was or not.

thetillmiester said:
Nobody is PRETENDing anything. I already said I wasn't sure if I was or not.
Click to expand...
Click to collapse
You were talking about flashing CM13, which will brick you if you're not unlocked

Nandr0idC0nsumer said:
You were talking about flashing CM13, which will brick you if you're not unlocked
Click to expand...
Click to collapse
Okay so if I unlock then flash CM13 will it work even though my eMMC is the 11 Toshiba?
EDIT: Nevermind, see edit on OP.

thetillmiester said:
EDIT: Nevermind, see edit on OP.
Click to expand...
Click to collapse
Yes it sucks that 11s cannot unlock
@GeTex and the others are working on an unlock but its not looking good for now.

6.0.1 G900VVRU2DPG2 Root

Hi community,
Not sure if this goes against TOS of the forum or if this is even the correct forum to be posting this question in. What is preventing a root from being created for 6.0.1? What would help get a root created for this phone?
I am willing to pay someone to create a working root method; whether it be public or just for me. I have an adequate number of phones to help develop a root. Applicants must be a trusted member of the community with a high reputation.
Please no flame comments. Only serious responses.
Thanks,
Andrew

root on marshmellow requires a unlocked bootloader (this applies to ANY marshmellow device )
if you have a CID15 device you can flash back to PB1 unlock the bootloader and then flash whatever 6.01 rooted rom you want
if you have a a CID11 device with a non-unlockable boot-loader you are SOL its impossible to root marshmallow with dm-verity enabled and there is no way around that
dm-verity cryptographicly checks the block map of the /system partition if there is so much as a text file out of place it won't boot

Legitsu said:
root on marshmellow requires a unlocked bootloader (this applies to ANY marshmellow device )
if you have a CID15 device you can flash back to PB1 unlock the bootloader and then flash whatever 6.01 rooted rom you want
if you have a a CID11 device with a non-unlockable boot-loader you are SOL its impossible to root marshmallow with dm-verity enabled and there is no way around that
dm-verity cryptographicly checks the block map of the /system partition if there is so much as a text file out of place it won't boot
Click to expand...
Click to collapse
Thanks for the response. It was very informative. I'll check which chipset I have on the phones. Hopefully there are some that are downgradable.
Not sure if my terminology is correct but does samsung offer an option to register the device as unlocked? Similar to how HTC offers an option to unlock it? Where they send you the unlock key or something.

andrewr74 said:
Thanks for the response. It was very informative. I'll check which chipset I have on the phones. Hopefully there are some that are downgradable.
Not sure if my terminology is correct but does samsung offer an option to register the device as unlocked? Similar to how HTC offers an option to unlock it? Where they send you the unlock key or something.
Click to expand...
Click to collapse
no the only bootloader unlock we have is for s5's with samsung flash memory aka CID15 devices
you can check which you have with this https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check&hl=en
first two numbers if its a 15 you are good follow the root and unlock threads if its a 11 nope you are sol

Legitsu said:
no the only bootloader unlock we have is for s5's with samsung flash memory aka CID15 devices
you can check which you have with this
first two numbers if its a 15 you are good follow the root and unlock threads if its a 11 nope you are sol
Click to expand...
Click to collapse
Yeah, I checked a handful of my phones and 2 of the 5 were CID 15. I was successfully able to downgrade to 5.0 and root. Using an app to check every phone is very annoying since I have to sideload the apk and launch which takes too long. Do you know of anyway using ADB that I could determine the eMMc chipset?
I spoke with Samsung for a possible solution that is equivalent to a root and they suggested Nox Console. Where I can remove bloatware and disable certain features of the phone for $3ea. Which is alright for locking down the device but apps that require root to accomplish what I need... So not much help there.
In your opinion, what are the chances someone creates a root for CID 11? Impossible?

andrewr74 said:
Yeah, I checked a handful of my phones and 2 of the 5 were CID 15. I was successfully able to downgrade to 5.0 and root. Using an app to check every phone is very annoying since I have to sideload the apk and launch which takes too long. Do you know of anyway using ADB that I could determine the eMMc chipset?
I spoke with Samsung for a possible solution that is equivalent to a root and they suggested Nox Console. Where I can remove bloatware and disable certain features of the phone for $3ea. Which is alright for locking down the device but apps that require root to accomplish what I need... So not much help there.
In your opinion, what are the chances someone creates a root for CID 11? Impossible?
Click to expand...
Click to collapse
if you searched the forum before asking any of this you would know the answer to that No not gonna happen extensive research was done it s impossible with the current method we have
for locked devices if you simply wanna turn apps off or block ota's I recommend this app
https://play.google.com/store/apps/details?id=com.ospolice.packagedisablerpro&hl=en
cat /sys/block/mmcblk0/device/cid
will return the cid from a shell
CID11's can be downgraded to 5.01 and then you can get root but NOT marshmallow and higher
oncid 15 devices you can unlock the bootloader https://forum.xda-developers.com/ve...t/rd-unlocking-galaxys-s5-bootloader-t3337909
and flash a rooted marshmallow rom if you already have root you can skip right to method 2

Legitsu said:
if you searched the forum before asking any of this you would know the answer to that No not gonna happen extensive research was done it s impossible with the current method we have
for locked devices if you simply wanna turn apps off or block ota's I recommend this app
https://play.google.com/store/apps/details?id=com.ospolice.packagedisablerpro&hl=en
cat /sys/block/mmcblk0/device/cid
will return the cid from a shell
CID11's can be downgraded to 5.01 and then you can get root but NOT marshmallow and higher
oncid 15 devices you can unlock the bootloader https://forum.xda-developers.com/ve...t/rd-unlocking-galaxys-s5-bootloader-t3337909
and flash a rooted marshmallow rom if you already have root you can skip right to method 2
Click to expand...
Click to collapse
That emmc command worked perfectly!
I don't load any custom roms so only getting root on stock 5.0 is exactly what I want. I was unaware CID11 was downgradable, the other post were a tad confusing in regards to the CIDs. I guess it was the terminology that I did not understand.
Thank you for the help!

andrewr74 said:
That emmc command worked perfectly!
I don't load any custom roms so only getting root on stock 5.0 is exactly what I want. I was unaware CID11 was downgradable, the other post were a tad confusing in regards to the CIDs. I guess it was the terminology that I did not understand.
Thank you for the help!
Click to expand...
Click to collapse
https://forum.xda-developers.com/ve...ow-to-flash-custom-6-0-1-roms-locked-t3393943
PB1 = 5.0