Database Develop

[Q] How to get rid of this "congrat" message after new update

I think I successfully installed the new update last night.
But everytime I reboot the phone, this same message keeps popping up.
----------------------------------------------
Congratualtions!
New software is update for phone is installed.
Phone is ready for use.
----------------------------------------------
*When I click Software Update again, it says "No Firmware"
*My phone also tries to connect to DM server right after every single boot
*My phone was never rooted, never tempered with.
There is something wrong with the update. Will this message go away in time?

tommae said:
I think I successfully installed the new update last night.
But everytime I reboot the phone, this same message keeps popping up and it seems the boot-time got slower than before.
Congratualtions!
New software is update for phone is installed.
Phone is ready for use.
Will this message go away in time? do I need to disable it from somewhere?
Click to expand...
Click to collapse
Mine did it maybe the first 5 times, but it seems to have gone away now

I am seeing the same thing. I think I've seen it 4 or 5 times by now. Will try a few times, to see how many times more it does that.
btw, mine's rooted, with stock firmware.

I rebooted at least 20 more times but the msg still pops up . Mine has never been rooted btw.

The problem isn't just the message.the update is being downloaded and installed everytime I reboot. In one instance, I was in the basement with bad signal, and it took about 30mins before it finished the update - and all that time, it wouldn't let me go past the password screen (my corporate acct requires me to have a password on the device).
So, is it just the 3 or 4 of us with this problem?
Sent from my SAMSUNG-SGH-I897

Try maybe rebooting through recovery (using the 3 button trick?)

Brynne85,
Could you explain the 3-button trick?
Thnx.
Sent from my SAMSUNG-SGH-I897 using XDA App

If u are getting the message that.....your update was installed successfully.... after ever reboot of the phone. In order to get rid of this message you need to dial this code from your phone. Code is *2767*3855# (be aware that code will factory format you phone so what this means is that u will loose every thing on the phone. For example: downloaded apps etc. I got this advise from samsung level 3 tech support. I did this on my brothers stock samsung captivate not rooted or anything, just stock. Also i am not responsible for anything that happens to u phone due to being rooted or whatever when preforming factory format. Backup u stuff like contacts or whatever.

hkk said:
Brynne85,
Could you explain the 3-button trick?
Thnx.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Turn your phone off, then press both the up & down volume buttons (hold them in) then press and hold in the power button as well. Continue holding all 3 until the ATT logo shows up, then let go of the power button, and a few seconds later, let go of the volume buttons. Your phone should boot up into a recovery console with blue letters. You'll use the up/down volume & power buttons to navigate this. But to do a reboot, I believe it's the first option and it will tell you to press the power button to "select" it...
May wanna try that before doing a whole format of your phone, but can't promise it'll work :-/ I just know mine quit doing after about 5 times and I'm pretty sure at some point between those times, I did this recovery thing just to see if my buttons worked (as some reported they couldn't get this to happen for them)

[Q] Foce close error all installed apps not showing 2nd time...

Hi,
I have a rooted GT-i9000m (bell Galaxy S Vibrant). I used the one click lag fix to root my phone and it works fine.
A few days ago out of no where all the apps started auto closing as soon as i opened them and then both the menu and back touch buttons lit up and the screen went black. I held the power down till it rebooted only to get and error with com.android.calendar even tho I never use the app. When it finish's booting none of my installed apps are showing.
The first time it happened with com.android.app and I did a full wipe and factory reset and just reinstalled everything.
Ideally I don't want to system reset to factory settings again and lose all my files and notes that i copied back on to the phone 2days ago...
Please note I have tried clearing the data for the calendar app in settings -> apps and i cleared the calendar back up. My problem is that none of my installed apps are showing...
(Update) I also cant reinstall or update apps due to a Installation error - Insufficient storage. But there's room on both SD cards. I also set 850mb for apps when i did the one click lag fix and i don't have 850mb of apps installed.
(Update 2) I did a factory reset again this time i didn't format the internal and external SD cards. (It works like new again) Thus I got to keep all my personal files and ring tones ect. The only thing that was deleted that I didn't back up is my Notes. This leads me to my new question whats best for backing up apps on a rooted SGS (bell Vibrant)?
If anyone has answers they would be much appreciated.

