yashsingh1/xdaforums huggingface dataset:
[Nexus Player Q&A, Help & Troubleshooting] Silenus21:
Thanks a lot.

Was going to make a thread about this problem I'm having too.
[Nexus Player Q&A, Help & Troubleshooting] TheShamsMan:
Awesome! Thanks for the tip! I just made the changes now and will report back first thing in the morning!
[Nexus Player Q&A, Help & Troubleshooting] mxup:
btw, i can testify the fix proposed by GabbyWC works!
[G4 Q&A, Help & Troubleshooting] mehra1:
Hi guyz,

Little background of my device: I have converted my device successfully to h815 by following this thread http://xdaforums.com/g4/general/lg-g4-f500l-restore-signal-flash-815-t3214574 and it worked like a charm for few weeks.

Last evening i just recieved few updates on apps from google play store as usual I clicked on update all and then after that my phone hanged for few seconds and started to bootloop with the same error.

Now i am not able put it in download mode, as it just boot again and again.

If any one have any solution please help.
[Xperia Z3 Q&A, Help & Troubleshooting] P3p3es:
Hello

Is there a patch for the issuance of marshmallow model D6633

Please advise me, please
[G2 Q&A, Help & Troubleshooting] bbb0777:
Touchscreen issue: Running "Check Synaptics Noise" fixes it, but only for ~8 hours.

So the general problem is 1.) double tap to wake doesn't work, 2.) I can't pull down the notification panel while in portrait mode.

