yashsingh1/xdaforums huggingface dataset:
[Kindle Fire General] matthend:
Thinking I will go to the local Wally world, as they have a bunch in stock. Do I turn off wireless immediately and try to flash one of the rooted 6.2.1 images? I definitely want at least root, if possible. Any advice is greatly appreciated!
[Kindle Fire General] Winglerw28:
Step 1: Disable WiFi

Step 2: Root your kindle using Kindle Utility located here: http://xdaforums.com/showthread.php?t=1399889 Note that this step requires you to install the Android SDK to use the USB drivers, a process that can easily be found by google search or even a search on that thread.

Step 3: Install FIREFIREFIRE and TWRP using the same utility above.

Step 4: Flash this ROM (pre-rooted 6.2.1): http://xdaforums.com/showthread.php?t=1402440

(Optional) Step 5: Install android market using this: http://xdaforums.com/showthread.php?t=1351283

From this point, you can re-enable WiFi. If you would like, you can install CM7 following this thread's guide (it is very easy now): http://xdaforums.com/showthread.php?t=1390773 CM7 is very full-featured for Fire now and very stable from what I have experienced.
[Kindle Fire General] Gam3r 4 Life:
Just got my Fire today. If its still under 6.2.1 Im going to root, twrp, and try out Cm7. Is there any 100% working methods for preventing the ota update?
[Kindle Fire General] Groovehog:
Im going to root, twrp, and try out Cm7

Yes. Your method stated above would do just that.
[Kindle Fire General] Gam3r 4 Life:
Thanks. I got it now. CM7 would prevent the OTA. Thanks
[Kindle Fire General] Gam3r 4 Life:
Hey guys another question. I see theres a new method for rooting, even with 6.2.1. Do you think it would be worth it to go ahead and accept the ota, then use the new method? What Im asking is this. Are the changes in 6.2.1 even worth it? Thanks
[Samsung Galaxy S (4G Model)] soccerman77:
Any easy ways?

I cant even find them unless i try to send a SMS
[Samsung Galaxy S (4G Model)] jager555:
You can just long press from your contacts list and delete. Out you can hide them.
[Samsung Galaxy Nexus] Neo3D:
How do you make a shortcut to the WiFi settings on the desktop? In the other Android, we were able to make shortcuts to any setting, was that removed in ICS?
[Samsung Galaxy Nexus] afilopou:
Go to widgets.There is a widget called Settings shortcut.Move it to your homescreen and you are going to have the menu of available settings.The last one is Wifi
[Samsung Galaxy Nexus] Neo3D:
Oh, so that's how it's done now. THANKS!
[Samsung Galaxy Nexus] Neo3D:
Hmmm, I noticed that there are no "direct" shortcuts available anymore, is this true?

Kinda sucks cuz I use Simi Clock and wanted the battery launcher to open up the Battery Setting screen.
[Samsung Galaxy Nexus] artvandelay440:
I use widgetsoid to add toggles to the notification bar, which will also launch wifi settings directly when pressed. (or any other setting you want) it has a widget too.
[Samsung Galaxy Nexus] weedahoe:
tons of 3rd party apps that also do this and a better job also
[Vibrant Q&A, Help & Troubleshooting] M9x3mos:
Kind of like the title says...

I was wondering if anyone can point me in the direction of a 2.3 rom that has wifi calling and functional gps.

Tried most recently Simply stock jwt and about 4 other roms none really worked. Simply stock ran great just couldn't get the GPS to lock at all wifi calling connecting but was robotic sounding.

Any recommendations would be greatly appreciated?
[Galaxy Note GT-N7000 Accessories] Final5k:
I just came across this auction on ebay. The seller sells the battery packed in retail packaging and this really seems to be a genuine battery. Actually there is only 1 person who has purchased it - is this person on XDA here and can share his opinions about the battery?

http://www.ebay.com/itm/GENUINE-SAM...315?pt=LH_DefaultDomain_3&hash=item2a1756f563

Edit :

Here's another ebay who is selling a Genuine looking battery. Since it is in retail packaging, this seems genuine but we need confirmation from someone who is willing to buy it.

http://www.ebay.com/itm/SAMSUNG-GAL...AU_MobilePhoneAccessories&hash=item1e69c31f76
[Galaxy Note GT-N7000 Accessories] ericshmerick:
This place got it before Samsung itself?

