Database Info

[Q] My half assed root.

[/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.

For Those Who Can't Root Try This!

I tried everything from this website and nothing was working... Idk why but it was very frustrating... I came along this video and I did it on my first try. I thought I should share this tut
http://www.youtube.com/watch?v=RyELJRy4rhE

Go down to TheUnlockr they have video walkthough step by step to obtain tempROOT (Visionary) and then permROOT (root.sh) just follow it as its more easier than the video you posted.
Sent from my HTC Glacier

The video he posted is easier.
Sent from my HTC Glacier using XDA App

TJBunch1228 said:
The video he posted is easier.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Really?
1a) download and install VISIONary.
1b) download and install Terminal Emulator
2) download and unzip the root folder
3) store the root folder on the SDCard
4) Temp Root / making sure set system to R/W and run Visionary.sh are checked
5) go to terminal emulator and type
$ su
# cd /sdcard/root
# sh root.sh
Click to expand...
Click to collapse
Seems pretty easy to me.

neidlinger said:
Really?
Click to expand...
Click to collapse
No, that black shelf guy has just been a debbie downer on everyone's posts lately, and I was drinking and feeling obstinate. I had my 4G rooted within like 45 min of ownership using the same method you posted.
Sent from my HTC Glacier using XDA App

TJBunch1228 said:
No, that black shelf guy has just been a debbie downer on everyone's posts lately, and I was drinking and feeling obstinate. I had my 4G rooted within like 45 min of ownership using the same method you posted.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
I had mine Rooted before i left the T-Mobile Store. True Story. I didn't have the Engineering Screen flashed but i did have it s=off prior to walking out of the door.

I had to use a different method that involved pushing files threw adb.. since the method that was all about temp enabling root and using the terminal emulator was useless

neidlinger said:
I had mine Rooted before i left the T-Mobile Store. True Story. I didn't have the Engineering Screen flashed but i did have it s=off prior to walking out of the door.
Click to expand...
Click to collapse
Yeah not quite THAT brave/crazy. Even though it can be done quickly and without a computer, I'd rather go slow and make sure it's done right. I'd get bit in the ass, I know it.
Sent from my HTC Glacier using XDA App

lol now thats comedy and here I am the bad guy? as I posted before here and other forums read below.
HKM said:
If you don't want to do it manually then you can do it easily via FileExp go use Astro or Root Explorer. From what you are saying I have my money on you didn't properly do TempROOT. I say go do TempROOT again then try what I suggested for PermROOT.
UPDATE: Here I found you Youtube videos how to do step by step.
tempROOT> http://www.youtube.com/watch?v=gylaXOCNzqU
permROOT> http://www.youtube.com/watch?v=Sy_aqKoeev4
Use the howto from Theunlockr video posted above it maybe easier for you to follow.
Well since you are up to the PermROOT I take it you have TempROOT, if so as you saying you have root.sh in root dir inside /sdcard so it would look like /sdcard/root/root.sh for the absolute path. Also you have console right? If not go download Terminal Emulator. Then type in "su" and press enter SU=Super User or @wheel,root permission base. Then use "cd /sdcard/root" press enter CD = Change Directory. Then do "sh root.sh" and press enter as sh is shall execute command. So it would look like this below:
su
cd /sdcard/root
sh root.sh
Now just do restart and make sure you have S=OFF as you will see it on top in HBoot screen. When you are back on go open Visionary+ and unclick TempROOT on boot and click TempROOT now. Then look below and click on Attempt PermROOT Now.
Click to expand...
Click to collapse

TJBunch1228 said:
Yeah not quite THAT brave/crazy. Even though it can be done quickly and without a computer, I'd rather go slow and make sure it's done right. I'd get bit in the ass, I know it.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
lol.
I wanted to do it in the store so that way if something went AWOL i could hand the phone back over and say "hey something is jacked with this phone, you need to get me a different one".
I just stored VISIONary on my SD card in the .apk format, and the folder on my SD card and swapped it. As he was punching everything in i installed astro, then Visionary, and terminal emulator and turned s=off. Once it was good i walked out....

