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
Related
So I started having trouble with the Cyanogen I'd been running and decided to move on to a new rom since there are a lot more options available now. I'm running the t-mobile version moto g and am rooted and using CWM and all that jazz, but it seems like I can't get any roms to run on my phone, the only one I got working was the pac rom (ended up doing a recovery back to february from stock 4.3 with root access) I did a clean install with it, and each time it would start having issues of the buttons disappearing and jumping the screen size around (kind of like it was switching in and out of immersive mode every half a second) I tried it 3 times and made sure the settings for full screen were off and it would still start randomly doing that after about 15 minutes or so. On one of my factory resets (the only way I could get out of this jumping screen) I tried updating to 4.4 and ofcourse that failed, then I tried moving on to another rom cyanhacker and cyanogen 11 with aerokernal and both of these said they couldn't install over a corrupted something or another.
So basically what do I need to do? Am I going to have to go back to stock and then update to 4.4.4 and then re-root and a new image and all that jazz or is there any easier way of getting pac-rom on my phone from 4.3?
Bueller? Bueller? Anyone?
Hi guys,
After searching for a few days and doing stuff myself (perhaps not everything for the best), I finally get it over with and ask for advice.
I've got a GT-N8010, since long been running an unofficial CM11 build (since one of these CM11 builds, the device was known as a GT-N8013).
Last week I started looking at the unofficial CM12.0 and CM12.1 builds, those looked promising.
After some info, I flashed to the CM12.1 build. A few minutes later, Android 5.1 in all it glory... everything running fine. Saturday evening I noticed I didn't get root.
Without thinking straight, the next morning I started flashing superuser but as you might imaging, that totally f'ed the system.
Now logically, one could just reflash CM12.1 and be done with it .. somehow I skipped all logic and started tinkering in recovery (TWRP).
After some doing, I managed to even F-up TWRP, it wouldn't boot anymore. The TeamWin logo was visible, screen flashed, logo and back.
No worries, there's still the download mode .. yeah about that ... already in panic mode .. doing more harm than good.
So .. Now I'm at this curious state.
I've managed to get it booting to a stock ROM. TWRP is also running.
The weird stuff I'm encountering now:
The device is semi recognized as a GT-N8000, if it was just that, I really don't care.
I said semi, when I want to flash another ROM (even specifically the CM12.1 for GT-N8000) it always states (in ADB Sideload in TWRP) that the package is not for this device.
There's a whole lot of devices listed, then it states "this device is ." , as in blanco device?
Anyone got an idea how to fix it so I can enjoy the Android 5.1 build again? (and seriously, remove the stock rom would be the first priority)
Thanks.
Hey folks, first of all, sorry but I couldn't find anything that helped.
I have a Galaxy Note 4 (SM-N910F (international Version); Codename: "trltexx") and had flashed an unofficial version of Cyanogenmod 14.1. Except for a few bugs, it was running fine.
I've then changed to Lineage OS 14.1, obviously unofficial as well. This was running fine too and had less bugs (i.e. camera was working unlike with CM).
Well, then, after about a week or so, the phone became unstable and just won't recover from it since then - at least two weeks.
System and Play Store apps/services began to crash (sometimes several at once), the device restarts/turns off randomly or keeps displaying the boot animation and won't turn on till I take the battery out and put it back in.
The weird thing is, these problems sometimes don't occur at all and everything runs nice and smooth and later, everything starts again and is even worse. It feels like the phone is destroying and recovering itself over and over again.
Right now, I'm running the latest version of Ressurrection Remix OS (V5.8.1./Android 7.1.1).
Well, I'd like to thank you in advance for your answers.
User422 said:
Hey folks, first of all, sorry but I couldn't find anything that helped.
I have a Galaxy Note 4 (SM-N910F (international Version); Codename: "trltexx") and had flashed an unofficial version of Cyanogenmod 14.1. Except for a few bugs, it was running fine.
I've then changed to Lineage OS 14.1, obviously unofficial as well. This was running fine too and had less bugs (i.e. camera was working unlike with CM).
Well, then, after about a week or so, the phone became unstable and just won't recover from it since then - at least two weeks.
System and Play Store apps/services began to crash (sometimes several at once), the device restarts/turns off randomly or keeps displaying the boot animation and won't turn on till I take the battery out and put it back in.
The weird thing is, these problems sometimes don't occur at all and everything runs nice and smooth and later, everything starts again and is even worse. It feels like the phone is destroying and recovering itself over and over again.
Right now, I'm running the latest version of Ressurrection Remix OS (V5.8.1./Android 7.1.1).
Well, I'd like to thank you in advance for your answers.
Click to expand...
Click to collapse
Greetings and welcome to assist. Have you tried asking in the rom threads to see if anyone else is having the same issues ? Unfortunately using cm/lineage based roms can have bugs as they are not based on samsung firmware
Regards
Sawdoctor
Hi, thanks for the answer. I wanted to say that I went down to resurrection remix Rom which is based on Android 6 (Marshmallow).
It's fine now.
Now I'm just looking to find a way to hide my root. Can't use my banking app anymore since I've rooted my device.
Update 2: The phone problems I have described reoccur over and over again. A factory reset via TWRP fixes that and then the phone slowly goes back to the old problems.
I don't know what to do anymore except for doing this over and over again.
I did a quick search but most of what I found was > 1 year ago. For those still rocking the SGS3 as their daily driver, what's the best ROM available from a stability / security perspective? Are there any changes since last year, or has everybody moved on? I'm on 4.4.2 right now and have noticed things have been slowing down over the past year or so but I'm still fighting the urge to upgrade to a new phone. I still think Samsung nailed it with this model and would like to hang onto it a little while longer.
edit: I've been looking around and it looks like I'm out of luck because I'm probably on the 4.4.2 NE1 firmware. Sad times.
So I dug out my old SGS3 with the busted screen and swapped out the mainboards with the newer 4.4.2 one so I could get access to my old unlocked bootloader. Tried flashing the latest builds of Lineage, OctOS, and Carbon but all 3 would just bootloop. I thought maybe it was because I was on an old CWM recovery so I hunted all over until I found a ROM I could boot (an old Gingerbread AOKP build) so I could use it to install TWRP.
Got TWRP 3.1 going on there and tried again with all the Nougat ROMS (Lineage, OctOS, Carbon) but no luck, still the same behavior. So I threw in the towel and bought an Essential PH1. It's the only good looking phone I could find in the same size range as the SGS3.
*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.