Related
Hey all,
I just received my i777 and I'm impressed. Coming from a sgs4g seems like a huge improvement, though the devices look physically the same LOL (with the i777 being a bit on the larger side).
Anyways, I've been flashing roms for about a year now with my sgs4g. The forums for the sgs4g had very detailed instructions when flashing, instructions like, what to do if coming from stock, but on this forum ppl just assume you have CWM installed.
What I want is a safe way to upgrade to, let's say, phone bricker. I've noticed that all roms are installed through CWM, and all OP say is "make sure CWM is installed", but there's no mention whatsoever on how to install CWM on this phone.
Maybe i'm complicating things a little bit. On my previous phone, Rom Manager downloaded from market was a NO NO because it'd brick it. So we had to flash a modded CWM via odin made specifically for our phones. Maybe for this phone installing rom manager is all that is needed? yes? OK, found the FAQ. no ROM manager.
Also, somehow this phone came rooted... I bought it new from a store but the unlocked version since I live outside USA.
So, if I'm not mistaken, I should just install rom manager, select my phone from the list, flash CWM recovery and flash away roms on the dev section. Am I correct? I don't want to brick my phone
I would not use Rom manger it's proven to be more of a headache for this device. Look on the dev section there are a couple of packages that you can use to get cwm. If your already rooted you could simply flash a custom kernel like entropys daily driver which already has cwm included in kernel.
Again, if your rooted, easiest way could be to simply use mobile Odin to flash custom kernel(I'm assuming your running gingerbread).
I bought the full version of mobile ODIN. makes life a little simpler when flashing, in my opinion. It's worth the few bucks.
eep2378 said:
I would not use Rom manger it's proven to be more of a headache for this device. Look on the dev section there are a couple of packages that you can use to get cwm. If your already rooted you could simply flash a custom kernel like entropys daily driver which already has cwm included in kernel.
Again, if your rooted, easiest way could be to simply use mobile Odin to flash custom kernel(I'm assuming your running gingerbread).
Click to expand...
Click to collapse
Running GB, yes. It's (i think) completely stock: GB KJ4.
I've checked and I have standard recovery, so I'm looking for the best and safest way to get cmw.
Mobile odin looks like a good option, but would I need the full paid version?
mikeflash said:
Running GB, yes. It's (i think) completely stock: GB KJ4.
I've checked and I have standard recovery, so I'm looking for the best and safest way to get cmw.
Mobile odin looks like a good option, but would I need the full paid version?
Click to expand...
Click to collapse
You don't need pro version, lite version will do just fine. Are you sure you're rooted? You have superuser app? Whether you're rooted or not look here(if you are rooted look at #3 : http://forum.xda-developers.com/showthread.php?t=1311081
Check out this thread, was my experience and I'm running PhoneBricker just fine!
However, backup your apps before flashing and factory reset, wipe cache and dalvik after (possibly before as well) and you should be fine! Will root then you can flash away.
Clay
Sent from my SGH-I777 using XDA
One other point for you. Your phone was flashed, in most probability by the folks who sold it to you, with a leaked version of Gingerbread, UCKJ4. As a result, your flash count is probably at 1, and the secondary bootloader was probably replaced with one that disables the ability to clear the flash counter with a usb jig. If this matters to you, you can test first with a jig to see if it will reset, and if not, you can flash the original UCKH7 secondary bootloader to fix it. Needed files can be found in the Download Repository.
Oh, and my guide explains how to flash a modified kernel containing ClockworkMod Recovery if you need it.
Well, I flashed my phone last night. Used mobile odin for flashing a kernel (siyah) to get CWM, then flashed phone bricker via CWM like I used to do on my old phone. Everything went smooth.
Though I'm not fond on this "4.0.3", it's just a launcher that looks like ICS but I don't want to believe it's a true ICS ROM, because it feels weird, I certainly prefer stock GB (or a custom GB rom) instead of some heavily modded rom with ICS theme.
creepyncrawly said:
One other point for you. Your phone was flashed, in most probability by the folks who sold it to you, with a leaked version of Gingerbread, UCKJ4. As a result, your flash count is probably at 1, and the secondary bootloader was probably replaced with one that disables the ability to clear the flash counter with a usb jig. If this matters to you, you can test first with a jig to see if it will reset, and if not, you can flash the original UCKH7 secondary bootloader to fix it. Needed files can be found in the Download Repository.
Oh, and my guide explains how to flash a modified kernel containing ClockworkMod Recovery if you need it.
Click to expand...
Click to collapse
There're several new terms I need to learn about this phone that weren't used on sgs4g. Such as DPI (i.e lowering it, what for? isn't that a step back?) and flash counter.
I suppose flash count is just a counter for how many times you have flashed the phone with custom Roms, so that warranty people can check if a returned phone was damaged due to bad flash, or something like that. Am I correct?
If that's the case, then I'm not too worried about flash count because I live outside US, and my AT&T phone wouldn't get warranty over here, but I'll definitely look into that, to check where my counter is at and to check if resetting it back to 0 is still possible.
I'll be checking up on the links you provided.
Thanks a lot.
mikeflash said:
Though I'm not fond on this "4.0.3", it's just a launcher that looks like ICS but I don't want to believe it's a true ICS ROM, because it feels weird, I certainly prefer stock GB (or a custom GB rom) instead of some heavily modded rom with ICS theme.
Click to expand...
Click to collapse
It is a true ICS rom. Samsung didn't do a lot of cosmetic changes when they moved the S2 to ICS though...most changes are under the hood.
If you want something that looks and feels more like true ICS, you should consider trying either CM9 or AOKP. They are both based on Google's source code, nothing Touchwiz about them.
Or if you'd rather stick with what you have, you can always try different launchers. I'm running ICS, but I use Go Launcher and it runs beautifully.
mikeflash said:
There're several new terms I need to learn about this phone that weren't used on sgs4g. Such as DPI (i.e lowering it, what for? isn't that a step back?) and flash counter.
I suppose flash count is just a counter for how many times you have flashed the phone with custom Roms, so that warranty people can check if a returned phone was damaged due to bad flash, or something like that. Am I correct?
Click to expand...
Click to collapse
That is mostly correct. You're right about the purpose of the flash counter, but it actually counts how many times you flash kernels, not roms. And even then, it only increments if you flash a kernel via Odin in download mode. Flashing a kernel in Mobile Odin or CWM doesn't touch the counter.
Incrementing the flash counter also places that possibly annoying yellow triangle on bootup on your phone. Since you're on ICS, you can just use triangle away app from play store (free version is on here somewhere) to get rid of it, though I'm not sure if that'll fix the whole secondary bootloaders thing (probably not). I think it'd be worth it to fix that just so you don't run into anymore problems later if you decide to change something, especially since after the fixes you can just nandroid back to your current setup, but it's not essential and completely up to you.
Sent from my Samsung SGH-I777 using XDA
I'm confused why this thread was started. There ARE detailed instructions in the stickies and by using Google search along with the words XDA after the search u would easily find any and all information needed. Why do we need a thread dedicated to helping one person read stickies which already have this information.
Sent from my SGH-I777 using Tapatalk 2
Phalanx, did you not read the Title?
It says be nice!
crawls back into hole
Sent from my SGH-I777 using XDA
Phalanx7621 said:
I'm confused why this thread was started. There ARE detailed instructions in the stickies and by using Google search along with the words XDA after the search u would easily find any and all information needed. Why do we need a thread dedicated to helping one person read stickies which already have this information.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Thank you friend.
To sum up for OP
1. Strongly suggest NOT to use ROM Manager on any custom ROMs unless you are surely running CyanogenMod ROM.
2. Check the "About phone" to see if it is true ICS or ICS-theme GB.
I ran a quick search and did not find the answer (and frankly as a busy student I don't have time to read through 97 pages of threads). Is it possible/advisable to...
1) install safestrap
2) WIPE STOCK ROM?
3) install Hyperdrive or other custom rom (compatible with safestrap)
4) AND USE ALL OF THE INTERNAL MEMORY FOR SAID CUSTOM ROM?
If possible what would be the issues if any resulting from doing this?
Install safestrap. Create a new Rom Slot 1 don't wipe stock ever!! Once Rom Slot 1 is created with atleast 2GB worth of space it will be activated then flash Hyper drive and the ME7 module then you should be golden
Sent from my SCH-I545 using Tapatalk now Free
Maybe I don't fully understand what the 2GB worth of space is used for... does this mean that for the Hyperdrive slot I will only have 1/8 of the phones 16GB for the rom, apps and other stuff or is that just for the rom and apps/etc will still have the rest of the memory to use?
theshadles said:
I ran a quick search and did not find the answer (and frankly as a busy student I don't have time to read through 97 pages of threads). Is it possible/advisable to...
1) install safestrap
2) WIPE STOCK ROM?
3) install Hyperdrive or other custom rom (compatible with safestrap)
4) AND USE ALL OF THE INTERNAL MEMORY FOR SAID CUSTOM ROM?
If possible what would be the issues if any resulting from doing this?
Click to expand...
Click to collapse
While I will say you can easily brick your device doing this, I had ODIN ready in case I needed it, and I went ahead and did just this. I installed SafeStrap, wiped cache/dalvik/system, and went ahead and flashed Hyperdrive and the modules fix into the stock ROM slot.
While it is not advisable to do this, my phone has been operating FLAWLESSLY ever since I did this. I have not had a single issue and everything works perfect paired with the stock kernel. I am enjoying Hyperdrive while still having all of my storage. I have had to Odin before so I was prepared to just in case flashing went wrong.
Again, most people will advice against this, but .... it does work.
The possible brick sounds spooky to me but how is the space per slot allocated? Does 2GB mean as far as that slot is concerned the phone only has 2GB internal space to use for the rom and all other data (apps and stuff). Or is it just 2GB for rom only and the other data can fill the rest of the space. (Is it like partitioning a drive for a dual boot on a computer only you can't access the data on the other partitions?)
roboots21 said:
While I will say you can easily brick your device doing this, I had ODIN ready in case I needed it, and I went ahead and did just this. I installed SafeStrap, wiped cache/dalvik/system, and went ahead and flashed Hyperdrive and the modules fix into the stock ROM slot.
While it is not advisable to do this, my phone has been operating FLAWLESSLY ever since I did this. I have not had a single issue and everything works perfect paired with the stock kernel. I am enjoying Hyperdrive while still having all of my storage. I have had to Odin before so I was prepared to just in case flashing went wrong.
Again, most people will advice against this, but .... it does work.
Click to expand...
Click to collapse
I just did this on my Verizon Note 3 SM900V Android version 4.3 with Kernel 3.4.0 and Baseband version N900VVRUBMJE with Hardware version N900V.07 but please excuse the ignorance. What modules fix? Where do I find this modules fix? Is there a special version that I will need for my specs? It seems to be working fine without it so is this a must have? Thank you!
theshadles said:
I ran a quick search and did not find the answer (and frankly as a busy student I don't have time to read through 97 pages of threads). Is it possible/advisable to...
1) install safestrap
2) WIPE STOCK ROM?
3) install Hyperdrive or other custom rom (compatible with safestrap)
4) AND USE ALL OF THE INTERNAL MEMORY FOR SAID CUSTOM ROM?
If possible what would be the issues if any resulting from doing this?
Click to expand...
Click to collapse
It is possible to flash over the stock ROM using Safestrap. It's then no longer safe, so if that ROM fails to boot, you must use Odin to restore a factory ROM to recover. That's the concern: if anything goes wrong, then you're going to be in emergency recovery mode.
Also note that flashing over the stock ROM isn't supported.
---------- Post added at 08:40 AM ---------- Previous post was at 08:39 AM ----------
whitelion411 said:
I just did this on my Verizon Note 3 SM900V Android version 4.3 with Kernel 3.4.0 and Baseband version N900VVRUBMJE with Hardware version N900V.07 but please excuse the ignorance. What modules fix? Where do I find this modules fix? Is there a special version that I will need for my specs? It seems to be working fine without it so is this a must have? Thank you!
Click to expand...
Click to collapse
If you flash over the stock ROM, then the kernel modules are still there. Without those modules, things like WiFi won't work.
k1mu said:
It is possible to flash over the stock ROM using Safestrap. It's then no longer safe, so if that ROM fails to boot, you must use Odin to restore a factory ROM to recover. That's the concern: if anything goes wrong, then you're going to be in emergency recovery mode.
Also note that flashing over the stock ROM isn't supported.
---------- Post added at 08:40 AM ---------- Previous post was at 08:39 AM ----------
If you flash over the stock ROM, then the kernel modules are still there. Without those modules, things like WiFi won't work.
Click to expand...
Click to collapse
Oh ok so there really isn't anything extra I have to do then right? The member above stated that he flashed his rom over the stock rom and installed the modules fix so that had me thinking I had another step to go. So far all is working great and if something does go wrong I do have Odin and I even backed up the stock rom to be safe.
whitelion411 said:
Oh ok so there really isn't anything extra I have to do then right? The member above stated that he flashed his rom over the stock rom and installed the modules fix so that had me thinking I had another step to go. So far all is working great and if something does go wrong I do have Odin and I even backed up the stock rom to be safe.
Click to expand...
Click to collapse
You should be good. And yea if something goes wrong while on that stock slot usually Odin is the only way to.
Sent from my SCH-I545 using Tapatalk
theshadles said:
I ran a quick search and did not find the answer (and frankly as a busy student I don't have time to read through 97 pages of threads). Is it possible/advisable to...
1) install safestrap
2) WIPE STOCK ROM?
3) install Hyperdrive or other custom rom (compatible with safestrap)
4) AND USE ALL OF THE INTERNAL MEMORY FOR SAID CUSTOM ROM?
If possible what would be the issues if any resulting from doing this?
Click to expand...
Click to collapse
It's probably not the safest thing to do. What I would recommend, if you feel like you must try it (and I recommend that you not), is install safestrap. Install hyperdrive in the first free slot. Verify that it works. Then, if you really want to, install hyperdrive on the stock rom slot. Verify that it works. Then, if you really must, you can erase the other slot.
GeneralBelisarius said:
It's probably not the safest thing to do. What I would recommend, if you feel like you must try it (and I recommend that you not), is install safestrap. Install hyperdrive in the first free slot. Verify that it works. Then, if you really want to, install hyperdrive on the stock rom slot. Verify that it works. Then, if you really must, you can erase the other slot.
Click to expand...
Click to collapse
Okay, but what do you do if you can't create a rom slot? That's the problem I have so I may be forced to install over the stock rom if I want to use a custom rom.
fdrennon said:
Okay, but what do you do if you can't create a rom slot? That's the problem I have so I may be forced to install over the stock rom if I want to use a custom rom.
Click to expand...
Click to collapse
This thread is from awhile ago, if you're on 4.4 you can't use rom slots on Verizon with safestrap 3.72, you just have to take the risk and use odin or a backup to get your phone working again
Hey all,
* *Going to apologize in advance for a longer post, but I have a lot of questions I'm having a difficult time answering. Hope I'm posting in the correct forum too.
I'm on a Verizon GS4 (SCH-I545), 4.2.2. Build *JDQ39.I545VRUDML1. Presently Rooted and running Stock. (Based on horror stories I've been avoiding doing the update to the stock system)
I came from a Droid Bionic, and it was my first foray into rooting / modding Android phones, but I had it for 2.5 years and became quite proficient with what I could do with it. As a result, I've become very familiar with safestrap's touch screen. Before that I was capable of using bootstrap which used the type of recovery where I had to navigate it with volume keys.
So I have a series of questions that I can't get definitive answers for... More often than not when trying to flash ROMs I end up with a black screen and end up battery pulling and going back to stock system because I can't figure out why its happening.*
1. *Should I continue not taking the OTA update from verizon on my stock system? Most of the horror stories I hear about are with the ME7 build, but my present thinking is that the ML1 build is already past the ME7 one, so maybe all of the extra lockdown features are in place? I haven't been able to pin down exactly where I am on the build paths, and almost all custom ROMs are mentioning MDK or ME7, not really much mention of ML1 - I truly don't know exactly where I stand with this.
2. *Is it going to be easier in the long run if I just abandon safestrap and instead move to one of the other recoveries? I've read enough to understand that I need to flash the fix posted by Hashcode, although I don't really understand what the fix is doing, nor if I'm applying the correct fix. (the file I found was jfltevzw-ME7-modules.zip). Some of the other ROMs have specific fixes that I'm unsure what to do with, often using MDK or ME7 for the Radio. Again, since I don't really understand the differences between the builds, all I know is ME7 seems to be making it harder to flash ROMs. People have also said it doesn't matter if you're flashing the fix with the wrong name (IE I'm on ML1 but flashing the ME7 fix should still work... again not understanding exactly what it is is hurting me here).
* *2a. If I can/should stick with Safestrap, this is a side question - Are the ROMs usable in other slots than ROM slot 1? Throughout the life of my Bionic for the most part that was the only usable partition - most of the custom ROMs wouldn't work in other slots, is this still true?
3. *The only portion of success I've had is that I've had is with Hyperdrive. I've been able to flash this ROM fully and boot into it, but I've had no success with getting the wifi to work - a big problem since I'm not on unlimited data. I will post this specific question to the Hyperdrive thread itself to see if I can have someone help me, but all the research I've done on it has different people having different tricks that worked to get their wifi running (flashing the fix by queueing it after the ROM worked for some, canceling out before rebooting the ROM and separately flashing the Hashcode fix worked for others, one person even had to download the fix via their computer before transferring it to their phone in order for the fix to work - I've tried all of these things and still have no success with wifi).
I'm truly sorry if these questions have been answered before, but I have tried to look for the answers and there are just so many different specific ones I don't really know where I'm going wrong. I suspect there is a simple small detail that I'm doing which would make everything easier, such as using a different recovery, or that I''m flashing the wrong fix, etc. but I'm looking for a little advice to be able to have some success running these ROMs on my phone - After a week running the stock ROM, I'm already completely over it.
Thanks in advance for anyone that takes the time.
Sent from my SCH-I545 using Tapatalk
Quick update, I attempted to flash Bonestock on ROM slot 1 and was successful (previous attempts yielded black screens, but were all on ROM slot 2). I successfully got the ROM installed, but similar to Hyperdrive, I can get no wifi. Any attempt to turn it on yields the wifi flicking on for .25s before turning back off again.
Current assumption is that safestrap still wont load ROMs in other slots, but I still have no idea how to get wifi up and running.
Sent from my SCH-I545 using Tapatalk
I'm an idiot. Everywhere I put "ML1" I meant MI1. I've also determined via another howto YouTube video that MI1 is past ME7, so I am unsure if I should keep putting off OTAs, and also unsure if it will matter for my flashing customs.
Sent from my SCH-I545 using Tapatalk
Use MI1 modules not ME7 ones and flash the modules after you flash a rom. The black screen is normal give it ten minutes. Finally, Never, ever take an OTA.
Sent from my DROID RAZR using XDA Premium 4 mobile app
Found a post with the MI7 modules right before I checked back here and they worked like a charm. Now getting to look into some ROM goodness. Thanks much for the help!
Sent from my SCH-I545 using Tapatalk
Carrier: Verizon
Device: Samsung Galaxy S4 (MK2)
Custom ROM: Hyperdrive ROM
Phone is rooted, and Safestrap is installed and working flawlessly
I see this question posted all the time, but I'm reading a lot of conflicting information. As I've been searching around the net for a solid (and up-to-date) answer, I was wondering if there was a definitive answer to the following question:
Can I flash a custom ROM to the stock slot using Safestrap, remove the stock ROM from the phone, and keep the backup on my PC for later restoration?
I would assume that I should do the following:
1) Make a backup of the stock ROM (using Safestrap)
2) Wipe the Stock slot
3) Install/Restore custom ROM to the Stock slot
Am I correct in assuming this?
If there are any issues, I'd love to hear why. I'm still trying to figure out all the info. If there are any benefits/drawbacks, I'd also love to hear those. I'd consider myself a "conservative" user. I do nothing with themes and major modifications.
Thank you for any advice!
I apologize if this question has been answered elsewhere.
That works just fine and many people already have. AT&T people are in the same boat and do it too.
Sent from Black<3's I337 running Foxhound ROM
DeadlySin9 said:
That works just fine and many people already have. AT&T people are in the same boat and do it too.
Sent from Black<3's I337 running Foxhound ROM
Click to expand...
Click to collapse
Thank you for the information.
remainnameless said:
Thank you for the information.
Click to expand...
Click to collapse
Just make sure you have the Odin tar file for your phone just in case something goes wrong. Me and a few others ran into some issues messing with the stock slot. Good idea to have that anyways.
Sent from my SCH-I545 using Tapatalk
Just in case someone comes across this in the future:
Everything worked as planned. No issues to report.
But doesn't this entirely contradict what the website says?
On the How-To Safestrap site:
Install: This is for flashing a .zip file to the currently active system. Currently, this is disabled for the stock system. In a future release I will enable flashing to the stock system.
Click to expand...
Click to collapse
And yet people are wiping and flashing to stock fine?
Cool, I will try that
Sent from my SCH-I545 using XDA Premium HD app
DaGamer12345 said:
But doesn't this entirely contradict what the website says?
On the How-To Safestrap site:
And yet people are wiping and flashing to stock fine?
Click to expand...
Click to collapse
Hashcode didn't support flashing to the stock slot when I used SafeStrap. You could do it, but if you ran into problems you were not to expect any help from him.
Now whether or not he disabled that option completely in newer versions of SafeStrap I'm not really sure since I'm on an mdk S4 now.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Hashcode didn't support flashing to the stock slot when I used SafeStrap. You could do it, but if you ran into problems you were not to expect any help from him.
Now whether or not he disabled that option completely in newer versions of SafeStrap I'm not really sure since I'm on an mdk S4 now.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
reason why its called safestrap...and has saved me many times able to get back to my stock rom slot...but we all have our own levels of risk but hashcode made safestrap the way he did for a reason.
I run 3 roms on my S4 and have no issues with memory limitations
So then this is a yes on flashing to stock? Thinking about flashing a SS rom, but not sure how it goes.
I assume I would flash the kernel modules as you have to do that with every custom rom.
If Safestrap lives on the stock system, how does it stay after you wipe? It stays on an unwipe-able area? Because it can't stay on recovery, can it?
If anything goes wrong, I could just flash the MK2 stock with Odin, correct? It wouldn't trip KNOX flag to 0x1?
Out of curiosity, if an OTA was available for stock MK2, and I had it as a custom rom, it would brick the phone or what would happen?
In Titanium Backup, you DON'T restore all the system apps, and only the user apps when migrating roms?
This would be my first time wiping/flashing a rom over the system (and not just over a rom slot), so I'm nervous as almost all people new to this sort of thing.
DaGamer12345 said:
So then this is a yes on flashing to stock? Thinking about flashing a SS rom, but not sure how it goes.
I assume I would flash the kernel modules as you have to do that with every custom rom.
If Safestrap lives on the stock system, how does it stay after you wipe? It stays on an unwipe-able area? Because it can't stay on recovery, can it?
If anything goes wrong, I could just flash the MK2 stock with Odin, correct? It wouldn't trip KNOX flag to 0x1?
Out of curiosity, if an OTA was available for stock MK2, and I had it as a custom rom, it would brick the phone or what would happen?
In Titanium Backup, you DON'T restore all the system apps, and only the user apps when migrating roms?
This would be my first time wiping/flashing a rom over the system (and not just over a rom slot), so I'm nervous as almost all people new to this sort of thing.
Click to expand...
Click to collapse
Well, you're asking a lot of questions that have been already answered, so here's some quick answers.
1. Flashing the modules won't hurt.
2. Safestrap lives in separate directory on your internal storage. As long as you don't wipe the internal storage, it'll still be there. However, if you flash a stock ROM into the stock slot, then Safestrap won't be run during boot and can't be activated.
3. Yes, you can always flash an OEM stock ROM. Factory images from Samsung won't set the Knox Warranty Void flag. This does NOT mean that you can downgrade to an earlier release.
4. OTAs won't brick the phone - they'll fail if you have modified anything that the OTA will be patching.
5. You should only restore user apps and data. You must have the restorecon fix for that to work. Restoring system apps is pretty risky.
None of these are new questions or new answers. Yes, there's a lot to read here, but you really need to spend the time.
k1mu said:
Well, you're asking a lot of questions that have been already answered, so here's some quick answers.
1. Flashing the modules won't hurt.
2. Safestrap lives in separate directory on your internal storage. As long as you don't wipe the internal storage, it'll still be there. However, if you flash a stock ROM into the stock slot, then Safestrap won't be run during boot and can't be activated.
3. Yes, you can always flash an OEM stock ROM. Factory images from Samsung won't set the Knox Warranty Void flag. This does NOT mean that you can downgrade to an earlier release.
4. OTAs won't brick the phone - they'll fail if you have modified anything that the OTA will be patching.
5. You should only restore user apps and data. You must have the restorecon fix for that to work. Restoring system apps is pretty risky.
None of these are new questions or new answers. Yes, there's a lot to read here, but you really need to spend the time.
Click to expand...
Click to collapse
Oh I remember you! You made the Saferoot method I used. Sorry for asking some dumb questions, I just wanted verification for 1, 3, and 4. I'll have to search for the restorecon fix. I'll be flashing Eclipse because I was only looking for an AOSP experience and Hyperdrive has more than I need (leading to larger rom size). The rom is going to go through a big update sometime this weekend so I'll wait for the update.
DaGamer12345 said:
Oh I remember you! You made the Saferoot method I used. Sorry for asking some dumb questions, I just wanted verification for 1, 3, and 4. I'll have to search for the restorecon fix. I'll be flashing Eclipse because I was only looking for an AOSP experience and Hyperdrive has more than I need (leading to larger rom size). The rom is going to go through a big update sometime this weekend so I'll wait for the update.
Click to expand...
Click to collapse
Whew. I thought "Oh I remember you" was going to be followed by ".. you're that jerk that... " :laugh:
Have a good weekend.
remainnameless said:
Carrier: Verizon
Device: Samsung Galaxy S4 (MK2)
Custom ROM: Hyperdrive ROM
Phone is rooted, and Safestrap is installed and working flawlessly
I see this question posted all the time, but I'm reading a lot of conflicting information. As I've been searching around the net for a solid (and up-to-date) answer, I was wondering if there was a definitive answer to the following question:
Can I flash a custom ROM to the stock slot using Safestrap, remove the stock ROM from the phone, and keep the backup on my PC for later restoration?
I would assume that I should do the following:
1) Make a backup of the stock ROM (using Safestrap)
2) Wipe the Stock slot
3) Install/Restore custom ROM to the Stock slot
Am I correct in assuming this?
If there are any issues, I'd love to hear why. I'm still trying to figure out all the info. If there are any benefits/drawbacks, I'd also love to hear those. I'd consider myself a "conservative" user. I do nothing with themes and major modifications.
Thank you for any advice!
I apologize if this question has been answered elsewhere.
Click to expand...
Click to collapse
I just installed hyperdrive to the stock slot and everything works perfect.
I am about at my wits end...Rewind to two days ago...
Order of events:
1. Received my new S4 in the mail a few days ago to replace my old S3. I received the S4 fully updated with the NC5 OTA (yeah, I know, bad juju).
2. So I followed Surge's downgrade thread HERE and am now downgraded to the MK2 build, but with no sound and the telephone/calls app does not work.
3. I then downloaded GooManager and installed the OpenRecovery from TWRP, and it said it installed correctly. However, now I CANNOT GET INTO RECOVERY no matter how I try (via VolUp+Home+Power or via "Reboot into recovery" from the GooManager app). It just goes into Download mode with an error at the top in re that says "Could not do normal boot"
4. At this point the phone just boot loops into Download mode. Cannot go into recovery or the MK2 Rom. I then have to reflash the MK2 downgrade files in order (downgrade, system, cache) in order to get a working phone again and I have now probably done this at least 8 times. It is getting old.
So, I am curious what I need to do now. I have gone through the MK2 downgrade process multiple times and tried again to no avail. I also tried flashing the TWRP .Tar file (directly via Odin) but no luck also --- Is there like a super/clean ODIN file I can use that will also reset the recovery image on the phone? I feel that is my main problem, then I can fix the sound/phone problems after that.
This thing is 10x harder to get on CM than the S3 which I had running CM within 2 hours of ownership. I'd appreciate any help to get me back on path.
FYI - I can install Safestrap 3.71/3.72 and get into those fine, but if I want a chance of running CM I will need a Loki recovery right? If so, I just do not see how I am going to get there.
My ultimate goal is a clean rom, and I was so used to CM on my S3 that I'd hate to part with that, but if there is a Safestrap-friendly ROM that is very clean/similar, then I will take that any day. Ready to be done with this - easiest way out.
--edit--
Found this...can I just follow these steps or is that only for people still on MDK?? http://wiki.cyanogenmod.org/w/Install_CM_for_jfltevzw
There's absolutely no way to get cm, aosp, or twrp on your device .
Sent from my SCH-I545 using Tapatalk
joshm.1219 said:
There's absolutely no way to get cm, aosp, or twrp on your device .
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Yeah, pretty sure I am convinced of that now. :crying:
So, should I upgrade to the rooted-NC5 (Surge's method), and THEN put a Safestrap-custom-ROM on, or just do it now running rooted-MK2?
crobs808 said:
Yeah, pretty sure I am convinced of that now. :crying:
So, should I upgrade to the rooted-NC5 (Surge's method), and THEN put a Safestrap-custom-ROM on, or just do it now running rooted-MK2?
Click to expand...
Click to collapse
Well it depends. If you stay on mk2 you can only run 4.3 roms but there's a lot of them. If you upgrade then you can run 4.4 roms but there's only a couple right now.
Sent from my SCH-I545 using Tapatalk
joshm.1219 said:
Well it depends. If you stay on mk2 you can only run 4.3 roms but there's a lot of them. If you upgrade then you can run 4.4 roms but there's only a couple right now.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I definitely want 4.4.x. I found THIS one called PurifieD (port by gogolie) which is supposed to be clean-ish. We'll see: http://www.androidfilehost.com/?fid=23487008491966540
-edit-
^ hmm, no mirrors may try Fox and Hound instead:
http://www.androidfilehost.com/?fid=23487008491966537
^ and again...no mirrors.
Is there a consolidated link list of SS-compatible ROMs for the S4, or do I have to hunt and peck through the forum?
n/m - found a list of 4.3 roms, but it looks like I will have to hunt for 4.4 roms individually.
Conclusion: Going to try this rom: http://forum.xda-developers.com/showthread.php?t=2596654
I think I will sleep well tonight (crosses fingers)
crobs808 said:
I definitely want 4.4.x. I found THIS one called PurifieD (port by gogolie) which is supposed to be clean-ish. We'll see: http://www.androidfilehost.com/?fid=23487008491966540
-edit-
^ hmm, no mirrors may try Fox and Hound instead:
http://www.androidfilehost.com/?fid=23487008491966537
^ and again...no mirrors.
Is there a consolidated link list of SS-compatible ROMs for the S4, or do I have to hunt and peck through the forum?
n/m - found a list of 4.3 roms, but it looks like I will have to hunt for 4.4 roms individually.
Conclusion: Going to try this rom: http://forum.xda-developers.com/showthread.php?t=2596654
I think I will sleep well tonight (crosses fingers)
Click to expand...
Click to collapse
only a handful, so not that hard to locate in dev forum. Until hashcode comes out with a safestrap for verizon that enables rom slot creation for custom rom installs on 4.4 base phones I know many of us are staying clear of kitkat.
good luck
So I have not used Safestrap since my Moto X days a few years back, and I am having problems installing a new ROM. Here are my steps, please tell me if things have changed because I got unexpected results.
1. While running stock NC5 (rooted+SS installed), copied custom ROM (SS-friendly FoxHound port by gigili) and SU over to my internal sdcard (do not have an external as I never needed one for the S3)
2. Booted into SS and created a ROM slot in rom-slot1
3. Gave it the nickname FoxHound
4. Selected that rom-slot to be active, then went into advanced Wipe, and did Data, Cache, System, Dalvik
5. Went back to the Install menu so I could install the new ROM but there were no files. Actually, I found out it wiped my StockRom slot even though I have made the rom-slot1 active. Why?
Anyway, now I am back to a wiped stock NC5 and have to do this all over again. Am I supposed to not do step 4 (wipe) after I create the ROM slot? and Am I supposed to just install the custom rom in the Stock slot?
Ugg forget it. I now tried flashing the custom ROM on the safe side without doing the WIPE step and just got a rom that looked identical to the stock except that DATA was broken. Forget this - I guess I just have to live with stock rooted, and modify/freeze apps.