Database Info

Does anyone know how to root from 2.11.605.9 on a Mac? Auto or manual?

I've never done manual before.... so I'm completely illiterate here...

Easiest way is downgrade to 2.11.605.5 and then use the revolutionary tool
Sent from my ADR6400L using XDA App

carycooke said:
Easiest way is downgrade to 2.11.605.5 and then use the revolutionary tool
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
That tool works on Mac??? Also, not sure how to downgrade on a Mac either...

Go here http://forum.xda-developers.com/showthread.php?t=1401959
Download 2.11.605.5 file
Rename it to what it needs to be then boot to hboot downgrade
Then run the revolutionary tool
Find it on your mac on the web
If its not compatible I suggest running a emulator or downgrade and then get on a windows computer to run tool for a second
Sent from my ADR6400L using XDA App

crispy8826 said:
That tool works on Mac??? Also, not sure how to downgrade on a Mac either...
Click to expand...
Click to collapse
Downgrading has nothing to do with the computer, it's all with the phone.
As far as rooting the Thunderbolt on a Mac is concerned, you're better off just going to a Windows computer. I tried to do it on a Mac first but after around 8 hours of getting nowhere, I just used a friend's PC. If you're still trying to root and are having problems or if you can't downgrade the radio, let me know and I'll help.

ThunderNet said:
Downgrading has nothing to do with the computer, it's all with the phone.
As far as rooting the Thunderbolt on a Mac is concerned, you're better off just going to a Windows computer. I tried to do it on a Mac first but after around 8 hours of getting nowhere, I just used a friend's PC. If you're still trying to root and are having problems or if you can't downgrade the radio, let me know and I'll help.
Click to expand...
Click to collapse
I was able to root from a Windows 7 VM running in Fusion.
BTW, you don't have to downgrade to use Revolutionary to root. Here's a workaround: http://androidforums.com/thunderbolt-all-things-root/418539-thunderbolt-root-unroot-thread.html

dittman said:
I was able to root from a Windows 7 VM running in Fusion.
BTW, you don't have to downgrade to use Revolutionary to root. Here's a workaround: http://androidforums.com/thunderbolt-all-things-root/418539-thunderbolt-root-unroot-thread.html
Click to expand...
Click to collapse
Honestly, I found that just downgrading the radio was easier, but I'm not very good at using adb so that's probably why.

crispy8826 said:
I've never done manual before.... so I'm completely illiterate here...
Click to expand...
Click to collapse
I just did it this morning but on Windows 7, I did it with the same firmware that you have also, I posted up my experience in doing so right on the forums here, in the Thunderbolt Section > General (I cant post links yet lol)
Maybe it will be helpful! But as far as I know revolutionary (Which it uses) Is Windows/Linux only, try a VM!

