Develop Bugs

[Question] about hboot/superuser/custom roms

I have a few noob questions hopefully someone can answer
I rooted using toasts method part 1 and part 2
I have flipz .6 rooted rom and radio 1.39.00.05.31
Do I always have to go into hboot then select recovery every time or is there a direct path to boot into recovery?
Every time I install custom roms will i have to redownload all my apps every time? If so is there a way to easily back up the apps and restore them?
The superuser permissions app is there after rooting what is it used for?
LxMxFxD - the act of "ROOTING" is the act of giving super user. Super users are accounts on a phone or linux/unix device that can do EVERYTHING on the machine. Like the admin on windows. The whole point of rooting a phone is so you can get super user permissoins.
When i select the superuser permissions app i just see a black screen, should it do more than that?
ccapasso - What you are seeing is normal. The SuperUser Permission app is by default blank. However, once you start using apps that require su permission, such as Wireless Tether, it CAN start to have entries in it. I say CAN because you will notice that when you choose the Wireless Tether app, you will get a prompt asking you to allow. If you choose allow, it will continue as always. However, if you choose Always Allow, you will no longer get that prompt. Also, once you choose Always Allow, your SuperUser Permission app will now show a listing in it. If you simply choose Allow instead, you would still have nothing listed in the SuperUser Permission app.
How do I remove the proprietary apps?
you need to be in the recovery
from the cmd window type
Code:
adb shell
mount /dev/block/mtdblock4 /system
cd /system/app
rm amazonmp3.apk
check this post for a list of apps to remove

can anyone help me out with question 1 or 2?

1) http://forum.xda-developers.com/showthread.php?t=702214 - here's one way to do it...
2) Try Titanium Backup in the App Store - I tend to like it quite a bit.

oubravs2b said:
1) http://forum.xda-developers.com/showthread.php?t=702214 - here's one way to do it...
2) Try Titanium Backup in the App Store - I tend to like it quite a bit.
Click to expand...
Click to collapse
thanks!

[GUIDE] Super EASY Temp Root using normal SD Card

Big props to SAINTH for his guide. Some of my guide is a word for word rip off of his guide. I just copied it and played around to get a simpler way to root. It is still temporary but now when you have "SU" you are messing with the ACTUAL files on the device, NOT a copy on your SD card. Also, programs installed in root mode are still on your device when not in root mode.
I wrote this entire post while tethered to my device using this method.
NOTE: IF SOMEONE COULD GIVE ME A RECOVERY TO FLASH, I THINK WE WOULD HAVE PERMANENT ROOT
OK, I am a dev noob... total noob... please no flaming...
Getting Started: (ONE TIME STUFF)
1) Partition your SD card with at least a 300mb EXT3 partition. I Used gparted in Ubuntu. (ubuntu.com ...download the iso, boot as a live cd, install gparted....google for more details)
2) Download and install from Market: Bar Control. I will explain why in a moment.
3) Download and extract visionroot.zip into your tools directory.
4) Use adb to install programs and transfer files to your device:
On the phone, enable "USB debugging" in Menu -> Settings -> Applications -> Development
On a computer with the Android SDK tools installed and working (adb is included with the SDK, so install the sdk and you will have adb. GOOGLE "adb sdk install" for more details):
adb push busybox /data/local
adb push rage /data/local
adb push root /data/local
adb push rsync /data/local
adb push su /data/local
adb install Term.apk
adb install Superuser.apk
adb shell chmod 755 /data/local/busybox /data/local/rage /data/local/rsync /data/local/root
5) Run Bar Control and select Terminal Emulator to run in the task bar. Early on, when I was playing around with this rooting method, temp root would just disappear. I found it stays if I use Bar Control. I think since Terminal Emulator is in the task bar, android is less likely to kill it. I did this whole post using tethering without root ever going away.
Ok. SETUP stage is now over. From this point on is how you will get root each time you boot up your phone.
Getting Root:
1) On the phone, open "Terminal Emulator" from the taskbar and type:
cd data
cd local
./rage
Wait for it to say "[+] Forked NNNN childs." then press the back button until you are back at the home screen. It will be slow for a bit.
2) Open "Terminal Emulator" again from the task bar and it should force close. It's ok if it doesn't. Just skip to #3.
3) Open "Terminal Emulator" one more time from the task bar and the prompt should display "#". This is the ROOT prompt! You are almost golden now! Then type:
cd data
cd local
./root
You may get some "Killall: Can't kill such and such" messages. Not a problem.
DO NOT hit the back button. You want terminal to keep running. Hit the Home Button.
YOU NOW HAVE ROOT! Superuser should be working too. We may find that we dont need bar control and terminal running. Let me know and I will change my post.

