Develop Bugs

Can't connect to Sprint service

I was running CM10 yesterday and decided to flash on screen nav buttons after i had updated to the latest CM10 nightly build, everything was working fine. I created a nandroid backup before flashing the buttons and decided the buttons werent for me a few minutes after flashing so i restored back. The restore was probably corrupt or something cause i had a lot of my settings there still but many of my apps were gone and it felt wrong so i flashed CM10 after wiping everything, clean flash.
That's when the problems started... I couldn't get any cell service and logged into sprint.com to see if i could maybe reactivate it there but the site was under maintenance last night. Today I woke up and tried to activate it but failed. Flashed CM10 a few times still no signal, flashed back to stock using this http://forum.xda-developers.com/showthread.php?t=1737859 and still no signal. When i apply the OTA update and the phone restarts com.android.phone has stopped keeps looping.
Any ideas or should i reset the binary counter and take it into the Sprint store?

hvuong said:
I was running CM10 yesterday and decided to flash on screen nav buttons after i had updated to the latest CM10 nightly build, everything was working fine. I created a nandroid backup before flashing the buttons and decided the buttons werent for me a few minutes after flashing so i restored back. The restore was probably corrupt or something cause i had a lot of my settings there still but many of my apps were gone and it felt wrong so i flashed CM10 after wiping everything, clean flash.
That's when the problems started... I couldn't get any cell service and logged into sprint.com to see if i could maybe reactivate it there but the site was under maintenance last night. Today I woke up and tried to activate it but failed. Flashed CM10 a few times still no signal, flashed back to stock using this http://forum.xda-developers.com/showthread.php?t=1737859 and still no signal. When i apply the OTA update and the phone restarts com.android.phone has stopped keeps looping.
Any ideas or should i reset the binary counter and take it into the Sprint store?
Click to expand...
Click to collapse
Flash back to stock in Odin preferably. And do ##72786# in the dialer. No need to take the ota's. Just grab the newest modem from the forums here. Especially on an aosp based Rom.taking the full ota is pointless

Please make sure to update us...

