So, I'm definitely not new to the world of running custom roms at all and am finding myself stuck in my current situation with no explanation as to what is wrong. I've literally ran almost every rom there is to offer the MXPE minus the nougat roms with the exception of AICP and CM14. All of a sudden now anything I flash just loops forever. I've tried even restoring to stock then starting over again at 5.1.1, rooting, and then the only thing that has successfully flashed have been TruPureXMM and Sabissimos stock rooted ROM. Has anyone else ran into this issue or can shed some light from past experiences, PLEASE, let me know.
Related
So I've recently rooted and installed a custom rom on my phone for the first time with success. My phone is the T-Mobile Galaxy S3 N900T. I'm running C-Rom-KK-v7.1-20140622 which is based on 4.4.4 and it's great. I've been trying to find a custom kernel that I can load onto it to help increase the battery life, hence why I heard LK was really good for that, unfortunately every time I flash the kernel it just reboots to a black screen. The LED buttons will sometimes light up, but nothing else happens, and I'm forced to wipe and reinstall c-rom. I'm really looking forward to getting a custom kernel to work and any help would be appreciated.
OneDarkNite said:
So I've recently rooted and installed a custom rom on my phone for the first time with success. My phone is the T-Mobile Galaxy S3 N900T. I'm running C-Rom-KK-v7.1-20140622 which is based on 4.4.4 and it's great. I've been trying to find a custom kernel that I can load onto it to help increase the battery life, hence why I heard LK was really good for that, unfortunately every time I flash the kernel it just reboots to a black screen. The LED buttons will sometimes light up, but nothing else happens, and I'm forced to wipe and reinstall c-rom. I'm really looking forward to getting a custom kernel to work and any help would be appreciated.
Click to expand...
Click to collapse
Been a while since I scanned the N3 forum however, check that the ROM is compatible with the Kernel and If the Kernel does indeed run on the 900T - when I had my N3 T-Mo users used to have to flash a fix to boot N9005 kernels.
Could anyone of you guys kindly help me. I first flashed the unofficial Bliss rom based on cm13 first on my n910c. It was stable enough for daily use, maybe a bit rusty on kernel performance end but nothing too drastic. I however found one of my favourite and must have app Netflix would refuse to work on it whatsoever (loading spins forever when trying to play any movie/tv show). I have searched all over the net to understand why and now I also flashed this cm13 image to see if it could work in this rom. Result same issue!, I did the following and achieved no success
1) cache/dalvik clean and rebooted (the obvious) ALSO full factory wipe as well
2)a suggestion to rename/delete a certain liboencrypto.so
3)change my product model in build.prop
4)try a old xposed hack for tricking the app to think you are on unrooted phone
None of the above worked. I then flashed a lolipop simplerom5c image just to check if this issue is universal for all roms and I was wrong. Netflix ran with no issues in this one which uses a custom kernel and full rooted.
NOW MY actual question (pardon me for the boring and lengthy prologue)
Would flashing a custom kernel to CM13 for n910c possible? if so which one could anyone suggest? AND could it possible solve the dreaded Netflix issue?
I need some help, anyone, please! I have a Lg G2 VS980, rooted supersu by chainfire version 2.79 latest, i guess. twrp 3.2.0-1 by blastagator, and running resurrection remix 5.4.7(Lollipop 5.1.1) from stock rom VS98024a which i pushed with lgtool14, i believe. From stock VS98011a which i also installed a year ago when my ParanoidAndroid os Lollipop rom 5.1.1 just stopped working all together dont know why, still. tried flashing over that with lollipop CrDroid rom Lollipop 5.1.1 when the phone bricked. So I proceeded to start from scratch again learning as i go, im kinda good like that sometimes. so i did all of this all is working well and good again, except for one thing, when I try to flash any custom marshmallow even nougat roms they install like the lollipop ones fine, matching micro Gapps packages every time for marshmallow and nougat roms. wipe the dalvik and cache properly, all is good til reboot of the system. Lg logo comes up then black screen and nothing else ever, Ive let it sit for hours and nothing. i dont know what i am missing here i know its possible to go past lollipop but im at a loss here. ive searched til my eyes bleed but there is no comprehensive guide on how this is accomplished and what to do with the black screen issue im facing. i dont know if i need to do a bootstack change or something else i dont know about. If i could get some guidance here maybe a solution to this issue. hell i dont care if i got to start from scratch again. something guys. if you need any info i havent provided ask. and yes i have all the proper latest drivers, adb, fastboot, and even latest android studio from google, which i dont have a clue as to how to use. im not a noob but by no means a developer, lol.
Hi Guys
I have my Galaxy S5 now +- 3 years, and use a custom rom about 2 years now...
Until now, I'm unable to boot any custom rom, everything freezes at the boot screen...
I was using Resurrection Remix Nougat, but can't update it, not dirty and not clean.
Today I flashed a stock rom with Odin, and I can't boot any custom rom except the stock rom...
Can someone help me please?
thanks in advance!
Check the bootloader and modem, if it's the correct version. Otherwise, recovery might be the culprit. Nougat ROMs are kind of sensitive to older basebands, though results might actually vary.
Want to find a fix to all custom ROM's bootlooping on my SM-J320FN (did not bootloop before)
[
or alternatevly, i was wondering if modifying a some samsung galaxy SM-J320[something] nougat rom, to work on SM-J320FN would be possible (it has only android5.1.1 (lollipop) stock rom as far as im aware and i have searched quite a lot).
]
The thing is, i have the SM-J320FN (twrp and rooted) and for a while i ran various custom roms (based on nougat) on it with no problems. But then about a year ago it bootlooped on resurrection remix (which i had ran with not many problems for 1/2year). Then every custom rom (i tried RR, DotOS, ViperOS and more) began to give me a bootloop, only flashing the stock rom booted.
I wiped and formated everything i could, tried same country stock rom that i had originally and a different country one (thinking maybe the custom roms were not happy with something inside the stock rom that it was flashed after, but logically it does not seem even possible, as before flashing the custom one, the old one is wiped), but custom rom's just did not boot anymore. I could not log the boot either because it had boot animation but nothing showed in adb, i guess it did not get so far that it could connect with adb.
I suspect this may be caused by my camera not working (some hardware part most likely got damaged), because i think wiping my phone completely and flashing stock rom with Odin should restore every software part on the phone thus it would have to be something with hardware that's causing custom roms to bootloop, how else could the problem persist (i obviously might be wrong).
I don't remember when exactly the camera stopped working but i know for a fact that i had a custom rom at the same time, and it did not bootloop (for some time at least) and im also curious why this has not ever stopped the stock rom from booting if it is the case.
So basically what i wish i could do are two things. Firstly find what makes the stock roms able to boot correctly opposed to the custom ones. And secondly implement this to a similar models higher version rom or a custom rom (Nougat). Come to think of this, it seems a useful step to look how did the people that made these Nougat based rom's for SM-J320FN modify the rom so that it could run on it, the source code is open after all.
Why i want to have a higher android version on my phone? Because my countrys corona close contact detection app supports only 6.0 or higher and my banking app recently notified me that they will soon end support for my android version too (this is the real pusher for me as i use it very frequently and there is not really an alternative). And it would be nice to have some other apps too, that not compatible with Lollipop.
And yes, i know, just buying a newer phone would solve all my problems But im a minimalistic (and without money) person. The fact that i own a phone that is still working (or fixable) stops me mentally from buying a new one. Also as one would guess, i like tinkering with this kind of stuff (i study CS currently) and building a rom myself for my phone sounds like a cool and challenging project, as i have not done anything like this before (maybe this will help me: [guide]how to build/modify roms for samsung devices [7.0/6.0.1/maybe more]).
Anyways, i kinda got carried away with this post. But for now im tired and have to sleep so i'll just post this and will come back later to read this over, fix some mistakes (not a native english speaker) and add things i maybe missed.
If anyone read this through, im impressed and if you have the knowledge/time to answer then i Thank You in advance!
i need help i tried to install re dreaux but my phone bootloop on touch wiz custom rom so how can i fix that