What I've Used Root For So Far
Some people are questioning the value of root without custom ROM's. Here is what i have used ROOT for on this ROM so far:
1) Wireless Tether - this alone is worth it! The 9-5 version from this page works amazingly on the G2:
http://code.google.com/p/android-wifi-tether/downloads/list?can=2&q=NexusOne
2) Uninstall Crapware - I used Titanium to uninstall Web2Go. What a pile of steamy poop. EDIT: The software MAGICALLY reappears after reboot. I can't wait to crack this phone!
3) Back up with Titanium - Most awesome backup program out there. Needs root to work.

good stuff bro ima try this.

this is all well and good, but the point of rooting is the custom roms, we've had a Temp root since day one, but no reason to root it.

yes but
Dalamak said:
this is all well and good, but the point of rooting is the custom roms, we've had a Temp root since day one, but no reason to root it.
Click to expand...
Click to collapse
Yes we did BUT that temp root method didn't allow access to the real files of the device. It accessed copies (simply put I know). This temp root gives ROOT access to the entire device which puts us a GIANT step closer to a permanent solution.
Also, the other temp method couldn't handle installing Apps in one mode and using them in another. Some Apps disappeared at reboot. With this method, Apps that are installed in either mode are always accessible.
Basically I did this for my own device and just wanted to share with others

But of course I thank you for your efforts, you are a god, I meant no disrespect
texasaggie1 said:
Big props to SAINTH for his guide. Some of my guide is a word for word rip off of his guide. I just copied it and played around to get a simpler way to root. It is still temporary but now when you have "SU" you are messing with the ACTUAL files on the device, NOT a copy on your SD card. Also, programs installed in root mode are still on your device when not in root mode.
I wrote this entire post while tethered to my device using this method.
NOTE: IF SOMEONE COULD GIVE ME A RECOVERY TO FLASH, I THINK WE WOULD HAVE PERMANENT ROOT
OK, I am a dev noob... total noob... please no flaming...
Getting Started: (ONE TIME STUFF)
1) Partition your SD card with at least a 300mb EXT3 partition. I Used gparted in Ubuntu.
2) Download and install from Market: Bar Control. I will explain why in a moment.
3) Download and extract visionroot.zip into your tools directory.
4) Use adb to install programs and transfer files to your device:
On the phone, enable "USB debugging" in Menu -> Settings -> Applications -> Development
On a computer with the Android SDK tools (adb) installed and working:
adb push busybox /data/local
adb push rage /data/local
adb push root /data/local
adb push rsync /data/local
adb push su /data/local
adb install Term.apk
adb install Superuser.apk
adb shell chmod 755 /data/local/busybox /data/local/rage /data/local/rsync /data/local/root
5) Run Bar Control and select Terminal Emulator to run in the task bar. Early on, when I was playing around with this rooting method, temp root would just disappear. I found it stays if I use Bar Control. I think since Terminal Emulator is in the task bar, android is less likely to kill it. I did this whole post using tethering without root ever going away.
Ok. SETUP stage is now over. From this point on is how you will get root each time you boot up your phone.
Getting Root:
1) On the phone, open "Terminal Emulator" from the taskbar and type:
cd data
cd local
./rage
Wait for it to say "[+] Forked NNNN childs." then press the back button until you are back at the home screen. It will be slow for a bit.
2) Open "Terminal Emulator" again from the task bar and it should force close. It's ok if it doesn't. Just skip to #3.
3) Open "Terminal Emulator" one more time from the task bar and the prompt should display "#". This is the ROOT prompt! You are almost golden now! Then type:
cd data
cd local
./root
You may get some "Killall: Can't kill such and such" messages. Not a problem.
DO NOT hit the back button. You want terminal to keep running. Hit the Home Button.
YOU NOW HAVE ROOT! Superuser should be working too. We may find that we dont need bar control and terminal running. Let me know and I will change my post.
Click to expand...
Click to collapse

