Related
Hello, various posts say kenzo roms could be used on kate, but without modem files. Many users already tried flashing manually modified roms, bricking or having issues. Is there a full tutorial to how effectively:
- unlock bootloader (only unofficial way for what i understand...)
- root the phone (only flashing supersu via TWRP? what version of TWRP?)
- possibly modify existent kenzo roms to use them on kate (not only CM.... there are so many roms with various kernels too...are they working without problems on kate?)
so far i've been scouring the net for any possible guide, but there are really few to none specific for kate, and none answering clearly the previous questions....and i am sure i'm not alone as more and more people are buying right now the international version, and keep asking the same questions. Could somebody shed a light? thanks.
Following this thread. I bought international version and can't wait to flash CM
Inviato dal mio MI 2S utilizzando Tapatalk
You need to unlock bootloader and then flash TWRP. Once that's done all you need to do is flash CM13, CM13Firmware, Opengapps ARM64 and modem file for Kate (NON-HLOS from fastboot of MIUI8 Kate). Also can flash latest SuperSU for root.
To flash modem once CM13 is installed boot fastboot and then enter:
fastboot flash modem NON-HLOS.bin
Full guide
Is it possible to just install twrp and supersu and use miui roms?
http://forum.xda-developers.com/redmi-note-3/how-to/zcx-twrp-install-twrp-flash-supersu-t3462448
I wish there was a TWRP specifically for "kate" though. Because TWRP will think "kate" is "kenzo" for now.
is its possible to unlock the Kate version on the official way? Because in the Guide from Xiaomi ist the Point "You must on China Dev Firmware" but this versions isnt available for the kate version?
dadonali said:
is its possible to unlock the Kate version on the official way? Because in the Guide from Xiaomi ist the Point "You must on China Dev Firmware" but this versions isnt available for the kate version?
Click to expand...
Click to collapse
Until today, no one confirmed to have had success with official unlock. Even though it should be possible to unlock with the Mi Flash Unlock tool on every ROM, it is very likely that it can only reliable unlock when using a Chinese Developer ROM, which doesn't exist for Kate.
Most people are getting an error message in the above utility, saying that the MI account in the phone and the one used in the utility don't match, even if they do.
DPyro said:
Full guide
Click to expand...
Click to collapse
You found my guide.
Is there any good reason to wait for a reliable way to officially unlock the bootloader? Or any downside to go with the unofficial unlock method?
I got my phone yesterday and just found out today I actually had the Kate version. I don't really plan on going back to MIUI and from what I understand, the official unlock method would only make it easier to switch back to MIUI. Is that right?
(It's not my first time playing with custom ROMs, I have flashed multiple roms / kernels in the past but I always owned Nexus phones and it was quit dummy proof on these phones.)
BigBlarg said:
I don't really plan on going back to MIUI and from what I understand, the official unlock method would only make it easier to switch back to MIUI. Is that right?
Click to expand...
Click to collapse
That's my understanding, yes. Interestingly, when I had a Kenzo and unlocked it officially, the bootloader got relocked whenever I flashed something like CM. With Kate (unofficially unlocked), the bootloader wasn't relocked after flashing CM. In that sense, unlocking it via unofficial means may be advantageous.
Pumpino said:
That's my understanding, yes. Interestingly, when I had a Kenzo and unlocked it officially, the bootloader got relocked whenever I flashed something like CM. With Kate (unofficially unlocked), the bootloader was relocked after flashing CM. In that sense, unlocking it via unofficial means may be advantageous.
Click to expand...
Click to collapse
Thanks Pumpino!
I just followed your guide and successfully flashed CM 13 stable release without any issue.
It's only been a few minutes but everything seems to be working (much better than MIUI) so far.
BigBlarg said:
Thanks Pumpino!
I just followed your guide and successfully flashed CM 13 stable release without any issue.
Click to expand...
Click to collapse
You're welcome. I'm glad it went smoothly.
I've just edited my previous post, as "was" should have said "wasn't". ie. "With Kate (unofficially unlocked), the bootloader wasn't relocked after flashing CM."
Followed the guide and can't get the bootloader to unlock. Any ideas?
Downloaded the updated/modified emmc_appsboot.mbn, put it into the rom folder and flashed fine. Won't unlock.
BobSlob said:
Followed the guide and can't get the bootloader to unlock. Any ideas?
Downloaded the updated/modified emmc_appsboot.mbn, put it into the rom folder and flashed fine. Won't unlock.
Click to expand...
Click to collapse
I made a mistake at this part and it wouldn't allow me to unlock the bootloader. The guide to unlock the bootloader doesn't explicitly mention one important detail. In the screen where you have to allow USB debugging, you must also enable the option saying "Allow OEM unlock" or something like that. I didn't enable that option at first and in fastboot it would tell me I was not allowed to unlock the bootloader. So I had to reboot the phone normally, go through all the MIUI setup and finally re-enable USB Debugging and enable "Allow OEM unlock".
BigBlarg said:
I made a mistake at this part and it wouldn't allow me to unlock the bootloader. The guide to unlock the bootloader doesn't explicitly mention one important detail. In the screen where you have to allow USB debugging, you must also enable the option saying "Allow OEM unlock" or something like that. I didn't enable that option at first and in fastboot it would tell me I was not allowed to unlock the bootloader. So I had to reboot the phone normally, go through all the MIUI setup and finally re-enable USB Debugging and enable "Allow OEM unlock".
Click to expand...
Click to collapse
You sir are my hero! That was the issue. Many thanks.
One other question, when flashing the rom is it safe to put it on the SD card, or does it need to be on internal?
BigBlarg said:
The guide to unlock the bootloader doesn't explicitly mention one important detail. In the screen where you have to allow USB debugging, you must also enable the option saying "Allow OEM unlock".
Click to expand...
Click to collapse
Good point, although on mine, "Allow OEM Unlocking" was enabled by default. I used the developer ROM. Is it possible that it's not enabled by default on the stable ROM?
BobSlob said:
One other question, when flashing the rom is it safe to put it on the SD card, or does it need to be on internal?
Click to expand...
Click to collapse
Yes, totally safe. That's how I did it and that's also how I flashed multiple other Android devices using TWRP. Never had any issue putting the ROMs on the SD card.
Pumpino said:
Good point, although on mine, "Allow OEM Unlocking" was enabled by default. I used the developer ROM. Is it possible that it's not enabled by default on the stable ROM?
Click to expand...
Click to collapse
I did use the stable ROM, so that could explain it.
Alright, another problem. TWRP (tried a few versions) is unable to mount and wipe any partitions... any ideas? =P
Edit "Cofface TWRP Fix" as linked in the guide boot loops me
BobSlob said:
Alright, another problem. TWRP (tried a few versions) is unable to mount and wipe any partitions... any ideas? =P
Edit "Cofface TWRP Fix" as linked in the guide boot loops me
Click to expand...
Click to collapse
Did you try flashing first the Safe TWRP?
Seems the standard TWRP worked fine, disaster avoided
On the latest t mobile software, dev mode enabled, but I dont see "OEM UNLOCK" anywhere...does anyone have that option on their note 8?
thanks
wase4711 said:
On the latest t mobile software, dev mode enabled, but I dont see "OEM UNLOCK" anywhere...does anyone have that option on their note 8?
thanks
Click to expand...
Click to collapse
I think you use that TMO device unlock app.
I thought that was just for carrier unlock, NOT OEM unlock...have you used that app?
thanks
wase4711 said:
I thought that was just for carrier unlock, NOT OEM unlock...have you used that app?
thanks
Click to expand...
Click to collapse
No, I disabled it. Been with TMO too long, I'm not going anywhere and neither are they. Thanks for teaching me the difference, lol! This bootloader is locked.
there are a few different "locks" to deal with on this phone; the bootloader, which is currently locked, carrier lock, meaning you are locked to tmobile, and the OEM unlock, which allows you to flash roms, both stock and custom, assuming you have an unlocked boot-loader
On most other phones, in the developer options, there is a OEM Unlock entry you activate if you plan on flashing anything...
wase4711 said:
there are a few different "locks" to deal with on this phone; the bootloader, which is currently locked, carrier lock, meaning you are locked to tmobile, and the OEM unlock, which allows you to flash roms, both stock and custom, assuming you have an unlocked boot-loader
On most other phones, in the developer options, there is a OEM Unlock entry you activate if you plan on flashing anything...
Click to expand...
Click to collapse
The OEM Unlock option doesn't appear until 7 days after the device was first booted on the Exynos version. That might not be the case with your version because the bootloader is locked so the OEM Unlock toggle is redundant.
Have a read through this thread:
https://forum.xda-developers.com/galaxy-note-8/help/info-note-8-exynos-n950f-fd-oem-unlock-t3673140
I've had many phones with locked bootloaders in the past where the OEM unlock appeared in the dev options, so unless this is something new with the note 8. im not sure why its not there..
wase4711 said:
I've had many phones with locked bootloaders in the past where the OEM unlock appeared in the dev options, so unless this is something new with the note 8. im not sure why its not there..
Click to expand...
Click to collapse
All the OEM unlock toggle does is allow you to flash a custom recovery so you can then flash custom ROMs only if the the bootloader is unlocked. If the bootloader is locked like on US snapdragon N8s having the toggle is pointless.
If you check out the thread linked above you'll see that a bunch of people with exynos versions that do have unlocked boot loaders are missing the toggle which later appears & disappears. No one knows why yet, all just speculation.
The N8 is the first to have this happen. What a big headache. Hopefully they figure it out. I'm one of the lucky with an exynos N8 without that issue.
yeah, its not a big deal, especially since there is no way to unlock this bootloader at this point anyways...weird that it comes on and off on the Exynos though..
Torquemada288 said:
The OEM Unlock option doesn't appear until 7 days after the device was first booted on the Exynos version. That might not be the case with your version because the bootloader is locked so the OEM Unlock toggle is redundant.
Have a read through this thread:
https://forum.xda-developers.com/galaxy-note-8/help/info-note-8-exynos-n950f-fd-oem-unlock-t3673140
Click to expand...
Click to collapse
Correct, for our t mobile USA ones, we will never get that OEM Unlock option in any amount of days.
Well if we can. Get root we can oem toggle
smiley45 said:
Well if we can. Get root we can oem toggle
Click to expand...
Click to collapse
We already have a root, it just wasn't released yet and it seems to be the same as S8, so with similar disadvantages. Expect to be out any day now.
smiley45 said:
Well if we can. Get root we can oem toggle
Click to expand...
Click to collapse
Even if you get the OEM unlock toggle to appear it doesn't mean anything. If you have a locked bootloader the OEM unlock won't unlock it. OEM unlock is just a safety switch.
shouren04 said:
Even if you get the OEM unlock toggle to appear it doesn't mean anything. If you have a locked bootloader the OEM unlock won't unlock it. OEM unlock is just a safety switch.
Click to expand...
Click to collapse
Yes that maybe so.. but I will feel better when I add that option to my note 8... I'm just waiting on root and it on form there
Sent from my SM-N950U1 using Tapatalk
Oem needs to be unlocked before u can us cf autoroot or any other means of root I have j7 metro no oem unlock option tried to use Odin and cf auto root it failed because the bootloader is locked and can't be unlocked. I know this is for the n8 but I seem to be suffering from the same problem.
Lost without root
XxdeadhatexX said:
Oem needs to be unlocked before u can us cf autoroot or any other means of root I have j7 metro no oem unlock option tried to use Odin and cf auto root it failed because the bootloader is locked and can't be unlocked. I know this is for the n8 but I seem to be suffering from the same problem.
Lost without root
Click to expand...
Click to collapse
Does having an engineering bootloader help?
How do I test if the bootloader is unlocked?
Sent from my SM-G892U using Tapatalk
reukiodo said:
Does having an engineering bootloader help?
How do I test if the bootloader is unlocked?
Sent from my SM-G892U using Tapatalk
Click to expand...
Click to collapse
Its not plain and simple.
sent from my Pixel 2 XL or Note FE
so i cant root or put twrp on my j727U ? SEEN PEOPLE DO IT WITH J727p so why not the U ? no oem toggle on a galaxy how is this, should all come together and never buy phones from a company that goes against what customers want.
so i cant root or put twrp recovery on my galaxy j727U ? ? how has a phone tech not beat this by now even without oem toggle , it should still be beat by now.. this is why i liked htc cause they unlock bootloader for you and allow it on there own page, anyone wanna trade a htc for a new galaxy j7 ?
lol i think this thread needs to be closed
Yes there is an OEM unlock option. I know because I discovered It! Simply flash the K2 combination file, when factory binary loads go into the left hand screen, with apps. Click on the settings icon, then enable dev options the usual way. OEM unlock should be there. You may need to toggle it off and on a few times before you get the popup security message.
It makes a change in the system as it should. If you do a factory reset, then reload the factory binary, you'll see that Dev Options are already enabled (saved from last time you unlocked) AND OEM will already be toggled. This means that the unlock sticks!
So there you go. It even changes the OEM line in the .prop.... that being said...
DO NOT TRY TO FLASH TWRP AFTER DOING THIS!!!
(I already tried, the secure boot still is in effect, and you'll have a softbrick until you can re Odin your recovery. )
The OEM unlock may be one part of this, but there's more. Hopefully we are making progress toward the goal of a bootloader unlock!
I cannot unlock my bootloader for some reason now. I had applied for permission around a year and a half back, I got the permissions, unlocked the bootloader and flashed a lot of ROMS. When I flashed MIUI through fastboot, the bootloader got locked again. Now I want to try some ROMS, but I cannot unlock the bootloader. It goes all the way till 99 percentage and it then gives the message 'Current Account cannot unlock this device'. I have permissions and everything because when I go to the mi unlock site I'm directed to the download page, not to the application page. Also, when I try to bind the account to my phone in Mi Unlock status in developer options, it keeps saying 'Couldnt Verify, wait a minute or two and try again'. I've waited for a day and it still doesn't work. I only have one sim card in my phone(the one which I used to get permission) but still it keeps saying the same message again and again.
Please help!
Regards.
Hello. Though I never had the problem (was on NOS rom before I messed something and had to flash miui rom via fastboot and relocked bl, I easily reunlock again using official method like the first time).
Before unlocking, make sure your phone are locked by using cmd "fastboot oem device info" or something like that I forgot. And your phone developer option have allow oem unlocking ticked on. Make sure your phone mi account logged in and of course matched with the one on your pc/laptop. Have good usb cable, drivers, and stable internet. Also you can try unlocking using another version of miui rom (the one you used for the first unlocking).
Don't know if those helps though.
I had the same problem for almost 2 months, asked on the miui forum and nobody helped so i just unlocked it unofficially, works great! On RR N now!
Same
I have the same problem, and also I know a lot of people with it. It seems that xiaomi has banned the unlock tool I don't know why...
diontrevor said:
I cannot unlock my bootloader for some reason now. I had applied for permission around a year and a half back, I got the permissions, unlocked the bootloader and flashed a lot of ROMS. When I flashed MIUI through fastboot, the bootloader got locked again. Now I want to try some ROMS, but I cannot unlock the bootloader. It goes all the way till 99 percentage and it then gives the message 'Current Account cannot unlock this device'. I have permissions and everything because when I go to the mi unlock site I'm directed to the download page, not to the application page. Also, when I try to bind the account to my phone in Mi Unlock status in developer options, it keeps saying 'Couldnt Verify, wait a minute or two and try again'. I've waited for a day and it still doesn't work. I only have one sim card in my phone(the one which I used to get permission) but still it keeps saying the same message again and again.
Please help!
Regards.
Click to expand...
Click to collapse
Did you manage to unlock the bootloader? i have the exact same situation. unlocked my device 1 year ago, flashed miui fastboot rom and now unable to unlock . same error .
shubham dudeja said:
Did you manage to unlock the bootloader? i have the exact same situation. unlocked my device 1 year ago, flashed miui fastboot rom and now unable to unlock . same error .
Click to expand...
Click to collapse
I managed to unlock it unofficially. Was tired of just trying and trying everyday
diontrevor said:
I managed to unlock it unofficially. Was tired of just trying and trying everyday
Click to expand...
Click to collapse
I am facing same issue, could you please share unofficial method for 9.2.4.0
I flashed beta version of miui 9 by fastboot, i didnt faced such problem, i simply just logged on to the account on which i took permission and unlocked the bootloader
MOHD SOHAIL AHMED said:
I flashed beta version of miui 9 by fastboot, i didnt faced such problem, i simply just logged on to the account on which i took permission and unlocked the bootloader
Click to expand...
Click to collapse
Yeah its not an issue with all devices, I do have colleagues who have managed to unlock it officially, but still its a problem for a lot of people.
I have the exact same problem. Stuck at 99 when trying to re unlock, on both miui 8 and 9. I didnt bother trying to unlock with developer roms, just used the method to flash twrp without bl unlock. All good now on nos 8.
I'm happy with flash twrp only without unlocking bootloader since I got root access anyway
Why are you people trying to unlock bootloader when it's not even necessary on our phone? Just look on the forums a little bit more and you won't struggle anymore trying to unlock.
asakurato said:
Why are you people trying to unlock bootloader when it's not even necessary on our phone? Just look on the forums a little bit more and you won't struggle anymore trying to unlock.
Click to expand...
Click to collapse
by the way, can I flash custom ROM with my current twrp ?
I mean, I do have twrp installed without unlocking bootloader.
rs168 said:
by the way, can I flash custom ROM with my current twrp ?
I mean, I do have twrp installed without unlocking bootloader.
Click to expand...
Click to collapse
Yes you can. I have NOS 8.1 installed right now.
diontrevor said:
I cannot unlock my bootloader for some reason now. I had applied for permission around a year and a half back, I got the permissions, unlocked the bootloader and flashed a lot of ROMS. When I flashed MIUI through fastboot, the bootloader got locked again. Now I want to try some ROMS, but I cannot unlock the bootloader. It goes all the way till 99 percentage and it then gives the message 'Current Account cannot unlock this device'. I have permissions and everything because when I go to the mi unlock site I'm directed to the download page, not to the application page. Also, when I try to bind the account to my phone in Mi Unlock status in developer options, it keeps saying 'Couldnt Verify, wait a minute or two and try again'. I've waited for a day and it still doesn't work. I only have one sim card in my phone(the one which I used to get permission) but still it keeps saying the same message again and again.
Please help!
Regards.
Click to expand...
Click to collapse
Hi , just manage to add account and device without errors on mi note 3 by using SoloVpn app from playstore set to China .
Now i am waiting 72 hour's to proceed unlocking.
Apparently the error on add account and device starting with 80xxx and some Chinese text it's blocking the unlocking tool.
Sent from my Mi Note 3 using Tapatalk
asakurato said:
Why are you people trying to unlock bootloader when it's not even necessary on our phone? Just look on the forums a little bit more and you won't struggle anymore trying to unlock.
Click to expand...
Click to collapse
Tried everything and anything available on MIUI Forum but couldn't unlock. same error coming again and again.
redmi note 3 pro
how can i get root access without unlocking bootloader and twrp recovery
[email protected] said:
Tried everything and anything available on MIUI Forum but couldn't unlock. same error coming again and again.
Click to expand...
Click to collapse
Use this https://forum.xda-developers.com/redmi-note-3/how-to/kate-guide-install-lineage-os-locked-t3546154
Hello Guys, my device got locked after updating my device from miui 8 to miui 9 through a OTA update, i flashed fastboot ROM but it didn't work, I followed a temperory solution not second storage but a solution through ADB drivers ( developers tools ) i formatted through recovery and went to welcome settings from there clicked on terms and conditions and went to Google app searched for settings - created second space then went to activate developers settings and clicked on bebugging on etc , then went back to first storage and activated developers settings and switched OEM unlock , usb debugging on etc than I connected my device to pc, before that I installed abd drivers , from computer I opened CMD and typed few codes like device is connected or not than removed find devices.apk using code by this step I'm able to use my device but I cannot restart or reboot or switch off my device , if I do so it will go to bootloop. By using another code find me device APK will be saved on SD card, a developer said install it as user app ( it can't be installed as user or system app it just installs the app ) and bootloop problem will be solved but when I install it then again device got locked immediately after the install.
So I'm looking for a permanent solution for this, please help me. Thank you
If the device is locked. just unlock it officialy already. and u cannot just remove find device apk without root. u just disabled it.
Need proper answer, waiting for help
I didn't get, What U meant by Device got locked. Few things that can be done, Unlock Bootloader and flash MiUi Fastboot ROM or use any other custom ROMs. Unlock bootloader via Official methods or u can try unofficial methods too.
hoshang.govil12 said:
I didn't get, What U meant by Device got locked. Few things that can be done, Unlock Bootloader and flash MiUi Fastboot ROM or use any other custom ROMs. Unlock bootloader via Official methods or u can try unofficial methods too.
Click to expand...
Click to collapse
I mean my device got locked just like iCloud lock , I'm not able to use the device, I found temperory way of using it and wanted a permanent solution, yes I have flashed fastboot ROM but still device got locked after booting up.
johnstevenjs said:
I mean my device got locked just like iCloud lock , I'm not able to use the device, I found temperory way of using it and wanted a permanent solution, yes I have flashed fastboot ROM but still device got locked after booting up.
Click to expand...
Click to collapse
Unlock bootloader and use any Custom ROMs.
hoshang.govil12 said:
Unlock bootloader and use any Custom ROMs.
Click to expand...
Click to collapse
Bro I'm on miui 9 , is any unofficial way of unlocking bootloader for miui 9 ?
I donno, if there is any Unofficial way to Unlock Bootloader in MiUi9.
Hello,
After receiving my new Motorola x40 I realized that I wasn't able to use my GooglePay nor did it have other language support. So I decided to unlock my x40 bootloader via https://en-us.support.motorola.com/app/standalone/bootloader/unlock-your- device-a
It all worked. I managed to install a global rom with all the google apps and extra language support.
However, Global rom didn't allow my GooglePlay to use my cards or backup via googleOne since the flashing was unlocked. So I went to fastboot to " fastboot flashing lock". After which my cards were able to work.
After few days of using global rom I decided to go back to chinese one since I found it a bit easier to navigate.
So when I decided to go back to my old chinese rom, in "Developer Options" OEM unlocking says "Connect to the internet or contact your operator" and it is greyed out.
I tried using " fastboot flashing/oem unlock" in fastboot however it tells me that i need to unlock it in " developer options " first.
My phone has already been connected to wifi for around 90 hours on a Global rom And around a week before I transitioned from Chinese room over to global rom.
How long do I need to be connected to the internet or what operator do I need to contact to unlock my OEM again? Or maybe there is another way to unlock OEM without waiting?
Things I tried and failed:
1) Factory reset
2) Wipe/Cache reset via recovery​3) "fastboot flashing/oem unlock" via bootloader
Global rom used: https://mirrors.lolinet.com/firmware/motorola/rtwo/official/RETGB/
Have same problem.
cryptm said:
Have same problem.
Click to expand...
Click to collapse
How many days are you in this state? maybe you are closer to 7 days than I am
The toggle to unlock the bootloader is now enabled for me after 8 days. I have the Edge 40 Pro.
mine too, didn't look before, i own mine since 14 april
Ok so the theory is that once you get a global rom and "fastboot oem lock", it will act like new phone and will only unlock after 7-8 days. Guess will have to wait to test this theory out.
zeakey said:
Ok so the theory is that once you get a global rom and "fastboot oem lock", it will act like new phone and will only unlock after 7-8 days. Guess will have to wait to test this theory out.
Click to expand...
Click to collapse
Any update whether you can toggle OEM Unlocking?
Also, as someone who have been using Moto phones from China for years, CN ROM is way way way better the Global ROM when it comes to features and software updates. One useful feature is the built in Motorola Wallet app where I can use my phone as keycard and transpo card.
ijuanp03 said:
Any update whether you can toggle OEM Unlocking?
Also, as someone who have been using Moto phones from China for years, CN ROM is way way way better the Global ROM when it comes to features and software updates. One useful feature is the built in Motorola Wallet app where I can use my phone as keycard and transpo card.
Click to expand...
Click to collapse
Nope. Still not unlocked. Waiting for new firmware updates. So far EU region didn't get any.
zeakey said:
Nope. Still not unlocked. Waiting for new firmware updates. So far EU region didn't get any.
Click to expand...
Click to collapse
Supposedly OTA updates are being released, some can update successfully, others can't. Keep us updated if you're able to successfully update.
JustHereForNow said:
Supposedly OTA updates are being released, some can update successfully, others can't. Keep us updated if you're able to successfully update.
Click to expand...
Click to collapse
I did update from from 20-15 to 20-28 version. OEM still didn't get unlocked
zeakey said:
I did update from from 20-15 to 20-28 version. OEM still didn't get unlocked
Click to expand...
Click to collapse
I'm assuming it's a Motorola issue. I'm assuming maybe even real Edge 40 Pro devices can't unlock yet? Honestly if OTA works and so do all features (banking, 5g, etc) then I have no problem doing the conversion.
zeakey said:
I did update from from 20-15 to 20-28 version. OEM still didn't get unlocked
Click to expand...
Click to collapse
Does this mean you were able to update to 20-28 even with the locked bootloader (and locked OEM)?
Zechosenjuan said:
Does this mean you were able to update to 20-28 even with the locked bootloader (and locked OEM)?
Click to expand...
Click to collapse
I also updated without problem with bootloader closed and oem blocked and everything fine in the same way I solved the vpn and everything at 100 on the computer
ziggmax said:
I also updated without problem with bootloader closed and oem blocked and everything fine in the same way I solved the vpn and everything at 100 on the computer
Click to expand...
Click to collapse
What tools\steps did you take to update while bootloader and OEM are locked?
Zechosenjuan said:
What tools\steps did you take to update while bootloader and OEM are locked?
Click to expand...
Click to collapse
Using TinyFastbootScript flashing the reteu rom But when I installed it I blocked the bootloader thinking that it could be opened again to my surprise I could no longer activate the box so I have to wait and see if with any update I can go back To activate that option To activate that option
ziggmax said:
Using TinyFastbootScript flashing the reteu rom But when I installed it I blocked the bootloader thinking that it could be opened again to my surprise I could no longer activate the box so I have to wait and see if with any update I can go back To activate that option To activate that option
Click to expand...
Click to collapse
You won't be able to unlock the bootloader twice, impossible it's done by design by motorola.
You can only unlock your bootloader once
jody2k said:
You won't be able to unlock the bootloader twice, impossible it's done by design by motorola.
You can only unlock your bootloader once
Click to expand...
Click to collapse
does this mean the phone that went through unlock\lock of the BL will never get a firmware update (whether OTA or manual)?
Zechosenjuan said:
does this mean the phone that went through unlock\lock of the BL will never get a firmware update (whether OTA or manual)?
Click to expand...
Click to collapse
It's possible that we won't get OTA, only will know for sure in the future, i'm in the same situation.
But you can always manually update your firmware with rescue tool or through ADB as long it's the official firmware. You don't need a unlocked bootloader for that
jody2k said:
It's possible that we won't get OTA, only will know for sure in the future, i'm in the same situation.
But you can always manually update your firmware with rescue tool or through ADB as long it's the official firmware. You don't need a unlocked bootloader for that
Click to expand...
Click to collapse
This gives hope. Can you link me to flashing through adb? So far have only seen fastboot and magisk.
Zechosenjuan said:
This gives hope. Can you link me to flashing through adb? So far have only seen fastboot and magisk.
Click to expand...
Click to collapse
I think this method would work:
I screwed up...moto X40 bricked / Any EDL mode available?
Hi guys sadly I completely softbricked my motorola X40 phone i'm a idiot. I flashed to a wrong firmware file (edge 30 pro) and re-locked bootloader then found it phone doesn't properly boot anymore. I can boot it in fastboot mode but flashing in...
forum.xda-developers.com
But I think this will erase all your data so it's not a real "upgrade firmware" method
I also found out there is an "software update" in the lenovo rescue tool
Maybe it's worth the shot to try this out too, but for me it's says I have the latest firmware already (which is correct) so I can't test it out right now.