yashsingh1/xdaforums huggingface dataset:
[X 2014 Q&A, Help & Troubleshooting] likurik:
"Even though these phones are not carrier branded they are still "tuned" for regions used. The DE phone is designed for Germany and if you live in Germany this would be your best bet.

Remember the carrier networks are still regulated by individual country - and the phones have to confirm to the gov't and carrier requirements. Things like network switching and fast dormancy requirements are different and could impact battery life.

I am sure there are differences in firmware - they would all be EU if not - no reason to name files different if the same. As for the phone differences - we don't have that information here. You should be able to find the regulatory body for each country and look up SAR values.

I would also add that there could be differences in software due to patent issues - and maybe the software has different components to avoid patent disputes.

As I mentioned at the beginning - you should buy the phone that is official for your region. If you save a few $$$ buying a different version then you may face interoperability issues. Yes GSM should work everywhere - but as someone that travels, I know that when I go to another network, all features may not work they way they do on my home network. "
[X 2014 Q&A, Help & Troubleshooting] AGISCI:
Yes you can flash eu firmware. But considering you are in spain, I would recommend flashing the spain firmware retES instead:

http://www.filefactory.com/file/3kqjy5gd5rxp/VICTARA_RETES_XT1092_5.1_LPE23.32-25.1_cid7_CFC.xml.zip
[X 2014 Q&A, Help & Troubleshooting] surrealjam:
I'm assuming if you did convert the phone, even from retDE to retEU, you would not be able to receive the "official" OTAs via the standard update process? Or is this not the case?
[X 2014 Q&A, Help & Troubleshooting] AGISCI:
That is incorrect. He will be able to receive the official updates. However he will receive the retES updates instead of the retDE updates.
[Xiaomi Mi 4i] adrianyujs:
Hi guy, is there any ROM Cleaner available for Mi 4i? Somekind cleaning bloatware / lousy apps / unused apps...

Normally its flash-able via CMW. Someone please guide me.

Thx.
[Xiaomi Mi 4i] iamsahilkdm:
Well this time we have to be Cleaners...

Disable unwanted apps in TB

Or Just uninstall with System app remover

There's a thread on Miui forums bout that i followed.
[Xiaomi Mi 4i] adrianyujs:
Where is the link?
[Huawei Ascend P7] zaabolla:
Hi, i find this update but not for L10

it could help some one

here link: http://cn.club.vmall.com/thread-6033107-1-1.html
[Nexus 6P Q&A, Help & Troubleshooting] abraxo:
I'm seriously considering the 6P but it seems like all the features touted on the device are generally derived from Marshmallow. Sure it stacks rather well against other flagships right now but all the devices its going up against are running lollipop. When they get the Marshmallow features, will the 6P still match up or will they blow it out of the water?
[Nexus 6P Q&A, Help & Troubleshooting] PieOfJustice:
Depends. Remember that most phones won't be updated. The ones that will be uodated won't be for at least six months depending on the manufacturer. Some Android phones should be getting M in the next few weeks, but those are special cases and usually only for one sub-model at first. Truly the answer you seek has too many variables to consider.

Remember that Nexus devices are also meant as a pure android experience. Other manufacturers mod android so much it's not even the same experience.
[Nexus 6P Q&A, Help & Troubleshooting] abraxo:
I don't have any issues with android skins (touchwiz at least), but I do have some kind of complex with 'futureproofing' and the like, since whatever phone I'm getting will be my phone for a while.

Ultimately, the decision still hasn't been made for me because I know the dev community for whatever product I might get outside the 6P on ATT will be dead since they love locking their bootloaders
[Nexus 6P Q&A, Help & Troubleshooting] mosincredible:
Not exactly a feature but I consider having a different phone from most people a bonus. The Nexus will be a conversational piece around anyone who's remotely curious of tech.
[Nexus 6P Q&A, Help & Troubleshooting] PieOfJustice:
The one thing I've learned is that you can't future proof a phone. Manufacturers sole purpose is to make sure the phones are not future proof so they can sell you the update next year.
[Nexus 6P Q&A, Help & Troubleshooting] Smallsmx3:
It's a nexus. It will have Google support for 2 years and dev support past that. I'm pretty sure someone got kit kat running on the nexus 1. Pure android with always run smoothly even on an older nexus. So when the galaxy s7 rolls out next year your 6p might not get the best bench score it will still give better real world performance
[LG Leon Questions & Answers] pedrovay2003:
I've successfully rooted my T-Mobile LG Leon, and I've successfully installed TWRP, but for the life of me, I can't get the phone to boot into recovery. I can RE-boot into recovery from TWRP manager, but I can't actually boot into it from a fully powered-down state. I've tried every combination of the power and volume buttons I can think of, and nothing ever works. Download Mode works, the factory restore menu works, but I CANNOT get into recovery. Is there a very specific set of instructions anywhere that I can follow?

