Just curious if anyone knows if this might work for the Photon Q eventually.
http://forum.xda-developers.com/showthread.php?t=2225022
We don't need that, Photon Q BL is normally unlockable officially.
Yeah, but WOULD it work if we wanted to unlock that way?
Just curious.
It would - but your warranty would still be void (because if they are actually checking it, they will use the phone's fastboot).
Yes.
The result is the same, no matter if you use the official or the unofficial way.
The qfuse is blown > the bootloader is unlocked > the moto warranty is void.
No difference.
Thanks. That's all I was wondering.
I could see where someone would prefer to use an unofficial method. Seems like Moto wants a lot of info for "permission" to mod a phone. So, maybe someone would want to unlock, but not go through registering all of that with Moto.
Warranty, swarranty. Not too concerned about that personally. My experience with warranty is that they will find a reason not to honor the warranty anyway.
kabaldan said:
Yes.
The result is the same, no matter if you use the official or the unofficial way.
The qfuse is blown > the bootloader is unlocked > the moto warranty is void.
No difference.
Click to expand...
Click to collapse
Just wondering, what exactly is the "qfuse" ? I am deducing that it is a file that tells if the Q's boot loader has been unlocked, but does it determine that fact regardless of if it's unlocked officially or unofficially? And, if done so unofficially, would re-locking the boot loader change the "qfuse" and dupe the Motorola team from determining if the boot loader has ever been unlocked? Thanks!
Moto Q stock with Arrrghhh's kernel v.0.10
galacticservant said:
Just wondering, what exactly is the "qfuse" ? I am deducing that it is a file that tells if the Q's boot loader has been unlocked, but does it determine that fact regardless of if it's unlocked officially or unofficially? And, if done so unofficially, would re-locking the boot loader change the "qfuse" and dupe the Motorola team from determining if the boot loader has ever been unlocked? Thanks!
Moto Q stock with Arrrghhh's kernel v.0.10
Click to expand...
Click to collapse
Here's some info I found:
"There are two kinds of electronic fuses: Qfuses and efuses. efuses are programmable, usually by software once and by JTAG multiple times. However, Qfuses are WORM according to the information I have, which means iff the Milestone has a security Qfuse, and it is blown, then this cannot be reversed. There is usually no software programming to the Qfuses available, it is blown once during manufacturing/initial programming."
Source
Has anyone actually tested this on the photon Q and can say beyond a shadow of a doubt? I am guessing I am not the ony person who really wishes they could unlock the bootloader but can't because moto said no when they tried the official way, but I worry that trying an untested method for another phone has a chance to brick.
Every Photon Q is unlockable the official way, even from CSpire. You have a typo somewhere.
Related
I have searched and came up with no results, can the xt926 BL unlock exploit be used in the xt925?
I ask because if I unlock my 925 with the official moto tool it will be blacklisted and i will lose warranty...
The only difference between both is the unlockable BL and the radios so it *should* work, right?
has anyone tried this?
Yes it should work, it is good for any of the Moto phones with the newer snapdragon chipset (Razr HD, Atrix HD and Razr M).
amedeh123 said:
I have searched and came up with no results, can the xt926 BL unlock exploit be used in the xt925?
I ask because if I unlock my 925 with the official moto tool it will be blacklisted and i will lose warranty...
The only difference between both is the unlockable BL and the radios so it *should* work, right?
has anyone tried this?
Click to expand...
Click to collapse
You'll still might have a warranty problem if you send it in for a repair. You might not be blacklisted and you might flash a custom logo that doesn't have the bootloader unlocked screen, but that's a superficial and cosmetic fix.
amedeh123 said:
I have searched and came up with no results, can the xt926 BL unlock exploit be used in the xt925?
I ask because if I unlock my 925 with the official moto tool it will be blacklisted and i will lose warranty...
The only difference between both is the unlockable BL and the radios so it *should* work, right?
has anyone tried this?
Click to expand...
Click to collapse
Hello, where can i find this exploit?
Thanks
PantsDownJedi said:
You'll still might have a warranty problem if you send it in for a repair. You might not be blacklisted and you might flash a custom logo that doesn't have the bootloader unlocked screen, but that's a superficial and cosmetic fix.
Click to expand...
Click to collapse
Not really, over here the warranty is honored by certified 3rd party shops that in most cases repair our phones themselves (instead of the carrier dealing with it), mostly they only check for the warranty status via IMEI number before repairing it (thats from experience). This "cosmetic fix" is exactly what im looking for.
jluiscc25 said:
Hello, where can i find this exploit?
Thanks
Click to expand...
Click to collapse
Google "motopocalypse"
coolloser said:
Yes it should work, it is good for any of the Moto phones with the newer snapdragon chipset (Razr HD, Atrix HD and Razr M).
Click to expand...
Click to collapse
anyway, since my phone isn't insured, i wont be trying this...
ill either give it some time for possible defects to arise before using the official method OR for someone that actually tries it and posts here his results
amedeh123 said:
Not really, over here the warranty is honored by certified 3rd party shops that in most cases repair our phones themselves (instead of the carrier dealing with it), mostly they only check for the warranty status via IMEI number before repairing it (thats from experience). This "cosmetic fix" is exactly what im looking for.
Google "motopocalypse"
anyway, since my phone isn't insured, i wont be trying this...
ill either give it some time for possible defects to arise before using the official method OR for someone that actually tries it and posts here his results
Click to expand...
Click to collapse
I unlocked the bootloader on my 926 on Verizon. I installed the replacement Moto boot image for the cosmetic effect. If you boot the phone into the Fastboot screen the menu does say the phone is unlocked. According to the creator of the unlock exploit, Dan Rosenberg, the unlock blows a fuse inside the CPU chip and the unlocking is permanent. Even Verizon can't re-lock it with a firmware update. Your warranty would be permanently voided. But as was said, if a third party shop is only looking for a covered IMEI you should be good.
Hi, I'm receiving my new Moto G this week and I've read that the only way to gain root access at the moment is asking motorola to unlock the bootloader and thus, losing the warranty.
1.Does Motorola keep track of those who unlock the device so, even if you relock it, your warranty is still void?
2.Is there any other possible way to do that so you don't lose warranty?
3. And if so, is anybody working on that? Because if there will be another way I'd rather wait until some awesome developer achieves that.
Yes because you have to submit “fastboot oem get_unlock_data" to Motorola on their website to get the unlock code for the Bootloader secondary there is a qfuse and/or a flag which can not be set to default (at the moment).
At the moment not.
No idea, i'll wait some time, hopefully there will be a workaround someday. But if i remember right there is no way at the moment to revert the changes once the qfuse is broken.
Read more the questions have already been answered.
Much of Qualcomm's security architecture is implemented using QFuses, which are software-programmable fuses that allow one-time configuration of device settings and cryptographic materials such as hashes or keys. Because of their physical nature, once a QFuse has been blown, it is impossible to "unblow" it to revert its original value.
Click to expand...
Click to collapse
Link: Once you REQUEST!!! the unlock code, your warranty will be voided.
Plzzz help!!!!!!!!!!!!!!!!!!!!!!
you can't
K.V.K said:
Plzzz help!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
well my friend sry but you can't restore this code
most of devices like samsung,motorola etc they have.... lets say a key for the bootloader(is the door) and this key if you root your device
breaks and the half key stays inside the door hole to reminds you that the key is broken(the devicesis root/unlockbootloader).
so if you root any motorola device the code state goes
automatically 2 and stays like this,you can flash again the stock rom and relock the bootloader sure
but the code stays 2 for ever.
i hope to help you
moto g XT1541 stock rom 6.0.1 lockbootloader
bromoxitos said:
well my friend sry but you can't restore this code
most of devices like samsung,motorola etc they have.... lets say a key for the bootloader(is the door) and this key if you root your device
breaks and the half key stays inside the door hole to reminds you that the key is broken(the devicesis root/unlockbootloader).
so if you root any motorola device the code state goes
automatically 2 and stays like this,you can flash again the stock rom and relock the bootloader sure
but the code stays 2 for ever.
i hope to help you
moto g XT1541 stock rom 6.0.1 lockbootloader
Click to expand...
Click to collapse
I'm not exactly sure what you are saying, but I think the jist of it is how do you relock the bootloader... the answer is you cannot, once it is unlocked it will always report as unlocked, even if you reflash stock and find a way to relock the device.
When you unlocked your device, it was plainly stated in the disclosure on the website that once the bootloader is unlocked, it is irreversible.
yeap
acejavelin said:
I'm not exactly sure what you are saying, but I think the jist of it is how do you relock the bootloader... the answer is you cannot, once it is unlocked it will always report as unlocked, even if you reflash stock and find a way to relock the device.
When you unlocked your device, it was plainly stated in the disclosure on the website that once the bootloader is unlocked, it is irreversible.
Click to expand...
Click to collapse
YEAAA we say the same think,but i use an othey way to say it.
i say in the end you can relock the bootloader (more or less) when i say this i mean that you put some partitions back in boot loader
so when you flash the stock rom you can take any ota update,but the main bootloader is unlock always.
i know that form my old moto g2gen, moto x2013!!!
bromoxitos said:
YEAAA we say the same think,but i use an othey way to say it.
i say in the end you can relock the bootloader (more or less) when i say this i mean that you put some partitions back in boot loader
so when you flash the stock rom you can take any ota update,but the main bootloader is unlock always.
i know that form my old moto g2gen, moto x2013!!!
Click to expand...
Click to collapse
You could relock the bootloader on older Motos, but not anymore... Actually, it can be relocked but it will never report as locked or relocked, it will always be reported as unlocked. I don't how to be more plain in describing this.
And yes, you can take an OTA when unlocked, as long as you have a stock ROM and recovery and your bootloader is the correct version for your ROM. If your bootload and ROM are out of sync (ie. you have a Marshmallow bootloader and a Lollipop ROM), if your bootloader and ROM are out of sync, you could potentially get into a hard bricked situation.
ohh!!
acejavelin said:
You could relock the bootloader on older Motos, but not anymore... Actually, it can be relocked but it will never report as locked or relocked, it will always be reported as unlocked. I don't how to be more plain in describing this.
And yes, you can take an OTA when unlocked, as long as you have a stock ROM and recovery and your bootloader is the correct version for your ROM. If your bootload and ROM are out of sync (ie. you have a Marshmallow bootloader and a Lollipop ROM), if your bootloader and ROM are out of sync, you could potentially get into a hard bricked situation.
Click to expand...
Click to collapse
not any more? damn....yea we say the same think,sry for my english,yea i khow what you talking about i brick my moto x like this!!! any way.
ty for the new info about bootloader.
you was 100%
were you a clear,thanks a lot,and i hope to help him
Once I sent my hard bricked phone to Motorola. I had unlocked the bootloader and done the stupid mistake of sideloading an older version and upgrading to a newer, but still older version. When it came back, it said it was Status Code 0.
Wonder how they did it.
yagyaxt1068 said:
Once I sent my hard bricked phone to Motorola. I had unlocked the bootloader and done the stupid mistake of sideloading an older version and upgrading to a newer, but still older version. When it came back, it said it was Status Code 0.
Wonder how they did it.
Click to expand...
Click to collapse
They flash the eMMC chip (internal storage chip) directly... If you could get the right image you could possibly do it yourself with a few hundred to thousand dollar investment in a proper JTAG flashing unit.
Key would be getting the right Image, this would be far more than just a normal stock fastboot image, and is probably generated on the fly per device due to differences in serial number, IMEI, etc. These types of images don't get leaked out.
acejavelin said:
I'm not exactly sure what you are saying, but I think the jist of it is how do you relock the bootloader... the answer is you cannot, once it is unlocked it will always report as unlocked, even if you reflash stock and find a way to relock the device.
When you unlocked your device, it was plainly stated in the disclosure on the website that once the bootloader is unlocked, it is irreversible.
Click to expand...
Click to collapse
ok so what if you have never root unlocked, did nothing but use as intended to be.. never trying to do anything to it. wtf would i have a code 2 status then? care to sum that up for me.. cause 100% my situation.
wiytboi said:
ok so what if you have never root unlocked, did nothing but use as intended to be.. never trying to do anything to it. wtf would i have a code 2 status then? care to sum that up for me.. cause 100% my situation.
Click to expand...
Click to collapse
You unlocked the bootloader... It doesn't matter if you actually changed anything else or not. Once it's been done, this status code can never go back to 0. If the status code is 2 and you didn't unlock the bootloader, then someone else did.
acejavelin said:
You unlocked the bootloader... It doesn't matter if you actually changed anything else or not. Once it's been done, this status code can never go back to 0. If the status code is 2 and you didn't unlock the bootloader, then someone else did.
Click to expand...
Click to collapse
No I didn't.. I don't even know how to.. I just found out about recovery mode.. Wait wait before i say that.. How do you unlock boot loader? Turning developer mode on? Going to recovery menu? I've never hard reset it.. Just soft or doing new device. You said it could work fine for a while then shirt out? Like guy I bought from did and then I bought used for couple years and then went tits up?
wiytboi said:
No I didn't.. I don't even know how to.. I just found out about recovery mode.. Wait wait before i say that.. How do you unlock boot loader? Turning developer mode on? Going to recovery menu? I've never hard reset it.. Just soft or doing new device. You said it could work fine for a while then shirt out? Like guy I bought from did and then I bought used for couple years and then went tits up?
Click to expand...
Click to collapse
You unlock the bootloader with a series of steps that includes submitting a code to Motorola and getting an unlock code back... Performing it forces a factory reset as well. It's not something you can do by accident.
The issue with Status Code 2 was that an official update could have detected that and refused to update properly or done something worse... That never happened.
If everything is working fine, the status being 2 isn't important, it just means the previous owners had unlocked the bootloader and likely rooted or otherwise modified the phone.
Hello,
I have this old motorola razr xt910 that still works just fine. LineageOS now has a rom for it so of cause I want to see if it's better then the older cyanogenmod. But back in the days of the razr, we ran safestrap because the bootloader was locked and motorola didn't release an unlock for my region or not at all. Lineage wiki page states to unlock the razr by official means or a third party. This got my thinking, if the bootloader is encrypted with an unknown key, how can third party software unlock it? There is no way I believe a simple local laptop can brute force it, so what else can such software do? So from a PC point of view, I would simply delete the partition and make a new. Now I know very little about android, so this might be blatantly obvious to others but why not just delete the bootloader partition and flash the one we want?
Thanks
No one has any answers or comments?
That sounds kind of simalar to the question I was asking basiccly there are locks in place that will brick a device if you replace bootloader files because of crc checks elsewhere.
So, I have a Moto G9 Power, and I unlocked the bootloader to fool around with root access. Then I realised, that root access wasn't all that powerful as it was on older Android versions.
You simply do not have access to the root partition on Android 10, it is mounted read-only, and it ignores all commands to remount it as read-write.
Also, the location of the Boot animation zip of this phone is wierd, it is in /product/media, not /system/media, which effectively renders all Boot animation Magisk modules or apps useless.
Plus, the battery drain once unlocked and rooted was so much more than when on stock. And other stupid idiosyncrasies made being root not all that powerful.
So I decided to un-root and relock the bootloader.
The thing is, when it was stock, in fastboot mode, it showed
Code:
oem_locked
Now after relocking it by
Code:
fastboot oem lock
it shows
Code:
flashing_locked
I'm pretty sure the difference between the two is enough for the service center to deny my warranty (which I voided by unlocking it in the first place, I know, I know. But reverting back to stock should make the service guys not notice) if something happened to the phone.
Is there any way I can get the original message back? Am I permanently screwed? Please respond, anyone.
mistersmee said:
So, I have a Moto G9 Power, and I unlocked the bootloader to fool around with root access. Then I realised, that root access wasn't all that powerful as it was on older Android versions.
You simply do not have access to the root partition on Android 10, it is mounted read-only, and it ignores all commands to remount it as read-write.
Also, the location of the Boot animation zip of this phone is wierd, it is in /product/media, not /system/media, which effectively renders all Boot animation Magisk modules or apps useless.
Plus, the battery drain once unlocked and rooted was so much more than when on stock. And other stupid idiosyncrasies made being root not all that powerful.
So I decided to un-root and relock the bootloader.
The thing is, when it was stock, in fastboot mode, it showed
Code:
oem_locked
Now after relocking it by
Code:
fastboot oem lock
it shows
Code:
flashing_locked
I'm pretty sure the difference between the two is enough for the service center to deny my warranty (which I voided by unlocking it in the first place, I know, I know. But reverting back to stock should make the service guys not notice) if something happened to the phone.
Is there any way I can get the original message back? Am I permanently screwed? Please respond, anyone.
Click to expand...
Click to collapse
As far as I know anything with custom unlocks voids warranties the thing is that message likely changes to keep people from changing it back, I'm not sure what type of checks they do or how much your providers know about the device you have but considering they don't care as long as its relocked when you turn it in you may be alright. Its not like it couldn't be unlocked by them for various other reasons like flashing stock fw if it need to be fixed in that form unless they have someway of restoring that message themselves someone on our end would have to replicate it and that would take some dedicated development to do so.
Mr.Conkel said:
As far as I know anything with custom unlocks voids warranties the thing is that message likely changes to keep people from changing it back, I'm not sure what type of checks they do or how much your providers know about the device you have but considering they don't care as long as its relocked when you turn it in you may be alright. Its not like it couldn't be unlocked by them for various other reasons like flashing stock fw if it need to be fixed in that form unless they have someway of restoring that message themselves someone on our end would have to replicate it and that would take some dedicated development to do so.
Click to expand...
Click to collapse
Oh. Ok, cool. Cheers, mate, thanks!
mistersmee said:
Oh. Ok, cool. Cheers, mate, thanks!
Click to expand...
Click to collapse
I mean Motorola G Power devices are fairly popular here, wait around and keep an eye on your devices thread considering it can be unlocked with enough time you should be given a custom rom like LOS or Crdroid. The G7 power has tons of custom access as well as other G series device from Motorola so it is very likely to get something, which would very likely enable the custom access your looking for with modifications as it will be built normally.
Cheers!
Many Android devices set a "tampered" flag - which is responsible for voiding warranty of the devices - within the bootloader what can get queried by service centers.
jwoegerbauer said:
Many Android devices set a "tampered" flag - which is responsible for voiding warranty of the devices - within the bootloader what can get queried by service centers.
Click to expand...
Click to collapse
That makes sense, hence why the message changed. Is there a way to remove that tampered flag? I know that older Samsung devices had a flash counter, which could be reset back to zero. Maybe something similar?
Mr.Conkel said:
I mean Motorola G Power devices are fairly popular here, wait around and keep an eye on your devices thread considering it can be unlocked with enough time you should be given a custom rom like LOS or Crdroid. The G7 power has tons of custom access as well as other G series device from Motorola so it is very likely to get something, which would very likely enable the custom access your looking for with modifications as it will be built normally.
Cheers!
Click to expand...
Click to collapse
Will do.
mistersmee said:
That makes sense, hence why the message changed. Is there a way to remove that tampered flag? I know that older Samsung devices had a flash counter, which could be reset back to zero. Maybe something similar?
Click to expand...
Click to collapse
IDK.
jwoegerbauer said:
IDK.
Click to expand...
Click to collapse
Ok, cool. I'll search around.
mistersmee said:
That makes sense, hence why the message changed. Is there a way to remove that tampered flag? I know that older Samsung devices had a flash counter, which could be reset back to zero. Maybe something similar?
Click to expand...
Click to collapse
No nothing like that for Moto devices.
Generally, Motorola doesn't enforce the voided warranty issue.
If the device has a factory flaw and still would be under warranty, they will cover it.
At least this is based on posts on the forum.
sd_shadow said:
No nothing like that for Moto devices.
Generally, Motorola doesn't enforce the voided warranty issue.
If the device has a factory flaw and still would be under warranty, they will cover it.
At least this is based on posts on the forum.
Click to expand...
Click to collapse
Oh. Ok, that's a relief.