When I bought my Tab S4 I was excited to see that it had an unlockable bootloader but disappointed that there weren't many ROMS available. So I flashed WETA Kernel and lived with just root access. I just recently found out that my device is Treble supported. So would it be safe and possible to flash a GSI when running a Custom kernel such as WETA? Or should I return to stock? Im currently on SF4 and the June 1st security patch
Related
Hey, so I have the Canadian A5 2017 and have not received the Oreo update yet, once Its available for my phone i was planning on switching over to a custom Rom running Oreo 8.1 (can't yet since there's no oreo modem/boot loader available for my phone as far as I know). Just curious if it would be easier to root my phone now while it's on nougat and then install a custom Oreo Rom myself once the modem/bootloader are available?, or should I wait until I receive the Oreo OTA update and then root it after? Believe I read that there s a new boot loader lock of some sort that was introduced in the new new oreo that makes it a bit of a pain to unlock the boot loader. Also my phone is completely stock
Thanks for your help
Rooting on oreo is just a bit more difficult than nougat because of the rmm state, but there're a lot of way to bypass it easily. If you're on N just root without OTA updating oreo, but I don't know how many custom roms running stable oreo 8.1 exist. I had LineageOS 15.1 unofficial for A5 2017, great features but too buggy. Just look for something more stable
Obviously to flash a custom rom you need a custom recovery, but I think you knew it yet
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.
I wanted to root my A70 but haven't, as the TWRP is still buggy, magisk rooting is still a workaround root, etc. looking at A50 threads there are already major developments in rooting and custom kernels. Question is, how bout the A70 ?
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
Hi,
I'm a beginner to installing custom ROMs so forgive me if I'm asking dumb questions.
I'm thinking of buying a used G7 play and would like to install a custom ROM on it. It is the XT1952-1 version and I can't seem to find much information on running custom ROMs on it. The LineageOS page only lists XT1952-2 and -3 as supported models.
Is there a stable custom ROM I could use on this device as a daily driver where everything is working (including VoLTE and fingerprint sensor) and I will get security updates?
Thanks a lot in advance,
Tobias
I am also interested, because I have got an XT1952-1 phone which gets no system updates anymore. :/
I've got an XT1952-3 (US version) with Lineage 18.1 and it's fully stable, way smoother than with the stock firmware. It still receives system updates, despite the Motorola security updates are stuck at some mid-2021 version.