Related
I need help reverting to stock..
Here's the short version of the story.. My friend bought her i9195 in Italy, unbranded. She brought it to China.. she encountered the region/SIM lock.
I told her I could probably fix it. So, we rooted her phone, which we confirmed with Root Checker. Then, we tried using RegionLock Away. Didn't work. So I thought the "lock" was in the ROM.. so I wiped it and flashed CWM (during the root) and CM10.2.
The rom worked fine, but the SIM/region lock was still there. I tried to change the CSC with CSC select, but that wouldn't work, even with root. In that state, RegionLock Away returned "unable to find CSC info".. I thought it just needed the Chinese firmware and everything would be okay. On Samsung's website, there is no firmware for China. yippee! (Side note, when I inserted my US T-Mobile SIM, it worked fine.. but with a China Unicomm SIM, it would lock).
So I decided to revert back to the stock rom/firmware/modem.. I went on Samsung's website, downloaded the Italian version (where she bought it), and went into Odin v3.09.
In Odin, I unchecked the F. Reset Time.. I loaded the tar.md5 file in the AP field, and flashed away. I noticed that the KNOX warranty was 0x1.. but, it flashed fine and Passed.. but now the phone is stuck at the boot animation! I left it for an hour, so I know it's not just a slow first boot.
What do I need to fix for it to boot? What did I miss? Please help! Ultimately I would like it to be running the stock rom with the region/sim unlocked.. we don't mind if the warranty is void.
Just flash it again, then boot up in recovery mode, and make a wipe factory reset.
Thank you! That worked. It booted successfully.
Now to try and get rid of that pesky region lock..
I used oddin 1.85 to root my galaxy s3 AT&T phone SGH1747 android 4.3 i followed the directions and when i tried to root it shows failed and i thought that it was finish doing whatever and then i unplugged and now my phone is stuck at firmware upgrade encountered an issue please select recovery mode in klies and try again. I tried removing the battery turning it back on and its still stuck at the same screen. Im new at this please help.
dime10 said:
I used oddin 1.85 to root my galaxy s3 AT&T phone SGH1747 android 4.3 i followed the directions and when i tried to root it shows failed and i thought that it was finish doing whatever and then i unplugged and now my phone is stuck at firmware upgrade encountered an issue please select recovery mode in klies and try again. I tried removing the battery turning it back on and its still stuck at the same screen. Im new at this please help.
Click to expand...
Click to collapse
Just reflash the same rom, this can happen if the odin flash fails. All you have to do is reflash the same rom, if it fails again then just try another USB cable. And one more thing, make sure that the rom you are flashing is the right one.
Are you flashing the phone on a PC? I'm asking because I think the latest release of Odin is 3.07. Using an outdated version of Odin and/or drivers may have caused of the problem.
Since you're on AT&T running 4.3, you cannot reflash an AT&T ROM because there is no AT&T 4.3 ROM that is flashable via Odin. Do not try to flash any ROM that tries to flash an older bootloader because this will brick your phone.
I turned on my rooted Virgin Mobile Galaxy S 3 when it got stuck on the Samsung logo. The logo is animated but the phone will not progress past it. The phone is unable to boot into recovery or download mode; when I try to do so, the phone behaves as if I tried to simply turn it on normally. Samsung Kies is unable to connect to my phone but it does notice when I connect the phone to my computer. Odin also knows when the phone is connected. This occurred after using Odin for something I downloaded from http://forum.xda-developers.com/showthread.php?t=1739426.
asodiu said:
I was messing around with my rooted Virgin Mobile Galaxy S 3 when it got stuck on the Samsung logo. The logo is animated but the phone will not progress past it. The phone is unable to boot into recovery or download mode; when I try to do so, the phone behaves as if I tried to simply turn it on normally. Samsung Kies is unable to connect to my phone but it does notice when I connect the phone to my computer. Odin also knows when the phone is connected.
Click to expand...
Click to collapse
You are actually at the forum for the i747M/U variants of the SG3. To see if we can help you, however, you would need to provide more info ... You said you were doing stuff with your phone? Were you trying to flash a firmware or something? If so, what were you flashing and at what stage did your phone get stuck in the bootloop?
It's not a hard brick if your phone still makes some attempt at starting.
Larry2999 said:
You are actually at the forum for the i747M/U variants of the SG3. To see if we can help you, however, you would need to provide more info ... You said you were doing stuff with your phone? Were you trying to flash a firmware or something? If so, what were you flashing and at what stage did your phone get stuck in the bootloop?
It's not a hard brick if your phone still makes some attempt at starting.
Click to expand...
Click to collapse
I was flashing a download found in the link I have given (the newest Bell one). My phone had progressed past the first sign of the Samsung logo, past the screen saying "Samsung GALAXY S III" and past the animation with the sound before getting stuck on the next Samsung logo.
After flashing, did you boot to recovery and wipe data and cache?
audit13 said:
After flashing, did you boot to recovery and wipe data and cache?
Click to expand...
Click to collapse
As I have said, I am unable to boot to recovery or boot to download mode. I did not wipe data and cache.
Actually, after removing my battery for approximately forty minutes, I was able to boot into download mode. When I attempted to boot into recovery mode after turning on the phone normally (which resulted in the phone being unable to progress past the Samsung logo), I was once again only able to turn on the phone normally and get stuck on the logo.
asodiu said:
Actually, after removing my battery for approximately forty minutes, I was able to boot into download mode. When I attempted to boot into recovery mode after turning on the phone normally (which resulted in the phone being unable to progress past the Samsung logo), I was once again only able to turn on the phone normally and get stuck on the logo.
Click to expand...
Click to collapse
I recommend getting your hands on the Android SDK and using adb to boot into download and recovery modes. I got a water damaged d2att from friend a few months ago and the old volume down key doesn't work and using the command prompt and adb, you can get it to boot to whichever mode you want.
Sent from my SPH-L710 using Tapatalk
asodiu said:
I was flashing a download found in the link I have given (the newest Bell one). My phone had progressed past the first sign of the Samsung logo, past the screen saying "Samsung GALAXY S III" and past the animation with the sound before getting stuck on the next Samsung logo.
Click to expand...
Click to collapse
Virgin Mobile is a 'virtual' mobile network operator but ports mainly on the Sprint CDMA network. Unless your phone specifically had Bell firmware or was porting on Bell, flashing the Bell version would be wrong and could, nay would, cause a brick. Thankfully, though it appears to be only a soft brick and may be recoverable by re-flashing compatible firmware. Unlike Sprint and Virgin which are CDMA networks, Bell is GSM so I'd very much doubt that the firmware you were trying to flash was compatible with your phone. The fact that your phone is still trying to boot suggests that the bootloader is still intact but the system itself has been compromised. Can you remember what Android version your phone was on the last time it functioned normally? If so, I would suggest you visit Sammobile.com or androidfilehost.com and find the same version (or higher) for your phone and then flash to return to stock or near stock. You can always re-root afterwards or flash a custom ROM when your phone is back to working normally.
Since you can get into download mode, you can flash custom recovery in case the stock file you find is a zip file to be flashed via recovery. You should be able to get into recovery mode if you try the button combo again after you have flashed custom recovery via Odin. Otherwise, if it's a *.tar file, just flash directly with Odin.
Larry2999 said:
Virgin Mobile is a 'virtual' mobile network operator but ports mainly on the Sprint CDMA network. Unless your phone specifically had Bell firmware or was porting on Bell, flashing the Bell version would be wrong and could, nay would, cause a brick. Thankfully, though it appears to be only a soft brick and may be recoverable by re-flashing compatible firmware. Unlike Sprint and Virgin which are CDMA networks, Bell is GSM so I'd very much doubt that the firmware you were trying to flash was compatible with your phone. The fact that your phone is still trying to boot suggests that the bootloader is still intact but the system itself has been compromised. Can you remember what Android version your phone was on the last time it functioned normally? If so, I would suggest you visit Sammobile.com or androidfilehost.com and find the same version (or higher) for your phone and then flash to return to stock or near stock. You can always re-root afterwards or flash a custom ROM when your phone is back to working normally.
Since you can get into download mode, you can flash custom recovery in case the stock file you find is a zip file to be flashed via recovery. You should be able to get into recovery mode if you try the button combo again after you have flashed custom recovery via Odin. Otherwise, if it's a *.tar file, just flash directly with Odin.
Click to expand...
Click to collapse
I have successfully managed to flash stock filmware on my phone and now it is working fine. The post which I got the file that I attempted to flash stated that the Bell version would work with the Virgin Mobile phones. My Galaxy S 3 was running Android 4.3.
asodiu said:
I have successfully managed to flash stock filmware on my phone and now it is working fine. The post which I got the file that I attempted to flash stated that the Bell version would work with the Virgin Mobile phones. My Galaxy S 3 was running Android 4.3.
Click to expand...
Click to collapse
Glad to know it's working fine now. Unless the firmware for the 2 phone models have identical build numbers, I'd be surprised the post suggested that cross-flashing may be OK.
Hi guys,
I have the t-mobile s6 edge
After messing around with my device last night and this morning, I decided to go back to stock for a bit.
I have ODIN 3.10.6. I went into download mode on my phone. extracted the stock firmware from this thread: http://forum.xda-developers.com/galaxy-s6-edge/general/sm-g925f-s6-firmware-thread-t3078841
loaded the "G925TUVU1AOCG_G925TTMB1AOCG_G925TUVU1AOCG_HOME.tar.md5" file into the ap box for odin
connected my phone to computer, odin recognized it. hit start. ran successfully. rebooted, android guy came up briefly and said installing system update, then it changed to "Erasing..." then it rebooted again
now it's just bootloops forever after the tmobile screen. I can boot to recovery and it says installing system update each time I boot to recovery, but selecting reboot system there shows a no command error. force the phone to power off... power on again to bootloops.
tried to go into download mode again and reflash everything through odin, same issue!
I started last night by rooting using chainfire, then installing TWRPv2, then I flashed the 5.1.1 ROM available from @eousphoros (sorry for the tag, just thought you might want to be apprised of the issues in getting back to stock after using the 5.1.1 ROM).
with 5.1.1 loaded, smart switch didn't recognize the phone for a reset so I decided to go with the ODIN method and now i'm in bootloop city
any help would be greatly appreciated
kswa1987 said:
Hi guys,
I have the t-mobile s6 edge
After messing around with my device last night and this morning, I decided to go back to stock for a bit.
I have ODIN 3.10.6. I went into download mode on my phone. extracted the stock firmware from this thread: http://forum.xda-developers.com/galaxy-s6-edge/general/sm-g925f-s6-firmware-thread-t3078841
loaded the "G925TUVU1AOCG_G925TTMB1AOCG_G925TUVU1AOCG_HOME.tar.md5" file into the ap box for odin
connected my phone to computer, odin recognized it. hit start. ran successfully. rebooted, android guy came up briefly and said installing system update, then it changed to "Erasing..." then it rebooted again
now it's just bootloops forever after the tmobile screen. I can boot to recovery and it says installing system update each time I boot to recovery, but selecting reboot system there shows a no command error. force the phone to power off... power on again to bootloops.
tried to go into download mode again and reflash everything through odin, same issue!
I started last night by rooting using chainfire, then installing TWRPv2, then I flashed the 5.1.1 ROM available from @eousphoros (sorry for the tag, just thought you might want to be apprised of the issues in getting back to stock after using the 5.1.1 ROM).
with 5.1.1 loaded, smart switch didn't recognize the phone for a reset so I decided to go with the ODIN method and now i'm in bootloop city
any help would be greatly appreciated
Click to expand...
Click to collapse
You probably need to do a factory reset
In the future you should make a full backup before installing a rom
kswa1987 said:
Hi guys,
I have the t-mobile s6 edge
After messing around with my device last night and this morning, I decided to go back to stock for a bit.
I have ODIN 3.10.6. I went into download mode on my phone. extracted the stock firmware from this thread: http://forum.xda-developers.com/galaxy-s6-edge/general/sm-g925f-s6-firmware-thread-t3078841
loaded the "G925TUVU1AOCG_G925TTMB1AOCG_G925TUVU1AOCG_HOME.tar.md5" file into the ap box for odin
connected my phone to computer, odin recognized it. hit start. ran successfully. rebooted, android guy came up briefly and said installing system update, then it changed to "Erasing..." then it rebooted again
now it's just bootloops forever after the tmobile screen. I can boot to recovery and it says installing system update each time I boot to recovery, but selecting reboot system there shows a no command error. force the phone to power off... power on again to bootloops.
tried to go into download mode again and reflash everything through odin, same issue!
I started last night by rooting using chainfire, then installing TWRPv2, then I flashed the 5.1.1 ROM available from @eousphoros (sorry for the tag, just thought you might want to be apprised of the issues in getting back to stock after using the 5.1.1 ROM).
with 5.1.1 loaded, smart switch didn't recognize the phone for a reset so I decided to go with the ODIN method and now i'm in bootloop city
any help would be greatly appreciated
Click to expand...
Click to collapse
AHH!! Sorry to have made this post... here's what I did to get it actually boot:
reflahed the stock firmware through odin again, tried to reboot, it failed, obviously. rebooted to recovery, factory reset in recovery, power down option in recovery, then turned the phone on again and it magically worked!
hopefully this post will help someone who encountered the same issue
eousphoros said:
You probably need to do a factory reset
In the future you should make a full backup before installing a rom
Click to expand...
Click to collapse
thank you so much for the quick reply, I ended up figuring out the solution while you were typing. sorry to pull you away from other tasks. I have several backups saved to my PC but thank you for the reminder!! :laugh::laugh:
kswa1987 said:
AHH!! Sorry to have made this post... here's what I did to get it actually boot:
reflahed the stock firmware through odin again, tried to reboot, it failed, obviously. rebooted to recovery, factory reset in recovery, power down option in recovery, then turned the phone on again and it magically worked!
hopefully this post will help someone who encountered the same issue
Click to expand...
Click to collapse
I had the same excat same thing happen when flashing this via Odin. I didnt need to Odin stock twice though . I just booted stock recovery and did a factory reset. After that I went ahead an powered down and rebooted . All good now
How long did you have to wait in the stock recovery to get past the "installing system update" screen? Mine just sits there and I'm unable to view other options in recovery.
EDIT for noobs (like me): wait 30 seconds on the "installing system update" screen.
I'm still stuck in boot loop
Im in the same exact situation , but I'm still stuck in boot loop. I followed your restore instructions and nothing. Please help.
Creel711 said:
Im in the same exact situation , but I'm still stuck in boot loop. I followed your restore instructions and nothing. Please help.
Click to expand...
Click to collapse
Looks here, may apply to your case. http://forum.xda-developers.com/showthread.php?p=63226466
Pp.
I initially used odin to flash OI1 update, after a rom I was using caused problems and I got bootloop. It changed bootloader value to b:3 and I'm unable to downgrade now so I used smart switch which didn't recognize device so used emergency recovery and still bootloop. I have factory reset and wipe cache multiple times along with adb side load and individual flashes of bootloader, modem, kernel, flashed custom kernel and twrp to access fix permissions and to mount partitions with advanced wipe etc and still wont boot past logo. Also during one fix attempt phone said can't mount system.. Idk I'm not understanding where the problem is .everything says successful but I'm still in bootloop. Please help. I've spent hours everyday for the past week searching & trying different things that seem might help so open to any suggestions.
Problem with Samsung Galaxy S4 Mini GT-I9195
Hi everyone
I'm new to the whole ROM flashing and using Odin. I had a bootloop problem and recovery mode showed all the options but has a green android man laying down with red icon above him and No Command below the android man. Tried the factory wipe and cache wipe but it gives some red writing with the word failed in the coding and the word error under the android man. Tried to flash a stock ROM from sammobile using Odin. Odin gives a pass but the same problems persist. Can someone please help?
any solution, i have this problem to? only bootloop, nothing else. Updatet bootloader with 4up
kswa1987 said:
Hi guys,
I have the t-mobile s6 edge
After messing around with my device last night and this morning, I decided to go back to stock for a bit.
I have ODIN 3.10.6. I went into download mode on my phone. extracted the stock firmware from this thread: http://forum.xda-developers.com/galaxy-s6-edge/general/sm-g925f-s6-firmware-thread-t3078841
loaded the "G925TUVU1AOCG_G925TTMB1AOCG_G925TUVU1AOCG_HOME.tar.md5" file into the ap box for odin
connected my phone to computer, odin recognized it. hit start. ran successfully. rebooted, android guy came up briefly and said installing system update, then it changed to "Erasing..." then it rebooted again
now it's just bootloops forever after the tmobile screen. I can boot to recovery and it says installing system update each time I boot to recovery, but selecting reboot system there shows a no command error. force the phone to power off... power on again to bootloops.
tried to go into download mode again and reflash everything through odin, same issue!
I started last night by rooting using chainfire, then installing TWRPv2, then I flashed the 5.1.1 ROM available from @eousphoros (sorry for the tag, just thought you might want to be apprised of the issues in getting back to stock after using the 5.1.1 ROM).
with 5.1.1 loaded, smart switch didn't recognize the phone for a reset so I decided to go with the ODIN method and now i'm in bootloop city
any help would be greatly appreciated
Click to expand...
Click to collapse
had the same issue ... did a factory wipe...(had lineage os 14 installed with gapps 7.1.1) flashed stock rom using odin(success) . stuck in bootloop(samsung logo fades in and out) pleaase help (sm-g900H)
Very usefull post, same issue, solved trough recovery->wipedata/factoryreset. Thanks!!!!
my s6 was freezing and restarting again and again, I reinstalled the firmware for odin and then it didn't encounter any problem for a whole day but now i have the same problem again - freezing and restarting
any help would be appreciated
I am already done with factory reset and wiping cache partition but still nothing turnout to be helpful
Hi Please help me.
I did everything that mentioned but no succes at all. Any new suggestion?
Btw my phone passing ODIN and stuck in "installing system updates then erasing"
hello
i need downgred g925t frome androide 7 to 6 or 5.1.1
can anyone help me
im flashed phone whit dis frimwer from anroide 7 G925TUVS6FRC1_G925TTMB6FRC1_TMB
im dawnloaded this frimwer 4Files-G925TTMB3EPD1-6.0.1-By-NoLoGiG but not work or not flashed have error
I received a notification for an update today, so I went ahead and did it. It completed one cycle and then rebooted and began a new cycle. At 30% the android mascot fell over and the update failed. This continued for 10 minutes or so. I then shut the phone down after a reboot and it went to a boot loop getting to the Samsung/Android logo. I read that going into recovery mode could fix the issue with a wipe cache and restore, only, trying to get into recovery mode gives me a blue screen with an message saying "software not authorized by at&t is installed on the phone".
I bought the phone today and did not do much except mess with the streaming apps. I did not try to root or install custom roms and I believe the error is due to the update not completing. Is there a way I can fix this or should I just take the phone back to at&t and get a new one? As I said, I bought it today (technically yesterday I guess).
Thanks in advance for the feedback and advice
Try flashing the latest firmware from sammobile or updato.com or use the samfirm tool from XDA (fastest) and ODIN 3.13.1 to flash it
Use CSC and not HOME_CSC
Flash all 4 parts together
This will not void warranty or trip knox