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
Related
I'll go ahead and admit that, yes, I'm completely new to the rooting and rom world, but I read a thread about a 1-click app and downloaded it. I followed (or so I thought) the directions to a tee and my phone isn't working now. I downloaded the GSB 2.5 and had that on my sdcard. I rooted my phone (and a screen appeared saying it was rooted) and then I rebooted the phone and flashed the GSB rom as it said to do. It was on the cyanogen screen for over an hour, recycling and I finally pulled the battery out when others said it only took 5-10 minutes for them. So I repeated the process as others have said to do, but it's still doing the same thing. I'm going insane now. I put everything into that phone and really cannot afford to lose it all. I thought I backed up everything, but I can't tell now. Please tell me I didn't "brick" my phone. What should I do? I even tried to go back to the factory setting, but it keeps going through the cyanogen thing again. I have no idea what to do now and desperately need help from those who actually know what they're doing. Anyone know what to do and can describe this to someone who doesn't really get all the lingo???
Hello, thank you for reading this, to start with.
First off, here are the specs of the phone I am asking about:
Galaxy S 4G exclusive from T-mobile
Model #: SGH-T959V
Firmware: 2.2.1
Kernel:2.6.32.9
Build #: FROYO.VUVKD1
If that's not enough please ask.
Back Story: Phone was given to my ex by his mother. It was for T-mobile, which don't have good plans for pre-paid/pay as you go in my area. So I was asked to make it work for ATT. I rooted using Superoneclick, and then did the hex voodoo and unlocked the phone. It worked for a few months, no problem. There was no data plan so no phone internet was acessed, wifi was but only rarely. It DID work.
Then, the other day, my ex dropped it. It worked just fine for a minute or two, but now is stuck with no service, and such. No imei number. No phone number. Nothing. Searches for the provider. Sim card has been replaced just in case. I've restored and re-rooted, but i couldn't re-unlock the sim # as the hex editor couldn't find the code. AND the sim doesn't ask for an unlock code when inserted.
I have googled and searched my tushie off to figure this out. All my answers are bad flashing of roms and such, and the last anything that was done to it out of ordinary use was me unlocking it, and it worked for months.
Keep in mind that i haven't a clue what flashing a rom means, or what odin is (i read that several times, haven't a clue what it is), and I know how to follow step by step instructions as long as they use reasonably understandable terms to the android nooblett.
I am currently running on an ubuntu laptop, so downloading and running anything means I download, put it on a flash drive, and install it or run it on a windows computer that doesn't have internet access (long story, i'm rambling as it is).
Some extras:
I did not do any backups, because everything worked for the longest time anyways.
I've tried a few things involving nv_data.bin and the like, but it seems they don't exist or are hidden from my silly self.
I have to re-root and such as I've just performed a factory reset to see if that would fix the issue.
I am extremely tired so I'll likely do nothing tonight, including responding, as I have to work tomorrow and lots of other things.
I am a rambling idiot, feel free to mock me for it, but i do try and give out as much information as I can.
Any questions? If not, please, please, please tell me an answer that doesn't involve sending this phone back, because it's long out of warranty and has passed through many hands (the previous people did not like t-mobile either...).
And thank you for reading the ramblings of this idiot.
Are you sure it's not a hardware issue? I dropped my old iPhone 3G and it stopped recognizing my SIM unless it was placed just right. Have you tried any other SIM cards in there? Take a look at my SGS4G carrier unlocker (link is in my signature) and see if it scans through your nv_data.bin file correctly. I never liked that people encourage direct editing of that file. :/
Have you tried seeing if Samsung Kies mini will recognize your phone? Since you still seem to be on factory stock and did a factory reset.... download Kies mini, plug your phone in and see if it will recognize it. Kies mini - in case you are unaware is Samsung's software to update our phone.
If it recognizes your phone - try to do the upgrade to Gingerbread. If it will upgrade to Gingerbread, it might rewrite your efs folder - which is where the IMEI and phone information is stored. If it doesn't rewrite the efs folder... it shouldn't matter if your phone is out of warranty as Kies mini - you will say and not mention the other stuff you have done - messed it up during the upgrade... which is happening to people more than you would think. Take it back to where you purchased the phone and give it a shot. Or try contacting Samsung. Many have done that as well. You need a computer you can download Kies mini to and do the upgrade... in other words - a computer with internet access you can work on.
o You may start with another Factory Reset
o Download Kies mini if you do not already have it. < - - Click link here for Kies mini - When you follow this link you will see two tabs - 'Manuals' and 'Software' - click software and download.
o Make sure your phone is charged.
o Make sure USB Debugging is off.
o Start Kies mini on the computer.
o Make sure phone is not connected to computer yet.
o In USB Settings on phone select ‘Kies (Firmware update)’ if it is not set to ask every time.
o Plugged in phone, let device drivers install on computer. You will see a notification on your computer when complete.
o Then Kies mini will recognize the phone.
o Hit upgrade and wait.
o Phone will eventually reboot. Check your IMEI.
---------- Post added at 05:32 AM ---------- Previous post was at 05:26 AM ----------
FBis251 said:
I dropped my old iPhone 3G and it stopped recognizing my SIM unless it was placed just right. Have you tried any other SIM cards in there?
Click to expand...
Click to collapse
You owned an iPhone FB? Damn!
FB is one of the best on here... however, if you are on stock you should try an upgrade if Kies mini will recognize your phone. I have read flashing stock - in this instance via Kies mini - has many times rewritten the efs folder for people with IMEI problems. Either way - if he is on stock everything he can take it in to T-Mobile and ask for you?
Thoughts on that FB?
lumin30 said:
You owned an iPhone FB? Damn!
FB is one of the best on here... however, if you are on stock you should try an upgrade if Kies mini will recognize your phone. I have read flashing stock - in this instance via Kies mini - has many times rewritten the efs folder for people with IMEI problems. Either way - if he is on stock everything he can take it in to T-Mobile and ask for you?
Thoughts on that FB?
Click to expand...
Click to collapse
I still have it lying around and it's bricked. I wanna try flashing it again with another USB cable but I can't find my spare.
Hmm, haven't ever tried the kies mini approach but it's worth a shot, especially if it'll restore the /efs directory.
If it IS fully stock, then yes take it in to T-Mob and see if they'll give you a replacement and next time don't go editing anything in /efs directly.
Thank you everyone. I will try these things later today. Like I said the only things I've personally done to it are root and unlock. I dunno what happened and its possible it could be hardware, but ill try updating it through kies first. Again thank you, ill keep you updated on what happens.
RamblingIdiot said:
Thank you everyone. I will try these things later today. Like I said the only things I've personally done to it are root and unlock. I dunno what happened and its possible it could be hardware, but ill try updating it through kies first. Again thank you, ill keep you updated on what happens.
Click to expand...
Click to collapse
Hi,
If the problem is solved for you please edit the title in the OP and add [SOLVED] to it
10x
Ok Guys/Gals, I'm stumped...
Followed the instructions. Mini Kies on computer that works with it (windows vista 32 bit), waited til kies told me to plug in the device. I did. Drivers installed. I waited. And waited. And waited. And waited a bit more. Then it pops up for me to enter a pattern. No pattern had been established with that phone before. So I set one up on the phone, and redid all that, thinking that's all I had to do. Asked me for the pattern again, I put it in.
Here are the steps i'm taking.
Mini kies asks me to plug in my phone.
I do it (this is the phone in the thread, not my actual phone).
And I wait. A while, actually. Somewhere in the line of 1-5 minutes.
And now i get a little popup. "Pattern" the header reads. "The mobile phone is locked. To connect, use the mouse to enter the pattern as specified by the mobile phone." Followed by the pattern unlocker.
I place the pattern i created on the phone in to the one on the computer. It must not be right (as there was none to begin with, and i had to create new and redo this whole step) because now it reads:
Firmware version: device cannot be upgraded
Firmware upgrade: (this is a blank nothingness)
Agh, don't get me wrong, i love this stuff, but after dealing with a defaulty U-scan computer all day (i am a cashier...), computers are not on my good list.
Please help ?
Ok, so after hours of crying, moaning, cursing, yelling at the phone, cursing SD cards for being so small, cursing the better phone for being more retarded than it's cheapo brother the Prevail, I fixed it.
I was so frustrated, i reset everything, again. Still wouldn't work with kies. Checked everything. Made sure I was doing everything right. Googled every last letter i could find about my issue.
I wanted to throw the phone, but instead, i took the battery out, the sim card out, and the SD card out, and cursed each and every one of them out. Before I continue, let me say, that I'd done this before, for approximately the same time, if not longer. Then, i threatened their inanimate lives and put them back, and tried to do the kies update. Turned on the phone, not expecting any miracle of any sort. Suddenly the phone's alive with all sorts of missed calls and texts and who knows what else. So while the phone is no longer rooted, it's still unlocked, and works like a dream again.
TL;DR version? Took the battery, sim, and SD card out for a while. Even though I'd done this as the first thing i did when this issue started happening, perhaps yelling at them made the difference.
Thank you all for putting up with me and my rambling idiocy.
Awesome, glad you got it working again. Maybe we need to put "threatening sdcard/SIM card" methods into the wiki...
stephen_w said:
Awesome, glad you got it working again. Maybe we need to put "threatening sdcard/SIM card" methods into the wiki...
Click to expand...
Click to collapse
Stephen
I threaten my phone with a trip to the recycling yard all the time. It works.
And to the OP glad you got it figured out. A few people with the imie issue have used the pull battery wait ten approach and it seems to work.
Glad you fixed it.
I strongly suggest you make a copy of your efs folder in case you have an IMEI issue again. I keep a copy of my efs folder on my external sdcard and my PC.
I wanted to see if I can post something without getting ridiculed. I know that I should probably just put up with the few crashes that are happening, cause its the greatest phone in the world, puts my previous iPhone3GS to absolute shame, and I LOVED that Phone, and turns out I like showstock too . I usually keep things /prefer stock all the way just rooted but I couldnt be and be at 2.3.6. I want to get some clarification on couplethings.
I am on my second ATT SGS2. First one had a GPS issue. Tried everything and finally convinced ATT warranty that the problem was hardware. They said they would advance replace the handset. So I got it back to stock in every way except the flash counter,this was in December so long before I was aware of mobile odin. Flash counter was at about 12 when I was done trying different ROMs,mostly just try to get the GPS to work. Has anyone ever heard of someone getting charged on a return phone that had a flash counter above stock? Ill update, I seriously doubt I have anything to worry about but, just wondered.
My real question, does everyones SGH-I777 crash on occasion? If so how often? I so happy with the current code that is running on the phone with the exception that it sometimes sleeps and wont wake up, and sometimes it just plain crashes hard, locks up and has to be hard rebooted. Usually this happens about 1 time a day each the lockup and the forever sleep. I wiped before installing current rom and any before that. The only reason I am not stock is cause I wanted the CKK6, 2.3.6 update to work and to keep root privaledges, but also needed my wifi cause ATT is throttling me down to dial up speeds when I reach 2GB. So wrong. Anyway thats another thread.
Anyway I loaded shostock with siyah kernel 2.6.35.14. after wiped everything including both caches. The GPS is solid now, phone is fast, battery is egh, I keep a charger with me... but it crashes hard from one to three times a day. Locks up playing tunes, or wont wake up with out being plugged in or rebooted by holding down the power button, screen blank whole time. Do I have another defective handset or should I just go back to 2.3.4 and UKH7 or should I just deal with the crashes and should get my ass chewn out for the next 10 posts for banned or asking an absolutely ridiculous, moronic, long winded question?
Thanks for the hours of fun all you code writing types.
Oops I knew I was gonna screw it up and get hazed!!!
I knew Id screw it up. I was so nervous about posting on this site.. lol. I meant to post this in the AT&T Samsung Galaxy S2 Q & A forum and it ended up in this one some how. It does not appear that I can move it to where it should be, so maybe someone will have an answer here, or maybe I will get my head torn off, or maybe one of the nice moderators can move it for me.... Thanks in advance.
Hi guys, I'm having a problem rooting an HTC Aria that I recently acquired, and I'm not sure how to search for my answer. I guess Ill try to explain what happen as best as I know, since some things happened so fast I have no idea exactly what happened. Its also worth mentioning that I have no experience rooting android phones, but I'm not an idiot, so please don't be afraid to help because you think Im gonna be waste of your time.
I used the tool unRevoked with Reflash to inflict the damage. Things seemed to be going great, in fact at one point it even said this was a triumph. Somewhere towards the very end, it looked as if it complained about not finding a file on the sd. It was so fast I couldn't read it because I was looking at the computer at that time. Im not surprised it didn't find the file it was looking for since I had no sd card installed. The tutorial/procedure that I read was very detailed, so detailed that he sometimes took a minute to make sure the reader knew to double click the file to open it, yet there was no mention of absolutely needing an sd card for it to work.
Now when I re-run reflash, when I get to the point where you have to choose HBoot USB, it wont ever let me pick it. It just forces me to pick Fastboot or one of the other ones, spits out several lines of green text that is way too fast to read, then gives you the option to pick HBoot again. It never leaves this menu now, not by way of reflash anyway. I can still unplug and reboot my phone , and operate it like normal, but reflash wont go past that recovery menu. I did a factory reset, that didn't help. I also picked recovery on that menu. I browsed the options, but Im afraid to make another move at this point without some input. If someone could please maybe tell me what happened and how to proceed I would be very grateful.
Thank you
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!