[Q] New to Android, Issue Rooting US-VZW-GS4 [SCH-I545] - Verizon Samsung Galaxy S 4

I bought a US GS4 on Verizon two weeks ago, and I recently stumbled upon this XDA thread http://forum.xda-developers.com/showthread.php?t=2301720. Even though I am new to this, I am fairly technical so I decided to try it out. I am currently on the stock OS that came with the GS4. Currently, I want to get root access so I can remove some this Samsung bloatware.
I read the thread and prepared my phone by enabling USB debugging, allowing installations from unknown sources. Then, I installed Kies/Samsung USB drivers on my computer. Next, I removed my lock screen pw entirely and hooked my phone up to my computer via USB. When I ran the RUN_ME.bat, I immediately received a message asking me to allow my computer to access the phone. As it said in the thread, I clicked always allow.
Next, Odin 3.0.7 was initialized and my phone went to a Downloading screen with the green android icon. As soon as the ODIN software initializes, the message box in the lower left hand showed:
<ID:0/005> Added
<ID:0/005> Removed
It was almost like Odin could access my phone for a second and then was kicked out. At that point, I still unchecked "F Reset", selected the .tar file under the PDA button and attempted start. I then got the "<OSM> All threads completed. (succeed 0 / failed 0)" notification. Luckily, I was still able to simply reboot my phone when this happens. I research this happening to other people with Odin, and some threads suggested disabling anti-viruses, using the USB ports on the back of the computer instead of front, and using the cable that came with the phone. I have tried all of these things and I am still having the same issue.
Has anyone experienced this? Since I am new to this, I hope I am not missing something ridiculous. I tried to reply to the XDA i545 too thread but it says I don't have access and I should post in the Q&A forum here. I searched the forums and couldn't find something identical for the new i545's. I appreciate any feedback and help.

I had a hell of a time rooting, but that's because I run a Mac with a windows 7 VM, and the USB passthrough and driver install didn't work terribly well. I eventually got it, but wish it had waited for the all in one root tool. You may want to give that guide and utility a shot.

citenx said:
I had a hell of a time rooting, but that's because I run a Mac with a windows 7 VM, and the USB passthrough and driver install didn't work terribly well. I eventually got it, but wish it had waited for the all in one root tool. You may want to give that guide and utility a shot.
Click to expand...
Click to collapse
That's what I am using unfortunately =[. I am using a Windows XP machine, too. It's odd that my phone recognizes the computer accessing it, but won't let the computer connect via ODIN.

Related

[Q] samsung fascinate driver install problems!!! hELP!!!

