So I have my galaxy s4 here and its vibration seems really weak from bootscreen to the actual phone. I've installed cwm and rooted the device. I wasn't having this issue before but now its really weak. I have CyanogenMod 10.1.2 installed on it. Anything I can do?
re: fresh start
wutbutt said:
So I have my galaxy s4 here and its vibration seems really weak from bootscreen to the actual phone. I've installed cwm and rooted the device. I wasn't having this issue before but now its really weak. I have CyanogenMod 10.1.2 installed on it. Anything I can do?
Click to expand...
Click to collapse
The best thing you can do is to start at square one and Odin flash the stock firmware
to get your phone back into proper working condition.
You can find and download the official stock S4 firmware at http://SamMobile.com
Good luck!
Related
whenever i flash any custom rom whether the rom version is android 4.2/4.1.2/4.1.1 , my phone has no bootscreen and a messed up flashscreen when it sais (samsung galaxy note 2 GT-N7100) but then after waiting the appropriate time, the rom works fine but same problem when rebooting... i attached the flashcreen and how it looks like, i have no idea why this happens.i just press the lockscreen after rebooting and waiting and the rom works normally. i rooted using the Galaxy Note II Toolkit v3.0.0 GSM. i first experienced this right after flashing and entering recovery(cmw) but twrp worked fine then, now any rom i flash i experience this,
Is anyone faceing a similar problem or can help in anyway ?
I am using Samsung Galaxy note II GT-N7100
possible hardware issue.. have you tried reflashing the original firmware?
yes it works fine
agent_so said:
possible hardware issue.. have you tried reflashing the original firmware?
Click to expand...
Click to collapse
yes both screens work fine on stock rom after restoring ...so i dont think its an hardware issue
Hey guys I have white galaxy nexus maguro.
The problem I facing is quite strange and I want help.
I have been using my phone from more than 6 months my phone works fine with stock rom i tried installing rom before months back a custom rom and it was CM 10.1 my phone touch starts to respond after sometimes clicks are happening everywhere i changed rom back to stock and problem goes.
So now after many months i came to know about this amazing rom for gnexus CrDroid based on Cm10.2
I just installed it and the problem i faced before is here again.
So conclusion to all this is my screen touch response is extra sensitive or i dont know what happens with it when i install a custom rom on it,
On stock rom its fine,
So what you guys think i should do or anyone else had the problem like that if they solved it please help thanks
Nuke_- said:
Hey guys I have white galaxy nexus maguro.
The problem I facing is quite strange and I want help.
I have been using my phone from more than 6 months my phone works fine with stock rom i tried installing rom before months back a custom rom and it was CM 10.1 my phone touch starts to respond after sometimes clicks are happening everywhere i changed rom back to stock and problem goes.
So now after many months i came to know about this amazing rom for gnexus CrDroid based on Cm10.2
I just installed it and the problem i faced before is here again.
So conclusion to all this is my screen touch response is extra sensitive or i dont know what happens with it when i install a custom rom on it,
On stock rom its fine,
So what you guys think i should do or anyone else had the problem like that if they solved it please help thanks
Click to expand...
Click to collapse
You didn't do anything wrong while flashing? Or maybe a mod? Maybe even an app? You could try to flash the ROM and don't install apps and see how that goes for some days. If that doesnt work maybe you could flash stock via fastboot and then flash the ROM.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
You didn't do anything wrong while flashing? Or maybe a mod? Maybe even an app? You could try to flash the ROM and don't install apps and see how that goes for some days. If that doesnt work maybe you could flash stock via fastboot and then flash the ROM.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for replying
No I didn't do anything wrong its not my first andriod phone even tho that post was first one on xda never ran into problem.
I think its problem with gnexus many people have different issues with roms but mine is just that its giving me issues on custom roms tried many things flashing again dirty flashed everything.
on stock problem is gone but on the ones i mentioned i am getting this bug that i cant even use my phone i unlock it and touch starts to respond all over the screen
Hey guys since i am testing i just installed slimbean and its working perfectly just like how stock behaves so can someone tell me what slimbean 4.3 and Stock 4.3 have in common and what CM10.2 has not and giving me issues?
Hi guys,
I have had the s2,s3,galaxy nexus,original note and i am used to flashing and modifying,but i have a serious issue with the note 2.
The problem is whenever i flash AOSP rom(cm,aokp,pa) my wifi would not connect.It shows the name of the network and when i click conenct nothing happens.Flashing back TW rom fixes it,wifi works like a charm. I've done full wipes but it doesn't seem to resolve the issue.I tried different kernels,but that doesn't help either.
So I am stuck at TW roms and i hate that.Anyone has any ideas?
You can try options 2 and 3 from this thread.
Thanks for your reply,but i tried this and it didn't solve my problem.
Anyone?
spookhc said:
Anyone?
Click to expand...
Click to collapse
I Have the same problem...
Not sure that it will help you but I read something yesterday about this issue.
The solution was to NOT restore your Google profile during first boot so you should full wipe and try again.
Primokorn said:
Not sure that it will help you but I read something yesterday about this issue.
The solution was to NOT restore your Google profile during first boot so you should full wipe and try again.
Click to expand...
Click to collapse
This actually has nothing to do with the problem.
After a few days I finally found the cause ,and therefore,a decision to the problem.
It is the bootloader from 4.3 sammy leaks.It seems that this new leaks(probably the reason being KNOX) cause malfunction of wifi in aosp roms.What i did was ODIN flash stock MG1 from sammobile .This brought back stock recovery so i had to flash TWRP again and it solved the issue for me.
Before that i had tried changing roms,kernels,recovery,modems and nothing worked so I am pretty sure it is the new 4.3 leaks bootloader.
Some people will say that it can\t be the issue because they are using 4.3 sammy and do not experience the same problem on aosp roms,but i think thats because they flash it through CMW ,which doesn't change bootloader,while flashing through ODIN does.
With my Note2 this is not the solution. I've tried everything. What you said, move file "pit" ..... but nothing. I can not connect wifi. The connection does not appear region Spain, and have opted to choose europe, but neither. I do not know to do. CM 10.1 also does not work WIFI. In Stock ROM or Custom ROM works fine fine, but in ROM CM 10.1, 10.2, AOKP don't work.
spookhc said:
This actually has nothing to do with the problem.
After a few days I finally found the cause ,and therefore,a decision to the problem.
It is the bootloader from 4.3 sammy leaks.It seems that this new leaks(probably the reason being KNOX) cause malfunction of wifi in aosp roms.What i did was ODIN flash stock MG1 from sammobile .This brought back stock recovery so i had to flash TWRP again and it solved the issue for me.
Before that i had tried changing roms,kernels,recovery,modems and nothing worked so I am pretty sure it is the new 4.3 leaks bootloader.
Some people will say that it can\t be the issue because they are using 4.3 sammy and do not experience the same problem on aosp roms,but i think thats because they flash it through CMW ,which doesn't change bootloader,while flashing through ODIN does.
Click to expand...
Click to collapse
Hello XDA. Currently I own a Samsung Galaxy S3 SGH T999 from T-Mobile. As soon as I got it I had my cousin root it for me. For a while I had no issues flashing ROMS. The ROM I am using is AVATAR 4.2.2. I am noticing now that when I go to flash a new ROM it stays in the boot logo screen. It does that with just about every ROM I try to flash. I went back to my cousin and he updated TWRP for me. To this day I am still having the same problem. I am not sure what is going on please help me.
ghostgaming said:
Hello XDA. Currently I own a Samsung Galaxy S3 SGH T999 from T-Mobile. As soon as I got it I had my cousin root it for me. For a while I had no issues flashing ROMS. The ROM I am using is AVATAR 4.2.2. I am noticing now that when I go to flash a new ROM it stays in the boot logo screen. It does that with just about every ROM I try to flash. I went back to my cousin and he updated TWRP for me. To this day I am still having the same problem. I am not sure what is going on please help me.
Click to expand...
Click to collapse
Be aware that you need to completely wipe your phone when switching between ROMs (does not apply if you are upgrading to a newer version of the same ROM). Flashing over can cause issues like yours.
Hello,
So I've flashed before Slimbean, but had problems with the "can't connect to camera" problem, so I decided to flash Slimkat 4.4.4 which fixed the camera problem.
New problem now is that i can't get any gps signal. I can turn it on, but no signal. Anyone have a solution to this, or is experiencing the same problem?
Downloaded from here: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1074-d2att-d2tmo
drakemiller40 said:
Hello,
So I've flashed before Slimbean, but had problems with the "can't connect to camera" problem, so I decided to flash Slimkat 4.4.4 which fixed the camera problem.
New problem now is that i can't get any gps signal. I can turn it on, but no signal. Anyone have a solution to this, or is experiencing the same problem?
Downloaded from here: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1074-d2att-d2tmo
Click to expand...
Click to collapse
Hi, the link you provided points to build 4. You can find build 9 which is the latest slimkat here http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1183-d2lte
This is the one I have for my Koodo I747M. *note camera seemed a little buggy in some instances, so I installed open camera. Seemed to work a lot better.
I'll give it a try, thanks for the help. Quick question, will this work on my phone model without bricking? I only tried the at&t not the d2lte.
Also can you send me the link for this open camera you were talking about for my device as well?
drakemiller40 said:
I'll give it a try, thanks for the help. Quick question, will this work on my phone model without bricking? I only tried the at&t not the d2lte.
Also can you send me the link for this open camera you were talking about for my device as well?
Click to expand...
Click to collapse
I'd imagine it should be ok, since we have the same phone pretty much I'm on koodo which is pretty much telus without the customer service hehe. for kitkat at the end of development they basically lumped a d2att, d2tmo etc together. (this has reverted for the lollipop builds out there).
The last OTA I got was FOB1, so you may want to go to stock to ota to the latest updates from telus. Just so you have the latest bootloader/firmware. But that's up to you of course.
It's a google play app open source, the slimkat one I had seemed to lockup when switching from front to back camera and from camera to video. https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en
What are you using to flash them?
serathe said:
I'd imagine it should be ok, since we have the same phone pretty much I'm on koodo which is pretty much telus without the customer service hehe. for kitkat at the end of development they basically lumped a d2att, d2tmo etc together. (this has reverted for the lollipop builds out there).
The last OTA I got was FOB1, so you may want to go to stock to ota to the latest updates from telus. Just so you have the latest bootloader/firmware. But that's up to you of course.
It's a google play app open source, the slimkat one I had seemed to lockup when switching from front to back camera and from camera to video. https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en
What are you using to flash them?
Click to expand...
Click to collapse
Im not very experienced lol and got lost on:
"The last OTA I got was FOB1, so you may want to go to stock to ota to the latest updates from telus. Just so you have the latest bootloader/firmware. But that's up to you of course. "
I'm using TWRP
Ah, ok I just keep a backup in case anything goes bad flashing roms. If you use TWRP to flash them it only affects the boot image, data and system. So if you have problems you can restore from backup nice and easy.
I'm swapping between a few right now. So far my only uh oh experience was when I tried to upgrade TWRP, no problems with roms. But I use TWRP as well, works great.
Basically the baseband version on our phone, it's the radio and bootloader. Before I had rooted it I had gotten the latest updates by checking for updates. It downloaded and upgraded to FOB1 (Baseband I747MVLUFOB1), then I rooted and played with flashing. Not sure if you made a backup of your original install before trying another rom. But it's not a necessity for slimkat, I don't believe.
serathe said:
Ah, ok I just keep a backup in case anything goes bad flashing roms. If you use TWRP to flash them it only affects the boot image, data and system. So if you have problems you can restore from backup nice and easy.
I'm swapping between a few right now. So far my only uh oh experience was when I tried to upgrade TWRP, no problems with roms. But I use TWRP as well, works great.
Basically the baseband version on our phone, it's the radio and bootloader. Before I had rooted it I had gotten the latest updates by checking for updates. It downloaded and upgraded to FOB1 (Baseband I747MVLUFOB1), then I rooted and played with flashing. Not sure if you made a backup of your original install before trying another rom. But it's not a necessity for slimkat, I don't believe.
Click to expand...
Click to collapse
Yeah I always create a nandroid and backup my IME.
drakemiller40 said:
Hello,
So I've flashed before Slimbean, but had problems with the "can't connect to camera" problem, so I decided to flash Slimkat 4.4.4 which fixed the camera problem.
New problem now is that i can't get any gps signal. I can turn it on, but no signal. Anyone have a solution to this, or is experiencing the same problem?
Downloaded from here: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1074-d2att-d2tmo
Click to expand...
Click to collapse
First thing to try for GPS problems is taking off the back cover and snugging up all the little screws around the phone. Sometimes they work their way loose and the GPS antenna seems to be the first thing to suffer from it.
If that doesn't cure it you might need to flash a stock or at least stock based ROM and rebuild the nvram. Here's a link that describes how to do that if you need to.