Related
Wondering if it's possible to re-lock the bootloader. Would it be the same as a Nexus device?
bootloopz said:
Wondering if it's possible to re-lock the bootloader. Would it be the same as a Nexus device?
Click to expand...
Click to collapse
Yes however it will leave the tamper flag and if you used the dev site it will still be logged.
tw1tch175 said:
Yes however it will leave the tamper flag and if you used the dev site it will still be logged.
Click to expand...
Click to collapse
I know this is an older post but I've been unable to find the instructions for re-locking the bootloader. Any help would be appreciated.
I had the electrify m, the RAZR m for us cellular, and I unlocked it through Motorola. I was giving it to someone else and wanted to relock it and never found any instructions to do so. I contacted Motorola and they said once it was unlocked the was no way to relock. I would guess it's the same with the moto x.
Sent from my XT1055 using Tapatalk
fastboot oem lock doesn't work?
It does. Fastboot OEM lock. Just go back to signed software before, m Kay ? Else you won't boot
Sent from my XT1058 using xda app-developers app
I tried it with my electrify m and it wouldn't work.
Sent from my XT1055 using Tapatalk
https://plus.google.com/110773150384694258853/posts/XUF8UP9iVfi
Here's how from p3droid
tw1tch175 said:
Yes however it will leave the tamper flag and if you used the dev site it will still be logged.
Click to expand...
Click to collapse
Has anyone tried re-locking a non-dev Moto X? If so, does it get rid of the "bootloader unlocked, warranty void" message that you get every time u boot ur phone?
mschumacher69 said:
Has anyone tried re-locking a non-dev Moto X? If so, does it get rid of the "bootloader unlocked, warranty void" message that you get every time u boot ur phone?
Click to expand...
Click to collapse
Makes no difference, even when you flash the sbf firmware the logo warning still pops up, so you're best just flashing a new logo.bin file . you'll find them in the themes section, fastboot flash logo (name).bin and your done. If you need to rsdlite at any time in the future, just remove the line flash logo bin from the XML file
Sent on my Moto X
flashallthetime said:
Makes no difference, even when you flash the sbf firmware the logo warning still pops up, so you're best just flashing a new logo.bin file . you'll find them in the themes section, fastboot flash logo (name).bin and your done. If you need to rsdlite at any time in the future, just remove the line flash logo bin from the XML file
Click to expand...
Click to collapse
Even if u re-lock the bootloader?
bootloopz said:
Wondering if it's possible to re-lock the bootloader. Would it be the same as a Nexus device?
Click to expand...
Click to collapse
tw1tch175 said:
Yes however it will leave the tamper flag and if you used the dev site it will still be logged.
Click to expand...
Click to collapse
planktoid said:
It does. Fastboot OEM lock. Just go back to signed software before, m Kay ? Else you won't boot
Click to expand...
Click to collapse
Has anyone tried re-locking the bootloader of their Moto X??
mschumacher69 said:
Has anyone tried re-locking the bootloader of their Moto X??
Click to expand...
Click to collapse
Does not work for me. I get:
No valid PIV block in SP for system
chaoslimits said:
Does not work for me. I get:
No valid PIV block in SP for system
Click to expand...
Click to collapse
Did u try re-locking on your model/carrier stock rom, a stock rom from another model/carrier or a custom rom?
Thanks
mschumacher69 said:
Did u try re-locking on your model/carrier stock rom, a stock rom from another model/carrier or a custom rom?
Thanks
Click to expand...
Click to collapse
Went back to stock 4.4 via RSD Lite then tried to relock.
chaoslimits said:
Went back to stock 4.4 via RSD Lite then tried to relock.
Click to expand...
Click to collapse
Which model/carrier do u have?
mschumacher69 said:
Which model/carrier do u have?
Click to expand...
Click to collapse
Vzw Dev Edition
chaoslimits said:
Vzw Dev Edition
Click to expand...
Click to collapse
Have u tried this?
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
mschumacher69 said:
Have u tried this?
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Click to expand...
Click to collapse
Yes. That (minus userdata removal) is what RSD Lite does. I tried with fastboot and mfastboot as well.
chaoslimits said:
Yes. That (minus userdata removal) is what RSD Lite does. I tried with fastboot and mfastboot as well.
Click to expand...
Click to collapse
Weird. So is ur phone bricked now or it just did not lock?
I decided to return my phone. However, I unlocked the bootloader and have since updated to 4.4.2. I am little hesitant flashing 4.4 back, and the new firmware is not available on their website yet.
Ideally, I want to return the phone to the state I received it in, locked bootloader, stock recovery, etc.
What are my options?
Thank you.
Edit: Posted in the wrong section. Will someone please move to Q/A?
Badal
badalj said:
I decided to return my phone. However, I unlocked the bootloader and have since updated to 4.4.2. I am little hesitant flashing 4.4 back, and the new firmware is not available on their website yet.
Ideally, I want to return the phone to the state I received it in, locked bootloader, stock recovery, etc.
What are my options?
Thank you.
Edit: Posted in the wrong section. Will someone please move to Q/A?
Badal
Click to expand...
Click to collapse
I would just do a device reset and send it back how it is. Wrong software, bricked, whatever.
badalj said:
I decided to return my phone. However, I unlocked the bootloader and have since updated to 4.4.2. I am little hesitant flashing 4.4 back, and the new firmware is not available on their website yet.
Ideally, I want to return the phone to the state I received it in, locked bootloader, stock recovery, etc.
What are my options?
Thank you.
Edit: Posted in the wrong section. Will someone please move to Q/A?
Badal
Click to expand...
Click to collapse
If you upgraded to 4.4.2 then you cannot downgrade to 4.4.
Mr. Orange 645 said:
If you upgraded to 4.4.2 then you cannot downgrade to 4.4.
Click to expand...
Click to collapse
I did not realize that. Thank you!
Can someone confirm that they have successfully done this? I would hate to brick a phone I want to return.
badalj said:
I did not realize that. Thank you!
Can someone confirm that they have successfully done this? I would hate to brick a phone I want to return.
Click to expand...
Click to collapse
Confirm that they have successfully done what?
Mr. Orange 645 said:
If you upgraded to 4.4.2 then you cannot downgrade to 4.4.
Click to expand...
Click to collapse
Even with an unlocked DE?
*EDIT* I did some reading. eFuse sounds pretty crappy.
This isn't a nexus guys. We have limits. Going backwards on an x can lead to a brick.
Sent from my Moto X cellular telephone...
---------- Post added at 04:51 AM ---------- Previous post was at 04:49 AM ----------
The dev edition works no differently than any other x with an unlocked bootloader. They are exactly the same. The dev keeps the warranty, the only difference.
Sent from my Moto X cellular telephone...
badalj said:
I did not realize that. Thank you!
Can someone confirm that they have successfully done this? I would hate to brick a phone I want to return.
Click to expand...
Click to collapse
Is this on Verizon? If so, just send it back. They don't care. They send them back to Motorola to be refurbished. Don't even think twice about it.
Cozume said:
Is this on Verizon? If so, just send it back. They don't care. They send them back to Motorola to be refurbished. Don't even think twice about it.
Click to expand...
Click to collapse
Thread title says DE... DE's don't return to Carrier, they go directly to Moto, so being on Verizon wouldn't make difference.
badalj,
Why are you returning? Is it because you've changed your mind and don't want the X? or are you trying to do a warranty exchange?
Check your bootloader version. If its not 30.B4, then you should be able to flash to the 4.4 DE rom on Moto's site. If you do have 30.B4, you are stuck. If you used a 4.4.2 OTA from T-Mobile, then I wouldn't worry about being on 4.4.2.
As far as relocking your boot loader, I don't think its needed. The warranty is not voided on DE phones. But more importantly, once you click ACCEPT and request the code, they have record you have the code, and assume you unlocked. (per the wording, if you accept and request the code, non-DE phones have immediately voided their warranty.)
KidJoe said:
But more importantly, once you click ACCEPT and request the code, they have record you have the code, and assume you unlocked. (per the wording, if you accept and request the code, non-DE phones have immediately voided their warranty.)
Click to expand...
Click to collapse
Actually they can tell if you used the code or not, once you use the code on your phone then it trips the eFuse and burns it up, there is no way to repair it either, rather smart on Qualcomm/Motos part
I am just wondering if bootloader of nexus 6 from ATT is unlockable or not.
if yes, I am considering to buy one.
ahmao said:
I am just wondering if nexus 6 from ATT bootloader is unlockable or not.
if yes, I am considering to buy one.
Click to expand...
Click to collapse
Yes All Nexii have unlockable bootloaders.
That's the whole point, AFAIAC.
Yep, did it myself a few hours ago.
kashk5 said:
Yep, did it myself a few hours ago.
Click to expand...
Click to collapse
Then it can be flashed with Google factory lollipop image, right?
ahmao said:
Then it can be flashed with Google factory lollipop image, right?
Click to expand...
Click to collapse
It's already Google lollipop. Comes that way. Also stock image is posted if you should ever need to re flash.
ahmao said:
Then it can be flashed with Google factory lollipop image, right?
Click to expand...
Click to collapse
Absolutely, but there's really no reason to because the ROM on the AT&T Nexus 6 is identical to the one on models sold directly by Google and Motorola. The only difference is that AT&T utilized the boot animation partition to insert their logo and boot sound before the Android boot animation.
If you stuck an AT&T SIM into a Play Store or Motorola bought phone, you'll still end up with carrier bloatware (fortunately, it only installs two apps).
I know this is noob question and it may require a lot to answer it. I have always had at&t samsung devices this is my first nexus so rooting, bootloader unlock is new to me on this device. I was hoping someone could give me instruction list on what to do first, next, and so on for getting completely rooted, unlock bootloader, and recovery. If not i understand its a lot to ask. Thanks in advance
kashk5 said:
Absolutely, but there's really no reason to because the ROM on the AT&T Nexus 6 is identical to the one on models sold directly by Google and Motorola. The only difference is that AT&T utilized the boot animation partition to insert their logo and boot sound before the Android boot animation.
If you stuck an AT&T SIM into a Play Store or Motorola bought phone, you'll still end up with carrier bloatware (fortunately, it only installs two apps).
Click to expand...
Click to collapse
But it can immediately be removed without root, by the same means as uninstalling any program.
Thus, it's very very minimal bloat
Abostley said:
I know this is noob question and it may require a lot to answer it. I have always had at&t samsung devices this is my first nexus so rooting, bootloader unlock is new to me on this device. I was hoping someone could give me instruction list on what to do first, next, and so on for getting completely rooted, unlock bootloader, and recovery. If not i understand its a lot to ask. Thanks in advance
Click to expand...
Click to collapse
See Wugfresh Nexus Root Tool Kit in development section. Wug's tool kit, something like that. You install it on your computer then it's pretty self - explanatory
kashk5 said:
Absolutely, but there's really no reason to because the ROM on the AT&T Nexus 6 is identical to the one on models sold directly by Google and Motorola. The only difference is that AT&T utilized the boot animation partition to insert their logo and boot sound before the Android boot animation.
If you stuck an AT&T SIM into a Play Store or Motorola bought phone, you'll still end up with carrier bloatware (fortunately, it only installs two apps).
Click to expand...
Click to collapse
Is it easy to remove the carrier lock also?
ahmao said:
Is it easy to remove the carrier lock also?
Click to expand...
Click to collapse
No idea, I'm not sure whether anyway has attempted to remove it yet. Most people have only just gotten their hands on the AT&T variant within the last 24-48 hours, so it'll probably take a little time.
I bought my Nexus 6 through AT&T last November. It is paid off and I am in my normal right to unlock. I requested my code from AT&T, but it doesn't work when entered. Anyone else experience this? I get the unsuccessful error upon entering the code.
I do have the boot loader unlocked, customer Kernel, and root. Does this make a difference and potentially could be causing my issue?? Any other solutions?
Thanks
roaddaw9 said:
I bought my Nexus 6 through AT&T last November. It is paid off and I am in my normal right to unlock. I requested my code from AT&T, but it doesn't work when entered. Anyone else experience this? I get the unsuccessful error upon entering the code.
I do have the boot loader unlocked, customer Kernel, and root. Does this make a difference and potentially could be causing my issue?? Any other solutions?
Thanks
Click to expand...
Click to collapse
I don't think it's the modifications to your device. My N6 was bootloader unlocked, decrypted kernel, and rooted when I used the AT&T supplied carrier unlock code.
FWIW: the 1st attempt to unlock it, it didn't work for me. On the 2nd attempt (after a reboot in between) it did work. Sorry, but I don't have a clue why...
cam30era said:
I don't think it's the modifications to your device. My N6 was bootloader unlocked, decrypted kernel, and rooted when I used the AT&T supplied carrier unlock code.
FWIW: the 1st attempt to unlock it, it didn't work for me. On the 2nd attempt (after a reboot in between) it did work. Sorry, but I don't have a clue why...
Click to expand...
Click to collapse
I think you might have to be stock for the code to work. I know some of my phones in the past, you had to be stock.
jawmail said:
I think you might have to be stock for the code to work. I know some of my phones in the past, you had to be stock.
Click to expand...
Click to collapse
You might be right. But, for God's sake, don't relock the bootloader!
jawmail said:
I think you might have to be stock for the code to work. I know some of my phones in the past, you had to be stock.
Click to expand...
Click to collapse
I remember a carrier version of the HTC hero wouldn't accept the code on stock. I had to root and Rom it to get the code to work.. That's how I got into all this.
danarama said:
I remember a carrier version of the HTC hero wouldn't accept the code on stock. I had to root and Rom it to get the code to work.. That's how I got into all this.
Click to expand...
Click to collapse
Son got robbed of his phone (S6) today at knife point. Good luck activating that ****er.
Hey guys,
Not sure if I am going to be able to do anything about this. I signed up for the OTA beta program, device downloaded the OTA. When I got to the flashing stage it went to recovery and failed for some reason. Now I am unable to boot the device just gets stuck at Google splash screen. Cannot OEM unlock in fastboot because it was not enabled in developer options prior so flashing any images is out of the question. Is there any hope for me past this point or is the device bricked?
wolfnumba1 said:
Hey guys,
Not sure if I am going to be able to do anything about this. I signed up for the OTA beta program, device downloaded the OTA. When I got to the flashing stage it went to recovery and failed for some reason. Now I am unable to boot the device just gets stuck at Google splash screen. Cannot OEM unlock in fastboot because it was not enabled in developer options prior so flashing any images is out of the question. Is there any hope for me past this point or is the device bricked?
Click to expand...
Click to collapse
reboot into bootloader mode and flash that way. OTA is the worst way to update, IMO.
mikeprius said:
reboot into bootloader mode and flash that way. OTA is the worst way to update, IMO.
Click to expand...
Click to collapse
I can't flash images with a locked bootloader or is there a way around that?
wolfnumba1 said:
I can't flash images with a locked bootloader or is there a way around that?
Click to expand...
Click to collapse
the OTA wiped your custom recovery and didn't load the ROM properly !??!?!?! Yikes....................if your phone has stock recovery and the bootloader is locked then it is bricked and you need to send it in.
Device was completely stock, including recovery no custom recovery or root or anything.
That's strange....
mikeprius said:
That's strange....
Click to expand...
Click to collapse
Lol I know tell me about it.... I am going to see if motorola will send me a replacement but not to confident they will.
did you have root before taking the ota? anyways, sounds like you have the first N brick.
wolfnumba1 said:
Lol I know tell me about it.... I am going to see if motorola will send me a replacement but not to confident they will.
Click to expand...
Click to collapse
They may....I think the big question is if they still have any in stock......anyways, let us know what happens....that's a very unfortunate situation. The first thing I did when I got my phone was unlock the bootloader and I have not re-locked it since.
simms22 said:
did you have root before taking the ota? anyways, sounds like you have the first N brick.
Click to expand...
Click to collapse
No did not have root, was completely stock.
mikeprius said:
They may....I think the big question is if they still have any in stock......anyways, let us know what happens....that's a very unfortunate situation. The first thing I did when I got my phone was unlock the bootloader and I have not re-locked it since.
Click to expand...
Click to collapse
Yea sucks, device is out of warranty so I am SOL it seems. Lol I don't unlock because it breaks android pay and other security features which I did not want to disable.
wolfnumba1 said:
No did not have root, was completely stock.
Click to expand...
Click to collapse
yea, read. i was going to post when no one else posted, but had a customer walk in. by the time i posted it was too late :angel:
wolfnumba1 said:
Yea sucks, device is out of warranty so I am SOL it seems. Lol I don't unlock because it breaks android pay and other security features which I did not want to disable.
Click to expand...
Click to collapse
This is even more unfortunate. You can use Android Pay with an unlocked bootloader. I've flashed my phone back to stock images with the bootloader unlocked and Android Pay works. It's not contingent on a locked bootloader, only factory stock images.
mikeprius said:
This is even more unfortunate. You can use Android Pay with an unlocked bootloader. I've flashed my phone back to stock images with the bootloader unlocked and Android Pay works. It's not contingent on a locked bootloader, only factory stock images.
Click to expand...
Click to collapse
Oh weird, when you check off the allow oem unlock it says disabled security features, I wonder what that means then... yes it sucks, now a very nice looking paperweight lol
wolfnumba1 said:
Oh weird, when you check off the allow oem unlock it says disabled security features, I wonder what that means then... yes it sucks, now a very nice looking paperweight lol
Click to expand...
Click to collapse
That's just a general warning. No bearing on AP.......well you may be able to sell the phone as some people may buy it. I'm sure someone out there has a way to get it back, but I'm not sure how. I recall seeing a thread where someone in Cambodia did the same thing and he took it to a shop that was able to reverse it.....
mikeprius said:
That's just a general warning. No bearing on AP.......well you may be able to sell the phone as some people may buy it. I'm sure someone out there has a way to get it back, but I'm not sure how. I recall seeing a thread where someone in Cambodia did the same thing and he took it to a shop that was able to reverse it.....
Click to expand...
Click to collapse
Lol really? Recall where?
wolfnumba1 said:
Lol really? Recall where?
Click to expand...
Click to collapse
I can't find the thread, but I did find this one:
http://forum.xda-developers.com/nexus-6/help/nexus-6-bricked-november-security-ota-t3242773
It looks like you are not the first to be bricked with an OTA update. There should be a sticky about this issue moving forward.
mikeprius said:
I can't find the thread, but I did find this one:
http://forum.xda-developers.com/nexus-6/help/nexus-6-bricked-november-security-ota-t3242773
It looks like you are not the first to be bricked with an OTA update. There should be a sticky about this issue moving forward.
Click to expand...
Click to collapse
Lol so ****ty, looks like the phone is ****ed
wolfnumba1 said:
Hey guys,
Not sure if I am going to be able to do anything about this. I signed up for the OTA beta program, device downloaded the OTA. When I got to the flashing stage it went to recovery and failed for some reason. Now I am unable to boot the device just gets stuck at Google splash screen. Cannot OEM unlock in fastboot because it was not enabled in developer options prior so flashing any images is out of the question. Is there any hope for me past this point or is the device bricked?
Click to expand...
Click to collapse
Count me in as one of the potentially many more that bricked his phone while trying out the Beta program via OTA...
sorry to tell you this , but with locked bootloader , your phone is hard bricked, no way to recover, only by sending it back to motorola or amazon if you bought from them. i sold about 100 pieces of nexus 6 to customers and my first advice to them is to check " Enable oem unlocking "
anyway email google and blame them for this and i am sure they will help