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
hi,i have a mate 10 pro with stock android 8, unlocked bootloader by flashing unlock key via fastboot. frp unlocked.
stock recovery. not rooted.
bla-l29 c432 131
when i start my mate 10 it says "device cannot be trusted".. before it boots as normal.
Can i lock\relock bootloader and make it go away??
tried:
fastboot oem relock "unlock code"
fastboot oem lock "unlock code"
and it came password failed :\
usb debugging: on
oem unlock: on
flash oem info of sorts?
try: fastboot reboot oem relock?
if i switch oem unlock to off again in developers option and then use commands??
Thanks for help!
FiXed, used adb interface drivers, i tried several until i found 1 that worked
Hi, with mate 8 and mate 9 when you flash officiel firmware he relock bootloader, try this or you can buy credit (4) for relock with DC unlocker.
So... tell me please why you unlock your bootloader if you don't flash twrp or root ??
Dont buy any credit. I Will provide you The solution today.
---------- Post added at 05:49 AM ---------- Previous post was at 05:03 AM ----------
614Emil said:
hi,i have a mate 10 pro with stock android 8, unlocked bootloader by flashing unlock key via fastboot. frp unlocked.
stock recovery. not rooted.
bla-l29 c432 131
Click to expand...
Click to collapse
Use this tutorial (flash update)
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
In short:
- download your full firmware (3 files)
- in repack part chose to lock bootloader
- ota part
End of story.
badmania98 said:
Dont buy any credit. I Will provide you The solution today.
---------- Post added at 05:49 AM ---------- Previous post was at 05:03 AM ----------
Use this tutorial (flash update)
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
In short:
- download your full firmware (3 files)
- in repack part chose to lock bootloader
- ota part
End of story.
Click to expand...
Click to collapse
Thanks, I will try this later and let you know how it goes!
If you only want to relocked your bootloader just use the HWOTA8_Mate 10 tool from the link bellow.
download the tool > go to lock directory > use relock.bat
you'll need to provide your bootloader unlock code to re-locked it.
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
Lykeul said:
Hi, with mate 8 and mate 9 when you flash officiel firmware he relock bootloader, try this or you can buy credit (4) for relock with DC unlocker.
So... tell me please why you unlock your bootloader if you don't flash twrp or root ??
Click to expand...
Click to collapse
hi aok ill look into that plan was getting viper or some good sound mod, but it seems its not finished developed for Oreo 8.0
Buran79 said:
If you only want to relocked your bootloader just use the HWOTA8_Mate 10 tool from the link bellow.
download the tool > go to lock directory > use relock.bat
you'll need to provide your bootloader unlock code to re-locked it.
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
Click to expand...
Click to collapse
it did not work :\
614Emil said:
it did not work :\
Click to expand...
Click to collapse
did you try info.bat? does it restart to fastboot mode so you can see the bootloader status?
what method or tool did you use to unlock de bootloader?
Buran79 said:
did you try info.bat? does it restart to fastboot mode so you can see the bootloader status?
what method or tool did you use to unlock de bootloader?
Click to expand...
Click to collapse
i have to set it in fastboot manually then it shows:
Lock state info:
FB LockState: LOCKED
USER LockState: UNLOCKED
Current build number:
BLA-L29 8.0.0.131(C432)
Product model:
BLA-L29
to unlock i used cmd and -fastboot oem unlock "code"-
Buran79 said:
If you only want to relocked your bootloader just use the HWOTA8_Mate 10 tool from the link bellow.
download the tool > go to lock directory > use relock.bat
you'll need to provide your bootloader unlock code to re-locked it.
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
Click to expand...
Click to collapse
hi^^ did not work either, after i put in the "code" in the cmd window,i can see Failed before the cmd window quickly dissapears
614Emil said:
hi^^ did not work either, after i put in the "code" in the cmd window,i can see Failed before the cmd window quickly dissapears
Click to expand...
Click to collapse
I think you are not having proper mate 10 pro windows drivers. Try following the HWOTA_mate10 guide about preparation, there is a registry fix and you should uninstall HiCare for proper device recognition
Buran79 said:
I think you are not having proper mate 10 pro windows drivers. Try following the HWOTA_mate10 guide about preparation, there is a registry fix and you should uninstall HiCare for proper device recognition
Click to expand...
Click to collapse
Hi, i just started thinking about that, just to be sure since i did not get mtp folder in my computer anymore(win 10)
i switched to my laptop win 8.1,
installed the adb driver manually as adb composite interface in normal mtp\debug phone on.
in fastboot the driver said adb sooner single interface
and then when i am supposed to switch inn to the stock recovery modded with adb support,
i get 3 devies with yellow ! in device manager:
1. huawei- device properties and details then choose bus reported device description: huawei
2. unknown device: - device properties and details then choose bus reported device description: adb interface
3. unknown device: - device properties and details then choose bus reported device description: hdb interface
what should i set these to manually?
i am trying to use "flash update" in HWOTA_mate10 guide and i am on step D run ota.
supposed to switch from fastboot to recovery then the script waits for adb connection
Did you disable oem unlocking in developer options?
EngrVan said:
Did you disable oem unlocking in developer options?
Click to expand...
Click to collapse
no, but i just fixed it!
it showed adb interface, i tried different android drivers\adb drivers, found the right combo inn the end
Bootloader Unlock not possible - but eRecovery working
@ante0
I have Mate 10 BLA-L09c432 and installed latest Firmware 8.0.0.157 since two days. I updated with official OTA.
Before I had 8.0.0.137 → on that Firmware I read the Bootloader Unlock Code with DC Unlocker → and I got a new Unlock Code.
The originial Unlock Code did not work anymore (Phone was from a friend of mine and bricked and I restored it by FunkyHuawei - and bought it).
I unlocked the Bootloader with the new Code (read by DC) and it worked.
Two days ago I decided to update with OTA. I reflashed the original recovery_ramdisk and ramdisk.img. Update was succesful.
→ I tried to relock the Bootloader (because I am thinking about to sell the phone) → and it does not work! Not with the originial Code, not with the new Code (read on b137)
I did nothing wrong, because this year I unlocked about 40 devices (because I am helping to repair bricked phones from Users of Android Hilfe de) and I know very well how to do. (OEM Unlock enabled, ADB Debugging and USB Debugging enabled, HiSuite HDB disabled, HiSuite on PC closed, ADB and Fastboot working....)
Code:
fastboot oem relock UNLOCKCODE
does not work
But I have no idea yet how to relock the Loader I will try once more - but perhaps you or someone has an idea?
So perhaps I should just be happy to have a unlocked Phone and keep it instead of selling it....
Everything else is working.
And I found out some interesting point → seems Huawei started to bring the Feature of eRecovery even to European Versions of his Phones (from a certain firmware version)
I booted to Huawei eRecovery and "Download latest version and Recovery" is running without FunkyHuawei
Tecalote said:
@ante0
I have Mate 10 BLA-L09c432 and installed latest Firmware 8.0.0.157 since two days. I updated with official OTA.
Before I had 8.0.0.137 → on that Firmware I read the Bootloader Unlock Code with DC Unlocker → and I got a new Unlock Code.
The originial Unlock Code did not work anymore (Phone was from a friend of mine and bricked and I restored it by FunkyHuawei - and bought it).
I unlocked the Bootloader with the new Code (read by DC) and it worked.
Two days ago I decided to update with OTA. I reflashed the original recovery_ramdisk and ramdisk.img. Update was succesful.
→ I tried to relock the Bootloader (because I am thinking about to sell the phone) → and it does not work! Not with the originial Code, not with the new Code (read on b137)
I did nothing wrong, because this year I unlocked about 40 devices (because I am helping to repair bricked phones from Users of Android Hilfe de) and I know very well how to do. (OEM Unlock enabled, ADB Debugging and USB Debugging enabled, HiSuite HDB disabled, HiSuite on PC closed, ADB and Fastboot working....)
does not work
But I have no idea yet how to relock the Loader I will try once more - but perhaps you or someone has an idea?
So perhaps I should just be happy to have a unlocked Phone and keep it instead of selling it....
Everything else is working.
And I found out some interesting point → seems Huawei started to bring the Feature of eRecovery even to European Versions of his Phones (from a certain firmware version)
I booted to Huawei eRecovery and "Download latest version and Recovery" is running without FunkyHuawei
Click to expand...
Click to collapse
Use the DLOAD method with the B150 firmware from androidhost.ru, that should lock (not relock) it.
Pretoriano80 said:
Use the DLOAD method with the B150 firmware from androidhost.ru, that should lock (not relock) it.
Click to expand...
Click to collapse
Thanks Mate :good:
So I have just to check the Xloader thing before
Tecalote said:
Thanks Mate :good:
So I have just to check the Xloader thing before
Click to expand...
Click to collapse
B150 from androidhost.ru is xloader 2, which build do you have now?
Pretoriano80 said:
B150 from androidhost.ru is xloader 2, which build do you have now?
Click to expand...
Click to collapse
I have b157 (latest Firmware for c432, installed with official OTA (Full) from b137 to b157)
Tecalote said:
I have b157 (latest Firmware for c432, installed with official OTA (Full) from b137 to b157)
Click to expand...
Click to collapse
Then you can use B150 to downgrade with DLOAD method. That should reset the phone and lock the bootloader, to fabric condition.
Hi friends!
I'm new in Mi 8 Lite community. I wonder a thing. If i unlock my bootlader, can i lock it again ?
Thanks for your answers.
Absolutely you can
https://youtu.be/O6qU57iGhBg
hamidezat20 said:
https://youtu.be/O6qU57iGhBg
Click to expand...
Click to collapse
Will this work on Mi 8 Lite ?
Yes this method works on all xiaomi devices
Hello!
Some people claim that locking up the bootloader on newer Xiaomi devices could brick the phone.
Does this information proceed?
Has anyone tested?
---------- Post added at 08:51 PM ---------- Previous post was at 08:31 PM ----------
hamidezat20 said:
https://youtu.be/O6qU57iGhBg
Click to expand...
Click to collapse
This video shows how to install stock ROM. But no to lock bootloader.
I dont understand the language. So, I dont see when he lock bootloader.
Sorry! Bad english... ::laugh:
alxsduarte said:
Hello!
Some people claim that locking up the bootloader on newer Xiaomi devices could brick the phone.
Does this information proceed?
Has anyone tested?
---------- Post added at 08:51 PM ---------- Previous post was at 08:31 PM ----------
This video shows how to install stock ROM. But no to lock bootloader.
I dont understand the language. So, I dont see when he lock bootloader.
Sorry! Bad english... ::laugh:
Click to expand...
Click to collapse
This video don´t show how to lock bootloader so the essential part is missed, maybe the guy is talking about but most of users won´t understand what he says and is not reflected on the options that he is using.
If you want to lock bootloader using MiFlashTool then at time to flash a stock rom you have to check on "Clean All and Lock" option down at the right in the tool.
Locking bootloader can´t never brick device by itself, the problem is that some users tried to do it using a custom rom, a custom recovery, rooted or with a cross-firmware that was not released originally in the device and happened that after device was locked again then refuses to boot to android system so bootloader detects that some partition/s was/were altered.
If you only unlocked bootloader and you are using all stock and non rooted you can relock it without need of use mi flash but using only the typical fastboot command
Code:
fastboot oem lock
then check if it was correct with
Code:
fastboot oem device-info
BUT never try to lock it of this way if some non-stock file was flashed and currently using on your device be custom rom, custom recovery, root, logo, custom kernel, etc.
SubwayChamp said:
This video don´t show how to lock bootloader so the essential part is missed, maybe the guy is talking about but most of users won´t understand what he says and is not reflected on the options that he is using.
If you want to lock bootloader using MiFlashTool then at time to flash a stock rom you have to check on "Clean All and Lock" option down at the left in the tool.
Locking bootloader can´t never brick device by itself, the problem is that some users tried to do it using a custom rom, a custom recovery, rooted or with a cross-firmware that was not released originally in the device and happened that after device was locked again then refuses to boot to android system so bootloader detects that some partition/s was/were altered.
If you only unlocked bootloader and you are using all stock and non rooted you can relock it without need of use mi flash but using only the typical fastboot command
Code:
fastboot oem lock
then check if it was correct with
Code:
fastboot oem device-info
BUT never try to lock it of this way if some non-stock file was flashed and currently using on your device be custom rom, custom recovery, root, logo, custom kernel, etc.
Click to expand...
Click to collapse
Thank you, bro!
All my doubts are clear now!
you cant lock bootloader if you firmware was originally chinese and you have changed to global..
if your firmware was global and you unlocked , yes you can lock it again using flashtool and oficial GLOBAL fastboot rom,developer or stable..:good:
Hello, I've been trying to unlock my Mi8 Lite for a while (bootloader) but it is always stuck at 50% on MiUnlock, I've tried multiple drivers and disabling driver signature in Windows 10. It never gets beyond that point and always shows a '-1' error. Did anyone encounter this or better yet solved it? I've searched many times on Google and Youtube but with no success.
I had requested an unlock from Xiaomi and disabled all my other devices from my account.
Any help would be appreciated as this has become unnecessarily complicated, Thanks!
Shillopellos9 said:
Hello, I've been trying to unlock my Mi8 Lite for a while (bootloader) but it is always stuck at 50% on MiUnlock, I've tried multiple drivers and disabling driver signature in Windows 10. It never gets beyond that point and always shows a '-1' error. Did anyone encounter this or better yet solved it? I've searched many times on Google and Youtube but with no success.
I had requested an unlock from Xiaomi and disabled all my other devices from my account.
Any help would be appreciated as this has become unnecessarily complicated, Thanks!
Click to expand...
Click to collapse
Check again if it´s correctly binded your MiAccount on Developer Options and try with other MiUnlock version.
Shillopellos9 said:
Hello, I've been trying to unlock my Mi8 Lite for a while (bootloader) but it is always stuck at 50% on MiUnlock [...] It never gets beyond that point and always shows a '-1' error. Did anyone encounter this or better yet solved it?
Click to expand...
Click to collapse
Yes, I had the same issue and got it solved by using Mi Unlock on another PC. My main PC is using AMD Ryzen 2700 CPU, my laptop Intel Core i7-4712HQ. Wasted like 2 hours on my PC, while it worked first try on my laptop. Please note, the software told me to now wait 360 hours - it didn't unlock right away (this looks like expected behavior).
tolga9009 said:
Yes, I had the same issue and got it solved by using Mi Unlock on another PC. My main PC is using AMD Ryzen 2700 CPU, my laptop Intel Core i7-4712HQ. Wasted like 2 hours on my PC, while it worked first try on my laptop. Please note, the software told me to now wait 360 hours - it didn't unlock right away (this looks like expected behavior).
Click to expand...
Click to collapse
Soo i saw your reply and straight away tried unlocking with stock drivers on freshly bought laptop (today) with a Celeron, it worked straight away, Thanks! (i have a Ryzen 1600 desktop)
Witch version of Mi unlock software you suggest for unlocking bootloader?
I have China phone redmi note 8..and i want to flash global ROM but all Google say that if u lock the bootloader again...the phone will brick...so help me
Also, i have a question! My phone is on EU version, but i prefer the global version. Can i lock the bootloader back after i flash the version in fastboot mode?
Flash Mi 8 Lite image with mi flash tool and make sure you select clean all and lock in right bottom..
ThePscho said:
Hi friends!
I'm new in Mi 8 Lite community. I wonder a thing. If i unlock my bootlader, can i lock it again ?
Thanks for your answers.
Click to expand...
Click to collapse
You can flash fastboot ROM and set to clean all and lock, then the bootloader will be locked by a script from fastboot ROM
alicization said:
You can flash fastboot ROM and set to clean all and lock, then the bootloader will be locked by a script from fastboot ROM
Click to expand...
Click to collapse
Once i unlocked the bootloader, after i set a new password and fp it just kept saying that i need to enter my password every 0 hours. Tbh it did warn me when i accepted the oem unlocking that security features like fp, face recognision and find device will be disabled. So here is the question, is there any way at all to lock the bootloader without factory resetting?
P.S. : I have flashed twrp and miui 12, because i destroyed the miui 11 [:
Hi, I have a device that does not allow the unlocking of the bootloader, obviously it is a mediatek, if I take the file lk.bin on HxD it says "oem unlock is false.cmd_boot", there is no way to modify the file Lk.bin and add the oem unlock command?
When I do oem unlock on fastboot it says unknown command.
Try This
Try this : Type: fastboot flashing unlock
SlendowManX said:
Try this : Type: fastboot flashing unlock
Click to expand...
Click to collapse
Not work
XRed_CubeX said:
Not work
Click to expand...
Click to collapse
A phone's Fastboot is not always the same as AOSP Fastboot. How Fastboot is implemented depends on OEM/Carrier. If a chipset related flash tool is provided then you can assume that Fastboot does not work as expected.
XRed_CubeX said:
Hi, I have a device that does not allow the unlocking of the bootloader, obviously it is a mediatek, if I take the file lk.bin on HxD it says "oem unlock is false.cmd_boot", there is no way to modify the file Lk.bin and add the oem unlock command?
When I do oem unlock on fastboot it says unknown command.
Click to expand...
Click to collapse
LK.BIN is ( Qualcomm's version of ) device's bootloader. Wondering why you want to modify it ( i.e. remove/change text in it ), this because of all settings related to device's bootloader are stored in Android's system file named build.prop?
FYI:
LK.BIN has the following:
Variety of nand devices for bootup
USB driver to enable upgrading images over usb during development
Keypad driver to enable developers enter ‘fastboot’ mode for image upgrades
Display driver for debugging and splash screen
Enable Android recovery image and image upgrades
jwoegerbauer said:
LK.BIN is ( Qualcomm's version of ) device's bootloader. Wondering why you want to modify it ( i.e. remove/change text in it ), this because of all settings related to device's bootloader are stored in Android's system file named build.prop?
FYI:
LK.BIN has the following:
USB driver to enable upgrading images over usb during development
Keypad driver to enable developers enter ‘fastboot’ mode for image upgrades
Display driver for debugging and splash screen
Enable Android recovery image and image upgrades
Click to expand...
Click to collapse
Ok if I don't have to edit LK then what should I edit on build prop to unlock the bootloader? Fastboot oem unlock and flashing unlock does not work, says unknown command
P.S: Everyone has the same problem as me and in any case my soc is Mt6737M and the OEM is Meizu, it has no official tools released to unlock the bootloader and I would like to know if there is another way
XRed_CubeX said:
P.S: Everyone has the same problem as me and in any case my soc is Mt6737M and the OEM is Meizu, it has no official tools released to unlock the bootloader and I would like to know if there is another way
Click to expand...
Click to collapse
I guess there is no other method.
Take note that carrier exclusive models (ex. Verizon, AT&T, Tracfone) are almost never unlockable. Probably your device is one of these.
BTW: To edit Android's system file build.prop device's Android must got rooted before what requires SuperSU ( or similar ) got installed before what requires device's bootloader got unlocked before ...
jwoegerbauer said:
I guess there is no other method.
Take note that carrier exclusive models (ex. Verizon, AT&T, Tracfone) are almost never unlockable. Probably your device is one of these.
BTW: To edit Android's system file build.prop device's Android must got rooted before what requires SuperSU ( or similar ) got installed before what requires device's bootloader got unlocked before ...
Click to expand...
Click to collapse
My meizu has a pre-installed Root (can be activated with the flyme account), it is also convertible into SuperSU. However my device is not part of any carrier.
So having the root I can easily modify build.prop
@XRed_CubeX
OK, then look inside here.
EDIT:
You additionally can try to replace existing ADB & Fastboot binaries by those as attached
jwoegerbauer said:
@XRed_CubeX
OK, then look inside here.
EDIT:
You additionally can try to replace existing ADB & Fastboot binaries by those as attached
Click to expand...
Click to collapse
Ok i try later but what i have to do with this binaries?
jwoegerbauer said:
@XRed_CubeX
OK, then look inside here.
EDIT:
You additionally can try to replace existing ADB & Fastboot binaries by those as attached
Click to expand...
Click to collapse
Anyway with mixplorer I tried to modify the build.prop and add "ro.oem_unlock_supported = 1" but nothing, if I restart in fastboot and I do fastboot flashing unlock this comes out:
Code:
D:\Users\XRed_CubeX\Desktop>fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
XRed_CubeX said:
Code:
D:\Users\XRed_CubeX\Desktop>fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
Click to expand...
Click to collapse
Remember I told you
A phone's Fastboot is not always the same as AOSP Fastboot. How Fastboot is implemented depends on OEM/Carrier.
Click to expand...
Click to collapse
Understand finally that implementation of Fastboot on your phone isn't the same as AOSP Fastboot.
jwoegerbauer said:
Remember I told you
Understand finally that implementation of Fastboot on your phone isn't the same as AOSP Fastboot.
Click to expand...
Click to collapse
Yes ok but anyway I did what you told me that is to modify the build prop as I told you before and nothing has changed, I don't know if I missed something but what I changed I wrote before
XRed_CubeX said:
Yes ok but anyway I did what you told me that is to modify the build prop as I told you before and nothing has changed, I don't know if I missed something but what I changed I wrote before
Click to expand...
Click to collapse
My last 2 cents here:
IIRC I never told you to modify build.prop entries to get things work as expected.
jwoegerbauer said:
My last 2 cents here:
IIRC I never told you to modify build.prop entries to get things work as expected.
Click to expand...
Click to collapse
So what should I do in my case?
jwoegerbauer said:
My last 2 cents here:
IIRC I never told you to modify build.prop entries to get things work as expected.
Click to expand...
Click to collapse
P.S:I tried to look at the build.prop better but there is nothing interesting or attributable to an unlocking of the bootloader, there is probably nothing to do, if you are interested, here is a site where there is the build.prop.
i try the version of Magisk 23.0 but this is not worked.
It's the same with all other Xperia devices without customise recovery.
You first use Unsin (can find it in XDA) to the boot_blahblahblah.sin from stock firmware for unsin it. Therefore you will see a .IMG is generated.
Second, you transfer the .IMG to your phone, and use Magisk to patch (install - select file and patch) the boot file.
After it's patched (you can find it in the Download folder). Transfer the patched one back to your PC, and make phone enter fastboot mode (or the blue light mode). Then you run this command on Windows Shell (Google it, it's easy)
Fastboot flash boot the_file_name.img
After it's done, boot into your phone, you can find icon of Magisk, install it, and your phone is rooted in this stage.
Nevermind figured it out
Kylewolf said:
Nevermind figured it out
Click to expand...
Click to collapse
Before you do anything, a unlocked bootloader is must required.
JaneValley said:
It's the same with all other Xperia devices without customise recovery.
You first use Unsin (can find it in XDA) to the boot_blahblahblah.sin from stock firmware for unsin it. Therefore you will see a .IMG is generated.
Second, you transfer the .IMG to your phone, and use Magisk to patch (install - select file and patch) the boot file.
After it's patched (you can find it in the Download folder). Transfer the patched one back to your PC, and make phone enter fastboot mode (or the blue light mode). Then you run this command on Windows Shell (Google it, it's easy)
Fastboot flash boot the_file_name.img
After it's done, boot into your phone, you can find icon of Magisk, install it, and your phone is rooted in this stage.
Click to expand...
Click to collapse
good job my friend.
JaneValley said:
Before you do anything, a unlocked bootloader is must required.
Click to expand...
Click to collapse
Hello
Did you find Xperia 1 iii on Sony Developer site?
Or how did you achieve the unlock file?
Regards,
Olavbson
Where the hell do i find the official firmware, thats where im stuck
ya id like to unlock bootloader so i can achieve root on us xperia 1 iii. nothing has worked. and xperia 1 iii isnt on sony develope site to unlock bootloader. either. how are people doing this.
jporter396 said:
ya id like to unlock bootloader so i can achieve root on us xperia 1 iii. nothing has worked. and xperia 1 iii isnt on sony develope site to unlock bootloader. either. how are people doing this.
Click to expand...
Click to collapse
same am stuck at bootloader unlock rn. Cannot flash
olavbson said:
Hello
Did you find Xperia 1 iii on Sony Developer site?
Or how did you achieve the unlock file?
Regards,
Olavbson
Click to expand...
Click to collapse
Sorted it? Rooted mine earlier on. To unlock the bootloader you can just pick Xperia 1 or 1II it doesn't matter 1III will be added eventually but doesn't make a difference.
AJHutchinson said:
Sorted it? Rooted mine earlier on. To unlock the bootloader you can just pick Xperia 1 or 1II it doesn't matter 1III will be added eventually but doesn't make a difference.
Click to expand...
Click to collapse
What about DRM keys? how do u deal with that.
AJHutchinson said:
Sorted it? Rooted mine earlier on. To unlock the bootloader you can just pick Xperia 1 or 1II it doesn't matter 1III will be added eventually but doesn't make a difference.
Click to expand...
Click to collapse
Hey sorry another question, i know rooting will kill netfleex and such but did u notice any other side effects, can you still view HDR
rom4ster said:
Hey sorry another question, i know rooting will kill netfleex and such but did u notice any other side effects, can you still view HDR
Click to expand...
Click to collapse
I haven't noticed anything that's not working buddy
AJHutchinson said:
I haven't noticed anything that's not working buddy
Click to expand...
Click to collapse
Thanks, sorry to bother you more but how did you unlock the phone exactly?
I am getting this error on fastboot
fastboot oem unlock 0x2DC728328A49EEAB
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
rom4ster said:
Thanks, sorry to bother you more but how did you unlock the phone exactly?
I am getting this error on fastboot
fastboot oem unlock 0x2DC728328A49EEAB
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
Click to expand...
Click to collapse
Mine was doing the same buddy, make sure you have entered the correct IMEI and that you have OEM unlock and usb debugging turned on in the developer settings
AJHutchinson said:
Mine was doing the same buddy, make sure you have entered the correct IMEI and that you have OEM unlock and usb debugging turned on in the developer settings
Click to expand...
Click to collapse
i verified OEM unlock is on in settings I am copying the IMEI reported by ADB directly, and USB debugging is on yet the error persists. What solved it for you?
rom4ster said:
i verified OEM unlock is on in settings I am copying the IMEI reported by ADB directly, and USB debugging is on yet the error persists. What solved it for you?
Click to expand...
Click to collapse
Check the IMEI by dialing *#06# see if it matches up with that one, if using Dual SIM variant use the first code
AJHutchinson said:
Check the IMEI by dialing *#06# see if it matches up with that one, if using Dual SIM variant use the first code
Click to expand...
Click to collapse
Also is
Code:
Fastboot devices
showing a device? Maybe it's not installed properly?
same issue here. command not supported error. did everything on sony guide to the t. us variant, windows 10. not sure what to do
fastboot shows device too
jporter396 said:
same issue here. command not supported error. did everything on sony guide to the t. us variant, windows 10. not sure what to do
fastboot shows device too
Click to expand...
Click to collapse
Annoying aye, my issue was with the IMEI I must have been putting a wrong digit in but it worked eventually