Good afternoon -
Hopefully a quick question. I've been unable to find a clear and concise answer to this question so far.
TL;DR version: When Trying to flash stock firmwares, ODIN starts the flash but hangs on system.img.ext4 install. No error, just hang. Eventually I killed and tried again a few times (with different rom files too), same result. Left flash running overnight, same result. Was able to flash TWRP without issue. Please help! Not sure what I'm doing wrong here.
Detailed version:
I wanted to put Android 6.0 or 6.0.1 on my Sprint Galaxy S5 (SM-G900P). Previously I was running BOG1 I believe (Can't remember for sure) It was rooted so I couldn't use install via OTA Update. I made a backup of my previous rom So /hopefully/ I can go back if necessary. Here's the issue right now:
I downloaded the ...PCA Build from here: galaxys5update.com/galaxy-s5-stock-firmware.
Then wiped dalvik and regular cache, then put phone in download mode, and ran ODIN 3.XX.X (I tried a number of versions, 3.10.something, 3.07.something, 3.11.something (sorry for the lack of complete info, not in front of that computer right now so I don't have the exact details).
I loaded the Tar.md5 file into the proper spot in ODIN, then start the install. It starts running, I can see the progress in the information window. Then it gets to "system.img.ext4" and appears to freeze. I've let it go for 20-30 mins before disconnecting. I tried a different rom file and same result, ODIN just hangs. No error, just a hang. I left it running a flash overnight and it was still stuck at system.img.ext4 when I woke up this morning.
I was able to successfully flash TWRP but that's not really the solution.
Any help you might have would be greatly appreciated.
Thanks,
C
Update: I flashed a nandroid backup from right before I started all this. It installed fine. I'm back to my Android 5.0. However, WIFI has stopped working, and the phone stops responding a little bit after the screen turns off, requiring a battery pull and reboot. Additionally, making or accepting calls causes a reboot.
Another update: Tried KIES to install new Firmware through normal update method, it starts but then hangs at 3%.
So any help you might have would be really appreciated!
same problem
I have the same problem. Did you ever find a solution to the system hang on that file problem???
cjs678 said:
Good afternoon -
Hopefully a quick question. I've been unable to find a clear and concise answer to this question so far.
TL;DR version: When Trying to flash stock firmwares, ODIN starts the flash but hangs on system.img.ext4 install. No error, just hang. Eventually I killed and tried again a few times (with different rom files too), same result. Left flash running overnight, same result. Was able to flash TWRP without issue. Please help! Not sure what I'm doing wrong here.
Detailed version:
I wanted to put Android 6.0 or 6.0.1 on my Sprint Galaxy S5 (SM-G900P). Previously I was running BOG1 I believe (Can't remember for sure) It was rooted so I couldn't use install via OTA Update. I made a backup of my previous rom So /hopefully/ I can go back if necessary. Here's the issue right now:
I downloaded the ...PCA Build from here: galaxys5update.com/galaxy-s5-stock-firmware.
Then wiped dalvik and regular cache, then put phone in download mode, and ran ODIN 3.XX.X (I tried a number of versions, 3.10.something, 3.07.something, 3.11.something (sorry for the lack of complete info, not in front of that computer right now so I don't have the exact details).
I loaded the Tar.md5 file into the proper spot in ODIN, then start the install. It starts running, I can see the progress in the information window. Then it gets to "system.img.ext4" and appears to freeze. I've let it go for 20-30 mins before disconnecting. I tried a different rom file and same result, ODIN just hangs. No error, just a hang. I left it running a flash overnight and it was still stuck at system.img.ext4 when I woke up this morning.
I was able to successfully flash TWRP but that's not really the solution.
Any help you might have would be greatly appreciated.
Thanks,
C
Click to expand...
Click to collapse
I don't know if I have ever gotten that error before. You can try to update your samsung drivers on your computer, and make sure you are using the cable your phone came with. It sounds silly, but I have had issues with ODIN if I am not using the original cable.
Related
Hi everyone I just recently purchased a used S4 the GT-i9500. Everything seemed fine until I got home. It detected my T-Mobile Sim fine but I could only access 2G data and could not connect to any WiFi network I came across. The rom was stock 4.2.2 and the phone was rooted pre purchase. So after fiddling around for a few minutes I discovered the previous owner had flashed TWRP v2.4.1.0 as his choice for a Custom Recovery. Now at this point I had decided to flash on a Custom Rom and of course I first made a backup before flashing on WanamLite. Now after attempting to flash it I immediately received a failure. I tried turning off the signature verification and it did not flash. Now in my frustration i attempted to wipe everything and tried flashing Omega Rom v14. Now i was able to go through with the installation and choose what I wished to install and when I pressed Install things went along smoothly until I hit the app SecSafetyAssurance.apk where it freezes. This is a bump that I've run into at least 5 times already. I changed certain options I wanted to install and eventually made it past this and I am prompted to reboot. Now when I do this to my dismay I just receive a black screen. Upon pulling out the battery and attempting to reboot I still receive a black screen. when I boot back into the Recovery and attempt to reboot the system from within TWRP it warns me saying No OS Installed Are you sure you want to reboot. Im at a loss of what to do. I have read about other members suggesting to use ODIN but I am very confused about how to access Download Mode in order to flash a stock rom from SamMobile.com. I could use a few tips or maybe a few options that I'm left with in order to obtain the operation of my phone again. I would like to get my phone back and Im sure some users can relate to how Im feeling so any help at all would be greatly appreciated. Thank you very much in advanced!
JmastahJay56 said:
Hi everyone I just recently purchased a used S4 the GT-i9500. Everything seemed fine until I got home. It detected my T-Mobile Sim fine but I could only access 2G data and could not connect to any WiFi network I came across. The rom was stock 4.2.2 and the phone was rooted pre purchase. So after fiddling around for a few minutes I discovered the previous owner had flashed TWRP v2.4.1.0 as his choice for a Custom Recovery. Now at this point I had decided to flash on a Custom Rom and of course I first made a backup before flashing on WanamLite. Now after attempting to flash it I immediately received a failure. I tried turning off the signature verification and it did not flash. Now in my frustration i attempted to wipe everything and tried flashing Omega Rom v14. Now i was able to go through with the installation and choose what I wished to install and when I pressed Install things went along smoothly until I hit the app SecSafetyAssurance.apk where it freezes. This is a bump that I've run into at least 5 times already. I changed certain options I wanted to install and eventually made it past this and I am prompted to reboot. Now when I do this to my dismay I just receive a black screen. Upon pulling out the battery and attempting to reboot I still receive a black screen. when I boot back into the Recovery and attempt to reboot the system from within TWRP it warns me saying No OS Installed Are you sure you want to reboot. Im at a loss of what to do. I have read about other members suggesting to use ODIN but I am very confused about how to access Download Mode in order to flash a stock rom from SamMobile.com. I could use a few tips or maybe a few options that I'm left with in order to obtain the operation of my phone again. I would like to get my phone back and Im sure some users can relate to how Im feeling so any help at all would be greatly appreciated. Thank you very much in advanced!
Click to expand...
Click to collapse
Well first thing is get the latest stock firmware for your variant from my sign and get odin 3.07
For download mode power off phone unplug,, press volume down home and power all together till something pops up and release then press volume up and connect to pc
Open odin click pda and select that firmware u downloaded start the process
For more info check my sign help thread link it has more options on the same
.
JmastahJay56 said:
Hi everyone I just recently purchased a used S4 the GT-i9500. Everything seemed fine until I got home. It detected my T-Mobile Sim fine but I could only access 2G data and could not connect to any WiFi network I came across. The rom was stock 4.2.2 and the phone was rooted pre purchase. So after fiddling around for a few minutes I discovered the previous owner had flashed TWRP v2.4.1.0 as his choice for a Custom Recovery. Now at this point I had decided to flash on a Custom Rom and of course I first made a backup before flashing on WanamLite. Now after attempting to flash it I immediately received a failure. I tried turning off the signature verification and it did not flash. Now in my frustration i attempted to wipe everything and tried flashing Omega Rom v14. Now i was able to go through with the installation and choose what I wished to install and when I pressed Install things went along smoothly until I hit the app SecSafetyAssurance.apk where it freezes. This is a bump that I've run into at least 5 times already. I changed certain options I wanted to install and eventually made it past this and I am prompted to reboot. Now when I do this to my dismay I just receive a black screen. Upon pulling out the battery and attempting to reboot I still receive a black screen. when I boot back into the Recovery and attempt to reboot the system from within TWRP it warns me saying No OS Installed Are you sure you want to reboot. Im at a loss of what to do. I have read about other members suggesting to use ODIN but I am very confused about how to access Download Mode in order to flash a stock rom from SamMobile.com. I could use a few tips or maybe a few options that I'm left with in order to obtain the operation of my phone again. I would like to get my phone back and Im sure some users can relate to how Im feeling so any help at all would be greatly appreciated. Thank you very much in advanced!
Click to expand...
Click to collapse
Flashing through odin is one option.... some users have reported that there were some hiccups when installing omega 14 because of the aroma script.....try a different rom...there are many others to choose from....or you could flash stock via odin as said on the earlier comment good luck
Feedback
Today I attempted to use ODIN to flash now I am still currently attempting this. When I press the volume down key, power, and home button it takes me to the custom recovery TWRP instead of download mode. The phone did this when I first purchased it. When I still had what appeared to be the stock rom it would always take me to the recovery. When I would use the volume up instead of down it would take me to the factory test mode now mind you this happened when the OS was still installed. When i try that combination now i just receive a blank black screen. Are there any other ways to boot into download mode?
ATT Galaxy S4 currently running Goldeneye 6.0 and TWRP 2.6.0.0 (never installed MF3 base, but have tried both MF3 and MDL modems)
First odd thing...
[About->Status->Device Status] is listed as "Sd card" instead of the more common "Official" or "Custom".
Anybody know what that means or is telling me?
This is the latest thing I've noticed with my phone, which has been having all sorts of issues lately that I cannot seem to figure out. My main problem is, I can reinstall a new ROM, boot into the ROM, change settings around, reboot just fine, but, as soon as I install anything from the Play Store, the next reboot will hang on the initial Samsung splash screen. Wiping is the only fix I've found, and fixing permissions in TWRP errors out with an error that it cannot chown one of the new/updated .apk files.
Both Goldeneye 5 and 6 are doing this now (5.0 was installed and rock solid for several weeks before this all showed up...it started sometime after I decided to try out a couple of the aroma roms and then came back to GE).
Used ODIN to go back to factory rom, re-rooted/installed TWRP, then reinstalled GE6.0, but the same thing happened. Everything looked good until I ran updates from the store, then I was stuck again (note: used Root Explorer to check to permissions on the updated apks before rebooting and they were all correct (755)).
Other things I've noticed are:
1. Sometimes, on any reboot, the startup locks at the initial Samsung screen and I have to long press the power button to get it to reboot. It usually boots the second time around (this is before I install any additional apps and am completely unable to reboot).
2. Sometimes when wiping cache, davlik, and/or data, TWRP will seem to hang for up to a minute when trying to initialize the partition. A couple of times it even hard reboot my phone when I did a cache+davlik wipe.
3. I rolled back to a recovery image just fine; however, it was a couple months old. Everything started off looking great, but once I updated to a new ROM, my issues returned.
Trying Heimdall to go back to factory; however, I'm having issue with my laptop and getting the Zadig drivers installed. While I'm working that out, figured I'd see if anyone else has any suggestions on what else I should be trying or looking out.
thx
I would flash your phone back to MDL stock with odin using the mdl tar. This should format your paritions correctly. You could also reinstall MDL using kies since they still don't support MF3.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Hi
I reflashed my S5 with a stock rom to remove all the Carrier blocks and extras. After the flash the device booted up and instantly came up with the error saying acore has stopped working and then around around 5-10 seconds the phone reboots and does it again. What can I do?
Thanks
Wildey1771 said:
Hi
I reflashed my S5 with a stock rom to remove all the Carrier blocks and extras. After the flash the device booted up and instantly came up with the error saying acore has stopped working and then around around 5-10 seconds the phone reboots and does it again. What can I do?
Thanks
Click to expand...
Click to collapse
Data factory reset in recovery.
Wildey1771 said:
I reflashed my S5 with a stock rom to remove all the Carrier blocks and extras. After the flash the device booted up and instantly came up with the error saying acore has stopped working and then around around 5-10 seconds the phone reboots and does it again. What can I do?
Click to expand...
Click to collapse
It's hard to answer since you provided no crucial details about your phone, configuration or how you flashed it.
You didn't tell us which S5 model you have or your carrier. Nor what firmware file you flashed, so we don't know if it was a compatible file. No Odin log, so we don't know if the flash had errors or not. And you didn't describe how you flashed step by step so we don't know if you missed essential steps.
At a guess, try wiping the partition cache from recovery mode. Then if necessary, do a factory data reset as well (will delete user files!). If you have ongoing problems, then you should restore your backup and try again from that stable condition.
No backup? That is a bad habit to say the least. In that case, flash a full stock firmware image that matches the carrier that the phone was originally sold for.
.
fffft said:
It's hard to answer since you provided no crucial details about your phone, configuration or how you flashed it.
You didn't tell us which S5 model you have or your carrier. Nor what firmware file you flashed, so we don't know if it was a compatible file. No Odin log, so we don't know if the flash had errors or not. And you didn't describe how you flashed step by step so we don't know if you missed essential steps.
At a guess, try wiping the partition cache from recovery mode. Then if necessary, do a factory data reset as well (will delete user files!). If you have ongoing problems, then you should restore your backup and try again from that stable condition.
No backup? That is a bad habit to say the least. In that case, flash a full stock firmware image that matches the carrier that the phone was originally sold for.
.
Click to expand...
Click to collapse
The Model is SM G900F. Its On Three Carrier. I Flashed A STOCK (From SamMobile) Firmware 4.2.2.
The Flash Process Was Successful. No Errors.
Put Device In Download Mode
Connected To Computer
Loaded Firmware Into PDA
Ftime reset
Auto Reboot
Started The Flashing.
Completed.
Phone rebooted. Got Acore has stopped. Then the phone reboots.
But since I needed my phone working quickly I took the path of factory reset and that seems to have fixed it. I did try clearing the cache but no effect.
I believe I know the issue. I used a launcher called Themer. I have reasons to think that was causing the issue because as it was loading in the background I managed to quickly hit the continue button to close the crashed process boxes and as the Launcher finished "Loading" it when it rebooted.
WARNING FOR OTHERS. Always Remove Other Launchers Before Flashing As A Precaution! (Warnings From Newbies Hehe)
I have a Samsung Galaxy Tab 4 8” SM-T330NU running 5.1.1. The box tells me the ‘real’ model is SM-T330NYKAXAR. I decided to root the phone, because I want to get to Marshmallow and to get rid of this extra bloat where. (I will mention I have a good amount of experience rooting, including just rooting my Droid Turbo).
Anyway, after a lot of looking around the forums, I decided to use the CF-AutoRoot method (CF-Auto-Root-milletwifiue-milletwifiue-smt330nu) to root. I got Odin and installed it (along with the Samsung drivers) onto my Windows 10 PC; set debugging, on; and ran Odin. I followed the directions and it appeared to root properly; and I got to CWM recovery. Woo hoo! (Or so I thought)
So then after making sure I can get into recovery, I rebooted back into my stock ROM. Unfortunately, I got stuck at the Samsung logo; tried rebooting multiple times; even did a factory reset/wipe (as per instructions I saw on the forum) but to no avail. (Even let it set for over an hour but it never got past the Samsung logo).
After some more reading, I figured I might as well go ahead and flash a new ROM; so I think (if I remember correctly) I tried the JazzROM. It got up to about 69% and then it just quit - screen went black, and then it rebooted back to Odin mode. Obviously it didn’t work; then when I tried to get back into recovery to wipe and try the flash again, I got the message ‘Cannot mount \system - invalid argument’.
Again, after much reading and trying, I was able to get TWRP recovery installed and then wiped/formatted the system partition, which I had read would help get rid of that error. And it did seem to fix it.
So I can re-root with Odin without any issues; I can get to Recovery (either CWM or TWRP depending on which I flash), but no matter what I do, it either gets about 2/3 the way thru the flash process and then reboots back to Odin mode; or (using TWRP) I can get it certain ROMS to flash successfully, but after rebooting it goes right to Odin mode (saying it could not do normal boot). I even tried loading a stock, with the same result.
Which leads me to my first question: Exactly which ‘stock’ file should I be loading? I am having a hard time finding one - either it leads me to a dead end, or the download doesn’t work.
- When in CWM recovery, it shows the following:
At the top:
LMY47X.T330NUUEU1BOI1
Bottom:
#Manual Mode#
— Applying Multi-CSC...
Applied the CSC-code : XAR
Successfully applied multi-CSC.
Are these correct?
- When TWRP is installed (3.0.0-3) it starts by asking me about the ‘Unmodified System Partition’ and whether it should be kept read-only or allow modifications. I assume allow mods? Otherwise I don’t see how you could apply a new ROM? (I haven’t seen this in a while, not in my install of TWRP to the Droid Turbo). So just want to make sure I am selecting the right option.
- I am also concerned about whether I am using the right packages for this tablet. Based upon what I see on the box and sticker (which I still have) this should use the stock ROM LMY47K.T330NUUEU1BOI1 model; but I’ve also seen things referring to a BOG1 model? Mine is the T330NU English and (I assume) US model since I am in the US.
Any ideas as to what is going on? If I can at least get back to stock I could then start from scratch with the appropriate info; or just install one of the new ROMS (I’ve tried Jazz, Dirty Unicorns, UltraStock). I don’t think I am ‘bricked’ because if so I wouldn’t be able to get to Odin or recovery. Any help appreciated here. Thanks!
-Tom (Chimp)
NM, finally got it working, running DU and running fantastically, if I may say so. Getting TWRP to install finally fixed everything.
Sent from my SM-T530 using XDA-Developers mobile app
Hey everybody, I need help. I have a J320P that is stuck in a boot loop, when it was found like this by my friend they came to me and asked if I could help. I have no information on how this happened other than they took a shower and when they came back it was like this. I have tried installing stock firmware 3 times to no luck. I might have an sd card somewhere with the backup for this phone but finding it would take some time so in the mean time I am turning to the forums. If anyone could help that would be amazing. I will provide more information and answer questions as they come.
Steps I have taken:
1. dirty flash of stock latest firmware
1. wiping the phone completely
2. Installing latest stock firmware
3. Still bootlooped
Not solved
So after triple wiping through TWRP and installing the stock firmware again it was still looping so i left to run to the store quickly and when I returned I tried powering it on and it loaded normally and I am still setting it back up.
Leaving the original comment. After coming home from work my friend said it had started doing it again, and it is. This time there was no root and no system anything messed with, does this mean there is a hardware problem?