Related
Let's see....Where do I start...
I've tried the Mac route....No luck in any successful root using Mac OS X. With that being said, I have done the following.
I have virtually booted my Mac OS X to simultaneously boot into Windows XP SP3 Home Edition using VMWare Fusion Professional Version 5.0.3 (1040386).
I went to this link here ( after deleting all Samsung drivers from previous tries and restarted windows ) and installed the driver on the Windows XP Virtual Machine.
SAMSUNG_USB_Driver_for_Mobile_Phones.zip (25.32MB)
I then went and downloaded two versions of Odin. Version 1.87 and Version 3.07.
I also downloaded Heimdall Suite V 1.4.0
I essentially followed the steps in this Youtube video by qbking77.
How to Root the Samsung Epic 4G on FC09 - Latest
With everything said and done, my phone isn't recognized in Odin or Heimdall. However, it's recognized in normal mode. It obviously doesn't root like that.
I put my phone in download mode, plug it in. Let it sit for at least 5 minutes even though it technically should be less than a minute for the USB detection to come up. It doesn't detect anything at all.
I've used 3 other cables.
I've double checked the settings with VMware Fusion for the USB Configuration. Essentially, when I have XP running, anything that is plugged in via USB will automatically connect to XP rather than OS X.
Any help on this would be great! Thanks in advance.
Edit
Edit
To my knowledge, heimdall was made to do the same thing as odin, but on Mac OSX and Linux. Try dual booting?
Sent from my SPH-D700 using Tapatalk 2
I have used a windows vm and throught vmware rooted my epic. I lack the mac and virtualizing a mac to virtualize a winblows box is too much fun for this lad.
Sent from my SPH-D700 using xda app-developers app
Djinn23 said:
I have used a windows vm and throught vmware rooted my epic. I lack the mac and virtualizing a mac to virtualize a winblows box is too much fun for this lad.
Click to expand...
Click to collapse
I'm not quite sure what you mean by this.
DarkXShadowX21 said:
I'm not quite sure what you mean by this.
Click to expand...
Click to collapse
I'm not sure what he means either, but maybe Heimdall didn't work because I think Heimdall and Odin files are packaged slightly differently.
Have you followed the instructions in post #2 in this thread?
The Windows issue may be the USB Driver. When I updated Windows version, my old driver failed to COM link with my phone in ODIN while I was still able to read and write to USB as well as gain adb access. I searched and found another poster stating the latest driver from Samsung fixed it. Worked for me as well. Try the link below.
http://downloadcenter.samsung.com/c...ng_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
Disclaimer: Samsung, nor I, assume no responsibility; use at own risk... usual TOS.
Here, in case anyone has trouble finding the cwm-5.0.2.7-epic4g.tar (for ODIN) thanks to kennyglass123
Sent from my SPH-D700 using xda app-developers app
samep said:
The Windows issue may be the USB Driver. When I updated Windows version, my old driver failed to COM link with my phone in ODIN while I was still able to read and write to USB as well as gain adb access. I searched and found another poster stating the latest driver from Samsung fixed it. Worked for me as well. Try the link below.
http://downloadcenter.samsung.com/c...ng_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
Disclaimer: Samsung, nor I, assume no responsibility; use at own risk... usual TOS.
Here, in case anyone has trouble finding the cwm-5.0.2.7-epic4g.tar (for ODIN) thanks to kennyglass123
Sent from my SPH-D700 using xda app-developers app
Click to expand...
Click to collapse
Thank you for some insight on this. I have switched out my Windows XP for Windows 7 Ultimate ( I've actually read a few people who used this on a virtual machine and it worked perfectly for them ) . I turned on the automatic updates and everything was updated. Windows 7 is working perfectly. The problem is still occurring though. I have used every version of Odin from 1.83 to 3.09. I put my SPH-D700 into download mode and if I configure vmware to "ask" for what to use when I plug it in in the USB menu, I've managed to get as far as the window popping up to allow me to select windows. I made it pop up by booting into download mode without the battery in and putting in after I put it into download mode. With that being said, nothing shows up in Odin still. I have used several drivers for this device. Here's the list of drivers I used:
Samsung USB Driver for Mobile Phones 1.3.8
Samsung USB Driver for Mobile Phones v1.5.14.0
Samsung USB Driver for Mobile Phones v1.5.27.0
SAMSUNG USB Driver for Mobile Phones ( No Version, default I believe )
Samsung Kies ( It downloads the default driver automatically )
I've also was trying to use this tar file:
SPH D700 FC09 8Gb REL.tar.md5
I have installed, uninstalled, and rebooted every time I did this to ensure that drivers would't conflict.
I even brought my phone to my neighbors house to use his XP machine. I brought the software with me to do this. I also had to update his USB drivers because of the yellow exclamation mark in the device manager menu. I did that and was able to fix his USB driver. It still didn't recognize my device. ( I believe it was his computer though because it's in really bad shape :/ )
I was told at one point that I could have a faulty secondary bootloader. If that's the case, is there a way to fix that myself? If that's not the case, I'm just not sure what to do at this point to root this phone. I've felt like I've exhausted all my options other than to find someone who has a decent windows machine and try with that.
I have a Mac OS X 10.8.4 and tried using Heimdall. That didn't work at all. From my understanding, Heimdall is used to root? Flash devices? Both? Regardless, it didn't work when I tried using it on Mac. Hence why I am using VMWare Fusion Pro ( The latest version before the newest 6 that just came out ) with Windows 7 Ultimate.
If there is anything that I am missing, anything at all that I could successfully root this phone with the methods I have been trying, some information on how to do this would be great! I've been trying to root this phone for quite awhile now with no success.
I would give the tar a try that you gave me but without Odin recognizing the device, I have no way of being able to do anything. That "COM" never shows up. Currently, I have the Samsung USB Driver for Mobile Phones v1.5.14.0 driver installed because that is the exact one from the Samsung website specifically for the SPH-D700.
jeffreyjicha said:
To my knowledge, heimdall was made to do the same thing as odin, but on Mac OSX and Linux. Try dual booting?
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
I haven't tried boot camp with windows yet. I used to have a dual boot set up that way but I have not set that back up yet. That is one avenue I have not tried thus far. I may actually give that a go just for kicks. As for as my previous post goes, I've been just working at it through VMWare Fusion Pro which is a virtual machine for Windows.
jeffreyjicha said:
I'm not sure what he means either, but maybe Heimdall didn't work because I think Heimdall and Odin files are packaged slightly differently.
Have you followed the instructions in post #2 in this thread?
Click to expand...
Click to collapse
Thank you for the link to this specific thread. I actually have not come across that one yet. I appreciate you linking me up with it! I'll be reviewing that thread tomorrow and see if I come across something useful in it.
DarkXShadowX21 said:
Thank you for some insight on this. I have switched out my Windows XP for Windows 7 Ultimate ( I've actually read a few people who used this on a virtual machine and it worked perfectly for them ) . I turned on the automatic updates and everything was updated. Windows 7 is working perfectly. The problem is still occurring though. I have used every version of Odin from 1.83 to 3.09. I put my SPH-D700 into download mode and if I configure vmware to "ask" for what to use when I plug it in in the USB menu, I've managed to get as far as the window popping up to allow me to select windows. I made it pop up by booting into download mode without the battery in and putting in after I put it into download mode. With that being said, nothing shows up in Odin still. I have used several drivers for this device. Here's the list of drivers I used:
Samsung USB Driver for Mobile Phones 1.3.8
Samsung USB Driver for Mobile Phones v1.5.14.0
Samsung USB Driver for Mobile Phones v1.5.27.0
SAMSUNG USB Driver for Mobile Phones ( No Version, default I believe )
Samsung Kies ( It downloads the default driver automatically )
I've also was trying to use this tar file:
SPH D700 FC09 8Gb REL.tar.md5
I have installed, uninstalled, and rebooted every time I did this to ensure that drivers would't conflict.
I even brought my phone to my neighbors house to use his XP machine. I brought the software with me to do this. I also had to update his USB drivers because of the yellow exclamation mark in the device manager menu. I did that and was able to fix his USB driver. It still didn't recognize my device. ( I believe it was his computer though because it's in really bad shape :/ )
I was told at one point that I could have a faulty secondary bootloader. If that's the case, is there a way to fix that myself? If that's not the case, I'm just not sure what to do at this point to root this phone. I've felt like I've exhausted all my options other than to find someone who has a decent windows machine and try with that.
I have a Mac OS X 10.8.4 and tried using Heimdall. That didn't work at all. From my understanding, Heimdall is used to root? Flash devices? Both? Regardless, it didn't work when I tried using it on Mac. Hence why I am using VMWare Fusion Pro ( The latest version before the newest 6 that just came out ) with Windows 7 Ultimate.
If there is anything that I am missing, anything at all that I could successfully root this phone with the methods I have been trying, some information on how to do this would be great! I've been trying to root this phone for quite awhile now with no success.
I would give the tar a try that you gave me but without Odin recognizing the device, I have no way of being able to do anything. That "COM" never shows up. Currently, I have the Samsung USB Driver for Mobile Phones v1.5.14.0 driver installed because that is the exact one from the Samsung website specifically for the SPH-D700.
Click to expand...
Click to collapse
I wish I took better notes when solving this... I can't help the MAC Heimdall method but if you want to get Windows working, I'd stay with that USB driver and try installing Microsoft Visual Basic Power Packs 3.0 I'm also using ODIN3 v1.85. You didn't mention the PIT Victory file; it's needed if following the un-brick method with repartition enabled.
Funny thing about newer Windows versions, they're lighter and don't include needed packages to develop.
My recall is bad; I've rooted two different phones and setup to theme apk's again and downloaded several packages and depends and can't recall which package needed the depends for Windows... but looking at my Windows setup, I can at least tell you what I installed. The Visual Basic auto-installer works with Windows to tell you what version of Visual Basic you need for your applications when you attempt an install so follow the guidance it gives if it suggests another Visual Basic Version. I know I needed java for adb and Android SDK and I had to modify Environmental Variables to allow those applications to see each other but I don't think you need all that to root. Hope that helps some; maybe someone else more savvy with Windows or Heimdall can jump in and help.
Edit: Forgot to mention that you should open a new ODIN session for each file pushed. Once ODIN is opened, hold power and 1 button on slide-out kb while plugging the USB cable in. You should see the COM added within seconds, not minutes. The battery can stay out while using USB with ODIN; the intent is to prevent a reboot after file install so you can unplug USB after it attempts to reboot (it cannot without a battery), close ODIN and re-open ODIN and enter download mode to install the cwm recovery tar. If you get that far, you don't actually have to boot that rooted tar; just install battery, three finger salute into recovery and flash a MTD custom ROM; all customs ROMs in forum should auto-convert from BML to MTD (or you can stay with the rooted stock or flash custom BML ROM... Important to remember there is no autoconvert from MTD back to BML; that's what ODIN with repartition and PIT file is for as well as recovering a semi-bricked phone). Good Luck.
If Odin still does not recognize it borrow someone's thick BlackBerry cable.
Good one; forgot about that. My Samsung cable didn't work so the wife and I swapped cables long ago. I got her HTC USB cable and it has served me well except that the outer shell has frayed at and around the connectors.
Sent from my SPH-D700 using xda app-developers app
samep said:
I wish I took better notes when solving this... I can't help the MAC Heimdall method but if you want to get Windows working, I'd stay with that USB driver and try installing Microsoft Visual Basic Power Packs 3.0 I'm also using ODIN3 v1.85. You didn't mention the PIT Victory file; it's needed if following the un-brick method with repartition enabled.
Funny thing about newer Windows versions, they're lighter and don't include needed packages to develop.
My recall is bad; I've rooted two different phones and setup to theme apk's again and downloaded several packages and depends and can't recall which package needed the depends for Windows... but looking at my Windows setup, I can at least tell you what I installed. The Visual Basic auto-installer works with Windows to tell you what version of Visual Basic you need for your applications when you attempt an install so follow the guidance it gives if it suggests another Visual Basic Version. I know I needed java for adb and Android SDK and I had to modify Environmental Variables to allow those applications to see each other but I don't think you need all that to root. Hope that helps some; maybe someone else more savvy with Windows or Heimdall can jump in and help.
Edit: Forgot to mention that you should open a new ODIN session for each file pushed. Once ODIN is opened, hold power and 1 button on slide-out kb while plugging the USB cable in. You should see the COM added within seconds, not minutes. The battery can stay out while using USB with ODIN; the intent is to prevent a reboot after file install so you can unplug USB after it attempts to reboot (it cannot without a battery), close ODIN and re-open ODIN and enter download mode to install the cwm recovery tar. If you get that far, you don't actually have to boot that rooted tar; just install battery, three finger salute into recovery and flash a MTD custom ROM; all customs ROMs in forum should auto-convert from BML to MTD (or you can stay with the rooted stock or flash custom BML ROM... Important to remember there is no autoconvert from MTD back to BML; that's what ODIN with repartition and PIT file is for as well as recovering a semi-bricked phone). Good Luck.
Click to expand...
Click to collapse
I downloaded and installed Visual Basic. I'm not quite sure what that was suppose to do honestly. It didn't seem like anything changed. I still don't have the "COM" showing up in Odin 1.85. You are right about me forgetting to mention the "PIT" file. I actually did have that. ( victory_8G_100528.pit )
I loaded that into Odin as well as the ( SPH D700 FC09 8Gb REL.tar.md5 ) into the "PDA" section of Odin. Even though the "COM" didn't show up, I tried to run in anyways, this was the message I got in the console.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also, these are the USB cables I am using. One is a short one and the one the the "B" on it is a normal length. I don't know what the "B" stands for but I don't know if that's a Blackberry one or not.
Also, will Odin still recognize the device if the MicroSD card is in? I actually never tried without taking it out.
Gotta say I agree with Kenny on the cable.
When I tried to replace my frayed cable with a "data sync" mini USB cable, it did not support adb.
Go with what you know; borrow or invest in a thick BlackBerry mini USB cable.
Can't guarantee but I think the cable is your problem.
Sent from my SPH-D700 using xda app-developers app
Blackberry USB Cable
kennyglass123 said:
If Odin still does not recognize it borrow someone's thick BlackBerry cable.
Click to expand...
Click to collapse
samep said:
Gotta say I agree with Kenny on the cable.
When I tried to replace my frayed cable with a "data sync" mini USB cable, it did not support adb.
Go with what you know; borrow or invest in a thick BlackBerry mini USB cable.
Can't guarantee but I think the cable is your problem.
Click to expand...
Click to collapse
Do one of you perhaps have any good sources for where I could get a decent inexpensive Blackberry USB Cable? I've looked up quite a few but since I'm not certain that I would make the correct purchase, perhaps one of you could point me in the right direction. I would appreciate it. Thanks
Would this be a decent one to buy?
New OEM BlackBerry Micro USB 1m Data Cable Charge & Sync 9900 9930 9800 9810
I just went ahead and purchased it. With a 30 day return policy and the price only being $1.99, it's not really that big of a deal. Lol! I suppose we just wait and see what happens when I receive this cable. Let the waiting begin...
DarkXShadowX21 said:
Do one of you perhaps have any good sources for where I could get a decent inexpensive Blackberry USB Cable? I've looked up quite a few but since I'm not certain that I would make the correct purchase, perhaps one of you could point me in the right direction. I would appreciate it. Thanks
Would this be a decent one to buy?
New OEM BlackBerry Micro USB 1m Data Cable Charge & Sync 9900 9930 9800 9810
I just went ahead and purchased it. With a 30 day return policy and the price only being $1.99, it's not really that big of a deal. Lol! I suppose we just wait and see what happens when I receive this cable. Let the waiting begin...
Click to expand...
Click to collapse
Yes! That one will definitely work. I usually buy 5 when I need them.
kennyglass123 said:
Yes! That one will definitely work. I usually buy 5 when I need them.
Click to expand...
Click to collapse
I just received the cable. It didn't work... :/
I'm uninstalling and reinstalling the Samsung USB Driver for Mobile Phones v1.5.14.0 driver. I'll try again to see what happens.
I suppose I need to diagnose this issue in order for this to work. I don't see how a Samsung Galaxy S1 Epic 4G SPH-D700 is drawing to much power in download mode though....
I even put my mac into safe mode so it would load a new set of kernals rather than the ones from the cache files. That still didn't work for 2 reasons.
1.) Heimdall Front-end doesn't recognize the device in download mode
2.) I'm not able to boot into windows with VMWare Fusion because that specific kernal isn't loaded into safe mode.
Only necessary kernals are being used in safe mode.... I'll keep updating as I go.
Update on my Windows 8 Pro USB driver issues.. but maybe old news.
@DarkXShadowX21,
I posted earlier that I had to install Microsoft Visual Basic Power Packs3. I found the note in my logs were referenced to a problem I was having with the HTC USB driver, AFIAK, I came upon a post somewhere in xda stating I needed it (exact reason or problem I had at that time not noted). So when I ran the installer, I got a pop-up stating I must first install Microsoft.NET Framework 2.0 Running that installer, I got another pop-up stating I needed Microsoft.NET Framework 3.0, instead. Both programs installed without error. Dependencies were determined by programs already installed in my system. Anyway, my PC now sees both phones correctly now. But looking at my update history, I'm getting security updates for Microsoft.NET Framework 3.5 and 4.5 (both versions).
Looking at my Windows Control Panel/Programs and Features, I have Microsoft Visual c++ 2005 Redistributable and Microsoft Visual c++ 2008 Redistributable x86 9.0.30729.4148 these show as being installed the next day but all I had in my notes following that was some developing programs I installed. The 30729 looks to be part of the Android-SDK bundle for Windows. I also have java installed for developing. IIRC, these are not requirements for ODIN; I had minimal effort getting ODIN to work on my wife's Windows7 laptop but at least for the HTC phone and drivers, Windows 8 Pro was lacking some tools. After getting the HTC USB drivers functional and rooting that phone, I only had to get the right Samsung USB driver to get ODIN COM to work. But since I did the HTC first, not sure if any of the above was needed for ODIN to see the Epic.
Good luck.
samep said:
@DarkXShadowX21,
I posted earlier that I had to install Microsoft Visual Basic Power Packs3. I found the note in my logs were referenced to a problem I was having with the HTC USB driver, AFIAK, I came upon a post somewhere in xda stating I needed it (exact reason or problem I had at that time not noted). So when I ran the installer, I got a pop-up stating I must first install Microsoft.NET Framework 2.0 Running that installer, I got another pop-up stating I needed Microsoft.NET Framework 3.0, instead. Both programs installed without error. Dependencies were determined by programs already installed in my system. Anyway, my PC now sees both phones correctly now. But looking at my update history, I'm getting security updates for Microsoft.NET Framework 3.5 and 4.5 (both versions).
Looking at my Windows Control Panel/Programs and Features, I have Microsoft Visual c++ 2005 Redistributable and Microsoft Visual c++ 2008 Redistributable x86 9.0.30729.4148 these show as being installed the next day but all I had in my notes following that was some developing programs I installed. The 30729 looks to be part of the Android-SDK bundle for Windows. I also have java installed for developing. IIRC, these are not requirements for ODIN; I had minimal effort getting ODIN to work on my wife's Windows7 laptop but at least for the HTC phone and drivers, Windows 8 Pro was lacking some tools. After getting the HTC USB drivers functional and rooting that phone, I only had to get the right Samsung USB driver to get ODIN COM to work. But since I did the HTC first, not sure if any of the above was needed for ODIN to see the Epic.
Good luck.
Click to expand...
Click to collapse
For Windows 7,
I went ahead and downloaded this
Microsoft .NET Framework 4 (Standalone Installer). I actually downloaded on top of the download you provided me with. I'm pretty sure this is ok because this is the most updated version of .NET Framework for Windows 7. After the installation, nothing happened by the way. I didn't get a pop up asking to update anything further. I have 3.0 installed and the version for Windows 7 that I provided.
As far as setting up all the additional programs for the HTC drivers, I don't really need to do that since this is a Samsung device obviously. I understand you are stating that to explain that you were able to get your Samsung device seen after installing drivers for the HTC and finding the correct driver.
As far as finding the correct driver, I suppose I need to figure out EXACTLY which driver it is that is going to allow Odin to recognize the SPH-D700 in "Download Mode".
I used the Samsung USB Driver for Mobile Phones v1.5.14.0 only because I found a source from Samsung directly that this is the correct driver for this device.
I've also read that Samsung Kies was able to install the default Samsung drivers for most Samsung devices and that also have worked for them. It didn't work for me.
After the installation of .NET Framework I went ahead and tried to plug in my device to see if Odin would recognize it.
COM Never showed up.
I left the USB cable in, removed the battery, put the battery back to to show this pop up.
Ever after I click windows. Nothing showed up in Odin....
Pretty straightforward question. I'm looking at going from a Windows laptop to a macbook and want to make sure some of the programs I use frequently work. Will Odin work via Windows on a Mac? Thanks.
Anyone? Really want to pull the trigger on this MBP, but want to ensure I can still tinker with my android devices...
i just used Odin and it would not work on my MBP with Parallels Win 7. I had to drag out my PC and then Odin worked fine
red321red321 said:
i just used Odin and it would not work on my MBP with Parallels Win 7. I had to drag out my PC and then Odin worked fine
Click to expand...
Click to collapse
How about boot camp? Do you think the issue has to do with drivers? Not familiar with Mac OS yet... My current laptop is the only windows machine I own and don't want to get rid of it in lieu of the MBP in case some of my programs don't work...
Haven't tried boot camp
Sent from my SM-P600 using XDA Premium HD app
Sent via PM, but finally realized why it wasn't posting in the forum (links)
...So posting here since someone else may need/want this at some point:
1) You'll want vmware fusion; there's a trial. You can easily install and uninstall it on a mac if you don't want to pay. Vbox and parallels won't work.
2) You'll need the Samsung USB drivers for phones exe from Samsung's website. You'll probably also want to separately get the Kies binaries (both windows bins).
3) MS offers pre-made VMs in virtualbox format (ova's); these aren't activated and expire in 30 days, but will still sorta work after that (they'll shut down after about 30-60mins after that point). Easy enough to just reimport; not sure how often you plan on using Odin. Kies itself is generally ok on a mac, but nothing else is (aside from like graphics-tab apps, and generic usb file stuff). You'll want to get Win7 vm images. These should work but if not you can google; MS doesn't make a secret of their VMs, they're made for developers to check compatibility between different versions of IE. Get all of these and then decompress, and you'll get an .ova file (links to Win7-IE10 VM archive files removed as I don't have 10 posts yet).
4) In VMware Fusion, you'll want to import the .ova file (.ova's are technically virtualbox images, but vmware will easily convert them to its own format). Once you've imported it go into the VM's settings and allocate 2gb of ram or so to the VM (I wouldn't go much below that; if you have a later mac that shouldn't be a problem; you might be able to get by on 1.5gb though I haven't tried). You'll also want to go into the vmware usb settings and make sure to be prompted when you add a device instead of just attaching it to one or the other or you'll wind up with issues, possibly, later on.
5) Boot the Win7 vm, install VMware tools, reboot, install samsung drivers, and then install Kies if you want Kies as well (Kies may also bridge some driver gaps, I can't remember; I do remember I had a bit of trouble with correct device recognition; I'll keep an eye on this thread and if you have a problem post publicly and I can message you with the proper driver set otherwise this should work afair); the problem, if I recall, was in detecting the specific USB devices/hub, if anything. DO NOT plug in your tablet until all of these drivers have been installed and you have rebooted the VM. You've been warned.
6) Boot the VM, plug the cable into the tablet, and then the other end into the Mac. If you've set up the USB prompting properly (btw make sure you set it to 2.0 not 3.0), you should get a prompt asking if you want to attach it to the Mac or Windows; choose Windows. The drivers should do there thing in a few minutes and eventually recognize the tablet. You may or may not want to reboot the VM one last time at this point before opening Odin, but at this point it should all work.
* A note: you'll probably want to enable a shared folder via VMware with the contents of anything you want to flash and the exes to flash them with; this is pretty straightforward in the VM settings. You'll want to copy/paste from that shared folder to the VM, not run from it; Odin and other stuff tends to hang if you try to run it directly from the share. I just keep everything I need or might want to use in the future on the VM and suspend it til I need it again, but you can just as easily shut it down and it'll retain all of the data, etc; just be mindful of the 30 day limit if you're using one of the precompiled VMs (as I said, they'll still work, but it can get naggy and shut itself down if not in use (or maybe if it is, but I haven't had it bomb out on me mid-flash (yet, knock wood)).
Good luck and enjoy.
not a single problem with parallels windows 8 or xp. while i flash 4.4.2 via odin i surf the web on mac safari.
supremekizzle said:
Pretty straightforward question. I'm looking at going from a Windows laptop to a macbook and want to make sure some of the programs I use frequently work. Will Odin work via Windows on a Mac? Thanks.
Click to expand...
Click to collapse
VMware should do.
It works very well on Linux.
That's interesting...
jpl69 said:
not a single problem with parallels windows 8 or xp. while i flash 4.4.2 via odin i surf the web on mac safari.
Click to expand...
Click to collapse
Mind if I ask what release of OSX and hardware you're on? I know I was having some USB recognition problems with the other two, but that was 2 point releases ago on Mavericks (on 10.9.3 now, haven't tried again). It could be a MBP thing also. I wouldn't mind using Parallels (I have a licensed copy) if it worked for this; as it stands I use parallels for OSX, vbox for *nix and android, and vmware for windows OSes for various reasons.
Macbook Pro 13.3 2012. Mavericks updated, parallels updated with latest version. Windows 8.1 work fine with odin, but i use mainly windows xp. both configure with usb 3.0 driver.
12GB ram, 512GB SSD samsung evo (this is just for show off not relevant to update our tablet) .
i used vmware sideways with parallels but find that parallels it's more faster, reliable and more crash proof.
after you connect the tablet to mac you get the option to connect to mac or virtual machine. afterwards you allways have the option to connect/disconect the usb periferic.
rsd2000 said:
VMware should do. It works very well on Linux.
Click to expand...
Click to collapse
That's what I use; until Ben Dobell can fix Heimdall for Linux for the P60X series I've just been booting into Win7 via VMWare from my Linux machine.
jpl69 said:
Macbook Pro 13.3 2012. Mavericks updated, parallels updated with latest version. Windows 8.1 work fine with odin, but i use mainly windows xp. both configure with usb 3.0 driver.
12GB ram, 512GB SSD samsung evo (this is just for show off not relevant to update our tablet) .
i used vmware sideways with parallels but find that parallels it's more faster, reliable and more crash proof.
after you connect the tablet to mac you get the option to connect to mac or virtual machine. afterwards you allways have the option to connect/disconect the usb periferic.
Click to expand...
Click to collapse
I'm on a late 2013 13.3 MBP. I think back when I was trying to debug the problem I'd read that USB 3.0 and how it's handled on the latest MB might have something to do with it, but I can't recall correctly. I should probably retry just for sh*ts and giggles; was always on the most recent Parallels, VMware, and VirtualBox. That said, I've found VMware in general to be more stable on my particular machine, and quicker to boot/suspend/unsuspend. It could very well just be my imagination or preference though, nosing its way in.
And talking about hardware is never showing off, as long as you're making good use of it. OS wars, however, is another story.
Hi,
Yesterday I have flashed a 6.0 ROM and right afterwards a supersu on my G Pad.
I guess something got messed up in the process because now I can't boot the ROM and not even boot into recovery.
I've tried to get into download mode using LG PC suite, but without success. someone has an idea how I can maybe save the tablet?
here is the error that I get :
I assume you have the V500 variant? If you go through the motions of putting it in Download mode through the hardware keys (I don't know if it's the same as on my VK810 variant), does it show up in Windows' Device Manager as "LGE..." in both the Modem and Ports section? If so, try flashing a TOT or KDZ made for your variant.
roirraW "edor" ehT said:
I assume you have the V500 variant? If you go through the motions of putting it in Download mode through the hardware keys (I don't know if it's the same as on my VK810 variant), does it show up in Windows' Device Manager as "LGE..." in both the Modem and Ports section? If so, try flashing a TOT or KDZ made for your variant.
Click to expand...
Click to collapse
I don't see it under ports.
maybe I need a driver that will match win10?
Dor-b said:
I don't see it under ports.
maybe I need a driver that will match win10?
Click to expand...
Click to collapse
What about under Modem? If it shows up under Modem then it might be worth a try flashing a KDZ with LG Flash Tool 2014.
I've never had to get a different driver package for different flavors of Windows for my LG devices. I've used the same packages on 7, 8.1 and 10 without any trouble. I don't know if things are different with non-Verizon LG devices, however, but I doubt it since LG is the one who does the driver work. I always go straight to LG's or in my case Verizon's website for the latest driver for my devices.
Are there anything listed in Device Manager as Unknown Device? If not, then it's not likely installing a different driver will produce a different result, as if Windows can't even see the device as unknown, then installing the driver won't help, but it can't hurt to try the latest driver version if you haven't already. Reboot after installing the driver and use the original USB cable and preferably with a USB 2.0 port that comes straight off your PC's motherboard (or on the back of the PC) and not through a USB hub.
roirraW "edor" ehT said:
What about under Modem? If it shows up under Modem then it might be worth a try flashing a KDZ with LG Flash Tool 2014.
I've never had to get a different driver package for different flavors of Windows for my LG devices. I've used the same packages on 7, 8.1 and 10 without any trouble. I don't know if things are different with non-Verizon LG devices, however, but I doubt it since LG is the one who does the driver work. I always go straight to LG's or in my case Verizon's website for the latest driver for my devices.
Are there anything listed in Device Manager as Unknown Device? If not, then it's not likely installing a different driver will produce a different result, as if Windows can't even see the device as unknown, then installing the driver won't help, but it can't hurt to try the latest driver version if you haven't already. Reboot after installing the driver and use the original USB cable and preferably with a USB 2.0 port that comes straight off your PC's motherboard (or on the back of the PC) and not through a USB hub.
Click to expand...
Click to collapse
It doesn't show under modem as well . I really don't know what else I can try.
I even tried to connect it on a win8.1 machine , but the tablet was not recognized as well.
Dor-b said:
It doesn't show under modem as well . I really don't know what else I can try.
I even tried to connect it on a win8.1 machine , but the tablet was not recognized as well.
Click to expand...
Click to collapse
Are you using the original USB cable that came with the device? After you install the driver, reboot the PC without the device connected, then go through the motions of putting the device in Download mode and connect the device to a USB 2.0 port (preferred over USB 3.x) that comes directly off the PC's motherboard - not through a USB Hub.
Give the PC up to 10 minutes to load the driver you had previously installed. Every time you connect a device for the first time to a different USB port, it has to load the driver again, and depending on various factors can take anywhere from 30 seconds to 10 minutes. After that amount of time if the Device Manager still isn't showing the device in the Modem and Port sections, then I don't have any idea what else to try either.
I've somehow managed to hardbrick my D855. I'm assuming that I'll have to use the shortpin method to get it working, but all the guides I've found so far use Windows, and I'm running Linux. I don't really feel like setting up Virtual Box on my crappy laptop, so can anyone help me out with doing this natively in Linux?
shockwaverider said:
I've somehow managed to hardbrick my D855. I'm assuming that I'll have to use the shortpin method to get it working, but all the guides I've found so far use Windows, and I'm running Linux. I don't really feel like setting up Virtual Box on my crappy laptop, so can anyone help me out with doing this natively in Linux?
Click to expand...
Click to collapse
As far as i know...You can't unbrick it with Linux. As you would need boarddiag tool which only comes as a windows executable.
I suggest you create some sort of On-The-Go windows installation and boot from a flash drive if u don't wanna through the whole VBox process or install Windows on ur physical machine.
mickeyasamoah said:
As far as i know...You can't unbrick it with Linux. As you would need boarddiag tool which only comes as a windows executable.
I suggest you create some sort of On-The-Go windows installation and boot from a flash drive if u don't wanna through the whole VBox process or install Windows on ur physical machine.
Click to expand...
Click to collapse
Thanks for the reply. Not sure what I'll end up doing, my laptop is on its last legs - only one working usb port and a fried keyboard. And the working usb port is usb3, and I've had bad luck installing Windows from that port in the past. There's also no dvd drive. And since I'm only interested in using the phone as a Plex receiver for my stereo anyway, there's no real rush.
Hello to all! Thank you for taking the time to read my post and questions!
While I'm quite PC savvy, I've never had the extra funds to invest in mobile devices such as tablets, but as luck would have it a buddy found a handful of old G Pad 8.3 (aka LG V510) tablets at a local dump early last year and dropped them off to me to play with. I successfully unlocked and rooted them all and was able to use the LG Flash tool to flash the proper 4.4.4 stock ROM to them, as well as using the mobile support tool (which is now defunct) at one point in mid 2021 to do updates from LG itself.
Not long after getting the tablets running I became sidetracked with other must do projects for months and these tablets languished here. Recently I pulled them back out, as I have more time to investigate uses for them at present.
The first tablet I moded allowed me to run Ubuntu and log into it from my desktop with VNC. No problems there. I can even install my mail server on it now that Linux is more exposed.
The next tablet I tried to mod I accidentally flashed the wrong firmware to... Bricked..... No power, no noise, no vibrate. All that I can see for any sort of response from the tablet is seeing Quallcomms 9008 mode in the Windows device manager, or Qualcomm, Inc. Gobi Wireless Modem (QDL mode) in Linux. Holding the power button for 15 secs will make the port reset but it doesn't change in any other way. the CPU is running as it stays warm until I disconnect the battery.
I have spent over 2 months trying to resolve this issue, using both Windows 7 & 10, as well as Linux, and so far no luck. I've downloaded MANY gigs of files. With Qfil and other similar tools, its constant sahara errors or firehose errors, despite having what appears to be the proper files for the firehose. The LG Flash tool tries to read it but then says the device is "differente", giving an F0000002 error, so I'd presume the wrong firmware flashed caused a change to the version number somewhere... So now the proper version won't flash with that tool...
On Linux, the only halfway encouraging responses I get is using a tool called EMMC_Recover. That tool on Linux has allowed me to send some partitions to the bricked device over USB, but certain partitions such as boot.bin, and a couple other needed partitions, EMMC_Recover responds back with a 256 error, which is an I/O error, so I would assume something is locked or not rooted proper any more on the bricked device after flashing the wrong firmware?
I have a good copy of a backup of one of the working tablets with stock ROM at 4.4.4, but have not been successful in getting the files all back onto the bricked device so it will boot.
I have also tried booting from an SD card, setting the card up a few diff ways as instructed online, but it made no difference. Button combinations combined with battery disconnects and reconnects while connecting the USB cable seem to make zero difference in its behavior. it's just plain dead other than the few things I could do with EMMC_Recover.
Other things I have tried included making up a 910k cable, which made no noticeable difference. Shorting the D+ to GND, no difference. Making sure the battery was fully charged on a working tablet, since it will not charged on a bricked tablet, but again no difference.
I realize that some devices have test points that need to be jumpered to flash them but where the device is already in 9008 mode I dont see the need, nor could I find any info what so ever about test points on the G Pad 8.3. The most I could find is a boot config setting in the service manual for this device, but the points are unclear in that manual and would take some time to trace out, if even possible short of removing the CPU/EMMC from the mother board.
I also read last night that while these devices can show as 9008 mode, that sometimes its not fully in that mode, but I cant confirm that myself. Does anyone know for sure?
JTAG sounds like its been an option for some bricked devices, but I dont have funds to risk on buying a box that may or may not work. The JTAG port pads are exposed on the edge of the board with no connector soldered on, but the chances of getting wires soldered onto that spot effectively and have the pads not tear away from the board are slim.
I'm also not sure what software would be used if I was to make my own JTAG device using something like a Pro-Micro ATMEL device. The JTAG hardware can be made, but I dont have the knowledge needed as to what to flash and where and how, and an extensive search really didn't answer those questions...
I'm not usually one to bother others with hardware or software issues, as I can usually work it out myself over enough time, but I seem to of run out of viable options after a couple hundred hrs of extensive reading and trial and error, so I am hoping someone here might have some other suggestions to try. Any help would be greatly appreciated.
Thanks to all for what you all do to help many people in need each and every day here!
So after making a few more attempts at various methods of de-bricking this tablet from Qualcomm 9008 mode, I've decided that I'm going to attempt to get 6 wires soldered onto the Jtag port, to see if i can program it with a stm32 "blue pill" that is flashed to be a Jtag programmer. Whether this works or not, and whether i can get the few wires soldered on the tiny pads or not, remains to be seen. I dont see any other viable way to fix this short of removing the cpu / ram stack, but I dont have a proper socket or programmer for that anyway.
I also dont have a hot air soldering tool, so putting a tiny socket on the Jtag pads is out of the question. Though I am game at some point to build such a tool. I was hoping to find attaching points away from those pads that are easier to solder to, but after probng with the meter only 1 is available at an alternate spot, the rest appear to go directly to the CPU.
AS far as the SD card boot method goes, clearly something does try to happen. I did set up a card with the full image and partitions from a working tablet, and edited the fstab and other files to reflect where the files were located, then repacked the boot and recovery loaders. I Then booted the patched boot image to a working tablet with the SD card in. It boot and ran either normal Android mode or TWRP recovery with no hesitation.
However, when I tried the same thing in the bricked tablet, it still didn't boot. It was clear that certain key combinations made a difference in how warm the processor runs, when the SD card was installed, but it ran cooler with the SD card out, so it does attempt to do something, but I have no idea what it is doing... So that method for now is a fail short of someone having another suggestion to try.
I have a question. Has anyone here on this forum succeeded or failed at Jtagging one of these tablets, or knows of anyone who has tried Jtagging one before? I really hate to put hrs into trying to get wires soldered on only to find that the Jtag port isn't enabled, or doesn't work proper unless some other step is taken, so any advice would be very welcome
Thanks again to all of you who took the time to read my initial post. I didn't expect to get so many views with such an old but very viable device, which I really would hate to throw away if it can be salvaged!! Thanks again for your time!!