CM7 DX2 No clue my back and home key decided to switch places any help?
Sent from my MB870 using xda app-developers app
116 Views and no response¿:what:
Sent from my MB870 using xda app-developers app
I dont know what causes that and I have never had that problem. But you can use a root file browser (I suggest root explorer) and navigate to /system/usr/keylayout/ and open the tegra-kbc.kl in a text viewer. Here, you can see what action each button is linked to. I'm attaching a screenshot of what mine looks like. Let me know if yours is the same.
I think so weird
Sent from my MB870 using xda app-developers app
Hmm. I dont know why it would be reversed then. I think I remember other people having this problem but I dont know much about it. It could be an app doing it. If you cant figure it out and its bugging you that much, maybe try booting into the CM7 recovery, wipe cache and dalvik and flash the ROM again. You shouldn't lose anything as long as you dont wipe data. Flashing the ROM again should put all your system files back in order though. Its worth a shot. Backup everything if you'd like though.
Lol I rsd sfb wiped flushed reloaded you name it... No clue
Guess I live with it? `
Sent from my MB870 using xda app-developers app
Really? I would think for sure that an SBF would do it if nothing else. That doesn't make sense. I have no clue then.
I was baffled too that's why I postEd in hope thanks n e way
Sent from my MB870 using xda app-developers app
this has been reported several times, but no real answer has been found, that I have seen
likely bad .sbf download
verify .sbf checksums with MD5 & SHA-1 Checksum Utility,(use to verify the hash/checksum to ensure the file integrity is correct with the matching file)
2.3.4 VRZ_MB870_4.5.1A-DTN-150-30_1FF_01.sbf MD5 Sum: B814E7086EEF6DF6CAFFC3763023B1AE
or try a different .sbf,
use ezSBF,
use 2.2, or 2.3.3 and take ota update
---------- Post added at 05:54 PM ---------- Previous post was at 05:52 PM ----------
or you can manually change them back with simple key remapping
read [Mod] Search button as Camera button (key remapping)
Checked and verified first & second download .
It seemed to happen quite a while after I thought it was stable unless anybody knows of a simple fix I'm just going say [email protected]$# it and leave it.
Ty ty I just flipped the #'s and problem fixed thanks for all your help
It happened to me SBF'n out of my worst brick yet with RSD Lite 5.3.1. I would see the "M" for not even 1 second before the screen read "FAILED TO BOOT 1". Luckily, our "M" load screen is default RSD mode even if your Dx² wont respond to the hard button boot commands, BUT IT HAS TO BE DONE ON RSD 5.3.1. to get out of this brick... only drawback is, home & back are switched. I bet once upon a time, anyone who has this flip, has used RSD 5.3.1
Sent from my MB870 using xda app-developers app
Nope rsd 5.7 newest I think but good guess
Sent from my MB870 using xda app-developers app
5.7 will unbrick the hardest of em from the mbm default logo? If so that's great ... cuz everyone I know that's hadda solid brick an used 5.3.1 to RSD had their keys flipped as well
Sent from my DROID X2 using xda app-developers app
Related
Alright I have the latest Group build, but with it, the software keys (home, menu, back, search) don't light up. I saw there was a fix for it, but how do I apply it?
Thanks!
Sent from my FroyoEris
The fix doesn't really work in my experience. The softkeys light up at weird intervals post fix and never when its actually useful. But if you want to try it download the zip file from the FAQ page and put it in the root of your SD card. Then boot to recovery and flash it. I ended up flashing the fix for the fix though cause it got annoying.
Good luck.
Todd
Sent from my FroyoEris using XDA App
toddsts said:
The fix doesn't really work in my experience. The softkeys light up at weird intervals post fix and never when its actually useful. But if you want to try it download the zip file from the FAQ page and put it in the root of your SD card. Then boot to recovery and flash it. I ended up flashing the fix for the fix though cause it got annoying.
Good luck.
Todd
Sent from my FroyoEris using XDA App
Click to expand...
Click to collapse
if you just wait your better off, once kaos actually fixes it it will be fine the soft_key_fix.zip is kind of a temporary fluke fix it just makes them light up in general not when they should.
For me it works only in my room don't know why but works only there maybe its because the sensor
Sent from my FroyoEris using XDA App
I'm currently running the supercharged script on my phone and I was wondering if it was safe to factory reset the phone. Also would I lose the supercharged script?
While you're here, can someone tell me how we get into stock recovery? Same as the X?
Sent from my DROID X2 using XDA Premium App
Bump? Does anyone know?
Sent from my DROID X2 using XDA Premium App
If you are doing a factory reset, I would remove the supercharge script and reapply it after the fact. Can you elaborate on the stock recovery... not sure what it was like on the X.
To pull up the Android Recovery, power off the phone, holding the volume down button power on the phone. Release both buttons when you see "Fastboot". Press the volume down button until you see "Android Recovery" and press both volume buttons. Not sure if this is the same as what you are looking for or not.
Ok, exactly what I was looking for. Should I also restore bloat or can that stay frozen?
Sent from my DROID X2 using XDA Premium App
If you restore with apps frozen, it will more than likely unfreeze them by default. I've never done a factory reset with frozen apps myself, but that is the going consensus. On a side note, if you want to leave the supercharge script in place, you can verify it is still running using the script manager after the reset. Setting up the supercharge script isn't very hard to do.
Alright thank you for the info sir. I always had a custom rom to depend on with my Fascinate so its a bit of a challenge with this one.
Sent from my DROID X2 using XDA Premium App
I used to use this app on my old phone (Rooted/ROM'd LG Ally). Would there be any issues with it on my new X2? I'm running Eclipse 0.1 with the custom recovery installed. I've hit the "Reboot" button and that works fine. I'm afraid to hit the "Recovery" button.
Why not try it and see? I don't think booting into recovery is going to harm you phone at all. It may just reboot and not enter recovery if that command is intended for CMR or it may enter Bootstrap Recovery. It's really hard to say because I have not used the program myself. No harm in trying. If something does go wrong just pull your battery.
yea you can use it. i use it all the time. if you download the app and go into settings, you can choose wich boots you can choose. by this i mean you can opt to take out the recovery option from the menu when you open the app.
Tried it out and it boots it to stock recovery but not the custom one. Thanks for the responses.
Sent from my DROID X2 using XDA App
matts175 said:
Tried it out and it boots it to stock recovery but not the custom one. Thanks for the responses.
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
Try the same thing plugged into a wall charger.
Sent from your Mom's house using Tapatalk
mistawolfe said:
Try the same thing plugged into a wall charger.
Sent from your Mom's house using Tapatalk
Click to expand...
Click to collapse
Good idea. Just tried it and still boots to stock recovery. I found a widget on the market that's working out for me. Its just a simple reboot button.
Sent from my DROID X2 using XDA App
matts175 said:
Good idea. Just tried it and still boots to stock recovery. I found a widget on the market that's working out for me. Its just a simple reboot button.
Worth a shot...
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
Sent from your Mom's house using Tapatalk
I think it's rather silly that the stock power button options do not include reboot. I mean, it has sleep for crying out loud.
zakth said:
I think it's rather silly that the stock power button options do not include reboot. I mean, it has sleep for crying out loud.
Click to expand...
Click to collapse
+1
Sent from my DROID X2 using XDA App
Just uninstalled Go launcher and locker. Now my Att note,running Gb stock, will not lock and show the password screen. Please advise??
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Second party lock screens are not the best for some one wanting password etc lock.
sent from my ICS powered gNote
Go to settings and set up a password lock.
-Once you go NOTE, you'd say 4 inches a Joke
SKyRocKeting727 said:
Go to settings and set up a password lock.
-Once you go NOTE, you'd say 4 inches a Joke
Click to expand...
Click to collapse
This is definitely the way to go for security!
Sent from my Icy G-Note Beast....... 0_o
I did. Still not working!
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
When removing some apps, they leave behind files in your phone so it doesnt completely gets removed. I think the go locker left some files in your phone to cause this. Try going into your my files folder, and delete any go launcher and go locker folders. It might just work.
-Once you go NOTE, you'd say 4 inches a Joke
It may be a corrupt efs. I had the same problem but mine happen because of a bad radio flash. This fixed it for me. (I used fix.zip )
Good luck
forum.xda-developers.com/showthread.php?p=25139907
Sent from my SAMSUNG-SGH-I717 using xda premium
tagmwar said:
It may be a corrupt efs. I had the same problem but mine happen because of a bad radio flash. This fixed it for me. (I used fix.zip )
Good luck
forum.xda-developers.com/showthread.php?p=25139907
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Phone is not rooted...thnks though.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
SKyRocKeting727 said:
When removing some apps, they leave behind files in your phone so it doesnt completely gets removed. I think the go locker left some files in your phone to cause this. Try going into your my files folder, and delete any go launcher and go locker folders. It might just work.
-Once you go NOTE, you'd say 4 inches a Joke
Click to expand...
Click to collapse
Thanks...but still not working. I erased folders and rebooted...i had lockscreen until the first timeout
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
reinstall the applications clear the cache then uninstall
drksilenc said:
reinstall the applications clear the cache then uninstall
Click to expand...
Click to collapse
Did that and same result.. Thanx
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Ceasare said:
Phone is not rooted...thnks though.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
Just because it's not rooted does not mean the keystr file is not missing.
Sent from my SAMSUNG-SGH-I717 using xda premium
What launcher are you using? Are you running a ROM? Tell us some info about what youre running currently.
-Once you go NOTE, you'd say 4 inches a Joke
SKyRocKeting727 said:
What launcher are you using? Are you running a ROM? Tell us some info about what youre running currently.
-Once you go NOTE, you'd say 4 inches a Joke
Click to expand...
Click to collapse
Using touchWiz, running gingerbread 2.3.6, stock unrooted. (Im waiting for the offical Ics)
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Wipe data/ factory reset. If it does not fix your issue. odin the stock tar
tagmwar said:
Just because it's not rooted does not mean the keystr file is not missing.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Excuse my ignorance(noob), but what is a keystr file and where is it found?
Finally, are all launchers this invasive?
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Ceasare said:
Excuse my ignorance(noob), but what is a keystr file and where is it found?
Finally, are all launchers this invasive?
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
I am not dev so they may be able to explain more then I.
Keystr is a android base file that in simple terms tells the phone to display the lockscreen or not and how to display it, (password, pattern) for the most part. It’s a simple file that can become corrupt or missing.
I first ran into the problem with a bad radio flash, but I have heard of it becoming corrupt just uninstalling a app. That leads me to believe it’s a issue with OS and not the app that it making the file become corrupt (missing)
Since you are not rooted there is no way for you to diagnose this correctly. About the most you could do is enter into the stock recovery on your un-rooted phone and do a factory reset. BUT in all honest I don't believe this will touch your EFS/IMEI directory. If this is indeed the problem your left with warranting your phone or rooting it to fix this problem yourself. If you’re going to root it to diagnose this problem and fix it, be glad to help you with that..
In short there is not a lot more we can do to help fix this problem without being rooted..
The launcher is not that invasive and can not touch your root folders (because your not rooted) how ever the underline android OS can, and OS files can become corrupt.
tagmwar said:
I am not dev so they may be able to explain more then I.
Keystr is a android base file that in simple terms tells the phone to display the lockscreen or not and how to display it, (password, pattern) for the most part. It’s a simple file that can become corrupt or missing.
I first ran into the problem with a bad radio flash, but I have heard of it becoming corrupt just uninstalling a app. That leads me to believe it’s a issue with OS and not the app that it making the file become corrupt (missing)
Since you are not rooted there is no way for you to diagnose this correctly. About the most you could do is enter into the stock recovery on your un-rooted phone and do a factory reset. BUT in all honest I don't believe this will touch your EFS/IMEI directory. If this is indeed the problem your left with warranting your phone or rooting it to fix this problem yourself. If you’re going to root it to diagnose this problem and fix it, be glad to help you with that..
In short there is not a lot more we can do to help fix this problem without being rooted..
The launcher is not that invasive and can not touch your root folders (because your not rooted) how ever the underline android OS can, and OS files can become corrupt.
Click to expand...
Click to collapse
Thanks so much! Your comment was well written and also exhastive.
Thinking about rooting but I only have a mac, is Heimdall an option? If so, how?
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
You are welcome..
As far as Heimdall goes the following link is about all i could find for directions..
http://forum.xda-developers.com/showpost.php?p=17828262&postcount=3
I am not even sure if it can do a full root or not. or if it will actually work on the I171.. Sounds like it may, but that is a risk you would need to decide if you want to take.
I just need to say this.. I personally would not attempt to root my $600 phone with unknown like Heimdall. Maybe someone else here has used it to root there phone and can help on this..
Heimdall sounds like it can flash the kernel alone so doing a (what i call) soft root may work.. (kernel root)
This should explain the two ways to root your phone. Refer to "b. Flash counter intact"
http://forum.xda-developers.com/showthread.php?t=1586223
As far as your mac. I know odin will work inside of a windows emulator on a mac..
Hope this helps..
tagmwar said:
You are welcome..
As far as Heimdall goes the following link is about all i could find for directions..
http://forum.xda-developers.com/showpost.php?p=17828262&postcount=3
I am not even sure if it can do a full root or not. or if it will actually work on the I171.. Sounds like it may, but that is a risk you would need to decide if you want to take.
I just need to say this.. I personally would not attempt to root my $600 phone with unknown like Heimdall. Maybe someone else here has used it to root there phone and can help on this..
Heimdall sounds like it can flash the kernel alone so doing a (what i call) soft root may work.. (kernel root)
This should explain the two ways to root your phone. Refer to "b. Flash counter intact"
http://forum.xda-developers.com/showthread.php?t=1586223
As far as your mac. I know odin will work inside of a windows emulator on a mac..
Hope this helps..
Click to expand...
Click to collapse
Thanks so much. I'm really rueing the day I.downloaded the launcher! I see why folks are clamoring for plain ICS. I really don't know what to do...
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
I need a way to pull all data from my phone. the screen turns on but is completely unresponsive in the middle of the screen so I can't type half the letters. Anyway to pull data from recovery?
Have you tried creating a backup from cwm?
Its not rooted, completely stock
Guessing you tried auto rotate? When mine went bad, I turned it on, and rotated every direction as needed. Worked for me. Kind of a pain, but allowed me to get all of my info......
Ya I tried, doesn't rotate
That's terrible. Sorry to hear.
The only other way would be a lapdock. I did that as well.
Have u tried adb pull?
Sent from my MB860 using xda app-developers app
ko_wei13 said:
Have u tried adb pull?
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
no i have not, its what i was thinking to do but dont know what to type in to pull everything
What data that you want to pull out? Do u familiar with LINUX platform?
Sent from my MB860 using xda app-developers app
Mainly pictures And a few contacts. Pictures weren't saving on SD card unfortunately. No I'm not familiar with Linux
Try install airdroid and see whether u can backup from there.
Sent from my MB860 using xda app-developers app
If XP try android commander
Load it up and you will see all partitions for your phone. Tick sdcard or mnt/emmc and pull to pc
But may not work with you being stock and unrooted
Sent from my MB860 using xda premium
on my mums atrix the touch screen was unreponsive like mentioned but this went away after a while.... it could be a software issue
Do a restore from proper .SBF with rsdlite, this will reset back to factory ROM. If your problem was software, this will fix.
Consider unlock and use CMW...
Sent from my Atrix using Tapatalk2.