yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Q&A, Help & Troubleshooting] nimataheri:
try to key in this in dialer

try to key in this in dialer

*#7284#

it has 4 option there..

UART

MODEM

PDA

USB

MODEM

PDA

For usb. select the PDA.if it already selected to PDA. reselect it by select MODEM and then PDA again.. Only change the USB setting.. andthen press back. try reconnect to kies again..

hope it helps..
[Galaxy S II Q&A, Help & Troubleshooting] jony770:
Windows firewall should be the way

I had the same problem like you. My SGS2 couldn't connect to PC. And after some research, I came to a thread. According to that thread, I solved my problem. It's the windows firewall. All you need to do to go to Control panel>Windows firewall.

From the left panel, u have to click "Allow a program or feature through Windows Firewall". Then you need to scroll down all the way to the bottom to select "Wireless Portable Devices". Tick all three boxes (domain, home/Work(private) and public).. Click OK.

Now I can easily connect my SGS2 to my computer. Hope it works same to you.

---------- Post added at 11:01 AM ---------- Previous post was at 10:51 AM ----------

I had the same problem like you. My SGS2 couldn't connect to PC. And after some research, I came to a thread. According to that thread, I solved my problem. It's the windows firewall. All you need to do to go to Control panel>Windows firewall.

From the left panel, u have to click "Allow a program or feature through Windows Firewall". Then you need to scroll down all the way to the bottom to select "Wireless Portable Devices". Tick all three boxes (domain, home/Work(private) and public).. Click OK.

Now I can easily connect my SGS2 to my computer. Hope it works same to you.
[Galaxy S II Q&A, Help & Troubleshooting] petarpan:
:crying: Unfortunately only solution for this issue is to replace usb connector, because some pins get loose and then not connect properly.

Had the same problem and this is how it's been solved for me.
[Galaxy S II Q&A, Help & Troubleshooting] tsm73:
galaxy s2 on flight mode and not charging

Please assist, I have a Samsung gs2, it was doing so well though sometimes it would lose network connection and by the time I realize I would have missed messages and calls.

My biggest problem started when it just stopped charging, I had to use another phone to charge the battery and I would survive for the day.... After about a month doing that it just went into flight mode... t never came out...

Must I give up?:eek:
[Galaxy S II Q&A, Help & Troubleshooting] manishdev:
Had a very similar error tried everything in d world and two different laptops and different cables but np solution den tried slim rom version 3 after downloading the same via wifi and d errors got fixed...I think its kernel issue or rom not sure as I tried many roms and kernels
[Galaxy S II Q&A, Help & Troubleshooting] _sem_:
I had a problem with SGS2 not wanting to shutdown (would just reboot) and charging problems.

The shutdown problem went away after thourough cleaning of the USB port.

But charging was not fixed. I had to replace the USB & mic board. Not very expensive and not so difficult, especially if you google up and read the repair manual. Mind there are different revisions of the board, and it is advisable to get the same revision, some are even physically different.

I've got a remaining problem with USB host connections via USB OTG cable to flashdrives and other devices which only work for a few seconds than fail, but I don't know if this is perhaps software (since the ICS update) or the board, ruled out cables.
[Galaxy S II Q&A, Help & Troubleshooting] Shapeless:
I think I found a solution.

Hello,

I found a solution that so far has worked ~90% of the time for me. I had the same problem as most of you - device not recognized, drivers not installing properly, etc.

I read around on different forums and did some self troubleshooting and came to these conclusions:

What I found out on my own:

I was able to make Windows detect my device by doing the following:

Launching Kies on my PC

On my Phone:

Connect the phone to the usb cable (but DO NOT connect the usb to the PC)

Go into Settings -> More settings -> USB utilities -> Connect storage to PC

After that plug in the USB into the PC -> Kies should give an error telling you to enable USB debugging (can't post pictures yet, or I would, sorry :( )

So, do what Kies tells you: go to Settings -> Developer Options -> Enable USB debugging

Windows should detect your device (not working 100% of the time)

What I found out by Googling (this method works almost every time)

Launch your Dialer

Press *#7284#

A menu will appear: under USB check PDA (if it is already checked, choose MODEM and then PDA again)

Connect your device; Windows should detect it

I hope my post will help at least one of you :)
[HD2 Android Q&A, Help & Troubleshooting and Genera] lokie538:
Hey guys, I need some quick suggestions if anyone has it. Currently I have a non working phone.

