yashsingh1/xdaforums huggingface dataset:
[Nexus Q General] dvinesett:
I don't think fastboot has a boot recovery option. When I try this, I get the message

cannot load 'recovery': no error

I'll go into more detail on what I've tried since then. I start with a factory reset Nexus Q then make sure it is still unlocked and has su/Superuser/busybox pushed onto it. I then go through the process

adb reboot bootloader
fastboot flash recovery "recvoery image location"

bootloader then writes the flash to the recovery partition seemingly without problems.

At this point fastboot recognizes the Nexus Q and adb does NOT recognize the Nexus Q.

Because fastboot has no utility (as far as I know) to reboot into recovery by itself, I reboot normally

fastboot reboot

(NOTE: using "fastboot reboot-bootloader" still only lets fastboot recognize the device, adb will not recognize it by bootloading from this)

Once adb recognizes the Nexus Q, I reboot into recovery

adb reboot recovery

At this point, the Nexus Q will not display anything and flash red (startup failed) and proceed to do a factory reset by itself.

I'm using the CWM steelhead beta image. (can't post link with under 10 posts; should come up as first link on google search)

I'll go into any more detail I can if necessary. Thanks for your time

EDIT: If someone knows of a method for sideloading a launcher that isn't via CWM, that information you be appreciated too! adb install didn't work; I got the message

'steelheadnightlyblahblah.zip' does not contain AndriodManifest.xml
rm failed for /data/local/tmp/'steelheadnightlyblahblah.zip', no such file or directory

I looked into this, and the nightly should have had the xml file in it (I think)
[Nexus Q General] dragon788:
dvinesett, try it with a different monitor. I realize this is probably slightly thread-necro, but it might help some other Nexus Q owners. The Nexus Q doesn't seem to send correct resolution parameters during early boot and as the CWM guys discovered, this can cause issues with most PC LCDs. TVs seem to have less issue with the resolution requested. There are a couple patched version of the recovery that fix the "tiny text" issue, but I don't think they've gotten the EDID issue during recovery/boot figured out.
[Motorola Droid X2] whojohnjones:
is it possible to run all droid x2 roms on milestone x2?
[Motorola Droid X2] Lrs121:
I'm not exactly sure but I don't think so due to the fact that the dx2 and the mx2 have different kernels
[Galaxy S III Q&A, (US Carriers)] rodriguez236:
Has anyone ordered from cnn.cn. I was looking into ordering a back cover for my S3. How was your experience with them. How are their products?
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] tkjxman:
Excuse passengers would ask me about costom GB rom is stable and not wasteful of battery Kalua fitting custom made ​​rom play games wearing what??

please its support and thanks
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Rechargelegend:
Excuse me but i dont understand what you mean?
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] xZAKIKAKIx:
?????????????

please use google translate if you weak in english.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] tkjxman:
sorry if the words he says difficult to understand.

gingerbread custom rom is stable and not wasteful battray wear what??
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] lokenok:
wtf...

are you trying to say

which gingerbread rom is stable and has good battery life and can play hd games

lol... no offence but laughed at the first post
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] tkjxman:
sorry if the english language I use is less clear:D
[T-Mobile Samsung Galaxy S II SGH-T989] jackmackeral:
hi all.

when i was running GB i would use ES File Manager to connect to my NAS at home and occasionally stream videos from my NAS to my t989. it would work flawlessly using moboplayer.

after upgrading to ICS, this doesnt seem to work at all. some files might play for a second or two but then just freezes.