i had the same problem
install rom manager from the market place
there is a option in there "Fix Permissions" just run that and it will fix it up for you
only takes 1-2min to run

Tried what you said but i cant install anything... I get Installation Error - Insufficient storage available.

I now understand the cause of the problem. I change my battery once and some times twice a day. At first I would wait for the long shut down (untill the screen goes totaly black) and then take off the back and swap out the battery. At least 3 times the phone would boot up and ask me for the network unlock code (I bought the unlock code directly from bell for 75$). I found this rather annoying so i tried just taking the battery out wile it was on (idle) and it appeared to work flawlessly at least 20-30 times before the phone would start to do an endless force close loop cycle. This kept forcing me to do a factory reset on the phone. I can only assume the one click lag fix and my disregard for the need of the shutdown before removing the battery must be all the cause of my problems.
I will try and see if my phone is more stable with out the one click lag fix.

nope that is not the cause of the problem
but it sounds like you are another victim of the lag fixes that is killing your internal SD card.
not the fault of the lag fix, it just make the problem apear sooner than later

I have been having a similar issue and I'm using Voodoo lagfix. I think it's because I took the battery out before it had completely shut down.

read this
http://forum.xda-developers.com/showthread.php?t=793404

Well the phone bit the dust today. I opened up google maps to look up an address and it crashed with the usual error. So i rebooted the phone and now it stays stuck at the boot logo. (the glowing S with both touch keys staying lit) So i did the recovery thing again but this time I had to do the Vol-up + home + power in order to get the phone working some what. IDK but it wont let me log into my google account to sync my contacts. My APN settings are correct and working and I even tried off my Wifi at home. I'll just hope its a google problem and not my phone acting up. Thanks for the pointer to the bad internal SD. That may be the problem kinda hard to prove it to Samy thoe...

I get force close errors after about 4-7 days of use. Now its gotten worse. A few days ago I was looking up an address and my phone crashed and rebooted it self. It then hug at the S boot logo for 20mins. I got to my friends apartment building to find my phone still stuck at this boot logo. I couldn't remember his apartment number or buzzer code... Normally i just check my contacts list and buzz the code. I was standing out side in the Canadian fall cold wind trying to get this phone to work... OMG i almost just smashed it on the spot. Anyways I remembered about something i had read on this forum about the recovery mode ( i had used it to root ) so i tried that out got the little menu and tried every option before having to do the dreaded factory reset. Well nothing work with the exception of the factory reset it got my phone working in about 5mins... LOL
Anyways I thought I might try upgrading the firmware when I got home. What a mistake... I cant control my phones MP3 player via my bluetooth car stereo any longer. Tried everything even a factory reset and formatting the internal and external SD's. I tried running it with out rooting it again and with out the lag fix in hopes that I wouldn't get a force close error. Wouldn't you know it about 5 hours after the factory reset un-rooted just after i finish coping over all my music. I get a force close error! So I tried again and this time the phone ran for about 30hours before it started giving me force close errors about the email now...
Sigh I've tried just about everything in my power to make this phone work. So I assumed it must be the phone... I called Samsung up to get a RMA going... Wouldn't you know it they tell me that I have to call my carrier to get it RMA/repaired. I try to explain that I bought the phone with out a contract and bought the unlock code from Bell so I could use it on Fido. They tell me to call Fido... ROFL Fido wouldn't even give me their APN settings when i got this phone so knew they would be of no help. They don't even have one android phone in their line up i tell the sammy rep. So they tell me I should go back to the Bell store I bought it from to get it repaired/RMA'ed.
I doubt Bell will be of much help but here's hoping.
Do you think my phone is broken, bad flash, buggy memory, ect and needs to be RMA'ed?

