• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Attempting to gain root with htc unlocked bootloader

scotty85 said:
nope,no need to relock to flash superuser. just download,place on root of sd card,then boot to recovery,wipe cache,wipe dalvik cache,then flash the file. when you reboot,youll see superuser in yur app drawer :)
Click to expand...

When you say to wipe dalvik cache, is that the same as the wipe data/factory reset option? I don't see anything about wiping the "dalvik cache".

These are the only options:

-reboot system now
-apply update from sdcard
-wipe data/factory reset
-wipe cache partition (did this already)
-install zip from sdcard
-backup and restore
-mounts and storage
-advanced
-power off

**Nevermind, found it in Advanced.

Flashed, and all set up in my apps. :D

So now I should be able to downgrade in order to get S-off, correct? And this is where you said I may have to relock?
 
yes,you now have root access,so you can start at the step "3) downgrade with adb" and enter those commands.

you will need to relock in order to flash the "downgrade froyo PB31IMG" so after you adb reboot bootloader to get to fastboot, you can type fastboot oem lock to relock it.

i am fairly certain that PB31IMG will not run with the bootloader unlocked, but you are welcome try try it if you want. worse case is that PB31IMG will not flash.

if you do relock it,the phone may automatically reboot after it relocks. if it does,it should be ok. just let it boot,then boot back to hboot to try and flash it.

if you have trouble flashing PB31IMG,you can try the directions in this post: http://androidforums.com/incredible...2-3-4-downgrade-get-s-off-24.html#post4107845
 
scotty85 said:
yes,you now have root access,so you can start at the step "3) downgrade with adb" and enter those commands.

you will need to relock in order to flash the "downgrade froyo PB31IMG" so after you adb reboot bootloader to get to fastboot, you can type fastboot oem lock to relock it.

i am fairly certain that PB31IMG will not run with the bootloader unlocked, but you are welcome try try it if you want. worse case is that PB31IMG will not flash.

if you do relock it,the phone may automatically reboot after it relocks. if it does,it should be ok. just let it boot,then boot back to hboot to try and flash it.

if you have trouble flashing PB31IMG,you can try the directions in this post: http://androidforums.com/incredible...2-3-4-downgrade-get-s-off-24.html#post4107845
Click to expand...

Err...can you walk me through that a little bit? Do I need to get into HBOOT and bring up the command prompt again, cd \Android, fastboot devices, and put that in, or...something else entirely? I'm sorry, I'm not sure what you mean by adb reboot bootloader.
 
sorry for the delayed reply,ive been at work. in retrospect,i should have told you to just follow the whole guide,as if you use the folder you allready have set up(and called android) for fastboot,adb,youll need make some minor changes to an adb command or 2.

the guide is about as good of a walk thru as i think i can give,so maybe just start from the beginning,and follow it all,with exception that you do NOT need tp do step "2) root with unrevoked 3.22" as you have allready rooted with htcdev.

when youre at the end of the adb commands in step 4,the last bold adb command is adb reboot bootloader. this command will take you to the fastboot screen,where you will enter the lock command fastboot oem lock

the bootloader will then relock,so you can flash the downgrade froyo PB31IMG

ive got some errands to run,but will be happy to answer whatever qhuestions you have. hope the above has cleared it up some for you :)
 
No problem; I have work today, too. I didn't bring my phone with me because I was neglecting my homework in my fervor to get it rooted. I really have to catch up on homework, though, I'm regretting not bringing my phone now, of course. >.> I really want to keep working on it, but I have to do this. Thank you so much for all your help, and I'll keep you posted when I get back on it. You guys are awesome. Probably be some time after I get off work, at 4:30.
 
scotty85 said:
any luck? :)
Click to expand...

So, I downloaded the 2.2 downgrade (PB31IMG.zip) file from the guide, and the md5 sum verifier won't recognize it to even verify the summy thingy. I'm not sure if this is relevant, but since the guide says "**make sure to check the md5 sums match those listed!**", I'm a bit concerned about it. Incidentally, Windows can't seem to unzip it, either, not that I need to.
 
