2nd Chance after USB issue, How to do it right?

[Guest PeBo75]

Hi there,

today i've got my second chance by returning my Desire with USB issue to the store for a refund (because they had no devices on stock for exchange). So i went straight to the next and got a new one (and paid 11EUR less than before :rolleyes: ). Now i'll give it another try but i'd like to document it as good as possible.

My starting situation is as follows:

• Out-of-the-Box HTC Desire A8181
  
• HBOOT 0.75
  
• Firmware 1.15.405.4 release-keys
  
• Radio 32.30.00.28U
  
  The goal should be somthing like this (maybe slightly modified)
  
  • Customized HTC Desire A8181 :D
    
  • HBOOT 0.75 (just in case this could be important for later downgrades if needed)
    
  • MoDaCo Custom ROM r3
    
  • Apps2SD+
    
  • Radio 32.36.00.28U (because of a UMTS issue with 32.30.00.28U in O2 Germanys network)
    

  Together with the new device i bought a Kingston SD, 8GB, class4, which is already partitioned with 64mb swap, 1536mb ext2, converted to ext3 and the remaining space is FAT32. I've done this in my HTC Hero with Amon-RAs Custom Recovery to avoid doing it in one more recovery session on the Desire.

  Last time i used Rooting Guide r3 via testimage and rootedupdate.zip to root it and later on i installed a kitchen MCR r2 via recovery. My Desire got USB disabled when i tried to flash a kitchen MCR r3 via recovery. All was done on a Windows7/32 machine.

  This time i would like to take as much of the risk out of the whole process as possible. That's why i'm currently downloading the r3 Tiny Core Linux image to use this for rooting and recovery. Also i will modify the step2-linux.sh or recovery-linux.sh to include the "nohup" when calling the custom recovery.

  Anyway, i still have some concerns about the whole thing and so i'd like to know the shortest way from start to finish without flashing/restarting recovery too often. So i have some questions left at this point.

  1. Is it possible to skip the rootedupdate.zip and to replace this directly by the MCR r3 zip file? As i understood the rootedupdate.zip is a stock ROM but rooted as the MCR images are too. So it seems to make sense not to flash rootedupdate.zip, then re-enter recovery to flash another rooted ROM again. Am i right here?

  2. What is the best way to include the Radio on the first flash process? Is it safe to flash both files in one recovery session? Unfortunately the Radio is no longer an option within the kitchen itself to be included in the MCR. Is there a good reason not to offer this?

  Currently i have a kind of a ToDo list as follows:

  [*]prepare TCL r3 CD for rooting and entering custom recovery

  [*]prepare and use SDs FAT32 part with MCR r3 and Radio zip file

  [*]modify step2/recovery with nohup

  [*]in recovery flash MCR r3 kitchen ROM

  [*]thereafter flash Radio update in same session

  [*]be very very happy with your personal HTC Desire, MCRr3, Apps2SD+ and Radio

  [*]find out what brand of beer Paul likes the most to donate some of them :(

  Any advices from the community on this would be highly appreciated!

[Guest afiorillo]

[...] find out what brand of beer Paul likes the most to donate some of them :rolleyes: [...]

That's a thing I'd like to know as well, mate. :D

By the way, you're proving some braveness in doing this second try, and you deserve all our attention and gratitude.

I don't think there'll be any issue in flashing the last ROM and the radio one in sequence: just remember to issue a "Reboot now" command just after that, as the radio installs itself during the next explicit reboot.

Also, I guess you can safely swap rootedupdate.zip with MCR r3 but I'd like to ear it from Paul' mouth.

Good luck!

[Guest EddyOS]

Number 2 is something I wanna know as I'm looking to include it in an MCRr3 build but I'm guessing it's not as simple as stick in the ZIP and re-sign it!

[Guest jdouce]

id use r5

[Guest PeBo75]

By the way, you're proving some braveness in doing this second try, and you deserve all our attention and gratitude.

I was at the store on Saturday for the return, they agreed but i forgot the charger in my wall socket! Yesterday, in addition, was a holiday in germany so i had to wait some days with my "brick" and got used to my Hero again. Maybe this takes some of the fear :rolleyes:

I don't think there'll be any issue in flashing the last ROM and the radio one in sequence: just remember to issue a "Reboot now" command just after that, as the radio installs itself during the next explicit reboot.

Also, I guess you can safely swap rootedupdate.zip with MCR r3 but I'd like to ear it from Paul' mouth.

Of course i'll leave recovery via Reboot menu option, that's what i did all the time before.

Good luck!

Thanks mate!

id use r5

Unfortunately i don't know of a TCL image with r5 included. But as i remember from following this threads the last weeks the difference between r3 and r4 was added support for HBOOT 0.80 and from r4 to r5 was the "nohup" modification. So, for my HBOOT 0.75 and with manually added nohup it should be fine, right?

[Guest afiorillo]

[...]

Also, I guess you can safely swap rootedupdate.zip with MCR r3 but I'd like to ear it from Paul' mouth.

[...]

Well, seems that Paul has spoken. :rolleyes:

Edited May 25, 2010 by afiorillo

[Guest PeBo75]

:rolleyes:

[Guest PeBo75]

Ohh YES, i'm back on MCR r3 with Radio update and Apps2SD+ working.

When connecting my phone to the PC running TCL i was a little bit in doubt if i should continue but then i recalled the one thing from Paul:

Pre-requisites

In order to complete this guide, you need the following...

• ...
  
• balls of steel (actually, I just made that up) :(
  

Sometimes even a joke can come true... :D

However, i did it and it was a good choice to do so. The phone is running quite good and right now i'm reinstalling most of my Apps. I thought about restoring a Titanium Backup but i didn't want to have weird things happening because the backup was from another phone. So, as all this mentioned in this thread, i started from scratch with a very clean installation.

Rooting and flashing went through very stable, no flickering at all and after flashing MCR r3 and Radio in one recovery session the phone rebooted 2 times only but with a good delay on the "quietly brilliant" screen on the second reboot. Then it came up with PIN pad and a notification bar showing that it's preparing SD card for use. This 2 seconds notification made me quite happy :(

Now i will leave it as is until some news about USB issue and rooting/recovery process itself. This is mainly because even balls of steel will get some scratches if you hit them with a (USB) brick! :rolleyes:

Thank you very much Paul for all your work on this! Thanks also to the nice community here which is a great place to get new informations and shared experience!

[Guest myth1001]

Ohh YES, i'm back on MCR r3 with Radio update and Apps2SD+ working.

When connecting my phone to the PC running TCL i was a little bit in doubt if i should continue but then i recalled the one thing from Paul:

Sometimes even a joke can come true... :D

However, i did it and it was a good choice to do so. The phone is running quite good and right now i'm reinstalling most of my Apps. I thought about restoring a Titanium Backup but i didn't want to have weird things happening because the backup was from another phone. So, as all this mentioned in this thread, i started from scratch with a very clean installation.

Rooting and flashing went through very stable, no flickering at all and after flashing MCR r3 and Radio in one recovery session the phone rebooted 2 times only but with a good delay on the "quietly brilliant" screen on the second reboot. Then it came up with PIN pad and a notification bar showing that it's preparing SD card for use. This 2 seconds notification made me quite happy :(

Now i will leave it as is until some news about USB issue and rooting/recovery process itself. This is mainly because even balls of steel will get some scratches if you hit them with a (USB) brick! :rolleyes:

Thank you very much Paul for all your work on this! Thanks also to the nice community here which is a great place to get new informations and shared experience!

Cool. Great to hear that you made it! :(