G925A stuck on welcome screen after factory reset - AT&T Samsung Galaxy S6 Edge

Its been about 2 months since my phone has been unreachable to everyone that is trying to call me even though my phone is fully working with full tower and data services active almost 24 hrs a day. Everything was working fine instead if someone tried to call me they would have to hear "This phone is unreachable at the moment" operator message. My operator is Airtel btw.
So i googled this issue and some people suggested factory resetting. I thought its just a factory reset and went to recovery and reset the phone (Not my first time, but my first factory reset after i upgraded to Nougat). So after factory reset i rebooted the phone from recovery and was greeted with the welcome screen. I added samsung account, google account. Everything went fine until it asked me for time and date. I selected the time zone and it was showing the correct time so i pressed next, then again it reverts back to the same screen. I tried pressing next a million times but im stuck on that screen.
I did a cache wipe and factory reset again and same problem. Please help.
I think my Android is G925AUCU6EQCF which should be Nougat 7.0. I updated it way back when Nougat came to xda through adb sideload and havent updated the security patches. So the firmware version must be this G925AUCU6EQCF.

Related

[Q] launcher crash after factory reset

Hello,
I have a SGS I9000 Gt from France I think.
Everything was running good. I installed a bunch of apps when I first got the phone, checking stuff out. After playing with it for a few months I now have a good idea of what apps I would like to keep.
I decided to do a factory reset so I could start fresh when froyo does come out.
I performed three button recovery and did factory reset and wipe cache partition.
Problem is when I reboot I constantly receive "The process "blank" has stopped unexpectedly. please try agian." message, and I hit force close and it just pops right back up. TwLauncher, Daily briefing, acore, and a google one.
I did notice that in the recovery mode menu I get some red text saying "multicsc : can not acces to /system/csc/XEF/system/" But when I go through the steps to reset and clear cache, it does it and gives me a message "wipe complete"
I removed battery and sim card No sd, and tried again with no luck, every time I boot now same thing, apps keep crashing.
I hope that makes sense I don't really know what to do.
So yea any help would be great!
Thank you so much for your time.
I almost have the same problem here.
I updated the firmware with Kies, using the default firware that was found by Kies.
I guess it has to be a custom made ROM made by/for my phone service provider (Bouygues, a French company).
Upon restarting, I get the same pop-up messages. Cannot close them fast enough to use anything. My phone is not usable, though not bricked.
Ps : formerly running off-the-factory custom Bouygues rom. Rooted and using OCLF or something lag fix.
I solved at least MY problem :
Do a factory reset and wipe cache AND user data. Simple as that
The answer was actually in the [Warning!!!] Do not flash... thread. I should slap myself for not looking into it first.
Hope it solves your problem too.
Thanks for the help, but how do you how did you wipe user data? Maybe I am blind but I don't see it?
I think I did that when I did the factory reset. When I do boot up however, my original unlock pattern is still set...so I don't know wtf is going on.
FIXED!!
I used Kies Registry Patcher v.1.6.0.0
then reset user data and cache WORKS GREAT AND I HAVE FROYO NOW!!

[Q] Please Help. 3 Day old SGS behaving very strangely

