Related
First off, I am not a noob. Flashed many roms on many different phones, and up until yesterday was happily flashing away on my s2. But now I'm stumped and no guide or search function has helped me so far. I've tried Entropy's return to stock, and several other threads, to no avail. I was flashing JB yesterday when something borked on the install. Long and short of it is that I cannot even get into recovery to fix it. I CAN however, get into download mode. I downloaded Heimdall with the frontend, downloaded the latest stock image, and booted my phone into download mode to install the image. The frontend says it detects the phone, but when I try to install the firmware it gives a .libs error and will not establish a connection to the phone. I am using Ubuntu 12.04 32bit, do I need ADB set up to use Heimdall? If so, then I need a guide to install on 12.04 since I have not had any luck getting ADB working on my machine. I am a noob to Linux, so be kind.
Regards, Scott
I would just use heimdall command line. I don't use linux much, but Entropy512 always said he didn't use the front end on linux. The command line directions are in his thread, and also in my guides.
I saw your thread, tried the command line, that's when I got the could not connect with phone error.
Sent from my HTC Sensation using xda app-developers app
Scott41373 said:
I saw your thread, tried the command line, that's when I got the could not connect with phone error.
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
If you haven't tried it already, try running heimdall as root. If I remember correctly, that's what I had to do on my Fedora 16 system to flash an image with heimdall.
run heimdall with su or sudo command.
Sent from my SAMSUNG-SGH-I777 using XDA Premium HD app
Will try, also didn't realize firmware needed to be in same path as Heimdall. Thanks
Scott41373 said:
Will try, also didn't realize firmware needed to be in same path as Heimdall. Thanks
Click to expand...
Click to collapse
The firmware really doesn't need to be in the same path as heimdall. When I flashed the rooted GB firmware I didn't have it in the same directory as heimdall and it flashed with no problem.
None of this worked. My phone is still in download mode, but it gave me an error when trying to flash the firmware. Hoping I am not completely hosed
As long as you can put the phone into download mode, you almost certainly can recover. I don't know all the ins and outs of using Heimdall with various linux distributions. You would have to talk to the developer or find a support board for Heimdall. Maybe you need to make arrangements to get access to a windows computer so that you can use odin to flash back to stock.
Scott41373 said:
None of this worked. My phone is still in download mode, but it gave me an error when trying to flash the firmware. Hoping I am not completely hosed
Click to expand...
Click to collapse
This is my be the problem "ATTENTION: Heimdall 1.3.2 broke compatibility for several devices. In most case it is recommended that you use version 1.3.1 instead." via http://www.glassechidna.com.au/products/heimdall/ if you need help getting it set up search YouTube for "Using Heimdall command line"
To get ADB working you need to get the Android SDK android-sdk_r20.0.1-linux.tgz http://developer.android.com/sdk/index.html if you need help getting it set up search YouTube for "Setting up Android SDK Ubuntu 12.4"
I'm pretty good with computers even though I don't really code (I do pretty much everything but that) yet I've had nothing but trouble trying to flash CWM 6.0.1.9 to a GT-I9300 version of SGS3.
Here's a brief list of the various approaches I've tried, as a result of my own intuition and following the advice given to people in similar situations across this forum and dozens of others. I might not have achieved my goal yet, but I assure you I'm persistent and thorough!
I've tried four different PCs at this point, three running Windows 7 (one desktop, one laptop, one nettop - all 32-bit) and one running Windows XP.
I've tried installing Kies, then removing Kies and just installing standalone "SAMSUNG_USB_Driver_for_Mobile_Phones".
I've tried various USB ports on all the systems
I've tried various ways of plugging in the phone (you know, before/after it's in download mode), making sure there are no other devices in the USB ports, restarting before loading Odin, making sure Odin is run as Administrator, making sure Odin is running before/after the phone is plugged in, keeping the phone plugged in via USB with the battery out then putting the battery in and booting to download mode etc etc.
I've tried about five different versions of Odin at this point. The phone appears in all of them - sometimes the COM port is yellow, sometimes it's blue. Bit confusing but I've given to understand the colour differs depending on the Odin version.
Suffices to say I've been as thorough as I can think to be. But in all cases, the "GT-I9300_ClockworkMod-Recovery-Touch-6.0.1.9.tar" cannot be flashed to the phone... it just appears to start and then stalls, eventually failing when it's left long enough, with the word RECOVERY in a white box at the top of Odin but the file never getting sent to the phone, it seems. I have similar problems trying all the various different things when trying to flash an older version of CWM to a Galaxy Ace, except this time it gets stuck at the SetupConnection part and eventually fails. It's very frustrating!
Honestly I don't know what else I can try. I'm really hoping for as many suggestions as possible, because unless I can get CWM installed on the S III there's no way I can back up the stock version of Jellybean via Nandroid, install Cyanogenmod 10.1 and finally enjoy the benefits of a fully rooted phone.
Thanks in advance to anyone who throws out an idea that makes me look at this in a different way and helps me solve the problem.
Have you got Kies installed? If so make sure it is disabled I'm systray, also run Odin as administrator
slaphead20 said:
Have you got Kies installed? If so make sure it is disabled I'm systray
Click to expand...
Click to collapse
I did have Kies installed, but then ditched it on all four PCs and just used the standalone drivers as mentioned, so I'm not having to worry about disabling Kies from systray or killing it completely via Task Manager,
As I understand it from reading lots of other threads across various forums, the drivers are all you really need Kies for. Unless there's something else it does I'm not aware of... as I say I'm trying every option I can think of, every combination of possibilities to get this thing done.
slaphead20 said:
also run Odin as administrator
Click to expand...
Click to collapse
As I say, whether I run Odin as Admin or not doesn't appear to make a difference, sadly. I will say that all four Windows PCs I mentioned are logged on as the master Admin account and I have all the "nag screens" of Windows disable ("Open File - Security Warning" for example) too.
Thanks for the reply.
Try it with a newer version of ClockwordMod Recovery. That may help.
m0cha5hake said:
Try it with a newer version of ClockwordMod Recovery. That may help.
Click to expand...
Click to collapse
I'm tempted to try this when I get the chance, but the thing is when I open the TAR file under the PDA column in Odin and try to flash the S III it correctly identifies the "recovery.img" file inside, it just never seems to send it to the phone even though USB Debugging is enabled before booting into download mode. I'd guess another version (older or newer) would have the same problem?
Using Samsung USB cable ???
jje
JJEgan said:
Using Samsung USB cable ???
jje
Click to expand...
Click to collapse
Yep, official Samsung USB cables that came with the phones (Galax yS III/Galaxy Ace).
I wouldn't want to state the obvious, but have you tried flashing a different file?
The fault could be with the file, not with Odin/Windows/Phone
And as far as Kies goes, I know from experience that if you uninstall it, it still leaves bits of itself around so still worth checking in Task Manager that there are no parts still running in the background. As we know, Odin and Kies don't get along.
Something that springs to mind - what version of Android are you using? 4.0.x, 4.1.x, pre 4.x?
Still no joy trying to flash the S III via Odin on Windows. To be honest it's far too much trouble for what should be a simple recovery flash so I think I'd like to do it under Ubuntu instead, I can make a Live USB stick and boot from that then install any needed files (I'm guessing Heimdall via Terminal could do it). Any tips on the easiest way to install CWM on the S III when running Ubuntu? I watched this video and I'm wondering how accurate it is...
Ubuntoo no idea very little posted suggested a Google search might bring up a how to even if for a different model .
It reads like a critical step is missing in your attempts to root via windows for some reason .
It is a 5 min job for most users .
jje
JJEgan said:
It reads like a critical step is missing in your attempts to root via windows for some reason
It is a 5 min job for most users
Click to expand...
Click to collapse
I know, and I've been thorough, that's why I'm so confused I can't seem to do something relatively easy. Odin just hangs and never sends the recovery.img from the TAR file to the phone... it looks like it goes to start with the RECOVERY box above the S III's ID:COM port and then never flashes. It's so odd.
Are you rooted?
slaphead20 said:
Are you rooted?
Click to expand...
Click to collapse
No that's the thing - I don't want to root until I can do a full backup of the original Jelly Bean with CWM - getting CWM on there is basically the first hurdle. But at this point I suppose it might be a good idea to compromise, just to get it done. Not sure really. Don't have enough experience rooting phones to know for sure.
Not sure but I think you need root access to install CWM recovery
m0cha5hake said:
Not sure but I think you need root access to install CWM recovery
Click to expand...
Click to collapse
With the S III you might be right, however I couldn't install CWM for the Galaxy Ace using different Odin versions like 3.04 and 3.07 either, and that phone is already rooted with CM 7.2 and already has an older version of CWM on it. Which leads me to believe that something is amiss with Odin and Windows, seeing as I've tried it on four different Windows machines (3 WIndows 7, 1 Windows XP). It's baffling and frustrating.
If the Ace is already rooted just flash a newer version of CWM in recovery
m0cha5hake said:
If the Ace is already rooted just flash a newer version of CWM in recovery
Click to expand...
Click to collapse
I did. I was just making the point that even on an already rooted/CWM enabled phone a new version of CWM was not able to be flashed across via Odin.
m0cha5hake said:
Not sure but I think you need root access to install CWM recovery
Click to expand...
Click to collapse
Yes you need to be rooted to install cmw
Use chainfire recovery to root and install cwm recovery mate
Then you can flash touch version
Sent from my GT-I9300 using Tapatalk 2
chubby65 said:
Yes you need to be rooted to install cmw
Use chainfire recovery to root and install cwm recovery mate
Then you can flash touch version
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
I was under the impression that newer versions of Clockworkmod don't need Chainfire first, is that wrong?
I want to thank everyone who has chipped in so far - I'm learning a lot!
zekepliskin said:
I was under the impression that newer versions of Clockworkmod don't need Chainfire first, is that wrong?
I want to thank everyone who has chipped in so far - I'm learning a lot!
Click to expand...
Click to collapse
Not sure mate I've always used chainfire to root and install cwm recovery works every time for me
Tried the touch version but always reverted back due to too many problems
Sent from my GT-I9300 using Tapatalk 2
I went to bed last night and the phone worked fine, CM 10.1 nightly. Overnight it must have crashed and I woke up to find it off. I started it up and it asked for a password for encrypted storage (I don't have encrypted storage). I rebooted it again and found it stuck on the GS2 screen and left it for 10 min or so. I tried rebooting again and same action.
I then put it in download mode and it is on the screen but I am not able to see the device on my computer. Ubuntu 13.04.
fastboot devices shows nothing.
Ideas?
Do you have SGH-I777? There is no fastboot on this phone. You would have to use download mode with Odin on a windows machine, or with Heimdall on Linux. You would have to have the correct USB driver installed, but I don't know Linux or what you need there.
creepyncrawly said:
Do you have SGH-I777? There is no fastboot on this phone. You would have to use download mode with Odin on a windows machine, or with Heimdall on Linux. You would have to have the correct USB driver installed, but I don't know Linux or what you need there.
Click to expand...
Click to collapse
After Ging around I found the Heimdall for my Mac and have been trying without luck to get a kernal to install. I am running this command:
sudo ./heimdall flash --kernel zImage --no-reboot --verbose
This error:
ERROR: libusb error -7 whilst receiving packet. Retrying...
Ideas?
dcunited08 said:
After Ging around I found the Heimdall for my Mac and have been trying without luck to get a kernal to install. I am running this command:
sudo ./heimdall flash --kernel zImage --no-reboot --verbose
This error:
ERROR: libusb error -7 whilst receiving packet. Retrying...
Ideas?
Click to expand...
Click to collapse
It's a little out of my experience, since I don't use Mac, and have used Heimdall only with windows. Some have reported having issues getting Heimdall to work with some versions of Mac OS, but I couldn't tell you the specifics. You might have to search out the answers.
Or, maybe it would be easier to borrow a windows machine and use Odin which definitely has less issues.
creepyncrawly said:
It's a little out of my experience, since I don't use Mac, and have used Heimdall only with windows. Some have reported having issues getting Heimdall to work with some versions of Mac OS, but I couldn't tell you the specifics. You might have to search out the answers.
Or, maybe it would be easier to borrow a windows machine and use Odin which definitely has less issues.
Click to expand...
Click to collapse
I am using your one-click stock+root on a Win7 machine, I will let you know how it goes. It appears to be taking awhile on factoryfs.img (10 min or so).
dcunited08 said:
I am using your one-click stock+root on a Win7 machine, I will let you know how it goes. It appears to be taking awhile on factoryfs.img (10 min or so).
Click to expand...
Click to collapse
Try to use one of the USB ports in the back of your machine. I had to restore using creepy's file a few months ago and had trouble at first, was taking way too long for Odin to recognize.
Just like your problem.
Once I moved to the rear port the Odin process worked perfectly, so maybe it will for you.
One other thing - make sure you have an i777 before using the files; Creepy asked you but I don't see where you've replied to that.
Sent from the i777
SteveMurphy said:
Try to use one of the USB ports in the back of your machine. I had to restore using creepy's file a few months ago and had trouble at first, was taking way too long for Odin to recognize.
Just like your problem.
Once I moved to the rear port the Odin process worked perfectly, so maybe it will for you.
One other thing - make sure you have an i777 before using the files; Creepy asked you but I don't see where you've replied to that.
Sent from the i777
Click to expand...
Click to collapse
It is an i777. Do you have Kies installed? Does it matter? I am using a laptop so I am not sure which one is the back
On my laptop i usually use the 1st usb port on the left.
Try a different micro usb/usb cable.
Sent from my SAMSUNG-SGH-I747 using xda premium
4-2ndtwin said:
On my laptop i usually use the 1st usb port on the left.
Try a different micro usb/usb cable.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Does kies matter?
Sent from my Transformer Prime TF201 using Tapatalk 4
If using Odin, just don't have kies open at all. There have been posts by others that kies causes conflicts with odin when both are open at the same time.
Sent from my SAMSUNG-SGH-I747 using xda premium
If you still have problems, find and try a different cable.
4-2ndtwin said:
If using Odin, just don't have kies open at all. There have been posts by others that kies causes conflicts with odin when both are open at the same time.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Agree, Kies is the devil. :thumbdown:
Sent from the i777
SteveMurphy said:
Agree, Kies is the devil. :thumbdown:
Sent from the i777
Click to expand...
Click to collapse
Ok, i uninstalled Kies and reinstalled the USB drivers from Samsung's website. It still seems to stop.
U have gotta try a different micro usb/usb cable, if ya haven't already.
Sent from my SAMSUNG-SGH-I777 using xda premium
4-2ndtwin said:
U have gotta try a different micro usb/usb cable, if ya haven't already.
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
I have tried two different ones in three different usb ports on two different computers.
I tried running as administrator, compatibility mode, leaving it for hours. It is definitely seeing the phone and attempting to push it but failing without giving an error message.
Sent from my Transformer Prime TF201 using Tapatalk 4
Then it sounds like you need to try another file, for whatever reason creepy's isn't working for you.
Try Entropy's UCKH7 PDA/tar files in the stickies in the development thread. If that doesn't work I don't know what will.
Sent from the i777
I'm trying to buy a cheap smartphone for my girlfriend. Just bought a used Vibrant from eBay only to find it had an IMEI blacklisted by T-Mobile. Already had put CM 10.1 on it and she loved it so I'm pissed.
Any tips for buying a decent used smartphone for under $100? Vibrant seems like one of the best and I'm partial to Samsung. Any recommendations for the fastest Android 4.x ROM with the best battery life for the Vibrant?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I'm having a really hard time reflashing to stock. All the write-ups seem to be out of date. I tried the AIO Vibrant Toolbox 2.5 and can't get the phone to show up in Odin. Then I tried these instructions:
http://forum.xda-developers.com/showthread.php?p=18765728
What's the best version of Odin to use currently? Is there a simpler, reliable way to flash back to stock from CM?
VQ30DE said:
I'm having a really hard time reflashing to stock. All the write-ups seem to be out of date. I tried the AIO Vibrant Toolbox 2.5 and can't get the phone to show up in Odin. Then I tried these instructions:
http://forum.xda-developers.com/showthread.php?p=18765728
What's the best version of Odin to use currently? Is there a simpler, reliable way to flash back to stock from CM?
Click to expand...
Click to collapse
Are you putting the phone into download mode before connecting to Odin? You must be in download mode, I prefer Odin 1.7, every other version hangs on me for some reason. I always follow the guide below, never messed with AIO toolbox. Follow this guide to get back to stock JFD (2.1) http://forum.xda-developers.com/showthread.php?t=849028
Sent from my SGH-T959 using Tapatalk 2
iTz KeeFy said:
Are you putting the phone into download mode before connecting to Odin? You must be in download mode, I prefer Odin 1.7, every other version hangs on me for some reason. I always follow the guide below, never messed with AIO toolbox. Follow this guide to get back to stock JFD (2.1) http://forum.xda-developers.com/showthread.php?t=849028
Sent from my SGH-T959 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, had the phone in download mode and was using Odin 1.7. I have the latest Samsung drivers for WIndows installed, and when I mount the SD card the phone shows up properly. That guide you linked to was one I tried. I couldn't get the phone to show up with "adb devices" either, but that was working before I installed CM 10.1. This stuff is so finicky it's frustrating. I've wasted countless hours on three different phones over the past few years, but overall it's worth it to get a better OS.
VQ30DE said:
Yeah, had the phone in download mode and was using Odin 1.7. I have the latest Samsung drivers for WIndows installed, and when I mount the SD card the phone shows up properly. That guide you linked to was one I tried. I couldn't get the phone to show up with "adb devices" either, but that was working before I installed CM 10.1. This stuff is so finicky it's frustrating. I've wasted countless hours on three different phones over the past few years, but overall it's worth it to get a better OS.
Click to expand...
Click to collapse
I assume your running Odin with administrator privileges, if not try that. Maybe try flashing a different rom, a stable rom could fix the issue. Make sure USB debugging is checked, shouldn't affect Odin but worth a try.
Sent from my SGH-T959 using Tapatalk 2
iTz KeeFy said:
I assume your running Odin with administrator privileges, if not try that. Maybe try flashing a different rom, a stable rom could fix the issue. Make sure USB debugging is checked, shouldn't affect Odin but worth a try.
Sent from my SGH-T959 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, tried running as admin.
I just tried Heimdall One-Click, and got the error they mentioned:
Do not flash bootloaders if you see this message:
Code:
Local and device PIT files don't match and repartition wasn't specified!
This message means your partition tables do not match the firmware.
You will need to use Linux to repartition with this firmware package. Install Ubuntu. In Linux, you can copy-pasta this into the terminal to correct the repartitioning problem and then flash bootloaders. http://forum.xda-developers.com/showpost.php?p=17485056&postcount=23
Click to expand...
Click to collapse
Seriously? I don't want to install Linux to flash this phone back to stock! No way to do this from adb in Windows or from within a rooted phone? Maybe I'll just return with with CM installed; the phone is basically a wifi device only unless the seller decides to change the IMEI and resell.
VQ30DE said:
Yeah, had the phone in download mode and was using Odin 1.7. I have the latest Samsung drivers for WIndows installed, and when I mount the SD card the phone shows up properly. That guide you linked to was one I tried. I couldn't get the phone to show up with "adb devices" either, but that was working before I installed CM 10.1. This stuff is so finicky it's frustrating. I've wasted countless hours on three different phones over the past few years, but overall it's worth it to get a better OS.
Click to expand...
Click to collapse
Try re-installing the driver for the phone.
I'm not sure if they changed it in the newer versions of CM but after a certain version you actually need the drivers for the Nexus S rather than the Vibrant for ADB to work properly.
(Someone correct me if this is no longer true)
---------- Post added at 05:02 PM ---------- Previous post was at 05:00 PM ----------
firefly6240 said:
Try re-installing the driver for the phone.
I'm not sure if they changed it in the newer versions of CM but after a certain version you actually need the drivers for the Nexus S rather than the Vibrant for ADB to work properly.
(Someone correct me if this is no longer true)
Click to expand...
Click to collapse
Try here for the driver
I wanted to flash a new firmware with my macbook using heimdall but to do this i need the PIT file for this phone. does anyone have any idea where to get this file?
thanks for the help
edit :
i think i found out that you can download the pit from the device using heimdall. but when i click this i get "Failed to send data!Releasing device interface..."
usb debugging is activated. phone is in download mode and detected.
pmcee said:
i think i found out that you can download the pit from the device using heimdall. but when i click this i get "Failed to send data!Releasing device interface..."
usb debugging is activated. phone is in download mode and detected.
Click to expand...
Click to collapse
Yes, you're right - you can retrieve the pit file (i think its a kind of partition table) using heimdall from the device itself.
I had the same problem with heimdall and my (linux) PC as well, and i'm not sure whether my heimdall setup is screwed (didn't have time to try a different phone) or the protocol changed for the alpha...
edit: i tried with a different samsung phone now - that worked
It seems, heimdall doesn't play with the galaxy alpha...
Did anyone suceed in using heimdall with the alpha?
DThought said:
Yes, you're right - you can retrieve the pit file (i think its a kind of partition table) using heimdall from the device itself.
Did anyone suceed in using heimdall with the alpha?
Click to expand...
Click to collapse
Did not dare to try this yet, but you can install USB2 functionality on VirtualBox, and you can download a Windows virtual machine from modern.ie.
You can give VirtualBox hardware access.
This way you can use odin if you are on Linux.
Or not, like I said, didn't dare try this yet. What if something breaks your phone? Just a thought. Try at own risk.
Redsandro said:
Did not dare to try this yet, but you can install USB2 functionality on VirtualBox, and you can download a Windows virtual machine from modern.ie.
You can give VirtualBox hardware access.
This way you can use odin if you are on Linux.
Or not, like I said, didn't dare try this yet. What if something breaks your phone? Just a thought. Try at own risk.
Click to expand...
Click to collapse
I don't see a reason for Odin if you simply can do:
Code:
heimdall download-pit --out slte.pit
heimdall flash --BOOT boot.img --pit slte.pit
Me neither. But if the Alpha does not work with Heimdall, at least for some of us, there's a quite compelling reason to use Odin.
Redsandro said:
Me neither. But if the Alpha does not work with Heimdall, at least for some of us, there's a quite compelling reason to use Odin.
Click to expand...
Click to collapse
I've compiled the latest version available in git and it works just fine ...