Related
I bought a Xiaomi mi 8 in a Xiaomi Shop in Shanghai. If I try to relock the bootloader I always get stuck booting on the recovery mode. Besides, I can not flash anything (supersu, xposed...) because I always end in bootloop; in both cases it is a softbrick
Can anybody help me?
If you have a mi8 Chinese box you aren't allowed to flash global ROM and lock bootloader.
And is there any way to fix it? Writing to Xiaomi, waiting X time...?
Thanks for your reply!
There are literally, more than a few hundred threads about not relocking. You modified your phone without reading up, no sympathy here. Your phone is dead if it is not global version. Gone. Paperweight. All the best to you
achickennugget said:
There are literally, more than a few hundred threads about not relocking. You modified your phone without reading up, no sympathy here. Your phone is dead if it is not global version. Gone. Paperweight. All the best to you
Click to expand...
Click to collapse
Hey! Nice to meet you and thanks for your kind answer. This placer is better thanks to people like you.
By the way,my mobile works perfectly. I relocked the bootloader more than once and I just needed to unblocked to solve it. About reading the posts, If you had read you would have realized that what interests me is simply to know if I can re-block the bootloader.
Who taught you to help people in forums that have problems and is probably having a bad time? Hitler?
Bortex19 said:
Hey! Nice to meet you and thanks for your kind answer. This placer is better thanks to people like you.
By the way,my mobile works perfectly. I relocked the bootloader more than once and I just needed to unblocked to solve it. About reading the posts, If you had read you would have realized that what interests me is simply to know if I can re-block the bootloader.
Who taught you to help people in forums that have problems and is probably having a bad time? Hitler?
Click to expand...
Click to collapse
You are welcome for my help. There are posts all over. I suggest you learn the courtesy of posting in the right sections instead or even better (to read first), this belongs in Q&A: https://forum.xda-developers.com/mi-8/help/to-relock-bootloader-chinese-device-t3834937 where if you read you would have realized it is all over the place, including one i created: https://forum.xda-developers.com/mi-8/how-to/please-read-tweaking-mi-8-t3833454. Anyways, have a good day, leaving this here for anyone else before they create another thread to "unblock" their bootloader
Bortex19 said:
And is there any way to fix it? Writing to Xiaomi, waiting X time...?
Thanks for your reply!
Click to expand...
Click to collapse
You can check out official xiaomi forum to see a way. However the official way posted there including open up the device & tinkering with the EDL mode, which is really too much of a hassle :/
---------- Post added at 10:58 AM ---------- Previous post was at 10:57 AM ----------
Bortex19 said:
Hey! Nice to meet you and thanks for your kind answer. This placer is better thanks to people like you.
By the way,my mobile works perfectly. I relocked the bootloader more than once and I just needed to unblocked to solve it. About reading the posts, If you had read you would have realized that what interests me is simply to know if I can re-block the bootloader.
Who taught you to help people in forums that have problems and is probably having a bad time? Hitler?
Click to expand...
Click to collapse
Are you having a modern Xiaomi device? How can you relock bootloader without sending it to bootloop?
achickennugget said:
You are welcome for my help. There are posts all over. I suggest you learn the courtesy of posting in the right sections instead or even better (to read first), this belongs in Q&A: https://forum.xda-developers.com/mi-8/help/to-relock-bootloader-chinese-device-t3834937 where if you read you would have realized it is all over the place, including one i created: https://forum.xda-developers.com/mi-8/how-to/please-read-tweaking-mi-8-t3833454. Anyways, have a good day, leaving this here for anyone else before they create another thread to "unblock" their bootloader
Click to expand...
Click to collapse
Better now, at least you're helping to find the information. And you are right, I should read more before doing anything; in fact, I read a lot but you know, internet is so big and it's no difficult to get lost in that information sea (even more if you're a noob in the area). I'll do it better next time.
Have a good day.
TeeHoang said:
You can check out official xiaomi forum to see a way. However the official way posted there including open up the device & tinkering with the EDL mode, which is really too much of a hassle :/
---------- Post added at 10:58 AM ---------- Previous post was at 10:57 AM ----------
Are you having a modern Xiaomi device? How can you relock bootloader without sending it to bootloop?
Click to expand...
Click to collapse
I bought it a couple of weeks ago. And no, I cannot relock it without sending it to bootloop.
The thing went like that: I unlocked the bootloader, I flashed the global ROM, I relocked the bootloader and I fell into recovery bootloop. So I entered on fastboot mode, I unblocked the bootloader again (with the Xiaomi tool), I went to fastboot again and I reflashed the global ROM.
The bootloader have to be open to allow the global ROM work. I don't know why I have avoided the brick, but this is what I've done at least twice.
Bortex19 said:
I bought it a couple of weeks ago. And no, I cannot relock it without sending it to bootloop.
The thing went like that: I unlocked the bootloader, I flashed the global ROM, I relocked the bootloader and I fell into recovery bootloop. So I entered on fastboot mode, I unblocked the bootloader again (with the Xiaomi tool), I went to fastboot again and I reflashed the global ROM.
The bootloader have to be open to allow the global ROM work. I don't know why I have avoided the brick, but this is what I've done at least twice.
Click to expand...
Click to collapse
Well if it bootloops the first time after you relocked it, it'll bootloop again & again. Was there any time after relocking did your phone boot properly? If not, you didn't avoid anything. As far as I understand, boot loop = soft brick.
And this is what I found on MIUI official forum:
TUTORIAL FLASH MI 8 BOOTLOP (SOFTBRICK & BRICK) WITH TESTPOIN:http://en.miui.com/thread-3459005-1-1.html
Bortex19 said:
I bought it a couple of weeks ago. And no, I cannot relock it without sending it to bootloop.
The thing went like that: I unlocked the bootloader, I flashed the global ROM, I relocked the bootloader and I fell into recovery bootloop. So I entered on fastboot mode, I unblocked the bootloader again (with the Xiaomi tool), I went to fastboot again and I reflashed the global ROM.
The bootloader have to be open to allow the global ROM work. I don't know why I have avoided the brick, but this is what I've done at least twice.
Click to expand...
Click to collapse
If I read it right, your device goes into bootloop when installing a Global ROM version and trying to block the bootloader. Probably your device is a Chinese version, which should only have the bootloader locked running a China ROM.
Otherwise, it will be bootloop.
gugugrp said:
If I read it right, your device goes into bootloop when installing a Global ROM version and trying to block the bootloader. Probably your device is a Chinese version, which should only have the bootloader locked running a China ROM.
Otherwise, it will be bootloop.
Click to expand...
Click to collapse
True that. Any Chinese devices running global will get (soft)bricked
Yeah, I was asking is you know the way to lock a chinese phone in global rom. Maybe in the future or with MIUI 10
Is it possible to enter EDL mode via opening your device and connecting the dots to enter 9008 Mode and than use QFIL (Qualcomm_Flash_Image_Loader) to restore the software, instead of going with the MiFlashTool and a needed EDL authorized account?
Bortex19 said:
Yeah, I was asking is you know the way to lock a chinese phone in global rom. Maybe in the future or with MIUI 10
Click to expand...
Click to collapse
This is still too early to know, because development is still slow.
Wrong forum section.
Sigray said:
Wrong forum section.
Click to expand...
Click to collapse
I could not find the way to change it. Do you know how to do it?
achickennugget said:
There are literally, more than a few hundred threads about not relocking. You modified your phone without reading up, no sympathy here. Your phone is dead if it is not global version. Gone. Paperweight. All the best to you
Click to expand...
Click to collapse
Even if he posted in the wrong section he didn't deserve an answer like yours. Keep in mind the Android cooperate spirit and try not to be that rude. And if you had read better his post you had understood how great is the information he gave, go on reading below.
Bortex19 said:
The thing went like that: I unlocked the bootloader, I flashed the global ROM, I relocked the bootloader and I fell into recovery bootloop. So I entered on fastboot mode, I unblocked the bootloader again (with the Xiaomi tool), I went to fastboot again and I reflashed the global ROM.
The bootloader have to be open to allow the global ROM work. I don't know why I have avoided the brick, but this is what I've done at least twice.
Click to expand...
Click to collapse
Actually these are excellent news, I had never read about a case like this. We knew that if the bootloader was unlocked by the seller and you locked it flashing a global rom (being a Chinese phone) you would get a brick only repairable through testpoint and using an authorized account. But I had never read about doing the same whith the bootloader unlocked by the user and I didn't know if it would be possible to unlock it again. So now we know this :
- Chinese unlocked by the seller -> brick locking while flashing global -> impossible to unlock and edl needed
- Chinese unlocked by the owner -> brick locking while flashing global -> ability to re-unlock and flash normally
I had some questions now :
1.- Did you have to wait to unlock the bootloader the first time? (360hrs, 720hrs.. You know)
2.- Did you have to wait when unlocking after the brick or was it instantly unlocked?
Thanks in advance!
descarao81 said:
Even if he posted in the wrong section he didn't deserve an answer like yours. Keep in mind the Android cooperate spirit and try not to be that rude. And if you had read better his post you had understood how great is the information he gave, go on reading below.
Actually these are excellent news, I had never read about a case like this. We knew that if the bootloader was unlocked by the seller and you locked it flashing a global rom (being a Chinese phone) you would get a brick only repairable through testpoint and using an authorized account. But I had never read about doing the same whith the bootloader unlocked by the user and I didn't know if it would be possible to unlock it again. So now we know this :
- Chinese unlocked by the seller -> brick locking while flashing global -> impossible to unlock and edl needed
- Chinese unlocked by the owner -> brick locking while flashing global -> ability to re-unlock and flash normally
I had some questions now :
1.- Did you have to wait to unlock the bootloader the first time? (360hrs, 720hrs.. You know)
2.- Did you have to wait when unlocking after the brick or was it instantly unlocked?
Thanks in advance!
Click to expand...
Click to collapse
It seems to me that this is not so, as some members still manage. However, since they did not add their personal Account to the developer options, they were not able to unlock the device again because they did not have the account associated with the device. It seems to be something related to different cases.
What can be recommended is that the devices unlocked by the seller, return to Chinese ROM more stable, and have your bootloader blocked. By then, the user requests to unblock the bootloader regardless of the time they have to wait. Thus making everything safer, in the case of possible bricks in the future.
gugugrp said:
What can be recommended is that the devices unlocked by the seller, return to Chinese ROM more stable, and have your bootloader blocked. By then, the user requests to unblock the bootloader regardless of the time they have to wait. Thus making everything safer, in the case of possible bricks in the future.
Click to expand...
Click to collapse
Have you ever heard of read about somebody doing that? Because I think there's still the doubt about the unlocking method used by the sellers, whether they do a regular unlock with an account or they patch the boot in any way which could cause problems locking the bootloader.
Hello Forum, this phone is really getting to me now.
I just want to return the phone to complete stock, box fresh with no messages about boot loader etc
as I may return the phone for another one
but in all my 11 years on xda, I have never had a problem like this phone.....
Bloody boot-loader messages, re-locking bootloader, returning to stock, firmware files...
I cant whatever i try, get rid of the N/A (if i use TWRP to install magisk) or BAD KEY if I dont use TWRP
My Phone details are as follows
its a xt1922-2 UK Generic Phone, it has had the OTA update (the June 2018 one), its a Moto G6 play JETER
Build Number is OPP 27.91.87
It doesnt matter whatever firmware I download, whether the flashing gives errors or not in FASTBOOT
I cant get rid of the error message n/a or bad key!!!
whenever I try to lock bootloader, by fastboot oem lock..... it say run the command again, I run the fastboot code again, and it gives a error, something similar to please flash a valid android image, I CAN relock it by using : fastboot flashing lock ........... but still the bootloader error is there!!! HELP!!!!
OK so I assume you have a pretty descent idea of what your doing but just to be sure... Your bootloader is unlocked when trying to flash stock via vast opt right? If it's not unlocked you can't modify system. Your using the Jeter firmware not aljeter right?
Can you grab screen shots of the errors to see if maybe there's something we see that you didn't that might be relevant.
Also stick to one thread per issue. That way we know what others ha e suggested, exactly what you have done, the outcome, etc.
Sent from my moto g(6) plus using Tapatalk
Xplorer4x4 said:
OK so I assume you have a pretty descent idea of what your doing but just to be sure... Your bootloader is unlocked when trying to flash stock via vast opt right? If it's not unlocked you can't modify system. Your using the Jeter firmware not aljeter right?
Can you grab screen shots of the errors to see if maybe there's something we see that you didn't that might be relevant.
Also stick to one thread per issue. That way we know what others ha e suggested, exactly what you have done, the outcome, etc.
Sent from my moto g(6) plus using Tapatalk
Click to expand...
Click to collapse
Right, Lets begin....
Originally i followed a guide to root my g6 play,that was by booting a patched twrp, and dm verity and another file beginning with Q, then flash the twrp........... all that was working except dm verity which gave a error (cant remember which one)
i have tried a different number of firmwares (motorola themselves said try jeter and alijeter - as some alijeter firmware are for my model xt1922-2)
now there was a OTA, as far as I can remember, there was 2 ota updates, they went smoothly, but still the BAD KEY message (brought on by the patched dm verity file i think)
after doing this ota, the oem unlocking button was no longer greyed out, so i tried fastboot oem lock but it gives errors about bootloader bad key and more, or invalid android image
whatever happens, i cannot relock the bootloader to remove the message, i cant flash any firmware for my model without one or two errors.......
the only thing that works, to show the bootloader is locked, is fastboot flashing_lock (as my bootloader screen shows flashing_unlocked) this shows, by doing fastboot getvar all and all that, that the bootloader is relocked....but I still have bad key error, and then have to oem unlock again to do anything.....help
Again is your bootloader unlocked when flashing stock?
Sent from my moto g(6) plus using Tapatalk
Xplorer4x4 said:
Again is your bootloader unlocked when flashing stock?
Sent from my moto g(6) plus using Tapatalk
Click to expand...
Click to collapse
yes, on the bootloader screen, it says flashing_unlocked
and on the development setting its greyed out and says bootloader is already unlocked
biggary said:
yes, on the bootloader screen, it says flashing_unlocked
and on the development setting its greyed out and says bootloader is already unlocked
Click to expand...
Click to collapse
Ok so let's put this out there first. I am helping you for free because I generally enjoy being a helping hand! I asked for screenshots, which we still have not gotten. I asked if bootloader was unlocked still to be sure, because I wasn't sure if you had tried to relock it. I think you did try to relock based on your post, but I had to ask twice to get that information out of you. If you truly want help, help those who want to help you help yourself.
That said, I asked for screenshots because I have never heard of a "bad key" error. The way I understood it you were seeing this error in TWRP. After a quick google search I found this image:
https://forums.lenovo.com/lnv/attachments/lnv/230/6043/1/IMG-20170528-WA0015.jpg
I assume this is the same error you see? If so, you can actually ignore it. If you don't want to ignore it, you can try going to bootloader and type this: fastboot oem fb_mode_clear
Also, you can try to see if there is a modified logo.bin for your device and flash it. You could try the G6+ logo.bin possibly:
https://forum.xda-developers.com/moto-g6/themes/bootlogo-remove-message-unlocked-t3789155
PS: I found this info with a quick google search, so I assume you didn't even bother to search?
Yes, I always search several times, and read other forums to see if error is posted elsewhere.
Its hard to take a screenshot when the phone is in bootloader mode.
the screen is totally black. it shows just in the top left hand corner with the words 'bad key' and if I installed magisk (I dont install twrp, I just boot into it), I get the message 'N/A', the bad key is caused by errors when flashing the stock firmware, for some reason, thats why I cant remove the message, or relock the bootloader.
The bootloader unlocked messages that you linked to, are completely different looking than mine.
One thing confuses me, when you boot into bootloader, it says JETER, as the model name, but no JETER firmware flashes properly, my phone is a xt1922-2 which for some reason posted everywhere as ALIJETER........ god, this phone is a pain in the arse!
I am having the same issue as you, i am trying so much that i forget about doing root and just want to lock my bootloader again ;-;
The XT1922-2 is an annoying little ****.
biggary said:
Yes, I always search several times, and read other forums to see if error is posted elsewhere.
Its hard to take a screenshot when the phone is in bootloader mode.
the screen is totally black. it shows just in the top left hand corner with the words 'bad key' and if I installed magisk (I dont install twrp, I just boot into it), I get the message 'N/A', the bad key is caused by errors when flashing the stock firmware, for some reason, thats why I cant remove the message, or relock the bootloader.
The bootloader unlocked messages that you linked to, are completely different looking than mine.
One thing confuses me, when you boot into bootloader, it says JETER, as the model name, but no JETER firmware flashes properly, my phone is a xt1922-2 which for some reason posted everywhere as ALIJETER........ god, this phone is a pain in the arse!
Click to expand...
Click to collapse
I agree it's a pain in the arse! Can't get past it at all! If I had the knowledge to work on the kernel and bootloader i'd make a custom bootloader that atleast said lenovo sucks instead.
All other moto G6 variants will haev the error that the other guy linked to, same as my Moto g5, G, E, and X did.
My E3 is worse as that has a Mediatek CPU lmao
w4r3zgod said:
I agree it's a pain in the arse! Can't get past it at all! If I had the knowledge to work on the kernel and bootloader i'd make a custom bootloader that atleast said lenovo sucks instead.
All other moto G6 variants will haev the error that the other guy linked to, same as my Moto g5, G, E, and X did.
My E3 is worse as that has a Mediatek CPU lmao
Click to expand...
Click to collapse
You can't get rid of it. You likely cannot relock bootloader. Warranty is void just by requesting unlock code. @biggary same
madbat99 said:
You can't get rid of it. You likely cannot relock bootloader. Warranty is void just by requesting unlock code. @biggary same
Click to expand...
Click to collapse
Yea warranty void.
biggary said:
Hello Forum, this phone is really getting to me now.
I just want to return the phone to complete stock, box fresh with no messages about boot loader etc
as I may return the phone for another one
but in all my 11 years on xda, I have never had a problem like this phone.....
Bloody boot-loader messages, re-locking bootloader, returning to stock, firmware files...
I cant whatever i try, get rid of the N/A (if i use TWRP to install magisk) or BAD KEY if I dont use TWRP
My Phone details are as follows
its a xt1922-2 UK Generic Phone, it has had the OTA update (the June 2018 one), its a Moto G6 play JETER
Build Number is OPP 27.91.87
It doesnt matter whatever firmware I download, whether the flashing gives errors or not in FASTBOOT
I cant get rid of the error message n/a or bad key!!!
whenever I try to lock bootloader, by fastboot oem lock..... it say run the command again, I run the fastboot code again, and it gives a error, something similar to please flash a valid android image, I CAN relock it by using : fastboot flashing lock ........... but still the bootloader error is there!!! HELP!!!!
Click to expand...
Click to collapse
I finally found this last night. Didn't remove the n/a, but it replaced the boot logo image with something that mostly hides it.
---------- Post added at 12:30 AM ---------- Previous post was at 12:30 AM ----------
jdavidm2 said:
I finally found this last night. Didn't remove the n/a, but it replaced the boot logo image with something that mostly hides it.
Click to expand...
Click to collapse
https://www.getdroidtips.com/moto-g6-plus-unlocked-bootloader-warning
jdavidm2 said:
I finally found this last night. Didn't remove the n/a, but it replaced the boot logo image with something that mostly hides it.
---------- Post added at 12:30 AM ---------- Previous post was at 12:30 AM ----------
https://www.getdroidtips.com/moto-g6-plus-unlocked-bootloader-warning
Click to expand...
Click to collapse
I found this for another g6. Use the firmware for your model and it may work.
https://forum.xda-developers.com/moto-g6/development/stock-firmware-moto-g6-t3792292/post78432631
https://www.xda-developers.com/motorola-moto-g7-plus-t-mobile/
It has NFC and B71 which G7 doesn't have.
Hopefully bootloader will be unlockable. If so, I may get one and paid in full and have it SIM unlocked, and flash RETAIL ROM
Any update on this? Been holding out on upgrading for this if it's true
If this is right it could be the revvl 3 or 3 plus as product sku is tmo revvl this is from wifi alliance
It's the g7 plus and g7 play https://www.tmonews.com/2019/07/t-mobile-revvlry-official-specs-price/
Can we root it using g7 plus method and unlock bootloader same way I currently have the phone
You can try to get bootloader unlock code it won't hurt nothing but as far as rooting I don't know but should be the same
krazy_smokezalot said:
Can we root it using g7 plus method and unlock bootloader same way I currently have the phone
Click to expand...
Click to collapse
If you can unlock the bootloader, then rooting will be the easy part as you can usually just flash Magisk (or create a patched boot.img in Magisk Manager and flash the patched boot.img). TWRP may even work too, assuming T-Mo didn't heavily modify the underlying software and kernel.
The only question is gonna be unlocking the bootloader as it's not technically branded a Moto device (although is allegedly has the same codename). Moto may not ship a bootloader code to you, you may need to go thru T-Mobile in some way first.
Jleeblanch said:
If you can unlock the bootloader, then rooting will be the easy part as you can usually just flash Magisk (or create a patched boot.img in Magisk Manager and flash the patched boot.img). TWRP may even work too, assuming T-Mo didn't heavily modify the underlying software and kernel.
The only question is gonna be unlocking the bootloader as it's not technically branded a Moto device (although is allegedly has the same codename). Moto may not ship a bootloader code to you, you may need to go thru T-Mobile in some way first.
Click to expand...
Click to collapse
But T-MOBILE don't offer bootloader unlock I work for them. Well just gonna try cause it's given the code name lake on cpu z and the manufacturer is Motorola
krazy_smokezalot said:
But T-MOBILE don't offer bootloader unlock I work for them. Well just gonna try cause it's given the code name lake on cpu z and the manufacturer is Motorola
Click to expand...
Click to collapse
Knowing they (as in T-Mo) doesn't offer codes, which I figured they didn't, then I'd at least try to paste your unlock code on Moto's site. Worst that'll happen is a message will pop up saying you device doesn't qualify.
t mobile g7 plus bootloader unlock
i can confirm that the bootloader for the t mobile moto g7 plus is locked and could not get a unlock from Motorola website it probably has to be paid for to get a unlock. i am unable to confirm at this time if you can get a unlock i got mine on JOD jump on demand. if someone out there gets one paid for and trys for a bootloader unlock please confirm if you can or not after it is paid for. i think you could but i cant confirm that at this time please any ones feed back would be a big help we should all work to gather on this i hope for a bootloader unlock or a work around if someone figures something out but as fas as i know at this time if you owe on 1 there is no boot loader unlock but just maybe the possibility after it is paid i am not shure if you would have to go though t mobile first to get a unlock thanks and anyone's feed back would be very much appreciated.
Also this is probably the same moto g7 build lake as the one off there website but with t mobile branding and a locked down bootloader so twrp and magisk root should work if you can get a bootloader unlock. if someone does please confirm here if it does work or not thanks and i welcome your feedback from anyone.
REVVLRY+ is indeed G7 plus
Jimhackthorn said:
i can confirm that the bootloader for the t mobile moto g7 plus is locked and could not get a unlock from Motorola website it probably has to be paid for to get a unlock. i am unable to confirm at this time if you can get a unlock i got mine on JOD jump on demand. if someone out there gets one paid for and trys for a bootloader unlock please confirm if you can or not after it is paid for. i think you could but i cant confirm that at this time please any ones feed back would be a big help we should0 all work to gather on this i hope for a bootloader unlock or a work around if someone figures something out but as fas as i know at this time if you owe on 1 there is no boot loader unlock but just maybe the possibility after it is paid i am not shure if you would have to go though t mobile first to get a unlock thanks and anyone's feed back would be very much appreciated.
Also this is probably the same moto g7 build lake as the one off there website but with t mobile branding and a locked down bootloader so twrp and magisk root should work if you can get a bootloader unlock. if someone does please confirm here if it does work or not thanks and i welcome your feedback from anyone.
Click to expand...
Click to collapse
Ok I'll try it cause it got it for free and it's paid off. Got it from my job as a gift. So I'll definitely check it out then I'm even more interested. But I kinda doubt it cause the bootloader has the name revvl in it in CPU Z. Bootloader goes by MBM-3.0lake_revvl-43c7c77-190517
Ok so no I tried fastboot oem unlock and nothing happens on the phone anyone else has any idea they want me to try. I'm able to check oem unlock but in fastboot the command oem unlock does nothing on the phone
unlock instructions
krazy_smokezalot said:
Ok so no I tried fastboot oem unlock and nothing happens on the phone anyone else has any idea they want me to try. I'm able to check oem unlock but in fastboot the command oem unlock does nothing on the phone
Click to expand...
Click to collapse
That's because you got to get a unlock key from Motorola. you will first need to make a account with Motorola https://motorola-global-portal.custhelp.com/app/standalone%2Fbootloader%2Funlock-your-device-b
here is your instructions on how to get a key
Put your device in fastboot mode (power off, then press the power and volume down buttons simultaneously).
On your desktop, open a command prompt or terminal, and go to the directory where you installed the Android ADB (or make sure fastboot is in your $PATH)
At the prompt, type $ fastboot oem get_unlock_data
The returned string will be used to retrieve your unlock key.
Paste together the 5 lines of output into one continuous string without (bootloader) or ‘INFO’ or white spaces. Your string needs to look like this: 0A40040192024205#4C4D355631323030373731363031303332323239#BD008A672BA4746C2CE02328A2AC0C39F951A3E5#1F532800020000000000000000000000 EXAMPLE
Check if your device can be unlocked by pasting this string in the field below, and clicking “Can my device be unlocked?”
If your device is unlockable, a "REQUEST UNLOCK KEY" button will now appear at the bottom of this page.
then get the key put in your email address and you will get UNIQUE_KEY
then in adb put in fastboot oem unlock ((UNIQUE_KEY)) here
then fastboot reboot
If yours is paid for please let me know if it works mine is not paid for.
Jimhackthorn said:
That's because you got to get a unlock key from Motorola. you will first need to make a account with Motorola https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
here is your instructions on how to get a key
Put your device in fastboot mode (power off, then press the power and volume down buttons simultaneously).
On your desktop, open a command prompt or terminal, and go to the directory where you installed the Android ADB (or make sure fastboot is in your $PATH)
At the prompt, type $ fastboot oem get_unlock_data
The returned string will be used to retrieve your unlock key.
Paste together the 5 lines of output into one continuous string without (bootloader) or ‘INFO’ or white spaces. Your string needs to look like this: 0A40040192024205#4C4D355631323030373731363031303332323239#BD008A672BA4746C2CE02328A2AC0C39F951A3E5#1F532800020000000000000000000000 EXAMPLE
Check if your device can be unlocked by pasting this string in the field below, and clicking “Can my device be unlocked?”
If your device is unlockable, a "REQUEST UNLOCK KEY" button will now appear at the bottom of this page.
then get the key put in your email address and you will get UNIQUE_KEY
then in adb put in fastboot oem unlock ((UNIQUE_KEY)) here
then fastboot reboot
If yours is paid for please let me know if it works mine is not paid for.
Click to expand...
Click to collapse
Cool thanks for this I'll follow this instructions to unlock bootloader. I'll post back my findings
krazy_smokezalot said:
Cool thanks for this I'll follow this instructions to unlock bootloader. I'll post back my findings
Click to expand...
Click to collapse
This is a common method to unlock Motorola smartphone bootloader.
Hopefully you will be lucky to get the code, but you may wait up to 2 weeks after initial release.
I can confirm that Motorola will give you the unlock code.
Findings
UNLOCKING AND LOCKING BOOTLOADER WILL WIPE YOUR DEVICE> BACKUP PERSONAL DATA IF YOU WANT TO KEEP IT.
I unlocked the bootloader and flashed the moto G7 plus RETAIL firmware. Everything worked fine except google pay, and verity being disabled.
Installing TWRP would always give me a recovery boot loop, so I stopped trying, instead just booting into TWRP with fastboot.
I cannot get verity enabled, even after flashing stock and locking the bootloader, so that means no Google Pay, no Google Fi, no whatever else requires verity.
Looking at
Code:
fastboot getvar all
Shows a flag that verity is disabled and another flag that warranty is void, even after flashing stock.
The stock firmware I found in a firmware repo, because I failed to do a full backup of my system (I only backed up boot, system, and data).
Would anyone be willing to unlock their bootloader, boot into TWRP, do a full backup, and share it, to see if I can get back to stock with verity enabled? I'd love Google Pay back.
BanterJSmoke said:
I can confirm that Motorola will give you the unlock code.
Click to expand...
Click to collapse
Wow!!!
This is HUGE!!!
Pay in full to get SIM unlocked first followed by bootloader unlock and flash RETAIL ROM and become G7 Plus
CDMA support is unknown
mingkee said:
Wow!!!
This is HUGE!!!
Pay in full to get SIM unlocked first followed by bootloader unlock and flash RETAIL ROM and become G7 Plus
CDMA support is unknown
Click to expand...
Click to collapse
Except it's nearly $100 less expensive to just buy an unlocked g7+
Hey Everyone,
I'm looking for help. I tried reverting my pixel 5 to stock from beta and am stuck at the boot screen with " your device is corrupt. It cannot be trusted and may not work properly."
I've spent days fiddling with it, and cannot get anywhere with the google repair website because it's saying my bootloader is locked. I don't understand how I purchased it unlocked. Anyway, I cannot get into the settings to unlock the bootloader. It's been a long time since I've been a tinkerer but I do have all the software downloaded to do so. I cannot get my PC to recognize the phone in the command prompt window to try and sideload a software install.
Has this happened to anyone and is there a solution out there somewhere?
Sean Hicks said:
Hey Everyone,
I'm looking for help. I tried reverting my pixel 5 to stock from beta and am stuck at the boot screen with " your device is corrupt. It cannot be trusted and may not work properly."
I've spent days fiddling with it, and cannot get anywhere with the google repair website because it's saying my bootloader is locked. I don't understand how I purchased it unlocked. Anyway, I cannot get into the settings to unlock the bootloader. It's been a long time since I've been a tinkerer but I do have all the software downloaded to do so. I cannot get my PC to recognize the phone in the command prompt window to try and sideload a software install.
Has this happened to anyone and is there a solution out there somewhere?
Click to expand...
Click to collapse
Buying it "unlocked" means you bought it free of a carrier, such as Verizon, who lock the bootloader, and can't be unlocked.
But you still need to unlock the bootloader, it comes locked, for security reasons. So if you never unlocked it, it's locked.
I haven't installed beta 12 yet.
Do you have the latest SDK tools? (adb, fastboot, etc)
I was under the impression though, that you can't downgrade with a locked bootloader. But not sure.
Sean Hicks said:
Hey Everyone,
I'm looking for help. I tried reverting my pixel 5 to stock from beta and am stuck at the boot screen with " your device is corrupt. It cannot be trusted and may not work properly."
I've spent days fiddling with it, and cannot get anywhere with the google repair website because it's saying my bootloader is locked. I don't understand how I purchased it unlocked. Anyway, I cannot get into the settings to unlock the bootloader. It's been a long time since I've been a tinkerer but I do have all the software downloaded to do so. I cannot get my PC to recognize the phone in the command prompt window to try and sideload a software install.
Has this happened to anyone and is there a solution out there somewhere?
Click to expand...
Click to collapse
This probably isn't of any help now, but going forward, it may be. In Developer options, you can enable 'OEM unlocking'. As you can see now, it may well be a very good idea to enable that **before** you start messing with the phone, because if something does go wrong (as it has for you), then you can (hopefully) still get to fastboot and do 'fastboot flashing unlock'.
So, knowing this, you may want to keep an eye out for some tool or something that will allow you to possibly turn on oem unlocking (because your device won't boot).
Another thing to try is switching slots and see if the other slot boots? If you can get to fastboot try; fastboot --set-active=(a or b), then fastboot reboot. (If you don't know which slot is active, do 'fastboot getvar all', in the output it will tell you which is current.
cheers
Your bootloader being locked should not affect your ability to restore factory images/OTAs from Google. They are signed by Google and will pass the signature checks. You should try to download the latest factory image (either 11 or 12beta) and flash it via recovery => adb sideload.
Hello
Hoping somebody can help getting my phone up and running again.
I wanted to unroot my phone, because i was having issues with danish "MitId". And was a bit sloppy with it.
First i tried using SuperSU to remove root. Because i didnt feel like setting everything up again. Didnt work.
Then I locked the OEM Lock in developer settings. Not thinking this would be a fatal error.
Got home from work, and said to myself. Jusk lock the bootloader and the phone will reset itself.
But this is not the case, when you have been stupid enough to lock the OEM lock.
Now I am stuck on "No valid operating system could be found. The device will not boot"
I can get in to fastboot by pushning power+vol down. But cannot flash anything since the phone thinks the OEM Lock is locked on it.
Does anyone know of a solution for me. Or is it going to the shop tommorow and say that my phone is going this. And hope they will sort it for me?
Can't you fix stuff by using https://flash.android.com/ ?
No, unfortuantly not. It fails:
Device Unlock DisabledFor security reasons, you need to enable "OEM unlocking" in order to flash your device. See the device preparation instructions for more information.
Pearsondk said:
No, unfortuantly not. It fails:
Device Unlock DisabledFor security reasons, you need to enable "OEM unlocking" in order to flash your device. See the device preparation instructions for more information.
Click to expand...
Click to collapse
Try sideloading the full OTA. You don't need an unlocked bootloader for that.
Unfortuatly not, if I try to enter recovery mode. The phone just goes back to the screen saying "No valid operating system could be found. The device will not boot"
ADB is not available to me
If you can't sideload the OTA, I'm afraid there is not much else you can do with a locked bootloader except try to RMA it.
Can you get into recovery at all. Even if it's the stock you can attempt a sideload of the stock OTA.zip from Google. You may also try if your on boot slot A
fastboot --set-active=b
On b use
fastboot --set-active=a
Try to see if the other boot slot has an a bootable OS.
*****I apologize I just saw it's actually still locked****"
Contact U-break I-fix if I typed that correctly. The third party warranty repair center for Google's warranty. I believe they can attempt to switch the boot slot with a locked bootloader with the equipment they use to reflash these devices. If anything it's under warranty get the RMA and if the bootloader is locked on it trade someone or sell it and use it to make buying a new cheaper..
JovialQuestion said:
Can you get into recovery at all. Even if it's the stock you can attempt a sideload of the stock OTA.zip from Google. You may also try if your on boot slot A
fastboot --set-active=b
On b use
fastboot --set-active=a
Try to see if the other boot slot has an a bootable OS.
Click to expand...
Click to collapse
No, I can get into fastboot and that is it.
But everything I try in fastboot gets rejected, since it says the phone is locked.
Does the bootloader screen on the phone have the option to boot into Rescue. This has a ADB connection but I am not sure if adb sideload works
Really mad that Google intentionally locks phones this way, turning them into completely functional, but useless piece of junk. I guess that's late stage capitalism for you xD
JovialQuestion said:
Does the bootloader screen on the phone have the option to boot into Rescue. This has a ADB connection but I am not sure if adb sideload works. Use the volume keys and power button to select it
Click to expand...
Click to collapse
Kofa1 said:
Really mad that Google intentionally locks phones this way, turning them into completely functional, but useless piece of junk. I guess that's late stage capitalism for you xD
Click to expand...
Click to collapse
Google is not responsible for phone's with locked bootloaders. They make the device with the specifications the carrier that sells it stipulates. Google themselves allows the unlock.
Lughnasadh said:
If you can't sideload the OTA, I'm afraid there is not much else you can do with a locked bootloader except try to RMA it.
Click to expand...
Click to collapse
Iam guessing the same. Phone doesnt want to do anything.
And since i cant get into the phone to oem lock i am stuck. Live in Denmark, so by law I havnt voided the warrenty by rooting.
Pixel warranty is always valid even if you unlock and root. Google doesn't void the warranty. Go to Google pixel support page. Find warranty and act as if your submitting a RMA and it will tell you after you enter the device IMEI how long your warranty is valid for
Delete
If that were true. Android flash tool https://flash.android.com/welcome
Would work as it's the same process for the browser to flash the very same file. Motorola allowed signed factory img on locked. Google had never allowed that in fastboot as far as I am aware
DroidRommer said:
All you need to do is go here Factory pixel firmwares and scroll down to pixel 7 panther assuming you're not on the pro (cheetah)
-select the latest version for your model whether that's Verizon or whatever if you have the carrier unlocked one like myself just choose the Feb firmware that doesn't have a carrier name at the end of the firmware number (you should have your phone plugged into your PC and in fastboot mode) click flash and follow the steps. These are Googles factory images so it doesn't matter if your bootloader is unlocked or not as long as you choose the latest version and the correct version for your phone. Tbh you can't really brick the pixel 7 as long as you have a PC and are able to put the phone in fastboot mode (holding the volume down and power button while powering on)
-Anytime you run into some kind of bootloop issue or wanna get rid of root flashing the stock firmware from this website will factory reset and revert your phone to the way it was the very first time it was pulled out of the box and powered on. If you have already tried this and you know forsure you did everything correctly then I must admit I have never had this happen and I'm someone who flashes custom roms and goes back to stock to get the latest security update just to turn around and flash another custom rom right after lol. If you need any help or advice feel free to pm me whenever. I have been rooting phones for a long time and have to say that the Google pixel is by far the most user friendly phone I've ever owned when it comes to custom rooms, rooting etc. You can ALWAYS go back as long as you know what steps to take. Sorry for the rant especially if you already figured it out.
Happy Customizing!
DROIDROMMER
Click to expand...
Click to collapse
Their bootloader is locked. You cannot flash a factory image like that with a locked bootloader. They also turned off OEM Unlocking in the developer settings. If they had left this enabled they would be able to use Android Flash Tool as that tool will unlock your bootloader if OEM Unlocking is enabled.
Kofa1 said:
Really mad that Google intentionally locks phones this way, turning them into completely functional, but useless piece of junk. I guess that's late stage capitalism for you xD
Click to expand...
Click to collapse
This wouldn't be Google, they basically encourage you too unlock the bootloader and root if you want as they give you all the tools you need and factory firmware options to go back if you make a mistake. Tbh if you are able to unlock and root the phone to start then you can go back. Even with a locked bootloader you can always flash the latest factory image on googles dev website, you just can't downgrade firmware or install different carrier firmware without the unlocked bootloader. If we really wanna poke at some phone developers I vote Samsung as I have had multiple people ask me to root their phones and if it's a US snapdragon version it cannot be done its so frustrating lol thanks for letting me vent, have a great day if you have the the carrier unlocked dev edition of the pixel 7 and ever need any help feel free to pm me. I have been rooting and romming pixels for a long time
Edit: I was not aware you couldn't flash the stock firmare using googles dev page without oem unlock. I apologize for jumping to conclusions. I thought I had every possible bad scenario happen to me by now but apparently I learned something new today.
DroidRommer said:
This wouldn't be Google, they basically encourage you too unlock the bootloader and root if you want as they give you all the tools you need and factory firmware options to go back if you make a mistake. Tbh if you are able to unlock and root the phone to start then you can go back. Even with a locked bootloader you can always flash the latest factory image on googles dev website, you just can't downgrade firmware or install different carrier firmware without the unlocked bootloader. If we really wanna poke at some phone developers I vote Samsung as I have had multiple people ask me to root their phones and if it's a US snapdragon version it cannot be done its so frustrating lol thanks for letting me vent, have a great day if you have the the carrier unlocked dev edition of the pixel 7 and ever need any help feel free to pm me. I have been rooting and romming pixels for a long time
Click to expand...
Click to collapse
Dude. You cannot flash factory images of any kind on any Google phone with the bootloader in locked status. Please stop giving false information on here. If you want to talk up Samsung do it on a Samsung post. Let's not confuse everyone please
DroidRommer said:
Even with a locked bootloader you can always flash the latest factory image on googles dev website, you just can't downgrade firmware or install different carrier firmware without the unlocked bootloader.
Click to expand...
Click to collapse
To use Android Flash Tool, you have to have OEM Unlocking enabled in Developer Options for it to be able to unlock the bootloader.
To flash the factory image in fastboot you must have an unlocked bootloader.
Lughnasadh said:
Their bootloader is locked. You cannot flash a factory image like that with a locked bootloader. They also turned off OEM Unlocking in the developer settings. If they had left this enabled they would be able to use Android Flash Tool as that tool will unlock your bootloader if OEM Unlocking is enabled.
Click to expand...
Click to collapse
Okay my bad you are right fortunately I have never had this happen. And like someone else said if he can't get into recovery then he can't sideload a factory ota... sorry I'm at a loss on this one. Some custom roms use "fastboot update file.zip" would that do anything in this case or would that command not even work with a locked bootloader I'm assuming. I apologize for trying to act like a know it all I've just never heard of this happening