Related
months ago i rooted my capy 2.1 eclair with update.zip file found on here and put it on my internal sdcard mounted on my mac....no more att crapware YE!!!
then i wanted froyo!!! i couldnt wait for samsung so i decided to flash my capy with a cognition rom ....froyo 2.2 nice!!!!
an hour later i booted to recovery mode and for some stupid reason i "reinstalled packages"...oh no!!! my capy is unrooted i cant access superuser privileges, i think its b/c the update.zip i lefted on sdcard unroot my phone
i didnt know what to do and i hate to read threads to find out...hmmmm maybe if i find a update.zip for 2.2 so i can root my capy again...BIG mistake update.zip files are not to be messed with
so i did a reinstall packages again, att white screen came up...goood, then galaxy S screen appeared and STAYED !!! with a off and on vibration...OH NOOO!!! OMG did i bricked my capy??? yep
BUT it goes to download mode!!! so i kinda knew there was still hope...
i read odin can unbrick phones but only work with windows and i m on a mac
but with windows xp in a virtual machine, ok lets try that....i tried with vm ware fusion, parallel and virtualbox and no luck connecting via usb
i dunno anyone with a PC and i dont want to buy one, no choice, gonna use bootcamp and go thru with it...i couldn't find my windows boot cd so i got one off craigslist... oh ****! apple wants windows xp WITH sp2! i only got the original xp. what imma gonna do...google....check this "Slipstreaming Windows XP with Service Pack 2" by Paul Thurrott (sorry i forget which VM was able to burn my cd with)
ok running windows xp sp2 on my imac, i followed this thread except i did not click on "clear master" http://forum.xda-developers.com/showthread.php?t=731989
WOW i m back at square one: eclair 2.1 with all at&t's crapware thats ok better than being stuck with a vibrating samsung/att paperweight!
now i m running di11igaf's rom
[ROM-FROYO] Di11i's Darkyy's Raw Steel-COMPLETELY REDONE & CAPTIVATEDw/SetiroNs Kernel
http://forum.xda-developers.com/showthread.php?t=831542&highlight=jg8
i really like it so far!!!!
a BIG thank you to ALL android developers and forum posters, you guys saved my capy and you are making Android better everyday !!!
ps. my english writing is not very good, if you want to rewrite my thread feel free
If you still had access to download mode, it was never really bricked to begin with...
This has been a huge help my Cousin's Captivate is having issues on Cognition I'll do this tonight and I've been considering the Rom you're using and you just made up my mind flash back to stock, reroot, and flash that Rom.
not development related, not bricked (bricked means the phone won't turn on), this is the exact same procedure that's already been discussed over a million times on this forum.
if you can get into download mode and you have access to ODIN (or even heimdall) you aren't bricked. ODIN requires windows, heimdall does not. Installing windows through bootcamp is no different than just having a windows PC in the first place.
Not really a dev thread but the user is simply sharing his experiences and how he solved an issue. Flaming him is not really necessary even if this procedure was already posted before.
Thread moved to General.
kinda true but if you're a mac user without windows, you are bricked unless u have access to windows or you pay someone to fix your phone or buy a new one, cant return to at&t with a rooted capy!
sorry if i posted my thread in the wrong forum, i thought since i rooted my capy it should belong under development.
@Kaik541: thanks for the heimdall tip
balishared said:
months ago i rooted my capy 2.1 eclair with update.zip file found on here and put it on my internal sdcard mounted on my mac....no more att crapware YE!!!
then i wanted froyo!!! i couldnt wait for samsung so i decided to flash my capy with a cognition rom ....froyo 2.2 nice!!!!
an hour later i booted to recovery mode and for some stupid reason i "reinstalled packages"...oh no!!! my capy is unrooted i cant access superuser privileges, i think its b/c the update.zip i lefted on sdcard unroot my phone
i didnt know what to do and i hate to read threads to find out...hmmmm maybe if i find a update.zip for 2.2 so i can root my capy again...BIG mistake update.zip files are not to be messed with
so i did a reinstall packages again, att white screen came up...goood, then galaxy S screen appeared and STAYED !!! with a off and on vibration...OH NOOO!!! OMG did i bricked my capy??? yep
BUT it goes to download mode!!! so i kinda knew there was still hope...
i read odin can unbrick phones but only work with windows and i m on a mac
but with windows xp in a virtual machine, ok lets try that....i tried with vm ware fusion, parallel and virtualbox and no luck connecting via usb
i dunno anyone with a PC and i dont want to buy one, no choice, gonna use bootcamp and go thru with it...i couldn't find my windows boot cd so i got one off craigslist... oh ****! apple wants windows xp WITH sp2! i only got the original xp. what imma gonna do...google....check this "Slipstreaming Windows XP with Service Pack 2" by Paul Thurrott (sorry i forget which VM was able to burn my cd with)
ok running windows xp sp2 on my imac, i followed this thread except i did not click on "clear master" http://forum.xda-developers.com/showthread.php?t=731989
WOW i m back at square one: eclair 2.1 with all at&t's crapware thats ok better than being stuck with a vibrating samsung/att paperweight!
now i m running di11igaf's rom
[ROM-FROYO] Di11i's Darkyy's Raw Steel-COMPLETELY REDONE & CAPTIVATEDw/SetiroNs Kernel
http://forum.xda-developers.com/showthread.php?t=831542&highlight=jg8
i really like it so far!!!!
a BIG thank you to ALL android developers and forum posters, you guys saved my capy and you are making Android better everyday !!!
ps. my english writing is not very good, if you want to rewrite my thread feel free
Click to expand...
Click to collapse
Lucky you
Im on MBP and trying the exact same process, but in Bootcamp when the phone is in download mode, ODIN would not recognise it through USB.
Not sure if it is Macbook thing. Had problem mounting it too when it was working.
Now im semi-bricked...... arrggggg
bedrmninja said:
Lucky you
Im on MBP and trying the exact same process, but in Bootcamp when the phone is in download mode, ODIN would not recognise it through USB.
Not sure if it is Macbook thing. Had problem mounting it too when it was working.
Now im semi-bricked...... arrggggg
Click to expand...
Click to collapse
Was odin 1click open before u plug the usb cable while pressing the volume buttons? My phone doesn't mount to macbook pro anymore but wakes my computer from sleep when plugged in. does mount on my imac, bootcamp xp2 and powerpc but self eject when copying or selecting files on bothSD cards. Copying files from MAC to SD is fine.
Sent from my SAMSUNG-SGH-I897 using XDA App
i was flashed my phone with the Perception-II-Beta-1 rom and now i cant enter to the recovery or fastboot mode,i need the flash.img of clockwork recovery or like that...to flash the recovery via terminal emulator,please help me.
i only was found the zip archive in the net...
when i try to enter to recovery mode the at&t logo appear and dont change...and when i press power is reboot...
:S when i can say the recovery when the capture program of sdk qtadb...
i was try to flash a zip watching the capture image but,the phone reboot...
Hi, you must be new here. There is no 'fastboot' on galaxy s phones, and you don't need to actually flash clockworkmod. What you need to do is get your phone into download mode and fix it with odin. Take a deep breath and a timeout to peruse the Captivate subforums. There is a wealth of information here about your very problem (particularly the stickied threads).
yes im new here,my old phone was a htc g1...and i was get the captivate on april 23...the problem is that i dont have windows and dont have any way of get it...im using gnu/linux,and odin is only for windows.
pd:sorry my bad english,my national language is the spanish...
That's what you get for being a non-conformist
Anyway, I think there's a linux version called heimdall. Or, you can simply run windows in a virtual machine, or try your luck with wine.
modest_mandroid said:
That's what you get for being a non-conformist
Anyway, I think there's a linux version called heimdall. Or, you can simply run windows in a virtual machine, or try your luck with wine.
Click to expand...
Click to collapse
Odin doesn't like virtual desktops. You need to use heimdall on linux or (barf) mac.
thanks guys,im downloading heimdall to try it...
studacris said:
Odin doesn't like virtual desktops. You need to use heimdall on linux or (barf) mac.
Click to expand...
Click to collapse
works great for me
i run vmware workstation on my laptop thats running ubuntu. thats the only way i use ODIN...in a VM, unless i'm at work
install a VM?? oh i dont know about that.. my computer is at least 200 times bigger than my phone... i dunno if i can program something that big and complicated.....
*sarcasm* aiming for that 51%
nothink...i cant compile heimdall in fedora...is no any form to do that with the terminal emulator? or some like it...
Wait a second.. did you try to flash Percep 2 without flashing the new 2.3.3 bootloaders? If so, you won't be able to reboot back into recovery until you either use odin to go back to a 2.2 rom and keep your old bootloaders, or use odin to flash the stock JVB with the new bootloaders. Either way, the only solution at this point (if my assumption is correct and you flashed a 2.3 rom without the new bootloaders) is to use odin.
i was resolved my problem with odin how you say thank you ...sorry for the disturb...
So i have been getting boot loops on every rom i've tried to flash from my sdcard in cwm. I tried using heimdall one-click on my mac but it keeps getting stuck at "claiming interface". I've already searched many threads but found nothing. Any help on how to fix this?
not to many people are giving up information on heimdall with a Mac. I know the web page talks about something called codeless kext but I don't have a Mac and have no idea what that is. my suggestion is to put Ubuntu on it.... jk but heimdall on Ubuntu is stupid easy, getting the video and wifi and cd-rom can be another story depending on your hardware. I think most Mac users are not to savvy or they'd just be running Linux I know osx is a great OS but it seems to lack users that like to tinker. well not totally true but with so few users the guys that really know Macs are hard to come by.
are you getting that message when you are installing one click to mac ?
Ok, I know I'm not the first to have this screen pop up because of a failed flash and I did indeed search before asking. I've been searching since late last night and so far I'm stumped. I've installed and reinstalled Samsung Kies to get the official drivers quite a few times so far (because the drivers Heimdall installs don't play well with ODIN) and that gets ODIN to recognize the phone but once I click start after putting in the ROM I am trying to install, it just sits saying "SetupConnection" for as long as I choose to let it sit there. If I try Heimdall, it changes drivers to one that is usable and then fails to get a response at handshake with Loke. I've never had this happen before. I was coming from ParanoidAndroid trying to unroot the phone to sell and now I'm here. Any ideas?
That is an alternate download mode that shows after a failed firmware update. Use Heimdall and one click back to stock.
You will probably need to uninstall any drivers installed by Odin in order for heimdall to work.
Sent from my SGH-T959V using xda premium
I'm aware of that. I know what the screen means. I only mentioned it as a point of reference. My point was that after getting that screen, everything I have tried to flash has failed. That's one of the ways I attempted. Any heimdall does the same thing, though. It fails at handshake with Loke. Being that there is no log, I am not entirely sure what is causing ODIN to fail but 2 different roms have had the same effect. Thanks for the response. By the way, I'm sorry if I seem snappish, I didn't mean to be. Just been a long aggravating night.
Heimdall One-Click. Not Heimdall. Use the second link in my signature. Read the notes and you will learn you can install Heimdal One-Click drivers for one usb port and Samsung drivers one a different usb port without confict.
I found the one click unbrick which worked like a charm. Going to attemp to get this thing back to stock again. Thanks for your help.
Oh, and by the way, this is the heimdall I was using. One click and stock KJ6. I've never tried actual heimdall. Didn't honestly know that there was a heimdall standalone version. By the time I started messing with this phone, all the one click stuff was already made. Made it a lot easier than the old days of rooting the G1, so I never looked for anything else til now. No point in making a job harder.
I need some help.
I am running a Linux system and am trying to flash the firmware on my Samsung phone.
Odin is out because, while I can start it via emulator, it will never be able to actually communicate with the phone via usb.
JOdin3, which is java and platform-independent, sees my phone, communicates with it... and insists that every blessed file I feed it is corrupt. Straight from Samsung's own website? 'Corrupt,' according to JOdin3.
Heimdall. Ah, yes, Heimdall of the elusive 'Heimdall Firmware Packages' that nobody seems able to explain how to make.
I have spent days of my life systematically hunting all this down across dozens of websites, figuring out how to get Odin, JOdin3, Heimdall, Samfirm, Samloader and I can't think what others working on my OS, only to find that every one of these programs breaks in the end.
Is this firmware flashing thing just a big joke? Or is it actually possible?
micheal3chaife said:
I need some help.
I am running a Linux system and am trying to flash the firmware on my Samsung phone.
Odin is out because, while I can start it via emulator, it will never be able to actually communicate with the phone via usb.
JOdin3, which is java and platform-independent, sees my phone, communicates with it... and insists that every blessed file I feed it is corrupt. Straight from Samsung's own website? 'Corrupt,' according to JOdin3.
Heimdall. Ah, yes, Heimdall of the elusive 'Heimdall Firmware Packages' that nobody seems able to explain how to make.
I have spent days of my life systematically hunting all this down across dozens of websites, figuring out how to get Odin, JOdin3, Heimdall, Samfirm, Samloader and I can't think what others working on my OS, only to find that every one of these programs breaks in the end.
Is this firmware flashing thing just a big joke? Or is it actually possible?
Click to expand...
Click to collapse
I'm a part-time Linux user also but I can't say that I've ever had luck with using Heimdall to flash Samsung devices. Many people have used it and had success but for me it has always been a pain getting the right "extra" packages installed and configured correctly for Heimdall to function correctly, it involves more than just installing and running Heimdall.
In my experience, Odin on a Windows PC is hands down the best way to go for flashing Samsung Devices.
Also, when you say they all fail in the end, what do you mean? Are they not working at all or are you able to begin the flash but it fails before it finishes the flash?
Droidriven said:
I'm a part-time Linux user also but I can't say that I've ever had luck with using Heimdall to flash Samsung devices. Many people have used it and had success but for me it has always been a pain getting the right "extra" packages installed and configured correctly for Heimdall to function correctly, it involves more than just installing and running Heimdall.
In my experience, Odin on a Windows PC is hands down the best way to go for flashing Samsung Devices.
Also, when you say they all fail in the end, what do you mean? Are they not working at all or are you able to begin the flash but it fails before it finishes the flash?
Click to expand...
Click to collapse
Hi, thanks for the sympathetic response (read: 'shouder to cry on').
"Break" in the sense that eventually, each of the programs I have tried - Heimdall, JOdin3, and Odin - have shown errors that, so far, have proven fatal:
*Heimdall requires 'Heimdall Packages' that seem to exist nowhere
*Odin fails to communicate with the phone
*JOdin3 returns a 'corrupted file' message when one directs it to the firmware to upload and flash. This issue has been reported to the maintainer's github as of 12 days ago, meaning it is a very recent issue.
The Heimdall issue *may* have a workaround - one can try, as per the maintainer's instructions on his github, feeding the component files one by one to the main process. I will try that.
A further possibility lies in the fact that previously, I had not enabled 'USB debugging' on the phone itself, which may or may not help with the interface.
There is also ADB, which I took a cursory look at last night. ADB appears to be able to work to move packets between a computer and a phone.
There is the option, on Samsung phones, to 'Appy update from SD card', which is what I propose to try now.
Latly, there is the option of installing an entirey different OS on the phone, and to hell with Android (?).
I will keep all you folks who are now rooted to the edge of your seats updated as things move along.
micheal3chaife said:
Hi, thanks for the sympathetic response (read: 'shouder to cry on').
"Break" in the sense that eventually, each of the programs I have tried - Heimdall, JOdin3, and Odin - have shown errors that, so far, have proven fatal:
*Heimdall requires 'Heimdall Packages' that seem to exist nowhere
*Odin fails to communicate with the phone
*JOdin3 returns a 'corrupted file' message when one directs it to the firmware to upload and flash. This issue has been reported to the maintainer's github as of 12 days ago, meaning it is a very recent issue.
The Heimdall issue *may* have a workaround - one can try, as per the maintainer's instructions on his github, feeding the component files one by one to the main process. I will try that.
A further possibility lies in the fact that previously, I had not enabled 'USB debugging' on the phone itself, which may or may not help with the interface.
There is also ADB, which I took a cursory look at last night. ADB appears to be able to work to move packets between a computer and a phone.
There is the option, on Samsung phones, to 'Appy update from SD card', which is what I propose to try now.
Latly, there is the option of installing an entirey different OS on the phone, and to hell with Android (?).
I will keep all you folks who are now rooted to the edge of your seats updated as things move along.
Click to expand...
Click to collapse
USB debugging makes a difference. Have you tried using older or different versions of Heimdall?
Are you running a VM to run windows and windows programs on linux or are you using wine to run windows programs? Wine doesn't work well enough to make it a viable option to run Odin.
I really suggest you bite the bullet and use a Windows system to use Odin. As long as you haven't corrupted any of the partitions on the device, flashing via Odin on a Windows PC will be effortless, a few clicks and a few minutes, done and done.
I think it could be dependent on the quality of the packages built by the packagers for your distro as to whether 'heimdall' works for you. I recently flashed LineageOS (2 days ago) on my old Galaxy Note 10.1 (2014) tablet using heimdall. I posted about it here: https://forum.xda-developers.com/f/galaxy-note-10-1-2014-edition-q-a-help-troubl.2502/
Note that hardware aspects such as a quality USB cable can at times be issues, and you may have better luck using a PC's USB-2 port instead of a USB-3 port.
In my case, for openSUSE LEAP-15.2 I successfully used heimdall-1.4.2
I also used android-tools-9.0.0 packaged for same openSUSE version, which provided 'adb' and 'fastboot'. While 'adb' worked for me, I could not not get 'fastboot' to detect my tablet when the tablet was in 'Odin' mode - and hence I could not flash with 'fastboot'. Fortunately heimdall did detect the Tablet when the Tablet was in 'odin' mode, and I was thus able to flash TWRP from 'heimdall'. I note specifying 'RECOVERY" in 'heimdall' did not work for me, but instead specifying the 'Entry' location for the flash (after checking the PIT) did work for me. Again, documented the details in that thread above.
In all cases on my GNU/Linux I used command line and not GUI front ends.
Goodl luck in your efforts.
Droidriven said:
USB debugging makes a difference. Have you tried using older or different versions of Heimdall?
Are you running a VM to run windows and windows programs on linux or are you using wine to run windows programs? Wine doesn't work well enough to make it a viable option to run Odin.
I really suggest you bite the bullet and use a Windows system to use Odin. As long as you haven't corrupted any of the partitions on the device, flashing via Odin on a Windows PC will be effortless, a few clicks and a few minutes, done and done.
Click to expand...
Click to collapse
I do not have ready access to a Windows machine, alas... Thanks for the other suggestions. Yes, I've been trying with wine, but with USB debugging disabled. My next attempt will probably be with Heimdall + USB debugging.
If I go the VM route, do you have a suggestion on how to set that up?
RE: Heimdall, I was under the impression that the most recent version (1.4.2, if I'm not mistaken) is best.
Again, thanks for the imput. Wish me ... maybe not luck, but continued systematic determination. And a little common sense.
You can run ADB wirelessly, means over Wi-Fi. So no Windows machine is required.
xXx yYy said:
You can run ADB wirelessly, means over Wi-Fi. So no Windows machine is required.
Click to expand...
Click to collapse
I"m not sure that helps them.
micheal3chaife said:
Heimdall. Ah, yes, Heimdall of the elusive 'Heimdall Firmware Packages' that nobody seems able to explain how to make.
....
Is this firmware flashing thing just a big joke? Or is it actually possible?
Click to expand...
Click to collapse
I hope you managed to finally succeed.
'Fresh' on the successful install of LineagOS-14.1 on my Samsung Galaxy-10.1 (2014) using adb and Heimdall on openSUSE-LEAP-15.2 (v.1.4.2 of heimdall) I then a couple of days ago proceeded to install LineageOS-14.1 on my wife's old Samsung Note-8 tablet.
As before, I pre-positioned the zip files for lineageOS and for GAPPS on her tablet, and then used heimdall to flash TWRP from my GNU/Linux PC.
it took me 3 attempts to flash TWRP, with the first failed attempted breaking the regular Android 4.1 boot to the Tablet, but fortunately it would still boot to the Tablet's recovery 'download' (flashboot) mode. The issue with the failures with me was a somewhat flaky USB cable. This is the best of about a dozen USB cables I own, and it works great for charging .... but for data transfer in a flash, my experience is the cable has to be very very VERY good. Note I was using a USB2 port.
Once TWRP was flashed, I tried to boot the Tablet to recovery mode, but the darn thing booted instead to the old Android 4.1. I was afraid that would wipe the TWRP, ... so I then with the Tablet still powered, ran 'adb' with appropriate recovery reboot options (from my GNU/Linux with Tablet connected), and the Tablet fortunately booted to TWRP (and it had not yet been wiped).
With TWRP running it was a simple matter to flash LineageOS and GAPPS. This time, BEFORE rebooting after the LineageOS/GAPPS flash, I was then careful to ensure TWRP re-flashed/installed, and it kept TWRP on the Samsung Galaxy Note-8. With my previous Samsung Galaxy Note-10.1 (2014) install I did not do that, and I had TWRP wiped after my reboot to LineageOS.
Again good luck in your efforts. I can say heimdall in GNU/Linux does work (together with adb).
micheal3chaife said:
I need some help.
I am running a Linux system and am trying to flash the firmware on my Samsung phone.
Odin is out because, while I can start it via emulator, it will never be able to actually communicate with the phone via usb.
JOdin3, which is java and platform-independent, sees my phone, communicates with it... and insists that every blessed file I feed it is corrupt. Straight from Samsung's own website? 'Corrupt,' according to JOdin3.
Heimdall. Ah, yes, Heimdall of the elusive 'Heimdall Firmware Packages' that nobody seems able to explain how to make.
I have spent days of my life systematically hunting all this down across dozens of websites, figuring out how to get Odin, JOdin3, Heimdall, Samfirm, Samloader and I can't think what others working on my OS, only to find that every one of these programs breaks in the end.
Is this firmware flashing thing just a big joke? Or is it actually possible?
Click to expand...
Click to collapse
Look here.