Develop Bugs

very strange problem for the experts

So I bought the phone unlocked (Tmobile branded). Came with stock unrooted ics.
I rooted it, and installed Jedi mind trick 7.
I traded it, then the guy and I mutually wanted to trade back.
The guy has the phone all jacked up, so I Odin'ed back to stock unrooted 2.3.6 using the guide on here.
When I do the "*#simlock#" my Android.phone.com (I believe it was), force closes and my 4g symbol disappears for a minute. Also I don't know if this is related but I can't seem to download anything now on wifi (trying to download the official ics for Odin)
What could be causing the issues and how can I fix this? Thanks in advance guys.

Nickdroid86 said:
So I bought the phone unlocked (Tmobile branded). Came with stock unrooted ics.
I rooted it, and installed Jedi mind trick 7.
I traded it, then the guy and I mutually wanted to trade back.
The guy has the phone all jacked up, so I Odin'ed back to stock unrooted 2.3.6 using the guide on here.
When I do the "*#simlock#" my Android.phone.com (I believe it was), force closes and my 4g symbol disappears for a minute. Also I don't know if this is related but I can't seem to download anything now on wifi (trying to download the official ics for Odin)
What could be causing the issues and how can I fix this? Thanks in advance guys.
Click to expand...
Click to collapse
If I were you, I would bypass the whole sim lock process and root it and install recovery and flash a ROM of your choice. If the problem corrects urself, the .tar you odined with could be corrupt. Happened to me but media.android.com force closed every five mins. So I rooted and flashed and it was gone. If it was jacked up but still on Jedi, he prob tried to factory reset or something. Usually that soft bricks, at times hard bricks it. Just try that.
Sent from my SGH-T989 using xda premium

I managed to reroot and went and did Jedi mind trick, everything is back to normal including the *#simlock# thing. I want to get mind trick 8, but it's a small file and for some reason keeps aborting.
Sent from my SGH-T989 using Tapatalk 2

I had that same problem downloading v8. It keeps downloading the HTML file. You have a few options of getting the file.
1. Download with PC and transfer the rom to your SD card.
2. Install dolphin browser and use that instead of the stock browser to download the rom.
I went with option 2 because I didn't have a PC near by. Worked great. Good luck.
Sent from my SGH-T989 using xda app-developers app

[Q] Cannot get wallet to work

Ok. I am really upset with Tmo for blocking Wallet. I used it ALL THE TIME on my Nexus S on AT&T and I LOVED it. I've been trying to get it installed since October when I bought the phone and I cannot for the life of me get it to work. Everything I try fails or screws up the phone and I have to re-flash, so I eventually just said screw it and went to AOKP because I felt like trying something new. My friend said that I would be able to just install wallet once I did, but that is not the case. the install fails when using an apk, wallet is hidden in the market, and once when I got it installed it says "not available on your device/carrier blah blah blah" and quits. So, what I want is a solution. I need to know how to make this work because I am starting to get really upset. No solutions I can find work, nothing I've tried is successful... I might just be doing it wrong or missing something but I am determined to get it to work. NFC is working fine, I used it several times already.
Phone info:
Model: SGH-T999
Android Version: 4.1.2
Baseband: T999UVDLJA
Kernel: 3.0.48-cyanogenmod-faux123-att-tmo-00041-ga2c7267
AOKP Version: aokp_d2tmo_jb_milestone1
Build: aokp_d2tmo_userdebug 4.1.2 JZ054K eng.sethyx.20121029.025840 test-keys

I only did this for Stock rooted, but I think on you only need to modify build.prop and install like normal - if you want to change the build.prop back, you have to use the Modaco modified wallet apk. I think. I don't know, I just remember it being discussed in the thread that went over how to do it on stock.
If you want to use stock, there's a thread that will walk you through it on these forums, it's like, only one more step.

