[Q] link_image[1995]: failed to link su CANNOT LINK EXECUTABLE - myTouch 4G Q&A, Help & Troubleshooting

Long story short is that yesterday I rooted my HTC Glacier and everything seemed to work fine. I was able to obtain admin privileges by opening a Android terminal and typing "su". Today after deleting a few files from my phone which I thought were junk (face palm) I go into terminal to check if the "su" command still works and I get the message "link_image[1995]: failed to link su CANNOT LINK EXECUTABLE".
I've checked and my s=off is still in place so it's not that that's causing the error message. I'm new to Android so I'm stumped as to what steps to take next in order to regain my admin privileges.
Thanks for any and all advice XDA Community.
Cheers!

Lazerfingers said:
Long story short is that yesterday I rooted my HTC Glacier and everything seemed to work fine. I was able to obtain admin privileges by opening a Android terminal and typing "su". Today after deleting a few files from my phone which I thought were junk (face palm) I go into terminal to check if the "su" command still works and I get the message "link_image[1995]: failed to link su CANNOT LINK EXECUTABLE".
I've checked and my s=off is still in place so it's not that that's causing the error message. I'm new to Android so I'm stumped as to what steps to take next in order to regain my admin privileges.
Thanks for any and all advice XDA Community.
Cheers!
Click to expand...
Click to collapse
Try re-running visionary. It won't hurt anything and it installs su, busybox, and superuser.apk when you run it. It won't mess up anything you already have installed and it might fix your problem.
Also, I'm sure Whosdaman will tell you and move the thread when he sees this but make sure you post questions in the Q&A section.

Ran Visionary and no dice. Thanks for the tip though and sorry for posting in the wrong forum.
Any other ideas?

Try going into xbin (cd /system/xbin) and typing ls and see if su is in there. If it is you could try running rom manager and "fix permissions" if it will let you.

Good deal. I'm actually out fixing someone else's desktop computer at the moment. I'll attempt your advice later tonight.
Thanks again.
Sent from my HTC Glacier using XDA App

Ok, had a free moment and was able to run ls, su was there but unfortunately I wasn't allowed the super user access needed to fix permissions.
Sent from my HTC Glacier using XDA App

Please post questions in Q&A section.

1. Go into settings-applications-manage applications and try clearing superusers cache/data. See where that takes you.
2. If that did not work - isntall a fresh copy of superuser app from the market and once more see where that takes you.

Sorry about that. All future posts of these sorts I'll be sure to put there.
Sent from my HTC Glacier using XDA App

Tried both of your tips but unfortunately am still getting the same error when I run the "su" command.
Any other thoughts?
Sent from my HTC Glacier using XDA App

Update: Superuser automatically downloaded a new binary and told me to unzip it in recover mode.
I went into recover move and attempted to unzip the binary and was greeted with an error message that said the file couldn't be unzipped because it was "bad".
Sent from my HTC Glacier using XDA App

Can you get su in adb?
The more I think about it, You're s-off so you can fastboot new recovery image and then flash new rom with all the goodies preinstalled. May be the easiest route.

To be honest I've had my pocket computer for all of a week, so I'v still not had a chance to play around with adb.
The whole reason I rooted in the first place was so that I could flash custom roms. You think I'll be able to flash even though "su" privileges don't seem to be working properly in my current rom?
Sent from my HTC Glacier using XDA App
Update: It's clear from reading around these forums that the way to get to know your phone and thus be able to fix it is via adb. So I'm installing the Android SDK now. Thanks for all of your help Borodin1 and Grankin01

Related

[Q] I cant get permroot can someone please help ???

