Develop Bugs

adb remount permission denied

I am getting a permission denied when I try to run "adb remount".
I am running the netarchy rooted ROM.
I am Unrevoked3 and Unrevoked Forever.
So my NAND is unlocked and I am rooted. Why does it still say Permission Denied?

Install the latest version of SuperUser (look in the Market). When you try to do adb remount, or su in adb shell, look at your phone. There'll be a popup asking for permission.

AzN1337c0d3r said:
I am getting a permission denied when I try to run "adb remount".
I am running the netarchy rooted ROM.
I am Unrevoked3 and Unrevoked Forever.
So my NAND is unlocked and I am rooted. Why does it still say Permission Denied?
Click to expand...
Click to collapse
In Netarchy's kernel thread he mentions something about unrevoked 3 not giving full access to root, not sure if he was just referring to the NAND or what but that may have something to do with it. If all else fails you can always go back and try rooting it manually without unrevoked.
just out of curiosity, what does your name mean? The last part looks like coder but what is azn 1337?

xHausx said:
In Netarchy's kernel thread he mentions something about unrevoked 3 not giving full access to root, not sure if he was just referring to the NAND or what but that may have something to do with it. If all else fails you can always go back and try rooting it manually without unrevoked.
just out of curiosity, what does your name mean? The last part looks like coder but what is azn 1337?
Click to expand...
Click to collapse
My leetspeak is a little rusty, but I think 1337 is 'leet' as in "elite"....and I'm guessing the young man is of Asian descent.

drmacinyasha said:
Install the latest version of SuperUser (look in the Market). When you try to do adb remount, or su in adb shell, look at your phone. There'll be a popup asking for permission.
Click to expand...
Click to collapse
Installed latest version of SuperUser.
"adb remount" still saying permission denied.
"adb shell su" did ask me for permission however.
xHausx said:
In Netarchy's kernel thread he mentions something about unrevoked 3 not giving full access to root, not sure if he was just referring to the NAND or what but that may have something to do with it. If all else fails you can always go back and try rooting it manually without unrevoked.
Click to expand...
Click to collapse
I thought Unrevoked Forever took care of the NAND not getting unlocked. It says on their website that it unlocks NAND.
Anyways, the whole reason why I went with unrevoked is because I could keep PRI 1.40_003. I had lost it when I manually rooted and had to go back to stock and then unrevoked to get it back.

I am having the same issues. I am unrevoked3 and unrevoked forever. It is always telling me either device not found or remote not allowed. As far as I can tell all of my drivers are up to date, I am fully rooted with nand unlocked, and the problem didn't start until just recently. Everything worked fine before. I will try to download an updated Superuser app and give some feedback on that when I get off work.
On a side note, does Busybox have anything to do with this sort of matter?
Sent from my regaw rooted EVO.

My problem appears to be a software/OS issue. When I wipe everything and install a stock 2.2 system, I am able to "adb remount".
My guess is that something is continually accessing the /system partition and holding a lock on it.
Does anyone know how I might check for this?

Just to clarify: yes, Unrevoked Forever does unlock NAND.
The issue must be with the rom? Try a different superuser/su...

AzN1337c0d3r said:
Installed latest version of SuperUser.
"adb remount" still saying permission denied.
"adb shell su" did ask me for permission however.
Click to expand...
Click to collapse
Mmmkay, your problem is either:
1) NAND is locked still (unlikely).
2) ROM is not set up to have shells be root by default (likely).
To test, open adb shell. If you see a $, then it's #2. If you see a #, then it's probably #1. To be extra sure, if you're seeing a $, type "su" then enter, approve the su request, then do "mount -o remount,rw /system", followed by "mkdir /system/testymctest". If you get a permission error, then your NAND is not unlocked.

