Database Develop

[Q] Would you tell me my I9000 dead not just dying....

Thanks in advance for any response!
The followings are my phone's symthoms:
1. My phone WAS FANTASTIC until I updated new Darky extreme version 9.2 (upgrade from 9.0)
2. I degraded it to the stock rom with Ryan's OLFG -> Working very well...
3. Until the phone was restarted. The phone was still working however
4. IT BECAME FREEZING. I couldnt scroll, couldnt touch the screen, or the phone response was like 5 mins later for each touch.
5. I followed instructions on the internet to flash with stock rom (JM8) and upgraded it to JPO, and the result is
6. THE PHONE COULDNT BE BOOTED at the Galaxy logo.
7. I tried to flash the phone over and over with different stock roms using ODIN 1.3 (with well understanding about repartition and PIT)
8. NOW, my phone is still able to access the download mode, but my PC CANNT SEE THE PHONE DRIVER ANYMORE(tested on 3 other laptops with the same result)
9. Reinstall USB drivers like 20 times, the results have been the same.
TO me this should be a phone death. Im gonna purchase the new Galaxy S 2
HOWEVER, If there is anyway to revive my phone back to normal (Cuz I wanna get some important data in the internal card), I will not only send a big gratitude but some DONATE as well.
Thanks.

so you put the phone in download mode first... then you attach the USB ???
Does anything happen when your in Odin ?? does it not say connected or anything ??
and have you tried doing a factory reset in recovery mode ??
aslong as your phone can go into download mode there is still hope so dont give up on it just yet

U obv have samsung kies right?. Go on processes on ur pc ctrl alt del n kill the kiestrayagent process
Sent from my GT-I9000 using XDA App

Surely I killed KS before doing ODIN. The PC(s) said it was Unknown device.
My phone was on when android 2.1 installed (but freezing, not just lagging .... completely freezing on the home screen) and would not boot if i installed 2.2
Sigh....
Thanks for your replies

The PC(s) said it was Unknown device.
Thats generally a USB /driver/windows problem .
You installed deadlys rom and it should still be recoverable even from that .
Is your phone picked up via Kies phone/Odin will need Kies installed .
I would have flashed back to a clean copy of Eclair first off to get the phone working .
jje

Both Kies and Odin could not see my phone... I killed Kies process before doing Odin, but the result was still a sadness.

Frustration at it's peak.

Hi there guys, That's it .
After reaching my highest limit of searching / installing / removing , z4root , super onclick, which btw none work, I am on the edge, basically , loosing my mind, and all I would like to do is just root my phone and have it working properlly and faster.
Now there are so many old root methods as the one I tryed Does any of you guys can help me out and explain how do I root my Samsung Galaxy S I-9000, with froyo 2.2 firmware ?
Thank you Omri.

what exact firmware,
i used JL2 and super one click worked for me.
try all of them.

Gets stuck on " Waiting for Device "
and i already unplugged the phone a couple of times with usb debugging on/off , any chance that im doing somthing wrong?

flash speedmod kernel.. or cfroot kernel

Can you see phone from the PC?
It sounds like the Odin method of flashing a custom kernel is not an option (if not try that - lots of info in the kernel posts)?
If your computer is not recognizing the phone try remove and reinstall drivers and kies and then also clean out the port on the phone with alcohol (and try another usb cable if you have one).
That my two bits. I tried in vain to root from the phone alone with 2.2 but finally got odin working by cleaning the port and now the possibilities are endless.

What exactly is this "Flashing / Kernel" options exactly , because the computer recognizes the USB just fine. ??

