I have a Verizon Samsung Galaxy S4 that was rooted on the 4.3 build with the saferoot method (I think, it's been awhile). I had since installed Xposed framework and installer, etc. I unrooted with the supersu unroot method. Now I can't connect my phone via USB in either Ubuntu or Windows 7 (it shows unknown device). Another S4 shows up and installs drivers just fine on my computer, and my phone isn't recognized by other computers running windows. Basically, no matter what I've done with ADB and Windows drivers, my phone will not talk with my PC and I cannot connect to Odin. I've factory reset my phone, and I just want to be able to communicate via USB. At this point I'm torn between whether or not it is hardware or software, but I'm going to do whatever I can with the software before I look at new hardware.
I'm looking at taking some of the firmware I've found on XDA and installing that through the stock recovery with the SD card. `SCH-I545_VZW_1_20131023084910_v4vth34m5z_fac.zip` is the package I have.
My question: is this okay to just push this `.zip` via stock recovery? Is there anything else I need to do, like install other packages, etc?
You can try to install this, then I would FDR again and then flash the actual full Odin file! That should do the trick!!
Also if you haven't tried, our the phone into download mode before connecting to the computer...and use Windows 7
Sent from my SCH-I545 using Tapatalk
Okay, I tried to install several firmware versions, but since I don't have a custom recovery it still checks for a signature and they all failed. OTA update also failed, but I don't know why. I ordered a new usb board for the phone. If that doesn't fix it, I'm not sure what will. I'll update when it gets in.
Related
I am on DXLE6 and rooted with CF-Root. I can't seems to upgrade to DXLF6. OTA didn't find any updates (While normal unrooted can). I tried then using KIES but after downloading firmware (phone shows download screen), it ended with error of phone not recognized.
There is no issue with the driver or connectivity as it can detect the S3, prompt software update in KIES, download the new firmware and switch phone to download mode but it stops there.
Does it mean rooted S3 can't upgrade after rooted?
I have no solution for your problem, but all i can say is that yes, you can upgrade using kies when rooted (did that a couple days ago, too lazy to set stuff up again).
Question: do you use the original cable that came with the phone? Can imagine that this may cause the issue!
I can also confirm that when rooted software update couldnt find OTA update
I would suggest you to simply download and flash the ROM you would get from kies using ODIN. Guides and download links etc can be found using search function on XDA.
OngL said:
I am on DXLE6 and rooted with CF-Root. I can't seems to upgrade to DXLF6. OTA didn't find any updates (While normal unrooted can). I tried then using KIES but after downloading firmware (phone shows download screen), it ended with error of phone not recognized.
There is no issue with the driver or connectivity as it can detect the S3, prompt software update in KIES, download the new firmware and switch phone to download mode but it stops there.
Does it mean rooted S3 can't upgrade after rooted?
Click to expand...
Click to collapse
You can flash a newer version of stock firmware with CWM manager or with Mobile Odin Pro and still keep root. You don`t need Kies to upgrade.
gee2012 said:
You can flash a newer version of stock firmware with CWM manager or with Mobile Odin Pro and still keep root. You don`t need Kies to upgrade.
Click to expand...
Click to collapse
Yes, but as i said... Was too lazy to set everything up again (homescreens etc) plus the links sammobile.com provides i can only access using VPN, which means lousy slow downloads
Jack_Random said:
Yes, but as i said... Was too lazy to set everything up again (homescreens etc) plus the links sammobile.com provides i can only access using VPN, which means lousy slow downloads
Click to expand...
Click to collapse
You don`t have to do a full wipe when upgrading, just wipe cache/dalvik cache.
With the download i can`t help you, download it from another pc from a friend/family and copy it to a sd card !
Unzip the downloaded .rar file once to a .tar file.
Perhaps this is known issue, something is corrupted about the USB. It just suddenly stops working 'USB Not recognised'. Tried rebooting both didn't work.
Fortunately, I did TiB full backup before. I reset the phone to factory setting and it is recognised again by KIES. I have since upgraded to LF6.
Anyone knows why the issue with USB corrupted somehow (must be software setting not hardware as reset did it).
Hopefully someone can help me. So I rooted my device using the Casual method. Tried many times. It still errored out but when I looked on my phone SU was installed. The root worked but when I tried to go into recovery, it took me to Android recovery not TWRP. So being ignorant, I decided to install TWRP through the Goo Manager and when I tried to go into recovery, I got the "system software not authorized by vzw" error. Could only get into download mode. Decided to flash back to stock using Odin. Process went fine but it basically put my phone back to where it was without root (same apps, settings, etc.). I guess it didn't do a complete flash? So I decided to run casual again to re root/unlock bootloader. Tried it multiple times on win7 64bit computer. Even tried it on a 32bit VM. Came up with this error. Someone please help!
Today my Verizon Samsung Galaxy S4 updated through the Verizon network. Previous to the update I was able to use Foxfi without any problems but I now get error messages and cannot. I have tried the tether option and it will work for short periods of time but eventually will kick me off. I really have enjoyed using Foxfi or 1-click tether in the past with this phone and on my iPhone 4 and don't want to pay for garbage Time Warner.
After searching this site it seemed best to try and root my phone and try another app to allow Wifi. I downloaded Motochopper and ran it through the terminal on my Mac. However, after going through the process several times i saw a failure message when it tried to root, the Superuser would not update and after checking with Root Checker Basic the phone was not rooted. I also tried using SU Update Fixer to no avail.
I have also tried to use Heimdall which unexpectedly quits so I cannot switch to the prerelease kernel, try rooting again, then switching back to the stock kernel.
I would really appreciate any help on how to root using OSX.
To be clear, I have a Samsung Galaxy S4 on the Verizon network with unlimited data. Model SCH-I545, Version 4.2.2, Kernel 2595, Build MI1 and am in developer mode with USB Debugging active, Allowed mock locations, no SD card and nothing seems to work.
stachemonkey said:
Today my Verizon Samsung Galaxy S4 updated through the Verizon network. Previous to the update I was able to use Foxfi without any problems but I now get error messages and cannot. I have tried the tether option and it will work for short periods of time but eventually will kick me off. I really have enjoyed using Foxfi or 1-click tether in the past with this phone and on my iPhone 4 and don't want to pay for garbage Time Warner.
After searching this site it seemed best to try and root my phone and try another app to allow Wifi. I downloaded Motochopper and ran it through the terminal on my Mac. However, after going through the process several times i saw a failure message when it tried to root, the Superuser would not update and after checking with Root Checker Basic the phone was not rooted. I also tried using SU Update Fixer to no avail.
I have also tried to use Heimdall which unexpectedly quits so I cannot switch to the prerelease kernel, try rooting again, then switching back to the stock kernel.
I would really appreciate any help on how to root using OSX.
To be clear, I have a Samsung Galaxy S4 on the Verizon network with unlimited data. Model SCH-I545, Version 4.2.2, Kernel 2595, Build MI1 and am in developer mode with USB Debugging active, Allowed mock locations, no SD card and nothing seems to work.
Click to expand...
Click to collapse
You shouldn't be trying motochopper on MI1 - use the "Root de la Vega" method in the Android Development forum for this phone.
http://forum.xda-developers.com/showthread.php?t=2487142
That should work with Heimdall as well as ODIN.
k1mu said:
You shouldn't be trying motochopper on MI1 - use the "Root de la Vega" method in the Android Development forum for this phone.
http://forum.xda-developers.com/showthread.php?t=2487142
That should work with Heimdall as well as ODIN.
Click to expand...
Click to collapse
What he said. ^^^^^^^^^
I have an old NetBook with Windows 7 that I use for this kind of stuff.
I run Parallels 9 with a burrowed Win 7. Helps to use the system that developers are on and everything works perfectly. Every now and then I get usb issues but I just reinstall drivers and I'm good to go.
Has anyone flashed the Root de la Vega PDA image using Heimdall? Is there any risk of bricking a phone when flashing the PDA image (that is, if something goes wrong, can the stock image be reflashed or the root image be flashed using Odin instead)?
I'm new to developing and not too experienced. I attempted to root my phone, but was only successful with unlocking the Boot loader. When I attempted to download the new Kit-Kat update, my phone encountered a Firmware upgrade issue. Now in recovery mode, Kies 3 fails to connect nor recognize my phone.
cfales25 said:
I'm new to developing and not too experienced. I attempted to root my phone, but was only successful with unlocking the Boot loader. When I attempted to download the new Kit-Kat update, my phone encountered a Firmware upgrade issue. Now in recovery mode, Kies 3 fails to connect nor recognize my phone.
Click to expand...
Click to collapse
Bah. Kies sucks. Odin is a much better tool for updating / fixing things. What update were you on, as it is important to know the actual build version as well because there are often mini updates that keep the same android version but update other things that can cause a headache if not rooted or modified properly. Also, are you sure it was the bootloader that you unlocked? There is the Loki option and SafeStrap recovery, but not a way to unlock the bootloader unless you have a Dev Edition. I think you had to go to 4.3 before 4.4.2 too. What part did it get to before it failed and you got the error message? If you're lucky, it didn't actually do anything important before it failed, because then you can use Odin to install the original system update you did have then restart from there. If not, then you will need to go to 4.3, then 4.4.2. Once you update to 4.3 and above, your only options for custom roms are via the SafeStrap recovery which has some serious limitations.
es0tericcha0s said:
Bah. Kies sucks. Odin is a much better tool for updating / fixing things. What update were you on, as it is important to know the actual build version as well because there are often mini updates that keep the same android version but update other things that can cause a headache if not rooted or modified properly. Also, are you sure it was the bootloader that you unlocked? There is the Loki option and SafeStrap recovery, but not a way to unlock the bootloader unless you have a Dev Edition. I think you had to go to 4.3 before 4.4.2 too. What part did it get to before it failed and you got the error message? If you're lucky, it didn't actually do anything important before it failed, because then you can use Odin to install the original system update you did have then restart from there. If not, then you will need to go to 4.3, then 4.4.2. Once you update to 4.3 and above, your only options for custom roms are via the SafeStrap recovery which has some serious limitations.
Click to expand...
Click to collapse
I tried to gain root access awhile ago, it showed that my bootloader was unlocked, but I don't recall ever gaining root access, so I left it alone and figured I was just gonna wait for Kitkat. It's weird what is happening to my phone now. It just says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." After trying Kies Lite and normal both versions 1 & Kies 3, my phone won't even be read nor connect to Kies anymore. It won't show up in Odin. I have tried fully uninstalling all the Samsung programs on my computer then redownloading and installing them and still no luck. I really don't know what else to do. Should I just take my phone into Verizon and try my luck?
cfales25 said:
I tried to gain root access awhile ago, it showed that my bootloader was unlocked, but I don't recall ever gaining root access, so I left it alone and figured I was just gonna wait for Kitkat. It's weird what is happening to my phone now. It just says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." After trying Kies Lite and normal both versions 1 & Kies 3, my phone won't even be read nor connect to Kies anymore. It won't show up in Odin. I have tried fully uninstalling all the Samsung programs on my computer then redownloading and installing them and still no luck. I really don't know what else to do. Should I just take my phone into Verizon and try my luck?
Click to expand...
Click to collapse
The chance of finding someone at VZW who could fix this is pretty slim. But the open lock graphic that shows up when you first boot the phone does not imply the bootloader is unlocked on Galaxy phones, unlike say, a Nexus. It just means that something has been done to trip the custom binary check. If you tell me what update you were on, I can tell you how to fix your phone, or if you don't know, then you just need to follow this :
http://forum.xda-developers.com/showthread.php?t=2578209
It should show up in Odin. Not when it has the warning like that, but when you boot to Download Mode. I've bricked plenty of Galaxies like that and have been able to recover every one.
es0tericcha0s said:
The chance of finding someone at VZW who could fix this is pretty slim. But the open lock graphic that shows up when you first boot the phone does not imply the bootloader is unlocked on Galaxy phones, unlike say, a Nexus. It just means that something has been done to trip the custom binary check. If you tell me what update you were on, I can tell you how to fix your phone, or if you don't know, then you just need to follow this :
http://forum.xda-developers.com/showthread.php?t=2578209
It should show up in Odin. Not when it has the warning like that, but when you boot to Download Mode. I've bricked plenty of Galaxies like that and have been able to recover every one.
Click to expand...
Click to collapse
Ok. Thanks, man. I was running on 4.3. My laptop runs Ubuntu, is Odin compatible with this software?
cfales25 said:
Ok. Thanks, man. I was running on 4.3. My laptop runs Ubuntu, is Odin compatible with this software?
Click to expand...
Click to collapse
You'll either need to use Heimdall or the http://casual-dev.com/2014/01/04/jodin3-web-browser-or-offline-flashing-tool/
Hello! Sorry for my panic and sense of urgency, but I'm currently away for school and my lease is ending at the end of the month and I have no way to contact my parents, real estate agents, movers, or anything now. All I have is my phone and computer, and I haven't renewed my internet for the month so it should be shut off any day now as well.
But I was running Lollipop (OC1) and rooted my phone the other day with the terrible KingRoot. I attempted to use this app that was supposed to remove KingRoot and replace it with SuperUser but it only removed KingRoot - nothing else. So I lost root access, but still had all the KingRoot crap on my phone. Today a Verizon update appeared on my phone and I clicked install - I didn't think anything of it because it wasn't a major OS upgrade, just a small patch. Plus I thought it'd help remove KingRoot. Uh oh. I was wrong.
I installed the update, it went into recovery and then attempted to install. next thing I know all I see is a black screen. I tried pulling the battery and rebooting it, but I can't get passed the Samsung logo - it just goes to a black screen (but I believe it's still on, draining battery). If I try to boot into recovery it INSTANTLY starts auto-installing this update, which it of course always fails to do and gives me an error message.
My brother said I need to use 'ADB' but he's busy and can't email me much more information. I'm entirely lost, panicked, and scared! I need my phone working soon. I'm assuming theres no way to 'fix' my phone - so I'm just going to have to suck it up and realize I lost everything (man I wish I saved a lot of people I was texting as contacts *face palm*). What can I do now?
P.S. If I need to install a new ROM or whatnot over this, then can I do so with a pre-rooted Lollipop ROM? That way I don't have to risk using KingRoot ever- ever again. NOTE I NEED ROOT FOR WiFi TETHER! My internet is being shut off very soon, so to get by in the meantime I planned on using my phone and its tether.
No... You need internet access..
BUT... If you backed up everything to the external SD, then you can regain contacts..
Otherwise, Any attempt to fix it won't do anything...
ADB won't work on this phone either...
What you need to do is download a program called Odin, and a OC1 stock tar... That will recover your phone, but you will lose all contacts unless you had the Verizon contact thing...
I had the exact same experience as you yesterday... I had to put my phone in Download mode and start fresh with the Verizon Software Update Assistant. All I really cared about was my pictures, and they were on the external SD card. The other response about using ODIN to go back to OC1 works just as well... Best of luck!
Odin is your friend
Don't panic. You're contacts and other media of a similar nature are usually backed up regularly enough if you don't mess with the default sync settings of your stock rom. We can all agree Kingroot is a terrible way to root because of it's unnecessarily bloated bundle that it installs along with its super user app. To get your phone working you need to 'Odin' back to stock and from there you can root and install a custom rom. However your choices are very finite because of the new SELinux enforcing files on the OC1 build for the Verizon bootloader.
Step 1) Download Odin here ---> http://forum.xda-developers.com/gal...08-2013-odin-3-09-odin-1-85-versions-t2189539
Step 2) Download the stock OC1 Build ROM for the SCH-I545 (Verizon Galaxy S4) here ---> http://forum.xda-developers.com/galaxy-s4-verizon/development/odin-5-0-1-lollipop-oc1-t3174850
Step 3) Once the download has finished (use DownloadThemAll add-on in FireFox to boost download speed) load the tar.md5 file into Odin
using the AP button.
Step 4) Put your phone into download mode and plug it into your computer. Make sure the cables aren't loose and click start in Odin.
Step 5) Wait for the phone to reboot and for the com-slot in Odin to turn green (will say "PASS!!" when complete).
If you use KingRoot to root the phone then I suggest googling how to replace KingRoot with SuperSu and following the tutorial W0lfdroids website here ---> http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html