yashsingh1/xdaforums huggingface dataset:
[Desire Q&A, Help & Troubleshooting] xky1980:
With Insertcoin 1.0.5 and Blade wifi fix (downloaded from market) the the situation has improved, but the problem has not yet been resolved.
[Desire Q&A, Help & Troubleshooting] veitograf:
I got the same problem with WiFi dropping when 3g is on. Also with leedroid 2.3 my 3g was off but connected by itself when there was no WiFi around. With Insertcoin its not working.
[Desire Q&A, Help & Troubleshooting] Deleted member 3370907:
Same issue here with Oxygen 2.1.3 and Radio 32.56.00.32U_5.17.05.08.

Cant confirm if its 3G related or not. WiFi connection was stable for 10min with 2g only. Another 10min with 3g enabled and i've got a disconnect again.
[Desire Q&A, Help & Troubleshooting] moshere:
I've the same problem since upgarding to GB ROM.

I found a fix for Desire S - see link http://xdaforums.com/showthread.php?t=1051674

Any chance to have the same for Desire?

Thank you

Moshe
[Desire Q&A, Help & Troubleshooting] :
I've pushed the calibration file onto my oxygen-desire and nothing changed. According to the Thread the framework.jar needs modification due to signal display errors only, so framework.jar is not the actual fix.
[Android Software/Hacking General [Developers Only]] sarfaraz1989:
I dont have a wifi dongle for my desktop machine and i dont intent to invest in one..Is there a hack/workaround so that i can use the wifi present in my android phone (Optimus One FROYO) to access other wifi networks on my computer/desktop ???? Any inputs are welcome
[Epic 4G General] DRockstar:
OK, this is a public service announcement, after having tested stock EE03 with all forms of one click roots, using rageagainstthecage-arm5.bin and GingerBreak, and the prognosis is:

We have come to the end of an era for one click roots. It's over, and the exploits have been patched.

So, for official gingerbread, I predict that the only way to root it, will be to odin/heimdall a rooted kernel and/or cwm. The current trend has been to flash a rooted kernel for other samsung devices.

Of course, there could be some chance that somebody will provide another exploit that'll give us adb rooting capability... but honestly, I doubt it will happen. Hopefully I can be proven wrong.

Anyways, I wanted to give users a heads up, before the inevitable flood of "why isn't this working for me" threads emerge whenever official gingerbread is released.

I had spent many hours getting ready to release a new all in one root and recovery, going so far as to make a new cwm and rooted kernel for it, to only discover the effort will be moot very soon.

Well, at least you can't say that I didn't give a warning.

Edit: just so you know, the cwm 3.1.0.1 thread has been updated as an odin flashable tar, so that clockwork can be applied, no matter what... you can find it in the dev section.
[Epic 4G General] tai376:
Sounds like the pre-rooted ROMs are OK then. ;)
[Epic 4G General] Top Nurse:
I think the Bonsai MasterKey unlocker *may* soon work on gingerbread devices. It flashes a recovery image which then let's you flash a rooted rom. We have also made Heimdal available in win32, win64, linux, and osx configurations.

Heimdall will alow you to eb13 and an EC05 modem togetther. I assume it would do a gb modem at same time as well.

Sent from Bonsai 7.1.1.1
[Epic 4G General] daddymikey1975:
maybe I missed something here but I'm running the EE03 build and I'm rooted.

CWM 3.0.2.5 (from EC05) allowed me to flash EE03 that included a rooted kernel. again, I apologize if I missed something in your post. Not trying to sound ignorant.
[Epic 4G General] KennyG123:
ACS prerooted the Gingerbread leak. He is talking about one-clicking the Gingerbread OTA.
[Epic 4G General] JMMusic:
There has never been, and will never be, an exploit free piece of complex software (like an OS). It can't be done. Whether the exploits are found, and how practical they are to use, may push people to do pre-rooted kernels and such, but that doesn't make an on-the-fly rooting impossible, just not easy or appealing.
[Epic 4G General] poit:
Like you have said, worst case is we have to wait for someone to post a prerooted version of the stock rom.

