yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
We appreciate that you aren't new to the android platform or to the galaxy-line. Regarding the i777, you are in good company, and if we know NOTHING about any other device, we know the i777 very well. We're here to help.

You mentioned that you flashed several recoveries to the device. For future reference, the recovery for the i777 is packaged with the kernel, and is not installed separately. Even the often-troublesome temporary flash-recoveries that can be found, are actually a kernel/recovery combination. The s959g (straight talk's s2) has the same partition layout as the i9100 and i777 (and several other s2's), and DOES use a separate partition for recovery.

The fact that desktop ODIN indicates PASS when the flash is complete tells us that all of the factory nand images flashed successfully (including boot). It is very common that the device needs to have the factory data reset even after the factory images have been installed via desktop ODIN, but of course that requires access to recovery. If after a successful factory flash, the vol+ & vol- & power button held-concurrently-until-recovery (<--while NOT plugged into a USB port) truly doesn't get you to recovery, then that would be a new one for me as well; all other signs (as you have stated them) point to a correctly functioning device.

I'm hesitant to point you to flash a custom kernel;

there's some unnamed part of the procedure affecting the process, and flashing another boot image won't be helpful

-or-

there's a hardware failure, and flashing another boot image won't be helpful

-or-

you're using an incorrect method to get to recovery, and flashing another boot image won't be helpful

If you want to try it anyway, custom_kernel_twrp_v2.7.1.0.tar file via desktop odin might be worth a try.

^^this will trip the flash counter

^^this will install any custom firmware, but will not boot anything below android 4.4.x

I apologize for the hijack [MENTION=2916435]creepyncrawly[/MENTION]
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
On the contrary, your input is valuable and desired.

[MENTION=3684275]Berthfield[/MENTION],

If there was actual nand damage in any partition that was flashed, you would not get a pass in Odin, as far as I know. Since you are unable to boot into any recovery, this indicates a problem with the nand memory, possibly a corruption issue. Please try the following (you might try accessing recovery after each step, and if you get to it, perform a wipe data/factory reset):

Instructions to clear nand read/write corruption. Instructions are specific; do them in order, and don't skip.

Odin3 v1.85 is recommended.

1) Download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA. Without ticking Re-Partitioning

2) Flash the Tar.md5 of the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.

3) If that is successful you are done. If it is not, then:

4) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning. (Please observe normal bootloader flashing caution.)

5) Flash the Kernel, as in step 1.

6) Flash the full stock Gingerbread distribution, as in step 2.
[AT&T Samsung Galaxy S II SGH-I777] Berthfield:
I was away from home for a bit and so was unable to work with the phone. I have followed the instructions given above but I am still unable to boot.

I was using the "I777UCKH7-REV02-home-low-CL503881.tar.md5" file downloaded from the download repository, is this the right file or is there another Gingerbread flash that wold be better to use?

I am really puzzled at what exactly is happening with this phone.
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
Yes, that is correct. That is the original stock gingerbread from when the phone was first released.

I agree that it is a puzzle. Just to be sure, you followed the directions exactly? I'm not sure why, but the sequence will clear nand read/write corruption. You might try once again with the SBL -> Siyah Kernel -> Full Gingerbread, just to make sure.

1) Flash the SBL by itself and pull the battery.

2) Flash the Siyah kernel by itself and pull the battery.

3) Flash the full Gingerbread stock and pull the battery.

4) Enter recovery and perform a wipe data/factory reset.

5) Reboot.
[AT&T Samsung Galaxy S II SGH-I777] Berthfield:
Did the above and it is still a no go.

I have come to realize that the phone seems to think it is in recovery mode when I attempt to enter it as if it is plugged in while on the black screen it doesn't display the charging animation. This occurs regardless of the kernel/recovery combo that is on the phone and while in that state it is also not detected by the computer. To rule out possible problems I have also attempted the flash on a different computer with a different cable and it is still the same.

I remember reading about the ICS hard-brick bug and that it was possible to brick the phone is a large enough file was written to memory. Is it possible that this could be my problem or would Odin return a error if the chip was damaged? Also I am not sure if this matters but I find it odd that after flashing the Siyah kernel and CWM the phone still hasn't tripped its custom binary counter.
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
Evidently, this situation is beyond my experience.

