Brand new Samsung S4, had successful root (checked via Root Checker). I had previously installed Clockworkmod but after some difficulty with flashing Cyanogenmod 10.2 I downloaded GooManager and installed it's preferred recovery, then re-downloaded the CM 10.2 and directed GooManager to install the .zip, and it popped up the "Downloading... Do not turn off target!!" The script in the top left says as follows
"Could not do normal boot.
ODIN MODE
Product Name: SSCH-1545
Current Binary: Samsung Official
System Status: Custom
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x0
CSB-CONFIG-LSB: 0x30
Write Protection: Enable
eMMC BURST MODE enabled"
It has been on this downloading screen with no changes for 2 hours. After researching other threads, I tried to reboot into recovery, only for this exact screen to pop up immediately, and again with no change for prolonged periods of time.
Any help would be greatly appreciated! I am fairly new to this as well, so the more user-friendly the better.
What software version are you running?
Sent from my SCH-I545 using Tapatalk
joshuabg said:
What software version are you running?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I can't remember off the top of my head... 4.2.3 pops in to mind, I'll research and post as soon as I find.
You can't ****ing use goomanager, god dammit read alittle before you **** up your phone. Just boot holding power, home, and volume down, and when prompted press no
I managed to get back to stock with root; I used Goo Manager -because- I did some reading, but obviously I read the wrong things. If someone could assist with the best structure to use (which recovery, best method for flashing, etc.) I would greatly appreciate it.
ziggums said:
I managed to get back to stock with root; I used Goo Manager -because- I did some reading, but obviously I read the wrong things. If someone could assist with the best structure to use (which recovery, best method for flashing, etc.) I would greatly appreciate it.
Click to expand...
Click to collapse
Search in android development. Factory Firmware is there. You'll need to Odin at this point. Whatever came on your phone stock. The firmware version matters here. Can't Odin a previous version. Only what's on it or a newer version. After that a reroot and find the safestrap thread in android development. Read up. This will be your recovery. No aosp. No custom kernels just touch wiz ROMs.
Sent from my SCH-I545 using XDA Premium 4 mobile app
ziggums said:
Brand new Samsung S4, had successful root (checked via Root Checker). I had previously installed Clockworkmod but after some difficulty with flashing Cyanogenmod 10.2 I downloaded GooManager and installed it's preferred recovery, then re-downloaded the CM 10.2 and directed GooManager to install the .zip, and it popped up the "Downloading... Do not turn off target!!" The script in the top left says as follows
"Could not do normal boot.
ODIN MODE
Product Name: SSCH-1545
Current Binary: Samsung Official
System Status: Custom
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x0
CSB-CONFIG-LSB: 0x30
Write Protection: Enable
eMMC BURST MODE enabled"
It has been on this downloading screen with no changes for 2 hours. After researching other threads, I tried to reboot into recovery, only for this exact screen to pop up immediately, and again with no change for prolonged periods of time.
Any help would be greatly appreciated! I am fairly new to this as well, so the more user-friendly the better.
Click to expand...
Click to collapse
you have soft bricked your phone by not understanding what you can and can't do with it. Better learn about odin process
Mightycaptain said:
Search in android development. Factory Firmware is there. You'll need to Odin at this point. Whatever came on your phone stock. The firmware version matters here. Can't Odin a previous version. Only what's on it or a newer version. After that a reroot and find the safestrap thread in android development. Read up. This will be your recovery. No aosp. No custom kernels just touch wiz ROMs.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I found several guides about flashing to original, but none of them match my build (I am MK2). The phone is behaving exactly as before except when I try to boot into recovery mode it sends me back to the "Downloading.... Do not turn off target!!" screen, and I have to go through the process to get back to "normal" behavior. Could I simply just flash a different recovery, or do I need to try to find MK2 to go back to original first?
I appreciate all the help so far!
ziggums said:
I found several guides about flashing to original, but none of them match my build (I am MK2). The phone is behaving exactly as before except when I try to boot into recovery mode it sends me back to the "Downloading.... Do not turn off target!!" screen, and I have to go through the process to get back to "normal" behavior. Could I simply just flash a different recovery, or do I need to try to find MK2 to go back to original first?
I appreciate all the help so far!
Click to expand...
Click to collapse
You CAN'T flash a recovery on your build. That's the whole problem. You need to Odin back to your stock build. There is an MK2 file in the development section.
Sent from my NCC 1701 using Tapatalk 4
riker147 said:
You CAN'T flash a recovery on your build. That's the whole problem. You need to Odin back to your stock build. There is an MK2 file in the development section.
Sent from my NCC 1701 using Tapatalk 4
Click to expand...
Click to collapse
Could you link me to it? I can't find anything that deals with soft-brick reversing for MK2.
ziggums said:
Could you link me to it? I can't find anything that deals with soft-brick reversing for MK2.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2578209
douger1957 said:
http://forum.xda-developers.com/showthread.php?t=2578209
Click to expand...
Click to collapse
Thanks! I assume I would need to do the full-wipe process rather than the no-wipe process?
ziggums said:
Thanks! I assume I would need to do the full-wipe process rather than the no-wipe process?
Click to expand...
Click to collapse
I think in the long run a full wipe is always the best route.
douger1957 said:
I think in the long run a full wipe is always the best route.
Click to expand...
Click to collapse
The link was exactly what I needed! The video link they had was especially helpful, I returned to stock. I do have a question moving on from here though... Can I use Odin to try to flash CM10.2 (the one that was unsuccessful previously)? And what recovery do you recommend? The other posters mentioned something about Safe... I'm really just trying to get a smooth, stable ROM so I don't have to deal with the bloatware and can customize a bit more for what I need. Sorry if I'm annoying, but I appreciate all the help!
ziggums said:
The link was exactly what I needed! The video link they had was especially helpful, I returned to stock. I do have a question moving on from here though... Can I use Odin to try to flash CM10.2 (the one that was unsuccessful previously)? And what recovery do you recommend? The other posters mentioned something about Safe... I'm really just trying to get a smooth, stable ROM so I don't have to deal with the bloatware and can customize a bit more for what I need. Sorry if I'm annoying, but I appreciate all the help!
Click to expand...
Click to collapse
Being on MK2 your ONLY option is Safestrap. No Cm, no AOSP.....Just TW. You have a lot of research to do. Start here: http://forum.xda-developers.com/showthread.php?t=2606501
ziggums said:
The link was exactly what I needed! The video link they had was especially helpful, I returned to stock. I do have a question moving on from here though... Can I use Odin to try to flash CM10.2 (the one that was unsuccessful previously)? And what recovery do you recommend? The other posters mentioned something about Safe... I'm really just trying to get a smooth, stable ROM so I don't have to deal with the bloatware and can customize a bit more for what I need. Sorry if I'm annoying, but I appreciate all the help!
Click to expand...
Click to collapse
Please do some research...you can't install cm or asop base roms or custom recovery like cwm or twrp...your only option is safestrap.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Related
Phone model: Verizon SCH-I545
Build JDQ39.I545VRUDMI1
Have already obtained root via this method: http://forum.xda-developers.com/showthread.php?t=2487142
Here is the problem: I am using CWM to attempt to reboot into CWM Recovery but the phone will only boot into normal recovery.
1) Is there a way to fix/get around this problem? (I assume that once I install a new Rom this problem will no longer occur)
2) Odin seems to be an option to install a new ROM without CWM recovery, however 100% of the ROMs I want to install are ZIP, not TAR as Odin requires. (I am unsure I should unzip and tar a ROM and expect that to work in Odin?)
Thanks for your help!
You'll have to use Safestrap, it's the only way for your build.
http://forum.xda-developers.com/showthread.php?t=2441441&styleid=18
Disappointing
Sir_Eagle said:
You'll have to use Safestrap, it's the only way for your build.
http://forum.xda-developers.com/showthread.php?t=2441441&styleid=18
Click to expand...
Click to collapse
Thanks! This saves me time.
So you are saying Odin is not an option? The only way to Flash a new ROM for my build is with Safestrap. Its very hard to tell by the thread if its safe to use, or even a real way to truly install a new ROM. By that I mean, I can't tell if Safestrap's method of installing a new ROM doesn't in fact replace the existing ROM, it just installs an alternate ROM to the side of the regular ROM?
This is disappointing enough that I may sell my S4 and stick with my Galaxy Nexus
ktamlyn said:
Thanks! This saves me time.
So you are saying Odin is not an option? The only way to Flash a new ROM for my build is with Safestrap. Its very hard to tell by the thread if its safe to use, or even a real way to truly install a new ROM. By that I mean, I can't tell if Safestrap's method of installing a new ROM doesn't in fact replace the existing ROM, it just installs an alternate ROM to the side of the regular ROM?
This is disappointing enough that I may sell my S4 and stick with my Galaxy Nexus
Click to expand...
Click to collapse
Odin is not an option for installing custom ROMs. Since the bootloader is locked, the only things you can flash on your device using Odin are factory stock files. No custom recovery, no AOSP or CWM at the moment - only what's compatible with Safestrap.
Yes, it's safe. SS installs the new ROM in free space in your phone's internal storage, leaving the stock ROM intact for recovery. This should have been quite clear if you read the Safestrap description.
k1mu said:
Odin is not an option for installing custom ROMs. Since the bootloader is locked, the only things you can flash on your device using Odin are factory stock files. No custom recovery, no AOSP or CWM at the moment - only what's compatible with Safestrap.
Yes, it's safe. SS installs the new ROM in free space in your phone's internal storage, leaving the stock ROM intact for recovery. This should have been quite clear if you read the Safestrap description.
Click to expand...
Click to collapse
I continued reading and accept reality now - I think I was in denial! My mistake of letting the phone update is seriously frustrating. My hope was to have the Google Edition ROM installed, but SS doesn't allow this currently.
Sorry to hear that... if you want custom software you need to read before you buy, assumptions are a mofo.
i'm guessing we can't simply use odin and flash to a different software build
endleesss said:
i'm guessing we can't simply use odin and flash to a different software build
Click to expand...
Click to collapse
That is correct. Once you take the plunge, you can never go back unless you or someone you know has Jtag experience.
Sent from my SCH-I545 using Tapatalk
itsdubai said:
That is correct. Once you take the plunge, you can never go back unless you or someone you know has Jtag experience.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I've only seen one person say they successfully used JTAG to downgrade firmware, granted he's a reputable developer, but even if you ask JTAG they'll tell you they can't get our model to downgrade.
Sent from my SCH-I545 using Tapatalk
I'm pretty new to this... I had my Verizon Galaxy S4 with MK2 build rooted and tried to install a ROM using GooManager. Now my phone is stuck in download mode. I've been searching for a stock MK2 recovery to use with Odin but haven't been able to find one. I also backed up my phone using SafeStrap and sent those files to my computer before I did this... is there any way I can restore using those files from my computer? I tried using them on Odin but it says the md5's are invalid. Any help would be appreciated...
stealyourdigits said:
I'm pretty new to this... I had my Verizon Galaxy S4 with MK2 build rooted and tried to install a ROM using GooManager. Now my phone is stuck in download mode. I've been searching for a stock MK2 recovery to use with Odin but haven't been able to find one. I also backed up my phone using SafeStrap and sent those files to my computer before I did this... is there any way I can restore using those files from my computer? I tried using them on Odin but it says the md5's are invalid. Any help would be appreciated...
Click to expand...
Click to collapse
I suggest read some postings next couple of days....This kind of issue has been killed to death. You just can't install any rom u want...especially with goo manager. If u search... should find a stock image for mk2 to use with odin...educate yourself on what odin can and can't do.
safestrap enabled, Hyperdrive driven
decaturbob said:
I suggest read some postings next couple of days....This kind of issue has been killed to death. You just can't install any rom u want...especially with goo manager. If u search... should find a stock image for mk2 to use with odin...educate yourself on what odin can and can't do.
safestrap enabled, Hyperdrive driven
Click to expand...
Click to collapse
I have since found the stock image for MK2 and I'm in the process of downloading it. I appreciate the reply
stealyourdigits said:
I have since found the stock image for MK2 and I'm in the process of downloading it. I appreciate the reply
Click to expand...
Click to collapse
Too many people are messing their S4 phones up...A couple dozen everyday we see here in xda.
safestrap enabled, Hyperdrive driven
decaturbob said:
Too many people are messing their S4 phones up...A couple dozen everyday we see here in xda.
safestrap enabled, Hyperdrive driven
Click to expand...
Click to collapse
Yeah, I tried to write a sticky that could help avoid at least some of these, but apparently the moderators didn't approve.
Yeah, there's a lot of threads with people that somehow managed the dozens of other posts by people who tried to use Goo Manager to flash custom recovery and failed.
But in the end, the lack of clear, up-front guidance that you can't flash custom recovery means that we'll continue to see people flashing the wrong thing. All we can do is to tell them how they screwed up.
k1mu said:
Yeah, I tried to write a sticky that could help avoid at least some of these, but apparently the moderators didn't approve.
Yeah, there's a lot of threads with people that somehow managed the dozens of other posts by people who tried to use Goo Manager to flash custom recovery and failed.
But in the end, the lack of clear, up-front guidance that you can't flash custom recovery means that we'll continue to see people flashing the wrong thing. All we can do is to tell them how they screwed up.
Click to expand...
Click to collapse
I know you tried. I'm not sure why moderator didn't oblige your request. As long as people don't want to research wtf they are doing...we will keep seeing the errors repeated time and time again. Amazing to me the foolishness. Anyway there is always next year!!
safestrap enabled, Hyperdrive driven
Purchased a Verizon S4 on swappa. The phone was rooted - in the description it said "It has not been updated to 4.3 and is currently rooted on 4.2.2 ME7 baseband" I am upgrading from a Galaxy Nexus I rooted as I run stuff like XPrivacy etc..
I get the phone, install titanium backup and do a full backup. The OTA update notification started popping up as well. Go to reboot the phone and reboot into recovery. (Familiar with doing that n the Galaxy Nexus, so why not? I am a foolish man)
The phone reboots into what I now learn is odin mode and says:
Could not do normal boot.
Odin Mode
Product name: SCH-I545
Current Binary: Samsung Official
System Status: Custom
CSB-CONFIG-LSB: 0x30
What has happened and how do I resolve it? Assuming it is fixable is it better to stay where I am OS version wise or accept the OTA update?
Thanks in advance for the help.
Thadster
Thadster said:
Purchased a Verizon S4 on swappa. The phone was rooted - in the description it said "It has not been updated to 4.3 and is currently rooted on 4.2.2 ME7 baseband" I am upgrading from a Galaxy Nexus I rooted as I run stuff like XPrivacy etc..
I get the phone, install titanium backup and do a full backup. The OTA update notification started popping up as well. Go to reboot the phone and reboot into recovery. (Familiar with doing that n the Galaxy Nexus, so why not? I am a foolish man)
The phone reboots into what I now learn is odin mode and says:
Could not do normal boot.
Odin Mode
Product name: SCH-I545
Current Binary: Samsung Official
System Status: Custom
CSB-CONFIG-LSB: 0x30
What has happened and how do I resolve it? Assuming it is fixable is it better to stay where I am OS version wise or accept the OTA update?
Thanks in advance for the help.
Thadster
Click to expand...
Click to collapse
Star here: http://forum.xda-developers.com/showthread.php?t=2606501
The guy who sold you it is an idiot. He attempted to use goomanager to flash a custom recovery. You can stay the way you are and not have a recovery, but if you want it back you should flash a no wipe ME7 Odin image. I did the same thing and is easily fixed
aidankiller4 said:
The guy who sold you it is an idiot. He attempted to use goomanager to flash a custom recovery. You can stay the way you are and not have a recovery, but if you want it back you should flash a no wipe ME7 Odin image. I did the same thing and is easily fixed
Click to expand...
Click to collapse
First off thank you for the rapid reply. While waiting, I have been research odin - kinda get what I have to do. First can you point me to the odin image you suggest? Would that file then go into the pda slot and get pushed to the phone? Will I have to reroot?
Thadster said:
First off thank you for the rapid reply. While waiting, I have been research odin - kinda get what I have to do. First can you point me to the odin image you suggest? Would that file then go into the pda slot and get pushed to the phone? Will I have to reroot?
Click to expand...
Click to collapse
Here's the odin file for your phone
http://forum.xda-developers.com/showthread.php?t=2357235
That file goes into the pda slot
After that go into the Dev section and search for how to root your phone.
Do some research and see if staying on an older build like me7 is worth it for you. Either way, you'll have safestrap and root. Everything past me7 has the Knox bootloader and security. Just read up a bit that's all.
Until you decide flash that in Odin... Root it.... and grab titanium backup and freeze SDM and FWupdater and you won't get any annoying OTA notifications.
Edit
The no wipe images are here
http://forum.xda-developers.com/showthread.php?t=2301259
Maybe you can get away with just doing a no wipe. Try it first.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Thank you.
The no-wipe did not work, but the other did. (Phew).
Phone is now operational and re-rooted. What are my recovery options with regards to backing up this current phone image? Having difficulty getting clockwork recovery to work. (Hesitant probably) Is sage strap a better option?
Thadster said:
Thank you.
The no-wipe did not work, but the other did. (Phew).
Phone is now operational and re-rooted. What are my recovery options with regards to backing up this current phone image? Having difficulty getting clockwork recovery to work. (Hesitant probably) Is sage strap a better option?
Click to expand...
Click to collapse
Like I said before. Start here: http://forum.xda-developers.com/showthread.php?t=2606501
Thadster said:
Thank you.
The no-wipe did not work, but the other did. (Phew).
Phone is now operational and re-rooted. What are my recovery options with regards to backing up this current phone image? Having difficulty getting clockwork recovery to work. (Hesitant probably) Is sage strap a better option?
Click to expand...
Click to collapse
You can't use clockwork, or any other custom recovery, on your phone. Safestrap is your only choice.
Brother-in-law dropped his s4 in the sink. After panicked drying it will turn on but the rom is scrambled. So he gave it to me. I can get it into recovery (odin) but I'm afraid I don't know much about odin. I found the most recent stock rom but it keeps giving me an error "Secure check failed: hidden". Is this because I'm using the wrong rom file or is it just permabricked?
DieKatzchen said:
Brother-in-law dropped his s4 in the sink. After panicked drying it will turn on but the rom is scrambled. So he gave it to me. I can get it into recovery (odin) but I'm afraid I don't know much about odin. I found the most recent stock rom but it keeps giving me an error "Secure check failed: hidden". Is this because I'm using the wrong rom file or is it just permabricked?
Click to expand...
Click to collapse
You can Odin back to stock & use Odin to flash a recovery like Philz Touch or TWRP. Unless, of course, it's a later build than MDK. In that case you are going to have to use Safestrap as a recovery and will be limited to the roms compatible with it. Roms are flashed from a recovery program, not from Odin.
wtherrell said:
You can Odin back to stock & use Odin to flash a recovery like Philz Touch or TWRP. Unless, of course, it's a later build than MDK. In that case you are going to have to use Safestrap as a recovery and will be limited to the roms compatible with it. Roms are flashed from a recovery program, not from Odin.
Click to expand...
Click to collapse
I'm /trying/ to Odin back to stock. I'm just not sure how to do that.
DieKatzchen said:
I'm /trying/ to Odin back to stock. I'm just not sure how to do that.
Click to expand...
Click to collapse
Several threads and YouTube videos about odin
Sent from my SCH-I545 using XDA Premium 4 mobile app
DieKatzchen said:
Brother-in-law dropped his s4 in the sink. After panicked drying it will turn on but the rom is scrambled. So he gave it to me. I can get it into recovery (odin) but I'm afraid I don't know much about odin. I found the most recent stock rom but it keeps giving me an error "Secure check failed: hidden". Is this because I'm using the wrong rom file or is it just permabricked?
Click to expand...
Click to collapse
I haven't done much with the SGS4 yet, but I think the problem you are having is the phone was not running the most recent software release (MK2) From what I've gathered in reading through other threads is you're going to have to try flashing each stock rom version until you find the right one. Of course the phone could just be completely screwed and nothing will work. I'd start by trying to flash MDK, if that works, consider yourself lucky because that is the holy grail version to have. You can actually unlock the bootloader and put a custom recovery on.
jgulig79 said:
I haven't done much with the SGS4 yet, but I think the problem you are having is the phone was not running the most recent software release (MK2) From what I've gathered in reading through other threads is you're going to have to try flashing each stock rom version until you find the right one. Of course the phone could just be completely screwed and nothing will work. I'd start by trying to flash MDK, if that works, consider yourself lucky because that is the holy grail version to have. You can actually unlock the bootloader and put a custom recovery on.
Click to expand...
Click to collapse
Thanks, I'll try that.
OK, made a dumb mistake. Not a frequent poster so I had to post here rather than in the thread where it belongs:
http://forum.xda-developers.com/showthread.php?t=2643031&page=266
[ROM]KOT49H【4.4.4】AOSP Official Google Edition 【Verizon!】06-25-2014
Basically, I didn't re-flash loki-doki. I had 4.4.2 running and had re-flashed 4.4.3 but somehow thought that I could reboot and then re-enter recovery to re-flash loki rather than doing it all at once. Dumb move. So now I have a perfectly good 4.4.3 load, but I can't enter recovery to do anything else. I want to flash the 4.4.4 image, but anytime I try to get into recovery I get the "System software not authorized by Verizon Wireless / Yellow Triangle" message.
I know I can Odin back to a stock image, but is there an easy way to force into recovery to flash loki-doki? Tried Flashify per another users post but that doesn't get me anywhere. Have not tried Triangle Away, because I didn't think that would cure my issue. The answer may be to re-flash, but I wanted to see if there was an easy way first. Running MDK btw....
Chad
Chad52 said:
OK, made a dumb mistake. Not a frequent poster so I had to post here rather than in the thread where it belongs:
http://forum.xda-developers.com/showthread.php?t=2643031&page=266
[ROM]KOT49H【4.4.4】AOSP Official Google Edition 【Verizon!】06-25-2014
Basically, I didn't re-flash loki-doki. I had 4.4.2 running and had re-flashed 4.4.3 but somehow thought that I could reboot and then re-enter recovery to re-flash loki rather than doing it all at once. Dumb move. So now I have a perfectly good 4.4.3 load, but I can't enter recovery to do anything else. I want to flash the 4.4.4 image, but anytime I try to get into recovery I get the "System software not authorized by Verizon Wireless / Yellow Triangle" message.
I know I can Odin back to a stock image, but is there an easy way to force into recovery to flash loki-doki? Tried Flashify per another users post but that doesn't get me anywhere. Have not tried Triangle Away, because I didn't think that would cure my issue. The answer may be to re-flash, but I wanted to see if there was an easy way first. Running MDK btw....
Chad
Click to expand...
Click to collapse
I am far from an expert but I think you are on the right track with having to do Odin.
I haven't used loki-doki before but after doing some reading the requirement is a working custom recovery.
This may be a dumb question but did you try to re-install something like CWM?
(CM11 jflte MDK baseband)
Chad52 said:
OK, made a dumb mistake. Not a frequent poster so I had to post here rather than in the thread where it belongs:
http://forum.xda-developers.com/showthread.php?t=2643031&page=266
[ROM]KOT49H【4.4.4】AOSP Official Google Edition 【Verizon!】06-25-2014
Basically, I didn't re-flash loki-doki. I had 4.4.2 running and had re-flashed 4.4.3 but somehow thought that I could reboot and then re-enter recovery to re-flash loki rather than doing it all at once. Dumb move. So now I have a perfectly good 4.4.3 load, but I can't enter recovery to do anything else. I want to flash the 4.4.4 image, but anytime I try to get into recovery I get the "System software not authorized by Verizon Wireless / Yellow Triangle" message.
I know I can Odin back to a stock image, but is there an easy way to force into recovery to flash loki-doki? Tried Flashify per another users post but that doesn't get me anywhere. Have not tried Triangle Away, because I didn't think that would cure my issue. The answer may be to re-flash, but I wanted to see if there was an easy way first. Running MDK btw....
Chad
Click to expand...
Click to collapse
Try unzipping whatever recovery it is you want to use and then use Flashify to " flash recovery image " and locate the Recovery. IMG you got from unzipping earlier.
Also I would run Tri Angle Away too.
If using that method to get you're recovery back doesn't help... Then yes Odin it is.
Sent from my SCH-I545 using Tapatalk
Thanks all. I use twrp, and have tried reflashing it, but nothing let's me reboot into recovery without the situation described above. My fault, so looks like back to square one I go...
Sent from my GT-I9505G using Tapatalk
Chad52 said:
Thanks all. I use twrp, and have tried reflashing it, but nothing let's me reboot into recovery without the situation described above. My fault, so looks like back to square one I go...
Sent from my GT-I9505G using Tapatalk
Click to expand...
Click to collapse
Are you just trying to get into recovery from the ROM? Or from a battery pull and phone off? Sometimes getting into it from the ROM can get borked but the other method works in which case flashing the ROM again should fix that. Again I'd also use Tri Angle Away
Sent from my SCH-I545 using Tapatalk
Trying from inside the ROM. I've got a fully functioning 4.4.3, but I'm locked out of getting into Recovery....
Chad
Flashify can't even get me into Recovery...
Thanks all, I ODIN'd back to stock and worked it all the way back forward to 4.4.4. Appreciate the help.
Chad
I hate digging up old threads especially when Hijacking them. But I wanted to say thanks for the information you provided. It helped a lot and got me back into recovery (TWRP 2.8.1.1). Now the real fun begins. I have not had this phone in my possession for quite some time (November 2013). Anyway, I was tasked with bringing it up to date and I might need some further assistance. If so, I'll start my own topic in this sub forum.
Thanks again @Mistertac.
Mistertac said:
Try unzipping whatever recovery it is you want to use and then use Flashify to " flash recovery image " and locate the Recovery. IMG you got from unzipping earlier.
Also I would run Tri Angle Away too.
If using that method to get you're recovery back doesn't help... Then yes Odin it is.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse