Develop Bugs

huge adb problemo

Okay i have a big problem...
I have rooted my device, however didn't run the ENG build, so my recovery is dependent on the pushing of the update.zip...
I flashed the myfroyo5 after pushing the update.zip... and ADB worked great, found the device in HBOOT and recovery.
Now after flashing this ROM, when i try and reboot back HBOOT no devices found.. however when i'm at the home screen with Myfroyo5 booted up, it sees the device..
Now i can't run any update, or get into clockwork recovery because i can't push the update.zip, because ADB can't see my device....
Please help! Any idea how i can get it to see my device with Myfroyo5? Otherwise i'm stuck with Myfroyo5 and can't reverse or do anything with it
Before all i did was change the option from device storage, to charge only, and that's how it worked...
again any ideas are appreciated!

wow 58 views and no one has any ideas? Please help!

Try turning on USB debugging mode?

Yes its always on, always check marked

I feel like I did have a similar problem at one point, but I don't remember how I resolved it. Sorry.

gee maybe you should have flashed the eng build as everyone was told to do when they rooted their slide. try a dozen different large and small SD cards, i don't really think that is what makes it work but others seem to disagree and maybe once you swap them out you'll get lucky. but first i would try flashing the eng build

tubaking182 said:
gee maybe you should have flashed the eng build as everyone was told to do when they rooted their slide. try a dozen different large and small SD cards, i don't really think that is what makes it work but others seem to disagree and maybe once you swap them out you'll get lucky. but first i would try flashing the eng build
Click to expand...
Click to collapse
Must your replies always, ALWAYS have some snarky bit about how the person asking the question screwed up?
Humans are prone to error. You have valuable insight but beating someone's ego up before you give it really offsets your kindness.
Sent from my T-Mobile myTouch 3G Slide using XDA App

They don't always have snarky bits, but when 90% of problems are caused by not following directions then it apparently needs to be retold, I help a lot and I gave ideas to try here. Odds are he can still flash the eng build and then get into clockwork, but not following directions causes issues like this.
Sent from my T-Mobile myTouch 3G Slide using XDA App

I see your point but, as I recall, the ENG build came after root had been put out there for a day or so. I'm also pretty sure it came after SlideMeRoot1.
Things like this, along with simple mistakes, can cause these errors. You are helpful but I just find the "hey, dummy" tone to be overkill.
Not everyone who screws up is out to **** up your day, ya know? I've been having my own ENG build problems because I made a mistake. It doesn't mean I don't know how to follow directions, it just means I made a mistake, the way every human on the planet does.
I apologize, as well, because my own real life smiley fun tone doesn't translate well to the forum. IE: you good kid.
tubaking182 said:
They don't always have snarky bits, but when 90% of problems are caused by not following directions then it apparently needs to be retold, I help a lot and I gave ideas to try here. Odds are he can still flash the eng build and then get into clockwork, but not following directions causes issues like this.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
Sent from my T-Mobile myTouch 3G Slide using XDA App

well first off.. i did follow directions... and it didn't work... and i've flashed multiple roms by just re-doing the ota.zip then the update.zip push, to get me into clockwork, until i flashed myfroyo5
which does not allow me to "charge only" which is why ADB doesn't allow to recognize my device in HBOOT/Recovery.
On the contra-ire i do know what i'm doing however a little bit of "knowledge" to point out maybe something that will fix an issue i have would be great.
Now i'm running myfroyo5, the device is seen by adb when the phones booted up, however upon reset to HBOOT/Recovery no devices are found. I've tried putting ENG build on my Sdcard, and HBOOT doesn't see it, also, i've tried pushing flash_image to /data/local, and mtd0.img to /data/local, and the files will not move.
That is part of my problem i'm assuming, i'll try another SD card to see if it will fix it, but i'm not sure its something that simple... but who knows, right?

javolin13 said:
well first off.. i did follow directions... and it didn't work... and i've flashed multiple roms by just re-doing the ota.zip then the update.zip push, to get me into clockwork, until i flashed myfroyo5
which does not allow me to "charge only" which is why ADB doesn't allow to recognize my device in HBOOT/Recovery.
On the contra-ire i do know what i'm doing however a little bit of "knowledge" to point out maybe something that will fix an issue i have would be great.
Now i'm running myfroyo5, the device is seen by adb when the phones booted up, however upon reset to HBOOT/Recovery no devices are found. I've tried putting ENG build on my Sdcard, and HBOOT doesn't see it, also, i've tried pushing flash_image to /data/local, and mtd0.img to /data/local, and the files will not move.
That is part of my problem i'm assuming, i'll try another SD card to see if it will fix it, but i'm not sure its something that simple... but who knows, right?
Click to expand...
Click to collapse
Just use CR new root method for the ota update and then follow the steps to flash ENG build. wouldnt that work? cause its unneccessary for the device to be recognized in hboot in adb that way =\ just guesing

i would do all that too.... you know i think the issue is the copying the files over... none of them are actually moving where they need to go!...
And when i try to do it manually the folder says "read only file system" and when i try to push files it says "1188 KB/s <0 bytes in XXXX.000s>
so none of the image files are moving over to allow me to flash ENG build... i swapped different SD cards and now i can flash the ENG build, but i cant move the files to /data/local before i do that, so right now its pointless to flash it...

javolin13 said:
i would do all that too.... you know i think the issue is the copying the files over... none of them are actually moving where they need to go!...
And when i try to do it manually the folder says "read only file system" and when i try to push files it says "1188 KB/s <0 bytes in XXXX.000s>
so none of the image files are moving over to allow me to flash ENG build... i swapped different SD cards and now i can flash the ENG build, but i cant move the files to /data/local before i do that, so right now its pointless to flash it...
Click to expand...
Click to collapse
do u have root in the shell script when u try to push the files over?

yes i do, that's whats really weird... i do adb shell, and i get #
when i do it the cat way, it does what it needs to, yet when i go search for the files using linda file manager they're still not there...
i dont want to flash eng build and it not work...

javolin13 said:
yes i do, that's whats really weird... i do adb shell, and i get #
when i do it the cat way, it does what it needs to, yet when i go search for the files using linda file manager they're still not there...
i dont want to flash eng build and it not work...
Click to expand...
Click to collapse
i mean u could always just unroot and start from square one

can't unroot if my device is not seen with adb in hboot / recovery

javolin13 said:
well first off.. i did follow directions... and it didn't work... and i've flashed multiple roms by just re-doing the ota.zip then the update.zip push, to get me into clockwork, until i flashed myfroyo5
which does not allow me to "charge only" which is why ADB doesn't allow to recognize my device in HBOOT/Recovery.
On the contra-ire i do know what i'm doing however a little bit of "knowledge" to point out maybe something that will fix an issue i have would be great.
Now i'm running myfroyo5, the device is seen by adb when the phones booted up, however upon reset to HBOOT/Recovery no devices are found. I've tried putting ENG build on my Sdcard, and HBOOT doesn't see it, also, i've tried pushing flash_image to /data/local, and mtd0.img to /data/local, and the files will not move.
That is part of my problem i'm assuming, i'll try another SD card to see if it will fix it, but i'm not sure its something that simple... but who knows, right?
Click to expand...
Click to collapse
I had the same problem just about and used the following thread. http://forum.xda-developers.com/showthread.php?t=710056 <-- BIG THANKS to Beartard for taking the time to type this all out. It worked just fine. I picked it up from - Installing the Engineering ROM - I kept my old update.zip file on the root of my sd card, and I got everthing back to normal, and everything works like new. Hope this helps

Suntar said:
I had the same problem just about and used the following thread. http://forum.xda-developers.com/showthread.php?t=710056 <-- BIG THANKS to Beartard for taking the time to type this all out. It worked just fine. I picked it up from - Installing the Engineering ROM - I kept my old update.zip file on the root of my sd card, and I got everthing back to normal, and everything works like new. Hope this helps
Click to expand...
Click to collapse
Thanks for the idea, but flashing the ENG build is pointless unless i can push the flash_image, and mtd0.img to /data/local... which for some reason my phone will not allow me to do this part;
Code:
type "adb push flash_image /data/local" and hit enter.
2. Type "adb push mtd0.img /data/local" and hit enter.

After AlphaRev?

Now that we S-OFF our Desire what can we do?
I tried to upgrade pre-installed apks (like google maps, gmail, ...) or change /system files but again device says me that I don't have sufficient permissions...
Maybe I didn't understand something really important regarding S-OFF. Where to read some more about?

You still need to be root to remount and/or write to /system.

Rudolfje said:
You still need to be root to remount and/or write to /system.
Click to expand...
Click to collapse
Yes I'm root.
And also I tried in "spareparts app" to check to mount filesystem in rw.