Update...
I got my phone back from repairs 2 weeks ago. They flat out replaced the phone for a new one. This was a huge headache for me because the new one wasn't unlocked. Took Bell 2 hours to get the new one unlocked wile my wife waited out side double parked downtown! (I thought it would be a quick pick up and I would be out) The blue-tooth works flawlessly again!!
Much to my dismay the replacement phone has started acting up much like my first one did. It gets several force close errors a day and has gotten to the point where it no longer can send or receive text messages (using Handcent). The stock Music Player app also force closes at random with more frequently. It looks like I got another Lemon. This time around I did NOT root, lag-fix, or flash firmware. I will be sending it for repairs as soon as I can afford to buy another phone to use wile this one is off at repairs. My back up phone is a 3~ year old Iphone3g that my son has made his... (cracked screen, vol rockers dont work, power button is jammed in, the LCD screen it self is bleeding on the top edge)
The Vibrant never let me down other than as a phone. As a divx player or using all-share it rocks! I use these features A LOT to play my 720p divx movies on any TV or the projector in the bedroom .
with that being said I might keep the phone just as a portable movie player to bring from place to place and put my sim in something more stable.

Boot loop

And now I'm boot looping won't go past n color startup animation wth
Sent from my Cyanogen Mod EVO using Tapatalk

I had that problem on my NC when it was rooted. Luckily I had another problem that let me get out by the 8 times reset manual method. Mine would occasionally update itself back to version 1.0.0. When it did that I managed to reset it & now a new NC is on its way to replace this one.
This probably won't help solve the issue but at least it lets you know you're not alone.

Mine boot looped and I did the full 8X reboot thing and then the 3 button data reset. All of that puts you back to "out-of-the-box" stock. You can then redo the autonooter rooting procedure.

Can't get out
I am stuck in a boot loop and cant get out.
First it was stuck on the droid boot animation from the auto config. After I put the autonooter card back in it started looping the rooted boot animation.
Did the 3 button thing and that forced an update but went back to bootlooping the rooted animation.
Then did the 8X reboots manually and that also forced the down arrow update, but then it still bootloops.
I tried getting in from PuTTy (as admin) but it never connects. Do I just use port 22? (to 192.168.2.2 with Data and username as root?)
adb doesn't work... going to bed now and will try again tomorrow after work.

What i had to do to resolve my issue was that was to do the 8x reset to trigger the factory reset of the OS and then do the 3 button reset of the user data. In my case it was a self tweaked issue with an app permisson. If I remember right the key combo is Power+VolUp+"n" key. Try this and let us know.
Sent from my NookColor using XDA App

Bigger Issues.... First Brick?
Nate731 said:
What i had to do to resolve my issue was that was to do the 8x reset to trigger the factory reset of the OS and then do the 3 button reset of the user data. In my case it was a self tweaked issue with an app permisson. If I remember right the key combo is Power+VolUp+"n" key. Try this and let us know.
Sent from my NookColor using XDA App
Click to expand...
Click to collapse
So ... I left my Nook in what I thought was an "OFF" state last night, only to bring it to work and find it says "Battery too low to Power on" "Please wait 15 minutes and try again"
I think... no worries... plug it in and let 'er sit for an hour.... an hour passes and I'm still getting the same screen.
Is this better or worse? let me see...
1) if it stays like this, I can return/exchange it at B&N and they won't be able to verify that it was rooted due to non-bootiness
2) If it eventually boots, I will have to try to get it out of bootloop.
3) If it comes to life and I can't get it out of bootloop, I will drain the battery again and go back to #1.
Any thoughts besides this current train?

sort of working?
OK....
so after charging on USB port (all I have at work today as I forgot the base to the charger), it will bootloop again... yay!
problem is... the bootloops take too much juice and won't allow me to fail 8 reboots. I can't even charge it up enough since I'm on USB charging and it keeps trying to turn itself on.
2 Options i see:
1) Go home and charge it on the wall and see if that helps
2) Discharge it to death and return within my 30 days (X-mas gift)

Doubt this will work, but have you tried putting in an autonooter sdcard and then plug it into the usb? If it tries to boot maybe it will boot from that sdcard?

Boot from the Froyo SD card, then fix /rom/devconf/BootCnt from ADB.

