Database Develop

Sensors not calibrated correctly

Hey guys,
This problem is here longer for me, I've already sent back my phone 2 times, and they won't resolve the issue.
My problem is that the accelerometer is not calibrated right. One side is ok, but in landscape mode it's calibrated horrible. For example, when I use the app 'Google Sky Map' holding the phone in portrait mode just works ok (the horizon is in a straight line). Switching to landscape makes it bad, the horizon is now from 1 corner into another corner...
As I said before, i've already returned it twice to HTC via the shop I bought it. They say I can calibrate it in the program settings. But that's the problem, in al lot of program's / games i cant. Also the plain android homescreen rotates irritating because of the bad callibration.
So, I googled about the issue and couldn't find any solution. But I did find some folder / file (akmd_set.txt) where the sensor info is stored. I have rooted my device, and am running the latest CyanogenMod on it. I already wiped, returned old (non root, stock) android versions on it, rooted again, flashed cyanogen. But none of this works....
Does anyone know a solution to calibrate my settings? Can I get that file, edit it on my PC and flash it back in maybe?
If yes, please explain me
Thanks in advance!

Don't take my word for gospel or anything but....
As far as I know, that file is auto-generated, meaning you can delete it and it will force the accelerometer to recalibrate itself.
I think Cyan's and RA's recoveries both have an option to "Wipe Rotate Settings" which I've done several times, so I know it's safe. Try this if you haven't already. Hope this helps.

Thanks for the reply, trying it out now.
Did the wipe rotation settings option I have to see if it worked, because none of my aps are working now.... they all have an plain android box icon and clicking on them says the app is not installed.
Yeah, i've got Apps2SD and the SD card is loaded, how to fix this? Then I can check if it worked with the Sky Map program.
Oh, and if not, how do I remove that file via terminal?
EDIT: Damn, can't get the apps to work again my whole phone seems broken now. I even can't install new apps :S
EDIT2: Just checked my SD card, it is still working good at my PC, but not in my phone. At once the phone can't read SD cards... Please, does somebody a solution?

It sounds like you wiped ext through recovery. Search on how to explore your sd card as root and see if your apps are there. You may need to reflash your rom unless you have a nandroid backup you can restore.

r4d14n7 said:
It sounds like you wiped ext through recovery. Search on how to explore your sd card as root and see if your apps are there. You may need to reflash your rom unless you have a nandroid backup you can restore.
Click to expand...
Click to collapse
Nope I didn't do that, it was just a file in the CM Rom that was changed. The phone wasn't able to read the SD card, but the PC was and in recovery mode it could read it too... So I just flashed the CM Mod again and it's working now.
Problem is, my sensors still don't work Please does anyone has a solution, or a how-to on how to change the file?

Sorry you're having so much trouble with this, but it's beyond my scope of knowledge at this point. Hopefully someone else can check it out. If the Cyanogen IRC channel is still around you might be able to find help there.

[Q] Phone is wigging out, need techsperts help.

Hi guys,
I have been searching the forums for 2 weeks now trying to fix this myself, but I have put my pride in my pocket and am asking for help.
Backstory: Rooted phone, flashed CWM, used tons of custom froyo ROM's (doc roms mainly) and most recently Darky's 9.3 (awesome).
But then i decided I wanted Gingerbread (this is where the trouble began). Gingerbread worked just fine, but as there is no custom roms, I flashed back to 2.2 (obviosly screwed something up), because since then I have been plagued with process com.whatever.android.somethingelse has stopped unexpectedly. please try again.
please don't ask which force close message I am getting, lets just say, I am pretty sure I am getting them all!
I have flashed stock 2.1, custom 2.1, stock 2.2, custom 2.2's, I even went back to gingerbread a few times trying to fix this ***** of a problem. I tried re partitioning just the .pit file and then the other 3 files seporatly. NOTHING WORKS.
So, I am calling out to all you guys and girls who are heaps smarter than me to please help. the phone functions, turns on, make or receive calls and texts (not mms), emails work sometimes, but if I turn the phone off and on all the settings are wiped and I need to reload all the user details.
Oh, I should also add another major issue, I cannot use the internal memory for anything, I cannot take pictures unless I select the external SD card, I cannot install apps from market or .apk. I cannot even move data to it when its mounted on the pc.
I am completely lost. please help me.
And thanks in advance.
I

C'mon guys, I know there is a lot to read, but please, can no-body help me?

Sounds like it might be a dead internal sd card. You said you tried a re-partition with 3 file firmware? That should fix pretty much anything. I think your only option is to return to samsung at this point.

