Related
Hi. This is my first time posting. I apologize in advance, im going to come across as a noob.
I got tired of waiting for google to get 2.3 to the N1 users. I decided it was time to unlock and root my phone, after all thats what it was designed for. Up until this point the phone was stock with all updates. I thought one touch root no longer worked. I dont know why i thought this. I used a guide to work through it. I cannot post links otherwise i would. ilikemygooglephone . com is where it came from
Everything worked according to this guide until I completed it and powered my phone on for the first time. I thought I was going to see a stock wiped nexus one...Instead I got shafted.
The phone reboots randomly. It happens quickly and unpredictably.
Notification bar will never slide down. If i try to the phone lags but never shows notifications.
No 3g
No wifi
The phone says I have no service (selected network tmobile unavailable) although I can still make and receive calls.
The sd card will not mount. I cannot access it on the phone. When pluggen into my laptop the phone will charge but wont give me the option to access the sd card.
At times the graphics are buggy and dont operate properly
There are probably other problems that i am forgetting but I think this says enough. Since i cannot access the SDcard I really dont know what to do.
Im sorry if this thread is in the wrong place or happens to be a previously answered question. I just really like my phone and I hope its not wasted. Can someone tell me what I did wrong or how i can get this right.
YEAH i noobed it.
I freaked out on the above issue for about 5 hours. Now I believe i have everything back to normal. My problem was i didnt load the proper superboot. Once i found the FRG83 one and redid the process using that instead it worked fine. Either i was using the wrong superboot or i had a corrupted download somehow.
Feels good to figure it out on my own though....i feel...less noob.....NAH
Hey, guys. Hoping some of you experts can help me diagnose what's wrong with my Samsung Infuse. I bought it off Craigslist at the end of May, and the guy had the phone with the original screen protector on it, with the original case and all accessories, so I had no reason to believe it had any problems. He told me the phone was already rooted & unlocked, which I wanted since I signed up with Straight Talk. I used it for June & July and had a host of problems, so I put on the CM10 ROM last week to see if it helped. It didn't. Here are the problems I continuously encounter:
1. When going to unlock my phone with a pattern, once in awhile it won't detect my finger-presses. Sometimes nothing shows up at all, sometimes one of the dots will highlight as I pass over it, but it won't draw. Eventually the screen turns off, and I turn it on and try it again. Usually it ends up working.
2. The battery dies much quicker than I expect it should. I tried running JuiceDefender and not running JuiceDefender, and it doesn't seem to make a difference. Even without using my phone much for anything, even with the screen off, the battery will run out before the day is out. It's like if you were driving and had a hole in your tire... seems like some sort of a leak.
3. The cell radio seems flaky. Sometimes I won't get texts on time. A lot of the time I can't access any data, which is very important as I use Google Voice for lots of my texting, so I send a text and it won't go out. Loading web pages or reloading my email shows that it is a data problem.
Those are the primary problems, and I suspect that somehow they are all related. I'm not sure if the Craigslist guy sold me a lemon, or there is some other problem that came up. I've tried multiple ROM's and disabling every app I can think of. Can anyone think of anything that would cause these problems & any way to fix it? Or do I just own a broke phone that I have to throw in the garbage?
Thanks in advance for reading!
a whole slew of problems can lead to a whole slew of possibilities for your issues.
first, i wasnt aware that you could do any of this on a straight talk phone, but i could be wrong. i am not the "expert" you may be looking or hoping for, though one i am sure will show up.
second, i think the response you may get is......did you go to JB straight from Gingerbread??? that will cause HUGE problems.
dd you read OP and follow to a tee??? again HUUUUGGEE problems.
the "never fail" here.....READ READ READ. feel confident as to what you are doing and follow steps one at a time. UNDERSTAND steps one at a time.
first thing that never hurts.....return to stock and start from scratch.
"super everything thread" under development.
Odin "stock-root & modded 3e rcovery.
follow all directions TO THE TTT.
if that doesnt work, you might have to get some mortar, you've got yourself a BRICK.
i know almost everyone else here is more of a expert than i am, but i do believe that is where they will tell you to start
good luck and be sure and thank the experts
captemo said:
first, i wasnt aware that you could do any of this on a straight talk phone, but i could be wrong. i am not the "expert" you may be looking or hoping for, though one i am sure will show up.
second, i think the response you may get is......did you go to JB straight from Gingerbread??? that will cause HUGE problems.
dd you read OP and follow to a tee??? again HUUUUGGEE problems.
first thing that never hurts.....return to stock and start from scratch.
"super everything thread" under development.
Odin "stock-root & modded 3e rcovery.
follow all directions TO THE TTT.
if that doesnt work, you might have to get some mortar, you've got yourself a BRICK.
Click to expand...
Click to collapse
While I have no idea what you're getting at by your Straight Talk comment, as ST is little more than AT&T service that's sold through a 3rd party at a discounted rate, the fact that he's using ST may be part of his problems, at least in regards to the network issues. I'm also having an unbelievable amount of data issues on ST. ST is having some network problems that are affecting a decent amount of customers who are on their AT&T network.
One thing that the OP may want to try is this: Download DNS Changer from the Play Store, and change your primary and secondary DNS to OpenDNS1 and OpenDNS2. Or try different settings, as there are a bunch that are available. That has made at least some difference with my data connectivity issues.
Based on my own experience, having tried to go to JB directly from GB, is that if it's going to affect your radio, it's likely to completely wipe out your EFS data so you won't have ANY cellular or data networking capabilities. As stated, that's simply based on how it worked out for me, and there could easily be other side-effects that just didn't happen to show up for me.
I agree with returning completely to stock UCLB3, with the GB bootloaders. Then flash Entropy's 4.4.2012 Kernel, which will also install CWM Recovery. I'd personally reccomend Heimdall, as it seems to be somewhat simpler. Detailed information on returning to stock via Heimdall can be found in this thread:
http://forum.xda-developers.com/showthread.php?t=1629079&highlight=heimdall+uclb3
If you use it, be sure to thank qkster for making it available. He's probably the most helpful person you're likely to find on this forum, especially where us noobs are concerned.
I would take it back to stock and start all over.
Here is a very helpful thread.
http://forum.xda-developers.com/showthread.php?t=1700416
I agree with parrot head. When issues arise go back to stock. That's the best part of our phones. They are damn near impossible to really mess up. Just have to be ware of bootloader flash going wrong. If you got your gb rom from keis your good to go though.
Sent from my SGH-I997 using xda app-developers app
Appreciate the response, guys. I guess it doesn't hurt to try to start from scratch... AGAIN! It just seems like I'm putting an awful lot of hours into putting new ROM's and bootloaders on this phone. Going to be especially frustrating if I go through all the steps and it still doesn't fix my issues, which would mean my phone is broke. Oh well, guess I have little other choice.
All of the issues sound related..
It shouldn't take long to drop to stock and flash up to JB.. I've bobbled and missed steps here and there and have had to return from stock more times than I care to admit.. even rooting and flashing up the ladder only take about 20 minutes if even that..
Good luck!
drnecropolis said:
All of the issues sound related..
It shouldn't take long to drop to stock and flash up to JB.. I've bobbled and missed steps here and there and have had to return from stock more times than I care to admit.. even rooting and flashing up the ladder only take about 20 minutes if even that..
Good luck!
Click to expand...
Click to collapse
Yes, the flashing process isn't that long, it's getting back my phone to all of my customized settings that ends up taking weeks. Home screen icon positioning, logging in to every app, system settings, etc.
Didn't create a backup?
drnecropolis said:
Didn't create a backup?
Click to expand...
Click to collapse
I've always created backups with Titanium Backup, but when I restore the apps, a lot of them ask me to re-login or re-verify myself.
Thanks for the advice guys.
Spent a whole day going back to stock, then CWM red, then ICS, then Jellybean. Things seem to be markedly better, but the phone still seems laggy in a few places. Is this just because it's not the latest and greatest processor?
Also, the GPS just does not work right. It's still identifying me as being in Missouri even though I'm in Nevada. Consistently. Do I just have to live with that?
veeRob said:
Thanks for the advice guys.
Spent a whole day going back to stock, then CWM red, then ICS, then Jellybean. Things seem to be markedly better, but the phone still seems laggy in a few places. Is this just because it's not the latest and greatest processor?
Also, the GPS just does not work right. It's still identifying me as being in Missouri even though I'm in Nevada. Consistently. Do I just have to live with that?
Click to expand...
Click to collapse
Are you still using the Trebuchet Launcher that comes built-in to the JB ROM? If so, that may be part of your lag problems. I just use ADW EX launcher. Here's an excerpt from the Paranoid Android JB OP:
******* EVERYONE: If you experience a sudden lag for no reason, IT is due to Trebuchet. GOOD NEWS though... From reading the log cat on my end, there is a very simple fix... Go to settings -Launcher - Homescreen - And Check "Resize any widget" and you are good to go! Instantly fixes the lag problem that a few have been experiencing. I have located the source code that needs to be changed and this will be enabled by default on future builds. ********
Click to expand...
Click to collapse
As far as the GPS goes, I think Samsung just used ****ty receivers in the Infuse. My GPS isn't quite as bad as yours seems to be, but it's nowhere near as accurate or reliable as the GPS chipset in my crummy little Optimus V.
I haven't tried the jig, but all the other symptoms such as dead screen,functionless buttons and all are there, so I think it is Hard Bricked. It's really weird what happened, I rooted my S3, it was working perfectly, then I unlocked the bootloader, it was perfectly fine even after that, then using ROM Manager I installed clockwork recovery mod, it was was working great. Then, I deleted my android market using ES File Explorer, and the guide for replacing the market told me to look for Vending.apk and then delete it, I looked but couldn't find it, so I 100% remember I tapped the search button in ES File Explorer and searched for Vending.apk, then suddenly a window popped up with names of files flashing but it didn't say searching or anything just three dots (...) and under there were two options YES and NO. I pressed No, it closed and then popped up again so this time I pressed Yes. then the names of files kept flashing and then it finished but didn't give me any search result, But my Phone memory was showing Empty, only the sd card folder was there and nothing else so I closed the app and opened it again, still the phone memory was empty, I was freaked out, so I restarted the phone and then, it never started :crying: I don't know what happened. Please help?
odin back to stock and start over....your device is far from hardbricked.
Really?? Can you please tell me step by step what to do?? I'm a complete noob at this!
droidstyle said:
odin back to stock and start over....your device is far from hardbricked.
Click to expand...
Click to collapse
My device does not go into download mode, nor in recovery, it's buttons are useless and there's a completely dead screen.
droidstyle said:
odin back to stock and start over....your device is far from hardbricked.
Click to expand...
Click to collapse
have you tried a different battery?
I forgot to mention, it's brand new, this happened the second day I bought it. So, the battery is flawless and perfect.
droidstyle said:
have you tried a different battery?
Click to expand...
Click to collapse
No its dead for sure. He tried to unlock the us cellualr S3 which would result in a perma brick.
You don't need to unlock the bootloader of the us cellular S3. That is why everything is labeled "verizon unlock" and stuff.
con247 said:
No its dead for sure. He tried to unlock the us cellualr S3 which would result in a perma brick.
You don't need to unlock the bootloader of the us cellular S3. That is why everything is labeled "verizon unlock" and stuff.
Click to expand...
Click to collapse
ahh i missed that detail...yes i agree its dead for sure! jtag or new replacement time.
Since it's only a couple days, take it back into USCC store. You're in your 15 day Window, they should swap it for a new one. Act dumb, don't tell them you rooted it. Just say you heard it buzz and it died. They'll mark it down as defective and give you a new one
How the hell was I supposed to know that? The US Cellular S3 is completely identical to the Verizon one, the only difference is the carrier logo, I rooted it with the Verizon S3's guide everything went perfectly fine, so I continued to do all the other stuff. I just got it 2 days ago :crying: . Huff, I've sent it for JTAG to a friend.
droidstyle said:
ahh i missed that detail...yes i agree its dead for sure! jtag or new replacement time.
Click to expand...
Click to collapse
ShazzyK-IDEOS said:
How the hell was I supposed to know that? The US Cellular S3 is completely identical to the Verizon one, the only difference is the carrier logo, I rooted it with the Verizon S3's guide everything went perfectly fine, so I continued to do all the other stuff. I just got it 2 days ago :crying: . Huff, I've sent it for JTAG to a friend.
Click to expand...
Click to collapse
a simple google search would of told ya that...
http://lmgtfy.com/?q=is+the+bootloader+unlocked+on+the+usc+galaxy+s3
research then flash dont flash then research!
tallgrasshawk said:
Since it's only a couple days, take it back into USCC store. You're in your 15 day Window, they should swap it for a new one. Act dumb, don't tell them you rooted it. Just say you heard it buzz and it died. They'll mark it down as defective and give you a new one
Click to expand...
Click to collapse
Great idea, but, I'm not in the US. I bought this phone from a guy who brought it from the US, I got it for half the price of an S3 here. So now, I don't know what to do, I gave it to friend, I hope he'll fix it, but if he's unable to can I give it to Samsung?
True, well said :'( I messed up big time.
droidstyle said:
a simple google search would of told ya that...
http://lmgtfy.com/?q=is+the+bootloader+unlocked+on+the+usc+galaxy+s3
research then flash dont flash then research!
Click to expand...
Click to collapse
Hi everyone,
I think my fiance might have hard-bricked his (new! Less than 24 hrs old!) Verizon Samsung Galaxy S III. He researched, rooted, set up bit-defender and it was working fine but when he tried to copy music files onto the micro-SD, they appeared to have gone onto the hard-drive instead and made his phone uber sluggish. We had some friends over, so he dropped the issue for a while and then went back to try to fix it only to make things worse. I know there isn't enough detail there about what *else* he tried to do, but when he came to bed last night he was kicking himself for not researching it enough and mentioned that he tried taking the batter out, resetting it, taking the sim card out, resetting it, telling bit defending to wipe the phone, etc. but all it would do last night was just display the 'samsung' logo then go to black.
This morning, I found your threads and tried to do the power+down+home advice that I've seen on a few threads here but it didn't work (obviously).
I suggested using the micro-SD adapter to try to explore the files on a PC, so we might look into that later.
Is there anything else you guys would recommend? I'm thinking the only thing to fix it now is the dopey route. :silly:
-Ami
Your phone is Soft Bricked not hard bricked, otherwise it wouldn't even turn on, Use A USB JIG to force it into download mode, then reflash with Odin.
Aminarra said:
Hi everyone,
I think my fiance might have hard-bricked his (new! Less than 24 hrs old!) Verizon Samsung Galaxy S III. He researched, rooted, set up bit-defender and it was working fine but when he tried to copy music files onto the micro-SD, they appeared to have gone onto the hard-drive instead and made his phone uber sluggish. We had some friends over, so he dropped the issue for a while and then went back to try to fix it only to make things worse. I know there isn't enough detail there about what *else* he tried to do, but when he came to bed last night he was kicking himself for not researching it enough and mentioned that he tried taking the batter out, resetting it, taking the sim card out, resetting it, telling bit defending to wipe the phone, etc. but all it would do last night was just display the 'samsung' logo then go to black.
This morning, I found your threads and tried to do the power+down+home advice that I've seen on a few threads here but it didn't work (obviously).
I suggested using the micro-SD adapter to try to explore the files on a PC, so we might look into that later.
Is there anything else you guys would recommend? I'm thinking the only thing to fix it now is the dopey route. :silly:
-Ami
Click to expand...
Click to collapse
ShazzyK-IDEOS said:
Really?? Can you please tell me step by step what to do?? I'm a complete noob at this!
Click to expand...
Click to collapse
If you're such a noob and unprepared for a brick, maybe you shouldn't have ventured down custom ROM/unlock avenue?
Just a thought.
Sent from my SCH-I535 using Tapatalk 2
ShazzyK-IDEOS said:
Your phone is Soft Bricked not hard bricked, otherwise it wouldn't even turn on, Use A USB JIG to force it into download mode, then reflash with Odin.
Click to expand...
Click to collapse
Yeah, this morning it won't even turn on no Samsung, no hope. Lesson learned... hopefully not a very expensive one.. :fingers-crossed:
Aminarra said:
Yeah, this morning it won't even turn on no Samsung, no hope. Lesson learned... hopefully not a very expensive one.. :fingers-crossed:
Click to expand...
Click to collapse
Pull the battery, put it in and let it charge for a while couple hours. Then hold vol - , home and power. If it week go into download/Odin mode you're fine. If so then go to the development thread stickies and follow droid style guide section 6
Sent from my SGS3 running Eclipse Touchwiz
Great thought, but let me tell you before my Galaxy S3 I owned a Wildfire S, tinkered with it every bit, OC,Rom,bootloader and everything, before that I owned a Huawei U8150, my first android, I literally went bezerk modding that thing. So, I'm not a noob at this,I was a noob at this different Carrier different software kinda thing, I thought the phone was the same and indeed it is, but the difference is that the Verizon's Bootloader is locked. I'm well familiar with everything, I just messed up by not researching that if the bootloader was unlocked already, mainly because I was a bit too excited about getting my S3.
1ManWolfePack said:
If you're such a noob and unprepared for a brick, maybe you shouldn't have ventured down custom ROM/unlock avenue?
Just a thought.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
tallgrasshawk said:
Since it's only a couple days, take it back into USCC store. You're in your 15 day Window, they should swap it for a new one. Act dumb, don't tell them you rooted it. Just say you heard it buzz and it died. They'll mark it down as defective and give you a new one
Click to expand...
Click to collapse
Yup!
I have an LG G2 D800, with stock everything; I did something either interesting or dumb, and now it won't boot. I never rooted it because all the instructions were for Windows, and I use Linux, and never found anything that explained how to do it with Linux, if possible. But I now have a a usable Windows (Vista) installed in a VM, so maybe I can do something.
Here's what happened; I hope someone can help steer me in the right direction...
I finished my AT&T contract, and decided to move to Project Fi. I got a Nexus 5X, and got an unlock code for my G2, which I wanted to give to my wife's brother in China. So, I needed to get a non-AT&T sim to enter the unlock code. Here's where I went wrong. I was curious about what would happen if I used the Project Fi sim, and since I wasn't rooted, I didn't think it would do anything bad (silly me!). Well, it did. It crashed, so I removed the sim and turned off the phone. Now, it won't boot. It sometimes just shuts down immediately, sometimes after the LG logo, sometimes after the AT&T logo, and a few times, it made it all the way to the login screen before turning off. Never further than that.
I did a factory reset, tried starting in safe mode many times, and sometimes it gets to a screen saying it's updating Android, but has never made it past 20 files before turning off. By the way, if it was reset, how could it update Android - wouldn't the WiFi need to be set up?
So, I'm wondering what might be wrong, and what might fix it. Obviously, I'm willing to try anything at this point, as it can't get much worse. The phone is in perfect shape, and would make a nice gift (or sellable item), so I hate to lose it.
I'm pretty technically inclined, but I don't know much about phone tech. I know Linux pretty well though, so I can follow directions without too much babying. Or, just point me the right direction.
It did go into download mode, but right now, it seems like it doesn't want to do that.
Thanks to anyone that can help.
Marty
martyfried said:
I have an LG G2 D800, with stock everything; I did something either interesting or dumb, and now it won't boot. I never rooted it because all the instructions were for Windows, and I use Linux, and never found anything that explained how to do it with Linux, if possible. But I now have a a usable Windows (Vista) installed in a VM, so maybe I can do something.
Here's what happened; I hope someone can help steer me in the right direction...
I finished my AT&T contract, and decided to move to Project Fi. I got a Nexus 5X, and got an unlock code for my G2, which I wanted to give to my wife's brother in China. So, I needed to get a non-AT&T sim to enter the unlock code. Here's where I went wrong. I was curious about what would happen if I used the Project Fi sim, and since I wasn't rooted, I didn't think it would do anything bad (silly me!). Well, it did. It crashed, so I removed the sim and turned off the phone. Now, it won't boot. It sometimes just shuts down immediately, sometimes after the LG logo, sometimes after the AT&T logo, and a few times, it made it all the way to the login screen before turning off. Never further than that.
I did a factory reset, tried starting in safe mode many times, and sometimes it gets to a screen saying it's updating Android, but has never made it past 20 files before turning off. By the way, if it was reset, how could it update Android - wouldn't the WiFi need to be set up?
So, I'm wondering what might be wrong, and what might fix it. Obviously, I'm willing to try anything at this point, as it can't get much worse. The phone is in perfect shape, and would make a nice gift (or sellable item), so I hate to lose it.
I'm pretty technically inclined, but I don't know much about phone tech. I know Linux pretty well though, so I can follow directions without too much babying. Or, just point me the right direction.
It did go into download mode, but right now, it seems like it doesn't want to do that.
Thanks to anyone that can help.
Marty
Click to expand...
Click to collapse
Greetings.
Thank you for using XDA Assist. I'm going to move this thread to the specific device Q and A forum. You should find expert help there. Good luck!
Hey all.
I use Samsung pay quite a bit, and I went to set it up on my AT&T S8 Plus, and when you open the app, you click continue, and a spinning ring just comes up, and nothing ever happens. I've uninstalled/reinstalled the app. I've turned on all permissions for the app and all permissions for the Samsung Pay Framework. My device is not encrypted, I dont know anything else to try or do. Is anyone else having this issue?
I just set mine up after reading this post. No issues. I am on AT&T
dave30534 said:
I just set mine up after reading this post. No issues. I am on AT&T
Click to expand...
Click to collapse
well that's frustrating. were you on wifi? did you use the new sim card that came with your phone or your old one? idk if that has anything to do with it, but i always just take my sim card out of my old one and put it in the new one.
Thanks!
Captain McFunk said:
well that's frustrating. were you on wifi? did you use the new sim card that came with your phone or your old one? idk if that has anything to do with it, but i always just take my sim card out of my old one and put it in the new one.
Thanks!
Click to expand...
Click to collapse
On wifi. My old phone does not have sim cards that fit this one. I used what came with the box. I had to register it by phone before they turned the phone to active.
I'm on AT&T as well and had no issues setting up.
Can you just put a cricket sim card in or setup with the att sim card first?
Still not sure what's going on here, but I used the SIM card that came in the box and it's still not working. It just spins once you click "start" -- I uninstalled it and downloaded the latest version from apk-mirror and when i ran it, it played a little video but then an error came up saying samsung pay isn't available when using a sim card from another country. please insert a sim card from korea......i mean wtf mate. I bought the phone from AT&T directly, so not sure what the deal is there. Anyone have any ideas for anything I can try?
Captain McFunk said:
I use Samsung pay quite a bit, and I went to set it up on my AT&T S8 Plus, and when you open the app, you click continue, and a spinning ring just comes up, and nothing ever happens. I've uninstalled/reinstalled the app. I've turned on all permissions for the app and all permissions for the Samsung Pay Framework. My device is not encrypted, I dont know anything else to try or do. Is anyone else having this issue?
Click to expand...
Click to collapse
I had the same problem at first. I tried restarting the app, rebooting the phone, clearing the app's cache & data, reinstalling the app, and wiping the system cache. I tried it on WiFi and on mobile data. None of that seemed to help. Then I left it alone for a couple of hours and the next time I tried, it just worked.
I have no idea what was causing the problem. I don't know if any of my efforts had a delayed result, or if the efforts were irrelevant and the problem just fixed itself. But either way, it's fine now.
Another failure, different
Captain McFunk said:
Hey all.
I use Samsung pay quite a bit, and I went to set it up on my AT&T S8 Plus, and when you open the app, you click continue, and a spinning ring just comes up, and nothing ever happens. I've uninstalled/reinstalled the app. I've turned on all permissions for the app and all permissions for the Samsung Pay Framework. My device is not encrypted, I dont know anything else to try or do. Is anyone else having this issue?
Click to expand...
Click to collapse
It still does not work on my S8+. It may have something to do with last OS update... ? All I know is, I used it for about a year with occasional odd failures, but it was reliable on my S7.
Now, it does not work at all. I called Samsung and the rep kept me on the phone for a long time, gathering details...