yashsingh1/xdaforums huggingface dataset:
[T-Mobile LG G2x] blackbeasst:
source? i have a dw and i got nuttin.
[T-Mobile LG G2x] vn00914361:
Official OTA is v21e

Unofficial OTA is v21y

v21y is highly NOT RECOMMENDED!!!

You can try by offline-upgrading back and forth both versions and check out the battery life
[T-Mobile LG G2x] nightf0x:
How is 21y unofficial?? It's clearly stated on t-mobile website..
[T-Mobile LG G2x] vn00914361:
Being stated on website doesn't mean it's official. T-mobile pulled it down and has been working on random freezing and signal drop since then
[T-Mobile LG G2x] russell956956:
I accidentally thanked you so your welcome :D, but how is it not official? From what i understand it was an official update from them, i dont think it was a leak either as they even gave out an update schedule, maybe they pulled it but its still 'official' from them.
[T-Mobile LG G2x] vn00914361:
It's official when it's ready and available for users to download. Check your phone if it can actually download it OTA
[T-Mobile LG G2x] nightf0x:
So it's unofficial according to you then. I have no idea where you are getting information that it was pulled.
[T-Mobile LG G2x] blackbeasst:
my wife got her ota last night. updated with no probs :D
[T-Mobile LG G2x] Jomyah:
I got mine last night too. I guess unofficially I got it.
[T-Mobile LG G2x] ickster:
Thank you to those who answered the actual question.

Wanna bet I don't get it? That's how I roll LOL.
[T-Mobile LG G2x] jaywillsoul:
I tried to do the update again last night since some people were getting there's over the weekend. Still a no go for me.

Sent from the last drop of EaglesBlood: 4.0.4 G2x
[T-Mobile LG G2x] edekalil:
I did the about phone and search for updates and my phone downloaded something but then said it was up to date. Nothing changed on the phone.
[T-Mobile LG G2x] ickster:
But you're not stock? You won't get the OTA by my understanding of what I've been reading. You may get a notice?

Still none for me.
[T-Mobile LG G2x] g2uzer:
LOL!!
[T-Mobile LG G2x] g2uzer:
Not yet, still waiting
[T-Mobile LG G2x] str8killinya:
Girls G2x got notification when we woke up today. Took about ten minutes to complete, it feels pretty smooth so far

Sent from my T-Mobile G2x

AOKP Build 35
[T-Mobile LG G2x] desynch-:
v21y is not recommended? Says who. Everyone who's switched loves the update, me included. Battery life is wicked great.

No random freezes, or reboots either.
[T-Mobile LG G2x] g2uzer:
Yup, is what I keep reading that people like it . Sucks that I haven't gotten mine tho
[T-Mobile LG G2x] FourM:
been using cm7 for quite some time. saw there was the V21Y KDZ leak so I tried it out and it was awesome. went back to V21E stock (rom and recovery) and have been waiting a week for the OTA. still nothing. hopefully it gets released on May 14th like Tmo says
[T-Mobile LG G2x] lindel:
Nothing via OTA, tried the KDZ update method and successfully bricked the phone. New one is on the way from T-Mobile...
[T-Mobile LG G2x] GTWalling:
If you had it installed via the KDZ, why did you go back to wait. It was not really a leak, was just posted to the LG Upgrade site before T-Mobile was ready. I have been running the KDZ version. The KDZ file is the same as the OTA and the one that will be up on the LG Upgrade site. Just curious.
[T-Mobile LG G2x] FourM:
I wanted to see if it was the actual release or not. Got the "new" kdz via LG Support Tool on May 14th and didn't see any difference.
[Optimus One, P500, V General] devdan:
Dear all,

I have some issues with my LG OO and stock rom 2.3.

There are many threads about improving GPS but they are all related to aGPS. I don't use the mobile connection for the fix, only predownload GPS data via GPS status, so all those fixes about time servers do not apply.

I have the following issues:

1) Sometimes about 10 stallites are found and also fixed within seconds but still, the phone will not get a GPS fix, never, no matter how long I wait. This can be fixed by disabling and enabling the GPS via the status bar button. Then the GPS is fixed within seconds. Anybody has an idea why this happens? Why is there no fix although I have perfect reception.