I tried that video from the Unlockr and it didnt work for me

Kush Smoke said:
I tried that video from the Unlockr and it didnt work for me
Click to expand...
Click to collapse
1) are you extracting and storing just the root folder to the SD card
and
2a) are you putting a space between the "d" and the "/".
2b) are you putting a space between the "h" and the "r".
it should look like this
$ su
# cd /root/sdcard
# sh root.sh
Click to expand...
Click to collapse
if you just type cd/sdcard/root or shroot.sh it will not work.
======
edit
you also have "change /system to r/w" for it to work properly.

As neidlinger stated you have to correctly type it in. But I came across people who does not understand root which is your direct absolute path in this case "/sdcard" now if you got confused with root folder and created new dir then its "/sdcard/root" which makes no diff as you can do it still.
HKM said:
su
mkdir /sdcard/root
mv /sdcard/root.sh /sdcard/root/
cd /sdcard/root
sh root.sh
Click to expand...
Click to collapse
^ this is not even needed but if you created /root folder inside /sdcard then you have to use it. Normally it makes no diff as you can use CD command to switch between it but people who don't understand console find it confusing.

NEW 2.3.4 MT4G Downgrade Instructions...

I had the issue of downgrading the NEW out of box 2.3.4.... I was given this link by neidlinger. I had to edit the ending of it to get it to work but it worked, and is working great. Here is the link, and below it is my edit of them.
P.S. MAKE SURE YOU USE THE LINKS TO DOWNLOAD THE PROGRAMS YOU NEED....IF YOU ALREADY HAVE THEM DOWNLOAD THESE AND REPLACE THEM.(JUST TO BE ON THE SAFE SIDE) It wouldn't work for me until I re-downloaded and replaced them.
http://wiki.cyanogenmod.com/wiki/HTC_Glacier:_Full_Update_Guide
Downgrading to 1.17.531.2
If the HTC Glacier is running a Gingerbread firmware (2.xx.xxx.x) (Settings » About Phone) you need to downgrade the device first in order to root. If the HTC Glacier is already running 1.17.531.2 or lower you can skip to the Rooting the HTC Glacier section.
1. You will need ADB on the computer to proceed thru this process. Follow the Android SDK guide, to get the ADB shell on the computer.
2. Download fre3vo, misc_version 0.2 & the 1.17.531.2 firmware:
o fre3vo: Download
md5: 010e076a4a93be876579711bf8934c70
o misc_version 0.2: Download
md5: 1f40aaf88d1bf15775631a58c4361218
o 1.17.531.2 firmware: Download
md5: 49d07f0ee7de1765a6a84cb12fa53110
3. Unzip the fre3vo & misc_version packages to the same folder as adb (the /platform-tools folder within the Android SDK folder).
4. Make sure the filename of the firmware is PD15IMG.zip exactly or it will not work and copy it to the same folder as adb.
5. Connect the HTC Glacier to the computer via USB.
6. On the computer, open terminal and run the following commands:
adb push fre3vo /data/local/tmp
adb push misc_version /data/local/tmp
adb shell
chmod 777 /data/local/tmp/fre3vo
chmod 777 /data/local/tmp/misc_version
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
adb shell
NOTE: You should have the "#" sign instead of the "$". If you do, you have temporary root, and can continue on. If you have the "$", then the exploit has failed, refer to xda developers, RootzWiki, or #G2Root for further assistance.
/data/local/tmp/misc_version -s 1.00.000.0
exit
7. Now that misc version has been downgraded, the HTC Glacier is ready to have the firmware downgraded. On the computer, open terminal and run the following commands:
adb reboot bootloader
8. Use Volume up/down keys on the HTC Glacier for navigation and Power key for confirmation. Select Bootloader to flash the 1.17.531.2 firmware.
( IT MAY AUTOMATICALLY START )
Once finished you can Root the device by following the instructions on this link…..
http://forum.xda-developers.com/showthread.php?t=858996

