yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Q&A, Help & Troubleshooting] Fallon9111:
Nope

I have not read this article. The new security features will stop you from rooting a device (using traditional methods) but any devices which can be unlocked can install custom roms and then also be rooted :)

Nexus devices can ALWAYS be unlocked and therefore can ALWAYS be rooted!
[Nexus 5 Q&A, Help & Troubleshooting] jd1639:
This is why you get a nexus device. Manufactures and especially carriers are locking down their phones to the point they're not any fun to own anymore. But nexus will always have custom roms and unlockable bootloaders
[Android Q&A, Help & Troubleshooting] xmmdx:
Hi everyone,

I have a huawei mediapad 10 link and have some questions.I searched the web to find a custom ROM but I couldn't find much info. And how can we use this tablet as a phone? As many people knows, we can use huawei mediapad 7 like a phone with huaweimediapadphone.apk but it is not working on huawei mediapad 10 link...Does anyone know a way about voice call and custom rom.. by the way sorry for my poor english..

Thank you in advance..
[Android Q&A, Help & Troubleshooting] xmmdx:
Up

Up

Up
[Android Q&A, Help & Troubleshooting] xmmdx:
U

P
[Android Q&A, Help & Troubleshooting] Osmaniac:
UP :p
[Android Q&A, Help & Troubleshooting] karth83:
1 install this rom update

http://consumer.huawei.com/en/tablet...n.htm?id=17842

2 install huaweimediapadphone.apk

3 the phone app works

tested it on my Huawei MediaPad 10 Link (s10-201u)

Courtesy jackal666 from another thread
[Xperia Arc Q&A, Help & Troubleshooting] rajumvgr:
Can KitKat be ported onto our Arc S phones ????
[Xperia Arc Q&A, Help & Troubleshooting] 17th_angel:
Perhaps...

http://xdaforums.com/showthread.php?t=2431179
[Xperia Arc Q&A, Help & Troubleshooting] popthosegaskets:
That was just a discussion thread... and now some people think that just because it can run on 512MB RAM they can install it on their phones straight away... If kitkat ever comes to the Arc/S it will take a while for it to become stable enough for daily use. Also, the drivers we use are old since there have been no updates. If you guys want kitkat running successfully on this device, these old drivers need to be integrated with the new software, which is very tedious. Mike is already going to drown under 4.2 and 4.3, adding another OS to the pile will place him under more stress.

Don't assume the work we developers do is simple, just because an update came out that meets the system specifications means it can run just by downloading and installing it in recovery. If you ever tried to create a ROM by yourself, you'll find out that a lot of work needs to be done, along with many user complains and flooding your development thread with useless posts. That's how messed up the user community is nowadays. Jader's UHD ROM thread is one example of how users interact with the developer.

僕のLT18iから送られてきた
[Xperia Arc Q&A, Help & Troubleshooting] 17th_angel:
Im sorry, but which part of perhaps its a "definitely yes"?

I just point to that thread so he and anybody with the same question can see that it really going to depends on how google code it and how hard could be for the developers to bring that code to our devices...

I never declared that it will be a fact, but you have to admit that the 512 MB its a nice hope.
[Xperia Arc Q&A, Help & Troubleshooting] popthosegaskets:
That reply was for that thread itself since some prick was like "hey Kitkat runs on 512MB devices"... I wasn't even referring to you in the first place.

Yes, it is hopeful but not promising, see Mike's reply at the thread itself

僕のLT18iから送られてきた
[Xperia Arc Q&A, Help & Troubleshooting] Deleted member 3493119:
Yes, it's possible to port Android 4.4 for our device but it all really depends on if there will be any developer / developers who want to spend their time porting 4.4 for our device. Mike have started working on it for our devices, but we will see when or if he releases it or not.

I might see if I'm able to sync the sources, but the main problem on my end is that my PC is really bad and not suited for development.
[Xperia Arc Q&A, Help & Troubleshooting] nrupareliya:
Yes, Harsh is developing the same, follow the link

http://xdaforums.com/showthread.php?t=2134257&page=184
[Xperia Arc Q&A, Help & Troubleshooting] tangosierra_:
The fact that it can run, does not mean that it will run.

Either way, I am sure the devs will be porting it over in no time.
[Xperia Arc Q&A, Help & Troubleshooting] nrupareliya:
Developers are trying hard, hope to see KK on Arc S soon
[Xperia Arc Q&A, Help & Troubleshooting] Attitude.SSJ:
Fyi harsh isn't developing kitkat.. It's just a kitkat ui for his rom update...
[Xperia Arc Q&A, Help & Troubleshooting] Bread123:
yes it is try to search if you wanna stable blasting fast rom with kitkat teme then flash super jelly bean by harsh with kitkat ui