If I access the hidden menu (3845#*800#), and go to: HW Device Test > Touch Test > Check Synaptic Touch Panel, it says: F54_FullRawCap Test Result: Fail

If I go to HW Device Test > Touch Test > Check Synaptics Noise - I can run the test, then everything will work for about ~8 hours. It'll also change to F54_FullRawCap Test Result: Pass.

Around 8 hours later though - back where we started, unless I run "Check Synaptics Noise" again.

I'm running Cloudy G2 2.2 with the standard Cloudy kernel. Re-installing the ROM has no effect. Changing the kernel to dominatrix has no effect.

Thoughts?
[G2 Q&A, Help & Troubleshooting] bbb0777:
Actually, now I think maybe just running: HW Device Test > Touch Test > Check Synaptic Touch Panel, two times, is what gives the phone a temporary fix.

Weird...
[Motorola Atrix HD] orangzeb:
Is it possible to move all installed apps to external or somehow set external storage as default for new installations and downloads ?

Anyhow I'm on custom and rooted rom. 4.4

Thanks.
[Verizon Samsung Galaxy S 4] jgastald:
Today I got verizon samsung s4 (new, from Woot). It came with Lollipop, but Kies suggested an update, so I tried it. The update failed and now I'm stuck on "Software Update Failed"

I couldn't find the "Verizon Software Repair Assistant" download.

I cant get it to boot to recovery. It just goes to "Software Update Failed" or ODIN

So I started trying to flash it with ODIN. Read a lot of threads (enough to realize that this is a deep mess and get quite confused) and tried half a dozen of ROMS, and a PIT, but all fail with these message in the phone:

"SW REV. CHECK FAIL : fused 8, Binary :6"

(of course, the Binary change with the firmware)

Does it means that I need a newer firmware? What else can I do?

Thanks,

Jorge
[Verizon Samsung Galaxy S 4] jgastald:
I don't have much info about what was on the phone before. The problem got me unprepared, since I expected the Kies update to be trivial.

But this is what I get on the "Software Update Failed" screen:

ODIN MODE

PRODUCT NAME: SCH-I545

CURRENT BINARY: Samsung Official

SYSTEM STATUS: Official

REACTIVATION LOCK: Off

CSB-CONFIG-USB: 0x30

SECURE DOWNLOAD: ENABLE

WRITE PROTECTION: Enable

eMMC BURST MODE: Enable

Please, help me fix my phone.
[Verizon Samsung Galaxy S 4] Matthew M.:
Have you tried flashing the firmware which corresponds to Fuse: 8? (Lollipop OC1 or OF1)
[Verizon Samsung Galaxy S 4] jgastald:
Tried with OC1 and got "Fused : 8 binary : 7"

I'm downloading OF1 from here: http://xdaforums.com/galaxy-s4-verizon/general/of1-stock-tar-t3216417

(taking forever)
[Verizon Samsung Galaxy S 4] jgastald:
While downloading the previously mentioned OF1 (20 min left now...),

I tried with the I545_Downgrade_to_OC1.tar mentioned here:

http://xdaforums.com/galaxy-s4-verizon/general/how-to-update-to-i545of1-5-0-1-keeproot-t3182544

I got a good start flashing, but then I got:

<ID:0/003> Odin engine v(ID:3.1100)..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> SingleDownload.

<ID:0/003> boot.img

<ID:0/003> NAND Write Start!!

<ID:0/003> recovery.img

<ID:0/003> NON-HLOS.bin

<ID:0/003> modem.bin

<ID:0/003> system.img.ext4

<ID:0/003> FAIL! (Auth)

<ID:0/003>

<ID:0/003> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

and on the phone:

SYS. REV. CHECK FAIL: Refer 2 > Binary 1
[Verizon Samsung Galaxy S 4] jgastald:
SOLVED!

I had some problems flashing OF1, but then I used my notebook instead my PC, and worked!

For the record, I used the OF1 from here:

http://xdaforums.com/galaxy-s4-verizon/general/of1-stock-tar-t3216417

Thanks!!

Jorge
[Nexus 10 Q&A, Help & Troubleshooting] baruch6132:
So. The original battery in my N10 corroded. I have replaced it with a battery from my padfone x station. Thing is: both have 4 wires. N10 had 2 black, 2 red and 2 separated blue wires. The padfone x station had 2 red, 2 black, 1 white and one yellow. I have it plugged in as such: black to black, red to red, and the blue connectors lined up with the way the yellow and white ones are lined up. I'm curious as to what the two blue and the white and yellow wires do. Keep in mind: the tablet works. It turns on and charges the battery. Problem is, it says it's stuck at 42% even when the tablet dies completely because the battery has no power whatsoever to lower the tablet. When charging, it says 42% but I know it's not that amount but is still charging the tablet. I know his, because after I let it completely die and plugged it in with the LCD disconnected for 20 min, and then unplugged the charger and the LCD back in and powered it, it turned on fine, but still read 42%. Any thoughts and ideas would be helpful. Thanks.
[Galaxy Note II Q&A, Help & Troubleshooting] misthero:
Hello,

I'm a noob but usually try to fix this kind of issues on my own, looking at the boards, following tutorials, learning, but this time I think I'm not able to find a solution on my own so I'm asking for advice here.

Some time ago I installed cyanogenmod 10.1 on my Note 2 LTE and was happy with it for some month, than last week I tried to upgrade to cm12.1 It worked but there where some issues and bugs, mainly I wasn't able to swap internal/external sd cards.

So I decided to go back to latest available stock rom 4.4.2 from sammobile.

Here is where the problem starts. The stock 4.4.2 resulter in a bootloop, tried cache/dalvik/factory reset, flash again, whipe again.. nothing.

The phone is not able to get past the white label "Samsung Note 2 gt-n7105" screen. It goes black than the white label again and again.

It doesn't even get to the Samsung animated logo.

Ok bottloop, no problem, try to flash again something else.

I tried different Custom roms, different kernels, different flashing methods. I can flash anything with no problem but every time a get a bootloop.

During the various attempts knox fired, but I don't care. I don't know if this could be the cause.

Actually the only firmware that works is the original oldest STOCK 4.1.2, every other stock firmware past that or any custom rom is bootlooping the same way. To fix I only can reinstall stock 4.1.2 with odin.

I really need any advice or hint.

At the moment my goal is to get at least to stock 4.3 but I cant.........

Thanks!
[Galaxy Note II Q&A, Help & Troubleshooting] ErnestChia:
When you first bought your phone, did it come with Knox?
[Galaxy Note II Q&A, Help & Troubleshooting] misthero:
nope it doesn't existed before, but now I can see it when I boot in download mode "knox warranty void:1"
[Galaxy Note II Q&A, Help & Troubleshooting] mysuperdonghae:
Try to get the latest firmware available via kies ,that worked for me

http://xdaforums.com/showthread.php?t=2088809/[URL]
[Galaxy Note II Q&A, Help & Troubleshooting] ErnestChia:
From what you've described, I think the Stock ROM 4.4.2 from Sammobile contained a bootloader update. So when you flashed this ROM, it updated your bootloader from the non-Knox version to the Knox version.

I am very unfamiliar with the technical details of Knox, but I think the new Knox bootloader is causing your bootloop problem.

However, I don't know why 4.1.2 works when everything else doesn't work!

Can you check the Stock ROM 4.4.2, and see whether it really contains a bootloader update?
[Galaxy Note II Q&A, Help & Troubleshooting] ErnestChia:
Since a boot.img is present, it means that it would flash your boot partition. So now we know for sure that when you attempted to flash the Stock ROM 4.4.2, your bootloader was changed to the Knox version.

So the lesson here is: before you flash anything via ODIN, always check to see if there is a bootloader update. Usually you don't want to be changing the bootloader on your phone.

***

So now there are 2 possible ways to reach your goal:

1) Keep your new bootloader and see whether you can get Stock 4.3 or Stock 4.4.2 running on your phone

