yashsingh1/xdaforums huggingface dataset:
[Security Discussion] optimumpro:
Wipe after 10 attempts, see here https://github.com/CyanogenMod/android_device_qcom_common/blob/cm-12.0/cryptfs_hw/cryptfs_hw.c

A factory reset wipes data, so whatever happens to master key is not significant. But even if the master key is reset, there is no use of it in terms of trying to get previously encrypted data. And by the way, the term reset is not correct: if you do a regular reset, the master key is not touched, as it is not sitting on data partition and if you wipe system and data, your master key is gone and the new one will be generated only when you enable encryption again.

I don't understand your consistent point that users won't bother with long passwords, when Android provides for separate passwords one for boot/encrption and another for screen (which is not used for encryption). As I have already said, I use an over 60 character boot password and a short screen pin. If I need to reboot the device, I use soft reboot, which does not require the password at all. So, having a long password does not create any undue burden.

Again, data/disk encryption is valuable, because it protects your device when it is off, meaning, no one can access your data... I have close to personal experience with "sophisticated attackers": they can do nothing with properly encrypted device that is turned off...

Closed source vs. open source. I am not saying open source is secure. I am saying that open source could be examined unlike proprietary one.
[Security Discussion] CHEF-KOCH:
My last words on this:

Well in the source nothing to user data gets wiped, only stuff that protects android system related files which proofs that the user data aren't safe if someone use forensic image and cloned everything.

Short screen pins can be cracked in minutes so as long we can sideloading anything before or after a boot especially if not all stuff is mounted it is still a risk.

Fastboot/softboot or whatever you want to call it isn't available on every device so you whole argumentation about complex passwords are useless (for example a friend of mine recently got the LG G3 which had fastboot deactivated). And of course if you got an error like kernel panic or other crash you can't fast reboot which also required that complicated and complex password - especially on mobile devices this is pretty annoying.

Again FDE on Android is placebo that's all, as long the user can dump the whole system and crack it on a PC which is powerful enouth it will be always useless. Apple use a unique key (if we can believe it) which can't be extracted with any tool or read out during the boot (maybe some day but I don't know any tool yet) so everything like brute force must be directly on the device which takes a lot of more time compared to a computer with an external powerful nvidia card and tools like hashkill/hashcat.

About explaining closed source, if you are good enouth you can reverse engineering most of the code - you don't even need to deobfuscate all stuff but in most time if you know the basics you know which weakness e.g. the encryption may have.

As long you not understand that sideloading is the biggest problem in android you not understand that all can be cracked soon or later and because you use xyz do not means that millions of stock users doing such complicated steps too to "secure" the phone which do not protect all stuff except the os itself. Android has defenses yes, but it is more to protect itself and not the private data that's the conclusion. It's a good step what was made with lollipop but there are still attacks which can't be that easily blocked, especially if the user doesn't know how or most if the mechanism are deactivated or simply to complex.
[Security Discussion] optimumpro:
And here are my last words. Click the link in the previous post and you will see code to wipe user data. There is annotation that says we will wipe everything related to encryption followed by the code itself that contains the words "wipe user data":

} else {

if(ERR_MAX_PASSWORD_ATTEMPTS == err)

wipe_userdata();

With regard to cracking everything soon, this is just your opinion that is not based on known facts. And one of the facts is that if spooks could break the encryption, they wouldn't need back doors and weakening.

Again, I fail to understand your point about users not using long screen passwords. You don't need long ones for your screen. But let's leave it there and agree to disagree. :p
[Security Discussion] optimumpro:
Look here for kernel changes:

https://github.com/AOSP-Argon/android_kernel_sony_msm8974/commit/29d918c1f11247602c58096a62084811bccc328f
[Security Discussion] CHEF-KOCH:
It won't touch userdata at all, it wipes only (as written) disk encryption related data stuff but I'm talking about sideloading user data and this will never be wiped since this will destroy other stuff too - so this prevents only some attacks if you just start you're phone. - Or if you dump the data without - in a locked state - the master key.

The stuff you linked is also different from my link from AOSP project since it's CM, also a mistake, because CM isn't stock or based on OEM's firmware. So all you're stuff may applies only to custom firmwares - I'm talking again about stuff which use the mass and not only certain "expert" people.

This is also from CyanogenMod which also only affects /cache/recovery which doesn't matter if the system was already booted success and (as shown) some stuff was already compromised or running in the background.

Yes and your wrong opinion is that it isn't crackable, same was said years ago about TrueCrypt which now is labeled as unsafe and I already mentioned tools which break it.

Seems you're to ignorant to understand which possible negative effects may comes with side-loading. As long you not understand this we can stop the entire discussion here (I already gave up because you don't know s much as I do which tools can break stuff) - it will be cracked and the the dm-crypt stuff was already cracked in Android 4. because of some fixes that doesn't mean anything. Again, because you use xyz that doesn't mean all use the same stuff you already ignored this several times now and I already said that - but okay.
[Security Discussion] optimumpro:
I guess we speak different languages. My point is (and it stands) that if encryption is properly implemented, there is no way to get data from unmounted encrypted partition. Let's forget about wiping, any sophisticated attacker will take an image of the device and then try to break a copy. However, to mount data, he will have to bruteforce my 60 character password that will unlock master key or break 256 bit AES. Good luck on either front. And I am not talking about stock, aosp or Cm roms. It makes no difference, the bottom line is he won't be able to do either of the above. I also don't care about careless users. They have a right to be ignorant and most enjoy it very much. Linux (on which Android is based) was not created for ignorant users...
[Security Discussion] CHEF-KOCH:
No, we are talking the same language but implementation has nothing much todo with the fact that attackers can bypass this with several 'tricks'. This was - and will always possible as long we can dump/inject/sideload the OS. You can't implement something if you don't know if already xsz was released and don't know how to fix it... (also called 0day).