---------- Post added at 08:02 PM ---------- Previous post was at 07:56 PM ----------

but kitkat based in my option is bet AORP kitkat rom try it
[Xperia Arc Q&A, Help & Troubleshooting] Scayris:
Just as a suggestion, I'm currently using VanirAOSP and it's pretty good. All I've to say is that right now one should get the vanir_anzu_4.4.2.012814 version, as the latest, vanir_anzu_4.4.2.022314, has a few additional bugs. On the mentioned good version WiFi works, everything is fairly smooth and you're left with enough space to actually install the apps you want, which seems to be an issue on many roms due to Arc's small internal memory.. Only real problem's the default browser lagging terribly, but I hear that's a general issue? Anyway, for anyone interested in kitkat on Arc it's definitely worth checking out.

Here's the thread: http://xdaforums.com/showthread.php?t=2627083
[Xperia Arc Q&A, Help & Troubleshooting] DuckyMomo:
If you want a good KK experiance I recomend carbon Rom just serach or let me doin' it for you her you are sir http://xdaforums.com/showthread.php?t=2575425
[Xperia Arc Q&A, Help & Troubleshooting] Lt.Shantanu:
AORP is stable for me.... you might wanna check :)

I m using AORP[anzu] from 2 weeks and it works awesome.:cowboy:

I will try VanirAOSP (out of curiosity), thanks for suggesting. ;)

Tried it. Really cool ROM, some minor bugs but its OK :)
[Xperia Arc Q&A, Help & Troubleshooting] DuckyMomo:
Tried ION kernel and stuff and I can say that apart of one or two really minor bug the KK experience is just awesome and will be better within some months i suggest you to follow all the "Xperia Overlay" thing a I hope it gonna be amazing:D:laugh:
[Samsung Galaxy Nexus] ancestralelf:
Hi there, I've recently found out samsung galaxy nexus usb protocol doesn't include any UMS option natively or using any roms/apps combination.

I was wondering tho, to make use of some of the space in the internal storage as a common flash drive, is it possible to create a FAT partition and mount it as an external sdcard? More or less like in phones where sd slot is present. Even tho the os wouldnt be able to recognize the new partition itself, I'd be glad to use some of the space as mass storage to connect the device to car radios and stuff like ps3.

Thanks for the attention

Federico

ps: sorry for the poor english it's a foreign language to me
[Samsung Galaxy Nexus] ancestralelf:
Up

I know this isnt the right section but as a new member in xda community I'm not allowed to post in specific areas. Thanks
[Samsung Galaxy Nexus] geoffcorey:
No it's not possible and won't ever be. If it was possible then you would have already found out how to do it.
[Galaxy S 4 Q&A, Help & Troubleshooting] mayank0019:
I recently updated my stock rom to 4.3 version and then was facing some problems with rooting. so i decided to downgrade back to 4.2.2 stock but every time I tried to flash the md5 file via odin, it fails and shows unsupported version in download mode.

