Sup you guys,
I may be in a new predicament for myself, so I would like to ask a few questions before I tackle this task. It seems that I've flashed a JB rom on the stock slot of SS, and I thought that I had the NC2 kernel intact to do so. However, all I get is a black screen and then a botched up system partition, a soft brick if you will, on the stock slot. Couldn't mount the system, so wiping anything is out the window. In order to make my phone usable for now, I had to install a rom on Slot 1. All is fine, but the battery drain is a killer, so I would like recover the system partition of the stock slot. Now, I've read a few threads that kind of pertains to my situation and I learned that a pit file flash can recover it back to normal. Can I just flash only the pit through Odin, or are there other steps that I have to do to get this back on track? Any help and guidance would be greatly appreciated.
I need help too
krazyg said:
Sup you guys,
I may be in a new predicament for myself, so I would like to ask a few questions before I tackle this task. It seems that I've flashed a JB rom on the stock slot of SS, and I thought that I had the NC2 kernel intact to do so. However, all I get is a black screen and then a botched up system partition, a soft brick if you will, on the stock slot. Couldn't mount the system, so wiping anything is out the window. In order to make my phone usable for now, I had to install a rom on Slot 1. All is fine, but the battery drain is a killer, so I would like recover the system partition of the stock slot. Now, I've read a few threads that kind of pertains to my situation and I learned that a pit file flash can recover it back to normal. Can I just flash only the pit through Odin, or are there other steps that I have to do to get this back on track? Any help and guidance would be greatly appreciated.
Click to expand...
Click to collapse
I just got into ROMs and safeatrap and such. I started by trying to load them to the stock slot, which failed every time. I then made slots and had 3 ROMs, but the battery life was not good.
So I wanted to put a ROM on the stock slot. This is with nc2 on kitkat. When I went to load a ROM in stock slot, safestrap failed saying it couldn't mount /system. I tried wiping, but there too it said fail to mount /system.
I did "Fix Permissions" and rebooted. I was greeted by the Samsung boot screen, but it froze there. No safestrap, nothing. I recovery booted and the stock recovery says "E:failed to mount /system (Invalid argument)"
So now it seems that no part of my phone can get to /system. I will look into a .pit file and would appreciate guidance as well.
Seems like you have the problem that I had a week ago. I fixed it by flashing a stock tar and the pit file through Odin. Though I wasn't too sure if just flashing pit would repair the system partition (though, I think it would've been fine; I should've just done it with no questions asked), but in my situation, I got a bit more desperate as my problem got sort of worse. Yea, running any rom on any slot other than the stock slot will kill your battery quick. So a reminder, if you have a messed up system partition, do not let the battery die because your phone will be soft bricked and you won't be able to boot up to anything other than Download mode. At that point, I just flashed the stock tar and the pit file just to be on the safe side and start over. After I rooted and installed SS, I went and checked if it was working properly. It did for the most part, but I remember that I was still on slot 1 before my battery died and SS was highlighted that I was still on that slot. I think because of that, it gave me certain errors on some of things I was testing out, but you will be able to install normally on the stock slot again. There are some other issues I have because of that ordeal, but it's not game breaking, so make sure that you're on the stock slot before flashing the files through Odin.
krazyg said:
Seems like you have the problem that I had a week ago. I fixed it by flashing a stock tar and the pit file through Odin. Though I wasn't too sure if just flashing pit would repair the system partition (though, I think it would've been fine; I should've just done it with no questions asked), but in my situation, I got a bit more desperate as my problem got sort of worse. Yea, running any rom on any slot other than the stock slot will kill your battery quick. So a reminder, if you have a messed up system partition, do not let the battery die because your phone will be soft bricked and you won't be able to boot up to anything other than Download mode. At that point, I just flashed the stock tar and the pit file just to be on the safe side and start over. After I rooted and installed SS, I went and checked if it was working properly. It did for the most part, but I remember that I was still on slot 1 before my battery died and SS was highlighted that I was still on that slot. I think because of that, it gave me certain errors on some of things I was testing out, but you will be able to install normally on the stock slot again. There are some other issues I have because of that ordeal, but it's not game breaking, so make sure that you're on the stock slot before flashing the files through Odin.
Click to expand...
Click to collapse
Thanks for the reply. I flashed a stock tar last night since the stock bootloader couldn't mount /system. Not sure which slot was selected in safestrap, I couldn't get back in because it would freeze before safestrap.
I did not use a .pit file (FYI), and am now back on stock ROM.
What I woluld like isto flash a custom ROM, say a debloated, rooted ROM with ODIN. I see they are all zips with folders, not .tar. Maybe I could take out the recovery.img and put it into a ROM's zip and save the zip as a tar and flash it? Would this possibly break my device if it tried to flash a wrong recovery? I don't know.
If anyone has some knowledge of these things, I would appreciate tips.
Why wouldn't you towel root, install SS, and install a ROM?
xdadevnube said:
Why wouldn't you towel root, install SS, and install a ROM?
Click to expand...
Click to collapse
Because I have only been able to get ROMs working on slots 1-4 of SS and not stock slot, so the battery life is terrible. Also, it would be faster and easier just to flash a ROM with ODIN and not have to worry if my version of android has a working root method (thankfully towelroot v3 worked).
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 need help. lol. my Samsung note 3 is stuck in bootloop. I posted this in the thread for the hyperdrive rom because its what I was trying to flash.
i wiped and flashed in the stock slot. and now im stuck in the bootloop problem. it says recovery booting in the upper left of the screen and just keeps rebooting. I tried going in to odin and reloading the "n900v kk firmware" and nothing. anyone know a fix for this. is there something I can download to flash to fix this. I know I will have to use odin, just not sure what.
donelam304 said:
I need help. lol. my Samsung note 3 is stuck in bootloop. I posted this in the thread for the hyperdrive rom because its what I was trying to flash.
i wiped and flashed in the stock slot. and now im stuck in the bootloop problem. it says recovery booting in the upper left of the screen and just keeps rebooting. I tried going in to odin and reloading the "n900v kk firmware" and nothing. anyone know a fix for this. is there something I can download to flash to fix this. I know I will have to use odin, just not sure what.
Click to expand...
Click to collapse
Hi I'm kinda new to the community and Android, but I'll try to help. I've been having issues trying to use safestrap to install my custom roms. I know that 3.72 had issues with the extra slots. That was supposed to be fixed in 3.75. In short I haven't reached a loop but have had to flash to stock several times with Odin. I had to remove my battery to get the phone in "power off" mode. From there, I booted to download for odin (assuming you can get it to boot to download-volume down/home/power buttons to get there).
Once I got there, I just made sure I had the firmware version I wanted to go back to, plugged it into odin and bam! Back to stock to start over.
Bryotch said:
Hi I'm kinda new to the community and Android, but I'll try to help. I've been having issues trying to use safestrap to install my custom roms. I know that 3.72 had issues with the extra slots. That was supposed to be fixed in 3.75. In short I haven't reached a loop but have had to flash to stock several times with Odin. I had to remove my battery to get the phone in "power off" mode. From there, I booted to download for odin (assuming you can get it to boot to download-volume down/home/power buttons to get there).
Once I got there, I just made sure I had the firmware version I wanted to go back to, plugged it into odin and bam! Back to stock to start over.
Click to expand...
Click to collapse
I can boot in to the download mode. has no problem. even tried flashing the n900v_kk_firmware.tar.md5 tar,
ALL_N900VVRUBMJE_N900VVZWMJE_2106277_REV03_user_low_ship_MULTI_CERT.tar.md5
and even tried the N900VVRUCNC4_N900VVZWCNC4_N900VVRUCNC4_HOME.tar.md5
and when I do the MJE one it says invalid. am I flashing the wrong file is there something else I should be using. when I get in to manual mode after it boots in to manual recovery mode it says im on NC4. it says in the upper left corner the following:
Android stem recovery <3e>
KOT49H.N900VVRUCNC
volume up/down to move highlight;
power button to select.
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
is there a way to flash safestrap or CWM in odin.
donelam304 said:
I can boot in to the download mode. has no problem. even tried flashing the n900v_kk_firmware.tar.md5 tar,
ALL_N900VVRUBMJE_N900VVZWMJE_2106277_REV03_user_low_ship_MULTI_CERT.tar.md5
and even tried the N900VVRUCNC4_N900VVZWCNC4_N900VVRUCNC4_HOME.tar.md5
and when I do the MJE one it says invalid. am I flashing the wrong file is there something else I should be using. when I get in to manual mode after it boots in to manual recovery mode it says im on NC4. it says in the upper left corner the following:
Android stem recovery <3e>
KOT49H.N900VVRUCNC
volume up/down to move highlight;
power button to select.
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
is there a way to flash safestrap or CWM in odin.
Click to expand...
Click to collapse
You're running the same build I have, been having similar issues. I used Odin no completely repartition and wipe the phone. I used N900VVRUCNC4_N900VVZWCNC4_N900VVRUCNC4_HOME.tar.md5 and the HLTE.pit file (for this build). In Odin You put the pit and md5 files in (.pit file in the PIT slot and md5 in the AP slot on Odin 3.09) This took me back to the KK NC4 build, granted, I lost alot of data but I didn't use a Nandroid backup either. This got me back to a functional device but i'm still having issues getting ANY custom roms to work. I did flash to NC2 kernel since then and still no luck. Let me know if that helps. I can get the files I used if you can't find them, but most everything came from xda.
PS. you can find some firmwares with recovery and other things added. I avoided these just to make sure I could get back to stock. I use Towelroot, BusyBox, SuperSU, and Safestrap 3.75 b04
Bryotch said:
You're running the same build I have, been having similar issues. I used Odin no completely repartition and wipe the phone. I used N900VVRUCNC4_N900VVZWCNC4_N900VVRUCNC4_HOME.tar.md5 and the HLTE.pit file (for this build). In Odin You put the pit and md5 files in (.pit file in the PIT slot and md5 in the AP slot on Odin 3.09) This took me back to the KK NC4 build, granted, I lost alot of data but I didn't use a Nandroid backup either. This got me back to a functional device but i'm still having issues getting ANY custom roms to work. I did flash to NC2 kernel since then and still no luck. Let me know if that helps. I can get the files I used if you can't find them, but most everything came from xda.
PS. you can find some firmwares with recovery and other things added. I avoided these just to make sure I could get back to stock. I use Towelroot, BusyBox, SuperSU, and Safestrap 3.75 b04
Click to expand...
Click to collapse
i done a search on the stock firmware you mentioned and after about 2 dozen websites and and trying about 15 flashes I finally got it to work. this has been one heck of a day. I finally got it to work. I am in the process of trying to get safestrap and stuff on it now. I already used towelroot to rot it. what version of safestrap do you recommend. I was told 3.72 was for KK. and 3.75 was for the Samsung galaxy S5.
donelam304 said:
i done a search on the stock firmware you mentioned and after about 2 dozen websites and and trying about 15 flashes I finally got it to work. this has been one heck of a day. I finally got it to work. I am in the process of trying to get safestrap and stuff on it now. I already used towelroot to rot it. what version of safestrap do you recommend. I was told 3.72 was for KK. and 3.75 was for the Samsung galaxy S5.
Click to expand...
Click to collapse
here is the link I found with all the carriers for the note 3
http://galaxynote3root.com/galaxy-note-3-repair/how-to-unroot-galaxy-note-3/
donelam304 said:
here is the link I found with all the carriers for the note 3
http://galaxynote3root.com/galaxy-note-3-repair/how-to-unroot-galaxy-note-3/
Click to expand...
Click to collapse
thanks so much by the way. I greatly appreciate the assistance.
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 really need some help guys! So frustrated!
I have a Samsung Galaxy S4 i337 using SafeStrap 3.75. I followed the guide PERFECTLY just as it says, I have flashed all the files I need to in Odin and still no boot. My baseband is a NB1 and I have followed the guide many many times to get it to the new OC3. Can anyone please help me out? This is the third time I have tried flashing the rom and then flashing the kernel along with the stock partitions and no boot. I know it takes longer than normal for the first boot but I left my phone sit for over an hour with no luck. I can't access SafeStrap after I flash the OC3 also to even get my phone back to working somewhat. The first initial boot after flashing everything it shows the [SafeStrap : Disabled] and then i click continue and it goes black then says the same thing and it does that about 5 times or so then just a black screen for over an hour. I'm having no luck
Brandon.Black said:
I really need some help guys! So frustrated!
I have a Samsung Galaxy S4 i337 using SafeStrap 3.75. I followed the guide PERFECTLY just as it says, I have flashed all the files I need to in Odin and still no boot. My baseband is a NB1 and I have followed the guide many many times to get it to the new OC3. Can anyone please help me out? This is the third time I have tried flashing the rom and then flashing the kernel along with the stock partitions and no boot. I know it takes longer than normal for the first boot but I left my phone sit for over an hour with no luck. I can't access SafeStrap after I flash the OC3 also to even get my phone back to working somewhat. The first initial boot after flashing everything it shows the [SafeStrap : Disabled] and then i click continue and it goes black then says the same thing and it does that about 5 times or so then just a black screen for over an hour. I'm having no luck
Click to expand...
Click to collapse
Odin back any of the Kitkat kernels so you can get in to Safestrap, and make sure the stock partition file you're using is the correct .tar format. If you have a zip, that needs to be flashed in Safestrap along with the ROM and modules. Then you can ODIN the kernel and start again. If it is the correct .tar format, then make sure you let the phone flash the kernel, reboot, and wait for ODIN to say pass.
DeadlySin9 said:
Odin back any of the Kitkat kernels so you can get in to Safestrap, and make sure the stock partition file you're using is the correct .tar format. If you have a zip, that needs to be flashed in Safestrap along with the ROM and modules. Then you can ODIN the kernel and start again. If it is the correct .tar format, then make sure you let the phone flash the kernel, reboot, and wait for ODIN to say pass.
Click to expand...
Click to collapse
I've followed everything to the tee. I've re-read the directions millions of times but it's not booting. I have absolutely no idea why on this earth it won't. I've charged my phone to a 100% so it's not my battery.. I've used ODIN and flashed all the needed files until the green light comes on and says "passed". SafeStrap flashes on and off but then right after its done doing that.. NOTHING, no Samsung Boot Logo or noises just a stupid black screen. My phone feels hot after I leave it sit for awhile but never comes on from there. I feel like I'm the only one having this problem, everyone seems to be getting it to work successfully but I'm doing EVERYTHING just as should. I've flashed many many Roms before and I'm completely stumped on this one.
So my brand new SD care went corrupt while I had a lot of programs running from it... By means of Link2SD app I put system files on there too and now I get
E:failed to mount /system (Invalid argument)
I can't seem to fix this problem and it doesn't seem that this problem arises very often because I have found nothing in searching. Any help would be great... I don't want to have to put a hammer to it and then call Asurion for a replacement..... but that does sound fun lol.
I have tried to Odin everything I have in my backups but not sure if any of those are actually the original rom. I have been trying to figure out how to Odin CM or TWRP on to it... or get them install in some form with out the APK. I saw something about them being able to fix the issue.
Have you tried using ODIN and flashing back to a fresh, stock ROM?
I forgot to put all that. I have tried to Odin everything I have in my backups but not sure if any of those are actually the original rom. I have been trying to figure out how to Odin CM or TWRP on to it... or get them install in some form with out the APK. I saw something about them being able to fix the issue.
Our phones do not support CM or TWRP because we have a locked bootloader. You are on a Verizon G900V, right?
Here's a link to a post with stock ROMs you can Flash via Odin. Choose the appropriate one for the version you want and Flash. Make sure you back up anythibg you want to save.
http://forum.xda-developers.com/showthread.php?t=2784880
It doesn't matter what I flash I get the same error. The other things I have found say that the system and/or EFS needs to be re-made so to speak. TWRP has a command that does it and CM allows you to go in though ADB and do it..... That is the best I have found for answers so far. I don't see anything for FlashFire or SuperUser.
Flash using ODIN not FlashFire or anything else.
I have flashed with Odin.... I get no where.... doesn't matter what kernel I use or ROM or anything.... I was saying that the people that have solved this porblem before are using CW or TWRP to access the ADB to send commands for the phone to re-setup the system/EFS
Did you Flash the pit file on the page I linked earlier? That should repartition everything.
Still the same problem
So I just kept flashing tar files from the post above and finally the NI2 took along with the pit file. Thanks for your help @btonetbone
Eventually the NI2 + .pit file being flashed together fixed the problem.