My understanding is that if emmc memory is damaged within a given partition, then Odin will not be able to successfully flash that partition. While I don't know exactly how Odin functions, I believe there are checks within the flashing sequence for each partition. So as stated before, it is assumed that if you get a pass in Odin, there is not emmc damage, at least not within the various partitions that Odin flashes.

There was one case I remember with the emmc super brick bug where the phone would boot, but would not function correctly. Evidently in that case, a small portion of the emmc memory was damaged. The usual symptom of that bug was a hard brick.

The charging issue could be hardware or it could be a failing or failed battery. Have you tried another battery?

Flashing the Siyah kernel and not tripping the flash counter is more than a little odd. The code that governs that behavior is in the secondary boot loader as far as I know, and you have reflashed that. Please bear in mind that anything I say is speculation, but this issue give me a lot of reasons to think it is a failed hardware issue.
[Galaxy Note 3 Q&A, Help & Troubleshooting] david199318:
I have a at&t note 3 model N900A and today when I took it to best buy to update to kitkat the kind gentlemen told me my phone was rooted. I looked for how to tell if the phone was rooted and someone poinred out this 'supersu' app wich I have in my phone. I need help on how to install kitkat or how to install ROMS and also what does the supersu app do? How do I use it? any help would be appriciated please be patient I am a beginer with this step by step would be appriciate it. I need to upgrade to kitkat need my gps to start working need it for work lol. I really want to be able to learn how to isntall roms and flash updates thank you.
[Galaxy Note 3 Q&A, Help & Troubleshooting] pete4k:
For starters, this forum is for international Note3, you have separate at&t note 3 forum, search there as it will have specific rooting info for your model. If you pick up ROMS here you could brick your phone. Supersu is like a supervising program granting permission to access restricted areas and running in administrative mode. If any program requests privileged access, Supersu will ask you if it should grant it. Of course giving privileged root access to virus or some badly behaving program could be very bad idea. I guess you got phone from somebody else, since it's rooted and you don't know about it?

Actually there is a program in Play Store that can check if you have root or not, or you can try to access system files using ES file explorer and see if it works. I'm not sure if having Supersu by itself means you have root ATM, previous owner could have root and maybe he brought it back to stock unrooted leaving Supersu behind?

---------- Post added at 02:08 AM ---------- Previous post was at 01:59 AM ----------

PS.

I would strongly suggest for you to do some serious reading in this forums and have full understanding of everything before installing custom ROMS etc. there is very good chance of bricking your device, not covered by warranty, by making even seemingly trivial mistake.
[Galaxy Note 3 Q&A, Help & Troubleshooting] david199318:
thank you I appriciate the help.

Thank you so much for the help I think I posted on the correct forrum. Yes I bought mg phone of cl w a cracked screen im experienced changing phone screens and fixing them so I did it with the note 3 just didnt know it was rooted I think it is.
[Samsung Galaxy Gear] W@r10ck:
Hi Guys any of you encountered getting stuck on Samsung Gear manager when tryin to connect to Samsung gear 1? Im on DN3 V5 Rom with Agni Kernel and I have Samsung gear 1 running Tizen. I tried clearing Rom/Cache/Dalvic, reinstall gear manager app a couple of times including from this thread http://xdaforums.com/showthread.php?t=2677686. I reset my gear which makes it unusable :( it can pair through bluetooth.
[Samsung Galaxy Gear] Zueski:
Before reinstalling gear manager did u try force closing it and reconnecting? That usually fixed it for Me. Worth a try it. Sometimes it takes a couple tries to connect to my phone
[Samsung Galaxy Gear] W@r10ck:
Thanks for your suggestion. Ive tried that already but it just stays connecting.My bluetooth detected and paired my Gear with no problem.
[Samsung Galaxy Gear] dmitry.matora:
Make sure your build.prop DOES NOT claim your device is a Samsung. (and reboot for reverted build.prop to take an action) That fixed an issue for me
[Samsung Galaxy Gear] sony21:
I have the same issue with a BQ M5, and One Plus One too. The gear manager was working before with both phones, but when I upgraded gear firmware with first the BQ , gear manager doesn't connect anymore. Then I reset my watch, delete apps, clean mobile... restart... etc with no luck. I try to install old firmware and an old gear manager app (the one that worked before with this phone and gear firmware) and same result, stuck on "connecting...". This has happend with both phones after they both upgraded firmware on the gear s2 using gear manager. I think it's something with the upgrade process, that makes the gear manager unusable on the phone that downloads and performs the upgrade on the watch. I have to initialize the gear with a friends phone so that I can almost see the time...

