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!
I feel like such a n00b but I've literally flashed dozens of ROM's between my Captivate and my Infuse.
Thanks for Entropy, I have my modem back so I can make calls (thank you!).
Now I'm trying to get back into CWM but everytime I flash it in Rom Manager...then reboot into recovery I get this error..
E:failed to verify whole-file signature
E:signature verification failed
And that's in 3e...it won't boot into CWM.
I tried rerooting and using the SGH-I777_ClockwordMod-Reovery_5.0.2.3.tar in Odin...when I reboot in recovery...it freezes up...
Any suggestions?
Hmm that one is odd.
Until further notice - don't use ROM Manager on our device. Kernel-included CWM is the way to go. My guess is that somehow ROM manager dorked up your system partition. You may need to Odin/Heimdall back to stock, then flash codeworkx's CWM kernel, although I'm surprised you weren't able to enter CWM after flashing codeworkx's kernel...
Edit: When you say it "freezes up" - do you mean stuck at the Samsung Galaxy S II screen, or does CWM come up?
If I flash back to stock and try to get into recovery...I get stuck at the above mentioned screen.
If I Odin the CWM 5.0.2.3 package and try to get into recovery...I get into the light blue recovery screen but every option I click on just brings me to the Rom Manager Hat Icon and does nothing (even though I don't have Rom Manager installed anymore). I get stuck in that menu...pull the battery...reboot...still in light blue CWM menu but every option just brings up the Rom Manager Icon.
Only way to "fix" is to get back into download mode, odin back to stock or re-odin the CWM 5.0.2.3 tar again. But, again, if I try to get into recovery from stock...3e recovery (ie useless) if I Odin back to CWM.tar...I get stuck in Rom Manager Icon hell.
Entropy512 said:
Hmm that one is odd.
Until further notice - don't use ROM Manager on our device. Kernel-included CWM is the way to go. My guess is that somehow ROM manager dorked up your system partition. You may need to Odin/Heimdall back to stock, then flash codeworkx's CWM kernel, although I'm surprised you weren't able to enter CWM after flashing codeworkx's kernel...
Edit: When you say it "freezes up" - do you mean stuck at the Samsung Galaxy S II screen, or does CWM come up?
Click to expand...
Click to collapse
Furthermore, the first day I had the phone, I used Rom Manager to install MUIU and it worked fine! Except I had the wrong modem (which I just found out today). I thought MIUI screwed up my phone (because I was unable to make calls) so I then flashed back to stock. Luckily someone posted the stock modem up and I installed that...phone works fine.
I'd like to get MIUI on again because it was smooth as butter and all I did is download the Rom Manager version...i Know it's not supposed to work but it did.
Drew489 said:
If I flash back to stock and try to get into recovery...I get stuck at the above mentioned screen.
If I Odin the CWM 5.0.2.3 package and try to get into recovery...I get into the light blue recovery screen but every option I click on just brings me to the Rom Manager Hat Icon and does nothing (even though I don't have Rom Manager installed anymore). I get stuck in that menu...pull the battery...reboot...still in light blue CWM menu but every option just brings up the Rom Manager Icon.
Only way to "fix" is to get back into download mode, odin back to stock or re-odin the CWM 5.0.2.3 tar again. But, again, if I try to get into recovery from stock...3e recovery (ie useless) if I Odin back to CWM.tar...I get stuck in Rom Manager Icon hell.
Click to expand...
Click to collapse
Might be because the buttons aren't the same as they are on the Captivate and each time you hit power or menu (which used to be select on the Captivate) it kinda blanks out the menu until you press it again. Use the volume keys to move up and down, home button to select, and back button to go back.
whoa, I'm retarded...that worked...thanks!
Yeah I was losing my mind too when I was first trying to flash Cognition. Just started mashing buttons and got lucky
Drew489 said:
Furthermore, the first day I had the phone, I used Rom Manager to install MUIU and it worked fine! Except I had the wrong modem (which I just found out today). I thought MIUI screwed up my phone (because I was unable to make calls) so I then flashed back to stock. Luckily someone posted the stock modem up and I installed that...phone works fine.
I'd like to get MIUI on again because it was smooth as butter and all I did is download the Rom Manager version...i Know it's not supposed to work but it did.
Click to expand...
Click to collapse
I9100 roms will work to an extent, but like you noticed there roms do not support our modems or capacitive keys. Could be other things that are unsupported as well.
Drew489 said:
If I flash back to stock and try to get into recovery...I get stuck at the above mentioned screen.
If I Odin the CWM 5.0.2.3 package and try to get into recovery...I get into the light blue recovery screen but every option I click on just brings me to the Rom Manager Hat Icon and does nothing (even though I don't have Rom Manager installed anymore). I get stuck in that menu...pull the battery...reboot...still in light blue CWM menu but every option just brings up the Rom Manager Icon.
Only way to "fix" is to get back into download mode, odin back to stock or re-odin the CWM 5.0.2.3 tar again. But, again, if I try to get into recovery from stock...3e recovery (ie useless) if I Odin back to CWM.tar...I get stuck in Rom Manager Icon hell.
Click to expand...
Click to collapse
I lost 4 hours of kernel development time to this thinking I broke something - see below.
tysj said:
Might be because the buttons aren't the same as they are on the Captivate and each time you hit power or menu (which used to be select on the Captivate) it kinda blanks out the menu until you press it again. Use the volume keys to move up and down, home button to select, and back button to go back.
Click to expand...
Click to collapse
This is correct - it's why you see a bunch of posts between myself, codeworkx, and atinm in the CWM thread.
The current behavior is a bit odd, but it is usable, it's just not documented properly right now.
I have a similar problem, I've found that whenever I get that message, and none of the options on cwm work I pull the battery and turn it back on and the install resumes. Not sure why it hangs up like that but its led to a few tense moments already
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.
im on stock root and i wanted to hopefully flash a rom, but first i needed a custom recovery. On my phone, i downloaded Rom manager and it asked me to install cwm. it found my device and it downloaded and said installed successfully. i rebooted into recovery and from there it loops and boots into recovery non stop. i remove the battery and put it back in and it still tries to boot into recovery with the loop. (Semi-fix) when i remove my battery and boot into download mode. i can cancel it and it will skip trying to boot into recovery and load just fine. i can then shut down or restart as needed. but booting back into recovery will start the issue over again. i just want to know a safe way to have cwm on my note 3, or how to revert it back to normal. any help please?
scarface195894 said:
im on stock root and i wanted to hopefully flash a rom, but first i needed a custom recovery. On my phone, i downloaded Rom manager and it asked me to install cwm. it found my device and it downloaded and said installed successfully. i rebooted into recovery and from there it loops and boots into recovery non stop. i remove the battery and put it back in and it still tries to boot into recovery with the loop. (Semi-fix) when i remove my battery and boot into download mode. i can cancel it and it will skip trying to boot into recovery and load just fine. i can then shut down or restart as needed. but booting back into recovery will start the issue over again. i just want to know a safe way to have cwm on my note 3, or how to revert it back to normal. any help please?
Click to expand...
Click to collapse
Pull battery let it sit for two minutes. Push menu button, volume down button, and power button at the same time boot into download mode. once there flash a fresh copy of your OS which ever version of KitKat your running. You lose all your personal data, but your beyond that now. Then here is link to my thread should answer all your questions http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 enjoy !!!
uknow said:
Yeah ive said it a few times this should not be used
If youve bricked your phone you can get back into your phone by holding volume down menu botton and power botton at the same time when it pops up the warning screen to enter download mode hit cancel your phone will then boot up after your phone is on if you do not have a computer the way you fix the phone so you dont have to do this every time your phone is off you need mobile odin and a kitkat cwm.img.tar for our phone flash it and problem solved you can now boot into cwm recovery then if you want you can flash a twrp img zip through cwm or just keep cwm hope this helps
Ps if you Google mobile odin the dev gives it away on his xda mobile odin page
Click to expand...
Click to collapse
.............^^^^^^...........
stuck in recovery loop also
hi i am new to all this..i managed to get my sprint note 3 4.4.4 NK4 rooted and i read that i also needed a custom recovery so i used odin to install "philz_touch_6.08.7-hltespr.tar.md5" and it said success but when i tried to get into it it just says recovery is not seandroid enforcing i also used rom manager to get into it automatically but it just keeps looping saying same thing. is there a way out of this mess?
update-- i found an updated version of the philz tar file and installed it with odin and that got me out of the loop..just havent tried to get back into recovery yet...lol
Cat1970 said:
hi i am new to all this..i managed to get my sprint note 3 4.4.4 NK4 rooted and i read that i also needed a custom recovery so i used odin to install "philz_touch_6.08.7-hltespr.tar.md5" and it said success but when i tried to get into it it just says recovery is not seandroid enforcing i also used rom manager to get into it automatically but it just keeps looping saying same thing. is there a way out of this mess?
Click to expand...
Click to collapse
First, pull the battery for a minute then reinstall hold the power, menu, and volume down buttons at the same time and boot into download mode. The version of Phil'z CWM you flashed is to old for 4.4.4 NK4. Now download to your desktop the right Philz CWM recovery file (Phil'z_Touch_6.48.4-hlte.tar.md5 ) here is the link https://goo.im/devs/philz_touch/CWM_Advanced_Edition/hlte/ there are two listed use the second one. Flash with odin and you should be good to go. Go to my thread http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 for more info.
done exactly as you said and the same screen came up saying recovery is not seandroid enforcing and then it jumps to Philz Touch 6 so im assuming everything is right now...i really appreciate the help! tyvm
different rom
ok..i installed cyanogen rom..i also used titanium backup..i want to go back to where i was but i dont see titanium backup on there anymore..how do i revert back?
i guess i need to update my phone n900p (help)
my rooted note 3 was running 5.0 L so i tried flashing a custom recovery both TWR and CWM now its stuck in boot loop. i read all the post showing you how to get out the bootloop. how ever i still need to put a recovery on my phone are there any updated links for this with odin because i was using the odin 3.0 sorry odin 307
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.