Database Info

[Q] Trying to bring I9020A back to stock?

I am sending my phone back into samsung for repair, and I want to bring it back to its stock condition. I have unlocked the bootloader, flashed CW recovery, and installed superuser with no problems, however cannot seem to figure how to go into reverse. I understand how to re-lock the bootloader. I have read on the forums through the countless amounts of people asking this. I am however trying to use the ROM for the GTJ61 build found from this thread http://forum.xda-developers.com/showthread.php?p=13478981 When I try to use Clockwork Recovery, and go to restore, it states there is a MD5 mismatch. Am I suppose to install from zip or update from SD with CWR, or should I try to flash everything back onto there? I do not know what to do. Am I even trying to use the right ROM? The GTJ61 build is the original build that came on my phone, but would another one work?

follow this thread http://forum.xda-developers.com/showthread.php?t=1033269
all you have to do is clear your data, flash the stock rom and stock recovery, and then lock the bootloader

Thank you very much. I figured it out. All I have to do now is destroy the evidence on my sd and seen my NS away.

I realize superuser is still alive and well after I did everything. How I would I get rid of it?

I just uninstalled it. it might have gotten restored when you logged in with your gmail account. did you wipe data and the cache with cwm before you flashed the rom?
edit: did the ots update to 2.3.4 install fine for you?

I am guessing you mean ota. I ended up using the 2.3.4 rom. Should I have used the 2.3.3? Yes I did clear out the cache and factory reset.

SleepyFox said:
I am guessing you mean ota. I ended up using the 2.3.4 rom. Should I have used the 2.3.3? Yes I did clear out the cache and factory reset.
Click to expand...
Click to collapse
I did mean ota lol. my bad. where'd you get a 2.3.4 rom from?
edit: if you used the 2.3.4 rom from the thread you posted, just be aware that it isn't official. i'm not sure if the link I posted has the official rom, but you can download OTA updates with it so I would assume that it's pretty damn official lol

I don't know too much on the subject, but I'm afraid that since it is a different build in the link you suggested that I will mess up my radio settings. I don't know if it would make a difference but when I did install superuser it was from CWR and not adb from the command prompt. Do think I should use the 2.3.3 rom you suggested?

SleepyFox said:
I don't know too much on the subject, but I'm afraid that since it is a different build in the link you suggested that I will mess up my radio settings. I don't know if it would make a difference but when I did install superuser it was from CWR and not adb from the command prompt. Do think I should use the 2.3.3 rom you suggested?
Click to expand...
Click to collapse
I don't know much about it either, but I would assume that you should put it on a stock rom if you're sending it back into samsung. I could be totally wrong though

I just am not sure if having super using on there would make a difference. They are suppose to do a wipe anyway. But I will contact them to make sure. It would still be nice to have superuser gone though.

SleepyFox said:
I just am not sure if having super using on there would make a difference. They are suppose to do a wipe anyway. But I will contact them to make sure. It would still be nice to have superuser gone though.
Click to expand...
Click to collapse
I would guess that superuser would be one of the first things they check for to see if you broke warranty. you could just uninstall it and wipe everything through cwm again to make sure it's gone

I managed to fix everything. I just was searching through the system folder of the 2.3.4 rom and to my surprise there was little old superuser. So I deleted the .apk and bin files. After that I restored the ROM. Fixed everything. The stress of sending in a phone with superuser is gone and I am back to being stocked

Two questions for you OP:
1. How do you have a warranty on a I9020A? Is it the subsidized version from Best Buy (i.e. "AT&T's sanctioned model")
2. Why do you need warranty repair? What broke?

Yes I got my phone from best buy. I just registered the imei with samsung and I am under the 1 year warranty. I have a problem with my battery draining 80% in 6 hours little to no use with all radios besides 2g turned off. I know that the NS has not so stellar battery life, but there is genuinely a problem with mine. It cannot even survive for half a day.