Suspect, at best...
[Galaxy Note GT-N7000 Accessories] Final5k:
Don't know but if the battery comes in the retail packaging like in samsung shops, this could be the real thing. Again, we must wait for confirmation from someone who bought it.
[Galaxy Note GT-N7000 Accessories] guent_peer:
Still no notice from amazon about when the original battery will be available...:(
[Galaxy Note GT-N7000 Accessories] xAnimal5:
If you guys want the OEM battery, just order from expansys. Mine just arrived for $37 USD and it is the only truly Original battery I've seen so far.

EDIT: It's $35 now and they accept paypal for it
[Galaxy Note GT-N7000 Accessories] Final5k:
Edited the 1st post to include another ebay link - seems like another genuine battery.
[Galaxy S II Themes and Apps] HellcatDroid:
With ICS on the horizon this might not be needed anymore....

But ICS having this feature as an Android feature, it made me looking again into finding out how to enable the device encryption Samsung added to it's Gingerbread ROM.

And I succeeded :D :cool:

And so I can present to you a little app that "just lets you enable device encryption" without the need for adding an Exchange 2010 account.

Like it? So do I :D

Don't care? Then move along :p

(i) some information regarding custom kernels in combination with device encryption can be found here!

Market links:

[ SGS2 Device Encryption (FREE) ]

[ SGS2 Device Encryption (PRO) ]

Screnshots:

Hope some like it :)
[Galaxy S II Themes and Apps] niko1986:
Great work Hellcat, going to buy the app but just need to clarify something.

You say no custom ROM but does this include non stock kernels? Apart from a kernel my S2 is stock.
[Galaxy S II Themes and Apps] HellcatDroid:
Unfortunately it really needs a stock kernel as well.

The device encryption makes use of the recovery binary (even in normal OS boot mode) to "unlock" the encryption when turning on the phone.

Even having the usual busybox symlinks (while having the original recovery binary) in /sbin breaks it and it just gets stuck, doesn't even show the password prompt.

What DOES work as far as custom kernels go, if it is stock kernel based (a total MUST, because of the crypto drivers), has stock recovery (NOT CWM!) and NO busybox symlinks in /sbin.

I made a "modded" version of my own kernel that indeed does work that way.

(That alone took me three days to figure out, WHY it breaks on custom kernels.)

So, unfortunately this is an "either, or" situation.

Either you use the device encryption and stay all stock - OR you go custom kernel/ROM but can't use device encryption.

It's a matter of personal priotities/preference, I for my part are going with the device encryption - I just love making digital fortresses out of my things (and yes, I DO use truecrypt on all of my computers :rolleyes:) - fortunately a rooted system stays rooted, no matter of the kernel.

So, I can see this isn't for everyone, but at least we have the option now :D
[Galaxy S II Themes and Apps] niko1986:
It is a tough choice, although I would like full encryption. Though it is obvious as it would likely be less secure.
[Galaxy S II Themes and Apps] looslip:
I'm glad that somebody is looking into Android security today rather than wait for ICS to fix it. Is this doing a block level encryption on the data?
[Galaxy S II Themes and Apps] HellcatDroid:
Yep.

It encrypts only used space at first (to not take about 2 hours, because it might take that long if your int. and ext. storage is rather full, like in my case) and after that the partitions are mounted via "mapper devices", so yes, the whole partitions are encrypted block-wise.

You also can't mount them anymore (like when you adb shell to it) due to the encryption and "mount" not finding any recognized filesystem (you can mount the mapper devices in /dev/mapper instead once the correct password has been entered, that's how the system does it on boot after password entry).

And you got to thank Samsung for this (IMO) amazing feature, they are the ones who put it in :)

I just figured how to enable it without an Exchange account.
[Galaxy S II Themes and Apps] looslip:
Do you have any reading that I can do on how encryption keys are used and stored? I'm in the information security space and want to see how viable something like this would be in an enterprise setting.

Thanks for doing this and sharing the knowledge with us!

:cool:
[Galaxy S II Themes and Apps] HellcatDroid:
How and where keys are stored depends on the implementiation.

Samsung's device encryption is actually aimed at use in enterprise environments, and IMO it's rather well implemeted.

The actual "device encryption key" used to crypt the paritions is stored in /efs/edk_p and is itself encrypted with the user's unlock password.

So, even if you gain access to the device, the edk_p file and everything, you can't do a thing without the user's password.

