-
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
- Thread starter scotty85
- Start date
-
- Tags
- htc droid incredible
I should also add, I updated to 4.08.605.2 using an RUU I found for it somewhere online. It worked fine and I'm still s-off and would also like to update to a stock 4.08.605.15 deoxed I found here:http://dinc.does-it.net/Stock_inc_4.08.605.15_deodexed.zip
So, how can I get back into my recovery, (in order to reflash it? and reflash the superuser, as you said, unless I'm missing something) and then, ultimately, flash the 4.08.605.15 that I found?
So, how can I get back into my recovery, (in order to reflash it? and reflash the superuser, as you said, unless I'm missing something) and then, ultimately, flash the 4.08.605.15 that I found?
sdrawkcab25
Extreme Android User
Just going to do this:
http://androidforums.com/incredible...egain-root-s-off-htc-unlocked-bootloader.html
hmm is you cant mount your sd,you may have bigger prollems.id start with the easiest to fix,and maybe try a different sd. also,do a full format in the PC to FAT32
im assuming you used the newest unrevoked... if so,try this older one: 322_reflash_package.exe
it has been know to work with this same wierd combo(froyo build/baseband,1.02 hboot)
Schnap. Just figured this out and now have achieved S-OFF!
This thread really helped with my mounting problems: [RECOVERY][18.06.2012] ClockWorkMod Recovery 5.5.0.4 - "v1.5" - Page 39 - xda-developers
For whatever reason, the etc/recovery.fstab file doesn't point to valid mount points on my device. For example, when in Recovery, if I shell into adb using adb shell, here's what recovery.fstab thinks are valid mountpoints:
Code:
~ # cat /etc/recovery.fstab
cat /etc/recovery.fstab
# mount point fstype device [device2]
/misc mtd misc
/recovery mtd recovery
/boot mtd boot
/system yaffs2 system
/datadata yaffs2 datadata
/data ext4 /dev/block/mmcblk0p1 NULL ext3
/cache ext4 /dev/block/mmcblk0p2 NULL ext3
/emmc vfat /dev/block/mmcblk0p3
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/sd-ext ext4 /dev/block/mmcblk1p2 NULL ext3However, when I look at my partitions, some of these mountpoints don't exist. (notice there's no mmcblk1p1):
Code:
~ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
31 0 640 mtdblock0
31 1 4608 mtdblock1
31 2 3072 mtdblock2
31 3 253952 mtdblock3
31 4 640 mtdblock4
31 5 40960 mtdblock5
31 6 152576 mtdblock6
179 0 15558144 mmcblk0In fact, my sdcard is actually located at mmcblko. So, if I shell into adb and just try to mount sdcard per what's in fstab, it fails:
Code:
~ # mount sdcard
mount sdcard
mount: mounting /dev/block/mmcblk1p1 on /sdcard failed: No such file or directoryThe same is true for /cache, /data, and /datadata - all the mountpoints are incorrect. However, if I mount these myself while in Recovery, they work:
Code:
# mount /dev/block/mtdblock5 /cache
# mount /dev/block/mmcblk0p1 /sdcard
# mount /dev/block/mtdblock6 /data
# mount /dev/block/mtdblock6 /datadataAnd, of course, now Recovery works! I can take backups, I can install zips from sdcard, etc.
It's not clear to me why I have this problem. I may just edit the recovery.fstab and replace it...
Anyways, problem solved. After I correctly mounted /sdcard, I was able to install unrevoked-forever.zip from your guide and now I have S-OFF!
Hopefully some other folks will find this thread and be helped by it as well.
This won't work on my Inc. I unlocked using HTCDev but it won't flash the CWM recovery.
Can anybody help me?
Same thing happened to me. I solved it by going back and (repeating) reflashing CWM recover. From then on, everything worked as expected.
scotty85
Extreme Android User
that is great info! thanks a bunch for sharing your findings.
yup... that will do it
sdrawkcab25
Extreme Android User
Yup, install this:
[ROM] Stock rooted OTA 4.08.605.15 - 06-27-2012 - xda-developers
By using these instructions:
http://androidforums.com/incredible-all-things-root/521423-how-flash-roms.html
Please help! I'm having a problem I haven't seen anyone else run into yet.
I'm on step 4 trying to downgrade to froyo, and my phone appears to have frozen after trying to flash it with the PB31IMG.zip. I followed all the instructions like so:
Command Prompt has been "waiting for device" for almost an hour now, and the phone hasn't changed from the HTC logo in that time. I'm terrified to unplug or close anything. I have very carefully followed all these instructions so far. Is this unusual? Is it safe to unplug the phone and restart step 4?
Please help! I'm leaving my phone plugged into my computer until I get a response.
I'm on step 4 trying to downgrade to froyo, and my phone appears to have frozen after trying to flash it with the PB31IMG.zip. I followed all the instructions like so:
Command Prompt has been "waiting for device" for almost an hour now, and the phone hasn't changed from the HTC logo in that time. I'm terrified to unplug or close anything. I have very carefully followed all these instructions so far. Is this unusual? Is it safe to unplug the phone and restart step 4?
Please help! I'm leaving my phone plugged into my computer until I get a response.
scotty85
Extreme Android User
Please help! I'm having a problem I haven't seen anyone else run into yet.
I'm on step 4 trying to downgrade to froyo, and my phone appears to have frozen after trying to flash it with the PB31IMG.zip. I followed all the instructions like so:
Command Prompt has been "waiting for device" for almost an hour now, and the phone hasn't changed from the HTC logo in that time. I'm terrified to unplug or close anything. I have very carefully followed all these instructions so far. Is this unusual? Is it safe to unplug the phone and restart step 4?
Please help! I'm leaving my phone plugged into my computer until I get a response.
yes,its perfectly safe to unplug the phone. you can try moving the plug to different ports and see if it picks it up. ive seen that happen,i have no idea why. usually when i see it,its when i erase cache after placing the phone in ruu mode.
you can pull the battery,boot to hboot,then select fastboot from the hboot menu and try again.
at this point the phone is not flashing anything,so unplugging will not hurt it.
ERROR encountered in step 4- CANNOT WRITE TO data/local/
sharing a problem i encountered + solution i found
htc incredible 1
i was able to follow scotty85's instructions all the way thru to yield a rooted incredible1 with s-off.
1st - thanks scotty85 for an awesome post. everything went perfectly smoothly with one minor hiccup (for me)... chapter 4...
4)rewrite the misc image with adb and downgrade to froyo
this step>
adb push flash_image /data/local/
adb push mtd0.img /sdcard/
the command console returned me an error saying it could not write to /data/local/ because it was "read only" (that's not verbatim, but it's close)
thank goodness i had some past experience with chmod permissions. And you gave the the hint to the solution, Scotty. My solution was to change directories to "data" on the htc and chmod the data/local/ directory to 0755
how to:
1) open command prompt terminal window and navigate to miniadb directory. for me it was:
cd c:\miniadb_inc
then check the devices adb devices
it returns my device serial number.
next, go into adb shell
type 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.
then type cd /data/
this puts you in your phone's data directory.
then change the mode of the /local/ directory to allow the user (you) to read, write, and execute.
type chmod 0755 local
it will repeat that back to you if successful.
now type exit (then hit return)
one or two times til you get out of adb shell and back to c:\miniadb_inc
check the connection again. type adb devices
if it returns your device serial number,
you can resume your progress thru step 4. picking up where it failed earlier:
adb push flash_image /data/local/
adb push mtd0.img /sdcard/
best wishes to all. & thanks scotty85 for an excellent tutorial.
sharing a problem i encountered + solution i found
htc incredible 1
i was able to follow scotty85's instructions all the way thru to yield a rooted incredible1 with s-off.
1st - thanks scotty85 for an awesome post. everything went perfectly smoothly with one minor hiccup (for me)... chapter 4...
4)rewrite the misc image with adb and downgrade to froyo
this step>
adb push flash_image /data/local/
adb push mtd0.img /sdcard/
the command console returned me an error saying it could not write to /data/local/ because it was "read only" (that's not verbatim, but it's close)
thank goodness i had some past experience with chmod permissions. And you gave the the hint to the solution, Scotty. My solution was to change directories to "data" on the htc and chmod the data/local/ directory to 0755
how to:
1) open command prompt terminal window and navigate to miniadb directory. for me it was:
cd c:\miniadb_inc
then check the devices adb devices
it returns my device serial number.
next, go into adb shell
type 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.
then type cd /data/
this puts you in your phone's data directory.
then change the mode of the /local/ directory to allow the user (you) to read, write, and execute.
type chmod 0755 local
it will repeat that back to you if successful.
now type exit (then hit return)
one or two times til you get out of adb shell and back to c:\miniadb_inc
check the connection again. type adb devices
if it returns your device serial number,
you can resume your progress thru step 4. picking up where it failed earlier:
adb push flash_image /data/local/
adb push mtd0.img /sdcard/
best wishes to all. & thanks scotty85 for an excellent tutorial.
preacherzson
Lurker
Having difficulty at Step 4:
after pasting the ./flash_image misc /sdcabrd/mtd0.img command into adb shell, it returns the following result: cd: bad substitution
I re-ran step 4 up to that point and got the same result. I also checked the SD card and the mtd0.img file is on it. What am I doing wrong / what does that prompt communicate?
Thanks
after pasting the ./flash_image misc /sdcabrd/mtd0.img command into adb shell, it returns the following result: cd: bad substitution
I re-ran step 4 up to that point and got the same result. I also checked the SD card and the mtd0.img file is on it. What am I doing wrong / what does that prompt communicate?
Thanks
gbiggie
La patience et le pardon
gbiggie
La patience et le pardon
Not sure exactly-I've run into the problem before with a few different devices. Lets just say the left port on my laptop is phone friendly:thumbup:
Glad it works for you now
