Black screen after installation stang5litre Ediition SCH-i545 VRUGOF1 - Verizon Samsung Galaxy S 4

Black screen after installation stang5litre Ediition SCH-i545 VRUGOF1
I have the problem. That my phone is not working after installing the stang5litre Ediition ROM.
That is, it is only the Samsung Galaxy S4 logo, short start-up tone, and the screen remains black and does not respond. Restart with removing the battery.
I was as successful procedure:
flashed with Odin a fresh stock ROM (I545VRUGOF1_I545VZWGOF1_I545VRUGOF1_HOME.tar.md5)
- Handy for Wifi furnishings.
- restart
- Rooted With Kingroot
- Converted to SuperSU
installed Flash Fire -
Then according to the instructions in the OF1 Instructions thread carried on:
Please refer
http://forum.xda-developers.com/gala...n-5-0-t3132555
Where is the error?
Is it provided for a howto?
I have flashing with odin and Stock ROM because its running.

You may need to use an earlier version FlashFire, the latest version will result in a black screen startup

muxuejin said:
You may need to use an earlier version FlashFire, the latest version will result in a black screen startup
Click to expand...
Click to collapse
he didn't RTFM and neither did you
FF likely moved wipe to the bottom on him so now he needs to odin back to stock

I had this same thing happen, but I got stuck in a setup wizard process closing error loop. When I tired to flash to stock, ODIN failed on every flash I tired, so my phone right now is in a soft bricked state with no signed of coming out of it.

No problem for me this rom... is good rom

Related

Bootlooping Roms Help

Just got my S4 in the mail today and the first thing I did was go looking for a Rom.
I rooted with towelroot and then installed Safestrap. My first flash was Slimkat but all it did was boot to a black screen. I went back to recovery and did a factory reset. Still black screen.
I re-booted to recovery and installed Google Play Edition. That got stuck on the boot logo for about 5 minutes. Went back to recovery and did a factory resit, still stuck on boot logo.
Next I installed Hyperdrive. stuck in bootloop for 15 minutes before I gave up and Odin'ed back to stock. any suggestion why I'm failing at installing custom roms?
swing4thefence said:
Just got my S4 in the mail today and the first thing I did was go looking for a Rom.
I rooted with towelroot and then installed Safestrap. My first flash was Slimkat but all it did was boot to a black screen. I went back to recovery and did a factory reset. Still black screen.
I re-booted to recovery and installed Google Play Edition. That got stuck on the boot logo for about 5 minutes. Went back to recovery and did a factory resit, still stuck on boot logo.
Next I installed Hyperdrive. stuck in bootloop for 15 minutes before I gave up and Odin'ed back to stock. any suggestion why I'm failing at installing custom roms?
Click to expand...
Click to collapse
Are you installing to the stock slot?
Yes. I have gotten the impression that you can ONLY install to the stock slot.
swing4thefence said:
Just got my S4 in the mail today and the first thing I did was go looking for a Rom.
I rooted with towelroot and then installed Safestrap. My first flash was Slimkat but all it did was boot to a black screen. I went back to recovery and did a factory reset. Still black screen.
I re-booted to recovery and installed Google Play Edition. That got stuck on the boot logo for about 5 minutes. Went back to recovery and did a factory resit, still stuck on boot logo.
Next I installed Hyperdrive. stuck in bootloop for 15 minutes before I gave up and Odin'ed back to stock. any suggestion why I'm failing at installing custom roms?
Click to expand...
Click to collapse
Assuming you are using Safestrap correctly.... check your downloads.
Also, slimkat is not compatible with your phone unless you are on mdk which I doubt. There is a process by which you can get the GPE ROM to run on our device if you aren't on mdk but I suspect all you did was flash the zip. We can't use AOSP Roms and if your going by the list of Roms in this thread http://forum.xda-developers.com/showthread.php?t=2297370 you will find most of them to be incompatible. There is no reason that Hyperdrive would get stuck in a bootloop unless there were something wrong with the install or your download.
liljoe727 said:
Assuming you are using Safestrap correctly.... check your downloads.
Also, slimkat is not compatible with your phone unless you are on mdk which I doubt. There is a process by which you can get the GPE ROM to run on our device if you aren't on mdk but I suspect all you did was flash the zip. We can't use AOSP Roms and if your going by the list of Roms in this thread http://forum.xda-developers.com/showthread.php?t=2297370 you will find most of them to be incompatible. There is no reason that Hyperdrive would get stuck in a bootloop unless there were something wrong with the install or your download.
Click to expand...
Click to collapse
Your right. I "Just flashed" I Odined back to stock and tried again, this time following the isntructions for flashing Hyperdrive and it's working fine. Imagine that! All i had to do was read the instructions.
swing4thefence said:
Your right. I "Just flashed" I Odined back to stock and tried again, this time following the isntructions for flashing Hyperdrive and it's working fine. Imagine that! All i had to do was read the instructions.
Click to expand...
Click to collapse
That usually helps ; )

