Related
Long story short, I messed up my Captivate.
I am on a mac so no odin... can anyone give clear instructions on how to install a new firmware in recovery mode or using a mac with adb?
I have searched and searched but still have no clue on where to begin.
Thank you in advance
Start here read all of what the topic says. Yes I know it's a tad long but you'll wanna read all of it because I'll bet 95% of the questions you'll have or issues you'll run into will be covered.
search for "heimdall"
it may need a terminal window open to use it. i dont know macs very well but i run in in mint with kde and like it. i think there are mac packages but if not it can be compiled for mac, sorry i cant help in that area.
it's much like odin but is developed and maintained by someon in the comunity and is all open source.
you can also use virtualbox or similar virtual machine software and install windows on it and run odin in the virtual machine.
edit: heimdall download page
http://www.glassechidna.com.au/products/heimdall/
If your on a mac then your your only options are get a copy of windows and install on your mac thru bootcamp. Heimdall works on a mac just fine if you have the right bootloaders but if you ever used odin oneclick to flash back to stock then for sure you have the wrong ones and since it's common to flash to stock to root your and flash a custom rom. I don't know of any one who has used it successfully on a mac in that specific situation. Another option is to use Odin with VM on Linux machine or just use a friends machine.
Sent from my SAMSUNG-SGH-I897
1tontomato said:
If your on a mac then your your only options are get a copy of windows and install on your mac thru bootcamp. Heimdall works on a mac just fine if you have the right bootloaders but if you ever used odin oneclick to flash back to stock then for sure you have the wrong ones and since it's common to flash to stock to root your and flash a custom rom. I don't know of any one who has used it successfully on a mac in that specific situation. Another option is to use Odin with VM on Linux machine or just use a friends machine.
Sent from my SAMSUNG-SGH-I897
Click to expand...
Click to collapse
i used odin oneclick many times, and heimdal works, only you need bootloaders if you select repartition. i just flash with no pit file or bootloaders at all. also i used heimdall with gb bootloaders on it. no problem.
you only need pit if you repartition. you only need to repartition of you messed up the filesystem badly, and for heimdall if you use repartition the program requires bootloaders as well as pit. odin couldnt care less if you have the bootloaders or not for repartition. im not sure why but that is how heimdal works.
Dani897 said:
i used odin oneclick many times, and heimdal works, only you need bootloaders if you select repartition. i just flash with no pit file or bootloaders at all. also i used heimdall with gb bootloaders on it. no problem.
you only need pit if you repartition. you only need to repartition of you messed up the filesystem badly, and for heimdall if you use repartition the program requires bootloaders as well as pit. odin couldnt care less if you have the bootloaders or not for repartition. im not sure why but that is how heimdal works.
Click to expand...
Click to collapse
You did this on a mac?
Sent from my SAMSUNG-SGH-I897
1tontomato said:
You did this on a mac?
Sent from my SAMSUNG-SGH-I897
Click to expand...
Click to collapse
why would the mac be different from linux if the problem is withthe bootloaders on the phone. seems illogical but i guess i have seen stranger things
Here is a link to the i9000 forums that explains a little better but the bootloaders on the 2.1 rom don't allow the phone to register in the mac OS. http://forum.xda-developers.com/showthread.php?t=878686
Sent from my SAMSUNG-SGH-I897
1tontomato said:
Here is a link to the i9000 forums that explains a little better but the bootloaders on the 2.1 rom don't allow the phone to register in the mac OS. http://forum.xda-developers.com/showthread.php?t=878686
Sent from my SAMSUNG-SGH-I897
Click to expand...
Click to collapse
ohh it's similar to a driver issue, i though you meant it would cause a problem with the phone for some reason. i get it. that can suck because vm software can be a pain. you may need to manually install the drivers in windows when it is a guest os.
Ok so i've tried to upgrade to GummyCharged, using the Odin version (figured it would have been simpler than doing it in CWM... don't ask why)
In any case, it keeps failing to install the Factoryfs.rfs
I've tried the stock ED1 file for the phone, tried a few other roms lying around, tried re-partitioning with the pit file floating around here.
It seems like it just will work half way then thats it..
I can hook my vibrant up and it works fine no problem, what could the issue be here!?!?!?!!
Try Heimdall or PST.
Try downloading from a different source as well.
Sent from my SCH-I510 using XDA App
Hit start, and when it verifies the MD5, slip your battery in. Or, if your battery is in during the process, take it out!
Sent from my Droid Charge running GummyFroyo 1.9.1
Booting it into SamPST/ODIN mode without the battery in, then sliding it in immediately before starting the flash, seemed to solve this issue for me.
I've been trying to figure this out for hours...
I recently got a Charge (I also have an old Fascinate). and I'm trying to root it. It came out of the box with EE4. I primarily use a macbook pro, but have learned that I can't root EE4 with it. So, I booted up my old school desktop PC.
I can't get Odin 1.82 (or 1.3 for that matter) to recognize my Charge or my Fascinate. I've tried 4 different Samsung driver files, and the computer recognizes the phones in USB Storage mode just fine (telling me that the usb cable is working fine). I can transfer files and everything. And yes, the phones have the yellow road sign looking thing and say "Downloading..."
But when I put either in download mode:
USB device not Recognized.
One of the USB devices attached to this conputer has malfunctioned and Windows does not recognize it. For assistance click this message.
Basically, acts as though no driver is installed. and when I click the message and go to Update the driver (while still in download mode), I went to C:\Program Files\Samsung\USB Drivers\, but there's tons of folders and non of them contain a working driver for download mode (I tried them all).
I don't care about the Fascinate. I only mentioned it because I thought there was something to neither phone working. And this is the first (and only) time I've tried to get Odin to work (ie. it hasn't worked ever).
I've searched all over the forums, internet, and soul trying to figure this out. I can't be the only one this has happened to. Or I'm missing something really fking obvious.
I'm on an old custom made desktop with an AMD 1700+ processor running Windows XP (not 64 bit).
tifford said:
I've been trying to figure this out for hours...
I recently got a Charge (I also have an old Fascinate). and I'm trying to root it. It came out of the box with EE4. I primarily use a macbook pro, but have learned that I can't root EE4 with it. So, I booted up my old school desktop PC.
I can't get Odin 1.82 (or 1.3 for that matter) to recognize my Charge or my Fascinate. I've tried 4 different Samsung driver files, and the computer recognizes the phones in USB Storage mode just fine (telling me that the usb cable is working fine). I can transfer files and everything. And yes, the phones have the yellow road sign looking thing and say "Downloading..."
But when I put either in download mode:
USB device not Recognized.
One of the USB devices attached to this conputer has malfunctioned and Windows does not recognize it. For assistance click this message.
Basically, acts as though no driver is installed. and when I click the message and go to Update the driver (while still in download mode), I went to C:\Program Files\Samsung\USB Drivers\, but there's tons of folders and non of them contain a working driver for download mode (I tried them all).
I don't care about the Fascinate. I only mentioned it because I thought there was something to neither phone working. And this is the first (and only) time I've tried to get Odin to work (ie. it hasn't worked ever).
I've searched all over the forums, internet, and soul trying to figure this out. I can't be the only one this has happened to. Or I'm missing something really fking obvious.
I'm on an old custom made desktop with an AMD 1700+ processor running Windows XP (not 64 bit).
Click to expand...
Click to collapse
the pc itself doesn't sound like the problem, at least not directly... the only things I can suggest would be to either try different USB ports, a different cable, uninstalling and reinstalling the driver: http://dl.dropbox.com/u/34782489/SAMSUNG_USB_Driver_for_I510_v1.3.1900.0.exe (which is made specifically for the Charge), disabling any antivirus that may be installed (or running Odin as administrator), and making sure USB debugging is ticked off under 'development' in applications settings
thanks for the quick response, but unfortunately, i've tried all of those except for disabling debugging. and, sadly, that didn't do the trick.
i've tried all of the usb cables i own (about 7). i've uninstalled and reinstalled divers from every link posted, and rebooted after each time. i've tried all of my usb ports on my computer. i've even cleared out the usb history in regedit.
::sigh::
tifford said:
thanks for the quick response, but unfortunately, i've tried all of those except for disabling debugging. and, sadly, that didn't do the trick.
i've tried all of the usb cables i own (about 7). i've uninstalled and reinstalled divers from every link posted, and rebooted after each time. i've tried all of my usb ports on my computer. i've even cleared out the usb history in regedit.
::sigh::
Click to expand...
Click to collapse
well if it was just the Charge I would say there may be a problem with the phone or somethings not being done right, I have heard of some people having phones (Fascinate mostly) that won't go into download mode for Odin but will work perfectly with everything else... however both phones not working seems to be some kind of issue with the pc or cable, but I couldn't say for sure as I'm not knowledgable on the hardware of android phones
1700+. That's REALLY old school.
Sent from my Droid Charge running GummyCharged 2.0
still can't get it to work...
is there any way to go back to eb01 or whatever without root or Odin?
or can someone post the Download Mode driver?
tifford said:
still can't get it to work...
is there any way to go back to eb01 or whatever without root or Odin?
or can someone post the Download Mode driver?
Click to expand...
Click to collapse
If anyone is an ADB guru here they may know how to do it with that, like pushing CWM to the phone and then you can probably flash to stock... I only know how to do basic things like install apk's and logcat
I know with most phones, you can't go back without root because the system doesn't let you. I'm used to the Droid incredible and incredible 2, where rooting and flashing roms is easy as pie with some knowledge of adb and cwm. none of the ed01, ee4, fu69 stuff to worry about. Odin seems very easy, and its damn near impossible to permanently brick your phone if you have it. BUT I can't get it to work.
is there an adb / non-Odin root method for ee4?
if I understand correctly, the gingerbreak method and one click method don't work with ee4. (I've tried both of those too)
Sent from my SCH-I510 using xda premium
Your on Mac? Have u tried using heimdall?
Sent from my SGH-I897 using XDA Premium App
I've tried using heimdall on my Mac and can't get it figured out. heimdall 1.3 (older heimdalls like 1.1.1 wont open) requires a framework.XML file which Odin roms don't have. I can create one but the only way I can do that is by using a .pit file (which creates a partition) which I'd have to take from other rom files. the only way can see it working is by Frankensteining it together to get it to flash which does doesn't seem right.
I could be completely misunderstanding how to get it to work. I could just use heimdall in terminal, but I don't understand it enough yet to attempt. heimdall 1.3 looks nothing like the way I thought it would (where I select all the recovery, bootloader, etc files individually)
grr...
Sent from my Xoom using Tapatalk
You know we DO have a PIT file right?
Sent from my Galaxy Tab running MIUI
which should I use? depending on the rom I use, does it matter which PIT file I use?
Sent from my SCH-I510 using xda premium
tifford said:
which should I use? depending on the rom I use, does it matter which PIT file I use?
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
there's only one PIT file and its for getting to stock 2.2 Froyo
so, I should only use it for flashing back to stock 2.2?
can I use it for flashing a 2.2 rom like gummy charged 1.9.1?
does it matter which stock 2.2 I use? ed01? ee4?
Sent from my SCH-I510 using xda premium
tifford said:
so, I should only use it for flashing back to stock 2.2?
can I use it for flashing a 2.2 rom like gummy charged 1.9.1?
does it matter which stock 2.2 I use? ed01? ee4?
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
yes only for stock 2.2 because it is what reformats your partitions after they've been converted to ext4 with lagfix/voodoo
as for stock roms EE4 is the latest and hasn't given me any problems when Odining but I suppose the others like ED1 or ED2 would be fine
just bricked it.
I was trying to revert back to ed1 so that I could root from there with gingersnap / gingerbreak through adb
I downloaded the Verizon stock ed1 file and pit file, inserted all of the files in the correct place (param = parameters.rfs etc.) it got to uploading kernel and failed. now my phone boots into a picture of a cellphone then an arrow pointing at a computer with a yellow triangle with a !
and I have no way of unbricking it.
I'm going to borrow someone's windows laptop and Odin it back to health (hopefully)
then I'm returning it for a thunderbolt. this phone has driven me mad.
Sent from my Xoom using Tapatalk
tifford said:
just bricked it.
I was trying to revert back to ed1 so that I could root from there with gingersnap / gingerbreak through adb
I downloaded the Verizon stock ed1 file and pit file, inserted all of the files in the correct place (param = parameters.rfs etc.) it got to uploading kernel and failed. now my phone boots into a picture of a cellphone then an arrow pointing at a computer with a yellow triangle with a !
and I have no way of unbricking it.
I'm going to borrow someone's windows laptop and Odin it back to health (hopefully)
then I'm returning it for a thunderbolt. this phone has driven me mad.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
soft brick, you need to odin EE4 stock with the PIT file and it'll be back to normal.. its almost impossible to permabrick this phone through user error, only if the boot.bin files are corrupted afaik
blazing through on my 4G Droid Charge
tifford said:
just bricked it.
I was trying to revert back to ed1 so that I could root from there with gingersnap / gingerbreak through adb
I downloaded the Verizon stock ed1 file and pit file, inserted all of the files in the correct place (param = parameters.rfs etc.) it got to uploading kernel and failed. now my phone boots into a picture of a cellphone then an arrow pointing at a computer with a yellow triangle with a !
and I have no way of unbricking it.
I'm going to borrow someone's windows laptop and Odin it back to health (hopefully)
then I'm returning it for a thunderbolt. this phone has driven me mad.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
We don't root through ADB.
Sent from my Droid Charge running GummyCharged 2.0
i borrowed a friend's windows laptop. i used Odin to go back to stock ED1
Then ROOTED THROUGH ADB on my mac...
i'm a happy camper now.
Thanks for the help guys
Have fun with ED1.. . If you update it will break root.
Sent from my Droid Charge running GummyCharged 2.0
I have to use Heimdall if I'm to flash my phone. At home I only have access to Mac. I used a PC at work to root my phone (superoneclick was waaay easy), but I don't want to push my luck with IT and my boss at work.
Is there a list of Heimdall packages for the SGS4G anywhere? I've been searching and can't find them anywhere. Maybe Heimdall 1.3 is too new??
I am hoping to use Audiophile because it just chaps my a$$ that I can't play a stock music player (TMOUS) without it skipping out (paucity of cpu cycles I imagine). I very much appreciate the post RaverX3X put up about Audiophile recently. However he focused on Odin and I can't use Odin.
Any ideas anyone?
No one has made any firmware packages for it.
You'd only use Heimdall for flashing a stock rom base with a custom kernel and then you'd have to flash audiophile through CWM anyway.
I'd make a firmware package for you if I wasn't on my way out soon though. Maybe if no one else has done it when I get back I'll set something up for you.
Alright I made the heimdall package for you, I haven't tested it though, so proceed at your own risk.
http://sourceforge.net/projects/tea..._kh2_with_kg4_kernel_heimdall.tar.gz/download
Did it work? I want to know so I can post it on the original thread.
You gave some qualifications about using CWM before putting up the Heimdall package. Since this is my first time flashing and I only have my SGS4G so I am going slowly. I got CWM installed and backed up. I downloaded your file and have it on my Mac. Before I try to use, I want to be sure I know what I'm doing. So I'm reading a lot of XDA first.
You will be the second to know I got it installed and working (with me being the first obviously. )
Thanks for the help.
You actually don't need CWM at all. You'll wind up with CWM after flashing this.
Okay, I'll give this one a try. In a previous message you said that after using Heimdall, I still need to flash Audiophile using CWM. Is that still true? Is there any other software I need to flash with CWM?
You might need to flash my busybox_installer.zip but I think Raver may have included that in the audiophile ftw installer.
Well I tried but Heimdall could never see my phone. I can connect USB storage using the phone, but Heimdall can't detect the device at all.
I've searched XDA trying to find MAC drivers for the phone that might be better than mine, but I've not found anything yet.
http://www.glassechidna.com.au/products/heimdall/
Scroll down and find the OSX version (Heimdall suite 1.3.0). It comes with Codeless kext (aka driver). It should install libusb for you.
Hmmm, I installed that package. I do not know why kext didn't work. I know I have a system reboot since then.
Maybe I'll uninstall and try to re-install.
Thanks A Lot
FBis251 said:
Alright I made the heimdall package for you, I haven't tested it though, so proceed at your own risk.
http://sourceforge.net/projects/tea..._kh2_with_kg4_kernel_heimdall.tar.gz/download
Click to expand...
Click to collapse
Hello. First of all I want to thank you for this wonderful rom. I know how to use Odin but recently I got a Mac so I'm still learning how to use it. I decided to upgrade to gingerbread last night and then hell went broke loose I almost BRICKED my phone:-(. But searching the XDA this morning I found this thread and BAAAMMMM my phone is working again. I dunno how it works but I know You put effort on doing this so again Thanks a Lot!!!!!
MjLvMj said:
Hello. First of all I want to thank you for this wonderful rom. I know how to use Odin but recently I got a Mac so I'm still learning how to use it. I decided to upgrade to gingerbread last night and then hell went broke loose I almost BRICKED my phone:-(. But searching the XDA this morning I found this thread and BAAAMMMM my phone is working again. I dunno how it works but I know You put effort on doing this so again Thanks a Lot!!!!!
Click to expand...
Click to collapse
Awesome, I'm glad it worked for you. I'll be making the Froyo portion of the heimdall package available soon in order to update my GB Starter Pack guide for mac/linux.
How straightforward was the install by the way? I'm still trying to get feedback from users.
I am very happy heimdall is working for you and you got the ROM flashed.
Very frustrated that I can't get heimdall to see my phone. I have CWM installed and I have the RootExplorer app working and I can see my SD card as a USB drive on my Mac. Is it possible to flash with just those three tools?
All the guides I see seem to focus on Odin or Heimdall. Do they do some magic that I can't accomplish on my own?
ustamills said:
I am very happy heimdall is working for you and you got the ROM flashed.
Very frustrated that I can't get heimdall to see my phone. I have CWM installed and I have the RootExplorer app working and I can see my SD card as a USB drive on my Mac. Is it possible to flash with just those three tools?
All the guides I see seem to focus on Odin or Heimdall. Do they do some magic that I can't accomplish on my own?
Click to expand...
Click to collapse
Sadly there's no safe way to flash bootloaders using CWM, which is the only reason we're using Odin/Heimdall. I can't diagnose the problems on a mac since I don't own one, but have you tried removing heimdall, restarting, reinstalling, restarting and trying again? Might make it work.
Thanks A Lot
FBis251 said:
Awesome, I'm glad it worked for you. I'll be making the Froyo portion of the heimdall package available soon in order to update my GB Starter Pack guide for mac/linux.
How straightforward was the install by the way? I'm still trying to get feedback from users.
Click to expand...
Click to collapse
Well I mess up with the bootloaders cuz Im coming from trigger rom froyo. But luckily for me I able to put the phone on Download Mode and the Heimdall just detected it. I just follow the read me files on the Heimdall then put your files on it. Press start and it work like magic... I have Gingerbread Phone
---------- Post added at 11:13 PM ---------- Previous post was at 11:12 PM ----------
ustamills said:
I am very happy heimdall is working for you and you got the ROM flashed.
Very frustrated that I can't get heimdall to see my phone. I have CWM installed and I have the RootExplorer app working and I can see my SD card as a USB drive on my Mac. Is it possible to flash with just those three tools?
All the guides I see seem to focus on Odin or Heimdall. Do they do some magic that I can't accomplish on my own?
Click to expand...
Click to collapse
Just try to put your Phone on Download Mode and pray that Heimdall can detect it. Then your good!!!!
i tried flashing my sgs4g with odin and now all i get is the samsung galaxy s 4g from tmobile screen and it just keeps loading like that in a loop.
at first when I tried odin, i was not able to reboot and my screen displayed all sorts of colors and just did not work. I unplugged and tried odin again and came up to this point. now i'm trying to just get my phone working again. help anyone?
Ok so I've been rooted and unlocked for a while now, but stayed with the stock rom as when I tried out Synergy Nightlies it gave me some errors. So I went to try out CleanRom 2.1, people liked it and I didn't notice any flashing errors. So I flashed it through CWM 6.0.1 and it gave me the yellow exclamation mark saying I had unauthorized data on my phone. So I followed the sticky on how to unbrick my phone using the 2 boot loaders and the root66 stock image. My issue is that when running the root66 stock image through Odin it fails at _XmitData_Read, which seems to be somewhere in system.img.ext4. I've tried rebooting the computer, the phone, Odin, it just doesn't work. So when I reboot my phone after the failure I get Odin auto loading saying:
Odin Mode
Product Name: SCH-I535
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Official
Qualcomm Secureboot: Enable
Then an image of a phone, 2 dots, a yellow exclamation, 2 dots and a computer are shown with the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.
Anyone able to help me?
can you still get to odin mode? also if you have kies installed on the computer erase it.
kidhudi said:
can you still get to odin mode? also if you have kies installed on the computer erase it.
Click to expand...
Click to collapse
Kies isn't installed on the computer and yes I am still able to get into Odin Mode.
I'm under the impression that "unauthorized software" message comes from the locked bootloader (if I'm wrong about that someone plese correct me.)
Sounds like you're functional enough to be able to Odin back to stock and go from there - that's what I'd try. See the stickied thread in the Q&A forum.
I would run the FULL VRALF stock image through ODIN to return to stock. That is always the safest way out of a sticky situation.
Thanks guys, according to another post the version of EZ-Unlock I used most likely gave a false report and never actually unlocked my phone. The problem with going back to stock, which if what I'm trying to do, is that it fails.
Could be an USB issue - an intermittent connection would be most likely to cause problems while sending the system partition since that's the biggest. I've had problems using adb from time to time if I plug into one of the front-panel ports on my PC but no trouble with one on the back.
Maybe try switching ports or try a different cable ...
Actually what usb plug are you using on your computer? You should be using one in the back of your computer by the power supply. Seen the front jacks not work correctly for large transfers. Finally, try another usb cable.
Sent from my SCH-I535 using xda app-developers app
Strange.... i was able to flash syergy on thefirst try. Never used odin during the whole process....
If youre rooted you need to make sure you have a custom recovery in place like cwm or twrp. Make sure you make a nand-backup.
I used casual to flash unsecure bootloader, with that and recovery in place you should be able to flash roms without any hitches....
I could never find a comprehensive guide on using odin so i never got around to testing it
kintwofan said:
Actually what usb plug are you using on your computer? You should be using one in the back of your computer by the power supply. Seen the front jacks not work correctly for large transfers. Finally, try another usb cable.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
So far I've tried 3 different USB cables and both a desktop, both front and back ports and a laptop, each one fails on the write of XmitData under system.img.ext4
I had a custom recovery installed and Odin is only being used to get me back to a stock rom, otherwise I did all my flashing under CWM 6.0.1 or twrp. I think the whole fake unlocked bootloader just hard bricked the software.
EDIT: Come to think of it I remember waking up to my phone in download mode. I think Verizon tried to install the update to my phone while I was sleeping. Granted it failed at the end, but I'm wondering if that did something to brick me now.
If you can get in download mode it can be saved. I woud re download the stock firmware or the 66, but personally i would go bone stock. You may just have a bad download.
Sent from my SCH-I535 using xda app-developers app
kintwofan said:
If you can get in download mode it can be saved. I woud re download the stock firmware or the 66, but personally i would go bone stock. You may just have a bad download.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Yea, I'm currently downloading at the speed of slug the newest update from the forums, will probably just redownload at home, since it's going to take over an hour >.<
EDIT:
Does anyone have a link for an older EZ-Unlocker, that is known to work, so that I don't get this problem yet again.
FIXED!
Ok, so using the newest stock rom from the dev forum worked. Can someone please give me a link to an old EZ-Unlocker so I can flash without worrying about another massive brick in my palm. I'm guessing that running the original root66 stock rom through dropbox somehow corrupted it.
LlirasChosen said:
Ok, so using the newest stock rom from the dev forum worked. Can someone please give me a link to an old EZ-Unlocker so I can flash without worrying about another massive brick in my palm. I'm guessing that running the original root66 stock rom through dropbox somehow corrupted it.
Click to expand...
Click to collapse
I personally suggest not using the app if you already had trouble. Just root your phone using the Debug Root method in Development, download the aboot.img from Adam Outlers thread HERE to your phone, and run the commands at the very bottom in Terminal Emulater app (from the market).
That way you know for sure your bootloader is unlocked. This is what I have done and never had an issue.
Edit: Glad you got your issue resolved!