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.
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 followed the instructions for permaroot-ing my G2, and everything went smoothly (thanks to everyone who contributed). After obtaining permaroot, I was prompted to install the OTA update. After applying the update I lost root permissions (tried the "su" command on terminal emulator and ADB). I figured I would just follow the steps again for permaroot, but when I run VISIONary for temp root it says "You device is already rooted". Also, I've checked the bootloader, and I still have S-OFF. I'm wondering if anyone has encountered this issue, and if there is a way to regain permaroot. Any help would be much appreciated.
Thanks!
Yes well if your going to root NEVER apply an OTA. Now that you applied it and you still have s off just flash a custom rom. They all have root. If you want to stay stock and just gain root back use the rage method.
Sent from my HTC Vision using XDA App
Thanks
Shortlived,
Thanks for your response. I actually couldn't just flash a custom ROM because I didn't flash ClockworkMod recovery before applying the OTA update. Because I lost root, I couldn't actually flash the recovery after applying OTA. The rage method worked perfectly though and I'm back to root!
You should go ahead and flash a custom recovery (clockworkmod) and make a nandroid back up now since you have root again.
Mistakes happen, but, there's always nandroid.
I don't know much about rooting, flashing ROMs or anything. But just have a few questions..
As the HTC WFS with S-ON can only be 'temporarily rooted' using ADB and downgrading HBOOT to bypass the RUU errors; I wanted to know what this actually means?
Is it the same as full permanent root or not?
What can I do with full root that I can't do with ADB root?
If I do temp root, what happens if I reboot my phone? Does the root permissions disappear and the system apps I've deleted return or what?
*se-nsei. said:
As the HTC WFS with S-ON can only be 'temporarily rooted' using ADB and downgrading HBOOT to bypass the RUU errors;
Click to expand...
Click to collapse
Never heard of a temp root for the Wildfire S, can you post the full guide on how to do it?
Can't help you with the difference between root and temp-root.
http://forum.xda-developers.com/showthread.php?t=1301388
anyone gonna help? :/
Hello!! I have problems to root HTC Wildfire S with Android 2.3.5 S-ON.
I've sucessfully unlocked bootloader of my HTC using the tutorial of HTCDev. The problem, is when I try rooting the phone using OneClick, unlock root and others programs. I have a problem when I try execute the exploit zergRush on my phone. I copy them into /local/data/tmp folder, and I change the permissions with chmod 777. All this steps, work fine, but when I execute the exploit zergRush with ADB, fail in the progress.
The progress fail when zergRush try to mount the system folder as read and write access. In this time, I suppose that system must be root, but no it's.
I think that the zergRush 2.3.3 exploit not work correctly in 2.3.5 Android versions, but shearching in this forum I found that this version work fine.
Can you help me please?
I'm a spanish people. I apologize if you don't understand me very well.
Sorry.
Thanks for your time.
I had the same problem rooting with that method. I found one that works way better. Also got s-off easily as well. I'm not at my computer but send me a private message and I'll send you links with instructions on how I did it. It was very easy. Zergrush would say it was working but would not complete correct.
Sent from my LG-VM670 using XDA
first recovery，and then root,very easy.
I tried and don't work
I've already tried to restore my phone and do rooting process again, and don't work.
Get root via Recovery. It's work!
Hammerin87 said:
I've already tried to restore my phone and do rooting process again, and don't work.
Click to expand...
Click to collapse
yes ,first recovery and then root.
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.