I have had my prime rooted and recently decided to unlock the bootloader for some JB goodness but when ever I try to flash a recovery in Goo Manager or Rom Manager it says successful then never works. When I try to boot into to recovery the stock recovery comes up with what I think is an error screen.
Is their that has experienced this or has a possible solution to my problem?
I am on 9.4.2.28 US if you need any more info let me know.
Nevermind kept trying for another 20 minutes and t worked oddly enough.
Related
Things went from bad to worst, I fixed my market update and had the utlities on the device i needed to i tryed flashing the Neutrino Rom.
After it was done it rebooted and said "failed to boot 2 starting rsd".
So I downloaded RSD Lite and found the unlock SBF which I applied. Now I can get into the FastBoot menu's and go to Android Recovery and try to do the back to stock option, it says it completes then reboots...
Then it just sits and sits and sits on the motorola Dual core logo.
Can someone please help me here. I cant seem to find any of my backups i made with system recovery or rom manager. I also didnt load RomRacers Recovery (which i just now noticed)
Any help is greatly appreciated.
So, did you unlock the bootloader before trying to flash the ROM?
Does it say "Unlocked" at the boot logo now?
Get back into fastboot and flash romracer's recovery and then try to mount the storage and get another rom on there.
SDRAKE101085 said:
Things went from bad to worst, I fixed my market update and had the utlities on the device i needed to i tryed flashing the Neutrino Rom.
After it was done it rebooted and said "failed to boot 2 starting rsd".
So I downloaded RSD Lite and found the unlock SBF which I applied. Now I can get into the FastBoot menu's and go to Android Recovery and try to do the back to stock option, it says it completes then reboots...
Then it just sits and sits and sits on the motorola Dual core logo.
Can someone please help me here. I cant seem to find any of my backups i made with system recovery or rom manager. I also didnt load RomRacers Recovery (which i just now noticed)
Any help is greatly appreciated.
Click to expand...
Click to collapse
i unlocked the bootloader after the update failed (i panicked) and yes it does say unlocked at the top now
Well, you mentioned you can get into fastboot so that's a start. You can try to flash a proper recovery and try to boot into recovery and see if you can mount the storage, or if you have a card reader you can just put a ROM on your sd card and then flash. If you can't get into recovery but you can get into fastboot you can flash a rom that way. You'll have to search for the procedure but I'm almost certain it can be done. If all else fails, you can install the unlocked "Full" SBF through RSD Lite, but it is not really recommended but should work.
SDRAKE101085 said:
i unlocked the bootloader after the update failed (i panicked) and yes it does say unlocked at the top now
Click to expand...
Click to collapse
Thanks so much. I got radracers on there and reflashed the neutrino rom again. Everything appears to be working. Now to just figure out the rest.
Thanks again.
Look tke the sd card and load the rom and google apps. Then go and fastboot wipe and re install the rom and try to boot honestly it just sounds like you got a corrupted rom
hey guys, searched the forum, found some stuff matching my post but figured i would put out an update. just rooted tonight, ive done these before and i used to be a member awhile ago but forgot what email used. anyway, galaxy s2 sch-r760. recovery problem. CWM doesnt seem to offer a proper recovery and im new to using odin so im not sure where to go from here. how can i go about making a backup if i cant get into recovery? i would like to do a new rom and back this thing up asap. need a new recovery or ideas for one. any help would be appreciated guys!
You need to expand on this.What did you do to root,do you have stock or cwm recovery?
Followed http://forum.xda-developers.com/showthread.php?t=1928566 to root. Its a generic CDMA. Root went fine. It tells me that it has root access. I am trying to flash CWM recovery and it won't boot into recovery from the CWM option. It shows the unpacking screen for a few seconds then reboots. As of now I am assuming its stock recovery because I can't get it to boot into recovery from CWM like I was saying
Tried doing a manual boot into recovery and it turned on, said galaxy s2, turned off then rebooted. Its acting like there is no recovery at all....
No help on this guys? Anybody mod generic s2 before?
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.
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.
Hello dear community
This is my very first thread I am making on this website, so please pardon me if I am on the wrong page of this website.
Anyways, I'm more or less desperate. I saw a youtube tutorial on how to install Android 4.4 Kit Kat on a Samsung Galaxy Note N7000 and I heard I'd need root AND a custom recovery.
Because I'm a total newbie to this kind of stuff, I tried the very first thing I saw that had something to do with custom recovery, because I already had my phone rooted. So, I looked up a tutorial on youtube on how to install CWM custom recovery and ended up with installing it successfully, but now my phone is stuck in a bootloop. As I already mentioned, I am a newbie and therefore I am very desperate at the moment, you know.
The only thing I can do is go to Recovery Mode, but if I try to turn the phone on it gets stuck in a bootloop (It actually doesn't loop at all, it just freezes at the moment when the Samsung Galaxy Note logo appears and doesnt do anything after that.).
I think my problem is that I actually threw a new Kernel on my phone, because the video title says "How to install Kernel with CWM [...]"
I would be very very very very very grateful if anyone was kind enough to help me get out of this!
I really need help!
Thanks!
PS.
If this helps you help me:
This happened when I had Android 4.1.2 installed.
There's going to be 2 ways to get out of this:
1) Reinstall the stock firmware via Odin.
2) Install a custom rom via recovery.
Personally, I'd go with number 2 because a) you wanted to update anyway and b) if you have the right recovery and rom, it'll be easier as you can just put the files you need on an external SD card and install via the custom recovery. Now, not all recoveries are able to flash any file. Many times you need specific ones to install the newer android versions. So, if you are wanting to install something 4.4 based, then using a recovery that was made, say, last year, probably will not work well if at all.
Another thing to try first, is to wipe the cache and dalvik cache in recovery since you said you tried to install a kernel. It is always recommended to wipe these when installing (assuming you did pick a compatible kernel with what you were trying to install).