I know they may seem like some dumb questions, but coming from the Galaxy Nexus, somethings have been somewhat different on the S4.
I rooted my MDK VZW S4 using this method by open1your1eyes0:
http://forum.xda-developers.com/showthread.php?t=2290798
I can not find this answer to this...I know I'm rooted, but is the bootloader also unlocked?
On the Nexus I had a second step after rooting that was necessary to unlock the bootloader. I don't see any additinal steps for the bootloader anywhere on the forum. I know ME7 does not have a bootloader unlock option, but I'm on MDK.
Next question...
I later flashed the official version of ClockworkMOD Tocuh Recovery which I've been told has the LOKI mod.
At this point can I flash a ROM exactly like I did on my NEXUS through the custom recovery?
I'm looking to flash:
http://forum.xda-developers.com/showthread.php?t=2384362
And my last question regarding back ups and Nandroids...
On my Nexus, my internal storage automatically was partitioned, so doing full wipes before flashing a new ROM never touched my nandroids, titanium backups, photos, etc...
Is this the same on the Galaxy S4 now, or should I be backing everything up to the extSDcard?
Thanks in advance. I really appreciate your help.
Your bootloader is not technically unlocked. Instead it has been bypassed through the "Loki" exploit. This makes no difference whatsoever to you as a user, though. You can flash new ROMs to your heart's content.
With regards to a wipe, when you wipe the system, cache, etc. through your recovery program it will only wipe the folders necessary to erase the OS, kernel, etc. Your downloaded data will be left intact as long as you don't put it in a directory that's used to store OS files.
ymDroid said:
I know they may seem like some dumb questions, but coming from the Galaxy Nexus, somethings have been somewhat different on the S4.
I rooted my MDK VZW S4 using this method by open1your1eyes0:
http://forum.xda-developers.com/showthread.php?t=2290798
I can not find this answer to this...I know I'm rooted, but is the bootloader also unlocked?
On the Nexus I had a second step after rooting that was necessary to unlock the bootloader. I don't see any additinal steps for the bootloader anywhere on the forum. I know ME7 does not have a bootloader unlock option, but I'm on MDK.
Next question...
I later flashed the official version of ClockworkMOD Tocuh Recovery which I've been told has the LOKI mod.
At this point can I flash a ROM exactly like I did on my NEXUS through the custom recovery?
I'm looking to flash:
http://forum.xda-developers.com/showthread.php?t=2384362
And my last question regarding back ups and Nandroids...
On my Nexus, my internal storage automatically was partitioned, so doing full wipes before flashing a new ROM never touched my nandroids, titanium backups, photos, etc...
Is this the same on the Galaxy S4 now, or should I be backing everything up to the extSDcard?
Thanks in advance. I really appreciate your help.
Click to expand...
Click to collapse
You Cannot unlock the bootloader. There is a workaround called loki that will allow you to install a Lokied recovery. Once you have custom recovery, which it seems you have done, installed then you can flash roms. Just be careful with your wipes to know for sure what you are wiping and be sure to make Nandroid backups to your external sdcard. You can then store a copy on your PC. I do all backups to external sdcard as internal space is limited.
Sent from my Hyperdriven SCH-I545 Dev Edition using Tapatalk 4.
So...just to confirm...
The official version of ClockworkMOD Tocuh Recovery 6.0.3.6 does have the Loki, correct?
Can I confirm this somewhere?
The exploit is in getting your custom recovery to run at all. If you can boot into CWM, Loki has already done its job.
Perfect
CrookedKnight said:
The exploit is in getting your custom recovery to run at all. If you can boot into CWM, Loki has already done its job.
Click to expand...
Click to collapse
Makes perfect sense now.
Thank you!
I flashed Bone 1.1.4 with no issues.
My question is regaridng my home screen.
I know custom launchers like NOVA allow you back up your home screen layouts and settings.
Is there anyway to back up your home screen layouts off of the stock launcher, or in this case the stock TouchWiz home screen layouts?
ymDroid said:
I flashed Bone 1.1.4 with no issues.
My question is regaridng my home screen.
I know custom launchers like NOVA allow you back up your home screen layouts and settings.
Is there anyway to back up your home screen layouts off of the stock launcher, or in this case the stock TouchWiz home screen layouts?
Click to expand...
Click to collapse
Titanium Backup. ROM Toolbox PRO also has an excellent back up app included.
Sent from my SCH-I545 using xda app-developers app
Mightycaptain said:
Titanium Backup. ROM Toolbox PRO also has an excellent back up app included.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
What feature on Titanium let's me back up my home screen layout?
ymDroid said:
What feature on Titanium let's me back up my home screen layout?
Click to expand...
Click to collapse
When you back up touch wiz home in tibu you can restore just data or the whole thing. Seems like I've done both and it worked out. Clear data from touch wiz home in application manager and you can get back to the default settings.
Sent from my SCH-I545 using xda app-developers app
Mightycaptain said:
When you back up touch wiz home in tibu you can restore just data or the whole thing. Seems like I've done both and it worked out. Clear data from touch wiz home in application manager and you can get back to the default settings.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Thank you for your help with this.
ymDroid said:
Thank you for your help with this.
Click to expand...
Click to collapse
No problem. It's what its all about right.
Sent from my SCH-I545 using xda app-developers app
Related
Currently have TWR recovery I flashed using goomanager but have been hearing bad thing about it. Can I just download Rom Manager from the play store and use it to flash clockwork or do I need to us another way to flash it ? Thanks !
If TWRP works fine for you then who cares what other people say or think about. I only run TWRP and have no issues with it.
Don't just go by what other people say, check out some videos on YouTube of ClockworkMod and see if it's for you. Very recently, an official CWM build appears to have become available so if you want to use that, it should be as simple as downloading ROM Manager and doing recovery setup.
I havent used TWR to flash anything yet just used it to to a backup of my stock rooted rom. Thanks for the replys.
mbh87 said:
If TWRP works fine for you then who cares what other people say or think about. I only run TWRP and have no issues with it.
Click to expand...
Click to collapse
I've ran both on multiple devices and i also prefer twrp. It's laid out nicer. Being able to wipe cache and dalvik in one shot or at least in one menu screen is way more convenient than them being separate options on separate screens.
sent from my Galaxy S4 using xda premium
+1 agree
Sent from my SCH-I545 using Tapatalk 2
Hello I'm new here how is everyone?
Okay here is my issue:
I have a Verizon Galaxy S4 its on Android 4.3 with the build ending in mj7. It is rooted via the vroot method. So I've been looking around for a custom recovery so I could flash a ROM (preferably CM 11). I've came across a safestrap version that worked with my build (3.70). I downloaded the apk, installed it, installed the recovery and booted into recovery fine. I made my back up via the tool and also have a Samsung kies back up from before my root. So after I backed up my data I did my data wipe of the phone. The generic wipe my SD card and the data in it are good. Well long story short the phone turned off without installing a new ROM. Well phone powers on and stuck on Samsung logo with the open lock on it.
Was wondering can I..
A: Somehow force the safestrap to start via adb and restore my back up?
B: restore my back up through adb itself?
C: Use Odin to restore my stock firmware somehow even while rooted?
D: Sideload CM from adb?
E: I'm out of luck buy a new phone?
Thank you.
Fiftysilver said:
Hello I'm new here how is everyone?
Okay here is my issue:
I have a Verizon Galaxy S4 its on Android 4.3 with the build ending in mj7. It is rooted via the vroot method. So I've been looking around for a custom recovery so I could flash a ROM (preferably CM 11). I've came across a safestrap version that worked with my build (3.70). I downloaded the apk, installed it, installed the recovery and booted into recovery fine. I made my back up via the tool and also have a Samsung kies back up from before my root. So after I backed up my data I did my data wipe of the phone. The generic wipe my SD card and the data in it are good. Well long story short the phone turned off without installing a new ROM. Well phone powers on and stuck on Samsung logo with the open lock on it.
Was wondering can I..
A: Somehow force the safestrap to start via adb and restore my back up?
B: restore my back up through adb itself?
C: Use Odin to restore my stock firmware somehow even while rooted?
D: Sideload CM from adb?
E: I'm out of luck buy a new phone?
Thank you.
Click to expand...
Click to collapse
I beg all you new guys spend a couple hours reading some threads here...If I had a dollar every time some one posted about issues with trying roms NOT compatible with SafeStrap .
Again...no cm or asop base roms will work with safestrap...
Sent from my SCH-I545 using XDA Premium 4 mobile app
Fiftysilver said:
Hello I'm new here how is everyone?
Okay here is my issue:
I have a Verizon Galaxy S4 its on Android 4.3 with the build ending in mj7. It is rooted via the vroot method. So I've been looking around for a custom recovery so I could flash a ROM (preferably CM 11). I've came across a safestrap version that worked with my build (3.70). I downloaded the apk, installed it, installed the recovery and booted into recovery fine. I made my back up via the tool and also have a Samsung kies back up from before my root. So after I backed up my data I did my data wipe of the phone. The generic wipe my SD card and the data in it are good. Well long story short the phone turned off without installing a new ROM. Well phone powers on and stuck on Samsung logo with the open lock on it.
Was wondering can I..
A: Somehow force the safestrap to start via adb and restore my back up?
B: restore my back up through adb itself?
C: Use Odin to restore my stock firmware somehow even while rooted?
D: Sideload CM from adb?
E: I'm out of luck buy a new phone?
Thank you.
Click to expand...
Click to collapse
You should be able to use Odin to get back to stock MJ7. There are guides in the development section. Just so you know, you can't flash Cm 11 with Safestrap. As far as I know, the only ROM that works with MJ7 and Safestrap is Hyperdrive 11. Even if you're on an older base, you would only be able to flash TW based ROMs with Safestrap.
My suggestion, do A LOT of reading. There's tons of info on these boards.
Sent from my NCC 1701 Using Tapatalk 4
C; Google how to Odin back to stock.
Have you tried to boot the phone into recovery and restore your backup with SS? I never used SS but if you can make a backup I'm sure you can restore one as well
Sent from my SCH-I545 using Xparent Skyblue Tapatalk 2
I beg all you new guys spend a couple hours reading some threads here...If I had a dollar every time some one posted about issues with trying roms NOT compatible with SafeStrap .
Again...no cm or asop base roms will work with safestrap...
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You are correct and that is my mistake.
You should be able to use Odin to get back to stock MJ7. There are guides in the development section. Just so you know, you can't flash Cm 11 with Safestrap. As far as I know, the only ROM that works with MJ7 and Safestrap is Hyperdrive 11. Even if you're on an older base, you would only be able to flash TW based ROMs with Safestrap.
My suggestion, do A LOT of reading. There's tons of info on these boards.
Sent from my NCC 1701 Using Tapatalk 4
Click to expand...
Click to collapse
C; Google how to Odin back to stock.
Have you tried to boot the phone into recovery and restore your backup with SS? I never used SS but if you can make a backup I'm sure you can restore one as well
Sent from my SCH-I545 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
It worked. Didn't the first time but tried ODIN again with a stock mj7 ROM I found here.
I restored back to factory and implemented vroot once again, swapped out the Chinese (Korean?) superuser for our good old traditional one. I then re-installed safestrap apk and re-installed the recovery. I went in and found my back up I made earlier today and restored my phone back to how it exactly was before all this mess started.
Lesson learned I'll do my due-diligence next time and just keep my root till I can find a solid method to getting CM/Stock android on my Galaxy S4.
I'll try Hyperdrive 11
Thank you guys for all your help.;
Fiftysilver said:
I restored back to factory and implemented vroot once again
Click to expand...
Click to collapse
Why vroot? There is an open rooting technique - http://forum.xda-developers.com/showthread.php?t=2565758
Seems like you've got more reading to do.
So I had originally had TWRP/Hyperdrive on my phone, and switched to CWM/Cyanogenmod. I noticed now that I seem to have two different recoveries on my phone, because if I hold up+home+power I can go to a different version of CWM Recovery than if I use the Rom Manager app to boot into recovery. How would I rectify this? Would it involve wiping the /boot partition? I don't know where/how recoveries are stored so I don't understand how I can have two.
Doing a fresh install of a ROM has not resolved this by the way. And actually currently, I can't hold the buttons and boot into recovery at all, it gets stuck on the Samsung logo. I can only get into recovery via Rom Manager or Reboot options if I'm in android.
Markstache said:
So I had originally had TWRP/Hyperdrive on my phone, and switched to CWM/Cyanogenmod. I noticed now that I seem to have two different recoveries on my phone, because if I hold up+home+power I can go to a different version of CWM Recovery than if I use the Rom Manager app to boot into recovery. How would I rectify this? Would it involve wiping the /boot partition? I don't know where/how recoveries are stored so I don't understand how I can have two.
Doing a fresh install of a ROM has not resolved this by the way. And actually currently, I can't hold the buttons and boot into recovery at all, it gets stuck on the Samsung logo. I can only get into recovery via Rom Manager or Reboot options if I'm in android.
Click to expand...
Click to collapse
I would just Odin back to stock MDK and start fresh and choose whichever recovery suits you. I had to do the same a while back myself
Sent from my SCH-I545 using Tapatalk
Mistertac said:
I would just Odin back to stock MDK and start fresh and choose whichever recovery suits you. I had to do the same a while back myself
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I've done that so many times.
Markstache said:
I've done that so many times.
Click to expand...
Click to collapse
My fault ...I see where you adressed that in the last part of your post. I'm no expert either on how recoveries are stored and executed.
I would think though that flashing stock mdk would fix this as it did for me. I used ROM manager to install cwm then I flashed Philz and haven't had a problem since. Hope someone else can help you.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
My fault ...I see where you adressed that in the last part of your post. I'm no expert either on how recoveries are stored and executed.
I would think though that flashing stock mdk would fix this as it did for me. I used ROM manager to install cwm then I flashed Philz and haven't had a problem since. Hope someone else can help you.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
The only way to fix is to Odin back to factory image and start over.
Sent from my SCH-I545 using xda app-developers app
cbmggm said:
The only way to fix is to Odin back to factory image and start over.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Yea that's what I said before too but the op said they've done that many times with no luck...
Sent from my SCH-I545 using Tapatalk
cbmggm said:
The only way to fix is to Odin back to factory image and start over.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
That's what I would have figured would fix it, because I'm pretty sure that's supposed to wipe /boot, but I found out I cannot flash kernels on my phone for some reason and when having to fix softbricks while experimenting with why it doesn't work and flashing different kernels, I had to do that whole process so many times I can go from softbrick back to where I'm at now in about 20 minutes.
Is your device in factory mode when using touchwiz roms?
jamesd1085 said:
Is your device in factory mode when using touchwiz roms?
Click to expand...
Click to collapse
I have no idea what you mean, and I'm not using anything touchwiz based anymore.
Markstache said:
I have no idea what you mean, and I'm not using anything touchwiz based anymore.
Click to expand...
Click to collapse
OK...well try something real quick for me...use a root manager and open your efs folder...are the files still there...if not your efs folder has been formatted to the incorrect format... That would explain funky recovery issues and not being able to flash kernels...that's the only things I can think of
jamesd1085 said:
OK...well try something real quick for me...use a root manager and open your efs folder...are the files still there...if not your efs folder has been formatted to the incorrect format... That would explain funky recovery issues and not being able to flash kernels...that's the only things I can think of
Click to expand...
Click to collapse
It sure is there and has files in it.
What is that folder? Should I delete the contents?
Markstache said:
It sure is there and has files in it.
What is that folder? Should I delete the contents?
Click to expand...
Click to collapse
Definitely don't delete your efs folder. Actually it's good practice to back it up
Sent from my SCH-I545 using Tapatalk
Markstache said:
It sure is there and has files in it.
What is that folder? Should I delete the contents?
Click to expand...
Click to collapse
No!!!!...you will lose your number and all data capability...just wanted to make sure everything was still mounting properly... I'm at a loss as to what else could be causing your issues
Markstache said:
I have no idea what you mean, and I'm not using anything touchwiz based anymore.
Click to expand...
Click to collapse
I'd find someone like Philz or a TWRP compiler to ask if u haven't already gone that route. I'm sure one of them will know. Hopefully [emoji41]
Sent from my SCH-I545 using Tapatalk
Something just occured to me. When flashing back to stock with odin I always use the nowipe image because it's all I can find. I think that technically means boot was never wiped. Would that explain my phenomena? Also where to find stock that will wipe?
Markstache said:
Something just occured to me. When flashing back to stock with odin I always use the nowipe image because it's all I can find. I think that technically means boot was never wiped. Would that explain my phenomena? Also where to find stock that will wipe?
Click to expand...
Click to collapse
I've always used this one
http://forum.xda-developers.com/showthread.php?t=2289325
I'm not 100% if its no wipe as it doesn't say. But it you haven't tried this one yet may be worth a shot
Sent from my SCH-I545 using Tapatalk
Mistertac said:
I've always used this one
http://forum.xda-developers.com/showthread.php?t=2289325
I'm not 100% if its no wipe as it doesn't say. But it you haven't tried this one yet may be worth a shot
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
^^^this should fix you up...but backup everything you can to external SD or computer...when it says full wipe its no joke
Mistertac said:
I've always used this one
http://forum.xda-developers.com/showthread.php?t=2289325
I'm not 100% if its no wipe as it doesn't say. But it you haven't tried this one yet may be worth a shot
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
So I flashed that one via Odin, followed the guide to root and everything step by step, and now that I'm back on stock kernel and want to install CWM Recovery, I downloaded Rom Manager and hit install recovery and it says everything worked but if I boot into recovery it's just the android stock recovery.
EDIT: Another thing I thought of. Could the fact that at one point I used this method to install CWM recovery on my phone have caused there to be two different recoveries running parallel?
http://galaxys4root.com/galaxy-s4-r...on-att-or-verizon-galaxy-s4-sgh-i337sch-i545/
UPDATE: Using this method I installed the latest version of CWM Recovery Touch but Rom Manager still thinks the normal version is installed, though now if I hit reboot to recovery from the app it actually takes me to the touch instead of a separate one. Is the app dumb or do I still have an issue? Also I cannot install kernels without tripping the count and having my phone tell me I need to go to a verizon store.
http://wiki.cyanogenmod.org/w/Install_CM_for_jfltevzw
Markstache said:
So I flashed that one via Odin, followed the guide to root and everything step by step, and now that I'm back on stock kernel and want to install CWM Recovery, I downloaded Rom Manager and hit install recovery and it says everything worked but if I boot into recovery it's just the android stock recovery.
EDIT: Another thing I thought of. Could the fact that at one point I used this method to install CWM recovery on my phone have caused there to be two different recoveries running parallel?
http://galaxys4root.com/galaxy-s4-r...on-att-or-verizon-galaxy-s4-sgh-i337sch-i545/
UPDATE: Using this method I installed the latest version of CWM Recovery Touch but Rom Manager still thinks the normal version is installed, though now if I hit reboot to recovery from the app it actually takes me to the touch instead of a separate one. Is the app dumb or do I still have an issue? Also I cannot install kernels without tripping the count and having my phone tell me I need to go to a verizon store.
http://wiki.cyanogenmod.org/w/Install_CM_for_jfltevzw
Click to expand...
Click to collapse
ROM manager may actually be the issue.
And as far as installing kennels I've never had an issue myself. The last link you posted is about flashing the md2 kernel in order to root the phone. Do you mean that?? Or installing say a KToonsez kernel after you're already rooted and have your custom recovery?
Sent from my SCH-I545 using Tapatalk
Mistertac said:
ROM manager may actually be the issue.
And as far as installing kennels I've never had an issue myself. The last link you posted is about flashing the md2 kernel in order to root the phone. Do you mean that?? Or installing say a KToonsez kernel after you're already rooted and have your custom recovery?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
As in installing a KT kernel after rooting and having a custom recovery and ROM on my phone. Right now I have three 3/22 nightly cyanogen up and running but as soon as I install kt it trips the Verizon security and on have to flash back to stock kernel to use my phone. Booting into Odin and canceling out to restart does not let me get past the yellow triangle
I screwed up my stock slot and was wondering if its safe to reset it as long as i disable OTA IMMEDIATELY after said restore?
I do not have any other roms on my device.
Bootloader is locked.
I DO HAVE SAFESTRAP ACTIVE (what im worried will screw up the restore).
I am rooted.
Yes, my device slot is beyond manual repair (system ui crashes with unknown error, libwebview crashes with missing index error, etc.).
Moral of the story: don't fall asleep ontop of your tablet whilst wakelock is active and es filemanager is open.
I just need to know if there is any risk of bricking my tablet or worse, efusing it.
Yes.
terra_byte_tech said:
I screwed up my stock slot and was wondering if its safe to reset it as long as i disable OTA IMMEDIATELY after said restore?
I do not have any other roms on my device.
Bootloader is locked.
I DO HAVE SAFESTRAP ACTIVE (what im worried will screw up the restore).
I am rooted.
Yes, my device slot is beyond manual repair (system ui crashes with unknown error, libwebview crashes with missing index error, etc.).
Moral of the story: don't fall asleep ontop of your tablet whilst wakelock is active and es filemanager is open.
Click to expand...
Click to collapse
So you didn't backup your stock slot, i.e. you can not restore that backup via Safestrap?
Using an official Amazon file for this is quite risky.
Would be interesting if someone would've a Safestrap backup of the Fire OS you need - which Fire OS and Safestrap versions are on your HDX anyway?
Cl4ncy said:
So you didn't backup your stock slot, i.e. you can not restore that backup via Safestrap?
Using an official Amazon file for this is quite risky.
Would be interesting if someone would've a Safestrap backup of the Fire OS you need - which Fire OS and Safestrap versions are on your HDX anyway?
Click to expand...
Click to collapse
I'm using the built in restore utility (accessed by holding down volume buttons on boot). Not safestrap's.
Sent from my KFTHWI using XDA Premium 4 mobile app
EncryptedCurse said:
Yes.
Click to expand...
Click to collapse
Do you mean: "yes, it's safe to restore" Or "yes, there is risk involved"
Sent from my KFTHWI using XDA Premium 4 mobile app
terra_byte_tech said:
Do you mean: "yes, it's safe to restore" Or "yes, there is risk involved"
Sent from my KFTHWI using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You will likely loose access to Safestrap recovery if you to a 'factory reset' from stock recovery. Even if it does work you likely won't get to a usable version of FireOS. As I recall adb and other forms of tethered communication are difficult/impossible with Safestrap v3 (you didn't say) so restoring an image captured elsewhere will be a challenge. There are reports OSX can communicate via adb in Safestrap v4. Haven't tested that. Would have to track down the post to see if it applies; need more details before investing the effort.
You don't have a lot of good options. Best keep reading. In your shoes I would NOT do a factory reset as it's an extreme long shot that will remove any hope of recovery if it does not work.
terra_byte_tech said:
I'm using the built in restore utility (accessed by holding down volume buttons on boot). Not safestrap's.
Sent from my KFTHWI using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You should've clarified that you were talking about a factory reset. I thought you were just restoring a backup within Safestrap.
Frankly, I'm not sure it'll solve anything. A factory reset doesn't just magically fix everything; it will only wipe the /data partition, so any changes you made to /system will still be there.
If you can still boot into Safestrap, I'd try getting a stock system image onto the device and flashing it from there.
terra_byte_tech said:
I'm using the built in restore utility (accessed by holding down volume buttons on boot). Not safestrap's.
Click to expand...
Click to collapse
EncryptedCurse said:
You should've clarified that you were talking about a factory reset. I thought you were just restoring a backup within Safestrap.
Frankly, I'm not sure it'll solve anything. A factory reset doesn't just magically fix everything; it will only wipe the /data partition, so any changes you made to /system will still be there.
If you can still boot into Safestrap, I'd try getting a stock system image onto the device and flashing it from there.
Click to expand...
Click to collapse
To further clarify flashing any stock rom is risky in Safestrap. Best use one from here. Your bigger problem is getting anything, including an image file, on your device given you can only boot into Safestrap.
Davey126 said:
To further clarify flashing any stock rom is risky in Safestrap. Best use one from here. Your bigger problem is getting anything, including an image file, on your device given you can only boot into Safestrap.
Click to expand...
Click to collapse
okay, so i figured out my version via build.prop and im running 13.3.2.5
is it safe to restore using the 13.3.2.6 file in the post you mentioned?
thank you for your patience.
i recently rooted my Galaxy S4 verizon SCH-I545 5.0.1 My main reason for doing so is because i want to install CM12 (to improve battery and no bloatware) but need to back up my stock ROM before wiping anything, so i can restore if anything gets messed up but when i installed CWM via ROM manager app , i booted in recovery only to discover that i didn't have the option to back up my stock ROM...nothing that says "back up and restore" or anything remotely close...so after alot of reading a searching it looks like TWRP was the one that most suggested for my phone. My question is, can i just use Flashify and flash TWRP over the existing CWM?? will this mess anything up or brick my phone??? please help and excuse my ignorance
neilson85 said:
i recently rooted my Galaxy S4 verizon SCH-I545 5.0.1 My main reason for doing so is because i want to install CM12 (to improve battery and no bloatware) but need to back up my stock ROM before wiping anything, so i can restore if anything gets messed up but when i installed CWM via ROM manager app , i booted in recovery only to discover that i didn't have the option to back up my stock ROM...nothing that says "back up and restore" or anything remotely close...so after alot of reading a searching it looks like TWRP was the one that most suggested for my phone. My question is, can i just use Flashify and flash TWRP over the existing CWM?? will this mess anything up or brick my phone??? please help and excuse my ignorance
Click to expand...
Click to collapse
Sorry not an option
Sent from my SM-T800 using XDA Free mobile app
Unless your bootloader is MDK you can't have TWRP,CWM or CM.
fudplayers said:
Unless your bootloader is MDK you can't have TWRP,CWM or CM.
Click to expand...
Click to collapse
So how can I tell if my boot loader is MDK or not?? I was able to put CWM on there threw the "ROM manager" app but like I said, lacks in options (no back up/restore) options....is there anything I can do?
Sent from my SCH-I545 using XDA Free mobile app
In your phone settings, about phone, it'll tell you what BL you're on. If you aren't on MDK and haven't taken the OF1 and OC1 update then you'd be safe with busybox and safestrap.
Looks like I have MDF
Sent from my SCH-I545 using XDA Free mobile app
Keep it! You can install CM, and whichever recovery you want. I never had the MDK phone so I was limited by recoveries and ROMs. You could use TWRP for your recovery. You're able to flash AOSP ROMs. I would keep your phone on MDK at all costs.
fudplayers said:
Keep it! You can install CM, and whichever recovery you want. I never had the MDK phone so I was limited by recoveries and ROMs. You could use TWRP for your recovery. You're able to flash AOSP ROMs. I would keep your phone on MDK at all costs.
Click to expand...
Click to collapse
Ok awesome, I wasn't sure if I was looking at the right thing or not.
In my settings it says...security software version: MDF V1.0 release 4
VPN V1.4 release 4
Is that my boot loader version or am I looking at the wrong thing?
Sent from my SCH-I545 using XDA Free mobile app
It should show in your build number under about phone. It'll be the last digits of that number.
fudplayers said:
It should show in your build number under about phone. It'll be the last digits of that number.
Click to expand...
Click to collapse
OC1 is what it is ...that's not good, is it?
Sent from my SCH-I545 using XDA Free mobile app
Well, I can't get King Root to work so I'm currently not rooted and am on OC1. I'd hold off on taking the next update, OF1 because there is no root for it yet. There's a thread on it in the general area that can explain it better than I.
fudplayers said:
Well, I can't get King Root to work so I'm currently not rooted and am on OC1. I'd hold off on taking the next update, OF1 because there is no root for it yet. There's a thread on it in the general area that can explain it better than I.
Click to expand...
Click to collapse
I rooted using the desktop version of kingroot (all in Chinese) and it worked for me...did it about a week ago. And yes, I'm holding off on the OTA update for that very reason but it still keeps popping up...super annoying! I really appreciate your help on this...I'm pretty new to all this so thanks for being patient and not ridiculing me bc I'm a "noob" lol ...everyone has to start somewhere though
Sent from my SCH-I545 using XDA Free mobile app
No problem, I'm not sure if you wanted to but SDM system app is the update app I'm pretty sure. You could freeze that in Titanium Backup and it should keep the update from appearing. I'm going through that but I'm not rooted so I can't do anything about it. It's all good, if I can help I try to and you have to start somewhere, if it has anything to do with just about any phone, you'll find on XDA.
fudplayers said:
No problem, I'm not sure if you wanted to but SDM system app is the update app I'm pretty sure. You could freeze that in Titanium Backup and it should keep the update from appearing. I'm going through that but I'm not rooted so I can't do anything about it. It's all good, if I can help I try to and you have to start somewhere, if it has anything to do with just about any phone, you'll find on XDA.
Click to expand...
Click to collapse
Yes, getting rid of this update would help a lot...I don't want to accidentally hit the Update button... I tried looking up ways to remove it before but got nowhere, I'll definitely try your method
Sent from my SCH-I545 using XDA Free mobile app
I did want to mention if you're really new that I'd be careful with the apps. Generally it's not good to uninstall or delete system apps and sometimes Google apps are the same way. A lot of times but not always, you can freeze those and be alright, other times it'll make your phone go crazy so I'd check out the posts on the safe apps to freeze. Another good thing about freezing them is if you have any issue, just unfreeze those.
fudplayers said:
I did want to mention if you're really new that I'd be careful with the apps. Generally it's not good to uninstall or delete system apps and sometimes Google apps are the same way. A lot of times but not always, you can freeze those and be alright, other times it'll make your phone go crazy so I'd check out the posts on the safe apps to freeze. Another good thing about freezing them is if you have any issue, just unfreeze those.
Click to expand...
Click to collapse
That's for the tip! I did read that in a few post in my journey. I need to find a list of safe stock apps that I can delete or freeze (like story album and amazon kindle) for my S4 ...I still need to get TB pro so I can do all that. Thanks again!
Sent from my SCH-I545 using XDA Free mobile app
Hilp.root galaxy s4 5.0.1
neilson85 said:
OC1 is what it is ...that's not good, is it?
Sent from my SCH-I545 using XDA Free mobile app
Click to expand...
Click to collapse
sorry mate, can't do cwm or twrp or cm.
Of1 rooted, roll back to MDK?
I have vzw s4 rooted with odin on OF1 and took the 5.0.1 OTA update. Is it possible to rollback to MDK or earlier version of Android so i can install TWRP or CWM, to be able to flash whatever custom rom i choose? Like do i need to downgrade say to 4.3 so i can upgrade to 6.0 cm13? If this is at all possible which android should i downgrade to?
Similar question here. I have a Verizon S4 (SCH-I545) and am on OF1. I just did a full factory restore using the recovery assistant software, I did not get an option of a version. From what I have been reading, it sounds like there is no way to get back to an earlier version, is that really true? I find it very hard to find current information, most of what I dig up seems to be dated. I just rooted the phone. All I really want is to install the AOSP ROM. I don't care what hoops I have to jump through, if only there is a path! I have tried Odin but keep getting an error that again I have not found any useful info on.
Rich