yashsingh1/xdaforums huggingface dataset:
[Moto X Q&A] scryan:
Appreciate the info given... I don't want to downgrade, I am not trying to downgrade, I understand why its a bad idea, ect...

My view point was more questioning the insistence that it being technically possible to downgrade creates a security flaw on a machine that is kept up to date by a responsible individual. Unless we are trying to speak more abstractly about that fact that given someone the opportunity to make a mistake makes it more likely for one to occur, I don't think that security threat exists until you actually use that ability to downgrade to something with a flaw.

I guess then it comes down to personal viewpoint of do I want my phone to brick it self to protect me from myself and like sam said, you choose to go elsewhere... But then that is somewhat what I am trying to figure out. Even though its not something I would probably ever have to deal with, I don't like the idea... But "bricking" can be such a vague term with manufacturer specific recovery tools and "different levels of bricking".

Just trying to understand how what and when actually happens. I probably need to read some more of the recovery threads, and I have been looking through old threads here while considering VZ dev moto X and waiting for the x + 1 announcement, but I figured I would jump on the thread while it was here.

I understand keeping it simple because its generally a bad idea all around, and its just best not to confuse things... but its been hard to find deeper discussion or information then the general warnings. A bit of a better picture from this thread though.

By "Our recovery devs" do you mean the ones doing the moto specific stuff? Do you know if this Is typical of the custom recoveries for other devices?
[Moto X Q&A] aviwdoowks:
[MENTION=5493962]scryan[/MENTION]

I know far less then other posters, but yes android recoveries are all very similar in that regard.
[Moto X Q&A] iKrYpToNiTe:
The thing is you keep looking at it from a PC point of view, where you basically have full control over the software and hardware. Phones have much tighter restrictions on them from carriers, fcc, etc they're not personal computers. So the reason they make it where you can't downgrade the bootloader is because that's what controls the restriction on downgrading any other partition on the device.

So with the Moto X's 4.4.4 update they probably blew an efuse, so users with a locked device can't downgrade. This is done because with locked devices they can only flash signed kernels, so by blowing the efuse they can't downgrade to the vulnerable 4.4.2 and below kernel even though it is signed correctly. This is because lets say a malicious app was able to get on a device that had the ability to downgrade say back to 4.2.2. That app could flash the older vulnerable signed kernel to the recovery partition, to disable write protection gain more control over the phone etc, without the users knowledge. Now that is a stretch and probably will never happen but that doesn't mean the threat isn't there, and hackers are very creative at deploying malicious attacks. So by updating the bootloader and blowing an efuse the older vulnerable kernels can't be flashed. Now this is all negated if you're unlocked of course, but if you don't want to ever worry about this issue don't update your bootloader. This is not recommended but I've mentioned it several times on this forum I haven't updated my X's bootloader since I bought it, it's still running the factory 4.2.2 bootloader, running 4.4.4 with no problem.

The other thing you're missing is we're technically not supposed to have the ability to restore our phones, except for the developer edition of course. The fastboot restore files are leaked not released to the public, they are designed for use when phones are returned to be refurbished. So they don't want the phones that are being refurbished to be flashed back to an older version, they want it to be refurbished and the latest software version flashed to it.
[Moto X Q&A] scryan:
A bit selfish, and perhaps lazy of me but I am only really here talking about the developer version, I just haven't bothered to write the full "verizon developer edition " every time (most of this is research for next phone, which will be developer handset)... To me, obviously a locked phone is going to have weird restrictions and hacked together paths to getting things done, your not supposed to have admin rights...(yeah, maybe I do look at it too much as a computer. Mostly because I am annoyed the differences seem intentionally imposed). But when I pay outright for a device so that I can own it and have full administrative control... anyways, thats a different more philosophical discussion. The point is I have been talking about an unlocked device using third party software where possible.

Either way, appreciate the reply. I have a better understanding of the issue... Though coming from an S4 it still seems weird that MDK*/developer phones don't seem to have the same issues/warnings. It would seem however that the difference may be that MDK/dev owners only use kernels/roms prepared for their devices and do not update the bootloader. I suppose if more people in the Moto X community were worried about maintaining the ability to downgrade an unlocked device it would be technically possible to upgrade in a way that could be easily reversed, similar to the S4.

(*MDK was the first VZ S4 firmware, and the only one that has a released exploit to allow for a full custom recover. Later locked firmwares must rely on safestrap)
[Moto X Q&A] :
You need to realize though... As far as the Moto X goes, they made it no different what so ever than any other unlockable moto X. The only benefit it has over the other devices that can be unlocked, is you keep your warranty. But all the same restrictions apply.

