Related
Some people like sticking with stock, and there isn't a huge issue with that as the stock ROM is pretty good on the Note 2. However, if you want to be stock and remained unlocked, it's quite difficult to do as every new OTA re-locks the bootloader. It's also difficult to stay stock and keep a custom recovery as it will be over-written on every boot.
Now, users that want to stay unlocked and have custom recovery have an option available. This will require you to be fully stock, if you've modified anything in /system, it won't work. The only change you can have is root, but if you've modified build.prop, the kernel, or removed any files, you need to restore. If you have any doubts, flash the alternate restore file (after extracting it) from here.
There is one other requirement for this, and that is you need a custom recovery installed. If you've unlocked, you'll already have one. If not, you'll need to be rooted and you can use ROM manager or GooManager to flash a custom recovery (after going back to stock of course).
Now you have the pre-requisites down, stock rom and custom recovery, so all you need are the files. There are two updates available, so there are currently two files to flash to be on the latest OTA. You can download them below, and installation is as simple as downloading them to your phone and installing them via recovery. If you went back to stock VRALJB, you'll start with the VRALJB to VRALL4 file, then flash VRALL4 to VRAMC3 to get to the latest system. It should be fairly easy to figure out.
If you have any errors when flashing, odds are, you did something to files in /system and caused a problem. If that is the case, start over and flash the alternate restore file and proceed from there. I'll continue to update this as new OTAs are released then as well.
[size=+2]Downloads[/size]
VRALJB to VRALL4
VRALL4 to VRAMC3
Will this update baseband also?
Sent from my SCH-I605 using XDA Premium HD app
Digbob said:
Will this update baseband also?
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
It updates everything except for sboot.bin, tz.img (both bootloader files), and recovery.
hey thanks for this!
I'm on VRALJB stock, rooted and unlocked with CWM.
But I added Google Wallet working, and using a different kernel for overclock.
I tried the first update to LL4 just to see what it would say, and errored when applying the NFC.apk file, which is from the Wallet patch.
Not sure if it's easier for me to try and get the phone back to stock by restoring the original NFC files and kernel, and then try the LL4 update again, or just flash the phone with the rooted C3 ROM, but then would have to reinstall all my apps and settings.
FAUguy said:
I'm on VRALJB stock, rooted and unlocked with CWM.
But I added Google Wallet working, and using a different kernel for overclock.
I tried the first update to LL4 just to see what it would say, and errored when applying the NFC.apk file, which is from the Wallet patch.
Not sure if it's easier for me to try and get the phone back to stock by restoring the original NFC files and kernel, and then try the LL4 update again, or just flash the phone with the rooted C3 ROM, but then would have to reinstall all my apps and settings.
Click to expand...
Click to collapse
it says you must be on completely stock rooted with a custom recovery. being you have a custom kernel is most likely the problem. anything modified in /system will cause a fail. flash back to vraljb alternate restore file, then upgrade...or boot into recovery and flash beans mc3 stock rooted .zip rom
either way you will most likely need to wipe data to upgrade...atleast thats normallya prerequisite when changing bases.
FAUguy said:
I'm on VRALJB stock, rooted and unlocked with CWM.
But I added Google Wallet working, and using a different kernel for overclock.
I tried the first update to LL4 just to see what it would say, and errored when applying the NFC.apk file, which is from the Wallet patch.
Not sure if it's easier for me to try and get the phone back to stock by restoring the original NFC files and kernel, and then try the LL4 update again, or just flash the phone with the rooted C3 ROM, but then would have to reinstall all my apps and settings.
Click to expand...
Click to collapse
I said completely stock, and if you modified anything on /system it would fail, and you're surprised that it failed? You installed the Google Wallet hack, which modifies files on /system, and then you have a custom kernel as well, both of which will cause this to fail (as I already stated). Just be happy that the file checks were left in place and your phone still works at this point.
imnuts said:
I said completely stock, and if you modified anything on /system it would fail, and you're surprised that it failed? You installed the Google Wallet hack, which modifies files on /system, and then you have a custom kernel as well, both of which will cause this to fail (as I already stated). Just be happy that the file checks were left in place and your phone still works at this point.
Click to expand...
Click to collapse
I knew that it wouldn't work, but have tried it just to see which error message it would show, which it stopped when it got to the NFC.apk. I know it needed to be fully stock with nothing changed in the /system.
I was just asking, at this point, would it be easier (or better) to try and get it back to stock by replacing the modified files with the original ones and try again.....or flash the modified C3 rooted ROM. I think Adam is still trying the get his root/unlock for C3 to work right for everyone.
Hey thanks for this! This'll make my wife very happy. I thought I'd have to clean install beans stock rom. She just loves stock.
Sent from my Note II using Tapatalk 2
If you have to go all the way back to stock, why not just take all of the OTA updates and then root/unlock your phone?
I am unlocked with recovery running beans stock vramc3. I flashed the new modem afterwards. How is this different?
radio five said:
If you have to go all the way back to stock, why not just take all of the OTA updates and then root/unlock your phone?
Click to expand...
Click to collapse
OTA fails if you have a custom recovery.
Sent from my Note II using Tapatalk 2
If I deleted a couple of apps that were pre installed after rooting, will it fail? Its all stock otherwise, rooted, custom recovery.
FAUguy said:
I knew that it wouldn't work, but have tried it just to see which error message it would show, which it stopped when it got to the NFC.apk. I know it needed to be fully stock with nothing changed in the /system.
I was just asking, at this point, would it be easier (or better) to try and get it back to stock by replacing the modified files with the original ones and try again.....or flash the modified C3 rooted ROM. I think Adam is still trying the get his root/unlock for C3 to work right for everyone.
Click to expand...
Click to collapse
You're setting your phone up again either way.
radio five said:
If you have to go all the way back to stock, why not just take all of the OTA updates and then root/unlock your phone?
Click to expand...
Click to collapse
Not everyone is running a custom ROM. Some people are unlocked and on stock rooted with custom recovery and that's it. This is meant so they can stay up to date and remain on stock, rooted, and custom recovery.
TonikJDK said:
I am unlocked with recovery running beans stock vramc3. I flashed the new modem afterwards. How is this different?
Click to expand...
Click to collapse
This will be fully stock (minus recovery over-write). Beans did some other stuff to his ROM package from what I saw the last time I looked at the thread. Nothing major or groundbreaking, but it isn't as close to stock as this is.
pmazz850 said:
If I deleted a couple of apps that were pre installed after rooting, will it fail? Its all stock otherwise, rooted, custom recovery.
Click to expand...
Click to collapse
Really?
VRALL4 to VRAMC3
Update fails, verified hash matches;
E: Error in /sdcard/Download/vrall4_to_ramc3.zip
(status 7)
I don't think I changed anything on this phone...all I did was unlock bootloader/flash custom recovery TWRP 2.3.2.3, just to NAND & Wifi Tether, completely stock.
Systom said:
VRALL4 to VRAMC3
Update fails, verified hash matches;
E: Error in /sdcard/Download/vrall4_to_ramc3.zip
(status 7)
I don't think I changed anything on this phone...all I did was unlock bootloader/flash custom recovery TWRP 2.3.2.3, just to NAND & Wifi Tether, completely stock.
Click to expand...
Click to collapse
It did it to me too. I'm just going to clean flash beans stock.
Sent from my Note II using Tapatalk 2
Mac of York said:
It did it to me too. I'm just going to clean flash beans stock.
Sent from my Note II using Tapatalk 2
Click to expand...
Click to collapse
Yah, I think I'm gonna wipe/flash beans odex rom VRAMC3 & radio/restore data from NAND backup from VRALL4, hopefully it should be fine. Unless anyone would know otherwise?
Systom said:
VRALL4 to VRAMC3
Update fails, verified hash matches;
E: Error in /sdcard/Download/vrall4_to_ramc3.zip
(status 7)
I don't think I changed anything on this phone...all I did was unlock bootloader/flash custom recovery TWRP 2.3.2.3, just to NAND & Wifi Tether, completely stock.
Click to expand...
Click to collapse
What change for Wifi Tether?
imnuts said:
What change for Wifi Tether?
Click to expand...
Click to collapse
WifiTether_TrevE_Mod_11_22_2012.apk
I've been on stock rooted ROM (MDK) for longest time w/ CWM recovery. I decided I wanted to get back on the update track after this recent update came out and is already rooted. I defrosted all apps, unrooted the device with Voodoo OTA rootkeeper, and uninstalled SuperSU. I then flashed stock firmware with Odin as explained here: http://forum.xda-developers.com/showthread.php?t=2301259
This didn't work. I get an error during install every time. After this I noticed when going into recovery (now stock) it would have an error immediately but then went into recovery. It would not let me clear the cache (after searching this seems to be common.) So I then did factory reset multiple times (didn't help) and next flashed a stock firmware that wipes my data. This had the same results as before. Do I have a corrupt recovery of some kind? Shouldn't flashing the stock firmware fix this? Do I need to get a new phone? Help!
zregnier said:
I've been on stock rooted ROM (MDK) for longest time w/ CWM recovery. I decided I wanted to get back on the update track after this recent update came out and is already rooted. I defrosted all apps, unrooted the device with Voodoo OTA rootkeeper, and uninstalled SuperSU. I then flashed stock firmware with Odin as explained here: http://forum.xda-developers.com/showthread.php?t=2301259
This didn't work. I get an error during install every time. After this I noticed when going into recovery (now stock) it would have an error immediately but then went into recovery. It would not let me clear the cache (after searching this seems to be common.) So I then did factory reset multiple times (didn't help) and next flashed a stock firmware that wipes my data. This had the same results as before. Do I have a corrupt recovery of some kind? Shouldn't flashing the stock firmware fix this? Do I need to get a new phone? Help!
Click to expand...
Click to collapse
i dont think you can update with an unlocked recovery... if you have cwm you have an unlocked recovery and i dont think you can relock it.
also you dont need to update if you have cwm then all you need to do is flash a MI1 rom (once they come out) and youre good. there is NO reason you would need to ACTUALLY update. you can flash pretty much everything whilst still keeping unlocked recovery under actual MDK firmware but with MI1 (or ME7) rom kernel and radios.
zregnier said:
I've been on stock rooted ROM (MDK) for longest time w/ CWM recovery. I decided I wanted to get back on the update track after this recent update came out and is already rooted. I defrosted all apps, unrooted the device with Voodoo OTA rootkeeper, and uninstalled SuperSU. I then flashed stock firmware with Odin as explained here: http://forum.xda-developers.com/showthread.php?t=2301259
This didn't work. I get an error during install every time. After this I noticed when going into recovery (now stock) it would have an error immediately but then went into recovery. It would not let me clear the cache (after searching this seems to be common.) So I then did factory reset multiple times (didn't help) and next flashed a stock firmware that wipes my data. This had the same results as before. Do I have a corrupt recovery of some kind? Shouldn't flashing the stock firmware fix this? Do I need to get a new phone? Help!
Click to expand...
Click to collapse
I would try using the me7 factory image that wipes everything and then try the upgrade.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
---------- Post added at 09:21 PM ---------- Previous post was at 09:19 PM ----------
reinaldistic said:
i dont think you can update with an unlocked recovery... if you have cwm you have an unlocked recovery and i dont think you can relock it.
also you dont need to update if you have cwm then all you need to do is flash a MI1 rom (once they come out) and youre good. there is NO reason you would need to ACTUALLY update. you can flash pretty much everything whilst still keeping unlocked recovery under actual MDK firmware but with MI1 (or ME7) rom kernel and radios.
Click to expand...
Click to collapse
There is no unlocked bootloader on the s4 what allows the installation of custom recovery is the loki exploit and its reversible.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
hexitnow said:
[/COLOR]
There is no unlocked bootloader on the s4 what allows the installation of custom recovery is the loki exploit and its reversible.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Click to expand...
Click to collapse
Thus the word think but thanks for the info...
hook the guy up with the link for reversing loki then
reinaldistic said:
Thus the word think but thanks for the info...
hook the guy up with the link for reversing loki then
Click to expand...
Click to collapse
There is no link or post on it really. Its a patched recovery and boot image so when you odin back to a factory image they get replaced with the non patched versions
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
zregnier said:
I've been on stock rooted ROM (MDK) for longest time w/ CWM recovery. I decided I wanted to get back on the update track after this recent update came out and is already rooted. I defrosted all apps, unrooted the device with Voodoo OTA rootkeeper, and uninstalled SuperSU. I then flashed stock firmware with Odin as explained here: http://forum.xda-developers.com/showthread.php?t=2301259
This didn't work. I get an error during install every time. After this I noticed when going into recovery (now stock) it would have an error immediately but then went into recovery. It would not let me clear the cache (after searching this seems to be common.) So I then did factory reset multiple times (didn't help) and next flashed a stock firmware that wipes my data. This had the same results as before. Do I have a corrupt recovery of some kind? Shouldn't flashing the stock firmware fix this? Do I need to get a new phone? Help!
Click to expand...
Click to collapse
I to am having same exact problem but im on me7 and was safstrapped????????
The advice from @hexitnow worked! I downloaded ME7 image here http://forum.xda-developers.com/showthread.php?t=2357235
It worked fine then I took the latest OTA. Thanks guys!:good:
Quick Qestion
I have a quick question, and i dont want to make a who new thread about it. But since we already talkin about it on here, is it worth it to do this Verizon update?? I just did a Verizon update 2 days ago. And now to me i think it just aggitated me. My Email are different now. My delete button moved and it added more buttons. And my task manager seems a lil different. Cant seem to put my finger on it.. But its weird. What else has changed? Was it even worth doing an update?
Alright, I don't really know what happened or what I did, but something bad happened. To begin with, I rooted my phone with Stump and that went fine. After a month or so my phone started to lock itself out and sometimes not unlock. This bug, I don't know what it was, was probably from one of the roms. I uninstalled and removed all the roms and "unrooted" my phone. When I try to root my phone again, it sees the phone as unsupported. I did a hard reset/ I even used towelroot and that was bad. My phone also can't be used on my computer because it won't read it as an LG device with a driver. I've hard reset several times and tried many things. What I know for sure is that one rom or something didn't get removed. For example, I had an emoji switcher rom and I still have Google's emoji's instead of the default LG after reset. I can also lock my phone by double tapping the top left corner, which was another rom. This is all when "unrooted"
Can someone help me fix this? I don't have a warranty on the phone and SuperSU doesn't let me do anything on it.
Andorew said:
Alright, I don't really know what happened or what I did, but something bad happened. To begin with, I rooted my phone with Stump and that went fine. After a month or so my phone started to lock itself out and sometimes not unlock. This bug, I don't know what it was, was probably from one of the roms. I uninstalled and removed all the roms and "unrooted" my phone. When I try to root my phone again, it sees the phone as unsupported. I did a hard reset/ I even used towelroot and that was bad. My phone also can't be used on my computer because it won't read it as an LG device with a driver. I've hard reset several times and tried many things. What I know for sure is that one rom or something didn't get removed. For example, I had an emoji switcher rom and I still have Google's emoji's instead of the default LG after reset. I can also lock my phone by double tapping the top left corner, which was another rom. This is all when "unrooted"
Can someone help me fix this? I don't have a warranty on the phone and SuperSU doesn't let me do anything on it.
Click to expand...
Click to collapse
after removing root, you need to flash back to stock to get it working again with the exploit.
Andorew said:
Alright, I don't really know what happened or what I did, but something bad happened. To begin with, I rooted my phone with Stump and that went fine. After a month or so my phone started to lock itself out and sometimes not unlock. This bug, I don't know what it was, was probably from one of the roms. I uninstalled and removed all the roms and "unrooted" my phone. When I try to root my phone again, it sees the phone as unsupported. I did a hard reset/ I even used towelroot and that was bad. My phone also can't be used on my computer because it won't read it as an LG device with a driver. I've hard reset several times and tried many things. What I know for sure is that one rom or something didn't get removed. For example, I had an emoji switcher rom and I still have Google's emoji's instead of the default LG after reset. I can also lock my phone by double tapping the top left corner, which was another rom. This is all when "unrooted"
Can someone help me fix this? I don't have a warranty on the phone and SuperSU doesn't let me do anything on it.
Click to expand...
Click to collapse
You have to flash back to stock via the link below. Once you Unroot it is the only way of getting root back. Plus it is always nice to know how to return to stock before someone starts rooting, flashing roms etc... so when you get into this positions you already know the solution.
Edit: Make sure you do not take the System update after you flash back to 10b otherwise you will not be able to root any way.
http://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140
Jimi Mack said:
You have to flash back to stock via the link below. Once you Unroot it is the only way of getting root back. Plus it is always nice to know how to return to stock before someone starts rooting, flashing roms etc... so when you get into this positions you already know the solution.
Edit: Make sure you do not take the System update after you flash back to 10b otherwise you will not be able to root any way.
http://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140
Click to expand...
Click to collapse
Thanks for the Help. I got my phone back to stock. I don't actually plan on rerooting it for a while. But, do you know why my phone won't take the system update? I tried to and an error appeared.
Andorew said:
Thanks for the Help. I got my phone back to stock. I don't actually plan on rerooting it for a while. But, do you know why my phone won't take the system update? I tried to and an error appeared.
Click to expand...
Click to collapse
Did you get back to stock via the method I supplied? It has to be done that way and then check in your "about phone" and verify you are on "10b". From here the phone should take the 11c update.
Jimi Mack said:
Did you get back to stock via the method I supplied? It has to be done that way and then check in your "about phone" and verify you are on "10b". From here the phone should take the 11c update.
Click to expand...
Click to collapse
Yes, I have 10b, but it fails to update to 11c
Andorew said:
Yes, I have 10b, but it fails to update to 11c
Click to expand...
Click to collapse
Did you disable anything ?
If you returned to stock v10b via the .kdz file, you will not get the OTA because your are on an earlier version of v10b than the phone released with.
You are in a perfect situation to flash bumped TWRP recovery and then the v11c modem, system, and boot images, effectively updating you just like the OTA would have.
If you require the OTA to self-apply, then you need to restore using the .TOT method.
Sent from my VS985 4G using Tapatalk
trent999 said:
If you returned to stock v10b via the .kdz file, you will not get the OTA because your are on an earlier version of v10b than the phone released with.
You are in a perfect situation to flash bumped TWRP recovery and then the v11c modem, system, and boot images, effectively updating you just like the OTA would have.
If you require the OTA to self-apply, then you need to restore using the .TOT method.
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
How can I flash a newer version such as 11c(Or upcoming Android L)? Without .tot
You can't. You kdz back to keep from getting the update so you can root and bump and flash roms. You tot to get to the right version to take the update
Once L is released OTA, our noble developers will make it possible for us who have root and recovery to flash the OTA components safely, retaining root and custom recovery.
We hope.
Why would you want to take the current locked OTA?
If you TOT you can still root. Before you take the update.
If anyone is interested, I saw this posted today. A small OTA update released by AT&T today.
http://www.androidcentral.com/att-pushes-out-update-htc-one-m8-brings-android-444-and-hd-voice
scott500 said:
If anyone is interested, I saw this posted today. A small OTA update released by AT&T today.
http://www.androidcentral.com/att-pushes-out-update-htc-one-m8-brings-android-444-and-hd-voice
Click to expand...
Click to collapse
This is merely a rumor. The ATT link is to the old May 2014 update.
Pay no attention.
The link to the att sight yes is for old 1.58 build, does not mean there isnt an update coming...as its being reported with a build number by more and more sights, could just be a rumour but it could also be rolling out.
Well, they finally released the update today. Finally have 4.4.4. On my m8. Now to wait for lollipop
Does anybody know where the OTAPkg file gets downloaded to? I'm trying to preserve the file and not have to download it again and again after a fail update. Thanks.
Edit: n/m found it, it's under the FUMO folder within the internal SD.
Please save a copy. We need it for a custom rom
Sent from my HTC One_M8 using XDA Free mobile app
johnnyutah22 said:
Please save a copy. We need it for a custom rom
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
I'm lost. I installed the 4.4.4 OTA, installed the latest CM12 nightly, and now I have no cell service nor options to select/enter an apn. Under apn it states "access point names not available for this user" HElP?!
ALSO, what custom roms can I run using this 4.4.4 OTA?!
bford152 said:
I'm lost. I installed the 4.4.4 OTA, installed the latest CM12 nightly, and now I have no cell service nor options to select/enter an apn. Under apn it states "access point names not available for this user" HElP?!
ALSO, what custom roms can I run using this 4.4.4 OTA?!
Click to expand...
Click to collapse
I can't help you with CM12, but I just installed Viper One and it seems to work fine.
I updated to the 4.4.4 via OTA yesterday, and Viper installed without a hitch.
NB: Make a Nandroid Backup before flashing please.
Whats the best way to update my girlfriend's rooted M8? Currently running 4.4.2 rooted S-ON. Can she just take OTA and then will have to re-root?
I'm S-OFF on my phone so I haven't had to deal with this. Already updated my firmware months ago and have been running 4.4.4 roms.
Thanks!!
Downloading it now.
You'll have to re-flash stock recovery, take the OTA update, then restore twrp (or other custom recovery) and re-root.
Could someone help me with the OTA update. I'm on stock 4.4.2 rooted and s-off. I placed back all the at&t crap in systems and tried my best to restore everything back to stock even recovery. I'm still getting a red triangle approx like 1/4 the way during the update. What sucks is that I have to download the whole update file again and it's 800+megs versus the prior updates which were a lot smaller. It's just very time consuming and would like to find out the root of the issue is.
I've done so many mods on the phone like the HK mod and various other ones. I'm trying to think back now to see if there is anything else and now I'm stuck. I don't want to restore my stock nandroid cause I would have to install everything all over again which would suck big time. I uninstall the drivers for viper4android, xposed, and even reverted the host file back from adaway. I just feel like there might be something within the system files that isn't suppose to be there. I even got rid of the att boot logo and sound but I had restored that back to stock as well. Please help if you could. Thanks.
Also is there anyway to flash twrp without using a pc? I tried flashify but it doesn't seem to be working cause it would revert back to the fastboot no matter what.
Same situation here I think... stock rom (never changed it yet), rooted, unlocked, s-off. Downloaded OTA then realized I needed to flash original recovery back. Did that, now AT&T sw update is of course telling me to wait 24 hours to check again. Any way around that?
jeremyenos said:
Same situation here I think... stock rom (never changed it yet), rooted, unlocked, s-off. Downloaded OTA then realized I needed to flash original recovery back. Did that, now AT&T sw update is of course telling me to wait 24 hours to check again. Any way around that?
Click to expand...
Click to collapse
Yeah just manually change the date one day ahead and try it again. It might take a couple of secs for it to prompt that there is an update.
I just posted a pre-rooted ruu in the dev section.
Backup data in twrp to your ext sd. Flash ruu via sd card method. Flash twrp using the free app flashify. Reboot to twrp and restore data.
No pc required.
Just make sure you backup files on internal.
volcalstone said:
Could someone help me with the OTA update. I'm on stock 4.4.2 rooted and s-off. I placed back all the at&t crap in systems and tried my best to restore everything back to stock even recovery. I'm still getting a red triangle approx like 1/4 the way during the update. What sucks is that I have to download the whole update file again and it's 800+megs versus the prior updates which were a lot smaller. It's just very time consuming and would like to find out the root of the issue is.
I've done so many mods on the phone like the HK mod and various other ones. I'm trying to think back now to see if there is anything else and now I'm stuck. I don't want to restore my stock nandroid cause I would have to install everything all over again which would suck big time. I uninstall the drivers for viper4android, xposed, and even reverted the host file back from adaway. I just feel like there might be something within the system files that isn't suppose to be there. I even got rid of the att boot logo and sound but I had restored that back to stock as well. Please help if you could. Thanks.
Also is there anyway to flash twrp without using a pc? I tried flashify but it doesn't seem to be working cause it would revert back to the fastboot no matter what.
Click to expand...
Click to collapse
There's a boot loader flashable twrp in the dev section posted by jball
dottat said:
I just posted a pre-rooted ruu in the dev section.
Backup data in twrp to your ext sd. Flash ruu via sd card method. Flash twrp using the free app flashify. Reboot to twrp and restore data.
No pc required.
Just make sure you backup files on internal.
Click to expand...
Click to collapse
I noticed that flashify also will install CWM or Philz. Is your method specific to TWRP or can you use the others. The reason I ask is because I currently use Philz and would need that to restore my backup.
johnnyutah22 said:
I noticed that flashify also will install CWM or Philz. Is your method specific to TWRP or can you use the others. The reason I ask is because I currently use Philz and would need that to restore my backup.
Click to expand...
Click to collapse
You can flash whichever you use.
I thought I read where this update would include the EYE Experience. Did I read that wrong or do I just not know how to use my camera anymore?
volcalstone said:
Could someone help me with the OTA update. I'm on stock 4.4.2 rooted and s-off. I placed back all the at&t crap in systems and tried my best to restore everything back to stock even recovery. I'm still getting a red triangle approx like 1/4 the way during the update. What sucks is that I have to download the whole update file again and it's 800+megs versus the prior updates which were a lot smaller. It's just very time consuming and would like to find out the root of the issue is.
I've done so many mods on the phone like the HK mod and various other ones. I'm trying to think back now to see if there is anything else and now I'm stuck. I don't want to restore my stock nandroid cause I would have to install everything all over again which would suck big time. I uninstall the drivers for viper4android, xposed, and even reverted the host file back from adaway. I just feel like there might be something within the system files that isn't suppose to be there. I even got rid of the att boot logo and sound but I had restored that back to stock as well. Please help if you could. Thanks.
Click to expand...
Click to collapse
I don't think root changes are the issue; as typically it will fail before it even goes into recovery with a message that the system has been modified. It might just be a bad download.
Setting up your phone again is really not that bad a proposition; especially if you use Titanium to restore apps. And it will also restore your Xposed installer and modules. Using Titanium, I can easily be up and fully configured again in about a half hour after a factory reset or RUU. Although, of course this will depend on the amount of customization in settings, etc.
You might consider updating with the new RUU (relocking bootloader required if s-on). Not only will this bypass the OTA install issue you are having, but makes for a cleaner install. Yes, you will have to set the phone up again; and you will also need to backup any data on internal storage, as it will be wiped by RUU.
Okay here's my tale of woe..
I rooted my phone last year - but at some point - took an update and lost root.
Though the phone still displays the "custom" boot screen with the padlock.
I tried to take the Lollipop update through the OTA but it fails and I get the "laying on his back" failed Android dude...
The phone DID take the first update.
I have: wiped cache in recovery, wiped data and cache in download manager.
No luck.
I have tried loading the NC5 kernel back on (via Odin 3.09) - but that makes the phone 100% unstable...reboots every 3 minutes..no access to apps - they lock and reboot etc etc.
Loaded the NG6 kernel back on to re-stabilize the phone and tried to Kies the update.
Kies downloads the update then when it tries to apply it the phone boots into "download mode"
I have been advised to:
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.
Click to expand...
Click to collapse
and - of course that doesn't work. NC5 won't let the phone run long enough to take an update..
It has been said:
Try to flash the OC1 with the pit file
Click to expand...
Click to collapse
But I haven't found the stock OC1 file anywhere to even try and begin to get it loaded.
Honestly - I'm not even really concerned about rooting right now. I'd really just like to get the phone back to a stock configuration and kernel and lollipop.
Developer mode is enabled. Obviously both Kies and Odin talk to the phone with no problems.
Any ideas ?
Thanks, Dan
Get your phone to 4.4.2, use the verizon software upgrade assistant program preloaded on your phone to update. I had this exact same problem and that's how I got to 5.0.1
You WILL lose root. And there's no method to root 5.0 right now, and people have been saying that there might never be. You also won't be able to downgrade, or at least there's no method to do so at the moment, so you will be stuck with lollipop for a while, maybe forever.
Yes.
Maybe I need to clarify.
I do not care about root at this point. I just want to get the phone back to a stock state and take the Lollipop update.
I'm curious as to why I will never be able to update beyond Lollipop.
Doesn't matter I guess - the phone will have been replaced by then - but still...why ?
Thanks, Dan
CyrusKhane said:
Get your phone to 4.4.2, use the verizon software upgrade assistant program preloaded on your phone to update. I had this exact same problem and that's how I got to 5.0.1
You WILL lose root. And there's no method to root 5.0 right now, and people have been saying that there might never be. You also won't be able to downgrade, or at least there's no method to do so at the moment, so you will be stuck with lollipop for a while, maybe forever.
Click to expand...
Click to collapse
I've downloaded (3) different 4.4.2 Firmwares.
FNK1
FNC5 (No Wipe)
FNG6 (No Wipe)
Any opinion on which one is best ?
Did you download these manually or OTA? When I re-flashed the NC5 kernel, I received NG6 then NK1 then the 2-part Lollipop updates all OTA back-to-back.
Sent from my SCH-I545 using XDA Free mobile app
I would use the ng6. That's what I was running.
Rip Syntaxx said:
Did you download these manually or OTA? When I re-flashed the NC5 kernel, I received NG6 then NK1 then the 2-part Lollipop updates all OTA back-to-back.
Sent from my SCH-I545 using XDA Free mobile app
Click to expand...
Click to collapse
Manually - from these (XDA) forums.
danielzink said:
Manually - from these (XDA) forums.
Click to expand...
Click to collapse
Hmm... I'm not sure if it makes a difference to download OTA instead of manually. I would think it's worth a shot flashing NC5 (if it will let you downgrade) and using the software update feature to update OTA the rest of the way.
Sent from my SCH-I545 using XDA Free mobile app
Got it finally !
started out by flashing (FNG6 (No Wipe)) in Odin 3.09
That got me to regular boots with no "custom" screen showing the lock symbol.
Then I had to take OTA updates to FNK1 then the OTA preliminary Lollipop update then (OTA) finally Lollipop itself.
No root - but that's OK.
It took about an hour and a couple shutdowns to get things running smoothly but it's all good now.
Thanks everyone for their help.