Dalamak said:
But of course I thank you for your efforts, you are a god, I meant no disrespect
Click to expand...
Click to collapse
LOL hahahah thats funny. I'm def not a god at this

Good job man! This will definitely make it seemer on the folks who aren't Linux friendly or lazy folks like me. Oh and btw... you're the futherest thing from a newb! Hahahha! You've been here longer than me. Its rare that I see the real old school guys here anymore. Weren't you in the wizard or tornado sub forum many years ago. You seem familiar...
Oh btw, someone posted a clockwork recovery that was allegedly compatible with the G2 but I don't think anyone had the balls to flash it. Its in the root think tank thread...

Nevermind. I've decided to retract my comment and just try the process to see what happens.

Method worked amazingly well!
Thank you for this!!

Awesome job!
Sent from my T-Mobile G2 using XDA App

Will this work with the 4 click on-device root apk posted in this thread: http://forum.xda-developers.com/showpost.php?p=8535854&postcount=95 ?

Looks like a great guide as only 1 part is required - this allows me to part in my G1 AmonRa Recovery FTW!~111
(Also a great option if you are worried about booting up your G2 after formatting the SD as any progs looking for files there will be disappointed until you can copy them back ...)
Running a continuous Ping in Term now to see if that does the trick ...
EDIT:
Alright! this is awesome!
Q:
IF all we have to do to keep root is to keep the shell open - can't we run a prog or command to prioritize that prog ... like ... i remember that auto taskiller had settings against apps that were in the forgroud, background, background services etc ...
can we fool the OS into thinking this is allways a foreground process even though it's really running in BG ...or somehow give it highest priority?
EDIT 2:
Installed WirelesTeather.apk and ran and installed binaries - SU came up and granted all permission w/o issue - everything looked good.
Didn't open any other programs and decided to test it later, after noticing the AP didn't show I checked Terminal from the taskbar and it was back to $ (was closed by system)
I am running a fish aquarium for livewallpaper - so I'm sure this is why it closed as I'm running more processes at idle ... however, it looks like opening pretty much anything will cause the terminal to close and kill the "temp root'
Running a continuous Ping in Term now to see if that does the trick
FINAL EDIT:
OK! Ran continuous ping, opened Quake 3 - played for a bit - closed it.
Checked Term from the status bar - My Ping is still running !!1111 (IE the shell didn't close and we still have root)
So ... maybe this helps

You are the man. Downloaded. Tested. It works!
Sent from my T-Mobile G2 using XDA App

GREAT WORK!
Got it up and running, and just got 2.26 down, 1.23 up on my laptop off wireless tether.

so since this works directly with system files what happens if you try to metamorph something..will it revert on reboot or stay

Excellent job!
You are a genius! Your guide worked perfectly! I am typing this while tethered to the G2 - I agree with you, getting Root for tethering is worth the hassle of getting Root access! Keep up the great work!
I had been taking the SIM chip from my G2 to G1 (rooted, of course!) for Internet access - No more! Thanks again!

sino8r said:
...
Oh btw, someone posted a clockwork recovery that was allegedly compatible with the G2 but I don't think anyone had the balls to flash it. Its in the root think tank thread...
Click to expand...
Click to collapse
ive tried, several different ways, even ones that had a good chance of bricking, i.e. messing with ruu, and swapping files in the middle of flashing, just to try and get this perm root

texasaggie1 said:
Some people are questioning the value of root without custom ROM's. Here is what i have used ROOT for on this ROM so far:
1) Wireless Tether - this alone is worth it! The 9-5 version from this page works amazingly on the G2:
http://code.google.com/p/android-wifi-tether/downloads/list?can=2&q=NexusOne
2) Uninstall Crapware - I used Titanium to uninstall Web2Go. What a pile of steamy poop.
3) Back up with Titanium - Most awesome backup program out there. Needs root to work.
Click to expand...
Click to collapse
For Wireless Tether, I'm getting an error where it can't start access point. Anyone else have that problem? My computer won't recognize it without it.
EDIT:
Never mind, access point won't start if WiFi is on, and WiFi Tether isn't automatically shutting it off (like I think it's done on other phones), so if anyone else has the problem, turn off WiFi, then run WiFi Tether.

Which Version?
aacrabtree said:
For Wireless Tether, I'm getting an error where it can't start access point. Anyone else have that problem? My computer won't recognize it without it.
EDIT:
Never mind, access point won't start if WiFi is on, and WiFi Tether isn't automatically shutting it off (like I think it's done on other phones), so if anyone else has the problem, turn off WiFi, then run WiFi Tether.
Click to expand...
Click to collapse
Which tethering apk are you using? If you are using the one from the link I provided it should work. I am not having to turn off wifi first for it to work for me.

Gfree_Verify Not Working, Not Sure if Root Worked

I followed all the steps from the Wiki: (http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD).
Now the problem is when I go to verify the root. On the Wiki, where it says run "su' in computer ADB shell, I get access denied. When I run "./gfree_verify" in computer ADB shell, I get
Error: Could not open modem device; /dev/****
Error: Verify could not initialize device
But in my apps on the G2 I see an icon for superuser permissions. So did the root take or not?
Thanks for any help, new to Android.

Go in to terminal on your phone and type SU
After pressing enter if it says permissions denied, you have no root, if a Su message pops up click allow... that means you have root
Edit: I think you have no root

MacaronyMax said:
Go in to terminal on your phone and type SU
After pressing enter if it says permissions denied, you have no root, if a Su message pops up click allow... that means you have root
Edit: I think you have no root
Click to expand...
Click to collapse
After typing Su in the terminal on the phone, I get a message pop that says either allow or deny. I click allow and it gives me root permission.

Then it`s OK!
After reboot/or try again,open terminal emulator on your phone and type "su".
If you get a superuser prompt, you have root!
After "su" you should see a line with "#".

Ganii said:
Then it`s OK!
After reboot/or try again,open terminal emulator on your phone and type "su".
If you get a superuser prompt, you have root!
After "su" you should see a line with "#".
Click to expand...
Click to collapse
After a reboot (two actually) after I enter su into terminal I dont get the popup anymore asking allow or deny. I get "#." I actually went through the whole rooting Wiki steps again, to root the phone (just cause I wasn't sure if I was rooted). Same results, the gfree-verfiy doesnt work and neither does the "older" method. But I get "#" after entering su in terminal on G2.
I also installed Rom Manager, I clicked Flash ClockworkMod Recovery and then chose Backup Current ROM. It asked for superuser permissions and I allowed it. It rebooted the phone and went to a ClockworkMod Recovery screen where I selected reboot device. Does this mean I backed up my current Tmobile ROM?
Another question, is it okay to delete the files I had to push to /data/local to root? How would I delete them?
I want to really thank you guys for all the help.

boost3d23 said:
After a reboot (two actually) after I enter su into terminal I dont get the popup anymore asking allow or deny. I get "#." I actually went through the whole rooting Wiki steps again, to root the phone (just cause I wasn't sure if I was rooted). Same results, the gfree-verfiy doesnt work and neither does the "older" method. But I get "#" after entering su in terminal on G2.
I also installed Rom Manager, I clicked Flash ClockworkMod Recovery and then chose Backup Current ROM. It asked for superuser permissions and I allowed it. It rebooted the phone and went to a ClockworkMod Recovery screen where I selected reboot device. Does this mean I backed up my current Tmobile ROM?
Another question, is it okay to delete the files I had to push to /data/local to root? How would I delete them?
I want to really thank you guys for all the help.
Click to expand...
Click to collapse
# sign means your rooted or have su access.
Go under manage and restore backups in rom manager, you should have a copy of the rom you just backed up. Unless you renamed the back up its probably a date.
Its ok to delete the files you pushed to data/local use a file manager like root explorer.
Sent from my HTC Vision using XDA App

After a reboot (two actually) after I enter su into terminal I dont get the popup anymore asking allow or deny. I get "#." I actually went through the whole rooting Wiki steps again. Same results, the gfree-verfiy doesnt work and neither does the "older" method. But I get "#" after entering su in terminal on G2.
Click to expand...
Click to collapse
You get "#" then it`s right,the app don`t ask you again about allow or deny!
About gfree-verify,I don`t know.Maybe something wrong with Script
or you have done something wrong with the commands!
I also installed Rom Manager, I clicked Flash ClockworkMod Recovery and then chose Backup Current ROM. It asked for superuser permissions and I allowed it. It rebooted the phone and went to a ClockworkMod Recovery screen where I selected reboot device. Does this mean I backed up my current Tmobile ROM?
Click to expand...
Click to collapse
If you choose "Backup ROM" you phone boot into Recovery,then you have
to choose "backup/restore option to backup you current ROM.
Otherwise you don`t have a backup

Again thanks guys.
Now i downloaded Astro and ES file Managers but I cant find the files. Do I need specifically need root manager? Im guessing the ones I downloaded cant access root files.

boost3d23 said:
Again thanks guys.
Now i downloaded Astro and ES file Managers but I cant find the files. Do I need specifically need root manager? Im guessing the ones I downloaded cant access root files.
Click to expand...
Click to collapse
I use Root Explorer or SUFBS (Super User File Manager and Terminal).

boost3d23 said:
Now i downloaded Astro and ES file Managers but I cant find the files. Do I need specifically need root manager? Im guessing the ones I downloaded cant access root files.
Click to expand...
Click to collapse
You should really have posted up in the existing thread about gfree on this, or otherwise in the Q&A forum
But anyway, yes, those file managers don't handle root. Well, ES does have an option to do so, but it doesn't work on the Vision. So you'll need a root-capable file manager, as joemm said.
On the backup, that sounds a bit odd, but you'll know that it's doing a backup because it'll take a while. You'll get a different screen where it shows you it's backup up the main phone partitions, and even which file is being backed up. When it's done, make sure you copy this backup somewhere else, like your PC (i.e. so you don't just have a single copy, in case something happens to it - e.g. corrupt SD card).

Thanks to everyone who provided insight. I had the same problem and was worried about bricking my phone, but this worked and I'm happily rooted!

[Q] Can't access /data in android (rooted)

Hi, I've tried SuperSU and SuperUser.
apps and adb shell can't access the /data partition.
it says that I don't have enough permissions ...
with adb shell I can cd to it, but even an "ls" says operation not permitted
I can access it just fine in CWM using adb shell
all other root directory works fine....
Does anybody know what's going on ? did i miss something ? I'm no expert when it comes to this
thanks for your help

kout said:
Hi, I've tried SuperSU and SuperUser.
apps and adb shell can't access the /data partition.
it says that I don't have enough permissions ...
with adb shell I can cd to it, but even an "ls" says operation not permitted
I can access it just fine in CWM using adb shell
all other root directory works fine....
Does anybody know what's going on ? did i miss something ? I'm no expert when it comes to this
thanks for your help
Click to expand...
Click to collapse
After typing adb shell and entering you have to type su and press enter again, then you`ll have the permissions you need

But how come root browser can't access that directory?
And why can I go to /system without having to type su first

kout said:
But how come root browser can't access that directory?
And why can I go to /system without having to type su first
Click to expand...
Click to collapse
How do you mean: root browser/ file manager on the phone to access system date? You have to be rooted to access system data on the phone. What exactly do you want to do?

Weird stuff, it's working with solid explorer, I had tried with rom toolbox browser and some other root browser from the play store and it wouldn't work
Thanks for the "su" tip I forgot you had to be su to access that folder :-S

kout said:
Weird stuff, it's working with solid explorer, I had tried with rom toolbox browser and some other root browser from the play store and it wouldn't work
Thanks for the "su" tip I forgot you had to be su to access that folder :-S
Click to expand...
Click to collapse
Is you`re phone rooted mate? The su command is for adb from your computer!

Of course it's rooted, I do have a bit of experience with that. It's just weird that certain root browser can't access the data partition despite having granted su permission to the app. Anyway its working great with solid explorer now, and with adb I've got the su command
I actually have the voice stuck on the same street in navigation, (known bug) so I had to delete some cached speech data in the data partition
I did it through cwm but I was wondering why it wasn't letting me do it once booted. Anyway thanks

Question Seeing root files from computer?

My OnePlus 9 Pro is rooted. I tried seeing the protected system files such as those in /data from my computer in the following ways and none of the work. (I can see these files with Root Explorer on the phone).
1) command line using "adb shell", "ls -l", "cd data", and then "ls -l". The first two commands work, but I get "Permission denied" on the last command.
2) The Google application "Android File Transfer" running on my Mac
3) The Mac application "MacDroid"
4) The open source application "OpenMTP"
Alls of these lead to only seeing the files in the simulated SD card. How can I did deep into the Android file system from my computer, while the phone is connected?
Thanks in advance

@tk_xda
Put su -c before the ls command, or open a root shell by running su. You also need to have superuser access for adb enabled to use this command.

tk_xda said:
My OnePlus 9 Pro is rooted. I tried seeing the protected system files such as those in /data from my computer in the following ways and none of the work. (I can see these files with Root Explorer on the phone).
1) command line using "adb shell", "ls -l", "cd data", and then "ls -l". The first two commands work, but I get "Permission denied" on the last command.
2) The Google application "Android File Transfer" running on my Mac
3) The Mac application "MacDroid"
4) The open source application "OpenMTP"
Alls of these lead to only seeing the files in the simulated SD card. How can I did deep into the Android file system from my computer, while the phone is connected?
Thanks in advance
Click to expand...
Click to collapse
Try adb shell then su and acknowledge it on phone.....

DavidxxxD said:
Put su -c before the ls command, or open a root shell by running su. You also need to have superuser access for adb enabled to use this command.
Click to expand...
Click to collapse
TheGhost1951 said:
Try adb shell then su and acknowledge it on phone.....
Click to expand...
Click to collapse
Thanks. Is there any way to get this level of access using the other utilities I named, or is the only way from the computer through adb commands?

@tk_xda
You can also use a terminal app to open a shell locally on the device. Be careful and don't run
Bash:
rm -rf /*
It will make a painful brick of it.
Have fun!

tk_xda said:
computer
Click to expand...
Click to collapse
Do a TWRP backup and open it on the computer with 7zip
(editing system files while the system is ON can lead to crash ...)

loopypalm said:
(editing system files while the system is ON can lead to crash ...)
Click to expand...
Click to collapse
Yes I can confirm.

tk_xda said:
Thanks. Is there any way to get this level of access using the other utilities I named, or is the only way from the computer through adb commands?
Click to expand...
Click to collapse
No, you could use Termux on phone, similar to adb

loopypalm said:
Do a TWRP backup and open it on the computer with 7zip
(editing system files while the system is ON can lead to crash ...)
Click to expand...
Click to collapse
I would want to access a small group of files on the computer. Copying an entire backup from the phone would be cumbersome. Typically, I might like to get nosy about the database tables an app uses to store its data and would want just the data for an app.
I would not be editing system files unless I have a specific informed purpose, but would like to be able to copy any of them to my computer that I choose to examine.
TheGhost1951 said:
No, you could use Termux on phone, similar to adb
Click to expand...
Click to collapse
I have Root Explorer app on the phone and can rummage with that when I desire to rummage into something on the phone. My current workaround when I want a few system protected or app data files is to copy them with the Root Explorer into the simulated SD card, and then get the data from there with the computer. By this post, I was hoping to navigate more directly just by connecting the phone to the computer and copying what I want.

tk_xda said:
I would want to access a small group of files on the computer. Copying an entire backup from the phone would be cumbersome. Typically, I might like to get nosy about the database tables an app uses to store its data and would want just the data for an app.
I would not be editing system files unless I have a specific informed purpose, but would like to be able to copy any of them to my computer that I choose to examine.
I have Root Explorer app on the phone and can rummage with that when I desire to rummage into something on the phone. My current workaround when I want a few system protected or app data files is to copy them with the Root Explorer into the simulated SD card, and then get the data from there with the computer. By this post, I was hoping to navigate more directly just by connecting the phone to the computer and copying what I want.
Click to expand...
Click to collapse
Some things are easy and some are not. It can't be about shortcuts all the time. Sometimes the reward takes some effort!

tk_xda said:
... database tables an app uses to store its data and would want just the data for an app.
Click to expand...
Click to collapse
Even if you found a way to mount "data" it will be encrypted (unless you running an old rom or flashed DFE before ...)
see also this