Not sure what could be wrong with your md5 summer. Another option would be to put the pb31img on your sd card,and use a market app called scary aliens AFV(android file verifier). Its a great,easy to use app. You are right to be concerned if you cant verify a files integrity.

Its no biggie that windows wont natively open the pb31img. I use 7 zip when i need to open one. If you want to unzip it and check out wats inside,make a copy of the file,then upzip that. Its a good practice to not extract the actual file that you intend to flash :)
 
scotty85 said:
Not sure what could be wrong with your md5 summer. Another option would be to put the pb31img on your sd card,and use a market app called scary aliens AFV(android file verifier). Its a great,easy to use app. You are right to be concerned if you cant verify a files integrity.

Its no biggie that windows wont natively open the pb31img. I use 7 zip when i need to open one. If you want to unzip it and check out wats inside,make a copy of the file,then upzip that. Its a good practice to not extract the actual file that you intend to flash :)
Click to expand...

I downloaded a different md5 version from cnet that worked just fine, but I gotta' go to bed nao. Long day, tomorrow. Keep you posted. Night. :)
 
I got to the very end of the code, I typed this in exactly, "./flash_image misc /sdcard/mtd0.img", and this happened:

error opening /sdcard/mtd0.img: No such file or directory

:( What do I do?
 
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Emily>cd c:\miniadb_inc

c:\miniadb_inc>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT071HJ05692 device


c:\miniadb_inc>md5sums flash_image

MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - PC-Tools.Net: Tools and utilities for Windows, Unix/Linux, DOS
Type md5sums -h for help

[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[c:\miniadb_inc\]
flash_image 0098a7dd6600b55fac34fc6645be5d7a

c:\miniadb_inc>md5sums mtd0.img

MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - PC-Tools.Net: Tools and utilities for Windows, Unix/Linux, DOS
Type md5sums -h for help

[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[c:\miniadb_inc\]
mtd0.img 34307be744275f1db1dd16af04c37839

c:\miniadb_inc>adb push flash_image /data/local/
1586 KB/s (76044 bytes in 0.046s)

c:\miniadb_inc>adb push mtd0.img/sdcard/
Android Debug Bridge version 1.0.26

-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.

If -p is not specified, the ANDROID_PRODUCT_OUT

environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>:<port> - connect to a device via TCP/IP
disconnect <host>:<port> - disconnect from a TCP/IP device

device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport

adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.

adb help - show this help message
adb version - show version num

DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition

scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns

adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:

- If <directory> is not specified, both /system and /data partitions will be u
pdated.

- If it is "system" or "data", only the corresponding partition
is updated.

c:\miniadb_inc>adb shell
$ su
su
# cd /data/local
cd /data/local
# chmod 0755 /data/local/flash_image
chmod 0755 /data/local/flash_image
# cd /data/local
cd /data/local
# ./flash_image misc /sdcard/mtd0.img
./flash_image misc /sdcard/mtd0.img
error opening /sdcard/mtd0.img: No such file or directory
# ./flash_image misc /sdcard/mtd0.img
./flash_image misc /sdcard/mtd0.img
error opening /sdcard/mtd0.img: No such file or directory
# ./flash_image misc /sdcard/mtd0.img
./flash_image misc /sdcard/mtd0.img
error opening /sdcard/mtd0.img: No such file or directory
#
 
Is your sd card present in your phone? Make sure its in charge only,and not disc drive mode. It looks like it never pushed mtd0 to your sd card,wich is why it can't find that directory
 
scotty85 said:
Is your sd card present in your phone? Make sure its in charge only,and not disc drive mode. It looks like it never pushed mtd0 to your sd card,wich is why it can't find that directory
Click to expand...

Ohhhh. Setting it to Charge Only, trying it again.
 
Everything seemed to work this time, except the last part. When I type in "adb reboot bootloader", it says adb: not found.

cd /data/local
# ./flash_image misc /sdcard/mtd0.img
./flash_image misc /sdcard/mtd0.img
# exit
exit
$ adb reboot bootloader
adb reboot bootloader
adb: permission denied
$ su
su
# adb reboot bootloader
adb reboot bootloader
adb: not found
# exit
exit
$ su
su
# adb reboot bootloader
adb reboot bootloader
adb: not found
# adb reboot bootloader
 
If it doesn't boot the first time,don't panic. Just run the pg31img again.

Once it finishes,and boots,you should be on froyo :)
 
zamkat said:
Ahh, I feel dumb, I totally didn't see that step. I'm really tired. I've never talked to a phone through a computer before. XD I'm only at the beginning of my IT classes. Q_Q
Click to expand...
But look how quickly your post count is rising, you'll be a "senior member" before you know it :D
 
sdrawkcab25 said:
But look how quickly your post count is rising, you'll be a "senior member" before you know it :D
Click to expand...

Ya, right. Senior in ineptitude, maybe...

So do I just flash unrevoked forever or...? The guide is a bit unclear. It says "run it as you did the previous version. before plugging in your phone,make sure 'disable phone security is checked' in the file menu."

I don't know where to disable the phone's security...I thought that's why I was doing this... -_-
 
correct-disabling phone security is why youre doing it :) there is a box you need to place a check mark so that unrevoked will disable security.

at this point,you have a couple options.

1)run unrevoked 3.22(normally you would use 3.32,but it didnt work for the other user that had htcdev unlock) hopefully it will install a recovery,and turn s-off. if you get a recvoery,but are still s on,then try flashing the "forever" patch in recovery.

