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.
clean flashing 0415 build giving me bootloops. after 20 mins, the nitrogen boot animation still ongoing, no welcome screen or nothing.
pls somebody help if 0415 build flashed successfully...
i tried both with latest gapps/dynamic apps. still stuck at nitrogen boot animation
(ps: i had the 0331 build downloaded, clean flashing that build boots normally, no issue. but 0415 giving me bootloop. even dirty flashing over 0331 build)
is ResetScreenLockv2.zip flashing mandatory? i only skipped that part as i was clean flashing.
PLEASE REPLY IF ANYONE IS ABLE TO FLASH 0415 (LATEST) BUILD
+1 I have this problem also on kate, cannot boot this rom, with or without gapps...
Sent from my Redmi Note 3 SE
My posts are not sending on forms page.anybody help me
yes , that build seems odd, I'm having same problem too
LoL people..it has been answered 100 times.
You need to be on MM bootloader for new builds...
If you never flashed MM fastboot ROM on your device, then you are still on LP bootloader.
You must flash fastboot rom and then unlock it officialy...in that case it will work fine and you dont need to flash anything
Easy way is to flash MM bootloader;
https://forum.xda-developers.com/re...11-01-2017-t3536211/post71942715#post71942715
Denis:) said:
LoL people..it has been answered 100 times.
You need to be on MM bootloader for new builds...
If you never flashed MM fastboot ROM on your device, then you are still on LP bootloader.
You must flash fastboot rom and then unlock it officialy...in that case it will work fine and you dont need to flash anything
Easy way is to flash MM bootloader;
https://forum.xda-developers.com/re...11-01-2017-t3536211/post71942715#post71942715
Click to expand...
Click to collapse
MM fastboot rom was flashed many days ago.
nos 7.1.1 builds work perfectly. i dont know what happened to later builds.
LOS, RR, AEX all 7.1.2 roms working. only NOS is stuck at the very first boot animaton
I have successfully flashed and have been using the 15th April build, for the last 3 days.
I am also using build
theincognito said:
I have successfully flashed and have been using the 15th April build, for the last 3 days.
Click to expand...
Click to collapse
pls share some detail
1. which rom were u using befor flashing nos
2. which twrp
3. flashing steps
Simoom Sadik said:
pls share some detail
1. which rom were u using befor flashing nos
2. which twrp
3. flashing steps
Click to expand...
Click to collapse
1. 13th April test build of NOS
2. Dadi11's unofficial twrp. 3.1.0
3. Simple dirty flash.
I'm also using 15.04 build. Installed clean, after formatted everything, except sd card. Everything is working. I'm using Unofficial 7.1.2. Dynamic Gapps found in NOS thread. Came from RR 7.1.1.
Flash ROM then boot into it. After that reboot to twrp and flash the gapps.
Is there any way to update lineage os without flashing latest miui & unlock official
Please suggest a way out so that i can update to latest lineage os builds without flashing official miui and unlocking bootloader officially.
kaveeshnayak92 said:
Please suggest a way out so that i can update to latest lineage os builds without flashing official miui and unlocking bootloader officially.
Click to expand...
Click to collapse
you can't do it, without update firmware your phone just bootloop not booting into system
For the love of all that is sweet, just do the following:
1. flash unlock_bootloader.zip from the LineageOS thread.
2. Flash Psy_Man's latest firmware ( Kenzo or Kate, whetever you need ).
3. Flash latest LineageOS nightly.
4. Clear Dalvik & Cache.
Influx of people that don't know what they are supposed to know makes this forum become the place where blind are leading the blind...
Can u please give the link of "unlock_bootloader.zip" file I cannot find it. Thanks
Tomo123 said:
For the love of all that is sweet, just do the following:
1. flash unlock_bootloader.zip from the LineageOS thread.
2. Flash Psy_Man's latest firmware ( Kenzo or Kate, whetever you need ).
3. Flash latest LineageOS nightly.
4. Clear Dalvik & Cache.
Influx of people that don't know what they are supposed to know makes this forum become the place where blind are leading the blind...
Click to expand...
Click to collapse
Thanks in advance!
Tomo123 said:
For the love of all that is sweet, just do the following:
1. flash unlock_bootloader.zip from the LineageOS thread.
2. Flash Psy_Man's latest firmware ( Kenzo or Kate, whetever you need ).
3. Flash latest LineageOS nightly.
4. Clear Dalvik & Cache.
Influx of people that don't know what they are supposed to know makes this forum become the place where blind are leading the blind...
Click to expand...
Click to collapse
Me too needs this i unlocked my bootloader unofficially
Tomo123 said:
For the love of all that is sweet, just do the following:
1. flash unlock_bootloader.zip from the LineageOS thread.
2. Flash Psy_Man's latest firmware ( Kenzo or Kate, whetever you need ).
3. Flash latest LineageOS nightly.
4. Clear Dalvik & Cache.
Influx of people that don't know what they are supposed to know makes this forum become the place where blind are leading the blind...
Click to expand...
Click to collapse
Hey mate, I have a locked device without root. Complete stock latest MIUI. Can I follow this procedure and flash lineageOS 14 safely? Just want to be sure before proceeding.
Tomo123 said:
1. flash unlock_bootloader.zip from the LineageOS thread.
2. Flash Psy_Man's latest firmware ( Kenzo or Kate, whetever you need ).
3. Flash latest LineageOS nightly.
4. Clear Dalvik & Cache.
Click to expand...
Click to collapse
Is it okay if I flash the latest firmware from here in TWRP: https://forum.xda-developers.com/redmi-note-3/development/firmware-hmnote3proglobal-t3574361 without flashing unlock_bootloader.zip? I had my bootloader officially unlocked.
TheRay said:
Is it okay if I flash the latest firmware from here in TWRP: https://forum.xda-developers.com/redmi-note-3/development/firmware-hmnote3proglobal-t3574361 without flashing unlock_bootloader.zip? I had my bootloader officially unlocked.
Click to expand...
Click to collapse
The unlock_bootloader.zip is for unlock unofficially only.
If u unlock officially u don't need it.
TheRay said:
Is it okay if I flash the latest firmware from here in TWRP: https://forum.xda-developers.com/redmi-note-3/development/firmware-hmnote3proglobal-t3574361 without flashing unlock_bootloader.zip? I had my bootloader officially unlocked.
Click to expand...
Click to collapse
If you had your bootloader officially unlocked then do it the normal way, why even go to shady paths and get compatibility issues in future.
The thing is all those firmwares which claims that bootloader won't be unlocked just removes bootloader from firmware, so it doesn't get upgraded but if you're on lollipop bootloader you have to do it the official way otherwise you will bootloop.
shashankpal said:
If you had your bootloader officially unlocked then do it the normal way, why even go to shady paths and get compatibility issues in future.
Click to expand...
Click to collapse
And what is the normal way?
TheRay said:
And what is the normal way?
Click to expand...
Click to collapse
Flash the firmware given by thestrix, and if your bootloader dosen't get locked you're on mm bootloader and fine to flash 7.1.2 roms. But if bootloader gets locked(which means you were on lollipop bootloader) then you have to flash latest miui dev rom through edl and unlock it again through miui unlock( it won't give you 50% error again).
shashankpal said:
Flash the firmware given by thestrix, and if your bootloader dosen't get locked you're on mm bootloader and fine to flash 7.1.2 roms. But if bootloader gets locked then you have to flash latest miui dev rom through edl and unlock it again through miui unlock( it won't give you 50% error again).
Click to expand...
Click to collapse
I am on an old LOS build right now. So all I have to do is flash this https://www.androidfilehost.com/?fid=817550096634767927 in TWRP and I will be on latest firmware. And then I should be able to flash the new LOS builds without any error 7. Is that correct?
TheRay said:
I am on an old LOS build right now. So all I have to do is flash this https://www.androidfilehost.com/?fid=817550096634767927 in TWRP and I will be on latest firmware. And then I should be able to flash the new LOS builds without any error 7. Is that correct?
Click to expand...
Click to collapse
Yep, if bootloader doesn't get locked you're good to go. Otherwise you have to do all the process I have explained above.
My RN3 (Kenzo) is running miui 7,unlocked bootloader and twrp installed. But whenever I install any rom it bootloops. First I tried to flash XENONHD it gets stuck in the xenonhd bootanimation and after that I flashed Pixel rom in this rom it never gets beyond the google boot logo. What's wrong with my device? Please guide me to fix this.
is there a way to know what version of bootloader we have ? (LL or MM)
Not directly, but if you remember where you have got it, you can guess.
amandutta01 said:
My RN3 (Kenzo) is running miui 7,unlocked bootloader and twrp installed. But whenever I install any rom it bootloops. First I tried to flash XENONHD it gets stuck in the xenonhd bootanimation and after that I flashed Pixel rom in this rom it never gets beyond the google boot logo. What's wrong with my device? Please guide me to fix this.
Click to expand...
Click to collapse
It means you're on LP bootloader. If you have officially unlocked, to upgrade to MM bootloader, flash the latest MIUI or the firmware provided by TheStrix on LOS official thread(this will relock your bootloader), go to fastboot, plug device and unlock via Mi Unlock. If you did it unofficially then read a few post back, someone posted a fix.
cyril5689 said:
is there a way to know what version of bootloader we have ? (LL or MM)
Click to expand...
Click to collapse
Nope.... well you can flash TheStrix's firmware, if your phone boots up then you're on MM, if it didn't(Mi logo flashes for a second before turning off again) then LP . Or try a safer way but you needed to download a full ROM. Download the latest LOS(or any latest LOS based ROM), flash it, if you get bootloop then you're on LP bootloader.
bloodytolits said:
Nope.... well you can flash TheStrix's firmware, if your phone boots up then you're on MM, if it didn't(Mi logo flashes for a second before turning off again) then LP . Or try a safer way but you needed to download a full ROM. Download the latest LOS(or any latest LOS based ROM), flash it, if you get bootloop then you're on LP bootloader.
Click to expand...
Click to collapse
Thx for your help.
I've flashed 2 firmwares on my kate(whithout emmc-appsboot.mbn file in it):
7.5.25 (beta) and 8.2.4.0 (stable).
I've got no problem when flashig both, but when I flash Resurection remix (last build which is based on LOS) I stuck on bootanimation. But i don't think it's a bootloop because my phone dont restart(Black screen + MI logo + bootanimation). it just stay on bootanimation and never boot (ask for pin)
Wait but why do you need to unlock officially​?? I unlocked unofficially and flashed lineage (i mean cm14.1) and it worked like a charm. Though you need the firmware.
Sent from my Pixel XL using Tapatalk
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.
Hello! I've been trying to install a custom ROM on my SM-J400M for a while now and none worked, recently i tried installing Magisk on it and now it is in a bootloop . Is there any custom ROM compatible with my device? Or it is impossible to install a custom ROM on it? At the moment it seems like it is not even rootable...
Also the version of TWRP that i installed on my device says that it is an SM-J400F instead of a SM-J400M which is the actuall name of the model. Is that a problem? If so please tell me how to unistall it, i wasnt able to find any way to uninstal TWRP on a soft-bricked phone.
Thanks in Advance!
TheChadGamer said:
Hello! I've been trying to install a custom ROM on my SM-J400M for a while now and none worked, recently i tried installing Magisk on it and now it is in a bootloop . Is there any custom ROM compatible with my device? Or it is impossible to install a custom ROM on it? At the moment it seems like it is not even rootable...
Also the version of TWRP that i installed on my device says that it is an SM-J400F instead of a SM-J400M which is the actuall name of the model. Is that a problem? If so please tell me how to unistall it, i wasnt able to find any way to uninstal TWRP on a soft-bricked phone.
Thanks in Advance!
Click to expand...
Click to collapse
I've managed to un-brick my phone! Still found no way to install a custom ROM on it tho...
TheChadGamer said:
Hello! I've been trying to install a custom ROM on my SM-J400M for a while now and none worked, recently i tried installing Magisk on it and now it is in a bootloop . Is there any custom ROM compatible with my device? Or it is impossible to install a custom ROM on it? At the moment it seems like it is not even rootable...
Also the version of TWRP that i installed on my device says that it is an SM-J400F instead of a SM-J400M which is the actuall name of the model. Is that a problem? If so please tell me how to unistall it, i wasnt able to find any way to uninstal TWRP on a soft-bricked phone.
Thanks in Advance!
Click to expand...
Click to collapse
Is There Any Custom ROM for Samsung Galaxy J4?
YES!
Although, this is not specific Custom ROM for this device. This ROM is GSI (Generic System Image), and J4 is greatly support it! (Because it has Android Oreo out-of-box)
How to install it?
Easy, install TWRP from TwrpBuilder's Github, flash GSI Image as usual, flash magisk (if bootloop, flash this might help), and done!
Please note that this is GSI, bugs are widely open. But, as far as I use J4, the only bug I feel are Camera and MTP (fixed by using custom kernel)
Edit: For your TWRP, which version you install?
RedLine_27 said:
Is There Any Custom ROM for Samsung Galaxy J4?
YES!
Although, this is not specific Custom ROM for this device. This ROM is GSI (Generic System Image), and J4 is greatly support it! (Because it has Android Oreo out-of-box)
How to install it?
Easy, install TWRP from TwrpBuilder's Github, flash GSI Image as usual, flash magisk (if bootloop, flash this might help), and done!
Please note that this is GSI, bugs are widely open. But, as far as I use J4, the only bug I feel are Camera and MTP (fixed by using custom kernel)
Edit: For your TWRP, which version you install?
Click to expand...
Click to collapse
Thanks for the reply!
I recently discovered that my Samsung J4 is carrier locked so i don't think it is possible to flash a custom ROM in it...
I really tried many things since this post but in the end it would always get stuck in a boot loop and i would have to flash the official firmware in it to restore it.
What TWRP version did i use?
I honestly don't remember but it probably was a unofficial TWRP 3.2.3 or something similar, not sure if it was unofficial or not but it seemed to work...
Also, how would i go around getting a custom kernel to use on the device that would fix those problems?
Again, thanks for replying!
-TheChadGamer
TheChadGamer said:
Thanks for the reply!
I recently discovered that my Samsung J4 is carrier locked so i don't think it is possible to flash a custom ROM in it...
I really tried many things since this post but in the end it would always get stuck in a boot loop and i would have to flash the official firmware in it to restore it.
What TWRP version did i use?
I honestly don't remember but it probably was a unofficial TWRP 3.2.3 or something similar, not sure if it was unofficial or not but it seemed to work...
Also, how would i go around getting a custom kernel to use on the device that would fix those problems?
Again, thanks for replying!
-TheChadGamer
Click to expand...
Click to collapse
I use TWRP 3.2, and flashed MY builded custom kernel (Only for GSI!) https://forum.xda-developers.com/galaxy-j/development/kernel-redline-kernel-samsung-galaxy-j4-t4188199/
You need to update to Android 10 Stock then flash the A64 A/B GSI. And remember to flash dm verity disabler then flash Magisk. Magisk is important too.
For more info about this, feel free to join our telegram group : https://t.me/SamsungGalaxyJ4
In there we have detail instruction to flash GSI for J4. And other issue discussion
I can't write the steps here, because the steps is little complicated. Cheers!
Thank you for your help!
Soon i will be giving it another attempt then !
Sorry for taking so long, even the site had a upgrade!
I actually am using Linux now but i am dualbooting with Windows to be able to use Odin. I have just now entered the Telegram group,
NamaSayaHendra said:
In there we have detail instruction to flash GSI for J4.
Click to expand...
Click to collapse
Where can i find those instructions in the group? I have never used Telegram before so i don't know where to look for them