billard412 said:
Flash back to stock in Odin preferably. And do ##72786# in the dialer. No need to take the ota's. Just grab the newest modem from the forums here. Especially on an aosp based Rom.taking the full ota is pointless
Click to expand...
Click to collapse
Don't mean to hijack the thread, but do you or anyone else know of any negative effects using this code? I've been working on my MIUI port for a while and this often happens to me (no signal, can't send sms etc)
Flashing back to a TW Rom and using the code has always worked, but idk if there's anything bad about using this like 3-4 times a week
Sent from my SPH-L710 using Tapatalk 2

billard412 said:
Flash back to stock in Odin preferably. And do ##72786# in the dialer. No need to take the ota's. Just grab the newest modem from the forums here. Especially on an aosp based Rom.taking the full ota is pointless
Click to expand...
Click to collapse
After I flash stock with Odin everything is fine, except for the cell service. Whenever the phone restarts by me or OTA update i get the com.android.phone has stopped loop. After typing your code in the dialer the phone restarted after flashing a screen, couldnt catch what it said. after the phone booted it started the com.android.phone loop again... I think ill just take it to sprint tonight before they close unless you guys have any other ideas

hvuong said:
After I flash stock with Odin everything is fine, except for the cell service. Whenever the phone restarts by me or OTA update i get the com.android.phone has stopped loop. After typing your code in the dialer the phone restarted after flashing a screen, couldnt catch what it said. after the phone booted it started the com.android.phone loop again... I think ill just take it to sprint tonight before they close unless you guys have any other ideas
Click to expand...
Click to collapse
Wipe everything before the Odin flash including /system and immediately after wipe data/factory reset before it boots.
---------- Post added at 02:28 AM ---------- Previous post was at 02:26 AM ----------
fergie716 said:
Don't mean to hijack the thread, but do you or anyone else know of any negative effects using this code? I've been working on my MIUI port for a while and this often happens to me (no signal, can't send sms etc)
Flashing back to a TW Rom and using the code has always worked, but idk if there's anything bad about using this like 3-4 times a week
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Don't think so I do it often too. Don't think it hurts anything tho

billard412 said:
Wipe everything before the Odin flash including /system and immediately after wipe data/factory reset before it boots.
---------- Post added at 02:28 AM ---------- Previous post was at 02:26 AM ----------
Don't think so I do it often too. Don't think it hurts anything tho
Click to expand...
Click to collapse
Thanks.. I've been Googling it and found some stuff on the Sprint forums the other day. I'll enter it when my 3G seems to lag a bit lol. Always provides a boost
Sent from my SPH-L710 using Tapatalk 2

I got it repaired at the Sprint store. They replaced the board after flashing didnt work for them either. It was probably the radio he said

ya cuz he dont no u ****ed wit it. i bet he didnt no wat he was doing and the sprint store wasnt necessary. my $.02

[Q] What is wrong with my Gnex?

Hey the Problem is the following:
3-5 random reboots every day
restarts during every phonecall after 1-3 Minutes
freezes when in standby, cant turn back on -> need to take battery out
often slow, especially when switching apps. or when typing
I have tried stock 4.3, CM10.2 recently and before that CM10.1 for a while.
I already send it in but they only said my battery is broken.
Is it possible that all my problems come from this?
I rather think my flash memory is broken? What you think?

JonnyZaggi said:
Hey the Problem is the following:
3-5 random reboots every day
restarts during every phonecall after 1-3 Minutes
freezes when in standby, cant turn back on -> need to take battery out
often slow, especially when switching apps. or when typing
I have tried stock 4.3, CM10.2 recently and before that CM10.1 for a while.
I already send it in but they only said my battery is broken.
Is it possible that all my problems come from this?
I rather think my flash memory is broken? What you think?
Click to expand...
Click to collapse
Since yesterday I am facing the same problems you are describing. At first I thought it was a bad flash or something like that. Clean installed various 4.3 costum roms and it's always the same.
Right now I will look deeper into it since the phone is unusable in that condition.
If I find a solution I will comment.
Best regards
Edit: Okay, works again flawlessly. I simply flashed an nightly from carbon-rom and the lags were gone. Hope it helps. What exactly caused the lag I don't know. For now I am staying on 4.2.2 Carbon as it is my favourite rom anyway and I will wait till there are stable 4.3 from carbon.

Are you sure it's the phone and not an app?

chrisinsocalif said:
Are you sure it's the phone and not an app?
Click to expand...
Click to collapse
Not pretty sure, but it still occured after countless factory resets, wipe cache, wipe dalvic cache and wipe system via TWRP.

Have you tried a clean install without installing apps to see if you get a reboot to eliminate an app as a possible cause?
Sent from my Nexus 7 using Tapatalk 4

chrisinsocalif said:
Have you tried a clean install without installing apps to see if you get a reboot to eliminate an app as a possible cause?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Yes I did. I only flashed for example newest PA and their PA Gapps.
So far I resolved it by "downgrading" to a 4.2.2 nightly from carbon. The lags are completly gone. I will stay and wait till carbon has stable 4.3.

why dont people try stock when they are having problems? going from 1 custom rom to the next does not prove it is the phone.
please fastboot flash the stock rom and do not restore any apps/data other than say your google acct

Zepius said:
why dont people try stock when they are having problems? going from 1 custom rom to the next does not prove it is the phone.
please fastboot flash the stock rom and do not restore any apps/data other than say your google acct
Click to expand...
Click to collapse
Already did that.

I am having the same/similar problems with my GNex too. Specifically bullets [1-3] from the original post. I am running unmodified yakjuux and have tried with just my google account with no other apps and the same problem exists.
Mine makes a noticeable "click" sound with a vibration followed by a reboot.
It usually happens during calls and after it boots the phone call log shows no record of the incoming/outgoing call that just happened. Its like a blue screen of death for android!
I have sent the phone back to Samsung's warranty service 4 separate times and each time they reported no trouble found in the completion report. They just factory reset or put an older version of jelly bean back on the phone and send it back to me with some notes of PRL updates and other nonsense to make it seem like they did something to fix it.
Does anyone have any suggestions (logs, adb, etc) how I can help prove to Samsung/service absolute that the phone is a lemon (other than trying to video tape the phone hoping it reboots - because that is the last resort)?
I already escalated to executive customer service and they refused an exchange because the completion reports show no trouble found :crying:
Thx!

well... I also have this problem.
First happened when I flash Cm10.2 nightly (don't remember which one).
Then I flash PA, or whatever... Looks like the random reboot relating to notifications? It's usually happened when whatsapp notification coming in, but not always.
But a few weeks ago I flashed stock ROM rooted (via TWRP, not fastboot).
The problems solved. No random reboots anymore. Then today I tried latest CM10.2, and it happened again... Wonder why... Looks like it's a very rare problems.
Interesting to see someone having the same problem...
Now I want to flash stock ROM via fastboot to check if it'll fix.
Btw, I can flash directly to CM 10.2 from 10.1, can't I? Or I should flash 4.3 via fastboot first?

lonestrider said:
Btw, I can flash directly to CM 10.2 from 10.1, can't I? Or I should flash 4.3 via fastboot first?
Click to expand...
Click to collapse
I believe CM offers an upgrade option somewhere in the system settings. Unless you want to wipe your phone and flash directly to 10.2 in which case I do not think you need to flash stock 4.3 first. Maybe just do a reset within 10.1 before you flash CM10.2 via whatever recovery (clockwork etc) you are using but even that may be unnecessary.
My 1 year warranty expires this month so if I can't manage to get something out of Samsung I am going to play around with flashing stock 4.3 as you suggested. I have tried converting yakjuux to yakju in the past but still saw the problem then which made me revert back to yakjuux so I could send the phone back for service).

[Q] Boot problems after two reboots

Hi there! I´ve got some issues with my gnex lately: I clean installed PA 3.99. Every went well for a couple of Days, including turning on and turning off the phone.The one strange thing happend. I installed an app, baammm, first reboot. Hm. Phone came up quickly, then baamm, second reboot. From then things went downhill... Stuck at Google-Logo. Had to pull Battery. Factory reset.
Now, everytime I boot the phone it is stuck at the Google-Logo. I have to install the ROM again and then it boots up. One time. I flashed the latest bootloader, which did not help.
Any ideas?

ive got this problem as well. probably worse.
ive got the latest nightly of carbon installed.
however once i reboot it is stuck at the google logo!!!!
im not sure if i need the latest bootloader or if im missing soemthing!
i came from a 4.2.2 rom .

astarman said:
ive got this problem as well. probably worse.
ive got the latest nightly of carbon installed.
however once i reboot it is stuck at the google logo!!!!
im not sure if i need the latest bootloader or if im missing soemthing!
i came from a 4.2.2 rom .
Click to expand...
Click to collapse
Yeah, pretty bad. At the weekend maybe I'll try to flash stock factory image. Hope that helps. But I've seen some things here at the forum. I'm slightly scared...
Sent from my Galaxy Nexus using xda app-developers app

[Q] Stuck on bootloader after changing screen density with Rom Toolbox

Hey guys. As the title suggests, I can't boot my Note 2 (sgh-i317). It is stuck on the AT&T logo and while it's stuck there it vibrates slightly every 5-6 seconds. I tried changing my screen density to 240 and it worked for a bit but annoed me. then I went to change it back and got this problem. I accidentally set it to 360 I think though, instead of 320. I have wiped the cache. I have wiped the data. I have installed roms countless times already with Odin. I'd imagine my reset counter is at over 10 just from today.
I've been searching on google and these forums for hours and have seen many suggestions, but none of them have worked. The farthest I have gotten was to get the phone to boot, but once I start going through all the setup stuff I begin getting error popups saying that Touchwiz home has stopped responding. As soon as I push OK the error immediately pops up again. I seriously can not do anything with my phone.
Is there any way to get a stock build.prop file somewhere for this phone, and if so, how would I install it if I can't even boot into the device?
Any help would greatly be appreciated. I have no idea where else to turn here. Thanks!
-Mark

Do you have a backup to restore from recovery ??
If not....then power down the device and remove the SD card and place it into a PC card adapter...
Then download or copy over a suitable rom...
Then place the SD into the phone and boot into recovery...
Fully wipe the device and flash the rom of choice...
Reboot....set....profit....g
Edit:
Are you certain that your power button is not stuck ?
If the method I suggested fails... and rebooting occurs with vibration...then your power button is suspect....g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

Thanks. Well I got it to boot finally, however there's been a couple issues since. It's on 4.1.2 right now...
1. Whenever I try to officially update to 4.3 through the settings, it downloads, then when installing it ALWAYS fails at 25%.
2. This is a big issue. My data connectivity is gone. I have no 4g access period. If I'm not using a wifi network, I can't do anything online, period. I've reflashed numerous times, and can't get it to recognize the network. I can make calls just fine, just no data.
I've tried wiping data and going to factory reset, but this doesn't help in any way whatsoever. I've popped out the battery and sim card and reinserted after a few minutes, still to no avail.
The funny thing also, last night my friend, who has the same phone, updated to 4.3 and got the EXACT issues I've been dealing with. The ONLY thing in common is that we have both rooted our phones in the past. When I first got 4.3 it worked fine. It wasn't until I rooted that these issues began. My friend's phone was not rooted, however it had been in the past. I'm thinking that this 4.3 update has an issue with phones that are rooted or have been at some time. I don't know how it can tell, but that's all I can think of. his phone now is also a doorstop, like mine.

K, fixed data connectivity from another thread here. For some reason, even if I wipe my system, it seems to still keep settings intact. In this case, nothing set in APN. Seems the more I try to fix my phone, the more problems show up.

If you updated to official 4.3...then yes ...a whole new host of problems are yours until the devs figure out the locked bootloader and it's knox flag...
Backups won't restore....and so forth...
Read around ....you'll see...g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

[Q] note 10.1 2014 bootloop

Ok I am REALLY frustrated. Yesterday my note was working fine and I shut it off like normal. Then the next day, when I went to turn it on, it kept saying the samsung logo over and over again. It then goes to the lockscreen and immediatly boots back to the sammy screen. Another weird thing is that it takes FOREVER to boot to the lockscreen before rebooting again. If i pull the pen out or touch the screen during that time, it vibrates like it should be on the lockscreen.Sometimes, the samsung logo will flicker and rotate sideways for a half a second and go back. Ive tried restoring my backups but it didnt fix it. Sometimes, it wont reboot and will work so idk what the problem is. I didn't do anything that would make it bootloop like this. Ive tried reflashing stock kernel and ive restored the boot but nothing. Im running cleanrom 1.2. Is that maybe a bug in the rom? I know I should probably update to the newest version but I havent felt like it. I REALLY need some guidance here. Thanks

I'm still unrooted on my p605 and I've had this happen as well, without the logo flicker and rotate. It righted itself after 5 - 10 loops all way to lock screen.
Sent from my SM-P605 using Tapatalk

hexbox117 said:
Ok I am REALLY frustrated. Yesterday my note was working fine and I shut it off like normal. Then the next day, when I went to turn it on, it kept saying the samsung logo over and over again. It then goes to the lockscreen and immediatly boots back to the sammy screen. Another weird thing is that it takes FOREVER to boot to the lockscreen before rebooting again. If i pull the pen out or touch the screen during that time, it vibrates like it should be on the lockscreen.Sometimes, the samsung logo will flicker and rotate sideways for a half a second and go back. Ive tried restoring my backups but it didnt fix it. Sometimes, it wont reboot and will work so idk what the problem is. I didn't do anything that would make it bootloop like this. Ive tried reflashing stock kernel and ive restored the boot but nothing. Im running cleanrom 1.2. Is that maybe a bug in the rom? I know I should probably update to the newest version but I havent felt like it. I REALLY need some guidance here. Thanks
Click to expand...
Click to collapse
I think you should just start over and do fresh install of CleanROM . the 2.0 one. With my experience I usually make a backup with twrp before I do anything for situations like your in. If you had a twrp backup you can just restore that and you would be good to go. I've learned to take a few extra minutes to make a twrp backup. Sometimes stuff just goes wrong. You can always flash stock firmware with Odin, then do a fresh install of CleanROM 2.0.If you search around forum you can find stock firmware.
That's just my opinion.

I have multiple back ups but when I restored them it still did it. I ended up factory resetting then using titanium to get my stuff back and it works like normal now.
Sent from my SM-P600 using XDA Premium HD app

I had the same issue running stock and twrp. I used odin to install the latest version of twrp - from there I loaded a user-compiled kernel - cleared the cache and it worked.

That didn't work for me sadly. But factory reset did so I'm good now
Sent from my SM-P600 using XDA Premium HD app

Still unrooted, did a factory reset, restored by Samsung account & Google account, still bootlooping. Seems to be taking longer to break out of it. Anyone got any ideas or solutions?
Sent from my GT-N7105 using Tapatalk

Contemplating the 4th factory reset in 2 days, as bootlooping has become never ending. It stops for a while with a factory reset, but by the time I've downloaded everything again it's back. It use to stop eventually but not any more. Does anyone know a way to stop this or at least what's causing it?
Sent from my GT-N7105 using Tapatalk

I had the same issue. To solve it, I went into the advanced Wi-Fi settings and unchecked "Always Allow Scanning". I have not had a boot loop since then.
Sent from my SM-P600 using Tapatalk

casimi said:
I had the same issue. To solve it, I went into the advanced Wi-Fi settings and unchecked "Always Allow Scanning". I have not had a boot loop since then.
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
Thanks Casimi, that worked perfectly. Just wish I had known about this 4 days ago, before I started doing factory resets. Anyway all fixed now. Again many thanks for the help.
Sent from my SM-P605 using Tapatalk

You're welcome. I don't know why Samsung still hasn't issued a fix for this. Had the same issue with my Note 3 as well.
Sent from my SM-P600 using Tapatalk

i have the same issue
hey guys !
i have the same issue on my note sm-p605 , I bought it about a week ago and didn't back up anything.
it started boot looping suddenly and i tried to enter the recovery mode but i couldn't .
p.s: my device is not rooted and am not that professional in these things.
kindly help me !

Thank You
Thank You so much I wasn't sure what I was going to do with my tablet. It's just to expensive to go out and buy another one. You are a life saver.
casimi said:
I had the same issue. To solve it, I went into the advanced Wi-Fi settings and unchecked "Always Allow Scanning". I have not had a boot loop since then.
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse

Eyadoo13 said:
hey guys !
i have the same issue on my note sm-p605 , I bought it about a week ago and didn't back up anything.
it started boot looping suddenly and i tried to enter the recovery mode but i couldn't .
p.s: my device is not rooted and am not that professional in these things.
kindly help me !
Click to expand...
Click to collapse
I had the same problem with my SM-P605. I took out the MicroSD card and the Note booted up. Now the wifi "Scanning always available" is also unchecked.
Did a reboot and it was fine.
I hope it lasts.