I have been running an ICS NAND rom on my hd2 for a while now, havnt had any issues (a few niggles with the rom, nothing major) so I thought today I would update to the latest version.

I used the hd2toolkit to resize the partition to the biggest size it would allow, then used ad recovery to flash the new .zip to the nand. This is where my problems started, whenever i booted it just showed the boot animation, (I waited over an hour and pulled the battery out and re booted / reflashed a few times).

I found with a differnet rom i tried, pulling out the SD car would allow it to get to the welcome screen, but no screen input was accepted. I thought this was a bit weird but pushed on. I tried a different rom and it stated after flashing that it was optimising applications and looked like it was stuck in a boot loop. I did some reading up about it and found that task29 should help. I ran this but then all the phone would do is show the green HTC on the white background, it wouldnt let me to get into magdlr menu.

I then decided to to a full restore and go back to the wm rom from th HTC site (The australia telstra version), this seemed to flash on fine, but now I can not slide or click buttons in wm, no screen input is accepted. Which is strange as it was doing this in an android rom, as I mentioned previously.

Any ideas on how I can get touch working / get a NAND android rom to work again.

Thanks in advance guys :)
[HD2 Android Q&A, Help & Troubleshooting and Genera] shanman-2:
First verify that you have hspl installed by powering on while holding vol down button to get to bootloader screen

Go back to the hd2 nand toolkit

1.task29

2. Select either cLK repartition or Magldr repartition and select size for your rom (not the maximum size). 200 mb is fine for ics using sdext partition.

3.Select magldr update recovery or cLK install recovery depending on your selection above.

4. Reboot phone by pressing power and holding to get to magldr or power and home button to get to cwm recovery.

5. Install ICS from sd card as before
[HD2 Android Q&A, Help & Troubleshooting and Genera] lokie538:
Thanks for the help, I had to flash a different radio version to get magdlr to boot.

I now have android running of my NAND, but the screen is non-responsive now, as it was yesterday.

I doubt it is hardware related, because I have never had an issue before yesterday when I wanted to change the android version, any ideas how I could get it working?
[HD2 Android Q&A, Help & Troubleshooting and Genera] htccraze:
Make a backup and then repartition again using HD2 toolkit. Maybe you got a bad download or something. Seems simple but it does happen. To me if I didn't know you choose the biggest it would sound like the partition wasn't big enough. Maybe try a cyanogen ROM since it reguires very little partition size and report back if successful.
[HD2 Android Q&A, Help & Troubleshooting and Genera] lokie538:
I have tried two different android roms and the stock wm image from htc's site, all of which the screen doesn't work on. I will have a try with a cyanogen ROM and see if that makes a difference. Thanks
[HD2 Android Q&A, Help & Troubleshooting and Genera] lokie538:
http://xdaforums.com/showthread.php?t=769026

I just tried this rom and still no deal. This is very weird as I haven't had any issues with the screen at all, the phone is still in new physical condition.

Does anyone want to have a stab in the dark, as I really need to use it as a GPS tomorrow and any help would be appreciated.
[HD2 Android Q&A, Help & Troubleshooting and Genera] htccraze:
Tell me what the steps you take to install a new ROM. Do you have MAGLDR or clk? Have you task29 yet? Are you sure your using the right partition? Are you using nand or sd Android?

If all else fails maybe check out this thread to reinstall

MAGLDR and then cwm. I've had problems in the past installing HyperDroid without

wiping my SD card first. Maybe check out this nand ROM instead or Coredroid found in my signature.
[HD2 Android Q&A, Help & Troubleshooting and Genera] lokie538:
When installing a new rom, I have resized the magdlr partition, then copied the .zip to the sd card, then in ad recovery installed the zip through there. This has worked fine in the past. I followed the videos you have linked and I'm pretty sure I'm doing everything right and yes ive used task29 several times. In AD Recovery every time it states that installation has been successful. I have also formatted my SD card many times.

The ROM you linked, I can find download links on the page, not sure if I'm just missing them.

I just tried an SD card rom, its doing the same thing, no touch input is accepted.

Does NAND roms and SD roms not working imply that it could well be hardware? I just dont understand as it stopped working when I was reflashing yesterday and it was not dropped or roughly handled in anyway during this process.