Cal you never mentioned if you cleared the user data... Did you?

Nate731 said:
Cal you never mentioned if you cleared the user data... Did you?
Click to expand...
Click to collapse
If you mean the 3 button reset? Yes.
If not... I did not because I'm not aware of it. (couldn't through the UI of course)

cal3thousand said:
If you mean the 3 button reset? Yes.
If not... I did not because I'm not aware of it. (couldn't through the UI of course)
Click to expand...
Click to collapse
Try Geezer's tip but do this:
Do three button reset WITH the autonooter card in there.

Got it working
Finally got it working after creating a Nookie Froyo card and booting off of that.
Then I reinstalled ADB on my work computer and reset the BootCnt file to 8...
that successfully restored /system and then the 3 finger trick actually gave an option to wipe.
Now to start over.
New Question: How likely is this hardware related and should I be looking to replace it before my 30 days is up>?

I ran into the same problem, trying the same solution - any luck the second time?

JasonBunting said:
I ran into the same problem, trying the same solution - any luck the second time?
Click to expand...
Click to collapse
My Nook has been great since the fix. But I also needed to use a program to turn off Wifi when I turn the display off.
I did it all from my Nookie...

confused?!
I was wondering how you fixed this..i have read everywhere, but nothing...im stuck in the nook co screen. This happened right after i plugged my nook to charge after my battery was drained...thnks

The phone shuts down when the screen goes black.

Hello,
Two days ago I upgraded to Gingerbread from 2.2.1, both times using Kies. I did the factory reset, CF root and put all my apps back with Titanium. No system backup was restored.
Suddenly the phone started to shut down if the screen shut down, regardless if I did a quick press on the powerbutton or let the screen time out. No lit buttons and the computer doesn't recognise the phone. The only way to start the phone was to press the powerbutton for 10 seconds. If the phone is correctly shut down you only need to press the button for approx two seconds for it to start.
I did another factory reset and the phone worked ok for a day but the problem showed up again today. EVERY single time the screen goes black the phone shuts down.
Edit:
I don't think the phone is shut down. When I call it I get a beep in the other phone as if nobody is answering. If I shut down my phone correctly and call it I get a voice that says "the number you dialed cannot be reached".
Any ideas?

I have the same problem with my phone at the moment, I have tried numerous software versions and all are the same, I think it is either a battery issue or a complete phone fault.
If it's still under warranty see if they will replace it.

You updated twice from what rom stock custom /original
Twice why ???
What network was the Kies firmware for re phones product code .
A flash through Odin to stock Froyo with pit 512 and repartition checked could well fix any faulty rom problem .
jje

ulsa said:
Hello,
Two days ago I upgraded to Gingerbread from 2.2.1, both times using Kies. I did the factory reset, CF root and put all my apps back with Titanium. No system backup was restored.
Suddenly the phone started to shut down if the screen shut down, regardless if I did a quick press on the powerbutton or let the screen time out. No lit buttons and the computer doesn't recognise the phone. The only way to start the phone was to press the powerbutton for 10 seconds. If the phone is correctly shut down you only need to press the button for approx two seconds for it to start.
I did another factory reset and the phone worked ok for a day but the problem showed up again today. EVERY single time the screen goes black the phone shuts down.
Edit:
I don't think the phone is shut down. When I call it I get a beep in the other phone as if nobody is answering. If I shut down my phone correctly and call it I get a voice that says "the number you dialed cannot be reached".
Any ideas?
Click to expand...
Click to collapse
It seems like when the device goes to sleep it cannot wake up any more. I'm getting the same problem by the way. The only way to come out of it as you mentioned already is to hold the power button for 10 seconds or pull the battery out.
My steps for upgrading from Darky's 9.5 were:
1) Odin stock JVB with bootloader (repartitioned with pit512)
2) Odin deodexed JVB without bootloader
3) Odin CF-Root
4) Applied lagfix through ext4
5) Flashed Gingerbread theme (v3 and after it v4)
6) Odin Voodoo
(with a reboot between each of the steps)
And that's about it. Have you applied any modifications or hacks?