Does it depends also on what ROM we are using?
Currently I'm using AuraxTSense 7.6.1.

...tried also changin rom... in particular using some that is sysrw but with no changes.
Is it possible that only me have doubt about this????

Does anybody knows how to change the picture from the start?
In the instructions it says"you can download the stock splash1 screen for HTC Desire from here. Make sure you flash it with 'fastboot flash splash1 desire_stock_splash1.img'.
"
How do you do this?

Bisis:you are doing something wrong. Mine works fine. And you should try to describe exactly how you have tried and failed.
BTW. If you don't know how to use s-off why did you flash it?
As for the splash1 screen, you do exactly what they say. When in fastboot you run the specified command. You need the Android sdk though as it is required to run adb and fastboot commands. I can help you further if needed

I think you need a file manager with root access...astro and so on not work...but root explorer or android mate do the job
With kind regards...Alex
Sent from my HTC Desire using XDA App

root explorer works fine, just remember to switch to R/W
i deleted some native apps with it.
hint: mobilism*

Is it possible with S-OFF to read the SIM UNLOCK code?

djcool37 said:
Is it possible with S-OFF to read the SIM UNLOCK code?
Click to expand...
Click to collapse
..where would that show up?

ALEX You were right!
Sent from my HTC Desire using XDA App

[GUIDE] Permanent Root with Visionary/gfree (No ADB Required)