Pennycake said:
I only did this for Stock rooted, but I think on you only need to modify build.prop and install like normal - if you want to change the build.prop back, you have to use the Modaco modified wallet apk. I think. I don't know, I just remember it being discussed in the thread that went over how to do it on stock.
If you want to use stock, there's a thread that will walk you through it on these forums, it's like, only one more step.
Click to expand...
Click to collapse
I tried that the first time and it caused a failure to boot. second time, it was a program that was supposed to do it for me - same result.

If you're using the Touchwiz fix (which I think is what you're talking about in the "do it for you" program bit -that will brick it since it's for TW ROMs only and not needed for/compatible with your ROM.
Did you do that or follow a different thread? If he latter, it might help to post in there or at least link to it here so people can see exactly what you did.
Sent from my SGH-T999 using xda app-developers app

Pennycake said:
If you're using the Touchwiz fix (which I think is what you're talking about in the "do it for you" program bit -that will brick it since it's for TW ROMs only and not needed for/compatible with your ROM.
Did you do that or follow a different thread? If he latter, it might help to post in there or at least link to it here so people can see exactly what you did.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
up until now I was using touchwiz. I screwed up the phone both times while using touchwiz. Now, I'm on AOKP and cannot find anything that works for that - everything seems like it's for touchwiz. What I tried was flashing wallet now on aokp, and it didn't harm the phone but the program will not work. If I load it, it just says "Unfortunately, Google Wallet is not yet available for your device or mobile network." and I want to know how to get around that on aokp, ignore touchwiz, I was just mentioning that because I ditched it in part due to the problems it had with wallet.

Like I said, I think you need to modify the build.prop just like before for the Wallet apk to install.
In the TW wallet thread, someone kept bricking their phone because they had a non-TW ROM and it was explained to them what to do instead. I would look there and read through until you find it.
Sent from my SGH-T999 using xda app-developers app

There is a thread in the themes and apps section that does this automatically for you. You install the apk, you choose your ROM, phone an carrier and then it reboots, installs the all and a lot you need to do is open the wallet and activate your card. Then go back to the original installer app and revert your build.prop. it does everything for you almost. Check it out
Sent from my Rooted Gameboy

Pennycake said:
Like I said, I think you need to modify the build.prop just like before for the Wallet apk to install.
In the TW wallet thread, someone kept bricking their phone because they had a non-TW ROM and it was explained to them what to do instead. I would look there and read through until you find it.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Ok ok, I think I understand you now. You still have to mod build.prop even on aokp? just don't have to do all that other stuff that you do have to do for touchwiz?

osmosizzz said:
There is a thread in the themes and apps section that does this automatically for you. You install the apk, you choose your ROM, phone an carrier and then it reboots, installs the all and a lot you need to do is open the wallet and activate your card. Then go back to the original installer app and revert your build.prop. it does everything for you almost. Check it out
Sent from my Rooted Gameboy
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2044362&highlight=wallet This thread?
I was using this exact app that it screwed up my touchwiz last time, and now it does not show an option for AOKP, just AOSP. Will the AOSP work?
Ok seriously. I didn't even run the app this time I just opened it and it screwed up my rom! God, why is this so infuriating! If someone had told me I would have to go through all this bull**** to get my stupid phone to work as well as my old, slow nexus s I would never have upgraded! BRB, time to reflash aokp.
*seeths with rage*

It was the thread about the by-hand fix for Jelly Bean.
I'd do it by hand just so you know exactly what you're doing so that you can troubleshoot if it goes wrong.
Are you rooted? I did this on the root66 root-injected ROM. I did find that you really need to check to make sure your build.prop has been properly edited - at first I was using an editor that just didn't work for whatever reason and wasn't saving the file.
This was the reason I rooted my phone and it worked great - so I'm sure you'll be able to figure out what is going g wrong and get it to work.
Sent from my SGH-T999 using xda app-developers app

