yashsingh1/xdaforums huggingface dataset:
[Galaxy S5 Mini Q&A, Help & Troubleshooting] mophets:
Hello? anyone ?

Finaly i dropped the s5 mini idea. I'm as interested in the waterproof capability as in the USB audio feature. And i'm not that into tweaking the phone without knowing the exact consequences. I ordered the xperia z1 compact, which seems to have all the pros i'm looking for without the cons (maybe a bit more expensive though).

Thanks for your help.

In France, the talking to somebody with no answer, and finding the solution, we name it the "duck theory". I've got my solution, thanks for being my duck.

Steph
[Galaxy S5 Mini Q&A, Help & Troubleshooting] jukl:
please open otg ? for 2015-08-12	Czech Republic	4.4.2	G800FXXU1AOG2	G800FOXX1AOG1

thx all
[Android General] zezein:
Please Devs made some custom roms for canvas gold A300 its a powerful phone and i think we all owners of canvas gold looking for custom roms
[Android General] latex82:
lolipop

have you tried one from this addres?

levelof.blogspot.com/2014/10/upgradeupdate-micromax-a300-canvas-gold.html
[Android General] reshu179:
Lollipop ROM or CM based ROM?

Did u find any better or stable ROM for Micromax canvas gold A300

Lollipop ROM or CM based ROM? Thanks in advance..
[Android General] emmanuelmmxa300:
High developers this is a lovely device

Please please

Spare little time to make a nightly version of cyanogen mod for this device

Please no website on wwwhas this device custom roms

And the miui rom on xda doesn't get installed with twrp plzzzzzz help
[XDA Assist] basilico:
Hello everyone, I just joined and I do not know if placed in the right forum.

I have a cell phone samsung gt-s6802 which installed as the gingerbread firmware v2.3.6 and it seems to me that you can not update it with the latest versions of Android. no way to do something?

thanks
[XDA Assist] Razvan:
Hi there,

I'm sorry but I founded only one custom ROM for your device. Please read carefully and proceed only if you are sure and have a backup:

CUSTOM ROM FOR ACE DUOS s6802 [RELEASED ]

CustomDroid ROM For Ace Duos s6802 [NEXT VERSION 2.0 Released]

Good luck
[G 2014 Q&A, Help & Troubleshooting] sandy1636:
I just unrooted my moto g xt1068 and flashed stock rom. But for some reasons i am unable to relock the bootloader. Just want to know that will I be able to receive OTA updates even when the bootloader is unlocked or should i have to relock the bootloader?
[G 2014 Q&A, Help & Troubleshooting] sandy1636:
why nobody answered my questions yet?:( Plz reply soon
[G 2014 Q&A, Help & Troubleshooting] NWKENT:
Unlocked bootloader, doesn't matter with updates, or system flash..only when one needs Root, then the bootloader needs unlocked, unless a Root exploit is used..

sent by my

5.0_22.11.6 Lollipop (Rooted)

TWRP v2.8.0.1-titan

UPDATE-SuperSU-v2.16

XT1064 Moto G (2nd Gen.)

http://waynekent.com/page6.html

"Praise Jah" YOU people.!
[G 2014 Q&A, Help & Troubleshooting] KrishnaSagar:
Try this:

Flash Stock firmware using these commands in this order:

[B]mfastboot.exe oem lock begin[/B]
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
[B]mfastboot.exe oem lock[/B]
mfastboot.exe reboot

Hope this helps :)
[G 2014 Q&A, Help & Troubleshooting] sandy1636:
i have already entered all these commands and successfully flashed stock rom. But when i enter mfastboot.exe oem lock, its shows as (bootloader) sst lock failure.
[G 2014 Q&A, Help & Troubleshooting] KrishnaSagar:
That is the standard procedure, but if you are getting errors then please refer to this thread:

http://xdaforums.com/moto-g-2014/general/guide-explaining-boot-loader-locking-t2933827
[G 2014 Q&A, Help & Troubleshooting] sandy1636:
I have followed the exact steps as mentioned in this thread. But still unable to relock the bootloader.

But I read somewhere that i can still get OTA updates even if bootloader is unlocked as long as i am in stock firmware and recovery﻿. Is that true?
[G 2014 Q&A, Help & Troubleshooting] KrishnaSagar:
Yes. OTA updates are available on Unlocked Bootloader as long as you dont Root or change the recovery.
[G 2014 Q&A, Help & Troubleshooting] grayme:
Thread hijack: If you have an unlocked bootloader and rooted xt1068 (and using Philz kernel) on the stock ROM, can you expect to get the OTA update?