That's not true, I agree that cracking/brute forcing ON the device is "almost" impossible yes [but remember hardware from the devices always getting better and better] - the reason apple implemented there unique ID directly on the hardware] that's totally okay and this will mostly destroy all known attacks - yes!

Yes - and, I crack 7 chars in around 5-9 hours. With the factor of ³ it took around 20 hours+ for each new char (NSA/FBI have a lot of more powerful hardware).

It make no sense to crack on the device (agree) but what you want understand at all that nobody need to crack something if it can be bypassed with several known attacks. For example you can set a 1000 char pass and a strong pin to unlock, but that won't prevent that someone steal your phone after all is unlocked. And of course you always miss the human factor, some people not using any pin or install any app from untrusted sites like apps.evozi.com (which was recently marked from OpenDNS as phishing site) so we don't need to talk about security as long there are several scenarios which is almost impossible to fix.

Yes, because you are the smartest guy. And all except you are stupid.. Wonderful argument. If google want a secure OS it would be already possible since the first release and not 5 major releases - so think about it. It's not only because NSA there is always a huge interest in collecting our user data, since, oh - they make money with it (remember the AOSP is non-profit except the OEM exclusive stuff).

But I agree this scenario is not (yet) crackable (and will be the challenge for the next defcon):

- ADB disabled (deamon not present and not running) - SU completely disabled

- Stock recovery/bootloader

- Strong passwords for recovery/pin/boot (if it is possible)

- AOSP based OS

- No pre-installed rootkit/no hdd/sd timing attacks due infected firmware

- No custom kernel

- No cold boot ( or modified DMA-based attacks, cold boot attacks, and evil maid attacks)

- No self decryption risk

But nobody I know including myself use such scenario, people always want to mod this and this and some stuff is very uncomfortable especially if a "power" user want to handle adb all the time. I must admit we are not all affected by such interest in cracking such complicated FDE, but as long if there are possibility I not recommend it at all or only for people that are smart enouth.
[Meizu MX] eltdesign:
Yes My meizu mx4 home button started to not working..I tryed to reset reboot also ınstall firmware again but no luck! First reboot did the trick and it worked little bit and after it stopped forever! When i push to home button area it push like one step up. ( i didnt tryed to install firmware with clear data option) but some of people also tryed that and it didnt effect something.. Any1 with same problem or found a solution ?
[Meizu MX] Learnincurve:
I and many others have the same problem. So far the only known fix is to replace the digitizer.

This is a well known problem with the hardware which Meizu are trying to avoid by saying there's a software fix just around the corner. Something they have been telling us for months now. There's a thread about this on meizufans.eu

Upgrading the firmware sometimes fixes the problem for a few hours or even days, but the problem always returns.

Best fix would be a different phone (maybe the MX4 Pro?)
[Sony Xperia T3] pranata.swijaya:
Hello,

