I'm trying to flash a ROM on a i337 S4 running 4.4.2 NB1, I have it rooted SuperSu installed and Safestrap custom recovery install. I boot into recovery create a new ROM slot (standard sized) flash ROM, flash NB1 modules, flash SuperSu (per ROM's instructions) then reboot. Now heres the problem, it will boot show Safestrap and the Samsung boot but right after that where you would normally see the AT&T boot or the ROM's boot it just goes black. Black screen nothing there no button press work nothing, I know the phones on because if I have it plugged into the computer through USB it will recognize it as an Android device. I let it sit for a good 10 minutes and nothing. Has happened on a couple different ROM's. The one I'm currently trying to flash in Empty Galaxy http://forum.xda-developers.com/showthread.php?t=2768183
Related
Hello,
I have a samsung galaxy s4 at&t on MF3. I rooted using the xda guide for MF3, and installed Safestrap 3.71 and TWRP 2.6.3.1.
Then I installed on ROM slot 1 several of the ROMs from this thread http://forum.xda-developers.com/showthread.php?t=2428254 including
Google Play Edition 4.2.2, Deadly Venom, SHOStock, Darth Stalker x1 but none seem to be working.
After installation is complete, I reboot on ROM slot 1, I see the Safestrap splash screen, then the screen turns black, the phone vibrates, and reboots again.Then it depends. I will see one of the following:
1. After the samsung logo with RECOVERY BOOTING in tiny blue letters on top, I see a recovery screen with a dead android that says "android system recovery <3e>" which gives me a few options (like reboot system, apply update from ADB etc). I have only chosen reboot, which is a regular reboot leading to the regular safestrap splash screen.
2. Samsung logo and regular boot, which leads to the safestrap splash screen.
What am I doing wrong? Are the ROMs I have tried not compatible with my phone?
I would appreciate any help.
thank you very much for the hard work!
Vassilis
Why flash TWRP? You already have safestrap, no need to flash a custom recovery that doesnt work on MF3.
Also have you flashed the MF3 module after flashing a rom?
pieta9999 said:
Hello,
I have a samsung galaxy s4 at&t on MF3. I rooted using the xda guide for MF3, and installed Safestrap 3.71 and TWRP 2.6.3.1.
Then I installed on ROM slot 1 several of the ROMs from this thread http://forum.xda-developers.com/showthread.php?t=2428254 including
Google Play Edition 4.2.2, Deadly Venom, SHOStock, Darth Stalker x1 but none seem to be working.
After installation is complete, I reboot on ROM slot 1, I see the Safestrap splash screen, then the screen turns black, the phone vibrates, and reboots again.Then it depends. I will see one of the following:
1. After the samsung logo with RECOVERY BOOTING in tiny blue letters on top, I see a recovery screen with a dead android that says "android system recovery <3e>" which gives me a few options (like reboot system, apply update from ADB etc). I have only chosen reboot, which is a regular reboot leading to the regular safestrap splash screen.
2. Samsung logo and regular boot, which leads to the safestrap splash screen.
What am I doing wrong? Are the ROMs I have tried not compatible with my phone?
I would appreciate any help.
thank you very much for the hard work!
Vassilis
Click to expand...
Click to collapse
Safestrap 3.71 is for mk2 builds. You are mf3 so you need 3.65. Safestrap is a modified TWRP flashing TWRP over it is needless & not going to help your phone. PLEASE READ! All this information is here on XDA for you. Plus horror stories of the uninformed who did as you & flashed 1st & asked questions later. Hopefully you made a backup before all this, if not, then there is a guide posted on here how to Odin back to stock mf3. Good luck.
John The Rhino said:
Safestrap 3.71 is for mk2 builds. You are mf3 so you need 3.65. Safestrap is a modified TWRP flashing TWRP over it is needless & not going to help your phone. PLEASE READ! All this information is here on XDA for you. Plus horror stories of the uninformed who did as you & flashed 1st & asked questions later. Hopefully you made a backup before all this, if not, then there is a guide posted on here how to Odin back to stock mf3. Good luck.
Click to expand...
Click to collapse
Thank you much for the prompt reply.
My phone boots fine the Stock ROM and works fine on the Stock ROM. Can I just install the right Safestrap version (3.65) after I boot the Stock ROM, and take things from there? or do I need to Odin to stock necessarily?
Thank you very much
Kaze105 said:
Why flash TWRP? You already have safestrap, no need to flash a custom recovery that doesnt work on MF3.
Also have you flashed the MF3 module after flashing a rom?
Click to expand...
Click to collapse
Thanks for prompt response. To clarify, I only installed Safestrap 3.71. I did not flash TWRP myself. I only mentioned the TWRP version that was inlcuded with Safestrap in case this was important for your answer.
I have tried flashing MF3 module after each rom with no luck.
Based on the response of another fellow, I think what I did wrong was installing the wrong safestrap version.
pieta9999 said:
Thank you much for the prompt reply.
My phone boots fine the Stock ROM and works fine on the Stock ROM. Can I just install the right Safestrap version (3.65) after I boot the Stock ROM, and take things from there? or do I need to Odin to stock necessarily?
Thank you very much
Click to expand...
Click to collapse
Whew, so glad your phone is fine. Yes, install Safestrap 3.65 then you can flash the mf3 custom rom of your choice in Safestrap recovery. Remember, Safestrap will always show as disabled on stock rom & active on a custom rom slot. Be sure to read & follow the rom developers install instructions. Safestrap has worked flawlessly for me. Don't forget to thank Hascode for his brilliant work.
Hi all,
Working with a AT&T NC1 safestrap phone. Having problems getting any custom rom to boot. Phone usually shows white on black Samsung logo for a few second then restarts, sometimes into stock recovery.
Detailed below is my method, and methods tried with same result. Perhaps someone can see the error of my ways.
I have been trying to start fresh.... so:
1) Odin I337UCUFNB1_TWRootable_Full_Odin.tar.md5
2) Do not boot, Download mode and flash 2400258.zip
3) Install tr, and SS 3.72
4) Reboot into recovery, install Hyperdrive 18.1 or Gravitron S4 3.2 for SS, then flash SuperUser then NC1 module.
No matter what, I cannot get a rom to boot. Just hangs at Samsung logo
Other methods tried:
1) Using I337_NB1toNC1_KeepRoot_OTA.zip and/or I337_NB1toNC1_KeepRoot_OTAwBL.zip to flash to NC1 before custom rom (after Odin NB1) (instead of 2400258.zip)
2) Using NB1 Odin Files from Magic Tool BL,AP,CP before flash of custom rom, tried also after flashing custom rom
3) flashing NB1 stock kernel
4) flashing NC1 stock kernel
Tried maybe 30 or 40 times, cannot get a custom Rom to boot. To be clear, stock boots just fine whenever i Odin back and upgrade to NC1.
Anyone out there insightful enough to lend a hand? More detailed instructions than on INDEX ALL THINGS POST? See my mistake? Losing my mind just a little bit, flashing the days away...
Any help greatly appreciated!
Are you trying to flash a custom ROM in the STOCK slot? Or a second slot?
I do NOT have safestrap but I know I have read you HAVE TO flash Roms in the STOCK Slot for it to work.
RockRatt said:
Are you trying to flash a custom ROM in the STOCK slot? Or a second slot?
I do NOT have safestrap but I know I have read you HAVE TO flash Roms in the STOCK Slot for it to work.
Click to expand...
Click to collapse
Always stock.
ajoh99 said:
Always stock.
Click to expand...
Click to collapse
Is your ROM SafeStrap Compatible?
Yes indeed. Tried a variety of them off the safe strap compatible page. I feel there is something I am missing but not sure what. I have been wiping data, davliche, cache, and system each time. Is this correct?
ATT Galaxy S4 i337, MK2 firmware
I was able to successfully gain root via the saferoot method, and I installed safestrap from the APK.
I loaded a custom ROM, the ATT Modules, and SuperSu.zip onto my extSD card, booted into safestrap, made a ROM slot 1 with default settings, did a wipe, installed the ROM, installed the ATT Modules, installed SuperSu.zip, then booted into download mode, and attempted to flash the Deadly Venom KitKat Magic Tool files to my device, however Odin was not detecting my S4, so I attempted to reboot my phone to see if it would boot regardless of that step, however now my phone can not even boot into recovery mode, and just hangs at the first SAMSUNG screen
Relevant links:
http://forum.xda-developers.com/galaxy-s4-att/development/rom-google-edition-s4-t2837239
http://forum.xda-developers.com/showthread.php?p=53758259#post53758259
http://forum.xda-developers.com/showthread.php?p=51067706#post51067706
How can I save my device?
After trying another USB port, I was able to get the drivers to install correctly and Odin could now see my phone. installing the magic tool box items did not solve the issue, so I followed the instructions here:
http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642
to get my phone back to a stock ROM
Now that odin is behaving, I'll see if I can get safestrap and a custom rom working correctly now.
Hello all,
I am looking for some advice, on getting my AT&T Samsung Galaxy S4 working again. I will keep this as short as I can:
I originally had 4.3 rooted with the MK2 firmware, and used Odin to flash my phone to 4.4 NB1, using the ROM in the Guide to Stock/Updating/Rooting thread.
This worked fine, and I was able to boot and use the phone, but my root access was gone.
I tried Towelroot, Kingo, etc... to no success.
I then followed http://forum.xda-developers.com/showthread.php?t=2692825 thread to semi downgrade to MK2 and was able to obtain root again. I also installed Safestrap recovery.
At this point I could not successfully boot back into the phone, though I could access Safestrap.
I flashed the stock kernel for NB1 again, but still could not boot.
I then flashed the stock NB1 ROM again.
After this, the phone would show the android icon and a progress bar, then restart, reach the Samsung load screen, start the AT&T load screen and then boot loop.
Once I reached this point, I could no longer access recovery, only download mode.
In my attempts since then. I've found if I stop the phone from ever getting to the Samsung load screen after flashing the stock ROM, I can then access recovery. As soon as I let it boot, I cannot access recovery.
I've flashed the stock ROM multiple times at this point, gotten into recovery and wiped the devices then rebooted multiple times.
I just don't know what else I can do.
Does anyone have any ideas? A place to look? Any help appreciated!
Hi,
I tried to install CWM on my rooted Note 3 N9005 with the latest 5.0 updates and the default recovery kept overwriting the custom. So I followed the advice on an article to delete the files [/system/recovery-from-boot.p] [/system/etc/install-recovery.sh] an this made my phone to fall in a loop, booting and trying to find these files then rebooting and so on...
I then had no choice but to load the stock ROM via ODIN which fixed the loop.
Is there anyway to install a custom recovery on a Note 3 running 5.0 - I want to do this in order to continue and install a custom ROM.
Thanks in advance for the answers!!
Don't use cwm as it has not been updated for a long time. Download the latest tar version of twrp for your phone.
Open Odin, uncheck everything except f.reset time, flash twrp, when you see the word "reset" in the status window, remove the USB cable from the phone, remove the battery, wait about 5 seconds, replace battery, use button combination to boot into recovery.
Thank you!!
What did the trick was that I quickly removed the battery and went to recovery mode. Even with "Auto Reboot" deselected the phone rebooted so if I left it it would have overwritten again the custom recovery.
Just a quick note to help others... anyone trying to flash Darklord or Phronesis ROM... USE TWRP v.2.8.0 and not the latest. The latest version for some reason won't install the ROMs.
thanx this wad so heapful .
:fingers-crossed::good:
abod7070 said:
:fingers-crossed::good:
Click to expand...
Click to collapse
Could be a year out of date and in some respects it is .
KEY is roms with AROMA installer will not work above 2.8 TWRP .