I'm finding conflicting responses to this on searching and if I need to go back to stock recovery would happily do that, but I don't want to wipe my device.
[G 2014 Q&A, Help & Troubleshooting] rufflove:
We shall see when the OTA is pushed to blighty. My advice would be to backup the boot, recovery and system partitions in their factory state before tinkering. I just rooted the stock ROM by booting from a TWRP image via fastboot, installed SuperSU and then used dd to image /boot, /recovery and /system to an external SD. If the OTA fails due to me having installed Xposed and removed system apps, I'll just restore the /system image and remove SuperSU... A wipe of the /data partition shouldn't be required.

If the OTA fails for you, I'd suggest flashing back the stock boot, recovery, and system images from the stock retgb firmware zip using fastboot and then trying the OTA upgrade process again.
[G 2014 Q&A, Help & Troubleshooting] grayme:
It's probably a bit late for me to use dd before I installed Xposed. Thankfully I did back up using CWM before I wiped in installing Lollipop from a thread on here. I think I'll just wait till Motorola decides to push OTA over here.
[G 2014 Q&A, Help & Troubleshooting] rufflove:
Aye, but you should be able to flash back the stock system image from the 4.4.4 release using Motorola's fastboot. I dunno if the standard fastboot or any of custom recovery distros support sparse images. There must also be some way of converting the partial, sparse files into a normal image, too... I guess the questions is whether it's more of faff to start from a formatted data partition, or not.
[G 2014 Q&A, Help & Troubleshooting] grayme:
I used to understand these phones, but everything just seems so much more complicated these days!

I'm getting old. :(
[Android Q&A, Help & Troubleshooting] sr18:
I have succesfully rooted and unlocked my Xperia U, but am having trouble again reinstalling to original rom. I connect the phone in flashmode, drivers are correctly installed, correct firmware downloaded from XDA. I always get the following errors:

10/042/2014 13:42:30 - ERROR - (X10flash.java:405) - Error in processHeader : 22 : The device does not recognize the command.

10/042/2014 13:42:30 - ERROR - (X10flash.java:405) - Error flashing. Aborted

pls give me some tips to get rid of it
[T-Mobile HTC One (M7)] QA Bot:
Q&A for [ROM] [OFFICIAL] Dirty Unicorns 4.4,M7-TMO[04/23/14]v7.0

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [ROM] [OFFICIAL] Dirty Unicorns 4.4,M7-TMO[04/23/14]v7.0. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[T-Mobile HTC One (M7)] Impacter1991:
link

Hello guys.

Can someone tell me why the link dont working? Or where can i download Dirty Unicorns 4.4 rom for HTC M7

Thanks
[8125, K-JAM, P4300, MDA Vario General] HuddaDudda:
I have a 8125 and I was able to unlock it fine. After unlocking it I upgraded to the underground crossbow edition rom - which the 8125 rebooted and was running. I tried out a couple things and everything seemed to be running/working fine. It was getting late so I put it down and went to bed. This morning when I got up the phone was off so I went to turn it on and nothing happened. I figured it just ran out of battery power plugged in the charger and guess what no red light on. I have tried everything under the sun but I cant get it to charge or startup. Anyone have any ideas? It was working fine.
[8125, K-JAM, P4300, MDA Vario General] mrhighoctane:
i know u said u've tried everything and i don't mean to sound like i'm takin the buscuit, but leave it on charge for n hour, then try bootloader. taking the battery out completely for a while could work.

i had so many problems with crossbow! think this was one of them.
[8125, K-JAM, P4300, MDA Vario General] HuddaDudda:
Unplugged

Well so far I left the charger plugged into the phone with the battery in it for over an hour now - with no luck. The red charging light doesn't even come on. Did you have that problem? I also left the battery out and plugged in - still nothing. Tried taking the battery out and then putting it back in while plugged in - no go.

