Database Develop

[Q] Please help me :(

I tried to upgrade to the new 2.2 froyo and all it gave me was the JM2, I had JM1 so I did it. Then the phone started to turn itself on and off again, so I did a factory reset from the recovery menu. Now nothing works and everything pops up with force close. I can't do anything but get back to the 3br. Please, I'm sure I'm getting freaked out for no reason but it's 4am here and I've been working on it for hours trying and looking for something.

did u have a lagfix installed on your phone before u started flashing to 2.1.1 ?

Very similar issue here - used regedit hack to get 2.2 - all I got was the JM2, phone was working fine, but I did factory reset hoping to clear all the old data, after this all I get is "Sorry!, The application TwLauncher (process com.sec.android.app/twlauncher) has stopped unexpectedly. Please try again"
I did have lag fix, but unnistaled it before upgrading to 2.2
How this could be solved ?

install via odin. Kies is a P.O.S

Got the same problem.
Installed Froyo using Kies and the registry hack. After rebooting I checked my Android Version: 2.1 Update 1. So I followed the instructions to do a factory reset. Now all I can do is boot the phone and type in my pin-code. Then there are lots and lots of popups telling me a process has stopped working ...
Can anyone help? Is odin really the only way to regain access to my phone?

Factory reset, clean cash, wipe internal sd-card

I already wiped the cache and also did a factory reset twice. When entering recovery mode I receive the error: "multisc: can not acces to /system/csc/DBT/system/"
How to wipe the internal sd card then?

I have the same problem! Have a brand new Vodafone handset (no lag fix etc.), ran the regedit patch and whilst I didn't get 2.2, I stayed on 2.1 update1 but unbranded. Was delighted to get rid of bloatware but after a factory reset, the same problem!
Using my registry settings, I flashed back to Vodafone firmware but the problem still remains

OK wiped and then even formatted the internal sd-card - did this from windows explorer whilst connected via usb.
I then did a wipe/factory reset, wiped the cache and then reboot.
Still the same problem!

I eventually got it to work
I flashed via Odin, the JPK firmware and that was stable enough to get some sleep. In the morning, I flashed JPM and then rooted and lag fixed. I took the lag fix and even the root off of it before trying to upgrade on Kies so I have no idea how that happened. I'm thinking that flashing with the new ROM is the only way to get it un-bricked after that but it's good anyway because now it has FroYo with root and lag fix even though I was originally trying to keep updates to official channels so to speak (guess I found out just how unsafe the official way is vs. the unofficial way).

Me too! Thanks for the advice, I ended up doing the same!
Only difference is I updated to JPM firmware as shown on this forum - works perfectly Likewise I would have preferred not to have to do the unofficial way - guess my warrranty is now void?
Out of interest, I found it hard to figure the difference between JPK and JPM but I seemed to conclude that JPM is a slightly more recent and technically the 'final' of Froyo?

Flashed via Odin and it started to work, finnaly.
Good question regarding formware versions - it is interesting for me also !

[Q] JPO available yesterday, gone today?

Yesterday I saw the news that JPO is starting to spread, along with a new Kies version. So I downloaded the new Kies and installed it. Hooked up my SGS, at that time running official JM1 patch (obtained through Kies a few months ago), and hit the update button.
Kies then showed that the JPO update was supposedly available to me.
Unfortunately, during flashing, something went wrong and I ended up with an incomplete update (the screen went solid-color pale green at one point and nothing more happened after that). Repeated atempts of Recovery after that, as well as Odin ended in similar failure. It looks like I can't run updates from this computer.
I then installed Kies on a different computer and hooked up the SGS there, in Download Mode, and tried to flash JPO (downloaded from the Dev forum here) using Odin. That worked partially - on restart, I only got Recovery mode with an error message, claiming that format of the internal memory failed.
So I downloaded official JM1 and flashed that, and it works.
Now I reconnected to Kies and tried to look for the JPO update on that other computer, but I now get this message:
PDA:JM1 / PHONE:JG6 / CSC:JG7
This device's version cannot be updated.
I'd really like to get me some Froyo now - what files will I need to do this through Odin, reliably?

Froyo probably hasn't started rollout for many carriers yet. And I'm not sure exactly which carriers have begun rollout So I can't help.

did u have lagfix installed ???

[Q] Official froyo upgrade fails, please help

Hi folks, looking for some help here please.
I have a samsung galaxy s on the three network in the UK.
I have not rooted or applied any lag fixes to it at present as i dont want to invalidate the warranty at such an early stage.
The official Froyo update became available via Kies this morning and i tried to update.
The phone connected to Kies alright, it downloaded the binary file OK and then stated it would start instal.
The progress bar did not move but my laptop made the sound when a USB device disconnects, then a second or two later made the same sound which i was taking to mean that the phone had reconnected, however Kies came up with a message that the connection had been terminated and then another message stating there had been an unexpected error and that the upgrade had failed.
It then offered to recover the phone.
Instructions were to remove the cable, remove the battery, start phone in recovery mode and then to reconnect cable. I did all of this but when i reconnect the cable, my phone is not recognised as having connected and nothing else happens.
If i restart phone it works OK on old firmware but if i try upgrading again, Kies gives a message that a previous upgrade failed and i should attempt recovering firmware. I have been at this for hours now with no joy.
I have two options in Kies, either to attempt upgrade again which always ends in error message that unexpected error occured, or to attempt recovery and in this case my phone is not shown as connected. When i start in recovery mode should i select any option or just leave it at the screen that appears.
At this point i really dont want to try any other firmwares or fixes so would really appreciate if anyone has had similar problems being able to throw me a lifeline.
Thanks for any help.

Sorry i cant help you but are you on payg or contract with 3?, im on contract with 3 but kies is not showing any firmware upgrade for me

I have had a three contract since they began, however i bought the samsung galaxy s about a month ago to replace my Nokia N86 as i fancied a change and didnt want to wait almost a year. So basically it is my contracted sim into a bought PAYG phone.
I have been following the posts at blog.three (sorry not able to post full URL) and they reported on Friday that the update would be here soon. Logged in to Kies this morning and it stated an update was due. My head is bursting with this as i have read so many posts and tried so many instals, and reinstals of Kies, i have tried upgrading with Sim card and SD card removed, still no joy. i am beginning to wonder if there is another flaw with the three version of froyo. Good luck anyway.
p.s, asking if i was on PAYG or contract made me think, so i tried putting the PAYG sim card in that i got with the phone, connected to Kies and upgrade still available however same error when trying to upgrade. The rollout may be by region or by banks of phone numbers, so you should get it shortly, although heres hoping it works for you

Thanks for the reply Doc, could you pm me that url pls?
Good luck to you with solving your problem.

Doc, just to let you know you aren't alone - I too have the same problem - tried it on both computers - says the update is available, it starts the download, the knocks the phone into download mode before coming up with an error message. I have tried to put it into recovery mode and it still fails - however I can just restart the phone and the old firmware is still in place.
No lagfix/root etc. Just a bog standard three phone.
Anyone who could help please!!!!!!!!

[Q] Samsung Galaxy S 19000M MAJOR problems, bad kernal, bad ROM...HELP:(

Hey guys I been having a huge problem with my Samsung Galaxy S 1900M its currently locked with Bell/Virgin Canada. I bought it off of some 2nd hand company. The phone was sold as is saying that it was unable to connect to the computer, (computer does not recognize it at ALL). I bought the phone amusing it was a ROM load problem. It came to me rooted and in almost perfect condition so I was quite happy with my purchase considering I paid $180 USD ($170 CAD). I tried connecting to the computer using the USB that came with the phone, and as stated it does not recognize it at all on ANY Windows/Linux base PCs. I also have another Samsung USB cable that I know works, I tired that as well...no success.
So I am assuming who ever loaded a ROM did not know what they were doing.So I have been searching all over the internet/google, XDA forums and Q&A and everyone point to loading a new kernal....BUT here is where it gets weird. Who ever had this phone previous did not flash a new kernal when updating and put the 3e recovery on the phone, WHICH MEANS I cannot flash any new: Kernals, OR ROMS using the CWM, which btw I am pretty sure isn't working properly because it goes into the base recovery mode with limited options, ex. reboot, sdcard update.zip, wipe cashe, format sdcard...nothing else.
Which brings us back to the original problem, I can not connect to the PC for ODIN to work its magic on the kernal....Please help....
Here is the current load,
Firmware Version: 2.2
Baseband: 19000UGJK4
Kernal Version: 2.6.32.9 shout.leeSEP-09 #1 ( I have never heard of this?)
Build: FROYO.UGJK4

may be a issue with drivers dont quote me though, i had to update drivers after flashing and updateing my galaxy s, as i had simular issue with odin, by not reconize, do you mean windows wont even detect the phone added, or is it connect and nothing? does the phone charge when connected to the pc ?

The phone does charge, but even with the Samsun Keis app, and having the proper Sumsung drivers it still wont even detect the phone. I even went to Device Manager and searched for new hardware/device. I also tried putting it into download mode, and connecting Odin. Windows still wont even detect it. I think its a problem with the kernal....for both issues...

Fixed the problem, hope this helps for others.
Just following up on this as I figured out what to do on my own in case anyone else has this issue.
It was quite simple actually, the kernal was faulty, and so was the ROM that was loaded just as I anticipated
1st:The person that previously owned the phone loaded FROYO custom build that was taken from a leaked version prior to the official release and had no USB support, therefore being unable to connect to the computer.
2nd: The kernal was a custom build and had a 3e recovery built into it and was not able to load any un-verified files(unofficial ROMS, firmwares, updates etc.), therefore I was not able to load a new ROM to fix the first problem, stated above, and visa versa.
I found a program on the market place called "kernal manager", I downloaded the PRO version by searching Google on the computer for the .apk file, I then copied the .apk file onto my external 2 GB SD card and ran the .apk file through the phone. I then opened "kernal manger pro" and opened the menu button, then hit search for kernals. A list of different models of phones came up, I browsed down to my handset maodel (Samsung Galaxy s 19000), press on it, and got a list of kernals. I took each top rated and downloaded kernal listed, did a little research on the internet and found one of them to be suitable. I then went back to the phone chose that kernal through "kernal manager", it asked me to flash then reboot, I hit yes, it then begun the process, and when finished reboot on its own. I then reboot into recovery again after the kernal had loaded and the first reboot and found that the new kernal had succsefully been flashed. I then was able to go about as I please. I uploaded a cm7.zip file to the external sd card, put it in the phone, boot to recovery browsed to the file, and ran it having complete success.
I am now happily running Cyanogen 7. Hope this helps anyone that needs it. Any questions just ask

[GER/ENG] "Revive" I9000 with dead EMMC beyond Android 2.3.7?

Hey guys,
dunno if I have to write english or german here, feel welcomed to answer in your prefered languages. The more opinions, the better!
I used rooted XXJVT (DBT) for a very long time but by time it went laggy AF.
Now I decided not only to reset the phone to make it work lagfree again but also flash Android KitKat via CWM.
The biggest problem I encountered: my eMMC died a few years ago, so I was forced to run the phone via microSD (had to scratch the chip off the mainboard to make it accept the microSD when flashing) and exchange the vold.fstab to make the phone use the microSD as internal storage. That way, it worked again. Until now.
Since the WhatsApp Services don't let any 2.3.7 and older OS verify their Account anymore (but those who were already verified can keep WhatsApp until Feb 2020) + I can't flash Custom Roms via CWM ("Waiting for SD-Card to mount" counting down from 20 to 0, then restart and same screen again, looped) probably because of the dead (no more existent) eMMC Chip, i guess the only way to make my phone work WITH WhatsApp again would be find a rom above 2.3.7 that I can flash via Odin..
Otherwise I guess I can shred my phone because it is restricted to SMS/Calls from now Q_Q
Now I need your help: Is there any possibility that I don't know yet? Any ROM out there that I could flash via Odin, dodging the "flash via CWM" way that doesn't seem to work for me (atleast, since my eMMC is dead, I don't know how could make it go past this "Waiting for SD-Card to mount" ****?
Greetings,
A desperate Android User^^