yashsingh1/xdaforums huggingface dataset:
[T-Mobile LG G2x] nydmt:
kk i am very desperate for help

i have been seeking help regarding rooting my optimus 2x for 2 months

heres the story:

i rooted my phone using superoneclick and everything worked out fine

then i flashed MIUI on my phone and it worked fine except the GPS was very slow

then i had flashed a recovery rom to go back to the stock Froyo

then i flashed Cyanogenmod 7.1 and it worked fine

i saw that MIUI had some new updates and that it was much better than Cyanogenmod in my opinion

So i went to ROM Manager and tried to reboot my phone into recovery but nothing happened at all

I've tried every way to boot into recovery but it goes to the stock recovery

I downloaded a root checker and it tells me my device is not rooted

now when i try to use superoneclick i get stuck

can any1 please help me

i've been posting in the superoneclick forum and no1 has been able to help me for 2 months
[T-Mobile LG G2x] ed116:
lol, use NVflash one click and flash CWM, you dont even need root, flash it then flash another rom.

if that doesnt work: factory reset, unroot, then re-root
[T-Mobile LG G2x] iheardulkwaffles:
Help me too!

I know this is going to sound incredibly dumb (and thats because i barley know anything about all of this stuff)

I've been trying to root my LG G2x for a couple days now, but it just wont work.

Ive followed all the steps to use superoneclick to root my device and the program works as far as i can tell. It finishes step 7 and gives me this message: "Killing ADB and restarting as root... enjoy!"

Unfortunately before i can even use my phone more messages start flowing out. I have absolutely no idea what any of it means, but the program and my phone both crash until i hard boot both so i would really appreciate any help!

This is the message i get: "$

$ export TEMPRANDOM=29169;export PS1=END:$TEMPRANDOM;/data/local/tmp/busybox mount -o rw,remount /system

mount: permission denied (are you root?)

END:29169export PS1=""

export TEMPRANDOM=92557;export PS1=END:$TEMPRANDOM;/data/local/tmp/busybox mount

rootfs on / type rootfs (ro,noatime)

tmpfs on /dev type tmpfs (rw,relatime,mode=755)

devpts on /dev/pts type devpts (rw,relatime,mode=600)

proc on /proc type proc (rw,relatime)

sysfs on /sys type sysfs (rw,relatime)

none on /acct type cgroup (rw,relatime,cpuacct)

tmpfs on /mnt/asec type tmpfs (rw,noatime,mode=755,gid=1000)

tmpfs on /mnt/obb type tmpfs (rw,noatime,mode=755,gid=1000)

none on /dev/cpuctl type cgroup (rw,relatime,cpu)

/dev/block/mmcblk0p1 on /system type ext3 (ro,noatime,data=ordered)

/dev/block/mmcblk0p7 on /data type ext3 (rw,relatime,data=ordered)

/dev/block/mmcblk0p2 on /cache type ext3 (rw,nosuid,nodev,noatime,data=ordered)

tmpfs on /mnt/extasec type tmpfs (rw,noatime,mode=755,gid=1000)

/dev/block/mmcblk0p6 on /nvdb type ext3 (rw,nosuid,nodev,relatime,data=ordered)

/dev/block/vold/179:8 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)

/dev/block/vold/179:8 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)

tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)

/dev/block/vold/179:17 on /mnt/sdcard/_ExternalSD type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)

/dev/block/vold/179:17 on /mnt/extsecure/extasec type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)

tmpfs on /mnt/sdcard/_ExternalSD/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)

END:92557export PS1=""

"
[T-Mobile LG G2x] chipis:
Yeap.. nvflash works. I tried the oneclick root. And got the same error as below... its a little complicated at first, because you have to do the steps onthe computer with the nvflash . After that i plugin the phone as thesteps and BOOM,no need to root, i am using a custom rom. Its fast my phone with two Dragon inside hell yeaaa....
[T-Mobile LG G2x] nydmt:
can u tell me exactly what u did? like step by step?
[T-Mobile LG G2x] jboxer:
Go to the root thread in my signature and then in that thread there is a link to the One Click Recovery Flasher using NVFlash. That thread is detailed, step by step and even has a link to a video. Not to be a smartass, but if you cannot follow that thread to install recovery on the phone then you should not be flashing roms on your phone. This is basic stuff you need to know and understand first or you are going to royally screw up your phone.
[Xperia Arc General] butchy93:
Hello, I have a bug with my wife's new Xperia Ray.

