How can I judge my inc is rooted? i can find the recovery vison is ClockworkMod Recovery 2.5.0.1!but i can not run root explorer.
Did I should run unrevoked3.1 again?
JohnHi said:
How can I judge my inc is root? i can find the recovery vison is ClockworkMod Recovery 2.5.0.1!but i can not run root explorer.
Did I should run unrevoked3.1 again?
Click to expand...
Click to collapse
...what???
I do not know whether my incredible phone is rooted,or not!
how can i judge it?
Install a terminal emulator and type the command su. If a tip pops up briefly claiming terminal emulator was granted rights then you have root. Oh and running unrevoked3 more than once won't hurt anything.
Sent from my Incredible.
Related
Rooted Evo 2.2 via UnrEVOked 3.21 stock everything. I can't get this to install. I emailed the dev and he told me that I need to use UnrEVOked Forever because 3.21 doesn't have NAND unlocked. According to the UnrEVOked website that is not true. 3.21 does have Nand unlocked.
Do any of you guys have any idea on how I can get this stupid app installed?
Titanium installed a version of it but I think that only Titanium can access it.
SantinoInc said:
Rooted Evo 2.2 via UnrEVOked 3.21 stock everything. I can't get this to install. I emailed the dev and he told me that I need to use UnrEVOked Forever because 3.21 doesn't have NAND unlocked. According to the UnrEVOked website that is not true. 3.21 does have Nand unlocked.
Do any of you guys have any idea on how I can get this stupid app installed?
Titanium installed a version of it but I think that only Titanium can access it.
Click to expand...
Click to collapse
If Titanium installed busybox try going to a sheel then type in busybox. If you get a display with a command listing then type in busybox --install /system that should install busybox so you can use the full command set.
kf2mq said:
If Titanium installed busybox try going to a sheel then type in busybox. If you get a display with a command listing then type in busybox --install /system that should install busybox so you can use the full command set.
Click to expand...
Click to collapse
What is a sheel? Is this some kind of adb thing? Can you explain it to me step by step like I have down syndrome please.
i have an older version of busybox (1.16.2) and while trying to install 1.17.1 the installer is telling me that installation failed because 1) the device is not nand unlocked or 2) app was unable to remount.
my phone has been nand-unlocked for months. i've even installed this and other busybox versions prior to trying now on this rom. can flashing a new rom (MetroDroid) change my nand-unlock status? (i dont think so)...
Max I got the same exact message from BusyBox. When I emailed the dev he told me that 3.21 does not have Nand unlocked, which does not appear to be true. I have stock everything...IDK wtf is going on with this app. It really blows!
I have titanium backup installed with the busybox version from tib. Downloaded the bbox installer from the market and installed ver. 1.17 just fine.
Rooted with unrevoked forever for s-off and regaw's root method and currently running rooted 3.29.
Thought i would get an error like you guys but install was without a hitch.
You can find out if you are NAND unlocked by turning your phone off and then turning it back on while holding the volume down button. If you see S=OFF then you are unlocked. Also make sure that nothing is using busy box or root and try killing any unnecessary apps with a task killer. You can't change it if something is using it.
Haus: if S is on what Rico have to do? can I change it from that boot screen? Do I have re root?
SantinoInc said:
Haus: if S is on what Rico have to do? can I change it from that boot screen? Do I have re root?
Click to expand...
Click to collapse
You can use unrevoked forever or install the engineering bootloader, if you plan on flashing a lot of ROMs the eng bootloader is probably your best bet. That will give you the fastboot tools and allow you to use Cyanogenmod
****. You were right man. S=On. I thought Unrevoked 3.21 unlocked nand. Did I screw up somewhere? What is this engineer bootloader u mention. I never heard of it. How do I get it? Is it hard to use?
You'll need to flash a custom Recovery and use that to flash either the eng bootloader or unrevoked forever. I believe ROM manager can install the recovery for you or the Amon RA thread in my sig has the instructions to do it manually. A quick search should turn up the eng bootloader, sorry I don't have the link handy though
Edit: Found it Evo eng hBoot .76 - Recovery Flashable
Hi All,
I just discovered a RUU 1.84.708.1. It is the localized version in my place.
I've already rooted and running ENG S-Off. After extracted the ROM image from RUU, I wonder how can I root (install superuser/busybox) and deodex the rom image before I flash it through CWM recovery?
Thanks in advance!
Anyone plz?
Sent from my HTC Vision using XDA App
Manual Deodexing:
http://forum.xda-developers.com/showthread.php?t=765270
Should be a way to apply these deodexing steps to the ROM pre-flash. I personally don't know how, but this would be the thread to ask about that in.
You could also ask how to root via cmd or terminal there.
Hope this helps in some way.
Hi All,
I tried to install the system.img inside the ruu and it was successful.
After that I attempted to used the rage/gfree method to gain a shell root. However, after the rooting process, whenever I start an app that asks superuser for root access, superuser force closes.
I've already gained eng s-off, but still not able to gain a shell root. Can anyone help on that?
IntegraR said:
Hi All,
I tried to install the system.img inside the ruu and it was successful.
After that I attempted to used the rage/gfree method to gain a shell root. However, after the rooting process, whenever I start an app that asks superuser for root access, superuser force closes.
I've already gained eng s-off, but still not able to gain a shell root. Can anyone help on that?
Click to expand...
Click to collapse
Have you tested whether or not you have shell root through a terminal emulator? Your version of Superuser might just be out of date.
ROK here's the story. I rooted my DINC when I first got it two years ago, well my girlfriend now wants hers rooted.
I read the wiki and all that. But everytime I try it gives me an error message after the first phone boot after trying to gain root access... error can't root is your firmware too new?
Now my steps are.
Plug phone in.
Install phone drivers. (I think this may be where i went wrong)
run unrevoked3
It does its stuff and reboots phone into hboot continues to do it's thing.
Reboots phone again.
Starts asking fir root.
Then I get the error.
Can you tell what I'm doing wrong?
Do I have to install the hboot drivers on my windows 7 machine when the phone is in hboot?
Help!
Ok first,I don't believe unrevoked supports the newest firmware update, but there are other methods...
second, if unrevoked completes successfully, try manually flashing the recovery, if that completes successfully, then make a backup and flash a new rom..
If it boots up however, try downloading superuser and install it, if it works, should be good to go
Sent from my Galaxy Nexus using XDA App
networkmagician419 said:
Ok first,I don't believe unrevoked supports the newest firmware update, but there are other methods...
second, if unrevoked completes successfully, try manually flashing the recovery, if that completes successfully, then make a backup and flash a new rom..
If it boots up however, try downloading superuser and install it, if it works, should be good to go
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Its 2.2
And it wont get root access. So no SU.. I installed rom manager and it says no root access. And I can't get into recovery I believe.
BossJ said:
Its 2.2
And it wont get root access. So no SU.. I installed rom manager and it says no root access. And I can't get into recovery I believe.
Click to expand...
Click to collapse
Are you s-off? If so flash cwm recovery thru hboot as a PB31IMG.zip. http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip. Then if you can access recovery use it to flash the su binary, installing the su app does not install the binary. You can go to preferencec in the su app and try installing it from there, but it usually fails. You can get the lates flashable one here. http://dinc.does-it.net/SuperUser/SuperUser_3.0.7.zip
cmlusco said:
Are you s-off? If so flash cwm recovery thru hboot as a PB31IMG.zip. http://dinc.does-it.net/PB31IMG.zip. Then if you can access recovery use it to flash the su binary, installing the su app does not install the binary. You can go to preferencec in the su app and try installing it from there, but it usually fails. You can get the lates flashable one here. http://dinc.does-it.net/su.zip
Click to expand...
Click to collapse
No. When I launch rom manager it says I need root. I'm not s-off.
My question is.. when I install the windows hboot drivers... does the phone need to be in hboot? I installed the hboot drivers when the phone was plugged in USB bur the phone was loaded into android 2.2
BossJ said:
No. When I launch rom manager it says I need root. I'm not s-off.
My question is.. when I install the windows hboot drivers... does the phone need to be in hboot? I installed the hboot drivers when the phone was plugged in USB bur the phone was loaded into android 2.2
Click to expand...
Click to collapse
Root and s-off are two different things, and you dont need rom manager to access recovery. However if your s-on you dont have a custom recovery to flash things in anyways.
Yes when you install the drivers you need to be in hboot to get the correct drivers.
If you ran unrevoked and it compleeted successfully you should have root and s-off. I would make sure the drivers are right, and then run unrevoked again.
cmlusco said:
Root and s-off are two different things, and you dont need rom manager to access recovery. However if your s-on you dont have a custom recovery to flash things in anyways.
Yes when you install the drivers you need to be in hboot to get the correct drivers.
If you ran unrevoked and it compleeted successfully you should have root and s-off. I would make sure the drivers are right, and then run unrevoked again.
Click to expand...
Click to collapse
OK. Unrevoked always failed. So. Must be the hboot drivers installing incorrectly.
cmlusco said:
Root and s-off are two different things, and you dont need rom manager to access recovery. However if your s-on you dont have a custom recovery to flash things in anyways.
Yes when you install the drivers you need to be in hboot to get the correct drivers.
If you ran unrevoked and it compleeted successfully you should have root and s-off. I would make sure the drivers are right, and then run unrevoked again.
Click to expand...
Click to collapse
So when I install the hboot drivers while the phone is in hboot... do I run unrevoked when thephone is still in hboot? Or do I restart the phone?
BossJ said:
So when I install the hboot drivers while the phone is in hboot... do I run unrevoked when thephone is still in hboot? Or do I restart the phone?
Click to expand...
Click to collapse
Yes restart the phome. Run unrevoked with the phone booted to the os.
cmlusco said:
Yes restart the phome. Run unrevoked with the phone booted to the os.
Click to expand...
Click to collapse
Thanks so much for your help! Finally got it all taken care of!
It's been soooo long since I've rooted any phone! BUT I finally got it!
Wooo
Thanks again!
Is there any way to get "s-off" on a device running 2.3.4? I have looked all over and tried all of the methods I have found. Is it possible to unlock & root this device or is it stuck running the stock setup?
Andriod 2.3.4
Baseband 2.15.10.07.07
Huckle_Berry said:
Is there any way to get "s-off" on a device running 2.3.4? I have looked all over and tried all of the methods I have found. Is it possible to unlock & root this device or is it stuck running the stock setup?
Andriod 2.3.4
Baseband 2.15.10.07.07
Click to expand...
Click to collapse
Only method I've seen for the Incredible is this one here:
http://forum.xda-developers.com/showthread.php?t=1306400
SlimSnoopOS said:
Only method I've seen for the Incredible is this one here:
http://forum.xda-developers.com/showthread.php?t=1306400
Click to expand...
Click to collapse
Awesome thanks for the help I will check that out!
Hi,
I have a g2 that I bought off eBay. I messed around trying to follow the rooting/s-off guide here but kept getting the error about not downgrading enough (the one where md5-1 and md5-3 are the same). I somehow managed to get CM9 on to it (Mimcry 1.3.2) and its running all good. I have superuser as an app on my menu.
However when I try to get superuser to gain temp root access or I type su into the terminal emulator I get an error. If I click on temp root in the superuser app it crashes and the terminal emulator gives me
reloc_library[1314]: 30857 cannot locate '-mktemp'…
CANNOT LINK EXECUTABLE
Click to expand...
Click to collapse
My bootloader says
VISION PVT SHIP S-OFF
HBOOT-0.82.0008
MICROP-0425
RADIO-26.13.04.19_M
eMMC-boot
April 13 2011, 14:51:54
Click to expand...
Click to collapse
Is my device rooted or not?
yea I believe you are but you had a bad download of the rom, try wiping and flashing it again with a fresh download. or you may be able to just wipe cahce and data and then fix permissions
there is an app in the market that will check root for you
Sent from my HTC Vision using xda premium
While you may have the superuser app, did you ever push the su and busybox binaries to the phone? What guide did you follow to root the phone? If I were to go by just the hboot alone I would say it looks like it was never downgraded and exploited, since typically you'd see S-OFF, or an engineering rom if someone has downgraded and rooted it.
What's the recovery you are using? what guide are you using for the rooting part? etc. If you flashed mimicry then it should have come with su/busybox/etc unless the phone prevented the flashing of the boot/kernel (Which would be typical with a stock bootloader).
kbeezie said:
While you may have the superuser app, did you ever push the su and busybox binaries to the phone? What guide did you follow to root the phone? If I were to go by just the hboot alone I would say it looks like it was never downgraded and exploited, since typically you'd see S-OFF, or an engineering rom if someone has downgraded and rooted it.
What's the recovery you are using? what guide are you using for the rooting part? etc. If you flashed mimicry then it should have come with su/busybox/etc unless the phone prevented the flashing of the boot/kernel (Which would be typical with a stock bootloader).
Click to expand...
Click to collapse
I followed the guide on the xda wiki. In another post I made when I was having trouble downgrading, you told me that I shouldn't have to because of already having s-off and the radio was on. (heres the op - thanks for your advice by the way).
I got all of the files (busybox/su etc) for the tutorial onto my phone using adb but could not execute the
./gfree -f -b hboot-eng.img -y recovery.img
Click to expand...
Click to collapse
command successfully in the rooting tutorial on the wiki.
I somehow managed to get clockwordmod on as my recovery but cannot access it without using adb; my hardware buttons dont seem to do anything in the bootloader menu so I have to run "adb reboot recovery" to get into clockwork mod, which then allows me to use the optical trackpad to navigate.
Hi all I've rooted my wildfire last year using unrevoked and all went ok... now I've used unrevoked another time to flash an updated clockworkmod 2.5.0.7 instead of my actual 2.5.0.1 almost because I can't charge my phone when it's off because of an old bug in cwm.
After running unrevoked the phone boots but I've lost superuser app and unrevoked itself fails with something like "cannot get root, firmware too new?" and if I run "su" from terminal emulator I got a "permission denied". The cwm is still version 2.5.0.1
Any idea?
I've just installed superuser app from the market and now I've restore the su command functionality...
What happened? and why unrevoked doesn't upgrade recovery image with the one I've specified?
mrfree2ita said:
I've just installed superuser app from the market and now I've restore the su command functionality...
What happened? and why unrevoked doesn't upgrade recovery image with the one I've specified?
Click to expand...
Click to collapse
I never would have the idea to re-run unrevoked for flashing a different recovery. Although it's also suggested in The Complete Wildfire Index thread I always would choose one of the three other methods (always done it by the PC49IMG.zip method).
Flashing a recovery isn't just a minor tweak if I'm correct. So I'm not surprised that you lost superuser temporarily. I personally would get a bit nervous to do this by revolutionary - but that's perhaps I'm already an old wise guy
Because I've used unrevoked (when I've rooted my wildfire it was the only way) I'm actually S-ON so the other 3 methods shouldn't work in my case.
mrfree2ita said:
Because I've used unrevoked (when I've rooted my wildfire it was the only way) I'm actually S-ON so the other 3 methods shouldn't work in my case.
Click to expand...
Click to collapse
oh well, I've been mistaken, then - yes that's the only method if you're s-on.