JJEgan said:
You updated twice from what rom stock custom /original
Twice why ???
Click to expand...
Click to collapse
I did not write that very clear. I meant that both the upgrade to 2.2.1 a couple of weeks ago and the upgrade to 2.3.3 was done with Kies, not Odin.
What network was the Kies firmware for re phones product code .
Click to expand...
Click to collapse
NEE
I did another factory reset... Odin flash is next.
I updated the phone to Gingerbread with Kies.
I then rooted it with Odin (CF)
I have not done any modifications other than that.

I'm starting to think it maybe be some root app's fault. When I reinstalled using Odin to stock all was fine, then installed CF-Root, but as soon as I restored my apps it started happening again. I froze SetCPU, NoLED, and WidgetLocker, and so far nothing bad has happened. Weird. Fingers crossed that it stays this way...

martino2k6 said:
I'm starting to think it maybe be some root app's fault. When I reinstalled using Odin to stock all was fine, then installed CF-Root, but as soon as I restored my apps it started happening again. I froze SetCPU, NoLED, and WidgetLocker, and so far nothing bad has happened. Weird. Fingers crossed that it stays this way...
Click to expand...
Click to collapse
I only have SetCPU of the ones you listed.
Did you do a factory reset before you frooze those apps? If not, I guess you have found the problem.
Maybe you should try to unfreeze them one by one?
Edit: One of my settings for SetCPU was to set the CPU to 100 MHz when the screen turned off. Could be something...

I found this in another forum:
"i figured out why SetCPU makes my phone never wake up, the settings i was using was ondemand 100 min 1000 max. SetCPU is set to 100 in standby and this is just too slow and puts the phone completely to sleep.
ive since moved up the phone to 400 min and ive gone a day without any sleeping.
"
http://samsunggalaxysforums.com/showthread.php/313-i-figured-out-why-SetCPU-makes-my-phone-never-wake-up

ulsa said:
I only have SetCPU of the ones you listed.
Did you do a factory reset before you frooze those apps? If not, I guess you have found the problem.
Maybe you should try to unfreeze them one by one?
Edit: One of my settings for SetCPU was to set the CPU to 100 MHz when the screen turned off. Could be something...
Click to expand...
Click to collapse
Yes, I factory reset. But it does look like SetCPU. I unfroze WidgetLocker overnight and no problem.
I also had a 100MHz setting when the screen turned off. So I think we have found the problem I guess I'll ask Chainfire why 100MHz no longer seems to work, but it did on 2.2. I'm a bit worried about the battery now...

[Q] Woke up to a less functional Captivate..