I agree, doesn't make the name Developer Edition seem to mean much.

The X is by far no Nexus.... Or even as friendly to flash with than a lot of other devices. But it is what it is. And I expect future Motorola devices will be no different.

Not a typical XDA members dream device, that's for sure.
[Moto X Q&A] scryan:
The VZ S4 Dev edition was a normal S4 with an unlocked BL(which I can't even find for sale new anymore?), didn't even get updates and if you used a regular OTA it would lock the phone irreversibly... So Moto X dev seems ahead in those reguards :D

Nexus I think would be a no brainer, but with all my complaints I haven't been able to find a carrier that can take me away from Verizon and they won't let me have one.
[Moto X Q&A] :
Yeah, Verizon doesn't like nexus or development in general it seems.

I'm not knocking the X though... It's just not a tinkerers ideal device. Little development support, no downgrading... Etc.

It's a great device anyway, even unrooted. But without all the moto features... Not a lot of interest in aosp /cm roms. Stock based roms or just gravity box are nice though.
[Moto X Q&A] iKrYpToNiTe:
Have you actually read the previous posts that other members have posted? The developer edition or in full as you say the "verizon developer edition" has the exact same software on it as a retail Verizon XT1060 that can be bought in the store has on them. There is no difference what so ever, all the extra money people spend on the dev edition is literally to put their phone's serial/imei number on the whitelist of Moto's bootloader unlock code generator! Every single Moto X is unlockable, but Moto has all of the retail Verizon and AT&T models on a blacklist, so that their website will not generate the bootloader unlock code for them. I have a retail Verizon XT1060, but thanks to the china middle man my X is now unlocked. So my previous post still stands, when they release software their main target group is locked users not unlocked users unfortunately.

Since you are looking at it from a computer point of view, then let me explain it this way. A computers bios is similar to a bootloader on a phone in a sense, and for the most part bios's are released only by the manufacturer and normally can't be downgraded once upgraded. So yes I understand your point that paying for a dev edition should give you full administrative rights but unfortunately it's a phone not a PC.

The OP asked why can't they downgrade, that normally means they're talking about a locked device. Now if the OP is unlocked then I don't see the point of this thread, because they can downgrade everything except the bootloader just fine. Once the bootloader is unlocked they can flash any kernel, baseband, or ROM they want they just can't downgrade the bootloader which doesn't matter when you're unlocked anyway. As sam posted in post #8 it's the secured bootloader don't confuse secure with locked or unlocked. If you want a more technical explanation of why you can't downgrade. Look up efuses and the part they play in bootloaders, cpus, xbox 360s, etc when it comes to downgrading. Also look over this pdf http://theroot.ninja/PAE.pdf it goes over android security and the boot sequence of most Android devices.
[Moto X Q&A] scryan:
YUP.

Wait... Did YOU actually read the previous posts that other members posted? Because the OP ACTUALLY asked:

And TWO POSTS LATER EXPLICITLY ASKED

Nothing about boot loaders even. Simply about installing 4.4.2 after upgrading to 4.4.3, EVEN ON A DEV EDITION?

He also has the signature:

The OP never even asked about bootloaders, just "installing 4.4.2" and it takes three pages of me pulling teeth for one of you to finally say :

Sorry me or the OP are not as smart as you. I'll leave now.
[Moto X Q&A] KidJoe:
PMJI,

Many who have never had Moto android phones in the past often confuse "unlocking the boot loader" with the "ability to do anything I want to the phone."

On HTC android phones when you obtain S-OFF while unlocking the boot loader you can in fact downgrade. You can flash all parts. But that is due to S-OFF, or turning security checks off, not unlocking the boot loader.

mDK on the S4 was mentioned. There a vulnerability was exploited (Loki I think) to allow you to reach a unlocked boot loader state. What other features did that exploit allow? Maybe it gave an s-off type state? I do know that once your phone was upgraded past MDK, you couldn't downgrade to use the exploit.

Point is, on the Moto X, developer edition, or other unlocked boot loader variant, the security features on the phone (which stay in place even when unlocking the boot loader) prevent downgrading GPT.BIN and MOTOBOOT.IMG when they change. ( except for the rare case of 4.4 to 4.2.2 w/camera update, for whatever reason, downgrading wasn't an issue)

We have seen soft bricks and/or features not work, when using mfastboot to downgrade only parts (skipping gpt.bin and MOTOBOOT.img), and we've seen many bricks when trying to upgrade via OTA when there are mismatched versions on a phone (gpt from one rom, with system.img of another, etc).

We've seen issues upgrading when using a full SBF/FXZ if mismatched versions are on the phone.... I.e. The need to use mfastboot to flash gpt and MOTOBOOT, reboot to bootloader followed by immediately flashing the entire rom, starting with gpt and MOTOBOOT .

The security checks on all variants of the Moto X get in the way and cause issues.
[Moto X Q&A] AGISCI:
The reason that the pre cam to pre cam did not fail was because the partition table and bootloader did not change between the two versions so, there was no problems. However they did change post cam.
[Moto X Q&A] KidJoe:
Thanks, I understand that, but other contents in motoboot.img did change... so I didn't want to get into specifics.
[Android Q&A, Help & Troubleshooting] samokat:
My b1-720 bricked after restore, somebody who have same tablet can upload Update.zip ?
[8125, K-JAM, P4300, MDA Vario General] s4vva:
I am able to switch between the standard sip's (keyboard, transcriber, block recogniser, phone pad etc.) however i have tried to instal a Greek keyboard (both from Lingvosoft and Interkey) if i try and select this keyboard to enter text the input method just switches back to the standard keyboard. (it does not display the greek keyboard at all).

I am using molski 2.26.10.2 if that helps.
[8125, K-JAM, P4300, MDA Vario General] richardfree:
co-ask

installed a Chinese input method. Sometimes cannot switch to that sip; sometimes, if already switched, cannot switch back to others.
[Nexus 5 Q&A, Help & Troubleshooting] ali262883:
I already own a nexus 5, I'm enjoying it, but sometimes I feel that the camera and display are very poor, I want a good camera and little bit lagg will be tolerable.. But i want a great camera.. A good display.. Please guide me
[Nexus 5 Q&A, Help & Troubleshooting] kevtrysmoddin:
Buy a galaxy camera and if your nexus 5 is running a custom kernel tune your display
[Nexus 5 Q&A, Help & Troubleshooting] simms22:
i have an s4 as well as a n5. stay far away from the s4! hell, ill sell it to you cheap, its the verizon version.
[Nexus 5 Q&A, Help & Troubleshooting] ali262883:
I know that.. But I'm a camera addict.. I'm mostly out with my friends, hangouts, night outs, beaches etc.. I need a good camera.. I take Selfies with rear camera because front camera sucks
[Nexus 5 Q&A, Help & Troubleshooting] simms22:
i got it just to use the camera actually, but samsungs software so pisses me off sometimes that i ended up using my n4 as a spare camera instead, and my s4 has been just laying around the last half year.

---------- Post added at 11:36 AM ---------- Previous post was at 11:35 AM ----------

and as i said, if you really want it, ill sell it to you, cheap. but its a verizon version.
[Nexus 5 Q&A, Help & Troubleshooting] shhbz:
best is to wait for the next nexus or else get a sony device they are the best in camera
[Nexus 5 Q&A, Help & Troubleshooting] kilowatt95:
I second shhbz here - wait for the next Nexus or get a Sony.

I don't find that Nexus 5 camera that bad though - sure, its not the best in the world, but it takes pretty good shots for what it is.

You could also consider a Samsung Galaxy K Zoom. The LG G3 is not a bad cameraphone either,
[Nexus 5 Q&A, Help & Troubleshooting] MrObvious:
The camera is a lot better IMO with HDR. You aren't buying a $600 phone so they cut the quality a bit but honestly the camera is the only thing that feels inferior on this phone and even then it can be tweaked a bit and runs great.

However the screen is good. I find Samsung washes out their screens with overly bright colors. The only complaint I have is the contrast in full sunlight but the full brightness makes up for that OK.
[Nexus 5 Q&A, Help & Troubleshooting] ali262883:
So i shouldn't?
[Nexus 5 Q&A, Help & Troubleshooting] ali262883:
G3 and xperia z1 out of budget.. Nexus is approximately 150$ expensive in India than the original price.. So not worth waiting for next nexus
[Nexus 5 Q&A, Help & Troubleshooting] dec1153:
How about a oppo n1 with the 360° 13mp camera for great selfies?
[Nexus 5 Q&A, Help & Troubleshooting] ali262883:
Probably no.. Its overpriced, expensive than s5 also in India..
[Nexus 5 Q&A, Help & Troubleshooting] MrObvious:
Shoot get the Nexus 5. You won't be disappointed.
[Nexus 5 Q&A, Help & Troubleshooting] doctor_droid:
Nothing to be confused about

If u want better camera and battery go for s4

If u want fast updates and pure android skin go for n5.

Depends entirely upon ur priorities
[Nexus 5 Q&A, Help & Troubleshooting] adichandra:
I was there. Got n5. Hate about camera and battery life. Switched to s4 and flashed GPE rom. Camera is nice and battery life is infinity with the battery kit, but really missed the speed of the nexus 5. Now i switched back to n5, with elemental x, undervolted, underclocked to 1.7ghz. Battery life is improved significantly and camera is much better now on 4.4.4. Camera on my first nexus 5 with older rom gave me a headache, focusing and taking a picture was slow, but not anymore.
[Nexus 5 Q&A, Help & Troubleshooting] ali262883:
I finally decided to stick with nexus 5 after doing many camera comparisons with the s4, I think nexus 5 has a better and more reliable camera.. S4 is totally unusable indoors even with perfect lighting.. Outdoors there are details, but colors are crap.. Saturated yet extremely unsharp display.. Nexus 5's crisp, sharp and almost near accurate lcd display beats the crap out of s4's display.. What's better with s4, just a little longer battery and better speakers..
[Nexus 5 Q&A, Help & Troubleshooting] ali262883:
In a mall while testing cameras,in first picture, s4 has a warmer photo, unrealistic, crap details, blurry, on the other hand nexus 5, better color accuracy, slightly better details, a bit steady (Now i know what's OIS is capable of).. Overall nexus 5 takes much better photos..
[Nexus 5 Q&A, Help & Troubleshooting] ali262883:
I have just one problem with my nexus 5, the warm display [emoji20].. It sometimes feels very bad looking at it..
[Nexus 5 Q&A, Help & Troubleshooting] Shiestie:
Nexus 5s are known to have a bit of a warm display, but compared to the s4 it still better, the s4 just brightens the colors to make the display look crisper
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
It can be tweaked with kernels and colour profiles.

Actually Samsung used SAMOLED panels not LCD. That's why it looks oversaturated. Completely different screen technology
[Nexus 5 Q&A, Help & Troubleshooting] ali262883:
Yes i know.. I always wanted an amoled screen.. But after using LCD screen i can't even think of using the amoled screen
[Nexus 5 Q&A, Help & Troubleshooting] bblzd:
The N5's pictures look better and the battery last longer, despite being smaller and powering a faster SoC. In other words, the S4 has nothing going for it and has been outclassed for almost a year now.
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
I prefer amoled personally. Not the colour reproduction but the fact that only pixels being used are turned on. I miss not being able to use my phone as a night clock.

But anyway, I wasn't suggesting you get one.
[Nexus 5 Q&A, Help & Troubleshooting] ali262883:
Thank you for your suggestions guys [emoji4]
[Nexus 5 Q&A, Help & Troubleshooting] :
Buy a 99 dollar Kodak and get far greater pics than any phone will ever give you.

Relying on a phone for things you want great pics of, is a severe gamble. On any phone. ?
[Nexus 5 Q&A, Help & Troubleshooting] Venomous Viper 119:
Flash the elemental x kernel & select slightly cooler colours during the installation. You'll definitely start loving your display, I'm sure.
[Nexus 5 Q&A, Help & Troubleshooting] ali262883:
I have similar feature in Linaro kernel.. It allows u to choose between 3 color profiles while flashing [emoji2]
[LG Optimus G Pro] jhaye93:
So my mobile hotspot isnt working, I installed Sqlite Editor but im not seeing 'tether_entitlement_check_state';

I NEED HELP PLEASE
[LG Optimus G Pro] Dannybones:
I had to modify this from instrux in this thread: http://xdaforums.com/showthread.php?t=2283615

I suppose since my phone is unlocked, those instrux didn't work right for me.

I am going to make these as dummy-proof as possible, since I is a dummy:

This worked for my LG Optimus Pro E980.

1) Phone must be rooted (easy to do, other posts cover that)

2) Pay $3 and download SQLite editor by Speed Software to your phone

3) Open SQLite Editor on your phone

