Database Users

Motorola Unlock BootLoader

Is it possible to unlock flipout from this website ? https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
Also is there any custom rom for it ?

No, the Unlock My Device program at the moment supports only one new device, the Photon Q 4G LTE.
I really hope that the masterminds at Motorola will soon add many more devices, especially older ones like the Flipout. Many of these devices are out of warranty by now anyway.
As for custom ROMs, there are none. Unfortunately the Flipout was not very popular with the modders. However, with an unlocked bootloader this could change.

So... how does one 'SIM unlock' this phone?
Do I understand right, that it needs to be rooted first?
Do I need to also CID unlock it, or is that only needed for flashing a custom ROM?

DylanKeyne said:
So... how does one 'SIM unlock' this phone?
Do I understand right, that it needs to be rooted first?
Do I need to also CID unlock it, or is that only needed for flashing a custom ROM?
Click to expand...
Click to collapse
Only way for BF/Charm is by code, does not require root. Check ebay: search for "unlock mb511" or "unlock mb502" - fairly cheap these days,
Actually, bootloader unlock and carrier/sim unlock are two different things, so we're rather off-topic here.
I'm sure Moto has no interest in unlocking bootloaders of phones they've already sold, so in response to the OP I should say, "No; absolutely not; not ever."

Hopes for the Verizon S5

I have always found the best methods for customizing previous phones on XDA. I hope the developers can easily overcome any bs Verizon puts up to stop root, tether, roms!
Keep up the great work

Thus far, all domestic (US) carrier versions of the S5 have locked bootloader, knox, etc. So challenges here may not be related directly to vzw, although historical bias obviously isn't unwarranted.

tdrussell said:
Thus far, all domestic (US) carrier versions of the S5 have locked bootloader, knox, etc. So challenges here may not be related directly to vzw, although historical bias obviously isn't unwarranted.
Click to expand...
Click to collapse
This appears to not be accurate at the moment, it's looking like the 900t, T-Mobile, had shipped with an unlocked bootloader

el7145 said:
This appears to not be accurate at the moment, it's looking like the 900t, T-Mobile, had shipped with an unlocked bootloader
Click to expand...
Click to collapse
Unlocked, or unlockable?
From anandtech:
"With the Galaxy S5, KNOX has finally come full circle, as all US carrier variants are shipping with a locked bootloader. "

tdrussell said:
Unlocked, or unlockable?
From anandtech:
"With the Galaxy S5, KNOX has finally come full circle, as all US carrier variants are shipping with a locked bootloader. "
Click to expand...
Click to collapse
unlocked...feel free to check out the chainfires auto root thread, he states "if his program works on the 900t then the bootloader is unlocked"
multiple people have successfully rooted their 900t using chainfires program
http://forum.xda-developers.com/showthread.php?t=2713950
EDIT: honestly at this point the only proof we have is trusting chainfire, and his determination that if you can flash his auto root then you have an unlocked bootloader...for some people thats proof enough and for others it is not (which i completely understand)

[Q] OEM unlock on Note 4?