i know that the phone can play the file because i have tried playing the same file locally and it works flawlessly. is this an issue with ICS and is there a workaround? thanks in advance.
[Samsung Epic 4G Touch] aghasi24:
i was just looking for a good stable gingerbread rom but blazer 4.1 is not an option because there is no download link.
[Samsung Epic 4G Touch] juggalo1300:
Go with either RUJELUS22_Blu_Kuban_EL29_V1.2.0_ODEXED or Calkulin_s_E4GT_ROM_v3.0. Both very good roms. Im using calks right now. Very good battery and super fast ui
[Samsung Epic 4G Touch] mremale:
I left ICS to use two great gingerbread roms. I love New Sensation rom (great without even using battery app) and blazr rom
[Samsung Epic 4G Touch] aghasi24:
Can u tell me how to download blazer rom 4.1? Because the download link us down
[Samsung Epic 4G Touch] juggalo1300:
I'd go under the devs profile on here and look to see if he has a webpage. Or even look up the wiki page for our phone and go under roms. It may be listed there with another DL link. I'll look around and see if I can find a link for you
[Samsung Epic 4G Touch] juggalo1300:
All I could find was a build for 3.9 here is a link to that DL

http://goo.im/roms/PhantomHacker/Blazer_Rom_El29_v3.9_Swagger2.zip

Here is the link to all of the info for our phone also. This will bring you to any and everything you need to know

http://xdaforums.com/wiki/Samsung_Epic_4G_Touch/ROMs
[Samsung Epic 4G Touch] LanceEpic:
Sent you a pm with a link to download it. I had it saved on my computer
[Samsung Epic 4G Touch] woody296:
Any chance you can send me the link also? thanks.
[Samsung Epic 4G Touch] LanceEpic:
sent
[Samsung Epic 4G Touch] Taco991:
I'd like a link too... btw where's the blazer thread???
[Samsung Epic 4G Touch] LanceEpic:
Sent link. Not sure if it works or not. Could someone let me know if it does?
[Samsung Epic 4G Touch] juggalo1300:
Here a link to the thread. But it's been updated for Ics.

http://xdaforums.com/showthread.php?t=1363071
[Samsung Epic 4G Touch] RandallOfLegend:
I have been running Calkulin's GB ROMs for over 6 months now. I highly recommend it!:cowboy:
[Samsung Epic 4G Touch] TheDriller:
CyanogenMod 7 is my fav GB rom. Lots of cool features plus great battery life

