Develop Bugs

[Q] Help on rooting

Sorry for making you read this if I made a nooby mistake.
So I rooted my Slide, and flashed the Eng-release to it. When I use ROM Manager to install the CM6 onto it, I can't get past touching reboot into Clockwork Recovery. I already flashed the Clowckwork into it (I think; you just need to push the Flash ClockworkMod Recovery button right?), but when I push the reboot into it button, nothing happens.
I tried the Fix Permissions button, and it says "An error occurred while attempting to run privileged commands!" That means that the app doesn't have root access, right? How do I give the app root access? I tried two superuser apps, one from the Market and one from this website, the one with a Ninja. When I choose preferences on the superuser app, it just hangs until I get the Force Close error.
How do I grant my app root access? I know I rooted my Slide because when I connect it to my phone and use adb shell, the pound sing comes up.

What method did you use? Did the phone have the 1.35 OTA Update?
Try this: download terminal emulator from the market, its free.
Turn on: you will see a "$" symbol type "su" (w/o qoutes)
if you see this "#" you are rooted..
Im sure there are easier other ways to check, thats just what I do. I know you didn't install the rom, so don't worry about that yet.
Chances are you arent rooted, I dont what adb shell would say, since I didnt have to use it directly, I just used my windows cmd prompt.

After looking at the other post a few below this one about the exact same problem that I had, I did what he did and copied the update.zip to my phone and booted into recovery. Thanks for the help, though I'm ok now.
Btw, I did have the terminal, and it did have the # sing
Sent from my T-Mobile myTouch 3G Slide using XDA App

[Q] Issues trying to Perm-Root using Visionary r14

So after 7 attempts, i decided i should seek help.
I've been trying to root my g2 using VISIONary r14.
1. I installed visionary r14 [i have usb debugging on] i leave all the check boxes unchecked and hit temp root
2. after temp root is finished, i hit attempt perm root.
phone reboots. i see superuser permission in the app drawer, all seems to be
fine.
3. Now I plug my phone to my PC via usb [i have the androidSDK and all drivers installed properly]
i change directory to C:\AndroidSDK\tools\
check adb devices and my device is listed.
then i shoot the following commands
adb push wpthis-OTA.ko /data/local/wpthis-OTA.ko
adb push hboot_7230_0.84.2000_100908.nb0/data/local/hboot_7230_0.84.2000_100908.nb0
adb shell
su
and this returns permission denied.
Ive searched everywhere and everyone says when the superuser prompt shows up check "Remember" and click yes. However this does not show up for me, at all.
I even go into terminal and try it, terminal also gives me 'Permission Denied'
any help anyone?

I'd just do it using the rage method. You obviously understand how to use some simple commands in adb, it's just that there's a few (read: not many) more. It's stickied in the development section.
Sent from my T-Mobile G2 running Cyanogenmod.

Yes rage way is the way to go. I think its a total of about 4 lines you need to enter
Sent from my HTC Vision using XDA App

yeah i ended up using the rage method, it was a lot easier than i thought it would be.

I did it using visionary r13 and terminal emulator. No pc. Go to youtube look up Blackprince310 he made a video on it. If it it doesn't work try permroot option on r13.
Sent from my T-Mobile G2 using XDA App

I would love to go the rage way, but I cannot get any permissions to do so...
Visionary r14 gives me a parsing error and does not install....
I've spent about 8 hours today trying to get this done!!! sigh!

Crey23 said:
I would love to go the rage way, but I cannot get any permissions to do so...
Visionary r14 gives me a parsing error and does not install....
I've spent about 8 hours today trying to get this done!!! sigh!
Click to expand...
Click to collapse
What steps have you taken? The rage way does not require visionary at all.
Sent from my HTC Vision using XDA App

shortlived said:
What steps have you taken? The rage way does not require visionary at all.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
right!!! I've been sitting at my pc for about 8 or 9 hours trying to root.
I continue to get adb: permission denied message no matter what I try. I follwed the adb for dummies guide that didnt work. I tried the VISONary r14 apk, I can't even open it.....
I'm beggining to wonder if I should run recovery first, get back to stock, and then try to root....how will that affect all my apps? Will it work?

Well you can always back them up with titanium backup. But yea i think you should do a factory reset then try the rage method. Follow the guide word for word. If you still got problems post em here i will try to help as much as i can. The whole process should take around 5min.
Sent from my HTC Vision using XDA App

