yashsingh1/xdaforums huggingface dataset:
[Xperia Z2 Accessories] Oxynium:
Hello, I have problem with MHL adapter, maybe someone can figure it out.

I bought first adapter, something like this:

[IMG="Image"]http://media.tumblr.com/b026a665faf14a9ba5c53559db8aff95/tumblr_inline_mrpx12d8FP1qz4rgp.jpg[/IMG]

This one works with my 1080p TV, but FPS is too low for anything except movies. I thought that it probably is MHL 1.0 adapter which supports only 24 FPS.

So I bought another one, MHL 3.0 Delock adapter

[IMG="Image"]http://www.bilder.delock.de/produkte/thumb/5502f6de7f34d3.15574520.jpg[/IMG]

beacuse I found somewhere that MHL 3.0 doesn't require external power and It supports 1080p with 60FPS. But this one doesn't work at all, phone makes "charging started" sound when connected to TV, but nothing happens. No MHL window pop-up, no even charging.

Where is the problem? Does MHL 3.0 require specific TV or something? It should work anyway, beacuse MHL 3.0 is backwards compatible. Maybe cable is disfunctional?

PS: TV is 50' Funai 50FDI7724/10
[Xperia Z2 Accessories] bycannn:
I dont think the second one can work without any circuit

Probably there is a curcuit on the cable for which transformation the display
[Xperia Z2 Accessories] cimihendriks:
your tv needs to support mhl, to use it without external power...
[Xperia Z2 Accessories] phperera:
try disabling "STAMINA Mode" it will increase FPS , if not ,

connect the MHL cable & goto Service menu by *#*#7378423#*#* & select

Service Tests -> TV-Out-Test -> Video format & change it to the low resolution (1280x720 60FPS) , go back , reconnect the MHL cable and see it helps.
[Android Q&A, Help & Troubleshooting] Wingthe:
Which can you consider the best app to hide your personal pictures and videos?

I have been looking for the best app to hide my personal stuff but never find any such app. I want an app which can give full protection and can totally hide my personal pictures.
[Android Q&A, Help & Troubleshooting] Onin1988:
Leo Privacy Guard is all you need. Just install it and you can hide your personal stuffs and no body will ever find your personal stuff except you. Just try it.
[Sony Smartwatch 3] Outcasst:
Hi, I just received my brand new SW3 and I'm having trouble setting it up.

I link it to my phone (Galaxy S6) and then it brings up the "Downloading" screen on the watch. About 1/10th of the way through it comes up on the screen that "Android Wear has stopped", followed by "Google Play services has stopped".

I've tried resetting the process many times and it happens over and over.

Any advice?

Edit: Downgraded to an earlier version of the Android Wear app, apparently the latest ones don't keep in constant contact with the watch, hence the crash. Went to the version from the 25th February and so far so good, it's got to 50%.
[Sony Smartwatch 3] spikeyl:
Have you got the latest firmware on the watch? I have a sw3 and s6 combination - it has been difficult with the latest updates, but a new version of play services a few days ago seems to have helped
[Sony Smartwatch 3] ebones:
For anyone interested, the exact wear companion version that can get you past this error is 1.0.5.1724356. It will update device from 4.4.* to 5.0.2. You may get a warning that "something went wrong" while downloading which can be ignored.
[Sony Smartwatch 3] labarbacoa:
I'm having this exact problem. After using the earlier Wear app, should I update it after?
[Sony Smartwatch 3] Rockamakis:
My wife had this same issue with her watch when she was trying to set it up. She has a S5. It kept getting stuck at the same point when downloading. I thought the watch was defective but it was an issue with the phone. I used my phone to setup the watch instead and had no problem. After it finished I connected it back to her phone and she hasn't had any problems since.
[Redmi Note General] tendulkaradi:
End
[Redmi Note General] tendulkaradi:
U guys seem to need everything for free...nonsupport to a developer

Sad.....
[Redmi Note General] Bitti09:
Reaction to Your post is the one I expected:

New ROM 4free? Good rom

Daily ota updates? Best rom ever

Donate something? What a ** ROM what other ROMs are good beside this .

On blind builds: tons of bug reports and limited ways to resolve them for the dev

Gesendet von meinem MI 3W mit Tapatalk
[Redmi Note General] tendulkaradi:
Well I guess this guys love the laggy miui7 and the buggy cm11 and xperiance ROMs... Duhh.....
[Redmi Note General] Bitti09:
It seems that they love MIUI & KitKat ROMs [emoji19]
[Redmi Note General] tendulkaradi:
Lol
[Redmi Note General] tendulkaradi:
Ending the thread
[XDA Assist] Dushan310:
Hi all,

