help......
i have a strange problem i was on 2.3.3 unrooted
i tried to downgrade to the uk generic firmware with
flashtool, it flashed ok i restarted phone but
when phone goes to desktop its blank just the darkblue wallpaper with nothing on it
just the time in the top right taskbar and the signal strenth and the simcard symbol with a red x on it and the battery status bar
and that it.
it wont scroll left/right for more home screens, none of the buttons do anything
apart from power button and volume up/down
when i scroll the notification bar down it just says emergency calls only
and then in the top left its got the numbers 1980 3 8
what the hell is goin on
my fone boots up but i cant use it in any way
edit i also tried the sony ericsson update tool and did a full wipe and update and still the same
edit #2 ive managed to get the phone to boot fully now but with out radio signal. wireless and everything else works ok
just cant make calls txt etc
is there no fix to get radio back online?
that's what happens when you mess with the downgrade. My guess is that you messed up the baseband. Bring it back from where you bought it and just say that it stopped working after update.
Update: Try http://forum.xda-developers.com/showthread.php?t=1056094 first
ye the power of hind site,
all in the name of wanting to downgrade to get root again
i did a flash from that site fastgsm
and it got my play back to life but with no radio
so atleast i can use it for music/games and gps apps etc
and connect wireless
but calls/txt i cant
Related
Okay, here's the sad story so far:
I have a (previously) unmodded G1, with normal T-Mobile software. Yesterday morning around 5AM I get the little notice that I can upgrade to Cupcake. Unfortunately, it's 5 in the morning, I couldn't sleep, and I wasn't thinking all that straight... so I decided to root my phone and upgrade it to 1.5 instead.
So I downgraded to RC29, got myself root access, and installed the latest Jesus Freke build. Now the fun starts. As soon as the phone boots into the JF build I get constant android.process.acore force close errors. And I do mean constant, I force close, and it pops up again, force close, pop up again ad infinatum. I reflashed a few more times, varying the order of installing the radio update and misc. stuff like that, but still no luck.
So I decide to go back to the T-Mobile build without root access. I mean, I lived without it before, and not having root is better than not having a functioning phone, right? So I download the official cupcake update from google's dev site and install that. Woohoo, no more force closing, it looks like everything works!
Orrrrr not. I can't get into Settings now. I've tried to open Settings from the home menu, from a shortcut on the desktop, and through the menu button. Every time I try to do so, it will open up a black screen (like it's starting to load the settings menu), stay there for anywhere between 1-4 seconds, then go back to the main desktop screen. Everything else on the phone works, Market, Camcorder, soft keyboard, everything. Most apps I've downloaded also seem to work. However, when I installed the Toggle Settings app and tried to toggle the GPS, it popped into the settings menu with a black screen with the Security and Location text at the top, and then promptly went back to the app without changing the GPS.
I've tried everything I can think of at this point and the almighty Google doesn't seem to have any answers, anyone else able to give me some help? It would be much appreciated.
Update and bump, because I really need some help here:
I flashed the phone back to RC30, and left it overnight. In the morning there was an OTA update to cupcake available, so I installed that. Unfortunately, even with the OTA update the settings menu still won't stay up. Any advice?
Croaka said:
Update and bump, because I really need some help here:
I flashed the phone back to RC30, and left it overnight. In the morning there was an OTA update to cupcake available, so I installed that. Unfortunately, even with the OTA update the settings menu still won't stay up. Any advice?
Click to expand...
Click to collapse
Silly question, but did you do an alt-W to wipe the phone?
yep, wiped it many times during my trials and travails.
before or after the issue with the settings menu?
I've actually tried it both ways, wiped or not wiped, the settings issue remains the same.
Hi guys, this is my first post here and I hope someone can help me please!!
I got my phone 5 weeks no problem till last night,
basically when I am in screen lock state and then go unlock, I keep getting this anoying WHITE screen which on the top in blue band say "wiedges setting" I have to press the return button (on the right ) to get out of that screen , this happen everytime I go lock position, also notice even DURING my call after about 5-6 minutes through the call this white screen appears and it ALWAYS goes away by pressing return button.
so please tell me how to get ride of this?
if not how to reset without losing my apps and data? if I do factory reset is my apps will stay in andriod market, or do they also get deleted?
my phone IS NOT rooted phone.
what can I do, this is really killing me, as its everytimes into my face.
Please help me...
thanks so much
Just take it back to samsung. It's a new phone it's still in warranty
Sent from my GT-I9000 using xda premium
QUESTION : you phone is running on which ROM ? check ABOUT PHONE you have all informations about your phone
If you don't want to change the phone yourself then take it back and they will replace it for you , mind it will take at least 3 weeks to get it back
But if you have little flashing know how , you can flash a 1 file rom which you will not lost any data or apps , and then if you want to make it little faster flash Chainfire's cf-root kernel and convert the files to EXT4 ( cf-root is a stock kernel with root access and cwm only)
It sound to me more like an app that is running in the background that is not properly configured. Have you downloaded any new applications in the last couple of days ? Try uninstalling them to see if you get rid of the problem.
Hi,
I am new to this forum and do not know much of the technical terms. So here is my problem as best as I could say...
I have a unlocked Samsung S4 purchased last Sept (Philippines/SE Asia version, I think). The phone worked fine until the latest upgrade to Kitkat 3 weeks ago.
A week after the upgrade, the phone started rebooting itself. After checking this forum, it looked like a battery problem. On checking, it did have a swollen battery. At the same time, the S4 stopped working as a phone - meaning I could browse, use apps, but could not make calls.
First changed the battery with an original from Samsung, hoping everything would sort out. Unfortunately, it did not. The phone still kept restarting and the network signal showed as not available. So I went to my provider and got a new SIM card and changed it.
Unfortunately, that has also not solved my problem.
Now, my phone keeps rebooting itself. If I connect it to the charger, then the phone starts successfully. At times, it behaves well, but suddenly/randomly, if I touch an app (any app, no pattern) it will reboot again. Once it starts rebooting, it keeps doing that in the screen which has the samsung music comes - it would turn off again and keep restarting until that screen reaches again. Only if I connect to the charger would it start. Again, there is signal at times and there is no signal most of the times. My area has good network signal, so that should not be the problem.
I tried clearing the cache and clear all data/apps, but still no luck. Also, my battery still has / holds charge - so that is not the problem.
Could somebody please help me!!! Please let me know if you need any other details regarding this.
TIA.
Baseband version: I9505XXUFNBE
1. Sig & log in Sammobile.com
2. Download ur firmware: HERE
3. Unzip it
4. Phone in DOWNLOAD MODE
5. Flash the firmware through ODIN like the pic attached
It has nothing to do with your battery...but yes a swollen battery can be dangerous. Follow the steps told by @Joku1981 and don't upgrade to kitkat. Wait for a stable release from samsung.
Hi,
I have already upgraded to kitkat, so cannot downgrade now.. . I had the request to upgrade to kitkat by the phone (Samsung).
As mentioned by Joku1981, I downloaded the Philippines firmware and did as mentioned. However, the phone was still randomly shutting down on opening some apps (esp Gallery, Playstore, Chrome) and failed to reboot.
I also tried to download the pit file and flash it again as mentioned in http://forum.xda-developers.com/showthread.php?t=2265477. Still no lock.
I tried with UK's version of firmware, still same problem.
The phone can be restarted only if connected to the usb cable.
The "No Signal" issue seems to have been solved, but the rebooting randomly seems to be a real pain now.
After my latest flash, while i was in the third screen setting up the phone for language/accessibility --> "wi-fi setup" --> "Accept Samsung t&c's", the phone shut down again...
Is there any counter to identify the number of times the phone is flashed? Would it cause any problem?
Thanks
Also No Service now!
Also noticed that after the last 2 restarts, the network signal shows full strength. However the default lock screen shows "No Service" (see picture). When I try to call when the phoneis in this status, the phone gets stuck in the dial screen and has to be rebooted...
akpreets said:
Also noticed that after the last 2 restarts, the network signal shows full strength. However the default lock screen shows "No Service" (see picture). When I try to call when the phoneis in this status, the phone gets stuck in the dial screen and has to be rebooted...
Click to expand...
Click to collapse
Though you flashed, do a factory reset one more time to be on the safe side - make sure the phone is 100% charged, and given your case do NOT touch the phone until the reset has completed.
One more thing to try - from experience some batteries are bigger than others and you said your previous one became swollen. This may cause the power pins to become too compressed causing the new battery to lose contact. This manifests on the phone as rebooting at the slightest of movement/flexing, try this:
1. Remove the battery
2. GENTLY pull out slightly the power pins on the phone - don't pull too hard.
3. Put the battery back, put a piece of cardboard or something at the bottom of the battery to make sure there's good contact
Let us know of the results
Nothing seemed to work but only got worse. The phone could not stay on even for a few hours. Finally gave it to the Samsung Service centre yesterday. They sad it might take upto 3 weeks if there was a motherboard change needed.
Fingers crossed...:crying:
hi all,
since a day i have an extremely annoying issue with the note3 (sm-9005)
first, when it boots - it takes ca.10 minutes. stuck on the samsung animated logo.
then the black screen appears with the status bar (which i can drag down). normally i should have a lock screen appearing. but it just remains black. and in the status bar i have a message " you can now safely remove sd card" and "tap to enter knox". nothing happens when tapping those two...
can i play back an update from the SD card so that FW renews and i don't have to so factory reset and reinstall everything?
(ps. when connecting phone to a pc it shows no disks inside the phone so that if it still was locked...)
thanks in advance!
What do you mean by an update ???
JJEgan said:
What do you mean by an update ???
Click to expand...
Click to collapse
well same thing as one would do using kies, only somehow without kies. i saw in the recover boot an option "apply update from external storage" and was wondering what file could i use for that?
i have SWC region on my device...
Answer is no via above.
Firmware update is via Kies or Odin .
Alternative is custom rom via custom recovery .
Sent from my SM-N920C using XDA-Developers mobile app
UPD: after some searching i was able to unlock the device through samsung's findmomybile. however, half of the apps are missing, most of the ones which are not missing do not work, etc...
i guess not much left but factory reset. hopefully these are not corrupt internal storage problems.
spad said:
UPD: after some searching i was able to unlock the device through samsung's findmomybile. however, half of the apps are missing, most of the ones which are not missing do not work, etc...
i guess not much left but factory reset. hopefully these are not corrupt internal storage problems.
Click to expand...
Click to collapse
Did anyone come up with a solution to this other than findmymobile? I have had the same problem with my Note 3, e.g. taking 5-10 mins to load up from power off, the dreaded black screen with the power / wifi / etc icons shown on the top. My Note 3 was password protected as well, meaning I can't get into it even with Kies. I have the latest stock firmware installed.
I hadn't installed any apps to my phone before it died, however I do recall a security update being installed earlier in the day (this looked like an official Android one).
Any ideas? I went along to a Samsung Service Centre for help and they had told me that they had seen at least 5 cases of this on a Note 3 over the last two days.
Security update ??
Sent from my SM-N920C using XDA-Developers mobile app
same problem
hi,
I have the same problem. how did your problem solved?
jake2097 said:
Did anyone come up with a solution to this other than findmymobile? I have had the same problem with my Note 3, e.g. taking 5-10 mins to load up from power off, the dreaded black screen with the power / wifi / etc icons shown on the top. My Note 3 was password protected as well, meaning I can't get into it even with Kies. I have the latest stock firmware installed.
I hadn't installed any apps to my phone before it died, however I do recall a security update being installed earlier in the day (this looked like an official Android one).
Any ideas? I went along to a Samsung Service Centre for help and they had told me that they had seen at least 5 cases of this on a Note 3 over the last two days.
Click to expand...
Click to collapse
Solved !!!!!!!!!
sade9gh said:
hi,
I have the same problem. how did your problem solved?
Click to expand...
Click to collapse
I did not receive any response from anyone from anywhere. So I tried on myself and started manipulating every corner. I tried bluetooth and I could backup my contacts. It was the first victory.
I restarted into safemode by holding down the Down Volume for about 10 minutes! I wanted to try calling via pc via bluetooth. Just as a blind try. Meanwhile I saw a Knox notofication I had seen before so I just clicked carelessly. Vow!! The Knox Lock Screen was there blinking behind some error messages. I tried my lock pattern but nothing happended. I tried more and more, I was thinking this may corrupt the LCD! because it was blinking and went on off rapidly.
I saw that a counter is reducing. 20 attempts left.. 19 attempt... I worked hard till 4 or 3 then some message popup saying knox may be uninstalled. I said who cares? and went on. finally knox was uninstalled. I continued manipulating other available corners of the Note 3 and after a while I restarted and vow!! It was like back to life!
I came here writing for those who are out there seeking every corner of the web for a liitle bit of information.
I backed up my stuff and did a factory reset. It seems fine now.
I suggest manipulating every possible sequence of events. It will pop up some error and then the answer may rise!
best wishes
in my case i unlocked it with findmymobile, backed up stuff to SD card and did factory reset without much further thinking.
phone works fine until today
Hello, sometimes the phone needs 1 to 3 seconds to react when I scroll on the screen. For example, if I click on a widget and want to go to the app drawer then the phone freezes as if it crashed. This also happend sometimes when i surfing the internet with Firefox or when the keyboard is popped up (SwiftKey).
Am i alone with this failure?
The phone is unofficial unlocked but has the original recovery and no root. Latest asus Firmware.
What can i do? I also did an reset of the hole phone but nothing worked.