Hi.
I've tried searching for an answer but can't find anything like this.
I was using Turkbeyrom v3 for some time; I saw V5 and gave it a try. I've done several rom changing so I have some idea how it works. Also I've rooted the phone (Galaxy S2) with Odin and then (another) with the "new method" (one click opens a bat file, uses zergrush). Anyway; after a day or two I realized wifi wasn't working so I decided I will try another rom; as usual, I went to Titanium Backup to make a backup but told me it didn't have root access. After trying SuperSu (came included) couldn't make it work either. So I decided I would just wipe everything and try a fresh install. However, can't boot into recovery mode. I only get an option "Press Home to boot the second ROM" and a countdown; tried the "second" rom but won't start. So I'm stuck with Turkbey V5 which seems to have done something with root access since I can't update Superuser or SuperSu, this makes Titanium and even RomToolkit useless.
I tried to root via the "new method", it does everything, but I still can't get root access or boot into recovery.
While writing this I realized that now I'm stuck on the animated start screen.
Any idea on how can I fix this? I can't boot into recovery, and now the phone is stuck in the animation.
Thanks.
Not familiar with the dual boot thing, so please search before doing this or let other help you....
Flash a cwm using Odin, you can flash any CF-root to get that.
Remove battery
Now get in to cwm recovery
Format data, cache, system from mount and storage
Now flash stock GB ROM using Odin.
Should be fixed, now get root and flash what ever you want to
Sent from my GT-I9100 using Tapatalk 2
As you are using dual boot you can only afford to use siyah kernel. Download the Odin version of siyah and flash it, all your problems will be solved. Additionaly if you need su app install it from market.
Sent from my GT-I9100 using xda premium
Related
I have successfully been able to root and install everything on my Mytouch4G just fine, however, when I tried to install my wife's Vibrant, I am stuck. Here is what I have done:
1) I rooted successfully using superoneclickv1.9.1
2) I installed ROM Manager and also downloaded the Auxora ROM to get ready to install
3) When I flash CWM recovery, it says current and latest recover is 2.5.1.2 (concern here that my mytouch says 3.0.2.4 - do different phones install differently with CWM?). When I look at all CWM recoveries I also notice there is two seemingly more current versions available 2.5.1.3 and 2.5.1.4. I have left it at .2 but wondering why all the versions.
4) When I reboot into recovery, I always get the stock recovery and have not been able to get CWM recovery so I am unable to flash my Auxora ROM. I ran update packages numerous times, and get a signature verification error. I have tried a recovery 3e patch that does not work either. I also gave a try at downloading and SDK, but received temp root errors (phone is already rooted).
After reading many posts, I cannot seem to get a direct answer on what I should do to get CWM to actually boot properly, so I can flash a ROM. Someone said to flash the stock JDK rom, but if I can't boot into recovery, how can I flash anything.
Any help would be greatly appreciated.
You need to get a program for your pc called odin to get back to stock. you can find that and instructions on how to use it if you search for the daily updated vibrant bible its GREAT
http://forum.xda-developers.com/showthread.php?t=849028
going to stock eclair heres a a great guide
So going back to stock eclair will then allow me to install CWM recovery then load roms?
Every once n a while I haft do the install packages thing twice before it gives me clockwork green
. Hope this helps.. o n btw u should look at some of the other roms in the bible before u try auxora
yes u should go back to stock eclair for every rom, in my opinion. Then after that do the 3 button combo and install packages and u will have to do it twice and then the green screen will kick in and ready to rock a new rom.
i hope this helps
What is your current firmware?
I see you posted over in the "NOOB GUIDE" thread, you should really try to root using the method posted there and not any one click root apps.
This should be the root method everyone uses:http://forum.xda-developers.com/showthread.php?t=723479
After root your phone recovery should be blue. Choose "reinstall packages" gives you green recovery(this may need to be repeated multiple times to work possibly including flashing CwMRecovery with ROM manager. I recently did it 5 times b4 i got green recovery)Once you access green recovery chose "apply sdcard:update.zip" go into advanced and choose "reboot recovery" This should give you red recovery. Do a nandroid backup and flash away. Good luck!
Another option you could do is to download SGS kernel flasher from the market and flash a voodoo injected kernel with that app. Then when you boot into recovery you will have red voodoo recovery and you can flash away.
Odin to stock the best way to flash a new rom
Sent from my SGH-T959 using XDA Premium App
jman531 said:
So going back to stock eclair will then allow me to install CWM recovery then load roms?
Click to expand...
Click to collapse
The stock 2.2 that Samsung distributed with their Kies tool has a recovery that checks signatures. Everything earlier does not check signatures. So either use something earlier to get CWM running, or use a ROM that doesn't have the stock 2.2 recovery in the first place, or mod your recovery using the method described in http://forum.xda-developers.com/showthread.php?t=833423
Using Odin to go back to stock Eclair between your flashes of modded roms has the benefit of taking care of this, and also can clear up left over bits and pieces that may interfere with the proper function of your new ROM.
ok, i followed the instructions and am back to eclair, however, whenever I install packages, it just reboots the phone, not even back into stock recovery. I use the 3 key method and get into recovery, run install packages, and the phone just boots back up...its like it isn't running the update.zip file...
UPD: When i load rom manager and try to reboot into recovery, it says the application superuser permissions has stopped unexpectedly and keeps force closing now....titanium backup wont run now either, my root permissions seem whacked after going back to eclair?
UPD2: I followed instructions to unroot and reroot here: http://forum.xda-developers.com/showthread.php?t=739300
It removed superuser, then added it back again, but I still get the unexpected error and it appears my root is not in place. I am back to eclair, and now need a certain way to get my root fixed, so I can try and flash CWM recovery. Without root working, it is not letting me. My wife hates me now for doing this to her phone, so those of you that are married, I would appreciate your assistance to get back on her good side...before Mother's day...please? =)
Ok, thanks for all the help, however, I am really back where I started. I can only get stock recovery, and for the life of me, cannot get CW recovery to load. I used ODIN to go back to eclair on the vibrant, have a good root on the phone now, and no matter how many times i reinstall packages i cannot get clockworkmod recovery to load, ever. Any more thoughts out there?
I had this trouble a few months back. Things to check before going into recovery:
You gotta have root access.
Make sure you have debugging on
Install busybox FIRST
Try uninstalling Rom manager and reinstalling the latest version.
apply the recovery for vibrant and let it boot into recovery.
When it boots into recovery Don't try to install packages yet. Just reboot.
Look here for the files:
http://forum.xda-developers.com/showthread.php?t=833423&highlight=3e+recovery
When it boots up push the update.zip to the sd card on the phone, not the external card.
Run the script and it should reboot back into recovery.
You should now be able to install packages.
This way has always worked for me.
starkiller86 said:
I had this trouble a few months back. Things to check before going into recovery:
You gotta have root access.
Make sure you have debugging on
Install busybox FIRST
Try uninstalling Rom manager and reinstalling the latest version.
apply the recovery for vibrant and let it boot into recovery.
When it boots into recovery Don't try to install packages yet. Just reboot.
Look here for the files:
http://forum.xda-developers.com/showthread.php?t=833423&highlight=3e+recovery
When it boots up push the update.zip to the sd card on the phone, not the external card.
Run the script and it should reboot back into recovery.
You should now be able to install packages.
This way has always worked for me.
Click to expand...
Click to collapse
thanks...It is rooted, but not sure about busybox...the stock recovery is 2e now since I went back to eclair, so not sure i should follow that link as it talks about modifying 3e and making it backwards compatable. I did use that process before I went back to eclair, and it didn't work for me. I have uninstalled rom manager, and reinstalled...and it is different in that it shows a flashed recovery 2.5.1.2, and never asks me for my phone type anymore...it used to ask me and i had to select vibrant....is the recovery supposed to be 2.5.1.2? when I show all recoveries it lists .1, .2, .3, .4 so wondering if I should use .3 or .4...why does it stay at .2?
starkiller86 said:
I had this trouble a few months back. Things to check before going into recovery:
You gotta have root access.
Make sure you have debugging on
Install busybox FIRST
Try uninstalling Rom manager and reinstalling the latest version.
apply the recovery for vibrant and let it boot into recovery.
When it boots into recovery Don't try to install packages yet. Just reboot.
Look here for the files:
http://forum.xda-developers.com/showthread.php?t=833423&highlight=3e+recovery
When it boots up push the update.zip to the sd card on the phone, not the external card.
Run the script and it should reboot back into recovery.
You should now be able to install packages.
This way has always worked for me.
Click to expand...
Click to collapse
OK>>> I GOT IT... Thanks to everyone who helped...Here is what was needed:
1) Install ODIN, install back to eclair
2) uninstall ROM Manager, reinstall
3) I needed to select the 2.5.1.2 recovery from the list again (this was important as it somehow knew of the previous load, but files were missing, or something was just wrong.) It finally loaded properly, and asked for phone type again, so selected vibrant
4) I rebooted into recovery, and instead of install packages, i rebooted once, as starkiller suggested
5) After reboot, went back into recovery from rom manager, and this time installed updates, and it showed that it replaced the recovery with CWM.
6) It rebooted into stock recovery however, so I once again selected install updates, and it went right into CWM recovery, and now I am flashing happy!!!
Thanks again everyone...this was soooooo different than my mytouch4g!
If you have the Kies update of Froyo, the 3e mod will sometimes not work. I've gotten to CWM though , but its best to downgrade then flash a ROM from there.
I just wanted to bump this thread because it really helped me.
I've messed around with numerous android phones, and I've never had thie issues I've had with this phone getting into recovery to flash ROMs
Thank you!
Hi all,
I rooted my SGS2 (KE7) with CF-Root ages ago and haven't done much since then, aside from take regular backups.
Looking at the Cyanogenmod stuff, I fancy giving it a go. All the guides talk about using the kernel at http://forum.xda-developers.com/showthread.php?t=1118693 .
Does anyone know if I can flash the cyanogenmod ROM using the recovery mode I have with CF-Root, or if I need to get use the kernel from the above patch first?
This morning I tried installing the kernel (from the CF-Root CWM), when my phone rebooted, the touchscreen worked on the unlock page but not once I unlocked (I use LauncherPro as my launcher). Rebooting into recovery mode didn't work (the phone just booted normally) so I reflashed CF-Root but still had the same problem however I could boot into recovery mode and restore this morning's backup.
Now, the phone boots (with the warning triangle, expected) but there is no response after I unlock for a minute or so. Setting the stock launcher back works but I'm confused about why this should happen and what I should do next.
Does anyone know why my non-stock launcher is now being non-responsive for the first minute after boot / what I can do to get it back?
Am I able to install cyanogen with CF-root, or do I need to use the kernel in the above link? and if so, do I need to do anything other than just flash and if not why didn't the phone boot into recovery when I tried it earlier?
Any suggestions gratefully received!
-Jeff
The cf-root kernel is all you need to install cm7.
peachpuff said:
The cf-root kernel is all you need to install cm7.
Click to expand...
Click to collapse
This is correct. However, after you install the cm7 .zip the first time, it will have only installed the kernel for cyanogen mod. So you will then need to boot back into recovery with 3 button mode and run the zip install again from there. You will then have CM7.
Electroz said:
This is correct. However, after you install the cm7 .zip the first time, it will have only installed the kernel for cyanogen mod. So you will then need to boot back into recovery with 3 button mode and run the zip install again from there. You will then have CM7.
Click to expand...
Click to collapse
Don't quite understand this. I've got the cm_galaxys2_full-39.zip (100MB), I was going to put this on the SD card, boot into recovery mode and install from there. Are you saying I need to do this same process twice? (and if so, why does it only install the kernel the first time when it is the complete zip file?)
Cheers,
-Jeff
CF-root => Cyanogen mod
Hello everybody,
There are a few threads that discuss this question, but they all draw a different conclusion.
This one for instance : http://forum.xda-developers.com/showthread.php?t=1367933 (or if the link is broken, search for : How can i use cf-root kernel for cm7?).
In the thread above they claim that CF-root is not compatible with CM7, however in this very thread there is said that when installing the .zip file twice, it should work just fine. As i'd like to install CM7 on my CF-rooted S2, i have to know for sure:
Is there a way to install CM7 on a CF-rooted device?
Many thanks
Rom manager doesnt work with cf root, so to flash cm7 download the zip, boot into recovery, and flash the zip twice, and it will work.
Make sure you wipe data and cache, and take backups before you do.
Sent from my GT-I9100 using Tapatalk
Ok, i'll give it a go .
Thanks for the quick response, it is much appreciated!
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.
Hi guys! I have been reading through the post and searching for possible solution to my Galaxy Tab GT-P1000 problem but I cant find any solutions. Here is the story:
I have flashed the GT-P1000 tab with clockworkmod version 6 (i am not sure the exact version) using Odin.
Now after flashing the recovery, I have successfully installed Cyanogenmod 11 (nightly build) and everything was successful and everything is great.
A friend of mine borrowed the tab and he put a pattern to lock the phone, instead of asking him what is the pattern I just decided to wipe the tab again to make a clean install. So what I did was I went to recovery and selected "format /system" which I shouldn't have, then after rebooting it is not booting up to Cyanogen anymore, so what i did was I just wiped everything (format /data, cache and factory reset)
Now this is the weird part, the devices has kept on booting up to clockwork recovery and it says the device is not yet rooted, it is asking me if it is ok to root it, I always selected yes
After another boot up, the clockwork recovery is now version 3.0.0.5??? it is really weird? I never installed any clockwork mod with a lower version... How did that happen?
Now whenever I try to install from sd card or restore it or mount it nothing happens, it just says:
E:Can't mount
E:unknown volume
E:unable process volume! skipping
I tried to flash the recovery again using Odin many times but still the clockwork mod is stuck in version 3.0.0.5.
Right now, I am not sure if my understanding of the entire system is correct:
1. Should I install a new recovery, if yes, how and why is it whenever I am installing it again it is not being installed, it gets stuck to version 3.0.0.5?
2. Are there any other recovery I should use and how should I install it? is it the same as using the Odin?
3. Is there a way to install the original recovery of this tab and then from there I will start over again.
@Battousai1
1. & 2. Find an Odin flashable recovery for p1000... Go to download mode and flash it with Odin...
After doing that you shouldn't have the problem anymore...
3. To install the original recovery find the stock rom which is again Odin flashable ... Flash it and you'll have the stock recovery...
Sent from my GT-P3100 using Tapatalk
zeetherocker said:
@Battousai1
1. & 2. Find an Odin flashable recovery for p1000... Go to download mode and flash it with Odin...
After doing that you shouldn't have the problem anymore...
3. To install the original recovery find the stock rom which is again Odin flashable ... Flash it and you'll have the stock recovery...
Sent from my GT-P3100 using Tapatalk
Click to expand...
Click to collapse
@zeetherocker, thanks! I am currently downloading the overcome recovery, hopefully this will solve the problem.
@Battousai1
Good luck... [emoji106]
Battousai1 said:
@zeetherocker, thanks! I am currently downloading the overcome recovery, hopefully this will solve the problem.
Click to expand...
Click to collapse
Hi guys, just an update, I have finally managed to restore my device's software back to its original version. Thanks to Overcome. Here's the thread for those who still have this device and have some similar problems: http://forum.xda-developers.com/showthread.php?t=1881981