[Q] New ROMs stuck at splash screen using SafeStrap - Android Q&A, Help & Troubleshooting

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

Related

[Q] Cannot get into phone after installing ROM

Installed CWM and rooted my phone tonight, everything went well. I have a canadian sgh-i527m. I took a backup through cwm and tried to install cyanogenmod and it failed. I don't recall the error....tried two other and both both failed as well. Now I can reboot and get into recovery but when i try and restart the phone, it just reboots itself a couple times and goes back to recovery on its own.
I I tried restoring the backup and says it's successful, but then it hangs at the glowing samsung screen. I wiped the cache and device and can only get to recovery. I'm downloading the stock os for bell and will install that through odin in the morning, but can anyone help with what i'm doing wrong? I never had any issues installing many roms to my note II.

[Q] Crie for help: S4 Cant get to recovery

Verizon S4 MDK
Background: I was on an MIUI port for the verizon s4, Wanted to flash to Chaos rom 3.0, recovery "Failed out every time, updated TWRP to 2.8.01, flashed Chaos 3.0 ( This rom requires a non stock kernal), Forgot to install Kernal before flashing (partly because i thought I already had one)< rom flashed successfully, rebooted and got a blue screen with pixels all over, rebooted again and the phone sits at a black screen that blinks every 5 seconds and vibrates, can ONLY get to Download mode no recovery.
*tried flashing twrp in ODIN and it fails, even on different Odin versions.
I want to atleast be able to get to recovery again so i can save my internal memory files (pictures mostly), how can i get there?
Trying to use MDK no wipe in ODIN now.
MDK no wipe.tar worked, allowed me to access my files. Thanks for all the help I didnt get! hope this post helps someone down the road

[Q] [HELP!] Stuck at ROM logo. (Various ROMs)

Was running Alliance 26 for a long time but Chrome was weird and slow so I figured I'd try out Alliance 27. Flashed Alliance 27 through TWRP recovery and got stuck at the logo. Figured my TWRP might be old so I upgraded from 2.6 to 2.8 and retried the ROM install... still stuck at logo. Then I thought it might be a kernel issue and flashed AGNi's pureSTOCK... still hangs on boot logo. I then tried several different ROMS, LiquidSmooth, DN3, etc. all flash fine but never get past the logo screen.
Anyone have any ideas where to go next?
I got DN3 5.2 to load finally, but it says that my sim card isn't inserted. I don't think my phone is registering as an I605 for some reason. Phone status lists it as something else... an S5 maybe? I'm confused.
[EDIT] Yeah. DN3 is saying my phone is a SM-G900F... Samsung Galaxy 5. Still says missing sim card.
theoldboiler said:
Was running Alliance 26 for a long time but Chrome was weird and slow so I figured I'd try out Alliance 27. Flashed Alliance 27 through TWRP recovery and got stuck at the logo. Figured my TWRP might be old so I upgraded from 2.6 to 2.8 and retried the ROM install... still stuck at logo. Then I thought it might be a kernel issue and flashed AGNi's pureSTOCK... still hangs on boot logo. I then tried several different ROMS, LiquidSmooth, DN3, etc. all flash fine but never get past the logo screen.
Anyone have any ideas where to go next?
Click to expand...
Click to collapse
Hi, quite a few of us are having this same problem. It appears to be several things; I.e. earlier bootloader unlock method and twrp. Try this method: install philz latest recovery. Format for a new install, flash rom. Immediately after (don't reboot) flash agni kernel. note: if it shows the kernel successfully flashed, your good. After, simply reboot and all should boot correctly. As an fyi, if you boot the rom and don't flash the kernel, it will not work. You must reformat and do the sequence above.
Sent from my SCH-I605 using XDA Premium HD app

[Q] Samsung XCover 2 always boots in recovery

Hello!
I have a Samsung XCover 2 (GT-S7710) and I've tried to flash a CM-Rom for quite a while, but without success. At some point my phone stopped to boot a single rom I installed. It automatically starts into CWM Recovery, even with my backup (made with cwm). I thought cwm could be the bad guy and I flashed the Stock Rom with Odin, but same problem here. In Odin everything is fine but again it starts in recovery automatically.
I've read that the bootloader could be the problem and you need to flash it with Odin, but I don't know which one to take, since all treads were about other phones.
Does anyone know which bootloader I have to take or if there is another solution?
Greetings!

Roms/Bootloaders/Recovery

ok so I might have a lot of posts on here but really I just blag my way through and I usually end up with a working rom but now, I am stuck.
I was running Sixperience V2 6.0.1 and after flashing lots of stuff including different bootloaders, it worked (I was coming from 5.1.1.) Anyway, I decided to flash something else and it failed (and wiped TWRP). So I have gone back to stock rom via Odin and flashed that. It's a 5.1.1 BTU and Odin says pass when installed. But that's now stuck on the boot screen. So rather than flash lots of bootloaders (I assume that's the problem) I wondered if someone might be able to help me get a Rom (any rom) back up and running.
Thanks
PS - I was trying to flash his new rom, the S7 port but it wouldnt get past the first Samsung splash screen.
Doesnt matter flashing a lot of bootloaders, what you flashed recently matters so -
Flash an appropriate mm bootloader then it might get past the splash screen.
And have you done according to instructions wipe - cache dalvik cache and format????

Categories

Resources