I went to a retailer and he flashed the 4.2.2 stock rom with another software (couldn't look properly which one). It wasn't odin. Can anyone tell me how can I downgrade from 4.3 via odin or let me know any other ways of doing so 'cause the rom I'd got installed from retailer didn't have network connectivity. I downloaded a fresh stock rom - 4.2.2 for my phone and it still gives the "unsuppoted version" error. I've already checked the version of stock rom and its the same that was running before all this mess...pls help..:confused:
[Galaxy S 4 Q&A, Help & Troubleshooting] lazerrr:
Same story. Need help too.
[Galaxy S 4 Q&A, Help & Troubleshooting] samersh72:
i guess you have the I9500 variant,

you have the secured bootloader, you can only downgrade to MH1 4.2.2 only because it has the same bootloader. MH1 can be found in XFE or XFA South Africa firmware
[8125, K-JAM, P4300, MDA Vario Software Upgrading] lonely_night:
I want to dump my Qtek 9100's WiFi module (include drivers). I use "rdmsflsh.pl" tools dumped the Qtek 9100's Wifi drivers file "TNETWLN.DLL". I make it into a CAB file include necessary registry keys and values. I install this CAB file in my other phone ( DOPOD 838 with chinese system, this system not the WiFi module, but it have WiFi card), install process is working fine, because i already see "SDIO WLAN Wireless Adapter" in my network card manager (before it without this adapter), but it not work, i don't know why?? maybe i dumped file "TNETWLN.DLL" is a incorrect file. can anyone tell me why?? thanks

i'm sorry for my bad english... :-(
[8125, K-JAM, P4300, MDA Vario Software Upgrading] mitel:
can you send me the file named tnetwln.dll?

wangquan0730@hotmail.com
[8125, K-JAM, P4300, MDA Vario Software Upgrading] lonely_night:
OK!

I send the file to your email

Thanks for help!!!
[8125, K-JAM, P4300, MDA Vario Software Upgrading] laurence22:
same phone

I have the same phone and I can not turn wifi on can you help me?
[Nexus 7 Q&A, Help & Troubleshooting] Anderson2:
My wife has a rooted nexus 7 2012 wifi and she unintentionally accepted the ota Android 4.3 update. So of course it unrooted her.

I originally had a hell of a time rooting this tablet using wugfresh nexus toolkit. Took me several days to succeed and the same thing is happening again. My Windows 7 laptop keeps installing the wrong drivers even though I selected the option to disable the auto driver configuration. Also USBDeview never shows the installed Samsung adb drivers yet when I try to install them I am warned they are already installed. It's already been hours and who knows how many retries and reboots!

So even though I'm a newbie I decided to go the Android sdk route.

1. Where do I download the files I need to just root the darn tablet?

2. What do I do next?

Please keep it simple........

Anyone want to walk me through it on the phone?

Thanks
[Nexus 7 Q&A, Help & Troubleshooting] bobbytomorow:
If you are new to using SDK, check this out for a well laid out tut on how to get set up and rooted.
[Nexus 7 Q&A, Help & Troubleshooting] Anderson2:
I now have android sdk set up.

What are the commands I should issue to root?

Thanks
[Nexus 7 Q&A, Help & Troubleshooting] bobbytomorow:
now you need to flash a custom recovery then flash a root zip file via windows command prompt...Have you figured out how to interface with your device and the windows command prompt? eg;

-a good first command is "adb devices" and see if it lists your device, if it does your golden...

-then you would issue "adb reboot bootloader"

-once in bootloader you would issue "fastboot flash recovery whateverrecoveryouchose.img"

-then while in bootloader toggle with the volume keys to "recovery" option and press power

-now you will be in your new recovery you just flashed and you can push the zipped root file you chose to the sdcard, "adb push rootyouchose.zip /sdcard/"

-once its been pushed you can flash it in recovery and reboot, and you are now rooted

-this is the latest cwm recovery that you could flash in fastboot as described above

-this would be the root file you want to push then flash in recovery

-this may be of some help, scroll down halfway
[Nexus 7 Q&A, Help & Troubleshooting] Anderson2:
Thank you so much for helping. You can't know how much it is appreciated.

-a good first command is "adb devices" and see if it lists your device, if it does your golden...

Got that. It works!!

-then you would issue "adb reboot bootloader"

Worked! Got the Android on his back.

-once in bootloader you would issue "fastboot flash recovery whateverrecoveryouchose.img"

Is recovery image on my pc or the tablet?

Why do I have to indicate the img name here if I will later select it
[Nexus 7 Q&A, Help & Troubleshooting] Anderson2:
When I write

Fastboot flash......... Img

I get

Unknown partition 'the image file name'

"error : cannot determine image filename for. '.......'
[Nexus 7 Q&A, Help & Troubleshooting] bobbytomorow:
You need to have downloaded a recovery image, that is what you flash I linked to one on my last post, that file is called "recovery-clockwork-touch-6.0.4.3-grouper.img" so you would issue,

fastboot flash recovery recovery-clockwork-touch-6.0.4.3-grouper.img

"fastboot flash recovery" is telling it to flash a recovery file and "recovery-clockwork-touch-6.0.4.3-grouper.img" is the recovery file in this case to be flashed so, combined its, "fastboot flash recovery recovery-clockwork-touch-6.0.4.3-grouper.img"

I do not use Windows, I use a terminal instead of windows command prompt so I can't be specific as I am not too familiar with windows command prompt. With terminal it is much easier in my opinion but you need to be running nix or Mac OS to have a terminal
[Nexus 7 Q&A, Help & Troubleshooting] Anderson2:
OK, still can't get past the final stage in rooting my wife's nexus 2012 nexus 7.

I have the proper drivers installed and it connects fine with my Windows 7 laptop.

From a Windows 7 command prompt

1. "abd devices "

Correctly returns the attached nexus

2. "abd reboot bootloader "

Correctly reboots the tablet

3. **here's where things breakdown :

I downloaded the latest twrp openrecovery img for grouper and renamed it (for simpler typing)

" openrecovery-twrp-grouper.img"

However, when I now issue the command

"fastboot flash recovery openrecovery-twrp-grouper.img"

I get an error :

Cannot open openrecovery-twrp-grouper.img

The same thing happened with the clockwork-touch recovery img. That is why I downloaded the twrp img which I am more familiar with anyway.

So, am I missing a step between rebooting the bootloader and flashing the recovery? After the bootloader is rebooted and I get the Android on his back with an empty belly, do I need to do something else before flashing?

Do I need to put the recovery image somewhere special in the nexus file structure?

I'm stuck.

Thanks
[Nexus 7 Q&A, Help & Troubleshooting] GedBlake:
Hi, Anderson2...

If I may throw in my couple of cents...

The recovery.img file to be fastboot flashed (TWRP or CWM, it really doesn't matter which) needs be to stored on your PC... on the same PATH as the FASTBOOT.EXE file. The easiest way of accomplishing this, is to copy it directly into the folder that contains your FASTBOOT and ADB executables.

Where this folder is located on your PC depends on how you have fastboot setup, but it's usually stored in a folder called /Platform-Tools (if I remember correctly). But because I've never bothered myself installing the whole Android SDK (of which Fastboot is a part of) on my PC, I'm not sure of it's precise PATH (ie. it's location) but I think it's somewhere in the Android SDK folder.

For myself, I just maintain a simple folder on the Windows desktop containing the FASTBOOT.EXE and ADB.EXE files and a few necessary Windows .DLL files. When I wish to fastboot flash a Custom Recovery, I simply copy the Custom Recovery .img file (TWRP or CWM) into this folder, rename it to recovery.img (renaming it thus makes typing at the command prompt easier, and reduces the scope for potential typos)... boot the Nexus 7 into the bootloader, hook it up to my PC via USB. And then open a command prompt on the folder, and run...

fastboot devices

This is purely diagnostic, and hopefully confirms a working fastboot connection.

You should see something like this...

025d2d424bxxxxx fastboot

A serial number followed by the word fastboot. If you see this, you can go ahead and run...

fastboot flash recovery recovery.img

(This command assumes an unlocked bootloader... indicated by an unlocked padlock symbol under the Google logo upon boot. If it isn't, you should unlock it with fastboot oem unlock BEFORE fastboot flashing the Custom Recovery).

My point is, though... the 'recovery.img' to be flashed must be in the same folder as the FASTBOOT.EXE file, or as you have discovered, you will get the error "Cannot open recovery-twrp-grouper.img".

If fastboot can't find it.. it can't open it:).

Hope this helps.

Rgrds.

Ged.
[Nexus 7 Q&A, Help & Troubleshooting] Anderson2:
Thank you very much! That is very helpful. I had assumed the recovery img should be on the tablet. No wonder fastboot could not find it! I'm sure that will solve my problem.

Thank you for helping. I'm slowly learning my way around the adb, fastboot commands as I'm sure I'll need them again when 4.4 unroots me again.
[Nexus 7 Q&A, Help & Troubleshooting] Anderson2:
Thank you all very much. I greatly appreciate your help.

This post should be a sticky!

One more question, this nexus 7 2012 is my wife's. But I also own a nexus 7I this one a 2013 which is currently rooted with Android 4.3 and twrp Nandroid backups. I'm afraid that when the 4.4 ota upgrade comes along it might again unroot both our tablets. Are the rooting commands or procedures different for the 2013 nexus 7 (other than using a flo recovery img,) or do I do exactly the same as described above?

Again, you guys are wonderful to help us newbies out. Many thanks to all. Wish I could do something in return.
[Nexus 7 Q&A, Help & Troubleshooting] GedBlake:
Hello again, Anderson2...

Well, you sort of are already doing something in return.... you're asking questions.

Questions that require answers. Those answers, whoever posts them, may be of assistance to somebody else. Somebody else looking for a solution to a similar problem.

I always look upon these forums as a means of sharing. Not everybody can know everything. God knows, I don't know everything.... and I've been messing around with Android for three years now. So don't worry so much about it being a quid pro quo sort of arrangement.

I know what I know primarily as a result of my own experiences and what I've learned here from the many (in most cases, more knowledgeable) posters here on XDA. What you learn

today

, you can pass on to others,

tomorrow

(metaphorically speaking). We, all of us, stand on the shoulders of each other.

With regard to the second generation Nexus 7 (2013)... I'm afraid I really don't know much about it... but I'd be surprised if rooting it deviated significantly from rooting the first generation Nexus 7....

Namely...

1). Unlock the bootloader.

2). Flash a Custom Recovery.

3). Using that Custom Recovery, flash some SU root package... probably from Chainfire.