drmacinyasha said:
Mmmkay, your problem is either:
1) NAND is locked still (unlikely).
2) ROM is not set up to have shells be root by default (likely).
To test, open adb shell. If you see a $, then it's #2. If you see a #, then it's probably #1. To be extra sure, if you're seeing a $, type "su" then enter, approve the su request, then do "mount -o remount,rw /system", followed by "mkdir /system/testymctest". If you get a permission error, then your NAND is not unlocked.
Click to expand...
Click to collapse
Thank you so much for the info. I have been searching high and low for a straight answer on this. Even though its not fixed I am much happier knowing what the issue is. Again thank you.
When I ran your test I got a $ which as you said means it is a conflict with my current ROM. So, if I flash a different ROM than I should be squared away yes? Again many thanks.
Sent from my regaw rooted EVO.

drmacinyasha said:
Mmmkay, your problem is either:
1) NAND is locked still (unlikely).
2) ROM is not set up to have shells be root by default (likely).
Click to expand...
Click to collapse
It says clearly SHIP S-OFF on my bootloader. This is the way to tell if you are Unrevoked Forever.
To test, open adb shell. If you see a $, then it's #2. If you see a #, then it's probably #1. To be extra sure, if you're seeing a $, type "su" then enter, approve the su request, then do "mount -o remount,rw /system", followed by "mkdir /system/testymctest". If you get a permission error, then your NAND is not unlocked.
Click to expand...
Click to collapse
Everything is as you described. It is #2. and when I do the "mount -o remount,rw /system" I get permission denied.
I'm not sure how Root Explorer works, but I assume it obtains root permissions and then run the mount command as you have described above.
My NAND is unlocked, I can get to it via Root Explorer and mount it as r/w and then access it through shell. However, if I don't use Root Explorer and try the command through the shell, it doesn't work.
It seems almost like I am not getting SU permissions even though my shell changes to a #.

AzN1337c0d3r said:
It says clearly SHIP S-OFF on my bootloader. This is the way to tell if you are Unrevoked Forever.
Everything is as you described. It is #2. and when I do the "mount -o remount,rw /system" I get permission denied.
I'm not sure how Root Explorer works, but I assume it obtains root permissions and then run the mount command as you have described above.
My NAND is unlocked, I can get to it via Root Explorer and mount it as r/w and then access it through shell. However, if I don't use Root Explorer and try the command through the shell, it doesn't work.
It seems almost like I am not getting SU permissions even though my shell changes to a #.
Click to expand...
Click to collapse
Hrm... Are you sure you have the latest version of ChrisDD's SuperUser from the Market, and then opened up its settings tab to make sure there's the latest su executable? That's the only thing I can think of.

drmacinyasha said:
Hrm... Are you sure you have the latest version of ChrisDD's SuperUser from the Market, and then opened up its settings tab to make sure there's the latest su executable? That's the only thing I can think of.
Click to expand...
Click to collapse
Yup I did exactly that.
It's some app I installed that is doing this. I nandroided my current config, reflashed the netarchy 2.2 rooted rom and was able to get access.
Then when I installed all the rest of my apps, I suddenly lost access.
Tommorow I will start fresh again and try apps one by one.

now i got # what else

[Q] Gfree Rooting!

Hey guys,
I took the advice of tons of people here to try the gfree method instead of the hboot or something, or the visionary permaroot.
the thing is, i did it my way and was too lazy to install ADB cuz it always failed and I don;t know how to use it.
I got a desire z- asian version
with a 1.2 version (NOT 1.7 that can't use gfree)
anyway
here's what i did
1) Installed Visionary to Temproot
2) got superuser for terminal emulator (ON PHONE)
3) chmod 777 the GFREE File on SDCARD
4) Tried to run it with the ./gfree -f command
5) IT SHOWS PERMISSION DENIED....WHYYY!???
WTF?
Anyway, if theres no o
ther way than ADBing this, I'll just go ahead and use the .ko file from the other rooting method..
THANKS GUYS