In the stock SMS app, some contacts don't have the quick reply bar, with send button and attached part.

I don't know where is the problem. I have ever re-flash the phone in 4.0.2.a.0.42.

Bug screenshot

View attachment 789460

No bug screenshot

View attachment 789454

Help me please.
[Xperia Arc General] electrash:
Send mail to SE or contact them on chat on their site, they will know what is it.

Best luck.
[Xperia Arc General] xtacy!:
Try holding down the Menu button. It might force the keyboard up. It's worth a shot.
[Xperia Arc General] butchy93:
I've tried, the keyboard up but the Send button doesn't appear
[Xperia Arc General] xtacy!:
For the time being, just try creating a new message each time. The new message screen possibly has the send button.
[Xperia Arc General] zonetrooper90:
Have you tried doing a system repair with PC Companion?
[Xperia Arc General] eccomania:
Could you check that number maybe its not saved as mobile number and makes problem ? Try to save it mobile once more ;-)
[Xperia Arc General] butchy93:
I was restoring old messages with sms backup and restore. It was the problem. So i reflash with SEUS and didn't restore messages and the problem seems to be solved.

Thanks for your help
[HTC Radar] chancooluk:
Hi

Is anybody else having issues with the sound enhancer app (in the settings menu)?

It doesn't function at all on my phone, there is no difference when srs is selected, and there doesnt appear to be any change when selecting an equalizer setting when earphones are connected.

Id really prefer not to reset the phone and delete my txts and settings...etc

Is there anything i can do to fix the problem?
[T-Mobile myTouch 4G Slide] masterkamon842:
Really smart move from the mods in xda, to remove the most active and helpful dev for the mt4gs forum, just for past personal issues... I didnt get along good with him, but he was very helpful, always participated and with his contributions encouraged more devs to work for the mt4gs.

Once again, not very smart mods... Forums are meant to be open, not restricted, as long as its regarding the topic of the forum, and that's all he did.

I might get banned and/or this post deleted, but i just had to give my opinion. Boop.
[T-Mobile myTouch 4G Slide] rei165:
What happened this time? Read the jist of it in your post but don't know details.
[T-Mobile myTouch 4G Slide] Litesorrows:
He's not gone, just off XDA. It suck major Donkey, but a true dev will dev no matter what. Undead is the stuff, love his roms :D *saw a post saying the dev was a male*. Rootzwiki is gonna have to be the new home of the Doubleshot :D
[T-Mobile myTouch 4G Slide] xT4Z1N4TRx:
What happened :o
[T-Mobile myTouch 4G Slide] Litesorrows:
The Hub Hub is that he was banned because of something he hade did a while ago. Its lame, there murding the Last good qwerty for T-Mo. Our Device was completly overshadowed by the Sensation.
[T-Mobile myTouch 4G Slide] texasaggie1:
lame

really lame XDA. I will change this if a mod will explain why this happened. What's the address of rootzwiki??
[T-Mobile myTouch 4G Slide] giangdude:
the_scotsman briefly explained it already. He was banned previously because he caused a lot of problems. Then he got around the ban by making a new account (which is against the rules) so he got banned again. Or at least that's what I understood from it.
[T-Mobile myTouch 4G Slide] mcdeezy:
From what I noticed is he was soooo arrogant and rude. He was always quick to jump on a noob for posting something wrong but as soon as you said something about one of his ROMs he would get pissy with you. Good riddance.
[T-Mobile myTouch 4G Slide] Techlvr:
That is true but he was getting better about that stuff.
[T-Mobile myTouch 4G Slide] masterkamon842:
Yes its true he was rude, but nevertheless he would help you out, not like other devs wich you might get lucky if they respond a question of yours. On top of that, he was the only one truely dedicated to the doubleshot. Others dev for us on their free time. Yes he is in rootzwiki and now so am I, but i really liked the simplicity in this forum... Oh well...
[T-Mobile myTouch 4G Slide] dung8604:
Have you ever had to do something you didn't want to because it was your job? Let's face it, the mods don't ban people for topics list this, they allow you to express opinions, etc. But if they allow everyone the leniency you are asking for, this entire forum would be a mess. There are few things that actually get you banned, and undead violated a few of them, several times. It sucks big big balls for us, but look at the big picture before calling out the admins. Overall, this entire forum is a better place because of what they do, positive or not.
[T-Mobile myTouch 4G Slide] dhkr234:
This is a knee-jerk fear based response from the clowns in charge here. It happens in a lot of places. There are TWO kinds of rude people -- stupid rude, and brilliant rude. Brilliant+nice practically doesn't exist on this planet. It is because there is a natural friction between intellect and ignorance. Neither can see from each other's perspective because their perspectives are so absolutely foreign to each other. It ends in a great deal of frustration between the two groups, which ultimately comes out as RUDENESS.