Ok people I'm pathetic.... I rooted using visionary installed titanium backup pro, astro, terminal emulator. I downloaded the root.rar files and put them onto the sd card. Unhooked my phone opened terminal typed su+enter but when I tried the sec command it wouldn't work I then went back into astro and h_boot and wpx are white in color and when I press on one of them it says file type ko not found. Can someone please please help me!!!! Do I have to have adb installed in order for the root.rar files to be found . Thank u very m much in advance. And if this is not the correct place to post this at let me know and I will move it thank u
Check out mackesters channel on YouTube he's got a good tutorial
Hey, you probably done all this... But thought I'd give a crack at it...
When trying to root using visionary
Quickly check these:
-did you have fastboot from >settings>applications turned off?
-was Set system r/w after root from visionary app checked?
-Temproot first
-Attempt permroot next
-Phone should reboot and you should see Super User app in the drawer.
Then follow the instructions here
If you wish to use root explorer to push the gfree file to /data/local you can do so too, its easier than adb commands.
Hope this helps. Good luck man.
Please post questions in the Q&A section.
Use root file explorer not Astro, check my signature. Also you said you downloaded the root.rar and placed it on sd, did you unzip it first?
Fastboot was off rw on. I don't know if I unzipped root.rar or not all I did was download it right click on it extracted to F drive moved to sd and in terminal is said not found our something when I entered the sec command.i did a factory reset so I'm starting fresh. What did I do wrong ? Thank u awesome people in advance
You sure you put the right file? Coz there are two gfree files...
Jmayes1786 said:
Fastboot was off rw on. I don't know if I unzipped root.rar or not all I did was download it right click on it extracted to F drive moved to sd and in terminal is said not found our something when I entered the sec command.i did a factory reset so I'm starting fresh. What did I do wrong ? Thank u awesome people in advance
Click to expand...
Click to collapse
rjhay22 said:
You sure you put the right file? Coz there are two gfree files...
Click to expand...
Click to collapse
This depends on the thread your following, he is referring to ULTIMATE S OFF
And extract is the same thing as unzip.
Sent from my HTC Glacier using XDA App
I guess I used the right one but it says ko file not found or sh file not found etc so I don't know what I'm doing wrong its driving me insane it shouldn't be this hard. Thanks for everyone help I'm still trying and will not give up lol
Are you doing this in the phone or thru a pc via adb? If adb also copy the files from root.rar to sdk/tools then adb will see them
Jmayes1786 said:
I guess I used the right one but it says ko file not found or sh file not found etc so I don't know what I'm doing wrong its driving me insane it shouldn't be this hard. Thanks for everyone help I'm still trying and will not give up lol
Click to expand...
Click to collapse
Sent from my HTC Glacier using XDA App
http://forum.xda-developers.com/showthread.php?t=834225
Try the alternative root process listed midway through OP I think you will have success, let me know if not then I know where your at.
I have had the best luck with this one
Sent from my HTC Glacier using XDA App

Rooting issue.. Cant get s off