I have problem ,

my phone is kyocera E6560 and i forget my pin, and i can't use my email to recover it problem is can't enable mobile data or wifi,

so try to format it ...it want work,

i google many times to find out a solution...but still i'm stack ...i tried volume down + home + power it wont work...

please help me:confused:
[XDA Assist] rirozizo:
Hi,

Since your device doesn't have a dedicated forum here on XDA, i suggest going HERE and asking for help there.

Good Luck!
[Nexus 6  General] bitpushr:
I had a hard time finding this information, so thought I would post a new thread!

After you root your phone, even if using standard recovery, the OTA updates will no longer install. You may get the notifications, but after it reboots to install, you will get a failed notification. Even if you uninstall root. This is because if there is any change to the system image at all, the OTA update will fail.

To install it is actually easy, just requires some legwork. I assume you understand what the bootloader is, and what adb and fastboot tools are since your phone is already rooted. If you used a toolkit, there are plenty of guides on XDA on how to install these tools manually.

Step 1 - Collect Needed Files:

Visit the Google System Images page and download the image for your existing ROM. Check your About Device page to get the exact ID, it should say something like LVY48E.

Extract the system.img file so you can flash it later.

Download the OTA image. All OTA images are listed on the Nexus 6 OTA Images thread. Find the file which upgrades "From" your current ROM id. It will only work if from matches your current image version. It will be named something like 2bef78c4a5ec8dbaa3df9d94e78af8622cd2a394.signed-shamu-LVY48F-from-LVY48E.2bef78c4.zip, and this file in particular flashes to the new LVY48F version from LVY48E version.

Step 2 - Flash Stock System Image:

This step replaces your system image with the stock system image. This will not delete your apps or other personal data, only the information stored on the system partition. The only exception is if you rooted and stored any data on this partition. Plug your phone into your computer. There is no way to do this without a PC.

Reboot into bootloader mode either from booting with POWER+VOLDOWN or via adb:

adb reboot bootloader

and flash the image

fastboot erase system
fastboot flash system system.img

At this point your system is stock again (unrooted).

Step 3 - Flash Update Image:

Enter the recovery mode. You can also do this via TWRP but I will cover with stock recovery. Press Volume Up/Down until you see RECOVERY and press power to choose. You are now in recovery.

Press and hold Power and tap Volume Up once to get the recovery menu. Then use Volume Up/Down to select "apply update from ADB" and then Power to select

I had to unplug and plug my phone back in at this point to get it to show up to adb. You can confirm it is visible with the command adb devices.

Apply the OTA update file using the following command, replacing the file name with your own:

adb sideload 2bef78c4a5ec8dbaa3df9d94e78af8622cd2a394.signed-shamu-LVY48F-from-LVY48E.2bef78c4.zip

After a few minutes the sideload will complete, the phone will reboot and optimize apps, and you can verify the update worked by checking your about system page again.

To root your device again, re-install SuperSU and you're good to go.
[Nexus 6  General] hayzooos:
I actually just asked about this in the T-Mobile thread, but thanks for making this. My question is, when installing system.img is there anything else you NEED to flash as well, specifically boot and/or cache?

Google has the latest stock image for T-Mobile so I was planning on flashing system and radio, but I wasn't sure if there was anything else required when flashing system.img.

I know I don't want recovery or userdata as that would replace TWRP and all my data, so I'd of course leave those out.
[Nexus 6  General] bitpushr:
Nope, system.img was all that I flashed, verified it worked fine with just that.
[Nexus 6  General] JTheAppMerchant:
So you just have to re-root after right?
[Nexus 6  General] bitpushr:
Correct
[Nexus 6  General] falconfox:
Thanks for this guide. I've been trying to figure out how to do this exact thing. When I do the command:

it gets to about 50%, then gives a Error message,

Any suggestions?
[Nexus 6  General] bitpushr:
First try a different USB cable and port.
[Nexus 6  General] torecdude:
Thanks for the guide. Does it wipe all the data and files in internal storage?
[Nexus 6  General] photolarry:
I did this successfully

I wanted to say thanks first of all for putting this up. It helps those rooted users out there that do actually want security patches applied to the system image. To answer the question above, No it does not wipe data or storage if you follow the instructions to only modify /system partition.