I am now going to investigate MTTY (for bad blocks) and try reflashing back to original WM again. Please post more suggestions if anyone has them.
[HD2 Android Q&A, Help & Troubleshooting and Genera] lokie538:
Another update: I just restored to default using the method listed below.

http://www.jayceooi.com/2011/08/15/how-to-restore-stock-rom-on-htc-hd2-video/

It took around 40-ish minutes and still no input from the screen, this is seriously frustrating.

WM boots fine and everything, but still no input is accepted.
[HD2 Android Q&A, Help & Troubleshooting and Genera] htccraze:
I'm sorry to say but if your having the same problem with all that then it sounds like the digitizer stopped working. Maybe someone else knows something I don't so I would wait to see if they could help out.
[HD2 Android Q&A, Help & Troubleshooting and Genera] lokie538:
Thanks mate, I am not sure why it would have just stopped last night. Appreciate all the help! I'll see if anyone else has any suggestions.
[HD2 Android Q&A, Help & Troubleshooting and Genera] htccraze:
It's not a problem. I do have to admit that it does seem pretty odd the timing of it. Hopefully it's a not the digitizer and someone would be able to point out what might be the cause of everything.
[HD2 Android Q&A, Help & Troubleshooting and Genera] lokie538:
This may seem a little crazy, but after having a search online about my issue, it seems that a ribbon going to the screen / digitizer is behind the power button on the HD2s, which apparently can get loose and after a sharp press of the button it started accepting screen input again!

The issue for me now is that when the power button it will stop accepting input again, untill I press it firmly again. I think I may need to open up the phone and check all the connections now.
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] oaker:
Hi all

I have a memory problem in block 2405.

I want to send it to guarantee, but i can not set back SPL.

I have HD2 WWE, HSPL2.08. I can see white screen or boot loader.

I try this:

1. HSPL4.exe, HSPL3_PKG.exe are going well to end but they really doesnt change HSPL to SPL.

2. from original ROM I build leoimg.nbh and boot from SD but I see this

00018003

LEOIMG.nbh fail

radio_V2 fail

Rcust

Boot

Splash1

OS

Configdata

UPDATE Terminated

UPDATE fail

3. to flash original rom stop after 1% with memory fail

4. mtty task29 say that block 2405 is fail

1. have you any idea how to change HSPL into SPL

2. how to build leoimg.nbh only with SPL part? I extract 02_SPL.nb from original RUU_signed.nbh ROM

3. which address range in HD2 have SPL?
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] samsamuel:
try using hspl2, and try to set 1.66 or 1.42. your current spl, 2.08, is a tmous spl, and can cause occasional issues with flashing stock from sd, even on a fully working phone.

ALso worth trying the freezer trick, too. Radio_fail is a fairly common fault, sometimes it gets fixed easily, , hspl works after several tries, or several attempts at flashing the correct stock rom from sd suddenly works, or chilling teh phone in teh freezer followed by an sd falsh suddenly takes and everything is fine again., , , but most times it doesn't get fixed.
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] oaker:
I solve the problem

thanks

I try your freezer trick and hspl2,hspl3,hspl4 in all possibilities but doesnt change hspl.

BUT I found the list of Hermes boot loader commands. And I set task 2a. And this solve the problem with memory. After it is running flash from SD.
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] samsamuel:
Ahh good to know.
[Galaxy S II Q&A, Help & Troubleshooting] vikeor:
After updating my SGS2 to ICS all my contacts got messed up and the Facebook pics got deleted. I synced FB again and again and nothing, no pictures are coming up! Any help?
[Galaxy S II Q&A, Help & Troubleshooting] Zeus65:
Hi I'm not sure if this helps, but saw this on the XXLPQ comments secition on androiddevices.com

Chiriks Reply:

March 15th, 2012 at 2:26 pm

@Chris Hill,

Remove acount, from setting- acounts and then , and check for face book app update, add it once again…