No loss method posted on YouTube
I just went through a procedure posted on Youtube by Nat3Mil that starts with a temp root of the 605.9 that then allows you to use revolutionary to root without data loss. I am running my first titanium backup on my now rooted thunderbolt 605.9 now and I am at the green end of noob town.
Since I cant paste links you will have to try a search for temp root 605.9 might throw Nat3Mil in for good measure.
here is the written part of the guide with the links removed
//WRITTEN GUIDE
1. install htc drivers
2. plug thunderbolt into computer
3. turn on usb debugging (settings, applications, development, (check) usb debugging, okay
4. download ThunderboltTempRoot.zip from link below
5. extract package to C:\
6. click start, type cmd, press enter
7. in command promt type
cd c:\ThunderboltTempRoot (press enter)
adb devices (press enter)
(at this point you should see your device listed with serial #, if not, reinstall the driver, make sure usb debugging is on, and remove any syncing software from computer (htc sync, itunes, etc) then try again. you cant continue unless your device is listed!)
adb push fre3vo /data/local/tmp (press enter)
adb shell chmod 777 /data/local/tmp/fre3vo (press enter)
adb shell /data/local/tmp/fre3vo -debug -start F0000000 -end FFFFFFFF (press enter)
8. Your thunderbolt is now temp rooted. DO NOT REBOOT or youll have to do this over.
9. go to my rooting video linked below and follow along to get perm root without wiping data! (you can skip the driver install, its the same driver as above)
Also on the video that he did showing the revolutionary part there was this note that speaks more to the original post:
SUCCESS! Booya, you rock. I used your other video for getting S-OFF with Gingerbread 2.4.3 and software update 2.11.605.9. Everything worked as shown in the videos. To my Apple-brandishing cohorts: I was able to do this with Windows XP via Parallels on a Macbook Pro. Make sure to have Parallels attach the phone to the Virtual Machine. Also, you might want to download the files required using a Windows browser just to prevent and corruptions issues when transferring between OSes.

[ADB/FB/APX Driver] Universal Naked Driver 0.72

Universal Naked Driver 0.72
** Google Nexus 4 Added
** Google Nexus 10 Added
** Google Nexus Q Added
** Google Nexus S Added
32 & 64 Bit Windows 8 / 7 / Vista / XP - Attached to this post!
MD5: 30D25BC073F010CA01178CD6E2C5E4FA
I am happy to release my Universal Naked Driver. This is to allow ADB, Fastboot & APX interfaces to work without installing any package much less multiples packages for users with multiple devices. Yes you can just install them and uninstall right away but why bother?
I was annoyed that I couldnt use my Transformer Prime and Galaxy Nexus without having versions and packages trip over each other. My previous post for the Sensation & Galaxy Nexus was helpful so I thought I would bring to XDA the newest Android driver available from source (which they call 4.0) and make it start talking.
Warning: Uninstall any previous driver package's you may have installed and also manually remove drivers by attaching your phone and going to Windows device manager and right click the entry for your phone and select "Uninstall" on the next prompt make sure to select "Delete the driver software for this device" then hit OK and reboot before installing these drivers
Code:
Google Nexus Devices ADB & Fastboot
Samsung Devices ADB & Fastboot
Asus Devices ADB, Fastboot & APX
HTC Devices ADB & Fastboot
Code:
[B]Windows 8 Instructions[/B]
How to Disable Driver Signature Enforcement in Windows 8:
From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon).
Click ‘More PC Settings’.
Click ‘General’.
Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
Wait a bit.
Click ‘Troubleshoot’.
Click ‘Advanced Options’
Click ‘Windows Startup Settings’
Click Restart.
Enjoy!

Since ICS is on the way you will get you bootloader upgraded most likely. Then the unlock APK should follow if Asus holds up there end.
This will allows for comminucation with your tablet and phones (execpt moto for now)
Hope Asus hits you up soon with the unlock.
Cheers!

DDMS ok on my evo 3D with your driver, will test my transformer later

Nice work, was waiting for this
Although, could you tell me how did you get into fastboot mode on device? Did you use ICS, or any special bootloader, maybe a modified one?

keyra74 said:
DDMS ok on my evo 3D with your driver, will test my transformer later
Click to expand...
Click to collapse
Thanks for the feedback
fonix232 said:
Nice work, was waiting for this
Although, could you tell me how did you get into fastboot mode on device? Did you use ICS, or any special bootloader, maybe a modified one?
Click to expand...
Click to collapse
On my transformer prime I think the fastboot option only was available after the bootloader came unlocked but I could be wrong. I just do not remember seeing it before.
But after the unlock it I rebooted to the bootloader and then there was three options 1) BootToOS 2) Fastboot 3) Wipedata.
Once you select fastboot it says enabling fastboot protocols. Hope this helps but I do have a prime so it may be different.

1wayjonny said:
On my transformer prime I think the fastboot option only was available after the bootloader came unlocked but I could be wrong. I just do not remember seeing it before.
But after the unlock it I rebooted to the bootloader and then there was three options 1) BootToOS 2) Fastboot 3) Wipedata.
Once you select fastboot it says enabling fastboot protocols. Hope this helps but I do have a prime so it may be different.
Click to expand...
Click to collapse
Hmm, then please remove the Fastboot options from the original Transformer's log, as we have no access to it yet ;D Maybe with a modified u-boot, but that needs some time.

