Related
I'm a newbie. More than that; I'm an English teacher. So maybe I had no business rooting my Vibrant. But I was tired of waiting for 2.2, so I figured out how to load Axura on my rooted phone. And loved it, until it started lagging.
The mistake I made was my haste in trying to install Voodoo lag fix. I mistakenly downloaded the European version (for the i9000, instead of the T959); to compound matters, I got impatient and tried to hard boot the phone when it hadn't rebooted in five minutes.
Long story short: I figured out how to use Odin (on the Boot Camp partition of my MacBook); downloaded 1.7, along with the 512 pit file and the stock kernel. Managed to get a "Pass!" from Odin after only about 15 seconds.
But when the phone reboots, it always boots into recovery mode. I get the Vibrant splash screen, then E:Can't mount /dev/block/s111 (Invalid argument).
I've spent hours looking over the forums here, as well as on other sites, and can't find a solution. The most common suggestion is to download Eugene373's Froyo that won't brick--but it has apparently been pulled from the internet.
Any suggestions? I don't think it's hopeless, because I can get to the system recovery screen (although with only four choices: reboot system now; reinstall packages; delete all user data; delete cache data).
Thanks for any help anyone can give.
froyo has been out for the vibrant for a while.
start odin
get into download mode
plug phone in(should already be in)
make sure a com port is lit up in yellow
put these files in said sections:
PIT: http://www.divshare.com/direct/12692662-720.pit
PDA: http://www.divshare.com/direct/13144348-b8e.zip
check repartition to fix your filesystems(you must have loaded the above pit to do this or it wont go right)
click start
this will take you back to JK2(what i use for stock froyo)
Thank you very much. I knew it was something simple like this. I had the correct .pit file, but I was missing the right .tar file.
Now, I'm pleased to say that I'm out of the tarpit!
(I'm assuming that JK2 is a stock ROM that I flash back to when I get my nerves back and start trying out custom ROM's again.)
Similar issue...in ODIN hangs on setupconnection
Hi All,
I have a similar problem. I am a newbie too..so sorry for the ignorance. I have spent tons of time reading and have flashed ROMS several times successfully. But something happened, and I am unsure why.
I am now stuck in Vibrant logo screen. I am able to do the three button thing to get to Android system recovery (2e) screen. I cannot get to download screen, but ODIN recognizes the phone. Here is the message listed in Odin as it seems to be stuck on Setup Connection.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Eugene_2E_JK2_Froyo.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/018> Odin v.3 engine (ID:18)..
<ID:0/018> File analysis..
<ID:0/018> SetupConnection..
My phone screen says
--Install from sdcard...
Finding update package...
Opening update package...
E:Can't open /sdcard/update.zip
(No such file or directory)
Installation aborted.
Now I know update.zip file was on there and a copy exist on external card. I have tried to run android-sdk-windows to use ADB to get to download screen but am unsuccessful- ADB is not a recognized command in cmd.
So now i have no phone :-(
Please help.
msz420 said:
Hi All,
I have a similar problem. I am a newbie too..so sorry for the ignorance. I have spent tons of time reading and have flashed ROMS several times successfully. But something happened, and I am unsure why.
I am now stuck in Vibrant logo screen. I am able to do the three button thing to get to Android system recovery (2e) screen. I cannot get to download screen, but ODIN recognizes the phone. Here is the message listed in Odin as it seems to be stuck on Setup Connection.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Eugene_2E_JK2_Froyo.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/018> Odin v.3 engine (ID:18)..
<ID:0/018> File analysis..
<ID:0/018> SetupConnection..
My phone screen says
--Install from sdcard...
Finding update package...
Opening update package...
E:Can't open /sdcard/update.zip
(No such file or directory)
Installation aborted.
Now I know update.zip file was on there and a copy exist on external card. I have tried to run android-sdk-windows to use ADB to get to download screen but am unsuccessful- ADB is not a recognized command in cmd.
So now i have no phone :-(
Please help.
Click to expand...
Click to collapse
You're probably going into Download mode wrong, or hitting the wrong combo, follow this guide:
1. Take off your phone's back cover and take out your SIM card.
2. Take out your phone's battery
3. Attach your USB cable to your phone while plugged in and have ODIN ready on screen.
5. You should have your usb plugged in WITHOUT your battery plugged in. Now hold both volume keys down, and put the battery back in while STILL HOLDING DOWN THE VOLUME KEYS!!!
6. Download mode should be on screen.
7. Load the .pit and .tar files into ODIN, DO NOT CHECK RE PARTITION!!!!
8. Please be patient, if you get stuck at cache, unplug and try again, that should fix your problem.
Remember don't select repartition unless you know what you're doing. That's for fixing your phone if you're really ****ed up, just try it without it first...
Nevermind... for now... adb is C:\android-sdk-windows\platform-tools... earlier post had it is tools. Now i have the screen i need...fingers crossed...
Vibrant Stuck in recovery loop
my phone is stuck in a recovery loop. I have tried entering into download mode but,it goes back to recovery. The message i get is
E:Missing bitmap indeterminate1
code -7
-Install from package
Finding update package
you guys rock
I just wanted to take the time to thank you for posting this. Real life saver. Thanks
I have a Samsung S3 on O2 (UK). Yesterday I got a system update notification and I downloaded and installed the update (it was quite big, about 300MB). There were no issues during the install and it restarted fine when it finished, however about an hour later the phone just restarted itself on its own (it was in my pocket) and then just kept looping the restart process over and over. I couldnt get the phone to get passed the logo screen. I tried removing the battery, sim card, etc but nothing helped. I read in a post here to try to use the "Recovery Mode" to restart the device. I did that and it worked, I was able to get the phone started again, but about half an hour later it did exactly the same thing but this time I couldn't get into recovery mode anymore! I read a few more posts on this forum and it looked like the update had soft bricked my phone. I could get the phone into download mode so I thought I would try using Odin to re-install the stock firmware. I followed the instructions on the post to the letter, downloaded the correct firmware from Samsung, installed the USB drivers for the phone but when I tried to use Odin it just said the the update failed. Now when I turn on the phone I get the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". I have read a few posts on suggested work arounds but no matter what I try Odin always just gets stuck on "Nand Start Write!!!". I have tried re-installing the USB driver, using a different cable and even a diff computer but always the same.
Can anyone help? This is really annoying. I have never tried to do a root or mess around with the phone so it seems really odd that something like this would happen following a standard update
P.S These are the instructions I followed when I tried to re-install the official firmware - http://forum.xda-developers.com/showthread.php?t=1671969
Boot to recovery factory restore then flash stock firmware via Odin .
jje
JJEgan said:
Boot to recovery factory restore then flash stock firmware via Odin .
jje
Click to expand...
Click to collapse
Its not letting me boot to recovery mode anymore. I can boot to download mode but when I try to boot to recovery mode it just keeps looping the startup screen which at the moment is the error message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
Then flash a stock ROM image through Odin
You only need to boot into download mode for odin download the relevant firmware package and odin when you connect it via usb in download mode you will notice the first com port on odin turn yellow to indicate a device is connected
Do a search for detailed instructions buddy
Sent from my GT-N7000 using xda app-developers app
ascottuk said:
You only need to boot into download mode for odin download the relevant firmware package and odin when you connect it via usb in download mode you will notice the first com port on odin turn yellow to indicate a device is connected
Do a search for detailed instructions buddy
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Hmmm. When I connect the phone it makes the sound in Windows that the phone has been connected but then in Odin the com port is blue not yellow. Does that mean that it has not detected the phone properly?
Glebun said:
Then flash a stock ROM image through Odin
Click to expand...
Click to collapse
This is the message I get in Odin when I try to flash the stock firmware:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXDLIH_I9300O2UDLI3_I9300BWDLI1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> system.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
You need a service centre with that comment Nand Start Write! .
jje
Yeah, you probably have corrupted NAND :/, take it for warranty repair, they will replace the mainboard. :thumbup:
Sent from my GT-I9300 using xda app-developers app
Hello, I have Galaxy SII, SGH-I777 w/AT&T. When i turn on the phone i get black screen that says "Samsung Galaxy SII". I can't get passed this screen. The only other thing i could do is hold up/down volume & power button that takes me to a screen where i'm giving 2 options, continue or cancel. Click cancel, i'm back at black screen. Click continue it takes me to "ODIN MODE" and says downloading. No clue what it's downloading but it's stuck at this screen now. I'm not very techy w/phones, not sure if there's a simple solution. Phone is factory OS, i never installed anything outside of what AT&T pushed through software upgrades. Please help!
When you press continue and get the screen that says downloading, your phone is in download mode, which means it is ready to receive new firmware via Odin. Since all you can get is either download mode or the black screen when you use the button combination that should take you to recovery, that means that the firmware has become corrupt in some way. The only way to fix this is to re-flash the stock firmware using Odin. Please read through some of the guides that are linked in my signature. That should give you enough basic information to flash back to stock. If you have any questions along the way, feel free to ask them here.
I followed steps in this link - step #2. http://forum.xda-developers.com/showthread.php?p=18630030#post18630030. When i got to this step "Click Start. Watch the progress bar advance in green while the message box in the lower area describes the steps. When the flash is finished, the top left larger edit box will turn green and say PASS! and your phone will automatically reboot." - instead of PASS, i got a red FAIL. Seems like i can't even get it to to flash?
ytka98 said:
I followed steps in this link - step #2. http://forum.xda-developers.com/showthread.php?p=18630030#post18630030. When i got to this step "Click Start. Watch the progress bar advance in green while the message box in the lower area describes the steps. When the flash is finished, the top left larger edit box will turn green and say PASS! and your phone will automatically reboot." - instead of PASS, i got a red FAIL. Seems like i can't even get it to to flash?
Click to expand...
Click to collapse
Since you are running stock ROM & kernel, if you've ever performed a factory reset or wipe on your phone then you may have an emmc superbrick on your hands.
Sorry, i'm not very savvy with the tech language, what does this emmc superbrick mean? Is my phone done and i should get a new one?
ytka98 said:
Sorry, i'm not very savvy with the tech language, what does this emmc superbrick mean? Is my phone done and i should get a new one?
Click to expand...
Click to collapse
What AJ Newkirk says is a possibility, but not definite. If the phone does have damage to the emmc memory, then yes, you would probably have to get a new phone. I only ever saw two reports of emmc memory damage reported here, and only one of them was even close to conclusive, so the likelihood that your phone has some other issue is quite good.
Do you know what version was currently on the phone? The latest version pushed out by AT&T is 4.0.4 (UCLL6). Also, did you ever perform a wipe data/factory reset at any time? And finally, please describe the circumstances surrounding the phone's failure to boot. We'll try to help.
Thanks this helps! I want to say i had the latest version, to be honest i don't recall but deferentially 4.something. I did a factory wipe a few months ago and then restored back up from Klies. I really don't know how/why it failed, i was charging it and texting infrequently. at some point i looked at the phone and saw the black screen. that was pretty much the end of it.
ytka98 said:
Thanks this helps! I want to say i had the latest version, to be honest i don't recall but deferentially 4.something. I did a factory wipe a few months ago and then restored back up from Klies. I really don't know how/why it failed, i was charging it and texting infrequently. at some point i looked at the phone and saw the black screen. that was pretty much the end of it.
Click to expand...
Click to collapse
If you were flashing the UCKH7 downloaded from that guide, try flashing the latest 4.0.4 firmware instead. You can get it from the download repository.
Also, after you open Odin on your desktop, enter download mode the usual way: with the phone off, hold down vol+ and vol- (but not power) while plugging in the usb cable.
Am i doing this right? i downloaded and extracted I777UCLL6_I777ATTLL6_I777UCLL6_HOME.tar.md5 then used Odin3 check PDA and ran...got a FAIL and info below:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I777UCLL6_I777ATTLL6_I777UCLL6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> Removed!!
<ID:0/006> SetupConnection..
<ID:0/006> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
ytka98 said:
Am i doing this right? i downloaded and extracted I777UCLL6_I777ATTLL6_I777UCLL6_HOME.tar.md5 then used Odin3 check PDA and ran...got a FAIL ...
Click to expand...
Click to collapse
Yes, but it appears that you may have Nand read/write corruption. (Not actual physical damage to the memory, but just corruption that needs to be reflashed.)
Here are the steps:
1) Flash kernel as PDA in Odin.
2) Flash the full stock package again as PDA in Odin.
If that is not successful then:
3) Download the Bootloader. Flash it as PDA in ODIN. Without ticking Re-Partitioning.
4) Flash kernel as PDA in Odin.
5) Flash the full stock package again as PDA in Odin.
I believe you can flash either a custom kernel or the stock kernel to clear the nand r/w corruption, but the problem is there are not many kernels packaged as tar available. I don't know whether flashing a Gingerbread kernel and then coming back with the ICS stock will clear the problem, but since the only kernel tar I know of is Gingerbread, why don't you try that first. If that doesn't work, I can package up an ICS kernel for you to use, but you'll need to be patient since I am pretty busy right now.
Download the Siyah 2.6.14 Gingerbread Kernel. From the line that says download, choose the TAR version. Flash that is step 1 and then the UCLL6 tar md5 package you used before in step 2.
Thanks so much for all the help. But at this point i can't even get past the initial black screen to and go into the "download" mode when i press up/down volume and power.
ytka98 said:
Thanks so much for all the help. But at this point i can't even get past the initial black screen to and go into the "download" mode when i press up/down volume and power.
Click to expand...
Click to collapse
Pressing all three buttons does not take you to download mode, it takes you into recovery mode. To enter download mode: (as I posted in a previous post in this thread) with the phone off, hold down vol+ and vol- (but not power) while plugging in the usb cable.
I ran SiyahKernel v2.6.14 TAR and got this response:
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
I then ran I777UCLL6_I777ATTLL6_I777UCLL6_HOME.tar.md5.7z and got this response:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I777UCLL6_I777ATTLL6_I777UCLL6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
i777 UCKH7 sbl.tar and this happens:
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Do you have the device already plugged in and in download mode when you start Odin? Try unplugging and plugging the device back in with Odin open.
Sent from my SGH-I777 using xda premium
Odin was open when i plugged the device in. I unplugged after every file I ran and plugged in again, without closing Odin.
Same boat
I am in the same boat. I will admit that i rooted my phone, and yes, selected a factory restore and now i am in this noob-predicament. Now I cant get the phone to communicate with ODIN. I have tried the jig with no avail. My phone displays:
"ODIN MODE
Product Name: SGH-I777
Custom Binary Download: YES (5 counts)
Current Binary: Custom"
When I use the Jig, the only display that changes is ODIN MODE changes to FACTORY MODE
Hoping for a cure...
Thanks for the help!!!
I had the same problem "can't open com port" until I used the original Samsung cable. I tried unsuccessfully for hours until I read that somewhere. With the right cable, it worked immediately.
Sent from my SGH-I777 using Tapatalk 2
ytka98 said:
Odin was open when i plugged the device in. I unplugged after every file I ran and plugged in again, without closing Odin.
Click to expand...
Click to collapse
To answer your earlier question, "Am I doing this right?" Look at the following complete instructions for Odin and follow as described. Attempt to flash the Siyah kernel tar (Step 1 in the previous post.)
How to use stand-alone Odin3 to flash firmware:
Follow and recheck each of the following steps. Do them in order listed, as some steps are dependent on previous steps. Instructions are for Odin3 v1.85. It should work with any version of Odin, but some details, like color of items, may be different.
1.) Open Odin on the Windows Desktop.
2.) Have the USB cable plugged into USB port on the computer, but *Not* plugged in to the phone.
3.) Shut the phone off.
4.) While holding down the vol+ & vol- keys, plug micro-usb plug into phone.
5.) In Odin, you should get the yellow box under where it says ID:COM with the text 0:[COMx], and in the Message area, <ID:0/00x> Added!! where x is some number, usually 1-8.
6.) In Odin, make sure Auto Reboot and F. Reset Time are checked and all other items are not checked.
7.) Click on the PDA button. Browse to the tar file you want to install and select it so its path appears in the text edit box next to the button.
8.) Make sure the check box next to the PDA button is checked.
9.) Click the Start button.
10.) You should see the green progress bar advancing.
Step 5) in this sequence will complete only if you have the correct drivers installed. Let us know how it goes, or which step is unable to complete.
If you get through all 10 steps and you still get the com port error, then try a different cable, or a different usb port, or even a different computer. If you have a desktop computer, you must use the usb port on the back, one that is connected directly to the motherboard.
Awesome, very detailed thank you very much, worked like a charm! i loaded "Siyah 2.6.14 Gingerbread Kernel file to PDA. Now i'm at step 10, i see green bar advanced, says "Kernel" right above it. Now i see the following message for the last 10 minutes:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> zImage
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Sign "Kernel" above green turned red and now says "Fail"
ytka98 said:
Awesome, very detailed thank you very much, worked like a charm! i loaded "Siyah 2.6.14 Gingerbread Kernel file to PDA. Now i'm at step 10, i see green bar advanced, says "Kernel" right above it. Now all the buttons on the screen are grayed out and i see the following message for the last 10 minutes:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> zImage
<ID:0/004> NAND Write Start!!
The phone still says "downloading...do not turn off target!!" . what's my next step?
Click to expand...
Click to collapse
If your problem is nand r/w corruption, you need to get a kernel to flash successfully as the first step, before you flash the complete package. The flash should complete in under 10 minutes, so it sounds like it's not going to complete. I could put the 4.0.4 stock kernel into a tar for you to try to flash to see what happens. Before I do that though, I need to find some additional information about the boot loader flash. I probably won't be able to get back to you before tomorrow.
I have a Verizon Galaxy S4 i545 that is soft bricked from a failed root. It was on NK1.
Odin fails early on regardless of which factory image I flash (mdk, mj7, nk1).
I have tried 5 cables and 5 all 5 USB ports.
The device manager shows Samsung Mobile USB CDC Composite Device, under which is Samsung Mobile USB Modem #x where x changes depending on which USB port I'm using.
Drivers installed correctly.
Odin shows connection on a COM port.
I've tried Odin v3.07 and 3.10. Same result for both.
Flashing gives:
<ID:0/012> Get PIT for mapping..
<ID:0/012> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1
Flashing with the correct PIT file gives:
<ID:0/012> Set PIT file..
<ID:0/012> DO NOT TURN OFF TARGET!!
<ID:0/012> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/012> Removed!!
<ID:0/012> Added!!
Try this package!
This one has the PIT. Please select these checkboxes in ODIN V3.10:
Auto-Reboot
Re-Partition
F. Reset Time
NAND Erase All
Phone Bootloader Update
Load all four file into matching ODIN slots.
If the device shows the firmware recovery screen, odin with that on screen, not "download mode".
Official Odin v3.10
https://drive.google.com/file/d/0B4RU_ZH5QUASNmxLX3JpejBXREE/edit?usp=docslist_api
Service Files:
https://docs.google.com/file/d/0B4RU_ZH5QUASdHE1b2Q2NXpVX0U/edit?usp=docslist_api
Sent from my SCH-I545 using Tapatalk
Thanks for the files and quick reply.
That gives me this, at the download screen:
<ID:0/012> Initialzation..
<ID:0/012> Erase...
<ID:0/012> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/012> Removed!!
<ID:0/012> Added!!
If I try to boot normally, it goes into Odin mode with a message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
Odin doesn't detect the phone at this screen or the Warning screen (vol up to continue, down to cancel).
What's next? I'm not familiar with Kies
Install kies 3, this will install the correct drivers for your device. Then connect device on the firmware screen, should fix the flashing issue.
Do NOT repair the device in kies, or else you won't be able to root anymore!
Sent from my SCH-I545 using Tapatalk
Kies 3 doesn't support the S4, it's Kies 2 apparently.
When I connect the phone, the Kies side bar hangs on "connecting..." indefinitely even though Odin will recognize the phone. This is in download mode. If I just turn it on or plug it in, it goes to the "firmware upgrade encountered an issue" screen and is not recognized at all.
The "Troubleshoot connection error" option seems useless. It does something behind the curtain and says "complete". Maybe it's fixing it, but it doesn't seem to "troubleshoot" since it won't tell me anything useful. I'm not sure that's the problem anyway because Odin does see the phone and attempt flashing. Anyway, when I run it, it warns me that "The device has not been disconnected" and prompts me to do so to continue, so obviously it recognizes the phone on some level.
Can you be more specific about connecting it but not repairing it? Kies has an "emergency firmware recovery" (won't work with device not showing up) and a "Firmware upgrade and Initialization". Are you saying I should only connect it and install drivers but not run either of those?
Kies also broke my drivers so that the phone wouldn't show anymore in Odin or the Device Manager in Windows. I had to manually reinstall drivers to fix this.
Is there an SD card unbrick image available?
I dug out my old trusty SGS2 to install CM13, the last time I used it was at the time of CM10.
I familiarized myself with the tutorials, and realized I have to re-partition the phone first, which requires TWRP. I downloaded the latest TWRP for the i9100 (3.0.2) and the Heimdall suite. Steps I took until failure:
1. Disable driver signature enforcement (I'm on W10)
2. Boot into download mode
3. Use zadig to replace the driver to libusb0
4. Use Heimdall to download the PIT file
5. Doesn't work - it gives me
Initialising connection...
Detecting device...
Claiming interface...
ERROR: Claiming interface failed!
Click to expand...
Click to collapse
Since I didn't get Heimdall to work, I thought to give Odin a try:
1. Downloaded Odin3 v3.11
2. TAR'd the TWRP IMG file
3. Tried to flash via Odin
4. Doesn't work - gives me:
<ID:0/005> Odin engine v(ID:3.1101)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> twrp-3.0.2-1-i9100.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
Click to expand...
Click to collapse
My laptop only has USB3 ports, I tried all of them. The cable is fine, I tried another good one which also didn't change anything. I'm not sure if I miss some crucial step or doing something wrong, as I haven't touched the device in years and am not very familiar with flashing it. I'm just looking for the 'easiest' way to get to CM13.
Appreciate any help!
Hi,
To re-partition try either this guide if you want to flash a pit-file with odin. Note you will also need to flash a kernel in .tar format to give you a working recovery.
OR try this tool to re-partition with recovery and to save your data(if you want to)
Basically the two steps you need to do are -
1. Re-partition (1GB is a good size) This doesn't require any particular recovery unless you use Lanchons re-pit tool
2. Make sure you have a recovery capable of flashing CM13(CWM 6.0.4.5+ or TWRP 2.7+) If you use open gapps, you will need to use TWRP
Once you are ready to flash CM13, make sure you flash a isorec recovery straight after. This only needs to be done once.
I had the error ERROR: Claiming interface failed! too. Then I tried different cables/USB port combinations and now I'm not getting that error anymore.
However I'm getting ERROR: Failed to access device. libusb error: -12 now
Tried with Heimdall, followed this guide:
. Download HeimdallSuite & Samsung USB Drivers
. Install Samsung USB Drivers
. Connect the phone in Download mode (Vol. Down + Home + Power)
. Go to Heimdall Suite/Drivers & open 'zadig' (Run in admin mode)
. Select 'List All Devices' under 'Options'
. Select 'Gadget Serial' & 'libusb0 (v1.2.5.0)' from the drop menu & scroll menu respectively
. Click on Install/Replace Driver
. Close 'zadig'
. Reboot again into Download mode
. Open 'heimdall-frontend'
. Select 'Utilities' tab & click on 'Detect' under 'Detect Device' option
. Make sure the 'Output' window says 'Device Detected'
. Scroll down to 'Download PIT' section & click on 'Save As...' under 'Destination File'
. Type any name under 'Name:' and select 'Save'. Do not give any filename extensions
. Click on 'Download'
Click to expand...
Click to collapse
EDIT: After a few hours of trying different things, I managed to connect with Odin3 v3.07 and I think it worked after going into device manager, then clicking on the your pc name > libusb0 somthing and right clicking, then check for updates. After that my device appeared under USB-controllers > Samsung Mobile USB CDC ......
EDIT2: I did not try to install TWRP though, instead I did this: http://forum.xda-developers.com/gal...ivatives/mod-increase-partition-size-t3011162