Develop Bugs

Think Ive messed My Phone Up :(

Hi all,
I foolishly use the Hermes unlocking software on my m5000. I can get into the phone but cant access the bootloader as the phone just re-sets - am I screwed?

Ive managed to get into bootloader and i am unlocking it using the correct software now
Is a rom update recommended too?
Regards,

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?

Rooting H815T Marshmallow

Hey all. So basically I recently purchased the H815T Australian optus model. It was initially on Lollipop but updated to MM & I need root so I can restore all my data from my previous device but seems I need to unlock the bootloader. Unfortunately it couldn't be done because the H815T isn't supported on the LG unlocking website. Is there another way to unlock the bootloader or rooting it? Please help guys, I really need to retrieve my data but can't do so till there is a method to root. Or would I have to downgrade to Lollipop & root? I'd immensely appreciate some assistance with this, cheers.

Stevo001457 said:
Hey all. So basically I recently purchased the H815T Australian optus model. It was initially on Lollipop but updated to MM & I need root so I can restore all my data from my previous device but seems I need to unlock the bootloader. Unfortunately it couldn't be done because the H815T isn't supported on the LG unlocking website. Is there another way to unlock the bootloader or rooting it? Please help guys, I really need to retrieve my data but can't do so till there is a method to root. Or would I have to downgrade to Lollipop & root? I'd immensely appreciate some assistance with this, cheers.
Click to expand...
Click to collapse
no bootloader unlock yet....
you need to be on LP.
but... you also need to know if you can downgrade. i for instance cant. there antirollback version you need to find out . if you can..

raptorddd said:
no bootloader unlock yet....
you need to be on LP.
but... you also need to know if you can downgrade. i for instance cant. there antirollback version you need to find out . if you can..
Click to expand...
Click to collapse
Thanks for your help. I really enjoy being on Marshmallow so don't really want to downgrade. Thankfully I got most of my whatsapp messages through google drive backup & most of the other apps did have some form of cloud storage. I'm gonna stick to MM till a rooting method does eventuate.

Change unlock bootloader allowed from NO to YES with root?

Hello,
I've recently obtained 2 new old stock Xperia Z1 Compact phones.
Both have their bootloader unlock allowed set to NO.
However, both are also running KitKat 4.2 with a really old kernel and the Easy Root Tool exploit should work to obtain root.
My question is whether the unlock allowed can then be forced to YES with the obtained root permissions and how?
I would like to flash LOS on both
Thanks,
Bobby

Not possible. There should be a HW way using testpoint

I am also trying to find a solution for this has anyone had any luck doing this with the S1 Tool and the bootloader unlock option using test point if yes please share here thanks.
I did find this https://forum.xda-developers.com/t/...ed-no-to-yes-is-now-finally-possible.4044091/

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.