Question system locked and flash locked - Moto G40 / G60

system was blocked and I can't install a rom in any way because the flash is blocked and to unlock you have to turn on the cell does anyone have a solution? (MOTOG60)

Can you elaborate the issue how was the system blocked? Which twrp did you use?

Related

[Q] Do I need to relock bootloader before update?

Hi,
I've just got the latest update. I'm on a rooted stock rom with unlocked bootloader and TWRP. I know I have to return to stock recovery before updating, but do I need to relock?
If not, will I still have root after updating? will the bootloader stay unlocked?
Thanks!
Yes bootloader can stay unlocked and will be unlocked after the update, root will be automatically be removed. You can reroot afterwards
Thanks for your quick reply.
I've also noticed something wierd with my keyboards (stock and swiftkey3) - When pressing '7' through the digit keyboard or longpress, in some apps the app crashes and restarts. can't punch in a password for my health care!
any ideas?
If you are on stock rom....no don't have an idea at the moment

Any way to unlock bootloader on MM?

Is there a workaround for unlocking the bootloader on marshmallow or is it in any way possible to revert back to lollipop? Really want to unlock it's bootloader for flashing a rom and pushing apps like whatsapp with adb.
I want this too, but unable to find any clue.
Same problem. Anybody find a solution?

[Q] Encrypted data

Hi guys,
I just got Xperia M from my friend to install on it some custom ROM and etc. but there is encrypted data and I cant do nothing with it.
I tried repairing software with Xperia Companion, but I get UEUpdateFailed UE_2005 error and cant get past it. I tried also to enter recovery, but there's no recovery. Dont know what to do, cuz I need to check if I can unlock it.
Thanks in advance
Hi,
I can't figure out what exactly is giving you trouble, so you might want to be a little more specific. So I don't know if this is helpful for you, but:
First, there is no stock recovery on the Xperia M. As long as you don't flash a recovery on it, there is none. So you won't be able to enter that.
Next thing, Xperia Companion is a software to update or repair the stock ROM. So you won't be able to flash a custom ROM with that.
Just backup the data (if the data is encrypted and still needed, you didn't say what exactly is encrypted) and use flashtool to flash a ROM.
I'm not sure what you mean with checking if you can unlock it. The encryption? The boot loader? SIM lock? If you can unlock the boot loader (and SIM lock status too) you can check with the service number, so no need to flash it for that. Or is the device not even starting up because of the encryption?
So I dont really know if I can unlock bootloader of that phone cuz I need to "you should confirm that it is possible to unlock the boot loader of your device by checking the service menu. In your device, open the dialler and enter *#*#7378423#*#* to access the service menu" but I cant cuz of encrypted data. When phone boots up it ask me for password, but I dont know it. When I tried to use repair function to flash stock software and then the encryption would be gone it gived me error mentioned before. I dont know any recoveries or Roms that I can flash on locked bootloader. Any sugestions ? I want to flash newest Lineage OS at the end.
Is it possible that the boot loader is already unlocked? PC Companion is not working with unlocked boot loader.
You can also use flash tool to check if the boot loader is unlocked or not.
how to check that in flashtool ?
You switch off your phone, hold the volume down key, connect the usb cable, then it should be recognized in flash tool. Then you click on the lock. It should tell you the state of your boot loader somewhere there.

CustomROM possible without root and (re)locked bootloader?

Hi,
Long story short:
is it possible to install customROM without root and to (re)lock the bootloader, and are there experiences with a similar situation where Apps check for closed bootloader and root (and stop working if detected)?
=> Goal: activate WiFi-Calling as my provider tuned down 2G-transmitpower due to the 5G-advances (without having enough 3G-coverage to make calls on UMTS-net)... BUT: I'm using two banks; one uses a PhotoTAN-App, that stops working if it detects an open Bootloader, the other Bank-App checks for Root & open Bootloader, and likewise stops working if detected. I have no idea about the PhotoTAN and Magisk, but the 2nd bank confirmed they checked rooted devices with Magisk, and that it does not work with it....
Thus, if I go for a CustomROM, I need to be sure that I can run it unrooted and with a locked bootloader....
Is there a way to install a CustomROM on the 5X with (re)locked bootloader and without root?
(or, if not possible: is there a way I can activate WiFi-Calling on StockROM if said one does not have the Carrier-Entitlements?)
Thanks for the help
@theunlucky: you don't need root to flash a custom ROM, only an unlocked bootloader. IMO you can lock it after flashing ROM.
rp158 said:
@theunlucky: you don't need root to flash a custom ROM, only an unlocked bootloader. IMO you can lock it after flashing ROM.
Click to expand...
Click to collapse
Are you sure about locking the bootloader after flashing a CustomROM? I've read several threads now, and it seems a locked BL only works with StockROM?
Not sure, therefore IMO IMO a locked BL prevents flashing CustomROM, not running. Try. If it doesn't work, you unlock BL again (triggers factory reset). In the worst case you've to flash latest firmware for a clean base..

Question Carrier ROM not updating since miui 12.5.5. Is there anything I can do to fix this?

Hi, my carrier purchased 'Lisa' came with its ROM showing as version RKOEUBY.
My carrier isn't keeping up with updates so was wondering if I can just flash the ROM RKOEUXM without unlocking the bootloader?
I have my banking apps etc on this phone so am reluctant to unlock the bootloader unless absolutely necessary.
If anyone else has found an easy way to solve this would be grateful for your feedback.
Many thanks
rockyrobin said:
Hi, my carrier purchased 'Lisa' came with its ROM showing as version RKOEUBY.
My carrier isn't keeping up with updates so was wondering if I can just flash the ROM RKOEUXM without unlocking the bootloader?
I have my banking apps etc on this phone so am reluctant to unlock the bootloader unless absolutely necessary.
If anyone else has found an easy way to solve this would be grateful for your feedback.
Many thanks
Click to expand...
Click to collapse
Hi !
The best way is to download the zip of your European ROM from the Xiaomi site and try to install it from the update utility in your phone's settings. If that doesn't work, you'll have to unlock your bootloader, install the ROM you want with the flash utility, and choose the relock option before the install starts. Then you will be on an official Xiaomi ROM, with your bootloader locked and you will have updates from Xiaomi and no longer from your operator.
Bill
Hi,
I confirm that manually flashing the European ROM does not work (in my case at least), so I am stuck on MIUI 12.5.6 with RKOEUSF ROM.
If anyone finds a way to upgrade to the official version without unlocking the bootloader, and therefore not breaking the warranty, I would be grateful if you could share it.
Thanks
Hi !
From the moment you want to install a new ROM, you have no choice but to unlock your bootloader. You can then reblock it. Afterwards, I don't know if the warranty is impacted because you go through the official unlocking from Xiaomi.
Bill
Thanks Bill,
I've just tried flashing the zip of my ROM and the phone just quits the update after a long pause, saying that it cannot verify update.
Guess I'll have to unlock the bootloader. There's plenty of info about how to do this, but I've noticed a number of people complaining about the flash process.
When they apply the update, at the end they get an error message. The only way they get round this is with an edit of the settings of miflash.
Is this something I need to worry about?
Just been reading about these errors and it appears that they are caused by the path to the ROM file having too many characters.
Placing the ROM file in your C: folder solves this.

Categories

Resources