Related
If anyone can help me with this issue,its killing me. I love the DARCHDROID rom,couldnt wait anymore so i had to flash it. Flashed darchdroid,lwp kernel and everything else works, minus a few fc's. In adb i have #,and my device appears to be rooted, i have rerooted more then 35 times in the past 5 hours read numerous posts here,even some that would imply to address this issue,but does not solve my problem....seems that i dont have root access to my new 2.1 rom shell.....if this is possible. Ive tried many other roms and never come accross one that you had to re root for.But this rom looked worth it. Everything i have read seems to work for others but not me. Well the geniuses are here so here is where i ask for assistance....any thoughts or replies would be greatly appreciated, im not giving up on this rom yet......thanks in advance!
The newest darch rom is already rooted. Make sure you 'adb remount'. That allows read/write access to /system if you want to push files to it.
oops
BTW, forgot some important info,didnt want to list all of my links and flood the thread Im still at it...anyone that is capable of offering me help will understand this error....when i get to step 9 in the xda guide.forum.xda-developers. cdma hero root guide,.....site wouldnt allow me to use the link,error?strange i couldnt link because all my good links are from this site......after i enter "cat sh > su"
i get "cannot create su: directory nonexistent"......i know this is a red flag for my problem and im sure theres an easy fix......tried makdir and im denied access. ..I now have a headache and thanks for any help.....
reflash the rom. there was no need to asroot2 the shell.
This is for anyone who is experienced with rooting using the rage method (command-line), using the Terminal Emulator, etc. I'm looking to root my phone, but aside from that, just looking to poke around and see what I can do at this point.
Ok, here's the skinny: I can get a temporary root (#) on my phone via the Terminal Emulator (will NOT show up in cmd.exe via adb) using the rage method, detailed steps are in my post here.
I can't push any files to /system after I get the temporary root - /system seems to lock up with any commands, like cat, attempting to do so (another post with details). However, I can copy /system files onto /sdcard, no limits as far as I know. Also, I can use dd to make a back-up of some of the mtd partitions. That's about the extent of the poking around that I've done after many hours of poring over other forums of different devices.
Where can I go from here? Can I use a different directory on the phone to try and push either su or Superuser to? Should I just give up? Haha.
I know that I already have my own thread dedicated to my phone and trying to figure out stuff for it. So, I hope I'm not stepping out of bounds by asking a question like this in regards to this rooting method...my apologies if I am being improper. My thanks and gratitude for anyone who reads this and can help me get to the next step, as little or big as that may be.
I'm trying to perm root my mytouch 4g using Visionary
I have android 2.2.1 and have successfully temp rooted using Visionary
I download the root folder from HERE
I put them in the root of the SD card and open up Terminal Emulator and type in
su
cd /sdcard/root
sh root.sh
when I type the first line (su) I get the # and am told that Terminal Emulator has been granted superuser permissions.
when I type in the second line (cd /sdcard/root) I get this message
cd: can't cd to /sdcard/root
What could be causing this?
Thanks
Jonathan
The "cd" command is a "change directory" command, and there is no directory called "root" on your SD card, because either you haven't unzipped what you downloaded, or you unzipped it in the wrong place.
Unzipping what you downloaded creates a directory (or a "folder", if you're a Windows user) called "root" that has several files in it -- a kernel module and a script, if I remember correctly. The script loads the kernel module and makes a call to it in order to set S Off.
thank you much, I think I figured out the problem. I'll try again later and see what happens. I'll post back with the results later. Thanks again!
Jonathan
NOTE: Ok, I can now run through the
su
cd /sdcard/root
sh root.sh
commands but when it's done and I check for s-off I don't have it (I still have s-on)
I've tried this twice to no avail. any advise?
i am having the same problem. i've tried this method about 15 times, mostly with visionary r14, but also a couple times with r11. i have also tried the gfree method a couple times as well via the semi-automated method. no s=off!
i have a new MT4G direct from phone upgrade order. i've read of others who have rooted the MT4G before multiple times, but can't do it now with a new phone. i'm wondering if it's something HTC has changed with the newest releases.....
kenrippy said:
i am having the same problem. i've tried this method about 15 times, mostly with visionary r14, but also a couple times with r11. i have also tried the gfree method a couple times as well via the semi-automated method. no s=off!
i have a new MT4G direct from phone upgrade order. i've read of others who have rooted the MT4G before multiple times, but can't do it now with a new phone. i'm wondering if it's something HTC has changed with the newest releases.....
Click to expand...
Click to collapse
HTC was going to install a measure that would prevent "rage methods" from working on their phones. How ever, none of the tech blogs are reporting that this has been rolled out. So i doubt that is the case.
make sure the its set up as sdcard/root. If you've just extracted the folder and copied the extraction to the sdcard it's not set properly.
neidlinger said:
HTC was going to install a measure that would prevent "rage methods" from working on their phones. How ever, none of the tech blogs are reporting that this has been rolled out. So i doubt that is the case.
make sure the its set up as sdcard/root. If you've just extracted the folder and copied the extraction to the sdcard it's not set properly.
Click to expand...
Click to collapse
yes, i understand the root folder in the root of the sdcard, and not 2 root folders. (sdcard/root/root)
like i mentioned, i read posts from a couple people on here with the same problems with new mt4g's after having done it multiple times before with success.
kenrippy said:
yes, i understand the root folder in the root of the sdcard, and not 2 root folders. (sdcard/root/root)
like i mentioned, i read posts from a couple people on here with the same problems with new mt4g's after having done it multiple times before with success.
Click to expand...
Click to collapse
then set up the ADB (see my sig) and do it the long way.
neidlinger said:
then set up the ADB (see my sig) and do it the long way.
Click to expand...
Click to collapse
after doing that, would i start on #4 in this guide?
http://forum.xda-developers.com/showthread.php?t=858996
kenrippy said:
after doing that, would i start on #4 in this guide?
http://forum.xda-developers.com/showthread.php?t=858996
Click to expand...
Click to collapse
nope you would start @ number 1.
you need to download those files and check the MD5SUM of every download load. the files need to be PERFECT for it to work correctly.
and i cannot stress enough. take your time and read directions. Read through the list a few times and make sure you have a good understanding of what you are doing. Doing that wrong can make your phone an expensive paper weight.
instead of pushing stuff to the "SDK tools folder" you store it to the ADB folder TrueBlue had you create in his walkthrough. And make sure to change your target folder to "c:\adb".
and remember you are choosing to do this. so if you screw it up. it's on your shoulders not mine.
neidlinger said:
nope you would start @ number 1.
you need to download those files and check the MD5SUM of every download load. the files need to be PERFECT for it to work correctly.
and i cannot stress enough. take your time and read directions. Read through the list a few times and make sure you have a good understanding of what you are doing. Doing that wrong can make your phone an expensive paper weight.
instead of pushing stuff to the "SDK tools folder" you store it to the ADB folder TrueBlue had you create in his walkthrough. And make sure to change your target folder to "c:\adb".
and remember you are choosing to do this. so if you screw it up. it's on your shoulders not mine.
Click to expand...
Click to collapse
thanks for all the help/info. i'll hold off for a while to see what else unfolds in the coming weeks in regards to alternate root methods. i don't want to brick this thing, just to get it rooted.
kenrippy said:
thanks for all the help/info. i'll hold off for a while to see what else unfolds in the coming weeks in regards to alternate root methods. i don't want to brick this thing, just to get it rooted.
Click to expand...
Click to collapse
The way this phone is made it's going to be pretty difficult to write a "one click s=off" program.
If you are wanting the benefits of being rooted you can always use VISIONary.apk when you need the root features like AD-HOC tethering or Screen Shots.
neidlinger said:
The way this phone is made it's going to be pretty difficult to write a "one click s=off" program.
If you are wanting the benefits of being rooted you can always use VISIONary.apk when you need the root features like AD-HOC tethering or Screen Shots.
Click to expand...
Click to collapse
what i'd really like to do is remove some bloatware and demo games. (not just hide them) any way to do that aside from perm root?
kenrippy said:
what i'd really like to do is remove some bloatware and demo games. (not just hide them) any way to do that aside from perm root?
Click to expand...
Click to collapse
not really. As soon as you reboot they'll pop right back up.
ok thanks.
Two things.
1. I've decided to put off perm rooting until I can understand adb and use it properly. No need to rush, I've got time.
2. Is it true that given time, effort, and ingenuity there really isn't such a thing as a bricked phone? It can always be recovered, it's just a question of how far you have to go to do it?
I've read around a lot and though I've heard many people talk of bricking their phone, it seems like many say that if you can use things like adb commands you can pretty well fix any issue, it's just difficult.
Like I was saying in point 1, I'm newer to all this and I'm learning so thanks for answering!
Jonathan
lanternslight456 said:
2. Is it true that given time, effort, and ingenuity there really isn't such a thing as a bricked phone? It can always be recovered, it's just a question of how far you have to go to do it?
Click to expand...
Click to collapse
At minimum, I believe the phone requires a functioning bootloader in order to be able to connect via USB to fastboot.
Any update on this? I also just got a mytouch 4g yesterday and am trying to root it. Is it possible right now?
Root the mt4g
Friend, I used the adb method here on xda, after I got the forked childs msg, and restart terminal w/e, make sue to pull out battery. Restart, the LAST THING I DID WAS USE VISIONARY r14, to attempt permroot, took me a week before I figured out to try this, the guide said phone would be rooted after terminal commands went through. So, to recap if u entered everything correctly, (my avg protection was telling me my phone was rooted for a week after I pushed gfree using the adb method but had no s-off, tried visionary permroot, BINGO!) THANKS TO ALL THE HARD WORK/GUIDES ON XDA, using ICE GLACIER ROM, titanium backup, rom manager, root explorer, my internet security (ad free web) set cpu, cache cleaner ng, drocap, couldn't get barnacle to work, the tethering on board works fine. Quadrant standard for benchmarking.
My wifes mt4g arrived today, and I had it perm rooted, with s-off in about 20 minutes, following this guide from the wiki:
http://forum.xda-developers.com/showthread.php?t=858996
Sent from my Nexus One using XDA App
danger-rat said:
My wifes mt4g arrived today, and I had it perm rooted, with s-off in about 20 minutes, following this guide from the wiki:
http://forum.xda-developers.com/showthread.php?t=858996
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
dude this method is great especially if your a noob or cant use adb for whatever reason just use visionary for temp root and then using root explorer move the gfree file to data>local then open terminal emulator and follow the instructions that gives you s-off and allows you to use visionary to permaroot when you reboot and then rommanager it now supports 3.xx so you can flash gingerroms just be careful and have fun
Greetings,
I am looking for an easy to understand method of root.
I have read the new user thread. I am afraid with this so called "easy" method for beginners, there is a lot of jargon used that I simply don't understand.
For example in the thread for easy root, I am lost at step #2 where I am instructed to:
"Note that adb is required.
Push misc.img, busybox, and psnueter using the following commands:"
I don't know what adb is let alone how to push misc.img, busybox and psnueter.
Can someone please point me to the instructions for absolute morons to this process like me.
Thanks in advance.
priapos said:
Greetings,
I am looking for an easy to understand method of root.
I have read the new user thread. I am afraid with this so called "easy" method for beginners, there is a lot of jargon used that I simply don't understand.
For example in the thread for easy root, I am lost at step #2 where I am instructed to:
"Note that adb is required.
Push misc.img, busybox, and psnueter using the following commands:"
I don't know what adb is let alone how to push misc.img, busybox and psnueter.
Can someone please point me to the instructions for absolute morons to this process like me.
Thanks in advance.
Click to expand...
Click to collapse
Android adb http://developer.android.com/guide/developing/tools/adb.html
which is in the sdk http://developer.android.com/sdk/index.html
You dont really need to know what the other tools are listed do, you just need to do what it says with them and the tools are linked in the thread you're reading to download I assume. If they aren't, then read through the manual method that is stickied in the developer's forum. A link for the tools (misc.img, busybox, and psnueter) can be found there.
I was a little nervous at first myself. I read over the directions several times and then found some information on how to get adb installed and working. Once I got that step understood the actual rooting process was super easy. You can cut and paste all the commands to ensure you don't typo. Just make sure to validate your checksums to save any potential headaches. My first attempt at it took about 20 minutes and I had absolutely ZERO issues.
It is well worth your time and effort. It is also far better to use this method than the easy root 1 steps as you will gain a slightly better understanding of how your phone works and what steps you can take when you inevitably mess something up flashing ROMS, mods and radios
Thanks for the quick reply.
I am not nervous, I just don't understand what any of this is.
I don't know what adb is or how to use it.
I don't know what copy and pasting the commands means.
I certainly don't know what "validate checksums" are.
I realize I am coming across as a comlete shmo, but explaining how to do this with more computer jargon doesn't clarify the process.
I really need instructions for dooshbags like me.
Thanks in advance.
There are also videos on YouTube showing JCases method and adb setup. I would link but I'm on my phone but it shouldn't be to hard to find.
Sent from my ADR6400L using XDA App
priapos said:
Thanks for the quick reply.
I am not nervous, I just don't understand what any of this is.
I don't know what adb is or how to use it.
I don't know what copy and pasting the commands means.
I certainly don't know what "validate checksums" are.
I realize I am coming across as a comlete shmo, but explaining how to do this with more computer jargon doesn't clarify the process.
I really need instructions for dooshbags like me.
Thanks in advance.
Click to expand...
Click to collapse
reading through this might help http://forum.xda-developers.com/showthread.php?t=1143188
There is no "easy", reliable way to root sans ADB and command lines. You will need to know this stuff before you try to root. You're going to need ADB in any event. If learning it isn't knowledge you desire, you shouldn't root your phone. For terms, you should refer to the dictionary stickied at the top of the forum. The best way to learn is to get the Android SDK, set it up, make sure your drivers are there, then play with ADB. Do simply stuff like check your serial number, the md5 of files on your SDcard, and harmless stuff like that. If you've got any questions along the way, feel free to PM me any time. I'm here often. And I'm usually faster than hunting through forums or the internet.
priapos said:
Greetings,
I am looking for an easy to understand method of root.
I have read the new user thread. I am afraid with this so called "easy" method for beginners, there is a lot of jargon used that I simply don't understand.
For example in the thread for easy root, I am lost at step #2 where I am instructed to:
"Note that adb is required.
Push misc.img, busybox, and psnueter using the following commands:"
I don't know what adb is let alone how to push misc.img, busybox and psnueter.
Can someone please point me to the instructions for absolute morons to this process like me.
Thanks in advance.
Click to expand...
Click to collapse
From what i think if u dont want the adb command line ****s you should try the software named "z4root". It automatically roots your phone.
Worked for me. And i think itz the easiest method available.
After installing the apk.
Open the application, click PERMANENT ROOT,
Then dnt let your phone sleep or lock itself, wait for about 10 minutes,
After the process reboot ypur phone.
Voila, you are rooted ..
Am new to the forums. please guide me..
Thanks and sorry for my poor english. Hope you like this.
Cheers!
__________________________________________________________
MODEL : LG Optimus GT540 (Rooted)
MOD : SwiftDroid v2.0 M6 (Based on CyanogenMod v7.1 RC0)
KERNEL : 2.6.29 (VirtualBox #309)
BUILD : GRJ22
RECOVERY : ClockworkMod Recovery v4.0
___________________________________________________________
BusyBox v1.19
SuperUser v2.3
SetCPU v2.2
I would not recommend "easy" root methods, since there is greater room for error. Understanding ADB will help you in the long run
MeAt.HoOk said:
From what i think if u dont want the adb command line ****s you should try the software named "z4root". It automatically roots your phone.
Worked for me. And i think itz the easiest method available.
After installing the apk.
Open the application, click PERMANENT ROOT,
Then dnt let your phone sleep or lock itself, wait for about 10 minutes,
After the process reboot ypur phone.
Voila, you are rooted ..
Am new to the forums. please guide me..
Thanks and sorry for my poor english. Hope you like this.
Cheers!
__________________________________________________________
MODEL : LG Optimus GT540 (Rooted)
MOD : SwiftDroid v2.0 M6 (Based on CyanogenMod v7.1 RC0)
KERNEL : 2.6.29 (VirtualBox #309)
BUILD : GRJ22
RECOVERY : ClockworkMod Recovery v4.0
___________________________________________________________
BusyBox v1.19
SuperUser v2.3
SetCPU v2.2
Click to expand...
Click to collapse
Don't think z4root works on the Thunderbolt just search youtube for Thunderbolt root and watch the tutorials. Links are provided for everything that needs to be downloaded.
Sent from my ADR6400L using XDA Premium App
I know z4root doesn't work for any modern HTC. You can have permanent root without s-off. The only way to do that is through ADB, using an engineering hboot, and applying various exploits. All the "easy" root methods are just scripts that do what jcase's guide lays out. And unlike the guide, if something goes south, you're lost and screwed. I think it would be safe to say "easy" roots have probably bricked more phones than anything else.
loonatik78 said:
I know z4root doesn't work for any modern HTC. You can have permanent root without s-off. The only way to do that is through ADB, using an engineering hboot, and applying various exploits. All the "easy" root methods are just scripts that do what jcase's guide lays out. And unlike the guide, if something goes south, you're lost and screwed. I think it would be safe to say "easy" roots have probably bricked more phones than anything else.
Click to expand...
Click to collapse
Is that u dbzfanatic? Looks awfully similar, lol.
Sent from my ADR6400L using XDA Premium App
nerogold said:
Is that u dbzfanatic? Looks awfully similar, lol.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Nope. Just a pieced up, inked up, "I been everywhere, man", freak of many talents and interests. Android phones are just one of them.
loonatik78 said:
Nope. Just a pieced up, inked up, "I been everywhere, man", freak of many talents and interests. Android phones are just one of them.
Click to expand...
Click to collapse
Sorry man I just wanted to say thanks to the other user I mentioned ,his method of rooting was and still is a great help to me already rooted 5 bolts and currently on #6 as I'm typing.
Sent from my ADR6400L using XDA Premium App
Do a google search for thunderbolt auto root. There is one posted in the Thuderbolt forums. I can't link directly to it because I don't have enough posts yet. I tested it on my wife's thunderbolt without a problem.
Greywolf66 said:
Do a google search for thunderbolt auto root. There is one posted in the Thuderbolt forums. I can't link directly to it because I don't have enough posts yet. I tested it on my wife's thunderbolt without a problem.
Click to expand...
Click to collapse
Yep, and the past guy to go that route, after being warned it was highly prone to failure, had it fail. Then he came back looking for help, but nobody could because what went wrong wasn't at all clear. Just not wise.
Ive used the one click root four times with no issues. Four diffrent tb's from 3 diffrent states. 2 of them had alrdy takin the ota's. Dont have the link handy but if was a time saver. Though a half arse understanding of the method helps avoid issues. Ill post the link when i get home.
Sent from my ADR6400L using XDA Premium App
loonatik78 said:
Yep, and the past guy to go that route, after being warned it was highly prone to failure, had it fail. Then he came back looking for help, but nobody could because what went wrong wasn't at all clear. Just not wise.
Click to expand...
Click to collapse
I rooted mine manually first. As you said in a previous post most "easy" roots are just scripts. That's what the one I used on my wife's was. I was following along the text of the batch file as I was running it so that if something happened I would know at what part of the script I was at. I had no problems with it though.
I'll agree that I could see where if someone where to run into a problem using script without any knowledge of what the script was doing they would probably end in a very bad place.
I think the obvious was missed in this thread: The OP is not a candidate for rooting. It's a risky task for experienced users and a non-task for noobs. He hasn't even stated a valid need for rooting the phone.
TabGuy said:
I think the obvious was missed in this thread: The OP is not a candidate for rooting. It's a risky task for experienced users and a non-task for noobs. He hasn't even stated a valid need for rooting the phone.
Click to expand...
Click to collapse
Come on, cut him some slack. Everyone was new once. He has already been warned.
Sent from my ADR6400L using XDA App
priapos said:
Thanks for the quick reply.
I am not nervous, I just don't understand what any of this is.
I don't know what adb is or how to use it.
I don't know what copy and pasting the commands means.
I certainly don't know what "validate checksums" are.
I realize I am coming across as a comlete shmo, but explaining how to do this with more computer jargon doesn't clarify the process.
I really need instructions for dooshbags like me.
Thanks in advance.
Click to expand...
Click to collapse
ADB "Android Development Bridge" Simply put just helps you develop apps and fix bugs. (In this case, you will use this to reinstall Android without a locked bootloader (a.k.a. S-Off) (the bootloader is code that is run when you first turn on your device that tells Android to run).
You don't have to know how to use ADB, but you must install it on your computer.
As far as copying and pasting commands go, the tutorial that you choose to visit will tell you to type this command ex: cp image.zip/sdcard/
You will just copy this code out of your browser (FireFox/Internet Explorer/Chrome/etc.) and paste it into a command line.
Your command line will depend on what operating system you use on your pc. Ex for Windows, you will use "Command Prompt" or on Linux/MAC you will use "Terminal".
As far as validation checksums goes, it is used to make sure that the file that you downloaded is 100% the same file that the developer made.
Basically, open up your command line and type (without quotes) "md5 image.zip" also, make sure you change to "image.zip" with whatever/where you file is at.
I would be more specific with these instructions I'd I knew what OS (operating system) you are using on your computer is.
After you type in the command and hit enter, it will spit out a long string of gibberish. Just make sure this "checksum" is the EXACT same as whatever the devolver put in the tutorial you are following.
As far as putting together an idiot proof guide, you will have to forgive us, but I don't think the people here want to have a bunch of people here flooding the forums with very basic questions that have been answered already on the internet. However, don't let that stop you from asking questions. Just make sure you help yourself first (Google what you don't understand) and then ask for clarification.
P.S. I claim touchscreen amnesty for any typos.
Sent from my ADR6400L using XDA App
Hello xda, I have a bit of a problem:
I have a Samsung Exhibit which I rooted using the zergRush method found here on the forums. At first everything worked fine. But recently I was trying to push a modified system app to my phone using adb and it told me the action wasn't permitted. Checking the shell, and terminal emulator on my phone to see if I had superuser permissions failed. So I went about trying to root my phone again, which according to the zergRush script said was successfull, but checking the shell once again showed that I still did not have superuser permissions. I did a factory wipe of my phone in hopes of trying to get it to root again with no success. But here's the weird part, although it doesn't appear I have root access all my apps that require root access (titanium backup, my screenshot app, and some of widgetlocker's features) still fully function.....
Does anyone have any idea what's going on here? I would love my system folder access back
Thanks in advance.
Dumb question, but your H-Boot shows S-Off? Just covering the bases... Also, do you have Super User installed and functional?
To be honest... I don't know what H-Boot or S-Off means. Pretty new to all of this. Mind giving me a walkthrough? I have superuser installed yes. It's granting programs superuser permissions. But I can't access su in terminal emulator or in the shell.
Well, I'm not the top tier technical person here, so I'm not exactly sure on how to get your problem resumed, since I've not heard of that. On the other hand, there might be a different way to accomplish what you are trying to do.
What are you trying to achieve, pushing a modified system app to do what and where? My suggestion, might be to just put it on your phone through USB to the root folder and then move it in ES File manager, or w/e you use. If all you are doing is pushing.
Obviously ADB shell detects your device, but I'm not sure why it is saying it doesn't have SU access. My other suggestion is to redo the ADB/Android SDK installs. I had a problem where I installed them wrong, by installing too much and ADB did not work properly. So, there might be a chance your phone is fine, but the ADB/SDK are not proper, somehow.
Let me know.
If that were the case, and my phone was fine, wouldn't I be able to access super user through terminal emulator on my phone? Right now when typing su in terminal emulator, the pop up to grant superuser permissions appears but when you allow it to have su permission the # doesn't turn to a $ like it should. The more I think about it the more I think it's a problem with superuser. I've seen people talking about an update to superuser that can break your root? Mehhhh.
Seems like other have had this problem too... Not sure if a nandroid recovery will fix this, otherwise you might have to try to unroot, and then reroot.
Sorry, just might have to do a little more digging than I was able to. Good luck