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.
Related
Here's the situation:
I recently s-off'd my Legend (Bell Canada variant) in order to try out ogo2's NewSense ROM and do some metamorph stuff. I also attempted in install ClockworkMod 3.0.2.8 via the fastboot method which seemed to work just fine.
I used ogo2's NewSense beta 2 without any difficulty, but decided to switch back to CM7 via a backup I made earlier. No problems so far.
Here's the problem:
Yesterday I tried to flash beta 4, and this is where things got a bit weird.
When I use Rom Manager to try flashing beta 4, it loads ClockworkMod 2.5.0.7. Likewise, if I reboot into recovery from ROM Manager, I end up in ClockworkMod 2.5.0.7.
If, however, I manually boot into recovery then I end up in ClockworkMod 3.0.2.8.
I've tried flashing beta 4 manually and through ROM Manager and each time the ROM seems to install just fine but I end up stuck at the splash image. Naturally, I try to manually boot into recovery so I can restore, but it often just reboots or gets stuck at the splash image before CWM can load. Not a problem anymore.
I have to do a couple of battery pulls before I can sucessfully enter recovery (when I do, it's CWM 3.x).
Since then I've restored to CM7, but I can't flash beta 4 and the CWM disparity doesn't seem right to me. In otherwords, my phone is completely usable but CWM doesn't seem right.
Does anyone have any insight into this problem or a possible solution?
The issue lies in the way ROM Manager deals with recoveries. When the Legend was first given ROM Manager support S-OFF was a thing of dreams, we had to use the fakeflash method to get to CWM, so Koush made ROM Manager use fakeflash with some phones. Ours was one of them. When you "flash" a recovery using ROM Manager a fakeflash .zip is downloaded to your phone and stored somewhere, then using a method I don't fully understand ROM Manager reboots to recovery and "flashes" the fakeflash .zip. Now, because S-OFF we can flash recoveries to the recovery partition, but Koush hasn't updated his app to allow us to make use of it, nor has he made an updated version of CWM in fakeflash format for it. If someone cared enough they could probably get support for the latter at least. Because Koush hasn't updated his stuff to make use of new developments for our phone, ROM Manager assumes S-ON and still uses the fakeflash method, hence CWM 2.0.5.1 when using ROM Manager.
Thanks for the info. I was beginning to suspect something along those lines but it's always nice when someone who actually knows something about it gives an explanation.
I've seen on the Cyanogen forum that there is a fake flash 3.0.2.8. Anyone who can confirm this? I can't manage to get it to work :S
Sent from my HTC Legend using Tapatalk
Ok guys heres the deal....i recently got a samsung fascinate from my sister cause I couldnt mod my inc any more. ok so....i got the phone rooted. i have su perm. i downloaded rom manager and installed it. now heres my problem. i can preform a backup no problem, but when i go to restore that backup it boots into clockwordmod and begins and then get an error about erasing boot img. or something like that. can tell exactly if i get some help from this. also cant install custom roms like i can with my incredible. i know it can be done cause i see roms and all for this phone. can someone please please help me.
Thats because cwm3 will not perform nandroid restores on stock roms. You need to flash cwm 2.5.1.x red recovery. Its the best recovery imo for any bml(touchwiz) rom. Go over to my guide in general section and you cand find cwm 2.5 in section 2&5. Oh and ditch rom manager...manually install cwm via odin!
If you're coming from an incredible, also keep in mind you don't have to be rooted to flash roms either, you just have to have a custom recovery. There aren't really any modifications like rooting procedures, S-OFF, etc, required for rom flashing, just odin a recovery and flash your selected rom.
Hello people....
I am new to SGS3 xda forum....i am from Pakistan...its been 2 weeks since i bought a SGS3 (second hand)...probably of 3mobile U.K...i was told by the seller that the phone was unlocked in Pakistan....as i tried system update from settings...it said that my phone was modified and could not be updated....so i decided to install CWM Touch on my SGS3 in order to create backup of my current stock ROM (4.1.1)...my phone is not rooted yet....i followed the instructions given in the following link:
http://jellybean-news.blogspot.com/2013/02/complete-guide-to-install-clockworkmod.html
Odin took 1 second and my phone was booted....Odin gave the Message ''Pass!''...everything went fine as it should have been...but when i went into the recovery mod...Stock Android Recovery is opening instead of CWM Touch....noting my phone is not rooted yet....it is also normally booting and everything is fine....can anybody guide me about the problem that i am currently facing...and its solution as well....?? Help Would Be Appreciated...
Edit:Just Flashed CF-Root Pakcage Including SuperSU and CWM Manager with CWM v5.5.0.4....now it goes into CWM...but still one noob question....have my previous stock android recovery and CWM Touch been automatically deleted/replaced?...or they still exist?? Thanks
Sounds like you were trying to install a cwm without being rooted.
Cwm replaces the stock android recovery. You could now try flashing the cwm touch through your current cwm. Make sure its a zip. If you come and ask for help You should really follow a guide on xda though. They are the best guides around.
Shehram Ahmad said:
Edit:Just Flashed CF-Root Pakcage Including SuperSU and CWM Manager with CWM v5.5.0.4....now it goes into CWM...but still one noob question....have my previous stock android recovery and CWM Touch been automatically deleted/replaced?...or they still exist?? Thanks
Click to expand...
Click to collapse
When you flash a recovery you will delete the previous recovery in doing so, your stock and touch are both gone - replaced with v5.5.0.4.
You can now boot into CWM and install a better recovery, try Philz touch recovery for instance.
So I'd been having some problems lately with my phone hanging on the Samsung screen on boot. Been running CM11 1/1/2014 nightly most recently. Decided to try using TWRP instead of CWM. That didn't seem to help my issue, so I tried installing CWM again. I used an app called Recovery Tools to download the touch version of CWM. After it said it installed, I tried to boot into recovery and got the error "Unauthorized software found. Please contact Verizon." (paraphrased a little).
Doing some research it looks like that error typically comes up when the bootloader is locked. Now, obviously I had my bootloader unlocked (well, Loki'd) because I was running CM11. Any help fixing this? I'm able to bypass the warning screen on boot if I hold down vol up + power like I'm going into download mode, but then hit vol down to cancel to boot up the phone. Once booted everything is ok, but any reboot just brings that up again. Using ROM manager to flash CWM recovery seems to work ok and it says its installed, but same issue. So does trying to flash TWRP from Goo.
If I were to run this tool that I used to root and loki before (http://forum.xda-developers.com/showthread.php?t=2301720) to install a recovery, would I be able to get everything going again? I think that somehow the recovery I installed wasn't Loki'd, although I picked the right one for my device.
Thank you in advance for any replies.
The fix I found was by pure dumb luck. I ended up trying to flash a recovery with Odin. Odin failed but reboot back into the os. I then used the twrp manager app from the playstore (mainly because goomanager wasn't downloading the recovery at the time) to flash the latest twrp recovery and all was good. Even though Odin failed at flashing the recovery I still think it helped somehow. I haven't thought much about why but I might have to now.
Sent from my SCH-I545 using Tapatalk
You could probably try using ODIN to get back to stock MDK and then Re-Root and install a recovery after.
Edit: And then flash CM11 again.
Sent from my SCH-I545 using Tapatalk
Will this one-click stock ROM work?
http://www.rwilco12.com/downloads.p... S4 (Verizon) (SCH-I545)/Stock ROMs/One-Click
or, which of the files on this page are what I would want? (about 1/3 of the way down for SCH-I545)
http://www.droidviews.com/how-to-install-latest-official-firmware-on-samsung-galaxy-s4-all-models/
I was actually able to reflash TWRP w/ their app from the Play Store. Still get a lot of boot hangs on the Samsung logo though. Seemed to happen less with CWM, but now I'm too scared to try to install a different recovery. I appreciate all your help guys.
about a month ago I tried to change to a new ROM on my sgh-i717R model note which was already rooted running TWRP and a custom ROM that I had installed quite awhile ago. I did not realize that TWRP had to be updated to a newer version to use the 4.4 ROMS and the update failed and bricked my phone. I managed to fix it and put back a stock Rogers 2.3.6 ROM and it put back the original samsung recovery. The problem now besides being on an old ROM there is a lot of input lag using on screen keyboard, so I want to try a new custom ROM to see if it fixes things, but when I try to flash a new recovery with Odin (TWRP 2.8.0.0), Odin tells me that everything is good and it passes, but when I then reboot my device and go into recovery mode afterwards, it is the same samsung recovery mode with only the custom binary download counter incremented, but TWRP is nowhere to be found... I have tried with several versions of TWRP and it is the same thing.
qazplokm said:
about a month ago I tried to change to a new ROM on my sgh-i717R model note which was already rooted running TWRP and a custom ROM that I had installed quite awhile ago. I did not realize that TWRP had to be updated to a newer version to use the 4.4 ROMS and the update failed and bricked my phone. I managed to fix it and put back a stock Rogers 2.3.6 ROM and it put back the original samsung recovery. The problem now besides being on an old ROM there is a lot of input lag using on screen keyboard, so I want to try a new custom ROM to see if it fixes things, but when I try to flash a new recovery with Odin (TWRP 2.8.0.0), Odin tells me that everything is good and it passes, but when I then reboot my device and go into recovery mode afterwards, it is the same samsung recovery mode with only the custom binary download counter incremented, but TWRP is nowhere to be found... I have tried with several versions of TWRP and it is the same thing.
Click to expand...
Click to collapse
You may have lost root when you went back to GB
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
captemo said:
You may have lost root when you went back to GB
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
yeah it was unrooted, but you cannot root without putting the custom recovery first.. Anyways I solved the problem, for some reason TWRP does not work (even though I tried all the versions specified for quincyatt and sgh-i717) but I was able to put on CWM no problems and re-root with superuser from there.
qazplokm said:
yeah it was unrooted, but you cannot root without putting the custom recovery first.. Anyways I solved the problem, for some reason TWRP does not work (even though I tried all the versions specified for quincyatt and sgh-i717) but I was able to put on CWM no problems and re-root with superuser from there.
Click to expand...
Click to collapse
I know this thread is a couple weeks old but I thought I'd add something that I have found that might help if someone else has this problem.
The only way I was able to install the new version of TWRP was to install the old one first while rooting the phone then download the new versions .zip and update it via TWRP. I was able to get the new version working that way and now I am able to flash any rom I want with no issues.
Hope this helps others.