I have ClockworkMod 5.5.0.4 currently installed, when I reboot into recovery mode, the menu scrolls by really fast on an endless loop, and I cannot select anything.. So I was wondering how I would get the stock recovery back onto my tab.. Any help is much appreciated.. Thanks
I think you got the rolling CWM issue:
Look over here: http://forum.xda-developers.com/showthread.php?t=1555984
I'm now at 4.0.4 and have the hc stock recovery somewhere.
Whithout knowing that ics has the same recovery than hc exactly, and I'm not convinced that it is so, don't think it helps you much.
But the above Link could help you way better.
edit1:
i had same issue with CWM 5.5.0.4, flashed a different bootlaoder and it worked...BUT if you then recover back to hc for example you get strange behavior here... just tbh
the best way is to flash the entire firmware on the tab. And obviously the more destructive one too.
I suggest you also to install the cwm recovery 5.5.0.4. That's the only non-rolling recovery you will find, and to do that it's not necessary to reinstall the stock one
here's the link to the good recovery for you: http://www.teamovercome.net/p7500/?page_id=8.
If you're already using this and still have the rolling screen, the problem is the bootloader: so follow this post http://forum.xda-developers.com/showpost.php?p=27830023&postcount=41 and your recovery should be fine.
If the problem still goes on, problably you did a little bit mess flashing roms and recoverys and in that case your only solution is to flash the entire stock firmware erasing all the old stuff and then reinstall cwm, root the device and so on.
Thanks for all your help guys I will give it a shot..
Sent from my SGH-I727R using xda app-developers app
Related
I am trying to put Clockwork Recovery on the Vibrant and when I first boot it I need to manually select "reinstall packages". I usually have to do this two times in a row and then it boots into the cw recovery. But when I reboot into the recovery it boots back into the samsung recovery and I have to select "reinstall packages" again to get into cw. This isn't normal correct? I saw that I should only have to do this once and then it should boot into cw recovery everytime with no problems. The phone came with 2.2 stock.
In my experience with stock roms, i have to hit re-install packages twice to go to clockwork recovery.
Well what I am wondering is do you have to do that everytime you want to go into the recovery? Also could that possibly affect the phone to where I would not be able to restore it back to factory if something were to go wrong if I flashed a new ROM?
i assume you have rom manager right? You can do select reboot into recovery so that it will bring you straight to clockwork mod recovery. Also there's an app called "quick boot", that can make you go to recovery or download mode faster.
And no that won't affect anything when you want to flash another rom.
Your fine. Recovery will not effect going to back to stock because odin overrides all. Like the other guy said when your using a stock rooted rom you almost always have to hit it twice. Flash a custom rom and it will always go into recovery with out a hitch.
Sent from premium app
rom:trigger 2.9.3
kernel;overstock 1.4.3
theme:custom mash of all orange/tangerine
Ok, thank you for your help. I didn't know if it was having a problem or something.
Sorry for the bump, but I didnt want to start a new thread.
I'm having this same problem, but reinstalling the packages isnt working. I've done it 3 or 4 times
Tbry said:
Sorry for the bump, but I didnt want to start a new thread.
I'm having this same problem, but reinstalling the packages isnt working. I've done it 3 or 4 times
Click to expand...
Click to collapse
This should help you out.
Thanks for the link. I decided it is probably a better idea just to get a new kernal. My vibrant has andriod 2.1.1 right now. I read elsewhere that custom kernals come with clockwork recovery, plus that would eliminate any problems with my current kernal and the 2.2.1 ROM I am about to flash... Right?
Just need a guide for it.
Edit: I'm trying this. How long is it supposed to take?
Edit2: it failed when it trys to stop the adb server.
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.
Hi, so I bought a used TF201 from someone that had already rooted and put CM10 on the tablet. However, idiot me decided to factory reset using the system settings instead of going into the CWM and doing a factory reset. This put me into a CWM loop, as I could only boot into CWM recovery mode. I used this guide to unbrick my device, and it worked. However, the problem is that everytime I want to update CM10 to a new nightly, I get stuck in CWM recovery again, and have to apply the fix every time. Is there any way to fix this? I don't want to have to do the unbricking every time I update CM10. Thanks!
yeee707 said:
Hi, so I bought a used TF201 from stock someone that had already rooted and put CM10 on the tablet. However, Idiot me decided to factory reset using the system settings instead of going into the CWM and doing a factory reset. This put me into a CWM loop, as I could only boot into CWM recovery mode. I used this guide to unbrick my device, and it worked. However, the problem is that everytime I want to update CM10 to a new nightly, I get stuck in CWM recovery again, and have to apply the fix every time. Is there any way to fix this? I don't want to have to do the unbricking every time I update CM10. Thanks!
Click to expand...
Click to collapse
Stop using CWM. That is what is causing all your problems. Go to TWRP website and get ICS version. Make sure you don't flash the jellybean version on your ICS bootloader or you might brick it.
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?
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.