I bought phones for my parents for Christmas. Managed to find two BNIB MDK Verizon GS4s on eBay. I currently have an S4 MDK that I rooted myself with no problems.
I went through using the Odin method to downgrade the kernel to root the device, just like I did on mine. When I downloaded ROM Manager, for some reason it wouldn't allow me to flash CWM, so I used terminal emulator to install it using the Loki method found here:
http://galaxys4root.com/galaxy-s4-r...on-att-or-verizon-galaxy-s4-sgh-i337sch-i545/
After I booted into CWM recovery, I wiped everything (didn't nandroid :/) before installing a stockish debloated ROM - BoneStock 1.1.4 which is what I've been running. When I went to install The ROM zip from my ext sd card, the card wouldn't mount. I can't get my device to mount at all in recovery so I can't even sideload anything.
One thing that I may have done wrong is not flashed the second CWM file to upgrade the recovery to CWM v6.0.4.7.
Currently the phone will not boot passed the Samsung logo. Is there anyway to flash a different version of CWM through recovery? Or would that even fix my problem? I can get into download mode fine. I can still boot into CWM but it's useless at this point.
Could someone PLEASE help me! I feel like I've made a stupid mistake somewhere.
I check the CWM recovery version on my device and currently I'm running version 6.0.3.2. Could that be the reason I keep getting the error unable to mount the sd card? Does anyone have a current version of CWM recovery that's flashable over ODIN? I'm thinking that's my last resort before attempting to restore the MDK TAR.
Bullhead00 said:
I bought phones for my parents for Christmas. Managed to find two BNIB MDK Verizon GS4s on eBay. I currently have an S4 MDK that I rooted myself with no problems.
I went through using the Odin method to downgrade the kernel to root the device, just like I did on mine. When I downloaded ROM Manager, for some reason it wouldn't allow me to flash CWM, so I used terminal emulator to install it using the Loki method found here:
http://galaxys4root.com/galaxy-s4-r...on-att-or-verizon-galaxy-s4-sgh-i337sch-i545/
After I booted into CWM recovery, I wiped everything (didn't nandroid :/) before installing a stockish debloated ROM - BoneStock 1.1.4 which is what I've been running. When I went to install The ROM zip from my ext sd card, the card wouldn't mount. I can't get my device to mount at all in recovery so I can't even sideload anything.
One thing that I may have done wrong is not flashed the second CWM file to upgrade the recovery to CWM v6.0.4.7.
Currently the phone will not boot passed the Samsung logo. Is there anyway to flash a different version of CWM through recovery? Or would that even fix my problem? I can get into download mode fine. I can still boot into CWM but it's useless at this point.
Could someone PLEASE help me! I feel like I've made a stupid mistake somewhere.
Click to expand...
Click to collapse
MDK TAR sounds like the only way to go. Make sure to get the MDK one though!
Theoretically, there are other ways, such as flashing a new recovery from your current one, but with Loki, that would probably be harder than what its worth.
Does anyone have any clue why I wasn't able to use ROM manager to flash CWM recovery?
ODIN MDK TAR file worked. I still don't know what went wrong and why CWM recovery couldn't mount my SD card so I could flash a ROM.
Related
My old one started getting the sim card error.Still under warranty so...new phone in hand. (Refurb) I rooted using Odin 3v1.85 installed SuperUser and ClockworkModRecovery. All moves along fine. Now I try to install ROM zips (tried three) and they all abort quickly. It starts opening and checking and aborts saying error with zip file. I have downloaded three different ROMs and redid it from different sites too...same thing. What am I doing wrong?
Did you update your recovery after rooting? I recommend twrp which can be found in the original development section.
"Update my recovery" Hmmmm....since I am unsure what you mean...I guess not. TOG recommended TWRP over CWM too. I'll go take a look see. By "original dev section" I assume you mean the other subforum?
Quick explanation of updating my recovery?
Thanks for your valuable time. Here, have a coffee...U)
EDIT:
OK, I went, found and downloaded the latest TWRP2.zp for Odin install, since I'm most familiar with that method. So, am I right in these steps?
1. Re-root w Odin using .tar file from the TWRP.zip using the PDA button.
2.Update?
3. Reboot into recovery (does twrp use the same method as cwm?)
3.Install ROM zip of choice...rejoice?
That's way too complicated broseph...
You still have cwm right?
Just Go back to the twrp thread, download the recovery flashable zip.
Put it on your sdcard and flash it in cwm like a Rom.
Once that's done reboot recovery and you'll now have twrp
Button combos are built into the boatloaders, changing recovery has no effect on them whatsoever.
OK
Thanks again all....I did all of the above and finally got the ROM to load, then Gapps, and the rest of the drill. I never could access my back-up that I stored on my ext SD card and the card is not showing in any file explorers (although it shows in storage, under settings ?).
AT least I have a functioning phone...yay.
Sd card is named as /emmc and several other names.
I was trying to switch my phone over to CWM from TWRP. I tried flashing using ROM manager but it was always rewritten. I decided to grab the .img file from the CWM site and flash it in terminal emulator like I had done with TWRP before. It seemed to flash but when i rebooted I got the message that the system software was not authorized. I thought the file I downloaded was loki but I guess not. Do I have to odin back to stock now or is there another method?
So I just realized it was being stupid and was stuck trying to boot recovery. I booted to download mode and selected cancel to force it out of this loop. Once it did this I was able to boot the system and restore a proper recovery.
On a side note, does anyone know why flashing CWM doesn't stick. I read some things about the recovery being flashed every boot but all the information was out dated, I couldn't find anything about the S4.
thecaptain0220 said:
On a side note, does anyone know why flashing CWM doesn't stick. I read some things about the recovery being flashed every boot but all the information was out dated, I couldn't find anything about the S4.
Click to expand...
Click to collapse
ROM manager does work...try flashing then reboot at least once before booting recovery...and if you are running a stock tw rom some will attemt to overwrite custom recovery...in newer cwm it will ask you if you want to disable recovery install...clicking yes will stop the process keeping custom cwm
I have Safestrap up and running again but I'm wondering how can you install other recoveries like TWRP and CWM so I can boot directly into the custom recovery without a splashscreen I believe it's called (newbie here). I followed instructions online with GooManager for TWRP and ROM Manager for CWM but neither will actually boot into the custom recovery.
In GooManager after it says the TWRP recovery has been installed, it will reboot but then take me to the downloading boot screen and say "could not do a normal boot." What's with that? I actually had to use ODIN again to flash the stock ROM back (I tried this three times to no avail...)
And for CWM it says it successfully flashed in ROM Manager but when I actually reboot into recovery, whether it be from the app or manually, it will just boot into the stock Android recovery. I don't get it...
What am I doing wrong and/or is my phone not compatible with these recoveries?
Specs:
Verizon Galaxy S4
Android 4.3
Build MK2
Kernel MK2
Also are there any other recoveries that might work with my phone?
Thanks!
....
Bootloader is locked and custom recovery can't be installed on newer/updated S4. Do some reading to find out what is and is not possible with a locked bootloader.
the immunity said:
I have Safestrap up and running again but I'm wondering how can you install other recoveries like TWRP and CWM so I can boot directly into the custom recovery without a splashscreen I believe it's called (newbie here). I followed instructions online with GooManager for TWRP and ROM Manager for CWM but neither will actually boot into the custom recovery.
In GooManager after it says the TWRP recovery has been installed, it will reboot but then take me to the downloading boot screen and say "could not do a normal boot." What's with that? I actually had to use ODIN again to flash the stock ROM back (I tried this three times to no avail...)
And for CWM it says it successfully flashed in ROM Manager but when I actually reboot into recovery, whether it be from the app or manually, it will just boot into the stock Android recovery. I don't get it...
What am I doing wrong and/or is my phone not compatible with these recoveries?
Specs:
Verizon Galaxy S4
Android 4.3
Build MK2
Kernel MK2
Also are there any other recoveries that might work with my phone?
Thanks!
Click to expand...
Click to collapse
I'm not sure how any one misses a sticky thread like this one:
http://forum.xda-developers.com/showthread.php?t=2606501
Hi All, I rooted my Verizon GS4 with this method "[GUIDE] Root for Verizon Galaxy S4 ***VRUAMDK Build Only!***" back before the first update so I have Root with Baseband I545VRUAMDK, Build JDQ39.I545VRUAMDKand Kernal 3.4.0-562219. I haven't tried to install any ROMs since then but started to get the itch so I started refreshing myself on the process and found that when I try to reboot into CWM Recovery it boots to Android System Recovery 3e. I'm looking for guidance on how to get CWM working properly. ROM Manager says I am using CWM 6.0.4.7. Any help will be appreciated.
Thanks
jpp2109 said:
Hi All, I rooted my Verizon GS4 with this method "[GUIDE] Root for Verizon Galaxy S4 ***VRUAMDK Build Only!***" back before the first update so I have Root with Baseband I545VRUAMDK, Build JDQ39.I545VRUAMDKand Kernal 3.4.0-562219. I haven't tried to install any ROMs since then but started to get the itch so I started refreshing myself on the process and found that when I try to reboot into CWM Recovery it boots to Android System Recovery 3e. I'm looking for guidance on how to get CWM working properly. ROM Manager says I am using CWM 6.0.4.7. Any help will be appreciated.
Thanks
Click to expand...
Click to collapse
From what I've read about that issue is people have had to Odin back to stock then start over. Now maybe you could try installing another recovery like Philz maybe using Odin or try Goo for TWRP before you Odin back to mdk and go through all that.
Sent from my SCH-I545 using Tapatalk
I had a similar thing a few years ago, with what I know now I think the recovery is temporarily flashed with CWM to gain root and stock recovery is replaced after, I'd look for an actual CWM recovery to flash in.
Same applied to me using a ROM Manager, said it was v.xxx made a backup, flashed a ROM, turns out was left without a backup..... noob-old days
Bashing away at my HTC Desire C
Thank you for the solid replies, I'm interested in getting experience with the other recovery methods anyway so I'll try those and worse case I start from scratch.
I have pretty much this same issue. I was happily running 6.0.44 CWM, installed via CWM.
Then I happened to check and see there's an update to 6.0.47. I installed via ROM manager which reported success. Except that it isnt. I basically have 2 recoveries as far as ROM manager is concerned. It thinks I'm on 6.0.47, but 6.0.44 is what boots. I'm betting it's the same issue you have.
I re-flashed Twrp trying to fix it. Now twrp is what recovery always boots; but Rom manager still thinks 6.0.47 is installed. Rom manager shows BOTH recoveries in the "Recovery already installed" menu.
Seems the issue here is the 6.0.47 when flashed via Rom manager. It bugs the crap out of me that it seems like I have 2 recoveries installed somehow. Not sure how that's possible, but everything seems like it's functioning for me.
Compare the sizes of the recoveries, one thing I've come across is when you flash a new .img in because of the NAND chip process for writing/erasing I have had 'remnants' from previous files.
In one respect it is unlikely but I wouldn't rule it out until you check yourself. It could just be left on the list as a marker that it has previously been installed.
Personally I don't use ROM Managers now, it's into TWRP Recovery and backup from there
Bashing away at my HTC Desire C
Look Like I'll Have to Start From Scratch
I'm just getting back to this because work was crazy. No Matter what recovery I try always comes up with Android System Recovery 3e. Stock MDK and re-root it is.
Maybe try using GooManager to install TWRP after you've gone back to stock.
I recently bought a used Galaxy Tab 2 off of Craigslist where everything worked perfectly fine.
I wanted to update to Lollipop, having done so already on my Note II, so I was gonna get CWM to flash the zip.
The CWM wouldn't boot up so I tried TWRP, didn't work also.
I found all the appropriate .tar files for Odin to flash but it simply won't boot into neither CWM nor TWRP.
I tried many versions of each one and when i go into bootloader mode, it recognizes that i did change the binary.
I used odin to flash the recovery mods.
Can't find a way to root without CWM so i can't use apps like ROM Manager or Rashr.
Fastboot from SDK won't recognize my phone so that wasn't an option.
Please help!
Searched far and wide for an answer but still can't boot into CWM nor TWRP.
I love Lollipop and really want it on my tab.
Everything else works fine except this frustration.