Idk if its because im using android terminal emulator and not the regular one"wouldnt open kept force closing" but when I root using visionary 11 and atu, when I input last code "sh root.sh" it roots my phone but everytime I power down to check if the s is off it is still on.. Ive master reset and everything. Since I got the phone two days ago should I return for a new one and try to root that one??? Is there something im doing wrong.. Usb debugging on, fast boot off, on visionary last option checked.. Somebody...anybody.. Please help
Sent from my HTC Glacier using XDA App
Does usb debugging have to be on with that method?
Sent from my HTC Glacier using XDA App
yes turn debugging on and turn off fast boot
jstew6260 said:
Idk if its because im using android terminal emulator and not the regular one"wouldnt open kept force closing" but when I root using visionary 11 and atu, when I input last code "sh root.sh" it roots my phone but everytime I power down to check if the s is off it is still on.. Ive master reset and everything. Since I got the phone two days ago should I return for a new one and try to root that one??? Is there something im doing wrong.. Usb debugging on, fast boot off, on visionary last option checked.. Somebody...anybody.. Please help
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Are you 100% sure that you have it extracted and set up as sdcard/root/root.sh
I've seen a lot of people not pull the folder out and it it'll be set up such as sdcard/root/root/root.sh
Yea ive extracted root from androzip.. Im sure because the first time I did it but didnt extract the root file the root didnt go through from term emulator.. Error message like cant find root file
Sent from my HTC Glacier using XDA App
I'm having this exact problem with my t-mobile replacement I just got.and its not me because I re rooted my bad phone with the same files and method and works fine... I'm very worried that htc or google may have locked us out... Please help guys I need to send my old phone I'm on now back and want to sort this out first... Mine haas dust under the screen.... In h-boot the info is identical to my old phone only difference is the part number on the phone. I'm very worried!
Also my replacement came with 2.2.1 from the box if that helps.I have pulled the battery and retried several times and no luck at all. Root.sh goes through like but when I reboot I always have so-on. I've done this several times on my old phone with no issues.
Soo I just got a new 4g.. since its within my 30 days.. and Ima use the same method... hopefully it works... ill keep y'all posted
Sent from my T-Mobile G1 using XDA App
2rz_taco_sr5 said:
Also my replacement came with 2.2.1 from the box if that helps.I have pulled the battery and retried several times and no luck at all. Root.sh goes through like but when I reboot I always have so-on. I've done this several times on my old phone with no issues.
Click to expand...
Click to collapse
I'm having the same issue with my replacement phone. The process goes through smoothly until I restart and find out that I'm still not rooted.
We might need a new root method... I hope not
Same issue here, gents. Tried a bunch and still showing s=on. Bum.
I pmed the mod to se ifeel we can post something up in the dev section to get this better noticed. Hope he agrees!
Dud you run visionary the second time?
Sent from my HTC Glacier using XDA App
Hey man. Thanks for the tip. Ran multiple times and its still showing as s=on. Tried multiple methods with same results.
Sent from my HTC Glacier using XDA App
dodgepot said:
Hey man. Thanks for the tip. Ran multiple times and its still showing as s=on. Tried multiple methods with same results.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Did any of you have usb debugging check?
i promise its not a user error. i can root and unroot one phone and my new one WILL NOT root. i had already unrooted my phone to be returned and rooted it back in less than a min. but my new one will not root no matter what i try...
i feel dumb for taking so long to look at this method but this worked like a charm for me guys.
http://forum.xda-developers.com/showthread.php?t=858996
if you just want s-off do these steps (from the link only simplified for s-off only which is all i cared about)
this uses adb so if you want you can try the method explained right after step 4 that uses only the phone.
Make sure you have visionary installed on your device. (If you were already permarooted w/s=off ignore this step.)
Download this file:
http://www.mediafire.com/?s7afymwe2wb3x60
md5sum: b73c56ca0e21664c5756d4ad295063c5
1. Now unzip the file into your SDK tools directory. (just put the files that are in the zip right into the tools folder that is in your sdk folder)
2. Plug your device into your computer. (have debugging on!)
3. Now go to your sdk folder and while holding shift down right click on the tools folder. Select open command window here. If you are in linux (ubuntu) right mouse click on your SDK tools folder, choose actions, and choose open command window(or whatever it's called). Otherwise, open a command prompt and cd your way to your SDK tools directory.
4. Type "adb push gfree /data/local" and hit enter.
Optionally, for those without sdk knowledge you could dl the file to your phone use androzip or something like it to unzip the file and then use root explorer to move the file named gfree to /data/local. Not the gfree.h file. All the other files are source code inlcuded for the gnu license. This would skip the first 4 steps.
5. Now unplug your device from the computer.
6. Run visionary to gain temp root.
7. Open terminal emulator on your device, type "su", and hit enter to gain root privileges.
8. Type "cd /data/local" and hit enter.
9. Now type "chmod 777 gfree" and hit enter to make the program executable.
10. Type "./gfree -f" and hit enter.
11. now to turn security off and set super CID the command is "./gfree --secu_flag off --cid 11111111" + enter.
reboot and s should be off again all credit to the link above this is just a simplified version for people like us who just want s-off. this is what i did and worked great. look at the thread for a list of things you can do with gfree like simlock off etc.
big nu said:
Did any of you have usb debugging check?
Click to expand...
Click to collapse
Yeah, I had that option selecteed.
Edit: trying that way now, 2rz
any luck? i tried to simplify it as much as possible for those of you just starting out...
Just one question, the section about downloading the file directly to the device, it says copy to /data/local, the local directory doesnt exist. Do I create that dir? I may have to sdk from my windows machine. Sorry for tbe trouble.
2rz_taco_sr5 said:
any luck? i tried to simplify it as much as possible for those of you just starting out...
Click to expand...
Click to collapse
Sent from my HTC Glacier using XDA App

Help Needed... Think I Bricked my Nexus S

Greetings,
Okay, so I endeavoured to root my phone last night and was successful. I ran into trouble when the clockwork recovery and superuser permissions kept getting removed each time I rebooted the phone. This morning, I tried to restore the superuser permissions by following the steps I found here on xda but after running the terminal script I rebooted my phone and when my phone wouldn't boot beyond the Google screen.
Now, I'm at the Google splash screen with no way to move forward. I'm a mac user and I don't really get the adb thing. Got adb to work with mac from a youtube video, but still not sure what commands to run.
I can't access clockwork recovery from the bootloader.
What I've done so far:
- wiped cache
- wiped/factory data reset
- retraced my steps by using terminal to setup superuser permission from this post (http://forum.xda-developers.com/showthread.php?t=927838)
What I think:
- maybe in all of my clicks I removed the ROM, so the phone doesn't have a ROM to work with.
This maybe a really infantile conclusion, but I know there's a solution (had a rooted G1 that I flashed all the time and thought I bricked once but was able to get it back to stock).
Eagerly waiting for a reply... no cell phone if this can't be fixed.
Tamaratee
__________________
Phone: Nexus
Rooted with problems
This post might help:
http://forum.xda-developers.com/showthread.php?p=9866675
It has the adb commands on how to replace the existing boot loader with cwm and all.
Hope it helps.
EDIT: If all else fails, you can try flashing a nandroid backup (2.3.3). This post would guide you:
http://forum.xda-developers.com/showthread.php?t=979851
Greetings Cygnum,
Thanks for the suggestion. I have a question: will these commands work on a Mac?
Thank you to AllGamer for suggesting that I post this question here and for the following suggestion:
AllGamer said:
please post the same question in QA or General, then we can all help you
PM is not the best place to ask for help.
The first thing to do is to download the full set of Android SDK 2.3+ for MAC
then we'll continue from there.
Click to expand...
Click to collapse
How do I proceed AllGamer? I downloaded the mac SDK from here (http://developer.android.com/sdk/index.html).
Follow steps 1-7 from here to get back Clockwork Recovery.
http://forum.xda-developers.com/showthread.php?t=878446
If your bootloader is already unlocked, you can skip those steps.
Do steps 8-9 to copy this file over to your USB drive.
http://devsforandroid.com/ip.board/index.php?/files/file/94-stock-deodexed-233-voodoo-rooted/
This rom is Master's Stock 2.3.3 ROM that is already rooted which should get you up and running.
Unmount, go back. Wipe system data, wipe cache. Go to advanced, Wipe Dalvik-cache.
Go back, choose to install zip from SD card. Locate Master's stock ROM. Flash that.
In the end, you'll have a stock deodexed rom that is rooted. Keep in mind that you will lose all your data, but that at least puts you back on track.
Also wanted to mention if you didn't already know, mac scripts are run with a "./" in front of them. So to use the adb command you would do something like, "./adb reboot bootloader" after you have changed your directory to the folder that contains the sdk files.
peeturr said:
Also wanted to mention if you didn't already know, mac scripts are run with a "./" in front of them. So to use the adb command you would do something like, "./adb reboot bootloader" after you have changed your directory to the folder that contains the sdk files.
Click to expand...
Click to collapse
I feel bad for being a stickler here, but this is only true if he has not added the location of the binaries to the PATH. ./ just specifies to start in the local directory rather than look to the PATH to search for the file, it's not a requirement for running a script.
krohnjw said:
I feel bad for being a stickler here, but this is only true if he has not added the location of the binaries to the PATH. ./ just specifies to start in the local directory rather than look to the PATH to search for the file, it's not a requirement for running a script.
Click to expand...
Click to collapse
Yeah my bad. Just whatever had worked for me. Pretty new to mac myself.
Sent from my Nexus S using XDA App
krohnjw said:
I feel bad for being a stickler here, but this is only true if he has not added the location of the binaries to the PATH. ./ just specifies to start in the local directory rather than look to the PATH to search for the file, it's not a requirement for running a script.
Click to expand...
Click to collapse
Doesn't ~/ do the same as well?
Sent from my MattedBlues CM7 Nexus S from the XDA Premium app.
kenvan19 said:
Doesn't ~/ do the same as well?
Sent from my MattedBlues CM7 Nexus S from the XDA Premium app.
Click to expand...
Click to collapse
No. ~/ specifies your home directory
Thanks Everyone
Thanks for all the suggestions and help I received. I PM'd KenVan and he provided me with the script and my Nexus S is up and running.
I just had this problem on the weekend I could not get past the lockscreen so I flashed cyanogen nightly and bam booted fine
Sent from my Nexus S using XDA App
Problem Solved Over the Weekend
Thanks for the help everyone. I posted this in a couple places, so I forgot to update this thread.
I fixed the problem with detailed steps from KenVan. Thanks again though to all of you for your suggestions.

[RESOLVED] Stubborn security on MT4G. Will not Temp-Root.

I was able to root my MT4G with ease using VisionARY r14. My friend purchased a MT4G shortly after and I was trying to root it for him, I used several methods and no luck on any of them.
I've tried using:
1. Visionary temp root>attempt perm root
2. Visionary temp root>terminal (sh root.sh)
3. Visionary temp root>terminal (/data/local/wpx.ko)
From what I understand #2 & #3 basically are the same. So going back to the problem, on MY phone (I don't recall if I used #1 or #2), I rooted with no issues. On his phone, the root is not sticking, every time I go into the bootloader on his S=on still. Nothing stands out or is out of the ordinary, and I would think it would have rooted just fine, the scripts ran via terminal emu and looked okay and all.
Something else I've noticed is when I install CWM Recovery via ROM Manager, after temp root from Visionary the install of CWM Recovery itself was fine, though after going into bootloader and trying to access recovery or booting into recovery from ROM Manager, it doesn't go into recovery, I get the cell with red triangle and "!" on it. I'm assuming that this is a result of it being unrooted still? Anyone else run into a stubborn MT4G like this? I've attached 2 pictures for visual aid of the phone's bootloader screen and about screen below.
Any suggestions or help is greatly appreciated, I've been trying to root it for over a week now and no luck.
I can't see the pics you posted, but I had this issue myself, for me the answer was to find a stock recovery pre ota update and force it, then I ran visionary and terminal with sh root.sh or whatever... Hope this helps... Just try to find an image of pre ota stock rom and go from there... There is a good forum here with a walkthrough to do this... Post results please, would like to know if this was your issue...
Sent from my HTC Glacier using XDA App
Hey I ran into the same problem, with that 86.0000 boatloader u must use the gfree chmod777 process its because its after the ota update
Sent from my HTC Glacier using XDA Premium App
grankin01 said:
Ok guys, first of all Scotty2 gets all the credit for the program R&D. I used my device as a test bed and have tried a couple different kernels (Gr8Gorilla's O/C Kernel and the stock kernel).
Now for the boring stuff ...
This is a very invasive way of rooting your device but the benefit is TRUE S=Off and root privileges throughout the system. As such, you do this at your own risk and if you brick your device neither Scotty2 nor myself are responsible, YOU ARE!!! Do this at your own risk!!!
This is not for the faint of heart and if you have any reservations about doing things like this do not do it.
This process will do three things for your device. I will explain them here:
1. It will set up Super CID on your device allowing you to flash any carriers rom (not just tmobile). Giving you more freedom with your choice of software. The software still needs to be device specific to the glacier for compatability reasons though. Like vodafone glacier roms etc.
2. It will subsidy unlock your device. In other words, it will SIMUNLOCK your phone allowing you to use an AT&T sim card and so on in your device without needing the unlock code from HTC.
3. Most important of all it will turn the RADIO S=Off. This is the ultimate S=Off because the radio is what controls the security flag in the first place. Once you turn it off here it is off everywhere and will allow you pure unadulterated access to your device.
This process will not change your bootloader (unless your on 0.86.0000 and you follow the optional steps).
Now, you may be asking "Why do this? I already have root from your other guide and it has given me r/w access to system and recovery. I thought this meant we had permanent S=Off." This is only partially true. We have had an engineering bootloader and "Label" s=off not radio s=off. When you turn the security off in radio it is off permanently no matter what hboot you have installed engineering or otherwise. However, it is optional but you can still copy the engineering hboot over and it will allow you to flash whatever you like without (as much) fear of bricking your device.
This guide assumes you know how to use ADB. If you do not there are guides all over XDA to show you how. There is even a really good one in this forum. Also here is a video on how to setup adb discovered by topgun303: http://www.youtube.com/watch?v=1UF5w1dKe2U
*NOTE*
For some reason this process can bork your recovery. If you notice after following the steps below that in order to reboot from recovery you have to uninstall/reinstall the battery and hit the power button, just install/reinstall clockwork recovery through Rom Manager in the android market and it will fix your problem.
CONFIRMED: Guide does work for pre-OTA devices!!! Thanks xanz!
Here we go:
If you are already permarooted per the other guide just follow the first 11 steps.
Make sure you have visionary installed on your device. (If you were already permarooted w/s=off ignore this step.)
Download this file:
http://www.mediafire.com/?s7afymwe2wb3x60 New version of gfree with more options! See below.
md5sum: b73c56ca0e21664c5756d4ad295063c5
1. Now unzip the file into your SDK tools directory.
2. Plug your device into your computer.
3. Now open explorer and hold down shift at same time you right mouse click on your SDK tools directory (platform-tools if you have the R8 version of the SDK). Select open command window here. If you are in linux (ubuntu) right mouse click on your SDK tools folder, choose actions, and choose open command window(or whatever it's called). Otherwise, open a command prompt and cd your way to your SDK tools directory.
4. Type "adb push gfree /data/local" and hit enter.
Optionally, you could dl the file to your phone use androzip or something like it to unzip the file and then use root explorer to move the file named gfree to /data/local. Not the gfree.h file. All the other files are source code inlcuded for the gnu license. This would skip the first 4 steps.
5. Now unplug your device from the computer.
6. Run visionary to gain temp root. (If you were already permarooted w/s=off ignore this step.)
7. Open terminal emulator on your device, type "su", and hit enter to gain root privileges.
8. Type "cd /data/local" and hit enter.
9. Now type "chmod 777 gfree" and hit enter to make the program executable.
10. Type "./gfree -f" and hit enter.
New features in gfree.
gfree usage:
gfree [-h|-?|--help] [-v|--version] [-s|--secu_flag on|off]
-h | -? | --help: display this message
-v | --version: display program version
-s | --secu_flag on|off: turn secu_flag on or off
-c | --cid <CID>: set the CID to the 8-char long CID
-S | --sim_unlock: remove the SIMLOCK
With the new features you can turn off one thing at a time. You can also turn security back on and set the CID back to stock if you wish. To turn simlock back on you still have to follow the revert procedures on this page as the information that is patched to turn the lock off is encrypted and we can't write back to it other than restoring the entire image.
So, if you wanted to leave simlock on but turn security off and set super CID the command would be "./gfree --secu_flag off --cid 11111111" + enter. The -f switch after ./gfree that is now in the above step (./gfree -f) just tells gfree to patch everything.
11. Wait for the program to finish and then reboot into HBoot to see if S=Off. Also, check your bootloader version. If it says s=off and has bootloader version 0.86.0000 it worked.
If you already had hboot 0.85.2007 you can check it through the hboot menu. It gives you an option for "system info" in the hboot menu. Highlight it and hit power. It should say CID = 11111111 or something like that. If it does your golden.
Congratulations!
12. If this is the first time you have rooted your device you will need to run visionary again (temproot w/set system r/w after root checked and then attempt permroot) to make root privileges permanent and then reboot again. Now "su" should work properly for you.
Gfree writes a backup of the file that it patches named Part7backup-numbers.bin on your sdcard. I suggest putting this file in a safe place as it is the only way to revert if you need to.
[Optional] Steps to flash engineering bootloader.
1. Restart your phone and plug it back into your computer.
2. Download this file: http://www.megaupload.com/?d=NN5726Z8
md5sum: df4fd77f44993eb05a4732210d2eddc6
3. Copy the file to your SDK tools directory.
4. Open a command prompt again and cd into your SDK tools directoty (platform-tools if your on the new R8 SDK).
5. Type "adb push hboot_dhd.nb0 /data/local" and hit enter.
6. Now open terminal on your device and type "su" and enter to gain root priviliges.
7. Type "cd /data/local" and enter.
8. Now type "dd if=hboot_dhd.nb0 of=/dev/block/mmcblk0p18" and hit enter.
9. You should see something like: 2048 bytes in 2048 bytes out 1048576 bytes copied blah blah blah.
10. Now restart the device into hboot and check if your bootloader version is 0.85.2007. That is what you want to see.
Congratulations, you now have a TRUE root and engineering bootloader on your shiny MT4G!!!
Click to expand...
Click to collapse
Sent from my HTC Glacier using XDA Premium App
ZuluNexus said:
Hey I ran into the same problem, with that 86.0000 boatloader u must use the gfree chmod777 process its because its after the ota update
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
I second this, gfree works great
ZuluNexus said:
Hey I ran into the same problem, with that 86.0000 boatloader u must use the gfree chmod777 process its because its after the ota update
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
This would explain why I had to flash the pre ota stock image before I could root using the sh root.sh.... I am sure the chmod777 would have worked also...
Sent from rooted Royal Glacier using XDA app
powduh09 said:
I can't see the pics you posted, but I had this issue myself, for me the answer was to find a stock recovery pre ota update and force it, then I ran visionary and terminal with sh root.sh or whatever... Hope this helps... Just try to find an image of pre ota stock rom and go from there... There is a good forum here with a walkthrough to do this... Post results please, would like to know if this was your issue...
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
I see. So just get a pre ota stock rom and Visionary would be the simplest way then? But would the pre ota stock ROM also include the < 86.0000 botloader?
ZuluNexus said:
Hey I ran into the same problem, with that 86.0000 boatloader u must use the gfree chmod777 process its because its after the ota update
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
ZuluNexus said:
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
ziggy34 said:
I second this, gfree works great
Click to expand...
Click to collapse
Thumbs up
powduh09 said:
This would explain why I had to flash the pre ota stock image before I could root using the sh root.sh.... I am sure the chmod777 would have worked also...
Sent from rooted Royal Glacier using XDA app
Click to expand...
Click to collapse
Which method did you use to flash the pre ota image?
And thanks everyone for the quick replies!
When I flahed pre ota I found the forum on here for it. Just placed the file on my sd card and named it PD15IMG and booted phone to hboot, it found update and went from there
Sent from rooted Royal Glacier using XDA app
powduh09 said:
When I flahed pre ota I found the forum on here for it. Just placed the file on my sd card and named it PD15IMG and booted phone to hboot, it found update and went from there
Sent from rooted Royal Glacier using XDA app
Click to expand...
Click to collapse
Awesome, what is hoped for! Thanks!
Sent from my HTC Glacier using XDA App
EDIT!!
RESOLVED!
Unfortunately the method of just using the PD15IMG did not work because the bootloader recognized it as an older image and wouldn't update it. I came across this thread and successfully rooted!! =]
http://forum.xda-developers.com/showthread.php?t=995549
I improvised a bit and did not use "Androzip" I had "Adao File Manager" already installed on my friends phone. Basically.
Credit goes to the OP of the posts!! But here's the link to the gfree the OP is referring to. http://forum.xda-developers.com/showthread.php?t=858996
I am having a problem getting the gfree files to move where they need to be and sry guys, unsure of ow to use sdk, im need the dummy dummy guide anyone? Ive been researching for days lol
Rainbowbright081 said:
I am having a problem getting the gfree files to move where they need to be and sry guys, unsure of ow to use sdk, im need the dummy dummy guide anyone? Ive been researching for days lol
Click to expand...
Click to collapse
You need a root explorer.
*Root can be accomplished without SDK.
Sent from my Glacier running CM7 RC2 via XDA app.
YOu can try using mt4groot.zip google it
I managed to get it done right with adb, s=off perm, running cm7 with honeycomb. Quite awesome!
Sent from my HTC Glacier using XDA Premium App
lilazngoku8 said:
YOu can try using mt4groot.zip google it
Click to expand...
Click to collapse
It's in the second link I posted. Safer than Googling.
Rainbowbright081 said:
I managed to get it done right with adb, s=off perm, running cm7 with honeycomb. Quite awesome!
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
Running CM7 with Honeycomb? I am mistaken? You mean the honeycomb theme?
Sent from my Glacier running CM7 RC2 via XDA app.
Sry yes running the honeycomb theme
Sent from my HTC Glacier using XDA Premium App
Rainbowbright081 said:
Sry yes running the honeycomb theme
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
Lol cool, I was going to say, 3.0??!! ; )
gordonzhao said:
Awesome, what is hoped for! Thanks!
Sent from my HTC Glacier using XDA App
EDIT!!
RESOLVED!
Unfortunately the method of just using the PD15IMG did not work because the bootloader recognized it as an older image and wouldn't update it. I came across this thread and successfully rooted!! =]
http://forum.xda-developers.com/showthread.php?t=995549
I improvised a bit and did not use "Androzip" I had "Adao File Manager" already installed on my friends phone. Basically.
Credit goes to the OP of the posts!! But here's the link to the gfree the OP is referring to. http://forum.xda-developers.com/showthread.php?t=858996
Click to expand...
Click to collapse
This is just a laid out variant of the ./gfree method. It'll work but it's been around since the dawn of the Glacier. It's nothing special .

[Q] Need Help/advice

I used this method to try and root the xformer......... all worked good until I tried to push the Superuser apk it did not push. Upon trying again, it said it was a read only file
Any suggestions?>
It is a 4/23/11 build I was using BLobV5
http://androidroot.mobi/asus-eee-pad-transformer-tf101-root-cwm-recovery/
Thanks
Do "adb remount" then try again.
Sent from my HTC Vision using XDA Premium App
well Got the superuser but still does not allow titanium backup to access root, I have busybox downloaded, and downloaded rom manager ad rebooted a couple of times
???? repush superuser ?

Categories

Resources