i need help, i have tried everywhere and can't find anything and any help would be greatly appreciated
i'm on the road to root my samsung galaxy fascinate and have ran into a laundry list of problems. i have rooted many android phones coming from eclair, froyo, and gingerbread, but seem to be stuck at the slightest of problems when it comes to the fascinate.
i can not install the drivers to the fascinate. i have searched through the web for all the drivers and have tried every possible galaxy driver. the driver simply won't install on my windows 7 prof 64bit machine. i have never ran into this problem before with any other phone. every time i try to install the driver it gets to the very end of the install then pops up with the message "windows was unable to install the driver"
It also gave me the option to view the failed windows installation log, which after many successful steps, at the end the log shows this error:
Action ended 1:26:53: ShowMsiLog. Return value 0.
=== Logging stopped: 12/16/2011 1:26:53 ===
MSI (c) (0C:08) [01:26:53:750]: Product: SAMSUNG USB Driver for Mobile Phones -- Installation operation failed.
MSI (c) (0C:08) [01:26:53:750]: Windows Installer installed the product. Product Name: SAMSUNG USB Driver for Mobile Phones. Product Version: 1.3.550.0. Product Language: 1033. Manufacturer: SAMSUNG Electronics CO., LTD.. Installation success or error status: 1603.
i have also attached the entire log
the first thing i did was plug in the phone, which windows sensed this and automatically installed a driver, not sure which. after this i unplugged the phone and then checked "usb debugging" for rooting purposes and plugged the phone back into the computer which windows then installed another driver automatically, then following the steps from xda to root the phone, i downloaded the given drivers which is where the problem first occurred and the drivers were unable to download.
I'm simply trying to get root access to the phone and can't do anything with the phone with crappy drivers...i can't even mount usb sd card now to transfer data anymore. the drivers have completely been shot. i desperately need help. please
also what is the absolute easiest way to root the fascinate? is it with one click root or with Odin? Because the fascinate just updated itself from 2.2.2 EH05 to 2.3.5 EH03 and i'm not sure which program supports rooting which version of android. also all other android devices simply give root access to the stock rom, which is great cause i get to keep all my apps, messages, contacts...etc, then simply titanium backup everything and transfer it over to the new rom. is it different with the fascinate? will rooting the device simply flash a completely new rooted rom? therefore loosing everything? if anybody has any answers to any of these questions, please be my hero. thanks
Uninstall everything you previously installed in the way of Samsung drivers (in fact, you could use Windows 7 backup and restore to restore your PC to the state it was in the day before you installed the drivers as they are sometimes hard to uninstall completely). Reboot and simply plug your phone (with USB debugging of course), and let Windows automatically install the drivers for you like it did before you installed the ones linked to on XDA. This time, if your PC recognizes your phone, just keep the drivers you have and don't install the ones linked to. Those drivers from the guide are for those whose PC doesn't automatically install working drivers. From that point, just follow the rest of the guide and skip the install drivers part. You will not have to install any further drivers unless you flash an AOSP ROM, in which case you'll have to follow the instructions in the OP of the ROM thread. I hope this works for you.
Has anyone seen John Connor?
awesome thank you, i will try this out, and if this doesnt work i can always try another pc.
and as to the question of rooting the fascinate, like i said before i've never had a phone that has been wiped when i got root access initially, but it seems that everyone is saying that a rooted rom must be flashed from Odin in order to have root access. In other builds it seem that all is done is busybox and superuser are just pushed to the phone. will the fascinate be wiped when initial root is acquired?
bigwhat said:
awesome thank you, i will try this out, and if this doesnt work i can always try another pc.
and as to the question of rooting the fascinate, like i said before i've never had a phone that has been wiped when i got root access initially, but it seems that everyone is saying that a rooted rom must be flashed from Odin in order to have root access. In other builds it seem that all is done is busybox and superuser are just pushed to the phone. will the fascinate be wiped when initial root is acquired?
Click to expand...
Click to collapse
root is not flashed via odin, rather cwm is...then the root file su_2.6.3.1 is flashed via cwm. If you need directions section 5 of my guide in general section has it covered...everything needed is there including the correct recovery and root file.
I will tell you what...the Fascinate is probably the biggest pain in the ass phone...I tried forever to root my friends and couldn't get it done...need to try again I guess, but it was a driver issue as well..ODIN just wouldn't recognize the dam phone
Use Droidstyles guide. Very easy to follow. Also, the USB cable for some reason seams to be a bit finicky at times with this device. Unplug from phone and replug. Sounds odd but trust me, I have done this many times.
Sent from my SCH-I500 using XDA App
I am having a problem too and it's not covered anywhere i've seen to date. I've got an XP and a Win7 box at home. On both, I've tried with no drivers and i've tried with every other driver set I can find and every time I hook the phone up to the machine it pops up saying USB device couldn't be recognized or something. I'm going nuts! I've never had so much difficulty in my life, not even the first time changing ROMs on anything.
Droidstyle- I've seen your guide and unless I missed it doesn't cover this. Have you seen or heard of this and have any ideas at all?
Thanks!

[Q] Samsung Charge usb issue, please help!

