Related
I had a interesting Chat session today with a Moto CSR here is the log:
Me: I purchased a Used Motorola Droid RAZR HD (Verizon) Retail Version Phone. The purpose was to work on android development. I am interested in unlocking my bootloader for that purpose. The phone itself is out of warranty and therefore I am not concerned about voiding the non-existent warranty. Your Bootloader Unlock webpage here seems to not allow me to do so as it is not developer edition.
Me: From my understanding a Dev Version is the only phone listed. However as previously stated I am out of warranty and wondering if it were possible through customer support to unlock my bootloader.
Gerald Ray: I see. Thanks for the information. Please know that here with Motorola we do not advice to unlock the Bootloader of our phones and for that we don't have steps to do it. If you need further assistance, you may check our nearest Repair Center in your area.
Me: Sorry your response is not clarifying.
Me: Is it possible to unlock the bootloader of a Retail XT926 Motorola Droid RAZR HD that is a Non-Developer version?
Gerald Ray: Yes, it is possible.
Me: I live in Sacramento California where is the nearest Motorola Repair center?
Gerald Ray: This is the site to check: http://www.service-center-locator.com/motorola/motorola-service-center.htm
Gerald Ray: Is there anything else that I can assist you today aside from this?
Me: based on the information provided it seems there are no service centers in my immediate area
Gerald Ray: I understand. You may check the nearest one.
Me: Does this require for me to be there in person?
Gerald Ray: You may try calling them first. We have phone numbers from that site.
Me: Ok thank you
I have emailed three of the service centers provided on the webpage he indicated to get their response to this possibility. I will update the thread once I get confirmation or denial of the ability to unlock the bootloader from the service center.
This thread has potential!
As long as the latest ota hasn't been applied, you can unlock the boot loader. Not sure why you're going through all the hassles of calling a csr.
That is unless you're talking about a phone that does have the latest ota which patches the boot loader unlock exploit.
Sent from my Droid RAZR HD under an Eclipse.
I hoping it works because I have a RAZR Maxx HD... That I would like to unlock the boatloader.
Sent from my SGH-T889 using Tapatalk
Y
TheGman125 said:
I hoping it works because I have a RAZR Maxx HD... That I would like to unlock the boatloader.
Sent from my SGH-T889 using Tapatalk
Click to expand...
Click to collapse
Unless another exploit has been found for the latest ota, and believe me we would know if there was, you will not be able to unlock the bootloader unless the phone was already unlocked before the ota.
The ability to unlock the bootloader on the hds was due to a security exploit in the code that existed before the latest ota. Using this exploit, Dan came up with code that fooled the phone into unlocking the bootloader. Once it did this, there was an eFuse that was blown to signal that the bootloader was unlocked. This fuse cannot be reset ever back to a locked state.
However, if you applied the ota before unlocking the bootloader, then what the ota did was patch/fix the exploit which means Dan's unlocking code no longer works, therefore you cannot unlock the bootloader.
It took Dan a long time to find the exploit. He has stated he does not have the time to look for a different one. In fact, there may not be another one. We were lucky that the first one was even found.
So unless Motorola decides to allow the hds to be part of the unlocking tool, I would not hold my breath.
The only other hope for you is if someone were to get kexec running on the HD. However, since because of the (now closed) exploit, no one has attempted it. Since a lot of people have their phones unlocked, I don't think the developers are working on kexec.
Plus, with the HDs being about a year old, and newer phones especially are being released, I just don't see anyone putting forth the time and effort to do this.
But, you could always put out a bounty to see if you raise enough cash to give someone if they attempt and succeed. Usually these don't result in anything coming to fruition.
Sent from my Nexus 7 using Tapatalk 4
iBolski said:
Y
Unless another exploit has been found for the latest ota, and believe me we would know if there was, you will not be able to unlock the bootloader unless the phone was already unlocked before the ota.
The ability to unlock the bootloader on the hds was due to a security exploit in the code that existed before the latest ota. Using this exploit, Dan came up with code that fooled the phone into unlocking the bootloader. Once it did this, there was an eFuse that was blown to signal that the bootloader was unlocked. This fuse cannot be reset ever back to a locked state.
However, if you applied the ota before unlocking the bootloader, then what the ota did was patch/fix the exploit which means Dan's unlocking code no longer works, therefore you cannot unlock the bootloader.
It took Dan a long time to find the exploit. He has stated he does not have the time to look for a different one. In fact, there may not be another one. We were lucky that the first one was even found.
So unless Motorola decides to allow the hds to be part of the unlocking tool, I would not hold my breath.
The only other hope for you is if someone were to get kexec running on the HD. However, since because of the (now closed) exploit, no one has attempted it. Since a lot of people have their phones unlocked, I don't think the developers are working on kexec.
Plus, with the HDs being about a year old, and newer phones especially are being released, I just don't see anyone putting forth the time and effort to do this.
But, you could always put out a bounty to see if you raise enough cash to give someone if they attempt and succeed. Usually these don't result in anything coming to fruition.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
That sounds like a good idea... Would you be able to help with that? The devices are still good and a lot of people like my self would like to try 4.3 and get that great battery life on most if my devices.
Now, could we create community in Google+ and twitter to increase awareness of the bounty?
Sent from my SGH-T889 using Tapatalk
Since my tiny hopes of N5 coming on Verizon is now official dashed, I need to unlock my phone...
i'll be patiently waiting for this thread to update!
Sorry to bring up an old thread, but apparently, no news from the op with a reply is bad news.
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.
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
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
I've been searching like a madman trying to figure out why I cannot unlock my bootloader, I have followed Heisenberg's How-To Guide For Beginners to the T and when I get to Motorola's website to get the unlock code I get this message "your device does not qualify for bootloader unlocking". My device is one of the one's listed on their website as being able to be unlocked. Can anyone help me figure this out?
Contact Motorola.
Hitti2 said:
Contact Motorola.
Click to expand...
Click to collapse
I did through chat they gave me a number to call because the person I spoke with couldn't figure it out, I just don't want them to know that I am unlocking it and put me down as a voided warranty. Just figured I'd ask here first before contacted them.
MrKite4 said:
I did through chat they gave me a number to call because the person I spoke with couldn't figure it out, I just don't want them to know that I am unlocking it and put me down as a voided warranty. Just figured I'd ask here first before contacted them.
Click to expand...
Click to collapse
Well, you can't get an unlock code from Moto AND keep your warranty. You don't even have to use it.. once you request it, warranty is gone. Not sure how hard-a$$ed they are about it, but they sure give plenty of warnings during the process.
djroese33 said:
Well, you can't get an unlock code from Moto AND keep your warranty. You don't even have to use it.. once you request it, warranty is gone. Not sure how hard-a$$ed they are about it, but they sure give plenty of warnings during the process.
Click to expand...
Click to collapse
Good to know, thanks. It's not worth it right now then I'm still covered under warranty for another 8 months and just had to send the phone out for repairs to the USB charging port.
MrKite4 said:
I've been searching like a madman trying to figure out why I cannot unlock my bootloader, I have followed Heisenberg's How-To Guide For Beginners to the T and when I get to Motorola's website to get the unlock code I get this message "your device does not qualify for bootloader unlocking". My device is one of the one's listed on their website as being able to be unlocked. Can anyone help me figure this out?
Click to expand...
Click to collapse
Just call, the warranty will be canceled, but if you relock the bootloader the recovery will tell you, so, just call and get the code, unclock that thing and welcome to the good world of guys with no time :V. Keep us updated.