I’ve backed up with TWRP but have done something wrong as I can’t boot the phone. I see ID: bad key.
I can access fastboot with [downvolume power]. START doesn’t boot the phone but I can see the backup in RECOVERY MODE. I restored the backup but still can’t boot.
What did I do wrong? How can I fix things?
Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services
must have gone something wrong on the restore. There’s not much online as to ‘bad key’. I’d flash every partition but(!) the USERDATA from /e/ install image and stock firmware.
The problem occurred prior to restoring. I restored to try to fix the problem.
I haven’t /e/ installed. I was trying to backup prior to installing /e/. I have no USERDATA I wish to retain.
I’m a touch uncertain what you mean by ‘flash every partition.’ I just restored and was told it was successful but the phone still won’t reboot. It locks on the ‘Your phone has been unlocked and can’t be trusted’ screen.
ah ok, got it. Do you have access to stockrom images of your device? lolinet has some until 2019. There is Motorola windows software that can do the same from official sources. Pick the appropriate region of your device and you can go back to a state where things work.
I understand why you’d want to image the partitions yourself in twrp (and not rely on external stockrom images).
About Lenovo (Motorola) Rescue and Smart Assistant (RSA):
It has an evil feature where you must login to Live/Gmail and other choices or you can’t use the tool, at least I couldn’t find a way. Once you allow it it collects all your contacts and reads email.
Try to use an account that you don’t use often or create an empty account. I was off my game and logged into a Hotmail account I sometime use.
Luckily Hotmail/Live mail notifies you and allows you to delete the apps access, but damage may have been done. Just a heads up.
It’s called Rescue and Smart Assistant RAS, use cation.
I believe I found what you refer to at https://motostockrom.com/motorola-moto-g5-xt1676. I’m a touch confused why restoring my backup doesn’t do the trick but such a backup apparently isn’t as complete as I assumed.
Regardless, I can’t see my phone using ‘adb devices’ unless I bring up Recovery Mode in fastboot. It then lists as recovery in ‘List of attached devices.’ Is it OK to proceed at that point?
I wish I knew what the heck I did to produce ID: bad kay. My backup apparently succeeded but I was having trouble transferring it to my PC via USB.
as to the Moto G5 link - there’s also https://mirrors-obs-2.lolinet.com/firmware/lenomola/2017/cedric/ (see region-coded folders).
From what I understood on ‘bad key’ - (never consciously registered reading ‘bad key’, if you still can, maybe post a photo of the screen for posterity) - it’s just the unlocked state warning partition keys not to validate (of the boot-verity sort). You’d boot right past the screen if the next partition is bootable. So I guess in the process of imaging the partition something got altered? pure speculation, I’d need see get into this myself.
Forgive me but this is new to me and I’ve shown a real talent for messing this up. Let me try again as there are so dang many files. These are acceptable?
https://mirrors-obs-2.lolinet.com/firmware/lenomola/2017/cedric/official/RETRU/XT1676_CEDRIC_RETRU_7.0_NPPS25.137-93-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
https://mirrors-obs-2.lolinet.com/firmware/lenomola/2017/cedric/official/RETEU/XT1676_CEDRIC_RETEU_DS_8.1.0_OPP28.85-19-4-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
And I’m assuming it’s too easy to flash only https://mirrors-obs-2.lolinet.com/firmware/lenomola/2017/cedric/blankflash/blankflash_from_OPQ28.85-8.zip.
are you in those markets? RETEU - retail eu, RETRU retail russia - 7.0 / 8.1 for Android version, take the latest. Make sure by reading either the fastboot screen or the printed label behind the battery that you got the right XT model number.
An update … I flashed the Moto 8.1 firmware and can now boot the phone. However, I still see ‘bad key.’ Perhaps ‘bad key’ is a red herring. When booting to Fastboot I see N/A.