In both directions.

Now fact of the matter is that if you ban everyone who is RUDE, you ban everyone you actually need in order for this system to work to begin with. You can have developers who are rude mixed in with users who are not nearly as knowledgeable, or you can ban everyone with knowledge and intelligence and have a bunch of whiny users, among whom there is not a single one with the ability to actually push the PURPOSE of the forum to being with.

Two choices: Either accept a bit of rudeness and condescension, OR, shoot yourself in the head. Can't have it both ways.
[T-Mobile myTouch 4G Slide] Madblaster6:
True, but many will agree he erned his way back.

Sent from my mt4gs
[T-Mobile myTouch 4G Slide] masterkamon842:
Well the least the admins can do is tell us what really happened, since we the community are the affected ppl... Not just say "for past issues". That makes me think its personal. And if it is, then they are just pricks for messing up the main doubbleshot dev.
[T-Mobile myTouch 4G Slide] unclespoon:
I picked up the Galaxy S II yesterday. I'm out. No more dev support and potential wasn't really there anymore even though the phone was great.
[T-Mobile myTouch 4G Slide] CoNsPiRiSiZe:
Yepp. switching to Verizon tomorrow (or later IDK, but soon i know that) and picking up a Droid RAZR.
[T-Mobile myTouch 4G Slide] DistrictDigital:
He's still developing, he's just at RootzWiki...
[T-Mobile myTouch 4G Slide] Droidmoder:
He kanged a few roms without permission as teamjokerface name. That was one of the biggest things plagurisim I suppose.

My thing is he leanred from his mistake and improved his ethics. The fact that he made a new name and improved himself should be an awsome acheivement nota ban.
[T-Mobile myTouch 4G Slide] the_scotsman:
Basically this is correct.

If any of you recall TeamPokerFace, we banned him many months ago for several reasons, including a lot of epic kanging and being a read idiot.

Undeak=TeamPokerFace

Creating a new account just to get around a ban is something we never have and never will allow, regardless if they have "changed" or not.

Thank goodness we have people like you here :)

You have

absolutely

no idea what you are talking about...it has NOTHING to do with anyone being rude...so please refrain from making stupid assumptions about us :rolleyes:

And now that you have the reason, there's no longer a need for this thread to remain open.
[Samsung Galaxy Nexus] Matcarroll:
Sent quite a few text messages and emails today and closed both the applications a few times in error as the homepage button is right under the space bar and very sensitive!

I suppose I will get use to it however with time.
[Samsung Galaxy Nexus] NexusDro:
This is what I fear the most when I first heard about the software button. Hopefully my fingers will get used to it.
[Samsung Galaxy Nexus] _hyperdude:
It's not too different from having a capacitive button right below the screen. Just need to type a little slower I'd say
[Samsung Galaxy Nexus] Deleted member 2842059:
http://www.youtube.com/watch?v=eTMpctKxY3E&sns=em

He agrees with you.
[Samsung Galaxy Nexus] Tjotte:
Type in landscape mode ;)
[Samsung Galaxy Nexus] Chirality:
Yeah, I'd say having software buttons and having capacitive buttons are both equally bad for this reason. This is why I prefer real physical buttons.
[Samsung Galaxy Nexus] Deleted member 2842059:
YT guy also agrees with you. Win. Win.
[Samsung Galaxy Nexus] appelflap:
Try a keyboard on which you can set the height of the bottom row. Thumb keyboard for example :) or smart keyboard. Btw as the developer of thumb keyboard I plan to add an option to add extra space under the bottom row of the keyboard so it floats a bit above the keys.
[Samsung Galaxy Nexus] player911:
They just need to make the softbuttons hide when the keyboard is open. Not hide completely but minimize so it would require 2 taps. One to maximize the buttons and one tap to go. Or shuffle them around. Or add a forth softbutton (search?) So the alignment isn't directly below it.

