Develop Bugs

[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.

[Q] Metamorph

I'm on a HTC Desire, rooted with unrevoked and I have flashed the Oxygen ROM. I want to install custom framework, but every time I try to open Metamorph, I get the ''some files could not be extracted and set up. please make sure you have enough space in /system''. I have tried
''adb remount
adb shell
ln -s /system/xbin/busybox /system/xbin/cp'', but still without luck. Could someone please tell me what to do? I'm not very skilled at this, so please explain carefully. Thanks!

Isnt it because of the fact you need BusyBox from the market in order to get Metamorph to work, but BusyBox is not working for Desire yet.
it says so in the description of BusyBox in the market.

If you want busybox download titanium backup and open it, you will see how obtain busybox working on desire It worked for me

qweasdfzxc said:
If you want busybox download titanium backup and open it, you will see how obtain busybox working on desire It worked for me
Click to expand...
Click to collapse
Thanks, but am I supposed to do something after I've installed busybox with titanium? Or just open MM? cus that didn't work. And also, why can't I delete the 'busybox' file from /xbin? Sorry for being such a noob, but you're my hero if you can help me with this!

I have no idea how metamorp works or what you are trying to do, but if you want to write to the system partition while booted you need to be S-off.
If you want to delete busybox and you're not S-off, you need to do it with adb while in recovery.

TheGhost1233 said:
I have no idea how metamorp works or what you are trying to do, but if you want to write to the system partition while booted you need to be S-off.
If you want to delete busybox and you're not S-off, you need to do it with adb while in recovery.
Click to expand...
Click to collapse
alright, thanks. which adb command? tried adb uninstall, but that didn't work, unless i did something wrong

adb shell
rm /system/xbin/"whatever you are trying to remove from there"
To see what is in there:
ls /system/xbin
But i don't think uninstalling busybox will fix your problem since you got a error regarding /system and you won't be able to write to there unless you're S-off.

TheGhost1233 said:
adb shell
rm /system/xbin/"whatever you are trying to remove from there"
To see what is in there:
ls /system/xbin
But i don't think uninstalling busybox will fix your problem since you got a error regarding /system and you won't be able to write to there unless you're S-off.
Click to expand...
Click to collapse
Ok, thanks a lot anyway!

[Q] unrevoked worked but phone still not rooted?

It took me 4 hours to get unrevoked root my phone (turned out that the actual version is buggy) but somehow it seems not "really" rooted.
I want to install titanium backup, so when I start it I get this popup to grant root access but titanium still says it is not ok.
I can do a "su" in the shell but not a whoami. - I don't understand why.
If I go into the recovery menu it says ClockworkMod Recovery v.3.0.0.5
Bravo PVT1 SHIP S-ON
HBOOT 0.93.0001
Microp-031d
Radio-5.10.05.23

If you bothered to check the Titanium website you'd see you need to click the 'Problems' box to install BusyBox. Without this TB won't work
http://matrixrewriter.com/wiki/tiki-index.php?page=TB+-+User's+guide

EddyOS said:
If you bothered to check the Titanium website you'd see you need to click the 'Problems' box to install BusyBox. Without this TB won't work
http://matrixrewriter.com/wiki/tiki-index.php?page=TB+-+User's+guide
Click to expand...
Click to collapse
It even says on first Titanium Backup launch!

Yep...pops up a message. Click "Problems?" at the bottom for a reliable busybox.

Believe me I bothered a lot to look around and I tried for hours and hours.
Titanium complained about not having root privileges not about busybox. And in the help on their homepage there was this guide "how to check if your phone is rooted properly" by issuing the su command followed by whoami which is obviously misleading.
However, thank you for pointing me in the right direction. It seems to work now.

OK. Now I am convinced - this was completely not my fault. Not only is the documentation missleading, the software is buggy as well.
Going to the Problems? Menu suggests it would fix your issues with busybox by installing it and such...
Well, it does download it to your device but it is not usable until you install it manually via the android sdk in recovery mode. Until then you will not get an app listing. I wonder where to find this little detail in the docu (talking about laziness)

No one else seems to have this issue so not sure what you're doing differently
I just went to running a custom ROM so once rooted didn't have any issues

When you flash your phone with unrEVOked, try using Clockwork 2.5.0.7 as I used this version and it worked 1st time.

SOLVED
Thanks guys. I already solved all problems. It was horribly difficult to get over all these pit falls but finally I reached my goal (a Titanium Backup).
What caused me most trouble was the unclear description of Titanium Backup, especially the part in which they state "if whoami does not respond so and so you are not root"... BULL****!!!
"Short" list of how I got my Desire with HBOOT 0.98 rooted and installed Titanium Backup:
Unrevoked root, but not the latest version 3.32. This one will stop with an Error: Cannot get root. Is your firmware too new? or something similar. Instead use version 3.2
Install Titanium and start it. Superuser will popup and ask for permissions - grant.
Make the changes in the application settings that Titanium asks for (I think usb debugging and allow applications that are not from market) and forget about the message telling you you have no sufficient root privileges, that is not true - I guess what they really mean is that busybox is not installed on your system (would be nice if they'd said what they mean).
Go to the "Problems?" button and let Titanium install Busybox.
... not over yet!
Titanium will now not complain about root privileges any longer but you will still not see any application listings in the software. So maybe there is still something wrong. But what could that be? The root priviliges? WRONG!. Titanium downloaded busybox but did not bother to also install it, although it said it did ;-)
Get the android SDK from Google and install it. (you will also need the Java JDK). You can uncheck most of the packages during installation, probably all. We are only interested in the adb tool that is included in the base installation (I think it is, I also installed the Android SDK Platform tools, SDK Tools and SDK Platform Android 2.2 - just because I was not sure about it).
Boot phone into recovery and connect with the adb shell. (this is a little tool that you will find in the tools subdirectory in the android sdk. You need to start it from the command prompt)
Once connected you need to install busybox manually. Titanium did download the data but did not install! How to do this is described by Loccy here:
Code:
Actually, what I did was use Titanium's busybox:
* install Titanium
* run Titanium
* click the "problems" button and install Busybox
* boot into recovery
* adb shell from my Mac
* mount /system
* cp /data/data/com.keramidas.TitaniumBackup/files/busybox /system/bin
* cd /system/bin
* ./busybox --install -s .
Instead of using the mount commands, listed above I mounted the mentioned directories with the mount option in the ClockworkMod recovery menu, that comes with the unrevoked rooting, because the mount commands did not work properly for me. Also, I had to cd into the /data/data/com.keramidas.TitaniumBackup/files/busybox directory and copy busybox to /system/bin/. from there.
Code:
cd /data/data/com.keramidas.TitaniumBackup/files
cp busybox /system/bin/.
cd /system/bin
./busybox --install -s .
But I might have had a typo.
reboot the device and enjoy.
I should mention, if you NOW issue the suggested "su" and "whoami" commands in a shell that according to Titaniums super HOWTO should tell you if you have root privileges, THEN you will get the right response.
In Conclusion:
Forget about the Titanium howto. If Unrevoked finished with no error you HAVE root privileges, no matter what Titanium tells you. Another indicator: If the superuser popup appears, you should be rooted as well.
Install Busybox either completely manually or with the above described method via Titanium. The busybox setup has worked if you can issue the "su" and "whoami" command in a shell.
@EddyOS: "Noone" might not be entirely true - If Titanium was so clear you would not find tons of "how do I install it" questions in the forum. If it works on some *or most* devices but on others not, this is just an indication for sloppy coding. And a user should not have to spend hours over hours to surf some forums for solutions that should have been provided by the developers in the first place. Some people have a life...

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.

Lost shell root access

Hi,
i have a rooted Desire Z currently running CM9 RC2, and I've noticed recently that my # shell has been replaced by a [email protected]:/ and it seems like I don't have root access there. I can't ls in /data/ for example, and su throws a permission denied error. However, apps that require root access(such as Titanium Backup) still seem to work. I noticed this happen right after I installed and ran Busybox. I did not even install busybox from the app as I already have it. I was just trying to get the apk file for another device with no internet access. I'm not sure if this app is what caused it, but it was when I noticed it.
In any case, short of a nandroid restore how do I get back shell root access and the proper shell?
Thanks.

Most likely your root access under System Settings -> Development was changed from "ADB and Apps" to "Apps Only".
PS: why would you be installing busybox, CM9 came with it (likewise with superuser and su).

Thanks. That worked.
Like I mentioned in my original post
I did not even install busybox from the app as I already have it. I was just trying to get the apk file for another device with no internet access.
Click to expand...
Click to collapse

goister said:
Thanks. That worked.
Like I mentioned in my original post
Click to expand...
Click to collapse
Though your quote here conflicted so wasn't sure :
I noticed this happen right after I installed and ran Busybox.
Click to expand...
Click to collapse

Sorry for the confusion, by running busybox I meant simply launching the Busybox app(which is just an installer, not busybox itself), but not clicking the "install busybox" button in the app to actually install busybox on my phone.