Related
I just got my Galaxy S and want to update the ROM but dont know the exact process. Various Roms say to apply update.zip first but I keep getting e:signature verification failed so I cant proceed.
I tried update.zip for 'ClockworkMod' and it gave the same error.
Any help appreciated.
Robert
redesignni said:
I just got my Galaxy S and want to update the ROM but dont know the exact process. Various Roms say to apply update.zip first but I keep getting e:signature verification failed so I cant proceed.
I tried update.zip for 'ClockworkMod' and it gave the same error.
Any help appreciated.
Robert
Click to expand...
Click to collapse
You need to flash a kernel with clockwork mod recovery such as :
http://forum.xda-developers.com/showthread.php?t=822756
Flash with Odin and put the kernel in the PDA section. Once flashed you will have clockwork mod recovery. The reason you can't apply roms is because you have Recovery 3e which won't apply unsigned .zips.
When booted into clockwork mod just select apply .zip from sd card and choose the ROM you want to install and then reboot.
Simple really
I sure hope you have checked first if your 3-button combo works. Otherwise you soon will be figuring out how to unbrick your Galaxy....
pwhooftman said:
I sure hope you have checked first if your 3-button combo works. Otherwise you soon will be figuring out how to unbrick your Galaxy....
Click to expand...
Click to collapse
Yep, forgot to mention this. VITAL thing that you must to first before messing with your Galaxy.
Please check that you can get into download mode before doing anything!
yeah the volume up, home and power works... thats what has been getting me into the boot menu...
Cheers for the answer, Ill try that now
Ok so I'm new to flashing a ROM, and Im having a little problem with ROM Manager. Ive been trying to make a backup of my current ROM prior to flashing to a new ROM. However when I choose the option to backup current ROM it shows me the name of the backup and then reboots my device (Samsung Captivate) into recovery mode. Not really sure what it wants me to do there so I choose to reboot the device, I then check to see if it made the backup and nothing??? Im not sure what it is that Im doing wrong but Im sure I must be missing a step. The phone is rooted, running 2.2 other than that nothing else has been moded. If any of you can help me I would appreciate it, I just dont want to move forward with flashing a ROM before Ive backed up the current ROM. I have made a backup of all apps and data using Titanium.
Xanaki said:
Ok so I'm new to flashing a ROM, and Im having a little problem with ROM Manager. Ive been trying to make a backup of my current ROM prior to flashing to a new ROM. However when I choose the option to backup current ROM it shows me the name of the backup and then reboots my device (Samsung Captivate) into recovery mode. Not really sure what it wants me to do there so I choose to reboot the device, I then check to see if it made the backup and nothing??? Im not sure what it is that Im doing wrong but Im sure I must be missing a step. The phone is rooted, running 2.2 other than that nothing else has been moded. If any of you can help me I would appreciate it, I just dont want to move forward with flashing a ROM before Ive backed up the current ROM. I have made a backup of all apps and data using Titanium.
Click to expand...
Click to collapse
When it goes into recovery, is it the ClockWorkMod recovery menu? Green text? If it isn't getting there you need to install it from ROM manager first or just install it off an update.zip file that is floating around XDA and other sites. Once that is setup, you can run the backup through ROM Manager. It should boot into a recovery mode and then start doing a lot of writing of files to your new backup directory.
Post back if you are still having problems.
I did select the option for flashing ClockWorkMod recovery and chose the Captivate as my device. It did say that it sucessfully downloaded the file and Im assuming that it meant it installed it. And to answer your question I think I can safely say that no its not clockwork recovery when it reboots as it does say at the top of the screen "Android Recovery" so Im pretty sure that ClockWork is not installed. But I will look for that update.zip file and try to install it that way...
Xanaki said:
I did select the option for flashing ClockWorkMod recovery and chose the Captivate as my device. It did say that it sucessfully downloaded the file and Im assuming that it meant it installed it. And to answer your question I think I can safely say that no its not clockwork recovery when it reboots as it does say at the top of the screen "Android Recovery" so Im pretty sure that ClockWork is not installed. But I will look for that update.zip file and try to install it that way...
Click to expand...
Click to collapse
I'm sorry, you are looking for recovery-update.zip. I would try to run the ROM Manager install again and see what happens. I haven't had to play with the Android Recovery in quite some time but if the recovery-update.zip file is in the root of your sd card, you should be able to install it through the Android recovery. I'll keep looking. If I can find the file on my phone, i'll post it. Good luck.
If this is your first time booting into CWM recovery it will go to the base recovery first. Then you need to "reinstall packages". That will replace the recovery file with the CWM recovery file and return to the main menu. Then choose reintall packages one more time and it should bring you to CWM recovery instead of the base one. From then on it should bring you directly to the CWM recovery.
As for the backup it's done from CWM recovery. So once you get thru the steps above you will see backup and restore options on the recovery menu and you can go thru that process.
There may be some help in here: http://forum.xda-developers.com/showthread.php?t=734163
First try to flash it again through ROM Manager.
mxracer101 said:
If this is your first time booting into CWM recovery it will go to the base recovery first. Then you need to "reinstall packages". That will replace the recovery file with the CWM recovery file and return to the main menu. Then choose reintall packages one more time and it should bring you to CWM recovery instead of the base one. From then on it should bring you directly to the CWM recovery.
As for the backup it's done from CWM recovery. So once you get thru the steps above you will see backup and restore options on the recovery menu and you can go thru that process.
Click to expand...
Click to collapse
DUH...I thought there was another step. Thanks mxracer. Give that a go and see if you get what you are looking for.
Thanks!! Trying that now
Ok still having a problem, I followed the instructions just as posted but this is what I get:
-- Install from sdcard --
Finding update package...
Opening update package...
Verifying update package
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Ok so what do I do? Im thinking I need to find that recovery-update.zip you were talking about?
Xanaki said:
Ok still having a problem, I followed the instructions just as posted but this is what I get:
-- Install from sdcard --
Finding update package...
Opening update package...
Verifying update package
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Ok so what do I do? Im thinking I need to find that recovery-update.zip you were talking about?
Click to expand...
Click to collapse
That update.zip should have been placed there by ROM Manager. Possibly try uninstalling & reinstalling ROM manager. Else, that update.zip should be somewhere. I'd grab the one off my phone but I'm not entirely sure which one it is. My ROM already had CWM with it. I'll try to look for a correct update.zip but I'm at work so I'm not going through XDA all day.
trekie86 said:
That update.zip should have been placed there by ROM Manager. Possibly try uninstalling & reinstalling ROM manager. Else, that update.zip should be somewhere. I'd grab the one off my phone but I'm not entirely sure which one it is. My ROM already had CWM with it. I'll try to look for a correct update.zip but I'm at work so I'm not going through XDA all day.
Click to expand...
Click to collapse
you missed the part where he said he was running 2.2?
2 words:
3e recovery
trekie86 said:
DUH...I thought there was another step. Thanks mxracer. Give that a go and see if you get what you are looking for.
Click to expand...
Click to collapse
Pirateghost said:
you missed the part where he said he was running 2.2?
2 words:
3e recovery
Click to expand...
Click to collapse
Not sure what it is that you're saying I need to do, what is 3e recovery?
Xanaki said:
Not sure what it is that you're saying I need to do, what is 3e recovery?
Click to expand...
Click to collapse
this will explain and provide a fix for you....
http://forum.xda-developers.com/showthread.php?t=909213
Pirateghost said:
you missed the part where he said he was running 2.2?
2 words:
3e recovery
Click to expand...
Click to collapse
You're right, I did miss that. Haven't had to do anything with 3e recovery before. Xanaki, are you on Rogers with their official 2.2 or the leaked AT&T 2.2?
Pirateghost said:
you missed the part where he said he was running 2.2?
2 words:
3e recovery
Click to expand...
Click to collapse
I missed it too. The above post regarding 3e recovery is what you need to do, one of the phones I have I need to do the same process after flashing back to stock. Sorry for the confusion.
Been having a similar issue when it takes you to stock recovery, I hold down both volume buttons and power until I see AT&T let go of power it usually takes me to clockwork recovery menu, I then select whatever I want to do backup, recover, or install from sd.
I don't know why it started doing that but that's what I found works. Hope it helps.
trekie86 said:
You're right, I did miss that. Haven't had to do anything with 3e recovery before. Xanaki, are you on Rogers with their official 2.2 or the leaked AT&T 2.2?
Click to expand...
Click to collapse
Im on the leaked AT&T version of 2.2 not Rogers. I haven't had the chance yet to try the recovery method mentioned but I plan on doing so today, I will update as to if this works or not. Also I did read somewhere that flashing a new Kernal might resolve this issue, I do have SGS Kernal Flasher but I dont have another Kernal to flash to...
Tried SuperOneClick using both methods and it didn't work. Any suggestions?
I also would like to know this before I update.
Sent from my Nexus One
I couldn't get it to work either... had to revert back to 2.2 and root using Super One Click from there to restore back to my CM7 backup.
I would suggest waiting for superoneclick to be updated to support gingerbread.
Yep, that's what I was going to do but was hoping someone had a way beforehand so I could my backups going again
Install the Gingerbread update using a custom recovery, then install this: http://forum.xda-developers.com/showthread.php?t=682828 BEFORE rebooting.
Or if you want to root manually, follow the instructions for rageagainsthecage in my signature.
efrant said:
Install the Gingerbread update using a custom recovery, then install this: http://forum.xda-developers.com/showthread.php?t=682828 BEFORE rebooting.
Or if you want to root manually, follow the instructions for rageagainsthecage in my signature.
Click to expand...
Click to collapse
Tried to root manually with your instructions w/ rageagainstthecage but its not cooperating... Once I run rageagainstthecage, it will exit out of shell, then USB bugging dissapears on the N1 notification bar, and can't get it back without rebooting the N1, also it won't show up in windows device manager until N1 is rebooted...
Did you use this method to root your phone with 2.3.3 or did you flash the update then flash the other update to get root?
Thanks,
How did you revert back to 2.2? What Passimg.zip did you use? Or are you unlocked?
quick_ said:
Tried to root manually with your instructions w/ rageagainstthecage but its not cooperating... Once I run rageagainstthecage, it will exit out of shell, then USB bugging dissapears on the N1 notification bar, and can't get it back without rebooting the N1, also it won't show up in windows device manager until N1 is rebooted...
Did you use this method to root your phone with 2.3.3 or did you flash the update then flash the other update to get root?
Thanks,
Click to expand...
Click to collapse
I flashed the update then flashed then flashed the other file I linked to. If rageagainstthecage doesn't work, try the newer exploit (psneuter).
quick_ said:
Tried to root manually with your instructions w/ rageagainstthecage but its not cooperating... Once I run rageagainstthecage, it will exit out of shell, then USB bugging dissapears on the N1 notification bar, and can't get it back without rebooting the N1, also it won't show up in windows device manager until N1 is rebooted...
Did you use this method to root your phone with 2.3.3 or did you flash the update then flash the other update to get root?
Thanks,
Click to expand...
Click to collapse
This is exactly what's happening for me as well. Manual rageagainstthecage worked perfectly with froyo.
Sent from my Nexus One using XDA App
dnlsmy said:
How did you revert back to 2.2? What Passimg.zip did you use? Or are you unlocked?
Click to expand...
Click to collapse
http://www.mediafire.com/?dxwh5l4b5ygh6nf
No need to unlock the bootloader. Just download the file, rename it to PASSIMG.zip, put it on the root of your SD card and boot into the bootloader. It will scan the file for a minute or so and then ask if you want to flash it. Just hit the up volume button to flash.
I've got what appears to be temp root with rage ($ changes to #), but I can't get the system to mount as rw, which is wierd...
Sent from my Nexus One using XDA App
uansari1 said:
http://www.mediafire.com/?dxwh5l4b5ygh6nf
No need to unlock the bootloader. Just download the file, rename it to PASSIMG.zip, put it on the root of your SD card and boot into the bootloader. It will scan the file for a minute or so and then ask if you want to flash it. Just hit the up volume button to flash.
Click to expand...
Click to collapse
It comes up with the message "Main Version is Older!" "Update Fail!"
My phone is not rooted and on official 2.3.3 flashed through stock recovery via update.zip
EDIT: Used first method, reflashed with passimg.zip (frg33) then updated one by one back to fgr83g, rooted (superoneclick) installed amon_ra, recovery via rom manager, put 2.3.3 gingerbread update on SD as update.zip, also put the su-2.3.6.1-ef-signed.zip on SD.
Flashed 2.3.3 update via amon_ra recovery (had to turn off signature verification), once it reset (not rebooted) back to recovery picked to flash zip, picked su-2.3.6.1-ef-signed.zip, (had to turn off signature verification again), rebooted, and now have root!! Now i can finally restore my apps
Worked great!! Thanks efrant!!!
uansari1 said:
http://www.mediafire.com/?dxwh5l4b5ygh6nf
No need to unlock the bootloader. Just download the file, rename it to PASSIMG.zip, put it on the root of your SD card and boot into the bootloader. It will scan the file for a minute or so and then ask if you want to flash it. Just hit the up volume button to flash.
Click to expand...
Click to collapse
awesome... thanks for the info. this should become a sticky or something for people that are trying to go back and root the phone again. thanks.
uansari1 said:
http://www.mediafire.com/?dxwh5l4b5ygh6nf
No need to unlock the bootloader. Just download the file, rename it to PASSIMG.zip, put it on the root of your SD card and boot into the bootloader. It will scan the file for a minute or so and then ask if you want to flash it. Just hit the up volume button to flash.
Click to expand...
Click to collapse
Will this wipe everything installed on the phone? Thanks.
colins said:
Will this wipe everything installed on the phone? Thanks.
Click to expand...
Click to collapse
It will wipe out everything except your SD card. You will have to reinstall all your apps, settings etc... Backup your apps with titanium backup first, along with a nandroid backup if you want.
http://forum.xda-developers.com/showpost.php?p=11619356&postcount=67
I flashed the su.zip and still have root.
quick_ said:
EDIT: Used first method, reflashed with passimg.zip (frg33) then updated one by one back to fgr83g, rooted (superoneclick) installed amon_ra, recovery via rom manager, put 2.3.3 gingerbread update on SD as update.zip, also put the su-2.3.6.1-ef-signed.zip on SD.
Flashed 2.3.3 update via amon_ra recovery (had to turn off signature verification), once it reset (not rebooted) back to recovery picked to flash zip, picked su-2.3.6.1-ef-signed.zip, (had to turn off signature verification again), rebooted, and now have root!! Now i can finally restore my apps
Worked great!! Thanks efrant!!!
Click to expand...
Click to collapse
How were you able to flash FRG33 on Gingerbread? My HBOOT is 0.35.0017 and I can't seem to flash it without a "Main Version is Older!" error.
dnlsmy said:
How were you able to flash FRG33 on Gingerbread? My HBOOT is 0.35.0017 and I can't seem to flash it without a "Main Version is Older!" error.
Click to expand...
Click to collapse
Did u rename to passimg.Zip and let the bootloader flash it (power+volume down)? I had the new hboot too and it worked fine
Sent from my Nexus One using XDA App
Hello,
I rooted the N1 and used Miui rodriquezstyle rom
When i go 2 bootloader, the Microp version is 0c15 which probably means its an Slcd nexus 1(not sure)
How do i return this to stock rom 2.2?
i have seen many links (including wiki) but im not sure of the correct rom to flash
Can some1 kindly please provide the correct link with the rom to flash, so that i dont brick my new N1?
Thanks
Ramu
What is so urgent? Nuclear war is about to break out from the phone if it's not unrooted ASAP? We have only several minutes left till the Earth blows up?
You can't return to stock 2.2 ROM, since stock 2.2 doesn't support SLCD. You can return to FRG83, which you just need to flash in the custom recovery you currently have. Just turn off the signature checking.
Jack-thanks for the assist there!!
You can return to FRG83, which you just need to flash in the custom recovery you currently have. Just turn off the signature checking.
I did not quite understand what you meant by the above statement!!
I already have the Frg83 rom renamed as Passimg.zip on my Sd card
Do i just boot into recovery by holding Vol down+power and choose "apply update from zip etc?
I really did not understand, what you meant by turning off signature checking
thanks again
He means you flash the rom the same way you did to get the current rom on the phone. Signature check is in the recovery.
Sent from my Xoom using Tapatalk
darkkid85 said:
Jack-thanks for the assist there!!
You can return to FRG83, which you just need to flash in the custom recovery you currently have. Just turn off the signature checking.
I did not quite understand what you meant by the above statement!!
I already have the Frg83 rom renamed as Passimg.zip on my Sd card
Do i just boot into recovery by holding Vol down+power and choose "apply update from zip etc?
I really did not understand, what you meant by turning off signature checking
thanks again
Click to expand...
Click to collapse
if u already have passimg.zip in yr folder-it should automatically rewrite yr rom to the frg83...
nothing to do on yr side...
just copy into yr sd card
press vol down and power...
when it reaches the bootloader screen(the one with the 3 androids at bottom)
it should run by itself
it dont even have to go to the recovery(amon ra/clockwork
Hey everybody,
I just got back my motorola milestone from my provider because it has the ghost hand issue.
Now my problem is the I flashed the GOT back and I tried the original Shols as well with vulnerable recovery and I have the following issue.
I press power and X together, the triangle comes up and when I choose install update.zip the installing is coming and it says install successful but I got the recovery menu back and not the open recovery.
Any ideas? I will re-flash the phone again as soon as I got home but still it's a strange and weird issue. I tried to use ClockWork mod as well, same thing happened.
Thanks in forward!
Phami
Clockwork recovery isn't compatible with Milestone.
Try this recovery: http://forum.xda-developers.com/showthread.php?t=1091787
Eiertschik said:
Clockwork recovery isn't compatible with Milestone.
Try this recovery: http://forum.xda-developers.com/showthread.php?t=1091787
Click to expand...
Click to collapse
Not working....I get the verification failed error message, like I didn't flashed the vulnerable sbf.
SO I reflashed with the RTEU Shols and then the vulnerable flash the one that's working with the 90.78 bootloader
I tried to flash GOT, same error message, it feels like the RSD Tool is just simply wiping the phone but do not flash the OS on my phone.
I thought maybe that's the problem so I tried a different RTEU and that didn't even boot up my phone, so it's doing something...I try to reflash GOT again..if it is not gonna help me then I don't know what to do...I never had this issue before...Never...I'm not a noob, I used a lot of a different ROMs and finally I see we got 2nd boot working my phone doesn't reach the open recovery...loooolllll
HELP ME haha
Update: Tried it, didn't work...
It maybe the problem of that I have Windows 7 64bit on my laptop and it has some issues with RSD Lite before i re-installed the Windows...Force Flash and some other stuff...How can I check that I have GOT on my phone or the original shols? Should be somewhere at "About Phone" section.
Don't flash the OR with RSDLite!
Flashing installs it to the phone's internal memory.
Just copy&paste the 'OpenRecovery' folder and the 'update.zip' to the root of your sd-card.
Erovia said:
Don't flash the OR with RSDLite!
Flashing installs it to the phone's internal memory.
Just copy&paste the 'OpenRecovery' folder and the 'update.zip' to the root of your sd-card.
Click to expand...
Click to collapse
I flashed the OS not the OR, as I stated I'm not a noob with it, I already been thru with almost all the ROMS that's being available on our MileStone but I never faced an issue like that! I don't know where I go wrong I have one idea left maybe that will help me! Thank You tho!
http://android.doshaska.net/rootable - recovery check might be restoring stock recovery.
mrvek said:
http://android.doshaska.net/rootable - recovery check might be restoring stock recovery.
Click to expand...
Click to collapse
Good tip but I tried it.
At the moment I have the stock 2.2.1 on my phone Retail Europe version and it's still messed up. I can't acces the OR, I flashed the RAMDLD 90.78 but no luck...I'm on windows 7 i might try to flash it from my C: drive but still I get the error message at the moment:
"E:EOCD marker occurs after start of EOCD E:signature verification failed"
Kinda strange
therealphami said:
Good tip but I tried it.
At the moment I have the stock 2.2.1 on my phone Retail Europe version and it's still messed up. I can't acces the OR, I flashed the RAMDLD 90.78 but no luck...I'm on windows 7 i might try to flash it from my C: drive but still I get the error message at the moment:
"E:EOCD marker occurs after start of EOCD E:signature verification failed"
Kinda strange
Click to expand...
Click to collapse
Not at all. Vulnerable recovery is the solution. And then remove recovery check from system before it boots to android.
mrvek said:
Not at all. Vulnerable recovery is the solution. And then remove recovery check from system before it boots to android.
Click to expand...
Click to collapse
The problem is, that I don't have that install-recovery.sh in my system/etc/
Should that file dissappear when I first boot the phone after flashing the vulnerable RAM DL?
therealphami said:
The problem is, that I don't have that install-recovery.sh in my system/etc/
Should that file dissappear when I first boot the phone after flashing the vulnerable RAM DL?
Click to expand...
Click to collapse
No. After you flash vuln. recovery you need to boot directly to recovery and remove that file.
mrvek said:
No. After you flash vuln. recovery you need to boot directly to recovery and remove that file.
Click to expand...
Click to collapse
I mean what If I do not remove it right after flashing the v. recovery? That .sh file should be in system/etc or not?
mrvek said:
http://android.doshaska.net/rootable - recovery check might be restoring stock recovery.
Click to expand...
Click to collapse
I could reach my open recovery once I did what I had to but I couldn't delete the .sh file but i was able to install the newest cm 7.2.4...but it stopped working on the motorola logo, i came home now I could do the rteu shols and now I can't reach recovery once again lol...I should have to delete, then "re-install" OR on my SD card but as soon as I turn SD card on the portal and tools coming back again for some unkown reason...goooshhh lol