A note about the LMY48M update file and the above comments in the OP : This update changes the kernel (in other words), the boot.img file as well. So if you have flashed a non-stock kernel, you will need to go back to stock during the update (and I suggest just leaving it). That is the partition called boot where boot.img lives. It mainly is the kernel. The way to go back to stock (say if you flashed franco with the FKupdate tool and did not do it manually) is to simply do like above and flash it from the factory image he mentions above for 48I file.

You reboot to the bootloader (*I assume you know how*) with power and vol down button. And then the following command after flashing system.img:

fastboot flash boot boot.img

This takes you to stock LMY48I and should allow you to update now to 48M. I learned this by watching the update failure messages as well as noticed it has boot.img changed in the zip file. Hope this helps others. :good:
[Nexus 6  General] confused2much:
I'm having the exact same issue/error. Already tried new USB ports and cables.
[Nexus 6  General] jase33:
Open the update .zip file and go to META_INF > COM > GOOGLE > ANDROID. You will find the "updater-script" file.

Open that file using a text editor like notepad or notepad++ and delete the following text; starting from "assert ....... till the semicolon of the last getprop command.

Place that file back into the update .zip file and reflash. This should remove the status 7 error.
[Nexus 6  General] confused2much:
I'll try this now, thanks for the response!
[Nexus 6  General] :
Honest question: why would you flash a system image and an ota when you could just flash the new system image?
[Nexus 6  General] jase33:
By flashing just the current system image your data stays in tact. Then you can take the OTA, it will see the system image unmodified, and it will update everything for that new version without wiping data.
[Nexus 6  General] confused2much:
I do not have the text "assert" anywhere in that file....
[Nexus 6  General] sansnil:
Easier to just flash the new system image that gets you to the same place as the OTA.
[Nexus 6  General] hayzooos:
I was wondering this same exact thing, but I was assuming it was because the OTA was hitting people before that matching Google Factory Image was available. This would bring you almost back a version (to being stock) so you could take the OTA.

If the OTA is to match the same Factory Image you can get from Google, I have no idea why you'd do both steps.
[Nexus 6  General] mattmtx:
Hi, I have the LNX07M, and I don't find it in the google page. Can you help me? please!
[Nexus 6  General] gohamstergo:
I think the only reason to do both steps is to apply the update ASAP. If you are ok waiting, then only flash the new system.img. That's definitely what I always do. I don't mind waiting. I have Google Play Services notifications hidden now anyway, so those update notifications don't show up and bug me.

Thanks for the walk through though, [MENTION=450224]bitpushr[/MENTION], I'm sure many can make use of it.
[Nexus 6  General] archbox:
Honestly, you shouldn't edit those files as that can be dangerous, and disabling the filesystem check can be dangerous, and it probably won't work because then the zip would fail signing verification.

If you followed all of the instructions in OP and still get error 7, try, on top of erasing and flashing the stock system.img, also extract and erase then flash boot.img and recovery.img. You will get error 7 if your recovery and kernel (boot.img) aren't stock.
[Nexus 6  General] jj14:
No reason (unless the factory image is delayed). Flashing the new system image is the faster way (just flash the latest system.img, and if the radio is newer, flash that as well, and then, reroot using twrp)

---------- Post added at 09:14 PM ---------- Previous post was at 09:11 PM ----------

LNX07M was a dev build - it isn't going to get OTA to current build. Where did you buy your phone from? Contact them, and ask the to replace it - or you can read the sticky about how to flash factory images and flash the one for your carrier.
[Nexus 6  General] mattmtx:
I bought on Amazon (Motorola Amazon), and a friend brought me to Argentina. So, its the second choice. What I have to read? Install a new img rom downloaded from here and here, or it's the same?

Download the gapps for 5.1.1 in the case that I chose that one. I flash all with TWRP.

Thanks in advance!

Ah, and all these I can do with NRT in advanced utilities?
[Nexus 6  General] jj14:
The 2nd link you mentioned is for OTA, so that is not going to be helpful. First one gets you the link to the images but not the details on the steps...

Read http://xdaforums.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 - the first post at least... Completely :)

Method 1 to flash using flash-all will likely not work, so read method 2. Remember that when you unlock bootloader, your phone will be wiped - all data wiped.

