Database Users

Eris Recover Missing?

OK so I downloaded the original 2.1 leak.
It changed the boot loader (I believe that's the reason after the 2.1 update why people weren't able to rollback to 1.5, yes I know 2.1 rooted rom's can roll back now) and then installed 2.1 OTA "official"... guess it was the second attempt at 2.1 since VZW canned the first test ROM.
Anyway... so now I am running the latest OTA non-root ROM and if I hit power + volume up to enter recovery mode (or install other ROMs like EvilEris1.1.zip, Legend.zip) I get an Exclamation point.
Hitting Power and Volume down gets me into hboot where I could install the PB00IMG.zip (it checks for a few other names like this as well).
Is there anyway to restore that recovery functionality?
Also, which I am assuming because I'm running non-root ROM, when trying to use adb I cannot run "adb root", "adb mount", or "adb shell" and remount /system as rw. Complains can't do this because it's official rom?
Any help here getting me to the point that I can recover if necessary, install EvilEris, Legend, etc for testing purposes, even recover to rollback and start all over... would be greatly appreciated.
Thanks
Chris

nemish13 said:
OK so I downloaded the original 2.1 leak.
It changed the boot loader (I believe that's the reason after the 2.1 update why people weren't able to rollback to 1.5, yes I know 2.1 rooted rom's can roll back now) and then installed 2.1 OTA "official"... guess it was the second attempt at 2.1 since VZW canned the first test ROM.
Anyway... so now I am running the latest OTA non-root ROM and if I hit power + volume up to enter recovery mode (or install other ROMs like EvilEris1.1.zip, Legend.zip) I get an Exclamation point.
Hitting Power and Volume down gets me into hboot where I could install the PB00IMG.zip (it checks for a few other names like this as well).
Is there anyway to restore that recovery functionality?
Also, which I am assuming because I'm running non-root ROM, when trying to use adb I cannot run "adb root", "adb mount", or "adb shell" and remount /system as rw. Complains can't do this because it's official rom?
Any help here getting me to the point that I can recover if necessary, install EvilEris, Legend, etc for testing purposes, even recover to rollback and start all over... would be greatly appreciated.
Thanks
Chris
Click to expand...
Click to collapse
it sounds like you installed an official non root image over root, replacing everything including the recovery img. We have no current way of rooting your phone.

Nope,
As I said I have downloaded and installed the following
Beginning of March --
HTC 2.1 Leak Rom
Verizon test rom, REJECTED. Do not Install if you want root.
Rom: http://www.sendspace.com/file/frqze0
March 30 Installed --
HTC 2.1 Release Candidate (AKA OTA) Leak Rom
Verizon test rom, possible OTA leak. Do not Install if you want root.
http://www.megaupload.com/?d=RHNAWUR0
Never downloaded or installed any other ROM. Never installed a root ROM.

nemish13 said:
Nope,
As I said I have downloaded and installed the following
Beginning of March --
HTC 2.1 Leak Rom
Verizon test rom, REJECTED. Do not Install if you want root.
Rom: http://www.sendspace.com/file/frqze0
March 30 Installed --
HTC 2.1 Release Candidate (AKA OTA) Leak Rom
Verizon test rom, possible OTA leak. Do not Install if you want root.
http://www.megaupload.com/?d=RHNAWUR0
Never downloaded or installed any other ROM. Never installed a root ROM.
Click to expand...
Click to collapse
sorry dude

well, you are not going to be able to install other roms since you do not have root. i believe you should be able to get into recovery, but only able to do basic functions such as data/wipe. you wont be able to install new roms via recovery. the only real function you will have is to go into hboot and flash the current build version or a higher build version of the pb00img.zip file.
like jcase said, there is no way to root your phone, unless you have the official build version 1.5.

ECLIPS3 said:
well, you are not going to be able to install other roms since you do not have root. i believe you should be able to get into recovery, but only able to do basic functions such as data/wipe. you wont be able to install new roms via recovery. the only real function you will have is to go into hboot and flash the current build version or a higher build version of the pb00img.zip file.
like jcase said, there is no way to root your phone, unless you have the official build version 1.5.
Click to expand...
Click to collapse
I can do hboot (Power + Volume Down) but I can't do recovery at all (Power + Volume Up). Just get Exclamation Point.
So one of these Verizon Test Roms erased the "stock" recovery mode as it is no longer there and there is no way I can figure out how to restore that, forget a modified recovery.

just a question , what if someone backed up the files off the card to their computer or somewhere? i was just wondering cuz a lot i have been readin , people have downloaded the wrong file and lost root .if they have it backed up ,couldnt they just replace the files on the card with the ones saved and be able to do a recovery? i dont know much about how this works so dont rip me to bad lol just asking

HTC?!?!?!?
So someone from HTC needs to post a signed "su enabled" ROM...
Hello? HTC employees... help here like you did for the 1.5 "su enabled" leak that got us root... PLEASE!!!

nemish13 said:
So someone from HTC needs to post a signed "su enabled" ROM...
Hello? HTC employees... help here like you did for the 1.5 "su enabled" leak that got us root... PLEASE!!!
Click to expand...
Click to collapse
Doubtful it will happen for the eris again.

jcase said:
Doubtful it will happen for the eris again.
Click to expand...
Click to collapse
yeah but we can hope here... someone working for HTC has to be nice enough to take the OTA, enable root, sign it (most important) and post it...
I can't think people at HTC wouldn't share if they had the ability to help the community out now... LOL

More than likely only a hand full of people have the ability to sign the roms. We didn't get a release rom with root, we got a engineering rom.
Odds are in the favor or a root exploit, go see what Paul O'Brian has done with the HTD Desire and Legend . Hopefully that can help us.

Rooting OTB 2.1 Eris

I have now Rooted Two 2.1 Eris the last few days. I dont know if this has been covered, I did a search and honestly searching here is a little fetch.
This is a place holder.
POST here if you want to know how to root 2.1 or post here and let me know if its already been known how to root.
Here is the Phone Information and Specs of the one i just rooted.
Firmware Version
2.1
Baseband
2.42.00.04.12
Kernel Verison
2.6.29-8a03cb9a
[email protected] #1
Build Number
2.36.605.1 CL165907 Release-keys
Software Number
2.36.605.1
Browser Version
WebKit 3.1
PRL Version
58005
ERI Version
5

Were the specs like this before or after the rooting?

After the root.
I should have got the specs before the root. I can tell you how to do it if you have a 2.1 its fast.
I just want someone on here to verify it.

Sure why not.

Just post how to do it instead of trying to drag on a thread and make yourself big, I honestly dont think you did root them or you would of posted a tutorial. prove me wrong... go for it.

FireSokar said:
Just post how to do it instead of trying to drag on a thread and make yourself big, I honestly dont think you did root them or you would of posted a tutorial. prove me wrong... go for it.
Click to expand...
Click to collapse
Yeah honestly I'm with this guy ^.

Trust me i dont need to make myself big on xda i could care less.
Heres what I have been doing on them, push the 1.5 root to the phone reboot recovery install like you would root on 1.5 It should complete.
You will notice when it reboots that YOU DO NOT HAVE SUPER USER.
What i did was went to my cmd prompt typed adb shell, i have #. So i proceeded with installing recovery.
Once installing the new recovery i adb reboot recovery again. This time you get the green letters with the recovery, I installed the offical2.1with root over the OTB 2.1 with root. Pretty much you could install any rom with root on it.
Wiped and rebooted. Now i have 2.1 with superuser and root.

amoamare said:
Trust me i dont need to make myself big on xda i could care less.
Heres what I have been doing on them, push the 1.5 root to the phone reboot recovery install like you would root on 1.5 It should complete.
You will notice when it reboots that YOU DO NOT HAVE SUPER USER.
What i did was went to my cmd prompt typed adb shell, i have #. So i proceeded with installing recovery.
Once installing the new recovery i adb reboot recovery again. This time you get the green letters with the recovery, I installed the offical2.1with root over the OTB 2.1 with root. Pretty much you could install any rom with root on it.
Wiped and rebooted. Now i have 2.1 with superuser and root.
Click to expand...
Click to collapse
Correct me if I'm wrong but by 1.5 root you mean the 1.5 to 2.1 rooted update and that only works for phones running 1.5 which we already had. Now there trying to get root for the 2.1 leaks/ota. not to mention i think the 1.5 root was a PB00IMG.zip which is not for recovery.

Okay so I initially didnt think i would have to spell this out.
Push PB00IMG.zip to root of the SDCARD on a 2.1 OTB eris.
Adb reboot recovery apply the PB00IMG.zip
Wait for complete and reboot phone.
When the phone boots up you WILL NOT HAVE THE SUPERUSER installed. Instead if you go to your cmd prompt and type adb shell you get the # < then install the recovery-RA-eris-v1.6.2.img and flash image as usual.
Reboot recovery this time you get the Green Letters Recovery.

amoamare said:
Okay so I initially didnt think i would have to spell this out.
Push PB00IMG.zip to root of the SDCARD on a 2.1 OTB eris.
Adb reboot recovery apply the PB00IMG.zip
Wait for complete and reboot phone.
When the phone boots up you WILL NOT HAVE THE SUPERUSER installed. Instead if you go to your cmd prompt and type adb shell you get the # < then install the recovery-RA-eris-v1.6.2.img and flash image as usual.
Reboot recovery this time you get the Green Letters Recovery.
Click to expand...
Click to collapse
I would like it if you spelled it out even more. I am not familiar with all the ADB shell commands, so could you list the exact command for each step? That would help me out greatly, thanks!

AcidRoot said:
Correct me if I'm wrong but by 1.5 root you mean the 1.5 to 2.1 rooted update and that only works for phones running 1.5 which we already had. Now there trying to get root for the 2.1 leaks/ota. not to mention i think the 1.5 root was a PB00IMG.zip which is not for recovery.
Click to expand...
Click to collapse
He is trying to tell you that he has the old root method working on 2.1.
I know that he has done this on two devices. One fresh out the box with 2.1 and one that was updated to 2.1.
I am looking for a 2.1 Eris myself to duplicate.
I personally remember having a problem loading the root file on a 2.1 Eris, but I only tried one of them. Then I left it alone.
I think I gave up too easy when I was told that it could not be done with that file.

Exactly I was told it could not be done.
What happend was the one out of box I ended up launching the Root with out checking if it was 1.5 or 2.1 When the phone wouldnt reboot after trying to root i wiped the handset. It loaded after some time like 15 mins. I looked for the Superuser program and it wasnt installed.
Ended up checking software version it was 2.1. A little fustrated I ran my script for cricket WITCH REQUIRES ROOT.
It rebooted the phone and what did i notice my **** was on the phone without root. So i thought. I check adb shell and i got the #. So i hit up installing recovery and i was able to install it so i install the official 2.1 with root rom to get the superuser apk on the phone.

amoamare said:
Exactly I was told it could not be done.
What happend was the one out of box I ended up launching the Root with out checking if it was 1.5 or 2.1 When the phone wouldnt reboot after trying to root i wiped the handset. It loaded after some time like 15 mins. I looked for the Superuser program and it wasnt installed.
Ended up checking software version it was 2.1. A little fustrated I ran my script for cricket WITCH REQUIRES ROOT.
It rebooted the phone and what did i notice my **** was on the phone without root. So i thought. I check adb shell and i got the #. So i hit up installing recovery and i was able to install it so i install the official 2.1 with root rom to get the superuser apk on the phone.
Click to expand...
Click to collapse
version 1.47 or 1.49?

amoamare said:
Exactly I was told it could not be done.
What happend was the one out of box I ended up launching the Root with out checking if it was 1.5 or 2.1 When the phone wouldnt reboot after trying to root i wiped the handset. It loaded after some time like 15 mins. I looked for the Superuser program and it wasnt installed.
Ended up checking software version it was 2.1. A little fustrated I ran my script for cricket WITCH REQUIRES ROOT.
It rebooted the phone and what did i notice my **** was on the phone without root. So i thought. I check adb shell and i got the #. So i hit up installing recovery and i was able to install it so i install the official 2.1 with root rom to get the superuser apk on the phone.
Click to expand...
Click to collapse
What was the boot screen like? The Green Android people that wave at you or the HTC "quietly brilliant" screen

Holy **** It works!

I dont remember boot screen.
as far as version 1.47 or 1.49
Im not sure what your asking here, version of the PBIMG i used ?

amoamare said:
I dont remember boot screen.
as far as version 1.47 or 1.49
Im not sure what your asking here, version of the PBIMG i used ?
Click to expand...
Click to collapse
No when you took the phone out of the box and started it for the first time after the green androids on skate boards did little green android guys wave or did you get the htc quietly brillant

amoamare said:
I dont remember boot screen.
as far as version 1.47 or 1.49
Im not sure what your asking here, version of the PBIMG i used ?
Click to expand...
Click to collapse
HBOOT version I believe.

PusherRobot said:
Holy **** It works!
Click to expand...
Click to collapse
Hey man, what are the commands you used? I pushed PB00IMG.zip to the sdcard, but when I do > adb reboot recovery , it simply restarts and shows that phone icon with the red triangle over it. When I manually pressed power and volume down, the same error as always occurs (version is older). What am I doing wrong?

amoamare said:
I dont remember boot screen.
as far as version 1.47 or 1.49
Im not sure what your asking here, version of the PBIMG i used ?
Click to expand...
Click to collapse
Well congratulations, you found a bass ackwards way to root a phone with a (more than likely) 1.47 bootloader. We've had it for months, welcome to the party. Although, You're a little late...

trying to root the OTA 2.2 upgrade

so i accidentally installed the 2.2 OTA and it got rid of my root and everything and to my understanding you cant root the OTA 2.2...am i totally screwed or is there away to downgrade some how or something and get root back

Screwed for now anyway until they find a hole. You'll need patience for a bit. I'm assuming you didn't install unrevoked forever?

egobuster1 said:
so i accidentally installed the 2.2 OTA and it got rid of my root and everything and to my understanding you cant root the OTA 2.2...am i totally screwed or is there away to downgrade some how or something and get root back
Click to expand...
Click to collapse
No you are not. I did the same thing. You can downgrade your phone and then root and S-OFF it. Once this is done, you can upgrade to 2.2 and then root the phone. Check my post: http://forum.xda-developers.com/showthread.php?t=771178
This will give you the steps and links to follow. Enjoy.

I went to the link above, and tried condition five but I got stuck at step 18-19, When I re-enter adb shell I dont have root, I still have $ not #. Has anyone else had trouble or done this yet? Im running Ubuntu if that makes a difference

adb shell
cd /data/local/tmp
chmod 0755 /data/local/tmp/rageagainstthecage-arm5.bin
cd /data/local
chmod 0755 /data/local/flash_image
cd /data/local/tmp
./rageagainstthecage-arm5.bin
This worked

just followed all the steps i thought and everything went well got the # sign instead og hte $ sign and everything and when i restarded it for it to load the PB21img file once it did that it erroed and said the main version is older udate fail..not sure what to do

egobuster1 said:
just followed all the steps i thought and everything went well got the # sign instead og hte $ sign and everything and when i restarded it for it to load the PB21img file once it did that it erroed and said the main version is older udate fail..not sure what to do
Click to expand...
Click to collapse
What steps are you refering to?

dalepl said:
What steps are you refering to?
Click to expand...
Click to collapse
i followed condition #5 and everything seemed to go as plan until the reboot then it gave a error. im gonna download a older RUU off the the site and see if maybe thats the problem but i dont know what else to do if not
also in the instructions it says to push pc31img and i think its supposed to be pb31img

egobuster1 said:
i followed condition #5 and everything seemed to go as plan until the reboot then it gave a error. im gonna download a older RUU off the the site and see if maybe thats the problem but i dont know what else to do if not
also in the instructions it says to push pc31img and i think its supposed to be pb31img
Click to expand...
Click to collapse
Thanks, will update.

egobuster1 said:
i followed condition #5 and everything seemed to go as plan until the reboot then it gave a error. im gonna download a older RUU off the the site and see if maybe thats the problem but i dont know what else to do if not
also in the instructions it says to push pc31img and i think its supposed to be pb31img
Click to expand...
Click to collapse
What error did you get? Did HBoot load the image?

egobuster1 said:
i followed condition #5 and everything seemed to go as plan until the reboot then it gave a error. im gonna download a older RUU off the the site and see if maybe thats the problem but i dont know what else to do if not
also in the instructions it says to push pc31img and i think its supposed to be pb31img
Click to expand...
Click to collapse
I used this RUU to extract the ROM.
RUU_IncredibleC_Verizon_WWE_1.22.605.2_Radio_1.00.03.04.06_hboot_0.79_release_161494_NoDriver_0514
You can get it here: http://www.shipped-roms.com/shipped/Incredible/RUU_IncredibleC_Verizon_WWE_1.22.605.2_Radio_1.00.03.04.06_hboot_0.79_release_161494_NoDriver_0514.exe

dalepl said:
What error did you get? Did HBoot load the image?
Click to expand...
Click to collapse
no it started to proccess through like it was going to and then said error the image is to old or something what ever it says if you just try and load the img with out having root access

i got the same error, main version is older! i tried rom.zip from all 4 RUU. i think we need to revert to an older hboot but i have no clue how to do that without root.

ya i think we need a older Hboot also but like you stated im lost as of how to do it

yep tried again with a different RUU and got the error main version is older.
not sure if there is a fix or what to do for this

Help Help Help...SOS..Permissions Issues

Hello,
I am having real problems with my phone. I was trying to root the phone and I am stuck. I have S=off on the HBOOT screen, android version 2.2, software version 1.14.531.1.
I am not able to perform Visionary temp root, can't load clockwork recovery, and can't install Busybox. When I try SU within terminal, I get the error "must be suid to work properly".
When I try to install Busybox, I get the error "The application failed either becasue you device is not NAND unlocked or we were unable to remount".
I cant install ClockWork recovery..I get the error "an error occured while trying to run privilidged commands"
I have tried everything which is probably why I am stuck. I tried to force the update to 2.2.1 but won't work. The phone goes thru the motions of updating boot, radio, etc...However, still the same results are its done. THe phone stays on 2.2.
I have tried doing all of the root methods avail: Using Visonary, rage, etc... None of them will work.
Can anybody offer me advice to get root back so I can 1. install a recovery and then install another rom? I need a way to basically put the phone back to factory installed software and start fresh.

Try this worked perfectly for me. also make sure you have ADB installed and working properly before attempting root.
http://forum.xda-developers.com/showthread.php?t=858996

lancer123 said:
Hello,
I am having real problems with my phone. I was trying to root the phone and I am stuck. I have S=off on the HBOOT screen, android version 2.2, software version 1.14.531.1.
I am not able to perform Visionary temp root, can't load clockwork recovery, and can't install Busybox. When I try SU within terminal, I get the error "must be suid to work properly".
When I try to install Busybox, I get the error "The application failed either becasue you device is not NAND unlocked or we were unable to remount".
I cant install ClockWork recovery..I get the error "an error occured while trying to run privilidged commands"
I have tried everything which is probably why I am stuck. I tried to force the update to 2.2.1 but won't work. The phone goes thru the motions of updating boot, radio, etc...However, still the same results are its done. THe phone stays on 2.2.
I have tried doing all of the root methods avail: Using Visonary, rage, etc... None of them will work.
Can anybody offer me advice to get root back so I can 1. install a recovery and then install another rom? I need a way to basically put the phone back to factory installed software and start fresh.
Click to expand...
Click to collapse
if you want to go back to stock follow the downgrade thread (linked in the thread about forcing the update) then follow the one linked above me here... it's faster than my forcing the update method (once you get radio s-off and the eng boot loader you can actually just flash the update.zip from my thread....)
EDIT: and in the future please post in the proper section or reply in the thread of the guide you're having problems with.

Thank you for trying to quickly help me. I started to follow the instrucions for downgrading and got stuck at the ADB Shell command. Within the Shell, I typed SU and got the following error "must be usid to work properly". Can you please offer any advice to get around this error?
Thanks,
Lance

to be suid you have to have temp or full root access. my sugestion would be to start the process from scratch. have you tried the visionary method?
i cant post the link to the other forum but its readily availible if you google it.
i didnt see the download link in the site i found so if you need the file PM me your email and ill send it back to you

Hello,
Yes, I did try Visonary and will not get SU working. The S=off is already showing. However, no matter what I do, I can't get SU to work. The device appears to be rooted but won't allow any advanced permisson comands to be used such as SU. I have tried re-installing superuser. that didn't help either.

launch the current version of SU you have on your phone and select settings scroll to the bottom of the page and under "superuser Information" you should see "Su binary Vx.x.x-xx) what is the version #?
Click on that and see if it updates the version if it does update try rebooting launch terminal and retry SU

Hello,
I checked the version of SU and did find there is an update. I tried to install and got the followng error 'An error occured and su was not updated. a zip file has been placed on your sdcard. please reboot into recovery and flash it".
The problem is that I can't get into recovery as I get the red exlimation mark. I can't find a way to install a recovery program because of permission issues.
Any further suggestions?

Please post questions in Q&A section.

Aren't you suppose to be on 2.2.1 before you start any rooting. Op=reading fail!
Sent from my HTC Glacier using XDA App

Thanks for the confirmation that I screwed up. Do you have any advice to help me fix the problem:?

lancer123 said:
Thanks for the confirmation that I screwed up. Do you have any advice to help me fix the problem:?
Click to expand...
Click to collapse
How in the first place you get the s=off. In order to get s-off you need root! Is also known that to boot into recovery thou need to try several times before its locks! The better way to deal woth it is reading! The root method in the dev section help a lot! Read, read! That's the better way to learn! If you are in eng hboot and s= off there's a possibility that you only need to reboot into recovery several times! Other than that just read with patience!
Sent from my HTC Glacier using XDA App

lancer123 said:
Thanks for the confirmation that I screwed up. Do you have any advice to help me fix the problem:?
Click to expand...
Click to collapse
My advice (without trying to hurt feelings too much) is DON'T ROOT. You obviously don't really know your way around Android too well at this point. I would familiarize yourself with everything before diving in head first.
Despite popular belief, having root does NOT in fact make you cooler.
WAAAY too many new users are trying to root because they think it's cool or heard it's cool. You need to learn your device first.

deviusdragger said:
Aren't you suppose to be on 2.2.1 before you start any rooting. Op=reading fail!
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
no... you fail

lancer123 said:
Thanks for the confirmation that I screwed up. Do you have any advice to help me fix the problem:?
Click to expand...
Click to collapse
lancer... get on IRC I will help you
EDIT: or AIM, or yahoo, msn, or gtalk.... my info is in my profile

If you have S=Off on your phone already, your best bet would be to flash Clockwork recovery through FASTBOOT.
If you are unsure of how to do this, refer to this link from the Cyanogen Wiki:
http://wiki.cyanogenmod.com/index.php?title=Fastboot
The page will point you in the right direction for everything that you need.
Have the ROM that you want to install on your SD Card because FASTBOOT will probably not allow you to directly flash all the other partitions, but it will at least allow you to flash recovery, then boot into Clockwork and Install a new ROM.

2.3.4 Latest OTA[2.77.651.8] Downgrade!!

Hey guys, so since the latest OTA, we haven't been able to downgrade nor root the shift, if we were on the latest OTA. I've been hunting through methods for downgrading and rooting, but nothing came about that actually worked. Finally having a free mind after my AP Physics exam, I got a train of though going, and tried Indirect's downgrade method, which yes, failed. What happened is when tacoroot tried to reboot the phone, it didn't have the permissions to reboot the phone, and so when the "error" on the CMD wrote that I have no permission to reboot the phone, I whipped out quick root, and did the reboots through it. Using quick root and Indirect's method of downgrading, I managed to downgrade to Android 2.2, and got to root my phone, then flash some ROMs.
Solution:
When you are in the step in Indirect's tutorial where you use the
Code:
[COLOR="Red"]adb shell sh /data/local/tmp/taco --setup[/COLOR]
command, you'll notice that tacroot doesn't have the permissions to reboot, at that time, you have to open lyriquidperfection's "HTC Quick Root v1.1.13" application and execute the reboot to recovery command through it by clicking on the drop down in reboot options, and choosing to reboot to recovery.
When you are at the step in the tutorial when you boot to hboot in order to downgrade, you can use the Quick Root application to reboot to bootloader where you flash your downgraded PG06IMG.zip.
Links:
Indirect's - Root and downgrade for Android 2.3.4
lyriquidperfection's - HTC Quick Root v1.1.13
If any clarification is needed, please post below, this is simply a quick guide to allow people to downgrade and if they choose, root it or flash a ROM. I take NO responsibility in what you do with your device nor when you void your warranty. I take NO credit for neither Indirect's method of downgrading, nor lriquidperfection's application, though I would appreciate a thanks for my compiling this "quick guide" to help you downgrade your device. If you're looking for credits on the method and application, they should be found at those posts.
Good luck,
John
*If you want to flash a rooted version of this update, go to this thread
Just keep in mind you can't flash a new ROM to your phone until you downgrade.
local.prop: permission denied resolution by CNexus: his post
For anyone else who has problems, here's what I did. if you get the message
Code:
local.prop: permission denied
After running
Code:
adb shell sh /data/local/tmp/taco --root
Then simply run the following command again (step 2 of Indirect's method)
Code:
adb shell chmod 755 /data/local/tmp/taco
The problem is that your phone resets the permissions of that directory, so it doesn't let tacoroot execute and do its thing.

Nice
Sent from my HTC Evo Shift using xda app-developers app

BigSplit said:
Nice
Sent from my HTC Evo Shift using xda app-developers app
Click to expand...
Click to collapse
Thanks, glad to see people appreciating this

Very nice, and much appreciated . Hellua nice find.

Very nice find, I would triple thanks if I could
ICS rom, here I come.
Sent from my PG06100 using xda premium

Might want to add the Software Number to the OP

indirects method for 2.3.4 wouldnt work for me on the latest ota but lyriquidperfection's - HTC Quick Root v1.1.13 method rooted like a charm. i was running completely stock 2.3.4 latest with the newest hboot and with some force and annoyance managed to somehow trick the new hboot into doing the downgrade to 2.2 and i was able to get s-off/full root again.
if i can figure out what exactly i did ill post it up for everyone but im not entirely sure. it mightve been a fluke.
all i know for sure is after i got root with lyriquidperfection's - HTC Quick Root v1.1.13
i dd the misc.img a ****load of times and then dd the eng hboot a ****load of times until it <------like 30 times in a row each lol, one after another the other.
it forced the hboot to relock the htcdev unlock and accidentally took the 2.2 downgrade (PG06IMG.zip) so i could switch hboots again.
its a helluva gamble but if anyone else has unlocked through htcdev and is willing to gamble on it have fun, if you brick it isnt my fault and i hold no responsibility over it. i think i pissed the phone off and it gave up but it worked for me. it was really a combination of using the lyriquidperfection's - HTC Quick Root v1.1.13, indirects root method, and vicodans method.

OP: so you tried my method and it failed too?

VICODAN said:
OP: so you tried my method and it failed too?
Click to expand...
Click to collapse
I believe I may have come across it. This weekend I may go back to 2.3.4 to test out some other solutions, mix and match, just to see what over all works.

JohnnyCakeXM said:
I believe I may have come across it. This weekend I may go back to 2.3.4 to test out some other solutions, mix and match, just to see what over all works.
Click to expand...
Click to collapse
yeah, i had to do a complete mashup to get my hboot to take the 2.2 downgrade, im still trying to remember how i did it and debating on taking the gamble again myself

Lol, i'm just fine with this method. Worked for me, therefore I am satisfied,

JohnnyCakeXM just a suggestion, but you may want to give a little more detail in the OP. Maybe a Step by Step .

prboy1969 said:
JohnnyCakeXM just a suggestion, but you may want to give a little more detail in the OP. Maybe a Step by Step .
Click to expand...
Click to collapse
Basically he just used a reboot app to do the needed reboots since taco couldn't and everything else is done by script
Sent from my miTouch-4G-Slide using Tapatalk 2

strapped365 said:
Basically he just used a reboot app to do the needed reboots since taco couldn't and everything else is done by script
Sent from my miTouch-4G-Slide using Tapatalk 2
Click to expand...
Click to collapse
I understand what he did . It's just I've received a few PM's asking what his steps are. So rather then explain it every time, I figured I'd give him a heads up to give a more detailed OP for the newbs.
TEAM MiK
MikROMs Since 3/13/11

Moved from THIS thread.
---
prboy1969 said:
Well I think you would've be better off posting in JohnnyCakeXM's thread. Might want to think about moving this discussion over there. But anyway. It sounds like you did not actually complete the first part of the process.
A factory Reset isn't going to do it.
Click to expand...
Click to collapse
Well thats the problem, to complete the first part, I need to get that menu to show up again, but it won't and just gives me the recovery icon
But any ideas? I was thinking of running the 2.3.4 RUU, but it may not take because of the OTA, so idk
Sent from my PG06100 using xda premium

CNexus said:
Ok, so today I got around to rooting my phone, running the latest OTA with JohnnyCakeXM's process
I ran the command that was denied "adb shell sh /data/local/tmp/taco --setup"
Gives error (expected)
Rebooted through HTC Quickroot, pressed the 3 buttons and got the "cache files" error
It gave me the "Android System Recovery <3e>" menu...but then I kinda just pulled the battery instead of selecting "Reboot system now"
Now whenever I try to go through this again to get to the "3e" menu, it just stays stuck in recovery (with the ! sign) after I press VolUp + VolDown + Power
Any help as to how to get to that menu again?
Click to expand...
Click to collapse
CNexus said:
Moved from THIS thread.
Well thats the problem, to complete the first part, I need to get that menu to show up again, but it won't and just gives me the recovery icon
But any ideas? I was thinking of running the 2.3.4 RUU, but it may not take because of the OTA, so idk
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
I do not think the 2.3.4 RUU is going to work for you. The issue I believe is that you didn't actually complete Indirects part of the method.
The command " adb shell sh /data/local/tmp/taco --setup " should have gone through before you went any further. I would try starting the whole process over again.

I'll take care of it some time tonight, or tomorrow. Just will have to re-flash stock 2.3.4 to ensure everything is in order and I'll even make a video for it. Text tutorial will come first, when it does.

prboy1969 said:
I do not think the 2.3.4 RUU is going to work for you. The issue I believe is that you didn't actually complete Indirects part of the method.
The command " adb shell sh /data/local/tmp/taco --setup " should have gone through before you went any further. I would try starting the whole process over again.
Click to expand...
Click to collapse
Thats the reason why JohnnyCakeXM posted this thread in the first place...? Because the command DOESN'T go through completely so you need to use some third party program to do the reboots for you
EDIT: Yes, I have gone through it multiple times and even checked my cables and everything to make sure that none of that was the problem before I even posted here
Sent from my PG06100 using xda premium

CNexus said:
Thats the reason why JohnnyCakeXM posted this thread in the first place...? Because the command DOESN'T go through completely so you need to use some third party program to do the reboots for you
EDIT: Yes, I have gone through it multiple times and even checked my cables and everything to make sure that none of that was the problem before I even posted here
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
What he said in the OP was :
" when tacoroot tried to reboot the phone, it didn't have the permissions to reboot the phone, and so when the "error" on the CMD wrote that I have no permission to reboot the phone, I whipped out quick root, and did the reboots through it. "
So unless I'm not reading his OP incorrectly ( which is a possibility ) , the command has to go through. But it will fail to reboot, then you use Quick Root to do the Reboots. Again this is why I suggested a Clearer Step by Step OP. So that the process can be more easily followed, and diagnosed if there is an issue . It leaves a lot less to interpretation.

prboy1969 said:
What he said in the OP was :
" when tacoroot tried to reboot the phone, it didn't have the permissions to reboot the phone, and so when the "error" on the CMD wrote that I have no permission to reboot the phone, I whipped out quick root, and did the reboots through it. "
So unless I'm not reading his OP incorrectly ( which is a possibility ) , the command has to go through. But it will fail to reboot, then you use Quick Root to do the Reboots. Again this is why I suggested a Clearer Step by Step OP. So that the process can be more easily followed, and diagnosed if there is an issue . It leaves a lot less to interpretation.
Click to expand...
Click to collapse
Yes, I ran tacoroot --setup, waited for the error, and then rebooted through Quickroot
I think I said this in my original post in the other thread..?
Sent from my PG06100 using xda premium