Related
Hello, i updated my GT540 to the 1.5 update from Mur4ik today, since this update i can't connect to my wifi, it says it's getting ip and then starting again, a loop for all the time. It worked since 1.6 and every rom later, 2.1, 2.2 and 2.3 and it worked in 1.4 of Mur4ik's Version. What is wrong now?
The Wifi is secured by WEP.
make sure you have typed the security key in right i have typed it in wrong and made me think it was connecting until i redone the security code
i have checked it several times now, i have done a factory reset via recovery mod and now it works. But thanks for the answer
Next time if you got some problems like that, just when you flash over fastboot write this:
fastboot -w
fastboot erase system
fastboot erase boot
fastboot flash system system.img
fastboot flash boot boot.img
fastboot -w
fastboot reboot
and have phun, I got some problems like u and the second time i was making it like that and it works perfectly !
torq1337 said:
Next time if you got some problems like that, just when you flash over fastboot write this:
fastboot -w
fastboot erase system
fastboot erase boot
fastboot flash system system.img
fastboot flash boot boot.img
fastboot -w
fastboot reboot
and have phun, I got some problems like u and the second time i was making it like that and it works perfectly !
Click to expand...
Click to collapse
right but also before do that is suggested to do a factory reset first of all
Thank's for this method.
it happened with me too..
after few day's i've realized that, it was after busybox updateing :S
Try edit ro.wifi.channels=(number from 12 to 16) in system/build.prop in Notepad++ (not in Root Explorer...)
Sorry for my english
I readed in the Mainthread about Wifi Problems but cant post there but whatever.
I've got the same Problem, but my Phone was rebooting for about an Hour again and again.
Finally i turn the airplane mode on but anyone know how to solve that Problem?
nick1990 said:
I readed in the Mainthread about Wifi Problems but cant post there but whatever.
I've got the same Problem, but my Phone was rebooting for about an Hour again and again.
Finally i turn the airplane mode on but anyone know how to solve that Problem?
Click to expand...
Click to collapse
first try removing wifi conections "forget" and add them again if that doesnt work then make factory reset or eather case reflash.
if so by fastboot use
fastboot -w
fastboot erase system
fastboot erase boot
then flash 1.8 again
fastboot flash boot boot.img
fastboot flash system system.img
fastboot reboot
Somehow after restarting my phone multiple times the issue is fixed. not sure what happened. But thank you everyone who may have took the time to try and investigate the issue. Really appreciated.
***************
AoA, hey guys,
was hoping someone here could help me out since I'm somewhat of a novice with flashing, etc
Anyways, I just flashed stock rom 4.4 for my nexus 4 downloaded from here: https://developers.google.com/android/nexus/images
But I since then many apps of mine are crashing, including facebook. The commands I followed for flashing are these:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-mako-makoz30d.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.03.img
fastboot reboot-bootloader
fastboot -w update image-occam-ktu84p.zip
I have added two log cats for when facebook crashed and they are here
The log cat was running for a while so please only focus on the end of the file
Full log cat:
first crash: https://drive.google.com/file/d/0BxamHeosEfaBd3dBcGg4NFFkLVk/view?usp=sharing
second crash (occured after I cleared facebook's data and tried again): https://drive.google.com/file/d/0BxamHeosEfaBeDB0dFdtVXhmaVE/view?usp=sharing
Partial log cats containng only the ending part are attach (had to cut them because of upload size limitation)
Hey everyone,
so fingerprint was working nicely for a while - but then it got sluggish. Took a couple of tries to get it unlocked and stuff. I (re-)added the fingerprints which helped at first. Then adding new fingerprints was sluggish as hell to a point where it didnt recognize my finger at all.
Camera app was sluggish as well (unusable) and then after 2-3 reboots it suddenly worked flawlessly again (camera AND fingerprint)! Felt like a cache thing or so...
Then it completely stopped working again!
So I made a factory reset - didnt help! Then I rooted and tried CM13 and CM12.1 - clean wipe etc - no luck at all!
I think it might be broken - but does anyone have an idea or approach I could try?
Thanks in advance!
debay said:
Hey everyone,
so fingerprint was working nicely for a while - but then it got sluggish. Took a couple of tries to get it unlocked and stuff. I (re-)added the fingerprints which helped at first. Then adding new fingerprints was sluggish as hell to a point where it didnt recognize my finger at all.
Camera app was sluggish as well (unusable) and then after 2-3 reboots it suddenly worked flawlessly again (camera AND fingerprint)! Felt like a cache thing or so...
Then it completely stopped working again!
So I made a factory reset - didnt help! Then I rooted and tried CM13 and CM12.1 - clean wipe etc - no luck at all!
I think it might be broken - but does anyone have an idea or approach I could try?
Thanks in advance!
Click to expand...
Click to collapse
I had the same experience after trying cm13. That is what I did. You could give this a try:
Download the fast signed image of COS 12.1 here http://builds.cyngn.com/factory/ham/cm-12.1-YOG4PAS3OH-ham-signed-fastboot.zip
Unzip it
Open cmd or terminal
Go to the unzipped folder
Execute this step by step:
fastboot -i 0x2b4c flash aboot emmc_appsboot.mbn
fastboot -i 0x2b4c flash modem NON-HLOS.bin
fastboot -i 0x2b4c flash rpm rpm.mbn
fastboot -i 0x2b4c flash sbl1 sbl1.mbn
fastboot -i 0x2b4c flash dbi sdi.mbn
fastboot -i 0x2b4c flash splash splash.img
fastboot -i 0x2b4c flash tz tz.mbn
fastboot -i 0x2b4c flash persist persist.img
This will restore your bootloader to stock Cyanogen OS. It will remain unlocked. After that you should be able to setup your fingerprints again.
Planet X said:
I had the same experience after trying cm13. That is what I did. You could give this a try:
Download the fast signed image of COS 12.1 here http://builds.cyngn.com/factory/ham/cm-12.1-YOG4PAS3OH-ham-signed-fastboot.zip
Unzip it
Open cmd or terminal
Go to the unzipped folder
Execute this step by step:
fastboot -i 0x2b4c flash aboot emmc_appsboot.mbn
fastboot -i 0x2b4c flash modem NON-HLOS.bin
fastboot -i 0x2b4c flash rpm rpm.mbn
fastboot -i 0x2b4c flash sbl1 sbl1.mbn
fastboot -i 0x2b4c flash dbi sdi.mbn
fastboot -i 0x2b4c flash splash splash.img
fastboot -i 0x2b4c flash tz tz.mbn
fastboot -i 0x2b4c flash persist persist.img
This will restore your bootloader to stock Cyanogen OS. It will remain unlocked. After that you should be able to setup your fingerprints again.
Click to expand...
Click to collapse
thank you so much, but unfortunately it didn't help :/
BTW: I am currently on COS12.1
Hello,
I have the same problem, after an boot my fingerprint stopped working. CyanogenMod and Cos 12.1 same problem. I waiting for your Help Guy.
Same problem here. Fingerprint scanner stopped working one week ago.
I can't unlock my phone nor add new fingerprints.
I haven't rooted my phone.
I am very disappointed.
debay said:
thank you so much, but unfortunately it didn't help :/
BTW: I am currently on COS12.1
Click to expand...
Click to collapse
you can also install any Cm12 nightly via TWRP then restore COS.
oh well, so I am not alone with this :/
I just tried CM12 nightly via TRWP, doesnt work as well....
It looks like that this is a hardware error. If you did what I have asked and it didn't fix it you should reflash the latest COS and lock your bootlaoder to send it for repair. Let's hope it will not take long...
Try to install the ZUI version with the QFIL tool, It will be wipe out everything. I think it's because of the software is mixed with something
I have the same problem with cmod. it was working very well with COS.
Always after reflashing the first times works great, but after a while begins to fail. Rebooting does not solve anything.
I think works better with yesterday update, but i have to recreate all stored fingerprints. its not working as good as COS but, for now, is usable.
I also have this issue... It's already a week or 3. Also did a factory reset, it didn't help.
What can we do?
If you want to set new fingerprints, does it also vibrate the whole time?
I had this issue. I just stored the same fingerprint twice. This allows the phone to store 40 images of the print rather than 20 and makes it a lot faster. It's just a simple workaround but I feel like it may help.
JonnyAw said:
I had this issue. I just stored the same fingerprint twice. This allows the phone to store 40 images of the print rather than 20 and makes it a lot faster. It's just a simple workaround but I feel like it may help.
Click to expand...
Click to collapse
Thats different - most of us cant even register new fingerprints - it just doesnt work at all anymore
Using the QFIL tool to wipe everything seems to be the last resort - I might try this
I have the same problem , the fingerprint sensor functioned very well for two months ago , and now he gives no more signs of life
I have a stock zuk z1 with COS 12.1 never root, stock bootloader, i never flash any rom on this phone
when i go in settings, all fingerprints are disappeared and i cant register new one, the sensor does not react
please help me guys
(sorry for bad english i speak french)
Little UP, today i have installed Zui internation, same problem..
ps:sorry for my english
Monget said:
Little UP, today i have installed Zui internation, same problem..
ps:sorry for my english
Click to expand...
Click to collapse
if you can try to install CM13, in the last nightly the fingerprint sensor is working
i can't do this with my zuk because i have to send it back to the seller
je suis aussi sur le forum jv on a eu le soucis de capteur pratiquement au même moment.
samzou said:
I have the same problem , the fingerprint sensor functioned very well for two months ago , and now he gives no more signs of life
I have a stock zuk z1 with COS 12.1 never root, stock bootloader, i never flash any rom on this phone
when i go in settings, all fingerprints are disappeared and i cant register new one, the sensor does not react
please help me guys
(sorry for bad english i speak french)
Click to expand...
Click to collapse
I have the same issue as you. Using the same version of ZUK and about 2 months ago fingerprint scanner stopped responding completely. Now the home button itself is playing up and I've had to revert to using on-screen buttons just to use the phone normally. I purchased my phone through GizChina so got in touch with them and they said to send it back to them as it's still in warranty. Gonna do that next week because it sounds like hardware fault to me?
I don't know but did someone ever tried what I have written in post 2? It has recovered my fingerprint reader already twice. You could also try to only restore the persist.img.
Planet X said:
I don't know but did someone ever tried what I have wurmen in post 2? It has recovered my fingerprint reader already twice. You could also try to only restore the persist.img.
Click to expand...
Click to collapse
I read your post but it's too confusing for a noob like me believe it or not
Planet X said:
I don't know but did someone ever tried what I have wurmen in post 2? It has recovered my fingerprint reader already twice. You could also try to only restore the persist.img.
Click to expand...
Click to collapse
Yeah as I said, I did! Didn't work unfortunately....
And I finally got the time to try the QFIL Tool - Bad news: Doesn't work as well
So it's hardware related and my device is going back....
TLR: Phone boots up and says. Launcher has stopped working, contacts has stopped working and etc.
Ok so i bought Moto G4 XT1625, yesterday. Was very happy with the device. It came with Android 6.0.1, i updated it to nougat 7.0.
But in android 6.0 and 7.0 both i noticed the phone giving random apps freezes and randomly even restarting on 7.0. The problem was minimal so i rebooted the phone 2,3 times and made it working. Then i received another update "NPJS25.93-14-4" on that update the phone got successful but bootlooped when booting for the first time on that update. I thoughts its ok so rebooted to bootloader and booted the phone from bootloader. the phone booted. after that another update came "NPJS25.93-14- (5 or 8) i dont remember properly" in this update the update failed during the installation. Keep in mind that i did not touch anything before this update. The phone was totally stock with stock recovery and everything. On this update the phone failed the update and i got constant bootloop no matter if i factory reset or erase cache it kept bootlooping, now i unlocked the bootloader and installed twrp and flashed a custom stock rom it crash on the boot. Again the random app has stopped working error came continously making the phone unusable. Then i flashed the stock rom correct firmware and everything it bootlooped again, then i rebooted numerous times the phone booted fine. Installed apps. This time did not get any app has stopped working error. Then rebooted the phone to install the sim card phone bootlooped again. Im 99% sure this is a hardware issue. Can somebody enlighten me? Whats going on in here? Thanks. I never faced this kind of problem ever in my life, i have bought more than 100 devices.
@whizinc
The Story is really frustrating especially when you bought it new :laugh:
So let's try to get your device working!
since you unlocked the bootloader you should clean flash the stock rom with fastboot https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 and see what happens. Don't put sim cards in and disable wifi. Just flash, boot and play around to see if it works without reboot.
strongst said:
@whizinc
The Story is really frustrating especially when you bought it new :laugh:
So let's try to get your device working!
since you unlocked the bootloader you should clean flash the stock rom with fastboot https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 and see what happens. Don't put sim cards in and disable wifi. Just flash, boot and play around to see if it works without reboot.
Click to expand...
Click to collapse
I used the OEMLock.bat script. So far the phone booted first time properly without any issue. Sim is working as well. Current its on setup wizard checking network. Lets hope its fixed permanently. I will play with the phone for 5,10 hours constantly and report back. Thanks alot man!
whizinc said:
I used the OEMLock.bat script. So far the phone booted first time properly without any issue. Sim is working as well. Current its on setup wizard checking network. Lets hope its fixed permanently. I will play with the phone for 5,10 hours constantly and report back. Thanks alot man!
Click to expand...
Click to collapse
Good luck:good:
UPDATE
It did not get past the "Checking Network" thing and after pressing the power button screen went black but i could see nav bar and status bar only. The phone has faulty hardware. Im now sure. Going to get it back tomorrow from where i bought it. Lets hope i get a refund or replacement. I bought it from a local mobile mall.
strongst said:
Good luck:good:
Click to expand...
Click to collapse
this phone has faulty hardware. IT failed. Again random apps saying "keeps stop working" such as : snapchat has stopped working
whizinc said:
this phone has faulty hardware. IT failed. Again random apps saying "keeps stop working" such as : snapchat has stopped working
Click to expand...
Click to collapse
Have you installed any third-party apps or restored them?
strongst said:
Have you installed any third-party apps or restored them?
Click to expand...
Click to collapse
nope, not a single app. Everything is clean and properly flashed.
whizinc said:
nope, not a single app. Everything is clean and properly flashed.
Click to expand...
Click to collapse
Snapchat is pre-installed?
strongst said:
Snapchat is pre-installed?
Click to expand...
Click to collapse
You did not get me brother. I was giving an example. Here is a real example:
"Contacts has stopped working"
".com android process keeps stopping"
these are the random errors.
whizinc said:
You did not get me brother. I was giving an example. Here is a real example:
"Contacts has stopped working"
".com android process keeps stopping"
these are the random errors.
Click to expand...
Click to collapse
It's irritating that you described that problem here before https://forum.xda-developers.com/mo...d-stock-jx-s-rom-series-t3658055/post73877878 now posting in a new thread. Does it mean you flashed the modified stock rom first and get the error and after this you flashed fastboot stock rom like described here? I don't get you.
@echo92 did you follow?
strongst said:
It's irritating that you described that problem here before https://forum.xda-developers.com/mo...d-stock-jx-s-rom-series-t3658055/post73877878 now posting in a new thread. Does it mean you flashed the modified stock rom first and get the error and after this you flashed fastboot stock rom like described here? I don't get you.
@echo92 did you follow?
Click to expand...
Click to collapse
posted in a new thread because the problem did not belong to the rom's thread, im sorry did i do something wrong? No. I did not flash the stock custom rom before all of this. I never wanted to flash a custom rom. The thing is the phone failed an OTA update which let me to come to this decision. The phone failed ".5" update and after that it bootlooped. So i thought flashing twrp and flash a custom rom with a clean install would fix it but even the custom rom the " xxx app stopped working error" came continously.
After that i followed echo92's guide and flashed the whole stock rom through fastboot. Still same issue. Random apps crashing.
I think this is hardware issue. Because every idea has been fail till now.
What do u say?
edit: note: when the phone failed ".npj25.93-14-5" update it was completely stock and i did not even touch anything, i dont know why it failed on the first place?
strongst said:
It's irritating that you described that problem here before https://forum.xda-developers.com/mo...d-stock-jx-s-rom-series-t3658055/post73877878 now posting in a new thread. Does it mean you flashed the modified stock rom first and get the error and after this you flashed fastboot stock rom like described here? I don't get you.
@echo92 did you follow?
Click to expand...
Click to collapse
Yep, I've been tracking the topic over both topics, gonna reply here to keep the other ROM thread clean too As I understand it:
Bought the device, had random issues with apps crashing on MM and Nougat.
Flashed TWRP and accidentally took the OTA, soft bricking in the process.
Flashed J-X's NPJS25.93-14-8 modified stock ROM, still app errors.
Reverted back to stock, still app errors, to the point where the device isn't useable and is now bootlooping...
However, @whizinc it's odd that you're experiencing these errors across flashes of the stock ROM and even a modified stock ROM and the data's been wiped each time...
Can you just confirm that with the NPJS25.93-14-4 (March 2017 fastboot ROM) that the stock ROM was flashed with these instructions as well, given that something odd's happening with your device...
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot reboot
The difference is that these include re-flashing your GPT/bootloader (just in case) and also include the equivalent of a factory reset (so effectively a clean install of the stock, unmodified, ROM). I recall you've mentioned doing this, just want to ensure we have a clean slate to work with.
If you can, can you post the output of your flash commands, just want to see if the flash worked, hold fire on updating to NPJ25.93-14.5 for now (or if you want to try your luck, you can get the fastboot file from here - you need to flash it with the above instructions, as it's an upgrade: https://androidfilehost.com/?fid=673368273298984458 )
Else, it may be a hardware failure - when you bought the device, was it new or sold as used? Do you have a warranty with the shop you bought the device from? If you can, can you boot into bootloader, attach your device to your computer, and in the adb terminal, type 'fastboot getvar all' without the quotes, please? This should output a list of the basic details of your device, please post that here - you may wish to edit out your IMEI if you wish.
I have difficulty understanding why someone would void the warranty (by unlocking the bootloader) of a phone that is seemingly defective out if the box. Not a very good idea.
echo92 said:
Yep, I've been tracking the topic over both topics, gonna reply here to keep the other ROM thread clean too As I understand it:
Bought the device, had random issues with apps crashing on MM and Nougat.
Flashed TWRP and accidentally took the OTA, soft bricking in the process.
Flashed J-X's NPJS25.93-14-8 modified stock ROM, still app errors.
Reverted back to stock, still app errors, to the point where the device isn't useable and is now bootlooping...
However, @whizinc it's odd that you're experiencing these errors across flashes of the stock ROM and even a modified stock ROM and the data's been wiped each time...
Can you just confirm that with the NPJS25.93-14-4 (March 2017 fastboot ROM) that the stock ROM was flashed with these instructions as well, given that something odd's happening with your device...
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot reboot
The difference is that these include re-flashing your GPT/bootloader (just in case) and also include the equivalent of a factory reset (so effectively a clean install of the stock, unmodified, ROM). I recall you've mentioned doing this, just want to ensure we have a clean slate to work with.
If you can, can you post the output of your flash commands, just want to see if the flash worked, hold fire on updating to NPJ25.93-14.5 for now (or if you want to try your luck, you can get the fastboot file from here - you need to flash it with the above instructions, as it's an upgrade: https://androidfilehost.com/?fid=673368273298984458 )
Else, it may be a hardware failure - when you bought the device, was it new or sold as used? Do you have a warranty with the shop you bought the device from? If you can, can you boot into bootloader, attach your device to your computer, and in the adb terminal, type 'fastboot getvar all' without the quotes, please? This should output a list of the basic details of your device, please post that here - you may wish to edit out your IMEI if you wish.
Click to expand...
Click to collapse
No no, You got the story wrong. Let me make it correct.
1: Bought the phone from a local mobile mall i have 3 days warranty left. (Phone was on Android 6.0 update)
2: Did not touch the phone. Just installed my daily apps. i.e: whatsapp,facebook and stuff.
3hone started doing odd things like auto touch while charging and apps saying "force stopped" error
4:Then i thought that this is Android 6.0 bug on Moto g4, so i should update it via OTA.
5: Updated to 7.0 same issues.
6:I saw another update did it as well 14-4 update. This update caused bootloop but i managed to make it through by booting from bootloader.
7: Then saw another update 14-5 and that update failed. (WHILE THE WHOLE PHONE WAS ON STOCK STATE) Why did the update fail? I didnt even touch the recovery or anything at that time.
8: Then i flashed the custom rom and the rest of the story goes on as u mentioned in the post.
And yes i cleaned flash the rom with the OEMlock.bat script that the guy above gave to me. It included all things such as boot,modem and all stuff. So it was def a clean install.
"fastboot oem lock begin
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem lock
fastboot reboot"
This was the script i used to flash the fastboot rom which is 14-4.
Then again got force stop errors and the 14-5 update failed causing bootloop again.
I just have 2 hours to check the devices further or else im gonna return it today. Thanks
MisterSteve said:
I have difficulty understanding why someone would void the warranty (by unlocking the bootloader) of a phone that is seemingly defective out if the box. Not a very good idea.
Click to expand...
Click to collapse
The phone was not in the official warranty from the start lol. I bought it used from a local mobile mall, they give 3 days checking warranty tho. I will try to get another handset. If i cant get it working.
whizinc said:
The phone was not in the official warranty from the start lol. I bought it used from a local mobile mall, they give 3 days checking warranty tho. I will try to get another handset. If i cant get it working.
Click to expand...
Click to collapse
Oh, you didn't mention that you have bought a used device! Bring it back to the shop and buy another/new one. Who knows what's wrong with that device or which history it has...
Apologies for getting the story mixed up, the information you provided in your corrected post and subsequently makes the situation worse though. Sounds like you bought a device exhibiting ghost touching or the beginnings of ghost touch and possibly was hard bricked/had the incorrect firmware flashed previously. As strongst mentioned, return that device. It sounds like it'll be more trouble than it's worth... especially for a used device.
UPDATE
I returned the handset to the shop guy, he was skeptical at first but then he gave it to another guy who said that the phone would go in used market claim and then after that he'll either return me the money or give me a new G4 device. I'll have to wait till monday. It sucks. Anyways Thanks alot guys for the help i appreciate it alot.
Feel free to lock the thread @ moderators.