Posted this on the general discussion section but have had no replies, hopefully someone here can help?
Hi everyone, first, this is my first post, new to the forums, at least as a registered user. I have a problem with my phone. I know most of you are wondering why I have not just read the other posts on the forums, but I have. I have attempted every solution to the problem posted previously.
Background: Phone: Samsung charge.
I was being impatient and did not want to wait for the gingerbread update form Verizon. I flashed the leaked gingerbread 2.3.4 onto my phone using odin. Everything went great. I was able to use my phone with no problems except shortened battery life, but nothing major. About a month ago the battery life was impossible to maintain and there were some software bugs, like clicks during calls, startup taking forever, around 2 minutes on average!, and random restarts that never happened before. I decided to look up some fixes and found that verizon and samsung had released GB 2.3.6 for the charge. I got excited and decided I wanted to get that, but I could not via OTA. I read some forum posts and they mentioned attempting a factory reset on the phone then trying OTA update. I went ahead with factory reset and everything went fine. My startup time is around 25 seconds now and no random clicks or gliches, but still not on 2.3.6, which was the whole point. I then decided to just flash the stock 2.3.6 rom to the phone.
Problem: When I plug my phone in to multiple computers it will charge but not connect to the computer. This means on my Mac it does not show as an external drive, which it has in the past. On my windows 7 machine it says that drivers were installed but could not be used (I can get the exact quote if needed.) I attempted to go into device manager and solve problem that way but it shows my phone as "unknown device". I have tried to enter download mode when hooked up to windows computers and no connection is found.
Possible solutions attempted and their outcomes:
1. As stated, I attempted the method shown in a thread on droid forums for installing the samsung drivers. I have attempted multiple times to install the drivers on my windows machine and the device remains "unknown".
2. I have attempted multiple cables on multiple computers, both mac and windows 7. No change.
3. I have installed adb and attempted to locate devices using adb devices command on mac. No devices found.
4. I have attempted all methods with both usb debugging checked and unchecked.
5. I have tried every possible usb port I have.
Ideas/questions I have had that I have no idea are possible or how to fix!
Would a factory reset take away the ability to connect to a computer from my phone. So, is there a piece of software in the build I have that controls the connection between the computer and the phone, an identifier of sorts, which is now missing, now that I have reset the leaked ROM.
Is there a way to flash a new ROM without connecting to a computer, via the sd card, and what is that? I have read some things in other posts but am too much of a n00b to understand most of them when using sdcards.
ANY help will be greatly appreciated. PLEASE PLEASE PLEASE!!! I have been at this for at least 6 hours, sifting through forums, searching google, attempting fixes that others have stated worked for them, only to fail every time. Thank you all.
have you try on a different pc?
maybe on your PC there is some problem with the drivers.
Moreover to connect via
adb u must enable Debug mode on your device in the application menu.
To flash kernel or other directly from your sd you can use the clockwordmode, but to install it you must before
install it and i fear you must use your cable connection
Sent from my GT-I9100 using XDA App
I have tried multiple PCs and a mac, even windows on bootcamp. I have installed drivers on every one, even uninstalled and reinstalled on one. One PC, my laptop was a fresh windows install (it was a linux box but I needed windows to use Odin). I was in debug mode and not in debug mode when attempting adb. Thanks for the suggestions though. As I said, I have tried numerous things and am completely stuck! so frustrating!
"I attempted to go into device manager and solve problem that way but it shows my phone as "unknown device"
Exactly there... you can try to force device to install a different driver.
Double click the unknown device then driver then update driver then find software in your computer then choose manually from a list of device drivers in your computer then show all devices you should see "android adb interface" or something related to google or android.
Try it... i hope this can help you.

Bit of a problem with rooting

Hi all. So I just picked up a Verizon Note 2 today and happily looked forward to rooting it. I'm on 4.1.2 Jellybean VRAMC3, model number SCH-I605. I'm afraid I may have messed something up.
I had downloaded Odin and installed the Samsung USB drivers and all that good stuff. Odin picked up the phone and all that, but a bit more looking around seemed to indicate that the usual Odin method of rooting wouldn't work on the latest version that I had.
So I downloaded the CASUAL installer and got that to run. It ran through the install, rebooted the phone, and then said it was waiting for Windows to recognize the device again so that it could continue with the install.
At that point, Windows informed me that a driver install had failed and the CASUAL install did not proceed any further, despite waiting a good 5-10 minutes.
Since doing this, the phone has had bizarre USB connection issues. Odin and Kies do not read the phone at all. Plugging the phone in brings up an additional drive for about two minutes with a Verizon Assistant Manager EXE, a USB Drivers EXE, and a couple other things, then it disappears.
The phone will often display a message informing me "Unable to find software on your PC that can recognize your device." This happens regardless of being in USB Debugging mode or not.
I've tried uninstalling and reinstalling several versions of Samsung's drivers as well as Kies. I also tried a factory reset on the phone itself, but these connectivity issues (and accompanying warning messages) persist.
Not sure how to proceed from here and would love a bit of help. Thanks!
Additional notes: All normal functions of the phone are working fine, and the computer DOES detect the phone as a "Samsung Android Device", but as stated Odin and Kies are not able to detect/connect with it.
Update: Messed with drivers a bit more and Odin will now pick up the phone again. When the phone disappears as a "drive" with install helper stuff, it reappears as a portable device, and I can browse the innards of the phone to put music and other stuff on it. CASUAL however still does not pick up the phone.

[Q] Problem With Trying To Use Casual