After seeing lots of users struggle to root their phone with the existing guides (or worse, brick their phones), often times because of an inability to install/use ADB correctly (so they hobble together steps from multiple guides), I decided to write up a guide for rooting without the need for ADB. This guide uses the Visionary program to achieve temporary root and then gfree to achieve permanent root. Visionary is used only for the temporary root and nothing else (since many on these forums are wary of the app for permanent rooting). All of the gfree steps were scripted together to make things more convenient (and allow less room for user error in typing things in). This has been tested to work with multiple G2s and theoretically should work with the Desire Z as well (if you have the 1.72 OTA though, you will need to downgrade first in order to root as per the instructions in the wiki). All credit goes to the original developers of these programs and those others who aided in achieving root originally (I didn't add anything new content-wise, just bundled it up nicely).
WARNING: A few Desire Z users have reported being stuck on the HTC logo after following this guide. Without having a Desire Z myself, it is difficult to figure out why (since this simple automates known working methods). For the time being, I recommend Desire Z users obtain permanent root using one of the other guides out there.
Instructions
1. Install Terminal Emulator and a file manager (such as Astro File Manager) from the Market.
2. Extract the contents of the zip file to the SD card (this will create a directory called root_files on the card). When done, make sure you unmount your SD card from your computer if you had mounted it as a storage device to transfer the files.
3. Enable Unknown Sources (under Settings->Applications) and USB Debugging (under Settings->Applications->Development).
4. Using your file manager, navigate to the root_files directory on your SD card and select "com.modaco.visionaryplus.r14.apk" to install the Visionary app.
5. Start the Visionary app.
6. Click on "Temproot now." Leave all other settings unchecked.
7. Start the Terminal app.
8. Type the following commands (the $ and # symbols represent the command prompt and should not be typed):
Code:
$ su
# cp /sdcard/root_files/perm_root /data/local/perm_root
# chmod 777 /data/local/*
# /data/local/perm_root
You will see multiple messages scroll by as the programs run. Once you are returned to the prompt in terminal, you will have permanent root (S-OFF), as well as subsidy unlock and SuperCID. At this point, you can also choose to flash the engineering hboot as explained in the wiki. Flashing this hboot allows you to use the flashboot program to flash images from your computer to your phone (which can be very helpful when stuck in a bootloop for example). Note, this is often times the step that bricks people's phones when following other guides. To help mitigate the danger involved, I created a script that first checks the md5 of the hboot file to ensure it didn't get corrupted and then actually performs the flash (many times the bricking occurs because of a typo in this command). If you wish to flash the engineering hboot, type the following command in terminal if you have a G2:
Code:
# /data/local/tmp/flash_hboot
Or this command if you have a Desire Z
Code:
# /data/local/tmp/flash_hboot_z
If you get a verification failed message, you should re-download the files, re-extract them to your SD card, and run the flash_hboot script again.
If you don't want the engineering hboot, just reboot your phone. You can verify you have permanent root by holding volume down while powering on (you'll see S-OFF in the first line of the bootloader). You are now free to install a new recovery and start flashing custom ROMs. If you don't want to flash a new ROM, it's safe to uninstall the Visionary app at this point.
And if you are curious, you can open the perm_root and flash_hboot files in a text editor to see what they are actually doing...

thnak you bro man this was way better !!!

does this apply to someone who just bought the G2.currently on stock 2.2?

GHOST99K said:
does this apply to someone who just bought the G2.currently on stock 2.2?
Click to expand...
Click to collapse
YES!!!! Especially you! This is much easier than the previous ways!
NICE!

I wish I had seen this last night before I spent 4 hour trying to get ADB to see my wife's new phone. Oh well got it working the hard way

Copy flash_hboot
Do you need to copy the flash_hboot like the perm_root file?

Crey23 said:
YES!!!! Especially you! This is much easier than the previous ways!
NICE!
Click to expand...
Click to collapse
cool i guess 2 of my friends will be pleased to hear this cuz i'll be helping them to root their phones.

worked like a charm! sweet man, saved me a lot of time by making this thread and guide, definitely should be added to wiki or sticky thread.

I just bought a T-mobile G2 as well, and I love the phone as is, but I just want to root it, so I can over-clock the cpu just a little bit (maybe about 1Ghz is fine). Can I use this method and keep the phone as is? Or does this method delete everything and I need to use custom rom? I'm coming from original MyTouch 3G (without 3.5 jack) rooted with CM, but I am still a newb.

misterykid89 said:
I just bought a T-mobile G2 as well, and I love the phone as is, but I just want to root it, so I can over-clock the cpu just a little bit (maybe about 1Ghz is fine). Can I use this method and keep the phone as is? Or does this method delete everything and I need to use custom rom? I'm coming from original MyTouch 3G (without 3.5 jack) rooted with CM, but I am still a newb.
Click to expand...
Click to collapse
Once you root the phone, everything will stay as is. Here's a link to overclock to at least 1 GHz on stock ROM: http://theunlockr.com/2010/10/20/t-mobile-g2-overclocked-to-1-42ghz-how-to-overclock-your-t-mobile-g2/
However, it's required you first set up ADB.

I can't just download setCPU and over-clock? I thought as long as the phone is rooted, I can do that...

misterykid89 said:
I can't just download setCPU and over-clock? I thought as long as the phone is rooted, I can do that...
Click to expand...
Click to collapse
You can still download SetCPU, but just having the app itself won't let you overclock the phone. You can try flashing a different ROM and you'll be overclocked once you run that ROM.

Wait, but the recommended and safest way is still with Rage and GFree, right? VISIONary was found to do something with the phones file system that messes up some phones I thought, right? I thought that is why scotty2 made Rage, or am I wrong?

KoolKidsKlub said:
Wait, but the recommended and safest way is still with Rage and GFree, right? VISIONary was found to do something with the phones file system that messes up some phones I thought, right? I thought that is why scotty2 made Rage, or am I wrong?
Click to expand...
Click to collapse
Rage/G-Free is still the safest but they both require ADB, which can be quite a hassle to install for many. True that Visionary has been found to mess one's phone up, but this method only implements the temp root procedure from Visionary (which doesn't require ADB) and the perm root procedures from Rage/G-Free for a more simple way to root one's G2.

so its more like the best of both methods then... i gave up cus i couldnt figure out the ADB but this way looks way easier so ima give this a try thanks for this

Worked perfectly first try. Thanks!

What exactly is kernel? I've seen some people saying they are running over-clock on their G2 with a modded kernel on stock ROM.

misterykid89 said:
What exactly is kernel? I've seen some people saying they are running over-clock on their G2 with a modded kernel on stock ROM.
Click to expand...
Click to collapse
Search google for "Kernel Operating System"

What I meant was is it okay to just change the kernel and run stock ROM that came with my T-mobile G2? Would it not change anything except for the clock speed?

misterykid89 said:
What I meant was is it okay to just change the kernel and run stock ROM that came with my T-mobile G2? Would it not change anything except for the clock speed?
Click to expand...
Click to collapse
Different kernels can be compatible only with certain ROM's. Check on on the kernel before you flash to stock ROM

Prem Root MyTouch 4g 0.86.0000 bootloader!

