I've looked around and seen that Kingroot PC is the way to go to root my VRUGOC1 galaxy s4.
However every time I plug my phone in to Kingroot I get a screen with a phone and a few sentences in Chinese on it.
The PC app doesn't even start trying to root, it just skips straight to that screen. I think that it's getting me to use the mobile app version given the phone picture, but if that's the case then I've found myself in a dilemma since the app tells me to use the Desktop version every time too.
How do I get the PC Kingroot to actually start rooting? Or can someone translate this for me?
I tried for a long time to get either of the Kingroot programs to work but both the PC and app failed. I quit trying a month or so back but tried again last night. It did the same thing you're talking about, it installed the app even though I was using the PC. It seemed like it could no longer use the PC version, only the app version so I don't know what's going on.
Do you reckon theres something different about our phones? Also did you ever try reflashing oc1?
I'm not sure if there's a difference. The one I currently have is a refurb, my last one the volume button was stuck in the up position. I have flashed OC1 several times but that didn't work either.
Same thing happening to me. It really sucks. I rooted fine less than a month ago and then in soft bricked and odined the "revert to oc1" from muniz's post. Now I can't root no matter what I try.
Sent from my SCH-I545 using Tapatalk
araucaria said:
I've looked around and seen that Kingroot PC is the way to go to root my VRUGOC1 galaxy s4.
However every time I plug my phone in to Kingroot I get a screen with a phone and a few sentences in Chinese on it.
The PC app doesn't even start trying to root, it just skips straight to that screen. I think that it's getting me to use the mobile app version given the phone picture, but if that's the case then I've found myself in a dilemma since the app tells me to use the Desktop version every time too.
How do I get the PC Kingroot to actually start rooting? Or can someone translate this for me?
Click to expand...
Click to collapse
Have you tried enabling USB Debugging under Developer Options?
I just rooted my S4 yesterday using Kingroot. I did clean flash OC1 through Odin and then did a Factory Data Reset through Recovery before rooting.
haza12d said:
Have you tried enabling USB Debugging under Developer Options?
I just rooted my S4 yesterday using Kingroot. I did clean flash OC1 through Odin and then did a Factory Data Reset through Recovery before rooting.
Click to expand...
Click to collapse
Kingroot would not have let me click the root button if I didn't enable it. I guess I forgot to mention that I clicked the button, haha. I will try re-flashing this weekend. Maybe the OTA I took messed something up?
Also, could I get the OC1 tar and the version of Odin that you used?
Does not work for me
Trying to use desktop version of KingRoot. Did clean flash of OC1 with odin, did factory reset after that then enable usb debugging. This is what I get.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Apk version does not work either. Please help me...I need root back.
beavis5706 said:
Trying to use desktop version of KingRoot. Did clean flash of OC1 with odin, did factory reset after that then enable usb debugging. This is what I get
Apk version does not work either. Please help me...I need root back.
Click to expand...
Click to collapse
hey beavis, I got the exact same thing as you did. and when I clicked the blue button it just launched kingroot on my phone, which doesnt work either. I read on another thread that kingroot suddenly stopped supporting the vzw sgs4 on oc1 for some reason. unfortunately I've given up, heh. I hate to say it but I believe root for our outdated phones on 5.0.1 is a lost cause. sorry.
Hey everyone, for those of you who downgraded back to OC1 from OF1 and lost root as well as the ability to root again via KINGROOT, I found a way to re-root.
I used WonderShare MobileGo one click root and I now have superuser again.
http://www.wondershare.com/mobile-phone/how-to-root-android.html
If you could figure out king root in all Chinese you should have no problem figuring this out.
I should mention this is a Windows application that you need to install. Connect your phone via USB with debugging enabled. The rest should be self explanatory.
Related
Just checked for update under settings and there was an update, but when the phone restarts and tries to install the update, it fails. Anyone else?
"Software Update: Install Interrupted - The software update could not be installed at this time."
Are you on a completely stock phone?
Sent from my SAMSUNG-SGH-I777 using Tapatalk
^yup, complete stock phone.
I checked for updates and there was one, downloaded, update failed.
Just bought my I777 from ATT and powered it up. Completely stock and experienced the same failure.
Same here. Completely stock. Tried my Girlfriends SGS2.....same deal.
Guess I wasn't the only one with the failure.. lol.. wonder what's the update about..
Mine failed also, completely stock as well. Out of curiosity what is this update include?
OTA updates probably aren't a good thing for you to try and do. They have been known to brick the og gs line. If there is an update you should try over Samsung Kies
Sent from my SAMSUNG-SGH-I777 using Tapatalk
CB650 Wolf said:
OTA updates probably aren't a good thing for you to try and do. They have been known to brick the og gs line. If there is an update you should try over Samsung Kies
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Click to expand...
Click to collapse
I just tried Kies. No update there.
Same thing here, just tried on my wifes phone and after restart says update failed.
Just talked to AT&T. The rep said there wasn't an update for the I-777 only for the Skyrocket.
Samsung also says there is no update.
Same old stuff........AT&T says talk to Samsung......Samsung says talk to AT&T.Should have know that's how it would go.
lol, so AT&T pushed the update to the wrong devices or something?
I think what happened was that the update application glitched out. Or maybe they're testing the machines for a bigger update. Maybe KK6 or whatever just came out.
It seems like everyone at at&t has left the original GS2 And just focused on the skyrocket.. (Noting that at&t announced the skyrocket would be updated to ICS but have yet to say anything on the original gs2..)
- At&t Galaxy S II Running
***ICScrewD V1.3***
Unless, my searches and searches have just missed over something completely hahah. Inform me if I'm wrong!
- At&t Galaxy S II Running
***ICScrewD V1.3***
It's just AT&T trying to secretly install CIQ on the phones.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
^Possibly xD
I ran into this problem too, but after 3 attempts (2 fails and 1 success) to install the update, I got it to work!
First of all, this update is NOT the SkyRocket's... after all, we are on the Orignal SGS2, and the SkyRocket and OSGS2 have COMPLETELY different model numbers.
Second of all, the update brings the phone to 2.3.6 and firmware I777UCKK6. If I am correct, 2.3.6 is also supposed to have better battery life
So, to get the update to work, here is what I did:
*NOTE* I too was 100% stock, but rooted and removed some of the bloatware on the phone. It seems that this may have caused the update failure.
1) Flash one of the kernels found on Entropy512's post on how to return to stock. It seems that whether you choose the rooted or non-rooted one does not matter (EX: I was already rooted and installed the non-rooted Kernel, but remained rooted afterwards). This will return all bloatware to the phone.
2) Wait 24Hrs OR change the date forward a day
3) look for an update again and install
4) Enjoy the update!
5) If rooted, then you will need to root again
6) Once rooted, you can remove the bloatware again. I recommend copying it to a separate folder so that future OTA updates can be done by simply copying the apk files back to system/apps.
I hope this works for everyone else too
spexwood said:
I ran into this problem too, but after 3 attempts (2 fails and 1 success) to install the update, I got it to work!
First of all, this update is NOT the SkyRocket's... after all, we are on the Orignal SGS2, and the SkyRocket and OSGS2 have COMPLETELY different model numbers.
Second of all, the update brings the phone to 2.3.6 and firmware I777UCKK6. If I am correct, 2.3.6 is also supposed to have better battery life
So, to get the update to work, here is what I did:
*NOTE* I too was 100% stock, but rooted and removed some of the bloatware on the phone. It seems that this may have caused the update failure.
1) Flash one of the kernels found on Entropy512's post on how to return to stock. It seems that whether you choose the rooted or non-rooted one does not matter (EX: I was already rooted and installed the non-rooted Kernel, but remained rooted afterwards). This will return all bloatware to the phone.
2) Wait 24Hrs OR change the date forward a day
3) look for an update again and install
4) Enjoy the update!
5) If rooted, then you will need to root again
6) Once rooted, you can remove the bloatware again. I recommend copying it to a separate folder so that future OTA updates can be done by simply copying the apk files back to system/apps.
I hope this works for everyone else too
Click to expand...
Click to collapse
Or just flash UnNamed 2.0
Well, yeah, but some prefer to stay on official stock firmwares... like myself lol.
Please help me pals, i'm so concerned.
I went on to root my LGMS769 using vroot, and i knew it was going to install it's own chinese version of Superuser. After investigating, i realize i rather have no root than this root...actually i don't even think it rooted my phone as i tried to run Titanium and it said it found no root...
So that was sketchy and now Idk what to do to undo everything vroot did!!! I want it OUT. A Factory didn't work, and it sucks i'd already done the software update after unboxing it today to the latest version v10e i think. Sigh!!! :crying:
lolilawl said:
Please help me pals, i'm so concerned.
I went on to root my LGMS769 using vroot, and i knew it was going to install it's own chinese version of Superuser. After investigating, i realize i rather have no root than this root...actually i don't even think it rooted my phone as i tried to run Titanium and it said it found no root...
So that was sketchy and now Idk what to do to undo everything vroot did!!! I want it OUT. A Factory didn't work, and it sucks i'd already done the software update after unboxing it today to the latest version v10e i think. Sigh!!! :crying:
Click to expand...
Click to collapse
I think there is also an option to unroot your device in vroot app. After rooting phone using vroot, if you again connect your phone to pc and run vroot, a button appears which have written ROOT starting with some chines signs on it, it might be unroot button. but i haven't tried it, so can't say weather it will work or not or what it will do.
But there is another method. Install SuperSU from play store. on its first run it will detect chines super user and will ask to uninstall it. simply uninstall chines super user, install latest super user binaries. Then install file manager from play store, tick on root explorer in setting, allow root excess, also tick on "mount system folders", then delete file named "su" located in /system/bin folder, then exit file manger and uninstall superuser reboot your phone and its done.
one another safe method is reflash factory rom.
i have used this method many times to unroot my phone, bt even then
:fingers-crossed:PLEASE TRY THIS AT YOUR OWN RISK, I AM NOT RESPONSIBLE IF SOMETHING GOES WORNG:fingers-crossed:
SuperSU : https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
File Manager : https://play.google.com/store/apps/details?id=com.rhmsoft.fm&hl=en
Thanks 4 ur reply!!
THANKS so much for your reply gdjindal!! :victory::victory:
I'm going to go on and invest my time in trying what you told me later and I will get back to the thread with the results. I hope for the best! :fingers-crossed::cyclops:
lolilawl said:
THANKS so much for your reply gdjindal!! :victory::victory:
I'm going to go on and invest my time in trying what you told me later and I will get back to the thread with the results. I hope for the best! :fingers-crossed::cyclops:
Click to expand...
Click to collapse
if it worked plz don't forget to press thanks button:good:
Remnants Vroot??
gdjindal said:
if it worked plz don't forget to press thanks button:good:
Click to expand...
Click to collapse
Surely i will not NOT Thank you if it didn't work!
1. Vroot in English for Windows did have an unroot option! But guess what, remember i told u my phone wasn't rooted by vroot to begin with even though they stated as yes, already rooted?? So i rooted again to rid out the probability of error on first root, ran root checker app and vroot really didn't root my phone although it was stating it did on PC. Smh.
But since awkwardly when i'd plug it in USB port vroot would say my phone had root privileges, whatever, i proceeded with their 'Unroot' option which removed the Superuser App, woosh, but it left one other app! Gross!!! I think this one is implanted when u connect ur phone to vroot before and after u root. This app was easy to remove with uninstall...but now i'm here worried and wondering about the possibility it left any other remnants in the background
2. I hit another post and downloaded 'root cleaner' here by LilTechPrincess - "VRoot Cleanup Tool - Easily replace VRoot with SuperSU"
with hopes that this would remove any remnants of vroot contact. It ran smoothly, except it didn't install SuperSU cause i'm not rooted but I just still feel insecure about whether or not vroot remnants r gone!!
How can I b sure all vroot remnants, like in the system for example, r gone!? I have not even assigned a google account to my phone due to worry.
@ gdjindal, I'm noob:angel: so is there any other way to have clean system than flashing my ROM fresh? LGMS7769.
Below some random screenshots: -2nd Pic, I cleared app data b4 uninstalling-
--------------------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
lolilawl said:
Please help me pals, i'm so concerned.
I went on to root my LGMS769 using vroot, and i knew it was going to install it's own chinese version of Superuser. After investigating, i realize i rather have no root than this root...actually i don't even think it rooted my phone as i tried to run Titanium and it said it found no root...
So that was sketchy and now Idk what to do to undo everything vroot did!!! I want it OUT. A Factory didn't work, and it sucks i'd already done the software update after unboxing it today to the latest version v10e i think. Sigh!!! :crying:
Click to expand...
Click to collapse
Authorize SuperSU from the Play Store with Vroot and use SuperSU to uninstall Vroot and perform a full unroot.
fora-mejora said:
Authorize SuperSU from the Play Store with Vroot and use SuperSU to uninstall Vroot and perform a full unroot.
Click to expand...
Click to collapse
Thanks for ur time fora-mejora!
I'd already 'unrooted' w vroot...(since it never rooted me to begin with, at least not officially' but that unroot with vroot did remove their apps except for the one the 'PC synching' would put in, that is for the program to link w ur phone...that i removed manually.
But i went on and did full unroot w superuser on my unrooted phone and it only uninstalled itself..no reboot and all..guessing it's because i have no root and no vroot blah blah to begin with.
I'm just curious about my system files now. Even unrooted, r they contaminated w vroot remnants?
--SO i just thought maybe installing a malware scanner like Dr. WEB would help me discover if vroot would leave any sketchy remnants. What ya think?
lolilawl said:
Thanks for ur time fora-mejora!
I'd already 'unrooted' w vroot...(since it never rooted me to begin with, at least not officially' but that unroot with vroot did remove their apps except for the one the 'PC synching' would put in, that is for the program to link w ur phone...that i removed manually.
But i went on and did full unroot w superuser on my unrooted phone and it only uninstalled itself..no reboot and all..guessing it's because i have no root and no vroot blah blah to begin with.
I'm just curious about my system files now. Even unrooted, r they contaminated w vroot remnants?
--SO i just thought maybe installing a malware scanner like Dr. WEB would help me discover if vroot would leave any sketchy remnants. What ya think?
Click to expand...
Click to collapse
If you are that concern, just perform an offline flash or install my themed 10e, wipe your data and be done with the issue.
Sent from my LGMS769 using XDA Premium 4 mobile app
I had received a refurbished phone from Verizon after I had to send my old phone. My phone was still under warranty so instead of taking the time to fix it I exchanged it. When I powered it on it was running on 24b with no problems. I was informed that there were OTA updates so I began to update it as usual. After I downloaded one of the updates and began installing the update, I saw something off. The installer looked completely different from my old phone (including others that I know that have the phone) and looked like it was custom. (I posted some pictures for some visual aid.) After the update completed, I checked the android version and it updated correctly using the OTA update. Looking through the settings, I found out that it is apparently modified before I even got the chance to root or make any Rom changes. Does anyone know anything about this particular installer? Also, should I even attempt to root the phone not knowing what to expect from it? I don't want it to get bricked after just receiving the phone. Thank you .
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That looks like the normal OTA installation screen to me. I don't recall if it was always that way through all the OTAs on the VS985, but it's been like that at least since 23A/B/C. I think it's always been basically like that though.
I did a lot of experimenting recently with flashing the 35B KDZ and taking the two following OTAs to get to 47A, that's why it's fresh in my mind.
As far as "Modified" status. There can be very minor things which manage to tweak the Official status into Modified. Even though I had recently flashed the 35B KDZ several times, I found that my status remained "Modified" both before and after taking the following OTAs. It was only after I restored to 10B via the TOT method (and 35B .DLL) and then re-flashed the 35B KDZ that my status remained "Official". The reason I had done so was actually because I was experiencing some very weird problems that flashing KDZs didn't solve, and it turns out flashing the 10B TOT solved all the issues. @xdabbeb explained and I've since noticed myself, that TOTs flash more partitions than KDZs, so they're really superior as a method to putting your phone back to a known good state.
Obviously we pay more attention to the details than Verizon does.
So I recommend you do the same that so you know for certain there's nothing wonky left behind, although I wouldn't overly worry about it either.
I happen to not have re-rooted since 47A came out just because I've been busy.
Edit: By the way, I had also run several experiments with using the Kingroot app to root 35B, 46A and 47A so it's very possible Kingroot was the cause of whatever corruption had occurred with my software that required flashing the TOT to solve.
roirraW "edor" ehT said:
That looks like the normal OTA installation screen to me. I don't recall if it was always that way through all the OTAs on the VS985, but it's been like that at least since 23A/B/C. I think it's always been basically like that though.
I did a lot of experimenting recently with flashing the 35B KDZ and taking the two following OTAs to get to 47A, that's why it's fresh in my mind.
As far as "Modified" status. There can be very minor things which manage to tweak the Official status into Modified. Even though I had recently flashed the 35B KDZ several times, I found that my status remained "Modified" both before and after taking the following OTAs. It was only after I restored to 10B via the TOT method (and 35B .DLL) and then re-flashed the 35B KDZ that my status remained "Official". The reason I had done so was actually because I was experiencing some very weird problems that flashing KDZs didn't solve, and it turns out flashing the 10B TOT solved all the issues. @xdabbeb explained and I've since noticed myself, that TOTs flash more partitions than KDZs, so they're really superior as a method to putting your phone back to a known good state.
Obviously we pay more attention to the details than Verizon does.
So I recommend you do the same that so you know for certain there's nothing wonky left behind, although I wouldn't overly worry about it either.
I happen to not have re-rooted since 47A came out just because I've been busy.
Edit: By the way, I had also run several experiments with using the Kingroot app to root 35B, 46A and 47A so it's very possible Kingroot was the cause of whatever corruption had occurred with my software that required flashing the TOT to solve.
Click to expand...
Click to collapse
I panicked when I saw the way it installed the update plus the modified status. My previous phone had more of a basic installation, I remember it would just be black with the Android logo in the middle. I even compared it with my father's phone and it was different from the refurbished one I just received. I'll look into doing a ToT flash when I can. Thank you for the quick response!
Supernic100 said:
I panicked when I saw the way it installed the update plus the modified status. My previous phone had more of a basic installation, I remember it would just be black with the Android logo in the middle. I even compared it with my father's phone and it was different from the refurbished one I just received. I'll look into doing a ToT flash when I can. Thank you for the quick response!
Click to expand...
Click to collapse
You're welcome! Good luck.
Hi everyone. I just got this update showing up on the phone. didn't install it cause I was on rooted of1 it looked like that its a new update that came out today. Anyone have some idea about it? I'll be uploading the update.zip file soon. my internet sucks and upload takes an hour X(...
Update: I took a look in the zip file, and looked at the metadata file under Meta-INF/com/android/. and it said
post-build=Verizon/jfltevzw/jfltevzw:5.0.1/LRX22C/I545VRSGPL1:user/release-keys
post-timestamp=1481263333
pre-build=Verizon/jfltevzw/jfltevzw:5.0.1/LRX22C/I545VRUGOF1:user/release-keys
pre-device=jfltevzw
so... im guessing that means the new update is still android 5.0.1?
update
heres the link for hte update zip
https://drive.google.com/open?id=0Bw35VbWkMyAhMzA0RUNYVC1sWDA
bangdosa said:
Hi everyone. I just got this update showing up on the phone. didn't install it cause I was on rooted of1 it looked like that its a new update that came out today. Anyone have some idea about it? I'll be uploading the update.zip file soon. my internet sucks and upload takes an hour X(...
Update: I took a look in the zip file, and looked at the metadata file under Meta-INF/com/android/. and it said
post-build=Verizon/jfltevzw/jfltevzw:5.0.1/LRX22C/I545VRSGPL1:user/release-keys
post-timestamp=1481263333
pre-build=Verizon/jfltevzw/jfltevzw:5.0.1/LRX22C/I545VRUGOF1:user/release-keys
pre-device=jfltevzw
so... im guessing that means the new update is still android 5.0.1?
Click to expand...
Click to collapse
Most likely just a security update.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Well ill try to hold off, because last time i took an OTA update i was stuck for months with no root and wifi hotspot.
Still Android 5.0.1 Lollipop
I completed the update this morning. This is still Android 5.0.1 Lollipop.
edboyd59 said:
I completed the update this morning. This is still Android 5.0.1 Lollipop.
Click to expand...
Click to collapse
Any noticeable differences?
Did you loose root after update?
bangdosa said:
Hi everyone. I just got this update showing up on the phone. didn't install it cause I was on rooted of1 it looked like that its a new update that came out today. Anyone have some idea about it? I'll be uploading the update.zip file soon. my internet sucks and upload takes an hour X(...
Update: I took a look in the zip file, and looked at the metadata file under Meta-INF/com/android/. and it said
post-build=Verizon/jfltevzw/jfltevzw:5.0.1/LRX22C/I545VRSGPL1:user/release-keys
post-timestamp=1481263333
pre-build=Verizon/jfltevzw/jfltevzw:5.0.1/LRX22C/I545VRUGOF1:user/release-keys
pre-device=jfltevzw
so... im guessing that means the new update is still android 5.0.1?
update
heres the link for hte update zip
https://drive.google.com/open?id=0Bw35VbWkMyAhMzA0RUNYVC1sWDA
Click to expand...
Click to collapse
bilgerryan said:
Most likely just a security update.
Click to expand...
Click to collapse
Is it just me? That's a new bootloader version isn't it? OF1 - PL1.
https://forum.xda-developers.com/verizon-galaxy-s5/general/update-pl1-potential-problem-t3528505
rooted device now bricked
I had rooted my device on OF1 using kingroot, and processed this update. I'm now bricked. It just hangs on the Samsung custom splash screen...
Any advice?
nic boles said:
I had rooted my device on OF1 using kingroot, and processed this update. I'm now bricked. It just hangs on the Samsung custom splash screen...
Any advice?
Click to expand...
Click to collapse
Flash stock with Odin. Follow my stickied thread in this Sub-Forum. If it updated your bootloader you might be hosed. Until the firmware is released.
Just so you know, you're supposed to unroot and then take the update
Ok, I'll try reflashing stock with odin.
I thought I did unroot it, using the kingroot instructions. I went into settings, told it to unroot, and restarted... then applied the update. Unless there was something else I was supposed to do?
nic boles said:
Ok, I'll try reflashing stock with odin.
I thought I did unroot it, using the kingroot instructions. I went into settings, told it to unroot, and restarted... then applied the update. Unless there was something else I was supposed to do?
Click to expand...
Click to collapse
Kingroot sets itself as a system app. Any alteration to the system partition and an OTA will Bork it.
Hey guys, I just got bricked by the OTA as well. 6 months or so ago I flashed the old kernel (OC1 I believe?) and then rooted with kingoroot or whatever. That was a mistake... all kinds of security notices and other weird sh*t that i didn't have time to deal with. So I used kingoroot to remove the root and flashed back OF1 or whatever was current. Still had the custom boot screen which was annoying but I thought I was back to normal... evidently that wasn't the case. Kind of salty right now because I probably just lost all of my data...I guess that's my lesson for getting a Samsung and attempting to make it usable. Currently I cannot get into safe or recovery mode: when i press the volume up and power it just takes me back to the "installing system update" and then "error!!". If anyone knows a way for me to get back in it would be greatly appreciated. If not, does anyone know which version firmware to install and where I could find it?
JoshTehSquash said:
Hey guys, I just got bricked by the OTA as well. 6 months or so ago I flashed the old kernel (OC1 I believe?) and then rooted with kingoroot or whatever. That was a mistake... all kinds of security notices and other weird sh*t that i didn't have time to deal with. So I used kingoroot to remove the root and flashed back OF1 or whatever was current. Still had the custom boot screen which was annoying but I thought I was back to normal... evidently that wasn't the case. Kind of salty right now because I probably just lost all of my data...I guess that's my lesson for getting a Samsung and attempting to make it usable. Currently I cannot get into safe or recovery mode: when i press the volume up and power it just takes me back to the "installing system update" and then "error!!". If anyone knows a way for me to get back in it would be greatly appreciated. If not, does anyone know which version firmware to install and where I could find it?
Click to expand...
Click to collapse
You need to hold volume down and power, then use Odin to reflash to OF1. That is what I just did.
sammobile(dot)com/firmwares/download/53590/I545VRUGOF1_I545VZWGOF1_VZW/
how to unroot?
I rooted using the wondershare method last year.
How do i un root so i can update it without bricking my device? Any help or links would be appreciated.
update: nic boles, that last post worked like a charm,,thanks!
I'll wait a while to try to root again.
foxfi seems to work and that's the most important thing to me.
Has anyone tried rooting on the new update?
bama9393 said:
Has anyone tried rooting on the new update?
Click to expand...
Click to collapse
Maybe I read it wrong, but I think the person that tried said they were bricked.
bilgerryan said:
Maybe I read it wrong, but I think the person that tried said they were bricked.
Click to expand...
Click to collapse
you have to unroot before the update
If you were rooted and made even the slightest change to /system, the update will hose you.
If you want the update, best to Odin back to OF1 stock first, then OTA.
bg260 said:
If you were rooted and made even the slightest change to /system, the update will hose you.
If you want the update, best to Odin back to OF1 stock first, then OTA.
Click to expand...
Click to collapse
Now can i root after the update with wonershare or kingroot?
edwardnizz said:
Now can i root after the update with wonershare or kingroot?
Click to expand...
Click to collapse
I wouldn't try it.
I mirrored the firmware here btw. Like 6 months ago.
Hi
I have the S4 Verizon OF1 and I want to install Stang5litre, but at the time of switching from Kingroot to superSU, it gives me many errors and I simply lose the Kingroot and that's it. I tried twice with the execution of a code in the terminal:
"sh /sdcard/mrw/root.sh"
And the first time (with the latest version of Kingroot) did not work, he simply made many mistakes and eliminated Kingroot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now that I did it for the last time with an earlier version of Kingroot and running the same code, it gave me a lot of errors and in the terminal they asked me if I wanted to cancel any action, press Enter, etc. until he stopped asking. When I restart the phone, I find SuperSu v2.49, but it does not update the binary files. Then I uninstalled it and wanted to go back to root with Kingroot, but it does not let me install it, I can not install the application.
I add that the phone seems to recognize the root, but since there is no application to authorize this permission, it does not. I say this because I have root applications, and when I open them they are waiting for root authorization, something that did not happen when the phone was not root
I hope someone helps me
You can either remove kingroot and all of its files manually using a root file explorer like root browser from the play store and then install superSU v2.49 (which is what I had to do) OR get the paid SuperSuMe app also from the play store which will automate everything and remove kingroot for you.
OF1, KingRoot 5.3 -> Super-SUme->root kept and KR gone
I'd soft-bricked my SCH-I545, then had to wipe and Odin-flash to stock to get it back. Then I used KingRoot 5.3 and got it rooted easily. But then of course, I really didn't like the extra mysterious apps and wanted to get back to SuperSU. Mind you, I'd rooted that Verizon-bugger the hard way the first time, and due to bad habits, had not taken notes and constructed my own tutorial along the way, as a good techie would. D'OH!
Carefully read the notes for Super-SUme... it will get it done for you if you can shell out the Google Play credit. (I did, to punish myself for the above laziness). Especially follow the advice on changing the default KR settings before running Super-SUme (The notes and advice are in the "read more" section on Google Play...)
https://forum.xda-developers.com/general/paid-software/supersu-please-t3110954
KingRoot is gone as far as I can tell, then It's Titanium Backup and multiple restore attempts and etc etc manually rebuilding what doesn't restore.... and you are back to your S4.
HTH
Well that's good to know. Wish I could have gone that route. I had to remove king root manually with root browser.
cnshht said:
I'd soft-bricked my SCH-I545, then had to wipe and Odin-flash to stock to get it back. Then I used KingRoot 5.3 and got it rooted easily. But then of course, I really didn't like the extra mysterious apps and wanted to get back to SuperSU. Mind you, I'd rooted that Verizon-bugger the hard way the first time, and due to bad habits, had not taken notes and constructed my own tutorial along the way, as a good techie would. D'OH!
Carefully read the notes for Super-SUme... it will get it done for you if you can shell out the Google Play credit. (I did, to punish myself for the above laziness). Especially follow the advice on changing the default KR settings before running Super-SUme (The notes and advice are in the "read more" section on Google Play...)
https://forum.xda-developers.com/general/paid-software/supersu-please-t3110954
KingRoot is gone as far as I can tell, then It's Titanium Backup and multiple restore attempts and etc etc manually rebuilding what doesn't restore.... and you are back to your S4.
HTH
Click to expand...
Click to collapse
Hi, I'm sorry I responded so late, but I didn't have time to check the notifications.
Ok, I used ODIN to install OF1 again, it took me 3 tries. But then it settled well and I did not have the problems that caused the change from Kingroot to SuperSu. Now the problem is that it will not let me install Kingroot. At the time of installing the application says "the application could not be installed"
I want to root with SuperSU because I want to install Stang5litre.
I have some experience in installing Roms, but I had never had a phone with the Bootloader blocked
Perhaps I misunderstood your OP. I didn't think your goal was to keep KingRoot. I thought you wanted a rooted SCH-I545 and to try stang5litre. I think if you want to have a good experience with stang5litre you want to have SuperSU on your phone as the root administrator, rather than KingRoot (and you realize, I hope, that you can only have one or the other, not both...right?)
The program I reported on (Super-SUme") first uses, then *removes* KingRoot, after you have installed KR onto a stock ROM. SuperSU, itself, cannot root your SCH-I545 from stock ROM, that takes KR (or another pathway) as a steppingstone. But then Super-SUme converts your SCH-I545 root to SuperSU, and in a noob-friendly way removes KR, with all it's wide-ranging permissions, from your phone. Download ("RootCheck" by Joey Krim as one example of) a rootchecker, and see if it can verify root.
If it verifies you have a root admin via SuperSU set up, and if you want the 'stang5litre' ROM pkg you should be ready to try flashing it. I believe the process (recommended elsewhere on XDA) uses "flashfire" (another app.) I did not go there. I only rooted my S4 and am keeping SuperSU on it as root administrator....
I might try out the 'stang someday. But for now I am debloating manually with Titanium Backup (Pro) "freeze" function.
--> If you successfully flashed a stock OF1 and immediately after that: You could not get KingRoot 5.3 to root your SCH-I545 ? (again, you can use a rootchecker app to verify root even if it's via KR)
...If this is where you are stalling, maybe someone else in the community has advice (?) All I have for you is a wish for good luck. There are other ways to root the SCH-I545 but none are easy. The trouble with the Verizon version of the S4, ultimately, is that the bootloader is booby-trapped, rather than locked. Some microcoded firmwarey lit'l landmines occasionally referred to as Q-fuses, I think.... If you try to flash your SCH-I545 to an earlier stock ROM (whether trying just to root, or if you haven't yet found out that you can't have an actual custom ROM)... ... if you try that, reports have woefully told, a "fuse" blows and then it's you, your soldering iron, and a hard brick. Get back on here with pics and detailed howto for a hand-soldered chip-swap and you will be a hero. (Not like me. I stand on the shoulders of giants, here, if I'm having a lucky day.)