yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] Pramod9964:
Guys ,i wanted a suggestion of apps for the the following scenario

i want an app which would detect my phone in my windows pc as a drive where in could treat my phone as any other drive,where data transfers happen via local INTRANET,i dont want any authentication to be present between,if my phone and pc are on same wifi, the phone should be enabled as a drive, i know its too much ,but just asking if at all if we have an app like this

p.s:airdroid sorta does this,but not exactly this
[General Questions and Answers] ryanallaire:
There's an app called wondershare by mobile go, it says it can transfer apps, pics, etc. and data between phones. I tried it with my s3, and an off brand tablet, it recognized the s3 but not the tablet so i haven't used it yet. Try it out..
[General Questions and Answers] ishaang:
You can use Samba Filesharing to map the SD card - https://play.google.com/store/apps/details?id=com.funkyfresh.samba&hl=en

And I read somewhere about File Expert - https://play.google.com/store/apps/details?id=xcxin.filexpert&hl=en
[iPAQ rw6828, XDA Atom General] Yurochka:
Does smb testing it?
[iPAQ rw6828, XDA Atom General] bedav:
interesting question !
[iPAQ rw6828, XDA Atom General] kjskho1:
u can read thru the data sheet or white paper, i dun think it is supported in any current device... hope i m wrong :)
[iPAQ rw6828, XDA Atom General] twitty1437:
Actually i'm also thinking of buying a 4GB miniSD card, but it's using the new SD 2.0 standard. So i doubt our PDA supports it
[iPAQ rw6828, XDA Atom General] airone:
It's not compatible.I've tested 4GB miniSD on my HP iPAQ rw6815 and there is no way.Can't detect!
[iPAQ rw6828, XDA Atom General] d1eter:
what about a 2GB miniSD high-speed (80x), compatible or not?

thank you.
[iPAQ rw6828, XDA Atom General] aeronic:
depends on the brand I guess. I have heard of few people using the newer high speed 2GB miniSD cards on Atom with no problems.
[iPAQ rw6828, XDA Atom General] d1eter:
Transcend 2GB miniSD 80x
[iPAQ rw6828, XDA Atom General] Knightro:
I'm using it for the past 5 mos with no problem on my Atom.
[iPAQ rw6828, XDA Atom General] davidw89:
Is there a firmware upgrade that will make it work? DO i have to format it or something..and i dont even know where i can buy these :/
[iPAQ rw6828, XDA Atom General] d1eter:
thanx for the comfirmation, ordering it now.. :D
[General Questions and Answers] 8ttype4:
Hypothetically speaking, if you were to take a 4G LTE SIM card out of a Verizon tablet that has a dedicated tablet data plan and place that card in a Verizon smartphone, would said smartphone be limited to only 4G LTE data, or would it also have access to 3G/2G/1x as well?

Please no guesses or assumptions- just need to know if the data received on the device is based on the sim card or on internal radios for Verizon.

Thanks!
[General Questions and Answers] 8ttype4:
bump
[Moto X Q&A] Megatron007:
It will be great ..if anyone can compile mahdi rom for moto x...mahdi rom has all features , tweaks and battery performance ..can anyone compile it..i am buzy for some days so i cant compile it :/
[X 2014 General] Vultorus:
As discovered in the Q&A post found here: http://xdaforums.com/moto-x-2014/help/root-t2886674/page2

Just like the first Moto X, users have been having success rooting by unlocking the bootloader and just flashing SuperSU with CWM. This is a test release so it may be wise just just boot to CWM to flash SuperSU instead of flash it. Use caution as always.

Bootloader Unlock Guide: http://xdaforums.com/moto-x-2014/general/guide-unlock-bootloader-moto-x-2014-t2876773

CWM Test 8: http://d-h.st/XJr

SuperSU flashable ZIP: http://xdaforums.com/showthread.php?t=1538053

I can report that this did work for me and I have achieved root.

Steps I took:

1. Unlock bootloader using Motorola's website

2. boot to bootloader, flash or boot to recovery with fastboot command (fastboot flash recovery cwm.img/fastboot boot cwm.img) *There really isn't a reason to flash this. It is very broken. Consider keeping your original recovery!*

3. boot to cwm and flash superSU zip

4. CWM will prompt to fix root, choose YES

5. Rooted!

