[DBONE1221]

So when you did
$ ./adb shell dd if=/data/local/misc.img of=/dev/block/mmcblk0p17
do you know if it successfully made the image?

then you used the command
$ ./adb reboot bootloader

it went into the bootloader you made the selection and it didnt switch over

If it did make the above image. thats all you needed , perhaps you can pull the battery and enter the bootloader manually

i ended up restarting the phone from the bootloader, is there a way to start from where i left off or do i need to re enter the adb commands? thanks sorry how do i enter the bootloader manually??

[DroidXcon]

i ended up restarting the phone from the bootloader, is there a way to start from where i left off or do i need to re enter the adb commands? thanks sorry how do i enter the bootloader manually??

the first set of commands only granted you temporary root so that you could copy that img file.

so you can just pick up from where you left off now

[DBONE1221]

I never finished the files in the bootloader, waited 10 seconds-- nothing is it bad to restart again? when i get to the step and wait another 10 seconds without nothing what should i do?

[DroidXcon]

I never finished the files in the bootloader, waited 10 seconds-- nothing is it bad to restart again? when i get to the step and wait another 10 seconds without nothing what should i do?

well what im saying is if you got to the point of writing

./adb bootloader

then you can pick up where you left off right there,

but if you feel like you want to start over i think it should be fine at worst it will just overwrite or make another img file

[DBONE1221]

Thank you so much--
If i had a Starbucks card id send you the card #!

[DroidXcon]

Thank you so much--
If i had a Starbucks card id send you the card #!

lol thanks , try it and please let us know your results

[DBONE1221]

well what im saying is if you got to the point of writing

./adb bootloader

then you can pick up where you left off right there,

but if you feel like you want to start over i think it should be fine at worst it will just overwrite or make another img file

got back to the same screen.. i am having problems with these specific steps: You should see several files loaded and checked. Don't freak out at the warnings. The screen will eventually clear and you will see "checking pd05img.zip."
Eventually, you will be asked: Do you want to start update? Press the volume up button to say yes.
Once you do, you will see a progress bar in the upper right corner and a bunch of stuff going on in the middle. Just be patient and let it do its thing.
Press power to reboot.

is there a possibility that i did not download something correctly?

[DroidXcon]

got back to the same screen.. i am having problems with these specific steps: You should see several files loaded and checked. Don't freak out at the warnings. The screen will eventually clear and you will see "checking pd05img.zip."
Eventually, you will be asked: Do you want to start update? Press the volume up button to say yes.
Once you do, you will see a progress bar in the upper right corner and a bunch of stuff going on in the middle. Just be patient and let it do its thing.
Press power to reboot.

is there a possibility that i did not download something correctly?

did you by any chance skip over
4. Download the following file to your SD card: PG05IMG_downgrade.zip

Using Safari: click link to open Multiupload page --> right click the direct download button > download linked file as > click No Name in upper left corner (your SD card) > click save

5. On your SD card rename: PG05IMG_downgrade.zip to PG05IMG.zip

[DBONE1221]

did you by any chance skip over
4. Download the following file to your SD card: PG05IMG_downgrade.zip




5. On your SD card rename: PG05IMG_downgrade.zip to PG05IMG.zip

Yes, I have it already under a folder named Downgrade.

[DroidXcon]

Yes, I have it already under a folder named Downgrade.

remove it from the folder and leave it on the base of the sdcard not in any folders

[DBONE1221]

took it out, ill let you know how it goes

[DroidXcon]

took it out, ill let you know how it goes

Any results?

[DBONE1221]

Yes, that worked but downloaded shoot me and says i do not have root status s there something i need to do?

[DroidXcon]

Yes, that worked but downloaded shoot me and says i do not have root status s there something i need to do?

you downloaded superuser app, then rebooted the phone?

[DBONE1221]

Yes, restarting phone again. hold on. Btw what exactly is superuser?

[DroidXcon]

Yes, restarting phone again. hold on. Btw what exactly is superuser?

root = gaining super user permission, gives you permission to change anything you want

superuser app is a way of managing what apps have those permissions

[DBONE1221]

it worked! thank you so much for helping me through this you have no idea..

[DroidXcon]

it worked! thank you so much for helping me through this you have no idea..

Great congrats very welcome

[DBONE1221]

last question.. how do i download the newest kernel source?? :X

[Raptor007]

Sounds like you flashed the downgrade image. See post #3 of the Windows sticky I started; that's the process you should follow to unroot. You can adapt the same procedure to Mac. Just put a ./ in front of the ADB commands.

Cory - I was trying to return to stock as well tonight following the procedure but as you noted for the MAC. I got to the last part

# dd if=/data/local/misc.img of=/dev/block/mmcblk0p17
and I get a denied error. Here is the commands I typed into the terminal.

$ cd ..
$ cd ..
$ cd and*
$ cd tools
$ ./adb devices ( the device comes up as attached)

$ ./adb push misc.img /data/local/
$ ./adb push busybox /data/local/
$ ./adb shell chmod 777 /data/local/busybox
$ ./adb shell

Then type the following; not including the $

$ su (when I typed this I get permission denied and cannot proceed)

Then type the following; not including the #

# /data/local/busybox md5sum /data/local/misc.img


The Command window must display the following checksum: c88dd947eb3b36eec90503a3525ae0de

# dd if=/data/local/misc.img of=/dev/block/mmcblk0p17
# reboot bootloader

