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!

Problem with all CM 12 Roms I9500

hey everyone
so ... i decided not to flash any samsung rom again as they are like @ [email protected]!# !!!! they are extremely laggy and CM is awesome even with some bugs but i don't know why my device seems to be the only one which has this problem
after installing tean canjica rom at the begging i got no service then the signal appeared for about couple of seconds then no service again
and that never stops and 99.9999% of time is no serivce
tried 3 different modems with 3 different methods ( TWRP , CWM & odin )
but still no luck
ps. when i flash samsung stock the problem disappears but on TeamCanjica or Remix rom the problem appears
thanks for your time

DaRkEMpRoR said:
hey everyone
so ... i decided not to flash any samsung rom again as they are like @ [email protected]!# !!!! they are extremely laggy and CM is awesome even with some bugs but i don't know why my device seems to be the only one which has this problem
after installing tean canjica rom at the begging i got no service then the signal appeared for about couple of seconds then no service again
and that never stops and 99.9999% of time is no serivce
tried 3 different modems with 3 different methods ( TWRP , CWM & odin )
but still no luck
ps. when i flash samsung stock the problem disappears but on TeamCanjica or Remix rom the problem appears
thanks for your time
Click to expand...
Click to collapse
Hi,
Wait for new build comes up. I see on TeamCanjica's thread, the developer will update the ROM. I tested GearCM and no network problem (before I revert to Prism Barebone). The problems you mention above might apply on all CM based ROMs that using TeamCanjica's device tree until their sources updated.
Possibly workaround is to update your modem.

Note 3 (N9005) auto rotation does not work for any CFW

Dear Community,
I hope that this is the right place to post and any of you can help me.
My (aktual) Hardware/Software bits:
Galaxy Note 3 (SM-N9005)
Android: 5.1.1
Baseband-Version: N9005XXUGBOD3
Kernel-Version 3.4.108-f2fs-temasek-cm12.1-hlte-v1.25+
temaseksnappy #1
Temasek unofficial version V16.4
Build: LMY48J test-keys
Recovery: twrp 2.8.7.0-hlte-4.4
My actual problem is the following: My Note 3 by default had a 4.4.2 OFW on it, which I early upgraded to Lolipop 5.0.1. Everything works for the OFW 4.4.2 and 5.0.1 fine. As soon as I try to flash it with a CFW like CM11, CM12, CM12.1, CM12.1 (temaseksnappy), Gummy 4.4.4 I am losing the feature of auto rotation.
Of cource I did a clean flash, wiping DALVIK/CACHE/DATA and system, double time even one befor the flash, one after.
I also tried to put the battery, sim and sd out for few min before rebooting, while autorotation is manualy turned off.
Even a MODEM I flushed to fix this issue, but without success. Nothing helps but going back to OFW.
My last try was downgrading to the original 4.4.2, including baseband trieing from there to go to any CFW (CM11) as well as from OFW 4.4.2 -> OFW 5.0.1 -> CFW 5.1.1 (http://forum.xda-developers.com/galaxy-note-3/development/hlte-spr-vzw-temaseks-unofficial-t2953375)
There was also a post about a possible missing or broken lib in /system/lib which I replaced
Nothing helps (libGNU... something). This helped me alreay once in OFW after kicking out all the junk apps, but this is a different storry and not related anyhow.
Is there anybody out there who has the same problem or even better knows a solution?
My shot would be that:
1) CM has a problem with my particular hard-/software (Kernel, Baseband, Recovery, whatever) as I just tied CM or at least CM based CFWs.
PLEASE HELP.
Thank you very much in advance.

After about almost a year I cam back, giving again a try to CM, However I still have the same issue. Finally Anybody please!

Do you have the same issue with touchwiz 5.1.1 and 6.0.1?. Not the cm/aosp roms which aren't samsung based.
Sent from my SM-N920C

Rosli59564 said:
Do you have the same issue with touchwiz 5.1.1 and 6.0.1?. Not the cm/aosp roms which aren't samsung based.
Sent from my SM-N920C
Click to expand...
Click to collapse
Hello,
Thx for your reply. Right now I am on CM13 (temasek hlte v9.6)
http://forum.xda-developers.com/galaxy-note-3/development/hlte-spr-vzw-temaseks-unofficial-t2953375
This might should be specially compiled for sm-n9005 like mine.
Everything expect rotation works fine. However The accelleration is also working fine as I tested with "sensor test". Even the integrated camera App is rotating, however the rest is not.
In addition I downloaded "adaptive rotationfree", If I set it "stock Auto" nothing happens, but if I set it to "force auto" the rotation will work exacly once and then stops undtil I force it to portrait again.
What do you mean exactly with "touchwiz"? Is this jus a different kernel or a whole CFW?
As I wrote in the frist post I tried already a lot of CFW and ALL had this issue, but the OFW ;(
What shell I flush to get this working, which is not OFW?
BIG THX for YOUR HELP

Touchwizz is the firmware that comes with the stock Samsung firmware .
Also in custom Samsung based roms .

Hello,
thx for the tip with TouchWiz vs aosp. At the moment I am running "DarkLord N5 Release Candidate 2.12" which can get find here: http://forum.xda-developers.com/galaxy-note-3/development/rom-darklord-s6-port-alpha-t3083087
This Rom is TouchWiz Based and guess what ....
Autorotation works.
However I do not understand what the problem realy is and would prefer to run cm13 insteat. I mean even samsung devices got a accellerator within which works also fine with AOSP software, showing numbers moving while turning the phone. In addition for example on the post http://forum.xda-developers.com/galaxy-note-3/development/hlte-spr-vzw-temaseks-unofficial-t2953375 it is said that this is explicite for note 3 including the model n9005. So ...
Can anybody point me to the problem or even better to the fix?
Is there any chance CM would fix this?
Regards

S3 Neo (I9300I) Bootloops randomly

Hi guys! my s3 neo started randomly bootlooping after 1 year, I had RR 5.5.9 on it. I noticed that if I press button_vol_up when bootlooping the phone starts to access recovery, but suddenly continue rebooting so I tried to wipe ALL in the s3 neo from TWRP and with Odin I reflashed a new version of TWRP. After that, I clean installed the RR 5.5.9 and for a few days started working good.
Yesterday night the problem seems reappeared and then I soldered a new power button thinking it was the problem ( even if it's a random problem, it seems) but without fixing this problem. So I decided to desolder the power_button and starting using without it, and the phone was working very good, after 6 hours booom! the bootlooping is still here.
Can anyone help me? Thanks in Advance

When your RR is based on CM12.1 then the bootloop occurs when you install some new updated apps. You have 3 choices.
1) avoid these apps
2) Inform the developer of the apps, that with the new update your cm12.1 version gets a bootloop. The bootloop occurs, when the updated Version of the app was build with the new android build tools. The Solution is to use aapt instead of aapt2
3) upgrade to cm13 or cm14.1 . Theres also a RR based on 14.1. I didn't try this version, but i think with this rom you will not have the bootloop

same problem.
I have tried to flash it with many firmware without any success.
any help

alaa92 said:
same problem.
I have tried to flash it with many firmware without any success.
any help
Click to expand...
Click to collapse
What exactly is your problem?
Meanwhile there are quite stable Custom Roms that would be there:
- CM 12.1 from December 2017 (no more bootloops!)
- LOS 14.1 from August or also December 2018
- crDroid from November 2018

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