Hmm, I had that very issue with three past i9020a's (two from Amazon, one white one from Newegg). They were all the Rogers model, which is said to be identical to the one Best Buy is selling as a subsidized model.
I just bought another i9020a on eBay (no, I never learn) and hope to try some fancy methods to save on battery life (ROMs, etc). I also experienced VERY slow 3G with the i9020a on AT&T's 3G network here in the US. Like 300kbs download slow. I read that if you flash the radio to KB3 it gets very fast, like HSPA 3G should be.
I don't care about rooting and flashing because my phone will not have a warranty. I do, however, suspect that there is nothing wrong with your phone, rather the battery life is just random. One of the i9020a models I had drained a fresh charge in like 3 hrs of sitting idle w/full bars. The phone was burning hot. I restarted it, charged it up, and it lasted over 16 hrs the next time. Very erratic and strange, but that seems to be par for the course with the NS.

I would first see if the phones you bought were registered yet. You never know when you would need samsung to take care of something for you. The correct radio for the US ATT is UCKE1. You should be getting data speeds of about 3.3 megabits. My battery has been consistently low.

SleepyFox said:
The correct radio for the US ATT is UCKE1.
Click to expand...
Click to collapse
So that may explain what's different between the international (i.e. Canadian) I9020A and the "Best Buy" AT&T sanctioned I9020A...a different radio?
Is it possible to flash the KB1 radio of the Canadian I9020A to the AT&T friendly UCKE1 radio?

my phone kind of messed up

