Guest Paul Posted May 6, 2010 Report Share Posted May 6, 2010 I have new download locations online for the root files... feedback appreciated! :P P Link to comment Share on other sites More sharing options...
Guest andyokane Posted May 6, 2010 Report Share Posted May 6, 2010 Can you please tell me where can I find the r3 instructions? Thanks! I would also like a link to the R3 method please, I have the files! Link to comment Share on other sites More sharing options...
Guest SiX-P4cK Posted May 6, 2010 Report Share Posted May 6, 2010 I would also like a link to the R3 method please, I have the files! here Link to comment Share on other sites More sharing options...
Guest pdageek13 Posted May 6, 2010 Report Share Posted May 6, 2010 (edited) "When this step has completed, using the optical trackball, navigate to the 'BOOTLOADER' and then 'RECOVERY' option on the menu, using the volume buttons to move and the power button to select." NO -> using volume and power buttons ! anyway thanksssssssssss it worked great Edited May 6, 2010 by pdageek13 Link to comment Share on other sites More sharing options...
Guest Paul Posted May 6, 2010 Report Share Posted May 6, 2010 Fixed. :P P Link to comment Share on other sites More sharing options...
Guest omesanni Posted May 6, 2010 Report Share Posted May 6, 2010 Paul u said you wuld put a video up on how to root the htc desire but u still haven't done it and u've been sayin it 4 quite a while now. When is d video coming out I have a question, after rootin htc desire, does the generic rom still have htc sense with it or is dat stripped? Link to comment Share on other sites More sharing options...
Guest aslocum Posted May 6, 2010 Report Share Posted May 6, 2010 i get this error :P < waiting for device > sending 'zip' (137446 KB)... OKAY writing 'zip'... INFOadopting the signature contained in this image... INFOsignature checking... INFOzip header checking... INFOzip info parsing... INFOchecking model ID... INFOchecking custom ID... INFOchecking main version... INFOstart image[hboot] unzipping for pre-update check... INFOstart image[hboot] flushing... INFO[RUU]WP,hboot,0 INFO[RUU]WP,hboot,100 INFOstart image[radio] unzipping for pre-update... INFOstart image[radio] flushing... INFO[RUU]WP,radio,0 INFO[RUU]WP,radio,6 INFO[RUU]WP,radio,14 INFO[RUU]WP,radio,19 INFO[RUU]WP,radio,27 INFO[RUU]WP,radio,36 INFO[RUU]WP,radio,44 INFO[RUU]WP,radio,51 INFO[RUU]WP,radio,59 INFO[RUU]WP,radio,100 FAILED (remote: 90 hboot pre-update! please flush image again immediately) sending 'zip' (137446 KB)... FAILED (command write failed (No such file or direc tory)) i have a german t-mobile branded with 0.75 Link to comment Share on other sites More sharing options...
Guest Aelred Posted May 6, 2010 Report Share Posted May 6, 2010 @aslocum: I had that same error trying to root on Win 7 x64 but once I changed to Ubuntu x86 it worked just fine :P Link to comment Share on other sites More sharing options...
Guest bbawden Posted May 6, 2010 Report Share Posted May 6, 2010 (edited) ... select the option to apply an update zip from sdcard, and select 'rootedupdate.zip'. This will take a little while, so go make a nice cup of tea... How long is "a little while" Mine has been sitting at "verifying update package" for 10 mins, and the progress bar behind the text does not seem to have moved at all. How long should I leave it? (edited for spelling) Edited May 6, 2010 by bbawden Link to comment Share on other sites More sharing options...
Guest aslocum Posted May 6, 2010 Report Share Posted May 6, 2010 Have tried it with win7 32bit. Will try with my macbook later. @aslocum: I had that same error trying to root on Win 7 x64 but once I changed to Ubuntu x86 it worked just fine :P Link to comment Share on other sites More sharing options...
Guest coercri Posted May 6, 2010 Report Share Posted May 6, 2010 i get this error :P < waiting for device > sending 'zip' (137446 KB)... OKAY writing 'zip'... INFOadopting the signature contained in this image... INFOsignature checking... INFOzip header checking... INFOzip info parsing... INFOchecking model ID... INFOchecking custom ID... INFOchecking main version... INFOstart image[hboot] unzipping for pre-update check... INFOstart image[hboot] flushing... INFO[RUU]WP,hboot,0 INFO[RUU]WP,hboot,100 INFOstart image[radio] unzipping for pre-update... INFOstart image[radio] flushing... INFO[RUU]WP,radio,0 INFO[RUU]WP,radio,6 INFO[RUU]WP,radio,14 INFO[RUU]WP,radio,19 INFO[RUU]WP,radio,27 INFO[RUU]WP,radio,36 INFO[RUU]WP,radio,44 INFO[RUU]WP,radio,51 INFO[RUU]WP,radio,59 INFO[RUU]WP,radio,100 FAILED (remote: 90 hboot pre-update! please flush image again immediately) sending 'zip' (137446 KB)... FAILED (command write failed (No such file or direc tory)) i have a german t-mobile branded with 0.75 I had that, I just went back to the last command I typed and did it again - OK the next time. Link to comment Share on other sites More sharing options...
Guest chai-kung Posted May 6, 2010 Report Share Posted May 6, 2010 Help me please... I have this problem. I try on win7 64bit and it didn't work then I switch to Ubuntu and still cannot root (using ubuntu-10.04-desktop-i386.iso boot from wmware 7) From win7 64bit cmd step1-window Desire Root Step 1 Erasing cache and rebooting in RUU mode... erasing 'cache'... OKAY ... OKAY About to start flash... < waiting for device > sending 'zip' (137446 KB)... OKAY writing 'zip'... INFOadopting the signature cont INFOsignature checking... INFOzip header checking... INFOzip info parsing... INFOchecking model ID... INFOchecking custom ID... INFOchecking main version... INFOstart image[hboot] unzipping for pre-update INFOstart image[hboot] flushing... INFO[RUU]WP,hboot,0 INFO[RUU]WP,hboot,100 INFOstart image[radio] unzipping for pre-update. INFOstart image[radio] flushing... INFO[RUU]WP,radio,0 INFO[RUU]WP,radio,6 INFO[RUU]WP,radio,14 INFO[RUU]WP,radio,19 INFO[RUU]WP,radio,27 INFO[RUU]WP,radio,36 INFO[RUU]WP,radio,44 INFO[RUU]WP,radio,51 INFO[RUU]WP,radio,59 INFO[RUU]WP,radio,100 FAILED (remote: 90 hboot pre-update! please flus sending 'zip' (137446 KB)... FAILED (command wri tory)) Rebooting to bootloader... < waiting for device > rebooting into bootloader... OKAY Step 1 complete - now use the bootloader menu to To do this, press the power button, wait a few s and power button to select the RECOVERY option. Desktop\r4-desire-root> chai@ubuntu:~$ cd Desktop chai@ubuntu:~/Desktop$ cd root chai@ubuntu:~/Desktop/root$ ./step1-linux.sh Desire Root Step 1 Erasing cache and rebooting in RUU mode... [sudo] password for chai: erasing 'cache'... OKAY ... OKAY About to start flash... < waiting for device > sending 'zip' (137446 KB)... OKAY writing 'zip'... INFOadopting the signature contained in this image... INFOsignature checking... INFOzip header checking... INFOzip info parsing... INFOstart image[hboot] unzipping for pre-update check... INFOstart image[hboot] flushing... INFO[RUU]WP,hboot,0 INFO[RUU]WP,hboot,100 INFOstart image[radio] unzipping for pre-update... INFOstart image[radio] flushing... INFO[RUU]WP,radio,0 INFO[RUU]WP,radio,6 INFO[RUU]WP,radio,14 INFO[RUU]WP,radio,19 INFO[RUU]WP,radio,27 INFO[RUU]WP,radio,36 INFO[RUU]WP,radio,44 INFO[RUU]WP,radio,51 INFO[RUU]WP,radio,59 INFO[RUU]WP,radio,100 FAILED (status read failed (Cannot send after transport endpoint shutdown)) < waiting for device > sending 'zip' (137446 KB)... OKAY writing 'zip'... INFOadopting the signature contained in this image... INFOsignature checking... INFOzip header checking... INFOzip info parsing... INFOstart image[boot] unzipping & flushing... INFO[RUU]UZ,boot,0 INFO[RUU]UZ,boot,40 INFO[RUU]UZ,boot,85 INFO[RUU]UZ,boot,100 INFO[RUU]WP,boot,0 INFO[RUU]WP,boot,45 INFO[RUU]WP,boot,90 INFO[RUU]WP,boot,100 INFOstart image[rcdata] unzipping & flushing... INFO[RUU]UZ,rcdata,0 INFO[RUU]WP,rcdata,0 INFO[RUU]WP,rcdata,100 INFOstart image[recovery] unzipping & flushing... INFO[RUU]UZ,recovery,0 INFO[RUU]UZ,recovery,24 INFO[RUU]UZ,recovery,44 INFO[RUU]UZ,recovery,65 INFO[RUU]UZ,recovery,93 INFO[RUU]UZ,recovery,100 INFO[RUU]WP,recovery,0 INFO[RUU]WP,recovery,22 INFO[RUU]WP,recovery,44 INFO[RUU]WP,recovery,67 INFO[RUU]WP,recovery,89 INFO[RUU]WP,recovery,100 INFOstart image[sp1] unzipping & flushing... INFO[RUU]UZ,sp1,0 INFO[RUU]UZ,sp1,100 INFO[RUU]WP,sp1,0 INFO[RUU]WP,sp1,100 INFOstart image[system] unzipping & flushing... INFO[RUU]UZ,system,0 INFO[RUU]UZ,system,3 INFO[RUU]UZ,system,7 INFO[RUU]UZ,system,12 INFO[RUU]UZ,system,16 INFO[RUU]UZ,system,20 INFO[RUU]UZ,system,25 INFO[RUU]UZ,system,29 INFO[RUU]UZ,system,33 INFO[RUU]UZ,system,37 INFO[RUU]UZ,system,41 INFO[RUU]UZ,system,45 INFO[RUU]UZ,system,50 INFO[RUU]UZ,system,54 INFO[RUU]UZ,system,58 INFO[RUU]UZ,system,62 INFO[RUU]UZ,system,66 INFO[RUU]WP,system,0 INFO[RUU]WP,system,66 INFO[RUU]UZ,system,66 INFO[RUU]UZ,system,68 INFO[RUU]UZ,system,74 INFO[RUU]UZ,system,76 INFO[RUU]UZ,system,78 INFO[RUU]UZ,system,80 INFO[RUU]UZ,system,83 INFO[RUU]UZ,system,85 INFO[RUU]UZ,system,87 INFO[RUU]UZ,system,89 INFO[RUU]UZ,system,91 INFO[RUU]UZ,system,93 INFO[RUU]UZ,system,96 INFO[RUU]UZ,system,98 INFO[RUU]UZ,system,100 INFO[RUU]WP,system,66 INFO[RUU]WP,system,68 INFO[RUU]WP,system,70 INFO[RUU]WP,system,72 INFO[RUU]WP,system,74 INFO[RUU]WP,system,76 INFO[RUU]WP,system,78 INFO[RUU]WP,system,80 INFO[RUU]WP,system,83 INFO[RUU]WP,system,85 INFO[RUU]WP,system,87 INFO[RUU]WP,system,89 INFO[RUU]WP,system,91 INFO[RUU]WP,system,94 INFO[RUU]WP,system,96 INFO[RUU]WP,system,98 INFO[RUU]WP,system,100 INFOstart image[userdata] unzipping & flushing... INFO[RUU]UZ,userdata,0 INFO[RUU]UZ,userdata,100 INFO[RUU]WP,userdata,0 INFO[RUU]WP,userdata,100 OKAY Rebooting to bootloader... rebooting into bootloader... FAILED (status read failed (Value too large for defined data type)) Step 1 complete - now use the bootloader menu to enter recovery mode. To do this, press the power button, wait a few seconds, then use the volume keys and power button to select the RECOVERY option. chai@ubuntu:~/Desktop/root$ ./step2-linux.sh Desire Root Step 2 Pushing required files to device... * daemon not running. starting it now * * daemon started successfully * error: device not found error: device not found Pushing update file to device sdcard - this may take a few minutes... error: device not found error: device not found Now wipe and apply rootedupdate.zip from the recovery image menu. chai@ubuntu:~/Desktop/root$ error: device not found ^C chai@ubuntu:~/Desktop/root$ Link to comment Share on other sites More sharing options...
Guest zaphyr Posted May 6, 2010 Report Share Posted May 6, 2010 (edited) i get this error :P < waiting for device > sending 'zip' (137446 KB)... OKAY writing 'zip'... INFOadopting the signature contained in this image... INFOsignature checking... INFOzip header checking... INFOzip info parsing... INFOchecking model ID... INFOchecking custom ID... INFOchecking main version... INFOstart image[hboot] unzipping for pre-update check... INFOstart image[hboot] flushing... INFO[RUU]WP,hboot,0 INFO[RUU]WP,hboot,100 INFOstart image[radio] unzipping for pre-update... INFOstart image[radio] flushing... INFO[RUU]WP,radio,0 INFO[RUU]WP,radio,6 INFO[RUU]WP,radio,14 INFO[RUU]WP,radio,19 INFO[RUU]WP,radio,27 INFO[RUU]WP,radio,36 INFO[RUU]WP,radio,44 INFO[RUU]WP,radio,51 INFO[RUU]WP,radio,59 INFO[RUU]WP,radio,100 FAILED (remote: 90 hboot pre-update! please flush image again immediately) sending 'zip' (137446 KB)... FAILED (command write failed (No such file or direc tory)) i have a german t-mobile branded with 0.75 I get the same, but I get to the end, and then a red triangle at the recovery screen. Win XP computer, 0.75 I tried with the tinycore cd as well, with the same result... :D Edited May 6, 2010 by zaphyr Link to comment Share on other sites More sharing options...
Guest bbawden Posted May 6, 2010 Report Share Posted May 6, 2010 How long is "a little while" Mine has been sitting at "verifying update package" for 10 mins, and the progress bar behind the text does not seem to have moved at all. How long should I leave it? (edited for spelling) Never mind - it worked after the 3rd or 4th attempt. Not sure what that was about. Link to comment Share on other sites More sharing options...
Guest jasup Posted May 6, 2010 Report Share Posted May 6, 2010 I keep having " Failure at line 5 symlink busybox system : xbin /[ :P :D tried to reflash many times Link to comment Share on other sites More sharing options...
Guest bbawden Posted May 6, 2010 Report Share Posted May 6, 2010 OK, it installed the rootedupdate OK. Now how to I boot into the menu, so I can apply the custom ROM zip? Thanks. Link to comment Share on other sites More sharing options...
Guest FatherD Posted May 6, 2010 Report Share Posted May 6, 2010 Hi Paul ... HELP! [*]In the terminal window, enter either 'step2-windows.bat', './step2-mac.sh' or './step2-linux.sh' as appropriate. I get to this part on my XP ... step2-windows.bat returns: Desire Root Step 2 Pushing required files to device... * daemon not running. starting it now on port 5037 * * daemon started successfully * error: device not found error: device not found Pushing update file to device sdcard - this may take a few minutes... error: device not found error: device not found Now wipe and apply rootedupdate.zip from the recovery image menu. error: device not found My phone is sitting with the red triangle / exclamation ... what went wrong? :P Link to comment Share on other sites More sharing options...
Guest potter97 Posted May 6, 2010 Report Share Posted May 6, 2010 (edited) Hi Paul ... HELP! I get to this part on my XP ... step2-windows.bat returns: Desire Root Step 2 Pushing required files to device... * daemon not running. starting it now on port 5037 * * daemon started successfully * error: device not found error: device not found Pushing update file to device sdcard - this may take a few minutes... error: device not found error: device not found Now wipe and apply rootedupdate.zip from the recovery image menu. error: device not found My phone is sitting with the red triangle / exclamation ... what went wrong? :P I'm sorry but are you retarded?? What do you think "error:device not found" means??????? Try making sure you htc is plugged in all the drivers are installed, htcsync installed, check you are not using any other extension usb leads, only use the back USB hub on Pc's, dont use any USB extension hubs at all, Finally check you actually have a connection via adb, by setting up the adb on your pc, guides are everyware for this. then check devices with "adb devices" Oh and you may want to actually read the thread as this has been answered over and over again. USE SEARCH FFS!!!! I mean i learnt all of this in a week when paul released it, but unlike many i actually read up a bit about it first instead of jumping in feet first without know what the hell im doing. Your trying to fly a plane without wings, AIN'T GONNA WORK! Do what most normal ppl do, RESEARCH its not hard, its all here...... You just need to pull your finger out and not rely on Paul to sort you out, the mans busy enough without spoon feeding people who just cant help themselves Edited May 6, 2010 by potter97 Link to comment Share on other sites More sharing options...
Guest aslocum Posted May 6, 2010 Report Share Posted May 6, 2010 FAILED (remote: 90 hboot pre-update! please flush image again immediately) sending 'zip' (137446 KB)... FAILED (command write failed (No such file or direc tory)) my error is gone. i had just tried another computer (my netbook, also running win7 32bit). all working fine now and rooted :P maybe some usb ports/chips are not good for flashing? Link to comment Share on other sites More sharing options...
Guest afiorillo Posted May 6, 2010 Report Share Posted May 6, 2010 [...] maybe some usb ports/chips are not good for flashing? Maybe messed up computers didn't help :P Link to comment Share on other sites More sharing options...
Guest jeckyllhavok Posted May 6, 2010 Report Share Posted May 6, 2010 Hi there, i got a problem with rooting one of the Desires: My Desire is a Non branded HTC One, i completed the root Process without any problems. Today i wanted to root the desire of a friend of mine, it's a software branded t-mobile one. I created the gold card and succesfully finished step 1 - in windows and in Linux. But at step 2 i always got the message "Device not found" The Bootloader Infos are the same as on mine: BRAVO UNKNOWN SHIP S-ON HBOOT-0.75.0000 MICROP-031d TOUCH PANEL-SYNT0101 RADIO-4.05.00.11 MAR 5 2010,21:12:15 If anyone had an idea .... THANKS Link to comment Share on other sites More sharing options...
Guest iom_jack Posted May 6, 2010 Report Share Posted May 6, 2010 is it okay to use in orange???? thank you paul. btw, any chance for unlocking? Link to comment Share on other sites More sharing options...
Guest mjaore Posted May 6, 2010 Report Share Posted May 6, 2010 is it okay to use in orange???? thank you paul. btw, any chance for unlocking? u have 2 look if u got bootloader 0.75! if u have it is possible... if u have 0.80... u'll have 2 wait until the new tutorial is out. Link to comment Share on other sites More sharing options...
Guest cschmitz Posted May 6, 2010 Report Share Posted May 6, 2010 @CSCHMITZ and others who are willing to help. Hello, thank you for the effort to answer my question. It seems you are the only one who are willing to help or willing to think about it. I am from the Netherlands and there are some things in your answer that I do not quite understand. Your talking about using a generic "unroot". How do I do that and where can I find a generic "unroot"? Also you are talking about Market Locale is not the problem but my bought content association. Whta do you mean by this? what is Locale and especially what is my bought content association. And the last advice of you is to do a clean new install+root. Can you tell mewhere to find a clean install. I already installed and rooted twice now. Both with first installing the testruu from Paul through windows and after that I installed app2sd, the one with the clean davik cache or something. Did I use the correct Rom (testruu.exe) or do I need to use a different one? Please help me again. I am stuck at this point. I had this market issue for a few minutes aswell, it self corrected itself when syncing. Right now, try to add a new google account to your phone, then delete the old one from it, then readd it, see if that fixes the market. If that doesnt work, go back to the very first ROM(http://android.modaco.com/content/htc-desire-desire-modaco-com/307683/howto-unroot-your-htc-desire/) and wipe the device properly. I would also very much recommend using linux to root etc, most issues seem to be related to windows drivers not found and people badword with a2sd without knowing it, so just eliminate these two. When you have a fresh new device setup, skip all account setups for good measure, add a different google account first, then see if the market is shown, then add your old one. Link to comment Share on other sites More sharing options...
Guest alpinux Posted May 6, 2010 Report Share Posted May 6, 2010 (edited) u have 2 look if u got bootloader 0.75! if u have it is possible... if u have 0.80... u'll have 2 wait until the new tutorial is out. Further more as i see it, the rootprocess isn't completly accomplished as we don't have access to /system (as paul wrote in his tutorial) on a normally booted desire. Thats the reason why some programs that require root don't work (e.g. adblock). In my eyes this makes the desire less interesting in matters of functionality compared to the nexus one, because we may never get write access to /system which causes a handicapped, still pretty awesome phone. Edited May 6, 2010 by alpinux Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now