Database Users

half way to restore and I'm stuck, and help?

Long story short, I was running Axura2.04, and I discovered I wasn't getting voice mail notification so I went to restore the phone to a backup rom I had made of the stock version using Clockwork Premium, and after it finished installing it got stuck on the Vibrant/Samsung screen.
I was unable to boot to recovery, and I now have the phone connected to my computer via USB and I got it into what appears to be download mode (there's a yellow triangle with a droid shoveling dirt) and I'm stuck.
I am on a mac and do not have access to a PC. Any advice on how to proceed?
(ps i am relatively new to all of this, I've only been at it for a a few weeks)
Thanks

If I'm screwed someone just tell me and I'll make a trip to the t-mobile store and bite the bullet.

Sounds like you need a kernel flash for a 2.1 Rom... try using odin if you can.

dav1dM said:
If I'm screwed someone just tell me and I'll make a trip to the t-mobile store and bite the bullet.
Click to expand...
Click to collapse
You're not screwed, but only providing you can either gain access to Windows somehow (for an Odin3 reflash) or are comfortable with using a command line tool similar to Odin3 that is available for the Mac, Heimdall.. Heimdall has no GUI..
Heimdall is available here..
http://www.glassechidna.com.au/products/heimdall/
The XDA thread on it is available here..
http://forum.xda-developers.com/showthread.php?t=755265
General instructions for flashing firmware via Odin3 can be found in various links that link from the Vibrant Bible thread at the top of the dev section.
Best of luck

Isn't there a PC emulater that you can get on your Mac? If you can get that then get Odin and the right files and flash back to stock. Do a search around here for Odin.
Sent from my SGH-T959 using XDA App

Thanks for help guys, I'm meeting up with a friend tonight who has the software for a PC emulator so I'm going to try running Odin from there
I'll keep you posted

Get heimdall, it works on mac
Sent from my SGH-T959 using XDA App

I worked with Thegreat520 and we got the phone up and running again using the methods outlined in the stickie above. I tried using Heimdall, but that's too far beyond me, I can't code to save my life, took college courses for it and even that couldn't save me.
That said we did find out that using a virtual machine on a mac doesn't work, it has something to do with how the computer recognizes the device, and there is another thread here somewhere in which someone else ran into the same problem.
Thanks for not flaming me guys, the ultimate mistake happened because I was restoring a backup of a ROM and didn't clear the cache or the user data before hand. Lesson learned the hardway.

$10 paypal donation to anyone who can help me root my bell i9000m 2.1 eclair phone

BELL USERS ONLY
i9000m
2.1 eclair (stock)
how can I root this? (that z4root app doesn't work)
that super one click thing just hangs and stalls / closes on "waiting for device"
$10 to the first person who can show me how to root

Funkadelick said:
BELL USERS ONLY
i9000m
2.1 eclair (stock)
how can I root this? (that z4root app doesn't work)
that super one click thing just hangs and stalls / closes on "waiting for device"
$10 to the first person who can show me how to root
Click to expand...
Click to collapse
Why don't you follow the guide on my sig? After updating to 2.2 and flashing a kernel, you will have root
or check out this post : http://forum.xda-developers.com/showthread.php?t=742403

i can help u and make it asap if ur near me "toronto canada area" free help no charges

PaulForde said:
Why don't you follow the guide on my sig? After updating to 2.2 and flashing a kernel, you will have root
or check out this post : http://forum.xda-developers.com/showthread.php?t=742403
Click to expand...
Click to collapse
Because my computer is windows 7 x64 and it sucks with drivers etc. (i can't get keis to work if my life depended on it) and so i can only assume I will have issues "flashing" and stuff. Plus I don't wanna void my warrenty
I just want to root my i9000m 2.1 phone - that's it - it shouldn't be too hard but apparently it is hence my $10 donation to anyone who can help me

astralmaze05 said:
i can help u and make it asap if ur near me "toronto canada area" free help no charges
Click to expand...
Click to collapse
I live in Calgary - why can't you just tell me lol
do you have the update.zip ?

Funkadelick said:
Because my computer is windows 7 x64 and it sucks with drivers etc. (i can't get keis to work if my life depended on it) and so i can only assume I will have issues "flashing" and stuff. Plus I don't wanna void my warrenty
I just want to root my i9000m 2.1 phone - that's it - it shouldn't be too hard but apparently it is hence my $10 donation to anyone who can help me
Click to expand...
Click to collapse
im using win 7 x64 and its all running well i think rooting will also void ur warranty o.o

Make sure you've got the Samsung USB Drivers installed
Make sure you check allow usb dev in settings
open up super one click
connect your phone and you should be good to go...you probably don't have the mobile drivers isntalled
Heres the 64 bit drivers
http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x64.shtml

My PC is windows 7 64bit and kies works fine + windows 7 is brilliant for drivers. Try flashing using Odin with stock 2.2 can be found easily with detailed instructions, just Google it. Then try rooting from there. Wouldn't worry about warranty, your making your phone work better. Have fun.
Sent from my GT-I9000 using XDA App

try reinstalling kies then running the link I sent you, it should work fine. I'm running 64bit windows and everythings works great for me.

some instructions for rooting
if it is possible to update ur phone with kies try to find your phone version and flash the pda with odin
link:CF-root http://forum.xda-developers.com/showthread.php?t=788108
after that put the update.zip file on ur internal sd dont put it on external then im sure after u flashed it with that cf-root u can use do the 3 button trick just choose install update.zip on the menu apply it twice then u will have Clockwork mod now u can install any custom rom that u want
update.zip on attachment

omalek said:
My PC is windows 7 64bit and kies works fine + windows 7 is brilliant for drivers. Try flashing using Odin with stock 2.2 can be found easily with detailed instructions, just Google it. Then try rooting from there. Wouldn't worry about warranty, your making your phone work better. Have fun.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Here's the question I have. If I completely uninstall everything, drivers, keis, etc. and then re-install Keis - I get thet MTP failed drivers error with windows.
So then I was told to install the Windows Samsung x64 bit drivers (which I do) -- but this doesn't work either.
Then I try to "reinstall drivers" from Keis - but this does nothing either.
Any and all combinations of the above has been tested and failed -- it just sits there "trying to connect" to device - but nothing ever happens, ever.
Keis is by far the stupidest program I've ever come across - how can it possibly not work right out of the box ? I have seem hundreds of people in my case - there is no excuse for such ****ty software.

Heres the thing - I want to flash, but I want to back up all my apps and stuff first, which I can't do without ROOT
Don't get me wrong, I'm going to flash away, but not until I back up all my apps - Titanium requires ROOT which is why I am here... i need to figure out a way to root so I can back up my stuff (i have like 160 apps I don't want to re-download)
Any ideas on how to back up apps WITHOUT needing to root ?

Funkadelick said:
Heres the thing - I want to flash, but I want to back up all my apps and stuff first, which I can't do without ROOT
Don't get me wrong, I'm going to flash away, but not until I back up all my apps - Titanium requires ROOT which is why I am here... i need to figure out a way to root so I can back up my stuff (i have like 160 apps I don't want to re-download)
Any ideas on how to back up apps WITHOUT needing to root ?
Click to expand...
Click to collapse
ive sent a private message just add me on msn messenger ill try to help u and explain how o.o i hope it will work

Funkadelick said:
Heres the thing - I want to flash, but I want to back up all my apps and stuff first, which I can't do without ROOT
Don't get me wrong, I'm going to flash away, but not until I back up all my apps - Titanium requires ROOT which is why I am here... i need to figure out a way to root so I can back up my stuff (i have like 160 apps I don't want to re-download)
Any ideas on how to back up apps WITHOUT needing to root ?
Click to expand...
Click to collapse
If you flash clockwork mod recovery or a kernel that incorporates it then you can backup and restore your apps in /data from there
Hope this helps!
Sent from my GT-I9000 using XDA App

Funkadelick said:
Here's the question I have. If I completely uninstall everything, drivers, keis, etc. and then re-install Keis - I get thet MTP failed drivers error with windows.
So then I was told to install the Windows Samsung x64 bit drivers (which I do) -- but this doesn't work either.
Then I try to "reinstall drivers" from Keis - but this does nothing either.
Any and all combinations of the above has been tested and failed -- it just sits there "trying to connect" to device - but nothing ever happens, ever.
Keis is by far the stupidest program I've ever come across - how can it possibly not work right out of the box ? I have seem hundreds of people in my case - there is no excuse for such ****ty software.
Click to expand...
Click to collapse
Ok well forget using keis and just try flashing with Odin. Make sure keis isn't open when you do this though. You will have to put the phone in to download mode to flash it with Odin. Or if you don't want to mess about with Odin make sure USB debugging is off and try using the other USB setting like mass storage then it wont go through keis when you connect it. Hope this helps
Sent from my GT-I9000 using XDA App

gingerbread for sc-02b

For those with NTT sc-02b. there is a new firmware available on KIES. it is 2.3.3. baseband sc02bomke3. i updated my phone but in my opinion, it kinda suck.

Works good for me. Its much smoother than the previous rom. But, i cant figure out how to root.
Tried super one click and the gingerbreak .apk. they just run forever.
Sent from my SC-02B using XDA App

I just upgraded too.
Works good for me too (actually seems faster from the get-go and I like the new status bar design).
Unfortunately One Click Root is not working for me either.
There are some instructions on how to get it to work already on komugi.net but they are beyond my abilities.
Unfortunately XDA won't let me post direct links yet so here are the instructions copied directly from the site
In Japanese...
この画面を見た時は＼ｵﾜﾀ／と思ったのですが生きてました。
・やり方
1. アップデートのdecode済みファイルを入手する。
2. boot.bin と Sbl.bin を抜いてリパックする。カーネル単体のも作る。
3. リパックしたファイルを Odin3 で flash
4. 適当な rootカーネルを Odin3 で flash
5. リカバリモードから suコマンドを送り込み chmod 6755 su する。
（ドコモロゴで止まった場合でもadb shellから操作可能）
6. Odin3で純正カーネルをflashする。
7. 起動後に root になって Superuser.apk とか busybox とか入れる。
8. おわり。
・問題点
リカバリモードに入れない。
毎回起動時に↑画像のように画面が乱れる。
（画面が乱れるのはbootloaderを更新していない事が原因の模様）
・追記
bootloaderのアップデートを行っても特に問題無く「4.」以降の作業が行える事を確認した。
この場合問題点は全て解決される。
従来のCWMはRecoveryの仕様が変わったため使用不可。
English Translation (from Excite)...
It lives and [mashita] . though thought ＼ [owata]/when this screen is seen.
･Way
1. The file that is decode of the update is obtained.
2. With boot.bin Sbl.bin is pulled out and [ripakku]ed. The kernel unit is made.
3. The [ripakku]ed file With Odin3 Flash.
4. It is suitable The root kernel With Odin3 Flash.
5. From the recovery mode The su command is sent Chmod 6755 su is done.
(It is possible to operate it from adb shell even when stopping in the DoCoMo logo. )
6. Flash does a pure kernel with Odin3.
7. After it starts Become root Superuser.apk Busybox is put.
8. End.
･Problem
It doesn't put it in the recovery mode.
The screen falls into disorder like ↑ image when starting every time.
(It is a pattern that the screen falls into disorder caused by the thing that bootloader has not been renewed. )
･Postscript
The thing that it was possible to work especially unquestionably since "4." even if bootloader was renewed was confirmed.
In this case, all problems are solved.
Because the specification of Recovery changed, past CWM cannot be used.
Hopefully someone will figure out a simpler method soon or dumb it down a bit for me

Yeah. . . Looks rather complicated. I'm hoping for something that can be undone as well, but alas. I may have to finally study up on using Odin and all that jazz.
Sent from my SC-02B using XDA App

Chainfire's cf root method can be used to root this version with one additional step. After flashing and booting one time Chainfire's cf kernel you will have to go back to download mode and re-flash the original ke3 kernel. This will leave you with busybox, su, and superuser install in the correct places. You will not have 2e recovery or cwmod and there will be a couple of Chainfire's utilities that won't work on our kernel that you should be able to uninstall. Since none of his kernels are the same as ours I used the newest one from around post 6. I've done this a couple of times and it seems to work well. As always I take no responsibility if you brick your phone. I have attached the original ke3 kernel the tar file inside the attached zip may take a long time to flash possibly because I made it in 7zip instead of booting ti Linux to make it properly.
If your not comfortable playing with Odin and flashing phones I recommend waiting on someone to come up with a safer process.
link to CFroot thread http://forum.xda-developers.com/showthread.php?t=788108&highlight=cf+root

dejanet said:
Chainfire's cf root method can be used to root this version with one additional step. After flashing and booting one time Chainfire's cf kernel you will have to go back to download mode and re-flash the original ke3 kernel. This will leave you with busybox, su, and superuser install in the correct places. You will not have 2e recovery or cwmod and there will be a couple of Chainfire's utilities that won't work on our kernel that you should be able to uninstall. Since none of his kernels are the same as ours I used the newest one from around post 6. I've done this a couple of times and it seems to work well...
Click to expand...
Click to collapse
Thanks for the tips dejanet...
I gave it a try using CF-Root 3.7 and my SC-02B is stuck in a startup loop now... Maybe I did something wrong though? I don't need to select a PIT file in Odin, do I?
I'll give it another go with an older version of CF-Root, but if you have a specific version that you know works and any tips, that'd be great.

I used the newest one. And you for sure don't want to use a pit file or repartition. You might want to flash back to the ke3 kernel first.
Sent from my L-06C using XDA Premium App

OK! Had to reset my phone to factory once for some reason, but then I was able to flash just as you suggested and it worked fine this time. No looping.
Maybe there was something dirty in the system that was interferring? Maybe I should have tried clearing cache from recovery instead of just restoring to factory first...
Anyway:
Used Cf-root 3.7 flashed PDA with Odin once, rebooted... no baseband..
Used the stock kernel you provided (thank you very much) flashed PDA with Odin and done.
SC-02B 2.3.3 version KE3 Rooted!
(Only really sad thing about resetting to factory was that I hadn't been able to run Titanium Backup without root, so I lost all my Angry Birds progress since the 7th. (T_T) ... some lost spmode emails too, but no big deal.)

rooted 2.3.3 gps problem
My sc-02b rooted 2.3.3 but gps cannot work. I used Angrygps/GPS status/GPS test to connect the satellite, but it's all failed. I also followed the instruction to set up angrygps and gps.conf. Any one know what happen? Is it caused by rooted rom?
Thanks.

Glad you we're able to get root working. Can't think of anything in the root process that would break GPS I rarely use it with this phone sine it has never worked well for me I'll play with it tomorrow.
Sent from my L-06C using XDA Premium App

I'll test GPS too next time I go outside (not till 8pm tonight though).... my work desk isn't close enough to the window to get a GPS signal...
Never even thought to try that and see if it was working. Definately an important feature on the weekends.

dejanet said:
Chainfire's cf root method can be used to root this version with one additional step. After flashing and booting one time Chainfire's cf kernel you will have to go back to download mode and re-flash the original ke3 kernel. This will leave you with busybox, su, and superuser install in the correct places. You will not have 2e recovery or cwmod and there will be a couple of Chainfire's utilities that won't work on our kernel that you should be able to uninstall. Since none of his kernels are the same as ours I used the newest one from around post 6. I've done this a couple of times and it seems to work well. As always I take no responsibility if you brick your phone. I have attached the original ke3 kernel the tar file inside the attached zip may take a long time to flash possibly because I made it in 7zip instead of booting ti Linux to make it properly.
If your not comfortable playing with Odin and flashing phones I recommend waiting on someone to come up with a safer process.
link to CFroot thread http://forum.xda-developers.com/showthread.php?t=788108&highlight=cf+root
Click to expand...
Click to collapse
Quick and easy and works like a charm! Thanks so much!!!!!!!!!!!!

I got a chance to test the GPS and seems to be working ok for me. The one thing I did do was use gps status to reset the assist data.

Have you changed the setup of Angrygps and gps.cong(system/etc)?
Compared to 2.2.1, GPS function on 2.3.3 is useless for me.
Is there anyone know how to optimize it?
Thanks.

Stock ROM download?
Anybody have links to this stock firmware? Maybe modem and pit files too? I've been looking all over the net and on Japanese sites but the best I can find is a place to download a pre-rooted KE3.

how's the battery life compared to froyo? Can the camcorder & camera shutter sound finally be muted on the gingerbread update???........

can someone please upload the 2.3.3 firmware for SC-02B here because for some reason my Samsung Kies says "this firmware cannot be updated", so the only solution for me is flashing the firmware via ODIN

Guys, I am stuck in a bootloop after flashing latest CF-root then flashed back original kernel. How can I fix it without reflashing the whole kernel? I have tried flashing the original kernel provided by Dejanet many times but to no avail.

hello people, long time no see
I myself got the upgrade to gingerbread 2 days ago, and rooted that evil thing yesterday, using CF kernel
well, as I was expecting, that damn CWM just wiped away my mmcblk0p3 partition (fortunately I have a dump) so some original apps don't work anymore, but those were expendable
odd enough, I don't even have root access when using the shell in recovery, get some segfault at best
bad news is that I don't have the sources for Samsung's version of the kernel, so I'm not even able to make my own recovery-2e
it's very annoying to see all the good work done by the community that we're not even able to enjoy... sigh

Can you please post the sc-02b OMKF2 Kernel? I already update to the latest version. Last time I follow your selotion. Is worked well. Thanks !

want to root my new sprint samsung galaxy s4

I have a brand new sprint samsung galaxy s4 and would like to do an one click odin root but every link on this site doesnt work to download odin 1.85 they all popup with the odin and Japanese in a popup after unzipping????? Can I get a working Odin 1.85 link and the correct tar file download so I can root my phone. PLEASE I would prefer to do the same as I did with my s2 and do a CWM and use SuperSU but use odin to do my rooting. Am I missing something here with rooting my phone? Im a NOOB so I would greatly appreciate someone to give me the easiest instructions on how to root my phone where Ill have a custom recovery just like the old school odin one click for the sprint galaxy s2 epic touch. I don't wanna mess up my brand new phone but loved the rooting rights I had with my old s2 but with being able to have the benefits of the new kitkat version. Anyones expert help would be greatly appreciated!!!!

Look for CF-AutoRoot (ChainFire) http://forum.xda-developers.com/showthread.php?t=2257101
Sent from my Nexus 7 using XDA Free mobile app

hey buddy this site relies heavily on its users doing their own research, you are unlikely to find many helpful replies to this question since it is very well documented if you use the search function...or google. Or just even browse through the threads a bit. But I'll throw you a bone.
1. Download Chainfire's CFautoroot. Thanks chainfire! He conveniently includes a compatible version of odin in the zip (v3.07 if I'm not mistaken).
2. Extract the zip, and run odin.
3. Press the PDA button and select the CF-Auto-Root-jfltespr-jfltespr-sphl720.tar that was extracted from chainfire's zip.
4. Completely power off your phone. If you are unsure if it is completely off, pull the battery. Press and hold the power button and vol down until it boots into download mode. Press vol up to continue.
5. Connect your phone via usb to your computer.
6. Make sure odin recognizes your phone (one of the little boxes should read com x, where x is a number. it was com4 for me). if it doesn't you will need to install the samsung mobile phone drivers. if you plugged your phone into your computer since you've had it, you likely have these drivers installed already.
7. Press start.
8. Profit! You are now probably rooted. or your phone is bricked. ha just kidding - but please research a little next time before you ask a question
PS - this voids your warranty. also you should go click on some ads in chainfire's website.

[Q] Bricked my SGH-I337... things I have tried to so far

Been searching and trying various things to fix my bricked phone. For some background of what initially went wrong.
I had the phone rooted following these steps.
http://forum.xda-developers.com/galaxy-s4-att/general/how-to-root-i337ucufni1-t2881298
and then also had installed safetrap. I then wanted to use a custom rom http://forum.xda-developers.com/showthread.php?t=2616221 from here so I booted into safetrap recovery. (Was running 4.4.2 at this point.)
First I did backup my existing system to the sd card (maybe this will come in handy later in fixing things?)
Then I went to install and selected the three files I was suppose to use.
After i selected them, I realized I hadn't wiped things, so I left the safetrap install and went to the wipe option. I wanted to make sure I wiped everything except the SD card and here is where I probably screwed up... in the advanced wipe I selected everything to be wiped except for the sd card. It did it's thing. I then went back and selected "install" and here is where things looked different... I figured I'd be back to the option to select what to install, but instead it just went to a terminal window and it showed 'something processing' (Can't recall exactly what it said) and it was just stuck there. I left it for a quite a while (10 minutes or so) and still nothing, so I decided I'd try to start over, so I popped battery out and rebooted.
That's when all I got was the samsung splash screen.
At this time I "was" able to get into both recovery mode and download mode (Not longer can get to recovery mode... probably broke it based on stuff I did coming up.)
So then I was at the stage of googling and researching what to do. The option that seemed to come up over and over was this one http://forum.xda-developers.com/showthread.php?t=2663545 and I would repeatedly try it and everything looked to go well (saw stuff in odin installing) but at then end it just says "failed."
This led me to try the keis approach which I also so recommended. The initial attempt failed so I then tried the keis emergency firmware recovery option, but apparently something is wrong here since I don't see my device listed and have no idea what the recovery code would be.
I also had tried first installing the two kernels I had used that enabled me to first root my phone (listed in the first link NC1 stock and NI1 stock) and then using odin as described above, but same result.
Note lastly, if I now try get into recovery mode, I get the yellow message about keis failed to install (I can get the exact verbiage if it helps.)
Sorry for the lengthy explanation but figured some background might help. I can still get to download mode and use Odin so I figure there must be something I can probably do? Any ideas what to try would be greatly appreciated. Maybe I need to try and flash with a different PIT and different firmware? I'm just not sure what to try.

First, this should be in q&a, not the general forum. It gets lost here.
See this and flash the nb1 tar file in Odin. http://forum.xda-developers.com/showthread.php?p=56453100
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
First, this should be in q&a, not the general forum. It gets lost here.
See this and flash the nb1 tar file in Odin. http://forum.xda-developers.com/showthread.php?p=56453100
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for trying to help JD. I'll maybe repost in the questions forum (sorry I didn't see that.)
Note from the link above I tried both
NB1 ROOTED WITH SAFESTRAP
nb1 I337UCUFNB1_TWRootable_Full_Odin
and
NB1 STOCK (and optional upgrade to NJ4)
AP_I337UCUEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar.md5
Both of them run through their motions but end up with failed as shown here ...
https://dl.dropboxusercontent.com/u/86998/Screen%20Shot%202014-11-27%20at%2012.13.45%20AM.png
:crying:

Thread moved to Q&A
Please remember the word "bricked" is used to describe a phone that can no longer power on at all
Soft--bricked or sponged is used to describe a phone that at least can still get into download mode or LEDs light, etc.
Thanks
FNSM

rickcr said:
Thanks for trying to help JD. I'll maybe repost in the questions forum (sorry I didn't see that.)
Note from the link above I tried both
NB1 ROOTED WITH SAFESTRAP
nb1 I337UCUFNB1_TWRootable_Full_Odin
and
NB1 STOCK (and optional upgrade to NJ4)
AP_I337UCUEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar.md5
Both of them run through their motions but end up with failed as shown here ...
https://dl.dropboxusercontent.com/u/86998/Screen Shot 2014-11-27 at 12.13.45 AM.png
:crying:
Click to expand...
Click to collapse
Try a different usb cable and ports. Odin can be finicky. It looks like you're doing everything correctly
Sent from my Nexus 9 using XDA Free mobile app

Thanks!
jd1639 said:
Try a different usb cable and ports. Odin can be finicky. It looks like you're doing everything correctly
Click to expand...
Click to collapse
First off THANKS for not just giving up on me and stating the above.
After trying several USB cables it got me thinking, what else could maybe interfering with how Odin is working? When I originally rooted and flashed some kernels using Odin in my windows VM (using VMware Fusion) on Macbook Pro things had gone just fine, but I realized I might have done all of that before having upgraded to Mavericks.
So on a whim, I figured I'd try the trial version of Parallels and use my windows image with that.
Sure enough BINGO it worked!!
I would have guessed the VM as the problem sooner if my old windows vm under Fusion would have said that it couldn't connect, but what threw me off is that it DOES connect... but obviously some kind of USB protocol is getting messed up. The fact you mentioned bad cables and "finicky" prompted me to try Parallels.
Regardless I'm happy now. I'll spend the $70 and just use windows on Parallels from now on.
Thanks again!!!

rickcr said:
First off THANKS for not just giving up on me and stating the above.
After trying several USB cables it got me thinking, what else could maybe interfering with how Odin is working? When I originally rooted and flashed some kernels using Odin in my windows VM (using VMware Fusion) on Macbook Pro things had gone just fine, but I realized I might have done all of that before having upgraded to Mavericks.
So on a whim, I figured I'd try the trial version of Parallels and use my windows image with that.
Sure enough BINGO it worked!!
I would have guessed the VM as the problem sooner if my old windows vm under Fusion would have said that it couldn't connect, but what threw me off is that it DOES connect... but obviously some kind of USB protocol is getting messed up. The fact you mentioned bad cables and "finicky" prompted me to try Parallels.
Regardless I'm happy now. I'll spend the $70 and just use windows on Parallels from now on.
Thanks again!!!
Click to expand...
Click to collapse
Glad you finally got it working
Sent from my Nexus 9 using XDA Free mobile app