yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Q&A, Help & Troubleshooting] invalidtarget:
@Lennyz1988: Thanks for the reply. So far I have only tried entering recovery up to two restarts (restarting once with Vol. Up + Home + Power, then doing it again once it restarts) though I have not tried three times like you said worked for you. I will try this when I get home today though and I'll post an update when I test it. As for KIES im a little out of luck using it, as my phone isn't recognized by KIES in its current state (even though I have all of the proper drivers, I guess not having a working firmware is blocking KIES from interaction with the device? Thanks for the suggestion, do you have any idea of being able to recover my phone enough so that KIES will recognize it again? I have tried something similar to the guide you linked but after I selected my device and enter my serial, KIES gives me some error stating that no firmware could be linked to the device I entered? I could have entered it wrong, though I tried about 2 or 3 times with no luck. I will try the exact way the guide explains when I get home today, so thank you for the link and suggestion. Also, thanks for the reply by the way!
[Galaxy S II Q&A, Help & Troubleshooting] gastonw:
Re: [Q][GT-I9100M Virgin/Bell] Can't Unbrick, always "Complete(Write) operation faile

Siyah will get you rooted and will install CWM recovery.

Sent from the little guy
[Galaxy S II Q&A, Help & Troubleshooting] invalidtarget:
UPDATE: Ok, so my current status today is as follows.

1. I have tried the suggestion of multiple restarts to get into Recovery Mode while the CF-Root kernel is flashed, however the situation did not change and I still only get the boot logo screen with the yellow /!\ triangle. I have tried holding for a total of 5 minutes and nothing happened, same goes for holding the buttons until it restarts, releaseing the buttons, and repressing them to restart again. No change after 10 restarts, but thanks for the suggestions! Any other ideas to share?

2. I have attempted to follow the link provided for recovering through KIES, however when I enter my model and s/n KIES gives me the message "GT-I9100 does not support initalising." I have also tried using my exact model, which is the GT-I9100M and still got the same message, except that it said "GT-I9100M does not support initalising." Not sure if I entered something incorrectly? I make sure that the model number is all capitalized as GT-I9100 and GT-I9100M, and I enter all 11 characters from my S/N (serial number). Have I done this wrong or is there some reason that KIES doesn't support my phone?

3. Currently about to try flashing Siyah and going to see how that works, I will post an update once I get the results.

UPDATE: Ok I have been able to flash Siyah, however I still cannot enter recovery mode. Any suggestions on a ROM to try and flash? As I've said, im using a Samsung Galaxy S II, model GT-I9100M from Virgin Mobile in Canada. Do I need a kernel with UGKG2 support, as that's apparently the proper firmware version that I need for this device?

Once again, many thanks to all of you for your time.

Cheers,

IVT

UPDATE (02/25 4:50pm EST): Still having immense troubles getting recovery mode to boot... I have tried using the following:

KERNEL: CF-Root ; FLASH: Successful ; RECOVERY MODE: Unable to access

KERNEL: Siyah ; FLASH: Successful ; RECOVERY MODE: Unable to access

KERNEL: CWM Recovery ; FLASH: Successful ; RECOVERY MODE: Unable to access (http://xdaforums.com/showthread.php?t=1118693&highlight=kg2)

Could the issue with flashing ROMs and being unable to enter Recovery Mode both be caused by my phone not being wiped? If so, is there any way to hard-wipe the device without using a recovery manager?

Thanks,

IVT
[Galaxy S II Q&A, Help & Troubleshooting] Lennyz1988:
Alright.

1. Uninstall kies completely.

2. Download the latest version of kies.

3. Install kies and make sure the drivers are selected during the install process.

4. Disable virusscanners

5. Put the device in download mode.

6. Plug the device in a backport usb (not the front). Also try different usb cables. Some work and some don't.

7. Kill all kies processes in the task manager.

8. Download the latest version of Odin. Also keep the 1.85 so you can try both. Make sure you run Odin as an Administrator!

9. Try to flash now.

If it fails, try a different cable. Then try the same procedure on a different pc. If it keeps failing report back.

Btw, I9100M is the same as I9100.

Here is a thread with stock firmwares:

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

First try the latest. DONT use .pit or re-partition yet. If that one does not work try this version:

I9100XWLP3

And if that doesn't work, try only flashing CWM recovery. Try first the JB version and if it fails the ICS.

http://xdaforums.com/showthread.php?t=1118693
[Galaxy S II Q&A, Help & Troubleshooting] gastonw:
Re: [Q][GT-I9100M Virgin/Bell] Can't Unbrick, always "Complete(Write) operation faile

Amen to the above.

I, on the other hand, would like you to flash this: http://www.sammobile.com/2012/11/15/i9100xxlsj-–-galaxy-s-ii-android-4-1-2-jelly-bean-test-firmware/

Only CODE, MODEM and CSC.

If the flash is successful, you should be able to pass the boot animation.

Sent from the little guy
[Galaxy S II Q&A, Help & Troubleshooting] Lennyz1988:
Can you post the complete logs from Odin after trying the above? Please use something like http://pastebin.com so the topic won't get filled.

If the above fails then we will try flashing a bootloader and after that we could try using .pit and re-partition.
[Galaxy S II Q&A, Help & Troubleshooting] gastonw:
Re: [Q][GT-I9100M Virgin/Bell] Can't Unbrick, always "Complete(Write) operation faile

I think odin flashes are successful all the time in this case.

Sent from the little guy
[Galaxy S II Q&A, Help & Troubleshooting] invalidtarget:
EDIT: I have noticed that basically all firmware and md5s fail at NAND Write. I hear this can be fixed through reinstalling the proper USB Drivers (will attempt to do this, AGAIN...) but can also mean that my NAND Memory is corrupted (a little pessimistic to think down this line, because I'm pretty sure that means my phone is finished...) I doubt its corrupted since I can flash kernels still, but I'm no expert. Any observations, insight, or opinions are welcome.

Thanks,

IVT

Edit: Was just looking around and kind of thought of something. If my NAND Writing is the problem, wouldn't repartitioning my phone offer a potential fix? Could the problem I have with accessing my Recovery be because of the messed up partitions?

Someone give me some feedback on this idea, and if you agree how would I go about doing something? I've heard to generally stay away from PIT and Bootloaders, as they are a little less forgiving than firmware and kernel flashing.
[Galaxy S II Q&A, Help & Troubleshooting] gastonw:
Re: [Q][GT-I9100M Virgin/Bell] Can't Unbrick, always "Complete(Write) operation faile

Nicely done man, If you want you can add [SOLVED] to the topic.

I'm sure it'll help users with the same issue.

Sent from the little guy
[Galaxy S II Q&A, Help & Troubleshooting] kamiz9999:
Hello,

I started last year and a thread with this problem : http://xdaforums.com/galaxy-s2/help/i9100m-stuck-loading-page-samsung-t2692853

I gave up after I spent a lot of hours to solve the problem without any success

I made a clean up of my desk and found this sleeping phone so I tried again without any success this week, but yesterday I found your thread and I thought it was my problem something messed up with the partition.

I had all the files already from your list except the PIT file, I did find yesterday the exact same PIT.

I followed all your step

1-Flashing Kernel in PDA

2-Flashing PIT file, when I flash the PIT, I also add all the firmware, csc, phone as you can see on the pictures attached. The problem after this step is I got a lot of red lines appearing all starting by : E:failed to mount /cache

I can access my phone in downloading mode, install cwm and flash custom firmwares but all the time stuck at boot logo

Can anyone help ?
[Sprint Samsung Galaxy S III] bocaccio:
I tried to root it with the toolkit and it wont boot past the samsung logo. Just stays with the blue ligt on.
[Sprint Samsung Galaxy S III] teh roxxorz:
Well it sounds like you have a boot loop. And for the record, if the phone physically turns on, it boots; so you may wana change your title.

I'd go back into recovery, do a clean wipe and reflash your ROM.
[Sprint Samsung Galaxy S III] bocaccio:
When i hold up/home/power i see the blue words at top left and it continues to boot then i see the blue light again.
[Sprint Samsung Galaxy S III] teh roxxorz:
Not bashing, but in the future, i think you should have read up more on it, because you could seriously mess up your phone if you mess up.

Though:

Recovery > turn the phone off. vol up + home button + power. you'll see 'recovery' in blue letters, when you see then, release the buttons.

Download mode > turn the phone off; vol down + home + power
[Sprint Samsung Galaxy S III] bocaccio:
Ok i got in and wiped userdata/cache/dalvik cache. then rebooted. i heard the reboot sound and nothing came on the screen though back to the blue light.
[Sprint Samsung Galaxy S III] bocaccio:
Well I got it on with a restore. Apparently I do not know how to root. Thanks for the patience :)
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] incisivekeith:
Since Project Butter was announced as groundbreaking for Android devices, it would be good to know what the community thinks about it as the official JB ROMs have launched.

Please provide your input as a casual user and your day-to-day experience, and also as a more techie user or a developer.

The intent is to provide Samsung, if they still lurk on XDA, feedback on how they can improve future development to make Android really smooth, even though the UI is not treated with priority, as it is on iOS.

As far as I am concerned, I didn't notice any difference from ICS to JB on a stock ROM; essentially, Project Butter doesn't exist for my device. The device still stutters where it did on ICS.

4.1.2 JB LSZ Ultimate 5.2 ROM, KSO Modem, Phil's LSZ kernel, Carrier: AT&T (US)
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] clandestino123:
I would agree with your assessment. I think that the stock JB is very stable, however there is no noticeable difference in speed compared with, say, LRQ.

