Database Info

phone...!...PC (SOLVED)

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.

[Q] NAND Write Start Fail in Odin

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!

[Q] Someone plz help a n00b trying to root...

Any help or advice here would be GREATLY appreciated --
Q: Is it possible to get root on my S3? SCH-I535 running stock android 4.3 (I535VRUCNC1)
First, I am new to rooting so please refrain from ridicule... I have been online literally since this morning trying to find a way to do this, so needless to say I have searched. Tried Motochopper in OS X, and when that didn't work, went so far as to install Windows in VMware to try saferoot and CF autoroot--still no luck. From what I've read, I am I correct in understanding that this may not be possible? Bottom line: All I want is root in order to mount the internal memory to a volume for recovery of deleted files.
Thanks!

You're gonna have to ODIN back to ML1. NC1 has a Saferoot/Safestrap patch... The is thread on it. XDA search is your friend...
Sent from my SCH-I535 using XDA Premium 4 mobile app

Try this:
http://nasirtech.blogspot.com/2014/04/root-i535vrucnc1-android-43-stock.html

Thanks guys, but I've just about given up on this and am not too eager to dig my hole deeper. I'll spare the details as to why I'm doing this, but at this rate I also wonder if my files could even be recovered from internal memory after 2 days anyway.
I tried reverting to ML1 with the method here: [GUIDE Win/Linux/Mac] Debrick 4.3 with Odin or Verizon Utility + PIT [SOFT BRICK]
and had even worse luck as it ended up soft-bricking my phone into Odin/download mode loop that said "firmware upgrade encountered an issue..." Fortunately this morning I gave it one last go assuming nothing to lose and tried repartitioning with just the pit file in Odin 3.07, and that got it to reboot.
@Rushead, I have tried the method in that link to the best of my ability and haven't had any luck. It fails at writing NAND.
I wonder if the fact that I'm attempting this on my mac in a Windows XP x64 virtual machine is part of the problem. I hadn't used it in years and ran a ton of updates, but I've been getting errors to the effect of "Wlanapi.dll is missing" since installing the samsung drivers and Kies. Perhaps I just can't get the drivers to install correctly?

messier42 said:
Thanks guys, but I've just about given up on this and am not too eager to dig my hole deeper. I'll spare the details as to why I'm doing this, but at this rate I also wonder if my files could even be recovered from internal memory after 2 days anyway.
I tried reverting to ML1 with the method here: [GUIDE Win/Linux/Mac] Debrick 4.3 with Odin or Verizon Utility + PIT [SOFT BRICK]
and had even worse luck as it ended up soft-bricking my phone into Odin/download mode loop that said "firmware upgrade encountered an issue..." Fortunately this morning I gave it one last go assuming nothing to lose and tried repartitioning with just the pit file in Odin 3.07, and that got it to reboot.
@Rushead, I have tried the method in that link to the best of my ability and haven't had any luck. It fails at writing NAND.
I wonder if the fact that I'm attempting this on my mac in a Windows XP x64 virtual machine is part of the problem. I hadn't used it in years and ran a ton of updates, but I've been getting errors to the effect of "Wlanapi.dll is missing" since installing the samsung drivers and Kies. Perhaps I just can't get the drivers to install correctly?
Click to expand...
Click to collapse
Try an actual Windows machine before giving up hope bud

Rushead said:
Try this:
http://nasirtech.blogspot.com/2014/04/root-i535vrucnc1-android-43-stock.html
Click to expand...
Click to collapse
There are links to this guy all over. However, I can't get it to work and neither can anybody else as far as I can see. Don't bother.

[Q] Odin com1 port not recognizing phone

Hello all,
I have a verizon note 3 nc4. I would like to revert back to nc2 so that I may take advantage of some of the roms they have like hyperdrive. I have safestrap 3.75, have phone rooted, when I go to odin mode and use odin 3.09 which I assume to be the latest version it does not recognize my phone. Admittedly I am rather novice so the obvious is more than likely the answer.
Steps I have taken:
I have tried several USB ports on my tower, my cord does transfer data/charge fine so I do not think it's faulty.
I have tried several versions of Odin with no change.
if someone can help me I would be very grateful. As always, thank you!

deindichter said:
Hello all,
I have a verizon note 3 nc4. I would like to revert back to nc2 so that I may take advantage of some of the roms they have like hyperdrive. I have safestrap 3.75, have phone rooted, when I go to odin mode and use odin 3.09 which I assume to be the latest version it does not recognize my phone. Admittedly I am rather novice so the obvious is more than likely the answer.
Steps I have taken:
I have tried several USB ports on my tower, my cord does transfer data/charge fine so I do not think it's faulty.
I have tried several versions of Odin with no change.
if someone can help me I would be very grateful. As always, thank you!
Click to expand...
Click to collapse
Reinstall Drivers!!

pushkardua said:
Reinstall Drivers!!
Click to expand...
Click to collapse
I did attempt that. I attempted it five times to be precise. What ended up being the issue, is my cord and computer do not so easily get along, it kept failing to recognize my phone, eventually out of dumb luck odin recognized it and I was able to flash the nc2 and get hyperdrive working.
OR so I thought I needed to do. Come to find after hyperdrive was flashed I went to about phone and saw I still had nc4, now my stock will not load it just sticks on verizon screen. Hyperdrive works well enough I just don't quite understand what happened to cause these issues. Thank you for your attempt and time however.

deindichter said:
I did attempt that. I attempted it five times to be precise. What ended up being the issue, is my cord and computer do not so easily get along, it kept failing to recognize my phone, eventually out of dumb luck odin recognized it and I was able to flash the nc2 and get hyperdrive working.
OR so I thought I needed to do. Come to find after hyperdrive was flashed I went to about phone and saw I still had nc4, now my stock will not load it just sticks on verizon screen. Hyperdrive works well enough I just don't quite understand what happened to cause these issues. Thank you for your attempt and time however.
Click to expand...
Click to collapse

S8 bootloop, ODIN fails at write, finally asking for help

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