kwhkkwhk said:
Hey guys,
I took the advice of tons of people here to try the gfree method instead of the hboot or something, or the visionary permaroot.
the thing is, i did it my way and was too lazy to install ADB cuz it always failed and I don;t know how to use it.
I got a desire z- asian version
with a 1.2 version (NOT 1.7 that can't use gfree)
anyway
here's what i did
1) Installed Visionary to Temproot
2) got superuser for terminal emulator (ON PHONE)
3) chmod 777 the GFREE File on SDCARD
4) Tried to run it with the ./gfree -f command
5) IT SHOWS PERMISSION DENIED....WHYYY!???
WTF?
Anyway, if theres no o
ther way than ADBing this, I'll just go ahead and use the .ko file from the other rooting method..
THANKS GUYS
Click to expand...
Click to collapse
Ive seen this before, which files did you put on the sdcard, If you put the entire gfree02.zip file on your sdcard this is worng. You need to unzip the gfree02.zip file and place only the gfree file from the unzipped gfree02.zip file on the root of your sd card.
then re-run using this Code:
Code:
$ su
# cd /sdcard
# chmod 777 gfree
# ./gfree
# sync

i did everything as said, moved only the gfree file onto the sdcard.
everything works until ./gfree
it says: "./gfree: permission denid"
i don't really know whats wrong. the kernels right - its a stock 2.2 asian desire z on 1.2 version or something.
thanks SO MUCH For the reply though. I REALLY APPRECIATE IT

The guide says not to use Visionary for temp root before using gfree, in fact it says to either turn it off (if set to auto-soft-root on boot) or uninstall it altogether.
the gfree method has you use the rage method to obtain temp root.

raitchison said:
The guide says not to use Visionary for temp root before using gfree, in fact it says to either turn it off (if set to auto-soft-root on boot) or uninstall it altogether.
the gfree method has you use the rage method to obtain temp root.
Click to expand...
Click to collapse
Thats if your gonna temp root with Rage, requires ADB to push the files, which he is trying to avoid using ADB, gfree has been done the way he is trying before.

I don't believe you can run the gfree program from the sdcard mount point. You should try moving it to the phone itself (try putting it in /data/local directory as instructed in the wiki). That should take care of your permission denied issue.
Also, you may want to copy over all of the other files as listed in the wiki (except for rage since that's not needed for you). The wiki says you need to run the root command after running gfree (it'll set up things like busybox and su for you). You could also do all it manually yourself if you really wanted to...

But how do I move it off the sdcard? I tried using es file explorer but it says gfree can't be moved. And I cant mount the internal memory. Thanks for the advice though

If you are temp rooted you should be able to remount your file system as read/write, you will need to do this to copy files to the /system path and set permissions.

raitchison said:
If you are temp rooted you should be able to remount your file system as read/write, you will need to do this to copy files to the /system path and set permissions.
Click to expand...
Click to collapse
How would I do that?
remounting the file system? i can't find that option in settings...
and by copying the files, is that done through a file manager on the phone?
or on a computer?
thanks so much guys for the help

It shouldn't make a difference if gfree is on /sdcard or not.
To the OP - do you have a # (root) prompt when you are trying to run gfree ? You need that or it won't work. Have you followed exactly the commands that joemm posted, and you didn't get error messages from any of them ?

Yes I do have that sign. Everythin works (chmod, su) until the last code which is to run it.

kwhkkwhk said:
Yes I do have that sign. Everythin works (chmod, su) until the last code which is to run it.
Click to expand...
Click to collapse
Do "ls -l gfree" and copy and paste up here the output please. Something is still wrong.

It shows
Rwxr-x system sdcard_rw 134401 2010-12-11 08:57 gfree

