Hi guys, right now I cannot boot my phone up, it is giving me "ERROR: Slot Unbootable: Load Error"
-When I Click start it brings me back to the same screen
-Restarting bootloader brings me to back to the same screen
-Download mode errors in "ERROR: Operation Denied
-Cannot boot into recovery mode, same error (Unbootable: Load Error)
-Cannot run fastboot flashing unlock:
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.003s
-Cannot flash img :
FAILED (remote: Flashing is not allowed in Lock State)
-Cannot enable OEM Unlock in developer's option since I cannot boot the phone up.
-flash-all.bat gives me "Operation is not allowed in Lock State"
The device is used when I bought it so I cannot RMA it or get a refund.
Am I out of luck? See below for screenshot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Look into this:
https://skipsoft.net/skipsoft-unified-android-toolkit/
Sent from my [device_name] using XDA-Developers Legacy app
jasonbiggs said:
Look into this:
https://skipsoft.net/skipsoft-unified-android-toolkit/
Click to expand...
Click to collapse
That only works with OEM switch ticked, won't do anything for him now
This exact scenario happened to me as well, phone randomly vibrated and turned off and I got this.
Why not just call them and explain the issue but don't mention it being used? I'm sure they'll still RMA it.
crixley said:
That only works with OEM switch ticked, won't do anything for him now
This exact scenario happened to me as well, phone randomly vibrated and turned off and I got this.
Why not just call them and explain the issue but don't mention it being used? I'm sure they'll still RMA it.
Click to expand...
Click to collapse
To Google? Wouldn't they think it would be shady if you got the phone brand new from somewhere (like craigslist) and it wasn't working? I guess calling them wouldn't hurt.
Zilchary said:
To Google? Wouldn't they think it would be shady if you got the phone brand new from somewhere (like craigslist) and it wasn't working? I guess calling them wouldn't hurt.
Click to expand...
Click to collapse
I'm not advising anything here, but I'm not sure how they'd know. If you mention it straight off the bat I'm sure they aren't going to do anything for you.
Have you tried switching slots to see if the other one would boot by typing fastboot --set-active=b
I had a similar issue and that was able to fix it, but then again my device was unlocked, so not sure if that will help
bbacon said:
Have you tried switching slots to see if the other one would boot by typing fastboot --set-active=b
I had a similar issue and that was able to fix it, but then again my device was unlocked, so not sure if that will help
Click to expand...
Click to collapse
You can't switch slots with a locked bootloader.
I feel like we should be able to fastboot flash stock images even if bootloader locked, or at least separate the recovery from the boot image. Seems like a dumb idea how they have it currently, since if anything happens to the boot image you're stuck with a paperweight.
Not sure if you were able to get a fix, but you could always try to download the factory image and remove the "-w" from the .bat file. Of course, if there's nothing on the phone, keep the "-w" and do a full wipe.
https://developers.google.com/android/images
b00ster23 said:
Not sure if you were able to get a fix, but you could always try to download the factory image and remove the "-w" from the .bat file. Of course, if there's nothing on the phone, keep the "-w" and do a full wipe.
https://developers.google.com/android/images
Click to expand...
Click to collapse
Can't flash with a locked bootloader. They don't even allow you to flash their own signed images.
crixley said:
Can't flash with a locked bootloader. They don't even allow you to flash their own signed images.
Click to expand...
Click to collapse
I thought you could flash the image, but not sideload OTA's? Couldn't remember as I've had my VZW Pix2 unlocked.... It's possible that it's the other way around, OTA's but not images.
**EDIT**
Yep, OTA's not full images. Sounds like this PIX was botched, then the BL was locked.
https://developers.google.com/android/ota
b00ster23 said:
I thought you could flash the image, but not sideload OTA's? Couldn't remember as I've had my VZW Pix2 unlocked.... It's possible that it's the other way around, OTA's but not images.
**EDIT**
Yep, OTA's not full images. Sounds like this PIX was botched, then the BL was locked.
https://developers.google.com/android/ota
Click to expand...
Click to collapse
Yep it is a ridiculous concept, I have no idea what they were thinking. I had this exact same thing happen and needed to RMA, when if I had an unlocked bootloader I could have easily fixed it. Then I received a refurb, and with refurbs you cannot unlock the bootloader lol
I think I'm probably done with pixels after this one. The quality control is terrible.
crixley said:
Yep it is a ridiculous concept, I have no idea what they were thinking. I had this exact same thing happen and needed to RMA, when if I had an unlocked bootloader I could have easily fixed it. Then I received a refurb, and with refurbs you cannot unlock the bootloader lol
I think I'm probably done with pixels after this one. The quality control is terrible.
Click to expand...
Click to collapse
If you received a refurbished Google phone (not Verizon) that had the inability to unlock the BL, I would send that puppy back until I got one. I mean, why spend the big $$ into a phone and have a warranty, and then have features removed after using the warranty. No way in my book.
b00ster23 said:
If you received a refurbished Google phone (not Verizon) that had the inability to unlock the BL, I would send that puppy back until I got one. I mean, why spend the big $$ into a phone and have a warranty, and then have features removed after using the warranty. No way in my book.
Click to expand...
Click to collapse
Several people have sent back 3 or 4 and had the same thing happen every time. Unfortunately I can't go a week per time without a phone since I use mine for work, and they refuse to send me a new one.
crixley said:
Yep it is a ridiculous concept, I have no idea what they were thinking. I had this exact same thing happen and needed to RMA, when if I had an unlocked bootloader I could have easily fixed it. Then I received a refurb, and with refurbs you cannot unlock the bootloader lol
I think I'm probably done with pixels after this one. The quality control is terrible.
Click to expand...
Click to collapse
I have the same problem. My bootloader is unlocked. Can you please help me?
Zilchary said:
To Google? Wouldn't they think it would be shady if you got the phone brand new from somewhere (like craigslist) and it wasn't working? I guess calling them wouldn't hurt.
Click to expand...
Click to collapse
Hi @Zilchary .
So, finally what have you did?
My Pixel 2 gets that same error after December 2018 Security Patch applied.
I bought my Pixel 2 directly from Google Store USA.
So I enter the CHAT for PIXEL SUPPORT (from Google REPAIR , then Contact US), And Explain I got stuck in Bootloader locked with Error: Slot Unbootable
They immediately understand the problem and tell me I need to RMA (Return merchandise authorization) the phone,
so the Information they ASK ME was :
1) My Phone IMEI, with that info they tell me That I had purchased the Phone in Google Store
2) So they ASK for the "ORDER ID" in my account in Google Store, And with that info they ask me to choose between two options:
3) a) Me to Send first my phone, wait for delivered to them (they need to check the phone) and then send me a REFURBISHED PHONE. or b) PRE-Charge my Credit Card with the price of a Pixel 2,
so They send right now a REFURBISHED phone and IF they don't get my Pixel 2 in "X" day they will actually apply the Charge to my Credit Card.
So the way I see the matters, PIXEL 2 phones has 24 months of warranty in countrys where Google sell it, but you will have problems if YOU DON`T HAVE the "ORDER ID" of the Google Store.
If you actually have this "ORDER ID" because the seller gave you that info when you Purchase, YOU can just tell the PIXEL SUPPORT to send you the FEDEX information (the FEDEX LABEL TO SEND THE PHONE) to your NEW EMAIL (your actual email)
But If you don't have the "ORDER ID" you will have to try to contact the seller to get that "ORDER ID" or you should explain to COSTUMER SERVICES that you don't have it but that will be messy.
and don`t even imagine if the PHONE has BAD IMEI report.
Let me know what happens with your phone
and Have you try this link to github ? (read section: "ERRORS" between sections "iYTBP" (Youtube) and "CameraNX")
Hi @sabrosolatino
The phone was actually my sister's, I asked her what she did and this was her response :
I called 866 246 6453 to the google support line.
The Android reboot system came up and I couldn't reboot or get out of the same screen. The first time I called they told me to click a combination of keys to try to reboot the system. Nothing worked. He told me he needs the order ID # to process the warranty to get a replacement phone. I didn't have the order ID # and told me to call back when I have it. He also said because I don't have the order ID #, I can call their partner repair centers and bring it in to get it fixed or have someone come to the house to fix it in real time. I called the 2nd time and spoke to a different rep, he told me I have a 2-year warranty if there are no physical damages to the phone (until 4/23/20) and the next step is to ship out my phone and get a replacement. They confirmed my email address and sent me the shipping labels. He didn't need an order ID # to process the replacement.
So yes, there was nothing we could do since we couldn't boot it into recovery, ended up shipping out the phone without an order ID #.
Hope everything goes well for you!
I was also told that after she got her phone RMA'd, the phone she got was a refurbished phone at the agent said "It's basically brand new".
This isn't a new issue, it typically happens with something doesn't flash right. Using this tool and applying the monthly update helps me out of this bind every time.
that did it, select reboot bootloader then fastboot --set-active=a in command prompt window, then use the flash-all.bat with "-w" removed in the extracted factory image. Profit!
Zilchary said:
Hi guys, right now I cannot boot my phone up, it is giving me "ERROR: Slot Unbootable: Load Error"
-When I Click start it brings me back to the same screen
-Restarting bootloader brings me to back to the same screen
-Download mode errors in "ERROR: Operation Denied
-Cannot boot into recovery mode, same error (Unbootable: Load Error)
-Cannot run fastboot flashing unlock:
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.003s
-Cannot flash img :
FAILED (remote: Flashing is not allowed in Lock State)
-Cannot enable OEM Unlock in developer's option since I cannot boot the phone up.
-flash-all.bat gives me "Operation is not allowed in Lock State"
The device is used when I bought it so I cannot RMA it or get a refund.
Am I out of luck? See below for screenshot.
Click to expand...
Click to collapse
Oh, man. This is exactly what happened to my Pixel 2. I bought mine stock, new, from VZW in August 2018. November OTA came in and the phone didn't install the update properly and I landed on this screen. There was absolutely nothing I could do. A few fastboot commands would return some data but because of the locked bootloader I was SOL.
I RMA'd mine. Google didn't even ask questions. They just asked me to turn the phone in.
I'm sorry you can't RMA yours.
I don't know, friend. You might be looking at a paperweight.
Related
Hello,
I messed with my Pixel phone and now I feel it bricked. It was working fine until I update it to 8.0 Oreo. Then I rooted it using magisk.
Later, I decided to re-lock my bootloader, which was really a big mistake. I did re-lock it using the following command:
fastboot oem lock
It showed me if I lock my bootloader, it would wipe everything. I hit yes.
After that, this issue started, my phone won't start, as soon as the google logo shows up, it restarts and does the same thing everytime.
I tried to install the factory image, "sailfish" for Pixel 8.1.0, using the following command:
flash-all
it gave me an error message. It said I need to unlock the bootloader.
Of course, I tried to unlock the bootloader using the following command:
fastboot flashing unlock
It also gave me an error message, it said:
FAILED (remote: oem unlock is not allowed)
I don't know what else should I do. I tried to find a solution for my problem, but there is no clear answer.
One of the common solution is to enable the USB debugging/OEM unlocking from the developer settings. But, again, I can't even turn on my phone and use it normally.
The only thing that I can access to is the bootloader screen.
There are several threads which state "hey don't try relocking your bootloader for any reason" for a reason. You CANNOT relock these phones with ANY custom firmware or modifications. Your phone is bricked. You can try talking to Google and they /may/ rma your phone but there is 0 guarantee especially given that you did something that is a known feature and is intended to brick the phone. Can't hurt to try though
KittyRgnarok said:
There are several threads which state "hey don't try relocking your bootloader for any reason" for a reason. You CANNOT relock these phones with ANY custom firmware or modifications. Your phone is bricked. You can try talking to Google and they /may/ rma your phone but there is 0 guarantee especially given that you did something that is a known feature and is intended to brick the phone. Can't hurt to try though
Click to expand...
Click to collapse
You are totally right. I'll contact them to RMA my phone.
hamooz92 said:
You are totally right. I contact them to RMA my phone.
Click to expand...
Click to collapse
Good luck. Update the thread with the results cuz I'm curious if they will rma a phone bricked like that
The Nokia 7.2, surprisingly, comes with an unlockable bootloader. The information is shared by TechMesto and I am just re-using it to create this guide.
Notes:
Unlocking the bootloader may void the device's warranty.
All existing data on the device will be erased.
To unlock:
Update: Nokia has disabled the unlock ability with the December MR. You can only unlock if you downgrade your phone to an old release first. You can get it at Nokia Care or by buying remote flashing services.
Before you start: Make sure that you have platform-tools downloaded on your PC. You need to open a CMD or Terminal window in the folder where you have saved the platform-tools, unless you have installed them system-wide.
• First of all, enable Developer Options by tapping 7 times on BuildID in "About phone".
• Then go to developer options and enable OEM Unlocking option.
• Now reboot the phone into bootloader/fastboot mode. You can use the adb command:
Code:
adb reboot-bootloader
or else use hardware keys to reboot to bootloader mode.
• Make sure the phone is detected in fastboot mode. Then send the OEM unlocking command:
Code:
fastboot flashing unlock
• Confirm the unlock on the phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
• That's it!
You can also do the unlock_critical if you plan to flash the bootloader.
Reserved for future use.
I am on a Nokia 7.2, a dual-sim variant with 6GB RAM and 128 GB ROM. The model name is TA-1196.
I am currently having issues with this method, whenever I try to flash unlock, prior to the V1.160 update, the fastboot will report back saying "Write to device failed (unknown error)".
If anyone would enlighten me I would be happy to hear.
Edit: Currently on build number 00WW_1_060
Edit 2.0: Works after updating to build 00WW_1_160. Seems Nokia enabled this method by mistake. Who knows?
KohGeek said:
I am on a Nokia 7.2, a dual-sim variant with 6GB RAM and 128 GB ROM. The model name is TA-1196.
I am currently having issues with this method, whenever I try to flash unlock, prior to the V1.160 update, the fastboot will report back saying "Write to device failed (unknown error)".
If anyone would enlighten me I would be happy to hear.
Edit: Currently on build number 00WW_1_060
Edit 2.0: Works after updating to build 00WW_1_160. Seems Nokia enabled this method by mistake. Who knows?
Click to expand...
Click to collapse
Hi, looks like you were initially doing flash unlock instead of flashing unlock? And since there was nothing to flash, it failed.
singhnsk said:
Hi, looks like you were initially doing flash unlock instead of flashing unlock? And since there was nothing to flash, it failed.
Click to expand...
Click to collapse
I was using flashing, and as my edit has said, it seems the option to unlock the bootloader was only enabled after version 160.
KohGeek said:
I was using flashing, and as my edit has said, it seems the option to unlock the bootloader was only enabled after version 160.
Click to expand...
Click to collapse
That's okay, but the output you got wasn't appropriate for that command. If the unlock support isn't allowed it will say "flashing unlock is not allowed". Or in case the bootloader isn't including that command at all, it will say "Unknown command".
I might be wrong too, but your output isn't something i've seen on any of the phones i've owned, whether unlockable or non-unlockable. That output is what I usually get when the command is not proper, or the drivers aren't properly installed or the fastboot device isn't properly responding. Rebooting to bootloader should usually fix it. At least it does on other Nokia and Sharp phones.
singhnsk said:
That's okay, but the output you got wasn't appropriate for that command. If the unlock support isn't allowed it will say "flashing unlock is not allowed". Or in case the bootloader isn't including that command at all, it will say "Unknown command".
I might be wrong too, but your output isn't something i've seen on any of the phones i've owned, whether unlockable or non-unlockable. That output is what I usually get when the command is not proper, or the drivers aren't properly installed or the fastboot device isn't properly responding. Rebooting to bootloader should usually fix it. At least it does on other Nokia and Sharp phones.
Click to expand...
Click to collapse
I was curious too, it kicked me off the bootloader screen when I was doing that on version 060, but it seems all is well now
https://nokiamob.net/2019/11/02/off...nlock-the-nokia-7-2-and-nokia-6-2-bootloader/
I unlocked bootloader now how to root this phone they didn't released kernel source for preparing twrp should i root the phone with magisk patched boot.img??
Coolboy996 said:
I unlocked bootloader now how to root this phone they didn't released kernel source for preparing twrp should i root the phone with magisk patched boot.img??
Click to expand...
Click to collapse
You can use TWRP or patched image to root the 7.2
Can confirm that it is still unlockable. Got 2 of them today from Argos in the UK (Scotland). They are on 00WW_1_130 with security batch from 2019/08/05.
Only thing I had to do was enable internet and reboot to get the option to stop being greyed out.
Just got mine today and it forced a system update upon activation. I was unable to unlock the bootloader.
allc0re said:
Just got mine today and it forced a system update upon activation. I was unable to unlock the bootloader.
Click to expand...
Click to collapse
Are you sure? Has Horrendously Menacing Dicks actually started blocking people having reasonable control of their 7.2 devices after letting them have it for so long?
allc0re said:
Just got mine today and it forced a system update upon activation. I was unable to unlock the bootloader.
Click to expand...
Click to collapse
Yep. They blocked the ability with the most recent December MR.
singhnsk said:
Yep. They blocked the ability with the most recent December MR.
Click to expand...
Click to collapse
Ah that sucks. Did you try connecting to the internet and rebooting? That enabled the option to enable OEM Unlocking in developer settings for me.
CGarz said:
Ah that sucks. Did you try connecting to the internet and rebooting? That enabled the option to enable OEM Unlocking in developer settings for me.
Click to expand...
Click to collapse
I was able to turn on OEM Unlocking in Developer Options, but running the command in fastboot failed.
That really sucks. Now no devs will buy it =(.
allc0re said:
I was able to turn on OEM Unlocking in Developer Options, but running the command in fastboot failed.
Click to expand...
Click to collapse
I know they planned to lock it down ; however were you using the most recent fastboot (platform-tools). I know I had issues with not having most current versions.
bkttk2 said:
I know they planned to lock it down ; however were you using the most recent fastboot (platform-tools). I know I had issues with not having most current versions.
Click to expand...
Click to collapse
I also can not unlock the bootloader after update security 05/12/2019...MB no longer unlockable bootloader any more.
Lamtanloc512 said:
I also can not unlock the bootloader after update security 05/12/2019...MB no longer unlockable bootloader any more.
Click to expand...
Click to collapse
Think we may be out of luck then, but one last suggestion. I noticed when reading through the thread on user indicated they were using "flash" instead of "flashing" when trying to unlock the bootloader.
I know I personally did the same thing at first. Did anyone confirm that "flashing" was used?
I know the older methods used flash. Just asking.
OG Pixel from Verizon, had it for years, battery has been really ****ty lately. So I had to send my phone in to get a new battery, and the cost was similar to go thru google store, so I did. Wiped the phone, restored to stock android, but left bootloader unlocked. Got the phone back today and version of android was downgraded and bootloader was locked.
How ****ed am I and what are my recourses? Tried google support, they're nearly useless.
If you never booted the device yet you can try "fastboot flashing unlock" and it will just re-unlock. Other than that I don't think you will ever see a unlock status on that phone. This is why I do my repairs myself.
Fastboot flashing unlock was unsuccessful, but I suspect that was because the phone was booted up for "troubleshooting" with Google "support."
I assume then there's no way to return it to the post-flash pre-boot state without some closely guarded hardware and software?
Before updating in any way... Search Verizon unlock Pixel and see if that process will unlock. If you allow update past a certain level stuck with no options then if Verizon locked.
Oh, would never allow an update. I'm not crazy. Tried the unlock method with uninstalling the phone app before you get internet access the day I got it, still no dice. Thanks tho.
I just did a credit card chargeback as they sent me back my device in an unusable condition and refused to compensate for it. We'll see how it shakes out in a few weeks probably. Bought a refurb Pixel 3 in the meantime and it was already unlocked, so all is well.
Thanks for the replies though.
-N
n8lee said:
Fastboot flashing unlock was unsuccessful, but I suspect that was because the phone was booted up for "troubleshooting" with Google "support."
I assume then there's no way to return it to the post-flash pre-boot state without some closely guarded hardware and software?
Click to expand...
Click to collapse
Can you tell me what security patch you are on? If you are somewhere around Android 9 patch (potentially Android 10 early patches) you can re-unlock. If you try ticking the OEM unlock option in Dev options or if i heard correctly the phone wont boot? If you know your exact version you can try flashing it through recovery, or trying "fastboot unlock" after ticking the oem unlock. Also remember those old workarounds of removing android.phone and such? Yeah try those. Good luck. We'll try and get you unlocked again.
I got the Unlock Code from Moto with no problem, but can't get the phone to take it. FAIL, over and over again. I've tried several times, rebooted the phone, powered off, even tried an FDR. I keep getting a 'FAIL" message trying to push the code to the phone.
Just got the phone (used) today and I do have Unlock enabled in Dev Options. CID is 0x0032, obviously unlockabled since I did get the code from Moto. Twice. I redidthe Unlock request with a new string and got the same code again. Nothing is working. I've unlocked 15 or more Moto phones and never had anything like this happen before.
Using "fastboot oem unlock UNIQUE_KEY [20-character unlock code string]". Copied it, typed it manually, etc etc. FAIL FAIL FAIL.
Frustrating. Any clues/suggestions?
- - - - -
Edit to add: This phone has (I presume) the newest firmware on it, QZKS30.Q4-40-95-9 (RETUS), which has not been uploaded to lolinet yet.
Could this newest update be the problem? If so, can I safely roll back to 95-6 or even something older?
= = = = = = = = =
SOLVED. There was apparently an issue with the first phone I tried. Bought a second XT2113-2 relatively cheap (64GB) which came with the same 40-95-9 firmware, and it took the unlock code without a hitch.
I recall that I experienced something similar to this as well. A little bit of searching lead me to believe my issue was an older stock firmware bug. My stock firmware was initially from Jan 2021 and I did ota updates until it got to about Aug 2021 and then the phone unlocked. Can't say for sure that the deviced just needed time to "phone home" before allowing unlocking tho (I've read rumors).
If there is a ota update available, try that. I do know that I am able to relock/unlock on the 40-95-6 (Feb 2022) RETUS stock firmware.
notmyrealhandle said:
I recall that I experienced something similar to this as well. A little bit of searching lead me to believe my issue was an older stock firmware bug. My stock firmware was initially from Jan 2021 and I did ota updates until it got to about Aug 2021 and then the phone unlocked. Can't say for sure that the deviced just needed time to "phone home" before allowing unlocking tho (I've read rumors).
If there is a ota update available, try that. I do know that I am able to relock/unlock on the 40-95-6 (Feb 2022) RETUS stock firmware.
Click to expand...
Click to collapse
Thanks for replying. This phone has 40-95-9 firmware (March 1, 2022) which looks to be the latest OTA.
I have wondered if I'm stuck in another one of the newer Moto's (or Android's) mysterious holding patterns. Maybe it'll work in a few days. I will certainly post here if that's the case. . . . But why give me the Unlock button plus the Unlock Code, but then hold me back from actually pushing it to the phone? That wouldn't make a lot of sense.
This is the exact message returned by the bootloader every time:
(bootloader) usage: fastboot oem unlock < unlock code >
FAILED (remote failure)
I believe I'll try reflashing the 40-95-9 firmware, downloaded this morning via Rescue and Smart Assistant.
Reflashing firmware didn't help.
Edit to add:
I should probably stress, I flashed the entire firmware with no problems at all.
Should that suggest that this bootloader unlocking failure is not a hardware problem? . . . because if broke hardware is a possibility, I would definitely want to return this phone to the seller.
Moondroid said:
Reflashing firmware didn't help.
Edit to add:
I should probably stress, I flashed the entire firmware with no problems at all.
Should that suggest that this bootloader unlocking failure is not a hardware problem? . . . because if broke hardware is a possibility, I would definitely want to return this phone to the seller.
Click to expand...
Click to collapse
Two other things you can try:
1. make sure you are using an up to date fastboot exe (I'm using fastboot version 33.0.1-8253317 on ubuntu linux).
2. Try from both the bootloader mode and fastbootd mode on the device - I forget how to get to fastbootd from stock `adb reboot fastboot` might do it.
EDIT I'm pretty sure you want to be in the bootloader mode. Just thought I'd mention it as fastbootd was new to me and some fastboot commands seem to like the device to be in one mode or the other.
HTH
notmyrealhandle said:
Two other things you can try . . .
Click to expand...
Click to collapse
Still nothing.
I found some newer adb & fastboot utils (2021 vs 2018) and tried those. That just changed the error message a teensy bit (replaced "remote failure" with a couple of bare quote marks).
I also uninstalled & reinstalled my Motorola drivers before trying the newer adb & fastboot. That didn't help either.
Trying to boot twrp gives me a "permission denied" error.
So all I can think to try now is to run another firmware reinstall via LMSA (Rescue and Smart Assistant), just to see if that hiccups anywhere as much as anything. (I manually flashed all the files the first time.)
I think it's past time for me to say something like "this doesn't just suck, it SUPER-sucks." Moto gave me the phreaking Unlock code, but the phone won't let me use it.
Moondroid said:
Moto gave me the phreaking Unlock code, but the phone won't let me use it.
Click to expand...
Click to collapse
It will only work 48 hours after the unlock email is sent, as per this thread <https://forum.xda-developers.com/t/oem-unlocking-grayed-out-on-moto-g-play-2021.4259833/page-2>
I recently went through this myself. It was really baffling because the customer service / tech support would not tell me anything about it. Maybe it's some kind of hyper secret security measure?
Just keep the phone online and wait it out.
slipchicken said:
It will only work 48 hours after the unlock email is sent, as per this thread <https://forum.xda-developers.com/t/oem-unlocking-grayed-out-on-moto-g-play-2021.4259833/page-2>
I recently went through this myself. It was really baffling because the customer service / tech support would not tell me anything about it. Maybe it's some kind of hyper secret security measure?
Just keep the phone online and wait it out.
Click to expand...
Click to collapse
I tried the unlock code 5 minutes after I got it. Why would I wait 48 hours? Lol . . .
If this is another "time-delay" thing it doesn't make any sense at all. OEM Unlock was already enabled, the phone gave me an unlock string to send Moto, and I got the unlock key from Moto with no delays at all. Within an hour after unboxing the phone I was trying to push an unlock code to the phone.
I also tried getting another code from Moto, generated a new string and all, but the second code Moto sent me was exactly the same as the first. I did try it (again) on the phone but got the same "FAILED" message as before.
This is just nuts. Unless the latest OTA 95-9 is in fact the culprit. Moto's unlock-code process might still send unlock codes that possibly will no longer work after a certain point? Hopefully I'll get a definitive answer on this aspect soon.
Moondroid said:
Moto's unlock-code process might still send unlock codes that possibly will no longer work after a certain point? Hopefully I'll get a definitive answer on this aspect soon.
Click to expand...
Click to collapse
I meant that it will only start working once 48 hours have passed. Leaving internet active may be a requirement, and a restart may be a requirement too.
For instance if you get the first code email at 8:00am on June 7th, the code will only work after 8:00am on June 9th.
EDIT: Also I have tried manually changing the time in the phone's settings and it didn't work. I had to wait the full 48 hours for it to start working.
I do agree however that it is absolutely nuts of Motorola to do this without any sort of explanation. That's why I assume it's some kind of secretive or misguided anti-theft measure.
slipchicken said:
I meant that it will only start working once 48 hours have passed. Leaving internet active may be a requirement, and a restart may be a requirement too.
For instance if you get the first code email at 8:00am on June 7th, the code will only work after 8:00am on June 9th.
EDIT: Also I have tried manually changing the time in the phone's settings and it didn't work. I had to wait the full 48 hours for it to start working.
I do agree however that it is absolutely nuts of Motorola to do this without any sort of explanation. That's why I assume it's some kind of secretive or misguided anti-theft measure.
Click to expand...
Click to collapse
I was in that thread you quoted and I don't remember anything about having to wait AFTER getting the unlock code. Wait for OEM Unlock to show as enabled in Dev Options, yes, I'm thoroughly familiar with that. But I have never-never-never had to wait for an unlock code to work after receiving it from Moto. If that's in there somewhere please point more specifically? because I've unlocked a whole bunch of Moto phones and as I said, I've never heard of being able to enable OEM Unlock, getting the unlock code from Moto and then having to wait to use it.
See bottom of top post. The phone had some kind of problem that wouldn't allow it to accept the unlock key.
HELP! I was trying to re-lock my bootloader so I went into Developer options and turned off the OEM unlocking option, which told me to restart my device. restarting it brought me to the bootloader so I then issued the fastboot.exe flashing lock command and after that I'm getting the message No valid operating system could be found. The device will not boot. what are my options??
dimm0k said:
HELP! I was trying to re-lock my bootloader so I went into Developer options and turned off the OEM unlocking option, which told me to restart my device. restarting it brought me to the bootloader so I then issued the fastboot.exe flashing lock command and after that I'm getting the message No valid operating system could be found. The device will not boot. what are my options??
Click to expand...
Click to collapse
The correct command is fastboot flashing lock. If you can get into bootloader reflash the factory image and it should reboot
If you want to re-lock the bootloader, you need to have a completely stock ROM or have a ROM with a custom avb key flashed. Anything else will show the error you noted.
You should be able to solve this by flashing the stock OTA in recovery mode.
K1nsey6 said:
The correct command is fastboot flashing lock. If you can get into bootloader reflash the factory image and it should reboot
Click to expand...
Click to collapse
I can get into the bootloader, however here I'm seeing the message that the bootloader is already locked! tried flashing the November update, but getting the failed message that I need to be unlocked
craigacgomez said:
If you want to re-lock the bootloader, you need to have a completely stock ROM or have a ROM with a custom avb key flashed. Anything else will show the error you noted.
You should be able to solve this by flashing the stock OTA in recovery mode.
Click to expand...
Click to collapse
when I try to get to recovery mode through the bootloader, it immediately spits me back out to the message that there's no valid operating system and to press the power button to power off
Seems like you messed up and bricked your device try seeing if you can unlock your bootloader still if not contact whoever you got device off and report for warranty
dimm0k said:
when I try to get to recovery mode through the bootloader...
Click to expand...
Click to collapse
FYI, the bootloader is one of the functional recovery modes.
Try the online Google flash tool. This is what I used to flash back to stock after unrooting my device to run some tests. Although in my case, as you're meant to, I performed the flash prior to re-locking the bootloader, so it might not work for you.
Android Flash Tool
flash.android.com
minidude2012 said:
Seems like you messed up and bricked your device try seeing if you can unlock your bootloader still if not contact whoever you got device off and report for warranty
Click to expand...
Click to collapse
NippleSauce said:
FYI, the bootloader is one of the functional recovery modes.
Click to expand...
Click to collapse
Beefheart said:
Try the online Google flash tool. This is what I used to flash back to stock after unrooting my device to run some tests. Although in my case, as you're meant to, I performed the flash prior to re-locking the bootloader, so it might not work for you.
Android Flash Tool
flash.android.com
Click to expand...
Click to collapse
unfortunately that was a no go for me as well... tells me I need to unlock to perform any of the functions
that said, any possibility the guys at Ubreakifix would be able to get this fixed?
dimm0k said:
unfortunately that was a no go for me as well... tells me I need to unlock to perform any of the functions
that said, any possibility the guys at Ubreakifix would be able to get this fixed?
Click to expand...
Click to collapse
Unlikely. This now needs a logic board swap I suspect. You can't unlock the bootloader as you toggled the OEM switch in developer options then relocked the bootloader before flashing stock, you can't boot to Android to untoggle that switch to allow another fastboot unlock command because you have a non-stock image installed with a locked bootloader, and you can't flash back to stock.
Sorry to say, your phone appears to be bricked.
Send it back for a warranty swap. The bootloader is listed as being locked, so unless they delve deeper, it's not obvious the end-user is at fault rather than the device simply refusing to boot one day for no apparent reason.
Beefheart said:
Send it back for a warranty swap. The bootloader is listed as being locked, so unless they delve deeper, it's not obvious the end-user is at fault rather than the device simply refusing to boot one day for no apparent reason.
Click to expand...
Click to collapse
should I try sending it back for a warranty swap or would sending it into Google for repairs not be a good idea?
Did you buy it direct from Google? If so that could be an issue, as they're likely going to try to diagnose the fault prior to sending out a replacement, and will discover it's caused by you before refusing a replacement. Where as if you bought it from some a third party vender, they will likely just swap it without any in depth checks.
Beefheart said:
Did you buy it direct from Google? If so that could be an issue, as they're likely going to try to diagnose the fault prior to sending out a replacement, and will discover it's caused by you before refusing a replacement. Where as if you bought it from some a third party vender, they will likely just swap it without any in depth checks.
Click to expand...
Click to collapse
I purchased this from Amazon when they had the $200 Amazon GC offer... they're allowing me to return the phone, but if I were to buy it again from them it would be at full price. for some reason they are not allowing exchanges/replacement. that said, I was exploring if it would be worth sending to Google for a repair... when you say they in the last sentence, are you referring to Google or the third party vendor?
dimm0k said:
I purchased this from Amazon when they had the $200 Amazon GC offer... they're allowing me to return the phone, but if I were to buy it again from them it would be at full price. for some reason they are not allowing exchanges/replacement. that said, I was exploring if it would be worth sending to Google for a repair... when you say they in the last sentence, are you referring to Google or the third party vendor?
Click to expand...
Click to collapse
That's their policy. I bought a Logitech MX Keys for £65 in a UK deal about 10 months ago. When it developed a fault, they offered me a full refund but point blank refused an exchange for a new keyboard, which annoyed me no end as it had gone up to £105 at that point. But it can work the other way around too and you can be the one with the money in your pocket. I've had that happen too.
Beefheart said:
That's their policy. I bought a Logitech MX Keys for £65 in a UK deal about 10 months ago. When it developed a fault, they offered me a full refund but point blank refused an exchange for a new keyboard, which annoyed me no end as it had gone up to £105 at that point. But it can work the other way around too and you can be the one with the money in your pocket. I've had that happen too.
Click to expand...
Click to collapse
damn, that is rather disappointing! that said and from your response, I guess it's better to go and return to Amazon then...
dimm0k said:
damn, that is rather disappointing! that said and from your response, I guess it's better to go and return to Amazon then...
Click to expand...
Click to collapse
The question is, can you use the GC when you purchase another phone?
schmeggy929 said:
The question is, can you use the GC when you purchase another phone?
Click to expand...
Click to collapse
unfortunately Amazon thought of abuse this way and priced it so that the device was $200 less from the get-go and charging $200 for the GC
Doesn’t matter what they say, if the device is in warranty, just write them that the device is damaged. They must replace it.