Database Users

[Q] Stock rom 2.3.4 - BT Problems

hello all,
i have updated to 2.3.4 jvp from js3 telenor
all is fine, battery usage is much much better, no laggs, and no FC/FR..
i have turned on the bluetooth once set the name, and turned it off....
after i rooted and brought backups back,i cant use BT anymore. it just stands and turning on for a min or two, and than goes to TURNED OFF state...
update on the issue: i have recently de-odexed the phone, and the BT worked fine again for the first 3-4 initializations and than it hangs again in the way described above.
any help? any ideas?
i'm willing to try loading a custom modem or kernel to the phone to see if it helps, but as im new to this and didnt quite find the info im looking for. browsing for hours, (and i did ask in some threads to no avail.)
Will loading a custom modem/kernel wipe my data?
is there a solution perhaps?
ty again in advance

Edit: sorry wrong post

You're probably using a custum kernel.
Revert to stock kernel and BT will work
Or you can try my modified stock kernel where BT works fine

i think it is a custom kernel, as it came with CWM. Could it be the CWM thats causing this ?
is ur modified stock kernel rooted?
i would hate to loose cwm backup functions , can it be installed after?
and most important question: Will loading a custom modem/kernel wipe my data?
EDIT: just saw this in CWM
Current Kernel: CF-Root 3.7

There have been problems with CF-Root kernel and Bluetooth. I had the exact same thing.
Take a look at the CF-Root thread

Regarding flashing Glitch.v14-pre5 bootloop fix

Hi all
since i cannot post in Developer's apropriate forum i share with you here..
I have tried all ICS rom there is (not that many yet..) with Glitch v14 pr5 kernel, and they ALL give me bootloops... if not right away then after some period of time, and there is NO way to enter CWM
So i reflashed many many times in odin with different stock and other roms, but always with same result bootloops or a glitch screen logo that dont go any further.
Only if i go in recovery and format ALL options avalible and do a wipe data/factory reset afterwards + run the reset nstools zip avalible (off course only if you have been installing the glitch kernel )
Only then i get a error free install + i can boot in CWM and reboot whitout getting these errors......
Then im able to install > [ROM]SGS ICS 4.0.3 Doctor's ROM [01-12-2012]
and running on day 2 whit out any errors now..
Using nstools to oc and undervolt, is working fine selecting one of the 2 new goveneurs interactiveX or smartassv2 and DIDDLE deep sleep working perfect, BUT nstools wont tel you i always shows 0 in idle time (its nstolls fault) but voltage control EXTREME shows the right numbers
EDIT: Forgot to say that i pulled the externel sd card before going into CWM ! and do NOT deactivate nctools in app maneger !
Hope its ok posting this here ? plz delete or move else admins
Greets to all

[Q] Baseband broken? [half fixed]