I am new to Android development so please pardon me if I get something wrong and does not understand clearly.

I want to modify Android NFC stack to accomodate a tag that I want to control from Android application side.

My tag is comply with ISO/IEC 14443-3:2001 Type B.

* First before modify anything (Xperia T3 running Stock ROM 18.1.A.21), I have tested NFC TagInfo application from Hadenberg:

play.google.com/store/apps/details?id=at.mroland.android.apps.nfctaginfo

Of course the application cannot process complete information because my tag is limited upto ISO/IEC 14443-3B.

But the application can show messages that my tag is detected as ISO/IEC 14443-3.

With this same application, different phone shows nothing. I have tested it on Nexus 5, Samsung Galaxy S5, and Sony Xperia M.

So I decided to work on Xperia T3 because it is the only one who can detect and report my tag.

* Then I tried to build both AOSP (KitKat and Lollipop) for Xperia T3 based on these guides:

developer.sonymobile.com/knowledge-base/open-source/open-devices/aosp-build-instructions/how-to-build-aosp-kitkat-for-unlocked-xperia-devices/

developer.sonymobile.com/knowledge-base/open-source/open-devices/aosp-build-instructions/how-to-build-aosp-lollipop-for-unlocked-xperia-devices/

By the time I write this thread, the guide directs me to use KitKat version 4.4.4_r2 and Lollipop version 5.0.2_r1.

* I can build and flash both of these AOSP ROM to Xperia T3, I can boot to the homescreen and control the device normally.

However it has problems:

- on AOSP KitKat : I cannot enable NFC from phone settings. It is disabled and greyed out.

When I touch it, it does not automatically checked, I have to lock the screen and unlock it then the NFC settings would be checked.

But NFC TagInfo application reports that NFC is not turned on, so I cannot detect any tags on this AOSP KitKat.

- on AOSP Lollipop: My NFC works, I can enable it from phone settings.

Using the same application again which is NFC TagInfo, I can detect standard NFC tag but now the application cannot detect and report my ISO/IEC 14443-3B tag.

Question:

1. Can someone confirm that NFC on AOSP KitKat for Xperia T3 is also does not work?

2. Because my NFC does not work on AOSP KitKat, I cannot compare it to Sony Stock ROM (18.1.A.21).

I am wondering if the same application (NFC TagInfo) can detect my tag on Xperia T3 stock ROM (KitKat, build number 18.1.A.21) but cannot detect my tag on AOSP Lollipop ROM (5.0.2_r1).

Does Sony has proprietary modification on its Android NFC stack?

3. I found on Sony Open Source download:

developer.sonymobile.com/downloads/xperia-open-source-archives/open-source-archive-for-build-18-1-a-1-23/

It contains both kernel and some source like platform.

Is it possible for me to use it and build the same Sony Stock ROM?

Thank you for your concern.

Note: Sorry I have to modify the link because it prevents me from posting outside links.
[Xperia SP Q&A, Help & Troubleshooting] zengraviz:
Help! I think i bricked my phone!

so i was going to install a rom, as always i wipe this and that

but accidentaly my sdcard are not detected, there's nothing on my sdcard

but i already wiped everything

i rebooted my phone and only to find out that my phone now romless and cant boot into recovery!

help please anyone :(
[Xperia SP Q&A, Help & Troubleshooting] adil786ali63:
try flashing the stock Sony ROM via flashtool... and try again by installing a custom recovery over the stock ROM... Hope it helped!!! :)
[Xperia SP Q&A, Help & Troubleshooting] aganhakiem:
or maybe you can try to flash recovery via flashtool bro,

hope this will help :good::laugh:
[Xperia SP Q&A, Help & Troubleshooting] zengraviz:
i just flashed stock .ftf file and my phone boot normally thanks
[G3 General] kitelooper:
Hello, i would like to ask the developers on xda if they know aproximate the time Root will be ready on Official Stock Lollipop Lg g3 (NOT lollipop rom).

Your answer can help a lot of followers on xda that wanna keep LG G3 Official lollipop without installing any rom... Lots of ppl just searching and asking about Root on lollipop as it is.

Thx for your answers already.

Keep up the good wrok.

p.s. Plz don't say go back to kitkat root and install rom with lollipop and root --- we ask for the root of the official lollipop, thx.
[G3 General] davidez25:
I agree too. I would like to
[G3 General] MarcusOptimus:
I Agree.
[G3 General] Neontc:
Eta's are the biggest no-no on this site. These developers do this stuff out of the kindness of their hearts, aside from jobs and families. Asking for a time frame for any sort of development is a huge slap in the face of the devs. With that being said, all you can do is what you said already, go back to kit kat and flash a rooted lollipop rom, and be patient with the devs, as this is not their job.
[G3 General] kitelooper:
Plz read before you answer.. We asked not to say about Roms and staff..

And ppl dont need axcact date only if it will take 1 to 2 months or 6-year, so is not excact date.
[G3 General] Neontc:
Not sure what you meant by that, but you clearly asked for an eta of a root method. The only way you can have rooted lollipop is to downgrade and flash like you mentioned, and wait patiently for something to come up.
[G3 General] kitelooper:
Read before u answer plz..We already know that so i ask for something else obviously.
[G3 General] Neontc:
Haha, alright man, good luck.
[G3 General] GuestK00280:
No, no one knows the time.

But it's definitely not before G4 is released. If there is a root exploit for LL, it lies in LG's services, and it would most likely apply to all LG phones running 5.0. Releasing something like that before the release of G4 and other 5.0 phones is a bad idea.
[G3 General] ChongoDroid:
Read before you answer pls

No ETA, period. Bye bye now.
[G3 General] teddy0209:
I don't think there would be further development on root on g3, (same w/ the bootloader) as we have already a working custom recovery... Just my opinion though... [emoji4]
[G3 General] joooe:
^This!
[G3 General] BreakingVZW:
Gasp! iPhone! Get him! ;)
[G3 General] topet2k12001:
Root Is Possible!

Hi Friends,

I am a fairly new owner of a D858HK (dual-SIM) variant of the LG G3. An update to Lollipop came in so I got interested.

Focusing instead on getting root and "bump'd" TWRP (custom recovery), I figured it out through the help of [MENTION=2684188]autoprime[/MENTION] and his thread.

I know there are a lot of developers who are able to "tear down" the official Lollipop firmware, pre-root it, and repackage/distribute it, however, the D858HK variant is not as widespread as the D855 so I had very little hopes for custom ROMs. So I documented everything that I have learned through reading the relevant threads, tested it on my LG G3 variant (with 100% success rate), and put up a thread to share it. You can check it here: click me!

I'm interested to know if this will work with other LG G3 variants. If it does, please let me know. :)

In the meantime, this finding got me interested in learning more. I'll probably start with the easy ones like pre-rooting and repackaging the stock firmware. Who knows, I might eventually progress to where I can modify/create a ROM (that's ambitious, but not impossible).
[G3 General] GuestK00280:
Nice guide!

This will work with any phone.

You can easily create a flashable zip and share it for you fellow d856/857/858HK users.

Just take META-INF (updater-script) from robalm's zip, bump boot.img, substitute d855 images with 858 ones, and voila! You have a repacked 858 stock rom.
[G3 General] ferdinez:
Well ETA stands for Estimated time of arrival not exact time of arrival so what you are asking for is an eta!! we would all love to get some info on the root for lollipop but keep it cool man. you dont have any developer here on your payroll so if they say don't bother them about ETAs then you better get a glass of tequila and chill out. and hope and pray for ETA. or better still swap your g3 for a nexus.
[G3 General] Marcovanbasten:
Root available for LL
[G3 General] agritux:
You can root. Link: http://xdaforums.com/showthread.php?t=3050179

LG-D855 cihazımdan Tapatalk kullanılarak gönderildi
[G3 General] dimkit:
Finally that's very good news
[G3 General] tholyir:
better written guide for lollipop root:

http://xdaforums.com/android/development/guide-root-method-lg-devices-t3049772
[G3 General] QSR1:
Thanks

Thanks for all important information. I have just moved from LG F400K (G3 Korean variant) to D858HK. I thought that there is no twrp/roms/lollipop firmware for D858.... But thanks to you...

Please further help us by creating a lollipop flash-able rom for D856/857/858 users. It will really help lesser expert users like me.

Please also clear one more thing. After rooting stock lollipop, i can just simply flashed your shared file "twrp-2.8.4.0_d858-signed.img" for recovery? (i do not understand what to do with file in sharing folder "lollipop-bumped-boot.img")

Thanks very much!
[G3 General] topet2k12001:
You're Welcome

Hi @QSR1,

You're very much welcome. :)

