Froyo Root - Droid Incredible General

Is there any word when the unrevoked team will release a version of unrevoked that will work on Froyo? I messed up and loaded the OTA RUU and did not unrevoke forever before doing this. I have tried downgrading back to 2.1, but have had no luck. Every time I launch the RUU, the phone disconnect, so the RUU cannot read the phone. When I close the RUU, the phone reconnects.
If anyone has a fix for this, then maybe I can downgrade to 2.1 and then do the update correctly. Otherwise, I will have to wait on the unrevoked team.
Thanks
Sent from my ADR6300 using XDA App

Just put this on the root of your SD card as PB31IMG.zip, boot into hboot, and hope it doesn't complain about the radio version. Then use unrevoked3 for clockwork, unrevoked forever for s-off, and re-flash the RUU.

If this is the stock 2.1, I tried it. The system rejected it because it was an earlier version. Thanks.
Sent from my ADR6300 using XDA App

This should help
http://forum.xda-developers.com/showthread.php?t=768295

What about the exploid for DX that works with Evo as well. Has anyone tried this on an OTA 2.2 Inc? It would be a bummer to have to downgrade to upgrade again.

TNS201 said:
This should help
http://forum.xda-developers.com/showthread.php?t=768295
Click to expand...
Click to collapse
TIS201. I will give this s try when I get home from work. Looks promising. Thanks. Will let you guys know how it goes.
Sent from my HTC Droid Incredible using XDA App

TNS201 said:
This should help
http://forum.xda-developers.com/showthread.php?t=768295
Click to expand...
Click to collapse
OK. I gave this a try and all looked good until I rebooted the phone. Once again the bootloader said I was trying to load an older image and would not load. So, I looked around and found some other links. In the end, what I found that in the instructions, step 6 says:
adb shell
cd /data/local/tmp
chmod 0755 /data/local/tmp/rageagainstthecage-arm5.bin
cd /data/local
chmod 0755 /data/local/flash_image
In another forum I found a difference in the instructions in that it used 777 instead of 0755. I tried this and the phone loaded the PB31IMG.zip file as it should. The only problem I then had was there was something wrong with the file and I was stuck in the bootloader. I downloaded a different image and tried again. This one also loaded and this time the phone booted just fine. I now have the phone back to stock with 2.1 Update1.
Thanks for your help. I think after I get everything back up and running, I will post the steps with the correct data. Now, to reroot the phone and this time load unrevoke forever.

Related

Main Version Is Older! Update Fail! Message

