Related
I'm not new to android whatsoever.. I've just returned from an Iphone 4s cause i was missing the openess of android. Now.. i've pulled out my old Nexus S 4g, Updated it to 4.0.4 and i cant get it to connect to my computer for the life of me! tried 4 different cables, 5 different computers, every driver i could find and nothing. I've come to believe this is a software failure... All i need is root and i will be able to sleep at night. Could someone package up .zip to give root and twrp recovery that i could flash through stock recovery? I dont know else i could do to get root... but this problem is becoming quite annoying.
1. There is no way to package a zip to flash through stock recovery since it would have to be signed.
2.For someone who is "not new to android whatsoever" making 2 threads about the same topic 2 minutes apart isn't exactly acting the part.
Try this guide.
Actually you're wrong, On the Epic 4G someone did in fact manage to do so. And yeah since i'm not new to these forums i understand that stuff like this gets overlooked so i made two posts. Cry me a river.
BTW Thanks harb... but that would involve being able to connect to my PC. Which just is not possible right now.
Thats the Android Karma... it happens but a little advice.
If you can't connect to the computer then it might a hardware issue not software.
If getting root was that easy that you just had to flash a zip on stock then everyone would be doing it. And good luck getting root without unlocking your bootloader first. Not to be rude but the problem could possibly be between the computer and the chair.
robogoflow said:
Thats the Android Karma... it happens but a little advice.
If you can't connect to the computer then it might a hardware issue not software.
If getting root was that easy that you just had to flash a zip on stock then everyone would be doing it. And good luck getting root without unlocking your bootloader first. Not to be rude but the problem could possibly be between the computer and the chair.
Click to expand...
Click to collapse
It's ok, not rude. I understand what you are saying... but did you not read what i just said? somebody had accomplished this on the Epic 4G and i'm just trying to find someone who has done it with the NS4G.. I've had 4 Android devices, rooted them all and been here since the beginning. It's not a hardware problem, it connected fine before when it was on gingerbread... i downloaded the OTA ICS then flashed through stock recovery.. but if you read what i said in the first post this problem only occured AFTER updating. This is why i quit using XDA a long time ago, because people just post a bunch of useless information instead of trying to help... The problem is not me my friend, its the damned ICS update, i've read multiple posts all over the interweb w/ people who have had the same problem, yet no resolutions other than bending up the micro usb male piece on my phone which is not the problem as i said it was working fine before i updated. Have tried multiple samsung drivers, pda net, and Android SDK Drivers, multiple Cords from samsung, to htc, to blackberry and palm pre and even a nokia one now. and 5 different computers... so tell me smart guy, what would you do?
grumpySasquatch said:
It's ok, not rude. I understand what you are saying... but did you not read what i just said? somebody had accomplished this on the Epic 4G and i'm just trying to find someone who has done it with the NS4G.. I've had 4 Android devices, rooted them all and been here since the beginning. It's not a hardware problem, it connected fine before when it was on gingerbread... i downloaded the OTA ICS then flashed through stock recovery.. but if you read what i said in the first post this problem only occured AFTER updating. This is why i quit using XDA a long time ago, because people just post a bunch of useless information instead of trying to help... The problem is not me my friend, its the damned ICS update, i've read multiple posts all over the interweb w/ people who have had the same problem, yet no resolutions other than bending up the micro usb male piece on my phone which is not the problem as i said it was working fine before i updated. Have tried multiple samsung drivers, pda net, and Android SDK Drivers, multiple Cords from samsung, to htc, to blackberry and palm pre and even a nokia one now. and 5 different computers... so tell me smart guy, what would you do?
Click to expand...
Click to collapse
Bro... Chill... They're just trying to help you out. There is NO way to to root your NS without a computer (currently. We are not Epic 4G owners here). You said you didn't use your NS since GB, SO during the time in between something could have happened to the hardware. Don't rule that out just yet. Your drivers might also be bad. Is this what migrating to iOS does to people? Makes them snobby and demand fixes to problems they can't figure out on their own? Don't hate on the XDA forums. If we're not helping you "hit the thanks button anyways, you ungrateful bastard" (XDA into video ). Anywho. Chill. Keep trying.
Nexus S (GSM i9020a)
Paranoid (14.a Hybrid - 4.0.4)
Matrix Kernel (CFS - 20.0)
Intellidemmand (800/100)
Live OC (105 - 800/1000)
Deep Idle (On - Noop)
BLX - 96 (Inverted Apps)
I am chill, i am just trying to describe what I've already done so maybe someone could suggest something else. And no what i meant is i downloaded the OTA on my computer than transferred it onto my Nexus through USB mount a couple of days ago so i know its not a hardware issue. Im not demanding fixes, just trying to see if anyone has done been able to figure this out yet as i know im not the only one with this issue. And there is a big problem w/ people on the XDA forums as a whole.. i am a little frustrated and just dont like when someone is telling me is a User issue when i have tried everything conceivable and know what i am doing.. Sorry if this offended you. and IOS is a good device.. its just like.. NWO they want to control everything haha. I'd rather be part of the rebel faction. even though i love my ipad XD
There is currently no way to root 4.0.4 without an unlocked bootloader (and no custom recovery), and the only way to get an unlocked bootloader is to either have root or plug it into the PC and unlock via fastboot. As such, you are stuck with sorting out drivers - despite how annoying they are.
The video i linked to above describes in detail (and through video) exactly how to sort out NS drivers on Windows machines as well as the required fastboot commands to get a custom recovery.
Harbb said:
The video i linked to above describes in detail (and through video) exactly how to sort out NS drivers on Windows machines as well as the required fastboot commands to get a custom recovery.
Click to expand...
Click to collapse
Yes that is a good video, and does a job well done in describing on how to install drivers. My main issue is that my Computer(s) are'nt recognized my device at all... It doesn't show up as android device, or nexus s... but Unknown device. If i could figure this out i believe i could handle the rest.
grumpySasquatch said:
Yes that is a good video, and does a job well done in describing on how to install drivers. My main issue is that my Computer(s) are'nt recognized my device at all... It doesn't show up as android device, or nexus s... but Unknown device. If i could figure this out i believe i could handle the rest.
Click to expand...
Click to collapse
Pretty sure that video describes that. You need to open up device manager, double click unknown device (while device is in fastboot), hit update driver and navigate to the provided drivers on the site. Watch it a few times, you'll figure it out.
Have you tried to install PDANet? I've read numerous times about it working wonders for users who have trouble with drivers. It has all of the necessary drivers built in.
Sent from my Nexus S using xda premium
d_phekt said:
Have you tried to install PDANet? I've read numerous times about it working wonders for users who have trouble with drivers. It has all of the necessary drivers built in.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
yes i second that,PDANet Drivers usually work across all devices you should try them.
Like ppl said before, try PdaNet drivers it might help.
thanks everyone, , but like i said i tried pretty much every driver you can find online. they will not install as my device comes up as "Unknown", i've literally tried every piece of literature on the web relating to this issue... at this point i'm just going to wait for the JB update and see what happens.
grumpySasquatch said:
It's ok, not rude. I understand what you are saying... but did you not read what i just said? somebody had accomplished this on the Epic 4G and i'm just trying to find someone who has done it with the NS4G.. I've had 4 Android devices, rooted them all and been here since the beginning. It's not a hardware problem, it connected fine before when it was on gingerbread... i downloaded the OTA ICS then flashed through stock recovery.. but if you read what i said in the first post this problem only occured AFTER updating. This is why i quit using XDA a long time ago, because people just post a bunch of useless information instead of trying to help... The problem is not me my friend, its the damned ICS update, i've read multiple posts all over the interweb w/ people who have had the same problem, yet no resolutions other than bending up the micro usb male piece on my phone which is not the problem as i said it was working fine before i updated. Have tried multiple samsung drivers, pda net, and Android SDK Drivers, multiple Cords from samsung, to htc, to blackberry and palm pre and even a nokia one now. and 5 different computers... so tell me smart guy, what would you do?
Click to expand...
Click to collapse
So the ICS update makes you unable to boot to fastboot and makes your device unable to be recognized by your computer from there?
That's a new one. As far as I know, "Unknown device" is actually your device being recognized, just the driver doesn't get installed correctly.
Have you tried manually specifying which driver to install and selecting the PDA Net driver? Look at Harbb's last post.
Have you went as far as editing the drivers inf to match your hardware ID? I know I had to do that way back when the PDA net drivers weren't even available.
'til then, user error.
polobunny said:
Have you tried manually specifying which driver to install and selecting the PDA Net driver? Look at Harbb's last post.
Have you went as far as editing the drivers inf to match your hardware ID? I know I had to do that way back when the PDA net drivers weren't even available.
'til then, user error.
Click to expand...
Click to collapse
I swear you people don't listen, look i did everything in the video exact when i try to manually specify the driver it comes back saying that the folder you specified doesn't contain a compatible driver for your device... I'm not an imbecile and know how to follow instructions on a video. I know most people skip research cause they're too lazy to figure it out themselves... i posted on here as a last resort and feel like people are telling me what i already know then telling me its my fault, ridiculous. if you guys are just going to repeat what the last five people have said instead of trying to offer a new soloution then why even bother posting?
Epic 4G could do this in FROYO... It was patched by google in 2.3+. Do you want an app to secretly root you and install malware?
Sent from my Samsung Epic 4G using Tapatalk 2
grumpySasquatch said:
I swear you people don't listen, look i did everything in the video exact when i try to manually specify the driver it comes back saying that the folder you specified doesn't contain a compatible driver for your device... I'm not an imbecile and know how to follow instructions on a video. I know most people skip research cause they're too lazy to figure it out themselves... i posted on here as a last resort and feel like people are telling me what i already know then telling me its my fault, ridiculous. if you guys are just going to repeat what the last five people have said instead of trying to offer a new soloution then why even bother posting?
Click to expand...
Click to collapse
Well it is going to be basically one of two things.
1. Is user error of some sort. That is what people have been trying to help with.
2. Is hardware issue that no one can help you with of course. Or some software issue causing it to not show up for who knows what reason. Neither of which folks can help with since a computer is not seeing it. So they revert back to what they can. Point 1
When you asked a question like is there a zip that you can flash in stock recovery to give you root or custom recovery that also doesn't help your cause for people assuming user error.
The one other thing you can try is download mode and Odin.
grumpySasquatch said:
I swear you people don't listen, look i did everything in the video exact when i try to manually specify the driver it comes back saying that the folder you specified doesn't contain a compatible driver for your device... I'm not an imbecile and know how to follow instructions on a video. I know most people skip research cause they're too lazy to figure it out themselves... i posted on here as a last resort and feel like people are telling me what i already know then telling me its my fault, ridiculous. if you guys are just going to repeat what the last five people have said instead of trying to offer a new soloution then why even bother posting?
Click to expand...
Click to collapse
Cool. Trash your Nexus S, clearly broken.
Edit: That's nice of you albundy, but Mr grumpySasquatch (fitting name eh?) has tried everything, including modding the drivers inf. His Nexus S is broken beyond repair, also the first one we've ever seen that won't adb but works fine for USB mounting. *chuckle*
I hear people referring to IMEI and that may lose it of they flash a custom ROM? What does this to refer to and what are the implications?
Thank you -
IMEI
If you flash a non TW ROM you could lose your IMEI, which allows you to log on to the Verizon network. If it gets borked you'll have to restore a back-up or try to restore from the IMEI number in the battery compartment. There are a couple of great threads on hot to do it. Just Search. I just backed-up mine and it was really easy. Don't forget to thank the DEV. They are amazing. If i could have children I would want one of there's.
Jothen2002 said:
I hear people referring to IMEI and that may lose it of they flash a custom ROM? What does this to refer to and what are the implications?
Thank you -
Click to expand...
Click to collapse
You can lose it with a TW rom as well.
Sent from my SCH-I535 using xda app-developers app
Consider the IMEI as a serial number of sorts that's unique to your device (though not necessarily true) so that it can identify itself to the network through the sim card. Also consider that it can be corrupted and removed for many unknown reasons at this time.
Moral of the story: Back it up before making any changes to the phone.
This method backs it up from stock while your IMEI is still intact: http://rootzwiki.com/topic/32397-tutorial-imei-backup-nv-with-qpst-us-variants/
This method with attempt to repair said IMEI when it's gone south/missing: http://forum.xda-developers.com/showthread.php?t=1802024
tu3218 said:
You can lose it with a TW rom as well.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Actually if you're on stock rom/kernel then you don't have to worry about randomly losing your IMEI. It only seems to occur when flashing or running a custom kernel. This means a custom touchwiz kernel can cause it.
Some people are saying its not a preventable issue. I'm sure I'm not alone in thinking that's unacceptable. I'm hopeful one of the many smart devs working on this phone can figure it out. This phone has overcome too much to be gimped by an issue like this. The IMEI issue essentially makes running custom kernels impractical for people who cannot afford to lose their phone's basic functions; it can happen at any given time.
I'll continue to hope that since this issue exists across all carrier editions it will be solved.
Div033 said:
Actually if you're on stock rom/kernel then you don't have to worry about randomly losing your IMEI. It only seems to occur when flashing or running a custom kernel. This means a custom touchwiz kernel can cause it.
Some people are saying its not a preventable issue. I'm sure I'm not alone in thinking that's unacceptable. I'm hopeful one of the many smart devs working on this phone can figure it out. This phone has overcome too much to be gimped by an issue like this. The IMEI issue essentially makes running custom kernels impractical for people who cannot afford to lose their phone's basic functions; it can happen at any given time.
I'll continue to hope that since this issue exists across all carrier editions it will be solved.
Click to expand...
Click to collapse
First of all thanks for sharing...
So I have already installed a custom rom ( currently synergy r39) and a custom kernel imoseyon 0.2.2...
So I better go make a back up ASAP ...
I lost mine once while running an unofficial cm nightly. I flashed it and everything worked fine. Then I restarted the phone and I lost my imei. It was a pretty quick fix because I backed up efs.bin file. I then used the qualcomm tool to restore the imei and then I pushed the efs.bin backup over the current one. I then reflashed that cm nightly again and I was working again. It took about 25 min. The only downside is if this happens and you don't have a computer you can't use your phone till you get to one.
Best thing is to not panic and check the threads here. It's an easy fix. I wouldn't be worried.
Sent from my SCH-I535 using xda premium
Div033 said:
Some people are saying its not a preventable issue. I'm sure I'm not alone in thinking that's unacceptable. I'm hopeful one of the many smart devs working on this phone can figure it out. This phone has overcome too much to be gimped by an issue like this. The IMEI issue essentially makes running custom kernels impractical for people who cannot afford to lose their phone's basic functions; it can happen at any given time.
I'll continue to hope that since this issue exists across all carrier editions it will be solved.
Click to expand...
Click to collapse
+ 1
This issue has pretty much scared me away from flashing. The set up I have going is working, so I'm hesitant to take nightlies for a test drive and increase my chances of being without a phone until I can cuss enough to get it fixed.
Sent from an overpriced Verizon tower.
I'm curious if the AT&T or Sprint Galaxy S III owners are seeing this IMEI issue much, as well.
- ooofest
ooofest said:
I'm curious if the AT&T or Sprint Galaxy S III owners are seeing this IMEI issue much, as well.
- ooofest
Click to expand...
Click to collapse
All variants are.
Sent from my SCH-I535 using xda premium
ruben8448 said:
I lost mine once while running an unofficial cm nightly. I flashed it and everything worked fine. Then I restarted the phone and I lost my imei. It was a pretty quick fix because I backed up efs.bin file. I then used the qualcomm tool to restore the imei and then I pushed the efs.bin backup over the current one. I then reflashed that cm nightly again and I was working again. It took about 25 min. The only downside is if this happens and you don't have a computer you can't use your phone till you get to one.
Best thing is to not panic and check the threads here. It's an easy fix. I wouldn't be worried.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Had a couple questions for you as I'm running the CM10 alpha and about to move to the nightlies. Is there any advantage to backing up the efs.bin file as opposed to creating the QCN file that is described in the IMEI backup threads? Can you use QPST to backup the efs.bin? It sounds like its better to have both than just the QCN file. Sorry I don't know what exactly the efs.bin file is so apologies if I'm not making sense.
Thanks!
xsteven77x said:
All variants are.
Click to expand...
Click to collapse
Yeah, I have been getting that impression from reading around since my post.
I'm not going beyond root for this phone until something more definitive to prevent the IMEI issue can be found.
I must have flashed ROMs on my Incredible hundreds of times, quite casually, and it seems best to avoid the problems we're seeing with people who have attempted to restore their identifier and still have roaming indicator showing, etc.
- ooofest
There isn't a thread for this for our phone, so I thought I would make one seeing as i've tried it. A program called mobile odin https://play.google.com/store/apps/details?id=eu.chainfire.mobileodin.pro&feature=nav_result Will allow you to run odin from your device without connecting it to your computer. Its super simple to use and it works pretty well. My charging port is hosed so I can't connect it anyways. I was on ICS and needed to go back to GB. Had to use this app and got back on GB no problem. I don't see a free version of the app anywhere so depending on how much you use odin, 5 bucks might be a good investment.
Hmm I ran the program and sent the logs a few months ago and never heard anything back to get our device supported and still doesn't say it supports this device.
It takes 30 minutes to run the system dump to find out our device isn't compatible......after running the dump....and to find out it wouldn't work
Its not worth the hassle when you've only got 15 minutes to get the refund.
I'd like to see screenshots or something to show that this actually does officially work on our device ....considering its not on the list of compatible devices.
Thanks
I guess after 2 days without a response ....there's not going to be one?
To bad I was hoping that it was going to be worth the money
Too bad I'm stuck on ics as well got excited when I started reading this thread.
Sent from my SGH-T959V using xda app-developers app
??? Anything???
Or is this just a bogus post....and in the wrong section....should have went in themes and apps
A search would show that XDA members gets a lite version as with lots of other apps for free.
http://forum.xda-developers.com/showthread.php?t=1347899
Ive run it.....it generates a dump file (mobileodin.txt) that you send in and hope that he incorperates your device in the next update .....and since it does this ...it basically is not suported as of yet.
So the op is saying it works.....but in fact it doesnt.
I would like to see some evidence that it works for him and like to know how it does on his device and not on mine.
Also with the lite version you have to dl a flash kernal specific to your device from that same thread....but since our device is not suported...you wont find one.
Y'all should do alot more reading before posting links to something that doesnt suport our device.
i did read that thread thuroughly....very thuroughly,even flashed a few flash kernals he added that were for the other models similar to ours in great hopes of getting this to work.
This is what you get....it does take about 30 minutes to generate the text file to send in
Oh magda623....are you there?
we are awaiting your reply.
Im sure there is hundreds of us that would like to have this running on our phones...please let us know how to make it work.
Ok ok i give up on magda to humor us on how it works on his device.
I urge everyone to use the link a couple posts up and dl the mobile odin lite,run it and send your mobileodin.txt to chainfire and plead with him to include our device....im sure he will eventually get our message.....after all he does say he is only working on samsung devices at this time.
****wouldnt it be awsome to flash back and forth from mtd to bml roms without ever having hook up to your comp!!!****
Lol am i seriously the only one that finds this to be something that would make life amazing on the sgs4g?
new ealsjur
Mobile ODIN did not recognize the device when I was on CM9
Something about flashing the phone from the phones makes me uneasy. What if you need to repartition using a pit or something, while the phone is on and in use.
Btw short I sent a dump file a long time ago and have been retrying ever since with no luck so far, maybe I'll make another dump today after work
Sent from my SGH-T959V using Tapatalk 2
getochkn said:
Something about flashing the phone from the phones makes me uneasy...
Click to expand...
Click to collapse
I've stayed out of this one for just that reason. It's bad enough to be messing with the underpinnings of an OS when you don't have true single-user mode, a "safe" boot, kernel, and emergency filesystem available, nor alternate boot media if things go really bad. Doing all that from user-land while the system is running all services sounds like just asking for trouble.
You can do most of what you are asking for in Recovery
Flash kernel/boot/recovery
Flash /system
Flash other run-time partitions
Flash modem
If you can't get into recovery, are you really able to run some Android program?
I'm not really seeing the need for this, except for people who have broken their USB connector and can't connect to a computer. Even then, when would you need ODIN? When things are so hozed up you need to start from scratch, yes, but if you have a broken USB, what are you doing flashing risky things?
If someone can show what this would do that you can't do in recovery, as well as a meaningful use case for it, I'll mull over how to do it. Basically, if an app can do it, a script in recovery sure should be able to as well.
I tend to think the reason we dont have support is because of the quirkiness of this phone.
I agree eollie ....I gave up on this a while ago...really it doesn't matter to me anyhow....I mostly thought it was a great idea.
I don't tend to have issues with flashing...or recovering.
And even if I did....I wouldn't be dumb enough to post here lmao.
I have tried a few custom roms and then when I reflash back to any of the 3 stock roms floating out there for the GS3 Verizon my Google Play Store remains permanently broken. Alogcat indicates that it is getting back an unexpected response code 400 from google. I suspect this may mean that it fails to update because SSL is broken in some way but I could be wrong.
I have done all the normal things one does to bring back the market such as clearing the data on Google Play and services framework and rebooting, but that has no positive effect. Nor does deleting my account and re-adding it or creating a new account. Also Google+ will say "No Connection" but once I close out of it and reopen it, it will always log in to my account automatically without error. I will say that the error is reminiscent of the kind of error you would expect if your time is wrong, but it is correct. Any help will be appreciated it..
Go post in Q&A Forum.
iSheep... iSheep... Meowww that's Apple
This does not belong in development.
Sent from my Galaxy SIII
considering that out of all the roms I have tried Play now only works in one of the many roms posted here.. I feel like it is connected.
http://goo.im/devs/invisiblek/i535/roms/cm10.unofficial.nightlies build 20121005 is the only rom I can flash on my device now and having a working Google Play but I absolutely hate this rom. It has bugs, it lacks polish.. yet it also seems as if it screwed up Play in some way on my device... so please install this rom and tell me I should be posting somewhere else.. where everyone only discusses the usual methods of fixing Play and no one takes any real steps to really debug the problem to get to the root of it.
glitchbit said:
considering that out of all the roms I have tried Play now only works in one of the many roms posted here.. I feel like it is connected.
http://goo.im/devs/invisiblek/i535/roms/cm10.unofficial.nightlies build 20121005 is the only rom I can flash on my device now and having a working Google Play but I absolutely hate this rom. It has bugs, it lacks polish.. yet it also seems as if it screwed up Play in some way on my device... so please install this rom and tell me I should be posting somewhere else.. where everyone only discusses the usual methods of fixing Play and no one takes any real steps to really debug the problem to get to the root of it.
Click to expand...
Click to collapse
Doesn't matter if you have the issue on every rom it doesn't belong in the development section. Take the real step of posting this in the proper section.
Sent from my Galaxy SIII
I would have to agree seems like the good place to post it since we are all flashing roms and they bare having this issue... I was pleased to see this here as in have been having this issue on synergy 74 and up and now I see it's others so now all the developers will be aware of what's going on and maybe find a fix
Sent from my SCH-I535 using xda app-developers app
READ FORUM RULES BEFORE POSTING
Development is for Developers to post threads
Questions go in Q&A
Thread moved
Moderator
I love how people comment in a thread telling you that you posted in the wrong section, but don't offer up any advice.
I don't know a whole lot about your issue, but instead of flashing a stock rom maybe you could odin back to stock, accept OTA, and start over?
Not sure if that would clear up your issue, but hope I helped...!
josh995 said:
I love how people comment in a thread telling you that you posted in the wrong section, but don't offer up any advice.
I don't know a whole lot about your issue, but instead of flashing a stock rom maybe you could odin back to stock, accept OTA, and start over?
Not sure if that would clear up your issue, but hope I helped...!
Click to expand...
Click to collapse
Thanks Josh, but yea I have been flashing back to stock via Odin a lot, more times than I can count now! I've been using the HOME_I535VRALF2_I535VZWALF2_618049_REV09_user_low_ship.tar.md5 image file but Kies says it is the most recent as well so there is no newer OTA to come down. I've also tried LG and HD roms via Odin, but regardless the Google Play Store remains broken. I am positive that I have restored everything back to its original configuration as per multiple guides on the subject. It is extremely frustrating as I have spent countless hours now trying to fix this one issue. I've spent more time researching this issue on google, in the forums and irc chat rooms and speaking with more devs than what those people would care to know about. There is a serious issue here that is being ignored.
I develop iPhone apps, I do IT support, and network infrastructure for a large manufacturer and I always get a great deal of enjoyment figuring things out but something like this, which should be so simple and just work, ticks me off to no end. For me this just creates the case in point why it makes it difficult for me to care much for the Android platform as a whole. It still has a lot of growing up to do before it catches up with iOS. I use a phone to get from point A to point B and I expect a certain baseline level of performance and things to just work. I left the platform 2 years ago and from the outside it looked as though things have been improving, but I can see now that not much has changed in the OS or community and the platform isn't ready for much of anything beyond a tablet for me personally as it is just a no go as a phone OS.
I would really like to figure this out still.. so to the first person who can give me the resolution or help me significantly in some way I will gift $50 to you over paypal.
Arriving at a solution
glitchbit said:
I would really like to figure this out still.. so to the first person who can give me the resolution or help me significantly in some way I will gift $50 to you over paypal.
Click to expand...
Click to collapse
Well, you don't seem to be flashing a Base ROM using Odin. It being broken like that usually indicates DPI issues, which are carrying across ROMs.
1. Is your phone encrypted? (Do a reset and Erase everything from within, that should fix it) Settings > Backup and Reset > Reset
2. Is the ROM you are flashing using Odin a Base FW?
I had this happen on an old incredible. What it turned out being was that my phone wasn't activated. I don't think that is your problem because it sounds like you use it, but could be a corrupted area of the phone that flashing doesn't touch. I don't think its a ROM because I've flashed them all and my market has always worked.
I would try a couple things to see if either helps. First, Odin back to stock then turn you phone off pull the sim card, boot back up and let it settle, power off put the sim back in and power up. Second, if that doesn't work dial *2767*3855# to repo vision your phone, but this factory resets and people say it erases your internal SD card so back that up. Hope one of those help.
Also if neither of those work, try a new sim card. That seems to fix 90% of peoples problems on this phone.
Sent from my S3 running Eclipse 2.1
kintwofan said:
I had this happen on an old incredible. What it turned out being was that my phone wasn't activated. I don't think that is your problem because it sounds like you use it, but could be a corrupted area of the phone that flashing doesn't touch. I don't think its a ROM because I've flashed them all and my market has always worked.
I would try a couple things to see if either helps. First, Odin back to stock then turn you phone off pull the sim card, boot back up and let it settle, power off put the sim back in and power up. Second, if that doesn't work dial *2767*3855# to repo vision your phone, but this factory resets and people say it erases your internal SD card so back that up. Hope one of those help.
Sent from my S3 running Eclipse 2.1
Click to expand...
Click to collapse
kintwofan, you may be on to something. I have flashed the 3 base roms for my phone G7, LG, and HD to no avail. I actually use this phone on another carrier and so I have manually programmed this phone myself. So there may be something regarding the activation that is causing this issue.
glitchbit said:
kintwofan, you may be on to something. I have flashed the 3 base roms for my phone G7, LG, and HD to no avail. I actually use this phone on another carrier and so I have manually programmed this phone myself. So there may be something regarding the activation that is causing this issue.
Click to expand...
Click to collapse
Sounds like may need a buildprop change. Try changing buildprop to your carrier. Although one of my rezounds is on Tmobile without problems. Using T-mobile APN. S3 should auto add the APN. At least it does with international sim.
Use market enabler then to see if you can tell it your carrier. I'm sure you can Google the apk
You could also still do the reprovision, but I'm sure you'll have to reprogram it.
Sent from my S3 running Eclipse 2.1
Market enabler didn't work on synergy 74
Sent from my SCH-I535 using xda app-developers app
GREGHARKINS said:
Market enabler didn't work on synergy 74
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I assume you're on Verizon so did you try the other suggestion I posted? I used to run synergy with no problem so I would assume something got corrupted on your phone in a segment that isn't flashed.
Sent from my S3 running Eclipse 2.1
OTA attempts to activate this phone on the carrier fails, hence the manual programming. I have tried market enabler and and market unlock but they fail to work in the stock roms and the synergyrom. The only rom that has a working Market/Play is http://goo.im/devs/invisiblek/i535/roms/cm10.unofficial.nightlies I specifically used 1005 and 1012 and they both work fine.
I don't know what he does differently but it works for whatever reason.. http://forum.xda-developers.com/showthread.php?t=1788443
I just don't really care for the rom, it seems like my reception and wifi has issues on it vs the stock.
glitchbit said:
OTA attempts to activate this phone on the carrier fails, hence the manual programming. I have tried market enabler and and market unlock but they fail to work in the stock roms and the synergyrom. The only rom that has a working Market/Play is http://goo.im/devs/invisiblek/i535/roms/cm10.unofficial.nightlies I specifically used 1005 and 1012 and they both work fine.
I don't know what he does differently but it works for whatever reason.. http://forum.xda-developers.com/showthread.php?t=1788443
I just don't really care for the rom, it seems like my reception and wifi has issues on it vs the stock.
Click to expand...
Click to collapse
Interesting, so the reprovision didn't work? Have you tried just pulling the play store from his gapps? Also, you could try his jellywiz ROM maybe he did the same thing to it were your play works, if you like touchwiz. I guess you could also upload the build.prop from that working ROM and I'll compare it to mine when I get time and see if I notice any major differences.
By the way have you tried Eclipse ROM, its very nice and bug free.
Sent from my S3 running Eclipse 2.1
Still looks probably to be a buildprop vs carrier change issue. CM is built off source and works and the TW roms are built off different carrier bases and don't work. Playstore looks at the buildprop.
Hi
I have 822 got it from ebay
the issue is it turns off itself many times
everytime that happens i can say the phone was in idle mode and screen turned off.
i saw its a lumia wide complaint , is there a fix , i have tried all the button tweaks as well as downgraded the firmware too , to no avail.
sending back is no option obviously
what should i do
Guys I could really use some help here.
Thanks
Sent from my SCH-R950 using Tapatalk 2
lord dredd said:
Guys I could really use some help here.
Thanks
Sent from my SCH-R950 using Tapatalk 2
Click to expand...
Click to collapse
About the only thing I could say is hard reset your phone, but you lose everything. If you have access to it, you may try using the Nokia Care Suite and download the newest ROM available for your phone and trying a factory recovery with that. You will also lose everything that way.
Other than that I can't really say. I'm having a hard enough time getting help with my 820. Everyone kind of skipped the 820 (and it's variants) and went straight for the 920. This forum doesn't really get a whole lot of activity, as you have probably been able to tell. You may try looking for suggestions in the 920 forum. Something similar will likely be around in there. They are quite active, though they may just tell you to come post in here lol.
darthcircuit said:
About the only thing I could say is hard reset your phone, but you lose everything. If you have access to it, you may try using the Nokia Care Suite and download the newest ROM available for your phone and trying a factory recovery with that. You will also lose everything that way.
Other than that I can't really say. I'm having a hard enough time getting help with my 820. Everyone kind of skipped the 820 (and it's variants) and went straight for the 920. This forum doesn't really get a whole lot of activity, as you have probably been able to tell. You may try looking for suggestions in the 920 forum. Something similar will likely be around in there. They are quite active, though they may just tell you to come post in here lol.
Click to expand...
Click to collapse
Thanks mate but i have done hard reset like 10 times already.
Flashed older firmware, then updated.
Flashed newest firmware as well.
Kept it stock without adding app and not using any wifi but to no avail.
Vzn forums say nokia knows about this and they are working for a fix.
But I don't think they can do anything, it's a widespread issue with many windows phone, just goes to show window mobile still has a long way to go
Sent from my SCH-R950 using Tapatalk 2