(my browser spazzed and I lost my last post if it shows up as a double ignore the other one!)
I'm new to Android and finding it confusing so thanks for the help so far!
I have a 910F Note 4 on Lollipop and want to root it to get rid of bloatware and possibly stop ads (if I can convince myself it's ethical) btu I *may* want to custom ROM it later.
So far your help and my reading have taught me this:
-- I can root using chainfire in order to get rid of bloat and block ads
-- If after rooting I later want a custom ROM or Xposed I'll need to get custom recovery in which case I'll be able to add CWM or TWRP later to my rooted phone
Assuming the above are true (if not please tell me!!) my question is this:
What on earth is oem unlock/bootloader unlock? In my reading I've come across people talking about this and it wiping the phone. I can't find an easy answer online. If I root +/- do CWM/TWRP will that automatically do OEM unlock or are they different things? Is bootloader unlock a different thing too? I'm confused! Will I need to root AND custom recovery AND oem unlock AND unlock bootloader?
Thanks in advance!!!

Some devices come with a locked bootloader, where you may be able to root the device via an exploit, but you can't change lower level software (ie kernel and/or recovery)... unless there is an unlock method for the bootloader.
The devices that do have a locked bootloader can be locked by the manufacturer, or by the carrier. That's the difference between the two. Either way the bootloader is still locked, only difference is who called for the locking.
For example, note 4 on tmobile does not have a locked bootloader, however, note 4 on at&t does. That decision was made by at&t, not Samsung. As far as I know, the at&t variant does not have a method for unlocking the bootloader yet so there's not much development for the device.
Compare to nexus devices, where Google automatically has the manufacturer lock the bootloader, but it being a development device, it's the easiest bootloader to unlock. It's literally a one line command in adb. HTC devices are locked but you can get an HTC dev code to unlock it from HTC.
I hope that makes sense. The best way to determine if your device has a locked bootloader is to visit the development forum or the general/Q&A forums for your device. If you have a locked bootloader and there is an unlock method, you only have to do it once (until you update or relock your bootloader). Some locked devices never get an unlock method. It designed to maintain the security and integrity of the device, but it also prevents user tampering.

Thank you for your thorough reply absinthesummer, very helpful.
However I'm still a little confused. My reading suggests to me that T-Mobile (910T) is *rootable* and the AT&T version (910S?) is not *rootable* but I'm in the UK and don't use these providers I use EE. And so I have the international variant of the Note 4 which is the 910F. I don't see a subforum or help for the UK EE version of the note 4 but as it's the 910F I assume that's the one I need to search for and not worry that EE will have put their own lock onto the 910F??
Now, because this happens to coincide with what you are saying has a locked bootloader or not, am I to assume that whether or not something is rootable is the same as whether or not it has an unlockable bootloader? i.e. is something only rootable or not because its bootloader is unlockable or not? If so therefore am I correct to assume that as the 910F which I have is rootable that it is also bootloadunlockable? And furthermore am I correct to assume that the very process of rooting itself unlocks the bootloader? Or perhaps in the case of the 910F it doesn't need to be so is even easier than Nexus devices? i.e. I just simply root and that in itself mean bootloader is already unlocked (and I am assuming that oem unlock is the same thing?)
I'm getting myself in a muddle I think!

Hehe it's totally cool, and yes your carrier could put a lock on it but that's incredibly rare in Europe due to frequent traveling between countries and the need to change Sims and carriers often... or at least that's what I've been told. The US carriers who lock their bootloaders are typically GSM carriers who do not expect you to need to root/carrier unlock/whatever. It's a control thing imo.
Anyway, your note 4 does not have a locked bootloader. If you check the development forum for your device you will see plenty of roms and guides and directions for rooting. That's usually a good indication that a device is unlocked (and those anticipating the release of new devices tend to get lock information prior to release, so they know which device they intend to buy).
Anyway, since you don't have a locked bootloader I wouldn't worry about it... that reminds me of a device I had for about a week, the LG L9. It had an oem bootloader lock but the international variant did not. We could root it & use a specially designed recovery with the bootloader locked but we couldn't flash a custom kernel (with a custom rom). They figured out that we could flash the international firmware and unlock that way, but it would make our display backwards (mirrored) and while that could be fixed, we would never be able to revert the boot screen. Now that's way too much trouble to go through just to unlock a bootloader and I did end up returning it and getting an s3 instead.
Bootloader locks are no fun, but they are not often placed on international devices for various reasons, so really I wouldn't worry about it too much.
If you get a device like a Google nexus, or an HTC that has a known locked bootloader, the bootloader and unlock method will be specifically mentioned in the routing guide. I hope that helps.
One more thing: rootability and locked bootloaders are not mutually exclusive, sometimes you can root devices with locked bootloaders and sometimes people will come up with ways around them (ie note 3 has safe strap recovery that runs parallel to stock recovery) to be able to use custom roms. However, if no exploit is found and there is no workaround, development will stall until one or both of those things is found. You may be able to root a device with a locked BL, but you may not be able to flash custom roms/kernels without a workaround. What I meant though is if you see a popular device with very little development, that's probably due to a locked bootloader and not having found a way around it yet. Most guides will explicitly mention the BL though if it's something you need to do

Yet another thoroughly helpful and detailed reply. Thank you very much indeed. You're a star!

Us t-mobile giveway to developer

I am giving away a new S7edge to a developer of my choice to work on and create root/unlock for the snapdragon version.
If you feel you are competent enough to provide root for this device then send me a PM.
If you feel you know a dev that can do it if they had the device in hand then post their name here in this thread or send me a PM. In the end I choose who gets it based on their background. I will pay for shipping, etc for the developer of choice. All I ask is for you to work diligently on this device.
This device is the future of locked, unrootable devices. The sooner we get through this barrier the better for the sake of all future devices. This isn't the end, only the beginning.
There will be no developer bashing in this thread and will have this thread closed immediately if it happens.

Good offer! This giveaway plus the bounty would hopefully entice someone. It's a good chunk of $$$!! I really hope someone with enough time and smarts would find root. I can live with TW as long as it is rooted (I'm a rooted 930F user). See T-Mobile Galaxy S7 Edge and AT&T forums for the bounty threads. I think there is another thread on the Sprint S7 forum as well.
OP's giveaway is for an SM-G935T, Qualcomm SnapDragon SD 820 Galaxy S7 Edge. All US variants are the same (SM-G935T/A/P/V) . A root for SM-G935T should work on the regular US S7 as well (SM-G930T/A/P/V). It is bootloader-locked and it will remain so unless Samsung releases an unlock, but due to the way the BL was locked, it would be near impossible anyway. So, no custom ROM.
It may be rootable if a stable exploit can be found. Folks have been comparing the US SnapDragon to Chinese SnapDragon S7, but it is not comparable. Here is a good summary regarding the bootloader situation:
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