Hi,
Thanks in advance for anyone who tries to help me.
A few weeks ago I tried to gain root access to HTC Eris. I followed the prereq and part one of the guide but stopped there. Rebooted my phone, checked the version (2.1) and went about reinstalling apps and such.
Now I want to install a different ROM so I went back and tried to start from the beginning and put PB00IMG.zip on my phone, went to hboot, let run but then I get the message "Main Version is older! Update Fail! Do you want to reboot device?"
So when I move onto III in the walk through, I get an error on the command
adb push flash_image /system/bin
It would seem like I've lost root right? Is there anyway I can check to see if I accidentally installed the leak w/o root?
Thanks,
Nate
Easy way is to do
adb shell
if the prompt is
$
your likely on leak
if the prompt is
#
your on root.
Once your on root, flash recovery.
I am anticipating the next question, so here is your answer. If you did indeed root your phone, you should have loaded a recovery image as jcase mentioned.
First, load the new ROM onto the root of your sd card. Next, power off your phone. Then, hold down the vol up button and turn on your phone. It should boot into the recovery console. From here to load another ROM, you need to perform a wipe and then load your new ROM by flashing. You should see a Wipe and Flash from Zip menu option in recovery.
In the Wipe menu, choose the first two options in order (factory reset and cache). Wait for each to complete. Next, pressing vol down should get you back to the main menu. From here choose Flash from Zip and then select the ROM zip file you loaded onto your sd card and wait for the update to complete. Last, reboot your phone from the menu.
jcase said:
Easy way is to do
adb shell
if the prompt is
$
your likely on leak
if the prompt is
#
your on root.
Once your on root, flash recovery.
Click to expand...
Click to collapse
$
When you say "likely" you pretty much mean "sorry but you're non-rooted and I don't want to be the one to tell you" ?
xnatex21 said:
$
When you say "likely" you pretty much mean "sorry but you're non-rooted and I don't want to be the one to tell you" ?
Click to expand...
Click to collapse
You have 2.1 from the OTA, or on phone at purchase or from an image you flashed?
try su
xnatex21 said:
$
When you say "likely" you pretty much mean "sorry but you're non-rooted and I don't want to be the one to tell you" ?
Click to expand...
Click to collapse
adb shell
$ su
If you still have a $ then you most "likely" loaded a leak rather then root. If you get a # then you are in luck.
I don't remember if the the leak that included su had adb set to root by default.
good luck.
jcase said:
You have 2.1 from the OTA, or on phone at purchase or from an image you flashed?
Click to expand...
Click to collapse
I followed a guide a few weeks ago that must have been for the leaked version of 2.1.
thisismyanonymousaccount said:
adb shell
$ su
If you still have a $ then you most "likely" loaded a leak rather then root. If you get a # then you are in luck.
I don't remember if the the leak that included su had adb set to root by default.
good luck.
Click to expand...
Click to collapse
I get
su: permission denied
Click to expand...
Click to collapse
I guess that means my phone I'm stuck with it...FML!
xnatex21 said:
I guess that means my phone I'm stuck with it...FML!
Click to expand...
Click to collapse
Yes, sadly you are now stuck with the Leak.
Stay tuned as the devs are still working on it.
g00gl3 said:
Yes, sadly you are now stuck with the Leak.
Stay tuned as the devs are still working on it.
Click to expand...
Click to collapse
Does anyone know what HTC says about all of this? Can I send the phone back to them and have them "restore" the phone to factory settings?
xnatex21 said:
Does anyone know what HTC says about all of this? Can I send the phone back to them and have them "restore" the phone to factory settings?
Click to expand...
Click to collapse
Technically, modifying your device would void warranties. Even if they could "restore" the device, it would still have the newer bootloader that is causing the rooting issue. Some people have "lost" or "broken" the device bad enough that they could get a replacement from Verizon. However, there is mixed results as to what bootloader the refurbished devices come back with.
I posted before about the safety of re-rooting my eris from 1.5 to a rooted 2.2 rom, and due to lack of responses on any forums over the web, I jumped the gun today. First off my Eris after un-rooting it, wouldn't take the OTA update for 2.1, it downloaded and verified that, but after it rebooted, it was still at 1.5 saying no new updates are available. I cannot download the eris 1 click root app as it's only for 2.1 I'm assuming because it says it's not compatible with 1.5 firmware when I download it. I tried to follow this guide [Walkthrough] From stock (1.5) to rooted 2.1 (update - new link) - xda-developers and when I installed the PB00IMG.zip it downloaded but failed to flash and the screen read "Main version is older". I tried this guide All-In-One Auto-Root Script - Page 4 - xda-developers and when it says it's flashing the root image, it goes straight to a screen with only two options "recovery" something and "fastboot". None of which are listed as options in the guides. I am just trying to root my 1.5 eris and flash the KaosFroyo V3 eris rom with Amon Ra's recovery image. Thanks if anyone can help my problem, or shed light on the situation! Sorry if there's been a fix to this problem already stated, I've desperately been browsing many forums and hundreds of replies to no avail. Thanks again.
It looks to me like you got a pretty reasonable answer to the same question over on Android Forums
bftb0

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

[Q] Trouble Rooting and geting "SU" permissions Mytouch 4g. HELP!

