Related
Hello, and thanks for reading this. I know it's long, but I wanted to be specific.
I got a brand new AT&T Galaxy S4 yesterday, and decided I wanted to run CM. I easily rooted using this
method, but ran into problems in multiple attempts to install CWM. I found out about the MF3 software version, which I have, so I installed safestrap.
In safestrap, I factory reset, installed CM 10.2-20131102.zip
snapshot, and then installed loki-doki.zip as mentioned in this thread (there were some mentions in the xda forums but I can't find the one I was looking at earlier.) The problem is I forgot to make
a new rom slot/partition thing, so I think I wrote over the stock rom.
Now, when I turn on the phone, an option for safestrap comes up. If I choose to not go through safestrap, the screen goes blank black, but the phone stays on until I
hold the power button and it vibrates, indicating a power down. Safestrap's recovery mode still works as expected.
What I've already tried:
1. Factory reset. Nothing changed.
2. Create rom slot for CM, install, and boot (Has since been uninstalled). Nothing changed.
3. manually put stock rom zip into phone. Computer did not recognize device.
4. Use adb to push same stock rom zip onto phone. ADB did not see device.
5. Change PIT via ODIN as per a thread I can no longer locate. Nothing changed.
6. Take a stock rom and flash it from ODIN (I used the PDA, then bootloader, option because I wasn't sure which to select.) Both failed.
Is this something y'all can help me with? What do I do? If you have any ideas, questions, comments, please ask. I know I need more information.
Thanks for the help.
FalseAim said:
Hello, and thanks for reading this. I know it's long, but I wanted to be specific.
I got a brand new AT&T Galaxy S4 yesterday, and decided I wanted to run CM. I easily rooted using this
method, but ran into problems in multiple attempts to install CWM. I found out about the MF3 software version, which I have, so I installed safestrap.
In safestrap, I factory reset, installed CM 10.2-20131102.zip
snapshot, and then installed loki-doki.zip as mentioned in this thread (there were some mentions in the xda forums but I can't find the one I was looking at earlier.) The problem is I forgot to make
a new rom slot/partition thing, so I think I wrote over the stock rom.
Now, when I turn on the phone, an option for safestrap comes up. If I choose to not go through safestrap, the screen goes blank black, but the phone stays on until I
hold the power button and it vibrates, indicating a power down. Safestrap's recovery mode still works as expected.
What I've already tried:
1. Factory reset. Nothing changed.
2. Create rom slot for CM, install, and boot (Has since been uninstalled). Nothing changed.
3. manually put stock rom zip into phone. Computer did not recognize device.
4. Use adb to push same stock rom zip onto phone. ADB did not see device.
5. Change PIT via ODIN as per a thread I can no longer locate. Nothing changed.
6. Take a stock rom and flash it from ODIN (I used the PDA, then bootloader, option because I wasn't sure which to select.) Both failed.
Is this something y'all can help me with? What do I do? If you have any ideas, questions, comments, please ask. I know I need more information.
Thanks for the help.
Click to expand...
Click to collapse
A few things...
CM will not work on SafeStrap as of right now, it's AOSP-based whereas SS currently only supports TouchWiz-based ROMs.
Is your stock ROM-slot intact, or did you flash over it as well? if so move on to the next bullet.
Your need to take these files and use ODIN to flash back to stock MF3 (I don't know what stock files your using) and start from scratch.
Alternatively, you can try to flash a TouchWiz-based ROM (look here) in a ROM-slot other then stock in SafeStrap and see if it works, just don't forget to flash the MF3 modules afterwards.
NighthawkXL said:
A few things...
CM will not work on SafeStrap as of right now, it's AOSP-based whereas SS currently only supports TouchWiz-based ROMs.
Is your stock ROM-slot intact, or did you flash over it as well? if so move on to the next bullet.
Your need to take these files and use ODIN to flash back to stock MF3 (I don't know what stock files your using) and start from scratch.
Alternatively, you can try to flash a TouchWiz-based ROM (look here) in a ROM-slot other then stock in SafeStrap and see if it works, just don't forget to flash the MF3 modules afterwards.
Click to expand...
Click to collapse
I really appreciate the help. I had no idea CM would not work with SafeStrap. Is it possible to get CWM through SafeStrap? If not, I'll just have to do some research to see if I want one of the TW-based ROMs, I've never looked into it before. Actually, just before you posted, I started the Odin flashing in this thread, which seems to be another thread pointing to the same file downloads written by the same guy as the thread you posted. The phone is back to perfect stock; no root, no SafeStrap, still MF3 software version. I'm going to reroot and reinstall SafeStrap, and not be so reckless this time. Thanks again for the help!
No CWM won't run on the locked MF3 bootloader. SafeStrap is "recovery" itself designed specifically for MF3 devices. Just use a TW Rom and br careful!
Sent from my SGH-I337 using Tapatalk
NighthawkXL said:
No CWM won't run on the locked MF3 bootloader. SafeStrap is "recovery" itself designed specifically for MF3 devices. Just use a TW Rom and br careful!
Sent from my SGH-I337 using Tapatalk
Click to expand...
Click to collapse
Do you think you could help me install a ROM? I tried to get GoldenEye, but it didn't work. I made a new ROM slot and didn't change any of the default sizes. Then I activated that ROM slot, wiped the data, and intalled the GoldenEye zip file from the /sdcard folder. The I rebooted, and installed the MF3 modules on the same ROM slot. Then I rebooted again, but all I got was a black screen. I was able to get back into SafeStrap and the stock ROM still works, but what did I do wrong installing GoldenEye?
I deleted and then remade the ROM slot, and tried installing the two files again without rebooting in between, but it didn't change anything. But I did notice the following when trying to install the MF3 modules:
Installing 'sdcard/jflteatt-MF3-modules.zip'..
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Updating partition details...
E:Unable to mount internal storage.
SafeStrap says "Successful," but this text doesn't sound like it. I couldn't find any in-depth tutorial on using SafeStrap, so I'm not sure what to try next.
Thanks for the help.
FalseAim said:
Do you think you could help me install a ROM? I tried to get GoldenEye, but it didn't work. I made a new ROM slot and didn't change any of the default sizes. Then I activated that ROM slot, wiped the data, and intalled the GoldenEye zip file from the /sdcard folder. The I rebooted, and installed the MF3 modules on the same ROM slot. Then I rebooted again, but all I got was a black screen. I was able to get back into SafeStrap and the stock ROM still works, but what did I do wrong installing GoldenEye?
I deleted and then remade the ROM slot, and tried installing the two files again without rebooting in between, but it didn't change anything. But I did notice the following when trying to install the MF3 modules:
Installing 'sdcard/jflteatt-MF3-modules.zip'..
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Updating partition details...
E:Unable to mount internal storage.
SafeStrap says "Successful," but this text doesn't sound like it. I couldn't find any in-depth tutorial on using SafeStrap, so I'm not sure what to try next.
Thanks for the help.
Click to expand...
Click to collapse
All of this is covered in the "SafeStrap" thread.
I have a Note 3 that I bought the day they where released so obviously I don't have the latest firmware.
I have safestrap installed (rooted with delavega). I have the stock but debloated ROM in the stock slot & Beans awesome ROM running in slot 1.
I have nandroid backups of both ROMs (on my 64gig card) and I have actually done a restore of both just to make 100% sure they worked.
I should probably leave well enough alone as EVERY SINGLE THING works perfectly in my slot 1 Beans setup but I'm still kinda on the fence about flashing the new firmware (my long time Wife once commented "you break things intentionally just so you can figure out how to fix them!!").
I have never had a phone that used safestrap so this is all new to me. My questions are:
1. I have downloaded the Odin flashable tar for the new firmware. If I flash this, does it wipeout safestrap/the ROM slots etc.(like formatting a windows hard drive) so it becomes basically a new stock phone unrooted and all the internal storage blank??
2. If that is the case, can I first flash the new firmware tar, then root with kingblo, then install safestrap/recreate ROM slot 1 and then restore the nandroid of my current Beans BU and be basically right back to where I am now but with the new firmware installed??
jmorton10 said:
I have a Note 3 that I bought the day they where released so obviously I don't have the latest firmware.
I have safestrap installed (rooted with delavega). I have the stock but debloated ROM in the stock slot & Beans awesome ROM running in slot 1.
I have nandroid backups of both ROMs (on my 64gig card) and I have actually done a restore of both just to make 100% sure they worked.
I should probably leave well enough alone as EVERY SINGLE THING works perfectly in my slot 1 Beans setup but I'm still kinda on the fence about flashing the new firmware (my long time Wife once commented "you break things intentionally just so you can figure out how to fix them!!").
I have never had a phone that used safestrap so this is all new to me. My questions are:
1. I have downloaded the Odin flashable tar for the new firmware. If I flash this, does it wipeout safestrap/the ROM slots etc.(like formatting a windows hard drive) so it becomes basically a new stock phone unrooted and all the internal storage blank??
2. If that is the case, can I first flash the new firmware tar, then root with kingblo, then install safestrap/recreate ROM slot 1 and then restore the nandroid of my current Beans BU and be basically right back to where I am now but with the new firmware installed??
Click to expand...
Click to collapse
I basically have the same set up as you except I’m running Hyperdrive. I just did this myself about an hour ago and didn’t lose anything. But I did and always make a backup before I do anything just in case.
1. Download Beans MJ7 Full Stock Tar: http://www.androidfilehost.com/?fid=23212708291674903
2. Make sure you boot into your “stock rom” before you Odin the stock tar. Latest Odin v.3.09: http://www.androidfilehost.com/?fid=23212708291676783
3. Odin the stock tar and when you’re done you’ll be un-rooted but on the MJ7.
4. Download and install the Kingo Root App to your PC and follow the instructions. LINK REMOVED BY VECTUS
5. After you re-root your phone and it reboots go back into safestrap or re-download it if it’s missing and reinstall the recovery. http://forum.xdadevelopers.com/showthread.php?t=2517610
Everything was still there for me when safestrap recovery booted up. I didn’t lose any data.
Good luck
Uhm. I don't think you're allowed to post links for Kingo.
Sent from my SM-N900V using Tapatalk
haza12d said:
Uhm. I don't think you're allowed to post links for Kingo.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Its not... I removed the link... :good:
Whoops you're right my mistake sorry about that.
Sent from my SM-N900V using xda premium
Is that app the only way to root the note 3 currently?
Thanks for the responses guys, it went like clockwork.
I Odin flashed the full mj7 tar that I downloaded from crack flashers (after beans like timed out on me about 25 times). Then immediately did the Kingo thing which worked super.
At that point, I installed the newest safestrap & recreated the same #1 ROM slot I had before the flash. I then restored a nandroid I had made of the Bean ROM install from that slot from before the Odin flash to that new ROM slot and it works perfectly.
I see no difference whatever except for the new firmware showing in the device properties.
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.
I need some serious help guys. Here's the scenario:
When installing a custom rom to my phone using Safestrap I put it on the stock slot on accident. Here's all my phone information:
Verizon S4
Sch-1545
Android 4.3
I545VRUEMK2
Kernel 3.4.0
Running Hyperdrive RLS15 on Safestrap 3.71 (?)
How do I go about restoring Verizon's stock rom onto the stock slot and having Hyperdrive on a different slot without bricking my phone? I've tried to think of this a million ways and so far have come to few conclusions as to how to make this work. Any guidance would be much appreciated.
Start from scratch. Reinstall the stock ROM via Odin, then do what you need to in order to get SafeStrap back onto the phone, then put the custom ROM in the correct slot.
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.