So, i have a Samsung Galaxy S III i747... Flashed it with CyanogenMod, and saw horrible battery life, and the phone stayed hot... Flashed back to an older version of CyanogenMod, and it was just unstable and a mess, so i formatted everything from recovery, and installed the stock ROM via Odin... Stock ROM worked, but i wanted back to Cyanogen, so i rooted the phone, downloaded the ROM manager, downloaded the ROM, and installed it... And it failed. So, i figured i'd hit the NAND Erase All button in Odin, and then repartition the phone, thinking the buttons wouldn't blow up the world... Now i'm stuck at the Samsung logo at boot. I've tried several different versions of the stock ROM, i can still get into recovery, and i can still get into download mode, but it always get stuck at the Samsung Logo after the AT&T carrier video.
Anyone have any ideas? I'm really hoping i didn't brick my phone... Odin sees it, and everything still works, i just can't boot the stock ROM, which means i can't get anywhere else.
try a factory reset in recovery after flashing rom
PhoneTamer said:
So, i have a Samsung Galaxy S III i747... Flashed it with CyanogenMod, and saw horrible battery life, and the phone stayed hot... Flashed back to an older version of CyanogenMod, and it was just unstable and a mess, so i formatted everything from recovery, and installed the stock ROM via Odin... Stock ROM worked, but i wanted back to Cyanogen, so i rooted the phone, downloaded the ROM manager, downloaded the ROM, and installed it... And it failed. So, i figured i'd hit the NAND Erase All button in Odin, and then repartition the phone, thinking the buttons wouldn't blow up the world... Now i'm stuck at the Samsung logo at boot. I've tried several different versions of the stock ROM, i can still get into recovery, and i can still get into download mode, but it always get stuck at the Samsung Logo after the AT&T carrier video.
Anyone have any ideas? I'm really hoping i didn't brick my phone... Odin sees it, and everything still works, i just can't boot the stock ROM, which means i can't get anywhere else.
Click to expand...
Click to collapse
I Odin'd to stock a couple days ago and was at the Samsung Logo for a WHILE (over and hour). It did just go eventually.
Not sure what did it... Got a PIT file, and then did the NAND Erase All bit again when i installed the stock ROM again. Wiped data as soon as install finished, and it booted right up. I'm happy again
Now if i can just figure out the LTE glitch...
Related
I was messing with my Gs2, trying out some new roms (it has been rooted and custom flashed since i got the phone a while ago) and ended up with a soft brick getting stuck at the Samsung screen during boot. No big deal I though (since this is my backup phone I didnt worry about it) and planned on flashing back to stock with Odin and starting over. I flashed the stock 4.1 via odin and it all seemed to go fine, but when it rebooted it got stuck at the same samsung screen. I left it there for like 20 minutes and it never booted. I then downloaded the stock 4.0 and same thing. I am about to try going back in time to the stock 2.3 and see if i can work my way forward from that, but if it doesnt work, what is the cause of the phone not being able to boot after all these stock flashes?
jay-red said:
I was messing with my Gs2, trying out some new roms (it has been rooted and custom flashed since i got the phone a while ago) and ended up with a soft brick getting stuck at the Samsung screen during boot. No big deal I though (since this is my backup phone I didnt worry about it) and planned on flashing back to stock with Odin and starting over. I flashed the stock 4.1 via odin and it all seemed to go fine, but when it rebooted it got stuck at the same samsung screen. I left it there for like 20 minutes and it never booted. I then downloaded the stock 4.0 and same thing. I am about to try going back in time to the stock 2.3 and see if i can work my way forward from that, but if it doesnt work, what is the cause of the phone not being able to boot after all these stock flashes?
Click to expand...
Click to collapse
Im stuck in the same boat with my S4
which ODIN version are you using and are you using the links from SAMMOBILE to get the firmware you need ? also what are your methods of procedure and is odin giving out any errors or saying pass and still no boot ?
I have been using the i747z ROMs for quite some time and after trying a bunch of other ROMs I always reverted back to theirs. So when their 3.0 version came out with Android 4.3 I installed it, using ClockWorkMod recovery. Right after it installed, CWM displayed a message about the boot loader and to fix it. So I went ahead and did that (Don't really remember what the message was) What I know is that I lost root. Also the phone could not connect to the mobile network, only on Wifi. So this morning, I factory reset the phone again, and attempted to root the phone with Odin with CF-Auto-Root-d2att-d2uc-samsungsghi747 (which I had used when I first rooted the phone). Now the phone doesn't boot past the 2nd samsung logo, it starts out with the Samsung logo with the blue circle around it, then the AT&T Rethink Possible and then the plain white Samsung logo. Also, the LED has a slow blue flicker.
I can get the phone into download mode and I have used Odin to attempt to load the stock firmware and the stock bootloader. But after restarting the phone I can't get past the same screen described above.
I am pretty sure this is not related to the i747z v3.0 ROM but rather something a miss with the order in which things need to start in Android. I have done some reading on that but I am not sure what I need to do to correct this soft brick situation. ( I have googled "soft brick" as well)
Any thoughts would be greatly appreciated!
mozphoto said:
I have been using the i747z ROMs for quite some time and after trying a bunch of other ROMs I always reverted back to theirs. So when their 3.0 version came out with Android 4.3 I installed it, using ClockWorkMod recovery. Right after it installed, CWM displayed a message about the boot loader and to fix it. So I went ahead and did that (Don't really remember what the message was) What I know is that I lost root. Also the phone could not connect to the mobile network, only on Wifi. So this morning, I factory reset the phone again, and attempted to root the phone with Odin with CF-Auto-Root-d2att-d2uc-samsungsghi747 (which I had used when I first rooted the phone). Now the phone doesn't boot past the 2nd samsung logo, it starts out with the Samsung logo with the blue circle around it, then the AT&T Rethink Possible and then the plain white Samsung logo. Also, the LED has a slow blue flicker.
I can get the phone into download mode and I have used Odin to attempt to load the stock firmware and the stock bootloader. But after restarting the phone I can't get past the same screen described above.
I am pretty sure this is not related to the i747z v3.0 ROM but rather something a miss with the order in which things need to start in Android. I have done some reading on that but I am not sure what I need to do to correct this soft brick situation. ( I have googled "soft brick" as well)
Any thoughts would be greatly appreciated!
Click to expand...
Click to collapse
After flashing through odin did you format data?If not try it.
Go into recovery and wipe data.
**SOLVED**
Thanks xXFl4sh, I had tried that.
Solved!
Alright where do I start? How about RTFM Some how I had missed the part about flashing a bootloader and a modem after the ROM. Not recalling having to do that before, I skipped right over it. Once the recovery CWM 6.0.3.1 was finally loaded, getting the flashing the ROM, the bootloader and the modem was easy as usual.
The key was having to use Odin to install a recovery in .tar or .tar.md5 format since I could not access a Recovery Mode on the GS3, as well as a rooted stock image (I used root66_ATT_I747UCDLK3.tar.md5 which is a rooted Android 4.1.1 for AT&T) For the recovery, I couldnt' find a .tar or .tar.md5 for ClockWorkMod (did find a utility to convert it, but didn't want to introduce another variable into the mix) so I used one from Team Win Recovery (v2.6.3.0) and with that I loaded the CWM recovery. Once all of that was in place, I proceed to factory reset, clear data, cache, system and then flash the new ROM, bootloader and modem.
In all of this I learned quite a bit about the whole process and how to narrow down possible resolutions. I still see the "Rom may flash stock recovery on boot" message after flashing either a ROM, bootloader or modem, but just backing out without answering Yes or No seems to work. Also (and this may be related, I don't see the option to restart in recovery from shutdown menu). Don't really know what that's all about for now, and honestly don't want to mess around (at least for a while)
I know the steps are general, but I hope this can help some else if they get their devices in a soft brick situation. As for the i747z v3 ROM with 4.3, I really like it, everything works (Wifi,Blutooth,tethering) and the battery seems good as well.
Thanks!
Experienced Galaxy rooter here. I used Odin Mode on the Sg3 as well as my gf Pro tab 8.4 and my 10.1 as well. Ive never had problems until now. So here's what happened today:
This morning
I decided to install Twrp using Flashify. Having been rooted for months, it worked. I then installed Cm 11 using TWRP. I wiped cache and installed gapps from goo manager. Everything went smooth. I played around with it for about an hour. No problem.
Then I installed Team freezes ROM. I used flashify. Everything seemed normal, then I realized I couldn't get past Samsung title screen. So i plugged up to Odin and installed stock Recovery. Nothing. Reinstalled TWRP... can't get into Twrp. Used Odin again to install Phillz.. Nothing.
Once again I installed original stock through Odin. Here I am again stock at the Samsung boot screen. I can only do three things 1. Turn off 2. Reset 3.odin mode
What do i do?
I just want to get this thing to boot so i can see what happened or at lest into some sort of recovery where i can load from sd
If you're in Download (Odin) Mode....
Make sure you have S/N on hand.
Enter Download Mode and run KIES3, choose Firmware Upgrade and Initialization
Enter model number and S/N
Returning to bone stock may take an hour, so make sure the battery is fully charged. Moreover, YOUR TAB WILL BE TOTALLY WIPED AND GO BACK TO BONE STOCK!
mingkee said:
If you're in Download (Odin) Mode....
Make sure you have S/N on hand.
Enter Download Mode and run KIES3, choose Firmware Upgrade and Initialization
Enter model number and S/N
Returning to bone stock may take an hour, so make sure the battery is fully charged. Moreover, YOUR TAB WILL BE TOTALLY WIPED AND GO BACK TO BONE STOCK!
Click to expand...
Click to collapse
Thanks for this. I lost my system due to System Cleaner 2 fudgin' it up on reboot. I was about to hassle Best Buy into an exchange but gave this a try. I thought I had it made by doing a factory reset but even that didn't work. Luckily Kies came to the rescue after I figured out they wanted a generic model SM-T320, not the rest of it. Again thanks to you mate!
So here's the back story. I'm usually good with roms/recovery/flashing. Even did some custom rom work on my old Galaxy S 4G, so not a noob. I have a Wind T999V.
Had Touch-CWM installed, ran a few 4.4 ROM's for a while, tried LP, Liquid smooth. Liked it ok, but wanted to try OctoROM LP. It needs TWRP. Had a few problems with TWRP before on my phone, the Wind variant seems somewhat different in small ways, but figured I'd give it a try again to flash OctoROM since it needs TWRP. Thought maybe the TWRP has improved since I tried last, so installed TWRP, tried to flash Octo, but TWRP wouldn't see my internal SD card at all. The same problem I had before. I didn't feel like digging out a SD card from my camera to put Octo on, so rebooted the phone, installed CWM back, rebooted again, got a bootloop somewhere along the way.
Figured I'd go with Odin back to stock and start over. Grabbed odin (hard now, lots of spam/scam copies) and my stock firmware for the Wind version from Doc's thread. Flash the tar, which took forever (used a sort of crappy cable) and it auto rebooted after like 20 mins of flashing, just stuck at the sammy logo for like 20 mins. Too long, still looped I think.
Grabbed a different cable and a newer version of a good odin I know from my network I had laying around, 3.09, and tried again. At the pulsing samsung logo again, going to wait, but if I did softbrick it, do I need to repartition and a pit file to get the FS back to something different than any of the KK or LP rom's I ran?
EDIT:
Read some threads and took doc's advice and booted into stock recovery and wiped data and cache, and it finally booted. Phew.
Hello, I have this SM-T520 galaxy tab pro 10.1 that I bought new some years ago. I had rooted it and ran with it for a while until I wanted to flash a custom rom. I can't remember how that went but I assume it went badly, since it hasn't been able to boot into anything for years. It tries to boot up as long as it has power (even without pressing the power button) but it doesn't do anything after you get to the Samsung screen. It just stays on a back lit black screen. I can get into the Android system recovery by pressing power and volume up, then releasing power. It says it has "K0T49H.T520XXUANAE" at the top but I'm not sure if I had changed that at some point. Anyway, even after wiping data/factory reset and wiping cache partition it still cannot boot. I tried updating from external storage a few times before but it kept failing. Maybe I had the wrong file? What can I do to fix this thing? Any help is appreciated.
Go to pc, download odin. Go to https://www.sammobile.com/firmwares/ enter device and look and download lastest offered firmware for your region. Flash downloaded firmware with odin. You should be on a booting stock rom now.
You can do this as often as you like (eg. when device is bad after playing with custom roms).
hamudistan said:
Go to pc, download odin. Go to [website] enter device and look and download lastest offered firmware for your region. Flash downloaded firmware with odin. You should be on a booting stock rom now.
You can do this as often as you like (eg. when device is bad after playing with custom roms).
Click to expand...
Click to collapse
That worked perfectly... I feel like that was too simple and I should have been able to find this online somewhere. Maybe I just couldn't find the right word combo in google.... Thanks!!
Now to try flashing a custom rom on this, since touchwiz makes me cringe.