What concerns me is that all the backup and recovery options I have found require root to work. I'd like to install the new Gingerbread when it comes out, but I'll have to wait for root one way or the other
[Epic 4G General] KennyG123:
I thought the paid MyBackup Pro works unrooted?
[Epic 4G General] daddymikey1975:
it does, however, some of the features require root permissions IIRC.
[Epic 4G General] mkasick:
Has it been confirmed that EE03's vold is patched against CVE-2011-1823, or is it just that the present GingerBreak doesn't work? They claim in the exploit README that offset/indexes may have to be adjusted on some devices.
[Epic 4G General] Shoulon:
So are you saying we should wait before we OTA, when or if the OTA comes?
[Epic 4G General] Whosdaman:
Gingerbread can be rooted with gingerbreak. Just like every other device
[Epic 4G General] Shoulon:
Yes we know that wdm. It's just a warning the OP is trying to tell everyone.

atleast people better know.
[Epic 4G General] Whosdaman:
I was answering a question. People don't know. Look at the post above you
[Epic 4G General] theimpaler747:
Not true. Gingerbreak did not work on the EE03 leak.
[Epic 4G General] zanderman112:
Hmm, interesting..

[sig]I'm close to rooting, i have to wait for a replacement :([sig]
[Epic 4G General] iSaint:
With a 100th thanks...
[Epic 4G General] Whosdaman:
Do you have the tar so we can test it?
[Epic 4G General] mkasick:
Well it appears so, sort of. It looks like vold may not be patched with the array bounds check, but libsysutils.so is patched to ignore netlink messages from user processes, so the exploit commands can't be sent to vold. Bummer.
[Epic 4G General] Overstew:
Well that sucks! Hopefully Gingerbreak creators can find a way to exploit around the patch. Otherwise, the Epic is doomed!
[Epic 4G General] BeerChameleon:
Good thing I know how to use odin superbly :p to me its easier then one click :)
[Epic 4G General] mattallica76:
Heimdall has become my friend lately.
[Epic 4G General] theimpaler747:
Yes. Will I give it out, not a chance.
[Epic 4G General] Death259:
Understandable. Don't want to get any leak sources in trouble.
[Epic 4G General] theimpaler747:
Exactly. It's odd that WDM wants it, since he cares about sources.
[Epic 4G General] zanderman112:
I think he just worded it wrong. I think he was asking if *you* tested it on the tar, but worded it wrong. Trying to be optimistic :)

[sig]I'm close to rooting, i have to wait for a replacement :([sig]
[Epic 4G General] compuw22c:
You guys should see what Verizon did to the Charge I got my mom for Mother's day. They delay the phone 2 weeks, nobody knows why (people assumed the LTE outage was the cause). Finally its released, and on release day, they release an update that seems to do NOTHING ELSE but break root.

Now, this could have been done at Verizon's request (at least they kept Bing off the thing. God I hate verizon...) but it may be a sign of things to come.

