Hello all,
I purchased a nexus 6 several moons ago as a backup phone and when I tested it, my sim card was recognized and I was able to send and receive messages. Today I am planning to use it but I realized that it is in demo mode. I can use the phone without any issues but it drains the battery as it keeps playing a nexus ads every few seconds and the phone is unusable as of right now.
I enabled the Developer Options but when I try to enter Developer Options it says that the device is locked. I have access to fastboot but if I enter "fastboot oem unlock", I get the following:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote: '')
fastboot: error: Command failed
I thought that the bootloader was locked and I registered on the motorola website to get the unlock code but it appears that the bootloader is unlocked. If I issue "fastboot oem get_unlock_data", I get the following:
(bootloader) This command is not needed to unlock. Run fastboot oem
I also tried to flash the bootloader with "fastboot flash bootloader bootloader-shamu-moto-apq8084-71.10.img" and I get:
(bootloader) has-slot:bootloader: not found
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (3807 KB) OKAY [ 0.122s]
Writing 'bootloader' (bootloader) Unlock before flashing
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) unlock directly.
OKAY [ 0.002s]
Finished. Total time: 0.003s
Is there any thing that I can do to access the developer options?
Thank you.
pczsamqa said:
Hello all,
I purchased a nexus 6 several moons ago as a backup phone and when I tested it, my sim card was recognized and I was able to send and receive messages. Today I am planning to use it but I realized that it is in demo mode. I can use the phone without any issues but it drains the battery as it keeps playing a nexus ads every few seconds and the phone is unusable as of right now.
I enabled the Developer Options but when I try to enter Developer Options it says that the device is locked. I have access to fastboot but if I enter "fastboot oem unlock", I get the following:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote: '')
fastboot: error: Command failed
I thought that the bootloader was locked and I registered on the motorola website to get the unlock code but it appears that the bootloader is unlocked. If I issue "fastboot oem get_unlock_data", I get the following:
(bootloader) This command is not needed to unlock. Run fastboot oem
I also tried to flash the bootloader with "fastboot flash bootloader bootloader-shamu-moto-apq8084-71.10.img" and I get:
(bootloader) has-slot:bootloader: not found
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (3807 KB) OKAY [ 0.122s]
Writing 'bootloader' (bootloader) Unlock before flashing
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) unlock directly.
OKAY [ 0.002s]
Finished. Total time: 0.003s
Is there any thing that I can do to access the developer options?
Thank you.
Click to expand...
Click to collapse
Have you tried factory resetting the device to exit demo mode?
Edit:
Before factory resetting, make sure all Google accounts are removed. Otherwise FTP might get triggered.
Related
Hello. I have a dev edition One that was converted into a Google Edition, and now I'm trying to return back to sense. I have an RUU to install, but everytime I run the command "./fastboot oem rebootruu" I get the following:
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.011s]
finished. total time: 0.011s
Any help would be appreciated. It seems I can't mod anything with the phone until I get into RUU mode. Thanks.
dsass600 said:
Hello. I have a dev edition One that was converted into a Google Edition, and now I'm trying to return back to sense. I have an RUU to install, but everytime I run the command "./fastboot oem rebootruu" I get the following:
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.011s]
finished. total time: 0.011s
Any help would be appreciated. It seems I can't mod anything with the phone until I get into RUU mode. Thanks.
Click to expand...
Click to collapse
"fastboot oem rebootRUU"
I'm pretty sure it's case sensitive.
Sent from my HTC One using xda app-developers app
So, I was BROWSING REDDIT, and an app starts downloading in the background. Which somehow caused google play services to crash, along with everything running on my phone. Then bootloop. Completely unprompted. Still at a loss here.
My nexus 6 is unlocked, no custom kernel or xposed installed, just running AOSiP 3.3 android 6.0.1. havent flashed anything other than that, which i flashed more than a month ago.
So, my troubleshooting thus far.
./fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.002s
device still says UNLOCKED STATUS CODE 3
next i tried:
./fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (12004 KB)...
OKAY [ 0.378s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.382s
and lastly, I tried:
./fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (8196 KB)...
OKAY [ 0.259s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 0.264s
So, i'm kinda at a loss here. Recovery is failing to mount to storage, etc. Again, I was BROWSING REDDIT and this happened. I'd like to save my data at all costs. if anyone has any ideas, please, I am desperate. thank you.
Sorry but why open a new thread on the same issue? Did you think you would get a different answer than what you were getting in your original thread?
alryder said:
Sorry but why open a new thread on the same issue? Did you think you would get a different answer than what you were getting in your original thread?
Click to expand...
Click to collapse
to condense, summarize and make clear what i have already tried, and to seek further troubleshooting to my issue. there must be someone with an idea of how to fix this. if not, does it really hurt the forum? i am a person with a problem, seeking advice.
While I agree it's good to summarize the issue and layout what you've tried to resolve it, it could have been done as a post in your original thread to avoid the clutter of having two threads about the same issue. I also think you got the correct answer in the original thread that, however it happened, your bootloader has somehow became locked and in all likelihood the device is beyond repair. Sorry to say so but that's the way I see it.
alryder said:
While I agree it's good to summarize the issue and layout what you've tried to resolve it, it could have been done as a post in your original thread to avoid the clutter of having two threads about the same issue. I also think you got the correct answer in the original thread that, however it happened, your bootloader has somehow became locked and in all likelihood the device is beyond repair. Sorry to say so but that's the way I see it.
Click to expand...
Click to collapse
how is that even possible?
I'm super curious on what downloaded in the background...
Sent from my Nexus 6 using Tapatalk
MrBlob69 said:
I'm super curious on what downloaded in the background...
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
automatic update of some sort. it crashed my phone as soon as it was finished updating. didnt know a background app update could relock my bootloader and brick my phone. not sure why some are suggesting the bootloader is locked when it still displays status code 3 device is unlocked.
Post a screenshot of the bootloader screen
Sent from my Nexus 6 using XDA Free mobile app
The only thing that I can think of is you could try formatting /system and /boot separately and then try again flashing the system and boot images???
Sent from my Nexus 6 using Tapatalk
MrBlob69 said:
The only thing that I can think of is you could try formatting /system and /boot separately and then try again flashing the system and boot images???
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
This won't work as if the bootloader is locked, you cannot wipe/flash img files to the phone.
To answer your question OP, we can't tell you how this happened, or what the download was that happened in the background, we simply weren't there and don't know what you have installed to your phone. This line indicates that "Allow OEM Unlocking" is not enabled in Developer Options:
Code:
(bootloader) [B]Check 'Allow OEM Unlock' in Developer Options.[/B]
FAILED (remote failure)
finished. total time: 0.002s
With that not enabled, you cannot issue:
Code:
fastboot oem unlock
You also cannot flash factory images to the device, or wipe the device either. I'm afraid that this device is bricked since it appears your bootloader is locked.
scottshebs said:
So, I was BROWSING REDDIT, and an app starts downloading in the background. Which somehow caused google play services to crash, along with everything running on my phone. Then bootloop. Completely unprompted. Still at a loss here.
My nexus 6 is unlocked, no custom kernel or xposed installed, just running AOSiP 3.3 android 6.0.1. havent flashed anything other than that, which i flashed more than a month ago.
So, my troubleshooting thus far.
./fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.002s
device still says UNLOCKED STATUS CODE 3
next i tried:
./fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (12004 KB)...
OKAY [ 0.378s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.382s
and lastly, I tried:
./fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (8196 KB)...
OKAY [ 0.259s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 0.264s
So, i'm kinda at a loss here. Recovery is failing to mount to storage, etc. Again, I was BROWSING REDDIT and this happened. I'd like to save my data at all costs. if anyone has any ideas, please, I am desperate. thank you.
Click to expand...
Click to collapse
i guess all the time i devoted to you yesterday means absolutely nothing to you, and you learned nothing.. thanks
RMarkwald said:
This won't work as if the bootloader is locked, you cannot wipe/flash img files to the phone.
To answer your question OP, we can't tell you how this happened, or what the download was that happened in the background, we simply weren't there and don't know what you have installed to your phone. This line indicates that "Allow OEM Unlocking" is not enabled in Developer Options:
Code:
(bootloader) [B]Check 'Allow OEM Unlock' in Developer Options.[/B]
FAILED (remote failure)
finished. total time: 0.002s
With that not enabled, you cannot issue:
Code:
fastboot oem unlock
You also cannot flash factory images to the device, or wipe the device either. I'm afraid that this device is bricked since it appears your bootloader is locked.
Click to expand...
Click to collapse
forgive me, but how can the phones bootloader lock itself? this is the fastboot screen still saying code 3 unlocked. sorry if i am stubborn, just refusing to believe my 300 dollar device bricked itsself while i literally did nothing. never seen anything like this.
31ken31 said:
Post a screenshot of the bootloader screen
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
just posted, still status code 3.
Thread closed.
Not sure why the OP started 2 similar threads (like THIS) and ignored the help provided already....
Hello,
My Huawei P10 will not start up. Can boot into fastboot no problems, this is what comes out.
Android reboot reason:
coldboot
NA
volumnkey_down_press_process_func
Tried to flash a recovery into phone to boot upin recovery, however it comes with this error.
fastboot flash recovery twrp_p10_0.1.img
target reported max download size of 471859200 bytes
sending 'recovery' (24954 KB)...
OKAY [ 0.532s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.539s
When charging the Electric symbol appears with a circle around it and it is in red. Randomly when charging it will turn on by itself and get frozen on the Huawei logo. But it will not turn on at all when not plugged into mains. Trying to turn on when it is plugged in mains only displays charging logo.
Not entirely sure if that is the correct recovery that I should be using, quick google search has given me that result. Would it be possible to flash a stock ROM?
suenoromis said:
Hello,
My Huawei P10 will not start up. Can boot into fastboot no problems, this is what comes out.
Android reboot reason:
coldboot
NA
volumnkey_down_press_process_func
Tried to flash a recovery into phone to boot upin recovery, however it comes with this error.
fastboot flash recovery twrp_p10_0.1.img
target reported max download size of 471859200 bytes
sending 'recovery' (24954 KB)...
OKAY [ 0.532s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.539s
When charging the Electric symbol appears with a circle around it and it is in red. Randomly when charging it will turn on by itself and get frozen on the Huawei logo. But it will not turn on at all when not plugged into mains. Trying to turn on when it is plugged in mains only displays charging logo.
Not entirely sure if that is the correct recovery that I should be using, quick google search has given me that result. Would it be possible to flash a stock ROM?
Click to expand...
Click to collapse
Bootloader and FRP unlocked (both red on Fastboot screen)?
Test in Fastboot (first command below):
Code:
fastboot oem get-bootinfo
PAUSE
fastboot oem get-product-model
PAUSE
fastboot getvar vendorcountry
PAUSE
fastboot oem get-build-number
PAUSE
fastboot oem oeminforead-SYSTEM_VERSION
PAUSE
Try booting to eRecovery (connect to charger, keep pressing Vol+, then Pow) and Install latest firmware and recovery
zgfg said:
Bootloader and FRP unlocked (both red on Fastboot screen)?
Test in Fastboot (first command below):
Code:
fastboot oem get-bootinfo
PAUSE
fastboot oem get-product-model
PAUSE
fastboot getvar vendorcountry
PAUSE
fastboot oem get-build-number
PAUSE
fastboot oem oeminforead-SYSTEM_VERSION
PAUSE
Try booting to eRecovery (connect to charger, keep pressing Vol+, then Pow) and Install latest firmware and recovery
Click to expand...
Click to collapse
PHONE Locked
FRP Lock
Code:
C:\adb>fastboot oem get-bootinfo
...
(bootloader) locked
OKAY [ 0.001s]
finished. total time: 0.001s
C:\adb>fastboot oem get-product-model
...
(bootloader) VTR-L09
OKAY [ 0.005s]
finished. total time: 0.006s
C:\adb>fastboot getvar vendorcountry
vendorcountry: ee/gb
finished. total time: 0.006s
C:\adb>fastboot oem get-build-number
...
(bootloader) :NRD90M test-keys
OKAY [ 0.005s]
finished. total time: 0.005s
C:\adb>fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :VTR-L09C652B101
OKAY [ 0.007s]
finished. total time: 0.007s
That is what I get when running your code
Edit: Doing VolUp + Power key with charger does nothing. restarts the charging logo.
charging logo loops when charger is plugged in and doing nothing. Shows charging logo, led notification flashes red 3 times and turns off, turns on again with charging logo, red led flashes 3 times, turns off...
suenoromis said:
PHONE Locked
FRP Lock
Code:
C:\adb>fastboot oem get-bootinfo
(bootloader) locked
OKAY [ 0.001s]
finished. total time: 0.001s
...
Click to expand...
Click to collapse
So Bootloader (and FRP=OEM) locked, you are not allowed to flash anything ;(
zgfg said:
So Bootloader (and FRP=OEM) locked, you are not allowed to flash anything ;(
Click to expand...
Click to collapse
Phone = Dead
?
suenoromis said:
Phone = Dead
?
Click to expand...
Click to collapse
You can try flashing by Testpoints - need to open cover and short-wire the pins.
Never played with, here is some guide for P10
https://forum.xda-developers.com/mate-9/help/solution-19-00-fix-hardbricked-huawei-t3750315
You can also ask for paid help from (discuss before you buy credits):
https://ministryofsolutions.com/paid-services/amp
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
https://chimeratool.com/
https://funkyhuawei.club/
Hello guys.
So, I recently bought a new phone and thought "let's try rooting my old one" and tried it on my G7+. I ended up not liking out it turned out (Netflix DRM, Vanced didn't work properly, etc).
So I reflashed the stock ROM and put the comand fastboot oem lock.
The thing is, after I boot the device again, all the messages still appear, like Your device has loaded a different operating system" and below that "ID: " (blank) and I also get "Verity mode is set to disable".
The thing is, every tutorial I come across to relock the bootloader(regular G7, G7 Power, G6, etc), says that when you enter the command "fastboot oem lock" two times, the message that you should only flash signed images, does not appear. I instantly get the state flashing_locked, and I can't continue flashing the stock firmware like every other tutorial shows.
In short, once you enter the command "fastboot oem lock", it's locked for good, and you can't do anything unless you unlock it again, starting the whole process again.
The problem is, even with the bootloader locked again, my device still shows as "insecure", Netflix is nowhere to be found on the app store, and the state of my device is not certified.
I wouldn't have unlocked If I knew it was going to be this difficult to get it back. Selling it now would be next to impossible.
Here are some examples of the errors I'm getting:
C:\ProgramData\LMSA\Download\RomFiles\LAKE_QPWS30.61_21_18_7_subsidy_DEFAULT_regulatory_XT1965_2_SUTEL_DS_CFC.xml>fastboot oem lock
...
(bootloader) ***************************************
(bootloader) WARNING: This command erases user data!
(bootloader) Please re-run this command to confirm.
(bootloader) ***************************************
OKAY [ 0.022s]
finished. total time: 0.024s
C:\ProgramData\LMSA\Download\RomFiles\LAKE_QPWS30.61_21_18_7_subsidy_DEFAULT_regulatory_XT1965_2_SUTEL_DS_CFC.xml>fastboot oem lock
...
(bootloader) Bootloader is now locked
OKAY [ 0.045s]
finished. total time: 0.046s
C:\ProgramData\LMSA\Download\RomFiles\LAKE_QPWS30.61_21_18_7_subsidy_DEFAULT_regulatory_XT1965_2_SUTEL_DS_CFC.xml>fastboot oem lock
...
(bootloader) Already locked
OKAY [ 0.012s]
finished. total time: 0.014s
C:\ProgramData\LMSA\Download\RomFiles\LAKE_QPWS30.61_21_18_7_subsidy_DEFAULT_regulatory_XT1965_2_SUTEL_DS_CFC.xml>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (23537 KB)...
OKAY [ 0.618s]
writing 'boot_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.678s
Click to expand...
Click to collapse
Does anyone know how to fix this?
Did you ever get this sorted ? I have the same problem on my G7 Plus. I unlocked, then loaded Lineagos, but then decided to go back to stock, I used LMSA to rescue the phone, but still got the warning and boot time "Your phone has loaded a different OS" and I can't use GPay. I tried the fastboot OEM lock (worked) and fastboot flashing lock, but I still get the warning and I can't use GPay.
I think in my case the LMSA rescue didn't work because I was originally on Android 9 and the rescue took me straing to Android 10
Elrom said:
Hello guys.
So, I recently bought a new phone and thought "let's try rooting my old one" and tried it on my G7+. I ended up not liking out it turned out (Netflix DRM, Vanced didn't work properly, etc).
So I reflashed the stock ROM and put the comand fastboot oem lock.
The thing is, after I boot the device again, all the messages still appear, like Your device has loaded a different operating system" and below that "ID: " (blank) and I also get "Verity mode is set to disable".
The thing is, every tutorial I come across to relock the bootloader(regular G7, G7 Power, G6, etc), says that when you enter the command "fastboot oem lock" two times, the message that you should only flash signed images, does not appear. I instantly get the state flashing_locked, and I can't continue flashing the stock firmware like every other tutorial shows.
In short, once you enter the command "fastboot oem lock", it's locked for good, and you can't do anything unless you unlock it again, starting the whole process again.
The problem is, even with the bootloader locked again, my device still shows as "insecure", Netflix is nowhere to be found on the app store, and the state of my device is not certified.
I wouldn't have unlocked If I knew it was going to be this difficult to get it back. Selling it now would be next to impossible.
Here are some examples of the errors I'm getting:
Does anyone know how to fix this?
Click to expand...
Click to collapse
You can try downloading each versions from your region (RETUS, RETEU, etc) and retry the relock process until you find the correction version.
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Hi, I'm pretty sure I know the answer is I'm out of luck but hoping for some tips if anyone has them. My Moto X4 XT1900-1 AndroidOne phone bricked itself. It was complaining about not having a SIM card, so I shutdown the phone to clean the SIM card, and when it rebooted I got the "your device is corrupted and can not be trusted" screen of death. This phone is not unlocked and I've tried to unlock it with no luck. I also tried using the Motorola Rescue and Smart Assistant tool, which fails while flashing the bootloader. These are the commands I've tried from fastboot:
fastboot oem unlock:
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.001s]
Finished. Total time: 0.001s
fastboot oem get_unlock_data:
(bootloader) Failed to get unlock data.
OKAY [ 0.002s]
Finished. Total time: 0.002s
fastboot flashing unlock:
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.001s]
Finished. Total time: 0.001s
fastboot flashing unlock_critical:
(bootloader) Not supported command
OKAY [ 0.000s]
Finished. Total time: 0.000s
Any suggestions would be awesome.