Hello everybody.
I am having serious trouble with my phone and I was hoping some of you might be able to help me out.
I just bought my SGS 3 days ago. It came with android 2.1.1 eclair installed.
I had read that that version was not the best ( the first thing I saw when I opened the phone actually was an error screen, and the lag was horrible) so when I got home I decided to try and upgrade it using the official software for it (Kies).
Unfortunately Kies would simply disconnect my phone when I told it to upgrade, after which it would ask me to upgrade again >.>
So I decided to use Odin to flash one of the newer 2.2.1 versions.
I flashed a 'JS3' version with a repartition to 803 pit , but it crashed after rebooting with the dbdata error (which as I learned later was caused by not flashing a full firmware).
I flashed JPU after which worked great. It was fast and responsive.
However my phone kept crashing. Whether on standby, using apps, or just trying to dial a number, it would freeze, start vibrating, and sometime reset, other times just stay frozen until I force shut down it from the power button.
I flashed JS5 afterwards, with full cache clearing, factory reset etc. Still crashed.
Then I tried flashing Darky's 9.2 Ressurection. Loved it but I couldn't even set up my google account because it crashed constantly.
Then I went back to what I believe is the current official version for my location and carrier (Vodafone Romania), JP9 .
After flashing it didn't crash, but after a while (one night), it started crashing like crazy, even wound up with weird gray lines and a freeze in the morning.
I was hoping someone here might know what is wrong with it. I already sent it back to be serviced but I am thinking maybe I broke it somehow and would like to know how so I don't do it again.
The phone is network locked, which I later learned is usually a bad thing for flashing, unfortunately I didn't know about that when I started.
well first of you want to remove the network lock so try these:
http://forum.xda-developers.com/showthread.php?t=761045
http://forum.xda-developers.com/showthread.php?t=913681
next step is to register on www.samfirmware.com (its free) and here is where you will get all the latest official firmwares from samsung..
what you want to do is download (XWJS5) with all 3 files and PIT and flash that through odin with RE-PARTITION..
Before you do that, put your phone into recovery mode (volume up + Home button + Power button ) and do a factory reset / wipe cache ect...
so when you have done that and flashed the new firmware. let me know what the outcome is..
another thing.. ALWAYS MAKE SURE KIES IS CLOSED.... EVEN IN THE ICON TRAY... AND MAKE SURE DRIVERS ARE UP TO DATE.
other than that you shouldn't have any problems
hi, thanks for the advice.
I already did most of that however. I did a factory reset numerous times, and I also did a full repartition flash more than once, to no avail.
I am waiting to get it back from warranty service now but I am wondering what went wrong.
Was it broken when I bought it or did I damage it somehow by trying to flash it while network locked ?
flashing with network lock wouldnt make everything force close. the worst thing that could happen when flashing with network lock is not picking up a signal and possible IMEI corruption.
i think you may have just flashed the wrong ROM, it happens to us all, but the more you do it the more experienced you become and you soon learn methods to restore things..
dont worry too much it will be fine when it comes back from samsung, just be sure to read up properly if you have any doubts.. or ask a question first you will get a reply quicker than you can Unbrick your phone..
My phone seems to hate the 803 pit file. Lots of force closes when I used it. Try using 512, see if that works any better.

[Q] Galaxy S i9000 won't factory reset and force closes frequently - now with logcat

