yashsingh1/xdaforums huggingface dataset:
[XDA Assist] kloroform:
How do I get this notification back? I accidentally clicked Do not show this again checkbox and now when ever I enable Mobile Data, it doesnt asks for confirmation anymore

how do I get this option back?
[XDA Assist] v7:
Hello,

Thanks for using XDA Assist.

I'm not sure if you can bring that back without reflashing the ROM.

Maybe you can ask in Android Q&A,Help and Troubleshooting and find some help :)

___

v7

XDA Assist
[XDA Assist] kloroform:
will a Factory Reset work?
[XDA Assist] v7:
Yeah!Probably :)

___

v7

XDA Assist
[P3600 General] falmost:
Is it possible to create an RSS Feed for this Forum? I would be easier to find out about the new posts....
[P3600 General] blessipo:
You mean something like that? http://xdaforums.com/external.php?type=RSS2&forumids=313

B
[P3600 General] falmost:
Yes, that's what I meant! Thank You very much!
[P3600 General] zelidar:
This is great blessipo. Thank you very much as well :). I have now imported it in my mobile RSS reader right on the Trinity.
[Sony Xperia ZL] Linwood.Ferguson:
I have a C6506 that is unlocked, have checked via the service code. Not just unlockable but unlocked. Certain.

I've used both older flashtool64 that worked before (0.9.11.0) on a Surface Pro (windows 10) and newer (0.9.19.10) on a desktop (Windows 10 also).

In both cases I can flash 10.7.a.0.222 for C6506. I also can flash 10.3.a.0.423 on the Surface (did not try on others). It boots, it works, no issues.

I can get in fastboot mode on the phone (blue light), but on the surface with the older Flashtools (and associated drivers) I cannot access the phone at all, just waiting for device.

On the newer flash tools with drivers installed (turned off signing verification) I can get into fastboot and do things like a "getvar version", but I cannot do more complex things like get the unlock status, nor can I flash a boot image (in this case from CM 12.1). It says "Command not allowed" in the write phase. Yes, the phone is unlocked, really, at least it says it is, and I did do an unlock code with legitimate Sony provided codes. And previously rooted using it as unlocked.

I've also tried getting root with a pre-rooted 10.7.a.0.222 -- I can get an older version rooted, put recovery on it, I can do the install of the zip and it completes -- then boot loop. This is using Beta-SuperSU-V2.52.zip and zl-lockeddualrecovery2.8.23-release.combined.zip with PRFCreator. (The recovery is also what I used to do the install). Boot loop. Can't get out of it without a new flash despite power off, resets, etc. Can't get back into recovery either at that point.

I do have the phone working with a non-rooted stock Sony 10.7.A.0.222. As mentioned, flashes fine. I just can't seem to get CM running (can't fastboot the boot image), nor can I get root on the stock sony (boot loop).

I've also tried the fastboot program on the current SDK as well as the one in Flashtools without any difference, still can't flash a boot.img from cm12.1.

I feel like I'm missing something fundamental, like maybe some aspect of running Windows 10 that is interfering (I have no older version currently). I'd suspect CM12.1 but it also is failing with the typical root technique for 5.1.1 stock (i.e. root older version first).

While I am not an active developer, this is not my first round of flashing or updating the phone, though it is my first round in a year or more, certainly since Windows 10.

I realize this is a lot like "nothing is working what could be wrong" and not a very specific question, but wondering if anyone has any suggestions as to whether there might be a common cause here.
[Sony Xperia ZL] Linwood.Ferguson:
I do have one more interesting piece of information that I do not understand.

I downloaded Emma and tried to use it to flash stock just to make sure the image I had was good for stock.

Emma says "this phone is locked". So thinking my last flash re-locked it, I went into flash tools and did this:

U:\AndroidSDK\platform-tools>fastboot oem unlock 0xkey-from-sony

...

OKAY [ 2.969s]

finished. total time: 2.969s

After doing so, Emma STILL says it is locked.

Flash tool however allows me to flash it.

Any clue why Emma would say "locked" when I just finished unlocking it?

In service, configuration it says "Yes" to unlocked, not "no/yes" or any other combination, just "yes".
[Sony Xperia ZL] ham5:
focus on getting the sdk tools to work, like fastboot. What do you mean it just does not flash( show console output of your fastboot flash boot boot.img), Is fastboot not recognized in the device manager, It is odd you can use it to 'oem unlock'... I had to change driver files when I switched from windows 7 to windows 10. if you can 'fastboot devices' and 'adb devices' you should be good to go as far as flashing, maybe you have bad images not made for the phone? I am no pro take my information with a grain of salt.
[Sony Xperia ZL] Linwood.Ferguson:
I will try again tomorrow (need the phone tonight and it takes a while to get stock back up and configured).

