Related
It says e: signature verification failed. S-off but no Root. Btw doing this from recovery 3e
It means you have a corrupt file. Re-download and try again.
Sent from my HTC Vision using XDA App
Did it..same error
any1?
1010101010
I don't know if ur recovery has this option, but on CWM you can turn the verification process off, if u are sure your file is ok.
I flashed a new kernel too today and i had to try it 3 times in a row until the flashprocess proceeded.
Sorry 4 my english, not a native speaker
it doesn't it's the Recovery from the stock HTC sensation. I dunno how to flash the su.
Flash from Clockwork
EDIT: have you checked the MD5? Should be
a2844ac335a5c1cfdb9bea2fc041b415
Sent from my HTC Vision using XDA App
If u have already S-OFF try to install ClockworkRecovery.
Follow Step 2:
-> http://forum.xda-developers.com/showthread.php?t=1192300
done fixed.
I received an error in cwm also, but after reboot everything worked.
I recieved the same error but I remembered the same thing happening with the update.zip on my old vibrant so .. I installed it twice. When it errors out the first time, select it again and install. Worked for me...
PLEASE HELP!! I have successfully rooted the device and was doing ok after flashing CWmod recovery 6.0.1 through E-Z recovery app and running Liquid Rom. I managed to be dumb enough to flash CWMod version 5.8.4.9 through Rom manager and when I rebooted my phone it got stuck in boot loop. I am able to get into CWMod 5.8.4.9 but I cannot restore my backup anymore. I can also data wipe and install a new rom, but it all just keeps going into bootloop and I cannot get past the samsung custom unlock screen. It first flashed that, then the android man pops up on the next screen like its loading something and then just keeps looping through the process. I did not use ODIN for any of this process and I dont know how to get myself back tothe point where I can reboot. Any help would be tremendously appreciated, because I'm dead stuck and in a panic. Thanks in advance for any assistance.
Happend to me last night...
I made the same mistake... DO NOT download any recoveries from ROM manager. I found out the hard way... So the problem now is your phone is stuck using the recovery you downloaded. I am not sure of a quick way using that recovery if you can revert back but... My solution got me where I needed to be in order to get going again.
I had to use Odin to root to stock ROM. Yes when you wipe it will destroy your data but not your pictures, downloaded files, and other files you put on there. When I re-rooted with stock all my stuff for CM10, gapps, and the kexec CWM was there.
So use this guide...
http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
Section 1!!!!! And follow the steps EXACTLY the way it says to.
This is why i have never liked rom manager...
The best solution for us to flash recoveries is ez recovery free from the market. I would use this going forward once you Odin back to stock
Sent from my SCH-I535 using xda premium
Same **** happened to me.
Odin. I lost my pics and internal memory though...
Sent from my SCH-I535 using Tapatalk 2
I have an att htc one x that has 4.01 and 2.20 software. I was able to successfully root the phone and now I'm trying to install CM10 but it's failing when trying to install.
It says it missing a MD5 File and says theres an error in the SD card/download/ the cm 10 file.
What am I doing wrong? Thank you
Make sure the Rom is for our phone and check the md5 sum it might be a bad download
I've tried redownloading the file several times and I'm still getting the same error message.
I'm downloading CM10 from here http://get.cm/?device=endeavoru
kswannabe said:
I've tried redownloading the file several times and I'm still getting the same error message.
I'm downloading CM10 from here http://get.cm/?device=endeavoru
Click to expand...
Click to collapse
Wrong version, endeavoru is the international (Tegra3) One X. Our phone is code named evita.
Just stick to the Development forum here, to avoid flashing ROMs for the wrong version of the One X:
http://forum.xda-developers.com/forumdisplay.php?f=1726
Thanks for the information.
Was able to successfully flash to CM10 but I'm stuck at the CM10 boot screen. Circle going counter clock wise around. What should I do?
kswannabe said:
Thanks for the information.
Was able to successfully flash to CM10 but I'm stuck at the CM10 boot screen. Circle going counter clock wise around. What should I do?
Click to expand...
Click to collapse
If you flashed an international rom, there's a good possibility you messed something up. Factory reset, wipe /system, and try flashing the correct CM10 rom again.
Ok. I'm trying to do a factory reset from bootloader but whenever I do, it goes to the CM10 boot screen where I was earlier. How can I do a factory reset?
kswannabe said:
Ok. I'm trying to do a factory reset from bootloader but whenever I do, it goes to the CM10 boot screen where I was earlier. How can I do a factory reset?
Click to expand...
Click to collapse
A guy I was working with had the boot screen splash. If you've flashed the correct one, then wipe your caches. if that doesn't work reflash.
kswannabe said:
Ok. I'm trying to do a factory reset from bootloader but whenever I do, it goes to the CM10 boot screen where I was earlier. How can I do a factory reset?
Click to expand...
Click to collapse
Don't do it from bootloader, it can corrupt your sdcard. Do it from recovery.
Go into recovery, wipe cache, dalvik cache, factory reset and system. Then install the CORRECT rom.
Sent from my One X using xda premium
How can I reflash?
Thanks
-edit-
I was able to get back into TWRP. There I tried to do a factory reset but it tells me it failed. And after installing CM10, do I have to go back into bootloader and flash boot.img from the CM10 nightly zip file?
And there goes my stock rom... Factory reset is not working on TWRP and tried system reset thinking it would get rid of CM10 but instead erased my stock rom.
Please help, need a working phone soon..
kswannabe said:
How can I reflash?
Thanks
-edit-
I was able to get back into TWRP. There I tried to do a factory reset but it tells me it failed. And after installing CM10, do I have to go back into bootloader and flash boot.img from the CM10 nightly zip file?
Click to expand...
Click to collapse
There are stickies and tuts around here for this.. but, the reason why it's not working for you is you didn't flash the boot.img first. before you installed the .zip. Also, you'll need the latest gapps for that ROM as well.
Not familiar with the forums around here, so if you could link me some of these stickies or tutorial it would be great.
Have a look here
Sent from my One X using xda premium
timmaaa said:
Have a look here
Sent from my One X using xda premium
Click to expand...
Click to collapse
or here http://forum.xda-developers.com/showthread.php?t=1952076
I have this problem. i went to the thread you posted, loaded TWRP, I've factory reset and what not, but now I'm stuck in TWRP without any real viable options. When I try to reboot to system, it brings me back to TWRP menu.
mfc1288 said:
I have this problem. i went to the thread you posted, loaded TWRP, I've factory reset and what not, but now I'm stuck in TWRP without any real viable options. When I try to reboot to system, it brings me back to TWRP menu.
Click to expand...
Click to collapse
Do you have a rom flashed? If so, wipe both caches and reboot. If that doesn't work, reflash and do a system wipe from TWRP.
Sent from my HTC One XL cellular device over clocked to 1.9Ghz
Rooted SGH-T989D trying to flash CM10
kswannabe said:
How can I reflash?
Thanks
Click to expand...
Click to collapse
hi. i have fallowed all the steps to root my phone from this site. when i go down to how to flash a rom i have some issues.
i am trying to flash CM10. when i go to install on (step 8) i get an errer. my screen says
Updating partition details...
Running boot script...
Finished running boot script.
E:Unable to open zip file.
Error flashing zip /external_sd/cm-10.1-hercu
Updating partition derails...
then it shows the home butten. failed in red than wipe cach/dalvik and reboot system buttons
anyone have any idea what im doing wrong?
Exactly which phone do you have? It looks like it says Hercules in the cm file name you wrote, which I think is a Samsung.
Sent from my Evita
I originally was using TWRP the latest version, and every time I tried to make a backup, it would say error too many open files, data lost found and then error tarring split files... so I tried flashing CWM and when trying to make a backup it said error while making a backup image of /data. I really don't know what to do, as now I'm basically forced to stay on the rom I'm on, and I want to try out something new. Any help?
Bump.
So you are rooted and bootloader is unlocked correct. Are you sure you have the latest twrp. You could get goo manager app and get latest through there by going into settings and flash recovery. Then when in recovery don't select anything extra when you go to backup. Should work fine if your rooted and bootloader is unlocked. Remember if you took Verizon latest ota them your bootloader would be locked again, just putting that out there.
Sent from my SCH-I605 using xda premium
Hi everyone. After 5 months, I decided to come back and try to root my phone again.
First, I'm on JB 4.1.2 with my VZW GS3.
I get to this step in the process.... Step 4 - Rooting Your Device and Unlocking Your Bootloader and every option I choose, tells me that the signature failed and the installation is aborted. Can someone tell me what I did wrong, if it can be fixed, and how?
I was once rooted before, and went back to stock using ODIN in the past. Will that have an effect on it?
When I got to Step 3, I used these instructions: •Flash the VRALEC Bootchain using ODIN v3.07 - My phone shows VRBMB1 - should I have used that boot chain instead? Can I still flash it using ODIN, over what is already there?
I can get my phone to boot normally, but when it boots it just shows custom at the bottom. I haven't bricked it or anything, I'm just concerned I haven't messed up the root process all together.
Thanks for the help...
Did you choose to install the zip in recovery or did you pick a different option? First make sure your zip is good and you didn't get a bad download. You can flash the VRALEC Bootchain whenever, and you must do it before flashing your recovery. If installing your zip isn't working in CWM try installing TWRP and flash the zip on that recovery instead. And no restoring back to stock with Odin won't affect anything.
Sent from my Verizon Samsung Galaxy SIII
joshua5683 said:
Did you choose to install the zip in recovery or did you pick a different option? You can flash the VRALEC Bootchain whenever, and you must do it before flashing your recovery. If installing your zip isn't working in CWM try installing TWRP and flash the zip on that recovery instead. And no restoring back to stock with Odin won't affect anything.
Sent from my Verizon Samsung Galaxy SIII
Click to expand...
Click to collapse
I chose to install the zip in recovery, and I did it after flashing my recovery.
Can I install TWRP using ODIN, right over the CWM installation? Will it hurt anything?
Thanks for your help!!
lou1210 said:
I chose to install the zip in recovery, and I did it after flashing my recovery.
Can I install TWRP using ODIN, right over the CWM installation? Will it hurt anything?
Thanks for your help!!
Click to expand...
Click to collapse
Here's what I did:
1. Booted into ODIN, Flashed VARELC
2. Booted into ODIN again, Flashed Recovery (following ALL directions exactly) Pulled battery, put back in, went back into ODIN
3. Attempted to install the Update -> Download SuperSU + Unlocked Bootloader (showed FIXED in the file name)
4. Got this process: finding update package, opening update package, verifying package, signature verification failed, Installation Aborted.
lou1210 said:
Here's what I did:
1. Booted into ODIN, Flashed VARELC
2. Booted into ODIN again, Flashed Recovery (following ALL directions exactly) Pulled battery, put back in, went back into ODIN
3. Attempted to install the Update -> Download SuperSU + Unlocked Bootloader (showed FIXED in the file name)
4. Got this process: finding update package, opening update package, verifying package, signature verification failed, Installation Aborted.
Click to expand...
Click to collapse
Yeah you're doing everything right I don't know why it's saying that. Try installing with TWRP - you can flash it at anytime and overwrite the old recovery.
Sent from my Verizon Samsung Galaxy SIII
lou1210 said:
Here's what I did:
1. Booted into ODIN, Flashed VARELC
2. Booted into ODIN again, Flashed Recovery (following ALL directions exactly) Pulled battery, put back in, went back into ODIN
3. Attempted to install the Update -> Download SuperSU + Unlocked Bootloader (showed FIXED in the file name)
4. Got this process: finding update package, opening update package, verifying package, signature verification failed, Installation Aborted.
Click to expand...
Click to collapse
Your second and third step are wrong. You need to flash SuperSU in recovery NOT download mode. Download mode handles "tar" files, recovery handles "zips."
Edit: well, the latter half of your second step is wrong, pull battery then boot into recovery mode...home, volume UP, and power
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
Your second and third step are wrong. You need to flash SuperSU in recovery NOT download mode. Download mode handles "tar" files, recovery handles "zips."
Edit: well, the latter half of your second step is wrong, pull battery then boot into recovery mode...home, volume UP, and power
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I'm sorry, I am doing the supers in recovery, not ODIN. I tried both CWM now and TWRP and still have the same exact error messages. Not sure what to do to fix this, but I'm almost ready to try to reverse what I did. I have been wanting to remove the bloatware and now I saw the Carbon ROM that looks pretty cool. If you can get me past this issue, it would be great.
Oh I just noticed you chose update. You have to choose to install in CWM not update. But if it didn't work in TWRP either it sounds like there is something wrong with the zip file. Have you tried redownloading the zip file?
Sent from my Verizon Samsung Galaxy SIII
lou1210 said:
I'm sorry, I am doing the supers in recovery, not ODIN. I tried both CWM now and TWRP and still have the same exact error messages. Not sure what to do to fix this, but I'm almost ready to try to reverse what I did. I have been wanting to remove the bloatware and now I saw the Carbon ROM that looks pretty cool. If you can get me past this issue, it would be great.
Click to expand...
Click to collapse
Here is another interesting thing....
Should I have an install or is Apply Update the same thing. When I boot into recovery, here are my choices:
reboot
apply update from adb
apply update from external storage
wipe data/factory reset
wipe cache
apply update from cache
Do I have the right version of recovery? Does this help any?
Ok. So I decided to download a new recovery file for CWM and this time it worked.
I'm not sure what told me to do it, but I decided to give it a go.
Next question, I remember the root processing being very involved with clearing cache, clearing dalvik cache, etc.
Is there a link to the newest process on how to root exactly and apply new ROMs? I of course will be backing up my existing ROM first.
lou1210 said:
Ok. So I decided to download a new recovery file for CWM and this time it worked.
I'm not sure what told me to do it, but I decided to give it a go.
Next question, I remember the root processing being very involved with clearing cache, clearing dalvik cache, etc.
Is there a link to the newest process on how to root exactly and apply new ROMs? I of course will be backing up my existing ROM first.
Click to expand...
Click to collapse
That's odd someone else had that issue where install wasn't an option. He ended up using TWRP. That clearing thing is for flashing roms. The way you flash every rom is wipe data/factory reset, clear cache, clear dalvik cache, and wipe /system. Make a backup before. I recommend using TWRP cause there have been times in CWM where I would try to restore and I would get an MD5 mismatch error, which I've never gotten on TWRP
Sent from my Verizon Samsung Galaxy SIII
I was thinking of using the carbon ROM. I realized that I didn't install the md5 file extension for cwm using ODIN so I went back and flashed it with one i was able to find, and it worked. I'm ok with using twrp but I haven't been able to find an md5 file for ODIN. Can you give me a link to one? I've only found .tar files and that seems to have been my problem. I might still try to use cwm now that I have my existing stock ROM backed up. Still debating.
On a side note, if I decide to unroot again, since I have not flashed, is there a method for that so I don't lose what I've got?
Sent from my SCH-I535 using Tapatalk 2
lou1210 said:
I was thinking of using the carbon ROM. I realized that I didn't install the md5 file extension for cwm using ODIN so I went back and flashed it with one i was able to find, and it worked. I'm ok with using twrp but I haven't been able to find an md5 file for ODIN. Can you give me a link to one? I've only found .tar files and that seems to have been my problem. I might still try to use cwm now that I have my existing stock ROM backed up. Still debating.
On a side note, if I decide to unroot again, since I have not flashed, is there a method for that so I don't lose what I've got?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
What do you mean you can't find the md5? You can flash the .tar twrp recovery in Odin the same way you flash md5s. And no sorry I don't know of any way to unroot without flashing a factory image. But to get your apps back you can use App Backup and Restore. It won't recover the app data obviously cause you need root for that but it's faster for restoring your apps so you don't have to make a list and download each one off the Play Store.
The file I had used didn't have an md5 filename and I think that's why it failed. I found one and downloaded it so it worked for me after that. Thank you for the unroot info too.
Sent from my SCH-I535 using Tapatalk 2
lou1210 said:
The file I had used didn't have an md5 filename and I think that's why it failed. I found one and downloaded it so it worked for me after that. Thank you for the unroot info too.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
No problem glad you got things working
Sent from my SCH-I535 using xda app-developers app