[HD2 Android Q&A, Help & Troubleshooting and Genera] YZ:
[26.Mar][Fix] ★★★MARKET INCOMPATIBLE ISSUES, Bootloops, Random reboots -AND MORE- ★★★

MOST ASKED QUESTION ARE ANSWERED IN THE LINK BELOW :

http://xdaforums.com/showthread.php?t=945427

--------------------------------------------------------------------------------------------------------------------------------------

This thread was opened as a question, but now I have some solutions, so I thought I should change it to a fix. Hope this helps!

Introduction:

"Your device is not compatible with this item"/market incompatible issues

Possible solutions to fix the random reboots

Possible solutions to fix bootloops

1. "Your device is not compatible with this item"/market incompatible issues​

​

I will list the solutions that I know about, hope this helps. (if you have other solutions, please reply in the thread)

1.

Clear market cache.

2.

Edit this in system/build.prop to make market recognize your phone as sgs2

ro.product.model=[B]GT-I9100[/B]
ro.product.brand=[B]samsung[/B]
ro.product.name=[B]GT-I9100[/B]
ro.product.device=[B]GT-I9100[/B]
ro.product.board=[B]GT-I9100[/B]
ro.build.product=[B]GT-I9100[/B]

3.

Change DPI to 240.

4.

Download Market Enabler.

Go to the settings list and long-press Verizon [us] and then fake this provider now.

5.

Currently working for me:

LCD Density Modder

Pro

What the app does, is to download a vending.apk to your phone based your preferred dpi. The vending.apk has a "hack" inside, which will trick market to think that your phone is on 240 dpi.

It's a paid app, but it's worth it.

2. Possible solutions to fix the random reboots​

​

- Turn off automatically detect time

- Turn off automatically back light.

- Do not overclock

- Turn off Background data and Auto-sync: Menu > accounts & sync > uncheck "Auto-sync" and "Background data"

The options above "may" fix your rebooting issue, but the one that helped me (no reboots for over 4 months) and few other people was:

Go to Settings - Wireless & networks - Mobile networks - Network operators

Now choose your network operator manually.

I think this fixed my random rebooting issue because sometimes my phone would disconnect from my network and that's when the reboots occurred.

Another "proof" is that the random rebooting was reduced while using magldr. As we know, magldr is more stable when it comes to data, as it uses RMNET. So the disconnecting may be the issue.

Anyways, it worked for me, I hope it works for you too.

3. Possible solutions to fix bootloops​

Update 15.FEB.2012:

(Thanks to Seadersn for the idea)

Increasing the partition that contains the bad blocks will not always help.

To fix this, try increasing the first partition (which is recovery, in cLK)

fastboot oem part-resize recovery:50

fastboot oem part-commit

If your phone won't pass the android screen after a reboot, try decreasing the recovery partition. I ended up at 10.

--------------------------------------------------------------------------------------------------------------------------------------

- Make sure you have performed a task 29 (clean install) before complaining about anything ;)

- If you flashed or edited something in your system, then rebooted and your phone was stuck, then try to go back to how your phone was.

For example:

If you were using kernel 1, but then flashed kernel 2, which caused the bootloops, re flash kernel 1, and it should be fixed ;)

The solution for most of the people:

The Htc Hd2 came out in 2009, and if you are one of the people that have been using it since, then your phone is pretty old. We flash our nands very often, as new rom/kernel updates are released. This is causing bad blocks on the nand. Bad blocks are mostly causing bootloops, but it can even cause small issues like app2sd not working (funny, but it happened to me).

Solution:

Connect your phone to your pc and open the folder where the adb tools are located. Open terminal and type in:

adb shell dmesg

You will see a lot of text... Scroll down and you should see something like:

###BAD BLOCK 1234 56789###
###BAD BLOCK 1234 56789###

OR (recommended) (CLK ONLY):

Enter cLK bootloader. Connect your phone to your pc. Open cmd inside a folder containing fastboot files and type in this: (similar to task29)

fastboot oem format-all

If you do not see any bad blocks, you are lucky ;) if you do, then do this:

- CLK USERS ONLY:

- THIS WILL DELETE YOUR CURRENT ROM AND CWM!

- You need fastboot drivers working on your computer

1. Install clk 1.5 link

2. Turn off phone. Click on power button once, and hold back button. Connect your phone.

3. Download fastboot.zip (scroll down)

4. Locate to the folder where the .zip is located and extract it. Hold shift while right clicking (inside the folder), open terminal.

5. This part depends on where your bad blocks are located. For example, lets say it is located in "system" then type this in the terminal:

fastboot oem part-resize system:160

The "160" is just an example. You will need to experiment with the partition size.

My bad blocks are located in "misc". After some minutes with experimenting, I ended up with increasing it to 25.

IMPORTANT:

When you are done re sizing your partition, type this in your terminal:

fastboot oem part-commit

Your phone should now reboot. Re flash cwm, then install your rom and check if it boots now.

ADVANCED ADVANCED USERS ONLY!​

If you have bad blocks, and task 29 is not erasing it, you can try something called task2a using mtty. It is not guaranteed that this will erase your bad blocks, but there is a possibility.

You will need some drivers and mtty installed.

link

-----------------------------------------------------------------------------------------

My Bad blocks: http://xdaforums.com/showpost.php?p=22994536&postcount=968

If you have tried everything in my guide, but your phone won't run android anymore.. The time is in to get a new phone :(

I hope this helped you :)

Please thank the devs for their work ;)

I would appreciate a thank myself :rolleyes:

PLEASE PM IF I MADE SOMETHING WRONG/MISSED SOMETHING