2) GPS fix is present but suddenly, the GPS icon will disappear from the status bar and no app will receive any GPS data. This is also fixed by disabling and enabling GPS via the status bar button.

Those issues are specially annoying when using background services because in that case you rely on a stable GPS connection.

Any ideas?

Best regards,

DevDan
[HTC EVO 3D] chadharrop:
Need to fix. Only some roms and modified supper wipe. Is there something I am missing.
[HTC EVO 3D] evo bryan:
Best thing I can say is if you have a spair sd card and download from pc as well
[HTC EVO 3D] laie1472:
Try reflashing your recovery. Then try this

http://xdaforums.com/showpost.php?p=10878511&postcount=8311

To see if will help any.

#Root-Hack_Mod*Always\
[Wildfire Q&A, Help & Troubleshooting] StevoMark10:
Hi,

I don't know how to install the Cyanogenmod on my HTC Wildfire:o Can someone help me? My MSN: hafc10@live.nl

Thanx!
[Wildfire Q&A, Help & Troubleshooting] usaff22:
Guide. Sig. Below. Those will help you find the mystery rooting guide.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

No, seriously. There are a thousand and one guides to root the Wildfire. Please use the search function or your natural eyes before asking a question. There's one in my signature.
[Wildfire Q&A, Help & Troubleshooting] StevoMark10:
Thanx

Thanx;)
[Wildfire Q&A, Help & Troubleshooting] nav33n:
It's Simple

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

First of all you need to downgrade your HBOOT from 1.01.0002 to 1.01.0001 and S-OFF using buzzdowngrade

software.:)

Now i'm useing

Cyanogen mod 7.2

in my HTC Wildfire A3333.

Rooting is very simple.
[Samsung Epic 4G Touch] sfhub:
Reference Section

A) Resources

a1) tar.md5 versions of One-Click (for regular ODIN):

SPH-D710.FE07_CL519197_ROOTED-sfx.exe [Mirror1 / Mirror2] [MD5: b37d2a358c3cef3a2e2e182b59e6a81a / Size: 304,110,919]

SPH-D710.FE07_CL519197_ROOTED_NODATA-sfx.exe [Mirror1 / Mirror2] [MD5: 49d4280ea37dd3fc52fbbf70ef992302 / Size: 303,121,865]

B) (Individual) STOCK FE07 ODIN/CWM Components

b0) Odin3 v1.85 (windows)

- these are ODIN tar.md5 files bundled in a 7-zip self-extractor

- ONLY use

PDA Button

for any of the following

- Windows - Double-click on the self-extractor and choose your ODIN directory

- Mac/Linux - Use 7-zip to extract

b1) [ODIN] FE07 Modem [Mirror1 / Mirror2] [MD5: e743fac81db162edb636177eaa89fc71 / Size: 4,094,526]

b2) [ODIN] FE07 Kernel [Mirror1 / Mirror2] [MD5: 0257bf91d3dac617162d2fe5f02aabd5 / Size: 6,077,404]

b3) [ODIN] FE07 ROM [Mirror1 / Mirror2] [MD5: e4c11dd1432ac07c6659b4eb9d3947e3 / Size: 285,590,878]

b4) [ODIN] FE07 ROM + root [Mirror1 / Mirror2] [MD5: 14c4e4568b707c6789bdd7b4db72132d / Size: 285,565,228]

b5) [CWM] FE07 Modem [Mirror1 / Mirror2] [MD5: 7addab11150f922e2e0fa8c3b1850383 / Size: 5,133,616]

b6) [CWM] FE07 Kernel [Mirror1 / Mirror2] [MD5: b27f482ea0b9a0ebcedb719617896a2e / Size: 6,035,270]

b7) [CWM] Repack - FE07 Kernel (Unlocked Recovery) [Mirror1 / Mirror2] [MD5: ffa2f265c1cdb8f2827c3bcba7f953b5 / Size: 6,036,030]

b8) [CWM] Repack - FE07 Kernel (Plus) [Mirror1 / Mirror2] [MD5: 1e45087a6d150000aadfd1d5607d4c87 / Size: 6,021,208]

- Plus = unlocked recovery, initd, bootanim, usb-ms, adb-root

C) FAQ

c1) Windows tells me "Unrecognized device (code 42)" and ODIN OC doesn't see my phone

