Related
So, I need to get back to pure stock, un-everything, however, I have a problem standing in my way:
I have SafeStrap installed (3.62 if I recall correctly), but I had to recover a bad install and now I can't even boot into SafeStrap anymore but the still boots into the Cyanogenmod ROM I installed. I have ME7 installed on my stock partition. Is there anyway I can force the phone to boot into SafeStrap, or boot into my stock partition, or update through Loki?
Edit: So I installed SafeStrap 3.65 and discovered that I recovered my Cyanogenmod install onto my stock ROM partition. Not sure if this is bad or not... :/
Edit 2: Okay... I found my old SD card with my original ME7 backup on it, so I'm back to that. Now I need to uninstall a bad Clockworkmod install because it's preventing me from updating.
spendle said:
So, I need to get back to pure stock, un-everything, however, I have a problem standing in my way:
I have SafeStrap installed (3.62 if I recall correctly), but I had to recover a bad install and now I can't even boot into SafeStrap anymore but the still boots into the Cyanogenmod ROM I installed. I have ME7 installed on my stock partition. Is there anyway I can force the phone to boot into SafeStrap, or boot into my stock partition, or update through Loki?
Edit: So I installed SafeStrap 3.65 and discovered that I recovered my Cyanogenmod install onto my stock ROM partition. Not sure if this is bad or not... :/
Edit 2: Okay... I found my old SD card with my original ME7 backup on it, so I'm back to that. Now I need to uninstall a bad Clockworkmod install because it's preventing me from updating.
Click to expand...
Click to collapse
odin you stock full wipe firmware
why did you install cyanogen mod with safestrap? you cannot do that lol.
but anyways. Yes use odin and use stock firmware tar to recover fully to stock.
Ok so i rooted my Me7 sch-1545 on 4.3 and installed Synergy rom with safestrap when it 1st released last fall (or whenever it was)
was moderately satisfied with this rom but by now i assumed there where better options so i decided on hyperdrive rls15.
so basically im an idiot and decided to operate off of what i remembered of how to flash a rom instead of reading anything (genius right?).
downloaded
Safestrap-JFLTEVZW-3.70-B01.apk from xda installed and then installed the updated recovery via app
rebooted opened safestrap recovery went though to system reboot and restarted my phone.
then proceeded to download
Hyperdrive RLS15 S4.zip
moved the zip to ext sd card then booted into recovery
so right here is where im pretty sure i bricked my phone :laugh::good:
selected install in recovery, selected the rls15 zip and drumroll.... selected the STOCK rom slot
went though the hyperdrive setup deleted cache and dalvik selected a few different options mostly left it as what was already checked.
agreed to terms etc and proceeded to install it everything was working well installation completed
selected to reboot
"samsung s4 splash screen"
then blackscreen with a "pulsating" dimming and brightening blue light left it like this for 20 minutes as it stated could take an extended amount of time on first boot
with no option of booting back into safestrap at any point
so after that wasnt doing anything opted to try out the stock recovery power home vol up
this method immediately takes me to odin mode
Odin mode
product name:sch 1545
current binary:samsung official
sytem statusfficial
csb-config-lsb: 0x30
write protection enabled
Downloading do not turn off target!!
and cannot access any other options
tldr: sch-1545 me7
flashed rls15 rom to stock rom slot in safestrap recovery
can no longer boot the phone or into safestrap or stock recovery only ODIN mode
So basically is she done for or do i have any options?
download mk2 odin flash. reinstall safestrap and install into a rom slot not stock. it will work just fine
thanks
evilryry said:
download mk2 odin flash. reinstall safestrap and install into a rom slot not stock. it will work just fine
Click to expand...
Click to collapse
trying this out now :victory:
my liege i am bound to thee
evilryry said:
download mk2 odin flash. reinstall safestrap and install into a rom slot not stock. it will work just fine
Click to expand...
Click to collapse
so help
much fix
wow
Hello,
What I’m trying to do
I’m looking for a step by step guide to help me flash the new HyperDrive RLS18.1 ROM on my Galaxy S4 currently running Hyperdrive RLS15.
I tried to figure it out on my own via google and youtube and a ton of websites but each set of instructions was more unclear than the last to me.
Reason why I want to change
I use the Verizon galaxy S4 (T-mobile is my network though) with Hyperdrive RLS15 and it has stopped being smooth. It’s now too choppy to use as a daily driver and I would like to do a fresh install (plus upgrade while I’m at it)
Experience with rooting
Moderate. I have installed a few ROMS in the past (on my S4 and a Note 1). However, I haven’t done this for some time and I can’t find a well written guide as to install this particular ROM that addresses the issue of whether I can do this via safestrap on an MJ7
Phone specs
• I used the phoneInfo app to check these
Model: SCH – I545
Device type: jfltevzw
Bootloader Version: I545VRUEMJ7
Baseband Version: I545VRUEMJ7
PDA version: I545VRUEMK2/ I545VRUEMK2a
CSC Version: I545VZWEMK2
Build Number: RLS15 (I545VRUEMK2)
Android version: 4.3
What I’ve downloaded so far
gogolies-wififix-VZW-FN2-NC2-w-modules-SS.zip
Hyperdrive+RLS18.1+KK+S4.zip
UPDATE-SuperSU-v1.94.zip
I545VRUFNC5_modem.zip
Questions I have:
How do I install the Hyperdrive 18.1 to my phone as-is, without bricking it?
I would appreciate a step-by-step guide, a link to a video, a link to an article or whatever. I can’t literally afford to brick this phone. Haha
Thank you.
T.
medic211987 said:
Hello,
What I’m trying to do
I’m looking for a step by step guide to help me flash the new HyperDrive RLS18.1 ROM on my Galaxy S4 currently running Hyperdrive RLS15.
I tried to figure it out on my own via google and youtube and a ton of websites but each set of instructions was more unclear than the last to me.
Reason why I want to change
I use the Verizon galaxy S4 (T-mobile is my network though) with Hyperdrive RLS15 and it has stopped being smooth. It’s now too choppy to use as a daily driver and I would like to do a fresh install (plus upgrade while I’m at it)
Experience with rooting
Moderate. I have installed a few ROMS in the past (on my S4 and a Note 1). However, I haven’t done this for some time and I can’t find a well written guide as to install this particular ROM that addresses the issue of whether I can do this via safestrap on an MJ7
Phone specs
•I used the phoneInfo app to check these
Model: SCH – I545
Device type: jfltevzw
Bootloader Version: I545VRUEMJ7
Baseband Version: I545VRUEMJ7
PDA version: I545VRUEMK2/ I545VRUEMK2a
CSC Version: I545VZWEMK2
Build Number: RLS15 (I545VRUEMK2)
Android version: 4.3
What I’ve downloaded so far
gogolies-wififix-VZW-FN2-NC2-w-modules-SS.zip
Hyperdrive+RLS18.1+KK+S4.zip
UPDATE-SuperSU-v1.94.zip
I545VRUFNC5_modem.zip
Questions I have:
How do I install the Hyperdrive 18.1 to my phone as-is, without bricking it?
I would appreciate a step-by-step guide, a link to a video, a link to an article or whatever. I can’t literally afford to brick this phone. Haha
Thank you.
T.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2301724
liljoe727 said:
http://forum.xda-developers.com/showthread.php?t=2301724
Click to expand...
Click to collapse
Thank you for the link. I read through and it says:
SAFESTRAP USERS MUST UPDATE TO BASE 4.4.2 FIRMWARE BEFORE FLASHING RLS16
1. Download latest Hyperdrive Rom version
2. Reboot into Safestrap
3. Must flash on stock slot with SS 3.72
4. Wipe Data/Factory Reset
5. Wipe cache and dalvik cache
6. Install Rom
7 Flash super su root zip
7. Flash Modules.zip in found safestrap thread(if needed) (not needed on rls18)
8. Reboot (First Boot may take up to 10 mins)
9. Let Phone sit for 10 minutes
10. Reboot again
11 Enjoy!
Question:
What does Base 4.4.2 firmware refer to? Does this mean i must have the stock Touchwiz 4.4.2 before i can use safestrap to install the RLS18.1?
Please help
medic211987 said:
Thank you for the link. I read through and it says:
SAFESTRAP USERS MUST UPDATE TO BASE 4.4.2 FIRMWARE BEFORE FLASHING RLS16
1. Download latest Hyperdrive Rom version
2. Reboot into Safestrap
3. Must flash on stock slot with SS 3.72
4. Wipe Data/Factory Reset
5. Wipe cache and dalvik cache
6. Install Rom
7 Flash super su root zip
7. Flash Modules.zip in found safestrap thread(if needed) (not needed on rls18)
8. Reboot (First Boot may take up to 10 mins)
9. Let Phone sit for 10 minutes
10. Reboot again
11 Enjoy!
Question:
What does Base 4.4.2 firmware refer to? Does this mean i must have the stock Touchwiz 4.4.2 before i can use safestrap to install the RLS18.1?
Please help
Click to expand...
Click to collapse
Go to settings/about device on your phone and see what Android Version you are on. If you are not on 4.4.2 then yes, you will need to update.
liljoe727 said:
Go to settings/about device on your phone and see what Android Version you are on. If you are not on 4.4.2 then yes, you will need to update.
Click to expand...
Click to collapse
I'm on RLS15 currently which means i'm on Android 4.3.
I'll download a stock Kitkat ROM and then follow the RLS18.1 instructions.
I hope that works.
Thanks a lot!
medic211987 said:
Thank you for the link. I read through and it says:
SAFESTRAP USERS MUST UPDATE TO BASE 4.4.2 FIRMWARE BEFORE FLASHING RLS16
1. Download latest Hyperdrive Rom version
2. Reboot into Safestrap
3. Must flash on stock slot with SS 3.72
4. Wipe Data/Factory Reset
5. Wipe cache and dalvik cache
6. Install Rom
7 Flash super su root zip
7. Flash Modules.zip in found safestrap thread(if needed) (not needed on rls18)
8. Reboot (First Boot may take up to 10 mins)
9. Let Phone sit for 10 minutes
10. Reboot again
11 Enjoy!
Question:
What does Base 4.4.2 firmware refer to? Does this mean i must have the stock Touchwiz 4.4.2 before i can use safestrap to install the RLS18.1?
Please help
Click to expand...
Click to collapse
Correct. Use Odin (I recommend 3.09) to flash either the full wipe or no wipe tar files here: http://forum.xda-developers.com/showthread.php?t=2735172
Then gain root using towelroot, install safestrap 3.72, and you're good to go.
joshm.1219 said:
Correct. Use Odin (I recommend 3.09) to flash either the full wipe or no wipe tar files here: http://forum.xda-developers.com/showthread.php?t=2735172
Then gain root using towelroot, install safestrap 3.72, and you're good to go.
Click to expand...
Click to collapse
Hello,
Thank you for the help so far. i used the link you provided to flash the stock ROM provided back onto my phone with Odin. But it's still at Android Version 4.3.
1. Can i go ahead with this stock ROM now, install towelroot, install safestrap 3.72 and then install Hyperdrive ROM RLS18.1?
2. Or do i have to upgrade to Stock 4.4.2/4.4.4 before i can flash HyperDrive ROM RLS18.1? If Number 2 is the case, would you be so kind as to give me a link for the Stock ROM 4.4.2/4.4.4 upgrade process + neccesary files?
Thank you for the help so far
T.
medic211987 said:
Hello,
Thank you for the help so far. i used the link you provided to flash the stock ROM provided back onto my phone with Odin. But it's still at Android Version 4.3.
1. Can i go ahead with this stock ROM now, install towelroot, install safestrap 3.72 and then install Hyperdrive ROM RLS18.1?
2. Or do i have to upgrade to Stock 4.4.2/4.4.4 before i can flash HyperDrive ROM RLS18.1? If Number 2 is the case, would you be so kind as to give me a link for the Stock ROM 4.4.2/4.4.4 upgrade process + neccesary files?
Thank you for the help so far
T.
Click to expand...
Click to collapse
Okay good, glad you got it going. Yeah you can use http://forum.xda-developers.com/showthread.php?t=2735172 these files to upgrade. Then use towelroot and SS 3.72, which is in the AT&T section.
Then search for the VZW NC5 modules by Surge 1223 and the NC2 wifi fix zip by Gogolie, flash the NC5 modules with the rom and if wifi or bluetooth isn't working flash gogolie's zip.
It also seems that safestrap users now need to flash the supersu.zip (Google it) with 4.4 roms to retain root.
If you can't find the links to anything, let me know.
EDIT: I just read the rest of your OP lol. Sorry [emoji5] I see you have all of that already. But make sure to find the NC5 modules not that modem zip. You're modem will be NC5 anyway once you flash the tar file in Odin.
I should also say, you'll probably have less issues if you back up important data to external storage and flash the full wipe version.
joshm.1219 said:
Okay good, glad you got it going. Yeah you can use http://forum.xda-developers.com/showthread.php?t=2735172 these files to upgrade. Then use towelroot and SS 3.72, which is in the AT&T section.
Then search for the VZW NC5 modules by Surge 1223 and the NC2 wifi fix zip by Gogolie, flash the NC5 modules with the rom and if wifi or bluetooth isn't working flash gogolie's zip.
It also seems that safestrap users now need to flash the supersu.zip (Google it) with 4.4 roms to retain root.
If you can't find the links to anything, let me know.
Click to expand...
Click to collapse
Ok thanks. I'll get going on this. I'll give you feedback as i go along.
Thank you!
T,
medic211987 said:
Ok thanks. I'll get going on this. I'll give you feedback as i go along.
Thank you!
T,
Click to expand...
Click to collapse
Just edited sorry didn't see you had most of the files already. Used to dealing with people who do no research whatsoever lol, thank you for trying before asking for help.
So my situation is virtually identical. I tried precisely what you suggested here, based off reading through ~700 replies on the Hyperdrive thread trying to figure out exactly the same. My experience went as follows:
Tried using the method described by Surge1223 here: http://forum.xda-developers.com/showthread.php?t=2726868 which failed to update to NC5, and subsequently prevented the phone from booting. Attempted the recovery instructions at the bottom of the post after getting the error about firmware and needing to use recovery mode in Kies. All files flashed successfully at the indicated time in the instructions, phone still wouldn't boot.
Found the MK2 full-wipe Odin image (http://forum.xda-developers.com/showthread.php?t=2578209) and was able to get that flashed and booted successfully. Still being on 4.3, I downloaded the NC5 full-wipe Odin image and flashed that on to make sure everything was stock and nothing was being carried over. Was able to get root, install SS, SuperSU, etc
Reboot to SS to do the ROM installation on the Stock slot and everything completes without issue. Flash SuperSU after and reboot....to a black screen. Instructions say let it sit 10 minutes. I let it sit 20, no joy. Reboot the phone and am greeted with the Samsung Galaxy S4 image, then Safestrap, then back to a black screen. Again, let it sit upwards of 20 minutes with no changes.
I've tried wiping system along with the other partitions before installing and I've tried leaving it. No difference.
I've tried 4 different kernel options with the Aroma installer. No difference.
I've tried as bare-bones as possible installation of Hyperdrive. No difference.
I got the SELinux permission changer and set it to permissive and tried to install. No difference.
Now I'm sitting on NC5, rooted stock image. I'm at my wits end for things to try to get Hyperdrive working. Suggestions?
Praetoriaxn said:
So my situation is virtually identical. I tried precisely what you suggested here, based off reading through ~700 replies on the Hyperdrive thread trying to figure out exactly the same. My experience went as follows:
Tried using the method described by Surge1223 here: http://forum.xda-developers.com/showthread.php?t=2726868 which failed to update to NC5, and subsequently prevented the phone from booting. Attempted the recovery instructions at the bottom of the post after getting the error about firmware and needing to use recovery mode in Kies. All files flashed successfully at the indicated time in the instructions, phone still wouldn't boot.
Found the MK2 full-wipe Odin image (http://forum.xda-developers.com/showthread.php?t=2578209) and was able to get that flashed and booted successfully. Still being on 4.3, I downloaded the NC5 full-wipe Odin image and flashed that on to make sure everything was stock and nothing was being carried over. Was able to get root, install SS, SuperSU, etc
Reboot to SS to do the ROM installation on the Stock slot and everything completes without issue. Flash SuperSU after and reboot....to a black screen. Instructions say let it sit 10 minutes. I let it sit 20, no joy. Reboot the phone and am greeted with the Samsung Galaxy S4 image, then Safestrap, then back to a black screen. Again, let it sit upwards of 20 minutes with no changes.
I've tried wiping system along with the other partitions before installing and I've tried leaving it. No difference.
I've tried 4 different kernel options with the Aroma installer. No difference.
I've tried as bare-bones as possible installation of Hyperdrive. No difference.
I got the SELinux permission changer and set it to permissive and tried to install. No difference.
Now I'm sitting on NC5, rooted stock image. I'm at my wits end for things to try to get Hyperdrive working. Suggestions?
Click to expand...
Click to collapse
Did MD5 match on the Hyperdrive download? Do you have busybox installed?
samsung galaxy s4 sch-1545 vzw
i tried to install a custom rom somthing wrong and now no phone
i can get into download mode but thats it. when i turn on the phone it tells me to connect
to kies to do a recovery but my device is not supported
i have tried to flash stock rom in odin but it fails everytime not sure what im doing wrong please help
porter46985 said:
samsung galaxy s4 sch-1545 vzw
i tried to install a custom rom somthing wrong and now no phone
i can get into download mode but thats it. when i turn on the phone it tells me to connect
to kies to do a recovery but my device is not supported
i have tried to flash stock rom in odin but it fails everytime not sure what im doing wrong please help
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2735172
Flash the full-wipe version in Odin.
Then if you want custom roms, follow my instructions:
First, obtain root. Go to your Settings/Security, check "allow installation from unknown sources". Go to www.towelroot.com , click on the lambda, install the towelroot.apk, then open it and hit "make it ra1n". After reboot, download SuperSU. Open it, it will prompt you to update binaries, do so using the "normal" option. Congrats, you're rooted.
The only custom recovery you can have on NC5 is Safestrap, no TWRP or CWM. You can only flash TW rom's and a select few GPE rom's. You need to use AT&T's 3.72 safestrap for kit kat rom's, which can be found here: http://forum.xda-developers.com/show....php?t=2448925
To install safestrap, first install busybox. Find it here: https://play.google.com/store/apps/d....busybox&hl=en
Then, change selinux status to permissive. Do this by using selinux mode changer: https://play.google.com/store/apps/d....selinux&hl=en
Now install the safestrap apk, open it and hit the install recovery button.
To flash a kit kat rom with SS 3.72, you must use the "stock" slot. ROM slots don't work. You can still make a backup of your stock rom incase anything goes wrong. Be warned, you should have Odin and an NC5 tar file ready to go at all times on your comp.
So, you install the rom like you normally do with TWRP or CWM. Wipe data, cache, dalvik cache, system. Then flash rom, modules, and SuperSU.
The NC5 modules are here: https://www.androidfilehost.com/?fid=23486521113837640
The SuperSU zip is here: http://forum.xda-developers.com/show....php?t=1538053
If you forget to flash SuperSU, you may lose root. You can still get it back by using towelroot. If Wifi isn't turning on, try going back into Safestrap and flashing this: https://www.androidfilehost.com/?fid=23487008491963696
To install one of the Google Play Edition ROM's, use the directions in this thread: http://forum.xda-developers.com/gala...ition-t2817708
I seem to have the same exact phone and problem as this guy, so I'll jump in here. I've been working on my un-bootable Verizon Samsung Galaxy S4 i545 phone for about 4 full evenings with no luck.
My history up to this point:
Have Verizon Galaxy S4 i545 with latest OTA stock updates, never rooted. Build number ends with NC5.
Sunday night, performed Towelroot.
Installed SuperSU and SafeStrap.
Performed steps to disable KNOX.
Booted into SafeStrap 3.72.
OK, backed up the Stock Rom to my ext 64gb SD card.
Created a new ROM Slot and tried to install Google Play Edition S4 ROM to it.
On reboots it was booting into the regular Stock ROM (which I had factory reset btw) instead of my custom ROM, even though ROM Slot 1 was active.
Deleted ROM Slot 1 and tried flashing my ROM to Stock ROM slot.
Seem to fail.
SafeStrap now reports this when I click on STOCK ROM:
System partition Size: 0MB (0MB Free)
Data partition Size: 0MB (0MB Free)
Cache partition size: 2046MB (1984MB Free)
OK, so SafeStrap is clearly very messed up.
Booted into Download mode.
Got Odin 3.09 installed on Windows and got the firmware provided here: rootjunkysdl - dot - com/?device=Galaxy%20S4&folder=Firmware that ends in NC5 -- by the way the forum link you posted has dead 404 download links for both Firmwares. Seems like RootJunky was kind enough to mirror them on his server though.
Odin hangs when I try to flash the .tar.md5 file -- it says Device Added and the COM port is there so I know it's connected. After a few minutes with no progress or changes, it says "Complete(Write) operation failed" FAIL.
I think my phone's partitions got screwed up, or else it has a write lock on it. Any help would be MUCH appreciated and will even donate $25 to a project of your choosing upon getting this working.
UPDATE: Sure enough, just 15 minutes after I posted this I gave it one more full go in Odin 3.07 instead of 3.09 and it seems to be working now. Not sure if that had anything to do with it. Sucks that this phone can't work with custom recoveries like ClockWork... SafeStrap takes up a lot of extra space because you have to store both roms on the card at once.
Update 2: You also posted an Error 404 link to the Google Play Edition forum post. I'd like to get that on my phone.
joshm.1219 said:
http://forum.xda-developers.com/showthread.php?t=2735172
Flash the full-wipe version in Odin.
Then if you want custom roms, follow my instructions:
First, obtain root. Go to your Settings/Security, check "allow installation from unknown sources". Go to www.towelroot.com , click on the lambda, install the towelroot.apk, then open it and hit "make it ra1n". After reboot, download SuperSU. Open it, it will prompt you to update binaries, do so using the "normal" option. Congrats, you're rooted.
The only custom recovery you can have on NC5 is Safestrap, no TWRP or CWM. You can only flash TW rom's and a select few GPE rom's. You need to use AT&T's 3.72 safestrap for kit kat rom's, which can be found here: http://forum.xda-developers.com/show....php?t=2448925
To install safestrap, first install busybox. Find it here: https://play.google.com/store/apps/d....busybox&hl=en
Then, change selinux status to permissive. Do this by using selinux mode changer: https://play.google.com/store/apps/d....selinux&hl=en
Now install the safestrap apk, open it and hit the install recovery button.
To flash a kit kat rom with SS 3.72, you must use the "stock" slot. ROM slots don't work. You can still make a backup of your stock rom incase anything goes wrong. Be warned, you should have Odin and an NC5 tar file ready to go at all times on your comp.
So, you install the rom like you normally do with TWRP or CWM. Wipe data, cache, dalvik cache, system. Then flash rom, modules, and SuperSU.
The NC5 modules are here: https://www.androidfilehost.com/?fid=23486521113837640
The SuperSU zip is here: http://forum.xda-developers.com/show....php?t=1538053
If you forget to flash SuperSU, you may lose root. You can still get it back by using towelroot. If Wifi isn't turning on, try going back into Safestrap and flashing this: https://www.androidfilehost.com/?fid=23487008491963696
To install one of the Google Play Edition ROM's, use the directions in this thread: http://forum.xda-developers.com/gala...ition-t2817708
Click to expand...
Click to collapse
You should see about getting this stickied on Q and A. It seems nobody reads anything and maybe a title like "EVERYTHING YOU NEED TO FIX YOUR SOFT BRICKED PHONE" might get some reads.... just a thought.
statikeffeck said:
I seem to have the same exact phone and problem as this guy, so I'll jump in here. I've been working on my un-bootable Verizon Samsung Galaxy S4 i545 phone for about 4 full evenings with no luck.
My history up to this point:
Have Verizon Galaxy S4 i545 with latest OTA stock updates, never rooted. Build number ends with NC5.
Sunday night, performed Towelroot.
Installed SuperSU and SafeStrap.
Performed steps to disable KNOX.
Booted into SafeStrap 3.72.
OK, backed up the Stock Rom to my ext 64gb SD card.
Created a new ROM Slot and tried to install Google Play Edition S4 ROM to it.
On reboots it was booting into the regular Stock ROM (which I had factory reset btw) instead of my custom ROM, even though ROM Slot 1 was active.
Deleted ROM Slot 1 and tried flashing my ROM to Stock ROM slot.
Seem to fail.
SafeStrap now reports this when I click on STOCK ROM:
System partition Size: 0MB (0MB Free)
Data partition Size: 0MB (0MB Free)
Cache partition size: 2046MB (1984MB Free)
OK, so SafeStrap is clearly very messed up.
Booted into Download mode.
Got Odin 3.09 installed on Windows and got the firmware provided here: rootjunkysdl - dot - com/?device=Galaxy%20S4&folder=Firmware that ends in NC5 -- by the way the forum link you posted has dead 404 download links for both Firmwares. Seems like RootJunky was kind enough to mirror them on his server though.
Odin hangs when I try to flash the .tar.md5 file -- it says Device Added and the COM port is there so I know it's connected. After a few minutes with no progress or changes, it says "Complete(Write) operation failed" FAIL.
I think my phone's partitions got screwed up, or else it has a write lock on it. Any help would be MUCH appreciated and will even donate $25 to a project of your choosing upon getting this working.
UPDATE: Sure enough, just 15 minutes after I posted this I gave it one more full go in Odin 3.07 instead of 3.09 and it seems to be working now. Not sure if that had anything to do with it. Sucks that this phone can't work with custom recoveries like ClockWork... SafeStrap takes up a lot of extra space because you have to store both roms on the card at once.
Update 2: You also posted an Error 404 link to the Google Play Edition forum post. I'd like to get that on my phone.
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal...ow-to-install-aosp-s4-google-edition-t2817708
Here you go
liljoe727 said:
You should see about getting this stickied on Q and A. It seems nobody reads anything and maybe a title like "EVERYTHING YOU NEED TO FIX YOUR SOFT BRICKED PHONE" might get some reads.... just a thought.
Click to expand...
Click to collapse
I would but I honestly have no confidence in anyone reading a sticky haha
joshm.1219 said:
http://forum.xda-developers.com/gal...ow-to-install-aosp-s4-google-edition-t2817708
Here you go
I would but I honestly have no confidence in anyone reading a sticky haha
Click to expand...
Click to collapse
That would be.... revolutionary. Lol.
I'm run a Sprint Note 3 stock rooted 4.4.2 NC5 with Philz CWM version hltespr 6.12.9. I decided to update to 4.4.4 NK4. First, thought I would skip a step by not unrooting device and just did a factory reset. Then booted into download mode and Odin flashed NK4 ( I used a fresh copy from Sammobile 1.50gb zip ). When the flash was finished ( Passed on odin ) the device tried to start and bootlooped or what some might call a soft brick. Pulled the battery and then booted into recovery, and found to my suprise that the custom recovery was still installed. The Odin flash did not completely take, so while in recovery I wiped caches, data, and system.
Now from recovery booted into download mode and Odin flashed NK4 again. This time it installed properly and so I went back and forth from NC5 to NK4 about 6 times. Why, to check various things like signal strength ( about the same with both NC5 and NK4 basebands ) GPS ( found no problem with getting GPS to lock with NK4 ) Ram footprint ( at first boot up NK4 only slightly larger than NC5 ) . Of course going back to NC5 from NK4 resulted in bootloop or soft brick at boot up, the easiest way to fix this is to pull the battery boot into recovery do a factory reset, then Odin flash NC5 again. If you are the least bit timid about bootloops and soft bricks I don't recommend doing this.
Ok, so now I have a stock, recovery status ( official ) NK4 installed. Next installed a custom recovery, went with Philz CWM hltespr v6.12.9 ( this recovery is bulletproof ). I Odin flashed Philz and booted the device everything good. Next booted into recovery and flashed Super Su v2.40. Then booted back into NK4 everything running great used root checker and the device is rooted.
Now I have stock rooted NK4, so now to debloat the device started with KNOX. Went to SuperSu and clicked ok to disable KNOX, SuperSu froze at "disabling KNOX". I rebooted the device and downloaded Root Explorer then did a KNOX search and about 25+ files containing KNOX ( more than in NC5 apparently they added a few new ones to NK4 ) did a multi-delete and then rebooted device and it bootlooped at start up.
So back to square one, flashed Nk4, Philz recovery, and tried the experimental ( BETA ) SuperSu 2.4.3 version. Device booted up fine, tried to disable KNOX and again it froze at "disabling KNOX", again I tried to remove all the KNOX files with Root Explorer and it bootlooped again at start up. At this point I'm going to wait till Chainfire has a cf-autoroot for NK4 and a SuperSu that will disable KNOX. Went back to NC5 with everything running smooth as glass, hope this info is helpful. Enjoy !!!
jimzweb1 said:
I'm run a Sprint Note 3 stock rooted 4.4.2 NC5 with Philz CWM version hltespr 6.12.9. I decided to update to 4.4.4 NK4. First, thought I would skip a step by not unrooting device and just did a factory reset. Then booted into download mode and Odin flashed NK4 ( I used a fresh copy from Sammobile 1.50gb zip ). When the flash was finished ( Passed on odin ) the device tried to start and bootlooped or what some might call a soft brick. Pulled the battery and then booted into recovery, and found to my suprise that the custom recovery was still installed. The Odin flash did not completely take, so while in recovery I wiped caches, data, and system.
Now from recovery booted into download mode and Odin flashed NK4 again. This time it installed properly and so I went back and forth from NC5 to NK4 about 6 times. Why, to check various things like signal strength ( about the same with both NC5 and NK4 basebands ) GPS ( found no problem with getting GPS to lock with NK4 ) Ram footprint ( at first boot up NK4 only slightly larger than NC5 ) . Of course going back to NC5 from NK4 resulted in bootloop or soft brick at boot up, the easiest way to fix this is to pull the battery boot into recovery do a factory reset, then Odin flash NC5 again. If you are the least bit timid about bootloops and soft bricks I don't recommend doing this.
Ok, so now I have a stock, recovery status ( official ) NK4 installed. Next installed a custom recovery, went with Philz CWM hltespr v6.12.9 ( this recovery is bulletproof ). I Odin flashed Philz and booted the device everything good. Next booted into recovery and flashed Super Su v2.40. Then booted back into NK4 everything running great used root checker and the device is rooted.
Now I have stock rooted NK4, so now to debloat the device started with KNOX. Went to SuperSu and clicked ok to disable KNOX, SuperSu froze at "disabling KNOX". I rebooted the device and downloaded Root Explorer then did a KNOX search and about 25+ files containing KNOX ( more than in NC5 apparently they added a few new ones to NK4 ) did a multi-delete and then rebooted device and it bootlooped at start up.
So back to square one, flashed Nk4, Philz recovery, and tried the experimental ( BETA ) SuperSu 2.4.3 version. Device booted up fine, tried to disable KNOX and again it froze at "disabling KNOX", again I tried to remove all the KNOX files with Root Explorer and it bootlooped again at start up. At this point I'm going to wait till Chainfire has a cf-autoroot for NK4 and a SuperSu that will disable KNOX. Went back to NC5 with everything running smooth as glass, hope this info is helpful. Enjoy !!!
Click to expand...
Click to collapse
just freeze the knox **** with titanium easier.
jimzweb1 said:
I'm run a Sprint Note 3 stock rooted 4.4.2 NC5 with Philz CWM version hltespr 6.12.9. I decided to update to 4.4.4 NK4. First, thought I would skip a step by not unrooting device and just did a factory reset. Then booted into download mode and Odin flashed NK4 ( I used a fresh copy from Sammobile 1.50gb zip ). When the flash was finished ( Passed on odin ) the device tried to start and bootlooped or what some might call a soft brick. Pulled the battery and then booted into recovery, and found to my suprise that the custom recovery was still installed. The Odin flash did not completely take, so while in recovery I wiped caches, data, and system.
Now from recovery booted into download mode and Odin flashed NK4 again. This time it installed properly and so I went back and forth from NC5 to NK4 about 6 times. Why, to check various things like signal strength ( about the same with both NC5 and NK4 basebands ) GPS ( found no problem with getting GPS to lock with NK4 ) Ram footprint ( at first boot up NK4 only slightly larger than NC5 ) . Of course going back to NC5 from NK4 resulted in bootloop or soft brick at boot up, the easiest way to fix this is to pull the battery boot into recovery do a factory reset, then Odin flash NC5 again. If you are the least bit timid about bootloops and soft bricks I don't recommend doing this.
Ok, so now I have a stock, recovery status ( official ) NK4 installed. Next installed a custom recovery, went with Philz CWM hltespr v6.12.9 ( this recovery is bulletproof ). I Odin flashed Philz and booted the device everything good. Next booted into recovery and flashed Super Su v2.40. Then booted back into NK4 everything running great used root checker and the device is rooted.
Now I have stock rooted NK4, so now to debloat the device started with KNOX. Went to SuperSu and clicked ok to disable KNOX, SuperSu froze at "disabling KNOX". I rebooted the device and downloaded Root Explorer then did a KNOX search and about 25+ files containing KNOX ( more than in NC5 apparently they added a few new ones to NK4 ) did a multi-delete and then rebooted device and it bootlooped at start up.
So back to square one, flashed Nk4, Philz recovery, and tried the experimental ( BETA ) SuperSu 2.4.3 version. Device booted up fine, tried to disable KNOX and again it froze at "disabling KNOX", again I tried to remove all the KNOX files with Root Explorer and it bootlooped again at start up. At this point I'm going to wait till Chainfire has a cf-autoroot for NK4 and a SuperSu that will disable KNOX. Went back to NC5 with everything running smooth as glass, hope this info is helpful. Enjoy !!!
Click to expand...
Click to collapse
What version of Odin are you using and where did you get your tar files from? I'd like to try flashing back to NC5 from NK4 to gain root without tripping Knox until something other than cf-auto can root NK4.
Sent from my SM-N900P using Tapatalk 2
biggdevon said:
What version of Odin are you using and where did you get your tar files from? I'd like to try flashing back to NC5 from NK4 to gain root without tripping Knox until something other than cf-auto can root NK4.
Sent from my SM-N900P using Tapatalk 2
Click to expand...
Click to collapse
Read through this thread should answer all your questions http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440
on my thread I list micmars as he has a great XDA site for .tar files. However I got the tar. files from here http://www.sammobile.com/firmwares/. If flashing back to NC5 results in a bootloop DON"T PANIC !!!! Just pull the battery boot into recovery and wipe cache and do a factory reset. Than pull the battery and boot into download mode and flash NC5 again. One thing on the second flash be PATIENT, after odin finishes and says PASSED " DO NOT UNPLUG THE DEVICE " you will notice at this point is where a blue flash line starts that is the recovery the last thing being flashed !!! It takes about 3 to 5 minutes after you see PASSED your device screen will dim and it will start up for first time use.
Your process worked like a charm for me. Fully rooted stock NC5 from NK4 using towelroot. Is there anyway to retain root and go back to NK4?
Sent from my SM-N900P using Tapatalk 2
biggdevon said:
Your process worked like a charm for me. Fully rooted stock NC5 from NK4 using towelroot. Is there anyway to retain root and go back to NK4?
Sent from my SM-N900P using Tapatalk 2
Click to expand...
Click to collapse
No, sorry NH7 closed the exploit used by Towelroot in NC5. It has not been updated for NH7 or NK4. If you use Towelroot, cf-atuoroot, or De La Vaga root on NH7 or NK4 you will trip KNOX !!!
If your KNOX warranty is tripped like mine then root with SuperSU. Just flash in a custom recovery for any version of KitKat you want to root. If you have not already checked look at my thread http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 I changed the rooting instructions. Enjoy !!!
So is it possible to flash nc5 nh7 or nk4 tars at any time . I'm on nk4 full firmware and baseband .. just wanna make sure .. THNX FOR THIS INFO
chico260 said:
So is it possible to flash nc5 nh7 or nk4 tars at any time . I'm on nk4 full firmware and baseband .. just wanna make sure .. THNX FOR THIS INFO
Click to expand...
Click to collapse
Yes, I have done it many times now. As I stated above just be aware that a bootloop can occur going back to NC5 from NH7 or NK4. Don't Panic just follow the instructions above and it's smooth sailing. Besides the info above you can check out my flashing thread here http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 Enjoy !!!
jimzweb1 said:
Yes, I have done it many times now. As I stated above just be aware that a bootloop can occur going back to NC5 from NH7 or NK4. Don't Panic just follow the instructions above and it's smooth sailing. Besides the info above you can check out my flashing thread here http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 Enjoy !!!
Click to expand...
Click to collapse
Also will the one click work going from nk4 to nc5?
Im on NH7 modem and baseband and im trying to go to Nk4 modem but I get this error on Odin 3.07
EDIT: I got it
Jocutz1987 said:
Im on NH7 modem and baseband and im trying to go to Nk4 modem but I get this error on Odin 3.07
EDIT: I got it
Click to expand...
Click to collapse
You need remove SIM card when fresh the ROM, maybe helpful. Should see all pass here instead of any fail.