Database Users

Updated post: Can't get my phone to work at all

I've got two main problems with my galaxy s.
1) Today at around 1pm I had to force close something (I don't even remember what it was. I had just woken up the phone and went to check my mail, so I assume Launcher pro or something). It kept prompting me to force close, so I just took out the battery and reboot it. The phone can no longer get passed the initial screen (before the S). I've tried to reset to factory defaults, and it still doesn't work. I assume I can re-flash (not home yet) - but I'm wondering what would cause this type of behavior. FYI - I've been running 2.2 JPH with Rombie's mod)
2) I get really bad reception. I constantly will have my phone go from no service to 3-4 bars while sitting in the same spot. I also have a problem in busy areas where I'll lose my connection completely (whereas other people with different phones seem to have no problem right beside me). Is there anything that could be causing these issues?
Side note: When I originally upgraded to 2.2 JPH I had efs issues for a while, and it took me a while to get it up and running. It's working now (phone and data) - I'm just worried there's some residual effects of a mildly corrupted efs or something.

Update...
Things have gotten worse and I really need some suggestions.
I've tried flashing about 5 different firmwares and I can't get the thing going.
The closest I've come is with the stock jh2 firmware. It boots and it goes to a black screen after the S logo. I know this has been brought up but I have not had success with solutions I've found in other threads. I've tried it with pit512 513 and 803. I've tried it with repartition checked and unchecked.
When I try a 2.2 rom (such as the latest jpk) and upon resetting in the recovery mode, I receive an SDCARD failed to mount error (although one time I also received a failed to load DBDATA error). It also won't let me format the sdcard in this screen as obviously it can't mount it.
The closest I've come to getting the sdcard working is on the jh2 firmware i can "load update.zip" from my firmware, and it seems to actually load - unfortunately that update.zip is completely useless (as it's just an unlocker update i believe) - and I can't change the update.zip as I can't access the sdcard.
Please help if you can!