Alright kids I'll try to make this a simple as possible those of you that are scratching your heads and wondering why you cant get S-on to say OFF..... on the newer MT4G with bootloader 0.86.0000 HERE WE GO.
Step 1:
Download Androzip,Terminal Emulator,Root Explorer and Superuser
Download - Visionary11(yes its an old build, but its simple and less confusing for you noobs.)
Once you have these apps put them on you MT4G homescreen page(doesnt matter in what order just as long as these apps are quickly accessible to you.)
Step 2:
Make sure you go into Settings on your MT4G.
now that you have selected Settings select Applications Make sure that Unknown sources has been selected
On the same Settings screen you will also see Fast boot Make aure to deselect it!
Once the Fast boot has been deselected, select the Development you be transfered to another screen the only items that should be selected is USB debugging. Once you have finished this go back to you home screen.
Step 3:
At this point you should be at the home screen with all the apps you downloaded in Step 1.
Now Select Visionary, once Visionary is open select Set system r/w after root.
Now press Root Now!. let Visionary temproot your MT4G(CAN TAKE UP TO 10-30 SECONDS BE PATIENT!)
Ok that part is Done. go back to your home screen.
Step 4:
Select Terminal and type - su you should see "Terminal Emulator has been granted superuser permission", it will be a real quick pop up saying this. Ok you are now temp rooted. go ahead and select the hardkey arrow and press it until you get to the home screen.
Step 5:
With theMT4G's internet browser find the gfree file on the TRUE PermaRoot and the ULTIMATE S=Off!!! forum
Open the gfree file with Androzip, that you download onto your MT4G NOT with what your computers
unzips this file with!
Step 6:
Once you have Unziped the gfree file from your phone into your phone, you will need to locate and transfer everything that is in the gfree folder DO NOT TRANSFER THE FOLDER ITSELF WITH THE CONTENTS IN IT. Just open the gfree folder and transfer everything inside there. Time to locate where Androzip placed the gfree file
Open Root Explorer scroll down until you see the sdcard file, ok open it!
Scroll down until you see the AndroZip file open it! WALA.... I present to you the extracted gfree scripts. Now that your looking at them, I need you to select the Menu Hardkey Button which is next to your home Hardkey Button. Once you've pressed the Menu hardkey it will options will pop up on your MT4G screen, select Multi-select now select everything inside of the gfree folder.( youll notice the green checks when selecting ) you will also see another option of commands, select move
Now with move selected, navigate those files with the arrow hardkey on your MT4G to /data/local and paste them in that location. Done with that process! close your Root Explorer and return to your home screen.
Step 7:
Open Terminal Emulator and type the following:
type "su", and hit enter
type "cd /data/local" and hit enter.
type "chmod 777 gfree" and hit enter to make the program executable.
type "./gfree -f" and hit enter.
Wait for the program to finish and then reboot into HBoot you'll see that S=Off. Also, check your bootloader version. If it says s=off and has bootloader version 0.86.0000 it worked!
You will need to run visionary11 again (w/set system r/w after root checked and then press Root Now!) to make root privileges permanent and then reboot again. Now "su" should work properly for you.
This will work 100 percent if you read these instruction very carefully and follow these steps exactly!

Thats the same instructions from the gfree thread.
How is this different?

if this is the same then why the hell are people not getting it?! im seeing a lot of people regarding that the newer MT4G with bootloader .86 is extremely hard or damn near impossibly to S-off if this doesnt explain how to do it in lamens term then these people are true NOOBS and should stick with their STORM 2 stick with the basics and not with the FAKE Sh**t!. just trying to help

mine had bootloader 86 and it rooted just fine. People just need to follow the directions better.

easeback said:
if this is the same then why the hell are people not getting it?! im seeing a lot of people regarding that the newer MT4G with bootloader .86 is extremely hard or damn near impossibly to S-off if this doesnt explain how to do it in lamens term then these people are true NOOBS and should stick with their STORM 2 stick with the basics and not with the FAKE Sh**t!. just trying to help
Click to expand...
Click to collapse
My phone has 86. Bootloader and it took me bout 15 min using gfree method still has 86. Bootloader i didnt do eng but root was easy as pie
Sent from my HTC Glacier using XDA Premium App

He took out the the extra talk and just put it very simple it shouldn't take no more the 5 min to do

