Hi all,
I previously had my GS4 rooted on JellyBean, running the stock ROM and ClockworkMod. I upgraded my phone with the Verizon update to 4.4.2 when the update came out. I am now on the NC5 build. I am now trying to root my phone again, to run a different ROM. I still have Rom Manager and SuperSU on my phone from the last root.
I tried using Towelroot yesterday. It said the root was successful. I was able to go into Rom Manager and update CWM, which also said it flashed successfully. SuperSU is working. However, when I try to boot into CWM, it boots into the stock (I think) recovery. I'm trying to run a nandroid backup before I do anything drastic.
Do I have to wipe my device, and start fresh? It seems that CWM is installed, but the stock recovery is overriding it. Sorry if this is a noob-ish question. I've been out of the Root game since my Incredible.
Leach0789 said:
Hi all,
I previously had my GS4 rooted on JellyBean, running the stock ROM and ClockworkMod. I upgraded my phone with the Verizon update to 4.4.2 when the update came out. I am now on the NC5 build. I am now trying to root my phone again, to run a different ROM. I still have Rom Manager and SuperSU on my phone from the last root.
I tried using Towelroot yesterday. It said the root was successful. I was able to go into Rom Manager and update CWM, which also said it flashed successfully. SuperSU is working. However, when I try to boot into CWM, it boots into the stock (I think) recovery. I'm trying to run a nandroid backup before I do anything drastic.
Do I have to wipe my device, and start fresh? It seems that CWM is installed, but the stock recovery is overriding it. Sorry if this is a noob-ish question. I've been out of the Root game since my Incredible.
Click to expand...
Click to collapse
I believe when you accept the Verizon OTA update it locks down custom recoveries like CWM/TWRP and the only option is SafeStrap.
scrillakev said:
I believe when you accept the Verizon OTA update it locks down custom recoveries like CWM/TWRP and the only option is SafeStrap.
Click to expand...
Click to collapse
Ah ha. Thanks for the reply. So can I proceed with installing SafeStrap, or do I need to uninstall CWM first?
Leach0789 said:
Ah ha. Thanks for the reply. So can I proceed with installing SafeStrap, or do I need to uninstall CWM first?
Click to expand...
Click to collapse
Yea if your on a Verizon s4 running any build after MDK... which you are... SafeStrap is your only option.
Hard to say what that will do to your phone after trying to install CWM.... usually it just soft bricks it and you need to Odin back to stock...
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Yea if your on a Verizon s4 running any build after MDK... which you are... SafeStrap is your only option.
Hard to say what that will do to your phone after trying to install CWM.... usually it just soft bricks it and you need to Odin back to stock...
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I just started the process of installing SafeStrap, but maybe I will wait until I'm home from work, in case I need to Odin..
Leach0789 said:
I just started the process of installing SafeStrap, but maybe I will wait until I'm home from work, in case I need to Odin..
Click to expand...
Click to collapse
May be a good idea just in case. I've seen some on here do the same as you with ROM manager and once they rebooted they were brought to the unauthorized software detected screen.... And without a recovery and a backup already made you'd be out of luck.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
May be a good idea just in case. I've seen some on here do the same as you with ROM manager and once they rebooted they were brought to the unauthorized software detected screen.... And without a recovery and a backup already made you'd be out of luck.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
It would probably be smart to remove CWM with Odin before attempting SafeStrap, correct? Is there a specific thread for removing CWM from a Verizon S4? I searched around but couldn't find anything specific to the S4.
Edit: I found a guide on NasirTech. Looks like that will work.
Leach0789 said:
It would probably be smart to remove CWM with Odin before attempting SafeStrap, correct? Is there a specific thread for removing CWM from a Verizon S4? I searched around but couldn't find anything specific to the S4.
Edit: I found a guide on NasirTech. Looks like that will work.
Click to expand...
Click to collapse
Well it didn't actually install it since your kernel doesn't allow for it now but what I would do is just use Odin and start over. Can use a No Wipe file and keep all your stuff.
You could try the method you found... I'm just not familiar with it.
Hard to say really how it will act. Maybe you'll have no issues at all just be able to install SafeStrap. Maybe you'll be able to install it but then it won't boot properly into it... who knows. Both have happened to me with my recovery ( CWM ),.. and using Odin was the only thing that helped.
Good luck .. I'm sure you'll get it going
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Well it didn't actually install it since your kernel doesn't allow for it now but what I would do is just use Odin and start over. Can use a No Wipe file and keep all your stuff.
You could try the method you found... I'm just not familiar with it.
Hard to say really how it will act. Maybe you'll have no issues at all just be able to install SafeStrap. Maybe you'll be able to install it but then it won't boot properly into it... who knows. Both have happened to me with my recovery ( CWM ),.. and using Odin was the only thing that helped.
Good luck .. I'm sure you'll get it going
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Thanks! Would you mind helping me find a correct no-wipe file? I found a couple files, but since I'm a new user I can't post links here, so I can't ask anyone if its the correct file or not!
Leach0789 said:
Thanks! Would you mind helping me find a correct no-wipe file? I found a couple files, but since I'm a new user I can't post links here, so I can't ask anyone if its the correct file or not!
Click to expand...
Click to collapse
Here you go!
http://forum.xda-developers.com/showthread.php?t=2735172
Yup... Tulsa you're quick!! Lol
Grab the NC5 No Wipe...
Sent from my SCH-I545 using Tapatalk
Tulsadiver said:
Here you go!
http://forum.xda-developers.com/showthread.php?t=2735172
Click to expand...
Click to collapse
Thanks! You guys rock.
Related
Got a s4 today, followed the root guide here, using mdk pre release kernel. Did not unlock the boot loader. Loaded hyperdrive and after loading everything did the reboot. left me at the black samsung screen with an unlocked padlock and custom underneath. i can get into recovery and download. but no matter what i do will not progress screens (even tried full cache, dalvic, system, and data wipe and reloaded Hyperdrive. same results)
Should i re flash back to stock and try the entire process over again? if so, links please
also, what did i do to soft brick my phone? for future avoidance
and whats the difference between mdk and me7?
You probably got a bad download of the rom. Its a good idea to verify the md5 after its been downloaded. Once you can get a good download of the rom you dont need to odin back you can flash the rom in recovery and youll be good to go. The me7 ota is the newest firmware, has a few nice changes but it also has a non exploitable boot loader so you cant run a custom recovery on it.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
You probably got a bad download of the rom. Its a good idea to verify the md5 after its been downloaded. Once you can get a good download of the rom you dont need to odin back you can flash the rom in recovery and youll be good to go. The me7 ota is the newest firmware, has a few nice changes but it also has a non exploitable boot loader so you cant run a custom recovery on it.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
To clarify, your suggesting re downloading rls8, and try flashing that. Then, if that doesn't work, re flash the stock kernel (basically go through the Odin root guide again?)
Thanks!
Redownload rls8 verify the md5 checksum to make sure its not another bad download and then flash. As long as you can get into custom recovery of your choice and the download is good theres no reaaon it shouldnt work.
Sent from my SCH-I545 using Tapatalk 2
correct md5sum, same results.
both odin'd kernels have no effect, same boot problem. anyone know a fix?
Hopefully someone will. Same problem. Putting my phone back to stock rooted MDK works. The minute I try to flash Hyperdrive 8 and 8.1, it boots fine, then hangs on a restart.
Atleast, Will verizon exchange the phone seeing this?
Your mistake, why should Verizon replace something you caused.
Did you make a nandroid of the stock Rom prior to flashing?
Sent from my SCH-I545 using Tapatalk 4
Addiso said:
Your mistake, why should Verizon replace something you caused.
Did you make a nandroid of the stock Rom prior to flashing?
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
and yet no one has yet been able to pinpoint what mistake i made in installing a rom i've used for 12 months (s3) and installing a new version on a new phone while following every instruction to the letter, suddenly ****s on me. so please, enlighten me, what mistake did i make?
You didn't make a mistake. Chances are, you just used the wrong recovery. I spent 7 hours last night trying to fix my phone. I factory reset this morning to the stock MDK and re-rooted and figured out how to use ADB to install the Clockwork Mod Recovery. It's difficult to get started and figure out how to install and use it, but there are resources out there that will help you figure it out. I reinstalled the new 8.1 Hyperdrive with CWM recovery and was delighted when the ROM actually rebooted without fuss. It did hang on the Custom unlock screen long enough to make me nervous though. Figure out ADB and add CWM. It will work.
Edit for your steps: Reinstall the stock MDK with Odin. Reroot as per the instructions in the MDK root thread. Instead of TWRP, use CWM Recovery (which isn't nearly as easy), then reinstall the latest Hyperdrive (or whatever you were trying to install).
Hey guys, I need help.
I consider myself fairly adept at handling rooted devices, but I have not been following development for the GS4 for the last several months and have been running the last release of Synergy before their hiatus.
I was going to try out something different. I always enjoyed Beanstown's Jelly 'Beans', and thought I would try Build 7.
Now I am stuck at the Samsug Galaxy Boot Logo and it never goes to the Custom Boot Screen.
WORSE...I managed to break my recovery...so it will not boot their either.
Only mode I can boot to is Download.
Maybe I am just blind but I searched and could not find any Odin flashable recoveries...does anyone have one? Is there a rooted MDK file out there that I can flash via Odin?
Someone please help
Did you do the proper wipes when flashing the new rom? There arent any odin flashable recoveries for the s4. I would probably use the no wipe mdk image to recover (wont lose any user data) since you have no custom recovery to flash something with. Youll have to start over but youll have a working phone at least.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Yes...I always wipe well when I am flashing. Almost every problem I have ever had going back to the Droid 1 was from a Dirty Wipe. I also tried searching for issues and warnings before moving forward...but did not find anything with my searches.
So just to be sure I have this right...start with this
http://forum.xda-developers.com/showthread.php?t=2301259&highlight=mdk
Then re-root as I did originally
http://forum.xda-developers.com/showthread.php?t=2290798
Then I can reflash CWM Recovery from Rom Manager? Will it automatically flash loki'd version?
Finally once there...can I just flash Beantown's Jelly Beans Build 7 or do I need to update the radios first? Can I use the just the MJ7 modem from the post below or do I need other parts updated too?
http://forum.xda-developers.com/showthread.php?t=2487298
Thanks all!
jbg25 said:
Yes...I always wipe well when I am flashing. Almost every problem I have ever had going back to the Droid 1 was from a Dirty Wipe. I also tried searching for issues and warnings before moving forward...but did not find anything with my searches.
So just to be sure I have this right...start with this
http://forum.xda-developers.com/showthread.php?t=2301259&highlight=mdk
Then re-root as I did originally
http://forum.xda-developers.com/showthread.php?t=2290798
Then I can reflash CWM Recovery from Rom Manager? Will it automatically flash loki'd version?
Finally once there...can I just flash Beantown's Jelly Beans Build 7 or do I need to update the radios first? Can I use the just the MJ7 modem from the post below or do I need other parts updated too?
http://forum.xda-developers.com/showthread.php?t=2487298
Thanks all!
Click to expand...
Click to collapse
Yeah looks like you got everything in order. Rom manager or rom toolbox will auto loki the recoveries. No need to update radios when flashing beans either. Itll already have the radios included unless your wanting to flash the mj7 radio seperately then I believe youll be ok doing that. I havent done alot of reading on the newest radios.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Back up and running with stock rooted MDK and CWM Recovery.
Now to try and flash a ROM.
jbg25 said:
Back up and running with stock rooted MDK and CWM Recovery.
Now to try and flash a ROM.
Click to expand...
Click to collapse
good deal just saw your pm was gonna say flash mdk odin but it looks like you found it
beanstown106 said:
good deal just saw your pm was gonna say flash mdk odin but it looks like you found it
Click to expand...
Click to collapse
Thanks for getting back to me! :good:
I am up and running...but with but not with 'Beans' Build 7 ... I have tried everything...and no matter what it stalls at the SGS4 Splash Screen and never progresses.
I thought maybe it was the new recovery I flashed ( CWM Touch Recovery 6.0.4.4) .... BUT I got Hyperdrive to install and boot. So maybe my SGS4 just doesn't like Beans...which sucks cause I ran that almost exclusively on my SGS3.
jbg25 said:
Thanks for getting back to me! :good:
I am up and running...but with but not with 'Beans' Build 7 ... I have tried everything...and no matter what it stalls at the SGS4 Splash Screen and never progresses.
I thought maybe it was the new recovery I flashed ( CWM Touch Recovery 6.0.4.4) .... BUT I got Hyperdrive to install and boot. So maybe my SGS4 just doesn't like Beans...which sucks cause I ran that almost exclusively on my SGS3.
Click to expand...
Click to collapse
Try TWRP 2.5.0.2.
Most of the devs use it.
Sent from my SCH-I545 using xda app-developers app
Mightycaptain said:
Try TWRP 2.5.0.2.
Most of the devs use it.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I downloaded and installed the latest TWRP 2.6.3.0 from DsLNeXuS's Recovery Tools App as Goo Manager is not finding a recovery for my device.
Still no good...nothing I do makes Beans Build 7 work ....
jbg25 said:
I downloaded and installed the latest TWRP 2.6.3.0 from DsLNeXuS's Recovery Tools App as Goo Manager is not finding a recovery for my device.
Still no good...nothing I do makes Beans Build 7 work ....
Click to expand...
Click to collapse
Go here. Get 2.5.0.2
http://techerrata.com/browse/twrp2/jfltevzw
Instructions
http://teamw.in/project/twrp2/181
At the bottom of the page.
Edit;
Or flash this in recovery
http://forum.xda-developers.com/showthread.php?p=45006486
I would reboot to recovery after flashing to make you got it on the right version.
Then make sure you can still boot back to your rom.
Then go back to recovery
Wipe
Factory reset.
Advanced
Check system, Data, davlik and cache
Wipe
Go back to main screen
Install
Fund your rom to flash.
Sent from my SCH-I545 using xda app-developers app
Me too. I tried the [ROM][TW4.3]STOCK-ROOTED-MJ7-AROMA-LOKI'd ROM with CWMR. Wiped Dalvik. Cache, Ractory Rest/Data. Seemed to install fine but then hung at "Custom". Fortunately I was able to a Nandroid Restore but not sure where this went wrong. Finally got TWRP to install after several failed GooManager attempts over the past month. May CWMR is the problem.
I installed Safestrap onto my GS4 in hopes of installing a ROM to get ride of touchwiz. I found a safestrap compatible ROM and installed it through safestrap. Now I cant boot into the system. I wiped all data and cache and factory setting. When ever I restart, sometimes it says: [Safestap: Disabled] or [Safestrap: enabled] I can access recovery. I tapped continue on both and just doesn't work.
Bit of a noob so dont be too hard
EDIT: I Installed Hyperdrive successfully until the end. Its at this screen: Beginning Android OS 4.3 boot sequence... .... .... ...." It has stayed here for hours, all night. Should I take out the battery? Buttons don't work
High_Rez said:
I installed Safestrap onto my GS4 in hopes of installing a ROM to get ride of touchwiz. I found a safestrap compatible ROM and installed it through safestrap. Now I cant boot into the system. I wiped all data and cache and factory setting. When ever I restart, sometimes it says: [Safestap: Disabled] or [Safestrap: enabled] I can access recovery. I tapped continue on both and just doesn't work.
Bit of a noob so dont be too hard
Click to expand...
Click to collapse
So you created a rom slot and flashed the rom to that slot? What build base are you..why SS version did u use and rom did u flash ...?
Sent from my SCH-I545 using XDA Premium 4 mobile app
decaturbob said:
So you created a rom slot and flashed the rom to that slot? What build base are you..why SS version did u use and rom did u flash ...?
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I created the rom slot. Im MK2, I used safestrap because I have a locked BL. Whats SS? I used a ROM called Barebone Stock.
When ever I flash a rom, all that happens when I restart is it says safestrap: Disabled or enabled. I choose recovery every time because rebooting doesnt do any thing.
High_Rez said:
I created the rom slot. Im MK2, I used safestrap because I have a locked BL. Whats SS? I used a ROM called Barebone Stock.
When ever I flash a rom, all that happens when I restart is it says safestrap: Disabled or enabled. I choose recovery every time because rebooting doesnt do any thing.
Click to expand...
Click to collapse
SS is SafeStrap but you should try to uninstall the rom and reboot into stock and then go back and try to reinstall the rom
Sent from my SCH-I545 using Tapatalk
High_Rez said:
I created the rom slot. Im MK2, I used safestrap because I have a locked BL. Whats SS? I used a ROM called Barebone Stock.
When ever I flash a rom, all that happens when I restart is it says safestrap: Disabled or enabled. I choose recovery every time because rebooting doesnt do any thing.
Click to expand...
Click to collapse
SS = abreviation for safestrap, thought that was pretty obvious
barebone ROM? Im not familar with that one being SS compatible. The safestrap disabled msg on display means the stock rom slot is active and the phone should boot to stock. When you have rom loaded into a rom slot 1 or 2 or whatever, you must "activate" that slot for it to boot. I would suggest deleting the rom slot you made and start over.
decaturbob said:
SS = abreviation for safestrap, thought that was pretty obvious
barebone ROM? Im not familar with that one being SS compatible. The safestrap disabled msg on display means the stock rom slot is active and the phone should boot to stock. When you have rom loaded into a rom slot 1 or 2 or whatever, you must "activate" that slot for it to boot. I would suggest deleting the rom slot you made and start over.
Click to expand...
Click to collapse
So I made a 3rd rom slot and installed hyperdrive. everthing went well until the end. Its at this screen that says "Beginning Android OS 4.3 boot sequence...." Its been on this screen for hours. All night
High_Rez said:
So I made a 3rd rom slot and installed hyperdrive. everthing went well until the end. Its at this screen that says "Beginning Android OS 4.3 boot sequence...." Its been on this screen for hours. All night
Click to expand...
Click to collapse
So, let's start from the basics - you're not telling us what versions of anything that you're using.
First, what build is your phone? i.e. the stock slot.
What version of Safestrap are you trying to use?
What version of Hyperdrive are you trying to flash?
When the phone hangs like that during boot, something critical has crashed that's preventing the boot.
You're booting Android 4.3 according to the above, so you should be flashing using SS 3.71 on build MJ7 or MK2 and Hyperdrive RLS14.
If all that is correct: the build is MJ7 or MK2, the Safestrap is 3.71, and you're trying Hyperdrive RLS14, then the likely cause is that you have a bad download. Check the md5sum after downloading to ensure that it's OK. Download it to your PC, not directly to the phone, then check the MD5 before transferring it to your sdcard and flashing it.
k1mu said:
So, let's start from the basics - you're not telling us what versions of anything that you're using.
First, what build is your phone? i.e. the stock slot.
What version of Safestrap are you trying to use?
What version of Hyperdrive are you trying to flash?
When the phone hangs like that during boot, something critical has crashed that's preventing the boot.
You're booting Android 4.3 according to the above, so you should be flashing using SS 3.71 on build MJ7 or MK2 and Hyperdrive RLS14.
If all that is correct: the build is MJ7 or MK2, the Safestrap is 3.71, and you're trying Hyperdrive RLS14, then the likely cause is that you have a bad download. Check the md5sum after downloading to ensure that it's OK. Download it to your PC, not directly to the phone, then check the MD5 before transferring it to your sdcard and flashing it.
Click to expand...
Click to collapse
My buld is MK2
The The SS version is: it doesnt say. But is says TWRP v2.6.3.1.
Im using hyperdrive RLS14 S4.zip
I have my SD in my PC and I downloaded it from the forum to it. then flashed it. Also I think I screwed up stock because i cant access the system. I cant boot into it.
High_Rez said:
My buld is MK2
The The SS version is: it doesnt say. But is says TWRP v2.6.3.1.
Im using hyperdrive RLS14 S4.zip
I have my SD in my PC and I downloaded it from the forum to it. then flashed it. Also I think I screwed up stock because i cant access the system. I cant boot into it.
Click to expand...
Click to collapse
OK, If your stock slot is damaged, you probably need to re-flash and start over.
Download the MK2 "No-Wipe" rom image from this thread and flash it using ODIN 3.09 - that'll get you back to stock, Then try the Safestrap stuff again. Seems like you have the right versions of things, so if you follow the directions, it should boot OK.
Be sure to check the MD5 of anything you download. There's free software available that does that.
k1mu said:
OK, If your stock slot is damaged, you probably need to re-flash and start over.
Download the MK2 "No-Wipe" rom image from this thread and flash it using ODIN 3.09 - that'll get you back to stock, Then try the Safestrap stuff again. Seems like you have the right versions of things, so if you follow the directions, it should boot OK.
Be sure to check the MD5 of anything you download. There's free software available that does that.
Click to expand...
Click to collapse
Do I need to worry about any root?
High_Rez said:
Do I need to worry about any root?
Click to expand...
Click to collapse
Yeah after you flash the image in Odin use the saferoot guide that k1mu posted to obtain root again.
Sent from my HTC6600LVW using XDA Premium 4 mobile app
k1mu said:
OK, If your stock slot is damaged, you probably need to re-flash and start over.
Download the MK2 "No-Wipe" rom image from this thread and flash it using ODIN 3.09 - that'll get you back to stock, Then try the Safestrap stuff again. Seems like you have the right versions of things, so if you follow the directions, it should boot OK.
Be sure to check the MD5 of anything you download. There's free software available that does that.
Click to expand...
Click to collapse
I just dont see why I need to restart every thing. Is there any other possible way?
High_Rez said:
I just dont see why I need to restart every thing. Is there any other possible way?
Click to expand...
Click to collapse
Well is your stock slot still working? If u just messed up a ROM slot than you can erase them and start over.
But if it was your stock slot then using Odin probably is the only thing that will help you.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Well is your stock slot still working? If u just messed up a ROM slot than you can erase them and start over.
But if it was your stock slot then using Odin probably is the only thing that will help you.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Ok. Thanks
High_Rez said:
Ok. Thanks
Click to expand...
Click to collapse
Are you all set now?? Sounds to me like you messed up the stock slot from what I could gather from earlier posts.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Are you all set now?? Sounds to me like you messed up the stock slot from what I could gather from earlier posts.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Odin is not reading my phone. Yeah, all i need to do it flash the original firmware and root it and start over. But i dont see how that could work.
High_Rez said:
Odin is not reading my phone. Yeah, all i need to do it flash the original firmware and root it and start over. But i dont see how that could work.
Click to expand...
Click to collapse
I heard that you need to use the cord that came with the phone when you got it. So make sure you are and also try another USB port.
Sent from my SCH-I545 using Tapatalk
High_Rez said:
Odin is not reading my phone. Yeah, all i need to do it flash the original firmware and root it and start over. But i dont see how that could work.
Click to expand...
Click to collapse
Well you probably just need the USB drivers for your phone that's all. I just went through that myself with my new laptop. I ended up just googling it and finding the right ones.
It will work for you, once your back to stock just use Saferoot again, then install SafeStrap again... Then be certain whatever ROM u flash is SafeStrap compatible. I'd say use ROM slots for the time being until your more comfortable with things.... Don't take that the wrong way... Just saying is all. Messing with the stock slot can lead you back to where you're at right now that's all.
Sent from my SCH-I545 using Tapatalk
---------- Post added at 03:19 PM ---------- Previous post was at 03:17 PM ----------
Try the drivers that k1mu has in his saferoot thread
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Well you probably just need the USB drivers for your phone that's all. I just went through that myself with my new laptop. I ended up just googling it and finding the right ones.
It will work for you, once your back to stock just use Saferoot again, then install SafeStrap again... Then be certain whatever ROM u flash is SafeStrap compatible. I'd say use ROM slots for the time being until your more comfortable with things.... Don't take that the wrong way... Just saying is all. Messing with the stock slot can lead you back to where you're at right now that's all.
Sent from my SCH-I545 using Tapatalk
---------- Post added at 03:19 PM ---------- Previous post was at 03:17 PM ----------
Try the drivers that k1mu has in his saferoot thread
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I found the drivers but they say its already installed on my computer.
High_Rez said:
I found the drivers but they say its already installed on my computer.
Click to expand...
Click to collapse
Reinstall them then restart your computer
Sent from my SCH-I545 using Tapatalk
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've had this problem since December or so now, (whenever CM11 came out) and I've tried asking for help everywhere, including here before. But I'm sending out one final hail mary request. For some reason, whenever I download a 4.4 Rom for my phone and I have my wifi running, the phone will freeze after I hit the power button and will not turn the screen back on at all or it will freeze while I'm using it. The only way to get the phone back on is by doing a battery pull.
Here is everything I've tried: various Roms, various kernels, different steps to install (full wipe, wipe cache, etc.), I've even unrooted and gone back to stock to start from scratch and it still happens.
If anyone could please help me out, I'm stuck running 4.3 and I want to be able to run 4.4. Hopefully I can finally find a fix for this issue I'm having. I don't think it's faulty hardware because one other person or so has had the problem as well. Help me XDA, you're my only hope!
What firmware do you have? Since you mentioned different kernels, are you still on MDK? Have you ever taken any if the OTA updates?
Sent from my SCH-I545 using Tapatalk
jmgib said:
What firmware do you have? Since you mentioned different kernels, are you still on MDK? Have you ever taken any if the OTA updates?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Yeah I'm still on MDK. And no I never did an OTA.
What recovery are you using?
It happens to you all the time now? I've been so busy with work and school now that I hardly have any time at all. I really do want to pinpoint the issue before I throw this thing out the window....lol
thesoldier said:
It happens to you all the time now? I've been so busy with work and school now that I hardly have any time at all. I really do want to pinpoint the issue before I throw this thing out the window....lol
Click to expand...
Click to collapse
Me too ha, like I said this is my final hail mary. If I can't get it fixed I'm going to buy a new phone and I really don't want to have to do that. I'm praying one final time for someone to figure a fix for me.
joshm.1219 said:
What recovery are you using?
Click to expand...
Click to collapse
I've used CWM and TWRP. Currently using TWRP.
Nwwolf1 said:
I've used CWM and TWRP. Currently using TWRP.
Click to expand...
Click to collapse
This what I would do if I was you.
Flash full wipe MDK tar file
Root using towelroot
Install latest TWRP via flashify
Flash jrkruse's stock 4.4.2 NC5 rom for MDK, picking the stock talexop kernel in aroma.
If that doesn't work, I don't know what to tell you.
joshm.1219 said:
This what I would do if I was you.
Flash full wipe MDK tar file
Root using towelroot
Install latest TWRP via flashify
Flash jrkruse's stock 4.4.2 NC5 rom for MDK, picking the stock talexop kernel in aroma.
If that doesn't work, I don't know what to tell you.
Click to expand...
Click to collapse
Will I be able to still run AOSP Roms or will I have to stick with TW?
Nwwolf1 said:
Will I be able to still run AOSP Roms or will I have to stick with TW?
Click to expand...
Click to collapse
No you can still run AOSP roms, the only way you can lose MDK bootloader is if you flash firmware in Odin that is anything other than MDK, or if you take an OTA update while completely stock.
I guess I should say that after rooting stock MDK via towelroot, use a root explorer to delete SDM.apk and FWupgrade.apk from /system or /system/priv-app to prevent the phone from auto-updating before you flash a custom rom.
joshm.1219 said:
No you can still run AOSP roms, the only way you can lose MDK bootloader is if you flash firmware in Odin that is anything other than MDK, or if you take an OTA update while completely stock.
I guess I should say that after rooting stock MDK via towelroot, use a root explorer to delete SDM.apk and FWupgrade.apk from /system or /system/priv-app to prevent the phone from auto-updating before you flash a custom rom.
Click to expand...
Click to collapse
I'll definitely give it my best shot. Thank you!
Nwwolf1 said:
I'll definitely give it my best shot. Thank you!
Click to expand...
Click to collapse
Good luck, just letting you know, that full wipe tar file will wipe EVERYTHING. So make sure you have anything that you care about backed up on am external SD card or the cloud.
joshm.1219 said:
Good luck, just letting you know, that full wipe tar file will wipe EVERYTHING. So make sure you have anything that you care about backed up on am external SD card or the cloud.
Click to expand...
Click to collapse
Yeah I've got my music and photos backed up on my external SD and contacts backed with Google, those are really the only things I care about.