Almost everything besides flashing a zip is broken in this CWM release, don't expect to be able to backup with it.
[X 2014 General] km8j:
I appreciate you posting this, could you by any chance post a little bit more detail on how to do the flash? Is it as simple as extracting the recovery image and flashing from ADB? How do you then flash SuperSU?
[X 2014 General] Vultorus:
I added some basic steps to original post, use caution as this isn't the most secure way to root but it will do for now. If you need further help, you should probably wait for a safer method.
[X 2014 General] km8j:
What are the gaps in security? When you say secure, do you mean safe as in not bricking the phone or security as in data is at risk, etc.?
[X 2014 General] mrvirginia:
the steps you listed are pretty much it. can't get any easier than that. exactly how it was on the previous MotoX. unlock bootloader, fastboot flash recovery .img. then just reboot to recovery and flash SuperSU zip. very straight forward.

edit: also, fix permissions shouldn't be required...
[X 2014 General] Vultorus:
It was just mentioned in the original post, I guess it doesn't matter. And by not secure I mean that the CWM is a test release so I don't know what could go wrong.
[X 2014 General] mrvirginia:
yeah i'm still awaiting a device so i'm not 100% sure on the persmissions. the zip should do all the work for the user, though, via the update-binary.

btw thanks for posting.
[X 2014 General] DarkLey:
Thanks for posting this, I suggested the guys in Q&A to do that. If anybody needs help, I made the process successfully back on Q&A (when they were testing the recovery)
[X 2014 General] Vultorus:
If anyone notices the permissions making a difference let me know, I'm curious as to why everyone was saying it had to be done..
[X 2014 General] rogeriorc:
"cannot load 'recovery': Permission denied" when trying "fastboot boot recovery cmw.img"

My bootloader is unlocked.

---------- Post added at 08:56 PM ---------- Previous post was at 08:37 PM ----------

ops, forget about it.

the command is "fastboot boot cmw.img"

And I am rooted! :laugh:
[X 2014 General] graffixnyc:
Worked for me. I'm now rooted
[X 2014 General] tacosrdelicioso:
2/10 needs more Verizon :P
[X 2014 General] Vultorus:
I apologize, I did not realize if you are just booting, you don't need the "recovery" part of that command. Glad it worked for you!
[X 2014 General] jeffy210:
You mention that this version of CWM is limited to basically sideband loading and won't do backup. Do you happen to know where I can find a copy of CWM for the X 2014 that gives me shell access? I've already unlocked and rooted my phone, but busted my screen and want to back things up. I went to their rom manager page and can't find either version of the X. Would either a 6.0.5.1 or one of the Nexus ones work?
[Galaxy Note 3 Q&A, Help & Troubleshooting] LionheartSilver:
SCREEN MIRRORING WORKING!

​

I'd like to share with everyone here the solutions already working / verified to work to use Screen Mirroring in our rooted devices!

I post this because i searched for a lot of time for an answer to this problem and couldn't find anything!

Finally I found an anwer on another topic (Link here) thanks to [MENTION=2176838]THEDEVIOUS1[/MENTION], so in order to have any other answer concentrated in 1 topic for everyone to find it in an easy way, here's the info:

SOLUTION 1 - Edith build.prop (thanks to [MENTION=2176838]THEDEVIOUS1[/MENTION])

For this method, we only need our favorite file manager with root permisions or a build.prop editor

Open the file: build.prop (located at /system/build.prop)

Add at the end of the file this: wlan.wfd.hdcp=disable

Save changes

Reboot your device

DONE! Screen Mirroring working :D!

VERIFIED WORKING ON:

Samsung Galaxy Note 3 / N900W8 / Stock odexed ROM 4.4.2

[*]Samsung Galaxy Note 4 / 910T / Stock odexed ROM 5.0.1

[*]Samsung Galaxy Note PRO 12.2" / P900 / Stock odexed ROM 4.4.2

​

SOLUTION 2 - Uninstall AllShare Updates (thanks to [MENTION=3118015]chief10rules[/MENTION])

For this method, we only need to follow this steps:

On your Note Pro/Tab Pro find All Share Cast from Samsung and UnInstall all the updates. Then click Force Close, all of this should be done in Application Manager.

Restart your Note Pro/Tab Pro (Very Important)

Using two fingers pull down the main screen from top down to unveil the controls menu. Touch Screen Sharing while the Miracast or other screen sharing service (Wifi Direct etc) is activated on Your TV.

Let it auto find it and auto connect..........Viola!

VERIFIED WORKING ON:

Samsung Galaxy Note PRO 12.2" / P900 / Stock odexed ROM 4.4.2