4) Click on "FILES" tab on top

5) Click on "data"

6) Click on "data" (from this point on, you may have to do some scrolling to find the right entry)

7) Click on "com.android.providers.settings"

8) Click on "databases"

9) Click on "settings.db"

10) Click on "system"

11) Click on "tether_entitlement_check_state" so it highlights grey (on mine, it's _id 24343, and so was near the bottom of the list. Yours may differ)

12) Click the pencil icon on top to start editing

13) Change the value to 0 (Mine was 5)

14) Click "Save"

15) Reboot your phone

16) Turn on Wifi Hotspot, and start Hotspottin'!

Let me know if this worked for you, and if your phone is unlocked.
[G2 Q&A, Help & Troubleshooting] InnocentRaver:
Hello I need help about an Android app called "AutoRec". I have rooted my LG G2 D802 4.4.2 with IOroot but I did not get SU app so I downloaded one from google play called "SuperSU" and I have checked and it says my device is rooted properly. I wanted to do a EFS Backup just in case so I started searching how to flash a custom recovery image. Luckily I found AutoRec and done it as instructed. But when I enter recovery mode from my phone it shows the standard stock LG recovery instead of TWRP 2.7. But after using the app again and tapping go to recovery from the AutoRec app after finishing I could use TWRP but once rebooted, it does not enter TWRP again when I try to enter to recovery mod, instead it shows the stock recovery. Can any of you help me please? Thank you.
[G2 Q&A, Help & Troubleshooting] bender_007:
Solved :)