Anyway, I've found this tutorial here...

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

...and it appears to follow a very similar template.

The Nexus 7 (2013) forum itself, which is also worth visiting, is located here....

http://xdaforums.com/nexus-7-2013

Rgrds,

Ged.
[T-Mobile LG G2x] Ersio:
cliffs:

Got the phone from a friend of a friend.

It has the cyanogen mod on it (not sure which one)

Been using it for a few months and loved it, but now the phone is really acting weird, screen won't open/delayed etc

I would love to unroot this phone and just go back to regular stock that comes with the g2x but can't really find any good source to tell me how.

Am I screwed since I wasn't the one to root this phone?

Just figured out I have version: Cyanogenmod-7.2.0-p999

Add on:

I've tried to download the stock and I get this

Finding update package...

Opening update package...

Installing update...

Installation aborted.
[T-Mobile LG G2x] hippiesky:
Try a different cm7 rom
[T-Mobile LG G2x] Pain-N-Panic:
In all honesty I would just flash the latest vanilla version of CM7 from get.cm. Its the most reliable ROM for this phone and way better than any stock firmware released by LG. There's tons of kernels you can flash also if you're into overclocking and undervolting like I am. However the stock cm kernel does the job.
[T-Mobile LG G2x] Ersio:
ishoid large

I appreciate the suggestions, however it still does not relate to the more pressing problem of how I can not flash the rom. As pointed out in my first post, it comes up as

