My droid incredible has been having some major problems with any GPS-related functions when flashing to custom ROMs. I've tried CM7, OMGB, OMFGB, and MIUI so far. The GPS worked great in OMGB and OMFGB after updating the radio, but when I tried this on CM7 and MIUI (both of which seemed much smoother and refined), no dice. I've also tried completely reflashing the rom (yes, I did wipe data, cache, and dalvik cache), uninstalling WeatherBug, flashing 4 different radios (4.08, 11.19, 5.02 and 5.06) as well as reflashing the original stock 7.28 radio, and even tried that fix through a sense rom where you dial some ## number and then enter some MSL number. That didn't seem to work for me, the call didn't even go through. No matter what I try, I can't seem to get GPS to work on either of the custom ROMs that I love. Major bummer, because I used GPS daily on stock 2.2 Froyo before rooting my phone. I'd appreciate any help at all on this issue and I really would like to get my phone's GPS functionality working again.
P.S. - I've already spent countless hours searching XDA as well as other forums about this issue, and the above list of troubleshooting steps is what I've come up with so far. Please don't lecture me with a useless response such as "Use the search function" as I have already done so. Thanks
Seems like you've done your research. Have you tried an app titled "GPS Status & Toolbox" in the market?
Just tried that app but no luck. I tried clearing the current GPS settings and then downloading new ones. Anything I'm missing?
I only saw mention of AOSP roms, did you try using *228 on a Sense rom? I'm not sure if there's a difference performing this on an AOSP rom but I recall folks saying to do that on a Sense rom. As you stated, GPS worked on two roms just not MIUI or CM7, which is weird. Have you returned to or are you currently using OMGB and OMFGB and retained your ability to use gps? I'm trying to rule out this being a hardware issue since you noted GPS failed on two of four roms.
SlimSnoopOS said:
I only saw mention of AOSP roms, did you try using *228 on a Sense rom? I'm not sure if there's a difference performing this on an AOSP rom but I recall folks saying to do that on a Sense rom. As you stated, GPS worked on two roms just not MIUI or CM7, which is weird. Have you returned to or are you currently using OMGB and OMFGB and retained your ability to use gps? I'm trying to rule out this being a hardware issue since you noted GPS failed on two of four roms.
Click to expand...
Click to collapse
Just reflashed OMFGB, and now GPS DOESN'T work?!?!?!?!? I've tried everything all over again, format SD card, reflash radio, I'm clueless.
Do you recall performing anything on your phone that may have messed with the gps? Do you restore system data at all with something like Titanium? My only other suggestion is to flash rmk40's gingerbread leak found here:
http://forum.xda-developers.com/showthread.php?t=1087077
The reason I'm suggesting is due to the 3G drop issue that people have fixed by flashing this. I'm doubtful, but maybe this could resolve the gps issue as well? Aside from this, I'm hoping another XDA member has suggestions/solution as it looks like hardware failure if you do not recall anything odd that caused the gps issues.
SlimSnoopOS said:
Do you recall performing anything on your phone that may have messed with the gps? Do you restore system data at all with something like Titanium? My only other suggestion is to flash rmk40's gingerbread leak found here:
http://forum.xda-developers.com/showthread.php?t=1087077
The reason I'm suggesting is due to the 3G drop issue that people have fixed by flashing this. I'm doubtful, but maybe this could resolve the gps issue as well? Aside from this, I'm hoping another XDA member has suggestions/solution as it looks like hardware failure if you do not recall anything odd that caused the gps issues.
Click to expand...
Click to collapse
I do use Titanium to restore system data. I flashed from CM7 to MIUI and did a batch restore of EVERYTHING, and got a FC on android.process.acore. I reflashed MIUI and the FC problem was fixed, but GPS still did not work. After this I flashed back to OMFGB and even complete stock 2.2 with sense, still no GPS. I will try your suggestion above, however I'm doubting this is a hardware problem as my GPS worked fine before rooting my phone. I'm guessing I screwed up something to do with the software, I just don't know enough about the subject to make an educated guess about what I screwed up. Anyway, I'll try flashing that gingerbread leak and let you know. Thanks for all the help so far guys.
SlimSnoopOS said:
Do you recall performing anything on your phone that may have messed with the gps? Do you restore system data at all with something like Titanium? My only other suggestion is to flash rmk40's gingerbread leak found here:
http://forum.xda-developers.com/showthread.php?t=1087077
The reason I'm suggesting is due to the 3G drop issue that people have fixed by flashing this. I'm doubtful, but maybe this could resolve the gps issue as well? Aside from this, I'm hoping another XDA member has suggestions/solution as it looks like hardware failure if you do not recall anything odd that caused the gps issues.
Click to expand...
Click to collapse
No luck. GPS still is not working.
Aight, well one thing is you are not supposed to backup/restore system data. Idk how deep it affects rom flashes but that is very likely the source of your gps issues. Have you flashed a rom without restoring anything and checking gps? With titanium you are supposed to backup user data. If you ask many dev's, they strongly discourage backing up system data.
1) flash a rom (step 2 is an option within Settings in gingerbread roms, idk about froyo roms)
2) if you want to completely start from scratch Cancel google restore by NOT signing into your google account upon initial setup. Go into Settings>Privacy and uncheck "Back up my settings" as well as "Automatic Restore."
3) sign into your google account and let it sync
4) test your gps
If you always restore system data through Titanium each time you flashed a rom PRIOR TO testing gps, this may have resulted in your problems.
I'd have to agree with slimsnoop, my first flash I made the mistake of restoring system data and everything went crazy wifi freaked, gps, repeated fc's. I'd try flashing then try gps, if its working then i'd restore apps one by one and see if any interfere with the gps. If that doesn't work then i'd go stock, master clear/factory reset and see how that goes make sure EVERYTHING important is backed up to your pc cause it will wipe it clean, if none of that works then i'd leave it stock and take it in for replacement or repair if possible.
Sent from my i897 w/Andromeda 3, Suckerpunch kernel, & 1.3Ghz OC using Tegrak.
SlimSnoopOS said:
Aight, well one thing is you are not supposed to backup/restore system data. Idk how deep it affects rom flashes but that is very likely the source of your gps issues. Have you flashed a rom without restoring anything and checking gps? With titanium you are supposed to backup user data. If you ask many dev's, they strongly discourage backing up system data.
1) flash a rom (step 2 is an option within Settings in gingerbread roms, idk about froyo roms)
2) if you want to completely start from scratch Cancel google restore by NOT signing into your google account upon initial setup. Go into Settings>Privacy and uncheck "Back up my settings" as well as "Automatic Restore."
3) sign into your google account and let it sync
4) test your gps
If you always restore system data through Titanium each time you flashed a rom PRIOR TO testing gps, this may have resulted in your problems.
Click to expand...
Click to collapse
Tried that on Cyanogenmod just now, and I unchecked "backup my settings", however "automatic restore" was checked and greyed out, I couldn't do anything about that one. Also, I had to sign into my google account in order to download maps so I could test it. So if google sync is interfering with the GPS I'm not able to stop it from syncing on a custom rom. Thanks for the suggestion, though.
Jsmokey said:
I'd have to agree with slimsnoop, my first flash I made the mistake of restoring system data and everything went crazy wifi freaked, gps, repeated fc's. I'd try flashing then try gps, if its working then i'd restore apps one by one and see if any interfere with the gps. If that doesn't work then i'd go stock, master clear/factory reset and see how that goes make sure EVERYTHING important is backed up to your pc cause it will wipe it clean, if none of that works then i'd leave it stock and take it in for replacement or repair if possible.
Sent from my i897 w/Andromeda 3, Suckerpunch kernel, & 1.3Ghz OC using Tegrak.
Click to expand...
Click to collapse
I've actually already tried a complete restore back to 2.2, as well as a factory reset once I"m already at stock configuration. I'll try that again tonight if I get a chance. Is there anything you can recommend when retsoring back to factory configuration? any hidden settings I'm missing that have something to do with the radio or GPS or wireless settings?
No the only settings I've found for gps is location for pics and stuff, besides a factory reset should of changed it all back anyways, i'd say its a hardware issue but seeing as two roms were working at one point and not now it kind of seems that maybe something isn't getting erased with factory reset thats catching you up, I'm not sure what the code is for yours but i'd try the actual master clear code. I read somewhere theres a difference between factory reset and master clear not sure if there really is though, and if you can find a secret code list there might be something where you can change the gps sat pool. When I get home tonight I'll do some digging and see if I can't find something to get this working for you
Sent from my i897 w/Andromeda 3, Suckerpunch kernel, & 1.3Ghz OC using Tegrak.
When you install cyanogen, to test maps without signing in, download the gapps package from the cyanogen thread on this forum or on cyanogenmod forums
Sorry, can't provide links. On cell
Sent from my ADR6300 using XDA App
Cryous said:
When you install cyanogen, to test maps without signing in, download the gapps package from the cyanogen thread on this forum or on cyanogenmod forums
Sorry, can't provide links. On cell
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I do use the gapps package. It's also available on rom manager, however when you flash the gapps package it's basically multiple market links that take you to the apps of your choice so you can download the latest version. This requires you to sign into the market, which requires you to sign in to your google account =/
The only other solution I could think of is finding an .apk of the maps app, and doing that manually. I can't imagine that the google sign in is what is interfering with the GPS though. I'll try Jsmokey's suggestion and search for a master reset code, maybe that'll do the trick for me. If i'm flashing to the stock config the maps app is already included anyway. Thanks for the idea though.
Jsmokey said:
No the only settings I've found for gps is location for pics and stuff, besides a factory reset should of changed it all back anyways, i'd say its a hardware issue but seeing as two roms were working at one point and not now it kind of seems that maybe something isn't getting erased with factory reset thats catching you up, I'm not sure what the code is for yours but i'd try the actual master clear code. I read somewhere theres a difference between factory reset and master clear not sure if there really is though, and if you can find a secret code list there might be something where you can change the gps sat pool. When I get home tonight I'll do some digging and see if I can't find something to get this working for you
Sent from my i897 w/Andromeda 3, Suckerpunch kernel, & 1.3Ghz OC using Tegrak.
Click to expand...
Click to collapse
No luck finding a "master clear code" on Google, but I did find that there is an option for factory reset in the hboot menu. Is this what you're referring to possibly? Also, is this different from the factory reset option in settings>storage while the phone is on?
UPDATE: Just called verizon, apparently they are out of stock of dinc's and are sending me a dinc 2! =D
Anyway, what steps can I take in the future to make sure I DON'T screw up my phone the next time in the first place (besides NOT restoring system data in Titanium)?
snoshreddax21 said:
No luck finding a "master clear code" on Google, but I did find that there is an option for factory reset in the hboot menu. Is this what you're referring to possibly? Also, is this different from the factory reset option in settings>storage while the phone is on?
Click to expand...
Click to collapse
Yeah I wasn't sure if it had a master clear or not some phones do some don't, I can't remember if what you're talking about is different from regular factory reset or not its been a while since I played around with a droid inc. Glad to hear you're getting a replacement and an upgrade at that. Basically do searches for what you can back up and back up everything system related you possibly can, you can't be too prepared when disaster strikes.
Sent from my i897 w/Andromeda 3, Suckerpunch kernel, & 1.3Ghz OC using Tegrak.
Sounds great. I'll probably do a nandroid backup at absolute stock and make sure it's working correctly. Thanks to everybody for all the help.
-snoshreddax21
Do you mean if you call them for a warranty replacement they will send you a dinc2?
Sent from my ADR6300 using XDA App
Glad to be of service! Hopefully things work out on the DInc2 for you.
As far as warranty replacements go, the availability of DInc vs. DInc 2 depends on what they have in stock in your area. At this point, I wouldn't be surprised if more folks received DInc 2's as replacements.
Related
Hey everyone.
I know there's a couple other threads with this problem, but none of them included their last_kmsg files. It took a bunch of tries before I could stay booted up long enough to grab it, but I have one.
I'm getting a significant number of reboots on my EVO. Like almost unusable at times. It seems fairly random, although there's a slight suspicion is has something to do with the GPS. Maps has been a crash-cause before and the most recent bout last night was brought on by foursquare. (the annoying part is I had just used 4sq fine 30 minutes prior with no issues. Then, booted it up, refreshed locations and my phone was unusable for hours.)
I've done all the standard things. Fix permissions, wipe cache, wipe dalvik, wipe data/system, reinstall the latest CM7 build (update-cm-7.0.2.1-Supersonic-signed.zip), wipe cache, wipe dalvik. I entered my google account info but told it not to sync anything. It is now rebooting less than a minute after it starts up. I haven't installed any apps at all since this most recent wipe/reload of CM7. It reboots with and without the sd card installed.
I'm at a loss here and getting incredibly frustrated. Many replies say it's as easy to fix as wipe everything and re-do it. Obviously something abnormal is screwed up on my phone and I can't figure it out.
Here's the pastebin from this morning: pastebin.com/Ki7H8bH3 (Crap, I don't post here enough to be allowed to post links. Just add the http part to that.)
And then when I got awake enough, I did another complete wipe/reload. The rebooting is even worse now, it's taken me almost an hour to get to a point I can install es explorer to try and pull another file. And when I did, it was blank.
Any ideas?
Thanks!
1. Go to the link below and download the PC36IMG.zip file for amon RA v2.3 and place it on the root of your SD card.
http://forum.xda-developers.com/showthread.php?t=705026
2. Shutdown your device.
3. Simultaneously press the DOWN volume button and the power button until your device starts. There will be a short pause and then a few lines of text will scroll across the screen. Afterwards, the bootloader will automatically detect the PC36IMG.zip file and prompt you to install it. Follow the easy prompts to install. Installation will take less than 10 seconds to complete. Afterwards, reboot into your new recovery. Go to the backup/restore menu and make a nandroid backup of your current setup.
4. Now go to the wipe menu and wipe EVERYTHING in it EXCEPT the SD card.
5. Go to the flash menu and flash the rom you desire to flash.
On many occasions, reflashing the recovery solved rebooting issues and hopefully, it will solve yours.
posting & replying via the XDA Premium app.
Hi dougjamal,
Thanks for the reply.
I've made some progress. Last night I had done a majority of what you suggested, with installing amon RA. I've also just formatted my entire sd card just to be sure.
I haven't tried wiping things other than cache and dalvik, so I'll try that.
My progress I mentioned is that I had CM7 up and running until I flashed a new kernel and gapps in there. So I guess I'll just stick with the stock CM7 kernel, try your extra wiping and see how that works.
Thanks!
grifta67 said:
Hi dougjamal,
Thanks for the reply.
I've made some progress. Last night I had done a majority of what you suggested, with installing amon RA. I've also just formatted my entire sd card just to be sure.
I haven't tried wiping things other than cache and dalvik, so I'll try that.
My progress I mentioned is that I had CM7 up and running until I flashed a new kernel and gapps in there. So I guess I'll just stick with the stock CM7 kernel, try your extra wiping and see how that works.
Thanks!
Click to expand...
Click to collapse
You're very welcome. Sorry for the delayed response. I was having a late lunch and then drove home. Anyway, keep us informed of your progress and enjoy the rest of your day.
posting & replying via the XDA Premium app.
No worried on any delay, just glad to have someone that took a read and time to reply!
Ugh, it's the randomness of this that has me so frustrated. I thought I had a good install again, I left it sit on the "touch the android" screen for a few minutes and it stayed on. Made it through the setup process ok. I allowed the setup to "auto-download" a handful of the google apps it asks if you want. Once they got to about 38%... boom, restart.
So I did another toooootal wipe and I'll manually install those apps one by one. We'll see...
dougjamal said:
1. Go to the link below and download the PC36IMG.zip file for amon RA v2.3 and place it on the root of your SD card.
http://forum.xda-developers.com/showthread.php?t=705026
2. Shutdown your device.
3. Simultaneously press the DOWN volume button and the power button until your device starts. There will be a short pause and then a few lines of text will scroll across the screen. Afterwards, the bootloader will automatically detect the PC36IMG.zip file and prompt you to install it. Follow the easy prompts to install. Installation will take less than 10 seconds to complete. Afterwards, reboot into your new recovery. Go to the backup/restore menu and make a nandroid backup of your current setup.
4. Now go to the wipe menu and wipe EVERYTHING in it EXCEPT the SD card.
5. Go to the flash menu and flash the rom you desire to flash.
On many occasions, reflashing the recovery solved rebooting issues and hopefully, it will solve yours.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Seems like this gets posted quite often, huh??? lol
Don't rule out a corrupt download. If you have the time, download both Salvage-Mod 1.2.1 and the gapps zip from http://www.salvage-mod.com/node/4. If you like CM7, you may like Salvage-Mod. It is pure gingerbread. If you decide to flash it, see whether or not you get bootloops with it.
posting & replying via the XDA Premium app.
HipKat said:
Seems like this gets posted quite often, huh??? lol
Click to expand...
Click to collapse
Indeed, my friend...lol...but it works.
posting & replying via the XDA Premium app.
HipKat said:
Seems like this gets posted quite often, huh??? lol
Click to expand...
Click to collapse
It does and it wish it was that easy. It's frustrating to read that others seem to have no issues at all yet when I follow those directions, which are everywhere, nothing seems to work.
dougjamal said:
Don't rule out a corrupt download. If you have the time, download both Salvage-Mod 1.2.1 and the gapps zip from http://www.salvage-mod.com/node/4. If you like CM7, you may like Salvage-Mod. It is pure gingerbread. If you decide to flash it, see whether or not you get bootloops with it.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
I re-downloaded CM7 this morning thinking that might be the issue, but it hasn't seemed to help. I'll give a different rom a try probably, maybe there's something other than CM7 I'd be content with.
Whelp, I downloaded SalvageMod and their gapps. Wiped everything, installed salvage, installed gapps, rebooted.
I got through set-up, was ok for a couple minutes, then as I was going into my contacts to see if they had sync'd yet... reboot.
This makes me think this can't be a ROM issue.
Any other ideas?
Does the same thing happen when you run a stock (or close-to-stock) rom? Main reason I ask is that this might actually be some sort of hardware problem, but one of the best ways to test for that is to be running on stock software. I wouldn't necessarily suggest flashing an RUU to get to the latest official release, but there are stock rooted roms out there that you could try.
You probably went with CM specifically to get away from Sense and the default HTC stuff (that's most people's reasons anyway), but if you flash a stock rom and it's still rebooting like that then I'd say chances are REALLY good that it's hardware and that you'd have grounds for getting a replacement phone (just remember to unroot first.)
And if it stops randomly rebooting on you then you'll have at least narrowed things down a bit.
jesuspgt said:
Does the same thing happen when you run a stock (or close-to-stock) rom? Main reason I ask is that this might actually be some sort of hardware problem, but one of the best ways to test for that is to be running on stock software. I wouldn't necessarily suggest flashing an RUU to get to the latest official release, but there are stock rooted roms out there that you could try.
You probably went with CM specifically to get away from Sense and the default HTC stuff (that's most people's reasons anyway), but if you flash a stock rom and it's still rebooting like that then I'd say chances are REALLY good that it's hardware and that you'd have grounds for getting a replacement phone (just remember to unroot first.)
And if it stops randomly rebooting on you then you'll have at least narrowed things down a bit.
Click to expand...
Click to collapse
Hey jesuspgt,
I haven't tried that yet. I'll look around for a rooted stock ROM later and give that a shot.
My current status is back to uncertainty. At the moment, my evo has been sitting here fine, not rebooting, for the past hour or two. It's still the Salvage ROM I first installed (i.e. I haven't reinstalled it since it rebooted). Now I haven't really used it any, so it might go to hell as soon as I do that, but for now, it's on and only had that one (maybe two, I can't keep track...) initial reboot.
That's what makes it tricky to diagnose. I know using any custom ROM runs the risk of loosing stability and all ROMs probably produce a reboot here and there. Tough to tell if it's just a "comes with the territory" type of reboot or an actual problem.
Even though I'm sure there's some CM features I'll miss, maybe Salvage is my answer.
Thanks!
*sigh* Well I decided to try using some apps and guess what... reboot.
All I was doing was trying to play a game of Androminion, which is about as basic and not-tasking as possible, so I can't imagine that's what crashed things.
The only thing I can think of that you *may* need to do is reflash your hboot and/or your baseband, PRI & NV from within recovery. You can download it from the link below.
http://forum.xda-developers.com/showthread.php?t=715485
posting & replying via the XDA Premium app.
dougjamal said:
The only thing I can think of that you *may* need to do is reflash your hboot and/or your baseband, PRI & NV from within recovery. You can download it from the link below.
http://forum.xda-developers.com/showthread.php?t=715485
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Excellent, I'm going to try that. My hboot is still 0.93!
Hey dougjamal,
Just wanted to drop an update. I know how annoying it is to help someone out and never hear how things ended up!
Who knows what combo helped, but I'm fairly stable now. After updating my hboot, I flashed to Sprint Lovers, did the ##GPSCLRX# trick and then flashed to the latest nightly of CM7 (63 I believe). Only one or two crashes and one bootloop since then.
Of course, as luck would have it, a new problem showed up in the form of a dead spot on my touch screen. Right about where the "Clear" button is for notifications, that entire strip across the phone won't respond to touch. I was hoping it was a nightly issue, but I switched to a different rom and the issue was still there. Looks like it's going in for a warranty claim after-all!
Thanks for all your help
-grifta67
I searched around for a fix, but nothing I have tried so far has worked.
I am running CM A3, FD19 Modem, and the FD19 kernel. The ROM runs like a dream; much better than I was expecting. There are, however, a couple of major issues I am having.
The dialer codes are screwed (such as *#*#8778#*#* and *#*#INFO#*#*), stopping me from doing any kind of service programming on my SPH-D710 (I flashed the phone from Sprint to MetroPCS.) That being said, I cannot get mobile data because I cannot edit any of the settings on the phone, including my APN (supposedly due to a mismatch with build.prop? That's what I dug up, at least.)
I would love to be able to continue using CM9, but I cannot be without mobile data. Any ideas?
I would have posted in the Dev section, but I am under my 10 posts.
Much thanks in advance!
So I flashed my nandroid backup...
I wiped the cache and performed a reset. I restored my nandroid backup of my previous setup using AnaKonda ROM v.1 using the FC24 kernel and the FC22 Modem. I am having the same exact issue as with CM9. When use ##3282# and go to edit any of the settings, I get a modem error. I am totally stumped. Please help!
I thought you couldn't edit modem settings from CM ROMs. You have to use Touchwiz-based ROMs.
I thought your changes would have to be made through software and not directly on the phone, QPST I believe. Also your question is in the right place since you would of gotten lit up if you put this in development. Have you tried using the software recommended in so many convert to MetroPCS threads?
edit: Just saw that you do have to do those codes on one tutorial but I know I seen other tutorials that were more software driven... Hope you get it done Good luck
Mobile data is back!
playya said:
I thought your changes would have to be made through software and not directly on the phone, QPST I believe. Also your question is in the right place since you would of gotten lit up if you put this in development. Have you tried using the software recommended in so many convert to MetroPCS threads?
edit: Just saw that you do have to do those codes on one tutorial but I know I seen other tutorials that were more software driven... Hope you get it done Good luck
Click to expand...
Click to collapse
In order to use QPST or CDMA tools, the phone has to have UART and USB set to Modem, which when I try to change these settings from PDA it doesn't stick.
webran61 said:
I thought you couldn't edit modem settings from CM ROMs. You have to use Touchwiz-based ROMs.
Click to expand...
Click to collapse
I honestly wouldn't know one way or the other. I can VIEW those settings as if I was on a TW ROM so long as I don't need to enter my MSL. I have the correct MSL, the sofware just won't progress any further.
Mobile data is now working! I used Calkins Format all, wiped the cache, dalvik cache, and /Data. I then restored my nandroid backup, wiped the cache and dalvik-cache again, followed by flashing the FD19 AOSP Kernel.
After a good power cycle, it work, and the data speeds are reporting twice as fast as they were before from speedtest.net.
I would like to be able to set my phone back to modem, but I won't be greedy. Thanks for the help!
On a different thread i asked for help with regards to pin locked. While under GB i used pin lock with Go locker and also stock. Never had an issues. Since ICS update, as my other thread my screen will lock with Samsung pin lock with no matter what i am doing. So is getting extremely annoying. I have done 5 factory reset, 2 after finally rooting my phone. Now it has being weeks since ICS and i am still with the problem.
Trying to live with it, but now daily is getting more annoying since now is really asking for pin like every min. I went on a trip over the weekend. While using telenav, the phone ask for pin over 30 times within the 3 hour drive.
Now at this point, with TBU i have already removed but backup 5 bloatware and froze the most. Here is my question, what or how can i bring the phone to clean factory setting. Including formatting the card. Do know i checked it while under the other resets and never formatted.
I am hoping that with a new clean, swype, or whatever steps i can take to completey clean my phone of anything and everything it will fix this issue.
Any thoughts?
dragonfire665 said:
On a different thread i asked for help with regards to pin locked. While under GB i used pin lock with Go locker and also stock. Never had an issues. Since ICS update, as my other thread my screen will lock with Samsung pin lock with no matter what i am doing. So is getting extremely annoying. I have done 5 factory reset, 2 after finally rooting my phone. Now it has being weeks since ICS and i am still with the problem.
Trying to live with it, but now daily is getting more annoying since now is really asking for pin like every min. I went on a trip over the weekend. While using telenav, the phone ask for pin over 30 times within the 3 hour drive.
Now at this point, with TBU i have already removed but backup 5 bloatware and froze the most. Here is my question, what or how can i bring the phone to clean factory setting. Including formatting the card. Do know i checked it while under the other resets and never formatted.
I am hoping that with a new clean, swype, or whatever steps i can take to completey clean my phone of anything and everything it will fix this issue.
Any thoughts?
Click to expand...
Click to collapse
What delay are you using before pin lock comes on? Try and step it up a bit longer
i already tried the delay. Heck i even called tmobile and they couldnt figure it out. It happens while using it, meaning, i will be typing a text, and pin locks comes up, searching the net, using an app, anything, it will happened back to back. Especially installing an app. I will be on play store, download an pp, try to install it and pin lock will come up. And no just pin lock, i change it to lines, facial, and just slide and they all do it.
dragonfire665 said:
i already tried the delay. Heck i even called tmobile and they couldnt figure it out. It happens while using it, meaning, i will be typing a text, and pin locks comes up, searching the net, using an app, anything, it will happened back to back. Especially installing an app. I will be on play store, download an pp, try to install it and pin lock will come up. And no just pin lock, i change it to lines, facial, and just slide and they all do it.
Click to expand...
Click to collapse
Have you tried darkside wipes and fresh installs without restoring TB data?
well there was no removal or installation with TB after the last factory reset. So here are my questions.
1. What is the different between, Clockworkmod recovery wipe/factory reset and the ICS actual factory reset?
2. I know i used Darkside cache wipe to fix my hanging failures after root with permission fix too. What would Darkside wipe do?
I just want to do anything and everything to clean my phone completely and start fresh while keeping root access. Also, if resetting the phone, should i reinstall all bloatware i uninstall using TB?
Any thoughts?
So, it seems that my problems, after visiting so many sites, as all know including this one, there is no solution. Except one. Since i am rooted, i might as well and crab my cojones and install a custom rom. This might help me removing everything and starting fresh.
Can any reassure me that i am not so stupid and i wont brick my phone? lol
Can anyone suggest a great rom? i dont care in regards to battery life and such, after reading under android development, i think all roms give just about the same. But maybe there is one that has being favor by most. And i noticed way too many under Android development.
Also, do all rom come with kernels, radio and all the necesary for the T989? or would this be things i will have to obtain separate?
I know i will be doing another nanbackup, using TBP for app backup as well as backup pro. But, should i reinstall all bloatware that i unistalled with TBP?
Thanks in advance for the time some have given me here by helping me.
I use the Infamous rom and it's been stable and worked well for me, though you will get several answers on this. Everyone likes something different. Since you are already on ICS, your radio should be fine. The roms all come with kernels. If possible, install your apps fresh from the market, sometimes there are issues when you use TB to restore apps or data.
Make sure to grab the darkside super wipe and darkside cache wipe tools. The first post in each rom thread should have flashing instructions (they are not all the same, some require flashing google apps, some have them baked in already).
Infamous is fiyahhhh power. Can't get enough and cant wait til next update. Its gonna be the ish!!! But don't stick to one rom. Try em all and choose for yourself. What I like might not be the same you like. Good luck
Sent from my SGH-T989 using xda app-developers app
datrapstar said:
Infamous is fiyahhhh power. Can't get enough and cant wait til next update. Its gonna be the ish!!! But don't stick to one rom. Try em all and choose for yourself. What I like might not be the same you like. Good luck
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
You make a good point. And is not that i dont like Stock, is just that this stupid pin crap hasnt stop even after 4 factory reset.
BTW, which one is Infamous, i see so many darkside, AOKP, juggernaut, but cant find Infamous.
http://forum.xda-developers.com/showthread.php?t=1645985
^ enjoy
So i want to install a custom rom, but before i do i wan to another nand. I am trying to restore the following app which i uninstall with TBP (Talkbalk, voice command, and yahoo finance) however, it has being already 30mins since i click on Talkbalk and restore and until this point, right now is 749p (30 mins later) TBP it still saying restoring APP+Data talkbalk 3.0.2.
What can i do here? i am afraid of not uninstalling the following add and if i brick or want to go back to stock i wont be able to. Also, i did notice that i have little to no space under my system/app, i recall only install S Voice, but i dont even find that system/app, so i do not know what is taking all the space when i unistall 3 apps.
any suggestions?
no one has any ideas what i should do? or how can i get this programs reinstall?
dragonfire665 said:
no one has any ideas what i should do? or how can i get this programs reinstall?
Click to expand...
Click to collapse
If your still around, give me specifics of what you want done and I'll do my best to point you in the right direction. I'm not a dev but I can help you even if it means starting from scratch.
1) to reset back to factory. Look up a Google site called galaxys2root.com and find you model. Follow the instructions. You be back to factory. After you done all of that factory reset your phone from within the settings menu. You will erase everything on your phone minus your external SD card.
2) on the same site re root your phone and install superuser. It has a step by step guide of this as well.
3) search the forums on xda and find your device and the roms that are supported for your specific device.
4) you want to find darkside super wipe and darkside cache wipe. Install both on your SD card. Your get used to using both this tools.
5) choose the rom of your liking and install on your SD card.
6) follow ops instructions about install without any changes. Don't change any of the steps. If you do not follow the steps It will make the the install not work correctly.
7) BE PATIENT. Let the rom settle in your phone. After you install everything, make sure you fix permissions so that way everything falls into place.
..... this is the way I have done it and yet to have an issue. Your best bet is to read EVERYTHING. Don't just skim thru the original post and just go by the screenshots and choose just cuz it looks cool. Research all the thread to find out what issues are there and what not.
Last but not least thanks the dev or devs involved in the rom, tools, kernels that you decide to use. Their doing all of this for free. And I feel like I need to say this even tho I know it sound very minor. But Google is your best friend.
"feeding this unicorn carrots til the finish line"
Hey there everyone,
I am honestly at a bit of a loss.
I have an AT&T GS3, and I noticed that all the bloatware was SERIOUSLY draining the battery and hogging up RAM, so I thought it would be a great idea to get a custom rom to enhance my phone.
I used the GS3 Toolkit to flash TWRP recovery. - All went well
I read up on some different Roms, and i chose to install http://forum.xda-developers.com/showthread.php?t=2089821
I installed RLS16
I followed the instructions,
Wipe data/factory reset
Wipe dalvik cache
Wipe /system
I went through the Aroma installer and chose to install the Developer's Pick.
This includes a bunch of little addons like 4.2 camera, gallery, keyboard, etc.
but it also installs lean kernel.
The install went fine, nothing said it failed
but once i was in the rom. Things got terrible.
My phone randomly crashed and shut off, like within minutes each time, camera would crash the phone, causing it to shut off, etc.
So i went through the GS3 toolkit, downloaded and reflashed the stock Rom and recovery.
Once it booted, I keep getting "Unfortunately Messaging has Stopped" and I cannot receive or send text messages, even through other texting programs like Handcent SMS.
No matter what, it keeps crashing (the messaging, not the rom). I factory reset, wiped, everything. Nothing will fix it.
I thought that maybe the stock rom doesnt include stock kernel? So i went online, downloaded the stock kernel, flashed, reflashed stock rom, and STILL the same thing. Messaging has stopped working.
Also as a side note, when i tried to do a google voice search. I get a page saying Sorry and that my computer or phone might be sending network requests or something along those lines.
I cannot think of anything else I can do....
If anyone has any idea, please let me know...
Thanks!
eternalcold said:
Hey there everyone,
I am honestly at a bit of a loss.
I have an AT&T GS3, and I noticed that all the bloatware was SERIOUSLY draining the battery and hogging up RAM, so I thought it would be a great idea to get a custom rom to enhance my phone.
I used the GS3 Toolkit to flash TWRP recovery. - All went well
I read up on some different Roms, and i chose to install http://forum.xda-developers.com/showthread.php?t=2089821
I installed RLS16
I followed the instructions,
Wipe data/factory reset
Wipe dalvik cache
Wipe /system
I went through the Aroma installer and chose to install the Developer's Pick.
This includes a bunch of little addons like 4.2 camera, gallery, keyboard, etc.
but it also installs lean kernel.
The install went fine, nothing said it failed
but once i was in the rom. Things got terrible.
My phone randomly crashed and shut off, like within minutes each time, camera would crash the phone, causing it to shut off, etc.
So i went through the GS3 toolkit, downloaded and reflashed the stock Rom and recovery.
Once it booted, I keep getting "Unfortunately Messaging has Stopped" and I cannot receive or send text messages, even through other texting programs like Handcent SMS.
No matter what, it keeps crashing (the messaging, not the rom). I factory reset, wiped, everything. Nothing will fix it.
I thought that maybe the stock rom doesnt include stock kernel? So i went online, downloaded the stock kernel, flashed, reflashed stock rom, and STILL the same thing. Messaging has stopped working.
Also as a side note, when i tried to do a google voice search. I get a page saying Sorry and that my computer or phone might be sending network requests or something along those lines.
I cannot think of anything else I can do....
If anyone has any idea, please let me know...
Thanks!
Click to expand...
Click to collapse
When you flashed stock, did you flash the one for your carrier? (It should flash the kernel at the same time)
Did you try clearing the messaging app's data/cache?
Did you try flashing another custom ROM to see if you still get the errors? If not, could give 4.2.1 a shot.
BWolf56 said:
When you flashed stock, did you flash the one for your carrier? (It should flash the kernel at the same time)
Did you try clearing the messaging app's data/cache?
Did you try flashing another custom ROM to see if you still get the errors? If not, could give 4.2.1 a shot.
Click to expand...
Click to collapse
Yeah i flashed the one for my carrier. And i figured it would do the kernel, but just in case i tried flashing it separately....
and yeah i did try wiping the data/cache, but i will try it again.
and I could always try flashing another custom rom. Do you have any suggestions? i just want one that works quickly, is stable, and has messaging lol
eternalcold said:
Yeah i flashed the one for my carrier. And i figured it would do the kernel, but just in case i tried flashing it separately....
and yeah i did try wiping the data/cache, but i will try it again.
and I could always try flashing another custom rom. Do you have any suggestions? i just want one that works quickly, is stable, and has messaging lol
Click to expand...
Click to collapse
Look in my sig I don't give suggestion per say cause it's up to the user's preference but I'll always be running something that works.
BWolf56 said:
Look in my sig I don't give suggestion per say cause it's up to the user's preference but I'll always be running something that works.
Click to expand...
Click to collapse
I might try that one out. I was looking at some reviews, someone said there may be Bluetooth issues. I just bought the Moga, and i need BT to work perfecty...
Any input on that?
eternalcold said:
I might try that one out. I was looking at some reviews, someone said there may be Bluetooth issues. I just bought the Moga, and i need BT to work perfecty...
Any input on that?
Click to expand...
Click to collapse
Best thing to do is to read changelogs but for now I'll give you the answer, it has been fixed a few releases ago in Task650's AOKP.
BWolf56 said:
Best thing to do is to read changelogs but for now I'll give you the answer, it has been fixed a few releases ago in Task650's AOKP.
Click to expand...
Click to collapse
Alright, i'll flash that one, i'll post to here when it's finished. Thanks!
Did you check your IMEI?
xBeerdroiDx said:
Did you check your IMEI?
Click to expand...
Click to collapse
Just checked, my IMEI is there.
Also, i found this thread
http://forum.xda-developers.com/showthread.php?t=1804782
but their images wont show. Any idea what route they are taking to solve this??
eternalcold said:
Just checked, my IMEI is there.
Also, i found this thread
http://forum.xda-developers.com/showthread.php?t=1804782
but their images wont show. Any idea what route they are taking to solve this??
Click to expand...
Click to collapse
That guy flashed the bootloaders. I'm not sure what the pictures are supposed to be but they don't seem to lead to anything.
My take on it: Don't play with bootloaders, it's the only way to really brick your phone (if something goes wrong that is).
BWolf56 said:
That guy flashed the bootloaders. I'm not sure what the pictures are supposed to be but they don't seem to lead to anything.
My take on it: Don't play with bootloaders, it's the only way to really brick your phone (if something goes wrong that is).
Click to expand...
Click to collapse
Understood, I wont mess with them.
I really just want to understand a couple things.
1. Why did the ROM I installed before work for everyone else except me? and i followed the instructions.
and 2. after flashing to stock, how am I unable to fix this?
mainly to just learn what went wrong.
Sometimes the reason just...you had a bad flash or something broke down in there. I did the CF easy root method and flashed TWRP in goo manager and then started flashing. I've never tried the toolkit but like anything many times it just depends on the download you got or a bad flash. We've all had several...just hate when it involves rooting or using ODIN.
hednik said:
Sometimes the reason just...you had a bad flash or something broke down in there. I did the CF easy root method and flashed TWRP in goo manager and then started flashing. I've never tried the toolkit but like anything many times it just depends on the download you got or a bad flash. We've all had several...just hate when it involves rooting or using ODIN.
Click to expand...
Click to collapse
Thanks,
Is there any way to repair it?
Alright, so....
I think i have figured out what the issue was. Or by random chance got it fixed.
I was going to try to install the Synergy Rom. And while going through the custom setup, i noticed "Install AOSP Messaging" and "Install TW Messaging"
I chose the TW messaging, and went through the rest of the installer.
For some reason i kept hanging at the "Samsung Galaxy S3" logo, and it would not boot.
(Honestly, i've used custom roms since the HTC Touch Pro 2, and i've NEVER had such issues. And i personally think the TP2 was way more difficult lol)
So I ONCE AGAIN flashed to stock. and randomly the messaging works!
I only can guess that even when flashing the stock rom, it doesnt change something regarding the messaging app. I'm not sure. All i know is that i'm on stock again and everything is working. I highly doubt i'm going to try another custom rom for a while until i have a full understanding of what happened.
But in case anyone else was having this problem, i hope this helped.
Hey guys, long time browser, first time poster, but not a reason for celebration, alas.I come to you guys out of frustration after hours of being unable to solve my issue cruising the interwebs, and the thread title kinda says it all.
To start from the beginning, I recently delved into the rooted world by means of towelroot (kitkat 4.4.2), installed xposed framework, got the modules XBlast and XPrivacy, and you might have guessed, fiddled around with each. Everything was fine and dandy until I was having issues receiving/making calls through an app (LINE, if you know it), and so I attempted to figure out what the issue was, very much assuming XPrivacy to be the culprit. Couldn't get it to work, which is when I decided to restore my backup I made using Clockwork. Should have been nice and smooth sailing, but...
Upon having it "restored" I booted on into it, which is when I got smacked in the face; as soon as I'm booted, most, if not all, my apps are reporting that they have stopped working by a bombardment of error messages in endless succession, making just browsing the home screens almost impossible. Also with this barrage came the lack of cell service, a nice white n' slashed out circle in what should be my bars of signal. I tried again to restore my phone from my backup. Same issue, but I did notice during the recovery it made mention of something like "secure_android" missing? This sent me on my hours of head banging, turning up *possible* resolutions, which didn't work. I've tried flashing the stock bootloader, gapps, and nothing. Now, my data and apps are all still there and I can get into recovery without issue, it's just the pain of not being able to actually using any of it.
I have debugging switched on on my phone, but do not have some sort of adb app installed on it, nor could I access any market place to try. I'm not so sure I would be able to install anything on my phone given my current circumstances, anyway.
Please, if any of you out there have some idea as to what is going on, I'm all eyes (as ears on a forum don't work so well)! If there are any details I may have omitted and so on, just let me know and I'll supply it--
Thank you all so much in advance for any possible steps that may resolve this issue!
Fingerless said:
Hey guys, long time browser, first time poster, but not a reason for celebration, alas.I come to you guys out of frustration after hours of being unable to solve my issue cruising the interwebs, and the thread title kinda says it all.
To start from the beginning, I recently delved into the rooted world by means of towelroot (kitkat 4.4.2), installed xposed framework, got the modules XBlast and XPrivacy, and you might have guessed, fiddled around with each. Everything was fine and dandy until I was having issues receiving/making calls through an app (LINE, if you know it), and so I attempted to figure out what the issue was, very much assuming XPrivacy to be the culprit. Couldn't get it to work, which is when I decided to restore my backup I made using Clockwork. Should have been nice and smooth sailing, but...
Upon having it "restored" I booted on into it, which is when I got smacked in the face; as soon as I'm booted, most, if not all, my apps are reporting that they have stopped working by a bombardment of error messages in endless succession, making just browsing the home screens almost impossible. Also with this barrage came the lack of cell service, a nice white n' slashed out circle in what should be my bars of signal. I tried again to restore my phone from my backup. Same issue, but I did notice during the recovery it made mention of something like "secure_android" missing? This sent me on my hours of head banging, turning up *possible* resolutions, which didn't work. I've tried flashing the stock bootloader, gapps, and nothing. Now, my data and apps are all still there and I can get into recovery without issue, it's just the pain of not being able to actually using any of it.
I have debugging switched on on my phone, but do not have some sort of adb app installed on it, nor could I access any market place to try. I'm not so sure I would be able to install anything on my phone given my current circumstances, anyway.
Please, if any of you out there have some idea as to what is going on, I'm all eyes (as ears on a forum don't work so well)! If there are any details I may have omitted and so on, just let me know and I'll supply it--
Thank you all so much in advance for any possible steps that may resolve this issue!
Click to expand...
Click to collapse
Sounds like your backup was a downgrade (old version).
I would suggest doing a factory reset, test it. If that doesn't do it, use Odin to flash stock firmware (which can be found in the general section stickies).
BWolf56 said:
Sounds like your backup was a downgrade (old version).
I would suggest doing a factory reset, test it. If that doesn't do it, use Odin to flash stock firmware (which can be found in the general section stickies).
Click to expand...
Click to collapse
Thanks for responding! I did try a wipe data/factory reset via CWM, then restored from there. Didn't work. I'm not sure if there is a particular order in how it should be done such as "factory reset, reboot phone into recovery, restore" or if I should be able to get away with "factory reset, restore", the latter being what I did. I also got a hold of a bootloader file and modem base band for build I747UCUFNE4, if those would be useful in any way.
If it's of any help, I somehow got the Unofficial Omni ROM 4.4.4 to work without any issue, but not quite happy enough with the overall interface of it, yet slowly adapting having installed a touchwiz launcher just to hold me over.
I've tried locating the backup CWM created on my phone so that I could store it on my computer and generate another backup as from what I read, the unpaid version only allows you one at a time, but had no luck digging through my directories. I'm currently investigating this online nandroid backup thing to see if there's anything to it.
I've also come across some file labeled "I747UCUFNE4_Stock_Rooted_Deodex" which is a zip, but I'm reading ODIN uses tar as it's compression of choice? Does this mean I should flash this file via recovery, or? Also, the file size is a whopping 920MB or so... that normal? (Edit: this is where I found the file http://forum.xda-developers.com/showthread.php?t=2788357 which says to flash in recovery)
Thanks again for your response! I was really thinking my problem would just be glanced over.
Fingerless said:
Thanks for responding! I did try a wipe data/factory reset via CWM, then restored from there. Didn't work. I'm not sure if there is a particular order in how it should be done such as "factory reset, reboot phone into recovery, restore" or if I should be able to get away with "factory reset, restore", the latter being what I did. I also got a hold of a bootloader file and modem base band for build I747UCUFNE4, if those would be useful in any way.
If it's of any help, I somehow got the Unofficial Omni ROM 4.4.4 to work without any issue, but not quite happy enough with the overall interface of it, yet slowly adapting having installed a touchwiz launcher just to hold me over.
I've tried locating the backup CWM created on my phone so that I could store it on my computer and generate another backup as from what I read, the unpaid version only allows you one at a time, but had no luck digging through my directories. I'm currently investigating this online nandroid backup thing to see if there's anything to it.
I've also come across some file labeled "I747UCUFNE4_Stock_Rooted_Deodex" which is a zip, but I'm reading ODIN uses tar as it's compression of choice? Does this mean I should flash this file via recovery, or? Also, the file size is a whopping 920MB or so... that normal? (Edit: this is where I found the file http://forum.xda-developers.com/showthread.php?t=2788357 which says to flash in recovery)
Thanks again for your response! I was really thinking my problem would just be glanced over.
Click to expand...
Click to collapse
I meant factory reset without restoring.
But now that you're back up and running, there's no need for it (unless you flash another ROM). You could flash NE4 if you wanna get back on the official ROM but there are also tw custom ROM which you can look into (you're currently using an aosp one).
As for the 920mb, yeah.. That's Sammy at its best, bloating their ROMs.
BWolf56 said:
I meant factory reset without restoring.
But now that you're back up and running, there's no need for it (unless you flash another ROM). You could flash NE4 if you wanna get back on the official ROM but there are also tw custom ROM which you can look into (you're currently using an aosp one).
As for the 920mb, yeah.. That's Sammy at its best, bloating their ROMs.
Click to expand...
Click to collapse
You think it would be safe to do a factory reset and try to restore just the data from my recovery? Or is it possible that the data is somehow the issue with everything going wonky?
I'm very new to the ROM thing, Omni was easy to get up and running, but actually playing with a ROM was more of a last ditch effort to see if the problem would be resolved that way and give any sort of indication as to what the issue was (still haven't the sllightest). It's currently not rooted (at least according to my root checker) and the towelroot method doesn't seem to work on it. I kinda need to be rooted if I wanted to make a nandroid, I really want to make a back up of what I currently have set in case I screw the pooch trying to get things back to "normal", yet I'm afraid of overwriting my only recovery and losing whatever data is embedded, though I'm not too deeply saddened by the thought of not having chat histories and whatnot, it would just be nice to have. Perhaps you have thoughts, or anyone else out there, on the matter? I know my first step would be to at least root my current ROM, then back up, I found this as a means to root Omni (http://forum.xda-developers.com/showthread.php?t=2672160), but how do I determine whether I'm using an ARM based or x86 based device?
Good to know the file size for the stock ROM is considered normal. I didn't even consider carrier/Samsung bloat to have such a huge impact.
Thanks, yet again!