Pennycake said:
It was the thread about the by-hand fix for Jelly Bean.
I'd do it by hand just so you know exactly what you're doing so that you can troubleshoot if it goes wrong.
Are you rooted? I did this on the root66 root-injected ROM. I did find that you really need to check to make sure your build.prop has been properly edited - at first I was using an editor that just didn't work for whatever reason and wasn't saving the file.
This was the reason I rooted my phone and it worked great - so I'm sure you'll be able to figure out what is going g wrong and get it to work.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
IF I'm not mistaken aokp is rooted by default. Anyways, I'm in the process of reinstalling it... again.

Pennycake said:
It was the thread about the by-hand fix for Jelly Bean.
I'd do it by hand just so you know exactly what you're doing so that you can troubleshoot if it goes wrong.
Are you rooted? I did this on the root66 root-injected ROM. I did find that you really need to check to make sure your build.prop has been properly edited - at first I was using an editor that just didn't work for whatever reason and wasn't saving the file.
This was the reason I rooted my phone and it worked great - so I'm sure you'll be able to figure out what is going g wrong and get it to work.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
used an app from the market to edit my build.prop and it works perfectly now. Thanks!

[Q] Newbie questions

Hi all.
My first post here and a couple of questions.
Per instructions found here http://forum.xda-developers.com/showthread.php?t=2195283 , I was able to root my phone using TWRP and odin.
The phone works fine but many of the apps are missing (maps, youtube etc). I was able to download the maps 6.14 apk and install it, but the gps takes forever to lock now. Is there a s2 specific app that was somehow wiped out by the rooting process?
Also, the stock browser is set to full screen, but when typing in the address, the address bars flickers on and off and I can only see the google search suggestions untill I press the keyboard again. Im using stock samsung keyboard.
Don't know if it's normal, but the phone doesn't pull my contacs from the sim card before or after root. I used to have HTC Mytouch from T-mobile and the names and phone numbers all came up as soon as I insterted the sim card into that phone when I bought it 2 years ago.
Thank you.
Sorry forgot to add.
The phone is ( was?) stock JB 4.1.2 (t-mobile) and the only thing I did was root it.

The only thing I can think of is to re flash the stock ROM in Odin. Then redo installing recovery. I followed roughly the path to root you described and didn't have any problems.
Sent from my Nexus 7 using Tapatalk 4 Beta

tronmech said:
The only thing I can think of is to re flash the stock ROM in Odin. Then redo installing recovery. I followed roughly the path to root you described and didn't have any problems.
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thanks for the suggestion.
Do you know if the settings and data will be wiped out if I try to reinstall ? I dont have a spare phone I would hate to lose the apps and the texts and etc.

Well, if you have twrp, install it first and make a backup that INCLUDES the preload partition as well as data, system, cache, etc. Then you don't need to worry. But odining stock job over stock job should be harmless since it won't overwrite data -- just be sure repartition isn't checked
Sent from my SAMSUNG-SGH-T989 using Tapatalk 4 Beta

Well, unrooted, rerooted, wiped clean, reinstalled stock 4.1.2 and nothing ...
The gps is crap with all the .conf files tried. And no matter what, once I install SU , the damn apps disappear after reboot. Plus considering that it's a 1.5mhz processor, its slower than my old HTS 1.2mhz Mytouch and even 1mhz ZTE warp. Probably gonna send it back. Too bad, since I like the screen a lot.

You're missing apps can be redownloaded from the play store. As for your GPS problem, download and follow the instructions to install AGPS from this thread and you should be fine.
Sent from my SGH-T989