Any fix for Linux? DDMS doesn't find my TF anyomore since I upgraded to ICS

DDMS confirmed working on my ics transformer and windows here (with these drivers)
http://imgur.com/Wnmhd

gnufabio said:
Any fix for Linux? DDMS doesn't find my TF anyomore since I upgraded to ICS
Click to expand...
Click to collapse
Hey try adding these device ID's to your USB config, this should allow ADB, APX and also Fastboot if and when TF101 gets a unlocked bootloader.
USB\VID_0B05&PID_4E1F
USB\VID_0B05&PID_4E1F&MI_01
USB\VID_0B05&PID_4E3F
USB\VID_0B05&PID_4E3F&MI_02
USB\VID_0B05&PID_4DAF
USB\VID_0B05&PID_4DAF&REV_0000
USB\VID_0955&PID_7820
keyra74 said:
DDMS confirmed working on my ics transformer and windows here (with these drivers)
http://imgur.com/Wnmhd
Click to expand...
Click to collapse
Thanks for the feedback!

complete noob question. adb still confuses me and im tryin to unbrick my prime. its in the recovery bootloop, the thread im following says to do some adb commands. but "adb shell" gives me the message "adb" is not a recongnized as a command or blah blah.. so i figured its cause i don't have the drivers? well anyways.. this thread looks like it has what i need... but where\how do i install the drivers? tia.

shady503403 said:
complete noob question. adb still confuses me and im tryin to unbrick my prime. its in the recovery bootloop, the thread im following says to do some adb commands. but "adb shell" gives me the message "adb" is not a recongnized as a command or blah blah.. so i figured its cause i don't have the drivers? well anyways.. this thread looks like it has what i need... but where\how do i install the drivers? tia.
Click to expand...
Click to collapse
ya... adb not recognised means you don't have the android sdk installed. Also this is the tf101 not the prime. To install drivers hit start and type in drivers. find the one that says unknown or android 1.0 or apx or something right click and hit manually install driver

mrevankyle said:
ya... adb not recognised means you don't have the android sdk installed. Also this is the tf101 not the prime. To install drivers hit start and type in drivers. find the one that says unknown or android 1.0 or apx or something right click and hit manually install driver
Click to expand...
Click to collapse
You also get that message if you have the SDK installed but not in your path and you are trying to run the command outside of the Android\android-sdk\platform-tools\ directory where the adb command resides. I have posted a guide for installing the SDK and then installing these drivers in the Roach's Clockwork Mod Recovery thread. I was trying to help solitude65 who installed a Recovery that only reads internal apparently after he wiped the internal sdcard or didn't realize he needed a ROM on the internal sdcard. Not sure how much of it will apply to the Prime as I have a TF101 and used it to confirm the steps I posted over there.
---------- Post added at 09:43 PM ---------- Previous post was at 09:40 PM ----------
1wayjonny said:
Hey try adding these device ID's to your USB config, this should allow ADB, APX and also Fastboot if and when TF101 gets a unlocked bootloader.
USB\VID_0B05&PID_4E1F
USB\VID_0B05&PID_4E1F&MI_01
USB\VID_0B05&PID_4E3F
USB\VID_0B05&PID_4E3F&MI_02
USB\VID_0B05&PID_4DAF
USB\VID_0B05&PID_4DAF&REV_0000
USB\VID_0955&PID_7820
Thanks for the feedback!
Click to expand...
Click to collapse
Can you tell me specifically what USB config you are referring to and where to find it?

Thank you SO much! I was pulling my hair out, trying to find drivers for my TF101 in recovery mode, and I couldn't.. But these helped me immediately, and did the job!
Thank you!

I am on Windows 8 and couldn't get this installed with an error about missing the hash for the file. It of course is missing, since this isn't a signed driver.
I followed the instructions at http://dhakshinamoorthy.wordpress.com/2012/05/14/installing-an-unsigned-driver-in-windows-8-x64/ and was able to install the driver. If you're using Windows 8, you can do the same to install these unsigned drivers (or any other unsigned drivers for that matter).