It happens even on my G2x. I think its just growing pains when moving into a larger screen. Going from a Nexus One to a G2x (3.7" to 4") messed up my typing until I got used to it.

G2x - 2.3.7 CM7

Transformer - 3.2 Revolver OC/UV
[Samsung Galaxy Nexus] Chirality:
I think Google just needs to figure out that having a virtual home button is a really ****ing dumb idea. Apple figured this out with the iPhone 1. Why the **** can't Google get a clue already?
[Samsung Galaxy Nexus] Aridon:
Take a pill and chill on the language.
[Samsung Galaxy Nexus] onthecouchagain:
You're the fellow behind Thumb Keyboard? I love TB Keyboard! I've emailed you a few times about custom auto-corrections. Please implement them soon! :D It's the only one single thing missing from TB Keyboard.

Edit: And yes, I can vouch. Thumb keyboard is excellent and allows you to adjust the space bar line.
[Samsung Galaxy Nexus] appelflap:
I'm working on a update in which I want to include the new spellchecking options offered by Ice cream sandwich. When working on it I also want to look at some options to customize the suggestion model. For now I'm planning to add the new ICS suggestion model as an option. For me it isn't as useful as the current suggestion model used, but I'm sure for others it will fit their typing style better.
[Samsung Galaxy Nexus] martonikaj:
Settle it down a little bit man...
[Samsung Galaxy Nexus] onthecouchagain:
That sounds terrific.

Will custom auto corrections be in an update after that? I think since everyone types a little differently and thus makes their own mistakes, custom auto corrections will go a long way in helping everyone's typing. For example, I know I constantly hit "km" instead of "I'm". It'd be great if I could set up a custom correction where every single "km" typed will correct to "I'm."
[Samsung Galaxy Nexus] r3k0:
landscape ftw tbh ;)
[Samsung Galaxy Nexus] player911:
Virtual buttons are awesome. They just need tweaks. Perhaps just reordered. Or perhaps make the icons further down on the screen and make the hit area smaller while the keyboard is up. There are lots of solutions.

Just needs tweaked.

G2x - 2.3.7 CM7

Transformer - 3.2 Revolver OC/UV
[Samsung Galaxy Nexus] Chirality:
What's good about virtual buttons?
[Samsung Galaxy Nexus] Deleted member 2842059:
They are virtual? (I had to guys.)

For starters? No physical buttons = bigger screens for the same real estate since you don't have to have the space for actual physical buttons and as an added bonus less complexity and chance of something physical breaking or going wrong in the device since it's all screen. You could argue that costs come down do to less hardware and time to actually make a device that's all screen. I'd also say if you wanted to add something down the line with the virtual buttons it's easy: software tweak.
[Samsung Galaxy Nexus] Aridon:
You can do a lot more with software than you can with hardware.
[Samsung Galaxy Nexus] Chirality:
Nope, you are not getting any more screen real estate, not with the way ICS does it. The buttons are almost always taking up part of the screen. Yes the costs come down, I'm sure that's why the manufacturers like their virtual buttons and capacitive buttons so much. But I don't see how that's good for me: I'm still paying the same price for the phone. And when was the last time you heard somebody have problems with physical buttons breaking while the phone is not obselete?

Here's something you can't do with software: provide real haptic feedback and use physical displacement to prevent accidental activation.
[Samsung Galaxy Nexus] robrob777:
Yeah I was thinking this too, the soft buttons are not the best idea in the world, they are innovative but not practical IMO.

I had the HD2 with some arrow buttons below the space bar and I was always pressing them, drove me crazy (in winmo6.5, thanks God somebody ported Android to it)

In the nexus S with capacitive buttons I don't have that problem at all when typing messages.

So there is a difference for me btw soft and capacitive buttons.
[Samsung Galaxy Nexus] sauron0101:
The problem is that software buttons is probably going to be worse than capacitive buttons. With capacitive, at least there was a gap between the screen and the buttons. Software buttons though ... no gap means that it's easier to accidentally press.
[Samsung Galaxy Nexus] rogercoda:
I'm surprised I haven't seen this mentioned yet, but one thing I love about software buttons, is that you receive visual feedback from pressing them, whereas with capacitive your sole reliance is on haptic feedback, which can sometimes be a slight annoyance
[Samsung Galaxy Nexus] kristovaher:
Well, there is a simple response to that. Virtual buttons are future proof. Should Android decide to change things around within a year, your buttons will also be changed, for example if they decide to put Search button back.
[Samsung Galaxy Nexus] JRK-Scope:
I have to wonder. Will there be a future tweak to add a call and end button in the virtual space?
[Samsung Galaxy Nexus] Chirality:
Good points. But let me ask you this: what would you prefer out of these two options:

Option 1: buttons that give you visual feedback and are future proof in case the layout needs to be changed.

Option 2: buttons that give you physical feedback, and need to be physically depressed to activate to prevent accidental activation.
[Samsung Galaxy Nexus] kristovaher:
I prefer non-physical keys for the same reasons why I prefer touch-screen keyboard. People are different, some like physical buttons, some not.

I am fine with power and volume being physical buttons, since both serve a function even when you are not looking at the screen, but on-screen buttons are much better for me, even if only because of visual feedback, future proof approach and more screen space for videos.

The phone also looks much better when turned off, I've never liked physical buttons gathering dust or becoming visibly worn out.
[Samsung Galaxy Nexus] sauron0101:
Option 2 of course.

Android will have to maintain at least some degree of backwards compatibility with the traditional 4-button layout anyways for at least a year or two.
[Samsung Galaxy Nexus] Egan:
They should add the option for double tap, to prevent accidental activation. Wont you agree and find this a good solution?
[Samsung Galaxy Nexus] mcfar45:
Is there any chance that we could see Mods and ROMS which tweak the button layout to be ordered in other ways/add other buttons. For example, I am used to the HTC button layout and so it would be nice to have the software buttons ordered like this.
[Samsung Galaxy Nexus] zarch1972:
Tweak Here to allow different "Legacy Menu" button combo's.

http://android.modaco.com/topic/348762-21-nov-legacy-menu-patches-lhs-rhs-both-normal-always-on/
[Samsung Galaxy Nexus] Eggcake:
Why not hide the buttons when the keyboard is open? Or minimize them.
[Samsung Galaxy Nexus] Gundea:
It's also possible to implement a heuristic for determining whether or not the touch of the software button was accidental or intentional, it has the possibility to misfire, but that could be rectified by a quick second touch.

Another solution might be to keep the buttons in low profile mode in more cases?
[Samsung Galaxy Nexus] Chrono_Tata:
I don't think the low profile mode prevents accidental button presses. It literally just makes all the icons little pale blue dots. (Yay Carl Sagan reference)
[Samsung Galaxy Nexus] bigmout:
Physical buttons are more prone to accidental activation when in pockets or purses.
[Samsung Galaxy Nexus] Chirality:
That's why we have lock screens...
[Samsung Galaxy Nexus] kristovaher:
Exactly, he pointed it out because it was pointed out before as if hardware buttons are better in that regard. They are not. And neither matter if there's a lock screen.
[Samsung Galaxy Nexus] seakins:
Actually, I have found that when the buttons are in low profile mode. I have to press it once to change them back to the actual button form and then press again for the button to preform the action.

So yes, probably having the buttons in their low profile mode more often would work for me.
[Samsung Galaxy Nexus] Chrono_Tata:
In which app are you getting this behaviour? Because I'm trying the low profile mode in the Gallery and one press is all it takes to activate any of the 3 buttons.
[Samsung Galaxy Nexus] blunden:
When watching video you get the full size of the screen so what he said was true in some instances. That's when it matters the most to me. :)

That gap is just a software thing. The capacitive buttons use the same digitizer as the rest of the screen but they might discard input from some areas. That could be done now too if they realy wanted to.
[Samsung Galaxy Nexus] Chirality:
Uhh...hardware buttons are better at preventing accidental activation when you are using the phone. In your pocket or your purse, hardware buttons and software buttons are the same, because neither can get past the lock screen.

I don't see anybody here talking about how hardware buttons are better in pockets or purses.
[Samsung Galaxy Nexus] bigmout:
Not necessarily. A hardware button that activates the screen can cause all kinds of mischief, especially in a pocket where your body may unlock the lockscreen. For example, I have my trackball set to wake my Nexus One, and have occasionally unlocked the phone and activated apps just by walking.

Also, while we're on the subject, hardware buttons tend to fail over time. The Nexus One power button and trackball issues are examples.
[Samsung Galaxy Nexus] Chirality:
Well, there's your problem.