I am with the idea of changing the rom of my G9600 to a GSI or another rom, but from what I have seen in the GSI you have to have the same security patch between the vendor and the rom, that is where the problem I have lies the February update and I already have the phone with twrp and majisk and the klavit kernel, I mean it doesn't update from the OTA.
How do I update the stock rom?
And which rom do you recommend me to change, in my other phones I always used roms with a great margin of customization like the Resurrection Remix.
Thanks all.
if you're not receiving the latest software update, then just manually download the rom from SamMobiles or Frija and flash it through download mode by using Odin.
Try finding in the Snapdragon section, since I'm on 960f which is Exynoss version.
I'm using EvolutionX rom which have lot of customization, I believe there's one for the Snapdragon but it's been discontinued
Related
I have updated to oreo but the phone has terrible battery life even after trying to disable some wakelocks , using greenify , forcing doze etc. I was wondering if I could flash lineage os or let's say resurrection remix on the phone while it has oreo firmware .
I also would like to know
leodiavata said:
I have updated to oreo but the phone has terrible battery life even after trying to disable some wakelocks , using greenify , forcing doze etc. I was wondering if I could flash lineage os or let's say resurrection remix on the phone while it has oreo firmware .
Click to expand...
Click to collapse
iMZee said:
I also would like to know
Click to expand...
Click to collapse
Of course custom roms can be flashed after stock Oreo update.
BUT:
You need to read the requirements in the thread for the specific rom you wish to flash.
There is no single answer for all cases/roms.
Each rom is going to be different, based on whatever blobs were used during rom compilation.
If the rom was built using Oreo blobs, then Oreo firmware is required.
If the rom was compiled using Nougat blobs, then it would require Nougat firmware, despite the actual version of android it is...
So...., read the OP of the thread for the rom you want to flash.
If that doesn't answer your question, then read the last 5-10 pages of the thread.
Still no answer found, then ask in that particular rom thread, what firmware is required.
It's actually pretty simple and typically requires a little reading.
(eventually, all Oreo based custom roms, should be using Oreo blobs and would then require Oreo firmware)
Things are in what I consider a transition phase currently....
TL;DR: LeeDroid 5+ is your only option ATM.
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!
I currently have completely stock and BL locked M1803E7SG 3/32, on MIUI 10.3.1.0 Stable Pie.
Tomorrow is my big day, timer in MIUI unlocker will finaly allow me to completely mod my device.
I did some modding a long time ago on Xperia X10/Xperia Play (old 2.3.3 Gingerbread times), but many things changed nowadays, so I have few questions:
1) Firmware - is it something like low-level SoC driver pack included in official releases? Back in a day nothing like that was updated/changed. I have latest stable Pie so that point shouldn't be a problem beacuse I will flash Pie FW compatible ROM, just want to confirm my understanding there.
2) ARB - as far as I'm concerned, this thing has no meaning if I'll flash Pie AOSP ROM over stock Pie MIUI right?
3) Kernels - again, back in a day kernels were completely separate from ROMs itself, do modern ROMs require kernel flash when going from official MIUI to AOSP-based ROM? Or is AOSP-compatible kernel already included in ROM .zip?
I want to use this one:
https://forum.xda-developers.com/redmi-note-5-pro/development/rom-cosp-t3891988
Another thing about kernels, I want to use latest PureCAF, do i need to flash it before ROM .zip or after?
So my path should be like that:
Official MIUI Pie + stock kernel + locked BL
1. Unlock BL via official Xiaomi tool
2. Flash latest TWRP thru fastboot, boot into it, flash Lazyflasher thru TWRP
3. Perform a wipe (dalvik, system, cache, data)
4. Flash ROM .zip thru TWRP, flash Gapps.
5. Flash PureCaf .zip thru TWRP again
6. Reboot into clean&fast new phone?
Oxynium said:
Hello!
I currently have completely stock and BL locked M1803E7SG 3/32, on MIUI 10.3.1.0 Stable Pie.
Tomorrow is my big day, timer in MIUI unlocker will finaly allow me to completely mod my device.
I did some modding a long time ago on Xperia X10/Xperia Play (old 2.3.3 Gingerbread times), but many things changed nowadays, so I have few questions:
1) Firmware - is it something like low-level SoC driver pack included in official releases? Back in a day nothing like that was updated/changed. I have latest stable Pie so that point shouldn't be a problem beacuse I will flash Pie FW compatible ROM, just want to confirm my understanding there.
2) ARB - as far as I'm concerned, this thing has no meaning if I'll flash Pie AOSP ROM over stock Pie MIUI right?
3) Kernels - again, back in a day kernels were completely separate from ROMs itself, do modern ROMs require kernel flash when going from official MIUI to AOSP-based ROM? Or is AOSP-compatible kernel already included in ROM .zip?
I want to use this one:
https://forum.xda-developers.com/redmi-note-5-pro/development/rom-cosp-t3891988
Another thing about kernels, I want to use latest PureCAF, do i need to flash it before ROM .zip or after?
So my path should be like that:
Official MIUI Pie + stock kernel + locked BL
1. Unlock BL via official Xiaomi tool
2. Flash latest TWRP thru fastboot, boot into it, flash Lazyflasher thru TWRP
3. Perform a wipe (dalvik, system, cache, data)
4. Flash ROM .zip thru TWRP, flash Gapps.
5. Flash PureCaf .zip thru TWRP again
6. Reboot into clean&fast new phone?
Click to expand...
Click to collapse
1. Don't care about that driver, the only thing you need to pay attention is the rom based on oreo or pie fw. The other thing you need to know is if the custom recovery compatible with pie fw or not, i recommend latest OrangeFox R10 RC3.1 as it's unified for both oreo and pie fw.
2. ARB has almost no meaning now, old arb3 fw is just too outdated and not recommended to use as lots of roms now moving on to pie fw which makes this even more meaningless now.
3. No, compatible kernel is now included in the rom zip itself, although you can choose to flash another custom kernel based on your taste for better performance or battery backup, noted that some kernel only supports aosp, some only for miui, some for both and some only supports pie/oreo fw.
4. Your step is right, but you'll need to flash dummy.img (just google whyred dummy.img) before you can flash other in fastboot, Orangefox doesn't require lazyflasher, TWRP does. For Gapps, read careful if the rom already includes it or not (Pixel Experience for example), miui based like xiaomi.eu doesn't need it too, custom kernel is flashed after rom.
sushuguru said:
1. Don't care about that driver, the only thing you need to pay attention is the rom based on oreo or pie fw. The other thing you need to know is if the custom recovery compatible with pie fw or not, i recommend latest OrangeFox R10 RC3.1 as it's unified for both oreo and pie fw.
2. ARB has almost no meaning now, old arb3 fw is just too outdated and not recommended to use as lots of roms now moving on to pie fw which makes this even more meaningless now.
3. No, compatible kernel is now included in the rom zip itself, although you can choose to flash another custom kernel based on your taste for better performance or battery backup, noted that some kernel only supports aosp, some only for miui, some for both and some only supports pie/oreo fw.
4. Your step is right, but you'll need to flash dummy.img (just google whyred dummy.img) before you can flash other in fastboot, Orangefox doesn't require lazyflasher, TWRP does. For Gapps, read careful if the rom already includes it or not (Pixel Experience for example), miui based like xiaomi.eu doesn't need it too, custom kernel is flashed after rom.
Click to expand...
Click to collapse
Hi where can I download the RC10 version of orangefox? Looking in the development thread, the source forge page has RC9 as the latest.
Sent from my Redmi Note 5 using Tapatalk
gsmyth said:
Hi where can I download the RC10 version of orangefox? Looking in the development thread, the source forge page has RC9 as the latest.
Click to expand...
Click to collapse
https://files.orangefox.website/OrangeFox Beta/whyred/
sushuguru said:
https://files.orangefox.website/OrangeFox Beta/whyred/
Click to expand...
Click to collapse
Hi,
Can you please guide me as well? I'm on same boat as OP.
I have to unlock BL and install custom ROM. I'm on MIUI 10.0.6.0 Oreo (Indian whyred).
I can just follow this thread right?
https://forum.xda-developers.com/redmi-note-5-pro/how-to/one-xiaomi-redmi-note-5-whyred-unlock-t3778049
And I want to install Pixel Experience ROM. And what's about this fw-less ROM!
So, for PE Pie ROM, I just install the other recovery (Orangefox) instead of twrp. Everything else is same right.
1. Unlock BL from the main thread
2.Install Orangefox recovery
3.Flash ROM
Thanks
Hello friends
I'm trying to flash custom Q roms in TWRP on my S9 (SM-G960F), but have received the same error message for any Q rom:
ERROR:
Vendor image on the device
is NOT compatible
Expected Android 10 vendor
Click to expand...
Click to collapse
I've only been able to successfully flash P roms, namely the Pie-based LightRom.
Based on the error message, it seems I need to update the firmware to Q before installing custom Q roms?
I've also seen some roms note installation requirements like "ROM Firmware Required: OneUI 2.x", which is new to me (have not seen a TW/OneUI ver requirement for roms I've used on S4, S7, N8).
May I ask someone to explain the steps required to install Q roms (eg, Havoc-OS) coming from P firmware? There seems to be some assumptions in most install instructions I'm not aware of, maybe since I am on older FW. (I am asking here, since I did not find instructions in any of the Q roms I tried)
So far, all I have done to the phone since unboxing it was to install TWRP 3.4.0, following the official guide for Exynos S9.
I am guessing I need to download latest official firmware image from sammobile or something for my device, and flash it in Odin. Is this correct?
If so, can someone explain the steps so that I can have latest FW for my device while maintaining TWRP and not bricking the device?
Thank you for your help
Extra info
(Snapshot from LightRom rom)
One UI version: 1.0
Android version: 9
Baseband version: G960FXXU6CSG4
Kernel version: 4.9.59
Android security patch level: 1 October 2019
Click to expand...
Click to collapse
UPDATE:
I installed latest firmware from Sammobile, flashed it through Odin following their instructions, reinstalled TWRP, and am now able to flash Q roms.
For those who have stock rom < Q, I would suggest updating firmware through OTA before flashing TWRP. If you cannot OTA, download the latest firmware from Sammobile and flash it through Odin following their instructions, then flash TWRP, then you can flash Q roms.
So:
Update firmware through OTA or via Odin with latest firmware from Sammobile.
Flash TWRP
Flash whatever rom you want.
Hello, I was wondering if I need to update my firmware on my Xiaomi Redmi Note 5 Pro (whyred).
The reason for it is because it shows "1. November 2018" as latest vendor security patch level.
I am currently running LineageOS 17.1 which is based on Android 10 together with the Lineage recovery.
Mainly I have these questions:
1. Do I need to update the vendor firmware? In other words would that even increase the Vendor security patch level?
2. When I checked this website: https://xiaomifirmwareupdater.com/firmware/whyred/ it shows the latest Vendor Firmware to be from 2021, however with Android 9.0, would that even work with LineageOS 17.1 which is Android 10 level?
3. Would I need to flash back to the official Rom on Android 9.0 in order to then flash to the 2021 firmware ( should be included in the latest official rom anyway) and then flash back to LineageOS 17.1?
Any help is greatly appreciated as this is my first phone on LineageOS. (I did had a couple of other phones in the past with unofficial Roms so I am not a completely noob.)
Thanks and have a good day
StriKe_jk said:
Hello, I was wondering if I need to update my firmware on my Xiaomi Redmi Note 5 Pro (whyred).
The reason for it is because it shows "1. November 2018" as latest vendor security patch level.
I am currently running LineageOS 17.1 which is based on Android 10 together with the Lineage recovery.
Mainly I have these questions:
1. Do I need to update the vendor firmware? In other words would that even increase the Vendor security patch level?
2. When I checked this website: https://xiaomifirmwareupdater.com/firmware/whyred/ it shows the latest Vendor Firmware to be from 2021, however with Android 9.0, would that even work with LineageOS 17.1 which is Android 10 level?
3. Would I need to flash back to the official Rom on Android 9.0 in order to then flash to the 2021 firmware ( should be included in the latest official rom anyway) and then flash back to LineageOS 17.1?
Any help is greatly appreciated as this is my first phone on LineageOS. (I did had a couple of other phones in the past with unofficial Roms so I am not a completely noob.)
Thanks and have a good day
Click to expand...
Click to collapse
LOS has old version of vendors. Yes from 2018.. they build on that... if you wanna updated version go to LOS github and ask there.. that's how it is, nothing can be done here. Only LOS team can help you.
Good luck and stay safe!
drnightshadow said:
LOS has old version of vendors. Yes from 2018.. they build on that... if you wanna updated version go to LOS github and ask there.. that's how it is, nothing can be done here. Only LOS team can help you.
Good luck and stay safe!
Click to expand...
Click to collapse
Does this mean 2018 is the latest vendor security patch level?
StriKe_jk said:
Does this mean 2018 is the latest vendor security patch level?
Click to expand...
Click to collapse
If you use LOS, than yes.
Maybe I am a bit dense to understand this, but shouldn't all have the same? I thought Vendor security patch level are bugfixes from the vendor, so it only makes sense to me to include the latest patches in all roms to get this baseline patch level. Ofc every ROM can feel free to increase security even further with additional patches on top of that.
StriKe_jk said:
Maybe I am a bit dense to understand this, but shouldn't all have the same? I thought Vendor security patch level are bugfixes from the vendor, so it only makes sense to me to include the latest patches in all roms to get this baseline patch level. Ofc every ROM can feel free to increase security even further with additional patches on top of that.
Click to expand...
Click to collapse
Yap, but every custom Rom has it's own vendor version. LOS has old one and many custom ROMs. It's actually developer decision what version he's gonna use to build rom. That's it. Yes MIUI ROM uses latest. You can't mix them because you'll get bootloop or bricked device.
For latest version you need to ask developer to update it.
StriKe_jk said:
1. Do I need to update the vendor firmware? In other words would that even increase the Vendor security patch level?
Click to expand...
Click to collapse
The vendor security patch level is just a setting configured here: https://github.com/LineageOS/androi...0038ae0340b1da03ae9c00ff50/BoardConfig.mk#L56
The official LOS 18.1 rom contains at least some vendor blobs from the latest MIUI V12.0.2.0.PEIMIXM rom.
That probably means the vendor security patch level date is not accurate and can be ignored.
StriKe_jk said:
2. When I checked this website: https://xiaomifirmwareupdater.com/firmware/whyred/ it shows the latest Vendor Firmware to be from 2021, however with Android 9.0, would that even work with LineageOS 17.1 which is Android 10 level?
Click to expand...
Click to collapse
Yes, it works. Considering you are currently using even older firmware.
StriKe_jk said:
3. Would I need to flash back to the official Rom on Android 9.0 in order to then flash to the 2021 firmware ( should be included in the latest official rom anyway) and then flash back to LineageOS 17.1?
Click to expand...
Click to collapse
You can flash the firmware ZIP from https://xiaomifirmwareupdater.com/firmware/whyred/. It only updates the various firmware partitions without touching the "boot", "system" and "vendor" partitions (on which LOS is installed).
For some reason the firmware ZIP is missing the new boot logo. It can be updated manually by extracting the file "/firmware-update/splash.img" from the latest MIUI Rom and flashing it in Fastboot Mode with
Code:
fastboot flash splash splash.img
I'm on Lineage OS 18.1 now with Android 11 and figured I just leave it as is. But thanks all for the help