Related
I did this to my own Motorola Atrix 4g running rom: HB 2.3.4 oc 1.3ghz ext4 with the newest cwm installed
***i take no responsibility if this messes up your phone. I just did it to mine tonight before the replacement arives and wanted to help anyone else worried about being charged $399 for unlocking our bootloader
1) you need to download
//www35.megaupload.com/files/70b7d352e9514672c426f9dda58d3f6e/AUTOMATIC_UNLOCK_V4.2.zip
just incase something goes wrong you can unbrick it
2) RSD lite 5.3.1
//crackflashers.com/b16/Atrix/RSDLite5.3.1.msi
3) Newest moto update 2.3.4
//gitbrew.org/~dasmoover/android/atrix/1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf.gz
boot into rsd mode and flash the official update using rsd lite, it will stop at 100% but never finish. once you see the at&t logo you can unplug if it takes forever and just wait for it to load.
after you will no longer have cwm or the "unlocked" text at boot, but all your data will still be on the phone so dont forget to wipe after.
***link #1 is only if you have problems booting after using rsd lite (i didnt need it)
EDIT_____-----____-
before doing anything, i did open up the .bat file named MAIN in the unzipped, "automatic unlock" folder. i tested out all the relevant options such as "restore to stock" and "repair boot error". I never actually used the software, but maybe just installing and initializing it was what it took to break through
steevquinn said:
I did this to my own Motorola Atrix 4g running rom: HB 2.3.4 oc 1.3ghz ext4 with the newest cwm installed
***i take no responsibility if this messes up your phone. I just did it to mine tonight before the replacement arives and wanted to help anyone else worried about being charged $399 for unlocking our bootloader
1) you need to download
//www35.megaupload.com/files/70b7d352e9514672c426f9dda58d3f6e/AUTOMATIC_UNLOCK_V4.2.zip
just incase something goes wrong you can unbrick it
2) RSD lite 5.3.1
//crackflashers.com/b16/Atrix/RSDLite5.3.1.msi
3) Newest moto update 2.3.4
//gitbrew.org/~dasmoover/android/atrix/1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf.gz
boot into rsd mode and flash the official update using rsd lite, it will stop at 100% but never finish. once you see the at&t logo you can unplug if it takes forever and just wait for it to load.
after you will no longer have cwm or the "unlocked" text at boot, but all your data will still be on the phone so dont forget to wipe after.
***link #1 is only if you have problems booting after using rsd lite (i didnt need it)
Click to expand...
Click to collapse
And this didn't brick ur phone.
Sent from my MB860 using XDA App
anupash said:
And this didn't brick ur phone.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
amazingly, no
AFAIK the bootloader is still unlocked, it just doesn't show the "UNLOCKED" in the bootscreen anymore and reflashes/ overwrites CWM with the original ANDROID RECOVERY.
There are already several threads about this. You cannot relock the bootloader, only hide "unlocked" the boot logo screen.
But if I have already hard bricked my phone? what to do? it shows nothing ... the battery is charged
CaelanT said:
There are already several threads about this. You cannot relock the bootloader, only hide "unlocked" the boot logo screen.
Click to expand...
Click to collapse
^ This!
10char
I want to do a best buy warranty exchange (screen got lil bit scratch)....and would this method hide the "UNLOCKED" from the booting screen....is there any other method that you can hide the unlocked from the boot screen...reason being if they decide to just replace the screen and give it back the same phone...i dont wanna go through all the work....thank you...
CaelanT said:
There are already several threads about this. You cannot relock the bootloader, only hide "unlocked" the boot logo screen.
Click to expand...
Click to collapse
so...can u install custom roms: no. does it say unlocked at boot: no. so therefor it is unlocked for our purposes. The only way to unlock again is to rerun pudding. dont worry about what you've read elsewhere, im telling you this works.what other reason do u need to lock it for other than return. its people like you that cause misinformation. I did it, it works, now getting a new phone for free
---------- Post added at 11:29 AM ---------- Previous post was at 11:27 AM ----------
rockbio said:
I want to do a best buy warranty exchange (screen got lil bit scratch)....and would this method hide the "UNLOCKED" from the booting screen....is there any other method that you can hide the unlocked from the boot screen...reason being if they decide to just replace the screen and give it back the same phone...i dont wanna go through all the work....thank you...
Click to expand...
Click to collapse
dude, it takes 7 minutes...a lot of work? lol just get it done and be safe. you can always go back to before, or fix a bricked device if needed
---------- Post added at 11:35 AM ---------- Previous post was at 11:29 AM ----------
TinyRK said:
AFAIK the bootloader is still unlocked, it just doesn't show the "UNLOCKED" in the bootscreen anymore and reflashes/ overwrites CWM with the original ANDROID RECOVERY.
Click to expand...
Click to collapse
its not unlocked. you have none of the features of an unlocked phone after this process. there is no such thing as a software fuse - theres always a way to go back. remember when they said it would be impossible to have a full bootloader unlock??? a couple weeks later, what do you know, "pudding" shows up. dont post on stuff you have never tried. like they say i'll believe it when i see it.
lol.
hey OP do this.
$ sudo ./moto-fastboot oem lock
... INFOOEM lock is not implemented
or fastboot oem lock
lol.
oh ya btw. http://forum.xda-developers.com/showthread.php?t=1211198
http://forum.xda-developers.com/showthread.php?t=1260127
http://forum.xda-developers.com/showthread.php?t=1254029
http://forum.xda-developers.com/showthread.php?t=1168255
steevquinn said:
so...can u install custom roms: no. does it say unlocked at boot: no. so therefor it is unlocked for our purposes. The only way to unlock again is to rerun pudding. dont worry about what you've read elsewhere, im telling you this works.what other reason do u need to lock it for other than return. its people like you that cause misinformation. I did it, it works, now getting a new phone for free
---------- Post added at 11:29 AM ---------- Previous post was at 11:27 AM ----------
dude, it takes 7 minutes...a lot of work? lol just get it done and be safe. you can always go back to before, or fix a bricked device if needed
---------- Post added at 11:35 AM ---------- Previous post was at 11:29 AM ----------
its not unlocked. you have none of the features of an unlocked phone after this process. there is no such thing as a software fuse - theres always a way to go back. remember when they said it would be impossible to have a full bootloader unlock??? a couple weeks later, what do you know, "pudding" shows up. dont post on stuff you have never tried. like they say i'll believe it when i see it.
Click to expand...
Click to collapse
Unlocking the bootloader burns a software fuse in the bootloader. Same with the 4.9.51 update. That is what caused a lot of hard bricks. You cannot reflash the bootloader unless through nvflash with the SBK and a engineering cable, That would be the only way to patch the software fuses. This might remove the unlocked text at bootup and inhibit you from flashing roms, but the bootloader fuse is still blown, leaving proof of an unlocked bootloader.
Sent from my PG86100 using xda premium
And there's no way they can tell the phone has been unlocked when you return it? I'm thinking of exchanging my phone today. Currently unlocked and rooted.
archer75 said:
And there's no way they can tell the phone has been unlocked when you return it? I'm thinking of exchanging my phone today. Currently unlocked and rooted.
Click to expand...
Click to collapse
you can hide the "unlocked" but if they fastboot oem your phone lol then you're OOL.
I highly doubt they do though :T tbh..
darkamikaze said:
lol.
hey OP do this.
$ sudo ./moto-fastboot oem lock
... INFOOEM lock is not implemented
or fastboot oem lock
lol.
oh ya btw. http://forum.xda-developers.com/showthread.php?t=1211198
http://forum.xda-developers.com/showthread.php?t=1260127
http://forum.xda-developers.com/showthread.php?t=1254029
http://forum.xda-developers.com/showthread.php?t=1168255
Click to expand...
Click to collapse
why would i do that? i already sent my phone back, and there is absolutely no reason to relock a device for personal use. as soon as at&t recieves it, I imagine they turn it on, make sure it boots and no damage has been done. then they notify u that they recieved the phone and u are no longer the owner of it. Im sure as soon as the phone boots to the welcome screen without any weird things to indicate you have modified the phone, to at&t your phone is locked and unmodified. long before they test the phone for referbishing purposes, your account hold has been released and no one will ever know at one point their new, refurbished device was one a modded android with an unlocked bootloader, (Mod edit: Cease the abusive behavior)
armonwilson888 said:
Unlocking the bootloader burns a software fuse in the bootloader. Same with the 4.9.51 update. That is what caused a lot of hard bricks. You cannot reflash the bootloader unless through nvflash with the SBK and a engineering cable, That would be the only way to patch the software fuses. This might remove the unlocked text at bootup and inhibit you from flashing roms, but the bootloader fuse is still blown, leaving proof of an unlocked bootloader.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
No such thing as a software fuse, and if there were you could reverse it because it is software.
From IBM who developed eFuse technology:
" The patented technology, called "eFUSE," combines unique software algorithms and microscopic electrical fuses to produce chips that can regulate and adapt their own actions in response to changing conditions and system demands."
Nuff said!
steevquinn said:
why would i do that? i already sent my phone back, and there is absolutely no reason to relock a device for personal use. as soon as at&t recieves it, I imagine they turn it on, make sure it boots and no damage has been done. then they notify u that they recieved the phone and u are no longer the owner of it. afterwards, they flash all the memory and send it to be tested "thoroughly"(lol) for any internal damage before having the glass replaced and a new shell put on
Click to expand...
Click to collapse
that command will show you that your phone is still unlocked. that's why
anyway. believe us or not. but you cannot relock an unlocked device.
darkamikaze said:
that command will show you that your phone is still unlocked. that's why
anyway. believe us or not. but you cannot relock an unlocked device.
Click to expand...
Click to collapse
When you say 'device' are you only referring to Atrix?
Cus ya know.. you can relock the Xoom... just saying....
http://forum.xda-developers.com/showthread.php?t=967065
http://www.droid-life.com/2011/03/11/how-to-re-lock-the-motorola-xoom-bootloader-to-receive-updates/
CaelanT said:
No such thing as a software fuse, and if there were you could reverse it because it is software.
From IBM who developed eFuse technology:
" The patented technology, called "eFUSE," combines unique software algorithms and microscopic electrical fuses to produce chips that can regulate and adapt their own actions in response to changing conditions and system demands."
Nuff said!
Click to expand...
Click to collapse
so...your saying youve seen somewhere that says the atrix has IBMs "efuse" technology, or that it just exists to prove me wrong?
---------- Post added at 03:25 PM ---------- Previous post was at 03:21 PM ----------
TinyRK said:
WOW!
Real mature.
We just said, that the BL isn't locked. No reason to act like a kiddo and be offensive.
Grow up!
So letting others believe, that you're right is not correct, since the BL is not "re-locked."
I once did exactly what OP mentioned in the 1st post.
The UNLOCK disappeared, but the BOOTLOADER was still unlocked.
Click to expand...
Click to collapse
I said for our purposes (returning a defective unit) that the bootloader is effectivly locked. when in the process of returns does the step of running moto fast boot come into play? if that were so then the at&t techs would need to know the equivalent fastboot software for every single android phone.....HA! I doubt $9/hr at&T techs have any clue about this stuff unless they are into it on their own time
steevquinn said:
so...your saying youve seen somewhere that says the atrix has IBMs "efuse" technology, or that it just exists to prove me wrong?
---------- Post added at 03:25 PM ---------- Previous post was at 03:21 PM ----------
I said for our purposes (returning a defective unit) that the bootloader is effectivly locked. when in the process of returns does the step of running moto fast boot come into play? if that were so then the at&t techs would need to know the equivalent fastboot software for every single android phone.....HA! I doubt $9/hr at&T techs have any clue about this stuff unless they are into it on their own time
Click to expand...
Click to collapse
read
https://motorola-global-portal.cust...378/~/atrix---bootloader-mode-(efuse)-rooted*
Also, All Motorola would need to do is image the boot partition and hash that file and compare it to a hash of stock bootloader.. Two different hashes would be a dead give away that something was done to the bootloader.
Do they do that for every single return that comes in the door?? Most likely not. The probably reflash all their stuff back to it and leave it at that.
That being said.. you are arguing a failing point. The bootloader is still locked. Change the title of the thread to how to fool ATT if you have an unlocked bootloader and perhaps people will stop giving you **** about it.
steevquinn said:
so...your saying youve seen somewhere that says the atrix has IBMs "efuse" technology, or that it just exists to prove me wrong?
Click to expand...
Click to collapse
Motorola uses Efuse technology. Now I'm done with all these bootloader threads. Appears some of you will never listen, but offer no constructive arguments yourselves. I've done lots of homework myself. I'm not shooting from the hip. Believe what you wish!
Cya!
Assimilated via WinBorg 4G
Hey there.
So I tried to use the Nexus Root Toolkit to sideload the OTA, but now when I try to boot my phone it just shows the white google screen and doesn't do anything. I can use ADB and fastboot and get into the bootloader but I can't flash the factory image because I never checked the "Allow OEM Unlock" tick since I didn't plan on unlocking the bootloader. Can anyone help me out here?
Durvid said:
Hey there.
So I tried to use the Nexus Root Toolkit to sideload the OTA, but now when I try to boot my phone it just shows the white google screen and doesn't do anything. I can use ADB and fastboot and get into the bootloader but I can't flash the factory image because I never checked the "Allow OEM Unlock" tick since I didn't plan on unlocking the bootloader. Can anyone help me out here?
Click to expand...
Click to collapse
This is exactly why you should never mess with updates or flashing anything with a locked bootloader. If a factory reset doesn't fix it you're likely out of luck.
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
DON'T USE A TOOL KIT ! UNLESS YOU KNOW WHAT YOU ARE DOING ! There where clear instructions on how to flash OTA's on this site and likely in the toolkit.
Unfortunately this is a case of NOT reading before doing things, I have yet to see anyone recover from this.
Best of luck tho, but it might be a lesson learned the hardway a.k.a RMA
hutzdani said:
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
DON'T USE A TOOL KIT ! UNLESS YOU KNOW WHAT YOU ARE DOING ! There where clear instructions on how to flash OTA's on this site and likely in the toolkit.
Unfortunately this is a case of NOT reading before doing things, I have yet to see anyone recover from this.
Best of luck tho, but it might be a lesson learned the hardway a.k.a RMA
Click to expand...
Click to collapse
I'll attempt this. Weirdly enough when I look at device info in adb it shows it as being on the newest version. But Yeah I'll attempt to flash what I was on before.
Yeah, I mean I've done this before with no issues on my Nexus 6 and there were no issues but that was unlocked when I got it. I just thought you didn't have to unlock the bootloader to sideload OTA's? I may be wrong.
hutzdani said:
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
Click to expand...
Click to collapse
Yeah like I thought, "Device is locked. Cannot Flash Images"
I wish I had known they added that "Allow OEM Unlock" Switch in Lollipop. Would have solved my problem if I had that toggled.
Durvid said:
Yeah like I thought, "Device is locked. Cannot Flash Images"
I wish I had known they added that "Allow OEM Unlock" Switch in Lollipop. Would have solved my problem if I had that toggled.
Click to expand...
Click to collapse
You just said you had a nexus 6 unlocked, how did you not know the switch existed?
hutzdani said:
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
DON'T USE A TOOL KIT ! UNLESS YOU KNOW WHAT YOU ARE DOING ! There where clear instructions on how to flash OTA's on this site and likely in the toolkit.
Unfortunately this is a case of NOT reading before doing things, I have yet to see anyone recover from this.
Best of luck tho, but it might be a lesson learned the hardway a.k.a RMA
Click to expand...
Click to collapse
akellar said:
You just said you had a nexus 6 unlocked, how did you not know the switch existed?
Click to expand...
Click to collapse
I bought it used on /r/hardwareswap and whoever I got it from had already unlocked it.
I know someone advised you to try to flash a bootloader, but it isn't going to work of your bootloader is locked. What build were you on and which OTA zip did you try to flash?
Heisenberg said:
I know someone advised you to try to flash a bootloader, but it isn't going to work of your bootloader is locked. What build were you on and which OTA zip did you try to flash?
Click to expand...
Click to collapse
I started on 6.0 MDB08L and was trying to flash 6.1 MMB29M
Durvid said:
I started on 6.0 MDB08L and was trying to flash 6.1 MMB29M
Click to expand...
Click to collapse
OK, but I need the name of the zip please.
Heisenberg said:
OK, but I need the name of the zip please.
Click to expand...
Click to collapse
Sorry, it's
533df5ddfa4297997634a8553f0122be5cca4c09.signed-angler-MMB29M-from-MDB08L.zip.
Grabbed it from here: https://www.reddit.com/r/Nexus6P/comments/3w6qzd/easy_how_to_sideload_ota_601/
Durvid said:
Sorry, it's
533df5ddfa4297997634a8553f0122be5cca4c09.signed-angler-MMB29M-from-MDB08L.zip.
Grabbed it from here: https://www.reddit.com/r/Nexus6P/comments/3w6qzd/easy_how_to_sideload_ota_601/
Click to expand...
Click to collapse
OK, just needed to make sure you had the right one. What have you done to troubleshoot so far?
Heisenberg said:
OK, just needed to make sure you had the right one. What have you done to troubleshoot so far?
Click to expand...
Click to collapse
I've tied to flash stock, but can't do that due to the bootloader being locked, tried to just hard reset but it just does the same thing where it gets stuck on the Google logo. I checked the manufacture info in the toolkit and everything is clean. Tried to flash the old bootloader but like you said I can't flash since I'm locked. Not really sure what else to do :/
Durvid said:
I've tied to flash stock, but can't do that due to the bootloader being locked, tried to just hard reset but it just does the same thing where it gets stuck on the Google logo. I checked the manufacture info in the toolkit and everything is clean. Tried to flash the old bootloader but like you said I can't flash since I'm locked. Not really sure what else to do :/
Click to expand...
Click to collapse
Honestly, I think you're pretty much screwed unfortunately. You could talk to Google support and see if they'll RMA the phone.
Heisenberg said:
Honestly, I think you're pretty much screwed unfortunately. You could talk to Google support and see if they'll RMA the phone.
Click to expand...
Click to collapse
Yeah I think they would do it since I technically didn't void any warrantys or anything. I appreciate the help. What do I need to make sure to do if I do this again in the future? Definitely "Allow OEM Unlock", and do I have to unlock the bootloader? I was under the impression that you didn't have to to flash an OTA.
Durvid said:
Yeah I think they would do it since I technically didn't void any warrantys or anything. I appreciate the help. What do I need to make sure to do if I do this again in the future? Definitely "Allow OEM Unlock", and do I have to unlock the bootloader? I was under the impression that you didn't have to to flash an OTA.
Click to expand...
Click to collapse
Definitely unlock the bootloader, it isn't needed to flash an update via the stock recovery, but it is needed to get out of sticky situations like this. If your bootloader was unlocked now you'd be up and running in ten minutes.
Durvid said:
Sorry, it's
533df5ddfa4297997634a8553f0122be5cca4c09.signed-angler-MMB29M-from-MDB08L.zip.
Grabbed it from here: https://www.reddit.com/r/Nexus6P/comments/3w6qzd/easy_how_to_sideload_ota_601/
Click to expand...
Click to collapse
Hilarious that the top comment is mine telling you why doing this is a bad idea
Heisenberg said:
Definitely unlock the bootloader, it isn't needed to flash an update via the stock recovery, but it is needed to get out of sticky situations like this. If your bootloader was unlocked now you'd be up and running in ten minutes.
Click to expand...
Click to collapse
Yeah, I'll probably wait for the update over the air for a while and maybe if I feel reallly eager I'll just make sure I unlock and such. Annoying that you can't unlock via fastboot anymore without that toggle. I get that Google is trying to make Android super secure but It's not too useful for folks like us. Sure it's bricked a lot of devices.
akellar said:
Hilarious that the top comment is mine telling you why doing this is a bad idea
Click to expand...
Click to collapse
I've done it before with other devices. I wouldn't say it's inherently bad. It's just that there was one toggle that I wasn't aware of that caused the issue. You live and you learn.
THIS IS NOT MY IDEA !
I found this in a N9 thread and it worked according to the user with the issue, apply this with the correct t factory image ( do it with the version you have on your device not the one you tried to update to ! )
This might not work but its worth a try ! Before doing this read about ADB and Fastboot !!!!!!!!!!!!!!!! Try and understand the basics and know what the commands are doing to help backtrack e.C.t
If it does work - go to settings and allow OEM Unlock and USB debug !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Then go read from reputable sources how to flash images manually via adb !!!!!!!!!!!!!!!!!!!!!!!
I'd follow vomers guides.
Had this problem with another device cool thing to remeber is that on locked devices the only thing that is different is that there is a signature before the MAGIC header so the solution is to pull the android stock images from https://developers.google.com/android/nexus/images. Once done extract the images in both the zip and the tar that is inside the zip. You will see recovery.img inside the tar. One thing about the boot process of TWRP is that it enables adb in preboot meaning while in the boot loop you should have access to adb. With access to adb all you need to do is dd the images over the corresponding partitions: i.e.
PLEASE NOTE NOT FOR THE FEINT OF HEART. I AM NOT RESPONSIBLE FOR YOU BRICKING YOUR DEVICE.
Quote:
adb push recovery.img recovery.img
adb shell dd if=recovery.img of=/dev/block/<recoverymmcblock>
I dont know if the default recovery has adb push update so id probably recommend doing this on every partition thats inside the tar, i.e. system, boot.
Hey all, does anyone have a full OTA image of NPG47I?
My phone is bootlooping and the bootloader is locked and OEM unlock was not enabled so I can't flash a factory image. I tried to sideload OTAs but I can not install over newer build. Is the OTA out there anywhere? Is it possible for someone to upload it, or do I have to wait for google to upload it?
Thanks in advance
pakifood said:
Hey all, does anyone have a full OTA image of NPG47I?
My phone is bootlooping and the bootloader is locked and OEM unlock was not enabled so I can't flash a factory image. I tried to sideload OTAs but I can not install over newer build. Is the OTA out there anywhere? Is it possible for someone to upload it, or do I have to wait for google to upload it?
Thanks in advance
Click to expand...
Click to collapse
I'm in the same boat with you. I think we have to wait for google to release new build OTA.
NPG47i build date is March 8th, 2017
We need new OTA pass March 8th 2017
pakifood said:
Hey all, does anyone have a full OTA image of NPG47I? My phone is bootlooping and the bootloader is locked and OEM unlock was not enabled so I can't flash a factory image. I tried to sideload OTAs but I can not install over newer build. Is the OTA out there anywhere? Is it possible for someone to upload it, or do I have to wait for google to upload it?
Click to expand...
Click to collapse
510jungleboy said:
I'm in the same boat with you. I think we have to wait for google to release new build OTA. NPG47i build date is March 8th, 2017. We need new OTA pass March 8th 2017
Click to expand...
Click to collapse
Have you both tried doing a factory reset?
pakifood said:
Hey all, does anyone have a full OTA image of NPG47I?
My phone is bootlooping and the bootloader is locked and OEM unlock was not enabled so I can't flash a factory image. I tried to sideload OTAs but I can not install over newer build. Is the OTA out there anywhere? Is it possible for someone to upload it, or do I have to wait for google to upload it?
Thanks in advance
Click to expand...
Click to collapse
v12xke said:
Have you both tried doing a factory reset?
Click to expand...
Click to collapse
Yes I have. Numerous time.
v12xke said:
Have you both tried doing a factory reset?
Click to expand...
Click to collapse
Yes, cleared cache and factory reset. Still bootlooping. :/
With a locked bootloader I'm not aware of anything more that can be done at this point. It will be 3 weeks until the May security update... and the bad part is that the new OTA may not work either.
510jungleboy said:
I'm in the same boat with you. I think we have to wait for google to release new build OTA.
NPG47i build date is March 8th, 2017
We need new OTA pass March 8th 2017
Click to expand...
Click to collapse
Seems like OTA upload is not far away. Also seems like many others are facing bootloop issues on 7.1.2 beta 2. https://productforums.google.com/forum/#!topic/nexus/oty0zlqLN1E
pakifood said:
Hey all, does anyone have a full OTA image of NPG47I?
My phone is bootlooping and the bootloader is locked and OEM unlock was not enabled so I can't flash a factory image. I tried to sideload OTAs but I can not install over newer build. Is the OTA out there anywhere? Is it possible for someone to upload it, or do I have to wait for google to upload it?
Thanks in advance
Click to expand...
Click to collapse
Why don't you unlock your bootloader?
Wow it's here. Flashed and rebooted, still in bootloop. RIP. https://android.googleapis.com/pack.../381836b75c8f534c45c95b15912272b72200ca1f.zip there's the zip if you want, lmk if it works for you. Side note, any idea how much out of warranty RMA costs? I called them and they said they can't tell me the price until after it's repaired...
DEVILOPS 007 said:
Why don't you unlock your bootloader?
Click to expand...
Click to collapse
How can I do that? I tried in adb and it says permission denied. I never enabled bootloader unlock in developer settings.
pakifood said:
How can I do that? I tried in adb and it says permission denied. I never enabled bootloader unlock in developer settings.
Click to expand...
Click to collapse
Plug it into your computer and make sure the drivers are installed especially the adb bootloader interface. Then go to your adb and fastboot directory and put your phone in bootloader mode. Then type fastboot devices and your devices serial should show up and then type fastboot oem unlock. Are you using Windows or a Unix based OS like Linux or Mac?
DEVILOPS 007 said:
Plug it into your computer and make sure the drivers are installed especially the adb bootloader interface. Then go to your adb and fastboot directory and put your phone in bootloader mode. Then type fastboot devices and your devices serial should show up and then type fastboot oem unlock. Are you using Windows or a Unix based OS like Linux or Mac?
Click to expand...
Click to collapse
In his first post OP already stated he never enabled OEM unlock in dev settings so there is no way to unlock via ADB/fastboot.
---------- Post added at 05:38 PM ---------- Previous post was at 05:27 PM ----------
pakifood said:
Seems like OTA upload is not far away. Also seems like many others are facing bootloop issues on 7.1.2 beta 2. https://productforums.google.com/forum/#!topic/nexus/oty0zlqLN1E
Click to expand...
Click to collapse
The BLOD phenomenon is completely independent of Android build. It is a hardware defect, usually the motherboard (bad memory, cracked solder connections, etc.) In your case, the replacement part costs upwards of 60% of the original cost of the phone. Time to move on.
v12xke said:
In his first post OP already stated he never enabled OEM unlock in dev settings so there is no way to unlock via ADB/fastboot.
---------- Post added at 05:38 PM ---------- Previous post was at 05:27 PM ----------
The BLOD phenomenon is completely independent of Android build. It is a hardware defect, usually the motherboard (bad memory, cracked solder connections, etc.) In your case, the replacement part costs upwards of 60% of the original cost of the phone. Time to move on.
Click to expand...
Click to collapse
Wow. RIP nexus. Guy at Huawei support told me he had no idea how much it would cost but said "he would guess $60 but idk cause I'm not technical. I think they're just gonna redownload the software." Not tryna pay 300 dollars to get this fixed. Thanks.
Hey guys, I'm trying to fastboot OEM lock (in fastboot) however all I get is this error..
" Failed: flashing lock is not allowed"
Any tips?
I'm not sure, as I just used "fastboot oem lock" just fine a few days ago.
Try with lowercase "oem". Might not make a difference, but I know I for sure use lowercase.
ArkAngel06 said:
I'm not sure, as I just used "fastboot oem lock" just fine a few days ago.
Try with lowercase "oem".
Click to expand...
Click to collapse
Thanks for the reply! The upper case OEM was just autocorrect. I am typing in all lower case..
Fyi, I flashed back to stock recovery. Not sure if that means anything..
mazubo said:
Thanks for the reply! The upper case OEM was just autocorrect. I am typing in all lower case..
Fyi, I flashed back to stock recovery. Not sure if that means anything..
Click to expand...
Click to collapse
Yeah, mine let me lock it with TWRP installed, although it wouldn't let me into recovery or boot the phone, so I had to simply unlock it again, flash the stock recovery, and lock it for it to wipe and do it's thing.
---------- Post added at 07:27 PM ---------- Previous post was at 07:22 PM ----------
Another thought, are you in a bootloop and that's why you are trying to lock it?
If not, maybe you turned the setting off in developer options that allows OEM unlocking?
Since if that's off the error you get is very similar:
"Failed: flashing unlock is not allowed"
ArkAngel06 said:
Yeah, mine let me lock it with TWRP installed, although it wouldn't let me into recovery or boot the phone, so I had to simply unlock it again, flash the stock recovery, and lock it for it to wipe and do it's thing.
---------- Post added at 07:27 PM ---------- Previous post was at 07:22 PM ----------
Another thought, are you in a bootloop and that's why you are trying to lock it?
If not, maybe you turned the setting off in developer options that allows OEM unlocking?
Since if that's off the error you get is very similar:
"Failed: flashing unlock is not allowed"
Click to expand...
Click to collapse
No bootloop here. Just the error when trying to lock..
mazubo said:
No bootloop here. Just the error when trying to lock..
Click to expand...
Click to collapse
Did you check the setting in developer options to see if unlocking is allowed?
ArkAngel06 said:
Did you check the setting in developer options to see if unlocking is allowed?
Click to expand...
Click to collapse
Yes, I'm trying to lock. The option is greyed out, stating "device is already unlocked"
mazubo said:
Yes, I'm trying to lock. The option is greyed out, stating "device is already unlocked"
Click to expand...
Click to collapse
That's also wierd, since mine is unlocked and allows me to turn it on and off at will.
Although the way your option is makes more sense. Just strange that it's different.
ArkAngel06 said:
That's also wierd, since mine is unlocked and allows me to turn it on and off at will.
Although the way your option is makes more sense. Just strange that it's different.
Click to expand...
Click to collapse
Very weird indeed! I have never had issues locking a phone before..
I know this will sound like the silliest imaginable attempt at an answer, but having unlocked and locked plenty of phones and having watched plenty of people in this forum try to answer these sorts of questions sensibly, I'm just going to skip to the nonsensical answer I've heard people say "worked for them".
Nonsense answer: Are you by any chance trying this from a USB 3.x port rather than a USB 2.x port? If yes, then try a USB 2.0 port. I suppose the same is worth a try using the official dash cable as well.
Everything you and Arkangel have said makes total sense. Mine also doesn't show the dev "unlock" setting once it is unlocked, so that doesn't seem an issue. Of course, you should have the original stock recovery installed, but you do, so check/try that crazy thing I said and good luck.
Hello!, i managed to get the boot.img and i patched the boot.img with magisk but i cant test it becuase my phone have bootloader locked and i dont know how to unlock it.
I cant post links until i have 10 posts thats why i put a point at the beginning of the link
.drive.google.com/drive/folders/1m1ajF_GNtthYYV6SbeG0tQWSbxJGdCyD
if someone can tell me how to unlock the bootloader i will try by myself.
If it works please tell me in this post.
RlxDev said:
Hello!, i managed to get the boot.img and i patched the boot.img with magisk but i cant test it becuase my phone have bootloader locked and i dont know how to unlock it.
I cant post links until i have 10 posts thats why i put a point at the beginning of the link
.drive.google.com/drive/folders/1m1ajF_GNtthYYV6SbeG0tQWSbxJGdCyD
if someone can tell me how to unlock the bootloader i will try by myself.
If it works please tell me in this post.
Click to expand...
Click to collapse
Have you tried unlocking the bootloader threw the developers settings thee option to unlock the bootloader is the 3rd or 4th option down, personally not tried it tho?
---------- Post added at 11:19 PM ---------- Previous post was at 11:12 PM ----------
Ash180287 said:
Have you tried unlocking the bootloader threw the developers settings thee option to unlock the bootloader is the 3rd or 4th option down, personally not tried it tho?
Click to expand...
Click to collapse
Am sure your aware but if you don't know how to get to the developers menu, open settings, click system at the bottom, go to about phone, and then click your build number 7 times to unlock the developers options.
Ash180287 said:
Have you tried unlocking the bootloader threw the developers settings thee option to unlock the bootloader is the 3rd or 4th option down, personally not tried it tho?
---------- Post added at 11:19 PM ---------- Previous post was at 11:12 PM ----------
Am sure your aware but if you don't know how to get to the developers menu, open settings, click system at the bottom, go to about phone, and then click your build number 7 times to unlock the developers options.
Click to expand...
Click to collapse
I didnt try anything until there is a guide of how to do it tested previously to avoid a possible brick.
RlxDev said:
Hello!, i managed to get the boot.img and i patched the boot.img with magisk but i cant test it becuase my phone have bootloader locked and i dont know how to unlock it.
I cant post links until i have 10 posts thats why i put a point at the beginning of the link
.drive.google.com/drive/folders/1m1ajF_GNtthYYV6SbeG0tQWSbxJGdCyD
if someone can tell me how to unlock the bootloader i will try by myself.
If it works please tell me in this post.
Click to expand...
Click to collapse
Thanks for this, i would try this if i could unlock the bootloader, but i neither know how to do it.
RlxDev said:
Hello!, i managed to get the boot.img and i patched the boot.img with magisk but i cant test it becuase my phone have bootloader locked and i dont know how to unlock it.
I cant post links until i have 10 posts thats why i put a point at the beginning of the link
.drive.google.com/drive/folders/1m1ajF_GNtthYYV6SbeG0tQWSbxJGdCyD
if someone can tell me how to unlock the bootloader i will try by myself.
If it works please tell me in this post.
Click to expand...
Click to collapse
unlocking the bootloader is simple, it works exactly with the black shark helo, you enable the unlock in the developer section and then I have it in fastboot mode and you send the command "fastboot oem unlock" the smartphone will restart and make a factory reset and you will have the bootloader unlocked
Sime90ita said:
unlocking the bootloader is simple, it works exactly with the black shark helo, you enable the unlock in the developer section and then I have it in fastboot mode and you send the command "fastboot oem unlock" the smartphone will restart and make a factory reset and you will have the bootloader unlocked
Click to expand...
Click to collapse
I tried today doing everything you say, but fastboot say command doesnt exist, maybe you have chinese version(I am using global version)
RlxDev said:
Hello!, i managed to get the boot.img and i patched the boot.img with magisk but i cant test it becuase my phone have bootloader locked and i dont know how to unlock it.
I cant post links until i have 10 posts thats why i put a point at the beginning of the link
.drive.google.com/drive/folders/1m1ajF_GNtthYYV6SbeG0tQWSbxJGdCyD
if someone can tell me how to unlock the bootloader i will try by myself.
If it works please tell me in this post.
Click to expand...
Click to collapse
Enable developer function and enable OEM unlock function
pichitpongx said:
Enable developer function and enable OEM unlock function
Click to expand...
Click to collapse
Did it worked for you?
I tried that and didn't work. I have global version
Anyone managed to unlock the boot loader on this phone? I would like to get one but need root.
adkilla said:
Anyone managed to unlock the boot loader on this phone? I would like to get one but need root.
Click to expand...
Click to collapse
Ditto. Waiting on confirmation of root.
r3flux said:
Ditto. Waiting on confirmation of root.
Click to expand...
Click to collapse
I'm also waiting for root confirmation, i have BS 2 Global and unlocking boot loader tutorial was posted by a skilled member, here is the link
https://forum.xda-developers.com/bl...ck-bootloader-problem-easy-t3895992?nocache=1
---------- Post added at 11:18 PM ---------- Previous post was at 11:04 PM ----------
Also here is a full guide to unlock Black Shark 2 and seems to be effective
Steps To Unlock Bootloader On Xiaomi Black Shark 2
1.) First Of We Need To Enable Developer Options
For That Go To Settings >> About Phone >> Now Tap On MIUI Version 6-7 Times
2.) Now Go Back >> Go To Advanced Settings >> Developer Options >> Enable OEM Unlocking & Tap On Mi Unlock Status
These Things You Have To Do It On Your PC/ Laptop
3.) Go To This Link >> Then You Will See MIUI Page Tap On Unlock Now >> Now Fill The Form To Get The Permission From Xiaomi
4.) Once You Applied you will get an OTP sent to your phone, Enter that OTP on your PC >> Then Hit Next. So, this way your application gets submitted
Now You Have To Wait Until You Get A Message On Your Phone Saying “You Are Eligible To Unlock The Bootloader”
Now Follow The Unlocking Procedure
6.) Once You Got The Message >> Next You Need To Download Mi Unlock Tool & Extract It
7.) After That Just Power Off The Device,>> Now Press & Hold Volume Down + Power Button At The Same Time To Boot Into Fastboot Mode
8.) Once Your Are In Fastboot Mode >> Connect Your Phone To PC/Laptop
9.) Now Open (Mi Unlock Tool) From Your PC/Laptop
10.) Next Click On Agree & Next Enter Your Mi-Account Username, Password And Sign In
Use Same Mi Account Details Which You Already Login Into Your Phone To Unlock Bootloader
11.) Hit Next >> After That Tap On Unlock
12.) Once The Process Is Done Tap On Reboot
13.) That’s It ? You Have Successfully Unlock Bootloader Of Xiaomi Black Shark 2
For tutorial link, you can PM me, i can't post it publicly to avoid any moderator ban
Update : **
No any solution above has worked with me, seems there is no active solution for unlocking boot loader of BS2. even developer around all sites doesn't offer effective solution.
The only 2 messages that you will get when you use adb are :
adb>fastboot flashing unlock
Error : Unlock is not allowed on device has sales on market!
adb>fastboot oem unlock
Error, Unknown command
Even MI tool couldn't unlock the bootloader, If Kanded can give a solution as he is a skilled member so it will be great help
Any update? Still waiting for the XBS2 unlocking bootloader and rooting it.
I have found this about patching MM:
https://www.htcmania.com/showthread.php?t=1466079
I Hope enjoy, I have the same problem, BS2 global to root,
Anyone who tried unlocking bootloader and rooting bs2 using the bs helo? CN variant
has anybody got solution? I think this device has a potential to fullfill
So sad. Until now there's no TWRP and way to unlock bootloader of this device.
iampatricktan said:
So sad. Until now there's no TWRP and way to unlock bootloader of this device.
Click to expand...
Click to collapse
Agree. I'm planning to switch to Red Magic 3 because there really is no sign of development on this device.
batuken said:
Agree. I'm planning to switch to Red Magic 3 because there really is no sign of development on this device.
Click to expand...
Click to collapse
Yeah. I don't how can we encourage dev to look into this device, their are many users of this phone that wants to have twrp and root. Also this device is very powerful.
iampatricktan said:
Yeah. I don't how can we encourage dev to look into this device, their are many users of this phone that wants to have twrp and root. Also this device is very powerful.
Click to expand...
Click to collapse
Black Shark is independent of Xiaomi when it comes to the software development. Their team just have to release the kernel source then that's when the real thing starts. Sadly though, the Black Shark team is very lousy and their support is very poor so let's just expect that this device will get stuck to Android Pie, like what happened to Black Shark 1 which development is "dead".