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

Root [HOW TO](gaining root)unlock,downgrade,and achieve s-off with htcDev

Hi Scotty.

First of all, thanks for your help.

Second of all, in the "[HOW TO]unlock,downgrade,and achieve s-off with htcDev" thread, At step 4 you say, "adb shell your prompt should change to a #. if it changes to a $,then type su note your phone may pop up a message asking you to allow permissions the first time you do this. if it does check "always" and touch "allow" on the superuser request on the phone screen."

So I get the $ sign, and when I type in su I get the response "su: Permission denied"

What should I do? If you already answered this, please direct me to it. Thank you.

Ebenezum
HTC Droid Incredible
Version 2.3.4
Other info will be supplied as needed.
 
Scotty85,
Thanks for this thread. My phone has been F'd up for the past 2 days and I lost root. Thanks to your thread I've gotten it re-rooted s-off, downgraded to 2.2 My only problem now is I can't get the Stock GB Image to flash. I've tried recovery and RUU with no luck. I'm stuck at 2.2. Any ideas?
 
Ebenezum said:
Hi Scotty.

First of all, thanks for your help.

Second of all, in the "[HOW TO]unlock,downgrade,and achieve s-off with htcDev" thread, At step 4 you say, "adb shell your prompt should change to a #. if it changes to a $,then type su note your phone may pop up a message asking you to allow permissions the first time you do this. if it does check "always" and touch "allow" on the superuser request on the phone screen."

So I get the $ sign, and when I type in su I get the response "su: Permission denied"

What should I do? If you already answered this, please direct me to it. Thank you.

Ebenezum
HTC Droid Incredible
Version 2.3.4
Other info will be supplied as needed.
Click to expand...
sounds like no root access :eek:

what happened when you did step 3? did the superuser file install correctly? if so,is superuser present in your app drawer?

if superuser is present,open it and see what its listing that it has granted and denied permissions to. you can try allowing things that are denied,or try clearing data from superuser(settings/apps/manage apps/superuser) and then try again.

ml4179 said:
Scotty85,
Thanks for this thread. My phone has been F'd up for the past 2 days and I lost root. Thanks to your thread I've gotten it re-rooted s-off, downgraded to 2.2 My only problem now is I can't get the Stock GB Image to flash. I've tried recovery and RUU with no luck. I'm stuck at 2.2. Any ideas?
Click to expand...

i need more details as to what youve tried to do,and what the direct results or error messages were as a result of your actions. if you have downgraded to 2.2 and become s off,it should be an easy prollem to sort :)
 
Good news. I got the image to Flash through HBOOT. I had been trying Clockwork Recovery (should that have worked?). I'm updated! The only thing I see that happed was that HBOOT was downgraded to version .92 Is there a benefit to leaving it or to update it? Thanks again..!
 
New problem. I apparently ok'd an OTA update. Phone rebooted then stopped at an icon of a phone with a red triangle/exclamation point. Pulled the batter, rebooted no problem. I tried to boot in to Clockwork Recovery from HBOOT.... same red triangle icon. Can't seem to re-flash the recovery because of the change to HBOOT. Is there an easier way to get Recovery back without going back through the downgrade?
 
ml4179 said:
New problem. I apparently ok'd an OTA update. Phone rebooted then stopped at an icon of a phone with a red triangle/exclamation point. Pulled the batter, rebooted no problem. I tried to boot in to Clockwork Recovery from HBOOT.... same red triangle icon. Can't seem to re-flash the recovery because of the change to HBOOT. Is there an easier way to get Recovery back without going back through the downgrade?
Click to expand...
Does you hboot say that you at s-off? If it does, can do this:
http://androidforums.com/incredible...egain-root-s-off-htc-unlocked-bootloader.html
 
Thanks again Scotty,

As it turns out no super user icon was found, but up until that step I thought everything was going perfectly. Should I start from the beginning and try again?
 
Ebenezum said:
Thanks again Scotty,

As it turns out no super user icon was found, but up until that step I thought everything was going perfectly. Should I start from the beginning and try again?
Click to expand...
you shouldnt have to start from the beginning. in a worse case,you could try reflashing superuser.

did you try clearing data in superuserr?

do that,then try typing adb shell and su again. this time make sure you have your phone away,and are watching for the pop up.

ml4179 said:
It is still s-off, but something else is screwed up now. I'm going to have go back through the whole thing.
Click to expand...

what is screwed up? you shouldnt have to redo anything... i suspect that you may be making it unnecessarily hard on yourself ;)
 
Ok, did as you said. There was no popup but everything seemed to be going well until this happened.

c:\miniadb_inc>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.014s]
writing 'unlocktoken'... FAILED (remote: not allowed)
finished. total time: 0.016s

So...Um...now what?:o
 
ml4179 said:
New problem. I apparently ok'd an OTA update. Phone rebooted then stopped at an icon of a phone with a red triangle/exclamation point. Pulled the batter, rebooted no problem. I tried to boot in to Clockwork Recovery from HBOOT.... same red triangle icon. Can't seem to re-flash the recovery because of the change to HBOOT. Is there an easier way to get Recovery back without going back through the downgrade?
Click to expand...

Look at Scotty so reply to my problem is had sounds the same
 
Nickynick said:
Could someone post some flashable camera lib files still can't get it to come on I'm running cyanogen 7 thanks
Click to expand...
Can't get the camera to start up? You can just reflash CM over top itself, it will reinstall the lib files.

If that doesn't work, you may just need a fresh install.

Or you can pull the lib files right out of the zipped up rom and flash them.
http://download.cyanogenmod.com/?type=stable&device=inc
 
Ebenezum said:
Ok, did as you said. There was no popup but everything seemed to be going well until this happened.

c:\miniadb_inc>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.014s]
writing 'unlocktoken'... FAILED (remote: not allowed)
finished. total time: 0.016s

So...Um...now what?:o
Click to expand...

arent you allready unlocked and have clockwork installed? why are you unlocking again? are you still on step 4?

edit:

if youre getting that error on step 5,make sure you are in fastboot. hboot will reply with a serial number to fastboot devices but not let you flash the unlock token.
 
ml4179 said:
I'm not sure where to go besides back to the beginning. Can't flash clockwork recovery over to reload Superuser. Any idea where to start otherwise?
Click to expand...

why cannot you flash clockwork? did you go to the link sdraw provided? there is no reason you cant flash clockwork as a PB31IMG file if youre still s-off.

some greater detail and explanation of the trouble you are having may help us help you.
 
Ok, I've made some progress. Got re-rooted with unrevoked and got superuser back and got clockwork recovery reloaded. Somehow I am stuck on version 4.06.605.3, I tried reflashing the 4.06.605.2 but it won't take. Phone appears to be working, but the weird thing is that the "Market" hasn't updated to Google Play (in hours) which make me think something is wrong. Ideas?
 
scotty85 said:
why cannot you flash clockwork? did you go to the link sdraw provided? there is no reason you cant flash clockwork as a PB31IMG file if youre still s-off.

some greater detail and explanation of the trouble you are having may help us help you.
Click to expand...

Sdraw posted a link for another user with camera problems in CM7. I'm not using CM
 
Definitely in Fastboot at step 5.

Now it says:


c:\miniadb_inc>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... FAILED (command write failed (No such file or
directory))
finished. total time: 0.001s

c:\miniadb_inc>

I tried the same command again and got this:

c:\miniadb_inc>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.014s]
writing 'unlocktoken'... FAILED (remote: not allowed)
finished. total time: 0.016s


Did I miss something? I thought I put it in the miniadb_inc folder. Should it be somewhere else? Perhaps something I hadn't considered?

Ok, found out I have a faulty usb cord. Trying again now, will let you know the result. I will say this step is taking a while though.

Alright. After switching cords and trying again I still get the remote: not allowed error when I try to unlock.
 
ml4179 said:
Sdraw posted a link for another user with camera problems in CM7. I'm not using CM
Click to expand...
he posted this in repsonse to your prollem:

sdrawkcab25 said:
Does you hboot say that you at s-off? If it does, can do this:
http://androidforums.com/incredible...egain-root-s-off-htc-unlocked-bootloader.html
Click to expand...

