Solution to Root Locked Rogers HTC Dream!

Huge Update!

Since writing this, the DroidX team has come up with an awesome rooting method sans JTAG. The bonus is it seems to work on all Android phones, not just the DroidX.

You’ll need:

A great guide can be found at http://androidheadlines.com/2010/07/guide-on-how-to-root-you-htc-dream-to-2-1.html for the steps to follow, or hop on over to the XDA Developers thread for up to the minute information and help.

My personal choice is the Android 2.1 ROM as it runs pretty smooth and you get all the goodies that most other phones still crave πŸ™‚ If you’re adventurous the 6.0.0RC1 ROM is out for Android 2.2 but when I installed the image it had quite a few issues still with performance. You can install any custom ROM once you’ve rooted the phone and a guide on how to do that is found at The CyanogenMod Wiki. Happy hacking!

Kept here for those who are curious enough
There is finally hope at last for all those people that were hurt by Rogers Wireless a month ago. Rogers released a new firmware for the HTC Dream for “911 emergency services” problems. It wasn’t a major problem with the phone and more a reason to stop people from rooting their phones on their network. We won’t get into that and their shady tactics for locking customers in and their horrible customer service, but we will mention that there is hope for all those locked phones!

A new possible workaround has come out that involves connecting to the phone via JTAG to access the debugger of the ARM firmware loader to load a different ROM than what has been deemed the “Perfect SPL” by modders. This new workaround will allow for a change in the memory address used for loading code so that the user can flash in their own Radio, SPL and ultimately Android image. Since this is a hardware hack, it will be nearly impossible for Rogers to make a software fix for this, and will allow people with bricked HTC Dreams and Magics to be able to revive their phones better than ever. A great job to everyone who was working on the team to find a software or hardware hole, and I’m glad that someone did at least (while decompiling I had found nothing software wise, I was getting quite worried).

For those who are looking for a link, check out:

for more info on how the JTAG is constructed and what software is needed. Please be careful though! This is still very early in the review and development stage and there are many thing that are left to be uncovered. Proceed at your own risk, but if you’re phone is already bricked, you have nothing to lose! So enjoy your now FREE Android phone, as was the original spirit of the device before Rogers got their hands on it! If you find anything new out or any mistakes please let me know, and if you have a success story please share it with everyone!

NVIDIA Driver Version 196.75 Recalled!

NVIDIA has issued a recall for the driver version 196.75 released earlier this week (March 2nd) due to reported problems causing the GPU fan to stop working, causing the GPU to run without cooling and eventually burn out.

Activision Blizzard first made note of the problem when its support division began receiving complaints about malfunctioning and overheating video cards. Beta testers for their upcoming game Starcraft II also made note of the issue reporting lower frame rates and game play issues. Blizzard issued this statement to all their players:

β€œWe’re getting reports where users are getting intermittent low FPS after installing these drivers. It seems that it is related to the fan control included in these drivers not working correctly and is causing the video card to overheat on 3D applications. This will affect Warcraft 3, World of Warcraft and StarCraft 2 Beta. Please uninstall the drivers and revert back to the older ones.”

NVIDIA has since pulled the driver from their website, rolling back to the previous stable 196.21 WHQL certified driver and have requested that users downgrade to the 196.21 version of the driver.

β€œWe are aware that some customers have reported fan speed issues with the latest 196.75 WHQL drivers on NVIDIA.com. Until we can verify and root cause this issue, we recommend that customers stay with, or return to 196.21 WHQL drivers. Release 196.75 drivers have been temporarily removed from our Web site in the meantime.”

It is recommended that if you have done a driver update recently that you check if you are running version 196.75 of the and to immediately roll back to an earlier stable version of the driver, even if you haven’t noticed any issues, until NVIDIA has resolved the failure report. Please contact NVIDIA to report graphics card failures, as it is a driver issue and not a game issue.

If you are looking for the rollback version of the driver you can find them below:

Windows XP: http://www.nvidia.com/object/winxp_196.21_whql.html
Windows XP 64-bit: http://www.nvidia.com/object/winxp64_196.21_whql.html
Windows Vista/7 32-bit: http://www.nvidia.com/object/win7_winvista_32bit_196.21_whql.html
Windows Vista/7 64-bit: http://www.nvidia.com/object/win7_winvista_64bit_196.21_whql.html