This may sound stupid, but does anyone know how to root specifically a RED mytouch 4g?? Maybe the color is intimidating or something, but I have successfully rooted 6 mytouch 4g's and not run into any problems.. I spent a week on this one to no avail. Its running 2.2.1, software number 1.17.531.2, build number 1.17.531.2 CL277036. Is there a manual way without using visionary? It wont grant me permissions even after temp root. Thanks.
try using the gfree method which is in the development section. It seems thats the only way to root the newer mytouches.
Update: Tried every single forum that appeared in the first 10 pages of google for 50 different search terms, and frankly, I'm ****ing beat.. I found a few similar topic forums, but only ONE exact build number, and everything with the SAME EXACT SYMPTOMS.. Is there really nobody out there that has tackled this debockle? I'm not sure what to do at this point, am I doomed?? I'm not a noob with this phone, but I'm not a developer or a programmer either. Anyone got any alternative root methods, other that the visionary, or flashboot methods for the exact specs on my phone??
I'm having the same issue with my red MT4G, had it since Feb. 11 Was able to root but not able to get the s-off same build and software as yours. Help Please!
tim4w5 said:
I'm having the same issue with my red MT4G, had it since Feb. 11 Was able to root but not able to get the s-off same build and software as yours. Help Please!
Click to expand...
Click to collapse
Thats weird, I achieved s=off, using this method: http://forum.xda-developers.com/showthread.php?t=858996
But I can't get superuser permissions to flash the older version of the bootloader, or use gfree. What did you use to root it?
Are these MT4Gs completely stock and out of the box? When I rooted a friend's device, VISIONary wouldn't even temproot at first. He later uninstalled some app and tried VISIONary again and temproot stuck, so maybe something else on the device is getting in the way? Either that or HTC incorporated some fix, we'd need more people with brand new MT4Gs to confirm.
gfree issues
I seem to be having the same issue but when I go to "chmod 777 gfree" I get the ./gfree: permission denied error
bvince05 said:
I seem to be having the same issue but when I go to "chmod 777 gfree" I get the ./gfree: permission denied error
Click to expand...
Click to collapse
Temp root with visionary then try again. Make sure fastboot is disabled before doing it. If it doesn't temp root try an older version of visionary. I used a combo of gfree method and visionary to get root and s off
Sent from my HTC Glacier using XDA App
EDIT: i replied to this while half asleep so figured i would be a little more clear.
i had the gfree permission denied error you got. so temp rooted with visionary(latest) but just froze up my phone. tried a older version and it temp rooted fine. went in to ADB got SU and threw the chmod command at it again and it went through.
hope this helps, not 100% sure it went through because of what i did but its worth a shot.
jdkoren said:
Are these MT4Gs completely stock and out of the box? When I rooted a friend's device, VISIONary wouldn't even temproot at first. He later uninstalled some app and tried VISIONary again and temproot stuck, so maybe something else on the device is getting in the way? Either that or HTC incorporated some fix, we'd need more people with brand new MT4Gs to confirm.
Click to expand...
Click to collapse
I've tried stock out of the box, used it for a while, got s=off, and it stuck even after factory resetting the phone between trying various different methods.
I agree with you regarding a patch of some sort on the software though. I've found this issue on 2 red htc glaciers now.
And although It's new, and shipped with 2.2.1, a buddy of mine goes through them like candy, and I've rooted every single one of them, no problem. even when they started shipping with 2.2.1 it wasnt an issue. So I think it's the newer manufacture build number etc with the red ones..
mustk1ll20 said:
Temp root with visionary then try again. Make sure fastboot is disabled before doing it. If it doesn't temp root try an older version of visionary. I used a combo of gfree method and visionary to get root and s off
Sent from my HTC Glacier using XDA App
EDIT: i replied to this while half asleep so figured i would be a little more clear.
i had the gfree permission denied error you got. so temp rooted with visionary(latest) but just froze up my phone. tried a older version and it temp rooted fine. went in to ADB got SU and threw the chmod command at it again and it went through.
hope this helps, not 100% sure it went through because of what i did but its worth a shot.
Click to expand...
Click to collapse
I have not tried that yet. Where can I find an older version of visionary? I looked for it on their website, but can't seem to find anything but the current version. (maybe I'm not looking hard enough) but.. Hopefully this will work
think this is the one i used. should be R11. may have been updated though, just got the link from another root method that says it r11.
http://www.megaupload.com/?d=7C2BMH3O
It's definitely r11, I'll try this as soon as I get home. thanks!
No problem, hope it works for you.
Sent from my HTC Glacier using XDA App
I dont think It's working. I installed it, then reboot my phone, then ran the app, and At first It looked really REALLY unstable and kept flashing and doing weird things, so I rebooted again, ran it, and now it looks like it's not doing anything at all. How long did it take for your phone to say root successful, maybe I'm just being impatient.
thats what mine did. Just let it do its thing. If its to unstable to put in your commands use adb. I used adb from start to finish just cuz I find it easier.
Didn't take long. It did flash a black screen things like that. But just follow the guide you were using to a T and once you get temp root it shouldn't be a problem from there
Sent from my HTC Glacier using XDA App
I'm kicking myself in the face for not documenting my method I used. I finally did it, but in such a weird way, I'm not sure exactly WHAT it was. I installed visionary 11, uninstalled r14, uninstalled superuser, and ran r11. out of frustration, I scared up some old methods for rooting 2.2, and installed z4 root.. That made it to the second stage, but froze there. So I RE-installed visionary r14, achieved a temproot, and from there flashed gfree, etc.. and eventually stuck a permaroot with s=off.. I apologize for not figuring out exactly what I was doing wrong, or what I did right to solve the problem.
****kkkkk man your slacking -______- I was looking forward to the answer I'm going crazy as well I rooted 3mt4gs in like 5min but my brothers is driving me nuts >=O
carlosdavampire said:
I'm kicking myself in the face for not documenting my method I used. I finally did it, but in such a weird way, I'm not sure exactly WHAT it was. I installed visionary 11, uninstalled r14, uninstalled superuser, and ran r11. out of frustration, I scared up some old methods for rooting 2.2, and installed z4 root.. That made it to the second stage, but froze there. So I RE-installed visionary r14, achieved a temproot, and from there flashed gfree, etc.. and eventually stuck a permaroot with s=off.. I apologize for not figuring out exactly what I was doing wrong, or what I did right to solve the problem.
Click to expand...
Click to collapse
Sent from my HTC Glacier using XDA Premium App
sh root.sh
Im getting passed everything, but when i try to run sh root.sh it say can't open root.sh Someone please help me.
I had troubles rooting my Red Mytouch until I came across this.. http://forum.xda-developers.com/showthread.php?t=995549
Follow this to a T and then do yourself a favor and downgrade your Hboot to 0.85.2007
I rooted mine. Go here. http://theunlockr.com/2010/12/10/ho...s-off-on-the-t-mobile-mytouch-4g-htc-glacier/ took me a bit to figure it out. But on this link it tells you to update if you arnt 2.21 or higher or if you haven't received the outa update. Well I did but when I tryed this method with out the update it didn't work so update anyways. IT WORKS!
Sent from my HTC Glacier using XDA App

