I was attempting to go back to stock in an effort to Get the update that just dropped. I have rooted, flashed, gone back to stock, rooted and flashed again prior to this with no problems.
I have been running JoshBeach's JellyBomb with no problems.
In trying to flash the stock .tar, it failed, I cannot get it to complete a flash, and it will only boot into emergency or download mode.
Should I try running CF Auto-root again?
GAPO said:
I was attempting to go back to stock in an effort to Get the update that just dropped. I have rooted, flashed, gone back to stock, rooted and flashed again prior to this with no problems.
I have been running JoshBeach's JellyBomb with no problems.
In trying to flash the stock .tar, it failed, I cannot get it to complete a flash, and it will only boot into emergency or download mode.
Should I try running CF Auto-root again?
Click to expand...
Click to collapse
Did you put your phone into download mode when initializing cf-root?
Sprint Galaxy Note 3
Stock rooted 4.3
Mart1an said:
Did you put your phone into download mode when initializing cf-root?
Sprint Galaxy Note 3
Stock rooted 4.3
Click to expand...
Click to collapse
Well, I had thought so. But I tried it again this morning, making sure to do so, and it worked. Still couldn't seem to install stock file, but I ran CF-root again(successfully), flashed TWRP in Odin, then flashed JellyBomb Domination. So, I still don't have the update, but I am functional. Thanks, bud!
I am a bit of a noob but I have rooted my sprint note 3 which came out successful. I have rooted my galaxy s3 before in the past and flashed many roms without any issues.
Once I rooted my note 3 I ran the stock rom for a week and then decided to kick it up a notch and flashed the bonsai rom, which worked fine until i discovered the camera didn't work. Before I flashed the bonsai rom, I did a backup of the stock rom via cwm. Once I figured out the camera didn't work with the bonsai rom, I reset and wiped the data for my phone and tried to restore the stock rom which i figured it was a boo boo because I got stuck in a bootloop so I reflashed the bonsai rom back on my phone until I got back home to my pc. At that point, I decided to unroot and return the phone back to stock. I used odin and followed unrooting instructions to a tee and I had an official stock firmware, but odin failed and I think I may have soft bricked my phone. In a panic, I downloaded a "rooted stock" rom and flashed that...after a few bootloops, I updated my cwm recovery and superuser app...and my phone has been working fine every since (whew). I really want to unroot, then re-root and just run the stock rom without flashing any more custom roms, however I am afraid of bricking it again.
I have the stock official firmware N900PVPUBMJ4_N900PSPTBMJ4_N900PVPUBMJ4_HOME.tar.md 5 which to my understanding is android 4.3. I do understand that 4.4 is out. I was wondering is it ok to flash the 4.3 using odin to return my phone back to stock?? I've been spooked ever since my soft brick encounter. Any info will be helpful. Btw, sorry for the long story. I figured I should give all the details. That would help me get to the bottom of it all
Thanks in Advance!
LadyDroid81 said:
I am a bit of a noob but I have rooted my sprint note 3 which came out successful. I have rooted my galaxy s3 before in the past and flashed many roms without any issues.
Once I rooted my note 3 I ran the stock rom for a week and then decided to kick it up a notch and flashed the bonsai rom, which worked fine until i discovered the camera didn't work. Before I flashed the bonsai rom, I did a backup of the stock rom via cwm. Once I figured out the camera didn't work with the bonsai rom, I reset and wiped the data for my phone and tried to restore the stock rom which i figured it was a boo boo because I got stuck in a bootloop so I reflashed the bonsai rom back on my phone until I got back home to my pc. At that point, I decided to unroot and return the phone back to stock. I used odin and followed unrooting instructions to a tee and I had an official stock firmware, but odin failed and I think I may have soft bricked my phone. In a panic, I downloaded a "rooted stock" rom and flashed that...after a few bootloops, I updated my cwm recovery and superuser app...and my phone has been working fine every since (whew). I really want to unroot, then re-root and just run the stock rom without flashing any more custom roms, however I am afraid of bricking it again.
I have the stock official firmware N900PVPUBMJ4_N900PSPTBMJ4_N900PVPUBMJ4_HOME.tar.md 5 which to my understanding is android 4.3. I do understand that 4.4 is out. I was wondering is it ok to flash the 4.3 using odin to return my phone back to stock?? I've been spooked ever since my soft brick encounter. Any info will be helpful. Btw, sorry for the long story. I figured I should give all the details. That would help me get to the bottom of it all
Thanks in Advance!
Click to expand...
Click to collapse
Depends on what version you are running, but sounds like you are on mj4 still... http://forum.xda-developers.com/showthread.php?t=2657828 this one is mj4 (4.3), if you are on 4.4 you need to go to the Android development forum and use whatever version you are on, just look for rwilcos one click.
tonyevo52 said:
Depends on what version you are running, but sounds like you are on mj4 still... http://forum.xda-developers.com/showthread.php?t=2657828 this one is mj4 (4.3), if you are on 4.4 you need to go to the Android development forum and use whatever version you are on, just look for rwilcos one click.
Click to expand...
Click to collapse
Yes...I am still on 4.3.
LadyDroid81 said:
Yes...I am still on 4.3.
Click to expand...
Click to collapse
Follow the instructions from this thread and you will be fully unrooted http://forum.xda-developers.com/showthread.php?t=2657828:good:
Hey everybody,
First time poster here. So I have an AT&T Galaxy S4 I337 that I have been running Cyanogenmod on for quite a while now. Well, after getting bored and wanting to revert to the original firmware, I went through the process of a factory reset to stock through Odin. Everything went smoothly, all that's left is to update to 4.4.2 Kitkat and to root my phone once again. I went into settings and began the OTA update thinking it would install 4.4.2. After about 20 minutes of updating and downloading, my phone finally finished rebooting, but when I checked to see what version of android I was running, it was still 4.2.2. Kies also says that I'm running the latest firmware. Why won't my phone or Kies pick up the new Kitkat update? Does it have something to do with the fact that I flashed a custom ROM before? I could really use some help!
Thanks!
ViridianFlea said:
Hey everybody,
First time poster here. So I have an AT&T Galaxy S4 I337 that I have been running Cyanogenmod on for quite a while now. Well, after getting bored and wanting to revert to the original firmware, I went through the process of a factory reset to stock through Odin. Everything went smoothly, all that's left is to update to 4.4.2 Kitkat and to root my phone once again. I went into settings and began the OTA update thinking it would install 4.4.2. After about 20 minutes of updating and downloading, my phone finally finished rebooting, but when I checked to see what version of android I was running, it was still 4.2.2. Kies also says that I'm running the latest firmware. Why won't my phone or Kies pick up the new Kitkat update? Does it have something to do with the fact that I flashed a custom ROM before? I could really use some help!
Thanks!
Click to expand...
Click to collapse
You can't update directly from 4.2.2 to 4.4.2. You're missing out on a couple of updates in between. But, it doesn't look like you've read a head too much. You can't root 4.4.2 directly. The current method for rooting it involves downgrading back to 4.3, rooting, installing the Safestrap recovery, and using that to install a stock rooted rom. Since you are already on 4.2.2 and can use a custom recovery, it is recommended to install a stock or custom rom and the accompanying modem. Once you go past 4.3, there is no return due to the Knox bootloader deal.
Hey folks... so I've been using SafeStrap on a stock (locked) MJ9 device to run a couple different roms, but I decided to restore my original backup so that I could get the new KK update. Every time I try to do the update, it downloads, reboots, gets about halfway up the progress bar, and then it fails and reboots. Anybody have any ideas what might be causing this or what might fix it? Huge thanks!
Unroot your phone
You may also want to try to flash a stock 4.3 MJ9 rom.
Well, unrooting didn't work, but reflashing the stock MJ9 with Odin did! Thanks folks!
Requesting help. I am not a noob by any means, I have installed custom roms many times, and rooted many phones, and installed and used safestrap on several phones, but I cannot get ANY custom rom to install properly on my Verizon Samsung Galaxy S4, which is (was) rooted, with Safestrap 3.72, and MK2 firmware.
I was running the stock 4.3/mk2 firmware, with the latest busybox and supersu, and the latest safestrap, and safe root installed. I was able to successfully root the phone, and install safestrap, but even when I created a rom slot, gave it a name, wiped it completely, and then try to install one of the many 4.3/mk2 "Safe" roms, no rom will boot, once installed. It is so frustrating! I read somewhere that with the Verizon S4, and MK2 firmware, you could only install a rom in the stock rom slot, so I tried that, and now safestrap is gone, and the phone boots to a light blue screen with little green checkmarks. So I'm in the process of downloading the original MK2 firmware from Samsung and using Odin to restore. Anybody have any ideas? I'm thinking of quickly getting rid of the S4 while it still has some value.
mactechnm said:
Requesting help. I am not a noob by any means, I have installed custom roms many times, and rooted many phones, and installed and used safestrap on several phones, but I cannot get ANY custom rom to install properly on my Verizon Samsung Galaxy S4, which is (was) rooted, with Safestrap 3.72, and MK2 firmware.
I was running the stock 4.3/mk2 firmware, with the latest busybox and supersu, and the latest safestrap, and safe root installed. I was able to successfully root the phone, and install safestrap, but even when I created a rom slot, gave it a name, wiped it completely, and then try to install one of the many 4.3/mk2 "Safe" roms, no rom will boot, once installed. It is so frustrating! I read somewhere that with the Verizon S4, and MK2 firmware, you could only install a rom in the stock rom slot, so I tried that, and now safestrap is gone, and the phone boots to a light blue screen with little green checkmarks. So I'm in the process of downloading the original MK2 firmware from Samsung and using Odin to restore. Anybody have any ideas? I'm thinking of quickly getting rid of the S4 while it still has some value.
Click to expand...
Click to collapse
3.72 is for 4.4 KitKat and was made for the AT&T version of the S4, therefore, you are not able to create slots. You would need to install 3.71 and only flash 4.3 based roms. If you want 4.4 based roms you need to upgrade to NC5 and install 3.72, but you are only able to flash to the stock side.
There's plenty of info for you to read in the General section.
riker147 said:
3.72 is for 4.4 KitKat and was made for the AT&T version of the S4, therefore, you are not able to create slots. You would need to install 3.71 and only flash 4.3 based roms. If you want 4.4 based roms you need to upgrade to NC5 and install 3.72, but you are only able to flash to the stock side.
There's plenty of info for you to read in the General section.
Click to expand...
Click to collapse
Thank you for your response. Actually what I failed to mention is I did have 3.71 installed first, and I had the exact same problem. So it's not an issue with the safestrap version. And I have tried about 12 different ROMs. Including BajaROM-S4-Release-v-2.2 and BoneStock4.3_S4v2.1. As I said, I'm not a newbie at all, and I'm not about to hunt and peck for information again (which is what I've been doing for two days now). I wouldn't have asked for help if I had been successful in my search.
I have never had an issue installing any safestrap compatible rom...3.72 is strictly for android 4.4 and no rom slots...so no way you would ever get a rom installed using 3.72 on MK2 base build. As for 3.71...never heard of any issue with SS compatible roms for 3.71 not installing right. Really difficult to figure out what you are doing wrong from what you are giving us...
sent by safestrap powered echo v26
decaturbob said:
I have never had an issue installing any safestrap compatible rom...3.72 is strictly for android 4.4 and no rom slots...so no way you would ever get a rom installed using 3.72 on MK2 base build. As for 3.71...never heard of any issue with SS compatible roms for 3.71 not installing right. Really difficult to figure out what you are doing wrong from what you are giving us...
sent by safestrap powered echo v26
Click to expand...
Click to collapse
Again, thanks for your help. I'm going to start with Odin. Wipe it all clean and start over. That's always the best option. Thanks!
basically, I'd follow this:
http://forum.xda-developers.com/showthread.php?t=2763834
I'd go back to MK2, root, BB, SS 3.71. Then go up to NC5 ROMs with SS 3.72. Wiping EVERYTHING along the way, system included, not just factory reset
Similar Issue
I not a noob either im very familiar with how this whole operation works.
I have a very similar issue as well I'm (unable to flash roms including my own recovery). I'm 100% knowledgeable on CM, but when it comes to Safestrap or TWRP base Recoveries I'm far from noon but not an expert so to say... Here's my issue. I have the NC5 firmware and once had the Hyperdrive RLS17.1 KK S4 Final.zip... I went back to the I545VRUFNC5-Stock-Root-Deodex.zip.... I recently attempted to download another ROM, (based on the same firmware of course) as soon as I attempted to flash it (which only took about 1 min and didn't work) I figured something was wrong. So I just decided to go back to my recovery that I've made a few moments ago. When I tried to do that. The msg " E: Unable to mount '/system' " appeared.
Now I've notice since then Wiping and Flashing return the same results.
There is no longer an OS on my S4... I can not Mount the System.
So I believe in stuck in Safestrap 3.72.
(Please let me know what other info you need, I spent the last couple of days trying to figure this out on my own, so far I'm losing the battle)
Please help guys.
same problem
mactechnm said:
Requesting help. I am not a noob by any means, I have installed custom roms many times, and rooted many phones, and installed and used safestrap on several phones, but I cannot get ANY custom rom to install properly on my Verizon Samsung Galaxy S4, which is (was) rooted, with Safestrap 3.72, and MK2 firmware.
I was running the stock 4.3/mk2 firmware, with the latest busybox and supersu, and the latest safestrap, and safe root installed. I was able to successfully root the phone, and install safestrap, but even when I created a rom slot, gave it a name, wiped it completely, and then try to install one of the many 4.3/mk2 "Safe" roms, no rom will boot, once installed. It is so frustrating! I read somewhere that with the Verizon S4, and MK2 firmware, you could only install a rom in the stock rom slot, so I tried that, and now safestrap is gone, and the phone boots to a light blue screen with little green checkmarks. So I'm in the process of downloading the original MK2 firmware from Samsung and using Odin to restore. Anybody have any ideas? I'm thinking of quickly getting rid of the S4 while it still has some value.
Click to expand...
Click to collapse
im having the same problem i am also frustrated i don't know what to do
Similar Issue
I know there must be a way... If only I can get it to mount the "system" and "systemorig"...
I'm going to play around with the Slots and the datas Size's and see what I come up with.
Pretty sure you will need to Odin the stock NC5 image and start over.
Sent from my SCH-I545 using Tapatalk
jmgib said:
Pretty sure you will need to Odin the stock NC5 image and start over.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Oh ok. The Stock NC5 image... Great.
Where can I find the stock image?
If possible, could you please send a link?
Thanks in advance
damien302 said:
I not a noob either im very familiar with how this whole operation works.
I have a very similar issue as well I'm (unable to flash roms including my own recovery). I'm 100% knowledgeable on CM, but when it comes to Safestrap or TWRP base Recoveries I'm far from noon but not an expert so to say... Here's my issue. I have the NC5 firmware and once had the Hyperdrive RLS17.1 KK S4 Final.zip... I went back to the I545VRUFNC5-Stock-Root-Deodex.zip.... I recently attempted to download another ROM, (based on the same firmware of course) as soon as I attempted to flash it (which only took about 1 min and didn't work) I figured something was wrong. So I just decided to go back to my recovery that I've made a few moments ago. When I tried to do that. The msg " E: Unable to mount '/system' " appeared.
Now I've notice since then Wiping and Flashing return the same results.
There is no longer an OS on my S4... I can not Mount the System.
So I believe in stuck in Safestrap 3.72.
(Please let me know what other info you need, I spent the last couple of days trying to figure this out on my own, so far I'm losing the battle)
Please help guys.
Click to expand...
Click to collapse
shonnick01 said:
im having the same problem i am also frustrated i don't know what to do
Click to expand...
Click to collapse
I only just saw these posts, I have not been on here for a week or so but if you are still having issues... As far as what went wrong to begin with, did you factory reset/advanvanced wipe all but the internal sd before flashing? Are you only installing into the 'stock' slot on SafeStrap? As far as the fix, if you are suck in Safestrap, you will need to boot into recovery mode, if possible and wipe/factory reset and then boot into download mode and flash one of these http://forum.xda-developers.com/showthread.php?t=2735172 in Odin.
liljoe727 said:
I only just saw these posts, I have not been on here for a week or so but if you are still having issues... As far as what went wrong to begin with, did you factory reset/advanvanced wipe all but the internal sd before flashing? Are you only installing into the 'stock' slot on SafeStrap? As far as the fix, if you are suck in Safestrap, you will need to boot into recovery mode, if possible and wipe/factory reset and then boot into download mode and flash one of these http://forum.xda-developers.com/showthread.php?t=2735172 in Odin.
Click to expand...
Click to collapse
Thanks a lot man. The is has been resolved...
I had to Odin the stock NC5 (exactly what you've just mentioned in your response.) I had to flash it twice actually. The first time only took about 3 mins. I then tried to restore my backup, but during the time it restari SS (when the flash was approximately 90% done) I then went to restart the system and then received the notice "No OS loaded). So I wiped all except my SD card and then I just thought to myself to just try and Odin the stock NC5 one more time (it was getting late and I was about to give up). On the 2nd attempi it took almost 3 times the length as before (15-20mins) when it finished, it bypass the " unlock Samsung screen " and displayed the stock splash screen and audio then the Verizon screen. ( I was happier the a crackhead at a free crack-give-away)...
So I want to thank you for responding, I was determined not to give up,, and it was really close before I was about throw in the towel... Thanks a bunch. (You're response was exactly what I did last night)... I was about to update my issue as soon as I fixed it las night was it was so late and I was really sleepy, then I wake up to your message with the exact fix.
Thanks a lot ☺☺