DrFredPhD said:
Sounds like it might be a dead internal sd card. You said you tried a re-partition with 3 file firmware? That should fix pretty much anything. I think your only option is to return to samsung at this point.
Click to expand...
Click to collapse
Thanks for the response.
is it possible to fix myself?
As Samsung will not cover it, even if I flash the stock Telstra ROM, it will still show that it has been rooted?

In doing your research, I'm sure you've heard of the internal SD problems that plague the i9000, are you by chance with Bell Mobility? This line concerns me..
"Oh, I should also add another major issue, I cannot use the internal memory for anything"
When I experienced multiple FCs (force closes) and incompatible system UID's, I tried flashing every kind of ROM there was with every kind of PIT file as well to no avail. However, one in particular worked for me and others. It is usually referred to as a full ROM. It contains the .csc and .sbl in it as well as the usual ROM contents.
The ROM I used is called FULL-i9000UGJH2.tar. Note, flashing this ROM with a pit file (be it 512, 513, or 803) wouldn't help me at all. What fixed the problem was flashing ONLY the ROM file in ODIN. Unfortunately, I can't find the thread where I found this ROM. I suggest searching around for it, if you can't find it PM me, and I will up it somewhere for you.
I'm not sure if this will help with your specific case, but its worth a shot. Also, wherever applicable, do a factory reset, clear your cache, and a full wipe install.
Good luck.
[edit]
Do a complete wipe and install with a stock 2.2 or 2.1 ROM in ODIN, there will be no evidence of a root.

Kops said:
In doing your research, I'm sure you've heard of the internal SD problems that plague the i9000, are you by chance with Bell Mobility? This line concerns me..
"Oh, I should also add another major issue, I cannot use the internal memory for anything"
When I experienced multiple FCs (force closes) and incompatible system UID's, I tried flashing every kind of ROM there was with every kind of PIT file as well to no avail. However, one in particular worked for me and others. It is usually referred to as a full ROM. It contains the .csc and .sbl in it as well as the usual ROM contents.
The ROM I used is called FULL-i9000UGJH2.tar. Note, flashing this ROM with a pit file (be it 512, 513, or 803) wouldn't help me at all. What fixed the problem was flashing ONLY the ROM file in ODIN. Unfortunately, I can't find the thread where I found this ROM. I suggest searching around for it, if you can't find it PM me, and I will up it somewhere for you.
I'm not sure if this will help with your specific case, but its worth a shot. Also, wherever applicable, do a factory reset, clear your cache, and a full wipe install.
Good luck.
[edit]
Do a complete wipe and install with a stock 2.2 or 2.1 ROM in ODIN, there will be no evidence of a root.
Click to expand...
Click to collapse
Thanks for this dude, I will start my search for that rom.
I do a factory reset, wipe cache and data every time, however after doing all of that and flashing a new rom, it still has my google account details in the phone?? this is wierd, as I factory reset from recovery mode AND wipe all data from within the phone? Any suggestions?
Edit: and no, its is an Australian Telstra i9000

glennr said:
Thanks for this dude, I will start my search for that rom.
I do a factory reset, wipe cache and data every time, however after doing all of that and flashing a new rom, it still has my google account details in the phone?? this is wierd, as I factory reset from recovery mode AND wipe all data from within the phone? Any suggestions?
Edit: and no, its is an Australian Telstra i9000
Click to expand...
Click to collapse
Hmm, that is odd. How are you flashing your ROMs, using CWM? Have you used ODIN before?

Kops said:
Hmm, that is odd. How are you flashing your ROMs, using CWM? Have you used ODIN before?
Click to expand...
Click to collapse
I am using odin, this is the wierd part. I have tried repartitioning, not repartitioning, I have tried 512.pt 803.pit, full wipe and reset from both in the phones settings and recovery mode. reboot it, go through settup wizzard (which eventually force closes requiring me to reboot), go into accounts and there is my google account still set up???
Edit: also, I cannot find a file called FULL-i9000UGJH2.tar, I am downloading i9000UGJH2.tar as we speak, but i doubt it is the one you were reffering to, if you are able to point in in the right direction, that would be ace.
Cheers