When I press "contacts" or "phone" button, there is still a lag. My understanding of project butter (rightly or wrongly) was that these kind of lags are supposed to be almost eliminated.

Interestingly, when my wife's galaxy S was running slimbean 3.0, it was close to what I expected "project butter" to deliver. However I reverted her SGS back to ICS due to stability issues.

edit- I'm on LM5

edit 2 - Interesting that 90 people have viewed this thread so far, and nobody has disagreed with Incisivekeith's review. Perhaps we can conclude that "project butter" is not included in LSZ or LM5.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] crash-petard:
To my mind, Project Butter means an entirely GPU accelerated UI. That is what explain this "buttery" feeling when you drag down the notification bar, when you scroll in the browser, etc..

It is certainly activated in our JB roms, because if it was not the case, the rom would be much more laggier, and touch wiz would be the pain it has ever been since the Galaxy S.

However, I'm sure our PB is a far less efficient one than used in the nexii phones. You can easily tell, there are still some lag in the appearance of the notification bar (when opening an app, laoding something..), and the whole feeling is absolutely not like any Apple device (that I despise, of course :p).

I have none of the technical skills to give a more detailed answer, but I remain amazed by the fact our devices are not free of any lag, in spite of their double core, big GPU, 1gb RAM etc...
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Galaxtus:
To realize project butter you need a high speed camera. If you running heavily skinned OS has TW you will tend to see some lags. Remember Our note is almost year and half old.... :)