Updated version, feedback helpful

1wayjonny said:
Updated version, feedback helpful
Click to expand...
Click to collapse
In order to provide feedback, I would have to have an issue...
the sarcastic joke and hidden props aside, I have a few now phones ill give it a go with sometime in the next week, amazing timing however, just reformatted my "utility" laptop... (CDMA Workshop is such a PITA to resetup after every reformat... so effing annoying! ****ty DRM and updates however are the requirements for a legit copy... sometimes I regret spending that $100)

Hammerfest said:
In order to provide feedback, I would have to have an issue...
the sarcastic joke and hidden props aside, I have a few now phones ill give it a go with sometime in the next week, amazing timing however, just reformatted my "utility" laptop... (CDMA Workshop is such a PITA to resetup after every reformat... so effing annoying! ****ty DRM and updates however are the requirements for a legit copy... sometimes I regret spending that $100)
Click to expand...
Click to collapse
No worries thanks for any help.

I having an issue trying to remove the previous version to the latest one I just sold my tf201 and today i got the nexus7 can someone help on a step by step on what to do in device manager. Now my galaxy nexus isn't recognized when i write adb devices in cmd after trying to push the latest one

perfecto
i tried rooting and playing with my TF101 when i first got it ages ago, but it was all such a pain in the ass. thank you for making this part a bit simpler.

Tried pointing Device Manager to the folder I unzipped Universal drivers to and got this.
Anyone else?

[Q] Obtaining root on generic tablet

Ok I've got a generic tablet from Walmart, the DOPO MD-740. It's running ICS 4.0.3. I've been in contact with customer service about this thing, and while they're friendly and courteous, they really don't know anything about their product. According to their lead tech "there is no recovery or download mode".
Headache.
Well fooling around with this device, I've found.... SOMETHING....
While holding the volume up button at the same time as the power button, it boots straight to one single image, shown below. I have a feeling it's the download mode. Whatever it is, it's progress. Can anyone recognize what I got into? It's not a fatal error-- when I hit the reset button and reboot the tablet normally, all is fine.
I've tried to reboot into recovery via adb but I get the message that the command is not allowed. And of course, su is not allowed either.
Anyone have any suggestions on running adb on my computer... what process I would need to follow to manually root an ICS tablet? Would I just follow the same steps as I would in manually rooting a gingerbread device, or is there different lines of code I would need to use for ICS?
As for what device the kernel for THIS device has been ported from (it's obviously emulating something that has a magnometer which this unit doesn't have, etc...)... tech support doesn't know that either. The only clue I have that MIGHT help (other than the kernel version, build number, etc... all this is documented in another post, if anyone cares to take a look) is the FIRST boot image is of the penguin.
I would appreciate ANY feedback/information/advice anyone could offer in progressing with this "adventure"!
Thanks
Well with another twenty minutes of blindly pressing buttons I've found the recovery mode. From the screen displaying the android with the open panel (which I have concluded is NOT the download mode), pressing volume up, back, and power at the same time opens the recovery mode. The recovery is:
Android system recovery <3e>
Recovery system v4.00
No option to apply zip from sd, I guess this is to be expected on a stock device.

hi
in application select usb debug mode
install from unknown sources
connect to pc and run DooMLoRD_v4_ROOT
should work
regards
fred

didn't work.
After adb started successfully, sat for two hours and did nothing.

hi
are you using windows ?
is it reconized by windows ? do you have the drivers installed ?
ich processor use that tablet ?

Yeah I'm running Windows Vista, and my PC does recognize the device when it's connected (says drivers have been installed properly when connected under USB debugging mode, no problem transferring files in USB mode)
It's the ARMv7 processor
The device is recognized as Full ASOP on Rk29sdk

I've run across a new problem, which might actually be the main issue of the WHOLE problem. I was trying to push some files with adb from my laptop and it came to my attention that the driver for my device only acknowledges it as a mass storage device, even when the tablet is NOT mounted for mass storage. SOOOO... I guess I need a driver that will allow me to use adb. Any suggestions?