glennr said:
I am using odin, this is the wierd part. I have tried repartitioning, not repartitioning, I have tried 512.pt 803.pit, full wipe and reset from both in the phones settings and recovery mode. reboot it, go through settup wizzard (which eventually force closes requiring me to reboot), go into accounts and there is my google account still set up???
Click to expand...
Click to collapse
If you're entering your gmail address in during the setup wizard, our google account will be linked. If you're not setting anything up and it is remembering your info, then something is definitely fishy.
I would flash back to a stock rom, and see what Samsung or your provider can do for you. In all honesty, the only thing I would be able to suggest is flashing and wiping
[edit]
When you download that ROM, open it up (using a program like WinRAR). The point of a full rom is that it contains
-cache.rfs
-dbdata.rfc
-factoryfs.rfs
-modem.bin
-param.lfs
-sbl.bin
-zimage
I'm unsure of any incompatibilities between the Canadian and Australian versions, but I will upload my copy for you to try.

Kops said:
If you're entering your gmail address in during the setup wizard, our google account will be linked. If you're not setting anything up and it is remembering your info, then something is definitely fishy.
I would flash back to a stock rom, and see what Samsung or your provider can do for you. In all honesty, the only thing I would be able to suggest is flashing and wiping
Click to expand...
Click to collapse
I'm not entering any info during the setup wizard?
could it be something to do with the file system gingerbread uses? these issues only started when I went back from gingerbread to froyo? (and before you ask, I have tried going back to gingerbread with no solution)
I may have to bite the bullet and shoot it back to Samsung... or just buy another one! would love to try FULL-i9000UGJH2.tar if you could remember where you got it?
Thanks again for your help.
Cheers,

glennr said:
I'm not entering any info during the setup wizard?
could it be something to do with the file system gingerbread uses? these issues only started when I went back from gingerbread to froyo? (and before you ask, I have tried going back to gingerbread with no solution)
I may have to bite the bullet and shoot it back to Samsung... or just buy another one! would love to try FULL-i9000UGJH2.tar if you could remember where you got it?
Thanks again for your help.
Cheers,
Click to expand...
Click to collapse
I seem to have remembered it being in this thread, which is why i had it on bookmark, but I'm not sure if the link has been removed or if i had been mistaken since I can no longer find it. I'm uploading for you to Rapidshare, where you can download as a free user...~30 mins . Again, I'm not sure if there are modem incompatibilities or not since this I am in Canada, and you are in Australia.
Another place to check may be here...
http://forum.xda-developers.com/showthread.php?t=846913

Kops said:
If you're entering your gmail address in during the setup wizard, our google account will be linked. If you're not setting anything up and it is remembering your info, then something is definitely fishy.
I would flash back to a stock rom, and see what Samsung or your provider can do for you. In all honesty, the only thing I would be able to suggest is flashing and wiping
[edit]
When you download that ROM, open it up (using a program like WinRAR). The point of a full rom is that it contains
-cache.rfs
-dbdata.rfc
-factoryfs.rfs
-modem.bin
-param.lfs
-sbl.bin
-zimage
I'm unsure of any incompatibilities between the Canadian and Australian versions, but I will upload my copy for you to try.
Click to expand...
Click to collapse
Mate that would be great, I am not too fussed about compatibility at this stage, just want to get access to the internal sd again, then I can flash one of the many working froyo roms I have.
Cheers bud.

glennr said:
Mate that would be great, I am not too fussed about compatibility at this stage, just want to get access to the internal sd again, then I can flash one of the many working froyo roms I have.
Cheers bud.
Click to expand...
Click to collapse
The way you're referring to accessing this internal SD....are you flashing your ROMs to an external microsd card?
Here is the full UGJH2 that I flashed (with no other options) that saved me.
http://rapidshare.com/files/456841681/FULL-I9000UGJH2.tar
Give it a shot.

Kops said:
The way you're referring to accessing this internal SD....are you flashing your ROMs to an external microsd card?
Here is the full UGJH2 that I flashed (with no other options) that saved me.
http://rapidshare.com/files/456841681/FULL-I9000UGJH2.tar
Give it a shot.
Click to expand...
Click to collapse
No, by accessing my SD, i mean being able to download ansd install apps (and things like that). also, just tried to remove my google (gmail) account from my phone, and it wouldn't let me, it keeps force closing.
Thanks for the upload mate, I really appreciate it, currently downloading it, will let you know.
Cheers again.

Kops said:
The way you're referring to accessing this internal SD....are you flashing your ROMs to an external microsd card?
Here is the full UGJH2 that I flashed (with no other options) that saved me.
http://rapidshare.com/files/456841681/FULL-I9000UGJH2.tar
Give it a shot.
Click to expand...
Click to collapse
Hey mate, no go, i got some functionality back on the phone, but still force closes and I cannot save anything to SD (or install apps).
another email account (an exchange server account) that was previously deleted has appeared back set up and working (I have not been able to set this up for a week), it appeared on its own which leads me to think there is a hidden partition on my internal sd, hence I cannot access it. must be something to do with Gingerbread.
Thanks for all your help though.