If any of this solutions worked for you, it would help a TON everyone here if you tell us your:

- Device

- Model

- ROM tested on

to add this info to the list of working devices :D

If you want to share any other solution, feel free to share it with us using a format like the used on this post and if it's confirmed working for anyone else, we will gladly add this to the main post :D!

Have a nice day! Hope this info helps anyone ^^
[Galaxy Note 3 Q&A, Help & Troubleshooting] freakyfranks:
This fix got rid of the hardware error, but now it keeps saying to restart screen mirroring after update. No update downloads and it never connects after turning on again. Same message keeps appearing. Any clue how to get past this hurdle?

BTW, I have an AT&T Note 2 running 4.4.2 AGNI kernel.

Thanks
[One (M7) Q&A, Help & Troubleshooting] kknb0800:
Hi,

I know this question has been asked many times before but I haven't been able to find a solution that works and I don't want to try anything that could make the situation worse.

I had rooted my HTC One M7 but now I want to unroot it so I followed the below steps taken from the link

http://xdaforums.com/showthread.php?t=2182823

1. Re-lock your bootloader (this will most probably wipe content of your device)

2. Copy downloaded .zip to fastboot.exe location (e.g. c:/SDK/platform-tools/fastboot.exe)

3. Re-name .zip file to firmware.zip

4. Open command prompt

5. Boot your device in fastboot mode (vol down + power ===> fastboot)

6. Connect device to the PC

7. In command prompt cd to fastboot.exe location

8. Make sure you have correct modeid and cidnum (type: fastboot getvar all)

9. Type: fastboot oem lock (if your device is not relocked yet)

10. Type: fastboot oem rebootRUU and wait for device to reboot

11. Type: fastboot flash zip firmware.zip and wait for process to complete

12. Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.

13. Type: fastboot flash zip firmware.zip and wait for process to complete

14.Type: fastboot reboot

15. Unlock your bootloader and flash custom recovery if you are going to use custom ROM.

I get all the way down to step 11 and it fails returning the below error:

C:\fastboot>fastboot flash zip firmware.zip

sending 'zip' (1176263 KB)...

OKAY [ 56.215s]

writing 'zip'...

(bootloader) signature checking...

FAILED (remote: 12 signature verify fail)

finished. total time: 145.854s

The ruu I tried to flash is the Guru Reset M7 3.62.401.1 one located here one

The phone is on the black htc logo screen and I still have it attached via usb. I don't really know what do now. Any help would really be appreciated!

Details are listed below

C:\fastboot>fastboot getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.55.0000

(bootloader) version-baseband: 4A.21.3263.04

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 3.62.401.1

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) serialno:

(bootloader) imei:

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0710000

(bootloader) cidnum: HTC__001

(bootloader) battery-status: good

(bootloader) battery-voltage: 3881mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-bb768ae1

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.071s
[One (M7) Q&A, Help & Troubleshooting] alray:
Guru reset is not a RUU nor a firmware and can not be flashed with "fastboot flash zip" command. It's a rom and must be flashed using a custom recovery.
[One (M7) Q&A, Help & Troubleshooting] kknb0800:
thanks for the info. I guess that what explain why it isn't flashing. How can I find the correct RUU file? I've looked in the usual places but I can't find one that matches my version-main or baseband
[One (M7) Q&A, Help & Troubleshooting] kknb0800:
turned out I needed to have s-off for it to flash after selecting the correct ruu
[XDA Assist] Sanfin99:
Hi,

Please find below My Device detail of my Tab, recently I updated my Recovery to CWM 6.0.4.8 touch using this image file downloaded from cwm website "recovery-clockwork-touch-6.0.4.8-fireball.img" using the tool flashify

The flash got completed and said it is success, but when i try to boot in recovery mode or hard boot into recovery mode, it doesnt get into recovery mode instead it boot the phone in normal mode and goes to home screen without any issues.

Problem: I am not able to boot into recovery mode which was working fine earlier.

Devise Info prior to updating CWM Flash to touch-6.0.4.8

(there was already a CWM as recovery without any version status as part OEM Product)

ROM: MT8312C_MC706_MC7062L1C2.2014041817

RECOVERY: ClockworkMod Recovery

BOARD: mc706

BOOTLOADER: unknown

BRAND: alps

SDK_INT: 17

CPU_ABI: armeabi-v7a

CPU_ABI2: armeabi

DEVICE: mc706

DISPLAY: MT8312C_MC706_MC7062L1C2.2014041817