Any suggestions or corrections are greatly appreciated.

[DroidXcon]

Cory - I was trying to return to stock as well tonight following the procedure but as you noted for the MAC. I got to the last part

# dd if=/data/local/misc.img of=/dev/block/mmcblk0p17
and I get a denied error. Here is the commands I typed into the terminal.

$ cd ..
$ cd ..
$ cd and*
$ cd tools
$ ./adb devices ( the device comes up as attached)

$ ./adb push misc.img /data/local/
$ ./adb push busybox /data/local/
$ ./adb shell chmod 777 /data/local/busybox
$ ./adb shell

Then type the following; not including the $

$ su (when I typed this I get permission denied and cannot proceed)

Then type the following; not including the #

# /data/local/busybox md5sum /data/local/misc.img


The Command window must display the following checksum: c88dd947eb3b36eec90503a3525ae0de

# dd if=/data/local/misc.img of=/dev/block/mmcblk0p17
# reboot bootloader

Any suggestions or corrections are greatly appreciated.

when you type su did you look at the phone and make sure to allow superuser access?

[notmebug]

For EasyTether removal:

Edit: To Fix:
1) Remove EasyTether from Network Preferences
2) In terminal run:
sudo kextunload -m com.mobile-stream.driver.EasyTetherUSBEthernet
3) Uninstall EasyTether from TB Applications.
4) Reboot TB. (This made it work, mac did not need a reboot)

Just figured this out today...

Remove Easytether from Mac OSX:
(it will pop-up a new network device every time you connect via USB otherwise... I'm using wireless tether now so it's rather annoying when I want to mount disk drive or usb charge)

Finder -> View -> Show System Files

delete: /System/Library/Extensions/EasyTetherUSBEthernet.kext

Awesome!
Did it actually reboot or did the screen just turn black. A reboot would have involved a vibration.
Thank you so much and great suggestions. Last night I attached a PDF to the first post, so you can see more verbose detail of each and everything returned for the various commands.

Screen went black, then solid white, bootloader restarted and began scanning PG05IMG.zip again. Not sure about vibrate but it caught me off guard.

[Raptor007]

when you type su did you look at the phone and make sure to allow superuser access?

Sorry it took so long to get back to your post. Last night I had already wiped my device, forgetting I needed Superuser on it. So I put Superuser back on along with Busybox. Started over as you can see here and I still get permission denied. Any other thoughts?

Last login: Tue Apr 5 18:25:43 on ttys000
91:~ Michael$ cd ..
91:Users Michael$ cd ..
91:/ Michael$ cd and*
91:android-sdk-mac_x86 Michael$ cd tools
91:tools Michael$ ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT12CS000687 device

91:tools Michael$ ./adb push misc.img /data/local/
2541 KB/s (262144 bytes in 0.100s)
91:tools Michael$ ./adb push busybox /data/local/
2513 KB/s (1062992 bytes in 0.413s)
91:tools Michael$ ./adb shell chmod 777 /data/local/busybox
91:tools Michael$ ./adb shell
$ su
Permission denied
$

[DroidXcon]

Sorry it took so long to get back to your post. Last night I had already wiped my device, forgetting I needed Superuser on it. So I put Superuser back on along with Busybox. Started over as you can see here and I still get permission denied. Any other thoughts?

Last login: Tue Apr 5 18:25:43 on ttys000
91:~ Michael$ cd ..
91:Users Michael$ cd ..
91:/ Michael$ cd and*
91:android-sdk-mac_x86 Michael$ cd tools
91:tools Michael$ ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT12CS000687 device

91:tools Michael$ ./adb push misc.img /data/local/
2541 KB/s (262144 bytes in 0.100s)
91:tools Michael$ ./adb push busybox /data/local/
2513 KB/s (1062992 bytes in 0.413s)
91:tools Michael$ ./adb shell chmod 777 /data/local/busybox
91:tools Michael$ ./adb shell
$ su
Permission denied
$

well you lost root it looks like try this

$ ./adb push busybox /data/local/
$ ./adb push psneuter /data/local/
$ ./adb push misc.img /data/local/
$ ./adb shell chmod 777 /data/local/busybox
$ ./adb shell chmod 777 /data/local/psneuter
$ ./adb shell /data/local/psneuter

then adb connection will kill and restart

$ ./adb shell

Then type the following; not including the $

$ su

Then type the following; not including the #

# /data/local/busybox md5sum /data/local/misc.img

[Cory Streater]

Sorry it took so long to get back to your post. Last night I had already wiped my device, forgetting I needed Superuser on it. So I put Superuser back on along with Busybox. Started over as you can see here and I still get permission denied. Any other thoughts?

Last login: Tue Apr 5 18:25:43 on ttys000
91:~ Michael$ cd ..
91:Users Michael$ cd ..
91:/ Michael$ cd and*
91:android-sdk-mac_x86 Michael$ cd tools
91:tools Michael$ ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT12CS000687 device

91:tools Michael$ ./adb push misc.img /data/local/
2541 KB/s (262144 bytes in 0.100s)
91:tools Michael$ ./adb push busybox /data/local/
2513 KB/s (1062992 bytes in 0.413s)
91:tools Michael$ ./adb shell chmod 777 /data/local/busybox
91:tools Michael$ ./adb shell
$ su
Permission denied
$

Been down that path already. If you hard reset you have to start all over again.