yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Q&A, Help & Troubleshooting] Danaa:
Hi,

I've installed Tap Tap Revenge 4 on my SII but it doesnt work properly. The image doesnt fit the screen, its some kind of resolution problem i think and i cant hit the notes.

I'm using ICS 4.0.3

Thanks in advance.
[Galaxy S II Q&A, Help & Troubleshooting] ctomgee:
First off, you designated this post as a question... So it should probably be in the Q&A forum, not General.

Second, to address your real question, are you on a stock firmware, or a custom ROM? "ICS 4.0.3" doesn't really reveal that information. It sounds like you're on a non-standard DPI setting. You could have changed that manually if you're rooted, or some custom ROMs have non-standard DPI set by default.
[Galaxy S II Q&A, Help & Troubleshooting] Danaa:
Sorry about that, I'm new :/

Its not rooted and I dont know what DPI is. Noob here :)

Thanks
[Galaxy S II Q&A, Help & Troubleshooting] ctomgee:
So... you're completely stock? I just loaded the game and it's fine on my phone. I'm on a (mostly) stock Gingerbread I9100. I doubt a completely stock ICS I9100 would have resolution issues.

What information does it say if you go to Settings > About phone?
[Galaxy S II Q&A, Help & Troubleshooting] Danaa:
GT-l9100

4.0.3

Kernel version : 3.0.15-l9100XWLP7
[Galaxy S II Q&A, Help & Troubleshooting] ctomgee:
Huh. If you're completely stock, non-rooted, and don't even know what DPI means, then I'm not sure why it's an issue for you. Sorry I wasn't of more help.

Though you may want to consider changing the title of your post; "ICS problem" is way too general for your particular issue. Could help bring more eyes to your post and hopefully someone who knows what the problem is.
[Galaxy S II Q&A, Help & Troubleshooting] Danaa:
Ok, thanks for your time.
[HTC Rezound] brando56894:
TL;DR check the last post

Has anyone else been experiencing random reboots lately? Mine seems to be intermittent, i used my phone for three hours straight two days ago and everything was fine. The damn thing just rebooted on me three times in the span of about an hour, two were within ten minutes of each other. I'm running cleanROM v1.4 with no cpu control apps, and I haven't changed anything in about 1.5-2 weeks.
[HTC Rezound] brando56894:
Just did it again. I'm about to smash this damn thing against the wall!!
[HTC Rezound] casper99801:
I'm running CleanRom 4.5 and have only experienced 1 random reboot. My girlfriend on the other hand is running stock gingerbread and experienced 5 random reboots yesterday. I asked her what she was doing at the time, and she was of no assistance. Definately something to keep an eye on!
[HTC Rezound] brando56894:
I got pissed and wiped everything, then reinstalled CleanROM DE with only the apps I use frequently and everything has been fine so far, haven't had one yet. Maybe it was a buggy app or something else because during this time my extended battery said it was at 80% then after one of the reboots it said 17% and I was like wtf? After the clean install it said 66%!
[HTC Rezound] brando56894:
I lied, it just did it again!
[HTC Rezound] Flyhalf205:
Are you s-off ? if not make sure you are flashing the boot.img after installing the ROM. Or if you are on GB firmware your installing the firmware patch if installing an ics ROM.
[HTC Rezound] brando56894:
Yea I have, it's nothing that simple sadly. At first I thought it was a buggy app so I wiped /data and only installed a few apps I use constantly, but it still happened. So I did a fresh install of the current rom I was on and didn't install any apps or restore any data, but it still did it. I just flashed another rom without restoring anything to see if it still happened and it did. I had an idea that it may be the latest radio image that caused it so I flashed to the one before the latest leak, but it still does it.

I'm currently in the process of flashing the original GB RUU to see if it still does it. If it does then I know it's definitely a hardware problem. If you couldn't already tell yes I am S-Off :D
[HTC Rezound] brando56894:
So the RUU didn't fix it but it did lessen the reboots. Now when I wake the phone up while running Gingerbread the data connection will take a minute or two to connect and will drop out sometimes while the screen is on.

It rebooted on me last night. Also during the night it did a factory reset (or I did it in my sleep!) because when I woke up the phone was at the "choose your language" screen and after I left that all my downloaded apps were gone.

