Good day everyone, I'm currently running Lineage OS 14.1 on my Honor 8, and the only problem I have with it is the recurring reboot happening every 30 min or so for no reason. The ROM is surdu's.
I'd like to switch to a more stable ROM even with missing functionalities (Bluetooth, fps...) from my current setup.
I tried a couple ROM already but as I flash them through TWRP they send me an error 7.
Before I flashed I tried doing nothing. I tried clearing cache. I do not wish to randomly try factory reset as it caused problem to me before.
Is that because I'm running nougat ? Or because I did something wrong to switch roms ?
Do I have to rollback to marshmallow and flash a new rom ?
Thanks for you by advance for your answers.
Ayzhil
Ok, so sorry about that, but the EU g&rbest version has ghost touch that make it unusable (almost impossible to navigate the menu or write the keyboard) with every custom rom.Actually I don't know why, but I finally reinstalled stock EU build B2017GV1.2.0B13 (B13 7.1.1) Kernel 3.10.84 , installed TWRP and rooted with magisk and everything is finally fine...I really hope that Oreo lineage won't have this problem, at the moment AOKP and the lineage can't be used on mine EU B2017G (( looks like I'm the only one with that problem (or almost all the people here has USA or UK version).
P.S.P I hope is the right section, please move it if am I wrong.Thank you
Hi!
Will try to be very brief.
So I've had the falcon xt1032 for 4 years now.
For the past 3 years I've used a custom ROM, Cyanogenmod then LineageOS. Never had any major problems, maybe a random reboot every once in a while due to a nightly rom.
About a month ago it started rebooting and freezing into a blue screen after reboot. Googled an XDA'd about it it looked like it was time to replace the phone.
I tried clean installing custom roms, nightly (Nougat 7.1) and stable (Marshmallow 6.0.1), and had the same issue (blue screen).
So I got a new phone.
I decided to change the bootloader to the original version and install the latest official release (Lollipop 5.1).
Used it for a week without a sim card and then put a prepaid sim card and it's been working ok for 2 weeks now.
What the hell could have happened?
For 3 years it worked ok with custom roms (stable and nightly). And now this.
Any ideas?
Thanks.
well all things aside, if you installed the stock ROM with fastboot, that sort of resets every issue supposedly introduced with using custom ROMs. who know maybe it is ready again for a bout of custom ROMs again
Hi All
I tried almost all roms given on the xda as well other platform.
My bootloader is unlocked
I installed twrp .then every thing become encrypted
Installed twrp again. Then tried all almost all roms. After installing rom phone went to bootloop....
Can anyone port pixel latest room for my devices. I will provide everything you need.
Thanks alot.
*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.