did you try with the drivers package from sdk ?

yup. Even gone as far as uninstalling the adb and sdk programs I had on my pc, downloading the newest versions and reinstalling. My computer "recognizes" the divice, but only as folders. Even when it's not mounted as mass storage.

STILL having te driver issue. Anyone have any suggestions on how to fnd a driver that will work with adb?
Sent from my Full AOSP on Rk29sdk using XDA

How did I root my “Full AOSP Rk29sdk”-MID 7-inch tablet (Android 4.0.3)
Hi Wingnut79 and others,
I have an Android 4.0.3 Tablet 7 inch, named "Full AOSP Rk29sdk" - and was also eager to root it....
After hours of search, trial and error, I succeeded.
My tablet is now fully rooted, and I can use ROM manager and all the aps for rooted android-devices....
How did I do that ?
I explain it here, in the attachment...
As you can see, my Windows is in the Dutch language, so I nevertheless hope everyone can understand what to do where...
I hope this can help...

Make sure it's not a Chinese Apad!
Make sure it's not a Chinese Apad! If u go on ebay u will see tons of tablets with ics 4.0.3. but the android on it it's a modified and weird version. I doublt it even is ics. One of my friends have it, and he cannot use the App Market, bcuz it said "Device not compatible with Market". Did u successfully downloaded stuff form the Market? If not, that maybe it's a piece of Chinese crap and u should call walmart for a refund.

It downloads apps from Android Market, Getjar, Amazon etc... just fine.
BAUDI--
I will try this later this afternoon, is it going to be an issue that my laptop OS is windows vista?