I have not tried the "bootloader" - but the phone will not turn on at all or respond in anyway. Its in a powered down state (or so it seems) - I dont think bootloader will work?? But I dont know anything about bootloader - is it on the ftp site and how do I use it?
[8125, K-JAM, P4300, MDA Vario General] bwesty:
Any chance the battery could have been completely discharged?..just a thought. I think i read that completely flat batteries wont charge up via usb. Disregard if thats a silly suggestion, just thought id offer my two cents.
[8125, K-JAM, P4300, MDA Vario General] Malik05:
try getting a new battery and see if it boots up...it can be your battery.and you are trying to charge with an AC adapter right?
[8125, K-JAM, P4300, MDA Vario General] HuddaDudda:
Wall Charger

I am charing it via the wall charger (not usb) and I am going to try to get another battery. Just weird that I never had a battery problem until I install the wm6??!! Unless the damn thing drained my battery dry and somehow damaged the battery. I called Cingular and they are sending me another unit as its still in warranty. So we'll see when I get it - I will try the new battery. Strange. Very Strange - because everything was working last night.
[8125, K-JAM, P4300, MDA Vario General] HuddaDudda:
Strange

Well after leaving the battery out all afternoon I took a go at the phone again, put in the battery then turned it on. It actually started booting up - showing the WM6 bootscreen. After about a minute it shut down like it was out of power. Strange. I know the phone is not bricked because if it was it wouldn't have just done what it did. Anyone have any suggestions how to fix it?
[8125, K-JAM, P4300, MDA Vario General] SL:
Could be a bad battery. You need to test out with some one else battery
[8125, K-JAM, P4300, MDA Vario General] Malik05:
u shud have plugged it in while it was booting...did u?
[8125, K-JAM, P4300, MDA Vario General] HuddaDudda:
New Battery

