heyo - I have a G930w8 Samsung S7 (Exynos.) I don't know what CSC the phone has. It was just sold new-in-box on Ebay as an unlocked Canadian Samsung S7. I'm using it in the US.
I've had it for a while. While attempting to update today, the phone, well... didn't update. It was stuck updating for a day. Could not get into recovery menu, but Odin/downloading mode worked.
I used Odin to flash this stock firmware: sammobile. com/samsung/galaxy-s7/firmware/SM-G930W8/XAC/download/G930W8VLS6CSH1/288555/ to the phone, using the CSC file (not HOME_CSC.) It worked. I did not flash the userdata and didn't use PIT as neither are included in the sammobile package. I didn't use re-partition, because whenever I try that, Odin (3.13.1) fails to flash with "Can't open the specified file, line 1892"
So, post-flashing, the phone boots to a "Erasing" screen, then to an "installing system updates..." screen, stops at 32%, then goes back to "Erasing". After a while on "Erasing", the Android logo freezes. I left it in this state for 30 minutes and nothing happened - I now plan to leave it there overnight, but in the meantime:
- if I force restart the phone, once it reboots it tries "Erasing" for a moment, then goes into a permanent "No Command" boot loop.
- If I re-flash the firmware, it goes back to the previously described "Erasing > Installing System Updates 32% > Erasing > Frozen logo on Erasing" state.
- If I go to the recovery menu, the phone usually randomly freezes or reboots. A couple times I successfully selected the factory reset option, at which point the phone would print "formatting /data...". It remained in this state for 30 minutes with no change, so I am not sure if it's freezing or actually doing something. I intend to also try leaving this overnight.
Can anyone help me get this phone functioning again? I am not sure what's going wrong here, if I have installed the wrong firmware, if I have installed the wrong CSC, do I need to use a PIT file, etc.
Edit: The phone is working again. For posterity, here is what I did:
- left it overnight at the "erasing" screen. It was still there when I woke up.
- went into recovery, tried a factory reset. It almost instantly went through. Rebooted the phone from recovery menu.
- phone now did "Erasing" for a moment, then, reboot > glowing samsung logo > setup screen > rebooted (with no prompting) into bootloop while I was setting up
- re-flashed the firmware, removed SD card
- now it does "Installing updates > 32% > erasing" except it doesn't freeze on erasing this time, it completes "Erasing" and reboots
- phone now boots normally
- encountered a crash/boot into bootloop after setting up the phone, but re-flashing (this time with HOME_CSC) fixed it
And I'm currently in the phone, able to use it... hopefully no more bootloops. What a cluster****.
Edit 2: I kept getting unprompted reboots into boot loops after 5-10 minutes of using the phone (after flashing.) Re-flashing with HOME_CSC would un-bootloop it, but I decided to let it boot loop for 30 minutes to see what would happen. It eventually stopped boot looping and stayed on the Samsung logo, not booting into recovery or anything. I turned off the phone (power + volumedown) and started it up and it booted just fine. Phone now doesn't appear to be bootlooping randomly.
Edit to the edit of the edit - actual solution: The phone still randomly rebooted every now and then, although no bootloop. I ended up installing TWRP through Odin and hard-wiping the phone ("Format Data".) A normal wipe did not work. I then finally re-flashed the stock ROM and now the phone has been working perfectly for hours.
Here's to hoping future Android updates don't prompt two days of attempts to un**** the phone!
Related
Battery was getting tired, so I ordered a replacement -- and installed it yesterday afternoon..
The phone worked normally -- until this morning.
I noticed a notification from my text app that it couldn't connect and that I should check my settings.
I went to settings and began by refreshing the PRL. During that process the phone froze and then went dead.
Totally dead.
So, I opened it up again to check the battery terminal connection -- and I believe it WAS loose -- so I reconnected it and checked it. Phone goes on!
But it only goes to the splash screen and then repeats. No boot animation.
It will go to the bootloader, but not boot the system nor recovery from there.
Using the fastboot commands, I re-flashed bootloader, radio, boot, system, (From 5.1 stock image) TWRP recovery and erased the cache.
Still stuck at the Google splash screen.
Anyone care to point me in a better direction?
Must be expiration time for Nexus 5 batteries from the initial run. I had to replace mine today as well. Try reflashing the cache and not erasing it after. I made that mistake a month or so ago and kept bootlooping.
Hello guys!
I am encountering an issue with my Samsung Galaxy S6 G920I. The phone suddenly started to restart on its own every 30 seconds or so. After some restarts the phone started to get completely stuck in a randomly time matter, and the only way to take it out of there is by doing a hard reset (volume down + power buttons).
I tried everything. Did wipe cache and factory reset in recovery mode, flashed a new stock ROM with Odin several times but it is still doing that.
The stuck issue also happens on screens like "installing update" or "erasing", after doing the ROM flash with Odin.
Any thoughts?
richardcr23 said:
Hello guys!
I am encountering an issue with my Samsung Galaxy S6 G920I. The phone suddenly started to restart on its own every 30 seconds or so. After some restarts the phone started to get completely stuck in a randomly time matter, and the only way to take it out of there is by doing a hard reset (volume down + power buttons).
I tried everything. Did wipe cache and factory reset in recovery mode, flashed a new stock ROM with Odin several times but it is still doing that.
The stuck issue also happens on screens like "installing update" or "erasing", after doing the ROM flash with Odin.
Any thoughts?
Click to expand...
Click to collapse
Try device initialization using SamsungSmart Switch. it Should solve the problem. But that method wipes entire internal storage. So backup before you do anything,
Device initialization is something like resetting it to factory setting by clean install of the firmware.
Hi, could you fix it ? The exact same thing happened to me. I was using stock firmware (I never rooted it or anything) and it suddenly began to reboot by itself. It can be stuck in a bootloop for 2 straight days and then suddenly boot normally and use it for a couple hours until it starts bootlooping again. After a month of having this issues I decided to flash stock 7.0 firmware with ODIN and also with Smart Switch but after succesfully applying the update the phone reboots with the "installing system update" screen and then it gets to 32% and it says "erasing" after which it starts the bootloop once again. I'm stuck with a $500 paperweight. I'm afraid it could be something with the motherboard any help is greatly appreciated!
maxaditya said:
Try device initialization using SamsungSmart Switch. it Should solve the problem. But that method wipes entire internal storage. So backup before you do anything,
Device initialization is something like resetting it to factory setting by clean install of the firmware.
Click to expand...
Click to collapse
HI! I just tried but it keeps doing the same thing
Team vievwer
cacha21 said:
hi, could you fix it ? The exact same thing happened to me. I was using stock firmware (i never rooted it or anything) and it suddenly began to reboot by itself. It can be stuck in a bootloop for 2 straight days and then suddenly boot normally and use it for a couple hours until it starts bootlooping again. After a month of having this issues i decided to flash stock 7.0 firmware with odin and also with smart switch but after succesfully applying the update the phone reboots with the "installing system update" screen and then it gets to 32% and it says "erasing" after which it starts the bootloop once again. I'm stuck with a $500 paperweight. I'm afraid it could be something with the motherboard any help is greatly appreciated!
Click to expand...
Click to collapse
just personal message me
My Samsung Galaxy S6 Edge is not booting even after a factory reset
A mobile app. for Android was installed successfully and since then I’m only having issues with my Samsung mobile:
- Since the installation of both the Hockey & Mobile Banking apps, my mobile freezes during any regular action and after a few seconds the device auto-restarts itself intermittently; this happened during the weekend while in use;
- Sunday night I uninstalled both the Hockey & Mobile Banking apps and the phone continued to freeze and restart intermittently. I was able to boot in SAFE MODE.
- This morning after the phone was turned off and turned on, the phone is not loading; the boot is looping and unable to reach the menu. I’m able to boot in SAFE MODE.
- This morning I did a Factory Reset, when done I get the “welcome” screen and right thereafter, the mobile freezes, auto-restarts and the boot keep looping.
Any help would be highly appreciated.
Hey guys, any suggestions...? I tried last night restoring the OS using Samsung Smart Switch application and the process went just fine the first time and during the setup process the phone just restarted against and for stuck in bootloop again.
I did a second attempt but after the PC is don and the phone boots it gets stuck.
Sometimes after restoring stock firmware and you get a bootloop, you have to boot to stock recovery and factory reset then wipe cache partition.
I know you said you did that once before you posted, you did that before you used SmartSwitch. Have you tried factory reset since restoring with SmartSwitch?
Yes, I did with SS last night; I did it again this morning and after completing the 100% software download, it started updating the device and at 97% it stopped and got the message "FAILED".
now as we speak, I restarted it again and now it's at 66^ downloading the files.
How can I perform a clean install using SS...? or do I need ODIN...? I want to keep the mobile as original as possible.
If you can find your stock firmware, download it and flash it with Odin, it's more reliable.
Maybe a stupid question: Where can I find my stock firmware...?
My info:
PDAIX / CSCI2 / PHONE: PHH (XFA)
I found the Firmware on SAMMOBILE: https://www.sammobile.com/firmwares/galaxy-s6-edge/SM-G925F/XFA/download/G925FXXU4DPIX/108273/
Is this a stock Firmware and reliable source...?
Sammobile is a very reliable source, if that firmware is the newest one for your model number and country/region/carrier then you're good to go.
I did install Firmware corresponding to my phone (PDAIX / CSCI2 / PHONE: PHH (XFA)) using Odin, I can use the phone for like 2 or 3 minutes and then it freezes, restarts and gets into boot loop.
Any more drastic measurements to take...? Is there an online tool to test the hardware function(s)...?
After flashing stock firmware, have you tried booting to stock recovery then do the factory reset and wipe cache then reboot.
Yes, I did...!
In ODIN, do I load only the "AP"...?
In most situations, AP is all you need if the firmware is an all in one firmware file, if you have a 4 part firmware then you need to put each part in its corresponding tab/slot in Odin.
Sometimes you have to flash more than once to be successful.
My phone is running like a horse now...! No more intermittent restarts nor boot looping.
I just did a clean install of Android 7.
The clean install of Android 7 went fine and now it's working back again, was because I changed the "Reactivation Lock" to OFF; I think this helped.
UPDATE: I have finally managed to get my phone working again! Am now currently re-downloading all my apps and transferring all my files back to my phone, running AOSPExtended (https://forum.xda-developers.com/oneplus-one/development/rom-aospextended-rom-t3732194) with OpenGApps. I'll write the steps I took to figure this mess out at the end of this post for anyone who might encounter the same problem in the future. :good:
So last night I left my phone charging overnight from 54% as I was downloading a couple of files (my internet is 1Mbps or 125KB/s). I've done this a couple of times before with no problems what so ever. But this morning I woke up and my phone was in a boot loop. I've tried everything I can think of and everything I could find on these forums, but to no luck. I am at my wits end and I have no clue what to do except to do a full factory reset, which I'd rather not do as its been a while since my last backup and I would lose a lot of precious files...
My Phone: OnePlus One 64GB Sandstone Black, purchased in August 2014.
ROM: cm-13.0-ZNH5Y-20161105-STABLE-Sultan-bacon
Recovery: TWRP+3.0.3-2-TugaPower
Firmware: bacon_firmware_update_2016_1-25_.4.0.1.c7-00011
The boot loop itself is odd, I'll describe them separately here.
-I can boot into fastboot, but not while the USB is plugged into my PC. I have to boot into fastboot, followed by plugging it into my PC. If I try to boot into fastboot while it is plugged in, the screen goes completely black and goes back into the bootloop. However, the phone shows up in Device Manager during the black screen.
- I can boot into Recovery, but the phone automatically reboots and goes back into the bootloop after a few minutes. One thing I have noticed is that if I let it reboot by itself, all the settings reset (including the confirmation to allow modifying of files when you first boot into recovery). But if I manually reboot back into recovery, the settings remain the same; atleast until it reboots automatically again.
Here, I'll list the things that I have tried to no avail:
1. Following this post - https://www.reddit.com/r/oneplus/comments/3izejg/so_youve_just_bricked_your_oneplus/, when I try to wipe Dalvik cache and cache from recovery, the phone goes right back into the bootloop
2. I tried flashing a newer version of TWRP (3.2.1-0 and 3.2.1-K2). After flashing I try to boot into recovery but the TWRP loading screen displays, and then goes right back into the bootloop. It wont even let me into the main menu.
3. I tried flashing a ROM through fastboot (via this post, https://forums.oneplus.net/threads/guide-oneplus-one-flashing-fastboot-recovery.301131/). The phone still remains in a bootloop.
HOWEVER, if I flash my previous recovery (TWRP+3.0.3-2-TugaPower replacing the stock cyanogen recovery from this method), my phone manages to get past the 1+ screen, and goes through my custom power on screen, and reaches the "Android is starting... Optimizing app 1 of 67." But it never gets past app 1, freezes, and then reboots. So now it's stuck in this "extended" bootloop thing.
What I want to know: is there anyway to fix my phone, or will I have to lose all my data and do a full factory reset through the ColorOS method? If anyone has any experience with this or knows a way to help, please don't hesitate!
Thank you in advance.
WHAT WORKED FOR ME:
After following the steps in this post (https://forums.oneplus.net/threads/guide-oneplus-one-flashing-fastboot-recovery.301131/) my phone was booting up, but was kicked back into a boot loop after freezing at the "Android is starting.. Optimizing app 1 of 67" screen. However, the recovery was now the default CyanogenMod recovery. I then re-flashed my previous recovery (TWRP+3.0.3-2-TugaPower) from fast boot, and it was now stable (no more auto-reboots). From there I made a backup off all my files onto my PC before proceeding. After that, I did what this post said (https://www.reddit.com/r/oneplus/comments/3izejg/so_youve_just_bricked_your_oneplus/) and wiped Cache + Dalvik cache. This allowed me to boot all the way past the "Android is starting" screen. However, the phone was still rendered unusable as there were non-stop notifications saying various apps had stopped working. I then booted back into recovery, downloaded and pushed a new ROM and GApps package on to my phone, wiped system, data, cache, dalvik cache, and installed the ROM and GApps pacakge, clearing the cache one more time before rebooting. Everything is working beautifully so far and I could not be happier! I hope this helps anyone else who encounters this problem, Cheers!
Hi all. Hoping someone can finally help me get my Galaxy Tab 2 working again.
A few years ago I decided to root it and install CyanoGenMod. It worked much faster after that and everything was fine. Then one day out of the blue I turned the tablet on and it eventually loaded to the home screen but it was messed up. A few seconds later the Tab 2 reboots itself and this just repeats over and over.
If I go into recovery mode I get the message "installing system update" for less than a second and then it changes to "no command" and eventually a message loads:-
# MANUAL MODE #
-- Appling Multi-CSC ...
Applied the CSC-code : BTU
did not match sized '/system/csc/common/system/csc/others.xml (No Data Available)"
If I try selecting the wipe cache partition option, it will try for a second or two and then shows error and reboots.
If I try the wipe data/factory reset option, it says the data has been wiped but the Android logo in the background changes to say 'error' underneath it. It then powers itself off. Turning it on brings up the boot loop as before with the messed up home screen appearing for a few seconds before it reboots. So it doesn't appear to be wiping any data at all.
Can anyone offer any assistance on how to get this working again please? I would be forever grateful.
PFMC84 said:
Hi all. Hoping someone can finally help me get my Galaxy Tab 2 working again.
A few years ago I decided to root it and install CyanoGenMod. It worked much faster after that and everything was fine. Then one day out of the blue I turned the tablet on and it eventually loaded to the home screen but it was messed up. A few seconds later the Tab 2 reboots itself and this just repeats over and over.
If I go into recovery mode I get the message "installing system update" for less than a second and then it changes to "no command" and eventually a message loads:-
If I try selecting the wipe cache partition option, it will try for a second or two and then shows error and reboots.
If I try the wipe data/factory reset option, it says the data has been wiped but the Android logo in the background changes to say 'error' underneath it. It then powers itself off. Turning it on brings up the boot loop as before with the messed up home screen appearing for a few seconds before it reboots. So it doesn't appear to be wiping any data at all.
Can anyone offer any assistance on how to get this working again please? I would be forever grateful.
Click to expand...
Click to collapse
See the best way to get out of this is to install the stock Samsung firmware using the ODIN tool.
Then if you ever wish to install a custom rom again you can do as you like. Hope this helps. If you are require assistance, feel free to reply to this conversation.
I have tried a few times to flash the stock firmware with ODIN but it would either install the whole thing but it actually didn't work, or the install would crash part way through.
Unless there is some error with the stock firmware I've found online, is there a link to the proper one that I can download from somewhere? Or a specific version of ODIN that is needed for it to work?