2) Try to restore your old bootloader

As I said earlier, I'm not familiar with the technical details of Knox, so I'm not sure how to get Stock 4.3 or Stock 4.4.2 running on your phone when your Knox indicator is already 0x1. You need someone else to help you.

And you can only restore your old bootloader if you happen to have made a copy of your boot partition before you flashed the Stock ROM 4.4.2. Even if you did have a copy of your original boot partition, I'm not confident with helping you to restore your old bootloader. You need someone else to help you in this case too.

Conclusion: I don't think I can help you to solve your problem :( I'm sorry. Hopefully someone else who is more of a pro than me will come along to help you out.

Good luck!
[Sable] motocrossmann:
Hi Fellas-

Has anyone seen information on how one might hack WPA2 support into a pre-AKU3 device? I'm thinking it may be possible to copy some DLL's and config files out of a newer ROM image and paste them into my hw6945 to get it to support WPA2. Any ideas?

BTW, I have tried using Juniper's Odyssey client v4.02 (included with the iPAQ), but that will not connect. Juniper has a newer version, but they want me to pay $50 to upgrade to v4.5 and even then there are no guarntees of it working.

PS... Good luck all on hacking WM6 support!!!!!
[Android Q&A, Help & Troubleshooting] Afik Cullen:
I have search and search for fix this issue but no one or no thread have the answer for this trouble,i have mukulsoni customrom grand 2 5.1.1 cm12.1 .when i try to move app to sdcard,,it succesfully moved but still in internal storage,not sdcard1(external memory)

But when i found an app that can fix this

I try to install nextApp sdFix (search in playstore),,it says this app for kitkat rom,but when i try,,its solve my problem,,and now i can move app to sd card

Thanks for the developer

If you have the same problem,then try

I hope it helped
[Samsung Galaxy Fresh/Trend Themes, Apps, and Mods] xenreon:
Hi guys,

So today I'm here with a completely unthemed ui mod for trend.... I only modded it with grid lidroid 23 toggles and xperia z2 tabs.... The looks are all same as stock, didn't touched any png.... People who likes the stock theme may like it

Features:

1. Xperia z2 tabs

2. Grid lidroid 23 toggles

3. Transparent status bar

Requirements:

1. Root

2. CWM/TWRP/PHILZ installed

3. A good file manager

How to install:

1. Copy/cut "mega-stock ui s7392.zip" to internal/external sd card (depends on your recovery)

2. Go to system/app and delete SystemUI.odex

3. Go to recovery mode (cwm/twrp/philz must be installed)

4. Flash "mega-stock ui s7392.zip"

5. Reboot and enjoy

Link:

https://www.androidfilehost.com/?fid=673368273298942886

Credits:

[MENTION=3862405]SpaceCaker[/MENTION]

[MENTION=4054594]lidroid[/MENTION]

[MENTION=3562083]wanam[/MENTION]