EDIT: Okay, I finally figured it out: You need to actually select to do a factory reset, and it throws you into the recovery menu.
[LG Leon Questions & Answers] EmdoPL:
Yeah, it was because the stock recovery doesn't exist as a menu, when you're running stock and enter the adb command "adb reboot recovery" it will reboot to the "factory reset mode" and the actual file of this mode is stored on partition named "recovery". Choosing the factory reset option boots the custom recovery because it replaces the said " factory reset mode" and that's the trick.
[LG Leon Questions & Answers] ninjasinabag:
You can access recovery from the powered off state by holding volume down and power on until you see the lg sign. Without letting go of volume down, depress on the power button before clicking it back in and holding both buttons in until you see twrp pop up.
[LG Leon Questions & Answers] TerraHedge:
If you reboot to recovery now, it''ll probally say secure booting error. Simply go to the Developer options and enable OEM Unlock and that'll make you boot to it
[LG Leon Questions & Answers] kruc Ire:
You boot in the download mode by holding the vol up 10 seconds and during this 10 seconds you insert the usb. The LG Leon brand screen will come on a minute then it will go into download mode. It says not to unplug until firmware is done updating. So I guess you should have your custom recovery or whatever before you do this. I have only got this far, and thusly it sits. All Dressd up with no where to go...haha
[LG Leon Questions & Answers] kruc Ire:
can't find "enable OEM" at all in developer options. have phone hooked computer, and on, it's sending and receiving. No OEM. Isn't there.

See, I'm trying to root this without using KingUser. Since I found that it was pretty easy to do from the very beginning with Samsung, and I just don't see any way to do it here. I can't get ADB Devices command to see the phone.
[LG Leon Questions & Answers] duffycop:
I think I have the same issue, but I rooted my phone using kingroot, I haven't tested the adb commands, I just want to use twrp but no luck, it says Secure booting error and I can't find OEM Unlock option in Developer Menu.
[LG Leon Questions & Answers] kruc Ire:
I got a good way to get it rooted with SuperSU. Ran a command window script I found out there. It worked and now I have SuperSU root. I also figured out how to get into recovery. It looks as though my phone is not the standard LEON that people are talking about here. It's got a few designations, and the T Mobile site advertises a Leon that seems very similar and is called by the name most are using..

Anyhow my LG Leon is designated as a H320. It also carries a v10 desiganation, v10b. The v10 is variable from a-h or a-i. It would seem that once it is updated to 5.1.1 android it gets upped, and becomes unrootable. Mine being a v10b was rootable, but it took me a while to get used to it, and make the command window work.

Unfortunately for me one of many things I tried before getting it rooted, was ADB fastboot. And since this told me to wait for too long, I pulled the plug on it and pulled the battery to get back into "normal" operations. Perhaps I should have waited, because after finding out a few things about the phone, I discovered the true way to get it into recovery:

The real way into recovery for my phone, is to (from power off state) hold the volume up, a few seconds, then plug the USB cable which is going to the computer into the phone. While holding the volume up until it comes to recovery. This will activate the recovery, (Now for me it activates that fastboot command line...and does nothing else). This was the bit of information I could have used from the beginning, that no one knows. All these places tell you to hold the power and volume up, and then let off power when the screen changes, but that never worked even once. You just hold the volume, and plug the USB from computer. This works.

For me it goes into a "FASTBOOT" header at the bottom of the screen that never changes.

I believe it does this because of my unsuccessful attempt to fastboot it before. And it does not have the right driver to get recognized in the computer. So I'm screwed as far as the recovery goes now.

It is rooted though. And it doesn't seem to have any alternate ROMS available anyways. so we're dealing with the loss of the recovery.

When I do try to use an app such as TWRP manager or CWM (ROM) Manager to reboot into recovery, I get a "boot certification verification -1" error instead of the fastboot line at the bottom of the startup screen and it boots normally from there. So many people asked about this "boot certification verification -1" and NO answers are available anywhere online. So that's where it stands for this phone right now.