searched the internet for a solution but same issue is happening already with Samsung phones to some people.

If someone have any clue on how to debug or try to trace this bug, any suggestion will be appreciated.
[Galaxy S 5 General] cuaran89:
Hello everyone

I want to flash a new, fast and nice performance ROM on my Galaxy S5, but i want to keep the stock camera and calendar app.

As far as i know, if i install a new ROM it will delete and replace the stock camera and calendar, so my question is, which ROM Omega or Cyanogen let me do that .

Thank you very much for your help
[Galaxy S 5 General] CZ Eddie:
Omega will let you keep the stock camera. Not sure about the Calendar.

You lose both in CyanogenMOD for sure.
[Galaxy S 5 General] SquireSCA:
Just out of curiosity, what don't you like about the stock ROM? The performance is on par with any of the alternat ROMs out there, so why risk borking your phone or losing apps that you want to keep?

Just get a different launcher to modify the look and feel of the phone to your tastes.
[Galaxy S 5 General] whtvr:
you're mostly correct but there's one thing that it's very different between TW ROMs (that I've tried) and AOSP ROMs (like CM or Carbon) - the notification and quick settings panels; i'm not sure how much these can be customized on TW ROMs and how easy it is to do so but in their default implementation I find CM's notificaiton and quick setting panels vastly superior to those of TW's
[Galaxy S 5 General] SquireSCA:
In what way? Been awhile since I used an AOSP ROM...

I mean, the notification panel is such a trivial thing most of the time. Shows battery, clock and basic alerts... To me, it isn't worth the risk of messing up a good phone, or introducing instability or missing features, just to tweak the battery alert or whatever...

I was all into ROMs on older phones like the DroidX, Thunderbolt and some others... because the stock roms were crap. Issues, random reboots, horrible lag, etc... The ROMs got the phones to work properly, they way they were meant to.

But on my LG G2 and now this GS5, I just don't see the need. There is no lag, everything works beautifully, and when I research the ROMs, there is always some bug, some missing feature, something that just doesn't work right... So I don't see any point in switching, when you have 20 launchers to choose from that can make your phone look and feel any way that you want, with no risk and with not having to give anything up...

Each generation of phone and release of Android, makes ROMs more and more obsolete, IMHO... I think that 90% of the people that use them today, do it either out of habit, or just because they want to show off to their nerdy friends. :)
[Galaxy S 5 General] Poine001:
Nice work!
[Galaxy S 5 General] cuaran89:
Well, you are so right, I will keep my stock ROM with the apps I want. But, now I have other question, my GS5 is on ATT and I want to remove the bloatware apps that I don't use, do you know where can I find the complete list for this carrier. Thanks for your time.
[Galaxy S 5 General] whtvr:
What I meant by the notification panel was not just the bar across the top of the screen with a bunch of icons but also the pulled down notification menu as well as the quick settings panel. On TW half of the screen's real estate of the notification menu is taken by a row of toggle icons (which are duplicated on the quick settings screen), two buttons that launch apps that I never used (S Finder and Quick Connect, I don't even know what these apps actually do) and a brightness slider (which in fairness can be disabled, if I recall correctly.)

Then you get to the quick settings panel on which there's also not that many shortcuts that I would use (most of which are for the extra features of TW which I also have no interest in) and there's quite a few that I'd love to see there but they're not available. On CM, on the other hand, the notification menu is clean and simple; it's not bl(essed|oated) with some additional buttons which you may or may not use. The quick settings screen is also much more customizable than that of TW's which only allows for rearanging of toggle icons. On CM you can add, remove and freely arrange all icons on the quick settings screen. And yes, you can add that row of icons to the notification screen and get rid of quick settings altogether, if so you desire.

Some toggles that are available on CM but not on TW are screen time out, lock screen disable/enable or torch. Personally I happen to be using these numerous times throughout the day so while it is only a minor inconvenience to go to the settings and change something manually it adds up quickly if you have to do that often.

To summarize my little rant - the notifications menu and quick settings panel section of the system's interface is used quite often by me (and I'd say others as well) and I simply find inadequate what TW has to offer here. The rest of the TW is either virtually the same as any other version Android or can be easily "fixed", example of which was mentioned by yourself (the launcher).

Now, I agree with you that it may not be worth it for some people to "risk" using a custom AOSP ROM but it can't be denied that by definition such ROMs offer a much greater flexibility and allow one to use their phone exactly how they want (to a greater degree than can be said about TW). Differences can ofcourse be described as "minor" but whether they're significant is for everyone to decide on their own. After all, if there was no need for custom ROMs (whether it's just showing off to nerdy friends or some other reason) people wouldn't create them...

Have a look in this forum. There's a good few "debloated" ROMs over there, and a list of what's removed is sometimes included. As for what to remove the apps with, I would personally recommend Titanium Backup.
[AT&T HTC One (M8)] SuperAndroidTech:
i need to go back to the stock att rom but i cant get s-off to use the RUU so can i have the link to the stock AT&T rom so i can flash it
[AT&T HTC One (M8)] Wonders_Never_Cease:
Search is a great thing,its on the htc site support for att htc one m8,dont need to be soff to use the ruu,but you will need to lock bootloader again to run it
[AT&T HTC One (M8)] iRunLinux:
You dont need s-off for RUU just use the ruu in the general att section of the m8 forums
[AT&T HTC One (M8)] redpoint73:
And more reading, too.

OP is obviously unclear on the basic facts and steps, and needs to learn more before proceeding.

S-off is not needed to run RUU. RUU will install stock ROM. And why do you need to RUU in the first place?
[AT&T HTC One (M8)] Wonders_Never_Cease:
Very unclear,this was a post i answered for them awhile ago.... http://xdaforums.com/showthread.php?p=53560486#post53560486
[AT&T HTC One (M8)] i4GS:
Has been answered before; and posted, try this:

http://xdaforums.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486
[Motorola Atrix HD] TecknoFreak:
Reseved
[Motorola Atrix HD] TecknoFreak:
Hey guys let me know if this work out as I lost my phone and I cant really test now. But hopefully the touch offset have been fix and incorporated to this work around.

Finger Crossed and thanks to all that have input me in a way to work with this project in special to dhacker.
[Motorola Atrix HD] bmatney:
Downloading and will report back.

---------- Post added at 09:51 PM ---------- Previous post was at 09:43 PM ----------

Touch points are still off.
[Motorola Atrix HD] Byakko Custom:
I saw the date and thought that we got a fully functional twrp...

I should have read the comments...

BTW, Doesn't twrp have ORS?

53 65 6e 74 20 66 72 6f 6d 20 6d 79 20 41 74 72 69 78 20 48 44 20 75 73 69 6e 67 20 74 61 70 61 74 61 6c 6b 2e 2e 2e
[Motorola Atrix HD] quasihellfish:
Would really love to test this but unless I'm a complete buffoon, I can't find a download link. OP only mentions downloading from the official TWRP page, but there doesn't seem to be anything for this device.
[Motorola Atrix HD] Byakko Custom:
OP Took down the link since it's still not working properly.

No point in flashing something that's not working properly right?

53 65 6e 74 20 66 72 6f 6d 20 6d 79 20 41 74 72 69 78 20 48 44 20 75 73 69 6e 67 20 74 61 70 61 74 61 6c 6b 2e 2e 2e
[Motorola Atrix HD] TecknoFreak:
True to this, I was hoping as on my device seen to be working fully except that I can test now because I made changes to it to update it and didnt saved my old settings. So buying another atrix hd as we speak this week to fix and correct the problem.
[Motorola Atrix HD] oscar the grouch:
I have a spare. I bought a spare off ebay last week. if it helps ill let you borrow it:good:
[Motorola Atrix HD] quasihellfish:
Wait. You have to buy ANOTHER Atrix HD?! Or is this the same replacement you mentioned previously?

You really need to be more careful with these things... ;)
[Motorola Atrix HD] TecknoFreak:
yeah bro I lost mine day before yesterday. lol
[Motorola Atrix HD] mega_man:
motorola photon q has offical twrp support cant we port it somehow for atrix hd ?
[Motorola Atrix HD] Byakko Custom:
The problem isn't porting/building for our device, it's the screen.

For some god-forsaken reason, only our device out of the entire moto-msm8960 branch has the "off touch points" issue.

53 65 6e 74 20 66 72 6f 6d 20 6d 79 20 41 74 72 69 78 20 48 44 20 75 73 69 6e 67 20 74 61 70 61 74 61 6c 6b 2e 2e 2e
[Motorola Atrix HD] oscar the grouch:
any luck with this. philz_touch_6.50.6-moto_msm8960 is giving me issues and he responded to my queeries
[Motorola Atrix HD] palmbeach05:
And why are we using a philz touch that isn't officially compatible with our device, esp when, over in the RHD thread, it clearly states that the last pre-kk bl compatible version is 6.48.6?

Sent from my MB886 CM10.2/4.3.1
[Motorola Atrix HD] oscar the grouch:
Because apparently i missed that. thanks for the sarcastic clarification.
[Motorola Atrix HD] quasihellfish:
Any progress on this [MENTION=1907864]Technofreak[/MENTION]? My phone is currently encrypted, and apparently TWRP is the only recovery that can deal with an encrypted /data partition. Before I completely nuke my phone back to stock, I'd love to test an alternative.
[Motorola Atrix HD] TecknoFreak:
I made it to work but the buttons still offset so I can't release like this until fix. But I extremely busy at work so we will see
[Motorola Atrix HD] quasihellfish:
Thanks. No pressure from me, I know what busy work is like...
[Motorola Atrix HD] oscar the grouch:
phil has discontinued the philz touch recovery.
[Motorola Atrix HD] chrisb906:
Any progress? I love twrp. ?
[Motorola Atrix HD] TecknoFreak:
Guys no further development. Im extremely busy at life at rhis moment and i have too many projects going at once.
[Motorola Atrix HD] [] AL []:
Why not update the OP with an "On Hold" status notice??
[Motorola Atrix HD] quasihellfish:
Yes. Project is on hold. See previous replies.

Sent from my mobile phone thingy.
[Motorola Atrix HD] chrisb906:
Deleted
[Motorola Atrix HD] quasihellfish:
But why? Literally two posts above yours gave you all the info you needed.

Stop asking.

Sent from my mobile phone thingy.
[Motorola Atrix HD] quasihellfish:
...sigh...

Really, the guy told you twice he was too busy, and you kept asking.

I think you need to re-read the sequence of events over the last 2 pages that got you to this point before either of us start bashing each other.

Sent from my mobile phone thingy.
[Motorola Atrix HD] marknoll:
K

My bad
[Motorola Atrix HD] quasihellfish:
aaaaand now you're deleting all your old posts and using multiple user accounts. Awesome.

I'm done.
[Motorola Atrix HD] chrisb906:
I told u I couldn't delete the dupe account. I had to go on a dang computer to delete the acct..wow...relax. at least I was being honest
[Motorola Atrix HD] Any PlayStore:
[Recovery]TWRP 2.8.0.0 for jbbl + kkbl

4.4.2 Bootloader ONLY

Fastboot image only

-------

4.1.2 Bootloader ONLY

Fastboot image only

Source

Who can tell me it is stable for Atrix HD?
[Motorola Atrix HD] quasihellfish:
Have you tried it? My gut tells me that it will boot, but the touchscreen points will be off. This makes it unusable, and has been the problem from the beginning. Feel free to flash it and report back!
[Motorola Atrix HD] bmatney:
I'll give it a shot. Back in 5 minutes.

---------- Post added at 09:38 PM ---------- Previous post was at 09:32 PM ----------

Installation aborted. It wouldn't even flash in philz.

---------- Post added at 09:42 PM ---------- Previous post was at 09:38 PM ----------

Haha my bad. I tried flashing the zip, but let me extract the IMG then flash it again with flashify.

---------- Post added at 09:46 PM ---------- Previous post was at 09:42 PM ----------

Yup. Bad touch points.
[Motorola Atrix HD] Any PlayStore:
At this point I think the best philz.

You can refer to the source.
[Motorola Atrix HD] palmbeach05:
Philz has essentially been retired for pre kk devices. If you want the latest recovery for a jbbl, see my 6.0.5.1 CWM thread. Its up to date with the correct version, i'll post a full update to it to include any recent changes on monday (its still 6.0.5.1 though)
[Motorola Atrix HD] Any PlayStore:
Thank you for your work. I like Recovery Touch.
[Motorola Atrix HD] dankimani:
Hey [MENTION=3692819]TecknoFreak[/MENTION]

Links not visible.

Kindly update. Urgent.

Thanks