glennr said:
Hey mate, no go, i got some functionality back on the phone, but still force closes and I cannot save anything to SD (or install apps).
another email account (an exchange server account) that was previously deleted has appeared back set up and working (I have not been able to set this up for a week), it appeared on its own which leads me to think there is a hidden partition on my internal sd, hence I cannot access it. must be something to do with Gingerbread.
Thanks for all your help though.
Click to expand...
Click to collapse
Edit: It just completely crashed again, force closes just about everything that is open, phone functionality is gone (phone icon vanished) as did contacts. freezes for a couple of minutes and then reboots. i may have to throw it at a wall!
I cannot find anything about the gingerbread partition that would cause problems with froyo. damn this thing!!!

Have you tried reformatting your internal SD
Settings>SD card and phone storage>internal SD>Format

http://forum.xda-developers.com/showthread.php?t=845708
You might find it useful.

SCIENTYREAL said:
Have you tried reformatting your internal SD
Settings>SD card and phone storage>internal SD>Format
Click to expand...
Click to collapse
Hi mate,
I have tried that several times, i think there is a hidden partition thanks to Gingerbread.

I would be sure that your internal sd card is screwed but since everything worked fine before gingerbread something else has probably happened. Also your data wont delete and that seems to be the source of the problem. Try to install the lagfix from k13d and see if it had any results. This should reformat all partitions on the internal sd.

[Q] Galaxy t679 root issues; Dire need of help/advice

Okay, so.. Excuse me in advance if I'm in the wrong section of the forums, because this is the only Exhibit section I can find.. And also excuse me for the length of this post, as my problem is a bit detailed.
Long story short, I had issues with my texts not being received. I tried wiping the phone and re-rooting (using root-stock found on this website - I can link if need be?).. Anyway, I went so far as to do a factory data wipe, which clearly wasn't a very good idea (I'm a bit new at this root business)..
Anyway, I ended up to the point where I'd reach the Android Setup Wizard, and start to go through it and it would crash.. Upon reboot, the phone would completely freeze at the second "SAMSUNG" logo (the white lettering). After this, I tried using odin to just flash the stock ROM to the phone via the PC, but neither the PC nor odin actually "see" the phone. (I have the drivers, but PC reads the phone as "USB Hub" for some reason) I moved on to other things...
I used bluetooth to put cwm and root-stock back onto the internal memory after removing my external SD card, and flashed cwm no problem. Everything was going well, and it even said it installed the root-stock (I did a data wipe beforehand).. Upon reboot, I now reach "Samsung Galaxy Exhibit 4G" logo, and it continually reboots in a loop. I can still access recovery mode, but I don't want to proceed any further without some outside input, considering I don't fully understand what's going on.
I'm aware that the phone seems to be "soft-bricked," because before I flashed cwm and root-stock, it was "working" in terms of being able to receive calls (and make them, after opening the contacts from inside a call), as well as send and receive texts via the notification bar. But the weirdest thing is, before I went the route of re-flashing the root/cwm, it wouldn't show me a homescreen of any kind, I couldn't use my menu button, and my home button was pointless to touch because it went nowhere. It was just a black screen (not a background, but completely black void) with a statusbar at the top.
Anyway, I'm currently stuck in a boot-loop and I'm very curious if there's any way I can fix this phone without using odin, because the phone isn't recognized by it or a PC, so I'm stuck using the device itself to do things. I'm VERY hopeful that someone takes the time to read this and offer any input they can, because I'm currently without a device and I have no means of getting another phone at the moment.
Thanks in advance for reading this, and for any input that you guys have to offer. Hopefully some day I'm not so noobish at this >.<

Ok, I know you've said you wiped but try this then reboot. In CWM wipe data/cache and under advanced wipe dalvik. Also if you have a working CWM you can flash rooted community ROM or flash to stock found here http://forum.xda-developers.com/showthread.php?t=1686384 scroll down till you see them. But wipe 3x don't know why some people need to but try it.
Note: a working cwm can flash any custom ROM with root pre-installed and you should be fine if you wipe the three I mentioned 3x format system under mounts and storage and format internal sd works wonders too.
Sent from my SGH-T679 using xda app-developers app
---------- Post added at 05:54 PM ---------- Previous post was at 05:53 PM ----------
If you need more help feel free to send me a pm
Sent from my SGH-T679 using xda app-developers app