Well I finally got the new battery I ordered today. When I put it into my phone it will boot into wm6 fine but will not sync with activesync 4.0 or charge via USB or plugged into the wall. I uninstalled activesync, rebooted my computer and installed Activesync 4.5 - but still no luck with the phone via usb syncing with my pc. Also when the phone in plugged into the wall via the wall charger it does not charge. I am beginning to think the port on the bottom somehow was disabled from the rom update, although I dont see any posts with people having that problem. I guess my next option is trying to reflash it to stock rom via a sd card since it wont connect via USB - however I can not find the information step by step how to do this. Can someone point me in the right direction?
[8125, K-JAM, P4300, MDA Vario General] mfrazzz:
Try going to the bootloader screen: Turn off your phone and then hold the camera button while you turn it on. When you are at the Rainbow screen (thats the bootloader) plug in your USB cord. You should see in the bottom left (above the left soft key) where it says USB. If it doesn't then I'd say your USB port is broken (I'm not aware of any ROM being able to disable that).

As for flashing from the SD card, I believe thats documented in the Wiki...
[One (M7) General] ABQNM:
Since HTC forgot to include the button backlight for the capacitive keys, there is a way to enable them, if you have root. I do not take credit for the app, I just happened to realize it works to enable the keys when I was telling another user about it who wanted to disable the backlight on a Sense ROM. I personally don't use the capacitive keys and use the onscreen nav bar, so I hadn't worried about them, but I just discovered this worked by accident.

Install the following app, grant root permission, and select either bright, dim or off and there is a set at boot option in the overflow menu/settings. The lights shut off with the screen. It isn't the perfect fix, but it will give you backlight on capacitive keys until HTC releases an update.

https://play.google.com/store/apps/details?id=org.sleepydragon.capbutnbrightness

Again, this is not my app, and if you want to support the developer, purchase the paid app from the Play Store.

Paid version: ($2 US) https://play.google.com/store/apps/details?id=org.sleepydragon.capbutnbrightness.pro

Developer's xda thread: http://xdaforums.com/showthread.php?t=2496347

Also, thanks to [MENTION=5482622]dragonballz2k[/MENTION] for pointing this out, you have to change the SELinux status to permissive using the following app in order for the permissions to be writable. https://play.google.com/store/apps/details?id=com.mrbimc.selinux

Just install the app, grant superuser permission, tap the "Permissive" button and reboot. Just leave the app installed. It will do its thing in the background automatically. (Note: this is not necessary if you are using ElementalX kernel as it already sets the SELinux status to permissive in the kernel.)

As always, any modifications to your device's software are at your own risk. Do not blame anyone but yourself if you break something. Not even your dog. He doesn't deserve it. And if he eats your friend's iPhone, let him sleep on the couch. He is a good dog.

Sent from my brain using human to phone transport technology.
[One (M7) General] ABQNM:
Second post because it is the cool thing to do.

Sent from my brain using human to phone transport technology.
[One (M7) General] D€INOS:
Didn't work, granted root permission through SuperSU, but the debug log shows files to be modified to be read-only
[One (M7) General] ABQNM:
Maybe it works because I am running a custom kernel, ElementalX 19.0. It is possible that it has changed the permissions of the necessary files.

Sent from my brain using human to phone transport technology.
[One (M7) General] D€INOS:
nope, i use ElementalX 19.0 too :p
[One (M7) General] ABQNM:
So if you tap the bottom (full sun) button in the app it doesn't light up the keys? The debug info shows as read only for me as well, but it lights up immediately for me.

On: http://imgur.com/HdZcSoY

Off: http://imgur.com/TnELt0E

Sent from my brain using human to phone transport technology.
[One (M7) General] D€INOS:
no I get a pop-up with an error message, efter that i looked at the log and since it showed read-only is assumed that was the issue, but maybe it's not.
[One (M7) General] ABQNM:
Maybe try revoking su permission and then accepting the supersu permission again when it prompts. If not, I'm not sure what the issue could be. I didn't write the app and it seemed to work fine for me, but there is a lot of craziness going on with sysfs security permissions and Lollipop on the m7 and m8. Flar2 (ElementalX dev) is having issues getting a lot of his custom features working properly because of this, but it seems to randomly affect some people and not others. Also make sure you have a current version of busybox.

Sent from my brain using human to phone transport technology.
[One (M7) General] dragonballz2k:
Figured it out is it is selinux use this app to fix the issue https://play.google.com/store/apps/details?id=com.mrbimc.selinux&hl=en
[One (M7) General] ABQNM:
Oh man. That is it. I completely forgot I had that installed. I had it running for my sound mod and forgot about it. I guess it does other things. Thanks! I will update OP.

Sent from my brain using human to phone transport technology.
[One (M7) General] D€INOS:
Thanks , that solved it for me as well. Does enabling permissive disturb any other apps you have with root access?
[One (M7) General] ABQNM:
It may actually make some work better. It may actually make some of the ElementalX kernel features work. I have had it installed since last Friday when I installed Project ERA (sound mod) and forgot about it and everything has been running great. In fact, things are working for me that others cannot get to work, even the kernel developer, flar2.

I have actually been talking to him about SELinux status and sysfs permissions in trying to fix some of the extra kernel features.

You just lose the protections afforded by SELinux enforced permissions that prevent other apps from modifying system files. Though KK 4.4.4 GPe did not have SELinux enforced. It was still permissive.

Sent from my brain using human to phone transport technology.
[One (M7) General] D€INOS:
Thanks for the info, good to know as I been using ElementalX for a long time and it's an awesome kernel.

All you developer are awesome actually, I feel less need every day to buy another Android phone since apart from the m7 bloody annoying buttons for volume and power, with super creations like ElementalX and hopefully in the near future xposed & gravitybox the M7 is a excellent phone. Although with 5.0.1, I really miss long press volume to change track with Gravitybox...
[One (M7) General] ABQNM:
Yeah I miss xposed for a few features, but not enough to go back to the laggy, battery hungry mess that was Kit Kat on the M7. I have already learned to live without it.

As for the volume key to change tracks, there are a few apps. I use this one. It works with Google Play Music, (and it says Power Amp and stock music players, but I don't use those so I can't test them). I can't get it working on Spotify or Rdio, even using the compatiblity modes. It doesn't use long press, but rather a double press of the volume up or down keys, but it is at least something. It doesn't use any extra battery since it only runs when music is playing and the screen is off. https://play.google.com/store/apps/details?id=com.silentlexx.volbtntrackctrl

Sent from my brain using human to phone transport technology.
[One (M7) General] D€INOS:
Yeah I use PocketSkip too, used it even in KK too a long time ago before i used GravityBox. PocketSkip is annoying because double press in more difficult in the pocket (with m7 awful volume rocker...) than a long press. Even more annoying is the sudden increase in volume before it change tracks. I mapped volume down in PocketSkip instead for the next song, more easy on the ear to hear a sudden drop in volume than an increase. I've e-mail and asked the author of any plans for long press and/or fixing the increase or drop in volume before skipping, but no response.
[One (M7) General] Hitch3n:
i will get it a try
[One (M7) General] ABQNM:
If you are running ElementalX kernel you don't need the selinux app as the kernel has already changed the status to permissive. I don't know about other kernels however.
[Sony Xperia T2 Ultra] the_prodigal_coder:
I ran a Deodexing script and the camera didnt work... I messed something up... So can someone please upload the stock camera apk from D5322 4.4.3 ?
[Sony Xperia T2 Ultra] Sun24664:
Stock Camera App 4.4.3 T2 Ultra

Take it

Link :- http://d-h.st/oAu

System. >Priv app>paste>set permission >to 644> rw_r_r
[Sony Xperia T2 Ultra] Sun24664:
Stock Camera App 4.4.3 T2 Ultra

Take it

System. >Priv app>paste>set permission >to 644> rw_r_r
[Nexus 7 (2013) Q&A] LexGr:
Hi everyone!

I have a problem with the OTA update of 5.0.1. I looked at some other threads that also talked about update problems, but those were different errors.

My Nexus 7 2013 (Wifi) is currently running 5.0, unrooted but unlocked.

The error is telling me:

Finding update package...

Opening update package...

Verifying update package...

Installing update...

Verifying current sytem

Not enough free space on /system to apply patches.

E: Error in @/cache/recovery/block.map

(Status 7)

I tried sideloading the update with Nexus Root Toolkit, but that had the same error.

Does anyone know what to do? I still have 5GB of free space left, but maybe not in system, I don't know.

Thanks in advance!
[Nexus 7 (2013) Q&A] newkydawg:
I was on 5.0 rooted with TWRP and got an error trying to take the OTA. So I downloaded the rooted rom from Scrosler found here http://xdaforums.com/nexus-7-2013/development/rom-factory-stock-rooted-rom-lrx22c-t2960745 , used Wugfresh's NRT 1.9.9 to update the bootloader listed in Scrosler's post, and then dirty flashed (no wipes) the 5.0.1 rom with TWRP. Painless and fast with no loss of data or anything.
[Nexus 7 (2013) Q&A] LexGr:
I get a 'page not found' error, but I will try your method! Thanks for helping, will let you know if it worked!
[Nexus 7 (2013) Q&A] Rugal:
Just wipe cache and start again.. it will installs without problems..
[Nexus 7 (2013) Q&A] LexGr:
Thanks, this worked perfectly!
[Nexus 7 (2013) Q&A] Telyx:
Worked perfectly on mine running 4.4.4, too. (I wiped cache and Dalvik before and after the flash, though, just for giggles. No idea if that made any difference.)
[Nexus 7 (2013) Q&A] Lordificated:
:good:
[T-Mobile, Samsung Galaxy SIII] rythym05392:
Hi,

I have just ported from AT&T to T-mobile. Upon porting, I was hoping that once I get a T-mobile enhanced Sim card, my Softcard (ISIS wallet) should work in my unlocked AT&T galaxy s3 phone. But no luck.

My first challenge was to get the T-mobile version of softcard from the play store. Reading through some post I found changing the following properties should make my device reflect as a T-mobile device. In my case with the Galaxy s3 (I747) , I have changed the below properties in build.prop file to mimic a T-mobile model galaxy s3.

build.prop values for t-mobile SGH-T999

ro.product.model=SGH-T999

ro.product.name=d2tmo

ro.product.device=d2tmo

I then also unrooted my phone, as softcard has a restriction that it will not work on rooted phones. But even after doing all this, on launching the T-mobile Softcard app, I get a message "To use softcard, your phone needs a different SIM card". This is despite of having the T-mobile enhanced SIM card. I am tired of searching on how I can make this work.

Your advise in helping me through this is much appreciated.
[T-Mobile, Samsung Galaxy SIII] Darth:
Hi,

I will have your thread moved to your device section.

Good luck!
[LG Optimus G Pro] abumy:
I am here looking for the same thing. Actually, on other devices a factory reset via stock recovery can fix it. I have thought this might help here with the og g pro.

For me, my device is refusing to show under the com port section in Windows device manager. My idea on a fix is to flash stock, factory reset, re-root etc, and then flash a nandroid. Except for the com port issue....

Anyone have an easier way or a solution to the com port thing? (running Windows 7 in virtualbox on ubuntu).