Sense home problems After lineageOS 14.1 update - HTC One A9

Hi guys, I'm new here, I've searched forum similar posts but I couldn't find anything.
I rooted my Nuogat 7.0 device with the last versions of twrp recovery and SuperSu. (The device is unlocked and S-ON)
A couple days ago I decided ti flash LineageOS 14.1 ROM and the super Gapps package. At the beginning all' ok, but I noticed that the HTC sense interface was absent.
So I tried install the last versions of it but it gave me crash problems everytime I tried to interact with it (like when moving apps or installing themes). I Also noticed that the layout is smaller than the one I had before installing lineageOS(app icons are smaller, and apps layout too (this doesn't happen when I launch Google home Launcher)).
I've tried installing older versions found on apkmirror, but they all give me the same problems.
LineageOS ROM was the correct one for my phone and GApps pack was the correct one for my CPU. Please help I like too much Sense home

Related

[Root/Rom Help] Features broken

I have been trying to install a custom Rom because of SuperSU failing to update binarys and getting stuck on boot. I have tried two different Roms (BlissPop and DirtyUnicorns) and both have the same exact problem that i have found so far, the home button doesn't return home or do anything for that matter, and the notification bar will only fully extend once any time after that and it only half extends after that.
So I guess my question is this. Is there something that i can do to fix the problem with the Roms, or is there a way i can fix SuperSU trying to update its binarys.
Tablet/Software Info
Roms: BlissPop, DirtyUnicorn (The ones with the problems i tried)
Gapps:Banks Gapps
Tablet:Nvidia Shield Tablet LTE US

SIM Unlocked G920W8, 9.0 and 10.0 ROMs no longer detect SIM.

*SOLVED: see reply*
The ROM I used before was LineageOS [10.0] and used a custom ROM with Android 9 before that. Needed to unlock my phone, and couldn't do that on Lineage, and had troubles flashing firmware with Odin, so I ended up using FrankensteinS6. The Stock kernel seems to let me input the NCK, and unlock the phone. So that's luckily finally over.
For about 4 days now I've been formatting phone and trying again and again. FrankensteinS6 works, some other 6.0/7.0 ROMs work. But LineageOS now enters a bootloop, and Pixel Experience (9.0 and 10.0) and Evolution X 10.0 don't detect the SIM. The ones that don't detect SIM also show no IMEI, which was worrying at first because I though I lost a partition.
Possibly related, the ROM of Pixel Experience Android 10.0 for G920W8 will not install because (paraphrasing) "This device is zeroflte, this file is for zerofltecan, zeroflte***, zeroflte***" claiming that my phone isn't one of those models. I got this S6 from Bell Canada, and I still have even the sticker that says it is a G920W8, not G920F. However, the Pixel Experience ROM for G920F flashes fine (sans the main problem).
I don't know the exact LineageOS ROM I used before, but I've tried all of their 10.0 releases, tried redownloading, and I get the bootloop every time. I see some info online of flashing modem firmware, but... I don't even know where to start with that. As I mentioned at the start, Odin is crapping out. I couldn't flash firmware with it, because it would reject the phone right after I started flashing. Anything I could do within TWRP would be great. I moved it back to FrankensteinS6 for my sanity, I started doing this Sunday and I'm starting to repeat steps over and over hoping that it just solves itself.
I tried to keep this straightforward, and I'm sure I did a bad job. I can extrapolate on what I have attempted. Please tell me what I have to do to get an android 10 ROM working on this old beauty again.
I do not have all the solutions. As per my tests with my SM-G920W8. I have managed to find ROMS and try them out. I have only seen Nougat 7.0 ROMS to work almost flawlessly. NOT 7.1.2, important, 7.0 only.
I have also tested some Pie and v10 ROMS like Pixel Experience. The ROMS boot nicely but since I do not use a SIM card to call as I use SIP phone numbers and require WiFi. But that left asside, I came upon serious camera issues no matter what I try. Up to now, SamStock ROM is pretty much the best Stock ROM I found but I always need to run the Magisk UNINSTALLER before re-installing the latest Magisk version..
As for Kernels, well, Anything that is oriented with Lineage OS, I've had camera issues even with Nougat v7.0. So basically, the only ROMS I found good, as of today, for now, are stock ROMS v7.0. But, to do your tests, Even if you have a 920F ROM, you can download a 920W8 kernel as long as you download a kernel which supports your installed Android version. Also make sure to download the proper Stock or AOSP kernel (AOSP for LineageOS). There's not many but there's a few ones that work properly.
Another option is to download an AOSP ROM that works for W8 phones, unzip the file and grab the boot file inside corresponding to the W8 or T-Mobile version. You simply unzip your real ROM you want top install, replace the boot file for the one you got and rezip it. This made my phone boot properly for some F version ROMS but again, not without issues. That's why, I really suggest v7.0 Srock ROMS. I hope this helps you a bit. Again, you can have your own tests and other users may have other answers, but this is based off over 30 bootloops in my case of trying to mod a ROM for the W8 model. It's not easy to find a good one for Canada, I admit!!!
I flashed TWRP years ago, and I found out that I had a G920F version flashed. I don't know why Lineage allowed me to use SIM before, but rectifying this issue seems to made the SIM work in newer versions.
I don't know what the S6's predisposition to having crashing cameras is, but I have avoided this in the past by using custom camera apps, like Open Camera. This has saved me every time.
As for the boot loops... I think another thing that helped is that "format data" doesn't wipe the OS. When you are in recovery, having issues with bootloops in various ROMs, try advanced wipe, and wipe the system. It didn't fix right away, but the time I got Pixel Experience 10 up and running that was the trick.

question about ROM - Samsung S9 SM-G960F (PHN)

hi everyone, I am new to this forum.
i've been interested in rooting / mods for my old Samsung s9 to give it a new life.
I did so by rooting it using the TWRP app in combination with the Magisk V23.0
now what happened was that i was downloading some random apps yesterday and for some reason the phone went on bootloop...
i accidentally deleted the system without making a backup lol... a little stupid of me...
now it keeps telling me that i've no OS on my phone. i was thinking that i could easily find the ''un-edited'' or simple version of my original OS. but i've looked through many sites without succes.. either looks 2 good to be true or just fake...
is there anyone who can advise me on what to do? i just want my phone to work with any OS right now... but which one is the cleanest or best to use? i do prefer a newer os like 10
thanks in advance!
If you still have access to recovery mode, your best choice would probably be installing LineageOS. It's the most lightweight ROM and many ROMs are based on Lineage. From what i can see, your phone is no longer officially supported.
I found this one based on Lineage 18.1 (Android 11). Before installing, take a look at the bugs, working, and installing sections.
And don't forget to install the Google Apps after installing the system and before rebooting.
that looks crispy. i appreciate your quick & good advise. can you tell me wether i can still run Magisk on it?
Yes, you can still flash Magisk or any type of root with both the OS and the GApps.
what i'm consider about is, wether a region code CRC matters?

Recent strange experience with this device

I have a Moto G3 XT1543 and since december I have given this device a second life and have been using it as a secondary phone. I decided to install LOS 14.1 because I feel is better for this device than LOS 17.1. Since then I had been using the phone and installing the updates without problems until a few weeks ago.
I thought I couldn't install the update because my version of TWRP was so out of date. So I decided to install the latest version for this device (twrp-3.5.2_9-0) and I was able to update the rom but it got me a lot of bugs, basically forced close in many processes.
So I decided to do a clean installation but still had a lot of bugs. So I installed previous versions of the rom, including the first one that I installed and worked fine, but it still had a lot of bugs (basically forced close in many processes, as I said before).
So I decided to go back to the TWRP I had before (twrp-3.4.0-0) and the bugs disappeared and I was able to use the rom without problems, but no matter what I do I cannot get youtube working now.
The gapps that I have been installed are open_gapps-arm-7.1-pico-xxxxxxxx and I have done all the possible combinations: old gapps with the most recent rom (lineage-14.1-20210829-UNOFFICIAL-osprey), the most recent gapps with the oldest rom I have (lineage-14.1-20201221-UNOFFICIAL-osprey), the oldest rom I have with old gapps and the most recent rom with the most recent gapps, but youtube still doesn't work
As I said before, it doesn't matter what combination I do, even the first one I installed and worked since last december, nor what version of YouTube I have installed, the application closes. As a possible solution I have deleted cache and data of youtube but the problem still. The funny thing is all the applications that I have, including other google apps (chrome, gmail, maps) work without problem.
I have tried alternatives like YT Go, YT Vanced and New Pipe and all three work without problem, but honestly, although they are better alternatives, I don't want to use them.
So does anyone know how to fix this?
I used this weekend for testing and long story short I can use youtube but I have no idea how it was fixed.
But I will tell you about everything I did in case someone in the future is going through a similar situation to mine.
Following the indications that FNetV1 gave me in another post, I downgraded my TWRP version to 3.0.2-r5, then I installed the oldest rom I have (lineage-14.1-20201221) with the oldest gapps I have (open_gapps-arm-7.1-pico-20210112) but youtube was not working.
So with that same version of TWRP I installed the most recent rom available (lineage-14.1-20210829) with the most recent gapps and still youtube did not work.
So I installed the latest unofficial version that Squid2 developed for this device (twrp-osprey-3.2.3-r1) and then installed the oldest rom I have with the oldest gapps I have. The result was the same, youtube was not working.
I thought the problem was the gapps, so I installed the latest rom available with the most recent gapps but now with the Nano package. But the result was the same, youtube was not working.
So I gave up and for the last time I reinstalled the latest rom avaible with the most recent gapps, again with the pico package and as expected youtube was not working.
The funny thing is after I finished setting up my phone, I restarted it, reinstalled YouTube and voilĂ , I can now use YouTube without any problem.
As I said at the beginning, I have no idea how the problem was fixed, especially because I also rebooted my phone on several occasions with the previous tests.
So if anyone has an idea what I did wrong from the beginning or how the problem was fixed, feel free to comment.

What if I install an older version of FlameGApps?

I recently tried to install a custom ROM on my Android device with the latest version of FlameGApps and ran into some problems (specifically, the device setup app kept crashing and looping on first startup of the device, never allowing me to get to the landing page).
Then I installed the previous version of FlameGApps onto my device (the one I was running before I installed a new version of LineageOS), and it works fine.
I'm just wondering: Is there any consequence to running an old version of FlameGApps? Does this make my device susceptable to security issues that have since been patched, or will all the GApps included in FlameGApps update themselves once the device is set up?
MachineMasher said:
I recently tried to install a custom ROM on my Android device with the latest version of FlameGApps and ran into some problems (specifically, the device setup app kept crashing and looping on first startup of the device, never allowing me to get to the landing page).
Then I installed the previous version of FlameGApps onto my device (the one I was running before I installed a new version of LineageOS), and it works fine.
I'm just wondering: Is there any consequence to running an old version of FlameGApps? Does this make my device susceptable to security issues that have since been patched, or will all the GApps included in FlameGApps update themselves once the device is set up?
Click to expand...
Click to collapse
It may not be a problem with the version that you're using, it might a problem with the size of the Gapps package. Have you tried installing a smaller Gapps package? Your system partition may not be big enough to fit your ROM and the Gapps package that you are using.
Thanks for the reply.
Actually, I'm not asking why the version of FlameGApps I was using had a problem (although your advice is helpful on that too!)
What I'm asking is whether there is any negative consequence to using an old version of GApps - does installing an old version of GApps permanently lock the various google apps to an older version, or will they self update from the play store after first bootup?

Categories

Resources