I also just got the OTA adr6425lvw_2.01.605.11-1.02.605.6 but it won't stick.

WTF is going on here? Do you guys think I need to do an insurance claim?
[HTC Rezound] ssoares01:
My GF's stock Rezound reboots pretty frequently too... Mine never does, even stock it didn't. After the last fiasco with VZW and sending phones back and forth she's not going to want to swap it out again :-/
[HTC Rezound] RomsWell:
While your on the stock unrooted untouched ruu do a factory reset from hboot. Then boot up reboot to recovery and flash your Rom.even though I'm soff I still reflash my kernel in hboot after wiping boot.
[HTC Rezound] brando56894:
I'm giving it a try now and I'll see what happens, thanks.

Edit: In the past 8 hours I haven't had any random reboots or radio problems (yet), but the battery stats still seem to be wacky (another symptom I forgot to mention). I had the phone off because the battery was dead and I was charging it at my cousin's house. When I left I turned the phone on and in a span of about ten minutes it first reported a reading of 40%, I opened an app for a few minutes and when I looked at it again it was down to 20%, a minute later it was down to 9%. I decided to shut it off for a few minutes, took the battery out and put it back in, then after I booted up it showed 55%! I also had my extended battery with me at the time which I thought was full but when I put it in, my Rezound just went to the white HTC screen and after a battery pull it wouldn't turn back on so I figured it was dead. I just put it back in now and tried to charge it, it's actually at 94%!

I'm currently on GB Firmware, running CleanROM DE v1.4. Before yesterday (?) I have been on ICS Firmware since the initial leak of ICS IIRC.
[HTC Rezound] brando56894:
It just started this crap again about 4 days ago, I was getting one per day on ICS. I ran the original GB RUU four times (twice, tested it out for a few minutes and noticed that data kept dropping out, then ran it again twice) and it still does it.

Before I ran the RUU I was on ConROM when it started so I flashed Nils latest work, when it started to happen again I flashed the kernel in TWRP, when that didn't work I flashed it directly via HBOOT (extracted the PH98IMG from the zip), which still didn't fix it.

I'm beginning to think that I did damage the radios during the S-Off process since I was one of the people that had been trying to run the exploit since v0.01, also during the later tries I realized that I was shorting out the wrong pins at one point :rolleyes: After I switched to the correct pins and used v0.02 or v0.03 it works and I had S-Off.

I'm about to go back to S-On and see if it still happens.....
[HTC Rezound] brando56894:
Just came back from Verizon and they're going to replace it for free since it's covered under the MFG warranty since the phone is only 8 months old.

I love how clueless their employees are: I told a guy that my phone was rebooting constantly and that that it keeps losing its connection to 4G (then demonstrated that it had lost it's connection even though mobile data was turned on and when I cycled it it would re-connect), he was about to mention a factory reset but I said I had done about 20 factory resets (didn't mention RUUs or anything) before he even got the words out, so he passed me off to their "tech guy".

Here's the real kicker...

I told him that the data radio keeps shutting off and it reboots constantly. His response was "the what?!" :eek: I told him 4G/the internet connection and that I've done numerous factory resets and he then said "we'll ship you a new one."