I am very new to the LG G3 myself, and as I mentioned in the First Post (First Page) of this thread, I am not a developer. Although I feel flattered that you think so. :)

The "Imageprep" is the very first script that I successfully programmed as I merely "forced" myself to learn how to do it. I was fueled by the desire to help others prevent making mistakes, because the unfortunate reality is that people don't like to read - they immediately jump ahead and do stuff that may be dangerous. Maybe this mindset and behavior is the influence of technology in itself...people want everything fast/quick, like instant coffee (just add water, wait 3 minutes, and BOOM! Coffee!).

That said, my real intention at first was to re-package a stock Lollipop firmware of the D858HK, pre-root and pre-"bump" it, and then share to everyone. But since I am still reading how to do it, I studied basic Shell Scripting to come up with a quick solution while I learn more difficult stuff in the background.

You are another person who inspired me to pursue my learning. I will read more about it and I will try. But please expect it to take a while.

For the lollipop-bumped-boot.img in my "Mega" Account: if you are a D858HK owner you can flash it. Although "Imageprep" also does the same thing, so I suggest don't touch the one in my "Mega" Account. Just to be safe.
[XDA Assist] mrigendra:
Hi all

I am trying to show battery level as a percentage while booting. I want to show the user before he gets to the android how much the battery is? But I am unable to find any info as if I have battery values how to show it to the user as a splash screen?
[Moto G Q&A, Help & Troubleshooting] bhanu9999:
Is there any way to hide sim number(status bar) in stock asian lollipop 5.0.2. ?????
[Moto G Q&A, Help & Troubleshooting] audit13:
Try this:

Open the dialler, click on settings, click on additional settings, and select the option you want.
[Moto G Q&A, Help & Troubleshooting] bhanu9999:
I meant in status bar. Sry i forget to write that in the question.
[Android General] Sushant Rohan:
[NOTE]. I will not be responsible to anything that you will done to your Phone Or Your SD Card but if you encounter any problem I will be there

[What It is] This process will increase your Internal SD card according to the size of second partition you made in the CWM Recovery

For this you may need the following things:

i. CWM Recovery

ii. Root Access

iii. Link2SD ( https://play.google.com/store/apps/details?id=com.buak.Link2SD)

iv. An SD Card

v. Root-Access

That's all

First Make 2 Partition Of SD Card

Do the following steps:

i. Make backup of your SD Card since our process requires formatting it.

ii. Go to the Recovery Mode. It may vary according to your phone

iii. Go to the 'Advance' option of CWM Recovery

iv. Choose the 'Partition SD Card' option

v. Choose SD-EXT Size(it may vary according to your phone, give 512 for 2 GB SD)

vi. Select 0 swap

vii. Wait and after the process is completed reboot you phone

Increase Internal SD card size by LINK2SD

To do this follow the given steps

i. Download and Install LINK2SD

ii. You will be prompted to choose among different file systems. Choose ext4 since it is the file system your recovery have formatted the SD Card

iii. Then a notification will appear 'Mount Script Created'. Reboot the phone.

iv.In the setting option of LINK2SD, check Auto Link. If you've some apps selecte Create Link and Mark all Options

Now you have done enjoy lots of heavier apps.
[Android Apps and Games] sale89:
Check out the description for this game: It's payback time! BECOME THE BOSS AND BEAT THE DICTATORS! Whack them! Smack them! Torture them! Beat 'em up! Go mad, show them what a wipeout looks like! You can't even imagine how relaxing this fun game can be.

Cool characters, amazing weapons and great gameplay.

Link for free download: Beat the Dictators

[IMG="pic1"]http://2.bp.blogspot.com/-zxfKeiBxc9k/VPQkPOCBjdI/AAAAAAAAACA/1UNMJXx9Cqw/s320/screenshot-2.jpg[/IMG]

[IMG="pic2"]http://4.bp.blogspot.com/-31kjxFB6VAg/VPQkRfMyEqI/AAAAAAAAACI/qqOfO7hY97o/s320/screenshot-1.jpg[/IMG]

[IMG="pic3"]http://4.bp.blogspot.com/-dBurP47Gnew/VPQkTp4it5I/AAAAAAAAACQ/5ogVO0fHY2M/s320/screenshot-5.jpg[/IMG]

Link for free download: Beat the Dictators
[Android Apps and Games] jonnyyxo:
Are you even serious?