Want to find a fix to all custom ROM's bootlooping on my SM-J320FN (did not bootloop before) - Samsung Galaxy J3 (2016) Questions & Answers

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

Related

[Noob Time] Why FLash To CM 10.1 ?

Good Evening Dudes
I'm just introduced on this section and it's first time than i ve had a stuff like this awesome samsung
Smooth Fast Strong And God ! it's the beautifull customisable stock rom (it's really beautifull to compare with htc stock rom)
well the question is not here and the target also
i've never had the oppotunitities to try a CM 10.1 on any device Htc desire x hasnt official CM and not possible to port CM10.1 cauz Htc doesnt provide the kernel source.... damn
(it's was juste for put in situation)
What's the real interest -Gain can i expect with the CM10.1 on the Galaxy S4 ?
Whith this rom it's sound interesting to put a custom kernel also.
what can we do with cm 10.1 than we cannot with a stock rom ?
Yeah a know , i can make a backup on my stock rom , flash the cm 10.1 try and if doesnt like it restore to the backuped stock.
Thanks for your time
If you had any other suggestion better than the CM 10.1 (i know it s on nightlies sound like equal as alpha but
topic is open :s
Well the Stock ROM is pretty much as bloated as a whale. CM is only 200MB in size, so first of all it will save space on your internal memory. Second of all, you won't have a lot of processes running in the background like you do now, your phone will be a LOT more responsive. Ofcourse, as with any custom ROM, there will be some bugs and those ROMs will need testing and updates (that's why nightlies exist). But eventually there will be stable versions and imo, it'll beat the stock any day. On the other hand, the stock ROM has some functions like the IR blaster, the smart-pause, smart-scroll and hover function, etc. If you're a big fan of those things, stick with your Stock ROM. But if you would like to a clean, simple, bloat free and faster experience than you have now, a custom ROM is a great way to achieve it. But that's not the only thing ofcourse, CM also has some extra functions and customization options you won't find in your stock ROM, you can tweak your system quite a lot and there are some things I couldn't live without (for example swapping your menu key for your recent apps switcher, and putting the menu function on the long press ).
Thanks a lot
Sound really interesting
CM 10.1 it's more in touch with i'm looking for
The actual build of CM 10.1 can be used on a basic day usage ? or it's better to wait a few days ?
If i flash the cm now ? need also to flash another kernel or just flash the zip by philw touch recovery ?
can i come back to my stock backuped rom after if i want ? with the restore function of philz touch recovery ?
I'm using Philz Recovery too and yes you can flash CM10.1 from there (I have the latest build from June 12th on it). Before you flash, make your sure you wipe/factory reset your phone in Philz Recovery. You might also need to flash the CM10.1 rom 2 or 3 times (the second time it usually works), on the first try it always gives a Status 7 error (don't worry). Look at the thread for the Offical CM10.1 Nightlies, there's a lot information there!
It's working pretty good for me, I haven't found any major bugs so far. Just make sure you make a Nandroid backup in Philz Recovery first (and store it your external SD card for safety and to save space ofcourse ). You can always return to that backup through the restore function in Philz Recovery yes.
Also, if you update your CM10.1 with a new nightly build (for example next week, or next month), do it manually and flash it in the recovery each time. Updating it from the Settings->About->Cyanogenmod Updates menu bricked my phone today, so I guess there is still a bug there. Besides that, there are no issues what so ever according to me.
PS: You're from Liege? I'm from Genk
last question before the first try
With the original Cm we need to flash gapps separately or it's inside the rom ?
If external suppose to take the last release on goo
If I remember correctly you need to flash it separately
Sent from my GT-I9505 using xda app-developers app
Try This one -> http://forum.xda-developers.com/showthread.php?t=2296266
Yeah after flash the rom 4 times finally she install correctly ( 3 times error7 but no affraid)
Ui is clear, phone running smooth and very well no issue with wifi or 3g
The first bug i ve seen was about the carrier name -- the carrier name is showed like an id on a database (think the code for showed the cells with carrier name is not correct)
For the rest no speciq issue detected
Thanks a lot for your help
PS : i ve also find a answer to one of my question
when use cm you must flsah the gapps separately and link is coming on cyanogen page.
I ve read also than the build for the S4 T-mobile seems to work fine on this phone more bugs corrected on it ?
No trying BT for the moment cauz i dont had BT device
@disturbed : i ll try the rom linked this evening . Thanks a lot

CM13/MM Netflix Loading Issue on N910C

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?

[Help] Back after long time, huge amount of confusion