[MENTION=5243661]dugeriss[/MENTION]
[Samsung Galaxy Fresh/Trend Themes, Apps, and Mods] 1234himanshu:
nice work ?
[Samsung Galaxy Fresh/Trend Themes, Apps, and Mods] Andrei Radu:
Aswome!!!
[Samsung Galaxy Fresh/Trend Themes, Apps, and Mods] lomitaswa:
Awesome...i really liked this one..:):):)
[Samsung Galaxy Fresh/Trend Themes, Apps, and Mods] silva89:
good stuff
[Device Reviews and Information] FumiJ:
I heard the news about Doogee X6 PRO, which is powered by mtk6735 quad core 64bit processor.

It attracts me about the cheap price to beat those mtk6735 quad core smartphones.

And last time we have aloso discussed Uhans u100 smrtphone, but it seems Doogee X6 PRO

will be much more competitive, i haven't got the real photo, so anyone can tell me which is better.

Doogee X6 pro or xiaomi redmi 2A ram 2gb version, which will be sold in single's day, 11.11?

Check Doogee X6 PRO main features:

5.5" HD 1280*720 IPS, Capacitive touch screen

MT6735 quad core CPU,1.0GHz

Android 5.1 OS, 2GB RAM 16GB ROM

Dual Cameras, front camera 2.0MP(SW5.0MP), back camera 5.0MP(SW8.0MP)

Dual SIM Card Dual Standby

Support 3G/WIFI/Bluetooth/Multi-language

2G:GSM850/900/1800/1900MHz; 3G:WCDMA900/2100MHz; 4G:FDD-LTE800/1800/2100/2600

I guess Doogee X6 pro just has 3G 900/2100MHZ, not all the band, which is very limited in some country,

but it can be used in Europe, anyone has made the review about it?
[Device Reviews and Information] pittss1c:
according to this site, yes

http://willmyphonework.net/
[Device Reviews and Information] AndroidPhoneEnthusiast:
DOOGEE X6 Pro supports 95% of all bands and all Gs

I own a copy of this phone and have personally checked the Amazon page where it says what bands and Gs it supports and it seems to support 95% of all cellular network bands, meaning that even if you are in a place with low G cellular networks and low band range, the DOOGEE X6 Pro will still be compatible with it. Also, you are probably getting the specification list from eBay, where the sellers list the vague information at the top and the detailed info at the bottom where their HTML-coded store section is.
[Nexus 5X Q&A, Help & Troubleshooting] jackdubl:
Wanted to just stay on the stock releases. Is there an easy way to flash them without wiping storage? I'm used to flashing everything in recovery, not used to getting stuff straight from Google.
[Nexus 5X Q&A, Help & Troubleshooting] zepeters:
You can follow this guide for the original N5: http://xdaforums.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701

Follow method 2 but make sure you

SKIP

this step:

Flashing userdata.img overwrites your personal data and writes the stock one. Also, don't "Wipe data/factory data reset"

Should do the trick ;) Also, be aware that flashing the boot.img and recovery.img will break root and flash the stock recovery. You'll have to manually flash a custom recovery and re-root :good:
[Nexus 5X Q&A, Help & Troubleshooting] kbbeer:
If you already have root and twrp can you skip flashing the boot and recovery img?
[Nexus 5X Q&A, Help & Troubleshooting] zepeters:
Not sure about that, I'd have to test it first. But I think twrp is version specific, so instead of flashing the stock recovery you can just flash the correct twrp version for the android version you're upgrading to. As for the boot.img, since rooting in marshmallow involves messing with the boot.img itself, I don't think it will work.

Again, this is me thinking out loud. I'd have to test it in order to give you a certain answer on this.
[Nexus 5X Q&A, Help & Troubleshooting] itzweber:
Basically this I believe. Make sure to flash vendor.img too though, or you will get some errors on boot. And ensure the rooted boot.img is compatible with the latest Nexus image via Chainfire's thread. So assuming it is, and recovery is as well:

fastboot flash system system.img

fastboot flash vendor vendor.img

fastboot flash cache cache.img

Tried with the latest Nexus image, and all seems well. Cheers

