Database Develop

[Q] Samsung Galaxy S 2.2 update - Plagued with ‘force close’ messages.

So basically, I registry hacked my PC so that I could update using the official 2.2 update in Kies for the Galaxy S.
Since I updated it, the phone has come unusable. Whenever it boots up I am plagued by force close messages (calendar storage, media, memo etc.).
I’ve tried getting into safe mode and hard resetting it. I can’t get either of these menus up. Tried holding down [vol down] key and pressing the power button, it just boots as normal when I do this.
Anyone have any ideas what’s wrong here?

I have the same problem as well, except that I am in a Scandinavian country. I did remove the lagfixes, and the only thing left was the rooting. I heard that the USB disconnected and reconnected in Windows under the firmware upgrade. When the smartphone was booted up, it still appeared to be 2.1-update1. So I did a hard reset, and that's where it begun to be softbricked with all the looping crash messages ("The process X has stopped unexpectedly. Please try again."), which are the following processes:
android.process.acore
com.sec.android.app.twlauncher
com.sec.android.provider.logsprovider
com.cooliris.media
com.android.calendar
com.sec.android.widgetapp.infoalarm
com.android.phone

alexdrans said:
Tried holding down [vol down] key and pressing the power button, it just boots as normal when I do this.
Click to expand...
Click to collapse
you have to hold down both [vol down] + [start] and then press the power button to start the phone in download mode. [vol up] + [start] and power to get into recovery mode. in all there are three buttons involved which have to be pressed all together. [start] is the big one on the front side of the Galaxy btw.
I had similar problems with the Kies update. So i wiped it clean, installed an old 2.1 version with odin and then installed on of the modifed 2.2 version from the development section here, also with odin. Now it works like a charm and with OCLF blazingly fast too.

I am experiencing the same problems...
how would i go about wiping the phone clear and back to the 2.1 version?
i only got the phone the other day and can barely use it now!
cheers

Guys i didnt wanted to open up a new thread so ill go ahead with my problem here.
The question is about the Kies Registry Patcher so i can force Kies to show me the 2.2 update.
My native country is Macedonia, and i can see two options to pick from with the Kies registry patcher for my country. One of them is the current versions i have on my phone and its representing the 2.1 update 1 android version.
To what 'Spoof Product Code As' i should set the registry patcher considering my location to get the proper update for my phone ?

alexdrans said:
So basically, I registry hacked my PC so that I could update using the official 2.2 update in Kies for the Galaxy S.
Since I updated it, the phone has come unusable. Whenever it boots up I am plagued by force close messages (calendar storage, media, memo etc.).
I’ve tried getting into safe mode and hard resetting it. I can’t get either of these menus up. Tried holding down [vol down] key and pressing the power button, it just boots as normal when I do this.
Anyone have any ideas what’s wrong here?
Click to expand...
Click to collapse
Have you tried click settings on your phone then privacy then factory reset that should solve it

Well, I had the same issue and here is what I did. I'm in Canada (not sure which thread my phone falls under as our Vibrant is not the same as the U.S. one) and my provider is Bell Canada. Well...what I did was this; I saw the update out there, so I connected through Kies, ran the update and waited nervously for it to boot. After it did boot, I got several Force Close errors, so I rebooted it. It came up more easily the second time. After it got done it's card scanning and crap, it was ready to go. BUT...I started getting random Force Close errors with different apps. I simply could not use ANY email app other than the GMAIL one itself, they just kept crashing. Handcent crashed too, but with a reboot would work. Well...this just didn't seem right as a college of mine did his at the same time and was working fine. So, today I did this; I copied ALL my useful data off the internal SD onto my external SD and then removed that external SD card. Then I formated the interal SD. Then I went and did a factory reset. After that, my phone worked perfectly! I put my external SD card back in and all is good now. Haven't had one error since. Now, before I did this, I'd get at least 1-2 Force closes per hour but I re-did my phone up about 3 hours ago now and like I said, no errors.
Maybe try this before you update:
1: Save old data off of Internal SD
2. Remove External SD card (just to be safe)
3: Format Internal SD card
4: Apply Froyo update
5: Reinsert External SD card upon completion and sucessfull reboots
6: Part-tay!!!!!

Just make sure you do a cache wipe and a user settings wipe.....you should have already backed up your stuff so worst case you will just have to reinstall everything. HOLD down Volume UP button, Home button and power button all at once, it will boot into recovery mode, use the volume rockers to select wipe cace and then use them to wipe the user settings, reboot and should be good.