Long time lurker, first time poster.
I woke up today to see my captivate screen showing blank screen (active black screen with buttons lighted up) being unresponsive. It was on it's charger from the night.
I pulled the battery to shut it down. It rebooted. I thought nothing about it until I tried to use it about an hour later.
I have had it on stock Froyo, with no root. Never have flashed any other ROM besides updates through kies.
Problems and things I've noticed so far:
No puzzle lock screen. Can't find it under "set screen lock". Only None, Pattern, PIN, Password available.
Home button and search button do not function(they light up like they are pressed, but not action occurs in any apps or home screen).
No data. Usually i'd see edge or 3g, but I have no data connection.
Text messages wiped. None available through "Messages"(though call log shows history of messages).
Keyboard was on stock android rather than swype(since changed back to swype).
Holding power button only shows "Power off" option. Before there was at least Airplane mode.
GPS was on(I hardly ever use it).
Location settings seemed to be default("use wireless networks" was unclicked)
Most other settings/app data seems fine.
About phone info:
Model Number: SAMSUNG-SGH-i897
Firmware version: 2.2
Baseband version: I897UCKB1
Kerner version: 2.6.32.9
Build number: FROYO.UCKB1
Click to expand...
Click to collapse
Other related things:
Day or two before I received a text message from AT&T to download Kies and use Froyo(Don't remember exact wording, lost the text message, but something to the effect it looked like a mass mailing text to update to Froyo using Kies). I was already on Froyo(flashed as soon as I found out it was available few months back).
I also got a text message about downloading their at&t app to manage my minutes and pay my bill(also already had that app).
My Captivate would randomly freeze/unresponsive a few times, but I didn't think much of it.
Google Music app seemed to randomly start playing the audio file i paused(just in my pocket, or once when i put headphones in to make a call).
Searching the forums, haven't found too much related.
One thread suggested using "home switcher", which I have tried(both Froyo and regular versions, though can't press home button for Froyo version). Neither seems to know what my default Home App is, but it only sees TwLaucher(I only have TouchWiz).
Tried installing an alternative launcher(ADW,LauncherPro), still no home/search button.
I'm without my computer for the weekend, so I can't backup my files and reset to factory just yet.
Anyone have any thoughts to fix this or know what may have went wrong?
I might finally make the jump to a Custom ROM if it'll fix this.

Yes, you should either flash a custom rom or do a factory reset. I will say an event similar to this, also involving text messaging, is what made me make the leap to Assonance, and then Serendipity, and I haven't looked back.
Sent from a state of Serendipity

At the least, try a master reset.

You're not alone....
Two Saturdays ago, I woke up, grabbed my phone to see what time it was and my phone was going haywire. It as blinking, flickering and rebooted on its own a couple of times...without me touching it.
When I DID manage to access the phone after a reboot there was no connection. I couldn't call, send/receive texts, nor could I access most of the features (during one of the haywire moments, the phone popped open my "Gallery" folder and started running a slideshow and then shut down. Again, all without me touching it!) There was a distinct blue circle with a slash where the 3G bars used to be on the top right corner of the phone.
I did a factory reset and didn't help. Wiped everything off the phone, but the device was still going nuts.
I got the phone in mid-December and have absolutely pampered that thing. Never dropped, never scratched, never abused. So I was surprised when I took it into the AT&T replacement center that the lady told me that my battery was wet! Not the phone, but the battery. Those two white-that-turn-pink indicators are so close to each other on the phone that I can't see how one gets wet while the other doesn't.
So they give me a new phone. One thing I noticed right away was that my data usage went WAY UP with the new device. To put it in perspective, I used 100 mb of data in 29 days and 64mb IN ONE DAY with my new phone. I thought it may be a one-time fluke, but it's not. I am only 10 days into my new month and am already at 164mb out of 200mb in my plan. I have NEVER used 164 mb in the 6 months previous, let alone in 10 days.
Fun's not over yet. I noticed a lot of crashes and "Force Closes" with the new phone too. I didn't even have any apps downloaded yet and things were still crashing. Last night I pull my phone out to take a picture and...nope. Screen was all kinds of whacked out and it crashed. And still does now every time I open the camera function. I managed to get in camera mode fast enough to do a reset, but didn't work. The screen is fine otherwise. So looks like I'm back to A&T tomorrow for another round.
I'm glad you posted this, cause the same morning all this happened -- literally, within 10 mins of me waking up -- my computer (brand new - 2 days old) went berserk and shut off and my stereo started flipping channels, turning the volume, treble, bass up and down..BY ITSELF without me touching ANYTHING! It was pretty freaky. I wondered if I was struck by lightning the night before.http://media.xda-developers.com/images/smilies/eek.gif

I was finally able to get back home today and do a factory reset. This (somewhat) solved the problem. Everything is mostly back to normal(home button and search button work on home screen, lock screen is there).
Lost a couple of game saves as I had no method to pull a save file(was doing adb pull on some known file locations).
I did run adb logcat before resetting, and home button and search button seemed to trigger something, just not follow through(Search button did work in a card game as a forward button and home button worked in the kies app to exit, just never as a return to home button in apps).
I'll be looking to root and flash a custom ROM, especially root so I can do a proper backup in case anything like this happens again.

I just want to say thank you posting in q&a and doing research before and after your flashing started. Then searched after your problem. You're a new member of a breed that are few and far between. I will hit your thanks when I get on my computer, app doesn't have it. You will go far here.