Hello all,
please forgive me first of all because I've had very little sleep due to this issue. And its a long thread, but more detail is better generally I believe.
First, some background, and unfortunately, it starts with my wifes phone.
My wife has a Galaxy S GT-i9000 on Orange in the UK. She has had it, probably about a year maybe at most. She has a few apps that she has downloaded but nothing major and on first looks when I got it nothing I expect would cause this issue, just facebook etc.
My wife came home and said, my phone keeps coming up with a message saying force close. Ahh, I thought, some apps gone nuts, but alas, it appeared to be many apps including Maps, Google Upload (I assume this is a system process), Facebook Katana and many more, probably about 20 Force Close messages pop up one after the other and it lags whilst trying.
Odd, I thought, I also noticed the icon for one of the apps on her homescreen had changed to the default White and Green one with the android on it.
I suspected something had gone wrong (obviously), I asked if she had rebooted it and she said she had. So, I rebooted it again, just incase. Same problem.
I then thought it might need an update, it was running official Kies 2.3.3 (or was it 2.3.4, I forget) so I plugged it into my netbook and ran Kies, had to update that as it didn't have the latest application update. I then started the firmware update, after backing up the phone using Kies.
Halfway through the update, Kies popped up a message saying something went wrong and that I had to unplug the phone, take out the battery and reboot. Odd, I thought as the phone was telling me to not doing anything. I waited a minute, nothing further happened, so I did this. Then I got the Black Screen of Death with the phone, the dots and the computer screen.
Crap!!! I thought, I managed to get into Download mode, and reflash it using what I believe was an official ROM using Odin. I then rebooted, and found that it STILL had the data on it and it STILL was doing the force close. At least I had it back to "working" though so I was mildly happy.
I then did a factory reset using the menu system, erased the USB storage (there is no external SD card in her phone) and rebooted, still force closing but prompting me to setup again. Weird. I went through the setup slowly, as every second or so a force close would popup, then when I completed the setup (which still had the wifi settings, account settings etc in it) the System Setup crashed with Force Close. I then rebooted and got to the Home Screen, but still crashing.
I rebooted and used the recovery screen to clear the cache and factory reset, despite the warnings I will lose everything, nothing was wiped.
I tried to update using Kies again but it tells me that the firmware/device is not supported. I am now trying to see if I can use Odin to install a Kies supported firmware. So that I can then try an update using that again.
Anyone got any suggestions, at present, my thoughts are, I was going well within the realms of warranty up until I reflashed it using Odin to try and get back in as I'd only used Kies to update and the issue "just started happening" without my missus doing anything.
There are no signs of damage on the phone and she tells me it was just sat on her desk all day.
So, my question is, what now? I'm of the opinion based on the above that if I can't reflash a warranty supported Kies update, then maybe a custom ROM will be worth a shot to see if its a hardware failure or if its software. I just have never had an issue like this with my HTC Desire and I've ran many custom ROMs and standard ROMs on it.
I do have the .tmp file of the update Kies downloaded, and I also have a Binary folder which has some file inside a couple more folders but its not a .tar or a .zip because when I try renaming it (after a copy) it won't open.
So, suggestions on a postcard, thanks if you got this far through this nightmare. All help massively appreciated.
Edit: it appears to be the same issue as this: http://forum.xda-developers.com/showthread.php?t=822238
I'll try some of their suggestions. Today I also did the *2767*3855# today which I found after a bit more searching. Same problem after a reboot. Force close and data still there.
I've tried and tried again to do various solutions for this, I've even ran a logcat using adb to see if I can see the problem. I suspect its a Dalvik Cache issue in that its unable to write to it for some weird reason.
I've downgraded it to Froyo following this guide: http://forum.xda-developers.com/showthread.php?t=1100906
It now detects in Kies and offers me a firmware upgrade. I suspect it will die again though if I try due to this Dalvik problem.
Wiping cache does not wipe the cache. Everything still appears to be there on reboot as mentioned above.
Here is a copy of the LogCat with Java errors all over it: http://leenukes.co.uk/downloads/logcat1.txt (its quite long)
I guess nobody knows. Today I will speak to Orange to try and get it fixed or replaced.
Sent from my HTC Desire using Tapatalk
We've been told it is beyond repair. We will see what they say when we go back into the shop. Its still in warranty so I don't see why they won't replace it.
Sent from my Galaxy Nexus using Tapatalk
I have a friend with a Galaxy S from Orange Romania and suddenly the phone kept showing Force Close on every App. He had 2.2.1 if I remember right. He whent with the phone to an Orange Shop and they only do a factory reset but data was not wiped.
So what i have done for him:
- start the phone in Download Mode
- start Odin with repartition check and XXJVT (2.3.5) firmware with 3 files (code, phone and CSC) + pit file .512
- after reflashing the phone does have all tha data, so i resarted in Recovery Mode and done a Factory Reset and a Cache Wipe
- i flashed Speedmonde Kernel k16.10 and do again from Recovery Mode a Factory Reset, Cache Wipe and Davlick Wipe.
On reboot the phone was CLEAN. No force closes for a week now.
Sorry for my English hope it helps!
ZiDanRO said:
I have a friend with a Galaxy S from Orange Romania and suddenly the phone kept showing Force Close on every App. He had 2.2.1 if I remember right. He whent with the phone to an Orange Shop and they only do a factory reset but data was not wiped.
So what i have done for him:
- start the phone in Download Mode
- start Odin with repartition check and XXJVT (2.3.5) firmware with 3 files (code, phone and CSC) + pit file .512
- after reflashing the phone does have all tha data, so i resarted in Recovery Mode and done a Factory Reset and a Cache Wipe
- i flashed Speedmonde Kernel k16.10 and do again from Recovery Mode a Factory Reset, Cache Wipe and Davlick Wipe.
On reboot the phone was CLEAN. No force closes for a week now.
Sorry for my English hope it helps!
Click to expand...
Click to collapse
Sound advice there mate, other thing I would have done is in recovery mode before the ODIN flash I would have format sdcard, making sure you have removed BOTH the external sd and the sim card, as it can wipe them as well.Then flash through ODIN as per instructions above.
Using JVT I would flash either speedmod or semaphore 2.1.1 which I personally use.
Happy flashing!!
turns out it was water damage and some parts corroded.
Its going to be claimed for on insurance.
Sent from my Galaxy Nexus using Tapatalk
Hello all,
the phone came back from repair yesterday, yay!
the phone now however, doesn't appear to lock onto a mobile signal for very long. Boooo!!!
After sending off for repair using insurance, we got the phone back yesterday but it now appears to be broke in another way. It won't lock on to a mobile signal, wireless is fine but data network and sometimes just mobile signal is patchy and keeps dropping.
I've just reset it to factory defaults, same problem. What I did notice, which is odd is that since it came back from repair, its now unlocked and I can put another networks SIM card in it, same issue there too so I know its the phone now.
I'm going to scour the forums to see if anyone else had/has issues like this, it is running the latest firmware now and a full wipe really did fully wipe it this time, as opposed to last time with its issues due to water damage. One step forward, two steps back?
Its going back to the insurance company. Especially as Orange were suggesting that we pay £70 for a new handset.
Absolute fool I had on support today, yesterday I at least had someone sensible.
Sent from my Galaxy Nexus using Tapatalk
SGS force close problem
Hey guys i m facing a similar solution in my samsung galaxy s. After deleting all the contents and uninstalling the applications, I m getting them back after rebooting and all applications has to be force closed after rebooting.
Please help me to solve this problem
Signal issues
leenukes said:
Hello all,
the phone came back from repair yesterday, yay!
the phone now however, doesn't appear to lock onto a mobile signal for very long. Boooo!!!
After sending off for repair using insurance, we got the phone back yesterday but it now appears to be broke in another way. It won't lock on to a mobile signal, wireless is fine but data network and sometimes just mobile signal is patchy and keeps dropping.
I've just reset it to factory defaults, same problem. What I did notice, which is odd is that since it came back from repair, its now unlocked and I can put another networks SIM card in it, same issue there too so I know its the phone now.
I'm going to scour the forums to see if anyone else had/has issues like this, it is running the latest firmware now and a full wipe really did fully wipe it this time, as opposed to last time with its issues due to water damage. One step forward, two steps back?
Click to expand...
Click to collapse
Sounds like a modem issue, where the techs at Orange put in the wrong modem for your firmware. I did the same thing when I upgraded from Froyo to Gingerbread.
Alternately, it could be a broken external antenna connection as a result of the corrosion from the water damage. Google "no signal fix" and look for a site that ends in .uk
Just a thought for others who come across this problem.
I