I know I said it already but I'll say it again ...Read those instructions thoroughly :)
[Nexus 6  General] mattmtx:
Oks, and I have an update (to 5.0.1) but I can't install because a rooted my phone and unlock the bootloader. If I want to upgrade I have to do a factory reset, and then try to install the update.

Do you recommend me that, first doing a factory reset, previously backup, and then try to install that update and see if that update it's ok, and later upgrade to a compatible new rom

Info: I have read that I get the update LRX21O , with the update from 5.0 to 5.0.1.
[Nexus 6  General] Borderpatrol1987:
Reading the directions twice can never be stated enough. :) that and ask first before you make a mistake :D
[Nexus 6  General] vMAC:
So following this process will require wipe of system? So you will have to reinstall all apps again?
[Nexus 6  General] Snowby123:
Does this tutorial work on other Nexus devices such as the Nexus 4 or the Nexus 7?
[Nexus 6  General] mattmtx:
No, I understand that with this process you dont lose any data. In my particular case, yes but because I have to install all again from zero.

If you have to follow this process its because you already unlocked your bootloader.

Enviado desde mi Nexus 6 mediante Tapatalk
[Nexus 6  General] vMAC:
Can anyone help me with why I would have an error when following this process?

I currently have build: LMY48I

When I follow this process and try to sideload the new system I get this error:

Verifying current system...
Package expects build fingerprint of google/shamu/shamu:5.1.1/LMY48I/2074855: user/release-keys; this device has google/omni_shamu/shamu:5.0.2/LRX22G/dees_troy02120939:eng/test-keys.
E:Error executing updater binary in zip '/sideload/package.zip

Here are the two links that I used to get the files:

LMY48M from LMY48I - https://android.googleapis.com/packa...I.4458964f.zip

5.1.1 (LMY48I)	Link	a60091da8140fff4a06df7616015f83d	230e50fe59a7a008e0a0cc6bd4bd2bda133b2378

I extracted the system.img and followed the directions above.

Any help would be greatly appreciated!
[Nexus 6  General] cmecha:
after trying to run the side load,

adb sideload 2888e222d3aaa1f60dea879699188fdd612e51c2.signed-shamu-LYZ28K-from-LYZ28J.2888e222.zip

i recieve "error:device (null) not found."

Also reinstalled Supersu and it's telling me i need to re-root.

any advice on side loading would be helpful, I also copied the zip in to the directory with ADB.
[Nexus 6  General] ethanhunt123:
Follow up to this.... what exactly does the OTA usually update? Just the boot, system, and radio images? Does it usually not touch userdata?

If so, flashing those images alone, is effectively the same as "sideloading" the OTA?

---------- Post added at 03:00 PM ---------- Previous post was at 02:57 PM ----------

I think i found my answer here... http://xdaforums.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
[Nexus 6  General] jj14:
Effectively, yeah. In the backend, it is slightly different. OTA only updates the necessary files in the partition, while the flash updates the partition as a whole. End result should be the same.
[Nexus 6  General] vMAC:
You need to check your drivers.

If you are getting Device Not Found, then the computer is not detecting your Google USB drivers.
[Nexus 6  General] cmecha:
I just ended up installing the updated image, did not wipe anything so I'm good.
[Nexus 6  General] SymbioticGenius:
While I think this is a good guide I suppose, I'm pretty sure it's just easier to use fastboot for everything. I flash the images and TWRP and root. Pretty easy once you try it

Sent from my Nexus 6
[Nexus 6  General] NLBeev:
Have done this a few times. Data is kept, but not the settings.

After every flash of system.img or unroot and OTA update, the build.prop settings are default. Because DPI is 560 again, icons are gone and the blacked out Google Now Launcher is white again.
[Nexus 6  General] doitright:
You should consider adding your customizations to /data/local.prop instead of /system/build.prop. The latter *will* be wiped every time your /system partition gets cleared. In general, the fewer changes you make to the /system partition, the easier your life will be.

---------- Post added at 09:01 PM ---------- Previous post was at 08:58 PM ----------

By flashing just the NEWEST system image, your data stays equally intact. Breaking it into two steps (installing the PREVIOUS system image AND THEN the OTA) is just a waste of time.

This is not opinion. This is fact.
[Nexus 6  General] jase33:
If you just flash the OTA system image you will not get anything else that may have been updated with the full OTA package. Lets say the OTA brings a new radio, or new boot image, or new kernel, or new recovery. You would then have to flash them separately if you wanted them. It all depends on your situation.
[Nexus 6  General] NLBeev:
At this moment the dpi is set to 384 (tablet mode). When that's changed to the Google default of 560, all icons are gone.