Anyone know what driver I should use to get the thing recognized in the computer? I have downloaded a zipped fastboot tools, and it won't get recognized inside the driver manager as "android" only as "unknown device" so I can't use that route....I'm thinking about doing a factory reset to try to erase the fastboot attempt. That may not help though. Anyone?
[LG Leon Questions & Answers] duffycop:
I dunno, I have the H340AR, with this phones happens the same that with the Samsung Galaxy Ace 3, there are, 3G versions, 4G versions, regional versions, etc.. GA3 have 7275R, 7275B, 7272L, 7272T, I dunno, maybe if we could get a device tree for a H340 and an H320 we could make some TWRP and CM compiling, but I just can't figure it out how to make a device tree or even where to begin..

I successfully rooted my H340AR with Kingroot, it works like a charm. I haven't tried fastboot and I tried to install TWRP in this link https://dl.twrp.me/c50/ but I get that F error "Secure booting error". I guess I have my bootloader locked, so I'm trying to figure out how to unlock my bootloader.

I'm trying to contact with some developers and see if anyone can help me build a device tree.
[LG Leon Questions & Answers] Coby5990:
]

Hi, I have that same phone H340AR LTE. I rooted it with Kingroot and also tried to use TWRP to gen into recovery and got that Security error. I only pulled out the baterry and turn it on again so it booted normally. I made a factory reset because I read that it could be a problem of OTA firmware update. Then I installed TWRP and BusyBox again and tried to get into recovery from TWRP option. When I did that, it showed up the Android lying in his back with a red triangle. I pulled a out the battery again and yes, it seems very dumb and simple but it worked and could reboot the phone.

However, I can't get into recovery from TWRP yet. I read that the problem with us not being able to unlock the bootloader(we don't have the OEM option) is because Leon has Lollipop 5.0.1 and OEM is for 5.1.1
[LG Leon Questions & Answers] BaconPr0:
when i pressed factory reset all it did was to a factory reset even though i flashed twrp.img successfully... help?

lg leon h345 lollipop 5.1.1
[LG Leon Questions & Answers] gsearle5:
This device has a locked bootloader. If you flash a custom recovery on it, it will not boot into recovery, but will report a security issue. You will lose all recovery functionality, including factory reset, adb, fastboot. If your phone fails to boot, you have a brick.
[Xperia Z5 Q&A, Help & Troubleshooting] kamalaggi:
Hi,

Im looking to get the Z5 but is there any difference between revision 2, revison 3 and revsion 4 handsets?
[Xperia Z5 Q&A, Help & Troubleshooting] augie7107:
Not sure what you are referring to with revisions. You referencing model numbers?
[Xperia Z5 Q&A, Help & Troubleshooting] kamalaggi:
Take a look at the attached picture.
[Xperia Z5 Q&A, Help & Troubleshooting] peperusso:
I have the version 3.

because there is also the version 4?
[Xperia Z5 Q&A, Help & Troubleshooting] Ben36:
Think my box said 2 on it. I'll check later at home. Maybe it's just what firmware comes pre installed?

Sent from my Xperia z5 by Tapatalk
[Xperia Z5 Q&A, Help & Troubleshooting] kamalaggi:
It looks like it might be a batch number for example revision 1 being the first batch of phones manufactured and so on.
[Xperia Z5 Q&A, Help & Troubleshooting] augie7107:
Could be. I have Rev 4 and got mine 10/5.
[Xperia Z5 Q&A, Help & Troubleshooting] gamer649:
Mine is apparently a Rev 2, manufactured in 2015 during 40 (15W40). I got my device on 19/10/15 (15W43). I'm interested to know the manufacture dates in relation to the rev number.
[Xperia Z5 Q&A, Help & Troubleshooting] Dolphin Trainer:
Rev 4 here, how do you find the manufactured date?
[Xperia Z5 Q&A, Help & Troubleshooting] gamer649:
Open the SIM card flap, there is a tab you can pull out. It is between the SIM tray and the motherboard. It is on the side closest to the screen.
[Xperia Z5 Q&A, Help & Troubleshooting] komugi:
Rev 4 here.
[Xperia Z5 Q&A, Help & Troubleshooting] Duvel999:
Revision 3 here..

Sent from my E6653 @ XDA Portal
[Xperia Z5 Q&A, Help & Troubleshooting] komugi:
Does the revisions have anything to do with the camera blur?
[Xperia Z5 Q&A, Help & Troubleshooting] LitoNi:
Mine is Rev 3 and was manufactured on week 39 (end of sept), and i have the blur on both sides and messed up center (doesnt take a straight line)
[Xperia Z5 Q&A, Help & Troubleshooting] chillaxnphilx:
Mine is Rev 4 from Taiwan
[Xperia Z5 Q&A, Help & Troubleshooting] Adrift98:
Could Rev number have to do with color maybe? Also, it's probably best to distinguish between Z5 and the compact when mentioning Rev #s.

