Here’s a quick tip on how to look up a saved wifi password on your Android handset. Let’s say you need to flash a new rom but you don’t have a password written down for a wifi access point you frequently use. Use any file explorer on your Android handset and navigate to the /data/wifi directory and view theĀ bcm_supp.conf file. This is just a basic text file that contains all your wifi access points and passwords that you’ve used previously.

Make a backup of it or simply write down the password you need, enjoy!

 

For some HTC Evo 3d users with HBOOT version at 1.5, flashing custom kernels is pretty much impossible with your standard recovery install. Due to updating the HBOOT to 1.5, you are forced to use HTC”s bootloader unlock method which opens up custom rom installs, but locks down the any boot partition modification. In layman’s terms, this prohibits all kernel installs.

However, there is a way to get around this. The below steps will assume you have ADB and Fastboot tools installed and ready to go. If you do not, please download it at the bottom of this post. This also assumes you know a little on how to use ADB and can follow basic command line directions.

I used the below method to flash Android Revolution successfully on a CDMA Evo 3d with HBOOT 1.5 — rom and kernel.

Note: this should be fairly painless, but problems always have a chance of occuring. You are on your own if you brick your device.

  1. Set up ADB/Fastboot tools and make sure the command adb devices shows your device. If this is your first time, grab and install the fastboot drivers from here.
  2. Ensure your Evo 3d is on HBOOT 1.5 (volume down + power from a powered off phone) and has been unlocked via HTC’s unlock method.
  3. Time to flash your desired recovery. I prefer TWRP, which can be downloaded below. Place this recovery.img within the directory that ADB and fastboot tools reside in.
  4. Boot your phone into the bootloader (volume down + power).
  5. Select fastboot.
  6. Connect your USB and issue the command fastboot flash recovery recovery.img. This will flash the TWRP recovery onto your phone. Do not reboot or exit out of the fastboot screen.
  7. We will now fastboot into the recovery instead of using the two finger salute. HTC will give write permissions thru the recovery to write to the boot partition via fastboot. Issue the command fastboot boot recovery.img. This will boot your Evo 3D into the TWRP recovery.
  8. With your favorite rom or kernel on your sdcard, you can now successfully flash them thru TWRP.

  Android ADB and Fastboot tools (13.2 MiB, 39 hits)
You do not have permission to download this file.

  TWRP Recovery for CDMA Evo 3D (4.9 MiB, 23 hits)
You do not have permission to download this file.

 

A lot of custom rom users on the Sensation 4G have noticed screen of death occurrences and reboots/lockups. A developer on XDA has dug deep and found that the HTC RUU (Rom Upgrade Utility) and OTA (Over The Air) updates differ in that a rpm image located on the RUU is not present on the OTA release. By not flashing this rpm image to the correct partition, the odd problems people have been facing with custom roms have been creeping up. From initial reports, it seems this is working for the people who have flashed the rpm.img file correctly.

I’ve actually never had the screen of death issue, but I prefer to have the correct rpm flashed anyway.

The link to the XDA thread contains a bootloader zip that reflashes your recovery and bootloader as well as the rpm.img in question. I prefer to flash the rpm file via fastboot USB since I don’t need to update or fuss with my recovery and whatnot. I also find it safer to do it via fastboot instead of a bootloader flash file.

If you already have the Android SDK installed and working, the fastboot tool is located in the tools directory. If you don’t have the SDK installed, download the zip below which contains the drivers you will need as well as the adb and fastboot executables for Windows. There is no need to install the entire SDK if all you want to use are the adb and fastboot tools.

** Flashing anything is your responsibility. What works for others may not work for you. Although this has worked fine for me, I am not responsible for what you may possibly do to your device.

  1. Download the ADB/Fastboot zip located in this post. You will need to be a registered user to download any files from DH.
  2. Open a command prompt to where you unzip’d the adb/fastboot file you just downloaded.
  3. Install the HTC drivers if you do not have that already.
  4. Disable fastboot under Settings->Power and then power down.
  5. Hold down volume – and then hit the power button.
  6. You are now in the bootloader (white) screen. Select fastboot from the options and hit the power button.
  7. Connect your USB cable from your phone to your computer.
  8. The fastboot banner should change to fastboot usb. If you don’t see this, stop and check your driver install.
  9. Download the rpm.img zip attached to this post and place it in the same directory as where you unzip’d the adb/fastboot zip. The md5sum for this file when unzip’d is 59a52ec272c0dbdaf262f1f32e543b4c. If your md5 does not match, DO NOT FLASH. Please redownload and try again.
  10. Issue the command “fastboot devices” and make sure your device shows up.
  11. If it does, issue the command “fastboot flash rpm rpm.img“. This should take all of 5 seconds to flash over to your handset.
  12. Once it flashes and you get the OK, unplug the USB cable and reboot the device via the menu and your power button.
  13. Enjoy and be free of the screen of death.

  Android ADB and Fastboot tools (13.2 MiB, 39 hits)