iburnhearts said:
You're missing apps can be redownloaded from the play store. As for your GPS problem, download and follow the instructions to install AGPS from this thread and you should be fine.
Sent from my SGH-T989
Click to expand...
Click to collapse
Thanks , but I already tried that.
As for the apps, it's really not a big deals, but the fact that the SU app makes them disappear is a bit of a concern. , plus the fact that gps works like crap even after the patch and several new gps.conf files , make this phone an overpriced and kinda overhyped toy. Frankly one shouldnt be looking at patches and fixes on a phone this "good". If an old ZTE and Htc work without a hitch, then this thing is about $150 too expensive for what it is.
And for the life of I cant understand why wouldnt sucksung put a damn led light on the case to alert the user of missed calls or texts instead of us having to resort to the nolite and such..
Thank you for all the help though).Thank you though for the help.

cyclefan said:
Hi all.
My first post here and a couple of questions.
Per instructions found here http://forum.xda-developers.com/showthread.php?t=2195283 , I was able to root my phone using TWRP and odin.
The phone works fine but many of the apps are missing (maps, youtube etc). I was able to download the maps 6.14 apk and install it, but the gps takes forever to lock now. Is there a s2 specific app that was somehow wiped out by the rooting process?
Also, the stock browser is set to full screen, but when typing in the address, the address bars flickers on and off and I can only see the google search suggestions untill I press the keyboard again. Im using stock samsung keyboard.
Don't know if it's normal, but the phone doesn't pull my contacs from the sim card before or after root. I used to have HTC Mytouch from T-mobile and the names and phone numbers all came up as soon as I insterted the sim card into that phone when I bought it 2 years ago.
Thank you.
Sorry forgot to add.
The phone is ( was?) stock JB 4.1.2 (t-mobile) and the only thing I did was root it.
Click to expand...
Click to collapse
Make Sure you Flash it Correctly.. Since you have TWRP Flash other Rom of your preferences and then DO THE CORRECT Wipes!.

Dennisalex said:
Make Sure you Flash it Correctly.. Since you have TWRP Flash other Rom of your preferences and then DO THE CORRECT Wipes!.
Click to expand...
Click to collapse
Appreciate the advice.
But Ive done that already. The gps ,when it does finally lock, takes forever. Regardless of the .conf files. And no matter what, after SU gets installed and the phones is restarted some apps are simply gone.

Instead of stock ROM I would give you the suggestion of trying out cyanogen mod since imo its actually much better everything wise over stock ROM
Give it a whirl and tell us what u think
See if the probs went away
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

Android 4.3 OTA Security Update Boot Loop Issue and Solution

I hit a boot loop snag on my Galaxy Nexus GSM after installing the recent 4.3 OTA security update. I had no issues with the initial Android 4.3 release, but the security update did something that made my device hit a boot loop. I could restore from a Nandroid backup, but about once a day I would hit the boot loop snag again. After dealing with daily restores for a couple days I dug into it a bit and found that when the phone gets mired in a boot loop I can fix it by deleting two files.
The trick is you have to be using TWRP on the recovery partition because that will let you use a file manager to delete the two files. There may well be other solutions but that's been the easiest for me. The two files which need to be deleted are:
/data/system/locksettings.db
/data/system/locksettings.db-shm
If you use Google Wallet you'll see a similarly named file there "locksettings.db-wal" -- DO NOT DELETE THIS ONE, just the two above.
If this helps anyone please post so if it doesn't people won't waste their time -- THANKS!

Told my cousin she said that it worked like a charm! What do those two files actually do?
Sent from my Galaxy Nexus using Tapatalk 4

Vekhez said:
Told my cousin she said that it worked like a charm! What do those two files actually do?
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
To be honest -- I have no idea. I found this by pure trial and error after a totally non-related post pointed to the /data/system folder.
The files appear to get recreated when the phone reboots so it's probably generated from the system partition ultimately.
From what I know now, it appears as though SuperSU is causing this somehow. Is your cousin using SuperSU do you know?
There was a recent update to version 1.60 of SuperSU which was supposed to address this and I think it did for some users, perhaps Nexus 4 users only, but I definitely have this issue still even with the newest 1.65 version.
I've ended up created a Tasker script to delete the files on reboot because I was tired of having to repetitively reboot into TWRP and manually delete them. It works well but I'd much rather fix the underlying cause.