The whole thing even supports (optional, must be explicitaly enabled) password recovery (in case you forgot your's) but when that's to be used it wants to mail you the reset password - but since we're doing it here without a linked/added Exchange account, that doesn't work.

But maybe I get an idea how to still make use of this....

I hope this answers your question a bit :)
[Galaxy S II Themes and Apps] looslip:
Absolutely! Thank you for the reply.

The inherent weakness in most one-off device encryption tools is key management and the security of how the keys are derived and kept, especially if stored on the device that its encrypting.

Anyhow, this is much much better than what the community already had in the first place. No solution is completely fool-proof but this is big step in the right direction.

Thanks again.
[Galaxy S II Themes and Apps] kalpik:
Great work! Will help a lot of people (not me though, can't let go of custom ROMs and kernels :D)
[Galaxy S II Themes and Apps] HellcatDroid:
Yeah, it's kinda "sad" this is so bound to being stock.

I am thinking about doing an at least similar thing that is more "generic" and would best case work on any Android on any device, but all ideas I came up so far (and that make half way sense) always require some level of kernel supprort.... :(

Well, maybe I'll be hit by a bolt of ideas when under the shower one day....
[Galaxy S II Themes and Apps] kalpik:
Patches requiring kernel support is not an issue IMO. Even Voodoo Sound etc required kernel patches, but look how popular it became! Every i9000 custom kernel has those patches.
[Galaxy S II Themes and Apps] sean.dexter:
Thanks best tool ever!

This is the best tool I've ever seen from a security perspective. Great work.

Will it work on the Galaxy Note as well? Since I have an S2 for work and a Note for private use, it would be really cool to know :-D

Best regards and thanks again,

Sean.
[Galaxy S II Themes and Apps] HellcatDroid:
Hmm, good point.... I shall brainstorm some more about this....

AFAIK the S2 is the only device Samsung added those functions.

But feel free to give it a shot, worst case: the functions are not available and the app will force-close when trying to set them.
[Galaxy S II Themes and Apps] BongoCZ:
So does this mean there might be encryption & bln or not? :)
[Galaxy S II Themes and Apps] HellcatDroid:
Don't wanna tease people too much, but yes, my phone is encrypted and BLN'ing :cool:

As mentioned above, custom kernels CAN work when they stick to some "rules" regarding the /sbin folder of the initramfs.

I am currently thinking about how to apply it to my kernel and will also write down and post the details about what to take care of, so everyone knows and kernel devs can make compatible builds of their kernels if they want.
[Galaxy S II Themes and Apps] BongoCZ:
And is there any chance you would share it now? :) I suppose it's not the one in your signature.

Edit: And what about battery drain? Have you noticed any difference?
[Galaxy S II Themes and Apps] HellcatDroid:
I'll build, write and post and share everything I have as soon as time permits, I'm not even at my PC at the moment.

The kernel I am currently running on my phone is just a "quick'n'dirty" test, by no means suited to be released.

Don't worry, everything will be posted :)
[Galaxy S II Themes and Apps] HellcatDroid:
OK, as promised, here's some information regarding custom kernels and device encryption:

What is it that breaks device encryption on custom kernels?

Two things: a custom recovery and additional commands (usually busybox symlinks) in /sbin.

A custom recovery like CWM is a definite death sentence as the device encryption mechanisms in the system rely on the original Samsung recovery binary in /sbin.

It's that binary that takes care of setting up the mapper devices and passing the crypto key to it so the encrypted partitions can be accessed.

Having said additional commands in /sbin can also make it fail, as the recovery binary calls a few external commands and if (due to path lookups) a busybox command from /sbin is executed instead of the Samsung version from some other location (/system/bin or /system/xbin for example) things fail and the device is not able to boot to the crypto stuff not properly initialized.

A custom kernel with BLN and some other goodies:

So, what I did to my own custom kernel was to put the original recovery back and wipe /sbin clean.

And now it works.

Of course it lacks a few things due to this, like CWM - and even if CWM would run (it DOES include a launchable CWM5, see below) it really isn't of much use as CWM would try to access the physical partitions for doing it's stuff, but those partitions are encrypted so it WILL fail, as you need to access the mapper devices instead (more info on those below)!

Also if you run around on a shell session (during normal OS or recovery) you're missing the busybox commands - but I put a "workaround" in for that" ;)

So, what do we have here:

custom kernel based on my v1.25 root kernel

full root shell access via ADB when booted into recovery!