reboot
[Xperia Z1 Q&A, Help & Troubleshooting] abo hani:
Hey guys, i have installed the latest 108 for my XZ1 C6903.

I have got some problems in the update like Heating and battery draining.

But its way better than 4.3!

Battery on screen time is 5 hours / Facebook - Facebook Messenger / CHROME.

Battery small usage / same apps - mostly stand by mode. 7 hours

I have bought it 3 days ago and i hate these problems -_____-

P.S : Rooted, CWM, LB.

I don't want to install ROMs.

I just want to solve this.

Battery temperature is 38-39!!
[Xperia Z1 Q&A, Help & Troubleshooting] FahmyAbou:
Well the 4.4.4 update should solve these problems, which is the case for most Z1 owners. Try to reset the phone and see what happens. And if the tem rises to 39 when using the phone then it is not an issue, as the z1 has a bad thermal condition.
[Android Q&A, Help & Troubleshooting] simes6600:
just noticed today a file, .tcookieid (33 bytes in length, dated yesterday, opened file, about 30 characters of Hex), has appeared on my M8 in every folder on my SD card, and is also on the root dir. anyone know what it is?
[Android Q&A, Help & Troubleshooting] whoamigriffiths:
Have you recently installed ifonts app?

I saw that I also had this file throughout my sdcard.

The only thing I can think of is that it has something to do with how ifonts deals with replacing and/or backing up your current Fonts.

I found your post after a google search about it. But there is not much info about it (that I can find)

It may be that everyone knows what these .tcookied files are and me and you are a pair of idiots lol.

But I figured I'd post just so you wouldn't feel on your own! :P

I'm gonna keep searching for answers and if I find anything I'll let you know.

All the best rich
[Android Q&A, Help & Troubleshooting] simes6600:
there could have been an update to ifonts recently, in the past few days, cant really remember as i have so much stuff getting updated daily. but ifonts makes sense as to what is making this small file. its harmless anyway, just wondered why it was appearing. surprised no one else has picked up on it here on XDA (apart from ourselves)...
[Android Q&A, Help & Troubleshooting] thesimpleboy:
Hello there,

Even i stumbled upon this post from the Google keyword query, my SD card was displaying as being damaged, so i was closely examining the contents of my SD card and i found this newly created file.

It was only in the root path of the SD card, nowhere else.

Even i think that this file might have belonged to iFonts, i have uninstalled the app and removed the file after iFont messed up my factory font restoration pretty badly.
[Android Q&A, Help & Troubleshooting] 4Freedom:
same here

On every folder on my sdcard appeared a file called .tcookieid with a strange code inside:eek:

I just installed some new application this afternoon, i am 100% sure that i hadnt it some hours ago.

If someone know what is the cause or what is this please let me know.

I cant find nothing on google
[Android Q&A, Help & Troubleshooting] jeckyhauhnar:
Just found it myself..delete some of it..i hope it doesnt affect my files.....curious?????:confused::confused:

Sent from my LG-D802
[Android Q&A, Help & Troubleshooting] krashd:
Well iFont has never even been near my device, I hadn't even heard of it until this thread. So either something else creates it too or it's nothing to do with iFont.

These little buggers are all over my SD card and internal storage.