Installed the BootloaderFix from Chainfire on my Tab und rebootet in order to bring Overcome to the Tab.
But now i have artifacts while booting and the usb port seems broken.
it does charge but when i plug it into the PC mass storage, kies and syn doesn't work und neither Heimdall or Odin are recocgnizing my tab.
The Tab is the Euro one with stock Gingerbread and rooted with cwm.
Some idea's ?
If you read the manual and my repeated warnings. DO NOT APPLY THIS PATCH IF YOU ARE ALREADY ON GINGERBREAD. Touching the bootloaders is the theoretically the only way to brick a Samsung device. THAT FIX WAS FOR FROYO only.
Now that its out of my system. Restock with Stock safe v5 (READ THE ENTIRE GUIDE FOR OVERCOME BEFORE YOU DO ANYTHING FROM NOW ON) then proceed to flash overcome.
thx. heimdall on my linux machine was bugged so i couldnt flash.
started the old xp maschine and xp did the trick
Related
I've read and searched as much as I can but haven't seen anyone else have this problem.
I flashed Froyo XWJP6 using Kies and changing the registry entries and I am generally happy with the rom but I've seen others posted I wanted to try out. My problem is that I have so far been unsuccessful getting odin to connect when I go into the rom download screen (down+home+power). Odin and kies both connect when on the home screen.
I understand that since its Froyo with e3 recovery that update.zip files need to be signed so odin is needed to either install a new rom, install clockworkmod or install a kernel that has e2 recovery.
Is there any way I can get odin to connect or downgrade to e2 recovery without going through odin? Or any other solution to downgrade to 2.1 and start again?
It feels like i'm missing something but I don't have the experience to figure out what it is.
Any help would be much appreciated.
Pete
This happens to me every now and then as well.What I would do is to re-install the samsung usb driver in my laptop. After that, odin sees my phone again in DL mode.
Sent from my GT-I9000 using XDA App
Make sure you're connecting in the right sequence for odin.
- start odin with phone unplugged
- boot phone into d/l mode
- connect phone to pc via usb
thanks very much for replying. I tried a different computer and it seems to be a dodgy usb port/driver problem on my works computer I had tried originally.
Hey guys, sorry for being a giant noob...
I am currently using an I9000t (telstra australia model) on Darky's 9.5
My computer is unable to detect (not even a notification/ping noise) when I plug a USB between it and the galaxy S.
I have tried the following:
Application -> USB Debug mode
Wireless connections etc -> USB Settings -> Mass storage/ask on connection
Changing USB Ports
Changing USB Cables (this is the one I used to flash from 2.1 to Darky's 9.5, so it should be ok)
Taking out Ext SD Card
Install samsung's driver on the PC
But sadly the issue still presists (note that the phone does not have the notification or symbol that the USB is plugged, however, it is charging)
There is a giant noob mistake did when flashing tho! I flashed 2.1 to Darky's 9.2 (without downloading the configurations app on the market), then installed the config app, flashed to 9.5 but forgot to turn off the speed and lag mods! I then went to recovery mode, turned off both mods, and reflashed 9.5 - then went to recovery and turned them on again. Could this have messed up the USB? If so, is there a way for me to have a clean slate and reflash again? (note that, I only have the resurrection 9.2 and 9.5 Extreme zip files... I was an idiot for not having a backup zip file...)
I have posted this message on the Darky forum but was referred to here, this also includes some of the steps recommended to me there.
darkyrom.com/community/index.php?threads/usb-connection-not-detected-by-computer.2353
Thanks in advanced
what kernel do you have mate?
try flash this on CWM
http://db.tt/xUlV2qo
Sent from my GT-I9000
i have Dark Core 1.4, would flashing this in conjunction with what I have cause issues?
Personal recommend would be to eliminate a bad rom and flash stock rom via Odin with pit 512 and repartition checked .
jje
try that file... its contain mount fix for sd ~ro to ~rw...it works for me...
if that cant solve you issue.. then flash back your rom via odin
recommended switch your kernel ro speedmod k13E then apply that file...
dont forget to disable lagfix first for safety works
hmm or you can try that file first for Dark Core..
Sent from my GT-I9000
Sad part is... I tried Odin with my cellphone in download mode - the computer does not detect it at all...
doesthisusernamework? said:
Sad part is... I tried Odin with my cellphone in download mode - the computer does not detect it at all...
Click to expand...
Click to collapse
ok maybe this the way out for debugging conect
1. Use that the file i uploaded before and try the fix for mounting..
just flash like usually on CWM its safe..
Recomended for you :
* Change your kernel to Speedmod K13E and apply that fix everything on Cwm recovery like usually to
That cause is your kernel not match for mounting sd card and phone mounting so it willnot discoverable by your computer
aware a lagfix of you change kernel
.. disable it first
Sent from my GT-I9000
check to see if your phone shows up in device manager when it's plugged in.
Sadly nothing shows up in device manager.. (sorry for the late reply)!
I will try the fix above later if that's ok... I do not know how to flash to speedmod so I'm scared it'll brick my phone... (without Odin, I cannot unbrick it)
After flashing to Overcome 2 beta 2 from JQ1 with application of bootloader batch, now during the booting (when there is a samsung galaxy tab sign) the screen becomes to show only lines, straight in many colours. What is more I do not have a USB connection with PC, neither in mass storage mode nor in Kies (I tried on 2 PC).
Additionally when I go to RECOVERY I am not able to see nothing else but the straight lines.
What might be the cause? I would love to flash it once again but I am not able to that. Of course I can use CMW from Android but I wanted to use Odin and to go back to JJ4 rom and then JQ1 and Overcome at the end.
Thanks for your advice.
Bart
Same issue. Guess I got too anxious for Gingerbread. Should have waited.
I think it's an issue with the bootloaders, reflash the stock one WITH bootloaders (posted by Chainfire) using Odin and DON'T apply the bootloader patch. That should sort you
TheGrammarFreak said:
I think it's an issue with the bootloaders, reflash the stock one WITH bootloaders (posted by Chainfire) using Odin and DON'T apply the bootloader patch. That should sort you
Click to expand...
Click to collapse
I would love to that but I have no USB connectivity.Whenever I try to connect to PC, I got new hardware found = 7 CDCs.
I change the USB in settings to PDA and did not help. No idea what to do now...`
bartekszymanski said:
I would love to that but I have no USB connectivity.Whenever I try to connect to PC, I got new hardware found = 7 CDCs.
I change the USB in settings to PDA and did not help. No idea what to do now...`
Click to expand...
Click to collapse
Can you not get to Download mode to flash using Odin?
ok manage to get connection as a mass storage but not in kies. now trying the connection with odin. yes i have it.
the problem was launcher pro which blocked the connection and not allowing the drivers to be installed.
now will try to install JQ1 once again but with which PIT?
edit
ok. all fine, reflash stock, cf root and now overcome, all the hustle due to the bootloader patch.
bartekszymanski said:
ok manage to get connection as a mass storage but not in kies. now trying the connection with odin. yes i have it.
the problem was launcher pro which blocked the connection and not allowing the drivers to be installed.
now will try to install JQ1 once again but with which PIT?
edit
ok. all fine, reflash stock, cf root and now overcome, all the hustle due to the bootloader patch.
Click to expand...
Click to collapse
Cool, glad you got it fixed
Hi everyone!
I have been reading all the posts I can to see if there was anything similar to what has happened to me. So this is the issue. The phone model is Samsung Galaxy S I9000GT
Last night I flashed my phone to install CyanogenMod and did the following steps:
Got it into Download mode with the three buttons
installed the Samsung USB composite device driver
Ran zadig.exe of the Heimdall Suite
Launched Heimdall frontend
unzipped Hardcore SpeedMOD kernel
ran the zImage of the Hardcore SpeedMOD kernel on Heimdall frontend (it was supposed to show a blue bar transfer but it was the normal green one on win7) it went to 100% and rebooted. It was showing the normal boot loop screen and then I tried to get it onto recovery mode and it went nuts.
After this, the phone went soft-bricked with the pc (problem icon) cellphone icons, I am able to get it onto Download Mode but unable to put it on Recovery Mode, I would like to put it on CM7 if possible, the only thing the phone does now is to get on the soft-bricked screen and on Download Mode, I have tried pluging it onto different machines running ODIN, a win7 and win XP, both 32 bit and none of them is able to recognize it, it is recognized as Gadget Device on the win XP machine, on the win7 with kies it just loops on the connecting icon, on Heimdall it doesn't recognize it at all... any ideas of what to do?
Make sure Kies is off and dead (check task manager processes for all kies related). Then try Odin.
Try cleaning the USB ports (phone/computer cable) as sometimes when the device is almost recognized that helps.
Did you try to get into recovery before it had fully flashed (ie rebooted and then gotten all the way to the homescreen)? If you tried to go into recovery during the first boot sequence then I could see having issue.
That being said, if you can get into download mode you likely only have an issue with 1) Driver (I would remove and reinstall) 2)Ports/cables (Clean and then Clean again - really I helped someone this morning that cleaned once but still had issues and then cleaned again and got it done) 3)Kies is active when it shouldn't be (like most of the time IMHO).
Also try to remove the battery, go into recovery and then immediately connect to odin. Once in odin, I'd flash a complete rom with pit file (and make sure it has all the files or you'll get a mounting error). But the key is getting Odin or Heimdall to see the phone.
G
thank you very much! it is now recognizable on Odin!!!!
So I have the 512.pit file but I don't have the PDA, Modem, Bootloader, CSC files, do you know where can I get them? I have already downloaded the CM7 zip file
ospina said:
thank you very much! it is now recognizable on Odin!!!!
So I have the 512.pit file but I don't have the PDA, Modem, Bootloader, CSC files, do you know where can I get them? I have already downloaded the CM7 zip file
Click to expand...
Click to collapse
Samfirmware.com will have a stockfirmware that should have them (but make sure all the files that create the partitions are there if you re-pit - my stock firmware does not have db_data on samfirmware but its needed for flashing with a pit file) though they are usually all packed in one file for the PDA spot.
But stock is likely not what you want. Just flash darky anything and which will get you CWM recovery which is what you want for CM7 (which I had problem trying - write down you Imei and back up you efs folder...).
G
Hello!
So I have already installed about 3 firmwares succesfully to my phone, the problem is that none of them recognizes the SIM Card, therefore rendering it useless again, I have installed 2 9000T (latinamerica version) and the 9000B and 9000M just to check, currently on Eclair on the 9000T with no option for upgrading it through kies. I just want to go back to the old firmware but I can't get to the one that is the one for my region apparently correct. Does having the SIM card in while flashing it and such has any effect on it being unable to recognize it?
No sim shouldn't matter. Have you tried changing the csc so it's your region?
Sent from my GT-I9000M using XDA Premium App
As you may see, I am total noob on this, how can I get the CSC file for my region or how can I change it?
Thank you very much
I have an issue, I was updating my Captivate to 2.2 with Odin3 One Click and that worked fine, then for some reason I cannot explain I tried to use Odin to upgrade to 2.3 (the blow fish one) flashed the image then got the restart with the blowfish and then used Odin to complete the process as per the instructions and got soft brick, I fixed this with the one click unbrick, then it went into a boot loop.
The loop is AT&T screen then fuzzy colours and a restart (like a graphics card has gone haywire).
I can get into the download mode by removing the battery, plugging the USB cable in holding the volume buttons then installing the battery the download mode appears but Odin is not picking up the phone.
When it is in the loop I can get Odin to identify the phone but when I try to go into download mode it won’t identify it. I have tried with adb and it does the same thing.
Any suggestions? I have looked at the forums for a long while so my apologies if this has already been covered.
Have you installed the necessary drivers on your computer?
Sent from my glitched ICS Captivate using XDA App
You may want to also take a look at the "Captivate Connection Issues" thread - it has some steps to help get you connected in download mode.
Once you have it connected, you can probably safely flash a Gingerbread stock rom to get back to a clean place to start flashing from.
Hi,
Yes forgot to mention that I have installed the correct USB drivers, Odin picks up the phone during the loop so that tells me that the Cable is fine and the drivers are working. I will try to re-install them just to be safe.
Thanks I will look through the connection issues threads and see if that helps, I am at work at the moment so will be later in the day.
The garbled bootscreen happens when you try to run gingerbread with froyo bootloaders. You must have chosen a bootloader free package. Instead, for your first time flashing to GB (and first time only), use a package with bootloaders
Sent from my CM9 ICS i897 Captivate
Haplo Nash said:
... upgrade to 2.3 (the blow fish one) ...
Click to expand...
Click to collapse
What is this blow fish one that you speak of? Korockinout13 is correct that you are getting the garbled screen because of an incorrect bootloader. You may be having issues because the ROM you flashed might be an i9000 based ROM and you will need different drivers.
DISCLAIMER: It's still earlier early and I haven't had all my coffee yet. Please correct my logic if it is wrong.
Red_81 said:
What is this blow fish one that you speak of? Korockinout13 is correct that you are getting the garbled screen because of an incorrect bootloader. You may be having issues because the ROM you flashed might be an i9000 based ROM and you will need different drivers.
DISCLAIMER: It's still earlier early and I haven't had all my coffee yet. Please correct my logic if it is wrong.
Click to expand...
Click to collapse
I believe the blowfish one he's referring to is the Fugu Root method.
About One-Click UnBrick
This Software:
Will work on all Samsung devices which use Odin3
Is a single, portable executable
Is the first one-click anything for our devices on Linux
Works on Mac
Works on Windows
Is open source
Is programmed in Java
Deploys and installs Heimdall for your OS
Is super easy to use.... Only one button!
Click to expand...
Click to collapse
The bolded line is why ODIN no longer detects your phone. The Heimdall driver has been installed. You can either go grab a Heimdall one click from here or remove the Heimdall driver (trying another USB port may work) and then try using ODIN again.
Yes it was the Fugu Root's one and I didnt update to a Gingerbread bootloader before I flased it onto my phone.
Thank you for all your help, I will never mess around with my phone at 2am again.
I managed to get Odin to pick up the phone and was able to re-load FROYO and will start again.
Do Apex ROM Heimdall one-click flash with bootloaders enabled. Most painless process.