Related
So I rooted using toastcfh's guide and everything works, including root (I was able to delete some of the bloatware ) but I am having one problem. Everytime I reboot into recovery, nothing comes up except for the background (the phone with the red triangle and exclamation point). To get the menu to show up, I have to run the recovery-windows.bat every time I want to use the menu.
Anyone know why it's not sticking and how to fix it? Thanks.
if you read toast's rooting instructions...
WHAT THIS ROOT METHOD SADLY WONT ENABLE YOU TO DO:
- Write to system or recovery while in android
- Flash a custom recovery that can be booted into by holding vol down and powering on
Click to expand...
Click to collapse
and, this should be in q and a
Thank you.
Gregalous said:
So I rooted using toastcfh's guide and everything works, including root (I was able to delete some of the bloatware ) but I am having one problem. Everytime I reboot into recovery, nothing comes up except for the background (the phone with the red triangle and exclamation point). To get the menu to show up, I have to run the recovery-windows.bat every time I want to use the menu.
Anyone know why it's not sticking and how to fix it? Thanks.
Click to expand...
Click to collapse
Code:
I was able to delete some of the bloatware
<----- what method did u use to do this i need to know cuz i wana do the same ..i tried root explorer like i always do but it didnt work
mccurt29 said:
Code:
I was able to delete some of the bloatware
<----- what method did u use to do this i need to know cuz i wana do the same ..i tried root explorer like i always do but it didnt work
Click to expand...
Click to collapse
Because you dont have rw permissions while in android.
While in recovery do this
adb remount
adb shell
cd /system/app
ls
This displays all apps.. Type this to remove them.
rm Sprint.apk
rm Sprint.odex
You must type exactly as the app appears and it is caps sensitive.
after i type adb remount i get (invalid)
will terminal work???
[/FONT I thought of myself as a well seasoned vet when it came to rooting. I have had a G1 and a Mytouch 3g. Since I now have the Mytouch 4g I would like to root it completely. I have run Visionary and can have SU privileges, then cant boot into recovery. I then tried using my computer to root. Still nothing.. Any help? Thanks you!
Olliej said:
[/FONT I thought of myself as a well seasoned vet when it came to rooting. I have had a G1 and a Mytouch 3g. Since I now have the Mytouch 4g I would like to root it completely. I have run Visionary and can have SU privileges, then cant boot into recovery. I then tried using my computer to root. Still nothing.. Any help? Thanks you!
Click to expand...
Click to collapse
Visionary is only part of the process. You need a couple more files and a working knowledge of abd and using terminal on your Mytouch 4G:
files:
wpx.ko
hboot_dhd.nb0
Visionary
A Terminal app (I use SUFBS)
Commands:
push the above two files to /data/local using ADB
adb push wpx.ko /data/local
adb push hboot_dhd.nb0 /data/local
run visionary and get temp root
Terminal:
Open up the terminal app and type in “su” to gain root access
Once the “#” appears, type in “insmod /data/local/wpx.ko” and hit Enter. You should get a “function not implemented error,” which is what you want.
This next terminal command will turn your device into a nice paperweight if you mess it up. If you do mess it up, don’t blame me, this all on you!
dd if=/data/local/hboot_dhd.nb0 of=/dev/block/mmcblk0p18 and hit Enter.
Close the terminal app, now open up visionary again. Run temp root again. You might get the “device already rooted” notification, this does not matter, what you are doing is locking in root.
Go back and open up your terminal emulator once more time and request root by typing “su”
Once you get the #, type “sync” wait about three minutes and reboot.
You should have permanent root with the security off (S-off), to check : With the phone off, hold down volume down and power to open Hboot. The top line of the screen should have “S-off” at the end.
I wanna try this step soooo bad but i'm scared ****less I brick my fone. Considering I only got it for just 2 days now.
I did the terminal process with terminal emulator 4 times & whenever I bash the root.sh file, the wpx.ko gives me trouble. Did it this morning @ 4am so I cant quite remember the exact statement it came back with
Paso876 said:
I wanna try this step soooo bad but i'm scared ****less I brick my fone. Considering I only got it for just 2 days now.
I did the terminal process with terminal emulator 4 times & whenever I bash the root.sh file, the wpx.ko gives me trouble. Did it this morning @ 4am so I cant quite remember the exact statement it came back with
Click to expand...
Click to collapse
try this method ive havent done it as im waiting for my, mytouch 4g to come but u should the comments are saying it worked for them
http://briefmobile.com/how-to-permaroot-and-unlock-your-mytouch-4g/comment-page-1#comment-48683
My wifes mt4g arrive today, and I had it rooted and s-off in about 20 minutes, following this method from the wiki:
http://forum.xda-developers.com/showthread.php?t=858996
Sent from my Nexus One using XDA App
Something went wrong....
alfadog77 said:
try this method ive havent done it as im waiting for my, mytouch 4g to come but u should the comments are saying it worked for them
Click to expand...
Click to collapse
I tried that method, but whenever I right click & open the command window & type 'adb push gfree /data/local'......I get "adb is not recognized as an internal or external command, operable program or batch file"
The unlocker's method worked great for me, even as a total noob, and was real easy.
http://theunlockr.com/category/howto/android_how_tos/htc-mytouch-4g-how-tos/
Paso876 said:
I tried that method, but whenever I right click & open the command window & type 'adb push gfree /data/local'......I get "adb is not recognized as an internal or external command, operable program or batch file"
Click to expand...
Click to collapse
That means that the adb binary isn't in the folder you are working from. Either the binary is missing, our you are in the wrong folder with you command prompt.
Sent from my Nexus One using XDA App
danger-rat said:
That means that the adb binary isn't in the folder you are working from. Either the binary is missing, our you are in the wrong folder with you command prompt.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Ok so lemme just recap what I did to see where I went wrong. I downloaded the SDK, installed the platform-tools folder, then hold shift same time as I click on the tools folder, select open command winder here & started to type in the prompt. So Now which file is the adb binary?? Maybe I can try & see if I somehow moved or removed it
alfadog77 said:
try this method ive havent done it as im waiting for my, mytouch 4g to come but u should the comments are saying it worked for them
http://briefmobile.com/how-to-permaroot-and-unlock-your-mytouch-4g/comment-page-1#comment-48683
Click to expand...
Click to collapse
Thats the same gfree method stickied in the dev section.
Paso876 said:
I tried that method, but whenever I right click & open the command window & type 'adb push gfree /data/local'......I get "adb is not recognized as an internal or external command, operable program or batch file"
Click to expand...
Click to collapse
You need to set up the android sdk first. follow the directions in this thread
Droid_duder said:
The unlocker's method worked great for me, even as a total noob, and was real easy.
Thats the first method I tried and it didnt work. I got that wpx.ho isn't recognized or something like that & 1024 in, 1024 out yada yada. I've noticed ppl say that its regular to get that back but I've dont it like 5 times & whenever i boot into hboot, I'm still seeing 'S-ON'
Click to expand...
Click to collapse
I got the wpx error, which is why I searched a bit more, and then used the method I posted earlier...
To help with the cmd prompt, down load this file, and place it in the same folder that the adb binary is in (it's a file, named adb). Double click this file, and it silk open a prompt in that folder...
http://db.tt/aVW40cy
Sent from my Nexus One using XDA App
Paso876 said:
I wanna try this step soooo bad but i'm scared ****less I brick my fone. Considering I only got it for just 2 days now.
I did the terminal process with terminal emulator 4 times & whenever I bash the root.sh file, the wpx.ko gives me trouble. Did it this morning @ 4am so I cant quite remember the exact statement it came back with
Click to expand...
Click to collapse
I had no trouble with my previously posted root, however I have read that some people had to place the files in the root of the SDCard (and change the commands accordingly of course) to get it to work.
option94 said:
Thats the same gfree method stickied in the dev section.
You need to set up the android sdk first. follow the directions in this thread
Click to expand...
Click to collapse
Thanks. I didn't know about this step until I realized last nite I had no clue what 'SDK' was...lol
alfadog77 said:
try this method ive havent done it as im waiting for my, mytouch 4g to come but u should the comments are saying it worked for them
http://briefmobile.com/how-to-permaroot-and-unlock-your-mytouch-4g/comment-page-1#comment-48683
Click to expand...
Click to collapse
Thanks, this finally worked for me. I had to setup SDK, ADB & then in some miraculously way I got through all the commands without any errors....lol
Thanks to those who chipped in, I'll go by and individually thank you guys.
I wonder what I'll do next?? lol
I used the Ultimate s=off method and rooted and unlocked in 10 minutes. Work like a charm
Olliej said:
[/FONT I thought of myself as a well seasoned vet when it came to rooting. I have had a G1 and a Mytouch 3g. Since I now have the Mytouch 4g I would like to root it completely. I have run Visionary and can have SU privileges, then cant boot into recovery. I then tried using my computer to root. Still nothing.. Any help? Thanks you!
Click to expand...
Click to collapse
There are 4 or 5 complete guides in the development section. Just read through them all and pick the one you're most comfortable with. With the scripts provided it makes it pretty safe.
I've rooted 4 phones with no issues.
ADB Shell connects just fine, but I cannot SU into it. I am rooted and have the latest SuperUser installed... In addition, I have USB debugging enabled, the LG drivers, and Root Explorer works perfectly.
RESOLVED:
You must have SuperUser OPEN while trying to SU from ADB. I don't remember this being needed on my Nexus One, but it's working now. I will keep this up for others that might need it....
Sceencast in droid explorer isnt working for me.rooted g2x. Maybe ill reinstall it after i get home from work. Is yours working?
Do you have SuperUser OPEN while trying to use it? Seems that it's not running persistently like it did on my N1
momentarylapseofreason said:
Do you have SuperUser OPEN while trying to use it? Seems that it's not running persistently like it did on my N1
Click to expand...
Click to collapse
just got home from work. gonna try it now.
nope, no screencast even with super user running. just rebooted. gonna try again. logcat seems to be going nuts though.
I was going crazy about this and asked Chris Soyars because I have never had to do this either. This is what he said:
"You can just type 'su' while in an adb shell, and it should drop you down to root. You won't get adb providing root until you have a boot image flashed that isn't running in secure mode.... -Chris Soyars"
wewoapsiak said:
I was going crazy about this and asked Chris Soyars because I have never had to do this either. This is what he said:
"You can just type 'su' while in an adb shell, and it should drop you down to root. You won't get adb providing root until you have a boot image flashed that isn't running in secure mode.... -Chris Soyars"
Click to expand...
Click to collapse
First you need to go to settings developer options and root access and check apps and ADB
Then you might have to do the CHMOD -R 777 /directorynameyouaretryingtoaccess
Guys. I am assuming the su in adb shell is preceded by an adb remount? By default system is ro not rw.
Sent from my LG-P999 using xda app-developers app
for some reason, i cannot gain permission through adb, i have tried everything. all i get is the $ sign. yes usb debugging is enabled, im running stock rom just updated with ota. i AM rooted, i have my drivers installed, idk why i cant get # via adb, someone help? any advice?
sk8dayfuknight said:
for some reason, i cannot gain permission through adb, i have tried everything. all i get is the $ sign. yes usb debugging is enabled, im running stock rom just updated with ota. i AM rooted, i have my drivers installed, idk why i cant get # via adb, someone help? any advice?
Click to expand...
Click to collapse
Follow the steps in this link: http://forum.xda-developers.com/showthread.php?t=1152148
He did an awesome job with this.
If you did follow this then you probably need to boot into recovery and change permissions settings.
when i type in su in adb i get # but when i type in adb shell i still get $, it says adb: Not found
sk8dayfuknight said:
for some reason, i cannot gain permission through adb, i have tried everything. all i get is the $ sign. yes usb debugging is enabled, im running stock rom just updated with ota. i AM rooted, i have my drivers installed, idk why i cant get # via adb, someone help? any advice?
Click to expand...
Click to collapse
i have the same issue after OTA update. root only with terminal emulator on the device. try'd to fix permission in recovery, no changes. adb shell gives me no #, only $, allways permission denied by trying su.
Edit:
it looks like that only adb can't switch the user. su_2.3.6.3_efgh is sccessfully installed via CWM 4.0.1.4 without any errors. all root apps (e.g. Titanium Backup Pro, Root Explorer, Superuser, Terminal Emulator) are working perfect. root check from market told me that adb binary is set to default shell user access as a standard non-root user. any idears?
holly1963 said:
i have the same issue after OTA update. root only with terminal emulator on the device. try'd to fix permission in recovery, no changes. adb shell gives me no #, only $, allways permission denied by trying su.
Edit:
it looks like that only adb can't switch the user. su_2.3.6.3_efgh is sccessfully installed via CWM 4.0.1.4 without any errors. all root apps (e.g. Titanium Backup Pro, Root Explorer, Superuser, Terminal Emulator) are working perfect. root check from market told me that adb binary is set to default shell user access as a standard non-root user. any idears?
Click to expand...
Click to collapse
i found i only have trouble with stock rom, i flashed leedroid rom last night and was able to get "#" with "adb shell" on the first try...
sk8dayfuknight said:
i found i only have trouble with stock rom, i flashed leedroid rom last night and was able to get "#" with "adb shell" on the first try...
Click to expand...
Click to collapse
for now i don't want to flash a custom rom, i'am using the VF stock ROM. So I still have the same issue
holly1963 said:
for now i don't want to flash a custom rom, i'am using the VF stock ROM. So I still have the same issue
Click to expand...
Click to collapse
You need to have Busybox installed.
Sent from my HTC Sensation 4G using Tapatalk
Rhiannon224 said:
You need to have Busybox installed.
Sent from my HTC Sensation 4G using Tapatalk
Click to expand...
Click to collapse
thanks for your help, busybox is successfully installed but i still can't change the user with adb
inside the trouble guide thread from the development they advice to flash a custom rom, but this is not my target.
seems the only way to get "#" from adb shell is with a custom rom. for me at least. i tried everything, changing the permissions of su, fixing permissions in recovery, and installing busybox,
When you type su are you going back to your phone and allowing super user for the unknown device? - I know that is a basic answer.
zylith said:
When you type su are you going back to your phone and allowing super user for the unknown device? - I know that is a basic answer.
Click to expand...
Click to collapse
i have thought about that method, but in the superuser.apk nothing comes up when trying to get a shell to my phone thorugh adb...
sk8dayfuknight said:
i have thought about that method, but in the superuser.apk nothing comes up when trying to get a shell to my phone thorugh adb...
Click to expand...
Click to collapse
When you're in CMD and type adb shell or su, if its the first time you should see a request to allow or deny su permission on the phone, right? Does that happen when you attempt?
Sent from my HTC Sensation Z710e
BlackElvis79 said:
When you're in CMD and type adb shell or su, if its the first time you should see a request to allow or deny su permission on the phone, right? Does that happen when you attempt?
Click to expand...
Click to collapse
there is no request on the phone, nothing happens (screen was on)
Open super user- and see if you already hit deny- You can also change it from there. Also when you type "adb devices" does your phone show up with serial number?
sk8dayfuknight said:
for some reason, i cannot gain permission through adb, i have tried everything. all i get is the $ sign. yes usb debugging is enabled, im running stock rom just updated with ota. i AM rooted, i have my drivers installed, idk why i cant get # via adb, someone help? any advice?
Click to expand...
Click to collapse
Try rooting again. Reinstall superuser.,also download busybox installer from the market and instal
Sent from my HTC Sensation Z710e using XDA App
It is not working with the stock ROM no point redoing every thing it wont work no matter how many times you try.
I doubt we will get much help it is not a problem with a custom ROM so there wont be that many peeps who will be looking into it.
Best bet it to stick a custom stock based ROM with a stock kernel.
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