[GUIDE] Super EASY Temp Root using normal SD Card - G2 and Desire Z Android Development

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.

Related

Ok removed some built in app's

So I took the plunge and have removed peep and learn more from the phone, all working well so far. don't want to push my luck and remove more.
How did you managed it? I'm guessing you have root access or something?
yes rooted and booted loads of bits i want to remove but not sure what effect they would have on the system.
adb shell rm /system/app/Learn*
adb shell rm /system/app/com.htc.Twitt*
I managed to remove learnmore and the Stocks app and its widget. No discernable bad effects. I used Root Explorer successfully to do this, thought I havent managed to get Root Explorer to Copy and paste either to or from the device (Yup I know its read only, but Root Explorer, when working correctly, allows you to toggle R/w and R/0 ).
Daisy xxx
Dayzee said:
I managed to remove learnmore and the Stocks app and its widget. No discernable bad effects. I used Root Explorer successfully to do this, thought I havent managed to get Root Explorer to Copy and paste either to or from the device (Yup I know its read only, but Root Explorer, when working correctly, allows you to toggle R/w and R/0 ).
Daisy xxx
Click to expand...
Click to collapse
Daisy! Quick question?? how did you manage to get root explorer to work. It seems to for-close on me all the time!
Dayzee said:
I havent managed to get Root Explorer to Copy and paste either to or from the device
Click to expand...
Click to collapse
It's now working here. I used the update.zip mentioned here to gain "adb remount" ability for an unrelated issue and a side-effect is that Root Explorer now copies/pastes as expected.
Maybe a little tutorial on how to uninstall apps ??
I remove "rosie" to get back old style android look : its blazing fast and all htc's applications still works.
I used the Update.zip from Pauls Method at MoDaCo (Should go in the wiki if Paul says its OK?) and then was able to copy from /data/app/ to my SD Card using Linda File Manager whilst in "adb remount" (link via usb, then use command prompt to get to the adb directory and type "adb remount" then use the Linda File manager to do the bizz.)
Haven't tried removing anything or putting anything in yet, cos I really don't know whayt I'm doing. I just want to know HOW it can be done really. :0)
Dayzee
minogue said:
Daisy! Quick question?? how did you manage to get root explorer to work. It seems to for-close on me all the time!
Click to expand...
Click to collapse
I don't get force closes, but it certainly doesn't work for me as it should. Pressing the buttons to change from R/W to R/O usually says Busy: cannot remount - also any "copy" seems to go ok but the "paste" never works.
I've got Root Explorer 1.4 I think. Also tried it with adb remount but it didn't seem to work either.
Daisy xx
NisseGurra said:
I remove "rosie" to get back old style android look : its blazing fast and all htc's applications still works.
Click to expand...
Click to collapse
I want to do this but worried I might get the "force close error" when opening the peoples application when using the standard android UI. Its happened a few times when I set Home as my default application, reverted back to Touchflo and it been working great.
Removing Rosie completely will also remove the black look that HTC put in the ROM? Or is that something that is fixed by theming? (Like the top bar being black on the Hero, but white on the Magic)
Edit:
Well I went ahead and gave Rosie the boot, allong with some other HTC widget stuff (which becomes obsolete when you remove Rosie) I used Root Explorer to delete the files (adb shell rm wouldn't work :-\)
All I need now is the default white bar at the top instead of the HTC Black one

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

[Q] Power-off shortcut??

Hi guys,
Is it possible to have a shortcut icon on homescreen that powers the phone off. I have a protective gel case on my Desire and its a pain in the a**e having to long press it through the case and then select power off and then ok to confirm.
I am using quick boot app which is excellent but no power off option with it. Just reboot, recovery and quickboot. Have already requested Dev to add the function but not hopefull.
When long pressing the power button a menu pops up right? Is it possible to invoke that power menu in another way? Perhaps with a shortcut?
Surely its not rocket science to be able to click an icon and the phone powers off???????
Edit: see last post for solution
??
C'mon guys, someone must know a way to achieve this. Otherwise, whats this forum for?
5 minute job to knock up a zip patch file or a simple app for someone who know's what their doing. I feel a lot of people (certainly those using protective cases) would find such an app or patch (for rooted users like me) very welcome.
I would happily do it for someone else.
you can power off with the command
reboot -p
Click to expand...
Click to collapse
you can use gscript (light version available on the market for free.) to add a shortcut to that command on the homescreen.
You will need root access, i think.
??
C'mon man, you must know how to show some sort of gratitude or give some sort of feedback. Otherwise, whats this forum for?
5 minute job to go on your computer (or phone) and post a reply for someone who know's what their doing. I feel a lot of people (certainly those who help others) would find a simple thank-you very welcome.
I would happily do it for someone else.
My point is if you can't be arsed to reply to your own thread in 24 hours why bump it after a day with no reply?
reboot controll widget
Mercianary,
Don't get your knickers in a twist
Only seen your reply this morning. Thanks for your suggestion - gscript. Gonna try it out later today. Will post back.
Cheers dude.
What....these feelings...I feel bad now...sorry.
That widget looks like it would do the job great. Just depends of your stingy like me and wouldn't pay 87p for an app when I can do the same for free.
Just installed gscript and run a reboot -p script but it doesn't work
I get a stderr: not permited error
I am rooted and have the superuser app
Any ideas??
Try
su
reboot -p
Edit: that wont work. Make sure you tick 'needs su' box in gscript when you make the script. Should make it work
Got su box checked.
Tried
su
reboot -p
Tried re-installing gscript.
Tried reboot
Is it not working because, although I am rooted with unrevoked 3.2, I still have s-on? I wonder. Or, is it because reboot is not allowed to be run as a script???
But I have superuser app. Puzzled. Any more suggestions as I really want to get this working. By the way scripts not requiring su run fine.
http://www.appbrain.com/app/quick-boot/com.siriusapplications.quickboot
Hello
Yes I am already using quick boot but it doesn't have the option to simply power off the phone. Only reboot, recovery and bootloader. I have asked the Dev to add this option as others have also asked but not hopeful anytime soon.
All I want is a homescreen shortcut that powers off the phone. Simples!
Why am I getting not permitted error messages when trying to run following from gscript.....
reboot -p
It is set to use superuser but gives the error. WHY!!!!
Try running the command from a terminal emulator. If that works we know gscript is the problem (in which case I can tell you a work around).
If it still doesn't work maybe your rom doesn't support it (I use cyanogenmod and it works fine for me.).
Edit: double check gscript is set to 'allow' in superuser.
Su
Shutdown
Works in terminal.
Sent from my Evil Lair using Doomsday Device
Ik Desire said:
Su
Shutdown
Works in terminal.
Sent from my Evil Lair using Doomsday Device
Click to expand...
Click to collapse
Not for me. It must be different on different roms.
Are you using a sense rom?
By terminal emulator, do you mean an adb shell from a command prompt on P.C........Or do you mean something that runs on the phone?
Edit: Ran Alpharev last night and am now s-off All went smoothly. Have installed root explorer and was wondering what file/directory permissions I need to change to be able to execute scripts?
btw, thanks for your suggestions Mercianary and IK Desire
Edit: installed Android Terminal Emulator and ran
su (it asked for superuser permision and i allowed)
#shutdown (phone powered immediately off but would not switch back on - had to pull battery)
#reboot -p (same as above)
Totally stumped and baffled.
mercianary said:
Not for me. It must be different on different roms.
Are you using a sense rom?
Click to expand...
Click to collapse
Leedroid 2.2e. Using terminal emulator on phone. I have the same problem (have to pull battery before rebooting). But previously this was not the case.
Sent from my Evil Lair using Doomsday Device
Update
Have found a solution (sort of!). Have installed busybox and have created a gscript script as follows....
busybox poweroff -d 10 -f
This works and powers the phone off after 10 seconds. The reason for the 10 second delay is to give the system enough time to unmount filesystems and stop services. An ordered shutdown if you like.
Thing is....Is this what actually happens? I mean the poweroff command in busybox doesn't go through the init system. So, is it a "clean, ordered" powerdown???? It switches back on ok afterwards and everything seems to work.
But the question is am I risking corrupting the filesystem by shutting down in the way?

T-mobile g2 root problems, other threads checked.

In the process of following the rooting wiki, had hella problems getting adb working. Got adb connected finally, got the money sign, tried first instruction, got adbermission denied. What could be the problem? Did a google search as well. I have the contents of adb tools, in the same place as g free, as it is completely impossible to start up adb shell, and then navigate to a completely different folder. Also, before moving adb tools, tried long addresses of the gfree stuff, same deal.
Did you do "adb shell" and then you tried more adb commands and got "permission denied" ?
If so, then that's because "adb shell" starts a command prompt session on your phone, and the adb commands need to be run on your PC, not your phone. So don't do the "adb shell" first.
So wait a second, you're saying that the wonderful wiki, either is in the wrong order, or requires me to follow the pc, and phone steps simultaneously? Because im running them from my pc. Which would be implied by my saying im following the wiki. Fyi, i meant the one on the g2, involving rooting the g2, on the xda-dev site. I've done this before, i know how to use adb. this is the first time i have rooted a g2. Don't mean to sound like a ****, but you basically didnt read anything i wrote.
The Wiki isn't in the wrong order. But IMHO it's very confusing that it shows a $ prompt when it shows "adb push" etc, because that makes it looks like it is run on the phone. But it's assuming you're running from Linux/Mac. On a PC the prompt for your adb commands would be C:\ or similar.
The Wiki doesn't tell you to run "adb shell"
So the answer to my question was yes, it works, but i had to wait 5 minutes to post this. I dont understand why there cant be a note that, unless you put adb into your path, cmd isnt going to recognize it unless its in the folder you're using. I feel no need to put a tool that i will use maybe once a year at most into path. also, when i just checked the wiki now, i noticed how the dollar signs had changed to c:/ ha ha. and sorry about the rudeness, at first it just seemed like you were making fun of me.
jenlow said:
Okay, so before i opened the adb shell from cmd, when i would type adb push, i would get adb is not recognized as an internal or external command. so, my solution of putting the adb tools into gfree, should work now once i cd to the gfree folder?
Click to expand...
Click to collapse
That's an issue with your path not being setup properly on your PC. You can adb adb's folder to the path to mean you can run it from anywhere. Otherwise you need to put the gfree tools etc in the same folder as adb, then cd to there and run the commands.
Or if the path is setup properly, cd to where the gfree tools are and start doing your "adb push" etc from there.
I have just edited the Wiki to show a "C:\" prompt for the stuff that's run on the PC, to try and avoid this confusion.
Did it work ?
jenlow said:
In the process of following the rooting wiki, had hella problems getting adb working. Got adb connected finally, got the money sign, tried first instruction, got adbermission denied. What could be the problem? Did a google search as well. I have the contents of adb tools, in the same place as g free, as it is completely impossible to start up adb shell, and then navigate to a completely different folder. Also, before moving adb tools, tried long addresses of the gfree stuff, same deal.
Click to expand...
Click to collapse
the "permission denied" thing... from the phone? Or from the computer? You know you need to be root in order to access the hardware, or at least set the permissions on the hardware to be accessible to your user account....???
And... you DID enable adb on the phone side, didn't you?
I used the Wiki and am now perm rooted. A few tips that may help you since they helped me to get it done. I opened a command prompt and noted the default path that opened. For me it was C:\Users\Ed . I used windows explorer to navigate there and open up the Ed folder and created a new folder in Ed that I named pr. This is where I unzipped both of the gfree zip files...into that same folder. When temp rooting and perm rooting, I simply opened up the command prompt, it opened to C:\Users\Ed and then I typed cd pr then I hit enter. That set me up to input the commands in the right place both times and it worked out just fine.
Another thing that I noticed. After temp rooting, I had to ctrl alt del to open up task manager and close down adb.exe (as noted in the instructions that appeared in terminal emulator). I couldn't load adb again until I closed it down and let it restart itself. When I entered the first command in the perm root process adb started up again by itself and all went well.
Good Luck! It is well worth it. I now have Cyanogen's latest stable build loaded along with the Google apps package that I found online.
Ed
OH! yeah, it did work. i thought i said that somewhere ha. I am currently running CM 6.1.1 now. I've decided that since the adb file, and necessary files are tiny i can just move them around to whatever i need to use adb for. Path editing should only be done by hand in linux And jesus CM has improved since i had it on my cliq. I'm like 90% sure i'm going to make a donation out of the school funds.
Root my phone!!! HELP
Hi Guys
I've tried root and my cell phone, but it is not. I've tried almost everything I have .. First I tried to root using the terminal emulator''''by typing different commands ..
Also, I tried the program''Visionary''but when I pressed the application so that it was held to root, but then the screen goes black, and I had to press the home button to get out of the situation ..
Also tried I saw another app called ''Universal androot'' and when I pressed root, then came the''Failed! No ~~~~~~~~~ Fu goo ..'' I also tried''app ''superoneclick I pressed the root, also came the''error: protocol fault (no status)''
What should i suppose to do, to fix this problem.. please reply
Thaaaanks!!!
mannær said:
Hi Guys
I've tried root and my cell phone, but it is not. I've tried almost everything I have .. First I tried to root using the terminal emulator''''by typing different commands ..
Also, I tried the program''Visionary''but when I pressed the application so that it was held to root, but then the screen goes black, and I had to press the home button to get out of the situation ..
Also tried I saw another app called ''Universal androot'' and when I pressed root, then came the''Failed! No ~~~~~~~~~ Fu goo ..'' I also tried''app ''superoneclick I pressed the root, also came the''error: protocol fault (no status)''
What should i suppose to do, to fix this problem.. please reply
Thaaaanks!!!
Click to expand...
Click to collapse
None of those apps work with the G2 to perm root without extra steps. And in that case only Visionary. You need to check out the vision wiki page.
Ed thoroughly described how to make it work. I did the exact same thing he did and got it last night.
jenlow said:
OH! yeah, it did work. i thought i said that somewhere ha. I am currently running CM 6.1.1 now. I've decided that since the adb file, and necessary files are tiny i can just move them around to whatever i need to use adb for. Path editing should only be done by hand in linux And jesus CM has improved since i had it on my cliq. I'm like 90% sure i'm going to make a donation out of the school funds.
Click to expand...
Click to collapse
What method did you use to root your cliq, and did you still have 3G? I have stock motoblur 2.1 on it now, I have it for a backup phone (got a G2), but I would like to root it.

HOW TO: Temp Root for DInc2

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?

Categories

Resources