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
Hey, I'm rooted and s-off, running (firmware, I think) 2.06.605.1 710RD. I've been ignoring the software update Verizon sent out a while ago by pressing the home button on my phone whenever the update popup appears, but I'd like to make it go away for good, and the best way to do that is to update.
The thing is, I'd like to do it without the hassle of unrooting and going back to s-on (if I even need to do that) to update, then getting s-off and root again. I heard it's possible if you flash a pre-rooted ROM of the update through a custom recovery, and I found a pre-rooted, updated rom a while ago on the forum, but now I can't find it. The update is called HTC6435LVW_2.07.605.1-2.06.605.1.
First of all, will this work?
Secondly, I'm going to keep searching for the 2.07 rom, but can anyone let me know if they have a link to the thread?
Thanks for your help.
Edit 2: To all who saw my first edit, I have confirmed that this is the TTY update, not the 4.2.2 update. However, I think the 4.2.2 update will be available after I flash the 2.07 update, so please let me know if flashing a pre-rooted rom still works for entire OS updates (and if there even is a pre-rooted rom for 4.2.2 yet).
Edit 3: Wow, I should have finished reading xda's article on the subject before I edited last time. Apparently there's already a pre-rooted rom for the 4.2.2 update, so that won't be a problem. Ok, that should be all.
I was searching to see if anyone else was having issues, but couldn't find any. I finally decided to turn the update off for the Verizon update, but it keeps saying unsuccessful and I'm assuming because the phone is rooted at the moment. Is there a way for me to install the mk2 update?
tuningmode said:
I was searching to see if anyone else was having issues, but couldn't find any. I finally decided to turn the update off for the Verizon update, but it keeps saying unsuccessful and I'm assuming because the phone is rooted at the moment. Is there a way for me to install the mk2 update?
Click to expand...
Click to collapse
Nope, it'll install even though you're rooted, but you need to restore anything you've modified before the OTA will work - or at least any files that the OTA is trying to upgrade.
k1mu said:
Nope, it'll install even though you're rooted, but you need to restore anything you've modified before the OTA will work - or at least any files that the OTA is trying to upgrade.
Click to expand...
Click to collapse
my guess is maybe the wifi tether, I was attempting to get it to work and there was a file or something to overwrite through a script from one of the threads I was reading. Could that be it?
tuningmode said:
my guess is maybe the wifi tether, I was attempting to get it to work and there was a file or something to overwrite through a script from one of the threads I was reading. Could that be it?
Click to expand...
Click to collapse
Very likely the tether - it changes the framework, doesn't it? That's very likely to be updated by the OTA.
Yeah, i have the same issues.. When i download the update ( I'm on MJ7 Rooted) it says please install, i click okay. It reboots it goes into the recovery, tries to update but shows a Error Android image, Restarts, then displays this message saying Error Phone couldn't update nothing was effected or something like that.What's the issue?! i wanna update / root because this message for the update pops up every damn day and it's so annoying! Please help me.
Mz8691 said:
Yeah, i have the same issues.. When i download the update ( I'm on MJ7 Rooted) it says please install, i click okay. It reboots it goes into the recovery, tries to update but shows a Error Android image, Restarts, then displays this message saying Error Phone couldn't update nothing was effected or something like that.What's the issue?! i wanna update / root because this message for the update pops up every damn day and it's so annoying! Please help me.
Click to expand...
Click to collapse
Flash the MJ7 no-wipe ROM that you'll find in the Android Development forum. That will restore all of the stock files that you should need (and also cause you to lose root.)Then, update to MK2 and re-root.
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.
Now Available!! 5.0.1!!!
Go get your lollipop ON!!!
Hopefully this will result in some bugs squashed with CM12. I am hoping for a better modem and better Bluetooth.
Queuing up downloads now, I have two of them pending for my device
are you able to capture the updates
I was able to capture the first update because im rooted. But i dont want to lose it if i update it. I hope the developers can find a way to keep root for the first update. if they can. I will happily capture the second update to get lollipop.
http://forum.xda-developers.com/showpost.php?p=60435732&postcount=54
dgutierrez04 said:
I was able to capture the first update because im rooted. But i dont want to lose it if i update it. I hope the developers can find a way to keep root for the first update. if they can. I will happily capture the second update to get lollipop.
http://forum.xda-developers.com/showpost.php?p=60435732&postcount=54
Click to expand...
Click to collapse
you could try taking it, then flashing the nc5 kernel through odin, and then (if someone's able to do this) get the kernel from nk4 and flash that
dgutierrez04 said:
I was able to capture the first update because im rooted. But i dont want to lose it if i update it. I hope the developers can find a way to keep root for the first update. if they can. I will happily capture the second update to get lollipop.
http://forum.xda-developers.com/showpost.php?p=60435732&postcount=54
Click to expand...
Click to collapse
How many updates are there? What does it mean 1st update? are there more updates?
meazz1 said:
How many updates are there? What does it mean 1st update? are there more updates?
Click to expand...
Click to collapse
apparently this is a 2-part update
part 1 is a build where the last three characters are NK4. this is a kitkat ROM that was likely used to prepare for lollipop
part 2 is the actual lollipop build, OC1. i think it's 5.0.1 but i'm seeing conflicting things from the internet
for some reason verizon likes doing major updates this way (i dont think they did it for jelly bean to kitkat though). but i've had a few of their phones, they've been doing two-part updates since the original galaxy s in 2010 lol
Hey everyone! Has anyone solved the mystery of the lollipop update fail? Seems alot of us are getting the first update without any issues, but the lollipop update is failing. It gives error 402, which one person at Vz told me was an error thrown due to having root. ( I don't have root ) Any suggestions appreciated!
gsmitchell said:
Hey everyone! Has anyone solved the mystery of the lollipop update fail? Seems alot of us are getting the first update without any issues, but the lollipop update is failing. It gives error 402, which one person at Vz told me was an error thrown due to having root. ( I don't have root ) Any suggestions appreciated!
Click to expand...
Click to collapse
My update is failing as well.
I've wiped cache in recovery, wiped data and cache in download manager...
Still fails.
I was rooted at one time - not rooted anymore.
I do still get the "custom" boot screen with the padlock though...
Can someone that has taken the OC1 ota update test to see if the 4.4.2 kernel has been blacklisted by:
1. Flash the I545_NK4_Stock_Kernel.tar.md5 using Odin. The device will not boot after flashing but we are just interested to see if the kernel will successfully flash.
2. To go back to normal flash the I545_OC1_Stock_Kernel.tar.md5 also in Odin.
This is the first test to determine if a downgrade workaround will be available for those that took the OC1 ota update.
muniz_ri said:
Can someone that has taken the OC1 ota update test to see if the 4.4.2 kernel has been blacklisted by:
1. Flash the I545_NK4_Stock_Kernel.tar.md5 using Odin. The device will not boot after flashing but we are just interested to see if the kernel will successfully flash.
2. To go back to normal flash the I545_OC1_Stock_Kernel.tar.md5 also in Odin.
This is the first test to determine if a downgrade workaround will be available for those that took the OC1 ota update.
Click to expand...
Click to collapse
Nope, it fails to flash
Here is the short log from the screen:
Code:
START [224, 1440]
SYS REV CHECK FAIL[K] : Refer 1 > Binary 0
SECURE MAGICCODE CHECK FAIL : boot
Is there a stock Odin TAR for this yet?
xdabens said:
Nope, it fails to flash
Here is the short log from the screen:
Code:
START [224, 1440]
SYS REV CHECK FAIL[K] : Refer 1 > Binary 0
SECURE MAGICCODE CHECK FAIL : boot
Click to expand...
Click to collapse
Not good. The 4.4.2 kernel has been blacklisted. Thx for testing.
Successful update (in two part harmony) yesterday. Stock system. Fox-Fi still works over Wi-Fi so I'm happy. No issues except 2nd update took a loooonngg time on the red Verizon screen. Make sure your battery is full or you are plugged in. No comments on battery life as I've been able to stay charged today. Getting used to it.
Hey everyone! If you getting the 402 Error, there is a thread that might have the fix. Go to the Error 402 when updating to Lolipop? thread. I am going to try it when I get home tonight.
dgutierrez04 said:
I was able to capture the first update because im rooted. But i dont want to lose it if i update it. I hope the developers can find a way to keep root for the first update. if they can. I will happily capture the second update to get lollipop.
http://forum.xda-developers.com/showpost.php?p=60435732&postcount=54
Click to expand...
Click to collapse
Thanks! Muniz_ri mentioned that you also captured the OC1 OTA package. I searched a lot but did not find it. Could you provide the link? Thanks again!
danielzink said:
My update is failing as well.
I've wiped cache in recovery, wiped data and cache in download manager...
Still fails.
I was rooted at one time - not rooted anymore.
I do still get the "custom" boot screen with the padlock though...
Click to expand...
Click to collapse
I had the same custom boot screen--even after unrooting. Tried using Triangle Away to reset the binary count, but the count was already at 0. So ultimately I had to re-flash the NC5 kernel via Odin to get things truly back to being recognized as stock.
Then updates started rolling in for NG6, then NK1. Finally the two-part update for Lollipop.
Sent from my SCH-I545 using XDA Free mobile app
People getting tthe 40 error did you at one time have safestrap installed? ??
---------- Post added at 09:42 AM ---------- Previous post was at 09:40 AM ----------
I've always found taking out sd card then a fresh Odin back to stock then doing my updates lead me to a flawless update process every time
Guys I'm on NC5 only rooted by towelroot what do I do please?!