I have Rev 2 yellow compact.
[Xperia Z5 Q&A, Help & Troubleshooting] dazul45:
I have rev 2, Z5 black, manufactured 15W39
[Xperia Z5 Q&A, Help & Troubleshooting] schecter7:
I think rev no has something to do with model numbers (4 models available for Z5). Mine is TW E6653 & it's rev 4 just like few others' here.
[Xperia Z5 Q&A, Help & Troubleshooting] LitoNi:
seems like all the rev 4 are from Taiwan and the 1 2 3 are from UK, and i would assume most defected phones are from UK....
[Xperia Z5 Q&A, Help & Troubleshooting] Adrift98:
My Rev 2 is from Taiwan
[Nexus 6P Q&A, Help & Troubleshooting] Signal2Noise:
Hi there!

I'm going from a rooted HTC One (M7) to the Nexus 6P very soon, and I have absolutely loved my One's silver/aluminum build and would like to get the 6P with the closest color to it.

Would that be the lighter aluminum color, or the darker one? (Obviously, it's not the darkest of the three...)

Thanks! Just trying to get what I want from this phone, and any feedback from anyone who has any of the phones above (6P Silver, 6P White, and/or HTC One (M7)) would be greatly appreciated! :D
[Nexus 6P Q&A, Help & Troubleshooting] Elnrik:
The aluminium color, I would think. I've heard the graphite color is very dark. I've heard the white doesn't feel like naked metal either.
[Nexus 6P Q&A, Help & Troubleshooting] jay661972:
From M7 to N6p, that's an excellent jump. M7 was a great phone, best of HTC years ago

I came from M7, M8, N6 then N6p
[Nexus 6P Q&A, Help & Troubleshooting] galaxys:
64gb Aluminum is what I ordered...should be a shining star! :)
[Nexus 6P Q&A, Help & Troubleshooting] Elnrik:
I thought something similar. Actually, what I thought was "OMFG, a M7? He still uses that? GO! Go get your N6P NOW! Don't stop at red lights! FFS..."

But I may not have as fond of memories of the M7 as others may have had.
[Nexus 6P Q&A, Help & Troubleshooting] Signal2Noise:
Haha! My One is working perfectly to this day and the main reason I'm upgrading is because I want stock Android without mods instead of only being able to flash ROMs with way more features than I want or need. Call me a perfectionist or a purist, but my M7 would last me way longer if I wasn't a needy prude about it! Haha!
[Nexus 6P Q&A, Help & Troubleshooting] Elnrik:
fixed.

Good choice in upgrades then! *applause*
[Nexus 6P Q&A, Help & Troubleshooting] Signal2Noise:
I thought the aluminum looks the most like the M7 in terms of coloring. Would that be a fair assessment?
[Nexus 6P Q&A, Help & Troubleshooting] Signal2Noise:
Well, I think I've made my decision to go with the aluminum 64GB model. Thanks for all of your replies! It's greatly appreciated. :D
[Nexus 6P Q&A, Help & Troubleshooting] Elnrik:
Yep!

---------- Post added at 02:11 PM ---------- Previous post was at 02:11 PM ----------

:good:
[Nexus 6P Q&A, Help & Troubleshooting] opz187:
m8 Harmon Kardon here. honestly this is the best phone I've ever owned.. but as solid as this phone is, time for 64 bit with some qhd. so I upgraded to the 64gb note 5, which was nice as hell, but there just isn't any development going on w it, think most ppl skipped on it. nexus 6p is, well, a nexus.. so sure to be bursting with custom everything. returned note 5, ordered 6p on Oct 10. have to wait until Nov 18-20 for delivery. gonna kill me. m8 should have some fluffy ports coming before then though
[T-Mobile LG G3] spc_hicks09:
The Gnex among devices has a Marshmallow build. Anyone with a G3 working on one?
[T-Mobile LG G3] hockeyhead019:
this is the only thread I've seen on it so far:

http://xdaforums.com/lg-g3/devs-only/marshmallow-6-0-0-d855-testing-real-t3220114

Other than that I saw that the G4 just got a 6.0 image uploaded. Hopefully we aren't far behind.
[T-Mobile LG G3] ssuds:
CM team already is.