I'm Fairly New To The Android Concept, And I See Its A Little Bit More To Trying To Jailbreak It Vs. The iPhone, I'm Getting Stuck Using The Casual "NoYouVerizon" Concept Of The "One-Click" Method, But As Going On, I Don't Understand The Log's, I've Tried Searching For It Constantly, And I've Been At This For A Week Straight Now, I Need STEP by STEP Instructions On What To Do, Because I'm Reading Alot Of Different Things, And It's Not Really Helping Me At All, I Have A Verizon Samsung Galaxy Note 2, With Version 4.1.2 On It, and I Have *Correct Me If I'm Wrong* VRAMC3? If Thats The Right Thing. Please Somebody Help Me. Send Me A Message For My Contact Information. I Wanna Get This Done Pleasee!!!
theres the step by step guide
http://forum.xda-developers.com/showthread.php?t=2024207
One click root not working XDA. Someone needs to go back in and put the fix in for ERROR: No partition with identifier "60" exists in the specified PIT
Ive tried everything so far, even uninstalling the phone driver driver to allow samsung driver to reinstall, even manually installed the dev driver. I even tried to use odin3 to install via xda instructions. Odin can detect device if I just plug the phone in but if I put the phone in down load mode and connect, nothing. I checked device mgr and it shows the device in usb connections. WTF, XDA is verizon winning??????
Update:
Well I did discover after all this that I am rooted but I think that s all. When I plugged my phone into the computer Casuals usb showed in the Device Mgr screen instead of Samsung. To confirm I downloaded root checker from the play store and I am rooted via super user. Theres an issue though with putting the phone in download mode and odin detecting.
Update 2
Well it finally just worked and I was able to get odin to detect the phone while in download mode. I am now on root66 !! Help for others: Be persistent, I think it took time for my pc to accept and activate the changes IE: the casual driver replacing the samsung. It literally just happened after about 5 or 6 failed attempts of running the one click root. And it happened after a couple of samsung driver deletions. When the phone was plugged in, I went to device manager on the pc , usb devices and deleted the samsung drivers. I wound up doing this about 3 times. I restarted my computer after this to. Then I plugged the phone in again and there was casual usb controller appearing in device manager, replacing samsung. That was when I discovered I was rooted even though I had gotten the error message that started this post. Later, I went ahead and was able to install root66 by following the xda directions. wow......it was an all day affair but hopefully this will take some of the grey area out for others with this problem.
Thank you XDA for working to [email protected]^! this phone that verizon and google so graciously shoved up our #$% with a warm smile. The wi fi button for the notification bar is not available, I believe this is due to verizon when they put their stink on the phone. I would like to get that back if possible. Also the google search popping up when you plug the headset jack in is still there, but you can go into settings/task mgr/ all aps and scroll down to google search and disable it. The annoying pop up voice search hasnt showed up since I did this.

[Q] Windows, Odin and Kies wont see phone. Still some connection

Hey I'll spare the story but basically I've softbricked/bootlooped my S4 in a way I have many times and fixed easily, however now I can't. Basically I tried to launch a bad ROM; same one thats failed me multiple times, stupid to try again but I've fixed this exact problem with this ROM before many times by flashing back to stock with Odin. The problem is my family computer was recently reformatted so I lost Odin, Kies, Drivers, anything I was using before. I redownloaded all those things only now none of them are working properly... When I load up Odin like I always have with my phone in download mode of course, select the tar and run. Only now it recognized a device is connected and I get a COM:03 or whatever but when I hit run it basically goes nowhere and just says "all threads complete completed 0 failed 0" or sometimes "completed 0 failed 1" can someone tell me what these messages are trying to tell me? I though maybe it was cuz I hadn't installed Kies but Kies says my device isn't responding, which I was told could be cuz I have a custom bootloader and my phone needs be 100% for Kies to recognize it but I feel like it used to recognize it with the custom loader. Maybe not. I also tried updating the windows USB drivers but everything was up to date. My computer makes a noise when I plug my phone in and charges it but can't be viewed in windows file explorer. Maybe that's cuz I'm in download mode.
I don't understand why it isn't working but I think its my computer. It's software is the only variable thats changed, I'm doing everything exactly as I used to. I think one of the many components to make this work isn't lined up properly and I don't know what it could be at this point. And PLEASE no answers like "did you check the USB port?". . . yes of course I checked the USB port, yes I'm in download mode, yes my cable works, redownloaded every program in multiple firmware versions. those are the only answers I've been able to find on this topic and none of them get me anywhere.
Can someone tell me what is different on my computers end now? As I've said, I've done this successfully 100 times on my computer before doing exactly what I'm now it just isn't working after the harddrive reset so I assume something has to be wrong on the computers end.
I have a VZWJFLTE SCH-I5454 galaxy s4 and I'm trying to boot back to stock (4.4.2 NC5 found on galxys4root.com).

Categories

Resources