If Samsung is smart, they won't alienate their customers like Apple, Motorola, and now HTC by locking down their phones and (in Motorola's case) telling customers to "look elsewhere". If they play their cards right they could be the only real game left in town! I'm very interested to see if the EVO 3D continues in the Thunderbolts footsteps (not that I intend to jump ship just yet, I just love good hardware :) )
[Epic 4G General] theimpaler747:
To answer that, yes we did :)
[Epic 4G General] zanderman112:
Good to know, bad for us :( lol :p

[sig]I'm close to rooting, i have to wait for a replacement :([sig]
[Epic 4G General] digiblur:
Big deal... odin back to 2.2. Install CWM...flash prerooted GB ROM.
[Epic 4G General] Darkshneider:
Im not worried. I can use Odin and dont do OTAs, I learnt my lesson back from my PSP days about updating to the latest firmware... WAIT FOR DEVS!
[Epic 4G General] iSaint:
Exactly me no see why all the drama is for.

can't we all be friends ??

Theese are for David...
[Epic 4G General] Overstew:
LMAO did u see that video on youtube? It has 95% of the votes are thumbs down. LOL!

(for the Rebecca Talentless Black)
[Epic 4G General] Whosdaman:
I was asking if you had it. Meaning you. And who cares about sources, rjmjr69 said yours got fired already. So what does it matter?

We already know that there is no employee information store in stock ROMs, so what is the hold up with the EE03.tar?

As well, Gingerbreak can be modified to work with Gingerbread if we can get the tar. So yes it could work if given the opportunity.
[Epic 4G General] mkasick:
But one of the exploits used by GingerBreak is already patched in EE03 ....
[Epic 4G General] Whosdaman:
That why we need to tell Chainfire so he can update Gingerbreak and exploit the new patch
[Epic 4G General] mkasick:
Given that the phones were sitting on store shelves, the LTE problems is a probable excuse. Having a bunch of Charges drop their LTE connections every thirty seconds would've left horrible impressions and become a support nightmare.

No, the update addressed a major privilege-escalating vulnerability with a successful exploit in the wild. Although this very exploit is a convenient means to achieve root on these devices, it still needs to be patched lest it be taken advantage of by malware similar to what we've seen in the past:
[Epic 4G General] mkasick:
It's not a matter of twiddling with some values to make it work though, the patch directly addresses one of the two exploited security vulnerabilities. Both are needed for GingerBreak to work, patching at least one of them stops it dead.
[Epic 4G General] Whosdaman:
If there's a will, Chainfire will find a way.
[Epic 4G General] stackz!:
He cannot. That's like saying rageagainstthecage can also be modified to work with gingerbread.

Not to mention, Chainfire has nothing to do with the actual exploit.
[Epic 4G General] ptfdmedic:
I rooted the Nexus S 4G using adb. Are you speaking specifically about the Epic or about oneclick roots in general. The adb method took like 5 minutes.
[Epic 4G General] Whosdaman:
Where do all these random noobs come from that know so much information?
[Epic 4G General] Top Nurse:
Just because they have a low post count doesn't mean they know squat...

Sent from Bonsai 7.1.1.1
[Epic 4G General] ptfdmedic:
Except Samsung is wanting to foster the development community. If it's locked down to tight that won't happen.
[Epic 4G General] zanderman112:
Yeah, its called lurking.

[sig]I'm close to rooting, i have to wait for a replacement :([sig]
[Epic 4G General] heathmcabee:
If the source was fired, then I don't see why it can't be released. Not like much more can be done to the guy.
[Epic 4G General] shabbypenguin:
Gingerbreak was patched, i know because i tested it myself. whether or not there is a new exploit released remains to be seen. but yall are lucky in that a pre-rooted kernel will work just fine. no the "bonsai hacking tool" will not work unless its a frontend to odin/heimdall and flashes the custom kernel/recovery. i am working with the samsung prevail on boost mobile right now witha few guys, everything for them is blocked. so they cant even get "temp" root to pull the stock kernel. yall at least got that much :P

i think there has been enough drama on this boards to last a good while. drockstar was nice enough to give a public warning to everyone, no need to start pissing matches in his thread.
[Epic 4G General] Xhyperion:
So the point is:

If you are currently rooted, it's a good idea to wait for a rom/kernel with 2.3 and just flash to that to avoid all the bull****.

If you are on stock but are on the fence about rooting now may be the time to do so.

Right?
[Epic 4G General] The Root:
Thanks!
[Epic 4G General] Whosdaman:
Does that mean everyone is just going to give up on trying to fix the gingerbreak?
[Epic 4G General] zanderman112:
I think it means we have to wait for the update to find out what happens.

[sig]I'm close to rooting, i have to see if its messed up first :([sig]
[Epic 4G General] Whosdaman:
Lets work on it right now! Release the tar then joeykrim and noobnl can work on getting a one click working
[Epic 4G General] zanderman112:
But, we don't know if it'll still work on whatever the official release is, hopefully EE19. Be patient, good things come to those who wait. Besides, its not like most of us will accept it OTA anyways. :)

[sig]I'm close to rooting, i have to see if its messed up first :([sig]
[Epic 4G General] Whosdaman:
True, but its better to prepare then to go in blind. We need to see what we are dealing with
[Epic 4G General] shabbypenguin:
joeykrim wouldnt work on it anyways. him and some of the other members of teamw.in are working on trying to crack wimax settings to allow a universal hook set for wimax (accross htc and samsung)
[Epic 4G General] bryanfritz1:
I'm not entirely sure what that means, but if I were to guess is that non-samsung wimax drivers? :-)