https://github.com/CyanogenMod/android_device_lge_d851/tree/cm-13.0
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] Montisaquadeis:
Heres the deal I have a kindle fire HDX 8.9" (Apollo) On firmware version 14.3.2.4_user_324002120 and was wondering if it is possible to unlock the bootloader.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
Yes. Procedure involves a rollback to FireOS 14.3.1.x, installation of TWRP recovery, updating the native bootloader and then working through the unlock procedure (tedious for some). Once complete you can flash several HDX compatible roms including Nexus v4, CM11, two lollipop variants (CM12, SlipLP) or stick with FireOS provided you don't want to install gapps.

If needed I can post an outline and link to contributor supplied guides in a day or so ... or perhaps someone will jump in with the gory details. Or you also can browse through the forums. I'd wait for more info as it's pretty easy to brick your device (no recovery) if you go off script. In no case should you tweak build.prop or flash different versions of FireOS without specific instructions.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] fabische:
"If needed I can post an outline and link to contributor supplied guides in a day or so..."

This would be highly appreciated! Thanks!
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] Cl4ncy:
With 3.2.4 you could use the rollback images provided by [MENTION=5749760]ggow[/MENTION]. Check page 2 of this thread (page 1 is about 3.2.5/3.2.6 users, who can NOT use the rollback images!).

This would require rooting with HDX Toolkit and installing Safestrap 3.75. With Safestrap v3.7x note that factory reset means standard wipe only! Do NOT open advanced wipe menu, and especially do NOT wipe system! Keep WLAN off/flightmode active to avoid getting updated by Amazon, (re-)root and disable OTA via HDX Toolkit after downgrade, then flash TWRP, update 3.2.3.2 bootloader via TWRP, unlock bootloader and flash ROM of your choice - be sure do create a backup of your Fire OS in TWRP and move it to your PC before you flash any custom ROM!

Read the info, and ask first if you have questions, i.e. before you brick your HDX. ;)
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] fabische:
cheers mate! Just wonder how I can rollback my Apollo from 14.4.5.2 to 14.3.2.4 which is required to unlock the bootloader.

All the instructions that I can find state that you cannot rollback below 14.3.2.8....
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
You can't. Any attempt to rollback below 3.2.8 will brick your device (anti-rollback protection). There is no way to unlock the bootloader on a device that has been upgraded (or began life) above 3.2.6.

However, with 4.5.2 you can root, install Safestrap v4 and then have a choice of CM11 or Nexus v4. Post back if you need assistance.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] fabische:
Thanks for the quick reply! Basically, I have constant issues with GAPPS running on my rooted 4.5.2 Apollo. For the last six months I have simply blocked any updates of Google Play Services (+chattr command). This was fine for a while, however, meanwhile apps like Google+ & Photos are working less than satisfying. I have updated Google Play Services today which eventually killed my Google Play Store. I managed to get back to the previous so-so state because I had backed up the Google Apps files with Titanium backup. Though my "simple" aim remains to have a working Gapps package on my system. However, the safestrap method, for some strange reason, is currently no option: when I install safestrap 4.1 and try to enter recovery the system goes into a black screen.

To cut a long story short my longterm plan now is to rollback to 3.2.8 again, upgrade to 4.5.2., root and reinstall Gapps manually (or is there a quicker option?). Possibly, Safestrap will work again then too.

Does this make any sense to you?

cheers!
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
You are in a tricky situation. If Safestrap v4 won't boot the contents in one of the native Amazon partitions (boot, recovery or system) may be damaged. You need some of these components to rollback or upgrade. If attempted outcomes can range from refusing to process the rollback/update file to an unrecoverable brick. You sometimes see this in a pure stock device. Working fine then bricks after receiving an OTA.

Thoughts:

- it is possible to 'refresh' the recovery partition with Flashify but you will need to find a compatible 4.5.2 recovery image

- suggest you upgrade to 4.5.5 first. Based on

limited

feedback the risk of a minor FireOS v4 upgrade is less than rolling back.

- if the upgrade is successful you can then attempt a rollback to 3.2.8 followed by upgrade to 4.5.2 (keep WiFi off!!)

- you should uninstall GAaps before upgrading/downgrading.

- there is increased risk if you previously changed permissions on system files to block OTA, etc.

- you will need to reenable OTA (hopefully just a file rename) to up/downgrade.

- I believe Safestrap v4 will install and run correctly if you successfully rollback and upgrade to 4.5.2.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] fabische:
Thanks, davey126. Before I set off for this next adventure: what is your guess that we will see an unlocked bootloader for current fire OS versions in the future? (this might save a lot of trouble)