14/Jun r6 riskfreeroot - HTC Desire rooting guide - now with HBOOT 0.80 and OS to 1.21 support

[Guest vib_]

r5 now online... this version no longer depends on the USB cable remaining connected to stop recovery exiting... MUCH safer! :rolleyes:

Paul, you remember about HTC Legend ? Issue with recovery and USB is not only Desire

[Guest Ajthescot]

im all good now thanks how do i upgrade the radio as info is a little vague

[Guest viper_campbell]

r5 now online... this version no longer depends on the USB cable remaining connected to stop recovery exiting... MUCH safer! :rolleyes:

P

Is there any chance of getting a download which is just the modified/added files etc?!?! Just means then we dont have to keep downloading the whole thing with the testimage and rooted update...

Thanks

[Guest afiorillo]

thanks sorry for being a pest but in the wipe option it only has .

wipe data/factory settings

wipe cache

wipesd;ext partion

wipebattery stats

wipe rotate settings

i dont seen. Select the 'wipe' option, then select the option to apply an update zip from sdcard, and select 'rootedupdate.zip'.

When nothing, then too much! :( I advised many times to follow the guides with the brain almost completely switched off (it's safer than making assumptions), but not switched off at all: «Select the 'wipe' option, then select the option to apply...» doesn't imply that the second options is under the first one' menu.

You've to enter the Wipe menu, wipe all the wipeable, then turn back one step and only at that point look for the 'Apply an update zip from sdcard' command.

Moving along menus never hurts anyone, so feel free to explore! Er... I said 'explore', not 'click wherever a click is possible' :D

Please don't take this as too much irony on you personally. :rolleyes:

[Guest Need_A_Username]

I keep thinking you've some kind of USB issue with your PC and/or cable: with a steady (software and hardware) USB connection the recovery console works with no glitches.

For safety purposes I urge you to edit the very last line in your recovery-*.* script files by adding the word 'nohup' (without hypens) between the words 'shell' and 'recovery': this will make the recovery console execution independent from the USB link.

Hmm doesn't sound good if I read your comment :rolleyes: Maybe a radio update would help? I am now on MCR r3 but still with radio 32.30.00.28U_4.05.00.11

And do you mean this script?

#!/bin/sh

echo Desire Recovery Mode

echo

echo Pushing required files to device...

echo

sudo ./adb-linux push files /

sudo ./adb-linux shell busybox --install /sbin

echo

sudo ./adb-linux shell /sbin/recovery &

And where exactly do I have to put it then?

Oh and about the r5 release, how do I update or whatever, should I just do all the steps again from the root process? :D

Thx for your help!

EDIT: damn, reading the post above me, I only wiped the data partition, thought I only had to wipe that one as it's always the data one when flashing roms and stuff :(

Edited May 24, 2010 by Need_A_Username

[Guest afiorillo]

Is there any chance of getting a download which is just the modified/added files etc?!?! Just means then we dont have to keep downloading the whole thing with the testimage and rooted update...

Thanks

Just read post #1882 in this thread to "patch" r4 to r5. :rolleyes:

[Guest anishnair]

r5 now online... this version no longer depends on the USB cable remaining connected to stop recovery exiting... MUCH safer! :rolleyes:

P

Mhh.. What about us who already have USB bricked phones?

[Guest viper_campbell]

Just read post #1882 in this thread to "patch" r4 to r5. :rolleyes:

Thanks, re-read and realised is was only 1 edit that needed doing, for some reason i thought there was alot more... it monday morning!!! haha!!

So the windows recovery text should now be:

echo Desire Recovery Mode

echo.

echo Pushing required files to device...

echo.

adb-windows.exe push files /

adb-windows.exe shell busybox --install /sbin

echo.

adb-windows.exe shell nohup /sbin/recovery &

Edited May 24, 2010 by viper_campbell

[Guest nerdo]

r5 now online... this version no longer depends on the USB cable remaining connected to stop recovery exiting... MUCH safer! :D

P

Thanks mate for this one, I guess it is safer against "sudden excitement clumsy movements" :rolleyes:

Waiting for rest of limitations to be sorted out :(

[Guest afiorillo]

You mean this script?

#!/bin/sh

echo Desire Recovery Mode

echo

echo Pushing required files to device...

echo

sudo ./adb-linux push files /

sudo ./adb-linux shell busybox --install /sbin

echo

sudo ./adb-linux shell /sbin/recovery &

And where exactly do I have to put it then? Oh and about the r5 release, how do I update or whatever, should I just do all the steps again from the root process? :rolleyes:

The last line should read:

sudo ./adb-linux shell nohup /sbin/recovery &

[Guest Aphax]

Thanks mate for this one, I guess it is safer against "sudden excitement clumsy movements" :rolleyes:

Waiting for rest of limitations to be sorted out :D

I wonder how much of a difference this makes with regard to the USB 'brick' problem. Someone just posted in the USB issue thread how he managed to break his USB while using 'nohup'; http://android.modaco.com/content-page/307...a2sd/page/680/#

[Guest Aphax]

When nothing, then too much! :rolleyes: I advised many times to follow the guides with the brain almost completely switched off (it's safer than making assumptions), but not switched off at all: «Select the 'wipe' option, then select the option to apply...» doesn't imply that the second options is under the first one' menu.

That's actually exactly what I thought it implied, and it caught me too. I really think it would be helpful if this particular instruction would be made a bit more.. explicit :/ I also asked for clarification in this thread and was actually told I only needed to pick the first option in the wipe menu, was that incorrect?

[Guest TheScrub]

Hi everyone,

I'm having similar issues to some of the other people here but i've yet to find a solution to my problem.

Step 1 completes without error after the scripts second attempt. Step 2 just can't seem to connect to the device, I don't know what's going wrong.

After Step 1 I take out the battery, swap the cards and enter the recovery menu option and run step 2 but it never works, any ideas?

NVM, was using a usb which it didn't seem to like

[Guest Paul]

Paul, you remember about HTC Legend ? Issue with recovery and USB is not only Desire

Yes, updating that now too! :rolleyes:

P

[Guest Paul]

Ah yes afiorillo, I couldn't remember who it was gave me the heads up on that command, THANKS! :rolleyes:

This isn't the 'safer method' i've been talking about, that's still coming, but this is a lot better, heh...

P

[Guest Paul]

Mhh.. What about us who already have USB bricked phones?

I'm still trying working on that, primarily with my HTC contacts...

P

[Guest Need_A_Username]

The USB bricking, does it happen randomly, or does it happen when you do something wrong? :s Cause I've read a lot about people having the problem, but not how it happend :s And seeing my usb connection being weird sometimes, it kinda frightens me :D :rolleyes:

[Guest Need_A_Username]

The last line should read:

sudo ./adb-linux shell nohup /sbin/recovery &

You are the man!

Tried entering recovery through windows again, worked like a breeze this time. Thx man!! :rolleyes:

[Guest afiorillo]

Ah yes afiorillo, I couldn't remember who it was gave me the heads up on that command, THANKS! :rolleyes:

I'm not the guy behind that trick, I don't remember who is... I'll do some search about that. :D

**EDIT** Got it: http://android.modaco.com/content-page/307...0/#entry1282423

This isn't the 'safer method' i've been talking about, that's still coming, but this is a lot better, heh...

P

Ah! Great news, as usual. :( Thank you.

Edited May 24, 2010 by afiorillo

[Guest anishnair]

I'm still trying working on that, primarily with my HTC contacts...

P

Thanks Paul

[Guest Ajthescot]

When nothing, then too much! :( I advised many times to follow the guides with the brain almost completely switched off (it's safer than making assumptions), but not switched off at all: «Select the 'wipe' option, then select the option to apply...» doesn't imply that the second options is under the first one' menu.

You've to enter the Wipe menu, wipe all the wipeable, then turn back one step and only at that point look for the 'Apply an update zip from sdcard' command.

Moving along menus never hurts anyone, so feel free to explore! Er... I said 'explore', not 'click wherever a click is possible' :D

Please don't take this as too much irony on you personally. :rolleyes:

thanks

it didnt say in the how to that pressing the volume down button took you back a screen.

[Guest kewell79]

- If you have a bootloader version 0.75.xxxx or below AND a current ROM of 1.15.xxx.x or below - DOWNLOAD (MediaFire) / MIRROR (ROMraid / CoBlitz) - MD5: 4845a38155e6a257a7de3fe0557ae34c

- ONLY if the above download is not suitable - if you have a bootloader version 0.80.xxxx or below AND a current ROM of 1.21.xxx.x or below - DOWNLOAD (MediaFire) / MIRROR (ROMraid / CoBlitz) - MD5: eb1dfb6fa93c592b6ccf0cabefcd2dec

when im using Modaco R3 now with 1.21, should i now choose the second zip when i wanna try another rom?

i had 0.75 and 1.15 before i rooted my phone

[Guest Paul]

I'm not the guy behind that trick, I don't remember who is... I'll do some search about that. :rolleyes:

**EDIT** Got it: http://android.modaco.com/content-page/307...0/#entry1282423

Ah! Great news, as usual. :D Thank you.

Heh, thanks, I think someone actually IM'd or IRC'd me, I forget. :(

P

[Guest Need_A_Username]

when im using Modaco R3 now with 1.21, should i now choose the second zip when i wanna try another rom?

i had 0.75 and 1.15 before i rooted my phone

Good question! I would guess you should take the second zip yes, but I'm not sure :rolleyes:

[Guest aluc]

Hi Paul,

in my case step 2 say's "no device found" what can this be?