Related
We received our Samsung Galaxy II phones a few days ago.
My wife had a Swiftkey and Swiftkey X keyboard apps in her Amazon appstore account. She installed Swiftkey X, and she was presented with an "update" that showed Swiftkey (not the X; apparently this is an issue with Amazon appstore based on Swiftkey site). Thinking that it was an update to the Swiftkey X, she apparently applied it, and immediately there were number of FC notices (she remembers seeing TWLauncher among them) and a spontaneous reboot of the phone. Then, she couldn't get online either through WiFi or 4G. At that point she gave the phone to me to fix it
Comparing her phone side by side with mine it is very clear that there's an issue with network connectivity. While mine flies through the pages, market downloads, etc. either on WiFi or 4G, hers get stock for 3-5 seconds before opening pages or sometimes just displays a "webpage cannot be found" or "connection error".
I went ahead and did a factory restore, but that seems to only delete user account, personal files, etc. if I understand it correctly. Moreover, the issue is still there after the restore. So, is there a way to restore the system files to stock as well? Can it be done without rooting, or does it require loading a fresh ROM?
Sorry for the lengthy message and thanks in advance!
http://forum.xda-developers.com/showthread.php?p=27322
that's a full factory reset.
Sent from my SGH-T989 using Tapatalk
mikeyinid said:
http://forum.xda-developers.com/showthread.php?p=27322
that's a full factory reset.
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply. Could you double check the link? I get "No Thread specified. If you followed a valid link, please notify the administrator".
Thanks again!
tenderidol said:
Thanks for your reply. Could you double check the link? I get "No Thread specified. If you followed a valid link, please notify the administrator".
Thanks again!
Click to expand...
Click to collapse
if you look at the sticky threads at the top of this forum there is one called index by AllGamer. Its at the bottom of the first post. Make sure you grab the Tmobile one and not the telus one
Sent from my SGH-T989 using Tapatalk
Here: http://forum.xda-developers.com/showthread.php?t=1323878
Everything goes back to stock.
You need to either:
1. Root
2. Install CWM through ROM Manager
3. Flash this
Or:
1. ODIN flash CWM
2. Flash this
513263337 said:
Here: http://forum.xda-developers.com/showthread.php?t=1323878
Everything goes back to stock.
You need to either:
1. Root
2. Install CWM through ROM Manager
3. Flash this
Or:
1. ODIN flash CWM
2. Flash this
Click to expand...
Click to collapse
Dude. That's a half ass way, it doesn't take you to stock. First of all its deodexed.. Just a sec
This is the only proper way to go back to stock THIS IS IT RIGHT HERE
Sent from my SGH-T989 using Tapatalk
Thanks again for the replies. So, I'm going to have to root it and put a stock image back I gues... I was hoping that SII had a fail safe similar to Nook Color where you can easily go back to stock if something was not right.
tenderidol said:
Thanks again for the replies. So, I'm going to have to root it and put a stock image back I gues... I was hoping that SII had a fail safe similar to Nook Color where you can easily go back to stock if something was not right.
Click to expand...
Click to collapse
you dont have to root it to run the odin package
mikeyinid said:
you dont have to root it to run the odin package
Click to expand...
Click to collapse
Oh, sorry about that. I'm a newbie for the SII rooting/modding (did quite a bit with Nook Color), and I need to do some reading first.
Smart man!
Sent from my SGH-T989 using Tapatalk
voidthedroid said:
Smart man!
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Alright, I'm halfway through. The rooting process for the SII is little different than NC, but the principles are the same.
By the way, is it safe to assume that some conflict between SwiftKey and SwiftKey X caused the problem on her phone? The reason I ask is because I'd like to put SwiftKey X on my SII (it has multi-language support) and I dont want to deal with the same issue if it was the culprit.
I believe I did enough reading at this point
Since this doesn't involve rooting (now I understand it), I'd like to get an "OK" from the guru before proceeding with the following "as newbie as it gets" steps:
1. Install Odin (v1.85)
2. Install Kies for the recent GSII drivers
3. Make sure Windows recognizes the phone in ODIN (seeing <ID:0/004> Added!! in the message box)
4. Turn off the phone
5. Turn on the phone by holding both the Vol-up and Vol-down buttons and plug the USB cable in while still holding both buttons
6. Select volume up button to proceed to download mode
7. Start Odin
8. Check the PDA button in Odin and browse to “T989UVKID_HOME_SGH-T989user_CL594724_REV00.tar.md5” file
9. Click Start in Odin and let it flash
10. Once it completes and reboots…..
Is that it? At Step 10, it should boot into a 100% T-Mo stock, right? Just to be sure, I’ll perform a factory reset after that point and start all over with the user files, apps, etc.
Thanks in advance!
Sounds good. But if you look in the stickied threads top of this forum the drivers for our phone are posted. No need to install kies but that does work also
Sent from my SGH-T989 using Tapatalk
tenderidol said:
Thanks again for the replies. So, I'm going to have to root it and put a stock image back I gues... I was hoping that SII had a fail safe similar to Nook Color where you can easily go back to stock if something was not right.
Click to expand...
Click to collapse
The "factory reset" you used IS the fail safe. The parts that "factory reset" doesn't remove is the part that won't be messed up unless you are rooted. So I don't even know how you touched /system etc without rooting...
mikeyinid said:
Sounds good. But if you look in the stickied threads top of this forum the drivers for our phone are posted. No need to install kies but that does work also
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Thanks a lot!
Just finished flashing the stock image and everything worked as expected. This was also a good practice to learn how to restore it to stock in case something goes bad.
513263337 said:
The "factory reset" you used IS the fail safe. The parts that "factory reset" doesn't remove is the part that won't be messed up unless you are rooted. So I don't even know how you touched /system etc without rooting...
Click to expand...
Click to collapse
The issue was created after installing a 3rd party keyboard and -by accident- applying an update that was supposed to be for a slightly different version, which resulted in numerous force closes and random reboots immediately. I might be wrong here, but that indicates that more than just the user files were affected, since deleting just user files via factory reset didn't help the network problem. However, flashing the stock image -without rooting- took care of the problem.
Ok after hours and hours, I finally got my KF rooted and online. I have installed superuser with KFU....I also installed the gapps from KFU, that part didnt work. I downloaded from the play store gmail. I am trying to get it to sync.....I think I need the google services framwork or something like that. I want it to be able to sync to my gmail and my phone. I know it is possible...but there is so many different websites and whatnot, I was hoping someone could point me in the right direction
thanks
Heather
You'll need to install the gapps zip. Can you provide a bit more information regarding that part not working? Maybe a screenshot of KFU at it?
By the way, I strongly advise you to install FFF and TWRP.
Dasanko said:
You'll need to install the gapps zip. Can you provide a bit more information regarding that part not working? Maybe a screenshot of KFU at it?
By the way, I strongly advise you to install FFF and TWRP.
Click to expand...
Click to collapse
I dont know how to do a screen shot. I've got it up and running. I have it rooted and the market app installed. that all works. The wierd thing is that when I first rooted this months ago...as soon as the KF booted up, all of my apps from my phone were there. AWESOME! But now, I have done the same thing and nothing. All of my amazon apps are there, but thats it. my calendar was there with all the dates, so I guess that means it was able to sync. but the gmail does not sync automatically. I have googleservicesframework.apk on there, installed and changed permissions. do I need the calendarsync.apk?
I used KFU this morning to root and I think it automatically installed twrp, when I boot up the first KF logo is blue, at the bottom there is a boot up menu, then it boots into the orange/yellow KF logo and its good from there. Does that mean I do have twrp installed?
Honestly, I went out and bought an asus tablet because I coulnd't get my KF to do what I wanted it to.. I jsut want to be able to use it as a basic tablet, to sync my email and celandar and run the play store, thats it
Id rather keep the KF because of the size and cost But I'm just frustrated...thanks for letting me vent
Heather
putney1477 said:
I used KFU this morning to root and I think it automatically installed twrp, when I boot up the first KF logo is blue, at the bottom there is a boot up menu, then it boots into the orange/yellow KF logo and its good from there. Does that mean I do have twrp installed?
Click to expand...
Click to collapse
Alright, you do have FFF installed (it's the blue KF logo screen). When you start up the KF, you'll notice on the bottom it's asking you to press the power button for a boot menu. Do press the power button a few times until it shows -Recovery-, and see if it boots into TWRP then - from there, choose "Install" and then pick the gapps zip (download http://goo.im/gapps/gapps-ics-20120429-signed.zip and put it in your KF if you haven't yet. You can delete that zip after it's been installed). You may also want to wipe cache and dalvik-cache.
putney1477 said:
do I need the calendarsync.apk?
Click to expand...
Click to collapse
This I don't know for certain - however, installing the gapps zip as instructed above should have everything google related working properly.
putney1477 said:
The wierd thing is that when I first rooted this months ago...as soon as the KF booted up, all of my apps from my phone were there. AWESOME! But now, I have done the same thing and nothing. All of my amazon apps are there, but thats it.
Click to expand...
Click to collapse
The reason that stuff was gone is probably due to an amazon OTA (over the air) update. To prevent stuff like that in the future, if you have the heart, you may want to look into flashing a custom ROM.
putney1477 said:
I dont know how to do a screen shot.
Click to expand...
Click to collapse
Press the "print screen" (Prt Scr) key on your keyboard (usually, it's next to F12) - then fire up Paint and just paste (control v or choose the select tool and right click on the image, then paste). It's a good idea to save it as PNG for better quality, or JPG for an usually smaller size, then you can either attach it here or upload to an image host, such as imgur.com, and link to it here.
putney1477 said:
But I'm just frustrated...thanks for letting me vent
Click to expand...
Click to collapse
No problem, we've all been there.
As a side note, do not allow Play Store to update Kindle applications - they'll malfunction until you uninstall those updates.
EDIT: Forgot to mention, you may want to read this: http://forum.xda-developers.com/showthread.php?t=1552547
Thank you so much for taking the time to help me out.
How many times to I hit the power button to get into recovery? I see when I a supposed to press it to get into the boot menu but It just keeps going, the the logo turns yellow orange and boots normally
I would love to install a custom rom. What would you reccomend? Im running an ICS one on my phone. .. Im a little less worried about bricking this, as opposed to my htc phone that I need for work (and thats running a custom rom) Its just that there are so many ways to do things and so many differrent devices that are different in every way possible when it comes to installing custom things
I guess I should be more patient. I figured out the recovery and I have installed the gapps.
putney1477 said:
How many times to I hit the power button to get into recovery? I see when I a supposed to press it to get into the boot menu but It just keeps going, the the logo turns yellow orange and boots normally
Click to expand...
Click to collapse
A few times, it's hard to say, as it kinda sucks at acknowledging your presses. You'll notice the letters change to a few options, with the middle one saying --Recovery-- or something like that, then just let it sit there and it'll load into TWRP in a few seconds -if- TWRP is installed. You can also just press the power button multiple times until it shows that boot menu.
putney1477 said:
I would love to install a custom rom. What would you reccomend? Im running an ICS one on my phone. .. Im a little less worried about bricking this, as opposed to my htc phone that I need for work (and thats running a custom rom) Its just that there are so many ways to do things and so many differrent devices that are different in every way possible when it comes to installing custom things
Click to expand...
Click to collapse
Well, first is having your issues fixed. As for which to pick, is a delicate matter. You can pick between a stock based custom ROM, if you do like the stock rom look... and there are also CM7 (Android 2.3, gingerbread) and CM9 (Android 4.0, ICS). I'm currently using the sgt7 ICS ROM, but your mileage may vary - each ROM is usually fairly different, and what I like may not be what you like. Either way, you can freely "hop" around trying out different ROMs until you decide to stick with one that works best for you.
putney1477 said:
Thank you so much for taking the time to help me out.
Click to expand...
Click to collapse
No worries.
EDIT: Nevermind, guess you figured it out. Don't forget to read this, it may help you understand things better: http://forum.xda-developers.com/showthread.php?t=1552547
I've been using my Galaxy Nexus for a month or so, with the official JB ROM (JR30C or whatever, deodexed and rooted) and today I opened Gmail.
That's it. I opened GMail, switched accounts, and my phone has been bootlooping ever since.
I wiped everything in CWM multiple times and reflashed it, and I can't get the phone to do anything else.
Any clues?
Do you have a working nandroid? Have you tried flashing a different ROM?
Allons-y
Xfanatic said:
Do you have a working nandroid? Have you tried flashing a different ROM?
Allons-y
Click to expand...
Click to collapse
I do not have a working NANDROID. I wasn't sure about the Internet policies at work, but it looks like I can at least make it on here, I'm not sure I'll be able to download another ROM.
I'm confused though, I mean I know it would help to try as many options as possible (to fix it) - but this ROM has been working for weeks. And the phone died randomly, not due to a recent file change or a botched program. The only boot loops I've experienced before were on the Nexus One, and it was always due to a buggy/bad flash or a corrupted ROM download - this one just developed epilepsy on its own...
Here's my plan, since these are the only things I can manage to download due to restrictions on Internet usage at work.
Factory 4.1.1 takju image from here : https://developers.google.com/android/nexus/images#takju
Modified ODIN software here: http://forum.xda-developers.com/showthread.php?t=1586807
ODIN won't rewrite my bootloader, recovery, or userdata, since I already OEM unlocked, but will reflash a stock image.
EDIT: ODIN won't do anything with my device. Trying this ROM instead:
http://forum.xda-developers.com/showthread.php?t=1801664 was using bigxie OTA before.
is your (sd)storage recognized? thus is a similar symptom to when the stirage goes bad.
Hook the phone up to adb, boot it, and let logcat run. Maybe that will turn something up.
Sent from my Galaxy Nexus using Tapatalk 2
simms22 said:
is your (sd)storage recognized? thus is a similar symptom to when the stirage goes bad.
Click to expand...
Click to collapse
Hmm, you know, I'm not able to find the option to mount to USB in CWM...and just in case I forgot where that is, when I plug it in, I get the "hardware failed" noise from Windows and not the usual friendly "plug in" sound.
infazzdar said:
Hook the phone up to adb, boot it, and let logcat run. Maybe that will turn something up.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'm at work, and I only have my work computer. Group/secpolicy won't allow me to install anything, no admin rights, etc.
Would it even do anything? The phone barely makes it through one second of the boot animation before it loops.
sheik124 said:
Hmm, you know, I'm not able to find the option to mount to USB in CWM...and just in case I forgot where that is, when I plug it in, I get the "hardware failed" noise from Windows and not the usual friendly "plug in" sound.
Click to expand...
Click to collapse
you cant mount the sd card. there is no USB mass storage period. not in recovery or booted normally.
Zepius said:
you cant mount the sd card. there is no USB mass storage period. not in recovery or booted normally.
Click to expand...
Click to collapse
Oy. Then how do I get another ROM on here? fastboot/adb?
sheik124 said:
Oy. Then how do I get another ROM on here? fastboot/adb?
Click to expand...
Click to collapse
Adb push.
Sent from my Galaxy Nexus using Tapatalk 2
Zepius said:
you cant mount the sd card. there is no USB mass storage period. not in recovery or booted normally.
Click to expand...
Click to collapse
sheik124 said:
Oy. Then how do I get another ROM on here? fastboot/adb?
Click to expand...
Click to collapse
Got more than one additional ROM on there via adb/recovery - my clue that CWM hasn't actually been able to do anything since the phone start looping is I'm still getting my custom boot animation.
I'm using the toolkit to reflash a stock image now. What a mess.
Even reflashing a stock image via fastboot did nothing. WTF happened to my phone? Won't stay on long enough to get a logcat
I'm having the same problem as this guy:
http://forum.xda-developers.com/showthread.php?t=1827685&page=2
I just got finished trying to flash 4.1.1 using ODIN. It still shows me the custom animation from bigxie's ROM (which has supposedly since been overwritten 2-4x times).
Screw you Samsung...this phone is a month old, I flashed -once- to rooted Jelly Bean, and the phone dies when I open the GMail app.
EDIT: WTF - I write screw you Samsung, it boots to the Welcome screen! Just long enough for me to see that my files aren't on it anymore, then it bootloops again. And again. Now it's re-stuck in a bootloop.
And now I'm at the homescreen. I can't rely on this thing like this...is my flash dying or something?
Nobody?
It worked long enough for me to re-enter all of my different Google account information and now it's dead again. Now it only flashes the boot animation for a split second for bootlooping.
I'm thinking of a hardware defect.
Beamed from my Grouper
Mach3.2 said:
I'm thinking of a hardware defect.
Beamed from my Grouper
Click to expand...
Click to collapse
Mee too. As you can see from my signature, I gave up and bought a One S yesterday night from Craigslist. Feels like a true successor to the Desire / N1. It's nice to finally have an AMOLED screen that actually seems color calibrated after the ugly mess that was my RAZR and my less than perfect GNex. It's a damn shame how much more painless flashing a recovery was on this thing.
Sent from my HTC VLE_U using xda app-developers app
Hi,
I just got my Galaxy Nexus (European ver., 4.1.1) few days ago and it randomly crashes all the time, especially when using apps with calling function (eg. dialer, viber, walkie talkie app...etc). It works fine sometimes and it crash and reboot automatically sometimes....
I have tried to flash it to CM10 and CM9, but the problem is still there.
Does any body know what's the problem?
I have two nexus (one for my family), and they both have the same problem.....
sorry for n00bness, but how to do reset to factory settings with customs rom? i tried settings>> backup and restore>> factory restore, but it didn't work.
Thank you
secretiff said:
Hi,
I just got my Galaxy Nexus (European ver., 4.1.1) few days ago and it randomly crashes all the time, especially when using apps with calling function (eg. dialer, viber, walkie talkie app...etc). It works fine sometimes and it crash and reboot automatically sometimes....
I have tried to flash it to CM10 and CM9, but the problem is still there.
Does any body know what's the problem?
I have two nexus (one for my family), and they both have the same problem.....
sorry for n00bness, but how to do reset to factory settings with customs rom? i tried settings>> backup and restore>> factory restore, but it didn't work.
Thank you
Click to expand...
Click to collapse
Well, if you have a custom rom, you probably have a custom recovery such as TWRP or CWM (ClockWorkMod Recovery), reboot to recovery, and select wipe data/factory reset, yes, and you are done.
If you are having problems rebooting to recovery, just power off the phone, hold volume up + volume down + press power, press volume down until you see the word "Recovery" and then hit power.
Wiping from a custom recovery (ClockWorkMod or TWRP) will not wipe your internal SD (pictures,music) but it will wipe your apps/settings. Wiping from a stock recovery will wipe your pictures/music/everything in addition to your apps/settings.
EDIT: What I find funny is that your phone reboots and both of them. Flash stock google factory image and see if it reboots. If it does, probably its a faulty phone. It would be a great idea to lock the bootloader with stock rom and return the device.
akash3656 said:
Well, if you have a custom rom, you probably have a custom recovery such as TWRP or CWM (ClockWorkMod Recovery), reboot to recovery, and select wipe data/factory reset, yes, and you are done.
If you are having problems rebooting to recovery, just power off the phone, hold volume up + volume down + press power, press volume down until you see the word "Recovery" and then hit power.
Wiping from a custom recovery (ClockWorkMod or TWRP) will not wipe your internal SD (pictures,music) but it will wipe your apps/settings. Wiping from a stock recovery will wipe your pictures/music/everything in addition to your apps/settings.
EDIT: What I find funny is that your phone reboots and both of them. Flash stock google factory image and see if it reboots. If it does, probably its a faulty phone. It would be a great idea to lock the bootloader with stock rom and return the device.
Click to expand...
Click to collapse
yes, they both rebooted with google stock rom when i got them! so i thought maybe it was something do with comparability or bugs from the stock rom...so i flash them with CM10, not working. then i thought...maybe it's the jelly bean? so i flash CM9....and it still happens...
Thanks for your suggestion, reli appreciate that
secretiff said:
yes, they both rebooted with google stock rom when i got them! so i thought maybe it was something do with comparability or bugs from the stock rom...so i flash them with CM10, not working. then i thought...maybe it's the jelly bean? so i flash CM9....and it still happens...
Thanks for your suggestion, reli appreciate that
Click to expand...
Click to collapse
I've also heard, some phones don't like Jelly Bean. But you have issues with CM9 too, so its really weird. Only solution for them was to return the device. There are reports of people having difficulties with any Jelly Bean based ROM (even stock)
akash3656 said:
I've also heard, some phones don't like Jelly Bean. But you have issues with CM9 too, so its really weird. Only solution for them was to return the device. There are reports of people having difficulties with any Jelly Bean based ROM (even stock)
Click to expand...
Click to collapse
oh...really??? guess we are just the unlucky minors...everybody is so happy with their nexus
it really irritates me cause i like my nexus, but it just have its spontaneous psycho flicks
after rebooting, it doesn't work right away...if i use those calling apps right after it finishes reboot, it will reboot again :crying:
I have to wait for some moments for it to work.......
sure im gonna return it, and buy another one from other stores... *sighs*
secretiff said:
oh...really??? guess we are just the unlucky minors...everybody is so happy with their nexus
it really irritates me cause i like my nexus, but it just have its spontaneous psycho flicks
after rebooting, it doesn't work right away...if i use those calling apps right after it finishes reboot, it will reboot again :crying:
I have to wait for some moments for it to work.......
sure im gonna return it, and buy another one from other stores... *sighs*
Click to expand...
Click to collapse
Sorry to hear man. Looks like it is a faulty one. However, Viber if you don't know, doesn't work on Jelly Bean. If you don't mind waiting, maybe you should use a spare phone in the mean time and wait for the next Nexus. :good:
akash3656 said:
Sorry to hear man. Looks like it is a faulty one. However, Viber if you don't know, doesn't work on Jelly Bean. If you don't mind waiting, maybe you should use a spare phone in the mean time and wait for the next Nexus. :good:
Click to expand...
Click to collapse
I tried to go to my cwm recovery and chose wipe data/factory reset but it's still CM9...
I would like to flash back to the stock rom, unlockbootload and unroot it so i can return. is there any way to do that? there isn't many tutorials online....
(Im using mac.)
Thank You
secretiff said:
I tried to go to my cwm recovery and chose wipe data/factory reset but it's still CM9...
I would like to flash back to the stock rom, unlockbootload and unroot it so i can return. is there any way to do that? there isn't many tutorials online....
(Im using mac.)
Thank You
Click to expand...
Click to collapse
nvm, i have already done it with my frds pc!
Hi, there are thousands of people with the same problem, its not the rom(JB)... but the proximity sensor that crashes the kernel, during calls, make the phone freeze/reboot.Search in google groups issue 37485, there are no solution, google and samsumg, dont say a word...It happens in nexus s too.
I have the same problem
firestruck said:
Hi, there are thousands of people with the same problem, its not the rom(JB)... but the proximity sensor that crashes the kernel, during calls, make the phone freeze/reboot.Search in google groups issue 37485, there are no solution, google and samsumg, dont say a word...It happens in nexus s too.
Click to expand...
Click to collapse
What shall one do then? I have such behaviour as well i think where phone has difficulties to come back from deep sleep.
I had this problem too
Random crashes which got worse, my phone would crash every 15 minutes.
I took the battery out and put it back and it didn't want to boot anymore.
Had to send it back to Samsung -> broken motherboard which got replaced
firestruck said:
Hi, there are thousands of people with the same problem, its not the rom(JB)... but the proximity sensor that crashes the kernel, during calls, make the phone freeze/reboot.Search in google groups issue 37485, there are no solution, google and samsumg, dont say a word...It happens in nexus s too.
Click to expand...
Click to collapse
OMG what the hell????? how come i never heard it before???
can't believe this is happening...how can they put the phone on the market without thoroughly testing it???
frandel said:
I had this problem too
Random crashes which got worse, my phone would crash every 15 minutes.
I took the battery out and put it back and it didn't want to boot anymore.
Had to send it back to Samsung -> broken motherboard which got replaced
Click to expand...
Click to collapse
is your phone new? or have been used for awhile??
firestruck said:
Hi, there are thousands of people with the same problem, its not the rom(JB)... but the proximity sensor that crashes the kernel, during calls, make the phone freeze/reboot.Search in google groups issue 37485, there are no solution, google and samsumg, dont say a word...It happens in nexus s too.
Click to expand...
Click to collapse
found a post discussing this issue on other forum:
http://code.google.com/p/android/issues/detail?id=38595
he temporarily solved the problem with using headphone when calling.
cuz the sensor is disabled when headset is plugged in
here are five conditions that proximity sensor disable during a phone call.
These conditions is default settings of Phone application in android.
You can find the source code in PhoneApp.java,
boolean screenOnImmediately = (isHeadsetPlugged()
|| PhoneUtils.isSpeakerOn(this)
|| ((mBtHandsfree != null) && mBtHandsfree.isAudioOn())
|| mIsHardKeyboardOpen
|| mOrientation == AccelerometerListener.ORIENTATION_HORIZONTAL);
(1) isHeadsetPlugged(): When user headset is plugged, proximity sensor will be disable
(2) isSpeakerOn: When user turn on the speaker, proximity sensor will be disable
(3) BT device is connected and audio path is On
(4) Hardware Keyboard is opened.
(5) DUT is at Horizional state.
Click to expand...
Click to collapse
Please read forum rules before posting
Questions go in Q&A
Thread moved
Friendly Neighborhood Moderator
Google, has just moderated me, for complain about have a useless Phone, see?? They dont have a solution, and they dont want to pay for people who spent 400$, in a useless phone...So they shut up us...Really sad became google policy...
---------- Post added at 02:22 PM ---------- Previous post was at 02:17 PM ----------
Yep, with phones it works, but its a pain in the ass have all the time the headphones conected, even in your pocket...
secretiff said:
is your phone new? or have been used for awhile??
Click to expand...
Click to collapse
I have it since it came out in December last year
frandel said:
I had this problem too
Random crashes which got worse, my phone would crash every 15 minutes.
I took the battery out and put it back and it didn't want to boot anymore.
Had to send it back to Samsung -> broken motherboard which got replaced
Click to expand...
Click to collapse
I have such problem with my Nexus S, I heard it was something wrong with bootloader for JB that Google released, which have caused countless Nexus S to be bricked.
I have tried everything even some hardware level modification provided by XDA member to save it but with no success so only solution is motherboard replacement...
Hope same thing won't happen to Galaxy Nexus... because if it does, I will try to buy 4th generations of Nexus series and I will be killed by someone because it would be very expensive and I just brought GNex 2 months ago...
Sent from my Galaxy Nexus using xda premium
frandel said:
I have it since it came out in December last year
Click to expand...
Click to collapse
so...it crashes randomly while it was new :cyclops: ?
tl;dr I have a blue LED showing up in the top left of the phone and nothing showing up on the screen after the SAMSUNG logo appears. I do hear the Sprint 4G LTE music, but that's it. The screen is off.
NOTE: I'm running Sprint's stock 4.1.1 ROM rooted.
Other threads I looked at (neither is the same issue):
http://forum.xda-developers.com/showthread.php?t=581929
http://forum.xda-developers.com/showthread.php?t=1792477
I had my first OTA update appear today. When I ran the update, Clockwork showed up and upon hitting "Yes", it failed. I looked around online and found this guide to reverse my rooting: http://www.epiccm.org/2012/06/sprint-sgs3-stock-restore.html
I was able to successfully flash TeamEpic-RemoveRoot-from-Recovery-signed.zip, but I didn't hit the keys right for the next one and ended up booting into the OS.
After restarting the phone, I hit the right keys and started ODIN. I saw COM show up in blue and put the TeamEpic-Sprint-SGS3-stock-boot-and-recovery.tar.md5 file in the PDA area then hit Start. I got a green PASS and then closed Odin and waited.
The phone had a black screen with that blue LED in the top left. I waited a while and then just powered it off. Took out the battery and tried again, same thing; although, the SAMSUNG logo does show up. It turns off when the Sprint part is supposed to show and at that moment I can hear the audio but the screen turns off. In this mode, the phone gets very very hot.
I can still boot into the stock recovery, but I can't do much else.
I just wanted the OTA . Does anyone know what might be happening?
EDIT: I put Clockwork Recovery back on, and then Advanced Recovered the boot part of a backup I did before this mess. Surprisingly, that worked. Problem is, I still haven't gotten the OTA working.
Ideas?
Just odin the stock tar
Sent from my SPH-L710 using xda app-developers app
CrfEpic4g said:
Just odin the stock tar
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
What do you mean by that? Which stock tar?
I think the latest tar we have is still Lj7 but idk. just flash the lj7 tar in odin and update to the latest ill try and find it for you
Sent from my SPH-L710 using xda app-developers app
---------- Post added at 08:50 AM ---------- Previous post was at 08:47 AM ----------
http://www.hotfile.com/dl/161492098/9fa8372/L710VPALEN_L710SPRALEN_SPR.zip.html
Theres a link to lj7 just download that flash it in odin and youll be back to stock. Then all you have to do is update to mb1.
Sent from my SPH-L710 using xda app-developers app
Saturn2888 said:
tl;dr I have a blue LED showing up in the top left of the phone and nothing showing up on the screen after the SAMSUNG logo appears. I do hear the Sprint 4G LTE music, but that's it. The screen is off.
NOTE: I'm running Sprint's stock 4.1.1 ROM rooted.
Other threads I looked at (neither is the same issue):
http://forum.xda-developers.com/showthread.php?t=581929
http://forum.xda-developers.com/showthread.php?t=1792477
I had my first OTA update appear today. When I ran the update, Clockwork showed up and upon hitting "Yes", it failed. I looked around online and found this guide to reverse my rooting: http://www.epiccm.org/2012/06/sprint-sgs3-stock-restore.html
I was able to successfully flash TeamEpic-RemoveRoot-from-Recovery-signed.zip, but I didn't hit the keys right for the next one and ended up booting into the OS.
After restarting the phone, I hit the right keys and started ODIN. I saw COM show up in blue and put the TeamEpic-Sprint-SGS3-stock-boot-and-recovery.tar.md5 file in the PDA area then hit Start. I got a green PASS and then closed Odin and waited.
The phone had a black screen with that blue LED in the top left. I waited a while and then just powered it off. Took out the battery and tried again, same thing; although, the SAMSUNG logo does show up. It turns off when the Sprint part is supposed to show and at that moment I can hear the audio but the screen turns off. In this mode, the phone gets very very hot.
I can still boot into the stock recovery, but I can't do much else.
I just wanted the OTA . Does anyone know what might be happening?
EDIT: I put Clockwork Recovery back on, and then Advanced Recovered the boot part of a backup I did before this mess. Surprisingly, that worked. Problem is, I still haven't gotten the OTA working.
Ideas?
Click to expand...
Click to collapse
Why are you so intent on taking the OTA? Freeza has a stock rooted ROM over in his thread. And if you want just update the baseband, just flash the "MB1 Firmware/modem/baseband update" file in the aforementioned thread.
If you're already rooted with a custom recovery (which you were/are), there's no reason to unroot just to flash the OTA. Freeza typically has his stock rooted ROM updated with the OTA within a week of it being released. In my area OTAs are kind of late, so he typically gets it out before I even see the notification.
So, in summary. OTAs are not required, XDA (and Freeza in particular) has you covered.
topherk said:
Why are you so intent on taking the OTA? Freeza has a stock rooted ROM over in his thread. And if you want just update the baseband, just flash the "MB1 Firmware/modem/baseband update" file in the aforementioned thread.
If you're already rooted with a custom recovery (which you were/are), there's no reason to unroot just to flash the OTA. Freeza typically has his stock rooted ROM updated with the OTA within a week of it being released. In my area OTAs are kind of late, so he typically gets it out before I even see the notification.
So, in summary. OTAs are not required, XDA (and Freeza in particular) has you covered.
Click to expand...
Click to collapse
I'll go ahead and give it a try then. I haven't ever had a ROM update since I got the phone in October so I figure the upgrade won't work right, and I'll need the full ROM. Currently doing a backup.
Does flashing a ROM affect all app settings? And if so, by that point I'd just wanna have another ROM. The main reason I am fine w/ the stock ROM rooted is bc all my settings and apps are already installed and configured as well as the fact that I know it will work properly. So if this removes my settings, no reason to go stock anymore aside from the fact that I've seen that CyanogenMod doesn't get as good of signal on the S III as stock-based ROMs. Do you know if this still true?
Saturn2888 said:
I'll go ahead and give it a try then. I haven't ever had a ROM update since I got the phone in October so I figure the upgrade won't work right, and I'll need the full ROM. Currently doing a backup.
Does flashing a ROM affect all app settings? And if so, by that point I'd just wanna have another ROM. The main reason I am fine w/ the stock ROM rooted is bc all my settings and apps are already installed and configured as well as the fact that I know it will work properly. So if this removes my settings, no reason to go stock anymore aside from the fact that I've seen that CyanogenMod doesn't get as good of signal on the S III as stock-based ROMs. Do you know if this still true?
Click to expand...
Click to collapse
Strange. I upgraded the ROM by flashing, everything seemed to work as I'm at 4.1.2 now, but the Upgrade notification is still there for some reason. Is there any way to tell the phone it's been upgraded?
Saturn2888 said:
Strange. I upgraded the ROM by flashing, everything seemed to work as I'm at 4.1.2 now, but the Upgrade notification is still there for some reason. Is there any way to tell the phone it's been upgraded?
Click to expand...
Click to collapse
Setting >scroll all the way to the bottom >about phone>read what it say there. If it says your on latest then it should be ok you may have to clear some things and if it doesn't say latest just edit the build prop.
Go to this thread by Cnexus and follow all instructions http://forum.xda-developers.com/showthread.php?p=39627397
Transmitted with a portable device using Xparent Blue Tapatalk 2
Saturn2888 said:
Strange. I upgraded the ROM by flashing, everything seemed to work as I'm at 4.1.2 now, but the Upgrade notification is still there for some reason. Is there any way to tell the phone it's been upgraded?
Click to expand...
Click to collapse
Are you on MB1 or MA6?
Just flash an updated rom, or follow the instructions in my OTA thread for how to get rid of it
Saturn2888 said:
I'll go ahead and give it a try then. I haven't ever had a ROM update since I got the phone in October so I figure the upgrade won't work right, and I'll need the full ROM. Currently doing a backup.
Does flashing a ROM affect all app settings? And if so, by that point I'd just wanna have another ROM. The main reason I am fine w/ the stock ROM rooted is bc all my settings and apps are already installed and configured as well as the fact that I know it will work properly. So if this removes my settings, no reason to go stock anymore aside from the fact that I've seen that CyanogenMod doesn't get as good of signal on the S III as stock-based ROMs. Do you know if this still true?
Click to expand...
Click to collapse
If you dirty flash the rom over whatever you had before, it should not affect any settings
CNexus said:
Are you on MB1 or MA6?
Just flash an updated rom, or follow the instructions in my OTA thread for how to get rid of it
If you dirty flash the rom over whatever you had before, it should not affect any settings
Click to expand...
Click to collapse
MB1 as of now. What do you mean by dirty flash the rom?
edfunkycold said:
Setting >scroll all the way to the bottom >about phone>read what it say there. If it says your on latest then it should be ok you may have to clear some things and if it doesn't say latest just edit the build prop.
Go to this thread by Cnexus and follow all instructions http://forum.xda-developers.com/showthread.php?p=39627397
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
I think the message isn't showing up anymore bc it hasn't bugged me at all today. Device Status is and has always been "Modified" anyway.
Thanks!
Saturn2888 said:
MB1 as of now. What do you mean by dirty flash the rom?
I think the message isn't showing up anymore bc it hasn't bugged me at all today. Device Status is and has always been "Modified" anyway.
Thanks!
Click to expand...
Click to collapse
A dirty flash is when you flash without clearing anything, and that's why no data is lost when you do one of those. However it can lead to issues, so i would advise against it when possible
CNexus said:
A dirty flash is when you flash without clearing anything, and that's why no data is lost when you do one of those. However it can lead to issues, so i would advise against it when possible
Click to expand...
Click to collapse
Yeah, last time I did that, the system wouldn't boot.