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
Related
Long time Galaxy Nexus user and I just received my S3 yesterday in the mail!
Of course I couldn't wait to root and unlock it using the very helpful thread RootDebug, EZ-Unlock11 and EZ-Recovery2.2. Via Odin I then flashed the latest CWM 6.0.1.2. At that point I attempted to flash via CWM the Unofficial CM10 JB Rom (http://forum.xda-developers.com/showthread.php?t=1788443). Everything seemed to go just fine but it hung at boot up for 20 minutes. In my haste to play I did not clear the cache which could have been the reason. At that point I pulled the battery and rebooted only to get the infamous message to take my phone to a VZW dealer. After countless trouble free flashes I suppose it was bound to happen at some point.
So via the recovery thread I loaded VRALEC, VRALF, and stock.vwx.root66.tar from the SoftBrick thread to get back up and running. Now however I cannot reflash CWM via Odin. It always fails and on my phone it says "secure check fail : recovery".
I rebooted the phone, computer, and otherwise havent changed anything.
Suggestions to get CWM back on my phone?
Thanks!
J
I did not see that you unlocked the bootloader.
Assuming you performed the Soft Brick guide successfully, what happens when you boot into the rom and download EZ Recovery and flash CWM? You mention flashing CWM only through Odin in your post.
bigmook said:
I did not see that you unlocked the bootloader.
Click to expand...
Click to collapse
Sorry, Bootloader was/is unlocked on this phone
SlimSnoopOS said:
What happens when you boot into the rom and download EZ Recovery and flash CWM?
Click to expand...
Click to collapse
I can boot into CWM 6.0.1.0 via the EZ recovery app
I did get a message i've never seen before upon exit of CWM. "ROM may flash stock recovery on boot. Fix?" I selected Yes - Disable recovery flash
Thanks again for your input!
follow my guide...link in sig!
That message only has bearing if your running the stock rom. Custom rom's will not flash original recovery. Choosing yes or no only matters on stock, will not make any changes on a custom rom
Sent from my SCH-I535 using xda premium
you can always try to flash the new cwm thru ez recovery. Just take the recovery zip and save it to your SD card then go to ex recovery and select custom then select your path to the zip you put on your SD card and flash then reboot and it should have flashed the new cwm without even using Odin. Also make sure you have ez unlock installed and unlocked just to make sure the boot loader is unlocked. Better to be safe than sorry.
Sent from my SCH-I535 using xda app-developers app
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
hey guys,
I flashed the VRALEC bootchain in Odin and i also flashed CWM as well. when i downloaded the SuperSU_bootloader.zip file to my phone i go in to try to flash it in CWM. every time it tells me that the E signature failed and installation aborted. i haved read online about toggling the signature in CWM but i cant locate it when i boot into CWM. can anyone help me?
thanks,
Does your recovery actually say ClockWorkMod? Are you choosing "install from sdcard"?
Sent from my SCH-I535 using xda app-developers app
it says android system recovery and i choose apply update from external storage.
the other choices are
reboot system
apply update from adb
wipe data
wipe cache
apply update from cache
??
Install unknown apps checked in security?
Sent from my SCH-I535 using xda premium
kendeezy said:
it says android system recovery and i choose apply update from external storage.
the other choices are
reboot system
apply update from adb
wipe data
wipe cache
apply update from cache
??
Click to expand...
Click to collapse
You're still on the stock recovery. Uncheck auto-reboot then flash the CWM tar again. Once it says Pass/Reset, unplug, pull the battery, then try booting into recovery again. It should look different now.
SlimSnoopOS said:
You're still on the stock recovery. Uncheck auto-reboot then flash the CWM tar again. Once it says Pass/Reset, unplug, pull the battery, then try booting into recovery again. It should look different now.
Click to expand...
Click to collapse
Did this work ? the "Pass/Reset" Took awhile to show in my experience.
SlimSnoopOS said:
You're still on the stock recovery. Uncheck auto-reboot then flash the CWM tar again. Once it says Pass/Reset, unplug, pull the battery, then try booting into recovery again. It should look different now.
Click to expand...
Click to collapse
It worked. thank you so much! so I currently have a verizon s3. will flashing the Vrbmb1 bootchain bring back the sms text notifications on the lock screen? I would really like to have that back. dont know why verizon got rid of it in the first place
kendeezy said:
It worked. thank you so much! so I currently have a verizon s3. will flashing the Vrbmb1 bootchain bring back the sms text notifications on the lock screen? I would really like to have that back. dont know why verizon got rid of it in the first place
Click to expand...
Click to collapse
No problem. No, flashing the bootchain has absolutely no impact on features within the rom. Honestly, idk how to reintroduce those into your system properly. Maybe there's a mod in the theme & apps section?
Enjoy the rooting world!
Sent from my SCH-I535 using xda app-developers app
kendeezy said:
It worked. thank you so much! so I currently have a verizon s3. will flashing the Vrbmb1 bootchain bring back the sms text notifications on the lock screen? I would really like to have that back. dont know why verizon got rid of it in the first place
Click to expand...
Click to collapse
Most TW roms have the bubbles re-enabled. Hack must be rom specific tho as it mods several rom specific system files. There is an old hack that brings them back but is no longer recommended as it jacks with carrier network side.
I updated to MF1, and it changed my recovery from ClockWork Touch to a much more basic recovery mode (rom manager says CWR and TWRP are both installed). I tried to flash basic clockwork using rom manager and as it reboot I got a message saying "software not authorized" and it would not boot.
I just used ODIN to flash the VRALEC boot chain which allowed the phone to boot. I still seem to have still have MF1. Step 6 here http://forum.xda-developers.com/showthread.php?t=2046439 says to then install the correct boot chain, but i dont see one for MF1 yet.
I then tried ODIN to flash CWR from the the above post with the same results (had to re odin vralec).
1. Should I ODIN the VRBMD3 boot chain in the mean time?
2. How do I get ClockWork Recover for MF1, touch or regular?
blindguyinanorgy said:
I updated to MF1, and it changed my recovery from ClockWork Touch to a much more basic recovery mode (rom manager says CWR and TWRP are both installed). I tried to flash basic clockwork using rom manager and as it reboot I got a message saying "software not authorized" and it would not boot.
I just used ODIN to flash the VRALEC boot chain which allowed the phone to boot. I still seem to have still have MF1. Step 6 here http://forum.xda-developers.com/showthread.php?t=2046439 says to then install the correct boot chain, but i dont see one for MF1 yet.
I then tried ODIN to flash CWR from the the above post with the same results (had to re odin vralec).
1. Should I ODIN the VRBMD3 boot chain in the mean time?
2. How do I get ClockWork Recover for MF1, touch or regular?
Click to expand...
Click to collapse
1. No, you don't have to change the bootchain. Vralec is just an old ics bootchain and should run fine.
2. http://forum.xda-developers.com/showthread.php?t=2096735
Use ez recovery to flash the most recent CWM recovery, touch or non-touch should both work great. Don't use rom manager anymore until it's updated, that's the second report I've seen of it doing that.
Sent from my SCH-I535 using Tapatalk 2
Did you ota to mf1 by any chance? Im pretty sure your boot loader was relocked.
Sent from my SCH-I535 using xda premium
Watoy said:
Did you ota to mf1 by any chance? Im pretty sure your boot loader was relocked.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I did OTA. I can still get into recovery, it is just not CWR.
BadUsername said:
1. No, you don't have to change the bootchain. Vralec is just an old ics bootchain and should run fine.
2. http://forum.xda-developers.com/showthread.php?t=2096735
Use ez recovery to flash the most recent CWM recovery, touch or non-touch should both work great. Don't use rom manager anymore until it's updated, that's the second report I've seen of it doing that.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
EZ-Recovery worked, but i also think i did something different inside CWR. It asked me if I wanted to disable something and this time I said yes.
blindguyinanorgy said:
EZ-Recovery worked, but i also think i did something different inside CWR. It asked me if I wanted to disable something and this time I said yes.
Click to expand...
Click to collapse
Good, if you say no it'll reinstall the stock recovery and you don't want that. The recovery you were seeing is the stock recovery, very basic with the hardly any options.
Sent from my SCH-I535 using Tapatalk 2
People, this is my last ditch effort posting here butI am now at a loss.
I have a Tab 2 10.1 P5110 and have followed a number of guides with no sucess. I have tried to install both TWRP AND CWM but the recovery already installed on the tablet chucks error messages but no explanations that are helpful. Most detailed error message I have is "Failed signature verification."
It appears I can Boot to ODIN and using Odin 3.09 send the tar file OK but when rebooting tablet no recovery has installed. Anothe rheadache is the downloads named GT-P5110_CWM are all seen as virus infected.
Any help would be appreciated here..
Thank you
Well, you could try these methods:
a.) Install TWRP using an app. This requires you to be rooted. First, install the twrp app through the play store. Then select install twrp and choose your model number and twrp version. Grant root access and install. After that, it will ask you to boot to recovery. Press ok. Congrats, you have twrp.
b.) Install through odin. Download Odin, and the tar file of twrp. Uncheck auto reboot in odin. Then flash the twrp tar in odin. After that, reboot to recovery (manually. If you dont, stock recovery will over write twrp. Booting to recovery prevents that and makes twrp permanent)
Press thanks if I helped
Also, the reason why it says signature verification failed is that stock recovery will only allow samsung signed files to install. Twrp and cwm? Out of the question
Cheers
Sent from my espresso3g using XDA Labs
Thank you for your reply. Using your method a, I managed to install twrp 3.0.2.6. I attempted to flash blismallow custom ROM but this failed immediately with the message "updater process ended with error 7". I then tried CM12 but same problem. After more reading I'm thinking could this be because my TWRP version is the new common version and the ROMS I am trying to flash are too old ? Thank you again
Sent from my HTC One_M8 using Tapatalk
OK update.... Downloaded the latest cm13 to test my theory, seems to be booting as I type this so fingers crossed. Thank you for pointing me in the right direction
Sent from my HTC One_M8 using Tapatalk
lisaamybeth said:
OK update.... Downloaded the latest cm13 to test my theory, seems to be booting as I type this so fingers crossed. Thank you for pointing me in the right direction
Click to expand...
Click to collapse
Good to know its working for you. Also if you take a look at andi34.github.io 's twrp section, it says it cant flash roms made prior to 22/03/2016.
Also, don't say thanks, press the thanks button instead it helps a lot
Sent from my espresso3g using XDA Labs
Lightracer said:
Well, you could try these methods:
b.) Install through odin. Download Odin, and the tar file of twrp. Uncheck auto reboot in odin. Then flash the twrp tar in odin. After that, reboot to recovery (manually. If you dont, stock recovery will over write twrp. Booting to recovery prevents that and makes twrp permanent)
Press thanks if I helped
Also, the reason why it says signature verification failed is that stock recovery will only allow samsung signed files to install. Twrp and cwm? Out of the question
Cheers
Sent from my espresso3g using XDA Labs
Click to expand...
Click to collapse
Thanks, this helps me