Okay guys, my phone is not booting up at all.
- I flashed hyperdrive, didn't like it and went to safestrap.
- I factory reseted, and tried to restore my old backup of the stock rom.
- I rebooted the phone, now it won't boot up anymore.
Was the backup corrupted? Now I only have stock recovery since safestrap didn't stick, and no rom, so I can't do anything.
Any way to install safestrap using adb or some sort? Please help me out, I'm in need of a phone
JustinBieber said:
Okay guys, my phone is not booting up at all.
- I flashed hyperdrive, didn't like it and went to safestrap.
- I factory reseted, and tried to restore my old backup of the stock rom.
- I rebooted the phone, now it won't boot up anymore.
Was the backup corrupted? Now I only have stock recovery since safestrap didn't stick, and no rom, so I can't do anything.
Any way to install safestrap using adb or some sort? Please help me out, I'm in need of a phone
Click to expand...
Click to collapse
I think you'll have to use Odin to flash whatever stock build you were on.
Sent from my NCC 1701 using Tapatalk 4
riker147 said:
I think you'll have to use Odin to flash whatever stock build you were on.
Sent from my NCC 1701 using Tapatalk 4
Click to expand...
Click to collapse
I'll try that, thank you!
Edit: I can't retrieve my backup because it's on internal memory and stock recovery doesn't have a file manager.. how will this work?
Doesn't the rom has to be in a .tar format for odin?
JustinBieber said:
I'll try that, thank you!
Edit: I can't retrieve my backup because it's on internal memory and stock recovery doesn't have a file manager.. how will this work?
Doesn't the rom has to be in a .tar format for odin?
Click to expand...
Click to collapse
I didn't mean your backup. I meant you would have to download either a no wipe or a full wipe rom.
Sent from my NCC 1701 using Tapatalk 4
JustinBieber said:
I'll try that, thank you!
Edit: I can't retrieve my backup because it's on internal memory and stock recovery doesn't have a file manager.. how will this work?
Doesn't the rom has to be in a .tar format for odin?
Click to expand...
Click to collapse
Exactly... Your going to have to call Odin in to rescue you. If it doesn't fix things with the no wipe, unfortunately the full wipe is going to be the way to go. Good luck!
Sent from my SCH-I545 using XDA Premium 4 mobile app
JustinBieber said:
Okay guys, my phone is not booting up at all.
- I flashed hyperdrive, didn't like it and went to safestrap.
- I factory reseted, and tried to restore my old backup of the stock rom.
- I rebooted the phone, now it won't boot up anymore.
Was the backup corrupted? Now I only have stock recovery since safestrap didn't stick, and no rom, so I can't do anything.
Any way to install safestrap using adb or some sort? Please help me out, I'm in need of a phone
Click to expand...
Click to collapse
there is a reason why hashcode set up safestrap to keep stock rom safe and why he offers no support to those who wish (at their peril) to flash a custom rom over the stock rom.
I have my rom stock rom intact and have 2 rom slots loaded each with there own custom rom and with a 32gb extsd card, have no issues with memory space.
JustinBieber said:
I'll try that, thank you!
Edit: I can't retrieve my backup because it's on internal memory and stock recovery doesn't have a file manager.. how will this work?
Doesn't the rom has to be in a .tar format for odin?
Click to expand...
Click to collapse
From this reply it appears that you don't quite know what odin is. I would find out, then use it to fix your phone.
Odd I figured Justin Bieber for an iPhone guy..
Mistertac said:
Exactly... Your going to have to call Odin in to rescue you. If it doesn't fix things with the no wipe, unfortunately the full wipe is going to be the way to go. Good luck!
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you!
thunderbls said:
Odd I figured Justin Bieber for an iPhone guy..
Click to expand...
Click to collapse
I like the s4 bro
Related
Hey All,
Ok so I have a problem and please excuse the dumb questions as I am new to Motorola (I came from the EVO).My device is rooted and bootstrap recovery installed and I created a backup of my normal setup. I tried to install the Alien ROM (I am not unlocked) and I did a wipe ect. the ROM will boot but I can't get past the touch here Android icon and I get a bunch of force closes.
I turned the phone off, put the wall charger in and I can not get back into recovery by holding the power and volume down to install my nandroid. My phone is stuck.....I can see fastboot but I don't know how to get back into my recovery.
Please help!!!!
Now that I think of it, my backup was on internal and the wipe might have erased the backup and bootstrap.....what the heck do I do now?
Mustangmatt1966 said:
Now that I think of it, my backup was on internal and the wipe might have erased the backup and bootstrap.....what the heck do I do now?
Click to expand...
Click to collapse
Did you install the ROM and theme all in one session?
Mustangmatt1966 said:
Now that I think of it, my backup was on internal and the wipe might have erased the backup and bootstrap.....what the heck do I do now?
Click to expand...
Click to collapse
It probably didn't erase your backup. You can always use rsdlite and flash cm5.
[email protected] said:
Did you install the ROM and theme all in one session?
Click to expand...
Click to collapse
Thats correct. Flashed ROM and then Flashed Theme
[email protected] said:
Did you install the ROM and theme all in one session?
Click to expand...
Click to collapse
Thats probably where I ran into an issue....as I see it says flash zip then reboot. Then flash theme after.... I am going to try and use RSD lite and CM5. Then go from there.
Mustangmatt1966 said:
Thats probably where I ran into an issue....as I see it says flash zip then reboot. Then flash theme after.... I am going to try and use RSD lite and CM5. Then go from there.
Click to expand...
Click to collapse
Yes exactly.you will be fine this way
Sent from my MB855 using xda premium
[email protected] said:
Yes exactly.you will be fine this way
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
Thanks MAX, I am so used to the EVO and flashing a rom and theme in the same recovery I didnt think twice about it....Lesson learned.
So I need to use RSD Lite and flash CM5. Then root again, install bootstrap, backup current rom. Then flash Alien, reboot, then flash theme and I should be ok?
Thanks for all of the help everyone, I got it resolved and fixed
So i was going to flash a rom I made a back up, I hit fixed permissions. and now all I have is Samsung Galaxy S4 logo and is just stuck there. I can get into twrp and have tried wiping and starting from a clean slate and restoring the back up but still get the galaxy logo? any suggestions ?
**have just tried to use odin and fails also*** How do I get back to stock please? Anyone please help
bump
Imprezive13 said:
bump
Click to expand...
Click to collapse
Have you tried flashing a stock ROM from TWRP?
-------edit----------
I just remembered. This used to happen on the Note 2 at times. If you're booting and get the Samsung splash screen, try going to TWRP and doing a Factory Reset a couple times. No idea if it will work, but with the Note that would usually clear whatever block existed and allow the ROM to boot past the splash screen. Good luck.
eakeller said:
Have you tried flashing a stock ROM from TWRP?
Click to expand...
Click to collapse
what do you mean ? first time ever having a problem with this. are you talking about the SCH-I545_MDK_562219_Stock_Restore.tar file ?
Imprezive13 said:
what do you mean ? first time ever having a problem with this. are you talking about the SCH-I545_MDK_562219_Stock_Restore.tar file ?
Click to expand...
Click to collapse
If it exists, it would basically be that ROM stuck into a .zip file which could be flashed from TWRP. I'm not sure it exists, was just browsing the Dev thread for you to see if anyone posted it. There is a version here http://forum.xda-developers.com/showthread.php?t=2292707 , but I'm not familiar with Loki enough to say whether or not you have it.
eakeller said:
If it exists, it would basically be that ROM stuck into a .zip file which could be flashed from TWRP. I'm not sure it exists, was just browsing the Dev thread for you to see if anyone posted it. There is a version here http://forum.xda-developers.com/showthread.php?t=2292707 , but I'm not familiar with Loki enough to say whether or not you have it.
Click to expand...
Click to collapse
Well for right now im trying to just get the phone back to its working condition. trying to using odin, but fails every time. and not sure what i should do.
Imprezive13 said:
Well for right now im trying to just get the phone back to its working condition. trying to using odin, but fails every time. and not sure what i should do.
Click to expand...
Click to collapse
If Odin isn't working for you, a solution might be had via TWRP since you can still get into the recovery. If you flash your ROM or try your backup, does the install complete or does it crash? Have you wiped cache, dalvik, system, and data before the flash?
-edit-
Sorry, just saw your OP where you said you wiped and tried. If I were you my next step would be trying a different ROM just to see if you can get something booting.
eakeller said:
If Odin isn't working for you, a solution might be had via TWRP since you can still get into the recovery. If you flash your ROM or try your backup, does the install complete or does it crash? Have you wiped cache, dalvik, system, and data before the flash?
Click to expand...
Click to collapse
Trying again. First wiping wiped cache, dalvik, system, and data , then restoring back up. I've tried this multiple times before hopefully it works this time. But generally when i hit reboot system afterward it just hangs at the Samsung Galaxy IV boot screen and does nothing.
Imprezive13 said:
Trying again. First wiping wiped cache, dalvik, system, and data , then restoring back up. I've tried this multiple times before hopefully it works this time. But generally when i hit reboot system afterward it just hangs at the Samsung Galaxy IV boot screen and does nothing.
Click to expand...
Click to collapse
After your backup restores, try using TWRP to do a Factory Reset a couple times before rebooting. Also wipe cache/dalvik again before the boot.
Failed again stuck at Samsung Galaxy S4 boot screen
eakeller said:
After your backup restores, try using TWRP to do a Factory Reset a couple times before rebooting. Also wipe cache/dalvik again before the boot.
Click to expand...
Click to collapse
Stuck again
Imprezive13 said:
Stuck again
Click to expand...
Click to collapse
Sorry to hear that, man. I'm out of ideas and hopefully someone with more know-how can give the solution.
Sent from my SCH-I545 using Tapatalk 2
I would try downloading a ROM to your computer then copying it to a microsd, put the card in your phone and then try to flash the fresh ROM from TWRP. (After wiping everything again.)
Sent from my SCH-I545 using Tapatalk 2
slim6596 said:
I would try downloading a ROM to your computer then copying it to a microsd, put the card in your phone and then try to flash the fresh ROM from TWRP. (After wiping everything again.)
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Ive been looking for the stock rom files no luck at the moment.
Maybe this one?
http://forum.xda-developers.com/showthread.php?t=2292707
Sent from my SCH-I545 using Tapatalk 2
slim6596 said:
Maybe this one?
http://forum.xda-developers.com/showthread.php?t=2292707
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
downloading now wish me luck
Good luck to you.
Sent from my SCH-I545 using Tapatalk 2
slim6596 said:
Good luck to you.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
got it working. on a deoxed rom. but is there a way to go completely back to stock using odin ?
http://forum.xda-developers.com/showthread.php?t=2289325
Sent from my SCH-I545 using Tapatalk 2
slim6596 said:
http://forum.xda-developers.com/showthread.php?t=2289325
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Well went to restart the phone and now its stuck on a Samsung logo with a unlocked icon thats says custom underneath it and just sits there.
I just picked up an S4 off swappa, MDK build already rooted and loki'd running TWRP 2.5.0.2
So I'll flash a ROM and sometimes they'll boot, sometimes they get stuck on the splash screen. If I reboot a ROM at all, it sticks on the splash screen. Sometimes it will randomly reboot itself. I have to battery pull from there, manually boot into recovery (sometimes it hangs on the splash here too), then reflash.
Weirdly, every time I do this (AKA everytime I try to reboot a ROM), once I get into the recovery it basically doesn't see my internal storage, shows it as "Internal Storage (0 mb)", no files shown in it.
I've tried fixing permissions yada yada, anyone have an idea as to what to do?
Internal storage? Like when you're trying to make a back up and you can choose between saving to the micro sdcard and internal, the internal shows 0mb there?
Sent from my XT912 using xda app-developers app
Surge1223 said:
Internal storage? Like when you're trying to make a back up and you can choose between saving to the micro sdcard and internal, the internal shows 0mb there?
Sent from my XT912 using xda app-developers app
Click to expand...
Click to collapse
Shows it like that everywhere in the recovery; install & restore section, file manager...
It has to be a recovery issue. I just formatted data with TWRP then booted into a ROM. Wtf.
Now I can't get anything to boot besides recovery... nor is there any guides for this.
joshm.1219 said:
Now I can't get anything to boot besides recovery... nor is there any guides for this.
Click to expand...
Click to collapse
Odin back to stock mdk, use the sch 1545 pit while in odin then reroot, install custom recovery
Sent from my XT912 using xda app-developers app
joshm.1219 said:
Now I can't get anything to boot besides recovery... nor is there any guides for this.
Click to expand...
Click to collapse
Are you wiping all the proper partitions before installing your rom? Ie factory data reset/system/both caches.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk. now Free
Surge1223 said:
Odin back to stock mdk, use the sch 1545 pit while in odin then reroot, install custom recovery
Sent from my XT912 using xda app-developers app
Click to expand...
Click to collapse
Yeah this is what I did.
I don't know what he did to this phone before I got it needed to start from scratch.
hexitnow said:
Are you wiping all the proper partitions before installing your rom? Ie factory data reset/system/both caches.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk. now Free
Click to expand...
Click to collapse
Yeah of course but the thing that was weird is that even when I hit "format data", which in twrp formats the whole internal sd; I could still boot the rom which shouldn't be possible.
Sent from my SCH-I545 using XDA Premium 4 mobile app
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