Just used Oden to stock, TB and rom manager to successfully flash Cog. 3.04
(firebird2 kernel, JK4 modem and then speed mod kernel (for voodoo control app)), first flash. The first thing that was done (from the stock rom) after installing rom mgr. and flashing cwm was to back up current rom. I think I botched that part as when I access "manage and restore backups" in cwm, all I get is a black screen. Or did I? I did find in the "cwm folder" on the internal sdcard, a "recovery-update.zip"
Is "recovery-update.zip", my back up of the stock rom made using cwm?
This was a complete by the book wipe and no other backups of roms were done.
Cog. 3.04 was then flashed, TB used to restore apps, all running smooth. O'joy I find gotta have it "voodoo control app." Flash "firebird2 kernel" then "Jk4 modem" using cwm, silly me finds "I9000 speedmod", flash on top of firebird2 kernel using cwm., was that an Oops? Every thing working great, love the setup.
Now when I try to reboot into recovery using cwm I get an E:failed to verify whole-file signature, E:signature verification failed, I then have to reboot system now. I can successfully reboot into cwm through the power button/recovery and the volume/power button method.
1. Is this an indicative problem to the "I9000 speedmod.zip" kernel that is preventing me from rebooting into recovery from cwm?
2. In cwm, under "install zip from sdcard" > "toggle signature verification" > "choose zip from sd card" > I find "speedmod.zip".
Could it be a signature verification problem within the i9000 speedmod.zip preventing the reboot into recovery from inside rom mgr.?
I have since installed from the market, Astro, SMS backup and voodoo toggle.
This noob wants to be sure to have done this correctly, If not I'll go back to ground zero, and do it again until I do it right. I just need a little guidance on which direction to proceed. My brain hurts and is stuck in a boot loop, lol.
Total time flashing from the leaked version of 2.2 was 40 min, two weeks on and off were spent reading, setting up drivers backing up and getting familiar with phone and process.
Related
I have just rooted my phone recently on my Droid X using Z4root and it worked fine. Then I backed up my phone using Titanium Backup, which also worked fine also. Then I installed ROM Manager and then flashed ClockworkMod Recovery within ROM Manager. When I click on Backup Current ROM the phone reboots fully without going into recovery. So I open ROM Manager and click "Manage and Restore Backups" and there is no file there.
I tried clicking "Reboot into Recovery" to see if I could select it there and the phone just reboots back to android without going into recovery. So then I turned off my phone and held down the home+power to go into recovery which works. When I'm there it doesn't have an option to backup my ROM. I don't want to flash this ROM I want to try until I can backup my current stock ROM, in case something goes wrong.
When at the blue recovery screen I notice at the bottom in yellow a message is displayed "E: Can't open /cache/recovery/command. Wondering if this is my issue. I also notice in recovery it gives me an option to "apply sdcard:update.zip" but I don't see an update.zip on my sd card, so I'm not sure if I should select this before being able to backup my stock ROM. I'm afraid to flash the ROM before knowing this current problem. Can anyone help me with this issue? I am new to the whole root and ROM hacks, but have been researching in depth and taking all precautions so I'm trying hard not to brick my phone. Thanx in advance.
First off update.zip is just an update.zip package. Could be anything thats an update and can be flashed. Yeah...not sure why rom manager doesnt work for you but all the same your better off doing it from recovery anyway. You can make backups in recovery you don't need rom manager just use rom manager to manage your backups it will see them no matter what! It will allow you to rename them as well so they are easily identifiable also. If your rom manager works youll be able to name the backup before hand! If you ask me rom manager doesnt update the roms fast enough anyway they are usually like 2 days behind! Good tool either way but not so good at replacing roms as recovery does a better job. I have never had one problem using recovery but I've had a problem every time I try to flash a rom using rom manager!
Okay I figured out that the ClockworkMod Recovery must not have flashed properly or something bc I was just at the dev's site and the picture of the recovery is different than mine bc it's green and has many more options to choose from. Plus it says ClockworkMod Recovery on the recovery screen and mine doesn't. It's blue and says android recovery at the top. When I open the ROM Manager it says that I have the ClockworkMod Recovery but I don't. I even tried reflashing but it didn't work either. So how do I get the ClockworkMod Recovery to flash correctly?
I am having same problem but I just use bootstaper and it works fine
I tried downloading the bootstrap from the creator of ClockworkMod Recovery but the link seems to be broken. What bootstrap are u using?
I found the bootstrap for the Droid X on the market and that fixed the issue I was having. Wish I would have known from all the other posts/articles I read that it was a requirement for the Droid X to have the bootstrap to run recovery
Ok, so I have been trying to help a friend flash a recovery (preferably CWM) but no matter what files I use, using Terminal, ROM manager, or even Flash Image GUI, I still just boot into normal 3e recovery. PLS HELP!
Hit reinstall.packages
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
you must have the modded 3e recovery. its a must. once you have that, you can install cwm through rom manager. select galaxy s i9000 and once its done, reboot into modded 3e and select reinstall packages, do that until you see clockworkmod. then you can reboot and flash whatever you want from rom manager or clockworkmod. if you flash a custom rom you prolly wont see 3e recovery again, especially if you are using a voodoo lagfix rom which must have cwm.
I've tried hitting reinstall packages but it says E: Failed to locate whole-file signature. Or something of the sort
Search, oh what a nice option it is.
http://forum.xda-developers.com/showthread.php?t=1144924
I had my phone rooted and and a few mods installed for the past while. I didn't like them so I went back to the origional Rogers ROM. I hated it, so I wanted to try out ICS for my phone. I can't get it to install CWM though. I've tried re-rooting it (and it completed, as far as I can tell). It should still be unlocked, again, as far as I can tell.
I've followed everything on http://forum.xda-developers.com/showpost.php?p=25526643&postcount=2
I've downloaded and isntalled Superuser repeatedly
and I've downloaded and isntalled CWM repeatedly.
when I try to "fix permissions" in CWM I get An error occurred while attempting to run privaleged commands!, but at the bottom it says complete.
Then when I try to restart in recovery mode I get
E:failed to verify whole-file signature
E:signature verification failed.
and then it shows that it's restarted in Samsung's recovery mode.
any ideas?
mac_angel said:
I had my phone rooted and and a few mods installed for the past while. I didn't like them so I went back to the origional Rogers ROM. I hated it, so I wanted to try out ICS for my phone. I can't get it to install CWM though. I've tried re-rooting it (and it completed, as far as I can tell). It should still be unlocked, again, as far as I can tell.
I've followed everything on http://forum.xda-developers.com/showpost.php?p=25526643&postcount=2
I've downloaded and isntalled Superuser repeatedly
and I've downloaded and isntalled CWM repeatedly.
when I try to "fix permissions" in CWM I get An error occurred while attempting to run privaleged commands!, but at the bottom it says complete.
Then when I try to restart in recovery mode I get
E:failed to verify whole-file signature
E:signature verification failed.
and then it shows that it's restarted in Samsung's recovery mode.
any ideas?
Click to expand...
Click to collapse
A couple of clarifications.
1. Rooting a phone only gives you access to root files (the OS). The superuse.apk, the su files.
2. Stock kernel do not give you the ability to flash insecure zip files. An insecure custom kernel is needed for this.
3. You don't need root to flash an insecure file in a modded cwm.
You are trying to flash an unofficial firmware or insecure *.zip with a secure stock kernel - not going to happen. There are two different ideas altogether.
To have the insecure cwm you are looking for, you need to flash the kernel on that post while in download mode.
Put your phone in DL mode. Flash the kernel then boot into modded cwm recovery
thanks for getting back to me. I had to step out to get some things before the stores closed.
doesn't Entropy's 4.4.2012 kernel do that though?
mac_angel said:
thanks for getting back to me. I had to step out to get some things before the stores closed.
doesn't Entropy's 4.4.2012 kernel do that though?
Click to expand...
Click to collapse
Yes it does. But you don't have it installed.
that's the SGH_I997 Entropy 4_4_2012-One-Click-Heimdall file that runs in Java? I've downloaded that and ran in repeatedly. Keeps saying completed and reboots the phone no problem.
I'm about to reboot in Samsungs recovery mode to try to flash the CWM-Superuser Busybox Root UCLB3 file. I'll wait for your response first.
mac_angel said:
that's the SGH_I997 Entropy 4_4_2012-One-Click-Heimdall file that runs in Java? I've downloaded that and ran in repeatedly. Keeps saying completed and reboots the phone no problem.
I'm about to reboot in Samsungs recovery mode to try to flash the CWM-Superuser Busybox Root UCLB3 file. I'll wait for your response first.
Click to expand...
Click to collapse
I don't remember if mac will flash the kernel correctly. If you check the CPU info and it shows entropy kernel and not the stock kernel, you should be able to boot into cwm recovery with the three finger technique. It will be a red recovery.
If cwm is blue, entropy is not installed.
If you are looking to install a different firmware, there is no need to root. Just flash the firmware you want in cwm. Chances are, the unofficial firmware is already rooted.
mac_angel was a nick I created about 18 years ago when I worked for Apple Canada. I haven't worked with a mac in God knows how long. My last IT job was IBM, lol.
Anyway, I'm not sure what happened. I went to restart in the Samsung's recovery mode again to flash with that file I mentioned and it booted in CWR. I cleared all the dev cache and everything, and flashed the ROM I had already moved over. Phone is still restarting, but it looks like I might be good. I didn't do anything from the time I first posted to now though, lol. I was about to try to flash that file and it worked. Only thing I can think of is that before I was always trying to restart the phone in CWR mode by selecting it to reboot in that mode from the application instead of the three finger salute (oh, wait, that's M$).
You got it going?
yes, thank you. Not sure if you can do it, but the thread can be closed now. Thanks for getting back to me, as well as your other great posts.
Have a Verizon Samsung Galaxy Note II (SCH-i605). Took the latest OTA update to VRUEMJ9. Have since rooted and installed SafeStrap and was happily running N3BULA ROM, when I decided to explore a bit and tried to flash Alliance ROM. Now I'm stuck on the Samsung boot screen and can go no further. I am able to access Android system recovery, but when I try to 'apply update from external storage' I get 'E:signature verication failed' message. Tried to flash to stock via Odin, but unsuccessful. Shows Added in Odin but nothing happens when I select the .pit file or the .tar file. This is a work issued phone, so any help to get up and running would be greatly appreciated!
Brantosapien said:
Have a Verizon Samsung Galaxy Note II (SCH-i605). Took the latest OTA update to VRUEMJ9. Have since rooted and installed SafeStrap and was happily running N3BULA ROM, when I decided to explore a bit and tried to flash Alliance ROM. Now I'm stuck on the Samsung boot screen and can go no further. I am able to access Android system recovery, but when I try to 'apply update from external storage' I get 'E:signature verication failed' message. Tried to flash to stock via Odin, but unsuccessful. Shows Added in Odin but nothing happens when I select the .pit file or the .tar file. This is a work issued phone, so any help to get up and running would be greatly appreciated!
Click to expand...
Click to collapse
Have you performed a "wipe data" option from the recovery after flashing the alliance ROM (it wipes your user data)?
Because I just visited the alliance ROM thread ( http://forum.xda-developers.com/showthread.php?t=2032447 and in the install instructions its mentioned so.
Better take a little time and properly read the install instructions during flashing..
Sent from my GT-I9070 using Tapatalk
dagger said:
Have you performed a "wipe data" option from the recovery after flashing the alliance ROM (it wipes your user data)?
Because I just visited the alliance ROM thread ( http://forum.xda-developers.com/showthread.php?t=2032447 and in the install instructions its mentioned so.
Better take a little time and properly read the install instructions during flashing..
Sent from my GT-I9070 using Tapatalk
Click to expand...
Click to collapse
I never had that option. I've flashed numerous ROMS before and am pretty meticulous when it comes to following instructions. It appeared to have a custom flash script which allowed me to pick what I did and didn't want to install. I tried to keep it mostly stock and when it completed, it automatically rebooted (didn't give me an option to 'wipe data') and now leaves me stuck on the Samsung Boot Screen. I was able to flash the .pit file via Odin, but keep getting a 'MD5 hash value is invalid' when I try to flash the .tar file.
Brantosapien said:
I never had that option. I've flashed numerous ROMS before and am pretty meticulous when it comes to following instructions. It appeared to have a custom flash script which allowed me to pick what I did and didn't want to install. I tried to keep it mostly stock and when it completed, it automatically rebooted (didn't give me an option to 'wipe data') and now leaves me stuck on the Samsung Boot Screen. I was able to flash the .pit file via Odin, but keep getting a 'MD5 hash value is invalid' when I try to flash the .tar file.
Click to expand...
Click to collapse
You should enter into recovery and then manually wipe data..
Also if that thing doesnt work, then have a look at this thread which explains how to go back to stock rom..
In addition,
A. Why doesnt Odin work?
Did you unextract the tar and pit from the rar/zip so that odin could recognize the files as suggested in dagger's link in section 1b step 2?
Did you install samsung drivers on your computer properly? You may use this toolkit for that
B. Rescue by CWM
Signature verification failed is caused (I think) by stock samsung recovery's choosiness, if you are sure you downloaded the zip correctly. What zip did you exactly try to flash?
So now, you may want to flash a cwm recovery or a kernel that contains cwm inside. Flashing usually uses adb using fastboot. Search "flashing a recovery image" or "flashing a kernel" where your chosen kernel should have cwm inside. cwm usually does not put out that signature verification error.
Remember:
You can access recovery mode through an app or by pressing a button combo when turning your phone on. Device specific.
Stock samsung recovery can wipe data.
CWM can also wipe data, and is the preferred installation method for most/all custom roms. And it can make a nandroid backup.
If ever you do choose to flash, you'll need the toolkit to install adb/fastboot drivers, but maybe since yours in locked bootloader the adb thing might not work.
Hope this helps
The error message doesn't get any more specific than that.
I have a Samsung Galaxy S Relay 4g, and I followed this guide to root it, using the files provided: http://forum.xda-developers.com/show....php?t=2256821 It seemed to work perfectly.
Then I backed up the factory (4.0.4/touchwiz) rom, used the recovery to wipe user data, cache partition, and dalvik cache, and then tried installing the stock kitkat zip. It got a little way into the process and then stopped, saying "Install aborted". It was able to boot into the stock (4.0.4/touchwiz) rom after that, so I did some googling and tried again with a version of Liquidsmooth specifically for the device. Same problem, except it said "Error 7" this time. I fixed that, tried again, and the "Error 7" message went away, but the "Install aborted" message stayed.
Now whenever I try to start it up, it boots straight into recovery mode. I tried restoring from the backup I made at the beginning, and it says "md5 mismatch". I've considered trying to flash the rom with Odin, but 1) the files aren't md5s/tars? and 2) I'm hesitant to do anything that may damage my phone further.
I've also tried googling around, with a lot of not-quite-helpful results. Any help would be amazing and highly appreciated.
Thanks!
TL;DR phone won't boot out of recovery mode, nor successfully flash any rom.
Usually there is an option to skip a md5 check when flashing from recovery. If you are confident your using a good copy of the rom, just skip the check and install.
croogrog said:
Usually there is an option to skip a md5 check when flashing from recovery. If you are confident your using a good copy of the rom, just skip the check and install.
Click to expand...
Click to collapse
I think I did that, though? The "toggle verification" option, right?
if your still stuck,
I would try using odin to flash the recovery again,
then flash a "recent" recovery, (I'm using the cwm recovery 6.0.3.7)
and finally try to flash the rom (possibly including the modem and bootloader)
Good luck