Dvarl said:
Note: a working cwm can flash any custom ROM with root pre-installed and you should be fine if you wipe the three I mentioned 3x format system under mounts and storage and format internal sd works wonders too.
Click to expand...
Click to collapse
If I do a format of system or internal SD, I won't lose the ROM or CWM off of the system storage? If I lose these, I have no way of putting them back on the phone because I was doing it via bluetooth and the phone doesn't boot in order to do that anymore - The same applies to using a different ROM, sadly >.<
Also, I've already wiped the dalvik and cache several times, because that was the only way I could make the phone boot into a mode I could access anything at all on previous to installing the root again. I haven't tried doing this again as of yet, but I will do so and report back.
Just some extra information, because it wouldn't allow me to do so (being new and having to wait):
When I rebooted after the format (to the original stock rom/recovery, and even from recovery) it gave an "invalid argument" for /preload, saying it was unable to be accessed. It also said it couldn't access tmb/csc/system.. I'm unsure what these actually are, but I'm under the impression they may be at the route of my problem. Will formatting repair or otherwise help with these items being unable to be accessed?

Formatting internal will get rid of ROM, but not recovery. You'll be fine if you wipe system and reboot (ed: need to install a rom before reboot).
Try putting your ROM.zip on your external before wiping internal by mounting USB storage and copy ROM to external, then wipe internal and install ROM.

Formatting system (twice) didn't help anything at all - Still gets stuck at Exhibit logo and reboots after about 30 seconds.
Same thing with wiping dalvik/cache, even after 4-5 wipes of each. Should I be rebooting recovery after each of these?
I can't mount usb storage to PC, because PC doesn't recognize the device when I plug it in afterward (or even before mounting). It hasn't recognized the device for quite some time, but it used to act as if it were plug & play when I purchased it, and even well into the time it was rooted. A few months back, I installed the drivers for it (found via Google and ultimately this website), which didn't help it recognize the device. It only recognizes the device when in the "MTP" mode, which allows me to access and transfer data without issues(and I can't do this without being able to access the phone to turn it on ). Otherwise, it says "USB Device Not Recognized - One of the USB devices attached to this computer has malfunctioned and Windows does not recognize it"
I already have the ROM on my PC, but without any means of transfer back to the phone, removing it from internal storage would mean I have no physical way of accessing any ROM in order to restore my phone to working order. I'm at a loss as far as this is concerned, because I have the drivers installed. I'm unsure whether the phone itself is damaged, but I hope this isn't the case and that there's a way to resolve this issue directly.
My biggest concern isn't really the PC not recognizing the device, apart from needing it if I remove the ROM. My main concern is getting the thing to actually boot beyond the logos.. But if I remove the ROM, how will I put it back when it doesn't load to be able to bluetooth anything, and the PC doesn't recognize what it is?
EDIT -
I just realized something... Mounting USB storage doesn't seem to matter as far as moving the ROM, because I can just move them around via the external SD using CWM to flash them - But this is assuming that CWM will remain on the phone after formatting internal SD. Will it stay? If so, I'm going to try rooted community ROM, because the root-stock gives me the impression that it does nothing but apply root. The thread states "otherwise no changes to your phone," which implies (to me) that it doesn't actually include anything the phone needs in order to operate - It only changes certain things to apply root access... Not sure if this is true or not, but it would help explain what the heck is going on.

OH MY GOD! YOU GUYS ARE AMAZING!!
Thank you SO, SO MUCH for helping me. My device is no longer a useless paperweight :good: :good: :good:
I wish I could click the "Thanks" button a thousand times!!
Just incase anyone else has this issue and is able to access notification bar, this is what I did from beginning to end, without all the nonsense between times:
1) Turn Bluetooth on
2) Transfer Clockworkmod via bluetooth to internal SD. ((Tip: Use a separate android device to do this, if PC isn't capable) If already installed skip to step 4)
3) Re-flashed Clockworkmod
4) Place Rooted Community ROM (found here) onto external SD and insert SD into device.
5) Boot device into Custom Recovery (CWM)
6) Wipe cache/dalvik (I did it 4-5 times, just to make sure it was clear)
7) Format system AND rom AND SDCard (internal ONLY - I did all 3 times just to be sure)
8) Flashed Rooted Community ROM from external SD card (it takes some time to install - It will say when completed)
9) Rebooted phone via Custom Recovery - When clicking this, be sure to select NO when it asks to fix the root. I clicked "YES" the first time and it DID NOT FIX THE PHONE. It got stuck in another boot-loop.
10) Initial boot took a bit longer than usual (which is normal), but afterwards, I no longer have a phone that's soft-bricked.
I just wanted to say THANK YOU GUYS VERY, VERY MUCH. You've saved my life by helping me sort through this! Very, very appreciative and I hope both of you have a wonderful day :good: :good:

Good to know. I think you may have lost PNP from a windows update by samsung. To get that back, uninstall those drivers and look for 1.3.2410 or here if interested.

Still the same issue. Device isn't recognized with normal MTP (just plugging into the USB), and it acts as if I haven't even plugged it in at all when trying to use "Mass Storage" from the Network settings in the phone.
I just direct installed the drivers from the exe. Am I doing something wrong?

Try another port, cable, or machine. It worked before, so it could be a driver or something physical.
ed: When you're booted into your rom, can you change storage connection to ums? cwm might be mass storage instead of mtp.
Also, are you able to receive texts now?

I'm able to do everything the device is supposed to do out of the box, aside from access MTP.
I only have the one PC, and all ports have pretty much the same reaction to the device. I don't have access to another cable, because I only have the one that came with the device.
Mounting USB Mass Storage through CWM gives the same result on the PC "Device Not Recognized" etc, etc.

Not even ten days later and I've had to re-flash the ROM. The device kept turning itself off and back on again, so I decided to just remove all the programs I'd installed, thinking something I installed was causing an issue. After doing so, the device kept crashing. Not a reboot of the device or anything of the sort. Literally everything would pop up saying " ----- has stopped responding" and ask to force close. Not really sure what could've caused that, considering I've only installed things that were on Google Play, but it gave me the impression that I had an app that wasn't working correctly with the ROM on the device.
I've brought it back to "vanilla" and I'm not going to bother installing anything at all on it for a while and see if the issue comes up again. Not sure if anyone else has had this problem before or not, but I figured I'd just give my two cents since I made this thread with intentions to figure out what was going on with my phone. If anyone has any insight as to why this may have happened it would be greatly appreciated so I can avoid it happening this time. I'll report back if the issue comes up again, or becomes persistent.
Thanks again for all of your help, and sorry if you've wasted your time reading this.
EDIT -
Device still reboots randomly, but I suspect it's a stuck power button. Is it possible that it just needs cleaning? Sometimes it reboots, sometimes it comes up with the option to power off after touching the power button to activate the touch screen, then upon pressing the back button, it reboots several seconds later as if I were holding the power the entire time.

Stuck in boot-loop help!!!
Carefully followed instructions, and carefully selected 2 .zip files for my t679 http://click.xda-developers.com/api...4G - xda-developers&txt=<b>root-stock.zip</b> and http://forum.xda-developers.com/showpost.php?p=26860509&postcount=4 installed cwm successfully, but after installation of root-stock.zip system reboot now stuck in "boot loop" now what?
- zCHEMDAWGz

Following this in its entirety means you've wiped your phone's system clean. You'll have to use something other than root-stock, because that specifically states that it changes nothing other than granting root access. Everything that was on the phone from the factory is what root-stock uses, apart from giving you root access for things like Superuser, firewalls, etc. In this case, none of the stock items are present.
I used Rooted Community ROM. It's pretty much the same as root-stock, but it has a few goodies (BootyCall, and I think Busy Box) included. There are several other roms you could use, so you're welcome to look around a bit instead of just going with that one, but using that one for now would give you a working phone again until you find another you may like more.

BobScramit said:
Following this in its entirety means you've wiped your phone's system clean. You'll have to use something other than root-stock, because that specifically states that it changes nothing other than granting root access. Everything that was on the phone from the factory is what root-stock uses, apart from giving you root access for things like Superuser, firewalls, etc. In this case, none of the stock items are present.
I used Rooted Community ROM. It's pretty much the same as root-stock, but it has a few goodies (BootyCall, and I think Busy Box) included. There are several other roms you could use, so you're welcome to look around a bit instead of just going with that one, but using that one for now would give you a working phone again until you find another you may like more.
Click to expand...
Click to collapse
good call, community rom resolved this issue... now the only item left is the original problem - wifi/bluetooth "error". most of the easy fixes have already been attempted, aside from determining definitively if hardware issue.

Was the error your reason for rooting? (or re-flashing a rom)?
Are you running the phone completely vanilla now? (no apps, no app updates, even of "stock" applications?) If not, you should try running it that way and testing the wifi and bluetooth prior to updating or installing things.
If it were something you installed that caused a software or hardware issue, it would've most likely been something you installed a day or two beforehand.(When it broke the first time.) If you suspect it was a specific app, stay away from it (or them) in the future.
Considering that you're running a newly flashed rom, it's a little odd that the bluetooth/WiFi unctionality would error, unless it were a hardware issue. The rom you're using shouldn't affect either of those negatively, even if the phone were bricked and you managed to repair it.