This is about the 5th time and 3rd different store where Verizon's employees have no idea what the hell I'm talking about. Half the time it isn't even tech related, I've schooled them on their own products and promotions multiple times (namely the 2 month return policy before christmas and the half-off extended battery deal [2 out of 3 employees in the same store didn't know that one])! It's pretty damn sad when a customer who reads Android blogs knows more about the promotions than an official Verizon employee....
[HTC Rezound] johnwaynegacy:
Afaik all android phones do this. Buy an iPhone
[HTC Rezound] brando56894:
Thanks for the helpful response! Ass... I had the original Droid for a year and the incredible for about six months, neither of which did this once. I've also had the Rezound since launch day, I could could the number of times it did this before a month ago on one hand!

Unless you have something useful to contribute STFU.
[HTC Rezound] johnwaynegacy:
If a phone randomly reboots in your pocket, or while you're sleeping... Would you know? I had 7 origional droids, 5 bionics, a rezound, a gnex, and a galaxy tab. I have yet to own an android device that doesn't randomly reboot. I have had devices up tor 11 days without it happening, but inevitability, it happened. I think its related to ram. I never really looked into, but its just a hunch. From what I see on my rezound it is just the shell rebooting and not the device. You are just too much of a fanboy to see that due to many factors, especially fragmentation, that android is super clunky. It is also generally bugged. I am typing this on my bugged sense keyboard, from my bugged WebKit browser. What made android good was open source. It isn't like that anymore.
[T-Mobile Samsung Galaxy S II SGH-T989] yajinni:
I am looking for the points in need to solder the wire at.

I am looking for something similar to this:

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

If you look at his third picture he soldered it to a resistor because he thought it was easier that way. I would prefer the same thing. Unfortunately this is the guts of an ATT S2 and it seems dif than our tmobile one.

If someone could provide this with a nice pic pointing out the spot that would be great!

Thanks.
[T-Mobile Samsung Galaxy S II SGH-T989] rastlin:
now i dont know about any solder points but what i did was to remove the back pannel and exposed the the carger port which is connnected to the usb port..then i went to my local hobby shop (here in the midwest i went to hobby lobby) and $6.99 later i purchased copper tape. what i had done was to look at the battery which is labled where the positive and negitive terminals and laid the copper strips accordingly, now on the other side i made sure that the inductive coil was also in line so that when i placed the battery cover on the back of the unit it will touch the copper tace lines. All i have left is to see if if the touchstone works ( i still have yet to purchase that...) and it will be complete. Now also i have the verision galaxy nexus extended battery installed and some how it all fits. once i have figured out how to get the pictures to show up from my flicker account i will repost them.....heres some quickie links (backdoor) http://goo.gl/6a4YY when i get my other camera back i will post a pic of the inside with battery
[T-Mobile Samsung Galaxy S II SGH-T989] yajinni:
I am sorry but the charger port that is linked tot he USB port?

Not sure what you mean. Can you please clarify?
[T-Mobile Samsung Galaxy S II SGH-T989] yepvegas:
please forgive the neebie question what you are trying to do....what is the purpose.

Thanks for your reply in advance.
[T-Mobile Samsung Galaxy S II SGH-T989] yajinni:
As the link in my original post says basically i want a wireless charging system called inductive charging.

Something similiar to this too that i found on the forum:

http://xdaforums.com/showpost.php?p=26443496&postcount=34

I want to take the wireless charger of a palm pre and modify it to work with my S2.

I need to take the charging coil and preferably solder it to the point on the S2 board where the charging takes place though the USB plug.

The guy in second link basically linked it to the battery contacts, i am not sure how safe that is since it bypasses most of the resistors and charging components of the board.

So hoping someone can help point out where i can do the positive and negative charging contact points on the board.
[T-Mobile Samsung Galaxy S II SGH-T989] yajinni:
Awesome! found what i needed here. Will post when i do my similar mod.

http://xdaforums.com/showpost.php?p=26610417&postcount=40
[Motorola Atrix 2] chsatish:
Two days ago i got a software update notification and i accepted and downloaded it installed then i got a new lock screen and the big change is i never got a gps lock in my position even after one hour also. before update i got position lock in seconds now i'm never got a lock so please suggest any ideas how i get my gps back please if you guys know any idea please tell me thank u or u guys have any idea how to disable last update pls answer me guys
[Galaxy Note GT-N7000 General] andreww88:
Let's hear it....
[Galaxy Note GT-N7000 General] ukicar:
ok I wait. ..
[Galaxy Note GT-N7000 General] RavenY2K3:
Forgive me for being skeptical but, Join date Feb 2011, and this is only your second and very open ended post?...... Hmmmm :S
[Galaxy Note GT-N7000 General] andreww88:
That's why I said "Let's hear it....". Like, I am very curious because I noticed the same thing you did. I hate doubting people, but sometimes you have to.
[Galaxy Note GT-N7000 General] panyan:
errr :confused:
[Galaxy Note GT-N7000 General] yllivia:
I very much doubt it. But lets hear your version of "The curious case of Benjamin eMMC bug"
[Galaxy Note GT-N7000 General] andreww88:
Why did you quote me?
[Galaxy Note GT-N7000 General] hg42:
:-) -- naturally, it's much faster to insert those short messages than rewriting a long german post in english.

Next time I should write the main text prior to posting anything, I think...

sorry...
[Galaxy Note GT-N7000 General] straycat:
WoooooooOOOOOOoooooooowwwww!!!!

YeeeeeeEEEEEEaaaaaAAAAAaaaahhhhhh!!!!!!

You are the man, bro.
[Galaxy Note GT-N7000 General] ukicar:
man has a few posts but are worth a lot. .. thanks for share with us
[Galaxy Note GT-N7000 General] straycat:
And... I just wonder it couldn't be possible to recreate the whole partition table with an appropiate tool like GNU/Linux "parted" or so?

Is the damage so serious? Is it physical??
[Galaxy Note GT-N7000 General] hackerboi:
Interesting Read, this should be of a great help to those bricked without warranty.
[Galaxy Note GT-N7000 General] hg42:
you *can* indeed try to recreate the standard partition scheme (I did it very early with a PIT file in Odin and also tried formatting those partions etc.), but this doesn't work because *accessing* those blocks in any way is the *real* problem.

yes, you can't even fix the bad blocks with the usual JTAG equipment.

I was told by a technician from a good repair center that a fix could eventually be possible by directly reprogramming the flash chip in some way (JTAG again), but no one tried yet, because this would cause several hours of work...

usually they swap the whole motherboard instead (which is >250EUR)
[Galaxy Note GT-N7000 General] straycat:
Thanks, hg42.

I really apreciate your efforts and to share with us.

I'm not a superbriked note owner but I follow with great interest those posts.

Again, thank you, man.
[Galaxy Note GT-N7000 General] Zamboney:
Wow man, that seemed really simple and straight forward. Next week well learn how to copy a file in Android, now that will be much trickier...

Thanks anyway for your efforts!
[Galaxy Note GT-N7000 General] hg42:
LOL, you're right, at the end I also thought, that's really simple

but, at least...I had several problems to solve before getting adb up and running properly with root permissions and having the necessary tools at hand (inside adb).

I think this was mainly because I wiped my /system before.

But, it's easy to be wise after the event.
[Galaxy Note GT-N7000 General] hg42:
hmm, I tried to export this partition scheme to a PIT file (using heimdall-frontend), but I got a file that is exactly equal to the one I flashed last via Odin, which was Q1_20110914_16GB.pit.

So I assume the PIT file is one way only?

A PIT file would probably allow even unexperienced users to unbrick their phones.
[Galaxy Note GT-N7000 General] neos_83:
This is the same method here:

http://xdaforums.com/showpost.php?p=26285877&postcount=12

Although your post I found easier to read.
[Galaxy Note GT-N7000 General] hg42:
@Morality do you have any uv or oc?
[Galaxy Note GT-N7000 General] Morality:
Not that I know of. And as far as I know, none of the kernels ive used has them by default. Im sorry for being a bit slow on responding but I find typing with a touchscreen keyboard a bit tedious and I currently dont have a pc available all the time :) ill responding to your earlier message asap.
[Galaxy Note GT-N7000 General] Morality:
I sincerely doubt it since all bad block found by dd or e2fsck were before the block 3322, Where Stock data ends. Space between Stock data end and Stock ums end was free of errors.