Sent from my SPH-D710 AOKP
[Samsung Epic 4G Touch] revamper:
I wish they had finished it :(
[Samsung Epic 4G Touch] juggalo1300:
Yea forget blazers. Just got my first brick trying to flash that ROM. I've been flashing for awhile now. Decided to try the smoothie after hearing all the hype. Just got my phone back up and running. Im sticking with calkulins. It's to bad he left behind his efgt work for HTC.
[Samsung Epic 4G Touch] SFG:
Post #3 on that thread has the GB build.
[Samsung Epic 4G Touch] SFG:
Just curious what you flashed from and what recovery you used. I'm new to the SGII.
[Samsung Epic 4G Touch] SFG:
http://goo.im/roms/PhantomHacker/

Downloading 4.0 as I type this.
[Samsung Epic 4G Touch] arbearce:
I've been using Calkulins v 3.0 and it's been great.
[Verizon Samsung Galaxy S III] CMTeamEpic:
Team Epic announces a proof-of-concept source-built kernel for the Verizon SGS3, complete with kexec hardboot support. This kernel serves two purposes:

1. To be included in custom recovery images, as it proves the capability of booting-via-kexec custom kernels from recovery.

2. To serve as a proof-of-concept boot kernel, to demonstrate that custom kernels are capable of running on the Verizon SGS3 in its present form.

Please see our blog post, Kexec, and a Proof-of-Concept Source-Built Kernel for the Verizon SGS3, for full details and source links.

CyanogenMod's Team Epic specializes in Sprint's flagship Android phones on Sprint.

If you appreciate our work, please consider supporting us with a tiny contribution. Thanks!
[Verizon Samsung Galaxy S III] ruvort:
Awesome! Thank you so much for your guys efforts

MyColorScreen
[Verizon Samsung Galaxy S III] ceo.mtcl:
Good luck guys.

☞ sent from my GS3
[Verizon Samsung Galaxy S III] mkasick:
Just to confirm, the kexec hardboot approach used here is a bit different from the typical kexec. The main difference is that we actually perform a hardware reboot, reinvoking the bootloader just prior to booting the kexec'd kernel.

The advantage to this approach is that it maintains a high-degree of compatibility and minimizes buggy behavior. The disadvantage is that it requires that the bootloader is capable of booting custom recoveries, which the present Verizon SGS3 bootloader is capable of doing.

Thus, it's very important that folks do not apply any over-the-air (OTA) update, until it is confirmed that custom recovery booting remains intact.

If it eventually arises that booting from a stock kernel/recovery is necessary, then it's likely a bunch of kernel bugs will have to be fixed, and it might still have compatibility issues observed in previous kexec attempts. It's linked in the blog post, but there's a bit more of a technical description of the hardboot approach in this old thread.

Thanks to invisiblek and captjtkirk for testing.
[Verizon Samsung Galaxy S III] droidfta:
you guys are awesome xda has the best devs ever! I worship you guys!
[Verizon Samsung Galaxy S III] Schaweet:
Wow! Thanks for taking the time to do this even though you guys aren't vzw owners. Great example of how great this community is.
[Verizon Samsung Galaxy S III] deitiphobia:
Unbelievable...you guys are awesome.

Jelly Bean here we come!
[Verizon Samsung Galaxy S III] jh120:
Forgive my paranoia, but does Verizon have the ability to force an OTA without us pressing an "OK" button?

Thanks to all who worked on this, you're awesome!
[Verizon Samsung Galaxy S III] Neverendingxsin:
nope. you have to accept the OTA
[Verizon Samsung Galaxy S III] pwned3:
Depends. My rezound didn't ask. I would wake up with my phone in recovery. It would fail to install the update because the stock recovery wasn't there but it never gave me a choice to install or refuse
[Verizon Samsung Galaxy S III] ErylFlynn:
Say we needed to return to stock, can we just use Odin, flash back the ROM or would their be a bit more to it?

And THANKS! You are just missing the raised finger picture to Verizon over this.
[Verizon Samsung Galaxy S III] skennelly:
I know this was an issue back in April(?) I haven't read anywhere that this has changed and I am curious to know this as well.
[Verizon Samsung Galaxy S III] tpike:
Glad to see some love from familiar faces. This is one if those times when i nuts being on sprint. From the galaxy tab, to the og epic, to the touch, sprint has allowed great things to happen on their devices. Now in big red, it's great to see we can use/reuse stuff across networks.

Big thanks!

Sent from my DROID RAZR using Xparent ICS Tapatalk 2
[Verizon Samsung Galaxy S III] neyenlives:
+1 :p
[Verizon Samsung Galaxy S III] mkasick:
In short, yes.

Longer answer:

Traditionally kexec works by having one instance of the kernel boot a second instance directly, that is, by avoiding the bootloader. For this to work, every kernel driver has to shutdown in such a way that the same driver (in the kexec'd kernel) can revive and restart the hardware it controls.

The problem is that some, maybe many, drivers aren't actually capable of doing that. For the most part, it's a feature only needed by kexec, so unless the device manufactuer is specifically targetting kexec support, usually one or more drivers will put some part of the hardware in a confused state. That's the main source of compatibility bugs with kexec.

Now, what we do in the kexec hardboot approach is use the Linux kexec infrastructure to load and stage a new kernel in memory. Then we perform a hardware-level reboot, reinvoke the bootloader, and then at the very beginning of the recovery kernel code, we check to see if there's a kexec'd kernel out there in memory and if so, jump to that instead.

The advantage with this technique is that once the kexec'd kernel is booted, the environment is the exact same as if it was a kernel flashed to the device--there shouldn't be any hardware compatibility issues.

As it turns out, the one compatibility thing we have seen, which is unusual reboot behavior, isn't actually an artifact of kexec. The same thing would happen if you flashed a "boot kernel" to the recovery partition and booted it directly.

---------- Post added at 09:30 AM ---------- Previous post was at 09:28 AM ----------

This is a temporary mechanism. To return back to the stock kernel, simply reboot the device.

To remove the custom recovery and fully flash back to stock, yes, you would use Odin.
[Verizon Samsung Galaxy S III] ckochinsky125:
Great work guys. You guys are awesome.
[Verizon Samsung Galaxy S III] Kreeker:
Amazing news!
[Verizon Samsung Galaxy S III] nosympathy:
So when you say you just reboot to get back to the stock kernel, is it a certain way of rebooting?

As in, if you were running soap and a kexec aosp kernel and rebooted and it forced you to the stock Samsung kernel, the phone wouldn't boot right?
[Verizon Samsung Galaxy S III] mkasick:
Say you have a ROM installed that's compatible with the stock kernel, but you also want to run a custom kernel. You can kexec the custom kernel from CWM. And, if you want to "switch back" to the stock kernel, just reboot.

But if you have a source-built ROM (CM, AOKP, etc.) installed to the /system partition then the stock kernel will be incompatible. You'll always have to kexec the source-built kernel.

That's a point of frustration for sure. If there's no other bootloader workaround found, we've discussed the idea of hijacking part of the boot process to detect if the stock kernel is being used to boot a source-built ROM, and if so, redirect it to boot recovery and automatically kexec a source-built kernel. Of course, the details on that still need to be figured out.

Anyways, what we're planning to do on the Sprint SGS3 is make the first CM releases actually (kexec) bootable from the SD card, so they won't be written to the /system partition at all. This lets both stock ROM and CM co-exist until the bugs can be worked out, and CM is worthy of being run full time.

I'd recommend that initial CM ports for the Verizon SGS3 use the same approach, at least in the beginnig.
[Verizon Samsung Galaxy S III] chadamir:
So, as it stands, merely rebooting the phone, for whatever reason and in any way, will revert back to the stock kernel? In order to back youll have to go into cwm and load the custom kernel?
[Verizon Samsung Galaxy S III] Metfanant:
what are the potentiall performance/battery drain related issues involved in using such a method??...coming from a DX and our "2nd Init" solutions to running ROMS like CM speed and smoothness are always important, and our 2nd Init ROMS had that, but im only willing to put up with extra battery drain issues to a certain extent...somewhat defeats the purpose...
[Verizon Samsung Galaxy S III] mkasick:
Actually, right now, rebooting the phone will reboot to recovery automatically. If you reboot from there, it "reverts" back to the stock kernel.

Yes, for now.

None. Once the kernel is running, its indistingushable from the way it would run if it were flashed to the device (and the bootloader unlocked), aside from the aforementioned unusual reboot behavior.
[Verizon Samsung Galaxy S III] Loglud:
I worked alot with helping this be built on the Nook Tablet (though we found a secChain hole), and it can be done with an alternative bootloader such as fattire's cyanoboot that can replace the boot loader. To avoid any conflicts with future ota's i would not rely on this KExec method. Kexec is a flag in the kernel. It would take 2 seconds for them to patch this which throws everything out the window. I would focus your time at looking at Aboot, and seeing if their is a way to overload the header to allow for a nonsecure boot. I have referanced this in another post but heres a good link:

How ever I do have to say this is a major step in the boot unlock and other things. Congradulations to you all.
[Verizon Samsung Galaxy S III] mikereidis:
Great ! :)

A bunch of us want to see if FM can work and we need kernels/modules with this in the config:

CONFIG_RADIO_ADAPTERS=y

CONFIG_RADIO_IRIS=y

CONFIG_RADIO_IRIS_TRANSPORT=m

Would you be able to build with this in the config ?

I don't want to "spam"/duplicate post in kernel threads (more than necessary), so I'll point you here for some further details: http://xdaforums.com/showpost.php?p=28515392&postcount=592

Thanks !
[Verizon Samsung Galaxy S III] platinumyahoo:
I was worried my coming soon SGS3 would not be rootable and romable because of the locked bootloader. thanks for restoring hope!
[Verizon Samsung Galaxy S III] minmongoblin:
So if it were to accidentally reboot itself like sometimes smartphones are prone to do, or if the battery dies and we reboot after charging, we won't be thrown into the stock bootloader because it'll auto-start into CWM?

That's great news, I was skeptical until reading this. Thanks guys!
[Verizon Samsung Galaxy S III] rothnic:
Can we take the kernel from your recovery and use it in any other recovery without any other modifications to the recovery? I couldn't get yours to mount the internal storage.
[Verizon Samsung Galaxy S III] mkasick:
If you're just transplating the zImage component, it should work.
[Verizon Samsung Galaxy S III] rothnic:
At some point I(or someone) probably needs to apply the patches you implemented for kexec to the Verizon kernel. I understand the config is different, but I wonder if the source is as well. I would be a little suprised if they are identical.
[Verizon Samsung Galaxy S III] mkasick:
Yes I had to modify the d2vzw kernel sources. The changes are in my d2vzw GitHub repo. That's a good starting point for building custom kernels.
[Verizon Samsung Galaxy S III] rothnic:
I thought you said that you used the Sprint kernel source with the VZW config? Is that repo the VZW source or the sprint source?

Edit: Either way I since noticed that Invisiblek has a kernel here: http://rootzwiki.com/topic/29561-kernel-invisiblek-v2-i535/
[Verizon Samsung Galaxy S III] antp121:
You guys know invisiblek has unnofficial builds of cm9 in in goo.im ?
[Verizon Samsung Galaxy S III] kman79:
I may be blind, but I didn't notice any CM9 builds in his goo.I'm
[Verizon Samsung Galaxy S III] PhantomGamers:
http://goo.im/devs/invisiblek/i535/roms
[Verizon Samsung Galaxy S III] kman79:
Nice, have you or anyone else tried it?
[Verizon Samsung Galaxy S III] cordell12:
data is not working yet...
[Verizon Samsung Galaxy S III] mkasick:
I did originally since the vzw kernel sources hadn't been posted at that time. Once the vzw sources were released, I rebased the patches against that tree.

The linked repo is based off the vzw sources.
[Verizon Samsung Galaxy S III] neyenlives:
wanted to revisit this thread to say thank you to those behind the work that gave us kexec ability, now that the phone is unlocked we can look back on this fondly
[Verizon Samsung Galaxy S III] tonu42:
Its kind of pathetic how smart people are. Like they're so smart to make this. Than after much moaning and groaning, our bootloader is unlocked. DONE. Mod close thread please.
[Verizon Samsung Galaxy S III] suzook:
Huh?? Last poster was thanking the dev of kexec. I want to thank them also, it made the last month of owning my s3 tolerable.
[Verizon Samsung Galaxy S III] Josolanes:
Agreed, and kexec allowed much more flexibility in kernels/roms initially than would have been possible otherwise. I'm very happy they made it, it gave the S3 a good jump start in the development community imo
[Galaxy Y GT-S5360 Themes and Apps] willymarky:
just enjoy the app :highfive:

View attachment 1186417

cracked screen.apk

http://www.mediafire.com/?phtx529kcdg5b97

View attachment 1186418

steamy window.apk

http://www.mediafire.com/?05ossbcq5gcjcs6
[Samsung Infuse 4G] echelonattack:
flasheable Zip into recovery only ics

Here is where I found are for samsung galaxy nexus but also work to samsung infuse

http://xdaforums.com/showthread.php?t=1616164[/url

work perfectly cm10 jelly bean.... update 8/11
[Samsung Infuse 4G] echelonattack:
...

imagen attachment
[Samsung Infuse 4G] GoSooners345:
may I ask as to where you found this
[Samsung Infuse 4G] GoSooners345:
Um wrong file?

This is the stock mms app for cm9
[Samsung Infuse 4G] cmoRe-_-:
I don't know what I'm doing wrong but once I reboot after install my MMS is still the same.

Sent from my SGH-I997
[Samsung Infuse 4G] echelonattack:
..

Just flash it and automatically install the app ... cm9/aokp/remICS
[Samsung Infuse 4G] cmoRe-_-:
I must have something else going on because that's what I did. I'll look into this. Thanks

Edit: I got it working. Reinstalled rom and now works. Thanks

Sent from my SGH-I997
[Samsung Infuse 4G] gl1669:
IF anyone was wondering, these will

not

work with CM10.
[Samsung Infuse 4G] echelonattack:
works CM10
[Sony Xperia P, U, Sola, Go] metcard:
Hi there..

does anyone know where I might be able to download the Australian generic gingerbread firmware for the xs?

I updated to the latest gingerbread firmware using pc companion and have the300 mb file in the blob_fs folder, but I'm not sure if or how to use that file to flash my xs using flash tool.

I am running ch generic ics.
[Sony Xperia P, U, Sola, Go] K900:
Decrypt blob_fs and flash it with flashtool.
[Sony Xperia P, U, Sola, Go] metcard:
Thanks for replying.

How do I decrypt blob_fs?

I think this answers my question.

xdaforums.com/archive/index.php/t-1537296.html
[Sony Xperia P, U, Sola, Go] K900:
Use flashtool.
[Galaxy S III Q&A, Help & Troubleshooting] WayToGo:
I have just switched from international GT-i9100 Galaxy S2 with ICS 4.0 to an international GT-i9300 Galaxy S3. I used Kies with S2 to sync my Outlook contacts, calendar, schedule and

memos

. When I connected S3 to Kies I noticed that option to sync Memos with Outlook Notes is not available. I suppose its another Google's way of gradually pushing users away from Outlook.

Anyone knows another way to sync, or at least manually import notes into S Memo on S3? Thank you.
[Galaxy S III Q&A, Help & Troubleshooting] Gal:
Unfortunately, same situation here.

I thought it is caused by localized name of folder Notes. Therefore I tried to manually create folder "Notes" in Outlook when disconnected and then connect with Kies. No luck, Memo sync still not available. Maybe I should delete old localized folder... later.

Thanks for any other suggestion!
[Galaxy S III Q&A, Help & Troubleshooting] OndrejP:
If you insist on synchronizing via Kies into built in Samsung app, contact Samsung so they fix Kies. Otherwise there are many applications on Google Play that sync Outlook notes into own notes apps via all kinds of methods. E.g my app Local Sync synchronizes notes directly from Outlook in own notes app.
[Galaxy S III Q&A, Help & Troubleshooting] R4M30:
Hey guys.

I have a GT- i9300, I rooted it in odin with CF root, no worries, installed foxhounds Rom with SiyahKernel. All was fine for a few weeks. My phone then randomly shut down one day and would not boot. (had not installed any 3rd party apps, custom upgrades or anything for a few days).

My phone now only boots to the Samsung splash screen. Will not boot into recovery mode either. Download mode still works :)

So i tried to re flash the kernel through odin but I get an error "no PIT partition"

Tried flashing a stock Firmware through odin, same error.

Tried flashing CWM again through Odin, same error,

Tried flashing CF root again in Odin, same error.

Any ideas please help???

I have looked all over the net for two days now and found some people with same problem but they have not fixed it yet.

Would a 3-part firmware work in Odin? If so I have downloaded countless ones only to find they are the single .tar file
[Galaxy S III Q&A, Help & Troubleshooting] JJEgan:
3 part works via Odin.

jje
[Galaxy S III Q&A, Help & Troubleshooting] R4M30:
Any idea where I can get one from? Every Rom I download is only the one .tar file.
[Galaxy S III Q&A, Help & Troubleshooting] tzujeff1008:
same problem here...

any help will be very appreciated...