if you have clockwork back,i would suggest just flashing a custom rom,and stop messing with factory RUUs.

it is normal for the market to have updated itself that quickly :)
 
Ebenezum said:
Definitely in Fastboot at step 5.

Now it says:


c:\miniadb_inc>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... FAILED (command write failed (No such file or
directory))
finished. total time: 0.001s

c:\miniadb_inc>

I tried the same command again and got this:

c:\miniadb_inc>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.014s]
writing 'unlocktoken'... FAILED (remote: not allowed)
finished. total time: 0.016s


Did I miss something? I thought I put it in the miniadb_inc folder. Should it be somewhere else? Perhaps something I hadn't considered?

Ok, found out I have a faulty usb cord. Trying again now, will let you know the result. I will say this step is taking a while though.
Click to expand...

faulty cable could do it.

do you still have the locked hboot that you started with? what version is it?
 
Sorry, I missed that. It's basically what I ended up doing. I tried CM7 for a while and wasn't happy. What would you recommend?
 
On that boot screen similar to that in the pictures you posted it says:

Incredible xc ship s-off
hboot-0.92.0000
microp-0417
touch panel-atmel224_16ab
radio-2.1510.12.20
jul 23 2010, 18:06:51

fastboot usb

<vol up> to previous item
<vol down> to next item
<power> to select item

bootloader
reboot
reboot bootloader
powerdown

I hope I didn't put up sensitive information just now. :p
 
ml4179 said:
Sorry, I missed that. It's basically what I ended up doing. I tried CM7 for a while and wasn't happy. What would you recommend?
Click to expand...
my inc hasnt been my daily driver for some time,so im pretty out of touch with what roms are available. i personally prefer AOSP,so i would run cm7,or check out some of the AOPS ICS roms :D

if you look on xda,im sure you can find a rom based on the lates OTA that incorporates the low space fixes:
Droid Incredible Android Development - xda-developers

Ebenezum said:
On that boot screen similar to that in the pictures you posted it says:

Incredible xc ship s-off
hboot-0.92.0000
microp-0417
touch panel-atmel224_16ab
radio-2.1510.12.20
jul 23 2010, 18:06:51

fastboot usb

<vol up> to previous item
<vol down> to next item
<power> to select item

bootloader
reboot
reboot bootloader
powerdown

I hope I didn't put up sensitive information just now. :p
Click to expand...

well the good news is that i know why its not working :)

apparently you were s-off when you started the process,and as such,the froyo downgrade overwrote the htcdev hboot with .92,wich is not compatible.

since you are s-off,you dont need to flash the unlock token(nor did you actually need to do this process at all :eek:)

you also,can use the directions from this link to install clockwork as a PB31IMG: http://androidforums.com/incredible...egain-root-s-off-htc-unlocked-bootloader.html

once you have clockwork back,you can install a custom rom of choice(you prolly dont really want to bother flashing the root files on stock froyo :eek:),and then go ahead and update your radio back to the latest :)
 
ml4179 said:
Ok, I've made some progress. Got re-rooted with unrevoked and got superuser back and got clockwork recovery reloaded. Somehow I am stuck on version 4.06.605.3, I tried reflashing the 4.06.605.2 but it won't take. Phone appears to be working, but the weird thing is that the "Market" hasn't updated to Google Play (in hours) which make me think something is wrong. Ideas?
Click to expand...

This rom has the latest software baked in:
http://forum.xda-developers.com/showthread.php?t=1737398
 
sdrawkcab25 said:
Can't get the camera to start up? You can just reflash CM over top itself, it will reinstall the lib files.

If that doesn't work, you may just need a fresh install.

Or you can pull the lib files right out of the zipped up rom and flash them.
CyanogenMod Downloads
Click to expand...

well i couldnt get the camera to startup ever since an update from htc it worked after one factory restore but only worked for a few photos... im convinced its a firmware issue not hardware but you never know.

i hate to be a pest but im not 100% sure on the way to go about flashing the lib files ...in hboot? or just with superuser access while its on?
 
You must log in or register to reply here.
Back
Top Bottom