Related
This is going to be simply a collection of links with important points...Please read ALL directions and comments carefully...as no one is responsible for any damage to your phone.
NOTE 1: IF YOU ARE UNROOTED AND ALREADY UPDATED WITH OTA, YOU CAN STILL USE THE PROCESSES BELOW TO ROOT AND FLASH RECOVERY.
>> Rooting Samsung Fascinate
>> Flashing Clockwork Recovery
NOTE 2: IF YOU ARE ROOTED AND WANT TO KEEP ROOT, DO NOT INSTALL VERIZON OTA UPDATE. WAIT FOR DEVELOPERS TO POST A ROOTED UPDATE.
If something went wrong and you did not have recovery installed, use Odin to restore system to stock >> Odin Restore files to get you to stock
If something went wrong, but you are still able to get into clockwork recovery >> Stock Nandroid Image
NOTE 3: IF YOU ARE ROOTED, HAVE LAGFIX AND APPS REMOVED, DO NOT INSTALL VERIZON OTA UPDATE. YOU WILL RUN INTO ISSUES. YOU NEED TO COMPLETELY GO BACK TO STOCK, THEN UPDATE. YOU WILL LOSE ROOT.
If you want to stop the OTA update notification, use this file which provides simple edits...but be careful as it may make further updates more difficult >> SCH-I500.DI01 Update
UPDATED:
OTA Update with Root and Busybox >> DH12 to DI01 update with root and busybox
Please post corrections and I will update the OP...I see too many people messing up their devices. Just want to help.
My path.
1) Stock with root mentioned in this dev section
2)restored CW backup
3)used CW to install the update mentioned in this thread.
No problems so far.
After reading this thread again I went to stock and stock kernel. Rooted and gold again.
I think that CPU Scale app causes the Fascinate to shut down, so if you use it and getting them.... remove the app or let me know if you fixed.
Thanks!!!
Now, here is something I didn't try yet. I am still stock (not rooted), ran the OTA...and with all people having issues, I am scared to root. I want to try but I think I will wait and see if anyone else does this.
tats_06 said:
This is going to be simply a collection of links with important points...
>> Rooting Samsung Fascinate
>> Flashing Clockwork Recovery
NOTE 1: IF YOU ARE ROOTED AND WANT TO KEEP ROOT, DO NOT INSTALL VERIZON OTA UPDATE. WAIT FOR DEVELOPERS TO POST A ROOTED UPDATE.
If something went wrong and you did not have recovery installed, use Odin to restore system to stock >> Odin Restore files to get you to stock
If something went wrong, but you are still able to get into clockwork recovery >> Stock Nandroid Image
NOTE 2: IF YOU ARE ROOTED, HAVE LAGFIX AND APPS REMOVED, DO NOT INSTALL VERIZON OTA UPDATE. YOU WILL RUN INTO ISSUES. YOU NEED TO COMPLETELY GO BACK TO STOCK, THEN UPDATE. YOU WILL LOSE ROOT.
If you don't care about root and want to install the OTA update manually >> SCH-I500.DI01 Update
Please post corrections and I will update the OP...I see too many people messing up their devices. Just want to help.
Click to expand...
Click to collapse
I thought the post about doing the OTA manually would allow you to keep root, seeing that it's a stripped down version.
Let me clarify that. If that's the case, I can update the OP.
Restored, updated and Rerooted
All is well. No problems so far.
Guys, pay attention to that update file. It is only updating modem.bin, and then updating your version number so you don't get nagged for an update. There are many more patches/updates in this fix than just modem.bin, and by doing only modem.bin you make it a bit more difficult on yourself to update down the road.
If that's all you want, go ahead and use it, but in no way did JT intend for this to get distributed as "this is what you should use if you have root" update.
Read before using, that's all I ask.
namebrandon said:
Guys, pay attention to that update file. It is only updating modem.bin, and then updating your version number so you don't get nagged for an update. There are many more patches/updates in this fix than just modem.bin, and by doing only modem.bin you make it a bit more difficult on yourself to update down the road.
If that's all you want, go ahead and use it, but in no way did JT intend for this to get distributed as "this is what you should use if you have root" update.
Read before using, that's all I ask.
Click to expand...
Click to collapse
Thanks for heads up...first post updated.
Bump.... Back to top till this gets stickied!
wasupwithuman said:
Bump.... Back to top till this gets stickied!
Click to expand...
Click to collapse
Thanks! I just reported it too to request for sticky.
Just thought I would menetion that phone is auto updating the software once it is downloaded to phone at night I woke up this morning and just reposed at work when I went to use wireless tether it wouldn't work looked at my phone and realized it had been auto updated time to go back to stock and reroot
Sent from my SCH-I500 using XDA App
azalvarez03 said:
Just thought I would menetion that phone is auto updating the software once it is downloaded to phone at night I woke up this morning and just reposed at work when I went to use wireless tether it wouldn't work looked at my phone and realized it had been auto updated time to go back to stock and reroot
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Do you have to go back to stock first before rooting? Or can you just run the root OVER the update? Thanks.
tats_06 said:
Do you have to go back to stock first before rooting? Or can you just run the root OVER the update? Thanks.
Click to expand...
Click to collapse
I don't think the update blocks root. you should be able to install the OTA as long as your not rooted, then once it is installed go ahead and root your device.
Ok...looks like root went thru...working on cwm recovery now.
OK, recovery installed successfully...running a backup right now.
Should I test restoring? Or should I assume I am safe?
Rooting after OTA update.
Can someone give a diffinative answer please. Can we root after the OTA update or does the update block root?
lukaro said:
Can someone give a diffinative answer please. Can we root after the OTA update or does the update block root?
Click to expand...
Click to collapse
If you have CWM installed, you always have root via adb, which means you can get your root apps working.
If you're not running CWM, I don't know. Someone who's tried rage.bin post-update could tell you.
lukaro said:
Can someone give a diffinative answer please. Can we root after the OTA update or does the update block root?
Click to expand...
Click to collapse
Yes you can root after update, I did it fine, but had to attempt it twice, the first try it hung, so had to do a battery pull, and then the second time it worked fine.
Nothing in the update seems worth it to return to stock (I've removed so many stock apps already.)
I'm having the Force Close loop issue. My CWR seems to be missing, as all I can access is Android system recovery <2e> with the options of:
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
Using the Odin method didn't work for me, on multiple tries. My SD card appears to be wiped clean and I can't enter debug mode.
Is there anything short of a miracle that I can do to fix my phone? I've seen a few posts with people saying they had similar problems as mine, but there was never and explanation of how or if they fixed there phone.
Thanks in advance
This morning I noticed I had an update available. I'm rooted with TWRP and SuperSU, by the way. After doing a little research first, I decided to download Voodoo OTA RootKeeper v2.0.3 just to be on the safe side. I then decided to let the update run it's course but it failed and took me to TWRP recovery. I was able to reboot to the regular system, but I've been getting the Verizon OTA update notification all day, but it just stays at the "busy" status bar without actually starting to download anything. When I try to access "Software Update" in the About phone menu under Settings, it says "Download interrupted. Software download will resume automatically." And then in a couple of hours, the whole process repeats.
I'm at a loss here. Is there a program that is slapping the OTA update down like TWRP? If so, how do I bypass it?
Thanks in advance.
Use this to update won't loose unlock or root
http://forum.xda-developers.com/showthread.php?t=2269736
TaPpEd from my TwEaKeD N2
jrbxx7 said:
Use this to update won't loose unlock or root
http://forum.xda-developers.com/showthread.php?t=2269736
TaPpEd from my TwEaKeD N2
Click to expand...
Click to collapse
good suggestion :good:
I just received my Galaxy s4 and activated the phone. I still have the old MDK build and not the new VRUAME7. The phone is trying to download the update and about 1/2 way there. I put the phone in airplane mode to stop the update.
I'd like to do the following:
1. root the phone
2. download ota rootkeeper
3. backup root
4. let the update proceed.
How can I stop the update from progressing. I'd like to turn the network back on after rooting to get a few programs that I use that require root access (that's my main reason for rooting. Not as much the ROMS etc).
Thanks.
UNCMo96 said:
I just received my Galaxy s4 and activated the phone. I still have the old MDK build and not the new VRUAME7. The phone is trying to download the update and about 1/2 way there. I put the phone in airplane mode to stop the update.
I'd like to do the following:
1. root the phone
2. download ota rootkeeper
3. backup root
4. let the update proceed.
How can I stop the update from progressing. I'd like to turn the network back on after rooting to get a few programs that I use that require root access (that's my main reason for rooting. Not as much the ROMS etc).
Thanks.
Click to expand...
Click to collapse
This question has been asked AND ANSWERED multiple times.
When it completes the download, you will be asked to approve the install. Tell it to defer the install for several hours, and use that time to root it and install OTA Rootkeeper. Then you can let the installation proceed.
k1mu said:
This question has been asked AND ANSWERED multiple times.
When it completes the download, you will be asked to approve the install. Tell it to defer the install for several hours, and use that time to root it and install OTA Rootkeeper. Then you can let the installation proceed.
Click to expand...
Click to collapse
My apologies. After posting I did some digging and found the answer. What can I say, I was happy when I saw my phone was pre-update and then panicked when I saw the update ongoing with no way to stop it.
Just got my phone today, it immediately starts to download update, so I'm just keeping all data networks disabled till I get things taken care of.
I just downloaded a OTA update on my S4, which I hoped was 4.4.4, but it looks like it is still Android 4.4.2. During the update, it says it was also updating KNOX, does anyone know what this update is, I was hoping it was the 4.4.4 upgrade. It did update KNOX to 2.0, so hopefully I can move my work stuff into KNOX now, and not have my basic phone subject to my work's locking policy.
The build number is KOT49H.I545VRUFNG6.
reckert said:
I just downloaded a OTA update on my S4, which I hoped was 4.4.4, but it looks like it is still Android 4.4.2. During the update, it says it was also updating KNOX, does anyone know what this update is, I was hoping it was the 4.4.4 upgrade. It did update KNOX to 2.0, so hopefully I can move my work stuff into KNOX now, and not have my basic phone subject to my work's locking policy.
The build number is KOT49H.I545VRUFNG6.
Click to expand...
Click to collapse
It's just small bug fixes for bluetooth connectivity and updates for KNOX 2.0.
Oh noze! Search is borken again.
How do you stop the ota updates
siouxhockey11 said:
How do you stop the ota updates
Click to expand...
Click to collapse
Download Titanium Backup and try to freeze SDM, you might have to purchase Titanium Backup Pro to freeze apps.
When it asks just click , No Thanks.. Update won't show again till you manually look for an update in settings.
I see the method for rooting the G6 involves the roll back to G5 and flashing G6. I've already towel rooted G5, will accepting the G6 OTA remove root for me because of the knox update? IOW if I want the LAG, is it better to flash G6 via odin, or can I just accept the OTA?
Thanks for your time!
BrianLayman said:
I see the method for rooting the G6 involves the roll back to G5 and flashing G6. I've already towel rooted G5, will accepting the G6 OTA remove root for me because of the knox update? IOW if I want the LAG, is it better to flash G6 via odin, or can I just accept the OTA?
Thanks for your time!
Click to expand...
Click to collapse
You will lose root if you flash NG6 on Odin or Accept the OTA update. The only way to keep root is to follow that flash back method if you want the update and keep root. My advice is not to updated at all. The NG6 update has issues with random reboots.
Fadtydawg said:
You will lose root if you flash NG6 on Odin or Accept the OTA update. The only way to keep root is to follow that flash back method if you want the update and keep root. My advice is not to updated at all. The NG6 update has issues with random reboots.
Click to expand...
Click to collapse
I would also advise not taking the NG6 update. I did and I went back to NC5. The random reboots seem to be unfixable and there really wasn't anything new and exciting with NG6, unless you need Knox 2.0 for some crazy reason! STAY WITH NC5!!!
michaely123 said:
Download Titanium Backup and try to freeze SDM, you might have to purchase Titanium Backup Pro to freeze apps.
Click to expand...
Click to collapse
I disabled SDM with 'No Bloat". Annoying notification for update is gone.
wulto said:
I disabled SDM with 'No Bloat". Annoying notification for update is gone.
Click to expand...
Click to collapse
Will this work for non-rooted phones?
dwmartin6341 said:
Will this work for non-rooted phones?
Click to expand...
Click to collapse
No u need a rooted phone.
Fadtydawg said:
When it asks just click , No Thanks.. Update won't show again till you manually look for an update in settings.
Click to expand...
Click to collapse
Say what? Mine is prompting me to install the update. It only gives me 2 choices "Install now" and "Install later", and if I choose later, it prompts me to pick a time for it to install. There is also a checkbox that says "Install automatically", which I am leaving unchecked. So, I think it's going to prompt me every day from now on, unless I root and then freeze something.
stuartv said:
Say what? Mine is prompting me to install the update. It only gives me 2 choices "Install now" and "Install later", and if I choose later, it prompts me to pick a time for it to install. There is also a checkbox that says "Install automatically", which I am leaving unchecked. So, I think it's going to prompt me every day from now on, unless I root and then freeze something.
Click to expand...
Click to collapse
It will just keep bugging you with the prompt everyday unless you root and freeze the apps.
With my wife's phone I went in to settings, application manager scrolled over to all & found SDM app & forced stopped it. Notification is now gone.
She IS NOT rooted.
I also have it auto hibernate using greenify so it does not come back.
Sent from my SCH-I545 using Tapatalk 2
So is this update buggy for those who were unrooted? Or just for those who were rooted and took the update?
I wonder if we were to unroot, take the update, then follow the root instructions if many of the problems go away?
Sent from my SCH-I545 using XDA Free mobile app
My wife's S4 is totally stock and she's had zero problems with the update. Took it earlier today.
After playing around with the update for a while, it looks like we have finally lost write access to the SD card like we were supposed to since the first Kit Kat update. I cannot write to the SD card (unrooted) with any file explorer, and my SMS backup app fails at writing to the SD card.
Zelmo88 said:
I would also advise not taking the NG6 update. I did and I went back to NC5. The random reboots seem to be unfixable and there really wasn't anything new and exciting with NG6, unless you need Knox 2.0 for some crazy reason! STAY WITH NC5!!!
Click to expand...
Click to collapse
I read your post..updated for the heck of it..FDR'd it...random rebooted after a a few minutes.
Its been 2 days so far, and the thing reboots 3-4 times a day.
I noticed that sometimes before it reboots, I'll unlock it, and it wont even register my security swipe..Then it reboots..Sometimes, if it does let me in, tapping on an icon does nothing...then it reboots...Other times, like this morning, it was just sitting on the end table, and it rebooted. Boy, you weren't kidding about the reboots.
BTW..All stock.
Here's what I did, worked.
I used the towel root method posted here (and other places I'm sure):
Ok...Forum won't let me post a link because I'm new. So Google "Root Verizon Galaxy S4 SCH-I545 on I545VRUFNG6 Firmware" and it will be the top choice from droid views.
Read the comments section too I posted the issue I was having then reinstalled super SU, flashed the NG6 Kernal and I've been good to go.
Hope it works out for you, I'm on NG6 with root, no errors, no reboots.
As per the title, I read something somewhere to the effect that from here on out, OTA updates will fail on most phones if they have been rooted, and this seems to be true for the Z Ultra GPE. So, what changed when I rooted my phone, and how do I undo it so that I can do the OTA update? I have looked through the forum, but nobody seems to answer it. I am rooted with Supersu using the Towelroot method. I am hoping to not have to unlock the bootloader or anything, just want to do this the official way. (I did backup my TA partition though).
jeraldjunkmail said:
As per the title, I read something somewhere to the effect that from here on out, OTA updates will fail on most phones if they have been rooted, and this seems to be true for the Z Ultra GPE. So, what changed when I rooted my phone, and how do I undo it so that I can do the OTA update? I have looked through the forum, but nobody seems to answer it. I am rooted with Supersu using the Towelroot method. I am hoping to not have to unlock the bootloader or anything, just want to do this the official way. (I did backup my TA partition though).
Click to expand...
Click to collapse
If your GPe is rooted only, the OTA should install just fine. If you made any system changes, you'll need to revert those though. I ran the OTA while I was rooted and didn't have any problems.
Visa Declined said:
If your GPe is rooted only, the OTA should install just fine. If you made any system changes, you'll need to revert those though. I ran the OTA while I was rooted and didn't have any problems.
Click to expand...
Click to collapse
Not so. See:
http://bgr.com/2014/11/14/android-5-0-lollipop-updates-and-root/
As mine is rooted, no dice, the OTA fails. So, how to unroot it so that the update takes?
jeraldjunkmail said:
Not so. See:
http://bgr.com/2014/11/14/android-5-0-lollipop-updates-and-root/
As mine is rooted, no dice, the OTA fails. So, how to unroot it so that the update takes?
Click to expand...
Click to collapse
well at the moment that doesn't effect the GPe, and may never. There will have to be a system image flashed to put the block device in a known state before the new way could ever be used, and if there is a system.img we can always flash that to get the OTA to work... no big deal I don't think.
jeraldjunkmail said:
Not so. See:
http://bgr.com/2014/11/14/android-5-0-lollipop-updates-and-root/
As mine is rooted, no dice, the OTA fails. So, how to unroot it so that the update takes?
Click to expand...
Click to collapse
First of all, BGR is a garbage site, and I wouldn't believe anything they say, ever. Second, that article is talking about avoiding root AFTER Lollipop is installed.
Having root will not cause the OTA to fail. If your OTA is failing, it's because you made a system change on your device.
*edit
If you were using Xposed, then that is more than likely why your OTA is failing.
What is Xposed? How would I check to see if it has affected my device? Only thing I did was Towelroot and running SuperSU. I may have done something to allow writing to the external SD card, but forget how I did that. I was intentionally trying to keep this phone basically stock so that it would easily update to Lolipop. I did a Titanium backup to the externalSD card and reset it to factory and the OTA update still fails though. I assume this was due to the fact that I rooted it. The bootloader is still unmodified, secureboot is still green - yes, lock state is locked. Only other thing I can think of is I installed an app that allowed me to set permissions by app (turn off location settings by app, etc) Sorry I can't give any more details than that...
jeraldjunkmail said:
I may have done something to allow writing to the external SD card, but forget how I did that.
Click to expand...
Click to collapse
jeraldjunkmail said:
Only other thing I can think of is I installed an app that allowed me to set permissions by app (turn off location settings by app, etc) Sorry I can't give any more details than that...
Click to expand...
Click to collapse
If you can't figure out what system change you made to your phone, just factory reset it, and run the OTA again. There was multiple people(me included) that took the OTA successfully, our phones were rooted and SuperSU was installed.
Visa Declined said:
If you can't figure out what system change you made to your phone, just factory reset it, and run the OTA again. There was multiple people(me included) that took the OTA successfully, our phones were rooted and SuperSU was installed.
Click to expand...
Click to collapse
As mentioned before, I factory reset this and wiped the cache from the stock recovery mode. Update won't take, stops shortly after it fails with "system update error". Since my last reset (been done a few times) it won't prompt me to get the OTA update, after my last reset last night. Any help is appreciated. Thanks!
{Damn thing won't work... (*&^&%^$$#}
jeraldjunkmail said:
As mentioned before, I factory reset this and wiped the cache from the stock recovery mode. Update won't take, stops shortly after it fails with "system update error". Since my last reset (been done a few times) it won't prompt me to get the OTA update, after my last reset last night. Any help is appreciated. Thanks!
{Damn thing won't work... (*&^&%^$$#}
Click to expand...
Click to collapse
The only fail-safe way I can see is to:
root
back up TA
unlock BL
hotboot custom kernel with recovery
flash 4.4.2
OTA to 4.4.3
OTA to 4.4.4
root and restore TA if you want a working camera
OTA to 5.0
blueether said:
The only fail-safe way I can see is to:
root
back up TA
unlock BL
hotboot custom kernel with recovery
flash 4.4.2
OTA to 4.4.3
OTA to 4.4.4
root and restore TA if you want a working camera
OTA to 5.0
Click to expand...
Click to collapse
As often happens, I sometimes see a solution I don't care to implement and begin to procrastinate. So, haven't looked at this problem for a while. I may have found the solution to my problems, but want to know if anyone has experience with it before proceeding. I re-installed superSU and went through the options. Buried in the options list is a box that offers "Full unroot, Cleanup for permanent unroot". What happens when I do this? does it just remove superSU or does it restore the phone back to factory status, before it was rooted? Thanks!
PS: @ blueether the solution is fine and I am sure it would work (I was going to go ahead with it until I saw that option in superSU), but have been hesitant to unlock the bootloader, etc, due to my unfamiliarity with hacking Sony products, and only want to do it as a last, final, no other option solution. Thanks for your help!
jeraldjunkmail said:
As often happens, I sometimes see a solution I don't care to implement and begin to procrastinate. So, haven't looked at this problem for a while. I may have found the solution to my problems, but want to know if anyone has experience with it before proceeding. I re-installed superSU and went through the options. Buried in the options list is a box that offers "Full unroot, Cleanup for permanent unroot". What happens when I do this? does it just remove superSU or does it restore the phone back to factory status, before it was rooted? Thanks!
PS: @ blueether the solution is fine and I am sure it would work (I was going to go ahead with it until I saw that option in superSU), but have been hesitant to unlock the bootloader, etc, due to my unfamiliarity with hacking Sony products, and only want to do it as a last, final, no other option solution. Thanks for your help!
Click to expand...
Click to collapse
That's fine and I take no offence at you not wanting to unlock the BL.
I haven't tried the full unroot option in supersu so I'm not sure what the outcome is. One of the other GPe users care to comment?
Well, turns out that the solution to unrooting the phone is to install superSU and than look inthe settings. It will offer you an option to completely uninstall root. It did what it says, and than you can check it with a check root app from the market. It reports that the phone is not rooted. Now the question is, will it pick up the OTA update... No luck with that after a clean factory reset, so not sure what to do next.
2 questions: If I unrooted my phone, and it says it is unrooted, is this true, in the fullest extent? Does towelroot do anything more than adding some permissions ans the superuser file?
If the phone won't pick up the OTA update, why? What went wrong?
Thanks!
jeraldjunkmail said:
Well, turns out that the solution to unrooting the phone is to install superSU and than look inthe settings. It will offer you an option to completely uninstall root. It did what it says, and than you can check it with a check root app from the market. It reports that the phone is not rooted. Now the question is, will it pick up the OTA update... No luck with that after a clean factory reset, so not sure what to do next.
2 questions: If I unrooted my phone, and it says it is unrooted, is this true, in the fullest extent? Does towelroot do anything more than adding some permissions ans the superuser file?
If the phone won't pick up the OTA update, why? What went wrong?
Thanks!
Click to expand...
Click to collapse
It sounds like the OTA is not being pushed at the moment/anymore. You could copy it to there the recovery can see it and manually install it
blueether said:
It sounds like the OTA is not being pushed at the moment/anymore. You could copy it to there the recovery can see it and manually install it
Click to expand...
Click to collapse
Can you point me inthe right direction for instructions on this process? Thanks!
Visa Declined said:
First of all, BGR is a garbage site, and I wouldn't believe anything they say, ever. Second, that article is talking about avoiding root AFTER Lollipop is installed.
Having root will not cause the OTA to fail. If your OTA is failing, it's because you made a system change on your device.
*edit
If you were using Xposed, then that is more than likely why your OTA is failing.
Click to expand...
Click to collapse
Your post is two years ago but i think you can help me,there is a new update for my phone and i am rooted i also have xposed installed so this mean i cannot update my sytem? Do i need to uninstall xposed? Im on stock rom and with TWRP recovery it would be a big help if you reply thanks.