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!
Trying to install clockworkmod but I have 3e recovery. I did it through rom manager which was a nub mistake but I didn't know 3e was going to troll me. So it says:
e:failed to verify whole file signature
e:signature verification failed samsung "3e"
I then followed this thread: http://forum.xda-developers.com/showpost.php?p=16909269&postcount=12
and tried the Speedmod kernel to get rid of 3e like the person said but that rom is for the international version and now I can't connect to verizon.
So at the point I am thinking using Odin is my only option but all roms are .zip and not .tar. I am clueless as what I can do. Please help me.
So I tried the Odin method in this thread http://forum.xda-developers.com/showthread.php?t=1026746 and flashed the pit and stock 2.1 files. It passed with green in odin but when I put the battery back in it boots into 2e but says # Manual Mode # at the bottom. I am not sure if that means the flash didn't actually work or what. I am lost now.
Thought I'd update this thread since I finally fixed the problem and sucessfully put Cyanogenmod7 without using the stupid Rom Manager after about 8 hours of work. So just in case someone wants to know what I did. For some reason Odin was not working so I used Heimdall v1.83 and the EB01 Heimdall package and sucessfully flashed to froyo 2.2. I mounted the sdcard and put Cyanogenmod7 and gapps on it.
Now I used Odin to flash the CM7 capable CWM (I think its version 4). Booted the phone into download mode and then used jt1134's ClockworkMod Recovery found in the CM7 fascinate wiki. The wiki says use Heimdall but I used Odin and it worked. The CWM is now blue instead of Red. Next I did a wipe data/factory reset along with wipe cache partition. I selected install zip from scard and choose the CM 7.1 package. Everything went well and it boots into CM7. NOW TO INSTALL THE GAPPS. I thought I just boot into CMW using the volume buttons and power button BUT NO that is NOT correct. In CM7 you have to hold the power button and press reboot and then select recovery AND THEN IN THAT CWM select install zip from sdcard (choose gapps). THIS IS IMPORTANT OR ELSE GAPPS WONT INSTALL. I was bummed for like another hour.
So there it is how to install CM7 just when you think you have been to hell and back with the fascinate. Never again am I volunteering myself to help root and install CM7 on a friend's fascinate. The droid incredible was soo easy!
Hi I have tried flashing my S2 but have run into an issue.
So i installed clockworkmod recovery 4.0.1.4 with the intention of installing cyanogen mod.
I then rooted the device using S2 root which said it was successful.
This was confirmed when i then installed and rom manager premium.
I downloaded Cyan from within rom manager and proceeded to install.
I selected to wipe data and dalivk.
The phone rebooted but hung for a long time on the white 3d triangle with an orange exclamation mark.
It then went into the clockworkmod recovery and I rebooted presuming everything was done.
Then my phone started as normal but went into the original rom but there was no app's, icons ect. I rebooted and app's icons were back.
So I rebooted into recovery mode again and tried to update from sdcard. no difference. So i read that wiping data/factory reset might help but now all i get is the boot loop between my carrier startup and the standard S2 startup.
I can still get into recovery and download mode but when i enter download mode I cannot see the phone in odin.
I have also tried putting the update.zip on my sd card manually from a PC download and use recovery mode to install it but thats not installing it either.
Any ideas or is my phone fubar?
All your questions answered and more in the dedicated thread http://forum.xda-developers.com/showthread.php?t=1176411
Hi thanks for the reply, i wish i had found that thread before attempting this.
I have managed to get odin seeing the phone now so its looking good.
problem i have is i need these:
XWKJ1:
Firmware info: PDA: XWKJ1| Phone: XXKI4 CSC:O2UKJ1
XWKJ1 Stock Kernel:
Password is: [email protected]
but multiupload was part of megaupload i believe so everything is gone.
Do you know where else i can find these.
Not sure why you'd want it, but
http://www.sammobile.com/firmware/ suggests http://hotfile.com/dl/145851215/0c1c8da/I9100XWKJ1_I9100O2UKJ1_O2U.zip.html
Thanks its just a learning curve, i will put cyan on again properly but want to learn as i go on how to do it right first time.
I've been following instructions to install Android 4.4 KitKat on Galaxy Mega 6.3 via Cyanogenmod 11.
My device has been rooted for some time, but I have never before installed any ROMs.
I have successfully (it seems) installed Clockworkmod via Odin, yet when I boot into Custom recovery mod, there is no "backup and restore" option, and indeed I seem to be in "Android system recovery", not CWM recovery (see screenshot).
I know that I can't install Cyanogenmod without Clockworkmod on board, so I'm nervous to proceed. Can anyone please advise?
AidanBell said:
I've been following instructions to install Android 4.4 KitKat on Galaxy Mega 6.3 via Cyanogenmod 11.
My device has been rooted for some time, but I have never before installed any ROMs.
I have successfully (it seems) installed Clockworkmod via Odin, yet when I boot into Custom recovery mod, there is no "backup and restore" option, and indeed I seem to be in "Android system recovery", not CWM recovery (see screenshot).
I know that I can't install Cyanogenmod without Clockworkmod on board, so I'm nervous to proceed. Can anyone please advise?
Click to expand...
Click to collapse
That looks like the standard recovery, not clockwork mod, what model of mega do you have?
You have to reboot to recovery first after flashing custom recovery. That's because the stock ROM checks if the recovery is changed and overwrites it with the stock recovery again.
Rebooting to recovery first will solve the issue.
Sent from my GT-I9205 using Tapatalk
Thanks for responding guys.
Jzsidebott: It's a Mega 6.3, GT-I9205, in England.
Silesh.Nair: I've installed "ROM Manager" and used "Reboot into recovery", but I get to the same place as before; "Android system recovery <3e>", exactly as the screenshot in my first post.
So I used Odin again, and again apparently successfully installed "GT-I9205-recovery.tar", but still I can only get standard recovery.
Could I ask you guys if you would recommend CyanogenMod Installer?
http://beta.download.cyanogenmod.org/install
I'm a newbie at this, so if this method is considered safe I'd be happy to go down that route. Any advice? Cheers.
Don't use ROM manager. Download the cwm tar file and use Odin to flash. Remember to untick auto reboot in Odin and then reboot to recovery first. It will work for sure. Don't flash anything if you are running Knox enabled firmware else you'll screw up your phone.
Sent from my GT-I9205 using Tapatalk
Thanks. As I said I did use Odin to flash. I just installed ROM Manager afterwards to try to find out whether the Odin Flash had worked. I am a newbie at this and to be honest I have no idea what Knox enabled firmware is or whether I'm running it. I think that for safety's sake I'd best drop the whole thing and not risk bricking my phone, but thank you all for the help all the same.
Hello,
I come for you, because I am trying to install android 4.4 on my phone, because android 4.3 isn't compatible with pokemongo.
I have a galaxy s3 GT-I9300 from a few years, I've never rooted it and it runs on android 4.3.
I've been looking for guides that say that I need to install CWM recovery to then be able to install CyanogenMod.
So I've downloaded Odin, and CWM recovery, added the CWM recovery .tar in the AP box of Odin, put my phone on download mod, plugged it, and run Odin.
It appears that it works succesfully, but when I reboot my phone in recovery mode, I still have Android Recovery System <e3>, and I can't install zip from sdcards (if I understood correctly, <e3> doesn't support zip, whereas <e2> does, and CWM is supposed to put it to <e2>), so I can't install CyanogenMod.
Here is a screenshot of my Odin after running it: (I can't post the link since I'm a new user, so it's on imgur)
/87oPm2l
I can't think of any more information to provide for now.
Thanks for your help.
chocolote4444 said:
It could be permission issues. But try using a different cable.
Also, the recovery you are flashing has to support the model of the phone, otherwise, Odin will refuse to install it.
Click to expand...
Click to collapse
Thanks for the answer, I was not in root mode.
I fixed it and it now works, I have been able to install CyanogenMod from the zip in recovery.
Now I tried restarting my phone, and it's stuck in "Android is starting".
I have a little blue alien popping on my screen, then the screen turns off, then the screen turns on and says things like "starting applications, preparing settings, optimizing applications". But it seems to be doing it on repeat and it's been an hour. Is it normal that it takes so long? I haven't seen it mentionned anywhere from what I checked.