(on normal OS boot adbd still runns as non-root!)

all features that are done by code edits (like BLN, touch sensitivity, etc.) WORK

some features DON'T work (basically everything that accesses /data or /sdcard during bootime, like init.d from /data/etc/init.d (init.d from /system works!) or the auto-import stuff from /sdcard/import).

Reason: the partitions are encrypted, the scripts fail to access them

some additional commands for convieniece:

backup - supposed to be run when booted into recovery, makes a backup similar to the CWM one to /sdcard/backup (backups EFS, kernel, system and data)

bb - installs all the additional busybox commands to /sbin at runtime - as the system (or recovery) is booted and the crypto is all setup, this is save to do (it just breaks stuff during boot).

So you can use all busybox commands and goodies as you (or apps relying in it) know it.

cwm5 - supposed to be run when booted to recovery, kills the stock recovery and starts up CWM 5.0.2.3.

As stated above, it won't do much good, but doesn't hurt either to have it.

Download: http://f.lui.li/get_227_c933.html

Any more questions?

Gimmi gimmi! ;)
[Galaxy S II Themes and Apps] BongoCZ:
Thanks! Now, do I really need original Samsung ROM, or is any original Samsung based ROM enough?
[Galaxy S II Themes and Apps] HellcatDroid:
Not exactely sure about that.

In theory, stock based should work - but then again you never know what the ROM makers changed or took out.

So, only actually giving it a try with your fav. ROM will tell....
[Galaxy S II Themes and Apps] hchxoom:
Been looking for a way to use encryption - any idea whether this will work on an i-777 (at&t) version sgs2? Thanks!
[Galaxy S II Themes and Apps] HellcatDroid:
It should work on the AT&T S2.

The device encryption is an officialy announced feature (by Samsung) of the S2, I doubt they would have taken it out of the US carrier variants.

You can just just try, grab this one:

https://market.android.com/details?id=net.hellcat.droiddev.sgs2devencfree

(it's the free one, so no risk)

Try to enable the encryption.

If it works, you will notice ;) (there will be a "encrypting internal storage" after the first reboot and a "encrypting USB storage" in the notification area when the system is booted).

Worst case: nothing happens.

Once enabled you can disable encryption again at any time, without loosing data, the phone will reboot and decrypt everything again.
[Galaxy S II Themes and Apps] hchxoom:
Thanks! Need to flash back to a stock kernel and rom to test - will do so over the next day or so and report back. Almost hope it fails - I'm going to miss some of the custom mods if stock is the price for encryption.
[Galaxy S II Themes and Apps] HellcatDroid:
Yeah, that's the downside - as it's a thing added by Samsung to their 2.3.x builds on t S2.

I am thinking for ages about a way to achive at least something similar in a more generic way so that it might work on most ROMs and devices, but haven't been really lucky with my ideas so far (most were not satisfying enough).
[Galaxy S II Themes and Apps] xdadroid88:
I think Samsung also sells the Note as Business Device.

So I just encrypted my Note with the Free edition. First I got a force close popup but after that there was a popup telling me that the device gets encrypted after a reboot and that worked without problems. The encryption took about 2 or 3 minutes.

Now even when I start your app and want to leave it with the back button I get a force close. I guess this could be an incompatibility between Android 2.3.5 (S2) and 2.3.6 (Note).

So far everything works as before.

How can I check whether the data is really encrypted?
[Galaxy S II Themes and Apps] xdadroid88:
@ HellcatDroid

It seems that there is a problem with other security advisors.

I have one ActiveSync mail account active which also has an security advisor. As soon as I open this mail account in the standard mail app I get a notification from your security advisor that the device will now reboot for device decrytion. I can close this popup with cancel but after a restart of the note the data gets decrypted nonetheless.

Any idea whats causing this?
[Galaxy S II Themes and Apps] charon420:
Hellcat. Awesome work man! This is something Ive been looking for since early last year.. I eventually just resolved to just waiting for ICS.. But now not^^ Everything seemed to work as planned on Korean Stock Rooted 2.3.6
[Galaxy S II Themes and Apps] HellcatDroid:
Would be pretty cool if this works on the Note as well.

About the FC: might be due to some policy settings not being implemented, so likely it's some "method not found" exception.

If I can find out which one it is, and if the encryption is really available on the Note I can make it fully compatible with it.... cool :D