You do not have permission to download this file.

  Sensation 4G rpm.img file (57.5 KiB, 10 hits)
You do not have permission to download this file.

 


I just started developing this odd creaking noise near the bottom and sides of my S4G. Even with a Seidio Active case wrapped around it, the creaking can be felt and heard when hitting the bottom buttons.

The fix is pretty easy. You just need to decrease the amount of movement the back cover has.

I had some .010 mil fiber (fish) paper laying around so I cut a small square that covers the sim card and microsd card area. You can probably use something else, but hey, why not use some insulated paper if you have it.

Lay the paper on top of the area and then slowly place the back cover back on. No holes are in that area above the sim and microsd, so no worries there. You should see an immediate improvement.

 

The official LG Gingerbread update is finally out for the LG/T-Mobile G2x! You will need to grab the LG Mobile Software updater. Please note that this will break any root access you already have.

So in typical DroidHype fashion, here is a link to grab a ClockworkMod flashable pre-rooted zip of the new 2.3.3 update.

Good job LG and T-Mobile for finally pushing this out!

Via [XDA]

*Update* – this appears to be LG’s release and not an official T-Mobile release. Once T-Mobile finalizes their testing, this will get signed and the over-the-air (OTA) will be sent out. Either way, this is good in LG’s eyes which means it should be good for most!

*Update* – LG’s release is indeed the same as the T-Mobile release. Flash away folks!

 

So from some insane crackflashing I did recently on my first G2x unit, I found out it suffered from some similar problems that my Droid Incredible experienced. On certain roms or kernels, it would just lock up the G2x on the initial boot screen. Not only that, it also heated up the CPU immensely in a short span of time.

Here’s what I attempted to flash that worked:

  • Eaglesblood 1.0.4 Froyo and GB Rom
  • Dark&Sinister 1.1 Froyo Rom
  • Ultimate Rom Froyo Rom
  • CM7 Nightlies Rom
  • Trinity 15 ext3 and ext4 kernels for EB/DS Froyo

Missing from that list is Faux123′s AOSP and CM7 based rom and kernel. As much as I would have loved to use it, I just couldn’t. Now before someone points, laughs and cries user error, I’ve been doing this for quite a while. I know how this works and what needs to get done to make it work. I’ve done the wipes, I’ve done the nandroid restores back to ext3, I’ve done everything. The end result is always a locked up LG boot screen and a blazing hot backside.

So how did I fix it?

Simple, grabbed a new G2x unit and test it. Within 10 minutes, I had Faux’s AOSP rom and Cm7 based kernel loaded and booted. So did my G2x have the same kind of bad memory blocks causing problems? Who knows at this point, but what I do know is I’m now using one of the smoothest rom and kernel combinations for the G2x.

 


It looks like all the freezes, lock ups, reboots and hot batteries on the T-mobile G2x are caused by a bad batch of batteries? From this forum post on the T-mobile customer forums, many are reporting that getting a newer replacement battery has pretty much eliminated all the above mentioned issues. If you have swapped the entire phone numerous times, try swapping just the battery instead.

 

The EagleBlood 1.0.3 Revamped rom is probably one of the more popular custom roms for the T-mobile G2x. The only flaw with it is the failure of Swype to work. This is actually not the fault of the rom, but more of the fault of the rom it was built on which is the leaked Gingerbread (2.3.3) rom.

To fix this, flash the following zip like you would any custom rom via Clockworkmod recovery. This should correct the error message that pops up telling you that Swype is in limited functionality.

Swype fix for EagleBlood 1.0.3 Revamped

[Update] – This should work for all ROMs based on the Gingerbread leak for the G2x.

 

image

 

So from a few reports on XDA, there’s some discussion on whether or not removing a piece of protective plastic from the back of the G2x results in better reception. The plastic can either be blue-ish or black like the picture above. It’s located right above the bottom speakers after you remove the back cover of the G2x. There’s no warranty voiding since it’s just a protective piece of plastic like you see on a lot of electronics.

One thing I did notice that was better was wifi calling. My first phone call out via wifi did not break up like it normally did. I’ll try on various access points through out the day, but try this out and see if it does anything for you.

 

I meant to post this a while back, but somehow forgot. Anyway, here’s the Adobe Flash 10.1 that works on the Viewsonic G-tablet. The Flash you see on the Market will NOT work.

Save to your Gtab and side load it via your favorite file manager.

Adobe Flash for Viewsonic G-tablet (registered users only)

© 2011 Droid Hype Suffusion theme by Sayontan Sinha

Switch to our mobile site