See here
http://forum.xda-developers.com/showthread.php?t=822756
This is for speedmod (if you need other options go to the stickies in the development section and look for the kernel list near the bottom of the stickies).
Follow the procedure for Odin installation. You will need to ensure you can go into download mode (Vol Down, home and power buttons to see - it should show android with a shovel in yellow - you can pull the battery to stop it if just checking but don't touch anything while Odin is working). If you cannot get 3 button download working, look for that fix in the forums too. I did not have that issue so I can't point you in the right direction there.
I think hardcore's page (author of the rom) has a link to an Odin guide. But its worth getting to know a bit as it will save your bacon if you need to get back to stock for warrenty.
Once you have this rom you'll be rooted and have clockwork Mod which allows flashing from the phone if you like (most custom roms are based on CWM installation). This is what I did once I got mine back from warrenty with 2.2 and then I flashed Darky's rom keeping the stock modem.

juvenileomri said:
Gets stuck on " Waiting for Device "
and i already unplugged the phone a couple of times with usb debugging on/off , any chance that im doing somthing wrong?
Click to expand...
Click to collapse
If you are stuck at "waiting for device"
do not exit Super One Click
1. pull out the usb from the phone,
2. turn off by pulling out the battery
3. put the battery back, turn on & plug in the USB

softbrick - halfdead download mode

Hey guys.
So I have a problem,
I was on darky's rom 10 and I have installed cyanogenmod7.
After that phone was woooow fast and great and everything...untill I decided to listen some tunes from external sd.
And so I have found out that I can't see external sd because I installed cyanogenmod on non froyo ROM.
Then I've tried to flash stock froyo but odin hanged a long time and I just restarted whole operation.
Now I have an icon ! that phone wants to connect to computer.
I can enter download mode with vol. down + home + power but it that state Odin cant see shiet. Only thing that can see phone in that state is windows (trying to install drivers and then fails!?) and kies (hanging on "connecting").
So, what are my options? Bricked for life? Or..... :S

k that symbol means connectivity issues, so try changing the usb port and if that fails try using another usb cable...run odin as administrator before trying all this!!

ok I've managed to get Odint to recognise it..
I've tried to flash froyo from this topic: http://forum.xda-developers.com/showthread.php?t=853950
and it doest boot, hangs at samsung/galaxy logo 4ever...

flashing darky's 9 resurection also gives no good thing.
just hangs on start samsung/galaxy logo/black screen in loop....

had the same problem as well and it was solved by plugging the usb cable at the back of the pc.
if that doesnt work try flashing other roms... you can find some tutorial on totallydubbed's youtube channel with the link of the rom in the description.
http://www.youtube.com/user/totallydubbedHD

Hey ppl,
I've had an awful fight with this phone and my brain and stupid PC.
omg
So, I have tried to flash 2.2 and it worked, then tried to flash cyanogenmod and it worked (again) but I couldn't reach external sd (again).
So I said to myself...f*** this s*** I'm going on stock,
And I did,
firmware version
2.3.4
baseband version
I9000XXJVR
kernel version
2.6.35.7-I9000XXJVR-CL425308
[email protected] #2
build number
gingerbread.xxjvr
This is what I have, and the problem I'm facing (again) is that phone or pc via USB can't recognise external SD.
Help please.
p.s. how can I easily go to cyanogenmod from here?

Kies is saying that "This version of the device cannot be updated."
Windows can't see either internal or external SD.

update;
I've installed Darky's 10.2 ressurection, something is very wrong with my phone.
Install went fine, rebooted ok.
Still no SD card, when I reinsert it, it says its blank or non supported format.
Tryed to reboot the phone and it just loops on darky's logo/animation.
Help?

[i9000b] BSOD - Phone ! Computer Screen

I had Android 4.0.3 (IceCream Sandwich) on my Galaxy S GT-I9000B (I did install it through Odin, nothing went wrong), but is was laggish (too much for it to handle, I think) and after a few months, I decided to roll it back to 2.3.3 (Gingerbread).
I started the process to install the firmware through Odin3 v1.85 - the file I download (from sammobile.com/firmware, had only one file that I used on the PDA space.
Odin recognized my phone and I started to install it, but after a while my phone was stuck on the downloading screen (2 hours of installation, I tought that something went wrong).
I then turned my phone off to try and install again, but when I turned it on, there were a Phone - exclamation mark - Computer Symbol.
I can get it to dowlonad mode (Volume Down+Home+Power), but when I plug it to the pc, it says "unknown device" and it can't find drivers for it.
I think I have the latest drivers from Samsung (I had from Kies and I re-downloaded a file somewhere from this forum named SAMSUNG_USB_Driver_for_Mobile_Phones_1_5_6_0.exe).
It appears that since windows can't install the drivers, Odin doesn't recognize the device - it was recognizing it before, when I was installing the firmware.
Now I'm stuck - I tried anything I saw in this forum and in other places - I did even pray for a miracle, but it didn't work
I know that there must be a way, but I don't know how.
Before I forget, I'm using Windows 7 Ultimate x64.

If you can get it in download mode everything should be fine, I've had a problem like this, my pc couldn't see the phone in download no matter what. Try to use another USB port, better another PC. Also I've heard that x64 doesn't get along well with Odin. If possible you can try Linux and Heimdall, after all Android is Linux too.

KainFromNod said:
I know that there must be a way, but I don't know how. Before I forget, I'm using Windows 7 Ultimate x64.
Click to expand...
Click to collapse
Ok, k4Z3666, has given you a starting point...the phone is still in download mode but without a booting ROM, so its OK, the problem is your PC, USB cable or USB port. If you want to be quick about it, just try on a lap top..if not a simple Reboot of PC ( after removing power cord) and Phone (after a battery Pull), and a switch to a different USB port at the back of PC can solve this for some...for other solutions try these http://forum.xda-developers.com/showpost.php?p=27205737&postcount=4571 anything else you may need can be found on My Android collections., link below

k4Z3666 said:
If you can get it in download mode everything should be fine, I've had a problem like this, my pc couldn't see the phone in download no matter what. Try to use another USB port, better another PC. Also I've heard that x64 doesn't get along well with Odin. If possible you can try Linux and Heimdall, after all Android is Linux too.
Click to expand...
Click to collapse
I tried other USB Ports and also rebooting. It was working just fine - it seems like a driver problem to me.
My notebook is dead, but I'll try using someone else computer.
Does Odin runs in Windows XP? I might try it in my virtual box - I doubt that it will work, but it is the best thing I have to do untill tomorrow.

I got it working in my mother's notebook - should I try something different? I only have the PDA, should I try a PIT?
I don't know what those do, but I read somewhere that PIT is used to recover bricked phones.
EDIT: I installed only the PDA, it worked fine on the 2nd time (first time, it got stuck but I could make it work changing the usb port and cable).
Now it is on loop - it repeats the samsung logo over and over again. Any ideas now?

KainFromNod said:
Now it is on loop - it repeats the samsung logo over and over again. Any ideas now?
Click to expand...
Click to collapse
what ROM did you use? Did you do any wipes?
Opps..you got an i900B, so make sure you are only using I9000B ROMS as i9000 is not compatible with your phone
Follow guidelines from here
http://forum.xda-developers.com/showthread.php?t=919219
http://forum.xda-developers.com/showpost.php?p=22941192&postcount=300

KainFromNod said:
Now it is on loop - it repeats the samsung logo over and over again. Any ideas now?
Click to expand...
Click to collapse
Assuming that you're on the right rom for your phone can you enter recovery mode? Try reinserting battery, and enter recovery with [vol+, menu button, power on]

KainFromNod said:
I got it working in my mother's notebook - should I try something different? I only have the PDA, should I try a PIT?
I don't know what those do, but I read somewhere that PIT is used to recover bricked phones.
EDIT: I installed only the PDA, it worked fine on the 2nd time (first time, it got stuck but I could make it work changing the usb port and cable).
Now it is on loop - it repeats the samsung logo over and over again. Any ideas now?
Click to expand...
Click to collapse
Yep if u want to back to stock u need pit file because ICS use different system file
Why u don't like ICS ? Its way better and faster than sammy ROM even its more stable , I think u should try it again with devil kernel with oc to 1.2 it will fly u can add some live oc which will give more fluidity
Sent from another galaxy powered by CM10 & Syiah

Ok, I'm posting it here just to leave a reply and reference for future generations, as my problem was solved.
xsenman said:
what ROM did you use? Did you do any wipes?
Opps..you got an i900B, so make sure you are only using I9000B ROMS as i9000 is not compatible with your phone
I used a firmware from my country (available here: sammobile.com/firmware/?page=3&model=GT-I9000B&pcode=ZTO&os=1&type=1#firmware) and I wiped the cache (I'm not sure what this means, but I believe it is the 2 options on volume up+menu+power)
Follow guidelines from here
http://forum.xda-developers.com/showthread.php?t=919219
http://forum.xda-developers.com/showpost.php?p=22941192&postcount=300
Click to expand...
Click to collapse
k4Z3666 said:
Assuming that you're on the right rom for your phone can you enter recovery mode? Try reinserting battery, and enter recovery with [vol+, menu button, power on]
Click to expand...
Click to collapse
I was entering recovery mode, but it was giving me some error when I tried to wipe the 2 things that I forgot the name =/
yahyoh said:
Yep if u want to back to stock u need pit file because ICS use different system file
Why u don't like ICS ? Its way better and faster than sammy ROM even its more stable , I think u should try it again with devil kernel with oc to 1.2 it will fly u can add some live oc which will give more fluidity
Sent from another galaxy powered by CM10 & Syiah
Click to expand...
Click to collapse
ICS wasn't faster here - it was laggish and always crashed some common apps (gallery, music player). I believe that the firmware wasn't completely "done" as it was being adapted from another version (my phone is brazilian) and some functionalities that it has (i.e. digital TV) wasn't available.
What I done to correct the boot was simple (I found a tutorial in a brazilian site, so it had all the roms that I needed).
1) Used a PIT and a stock rom to get it back to factory version;
2) Upgraded to Froyo (original) - That was kind of a mistake, the tutorial said to do it because then KIES would update it automatically to Gingerbread. The phone was fully functional, but KIES said that it couldn't update it (it recognized the phone and everything).
The tutorial stoped there, but since I had the ROM, I used Odin to install Gingerbread (the one that was looping) and it was done.
Now I need to remember how to root it because there are some dumb apps who can't get away (i.e. Orkut app, some demo games).
Thank you all for the help!

KainFromNod said:
I was entering recovery mode, but it was giving me some error when I tried to wipe the 2 things that I forgot the name =/
Click to expand...
Click to collapse
From recovery you can always try to flash another kernel, that would probably resolve things too. Anyways the problem's solved, glad to help

[Q] N7000 bricked - No USB connection possible

ok first things first, imma noob, and i did a stupid thing.
It started in last summer when i wasnt able anymore to connect the N7000 to my WIN 7 64bit (probably after an update to ICS /JB).
Well since i never needed to transfer files (64GB-sdxc) i didnt care much about it. but then in last times my phone/ram cache was full of so much unblockable bootloaded crapware so that i wanted to switch from a official 4.1.2 firmware to cyanogen. But since my USB wasnt working it wasnt that easy.
Side note: the USB-port was ****ed up before (short-circuit, screen woke up due to fake-loading). i fixed that by luck and some dark magic.. so of course i thought the connection problem were because oif the broken jack.
The day before yesterday i tried for 8 hours anything i could find to install another bootloader and flash CM (CWM / TWRP / Triangle away / minimal adb/fastboot etc.); didnt work, CWM seemed to boot up but loading failed all the time at 1/3rd of the bar at screen went black.
Yesterday my friend came over and i tried to use his USB-jack to connect my phone to my Pc, which failed. THEN i put the "broken" one from mine in his N7000; that was efficacious, everything worked fine, so the USB-jack wasnt the problem.
Later i had, out of frustration, moronism, and anger, the glorious idea to download and flash another (older) Kernel via mobile odin to install an old gingerbread stock rom on it afterwards.
That was stupid as i know now, all i can do now is enter download mode, but without USB-connectivity and the stock bootloader with the options reboot system / update from sd / wipe data / wipe cache / test redbend fota(FS) and boot, which stucks at the N7000-screen.
After i managed to **** things up i found an article which describes my (now former) USB-problem perfectly. it says to put in a special number combination on the phone to get to phoneUtil and then switch from modem mode to pda mode. i knew this screen before but i couldnt find it at the preferences on JB.
Now comes my question: What could be done to unbrick my phone? is there any help?

Can you not try another USB cable? Try cleaning out the pins and see if it works. Then flash speedmod.
Sent from my GT-N7000 using Tapatalk

backstreetboy said:
Can you not try another USB cable? Try cleaning out the pins and see if it works. Then flash speedmod.
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
>Just to clarify: with USB-Jack i mean the USB-Port with the connector to the motherboard; sorry if i misused the word
I dont think so cause we used only his cable when he was here and my phone neither connected with mine nor with his USB-Jack, but both Jacks worked on his phone.
Pro-question: Is there a difference between (usual) USB-connection in booted mode and connection in download mode? i mean is download mode something like a "safe mode" where the USB doesnt need to run on 100% availabilty? Should i try to find the phone via Odin in downdload mode again by using his cable? i dont think this could work else.

Samsung galaxy note gt-n7000 bricked. Need HELP!!
The phone shows " Firmware upgrade issue encountered an issue. Please select recovery mode in Kies & try again". I cant go to recovery mode ie. vol up+home+power. THings I have tried:
1. with Kies the device isnt recognised. I have updated the driver as well.
2. with odin every thing fails... flashing "all samsung recovery.tar", flashing stock jelly bean, flashing .pit file
I have googled for days and tried many things but isnt working. Need help