Stock Rom Flash - Verizon Samsung Galaxy S 4

Im currently using Safestrap, and made the really stupid mistake of flashing over the stock rom -_- and now im having problems flashing anything. I origionally flashed OctOS over the stock rom and when i rebooted the phone it didnt even get to the Welcome Screen, just sat at a black screen for ever. So then I flashed http://forum.xda-developers.com/show....php?t=2343355, and it gets to the Welcome Screen and just sits there for ever...
Im currently creating a partition and going to try flashing to a partition, where can I download the Verizon Galaxy S4 Stock Rom?
I did create a backup of the Stock Rom but when it was flashed over it Wiped the phone and I lost the backup

Related

[Q] Bricked... flashing stock rom doesn't work

Hey guys, I'm hoping someone can help me out. I've tried searching the forums and using different methods to recover it, but none have worked so far.
SO I flashed the ICS Domination theme over Diet ICS rom, stuff was continuously force closing, so I factory wiped with the intention of re-flashing just the rom... after a reset the phone was stuck on the samsung boot screen.
I've tried using Odin to load the stock Rogers rom, it says it worked, but trying to boot the phone up its stuck on the samsung boot screen.
Am I missing something? Is there anything you guys can suggest I try??
use ODIN to flash a new recovery.img and restore from a nandroid
I didn't make a nandroid backup (i know, retarded), where can I get one and how can I push it to my internal memory considering the phone won't start up and I can't flash from external SD

Stock ROM doesnt work

Hi there.
I had a custom rom on my Galaxy S3, and I wanted to go back to stock rom. Before I had a custom rom, I checked my product code, just in case if I ever wanted to flash stock rom. So, I downloaded a stock rom from sammobile and flashed it with Odin. I had a successful flash, but when the phone rebooted, it stopped at the samsung logo and it's like that every time I turn on the phone.
I aslo tried to flash it with the same rom, but from a different site (androidfirmwares), but every time I treid to do that, Odin crashed ( Odin downloader has stopped working).
I can't even boot into CWR to flash any custom rom, cuz it's gone. There is only stock recovery.
Please help
Which Rom were you trying to flash when this happened, and give details of how you flashed please
luka46 said:
Hi there.
I had a custom rom on my Galaxy S3, and I wanted to go back to stock rom. Before I had a custom rom, I checked my product code, just in case if I ever wanted to flash stock rom. So, I downloaded a stock rom from sammobile and flashed it with Odin. I had a successful flash, but when the phone rebooted, it stopped at the samsung logo and it's like that every time I turn on the phone.
I aslo tried to flash it with the same rom, but from a different site (androidfirmwares), but every time I treid to do that, Odin crashed ( Odin downloader has stopped working).
I can't even boot into CWR to flash any custom rom, cuz it's gone. There is only stock recovery.
Please help
Click to expand...
Click to collapse
if you are getting stuck on the boot screen after you flashed the stock rom this always works..go to recovery do a data reset and wipe cache.
this is really weird and a stupid thing I did when I was completely new to android..a little over a month ago.I got stuck on the boot screen and accidentally flash CF-Root instead of the stock firmware..when the phone rebooted it worked just fine.I dont think its supposed to work that way..:S
ahmedmaaiee said:
if you are getting stuck on the boot screen after you flashed the stock rom this always works..go to recovery do a data reset and wipe cache.
this is really weird and a stupid thing I did when I was completely new to android..a little over a month ago.I got stuck on the boot screen and accidentally flash CF-Root instead of the stock firmware..when the phone rebooted it worked just fine.I dont think its supposed to work that way..:S
Click to expand...
Click to collapse
I did as you said and it works :laugh:
Thank you :good:

[Q] Stuck in recovery mode (TWRP)

Hey guys,
I recently flashed a new 4.3 rom to my S3 (Imperium 21.0).
After a while i decided to update the kernel to Googy Max, downloaded it from OTA and went to install it via TWRP, after installing the galaxy decided it wouldn't boot and just returned to the recovery all the time, i thought it must be the broken kernel and re-flashed the rom, everything was fine until i went back to the recovery (to backup the rom), after i finished backup and tried to restart my S3 the same happens, the galaxy just reboots back to the recovery, and the only way i found to get of it is to re-flash the rom :/
I don't want to re-flash it again... Any ideas what can i do?
fr0z1k said:
Hey guys,
I recently flashed a new 4.3 rom to my S3 (Imperium 21.0).
After a while i decided to update the kernel to Googy Max, downloaded it from OTA and went to install it via TWRP, after installing the galaxy decided it wouldn't boot and just returned to the recovery all the time, i thought it must be the broken kernel and re-flashed the rom, everything was fine until i went back to the recovery (to backup the rom), after i finished backup and tried to restart my S3 the same happens, the galaxy just reboots back to the recovery, and the only way i found to get of it is to re-flash the rom :/
I don't want to re-flash it again... Any ideas what can i do?
Click to expand...
Click to collapse
Can close thread, after installing another recovery via Odin it was fixed

stuck after trying to flash rom

So i unlocked my phone and decide to flash a custom rom. I have an ATT HOX+ that was on 4.2.2. I rooted and installed CWM Advanced Edition PhilZ Touch recovery and then stupidly forgot to backup then wiped and installed the rom. the Rom i used AOKP Pure unofficial international. I flashed the img file first as well but didnt fix the stuck at boot screen with it saying initiating swagger. I think i should not be using this rom because my phone is from ATT. So bootloader still works, recovery still works i just cant mount my phone so i can send any more roms to try. And i cant push any zip to my phone. So im kinda stuck on what to do. Any Suggestions? Currently phoneless
anthonyuslu said:
So i unlocked my phone and decide to flash a custom rom. I have an ATT HOX+ that was on 4.2.2. I rooted and installed CWM Advanced Edition PhilZ Touch recovery and then stupidly forgot to backup then wiped and installed the rom. the Rom i used AOKP Pure unofficial international. I flashed the img file first as well but didnt fix the stuck at boot screen with it saying initiating swagger. I think i should not be using this rom because my phone is from ATT. So bootloader still works, recovery still works i just cant mount my phone so i can send any more roms to try. And i cant push any zip to my phone. So im kinda stuck on what to do. Any Suggestions? Currently phoneless
Click to expand...
Click to collapse
Why would it boot........????
Please do some reading......
The recovery itself the CWM Advanced Edition PhilZ Touch recovery is For INTERANTIONAL MODEL
Please note enrc2b means international HTC One X+ not AT&T
Please flash this recovery and for the list of custom ROM's for AT&T model refer to this thread
Got the phone working. Finally found a stock RUU that worked. and yah i didnt do enough reading prior to flashing this rom. Thanks for your help. Hopefully a 4.4 rom comes out for the ATT HOX+ soon.

[Q] New ROMs stuck at splash screen using SafeStrap

I have an unlocked AT&T Samsung Galaxy S4 and have been trying to use SafeStrap to flash new ROMs. Everything goes like normal, ROM looks to be successfully installed. But I have tried to flash three different ROMs that are compatible with SafeStrap and my device, and each of them get stuck in an endless splash screen (I waited more than 20 minutes.) I did not mess with the stock ROM slot, so that is still intact. This is really frustrating, has anyone else encountered this problem? I've already tried factory resets and data wipes on the ROM slot, and also have deleted and re-partitioned the slot twice. As suggested online, I was flashing three zip at once: the ROM, kernel, and superuser.
HAAAALP

Categories

Resources