yashsingh1/xdaforums huggingface dataset:
[LG Optimus 2x] owais40:
Use this link to download latest Official firmware for your phone

http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=[IMEI]

Replace [IMEI] with your IMEI in the link...

OR

Download firmware from here ... It also gives list of official links .... There are P990, P999, SU660,P990HN firmwares with different countries listed...

http://lg-phone-firmware.com/index.php?id_mod=3

Try to flash it as KDZ (or) extract .bin & .fls files from it using AIO Toolkit and then Smartflash those two files ... If you want to flash only baseband then .fls one is the baseband ....

I'm telling to do this because it may be possible that you are trying to flash wrong KDZ or wrong baseband and that's why, may be, you are not able to do it ....

If you flash v30 firmware then your bootloader will, most probably, be changed to new one .... So consider that in mind also before flashing .....

Or a better solution ..... Natalya said that he/she might be knowing the solution to your problem... So try to consult for that also....

Again, there is a dedicated development for P999 also on CyanogenMod apart from P990 http://get.cm/?device=p999 ...

---------- Post added at 07:09 AM ---------- Previous post was at 06:58 AM ----------

You just got a bit ahead of me in writing this comment ... I couldn't see it before writing my reply .... So one of the methods for confirming your phone is to look beneath your phone battery on the phone and another is to go to the first link I gave above and insert your IMEI also there in the link and then see what firmware download link LG returns .... Phone model will be also written in the download link, so you can check there also....
[LG Optimus 2x] earthabbey:
owais, as I said before I can not smartflash and the LG tool is not working. It doesn't matter what files I have there is no communication with the handset except via NV flash.

It is a p999dw, that is on the inside of the phone, that's how I knew, I just didn't know that meant it was a G2X as that is not written anywhere...whereas Optimus 2X was in the software and the battery says P990 and that thread on CM I linked you to gave me the impression that everything was the same except the provider. From what I've been reading I'm not the only person that has had this problem because also in Canada Wind Mobile advertised this phone as a 2X... so I am off to go through those solutions now *sigh* lol

Thanks again for all your help!
[LG Optimus 2x] owais40:
And what phone model does LG download link show ( The first link ) ...
[LG Optimus 2x] earthabbey:
ummm...from that I was able to download V11H_00.kdz. I also found in the other forum, for those of you experiencing the same issues I have:

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

Via that thread I was able to return the phone to stock :D I have cell reception again! yay! It is the old original version of everything but at least I have cell service again. :)

Incidentally the version from that thread is listed as V21E.... I'm not really sure what significance it is (if any) that the version numbers are different.
[LG Optimus 2x] owais40:
Congratulations on getting your phone running fully again :) :D .....

---------- Post added at 07:48 AM ---------- Previous post was at 07:46 AM ----------

V21 is an upgraded version than v11...
[Xperia Arc General] Frankness:
After 2 years whit my sony ericsson xperia arc. I have change it out whit samsung galaxy s4. Thanks for 2 years of fun and tiers and a lot of guidens from this forum :)

Ps my arc started to miss calls. Dont get sms and bad battery. Started sommer 2012 whit sony firmware ics. And now again on cm 7.
[Xperia Arc General] georgeiulian89:
You should've use this thread http://xdaforums.com/showthread.php?t=1724085 instead of making another one.
[Xperia Arc General] Frankness:
I thought about it. But its for arc s :)
[Xperia Arc General] georgeiulian89:
It doesn't matter, Arc and Arc S have the same thread ;)
[Xperia Arc General] Frankness:
Well my mistake then ;)
[Xperia Arc General] david azzz:
Great Cell Phones

I also will soon replace the SONY ARC S

to SAMSUNG S4 :cowboy:
[Micromax A110] Lal Ayer:
Mod edit: Please do not post mirrors with out the original developers permission and with out giving them full credit for their work.
[Micromax A110] Sk.D:
It's A limit. Dude this app we can download from playstore. Stop spamming xda.
[Sony Xperia Miro, Tipo (Dual), J, E] bnayagrawal:
have any one purchased or used it

costs 0.9k

images below
[Sony Xperia Miro, Tipo (Dual), J, E] sidbslay:
Affirmative

Yup! Its good to go. Best earphones under 1000 bucks trust me.
[Sony Xperia Miro, Tipo (Dual), J, E] fadlizuha:
where i've to buy cases for SONY XPERIA E???:cyclops::cyclops:
[Sony Xperia Miro, Tipo (Dual), J, E] iSpammer:
from your shop :p
[HTC Sensation] khaled13:
after i fixed my random reboots i flashed ViperS_1.6.3 ROM but the wifi never works i tried to flash boot.img with adb & other kernel & factory reset but nothing changed the wifi still not working its only work when i flash ViperS_3.0.0 any help !!:confused:
[HTC Sensation] ashkan-khatar:
Install WiFix manager, haven't you done yet?

