Im not stupid and i no how to read, just with this phone being kinda hard it took awhile to find the correct guide to downgrade and root.
i decided to follow this one, being updated this month
http://wiki.cyanogenmod.com/wiki/TM...l_Update_Guide#Rooting_the_TMobile_myTouch_4G
is this the correct one to use, cause i dont want to use the visionary app. heard that can be bad news
I also checked the emmc chip thru terminal emulator. and were good to go on that.
Ive already downgraded mt4g back to froyo.
but when copy/ paste commands for perm root, s off, h boot, when i paste line for su
it says failed, file is read only
everything still good with phone, i just want root and cwm
any help, would be appreciated and thanked
1) There's nothing wrong with Visionary or gfree. Don't be afraid.
2) cd to the directory of the file you're trying to run and chmod 777 the file. For instance, if the file was root.sh
chmod 777 root.sh
i remembered reading somewhere that using the visionary app can cause problems with lots of aggravation afterward.
and the phones not mine, im rooting it for a friend. ive rooted quite a few devices already but this is my first htc.
origionaly i ran the command at
C:\android sdk\platform-tools
all the command i had no problem with except when trying to push su
so are you saying i should change to
cd c:\android sdk\platform-tools\su>adb push su /sdcard/ ???
orginally i got back
failed to copy 'su' to '/sdcard//su': read-only file system
is it refering to my comp or android as read only file system?
trevor7428 said:
i remembered reading somewhere that using the visionary app can cause problems with lots of aggravation afterward.
and the phones not mine, im rooting it for a friend. ive rooted quite a few devices already but this is my first htc.
origionaly i ran the command at
C:\android sdk\platform-tools
all the command i had no problem with except when trying to push su
so are you saying i should change to
cd c:\android sdk\platform-tools\su>adb push su /sdcard/ ???
orginally i got back
failed to copy 'su' to '/sdcard//su': read-only file system
is it refering to my comp or android as read only file system?
Click to expand...
Click to collapse
I repeat, Visionary is fine.
Android.
I just used visionary today to root my wife's phone. I had to go through the whole downgrade process to get back to 2.2, and everything went very smooth. Now running JB from the codename thread and couldn't be happier with it.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Battery life is shaky on that rom, if you want to get the most out of your phone with jellybean, flash the CM10 port by 0.0 or Dark JellyBellyG1. Make sure to clear your batt stats before flashing darkjellybelly because codenamed messes with them.
THEindian said:
Make sure to clear your batt stats before flashing darkjellybelly because codenamed messes with them.
Click to expand...
Click to collapse
Unnecessary if he does a full wipe, which he should do between flashes anyway.
estallings15 said:
Unnecessary if he does a full wipe, which he should do between flashes anyway.
Click to expand...
Click to collapse
Hmm, a full wipe didn't work for me. I got off Codename and went back to insertcoin which i KNOW has awesome battery life and got mediocre battery life, not really different from Codename. Don't even nag me about the full wipe because I did it! lol.
THEindian said:
Hmm, a full wipe didn't work for me. I got off Codename and went back to insertcoin which i KNOW has awesome battery life and got mediocre battery life, not really different from Codename. Don't even nag me about the full wipe because I did it! lol.
Click to expand...
Click to collapse
Flash at 100% and drain it down then recharge. Battery life should normalize after that.
Downgrade and Root Guide..!
this is how i did mine..!
http://minus.com/mu9vZ3P38/
:good:
So I still don't no what I'm doing wrong. I've successfully downgrading.and when using visionary.apk. it says unknown user root. After entering su in terminal emulator. I've tried visionary11 and 14 and a plusversion. All with same results. R/W is checked and hit temp root
I've never had this much trouble rooting any tab or phone
trevor7428 said:
So I still don't no what I'm doing wrong. I've successfully downgrading.and when using visionary.apk. it says unknown user root. After entering su in terminal emulator. I've tried visionary11 and 14 and a plusversion. All with same results. R/W is checked and hit temp root
I've never had this much trouble rooting any tab or phone
Click to expand...
Click to collapse
Enable usb debugging in settings and reboot between every attempt with visionary.
estallings15 said:
Enable usb debugging in settings and reboot between every attempt with visionary.
Click to expand...
Click to collapse
Enable usb debugging in settings and reboot between every attempt with visionary
Click to expand...
Click to collapse
I already have USB debugging enabled, fastboot off. And I restart pull out battory, and even tried uninstalling visionary and reinstaling. There has to be something I'm missing. And just to verify I did downgrade to 2.2.1
trevor7428 said:
I already have USB debugging enabled, fastboot off. And I restart pull out battory, and even tried uninstalling visionary and reinstaling. There has to be something I'm missing. And just to verify I did downgrade to 2.2.1
Click to expand...
Click to collapse
Do a factory reset maybe, just to clean the slate.
factory reset is your best bet dude..! save all your data from your memory card onto your computer or something and format your memory card as well. then do a complete factory reset. it really does solve issues. but ofcourse, it's always a pain recustomizing your phone but yea...!
mokee92 said:
factory reset is your best bet dude..! save all your data from your memory card onto your computer or something and format your memory card as well. then do a complete factory reset. it really does solve issues. but ofcourse, it's always a pain recustomizing your phone but yea...!
Click to expand...
Click to collapse
Hell ya I hate factory reset without root lol. I was hoping I was doing one tiny lil thing wrong. Which was a super easy fix. Lol well if anyone can think of anything else. Let me no. Its my buddies phone. So can't try now. Any other ideas will be thanked too
Related
My buddy got this phone I want to hook it up as he's not great with tech stuff i rooted with z4root and just need to know how to access recovery cause i didn't see a reinstall packages option in standard recovery ? Any help would be awesome thanks guys
I just rooted with Z4root... then I installed Titanium Backup and then ROM Manager, giving both apps root access (which I verified with the SuperUser app). In ROM Manager I did "Flash ClockworkMod Recovery" and chose the Fascinate option and was told that it downloaded the latest ClockworkMod Recovery. What's my next step?... Choose "Reboot into Recovery" within ROM Manager or do it another way. (My goal is to install Voodoo5 using the stock ROM for now. I have the Voodoo5 file on the SD card.)
EDIT: Whoops. I just realized that I had downloaded the two files to get CWM working but hadn't followed the unzipping, etc. instructions. I'd better go back and read that CWM thread again...
First get CWM working
Then check out this ROM
Or this ROM
and if you really wanna get fancy check out this kernel
Just in case you screw up
If you need more help on each specific topic, just ask in the appropriate areas and there is usually someone around that can answer questions.
Thanks for the quick links... really appreciate it.
BTW - Titanium Backup asks for USB Debugging to be enabled... do you have to do this? It creates issues for me when connecting the phone as mass storage to my PC.
ALSO - I'm assuming I should take an initial backup with Ti before I get too far into this, right? Not having done a backup before... is Ti the best to use? (Do I just choose batch and pick an option(s)? Does choosing "Backup user apps + system data" backup game save data?) EDIT: Just did this and it ran fine but it switched my Live wallpaper back to stock?!? WTF?
monthlymixcd said:
Thanks for the quick links... really appreciate it.
BTW - Titanium Backup asks for USB Debugging to be enabled... do you have to do this? It creates issues for me when connecting the phone as mass storage to my PC.
ALSO - I'm assuming I should take an initial backup with Ti before I get too far into this, right? Not having done a backup before... is Ti the best to use? (Do I just choose batch and pick an option(s)? Does choosing "Backup user apps + system data" backup game save data?)
Click to expand...
Click to collapse
Quick links are awesome! They save time, for sure.
Check the box to ask each time for mass storage and kies. Then you can have debugging enabled, and yes you have to have it enabled or TB won't do it's thing properly. You can switch it back and forth also. That's what I do.
I use TB to do my app and system data backups. Just run a batch backup on user apps and system data, like you said. That's the best option to start with. This isn't the same as a nandroid backup, but it's a good second choice for if you need to wipe data and restore apps quickly like a ROM install that requires you to wipe data/factory reset.
phidelt82 said:
Check the box to ask each time for mass storage and kies. Then you can have debugging enabled, and yes you have to have it enabled or TB won't do it's thing properly. You can switch it back and forth also. That's what I do.
Click to expand...
Click to collapse
Perfect. Thanks! Only thing is... USB dubugging doesn't stay ticked, it's ticked and Ti says it's not, or the connection still triggers a missing driver error message with Vista on the PC. Oh well.
phidelt82 said:
This isn't the same as a nandroid backup, but it's a good second choice for if you need to wipe data and restore apps quickly like a ROM install that requires you to wipe data/factory reset.
Click to expand...
Click to collapse
Easiest way to do a Nandroid backup? BTW - Ti backup ate up 5GB of my sd card?!? Yikes!
Also, regarding this thread:
phidelt82 said:
First get CWM working
Click to expand...
Click to collapse
I get "adb: not found"?
monthlymixcd said:
Perfect. Thanks!
Easiest way to do a Nandroid backup?
Also, regarding this thread:
I get "adb: not found"?
Click to expand...
Click to collapse
Nandroid backup will be there once you get CWM working.
You can do everything from the phone, just read down through the pages to find the people that have done it. They have left instructions using terminal emulator and root explorer. You will find that in a lot of instances many problems will have different ways of dealing with them. You probably don't have the Android SDK which is how you get ADB working on your computer. This isn't critical, it just makes it so that you will have to either install it or use the other means available. (ie terminal emulator and root explorer)
Still getting errors after trying several of the things in the thread... Q:I never did get a robot voice when I ran Z4root and never saw a place to choose permanent... should I run Z4root again? I mean, I was able to install Ti, etc. so I must have root, right? But I think my issues stem from not being able to get redbend_ua into the /system/xbin folder. Astro can't paste it there, Root Explorer can't paste it there, but in the terminal it appears like chmod worked... thoughts?
monthlymixcd said:
Still getting errors after trying several of the things in the thread... Q:I never did get a robot voice when I ran Z4root and never saw a place to choose permanent... should I run Z4root again? I mean, I was able to install Ti, etc. so I must have root, right? But I think my issues stem from not being able to get redbend_ua into the /system/xbin folder. Astro can't paste it there, Root Explorer can't paste it there, but in the terminal it appears like chmod worked... thoughts?
Click to expand...
Click to collapse
Root explorer needs to be mounted RW. There is a button at the top that will say RO or RW.
Sent from my SCH-I500 using XDA App
phidelt82 said:
Root explorer needs to be mounted RW. There is a button at the top that will say RO or RW.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
"Mounted as r/w"
I tried this. Used root explorer to finally get redbend_ua into system/xbin but when I try to run the commands in the post it cannot find redbend_ua. I also cannot cd into xbin within the emulator to ls ... says xbin not found. Explorer can see it there... what gives? do you have to restore redbend_ua inside the xbin directory or will it work to restore it elsewhere?
EDIT: cd to /system/xbin worked and an ls shows the redbend_ua there but the chmod 777 redbend_ua fails to "Unable to chmod redbend_ua: No such file or directory
EDIT to the EDIT: Hang on... think I may have found where I went wrong. What's the terminal command for delete?
monthlymixcd said:
"Mounted as r/w"
I tried this. Used root explorer to finally get redbend_ua into system/xbin but when I try to run the commands in the post it cannot find redbend_ua. I also cannot cd into xbin within the emulator to ls ... says xbin not found. Explorer can see it there... what gives? do you have to restore redbend_ua inside the xbin directory or will it work to restore it elsewhere?
Click to expand...
Click to collapse
Are you doing /system/xbin? The first / is important. You don't need to cd to xbin, though.
Sent from my SCH-I500 using XDA App
Isn't there anyway to flash a rom using odin ? If not are the codes the same for terminal emulator as they are for adb to get cwm working? I'm from the vibrant section of this site running nero v4 right now I have a good understanding of odin for the most part but this not having an easy recovery is bs lol
willsnews said:
Isn't there anyway to flash a rom using odin ? If not are the codes the same for terminal emulator as they are for adb to get cwm working? I'm from the vibrant section of this site running nero v4 right now I have a good understanding of odin for the most part but this not having an easy recovery is bs lol
Click to expand...
Click to collapse
I've never flashed a ROM using Odin, but that doesn't mean that it can't be done. The process should be the same using terminal emulator or adb, just more of a pain. I agree it would be nice to have full CWM Recovery support (or any full recovery support) but I don't have the money to spend on a phone to send to Koush right now to get that done. As soon as I do, this will be done and then I'll have a tester phone for firmware builds. It really isn't that difficult to get it working, though. I've done it probably 30-40 times now and even the first time the only flub was in a typo for the second to last character (thought it was a 1 and not an L)
So you type this stuff in all in one line or what?
willsnews said:
So you type this stuff in all in one line or what?
Click to expand...
Click to collapse
Depending on which parts you are talking about, yes. Each new line is a line of code. If it moves to a new line, hit enter.
phidelt82 said:
Are you doing /system/xbin? The first / is important. You don't need to cd to xbin, though.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Yes. Something's definitely up 'cause when I try to use Astro to copy redbend_ua to /system/xbin the paste option is grayed out for that directory.
monthlymixcd said:
Yes. Something's definitely up 'cause when I try to use Astro to copy redbend_ua to /system/xbin the paste option is grayed out for that directory.
Click to expand...
Click to collapse
I can't remember if Astro has R/W options for the root directory. That may be the problem.
phidelt82 said:
Depending on which parts you are talking about, yes. Each new line is a line of code. If it moves to a new line, hit enter.
Click to expand...
Click to collapse
I just ned to get a custom recovery how did you type it in to terminal emulator? Like extacy how?i just dont want to mess up my buddies phone I want yo hook him up not **** him up lol
monthlymixcd said:
Yes. Something's definitely up 'cause when I try to use Astro to copy redbend_ua to /system/xbin the paste option is grayed out for that directory.
Click to expand...
Click to collapse
You guys are confusing the hell outta me I don't know who's answering me and who's answering you I know this pertains to this thread but im right in the middle of this process and its not even my phone
I apologize for the derail... I got mine working. I had a typo. I'm off to voodoo.
so im a previous iphone user and need something new to play with......i follow the instructions to root with visionary but my S is always on and wont be S-off.......what do i do?
Visionary can not perform S-OFF. People tried to come up with 1-click app to do that but it's not possible, at least right now.
Follow this guide to make it happen. It's not as hard as it looks.
borodin1 said:
Visionary can not perform S-OFF. People tried to come up with 1-click app to do that but it's not possible, at least right now.
Follow this guide to make it happen. It's not as hard as it looks.
Click to expand...
Click to collapse
ok yea i did this and from some reason the sdk is not picking up my mt4g......ive been actually trying since i posted this thread lol. things are just not cooperating with me
For me yo get s off o have go put a stock rom on my phone maybe that will help
Sent from my HTC Glacier using XDA App
cdw9800 said:
For me yo get s off o have go put a stock rom on my phone maybe that will help
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
I have a stock rom on though
Sent from my HTC Glacier using Tapatalk
Flipnfr3ak said:
so im a previous iphone user and need something new to play with......i follow the instructions to root with visionary but my S is always on and wont be S-off.......what do i do?
Click to expand...
Click to collapse
same as you(*), until last week when i came across this dude, who made it seem so easy. follw these links, and you will gain s-off with sim unlock through gfree 2:
http://www.youtube.com/watch?v=RyELJRy4rhE
http://www.youtube.com/watch?v=dXsORU5_rxI
http://www.youtube.com/watch?v=KvfHC1dQ0D4
http://www.youtube.com/watch?v=sIVMIwMgrWM
pay attention to it though, you don't wanna have a bricked new phone now!
------------------------------------------------------------------------------------------------
*by " same as you" i mean i was heaving a hard time gaining s-off, until these videos
Hi guys, my girlfriend just got a MT4G today and I'm having problems getting s-off too.
I've tried all methods and nothing seems to be working. Any suggestions? If you need more info just ask, but like i said, i've tried like three different ways and none work. I'll edit this post soon and add what common errors im getting
I couldnt get it done with Visionary r14, instead of getting the option screen when I opened it, it went straight to the rooting phone screen and just didnt work
I found r11 and used it instead and that solved my problem, the rest of the process went easy
PhantomRampage said:
Hi guys, my girlfriend just got a MT4G today and I'm having problems getting s-off too.
I've tried all methods and nothing seems to be working. Any suggestions? If you need more info just ask, but like i said, i've tried like three different ways and none work. I'll edit this post soon and add what common errors im getting
Click to expand...
Click to collapse
I had the same problem. I used one way to turn S-off when I had the myTouch 4g with the radio 0.85.xxxx. When I had my phone swapped since I made up an excuse to get the good screen, the radio was 0.86.xxxx. I tried to follow the same steps as I did with 0.85.xxxx, but wouldn't work. So I ended up trying the ULTIMATE GUIDE TO ROOT and it worked. I put everything unlocked even SIM. THen I used VISIONary r14 to have it root then perm root.
mbstang said:
I couldnt get it done with Visionary r14, instead of getting the option screen when I opened it, it went straight to the rooting phone screen and just didnt work
I found r11 and used it instead and that solved my problem, the rest of the process went easy
Click to expand...
Click to collapse
I tried r11 but it didn't work so I went to r14 with the ULTIMATE GUIDE TO ROOT and it works. So I guess each is their own.
Ok so I'm still having trouble with this. Can anyone tell me what I need to download for the sdk kit? I have a acer aspire one laptop either a d150 or a150.i don't know what the difference is. Running windows xp sp2 or 3 lol
Sent from my HTC Glacier using XDA App
Flipnfr3ak said:
Ok so I'm still having trouble with this. Can anyone tell me what I need to download for the sdk kit? I have a acer aspire one laptop either a d150 or a150.i don't know what the difference is. Running windows xp sp2 or 3 lol
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Dont even bother setting up the SDK. It is a pain in the arse!!! Use this method if you need to set up ADB.
Thank you I was looking for something like this
Sent from my HTC Glacier using Tapatalk
Seriously people, don't you read threads? The rooting method is very easy and does not require ADB or the SDK. I've rooted *5 PHONES* on the first try by reading and just following the damn directions.
You temproot, run a couple of commands in terminal, reboot, temproot, permroot, and go on your merry way.
If this doesn't work follow the guide for gfree and that will do it.
Here, I made a SUPER-STEP-BY-STEP guide. If this is still too complicated for you then you really shouldn't be rooting at all, as it requires some basic knowledge of how to use a computer and the phone. And I mean BASIC.
http://forum.xda-developers.com/showthread.php?t=834225
This one is pretty damn easy, takes all of 10 minutes. Use the Terminal Emulator method.
Read the first post all the way through before you start to make sure you understand the entire process. In a nutshell, here's what happens:
*Download root.rar and extract to be a folder called ROOT on your sdcard. The ROOT folder should not be inside any other folders, so it will be sdcard/root.
*Download a file manager from the Market. Linda File Manager is my favorite.
*Download Terminal Emulator from the Market.
*Download the Visionary.apk file from the link in thread.
*from home screen - MENU, SETTINGS, APPLICATIONS, ALLOW INSTALL OF NON-MARKET APPS. Make sure the box is checked. ALSO UNCHECK FAST BOOT.
*Open linda file manager, navigate to visionary and click on it to install.
*Reboot. This will take a minute.
*Open visionary, check the box for SET SYSTEM R/W AFTER ROOT.
*Hit button for TEMP ROOT. Give it a minute.
*Open Terminal Emulator and type THE ITALIC COMMANDS, pressing ENTER after each.
su
*You should get a prompt for SUPERUSER PERMISSIONS. Click ALLOW. Back in Terminal, continue with these commands, typing them EXACTLY as they appear and pressing ENTER after each line.
cd sdcard/root
sh root.sh
*Now just wait a few minutes.
*When it's done, shut down the phone.
*Hold volume down + power until you get to a white screen. If it says S-OFF near the top then you're almost done. If not, repeat the previous steps until you do see S-OFF.
*Reboot.
*Open visionary, make sure SET SYSTEM R/W AFTER ROOT is checked.
*Click TEMP ROOT.
*When done, click ATTEMPT PERM ROOT. This might take a few minutes. Your phone will reboot itself when done. (I think)
When you boot back up you should be permanently rooted and you are ready to install a custom ROM if you like.
*To verify that you are rooted, open Terminal Emulator and type su. If you get the # sign and a notice that superuser permissions were granted, then you have succeeded in rooting your phone. Congrats!
Installing a custom ROM is another procedure so do a search for the guides on those procedures.
Click to expand...
Click to collapse
Phateless said:
Seriously people, don't you read threads? The rooting method is very easy and does not require ADB or the SDK. I've rooted *5 PHONES* on the first try by reading and just following the damn directions.
You temproot, run a couple of commands in terminal, reboot, temproot, permroot, and go on your merry way.
If this doesn't work follow the guide for gfree and that will do it.
Here, I made a SUPER-STEP-BY-STEP guide. If this is still too complicated for you then you really shouldn't be rooting at all, as it requires some basic knowledge of how to use a computer and the phone. And I mean BASIC.
Click to expand...
Click to collapse
see ive done this many many times and my s just wont turn off.....its always on
Flipnfr3ak said:
see ive done this many many times and my s just wont turn off.....its always on
Click to expand...
Click to collapse
Are you making sure that "set system to r/w" and "run visionary.sh" are both checked at the time of temproot.
and are you getting any type of error codes when you type in the command lines.
Flipnfr3ak said:
see ive done this many many times and my s just wont turn off.....its always on
Click to expand...
Click to collapse
Assuming you're doing it correctly, some phones have trouble. Look for the guide titled ULTIMATE S-OFF, CHECK OUT EVEN IF ALREADY ROOTED.
http://forum.xda-developers.com/showthread.php?t=858996
The gfree method should do the trick.
I got it working after 4 hours -__- I'm not sure if it had anything to do with it, but once i removed the sim card it seemed to work. Got s-off and permroot and even flashed cm7 nightlies afterwards with no problems, then put the sim back i n
Phateless said:
Assuming you're doing it correctly, some phones have trouble. Look for the guide titled ULTIMATE S-OFF, CHECK OUT EVEN IF ALREADY ROOTED.
http://forum.xda-developers.com/showthread.php?t=858996
The gfree method should do the trick.
Click to expand...
Click to collapse
See I didnt do the visionary.sh check off part haha I don't remember see that part in the guide
Sent from my HTC Glacier using XDA App
I give up already I just can't get it to work nothing is working
Sent from my HTC Glacier using XDA App
Flipnfr3ak said:
I give up already I just can't get it to work nothing is working
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
SLOW DOWN, read the directions CAREFULLY, and make sure you understand the entire process before starting. I probably read the guides 20 times from start to finish before I rooted.
Here's a super-newbie step-by-step guide I typed up.
http://forum.xda-developers.com/showthread.php?t=834225
This one is pretty damn easy, takes all of 10 minutes. Use the Terminal Emulator method.
Read the first post all the way through before you start to make sure you understand the entire process. In a nutshell, here's what happens:
*Download root.rar and extract to be a folder called ROOT on your sdcard. The ROOT folder should not be inside any other folders, so it will be sdcard/root.
*Download a file manager from the Market. Linda File Manager is my favorite.
*Download Terminal Emulator from the Market.
*Download the Visionary.apk file from the link in thread.
*from home screen - MENU, SETTINGS, APPLICATIONS, ALLOW INSTALL OF NON-MARKET APPS. Make sure the box is checked. ALSO UNCHECK FAST BOOT.
*Open linda file manager, navigate to visionary and click on it to install.
*Reboot. This will take a minute.
*Open visionary, check the box for SET SYSTEM R/W AFTER ROOT.
*Hit button for TEMP ROOT. Give it a minute.
*Open Terminal Emulator and type THE ITALIC COMMANDS, pressing ENTER after each.
su
*You should get a prompt for SUPERUSER PERMISSIONS. Click ALLOW. Back in Terminal, continue with these commands, typing them EXACTLY as they appear and pressing ENTER after each line.
cd sdcard/root
sh root.sh
*Now just wait a few minutes.
*When it's done, shut down the phone.
*Hold volume down + power until you get to a white screen. If it says S-OFF near the top then you're almost done. If not, repeat the previous steps until you do see S-OFF.
*Reboot.
*Open visionary, make sure SET SYSTEM R/W AFTER ROOT is checked.
*Click TEMP ROOT.
*When done, click ATTEMPT PERM ROOT. This might take a few minutes. Your phone will reboot itself when done. (I think)
When you boot back up you should be permanently rooted and you are ready to install a custom ROM if you like.
*To verify that you are rooted, open Terminal Emulator and type su. If you get the # sign and a notice that superuser permissions were granted, then you have succeeded in rooting your phone. Congrats!
Installing a custom ROM is another procedure so do a search for the guides on those procedures.
Click to expand...
Click to collapse
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
Hey guys
I screwed up my vold.fstab trying to get "_ExternalSD" back.
Unfortunately! I did not run a nandroid before I made the change.
Now, I can dirty flash my rom on top, or go back to a nandroid from a few days ago, but I'd really just like to recover and go on my merry way. And maybe learn something in the process.
Only thing is, I can't figure out how to access the phone other than the External SD card through CWM.
Can I mount the internal /system and access through USB? Is there some facility to copy a file from one point to another? Any other methods? I guess the phone has to be up to run ADB, right?
I don't know how to generate a flashable zip but I could extract the original version of the file from the original rom. I assume that its non trivial to create a flashable zip, but maybe someone can comment? It looks like there is signing and certificates involved..
thanks for any ideas
bluenote73 said:
Hey guys
I screwed up my vold.fstab trying to get "_ExternalSD" back.
Unfortunately! I did not run a nandroid before I made the change.
Now, I can dirty flash my rom on top, or go back to a nandroid from a few days ago, but I'd really just like to recover and go on my merry way. And maybe learn something in the process.
Only thing is, I can't figure out how to access the phone other than the External SD card through CWM.
Can I mount the internal /system and access through USB? Is there some facility to copy a file from one point to another? Any other methods? I guess the phone has to be up to run ADB, right?
I don't know how to generate a flashable zip but I could extract the original version of the file from the original rom. I assume that its non trivial to create a flashable zip, but maybe someone can comment? It looks like there is signing and certificates involved..
thanks for any ideas
Click to expand...
Click to collapse
this is why i hate it when people make those guides.
messing with the vold.fstab is dangerous (even though its only a few lines) if your trying to recover your data, give up. its not going to happen. (sorry)
when you edit the vold.fstab it messed up the partitions on your internal SD card and most likely did the equivalent of wiped your /system partition. (or another important one.) your actually lucky it did not completely brick your phone.
your post was a little vague, but if you can, just restore an older nandroid, or wipe everything and install another ROM. (you can try dirty flashing but i dont think itll work)
if you cannot access CWM, then follow the steps in This guide. it should get you back up on your feet. after you follow that guide flash a gingerbread ROM (any gingerbread rom will do fine) then you can reboot and flash any ROM you want. (it needs this to fix a quirk in that script)
Hope you get it fixed
EDIT: re read your post, if your feeling adventurous and want to give it a shot, boot into CWM and connect it via usb. you can now get into an ADB shell on your phone by typing 'adb shell' if you have adb all setup and working. (im working from memory here so dont quote me on any of this)
now, you should be able to access your /system folder from that shell. be very careful though, i dont have much experience right here, and if i remember correctly you might not be in the full root directory yet)
if you can get into it try replacing your vold.fstab with a stock one,
if you dont have a stock one lying around, make a nandroid of the current state of the rom, then flash another rom, pull the vold.fstab, then re-restore back to the broken one and restore it (id upload mine but my phone is OOC right now )
after that just reboot and hope it resolves itself, if not then just follow my advice above
and keep that guide i linked to handy, messing around in CWM has the ability to brick your phone, if it does, then just follow that guide.
Klathmon said:
this is why i hate it when people make those guides.
messing with the vold.fstab is dangerous (even though its only a few lines) if your trying to recover your data, give up. its not going to happen. (sorry)
when you edit the vold.fstab it messed up the partitions on your internal SD card and most likely did the equivalent of wiped your /system partition. (or another important one.) your actually lucky it did not completely brick your phone.
your post was a little vague, but if you can, just restore an older nandroid, or wipe everything and install another ROM.
if you cannot access CWM, then follow the steps in This guide. it should get you back up on your feet. after you follow that guide flash a gingerbread ROM (any gingerbread rom will do fine) then you can reboot and flash any ROM you want. (it needs this to fix a quirk in that script)
Hope you get it fixed
Click to expand...
Click to collapse
How bout adb and pushing the file back in? Or cant you access the phone via adb?
Sent from my LG-P970 using XDA
N00BY0815 said:
How bout adb and pushing the file back in? Or cant you access the phone via adb?
Sent from my LG-P970 using XDA
Click to expand...
Click to collapse
re read your post and updated my last post right after you posted
after dealing with noobies all day, i forget sometimes people want to try big things
Thanks guys. The info I was missing was there's no special trick to attaching adb while in CWM! Just plug in!
My phone is back up and running and partitions are fine as far as I can see after just booting up.
Hi there! I messed up with the vold.fstab filfe on my tablet – I replaced it with a downloaded file with the intention to transfer apps to my external SD card.
Now my tablet is only showing the startup logo and won’t continue loading. I can access recovery mode. Now I want to restore the original vold.fstab file.
My questions:
1. Using the Android SDK, the file explorer does not show any files, though my tablet is recognized.
2. Using adb push, it yields an error: permission denied, how to successfully push the original vold.fstab and replace the existing vold.fstab?
3. If I dump an image of my tablet and edit the dumped image, would this be easier compared to the steps above?
Thanks!
http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.
TwitchyEye said:
http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.
Click to expand...
Click to collapse
Thanks, I will try it later when I got home. My tablet is not found here. I have a Skyworth S71(3G) with RK3066 chipset.
BryanF said:
Thanks, I will try it later when I got home. My tablet is not found here. I have a Skyworth S71(3G) with RK3066 chipset.
Click to expand...
Click to collapse
You need to do an adb remount before you can push. Was it rooted before?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Mansa_noob, yes, my tablet is rooted. I followed some instructions about adb but had an error saying access denied, and also no files are displayed at file explorer. See my posts above. I also mounted it successfully. I will post some sreenshots later.
Please if you have some instructions, I am willing to try.
---------- Post added at 07:06 AM ---------- Previous post was at 07:02 AM ----------
TwitchyEye said:
http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.
Click to expand...
Click to collapse
Hi twitchyEye, it did not work. It attemps to install (using the install update from ext sd card) but then says installation aborted.
Any more suggestions? Thanks
What recovery are you using? I suck with adb so I got nothing on that front.
It was the stock recovery from my Tablet. I don't have it on hand right now, I will post later. The chipset is RK3066. My problem is my tablet has no official support on the internet (maybe becaue it's still new). Model is Skyworth S71(3G).
I see. Yeah this is over my head man. I thought for sure you were running a custom recovery and it was an easy answer. I'm actually struggling right now with adb myself with a similar issue something about permissions whenever I try to do anything to my phone. So I guess right now would be a perfect time for somebody to chime in with a smarter answer!
TwitchyEye said:
I see. Yeah this is over my head man. I thought for sure you were running a custom recovery and it was an easy answer. I'm actually struggling right now with adb myself with a similar issue something about permissions whenever I try to do anything to my phone. So I guess right now would be a perfect time for somebody to chime in with a smarter answer!
Click to expand...
Click to collapse
Are you doing adb remount and still getting permission denied?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
mansa_noob said:
Are you doing adb remount and still getting permission denied?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
Yes, I did adb remount and still access denied
BryanF said:
Yes, I did adb remount and still access denied
Click to expand...
Click to collapse
This is strange. A properly rooted phone would adb remount to r/w system. Something is fishy. Is it rooted+
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
mansa_noob said:
This is strange. A properly rooted phone would adb remount to r/w system. Something is fishy. Is it rooted+
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
I am sure it is rooted, because I downloaded an application from Google play to check it it is rooted or not. It is really rooted. I alvo confirmed this as I can now fully backup and restore my apps using Titanium backup before the tablet is messed up.
BryanF said:
I am sure it is rooted, because I downloaded an application from Google play to check it it is rooted or not. It is really rooted. I alvo confirmed this as I can now fully backup and restore my apps using Titanium backup before the tablet is messed up.
Click to expand...
Click to collapse
OK. Odd or not, it is what it is. Is it possible for you to load a custom recovery?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
mansa_noob said:
OK. Odd or not, it is what it is. Is it possible for you to load a custom recovery?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
I want to try, but the stock recovery is my last hold as I have no stock ROM. If I overwrite the stock ROM, I cannot reinstall it as I don't have a copy of it.
So why not flash cwm with nvflash and then make a backup of your current stock rom? I did exactly that.
Sent from my LG-P999 using xda premium
Hey guys. I admit it....I'm a noob here (man it hurts to say that).
Anyway, I've been attempting to root my Tab 2 10.1 (P5113 w/ 4.0.4 upgrade) using the method weltwon describes here: thread 1657056 and I keep running into the following problem. When attempting to root it Odin keeps getting stuck at the "recovery.img" step (I've let the tablet sit for nearly 30 minutes at that step with no luck).
Based on some other posts I've attempted all the following with no luck:
Removed Lockout Security & Antivirus from the tablet
Disabled antivirus on the computer
Ensured the tablet is directly plugged into a motherboard usb port
Nothing has helped. The only thing I haven't tried is shifting to a different computer (only have a single computer at home). Fortunately I can force reboot the tablet and it comes back up to the stock ROM with no issues.
I'm using Odin V1.85_3 and running Windows 7 64-bit. Any ideas would be greatly appreciated.
Alan
SlickAl41 said:
Hey guys. I admit it....I'm a noob here (man it hurts to say that).
Anyway, I've been attempting to root my Tab 2 10.1 (P5113 w/ 4.0.4 upgrade) using the method weltwon describes here: thread 1657056 and I keep running into the following problem. When attempting to root it Odin keeps getting stuck at the "recovery.img" step (I've let the tablet sit for nearly 30 minutes at that step with no luck).
Based on some other posts I've attempted all the following with no luck:
Removed Lockout Security & Antivirus from the tablet
Disabled antivirus on the computer
Ensured the tablet is directly plugged into a motherboard usb port
Nothing has helped. The only thing I haven't tried is shifting to a different computer (only have a single computer at home). Fortunately I can force reboot the tablet and it comes back up to the stock ROM with no issues.
I'm using Odin V1.85_3 and running Windows 7 64-bit. Any ideas would be greatly appreciated.
Alan
Click to expand...
Click to collapse
Keep trying... odin sucks. Heimdale is better, but it is a little more complicated lol still figuring it out on my end with my infuse every once in a while.
If nothing else works you might be able to restore to stock... but I agree Heimdall is a better option.
Ryanscool said:
Keep trying... odin sucks. Heimdale is better, but it is a little more complicated lol still figuring it out on my end with my infuse every once in a while.
Click to expand...
Click to collapse
Heimdall did it. Thanks for pointing me that direction. :highfive:
SlickAl41 said:
Heimdall did it. Thanks for pointing me that direction. :highfive:
Click to expand...
Click to collapse
Well, I thought Heimdall did it. Guess I celebrated a bit early there. When attempting to boot into CWM I get thrown over to the Stock Android Recovery. Based on some more searching it looks like I'll have to roll back to 4.0.3 before flashing recovery.img. Back to the web and to figure that portion out.
Alan
SlickAl41 said:
Well, I thought Heimdall did it. Guess I celebrated a bit early there. When attempting to boot into CWM I get thrown over to the Stock Android Recovery. Based on some more searching it looks like I'll have to roll back to 4.0.3 before flashing recovery.img. Back to the web and to figure that portion out.
Alan
Click to expand...
Click to collapse
Alan, that's because the tabs have a script called install-recovery.sh that re-installs the stock recovery on each boot. you will need to find and remove that before the recovery flash will hold.
trying to find the thread that talked about where that script is located.... but if you have root explorer installed search and you'll find it. I would suggest saving a copy of it to the sdcard before removing it from the system... just incase it is ever needed for anything.
Ryan79 said:
Alan, that's because the tabs have a script called install-recovery.sh that re-installs the stock recovery on each boot. you will need to find and remove that before the recovery flash will hold.
trying to find the thread that talked about where that script is located.... but if you have root explorer installed search and you'll find it. I would suggest saving a copy of it to the sdcard before removing it from the system... just incase it is ever needed for anything.
Click to expand...
Click to collapse
Ok, now I feel like my head is starting to spin. The script is located in /etc (not to surprising there). This is where my head starts to spin. /etc has permissions of 777 (which rather blew my mind based on past unix and linux experience). Install.recover.sh has permissions of 544 which I would expect for an executable in /etc. That means I have to have root permissions to modifiy the file since root is the owner.
So, from my understanding I need to get CWM recovery installed so I can flash cwm-root which will grant me root access......seems kinda like a case of the chicken and the egg to me.
SlickAl41 said:
Ok, now I feel like my head is starting to spin. The script is located in /etc (not to surprising there). This is where my head starts to spin. /etc has permissions of 777 (which rather blew my mind based on past unix and linux experience). Install.recover.sh has permissions of 544 which I would expect for an executable in /etc. That means I have to have root permissions to modifiy the file since root is the owner.
So, from my understanding I need to get CWM recovery installed so I can flash cwm-root which will grant me root access......seems kinda like a case of the chicken and the egg to me.
Click to expand...
Click to collapse
Ok, I think I may see how to get around this.....Heimdall is rebooting my tablet after the recovery flash. Need to figure out the command line parameter that prevents reboot and then reboot directly to CWM Recover (guessing there but that's what I'm going to look for at least).
That did it.....found the --no-reboot common argument for Heimdall and then manually rebooted directly to CWM Recovery. That allowed me to boot into CWM Recovery without the install.recover.sh shell running. Waiting for first reboot after flashing the CWM-Root.....rebooted installed SuperUser and disabled SuperSU but still can't rename or delete the /etc/Install.recover.sh (even though the root browser was given su permissions by SuperUser) ..... sigh
I know I'm rooted because I can reboot using Quick Boot after granting it su access - that's just strange.
Finally, figured it out...You can't modify or delete Install.recover.sh in /etc. You must do it at the following location /system/etc
Alan
SlickAl41 said:
Ok, I think I may see how to get around this.....Heimdall is rebooting my tablet after the recovery flash. Need to figure out the command line parameter that prevents reboot and then reboot directly to CWM Recover (guessing there but that's what I'm going to look for at least).
That did it.....found the --no-reboot common argument for Heimdall and then manually rebooted directly to CWM Recovery. That allowed me to boot into CWM Recovery without the install.recover.sh shell running. Waiting for first reboot after flashing the CWM-Root.....rebooted installed SuperUser and disabled SuperSU but still can't rename or delete the /etc/Install.recover.sh (even though the root browser was given su permissions by SuperUser) ..... sigh
I know I'm rooted because I can reboot using Quick Boot after granting it su access - that's just strange.
Finally, figured it out...You can't modify or delete Install.recover.sh in /etc. You must do it at the following location /system/etc
Alan
Click to expand...
Click to collapse
Hey Alan, sorry... been away from the forums for a couple days. But it looks like you got it figured out you are correct on the Heimdall command, the only thing different that I did is that I already had root explorer purchased... so after the SuperUser install I just ran it to move the install_recover.sh to my SD card
Glad to hear you got it working!
I am trying to Flash the Stock ROM on my Galaxy Y PRO after it is gone into a bootloop (by itself), i am using ODIN , but it got stuck on Flashin the recovery img
i tried all The USB ports of my computer and only 1 worked. Please i need help and a sure answer thx
MultipleMonomials said:
If nothing else works you might be able to restore to stock... but I agree Heimdall is a better option.
Click to expand...
Click to collapse
How to use Heimdall when I have bl, ap, etc