Project Butter and How it Works
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] crash-petard:
Thanks for the link !

But we don't have the choice, i don't think any android AOSP/AOKP rom includes project butter, am I wrong ? These roms feel more laggy than any touchwiz rom, though they also feel lighter. And it's a shame (I blame samsung) because they are innovative and functionnal.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Zlotin:
AW: Is Project Butter effective on the Galaxy Note?

As far as I understand, pb is not an acceleration for the hole system, but an acceleration for gui: no micro-lags in launcher, scrolling in Browser and apps. And it does really better, than ics for me. Just compare xda app on both systems and you'll understand what I mean
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] AA1973:
I tend to disagree on the part which states that these AOSP/AOKP ROMs feel more laggy than TW ROMs. As of today, I run Asylum ROM 25/02 which includes major improvements concerning the overall UI experience. It is snappy and smooth. I do explicitly avoid the term "buttery smooth" as it is misleading.

They are not finished products, that's for sure-but being heavily developed. :thumbup:

Any TW ROM running 4.1.2 won't be "buttery smooth" neither, whereas the leaked 4.2.1 ROM for the S3 already showed improvement and thus where helpful to update the Mali blobs for CM10.1, which are successfully implemented. They do work nicely!

If permitted to ask: when did you last try out an AOSP/CM ROM?

Side note: if you blame Samsung, you're always right! I fully agree.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] sohamssd:
I'd like to step in here, and this is entirely wrong: Project Butter was not included in jb for viewing in high speed cameras: it was mainly to reduce lag and stutteriness in Android to make the experience amazing for common, general public. Not for professional photographers.