BobScramit said:
Was the error your reason for rooting? (or re-flashing a rom)?
Are you running the phone completely vanilla now? (no apps, no app updates, even of "stock" applications?) If not, you should try running it that way and testing the wifi and bluetooth prior to updating or installing things.
If it were something you installed that caused a software or hardware issue, it would've most likely been something you installed a day or two beforehand.(When it broke the first time.) If you suspect it was a specific app, stay away from it (or them) in the future.
Considering that you're running a newly flashed rom, it's a little odd that the bluetooth/WiFi unctionality would error, unless it were a hardware issue. The rom you're using shouldn't affect either of those negatively, even if the phone were bricked and you managed to repair it.
Click to expand...
Click to collapse
The WiFi error existed prior to my ownership. I have never got it to function at all, except for when I was first programming the access point names settings for new mobile network, and fiddling with the other settings in the area, it did show my LAN, allowed me to attempt connection then failed the process early stage. It seemed logical that a new system would alleviate any antagonistic action executed by any previous owner. The only certain detail was it had not been rooted. I have been told loading custom Rom is 2 birds deal, freshness and increased control. Also, based on the behavior of the device and pop-up error messages that indicate software failure makes it seem related to software hiccup. but just a hunch. Been wrong before, really don't want to tear down phone but am open to learning something new. Thanks
- zCHEMDAWGz

I truly have no idea why the software would have any issues that arose directly after installing the new rom.
The only thing I can really suggest is using cwm to wipe everything several times prior to re-flashing the rom again, but I'm guessing you already did that. On the off chance it were hardware related, it probably wouldn't actually give error messages, so I'm gonna retract that from this entirely as it's very unlikely.
If you haven't, wipe your internal memory, system, cache/dalvik. Just in case, be sure you remove your external SD so you can keep the rom on it. Also, while you're at it, remove everything else except the rom from the external SD in case something on it is causing the issue, then try to re-flash the rom.

BobScramit said:
I truly have no idea why the software would have any issues that arose directly after installing the new rom.
The only thing I can really suggest is using cwm to wipe everything several times prior to re-flashing the rom again, but I'm guessing you already did that. On the off chance it were hardware related, it probably wouldn't actually give error messages, so I'm gonna retract that from this entirely as it's very unlikely.
If you haven't, wipe your internal memory, system, cache/dalvik. Just in case, be sure you remove your external SD so you can keep the rom on it. Also, while you're at it, remove everything else except the rom from the external SD in case something on it is causing the issue, then try to re-flash the rom.
Click to expand...
Click to collapse
Followed instructions, still having same issue... also the problem was there before I flashed New rom. I'm stumped...

Well, it being there before flashing the rom is a start, but that doesn't really explain why the new rom wouldn't have fixed whatever the issue was. I'm assuming (because I honestly don't know) that bluetooth and wifi are both controlled through the same hardware, with different softwares running them on the device. If both of them are messed up and refuse to work even after a re-flash, chances are it's just dead.
Have you actually formatted system, cache, etc after wiping, prior to a new flash? I had to format mine several different times in order to stop the boot loops and crashing. It could be something that's stuck in the system, cache, etc that didn't go away with a simple wipe. Other than that, it very well could be a hardware issue.

If it is a latent issue maybe doing full wipes through adb is the next step. I remember reading some people had some issues with doing wipes through cwm. It might be worth a try at the very least.
Sent from my SGH-T679 using XDA Free mobile app

MI3 MMS problem (unable to send/receive with cellular data working)

Hi,
I was wondering if anyone has the same or similar problem as mine. I'm using an Mi3W (bought from China) and using it on T-Mobile network in California. Almost everything works fine (including cellular data) except MMS. I'm using my micro sim with an adapter.
A while back I was able to change the APN settings and send/receive mms with Go SMS Pro, but with me not using mms that much, either software update or phone reset lost that settings on my phone and until i realize it I can't seem to set the right APN again despite doing all the thing i remember and newly discover.
I have called customer support and research online and try (I think) everything I can. I haven't tested it with AT&T or another carrier, but since it worked before I'm a bit confused of what I should do. It's not that huge of a deal, considering Viber, whatsapp, and all the texting app out there now, but just bug me a tiny bit when I can't do such a normal function of a smartphone or having to occasionally ask that friend to resend the picture or that group to move to Viber so I can participate.
If anyone has any idea how to fix it or any suggestion I'd really appreciate it.
Thanks

I had similar issue, I had to use CWR and format both partitions and do a total wipe then do a fresh load, my theory is an update messes with the MMS somehow and it is carried over though other updates. I am on AT&T Wireless