2)assuming your hboot did not downgrade to .92,you can:
-reunlock using your original unlock token
-fastboot flash your recovery like you did above
-flash the superuser root files in recovery
-flash the "forever" patch in recovery

i would kind of like to see you try #2,just for S&Gs,as i was never quite clear if the other user that did this with htcdev unlock tried it. what worked for him,after numerous failures of unrevoked 3.32,was running 3.22.

i believe option #2 will work,but i cant say for sure. wicheever you decide to try,let us know how it goes :)
 
scotty85 said:
correct-disabling phone security is why youre doing it :) there is a box you need to place a check mark so that unrevoked will disable security.

at this point,you have a couple options.

1)run unrevoked 3.22(normally you would use 3.32,but it didnt work for the other user that had htcdev unlock) hopefully it will install a recovery,and turn s-off. if you get a recvoery,but are still s on,then try flashing the "forever" patch in recovery.

2)assuming your hboot did not downgrade to .92,you can:
-reunlock using your original unlock token
-fastboot flash your recovery like you did above
-flash the superuser root files in recovery
-flash the "forever" patch in recovery

i would kind of like to see you try #2,just for S&Gs,as i was never quite clear if the other user that did this with htcdev unlock tried it. what worked for him,after numerous failures of unrevoked 3.32,was running 3.22.

i believe option #2 will work,but i cant say for sure. wicheever you decide to try,let us know how it goes :)
Click to expand...

I'll try #2 for science, even though it's a pain in the ass. If things go wrong, I'm holding you accountable. :p

Before I do, though, there's some things I'm confused about. When I downgraded, I basically reformatted my phone with a fresh operating system, right? Which is why my bootloader is locked again? How does that not unroot the phone? Sorry, again if it's a dumb question. Also, is it okay for me to upgrade the OS back to the normal version, now?
 
zamkat said:
I'll try #2 for science, even though it's a pain in the ass. If things go wrong, I'm holding you accountable. :p
Click to expand...

thanks. i will very truly,sincerely appreciate the info :cool:

rest assured the worse thing that will happen is an error message saying "unable to nand unlock" or something to that affect. shouldnt be any smoke or flames :eek: :D

try flashing the forever zip a couple times if it doesnt work,or gives error messages. no need to wipe anything,other than a cache/dalvik cache wipe.

if it fails to give s-off or gives error messages,then reboot and try running 3.22 again :)

also,im off for some family easter shenanigans,but ill try and watch if you have questions :)
 
You must log in or register to reply here.
Back
Top Bottom