hi, i have a galaxy note 2 currently running 4.1.1 and a friend of mine downgraded it from 4.1.2 and it didnt work properly so he reflashed it to at&t (originally telus) and then reflashed it back to telus. He was attempting to unlock it. Ever since then, whenever i open messages and attempt to type, the keyboard doesnt appear. there is nothing that appears at the bottom where the keyboard should be. its just black and its definitely not in pen mode. When i usually start the phone up, it says "unfortunately, Snote has stopped working". and then when i attempt to open the app for Snote, it says there isn't enough space. When i go to enter my wifi password on the other hand, the keyboard appears. please help as soon as possible. thanks.
btw i have tried reseting and factory reseting and it hasn't solved the problem.
Related
I have a black Epic 4G Touch rooted and running EuroSkank just fine. I actually haven't experienced any issues besides video camera with effects causes FC. But I have a friend who has the white Epic 4G Touch and we rooted it, got a custom recovery and all went smooth. The second we put on the ROM on his phone he now is unable to make/Receive Calls and send/receive text/mms messages. Is there a color specific ROM? I tried flashing all sorts of ROMs to the device to fix it, but to no avail can I get it to work.
i have a white one and it works well with all kinds of custom roms. i believe they are the same.
feyerbrand said:
I have a black Epic 4G Touch rooted and running EuroSkank just fine. I actually haven't experienced any issues besides video camera with effects causes FC. But I have a friend who has the white Epic 4G Touch and we rooted it, got a custom recovery and all went smooth. The second we put on the ROM on his phone he now is unable to make/Receive Calls and send/receive text/mms messages. Is there a color specific ROM? I tried flashing all sorts of ROMs to the device to fix it, but to no avail can I get it to work.
Click to expand...
Click to collapse
White and black are essentiall the same phone.
Sounds like a network issue.
You could try a complete Stock+Root with an OTA build from sfhub http://forum.xda-developers.com/showthread.php?t=1721229 .
This should set everything right.
OR
You could try reseting the network settings. You'll need your MSL and a stock dialer.
Hands Free Activation/Network Reset:
Open dialer then ##72786# (factory reset on network settings)
Enter your MSL and hit OK
On the SCRTN screen select yes
Phone will auto reboot and take you to Hands Free Activation
If you have an SD card, media scanner will do its thing first.
Re-activation will initiate, let it run (DO NOT TOUCH THE SCREEN, no need to Press OK it will continue on its own)
Phone will then update Profile, then PRL, (you can select cancel when it searches for Firmware update if you want)
Phone will reboot again.
To get you MSL (if you're rooted)
1. Download "Terminal Emulator" from the app market.
2. Open Terminal Emulator.
3. type in getprop ril.MSL (make sure the .MSL is capitalized)
4. Press enter and poof, you have your MSL
Good luck
alright I found the problem. It wasn't the ROM at all, it wasn't the RIL, it wasn't anything to do with the custom ROM. It was actually his line that was having problems with the switch. We got it all figured out and the phone works great now. Thank you for your responses on getting it back up and working. We put a test line on the phone and it called just fine, so we found the issue was actually on his number. Phone fixed, and we are rocking the custom Jelly Bean again. Thank you everyone!
feyerbrand said:
alright I found the problem. It wasn't the ROM at all, it wasn't the RIL, it wasn't anything to do with the custom ROM. It was actually his line that was having problems with the switch. We got it all figured out and the phone works great now. Thank you for your responses on getting it back up and working. We put a test line on the phone and it called just fine, so we found the issue was actually on his number. Phone fixed, and we are rocking the custom Jelly Bean again. Thank you everyone!
Click to expand...
Click to collapse
Thanks for posting back the resolution. It always helps the community when we know what happened.
I'm on an S2 SPH-D710. I installed CM10 about 3 months ago, and about 2 weeks ago my 3g and MMS stopped working.
Right now I'm running the cm-10-20121027-EXPERIMENTAL-d710-ProjectSilk rom that was recommended.
I researched the problem and I keep coming across people saying it's the APN settings. But either everyone figures it out and leaves just a "OK Fixed it" message or they don't reply at all.
How do I access my APN from CM10?
[FIX]
Ok so I will offer my fix to anyone having the same problem.
Go here: http://forum.xda-developers.com/wiki/Samsung_Epic_4G_Touch/ROMs/S:D710.0.5S.EG30
Click the "Download-Full- One-Click" Link.
After it is done downloading turn off your phone. Then turn it on holding the power button and the volume down button.
Click Volume up to continue
The program you downloaded will need to be extraced which the EXE file does for you. Go to the Odin folder it created and run the program.
Plug your phone into your computer and wait for the program to say Added!
Then click start. This will factory reset your phone.
After it is all done you will boot into out of box state and possibly even get a network error code.
Go to settings/ about phone/ updates/ update system profile.
The phone will restart then BAM 3g and MMS working again.
Then reinstall your ROM. Basically updating the profile reset your APN settings which CM10 was unable to do.
Yo just bought a "new" s3 and the gps doesn't work. I say "new" because i looked at the flash counter before i rooted the phone and it said 1.
Anyways, I read through some of these threads and tried the screw tightening, that didn;t work.
I factory reset the phone, that didn;t work.
Tried topntp, that didn;t do anything..
tried other gps fix apps and nothing.....
I am a little afraid of opening up the phone to play around with gps antenna...
Has anybody found any luck with flashing a stock rom to fix this problem.
Any other suggestions please fill me in. I would really like to have a working gps.
I am running a Samsung S3
i747m
Jelly Bean 4.1.2 - vldmf1
Let me know if you need any more information about the software/firmware
zirgoth said:
Yo just bought a "new" s3 and the gps doesn't work. I say "new" because i looked at the flash counter before i rooted the phone and it said 1.
Anyways, I read through some of these threads and tried the screw tightening, that didn;t work.
I factory reset the phone, that didn;t work.
Tried topntp, that didn;t do anything..
tried other gps fix apps and nothing.....
I am a little afraid of opening up the phone to play around with gps antenna...
Has anybody found any luck with flashing a stock rom to fix this problem.
Any other suggestions please fill me in. I would really like to have a working gps.
I am running a Samsung S3
i747m
Jelly Bean 4.1.2 - vldmf1
Let me know if you need any more information about the software/firmware
Click to expand...
Click to collapse
1. Easiest and most reliable way. Try this first!
Enter the Samsung service mode by typing this code into the dial pad *#197328640#
Then go to Mainmenu>UMTS>Common>NV REBUILD>NV REBUILD> (Important: don't exit the menu yet!)
Wait 30+ sec
Long press power button and select "Restart / Reboot"
Now check your GPS from any software that may use GPS like "Maps" or "GPS Status"
Holy ****! You are a genius! That fixed the problem legit!
Whats the logic behind this?
Ok there's a short version to this and a long version, I'll start with the short version....
After a lot of tail chasing I've almost got the phone 100% back to how it should be, it seems that the only thing left to sort out is for me to be allowed to use USB instead of UART to reset my IMEI (got wiped out, "unknown"). Is there any reason why it wouldn't stick or a way to resolve it? The phone states "USB_Diag selected", "Change Complete", etc.... but when I click back it's still on UART. I've tried rebooting direct from that screen, coming out and rebooting, using the home button, etc, etc, etc. For whatever reason it just wont stick?
Long version......
I wanted to unlock the phone so that I could try out a payg sim that I was having issues with (only phone with a micro-slot). At first I tried to unlock it which didn't work, it suggested installing a prior baseband version of modem to get it to work so I tried that and it came up baseband unknown, imei unknown, etc, etc, etc. Fun fun fun. A bit of panic set in and I started installing anything I could find, I soon found myself with a "image resolution" boot error, which I believe was down to me trying to downgrade to 4.2.2 when 4.4 had already been installed. I eventually got myself back on an even keel but I'm still left with the IMEI unknown error. I'm trying to set it to the default using Samsung Tool Pro (24.3) but I keep getting an Access Violation (004074E0). I've disabled UAC just in case it wasn't fully running in administrators rights (which I had set it to do) and I've tried everything else I can think of. The one thing through browsing around that I can't get set properly is the 9090 menu to have USB instead of UART.
Info:
Model - GT-I9195
Version - 4.4.2
Baseband - I9195XXUCNJ5
IMEI - Unknown
Oh, one other thing that I recall. When selecting "Reset MSL" in the Samsung tools it said it completed successfully but my phone didn't reboot? I wasn't sure if that had anything to do with it. Secure boot status shows "Samsung"?
I have managed to force the IMEI using xposed but I would prefer not to go down that route if possible.
Thanks for any help
After applying the Android 12 OTA upgrade today, I can boot into the phone, however it looks like the System UI is constantly stuck instantly crashing upon launch, then reloading. the wallpaper is flickering on and off. I can take calls (and reboot the phone) just about, but I can't open any menu aside from the Power menu, or anything like that. Does anyone have any ideas how to resolve this? I'd try and enable adb mode or something like that but I can't beacuse I can't open any menu. I managed to boot into safe mode, but that had no effect and the problems are still happening.
Sometimes I can get it to briefly show the system icons, but it disappears too quickly for me to be able to do anything. If I was able to open the settings app, i'd be able to put it in USB file transfer mode to get my stuff of it, but I can't even do that.
Using the LG_UP tool, I can downgrade to the previous firmware, however I can't do anything as it then won't accept my encryption pin code. If flash the (broken) latest firmware back on, I can decrypt the phone, but I'm back where I was again where the system UI app just instantly crashes.
Right, so I think it's related to the lock screen. I was able to (somehow) manage to get it to the home screen from where I could open the settings app up and everything was fine, and was able to turn on USB file transfer mode. However as soon as the phone locked again, it stopped working. But it's very wierd.
You could try to do a factory reset. I think you have to start the device while holding one of the two power keys.
Ahkah said:
You could try to do a factory reset. I think you have to start the device while holding one of the two power keys.
Click to expand...
Click to collapse
I think that would work, but i'm trying to avoid doing that as there's still stuff i'd like to get off of it. Maybe a future firmware update may fix this bug.
Most probably there will be no further update. Do you have a chance to take a look at the system protocol via "adb logcat" during the crash? Typically the notorious "com.android.systemui" is the culprit.
PS: In fact it does not matter, but is your device some 820 (G8) or the downgraded version 810 (G8s)?
bergqvistjl said:
I think that would work, but i'm trying to avoid doing that as there's still stuff i'd like to get off of it. Maybe a future firmware update may fix this bug.
Click to expand...
Click to collapse
If you do decide to factory reset, please let us know if it resolved your issue.
idk which g8 you have but my g8 from xfinity just a few hours ago got the ao 12 v40a update and it did the saame thing the bottom screen buttons (home, back, etc ) flashed on n off crazily,
once i figured out the specific recovery mode combo and performed data wipe reset etc
it has seemed to of fixed it, phone calls and messaging are operational are what ive so far checked asa working phone out not recieved any incoming calls yet but messaging works
lmg820qm5
ao12 v40a
on metro pcs service
Ahkah said:
Most probably there will be no further update. Do you have a chance to take a look at the system protocol via "adb logcat" during the crash? Typically the notorious "com.android.systemui" is the culprit.
PS: In fact it does not matter, but is your device some 820 (G8) or the downgraded version 810 (G8s)?
Click to expand...
Click to collapse
It's the G8S. And I didn't have debug mode enabled, so adb doesn't work.
jtkc said:
idk which g8 you have but my g8 from xfinity just a few hours ago got the ao 12 v40a update and it did the saame thing the bottom screen buttons (home, back, etc ) flashed on n off crazily,
once i figured out the specific recovery mode combo and performed data wipe reset etc
it has seemed to of fixed it, phone calls and messaging are operational are what ive so far checked asa working phone out not recieved any incoming calls yet but messaging works
lmg820qm5
ao12 v40a
on metro pcs service
Click to expand...
Click to collapse
Yes, i'm pretty confident if I did a factory reset, it would work fine, but I really don't want to do that until i've got all my stuff off it.
i hear ya, understood, i just thought id fyi,
that the reset, as undesireable as it is. has appeared to fix the issue and phone, is as far as i can determine fully operational . the finger print reader, phone calls, and messaging all work
i just got the phone fixed less than an hour ago, after installing the 40a update a lil before noon or 2 hours ago lol