I have a AT&T Samsung S4 SGH-I337 NC1.
I rooted my phone and then I went into safestrap and backed up my phone. Then i installed Hyperdrive.
When i run hyperdrive the Wi-Fi doesn't work. (I think this is because there are no kernal modules available for NC1.)
So when i tried to restore to my rooted stock rom, the restore process always fails when it tries to restore the system files.
I think the backup is corrupted. When I researched Odin restores I found that you have to be in the stock rom which is not possible for me.
So what should i do I DO NOT WANT TO BRICK MY PHONE?
are there kernal modules available for my phone?
How can i get back to my stock rom?
PLEASE HELP!!!
All help is appreciated.
You need to just reflash the hyper Rom and then the modules.
Step 1; Get the kernel modules onto your micro sd card.
Suggestion; If you have an sd card just download them onto your pc then put them on the sd card. Then you can put the sd card back into the phone and proceed. I know the modules are in the op of the vision Rom thread.
Step 2; Boot into safestrap and reflash the Rom.
Step 3; Flash the kernel modules.
Reboot, wait at least 5 minutes and profit.
Good luck!
Sent from my i747 on T-Mobile that's getting awesome LTE speeds.
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?
I am currently on nc4 baseband version and i wanted to go back to my stock rom using safestrap version 3.75 (TWRP v2.7.1.0) When i activate stock rom and reboot, the phone stays on the verizon red screen with out any indication of doing anything. I have to take out the battery and load up to baja rom 15 or alliance rom v1 to get into phone. When i run stock rom the safestrap says its not active (is that normal?)
any help would be appreciated, first time android user.
Stock ROM won't load
Ok, I had this problem when I downgraded the kernel from nc4 to nc2 to load Biggins and Jasmine.
I just looked on Alliance, and the instructions do not say anything about downgrading. I am running Biggins, Jasmine, and Alliance. I lost my stock slot because many instructions tell you to load their ROM into stock slot, which NEVER worked for me! I did lose my stock install though. Try flashing the nc4 kernel with Odin.
This may help:
http://forum.xda-developers.com/showthread.php?t=2794918
If you have not flashed the nc2, I am not sure what is wrong. Let me know what you find out. All my slots work fine except stock, DO NOT overwrite stock if you can help it.
Oh boy, I really screwed this one up...
I purchased a used Note 3 from eBay, hoping to be able to root it after it arrived. Much to my surprise, it arrived rooted with Safestrap, Hyperdrive ROM in Stock slot, and a different Hyperdrive ROM in Slot1. I was also impressed that KNOX had not been tripped. (It said Custom, but the KNOX flag showed 0x00)
Sweet looking phone in hand, I was thrilled! I wasn't going to have to cut my teeth on rooting the device myself prior to having an opportunity to explore a rooted Android and a custom ROM. The very first thing I did was to use Safestrap to backup both the Stock slot and Slot1. After the backups, I booted the stock slot first, to see how a factory Note 3 should look. Surprise again, the stock slot booted a Hyperdrive ROM. I was a bit nervous that I didn't have a truly stock ROM, but wasn't too worried about it because I had no plans to resell or seek repairs under warranty.
I then spent a couple of days tinkering with the device. Unfortunately, half asleep during the wee hours of the morning, I was tinkering around with SuperSU -- setting grant/deny/prompt flags for different apps. Somewhere in the midst of that, SuperSU informed me that I had lost root. I checked with RootChecker, and sure enough NO Root.
Things got worse from there, as I'm sure you can imagine. RootChecker had a button to relaunch SuperSU, so I tapped it. This time, SuperSU wanted to re-install itself. Being the ignorant noob that I am, I told SuperSU to proceed, and crossed my fingers. After a few seconds of thrashing around, SuperSU wanted to reboot, so I said okay...
Now the device attempts to go into recovery, reboots itself, attempts recovery, reboots, again, and again... boot loop... and no way to charge the battery... I believe I am around 55% to 60% charged at the moment.
So I read great things about Odin and downloaded a copy -- not yet sure exactly what I was going to do with it. I have been trying to wrap my head around this for a couple of days now, but I have several questions that I hope somebody can shed some light on.
Does the rooting take place in the boot image, or in the ROM image? I am assuming it has to be in the boot image, but then I've heard you can have rooted and unrooted ROMs in different slots.
If I use Odin to flash fresh firmware, will this firmware will have a functional recovery tool bundled with it?
Since the phone is no longer rooted, the recovery will not be able to re-flash a ROM onto the device?
If an Odin installed recovery can't re-flash a ROM due to being unrooted, am I faced with JTAG options only?
If I were to use Odin to flash this firmware: http://forum.xda-developers.com/showthread.php?t=2726558 , could I perhaps get SafeStrap back and be able to restore the backups I made? The links on that page appear to be to the same (or very similar) firmware that was running prior to this disaster. NC2, Safestrap, etc.
If I can't use Odin to flash the firmware linked in the previous paragraph, and get Safestrap to restore my backups, can I use the firmware, ROMs, and PIT file linked here: http://forum.xda-developers.com/showthread.php?t=2576104 to restore the phone to factory conditions and re-root from there?
Finally, is there any way for me to avoid tripping KNOX at this point? I'm not really sure I care if it gets tripped, but if I can avoid it then I probably should. Am I likely to need KNOX container support on a private device in the near future? Is there any other reason to be spooked about losing KNOX? I really don't care much about the warranty.
Any help with this mess will be **greatly** appreciated!
lintex said:
If I were to use Odin to flash this firmware: http://forum.xda-developers.com/showthread.php?t=2726558 , could I perhaps get SafeStrap back and be able to restore the backups I made? The links on that page appear to be to the same (or very similar) firmware that was running prior to this disaster. NC2, Safestrap, etc.
Click to expand...
Click to collapse
Ok, if anybody comes across this thread looking for answers -- I did successfully use Odin to get this firmware back onto the device. Upon booting, I had Safestrap, was able to boot Slot1, and had root. When I boot from the Stock slot, still no root.
I have not yet attempted to restore the Stock slot backup, because I first want to see if I can boot Slot1 (to get root), and then find/mount the Stock slot image and see if I can find a way to re-root it manually.
lintex said:
Ok, if anybody comes across this thread looking for answers -- I did successfully use Odin to get this firmware back onto the device. Upon booting, I had Safestrap, was able to boot Slot1, and had root. When I boot from the Stock slot, still no root.
I have not yet attempted to restore the Stock slot backup, because I first want to see if I can boot Slot1 (to get root), and then find/mount the Stock slot image and see if I can find a way to re-root it manually.
Click to expand...
Click to collapse
Using any other slot other then stock is going to be problematic. So use the stock slot. You are using the nc2 firmware if you have the reboot to recovery bootloop issue. You can flash the nc4 patched firmware in beans firmware thread if you want. Reboot to recovery is not the same as reboot to safestrap. Download a fresh rom. Wipe everything but external sd under the advanced wipe button in safestrap. Flash your new rom making sure stock slot is the active slot. Setup phone like normal. Make a backup with your now freshly setup rom. Rinse and repeat for new roms. Label your backups if you want to rom jump. Always use stock slot. Odin the nc2 kernel if you have a blackscreen on first boot of a new rom.
RomsWell said:
Using any other slot other then stock is going to be problematic.
Click to expand...
Click to collapse
In my case, Slot1 is simply a rooted ROM that I can use when the Stock slot gets messed up. I have no desire or intent to tinker with Slot1. I consider it as an emergency tool only. It does seem to have an issue though. It never seems to want to power all the way down for some reason.
RomsWell said:
So use the stock slot. You are using the nc2 firmware if you have the reboot to recovery bootloop issue. You can flash the nc4 patched firmware in beans firmware thread if you want. Reboot to recovery is not the same as reboot to safestrap.
Click to expand...
Click to collapse
I am using the NC2 firmware, but I no longer have the bootloop problem. After using Odin to re-install the NC2 firmware from BeansTown, the device was once again able to boot to Safestrap. From there, I was able to select and boot either of the existing slots. Slot1 still boots to root, Stock slot is still unrooted. I should be able to use Safestrap to restore my Stock slot backup and regain root on Slot1, right?
The only reason I have not yet attempted to restore the Stock slot backup is because I hope to boot my rooted Slot1 ROM, mount the Stock ROM image, and fix the Stock ROM image. If not, then I will try to restore the Stock slot backup.
RomsWell said:
Download a fresh rom. Wipe everything but external sd under the advanced wipe button in safestrap. Flash your new rom making sure stock slot is the active slot.
Click to expand...
Click to collapse
I definitely plan to flash a new ROM, soon. I want a fresh clean ROM for personal use, and I also need to find a ROM that supports HDMI -- because I want to get Debian to display on a larger screen. My ultimate goal is to create my own ROMs. I have a bit of experience with kernel tweaking/building, and created a bootable Linux-based DVD image by hand. I believe I will someday be able to tweak phone ROMs as well, but I'm still fuzzy about much of the Android system. Stuff like locks and KNOX seem like quite a mine field and make me very nervous. A blank DVD coaster is one thing, an expensive smartphone is scary.
lintex said:
In my case, Slot1 is simply a rooted ROM that I can use when the Stock slot gets messed up. I have no desire or intent to tinker with Slot1. I consider it as an emergency tool only. It does seem to have an issue though. It never seems to want to power all the way down for some reason.
I am using the NC2 firmware, but I no longer have the bootloop problem. After using Odin to re-install the NC2 firmware from BeansTown, the device was once again able to boot to Safestrap. From there, I was able to select and boot either of the existing slots. Slot1 still boots to root, Stock slot is still unrooted. I should be able to use Safestrap to restore my Stock slot backup and regain root on Slot1, right?
The only reason I have not yet attempted to restore the Stock slot backup is because I hope to boot my rooted Slot1 ROM, mount the Stock ROM image, and fix the Stock ROM image. If not, then I will try to restore the Stock slot backup.
I definitely plan to flash a new ROM, soon. I want a fresh clean ROM for personal use, and I also need to find a ROM that supports HDMI -- because I want to get Debian to display on a larger screen. My ultimate goal is to create my own ROMs. I have a bit of experience with kernel tweaking/building, and created a bootable Linux-based DVD image by hand. I believe I will someday be able to tweak phone ROMs as well, but I'm still fuzzy about much of the Android system. Stuff like locks and KNOX seem like quite a mine field and make me very nervous. A blank DVD coaster is one thing, an expensive smartphone is scary.
Click to expand...
Click to collapse
As long as you stick to the known exploits like safestrap and towelroot then theres no worrys about knoxs. And no real way to perma brick the device. Make sure you stick to offical firmware when using odin and abuse your device like you would any other.
Hey All,
I have been out of the scene for a number of months now, and I'm trying to get my S4 back to life on a custom rom (Goldeneye happens to be my pick).
Currently, my S4 is running Android 5.0.1 on what I believe is a stock rooted rom. Safe-Strap IS installed, and I've been using the NC1 Flasher method to get back into Safe-Strap.
Inside of the GE thread, in the Q&A Section, there is a link for "AT&T SAFESTRAP USERS ONLY!!" , which describes a process of using the NC1 flasher to get into Safe Strap, installing GE with all of the 'SafeStrap' options, then flashing modules. Followed by ODIN'ing two files for the Stock Kernal / Partitions.
Trouble is, after following the above steps to (what I believe was) a T, My phone just boots back into my stock rooted ROM as if nothing happened.
The only thing I can consider, is that when I'm in SafeStrap, am I supposed to use a ROM slot, or just the default slot? The last time I used SafeStrap, the purpose was to keep your stock rom intact. Is that not the case on the S4?
Siiig said:
Hey All,
I have been out of the scene for a number of months now, and I'm trying to get my S4 back to life on a custom rom (Goldeneye happens to be my pick).
Currently, my S4 is running Android 5.0.1 on what I believe is a stock rooted rom. Safe-Strap IS installed, and I've been using the NC1 Flasher method to get back into Safe-Strap.
Inside of the GE thread, in the Q&A Section, there is a link for "AT&T SAFESTRAP USERS ONLY!!" , which describes a process of using the NC1 flasher to get into Safe Strap, installing GE with all of the 'SafeStrap' options, then flashing modules. Followed by ODIN'ing two files for the Stock Kernal / Partitions.
Trouble is, after following the above steps to (what I believe was) a T, My phone just boots back into my stock rooted ROM as if nothing happened.
The only thing I can consider, is that when I'm in SafeStrap, am I supposed to use a ROM slot, or just the default slot? The last time I used SafeStrap, the purpose was to keep your stock rom intact. Is that not the case on the S4?
Click to expand...
Click to collapse
I'm pretty sure only the stock slot will work. I haven't tried a ROM slot for a very long time, but have run many custom ROMs in the stock slot without issue. Good luck.