I had the same problem. My phone was working fine and then it just turned off and froze. I resetted it a few times and it would go to the S logo and then the screen would go blank and the buttons would light up. Resetting it a few more times made it work once but then when i started it again the phone would go back to the same problem.
I tried a ton of rom on it and some worked (but my internal sd card wouldn't mount). The problem got progressively worse by it's self and my phone wouldn't even start now. I recently send it back to Bell to get it repaired and hopefully they don't ping me saying it was my fault for ****ing around, which I doubt they will find out at this point since the damn thing doesn't even turn on.
I researched this a fair bit (2 full nights) and found out that it had something to do with me flashing Jp3 and that set my internal sd card as read only somehow. It's a bug and if you google it a lot of people have had this problem but none had a working solution and everyone of them had to send it back for repair.
Edit: I am also Canadian with a bell phone.

If I end up sending it back to bell, will flashing back to something like JH2 help cover my tracks?
Any idea how long it takes? I can't really go without a phone for more than a couple days =/

fuffalo said:
If I end up sending it back to bell, will flashing back to something like JH2 help cover my tracks?
Any idea how long it takes? I can't really go without a phone for more than a couple days =/
Click to expand...
Click to collapse
Honestly, it is a very frustrating process. They quote you a 2 - 6 week window and do not give you any hard time table and to top that off they don't have any loaner phones that are smart phones. The loaners cost $25 and $250 down.
I had to go out and find one from a friend and even then they wouldn't let me use a CDMA phone since i had a HSPA+ data plan and it some how ****s with their system. The only way you can use a phone on their network is using a HSPA+ phone if you need data. Luckily a friend had a HTC magic that was unlocked so I am using that now.
You can try to load up the default rom that ships with it and then send it in for repair.

Is the default rom JH2?

I believe it is this one I9000UGJH2

Alright so I can adb in to my phone when it's in recovery mode.
Does this help at all? Can i try anything from here?

[Q] lost 3g and gps after recovery

I have a Verizon galaxy tab. During the installation of CWM, my tab was locked up.
I used the recovery image that was mad by Clockworkmod during the process to get back to where I had started. When doing so, I ended up with no gps or 3g functions. The airplane mode is always on, and cannot be turned off.
I have tried installing a stock rom for the US verizon tab, with the same result, no 3g or gps and airplane mode locked on.
I am not sure what got lost in the recovery, and have not been able to find a answer in any searches I have done.
Any help on getting these functions back would be appreciated.

Same issue with Sprint Tab
I had the same issue with my Sprint Tab after installing a basic "Relax and Sleep" app. I fought it for 5 days with the help of Samsung and Sprint. We master reset and data wiped. We tinkered with multiple settings under the secret codes. In the end, Sprint said that they don't cover or service the device. They refused to swap out the device or do anything. Samsung said that I had to send it to them to repair and they would return it in 5-10 business days.
After multiple phone calls, I sent an email to every corporate email address I could find at Sprint. If I hadn't bought my Tab at a Third party vendor (Radio Shack), Sprint was willing to let me out of my contract. In the end I had to settle for 2-3 weeks without my 35 day old toy and a one month credit.
If you find a solution or the root of this problem, I would love to know.

What do you see when you type *#1234# into the phone dialer?

No phone dialer on a verizon tab, so I can't enter that.
Still looking for help in understanding what turned my radio off and how I can get it back.

Some additional information.
I reflashed the stock rom again to my tab. After doing so, I proceeded to re-download some of the apps I had on prior to the flashing. One of these is Z4root. When I opened the app to root the tab, it said the tab was already rooted.
This makes me wonder, is there any area of the file system that is not getting touched when I flash the new rom to the tab? If so, is this where the problem I am having with the radio being off, located.
Any thoughts?

Strange N4 Issues

I've had the phone for a few months, only used it for 2 weeks then put it back in the box with plans to resell it. Dad needed a new phone for his job so i decided to give it to him and every day for the past week ive gotten at least one phone call from him with problems. He is extremely new to smart phones but I never had a single issue with this phone prior to giving it to him. For some reason he will receive text messages or voice mail and sees the notification icons up on the notification bar but when he goes to pull the bar down it does nothing. The only way to resolve this issue is to restart the phone then all of a sudden the pull-down starts to function as it should. The phone is completely stock out the box i didn't feel the need to touch anything or have to root it for any reason.
He had to go to AT&T to get a sim card for it and the people there basically wanted to run him out of the store and not even touch the phone because they do not sell it so not a single person wanted to even help him out even though he just dropped more money into their pockets by upgrading his plan to a smart phone plan. before i gave him the phone all i did was a factory reset to wipe out any of my data on the phone so it was clean and like new for him.
Im at a loss because the whole time i used the phone i had no issues and since the day he got it he has had nothing but problems. I chalked this up to user error but its not because when he gave it to me to see if i could figure out why things were acting weird the only thing i could think to do was restart the phone. Does anyone have any suggestions as to why this may be happening and/or how to go about fixing it and not making him regret ever having to get a smart phone much less this N4?

New paragraph!
What messaging apps are you using? You could always download the toolkit and flash the stock factory image again.

I would try another factory reset just to make sure things didn't go haywire during the reset you already did. I have had a bad reset with a phone before.
Sent from my Nexus 4 using Tapatalk 4 Beta

yeah im gonna have to get with my dad and fool with the phone more. Its hard to troubleshoot something when he lives 45mins away and calls me with problems while im at work.
ONCE AGAIN the whole phone is stock so that would lead me to believe that the stock messaging app is being used. I will talk him through doing a reset again and see how that works out for him. From what he told me the only app hes even installed outside of everything that comes on the phone was Map Quest, which i told him he shouldn't need because Google Maps is already loaded on. So first im going to have him uninstall that from the phone as well as from his downloaded apps list in the play store and see if that changes anything.

[Q] Sleep of Death 2 days in a row :(

First of all, hi to everyone, i am new to the forum.
So i am a new owner of a Nexus 4, i have it for about 2 weeks. It's rev11, came with 4.2.2 out of the box, and it is completely stock and not rooted.
I didn't have any crashes or anything weird to indicate something is wrong with the phone in this time. And 2 days ago, i woke up at 12 instead of 9 i had my alarm, and the phone was not responding to unlock the screen and wake up. After some time pressing the power button it rebooted. So i though something temporary. I searched it here and is something known, sleep of death. I was not charging the phone btw. So i went my day using it again normally, and the next afternoon, i again try to unlock it to check something and see the time and again the same thing. Holding power button turned it on again after some tries. I didn't have to connect charger to reboot it as in some other cases i read, nor my battery percentage was any different or abnormal after the reboot.
But 2 days in a row can't be coincidence. The last app i installed before i noticed it is battery widget reborn.
So my question is, what is causing it? An app bug? I can restore to factory settings and it will stop? An OS bug? So we have to wait for android 4.3 for possible fix? Or a hardware issue? Because if it is hardware, i think i can still send the phone back and get a replacement, but this will leave me without a phone for 2 weeks maybe
Any help on this? From a little search on the forum most of cases seems to be an issue with apps undervolting the cpu while on standby or custom roms and custom kernels, but i am completely stock, and no app is doing anything to my cpu, i haven't enable something like that, and possibly without root even if i wanted it would not be possible.

Had this happen when I bought my phone back in January. It started happening probably mid-Feb and I probed through a ton of the internet and these forums for answers. The only thing I was left with was to call Google customer service and return the phone and replace it with a new one. So far, 2 months and never a SoD.
Provided you grabbed this from the Play Store:
Google customer service was very understanding and set me up with a code to buy a new phone off the Play Store and place the hold on my account. That new phone came in 3 days and I packaged up the old phone and sent it back with the labels Google provided and my account hold was removed in 4 days. They email you all the documents and UPS labels - you just do the rest. Most hassle-free return I have had and I deal with NewEgg RMTs quite often and I thought they were great...
and for reference: http://forum.xda-developers.com/showthread.php?t=2077148

Fusion.Coil said:
Had this happen when I bought my phone back in January. It started happening probably mid-Feb and I probed through a ton of the internet and these forums for answers. The only thing I was left with was to call Google customer service and return the phone and replace it with a new one. So far, 2 months and never a SoD.
Provided you grabbed this from the Play Store:
Google customer service was very understanding and set me up with a code to buy a new phone off the Play Store and place the hold on my account. That new phone came in 3 days and I packaged up the old phone and sent it back with the labels Google provided and my account hold was removed in 4 days. They email you all the documents and UPS labels - you just do the rest. Most hassle-free return I have had and I deal with NewEgg RMTs quite often and I thought they were great...
and for reference: http://forum.xda-developers.com/showthread.php?t=2077148
Click to expand...
Click to collapse
I bought from amazon uk, through a marketplace seller, but brand new. So they can't instantly ship a replacment since it is not officially sold from amazon, but it was fullfiled from amazon, so i can get a refund but i have to send it back and then re-order. This is quite the hassle. But on the thread you posted, i read multiple people saying that even the second or third phone they got back from RMA from Google still does that. So maybe is a software issue instead of hardware? Any other ideas to try before i go through the return and refund route?
Will a factory reset help in any way?
Or if i unlock bootloader, reflash the stock image, is it possible that this will fix anything? I mean is it possible to have a corrupted install of 4.2.2 on my device?

Hagaspar said:
I bought from amazon uk, through a marketplace seller, but brand new. So they can't instantly ship a replacment since it is not officially sold from amazon, but it was fullfiled from amazon, so i can get a refund but i have to send it back and then re-order. This is quite the hassle. But on the thread you posted, i read multiple people saying that even the second or third phone they got back from RMA from Google still does that. So maybe is a software issue instead of hardware? Any other ideas to try before i go through the return and refund route?
Will a factory reset help in any way?
Or if i unlock bootloader, reflash the stock image, is it possible that this will fix anything? I mean is it possible to have a corrupted install of 4.2.2 on my device?
Click to expand...
Click to collapse
As stated in the other thread, turn off WiFi. If you get a replacement, chances are you will still have the problem. A new thread didn't need to be started for this. You should have posted in the thread referenced.

How i fixed the Nexus 4 SODs
Same issue here with my Nexus 4. When connected to Wifi, with Android 4.3, every two days (more or less) it suffers a SOD.
And this is how I solved it: First, turn Google Play Store auto updates off. Second, install the 'Wake My Android Pro' app from the Play Store and set it to 4 minutes, Auto StartUp and Low Wake (and remember to use the 'back' button to save the preferences). No SODs for a week!

[Q] Verzion 900V probelm

I purchased a S5 G 900V (Verizon) on the 15th (of May) after my last phone died (Razr)... 2 months after the insurance expired of course. The S5 seemed to work fine for the first 3 days and like most I was setting it all up (w/exception of a few root only apps since the verzion phone is locked up).
This last Tuesday late afternoon the phone wouldn't turn on so I did a battery pull and when it booted up it had an unlocked icon (lock that was unlocked) display on the device and the word "custom" displayed under the open lock. The phone would go to sleep and not wake up without a battery pull each time. Device status under the settings area was also the word "custom". I had purchased the device from Best Buy along with insurance at our local mall... and at 7 pm after trying to get the phone to work correctly took it back to the store. The person that had sold me the phone was there along with one of the managers/assistant managers and they both keep telling me it was my own fault for attempting to root the phone (which I didn't do). They fought with the phone for and hour or so and couldn't get anything to work correctly... still getting the unlocked icon and custom word. I was told that if I could get it unrooted they would exchange the device for me, but they couldn't do anything with the phone until I could get it back into ua unrooted status. The assist manager did point me out to another website that explained the use of ODIN and where to get the stock Verizon rom.. which took a good few hours to d/l due to their slow server (not complaining, I'm glad they had it for me to begin with).
I set up and attempted to unroot the device with no avail. Did a factory wipe clean out cache etc etc the ODIN program kept saying it worked and I would be presented with all the normal new phone settings and hoops to jump thru as if it was just being activated... but on a restart the open lock and custom was still there.
Yesterday while looking over forums I noticed the phone was downloading an app I had already downloaded. I looked at the phone and it seemed as if it was re-installing some of the basic play store apps I had! I rebooted the phone and no lock appeared and under the Device status custom was gone and "original" was in it's place. I packed all my boxes and cables up and after work today took the phone in and had them exchange it for a new one. The same assistant manager was there when I had first taken the phone in when I had experienced the strange behavior.
She (the assistant manager), had no problem exchanging it since it didn't have that error showing up.
My major concern is if somehow if/when I connected the phone to my desktop did it (either the phone or computer) try and transfer files that made the phone act up in the first place? I have a rooted Nexus 7 and the Razr I had had ... had also been rooted. I don't think I have anything besides Samsungs device manager and Wugs Nexus Root toolkit, but those shouldn't mess the S5 up I have Eclipse installed but it doesn't launch without manual opening. I would both hate it if I had the same thing happen to this new phone but also dislike the idea of not plugging the phone in to transfer media if I wanted to.
Any ideas... or think it was a bad first phone?