FINGERPRINT: alps/mc706/mc706:4.2.2/JDQ39/1397814368:user/release-keys

HARDWARE: mt8312c

HOST: elinktek3

MANUFACTURER: alps

MODEL: WTAB 708

PRODUCT: mc706
[XDA Assist] matt4321:
Hi there,

Be sure to read over the manual and automatic instructions here, and try again, as best as you can: [Recovery] ClockworkMod Official and Advanced Builds

You can always ask here for further help: HTC Droid Incredible 4G LTE Q&A, Help & Troubleshooting
[T-Mobile, Samsung Galaxy SIII] Purple Ferret:
Edit: Well nevermind I seem to have fixed it. I thought it was the gain, but as it turns out I had the Noise Filtering option checked. The audio quality in calls is clear as mud now.
[General Questions and Answers] arup.shibai:
Hello!!!

I am Arup n I am using API level 17 on my Karbonn Alps A26. I have enabled "Show Touches" in the Developer options in Setting on my Karbonn Alps A26. How can I change the White dot which appears when I touch the screen?? :confused:

Please help me out... n thanx in advance.
[General Questions and Answers] joanthanmajh:
what do you mean? the white dots appearing is what is suppose to happen when you check the show touches options

if you want them gone just uncheck it
[General Questions and Answers] arup.shibai:
I do not want to remove it but i want to change that white dot to something else.

In short from where do i get custom touch indicator for my rooted karbonn alps a26
[About XDA developers] sensboston:
Please bring back "XDA 2010" theme... All current themes are uncomfortable to me (and - I think - to many-many customers too!). Colors, elements location - all that stuff are very annoying :(
[About XDA developers] Marcb:
It's there...

I've just changed back... WAY better...
[About XDA developers] bitpushr:
Ok ok, we brought it back for you all.
[About XDA developers] sensboston:
God bless you sir, thanks a lot! It's way better (no, WAY BETTER) for me!

P.S. Could you please next time do an experiment on the Pavlov's dogs first? :laugh: I'm taking my favorite site significant changes too close....
[JAMin, XDA Neo, S200 General] giuferra:
Hello everybody,

I have a Qtek S200 with Direct push enable: since few days ago I used it with a Vodafone IT Sim Card and it works perfectly. Now I'm using it with a TIM Sim Card and I have a problem: the configuration for direct push is correct (the same I used with the vodafone SIM) but now, after a sync and few seconds of inactivity the data connection gets disconnected!!! Obviously, direct push will not work anymore... Can anyone help me please????

THANKS!!!!

Giuseppe
[Xperia Z1 Compact Q&A, Help & Troubleshooting] giober98:
Hi yesterday I got a notification saying that my memory was 75% full, it gave me the option to move things to sdcard but it failed every single time. Is it a common and known bug? Could this be due to the fact that in 4.4 sdcard access is almost limited to read only? Is there a way to fix it?
[Xperia Z1 Compact Q&A, Help & Troubleshooting] profyler:
just remove the notification for this pop up. press and hold when the message pops again and romeve the notification option.
[Xperia Z1 Compact Q&A, Help & Troubleshooting] giober98:
I know how to remove notifications... But my question was "is the fact that moving files fails a bug of Sony software?"
[Xperia Z1 Compact Q&A, Help & Troubleshooting] eumanoid:
transfer failed

Files of the same filename already exist in target folder.

Ex. Sdcard/dcim/andro/dcm001

Sdcard1/dcim/andro/dcm001

This will cause the transfer to fail. Rename either the source or target files.
[Xperia Z1 Compact Q&A, Help & Troubleshooting] giober98:
Thanks a lot! I'll try and report back :)
[One (M7) Q&A, Help & Troubleshooting] Jimmyy9:
Hello , My main goal before starting this whole process was to put the phone back to 100% stock, back to **LOCKED**, so that I could get my phone repaired under warranty.

My main problem came with that my HBOOT version was 1.57.0000 and "S-On".

I have now come to this error in the FASTBOOT screen that says "Active cmdline overflow!" after trying to install a stock rom on my phone after reading somewhere that a person had managed to obtain S-Off after putting a stock + bulletproof kernel and running Firewater.

(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.27.3263.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4307mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-660ef031
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

I have read countless threads about this error, attempted to flash countless recovery images to try and gain access back to recovery mode from FASTBOOT but I get the same error. Which is after attempting to access Recovery when having flashed a new recovery image, it tries to go in but loops back round to FASTBOOT screen with the same "Active cmdline overflow! (1025 Bytes)

If someone please, has any fix to this problem, I would be greatly appreciated.

If there is any information you need to know please ask!
[One (M7) Q&A, Help & Troubleshooting] Jimmyy9:
Hi thank you for your reply, unfortunately I have read this topic almost back to front and have tried every recovery image that was posted, but none have been successful in allowing me into recovery mode.
[One (M7) Q&A, Help & Troubleshooting] alray:
then you'll probably need to send your phone for a motherboard replacement.
[One (M7) Q&A, Help & Troubleshooting] Jimmyy9:
I was thinking this may come down to this. I know that my phone is still under warranty until April next year, however if I send this phone back to them in the state it is in surely they will throw it back at me saying it's been messed about with?

The current status of the phone is **Tampered** and **Unlocked**. I'm afraid I do not know the command to print the information from the top of FASTBOOT.
[One (M7) Q&A, Help & Troubleshooting] alray:
If you already tried everything it the guide I have posted above then there is probably nothing more you can do. You can not remove TAMPERED and UNLOCKED flags from the bootloader screen with S-ON and this void your warranty. They will probably charge you to replace the main board.
[One (M7) Q&A, Help & Troubleshooting] Jimmyy9:
Thank you for your swift replies. :)

This further question goes beyond my knowledge of android development. Is there a way at all to make the device look like it is a hard brick to remove the evidence of Tampering and Unlocking? I can see this can be perceived as quite a bad thing to do morally, but I can see the coming quote from HTC for them to fix the motherboard as being quite high in price!
[One (M7) Q&A, Help & Troubleshooting] alray:
With S-ON and not able to boot in recovery, I don't know how.
[One (M7) Q&A, Help & Troubleshooting] Jimmyy9:
Thank you very much for your replies and help :)

