Database Users

[Q] What is params.bin and can it mess up my phone or can it fix my bluetooth?

Hey guys,
I'm currently using OzcanRom and it's just great - strongly recommended!
My only issue is exactly the same issue as described in this post:
I'm facing a very strange problem as i'm unable to switch on my bluetooth... last week only i rooted my phone and installed CWM recovery...then i installed Custom Rom's like Hassan ROM, Omega ROM, Cyanogenmod 11 Rom, Pacman ROM etc etc just to check various Rom's and their features out.....At first i installed only one ROM at a time and den also dual booted two ROM's by romswitcher...While i was checking my phone once i discovered that my phone's Bluetooth is not turning ON...The toggle is only becoming light green and also from the settings its only showing turning Bluetooth On but it's unable to turn bluetooth On.....Now i googled my problem and read across various forums for solution...I tried various things also flashed my firmware to stock samsung but still bluetooth does not turn On...also i flashed with stock samsung firmware of feb and march 2014 and updated my phone over OTA but still the problem persists....i even installed latest perseus kernel while rooted but still could not turn my bluetooth ON.
I would be very grateful if someone can help me solve my problem and help me Switch ON my bluetooth as it is very needed aspect for my daily use.
My Version of S4 is i9500 with android kitkat 4.4.2. Also all my other features are working normally on custom ROM's too.
Click to expand...
Click to collapse
I too installed this Omega rom at some point and once I did that these problems started.
A user in that thread posted a reply in which he uploaded a file which he claims fixed his problem.
I really need my bluetooth to work again and would love to flash this file using Odin if it would fix the problem
BUT
I have no clue what implications flashing this file can have, can it mess other things up? I've spent the last four hours setting things up again in my new ROM and I would hate to have to do it again or even worse, cause some unsolvable problem with my phone.
I assume some of the developers here could help me out - should I run it?
Thanks!

[Q] [N910F][Super fast and lollifamous] no sound

Hi, I have just installed latest Super fast and lollifamous ROM. This was 1st modification I made to my device. I used custom recovery from official ROM thread on xda. Now I have no sound on my phone. I have no idea what can I do in order to fix it. Can you help me? Thank you in advance.

Mikiwaw said:
Hi, I have just installed latest Super fast and lollifamous ROM. This was 1st modification I made to my device. I used custom recovery from official ROM thread on xda. Now I have no sound on my phone. I have no idea what can I do in order to fix it. Can you help me? Thank you in advance.
Click to expand...
Click to collapse
Firstly you should read the last ten Page's of said thread and see if anyone has this issue, if not then you could try factory resetting the device and see if that clears up the problem or
Flash stock firmware with Odin and test hardware. That rule's out any issues with the device itself and work from there.
Sent from my trltexx

Is there a way to multi boot different roms on the G2?

Hello,
I know dual boot and multirom! And I'm struggling a lot with multirom, can't get it to work... I can't find the "right" kernel, some files in the thread are dead and so on.. The thread seems kind of dead to me. I was trying for days now.
So is there somebody out there, who can provide us with working links / files and an short working instruction how we can boot different roms?
My device is D802. I don't care if my priamry ROM will be a Kitkat Stock or Resurrection Rom...
I'd be very grateful! Thank you!

Can somebody who really has an overview tell us if there is a way for multi boot on the G2 at all...
As I read on, I get the impression that it's not possible because of the locked bootloeader but then I don't understad why there was a thread about multirom... And I can't read pages of the multirom thread, it's too much
We need somebody with more experience here
Thanks again

I remember that someone talk about multiboot and say that lg g2 can boot only aosp ROM with another aosp or stock and another stock because of locked bootlader

amin44 said:
I remember that someone talk about multiboot and say that lg g2 can boot only aosp ROM with another aosp or stock and another stock because of locked bootlader
Click to expand...
Click to collapse
ok, thx, ****ty news :/
Also found this, but as too often, no summary, understable instructions - so for only a little circle of devs themselves in the end. That's kind of bitter.
http://forum.xda-developers.com/lg-g2/general/multi-boot-dual-boot-stock-slim-t2993233
It says e.g. you have fo flash a modem and there's a link with many different modems. So if you are not really deep in it, it is hardly usable. Also it semms to me that you have to read the whole thing to have a clue, the fiest post isn't updated (probably -on first glance)
Too bad. But I'm sticking on this. I want the multi/dual boot.

Need help finding the cause of the static on boot problem

OK, i know that most roms have the static on boot problem, which in itself isnt a big deal. But, i have found that the werewolf kernel doesnt have that issue. could someone help me find out why that kernel doesnt have that problem so we may fix other kernels? the kernel ends up freezing my UI and i have to reboot. Not sure if its related or not. I havent seen this anywhere so i thought i would post it. i am willing to test the kernel if i can get some help. Or just point me in the right direction on what i would need to look for if i tried to edit the kernel myself

It's open source isn't it? Look at the difference between the unmodified kernel source. I use that kernel as well to fix comfort view while not having static. The first time I tried the kernel my screen didn't respond to touch at all, not sure why it works now

lg kernels have the issue. werewolf is build from qualcomm sources with drivers added for our phones(same way lineage does it which is why theirs is fixed also) The fixes for those kernels cannot be applied to a standard kernel.

Want to find a fix to all custom ROM's bootlooping on my SM-J320FN (did not bootloop before)

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