Rooted NC won't restart

I did a manual shutdown because I couldn't kill some goofy NES rom app. Now it won't reboot. Do I have to replace the SD card with the imaged one every time I want to restart this thing?

No... Sounds like you medded something up when you manually rebooted, though. Oh well, just restore to factory and reroot and you should be fine Id bet...
Sent from my NookColor using XDA app

Crapcrapcrap. I think I broke it.
I tried to do the factory reset as you suggested but it wouldn't do ANYTHING. I did some more searching and finally got it to work by holding power button plus volume up plus home button and then holding power button. But it went to the future of reading screen and then the Nook screen and wouldn't do anything. More searching told me to reset it 8 times and on the 9th it would completely restore factory, so I tried that.
It seemed to have worked but then went into ANDROID boot/initialize sequence and was repeating that over and over and over. Seems weird that it would boot Android after a complete reset, but I digress....
I thought maybe it was because the imaged card was not in, so I inserted that into the slot. Same thing....repeat over and over Android boot up sequence.
I powered it down manually and it seemed dead again - not booting back up by traditional means. I tried holding different buttons, whatever...FINALLY got it to the future of reading screen again. Proceeded to boot up - Android sequence....you guessed it, on repeat. No card in now. Crap!
Please help! Newbie here not sure what to do!

your case is similar to what I experienced yesterday. I took out my memory card, and did factory reset and 8-time reset trick. On the 9th it installed a fresh rom (1.0.0), and booted successfully afterwards.

jerry_smith_80 said:
your case is similar to what I experienced yesterday. I took out my memory card, and did factory reset and 8-time reset trick. On the 9th it installed a fresh rom (1.0.0), and booted successfully afterwards.
Click to expand...
Click to collapse
Thanks for the response jerry. Something is definitely jacked here.
I did the 8-time reset again....Got the message it was installing a software update, the future of reading screen, etc.....and then it went into the freaking Android boot sequence on repeat again. Why is it booting up Android instead of 1.0.0?
No memory card here, either. I am totally flustered.
I would really appreciate any help that anyone out there can provide. Did I brick this thing?

Update. I powered it down from the Android reboot cycle and then followed the instructions here to perform another factor reset. Somehow this time it worked. It rebooted with 1.0.0 and made me go through the setup steps again.
I think I'm going to upgrade to 1.0.1 this time before rooting....I was having some bugs and somehow it culminated in the above debacle. Hopefully it is smooth sailing from here.

Something is still messed up here and I'm not sure what's going on.
As mentioned above, I finally got the thing to reset, clear, and boot back up with 1.0.0....or at least so I thought.
I had only ordered one book and it was present on the reboot - not sure if that is significant or not. At any rate, my initial plan was to update to 1.0.1 like I mentioned since I seemed to have issues/bugginess before w/ 1.0.0. I downloaded the .zip file to my desktop, copied it over exactly as instructed and the thing never rebooted with the update. I waited and waited. I put it to sleep and waited. I woke it up. I tried to navigate to it. Nothing.
Ok, perhaps another fluke. From what I've read the update is unimportant anyway. So I tried to root again with auto-nooter on 1.0.0. Followed steps again to a T. Even re-downloaded all of the files to my computer just to eliminate issues. Put my card in, plugged it into my laptop....never found any drivers. CN stayed off. Tried to boot it up manually - nothing. Tried to reset it manually w/ Power + home + volume up. Nothing.
Finally I removed the SD card and booted it up and it worked. During initialization I quickly put my card into the slot and it booted Android successfully....much like the first time I rooted it.
It is working...but not like it is supposed to. I'm wary to go down this path again considering the trouble I eventually encountered last time. Should I start over? What the hell did I do wrong?

[Q] [Bricked] autonooter... Will not reflash stock rom

Well here goes, I already reflashed the stock rom once from autonooter. 8 reboots then the stock rom becomes reflashed... Well in an attempt to return to stock 1.0 and install the updated autonooter I seem to have bricked my nook.
I can force reboot the nook 8 times and then the system update installed successfully... So it seems (progress bar reaches the end and nook reboots) but the splash screen is not stock! It runs the nook dev splash screen and will not boot. It will bootloop over and over. I tried another system reflash but same thing. What can I do?
Is it possible to run the autonooter sd card image ? Any other ideas?
Thanks

