Hi there,
After not reading this tutorial very carefully, I installed clockwork mod via odin using the proper method but then used Rom manager to update to CWM 3.x. I tried re-flashing the original file to get the previous version the same way I did previously, but I keep getting a red failed box above the yellow com port. What can I do? can I use the 3.x CWM installation to manually install roms or is that not a good idea?
Thanks for your help!
-noob
It seems your first problem is that "failed" message you're getting in odin. Something isn't communicating properly. Be sure to use the original OEM cable that came with the phone. Second, make extra sure your drivers are installed properly, and that you have the right version. (32 or 64 bit version) Last, make sure Odin installed properly, and your usb port is functioning correctly. Disconnecting other usb devices may help, if the problem is caused by a fouled up usb controller on your computer.
If you get odin working, then simply flash the newest RED cwm. It depends on if you have the voodoo lagfix enabled as to which cwm you need (orange cwm 3.0 doesn't support voodoo conversions), but personally, cwm 2.5.x.x works best for all amend scripted roms/themes. The newest community rom (which is amazing) was written with the newer edify scripting, which cwm 2.5 supports, but there is a newer red cwm that we really all need to be using. Just search the development stickies for more info.
Last, try booting into cwm manually instead of through Rom manager. Hold volume up, down, and power, then release only power (continuing to hold volume up and down)at the samsung logo until you see red cwm.
Related
hello all,
Just flashed this ROM using clockwork, only problem I ran into was clockwork will not reboot into recovery. Instead it reboots into samsung recovery.I would like to re-flash ROM. I am new to this, I was an iPhone user and it was pretty simple to reinstall operating system.
I use a macbook with snow leopard, what is going to be my best option to re-flash with the macbook. I have read about Odin, and ADB. But not really sure which to use or how to use them for just flashing a custom ROM.
Any help would be great!!!!1
RAMROD
Search "boot into recovery"....using buttons.
Power off
Hold vol+/vol- (keep holding)
Hold power (keep holding all three buttons)
Wait vibrant screen...wait for black...wait for second vibrant screen and release power button ONLY.
Should be set.
OR
Search for OS X...you can use Terminal to manually flash/reboot/etc. through utilities. Be careful though, the commands are slightly different.
I'm running OS X 10.4 (tiger) and never have to use the computer (outside of TGA_Gunman's one click root program)...everything can be done through the phone in most cases.
I have no problem getting it in this mode. I am trying to get it to boot into clockwork recovery, and the only thing that is loading is the stock kernal recovery menu.. So I am looking for a method that I can do it with my macbook. I have searched in google, and found other tutorials for other phones, but not the vibrant. If you know of one please let me know..
thanks
in sammy recovery hit 'reinstall packages' (may need to do this more than once) and it will reboot you to clockwork. then flash through clockwork like normal. this is why you need to leave the update.zip file on your sdcard after installing clockwork.
funeralthirst said:
in sammy recovery hit 'reinstall packages' (may need to do this more than once) and it will reboot you to clockwork. then flash through clockwork like normal. this is why you need to leave the update.zip file on your sdcard after installing clockwork.
Click to expand...
Click to collapse
I never removed the zip file from sd card, in fact while looking at the files contained in clockwork mod file. It contains the same files as my other Vibrant that is running fine. Just doesn't have Bionics Obsidian 2.2 running on it..
I tried what you said about clicking on re-install and did that 5-6 times. That didn't improve the problem.
thanks for the idea,
Back to the original Question, what is the easiest way to load different rom on my phone with my macbook?
Does the phone still boot up normally? If so, open Rom Manager and select "Flash ClockworkMod Recovery". Then select your device. Reboot into recovery and if you are still in the stock recovery, hit "Reinstall Packages". If that doesn't work, then I have no idea...
I have no ideal how to do anything... and is willing to try anything. CWM Recovery Will Not Install Roms... Error comes up- Amend scripting (update-script) is no longer supported.
amend scripting was deprecated by google in android 1.5
it was necessary to remove it when upgrading to clockwork 3.0 gingerbread based recovery please switch to edify scripting (updater-script and update-binary) to create working update zip packages.
installation aborded
Does anyone know how to update Amend to edify on the Fascinate?
Well, generally that decision is up to those making the scripts. I believe you're just looking to make it where you can flash things in CWM, and you need a different version of Clockwork to do that. Simply download the "cwm-recovery-ALL.zip" and flash that (Or use the Odin .tar file, either works the same)
http://forum.xda-developers.com/showthread.php?t=942021
Now go flash something. Wait, that came out wrong.
Its not working... i installed both ways... odin installed, but didnt work... i tried to flash it, but it said i needed to update to edify... help?
First, don't boot into CWM from ROM Manager. Avoid this. if you Odin it, then boot into CWM manually by shutting phone down, hold volume up, down, and power. When you see the samsung logo, release only the power. Continue holding volume up and down until cwm appears.
Do not use ROM Manager for any flashing on the fascinate, otherwise you end up exactly where you are. It's a great program, but it currently does not play nice with the fascinate.
What should i flash with? cwm isnt comping up... whats should i try? it comes up cannot find update.zip when i click install update.zip. cwm dosent come up when i keep holding the volume up volume down buttons
artvandelay440 said:
Well, generally that decision is up to those making the scripts. I believe you're just looking to make it where you can flash things in CWM, and you need a different version of Clockwork to do that. Simply download the "cwm-recovery-ALL.zip" and flash that (Or use the Odin .tar file, either works the same)
http://forum.xda-developers.com/showthread.php?t=942021
Now go flash something. Wait, that came out wrong.
Click to expand...
Click to collapse
Flashing not working. Same problem: Need switch to edify scripting...
works best for me when I odin a .tar package of CWR, I've had a lot of problems flashing a clockwork. zip.. sounds like you guys need an edify-only 3.x version of it, I think in the ComRom thread there's a link to one and if I remember correctly the one I'm using is "CWM3-Voodoo" (no voodoo kernels or anything required however)
tapatalked from my stock VZ Fascinate
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!
I have a Verizon Note 2 running 4.4.2.
I successfully rooted it without unlocking the bootloader or flashing a custom recovery, everything was stock. Everything worked fine after and I was able to use root-requiring apps.
Then, after attempting to flash custom recovery, since the bootloader was locked, I am now stuck at the screen that says: "System software not authorized by Verizon Wireless has been found on your phone..."
I am able to enter recovery (the stock recovery) as well as go into download mode. Normally this wouldn't be a problem as I could just flash stock through Odin in download mode.
However, ever since the soft-brick Odin won't recognize my phone (the yellow COM square does not come up), which is strange because Odin recognized my Note 2 in download mode before this happened.
And even stranger is the fact that it is not a driver issue, as when I plug in my Note 2 in download mode I get a message from Windows 7 saying that the serial gadget device driver was found and installed successfully (and the phone also shows up in Device Manager in control panel as fully installed while in download mode.
Yet Odin won't recognize it.
I have spent days searching for an answer and have yet to come across an issue identical to mine (everyone seems to be able to just flash stock through Odin to fix this particular soft-brick, but Odin is not recognizing my device), so I finally decided to post here.
Any suggestions at all are welcome as I am somewhat desperate at this point. I'd just like to get it back to stock (or flash a custom rom, it does not matter as long as I can get the phone to work).
I would like to point out that I have already tried the following:
- Different USB ports
- Using different USB cables
- Uninstalling and reinstalling the drivers
- Wipe/Factory Reset in stock recovery
From what I can see, my only options are to either somehow get Odin to recognize the phone (suggestions welcome here), or somehow flash stock through the default recovery (if possible, again, any input is appreciated).
William31 said:
I have a Verizon Note 2 running 4.4.2.
I successfully rooted it without unlocking the bootloader or flashing a custom recovery, everything was stock. Everything worked fine after and I was able to use root-requiring apps.
Then, after attempting to flash custom recovery, since the bootloader was locked, I am now stuck at the screen that says: "System software not authorized by Verizon Wireless has been found on your phone..."
I am able to enter recovery (the stock recovery) as well as go into download mode. Normally this wouldn't be a problem as I could just flash stock through Odin in download mode.
However, ever since the soft-brick Odin won't recognize my phone (the yellow COM square does not come up), which is strange because Odin recognized my Note 2 in download mode before this happened.
And even stranger is the fact that it is not a driver issue, as when I plug in my Note 2 in download mode I get a message from Windows 7 saying that the serial gadget device driver was found and installed successfully (and the phone also shows up in Device Manager in control panel as fully installed while in download mode.
Yet Odin won't recognize it.
I have spent days searching for an answer and have yet to come across an issue identical to mine (everyone seems to be able to just flash stock through Odin to fix this particular soft-brick, but Odin is not recognizing my device), so I finally decided to post here.
Any suggestions at all are welcome as I am somewhat desperate at this point. I'd just like to get it back to stock (or flash a custom rom, it does not matter as long as I can get the phone to work).
I would like to point out that I have already tried the following:
- Different USB ports
- Using different USB cables
- Uninstalling and reinstalling the drivers
- Wipe/Factory Reset in stock recovery
From what I can see, my only options are to either somehow get Odin to recognize the phone (suggestions welcome here), or somehow flash stock through the default recovery (if possible, again, any input is appreciated).
Click to expand...
Click to collapse
Wow... I'm stumped too as to why Odin won't recognize the phone. What method did you use to try to flash the custom recovery and what recovery did you flash? (You probably know now, but just in case.... if you can get the phone restored to stock 4.4.2 again... then you can't flash a standard custom recovery onto the phone because of the bootloader being locked down. You can use the modified TWRP called Safestrap recovery if you root again... and can only flash 4.4.2 touchwiz roms with stock 4.4.2 kernel after you get rooted again).
When you rooted, all I can think of is that something may have corrupted the drivers somehow and that's now conflicting with ODIN. With the phone in download mode... have have you went into the PC's Device Manager and tried to delete/reinstall any Samsung related drivers, (make sure to look for hidden drivers.... click scan for hardware changes after deleting them and the computer should reinstall the correct drivers). Also... have you made sure no other conflicting programs (like Kies) are running in the background?
You might try to do a system restore to an earlier point on your PC where ODIN recognized the phone to see if that would work.
If ODIN version 3.07 isn't recognizing the phone, you could try a newer version of ODIN. Here's some links to other ODIN versions that you might try: Download link for ODIN 3.09 ; Download link for ODIN 3.10.0. ~~With the newer ODIN versions, they have replaced the "PDA" slot with "AP"--so the .tar firmware file goes into AP in the newer ODIN. ****(For reference--Here's the XDA Thread where XDA recognized contributor -CALIBAN666- posted these links to newer ODIN versions. Hit the thanks button for him ****
---------------
If you can't get the restore to work with ODIN, you could try Samsung Kies to see if it can fix the device...
Where to download Kies -- http://www.samsung.com/us/kies/
Emergency Firmware Recovery using Kies 3 -- http://www.samsung.com/us/support/faq/FAQ00059169/81100
I hope that some of this info helps and that you can get it fixed.
Good luck!
mattnmag said:
Wow... I'm stumped too as to why Odin won't recognize the phone. What method did you use to try to flash the custom recovery and what recovery did you flash? (You probably know now, but just in case.... if you can get the phone restored to stock 4.4.2 again... then you can't flash a standard custom recovery onto the phone because of the bootloader being locked down. You can use the modified TWRP called Safestrap recovery if you root again... and can only flash 4.4.2 touchwiz roms with stock 4.4.2 kernel after you get rooted again).
When you rooted, all I can think of is that something may have corrupted the drivers somehow and that's now conflicting with ODIN. With the phone in download mode... have have you went into the PC's Device Manager and tried to delete/reinstall any Samsung related drivers, (make sure to look for hidden drivers.... click scan for hardware changes after deleting them and the computer should reinstall the correct drivers). Also... have you made sure no other conflicting programs (like Kies) are running in the background?
You might try to do a system restore to an earlier point on your PC where ODIN recognized the phone to see if that would work.
If ODIN version 3.07 isn't recognizing the phone, you could try a newer version of ODIN. Here's some links to other ODIN versions that you might try: Download link for ODIN 3.09 ; Download link for ODIN 3.10.0. ~~With the newer ODIN versions, they have replaced the "PDA" slot with "AP"--so the .tar firmware file goes into AP in the newer ODIN. ****(For reference--Here's the XDA Thread where XDA recognized contributor -CALIBAN666- posted these links to newer ODIN versions. Hit the thanks button for him ****
---------------
If you can't get the restore to work with ODIN, you could try Samsung Kies to see if it can fix the device...
Where to download Kies -- http://www.samsung.com/us/kies/
Emergency Firmware Recovery using Kies 3 -- http://www.samsung.com/us/support/faq/FAQ00059169/81100
I hope that some of this info helps and that you can get it fixed.
Good luck!
Click to expand...
Click to collapse
So I tried recovering with Kies and it just kept throwing errors at me, then finally I just closed it and, am not quite sure why, but went into Odin and it worked! Apparently trying to recover with Kies somehow fixed the Odin issue and I was able to flash stock through Odin. Thanks so much!
You mentioned there was a way to flash a safestrap recovery and then flash touchwiz roms? Do you by chance have instructions on how I could do this, or links to this information...?
William31 said:
So I tried recovering with Kies and it just kept throwing errors at me, then finally I just closed it and, am not quite sure why, but went into Odin and it worked! Apparently trying to recover with Kies somehow fixed the Odin issue and I was able to flash stock through Odin. Thanks so much!
You mentioned there was a way to flash a safestrap recovery and then flash touchwiz roms? Do you by chance have instructions on how I could do this, or links to this information...?
Click to expand...
Click to collapse
Cool. Glad you got it fixed.
As you know, you can root with GhettoRoot from this thread: http://forum.xda-developers.com/showthread.php?p=57238246
Then can install Safestrap from this thread: http://forum.xda-developers.com/showthread.php?p=51616723
I've never used Safestrap because I can use regular custom recoveries like CWM and TWRP. I'm still on a 4.1.2 unlocked bootloader and currently running TrentsKKRom, Build #2...which is 4.4.2 based with stock kernel, so I think it would work with Safestrap.
I'd recommend reading through the Safestrap thread thoroughly and asking questions there to make sure you get everything installed correctly. I've read that with Safestrap, you need to make a backup of your Stock ROM first and save it somewhere safe, like to your computer and on your external sd card...so you can easily restore it if needed. (I'd also make a backup of the ESF in Safestrap if it lets you, then save it somewhere safe).
After you are rooted with Safestrap, you'll have to flash custom ROM's over the stock slot in Safestrap, as the other slots apparently don't work. Again, you're limited to only using Touchwiz ROM's with the stock kernel because of the bootloader still being locked.
Check out TrentsKKRom and Alliance build 30 . (I personally like Trent's build 2 best with the S5 clean theme). I've also found Trent's ROM to be really smooth without UI lagging, the Bluetooth works good with no stuttering, and it pairs well with my Sony Smartwatch 3. (Edit: If you do try Trent's ROM, you may need to install a couple apps.... Chainfire's Supersu app to control your root permissions (at least I needed to), and the FolderMount app to fix a KitKat internal storage mounting issue).
Have fun!!
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.