Related
Hey guys, I seem to have bricked my moto x 2013.
Long story short. I was on soak test 5.0.2. I downgraded like i've done before without issue but this time something went wrong in a big way.
My phone will not boot and just goes to bootloader with the error
downgraded security version
update gpt_main version failed
failed to hab check for gpt_backup: 0x35
CID Read failure
Invalid CID status 0x69
Customer ID error: Contact Dealer: 0xdead
The big issue is my bootloader also relocked so now I can't flash anything to fix the problems.
The comand 'fastboot oem get_unlock_data' returns no result so can't unlock it!!!!
I don't suppose there is a way to unlock it without going through the Motorola website way or entering android?
Any help appreciated. Thanks.
I think you are using the wrong command for boot loader unlock, but push come to shove you might just have to deal with lollipop, or custom roms
The commands correct. I'm not getting a reply because the Cid has change to some strange incorrect one.
I can not flash anything without boot unlock so I can't use any rom lollipop or not.
I need away to unlock the boot loader via fast boot as I can still use that just not for flashing the firmware partitions
beljim7419 said:
The big issue is my bootloader also relocked
The comand 'fastboot oem get_unlock_data' returns no result so can't unlock it!!!!
Click to expand...
Click to collapse
How did you unlock the bootloader in the first place?
flash gpt and motoboot from lolipop, and you should be ok hopefully
JulesJam said:
How did you unlock the bootloader in the first place?
Click to expand...
Click to collapse
Following the Motorola guide on their website.
fastboot oem get_unlock_data
that returns a code and you paste it into their online form.
beljim7419 said:
Following the Motorola guide on their website.
fastboot oem get_unlock_data
that returns a code and you paste it into their online form.
Click to expand...
Click to collapse
Ok so you did it through the website. Didn't you save the email with your unlock code? That's all you need.
you could try that but i wasn't successful doing it on xt 925. I say flash away that gpt and motoboot
JulesJam said:
Ok so you did it through the website. Didn't you save the email with your unlock code? That's all you need.
Click to expand...
Click to collapse
Yes I did but when I tried using the unlock code command with the email code i got an error
I have finally got it to boot
flash gpt and motoboot from lolipop, and you should be ok hopefully
Click to expand...
Click to collapse
I tried this to no avil but after reading your comment that it should fix the issue decided to try again with a different Gtp although thought the lollipop ones were all the same.
Originally I tried the one from Blur_Version.221.41.31.ghost_row.Brasil.en.BR which did not work (in hind sight realise it is because I upgraded from that) so tried the Blur_Version.221.41.38.ghost_row.Brasil.en.BR one and it flashed!
then i rettried the 4.4.4 recovery and that now flashed so went in and wiped the cache and am now waiting for the phone to finish booting.
I'll go back to the latest soak if I can and let you know if all goes well.
Thanks guys.
JulesJam said:
Ok so you did it through the website. Didn't you save the email with your unlock code? That's all you need.
Click to expand...
Click to collapse
beljim7419 said:
Yes I did but when I tried using the unlock code command with the email code i got an error
I have finally got it to boot
I tried this to no avil but after reading your comment that it should fix the issue decided to try again with a different Gtp although thought the lollipop ones were all the same.
Originally I tried the one from Blur_Version.221.41.31.ghost_row.Brasil.en.BR which did not work (in hind sight realise it is because I upgraded from that) so tried the Blur_Version.221.41.38.ghost_row.Brasil.en.BR one and it flashed!
then i rettried the 4.4.4 recovery and that now flashed so went in and wiped the cache and am now waiting for the phone to finish booting.
I'll go back to the latest soak if I can and let you know if all goes well.
Thanks guys.
Click to expand...
Click to collapse
oh, dear it was working on 4.4.4. Tried to update to soak test and half way through the screens gone black and is unresponsive. wont turn on or reboot if i hold the power button down.
think it's definately gone this time. I'll leave it on charge and hope for the best.
it will bounce back man, possibly a corruption somewhere. IF not , reflash gpt and motoboot and redo your steps
beljim7419 said:
oh, dear it was working on 4.4.4. Tried to update to soak test and half way through the screens gone black and is unresponsive. wont turn on or reboot if i hold the power button down.
think it's definately gone this time. I'll leave it on charge and hope for the best.
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202
Read that thread and then read it again...then you may understand what happened and why you should never flash an OTA or Soak Test update zip after having ever downgraded your firmware.
This is well established information now and there is no excuse for users who don't pay attention or refuse to heed the warnings!
Sorry!
beljim7419 said:
oh, dear it was working on 4.4.4. Tried to update to soak test and half way through the screens gone black and is unresponsive. wont turn on or reboot if i hold the power button down.
think it's definately gone this time. I'll leave it on charge and hope for the best.
Click to expand...
Click to collapse
You can't get into bootloader mode?
JulesJam said:
You can't get into bootloader mode?
Click to expand...
Click to collapse
Nope, Proper dead. Black screen no access to anything. Tried pulling the battery but still the same.
*Dead*
beljim7419 said:
Nope, Proper dead. Black screen no access to anything. Tried pulling the battery but still the same.
*Dead*
Click to expand...
Click to collapse
Well there is a root method on the General forum in which they intentionally brick the devices then enter bootloader restore mode to root the phone.
I have no idea if it could save your device, but step 02 of the method bricks the phone:
http://forum.xda-developers.com/moto-x/general/moto-x-root-pogress-60-t3071602
If you can get into bootloader restore mode, perhaps you can save your phone.
What's the process for going about it? I did do a search, but didn't find anything useful. Any help would be appreciated.
Reasoning: I'm going to be upgrading and turning in the phone, so it's time to put it back to factory.
mlw4428 said:
What's the process for going about it? I did do a search, but didn't find anything useful. Any help would be appreciated.
Reasoning: I'm going to be upgrading and turning in the phone, so it's time to put it back to factory.
Click to expand...
Click to collapse
1. Go back to stock everything by following section 0 of this guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
2. While in bootloader mode, use the fastboot command "fastboot oem lock"
If you're turning in the phone to Verizon, this method is okay. However, don't do this if you plan on selling the phone to someone else. If they were to try and unlock the phone again, they would most likely brick it.
According to jcase relocking the bootloader it still shows a modified status code. Your warranty is permanently voided.
Are you on an Edge plan? Otherwise I don't know why you would be returning the phone to upgrade. Also not sure what their rules are on permanently modifying the software of one of these essentially "lease-to-own" devices, so might want to check the terms and conditions if this applies to you. If you are just trading it in for credit toward a new phone, I'd just sell it yourself unlocked and get a lot more for it.
Sent from my XT1254 using Tapatalk
SpyderPride said:
If you are just trading it in for credit toward a new phone, I'd just sell it yourself unlocked and get a lot more for it.
Click to expand...
Click to collapse
A bootloader unlocked, rooted XT1254 would be more valuable to a buyer than one locked down. You've already done all the hard work.
TheSt33v said:
1. Go back to stock everything by following section 0 of this guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
2. While in bootloader mode, use the fastboot command "fastboot oem lock"
If you're turning in the phone to Verizon, this method is okay. However, don't do this if you plan on selling the phone to someone else. If they were to try and unlock the phone again, they would most likely brick it.
Click to expand...
Click to collapse
Heya so I'm in a serious bind.
I skipped your step 1 and locked my bootloader. I have an unlocked bootloader. I recently upgraded through the normal verizon pushed update the marshmallow update. Anyhow. I now want to return the phone for an upgrade and well... I locked the bootloader. Then turn the phone off and turned it back on and it now says locked, but it says failed to validate system image. I then got freaked out and downloaded all the step 1 files and tried to flash the stock rom (which i already had installed!) and that doesn't seem to work. Did I brick my phone? Is there any way to get it working now that it is locked with any kind of android at all?
You're probably fine @droidfun1. You just need to use the marshmallow firmware package instead of the lollipop one. Get it here: https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3531571
Yup, I tried flashing the stock 6.0.1 rom with fastboot on my mac but I got all kinds of fails.
I found a mac compatible command line version of RSDLite and it totally worked! Not sure why fastboot couldn't successfully flash the same stock rom?
Now I just need to remove the bootloader unlocked warning (my phone is now locked status 2), but not sure if I can now that it is locked.
TheSt33v said:
You're probably fine @droidfun1. You just need to use the marshmallow firmware package instead of the lollipop one. Get it here: https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3531571
Click to expand...
Click to collapse
droidfun1 said:
Yup, I tried flashing the stock 6.0.1 rom with fastboot on my mac but I got all kinds of fails.
I found a mac compatible command line version of RSDLite and it totally worked! Not sure why fastboot couldn't successfully flash the same stock rom?
Now I just need to remove the bootloader unlocked warning (my phone is now locked status 2), but not sure if I can now that it is locked.
Click to expand...
Click to collapse
Strange. As far as I understand it, RSDlite just automates fastboot, so even if you're using RSDlite, you're actually using fastboot. Whatever works though.
As for the unlocked bootloader message, see my response to that post you made.
I have a Moto X First Gen XT1058, it had 5.1, then I upgraded with LineageOS to 6.0, it had some issues so I wanted to get back to 5.1, so I downgraded to 4.2.2 and then installed the OTA update, while rebooting after the install, my phone got full bricked, would not respond until I managed to get it into bootloader with a tutorial, but now I can't do anything pass that.
In the bootloader menus says:
Failed to hab check for gpt_main: 0x4e
CID Read Failure
Invalid CID status 0x69
Custome ID error. Contact Dealer: 0xdead
Fastboot Reason: Invalid CID
USB Connected
I am running fastboot 30.BE, I am trying to get the bootloader unlocked but everytime I try to get the "fastboot oem get_unlock_data" and get the error message "bootloader could not get unlock data".
I've tried almost 5 different adb tools, and drivers, I've read about 50+ post and tried all the commands , tried rsd but it wont flash gpt, maybe I haven't found the right post, but after several hours of research I running out of ideas, what can I try, what am I doing wrong?
Still stucked?
Cesarisg said:
I have a Moto X First Gen XT1058, it had 5.1, then I upgraded with LineageOS to 6.0, it had some issues so I wanted to get back to 5.1, so I downgraded to 4.2.2 and then installed the OTA update, while rebooting after the install, my phone got full bricked, would not respond until I managed to get it into bootloader with a tutorial, but now I can't do anything pass that.
In the bootloader menus says:
Failed to hab check for gpt_main: 0x4e
CID Read Failure
Invalid CID status 0x69
Custome ID error. Contact Dealer: 0xdead
Fastboot Reason: Invalid CID
USB Connected
I am running fastboot 30.BE, I am trying to get the bootloader unlocked but everytime I try to get the "fastboot oem get_unlock_data" and get the error message "bootloader could not get unlock data".
I've tried almost 5 different adb tools, and drivers, I've read about 50+ post and tried all the commands , tried rsd but it wont flash gpt, maybe I haven't found the right post, but after several hours of research I running out of ideas, what can I try, what am I doing wrong?
Click to expand...
Click to collapse
Salik Iqbal said:
Still stucked?
Click to expand...
Click to collapse
Sadly yes, I haven't figured out, I can't unlock bootloader, I can't flash a rom without unlocking bootloader, I've tried 5.1, 4.2.2 and 4.4.4, none of them work without unlocking bootloader, RSD Lite wont work, gets fail message, I'm really running out of ideas, still reading lots of threads from all over the world, even translating some foreign languages.
Download this:
https://drive.google.com/open?id=0BxZBxVJDPGZjaUFlSmt4cDFLYW8
Make sure your battery is charge enough, and you are getting battery ok, unrar the folder, and flash the . xml from rsd lite, hope your device boot again.
Best of luck.
Cesarisg said:
I have a Moto X First Gen XT1058, it had 5.1, then I upgraded with LineageOS to 6.0, it had some issues so I wanted to get back to 5.1, so I downgraded to 4.2.2 and then installed the OTA update, while rebooting after the install, my phone got full bricked, would not respond until I managed to get it into bootloader with a tutorial, but now I can't do anything pass that.
In the bootloader menus says:
Failed to hab check for gpt_main: 0x4e
CID Read Failure
Invalid CID status 0x69
Custome ID error. Contact Dealer: 0xdead
Fastboot Reason: Invalid CID
USB Connected
I am running fastboot 30.BE, I am trying to get the bootloader unlocked but everytime I try to get the "fastboot oem get_unlock_data" and get the error message "bootloader could not get unlock data".
I've tried almost 5 different adb tools, and drivers, I've read about 50+ post and tried all the commands , tried rsd but it wont flash gpt, maybe I haven't found the right post, but after several hours of research I running out of ideas, what can I try, what am I doing wrong?
Click to expand...
Click to collapse
Cesarisg said:
Sadly yes, I haven't figured out, I can't unlock bootloader, I can't flash a rom without unlocking bootloader, I've tried 5.1, 4.2.2 and 4.4.4, none of them work without unlocking bootloader, RSD Lite wont work, gets fail message, I'm really running out of ideas, still reading lots of threads from all over the world, even translating some foreign languages.
Click to expand...
Click to collapse
Salik Iqbal said:
Download this:
https://drive.google.com/open?id=0BxZBxVJDPGZjaUFlSmt4cDFLYW8
Make sure your battery is charge enough, and you are getting battery ok, unrar the folder, and flash the . xml from rsd lite, hope your device boot again.
Best of luck.
Click to expand...
Click to collapse
OH WOW, it worked, I tried dozens of gpt files and none of them worked, THANK YOU so much!!, saved my butt from buying a new phone, I will retire from flashing my moto x, stock rom for ever.
I am ARSH and Iive in india if some one is having brazzers membership p lzz give me for one day p lzz share with me my e-mail [email protected] plzzzzzz
No problem..
Cesarisg said:
OH WOW, it worked, I tried dozens of gpt files and none of them worked, THANK YOU so much!!, saved my butt from buying a new phone, I will retire from flashing my moto x, stock rom for ever.
Click to expand...
Click to collapse
I'm glad your phone is working again. Just curious, what were the issues you had with LOS 13 (ghost)?
I've been considering putting that on my phone, but would hold off or find another option if something won't work right. I'm still on stock 5.1.
mwaterbu said:
I'm glad your phone is working again. Just curious, what were the issues you had with LOS 13 (ghost)?
I've been considering putting that on my phone, but would hold off or find another option if something won't work right. I'm still on stock 5.1.
Click to expand...
Click to collapse
There was 2 main reasons why I had to go back to stock, the main one was that the OS would not let me uninstall any app, I tried everything I read online to try to fix it, even flashing the rom again, nothing work and the other reason was the phone app would not let me hear from the earpiece, it got fixed after getting back to 5.1 and many other bugs and sudden restarts, some of them might be cause by my phone or not, but since 5.1 everything is a lot more stable.
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
i have bough a x4 from ebay without warranty or anyting, the problem that i have. my phone says at the begining your device has loaded another operating system and then just a line of code says verity mode is set to disabled.
but after that the device starts normally, i have tried to lock the device again, but it doesn't work , maybe you have a solution for this problem :the model is XT1900-1 Type:M2997
the bootloader has been unlocked and to be honest relocking has no real benefits. leave it like it is, flash the latest stock image or a custom rom and ignore the bootscreen message.
cango123 said:
the bootloader has been unlocked and to be honest relocking has no real benefits. leave it like it is, flash the latest stock image or a custom rom and ignore the bootscreen message.
Click to expand...
Click to collapse
first, thank you for your response.
do you think, is that a motorola specific issue with corrupt bootloader ?
i guess the firmware of my device is a nougat, will it really help to get rid of a such blemish if i flash it??
doksch84 said:
first, thank you for your response.
do you think, is that a motorola specific issue with corrupt bootloader ?
i guess the firmware of my device is a nougat, will it really help to get rid of a such blemish if i flash it??
Click to expand...
Click to collapse
The message is normal for an unlocked bootloader - it is not corrupt. You cannot get rid of the message when the bootloader has been unlocked, even if it is relocked. Well, you can replace the boot image, but the ”verity" message will remain.
another problem
jhedfors said:
The message is normal for an unlocked bootloader - it is not corrupt. You cannot get rid of the message when the bootloader has been unlocked, even if it is relocked. Well, you can replace the boot image, but the ”verity" message will remain.
Click to expand...
Click to collapse
thank you guys, i just try to flash TWRP image, but it hangs with bootloader logs
getvar is-logical recove
getvar:has-slot:recovery
getvar_maxdown
Sending ....... in the command line? did anyone faces that problem ?