I recently received a new X821 (Probably one of these fake / misrepresented phones).
I opened it up, charged it, stuck the sim card in and tested it out. Made a couple of phone calls, tested the wifi. Everything seemed to be working great. The one thing I didn't test is Bluetooth. I installed TWRP, wiped the phone and flashed AOSP Extended. The next day, when I went to pair the phone with my head unit in my car Bluetooth wouldn't turn on. I hit the toggle for Bluetooth, and nothing happens.
Since then, I've tried just about every stock image I can find. I flashed each of the firmwares listed here in the NitrogenOS thread. No change. Bluetooth won't turn on. Right now, I've got it reverted back to stock with the Indian 19S rom and recovery, and still no change.
Before I start the rather lengthy RMA process, has anyone seen this, and is there any fix for it? My google-fu has turned up one other thread, and it has no responses.
[EDIT]Here's a quick video of me trying to turn Bluetooth on
I've now also tried the unbrick method here. Still no go on Bluetooth.
If this phone is actually an X829, like the "fake" thread linked above states, is there a different ROM for the X829? Would that help me with Bluetooth?
Related
a month ago i bought a brand new Sprint TP. And i was amazed by its GPS, it's the fastest mobile phone GPS i ever met. it only need 5 second to lock satellite. but yesterday suddenly it stopped working. with identical rom and identical radio. it's so weird. i try it to flash back to factory default and yet it still didn't worked. try also to update the radio but no hope. Do anyone have a solution for these weird problem?
are you using the stock rom & radio? you say you tried flashing radios but to no avail, which part failed? you were able to flash a new radio but it didn't solve the problem or you weren't able to flash a new radio period? we need a lot more information to help you
vince_wonk said:
a month ago i bought a brand new Sprint TP. And i was amazed by its GPS, it's the fastest mobile phone GPS i ever met. it only need 5 second to lock satellite. but yesterday suddenly it stopped working. with identical rom and identical radio. it's so weird. i try it to flash back to factory default and yet it still didn't worked. try also to update the radio but no hope. Do anyone have a solution for these weird problem?
Click to expand...
Click to collapse
If you have already reflashed the rom, it could be that you have a damaged unit in your hands. If I were you, I would relock it and run to a Sprint store asking for a replacement. Just my two cents...
Good luck!
[SOLVED] here are the solution:
hello friends, recently after i upgrade my Sprint TP ROM into several different type of ROM, my TP GPS can't lock and view the satellite anymore. i got frustrated and hopeless about it. i already tried almost every single method until i find these one:
http://www.smartphonejunkie.com/gps-still-cant-t183417.html?t=183417
so i matched the IP between QPST and the IP server and port number on HKLM/Software/HTC/SUPL AGPS. After i match both of it, suddenly it start working again and the result is superior. i can lock 8 satellite even indoor on my private room. when i got outdoor it only need around 3-5 seconds to lock. so it even faster than before that need around 20-30 second with QuickGPS. sorry for my bad english, i just want to share a GPS problem that actually very tricky and have various problem.
Note: i never changed any settings on my QPST and i set the SUPLAGPS to follow my QPST value.
it's interesting that each time i changed the ROM, it also changed the IP and Port inside that registry.
hope this tricks helps. thank you
I just had that happened too...
If the above suggestioon does not work, I had applied this fix which worked for me when my GPS suddenly stopped working for no reason. My stoped working just a day before yours did. This of course happed just as I REALLY needed my GPS to work.
Here is the Fix.
Using a registry editor .....
HKLM/Comm/ConnMgr/Providers/{7C4B7A38-5FF7-4bc1-80F6-5DA7870BB1AA}/Connections/Phone as Modem
Change the value AlwaysOn=1 to AlwaysOn=0
Soft Reset..
Worked for me.
If I helped send a thanks.
I'm a total newbie so please bear with me. I have a problem where whenever I reboot or after several hours I will have no service and won't be able to connect to my network operator. I have searched around and tried various things to try fix this but the only solution I've found is only temporary which is to put my SIM card into my old phone and then place it back into my GS2 which will give me a signal for several hours before it drops again.
I'm thinking it's probably a hardware problem but I wanted to see what you guys have to say.
Thanks,
I actually have a problem that sounds like it. When I leave my phone charging a long time and reboot it with the charger connected, it doesn't have service; the same happens when i turn it off and leave it charging, then (whithout disconnecting the charger) I turn it on.
Isn't it your case?
Are you running a custom rom? It could be your modem.
I was initially on CM9 and flashed Resurrection remix to see if that was the problem. I also tried flashing a new modem but I'm still getting the same problem but this was only recently and I've read that I should wait for a few days to see how well the modem works? Also since then, I haven't seen the error while running only, after I've reboot.
I've flashed a few modems and the problem still persists.
So I'm having a strange issue. I've already checked multiple threads, here and on other forums, most notably this one: http://forums.androidcentral.com/samsung-galaxy-note-2/263592-note-2-wont-charge.html
I read every post and no one has my exact issue. So here's the story:
I smashed my screen to bits on concrete, but I have the insurance so Asurion sent me another one. I'm not certain it's refurbished but It did not come in the same packaging my original one from the VZW store did so I'd say it probably is.
I made a backup of my rom using TWRP (Clean Rom VZW Edition - JB 4.1.1)
Then I got my new phone out and checked it and it was running the vramc3 version, so i tried to root/unlock/install recovery via the NoYou exploit. This failed due to driver issues, then after that was sorted out, failed again due to a partitioning issue. ("error: partition 60 blah blah...") So I tried to odin back to stock without realizing the newest firmware had to be flashed using the alternate stock rom for unlocked bootloaders (even though mine was not unlocked) so i flashed that and it worked, i was on the original stock firmware again. however the older version of the exploit for the stock firmware did not work (i'm assuming because the bootloader wasn't actually rolled back even though the firmware was) so i downloaded the ota updates and got back to vramc3 and tried the NoYou exploit again and it worked, so i had root, recovery, and an unlocked bootloader.
Because my old phone and new phone have different serial numbers, I modified the folder name and .log file entries of the TWRP backup of the old serial number to be the new phone serial number. This worked and my phone was restored. For 3 days it charged just fine, and then last night and all throughout today, I've been testing it after noticing it doesn't charge when connected to an a/c outlet, and does not recognize a connection to my pc..... SOMETIMES. Sometimes it works right away, other times it takes 10 minutes of being plugged in before it recognizes it. and other times it'll sit for an hour and never figure it out. All without me moving it around too, i really don't see how it could be a cable connection issue. I tried my old phone on the old and new samsung official a/c charges and both work flawlessly every time, so i'm certain the cables are good.
So i did some more testing. I tried doing a factory reset with the rom still installed. Still had charging issues. I tried wiping everything except my external sd card and installing the latest version of the rom which is based on the vramc3 update (fresh install, not using my backup), still doesn't always charge...
I didn't yank the cable out, drop the phone, or mishandle it in anyway in the past 3 days, and the leads for the usb connection on the phone don't appear to be damaged. I also tried moving the cable around the connection while plugged in to see if something wasn't making contact and it didn't make a difference. I also now have 2 batteries, both hold a charge perfectly fine, and charge perfectly fin in the old phone so I don't think it's related to them either, and I have tried the new phone with both batteries. So here's the question....
Is this a firmware issue, or a usb port issue? I still have the old phone and if it's a usb port issue i'll just swap it with the old one, but i'd prefer not to take it apart until someone more qualified to speak on the matter tells me that it's the problem, haha.
And if it's a firmware issue, what the hell do i do? since I have recovery operational, i was going to try a few other roms just to see if anything changes while i'm waiting for replies.
Pleeease help, as you can probably tell by the length of this post, this is driving me insane.
TallgeeseIV said:
So I'm having a strange issue. I've already checked multiple threads, here and on other forums, most notably this one: http://forums.androidcentral.com/samsung-galaxy-note-2/263592-note-2-wont-charge.html
I read every post and no one has my exact issue. So here's the story:
I smashed my screen to bits on concrete, but I have the insurance so Asurion sent me another one. I'm not certain it's refurbished but It did not come in the same packaging my original one from the VZW store did so I'd say it probably is.
I made a backup of my rom using TWRP (Clean Rom VZW Edition - JB 4.1.1)
Then I got my new phone out and checked it and it was running the vramc3 version, so i tried to root/unlock/install recovery via the NoYou exploit. This failed due to driver issues, then after that was sorted out, failed again due to a partitioning issue. ("error: partition 60 blah blah...") So I tried to odin back to stock without realizing the newest firmware had to be flashed using the alternate stock rom for unlocked bootloaders (even though mine was not unlocked) so i flashed that and it worked, i was on the original stock firmware again. however the older version of the exploit for the stock firmware did not work (i'm assuming because the bootloader wasn't actually rolled back even though the firmware was) so i downloaded the ota updates and got back to vramc3 and tried the NoYou exploit again and it worked, so i had root, recovery, and an unlocked bootloader.
Because my old phone and new phone have different serial numbers, I modified the folder name and .log file entries of the TWRP backup of the old serial number to be the new phone serial number. This worked and my phone was restored. For 3 days it charged just fine, and then last night and all throughout today, I've been testing it after noticing it doesn't charge when connected to an a/c outlet, and does not recognize a connection to my pc..... SOMETIMES. Sometimes it works right away, other times it takes 10 minutes of being plugged in before it recognizes it. and other times it'll sit for an hour and never figure it out. All without me moving it around too, i really don't see how it could be a cable connection issue. I tried my old phone on the old and new samsung official a/c charges and both work flawlessly every time, so i'm certain the cables are good.
So i did some more testing. I tried doing a factory reset with the rom still installed. Still had charging issues. I tried wiping everything except my external sd card and installing the latest version of the rom which is based on the vramc3 update (fresh install, not using my backup), still doesn't always charge...
I didn't yank the cable out, drop the phone, or mishandle it in anyway in the past 3 days, and the leads for the usb connection on the phone don't appear to be damaged. I also tried moving the cable around the connection while plugged in to see if something wasn't making contact and it didn't make a difference. I also now have 2 batteries, both hold a charge perfectly fine, and charge perfectly fin in the old phone so I don't think it's related to them either, and I have tried the new phone with both batteries. So here's the question....
Is this a firmware issue, or a usb port issue? I still have the old phone and if it's a usb port issue i'll just swap it with the old one, but i'd prefer not to take it apart until someone more qualified to speak on the matter tells me that it's the problem, haha.
And if it's a firmware issue, what the hell do i do? since I have recovery operational, i was going to try a few other roms just to see if anything changes while i'm waiting for replies.
Pleeease help, as you can probably tell by the length of this post, this is driving me insane.
Click to expand...
Click to collapse
This topic can be closed now. I looked up a video (http://www.youtube.com/watch?v=FfvOTFssDMM) of the swapping process and saw how easy it is, so i just went ahead and tried it, and it totally worked, so now it's charging fine again. Thank you to anyone who viewed this and hopefully this can help someone in the future.
I didn't read all of that. I was at a concert last night. But here what I know about the not charging thing.
In my experience
1.all the good galaxy phones do it.
2. Its not that it wasn't charging. Its that vzw turned the power up on the modems. If your in a low service or weak signal area your phone will actually drain the batter faster then you can charge it.
So if you notice this is happening. Switch your phone into airplane mode. Or turn off mobile data and let it charge for a while.
I have read about a few case's where the usb ports where disconnected. But I think the crazy fast radio battery drain is way more common.
I don't know if its the same for other carriers but I know a note guy a s4 guy and 2 other note 2 guys we all had the same problem with it.we are all Verizon too.
The original modem flash helps a lot but the 2nd one that went out ota is stronger in weak signal areas so we all use it and turn off our data if it gets to much.
Hello,
I'm somewhat new to the rooting world of Android but when I got my Note 2 last year the first thing I did was root it and unlock the bootloader, and kept that through the 4.1.2 (if I recall correctly) update. I knew I wasn't getting 4.2 and jumping straight to 4.3 as was Verizon's plan. I waited patiently and forgot about it entirely, so a couple of days ago I found the stock rooted deodex rom located here. I thought I had made the correct decision, it seemed to be for my phone, it flashed with no issues (both the rom and firmware) and runs fine except for one flaw which has proven to be a pain due to it cancelling my alarm every morning.
Whenever the lock screen comes up, the phone things a touch happens right in the middle of the screen. Nothing's there, but it doesn't matter what happens, I push the power button, plug its charger into it, it will always send out that one little ripple and as a result it cancels my alarm. I looked through the thread, I appear to be the only one with this issue.
Any recommendations?
Wow no wonder Ive been late to work all week. Phones doing the same thing.
Sent from my SCH-I605 using Tapatalk
As an update from my fiddling about this morning, it seems to only happen when the lock screen is set to the Swipe method. If set to a pattern, pin, anything else, this error doesn't occur. A temporary workaround at best, as this no longer allows me to access multiple lock screen widgets.
Wow man.. since my last post I wiped and am running a new rom, kernel, everything.. still doing it ?
Sent from my SCH-I605 using Tapatalk
I believe I've narrowed it down to a few possibilities, between it being the new ripple/ink effects on the lock screen or something to do with the multiple widgets. I can't believe we're the only ones dealing with this. Does anyone have any insight if even a complete reset, rom flash and kernel swap hasn't fixed it?
As another update, I appear to have been mistaken. While delayed slightly, the end result is no matter what, the alarm eventually silences itself after a few seconds, unknown why.
I had the same thing happen using n3bula (4.3) rom. Alarm would turn itself off. Didn't really have time to mess with it so I went back to beans 22 (4.1.2). If you figure anything out, let us know
Sent From My Sticky Note, Too?
As another update from yet more fiddling. I tested it this morning as it would normally be, hooked up to my computer charging, with my bluetooth headset on but also sitting on its charger. The alarm cut out even with pin set as the lock screen. When removed from the cable connecting it my computer and my headset on my ear, it didn't. Going to test further.
So, as yet another update, I believe I found the problem, a reply from prior posters experiencing the same thing would be helpful to see if it was the same issue. I have one of the original sony android smartwatches that connects through Bluetooth. On a hunch, I disabled Bluetooth on my phone before going to bed a few nights and wouldn't you know it, no problems. Did it again with the watch off and just the headset connected, again, no issues. Seems the watch is a bit too dated or butts heads with the MJ9 firmware driving the Bluetooth module.
So as to follow up. In my situation specifically, my music player is Poweramp and I noticed whenever my headset is connected and my alarm is going, it immediately tries to take over and start playing music, I think that's what caused my alarm to go silent. My headset is the Plantronics Voyager Legend, my smartwatch is the original Sony Smartwatch, I don't know if the combination of the three are relevant to the others in this thread having the problem.
Also. It appears to happen on 4.3 regardless. I've gone back after a clean wipe and used the stock 4.3 Samsung Verizon OTA rom, n3bula, and jelly beans and all of them produced the same problem when bluetooth was enabled with my watch and headset connected and poweramp installed.
ForcePhenomenon said:
Also. It appears to happen on 4.3 regardless. I've gone back after a clean wipe and used the stock 4.3 Samsung Verizon OTA rom, n3bula, and jelly beans and all of them produced the same problem when bluetooth was enabled with my watch and headset connected and poweramp installed.
Click to expand...
Click to collapse
when you wipe do you also format internal sd?
MunkinDrunky said:
when you wipe do you also format internal sd?
Click to expand...
Click to collapse
Correct, thought I'd noted that when I said clean wipe. I wiped internal storage, cache, everything you should when flashing a new rom, going to the point of doing it multiple times and even dirty flashing a few times to see if that would fix the problem (as it did fix some issues going on with n3bula and they actually recommend doing it.) But, nothing of the sort happened.
Ok. I just can't belive that problem is persisting. Must be the radio? Did you say you flashed one of your backups, where any of them prior to the firmware update? That is if any have the radio backed up too. You could flash the zips for any of the older radios.
MunkinDrunky said:
Ok. I just can't belive that problem is persisting. Must be the radio? Did you say you flashed one of your backups, where any of them prior to the firmware update? That is if any have the radio backed up too. You could flash the zips for any of the older radios.
Click to expand...
Click to collapse
Why would it be the radio's fault. It has zero problems transmitting whatsoever, zero problems pairing, nothing. It just seems that as soon as any sound output comes from the phone, Poweramp immediately wants to kick on and start streaming music to my headset.
And no, I didn't flash one of my backups. Prior to all this when my Note was still 4.1.2 it had no problems. I suppose it 'could' be something with the MJ9 firmware but why would it only affect this certain circumstance?
ForcePhenomenon said:
Why would it be the radio's fault. It has zero problems transmitting whatsoever, zero problems pairing, nothing. It just seems that as soon as any sound output comes from the phone, Poweramp immediately wants to kick on and start streaming music to my headset.
And no, I didn't flash one of my backups. Prior to all this when my Note was still 4.1.2 it had no problems. I suppose it 'could' be something with the MJ9 firmware but why would it only affect this certain circumstance?
Click to expand...
Click to collapse
have no idea but since it was a variable in this situation I thought to try to rule it out for certain.
I've had this device since march, and have no idea what is happening. My WiFi suddenly stopped working, and I can't find any way to enable it again. In the about section, it can't find a MAC address at all. I don't know whether or not the NIC got disabled, or if I would need to buy a new mainboard. If I could somehow enable it again via ADB that would be awesome. I've been having this issue for a while, and just put it on the backburner due to life, and would like to start using this phone again.
For added info: I'm in the U.S.A. and bought it through WirelessPlace, so I have no warranty on the device. I haven't tried through Xiaomi support yet, but I highly doubt they would help much, and also I would probably have to ship the phone out, and I would like to not have to do that.
Do hard reset and flash stock..if still issue, it's hardware failure..
11 Lite 5G NE
Last week (after 8 months od usage) my Bluetooth stopped working
When I tapped to turn on, the button was endlessly showing Turning on, never coming to Turned on (and no BT device was able to find my phone)
Also, if I opened another app (or locked window) while endlessly showing Turning on, then BT immediately went to Turned off
Since I also decided to upgrade MIUI (and OTA was failing, saying there is no memory to install the downloaded OTA package), I flashed the full Fastboot ROM (with hard reset) and it also solved my BT - now BT works again