Related
Hi guys, can anyone tell me how to do it? I have a kate device here, and I'm dying to have cyanogenmod installed on it. Wish there's a non-too-complicated way to get it done.
Update:
Official CyanogenMod 13 for Kenzo works well on Kate too! Everything seems good right now.
Hey can you please Dump your device with twrp and share it with us so we can try to unlock Band 20
Edit: i think banmeifyouwant did it the others way around. Guess you have to repartition your internal memory to have the Layout of kenzo. Also someone in miui Forum posted he has flashed kenzo fastboot to his Kate device but Radio is not working anymore.
wtfjajaja said:
Hi guys, can anyone tell me how to do it? I have a kate device here, and I'm dying to have cyanogenmod installed on it. Wish there's a non-too-complicated way to get it done.
Update:
Official CyanogenMod 13 for Kenzo works well on Kate too! Everything seems good right now.
Click to expand...
Click to collapse
Can you please advise where you got TWRP from? Without TWRP, there's no CM or even root for XMIUI and MIUI Tweaks.
Also looking for a compatible TWRP method for the Kate/prime version. Been scouring the net for hours but can't find anything concrete
Hemphiz said:
Also looking for a compatible TWRP method for the Kate/prime version. Been scouring the net for hours but can't find anything concrete
Click to expand...
Click to collapse
Cofface seems to be a reasonable choice. Otherwise, Alka.
Pumpino said:
Cofface seems to be a reasonable choice. Otherwise, Alka.
Click to expand...
Click to collapse
You have working twrp on Redmi Note 3 pro prime?
Hemphiz said:
You have working twrp on Redmi Note 3 pro prime?
Click to expand...
Click to collapse
I'm still waiting for mine to arrive. Others have used Cofface for Kenzo on their Kate.
Pumpino said:
I'm still waiting for mine to arrive. Others have used Cofface for Kenzo on their Kate.
Click to expand...
Click to collapse
Ditto. Mine is due tomorrow. Thought I'd try and do some revision before flashing but the info I'm finding isn't quite enough for me to gain the confidence to try... May I follow you and feed off your knowledge?
Hemphiz said:
May I follow you and feed off your knowledge?
Click to expand...
Click to collapse
I'll be flashing Cofface TWRP and Xposed, but not CM at this stage. If that's helpful to you, I'll post how I go (if I ever get my hands on it).
Hy guys.. My de vice is kate. But running cm13 fine, stable and no bugs! Please check baseband for confirm, this device is Kate.
Pumpino said:
I'll be flashing Cofface TWRP and Xposed, but not CM at this stage. If that's helpful to you, I'll post how I go (if I ever get my hands on it).
Click to expand...
Click to collapse
Any info/guides would be greatly appreciated. If you stumble across anything you think might be of help for me then feel free to pm me links. I don't know much but read plenty prior to the task ahead. And thanks
DOMRuan said:
Hy guys.. My de vice is kate. But running cm13 fine, stable and no bugs! Please check baseband for confirm, this device is Kate.
Click to expand...
Click to collapse
Perhaps you could post more info. Which TWRP did you use and did you have to modify partition sizes, etc? Or was it as simple as flashing the firmware file and then the ROM itself?
Pumpino said:
Perhaps you could post more info. Which TWRP did you use and did you have to modify partition sizes, etc? Or was it as simple as flashing the firmware file and then the ROM itself?
Click to expand...
Click to collapse
Hi guys! I helped him to get this working. All things started with He didn't know that him device is Kate in first time and flashed Kenzo 7.1.8 Lollipop with modified emmc... in MiFlash to get unofficial bootloader unlock with fastboot oem unlock-go command. He got 5.1.1 Kenzo ROM working but without SIM Card detected due to flashed Kenzo modem. After it, he just flashed latest ALKA TWRP with all partitions support in fastboot and flashed latest CM nightly + GAPPS + CM13-Radios zip. It boots fine but with NO SIM Card detected too and unknown Baseband version. Don't worry. To solve it, just boot in fastboot and flash Kate modem from Kate MIUI Fastboot ROM and voila, fully working CM in Kate device! You guys with flashed TWRP can try to flash CM ROM without modify Partition sizes because CM use less space then MIUI and Kate partition sizes are same from Kenzo. Only system is bigger than Kenzo system but it works, prof of it is flashing Kenzo ROM in Kate with MiFlash don't give error like flashing Kate ROM in Kenzo.
andersonaragao said:
After it, he just flashed latest ALKA TWRP with all partitions support in fastboot and flashed latest CM nightly + GAPPS + CM13-Radios zip.
Click to expand...
Click to collapse
Thanks for the info. What does flashing CM13-Radios.zip do? If we don't flash that, would it leave Kate's default modem active? Would we need to flash the Kate modem each time we install a new nightly? Having to connect the phone to the computer every time would be a pain.
Pumpino said:
Thanks for the info. What does flashing CM13-Radios.zip do? If we don't flash that, would it leave Kate's default modem active? Would we need to flash the Kate modem each time we install a new nightly? Having to connect the phone to the computer every time would be a pain.
Click to expand...
Click to collapse
You can try it. Download CM last nightly and copy to internal storage, unlock your bootloader officially, flash ALKA TWRP recovery, go to backup and select ENTIRE PARTITIONS and do a full backup of your phone then wipe SYSTEM + DATA + CACHE + DALVIK CACHE, flash CM13 + GAPPS and reboot. This will keep your modem and all firmware partitions save. If it don't work and you get bootloop, boot in ALKA TWRP again, click in RESTORE, UNCHECK ONLY FIRMWARE PARTITION and start the restore process. This will boot MIUI again. Then start the process again but now this time, flash CM13-Radios.zip after GAPPS flash and try to boot it. When it boot, restart in bootloader and flash Kate modem and you will get fully working ROM. Or you can replace non-hlos.bin with Kate on in CM13-Radios.zip before flash it.
And no, you don't need to flash Kate modem at each new nightly because CM ROM don't comes with Modem files in it. After you get fully working CM nightly, you will get all OTA's without need a PC connect.
DOMRuan said:
Hy guys.. My de vice is kate. But running cm13 fine, stable and no bugs! Please check baseband for confirm, this device is Kate.
Click to expand...
Click to collapse
Hy, please call us...how did you unlock the bootloader from your Kate? Offical or Unofficial?
Which TWRP do you use?
Which CM13 do you flash on your Kate? The official CM13 for Kenzo?
A little instructions would be so good...Thanks!
@andersonaragao would you suggest a forum for unofficial bootloader unlock please? I'm getting network dropouts and need to flash the modems but xiaomi can take up to 7 and a half years to send an unlock code
Hemphiz said:
@andersonaragao would you suggest a forum for unofficial bootloader unlock please? I'm getting network dropouts and need to flash the modems but xiaomi can take up to 7 and a half years to send an unlock code
Click to expand...
Click to collapse
Unfortunately, to unlock bootloader unofficialy in Kate, you need to flash 5.1.1 MIUI ROM for Kenzo with modified bootloader. I think the better is stay with your stock ROM and wait more for unlock code.
andersonaragao said:
Unfortunately, to unlock bootloader unofficialy in Kate, you need to flash 5.1.1 MIUI ROM for Kenzo with modified bootloader. I think the better is stay with your stock ROM and wait more for unlock code.
Click to expand...
Click to collapse
Ok. Will do. A factory reset fixed the network issue so I can't live with that. Cheers
1. All Recoveries built for Kenzo will work without any issue on Kate as well, You can just stay with official TWRP or CM Recovery as you're pleased.
2. You can always flash the official rom back with MiFlash in EDL mode, if you happen to brick your phone.
Official ROM for Kate
Stable: http://bigota.d.miui.com/V7.3.9.0.M...DE_20160523.0000.23_6.0_global_f7170696d8.tgz
Developer: http://bigota.d.miui.com/6.8.25/kate_global_images_6.8.25_20160805.0000.29_6.0_global_195d892285.tgz
3. To install Official Cyanogenmod 13 for Kenzo on Kate (coming from MIUI), you would have to modify the build.prop and then flash the supported firmwares .zip file. One thing worth mentioning here is that, you must remove or replace NON-HLOS.bin found inside the .zip file, otherwise your phone wouldn't be able to detect the sim card. Still, you can flash only NON-HLOS.bin for Kate (from official rom) on fastboot later if you prefer to skip all the trouble modifying the firmwares .zip file. In my case, the only required files from the firmwares .zip for CM13 to run properly are just emmc_appsboot.mbn and file_contexts.
Been using the Xiaomi Redmi Note 3 (Kenzo) for a long time now and since the ROM was outdated, I decided to update it this past weekend. However for whatever reason, something broke and I've been getting bootloops. Since then, this is what I did and it still doesn't work.
Used MiFlash to fastboot flash MIUI v8.5.1.0 Global Stable, and then OTA updated to v8.5.2.0.
Test the phone to make sure all functions work properly.
Immediately officially unlocked the bootloader using Mi Unlock.
Fastboot flashed TWRP 3.1.1.0.
Made EFS and ROM backups as usual.
Clean flashed Resurrection Remix 5.7.4 (Radon kernel) with /data and /cache as F2FS.
Flashed Open Gapps 6.0 ARM64 Mini.
Right now, I'm back to running stock MIUI v8.5.1.0, which was flashed using MiFlash. Then I did the OTA update to MIUI v8.5.2.0. May someone please guide me or correct the above steps in order to install the linked Resurrection Remix ROM? Or maybe a Nougat ROM?
geokilla said:
Been using the Xiaomi Redmi Note 3 (Kenzo) for a long time now and since the ROM was outdated, I decided to update it this past weekend. However for whatever reason, something broke and I've been getting bootloops. Since then, this is what I did and it still doesn't work.
Used MiFlash to fastboot flash MIUI v8.5.1.0 Global Stable, and then OTA updated to v8.5.2.0.
Test the phone to make sure all functions work properly.
Immediately officially unlocked the bootloader using Mi Unlock.
Fastboot flashed TWRP 3.1.1.0.
Made EFS and ROM backups as usual.
Flashed Resurrection Remix 5.7.4 (Radon kernel) with /data and /cache as F2FS.
Flashed Open Gapps 6.0 ARM64 Mini.
Right now, I'm back to running stock MIUI v8.5.1.0, which was flashed using MiFlash. Then I did the OTA update to MIUI v8.5.2.0. May someone please guide me or correct the above steps in order to install the linked Resurrection Remix ROM? Or maybe a Nougat ROM?
Click to expand...
Click to collapse
Try without f2fs. Use ext4
geokilla said:
Been using the Xiaomi Redmi Note 3 (Kenzo) for a long time now and since the ROM was outdated, I decided to update it this past weekend. However for whatever reason, something broke and I've been getting bootloops. Since then, this is what I did and it still doesn't work.
Used MiFlash to fastboot flash MIUI v8.5.1.0 Global Stable, and then OTA updated to v8.5.2.0.
Test the phone to make sure all functions work properly.
Immediately officially unlocked the bootloader using Mi Unlock.
Fastboot flashed TWRP 3.1.1.0.
Made EFS and ROM backups as usual.
Flashed Resurrection Remix 5.7.4 (Radon kernel) with /data and /cache as F2FS.
Flashed Open Gapps 6.0 ARM64 Mini.
Right now, I'm back to running stock MIUI v8.5.1.0, which was flashed using MiFlash. Then I did the OTA update to MIUI v8.5.2.0. May someone please guide me or correct the above steps in order to install the linked Resurrection Remix ROM? Or maybe a Nougat ROM?
Click to expand...
Click to collapse
Flash LOS 13 which is far stable than the RR 5.7.4. You should've flashed another rom before moving back to MIUI. The process you followed is correct but you also need to flash the compatible firmware like for RR you need CM13 firmare and for LOS you'll the recommended firmware posted in the thread itself.
I went through some ROM threads and one recommended flashing MIUI8 Global DEVELOPER and not Global STABLE. Am I supposed to be using MIUI 8 Global DEVELOPER as the starting point?
vistaabalaji said:
Try without f2fs. Use ext4
Click to expand...
Click to collapse
EXT4 had the same issue. Just bootloops forever.
naturist said:
Flash LOS 13 which is far stable than the RR 5.7.4. You should've flashed another rom before moving back to MIUI. The process you followed is correct but you also need to flash the compatible firmware like for RR you need CM13 firmare and for LOS you'll the recommended firmware posted in the thread itself.
Click to expand...
Click to collapse
The Resurrection Remix build I linked is based off of LineageOS 13 so it should be stable.
So you're saying I missed flashing a firmware? I see some ROMs recommend flashing the firmware, while others don't. Which is the proper firmware to flash if the ROM thread doesn't state which firmware to use?
geokilla said:
I went through some ROM threads and one recommended flashing MIUI8 Global DEVELOPER and not Global STABLE. Am I supposed to be using MIUI 8 Global DEVELOPER as the starting point?
EXT4 had the same issue. Just bootloops forever.
The Resurrection Remix build I linked is based off of LineageOS 13 so it should be stable.
So you're saying I missed flashing a firmware? I see some ROMs recommend flashing the firmware, while others don't. Which is the proper firmware to flash if the ROM thread doesn't state which firmware to use?
Click to expand...
Click to collapse
The one on this thread. Second post.
well seems to be a new problem...
so what must be done... i will suggest to get latest miui fastboot rom from here
https://forum.xda-developers.com/redmi-note-3/how-to/links-direct-official-download-links-t3449488
flash it via mi flash tool (im running 64 bit os ,so using mi flash beta ) in edl mode by wiping full things including storage..
if your boot loader is unlocked official way it must be unlocked now also if not i guess you know how to unlock it officially.
then use official twrp from
www.twrp.me
i faced this issue once and did the exact steps above and now no problem..
by the way i tried things like unplugging battery from the board... lol... read in miui forum...
I've been having very similar issues (updated official firmware in a non officially unlocked bootloader).
It's been hell but I've managed to get los14.1 installed. Now my issue lies with constant gapps crashes. I'm thinking of just giving up and getting miui.
Felheipe said:
I've been having very similar issues (updated official firmware in a non officially unlocked bootloader).
It's been hell but I've managed to get los14.1 installed. Now my issue lies with constant gapps crashes. I'm thinking of just giving up and getting miui.
Click to expand...
Click to collapse
use latest gapps.outdated or older one causes crashes...
adithyan25 said:
use latest gapps.outdated or older one causes crashes...
Click to expand...
Click to collapse
One would think so but in reality is the other way around. I'm using a 20170303 and it has been the most stable version across all my devices and so on.
Felheipe said:
One would think so but in reality is the other way around. I'm using a 20170303 and it has been the most stable version across all my devices and so on.
Click to expand...
Click to collapse
seriously the one from march??
dude just download older gapps wont work on latest updates. ot will force close for sure...
at least try before telling ..use latest one from opengapps... there is a reason they are updating tje sote everyday...ftom the may builds you need latest gapps as petr release dates... just give a try ..its only 150 mb or so.... i can vonform its duw to outdated gapps
adithyan25 said:
well seems to be a new problem...
so what must be done... i will suggest to get latest miui fastboot rom from here
https://forum.xda-developers.com/redmi-note-3/how-to/links-direct-official-download-links-t3449488
flash it via mi flash tool (im running 64 bit os ,so using mi flash beta ) in edl mode by wiping full things including storage..
if your boot loader is unlocked official way it must be unlocked now also if not i guess you know how to unlock it officially.
then use official twrp from
www.twrp.me
i faced this issue once and did the exact steps above and now no problem..
by the way i tried things like unplugging battery from the board... lol... read in miui forum...
Click to expand...
Click to collapse
That's exactly what I did, as I mentioned in OP lol. Except I wasn't flashing MIUI 8 in EDL mode.
adithyan25 said:
seriously the one from march??
dude just download older gapps wont work on latest updates. ot will force close for sure...
at least try before telling ..use latest one from opengapps... there is a reason they are updating tje sote everyday...ftom the may builds you need latest gapps as petr release dates... just give a try ..its only 150 mb or so.... i can vonform its duw to outdated gapps
Click to expand...
Click to collapse
I tried 0625 and the newest one. 0303 is the latest stable Google play services (as far as i am aware).
Felheipe said:
I tried 0625 and the newest one. 0303 is the latest stable Google play services (as far as i am aware).
Click to expand...
Click to collapse
no idont guess so...
pls try after downloading latest one from here
www.opengapps.org
arm64-7.1- pico(if you want Google assistant you must use nano or above)
iam using yesterday build of opengapps and not facing any issues...and do a clean flash if possible...
or else you can tru beansgapps....
edit:- playservices had updated many times after 0303.. so i can say its outdated
adithyan25 said:
no idont guess so...
pls try after downloading latest one from here
www.opengapps.org
arm64-7.1- pico(if you want Google assistant you must use nano or above)
iam using yesterday build of opengapps and not facing any issues...and do a clean flash if possible...
or else you can tru beansgapps....
Click to expand...
Click to collapse
I've tried yesterdays version. Play store wouldn't even open. Dirty flashed 0625 play store opens but a lot of apps crash, everything works fine with 0303.
I'm flashing miui and I'm going to try the official bootloader unlock, but this have been a couple of strange days.
Felheipe said:
I've tried yesterdays version. Play store wouldn't even open. Dirty flashed 0625 play store opens but a lot of apps crash, everything works fine with 0303.
I'm flashing miui and I'm going to try the official bootloader unlock, but this have been a couple of strange days.
Click to expand...
Click to collapse
dirty flashing isn't a solution ... theres changes in trees of the rom and kernel..
anyway head back to miui unlocl officially and when coming back to custom rom do wipe everything and give it a shot..probably the crash may be due to over written or exiating files...
happy flashing
~peace
I should mention I clean flashed the ROMs. Updated OP.
Ok trying it again right now and so far, this is what I did:
Used MiFlash to fastboot flash MIUI v7.7.6 Global DEV.
Test the phone to make sure all functions work properly.
Tried to unlock bootloader using Mi Unlock but it said bootloader is already unlocked.
Boot into MIUI again.
Fastboot flashed TWRP 3.1.1.0.
No boot into MIUI.
Flash Kenzo firmware 8.2.4.0 in TWRP
Clean flash LineageOS 13 and Open Gapps 6.0 ARM64 Mini with /data and /cache in EXT4
IT WORKS!
I guess now I'll try Resurrection Remix.
My phone is Redmi Note 3 SE (Kate), I have a big problem long time, when I open Airplane and close it again, I can connect LTE or H+ or any data signal (I can call anyone and send messenge just can't connect to internet), but if I reboot or fastreboot then I can connect to data signal, who can help me to fix this bug, i try another rom and flash kate firmware but didn't fix it.
Push
Have you any specific VPN app installed?
mehrshad.shafaghi said:
Have you any specific VPN app installed?
Click to expand...
Click to collapse
No
Help
changchiyin said:
Help
Click to expand...
Click to collapse
Hey bro which rom are u in??
AOSP or Miui??
If Miui than download fastboot rom and flash it using mi flash.
If aosp rom, update to latest firmware and try a different rom
But the fastboot rom flashing should fix the issue.
I had this exact bug too. I'm on official LineageOS 14.1 with a kate model.
My bug went away after an update of LineageOS and I think more importantly an update of my firmware that I downloaded from here:
https://forum.xda-developers.com/redmi-note-3/development/firmware-hmnote3proglobal-t3574361
I've firmware version 8.2.1 and LineageOS 20180214-nightly. I flashed the firmware without the emmc_appsboot.mbn file.
I would suggest to flash a new firmware and see if the bug goes away.
Androbots said:
Hey bro which rom are u in??
AOSP or Miui??
If Miui than download fastboot rom and flash it using mi flash.
If aosp rom, update to latest firmware and try a different rom
But the fastboot rom flashing should fix the issue.
Click to expand...
Click to collapse
Nitrogen OS，i try many rom all of them have this bug but not for everyone just for me
changchiyin said:
just for me
Click to expand...
Click to collapse
No, check my post.
So after checking the Xiaomi firmware site (didn't work, flashing the weekly firmware just appeared as stable) I haven't been able to get the developer firmware.
Does anybody know where I can get a hold of it without the MIUI ROM.
(It's needed for the latest Pixel Experience update and it isn't included with the update)
Title is meant to say MIUI ROM not room, autocorrect sorry.
dudeisbrendan03 said:
So after checking the Xiaomi firmware site (didn't work, flashing the weekly firmware just appeared as stable) I haven't been able to get the developer firmware.
Does anybody know where I can get a hold of it without the MIUI ROM.
(It's needed for the latest Pixel Experience update and it isn't included with the update)
Title is meant to say MIUI ROM not room, autocorrect sorry.
Click to expand...
Click to collapse
Always go here for latest vendor firmwares
https://mirror.akhilnarang.me/MIUI/beryllium/
and never use beryllium-V10.1.3.0-9.0-vendor-firmware.zip - this is an older version, even though the version number is higher than 9.
jackiass said:
and never use beryllium-V10.1.3.0-9.0-vendor-firmware.zip - this is an older version, even though the version number is higher than 9.
Click to expand...
Click to collapse
Whats going to happen if i flash the latest 9.2.25 vendor fw on global stable 10.2.2.0???
I get the same message when I want to install the ROM. I'm stuck and don't know what to do? Has anyone any tips to succesfully install the Pixel Experience ROM on a Pocophone?
DFlower said:
I get the same message when I want to install the ROM. I'm stuck and don't know what to do? Has anyone any tips to succesfully install the Pixel Experience ROM on a Pocophone?
Click to expand...
Click to collapse
Have you tried doing the above steps mentioned??
I mean..
Download and install via twrp the latest vendor firmware ,, about 400mb in size..
Then flash fde... Then flash the PE rom???
santiagoruel13 said:
Have you tried doing the above steps mentioned??
I mean..
Download and install via twrp the latest vendor firmware ,, about 400mb in size..
Then flash fde... Then flash the PE rom???
Click to expand...
Click to collapse
Thanks for your help, I used the wrong firmware version. I now used this file/version ->beryllium-9.2.25-9.0-vendor-firmware.zip and this worked fine !
From the link you mentioned -> https://mirror.akhilnarang.me/MIUI/beryllium/
DFlower said:
Thanks for your help, I used the wrong firmware version. I now used this file/version ->beryllium-9.2.25-9.0-vendor-firmware.zip and this worked fine !
From the link you mentioned ->
Click to expand...
Click to collapse
cva_kabil said:
Always go here for latest vendor firmwares
Click to expand...
Click to collapse
Is this dev or stable firmware?
dudeisbrendan03 said:
Is this dev or stable firmware?
Click to expand...
Click to collapse
Dev. That's why you need it even though you are coming from the latest official miui.
How to get a phone mi mix3
I am facing gps weak signal in custom rom I use various rom with all firmware but all result r same
U should use one custom rom with its appropriate firmware only obviously vendor is included everywhere nowadays
Which roms u tried ?
choose accuracy of gps and go outside
I was on Pigs lineage for two month and now on pe but same problem and now I can't go back to miui 12 anyone share link how to flash stock rom
aslam2121 said:
I was on Pigs lineage for two month and now on pe but same problem and now I can't go back to miui 12 anyone share link how to flash stock rom
Click to expand...
Click to collapse
Choose your firmware , correct version (global, EEA, China, Russia) and build:
https://mirom.ezbox.idv.tw/en/phone/davinci/
Check this forum (use search function) for flashing stock firmware.
You should know that there are two different kinds, recovery firmware to flash from TWRP (.zip ending) or fastboot firmware (.tgz ending) to flash by fastboot or Mi tool).
Sent from my Mi 9T using XDA Labs
I use gps everyday on lineage latest ROM and no problem, so your issue is related to settings or hardware
yaro666 said:
I use gps everyday on lineage latest ROM and no problem, so your issue is related to settings or hardware
Click to expand...
Click to collapse
Maybe reverting to miui and flashing back lineage will solve problem
Wolfcity said:
Choose your firmware , correct version (global, EEA, China, Russia) and build:
https://mirom.ezbox.idv.tw/en/phone/davinci/
Check this forum (use search function) for flashing stock firmware.
You should know that there are two different kinds, recovery firmware to flash from TWRP (.zip ending) or fastboot firmware (.tgz ending) to flash by fastboot or Mi tool).
Sent from my Mi 9T using XDA Labs
Click to expand...
Click to collapse
Can i flash twrp rom? Or i have to flash any firmware