Personally, when my one v is over clocked to 1.5 GHz and above ( and using a jelly bean ROM), the effect is mind blowing. I'd say the device comes near smooth as an iOS device, if not smoother. There are absolutely no lags and waits, and the device performs like a breeze.

Have you ever used a nexus device? That's the best implementation of a device blessed with project butter combined with the blessing of great developers of Google. I have not seen a nexus 4 lag ever. EVER.

Personally, I don't get what's it with galaxy note. I can't understand what's wrong with it to lag so much, I mean, sometimes it lags more than my one v which is a 1ghz single core processor ( I'm not talking about over clocking here).

I think only a professional dev can put light on this.

Sent from my One V
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] crash-petard:
I totally agree with you, and the fact that an incredible amount of great work is put in AOSP roms remains undeniable. As I said, I blame Samsung, and my respect for developers is unbounded. :)

My last try was for beerbong's paranoid android v2.99, and I've tried almost any rom in the original dev section. Still, it's been a long time since I have tried, so i'll have a look ! Of course, there are other things that make me stick to stock, SPen integration mostly (looks like there is still no way to use palm rejection in CM roms).

Anyway, I'm glad to see JB leaks help CM developers, I thought the only workaround required kernel sources.

@soham_sss

I see I'm not the only one wondering what could prevent the note from being smooth... :rolleyes:
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] hihipunkt:
For me, JB is very smooth. Don't forget, that our GNote has just that little Mali GPU which has to drive this huge 1280x800px (Macbooks of 2011 have this resolution :eek: ) screen. Based on that fact, JB is buttery smooth.

I suggest to set all animation times in the developer options of your phone to 0.5 (don't forget to reboot, to get the new speeds everywhere in the OS). It makes the Note feel much quicker and more responsive.

When you are there, also try "Force GPU rendering". Every app compiled with the 2.3 SDK has the GPU rendering flag set to off, this option forces it on. I haven't found any apps that don't like this setting and crash. Also, when you google for this, you won't find any apps neither that refuse to work.

I'm very happy with JB. It's smooth and the CPU doesn't have to render anything anymore. Nice!
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] crash-petard:
As I'm thorough, I tried Asylum ROM, as advised. :silly: One thing immediately stroke me : the notification bar is not smooth. It just isn't, there's a discomfort that should not be as if it was still CPU run. And I don't think I'm picky, it's a raw feeling. The rest of the rom is, indeed, pretty snappy (the browser appear much much lighter), but I really need this element of my UI to be impeccable as it come to smoothness, just like the home screens transitions.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] tommy_vercetti:
I was not aware that the Note uses Adreno? I thought it was Mali ;)
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] feartheanonymity:
+1 couldnt agree more.

Ive always had nit picks with my android devices (mainly samsung, some HTC's in the past) and have always experienced some sort of lag, with stock and custom ROMs.

But, correct me if im wrong, I believe this is down to the overlay put on by these companies, they cram the devices with ridiculous amounts of bloatware and eye candy and I feel that has an effect on the overall smoothness.

Ive yet to own a pure AOSP device (such as the nexus's) but i cant recall many people complaining about them.

But I prefer the looks of TW / Sense over AOSP (and ive tried lots of AOSP ROMs) so I accept that bit of lag for the overall look and functionality of things.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] hihipunkt:
Oops. I will change that. Nevertheless: That GPU just isn't the fastest anymore. ;)

And that AOSP is faster, is just normal when you don't unbloat your phone. It's the same with every other Android phone out there. Also AOSP doesn't offer multiwindow, I bet many people aren't really aware of the technical difficulties this brings with it. And therefore this phone is very smooth.

Also try tinkering with the build.prop a little.

windowsmgr.max_events_per_sec

persist.sys.use_dithering

persist.sys.use_16bpp_alpha

can help a lot with the "lag".

But I don't have any lag, so I'm not changing anything. Another thing to maybe consider: Do you have a corrupt install?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] incisivekeith:
The point of this thread is to discuss whether Project Butter is effective on the Note or not, WITHOUT any modifications.

