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.
Related
Heres the dealio- I have a Charge I want to root and put a custom rom on. I have done this before, with my Inc and my Archos tablet so I'm not a complete idiot.
I did use Odin and thought everything went fine, followed directions to install a zip from the card but the recovery menu never gave me that option. I am unable to get to the sdcard from the recovery menu. I got the option to install the update.zip but thats all. (I followed one of the many thousand "how to root your charge" threads)
Can someone tell me what happened?
Also, the first time I tried to do it, I realized I didn't have the right file, so I pulled the plug on my Charge while in Odin, also because it kept looping. Now Windows XP on that machine won't recognize the phone anymore.
Anyone have any ideas on that?
One more, I read that you need to downgrade the EE4 in order to root? Is that why recovery didn't work the first time, because I have the EE4? (I did see that info AFTER I installed the recovery)
I've been over these threads hundreds of times but I just don't have alot of time and there is alot of redundant information that makes it hard to get anywhere so I'd appreciate if someone could help me out.
willowave said:
Heres the dealio- I have a Charge I want to root and put a custom rom on. I have done this before, with my Inc and my Archos tablet so I'm not a complete idiot.
I did use Odin and thought everything went fine, followed directions to install a zip from the card but the recovery menu never gave me that option. I am unable to get to the sdcard from the recovery menu. I got the option to install the update.zip but thats all. (I followed one of the many thousand "how to root your charge" threads)
Can someone tell me what happened?
Also, the first time I tried to do it, I realized I didn't have the right file, so I pulled the plug on my Charge while in Odin, also because it kept looping. Now Windows XP on that machine won't recognize the phone anymore.
Anyone have any ideas on that?
One more, I read that you need to downgrade the EE4 in order to root? Is that why recovery didn't work the first time, because I have the EE4? (I did see that info AFTER I installed the recovery)
I've been over these threads hundreds of times but I just don't have alot of time and there is alot of redundant information that makes it hard to get anywhere so I'd appreciate if someone could help me out.
Click to expand...
Click to collapse
1) don't choose the option to select 'update.zip', that option doesn't work on the Charge... also it sounds like you were in the stock recover, you do flashing/wiping in ClockWorkMod recovery (CWM)
2) NEVER pull the cord out during an Odin flash unless its been like 30+ minutes and it looks like it froze or nothings happening, this is probably why your phone can't be recognized now (that is a good way to brick your phone and it sounds like you've got one)... now you will need to get the phone into download mode (if it still will) and flash the stock EE4 rom with the Charge PIT file (can't link from phone but these are in the How To Fix Your Phone sticky in Development) and start over
3) I don't quite understand your last question but no you don't need to be on EE4 to root and you can put CWM on any rom with Odin, EE4 at this point is mostly a 'return to stock' rom
blazing through on my 4G Droid Charge
The phone seems to be working fine, but maybe that is why I was in stock recovery mode, because it looks fine, but won't download now. Because I just tried to install a rom and I get an error. I had tried to install CWM, and thought thats what I was going to when I ended up in the stock recovery. I will try the Charge PIT file that you mentioned and see if that fixes anything, and then start over from there. If not I may be returning the phone since it's fairly new.
Thanks for your time
willowave said:
The phone seems to be working fine, but maybe that is why I was in stock recovery mode, because it looks fine, but won't download now. Because I just tried to install a rom and I get an error. I had tried to install CWM, and thought thats what I was going to when I ended up in the stock recovery. I will try the Charge PIT file that you mentioned and see if that fixes anything, and then start over from there. If not I may be returning the phone since it's fairly new.
Thanks for your time
Click to expand...
Click to collapse
when using the pit file be sure to have the repartition box checked in Odin
blazing through on my 4G Droid Charge
I don't have a PIT option on my Odin, or a repartition. It's version 4.13...is there a better version of Odin to work with and stick with? I'm working with 3 different computers here, so I know I have an Odin at home that was working but this one doesn't seem to connect. It's easier to troubleshoot whats going wrong if the proggies I'm using are at least a consistent version number. I DO know I had PIT on the Odin at home but version I'm using (at work) doesn't have it.
willowave said:
I don't have a PIT option on my Odin, or a repartition. It's version 4.13...is there a better version of Odin to work with and stick with? I'm working with 3 different computers here, so I know I have an Odin at home that was working but this one doesn't seem to connect. It's easier to troubleshoot whats going wrong if the proggies I'm using are at least a consistent version number. I DO know I had PIT on the Odin at home but version I'm using (at work) doesn't have it.
Click to expand...
Click to collapse
You need Odin3 1.82 (not just plain Odin). You can get it from http://forum.xda-developers.com/showthread.php?t=1160580
Thanks for the help guys. I got everything back to normal. Drivers and sdcard working properly now. Rooted. Now I just need to get Clockwork back on, and a different rom. Anyone have any fav roms so far? Would love some input on what everyone sees with the different radio builds.
If anyone can answer this, can we get mobile hotspot working on this? Thats a big part of why I need to root and rom this thing.
willowave said:
Thanks for the help guys. I got everything back to normal. Drivers and sdcard working properly now. Rooted. Now I just need to get Clockwork back on, and a different rom. Anyone have any fav roms so far? Would love some input on what everyone sees with the different radio builds.
If anyone can answer this, can we get mobile hotspot working on this? Thats a big part of why I need to root and rom this thing.
Click to expand...
Click to collapse
Everyone will have an opinion on ROM's and radios. My setup is in my sig. As for hotspot, android-wifi-tether works fine on all rooted roms. I've found 3.0pre12 to work the best. 3.1beta6 requires a reboot to get wifi working normally after tethering, but I don't have that issue on 3.0pre12. Be sure to immediately reboot after you install it, and then go in and set your phone type to Samsung Fascinate, and you should be good to go.
First, I tried searching for hours, and I haven't been able to find this same issue anywhere on the forums yet. If I missed it, sorry, and thanks.
I downloaded the stock 2.3.6 firmware from the Hiemdall One-touch thread here, and ran it on my phone (SGH-T959V Galaxy S 4G, and I made sure the firmware was for that specific model and not the Vibrant). It ran through the first time just fine, and then I went to do the bootloader (which I gather I probably shouldn't have done and didn't need to do maybe). Heimdall One-Click started running, then gave me this message and restarted the phone to a black screen:
Code:
Uploading PIT
PIT upload failed!
Ending session...
Rebooting device...
Now, I can pull the battery and get the phone into Download Mode just fine, and I've tried running the same firmware as well as several others (AntonX-Basic_with_a_twist, Stock KJ6 + root-One-Click, hampsterblade-Basic_MIUI_Kernel_r2_OC_UV, at least), but while they all do the first restore fine, none will load the bootloader and I get the same results every time. The phone is obviously not 100% bricked since I can get into Download Mode, but all I get is a black screen, no lights under the buttons and nothing on screen, not even the rainbow pattern or the Samsung logo. It's as if the phone isn't doing anything at all, and it doesn't change if I just pull the battery and leave it (tried for 15-20 minutes a little while ago). The only thing I can do is put it back into Download Mode, but none of the firmwares I've found have worked to restore the bootloader.
I am using a Mac with 10.8 and Java 1.7, and if it's necessary I can get access to Windows, but that will take me some time and effort, so if there's any way to resolve it using just the Mac that'd be best.
jW
When you flash the Heimdall package, does the phone boot fine?
It should have work with Mac, can you double check things?
If possible can you try re-downloading the .jar package.
And in the terminal run the .jar package (sorry I don't know OS X commands).
Thanks for the responses. It does not work after I run the Heimdall package, before or after I check the Flash bootloader checkbox. I have tried redownloading the packages several times, and I always run them with "java -jar [path to file].jar", which should be the proper command structure (and they do open and run and report success up until the point of that error, which is after the first time through but before any other steps complete in the Flash bootloader process).
Is there another method instead of the Heimdall One-Click .jar's that I can use? I have the full Heimdall installed of course, but I can't seem to find a stock PIT file for this phone that it will recognize.
jW
jondesu said:
Thanks for the responses. It does not work after I run the Heimdall package, before or after I check the Flash bootloader checkbox. I have tried redownloading the packages several times, and I always run them with "java -jar [path to file].jar", which should be the proper command structure (and they do open and run and report success up until the point of that error, which is after the first time through but before any other steps complete in the Flash bootloader process).
Is there another method instead of the Heimdall One-Click .jar's that I can use? I have the full Heimdall installed of course, but I can't seem to find a stock PIT file for this phone that it will recognize.
jW
Click to expand...
Click to collapse
As far as I know don't be desperate, that happened to me and I ended up with a bricked device.
Either boot into a free Linux distro. or use a Windows computer.
th3controller said:
As far as I know don't be desperate, that happened to me and I ended up with a bricked device.
Either boot into a free Linux distro. or use a Windows computer.
Click to expand...
Click to collapse
Thanks, I've got a Linux distro downloading and I'm looking into whether I could get a copy of Windows or borrow a PC easily.
jW
You've verified the md5 of the .jar file? I'm not sure which one you're using, please specify.
If the package file is fine and got downloaded correctly though, the next thing I'd try is a different USB cable. I have two cables, both work fine with my own phone, but I was flashing my friend's phone the other day and only one of them worked. This has happened to others too and it very likely might be the issue.
At this point though stop trying to flash the bootloaders. We're not sure whether your phone will flash successfully. You'll need to try flashing without the bootloaders and if the gingerbread package got flashed correctly you'll wind up getting the rainbow screen (assuming your phone still has the froyo bootloaders) which will be a good sign, and from there it'll be safer to flash the bootloaders.
FBis251 said:
You've verified the md5 of the .jar file? I'm not sure which one you're using, please specify.
If the package file is fine and got downloaded correctly though, the next thing I'd try is a different USB cable. I have two cables, both work fine with my own phone, but I was flashing my friend's phone the other day and only one of them worked. This has happened to others too and it very likely might be the issue.
At this point though stop trying to flash the bootloaders. We're not sure whether your phone will flash successfully. You'll need to try flashing without the bootloaders and if the gingerbread package got flashed correctly you'll wind up getting the rainbow screen (assuming your phone still has the froyo bootloaders) which will be a good sign, and from there it'll be safer to flash the bootloaders.
Click to expand...
Click to collapse
Thanks, I'll give that a try (still trying to get Linux installed here to try that as well). The first one I tried, and the one I think I'd prefer to use is the T959VUVKJ6 Stock UVKJ6 from the Heimdall One-Click thread in the forums here. I tried some of the others when that one failed. It downloaded fine, and I tried downloading it again with no change in the results.
I should clarify, btw, that I have been trying flashing it without the bootloader, but when I do that, it still sits on the black screen. The very first time I did it and one other time later, I did get the rainbow screen (and the first time, but never again, it did boot up to the stock OS and home screen), but now if I flash with or without the bootloader, I get nothing, probably because the bootloader got screwed up by the first bad flash.
My first step today will be using another cable (there's one handy, I just didn't think about it), and then I'll move on to trying Linux/Windows.
jW
Hi all,
for the last three days I've been carrying around a paper weight that looks remarkably like my Galaxy S3...
Anyway, I'm at a point where I don't know what else I could (or should) try. Today I thought I had a winner when I came across this thread: http://forum.xda-developers.com/showthread.php?t=1840030
I thought wrong. Flashing the bootchains works but then when I try flashing the root66.tar in Odin it always fails during NAND Write Start. I have seen people in the above thread with the same problem and then "never mind, I fixed it"-posts without explanations what they actually did... So, if you managed to fix it or know how to fix it, how does it work?
(I can't post in the same thread because I have less than 10 posts..)
Any input would be highly appreciated!
Thanks a lot and happy new year!
Cheers
In detail what did you do before this problem.
ThePagel said:
In detail what did you do before this problem.
Click to expand...
Click to collapse
Hm... a lot of (probably not very wise) things... Let's see...
It all started when I updated CM10.2 to a nightly release. Something went wrong, not sure what. I was talking to someone and when I checked my phone again it was just sitting there in TWPR and wouldn't boot up anymore (stuck in Cyanogen splash screen). I was still able to boot back into recovery and then tried flashing the stable CM10.2, which it didn't do. I factory reset the phone, tried flashing again, to no avail. The error message was that E: data something was missing or not accessible. From then on it's kind of a blur what I actually did, the list includes:
- trying to flash back to stock in Odin
- trying to flash new recovery in Odin
- trying to flash a pit file
- trying to install new firmware in Kies (after downloading the firmware Kies would just quit (PC), or not even download it and tell me that it's not posfible with my phone (Mac))
- trying the method described in the linked thread
At some point I wasn't even able anymore to boot into recovery (I think that was when I tried to flash a new recovery).
Thanks
I had a similar problem a while back: ODIN wouldn't flash anything and I could no longer get to recovery, etc.
I had been running Odin on Windows XP within a Virtual Machine, something that had never been a problem for me in the past. I ran it on native Windows and it flashed fine (root66.tar). If you're running ODIN inside a VM, try that.
http://forum.xda-developers.com/showthread.php?p=47886084#post47886084
-Joe
joeinternet said:
I had a similar problem a while back: ODIN wouldn't flash anything and I could no longer get to recovery, etc.
I had been running Odin on Windows XP within a Virtual Machine, something that had never been a problem for me in the past. I ran it on native Windows and it flashed fine (root66.tar). If you're running ODIN inside a VM, try that.
http://forum.xda-developers.com/showthread.php?p=47886084#post47886084
-Joe
Click to expand...
Click to collapse
Interesting. I am indeed running Windows in a VM... Need to try that later today. I'll report back later in the pm. Thanks!
IT'S BACK ALIVE! Thanks, Joe! Using a native Windows machine did the trick. I didn't use Odin, though, but did a firmware reset in Kies (was easier to do at work). Anyway, phone is up and running again. Next steps are getting CM back...
Thanks again!
Mungo Park said:
IT'S BACK ALIVE! Thanks, Joe! Using a native Windows machine did the trick. I didn't use Odin, though, but did a firmware reset in Kies (was easier to do at work). Anyway, phone is up and running again. Next steps are getting CM back...
Thanks again!
Click to expand...
Click to collapse
Be careful using kies in the future. If they start pushing 4.3 you will be screwed.
Haven't thought about that. It was still 4.1.2 and I'm back on CM10.2.
Thanks!
Hello. I need some help ASAP. My phone has been rooted (and running CyanogenMod 11) for a LONG while and lately I've been getting into network penetration. Long story short, I unlocked the bootloader of my GT-i9505G, but when it automatically rebooted, it was stuck in a recovery mood boot loop. I've tried reflashing stock Android (got failures), then CyanogenMod (some more failures), and then GApps (want some fail with that failure?). I've also tried to re-flash my firmware again using Odin 1.85, but it failed (surprise, surprise!) as well! It spit out the attached image in the end.
I'm very skilled with computers but lacking in the mobile phone department. I do know my way around them, but getting into THIS level (firmware flashing) on them is beyond me. I honestly don't know how my phone ended up like this, as I read through the guide to get an idea of what would happen and then went through the guide actually doing the work, and I followed it step by step. I REALLY need to fix this ASAP as I'm a high-school student and I take online classes. I'm sorry if this is on a really noob level, but that's exactly what I am and I'm panicking. I don't have a job and my life is on this device.
Hi, thank you for using XDA Assist. In odin DO NOT have re-partition checked. It'll probably work then. If not try different USB ports, the ones in back of the PC, and cables. Odin can be finicky. You might also try Odin 3.09, but 1.85 has always worked for me.
Good luck and don't panic!
jd1639 said:
Hi, thank you for using XDA Assist. In odin DO NOT have re-partition checked. It'll probably work then. If not try different USB ports, the ones in back of the PC, and cables. Odin can be finicky. You might also try Odin 3.09, but 1.85 has always worked for me.
Good luck and don't panic!
Click to expand...
Click to collapse
I got farther in the process this time, but it still failed. This time at the write operation. What should I do? I also tried it in Odin 3.09 but got the same results as in 1.85.
Hi, sorry for the late response. Are you still having problems? There is a forum for your device where others with your specific device may be able to help. It's located here, http://forum.xda-developers.com/galaxy-s4
So the past couple days I've been learning what I can about rooting. Finally decided to give it a shot and well I can't seem to get ODIN to work correctly. It seems to always end with abl.elf and then failing at write. I've tried Comsy and a few versions of ODIN including the latest version.
I'm currently downloading the latest firmware for my phone which is what I was updated to.
I have the Galaxy s8+ SM-G955U originally through VZW. I remember the ending of my firmware was CRE9 so I found this version off of Samsclub: G955USQU4CRE9_G955UOYN4CRE9. I downloaded some stock files for my device because I wanted to reset my bootloader version so I could root and use PARTCYBORG's rom. That's when it seemed to start looping.
I have access to download and recovery if you need that information. I also have downloaded the latest samsung drivers for Odin. I'm pretty sure if I could get it to write I could fix this issue but I've gone through a hundred threads on this forum and I'm pretty much a bit overwhelmed now. Please help
EDIT: I think I've nearly gotten it, but I'm stuck now. Odin 3.12 and Comsy 3.12 seemed to get me close. I've ran into missing Home Binary and Fail! Model Mismatch. Trying a 3.13 version of ODIN and then calling it.
One of the frustrating things about rooting for the first time is 'what are the expectations' in how things 'should' go.
Make sure you are using the most recent USB drivers. Odin, for some, will error out on the first flash attempt. It sure did when I was first learning, and it still does now, however someplace that I don't recall suggested this:
Connect with Odin, and Odin will say your phone is connected.
Setup your flash pieces.
Then flash.
Odon will fail, but this time you will leave the phone connected and re-enter download Odin.
Doing the above got me and others past the Odin errors on first flash attempts. It sure was troublesome.
Hope this works for you.
JeffDC said:
One of the frustrating things about rooting for the first time is 'what are the expectations' in how things 'should' go.
Make sure you are using the most recent USB drivers. Odin, for some, will error out on the first flash attempt. It sure did when I was first learning, and it still does now, however someplace that I don't recall suggested this:
Connect with Odin, and Odin will say your phone is connected.
Setup your flash pieces.
Then flash.
Odon will fail, but this time you will leave the phone connected and re-enter download Odin.
Doing the above got me and others past the Odin errors on first flash attempts. It sure was troublesome.
Hope this works for you.
Click to expand...
Click to collapse
hi I installed the image twrp 3.2.2.0 but by mistake on boot. how can I restore the boot? thank you