c2) What happened to USB Storage in ICS, how do I get the old GB behavior back?

c3) How do I run Auto Root, ODIN OneClick, or ODIN on Mac?

c4) What about the notification bug?

c5) How do I get Sprint TV to work?

c6) How do I get wifi tethering for ICS ROMs?

c7) How do I enable the stock ICS launcher instead of TouchWiz?

c8) How do I do screen captures in ICS?

c9) How come the wallpaper doesn't scroll?

c10) How do I resolve Contacts app Force Closing?

c11) How do I access the ##DEBUG# menu?
[Samsung Epic 4G Touch] sfhub:
Before anyone asks, yes it is

4.0.4

jase33 has kindly put together a lite ICS theme available in this post

CWM update.zip for FE07 Modem and Kernel are in 2nd post.

Scrolling feels slightly tuned from FD26, but not a major change. Some will still feel it is too fast. Some will think it is just right.

I will try and keep the following updated as people post experiences

Summary of Comments

Android OS Battery Usage -

Fixed

Android OS high battery usage appears to be fixed. This may have just been a cosmetic issue in the past, but people did not like seeing Android OS with a high percentage on the Battery usage screen. Now the Android OS entry has much lower usage % and in some cases won't even show up anymore if you just boot your phone and do nothing.

http://xdaforums.com/showthread.php?p=25831003#post25831003

Social Hub Widget -

Fixed

Reports are this app works now - thanks erasable

http://xdaforums.com/showthread.php?p=25829988#post25829988

WiFi with short DHCP leases disconnects often -

Fixed

Reports are WiFi disconnects associated with short DHCP leases doesn't occur anymore - thanks weboide

http://xdaforums.com/showthread.php?p=25841783#post25841783

Confirmed - thanks bloooctober

http://xdaforums.com/showthread.php?p=25842645#post25842645

##DEBUG# lock code not known -

Fixed

In GB releases ##DEBUG# asked for your MSL. In ICS releases ##DEBUG# asks for a lock code, which is 777468 (SPRINT) - thanks bubur_bewok

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

Notification Sound Bug -

Fixed

The issue with the notification sounds going away on their own has been fixed since FD24. It is being listed here so you don't confuse it with the Notification Light Bug (below)

http://xdaforums.com/showpost.php?p=25292863&postcount=3

Notification Light Bug -

Present

The notification light does not blink while charging, thanks someguyatx:

http://xdaforums.com/showthread.php?p=25832058#post25832058

Chrome Stutter-Scroll -

Present

Multiple reports of chrome stutter-scroll still being present

MTP / USB Mass Storage -

Present

There is still no UI to switch from MTP mode to USB Mass Storage Mode. I think this is a mistake because many PCs do not support MTP or don't support it well. USB Mass Storage Mode allows your phone to show up as a USB drive when you plug it into a computer and is much better supported. Workaround and issue is covered in more detail here:

http://xdaforums.com/showpost.php?p=24010029&postcount=889
[Samsung Epic 4G Touch] Vgamer4550:
Awesome, thanks SF...cant wait to play.
[Samsung Epic 4G Touch] jazzneel:
2nd!!woohoooo
[Samsung Epic 4G Touch] weboide:
NEAT! Thanks sfhub
[Samsung Epic 4G Touch] monkeychef:
That's a lot of details.
[Samsung Epic 4G Touch] weboide:
haha edited...
[Samsung Epic 4G Touch] kingdazy:
Hot diggity damn!

Sent from my calculator watch.
[Samsung Epic 4G Touch] weboide:
How's battery life? *troll*
[Samsung Epic 4G Touch] scarmon25:
Only have one question. I didn't see it in the FAQ's. How is the scrolling on this build? Also. Once again Sfhub you've went and outdone yourself. Thanks.
[Samsung Epic 4G Touch] nibrwr:
Excellent! Thanks
[Samsung Epic 4G Touch] sfhub:
CWM update.zip for kernel and modem are done uploading and in the 2nd post.
[Samsung Epic 4G Touch] RainMotorsports:
Alright im awake im awake lol. Putting files on mirror 2 now. Enjoy the speed :)

Rooted One click, modems and kernels up.
[Samsung Epic 4G Touch] sfhub:
I'm a bad person to ask because it was never to the point that it really bothered me.

Having said that, it feels tuned to be less sensitive from last release, but there will be some people who still think it is too fast.
[Samsung Epic 4G Touch] Imadroider:
Sweet! Thx again to all involved!
[Samsung Epic 4G Touch] kobridge:
Thanks sfhub!

4.0.4! Can't wait any more!
[Samsung Epic 4G Touch] tpapa:
I'm new to flashing so this may be a dumb question - I used the previous one click FD26 rom and then un-rooted using auto root....can I flash this right on top of what I have now or do I have to go back to GB?
[Samsung Epic 4G Touch] tmeader:
Hope they didn't mess with it too much. I felt FD26 was just about a perfect compromise between speed and controllability. Looking forward to giving it a shot later.
[Samsung Epic 4G Touch] scarmon25:
It wasn't that bad on the last one. Just needed more of a calibration to me. But yeah I feel ya. Everyone has their own preference and some will say its perfect and others will say still has a "bug" in it. Thanks for the quick reply.
[Samsung Epic 4G Touch] bigpeng:
Look back 1 page when sfhub answers overstew, there is a way to check at bottom.
[Samsung Epic 4G Touch] slick_rick:
edit: sfhub beat me to the answer

Yea I got it
[Samsung Epic 4G Touch] sfhub:
Presumably if the comments in the source code are accurate (which we do not know for sure) your fwrev is not affected by the bug. If the 2nd number came up as 0x25 then it would be one of the ones affected and the FE07 kernel would attempt to patch the problem at startup. Since your 2nd number is 0x0, the patch code feels you are unaffected by the bug and will do nothing.
[Samsung Epic 4G Touch] Esoteric68:
Okay when my terminal window opens I have root@android:/ #

when i try to type in the command shell@android:/$su it says not found. I'm sure it's a simple step I'm stupidly overlooking.

Also, if I got my phone way back in September am I more or less likely to have the appropriate EMMC hardware?

Should I maybe have mentioned I'm on Blu Kuban at the moment? lol Do I need to flash this first and then go through the steps?
[Samsung Epic 4G Touch] rob97ss:
It said App not installed!! I flashed both using Mobile Odin, pulled zimage.. Tried reinstalling from market, gave me error.. Reflashed stock kernel, it worked.. Maybe I'll try with Cwm just for ****s and giggles.. Anyway not a big deal.. Thanks

Bobby O'S Epic Touch
[Samsung Epic 4G Touch] sfhub:
Just skip su, you already have a rooted shell (as denoted by the # sign). Type the rest of the commands.

Also don't type the "shell@android:" stuff. Only the BOLDED words are needed. The other stuff is just the shell prompt that the terminal spits out at you if you are using certain shells.
[Samsung Epic 4G Touch] Optimal Carnage:
I was hoping to give Calkulin's Bare ROM Converter a go this time around. I've currently running the

STOCK FE07

Modem/Kernel/ROM i've continued to use the preserve data one click odin since who knows lol. My question is how do I go about flashing this zip if I dont have a custom recovery? I've been to spooked to really screw with CWM since everything stock works great. I guess i could always just navigate the system apps just hoping there was an easier way thats all. Sorry for the run on but my daughter like watching me type with more then one finger lmao
[Samsung Epic 4G Touch] sfhub:
When you say ICS messaging, are you talking about the stock messaging app used for SMS that is in the dock bar by default?

Is there any chance you have a /system/etc/init.d directory with files in it?
[Samsung Epic 4G Touch] slick_rick:
Sounds good! The one time I actually used CWM Touch to flash an ICS theme on an ICS rom, my phone didnt brick so I guess thats why. I got my phone launch day so maybe those aren't affected? Thanks for the info sfhub, I'll make sure to still be careful when flashing in unlocked recovery.
[Samsung Epic 4G Touch] sfhub:
You can either

1) use Auto Root to install FD02+CWM-Rogue and use that to flash this

2) pull the zImage out of the zip file and flash using Mobile ODIN