sansnil said:
To be honest -- I have no idea. I found this by pure trial and error after a totally non-related post pointed to the /data/system folder.
The files appear to get recreated when the phone reboots so it's probably generated from the system partition ultimately.
From what I know now, it appears as though SuperSU is causing this somehow. Is your cousin using SuperSU do you know?
There was a recent update to version 1.60 of SuperSU which was supposed to address this and I think it did for some users, perhaps Nexus 4 users only, but I definitely have this issue still even with the newest 1.65 version.
I've ended up created a Tasker script to delete the files on reboot because I was tired of having to repetitively reboot into TWRP and manually delete them. It works well but I'd much rather fix the underlying cause.
Click to expand...
Click to collapse
Yeah, they are using SuperSU...they are still on 1.5, I'll tell them to update.
Sent from my Galaxy Nexus using Tapatalk 4

Vekhez said:
Yeah, they are using SuperSU...they are still on 1.5, I'll tell them to update.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Thanks, Vekhez. Let me know if that hopefully fixes the problem for them. If it does it means I'm "special" not in a good way!

sansnil said:
Thanks, Vekhez. Let me know if that hopefully fixes the problem for them. If it does it means I'm "special" not in a good way!
Click to expand...
Click to collapse
Nope it didn't.. Same problem.
Sent from my Galaxy Nexus using Tapatalk 4

Vekhez said:
Nope it didn't.. Same problem.
Click to expand...
Click to collapse
Thanks for this. I'm sorry for your cousin but happy for me because that means it's not something unique or specific to my device.
This is helpful -- I'm going to post this over in the SuperSU thread and see if Chainfire will pick it up and look into it.
Stay tuned...

sansnil said:
Thanks for this. I'm sorry for your cousin but happy for me because that means it's not something unique or specific to my device.
This is helpful -- I'm going to post this over in the SuperSU thread and see if Chainfire will pick it up and look into it.
Stay tuned...
Click to expand...
Click to collapse
Ok, so it turns out this is actually being caused by the app "Delayed Lock" if you use a pattern lock. If you use a PIN/password lock it won't happen, but if you use a pattern lock with the current version of Delayed Lock on a Galaxy Nexus this boot loop issue will occur.
I've opened a bug with the Delayed Lock Dev so hopefully he'll find a way to fix it. In the meantime, choices are to either disabled/uninstall Delayed Lock (hate!) or switch to a PIN or password lock setting.

Hey guys,
I had the same problem and found out that it could be solved, without losing any data, by directly flashing the update.
Here's what I did: http://forum.xda-developers.com/showthread.php?t=2427613
Best of luck.

[Q] huge problem, need help

this morning I got unfourtunately, the process com.android.phone has stopped and cannot get the phone to boot without constantly hitting the "OK"
I see there is no signal, and can see in the phone information that the radio is turned off. I have an app that used to get to the screen but now it hangs due to the phone has stopped issue.
Is there any way I can turn the radio on by using some code with the dialer pad?
I have tried recovering 3 other nand backups, but none work. all have the same result.
Thanks for any help someone might be able to give me!
It is a rooted samsung galaxy s4 M919 from t-mobile

is it stock rooted or what ROM are you running ?what kernel? what settings ? what mods? we need some detail sir but for starters if you can get it to boot try *#2263# and if its not set to automatic try clicking your options auto is the default setting

bobolinko said:
this morning I got unfourtunately, the process com.android.phone has stopped and cannot get the phone to boot without constantly hitting the "OK"
I see there is no signal, and can see in the phone information that the radio is turned off. I have an app that used to get to the screen but now it hangs due to the phone has stopped issue.
Is there any way I can turn the radio on by using some code with the dialer pad?
I have tried recovering 3 other nand backups, but none work. all have the same result.
Thanks for any help someone might be able to give me!
Remove your sd card sim card and battery let set 10 minutes put back in see if the message is still present if so you might need a new sim card.
Click to expand...
Click to collapse