Thx for the suggestion to use /data/local.prop.
[Nexus 6  General] doitright:
All of those parts are included in the full system image package.
[Nexus 6  General] jase33:
The system image and the OTA package refer to two different things. The system image is one part of the OTA package. See the referenced OTA package LYZ28E from LMY47M and you will find the boot.img (kernel), bootloader, and radios as separate files.

If you only flash a system image in fastboot you will not get the other files in the OTA package. This is why, if you have modified your system files and the OTA fails, a fastboot flash of the unmodified system image from your current version is first required then the OTA update can be applied in full.
[Nexus 6  General] doitright:
No.

The system image is not contained in the ota. The ota contains only *PART* of the system image. The *DIFFERENCES* from the previous system image.

Full system packages (containing system.img and boot.img, among other parts) are available for download from https://developers.google.com/android/nexus/images?hl=en
[Nexus 6  General] stumpy352:
Um, that would be why the op instructs to flash the unmodified system image from the factory images, then adb the ota.
[Nexus 6  General] Philip:
Or just do it all through Nexus Root Toolkit - much easier, quicker and less prone to error.
[Nexus 6  General] atominvention:
I use nexus rootkit to unroot, flash latest image and root again, seems fine
[Nexus 6  General] entaro:
Will this work on the upcoming M update?
[Nexus 6  General] hayzooos:
Will it work? Probably. Should you do it? Probably not.

When upgrading to a new OS with as many changes as this, best practice is to always start fresh.

If you're going to piecemeal it, I'd suggest flashing the individual images with the exception of userdata.img so you test it out while keeping your data. If you run into any issues after that, probably best to just flash the whole shebang and start fresh with 6.0.
[Nexus 6  General] tsjanda:
Does flashing system.img replace twrp recovery? Just trying to understand the process. I am to adb system.img then reboot to recovery (twrp) and flash ota then reboot? Or do I flash ota and SuperSU, busybox and then reboot. Or can the ota even be flashed via twrp? Which is better sideload or twrp flash?
[Nexus 6  General] r3r3:
Well, I followed bitpushr's guide, I'm grateful for it but it didn't work. I haz Nexus 6 with mmb29q

I erased and flashed the correct system.img from the factory image related to my running firmware (mmb29q)

Then I tried to sideload the OTA from TWRP: TeamWin recovery it failed with "Status 7"

I then proceeded to flash the stock recovery and sideloaded from adb and default recovery - Same issue "Status 7"

So i booted my phone and used the default proposed OTA update and I get the same error:

Unexpected content...
error in @/cache/recovery/block.map
(status 7)

I read this

OTA checks the signature of the system partition. If it doesn't match a clean, untouched system partition, it will error. Rooting and then using the unroot option within the app will not return the signature back to what it was before it was ever rooted.

bitpushr any hint?

---------- Post added at 12:10 PM ---------- Previous post was at 12:06 PM ----------

No you have to flash recovery, but you might then get the same error in flashing the ota as me, read me above :)

In case you want to try, it's the same procedure as for system.img

adb reboot bootloader

fastboot erase recovery
fastboot flash recovery recovery.img
[Nexus 6  General] Didgeridoohan:
You can't have a custom recovery if you want to flash an OTA-file. System, kernel and recovery needs to be stock.

Since you know how to flash, just flash the parts of the factory image that have been updated since your last update (bootloader, radio, boot and system). Always skip userdata.img (if you don't want to wipe your data) and if you want to keep TWRP also skip recovery.img.
[Nexus 6  General] r3r3:
Okay realy? That works? Hmm wouldn't have guessed

Edit: Well that's super, Now I'll update my rooted nexus 6 like this each time! :)

For those willing to do the same it's super easy, I'm guessing the erase part might not even be needed. Just go to fastboot and flash away and ignore userdata.img and ignore recovery.img if you want to keep your third party recovery.

adb reboot bootloader

fastboot erase bootloader
fastboot flash bootloader bootloader.img

fastboot reboot-bootloader

fastboot erase radio
fastboot flash radio radio.img

fastboot reboot-bootloader

fastboot erase boot
fastboot flash boot boot.img

fastboot erase cache
fastboot flash cache cache.img

fastboot erase recovery
fastboot flash recovery recovery.img

fastboot erase system
fastboot flash system system.img

Thanks Didgeridoohan :good: