Hi i got a brand new already unlocked Redmi note 5 today, i updated it then flashed TWRP and used it to install LineageOS+gapps, but its stuck on the loading screen. I also tried ResurectionRemix and it was the same. Some people on LineageOS chat said that i should not have updated it. Is there any ROM that works or is my phone bricked? Help appreciated.
EDIT: MSM Xtended ROM works, RR remix doesnt load, LOS doesnt load
Any reason why LOS would not work?
Related
So, I own a Samsung Galaxy A5 2017 and I became interested in Custom ROMs. So without any knowledge about flashing custom ROMs I tried it on my other Samsung Galaxy S5 and it worked flawlessly.
Thinking it would be same for my own A5 2017, I went ahead and installed TWRP Recovery and flashed a custom ROM. Little did I know that doing so will trip my KNOX and I won't be able to use secure folder and most of the Samsung apps. Thinking it would be best to switch to a custom ROM, I went ahead and flashed Lineage OS 14.1.
The flashing process completed without any error, but the device did not detect my sim cards even though I had 2 sim cards installed in it. Turns out my baseband version was displayed as 'unknown' and my IMEI was also 'unknown'. This issue took me 2 whole days to resolve and I found a fix for you guys.
To fix the baseband issue, I realized that my official stock ROM was android 8.0 and I flashed a custom ROM of android version 7.1.2 since a custom ROM with 8.0 is not yet available for this device ATM(none that IK of). So, after 2 whole days it hit me that I had to flash the stock ROM of 7.0 on my device to fix the baseband of the device.
After flashing the stock ROM 7.0 on the device, I installed TWRP again and flashed the custom ROM once again and it fixed the baseband 'unknown' issue and my IMEI was back to normal again.
Now for the Samsung apps issue, after installing the custom ROM the S Health app, Gear app did not work. So to fix this issue I had to root my phone using Magisk and then change my build.prop file to bypass the issue.
This fixed my issue and made my apps works properly and now my Gear S3 also connects properly and functions very well.
For Resurrection Remix OS Custom ROM A5 2017 (a5y17lte): https:// androidfilehost.com/?fid= 818070582850504876 (remove the spaces)
For GApps (choose arm64) (7.1): google OpenGapps ( I can't post outside links yet )
Root through Magisk or SuperSU (both work)
For changing the build.prop file:
To fix this, open build.prop in /system and change ro.product.name=samsung and ro.product.manufacturer=samsung to another brand like lg or htc (in lowercase).
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Stable
Current Stable Version: 1
Stable Release Date: 2018-03-31
For anymore issue feel free leave them in the comments and I will try and help you guys out.
I also installed custom ROM lineage 14.1 on my galaxy a5 2017....after booting sim is not detected nor is IMEI is being showed...I havnt done a backup ......tried all possible ways....not working.....pls do help
Thanks
Sorry for the Late Reply
drajithkv said:
I also installed custom ROM lineage 14.1 on my galaxy a5 2017....after booting sim is not detected nor is IMEI is being showed...I havnt done a backup ......tried all possible ways....not working.....pls do help
Thanks
Click to expand...
Click to collapse
Its almost too late now, hopefully you have fixed this issue. If not could you let me know which stock OS version did you come from and what OS version did you flash.
For example my stock ROM was on Oreo 8.0 and I flashed a Custom ROM that was based on Nougat 7.1.2, So to fix this:
1. First Download the stock ROM of the same version as that of the Custom ROM (i.e. custom ROM is 7.1.2 Nougat so download Nougat stock ROM) flash this stock ROM.
2. You can now proceed to install the custom recovery and a flash the custom ROM now.
This should fix your issue as your CSC will be updated to match your custom ROM and will let your phone detect the sim cards.
MZainKh said:
Its almost too late now, hopefully you have fixed this issue. If not could you let me know which stock OS version did you come from and what OS version did you flash.
For example my stock ROM was on Oreo 8.0 and I flashed a Custom ROM that was based on Nougat 7.1.2, So to fix this:
1. First Download the stock ROM of the same version as that of the Custom ROM (i.e. custom ROM is 7.1.2 Nougat so download Nougat stock ROM) flash this stock ROM.
2. You can now proceed to install the custom recovery and a flash the custom ROM now.
This should fix your issue as your CSC will be updated to match your custom ROM and will let your phone detect the sim cards.
Click to expand...
Click to collapse
That doesn't work on the latest updates as downgrading is blocked.
Hello guys,
let's start off, several month's ago i bought Nokia 7 plus just cause for a new contract with the telecom,
due to lack of community custom roms and also able to unlock the bootloader i was a bit done with this phone.
Now my question is what's a smooth, battery friendly and user friendly custom rom to flash on ?
The phone it self feels a bit slow on the stock rom but otherwise it's a great phone.
EDIT : i tried to flash LOS and the device just restart in the boot somehow..
Kcetin20 said:
Hello guys,
let's start off, several month's ago i bought Nokia 7 plus just cause for a new contract with the telecom,
due to lack of community custom roms and also able to unlock the bootloader i was a bit done with this phone.
Now my question is what's a smooth, battery friendly and user friendly custom rom to flash on ?
The phone it self feels a bit slow on the stock rom but otherwise it's a great phone.
EDIT : i tried to flash LOS and the device just restart in the boot somehow..
Click to expand...
Click to collapse
most stable ofcource still oreo 8.1 ( LOS, AOSIP , even Google Pixel ROM ),
I have 2 nexus 5x,
8.1 google pixel rom + shadow kernel, for daily driver ( BLOD condition ), and
9.0 aosip + bitgapps + latest zest kernel for multimedia and entertainment
Kcetin20 said:
Hello guys,
EDIT : i tried to flash LOS and the device just restart in the boot somehow..
Click to expand...
Click to collapse
I have seen that happening after having a non-stock ROM installed and/or rooting it using Magisk. That seems to change the boot image and that confuses Lineage OS (I think).
I solved that by re-flashing the factory image from Google, booting the phone to TWRP recovery and flashing LOS.
Oh, and my daily driver is just Google's latest stock ROM for bullhead, so Android 8.1 rooted with Magisk and with Franco's Kernel. I like to have Xposed available which isn't available for Android Pie yet.
Hello friends,
I am very happy with LineageOs 16 in my klte (samsung s5) device so far. Zero problems for me.
I have just bought a Xiaomi Redmi 7a , and I am willing to give it a go.
I couldn't find Redmi 7a on LineageOs downloads. I presume it is not supported yet. Anyway I am willing to try most compatible image on it.
My question is:
Which image should I install? (violet ?)
What do you think major problems would be, since I will install another phone's image?
Many Thanks
ozkolonur said:
Hello friends,
I am very happy with LineageOs 16 in my klte (samsung s5) device so far. Zero problems for me.
I have just bought a Xiaomi Redmi 7a , and I am willing to give it a go.
I couldn't find Redmi 7a on LineageOs downloads. I presume it is not supported yet. Anyway I am willing to try most compatible image on it.
My question is:
Which image should I install? (violet ?)
What do you think major problems would be, since I will install another phone's image?
Many Thanks
Click to expand...
Click to collapse
Hi there and please forgive my english.
unfortunatly it is not that easy.. the best thing you can do is to unlock bootloader first using xiaomi miflashunlock, afterward you can head to this thread and, if you are able to follow all the instructions (and sadly i ve been not :crying you'll be on an unofficial lineage os rom.
https://forum.xda-developers.com/redmi-7a/how-to/custom-gsi-firmware-t3965820
update:
[ROM][9.0][OFFICIAL][PINE][NIGHTLY][SHARE] MoKee Open Source Android Project easiest way to get LOS like os..
wifi
Hi, i installed lineage os 17 on mi redmi 7a, but it have many issues.
The wifi doesnt work (i touch the button to activate it and it turns off inmediately
i cant install gapps (pico) because TWRP says that doesnt have any space on system partition
anybody can help me?
RazorNitro74717 said:
Hi, i installed lineage os 17 on mi redmi 7a, but it have many issues.
The wifi doesnt work (i touch the button to activate it and it turns off inmediately
i cant install gapps (pico) because TWRP says that doesnt have any space on system partition
anybody can help me?
Click to expand...
Click to collapse
Why don't you ask there?
https://forum.xda-developers.com/redmi-7a/development/rom-lineageos-17-1-t4056545
Hi everyone,
Recently I wiped my Moto G5 to factory reset, then installed the official Oreo 8.1 firmware, then installed CarbonROM custom ROM. Since then everything seemed to work fine, but people told me they can't join me via calls, they directly ended on my voicemail ...
I searched as I could a solution at my problem but found anything ... Is there a setting I forgot to set well ?
Thanks for your answers
It's an old outdated no longer supported rom
Please try changing your rom to lineage mintos for the latest custom rom for this device
Hi,
I was trying to update my Redmi Note 8t from 17.1 to 18.1. I ended up in a boot loop. I tried with the update from 22-4-4 and the previous one. I also updated the recovery image. I cleared all partitions and installed again. Nothing works.
Switching back to the latest 17.1. works.
Anyone else having this problem? How can I find out, what the problem is? Can I enable any logging?
adb logcat is not working during startup.
Regards, Sebastian
i can confirm this.
i tried with the 2022-04-18 build on redmi note 8T
I have the same problem.
Do you know where can i get 17 ?
I broke my Redmi Note 8T (Willow) by updating LOS 17 -> 18.1
(Bootloop, without even seeing the LOS animation)
In /proc/last_kmseg I saw that the underlying issue was caused by a fatal error in the modem.
I.e. something kernel<->modem broke the thing.
Through recovery, I flashed a modem update from
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
and everything is working again
Finally, I installed the latest official Miui version (12.5 I think it was), then I installed LinageOS 18.1 recovery and latest nightly from 23.5. again and it worked.
frauschrotti said:
Finally, I installed the latest official Miui version (12.5 I think it was), then I installed LinageOS 18.1 recovery and latest nightly from 23.5. again and it worked.
Click to expand...
Click to collapse
i can confirm that:
the MUI Version i downloaded i got from : https://xiaomifirmwareupdater.com/miui/willow/stable/V12.5.4.0.RCXEUXM/
willow_eea_global_images_V12.5.4.0.RCXEUXM_20220218.0000.00_11.0_eea
i needed to use the fastboot method and reflash all ROMs with the "flash_all.sh"