Hello,
Currently running RR Rom but I'm running it with a lots of bugs like proximity sensor, auto rotate does not work. Except that everything works great. Can anyone suggest me a ROM so I can get over this problems.
Thank you.
For sure, i use latest xiaomi.eu rom and have non of this bugs
The only problem for me is that I'm in love with stock android. I had a Nexus 5x before.
NitrogenOS
Just flash with MiFlash latest global dev fastboot rom with flash_all option.
Set it up, enable usb debbugging, OEM unlock, check that you are unlocked.
Flash ZCX twrp, backup all partitions to microSD(46 or so), format data, wipe all partitions except microSD.
Flash NitrogenOS
AOSPExtended
ionutarbanasi said:
Hello,
Currently running RR Rom but I'm running it with a lots of bugs like proximity sensor, auto rotate does not work. Except that everything works great. Can anyone suggest me a ROM so I can get over this problems.
Thank you.
Click to expand...
Click to collapse
Did u root it wit super su
What do you mean? I flash kate firmware, rom, gapps, and install kate modem.. whats wrong?
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.
Hello people, i just bought RN3 (Indian version with FPC sensor), i unlocked unofficially by flashing MIUI 7.1 and installed AICP 11 MM just after that, do i had to flash CM13 Firmware first?
Everything works fine but sometimes screen glitches and phone freezes so i have to force reboot it.
So should i now flash CM firmware? if yes with which TWRP? i'm using official twrp 3.0.2-2, reply soon....
Edit- solved
Flash CM firmware if your ROM is CM based at all, of course. If not, look for something in the ROM thread.
Dev.Katalyst said:
Hello people, i just bought RN3 (Indian version with FPC sensor), i unlocked unofficially by flashing MIUI 7.1 and installed AICP 11 MM just after that, do i had to flash CM13 Firmware first?
Everything works fine but sometimes screen glitches and phone freezes so i have to force reboot it.
So should i now flash CM firmware? if yes with which TWRP? i'm using official twrp 3.0.2-2, reply soon....
Click to expand...
Click to collapse
Personally I always flash it anyway. Fixes a few bugs like settings FC etc.
Dev.Katalyst said:
Hello people, i just bought RN3 (Indian version with FPC sensor), i unlocked unofficially by flashing MIUI 7.1 and installed AICP 11 MM just after that, do i had to flash CM13 Firmware first?
Everything works fine but sometimes screen glitches and phone freezes so i have to force reboot it.
So should i now flash CM firmware? if yes with which TWRP? i'm using official twrp 3.0.2-2, reply soon....
Click to expand...
Click to collapse
Dev.Katalyst,
any news with your glitches issue ?
did you successed solving it?
iTaisHi said:
Dev.Katalyst,
any news with your glitches issue ?
did you successed solving it?
Click to expand...
Click to collapse
yes, that was live display bug in old kernels. fixed after a week of this post.
Hi,
I have been using Nexys Experience ROM and I am in love with it. However, recently I wanted to try a 7.1 ROM. I am officially bootloader unlocked and currently using twrp-3.0.M4-0
The problem I am facing, no matter how I try, I cannot boot any 7.1 ROM. I have tried RR, CM14.1 and their respective firmware but after flashing the ROMs never boot and stuck on bootlogo.
Possible Combinations I tried:
1) Flashed CM14.1 Firmware
2) Flashed CM14.1 ROM + Gapps
Result: Stuck on Bootlogo animation
1) Flashed CM14.1 ROM + Gapps
2) Flashed CM14.1 Firmware
Result: Stuck on Bootlogo animation
1) Flashed RR ROM + Gapps
2) Flashed CM14.1 Firmware
Result: Stuck on Bootlogo animation
I use f2fs on /data and /cache
Any probable solution?
Is there any errors occurred during flashing process?
Sent from my Redmi Note 3 using Tapatalk
Nevermind, I reformatted /data and /cache using ext4 again and flashed EU Rom. Seems to be working. I tried EU rom before but it wasn't working because of f2fs.
Will try any 14.1 rom soon.
saiftheboss7 said:
Nevermind, I reformatted /data and /cache using ext4 again and flashed EU Rom. Seems to be working. I tried EU rom before but it wasn't working because of f2fs.
Will try any 14.1 rom soon.
Click to expand...
Click to collapse
Glad to hear that u overcame ur problem by yourself, and good luck mate.
Sent from my Redmi Note 3 using Tapatalk
f2fs is good but as I will need to go back & forth MIUi & CM/AOSP I guess it's better to stay on EXT4 for now. Until MIUI adds f2fs support.
@saiftheboss7
Hows nexus rom? Is it better then miui in terms of performance and stability? And dual sims are working on nexus experience rom?
I am currently on latest Miui 8 MM 6.12.8 (Epic Rom).. I have ZCX twrp installed and bootloader unlocked officially, can you guide where to start so that I can go back and forth Miui Cm/AOSP, I mean is there anything which need to be backed up before moving to nexus rom so that I can easily come back to Miui 8 MM..
Sent from my Redmi Note 3 using Tapatalk
IMO Nexus Experience is the most stable ROM I used. And the dev doesn't push any useless updates. In my usage, it was so much better than miui. I didn't try dual sim because I have only single sim. But should work without any trouble.
If you are official unlocked first flash the twrp recovery from TheStrix's CM thread. After twrp you can install any MIUI from Xiaomi Eu via the twrp recovery. They update the rom when there is a new stable release. Xiaomi eu roms are better than global rom because it does not have unnecessary softwares and also the china based rom which is more stable and optimized. I also used a debloating script that stripped away all junks of MIUI.
If you want to switch from miui, flash any custom rom using the same procedure. However, you should always do a wipe (factory reset) before flashing any rom.
saiftheboss7 said:
IMO Nexus Experience is the most stable ROM I used. And the dev doesn't push any useless updates. In my usage, it was so much better than miui. I didn't try dual sim because I have only single sim. But should work without any trouble.
If you are official unlocked first flash the twrp recovery from TheStrix's CM thread. After twrp you can install any MIUI from Xiaomi Eu via the twrp recovery. They update the rom when there is a new stable release. Xiaomi eu roms are better than global rom because it does not have unnecessary softwares and also the china based rom which is more stable and optimized. I also used a debloating script that stripped away all junks of MIUI.
If you want to switch from miui, flash any custom rom using the same procedure. However, you should always do a wipe (factory reset) before flashing any rom.
Click to expand...
Click to collapse
Thank you very much for guidance, I need both of my sims to work so its my main concern, If somebody is using dual sims on NX experience rom 10.4 kindly let me know so that I can flash it as well.
There is twrp-3.0.M4-0 recovery recommended by TheStrix on his CM thread, is this the one?
If we check nexus experience rom's page, they have recommended to use alka recovery only, kindly check below:
http://en.miui.com/thread-357205-1-1.html
And which version of Radon Kernel you are using? Is it 3.2?
Best Regards,
Sent from my Redmi Note 3 using Tapatalk
@saiftheboss7
NX Experience is a very nice and smooth rom I have just installed it and I'm loving it.
Kindly let me know how to enable screenshot button in notification panel? I can't find it anywhere.. The only thing which I am missing right now coming from Miui, is three fingers swipe down to take screenshot, is there any alternative?
Did you install Xposed Framework? If yes then which version and from where did you download it..
Thanks & Best Regards,
Hey guys, I want to switch to LOS14.1 by TheStrix, because it is now stable and bug-free.
There are some other things i want to flash too, so I just wanted to clear things up a bit.
I want to flash radon kernel, Arise sound mod, and magisk, because apparently magisk will allow me to use banking apps.
From referring to other people on the forum, i have the following:
1)Flash CM14 Firmware
2)Flash ROM
3)Flash GAPPS
4)Flash Radon Kernel
5)Reboot and setup phone
6)Flash magisk
7)Enable hide root
8)Flash Arise sound mod with arise magisk compatibility module.
So I have some questions regarding this procedure.
Do I have to flash supersu before flashing Magisk?
Is it worth it to switch data and cache to F2FS?
Do I need to switch recoveries to do this?
Is this the right order to flash the ROM and accompanying zips?
I am using the snapdragon redmi note 3 with fpc fingerprint sensor.
I have an officially unlocked bootloader.
I am currently on RR_MM official.
I would test it out myself, but i'm in college, so i don't really have time to do that.
If anyone would share their experiences or give me some pointers, it would be much appreciated.
No you must switch to RR n
[email protected] said:
No you must switch to RR n
Click to expand...
Click to collapse
Why is it a must to switch to rr n over los?
I actually don't really mind using either ROM, but I wanted to test out LOS for a while.
No its laggy too much
what i just did in the beginning was to wipe everything except the external sd card.
i would suggest to run the rom the rom first time without new kernel. i just updated my RR Nougat to todays release and wanted to flash radon just ahead, had some errors in recovery doing so. did a reboot, new rom was there but no radon. again flashing within recovery and no problems. with arise i have no clue, i dont use it
Quote from the Radon kernel v4.3 changelog, applicable to your step 4, 5 and 6.
Umang96 said:
If your rom uses magisk root, then don't flash radon immediately after rom, first boot to system once.
Click to expand...
Click to collapse
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.