Can't Unroot

[troo53]

So I'm following the tutorial and this is where I get hung up. Why am I denied?

http://www.androidpolice.com/2011/0...t-the-htc-thunderbolt-and-return-it-to-stock/

List of devices attached
HT11TS003113 device

MacBook-Pro:tools trev0079$ ./adb push misc.img /data/local/
2032 KB/s (262144 bytes in 0.125s)
MacBook-Pro:tools trev0079$ ./adb push busybox /data/local/
2102 KB/s (1062992 bytes in 0.493s)
MacBook-Pro:tools trev0079$ ./adb shell chmod 777 /data/local/busybox
MacBook-Pro:tools trev0079$ ./adb shell
$ su
/data/local/busybox md5sum /data/local/misc.Permission denied
$ img adb push busybox /data/local/

c88dd947eb3b36eec90503a3525ae0de /data/local/misc.img
md5sum: can't open 'adb': No such file or directory
md5sum: can't open 'push': No such file or directory
md5sum: can't open 'busybox': No such file or directory
$ dd if=/data/local/misc.img of=dev/block/mmcblk0p17
dev/block/mmcblk0p17: cannot open for write: Permission denied

 

[DroidXcon]

So I'm following the tutorial and this is where I get hung up. Why am I denied?

[Tutorial] How To "Un-Root" The HTC ThunderBolt And Return It To Stock | Android News, Reviews, Apps, Games, Phones, Tablets, Tips, Mods, Videos, Tutorials - Android Police

List of devices attached
HT11TS003113 device

MacBook-Pro:tools trev0079$ ./adb push misc.img /data/local/
2032 KB/s (262144 bytes in 0.125s)
MacBook-Pro:tools trev0079$ ./adb push busybox /data/local/
2102 KB/s (1062992 bytes in 0.493s)
MacBook-Pro:tools trev0079$ ./adb shell chmod 777 /data/local/busybox
MacBook-Pro:tools trev0079$ ./adb shell
$ su
/data/local/busybox md5sum /data/local/misc.Permission denied
$ img adb push busybox /data/local/

c88dd947eb3b36eec90503a3525ae0de /data/local/misc.img
md5sum: can't open 'adb': No such file or directory
md5sum: can't open 'push': No such file or directory
md5sum: can't open 'busybox': No such file or directory
$ dd if=/data/local/misc.img of=dev/block/mmcblk0p17
dev/block/mmcblk0p17: cannot open for write: Permission denied

after typing su, look at your phone and see if superuser app is asking you to allow or deny

 

[troo53]

Nope not saying anything.


$ su
Permission denied
$

 

[DroidXcon]

Nope not saying anything.


$ su
Permission denied
$

then you are not rooted

 

[troo53]

then you are not rooted

Then how do I have Set CPU, Titanium Backup, Wireless Tether all working? I can also use an emulator for random games.

I even went into root explorer and removed all the bloatware.

I followed this procedure below verbatim.

http://forum.androidcentral.com/thu...9-mac-procedure-how-root-htc-thunderbolt.html

I watched it at the end and it completed and said it was successful.

 

[DroidXcon]

Then how do I have Set CPU, Titanium Backup, Wireless Tether all working? I can also use an emulator for random games.

I even went into root explorer and removed all the bloatware. I followed this procedure verbatim.

http://forum.androidcentral.com/thu...9-mac-procedure-how-root-htc-thunderbolt.html

I watched it at the end and it completed and said it was successful.

download a free terminal emulator from the market
open it and type su, tell me if you get #

 

[troo53]

I installed Android Terminal Emulator:

I typed in su.

Super User popped up and said do you want to grant permission. Granted permission and I get #.

I'm just thinking about possible reasons why it's being like this. The whole reason I'm trying to unroot is to reroot so I can flash a custom rom, because when I go to install a rom and hit backup + wipe data it brings me back to the boot loader where it shows S is ON, and doesn't allow me to install the rom just the basic boot loader options.

 

[DroidXcon]

I installed Android Terminal Emulator:

I typed in su.

Super User popped up and said do you want to grant permission. Granted permission and I get #.

ok try again via adb

 

[dkoss]

If you have S-on you do not have read/write permissions yet you may need to go back to the tutorial and gain S-off. This is where you write the new bootloader and get the md5sum of 6991368ee2deaf182048a3ed9d3c0fcb.

 

[troo53]

$ dd if=/data/local/misc.img of=/dev/block/mmcblk0p17
/dev/block/mmcblk0p17: cannot open for write: Permission denied

 

[DroidXcon]

If you have S-on you do not have read/write permissions yet you may need to go back to the tutorial and gain S-off. This is where you write the new bootloader and get the md5sum of 6991368ee2deaf182048a3ed9d3c0fcb.

but if he had s on would he still have root privilages on the phone and not when using adb?

 

[troo53]

If you have S-on you do not have read/write permissions yet you may need to go back to the tutorial and gain S-off. This is where you write the new bootloader and get the md5sum of 6991368ee2deaf182048a3ed9d3c0fcb.

Do I go back through the whole tutorial to do this? Can I re-root even though I'm already rooted without going back to stock?

Essentially can I just start the whole procedure over even though I'm rooted without screwing anything up?

 

[dkoss]

but if he had s on would he still have root privilages on the phone and not when using adb?

I believe so, the original exploit was just root or su privileges with s-on. You could not write to the bootloader hence s-on (security on). He has root but not the ability to write to the bootloader.

The s-off is obtained when placing the first PG05IMG.zip to the phone.

 

[dkoss]

Do I go back through the whole tutorial to do this? Can I re-root even though I'm already rooted without going back to stock?

Essentially can I just start the whole procedure over even though I'm rooted without screwing anything up?

This should not be an issue. The first time I tried to root my D1 I think I went through the process about 10 times before I figured it out.

 

[troo53]

How will I know if I did it right then after going back through the steps? Is that the reason why I can't flash roms?

 

[dkoss]

How will I know if I did it right then after going back through the steps? Is that the reason why I can't flash roms?

After you flash the first PG05IMG.zip, which is the downgrade RUU, after the reboot you should have s-off.

This is why you cannot flash rom's.

 

[troo53]

This was in my folder... when I went to download the original file to restart the process:


The adb tool has moved to platform-tools/

If you don't see this directory in your SDK,
launch the SDK and AVD Manager (execute the android tool)
and install "Android SDK Platform-tools"

Please also update your PATH environment variable to
include the platform-tools/ directory, so you can
execute adb from any location.

 

[DroidXcon]

This was in my folder... when I went to download the original file to restart the process:


The adb tool has moved to platform-tools/

If you don't see this directory in your SDK,
launch the SDK and AVD Manager (execute the android tool)
and install "Android SDK Platform-tools"

Please also update your PATH environment variable to
include the platform-tools/ directory, so you can
execute adb from any location.

you should follow cory's procedure that it is sticked, the adb connection will be quicker and easier

 

[dkoss]

you should follow cory's procedure that it is sticked, the adb connection will be quicker and easier

He actually did say he followed that to a T.

I'm thinking something went wrong during the process. I would just go back through the tutorial. Just remember you have to have s-off to be able to write to the bootloader and you should see s-off the second time you reboot to bootloader.

 

[troo53]

Alright well I'll try it again and report back!