little puzzled any help appreciated

ok so i recently picked up a used mytouch 4g. i rooted it and have superuser ability along with rom manager. have tried and think i have installed 3.0.2.4 clockwork recovery. i flashed that multiple times.
however when i try and boot into recovery i merely get to the phone with the red !. am i missing something?
thanks for your time!
kdm212 said:
ok so i recently picked up a used mytouch 4g. i rooted it and have superuser ability along with rom manager. have tried and think i have installed 3.0.2.4 clockwork recovery. i flashed that multiple times.
however when i try and boot into recovery i merely get to the phone with the red !. am i missing something?
thanks for your time!
Click to expand...
Click to collapse
does you phone say s-off at the top when you boot into hBoot?
neidlinger said:
does you phone say s-off at the top when you boot into hBoot?
Click to expand...
Click to collapse
s-on. however i thought you could still root and flash roms with it on. looks like im wrong?
kdm212 said:
s-on. however i thought you could still root and flash roms with it on. looks like im wrong?
Click to expand...
Click to collapse
you are correct in your assumption.
The HTC Glacier and Vision have a security protocol in place that will revert the phone back to a 100% stock fashion every-time you turn off the phone. If you wish to do custom ROMs, recovery images, and radio files you must turn the "s-on" to "s-off".
neidlinger said:
you are correct in your assumption.
The HTC Glacier and Vision have a security protocol in place that will revert the phone back to a 100% stock fashion every-time you turn off the phone. If you wish to do custom ROMs, recovery images, and radio files you must turn the "s-on" to "s-off".
Click to expand...
Click to collapse
ok so i did see the thread for s-off yet it seems very intensive. im also assuming theres no other way to get s-off.
kdm212 said:
ok so i did see the thread for s-off yet it seems very intensive. im also assuming theres no other way to get s-off.
Click to expand...
Click to collapse
You can try the sh root.sh method.
1a ) download and install VISIONary.apk. Download from here
-Looks like you've done that since you have come this far.
1b) when you run VISIONary make sure both set system to R/W and Run Visionary.sh are both checked.
2) Download the script to the root of your SDcard
This is the file
3) Extract the folder from the .zip and store the folder with it's contents onto the root of the SDcard.
4) Download Terminal emulator from the market
-Link to the market for this app.
5) open the Terminal Emulator and type
Code:
$ su
#
The Dollar Sign " $ " should change to a pound sign " # ". If the Super user program ask for your permission, you'll want to grant it. You're screen should look like the box just above this line.
6 ) Change the directory to the root folder
Code:
# cd /sdcard/root
7) run the script
Code:
# sh root.sh
make sure you do not get any errors.
If you havent you can reboot into hBoot and look for s-off.
i personally used this method to root my phone before i left the t-mobile store when i bought the phone.
I CANNOT AND WILL NOT BE HELD ACCOUNTABLE IF YOU MESS UP YOUR PHONE. ROOTING ONES PHONE IS SERIOUS BUSINESS AND SHOULDN'T BE TAKEN LIGHTLY. IF YOU SHOULD BLAME ME I WILL LAUGH AND POINT.
neidlinger said:
You can try the sh root.sh method.
1a ) download and install VISIONary.apk.
-Looks like you've done that since you have come this far.
1b) when you run VISIONary make sure both set system to R/W and Run Visionary.sh are both checked.
2) Download the script to the root of your SDcard
This is the file
3) Extract the folder from the .zip and store the folder with it's contents onto the root of the SDcard.
4) Download Terminal emulator from the market
-Link to the market for this app.
5) open the Terminal Emulator and type
Code:
$ su
#
The Dollar Sign " $ " should change to a pound sign " # ". If the Super user program ask for your permission, you'll want to grant it. You're screen should look like the box just above this line.
6 ) Change the directory to the root folder
Code:
# cd /sdcard/root
7) run the script
Code:
# sh root.sh
make sure you do not get any errors.
If you havent you can reboot into hBoot and look for s-off.
i personally used this method to root my phone before i left the t-mobile store when i bought the phone.
I CANNOT AND WILL NOT BE HELD ACCOUNTABLE IF YOU MESS UP YOUR PHONE. ROOTING ONES PHONE IS SERIOUS BUSINESS AND SHOULDN'T BE TAKEN LIGHTLY. IF YOU SHOULD BLAME ME I WILL LAUGH AND POINT.
Click to expand...
Click to collapse
tried that and it does have s-off. thanks! however when i try to boot into recovery im still stuck with the phone and !...
EDIT: /sdcard/root/wpx.ko failed (function not implemented)
kdm212 said:
tried that and it does have s-off. thanks! however when i try to boot into recovery im still stuck with the phone and !...
Click to expand...
Click to collapse
After doing the above method you're gonna have to reinstall the recovery from Rom Manager. Watch it carefully do not let the phone sleep (I recommend going to delopment check never sleep while charging and plug it into a charger while it downloads.) You have to pay attention because it will ask for SU permissions when it finishes downloading, and it for some reason only gives you like 3 or 4 seconds instead of the usual ten. If you have already tried installing the recovery you may wanna go to the SU App and make sure that Rom Manager didn't get denied premission which is the default if you do not select Allow fast enough.
got it! thank you very much! cant wait to play with a new rom. any recommendations?
Virtuous Fusion 1.0.6 with sense 3.0/3D is fantastic!. Give it a go.
kdm212 said:
got it! thank you very much! cant wait to play with a new rom. any recommendations?
Click to expand...
Click to collapse
Try out a sense rom and non sense to decide which you like best. virtuous fusion 1.0.6 is pretty nice sense rom and cm7 or royalginger are awesome non sense roms.
im going to try both!
kdm212 said:
im going to try both!
Click to expand...
Click to collapse
Make sure to do Nandroid Backups prior to flashing new ROMs. And just a fair warning you might want to install the .85 (engineering) hBoot.
what is that hboot all about?
neidlinger said:
Make sure to do Nandroid Backups prior to flashing new ROMs. And just a fair warning you might want to install the .85 (engineering) hBoot.
Click to expand...
Click to collapse
Absolutely a great idea, little nerve wracking to make changes to hboot and radio but very worth it. The directions how to do engineering boot loader are in the ultimate s-off sticky. Confusing at first, but after you do it once it gets easier.
Sent from my HTC Glacier using XDA App
kdm212 said:
what is that hboot all about?
Click to expand...
Click to collapse
It's a option that helps prevent bricking the device. Allows you to flash section of to phone's workings
[sent via Cyanogen powered Android]
Shivansh said:
Virtuous Fusion 1.0.6 with sense 3.0/3D is fantastic!. Give it a go.
Click to expand...
Click to collapse
+++++100000000000000000000000000000000000000000000 BEST ROM I HAVE EVER USED!!!!!
*so far
so first i must thank you all for the help. now the bad, i decided to buy another mytouch 4g. my fiance liked the old one so much that she took it. so now im here with a new one and have nothing but problems.
im running 2.2.1 and seem to be able to root the phone. su icon is on and everything. BUT if i reboot the phone its like i have to start over. im not just temp rooting either. second, i cant get ANY terminal emulator to let me have su access.
visionary, z4root, adb. you name it and i seem to think ive tried it. lol this is unfair, my chicks phone is way better than mine.
any help would be so awesome.
kdm212 said:
so first i must thank you all for the help. now the bad, i decided to buy another mytouch 4g. my fiance liked the old one so much that she took it. so now im here with a new one and have nothing but problems.
im running 2.2.1 and seem to be able to root the phone. su icon is on and everything. BUT if i reboot the phone its like i have to start over. im not just temp rooting either. second, i cant get ANY terminal emulator to let me have su access.
visionary, z4root, adb. you name it and i seem to think ive tried it. lol this is unfair, my chicks phone is way better than mine.
any help would be so awesome.
Click to expand...
Click to collapse
Trade phones back so she gets the new one. Problem solved!
Seriously though, some of these phones won't root with visionary root.sh method. Bad news is if it's not working you will need to try gfree method to root which is indicative of a phone with the emmc chip that is considered to be faulty. For more info search for the thread about emmc chips.
Sent from my demonSPEED Glacier using XDA Premium App
so this is not a rootable phone?

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

Categories

Resources