Spit out from an HTC Sensation XE, a revived device while was dying due to lack of support, with TeamVenom, and other astonishingly amazing developers' benignity...
[HTC Sensation] khaled13:
i tried it but nothing fixed :rolleyes:

yeah random restarts are gone :good:
[HTC Sensation] ashkan-khatar:
If you aren't s-off, then re-flash the ROM smartflash enabled.

Spit out from an HTC Sensation XE, a revived device while was dying due to lack of support, with TeamVenom, and other astonishingly amazing developers' benignity...
[HTC Sensation] khaled13:
i S-OFF my phone nothing too , i tried smartflash nothing changed
[HTC Sensation] rzr86:
go to data>misc>wifi and delete wpa_supplicant.conf file

but first copy it in the sdcard for safe

then see if wifi works
[HTC Sensation] khaled13:
problem solved :good::good::cool:
[HTC Sensation] Chris Hamsandwich:
Where was the file located

Where was the file located
[Android Q&A, Help & Troubleshooting] Romar31:
Hi. I am currently running a miui port on my CM flare s100/Karbonn a9+. My problem is that the system detects audio files differently. Any music player installed will try to play all of the files on any extension on my storage except for *mp3's and other audios. What could be the culprit? Is there any library file, system apk, conf, permissions, xml or jar that i could check out, edit or replace? Any answers would be greatly appreciated. thank you
[Ouya Android Development] WinDroidGuy:
Device is pre-rooted, but only lets you do stuff via terminal. I didn't find a way to install Superuser/busybox on Mac, so I decided to make a simple guide. Took me all of 3min to complete, well since I already had the sdk and everything else installed.

You'll need this Superuser.apk, su binary and busybox.apk, dL the files from here http://d-h.st/BBk, once you have the files installed and launch Superuser it will ask you to update the binary, just click yes. Place the 3 files in your sdk/platform-tools folder.

Open Terminal cd sdk/platform-tools

On your Desktop go to Go…Go to Folder and type ~/.android, open adb_usb.ini and add 0x2836 to that file, save and close.

To verify it's listed:

./adb kill-server

echo 0x2836

./adb start-server

./adb devices

Your device should be listed here. If you want wireless adb access so you're not always hooked up to the console do the following, make sure your device is still connected via usb:

./adb tcpip 5555

unplug console

./adb connect xxx.xxx.xxx.xxx (this is the ip of your console, this is listed under manage…system…console info, should be the second line)

You're set, now you can install apps wirelessly to your OUYA console. You need to make the console read/write to do this do the following

./adb shell

su

mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP

mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/UDA

mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/CAC

Now we will install su binary, superuser and busybox

./adb push su/system/bin/su /sdcard/su

./adb shell

su

cat /sdcard/su > /system/xbin/su

ln -s /system/xbin/su /system/bin/su

chmod 6755 /system/xbin/su

exit

exit

./adb install com.koushikdutta.superuser.apk

./adb install stericson.busybox.apk

Should be up and running, if this helped you please thank me or donate a couple bucks :)
[Ouya Android Development] tcollum:
You rock!

I was at this for a while before I found your post. I'm on windows, but this is the only thread I could find that had anything useful ;) Mind if I share this around on other forums?
[Ouya Android Development] WinDroidGuy:
Just link them back, steps are almost identical for Windows. Just need to remove the ./ from the adb commands
[Ouya Android Development] rayman:
It's pure luck that this works. There's several things wrong with it.

There's no reason to have two copies of su. There should only be one, and at most have the other be a symlink.

the su binary should be chmodded '6755'.

It works because piping the contents of a file to another file usually leaves the permissions intact. So, sort of works - it leaves a broken copy of su in /system/bin and a luckily working one in /system/xbin.

So, tl;dr, the guide should be:

./adb push su/system/bin/su /sdcard/su
./adb shell
su
cat /sdcard/su > /system/xbin/su
ln -s /system/xbin/su /system/bin/su
chmod 6755 /system/xbin/su
exit
exit
./adb install com.koushikdutta.superuser.apk
[Ouya Android Development] WinDroidGuy:
Thanks, this was my first time doing anything like this...figured I'd try to hack together something from other guides, since I didn't see very many people with the device yet. I will change it now :)
[Ouya Android Development] lilstevie:
This is really pointless, userdata is already RW, cache should be RW, but more importantly you do nothing that would require them to be remounted
[Ouya Android Development] TadeoNYC:
I'm not sure what I am doing wrong here. Can anyone help? All the files are there.
[Ouya Android Development] elmerohueso:
The command should be "adb push su /sdcard/su" (pushing su to the sdcard).

Setup wired and/or wireless ADB

(Optional) Put adb.exe in your Windows PATH variable so you can run it from anywhere

Download and unzip the SuperUser files from http://d-h.st/BBk

Open an ADB shell with elevated permissions

adb shell
su

Mount the system partition as read-write

mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP

Exit the ADB shell

exit
exit

or CTRL + C

Push su to the sdcard

adb push su /sdcard/su

Open an ADB shell with elevated permissions

adb shell
su

Cat su into /system/xbin

cat /sdcard/su > /system/xbin/su

Create a symbolic link to su in /system/xbin from /system/bin (safer/cleaner than just putting su directly in the bin folder)

ln -s /system/xbin/su /system/bin/su

Set the su permissions to -rwsr-sr-x

chmod 6755 /system/xbin/su

Exit the ADB shell

exit
exit

or CTRL + C

Install SuperUser

adb install com.koushikdutta.superuser.apk

Install BusyBox

adb install stericson.busybox.apk

Run SuperUser on the OUYA (Make > Software > SuperUser) and allow it to update
[Ouya Android Development] TadeoNYC:
Thank you Elmero.

I'm so glad I gave up and went to bed last night. It could not have gone smoother. I followed the instructions for setting up wireless adb from here http://xdaforums.com/showthread.php?t=2272266 as well.

TIP: I wasted an hour or more trying to figure out why PC was not recognizing the OUYA at all. It was the stupid Micro usb port, compunding the fact that all the ports are to close to begin with

the micro usb port is very deep

. Neither of my Samsung cables worked, fortunately I have a kodak pocket video cam and the cable for that is a few mm longer and worked perfectly.
[Ouya Android Development] mybook4:
And who said Kodac isn't relevant anymore?
[Ouya Android Development] pdelponte:
The link to the Superuser.apk is not working.
[Ouya Android Development] WinDroidGuy:
Working fine for me...
[Ouya Android Development] FrostyWolf:
Not working for me either.
[Ouya Android Development] TadeoNYC:
There is an issue with the website. Just try back until it connects.
[Ouya Android Development] hellrokr:
just to be clear. once its rooted, can i install any android apk to the console? the one that i've bought from android play market?
[Ouya Android Development] FrostyWolf:
1) It's already rooted.

