I posted this in fascinate forums and haven't been able to get any help, so I figured I would post here as well. I have been running cm7 and installing the nightlies as they come out. When I flashed nightly #9, I lost complete use of my soft keys. Imagine how annoying it is to have to reboot to change screens. I installed a catlog to see if I could figure out what was going on, but I know absolutely nothing about programming. So, this is what I think I figured out. In the bootup, there's no device for "mice", says something about device not found, and then there's another error in system bootup about the"face" error. So I think I have lost something in the system bootup that runs my soft keys.
Does anyone else have issues with their soft keys? Before I lost them totally, my back button would activate all by itself until everything and I mean everything was closed.
I haven't been able to go back to stock to see if that works because I haven't had any computer access since this happened. I will be home tomorrow, so I can see if that helps.
If anyone has any other insight, I'd be really glad to know.
Thanks,
Mona
any solution yet to this my 4 soft keys wont work i dont know wat to do
No resolution for soft key fail
monac66 said:
I posted this in fascinate forums and haven't been able to get any help, so I figured I would post here as well. I have been running cm7 and installing the nightlies as they come out. When I flashed nightly #9, I lost complete use of my soft keys. Imagine how annoying it is to have to reboot to change screens. I installed a catlog to see if I could figure out what was going on, but I know absolutely nothing about programming. So, this is what I think I figured out. In the bootup, there's no device for "mice", says something about device not found, and then there's another error in system bootup about the"face" error. So I think I have lost something in the system bootup that runs my soft keys.
Does anyone else have issues with their soft keys? Before I lost them totally, my back button would activate all by itself until everything and I mean everything was closed.
I haven't been able to go back to stock to see if that works because I haven't had any computer access since this happened. I will be home tomorrow, so I can see if that helps.
If anyone has any other insight, I'd be really glad to know.
Thanks,
Mona
Click to expand...
Click to collapse
I had the same issue when I flashed to Paranoid Android, a jellybean based ROM. Everything worked fine for me with Cyanogenmod 7.2, then I flashed to Android 4.1 and lost the use of the soft keys. I still haven't resolved the issue.
For the record
Charcaroth said:
I had the same issue when I flashed to Paranoid Android, a jellybean based ROM. Everything worked fine for me with Cyanogenmod 7.2, then I flashed to Android 4.1 and lost the use of the soft keys. I still haven't resolved the issue.
Click to expand...
Click to collapse
In case anyone else has this issue, I tried flashing a stock Froyo ROM, a stock Gingerbread ROM, CM 7.2 again, and even stock GB with the latest Verizon Wireless update for GB and the softkey functions never returned. I've managed to put Paranoid Android 2+ back on the Fascinate, a Jellybean ROM, so I can mimic the buttons with onscreen controls, but it eats up a lot of screen real estate. It's a workaround, not a solution by a long shot.
Related
Please help me fix the camera of my Cingular 8125 G4 device. After I flashed a new rom using soft SPL method, which I think G4 safe rom, the camera is not working. When I press the camera button, I only see the spinning circle with different colors and the screen lights up a little bit than the normal brightness and stuck it there. And after a few seconds, the phone hangs up. Need to soft reset in order to put back the device in a functional state. I don't know why this happened as I followed all the necessary steps in using softSPL upgrade method. Maybe there is something wrong in the device registry. Does anyone has the same camera problem. Please share the tricks, tweaks or anything just to bring back the camera function again.
BTW, I reflashed back the official cingular stock rom but no luck at all its the same.
I see that you are using the TNT ROM, so I would to and flash UP to the newest version and see if that fixes your problem, it sounds like the camera software and drivers are not getting installed for some reason.
I reflashed the tnt rom but no good. Tried also to go back to the original cingular stock rom but still not working. Even in the windows\camera cannot make it. But when tried not to use the device for a some hour in standby mode, the camera works for a while then it hangs up. And go back to non-functional state.
Sir, what you think is the problem? I suspect its the software installed in the device based on what the camera behave. Or definitely the hardware itself and need to replace. Bad for me because I am living in the Philippines and as far I knew there is no service available in our country.
Thanks in advance whatever help you can give. Have a nice day.
Try using the wizard service tool to increase your page pool to 6mb.
Camera work again after....
My dead camera work again after I flashed rom cooked by Cracing. This rom is awesome. Its compatible with Wizard. Thanks to Cracing.
Shortly after Team DRH's last update for their ICS 1.2 I installed it no problem and it ran for a few weeks. Then I left the tablet alone for a week or so and when I turn it on now the wifi is not working, it just says "turning on wifi" but never actually does. I've followed the reflash instructions here: http://forum.xda-developers.com/showpost.php?p=23147934&postcount=4 and I can re-install ICS endlessly. But even after following those instructions, and even after RayWaldos NVFlash for dummies, it still always says "turning on wifi" but doesn't.
When, during the above flashing, I let the stock tapntap boot, wifi works no problem. It's only when i install a ROM that it stops working. I even tried installing Gtabcombover and it gave me the same "turning on wifi" problem.
I did try searrching the forums, but I see no mention of this anywhere.
Thanks.
If I can be more to the point: does anyone know of a way to completely reflash stock everything? I thought I was doing that, but obviously not enough.
Or do I need to crack open my case and push that Dirty Little reset button?
Slightly Askew said:
If I can be more to the point: does anyone know of a way to completely reflash stock everything? I thought I was doing that, but obviously not enough.
Or do I need to crack open my case and push that Dirty Little reset button?
Click to expand...
Click to collapse
I was able to use the DHR NUFLASH.. It worked real well for me.. download the right file (bootloader 1.1 or 1.2) to your pc, for your g-tab.hook up your USB cable Turn on your tab wile holding your volume (-) key , the logo will come on and then go black. Then go to the nuflash- win file, you downloaded to your pc and run.. The instructions are on the DHR site are vary good I read them a few times before I tried. Its worked great for me.. I'm a noob. Lets just say its just about makes the gtab un-brickable...
Sent from my G Harmony v2.8 using xda app-developers app
graftonrod said:
I was able to use the DHR NUFLASH. . .
Click to expand...
Click to collapse
Well the good news is that after reading your post I went straight to the DRH website and lo and behold they had just posted Beta 1.3 that morning. I redownloaded their Full Stock CWM 5504 NVFLASh file even though I already had it, and the Beta 1.3.
I flashed the stock file and let it boot just like they said but the setup process began a FC loop and would not complete. I simply rebooted and the setup was able to complete. The I installed the Beta 1.3 with no Gapps and it worked like a charm. Wifi was working and everything, except there was no Market. So I did a wipe/FR and installed again this time with Gapps and everything is back, wifi, market, all good. And I have noticed that it all seems to work a ton faster and smoother.
I just installed Galaxy Task 14 slim coming from CM10 Upgraded cwm to newest through Odin Flashed made a backup and installed Worked great for a few minutes Tried front and back cam out then out of nowhere the screen turned scribbled I cant see nothing not even power off or reboot buttons what do I do?
Galaxy Tab 10.1 p7510wifi
JavaKid said:
I just installed Galaxy Task 14 slim coming from CM10 Upgraded cwm to newest through Odin Flashed made a backup and installed Worked great for a few minutes Tried front and back cam out then out of nowhere the screen turned scribbled I cant see nothing not even power off or reboot buttons what do I do?
Galaxy Tab 10.1 p7510wifi
Click to expand...
Click to collapse
I rebooted and it seems to come up right will someone with more experience please elaborate on what may have been the cause so I can fix whatever happened.
EDIT: Keeps coming back eventualls flashing another kernal now. Any info would be great thanks.
Also tried installing CM10.1 newest out.... Same issue distorts screen with horizontal lines then just kept doing it....Had to restore twice from recovery only one rom works what up? Am I alone in this?
The only stable kernal is 2.6.36.4 but when I flash it doesnt take for newer builds...... Does anyone have the answer? If I dont put the tablet to sleep it works fine once awaken from sleep its scrambled again???
FIXXXED!!!!!!!!!!!
JavaKid said:
I rebooted and it seems to come up right will someone with more experience please elaborate on what may have been the cause so I can fix whatever happened.
EDIT: Keeps coming back eventualls flashing another kernal now. Any info would be great thanks.
Also tried installing CM10.1 newest out.... Same issue distorts screen with horizontal lines then just kept doing it....Had to restore twice from recovery only one rom works what up? Am I alone in this?
The only stable kernal is 2.6.36.4 but when I flash it doesnt take for newer builds...... Does anyone have the answer? If I dont put the tablet to sleep it works fine once awaken from sleep its scrambled again???
Click to expand...
Click to collapse
Did not realize this help section was so dead...... Anyways a few hourse later I discovered this thread pertaining to the issue... Should have a sticky or something its rather important so you don't think your tab is junk. For anyone having this issue go to http://forum.xda-developers.com/showthread.php?t=1975407
Cleared the issue right up I am on the latest cm build and running great no more sleep scribble display crap.
Hey Guys,
I use a stable 10.1.3 CM since a year on my S2. Lately the camera started to quit qorking: "can't connect to camera".
About this time the torch (LED app) app did the same thing: "unfortunately torch has stopped".
What I did: do a full data/cache/dalvik cache erase: factory reset.
The camera/torch still malfunctioning.
Then flashed the last nightly CM: cm11-20140429, but still no luck.
Then reflashed the old stable version, maybe if it'll work, but noooo.
Do you have any suggestion to resolve this issue? My phone is 2 years old, never had a problem with it. Until now.
Shall I flash something via Odin?
Is there a "deeper" way to rewrite the camera/LED firmware/code/whatever?
(I was wondering if flashing these 2 CM versions the appropiate firmware's aren't rewritten)
Thanks in advance for the replies!
you can try more ROMs. However, there is a possibility that its a hardware issue.
The camera stopped working on my galaxy S1 after a factory reset.
I never did get it working again, and I tried about 4 different camera firmwares, flashing back to stock, and replaced the camera module too. Nothing worked.
knuckles1978 said:
The camera stopped working on my galaxy S1 after a factory reset.
I never did get it working again, and I tried about 4 different camera firmwares, flashing back to stock, and replaced the camera module too. Nothing worked.
Click to expand...
Click to collapse
Sorry to hear that.
I'm wondering now to replace the camera module as well.
I quickly tried this 3 ROM: aosb_kk_1.3.6_i9100, omni-4.4.4-20140728-i9100-NIGHTLY, Slim-i9100-4.4.2.build.5-OFFICIAL-4068, but with the same disappointig result: no camera, no LED.
If I first start LED/torch isntead of camera, the LED sometimes flashes:
I switch on, but nothing happens. Then switch it off: after a few sec delay the button will show the "off" state, and during this process the LED flashes for 1 sec.
I will try to revert to stock with odin, maybe...
The camera module is very easy to change. All you have to do is unplug it and plug a new one in.
You might be luckier than me.
knuckles1978 said:
The camera module is very easy to change. All you have to do is unplug it and plug a new one in.
You might be luckier than me.
Click to expand...
Click to collapse
Yes, but what if the same thing will appear? Ie. I'll change the camera module, but won't work.
Isn't there an easier way to check if surely the camera moduled is dead?
Btw I downgraded it to stock ROM via Odin, but camera still dead, so it is probably not a software error. :crying:
There's no way of telling if your camera module is broken without putting a new one in.
It didn't fix it for me though. And believe me when I say I spent a lot of time trying to figure it out.
Ok then.
Thank you very much for the support!
Hi all, hoping to get some help. I rooted my phone the other week and was using viperrom. I had no problems whatsoever, no glitches that I could remember. That is, until I decided to trade my m8 with a friends Note 3. I factory reset it and give it to her, I left the viperrom on because she didn't mind but then the glitches started to happen. The onscreen bottom 3 buttons disappeared for her (home, back,etc.), So I reset it again but the problem persists. I searched for an at&t stock rom and sideloaded that after master resetting, wiping the dalvik cache and all that... now a different problem popped up. It hangs at the HTC logo for what seems like forever, but then I noticed the volume up and down make a noise as if the phone is loaded up. I pressed the power button a few times and eventually the screen turned on and I could see the home screen. This happens every time I restart the phone and I have tried reinstalling the stock rom a few times. I am now in the process of trying a different stock rom.. the first was odexed and this new one is deodexed, I dont know if that makes a difference in my situation but does anyone know what could be causing this? Any help would be appreciated.
Nvm, after a few more master resets it seems to have sorted itself out... not sure what it was but its gone now.
If its the latest version of Viper, based on 2.22 software, you need to update the firmware package, otherwise the long boot times will continue.
Details here: http://forum.xda-developers.com/showpost.php?p=54408500&postcount=9592