its gotta be an easier way to downgrade.

It's actually very simple... I did it after 2 showers of the "herbal" essence kind. Ha...!
Sent from my HTC Glacier using XDA App

BillyBoy74 said:
It's actually very simple... I did it after 2 showers of the "herbal" essence kind. Ha...!
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
i am kinda surprised with all the people on this site that no one has made a one click downgrade yet.

??????
Can anybody help me please?
i followed these steps and i still havent downgraded

bam5bam57 said:
Can anybody help me please?
adb cant read my mytouch 4g device.
Click to expand...
Click to collapse
You installed the usb driver and rebooted your computer?
Sent from my myTouch 4G using xda app-developers app

modbass said:
i am kinda surprised with all the people on this site that no one has made a one click downgrade yet.
Click to expand...
Click to collapse
Why dont you make one then?
Sent from my GT-N7000

thecool14soh said:
its gotta be an easier way to downgrade.
Click to expand...
Click to collapse
Actually used instructions from THeUnlockr.com - very easy to follow and worked like a charm.
http://theunlockr.com/2011/10/25/ho...ire-z-desire-hd-and-mytouch-4g-back-to-froyo/
CAUTION: there's a link to the Froyo ROM that seems to be defective - get the ROM from here:
http://forum.xda-developers.com/showthread.php?t=1476745&highlight=pd15img&page=1

Bass_Man25 said:
Actually used instructions from THeUnlockr.com - very easy to follow and worked like a charm.
http://theunlockr.com/2011/10/25/ho...ire-z-desire-hd-and-mytouch-4g-back-to-froyo/
CAUTION: there's a link to the Froyo ROM that seems to be defective - get the ROM from here:
http://forum.xda-developers.com/showthread.php?t=1476745&highlight=pd15img&page=1
Click to expand...
Click to collapse
I tried following theunockr directions but it didn't work. I wound up having to turn my SD card into a goldcard for it to finally downgrade (what a stupid idea going for the unlocked bootloader was)

This is the RIGHT one.

skygear said:
This is the RIGHT one.
Click to expand...
Click to collapse
This is the Right WHAT?

K-JACKS said:
This is the Right WHAT?
Click to expand...
Click to collapse
Shhh. Pretend it's not there and slowly walk away.

Jerk. This is the right set to downgrade.
Can't believe you were thanked for your stupid response.

Lol... Yes it works like a charm...
Estalling lol looking good so far for that RC title.
Sent from my HTC One S using Tapatalk 2

...Awesome... said:
Lol... Yes it works like a charm...
Estalling lol looking good so far for that RC title.
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
Hahaha :thumbup:

Thank You!
Thank you, I have an HTC Glacier MyTouch 4g and I can not root, unlock the bootloader, or downgrade! I just went through the Android Bullet but failed after about 5 tries.
modbass said:
i am kinda surprised with all the people on this site that no one has made a one click downgrade yet.
Click to expand...
Click to collapse

NOOB needs help
Can someone please help me.... trying to down grade and ready to give up. This is my second day on this and just got past (adb shell cat /dev/msm_rotator). Anyone have a new way to downgrade?

I always use the instructions on theunlockr.com actually just did it last week to a vision which is the same process. Make sure u follow directions exactly and don't skip through.
As long as u have adb set up correctly then all is good.
Sent from my HTC myTouch 4g using xda app-developers app

This Device Does Not Support This Exploit
I've tried a few different guides for temp root, but they all rely on fre3v0. The issue I am having is that after running the /data/local/tmp/fre3vo command, or its alternate configurations, the device returns:
Code:
Locating access point...
This device does not support this exploit.
This device does not support this exploit.
The expoit has failed.
Does anyone know what causes this issue? Or does anyone have an alternative way for gaining temporary root? I spent the evening looking around but haven't found any strong leads.
Device info: Android 2.3.4, HTC Sense version 2.1, Software number 2.32.531.1, Kernel 2.6.35.10-g4dcb781