Concentrating on fastbook and on my more-working desktop (the tablet definitely has some issue, I think driver related).

I installed the newest Flashtools, and also installed the fastboot and s1 drivers from it (I think that's what they are called). I configured Windows to permit them unsigned and they installed without error.

When I try to do CM12.1, what I did was download their distribution zip, and unzip it and pull out the boot.img file. I then put the phone in fastboot mode, and it worked and was recognized (e.g. "fastboot getvar version" responds).

Going by the instructions for CM12.1, I then tried to do "fastboot flash boot c:\pathwhereitwas\boot.img"

This does a send of the file, which works, and then does a write and says "command not allowed". So it appears to transmit the file but can't commit it to flash. I cannot post the log as didn't save it but if you think relevant can post tomorrow.

As to the locked issue -- after trying this the first time, I thought "maybe the phone has been locked again". So I did the #*#*service*#*# and see it says "yes" for unlocked. But just to be safe, I dug out my 2 year old email from Sony and did another unlock. As to why I did it with the "oem unlock" that's how CM12.1 suggests (https://wiki.cyanogenmod.org/w/Install_CM_for_odin). The first time I typed it, it failed, the second time it said "OK". Tried the flash boot again, same "command not allowed error".

The phone goes into fastboot mode easily (blue light, plus response to things like getvar). It goes into flash mode fine also, and indeed, after I gave up (each of several times) I flashed stock back on the phone and it came up with 5.1.1 stock.

I wanted to run CM12.1 as I really don't like that stock has not patched stagefright, plus I hate not having root.

Any suggestions what I may be doing wrong, that fastboot commands sometimes work, but I can't flash the boot file?

Am I flashing the RIGHT boot file? Should I be flashing the CM12.1 recovery image they have on their download page instead? (But the instructions are pretty clear).

I should note that the phone does not appear to have a recovery on it -- booting after flashing stock, and toggling all the volume buttons in any combination is just ignored.
[Sony Xperia ZL] ham5:
I think your really digging way to deep into this...

what is the difference between fastboot and flash mode? Ive never heard of this flash mode....

I don't believe it sends a file at all, it is flashed/written to the boot partition right away.. or is supposed to - I would consider this your chief complaint... "command not allowed" when trying to fastboot flash a boot.img -- I get a lot of hits googling that.. driver problems/bootloader locked
[Sony Xperia ZL] Linwood.Ferguson:
I'd welcome a shorter, simpler path.

Perhaps it is purely a sony thing. If, with the phone powered off, you plug it in holding the volume up button you end up in fastboot mode; if you plug it in with the volume down you end up in flash mode.

Flashmode is used by Emma and by Flashtools. Fastboot is used by the Fastboot utility. I'm unclear what happens under the cover, but they are not interchangeable.

As I said, I do not know what happens under the covers, but in fastboot mode when you do the "flash boot" it first says it transmitted a file (shows bytes sent, etc) then it does a "write" command itself and it is that write command that fails.

And therein lies my issue trying to flash the boot image -- the write command fails, and I cannot figure out why.

Drivers: I've tried the latest flashtool, and installed the drivers from there. They do install (with signing verification off), and they do connect and see the phone. Some commands work, but this one does not. Could it be the drivers? Certainly, but I do not know what to try to fix them.

Emma: I hate to keep coming back to this, but I do not understand why Emma says my phone is locked, when it clearly appears not to be. I've both re-unlocked it, confirmed it is unlocked with the service menu. But that it thinks it is locked, and the "write" command failure, makes me wonder if there is an issue either in the phone or windows or drivers that makes it act that way. incidentally I've also tried all this with antivirus/firewalls off with no effect.

Locked: just to confirm, in the service menu it says "Root Status" and "unlockable" as "yes". Not "Yes/no". That means it is currently unlocked, correct?

To your first point, I may be over-complicating it. I would welcome some suggestion of other simpler steps. I've done the same google, and don't see real solutions other than "try better drivers", but most threads seem to point to the flashtools drivers, and I've tried those, as well as installing Emma which (presumably) either used those or loaded its own.
[Sony Xperia ZL] Linwood.Ferguson:
Incidentally if this is more appropriate to the Q&A forum, and a moderator is handy, I would appreciate it moving. I placed it here because this relates mostly to the Flashtools drivers and the process of using fastboot.
[Sony Xperia ZL] ham5:
I cant say for sure .. CM's dialer does not work with service menu... but you defiantly not worried about root... your looking for the bootloader to be unlocked, not unlockable..
[Sony Xperia ZL] Linwood.Ferguson:
I've never gotten to CM on this phone so that's moot. I'm doing the service menu from the stock phone. And so far as I can tell the bootloader is unlocked.

I went back to a much older version of Flashtools (0.9.11) that dates from about the time I got the phone, but those drivers do not seem to install on Windows 10 at all.

But I'm not clear whether it is a driver problem, since some fastboot commands work fine.
[Sony Xperia ZL] ham5:
Just read using emma with lollipop can screw your phone up... in fastboot mode can you 'fastboot getvar version' ?

here is the CM wiki - https://wiki.cyanogenmod.org/w/Install_CM_for_odin - good luck I don't think I can be of any help.
[Sony Xperia ZL] Linwood.Ferguson:
Yes, in fastboot mode I can do the getvar version. It says 0.5.

I had read the wiki; as mentioned that is why I was trying to flash boot.img.

As requested here is a fastboot session log:

U:\AndroidSDK\platform-tools>fastboot getvar version
version: 0.5
finished. total time: 0.002s

U:\AndroidSDK\platform-tools>fastboot flash boot boot.img
sending 'boot' (10668 KB)...
OKAY [ 0.340s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.340s

U:\AndroidSDK\platform-tools>fastboot flashing get_unlock_ability
...
^C
U:\AndroidSDK\platform-tools>fastboot devices -l
EPxxxxx47K fastboot

U:\AndroidSDK\platform-tools>fastboot devices
EPxxxxx47K fastboot

U:\AndroidSDK\platform-tools>fastboot flash boot boot.img
sending 'boot' (10668 KB)...
OKAY [ 0.340s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.354s

U:\AndroidSDK\platform-tools>fastboot flash boot boot.img
sending 'boot' (10668 KB)...
OKAY [ 0.340s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.353s

As you can see some commands work, some do not. Not sure the get_unlock_ability is even supposed to work as it looks like a late comer to fastboot and the phone is old.

Most articles I find posted about "command not allowed" do not seem to get as far as being able to use fastboot at all, but even if it is a driver issue, not sure what I can do about it, these are the latest drivers.
[Sony Xperia ZL] Linwood.Ferguson:
Ok, I've managed to get this to work. I can tell you what I did, but not why, but in case it helped someone else.

The bootloader showed unlocked, but I ran the flashtool option to unlock it again, then WITHOUT REBOOTING I did the fastboot option to flash the boot.img.

It appears that if you reboot (to stock) in between, it does something that at least makes it appear the bootloader is locked (the service menu shows it NOT locked still).

There's another thread here that implies you need to do it multiple times, but I think the issue is not a need to do it more than once, but a need to make sure that (at least a late version stock) does not get a chance to run, as it appears to do something.

I'm now happily on 12.1. Well, sort of happy, I finally noticed it says it doesn't support the 6506 (as opposed to the 6503) so I might not stay long, but at least I worked out what was wrong. Thanks to those who encouraged me to keep looking.
[Android Q&A, Help & Troubleshooting] avistein:
Recently i ported a rom for my mtk6592 device.Every other bug is fixed,however i couldn't fix the resolution of the camera.My device supports upto 13mp,whereas the camera app(tried every camera apps) shows 8mp even in 4:3 ratio.Any help will be appreciated.
[Nexus 5X Q&A, Help & Troubleshooting] SeriesOfTubes:
Any way you can get the default dialer app to display the numpad when opening up? It's relatively unhelpful when it just displays a bunch of white space.
[Nexus 5X Q&A, Help & Troubleshooting] k.s.deviate:
Well if you open the app, bring up the dial pad and close it but leave it in memory it should open back up the way you left it.
[Nexus 5X Q&A, Help & Troubleshooting] jbdan:
So you don't have "favorites"?? I thought everyone had those....

I'd put the people I call/text/email the most in favorites that way they show up. If you don't want to do this then open the dialer> open up keypad> then hit home button. Re-open dialer and keypad pops up on mine
[Nexus 5X Q&A, Help & Troubleshooting] SeriesOfTubes:
It does open favorites by default. Favorites are helpful, but on ROMs like HTC Sense, the number pad opens when you launch the dialer and you can either dial a number right away or use the letters on the number pad to type the first few letters of a contact name to search for someone and then hit call.

I guess these are some of the finesse things that change among ROMs and I could download a different dialer app in the play store.

First nexus phone.
[Nexus 5 Q&A, Help & Troubleshooting] svno1:
I somehow decrypt my phone. Neither the Android system nor TWRP ask me for my pattern when startup. But the status in Encrypt Phone is encrypted, and so is ro.crypto.state. I am on Android 6.0.1 and using SuperSU 2.62 and Xposed v78. I have made backups before this stuff happened. Any suggestions?
[Nexus 5 Q&A, Help & Troubleshooting] davidshen84:
I have the same problem. Mines occur after I used the "Clean Master".

Have you figured out how to re-encrypt the phone again?

Thanks~
[Nexus 5 Q&A, Help & Troubleshooting] svno1:
sorry for the delay.

after some google I find out that this is a state of "encryption without password".

just disable and re-enable or change your lock screen should fix this issue.
[Nexus 5 Q&A, Help & Troubleshooting] svno1:
and where I find out this stuff: [nourl]https://source.android.com/security/encryption/#flows[/nourl]

……and I have no permission post outside links.
[Verizon Samsung Galaxy S 4] grantd:
Hey Everyone,

Has anyone else tried the CM13 Nightlies and Bluetooth? I first upgraded to CM13 from CM12.1 (only wiped cache and dalvik) and Bluetooth share was constantly crashing, this was the 2015-12-09 build. Turned off Bluetooth and rebooted to get rid of the prompts, figured would try another nightly in a few days to see if it cleared up. Here is my progression.

2015-12-09 - Inital CM13 load, Bluetooth share has stopped working prompts

2015-12-14 - Upgraded to this nightly, no more crashes but Bluetooth shows no devices

2015-12-15 - No change

- Restored an older CM12.1 nandroid backup, Bluetooth was working, so restored back

- tried full wipe and reload of nightly, no change, restored back to have my data

2015-12-17 - Updated again, no change

Realized today that even though Bluetooth HCI snoop log is turned off in development options, it seems to be generating the log anyways. Would this help anyone with troubleshooting?

Thanks in advance,

Grant
[Verizon Samsung Galaxy S 4] grantd:
Saving this slot for updates.

Also, if anyone else is on CM13 and don't have this issue, if you could share your upgrade experience and I will try to replicate it to test. Thanks

UPDATE:

So I have been loading each nightly since my opening post and have not had any luck with Bluetooth working, now with the 2015-12-21 Nightly, Bluetooth WORKS!!!!

from the changelog there is the following entry that may have been the issue:

device/samsung/jf-common

* b651ba7 Revert "jf: set BOARD_HAVE_SAMSUNG_BLUETOOTH"​

or could be (even though I am not on OJ2)

kernel/samsung/jf

* 67e35c4 bluetooth: update from OJ2​
[General Monetization] giftwallet:
Good evening every one of you,i'am new here,i am so happy to be with in you in a successuful forum like this one

So i want to present you a new application for mobile,that you may know,but this time with a new trick that allows you to collect unlimited coins and convert them to real money.i talk about: Gift Wallet

So Gift wallet is one of the newest and best Android application of the year 2015,that allows you to win gift cards by earning coins from downloading apps and taking surveys.

in this videos you can win unlimited coins thank's to our new trick.

For more informations,watch this video on youtube:Earn free cash and gift cards from your android phone,Gift Wallet hack
[Galaxy S3 Neo Themes and Apps] ashok225123:
HI Friends found the lenovo camera updted version with annoying pop-up removed and

im not created this this is a share so all credits go to gerardroid

downloalink

http://www.mediafire.com/download/y0bkxa36bt7zkce/SC3.6.7-removed-perm-popup-qrscanner.apk

futures:

it works like stock camera

panorama

hdr

low light

pip

burst

speechnight pro beauty

smile marco

timer etc

credits:

gerardroid
[Galaxy S3 Neo Themes and Apps] ashok225123:
reserved
[Galaxy S3 Neo Themes and Apps] Antox97:
Can you re-upload files?
[Galaxy S3 Neo Themes and Apps] ziad311:
I think it is impossible to bring manual focus to our device
[Galaxy S3 Neo Themes and Apps] cepsisx:
Link error
[Galaxy S3 Neo Themes and Apps] ashok225123:
sorry

i will re upload the link

thank you
[Galaxy S3 Neo Themes and Apps] ashok225123:
link updated
[Galaxy S3 Neo Themes and Apps] nalas:
On I9301I with RR 5.5.8 (Lollipop 5.1.1.) and Kernel Renix69 CM13 v2.0 for RR 5.5.8 - works good :)

Thx for the app.
[Galaxy S3 Neo Themes and Apps] techie_vintage:
Thanks!

It works good on I9300I too!
[Galaxy S3 Neo Themes and Apps] I'mTheMr:
Warning , don't install this app it will make your cpu 100% and drains your battery
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] L_B_J_1:
my wife just upgraded from the S4 because it was having some serious problems. and now all of her data on her SD card can't be recovered. its been put in mulitiple card readers and different devices to try to fix this problem. none of them can find the device or mount it weather its a different phone or computer. she has some stuff she really needs to recover on it. any help would be very appreciated.
[Nexus 9 Android Development] dadymon53:
Awesome! Will flash soon. Since it's cm based I assume this supports themes?
[Nexus 9 Android Development] Floyd_Flivercod:
Yes
[Nexus 9 Android Development] whowatchlist:
You should probably change the op. It looks like it is for opo but it's for the n9
[Nexus 9 Android Development] dadymon53:
Flashed with no problems, took awhile, just be patient. I have this loaded on my Flo (lollipop), loved it. Glad too see it come to the Flounder! As always love the boot animation! I'll have downloaded my old themes, miss the them engine, glad to get a break from layers! [emoji14]
[Nexus 9 Android Development] dadymon53:
Where might I find supersu?

Privacy Guard?
[Nexus 9 Android Development] Floyd_Flivercod:
Set up developer access then go to settings - developer options - Root access (set options)

No need to flash any supersu files
[Nexus 9 Android Development] Floyd_Flivercod:
I had the OP wrong. I compile this Unofficial for FLO & BACON also. Thanks for the catch!
[Nexus 9 Android Development] whowatchlist:
Loving the rom so far! Hope this gets official support from AICP
[Nexus 9 Android Development] Floyd_Flivercod:
It will be supported. Nightlies will start any day now!
[Nexus 9 Android Development] Hashbang173:
Yes, I have flounder on the list of mm nightlies. I'll create an official thread when they come out.
[Nexus 9 Android Development] Floyd_Flivercod:
New FLOUNDER MM build loaded 12/23 - https://www.androidfilehost.com/?fid=24340319927534368
[Nexus 9 Android Development] liang512:
Will this ROM encrypt the data partition, since it's from CM? Thanks!

Sent using XDA One
[Nexus 9 Android Development] Hashbang173:
No

https://github.com/AICP/device_htc_flounder/commit/ff746bc3e2b82e7e48f43034a6b2b98cd1510c80
[Nexus 9 Android Development] Marky__Mark:
How stable is this build? I'm on the latest AICP and I know I need to flash the vendor in order for this to work. Can I take a backup of my AICP 10.0 including the vendor and restore back to it if I need to? Don't see why that wouldn't work.
[Nexus 9 Android Development] Floyd_Flivercod:
Yes, just do a full backup first. The first build didn't give me any issues, but the latest is too early to tell.
[Nexus 9 Android Development] cerj:
Thank you guys for bringing us another great AICP rom.
[Nexus 9 Android Development] CZ Eddie:
[MENTION=5115949]Floyd_Flivercod[/MENTION] could you please add flounder_LTE to your builds?

It's officially supported by Cyanogen if that helps:

http://www.cmxlog.com/13/flounder_lte/

The USA and International LTE Nexus 9 are $359 @ HTC right now and the LTE works on Verizon and all other major US carriers now that Marshmallow is out.

http://store.htc.com/store?Action=C...104_G - US - NAM - HTC - PS - Tablet - B&Ps=1

I tend to donate and AICP is usually my preferred ROM. :)
[Nexus 9 Android Development] Floyd_Flivercod:
Flounder LTE should be supported by AICP when the nightlies start officially. I don't include it because I don't own the device. This is an "Unofficial" build I compile and share with the community until the official nightly builds start.
[Nexus 9 Android Development] Hashbang173:
First official nightly is here

official thread OP updated