Internet Connection Unstable (WiFi) Since Recent OTA Update

My phone is a T-Mobile branded HTC One M7 with Android 5.0.2. A few days ago, I received an OTA Android update and since then, WiFi has been unusable.
When WiFi is turned on, the phone sees and connects to the WiFi access point, but a error message pops up, "Internet Connection Unstable" with the SSID of the access point displayed below.
I contacted HTC support and was advised to wipe the cache partition. This did not work, and the next bit of advice was to do a factory reset on the phone. I'd like to avoid that if possible... has anyone else encountered this issue?
Thanks.
Earl
UPDATE: this turned out to be not a problem with the phone. I found a rogue DHCP server on the network that was causing the instability.
they might be right, a full reset is quite useful after a ota update (for HTC phones). After upgrading to lollipop I did have a couple of bugs (tho none as major as the one you're describing) and I had to do a factory reset to get everything working flawlessly.
And after trying to upgrade from stock 7.19.401.102 to 7.19.401.121 my m7 stopped working altogether, it got stuck in a bootloop at HTC's logo. I had to flash a nandroid backup I made when I was on KitKat and then upgrade to 7.19.401.102 lollipop, do a full reset, upgrade to 7.19.401.121, and then another reset. That fixed everything for me (maybe the factory resets weren't necessary in that case tho). But I no longer care about htc's stock roms to go through such trouble again.
HTC's ota update seem to have lots of bells and whistle (and annoyances) going about them, which is why I'm on 6.0.1 crdroid ROM.
try clearing the settings app data (from settings>apps) or the WiFi app data. There's no guarantee it'll work but it's better than having to do a full reset.