About checking: open up a shell (terminal app or adb) and execute "mount", look for the /data mount, if the originating device is something like /dev/mapper/data it's encrypted, if it's /dev/block/mmcblk0p10 it's not.

The policies of that Active Sync account explicitly set the "Requires Encryption" policy to "NO" (instead of just leaving it alone) - hence causing the decryption.

Usually policies add up and the most strict one takes effect, Samsung seems to have made a slight mistake here as they were under the assumption those settings will be used exclusively by the Active Sync engine.

Not much I can do against that.

But I will play around a bit with that scenario and try to find a way around this issue.

A workaround would be to launch the app after the "Going to DEcrypt" message and (re)enable encryption - nothing will happen the next reboot then, as it's already encrypted.

I know, not the most user-friendly solution, but that's all I (or the app) can do about it.
[Galaxy S II Themes and Apps] xdadroid88:
It seems to be a little bit more complicated.

Just to be sure I tested your app also on my S2 and there the decryption problem doesn't exist. I can read my mails from the same ActiveSync account without any problems.

Then I checked the security policies of the ActiveSync account and to my surprise "Geräteverschlüsselung erforderlich" is listed and checkmarked. But I'm sure that so far neither my S2 nor my Note where ever encrypted. How can this be?
[Galaxy S II Themes and Apps] charon420:
One thing ive noticed is the battery lvl is being drained at an alarming rate than before hand. Where now a full battery will last a few hours compared to over a day from before. It seems the system_level is taking up this usage where the encryption app is being utilized. Need a better battery now lol
[Galaxy S II Themes and Apps] HellcatDroid:
Hm, now I'm totally confused.... :confused:

So, same Active Sync account, just different S2 and it doesn't ask about decryption while on the other it does?

Hm, the encryption process was over yet, i.e. the system wasn't still encrypting internal or external storage? (because yes, THAT takes a huge impact on the battery, but once it's finished it's fine).

I can't really notice any difference in battery life on my S2.... :confused:
[Galaxy S II Themes and Apps] charon420:
It may be an app that is writing or checking the data in the background. I go through my running processes one by one and see if i can determine the culprate. May take a few days for me to report back^^

Update: it appears the email widget was the cause of the battery drain. Although settings were to manually sync it still caused the drain. Solution.. Remove widget from desktop. (Turns off system proccess)
[Galaxy S II Themes and Apps] xdadroid88:
It seems that it just takes longer until the popup for the decryption comes up. I tested the ActiveSync mail account and everything looked ok, then I put the S2 aside. About 10 hours later I wanted to check the battery usage but the S2 was completely switched off. After turning it on and entering the password the decryption process of the system started! And even worse after that I got one FC after the other. I never had something like that before. Battery level was at 60 % so that was not the cause that it switched off.
[Galaxy S II Themes and Apps] BongoCZ:
I tried it and it works fine with [ROM][2.3.6][KK2] Simple & Clean v2.4.3 'Performance & Battery Friendly + Jkay 13.2'

but i have a problem with flashing zips - when I try it from the recovery in this kernel, it ends with

E:signature verification failed

The zip package is ok, using another kernel flash was ok.
[Galaxy S II Themes and Apps] HellcatDroid:
The Active Sync account thingy is really weird and frankly totally confusing me at the moment....

I'll play around with that a bit and see what I can see....

Yeah, it's running stock recovery, not CWM.

If you use the kernel I linked to earlier in this thread, try this:

boot to recovery

open a shell via adb from the PC

run these two commands:

bb
cwm5

try again
[Galaxy S II Themes and Apps] BongoCZ:
I also had to manually mount the sd card using adb shell, but then it went fine :) I also bought the PRO version and external sd encryption is in progress ;) By the way does anybody have any idea how long it would take to bruteforce(/any other type of attack) the decryption key from edk_p file?
[Galaxy S II Themes and Apps] pulser_g2:
Presuming that the algorithm is known, and I'm sure it can just be reverse engineered, it depends pretty much on the length of your password, or should I say passphrase?

If your password is "hello123" or "xda", then it's not going to fare too well in my eyes :)

Pretty much any encryption like this will be attackable "offline" on a computer, with a key file or encrypted piece of data. I can open zips using some useless single threaded program at hundreds of millions of attempts per second, before a 40% overclock...

So imagine overclocked, and multi threaded, or even gpu based :p

I'd not fancy putting the farm on it being impenetrable, as ultimately you need to type in the password, and that limits 99% of people's passwords to being short and simple...