Thread closed
There is already a thread on it here
http://forum.xda-developers.com/tmobile-s7-edge/how-to/t-mobile-s7edge-to-developer-t3383568

Looking for straight forward answer.can verizon htc 10 be debranded?

Since theres no straight forward answer and the guides seem to be all over the place i was looking for a straight forward answer.can this be unbranded to like the dev edition or something else?

gillim74 said:
Since theres no straight forward answer and the guides seem to be all over the place i was looking for a straight forward answer.can this be unbranded to like the dev edition or something else?
Click to expand...
Click to collapse
Here is about all I can find from someone reliable.
http://forum.xda-developers.com/showpost.php?p=68150390&postcount=866
--To me this says - it should be fine to flash the full US Unlocked RUU/firmware, which is x.xx.617.x, I think the latest is 1.91.617.1
I personally have flashed the pmic-8996-1.img from multiple firmwares including, International, US Unlocked, and Tmobile testing out WiFi drain. So, some bits are ok, but the aboot.img (bootloader) contains the partition, so anything other than VZW or the US Unlocked could result in a brick.
Until someone takes the plunge and reports back, or unless their are people out there whom have done this but not seen the posts asking the question. So hopefully if they are out there they will see this thread and comment.

andybones said:
Here is about all I can find from someone reliable.
http://forum.xda-developers.com/showpost.php?p=68150390&postcount=866
--To me this says - it should be fine to flash the full US Unlocked RUU/firmware, which is x.xx.617.x, I think the latest is 1.91.617.1
I personally have flashed the pmic-8996-1.img from multiple firmwares including, International, US Unlocked, and Tmobile testing out WiFi drain. So, some bits are ok, but the aboot.img (bootloader) contains the partition, so anything other than VZW or the US Unlocked could result in a brick.
Until someone takes the plunge and reports back, or unless their are people out there whom have done this but not seen the posts asking the question. So hopefully if they are out there they will see this thread and comment.
Click to expand...
Click to collapse
Ive read this but theres no straight answer in theory it seems possible http://forum.xda-developers.com/htc-10/how-to/guide-how-to-drand-convert-htc-10-to-t3374593

