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.
Related
I rooted my phone a few weeks ago while I'm on mi1 software using de la Vega method and a little after I decided to use goomanager to flash a custom bootloader but instead got stuck in Odin with the message going something like (Odin mode cant boot normal) got out of it by pressing volume down + power then restart but now I can't even update my phone to 4.3 because everytime I do It goes back to that Odin downloading error screen please help I'd be gracious for any response .thank you
I'm getting a similar issue. Mine says:
Could not do normal boot.
ODIN MODE
Product name: SCH-I545
Current binary: samsung official
system status: Official
CSB-config-lsb: 0x30
Write protection: enable
then i just see the android guy with Downloading Do not turn off target.
doesn;t seem to be doing anything else, and i can;t push any buttons to get out.
illtrytohelpyou said:
I rooted my phone a few weeks ago while I'm on mi1 software using de la Vega method and a little after I decided to use goomanager to flash a custom bootloader but instead got stuck in Odin with the message going something like (Odin mode cant boot normal) got out of it by pressing volume down + power then restart but now I can't even update my phone to 4.3 because everytime I do It goes back to that Odin downloading error screen please help I'd be gracious for any response .thank you
Click to expand...
Click to collapse
Flash back to MI1. It does not support custom bootloaders.
You can use SafeStrap and that is about it.
joshrys said:
I'm getting a similar issue. Mine says:
Could not do normal boot.
ODIN MODE
Product name: SCH-I545
Current binary: samsung official
system status: Official
CSB-config-lsb: 0x30
Write protection: enable
then i just see the android guy with Downloading Do not turn off target.
doesn;t seem to be doing anything else, and i can;t push any buttons to get out.
Click to expand...
Click to collapse
Yea I just can't figure it out I hope this thread helps you too
tech_head said:
Flash back to MI1. It does not support custom bootloaders.
You can use SafeStrap and that is about it.
Click to expand...
Click to collapse
How would I go about flashing back to mi1 stock boot loader?
You'll need to look at one of the other threads on flashing with Odin. You will need the MI1 Odin file.
Sent from my SCH-I545 using Tapatalk
tech_head said:
You'll need to look at one of the other threads on flashing with Odin. You will need the MI1 Odin file.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Will it restore my phone ? Like loose all my stuff? And will I loose root sorry for all the questions but I really appreciate your help
illtrytohelpyou said:
Will it restore my phone ? Like loose all my stuff? And will I loose root sorry for all the questions but I really appreciate your help
Click to expand...
Click to collapse
Yes, it will wipe the phone and you will lose root.
I think there is a "no wipe version also" check the forums.
Check out -> http://forum.xda-developers.com/showthread.php?t=2301259
also - http://forum.xda-developers.com/showthread.php?t=2503676&page=3
After Installing 4.3 Update On Rooted MK2.... Update Stopped In Download Mode Now
illtrytohelpyou said:
Yea I just can't figure it out I hope this thread helps you too
Click to expand...
Click to collapse
My S4 Verizon Does And Says The Same As His But My System Status Says Custom.
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 was originally trying to just go to the new kitkat rom, i believe that was CM11 or something of the sort. But for some reason i cannot do anything with my phone when it comes to installing or changing the recovery. Odin fails every time. One-Click-Root fails every time (which i think is what i used from the beginning to root). I even upgraded ROM manager to pro so i could try the touch based recovery and it will not successfully install a recovery that i can boot into even though it says that it has and shows(ed) the current recovery being the most up-to-date version. And now since ive tried several different today, i have lost root somehow...even thought i just had it and didnt change anything with the root process...just trying to regain even the stock recovery. Basically what happens if i try to boot into recovery mode is it tries for half a second then boots to ODIN mode and in the top left corner it says failed normal boot or something of the sort.
Can someone point me in the right direction? would a factory reset within the android OS help anything? every thing is backed up, so that wont be an issue as far as apps/data and important files goes.
The phone still boots to my "rooted" 4.3 that i have installed, just dont have root privelages any longer...the phone still works as normal...just cant do anything root based...like run titanium backup or supersu, and even ROM manager is NOW giving me an error when trying to install a custom recovery.
I would like to restore to stock MDK so i can start from scratch and install the CM11 KitKat Rom if at all possible...
So you were mdk and loki'd correct...
safestrap powered Hyperdrive 12
decaturbob said:
So you were mdk and loki'd correct...
safestrap powered Hyperdrive 12
Click to expand...
Click to collapse
MDK yes, the loki part im not sure of...but i did try to do that again since having this problem...with no success...
MURD3RD said:
MDK yes, the loki part im not sure of...but i did try to do that again since having this problem...with no success...
Click to expand...
Click to collapse
you would have to to use the loki process to gain root and install the custom recovery at the time. I really can't help as I got into the S4 with ME7 base and been using safestrap.
i also tried following this link
http://forum.xda-developers.com/showthread.php?t=2290798
and it doesnt get past the first ODIN step and gets a fail
attached are some snips of the ODIN screen when it fails
decaturbob said:
you would have to to use the loki process to gain root and install the custom recovery at the time. I really can't help as I got into the S4 with ME7 base and been using safestrap.
Click to expand...
Click to collapse
you got a link to a good working Loki tutorial?
Here's a link to the stock mdk tar file. This will totally wipe your phone. http://www.sxtpdevelopers.com/showthread.php?t=237
Ryno77 said:
Here's a link to the stock mdk tar file. This will totally wipe your phone.
Click to expand...
Click to collapse
i did find that link before and am currently downloading it...but it is taking forever...everything else i download is blazing fast (50Mb D/L speed here at my buddies apartment) but yet this file is only downloading at 50KB/s...and is showing over 9-10 hours for the download to be complete...does anybody have a faster download source?
i know my connection is phenomenal since i downloaded a 9 gig file last night from a different source and it took under an hour...this .tar is less than 2 gigs...shouldnt take that damn long...
i also tried flashing the recovery .tar.md5 from that link...same exact result...
Questions and Help issues go in Q&A and Help section
Thread moved
Thanks
FNSM
kennyglass123 said:
Questions and Help issues go in Q&A and Help section
Thread moved
Thanks
FNSM
Click to expand...
Click to collapse
THANKS!!!
I knew i hadn't put it in the right place...hopefully it'll get more view here...and i can get this thing sorted out
so right now the screen shows (phone)--(yellow triangle)--(computer) and says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
this is after trying to install the stock restore .tar files in the link mentioned above...the device will NO LONGER boot the os and goes to this screen every time. I can still get it into download (Odin) mode though.
MURD3RD said:
i also tried following this link
http://forum.xda-developers.com/showthread.php?t=2290798
and it doesnt get past the first ODIN step and gets a fail
attached are some snips of the ODIN screen when it fails
Click to expand...
Click to collapse
The "fail (auth)" means that you're likely no longer running an MDK bootloader. It's refusing to load the MD2 that's used by Loki.
Do you get the same failure when you try to flash the stock MDK ROM image? What text shows up on your phone when you try to flash the stock?
Since you're stuck at the "Firmware upgrade encountered an issue." it indicates that the bootloader rejected a flash, which means you may have somehow updated to MI1 or later. The message on the phone when the flash fails will tell for sure.
k1mu said:
The "fail (auth)" means that you're likely no longer running an MDK bootloader. It's refusing to load the MD2 that's used by Loki.
Do you get the same failure when you try to flash the stock MDK ROM image? What text shows up on your phone when you try to flash the stock?
Since you're stuck at the "Firmware upgrade encountered an issue." it indicates that the bootloader rejected a flash, which means you may have somehow updated to MI1 or later. The message on the phone when the flash fails will tell for sure.
Click to expand...
Click to collapse
i can't remember what exactly the messages were right now...but currently Kies is trying a recovery "upgrade and initialization"...hopefully this works and my phone can at least be usable again...and THEN ill get back at trying to get the new KitKat, lol
MURD3RD said:
i can't remember what exactly the messages were right now...but currently Kies is trying a recovery "upgrade and initialization"...hopefully this works and my phone can at least be usable again...and THEN ill get back at trying to get the new KitKat, lol
Click to expand...
Click to collapse
You won't be on MDK, so no KitKat.
k1mu said:
You won't be on MDK, so no KitKat.
Click to expand...
Click to collapse
but i have had no problem flashing back to get rooted when i first got the device...even though several threads said it couldnt be done...all i need is to get back to stock and start from scratch...at least i hope this is the case. If it goes ahead and installs the newest 4.3 update...and i truly cant change it due to no exploits yet...then i guess ill have to wait...lol, it could be worse, haha
so kies just finished doing its thing and the phone booted up and is now running 4.3 MK2
MURD3RD said:
so kies just finished doing its thing and the phone booted up and is now running 4.3 MK2
Click to expand...
Click to collapse
That means you lost the mdk bootloader and can only use Safestrap to boot custom rooms :/ you will need to root via saferoot in the development thread first. Then load Safestrap which only has one ROM that currently works (hyper drive 12).
gnubian said:
That means you lost the mdk bootloader and can only use Safestrap to boot custom rooms :/ you will need to root via saferoot in the development thread first. Then load Safestrap which only has one ROM that currently works (hyper drive 12).
Click to expand...
Click to collapse
EDIT: well nevermind...i think i was just crazy to think something different...i am definitely running the latest release of 4.3 from vzw...fml...well at least it can still be rooted. Is there any development for KitKat on the new MK2 software? Ill do some searching around...
i do remember, however, doing something that a tutorial said specifically not to do...and it worked anyway...even though several people responding to the thread said not to do or it would brick the phone...o well i guess...if i find the link ill post it up...
gnubian said:
That means you lost the mdk bootloader and can only use Safestrap to boot custom rooms :/ you will need to root via saferoot in the development thread first. Then load Safestrap which only has one ROM that currently works (hyper drive 12).
Click to expand...
Click to collapse
would you happen to have a link to the safestrap tutorial? i cant seem to locate it...im gunna do some more searching, but if you had a link at the ready, that'd be awesome!!!
EDIT: Found it...no worries
gnubian said:
That means you lost the mdk bootloader and can only use Safestrap to boot custom rooms :/ you will need to root via saferoot in the development thread first. Then load Safestrap which only has one ROM that currently works (hyper drive 12).
Click to expand...
Click to collapse
so i found the thread for this ROM and it doesnt say anything about being able to run on MK2 build...can anyone shed some light on this? it only says MJ7...
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
My S4 was rooted on KitKat and working just fine. I used the Odin App to downgrade, root, and go back to NK1, so no custom recovery.
I should have frozen the update popup but I was going to do the update using Flashfire so I could keep root. in the process of downloading the Rooted Lollipop rom and apparently I accidentally clicked the update button when the popup caught me by surprise. I got the case off and the battery out just as it was booting up to install the update! AH! Is there any way to stop it now? Or am I screwed?
Thanks for the help!
Have you tried an ODIN image? If you've been snooping around recoveries, Safestrap would've been a good option to make a nandroid. Other than that, I'd be out of ideas. AFAIK download mode should be able to be accessed.
fdigl said:
Have you tried an ODIN image? If you've been snooping around recoveries, Safestrap would've been a good option to make a nandroid. Other than that, I'd be out of ideas. AFAIK download mode should be able to be accessed.
Click to expand...
Click to collapse
Thankyou, I apparently forgot a lot after I researched to root the phone. Yes I got into download mode. I should be able to just take the lollipop rooted rom I was going to use in Flashfire and flash it through ODIN on my PC correct?
you may have to flash nc5 full wipe tar and the pit file in surges thread and then root via towelroot and then flashfire the rooted oc1 rom.
thats what id do.
reliant_turbo said:
you may have to flash nc5 full wipe tar and the pit file in surges thread and then root via towelroot and then flashfire the rooted oc1 rom.
thats what id do.
Click to expand...
Click to collapse
Just used ODIN to flash the NK1 Kitkat that I was already on, and that got me back to my rooted Kitkat, phew. Now I will flashfire the Rooted OC1 Rom.
Thankyou for the quick replies! I almost messed that up pretty good.
Oh, and just to be safe the first thing I did was freeze the SDM updater. :good:
simpsonna said:
Just used ODIN to flash the NK1 Kitkat that I was already on, and that got me back to my rooted Kitkat, phew. Now I will flashfire the Rooted OC1 Rom.
Thankyou for the quick replies! I almost messed that up pretty good.
Click to expand...
Click to collapse
that works too. glad you got it to work.