3) wait until this evening and use Auto Root package to install it (I'm uploading a revised version)
[Samsung Epic 4G Touch] rob97ss:
Not the stock one..Ics app from play store..

Bobby O'S Epic Touch
[Samsung Epic 4G Touch] Esoteric68:
MAG4FA

0x0

0x0

Is there anything I could've typed incorrectly that would give skewed results? I never got that shell@android so I went with the root@android:/ # line.
[Samsung Epic 4G Touch] sfhub:
I've yet to actually see a fwrev (2nd number) that matches what the source is trying to patch so please don't get a false sense of security that you are safe. They could be patching an entirely different problem than what we were encountering.
[Samsung Epic 4G Touch] Esoteric68:
So still don't try to flash ROMs in ICS recovery, right?
[Samsung Epic 4G Touch] sfhub:
Well, if you'd like to contribute to the knowledge base in trying to determine if this bug is fixed then go ahead and flash. There is a reasonable chance that you are not affected. Should you get a /data brick then we know for sure the fix either isn't fixing what we think it is fixing or isn't doing it right. I would only suggest doing so if you have avenues to get your phone replaced if something goes wrong.

At some point, someone is going to have to be the guinea pig to figure this out or we will just live in eternal fear of flashing in ICS.

I would just give it a day or two and see if Garwynn and I can get more info.
[Samsung Epic 4G Touch] Esoteric68:
If I decide to do this, I would first need to flash this one-click and then attempt to flash a ROM in the stock recovery, yeah?

I'm running your repacked plus on Blu Kuban and I've been flashing updates to the ROM, and a kernal but haven't actually flashed another ROM.
[Samsung Epic 4G Touch] bigpeng:
Yea I got the same thing you got sfhub and like I said earlier, I used your FD26 plus stock kernel to flash Calks format all and his 1.5 rom and worked perfectly.

I'll be the guinea pig if you tell me what I need to do to test if it's actually fixed. No fear here. Awaiting your reply. I get my phones replaced for free.

Edit: since yours and mine match i guess i couldn't be guinea pig? I've already flashed calks with your stock FD26 plus kernel.. :confused:
[Samsung Epic 4G Touch] sfhub:
You don't have to flash the FE07 OneClick. The fix is in the kernel which is shared between Android and Recovery. You could just flash format_all from calk and then flash your ROM and/or modem. If you are extra bold try a wipe data/factory reset from recovery. That is the one causing /data bricks most often.
[Samsung Epic 4G Touch] JohnCorleone:
I swear, if anyone gets brave, starts going flash crazy, then bricks and blames sfhub I will go ballistic and I am generally a calm guy. Be patient and let the geniuses look in to it for a few days. Seems like they are getting close so be patient gang. I am as happy about these findings as anyone (ask any former OG Epic owner how much I used to flash and test) but be careful for a little while longer. I hate to see anyone brick

Sent from my SPH-D710 using Xparent Blue Tapatalk 2
[Samsung Epic 4G Touch] sfhub:
I would just start by flashing various ROMs and doing wipe data/factory resets from recovery.

If you are especially bold, use ROM manager to fake flash CWM Touch and do wipe data/factory reset a couple of times from there.

It would be nice to find one person with the affected fwrev (2nd # 0x25) to test the other scenario. In your case we'd be gathering supporting evidence that you are unaffected by the bug, but wouldn't actually be able to verify the "fix" is in play.

However, even gathering evidence that fwrev 0x0 is unaffected by the bug would be useful as it would allow people to flash more comfortably once they determine their fwrev.
[Samsung Epic 4G Touch] bigpeng:
I won't blame no one. But looks like all i need to do is flash the FE07 plus kernel and then wipe data etc with the recovery and flash any rom after that, correct? :D
[Samsung Epic 4G Touch] Esoteric68:
No worries. I always take full responsibility for my own actions.

He's given the appropriate warnings and suggestions, anyone who decides to undertake this does so at their own peril. But he's right, someone has to take the plunge at some point.
[Samsung Epic 4G Touch] bigpeng:
Okay, thanks sfhub. I'll let you know here soon.
[Samsung Epic 4G Touch] sfhub:
Pretty much. AOSP and AOKP seemed to like to trigger the problem also so you could try flashing those roms and doing wipe data/factory resets.

Keep in mind many ROMs include their own kernel, so after flashing each ROM, you should go back and install the FE07-plus kernel. I'll provide a .tar.md5 version you can flash through ODIN since it is more convenient. It is not as important in your case, if we are correct that you are not affected by the bug, but it would be important for someone with fwrev 0x25
[Samsung Epic 4G Touch] JohnCorleone:
Oh, not singling you or anyone else out. The point I was trying to make is that sfhub has made plenty of warnings so if anyone decides to help the community and test, thank you and remember you chose to do it.

Edit..hell I am going to check what I have and probably go for it myself but I am choosing to do so

Sent from my SPH-D710 using Xparent Blue Tapatalk 2
[Samsung Epic 4G Touch] autoprime:
has anyone confirmed they have a 0x25 firmware?

0x0 for me.. and it seems everyone else in here as well.

and just to be complete.. I have MAG4FA.
[Samsung Epic 4G Touch] JohnCorleone:
Going to check mine now...
[Samsung Epic 4G Touch] sfhub:
If someone knows someone who still has a /data brick phone lying around they can also check their fwrev since presumably they can boot into custom recovery and use adb with it.
[Samsung Epic 4G Touch] bigpeng:
Will this kernel let the ASOP/AOKP roms boot up fine, sfhub?
[Samsung Epic 4G Touch] Febby:
I just kinda dropped in here and started reading. How do i check for a 0x25?
[Samsung Epic 4G Touch] sfhub:
I looked at the changes they made a while back and I'd be surprised if this kernel allowed them to boot.
[Samsung Epic 4G Touch] sfhub:
There is always the possibility we didn't read the arguments for the fix properly and are checking the wrong fields, which is why I stress all this is very preliminary. I would feel more comfortable if we could at least find 1 person with 0x25, even better if that person had already had a /data emmc brick prior.
[Samsung Epic 4G Touch] bigpeng:
Okay, i guess. I'll just wipe with recovery and then flash aokp/asop roms if it boots, I'll have to get back to FE07 plus kernel somehow.

Edit: waiting for further findings.
[Samsung Epic 4G Touch] locoboi187:
How do I check? Last I read was that sfhub would make a write up but I think I missed it
[Samsung Epic 4G Touch] JohnCorleone:
MAG4FA

Ox0

0x0

Damn, I was hoping I could help with this. There's no other feeling like test flashing and waiting to see what happens

Sent from my SPH-D710 using Xparent Blue Tapatalk 2
[Samsung Epic 4G Touch] bigpeng:
Lol, yea. I guess I'll wait for sfhub and gars findings, just in case. My sprint stores closed now. :p
[Samsung Epic 4G Touch] bigpeng:
Damn just saw this. Wish i still had mine. I took it in and they swapped it out right away.
[Samsung Epic 4G Touch] donsh00tmesanta:
What does this mean not to flash fe07?

Sent from unnamed 2.0.1 powered galaxy s2 brought to you by sprint
[Samsung Epic 4G Touch] bigpeng:
No, it's fine to flash FE07. We were just talking about the kernel. Samsung supposedly fixed issues with bricks.
[Samsung Epic 4G Touch] locoboi187:
I got:

MAG4FA

0x0

0x0

So close :/
[Samsung Epic 4G Touch] edlee:
is there any easy way to go from fe07 kernel locked android recovery to an unlocked android recovery?
[Samsung Epic 4G Touch] CyberpodS2:
Presumably Mobile Odin would be the most painless...
[Samsung Epic 4G Touch] sfhub:
I'm curious, can you uninstall the app while on the regular stock kernel, then install the plus kernel, then install the app?
[Samsung Epic 4G Touch] sfhub:
Here are traditional ODIN .tar.md5 versions of Unlocked and Plus FE07 kernel repacks (they are 7zip self-extractors, so double-click to extract the .tar.md5 file):

FE07 Kernel Repack [Unlocked / Plus]

They *will* trigger the yellow triangle and increment the ODIN flash count, so if you care, use a usb jig or triangle away to reset.
[Samsung Epic 4G Touch] Tooke:
Benchmarks

I know, benchmarks are questionable, but I noticed a significant drop in both quadrant and linpack scores with this update. Was getting 3800 - 4000 consistent on quadrant and high 70's on linpack with FD26 stock full restore. Now, on FE07, getting 2700 quadrants and 40's on linpack. Anyone else confirm this drop in benchmarks?