easeback said:
if this is the same then why the hell are people not getting it?! im seeing a lot of people regarding that the newer MT4G with bootloader .86 is extremely hard or damn near impossibly to S-off if this doesnt explain how to do it in lamens term then these people are true NOOBS and should stick with their STORM 2 stick with the basics and not with the FAKE Sh**t!. just trying to help
Click to expand...
Click to collapse
this thread is beyond unnecessary.
i told those guys over n over they were doing it wrong lol. my phone came with .86 also and never had any issues.

Hes just trying to help but, it doesnt matter how many people post this, some of them still don't know how to follow instructions. Thanks for helping the noobs.
Sent from my HTC Glacier using XDA Premium App

Call me naive, but where do I obtain version 0.86.0000? My phone has 0.85.2007.

TeeJay3800 said:
Call me naive, but where do I obtain version 0.86.0000? My phone has 0.85.2007.
Click to expand...
Click to collapse
Version 0.86.0000 is what ur phone comes with u have yhe eng
Sent from my HTC Glacier using XDA Premium App

elry567 said:
Version 0.86.0000 is what ur phone comes with u have yhe eng
Click to expand...
Click to collapse
I have the engineering bootloader? I don't know how that's possible since I never changed it. I just rooted and installed CWM.

TeeJay3800 said:
Call me naive, but where do I obtain version 0.86.0000? My phone has 0.85.2007.
Click to expand...
Click to collapse
You have the eng bootloader. Your better off with it.

