Help ! I got a Kate with a Kenzo rom on it.
Can i flash a Kate rom via Miflash without loosing IMEI, WiFi and bluetooth.
Are there other methods of flashing Kate rom that keeps everything intact?
I have no root and my Bootloader is locked.
Any help aprecieated
rightnow i flashed a Kenzo rom with Kate modem and everything works.
If you wanna kate MIUI rom or your kate RN3 SE..then you must flashing kate RN3 SE fastboot rom with miflash..then you don't needed flashing kate modem again..
I have done that but now i have no wifi no bluetooth.
Gamester87 said:
I have done that but now i have no wifi no bluetooth.
Click to expand...
Click to collapse
What version of fastboot rom you're flashing it..?, and from where you're downloading it..?, is it right from here :
Latest Global Stable fastboot rom for Kate : V8.0.4.0.MHRMIDG
Latest Developer fastboot rom for Kate : v6.11.24
Also you had already choice set to "Clean all" while flashing with miflash..?
i have flashed these fastboot roms in EDL mode with choice set to "Clean all".
should i try it in fastboot mode?
Redmi Note 3 Special Edition Latest Global Developer Version
hxxp://update.miui.com/updates/v1/fullromdownload.php?d=kate_global&b=X&r=global&n=
Redmi Note 3 Special Edition Latest Global Stable Version
hxxp://update.miui.com/updates/v1/fullromdownload.php?d=kate_global&b=F&r=global&n=
in this rom the config.bin is missing i took it from the developer rom.
these roms are from hxxp://en.miui.com/a-234.html
sorry i cant post ouside links repplace xx in the adress with tt
I will try it with your roms and report back.
same with your roms no wifi no bluetooth. I will send this unit back.
Gamester87 said:
same with your roms no wifi no bluetooth. I will send this unit back.
Click to expand...
Click to collapse
Really weird things..
I though your phone already loosing IMEI and mac address on it..i think that's cause by flashing wrong fastboot rom before..you can check it under about phone..after flashing try check it if your phone still has it or not..
Not sure about this if any different in this case..if you still wanna try it to flashing via fastboot mode..you must unlocking your bootloader first..after flashing latest developer fastboot rom..adding your mi account..then go to fastboot mode..then unlock it with miunlock tool..after that if success unlocked..you can try flashing through fastboot mode.
If still doesn't success...just like you said..just send it back your phone to the seller or services center to get fix it or replace the unit with new one.
i dont lost imei i was just asking if ther is a method without loosing IMEI and WiFi.
The phone came with a shop rom i think. It was on MIUI ver. 8.0.1.0 but i couldn't update via updater. I always got the error " Couldn't boot to recovery mode " pretty strange. Thanks for help.
JJeamy said:
Really weird things..
I though your phone already loosing IMEI and mac address on it..i think that's cause by flashing wrong fastboot rom before..you can check it under about phone..after flashing try check it if your phone still has it or not..
Not sure about this if any different in this case..if you still wanna try it to flashing via fastboot mode..you must unlocking your bootloader first..after flashing latest developer fastboot rom..adding your mi account..then go to fastboot mode..then unlock it with miunlock tool..after that if success unlocked..you can try flashing through fastboot mode.
If still doesn't success...just like you said..just send it back your phone to the seller or services center to get fix it or replace the unit with new one.
Click to expand...
Click to collapse
Will not the warranty be void after so many experiments on the device?
Nope..just telling them about wifi and bluetooth problem, and bootloader still in locked state..
Gamester87 said:
i dont lost imei i was just asking if ther is a method without loosing IMEI and WiFi.
The phone came with a shop rom i think. It was on MIUI ver. 8.0.1.0 but i couldn't update via updater. I always got the error " Couldn't boot to recovery mode " pretty strange. Thanks for help.
Click to expand...
Click to collapse
friend. dont send it back. I can solve it for you.
andersonaragao said:
friend. dont send it back. I can solve it for you.
Click to expand...
Click to collapse
Thanks for the help. Now i have send it back it was bought on Ebay so no return cost.
Nevertheless Could you tell me how you would fix it. Just curious and maybe someone who is reading this thread later can solve the problem.
andersonaragao has fixed my phone. Big thanks. I can recommend this guy he know what he is doing.
Related
Just a heads up. I've got my RMP since today. As a usual nexus user as I was, the first thing was to unlock the bootloader and flash whatever I can. My destination was -> unlocked bootloader -> smiui with root.
What happened it the following:
1) I unlocked my bootloader following guides (unofficial way)
2) Installed TWRP
3) Flashed SMIUI
And welcome brick. I was in emergency port (9003), and the only way to get the device running was the disasembe way. Well it worked. Now I'm on 7.2.3 with root, but guys - watch what you are flashing. This is my 3rd device (Desire HD, Nexus 4, and now RMP), and this was the first time that I had such a headaches.
SMIUi contains the locked bootloader file, so if by any chance you decide to unlock it by the unofficial way - don't flash it.
Read...read....read and one more time read there are many threads explaining how to do it without getting bricked .
Yup already lernt my lesson. Deleting emmc_appsboot.mbn from the archive before flashing is the right way.
Anyway, SMIUI is totally unusable on our devices. Flashed 6.4.21 and 6.4.14 - on both of them I get no sim/no wifi. Can't connect the device to the PC in file transfer mode also. Now I'm running xiaomi.eu 6.4.21 without issues.
ktomov said:
Yup already lernt my lesson. Deleting emmc_appsboot.mbn from the archive before flashing is the right way.
Anyway, SMIUI is totally unusable on our devices. Flashed 6.4.21 and 6.4.14 - on both of them I get no sim/no wifi. Can't connect the device to the PC in file transfer mode also. Now I'm running xiaomi.eu 6.4.21 without issues.
Click to expand...
Click to collapse
Hello ktomov,
I made the same mistake. I couldn’t wait 10 days for the official unlock so I used the unofficially unlocked bootloader. Then I flashed TWRP and a Xiaomi EU ROM thinking that it’s probably gonna be OK since that’s not an official Xiaomi ROM. Nope! Bricked my device and had to use the testpoint method.
Now my question for you is what to do if want to flash a Xiaomi EU ROM again in case I don’t get the official unlock permission (is it even possible that I don’t get it?). Do I just need to replace the emmc_appsboot.mbn in the ROM’s ZIP file? I’m asking because there is a huge thread on this forum on how to maintain future OTA updates with unofficial unlock and I’d rather just stick with a TWRP-compatible ROM.
just refer to this thread if you flash anything on a unofficially unlocked bloader and ALWAYS DELETE emmc_appsboot.mbn
http://forum.xda-developers.com/redmi-note-3/how-to/creating-modified-boot-img-enabling-adb-t3359916
oh and as far as sMiui goes, dunno bout you, but it worked for me. it lags like hell, but it works. I had no issues with sim/wifi, and as far as MTP mode goes, disable adb in developer opts, that will trigger MTP mode. kinda annoying, but should work. same thing is happening on xiaomi eu and global roms too.
sikica133 said:
just refer to this thread if you flash anything on a unofficially unlocked bloader and ALWAYS DELETE emmc_appsboot.mbn
http://forum.xda-developers.com/redmi-note-3/how-to/creating-modified-boot-img-enabling-adb-t3359916
Click to expand...
Click to collapse
Thanks. That should make sure I don’t hardbrick my phone and retain access to EDL mode. But my question is whether replacing the emmc_appsboot.mbn is all I need to do when flashing a TWRP compatible ROM. No other scripts or changes are necessary?
Hvala u svakom slučaju.
sikica133 said:
just refer to this thread if you flash anything on a unofficially unlocked bloader and ALWAYS DELETE emmc_appsboot.mbn
http://forum.xda-developers.com/redmi-note-3/how-to/creating-modified-boot-img-enabling-adb-t3359916
oh and as far as sMiui goes, dunno bout you, but it worked for me. it lags like hell, but it works. I had no issues with sim/wifi, and as far as MTP mode goes, disable adb in developer opts, that will trigger MTP mode. kinda annoying, but should work. same thing is happening on xiaomi eu and global roms too.
Click to expand...
Click to collapse
Don't know what is going on with those roms, but for me sMiui 6.4.14 and 6.4.21 gives no-sim/no-wifi. Disabling dev still didn't got me to mtp. Haven't got such issues with xiaomi.eu roms though. 6.4.14 and 6.4.21 works like they should.
Filip013 said:
Thanks. That should make sure I don’t hardbrick my phone and retain access to EDL mode. But my question is whether replacing the emmc_appsboot.mbn is all I need to do when flashing a TWRP compatible ROM. No other scripts or changes are necessary?
Hvala u svakom slučaju.
Click to expand...
Click to collapse
Don't replace it. Just delete it from the archive prior flashing.
ktomov said:
Don't know what is going on with those roms, but for me sMiui 6.4.14 and 6.4.21 gives no-sim/no-wifi. Disabling dev still didn't got me to mtp. Haven't got such issues with xiaomi.eu roms though. 6.4.14 and 6.4.21 works like they should.
Don't replace it. Just delete it from the archive prior flashing.
Click to expand...
Click to collapse
Roger that!
So if you have unlocked the bootloader the unofficial way is there any way to flash a locked bootloader later on if for example you wish to give in you phone for repair at the service center?
devtherockstar said:
So if you have unlocked the bootloader the unofficial way is there any way to flash a locked bootloader later on if for example you wish to give in you phone for repair at the service center?
Click to expand...
Click to collapse
unlocking bootloader does not void your warranty
Ive recived a device with the model on the sticker : 2015161 which is by google the kate edition.
on fastboot getvar product I got kenzo.
so I flashed kenzo firmware and now I have no reception, on *#*#4636#*#* the radio cant be turned on.
what Ive tried:
flashing few kate stom firmwares : all stuck on bootloop
rewriteing the qcn : no network
unlocking the bootloader and flasing kate modem : no network
what else can I do ?
edit:
Can any one upload for me the following partitions from a phone with working cellular connection:
modem
modemst1
modemst2
fsg
and possibly QCN ?
thanks in advance !
I know it's an old post but I did the same thing. Did you find a solution?
Alaskan Dan said:
I know it's an old post but I did the same thing. Did you find a solution?
Click to expand...
Click to collapse
If you can't flash the kate firmware, do you will have to reinstall the latest stable version of MIUI using MiFlash. Take a look at Google how do you do it
snacs said:
If you can't flash the kate firmware, do you will have to reinstall the latest stable version of MIUI using MiFlash. Take a look at Google how do you do it
Click to expand...
Click to collapse
i cant install custom kate roms. i did flashed **** and now i bricked it GRRRR
fastboost still alive but this means miflash again and relock bootloader FFS i just want a stable custom rom that is not miui....
the phone was good till it got a memory crash and kept rebooting when ever i installed apps
finaly after 4months i had the time to fix it. and now i keep messing it up.
anyway. i will post a new post maybe some one will help.
but what i want to know what do i need to do when i want to install a custom rom on my kate. do i need to flash any modem? or not
reggiexp said:
i cant install custom kate roms. i did flashed **** and now i bricked it GRRRR
fastboost still alive but this means miflash again and relock bootloader FFS i just want a stable custom rom that is not miui....
the phone was good till it got a memory crash and kept rebooting when ever i installed apps
finaly after 4months i had the time to fix it. and now i keep messing it up.
anyway. i will post a new post maybe some one will help.
but what i want to know what do i need to do when i want to install a custom rom on my kate. do i need to flash any modem? or not
Click to expand...
Click to collapse
Miflash will not relock your bootloader. There is just an option to do it, but you can install latest dev weekly through miflash and get back on custom rom immediately. Maybe i dont know some specifics but i did it multiple times.
Borodavnochi said:
Miflash will not relock your bootloader. There is just an option to do it, but you can install latest dev weekly through miflash and get back on custom rom immediately. Maybe i dont know some specifics but i did it multiple times.
Click to expand...
Click to collapse
edl does. fastboot flash doesn't work. and bootlaoder is relocked
Hi all,
Thanks in advance.
Officially unlocked snap
baseband is unknown
no network
no wifi
bluetooth is unavailable
mac address looks something like this : 02:00:00 etc
I do have imei numbers for both slots both sv are unknown though
I didn't backup the efs partition
So I tried to flash a different rom but it failed luckly I had backed up the current rom and can access official twrp ( iwas using zcx but when flashing it hung so flashed offical) and fastboot
I'm really not sure how to proceed alot of what I have read seems to point me to fastboot a rom using miflash, but this thread shows a different way but I have my imei.
Thanks again
Try this ://forum.xda-developers.com/redmi-note-3/how-to/flash-recover-efs-snapdragon-t3406789
---------- Post added at 10:20 AM ---------- Previous post was at 10:19 AM ----------
Also witch device u have Kenzo Kate Mtk?
damn........apologies to all i can see what i did now looking at this thread I can see I have a Kate.......I've tried to flash kenzo over it.
I'm a idiot. I know
Now what?
crankyness said:
damn........apologies to all i can see what i did now looking at this thread I can see I have a Kate.......I've tried to flash kenzo over it.
I'm a idiot. I know
Now what?
Click to expand...
Click to collapse
now what? reflash with kate
ok so I tried to reflash with Kate I got up to the point where you try and upgrade the qualcomm driver to "10" i couldn't get this to work but flashed anyway Kate v8.0.4.0. After the flash it came up with a error but I rebooted and had dinner. Anyway it seemed to load up but was full of errors popping up at the bottom of the screen. I let it update again. and they went away and i got bluetooth back, next update bought wifi......next and I have a baseband????? baseband version is -8976_GEN_PACK-1.74446.1.75478.1
But to get it to work I did this I had to turn all the radios on and off, i can't get sms to send or recieve???? strange but hangouts work???? mi messenging just shuts really quick on opening android messaging wont let me write or send a message, it will only let me select a contact.
mobile network state is disconnected????????
I can make and recieve phone calls.
Do you have your IMEIs check that
Hi
imei's are both ok thanks.
xiaomi messaging closes on opening with a error but it's to quick to read, android messaging lets you select a contact but you can't write a message????
mobile network state is disconnected - I'm gonna try and manual change the apn's but not till after work .
managed to send pictures and text via hangouts on data last night so don't get why messaging does not work?
If I were you I would reflash a stable rom for your device through mi flash the latest if you want,and also if you have locked bootloader use edl mode instead of fastboot to flash!
Just flashed the latest global developer rom though system update, mobile network state is disconnected.......but I can make and receive texts and phone calls. Hopefully that's it and sorted.
As a side note I can see now that flashing kate when the drivers didn't work, it just reset the device to a early version........all personal data was was still there. This time round it wanted user names and passwords for everything.
Anyway thank you tabenf for your time ideas and patience.
crankyness said:
Just flashed the latest global developer rom though system update, mobile network state is disconnected.......but I can make and receive texts and phone calls. Hopefully that's it and sorted.
As a side note I can see now that flashing kate when the drivers didn't work, it just reset the device to a early version........all personal data was was still there. This time round it wanted user names and passwords for everything.
Anyway thank you tabenf for your time ideas and patience.
Click to expand...
Click to collapse
No problem:good::good:
tabenf said:
No problem:good::good:
Click to expand...
Click to collapse
Did you flash a Marshmallow version?
Of what???
trabuc said:
Did you flash a Marshmallow version?
Click to expand...
Click to collapse
Of what???
Sorry, wrong thread. My mistake
crankyness said:
Just flashed the latest global developer rom though system update, mobile network state is disconnected.......but I can make and receive texts and phone calls. Hopefully that's it and sorted.
As a side note I can see now that flashing kate when the drivers didn't work, it just reset the device to a early version........all personal data was was still there. This time round it wanted user names and passwords for everything.
Anyway thank you tabenf for your time ideas and patience.
Click to expand...
Click to collapse
If it still give you error then download fastboot rom from miui download. And flash it using edl method. This is much more convenient and it will solve all problem. Or if you dont mind using custom rom, then flash LineageOS and then flash Kate Firmware. Thestrix have provided the lates firmware for kate on his thread.
Hi everyone, im new to XDA. But that's kinda beside the point.
I have a Redmi Note 3 with Snapdragon 650 and 2gb ram 16gb storage. I wanted to install lineage os/R.remix because im kinda bored of miui and wanted nougat. I did the following steps to install.
1. Unlocked bootloader via no-permission or hack method.
2. Installed TWRP latest as of 10-6-2017 thru Fastboot.
3. Wiped cache,dalvik and data
4. Flashed R.Remix nightly 10-6-17 and then Gapps.
In this step, I had a problem. It was giving me error:7 (xiaomi.verify.modem) and so I modded the rom (updater-script) and worked. It had the animation loop soflashed NON-HLOS modem binary thru Fastboot and flashed the original signed ROM. But, the problem persists. It's stuck in the boot animation and looping infinitely. I left it for 30min-1hr and still loops. What do I do now? Please help me in this regard. Till then, MIUI again
bro you forgot to flash lazy flasher at first boot in rom after installing twrp.
dean [email protected]# said:
bro you forgot to flash lazy flasher at first boot in rom after installing twrp.
Click to expand...
Click to collapse
There's no need of lazyflasher on a custom Rom!
Do you want to know something else about what I did to solve the problem? Although I rolled back to miui bcos I needed my phone:good:
U need to update ur firmware. Download it from below link & follow the below steps.
https://www.androidfilehost.com/?fid=817550096634767927
Wipe system, Data, cache, Dalvik cache
Install above firmware
Install Custom Rom of ur choice
Enjoy
Let me know if it doesn't works
ExtGame said:
Hi everyone, im new to XDA. But that's kinda beside the point.
I have a Redmi Note 3 with Snapdragon 650 and 2gb ram 16gb storage. I wanted to install lineage os/R.remix because im kinda bored of miui and wanted nougat. I did the following steps to install.
1. Unlocked bootloader via no-permission or hack method.
2. Installed TWRP latest as of 10-6-2017 thru Fastboot.
3. Wiped cache,dalvik and data
4. Flashed R.Remix nightly 10-6-17 and then Gapps.
In this step, I had a problem. It was giving me error:7 (xiaomi.verify.modem) and so I modded the rom (updater-script) and worked. It had the animation loop soflashed NON-HLOS modem binary thru Fastboot and flashed the original signed ROM. But, the problem persists. It's stuck in the boot animation and looping infinitely. I left it for 30min-1hr and still loops. What do I do now? Please help me in this regard. Till then, MIUI again
Click to expand...
Click to collapse
Don't flash that miui firmware from post above, it will relock your bootloader because you are not officially unlocked.
Best way to go is to flash latest global dev fastboot rom, unlock officially. This way you will have no problems with flashing nougat custom roms.
So, should I install the latest global developer rom? I checked yesterday it was v7.6.7 while latest global stable was 8.2.4 which I have currently installed. I also checked via fastboot OEM device-info and, yeah, bootloader locked.:crying: So, I should install the dev. Rom and ask for permission and then unlock, like, the official way? I'm waiting for the reply. Make it clear and I'll try it. Thnx.
Edit : I also somehow got TWRP uninstalled:crying::crying: I don't know if this unexpected or was doomed to happen but yeah, again, just saying.
I just asked for permissions to unlock and..... Surprise!!! I got the permission in 5 minutes!!!
I feel kinda sad for the people who are waiting for more than 21 days...
Capt. John Yossarian said:
Don't flash that miui firmware from post above, it will relock your bootloader because you are not officially unlocked.
Best way to go is to flash latest global dev fastboot rom, unlock officially. This way you will have no problems with flashing nougat custom roms.
Click to expand...
Click to collapse
Okee, doin' it. I'll inform you later abt how its hapenning.
Good luck to me
ExtGame said:
Okee, doin' it. I'll inform you later abt how its hapenning.
Good luck to me
Click to expand...
Click to collapse
Good luck.
https://www.digitbin.com/unlock-bootloader-xiaomi/
https://www.howtogeek.com/240047/how-to-flash-twrp-recovery-on-your-android-phone/
https://forum.xda-developers.com/showthread.php?t=2317790
OMG OMG OMG IM TRIGGERED WHAT IS THIS??????!!!!!!!!!!!!!!
*calms down*
This MI Flash gets stuck at 99% even tho I got permissions (an SMS from MI) and shows current account not bound to device. What do I do? I also tried binding my account to phone by settings-->dev. options-->mi unlock which gave code 86012 and some Chinese characters which I honestly can't understand. I also tried installing global dev and doing the same thing but gives same 86012 and Chinese. Plzz help me in this regard. Would be greatly appreciated. Thanks.
Actually, nvm. I got lineage is installed and running on my phone by following a guide on how to install twrp without unlocking bootloader. Worked like a charm for me. I'm typing this now on lineage:silly: Anyways, thanks for the effort. Thread closed.
You could've just waited for 7 days and you would've unlocked your bootloader officially
how did it go buddy ?
ExtGame said:
Okee, doin' it. I'll inform you later abt how its hapenning.
Good luck to medid you falsh the custom rom , does it work cause i get stuck on bootanimation too
Click to expand...
Click to collapse
I am using it thru locked bootloader mrthod
ExtGame said:
OMG OMG OMG IM TRIGGERED WHAT IS THIS??????!!!!!!!!!!!!!!
*calms down*
This MI Flash gets stuck at 99% even tho I got permissions (an SMS from MI) and shows current account not bound to device. What do I do? I also tried binding my account to phone by settings-->dev. options-->mi unlock which gave code 86012 and some Chinese characters which I honestly can't understand. I also tried installing global dev and doing the same thing but gives same 86012 and Chinese. Plzz help me in this regard. Would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Same here please help
You can follow the tutorial on how to install lineage os with locked bootloader on redmi note 3. Works like a charm, i am using lineage os 14.1 with locked b.loader!!:good:
recommend you to wait for 5-7 days and unlock it officially...
So that you would never face problems in future.
Hello everyone, I and my father have the exact same phone (kenzo). The problem is that even though on mine everything works like a charm and I have changed a lot of roms, my father's phone every time I try anything goes soft bricked or have problems with signal and settings. Currently I have flashed via edl the Chinese Dev rom(5.1.1) with which everything works, besides the restrictions of the rom version(language, gapps). I must say that when I first install the Chinese Dev the Sim is not recognised or I have no signal. After the first update everything is ok and calling function works like a charm. After That I try to install twrp (zxc by ~xm) and restore a backup from the previous working installation, but the only I get is settings app fc and problems with calls. Neither of the two sides hear the other while in call. This occurred when I flashed a mm bootloader zip in order to boot to nitrogen is. (https://drive.google.com/file/d/0B3tM1cVKiyp6Q3RvNUtLdEp1Q3M/view ) The rom booted but I had no sound in calling, and the other side couldn't hear either. Any ideas?
Thanks for your time!
Aristalex said:
Hello everyone, I and my father have the exact same phone (kenzo). The problem is that even though on mine everything works like a charm and I have changed a lot of roms, my father's phone every time I try anything goes soft bricked or have problems with signal and settings. Currently I have flashed via edl the Chinese Dev rom(5.1.1) with which everything works, besides the restrictions of the rom version(language, gapps). I must say that when I first install the Chinese Dev the Sim is not recognised or I have no signal. After the first update everything is ok and calling function works like a charm. After That I try to install twrp (zxc by ~xm) and restore a backup from the previous working installation, but the only I get is settings app fc and problems with calls. Neither of the two sides hear the other while in call. This occurred when I flashed a mm bootloader zip in order to boot to nitrogen is. (https://drive.google.com/file/d/0B3tM1cVKiyp6Q3RvNUtLdEp1Q3M/view ) The rom booted but I had no sound in calling, and the other side couldn't hear either. Any ideas?
Thanks for your time!
Click to expand...
Click to collapse
Is ur device bootloader is unlocked ?
If yes then by which method u had unlocked by unofficial way or by official way?
Criston said:
Is ur device bootloader is unlocked ?
If yes then by which method u had unlocked by unofficial way or by official way?
Click to expand...
Click to collapse
I used to unlock it the official way. I found a post in the nitrogenOS thread that said that if the rom doesn't boot I should flash the zip that I have mentioned in my post. They said it was the mm bootloader. The zip contains a file named emmc_appsboot.mbn which is also on the unofficial unlock zip. So I suppose I unlocked it unofficially. I must say that every time after flashing fastboot rom the mi unlock said that bootloader was already unlocked.
Aristalex said:
I used to unlock it the official way. I found a post in the nitrogenOS thread that said that if the rom doesn't boot I should flash the zip that I have mentioned in my post. They said it was the mm bootloader. The zip contains a file named emmc_appsboot.mbn which is also on the unofficial unlock zip. So I suppose I unlocked it unofficially. I must say that every time after flashing fastboot rom the mi unlock said that bootloader was already unlocked.
Click to expand...
Click to collapse
U should unlock using the official way if u dont want to face any problem
And also if wanna Flash any custom rom first clean Flash miui using Mi flash tool and google how to Flash custom rom on kenzo
make sure u have backup of all ur files
Criston said:
U should unlock using the official way if u dont want to face any problem
And also if wanna Flash any custom rom first clean Flash miui using Mi flash tool and google how to Flash custom rom on kenzo
make sure u have backup of all ur files
Click to expand...
Click to collapse
Yes yes I know that with my kenzo everything works if I follow your advice. But with my father's one simply doesn't. I flashed the official miui with mi flash tool. The bootloader remained unlocked without reason. Also I tried clean flash and lock option on the tool without success. Then I wiped data and dalvik and cache and dirty flashed a miui custom rom over it. For the time being everything works perfectly except of the fingerprint sensor. Aida 64 recognize the fp, every other app not. Also I flashed radon kernel because I had settings app FC. That's all. I hope the info help you understand the situation that I am in, and find a way to make it respond as mine...
Mine and the other are exactly the same, they even had the same number on the sticker in the back and same fingerprint sensor. Mine takes every rom, unlock update without problems. My father's not. It is crazy...