[Q] Samsung Galaxy S 19000M MAJOR problems, bad kernal, bad ROM...HELP:( - Galaxy S I9000 Q&A, Help & Troubleshooting

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

Related

[Q] Kies no longer works with JPKXX

Hi Guys,
Upgraded my SGS to xxJPK and loving it.
Kies no longer recognises my phone (I was running earlier version then tried upgrading to latest and it still doesn't help), which is not the end of the world as I don't use it much but I like to get apps off the samsung store sometimes through Kies.
I can still download the games but they come in 2 files. One is a .app file which looks like it is the main part of the program as it's the largest. The other file is a .img file which I assume is some sort of reference file for the application.
Is there anyway to install these on my phone without using Kies?

Strange Captivate issue

OK.. First of all I want you to know that I'm not a n00b and that 99% of the cases I know what I'm doing with my phone but this is a weird one
Problem no.1: The simcard keeps on "disconnecting", resulting in disconnection from the network. Since the first seconds I start the phone it does this. Sometimes it doesnt even accept my PIN as being incorrect, but in the notification bar the SIM+! icon disappears for a moment. This is after I screwed a ROM and returned to stock using the OCD JF6.
Problem no.2: It wont master clear! No matter what I do, it wont do it. I tried since the first second when ODIN detects the phone. I tried it when it fully loads the ROM, it just wont go.
Background: Before, I had installed Froyo JPA i9000 ROM with Reoriented kernel 2.1.2 (voodoo lagfix+color,bln). Everything was soooooo fast on that ROM (with around 100 apps installed) but I wanted to theme it. So I tried to deodex it using xUltimate. I followed the (logical) instructions found in a post here and it didnt want to boot anymore... well, it did but in a FCs symphony.
I did what I believed is right and I returned to stock but I forgot to pull out the SIM card... then these problems appeared.
Gimme a hint what could I do. I'm asking first here because a working PDA without a SIM is .. acceptable but a totally bricked one is worse so before I take any steps further I need your opinion.
Thanks a lot.
No one?
Sent from my SAMSUNG-SGH-I897 using XDA App
icezar1 said:
OK.. First of all I want you to know that I'm not a n00b and that 99% of the cases I know what I'm doing with my phone but this is a weird one
Problem no.1: The simcard keeps on "disconnecting", resulting in disconnection from the network. Since the first seconds I start the phone it does this. Sometimes it doesnt even accept my PIN as being incorrect, but in the notification bar the SIM+! icon disappears for a moment. This is after I screwed a ROM and returned to stock using the OCD JF6.
Problem no.2: It wont master clear! No matter what I do, it wont do it. I tried since the first second when ODIN detects the phone. I tried it when it fully loads the ROM, it just wont go.
Background: Before, I had installed Froyo JPA i9000 ROM with Reoriented kernel 2.1.2 (voodoo lagfix+color,bln). Everything was soooooo fast on that ROM (with around 100 apps installed) but I wanted to theme it. So I tried to deodex it using xUltimate. I followed the (logical) instructions found in a post here and it didnt want to boot anymore... well, it did but in a FCs symphony.
I did what I believed is right and I returned to stock but I forgot to pull out the SIM card... then these problems appeared.
Gimme a hint what could I do. I'm asking first here because a working PDA without a SIM is .. acceptable but a totally bricked one is worse so before I take any steps further I need your opinion.
Thanks a lot.
Click to expand...
Click to collapse
Problem 1: can probably be fixed by reflashing stock with the SIM card *not* in the slot (that's about my only guess, never seen that).
Problem 2: master clear must be done with the phone turned on *NOT* download mode. the phone must be fully booted with adb debugging enabled in settings.
xUlimate: it's a poorly written application and it's success ratio is probably about 50/50, another tool to look into is auto-deodexer. Also, both the framework AND the system apps need to be deodexed to have everything play nicely (gtg taught me this one)
id experiment. from what i gather you were able to flash jf6 but it was a bad flash. does it still have download mode? maybe try to flash again and then try to master clear? maybe try to flash another rom, then try to flash back to stock?
this doesn't sound like anything anyone has seen before so your best bet is to just try something.
Thanks a lot for the replies guys!
The master clear was tried from all phone statuses (booting; finished booting; after the phone operated for a while) except download and recovery (i know is not suppose to be done from there).
I did reflash to stock without the SIM, same issue.
I will try flashing again some other rom. I'll try more and ill post the result here
Sent from my SAMSUNG-SGH-I897 using XDA App
OK, so, it seems that for some reason, after stock restore there were still remaining of XEE CSC in the phone..
I loaded the JPA back and now is all fine.
I am having the same issue, unable to clear with CWM or odin, or within the OS in either the stock rom or axura 4 or 5...
Can you please elaborate on your solution?
CSC looks familar to me, thats an ODIN file right? If so, what part of the phone would that be (kernal, modem, OS)?
What do you mean by load JPA? Odin package or CWM? WHole rom or specific parts.
thanks...this has got me stumped
Well, my issue is that I cannot use 2.1 anymore (any 2.1, tried stock Captivate and JM8 from i9000), I don't understand what is wrong but my first bet is that the /efs partition got changed in some way when I loaded JPA i9000 ROM.
Froyo works fine, any ROM I load give me full functionality but on 2.1 the SIM gets disconnected all the time and after a while the phone reboots by itself. Just to make it clear, I never had the usual Captivate reboot issue, it started when this SIM problem appeared.
Note: my product codes are fine, in both nv_data.bin and nv_data.bak the product code is finishing in ATT and my IMEI is available in both 2.1 and 2.2 and is correct, so no IMEI corruption here.
Could someone give me a hint?? Would flashing to stock with phone EFS clear help?

[Q] Please help, ODIN is not recognizing my phone at all

Ok, I was at the stock Froyo 2.2 update yesterday and saw 2.3.5 GB and installed using ODIN. There's a couple of aggravating features, mainly every time I plug in via usb or AC, the tethering process crashes. I don't even use tethering and don't know how to disable this process.
Anyways, all I want to do is return to the stock AT&T froyo. I've tried several one click packages for ODIN to return to stock, I CAN get into download mode, but once its plugged into the PC it says its installing device drivers, then it always fails. I tell Windows to search, and of course it can't find any.
How can I get this to work again, all I want is my 2.2 back
Read this thread

[Q] Samsung captivate driver issues (MIUI rom)

I started having issues with the MIUI rom and wanted to get a different ROM. The devices menu shows for the captivate device that there is no driver. I have tried to let windows find a driver but it cannot find one and I tried installing one manually but still has the same error. My only idea is that the device name changed so it cannot find a driver. Can someone tell me what their machine says the device name is for your samsung captivate? Or if I am wrong can anyone help me out?
MIUI version: MIUI-109160
Kernal: [email protected]#1
Thank you
Have you tried a Heimdall one-click (like the one in my signature)? That should detect your phone as part of the installation process, and let you flash back to stock (with CWM) as well.
Edit: okay I got it to work. Thanks I am now back to the default. If i have any more issues I will come back. Thank you
Yeah even tho it got back to the stock it can't read the sim card now. suggestions?

[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^^

Categories

Resources