PopeOnABomb said:
I've tried a few different guides for temp root, but they all rely on fre3v0. The issue I am having is that after running the /data/local/tmp/fre3vo command, or its alternate configurations, the device returns:
Code:
Locating access point...
This device does not support this exploit.
This device does not support this exploit.
The expoit has failed.
Does anyone know what causes this issue? Or does anyone have an alternative way for gaining temporary root? I spent the evening looking around but haven't found any strong leads.
Device info: Android 2.3.4, HTC Sense version 2.1, Software number 2.32.531.1, Kernel 2.6.35.10-g4dcb781
Click to expand...
Click to collapse
the method works trust me print full device info from hboot. just follow the guid on the unlockr.com and if u cant get s-off after they say u should follow the post in the comment or better yet a ton load of proven tuts on this site

[HOW TO] Update to 2.3.6 OTA Preserving Root Access! Working!! And Tested!

Hello guys! the instructions are very easy if you do the steps correctly.
This is my first post in the development section.
First, go to market and download OTA Rootkeeper
Second, open the app, Select Create SU Backup.
Third, Select Temp UnRoot(with backup)
Fourth, uninstall Superuser, if you have superuser elite uninstall it also! and uninstall OTA Rootkeeper(dont worry it will not delete UR Backup!)
Fifth, Download and install the OTA.
After it is done and reboot, do a power cycle.
and the last step, go to market, install superuser and ota rootkeeper.
Launch OTA Rootkeeper and Select RestoreRoot, accept the superuser permission, and reboot!
AND ur back with rooted 2.3.6!
Michael
Alternate method! This is Jim's method(Thanks jim for this other way)
To do the 4ever root hack do the following:
1) open root explorer or ew file manager etc...
go to /system/bin
find the file named mount_ext3.sh
touch and hold the file name until the menu appears, go to open in text editor.
Add the following line to the VERY bottom of the file, after the fi
chmod 4755 /system/bin/su
chmod 4755 /system/xbin/su
chmod 644 /system/app/Superuser.apk
2) SAVE!!!! the file.
3) Do the OTA update.
4) You should still have root after the update, now.
Jim
Enjoy, Hope this helps!

I missed step 3 and 4 this is why it did not work for me

Does this work if coming from SuperCharged V4, or only if coming from stock 2.3.5?
Thanks

Zoide_ said:
Does this work if coming from SuperCharged V4, or only if coming from stock 2.3.5?
Thanks
Click to expand...
Click to collapse
I don't know but as soon as I get home I'm going to check and see... Just got another A2 today, its going to be a good lil Guinea Pig... (insert evil grin here)
Sent from my MB865 using XDA App

The easier way to do this, is just do the 4ever root that was done for the bionic.
Just add these lines to the bottom of the /system/bin/mount_ext3.sh files with the text editor in root explorer, or through adb.
chmod 4755 /system/bin/su
chmod 644 /system/app/Superuser.apk
Do that BEFORE the OTA update, and you will not have any issues with OTAs ever again and loosing root. but if you did not do the update maually, and you used the one-click you might need to add the following line as well....
chmod 4755 /system/xbin/su
Jim

Zoide_ said:
Does this work if coming from SuperCharged V4, or only if coming from stock 2.3.5?
Thanks
Click to expand...
Click to collapse
cant tell you, i didnt had a custom rom on it while i tried but if i am correct the update will work with stock only. wait till Iggis Pop do the test before attempting.

I just used OTA Rootkeeper normally and it worked fine for me. Backed up root, temp un-rooted, downloaded and applied the update, then restored root from OTA Rootkeeper after the update finished. I have root back just fine...
Did this not work for others?

I must of did something wrong because this did not work for me. I followed the steps to a T and it didn't take.
Sent from my MB865 using xda premium

jimbridgman said:
The easier way to do this, is just do the 4ever root that was done for the bionic.
Just add these lines to the bottom of the /system/bin/mount_ext3.sh files with the text editor in root explorer, or through adb.
chmod 4755 /system/bin/su
chmod 444 /system/app/Superuser.apk
Do that BEFORE the OTA update, and you will not have any issues with OTAs ever again and loosing root.
Jim
Click to expand...
Click to collapse
be carefull, the update brings a new security environment and new security patches that google just released. the update over writes parts of the system data. the safest way that i tested is this method. be careful with ever root

