Hey guys,
Been lurking on the site for a while, I've searched all morning for what i need but with no success.
Setup: Att sgh-i777 rooted etc. running JellyBam 5.1
Problem: Power button stopped working, cannot use recovery to backup/flash new software.
Plenty of threads on the button issue, that's not the main question (suggestions welcome though) I just really want to backup before I send it off for repair.
Seems my best course of action is to get a kernel with touch based recovery. I tried downloading mobile Odin to flash a new kernel but it's telling me my phone isn't supported for some reason? I ran the dump file Odin suggested but not sure what to do with that info now. Next best option appears to be to get a .tar of the siyah kernel and flash it with Odin via PC. I just can't find a .tar for that kernel anywhere and I don't have enough posts to ask in the siyah thread.
So, can anyone give me a hand- either with trouble shooting mobile odin, or tracking down a .TAR of the siyah kernel or...any other suggestions?
Edit: Just found this- http://forum.xda-developers.com/showthread.php?t=1644240
I realize this is in the 9100 forum but looks like it simply converts a zip to an odin flashable tar which is what i'm looking for. Anyone have any experience with it?
Thanks in advance for any insight!
You want to do a nandroid backup? Yes just flash the siyah kernel in the development forum with mobile Odin. It does work with our phones.
Phalanx7621 said:
You want to do a nandroid backup? Yes just flash the siyah kernel in the development forum with mobile Odin. It does work with our phones.
Click to expand...
Click to collapse
Odin says "Device not supported, or not detected (check root)" see attached screen. I'm definitely rooted, have superSU1.04, use TI backup frequently etc.
It actually magically started working again last night though. I immediately did a backup but at the end it said "md5 checksum failed". I then ran kernel cleaner, wiped cache, wiped delvik and flashed the newest siyah and tried again and backup was successful and now i'm on touch recovery. Mobile odin still tells me not supported/not detected though- any idea what might cause that? could it be ROM related ?
I'm going to flash back to jellybam 4.1 today and see if that does it.
flet2 said:
Odin says "Device not supported, or not detected (check root)" see attached screen. I'm definitely rooted, have superSU1.04, use TI backup frequently etc.
It actually magically started working again last night though. I immediately did a backup but at the end it said "md5 checksum failed". I then ran kernel cleaner, wiped cache, wiped delvik and flashed the newest siyah and tried again and backup was successful and now i'm on touch recovery. Mobile odin still tells me not supported/not detected though- any idea what might cause that? could it be ROM related ?
I'm going to flash back to jellybam 4.1 today and see if that does it.
Click to expand...
Click to collapse
It possibly can be ROM related (but I am not certain). User AJ's Siyah kernel 7.6.8, it's works well with all the ROMs.
BeenAndroidized said:
It possibly can be ROM related (but I am not certain). User AJ's Siyah kernel 7.6.8, it's works well with all the ROMs.
Click to expand...
Click to collapse
Yup, running 7.6.7 now and enjoying it.. My power button is currently working again but i turned on 'swipe to wake' in Stweaks so when it fails again, at least i'll still have a working phone. the volume wake from AOKP settings doesn't work when the phone is in deep sleep so pretty useless. As long as i stay on Siyah kernel i guess i'll be able to limp along until i get the button fixed.
The Odin thing is still strange though, will have to try another ROM and see if it recognizes my phone then. Tried Jellybam 4.1 but kept getting reboots even with full wipe- tried flashing it twice. Maybe i got a bad download, i'll try again tonight.
flet2 said:
Yup, running 7.6.7 now and enjoying it.. My power button is currently working again but i turned on 'swipe to wake' in Stweaks so when it fails again, at least i'll still have a working phone. the volume wake from AOKP settings doesn't work when the phone is in deep sleep so pretty useless. As long as i stay on Siyah kernel i guess i'll be able to limp along until i get the button fixed.
The Odin thing is still strange though, will have to try another ROM and see if it recognizes my phone then. Tried Jellybam 4.1 but kept getting reboots even with full wipe- tried flashing it twice. Maybe i got a bad download, i'll try again tonight.
Click to expand...
Click to collapse
Try 7.6.8, I'm using 7.6.8-S and swipe works perfectly fine on my end.
BeenAndroidized said:
Try 7.6.8, I'm using 7.6.8-S and swipe works perfectly fine on my end.
Click to expand...
Click to collapse
Oh yea the swipe to unlock for siyah works great. I was referring to JellyBam's AOKP settings which offers a volume to wake. Volume wake works when on charger, but won't wake it from deep sleep. Siyah's Swipe wake does both :good:
I would still love to have an odin flashable .tar of siyah though- If anyone has any insight on how to get that (or make it from the .zip) that would be awesome. I used the tool from the thread linked in the OP and it did turn the kernal zip into a .tar but i don't dare flash it to test...
flet2 said:
Odin says "Device not supported, or not detected (check root)" see attached screen. I'm definitely rooted, have superSU1.04, use TI backup frequently etc.
It actually magically started working again last night though. I immediately did a backup but at the end it said "md5 checksum failed". I then ran kernel cleaner, wiped cache, wiped delvik and flashed the newest siyah and tried again and backup was successful and now i'm on touch recovery. Mobile odin still tells me not supported/not detected though- any idea what might cause that? could it be ROM related ?
I'm going to flash back to jellybam 4.1 today and see if that does it.
Click to expand...
Click to collapse
Read somewhere that jellybam 5.1.0 places the wrong phone info in the rom. It show up as i777 instead of sgh-i777 and this might be causing Mobile odin to fail on the compatibility test.
To turn your volume up button into a power button edit the /system/usr/keylayout/gpio-keys.kl file to read:
key 115 POWER WAKE
key 114 VOLUME_DOWNWAKE
key 102 HOME WAKE
key 107 ENDCALL
key 105 DPAD_LEFT
key 106 DPAD_RIGHT
key 103 DPAD_UP
key 108 DPAD_DOWN
key 232 DPAD_CENTER
key 116 POWER WAKE
key 212 CAMERA WAKE
key 115 is the volume up button. This only works in the fully booted os. Doesn't work in recovery.
Sent from my Apple IIe
Quicksilver13 said:
Read somewhere that jellybam 5.1.0 places the wrong phone info in the rom. It show up as i777 instead of sgh-i777 and this might be causing Mobile odin to fail on the compatibility test.
Click to expand...
Click to collapse
Yup that was exactly it. I notice it when i went back to Jellybam 4.1 and saw the full device name in the 'about'. Hopefully 5.2 drops soon with all the necessary fixes!
billyjed said:
To turn your volume up button into a power button edit the /system/usr/keylayout/gpio-keys.kl file to read:
key 115 POWER WAKE
key 114 VOLUME_DOWNWAKE
key 102 HOME WAKE
key 107 ENDCALL
key 105 DPAD_LEFT
key 106 DPAD_RIGHT
key 103 DPAD_UP
key 108 DPAD_DOWN
key 232 DPAD_CENTER
key 116 POWER WAKE
key 212 CAMERA WAKE
key 115 is the volume up button. This only works in the fully booted os. Doesn't work in recovery.
Sent from my Apple IIe
Click to expand...
Click to collapse
Thanks for this info. Is there a thread or tutorial somewhere that will explain how to access and edit this file? I assume it's not as simple as just navigating to it and making the changes?
Also, how do i get volume to go up if i turn it into a power button? wouldn't that make my phone lock every time i tried to turn up the volume then?
flet2 said:
Yup that was exactly it. I notice it when i went back to Jellybam 4.1 and saw the full device name in the 'about'. Hopefully 5.2 drops soon with all the necessary fixes!
Thanks for this info. Is there a thread or tutorial somewhere that will explain how to access and edit this file? I assume it's not as simple as just navigating to it and making the changes?
Also, how do i get volume to go up if i turn it into a power button? wouldn't that make my phone lock every time i tried to turn up the volume then?
Click to expand...
Click to collapse
It actually is just as simple as finding the file, mounting the directory as r/w and then editing the file. As far as turning up volume, you would have to turn down volume and then use the on screen volume panel to adjust.
Sent from my Apple IIe
Great thanks. So to mount the directory it appears i need to use ADB, or could i use an app such as Root explorer or something like this? https://play.google.com/store/apps/details?id=com.beansoft.mount_system&hl=en
Can i access the file right from my phone to make the changes once i have the directory mounted correctly?
flet2 said:
Great thanks. So to mount the directory it appears i need to use ADB, or could i use an app such as Root explorer or something like this? https://play.google.com/store/apps/details?id=com.beansoft.mount_system&hl=en
Can i access the file right from my phone to make the changes once i have the directory mounted correctly?
Click to expand...
Click to collapse
I use root explorer on the phone. If you use a rom that has support, you can add a line into your addon.d files to keep from having to manually change it everytime you update your firmware.
Sent from my Apple IIe
Thx for the info, i'll have to test this out. I'll nandroid and back up the original file too just incase!
Let me know how it works out for you.
Sent from my Apple IIe
Hi,
My wife's power button went out on her i777. Backed up the file and changed key 115 to power wake. Rebooted. This made volume up and down both stop working. Changed it back, they both work. Any ideas?
I have it running AOKP with AJK kernel.
Related
When I sleep my Fascinate or it sleeps from non activity it randomly goes into a permanent sleep where it will not respond to anything I do. The shortest amount of time I left it alone was 5 minutes and it still did it, but I've also left it alone for over an hour and had no problem. I don't get any noises or soft key lighting. It is not simply off though because a press or long press or longlonglong press on power does nothing.
The only way I've been able to get back is to Hold Power and Vol buttons or pull battery. When I do this I'm automatically booted into CWM red recovery, then I boot normal and everything is back.
I've copied the tutorial I used to root and Odin the EB01_DXC.tar.md5 package and then I added SC 2.9.2... I did all the right wiping and factory resets and back-ups as instructed in the tutorials.
Here is the Tutorial I used for Root
http://www.fascinateforums.com/forum/fascinate-rs-guides/1421-how-root-your-fascinate-install-froyo.html
Then I used this tutorial for SC 2.9.2 (non Voodoo, yes i got the right zip)
http://forum.xda-developers.com/showthread.php?t=983395
I've read that Titanium backup users get a similar issue, but I also read that they have soft button lighting whereas I do not. I also see that this is a kind of common Froyo issue but does anyone know of anything I can do? I uninstalled Titanium but it still happens
Here is my Phone Info:
Firmware Version
2.2.1
Baseband version
S:i500.04 V.EB01
Kernel version
2.6.32.9
Build Number
SCH-I500.EB01
Any Ideas?
Find adrenalyne's post on SOD or sleep of death, there is a fix posted there. I would link it but I an on my mobile app.
Sent from my SCH-I500 using XDA App
http://forum.xda-developers.com/showthread.php?t=960080
Thanks, I'll read it and see what I come up with
I'm using Gingervillain mod rom but also has this issue on erenz miui. Randomly I lose my volume, home, menu and back key functions. No light on home key but power key works fine! I select reboot and I regain function for a while.
I have not flashed any new kernels. I have checked my apps and can't see any new ones that could be causing a problem. I thought it could be overclock related but at stock frequency its the same.
Tearing my hair out please help! Will test a stock rom after work tonight...
Sent from my X10 using xda premium
i lost menu button function once.in first WB backup after doing factory reset. but didn't face that problem.Anyway it's 100% software problem.as volume buttons have nothing to do with home and back keys.
Also can u enter Recovery mode or flashmode ? then ur keys are fine.i can enter recovery mode in DoomKernel by volumeUp button.YOU know every one would suggest you to revert back to stock ROM. it's the best way to test your keys.
Hope they're fine.
Omar
I will try stock rom and kernel. However I know my current set up worked fine for at least a week or so. It must be a rogue app update or something its just impossible to pinpoint!
I can enter recovery just fine. All of a sudden my phone is OK for now but I know it will happen again!
Sent from my X10 using xda premium
Just an update.
I wasn't prepared to try stock rom as i KNOW my current setup did work. So at first i thought it was Titanium backup causing it as it happened straight after restoring apps. Installed apps manually but eventually got the error again.
Now i've flashed Dooms failsafe kernel and i'm testing that. If not it is an actual app from the market causing this!
Sorry for multiple posts. Just a bump to get this noticed. All appears well on failsafe kernel. My guess is my phone all of a sudden didn't like the undervolting as I didn't have it overclocked.
Ephumuris
I installed Resurrection Remix 2.5.1 (ICS) yesterday with the CM9 Kernel. Everything works (i think) up until I tried making a phone call. I have no audio during phone calls (I can still make them, i just can't hear or be heard). Audio works in other apps, such as music and games. The mic works when i try to use voice commands. I reflashed RR 2.5.1 with again, and tried the Siyah Kernel, and again using fluxi Kernel. I've rebooted the phone a dozen times, still no luck.
I had this issue the last time i tried to use an ICS rom (i tried 3 or 4 different roms about 3 months ago, all had the same issue). I downgraded to a GB rom (Unleased)and the phone was fine.
Any ideas?
(Aslo is the hardware back button and search button supposed to be disabled in ICS?)
2.5.1 is an AOKP ROM so I would suggest that from GB you flash an ICS stock firmware via Odin to get the bootloader installed properly and then you will need to do a full-wipe(possibly format system/data/cache if it helps)and then install.AOKP if not installed properly over AOSP will cause problems.
Threatlvlpurple said:
I installed Resurrection Remix 2.5.1 (ICS) yesterday with the CM9 Kernel. Everything works (i think) up until I tried making a phone call.
Any ideas?
(Aslo is the hardware back button and search button supposed to be disabled in ICS?)
Click to expand...
Click to collapse
The i9100 doesn't have a search button. The i9100 has a hardware home button, with a menu button on one side, and a back button on the other. This is the forum for the i9100...
If you really meant what you said about your phone having a search button, then I doubt you have an i9100. Check the label under your battery for model number.
EDIT to add; if you DO in fact have an i9100 and are just confused about the search/menu button... It sounds like you could also be describing an issue caused by a missing /efs/imei/keystr file. Do you also lack a power button menu, and the phone just shuts off if you hold the power button down? If so, are you missing that file?
If the answer is yes, make sure you are rooted, create an /efs/imei/keystr file containing the word ON.
Hmm. i didnt notice the AT&T version of the phone (the I777) had its own subforum. That's probably most of my issue, thanks for pointing it out.
So, As the title suggests, I've got a problem with my volume buttons in the FaaastJB v2.5 ROM.
The problem is they simply don't work. I've used a key testing app and when pressed, they both give "Unknown Key". However they work on my recovery and on the stock rom so its not the hardware itself. I've managed to get everything else working using the drivers on the site but I don't know if there is a driver related to the volume buttons or whether there is a file somewhere that I need to change? I have a backup of the system of the stock rom so can copy any drivers/files from there but so far nothing I've tried has worked.
So I'm wondering if anyone could point me in the right direction to fix this?
I would have posted this in the ROM thread but I haven't posted enough on XDA yet
Any help would be greatly appreciated!
EDIT: Doesn't Matter, It's been fixed. Turns out it was sun4i-keyboard.kl. The volume up and volume down were some random numbers instead of 115 and 114.
Thanks!
Adam
ajp8868 said:
So, As the title suggests, I've got a problem with my volume buttons in the FaaastJB v2.5 ROM.
The problem is they simply don't work. I've used a key testing app and when pressed, they both give "Unknown Key". However they work on my recovery and on the stock rom so its not the hardware itself. I've managed to get everything else working using the drivers on the site but I don't know if there is a driver related to the volume buttons or whether there is a file somewhere that I need to change? I have a backup of the system of the stock rom so can copy any drivers/files from there but so far nothing I've tried has worked.
So I'm wondering if anyone could point me in the right direction to fix this?
I would have posted this in the ROM thread but I haven't posted enough on XDA yet
Any help would be greatly appreciated!
EDIT: Doesn't Matter, It's been fixed. Turns out it was sun4i-keyboard.kl. The volume up and volume down were some random numbers instead of 115 and 114.
Thanks!
Adam
Click to expand...
Click to collapse
Hi, can you explain how you fixed that? I got the same problem, I replaced sun4i-keyboard.kl that worked for me in ics, and chmod 755, but still don't working. Any idea?
Edit: My mistake, I readed sun4i-keypad.ko, To fix this I¨ve just edited /system/usr/keylayout/sun4i-keyboard.kl and get volume buttons working again. I used my keys volume_up 139 volume_down 102
Hello,
I have a Galaxy S3 i9300 and I am running ArchiDroid V2.3.5 with Boeffla Kernel 2.2-beta1.
The problem I have with the phone is that it boot loops itself, although sometimes the phone does boot up and runs perfectly fine, but when I use my power button (on the right), it'll randomly turn off and reboot again. I have been using the "Sleep" option from the quick panel menu and not the power button.
I'm quite worried as I don't know if it is a hardware problem or just a problem with the ROM? I have tried wiping everything (sys, dalvik, cache, sd) and reinstalling a previous version of Archidroid but still no luck. If i press the power button for a second the boot menu comes up instantly (Reboot, Screenshot etc).
Also I am trying to install NeatROM (Sammy) to see if it works but in recovery I get this problem.
Code:
format() expects 5 args, got 4
E:Error in /data/media/0/i9300XXEMJ2_NeatROM_Lite_v4.8.zip
(Status 7)
Installation aborted
press any key to continue.
Thanks for the help in advance, I'm quite worried as this phone is nearly brand new!
Your problem is due to outdated update-binary used by Neat ROM.
You can try ArchiDroid 1.X to see if it's rom or hardware problem. For me it seems like your power button is getting stuck. and this causes hard reset.
JustArchi said:
Your problem is due to outdated update-binary used by Neat ROM.
You can try ArchiDroid 1.X to see if it's rom or hardware problem. For me it seems like your power button is getting stuck. and this causes hard reset.
Click to expand...
Click to collapse
Downloading Archi 1.X as I type. If it is my power button getting stuck, am I able to fix it myself?
i360* said:
Downloading Archi 1.X as I type. If it is my power button getting stuck, am I able to fix it myself?
Click to expand...
Click to collapse
Depends on your skills.
JustArchi said:
Depends on your skills.
Click to expand...
Click to collapse
Erm amateur skills at the moment
I will try Archi 1.X to see how it goes. Thanks for the prompt response.
JustArchi said:
You can try ArchiDroid 1.X to see if it's rom or hardware problem. For me it seems like your power button is getting stuck. and this causes hard reset.
Click to expand...
Click to collapse
Alright so this isn't a software problem as I'm having the same problem with this rom aswell
Any advice? I do not have warranty or insurance
This may seem absurd but this worked, LOL.
http://www.youtube.com/watch?v=SSLZFmhmBlc
I'm not sure if this is a temp fix or perm.
i360* said:
This may seem absurd but this worked, LOL.
http://www.youtube.com/watch?v=SSLZFmhmBlc
I'm not sure if this is a temp fix or perm.
Click to expand...
Click to collapse
Told you that it's hardware problem .