Related
THIS THREAD IS NO LONGER RELEVANT AS IT IS FOR A DIFFERENT ISSUE FROM THE PAST... IT GOT BROUGHT BACK TO THE TOP. DONT CONFUSE THIS WITH THE 3E RECOVERY "ISSUE"
THE BELOW ISSUE HAS BEEN ADDRESSED BY KOUSH. YOU SHOULD BE ABLE TO FLASH CWR VIA ROM MANAGER LIKE NORMAL NOW. IF YOU STILL HAVE ISSUES, THERE IS A FIX POSTED BELOW, THANKS!
Update from koush:
@clockworkmod Hey all, flashing recoveries through ROM Manager is busted. We hit a bandwidth/CPU quota on Google App engine.
If you are trying to flash Clockwork Recovery for the first time, it appears that a lot of users are having issues over the past 24 hours.
Normally, you would:
download Rom Manager
Click Flash Clockwork Recovery
it will ask for root privelages
you would select the Vibrant as your phone
after it downloaded CWR you would get a successful pop-up....
you could then click on reboot into recovery (and since it was the first time you would go to the stock recovery, click reinstall packages, and THEN you would go to Clockwork Recovery)....
well.... people can't seem to get there now. I am NOT having issues as I already have CWR. However, if you are, please download this file on your phones browser (just so you dont have to mount your phone to your pc.... which you can do if you prefer)
FILE DOWNLOAD HERE: View attachment update.zip
Move this file to the root of your internal memory. If you have any other update.zip file you can just overwrite it, or delete it prior to moving this file over, your choice....
NOW, go back to your stock recovery and press reintall packages.... you should go to CWR, if not, press to reinstall again... still no luck? blasphemy.
With all of that said, I need someone to post that this successfully works (it should, and you really can't lose anything)
I am contacting koush for an explanation of what's wrong....
i will check this out
everytime i boot into recovery and press reinstall packages my just restarts phone and i can't get into clockwork.
You generally have to tell it to reinstall packages twice.
^ that has not been the case for me.. but try it twice if if doesn't work the first time!
Yeah, it may depend on the ROM being run or something, but I've noticed it quite a bit.
yeah, something happened when rom manager updated in the last day where flashing recovery isnt compatable with galaxy s devices anymore. drove me freakin crazy cuz i just dl'ed nero and went to install and couldnt.
thank you again. +10 internets to u.
I started having an issue after flashing eugenes super kernel. I did a.clean install of axura and problem went away.
Powered by Axura
^ the rom would have nothing to do with it.
Koush has fixed this, it was server related.
THE BELOW ISSUE HAS BEEN ADDRESSED BY KOUSH. YOU SHOULD BE ABLE TO FLASH CWR VIA ROM MANAGER LIKE NORMAL NOW (NORMAL STEPS STILL INCLUDED BELOW). I KNEW THIS WOULD BE A QUICK FIX FOR KOUSH!
As of 10mins ago i was having this problem.
But thanks to this post and installing the downloaded update I'm back up!
Rom manager gave me errors when flashing the clockwork recovery
so had to go to the update.zip and i'm now back!
Dont think rom manager in the market has been updated
[i was coming from a odin[ed] JFD stock.
hope this helps someone else!
Thanks... this works for me :\
I flashed to JL4 and had a freaking wifi boot loop and gotta go back to Eugene's does not brick ROM and found out can't install CWM via ROM manager
I don't know if its supposed to fix it, but even after flashing this Im still having issues with ROM manager. Get an error every time I try to update the recovery. Also, I can't remember the last time fix permissions actually worked (eclair maybe?).
Anyone else feel my pain?
This is a fix, and you trying to update the recovery is no different than those who have issues not even using my .zip....
I updated the op with a tweet from koush. He has a fix on his site too (might as well download it from here though?
I downloaded the new update, still can't get into clock work. When I hit reinstall packages it says ... E: error /cache/update.zip
(bad)
Installation aborted
Sent from my SGH-T959 using XDA App
^^^ I'm having the same problem as well right now.
reinstall off market and it works
I thought I was sunk until an hour of searching found this post. Thank you all so much!
I have after upgrade to K6 the error messeage:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
I've try the update.zip from the 1st post,
reinstalled via market
update und select the Vibrant modell
everytime the same...
the phone is rooted via SuperOneClickv1.5.5-ShortFuse
Any help ?
None of this works because none of it addresses the real problem ,3E signature. Way to much trouble to go thru.
^ This thread was created when the Clockwork servers were down... it has absolutely nothing to do with 3e recovery... as that didnt even exist when this thread was created... hopefully others are not confused now that it was brought back to the top.
I didn't update it yet, because the thread was dead.
And to be fair the OP did have this:
THE BELOW ISSUE HAS BEEN ADDRESSED BY KOUSH. YOU SHOULD BE ABLE TO FLASH CWR VIA ROM MANAGER LIKE NORMAL NOW. IF YOU STILL HAVE ISSUES, THERE IS A FIX POSTED BELOW, THANKS!
Click to expand...
Click to collapse
post no longer relevant
If you want to update this, My modified cwm thread has the RED clockwork odin package.
adrynalyne said:
If you want to update this, My modified cwm thread has the RED clockwork odin package.
Click to expand...
Click to collapse
i think omj is going to change his op on af...ill copy that over when he does
When I get in Odin and select CWMRecovery_DJ05_DL09.tar.md5, it fails.
I did not touch any settings in Odin, just clicked PDA and selected that file.
Edit: Redownloaded that file and got it to work. I am now having an issue when applying update.zip... it starts but then comes up with an exclamation point inside of a triangle and the little Android guy... phone reboots fine.
Did you get this solved? Check out the thread at AF I had the same problem
worked like a charm..thanks!
SoCalSpecialist said:
worked like a charm..thanks!
Click to expand...
Click to collapse
ok so i havent been able to find a full answer..but does this leave the device in DI01 or 05 or 09?
just by looking at the files it seems as if it goes from 05 to 09 but once in about phone>build number it reads : DI01
so im just looking for a little clarification here..just rooted my Facinate minutes ago so im still stuck in the whole mindset of the Incredible.
I tried this. Have EA28. Not sure how. Didn't install. Saw install screen on phone last night and hit cancel.
Anyway, Ran Odin, CWMRecovery_DJ05_DL09.tar.md5, reboot, blue text, apply sdcard:update.zip, switched to red text, install zip from sd card, choose zip from sd card, su-2.3.6.1+busybox1.19.zip, choose zip from sd card, DJ05_DL09_kernel.zip (plain kernel due to dl09), ran titanium backup, could not acquire root priv.
Startup screen has sound, but not animation anymore. Installed superuser and it shows titanium backup under "allow". When I run TB, I get the error screen and below in another small screen says, "Titanium Backup has been granted superuser permissions". But can't get anywhere to backup apps. Says Root Access: Failed.
ideas?
Another thing that confused me was the red cwm says voodoo lagfix recovery v2.5.1.x. I thought you weren't supposed to use any voodoo for DL30? Not that I've made it that far due to titanium backup issue, but....
Can anyone confirm whether or not this to sure does or doesn't work with ea28? My wife updated he phone and now she wants it rooted.
Edit this does work for EA28. Everything went smoothly. Thanks nitsuj.
Sent from my SCH-I500 using XDA App
mdisaac said:
When I get in Odin and select CWMRecovery_DJ05_DL09.tar.md5, it fails.
I did not touch any settings in Odin, just clicked PDA and selected that file.
Edit: Redownloaded that file and got it to work. I am now having an issue when applying update.zip... it starts but then comes up with an exclamation point inside of a triangle and the little Android guy... phone reboots fine.
Click to expand...
Click to collapse
I also got stuck at the same screen. what did you do to resolve it????
Here is the link to my guide for rooting with a MAC. I do not have a PC and used these steps to successfully root my phone. After completing last step in guide and getting blue cwm on your phone, DL new red cwm and install
http://forum.xda-developers.com/showthread.php?t=967641
Sent from my SCH-I500 using XDA Premium App
EA28 going to DL09?
Hello..
I am just getting around to rooting my fascinate now. I have EA28. From the instructions, it appears you are going back to DL09. Is that correct? What is the significance of that? Should I care?
Thanks in advance!
This thread is old and should be deprecated. The directions still work, but you need to use the Odin package of ClockworkMod in this thread (it's the very first item linked) instead of the md5 file (DL05_DJ09) above.
However, if you're going custom the thing you should *really* do is Odin in one of the full-Froyo packages. This will include both root and recovery.
s44 said:
This thread is old and should be deprecated. The directions still work, but you need to use the Odin package of ClockworkMod in this thread (it's the very first item linked) instead of the md5 file (DL05_DJ09) above.
However, if you're going custom the thing you should *really* do is Odin in one of the full-Froyo packages. This will include both root and recovery.
Click to expand...
Click to collapse
Thanks S44. My goal is to go froyo, but I need to be rooted first in order to do that.
I have been reading all the threads but many of them are very long. The DL30 thread is over 50 pages long.
So should I:
1) follow the instructions in this thread but use the new ClockworkMod then
2) update to froyo.
What is the most current thread for updating to froyo on the fascinate while after I am rooted?
Appreciate it.
TheTinRam said:
Thanks S44. My goal is to go froyo, but I need to be rooted first in order to do that.
Click to expand...
Click to collapse
Actually, no you don't. Download mode is magic. You *do* need to be rooted to back up apps with Titanium, if you want to do that. In that case, follow the directions above (with the new recovery). Then back up your user apps + app data.
Whether or not you do this, you should move to Froyo with a full-Odin package. Download the ROM you want (either Nameless, Super Clean, or whatever) in zip form to your SD card. Follow the directions here (under "Most Thorough Method of Fixing Every Problem You Might Have") using the first two files here and the recovery I mentioned in my previous post. Yes, this is sort of overkill, but better to avoid stuff like corrupted dbdata from the beginning and not have to fix it later.
You might want to wait a day or so because it looks like jt is finally fixing up Clockwork.
EDIT: I read almost all of the 52 pages of the DL30 thread to realize that DL30 is out of date . I guess Its going to be EB01 or Superclean. Do you know if Superclean has the audio out via USB working for the docks?
I have some questions in regards to picking ROMs:
I am a little confused in where to find the latest versions. For example in the "most thorough me..." thread, there is a link to super clean version form 3/30/2011 yet wiki has super clean from last year. Where can I look at all the ROMs and descriptions?
Which froyo ROM would you recommend? I love Google's stock froyo, but I also want to use the fascinate's USB audio out on the car and desktop dock. I also would like to wifi tether.
Thanks again!
This post had a link to download ODIN but it was removed. Could you please provide that link again. It also had a link to "Samsung Drivers", don't I need that too?
I am going to take a shot at following the ""Most Thorough Method..." steps tomorrow morning and install superclean on my Facinate. Quick Q: In step one, it simply says to ODIN EB01. I can just do this without being rooted?
Also, you said jt is fixing up clockwork. What do you mean by this, what exactly does not work?
I know these are noob questions, but I am just starting out with this.
Thanks
Driver links are here. Odin is here.
Yes, download mode lets you Odin in complete firmware packages without root.
Most people are using Super Clean, so that has the most support (and themes), but there are some odd issues floating around with it. My guess is that a lot of those issues have to do with not cleaning up in the super-thorough way I'm suggesting, and with the permissions bug after flashing a theme (below). There's also navendrob's EC10-based "Nameless" ROM, and ahmgsk's DL30-based "TrulyFascinating" ROM. Nameless is good but he's about to drop a version 4 with a lot of fixes, so you might wait a day or so for that. TrulyFascinating seemed to be pretty good (heavily stability-tested), but he hasn't updated it in a while (busy with more recent Epic leaks, I guess). You might try running it with one of the state-of-the-art EC10 Voodoo kernels.
There are a couple of Clockwork bugs, but the one causing the most current problems is that the old one couldn't fix permissions properly. This causes issues after making a change to the /system after the initial ROM flash, generally when you flash a theme on top of it. The new one I linked above *can* fix permissions, but still requires you to manually mount /dbdata beforehand (actually, go to the "mounts and storage" submenu and make sure /system /dbdata and /data are all mounted -- that is, the option referring to them says "unmount", which will happen when they're mounted -- before you go to the "advanced" submenu and run the fix permissions script). The new new one coming soon will just fix it without a problem, and do other stuff too.
Once again thanks. I have everything I need....or so I thought.
I restored my phone to factory, loaded the drivers, fired up ODIN and added the PDA and PIT. I hit start.... nothing happens. "All threads complete, succeed 0 / failed 0"
Looks like I am missing something. Do I need to somehow tell ODIN where the phone is? I don't see a way to do that.
PS in step 4 its states "ODIN the CWM Recovery package ROM from this post". Does CWM bin file go into PDA or phone in ODIN?
I one again apologize for my noobiness.
The Clockwork step comes after you do the full package and boot with that.
Make sure you have Odin open *before* you connect the phone in download mode.
I have rooted my Vibrant using ROM Manager/Flash CWM Recovery. (I'm running 2.2, Kernel 2.6.32.9, Build FROYO.UVKA6.) I used this method because no matter what folder on the external or internal sd card I could not use the 'reinstall packages' option on the reboot screen. Now, I'm trying to place the Bionx or Nero ROMs on my phone, but can't get anything to install no matter what I do.
I don't think I anything wrong with the root because I kept getting the same 'E:signature verification failed Installation aborted' message everyone else seems to be getting. I'm wondering if Samsung/T-Mo didn't put anything in to prevent rooting and adding new ROMs.
I have rebooted my phone multiple times and have not gotten any results. Along with ROM Manager, I have Busybox installed.
Please feel free to ask questions for more details. I'm a noob to rooting, so I definitely allow for the fact that I might have screwed something up and will need to start over.
PN
PrimeNemesis said:
I have rooted my Vibrant using ROM Manager/Flash CWM Recovery. (I'm running 2.2, Kernel 2.6.32.9, Build FROYO.UVKA6.) I used this method because no matter what folder on the external or internal sd card I could not use the 'reinstall packages' option on the reboot screen. Now, I'm trying to place the Bionx or Nero ROMs on my phone, but can't get anything to install no matter what I do.
I don't think I anything wrong with the root because I kept getting the same 'E:signature verification failed Installation aborted' message everyone else seems to be getting. I'm wondering if Samsung/T-Mo didn't put anything in to prevent rooting and adding new ROMs.
I have rebooted my phone multiple times and have not gotten any results. Along with ROM Manager, I have Busybox installed.
Please feel free to ask questions for more details. I'm a noob to rooting, so I definitely allow for the fact that I might have screwed something up and will need to start over.
PN
Click to expand...
Click to collapse
This is because you are now on 2.2. Samsung patched the exploit from 2.1 that allowed cwm recovery to be flashed. The best thing I can tell you to do since you have root would be to either
A) ODIN down to 2.1 ROM then root again, then install rom manager and from there you can install cwm recovery OR
B) Use this method I posted based on Supercurios voodoo kernels found here:
http://forums.t-mobile.com/t5/Samsung-Vibrant/on-steps-to-flash-Bionix-V-1-2/m-p/720803#M5807 (look for the answer marked solution - and because you have root skip ONLY that part and download the proper supercurio's zip not the tar).
Supercurio's vibrant kernels found here:
http://forum.xda-developers.com/showthread.php?t=870480
Do this before you try anything else, this is your quickest and least painful solution:
http://forum.xda-developers.com/showthread.php?t=833423
Then:
When you boot into recovery and hit Reinstall Packages, the phone might reboot back into recovery, Reinstall Packages again and it will take you to the mod recovery, no more sig. verification.
Congrats!
Thanks.....
roumenjr and mavsfan.
I was able to get the root done. I took roumenjr's suggestion and it worked once I figured out that I was placing the ROMs in the wrong folder.
Now running Bionix Obsidian v2.
oooops..............
Alright, I have some weird things going on in my galaxy tab. I think its bricked, but if it is, its definitely only soft bricked.
Figured I'd post a video showing stuff as I cant really explain it. It shows up in my windows, so i can access inside it, but i have no idea what to do, it shows up in Kies, too
I'm wanting to hopefully make it usable, and if not usable AT LEAST get rid of clockwork mod recovery so I can return it!
So how do i fix my tab?
(note i was following the samsunggalaxytabhacks unrooting guide when I did this, I cant link b/c new
7510, btw
did you flash anything prior to this happening? I ask as I used the wrong kernel one time, one that wasn't for TW and when I rebooted it did the exact same thing... Did you make a backup?
Try to d/l one of the custom roms, since kies can see it, place the zip on sdcard and follow the OP to install it.
yeah im pretty sure i used the 3g model/non touchwiz kernal and this happened! i cleared m device, thinking it would fix it i guess i lost my backup!
go to roms section on 10.1 android development, and look for the correct kernel, transfer to sdcard via kies and go to recovery and reflash kernel for the TW. Or just d/l Tasks/Phantoms rom Paris and do the same, follow the OP to a T, that should fix it.
which one would be the right one?
I would use
http://forum.xda-developers.com/showthread.php?t=1284355
reload
There is a very good walkthough on putting your 7510 back to stock (first step I would suggest). This walk through gives you all the files you need. I have tested this (files include tested pit files, rom files, etc..)
Hope this helps...
http://p7510.teamovercome.net/?page_id=18
I rooted my S3, changed one file, and am now stuck in the startup screen. I've looked on the forums but I'd like to confirm what my recovery options are.
(1) Since I have no backup*, can I recover from a factory recovery for my model and still keep some of my data, apps and customizations?
It's a N American SIII (Rogers Wireless Samsung SGH-I747M). I can boot successfully into both Odin and CWM Recovery (Clockwork 5.5). BusyBox installed.
*I only did one thing:
renamed framework-res.apk to framework-res.apk2 to test permissions. Errors and crash ensued, then I restarted and here I am.
That apk file is part of a fix which is circulating that corrects a bug in the North American models' battery reporting, which requires replacing the apk with a slightly modified version. I thought trying a file rename was a safe small test, prior to backing up. The name "framework" should have tipped me off probably.
(2) Is factory recovery my best option? I would love to get in and just name the file back. But I can't get in.
(3) Was some automatic backup made that I overlooked? Rooting and the learning curve took so many steps I can't remember myself.
(4) Can I just restore the /system directory perhaps? Or some other advanced or custom restore?
Yep, relative noob here. Hope my question is placed correctly and I haven't missed another post with the answers I need, if not pls advise.
CWM Recovery Flash Zip - Not able to find zip on SD
Some progress here...
Since I think the problem is that I renamed framework-res.apk to framework-res.apk2, and since I had a backup of the original, I found and applied the following:
[GUIDE] How to make a cwm recovery flashable zip
Specifically:
Stuck my saved framework-res.apk into the archive in the correct folder (system/framework)
Renamed from sample.zip to update.zip
Copied update.zip to the root of my micro SD (went to buy one since I didn't have a working one)
Since the Guide didn't specify, I assume that flashing requires booting into CWM Recovery (in my case Clockwork 5.5) and using one of the "install zip from sdcard" options there. But it couldn't find the file. Here are my attempt outcomes:
- apply /sdcard/update.zip:
E: Can't open /sdcard/update.zip
(no such file or directory)
Click to expand...
Click to collapse
- choose zip from sdcard:
This just shows me the directory structure inside my phone
So how can I flash from a zip on the (external) SD card? I can't connect via USB except maybe with Odin, so I don't think I can put anything on my device.
No luck
Well, attempted the stock restore from Epic and still have a soft bricked phone.
According to the thread, everyone else is reporting success with Epic's version 4, but it's not working for me. Maybe I'm tired after 48 hours of this and I've missed something or am trying something that cannot work. No idea what's wrong.
I even resigned to losing everything (no backup) and starting over. Didn't think I'd have a permanent brick though.
Here is what everybody is raving about. CWM Recovery on all SGS3 LTE Variants
Will try again, just in case.
Any Luck?
I have done something similar...
I've been trying to find the stock boot from Rogers for the last 5 hours.
I can get into recovery mode and the download screen, but that's as far as I can get.
If you figure it out PLEASE let me know!
same boat
i just bricked my Rogers S3 with apparently a wrong ROM.
can't even get into recovery, totally bricked!
Were you able to find any solution?
Gave up and swapped hardware
I wasn't able to fix it. I was stuck between three useless boot options:
Regular boot - splash screen only and a vibration every few minutes
ODIN - showing that I had flashed the ROM 3 times
CWM - Clockworkmod's custom flash install, replacing the stock one
(Search the forums for the key combinations to get into these.)
I took it back to the store and they kindly replaced it. Glad they didn't know the key combinations. When they told me they needed an hour "to look at it" I thought I'd come back to a finger wag and a flat denial. That was a tough hour.
Make a backup, people; actually, I'm completely sure that a backup is enough. I'm still green at this.
snoops609 said:
I've been trying to find the stock boot from Rogers for the last 5 hours.
Click to expand...
Click to collapse
I understand that the Rogers Galaxy SIII stock recovery isn't out anywhere. If someone is aware of one, please post a link.
Revived my s3! I flashed the att boot img and that has fixed it. Of course my Odin count is up to 25.
And yes I'm sending this from my s3.
If anyone is still in need I still have the files I flashed with. Just shoot me a pm.
Details pls
snoops609 said:
Revived my s3! I flashed the att boot img and that has fixed it. Of course my Odin count is up to 25.
And yes I'm sending this from my s3.
If anyone is still in need I still have the files I flashed with. Just shoot me a pm.
Click to expand...
Click to collapse
Snoops, do you have a Rogers phone? Just trying to understand what you mean by "att boot img". Lol on the Odin count, I got up to 3 and thought I was badass.
Yes, I'd be interested in the files for future use, especially if you're on Rogers and have the LTE version of the Galaxy S3. Model SGH-I747M.
snoops609 said:
Revived my s3! I flashed the att boot img and that has fixed it. Of course my Odin count is up to 25.
And yes I'm sending this from my s3.
If anyone is still in need I still have the files I flashed with. Just shoot me a pm.
Click to expand...
Click to collapse
plese bro help me out...im stuck in the same hole..i just installed some font changer software and m:y phone just rebooted ....