• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Verizon] Issues with Casual One Click Method

C

corvetteii

Lurker
Has anyone had problems with the "Casual" one click method? I have tried it on three computers and made sure I had all the samsung mobile drivers etc and I can never get the Casual program to say "device connected" I did try to root it anyway since there were some youtube comments that said it still worked but it didn't root my SH-I535...It looked like it did and reset the phone but no root. Any advice? Thanks
 
Welcome corvetteii!
I moved your post to your own thread here:)

Have you tried a different, perhaps the oem, cord?

You said that it looked like it rooted the device, but what leads you to believe that it did not? Can you boot into recovery? (fully power off device, then hold the home and volume up buttons and at the same time push and hold power)
 
Thanks for moving my post and helping! I used rootchecker and it wasn't rooted. I did use the OEM cord ( with USB debugging enabled) and yes I can boot into recovery as well.. Its just weird that the casual program never says device connected but it clearly communicated with my device enough to simulate rooting the power cycle it. Perhaps I need to do the Odin method but I'm just so nervous I won't download the right files and screw it up lol.
 
Ok, so I'm not sure if this made a difference but I read in some other forums that you need to check "allow installation of apps from other sources than the play store" in order for Casual to work. I did that and it still never said my device was connected BUT it rooted my verizon S3 just fine this time. Now I have to figure out where to go from here like many others. I'm afraid of uninstalling any important apps that my phone needs, lol.
 
hmmm...so are you good to go? As in custom recovery, super user the whole shootn-shebang? Nice!! :D

Question tho, can your computer see your device when plugged into it normally?
 
I do have Superuser and root checker confirms my S3 is rooted. My computer sees my phone fine and I can access all my files etc although I dont understand why it never says connected on Casual. I have not installed a custom recovery as I'm not entirely sure what that is and if I can use Casual to do that or not....I'm taking baby steps so I don't do something stupid, lol. So right now, I can get into bootloader mode and I know what that looks like (factory reset, etc) BUT if I install, say, Clockwork Touch, will that bootloader screen look different?
 
I think you are referring to the "recovery" screen (home/volume up/power--correct?)

Casual should have installed TWRP recovery (a custom recovery) if I'm not mistaken.

What does that screen look like?

Edit: this is what stock recovery looks like:
Samsung-Galaxy-S3-Recovery-Mode.jpg
 
My recovery screen is stock like your picture there. I believe i selected the rootGS3 option only and did not install a custom recovery. In the casual program you can choose these options:
RootGS3,
flash insecure aboot,
install TWRP recovery
install CWM recovery
install CWM touch recovery
reboot recovery
reboot download

Here's the itinerary that Casual tells you to do:
Step 1. Root
Step 2. Flash Insecure Aboot
Step 3. Flash Recovery of Your Choice



I only rooted because I'm unsure what to do next. I assume install the recovery (don't know which one though) and I don't know what this "flash insecure aboot" means either. :confused:
 
I believe flashing the insecure aboot unlocks your bootloader (a requirement for most, if not all roms if you want to flash them)

And install a custom recovery is what you need to flash roms/kernels and other .zip files you want to install.


Edit: I just found this guy had a similar issue as you did where Casual never "saw" his device.....
http://forum.xda-developers.com/showpost.php?p=44131303&postcount=236

Edit again...I have to stop reading at post 245 there....my eyes hurt :(
Will continue reading tomorrow...
 
i was just scrolling through that thread myself. thanks for helping with this, again. So I did read of a guy bricking his phone while installing the custom recovery with casual because it didnt reboot his phone automatically and after 5 minutes, he shut his phone off. After that, bricked. Thats got me a little nervous but I'm thinking it should be fine. Do you think I should try another method of unlocking the bootloader and install a custom recovery instead of casual?
 
If there is another way to install recovery, it would be with the app goomanager
And to unlock the bootloader, ez unlock

Not sure about those in your case but it may work

You could also run casual again

There is always a risk to doing anything root related but I would try casual myself :)

Edit: thinking about this some more...I would run Casual again and choose the aboot and recovery install options...
 
breadnatty08 said:
BeanStalk just updated and is 4.3 based. Running really smooth for me. :)
http://forum.xda-developers.com/showthread.php?t=2354113
Click to expand...

Awesome, I may look into this one then. I was also reading about the BoneStock 3.4 as well (saw a youtube video from Tomsgt using the TWRP app manager to install this ROM) i'm guessing that is literally what it says, a stock ROM with the options of whatever bloatware you want or not? Its kinda difficult narrowing down what you think you want but then again, I guess you can just install a different one if you hate it. Mind you, I'm still new at this and a bit nervous lol.

I did complete a TRWP backup though! Which leads me to another question, IF I need to go from a custom ROM back to my stock ROM, my stock backup will do that for me right?

I did some reading about this Beanstalk 4.3 ROM and I'm confused about how exactly to do a couple things... I think I'm clear on how to install the ROM (save to SD card, then install with TWRP) But what is the process for installing GApps and the SU1.51.zip file after installing the ROM?
 
Using TWRP, you can add multiple .zip files (up to 10 I believe).
After you choose the ROM, click "Add more zips" then add the Gapps and SUfix file. If you're going from any other ROM, be sure to do a complete wipe, including a factory reset. If you're on the newest version of TWRP, it's the default setting for "Wipe".
Also, be sure to make a backup! :)
 
Casual worked fine for me despite using an ancient WinXP Pro laptop to do all the rooting. it requires the latest JAVA installed BTW
 
Late to the party here, but (in case someone stumbles upon this thread) I had this same issue with Casual not detecting my device.

My solution was putting the phone into download/ODIN mode (Volume+Down+Power, then Volume Up). After I did that, Casual detected with no problem, then installed root and TWRP.
 
twaelbroeck said:
Late to the party here, but (in case someone stumbles upon this thread) I had this same issue with Casual not detecting my device.

My solution was putting the phone into download/ODIN mode (Volume+Down+Power, then Volume Up). After I did that, Casual detected with no problem, then installed root and TWRP.
Click to expand...

Gave that a try, Kingo fails and tries to use other method and fails.
 
You must log in or register to reply here.
Back
Top Bottom