Hi guys.Your Suggestion is very much appreciated. (Updating to Nougat before anythin)

Hi there Guys. GoodDay. I just wanna ask. I recently bought Nexus 5x. And i see nougat is ready for update. But before that Ive found out on internet that some users that updated from MM to Nougat got stuck on bootloop and seems they cant figured it out i dont know if its model related(h791/h798). Google Employee says hardware. Here 's a qoute of a report. from androidauthority website.

"We've been hearing an increasing number of reports from Nexus 5X owners about bootloop issues after upgrading to Android 7.0 Nougat.

Many folks have been claiming that, after installing the Android 7.0 Nougat OTA, their Nexus 5X devices would unexpectedly crash and begin to randomly reboot after a few hours, or even days, of use. Some users say downgrading to Android 6.0 Marshmallow does the trick, while others say reflashing the Android 7.0 Nougat September update fixes the problem. Most people, unfortunately, have yet to find a good fix for the problem.

So if you run into this issue, what should you do?

Orrin, a Google employee, had this to say in the Nexus Help Forums:

We understand that a very small number of users are experiencing a bootloop issue on the Nexus 5X. We are continuing to investigate the situation, but can confirm that this is strictly a hardware related issue. For those of you that are currently experiencing this, please contact your place of purchase for warranty or repair options.

We're sorry for the inconvenience and appreciate your continued patience."

Im afraid that if i update via OTA just like them. chances it might or might not happen to me. and if did, can a tool like Wugfresh' NRT save it? or should i root and manually update to nougat via some toolkit or manually, is it safer? Thank You very much for your suggestions.
BtW: im on
LG H791 Android 6.0
Build MDA89E
Security Patch Oct.1,2015

from xda-developers http://ift.tt/2dsPlNI
via IFTTT

(DRM) TA partition (E6553 aka Ivy)

Dear readers,


Lets start from the beginning, roughly six months ago:

1) My trusty GT-I9300 died, had two for spare parts but ... SDS;
2) I got a Note 2, got blown off the road and ended up in the canal :( Phone was soaked, dead;
2) I bought an Xperia Z3+;
3) I unlocked the bootloader;
4) flashed AOSP.

Result: warranty void on day one!