I couldnt actually pinpoint their actual location or size, just that one spot was relatively Early in /system (so early it rendered the recovery un-usable when partitioned, but it can be restored by flashing a kernel via ODIN) and another one somewhere in /data. As said before, the Stock ums partition didn't have bad blocks in it according to parted check and dd.

I always installed my Roms to a partition scheme that didn't, according to e2fsck -c and dd, have any bad blocks in them (/system always started after 3322, after which I shouldnt have any bad blocks).

PA and asylum are cm9 based, kingdroid is TW/Stock based. Asylum is the smallest rom ive encountered, with practically Everything unnecessary removed.

Now that I think about it, I tried to initially fix the Superbrick, before finding out about repartitioning, by flashing a Stock bootloader. Could that have something to do with this? I am trying to provide any and all even tinier possibilities now :) I'll try to find a link to the One i flashed..

EDIT: Found it, I used this guide for the bootloader flash: http://xdaforums.com/showpost.php?p=23052721&postcount=10
[Galaxy Note GT-N7000 General] hg42:
@Morality, I think I'm lost...

To be really sure, you could scan all your current partitions (1-12) with dd.

I think the ROM itself doesn't matter, but the kernel.

I think, the boot loader should be irrelevant, too.

Which Type/Date/FwRev do you see in emmc check? Mine is VYL00M, 1/2012, 0x19
[Galaxy Note GT-N7000 General] Morality:
I will Reply to this when I have a pc available :)
[Galaxy Note GT-N7000 General] jayaka:
my story :)

