First off, I apologize if I missed a thread that already talked about this. I tried to search for one, but I couldn't find one that actually helped me.
Ok, so I rooted my phone and unlocked the bootloader with Causal. Then I used GooManager to install TWRP and it is the latest version.
From there, I booted into recovery and did the following:
1) Did a backup to my external SD card
2) Factory Reset/wipe cache and Dalvik cache
3) Install ROM
I have tried both Carbon ROM v1.8 and Cyanogenmod 10.1.2. I have downloaded them on my computer, made sure my connection was good, matched up my MD5 sums, and I know that they are for my Verizon Samsung Galaxy S3 (d2vzw).
Once I thought the ROM would almost be installed, it would tell me it failed and tell me that there was a failure with executing binary updater. So from there I tried to use my Nandroid backup to restore my phone back to it's previous state. But when that was almost done, It gave me a failure as well. Unfortunately, I'm not even sure what the error actually was. So I used Odin to flash it back and blah blah blah.
So does anyone has any idea what I could be doing wrong? Or does anyone have any tips?
This worked for me.
http://forum.xda-developers.com/showthread.php?p=30386309
http://forum.xda-developers.com/showthread.php?p=33701313
Sent from my SCH-I535 using Tapatalk 2
eXPilce said:
This worked for me.
http://forum.xda-developers.com/showthread.php?p=30386309
http://forum.xda-developers.com/showthread.php?p=33701313
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thank you, but I already know how to flash it back to stock and everything. I just have an issue with getting my roms to actually flash and to have backups that will actually restore instead of handing out errors left and right.
I had the same type of issue. When the new ROM didn't work, trying to revert didn't flash. Read that this would reset back to STOCK and retried the new ROM flash.
1st link specified to follow EXACTLY. I messed-up one step. But once I got it right. All became great to go.
I thought as you have, just go with it for the fix.
Sent from my SCH-I535 using Tapatalk 2
Related
Hi, I was using Paul Burtons ICS port and I made a backup of my Prime rom . However when I booted back to CWM and restored the NAND backup it says succesful yet when I reboot, the screen stays black after the transformer splashscreen/logo.. I tried erasing all data and factory reset and searched and checked the original thread... I can however go back to the ics port and successfully boot up to it... any help would be greatly appreciated.. thank you XDA.
goodness ya noob.. you shouldn't have flashed that ics port.. it was extremely experimental. Anyways seeing that you tried everything I would have, Im sorry to say that i can't help but I applaud you for at least searching and checking the original thread. LOL.
Sent from my GT-I9100 using Tapatalk
Thank you for trying, I just hope someone knowledgable saves my day... I really need it..
good news i done the same, i had to completly wipe everything, reflash the rom, im using kkrad 1.4.2 and then advance restore and restore data, job done
Sent from my HTC Desire using XDA App
wipe /syste /data /cache... basically everything in CWM possible, then re-flash the Prime or whatever you want
I did the same thing as op. But when I try restoring I get an error saying .android_secure.img is missing. Any ideas?
mafo5000 said:
I did the same thing as op. But when I try restoring I get an error saying .android_secure.img is missing. Any ideas?
Click to expand...
Click to collapse
Maybe a fresh install instead of a restore?
SiNJiN76 said:
Maybe a fresh install instead of a restore?
Click to expand...
Click to collapse
Im back at stock and i still cant restore. Its the .android_secure.img. its missing from my sd card
i had the same problem i did the wipes in cwm and then restored and got a black screen as you describe.
then i grabbed superwipe from revolution rom(i dnt kno if its neccessary but it worked) from black screen i boot into cwm ran superwipe loaded my rom which is revolver right from the rom flashable zip as a new install. then rebooted and back into cwm then restored my backup. not sure whats goin on or why it worked it may be overkill but i got back to my backup.
if you need better explaination just ask
So i would use super wipe lite or the normal one?
lhy1224 said:
So i would use super wipe lite or the normal one?
Click to expand...
Click to collapse
Use Super wipe lite if you want to keep SD card contents, but try the methods listed above before trying the latter .
Sent from my GT-I9100 using Tapatalk
Thank you to everyone ! It seems like i had to wipe everything and flash a clean install instead of my CWM backup. Thank you XDA community, you're the best !
Np, thank the others who really helped you
Sent from my GT-I9100 using Tapatalk
I am having trouble, and since I cant post on the page where this should be asked. (this is my first post) I am asking here hoping that somebody will look...
I have rooted my verizon S3 and it works great... I am however trying to install a CM10 Rom on my device. I have followed the instructions and get all the way to selecting the zip on the sdcard. it finds it, it opens it and after about 20 seconds it gives me a status 7 error and says error in XXXXXX\XXXXX .zip
I have done all the steps perfectly and have formatted and wiped it twice trying this... I even have my backup in place...
I have tried 3 or 4 different cm10 roms and they all give me the same error... What am i over looking?
Thanks
I think you need to flash a CWM/kexec hybrid recovery.
Download the app EZ Recovery and flash the hybrid CWM 6.0.1.0
Sent from my SCH-I535 using Tapatalk 2
Well if he made the nooby mistake to flash cm10 with a non kexec recovery ..i think he should abandon his hopes of installing cm10 considerong the lost IMEI issue
VERIZON GALAXY S 3
DROID3R said:
Well if he made the nooby mistake to flash cm10 with a non kexec recovery ..i think he should abandon his hopes of installing cm10 considerong the lost IMEI issue
VERIZON GALAXY S 3
Click to expand...
Click to collapse
That us not the issue... I can get into the CWM recovery just fine.. when I choose the install zip from sdcad and choose the rom it will go through finding the package, then opening the update package and then installing update... 20 seconds later i get some symlinks failed, then I get a status 7 error in the file itself..
kwiksilvr said:
That us not the issue... I can get into the CWM recovery just fine.. when I choose the install zip from sdcad and choose the rom it will go through finding the package, then opening the update package and then installing update... 20 seconds later i get some symlinks failed, then I get a status 7 error in the file itself..
Click to expand...
Click to collapse
I guess what I recommended did not work?
Sent from my SCH-I535 using Tapatalk 2
Marcismo55 said:
I guess what I recommended did not work?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
nope and now im stuck boot looping TWRP after trying what you suggested unsuccessfully.
I appreciate the help... any ideas how I can get out of TWRP back to CWM so I can restore a backup?
Thanks..
You could always Odin back to stock then re-root and install cwm again and restore your backup. May be an easier way not sure. But back up your files on a PC if you do that.
Sent from my SCH-I535 using xda app-developers app
kwiksilvr said:
nope and now im stuck boot looping TWRP after trying what you suggested unsuccessfully.
I appreciate the help... any ideas how I can get out of TWRP back to CWM so I can restore a backup?
Thanks..
Click to expand...
Click to collapse
I don't know how you are blaming me when I specifically told you to flash a ClockworkMod/Kexec recovery... not TWRP.
Seems your issue is lack of following directions. Good luck on solving your issue.
Sent from my SCH-I535 using Tapatalk 2
I rooted my GNote 10.1 with zedomax's method, including flashing CWM recovery and had no issues with it. I wanted to upgrade to JB, and was going to try CM10, but when I tried to flash the .zip file through CWM, it gives me an error message. I have included a screenshot of the error message if it will help.
I know it's not an official CWM, but I'm reading how others have done this and wondered if I somehow made a mistake. I've never had a problem flashing any other phone, and I don't know where to go from here.
There may be a different way but i fixed that problem by using TWRP which i got in a thread from in the development section. It flashed with no problems. Im not sure what the issue but try a different custom recovery.
Sent from my GT-N8013 using Tapatalk 2
Had this issue also. Flashing from twrp did the trick. So once rooted, twrp installs through goo manager, which is here:
https://play.google.com/store/apps/details?id=com.s0up.goomanager
Read up on the twrp thread in android original development. The touch pad is a little dodgy, but it's workable.
Sent from my GT-N8013 using XDA Premium HD app
suspect_device said:
I rooted my GNote 10.1 with zedomax's method, including flashing CWM recovery and had no issues with it. I wanted to upgrade to JB, and was going to try CM10, but when I tried to flash the .zip file through CWM, it gives me an error message. I have included a screenshot of the error message if it will help.
I know it's not an official CWM, but I'm reading how others have done this and wondered if I somehow made a mistake. I've never had a problem flashing any other phone, and I don't know where to go from here.
Click to expand...
Click to collapse
Here's a flashable CWM from source:
http://db.tt/huUWk7Ty
This may help a bit. I found this somewhere on the web but I can't seem to find it again.
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
I wanted to switch back to stock Rom, I flashed it with fastboot (I downloaded 4.4.4)
I installed Root and XPosed, but I uninstalled XPosed again, Android wanted to update to 4.4.2 (settings said i have 4.4), but I got an error, Installed twrp and tried it manully, i got an error (i think it was error excecuting binary...)
This guide should fix you up,
http://forum.xda-developers.com/showthread.php?t=2513701
Returning to stock isnt the Problem! I have the stock installed
dav20011 said:
Returning to stock isnt the Problem! I have the stock installed
Click to expand...
Click to collapse
Yes it is. You returned to stock then modified it so it is no longer stock. You cannot update unless you're still stock, but you're not. So flash latest stock.
Sent from my Nexus 5 using Tapatalk
I used CWM recovery to install it and then i got a more specific error (/system/framework/core.odex contains..., so it is xposed)Should I reflash the system.img, and does this wipe data?
dav20011 said:
I used CWM recovery to install it and then i got a more specific error (/system/framework/core.odex contains..., so it is xposed)Should I reflash the system.img, and does this wipe data?
Click to expand...
Click to collapse
If you use the flash all method in the link above it will wipe your data. If you fastboot flash system.img only then nothing gets wiped
All guides and info threads are available in my signature
Sent from my Nexus 5 using Tapatalk
OK thx i know how it works, I already flashed stock
If you knew how it works, why did you ask me how it works?
Sent from my Nexus 5 using Tapatalk
I didnt ask how to install stock
dav20011 said:
I didnt ask how to install stock
Click to expand...
Click to collapse
OK whatever. You asked if it wiped data, which insinuates that you don't quite know enough.
Anyway, whatever, you know where the guides and info threads are now. Every question you've asked is covered there so please read them before posting threads
Thanks.
Sent from my Nexus 5 using Tapatalk
I read many Website and I only read that flashing all images will wipe everything, I already thought that it will only wipe /system, but I wanted to be sure, losing data isnt funny
Nope. Its not funny. But at the same time, all covered I'm the sticky threads.
Sent from my Nexus 5 using Tapatalk