"Add on:

I've tried to download the stock and I get this

Finding update package...

Opening update package...

Installing update...

Installation aborted.

"
[T-Mobile LG G2x] TwitchyEye:
That sounds like a bad download.
[T-Mobile LG G2x] Ersio:
It was a pretty old link, is there a link to which rom I should download for stock?
[T-Mobile LG G2x] Pain-N-Panic:
out of curiosity...did you do a full wipe (factory data reset, both caches and format /system) before trying to flash the stock rom? I believe Buru, one of the dev's for the g2x has a stock rooted 2.3.4 rom available for download in the dev section. There's a few of them out there.

If all else fails you could always check out ROM for recovery here- http://xdaforums.com/showthread.php?t=1248644&highlight=search+this+forum
[T-Mobile LG G2x] Ersio:
I was literally about to send a post here about what you mentioned.

It appears I did have an old download.

I did indeed do a factory data reset, both caches and the delvik (forget how it's spelled) wipe.

I had then succesfully installed back to factory.

so far the only problem I notice is phone calls. it's like a broken TV + fax line noise that is very loud. Any Ideas?
[T-Mobile LG G2x] TwitchyEye:
What you need to do is flash the correct baseband fix from here http://xdaforums.com/showthread.php?t=1776843
[T-Mobile LG G2x] Ersio:
You my friend are amazing!!!

Now basically every now and then both on wifi and slightly when not on wifi, I can hear myself echo.

Also for some reason, when I try to video skype someone, my video does not work.

Any suggestions?

so far, glad to have this phone working better than it did before!
[T-Mobile LG G2x] TwitchyEye:
The video thing is kinda weird. Which rom are you running? If you're trying to run anything above gingerbread there's tons of issues with video. Mainly that it doesn't work.

The echo thing I think i've seen people mention that but I'm not sure where. I can't remember whether or not it was resolved. All I can think of is some setting somewhere and something about dual mics... yeah. That's all I got. Maybe someone else will remember.
[T-Mobile LG G2x] Ersio:
1 more thing if anyone can help. I know I've seen it some where, but I'm not able to use wifi to make calls/send text. I know there was something I had to download but can't find it again.
[Nexus 5 General] AndreaCristiano:
http://youtu.be/_NHYYbleY7c
[Nexus 5 General] crawlgsx:
People actually put these phones in the same category and compare them? Why?

Motorola X = dated hardware and overpriced. I don't care how much you can customize it. it's hardware doesn't compete with any modern smartphone. S4 Pro, in Fall 2013? pass.

it's hardware competes the with the Nexus 4 I guess, you could compare them, but at the price points again why bother.

So My apologies. That was a poor decision on my part, I do however stand by my opinions.
[Nexus 5 General] AndreaCristiano:
when you speak like that it is obvious you have never owned the MOTO X or actually used it for a length of time. Also it is obvious you didnt watch the video. PS I have owned all those phones( G2, S4 Note 2 etc ) and the MOTO X trumps them all even the Nexus 5 I just returned