And it should work, for me it`s removed issue…
[Galaxy S II Q&A, Help & Troubleshooting] ctomgee:
Also, you will have to load each contact in the FB app at least once for the picture to cache on your phone. Then, if they update their picture in FB, your phone will retain the old one until you load their picture in the FB app again, at least once.

EDIT: FYI, I told this to someone else, and it worked for them.
[Galaxy S II Q&A, Help & Troubleshooting] vikeor:
thanks guys, ill give that a shot
[Galaxy S II Q&A, Help & Troubleshooting] rez1:
did it work?

Im having the same problem after ics update XXLPQ... no contract picture...

Did it work for you?
[Samsung Galaxy Mini] salmaj:
Hi guys. Is there any improvenvement with the multiouch bug? I talking about that the Galaxy mini cant recognize the second touch instantly. You have move your fingers on the screen befor it recognize. It's annoying when you playing games.

Sorry for my bad english
[Samsung Galaxy Mini] KoperKiller:
First, if you overclock your device it should be solved; and second, wrong section dude :D
[Samsung Galaxy Mini] salmaj:
Why wrong section? It's a software based issue. Needs improvement. What kind of overclock solve this problem?
[Samsung Galaxy Mini] elixdragon:
I dont think theres any solution yet...its a driver problem n i guess samsung can fix this but they haven't yet..
[Samsung Galaxy Mini] aprizND:
first Samsung phone has zero multi touch conflict n problem.

second wrong section .

third laggy response is CPU problem( how its send dot per dot sensors)

fourth what the heck it is........??????

:D
[Samsung Galaxy Mini] roofrider:
Definitely wrong section..any question no matter what does not belong here unless u have developed something to improve it.

That being said it is not a bug from the roms but rather a samsung driver or some other prob as elixdragon said...this is a low end phone, what can we expect.

This exists even on stock gb (i assume it does)?? i never checked.

--edit--

read abv post.
[Samsung Galaxy Mini] D.O.C:
This is android development, not tech support. Regardless of a valid question there is no development here.

Please post in the appropiatte section or be subject to an infraction.

Thread closed
[HTC Rezound] scotty1223:
happened across this this morning:

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

(thanks to jcase on twitter)

value could be a couple different things,to us:

1)downgrade if there was an explolit in older firmware

2)use it to sneek on the signed eng hboot by using that in the third step instead of an s-on ship hboot,then running an RUU with hboot removed to finish recovering the phone

id love to try it,but i dont have a linux machine and my linux skills are basically none :eek:

your thots? :)
[HTC Rezound] anothen:
whoah! I just read through that whole process and that is some scary stuff right there. But looks like it could be great progress right there!
[HTC Rezound] NilsP:
Yeah, I am looking forward to Revolutionary or someone to make it a one click routine. That would be nice.
[HTC Rezound] punman:
Interesting. If I were to guess, I would say that HBOOT unlocks something in order to prep for a flash of a PH98IMG.zip ... when you intentionally brick the phone by messing with the flashable file you've left it in an unlocked state, which you can take advantage of after rebooting by directly copying to the raw partition a bootable image. Obviously some knowledge of the underlying phone hardware is needed in order to find, modify, or build from scratch this bootable image and finding the proper partition into which it needs to be copied -- the directions in the linked thread are for a different phone and different code and probably different partition names would be required.

This may not even work on the Rezound.

And, I should add, the potential to permanently and irrevocably brick your phone is quite high. :)
[HTC Rezound] con247:
It might work with the signed eng hboot. I would try it if I had a backup device. Hell if someone has one that is in terrible condition that is going to do an insurance claim reguardless, I would ask them to try it out. Or have me help them try it.
[HTC Rezound] dlsolo:
I'm gonna give this a shot. Worse thing that happens is, I go and buy another Rezound (or something else).
[HTC Rezound] anothen:
Yeah- I remember how easy it was on the Incredible to root. Then on the Thunderbolt it was a little harder (for those who aren't comfortable with adp commands) and eventually a one-click process came up. Now, it would be great to have something like that on the Rezound and maybe, just maybe, be able to root without this big, ugly UNLOCKED / RE-LOCKED showing in H-Boot!
[HTC Rezound] scotty1223:
You,sir,are a gentleman and a scholar :D looking fwd to your results. If it fails,ill throw a few bones your way to help purchas a replacement!
[HTC Rezound] con247:
can you hit me up on gtalk before you try? PM me please. I have some suggestions that might help it go better.
[HTC Rezound] lllboredlll:
i'm in... no luck with rom building today so i might as well fry my rezound :cool:
[HTC Rezound] con247:
If you are gonna try it now PM me please if you want to gtalk. I have a couple ideas/suggestions
[HTC Rezound] anothen:
awww yeah! here's hoping for some positive results!!
[HTC Rezound] mighty_markus12:
was just going to post this last night. good luck guys!
[HTC Rezound] con247:
For anyone that wants to try it

Start with the OTA PH98IMG.zip

Then swap with our shipped PH98IMG.zip

So you should be trying to go from Hboot 2.11 to 2.10

Then when in linux, recover with the signed eng hboot image we have.

After that, I would recommend using fastboot to turn secure flag off (assuming you didn't brick and it worked)

Then flash a homemade PH98IMG.zip with everything except hboot in it.

What should be done first is identify which emmc block hboot is before you start this process.
[HTC Rezound] Easton999GS:
woah... if we have a "signed" eng HBOOT why cant we just flash it over the one we already have?
[HTC Rezound] con247:
It's a lower version. So we need a downgrade like this to flash it
[HTC Rezound] fernando sor:
I'll pass everything in my paypal account to anyone who gets this. I think is like 60 or 70 dollars.
[HTC Rezound] jclendineng:
If this works kudos. S-off is like the rosetta stone of htc phones lol
[HTC Rezound] Marcismo55:
While I can't be as generous as you ;)...I will certainly donate towards someone who does attempt this.

Great find Scotty!
[HTC Rezound] Easton999GS:
What version number is the ENG HBOOT?
[HTC Rezound] scotty1223:
are you sure the eng hboot wont boot?

i get the impression it will,as in his last steps he boots to hboot 1.4(while still on the fimrware for 1.5) and has to run that RUU to finish recoverying the phone to a boot able state.

you might be 100% right,but i suggested what i did based on the assumption(wich i made from the info in the eveo 3d thread) that the eng hboot would boot,and the radio wont brick the device until you try and boot it fully into the OS.

just for discussion... im not saying your wrong,as i have no idea :)
[HTC Rezound] con247:
The eco 3d hboot 1.4 is a normal hboot. It is their original shipping one. So it is the equivelent of 2.10 for us. However, theirs is exploitable with revolutionary which is why they downgrading is their ticket to Soff
[HTC Rezound] scotty1223:
Right...

The thing that made me think the eng.hboot may boot without issue is the fact that the firmware on the phone at the time 1.4 boots is looking for 1.5. But no.security warning or anything. The phone does not seem to care it has booted a mismatched hboot
[HTC Rezound] loki993:
Seriously amazing if you guys manage to pull this off, really. I'm checking this thread every day multiple times a day just watching fascinated. I wish I could do something to help, but 1 I need my phone and 2 I know nothing about android development. I wouldn't mind learning though.
[HTC Rezound] con247:
I am honestly more excited about the possibility of being able to downgrade our radios and such.
[HTC Rezound] angryPirate12:
Aside from emmc_recovery and prep work, I really only need 3 files for the process. After reading the source thread a few times and reading some of the comments on the process, it seems that it doesn't matter what hboot you have, using this process you could be on 2.10, use 2.10 to trigger the brick, then flash 2.10 to save it. Now with that being said, I believe that as long as I only use hboot flashables, I can take any RUU, be it stock or the newest 3.11 and remove the hboot, boot, recovery, and radio (to be safe) to finish the process. I mean my phone currently is running 3.10 base with hboot 2.10 with baseband .95.

It'll roughly go like this: (using 3.11 as example)

- hboot_2.11.img - partial flash allow emmc_recovery to force flash

- hboot_2.05.img - emmc_recovery flashes to repair the partial flash

- RUU_3.11.img = completes the flash by adding missing files
[HTC Rezound] con247:
Hold on until I get more info. Someone pm'ed me saying they tied it and hardbricked the phone. However they didn't tell me what hboot they started on or what they tried to flash. I am assuming they tried the eng hboot which is what I and others expected to happen. However, a downgrade to 2.10 or 2.05 might be useful for people with bad ota experiences.
[HTC Rezound] angryPirate12:
interesting...
[HTC Rezound] dlsolo:
Just ordered another Rezound. Gonna try this again once I get the new device. Should be tomorrow afternoon. I messed up the first time. I'm gonna go a little slower and thoroughly read through the posts before I proceed again.
[HTC Rezound] mighty_markus12:
Is this an insurance replacement device? If soo its a ballsy move to brick another, hope you dont get charged full retail? You didnt say if you bought a new device or if verizon/htc sent you one?

Regardless i wish you luck and give you props for trying this.
[HTC Rezound] dlsolo:
I've got a smartphone budget and there's a good amount sitting in the account. It's been awhile since I've bought anything new so it's no big thing. Not retail but not replacement either.