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.
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.
Didn't see this posted anywhere else, seems to have just popped on my phone via the T-Mobile OTA update service. I can't take the update because I have modified the system image heavily and I am using 'Firefds Kit' to trick the system into thinking I am still running an official untouched image.
Figured I would let everybody know this has just come down the pike, hopefully we can get some more info and maybe even something flashable as this gets pushed out to more 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"
}
This OTA update is a 90MB update (at least for my device, which is on G900TUVU1GPE1) and upgrades G900TUVU1GPE1 to G900TUVS1GPG2 and G900TTMB1GPE1 to G900TTMB1GPG2.
I also got this update this morning.
As a side note, I was going back and forth between my about device screen and the update screen trying to compare my version to what the update says and after clicking "update later" 3 times the next time I clicked I only had the option to "update now". I wasn't able to hit the back button, home button, or recent apps button at all so I just restarted my phone to avoid having to do the update. Is this normal for all software updates? Is it also normal for it to state that you cannot downgrade after installing due to new security policies? Can this affect rooting my phone in the future?
Fixed Stagefright vulnerabilities
This OTA update fixed all the Stagefright vulnerabilities reported by Zimperium for my T-Mobile Galaxy S5 phone.
Follonwing are the reported vulnerabilities before the update. After the update there were no vulnerabilities found.
Critical
CVE-2016-2863 - Remote Code Execution vulnerability in Mediaserver
High
CVE-2016-2476 - Elevation of Privilege vulnerability in Mediaserver
CVE-2016-2477 - Elevation of Privilege vulnerability in Mediaserver
CVE-2016-2478 - Elevation of Privilege vulnerability in Mediaserver
CVE-2016-2479 - Elevation of Privilege vulnerability in Mediaserver
CVE-2016-2480 - Elevation of Privilege vulnerability in Mediaserver
CVE-2016-2481 - Elevation of Privilege vulnerability in Mediaserver
CVE-2016-2482 - Elevation of Privilege vulnerability in Mediaserver
CVE-2016-2483 - Elevation of Privilege vulnerability in Mediaserver
CVE-2016-2484 - Elevation of Privilege vulnerability in Mediaserver
CVE-2016-2485 - Elevation of Privilege vulnerability in Mediaserver
CVE-2016-2486 - Elevation of Privilege vulnerability in Mediaserver
CVE-2016-2487 - Elevation of Privilege vulnerability in Mediaserver
CVE-2016-2895 - Remote Denial of Service vulnerability in Mediaserver
Moderate
CVE-2016-2499 - Information Disclosure vulnerability in Mediaserver
Just got the update am rooted stock rom exposed installed how do i update with root
Hi Everyone, could you tell me which languages are available in this update ?
Thanks.
R.Simoes88 said:
Hi Everyone, could you tell me which languages are available in this update ?
Thanks.
Click to expand...
Click to collapse
Same ones as always
When I first got the message, I hit Update Now, and... bootloops. Completed the update process and just endless bootloops; at first, they went to the T-Mobile screen, but then cut out the drama and bombed right at initial Galaxy S5 screen. What upset me is that I was running stock; I just disabled some bloat with BK Package Disabler, nothing more. 'course, as with tradition, a long battery pull solved the problem. Seems to be working fine, and the update also seems to have solved that toolbox bug.
ShinySide said:
Same ones as always
Click to expand...
Click to collapse
without Portuguese (pt-BR)?
Never mind! As per tradition, a long battery pull solved the issue.
I wanted to confirm that T-Mobile/Samsung have gotten super aggressive with this update. After a certain amount of time, you won't be able to put off the update (no choices available other than 'Install Now', takes over the screen so you can't do anything else, and it disables the hardware buttons until you tap 'Install Now'.
A workaround, if you need it, (other than rebooting immediately) is to pull down the notification shade and either tap something in your shade, or tap and hold WiFi/Location/Bluetooth, etc. Once you have exited the update dialog, everything should be working as normal.
OK, for someone on gpe1 with twrp/systemless root and systemless exposed, what's the best way to update without losing anything? Preferably not going back to stock recovery...
Nateg900t said:
OK, for someone on gpe1 with twrp/systemless root and systemless exposed, what's the best way to update without losing anything? Preferably not going back to stock recovery...
Click to expand...
Click to collapse
Don't think it's possible unless you have the modem and bootloader tars, and I haven't seen them on the forums. Otherwise, I generally make a full backup and do a full wipe and factory reset. Odin the release, your data may still be intact if you didn't do a factory reset/wipe, root apps won't be functional, recovery will be stock.
Odin TWRP, flash SU, flash Xposed, Backup again at this point as your base. Restore data from previous backup... cross fingers and hope all goes as planned If not you have the base install to start restoring via TB or Play store.
mgp53 said:
Don't think it's possible unless you have the modem and bootloader tars, and I haven't seen them on the forums. Otherwise, I generally make a full backup and do a full wipe and factory reset. Odin the release, your data may still be intact if you didn't do a factory reset/wipe, root apps won't be functional, recovery will be stock.
Odin TWRP, flash SU, flash Xposed, Backup again at this point as your base. Restore data from previous backup... cross fingers and hope all goes as planned If not you have the base install to start restoring via TB or Play store.
Click to expand...
Click to collapse
Here:
ShinySide said:
Everything except system.img, cache.img, boot.img and recovery.img. So full upgrade beside those 4 items.
https://www.androidfilehost.com/?fid=24665509702141030
Click to expand...
Click to collapse
ShinySide said:
Here:
Click to expand...
Click to collapse
Wish I'd seen your post earlier.
Thanks
Man, they've gotten super aggressive with this update and I'm rooted. XDA gang: Before I do something stupid like losing my root, should I take the update or try to get around this?
I'm new to firmware/rom flashing arena. I had received the first Marshmallow update and then I accidently hit the updates option a few weeks later, well the most current update is saying that if I update I wont be able to downgrade. That tells me the if I'm not mistaken the bootloader is being locked like how AT&T and Verizon do it. I specifically bought a SM-G900T (T-Mobile USA KLTE) S5 to prevent from having the boot loader locked. Has anyone verified the bootloader is now locked on this latest update- aka has tried downgrading to a previous version because if you can't downgrade I'm not going to update and rather have the ability to customize my phone.
I am currently back to KitKat 4.4.2.
eidairaman1 said:
I'm new to firmware/rom flashing arena. I had received the first Marshmallow update and then I accidently hit the updates option a few weeks later, well the most current update is saying that if I update I wont be able to downgrade. That tells me the if I'm not mistaken the bootloader is being locked like how AT&T and Verizon do it. I specifically bought a SM-G900T (T-Mobile USA KLTE) S5 to prevent from having the boot loader locked. Has anyone verified the bootloader is now locked on this latest update- aka has tried downgrading to a previous version because if you can't downgrade I'm not going to update and rather have the ability to customize my phone.
I am currently back to KitKat 4.4.2.
Click to expand...
Click to collapse
Incorrect. The not being able to downgrade and locked bootloader are 2 completely different things.
You can still do anything you want. Only thing you can't do is odin back to the pervious version. However That does not include being able to flash an earlier version via a recovery.
Still can flash recoveries, kernels, roms, mods, etc etc. You just can't downgrade via odin or downgrade bootloaders. Anything with you can.
ShinySide said:
Incorrect. The not being able to downgrade and locked bootloader are 2 completely different things.
You can still do anything you want. Only thing you can't do is odin back to the pervious version. However That does not include being able to flash an earlier version via a recovery.
Still can flash recoveries, kernels, roms, mods, etc etc. You just can't downgrade via odin or downgrade bootloaders. Anything with you can.
Click to expand...
Click to collapse
yeah my S4 was locked down so i couldnt do anything to put in newer versions of Android after 5.1.1 let alone downgrade or put in custom roms.
I went ahead and put in 6.0.1 GPE1 (not latest) back into the phone.
I'm running android 5.0 baseband G900TUVU1DOB1 on my g900t stock and roooted because i don't wanna update and lose root. The update to marshmallow does intrigue me though cuz i hear it's a little faster. My question is, If i wan't marshmallow, do i have to update my phone to all the updates between 5.0 and 6.0.1? And also once i get to 6.0.1, is there a way to root it? BTW i am using the G900TUVS1FOJ4 recovery despite having the DOB1 baseband because it was the closest to stock the stock OB1 recovery i could find. I should still be able to update OTA right? If it turns out that i can't root 6.0.1 then i'll prolly just stay on 5.0 with my root.
I used to be on one of the 4.4.2 stock rooted roms without a custom recover so I didn't lose warranty coverage with Knox.
When GPE1 with 6.0.1 came out, I did a full reset, odin'd GPE1, then twrp recovery (flipping the Knox warranty bit, but at this point on a 2+ year old phone who cares), then flashed systemless root and systemless xposed from twrp recovery, then titanium backup restored my backed up apps.
It wasn't too bad, but now I have to restart about once or twice a day when things get really laggy... Like there is a memory leak or runaway process or something... Which was probably Samsung's plan to make me buy a new phone, in which case I'll probably go the nexus/pixel route since I'm tired of waiting forever for and then fighting each update to try and keep the same root functionality...
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.)