Related
After successfully flashing ClockWork RecoveryMod, I placed SU on the root of my SNS, powered it off, went into fastboot, but when I went into Recovery, it just went to Stock Recovery, the Exclamation Mark inside the Triangle with the Android next to it appeared, but no text or anything else is on the screen. I've let it sit for about 15 minutes, and nothing. I also can't do anything by clicking the volume buttons, or the power buttons. I've also unplugged the Phone, held the power button to try to reboot it, held volume-up and power to try to go back into fastboot, but nothing. Should I pull the battery? Why didn't it go into ClockWork RecoveryMod? Command Prompt gave me the whole " sending 'recovery' (3980 KB)... OKAY [ 0.621s]
writing 'recovery'... OKAY [ 0.511s]
finished. total time: 1.132s" thing...
What do I do? I can't just leave it sitting like this forever.
Edit: I unplugged and replugged it a few times, and it rebooted. But I've tried going back to fastboot and going into Recovery, and I get the same screen, over and over. I've even tried flashing CWRM again, and nothing. I'm using 3.0.2.4. Should I just use 3.0.0.5?
When you are in the stock recovery mode and you see the exclamation mark inside the triangle: Just hold the power button and hit volume up and you will get into stock recovery where you can perform a reboot etc.
Just try 3.0.0.5. There is something wrong with clokwork mod it you just went into stock recovery. You should be fine if you follow one of the guides on this forum.
If you still are using the stock rom. This only applies of on stock root rom because the custom rom have the edited already. You must do this. If you don't then you will have to flash clockwork ever time you reboot.
Reboot your Nexus S
Download and install Root Explorer app from Android Market
Open Root Explorer and navigate to etc directory
Tap on the gray box that says Mount R/W
Tap and hold on the file install-recovery.sh and rename this file to install-recovery.sh.old
Once renamed, download and install the app called ROM Manager from Android Market
Once installed, open ROM Manager app and choose Flash ClockworkMod Recovery option.
Hawky_ said:
When you are in the stock recovery mode and you see the exclamation mark inside the triangle: Just hold the power button and hit volume up and you will get into stock recovery where you can perform a reboot etc.
Just try 3.0.0.5. There is something wrong with clokwork mod it you just went into stock recovery. You should be fine if you follow one of the guides on this forum.
Click to expand...
Click to collapse
I tried it again with 3.0.2.5 from http://forum.xda-developers.com/showthread.php?t=988686. Did not work. Went again into Stock Recovery.
jerrycycle said:
If you still are using the stock rom. This only applies of on stock root rom because the custom rom have the edited already. You must do this. If you don't then you will have to flash clockwork ever time you reboot.
Reboot your Nexus S
Download and install Root Explorer app from Android Market
Open Root Explorer and navigate to etc directory
Tap on the gray box that says Mount R/W
Tap and hold on the file install-recovery.sh and rename this file to install-recovery.sh.old
Once renamed, download and install the app called ROM Manager from Android Market
Once installed, open ROM Manager app and choose Flash ClockworkMod Recovery option.
Click to expand...
Click to collapse
I'm a bit confused with your post.
I am still using the Stock Rom, but I don't have root access.
I've tried, after unlocking the Bootloader, going into Rom Manager and Flashing ClockWork, but it tells me first:
"You must root your phone for ROM Manager to function. Superuser was not found at "/system/bin/su" or "/system/xbin.su". (...)"
Then, when I still attempt to flash ClockworkMod, it tells me:
"An error occurred while attempting to run priviliged commands!"
I should have told the full story first.
I was once rooted, but it was through ROM Manager and flashing Clockwork from there. But then I had a few issues with my Wifi, and I decided to flash back Stock Rom. I still had an unlocked Bootloader though, so I thought that just redownloading Rom Manager and flashing CWRM and having Superuser installed would work. It didn't. So I attempted to root all over again, this time, manually.
But, I always go back to square one, it seems, when I try to get into Recovery.
What up with that?
After you flash CWM recovery, go straight into recovery from the fastboot menu. Do not reboot. Do not power off. Flash CWM and when it finishes immediately press volume down to select recovery and then press power to go in.
The Nexus S will overwrite CWM with stock recovery every time the phone boots by default. This could be what is giving you trouble.
Sent from my Nexus S using XDA App
matt2053 said:
After you flash CWM recovery, go straight into recovery from the fastboot menu. Do not reboot. Do not power off. Flash CWM and when it finishes immediately press volume down to select recovery and then press power to go in.
The Nexus S will overwrite CWM with stock recovery every time the phone boots by default. This could be what is giving you trouble.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Thank you so much!
That was it!
After I did that, I went straight into Recovery, flash SU, rebooted, went into ROM Manager, Flashed CWRM from there, and boom.
I don't understand why AllGamer's guide didn't already say that could happen. I'll post a comment there.
Thanks again!
EonHawk said:
Thank you so much!
That was it!
After I did that, I went straight into Recovery, flash SU, rebooted, went into ROM Manager, Flashed CWRM from there, and boom.
I don't understand why AllGamer's guide didn't already say that could happen. I'll post a comment there.
Thanks again!
Click to expand...
Click to collapse
No problem.
There is a script located in the /etc folder called install-recovery.sh. it runs every time you boot and installs stock recovery. You have two choices: always use rom manager to flash CWM every time you need to access recovery, or use root explorer to rename install-recovery.sh to install-recovery.sh.bak so that it will not run and will leave CWM installed.
Glad you got it figured out!
Sent from my Nexus S using XDA App
Or a third choice of course would be to install a custom ROM because they tend to not include that script
Sent from my Nexus S using XDA App
EonHawk said:
Thank you so much!
That was it!
After I did that, I went straight into Recovery, flash SU, rebooted, went into ROM Manager, Flashed CWRM from there, and boom.
I don't understand why AllGamer's guide didn't already say that could happen. I'll post a comment there.
Thanks again!
Click to expand...
Click to collapse
If you are talking about this guide then it does warn about this problem. I used the guide to root my nexus s and I followed all his steps, including renaming the necessary file - http://forum.xda-developers.com/showthread.php?t=895545
This is from his 2nd post - called notes:
NOTES:
It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
If you want to the CW recovery to remain permanently, you'll need to rename /etc/install-recovery.sh to something thing else
buachaille said:
If you are talking about this guide then it does warn about this problem. I used the guide to root my nexus s and I followed all his steps, including renaming the necessary file - http://forum.xda-developers.com/showthread.php?t=895545
This is from his 2nd post - called notes:
NOTES:
It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
If you want to the CW recovery to remain permanently, you'll need to rename /etc/install-recovery.sh to something thing else
Click to expand...
Click to collapse
Actually I think that guide does have two unnecessary steps that cause confusion. After flashing CWM, the guide instructs the user to power off, power on, and then to access recovery. The user should just access recovery immediately after flashing.
EDIT: I guess the problem is just that the bolded part should be added:
Then back on the SNS select Power Off (Reboot also works)
Power ON the SNS while holding volume up
buachaille said:
If you are talking about this guide then it does warn about this problem. I used the guide to root my nexus s and I followed all his steps, including renaming the necessary file - http://forum.xda-developers.com/showthread.php?t=895545
This is from his 2nd post - called notes:
NOTES:
It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
If you want to the CW recovery to remain permanently, you'll need to rename /etc/install-recovery.sh to something thing else
Click to expand...
Click to collapse
That's partly my fault, I never went down to the 2nd Post and saw those Notes, but what's the point of not including that already in the steps in the main Post? He could have just told to go straight from Recovery after flashing CWRM, but decided not to.
matt2053 said:
Actually I think that guide does have two unnecessary steps that cause confusion. After flashing CWM, the guide instructs the user to power off, power on, and then to access recovery. The user should just access recovery immediately after flashing.
EDIT: I guess the problem is just that the bolded part should be added:
Then back on the SNS select Power Off (Reboot also works)
Power ON the SNS while holding volume up
Click to expand...
Click to collapse
I think he should just have instructed to place the SU zip on the root of the SD card before flashing CWRM. That way, there wouldn't be a need to reboot to mount the SD to place SU, that way potentially losing the CWRM.
Well as it says I have root rom manager says version 5.5 or whatever is installed yet no matter how I try to boot to recovery I see no cwm? Am I missing something?
Sent from my SAMSUNG-SGH-I727 using XDA App
Did you just say you installed CWM Recovery with ROM manager?
Did you try
Push and hold Vol down plus power button til you see words at top left corner
Immediately push Vol up within about 5 sec to get into recovery.
or you could use "Transformer reboot to recovery" app from market.
If you don't see CWM recovery do you see stock recovery?
baseballfanz said:
Did you just say you installed CWM Recovery with ROM manager?
Did you try
Push and hold Vol down plus power button til you see words at top left corner
Immediately push Vol up within about 5 sec to get into recovery.
or you could use "Transformer reboot to recovery" app from market.
If you don't see CWM recovery do you see stock recovery?
Click to expand...
Click to collapse
For the love of GOD, if you used ROM Manager to flash CWM, you most likely have version 5.5.0.4... DO NOT USE IT!!!!
Refer to this thread: http://forum.xda-developers.com/showthread.php?t=1530337
Use Recovery Installer found here: http://forum.xda-developers.com/showthread.php?t=1346180
That will install a usable version of CWM and save you a LOT of hassle.
Thanks for the help guys. Ill hit the thanks button on both of y'all since I used both . Worked perfect
Sent from my SAMSUNG-SGH-I727 using XDA App
So did you install cwm with ROM manager? If you did, so a normal reboot to sew what happened.
I did install it through ROM manager first but it never would boot to recovery. I tried booting through ROM manager and all it would do is reboot, so then I downloaded a app to recovery boot still just rebooted thats when i posted the question and yall answered. Hope this answered you question for me
Sent from my Transformer TF101 using XDA
stepheng said:
I did install it through ROM manager first but it never would boot to recovery. I tried booting through ROM manager and all it would do is reboot, so then I downloaded a app to recovery boot still just rebooted thats when i posted the question and yall answered. Hope this answered you question for me
Sent from my Transformer TF101 using XDA
Click to expand...
Click to collapse
Reason I asked was a lot of peoples have problems with CWM after flashing through ROM Manager. If it's working for you that's good.
No it didn't I ended up flashing the one that the other guy posted the installer for and it worked
Sent from my Transformer TF101 using XDA
Hi.
Just rooted my TF101 (B80) using ViperMod V4,5.
SU working fine, got root access and everything.
My only problem is that i cannot enter recovery mode. I get the android with the red triangle.
I press Volume- + power, then volume+ and it says:
"booting recovery kernel image"
After that i get the android with the triangle.
Any idea how to solve this problem?
What you see is the recovery, only it's the stock recovery.
To get cwm recovery, use RecoveryInstaller by Gnufabio. Just look in the theme app section
baseballfanz said:
What you see is the recovery, only it's the stock recovery.
To get cwm recovery, use RecoveryInstaller by Gnufabio. Just look in the theme app section
Click to expand...
Click to collapse
I have used the recoveryinstaller.apk and still the same result. Then i tried installing a recovery using rom manager but still the same.
Can i use adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3 command?
P.S. I forgot to mention that i am on stock ICS ww.9.2.1.17
read the (epic noob guide) by luna_C666 in the general section.its got all the answers and more!
Sent from my Transformer TF101 using xda premium
original21 said:
I have used the recoveryinstaller.apk and still the same result. Then i tried installing a recovery using rom manager but still the same.
Can i use adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3 command?
P.S. I forgot to mention that i am on stock ICS ww.9.2.1.17
Click to expand...
Click to collapse
is your tf rooted?
baseballfanz said:
is your tf rooted?
Click to expand...
Click to collapse
Yes (I think). I used basic root checker and it says that is rooted. It also ask for super user access for it.
Ok. Solved.
I re-downloaded the recovery installer and everything is ok now. Thanks
I had the issue where I had the constant recovery loop and had to manually cold-boot linux every time. Then I followed all the directions that supposedly fixed that and it seemed to work (I could boot straight to android from power off). Now I can't boot into recovery at all. It just hangs at the Asus logo if I choose "reboot into recovery" and it hangs at "booting recovery image" if I use volume down. CWM shows that my recovery image is installed but there is something preventing it from launching.
Is there a way to format the recovery partition and flash it again? I tried the CWM "erase recovery" and that didn't work.
Sent from my Transformer TF101 using XDA Premium HD app
I've got the same issue, can do what I want, but can't boot to recovery ... grrrr
Same issues with boot and recovery
I am experiencing the same issue too, except I can't boot into the OS either so I am not sure what to do... I'll read the epic noob guide as described above and if I don;t come right there i'll post a thread as my challenges are slightly different to what is already posted.
Enigma_2k4 said:
I am experiencing the same issue too, except I can't boot into the OS either so I am not sure what to do... I'll read the epic noob guide as described above and if I don;t come right there i'll post a thread as my challenges are slightly different to what is already posted.
Click to expand...
Click to collapse
You have to hold the volume down at boot like you are booting to recovery, but then don't do anything and a menu to coldboot linux or to erase userdata comes up. Just wait and it will boot android.
Sent from my Transformer TF101 using XDA Premium HD app
original21 said:
Hi.
Just rooted my TF101 (B80) using ViperMod V4,5.
SU working fine, got root access and everything.
My only problem is that i cannot enter recovery mode. I get the android with the red triangle.
I press Volume- + power, then volume+ and it says:
"booting recovery kernel image"
After that i get the android with the triangle.
Any idea how to solve this problem?
Click to expand...
Click to collapse
After being rooted and flashing CWM instead of holding volume down+power.. just download this app from the market. Called: Transformer reboot to Recovery.
The app in your drawer icon is two blue arrows instead of orange and blue like the developers picture.
https://play.google.com/store/apps/...recovery&rdid=com.transformer.recovery&rdot=1
Ive noticed alot of people having issues booting with Clockworkmod into recovery or using power down and selecting recovery. (unless its done by hand). That app is a direct way into recovery. Most ROMs ive seen do not enter recovery even when the option is present.
Here is gnufabio, Recovery Installer - flash CWM with a Click
http://forum.xda-developers.com/showthread.php?t=1346180
after flashing use the Transformer reboot to Recovery app i listed above. Ive used it and it works.. i use the app to enter recovery all the time.
Hi All,
I've looked all around for the answer to this and am thoroughly lost. I have the Verizon Galaxy S3 with VRALHE. I rooted it, then used EZ-Unlock 1.2 to unlock the phone, then installed Rom manager and flashed CWR. It says it installed 6.0.1.2 but when I try and go into recovery it only goes into Android Recovery. If I flash CWR and right away click the boot into CWR button it seems to go but after that it will only go into Android Recover both via Rom manager and holding Volume Up, Power and Home. Anyone know whats going on?
Thanks for your help!
If it does go into cwm the first time then after that stock there are two files you need to erase that basically reinstall the stock recovery on reboot. I can't recall them, but you could probably search here and find them. Or the easier way is busy flash a custom ROM n that first boot into cwm. By the way ez recovery is better for installing our recoveries, give it a shot.... It may sick without the extra stuff I just told you.
Sent from my SCH-I535 using xda app-developers app
Anyone know where to look into about the files that need to be deleted? I'm not finding much. EZ recovery worked the first reboot but returned to Android recovery after a reboot.
Boss428man said:
Anyone know where to look into about the files that need to be deleted? I'm not finding much. EZ recovery worked the first reboot but returned to Android recovery after a reboot.
Click to expand...
Click to collapse
I would recommend re-flashing Clockworkmod Recovery from EZ recovery, then using EZ recovery to boot into Clockworkmod Recovery, after your are in Clockworkmod Recovery select the "Reboot system" option, you should then be asked if you want to erase two files to make Clockworkmod Recovery stick permanently (At least until you flash a different recovery) select the "Yes" option, then after it has completed that task the phone should reboot, while it is rebooting boot into recovery and you should find that Clockworkmod Recovery is still installed.
I like to help, but Google stuff. This is what you would have found as the second result
/system/recovery-from-boot.p*
/system/etc/install-recovery.sh
Sent from my SCH-I535 using xda app-developers app
So to confirm to everyone, Deleting the 2 files above does work! So delete the files then re-flash CWR and restart that's it!
I wanted to thank everyone for the help!
Same problem but a little different
shimp208 said:
I would recommend re-flashing Clockworkmod Recovery from EZ recovery, then using EZ recovery to boot into Clockworkmod Recovery, after your are in Clockworkmod Recovery select the "Reboot system" option, you should then be asked if you want to erase two files to make Clockworkmod Recovery stick permanently (At least until you flash a different recovery) select the "Yes" option, then after it has completed that task the phone should reboot, while it is rebooting boot into recovery and you should find that Clockworkmod Recovery is still installed.
Click to expand...
Click to collapse
I have the same problem sorta, my phone instead of going into CWR it goes into Android system Recovery, and it asks me for an update, I was trying to root my phone but it won't even let me go into recovery so I can root it. Do you know why it's asking me this? Also idk if this helps but the android dude is in the background with an open stomach and a triangle and an exclamation mark in it. Hope my details were helpful, thanks.
Wizardtech-101 said:
I have the same problem sorta, my phone instead of going into CWR it goes into Android system Recovery, and it asks me for an update, I was trying to root my phone but it won't even let me go into recovery so I can root it. Do you know why it's asking me this? Also idk if this helps but the android dude is in the background with an open stomach and a triangle and an exclamation mark in it. Hope my details were helpful, thanks.
Click to expand...
Click to collapse
What rooting guide did you follow? Did you flash Clockworkmod Recovery yet? If you can provide me with this information I can try help you further. If you haven't flashed Clockworkmod Recovery yet then you will be presented with the normal stock Android recovery system that you described.
Wizardtech-101 said:
I have the same problem sorta, my phone instead of going into CWR it goes into Android system Recovery, and it asks me for an update, I was trying to root my phone but it won't even let me go into recovery so I can root it. Do you know why it's asking me this? Also idk if this helps but the android dude is in the background with an open stomach and a triangle and an exclamation mark in it. Hope my details were helpful, thanks.
Click to expand...
Click to collapse
Ummm... You do not necessarily go into recovery to root it. Have you installed and used Odin through your PC? You say you are trying to root your phone, so before you get ahead of yourself trying to flash recoveries I recommend reading up a little bit, it is very important you follow directions specifically or you will brick your device....
http://forum.xda-developers.com/showthread.php?t=2046439
There is even a video watch it while you root your phone, and pause along with it.
If you have already done some of this, and done any of it wrong there are steps to recover through Odin.
I rooted with Casual and selected TWRP for Custom Recovery. Everything seems to be working fine, but I have been unable to start TWRP. With phone off, I hold volume down + Power. The phone will vibrate every few seconds until I release the power button. Then it starts in normal Android mode. Am I trying to start this in the wrong way or is there something messed up with TWRP on my phone?
joekiv said:
I rooted with Casual and selected TWRP for Custom Recovery. Everything seems to be working fine, but I have been unable to start TWRP. With phone off, I hold volume down + Power. The phone will vibrate every few seconds until I release the power button. Then it starts in normal Android mode. Am I trying to start this in the wrong way or is there something messed up with TWRP on my phone?
Click to expand...
Click to collapse
Until you flash a rom that has a custom menu to boot to recovery you have to hold volume up plus the home key while hitting the power button. Let the power button go but keep holding the volume up and home key then TWRP should start up.
Edit: You can also download Quick Boot by Sirius app from the play store and see if that gets you to your recovery until you get a rom on that let's you boot straight to recovery.
TheAfroSamurai said:
Until you flash a rom that has a custom menu to boot to recovery you have to hold volume up plus the home key while hitting the power button. Let the power button go but keep holding the volume up and home key then TWRP should start up.
Edit: You can also download Quick Boot by Sirius app from the play store and see if that gets you to your recovery until you get a rom on that let's you boot straight to recovery.
Click to expand...
Click to collapse
The buttons worked BUT TWRP isn't. I have an Android Robot, out for the count, he is on his back. The recovery must be messed up.
joekiv said:
The buttons worked BUT TWRP isn't. I have an Android Robot, out for the count, he is on his back. The recovery must be messed up.
Click to expand...
Click to collapse
That's the stock recovery. Download too manager and install twrp from the settings menu
Sent from my SCH-I535
jhoutz said:
That's the stock recovery. Download too manager and install twrp from the settings menu
Sent from my SCH-I535
Click to expand...
Click to collapse
Thanks, but I already tried redoing TWRP with Goo Manager. Program ran fine & finished, but when I rebooted into recovery I got the dead Android Robot again. Don't know how to proceed at this point. May try re-running Casual. Still reading everything I can find on this situation before doing anything.
From a powered off state, hold volume UP, home, and power. Let go of the power button when the phone vibrates.
Sent from my SCH-I535 using Tapatalk 4
SlimSnoopOS said:
From a powered off state, hold volume UP, home, and power. Let go of the power button when the phone vibrates.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Done that multiple times, same result - Android on back. Tried redoing TWRP with Goo manager, also Checked on lock/unlock with Ez Unlock - got "status unknown". Did not risk pressing either 'Lock' or 'Unlock' and exited app. Not sure what to do next.
Phone is working. Can make calls, messages, use & install apps and change settings. SuperSU is working, TB Pro is working. I did TB Backups & uninstalled multiple locked apps (Bloatware) before discovering that I cannot get into a working TWRP Recovery.
Any suggestions would be greatly appreciated.
joekiv said:
Done that multiple times, same result - Android on back. Tried redoing TWRP with Goo manager, also Checked on lock/unlock with Ez Unlock - got "status unknown". Did not risk pressing either 'Lock' or 'Unlock' and exited app. Not sure what to do next.
Phone is working. Can make calls, messages, use & install apps and change settings. SuperSU is working, TB Pro is working. I did TB Backups & uninstalled multiple locked apps (Bloatware) before discovering that I cannot get into a working TWRP Recovery.
Any suggestions would be greatly appreciated.
Click to expand...
Click to collapse
Odin flash a TWRP tar. Uncheck auto-reboot, once it successfully flashes, pull the battery then try booting directly into twrp.
SlimSnoopOS said:
Odin flash a TWRP tar. Uncheck auto-reboot, once it successfully flashes, pull the battery then try booting directly into twrp.
Click to expand...
Click to collapse
Will Odin work if I am unable to get the phone into a working bootloader?
joekiv said:
Will Odin work if I am unable to get the phone into a working bootloader?
Click to expand...
Click to collapse
It should. There's download mode and there's recovery mode. You are having issues flashing a recovery. I don't see anything in your prior posts about difficulty accessing anything else.
SlimSnoopOS said:
It should. There's download mode and there's recovery mode. You are having issues flashing a recovery. I don't see anything in your prior posts about difficulty accessing anything else.
Click to expand...
Click to collapse
Your link above for the "TWRP Tar" goes to a page that instructs to go into odin mode on the 'device' by pressing Vol down, home and power. When I do that I get the Android Robot standing and a message that says "Downloading Custom, do not turn off device". At this point no buttons work and I have no choices do do anything and have to do a battery pull to get out. If I go in any other way I get the Robot on its back.
EDIT: You link was only for the purpose of getting the tar file, not a suggestion to use Odin Mobile. I think that all of the time I spent reading about this issue is affecting my brain.
joekiv said:
Your link above for the "TWRP Tar" goes to a page that instructs to go into odin mode on the 'device' by pressing Vol down, home and power. When I do that I get the Android Robot standing and a message that says "Downloading Custom, do not turn off device". At this point no buttons work and I have no choices do do anything and have to do a battery pull to get out. If I go in any other way I get the Robot on its back.
Click to expand...
Click to collapse
Yes, you use Odin from a computer and boot your phone into download mode then connect it via usb to flash files. Based on your post, you haven't used Odin before have you?
Edit: If it makes it easier, this thread has a [HOW TO] for Odin and the process of flashing tar files as well.
SlimSnoopOS said:
Yes, you use Odin from a computer and boot your phone into download mode then connect it via usb to flash files. Based on your post, you haven't used Odin before have you?
Edit: If it makes it easier, this thread has a [HOW TO] for Odin and the process of flashing tar files as well.
Click to expand...
Click to collapse
No I haven't, but I realized (slowly) what you meant and edited my last post, Probably while you were posting this.
joekiv said:
No I haven't, but I realized (slowly) what you meant and edited my last post, Probably while you were posting this.
Click to expand...
Click to collapse
Ahh, I see that now. Also, per your earlier statement about EZ Unlock. If you have v1.2, just tapping unlock does not harm the phone in any capacity. In fact, fact I encourage you to do so just before using Odin (from a computer) to flash TWRP or CWM. EZ Unlock v1.2 only unlocks the bootloader.
Sent from my SCH-I535 using Tapatalk 4
Did your suggestion and Ran Ez Unlock again and pressed 'Unlock', Status now says UNlocked. Now that it does I'm going to give Goo Manager 1 more shot at fixing TWRP before I run Odin with the TWRP Tar you linked to.
joekiv said:
Did your suggestion and Ran Ez Unlock again and pressed 'Unlock', Status now says UNlocked. Now that it does I'm going to give Goo Manager 1 more shot at fixing TWRP before I run Odin with the TWRP Tar you linked to.
Click to expand...
Click to collapse
Cool, let me know what happens.
Sent from my SCH-I535 using Tapatalk 4
SlimSnoopOS said:
Cool, let me know what happens.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Ran Goo Manager, but no success. Put phone in download mode and used Odin to flash recovery with openrecovery-twrp-2.6.1.0-d2vzw.tar. Odin ran through to end and showed "Pass" and rebooted. Used Vol UP, Home & Power keys to enter TWRP got the Robot on his back with a Red Exclamation mark with this message below:
# Manual Mode #
"...Applying Multi ...CSC
Applying the CSC Code: VZW
Successfully applied Multi-CSC
I have 6 choices on this screen.
1 Reboot System Now (I pressed power and phone booted normally)
2 Apply Update from ADB
3.Apply Updated from External Storage
4 Wipe Data/Factory Reset
5 Wipe Cache Partition
6 Apply update from Cache
So I still can't get into TWRP and the only difference is now the Red Exclamation Point.
Did you uncheck "auto reboot" and pull the battery and boot into TWRP like I said before?
Here's a third method if the above does not work. Download EZ Recovery from the Play Store. Once you've done so, you can use my prior link from Rootzwiki and download a TWRP img (image) and use EZ Recovery to install that img file. For this method, make sure to use TWRP.img. Do not use the "tar" file, for this method, tar files are for Odin only.
Sent from my SCH-I535 using Tapatalk 4
SlimSnoopOS said:
Did you uncheck "auto reboot" and pull the battery and boot into TWRP like I said before?
Here's a third method if the above does not work. Download EZ Recovery from the Play Store. Once you've done so, you can use my prior link from Rootzwiki and download a TWRP img (image) and use EZ Recovery to install that img file. For this method, make sure to use TWRP.img. Do not use the "tar" file, for this method, tar files are for Odin only.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
SUCCESS! Flashed the recovery again, BUT this time with Auto reboot unchecked as you previously told me to do and that I missed. Thank you, not only for your help, but for all your patience as well.
joekiv said:
SUCCESS! Flashed the recovery again, BUT this time with Auto reboot unchecked as you previously told me to do and that I missed. Thank you, not only for your help, but for all your patience as well.
Click to expand...
Click to collapse
Ahh, sweet! haha glad I could help you out!