steviewevie said:
It shouldn't make a difference if gfree is on /sdcard or not.
Click to expand...
Click to collapse
By default on my phone (running CM6), the sdcard mount point is mounted with the noexec option (so no direct execution of any binaries). I assumed it was this way on all roms for security reasons, but I'm not familiar with Visionary. Are you saying that Visionary remounts the sdcard as exec for you? Or that it's already that way by default for the stock rom? If so, then yes, you can leave gfree on your sdcard. You can check by running mount in the terminal. You should see an entry for /sdcard with all of its options after it. If you see noexec in there, you will either need to move the files to the phone or remount your sdcard with the exec option instead.
If you want to copy files over to your phone while rooted, you could use Root Explorer (probably easiest way). I believe there are other free programs that allow r/w access, but I haven't tried anyway. Otherwise, you should be able to copy over the files in Terminal. I think the data partition is mounted as r/w but you can verify with the mount command mentioned above (on the line containing /data, look for either rw or ro). If there is a rw, then just use the copy command to copy the files where you need to:
Code:
su
cp /sdcard/gfree /data/local
If the data partition is mounted as ro, you'll need to remount as rw first:
Code:
su
mount -o remount,rw -t ext3 /dev/block/mmcblk0p26 /data
Pretty sure that won't be needed though.

ianmcquinn said:
By default on my phone (running CM6), the sdcard mount point is mounted with the noexec option (so no direct execution of any binaries).
Click to expand...
Click to collapse
ooh, ok, thanks, I never knew that. My apologies, that looks like why it's not running then.
If you want to copy files over to your phone while rooted, you could use Root Explorer (probably easiest way). I believe there are other free programs that allow r/w access, but I haven't tried anyway. Otherwise, you should be able to copy over the files in Terminal. I think the data partition is mounted as r/w but you can verify with the mount command mentioned above
Click to expand...
Click to collapse
Yeah, /data is mounted as rw by default, so should be fine to copy as you said.

Alright. This WORKS for running gfree
but for the step that makes the root "stick" according to the guide here...
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
where i says :
"You now have read-write access to your /system, hboot, and recovery partitions. But you still need to "lock in" root, and give you 'su' access in the future. So just do:
# /data/local/tmp/root
# sync
"
I can't find /data/local/tmp/root
so it fails to run..
any suggestions on this?
gfree runs fine. it says done when I did ./gfree -f
thanks guys for all the help!

kwhkkwhk said:
# /data/local/tmp/root
# sync
"
I can't find /data/local/tmp/root
so it fails to run..
any suggestions on this?
Click to expand...
Click to collapse
root is the binary that actually does the rooting, it's included in the gfree_temp-root zip. Did you copy that to /data/local/tmp or did you copy it somewhere else?

the only thing i did, if you were able to see my previous problem,
was just copying the gfree file over to the /data/local and running it
by ./gfree -f
other than that, i copied nothing else, since the guide using adb and the commands used moved nothing other than the gfree file i moved to /data/local
I didn't use the gfree_temp-root.zip folder, i used the gfree_02.zip (permaroot) folder.
and i temp rooted using visionary to get the needed gfree file onboard.
then do i need other filed then?
thank you so much for the quick reply.

kwhkkwhk said:
then do i need other filed then?
Click to expand...
Click to collapse
Yeah, root is actually just a script that installs things like busybox and su for you (see my earlier post).
You should copy those files to the proper locations listed in the wiki (pretty much every file but rage). It'll make life easier (otherwise, you'll have to do all of that stuff manually).
Congrats, you almost have a fully rooted phone.

THank you so much!
and thank you to all of you guys who helped me!
I managed to root my phone finally! Without adb!
YAY

[Q] busybox installed, but where?

Hi there,
i'm actually trying to do the wimax backup found here:
http://forum.xda-developers.com/showthread.php?t=887900
I went through all of this trouble trying to install busybox until I found out that Titanium backup already installed 1.16 on my phone. However I can't seem to find where it was installed to and the,
busybox sed -n '/BEGIN CERTIFICATE/,$p' /dev/mtd/mtd0 > /sdcard/rsa_OEM.key
command isn't working. Any thoughts? Sorry if this is the wrong spot to post. I'm still getting the hang of this forum.

I have the same problem. I think I'm getting this error in the terminal emulator because I don't have the system Busybox installed, just Titanium's app busybox, which is apparently different?. When I try to run Busybox installer, it errors saying I'm possibly not nand unlocked... I used UR3 and UR forever, and can confirm that I am S-Off. Doesn't S-Off = nand-unlock?