gillim74 said:
Ive read this but theres no straight answer in theory it seems possible http://forum.xda-developers.com/htc-10/how-to/guide-how-to-drand-convert-htc-10-to-t3374593
Click to expand...
Click to collapse
Yea. I guess just gotta wait to see if anyone has tried it, or pull the trigger yourself.

Mods can you please delete this thread as i got my answer and it wont help me in what i was trying to do please

andybones said:
Here is about all I can find from someone reliable.
http://forum.xda-developers.com/showpost.php?p=68150390&postcount=866
--To me this says - it should be fine to flash the full US Unlocked RUU/firmware, which is x.xx.617.x, I think the latest is 1.91.617.1
I personally have flashed the pmic-8996-1.img from multiple firmwares including, International, US Unlocked, and Tmobile testing out WiFi drain. So, some bits are ok, but the aboot.img (bootloader) contains the partition, so anything other than VZW or the US Unlocked could result in a brick.
Until someone takes the plunge and reports back, or unless their are people out there whom have done this but not seen the posts asking the question. So hopefully if they are out there they will see this thread and comment.
Click to expand...
Click to collapse
I had asked you about this very same thing a couple days back in the Root thread. Glad you were able to find a reliable post, thanks.

Tarima said:
I had asked you about this very same thing a couple days back in the Root thread. Glad you were able to find a reliable post, thanks.
Click to expand...
Click to collapse
Very welcome, my friend. :good:

andybones said:
Very welcome, my friend. :good:
Click to expand...
Click to collapse
Reviving this to ask a related question:
Can I safely flash the latest U.S Unlocked radio to my VZW 10 which has the latest VZW firmware?

If you flash the unlocked radio you will most likely lose all your verizon features such as volte and so on I would not if you use verizon services. For what purpose would you want to may I ask ? If you want to run your Verizon version on At&t or Tmobile there are threads on both I believe, but you should have support for other carriers already I believe as I think you will just get a non Verizon sim message is all but AndyBones can direct you on how to remove that nag.

M9guy said:
If you flash the unlocked radio you will most likely lose all your verizon features such as volte and so on I would not if you use verizon services. For what purpose would you want to may I ask ? If you want to run your Verizon version on At&t or Tmobile there are threads on both I believe, but you should have support for other carriers already I believe as I think you will just get a non Verizon sim message is all but AndyBones can direct you on how to remove that nag.
Click to expand...
Click to collapse
I'm not actually using the phone on Verizon network, I bought it second hand and using it on Rogers network in Canada. Everything runs fine including LTE, but reception is weaker than on my M7 (purchased from Rogers) hence my wanting to try the U.S Unlocked radios to see if things improve. Similarly voice call quality is not that great though it has improved with the 1.82 firmware upgrade.
I don't mind testing out the radio myself, just need some assurance about being able to without bricking the device due to firmware mismatch or other incompatibilities. As pointed out in this thread very little information exists out there from people who have unbranded their VZW 10s or flashed non-VZW radios.

Have you tried running the latest RUU for the Verizon HTC 10 ? This may fix your issue if you have not already. Also I think on another thread Dottat posted a method to reset your bands of some some if you look on his thread for being able to use the unlocked 10 on Verizon he has it posted on there I believe. Resetting the bands or modem has worked for some people with issues with signal.

M9guy said:
Have you tried running the latest RUU for the Verizon HTC 10 ? This may fix your issue if you have not already. Also I think on another thread Dottat posted a method to reset your bands of some some if you look on his thread for being able to use the unlocked 10 on Verizon he has it posted on there I believe. Resetting the bands or modem has worked for some people with issues with signal.
Click to expand...
Click to collapse
I'm not having an "issue" per se, I just want to see if I can get improved reception with a new radio, so I don't think an RUU flash would change much (I have already reset my modem for a separate issue).
Thanks for your help, I'm hoping that andybones or another dev can answer my question about being able to flash a non-vzw radio safely.