I did see in this thread http://xdaforums.com/showthread.php?t=2781953 that [MENTION=2605798]nkk71[/MENTION] was able to fix what seems to be an exact copy of the problem I have here. However what nkk71 actually did is very vague since he assisted the person through PM/Teamviewer. It would be great to hear what fixed the problem! :)
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Hi Jimmyy9,

unfortunately, it's a question of luck... i didnt post what we did, because it was (and still is) inclusive (otherwise i would have posted the solution).

in that particular instance, we were able to flash the noBCB recovery to the kernel partition and were able to access it.

i've tried the same (and a lot more) a couple of days ago, but without any success :(

it still eludes me what/when/why would allow a custom recovery to boot with S-ON on higher hboots, why it sometimes works, and most of the time it doesn't, so i really have very little to offer

unless you can get to a custom recovery (even a rooted ROM), i honestly can't help

just for info, i did a similar procedure on the HTC Butterfly S, but it also required an hboot downgrade to be able to get to recovery.

sorry, but unless you are able to get to any custom recovery or rooted ROM, i don't have any ideas
[One (M7) Q&A, Help & Troubleshooting] Jimmyy9:
Thank you for the detailed reply. I had been up for 30+ hours finding fixes and reading information regarding bricking phone and how to restore them. So my situation now is to either send it back to HTC repairs and confess to them I bricked my phone and cough up the costs for them to fix it,

Or

Attempt to fix the corrupt binary which I understand is the "misc" partition. I do however understand this may not be possible without s-off or recovery access. My only option would be if there existed a RUU h-boot 1.57 exploit? It might also be interesting to test the recovery img you used to fix the previous problem, obviously this is getting into desperation but I'm willing to try absolutely everything before I give in to sending HTC a bricked phone to fix.
[One (M7) Q&A, Help & Troubleshooting] nkk71:
fixing the misc partition, doesn't actually require s-off, just "somewhere" where you have access to "dd" partitions.... the problem is that [adb commands with root and busybox], are only available in:

* a booted rooted ROM with USB debugging enabled

or

* a custom recovery

unfortunately, (at least to the best of my knowledge and efforts), fastboot is not able to flash to the misc partition... i tried a lot of different things, but could not get fastboot to flash to the misc.

as i mentioned, a couple of days ago, i spent a good 3 to 4 hours on teamviewer with another user in the same situation as yours (except he had an international unbranded edition, which has a lot more signed firmwares than your model), and we went through a lot of permutations to try to get somewhere but unfortunately with no success

maybe if i have some time over the weekend, i'll do a teamviewer session with you, but i fear it will also end up in failure

if there is somebody close to you who has a jtag (or other hardware), i guess this could be fixed easily, but with software only there are only so many things you can do.