I haven't played too much with busybox to know much of its capabilities, but if you want to know the directory it is located in, run this from Terminal Emulator, or adb.
find -iname "*busybox*"
that will get you any and all file listings with busybox in it.

says denied, so I typed su, and get the #
then I type the find command, and tells me that 'find' is not found.
topdawgn8 said:
I haven't played too much with busybox to know much of its capabilities, but if you want to know the directory it is located in, run this from Terminal Emulator, or adb.
find -iname "*busybox*"
that will get you any and all file listings with busybox in it.
Click to expand...
Click to collapse

greyopaque said:
says denied, so I typed su, and get the #
then I type the find command, and tells me that 'find' is not found.
Click to expand...
Click to collapse
you should be able to run find without a hitch. I have had issues running a find while executing a remove, but find had always worked...
try remounting the system:
Code:
su
remount rw
find -iname "*busybox*"
Edit: I just ran find with only SU. What rom and kernel are you running? The only two things I can think of are:
1: The dev removed it from the rom
2: User error-- ensure the commands are lower case, there is a space where appropriate (denoted by ">")
Code:
find>-iname>"*busybox*"

The busy box that tb installs doesn't have all the commands. I had to install from the market to get all the commands.
Sent from my PC36100 using XDA App

its in system/bin most of the time but can be in different spots

Usually you can find busybox in /system/xbin

OMG... I feel stupid... I had install location set for SDCard. That's why busybox installer was failing. I changed it back to auto, and installed busybox, and now everything is working!