[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

Bricked?? Stuck at samsung logo screen for 1 sec then reboots.

Okay, So the title pretty much says it all. I am stuck at the Samsung boot logo (not bootanimation) and it only shows for about 1 second then reboots and continues.
This started after I tried to flash a rom and it messed up and I tried to flash via odin. I was on MJ9 and and got a bootloop so I did the odin thing. I've used odin before but it is not working well for me now.
I am able to boot into download mode but TWRP no longer works. I was able to flash via odin and it says success but the phone does not reboot like it should.
I have purchased a galaxy nexus on the cheap to hold me over until the nexus 6 is out but if I can fix my note, I would like to.
I know there were other threads about this same issue but it seems that they are all on a different version of the note, or on a s3 or something. Not to mention, I don't see anything that I could try without asking for some help on here. Can someone maybe point me in the direction of the factory firmware (preferably a rootable or already rooted version) that I can flash that will play well with my note.
Thanks guys!!!
amberkalvin said:
Okay, So the title pretty much says it all. I am stuck at the Samsung boot logo (not bootanimation) and it only shows for about 1 second then reboots and continues.
This started after I tried to flash a rom and it messed up and I tried to flash via odin. I was on MJ9 and and got a bootloop so I did the odin thing. I've used odin before but it is not working well for me now.
I am able to boot into download mode but TWRP no longer works. I was able to flash via odin and it says success but the phone does not reboot like it should.
Click to expand...
Click to collapse
Before you tried to flash a custom ROM and things went wonky...were you on Verizon's factory stock 4.3 MJ9 firmware, or on Beanstown106’s modified 4.3 MJ9 with TWRP installed?
Does the phone still boot into stock recovery? If so, you may be able to fix the phone by doing a factory reset.
amberkalvin said:
Can someone maybe point me in the direction of the factory firmware (preferably a rootable or already rooted version) that I can flash that will play well with my note.
Click to expand...
Click to collapse
If you were on Verizon's factory stock 4.3 MJ9, then you won't be able to Odin flash back to 4.1.2 or any earlier Android version because the bootloader has been locked down tight on 4.3 (and 4.4.2) with no current do it yourself method to unlock for those newer versions. You would want to restore the phone back to factory stock 4.3 though, if that's what version you were on before your phone got messed up. You can root the phone on 4.3 with saferoot, then use safestrap recovery to flash some custom Touchwiz ROM's.
If you were on the 4.1.2 based bootloader, (but running Beanstown106’s MJ9 firmware and TWRP), then you would want to restore your phone back to factory stock 4.1.2 and then root and unlock the bootloader again with CASUAL. This would give you the most flexibility with flashing custom kernels, ROM's, etc...
Check out Section 1b in Droidstyle's restore guide at this link: http://forum.xda-developers.com/showthread.php?p=34891181. The guide has download links for the files you'll need to restore the phone back to the correct build version.

[Q] Bricked S4 No OS, (I think?) NK1 with SS installed

Well here's the story..... So I want to install a custom ROM via SS, the install goes without issue. (I'm running stock NK1 Rooted at the time) I go to install a ROM , and It fails, so I go to reboot the device, and Its back into a bootloop. No big deal, iv'e delt with this before... .I attempt to flash it back to stock NC5 to root it and start over, the flash succeeds, but when I try to boot it i just get the "Samsung Galaxy S4" logo and it sits there doing nothing, and I cant boot into recovery for some reason, just goes back to ODIN mode. Is there anything that can be done?
Alex_Tisler said:
Well here's the story..... So I want to install a custom ROM via SS, the install goes without issue. (I'm running stock NK1 Rooted at the time) I go to install a ROM , and It fails, so I go to reboot the device, and Its back into a bootloop. No big deal, iv'e delt with this before... .I attempt to flash it back to stock NC5 to root it and start over, the flash succeeds, but when I try to boot it i just get the "Samsung Galaxy S4" logo and it sits there doing nothing, and I cant boot into recovery for some reason, just goes back to ODIN mode. Is there anything that can be done?
Click to expand...
Click to collapse
Try a reflash via Odin. It may help. Which image are you flashing?
Sent from the gap between universes.

S7 ATT

So I have an att s7 930u,
I installed the echo rom on it
http://forum.xda-developers.com/att-galaxy-s7/development/echoeromg935-g930multi-carrier-t3459277/
and I would like to install xposed framework on my device. tried many times but got bootloops. Also after installing the rom , my device now says 935 for the model number so im a little confused.
thx
just make sure you have a clean install of the echoe rom (meaning no left over files from other roots and flashes) I would just to make sure do a clean odin flash of the stock files then re-root and flash echoe all over again. Once you have everything set up just go to this page: http://forum.xda-developers.com/ver...-to-notes-root-install-xposed-unroot-t3411039 and then click on the install xposed instructions and follow it exactly. It takes a while for the phone to boot after flashing the rom so its not a boot loop if it takes 10 or 15 minutes.
Which version of Xposed are you using?

Categories

Resources