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
Related
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.
I can boot with volume up and get to the recovery screen. I am combing threads and doing all I can now. Any help is greatly appreciated. Downloading the SDK on slow work internet now and attempting to get all files I think I might need as we speak.
give members more details [what did u flash etc], so they can help u.
No, if you have recovery mode available nothing is lost.
Just download a ROM you like, and try flashing it. If it doesn't work, try formatting and then flashing again.
I flashed one click stock and I saw that SYSTEM failed while it was running. Now I get no boot but I can get to the stock recovery.
How do I get a rom onto the phone in its current state?
when I boot with the vol up / power combination I get a small menu for reboot bootloader, reboot, recovery or power off. If I select recovery I get the triangle icon with the ! and then after a minute or so I can get to what looks like a very small clockwork menu with: reboot system now, apply update from /sdcard, wipe data/factory reset or wipe cache partition. I have tried to apply a rom I had on in the list but it failed verification and the list is only partital it does not let me go all the way down.
In recovery you can still use adb to transfer files to the device.
Code:
adb push update.zip /sdcard
I am having trouble getting adb to work. I am following these instructions but something seems to be wonky?
http://androidadvices.com/how-to-install-set-up-and-use-adb-for-android-devices/#.UAWbt7Sm_Nk
can you point me in a better direction to get adb access
I just noticed at the bottom of my screen in slightly greyed out copy it reads: FASTBOOT STATUS - FAILINVALID COMMAND
magicwands said:
I flashed one click stock and I saw that SYSTEM failed while it was running. Now I get no boot but I can get to the stock recovery.
How do I get a rom onto the phone in its current state?
when I boot with the vol up / power combination I get a small menu for reboot bootloader, reboot, recovery or power off. If I select recovery I get the triangle icon with the ! and then after a minute or so I can get to what looks like a very small clockwork menu with: reboot system now, apply update from /sdcard, wipe data/factory reset or wipe cache partition. I have tried to apply a rom I had on in the list but it failed verification and the list is only partital it does not let me go all the way down.
Click to expand...
Click to collapse
That small menu as you called it is fastboot.
That recovery is stock recovery.
Connect to phone to computer and use fastboot to flash a custom recovery. Boot into said recovery. Mount usb storage. Transfer rom over to phone. factory reset/format system and flash new rom.
If you don't know how set up and use fastboot. Look it up.
I got the bootloader unlocked and TWRP installed but whenever I try to flash a rom I get the error message " E:error in /tmp/sideload/package.zip (status 7)
Any thoughts?
magicwands said:
I got the bootloader unlocked and TWRP installed but whenever I try to flash a rom I get the error message " E:error in /tmp/sideload/package.zip (status 7)
Any thoughts?
Click to expand...
Click to collapse
Do a full wipe, re-download the rom ( make sure its the correct rom for your device) and try again.
If it still fails. Flash the official stock images and make sure that at least works
I am fully wiped but I am going through the process again just to be sure, all I have on the device right now is TWRP its unlocked and boots into TWRP recovery fine. But everytime I flash, I have tried 3 roms and one was the NS4G_IMM76d_deodexed it hits me with the same error as before: e:error in /tmp/sideload/package.zip (status 7)
I am searching frantically for a fix, any help is appreciated.
magicwands said:
I am fully wiped but I am going through the process again just to be sure, all I have on the device right now is TWRP its unlocked and boots into TWRP recovery fine. But everytime I flash, I have tried 3 roms and one was the NS4G_IMM76d_deodexed it hits me with the same error as before: e:error in /tmp/sideload/package.zip (status 7)
I am searching frantically for a fix, any help is appreciated.
Click to expand...
Click to collapse
Download the following files:
7-Zip from http://www.7-zip.org
https://dl.google.com/dl/android/aosp/sojus-imm76d-factory-10660f4c.tgz
http://android.kcomputerzone.com/stock/sojus-imm76d-factory_windows-scripts.zip
http://android.kcomputerzone.com/extras/crespo-drivers.zip (just in case you need them)
Install 7-Zip
Extract sojus-imm76d from sojus-imm76d-factory-10660f4c.tgz (You will need to go in multiple levels deep to get to folder) to your desktop.
Extract contents of sojus-imm76d-factory_windows-scripts.zip to the sojus-imm76d on your the desktop.
With phone in bootloader mode run flash-all.cmd in the sojus-imm76d folder.
If all worked it should be boot and be working.
That should restore yours to default firmware all using fastboot. Hope this helps.
This site (http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/) got me up and running with TWRP then I been having issues flashing roms, I am able to get a Peter Alfonso stock rom to boot but then if I try to flash I get the same error. I was able to ODIN the stock 4.0.4 but nothing seems willing to flash via clockwork or TWRP.
Ok just to bring some closure to this, thanks for all the help. My problem with the status 7 error was that I was using the wrong clockwork recovery. It was bundled in a one click root for Nexus Galaxy and Nexus S, the Root worked great but the recovery was the incorrect version. In any event I am now 100% functional. Thanks to all that helped out.
magicwands said:
Ok just to bring some closure to this, thanks for all the help. My problem with the status 7 error was that I was using the wrong clockwork recovery. It was bundled in a one click root for Nexus Galaxy and Nexus S, the Root worked great but the recovery was the incorrect version. In any event I am now 100% functional. Thanks to all that helped out.
Click to expand...
Click to collapse
That is the problem with One click root/unroot. I know the simplicity is awesome but the end user is learning nothing. Doing it the ol' fashion way teaches the user how to use SDK, ADB, and other important simple things. I always say use the guide and do it yourself. Problems happen and instead of having to start a new thread you can trouble shoot it yourself. :good:
So, last night I was updating my phone to a newer version of Paranoid Android. In the process, I accidentally flashed TWRP over my preexisting flash of CWM and, in both being unfamiliar with TWRP, and an apparent conflict between the flashes, it soft bricked my phone. Most of my day has been spent recovering my phone.
I was able to restore my phone to stock using the excellent guide found here: http://forum.xda-developers.com/showthread.php?t=1840030
Then spent the next couple of hours installing updates, at which point I was eager to reflash my custom roms, etc.
Problem is, I can't get the phone to boot into CWM (or TWRP). Just goes to stock recovery. I've tried flashing the lazy way in ROM Manager, and in Odin (reads PASS), but it always goes to stock recovery. For that matter, in trying to flash with ROM Manager, it reads "an error occurred while trying to flash..."
Ideas?
TheBuzzard said:
So, last night I was updating my phone to a newer version of Paranoid Android. In the process, I accidentally flashed TWRP over my preexisting flash of CWM and, in both being unfamiliar with TWRP, and an apparent conflict between the flashes, it soft bricked my phone. Most of my day has been spent recovering my phone.
I was able to restore my phone to stock using the excellent guide found here: http://forum.xda-developers.com/showthread.php?t=1840030
Then spent the next couple of hours installing updates, at which point I was eager to reflash my custom roms, etc.
Problem is, I can't get the phone to boot into CWM (or TWRP). Just goes to stock recovery. I've tried flashing the lazy way in ROM Manager, and in Odin (reads PASS), but it always goes to stock recovery. For that matter, in trying to flash with ROM Manager, it reads "an error occurred while trying to flash..."
Ideas?
Click to expand...
Click to collapse
Do you want CWM or TWRP? If TWRP, you could just download GooManager from the Play Store and press Menu/Install Open Recovery Script.
For flashing either via Odin, deselect auto reboot in Odin then flash the recovery tar. Once its passed, pull the battery and boot directly into your custom recovery.
Sent from my SCH-I535 using Tapatalk 4 Beta
SlimSnoopOS said:
Do you want CWM or TWRP? If TWRP, you could just download GooManager from the Play Store and press Menu/Install Open Recovery Script.
For flashing either via Odin, deselect auto reboot in Odin then flash the recovery tar. Once its passed, pull the battery and boot directly into your custom recovery.
Sent from my SCH-I535 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thanks for the advice, but I got it working.
Tried Odin one more time, and it's booting into CWM properly now. Not sure why it didn't "take" the other 2-3 times that I followed the identical procedure, but it appears that my problems are fixed now.
I've searched and found a few different solutions for each of my problems. However, nothing has resolved the issue.
I tried to flash CM 11.0 to my Galaxy Tab 2 (GT-P3110) and now I can't get anywhere but my CWM Recovery screen.
When I try to install the ROM, I get a "Status 7" error. I've attempted the steps found here but they have not worked.
So, I decided to just recovery what I had before - easy enough. But then when I attempt to recover, I get an error of "MD5 Mismatch".
I've looked up ways to resolve this issue, but I can't complete the steps for 2 reasons. Firstly, I can't get to my File Explorer because my tablet won't completely boot. Secondly, my laptop has stopped recognizing my tablet for some reason. So, I'm unable to edit the file from there.
Lastly, when I just try to reboot system, I get an error explaining that I "may" have lost root access. If I select to "fix" this, it does nothing - just reboots back to recovery. If I choose no, same thing.
I've cleared dalvik, cleared cache partition, cleared data/factory reset, and formatted system - nothing makes a difference.
Any help is greatly appreciated. Thanks everyone.
IS there kitkat update for tab 2. Please inform about That}.
chandru andriod said:
IS there kitkat update for tab 2. Please inform about That}.
Click to expand...
Click to collapse
I believe so, yes.
@ohhello update your recovery. your recovery needs to be up-to-date to flash KitKat Roms. Link in my signature, all my latest recoverys can handle KitKat-Roms.
Android-Andi said:
@ohhello update your recovery. your recovery needs to be up-to-date to flash KitKat Roms. Link in my signature, all my latest recoverys can handle KitKat-Roms.
Click to expand...
Click to collapse
Okay - easy enough.
If I'm unable to get to ROM Manager, is there a way to update my Recovery within Recovery Mode?
I've zipped the .img file for the update.
Should I just install the zip from Recovery Mode?
THANKS!
download a flashable zip for your device from my thread and flash it in recovery. after that reboot the recovery to see the new recovery.
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