Hello,
It's been almost a little over a year since I was last really into android customization. Since it's been so long it has become clear to me that my phone is outdated in many ways. I'm still running OxygenOS 2.2.1 with Android 5.1.1. I've been wanting to update up to Android N (7.x.x) for a long time now, but haven't seen any real stable roms or haven't really had the time to look for one. Now I've finally found my self with free time and ready upgrade my rom. I've just faced couple of problems, I can't really find what should I do when upgrading from 5.1.1 to 7.x.x since no-one is really doing that anymore. I remember reading sometime back that if you dont have the right firmwares you'll brick ur phone, and I wouldn't really want to go through that hassle at the moment. Is it still a thing or should it be just fine for me to flash a new rom just on top of this? (Ofc with clearing memory etc) Other question that is in my mind is that is there any critical bugs in Android N roms? It's bit unclear to me since there are such many roms that have their status as work in progress or beta etc, but some roms have status as stable. Are there any roms that I should clearly avoid? Im not new to this so I don't really need any deep info how to do everything etc, just a bit of a oversight on how things are going atm.
Thanks.
first of all is ur device rooted?? If yes then install the latest twrp recovery...then take a backup.. and flash any nougat rom which u like...If at all u would need Volte support then u l have to flash the 3.5.7 firmware..or else the 3.1.0 firmware works fine with most of the nougat roms..some nougat roms i would recommend are AICP, Resurrection Remix and AOSP extended .... In my suggestion u should probably first upgrade the Oxygen Os on ur device through official updates via OTA atleast upto the 3.5.6 firmware
there's no need to update until 3.5.6, unless you aren't going to plan staying with OOS [the only "stable" firmware which provides you VoLTE working, but it's still M-based and not N].
as @mhd athiq said, unlock your bootloader [just in case you still haven't done it before] then update your TWRP recovery to the latest version.
then flash the incrementals OTAs until OOS 3.1.x and you are good to go to flash any custom ROM which is N-based.
to avoid any mistake, please make a EFS backup via terminal [just to have a backup of your modems] and save the files to a safe location.
I don't have a specific ROM to suggest to you, but in my experience I have found the CAF/AOSP-based ones to be the ones with the best battery backup and less bugs then LOS-based ones.
I have used happily for a few months CypherOS version 3.5.1 [not the latest one, I find it quite unstable as the developers tried to implement OMS].
sidenote:
flashing N-based custom ROMs upon OOS 3.5.6 firmwares gives random reboots and unstable network in many cases/scenarios.
so don't update to that OOS version unless you have a mandatory VoLTE feature required [but you'll have to live with random reboots and poor network stability].

Samsung S5 G900T ROM Help

Hello everyone, I'm pretty new around here I guess you could say, but I'm here today looking for your help.
I've had an S5 for almost a year now and have gone off and on with different rooting (had SuperSU and now have Magisk). But anyways, I am wondering what the "big deal" about Custom ROMs are. I've read up a little but haven't been able to decide on if it's a good idea or not. For example, I looked at Resurection Remix OS for the S5 and it seems pretty cool. Except I loose my data. Now I'm not too worried about that, but I would like to keep my text messages and such (if anyone could tell me how to back that up, that'd be great).
The second problem is that, I'm worried that I may end up hard-bricking my S5 when trying to install a Custom ROM on it, as this would be the first time.
The third problem is, I have no idea what ROM would be best suited for both me and the phone.
In summary, what I'm asking is:
1. What advantages/disadvanges are there for installing a Custom ROM on my S5.
1a. How would I backup important information (text-messages mainly, as I have done nanodroid backups and such)?
2. How "hard" is it to hard-brick a phone from installing a Custom ROM?
3. What good ROMs are out there that are well suited for the S5?

Twrp for 11?

Hey guys,
Anyone have any info when either unofficial or official twrp is coming for Android 11? I made the mistake of upgrading to 11 from 10 then tried flashing twrp which bricked my phone ( I fixed it, no biggie ). I just really want to flash a custom ROM and I can't find any other custom recovery that will do that and side loading twrp also gives a crashdump error. Unless anyone knows how to downgrade to 10, the the furthest downgrade I've achieved is 11.0.0, once I hit 10.x.x I get either a black screen or crash dump.
It's a lot there, I know. Much appreciated everyone.
Edit: reading more on this forum, I think I found a way to flash a custom ROM on Android 11.. I guess you can side load roms? So I guess I'm going to give that a try. I'm so old school, like back in 2011.
I had the same problem. Im using the Lineage recovery atm an idk why tbh. I think i used it for rooting and for now im only using magisk modules to obtain some featurers.
Sideloading roms is a thing but man i miss those old HTC Hero., HTC Desire times. Last years i was using a P30 pro without root and im so happy to have root again.
Anyway read carefully and have fun. I would love some answers from your experience here.
Do0ks said:
I just really want to flash a custom ROM
Click to expand...
Click to collapse
Most custom roms include all the files needed to flash the entire rom from a batch file. CrDroid for sure, but also Lineage. I'm sure there are more. My issue is not flashing, it's that all important nand backup from TWRP I miss the most. Switching roms is a lot more tedious when you have to re-install everything to revert back to your old setup.
Twrp for 8 and 8 pro may not happen ever, encryption is the problem
TWRP doesn't look promising considering the time that has passed since 8 launch...

Categories

Resources