I picked this phone for modability, sadly there are not that any developers active for this device and I have been slowly patching AOSP from Sony with some changes here and there trying to get a CM13 build going. But due to the dive into the water with my car, I have no desktop PC/laptop (both were i7 quad's) and my dualcore iMac makes development kinda tiresome.

Anyway, little did I know that upon unlocking the bootloader my DRM keys would be lost and on that note I did not really care either.

But today I accidentally started working on CM again and figured that the DRM messages about Widevine in logcat should be eliminated. So I looked into solutions, but the DRM "fix" wasn't creative enough (no sources, wtf?) for me and I set my aim on the culprit of it all: the TA partition!

I've probably been looking at it for at least half a day now and hallucinating due to sleep deprivation. BUT, I do NOT believe Sony just scrapped the DRM keys because you unlocked the device. The keys have come from somewhere, and the best thing about keys is: they can be reproduced!

So I have been looking through dumps, comparing things and found out that the keys are most likely "destroyed". I say "destroyed", because I believe there is a good chance of restoring them!

Gory details about the TA partition (post mortem):

CKb keys look like they are "blanked" with:
00XX 0000 0000 YY00
00XX 0000 0000 YY00

(I think XX represents the date (04-02, second of April) and YY represents the time (22:29) when I voided my warranty!

A CKb key is a simple Counter Key, so most likely easily recovered given enough data...

I noticed that there was a SQLite3 database file inside the TA partition, I extracted it and it holds the following data:

CREATE TABLE keytable ( dbAppId BLOB, dbUserId BLOB, dbKeyId BLOB UNIQUE, dbEncKeyType BLOB, dbData BLOB);

Looking at the last column of the table I noticed this:

The first entry = 31
The second entry is 313038
The third 323135
And the fourth 333232...

The dbData column increases with 10097 every time, could it be related to the CKb?

For the rest it looks like everything in the TA partition everything is in fact intact, except for CKb and AUTHCERT="UNKNOWN" for Marlin (not 100% sure if that is present pre-unlock)!

Marlin X509 certificates are intact.
HUK is the Hardware Unique Key, stored on a quite a few places.
Widevine looks intact.


So, why do I focus on the CKb? Simple, look at these reasons:

CBk is used in TLS/SSL authentication (requirement for NEMO (Marlin));
It is used in QSEE. < this is patched with the DRM "Fix";
It can be encoded as RSA and/or SHA1, and is easily verified in SBL with CRC.
TA unlock/lock data is passed as 0x0000000000000000.
If you use 10097 as a CRC polinomal, the last bit of your message changes (in this case your UID for ScubaKey and drm-client swap).


So, my question is:

Is there anyone with a backup of his TA partition that could send me a dump of this folder:

/dev/block/platform/soc.0/<bootdevid>.sdhci/by-name

You can leave userdata, system abd apps_log for what they are. I just want to compare bits spread over the other partitions.

I will need a dump from a locked state and one from an unlocked state where TA is not restored to see what actually gets changed.

You can PM me on the forum or sent an e-mail to my username at gmail.com, I will make you an account on my PC to drop the files!

from xda-developers http://ift.tt/2d0lDg0
via IFTTT

Need Acatel One touch Elevate (5017b) Rom

Hello everyone this is my first post here so forgive me if i'm doing this all wrong but i really need help here guys.. :( :(

I recently tried to delete some system apps on my phone via Superuser and i deleted some important system apps so i cannot use the WiFi at all (Causes my phone to reboot and everything if i try to connect to Any WiFi) so i wanted to flash the stock rom back to my phone in start all over but i cannot find a Rom for an Alcatel OneTouch Elevate (5017b) anywhere..

Can someone please post or find a stock rom for me so i can get my phone back the way it is.. ?

from xda-developers http://ift.tt/2dsPaBN
via IFTTT

Downgrade BLU Studio X8 HD from Kitkat to Jellybean

Hello - I am a new user of the Android system (been on Windows Phones for several years). I bought BLU Studio phone and found it could not talk to my car's Android Auto system as it was not a Jellybean or Marshmallow system. Is there a way I can downgrade to Jellybean or upgrade to Marshmallow, either by forcing a system build reset or any other means. Complete novice when it comes to Androids so my apologies if this is a dumb question.
Thank you all

from xda-developers http://ift.tt/2cvz4XS
via IFTTT

Camera Lag

Anyone know a way to get rid of the delay between when you hit the button to take a picture? My camera takes a few seconds to focus before it takes the shot, which always leaves you missing something in the moment. My wife has an m8 as well on another carrier but don't see the same lag there.

Sent from my HTC6525LVW using XDA-Developers mobile app

from xda-developers http://ift.tt/2djcjYy
via IFTTT

Google Pixel Launcher [TWRP] [APK's]

Google Pixel Launcher

I prepared a zip for flashing Google's new Pixel Launcher in TWRP recovery for my convenience and decided to share it as more and more users are enjoying the success of unlocking the bootloader and flashing the TWRP recovery on their new Honor 8 device.

For those having yet to unlock the bootloader of their Honor 8, I've attached the apk's below for simple apk installation with Unknown Sources enabled in System Settings. However, I have not installed either apk via this method so the attached apk's are simply provided for users without root to try and report success or failure.

Once successfully installed, Pixel Launcher can be set as the default launcher in EMUI by performing the following steps below:

Settings > Apps > Advanced > Default App Settings > Launcher

Attached Files

	Pixel Launcher.zip - [Click for QR Code] (3.22 MB)
	NexusLauncherPrebuilt.apk - [Click for QR Code] (2.42 MB)
	WallpaperPickerGooglePrebuilt.apk - [Click for QR Code] (2.25 MB)

from xda-developers http://ift.tt/2cttPmG
via IFTTT

Boot loop out of ideas

So I was on the note4UXEdge ROM for about a week, everything was fine. Today it randomly rebooted and Android would no longer load. It just loops on the splash screen, with Recovery reboot, recovery is not SEandroid enforcing, set warranty bit : recovery loop. I've tried to odin stock ROM but that just leads to recovery reboot loop. I've tried to odin a twrp recovery but that doesn't do anything, if that's even possible? Holding volume UP+power+home is supposed to get me to a menu to wipe cache/dalvik but I never get to that. I can still go into download mode so i hope there's more i can do. Halp please, thanks in advance. :eek:

from xda-developers http://ift.tt/2cttSPs
via IFTTT