I have tried both of the above suggestions and no joy!
I have 2 nandroid backups that were done when the phone was working fine, and recovering either one has the very same symptoms.
I'm not sure that all the phone is backed up or restored in entirety, unless there it a hardware fault in this phone. It's 31 days old today..... :<(
if anyone else has any ideas, I'm all ears!
Thanks!

Might just be a lemon. I would just flash back to stock then take the phone and get a replacement.

bobolinko said:
I have tried both of the above suggestions and no joy!
I have 2 nandroid backups that were done when the phone was working fine, and recovering either one has the very same symptoms.
I'm not sure that all the phone is backed up or restored in entirety, unless there it a hardware fault in this phone. It's 31 days old today..... :<(
if anyone else has any ideas, I'm all ears!
Thanks!
Click to expand...
Click to collapse
You still have given us no details on what you are running, stock, rooted, touchwiz, aosp. Do you know how to Odin back to stock? Sounds to me what happens when you flash a modem not meant for the phone.
Sent from my SGH-M919 using xda app-developers app

tylerholbrook said:
You still have given us no details on what you are running, stock, rooted, touchwiz, aosp. Do you know how to Odin back to stock? Sounds to me what happens when you flash a modem not meant for the phone.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
OMG! Sorry! It is a STOCK ROOTED SGH919, 4.22 M919UVUAMDL W/ 3.4.0-453951 Kernel
Thanks!

bobolinko said:
OMG! Sorry! It is a STOCK ROOTED SGH919, 4.22 M919UVUAMDL W/ 3.4.0-453951 Kernel
Thanks!
Click to expand...
Click to collapse
Odin back to stock I would think should alleviate your problem. I flashed an international modem when I was running omega rom and got flash happy when I was drunk. Had the exact same problem you are describing odin to stock worked for me
Sent from my SGH-M919 using xda app-developers app

tylerholbrook said:
Odin back to stock I would think should alleviate your problem. I flashed an international modem when I was running omega rom and got flash happy when I was drunk. Had the exact same problem you are describing odin to stock worked for me
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Yo Tyler!
I was not drunk nor did I flash anything, it was going fine and suddenly, poof!,,,,,
Anyway, I tried your suggestion and IT WORKED! I also saw, (I don't know how/why) all my apps being installed automatically!
Well, almost all anyway. I had to install only maybe 3 apps, and that was all. Even my keyboard configuration that I made lots of cosmetic changes to- via the apps setup, was like I had set it up as... Weird, but great for me!
Thanks for your suggestion. It's quite odd, as one of the nandroid backups was made using the exact rom image that I used to Odin back to stock....
Nevertheless, as the Hawaiians say, MAHALO NUI LOA! Tyler No Ka OI (Tyler is the best)
Aloha...

Glad I could help. The modem isn't in your back up that's why back ups won't fix this problem. As for apps, it's from syncing your Google account. Aloha
Sent from my SGH-M919 using xda app-developers app

bobolinko said:
Yo Tyler!
I was not drunk nor did I flash anything, it was going fine and suddenly, poof!,,,,,
Anyway, I tried your suggestion and IT WORKED! I also saw, (I don't know how/why) all my apps being installed automatically!
Well, almost all anyway. I had to install only maybe 3 apps, and that was all. Even my keyboard configuration that I made lots of cosmetic changes to- via the apps setup, was like I had set it up as... Weird, but great for me!
Thanks for your suggestion. It's quite odd, as one of the nandroid backups was made using the exact rom image that I used to Odin back to stock....
Nevertheless, as the Hawaiians say, MAHALO NUI LOA! Tyler No Ka OI (Tyler is the best)
Aloha...
Click to expand...
Click to collapse
If you chose to have Google back up and restore your apps, it will do just that.