I have a problem I dont even know what to do... maybe one of you can suggest me something...
i bought htc thunderbolt on a first day when it came out then some time later after drooling over my phone my boss got one too ;p
when last update came out he went ahead and upgrade his phone and his hotspot feature disappeared, yet i didn't do mine as i still wanted to use that feature...
now i s-off (whatever that is) and i even rooted my phone using this Revolutionary method (without wiping out my phone (thank god)) and i even installed wifi tether.
thankfully i also installed clockworkmod recovery *and* made a backup because every once in a while even though my radio (internet/wifi) is off verizon somehow kicks my phone into enabling radio (internet) and start downloading that update unless i cancel it, obviously when i dont see it i can't really cancel it... so what happened i wake up and i see android dude next to a question mark, my assumption that since i didn't really hit cancel it went ahead and apply update and probably because i mod it it fails somewhere along the line so i have to go to recovery through hboot and restore my backup...
i'm kinda of getting sick of doing it, my voip analog adapter at home died and i'm waiting one from my voip provider, so now my htc thunderbolt acting up with this stupid verizon update so its becoming really hard to communicate with outside world from my walls ;p
so any ideas how to deal with this situation? maybe either disable update somehow (since i've got root maybe *now* i should have an ability to disable it) i mean i even tried another rom: synergy ... oh yeah, apparently that rom isn't compatible with my radio and now i need to flash radio too in order to get that synergy to work... i mean what a pain in the ass this whole mess becomes (thanks to vzw,htc for not giving us gingerbread in october ice cream coming out already and we still using froyo ... so stupid!) or maybe somehow, dont even know if its possible but to apply that update without android dude w/ question mark... maybe roll everything back: unroot it, s-on then update it and back s-off and root it.
i'm confused... anyone?

You don't have to restore a backup to fix the failed update. Just boot into clockwork recovery and wipe cache. I would suggest updating to a rooted version of the newest OTA. Also if you go to about phone or software updates, I can't remember which, there is an option in there somewhere to uncheck scheduled update checks. I THINK that will stop it. If not, updating manually to a rooted version of the update will. Though I think you will have to update your radio with that as well. A custom ROM would also solve this.
Here is a link with some newer builds and radios:
http://forum.xda-developers.com/showthread.php?t=1081930
Sent from my HTC Thunderbolt

AT&T One X not keeping accurate time

I've noticed that the clock on my HOX runs slow. I have it set to automatically update the time and time zone. After about a day it will be 8-10 minutes slow. If I reboot the phone, it appears to update the time with AT&T and correct itself. I've also set the time to not automatically update and set the time manually. By the next day, it will be off again. That means the issue is not that AT&T has their time set wrong.
I'm running the stock 1.73 ROM. I have rooted the phone, but done virtually nothing else.
Is there a parameter to set how frequently it syncs the internal clock with the carrier time signal?
Does anyone else have this same issue? If so, was it fixed in a newer ROM? I'm not having any other issues, so I have not been any hurry to upgrade.

DonS said:
I've noticed that the clock on my HOX runs slow. I have it set to automatically update the time and time zone. After about a day it will be 8-10 minutes slow. If I reboot the phone, it appears to update the time with AT&T and correct itself. I've also set the time to not automatically update and set the time manually. By the next day, it will be off again. That means the issue is not that AT&T has their time set wrong.
I'm running the stock 1.73 ROM. I have rooted the phone, but done virtually nothing else.
Is there a parameter to set how frequently it syncs the internal clock with the carrier time signal?
Does anyone else have this same issue? If so, was it fixed in a newer ROM? I'm not having any other issues, so I have not been any hurry to upgrade.
Click to expand...
Click to collapse
As far as I know, if you disable automatic time and turn off the phone the phone doesn't have internal clock, meaning if you reboot it will be out of sync. With automatic checked, I'm guessing it only syncs after every boot or when you get signal again.
Sent from my HTC One X using xda app-developers app

Someone else had a very similar issue. Not sure if they resolved it. I will try to find the thread and link it here.
Though, the first thing I would do in your case is update to the latest OTA if you want to stay stock.
Edit: Here's the link http://forum.xda-developers.com/showthread.php?t=1665559&highlight=clock Looks like updating did solve the issues. So go ahead and do that.

Thanks for the link. At least two people in that thread noted the issue was worse with the 1.73 ROM. I'll probably go through all the steps to change the CID to the SuperCID, upgrade to the 1.85 ROM, unlock the bootloaded, install a custom recovery, reroot, and remove bloatware. Then I'm set to use custom ROMs.
Since I'll void the warranty from AT&T I was waiting to make sure there weren't any quality issues with the phone. I also needed a real reason to upgrade. Since everything else was working fine, I was in no hurry to upgrade.

DonS said:
Thanks for the link. At least two people in that thread noted the issue was worse with the 1.73 ROM. I'll probably go through all the steps to change the CID to the SuperCID, upgrade to the 1.85 ROM, unlock the bootloaded, install a custom recovery, reroot, and remove bloatware. Then I'm set to use custom ROMs.
Since I'll void the warranty from AT&T I was waiting to make sure there weren't any quality issues with the phone. I also needed a real reason to upgrade. Since everything else was working fine, I was in no hurry to upgrade.
Click to expand...
Click to collapse
By the way, the order is root -> supercid -> unlock -> recovery (use TWRP) -> flash custom romzzz
You don't actually need to go to 1.85 the official way or through the RUU. You can just flash a custom rom directly from any version provided that you wipe.

stnguyen09 said:
By the way, the order is root -> supercid -> unlock -> recovery (use TWRP) -> flash custom romzzz
You don't actually need to go to 1.85 the official way or through the RUU. You can just flash a custom rom directly from any version provided that you wipe.
Click to expand...
Click to collapse
I was thinking of going to the stock 1.85 ROM only remove the bloatware instead of a custom ROM. The order I mentioned is documented in a how-to method posted on another thread. With the process I listed I can always go to a custom ROM later on.

[Q] Flashing to stock - phone force closes process com.android.phone, help

Please bare with me since this is the first time having to post for an issue since I usually find an answer on your forums
So here's the situation.
I bought the photon q 4g lte from ebay and it came with the unlocked bootloader.
Needless to say it was with the stock ics and i tried to find a jellybean update because it wasn't taking the ota and ended up going with cyanogen since i had no problems before. However those phones i had before were with sim cards not cdma.
I found out i couldn't update prl or profile manually without having to do something on the pc.
So after searching left and right i found i could use rsl lite (I used 6.1.5) and eventually found the "stock" file from this post
http://forum.xda-developers.com/showthread.php?t=2095536&highlight=rsd+lite
I did the stock jellybean, got it to go through the process and it booted up with no errors.
However, when it boots into the os it pops up a force close on omadmclient_sprint_dataservice and eventually also on the process com.android.phone.
I tried putting it in airplane mode to see if the service error would go away but it didn't work for the process part crashing.
I tried re-flashing, deleting cache in recovery, doing a data/factory reset in recovery and the one time i was able to do a data factory reset within the settings menu.
I could not find anyone that said they had a rom that worked with sprint and updating prl within the rom, if anyone knows of one let me know and i will flash it through rsd.
Otherwise does anyone have an idea of what could be happening because googling the omadmclient part did not pull up anything specific and pulling up the process issue for other phones has not helped me either.

Was this a hacked GSM phone, or are you using it as CDMA?
I've never heard of people having FC issues after flashing a FXZ from RSD. Which one did you flash? Android 4.1.2 - Sprint US - 9.8.2Q-122_XT897_FFW-5 (No simlock) ?
If you are on stock, you should be able to update the PRL within the ROM.

I was trying to use it with cdma network through sprint. and yeah that was the file i downloaded, had to remove the getvar to get it working but flashed with no errors after doing that.
As for updating the prl i can barely navigate through the phone, there is no home page loading and the process pop comes up often enough that its hard to go through the settings

crispy6 said:
I was trying to use it with cdma network through sprint. and yeah that was the file i downloaded, had to remove the getvar to get it working but flashed with no errors after doing that.
As for updating the prl i can barely navigate through the phone, there is no home page loading and the process pop comes up often enough that its hard to go through the settings
Click to expand...
Click to collapse
Sounds like something went wrong mate. Are you already activated on Sprint? I don't know if that would matter, it might.
I would honestly redownload and redo the RSD process.

arrrghhh said:
Sounds like something went wrong mate. Are you already activated on Sprint? I don't know if that would matter, it might.
I would honestly redownload and redo the RSD process.
Click to expand...
Click to collapse
I originally tried to activate the phone through cyanogen and then when the rep said he couldnt do it because of the lack of prl to update within the rom we just setup the activation back on the old phone/ That phone is working on the network.
I re-downloaded the file just in case and re-flashed but same problem. The only thing i thought of was maybe updating the radio but since its a stock rom it should work out of the gate. whats also weird is i tried turning wifi on but it didnt work either.
Anychange you know of a rom that works with sprint. I dont care if its stock since i would probably root later again.

crispy6 said:
I originally tried to activate the phone through cyanogen and then when the rep said he couldnt do it because of the lack of prl to update within the rom we just setup the activation back on the old phone/ That phone is working on the network.
I re-downloaded the file just in case and re-flashed but same problem. The only thing i thought of was maybe updating the radio but since its a stock rom it should work out of the gate. whats also weird is i tried turning wifi on but it didnt work either.
Anychange you know of a rom that works with sprint. I dont care if its stock since i would probably root later again.
Click to expand...
Click to collapse
Which one are you flashing?
Try another perhaps...? I honestly have never heard of this. It sounds like the phone might be damaged, or the RSD process just did not flash correctly.
I guess I should ask, was the phone modified at all for the GSM SIM slot mod? I wonder if having a non-Sprint SIM in is messing with it... That is just a shot in the dark.

arrrghhh said:
Which one are you flashing?
Try another perhaps...? I honestly have never heard of this. It sounds like the phone might be damaged, or the RSD process just did not flash correctly.
I guess I should ask, was the phone modified at all for the GSM SIM slot mod? I wonder if having a non-Sprint SIM in is messing with it... That is just a shot in the dark.
Click to expand...
Click to collapse
so far the only rom i tried was 10.1 cyanogen and the stock rom for jellybean. However for the stock rom it doesnt let me downgrade to ics with rsd 6.1.5 do you think if i downloaded an old version i could downgrade to a lower stock rom?
Also I honestly had not looked for the cdma roms since most of what i saw was troubleshooting related for this phone but i just saw this rom -AOKP 4.2.2 (Android Open Kang Project) (CDMA&GSM) that you created - http://forum.xda-developers.com/showthread.php?t=2293892
I re-rooted and installed that one and it looks great, just wondered how you got sprint to activate the phone or if you had done it before changing the rom? Also how would the prl and profile be updated.
Lastly the wifi wasn't turning on this time either, it did work initially when i got the phone so that has me stumped.

crispy6 said:
so far the only rom i tried was 10.1 cyanogen and the stock rom for jellybean. However for the stock rom it doesnt let me downgrade to ics with rsd 6.1.5 do you think if i downloaded an old version i could downgrade to a lower stock rom?
Also I honestly had not looked for the cdma roms since most of what i saw was troubleshooting related for this phone but i just saw this rom -AOKP 4.2.2 (Android Open Kang Project) (CDMA&GSM) that you created - http://forum.xda-developers.com/showthread.php?t=2293892
I re-rooted and installed that one and it looks great, just wondered how you got sprint to activate the phone or if you had done it before changing the rom? Also how would the prl and profile be updated.
Lastly the wifi wasn't turning on this time either, it did work initially when i got the phone so that has me stumped.
Click to expand...
Click to collapse
To downgrade to ICS, you need to remove some additional lines. See this post for more information on that.
However, you should be able to update the PRL on either stock ROM.
I think I said this before, but I will say it again. You need to do PRL updates, activate the phone, and get EVERYTHING working on stock BEFORE you flash ANY custom ROM. This is just standard practice - you don't want to put the cart before the horse! Get the phone working, then play with custom ROM's.

What is the true newest firmware for the HTC One S Tmobile edition.

Hello all,
Long time reader, just started posted recently. I bought my HTC One S when it first came out, and immediately rooted it and installed the ViperOneS Rom on it. I never got the chance to recieve the OTA updates for JellyBean or any of the other firmware updates. Now, as I was reading the CM10.1 thread, it said that certain firmware updates were required to install the new nightlies. I figured it was time to RUU my phone to stock with the newest firmware, and then re-root it so that I can take advantage of the 3.4.x kernel in the new CM 10.1 releases. Anyway, I went to www.shipped-roms.com and went to ville, and saw that the newest release appeared to be the :
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe
....However, on my HTC One S news app, I looked back about two months, and it showed that Tmobile released a new RUU/OTA on June 24th, 2013. That build was labeled
RUU_Ville_U_JB_45_S_TMOUS_3.14.531.17_Radio_1.13.50.05.31_10.30.50.08L_release_320836_ICS_2_JB.exe
Now, the one on Shipped-Roms has the 3.16.x build as opposed to the Tmobile's 3.14.x. But the Tmobile has a higher number after the "release" at the end of the exe, being 320836 as opposed to 301814 on the Shipped-Roms RUU.
So does anyone know which one is truly the most recent firmware for the HTC One S. I went and installed the Tmobile One, im going to play around with it for a day or two before I root it again. It was said one of the reasons TMobile released this was to address battery drain issues for jellybean users.
The entire article is available here : https://support.htc.com/en-us/080-H...HTC_One_S™_for_T-MOBILE_ROM_Update_|6.24.2013
I ran the RUU with no problems and am now running stock, until I decide to root again. I basically posted this to make people aware that their might be a newer firmware available than the one they are using, and it isn't on any of the RUU list such as Shipped-Roms. Anyway, if I experience any problems with it, I will post. Take care - dRedmentia

dredmentia said:
Hello all,
Long time reader, just started posted recently. I bought my HTC One S when it first came out, and immediately rooted it and installed the ViperOneS Rom on it. I never got the chance to recieve the OTA updates for JellyBean or any of the other firmware updates. Now, as I was reading the CM10.1 thread, it said that certain firmware updates were required to install the new nightlies. I figured it was time to RUU my phone to stock with the newest firmware, and then re-root it so that I can take advantage of the 3.4.x kernel in the new CM 10.1 releases. Anyway, I went to www.shipped-roms.com and went to ville, and saw that the newest release appeared to be the :
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe
....However, on my HTC One S news app, I looked back about two months, and it showed that Tmobile released a new RUU/OTA on June 24th, 2013. That build was labeled
RUU_Ville_U_JB_45_S_TMOUS_3.14.531.17_Radio_1.13.50.05.31_10.30.50.08L_release_320836_ICS_2_JB.exe
Now, the one on Shipped-Roms has the 3.16.x build as opposed to the Tmobile's 3.14.x. But the Tmobile has a higher number after the "release" at the end of the exe, being 320836 as opposed to 301814 on the Shipped-Roms RUU.
So does anyone know which one is truly the most recent firmware for the HTC One S. I went and installed the Tmobile One, im going to play around with it for a day or two before I root it again. It was said one of the reasons TMobile released this was to address battery drain issues for jellybean users.
The entire article is available here : https://support.htc.com/en-us/080-H...HTC_One_S™_for_T-MOBILE_ROM_Update_|6.24.2013
I ran the RUU with no problems and am now running stock, until I decide to root again. I basically posted this to make people aware that their might be a newer firmware available than the one they are using, and it isn't on any of the RUU list such as Shipped-Roms. Anyway, if I experience any problems with it, I will post. Take care - dRedmentia
Click to expand...
Click to collapse
higher numbers not always newer builded software, since jb for the unbranded was released several months sooner than the tmobile one the higer number is logical. However there has been a ota for the unbranded going to 3.16.401.9
watch out, many people got bricked wanting to update there already updated firmware to the newest.
if its already on jb firmware and works flawlessy leave it as is, or take the risk.

real187 said:
higher numbers not always newer builded software, since jb for the unbranded was released several months sooner than the tmobile one the higer number is logical. However there has been a ota for the unbranded going to 3.16.401.9
watch out, many people got bricked wanting to update there already updated firmware to the newest.
if its already on jb firmware and works flawlessy leave it as is, or take the risk.
Click to expand...
Click to collapse
I installed the Tmobile Jan 24th RUU no problem. As I said, I rooted my phone right when I got home from the Tmobile store, so it was still running the original firmware it came with. Now Its up to date, running CM 10.1 flawlessly with the 3.4 kernel, and overall seems quicker and more responsive. Now hopefully the battery life issue gets resolved, that was the only problem I was having before. Thank you though, from what I understand this will be the last firmware update from Tmobile, so I will never have to go through that process again. The HTC One S still holds its own as a great phone, I don't see any need to upgrade anytime soon.

are you dunning CM10.1 nightlies? is it stable? Any issues with camera/ bluetooth/ 4g?
Do we need s-off for that?

myechophone said:
are you dunning CM10.1 nightlies? is it stable? Any issues with camera/ bluetooth/ 4g?
Do we need s-off for that?
Click to expand...
Click to collapse
Actually I am running the August 13th CM10.1 Nightlie, and the camera works, bluetooth works, but my damn 4g is not connecting. All my mobile data settings keep getting stuck on Edge network or worse. It said it would have taken 10 hours to download a 150 mb file....I didn't notice until I left my house earlier today because it was my day off so I didn't use my phone for work. It was working flawlessly on wifi, thought everything was going good, and once I started driving around the service would go in and out, and never made it to 4g once, I think in one or two spots it hit 3g, but most of the time it was stuck on EDGE:2 in the Phone Settings. If I can't get this issue fixed I will go back to the stable CM10, which sucks because that doesn't use the new 3.4 kernel, or use a different ROM based on that kernel.