HI, everyone
i got a problem with my defy recently.
i was running CM7 by Epsylon3.
As we all know, this rom comes with defy basebandswitcher v4.0, and it works well.
Yestoday, i want to update this "BBS" to v4.1. but when i uninstall v4.0 and install v4.1(http://forum.xda-developers.com/show....php?t=1203297), open it , it shows "unable to detect your baseband configuration, it's possibly damaged."
then i reinstall v4.0, but i cant find it in app drawer. i'm sure it's installed and i can see it in "setting-->applications-->manage applications" also in "dev tools-->package browser".
i tried the method in this thread: http://forum.xda-developers.com/showthread.php?p=21844497 . I renamed "system/etc/motorola/bp_nvm_default" and reset it to default use v4.1. but no new filefolder "bp_nvm_default" generated. and the problem still exist.
i also flashed offical SBF file 3.4.2_179-4.4(VFSBLUR) , 3.4.2_177-005(NORDIC) and reflashed CM7. still cant find app with v4.0 and the same message with v4.1.
Edit:half fixed... I reflashed stock sbf (different versions) several times , then flash CM7-11 again, after a bootloop, pull out the battery, power up, the "BBS" v4.0 bundled worked normally. but v4.1 still doesn't work.
Another question, i got a FOTA (com.motorola.process.system) FC. Maybe i should repost another thread. There is no responding here. Sorry for my poor english....

[Q] Problems Multiboot

Hi,
I'm trying to use Multiboot on my defy (Red lenses and GB kernel). My original rom is the latest CM9 by Quarx.
Every ROM I installed (I tried MIUI V4, XIUI and CM10, all for Defy+) I get com.android.phone FC and, I think its because of this error, i cannot find network (yes, I tried to switch my baseband to the correct one).
I tried Multiboot v0.6.1 and v0.5.1 and get the same error. I tried v0.7 with TWRP, but with this I stuck at Motorola logo.
Its the firist time i'm trying to use multiboot, I did all the steps of more than 1 tutorial and give me the same error. Anyone know something I may have missed? I'll keep trying and if I got something i'll post here.
Thanks.

did you get multiboot working?
if not, what error does it gave??
and what steps did you followed???

Basically I instaled multiboot V0.6.1, then installed Multiboot Manager Free and created an image with cache: 150Mb, data 250Mb, and system: 350Mb. Then I flashed one of the ROMs tha I mentioned.
I get it working, I can load the system, conect via wifi, navigate and etc, but after startup I get com.android.phone FC and get no signal. This happened with all the ROMs tha I've installed.
EDIT:
It seems that I could solve it, I uninstalled Multi Boot Manager and installed Vibhinna, deleted the old system image and did everything again. Now I get no errors.
Thanks.

You should also be aware that if you have a GB base ROM you should download the Defy+ versions of the ROMs you want to use in multiboot.

H918 WETA ROM 4.9.4 + Magisk 12.0 bootlooping

Hello there, I've been using the V20(H918) for a little while now and was running WETA Rom 4.8.5 with Magisk 11.0. When Magisk 12.0 released after rebooting and being on for a minute or 2 my phone would suddenly go back to the T-mo splash screen as if it were soft rebooting and then would repeat this process. I thought it might have been a download or flash issue so I tried wiping and doing a fresh install but if I ever restarted the device the same issue would appear. I've tried selecting or deselecting a majority of the options in the aroma installer for WETA but nothing seems to work. The rom seems to work fine with SuperSU installed so I'm thinking it might be something about the way my phone is set up but I haven't been able to pinpoint exactly what it is and I really would like to use Magisk for the hide feature. Based on the thread it doesn't seem like there should be any issues and I'm unable to ask my question directly in the thread. I'm not very experienced with these kinds of things so I'm sorry if I'm not being specific enough or if the solution is obvious. Thanks for anyone's help and time with this issue!

survivingarch said:
Hello there, I've been using the V20(H918) for a little while now and was running WETA Rom 4.8.5 with Magisk 11.0. When Magisk 12.0 released after rebooting and being on for a minute or 2 my phone would suddenly go back to the T-mo splash screen as if it were soft rebooting and then would repeat this process. I thought it might have been a download or flash issue so I tried wiping and doing a fresh install but if I ever restarted the device the same issue would appear. I've tried selecting or deselecting a majority of the options in the aroma installer for WETA but nothing seems to work. The rom seems to work fine with SuperSU installed so I'm thinking it might be something about the way my phone is set up but I haven't been able to pinpoint exactly what it is and I really would like to use Magisk for the hide feature. Based on the thread it doesn't seem like there should be any issues and I'm unable to ask my question directly in the thread. I'm not very experienced with these kinds of things so I'm sorry if I'm not being specific enough or if the solution is obvious. Thanks for anyone's help and time with this issue!
Click to expand...
Click to collapse
alot of people have this problem with 12.0 flash the 11.0 and dont update

survivingarch said:
Hello there, I've been using the V20(H918) for a little while now and was running WETA Rom 4.8.5 with Magisk 11.0. When Magisk 12.0 released after rebooting and being on for a minute or 2 my phone would suddenly go back to the T-mo splash screen as if it were soft rebooting and then would repeat this process. I thought it might have been a download or flash issue so I tried wiping and doing a fresh install but if I ever restarted the device the same issue would appear. I've tried selecting or deselecting a majority of the options in the aroma installer for WETA but nothing seems to work. The rom seems to work fine with SuperSU installed so I'm thinking it might be something about the way my phone is set up but I haven't been able to pinpoint exactly what it is and I really would like to use Magisk for the hide feature. Based on the thread it doesn't seem like there should be any issues and I'm unable to ask my question directly in the thread. I'm not very experienced with these kinds of things so I'm sorry if I'm not being specific enough or if the solution is obvious. Thanks for anyone's help and time with this issue!
Click to expand...
Click to collapse
Im currently running weta rom with magisk 12.0 on my h918. However there are 2 possible differences between yours and mine. 1) you are not in the latest version of weta rom 4.9.4. 2) you are probably flashing the stock kernel that comes in the weta aroma installer. Try with konvergent or another kernel other than the one from weta rom. (as soon as i flashed the weta kernel my phone was experiencing the dame thing yours did , then after i flashed konvergent back it came back to normal)

jinkerz9430 said:
Im currently running weta rom with magisk 12.0 on my h918. However there are 2 possible differences between yours and mine. 1) you are not in the latest version of weta rom 4.9.4. 2) you are probably flashing the stock kernel that comes in the weta aroma installer. Try with konvergent or another kernel other than the one from weta rom. (as soon as i flashed the weta kernel my phone was experiencing the dame thing yours did , then after i flashed konvergent back it came back to normal)
Click to expand...
Click to collapse
Did what you said and everything seems to be running smoothly, thanks very much for your help! Hoping a more updated kernel that doesn't force SuperSU and works with magisk comes out soon!