Don't waste your time with the rsa keys backup. You'll never be able to restore them.
Use the recovery (amon's 2.2.x) to make a backup of the entire wimax partition. Should the need arise, recovery will be easy. To date, i've yet to see instructions how to restore just the keys.

That's exactly what I did. Thanx!
gpz1100 said:
Don't waste your time with the rsa keys backup. You'll never be able to restore them.
Use the recovery (amon's 2.2.x) to make a backup of the entire wimax partition. Should the need arise, recovery will be easy. To date, i've yet to see instructions how to restore just the keys.
Click to expand...
Click to collapse

[Q] Why can't I seem to root?

Hey! So I got my G2 from a member on here last night (woohoo!) but I can't seem to root it. I tried every method on here including visionary and gfree. I had some success with gfree since I was able to sim unlock it. When in bootloader I get 's-off' on the first line. But when I go into Rom Manager it tells me I'm not rooted and when I type 'su' into terminal I get 'suermission denied'. Any help here? I really need to flash a new ROM due to ORD.
And just some info from System Info in the boot loader even though I think it's not needed here.
OS ver.-1.22.531.8
eMMC- unknown 2151MB 4407295sectors
Also under IMAGE CRC
hboot: 0x6570c0db
boot: 0x1b87420d
recovery: 0xd4af6ad9
system 0x9f52fea6

Any Update???

OK so you were able to get S-OFF via gfree but not permanent root, when you followed the gfree method, the last step (before the verify) of the gfree rooting guide on the wiki (not sure if that's the one you used) has you run a command to "lock in" root:
You now have read-write access to your /system, hboot, and recovery partitions. But you still need to "lock in" root, and give you 'su' access in the future. So just do:
Code:
# /data/local/tmp/root
# sync
Click to expand...
Click to collapse
I suspect this is where it went wrong.
You should be able to use the same method again to get perm root, just skip the gfree parts. Summary:
1. Get all the files on your phone (they are probably already there)
2. Get temp root using rage
3. Run the command (script) that I listed above
Link to the full instructions: http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#How_To_Get_R.2FW_Access_.28Permanent_Root_.2F_.22Permaroot.22.29

I tried the wiki method three times, making sure I typed everything correctly. After I type the line you put up I get a series on lines that show that some files can't be shown (I dont remember the exact ones off the top of my head, I'll redo it soon so I can tell you which ones). I also tried it with two different SD cards.
SO I found the errors in another thread started today:
Code:
/data/local/tmp/root
mkdir failed for /system/xbin, File exists
cp: can't stat '/system/xbin/busybox': Not a directory
Unable to chmod /system/xbin/busybox: Not a directory
/data/local/tmp/root: /system/xbin/busybox: not found
cp: not found
cp: not found
Unable to chmod /system/bin/su: No such file or directory

Strange, /data/local/tmp/root is just a script that does all of the stuff to get you permanent root, not sure why it shouldn't be working for you.
I think once you are temp rooted you should be able to install CWM recovery and use that to install a new (pre-rooted) ROM. If you are not ready to or don't want to jump into a custom ROM you can load the stock pre-rooted ROM and should not even have to wipe (would advise a nandroid backup of course)
http://forum.xda-developers.com/showthread.php?t=836042

raitchison said:
Strange, /data/local/tmp/root is just a script that does all of the stuff to get you permanent root, not sure why it shouldn't be working for you.
I think once you are temp rooted you should be able to install CWM recovery and use that to install a new (pre-rooted) ROM. If you are not ready to or don't want to jump into a custom ROM you can load the stock pre-rooted ROM and should not even have to wipe (would advise a nandroid backup of course)
http://forum.xda-developers.com/showthread.php?t=836042
Click to expand...
Click to collapse
I should try temprooting again and flashing CWM. And The only reason I want to root is to flash custom roms. lol.
EDIT: Well that didn't help. I followed the guide for temproot. I did get the root prompt (#) in terminal, but when testing with 'su' gives me 'su:not found'. And CWM still tells me I'm not rooted and wont let me flash the recovery.

Try using visionary to temp root, that may yield more success.
You may want to use ADB to pull out the remnants from your previous attempts.
If you have # in the terminal you should not need to su.
If you can't flash CWM using ROM manager try this method instead http://forum.xda-developers.com/showthread.php?t=902493

With visionary I push temp root, it makes me wait for like 10 minutes, and does nothing. I was just doing su to see what it does. I'll try removing everything with adb and redownloading all the files. Anyway, what's the command to remove with adb? lol

Open an ADB shell and use the rm command to remove individual files, I would remove everything you ADB pushed originally.
Code:
rm /sdcard/su
rm /sdcard/Superuser.apk
rm /data/local/tmp/rage
rm /data/local/tmp/busybox
rm /data/local/tmp/root
Will only run if you have root access (a # prompt) and you may get errors with some since clearly something isn't as it should be on your system.
Did you try using the flash_image utility to flash CWM?
Also if you can flash the engineering hboot you should be able to load CWM from fastboot.

So I removed the files, redownloaded, and redid the wiki root method.
Still no luck. Same error as posted before. This is getting on my nerves. lol

Did you try to install recovery using this method?
If that didn't work did you try to install the engineering HBOOT?

raitchison said:
Did you try to install recovery using this method?
If that didn't work did you try to install the engineering HBOOT?
Click to expand...
Click to collapse
I will attempt these methods soon and report back.

[Tutorial][S-on]Temp root Wildfire s

Original Thread
qzfive said:
In attempt to get root apps working on my Chacha after obtaining root shell via zergRush, I remembered an old exploit that my old Desire Z used called VISIONary+ that ran an exploit called rageagainstthecage (has since been patched by HTC) and mounted a ramdisk at /system/xbin, copied the su and busybox binaries to this ramdisk, and installed Superuser.apk as a normal application, which allowed for an almost fully functional root until reboot.
I opened up the VISIONary.apk with WinRAR and found a shell script with individual shell commands which match everything the application does. I typed these commands into adb shell running from my computer with my Chacha connected:
adb shell /data/local/zergRush (to obtain temproot via shell)
Once zergRush was done:
adb remount
adb shell mkdir /system/xbin (told me it already exists, assuming this is normal)
adb push Superuser.apk /data/app/
adb shell chmod 0644 /data/app/Superuser.apk
adb shell mount -t tmpfs none /system/xbin (this creates a ramdisk out of /system/xbin for the su and busybox binaries since they can't be pushed to the physical /system/xbin due to locked bootloader)
adb push busybox /system/xbin
adb shell chmod 4755 /system/xbin/busybox
adb push su /system/xbin/su
adb shell chmod 4755 /system/xbin/su
adb shell /system/xbin/busybox --install -s /system/xbin
After I typed all of that into adb on my computer, I obtained temproot on my Chacha (opened SetCPU, was asked for a Superuser prompt, haven't tested anything else yet). If anyone is willing to try this, please do so and report back. If this is better suited in the Development section, please inform me and I will remake this in Development.
EDIT: a modified su/Superuser.apk was required for this to work on newer Sense ROMs (Chacha included) - I have attached the modified su binary (must unzip) and Superuser.apk
VISIONary+ obtained from: http://android.modaco.com/topic/320350-19nov-r14-visionary-one-click-root/
Modified su/Superuser.apk from: http://forum.xda-developers.com/showthread.php?t=886999&highlight=superuser
-----
EDIT 2: attached a .zip which contains a .bat script which executes these commands for you, to make it easier and quicker to apply/reapply this temp root. Use the contents of temproot.zip instead.
Click to expand...
Click to collapse
Test it by myself and it works.
If you're running zergrush more than once you need to remove boomsh and sh.
type the following into adb shell:
1) "rm /data/local/tmp/boomsh"
2) "rm /data/local/tmp/sh"
App tested to be OK
-setcpu
-Titanium Backup (Backup and restore Data app only.)
-Root Explore (can't edit /system unless s-off)
Something that will never happen unless s-off
-flash custom rom
-flash recovery
-motify system, etc.
Bug:
-Speaker won't work ?

Is there some way not to loose root in such case after reboot ? Otherwise I don't see how temp root could be really useful.

Can we uninstall the stock apps using this method?
Sent from my HTC Wildfire S A510e using XDA App

drsjlazar said:
Can we uninstall the stock apps using this method?
Sent from my HTC Wildfire S A510e using XDA App
Click to expand...
Click to collapse
Something that will never happen unless s-off
-flash custom rom
-flash recovery
-motify system, etc.
Have I answered your question ?! NO

Reboot problem.....
It worked pretty well but my phone reboots if I keep it locked for a while.Any suggestions????

Wow, nice to know this works on other devices
The only "bugs" I noticed when I do this on my Chacha (similar device/same processor), is that the SD card unmounts itself when zergRush runs (might be part of the exploit zergRush does?), and that if I do this too early (ie. the "HTC Quietly Brilliant" bootanimation), it throws my phone into a bootloop -- haven't noticed any speaker bugs as of yet.
EDIT: I only get reboots when something tries modifying the /system partition - because my device is still S-ON (I'm trying to find an XTC Clip), the bootloader triggers a reboot
--Just another thought: since this mounts a ramdisk, would it work on any device that's temprootable?

Hmmm. Is it possible to make a fake flash of the recovery? Anyone try this?

qzfive said:
Wow, nice to know this works on other devices
The only "bugs" I noticed when I do this on my Chacha (similar device/same processor), is that the SD card unmounts itself when zergRush runs (might be part of the exploit zergRush does?), and that if I do this too early (ie. the "HTC Quietly Brilliant" bootanimation), it throws my phone into a bootloop -- haven't noticed any speaker bugs as of yet.
EDIT: I only get reboots when something tries modifying the /system partition - because my device is still S-ON (I'm trying to find an XTC Clip), the bootloader triggers a reboot
--Just another thought: since this mounts a ramdisk, would it work on any device that's temprootable?
Click to expand...
Click to collapse
Yes...I have used zergRush many times and it unmounts the SD card everytime.....so I think its not a bug......you answered my question of reboots tough,thanks.
And maybe this temproot method just might work for every device.

It doesnt work on htc pico (s"on).
Zergrush dont succeed
Sent from my Dell Streak using XDA App

jitin02 said:
It doesnt work on htc pico (s"on).
Zergrush dont succeed
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
Maybe HTC patched zergRush on the Pico/Explorer

Guyz, ya don't have to fight with mills, take a look at my topic: http://forum.xda-developers.com/showthread.php?p=21167193