Related
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.
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!
Hi there!
I'm trying to root Ziio 7 unit I got for a review for PurePC.pl, and so far so good I installed SuperUser app and su and busybox binaries. Now using terminal I can su without any problems. But the thing is, SU only seems to be working in terminal emulator. I've tried using some apps that should use root like ShootMe and ScreenshotIt, SetCPU and they just doesn't work.
ShootMe says "Starting Server failed", plus info that i need to have root access and enabled access to lower graphics (whatever it is).
ScreenshotIt just doesn't work without any information why, and SetCPU FC's after selecting profile. Although it gets me a nice SuperUser dialog, but that's as far as it goes, cause it crashes right after that.
Am I missing something to have a complete root? Interesting thing is that on this device, preferred PATH for executable binaries is /data/busybox/, and not a usual /system/bin. Interestingly, my su binaries refused to work from /data/busybox directory, so I moved them to /system/bin. Rest of the utilities and such are still in /data/busybox, but I don't know if this information is important in any way Have I missed something along the way? Please help. Cheers.
OK, I know why su gave me permission denied when running from /data/busybox. The /data partition was mounted with nosuid. But still the applications such as ShootMe won't work.
I waiting for. If who has a good new. Please tell me to private message.
Have you made any progress on this bagienny?
This is for n00bs like myself that had to search around before getting into this and doing it correctly. A lot was copied from the Inc S thread, but felt the instructions were needed here so no need for searching there and crowding their forum with our questions: http://forum.xda-developers.com/showthread.php?t=1039015
Psneuter exploit is working on DInc2, but because /system is locked on s-on phones, we can't copy su and superuser.apk into /system, apps required root access can't work.
The following procedure uses psenuter exploit to gain adb shell root, and then copy su (without privilege control ) and busybox into /sbin (which is on rootfs and in the global PATH list) to gain root access for apps.
The procedure:
1. Install the HTC Sync software or PDANet software to install drivers for your phone to Windows
2. Ensure that the device is in USB Debug mode, go to Settings > Applications > Development and "tick" USB debugging and plug in your phone to your PC
3. Unzip the attached .zip into a directory (like c:\adb)
4. Open a command prompt by going to start > run and running CMD, and cd to the directory where you extracted the .zip (like cd \adb)
5. Type "adb devices" > enter, and ensure that your device has been detected
6. Run the "pushroot.bat" file
7. Type "adb shell /data/local/tmp/getroot" > enter
8. Type "adb shell" > enter
9. You are now in # prompt. Type "/data/local/tmp/pushroot"
After the last step, a new # line appears. That's it! You're temporarily rooted
You have to redo steps 7, 8, 9 once you reboot your phone.
The procedure will have all apps gaining root access.
!!USE ON YOUR OWN RISK!!
Known working programs: Root explorer, Titanium backup, gscript lite, trasproxy 2.04, ...
Some apps check existence of su in /system/xbin , and reject to proceed if the su binary is not exist (like transproxy 3.08). For this kind of apps, this procedure won't help.
I run Bloat Freezer to rid the VZW apps
u can actually use the exact same process as the incS
I said that and linked to the Inc S thread for doing it
I just added in some steps for the issues I ran into, since it was my first time trying to do something like this and so others have a step by step to follow
And also so we have have something for this forum...thanks though
OK, question... if I do a temp root on the DInc2, then restore my wife's Titanium Backup to the new phone, can I also perminantly get rid of the VZW Bloatware, then reboot without Temp Rooting from that point on? (I know I will lose full Backups as well as SetCPU, etc. but will the Bloatware removal cause issues?)
I use Bloat Freeze and the VZW crap never comes back after a reboot when I have the "Alternate Freeze method" checked in the preferences, which is the Titanium Backup method
Maybe I am doing something wrong. I get to step #9 with
$ /data/local/tmp/pushroot and get
mount: operation not permitted
and a few more permission denied lines.
??? thanks in advance
Looks like the getroot did not work/run right, when you do step 8, the shell should start with the '#', not the '$'
Can somebody help me...after the last step, nothing happens. It just starts a new # line.
Posted from my Droid Incredible 2
Disregard. I got it. How can I effectively get rid of the bloatware? I moved a lot of it from system/app to my sdcard, but when I rebooted and lost root, it all reappeared.
Posted from my Droid Incredible 2
xgunther said:
Disregard. I got it. How can I effectively get rid of the bloatware? I moved a lot of it from system/app to my sdcard, but when I rebooted and lost root, it all reappeared.
Posted from my Droid Incredible 2
Click to expand...
Click to collapse
Use Titanium to freeze it. Don't delete it. Freezing works, but if you delete it it will just come back.
Sent from my ADR6350 using XDA App
I have done all the steps correctly up until step 5, well the problem is after typing in adb service, i get an extensively long list of different commands, and then the next step is to type in pushroot.bat, and when i do, heres what i get in return
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: dervice not found
C:\adb>
I dont know the problem...i do have Ongoing HTC Charge. USB Debugging connected. And PdaNet Connect (USB)
What could be the problem?
That should be adb devices, not serices
After that, you should see your device listed. When you typed services, the list you got was basically a help list for adb commands, since you did not type a valid one
Double check to make sure your device is detcted, if it is not, go to Windows' Device Manager and make sure the proper drivers were installed for your DInc
Ah, i appreciate the quick response i really do. I did type in adb devices, and what i got back was
List of devices attached
Afterwards, i did type in "pushroot.bat" and got a reply with again the same thing, error;device not found
In my window's device manager, i do have Android Phone, however the picture is only shown as a hard drive, which idk if that would have any affect. But yes, i didnt install any drivers from windows recommendations, like when i plug it in, the normal driver window pops up, but apart from that, i never did anything else except for the PDAnet 3.0 driver
Am i the only person who tries to delete apps and when the phone is restarted they come right back on.
mykenyc said:
Am i the only person who tries to delete apps and when the phone is restarted they come right back on.
Click to expand...
Click to collapse
You must "freeze" them with bloat freezer or a similar app.
xgunther said:
You must "freeze" them with bloat freezer or a similar app.
Click to expand...
Click to collapse
With only a temp root wouldn't any bloat freezing reset on reboot?
x Eacott said:
Ah, i appreciate the quick response i really do. I did type in adb devices, and what i got back was
List of devices attached
Afterwards, i did type in "pushroot.bat" and got a reply with again the same thing, error;device not found
In my window's device manager, i do have Android Phone, however the picture is only shown as a hard drive, which idk if that would have any affect. But yes, i didnt install any drivers from windows recommendations, like when i plug it in, the normal driver window pops up, but apart from that, i never did anything else except for the PDAnet 3.0 driver
Click to expand...
Click to collapse
Looks like your Dinc2 isn't being detected by your computer, watch you device manager when you plug in your phone and see what all is installed...sounds like that is the issue for you
sixteen2nd said:
With only a temp root wouldn't any bloat freezing reset on reboot?
Click to expand...
Click to collapse
Negative, Freezing works on the temp root after a reset, just make sure if you use Bloat Freeze that you select the alternative freezing option (Titanium Backup method) when you do it
LowFire82 said:
Looks like your Dinc2 isn't being detected by your computer, watch you device manager when you plug in your phone and see what all is installed...sounds like that is the issue for you
Click to expand...
Click to collapse
There are a lot of things that could prevent adb from picking up your device... easiest would be to double-check that you have the USB Debugging option enabled on the device. The next easiest would be to make sure you have the correct drivers installed. I'd recommend using an app like USBDeview to see an extended list of all your installed USB drivers, and then deleting anything related to HTC/Android/adb. You can then reinstall the correct drivers which I believe LowFire mentioned in his OP.
/threadjack
Ahh! OK, I had to do a Master Reset of my wife's Inc2, previously it had TempRoot working.
I followed the instructions from the beginning after it was reset, but I cannot get TempRoot access. MyBackup Pro, Titanium, Root Explorer all say there is no root access. I get the phone listed at adb devices and get no errors running the commands. Anyone have issues gaining root?
xgunther said:
Can somebody help me...after the last step, nothing happens. It just starts a new # line.
Posted from my Droid Incredible 2
Click to expand...
Click to collapse
I have the same issue...just another # line after typing in the string from step 9 and hitting enter
What did you do?
I need to make an EFS backup, never have before and flashed tonnes of roms, lol. But after reading it's probably a good idea.
Currently on CM13.
However, I've run into an issue. I downloaded Terminal Emulator. I enter "su" and it says on a new line: 255|[email protected]:/
So I then tried to enter: dd if=/dev/block/sdf1 of=/sdcard/modemst1.bin bs=512 - and it says permission denied?
Any help? :]
Root access
Are you sure the terminal has root access?
I use a CM13 variant as well and I had to disable and reenable root access from the developer options before any apps were able to get root. After doing that the first time its worked ever since. Even on cm13 you should get a permission prompt when an app requests root.
JoshAulder said:
Are you sure the terminal has root access?
I use a CM13 variant as well and I had to disable and reenable root access from the developer options before any apps were able to get root. After doing that the first time its worked ever since. Even on cm13 you should get a permission prompt when an app requests root.
Click to expand...
Click to collapse
Uh, 'su' is apparently supposed to give the terminal root access, apparently? lol
Sorta new to this.
ritchiedrama said:
Uh, 'su' is apparently supposed to give the terminal root access, apparently? lol
Sorta new to this.
Click to expand...
Click to collapse
When running the terminal app for the first time, entering su does not instantly grant it root access, but instead makes the app request access. If it has never been given you will get a prompt over the screen asking if you want to give the app root access. If you are not getting this prompt, then do this:
Go to developer options in settings
Tap on root access
Set it to disabled
Tap again and select Apps (or apps and adb)
Then run the terminal again and enter su
JoshAulder said:
When running the terminal app for the first time, entering su does not instantly grant it root access, but instead makes the app request access. If it has never been given you will get a prompt over the screen asking if you want to give the app root access. If you are not getting this prompt, then do this:
Go to developer options in settings
Tap on root access
Set it to disabled
Tap again and select Apps (or apps and adb)
Then run the terminal again and enter su
Click to expand...
Click to collapse
Thannks, where are these files once I did this?
It says internal storage but I don't see them.
edit: I see them on my phone but not on my PC when I plug my phone in, weird, lol.
ritchiedrama said:
Thannks, where are these files once I did this?
It says internal storage but I don't see them.
edit: I see them on my phone but not on my PC when I plug my phone in, weird, lol.
Click to expand...
Click to collapse
It should come to /storage/emulated/0
Aka the main internal storage folder which includes things like the downloads and pictures folders. The file should be called modemst1.bin
Hope this helps
Edit: I have no idea why it doesn't show when you plug in your phone. Maybe the file is set to be hidden and you dont have show hidden files and folders enabled on your pc? In any case I just backed mine to my google drive
JoshAulder said:
When running the terminal app for the first time, entering su does not instantly grant it root access, but instead makes the app request access. If it has never been given you will get a prompt over the screen asking if you want to give the app root access. If you are not getting this prompt, then do this:
Go to developer options in settings
Tap on root access
Set it to disabled
Tap again and select Apps (or apps and adb)
Then run the terminal again and enter su
Click to expand...
Click to collapse
JoshAulder said:
It should come to /storage/emulated/0
Aka the main internal storage folder which includes things like the downloads and pictures folders. The file should be called modemst1.bin
Hope this helps
Click to expand...
Click to collapse
I found them on my phone, not my pc.
They were 2mb each and I emailed them to myself and uploaded them to my dropbox, so all good? I can delete them now from my phone?
ritchiedrama said:
I found them on my phone, not my pc.
They were 2mb each and I emailed them to myself and uploaded them to my dropbox, so all good? I can delete them now from my phone?
Click to expand...
Click to collapse
Yep, the terminal only made a copy of the files, so as long as you can get them back when you need them they're safe to delete