Edit: Don't forget to re-flash SuperSU in twrp if you are not using the systemless root
[Nexus 5X Q&A, Help & Troubleshooting] kbbeer:
Cool, so just flash those three, then I'm guessing reboot ensure everything is working and reboot to recovery and flash supersu again.
[Nexus 5X Q&A, Help & Troubleshooting] zepeters:
What exactly is vendor.img? I don't think I ever flashed this file... not it is present in the factory images :eek:

EDIT: I've seen it in some flashing guides but it was only related to tablets somehow...
[Nexus 5X Q&A, Help & Troubleshooting] metpage:
vendor.img is new in 6.0 i believe that contain vendor proprietary info.

you also don't need to flash cache.img either (i never do and it have yet to experience any problems).
[Nexus 5X Q&A, Help & Troubleshooting] wpbear:
So assuming the boot.img, radio.img, and recovery.img is still compatible with the newer version...all you must flash is system.img and vendor.img, SuperSU.zip, wipe cache/dalvic in TWRP when upgrading these minor updates. Making a custom zip to do this in TWRP would be the easiest way.
[Nexus 5X Q&A, Help & Troubleshooting] kbbeer:
Everything seems to be working! Here is what I did to summarize -

I was on MDB08I and had twrp and root working properly. I downloaded the factory images for MDB08L and MDB08M, extracted until I had the img files.

fastboot flash system system.img

fastboot flash vendor vendor.img

fastboot flash cache cache.img

wipe cache/dalvic in TWRP

rebooted

flashed SuperSu in recovery

Done!

Did this first for L then repeated for M.
[Nexus 5X Q&A, Help & Troubleshooting] Infekxion:
Followed those steps except flashing Superuser, (I use systemless) data, root, and Elemental kernel are still in tact.

Sent from my Nexus 5X
[Nexus 5X Q&A, Help & Troubleshooting] neuroval:
Why did you do this for L and then for M? I am currently on MDB08I and was planning to flash system.img and vendor.img for M, skipping L. Then flash Supersu in TWRP. Would this work for me to be on the newest update and keep root?
[Nexus 5X Q&A, Help & Troubleshooting] Infekxion:
I was on "I" and flashed the .imgs for M and everything went well so it should work for you.

Sent from my Nexus 5X
[Nexus 5X Q&A, Help & Troubleshooting] kbbeer:
Another thread mentioned doing it in order so I was just being cautious. In reality only takes 5 more minutes to flash both. System didn't go through refreshing all apps after the L security update.
[Nexus 5X Q&A, Help & Troubleshooting] Mountainfisher:
i followed the steps above as well but went straight from i to m. everything works fine
[Nexus 5X Q&A, Help & Troubleshooting] neuroval:
Just went from I to M and everything seems to be working :)
[Nexus 5X Q&A, Help & Troubleshooting] dave2775:
Do we have to reflash modified boot image with this method?
[Nexus 5X Q&A, Help & Troubleshooting] Infekxion:
I didnt.

Sent from my SM-G920F
[Nexus 5X Q&A, Help & Troubleshooting] kbbeer:
Same here, only reflashed the original modified i img. During the first root.
[Nexus 5X Q&A, Help & Troubleshooting] Moonie17:
Did this straight from I to M and worked a treat, thanks!
[Nexus 5X Q&A, Help & Troubleshooting] ravichopra:
Anyone else notice a long reboot time after updating?

Went from i to m. Have been staring at this boot animation for 20 mins or so...
[Nexus 5X Q&A, Help & Troubleshooting] BlueZinc:
I just tried this method to update my rooted unencrypted stock Nexus 5x and it worked perfectly without loss of personal data.
[Nexus 5X Q&A, Help & Troubleshooting] solara1973:
There should be no reason to flash the L version, followed by the M. That only applies when you are doing OTA updates that only include specific changes for each update. When flashing the complete M firmware that you download directly from Google, that is the complete system image and includes all the changes to that point.

Flashing system.img from L and then from M is just wasting time and nand writes.

I'm also curious as to why cache.img was flashed, and then immediately cache is wiped using twrp?