sent from "The Other Woman"
[Epic 4G General] RushAOZ:
Gingerbread will also break your face. :)

my 2¢ via the EpC4gee
[Epic 4G General] Whosdaman:
That would be amazing.
[Epic 4G General] eigerzoom:
i hope this means i could finally use clear/clearwire credentials on the epic as currently the wimax nai is not editable like the evo...
[Epic 4G General] mkasick:
It's been alluded to before, but what exactly does GingerBreak buy us in terms of a one-click that can't already be achieved with Heimdall?

The advantage of using a local root exploit is being able to use it standalone, without requiring a host PC. To my knowledge though, Epic one-clicks have always required host PCs, so there's no difference there.

The other advantage of a local root exploit is being able to root a device without installing a custom (recovery/bml8) kernel. But one-clicks have been installing a custom recovery kernel for a while anyways.

Really it's probably just time to transition one-click roots over to being adb & Heimdall command-line client based. Use adb to force the device to reboot into download mode, use Heimdall to flash an "insecure" recovery kernel with adbd enabled and reboot into recovery, from there you have an adb root-shell to continue on with.

The only problem is if Heimdall can't reboot into (bml8) recovery directly, as a normal boot for folks who OTA upgrade will overwrite the recovery kernel with the stock kernel (if the stock kernel hasn't been replaced). In which case we have to flash a custom (bml7) kernel, but that's not a huge problem.

It's the direction that makes the most sense to go in anyways. Root exploits are often unreliable and have a tendency to be patched. Instead of "trying to fix GingerBreak", it makes sense to invest the time to use a Heimdall-based approach, which barring any major departure on Samsung's part with regard to kernel/recovery signatures, should continue to work with any future upgrade.
[Epic 4G General] tumbes20000:
Now if I am rooted and I do the ota will it just unroot the phone or will there be more damage?
[Epic 4G General] theimpaler747:
It will just unroot.
[Epic 4G General] Whosdaman:
Hey, do you have the prevail? I didn't even notice that part lol
[Epic 4G General] styles420:
I think it means most Epic owners on this forum are non-technical people that root because it's the cool thing to do (it really is), and therefore lack the knowledge to understand how a lot of it works. This means they also can't see any plan B, and are therefore ready to just roll over and give up.

This is not a criticism of the lack of knowledge (would you be offended if your surgeon said you knew nothing about brain surgery?) - but there is more hope than many people think

I'm an old school programmer that has been out of the game for a few years (life in the real world, no time for my hobbies... It's the only reason I miss high school). And the Epic is my first smart phone, since I resisted making the leap when they were still a premium option instead of the standard... But hopefully I'll have a little more free time in another month or so - I'll be doing a lot of research and experimentation to learn more, so maybe I'll be able to step up to the plate and lend a hand before too long...
[Epic 4G General] imjimmy:
Hi guys. I am on stock rooted with one click method and RFS file system. Other than the root nothing else is modified and everything is stock, including the launcher.

Is it possible to block the gingerbread sprint update? I really don't want to mess up the rooting because I have a lot of aps that depend on it. And I am fine on froyo because my understanding is that there is not many changes in the gingerbread anyway.

So please if someone can tell me how to block updates...much appreciated. How soon is this update coming?
[Epic 4G General] TexasLTE:
Great News ! We can ALL benefit from more folks who know what they're doing ( I fall under the non-technical category myself - but I greatly appreciate the work the developers put into their products )
[Epic 4G General] The Root:
Yay, smart people!
[Epic 4G General] Trickee360:
Quick, possibly stupid question to run alongside this discussion: given that dedicated rooters will need to decline OTA updates to avoid un-rootable firmware, what's the best way to block OTA updates on a stock ROM? Could I simply use Titanium Backup to backup the system apps and uninstall Asphalt 5 or something until I'm ready to move? This blocked updates last time, if I remember. If Samsung and Sprint really are acting aggressively to actively discourage rooting the gingerbread ROM, I'd like to be prepared in case they surprise us with it.
[Epic 4G General] KennyG123:
When it says a system update is available, just don't accept it. Say "not now". You probably have a couple of months before we will see it.
[Epic 4G General] The Root:
Acting that aggressively would probably result in app data being lost. I'm sure they would rather just leave us be than deal with thousands of, "Where's my Angry Birds data!?!?!!" phone calls from average customers.
[Epic 4G General] mkasick:
Plan B is already stated in the OP:

