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.

[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?

Is my M8 worthless?

Hello all,
I have a Verizon branded M8 AND have recently switched to TMob. The M8 is running 4.4.4 and is unfortunately still S-on and locked. Am I just stuck with a useless $600 phone until the Sunshine several developers come up with a way? Is that the only outfit with the capability of rooting this phone right now? Thanks in advance to anyone with any info.
Sent from my HTC6525LVW using XDA Free mobile app

Did you try calling verizon to get the unlock code?
If you have been with them for long, they will probably give it to you for free or maybe charge a fee but well you can use your phone then.
If they are unwilling to give you the unlock code then just say that you are gifting it to someone special or donating it. Just come up with a good humane reason and surely they will help.
They will also show you the procedure to unlock it.
Also as far as my knowledge goes, it is not possible to remove your phone carrier's lock using custom firmware.
Ravi.
-----------------------------
If you liked my post, please hit the thanks / thumbs up button.

grtbhl said:
Did you try calling verizon to get the unlock code?
If you have been with them for long, they will probably give it to you for free or maybe charge a fee but well you can use your phone then.
If they are unwilling to give you the unlock code then just say that you are gifting it to someone special or donating it. Just come up with a good humane reason and surely they will help.
They will also show you the procedure to unlock it.
Also as far as my knowledge goes, it is not possible to remove your phone carrier's lock using custom firmware.
Ravi.
-----------------------------
If you liked my post, please hit the thanks / thumbs up button.
Click to expand...
Click to collapse
I did try calling Verizon but i am trying to unlock the bootloader not the Sim. ... does that change your answer or should i try again?

See the htc forums on xda too.
Sim lock cannot be removed by flashing or installing custom firmwares. There is a separate procedure to unlock htc phones and their bootloaders.
I am familiar with htc sensation unlocking but don't know if it is the same for M8.
Will update you when I reach a full fledged computer with the relevant links.
You can also search the xda forums.
Ravi.
-----------------------------
If you liked my post, please hit the thanks / thumbs up button.

grtbhl said:
See the htc forums on xda too.
Sim lock cannot be removed by flashing or installing custom firmwares. There is a separate procedure to unlock htc phones and their bootloaders.
I am familiar with htc sensation unlocking but don't know if it is the same for M8.
Will update you when I reach a full fledged computer with the relevant links.
You can also search the xda forums.
Ravi.
-----------------------------
If you liked my post, please hit the thanks / thumbs up button.
Click to expand...
Click to collapse
I am quite familiar with the htc bootloader and the unlock process. The process includes going to the htc Dev site and getting an unlock token that you then flash to the device using fastboot command. The problem is that verizon seems to be the only carrier who has somehow not allowed this. When you put your a string in on the dev site it comes back with a message saying "your carrier doesnt support" somethin like that neway.... i am wondering though if there is a way to do something at a more physical hardware layer. I mean it is jus a qualcomm chip at the end of the day... if i were to crack it open physically would i be able to access a non populated jumper that would completely erase the eeprom??

See
http://forum.xda-developers.com/showthread.php?t=2711073
http://forum.xda-developers.com/showthread.php?t=2708464
http://forum.xda-developers.com/showthread.php?t=2695464
visit
http://firewater-soff.com/
It could help. Just searched xda for you. It does not require you to get unlock token from Htc.
Disclaimer: I have not tried any of the above. You do it at your own risk.
Ravi.

[WIP] Note Series Developer Edition Coversion

All,
Due to the recent accidental leak of Samsung eMMC vendor commands allowing write to protected eMMC areas, we are now able to write CID values on production devices.
@beaups has written an awesome tool called 'SamsungCID' (found here: https://github.com/beaups/SamsungCID). This tool is based off the research of @ryanbg . This makes the process all the simpler for developers to understand/port functionality!
I have built this tool from his source, and used it on a multitude of devices that use a Samsung eMMC. It works without flaw on the Moto G (Second Generation), Galaxy S5 (VZW/ATT, though, ATT doesn't have a Developer Edition that I am aware of, though, it still could work, I need a tester, PM me, or Telegram me @npjohnson), and many, many other devices form a variety of manufacturers..
How does this apply to you?
The Note 4 uses a Samsung eMMC, and has a Developer Edition. This means that it is vulnerable to this exploit.
How can you help this progress?
You can't.
Currently, the CID writes 'successfully', and persists across reboots, but one of the registers isn't fully flushed. I am working on a module that will flush the register and allow for the Developer Edition Aboot to be flashed via ODIN.
Now, you may ask "How could we load modules, I thought that was impossible?", the short answer is, it is. At least, without what we found (or, rather, stumbled across).
We have the device kicking into Developer Edition using the CID write, and a hardware modification, which we stumbled across (demo: here, credits to @PaulPizz for spending late nights testing the various things I would throw at him, and having the balls to do some dangerous stuff that I personally believed would permanently brick his device). This method is volatile, dangerous, and quite honestly, shouldn't work. When I am confidently able to prove how it works, I will release details on my blog: here. Until then (shouldn't be more than a month, but as always, this is a free time project, and could be put on hold for real life, as I am busy with Cyber Security competitions).
What will most likely be the course of action once I release:
- Change CID to a provided Developer Edition CID
- Use hardware mod to flash/boot the custom kernel I have build to enable module loading (or maybe I'll build the function into the kernel itself, haven't decided yet)
- Either load the module, or call the function (if the latter, I'll write a binary to do so)
- Revert the hardware mod
- Flash Developer Edition Aboot via ODIN
This should be bootloader version agnostic, but, as always, beware updates, and, I'd stay away from any incoming MM updates on all locked carrier variants if you want to retain the ability to use this. If Samsung can update the eMMC firmware using those vendor commands, they can sure as heck change them the same way. Then the ability to do this goes away entirely.
You may be asking, "Can I donate to progress?"
Well. Sort of. Beaups asked that all donations go to the Make a Wish Foundation, or @ryanbg (as he is getting hitched , may you forever 'make cooking' Ryan! Haha.).
If you'd like to donate to me, know that it is not for the CID write, but instead, the work and research put into getting this all worked out for this device. I will also be dividing any donations sent to me with my tester, as he has spent a fair bit of time on this, as have I.

@npjohnson I have two devices s4 and note 4 both from Verizon, I'm in Brazil right now so I don't know if it makes a difference but I'm able to use temporary root in my note 4 so if you want any help give me a shot, I'm not a developer but engineer so any you need from me to get this rooted count me

OMG Could it be?
npjohnson said:
All,
Due to the recent accidental leak of Samsung eMMC vendor commands allowing write to protected eMMC areas, we are now able to write CID values on production devices.
Beaups has written an awesome tool called 'SamsungCID' (found here: https://github.com/beaups/SamsungCID). This makes the process all teh simpler!
I have built this tool from his source, and used it on a multitude of devices that use a Samsung eMMC. It works without flaw on the Moto G (Second Generation), Galaxy S5 (VZW/ATT, though, ATT doesn't have a Developer Edition that I am aware of), and many, many others.
How does this apply to you?
The Note 4 uses a Samsung eMMC, and has a Developer Edition. This means that it is vulnerable to this exploit.
How can I help this progress?
I need a few thing to make this work:
- A few testers with Production devices, and root (temp-root should work fine) -- I will contact these people individually, do not ask here to test.
- One person with a Developer Edition that has root (need an aboot dump, and them to run one command).
If any of you know of someone with a Developer Edition, please get them in contact with me. I can be reached on Hangouts, or on Telegram (@npjohnson).
PLEASE do not post your CID publicly.
Click to expand...
Click to collapse
So you are saying this might be a path to perm root?

kerfex said:
So you are saying this might be a path to perm root?
Click to expand...
Click to collapse
Not only root but unlock bootloader please encourage anyone to help

The android gods have sent us a miracle
---------- Post added at 12:30 PM ---------- Previous post was at 12:29 PM ----------
I have a locked Verizon note 4 I'm willing to help

@npjohnson Im willing to help. I have been around the block a few times testing for other developers. I am on 5.1.1 and can hold temp root with Kingroot for about 15 minutes.
Edit: I can role back to 5.0 if needed.

@npjohnson
I believe these are some note 4 developer files. Hope this helps
https://www.androidfilehost.com/?w=files&flid=28873

@Venom0642 - Awhile back I think you said you had a developer addition note 4. Do you still have one? Can you help?

howellcp said:
@Venom0642 - Awhile back I think you said you had a developer addition note 4. Do you still have one? Can you help?
Click to expand...
Click to collapse
Sorry mate look at my Sig i been on Note 5 since it came out, so i don't have any Note 4.
Running On Samsung Galaxy Note 5 N920A Wicked Deadly Venom Theme

also willing,
have a retail Verizon,
on LP but can roll back to kk

I have a dev ed Note Edge BUT I bought it used and the previous owner blew retail firmware into it, so aboot is destroyed. Strange thing, though, I'm able to get perm root with the latest kingroot on 5.1.1.
If that's useful to you, I'm down if you're down!

h00rj said:
I have a dev ed Note Edge BUT I bought it used and the previous owner blew retail firmware into it, so aboot is destroyed. Strange thing, though, I'm able to get perm root with the latest kingroot on 5.1.1.
If that's useful to you, I'm down if you're down!
Click to expand...
Click to collapse
If you have a backup of that old aboot, then yes. Feel free to jump in on the thread I added in the Note Edge XDA forum.
kerfex said:
So you are saying this might be a path to perm root?
Click to expand...
Click to collapse
Bootloader Unlock, so yeah, permanent root, though, I don't know if write protection will still be active, but we can hope.
PaulPizz said:
@npjohnson
I believe these are some note 4 developer files. Hope this helps
https://www.androidfilehost.com/?w=files&flid=28873
Click to expand...
Click to collapse
It would... if you knew whose aboot that was, and they were around to dump their CID. Track them down, then we'll talk.

@morgej, please see original post.

Just out of curiosity, correct me if this is lame thinking or not worth trying but would it be possible to change the cid to turn the device into lets say another variant in order to utilize something like CROM.apk or to odin another variants tar files to oem unlock a device?

elliwigy said:
Just out of curiosity, correct me if this is lame thinking or not worth trying but would it be possible to change the cid to turn the device into lets say another variant in order to utilize something like CROM.apk or to odin another variants tar files to oem unlock a device?
Click to expand...
Click to collapse
You could, but the device 99% wouldn't boot.
Plus, you do realize developer editions are unlocked? Why would you want to flash to another variant to oem unlock? Literally the same thing.

Rom-Addict said:
also willing,
have a retail Verizon,
on LP but can roll back to kk
Click to expand...
Click to collapse
Please Hangouts message me if you have adb set up, and can use it.

Alright guys, a new exploit is great, but let's not get our hopes up just yet. How many times have we had our collective hearts broken over situations almost exactly like this one?
I really really hope this turns into something useful, but for now, I'm assuming it's just a flash in the pan.

Zues532 said:
Alright guys, a new exploit is great, but let's not get our hopes up just yet. How many times have we had our collective hearts broken over situations almost exactly like this one?
I really really hope this turns into something useful, but for now, I'm assuming it's just a flash in the pan.
Click to expand...
Click to collapse
1. I believe this will work. I tired to help but suck at adb now apparently.
2. No need to post if you don't believe. Just ignore

Zues532 said:
Alright guys, a new exploit is great, but let's not get our hopes up just yet. How many times have we had our collective hearts broken over situations almost exactly like this one?
I really really hope this turns into something useful, but for now, I'm assuming it's just a flash in the pan.
Click to expand...
Click to collapse
Well. Why don't you read the paper?
All devices that:
1. Use a Samsung eMMC (allows CID write)
&
2. A Developer Edition (allows you to supply a developer CID, and use their aboot)
Are vulnerable.
Question it if you will, but I am packaging things up as I write.

have adb setup but it's been awhile

Samsung Galaxy J7 Prime (SM-J727T1) Metro PCS Variant

Hello everyone, this is my first post so please take it easy on me. I have read a lot of threads regarding this phone but haven't seen or heard much about this specific device. From what I read was our BOOTLOADER is locked by the manufacturer & so far that's the major issue? Anyways, id love to see this phone get rooted and enjoy the perks of root.
Model Number: SM-J727T1
ANDROID VERSION: 7.0
BUILD NUMBER: NRD90M.J727T1UVU1AQG1

I can't find any root method what so ever.
Is anyone working on it?
Wondering if there is a similar method like the root on my j3 (cricket) granted that was a touchy root but worked aside from flashlight button not working and changing setting in build.prop to save wifi pass.
Love to see this j727t1 (metropcs) rooted and hopefully a twrp.

Dig in. It's going to be a long wait...

So I can tell. We aren't getting anywhere but I don't know what or where to start working on something. I'd like to develop or study how rooting works or just how to be able to be active in this community. If anyone has pointers please let me know.

Adb might work
I read something about using adb to unlock the bootloader. Only ever used adb once to root LG Stylo 2 it did work but there's a few steps and I don't have access to a computer long enough to find out if that would work on this phone. What about looking at other Android devices that have locked bootloader and see how they got past it.

There's no root for this device. Also, I doubt we will ever see root for this device. It has very small user base. I got mine for free with a free Amazon 1 year activation key, so no complaints.
When turning it on in cold weather, the task switch menu pops up and stays there for couple seconds, which is kind of annoying. Only happens when left in a cold environment. I was looking for root to disable soft-keys and enable on-screen menu key, but no luck.

Completely blown away by how they seem to neuter this j7prime phone which is suppose to be the successor? Hope to see root but it also doesn't seem likely as well.
Anyone know what case works on this phone? seems the ebay listing for j7prime doesn't exactly fit this phone; not surprising anymore since a brand name seems to be different across providers and regions!? Gonna have to buy a non carrier phone from now on.

Umm cases are sometimes difficult to come by but I know they sell cases at the mall near my house at some kiosk, also at Metro PCS, but I bought my case at Wal-Mart maybe about 2 months ago. It was actually an otter box and fits like a glove. This phones decent, sometimes can lag but otherwise I gave up on root hopes.

Only thing that could work
Ok how to do it, but some one could download the firmware from sammobile or what ever. Open the files and find out what codes to put where to have rooted firmware zip back up and upload to the internet that could be the only way around not having oem unlocked. I have downloaded firmware like this for other devices but Idk how to do the to do that exactly.

I made a thread about this already, I searched but might not have used all of the correct criteria to come to this thread at that time but this is what I found.
https://www.androidinfotech.com/2017/09/j7-prime-sm-j727t1-nougat-cf-root.html

Psych0Smil3s said:
I made a thread about this already, I searched but might not have used all of the correct criteria to come to this thread at that time but this is what I found.
https://www.androidinfotech.com/2017/09/j7-prime-sm-j727t1-nougat-cf-root.html
Click to expand...
Click to collapse
It's pointless, whoever posted that obviously doesn't own the device and hasn't got a clue.
All it's likely in succeeding to do do is soft brick the device if it even flashes at all which is unlikely.

I see unlocked US version has OEM unlock option after 14 days of first activation. There may be a hope to root with Magisk as long as getting correct ROM and boot.img from there.

mingkee said:
I see unlocked US version has OEM unlock option after 14 days of first activation. There may be a hope to root with Magisk as long as getting correct ROM and boot.img from there.
Click to expand...
Click to collapse
Nope not gonna happen. Bootloader is locked.

So i subscribed to this thread just to see if people really like this phone. After going to Metropcs and seeing what the latest phones. Turns out that i can't find a good reason to upgrade from the J700. No super Amoled, no front flash, still the same screen size and after playing with it. It just feels like a downgrade, i don't know. The only good thing about it is that it is black and has 32gb of storage which i thought it was going to be different from the 16GB version. Nope, same hardware with 32gb. I suppose the cpu is faster than the J700, but by how much faster?
Sent from my SM-J700T1 using Tapatalk

Picked up a J727t1 as a backup phone for my note 8. So far it seems fairly decent. I only want root so I can get rid of the MetroPCS splash screen and some built in apps. Aside from that, it runs surprisingly smooth. It's odd that there's no fingerprint reader though.
I'll just have to keep my eye out in this thread. Hopefully someone finds a way to root
Sent from my SM-N950U using Tapatalk

You can debloate, just downgrade to aqg1 and use a root package disabler cause they don't work on current firmware from my tests cause Knox kicks it for me. With it debloated, it eats on average 20% ram idle. You do lose restore from Samsung's side doing it which is a bummer.
Also, I use substratum and Google apps to get a black theme all around (swift black) with Nova launcher and 523 dpi. Sure paid apps, but worth it looking like stock Android.
No root, but there are work arounds if you only Google how to's and what not's

So you're telling me the j727t1 can be downgraded and rooted ( you mention the root package disabler )?
I was just researching to see if there's any unbranded firmware we could flash but I've seen where some have tried in other j7 models and lost 16 of their 32gb storage ( likely wrong pit file? ).
Id even be ok with stock TMobile firmware flashed but it seems all theirs are 16gb models too ( j727t vs j727t1 ). Didn't want to try using Comsey Odin with the TMobile package until I see something more definitive as to whether it works or not.
Sent from my SM-N950U using Tapatalk

Sorry, just a package disabler. Just so use to calling them "root" blah blah. Downgrading does work, I'm just not to sure how far back you can go. Plus all our firmware is 7.0. I'll download the first fw sammobile has to give a few root methods a try if it flashes
Yeah I've heard about flashing other carrier firmwares do work, just haven't tried myself as the 16-32 gb mess is in my way.
I know what I did was a pain, but I feel it's worth it. I only miss root for flashing roms when I needed breaks from the same old

where's the link to root SM-J727T1? This phone does not have oem unlock option so bootloader is locked. Unless an oreo update changes that; I wouldn't mess with it.

I am watching this thread even though i do not own this phone. The fact that there is no oem unlock on this phone makes me wonder if this is how it is going to be on future phones. I was reading regarding about anti-theft security on phones. By not having the option to toggle to oem unlock makes the phone more secure by forcing frp to be enabled once you link your google account to your phone. But this still does not explain why international phones do have this option available though.
In a nutshell, no oem unlock=no root or anything custom. If this is where Samsung is taking things from here on out. It is going to be a long time before anyone can figure out how to force unlock. Otherwise, no more root on Samsung devices.
Sent from my SM-J700T1 using Tapatalk