Yes, ALL the MT4Gs (at least all the ones I've seen) come with the 0.86.0000 bootloader. There shouldn't be any reason for this preventing you from rooting. The 0.85.2007 is the engineering bootloader. You get this either by manually flashing it (as per the instructions in grankin's true permroot thread) or if you used the root.sh script (such as those of us who followed theunlockr.com's walkthrough).
If you aren't succeeding with the gfree method, either you aren't following instructions properly or something else is interfering. My friend couldn't get VISIONary to temproot, but after uninstalling one of his file explorer apps, all of a sudden VISIONary worked.

Same here. Got mine the 11th of this month and rooted first try no problem.
option94 said:
mine had bootloader 86 and it rooted just fine. People just need to follow the directions better.
Click to expand...
Click to collapse
Sent from my HTC Glacier using Tapatalk

jdkoren said:
You get this either by manually flashing it (as per the instructions in grankin's true permroot thread) or if you used the root.sh script (such as those of us who followed theunlockr.com's walkthrough).
Click to expand...
Click to collapse
The method I used did include running the root.sh script, so that must be how I got the engineering bootloader. Thanks for the info.

TeeJay3800 said:
The method I used did include running the root.sh script, so that must be how I got the engineering bootloader. Thanks for the info.
Click to expand...
Click to collapse
That is correct... The root.sh includes the engineering bootloader within it and it is the better of the 2. I suggest installing it and you will not have any more problems.

SWEET! Thanks! I missed the other 50 threads with these directions!

Just a tip for people having problems rooting using the gfree method. Follow the instructions to the "T" and it works. As for the commands for terminal emulator...copy and paste them to a word document so you can be sure where there are spaces, and make sure that your 0's are not O's and so forth...Don't be afraid to ask for help, there are alot of nice people on this forum that will help you out.

thnx
thanks alot for this, idk why people on xda don't know how to speak in laymans terms, i guess it's to drive the noobies away, i've been around here since cyanogen had 3.0 on the G1, and i shyed away from using the gfree method on my buddies phone since it looked complicated (didn't want to do alot of reading and work) and i was just wanting to do it fast.
this thread simplified things for me so i can know what i'm doing, also i didn't want to download root explorere (dont' wanna pay $4) so i just pushed every file manualy using adb.
"adb push c:/blah data/local"

aalsmadi1 said:
thanks alot for this, idk why people on xda don't know how to speak in laymans terms, i guess it's to drive the noobies away, i've been around here since cyanogen had 3.0 on the G1, and i shyed away from using the gfree method on my buddies phone since it looked complicated (didn't want to do alot of reading and work) and i was just wanting to do it fast.
this thread simplified things for me so i can know what i'm doing, also i didn't want to download root explorere (dont' wanna pay $4) so i just pushed every file manualy using adb.
"adb push c:/blah data/local"
Click to expand...
Click to collapse
ES Filer explorer does what root explorer does as well, but it's free.

Can gain temporary root, but Permanent root will not stick.

Hello xda, in accordance with the signup video I have scoured the earth looking for an answer. However I'm not sure how much necro posting is frowned upon here so I thought it would be safer to just start a new thread.
I have an HTC Desire HD from Telus(for use on the Rogers network). I am in the process of rooting it but have encountered a problem. I can gain temporary root on the terminal emulator(Because the $ turns to #) however when attempting to run clockwork flash clockworkmod recovery I get the error "An error occurred while attempting to run privileged commands!"
I get the same error when attempting the "Fix Permissions" so I'm currently at a loss of what to do.
I have the ninja superuser icon in the apps menu however when I open it the screen is blank. I am unsure if this is how it is supposed to be or not. I have seen several references to a permission box that pops up during some of the steps but I haven't seen that at all.
I've tried four separate methods, the last of which coming from this thread http://forum.xda-developers.com/showthread.php?t=954997
I am currently at step B.d which involves running the S-OFF tool and Easy Radio OFF tool. But still clockwork will not flash a backup, and when I restart the phone I can not get super user to work on the terminal (ie by typing su) and must use the rage method to regain temporary root.
Also, I don't know if this is related or not, but when I restart the phone and attempt to boot in recovery mode, the volume buttons don't allow me to select other options, and instead the phone just forces me to reboot normally.
Some more facts:
model HTC Desire HD A9191
Build # 1.32.405.6
Android 2.2
Anymore info I'm probably forgetting just ask away!
So my question is: Can anyone identify what the issue is?
Thanks much for taking the time to read my question.

Does visionary not work for you?
I've seen that alot of success has been gained by doing temp root and perm root through it?
It does sound like the rage method might not be working for you from what I can tell..
I do want to check all the steps you followed before where fine?
Sent from outer space on my DHD running beatmod gingersense v1.3

Visionary was how I rooted mine. Worth a try if you havent tried it: http://android.modaco.com/content/software/320350/19-nov-r14-visionary-one-click-root/

Thanks for the visionary suggestion, but Visionary still isn't working :/
Has visionary been tested with the Telus Desire? I heard there was a difference. What happens when I attempt to temproot is it moves to a blank screen then goes back to the menu.

When I used visionary on 1.32 it did not always work first try ... generally always worked after 2 runs. then used it to perm root

It works. You do not have Telus software in your phone anymore.
Sent from my Desire HD using Tapatalk

Try my method (I made it because the methods I found for my Telus desire HD were flaky at best and only got temproots from it.)
Since you already flashed to 1.32 start at step 2
If you want to go gingerbread, dl the 2.36.405 ruu and use that and your pc to put 2.3.3 on it (dont worry, it works fine, i was using it since it came out and built a rom based off that, kingdom, and pyramid roms for my own sense 3 rom) and use the gingerbreak method.
http://driphter.com/index.php?topic=3867.0

Still haven't managed to get root. JSLEnterprises my antivirus won't let me download your file :/
I'm at a loss for what to do.

lemonpartyz said:
Still haven't managed to get root. JSLEnterprises my antivirus won't let me download your file :/
I'm at a loss for what to do.
Click to expand...
Click to collapse
Disable your Antivirus (Avast say's its malicious), Norton or F-Prot says its clean.
and Internet Explorer 9 says its not trustworthy (because there's .bat files in the zip), Firefox says its fine.
There is no malicious code in the zip, you can edit each individual batch file in the Resource folder to see the code. Its very simple and basic.

I disabled my antivirus, but when I run Install Visionary nothing happens. The CMD window opens and says it has been succesfuly installed but nothing has been installed, and nothing appeared in the app menu.
Edit: I went into the resource folder and then followed the steps from there and everything worked, except I still don't have the # symbol in terminal (even when entering "su") and ROM manager still gives me the same error.

lemonpartyz said:
I disabled my antivirus, but when I run Install Visionary nothing happens. The CMD window opens and says it has been succesfuly installed but nothing has been installed, and nothing appeared in the app menu.
Click to expand...
Click to collapse
go into the resource folder, edit the visionary install batch in notepad, delete the "cls" line, save and exit
rerun it with the phone attached. See if it truly installed successfully.

lemonpartyz said:
I disabled my antivirus, but when I run Install Visionary nothing happens. The CMD window opens and says it has been succesfuly installed but nothing has been installed, and nothing appeared in the app menu.
Edit: I went into the resource folder and then followed the steps from there and everything worked, except I still don't have the # symbol in terminal (even when entering "su") and ROM manager still gives me the same error.
Click to expand...
Click to collapse
you dont need to use the termial in my method.
Once visionary is installed, and you run it, and everything is done exactly whats described in my 9 easy steps thread (along with outcomes along the way), then you should be perm rooted, with s-off and eng-off with supercid.

I managed to install visionary with your method, however when running Eng-S I encountered the error "Bootloader corrupt, DO NOT REBOOT! Seek help from XDA!"
Help?
Edit: Followed the advice here http://forum.xda-developers.com/showthread.php?p=14936635 and s-off worked properly this time. Hopefully my DHD won't brick on reboot. Could super user be the problem? it never asks me for permissions or anything, all I have is an icon and a blank screen when i open the app.
Edit2: Rom manager took three attempts to install correctly. Still the same result "An error occurred while attempting to run privileged commands!"
FML

lemonpartyz said:
I managed to install visionary with your method, however when running Eng-S I encountered the error "Bootloader corrupt, DO NOT REBOOT! Seek help from XDA!"
Help?
Edit: Followed the advice here http://forum.xda-developers.com/showthread.php?p=14936635 and s-off worked properly this time. Hopefully my DHD won't brick on reboot. Could super user be the problem? it never asks me for permissions or anything, all I have is an icon and a blank screen when i open the app.
Edit2: Rom manager took three attempts to install correctly. Still the same result "An error occurred while attempting to run privileged commands!"
FML
Click to expand...
Click to collapse
looks like the superuser application isnt running properly.
I would use the 1.32 ruu (not the pd98img.zip off the sd) and then from a fresh install (without resoring any data other than google account to visit the market)
run through the visionary, s-off tool, eng-off tool, and then reboot again, then install rom manager from the market, run it, it should ask you for permission and may hang for a second, and then say you have about 5 seconds to allow root permissions.
Then install rom's away. if you're not into making seperate rom specific app folders on your sd card, google JSL Er3BuS. its a sense 3 rom without the extra scripts.

How do I install the 1.32 RUU if I can't install it from the SD card?
Thanks!

lemonpartyz said:
How do I install the 1.32 RUU if I can't install it from the SD card?
Thanks!
Click to expand...
Click to collapse
It is very easy mate,
1. Download the RUU of your choice from http://shipped-roms.com/index.php?category=android&model=Ace
2. Put your phone in charge mode only with USB debug on.
3. Make sure you have HTC Sync installed on your PC, and close HTC Sync application from your system bar in windows (make sure that HTC Sync is not running as all you need is the driver)
4. Right click on the RUU file and select "Run as Administrator"
5. Connect your DHD by the USB cable to your PC.
6. Click some boxed and "next"s.
7. Waiting!
8. Profit!

I tried following the steps here http://forum.xda-developers.com/showthread.php?t=841890
But got the error "ERROR [120]: Low MAIN BATTERY POWER. When the battery is above 30%.
This is getting ridiculous lol
I'm sorry I'm such a bother.

naailalzuhir said:
It is very easy mate,
1. Download the RUU of your choice from http://shipped-roms.com/index.php?category=android&model=Ace
2. Put your phone in charge mode only with USB debug on.
3. Make sure you have HTC Sync installed on your PC, and close HTC Sync application from your system bar in windows (make sure that HTC Sync is not running as all you need is the driver)
4. Right click on the RUU file and select "Run as Administrator"
5. Connect your DHD by the USB cable to your PC.
6. Click some boxed and "next"s.
7. Waiting!
8. Profit!
Click to expand...
Click to collapse
Tried this, now the update process has taken 45 minutes.

Well, it took 5 hours to finish, but finish it finally did. Rom manager installed no problem, flashed no problem and I am in the process of installing cryogen. Thanks everyone for their help and kind words.
Fingers crossed cryogen works.
I'm going away for the weekend, but when I come back I'll update this thread with the full details of what went down so hopefully someone will be helped by my many many hours spent raging.
-Lemonpartyz

lemonpartyz said:
Well, it took 5 hours to finish, but finish it finally did. Rom manager installed no problem, flashed no problem and I am in the process of installing cryogen. Thanks everyone for their help.
Click to expand...
Click to collapse
Glad its sorted for you , and hoping it status that way...enjoy your custom roms setting your phone free
Look forward to your post letting us know how its going.
Sent from outer space on my DHD running beatmod gingersense v1.3