Related
didn't enable developer options on this phone seeing that I was primarily going to use this phone as my daily driver so I carried on using the phone as is. the next day my phone show me an error, it said "Your device is corrupt. It can't be trusted and may not work properly." (Red) and I proceeded to link it showed me to see what the problem might be.
A few minuets after it showed me that error my phone shut down and couldn't turn on. I tried everything to reboot it but to no success, I was able boot it in fastboot mode and downloaded all the appropriate tools to do a flash install of a factory default image,I got the default operating system that the phone came with, as well as adb-tools required to perform a system wide flash seeing as i didn't have that much data on it.
Once everything was set, I followed the step by step instructions that google provided me on the restore to factory setting pages "https://developers.google.com/android/nexus/images". Seeing as I didn't enable developer options when my phone was working, I run into a prerequisite that needed that before I could flash my device.
While running the commands in cmd as an administrator, I run the command -
fastboot flashing unlock command and the console responded with -
FAILED (remote: oem unlock is not allowed)
I went back and reread this step, which was step number 4, It indicated "If necessary, unlock the device's
bootloader by running" the command. so i figured maybe it isn't really necessary, I proceeded to run the flash-all.bat
script, and it FAILED at every step saying -
FAILED (remote: device is locked. Cannot flash) //corresponding .img file//
It failed to flash my nexus 5x at every stage. So I did some research and found out that the problem was
that in the fastboot menu, the Device state was locked in a very assuring green color, and every where I
searched it indicated that this option to unlock the device was in the developer settings in the phones
OS, which is rather odd to put such a feature in the phones OS and fail to include the option in the fastboot menu. I
couldn't find any tool or assistance change the status of the device state to unlocked.
Now my question is, how can I change the device state to unlocked without enabling this options prior in the OS seeing
as i cant do that because my phone isn't coming on at all. any assistance or help would be highly appreciated.
Point of clarification, I have tried everything in accordance to what google nexus support pages have showed
me to the letter.
You can't enable OEM unlock by fastboot/recovery.
But there's another way to rescue your phone.
So
Can you boot into recovery? (Bootloader mode switch to recovery mode using volume keys and press power to choose it)
If it started and you would see an Android with an red triangle press power and hit volume+ to turn on menu. If it works you are safe.
Then download OTA image from Android developers page (OTA, not factory), launch command line (I don't know how it works on Windows, I've never flashed anything on Windows )
And you will need to flash this OTA image by executing adb sideload nameofpackage.zip
Remember to choose adb sideload in recovery first and then executing a command. It should flash and your phone should work.
Good luck!
Wysłane z mojego Nexus 5X przy użyciu Tapatalka
I cant boot in recovery mode... When I tried to boot in recovery stuck in google logo then power off...
Oh that's not good.
Do you have warranty on your phone?
The last thing I keep in mind is flashing using LG tool, but I might take a look on it because I don't know how to use it.
Wysłane z mojego Nexus 5X przy użyciu Tapatalka
No not in warranty....
I contact in LG service center they said chage the motherboard and cost around 170$
That amount so big??
Is there any method to unlock in this case from fastboot?
I need to unlock for custom kernel to flash.
Im on bootloop and oem locked in the system (befor got bootloop)
Help
Domin_PL said:
Oh that's not good.
Do you have warranty on your phone?
The last thing I keep in mind is flashing using LG tool, but I might take a look on it because I don't know how to use it.
Wysłane z mojego Nexus 5X przy użyciu Tapatalka
Click to expand...
Click to collapse
try to >>>Nexus Root Toolkit<<<
Do you your computer can see phone
There where some hidden fastboot commands on XDA. Maybe you can try some of them to see if they can go around this limitation.
Sent from my Nexus 5X using Tapatalk
akins0405 said:
try to >>>Nexus Root Toolkit<<<
Do you your computer can see phone
Click to expand...
Click to collapse
I have the same issue mentioned above. Downloaded Nexus Root Toolkit and i have tried unlock through Nexus Root Toolkit. It seems failure. Because, After detecting my device it reboots and my phone reboots and shows the google logo and reboot again and again... My phone will not boot into recovery mode. While we click on it, it shows google logo and reboots again and again... Is there any solution for this?
OMG!!!
I Have the exact same issue with my bq aquaris x5
I really wish someone would find a solution for this
Seems options are very limited now
Having exact same issue with Huawei Y3. After spending the whole day, came to the conclusion that there is now only two options left: a) Replace the motherboard. b) pay £15 at dc unlock website to unlock oem. Not decided which one should i go for..
I got the same issue.
Nexus 5X has no activated "Allow OEM Unlock".
I tried with the Nexus Root Toolkit.
When I try to unlock Bootloader or the option "Fix Bootloop" he wants me to put the phone into Fastboot.
When I put phone into Fastboot he recognizes it and then restarts the phone. From now on nothing more happens, because noe the bootloop is "active" again.
Recovery Mode is not working, too.
Before I can access it, bootloop starts.
Sound as the same issue as @tomsonmathewv has.
Can someone help me?
EDIT:
While I tried some other solutions my Nexus 5X booted and booted.
And suddenly it booted one time to the Pattern screen. I entered the pattern and waited again for the bootloop after google animation.
But then the google animation finished and a short black screen with s small blue line in the middle of the display appeared. Looked like a "graphics error". But then immediately the normal phone idle screen appeared. The phone started!
I immediately went to the DEV-Options and Allowed OEM-unlock. And I took screenshots of the current configuration.
The current Android is 8.1
Is it recommended to flash an older version of Android to prevent a new Bootloop?
I had the same issue after the latest Android update on my Nexus 5X.
Have you left the device in charge before it manage to start?
Thanks
EDIT: Solved leaving it unplugged.
Hey buddy try Nexus Root Toolkit v2.1.9 it will unlock your bootloader without turning your phone on it worked for me.
aadeekhan79 said:
Hey buddy try Nexus Root Toolkit v2.1.9 it will unlock your bootloader without turning your phone on it worked for me.
Click to expand...
Click to collapse
NRT isn't going to work unless you previously allowed for oem unlock in developer options. If you haven't done that and you can't boot into recovery or the system you're kind of sol.
Sent from my [device_name] using XDA-Developers Legacy app
Shuhan44 said:
Having exact same issue with Huawei Y3. After spending the whole day, came to the conclusion that there is now only two options left: a) Replace the motherboard. b) pay £15 at dc unlock website to unlock oem. Not decided which one should i go for..
Click to expand...
Click to collapse
does that software (dc unlocker) actualy works? i've got the same issue with honor 8 pro, which opt. you have selected.
In my case before my N5X started bootlooping I allowed OEM unlock but didn't enabled USB Debugging Mode in Developer options. Is there a way to unlock bootloader with USB Debugging Mode disabled? I want to try the UNBLOD tool, but unlocked bootloader is a requirement.
xrehpicx said:
OMG!!!
I Have the exact same issue with my bq aquaris x5
I really wish someone would find a solution for this
Click to expand...
Click to collapse
Hi
I also need help of a slightly different nature. I'm somehow locked out of my Huawei P10 whereby my unlock pattern is no longer recognized. USB debugging is not enabled. What are my option as i really do not want to factory reset the phone, did not backup data. Coincidentally enough, this occurred after the latest software update. Please can someone help me.
Thanks
Thanks
Roshan0746 said:
didn't enable developer options on this phone seeing that I was primarily going to use this phone as my daily driver so I carried on using the phone as is. the next day my phone show me an error, it said "Your device is corrupt. It can't be trusted and may not work properly." (Red) and I proceeded to link it showed me to see what the problem might be.
A few minuets after it showed me that error my phone shut down and couldn't turn on. I tried everything to reboot it but to no success, I was able boot it in fastboot mode and downloaded all the appropriate tools to do a flash install of a factory default image,I got the default operating system that the phone came with, as well as adb-tools required to perform a system wide flash seeing as i didn't have that much data on it.
Once everything was set, I followed the step by step instructions that google provided me on the restore to factory setting pages "https://developers.google.com/android/nexus/images". Seeing as I didn't enable developer options when my phone was working, I run into a prerequisite that needed that before I could flash my device.
While running the commands in cmd as an administrator, I run the command -
fastboot flashing unlock command and the console responded with -
FAILED (remote: oem unlock is not allowed)
I went back and reread this step, which was step number 4, It indicated "If necessary, unlock the device's
bootloader by running" the command. so i figured maybe it isn't really necessary, I proceeded to run the flash-all.bat
script, and it FAILED at every step saying -
FAILED (remote: device is locked. Cannot flash) //corresponding .img file//
It failed to flash my nexus 5x at every stage. So I did some research and found out that the problem was
that in the fastboot menu, the Device state was locked in a very assuring green color, and every where I
searched it indicated that this option to unlock the device was in the developer settings in the phones
OS, which is rather odd to put such a feature in the phones OS and fail to include the option in the fastboot menu. I
couldn't find any tool or assistance change the status of the device state to unlocked.
Now my question is, how can I change the device state to unlocked without enabling this options prior in the OS seeing
as i cant do that because my phone isn't coming on at all. any assistance or help would be highly appreciated.
Point of clarification, I have tried everything in accordance to what google nexus support pages have showed
me to the letter.
Click to expand...
Click to collapse
Every phone have boot. Img system . I also have a same fault redmi k20 pro. But i succeed to give rebirth it. Try to using fastboot commands only and flash fastboot flash boot boot. Img it will work definitely
Hi, i'm a user from France.
After installing the last Android version proposed by Mi on the 7th of June 2019 my phone is now stucked on the black screen with the red mention " this miui version can't be installed on this device " - I made the choice to wipe all the data - after restarting nothing changed and I'm stucked to the same black screen.
First big loss. I didn't do any thing solo, I've just being installing the official update proposed by the company like I always do when notification comes. I don't do extra stuff that I have no knowledge about, I'm a regular user.
Now I'm trying to wipe the data through my computer using XiaomiFlash, however I'm getting this error alert : Flash antirbpass error.
What does it mean ? I have read about Google protection briefly on the internet but now it's getting really complicated for me to swim in these waters,
none of the solution worked for me, from the ADB thing to the CMD thing - I also downloaded a "dummy" file which I don't know how to use. After installing ADB I don't get any file of that name in my ":c" repertory and when typing the command "fastboot etc" in CMD it says that it's not recognized. I don't know what I'm doing and I don't know what to do, I don't have a car to get to the nearest phone repair shop and it's like i'm in an alien world with all the technical vocabulary in front of me when search the solution online.
All help would be really appreciated for an ignorant beginner like me.
1.Connect phone to PC, backup important data.
2.Reboot phone to bootloader(fastboot,Power+Volume Down).
Goto PC CMD
fastboot flash antirbpass dummy.img
fastboot flash recovery twrp-3.3.1-0-whyred.img
3.Reboot to TWRP (Power+Volume UP).
Wipe DalvikCache, Cache, Data, Internalstorage, System, Vendor.
Install miui_HMNote5Global_V10.3.1.0.PEIMIXM_d4d2c9f2aa_9.0.zip.
Wipe Cache, Data and do Factory reset.
4.Reboot to system.
Just try abovementioned steps, good luck!
Thanks garyemail for your help.
I'm halfway done with this problem, but another thing came on the way which is :
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.3.1-0-whyred.img
target reported max download size of 536870912 bytes
sending 'recovery' (38924 KB)...
OKAY [ 0.937s]
writing 'recovery'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.942s
Apparently my phone is locked after being checked :
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.012s]
finished. total time: 0.014s
I know there is no way for unlocking it through "official" method by using whatever Xiaomi is throwing away, do you have a particular way to get that unlocked ?
I know Xiaomi and Google would scream out of hysteria by reading this post but I'm not trying to unlock my phone for the pure sake of adrenaline.
They putted out that Android Update, not me. It didn't work. Rather it blocked my phone.
Now that the only way to solve the problem is to unlock the phone, what do you know, they decide to put a lock on the phone that basically doesn't allow the user to officially and directly restore the phone.
What is wrong with these people ? Are we just supposed to throw the phone away and buy a new one whenever they are making an uncorrect move resulting in a broken phone ?
I learned now what I'm paying when adding a high price difference for an iPhone, I'm paying for avoiding all that torture which Google and Xiaomi together are dragging me into.
Buy a 1€ phone and spend 1000€ worth of time in searching the remedee in case of a problem. -> Android logic -> money saved at first look, whatever happen you are entirely on your own. A small rock hiding a mountain.
Buy a 1000€ phone and spend 1€ worth of time in searching for the remedee to the sickness. -> Apple logic -> expensive at first look, but client satisfaction guaranteed - time and energy saved.
First of all, you bought a non official phone, that mean you bought your phone out of your region. May your phone is from china and it supposed using china rom. But your phone a china version and using global rom but that not wrong, when that happen unlocked bloatloader is needed. the only problem is, when the global version installed, you or the guy that sold the phone to you, lock the boatloader so it seems look like a global phone version but actually its the china one and that forbidden by xiaomi itself, and they have announced a year ago on the miui forum. The only one solution is to unlock the bloatloader ones again. I hope you understand what i wrote and sorry for bad english
Wiguna77 said:
First of all, you bought a non official phone, that mean you bought your phone out of your region. May your phone is from china and it supposed using china rom. But your phone a china version and using global rom but that not wrong, when that happen unlocked bloatloader is needed. the only problem is, when the global version installed, you or the guy that sold the phone to you, lock the boatloader so it seems look like a global phone version but actually its the china one and that forbidden by xiaomi itself, and they have announced a year ago on the miui forum. The only one solution is to unlock the bloatloader ones again. I hope you understand what i wrote and sorry for bad english
Click to expand...
Click to collapse
Hey thanks Wiguna for your help, greatly appreciated. I'm facing now a new and big problem. The "unlock" button on the Mi Flash Unlock is greyed, apparently it's because my phone being locked, but the only way to unlock my phone is through Mi Unlock and they are blocking me the access to unlock my phone. Do you have any way to unlock the phone through a non-xiaomi way ?
I don't know why they would prevent their users for unlocking their phone, is it this illegal ?
RebornSAGA said:
Hey thanks Wiguna for your help, greatly appreciated. I'm facing now a new and big problem. The "unlock" button on the Mi Flash Unlock is greyed, apparently it's because my phone being locked, but the only way to unlock my phone is through Mi Unlock and they are blocking me the access to unlock my phone. Do you have any way to unlock the phone through a non-xiaomi way ?
I don't know why they would prevent their users for unlocking their phone, is it this illegal ?
Click to expand...
Click to collapse
There is no "non-xiaomi way" you have to flash the chinese official rom with miflash and then unlock your phone, thats the only way.
btw you can try the "EDL-Method".
Thanks Gerr1 and thanks anyone else who helped. Really appreciated.
[How To] Unlock Bootloader on Your Redmi Note 5 Pro
Try abovementioned link!...
First unlock your phone bootloader, then do the #2 setps again!...
Hi
Whenever, Irey to turn on the device, it freezes in the mi logo and can only access the FASTBOOOT. I tried to flash the device but ut says "Flashing is not allowed in Locking State" Also, I treid unnlocking the phone through the mi Unlock software but once it says "You've exceeded the number of verification attempts allowed within 24 hours" and I can login twice in a day to that aoftware it seems. Also, I tried to unblock the device through CMD but it says failed. Please Help. Its hard to work without a phone
Please help
My Nexus 7 2013 tablet got stuck in a bootloop and I had to so a wipe from recovery. I had a lot of videos and photos that I had not backed up. Looking around for software and most of the pc stuff requires you to mount as mass storage. I remember awhile back that you couldn't do this with the Nexus 7 but wanted to see if that has changed now thats its 2020.
Otherwise does anyone know any other software to give a try.
cloves said:
My Nexus 7 2013 tablet got stuck in a bootloop and I had to so a wipe from recovery. I had a lot of videos and photos that I had not backed up. Looking around for software and most of the pc stuff requires you to mount as mass storage. I remember awhile back that you couldn't do this with the Nexus 7 but wanted to see if that has changed now thats its 2020.
Otherwise does anyone know any other software to give a try.
Click to expand...
Click to collapse
Nothing has changed in 2020, mass storage is gone for good, for several years in fact, forget about it, it is simply impossible anymore. For licensing reasons, MS had been replaced with MTP long time ago. Just boot TWRP and regardless of your bootloop situation you can recover your stuff via MTP, what's the problem? Have you wiped also the 'userdata' partition? If so, there is no recovery method, as the EXTx FS is not really recovery/undelete-friendly.
If your N7 is locked and without TWRP, there is almost no chance to recover anything. I say 'almost' because there is an extremely difficult software method of unlocking it while preserving userdata, or using JTAG, or reading the eMMC chip in an external memory reader. So yeah it is doable but is your data worth the effort?
k23m said:
Nothing has changed in 2020, mass storage is gone for good, for several years in fact, forget about it, it is simply impossible anymore. For licensing reasons, MS had been replaced with MTP long time ago. Just boot TWRP and regardless of your bootloop situation you can recover your stuff via MTP, what's the problem? Have you wiped also the 'userdata' partition? If so, there is no recovery method, as the EXTx FS is not really recovery/undelete-friendly.
If your N7 is locked and without TWRP, there is almost no chance to recover anything. I say 'almost' because there is an extremely difficult software method of unlocking it while preserving userdata, or using JTAG, or reading the eMMC chip in an external memory reader. So yeah it is doable but is your data worth the effort?
Click to expand...
Click to collapse
Thanks for shedding light on this for me k23m! Till this date I was still running stock 6.0.1 and no twrp recovery. After hard resetting the tablet via stock recovery I was able to reboot into the IOS. I think the problem stemmed from me trying to remove the google search bar and then rebooting. I then went ahead and used Nexus Root Toolkit v2.1.9 and now I am unlocked, rooted, and have twrp running.
Thinking in PC terms, since the wipe data/factory reset was performed so quickly I was thinking most of the photos and vids should still be there and some sort of pc software would work. But without the mass storage feature show none of them are able to scan the tablet like a hard drive.
Based on what I mentioned above, would the second method you mentioned even work now that the phone is unlocked?
cloves said:
Thanks for shedding light on this for me k23m! Till this date I was still running stock 6.0.1 and no twrp recovery. After hard resetting the tablet via stock recovery I was able to reboot into the IOS. I think the problem stemmed from me trying to remove the google search bar and then rebooting. I then went ahead and used Nexus Root Toolkit v2.1.9 and now I am unlocked, rooted, and have twrp running.
Thinking in PC terms, since the wipe data/factory reset was performed so quickly I was thinking most of the photos and vids should still be there and some sort of pc software would work. But without the mass storage feature show none of them are able to scan the tablet like a hard drive.
Based on what I mentioned above, would the second method you mentioned even work now that the phone is unlocked?
Click to expand...
Click to collapse
Ah, the google search bar! It made my N7 bootlooping too. While I no longer use 6.0.1, I made a script for it to remove most of google apps. Safe removal of google search bar can be done with a modified script.
As for your data, it is truly gone. Note what happens during unlocking...
Code:
fastboot oem unlock
...
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) Unlocking bootloader done!
OKAY [ 48.203s]
finished. total time: 48.203s
48 seconds is not so quick actually. In "PC terms" formatting may be quick and data is still there indeed, however the bootloader relies on hardware erase+trim command. Here is a more detailed log from UART which I made a while ago:
Code:
[301620] fastboot: getvar:partition-type:userdata
[301620] fastboot: erase:userdata
[301630] card supports trim operation! use trim to erase card
[301630] add dummy read before trim on Hynix card
[317600] ERASE SUCCESSFULLY COMPLETED
Note "use trim to erase" - so called SD ERASE CMD38 command is sent to the eMMC hardware controller to erase many write blocks simultaneously in order to enhance the data throughput and they are completely zeroed-out in the process. If you don't believe me then check my old post on the subject. How else would I be able to squeeze 32GB into a 20MB archive file if there was recoverable data after erase? Incidentally, you can grab that p0.zip and get your own data copy for inspection on a PC, no need for mass storage.
Hello, I would like your help with my problem, I have a Xiaomi Redmi Note5, I was using it normally, I put it on the sofa and 10min later I see that thescreen is black and the buttons are not responding. So I decide to press the power button and the Mi logo appears, except that it ends there. The phone no longer boots on Android.
What I want above all is to recover my data, mainly my photos. (No I haven't activated the google cloud, I checked and there is nothing)
I think the problem is related to the storage of the phone which has saturated, for 2 3 days I had a message that there was less than 1.5G of storage left. My guess is that the storage has reached 100% and so the phone is bricked .. But that's just a guess.
I've read a lot to find a solution, but I don't have developer mode enabled or OEM unlock. I managed to use the fastboot mode and display the line with the phone id through the command: fastboot devices
On the other hand it is locked so impossible to use ADB, to my knowledge.
The recovery mode (volume up + power) does not seem to work, because nothing is happening.
I tried to load TWRP:
C:\adbfastboot flash recovery "twrp.img"
targetreported max download size of 536870912 bytes
sending'recovery' (42456 KB)...
OKAY [ 1.102s]
writing'recovery'...
FAILED(remote: Flashing is not allowed in Lock State)
I tried to unlock OEM :
C:\adbfastbootoem unlock
FAILED remote:Token Verify Failed, Reboot the device)
I also thought about emptying the cache in case it is the storage problem:
C:\adbfastbooterase cache
********Did you mean to fastboot format this ext4 partition?
erasing'cache'...
FAILED(remote: Erase is not allowed in Lock State)
Others infos:
C:\adbfastbootoem device-info
(bootloader)Verity mode: true
(bootloader)Device unlocked: false
(bootloader)Device critical unlocked: false
(bootloader)Charger screen enabled: false
I saw that there is an EDL technique by creating a contact (test point) in the phone, and I am ready to try that, I have already removed the back cover,but I did not find any info on how to use it to retrieve my data, only for fashing and wiping all the config… but that's really not what I want. If you know a technique allowing me to recover my data, I'd be glad.
Thanks for your help
Hi guys !
I've just get back my Motorola Z2 play i borrow to one of my friend, but after many trials it seems to be a bit of broken (talk about it below), and after seeking a lot of thread on internet, i feel blocked and i need any advice or help.
Here's the original situation :
- The bootloader has been unlocked in the following way (with fastboot oem get_unlock_data method, then retrieve the key from motorola website)
then, AICP 16.1 has been flashed.
- Everything worked fine except bluetooth can't be used anymore, it can't be activated anymore i didn't know why. (i get back the phone at this step)
- As i appreciate using bluetooth, i tried to upgrade AICP, flash it again and wipe cache/data to check if bluetooth become available again but it never happened.
So i tried to flash the official Motorola ROM and my issues started...
After flashing with this official ROM from Motorola (ALBUS_OPSS27.76_12_25_23_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC), phone worked well but i wasn't impossible to use any Google services (if i opened play store it says : "Impossible Connection, an issue has happened while trying to connect to google servers" every time, same error if i wanted to check updates and so on...)
I saw a post on internet that say to relock the bootloader to get the phone fully encrypted and to be trusted from google servers, so i did it using fastboot oem lock. (this is a huge mistake...i know...)
It didn't change anything and google services raise the same error, but now i'm unable to flash any other rom or anything... moreover, OEM unlocked tick on the phone menu is greyed out, i tried to let it connected to internet for ~10days but it doesn't change anything.
When i tried to unlock bootloader again to allow me to flash another rom (i wanted to try lineage os), i got those error :
Code:
fastboot oem unlock "CODE_FROM_MOTOROLA"
(bootloader) invalid boot state
OKAY [ 0.007s]
Finished. Total time: 0.010s
but also
Code:
fastboot flashing unlock
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options.
OKAY [ 0.009s]
Finished. Total time: 0.010s
but Allow OEM Unlock is still greyed out after 10days connected to the Wifi at home.
The current situation is, i can't unlock bootloader BUT, i can boot on TWRP for example. But when i try to flash anything it raises an error because bootloader is locked.
Is there any way to get out of this lock/unlock issues to be able again to flash a new custom ROM ?
Thanks a lot for your advices
motorbass said:
Hi guys !
I've just get back my Motorola Z2 play i borrow to one of my friend, but after many trials it seems to be a bit of broken (talk about it below), and after seeking a lot of thread on internet, i feel blocked and i need any advice or help.
Here's the original situation :
- The bootloader has been unlocked in the following way (with fastboot oem get_unlock_data method, then retrieve the key from motorola website)
then, AICP 16.1 has been flashed.
- Everything worked fine except bluetooth can't be used anymore, it can't be activated anymore i didn't know why. (i get back the phone at this step)
- As i appreciate using bluetooth, i tried to upgrade AICP, flash it again and wipe cache/data to check if bluetooth become available again but it never happened.
So i tried to flash the official Motorola ROM and my issues started...
After flashing with this official ROM from Motorola (ALBUS_OPSS27.76_12_25_23_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC), phone worked well but i wasn't impossible to use any Google services (if i opened play store it says : "Impossible Connection, an issue has happened while trying to connect to google servers" every time, same error if i wanted to check updates and so on...)
I saw a post on internet that say to relock the bootloader to get the phone fully encrypted and to be trusted from google servers, so i did it using fastboot oem lock. (this is a huge mistake...i know...)
It didn't change anything and google services raise the same error, but now i'm unable to flash any other rom or anything... moreover, OEM unlocked tick on the phone menu is greyed out, i tried to let it connected to internet for ~10days but it doesn't change anything.
When i tried to unlock bootloader again to allow me to flash another rom (i wanted to try lineage os), i got those error :
Code:
fastboot oem unlock "CODE_FROM_MOTOROLA"
(bootloader) invalid boot state
OKAY [ 0.007s]
Finished. Total time: 0.010s
but also
Code:
fastboot flashing unlock
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options.
OKAY [ 0.009s]
Finished. Total time: 0.010s
but Allow OEM Unlock is still greyed out after 10days connected to the Wifi at home.
The current situation is, i can't unlock bootloader BUT, i can boot on TWRP for example. But when i try to flash anything it raises an error because bootloader is locked.
Is there any way to get out of this lock/unlock issues to be able again to flash a new custom ROM ?
Thanks a lot for your advices
Click to expand...
Click to collapse
Your original issue was because you upgraded from stock Oreo, which if you would have spent the 5 minutes reading you would have known that A11 roms all require stock Pie modem.
As for your current situation, i don't think you can get out of this one; you might try your hand with Lenovo Moto Smart Assistant or try putting the pie update into the phone to force the updater to upgrade you but you really have put yourself in a weird situation. Your phone is now
1. Locked
2. On the stock rom
3. Without the original recovery
So the bootloader is ****ing confused as to what to do
Hi !
First of all, thanks a lot for your answer.
To be honest i simply used this thread when first upgraded to AICP ( https://forum.xda-developers.com/t/discontinued-rom-11-0-offical-aicp-16-1-albus.4335535/ ), so sorry i wasn't aware about any requirements about the stock Pie modern you mentioned.
Meanwhile, i already have a look with LMSA tool, everything is recognized but it can't load/flash anything as the bootloader is locked/broken.
motorbass said:
Hi !
First of all, thanks a lot for your answer.
To be honest i simply used this thread when first upgraded to AICP ( https://forum.xda-developers.com/t/discontinued-rom-11-0-offical-aicp-16-1-albus.4335535/ ), so sorry i wasn't aware about any requirements about the stock Pie modern you mentioned.
Meanwhile, i already have a look with LMSA tool, everything is recognized but it can't load/flash anything as the bootloader is locked/broken.
Click to expand...
Click to collapse
{
"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"
}
I know nowadays a short attention span is rewarded, but reading all the way through to the end is usually worth it. If LMSA can't save you then you have officially bricked your phone (unless you find some exploit) OEM Unlock remains unavailable because the image you flashed isn't signed, and as such the phone has gone into FLASHING_LOCKED instead of OEM_LOCKED; i'm pretty sure you can guess the difference between those two.
One last hail mary would be the updater and P; since OTA's are signed you may be able to unlock your phone again (and this time custom roms WILL work! How about that)
Yeah it's my mistake.. i've just focused on the first post tutorial rather than reading the whole posts before. I also dislike people doing this but this time it's me haha..
(You right i'm into Flashing_locked status.)
Unfortunately Update menu tell me i'm already up to date, don't know if it's related that also any google services says it can't connect to google servers.
i'm afraid OTA update will work again.
motorbass said:
Yeah it's my mistake.. i've just focused on the first post tutorial rather than reading the whole posts before. I also dislike people doing this but this time it's me haha..
(You right i'm into Flashing_locked status.)
Unfortunately Update menu tell me i'm already up to date, don't know if it's related that also any google services says it can't connect to google servers.
i'm afraid OTA update will work again.
Click to expand...
Click to collapse
That is probably because your particular region did not get Pie; search through this forum, there's a way to force the updater to recognize the OTA