jimbridgman said:
The easier way to do this, is just do the 4ever root that was done for the bionic.
Just add these lines to the bottom of the /system/bin/mount_ext3.sh files with the text editor in root explorer, or through adb.
chmod 4755 /system/bin/su
chmod 444 /system/app/Superuser.apk
Do that BEFORE the OTA update, and you will not have any issues with OTAs ever again and loosing root.
Jim
Click to expand...
Click to collapse
Jim,
I have a question about running a Deodexed rom. Will I have a problem upgrading or do I have to SBF back to stock? I also have the 1 percent mod that I love. How can I keep this. My understanding is this only works for deodexed roms.

tmease1 said:
I must of did something wrong because this did not work for me. I followed the steps to a T and it didn't take.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
can you tell me step by step what ou did so i can help you!

jimbridgman said:
The easier way to do this, is just do the 4ever root that was done for the bionic.
Just add these lines to the bottom of the /system/bin/mount_ext3.sh files with the text editor in root explorer, or through adb.
chmod 4755 /system/bin/su
chmod 444 /system/app/Superuser.apk
Do that BEFORE the OTA update, and you will not have any issues with OTAs ever again and loosing root.
Jim
Click to expand...
Click to collapse
x2 I used this method and it works fine. No messing around with OTA rootkepper, no need to uninstall superuser/etc.
Michael443 said:
be carefull, the update brings a new security environment and new security patches that google just released. the update over writes parts of the system data. the safest way that i tested is this method. be careful with ever root
Click to expand...
Click to collapse
ever root is arguably SAFER than your method. All it does is make the system change the permission on the files on every bootup. It's not rocket science.

09CarreraS said:
Jim,
I have a question about running a Deodexed rom. Will I have a problem upgrading or do I have to SBF back to stock? I also have the 1 percent mod that I love. How can I keep this. My understanding is this only works for deodexed roms.
Click to expand...
Click to collapse
I'm not Jim but I do have the answers to your questions!
You should flash the fkz's (sbf) files before you update, just a good idea to remove any oddities or potential problems. Also most modifications do relay on a deodexed ROM , so my guess is that it won't work with the new update yet. My personal recommendation would be to wait until lfaber06 incorperates this update into a nice little cwm flashable zip (around this weekend, or next), that will already contain root, as well as the 1 percent mod and the updated theming!

Thanks for the answer! Hey I'm from Ma as well.

well that's what i get for not reading here first. My coworker was demo-ing an app to our CEO and the update notification came in. A few minutes later he comes back and says he hit download then install when it came up. When i got it it was flashing in recovery already

extide said:
x2 I used this method and it works fine. No messing around with OTA rootkepper, no need to uninstall superuser/etc.
ever root is arguably SAFER than your method. All it does is make the system change the permission on the files on every bootup. It's not rocket science.
Click to expand...
Click to collapse
Well, this definitely bricked my phone.

toastthemost said:
Well, this definitely bricked my phone.
Click to expand...
Click to collapse
Are you sure you followed the instructions and put the files in the right directory? I havn't had any problems using this exact method as for a few others.

No way if it was done correctly that it bricked your phone.correctly can be accomplished by navigating to the proper file then copy pasting the code in order.the only thing you are modifying is superuser.

toastthemost said:
Well, this definitely bricked my phone.
Click to expand...
Click to collapse
You probably edited the ext3 mount script incorrectly then, that could easily softbrick the phone.

extide said:
You probably edited the ext3 mount script incorrectly then, that could easily softbrick the phone.
Click to expand...
Click to collapse
Not sure, I just pasted those two lines under "fi" or whatever was on the last line. Checked it. Saved it. Rebooted. Boot loop.

Can Someone Verify or Point Me In The Right Direction

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