I dont know how to link to a post with the xda app so here is the guide quoted
trigeek said:
There's already a guide here for obtaining permanent root using VISIONary, but some folks in #G2ROOT are having issues with the way that VISIONary modifies parititons. Using rage directly is a bit cleaner, since you know exactly what it's going to touch at each step of the way. I did NOT come up with any of this on my own, I'm building completely off of work that others have done. Speaking of which-
None of this would be possible without the tireless work that scotty2 put in. He stayed with the project for well over a month, through lots of smashed hopes and dead ends, until the solution was finally found. Were it not for his work, as well as the help of a few other key folks- we wouldn't be here. He deserves our thanks and some donations! We're talking hundreds of hours of work here, a couple bucks is not too much for that. His paypal is:
[email protected]​Send him some love! I'm not asking for anything myself, because I spent a half hour putting this together, and that doesn't deserve any donations!
[size=+2]G2 ROOT INSTRUCTIONS[/size]
=================================================
These are modified instructions based on the ones posted at http://bit.ly/g2root that use Visionary. A number of people have run into issues with the way that Visionary juggles around temporary partitions, and using the original root exploit is a much easier, and cleaner method for achieving permanent root. This tutorial will walk you through the rooting process by first achieving temporary root, and moving on to permanent root.
[size=+1]REQUIREMENTS[/size]
=================================================
Visionary disabled at boot or uninstalled completely
Android Terminal Emulator app
ADB
vision-combined-root.zip (Attached to this post, OR these two files: )
G2TempRoot.zip (http://forum.xda-developers.com/showthread.php?t=797042) NOTE: only download the files! Don't follow these instructions yet
vision-perm-root.zip (http://forum.xda-developers.com/showthread.php?t=833965) NOTE: again, just download the files from the thread.
In the commands to run below, $ or # represent the prompt and should NOT be entered as part of the commands.
[size=+2]VERY IMPORTANT![/size]​Visionary has caused filesystem corruption for some users during the rooting process. Before attempting the instructions below, make sure that you have "auto run on boot" turned OFF, and reboot your system. Since you will not need visionary anyway after this, you might as well just uninstall visionary and reboot NOW before doing anything.
[size=+1]TEMP ROOT[/size]
=================================================
ON YOUR PC:
Unzip the G2TempRoot files to a folder. From a cmd window or terminal, navigate to that folder and execute these commands:
Code:
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
ON YOUR PHONE:
Launch Terminal Emulator
/data/local/tmp/rage
Wait for the message: "Forked #### childs."
Menu > Reset Term - Terminal Emulator will exit.
Launch Terminal Emulator, it Force Closes. Launch a second time, and you'll have a root shell
**NOTE**: in the original directions from the XDA thread, you are instructed to run the /data/local/tmp/root script here. DON'T do this
just yet. Leave the terminal window open.
[size=+1]PERM ROOT[/size]
=================================================
ON YOUR PC:
unzip the vision-perm-root.zip and navigate to that folder. There will be four files. You will need to push two of these to your phone- hboot-eng.img, and one of the wpthis-[..].ko files.
If you HAVE applied the OTA update, push wpthis-OTA.ko.
If you HAVE NOT applied the OTA update, push wpthis-pre-OTA.ko.
Code:
$ adb push hboot-eng.img /data/local
$ adb push wpthis-OTA.ko /data/local
ON YOUR PHONE:
You should still have terminal emulator up, at a root prompt. Now run:
Code:
# insmod /data/local/wpthis-OTA.ko
You should see:
Code:
init_module 'wpthis-OTA.ko' failed (Function not implemented)
That means it worked. This next step is CRUCIAL. You must make sure that you are writing to the proper partition here or you could brick your phone. To be absolutely clear- the partition is mmcblk(zero)p(one)(eight)
Code:
dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18
You should see some messages indicating that it was written. Next, run:
Code:
# /data/local/tmp/root
This will lock in root, and give you 'su' access in the future. Next, run:
Code:
# sync
Now wait at least a minute, just to be safe. After waiting, reboot your phone using the power button. After it finishes starting up, launch the terminal emulator, and type 'su'. You should get the prompt asking you to grant permissions. If you got the prompt, congratulations! You have permanent root!
Click to expand...
Click to collapse
Sent from my HTC Vision using XDA App
Sent from my HTC Vision using XDA App

i need help, i perm rooted my phone now it got stuck at the HTC start up! what should i do?? pls reply ASAP!

htc desire gsm keeps restarting

hi my htc desire keeps restarting when i flash any gingerbread miui rom i have tired data2ext and a2sd and have wiped and also formated my sdcard and stil have same problem with both but it works fine with all other roms and the froyo version of miui. please help

What hboot are you using and how did you root your phone?
Sent from my HTC Desire using xda premium

hi im using normal hboot-0.93.0001 i used unrevoked to root my phone i am not really a noob i have flashed and rooted many phones but for some strange reason all other roms including miui froyo work on my phone but gingerbread miui wont it loads up to the home screen and then just reboots ive tried data2et version and a2sd version and same thing happens with both versions.i have also tried using diffrent recoverys amon-ra,clockwork etc and still get the same problem.

You need to understand what is going on under the hood.. Getting an adb logcat is the way to go..
Code:
Windows>Start>Run
echo "null" > log.txt
start log.txt
adb logcat > log.txt
Use Notepad++ to associate with the txt file and reload the file every couple of seconds while keeping the cmd shell in the background.. See what's happening just before it reboots. It could be anything from a bad script to a bad module

Have you tried gingerbread 2.8, its simple and a very plain ROM, I have had issues with miui roms with my desire, if that doesn't work I will keep looking my self, sorry I'm not very insightful, you have an odd problem.
Sent from my HTC Pyramid using xda premium

Nice one Droidzone, I will have to try that also.
Sent from my HTC Pyramid using xda premium

Hi droidzone thanks for your reply could u please maybe help me and tell me the steps to get the log cat i know how to access adb by cmd but thats about it im a noob when it comes to adb commands and dont know much about it and didnt really understand the commands that u asked me to do,do i enter those while in adb or before.

casanova786 said:
Hi droidzone thanks for your reply could u please maybe help me and tell me the steps to get the log cat i know how to access adb by cmd but thats about it im a noob when it comes to adb commands and dont know much about it and didnt really understand the commands that u asked me to do,do i enter those while in adb or before.
Click to expand...
Click to collapse
Once you open a command line prompt in the folder where adb is installed (or anywhere else, if the file adb.exe is in your Windows path variable-Dont worry about that if you dont know), you can directly type each line of the commands starting from step 2.
Before that, install Notepad+, and associate .txt file to open with it by default..
By the way, you have to start typing those commands directly after rebooting from recovery after installing the Rom..

hi droidzone i have installed notepad++ but dont understand how to install Notepad+, and associate .txt file to open with it by default. also my adb is located in c:\androidsdk\tools that is what i type in cmd to get adb working and if i type adb devices it shows my device.also i typed the commands u gave me once in adb and it says "the process cannot access the file because it is being used by another process."

casanova786 said:
hi droidzone i have installed notepad++ but dont understand how to install Notepad+, and associate .txt file to open with it by default. also my adb is located in c:\androidsdk\tools that is what i type in cmd to get adb working and if i type adb devices it shows my device.
Click to expand...
Click to collapse
Hmm.. I seem to be offering more Windows support than Android!
I meant Notepad+. Hold Shift, rightclick any text file, Choose Open with Notepad+ as default. You can go to your adb folder like you normally do and then type each line I posted and hit Enter after each time. You can also make a batch file with all those commands (search Google for that if you dont know how)

hi thanks i have made notepad+ to open as default but when i type the commands u told me it says "the process cannot access the file because it is being used by another process."

casanova786 said:
hi thanks i have made notepad+ to open as default but when i type the commands u told me it says "the process cannot access the file because it is being used by another process."
Click to expand...
Click to collapse
Hmm yes, that can happen if you have more than one adb.exe process running in the background because you exited it by closing the command shell with the close button instead of typing
Code:
exit
after done with it.
Use Ctrl+Alt+Del or Process Explorer to terminate the background adb.exe processes

Root doesn't work.

hello all, i rooted my a100 via the guide, and the root checker says its rooted, but i cannot get into shell. When i enable filesystem browsing, it won't allow me. Not even a prompt from su.
Sent from my LG-P999 using Tapatalk

joeyxl said:
hello all, i rooted my a100 via the guide, and the root checker says its rooted, but i cannot get into shell. When i enable filesystem browsing, it won't allow me. Not even a prompt from su.
Sent from my LG-P999 using Tapatalk
Click to expand...
Click to collapse
Did you install superuser from the market?

Im having a similar problem. I can verify that su has been moved to system/xbin/su but busybox nor Superuser detects root... Ive used all guides I can find to work this.

http://www.acertabletforum.com/foru...ssion/1167-rooting-iconia-a100-made-easy.html

Tried with no results

Did you update su binary?

Educate me, If you mean by trying to use superuser and update it through the settings, it was a no go.

I had a similar problem. It was showing as being in the /system/xbin folder, but I didn't have root. In my case, I was failing to move the su file out of the folder after extraction and put it in the /mnt/sdcard directory so the commands were just creating a blank su file in /system/xbin
Sent from my Acer Iconia Tab A100 using Tapatalk

How did you go about fixing the issue?

After extracting the zip I moved the su file (the one with no extension) from the extracted folders and tried the lines in the terminal again and it worked.
Sent from my Acer Iconia Tab A100 using Tapatalk

Ahh, Yea. Ive tried that already with no luck. It shows the file, roughly 25kb in the folder, but it also shows I have no root. Ive tried restarting, uninstalling superuser and reinstalling, etc...

did you ever get your tab rooted?

mvan4310 said:
Ahh, Yea. Ive tried that already with no luck. It shows the file, roughly 25kb in the folder, but it also shows I have no root. Ive tried restarting, uninstalling superuser and reinstalling, etc...
Click to expand...
Click to collapse
Could you post what build number your running, also after you've run the commands for copying over the su and download superuser from the market, if you open terminal emulator up and type su what does it output?
Have you tried this???
http://forum.xda-developers.com/showpost.php?p=21409649&postcount=177

painter_ said:
Did you install superuser from the market?
Click to expand...
Click to collapse
yes, after i did what the guide told me to do. i have the latest version of Honeycomb given out via OTA update. now in superuser, i didnt update it, as it fails evey time. also, when i type "su" into terminal, nothing happens. im trying to put the build.prop that was modded recently, so i can get an app made for gingerbread onto here, as well as getting a PS3 controller to connect, but both need root. i just dont understand why the root checking app says i have it, when i really dont. guess it just checks for the su file in xbin? i really hope someone can point me in the right direction

First, I really need to know the build number "the latest one the ota can give" isnt sufficiant. It can be found under settings -> about tablet toward the bottom.
Second, saying "nothing happens" isnt true.. something always happens... either it just spit out another line with $ or the next line showed up with a #. How long did it take for the next line to show up after you typed su in the terminal?
The more details you can provide, the better I can help... this isnt directed at the above poster but all users in general.
One thing you might want to try is to uninstall the superuser app, then run this command:
/system/bin/cmdclient ec_micswitch '`rm /system/xbin/su`'
and then go back through the root process (or use my quick root script). The above command will get rid of any bad su file that might be in /system/xbin.
Sent from my MB860 using XDA App

Build Acer_A100_2.007.04_COM_GEN1
Upon typing in su in the terminal, is shows another line with $. Ive tried your ten second root yesterday looking for other options, but it says permission denied, even when trying to run from other directories. Ive even opened the root.sh file and copied the whole file and pasted in the term and every command gives a permission denied but the 3 commands that you see everywhere else. when typing in ls -l /system/xbin/su I get around 26000 bytes. So the file is there.

mvan4310 said:
Build Acer_A100_2.007.04_COM_GEN1
Upon typing in su in the terminal, is shows another line with $. Ive tried your ten second root yesterday looking for other options, but it says permission denied, even when trying to run from other directories. Ive even opened the root.sh file and copied the whole file and pasted in the term and every command gives a permission denied but the 3 commands that you see everywhere else. when typing in ls -l /system/xbin/su I get around 26000 bytes. So the file is there.
Click to expand...
Click to collapse
Can you try the attached su binary. I don't recall where I got it from since is been a while but I've had issue with 2.3.2 su binary before and the attached is what I use to root mine.

S-OFF Failed？

I've followed the instruction of firewater s-off.
After successfully pushed 'firewater' to /data/local/tmp and changed the permission to 755, I've typed '/data/local/tmp/firewater' but nothing happened.
View attachment 2809420
It's the same problem under Windows 7.
Whats more, the file 'firewater' in /data/local/tmp disappeared automatically after '/data/local/tmp/firewater' has been executed.
Another question was that I had never entered 'su' after 'adb shell', but still got root permission?
Tried with both my MacBook Pro and desktop computer and got exactly the same results.

Seems you have got su permissions maybe you shouls check its log

Same issue, after adb push, I don't get SU request and everything else goes quite.
Sent from my HTC One_M8 using XDA Premium 4 mobile app

Some people have said using a different Superuser app gives a better result so perhaps change and see how you get on