To be a bit more concrete, there's two ways to root an Epic:

Plan A: Use a local-root exploit, if one exists, to get a root shell without modifying/flashing any additional software. Then install su binary in /system to obtain root privileges later.

Plan B: Odin/heimdall flash a custom, "pre-rooted" kernel image. Optionally install su binary in /system.

The patching of the GingerBreak vulnerabilities eliminates "plan A", which breaks the current strategy by which one-click roots work. "Plan B" is always available to us, and I'd be very surprised to see it go away in the Epic's lifetime.

The issue at hand is merely a matter of convenience, there's no question over the feasibility of rooting the official Gingerbread release.

Now, there's a different question of whether GingerBreak will/can be fixed. It can't in its current form. Now, perhaps someone will discover another vulnerability in Gingerbread and release an exploit for it, but that's no small feat. It's not really something for us to bother doing since it only makes the rooting process on the Epic marginally more convenient until the time the vulnerability is patched.

Folks with other devices (e.g., HTCs and current Motorolas) are far more motivated to find and develop an exploit since they don't have an unlocked host-based flashing mechanism to fall back on like we do. If they do develop an exploit, well, we may be able to make use of it at that time.

There's no evidence that anyone is acting to "discourage rooting." The patches that fix the GingerBreak vulnerability were commited by Google themselves to android-cts-2.3_r3 and are intended to curb malware.

Although they make rooting a bit more inconvenient, we welcome these patches in Gingerbread, as we don't want riff-raff market applications to, unknowingly, obtain root privileges without our permission.
[Epic 4G General] Trickee360:
This came out sounding harsher than I meant it. I retract the statement. What I was trying to point out is that it's odd to me that this issue would be unique to just the Epic and not be present in other manufacturer-produced ROMS based on 2.3.3. I clearly don't know as much about this as y'all. Sorry for injecting that into the conversation.
[Epic 4G General] Firon:
Not having a one-click root just ain't that big of a deal. Odin/heimdall is still ridiculously easy compared to the fastboot nonsense you need to do on some devices.
[Epic 4G General] mkasick:
Oh, that has to do with the timing of the release of GingerBreak and Samsung's work on the Gingerbread update.

GingerBreak was "announced" back in January but held off as the only device actually released with Gingerbread, the Nexus S, features an unlockable bootloader/other means for achieving root. It was speculated that Google would patch Android as soon as the vulnerability deals were known, which happens no later than when an exploit is released, and the GingerBreak folks wanted it to be used on devices that couldn't otherwise be rooted.

Last month saw the release of previously-unrootable devices either with Gingerbread or unrootable updates to Gingerbread--I'd guess the HTC Desire/Incredible/Wildfire S models. So GingerBreak was released on 4/21 (possibly sooner?). But the two vulnerabilities it exploits to achieve root were patched (other) by Google on 4/18.

Now, these patches were commited to the current Gingerbread Compatibility Test Suite, along with a new security test set (on 5/2), the first one of which is a test for the GingerBreak vulnerabilities.

Keep in mind that manufacturers that license Google Apps must release ROMs and upgrade that pass the relevant CTS for that Android version. So it appears that Google is stepping up their requirements so that manufactuers stay on-top of security vulnerabilities in updates, so we don't continue to have situations where manufacturer release ROM updates still vulnerable to exploits (e.g. rage) eight months after they're known and patched, a period during which we see the release of malware that uses them to steal personal information.

So yes, a Gingerbread update released, for a Google Apps-licensed phone, prior to May 3rd is probably vulnerable to GingerBreak while any update released after must not due to Google testing requirements.

(Perhaps not) coincidentally, May 3rd is also the build date of the latest Epic Gingerbread leak, which is patched against the GingerBreak vulnerabilities.
[Epic 4G General] imjimmy:
Thanks for the quick response. Much appreciated!
[Epic 4G General] DRockstar:
Bumping this thread, so more people are aware...

In anticipation, both cwm and clean kernel are available as tars now, in the development section...
[Epic 4G General] gpeterson:
Modding this phone wouldn't be fun if we didn't get a few challenges now and then...