Dear all,
i am facing back button problem its not working
but when i am using other button backlight of back button is getting on
its out of warranty
so kindly suggest what should i do
azhar.munshi said:
Dear all,
i am facing back button problem its not working
but when i am using other button backlight of back button is getting on
its out of warranty
so kindly suggest what should i do
Click to expand...
Click to collapse
First, be clear while asking any Help.
Mention the ROM over which you are..??
Have you enabled anything..??
Did you flashed anything..??
Reply with Above ^^ question.
i am on avatar rom
i didnt update any thing
i am facing this from last day
Disturbed™ said:
First, be clear while asking any Help.
Mention the ROM over which you are..??
Have you enabled anything..??
Did you flashed anything..??
Reply with Above ^^ question.
Click to expand...
Click to collapse
i am on avatar rom
i didnt update any thing
i am facing this from last day
azhar.munshi said:
i am on avatar rom
i didnt update any thing
i am facing this from last day
Click to expand...
Click to collapse
If you have any backup then flash it then report.
Disturbed™ said:
If you have any backup then flash it then report.
Click to expand...
Click to collapse
i had tried it but no change
its not working in recovery mode also
azhar.munshi said:
i had tried it but no change
its not working in recovery mode also
Click to expand...
Click to collapse
Do one thing. Take the backup of your ROM & flash Stock GB using Odin V 1.85. If it still become pain then GO to SSC.
Disturbed™ said:
Do one thing. Take the backup of your ROM & flash Stock GB using Odin V 1.85. If it still become pain then GO to SSC.
Click to expand...
Click to collapse
i had tried this also but same not working can anyone gives me link for changing touchscreen of galaxy r video
please
azhar.munshi said:
i had tried this also but same not working can anyone gives me link for changing touchscreen of galaxy r video
please
Click to expand...
Click to collapse
galaxy R Video.??
What he is asking is tutorial video...
Sent from my GT-I9103 using xda app-developers app
galaxy r back and menu button
karthik050782 said:
What he is asking is tutorial video...
Sent from my GT-I9103 using xda app-developers app
Click to expand...
Click to collapse
even for my galaxy r, back button is not working. I was using stock gingerbread. i flashed cyanogenmod nightly and back button doesnt work. so its hardware issue. and my menu button gets executed on its own. so if i can disable these hard keys and get the soft buttons on the screen itself, it wuld solve the problems. help me do it..
lavsen said:
even for my galaxy r, back button is not working. I was using stock gingerbread. i flashed cyanogenmod nightly and back button doesnt work. so its hardware issue. and my menu button gets executed on its own. so if i can disable these hard keys and get the soft buttons on the screen itself, it wuld solve the problems. help me do it..
Click to expand...
Click to collapse
Dont panic buddy. be Calm.
Answer these questions:
1) Is you softkeys(Lightning ones) working when you were on GB..?
2) Did you mess up with anything while installing..?? what you did brief your track.
3) Hardware keys are on screen, it may be enabled from Setting. But let give feedback of above 2 questions.
back button problem solved
It was not working in gingerbread too. So i flashed cyanogenmod nightly. However I have found some temporary solution, it was probably hardware issue.
Using ES File explorer or any file manager that has root access, go to system and mount R/W
Open build.prop in text editor
go to the end of the file and add this line
qemu.hw.mainkeys=0
save and exit and reboot
when u reboot u will get soft keys in ur screen only so u can use those soft screen instead of hardware buttons and for disabling the hardware buttons u can easily do if u r in cyanogenmod
lavsen said:
It was not working in gingerbread too. So i flashed cyanogenmod nightly. However I have found some temporary solution, it was probably hardware issue.
Using ES File explorer or any file manager that has root access, go to system and mount R/W
Open build.prop in text editor
go to the end of the file and add this line
qemu.hw.mainkeys=0
save and exit and reboot
when u reboot u will get soft keys in ur screen only so u can use those soft screen instead of hardware buttons and for disabling the hardware buttons u can easily do if u r in cyanogenmod
Click to expand...
Click to collapse
Why is editing need to take place..?? you can simply enable the hardware keys from setting.
enable soft keys like in nexus
Disturbed™ said:
Why is editing need to take place..?? you can simply enable the hardware keys from setting.
Click to expand...
Click to collapse
I dont want to enable hardware keys. I want to disable it. And editing is for getting soft nexus like buttons on the screen so u can use even if ur hard keys r not working...
lavsen said:
It was not working in gingerbread too. So i flashed cyanogenmod nightly. However I have found some temporary solution, it was probably hardware issue.
Using ES File explorer or any file manager that has root access, go to system and mount R/W
Open build.prop in text editor
go to the end of the file and add this line
qemu.hw.mainkeys=0
save and exit and reboot
when u reboot u will get soft keys in ur screen only so u can use those soft screen instead of hardware buttons and for disabling the hardware buttons u can easily do if u r in cyanogenmod
Click to expand...
Click to collapse
i had tried it but not working i had installed button saviour
can you give me some steps to disable hardware keys because its getting short
i had tried adding # in 139 & 158 line but not working
so please kindly revert
azhar.munshi said:
i had tried it but not working i had installed button saviour
can you give me some steps to disable hardware keys because its getting short
i had tried adding # in 139 & 158 line but not working
so please kindly revert
Click to expand...
Click to collapse
Go to setting->Display->Hardware keys-> disable it.
is any other way to create virtual key for back & menu
please where we have to enter that code in build.prop also
azhar.munshi said:
is any other way to create virtual key for back & menu
please where we have to enter that code in build.prop also
Click to expand...
Click to collapse
you can read it above (4 post above).
i had tried it but not working
please can you give me steps with screenshots
i am on avatar rom
to disable that key i am not getting any option in setting-display-hardware keys-
Related
Hi all,
Rumor has it I picked up a DEFY last week. Most people in the community know me for my work on the cliq/backflip/cliqxt. It's been quite some time since I posted any mods/work here on XDA so here we go. First I'd like to say thanks to Koush & Tenfar for the work they've done. They laid the ground work. I simply needed/wanted to improve on it more. I wanted to include the latest 2.5.1.x version since it has some bug fixes/new features also. So here you go. This recovery includes the latest 2.5.1.8 ClockworkMod Recovery, fixed fix_permssions script, and updated adb that allows root access when using adb shell. All your backups, downloads will reside in the clockworkmod directory on your sdcard just like a standard clockworkmod recovery. If you haven't noticed the fix_permissions script don't run properly via the recovery on the DroidX/Droid2/Defy. I simply fixed the script so it does work properly. Thanks again to both Koush & Tenfar. I'm looking into resolving the problem when you have USB debugging enabled you can't boot into recovery mode properly. This release still has that issue, just FYI. If you choose to use this version over Tenfar's, you'll need to un-install his version, install this one, & choose the option to install recovery once. After that, it's works the same way. Take care.
UPDATE: I've uploaded a new version to my 4shared as well as included it here. This new version simply adds a power off option to the menu & was a quick attempt to try to resolve the USB debugging option. I'll give it another try when I have time, until then, I hope you like having the option to power off your Defy from the recovery menu. I've also provided a link to the original version. Take care.
Steve, kb7sqi
Edit: Due to requests, I'm re-adding the link for this updated version. While I do have plans to come back to #android soon, until then, this will be unsupported by me till then. I'm glad it's been useful to others. Take care.
Latest Version:
Older version:
http://goo.gl/NtsTV
Steve
Great work! Will try it out asap.
installed seems to be working fine btw whats key test?
S1dew1nder said:
installed seems to be working fine btw whats key test?
Click to expand...
Click to collapse
It's does exactly what it sounds like. It simply returns the "key" value when you touch keys/buttons on your phone. It's handy if you're wanting to update a recovery to use certain keys if your phone has them. Perfect example, on the cliqxt the phone has a touch pad. So in the version I created for it, instead of needing to use the volume up/down, you could also use the touchpad for up/down/select as well. Take care.
Steve
kb7sqi said:
It's does exactly what it sounds like. It simply returns the "key" value when you touch keys/buttons on your phone. It's handy if you're wanting to update a recovery to use certain keys if your phone has them. Perfect example, on the cliqxt the phone has a touch pad. So in the version I created for it, instead of needing to use the volume up/down, you could also use the touchpad for up/down/select as well. Take care.
Steve
Click to expand...
Click to collapse
thanks for the answer dude, just did a back up with it all went well only diff was it made a new folder btw it will restore older back ups right?
kb7sqi said:
It's does exactly what it sounds like. It simply returns the "key" value when you touch keys/buttons on your phone. It's handy if you're wanting to update a recovery to use certain keys if your phone has them. Perfect example, on the cliqxt the phone has a touch pad. So in the version I created for it, instead of needing to use the volume up/down, you could also use the touchpad for up/down/select as well. Take care.
Steve
Click to expand...
Click to collapse
How can I can quit key test?
Power+VolUp results in a black screen.
pull the bat?
S1dew1nder said:
pull the bat?
Click to expand...
Click to collapse
that's what i did. but would've been nice to have long press (power button) to quit instead of battery-pull.
Ah, well, wouldn't need to use it twice anyway.
I'm gonna try restoring an older img, report back in a few.
S1dew1nder said:
thanks for the answer dude, just did a back up with it all went well only diff was it made a new folder btw it will restore older back ups right?
Click to expand...
Click to collapse
Yeah, you should be able to restore other nandroid backups.
racca said:
How can I can quit key test?
Power+VolUp results in a black screen.
Click to expand...
Click to collapse
You guys do know you don't have to pull the battery out right? You can hold down volume down button & hit the power button to turn the phone off while in the recovery. When you power the phone on, it'll boot up like normal. Take care.
Steve
Restore doesn't work. "can't find directory"
I will switch back to the old version
Andy
morphin said:
Restore doesn't work. "can't find directory"
I will switch back to the old version
Andy
Click to expand...
Click to collapse
try renaming the goapkrev folder on your sdcard to clockworkmod it should be able to find the directory then
S1dew1nder said:
try renaming the goapkrev folder on your sdcard to clockworkmod it should be able to find the directory then
Click to expand...
Click to collapse
You took the words right out of my mouth. I was just getting ready to type that. lol Thanks!
Steve
kb7sqi said:
You guys do know you don't have to pull the battery out right? You can hold down volume down button & hit the power button to turn the phone off while in the recovery. When you power the phone on, it'll boot up like normal. Take care.
Steve
Click to expand...
Click to collapse
ahhhhhh, i tried power+volup
thanks for the refreshment, and again for the great work!
now if only we can be rid of the annoying "debugging" bug.
racca said:
ahhhhhh, i tried power+volup
thanks for the refreshment, and again for the great work!
now if only we can be rid of the annoying "debugging" bug.
Click to expand...
Click to collapse
Thanks. I'm working on it. I got a little tired of rebooting my defy over 100 times yesterday when I was working on this. lol After I get my version done for the Motorola Charm, I'll get back to working on that.
Steve
kb7sqi said:
You took the words right out of my mouth. I was just getting ready to type that. lol Thanks!
Steve
Click to expand...
Click to collapse
lol np bud, btw is there any way to rename backup folders with out having a md5 miss match error?
S1dew1nder said:
lol np bud, btw is there any way to rename backup folders with out having a md5 miss match error?
Click to expand...
Click to collapse
i have no such problem ever. renaming always works and no such info is stored in the md5 file
do you think it could of happened because i edited the file name via my computer while my phone was in usb mass storage mode?
kb7sqi said:
Thanks. I'm working on it. I got a little tired of rebooting my defy over 100 times yesterday when I was working on this. lol After I get my version done for the Motorola Charm, I'll get back to working on that.
Steve
Click to expand...
Click to collapse
no pressure then, it's fine as it is.
i just need to remember, like really hard, to turn it off.
i wish i didn't make the same mistake not turning it off over and over again
S1dew1nder said:
do you think it could of happened because i edited the file name via my computer while my phone was in usb mass storage mode?
Click to expand...
Click to collapse
It's a good chance that could've caused it. I've had some wierd stuff happen doing things like that when in usb mass storage mode.
hi guys, i am using i9003, and i flashed my camera firmware using the code *#*#34971539#*#*, then the camera cannot work any more. blank screen appear after opening the camera app and camera failed message appears after several seconds. I tried to reflash other roms, all cannot work. is there any possibility to fix this?
thx in advance!!
fsmylc said:
hi guys, i am using i9003, and i flashed my camera firmware using the code *#*#34971539#*#*, then the camera cannot work any more. blank screen appear after opening the camera app and camera failed message appears after several seconds. I tried to reflash other roms, all cannot work. is there any possibility to fix this?
thx in advance!!
Click to expand...
Click to collapse
Why would you use a code to flash it? Replace the Camera.apk file. Also what firmware are you on? Would be nice if you mentioned that aswell.
i update my i9003 to GB, i offen met camera errors, so i tried to flash it by code, but it cannot work, and currently my rom is xxkb3
fsmylc said:
i update my i9003 to GB, i offen met camera errors, so i tried to flash it by code, but it cannot work, and currently my rom is xxkb3
Click to expand...
Click to collapse
I quote this from the KP9 Feedback thread, this has already been discussed, so please avoid making new threads, I will highlight the important part in bold. It's important that you look at the KP9 Flash guide to make sure your not missing any steps. Bootloader is a must to flash aswell.
1. Make all your backups using TB. Don't forget to move the TB folder to Ext_SD or PC after backing up.
2. Factory reset phone using manual code. (*2767*3855#)
3. Get into recovery mode and wipe all.
4. Now flash the new ROM as usual (latona and then the remaining 4 files.) Be sure not to make any lame errors here.
5. Factory reset again using manual code.
6. Now check to see if the power button functions and the phone reboots when you ask so. (It should work.)
7. Check camera. If you have a black screen, its okay.
8. Factory reset again using manual code.
9. Redo flash procedure again.
10. Factory reset again.
11. Check power button issue and camera. Both should be totally fine.
12. Press power button to lock and leave device for 10 mins. Now, press power button to check if the device wakes up as normal. It should. If you want to avoid the device being woken up by calls or texts or other notifications, just put it into flight mode and turn off Wi-Fi.
13. Root using SuperOneClick. It will show up Kernel Panic error in the end, but its no problem.
14. Just pull battery after that and restart phone. You should see SuperUser installed and working. Upgrade Busybox to 1.18.4 by Stericson.
15. Now install TB and go about your restoring business. DO NOT restore any system apps. Just restore User Apps and data.
16. If you didn't **** up any of the above, you should be up and running 2.3.4 without any issues (yet!).
yes, i tried this method, but it does not work for me, camera still keep black first, then camera failed message pops up... i am not sure if the camera is the same as i9000, then i can try the wave bin files. thx anyway
*#*#34971539#*#* and choosing the "update camera firmware" is a big no no.
The firmware for your camera is now gone.. Take it your samsung service center and *do not* mention the secret menu for camera. Just say it stopped working.
Many of these menus are hidden for a reason..
fooman123 said:
*#*#34971539#*#* and choosing the "update camera firmware" is a big no no.
The firmware for your camera is now gone.. Take it your samsung service center and *do not* mention the secret menu for camera. Just say it stopped working.
Many of these menus are hidden for a reason..
Click to expand...
Click to collapse
You get a thanks from me, Why do people get so curious to play with secret menu's to kill their phone. Congratulations, He now has a camera phone without camera.
thx for your help. but i just want to make my camera to work, not just playing.
My friend, I was the stupid one with same problem early this month.
Service center will need 1 hour to fix, don't waste your time reflash firmware.
I did that many times and no luck at all...service center the solution.
http://forum.xda-developers.com/showthread.php?p=15336141#post15336141
He erased his camera firmware thats why
Try this
http://forum.xda-developers.com/showthread.php?t=1171246
All i can see is going to service center and getting it fixed. Isnt their a solution that we can perform?
jaskiratsingh said:
All i can see is going to service center and getting it fixed. Isnt their a solution that we can perform?
Click to expand...
Click to collapse
Did you erase your firmware too?
This code should be spread far and wide..
http://samsunggalaxysforums.com/showthread.php/4834-SamsungApps-camera-firmware-update-available!?
My camera dont work too after i flashed kp9 to xxkb3 too.. Can anybody help me with this prob.. Or can anyone can post camera.apk that can run xxkb3 firmware.. Thanks much!
mjbri0613 said:
My camera dont work too after i flashed kp9 to xxkb3 too.. Can anybody help me with this prob.. Or can anyone can post camera.apk that can run xxkb3 firmware.. Thanks much!
Click to expand...
Click to collapse
You need to flash xxkb3 twice.
Hard reset, Flash first time, hard reset using code, flash again, hard reset using code and camera should work
Sent from my GT-I9003 using XDA Premium App
fooman123 said:
Did you erase your firmware too?
This code should be spread far and wide..
http://samsunggalaxysforums.com/showthread.php/4834-SamsungApps-camera-firmware-update-available!?
Click to expand...
Click to collapse
No... I didn't erase my camera firmware. I wanted to know, as no forum including above provides a solution
Sent from my GT-I9003 using XDA Premium App
jaskiratsingh said:
You need to flash xxkb3 twice.
Hard reset, Flash first time, hard reset using code, flash again, hard reset using code and camera should work
Sent from my GT-I9003 using XDA Premium App
Click to expand...
Click to collapse
Ok sir i will try it
jaskiratsingh said:
No... I didn't erase my camera firmware. I wanted to know, as no forum including above provides a solution
Sent from my GT-I9003 using XDA Premium App
Click to expand...
Click to collapse
Then given your acknowledgment that "no forum including above provides a solution" the general consensus (and multiple Google searches) -- seems to confirm that if one "updates" their camera firmware from the hidden menu -- that there is at present - no known, recovery - short of taking the phone to a samsung service center..
I just don't understand how re-asking the question is going to yield a different answer.. like the easy do-it-yourself solution is being withheld in favor of the more difficult one of taking the phone to the service center -- just waiting for someone to ask..
fooman123 said:
Then given your acknowledgment that "no forum including above provides a solution" the general consensus (and multiple Google searches) -- seems to confirm that if one "updates" their camera firmware from the hidden menu -- that there is at present - no known, recovery - short of taking the phone to a samsung service center..
I just don't understand how re-asking the question is going to yield a different answer.. like the easy do-it-yourself solution is being withheld in favor of the more difficult one of taking the phone to the service center -- just waiting for someone to ask..
Click to expand...
Click to collapse
Well....you are providing a link, thought it to be a solution. What I don't understand is the need to create multiple topics and giving circular reference.
If you have a solution except customer service then share, if you don't even a noob knows service center is my resort.
Sent from my GT-I9003 using XDA Premium App
service center refused my request because I bought the machine in hongkong, but iam in china at present, so I have to try to resolve it by myself...
Finally i disable that my soft keys (menu & Back hardware keys )......
See the instruction below ......
1) Use a program like root explorer
2) go to /system/usr/keylayout
3) create a new file named "melfas-touchkey.kl" with the following text:
#key 158 BACK VIRTUAL
#key 139 MENU VIRTUAL
4) also create a second file named "sec_touchkey.kl" with the same text
5) change the permissions of both files to "rw-r--r--" (just like the other files in the directory)
6) reboot...done!
Why to disable the menu and back key?
karthik050782 said:
Why to disable the menu and back key?
Click to expand...
Click to collapse
because my menu and back keys not working properly means sometime those keys are working without any touch and its so irritating ,
that's why i decided to disable that keys permanently , i already post for help but nothing happen , actually its hardware touchscreen issue ,
my phone is not in warranty that's why i disable that keys permanently , now i am using a software like soft keys its good for work on touch screen
sacfire said:
because my menu and back keys not working properly means sometime those keys are working without any touch
Click to expand...
Click to collapse
hv u visited ssc to know which particular hardware is faulty for that and how much it'll cost if u want to get them repaired/replaced
It may help others whose cell is/will be out of warranty....
Sent from my GT-I9103 using Tapatalk
ofabhishek said:
hv u visited ssc to know which particular hardware is faulty for that and how much it'll cost if u want to get them repaired/replaced
It may help others whose cell is/will be out of warranty....
Sent from my GT-I9103 using Tapatalk
Click to expand...
Click to collapse
Yes... He already told that his phone was out of warranty.
Even, I had faced the same problem and my touchscreen got replaced under warranty.
But, it will be very helpful for those who lose warranty.:thumbup:
Sent from my GT-I9103 using xda app-developers app
sacfire said:
Finally i disable that my soft keys (menu & Back hardware keys )......
See the instruction below ......
1) Use a program like root explorer
2) go to /system/usr/keylayout
3) create a new file named "melfas-touchkey.kl" with the following text:
#key 158 BACK VIRTUAL
#key 139 MENU VIRTUAL
4) also create a second file named "sec_touchkey.kl" with the same text
5) change the permissions of both files to "rw-r--r--" (just like the other files in the directory)
6) reboot...done!
Click to expand...
Click to collapse
Hi,
I found your thread because I have exactly the same problem. The back and menu keys are out of control. They are activating themselves all the time. Actually my i9103 is not usable. So I tried to find any solution to work around the problem. Well, I followed exactly your instructions but unfortunately it doesn´t work. So do you have any idea what else can I do? I´m using the 4.0.4 ICS version offered and explained in this thread here (http://forum.xda-developers.com/showthread.php?t=1725044). I hope you (or somebody else) can give me more hints,
Thx,
Dannol
Dannol said:
Hi,
I found your thread because I have exactly the same problem. The back and menu keys are out of control. They are activating themselves all the time. Actually my i9103 is not usable. So I tried to find any solution to work around the problem. Well, I followed exactly your instructions but unfortunately it doesn´t work. So do you have any idea what else can I do? I´m using the 4.0.4 ICS version offered and explained in this thread here (http://forum.xda-developers.com/showthread.php?t=1725044). I hope you (or somebody else) can give me more hints,
Thx,
Dannol
Click to expand...
Click to collapse
well i wld suggest u to move on to PA rom... it has n optio to disable menu keys n use on screen keys..
Sent from my GT-I9103 using Tapatalk 2
vipul12389mehta said:
well i wld suggest u to move on to PA rom... it has n optio to disable menu keys n use on screen keys..
Sent from my GT-I9103 using Tapatalk 2
Click to expand...
Click to collapse
Thank you very much for your fast reply. Well, as I am a totally newbie and only facing these topics (flashing, rooting, etc.) due to my heavy problem, I have no idea what a PA Rom is. Where do I get it? What differences are between a/the PA Rom and the ICS 4.0.4? How do I have to flash it? And finally, once flashed the Rom, how can I disable the softkeys?
Thanks once again,
Dannol
Dannol said:
Thank you very much for your fast reply. Well, as I am a totally newbie and only facing these topics (flashing, rooting, etc.) due to my heavy problem, I have no idea what a PA Rom is. Where do I get it? What differences are between a/the PA Rom and the ICS 4.0.4? How do I have to flash it? And finally, once flashed the Rom, how can I disable the softkeys?
Thanks once again,
Dannol
Click to expand...
Click to collapse
Buddy,
PA ROM is Paranoid Android ROM based on Jelly Bean (4.1.2) android. its higher version then ICS 4.0.4.
you can download the ROM from this Dev thread & can discuss your problem in this general thread. -> http://forum.xda-developers.com/showthread.php?t=1960167
For flashing new thing, rooting-> go here -> http://forum.xda-developers.com/showthread.php?t=1862688
also, if you are already rooted & CWM preinstalled then just download the file-> put it into sdcard-> go to recovery-> wipe data. cache, dalvik cache & then select install zip from card-> select the zip file & install it.
Note: the above procedure for JB ROMs(PA, PAC, CM10)
kataria.vikesh said:
Buddy,
PA ROM is Paranoid Android ROM based on Jelly Bean (4.1.2) android. its higher version then ICS 4.0.4.
you can download the ROM from this Dev thread & can discuss your problem in this general thread. -> http://forum.xda-developers.com/showthread.php?t=1960167
For flashing new thing, rooting-> go here -> http://forum.xda-developers.com/showthread.php?t=1862688
Click to expand...
Click to collapse
Thank you very much. :good: I will have a look and will try to flash it.
Dannol said:
Thank you very much. :good: I will have a look and will try to flash it.
Click to expand...
Click to collapse
It ok buddy. Also ,check the whats work & whats doesn't and changelog also. then flash any ROM.
kataria.vikesh said:
Buddy,
PA ROM is Paranoid Android ROM based on Jelly Bean (4.1.2) android. its higher version then ICS 4.0.4.
you can download the ROM from this Dev thread & can discuss your problem in this general thread. -> http://forum.xda-developers.com/showthread.php?t=1960167
For flashing new thing, rooting-> go here -> http://forum.xda-developers.com/showthread.php?t=1862688
also, if you are already rooted & CWM preinstalled then just download the file-> put it into sdcard-> go to recovery-> wipe data. cache, dalvik cache & then select install zip from card-> select the zip file & install it.
Note: the above procedure for JB ROMs(PA, PAC, CM10)
Click to expand...
Click to collapse
Hey buddy,
thanks for all the information. I already had a look on the links posted and would like to resolve the few doubts I have:
1. as you mentioned for already flashed and rooted phones I should only follow your instructions (which should be equal to the instructions of the PA Rom thread). I've found little differences: they say first to make a factory reset, than install rom and than gapps (?), after that I should wipe the cache partition and the dalvik cache and finally install a fix. You mentioned these steps in the beginning and you didn't mentioned any Gapps and any Fix. So, what are the right steps? As I said, I am a newbie and don't want to make any mistakes. That's why I'm asking all the details.
2. If the installation of gapps is really necessary, could you please confirm that the right version is "gapps-jb-20121011-signed.zip ".
3. Each installation I have to carry out with CWM using the recovery task, right?
Thx a lot,
Dannol
Dannol said:
Hey buddy,
thanks for all the information. I already had a look on the links posted and would like to resolve the few doubts I have:
1. as you mentioned for already flashed and rooted phones I should only follow your instructions (which should be equal to the instructions of the PA Rom thread). I've found little differences: they say first to make a factory reset, than install rom and than gapps (?), after that I should wipe the cache partition and the dalvik cache and finally install a fix. You mentioned these steps in the beginning and you didn't mentioned any Gapps and any Fix. So, what are the right steps? As I said, I am a newbie and don't want to make any mistakes. That's why I'm asking all the details.
2. If the installation of gapps is really necessary, could you please confirm that the right version is "gapps-jb-20121011-signed.zip ".
3. Each installation I have to carry out with CWM using the recovery task, right?
Thx a lot,
Dannol
Click to expand...
Click to collapse
Yes buddy. You are lilbit confused now. You need to flash the same through CWM.
Here what you have to do:
1) download the PA or PAC rom file and download latest 4.2 Leaked Gapps (download from here)-> Put it in your Sdcard
2) Boot into recovery -> Wipe data & cache & dalvik cache.
3) Flash PA or PAC ROM using recovery
4) Reboot
After rebooting, make few changes you want. Again go to recovery -> Flash Gapps -> Wipe cache & dalvik cache -> reboot
There are few fixes, which is already in OP of there respective threads . You can flash the latest one & can ask help after that.
Happy Flashing.:good:
Note: if you are over ICS & not rooted or doesn't know about eMMC Erase bug then please go through that first then wipe anything on you rmobile.
kataria.vikesh said:
Yes buddy. You are lilbit confused now. You need to flash the same through CWM.
Here what you have to do:
1) download the PA or PAC rom file and download latest 4.2 Leaked Gapps (download from here)-> Put it in your Sdcard
2) Boot into recovery -> Wipe data & cache & dalvik cache.
3) Flash PA or PAC ROM using recovery
4) Reboot
After rebooting, make few changes you want. Again go to recovery -> Flash Gapps -> Wipe cache & dalvik cache -> reboot
There are few fixes, which is already in OP of there respective threads . You can flash the latest one & can ask help after that.
Happy Flashing.:good:
Note: if you are over ICS & not rooted or doesn't know about eMMC Erase bug then please go through that first then wipe anything on you rmobile.
Click to expand...
Click to collapse
Ok, that sounds good. Will try it later when I'm at home. The last doubt I have is regarding your note. What do you mean with "if you are over ICS"? The phone is rooted and 4.0.4 is installed. Regarding the eMMC Erase bug, I only remember a eMMC brick bug (which you could check via an app). But its a different thing, right?
Dannol said:
Ok, that sounds good. Will try it later when I'm at home. The last doubt I have is regarding your note. What do you mean with "if you are over ICS"? The phone is rooted and 4.0.4 is installed. Regarding the eMMC Erase bug, I only remember a eMMC brick bug (which you could check via an app). But its a different thing, right?
Click to expand...
Click to collapse
firstly our phone is not compatible with the app u mentioned..
header over to ghis thread for detailed discussion..
[CAUTION][ICS][UPDATE][DOWNGRADE]Read before flashing ICS - http://forum.xda-developers.com/showthread.php?t=1842076
[CAUTION][ICS][UPDATE][DOWNGRADE]Read before flashing ICS
Sent from my GT-I9103 using Tapatalk 2
vipul12389mehta said:
firstly our phone is not compatible with the app u mentioned..
header over to ghis thread for detailed discussion..
[CAUTION][ICS][UPDATE][DOWNGRADE]Read before flashing ICS - http://forum.xda-developers.com/showthread.php?t=1842076
[CAUTION][ICS][UPDATE][DOWNGRADE]Read before flashing ICS
Sent from my GT-I9103 using Tapatalk 2
Click to expand...
Click to collapse
Ah well, ok, thank you for the advice. As far as I understood the thread there is always a certain chance that I can brick my phone while flashing it with CWM, right? Besides there is nothing I could do to eliminate that risk? What would you recommend me to do? And honestly, the actual failure with the softkeys makes my phone useless. So if I have to buy a new one because I bricked it or because the keys are going wild, there will be no difference for me.
Thx
Dannol said:
Ah well, ok, thank you for the advice. As far as I understood the thread there is always a certain chance that I can brick my phone while flashing it with CWM, right? Besides there is nothing I could do to eliminate that risk? What would you recommend me to do? And honestly, the actual failure with the softkeys makes my phone useless. So if I have to buy a new one because I bricked it or because the keys are going wild, there will be no difference for me.
Thx
Click to expand...
Click to collapse
just flash any ardatdat's 4.0+ kernel and u cn try d on screen keys instead of buying a new fone.
Sent from my GT-I9103 using xda premium
sacfire said:
Finally i disable that my soft keys (menu & Back hardware keys )......
See the instruction below ......
1) Use a program like root explorer
2) go to /system/usr/keylayout
3) create a new file named "melfas-touchkey.kl" with the following text:
#key 158 BACK VIRTUAL
#key 139 MENU VIRTUAL
4) also create a second file named "sec_touchkey.kl" with the same text
5) change the permissions of both files to "rw-r--r--" (just like the other files in the directory)
6) reboot...done!
Click to expand...
Click to collapse
hey dude iam also facing the same problem for the past two days....
please help me how to create the file,should i create a new folder and then the file text or how to do it please help.....
Dannol said:
Ah well, ok, thank you for the advice. As far as I understood the thread there is always a certain chance that I can brick my phone while flashing it with CWM, right? Besides there is nothing I could do to eliminate that risk? What would you recommend me to do? And honestly, the actual failure with the softkeys makes my phone useless. So if I have to buy a new one because I bricked it or because the keys are going wild, there will be no difference for me.
Thx
Click to expand...
Click to collapse
Buddy Chill. You have lost your soft keys. but bricking you phone will permanent loose it. BTW as @ bhavik buddy suggested, flash Ardatdat's kernel V 4 & higher. then wipe anything for flashing CM10.
---------- Post added at 09:34 PM ---------- Previous post was at 09:28 PM ----------
akashhari said:
hey dude iam also facing the same problem for the past two days....
please help me how to create the file,should i create a new folder and then the file text or how to do it please help.....
Click to expand...
Click to collapse
buddy, just download any explorer (with root facility, I will preferred Solid explorer). then create file from PC with matter & name give in OP. then push it in as suggested by OP with permission.
kataria.vikesh said:
Buddy Chill. You have lost your soft keys. but bricking you phone will permanent loose it. BTW as @ bhavik buddy suggested, flash Ardatdat's kernel V 4 & higher. then wipe anything for flashing CM10.
Click to expand...
Click to collapse
thanks for the help, but i dont understand because i have already installed PAC rom...what should i do know.....
I am trying to install NextGen 1.5
Problem is, in main menu, whenever I go to "recovery", fone gets struck with htc logo(white background). Then I have to take out battery, re-insert, press vol down+power up .....fast boot and run "recovery.bat" from pc(while connected fone to pc). then I get back the CWM Recovery Menu.
This is occuring everytime. Please help me to fix it.
Try with some other recovery, it's not like you don't have a choice And from which main menu you're getting in to recovery?
shortyoko said:
Try with some other recovery, it's not like you don't have a choice And from which main menu you're getting in to recovery?
Click to expand...
Click to collapse
well "main menu" refers to vol down+power button, which leads to "fast boot, recovery, factory reset" options.
Also u only suggest me some better recovery plz.
http://forum.xda-developers.com/showthread.php?t=2123503
I don't know if it's better or not, I'm still with the good old yannou's recovery, staying with the principle 'if it aint broke, don't fix it'
shortyoko said:
http://forum.xda-developers.com/showthread.php?t=2123503
I don't know if it's better or not, I'm still with the good old yannou's recovery, staying with the principle 'if it aint broke, don't fix it'
Click to expand...
Click to collapse
Thanks buddy...1 more thing, I hv installed nextgen1.5 Now when i go to music player-->sound enhancer..i get a FC, can u help me wid dis ?
Plus when i try to grant SU permission to any app..it says "Sorry, test failed. This feature cannot be granted to ur fone"
Fone is perfectly rooted. Had been using it for 1 yr, n now for the frst tym put custom rom and all these issues.
That's for the dsp
.Music player force closes bcoz of DSP libraries to fix just remove the library file from /system/lib/soundfx/libcyanogen-dsp.so it will perfectly like breeze.
Click to expand...
Click to collapse
For super user, enable usb debugging option from the phone menu(at the moment I don't remember where it was in the menu)
shortyoko said:
That's for the dsp
For super user, enable usb debugging option from the phone menu(at the moment I don't remember where it was in the menu)
Click to expand...
Click to collapse
Thanks a ton ! worked like charm ! +1
If u dont mind, tell me from where did u get that solution for music player ? I was looking for that but google dint help >_<
From NExtGen thread, when firstly 1.5 was released this was kind'a annoying bug, so there was a lot of question about that, here is the specific post from where I took it > http://forum.xda-developers.com/showthread.php?p=33599083&highlight=1+5+dsp+fix#post33599083
Just a friendly advice for the next time, there is a 'search in this thread' function which is really helpful when you have an issue with, whichever rom, cos it's possible for somebody to yell at you if you asked something that has been answered several times before
shortyoko said:
From NExtGen thread, when firstly 1.5 was released this was kind'a annoying bug, so there was a lot of question about that, here is the specific post from where I took it > http://forum.xda-developers.com/showthread.php?p=33599083&highlight=1+5+dsp+fix#post33599083
Just a friendly advice for the next time, there is a 'search in this thread' function which is really helpful when you have an issue with, whichever rom, cos it's possible for somebody to yell at you if you asked something that has been answered several times before
Click to expand...
Click to collapse
will keep that in mind thought google was more accurate, but oh well !
Help?
You got your answer bro, or still need help....
Sorry i checked PM today so didn't reply...:good:
artistaditya said:
You got your answer bro, or still need help....
Sorry i checked PM today so didn't reply...:good:
Click to expand...
Click to collapse
its fine, shortyoko helped me. You may edit the thread name with [solved] tag
try another custom rom
Hi there,
I have Htc Explorer with custom ROM sense 4 and philz touch recovery. I am facing soft keys problem they work perfectly in recovery but not in ROM/OS. Sometime they work but most of the time they don't. Kindly suggest me a solution. My Soft keys are working that is what I know for sure because they work fine in recovery.
One more question how to fix permissions in philz touch recovery because I don't see any option in this recovery to fix the permissions according to my knowledge maybe I am wrong. Do let me know if anyone knows the option of fixing permissons in philz touch recovery or any other good method.
Waiting for your kind reply,
Usman Aly said:
Hi there,
I have Htc Explorer with custom ROM sense 4 and philz touch recovery. I am facing soft keys problem they work perfectly in recovery but not in ROM/OS. Sometime they work but most of the time they don't. Kindly suggest me a solution. My Soft keys are working that is what I know for sure because they work fine in recovery.
One more question how to fix permissions in philz touch recovery because I don't see any option in this recovery to fix the permissions according to my knowledge maybe I am wrong. Do let me know if anyone knows the option of fixing permissons in philz touch recovery or any other good method.
Waiting for your kind reply,
Click to expand...
Click to collapse
Hmmm..... I have another fix: in build.prop at the bottom type: qemu.hw.mainkeys=0
Reboot and you should get on-screen keys. That'll work until u get ur problem fixed
I haven't used Philz in so long but if there's an advanced settings menu check there
Nick_73 said:
Hmmm..... I have another fix: in build.prop at the bottom type: qemu.hw.mainkeys=0
Reboot and you should get on-screen keys. That'll work until u get ur problem fixed
I haven't used Philz in so long but if there's an advanced settings menu check there
Click to expand...
Click to collapse
qemu.hw.mainkeys=0 is not working already gave it a try but nothing all in vain. no there is nothing related to fix permissions in advance as far as I knoq.
Usman Aly said:
qemu.hw.mainkeys=0 is not working already gave it a try but nothing all in vain. no there is nothing related to fix permissions in advance as far as I knoq.
Click to expand...
Click to collapse
That code works for samsung phones but I guess not on all. A third party app would be ur best bet for now. But is there and other recoveries available for ur phone?
Nick_73 said:
That code works for samsung phones but I guess not on all. A third party app would be ur best bet for now. But is there and other recoveries available for ur phone?
Click to expand...
Click to collapse
Well yes there are two or more recovery options are available for my phone. Ok will try some third party app.
Bump
Anyone Else there to help me?
Usman Aly said:
Well yes there are two or more recovery options are available for my phone. Ok will try some third party app.
Click to expand...
Click to collapse
Try twrp if available
Nothing still the same issue after installing twrp :/
Sent from my HTC Explorer using XDA Free mobile app
Usman Aly said:
Nothing still the same issue after installing twrp :/
Sent from my HTC Explorer using XDA Free mobile app
Click to expand...
Click to collapse
There's no fix permissions option or soft keys still don't work?
Soft keys still don't work. Fix permissions option is there and I have fixed the permissions even I've tried the stock Rom to check my soft keys but still same issue with soft keys on stock Rom. Now I am back on sense 4.
Sent from my HTC Explorer using XDA Free mobile app
Found one more thing that if I lock my device and then unlock it my soft keys work for a second.
Sent from my HTC Explorer using XDA Free mobile app
Bump
No one is here to help? I've searched through the internet and found that alot of people have gone through the same issue. Anyone with the solution?
How hard I have to bump my head in this post to get attention? Anyone?