4.1.2 JB LSZ Ultimate 5.2 ROM, KSO Modem, Phil's LSZ kernel, Carrier: AT&T (US)
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Bingoig11:
It isn't since AFAIK Samsung doesn't release source code for Exynos.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] AA1973:
If those on a TW JB ROM could download and install "Epic Citadel"(preferred via WiFi as it is a 150mb package) and play the demo. I bet it won't get beyond the 40fps in high quality..

I didn't advise to install Asylum and don't quite get the point of the notification bar. As long as Samsung fails to deliver "proper+sources" we won't get the real "butter" experience.

Apparently the leaked S3 ROM based on 4.2.1 went into a better direction as some Mali blobs could be used, but close to nothing from the 4.1.2 ROMs...

@incisivekeith It may be "project better", but not project butter.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] LoVeRice:
All we need is the official source code and then everyone will be happy n_n

_____________________________

via GT-N7OOO using XDA-2
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Galaxtus:
First of all this is not one v thread or an iOS speed competition. Different devices get different sources to work with. So it doesnt mean that one v is superior. I am happy that at least cm team is giving us nice smooth, fast and daily ROM. TW is for noobs. I don't care about other devices or bull**** until I choose them personally. High speed camera was just for fun...

Cheers from Hell.... :sly:
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] baz77:
once you remove bloatedstuff, like automated test, and about 30 others, own risk, reboot, flush cache/dalvik, you will notice considerable improvement, most of the time, but yeah it still stutters sometime.

damn endless tweaking, dont forget some to disable some triggers on boot fo apps you only need on demand.

all own risk buddies
[HTC EVO 3D] Deleted member 3020814:
Some background

I noticed this back when Sense ICS leaked out but it was never fixed. Then I moved on to AOSP roms which don't have this problem but I want my 3d back so I'm back to sense roms and the bug is still there even on newer sense roms. Note I haven't tried the Sense 4 roms as they are less functional than AOSP roms.

The bug

The cursor moves randomly. This is specially annoying when typing in forums. To recreate this bug it's simple. Just log into any forum and type a comment. Right away you may notice the bug after you type your user name when you click on the password field sometimes your username will flash in the password box momentarily. Now type out a couple of sentences in a comment box. At this point sometimes the cursor repositions itself mid sentence while you are typing. Again this is random so it doesn't always happen but typing fast (with either stock, swype or swiftkey it doesn't matter) seems to make it happen more often. Now if that doesn't make it happen try editing a word in the middle of the sentence not by selecting but by putting the cursor ahead of the word and hitting the backspace arrow. You'll notice the word will get deleted then magically reappear making it near impossible to edit text. Sometimes the entire word reappears and other times only some letters in it reappear.

What can you do about this?

If you are on a sense rom. Can you replicate the bug? What rom are you using? What browser? Do you know of a workaround?
[HTC EVO 3D] DjDom:
For some reason, Sense Roms do not like browsers.

I know people will disagree with me here, but, when running any version of Sense, Chrome would be horrible on it. It would flicker, lag, everything went wrong.

When I tried an AOSP or Cyanogen Mod Rom, Chrome worked perfectly.

It's a sense issue.

Stock browser should work fine though, as well as dolphin.
[HTC EVO 3D] mnomaanw:
Try the new chrome beta... It works perfect on all roms (not sure if the latest version will work correctly but the version that I have has no issues on any rom.)

@OP yes the cursor bug is still there.... Only solution for now is to use another browser.

EDIT : I see you edited it yourself.
[AT&T, Rogers HTC One X, Telstra One XL] guojunjay:
just like my title , few months ago i had bricked my xl. i sent back my phone to htc care centre. they repaired it for me after few days later. before i depair it my phone was 4.03 android hboot 0.95. after they repair for me it becomes 4.04 and hboot 1.14. yap, my question is i cant use the x factor to get super cid and s off my phone. to compound the problem is i cant use the s2w kernal. but i am able to use other non s2w kernal like elemental v1to v2.5. what could case this happened. i dicuss with someone he said is because of the ota update caused this hapenens , is this true , or maybe someone can give a solution to solve the problem. i tried all the ways in the forum .(sorry for my grammer mistakes and hopefully you guys can understand my sentence and get what i am trying to say)
[AT&T, Rogers HTC One X, Telstra One XL] a box of kittens:
Reboot into bootloader...you should already have supercid...what does it say besides cid does it say 111111111?