Update: Just flashed the mdb08m system.img, vendor.img, and radio.img (I wasn't getting Band 12 on TMobile on the original "e" radio.img, but instead HSPA, so decided to stick to stock in case there are other changes that can improve Fi cellular switching, etc). Also flashed the modified boot.img for mdb08m build found in another thread. Booted to TWRP, flashed SuperSu beta 2.52. Also flashed the Nav button swap, and the center time mods. Everything working the same as previous.
[Nexus 5X Q&A, Help & Troubleshooting] Jexx11:
Are you still encrypted or did you decrypt? Just curious if it makes any difference when updating the way you have.
[Nexus 5X Q&A, Help & Troubleshooting] solara1973:
I decrypted it with the "i" build using chainfire's modified boot.img originally. I remain decrypted using the newer modified boot.img from the "m" build (though the "i" version reportedly still works).

If you flash the latest stock boot.img (which i did not do), and then boot into the system, it will force encryption most likely. I doubt you'd lose your personal data when it starts to encrypt everything. But if you then go and flash the modified boot.img to prevent encryption, you'd have to format your personal data to remove encryption then.
[Nexus 5X Q&A, Help & Troubleshooting] BlueZinc:
Can we still use this method for the 6.01 update?
[Nexus 5X Q&A, Help & Troubleshooting] metpage:
yes, this method does not change no matter what version you are using.
[Nexus 5X Q&A, Help & Troubleshooting] BlueZinc:
Actually, the camera does not work if you follow this method. You must use the modified mmb29k bootimage for 6.01.

Flash bootloader
Reboot bootloader
Flash radio
Flash vendor
Flash system
[B]Flash modified mmb29k boot image[/B]
Reboot into recovery
Flash SuperSU-2.52
Wipe cache and dalvik (optional)
REBOOT
[Nexus 5X Q&A, Help & Troubleshooting] jackdubl:
That will probably be the case with each version. You'll need to flash the newest modified boot.img for whatever version you're updating to. It's just that sometimes the previous boot.img will still work on the latest version.
[Nexus 5X Q&A, Help & Troubleshooting] ivan.chh88:
This worked for me. Followed everything but I didn't wipe cache at the end. Thank you.
[XDA Assist] Lilmonster79:
I have a stock att SM-G900A S5 that is updated to 5.1.1 . From my understanding their is no root for this so far. So far I'm pleased with the update as its seems to be running a smoother and less loading time. For my taste there are absolutely to many irrelevant apps that I will never use. What can I do to get rid of some these and more importantly if I can do away with some of them, how will that affect my S5? I mainly use it at home as a Hotspot because I live in the swamps and our only option for Internet is satelite.
[XDA Assist] Calin:
Hi and thank you for using XDA Assist :)

If you're on LP then there is no Root method for this variant of the Galaxy S5

Regards
[Galaxy Note 4 Q&A, Help & Troubleshooting] mjrshark:
When I listen to any audio from whatsapp or any player and using bluetooth headset , bluetooth will turn off then on , I've search around and didnt find solution.

Even changed kernel , cleared bluetoot data/cache and still the same.

Am using rom erobot v9 , kernel spacex.
[Galaxy Note 4 Q&A, Help & Troubleshooting] GrippingSphere:
Try stock rom. I don't experience any Bluetooth problem with it.
[Galaxy Note 4 Q&A, Help & Troubleshooting] safzath:
Same happens to me,

Have you found the solution ???
[Galaxy Note 4 Q&A, Help & Troubleshooting] jacekw23:
I have the same problem on every 5.1.1 Rom. On 5.0.1 and 4.4.4 was ok. It happens when Bluetooth and WiFi are on at the same time. So I can't stream audio (e.g. spotify) to bluetooth devices.
[Galaxy Note 4 Q&A, Help & Troubleshooting] mjrshark:
nop , tried many kernels and roms , all are same
[Galaxy Note 4 Q&A, Help & Troubleshooting] safzath:
I eagerly need the solution for this issue.

I also tried several roms and kernels..

Still exists.:thumbdown:
[Galaxy Note 4 Q&A, Help & Troubleshooting] mjrshark:
up maybe someone got fix