LG G4 Loses Network After Root and ROM Installation

I recently rooted my H811 G4 (T-mobile) and then installed the latest Imperium ROM on it. Everything worked fine for three days. The only thing that kept popping up was an alert from Lookout, saying that the Imperium Settings app had riskware and wanted me to delete it. I just ignored the warning as I figured that it was being fussy over an app from a custom ROM. I also kept getting notifications to upgrade my version of Android but I ignored those too as I learned that with a rooted phone, it either won't work, or will unroot the phone. After 3 days, I suddenly lost connectivity to the T-Mobile network. Could still make calls and text over wifi, but nothing when the wifi was off. After going into the settings, it would say that the network was disconnected. I took the phone to T-mobile and they tested the sim card in another phone, to which it worked just fine. So that told me that something was obviously wrong with my handset. I restored the phone back to factory default and was able to make calls again. Imperium was still installed on it. So I went back into recovery and wiped the phone clean. After selecting to restart the phone in TWRP, I got stuck on the bootloader screen. So I downloaded LG Bridge and got it working again. I was going to wait till I got a notification to upgrade Android before rooting it again, but after 2 days, I never got it. Has anyone else had this happen? I thought Imperium was cool but I'm not thinking of just going with another custom ROM.
Musicman82121 said:
I recently rooted my H811 G4 (T-mobile) and then installed the latest Imperium ROM on it. Everything worked fine for three days. The only thing that kept popping up was an alert from Lookout, saying that the Imperium Settings app had riskware and wanted me to delete it. I just ignored the warning as I figured that it was being fussy over an app from a custom ROM. I also kept getting notifications to upgrade my version of Android but I ignored those too as I learned that with a rooted phone, it either won't work, or will unroot the phone. After 3 days, I suddenly lost connectivity to the T-Mobile network. Could still make calls and text over wifi, but nothing when the wifi was off. After going into the settings, it would say that the network was disconnected. I took the phone to T-mobile and they tested the sim card in another phone, to which it worked just fine. So that told me that something was obviously wrong with my handset. I restored the phone back to factory default and was able to make calls again. Imperium was still installed on it. So I went back into recovery and wiped the phone clean. After selecting to restart the phone in TWRP, I got stuck on the bootloader screen. So I downloaded LG Bridge and got it working again. I was going to wait till I got a notification to upgrade Android before rooting it again, but after 2 days, I never got it. Has anyone else had this happen? I thought Imperium was cool but I'm not thinking of just going with another custom ROM.
Click to expand...
Click to collapse
Modem problem. Don't waste your time. Oreo is the latest build for TM-LGG4:
https://forum.xda-developers.com/g4/development/rom-lineageos-15-1-t3806629
Need TWRP to flash.

Categories

Resources