2) You can already sideload anything you want to it, same as (almost) any android device, whether it is rooted or not. (http://xdaforums.com/showpost.php?p=41796467&postcount=11)
[Ouya Android Development] TadeoNYC:
So what steps need to be repeated after the OTA?

from my limited understanding I think it should be steps 4 through 12. Or does the system partition not need to be mounted as read-write again?
[Ouya Android Development] professorpoptart:
Yup 4-12

Edit

If su is still on the sdcard you can skip 6-8... wont hurt if you do them though...
[Ouya Android Development] mybook4:
Might be a good idea to do them. The OTA version of such is different from the one in this guide. I had tried keeping the stock su and superuser complained
[Ouya Android Development] htc-rocks:
Do you still have access to the ouya store after SU installed? I heard rumors that access to the store was blocked until root access removed?
[Ouya Android Development] datagutt:
You have full access to the OUYA store even when you are rooted.
[Ouya Android Development] ApplesRevenge:
Newbie here learning the ways and reading books/sites. Is this the SU binary and apk by Koush and are SU binaries interchangeable with differing superuser.apk?

Searching for it produces a lot of false positives and general user help.

I understand the rest of what was done.

Any feedback/urls are welcome.
[Ouya Android Development] tennisbgc:
Inputting the adb shell su I get device not found message. Im opening a comand promt in platform-tools.
[Ouya Android Development] TadeoNYC:
Do you have adb properly set up as on http://xdaforums.com/showthread.php?p=41247928 ?

Check your device manager and make sure your ouya is properly installed, you need adb drivers. Easiest ones to get are from Samsung kies, you'll then have to them manually select them "have disc". I figured all of this out in a few hours with a little help. It's hard because the info is a little spread around.
[Ouya Android Development] ineedaname:
This worked perfect thanks!!!
[Ouya Android Development] tennisbgc:
how exactly do you do step 4 Open an ADB shell with elevated permissions. Sorry for the stupid question.
[Ouya Android Development] TadeoNYC:
You really should just watch an adb tutorial on YouTube, because I'm not sure what it is that you don't understand at this point. I'm a complete noob to android and Linux and figured this out in a few hours. If you are this uncertain about what to do, maybe you shouldn't do it.
[Ouya Android Development] tennisbgc:
actually it turns out on the instrustion for setting up adb im not getting a device number after I input this

adb kill-server

echo 0x2836 >> "%USERPROFILE%\.android\adb_usb.ini"

adb start-server

adb devices
[Ouya Android Development] TadeoNYC:
Okay, go through this thread and look at all the steps others took to troubleshoot the device not being functional in the device manager in system panel. I told you to do this earlier, have you?

Let us know what type of device ouya is listed as in the device manager.
[Ouya Android Development] tennisbgc:
its listed as a portable device.What should it be listed as?
[Ouya Android Development] TadeoNYC:
Since mine isn't connected I'm not certain but I think it should be mtp. You need to go I'm too advanced properties and make sure it using adb drivers, if it isn't you need to manually add them by selecting update driver and then selecting have disk and pointing it to the adb driver.

Search Google, this exact problem is out there with much more of a walkthrough then I have time to provide.
[Ouya Android Development] simbaba:
Hello,

I follow exactly and i have 3 errors :

------------> Superuser is installed but can't update.
[Ouya Android Development] gianptune:
it looks like you mistyped something. "sumount: not found" maybe you forget to press 'enter' between 'su' and 'mount'. and later you have 'exitexit' this is supposed to be 'exit', <press enter>, 'exit'.
[Ouya Android Development] Theraze:
su and mount are two different commands. On different lines. Not a single command named sumount.

Or to say it differently... hit enter after step 4.
[Ouya Android Development] mfg_Static:
Whenever I type this it says

1|shell@android:/ $ su cat /sdcard/su > /system/xbin/su

/system/bin/sh: can't create /system/xbin/su: Read-only file system

and:

1|shell@android:/ $ ln -s /system/xbin/su /system/bin/su

link failed File exists

Any ideas what this could be?

I skipped this 2 parts and could install the apks, but I cannot update the superuser, because it fails with a error, and other apps doesn't seem to have root access.
[Ouya Android Development] elmerohueso:
You combined two commands into one. "su" is one command (to get elevated privileges), and "cat /sdcard/su > /system/xbin/su" is the next command.

______________________________________________________________________

I decided I'd clarify and simplify the steps a bit..

Note: Each command is on its own line. If box of code has 2 lines, it's 2 different commands. Press ENTER after each command.

Setup wired and/or wireless ADB, according to the steps at http://xdaforums.com/showthread.php?t=2272266

(Recommended) Put the full path to adb.exe in your Windows PATH variable so you can run it from anywhere

Download and unzip the SuperUser files from http://d-h.st/BBk (if you skipped step 2, you must extract these files to the same directory as adb.exe)

Open a Command Prompt/Terminal window and navigate to the directory with your extracted files

Push su to the sdcard

adb push su /sdcard/su

Open an ADB shell with elevated permissions

adb shell
su

Mount the system partition as read-write

mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP

Cat su into /system/xbin

cat /sdcard/su > /system/xbin/su

Create a symbolic link to su in /system/xbin from /system/bin (safer/cleaner than just putting su directly in the bin folder)

ln -s /system/xbin/su /system/bin/su

Set the su permissions to -rwsr-sr-x

chmod 6755 /system/xbin/su

Exit the ADB shell

exit
exit

or CTRL + C

Install SuperUser

adb install com.koushikdutta.superuser.apk

Install BusyBox

adb install stericson.busybox.apk

Run SuperUser on the OUYA (Make > Software > SuperUser) and allow it to update
[Ouya Android Development] mfg_Static:
Hi,

I tried this of course as well, because it I'd already written in the howto like that, but I had no success.

I finally managed to do it by sideloading the ota again, and then rooting again.

Now I also got a # instead of a $ when using su.

Everything then worked as described.

When there are other people out they with this particular problem: factory reset doesn't reset that files, try to sideload ota again and then it should work.

- Sent from Nexus 4 with Tapatalk
[Ouya Android Development] JebyDroid:
su is not working for me after I do

./adb shell
su

nothing changes and still I get

Operation not permitted

why?
[Ouya Android Development] Z51:
Tagging for later
[Ouya Android Development] elmerohueso:
Something must be wrong with your image. This issue usually happens if you've messed with su already (the one that comes built in) and either changed its permissions or removed it. You'll need to grab the latest OTA zip and flash it via recovery.
[Ouya Android Development] JebyDroid:
Thank you, I've only installed the CWM :angel: maybe is that one!
[Ouya Android Development] Kpyto:
Hello!

What is the root (su) password for ouya? ALPINE pass is not working :(
[Ouya Android Development] Silverbulletncsu:
I at random received an ota (same as what I already had) downloaded and installed. Rebooted and lost root.

What do I need to do to regain root? Same process or something different since these files have already been pushed and installed once?
[Ouya Android Development] TadeoNYC:
This question was asked and answered starting with post 17.

I would just do one click now.
[Ouya Android Development] PieOfJustice:
On "

./adb push su/system/bin/su /sdcard/su" it is Not Found.

I can do the first part of the instructions and open adb shell.
[Ouya Android Development] exitdust:
every time i enter the command 'su' i get permission denied...
[Networking] micken:
Anyone any experience of this, it's the first year that I will have a GPRS handset on holiday.
[Networking] romman:
02 GPRS France

I use 02 GPRS in France with no problem at all.

Just beware though, they charge something like £ 1.50 for connection in a 24 hour period and about £ 7.50 per MB !!
[Networking] micken:
:shock: :shock: :shock: :shock:

I think I'll disable it just in case it connects accidentally.

Many thanks romman
[LG Optimus 3D] @cyberspace:
I currently have this custom ROM installed http://xdaforums.com/showthread.php?t=2199659. Can I flashed directly the bootv21E ROM? I want to returned back to GingerBread.

Thank you!
[Xperia Arc Q&A, Help & Troubleshooting] padam.jeetsingh:
Hello Experts and Mod

I am new to this whole thing of playing with OS and Phone.

I have Xperia Arc (LT15i) running on 4.1.B.0.587, and its rooted.

I would like to update my phone to CM10.1 - Build 20130507 , I would appreciate , if someone can guide me on what all steps needs to be taken to update my phone. It will be great if you can share corresponding links or videos for the guidance.

Hoping to explore my phone in whole new way.

Thank you
[Xperia Arc Q&A, Help & Troubleshooting] Someguyfromhell:
1. Backup all your data, contacts, apps, SMS - whatever you need. Use Titanium Backup for apps.

Phone memory will be lost, everything on SDcard will stay.

2. Unlock your bootloader - unlockbootloader.sonymobile.com

3. Download the CM10 ROM for anzu.

4. Extract the kernel from inside the .zip file (kernel is in .img format). If you wish to use another kernel, for example nAa 3.0.8 or Fusion, then find them from Development section and download them.

5. Install the kernel via fastboot. Search for more info on this.

6. Enter the Recovery. Make sure phone is turned off, then turn it on, when kernel bootlogo appears, start clicking Volume Down button until a menu appears. Once there, use volume, home and back buttons to navigate.

7. Do a full nandroid backup, choose Backup and Restore and Backup. This will save your whole ROM and data, so you can restore your phone to that state later.

8. Choose Wipe Data/factory reset option to clear tracks of old ROM. You don't need to do anything else, otherwise you just waste time.

9. For CM ROMs, you must not format /system, if you find a guide that says it. Otherwise you get problems.

10. Then, back to main menu of the Recovery, choose install zip from sdcard, choose the zip file from sdcard and install it.

11. Once done, reboot your phone and let it boot.

Some people recommend to wipe cache, dalvik cache, battery stats etc. Factory reset already removes them so you do not need to do these again.
[Xperia Arc Q&A, Help & Troubleshooting] padam.jeetsingh:
:good::good::good:

Thank you for helping through this.....I have updated to Unofficial CM10.1 - Build 20130507. Now Touch is not working , its keeps on flicking between options......I am not able to use my phone , if I have to click any option , I have to Lock my screen and unlock it .

Please suggest , what can be done...thank you
[Xperia Arc Q&A, Help & Troubleshooting] popthosegaskets:
Did you follow the steps properly?

For CM10.1, use included kernel boot img in zip file.

僕のLT18iから送られてきた
[Xperia Arc Q&A, Help & Troubleshooting] Someguyfromhell:
Did you install the correct version for your phone? That is, did you install the one for Arc/anzu(codename for Arc)?
[Xperia Arc Q&A, Help & Troubleshooting] padam.jeetsingh:
Thanx Members..

Yes I did followed the steps .

I used the kernel from the zip file (boot.img). I also skipped point 7.