You need to wipe the NC. Power off. Hold power and home until it wipe screen appear. It might start wiping automaticlly or you may need to press home continue. Don't remember.

The 8 boot method is only half of the system wipe process. You still need to wipe /data. Steps to do that are at: http://nookdevs.com/Flash_back_to_clean_stock_ROM

It worked! Thanks
I could have sworn I did that several times. I had to hold both the power and nook button until the unit shut off. Then on the next boot attempt it gave me a data wipe option. Tricky little unit

[Q] Unable to install gapps on CM7 final

Just installed CM7 final on uSD card. Works fine. So I went on and followed instruction here http://forum.xda-developers.com/showthread.php?t=1000957 to install gapps. Rebooted a few times, including using the shutdown menu to boot into recovery. But nothing happens. CM7 boot the system without any interaction and there is no sign of gapps anywhere.
Anybody succeeded?
zip file I installed was gapps-gb-20110307-signed.zip

Rename to "update-gapps-gb-20110307-signed.zip"

I had the same problem too with gapps using those instructions. When CM7 final was released, I just reimaged my SD card and tossed cm7.zip and the gapps.zip file onto the root of the SD card and reinstalled CM7. It installed gapps as well and it appears to be working fine.

barf99 said:
Rename to "update-gapps-gb-20110307-signed.zip"
Click to expand...
Click to collapse
Nonsense, you use the name as-is.
OP,
Sounds like you're just not getting into recovery right, it takes some practice with the timing. And you can't 'shut down into recovery', AFAIK that does not work. You'll have to hold the right combination of buttons bootup.. You'll need to look for your particular recovery, but for me I hold Power and the N button during the boot process and let go of the Power button about 5s after seeing the "Reading" message.

Thanks. It looks like khaytsus is right: I need to let go of the power button but hold on to the N button for a bit.
Works now!

After flashing gasps and if you don't see market icon, connect to wifi. Then it should show up.

OMG thanks for the one above me! i was flashing and flashing again and again the whole day about 10 times or more! and the only thing i should do, was enabling wifi -.-

[Q] Help: Galaxy Mini/Pop won't boot.

I haven't rooted my phone whatsoever or installed a rom or something. One day, it just won't boot. I don't use it all the time, so the battery died. I charged it so I could use it and download an app. When I try to power it on, it will only reach the flashing Samsung logo with the black background and won't go any further so I result to opening the back cover the remove the battery and try turning it on again. Still won't boot. I tried draining the battery, but it still won't boot. Would booting it without the SD card solve this problem? I heard that if I did that, I would have to factory reset it using the hardware keys. I don't want to erase everything in the phone since I'm not able to back it up. Please help. Thanks!

ZAYNlienware said:
I haven't rooted my phone whatsoever or installed a rom or something. One day, it just won't boot. I don't use it all the time, so the battery died. I charged it so I could use it and download an app. When I try to power it on, it will only reach the flashing Samsung logo with the black background and won't go any further so I result to opening the back cover the remove the battery and try turning it on again. Still won't boot. I tried draining the battery, but it still won't boot. Would booting it without the SD card solve this problem? I heard that if I did that, I would have to factory reset it using the hardware keys. I don't want to erase everything in the phone since I'm not able to back it up. Please help. Thanks!
Click to expand...
Click to collapse
You can try to boot it without SD card, but i don't think that's the problem.
I think your only possible solution is to try doing a factory reset. Try to press HOME button and POWER button together until you get to the recovery. Than, depending on the recovery you have, search for a "wipe cache/data" or "data reset".
Another solution might be using Odin, but that's the last one...

frazar said:
You can try to boot it without SD card, but i don't think that's the problem.
I think your only possible solution is to try doing a factory reset. Try to press HOME button and POWER button together until you get to the recovery. Than, depending on the recovery you have, search for a "wipe cache/data" or "data reset".
Another solution might be using Odin, but that's the last one...
Click to expand...
Click to collapse
It did work. I thought of doing that but I waited for my friend so I could consult for another way, but I resorted to a hard reset. Thanks!

sorry for you, you can't get your data back
but to solve this
you can try to wipe everything through recovery mode
(while turn of, home button + power)
if you still can't access recovery mode or still the same after wiping
you must flash your mini
[TUT]Official Gingerbread 2.3.6 09.02.2012 GalaxyMini s5570~ODIN~UPDATED
for later, backup your data app by using Titanium Backup
must root