Hello thank you very much for your work.

I tried your pit files, 2 of them were ok for me. So i tried to flash a stock rom with each of the files. Actually i did, but each time i use a pit file different from the stock one, flashing was succesfull but the phone stucked at boot animation. If i use stock pit file, the system starts normally, i can start using the phone, touch screen but then freeze in a min, in an hour, in a day. The record is 48 hours with a stock rom and 72 hours with a custom rom:)

I tried many stock roms, both GB and ICS they do behave in a similar way.

At the moment i m using paranoid android, which is flashed via CWM and quite stable for approx. 24 hours. When it freezes i wipe everything and reflash it. But doing the same thing every day is quite annoying. Sometimes it is flashed easily, sometimes i have to struggle more.

I m using heimdall to flash ROM's. I've found a GB rom (N7000XXLA1) where there were ums.rfs, datafs.img besides factoryfs.img as separate files (in other GB or ICS roms, i had never seen ums.rfs ). factoryfs was flashed with a succes as usually but heimdall stucked at %100 of datafs (and if i cancel datafs.img, it stucked at %13 of ums.rfs). But on the other hand, as i've said i am able to flash many stock or custom roms and use them for some time without any problem.

I m not able to understand what is really my problem as i am a newbie and hope that someone from here may comment and help me to diagnose the problem so that i can try to find a way to fix it.

And yes, all these problem started right after i wipe/factory reset via CWM under a custom ICS Rom.

Thanks in advance.

---------- Post added at 05:27 PM ---------- Previous post was at 05:23 PM ----------

the working pit files were Q1_20110914_16GB-patched-regain-1024000-kB.pit and Q1_20110914_16GB-patched-regain-2040000-kB.pit
[Galaxy Note GT-N7000 General] hg42:
@ jayaka

The PIT of this thread change your partitions in a way that the bricked blocks are not used by any partition.

If you flash a stock PIT you repartition again and the blocks will be used again.

If any program on your phone accesses a damaged block, the phone will freeze.

So don't flash stock PITs.

They would only be needed if the partition sizes change (e.g. new ROM needs more space).

But I doubt this will ever be, because the N7000 has quite big partitions.
[Galaxy Note GT-N7000 General] jayaka:
thanks for the quick reply.

The problem is that if i use any of these 2 PIT files, the system stacks at samsung logo (boot animation). I don't know how to overcome this.

I think i always tried to flash a stock rom each time i use one of your PIT files via heimdall. Let me try with a custom rom via CWM on that new partition table, i'll post the result.
[Galaxy Note GT-N7000 General] hg42:
which PITs did you use?

In my first post, I wrote you should start with the patched-standard PIT with the correct size (16GB or 32GB).

Only if this works well, you should try others.

If your bad blocks are in system and/or data you will have a working phone (if you did all steps as I described, especially wipes).

If you still get freezes (and did all steps correctly, especially wipes!) you probably have bad blocks in your former internal sd partition (which seems to be a rare case).

This is why you should better start by checking where your bad blocks are (if you can manage adb etc.).

The ROM shouldn't matter much.

But, directly installing on a fresh partition (with kind of random data inside) via CWM may not work if the script in the installer zip doesn't do formatting itself, because there is no valid file system. You then have to format it first, which you can do when in a CWM recovery ("format system").

EDIT: I added this "format system" step to my first post. I think, it is not needed in most cases, but I inserted it to be sure.

Please (re-)read my description at the end of my first post and follow those steps. If that works for several days, you can try to optimize if really needed.

Note: if you forget those wipes you may get all kinds of feezes and weird behaviour.

E.g. if you have no data partition the phone may boot, but then you will get crashes all the time.

Internal sd is less critical, but some apps don't like this either.

If you get stuck at your boot loader, you probably have a problem with your system partition, which could be a bad block, but could also be a missing file system, or other problems.