marka2k said:
I had similar issue, I had to use CWR and format both partitions and do a total wipe then do a fresh load, my theory is an update messes with the MMS somehow and it is carried over though other updates. I am on AT&T Wireless
Click to expand...
Click to collapse
Thank you for your suggestion. What is CWR? I search google and the forum but haven't found something makes sense, did you mean CWM? I also didn't know about 2 partitions being in the phone until recently when I follow the CM11 development thread...feel pretty dumb lol. Just to make sure i understood you right you wipe the phone completely, erasing all the data and everything right? Thanks

CWM - Correct sorry about that.
download to internal storage the latest stable build, format both partitions under mounts and storage, wipe cache and wipe/factory reset (to make sure) then install and test.
dtrinh11 said:
Thank you for your suggestion. What is CWR? I search google and the forum but haven't found something makes sense, did you mean CWM? I also didn't know about 2 partitions being in the phone until recently when I follow the CM11 development thread...feel pretty dumb lol. Just to make sure i understood you right you wipe the phone completely, erasing all the data and everything right? Thanks
Click to expand...
Click to collapse

marka2k said:
CWM - Correct sorry about that.
download to internal storage the latest stable build, format both partitions under mounts and storage, wipe cache and wipe/factory reset (to make sure) then install and test.
Click to expand...
Click to collapse
Thank you marka, for the instruction, I'll get CWM installed and try that sometimes this week when i have time (still using stock recovery hehe).

I'm having the same exact issue, same phone model and carrier. I thought the newest weekly update would fix it, but apparently not. Did you manage to fix your problem after the full wipe dtrinh?

Something went horribly wrong with my Turbo!

So for some reason today, my phone restarted and now I can't call people or receive calls, if I do. My phone restarts. Also can't use Bluetooth or it also does the same and restarts what can cause this? My phone getting too hot and damaged the motherboard? When I installed a kernel it was corrupted? I really have no understanding what caused this. I had resurrection from on it. I updated it with a newer one and did a bootloop. So I put cyangemod on it and worked but noticed those huge issues. Thinking the ROM was corrupted I put rr back on it and had the exact same issues. Any help would mean everything to me

austtint said:
So for some reason today, my phone restarted and now I can't call people or receive calls, if I do. My phone restarts. Also can't use Bluetooth or it also does the same and restarts what can cause this? My phone getting too hot and damaged the motherboard? When I installed a kernel it was corrupted? I really have no understanding what caused this. I had resurrection from on it. I updated it with a newer one and did a bootloop. So I put cyangemod on it and worked but noticed those huge issues. Thinking the ROM was corrupted I put rr back on it and had the exact same issues. Any help would mean everything to me
Click to expand...
Click to collapse
Restore the stock rom using step 0 of this guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684. Once you confirm that your phone is fixed, re-flash whatever rom/setup you want.

TheSt33v said:
Restore the stock rom using step 0 of this guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684. Once you confirm that your phone is fixed, re-flash whatever rom/setup you want.
Click to expand...
Click to collapse
What he said. If you want to try and recover your data (DCIM folder, downloads, etc), edit out "%fastboot% erase userdata" from the .bat file. Chances are that if you had CM installed, the stock rom will be terribly buggy since the data partition won't be erased, but you can still connect to your PC and pull the files you want to save. Once you've recovered your files, you'll want to do a factory reset, which can be done using that command you edited out of the .bat file. If you'r on Mac OS or Linux, the commands are basically the same as what's in the .bat file, but the commands begin with ./fastboot. You'll need to have the fastboot executable in the same directory as where you've extracted the files from the xml.
Just a quick note, Moto has a notorious reputation of not playing nicely with CM. This is just my personal opinion, but after trying some of the non-stock options, I've settled firmly on the stock rom, as it seems to be the most stable. If you need tether, root, etc, you can flash TWRP after you've gotten the phone back up and running, and use TWRP to install root and flash my stock tether enabler patch.

austtint said:
So for some reason today, my phone restarted and now I can't call people or receive calls, if I do. My phone restarts. Also can't use Bluetooth or it also does the same and restarts what can cause this? My phone getting too hot and damaged the motherboard? When I installed a kernel it was corrupted? I really have no understanding what caused this. I had resurrection from on it. I updated it with a newer one and did a bootloop. So I put cyangemod on it and worked but noticed those huge issues. Thinking the ROM was corrupted I put rr back on it and had the exact same issues. Any help would mean everything to me
Click to expand...
Click to collapse
Have you tried to make a google caller as default caller app? Does your imei correct also?