Tarima said:
I'm not having an "issue" per se, I just want to see if I can get improved reception with a new radio, so I don't think an RUU flash would change much (I have already reset my modem for a separate issue).
Thanks for your help, I'm hoping that andybones or another dev can answer my question about being able to flash a non-vzw radio safely.
Click to expand...
Click to collapse
Is Rogers a CDMA based carrier (I legit don't know). You may need to do an entire us unlocked swap, not sure if anybody has tried that yet with a vzw phone.

No Rogers is a GSM network but my VZW 10 works fine on it.

If by debranding you mean to convert it to US Unlocked version, then Straightforward answer: Yes. You don't need to read further if all you needed was a yes or no, but I felt I should post what I did to convert it to US unlocked from Verizon for others who might need help.
Verizon 4G LTE devices are already unlocked. So, just to be sure, I S-OFFed my device first via sunshine. While S-OFFing, I chose the option of S-OFF with locked bootloader. Then I changed the CID to BS_US001. Didn't have to change the MID as it was the same as US unlocked version, i.e. 2PS650000. Flashed latest TWRP (for nand backup just in case). Flashed US unlocked RUU 1.8X.617.X. Successfully updated to 1.96.617.2 via OTA.
One thing that I immediately noted after converting to US Unlocked version was that the option of OEM Unlocking which was previously not present in the Verizon version became available in the Developer Options. Hope it helped.

GrimJoke said:
If by debranding you mean to convert it to US Unlocked version, then Straightforward answer: Yes. You don't need to read further if all you needed was a yes or no, but I felt I should post what I did to convert it to US unlocked from Verizon for others who might need help.
Verizon 4G LTE devices are already unlocked. So, just to be sure, I S-OFFed my device first via sunshine. While S-OFFing, I chose the option of S-OFF with locked bootloader. Then I changed the CID to BS_US001. Didn't have to change the MID as it was the same as US unlocked version, i.e. 2PS650000. Flashed latest TWRP (for nand backup just in case). Flashed US unlocked RUU 1.8X.617.X. Successfully updated to 1.96.617.2 via OTA.
One thing that I immediately noted after converting to US Unlocked version was that the option of OEM Unlocking which was previously not present in the Verizon version became available in the Developer Options. Hope it helped.
Click to expand...
Click to collapse
Hi GrimJoke,
Thanks your post! Since I last posted here I've managed to do exactly as you described and ran the Unlocked RUU, updated to 1.96. Now running stock ROM and everything works great, and in fact the phone runs better than it did on vzw software.
I've noticed the same regarding OEM Unlocking. I read from Captain Throwback here that we should now be able to unlock the bootloader with htcdev and with superCID 22222222. I won't try since it's pointless for me.

Tarima said:
Hi GrimJoke,
Thanks your post! Since I last posted here I've managed to do exactly as you described and ran the Unlocked RUU, updated to 1.96. Now running stock ROM and everything works great, and in fact the phone runs better than it did on vzw software.
I've noticed the same regarding OEM Unlocking. I read from Captain Throwback here that we should now be able to unlock the bootloader with htcdev and with superCID 22222222. I won't try since it's pointless for me.
Click to expand...
Click to collapse
Thanks a lot about the bootloader unlocking part. That was the only question I had. Now my life's complete.

GrimJoke said:
If by debranding you mean to convert it to US Unlocked version, then Straightforward answer: Yes. You don't need to read further if all you needed was a yes or no, but I felt I should post what I did to convert it to US unlocked from Verizon for others who might need help.
Verizon 4G LTE devices are already unlocked. So, just to be sure, I S-OFFed my device first via sunshine. While S-OFFing, I chose the option of S-OFF with locked bootloader. Then I changed the CID to BS_US001. Didn't have to change the MID as it was the same as US unlocked version, i.e. 2PS650000. Flashed latest TWRP (for nand backup just in case). Flashed US unlocked RUU 1.8X.617.X. Successfully updated to 1.96.617.2 via OTA.
One thing that I immediately noted after converting to US Unlocked version was that the option of OEM Unlocking which was previously not present in the Verizon version became available in the Developer Options. Hope it helped.
Click to expand...
Click to collapse
how about from Verizon to complete wwe using wwe radios for international gsm network?

does volte work with tmo, att etc after gsm?