Mine tablet is a chinese tablet - but it's clearly really Android 4.0.3.
So, I also download and install applications from Playstore /Android Market/ etc.
It has Wifi, Bluetooth, 3G, GPS-AGPS, FM-radio,.... and evrything works really fine.
My sole problem was: no rootaccess (what I didn't understand, because it's "Android Open Source Project"...?)
Wingnut79,
as far as described in the guide I refer to, it works equally well on Vista. Just sometimes a little bit other name or place to find the properties or so - but should not be a problem at all.
I forgot to insist on the need to kill and restart adb after each change. I am not sure its really necessary each time, but I experencied that when I first thought "again nothing", it seemed well to work after "adb kill-server" and then "adb start-server"....
At some steps (I can't remember wich) I even rebooted my PC....
Now, everything works immediately...
So ROM Manager etc. works well, I have SuperUser... etc .
Good luck!

baudi said:
Mine tablet is a chinese tablet - but it's clearly really Android 4.0.3.
So, I also download and install applications from Playstore /Android Market/ etc.
It has Wifi, Bluetooth, 3G, GPS-AGPS, FM-radio,.... and evrything works really fine.
My sole problem was: no rootaccess (what I didn't understand, because it's "Android Open Source Project"...?)
Wingnut79,
as far as described in the guide I refer to, it works equally well on Vista. Just sometimes a little bit other name or place to find the properties or so - but should not be a problem at all.
I forgot to insist on the need to kill and restart adb after each change. I am not sure its really necessary each time, but I experencied that when I first thought "again nothing", it seemed well to work after "adb kill-server" and then "adb start-server"....
At some steps (I can't remember wich) I even rebooted my PC....
Now, everything works immediately...
So ROM Manager etc. works well, I have SuperUser... etc .
Good luck!
Click to expand...
Click to collapse
Just because it says it is 4.0.3 doesn't mean its pure AOSP. Remember that the China gov has its hands into a lot and there are things that they like to install on their devices to monitor the users and then close it up so it can't be changed.
Sent from my Inspire 4G using Tapatalk 2

this app rooted my Full AOSP on rk29sdk
I tryed many ways trying to root my tablet, even unlockroot.exe
I found SuperOneClickv2.3.3 and it found my tablet right off, it said my tablet looks rooted( but I knew it was not) so I let it do the root process, it installed superuser also
SuperOneClickv2.3.3
you may have to temp turn your virus program off, I use avira so I right clicked the task bar icon and unchecked realtime protection

universel root
try the universel root for the version of android you have or of similar tabs

asdera-and said:
try the universel root for the version of android you have or of similar tabs
Click to expand...
Click to collapse
Where can we find this?
Is there a download link?
---------- Post added at 08:59 PM ---------- Previous post was at 08:58 PM ----------
carl1961 said:
I tryed many ways trying to root my tablet, even unlockroot.exe
I found SuperOneClickv2.3.3 and it found my tablet right off, it said my tablet looks rooted( but I knew it was not) so I let it do the root process, it installed superuser also
SuperOneClickv2.3.3
you may have to temp turn your virus program off, I use avira so I right clicked the task bar icon and unchecked realtime protection
Click to expand...
Click to collapse
Hello,
So SuperOneClick did work for you?
What kind of tablet do you have?
What version of Android was it running when you used SuperOneClick?
Thank you,

baudi said:
Hi Wingnut79 and others,
I have an Android 4.0.3 Tablet 7 inch, named "Full AOSP Rk29sdk" - and was also eager to root it....
After hours of search, trial and error, I succeeded.
My tablet is now fully rooted, and I can use ROM manager and all the aps for rooted android-devices....
How did I do that ?
I explain it here, in the attachment...
As you can see, my Windows is in the Dutch language, so I nevertheless hope everyone can understand what to do where...
I hope this can help...
Click to expand...
Click to collapse
I tried this and it worked. I got root on my device thanks alot for the guide.
Now to the real problem. I have two identical devices (rk29sdk). One is not booting and I can't manage to reset it.
My idea is make a full backup of the working device and somehow install it on the other one (the broken).
How can I do that - when I try to connect with adb it says:
Code:
C:\Windows\system32>adb devices
List of devices attached
0123456789ABCDEF device
Then this
Code:
C:\Windows\system32>
C:\Windows\system32>adb backup -apk -shared -all -f /backup/mybackup.ab
adb: unable to connect for backup
So it sees the device but I can't backup?
[edit]Now I connect to the device, the 'adb reboot' command works and the device responds. it's just the backup command that is not working.
Please help

asemore said:
I tried this and it worked. I got root on my device thanks alot for the guide.
Now to the real problem. I have two identical devices (rk29sdk). One is not booting and I can't manage to reset it.
My idea is make a full backup of the working device and somehow install it on the other one (the broken).
How can I do that - when I try to connect with adb it says:
Code:
C:\Windows\system32>adb devices
List of devices attached
0123456789ABCDEF device
Then this
Code:
C:\Windows\system32>
C:\Windows\system32>adb backup -apk -shared -all -f /backup/mybackup.ab
adb: unable to connect for backup
So it sees the device but I can't backup?
[edit]Now I connect to the device, the 'adb reboot' command works and the device responds. it's just the backup command that is not working.
Please help
Click to expand...
Click to collapse
i am not at my computer to post the commands, but you can type the commands to backup your system (or dump it) from a androids term console, you need busybox installed
edit: try this link
http://www.addictivetips.com/mobile...es-boot-recovery-and-system-partition-images/
;;
Sent from my Full AOSP on Rk29sdk using xda premium
---------- Post added at 03:40 AM ---------- Previous post was at 03:25 AM ----------
Beeg Boy said:
Where can we find this?
Is there a download link?
---------- Post added at 08:59 PM ---------- Previous post was at 08:58 PM ----------
Hello,
So SuperOneClick did work for you?
What kind of tablet do you have?
What version of Android was it running when you used SuperOneClick?
Thank you,
Click to expand...
Click to collapse
yes it worked for root, my chinese phone just shows Full AOSP on Rk29sdk
Sent from my Full AOSP on Rk29sdk using xda premium

carl1961 said:
i am not at my computer to post the commands, but you can type the commands to backup your system (or dump it) from a androids term console, you need busybox installed
edit: try this link
http://www.addictivetips.com/mobile...es-boot-recovery-and-system-partition-images/
Click to expand...
Click to collapse
The thing is I don't have access on my tablet. It won't boot.
So I can't start an app from the tablet, or maybe I can?

[Q] Question about Rooting on a Mac

I tried to post this in the "Beginners Guide for Rooting" but I do not have privileges. I am trying to root my new s3 on a mac so I am trying to follow the guidance in section one of the guide. However the links for samsung drivers are in an .exe format and the link to the java jdk files has expired. I downloaded the samsung drivers from the link and opened the (.exe) file and I attempted to install another version of the java jdk. When I connect Adam's casual the app recognizes my phone but I am unable to see it on my Mac through Finder. Am I ready to flash if the casual app can see my phone? Or do I need the osx compatible samsung drivers (not with a .exe filename) and a specific version of java jdk?
Thanks in advanced for any help. I tried to search for the answers but I have been coming up empty. Even though casual see's my phone, I'm still not sure if its ok to start flashing.

prescottc5 said:
I tried to post this in the "Beginners Guide for Rooting" but I do not have privileges. I am trying to root my new s3 on a mac so I am trying to follow the guidance in section one of the guide. However the links for samsung drivers are in an .exe format and the link to the java jdk files has expired. I downloaded the samsung drivers from the link and opened the (.exe) file and I attempted to install another version of the java jdk. When I connect Adam's casual the app recognizes my phone but I am unable to see it on my Mac through Finder. Am I ready to flash if the casual app can see my phone? Or do I need the osx compatible samsung drivers (not with a .exe filename) and a specific version of java jdk?
Thanks in advanced for any help. I tried to search for the answers but I have been coming up empty. Even though casual see's my phone, I'm still not sure if its ok to start flashing.
Click to expand...
Click to collapse
I don't remember if my phone showed up on my Mac in finder, but Adam's casual recognized my phone, I rooted and unlocked using the tool and have been flashing ROMS ever since.

davefields3 said:
I don't remember if my phone showed up on my Mac in finder, but Adam's casual recognized my phone, I rooted and unlocked using the tool and have been flashing ROMS ever since.
Click to expand...
Click to collapse
Did you download the samsung drivers in the link ( the .exe files) and install them on your mac? Also do you still have a copy of the java jdk files? The link in the "guide " is dead or the files have been moved. Thanks.

Mine did not show up in finder. I did have to download another program to interface with the phone. Just run Casuals and you will be fine.
Sent from my SCH-I535 using xda premium

prescottc5 said:
Did you download the samsung drivers in the link ( the .exe files) and install them on your mac? Also do you still have a copy of the java jdk files? The link in the "guide " is dead or the files have been moved. Thanks.
Click to expand...
Click to collapse
If I remember correctly, you can't download the samsung drivers on a Mac. And no, sorry I don't have the files

There is no drivers for mac. The only thing that will show is a sdcard if you have one. You are good to use Casual.

fr8cture said:
There is no drivers for mac. The only thing that will show is a sdcard if you have one. You are good to use Casual.
Click to expand...
Click to collapse
Mine doesn't show the sdcard. I can use ADB but that's the only way I can communicate to my device over USB. I have't tried Casual.

Well I finally got home so I could use my Mac with my phone. Casuals worked great a couple of weeks ago as did adb. Now, I can't get either to work. I read that some are having issues with the usb ports on the newer MacBook Pros. I will do a little know testing and see if I can find a way to make it work post back. I tried rebooting, different cables, etc with no luck. If anyone knows anything, please chime in.
Sent from my SCH-I535 using xda premium

HHF2 said:
Well I finally got home so I could use my Mac with my phone. Casuals worked great a couple of weeks ago as did adb. Now, I can't get either to work. I read that some are having issues with the usb ports on the newer MacBook Pros. I will do a little know testing and see if I can find a way to make it work post back. I tried rebooting, different cables, etc with no luck. If anyone knows anything, please chime in.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Okay, after a lot of digging, I finally figured out what I did. I take no credit for this, I found it on here in reply to a thread somewhere. I can't remember where as I usually view this site on my cell phone.
sudo kextunload -v /System/Library/Extensions/EasyTetherUSBEthernet.kext
from a terminal. I forget if you have to reboot or not.
This will disable tethering, but you can now see your device via adb.
To renable tethering once you're done debugging, use
sudo kextload -v /System/Library/Extensions/EasyTetherUSBEthernet.kext
This is for EasyTether only, but I am sure that there could be another type of app that would do the same thing? If you could isolate the app, it should be as easy as replacing the EasyTether part of the command and running that. Good luck, I personally know how aggravating that things like this can be.

ADB Offline and no access to bootloader

A few days ago I've tried using ADB but it said my device is offline. Earlier I tried ADB over network. Again, it said my phone is offline. So I wanted to see if I can get ADB access from the bootloader. Surprize: I can't get into the bootloader. If I turn my phone off and press Volume Down + Power, it just boots.
Now, my phone is working good, I just wanted adb access to do that darn EFS backup. And what's up with that "can't get into bootloader" stuff? I did it fine and dandy when I rooted my phone..
EDIT: well, since I can not do the backup the normal way, I just downloaded the efs folder as a zip. and dev/block/. Is it as effective as the normal way?

andrei1015 said:
A few days ago I've tried using ADB but it said my device is offline. Earlier I tried ADB over network. Again, it said my phone is offline. So I wanted to see if I can get ADB access from the bootloader. Surprize: I can't get into the bootloader. If I turn my phone off and press Volume Down + Power, it just boots.
Now, my phone is working good, I just wanted adb access to do that darn EFS backup. And what's up with that "can't get into bootloader" stuff? I did it fine and dandy when I rooted my phone..
EDIT: well, since I can not do the backup the normal way, I just downloaded the efs folder as a zip. and dev/block/. Is it as effective as the normal way?
Click to expand...
Click to collapse
It is Vol-Up + Power for bootloader. And you can't have adb access in bootloader mode. Only fastboot access.

Ok but why isn't adb working? Why does it always say it's offline?
Sent from my Google Nexus S

andrei1015 said:
Ok but why isn't adb working? Why does it always say it's offline?
Sent from my Google Nexus S
Click to expand...
Click to collapse
It could be that you installed some software/driver that overrides a working USB driver.
Try install Google USB driver from Android SDK Tools.
Install Android SDK Tools
When SDK Manager runs, select Google USB Driver, see attached pic
If missed, run SDK Manager again as Administrator
Also, make sure you turn on Developer options and "check" Andoid (USB) debugging option in Developer options setup.

_android_ said:
It could be that you installed some software/driver that overrides a working USB driver.
Try install Google USB driver from Android SDK Tools.
Install Android SDK Tools
When SDK Manager runs, select Google USB Driver, see attached pic
If missed, run SDK Manager again as Administrator
Also, make sure you turn on Developer options and "check" Andoid (USB) debugging option in Developer options setup.
Click to expand...
Click to collapse
Yup, I have all of the above.. Still offline >.<

andrei1015 said:
Yup, I have all of the above.. Still offline >.<
Click to expand...
Click to collapse
Do you have the Samsung Galaxy Nexus ADB interface showing in your device manager?
Try uninstall and reload again.

Almost = https://dl.dropbox.com/1/view/xiulpm329s4wxcd/Apps/CloudShot/shot_25022013_192328.png
Still it says offline.
(thank you for trying to help me )

In fastboot mode it looks like this:

just tested at work and it says "device" instead of "offline" which is good I think. The only difference is that at work I installed the SDK long after I got it at home and it has a slightly different folder structure and it also comes with eclipse.

Resolved. Downloaded the new SDK with ADT from the android site and it works. Please forgive me for posting so many times. Can someone please delete this thread?

andrei1015 said:
Resolved. Downloaded the new SDK with ADT from the android site and it works. Please forgive me for posting so many times. Can someone please delete this thread?
Click to expand...
Click to collapse
Good for you.
Anyway, if you followed post #4 and installed the new SDK Tools, would have saved you a lot of time.