Root [Virgin Mobile] System Update will not take

[ZROE01]

Hey all,

I know there are threads out there regarding this, and I feel like I've tried everything in them so maybe it's worth starting my own.

I have 3 VM Galaxy Victory 4G phones I pay for, a while back used the odin method to root all of them.

Few weeks ago this stupid update appeared. All of them were on the most recent TWRP.

As many of you would know, if you try and take the update with TWRP it fails, I did not know this, but found it out after the fact.

So begins my quest to either take the damned update or get rid of the constant prompts.

In my googling of this issue I found many suggestions, people talking about going into the the /cache folder and renaming whatever update info was there(there is nothing in my /cache folder)

I've also put back on a stock recovery and tried taking the update(while rooted) it would reboot into recovery, begin installing and about halfway through fail with a red yield sign next to the android guy and immediately reboots.

I've tried using stock kernal, rom, recovery, and no root to take this update and the same thing happens.

I've tried in custom rom with root and titanium backup to freeze the system update app, but the damned thing re-appears.

Most of the time the update takes a day or two to re-appear but it ALWAYS does.

How in the hell can I take this stupid thing or get rid of it once and for all?

Could it be the stock rom/kernal/recovery package i have is not 100% stock? I have no idea where to get this, I found an MD5 installer someone uploaded in another thread claiming it was 100% stock and have been using that in TWRP to re-install everything and end up as far as I know 100% stock, but if that were true, I would imagine it would take.

Is there something in my installation process I'm goofing up? Have I done something to my phone to assure this cannot take?

Would immensely appreciate any info, advice, or help.

Thank you!

 

[scary alien]

Hey ZROE01, welcome to our AndroidForums!

First off, can you tell us who your carrier is? (we need to get your thread moved to the proper all-things-root area)

I don't own or have any personal knowledge about your device, but I might be able to shed some light on the typical OTA process:

- you pretty-much need a completely stock device; now, in reality, this isn't 100% true since what you really need is for the set of files that the OTA cross-checks to be stock and that isn't the entire list of files on your device, just a relatively small subset of it that would be patched or replaced by the OTA process

- that set of stock files does indeed include the kernel, recovery, and any system files (i.e., your ROM)

- an OTA .zip file contains a file called the updater-script file that cross-checks and does the actual OTA installation (patching and replacing); the first half of the OTA does the verification and if any of the files fail the cross-checking (i.e., to make sure your device's files match what the OTA expects), the OTA will fail and you'll see what you already have (i.e., about half-way through it fails and shows you the upended Android)

- an OTA is indeed typically downloaded to the /cache partition; it usually gets auto-deleted when an OTA installation either succeeds or fails, so that would/should account for why you can't see/find the OTA .zip file; you typically need to find and copy it prior to attempting the OTA installation

- you can see what issues the OTA installation had and what errors it reports by viewing the contents of your /cache/recovery/last_log file after the OTA installation has been attempted (either good or bad); that file should tell you at least the first issue it encountered that is causing your OTA to fail (and therefore what you would need to try to get fixed before re-attempting)

- I can't really point you to a specific method for stopping the OTA updating from downloading and nagging you--that's often a device/Android version/carrier version dependent thing and your mileage may vary

- if you are able to get the OTA to download and before installing it, you could download and run my OTA Verifier app (use the file selector to point to the OTA .zip file (look in /cache); it will tell you of all of the issues that it thinks or can identify that the OTA might also run in to; that would give you the opportunity to see hopefully all of the issues instead of having to tackle them one at a time; anyway, check the link in my signature if you are interested

I can't do much more that get you started since I don't have the same device, but hopefully that helps a bit.

Cheers and best of luck!

 

[ZROE01]

Wow that was very informative. I'm no windows/linux newb by any stretch but pretty much am with android.

First off, I'm on Virgin Mobile

So, I got your app, went and tried to look into the OTA update but the only thing I can do is "restart and install" it says it's downloaded and verified already.

The app tells me "directory 'cache' appears to be secured against browsing", on this phone at present I am not rooted, is this why?

Also, the /cache folder has absolutely no contents, never has in any of my attempts. What would cause this? I assume it can't be mostly related to my carrier and not an issue I perhaps caused in all my wiping of system/cache and re-installing roms/recoverys.

Thank you so much for anything you may know. I think i'll look to finding the actual OTA download somewhere, if I can, and then placing that in the cache folder via pc and trying to take the update when I get home from work.

 

[scary alien]

Wow that was very informative. I'm no windows/linux newb by any stretch but pretty much am with android.

First off, I'm on Virgin Mobile

Ah, thank you very much! I've moved your thread and that might get more relevant eyes reviewing your issues and eliciting helpful responses .

So, I got your app, went and tried to look into the OTA update but the only thing I can do is "restart and install" it says it's downloaded and verified already.

I think you'll need to re-root (if you still can). Then, when you return to this same point, just try to have a root file explorer already launched (i.e., Root Explorer or ES File Explorer in root browsing mode, etc.) so you can search the /cache folder for the OTA's .zip file or copy it off to the /sdcard, etc. for later later (i.e., pointing my app to it).

You should be able to hit the home button and ignore the "restart and install" prompt--it shouldn't try to install without your explicit consent (although my Moto Droid X did indeed auto-install an OTA back in 2010--I'm still honked about that, LOL ). That should allow you to anything else you need to prior to retrying the install.

The app tells me "directory 'cache' appears to be secured against browsing", on this phone at present I am not rooted, is this why?

Oh, yes! Sorry, you do typically need to be rooted to view anything in the /cache folder, so that explains that issue and the one below.

Also, the /cache folder has absolutely no contents, never has in any of my attempts. What would cause this? I assume it can't be mostly related to my carrier and not an issue I perhaps caused in all my wiping of system/cache and re-installing roms/recoverys.

Yeah, it's probably showing as empty since you're not presently rooted.

Thank you so much for anything you may know. I think i'll look to finding the actual OTA download somewhere, if I can, and then placing that in the cache folder via pc and trying to take the update when I get home from work.

No problem--I'm happy to help!

(apologies if my answers above were a bit disjointed: I hopped around and added thoughts and comments as they came to me .

If you happen to know the exact name of the OTA .zip file, I could download it from elsewhere and make a shell version of it for you (i.e., that just contains the updater-script file) that you could run my app against. It won't be able to evaluate any of the root-protected files though until you are re-rooted.

Cheers!

 

[Madbat]

Here is the update to flash in twrp if you are rooted http://www.mediafire.com/?a9emvh5q9kf0nem all of the assert props are removed so you don't lose root or twrp. This is thanks to nick_73. He made this no props.zip update. Once you are re-rooted and have twrp recovery again and on stock ROM, just flash in twrp and presto! Update.
Or if you want the original update, unmodified, to install as in the previous post., its here http://www.mediafire.com/?a9emvh5q9kf0nem
Good luck! I used the no props update on 2 rooted virgin mobile victories and it went flawlessly.
If you don't have access to a PC to reroot, towelroot works for the victory. Just run towelroot and then get SuperSU from play store. Then you can install twrp with flashify, also from play store.
Here is The_Victorian's guide for this method http://androidforums.com/showthread.php?p=6624488

 

[ZROE01]

Alien,

I re-rooted and got your app checking the file, there was 1 false statement and here is a copy/paste of the results for your reference since you obviously take much interest in these things!

--------------------------------------------
Failed expression at line #749:
apply_patch_check("EMMC:/dev/block/mmcblk0p7:5802240:3e8ba802eec79a2dcf175b0ada50ddd203355a9c:5843200:eba13a62d5c0f2192dcad85e1f43338ecc7c7863", "eba13a62d5c0f2192dcad85e1f43338ecc7c7863", "3e8ba802eec79a2dcf175b0ada50ddd203355a9c") || abort("EMMC:/dev/block/mmcblk0p7:5802240:3e8ba802eec79a2dcf175b0ada50ddd203355a9c:5843200:eba13a62d5c0f2192dcad85e1f43338ecc7c7863 has unexpected contents.");
[actual SHA1 of target file: 2dc63099332d12d3ee109a99f96c69154274847cactual SHA1 of target file: a71168fbebaff22327720ca9214ba453358df394]


Selected file to process:
/cache/1fa7a4e39714f2adf82d2ed4fdeeef35cbf9d9d5.USER_L300_SPT_MG5_to_ND4_Update_FWD-1.zip
================
Analysis
================
statements read: 1552
expressions processed: 393
true statements: 392
false statements: 1
inaccessible count: 0
- there were (1) failed expressions encountered (see details above)
Device information:
Device: goghvmu
Maker: samsung
Model: SPH-L300
Carrier: Virgin Mobile
Board: MSM8960
Name: goghvmu
Bootloader: L300VPAMG5
Android OS: 4.1.2
(the above text has been copied to the clipboard)


Interestingly, after re-root there's still nothing showing in ES explorer with hidden files showing but obviously the files are there

Madbat,



Your solution gave me hope, and seemed too easy, but made sense...until I rebooted into TWRP and attempted to install it from internal storage.


It failed with this text:


E:unknown File System: 'datamedia'
Updating partition details...
Installing '/sdcard/1fa7a4e39714f2adf82d2ed4fdee
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
assert failed: getprop("ro.product.device") == "
getprop("ro.build.product") == "goghvmu"
getprop("ro.product.device") == "goghvmu"
getprop("ro.build.product") == "goghvmu"
E:Error in /sdcard/1fa7a4e39714f2adf82d2ed4fdee
(Status 7)
Error flashing zip '/sdcard/1fa7a4e39714f2adf82d
Updating partition details


I assume it cut off some of the full update filename but I'm not sure where the logs are stored for this so I just typed it up.


Does this spell out any clear indicator as to whats wrong?


Thank you!

Edit: I tried out ultra file explorer, was able to navigate to the cache folder and indeed see the same update as madbat had linked me(at least the name is the same) and tried deleting it/renaming it to see if perhaps having it in the cache was conflicting with trying to apply the downloaded update but it will not go away, even with being granted SU. What a stubborn thing...

Edit Edit: a 3rd file explorer let me delete the old update in the cache folder, rebooted, tried, same thing. However, interestingly enough now after trying to take the new update and restart, it won't restart and the update won't actually install and appear in cache. At this point I'm gonna walk away before I get to a point of no return(assuming that's possible) until you guru's can point me in the right direction.

 

[Madbat]

I apologize,I linked the unmodified update in both my links by mistake. This is the twrp flashable update for mg5 to nd4 http://link.tapatalk.com/api/click?...RP.zip&subId=50907a3f9889b7ea9ce755f67a05fb37
Sorry about that. It was late and I was doing it on my nexus 7 and linked the same file in both links.
This one really should work for you. If it doesn't, I have a clean mg5 backup you can use to go truly stock before flashing update. But I'm pretty sure this one will work.

 

[scary alien]

ZROE01,

Cool you were able to find the OTA's .zip file (1fa7a4e39714f2adf82d2ed4fdeeef35cbf9d9d5.USER_L300_SPT_MG5_to_ND4_Update_FWD-1.zip) :thumbup: .

I'm guessing you might not have turned on the Root Explorer feature/option in ES File Explorer (they've vastly complicated that app and it's hard to find the option/setting to turn that on--it used to be a very nice, simple interface, but have really bloated it up over the last couple of years--same deal as Astro File Explorer--those both used to be my favorites ).

Anyway, from the OTA Verifier output, I'm guessing that /dev/block/mmcblk0p7 might be your recovery partition? That would explain the warning if you've got TWRP installed.

I would also caution that flashing a .zip file that has any of it's asserts or cross-checks disabled is a bit dangerous unless you specifically know what is being bypassed / ignored. I.e., at the very least, the ro.build.product and ro.build.device checks should never be removed to keep folks from flashing a .zip on the wrong device.

If you can verify that /dev/block/mmcblk0p7 is indeed your recovery partition and you're able to re-flash the stock recovery, you should be able re-run OTA Verifier, make sure it comes up clean, and then re-try installing the stock OTA.

I'll have to defer to Madbat's expertise for possible next steps .

Cheers!

 

[Madbat]

I can say 100% that the file is for the virgin mobile victory. I know there are dangers removing all assert checks. Make sure your build and baseband both end in mg5 before installing this update.

 

[ZROE01]

I reflashed the new link Madbat provided, but it failed again.

I found where to copy TWRP details to a log so I have that to lend to the conversation(learning so much!)

[FONT=&quot]Installing '/sdcard/Download/MG5_to_ND4_Update_TWRP.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Register_libbootloader_updater Qcom msm8960
Verifying current system...
failed to stat "EMMC:/dev/block/mmcblk0p1:44402432:549c6acab7d5fe026fdb1ca2d2700e76a79f75ec:44697344:cbec286600b2e7129b25a6a0ee268ef30da5c1f8": No such file or directory
partition read matched size 44402432 sha 549c6acab7d5fe026fdb1ca2d2700e76a79f75ec
failed to stat "EMMC:/dev/block/mmcblk0p7:5802240:3e8ba802eec79a2dcf175b0ada50ddd203355a9c:5843200:eba13a62d5c0f2192dcad85e1f43338ecc7c7863": No such file or directory
contents of partition "/dev/block/mmcblk0p7" didn't match EMMC:/dev/block/mmcblk0p7:5802240:3e8ba802eec79a2dcf175b0ada50ddd203355a9c:5843200:eba13a62d5c0f2192dcad85e1f43338ecc7c7863
file "EMMC:/dev/block/mmcblk0p7:5802240:3e8ba802eec79a2dcf175b0ada50ddd203355a9c:5843200:eba13a62d5c0f2192dcad85e1f43338ecc7c7863" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: "EMMC:/dev/block/mmcblk0p7:5802240:3e8ba802eec79a2dcf175b0ada50ddd203355a9c:5843200:eba13a62d5c0f2192dcad85e1f43338ecc7c7863" has unexpected contents.
"EMMC:/dev/block/mmcblk0p7:5802240:3e8ba802eec79a2dcf175b0ada50ddd203355a9c:5843200:eba13a62d5c0f2192dcad85e1f43338ecc7c7863" has unexpected contents.
E:Error in /sdcard/Download/MG5_to_ND4_Update_TWRP.zip
(Status 7)
Error flashing zip '/sdcard/Download/MG5_to_ND4_Update_TWRP.zip'
Updating partition details...
Iata backup size is 508MB, size: 1870MB, used: 791MB, free: 1108MB, in data/media: 282MB.
[/FONT]


Alien,

What is this [FONT=&quot]/dev/block/mmcblk0p7 that you're talking about verifying? Something related to TWRP? You say reload the stock recovery then essentially attempt to flash the newest zip provided by madbat from there?

I think I answered that while spelling it out...will update soon

Edit:

Attempted to verify the newest update from Madbat and got this -

[/FONT]
--------------------------------------------
Failed expression at line #743:
apply_patch_check("EMMC:/dev/block/mmcblk0p1:44402432:549c6acab7d5fe026fdb1ca2d2700e76a79f75ec:44697344:cbec286600b2e7129b25a6a0ee268ef30da5c1f8", "cbec286600b2e7129b25a6a0ee268ef30da5c1f8", "549c6acab7d5fe026fdb1ca2d2700e76a79f75ec") || abort("EMMC:/dev/block/mmcblk0p1:44402432:549c6acab7d5fe026fdb1ca2d2700e76a79f75ec:44697344:cbec286600b2e7129b25a6a0ee268ef30da5c1f8 has unexpected contents.");
[not rooted--cannot access protected file/partition]
--------------------------------------------
Failed expression at line #745:
apply_patch_check("EMMC:/dev/block/mmcblk0p7:5802240:3e8ba802eec79a2dcf175b0ada50ddd203355a9c:5843200:eba13a62d5c0f2192dcad85e1f43338ecc7c7863", "eba13a62d5c0f2192dcad85e1f43338ecc7c7863", "3e8ba802eec79a2dcf175b0ada50ddd203355a9c") || abort("EMMC:/dev/block/mmcblk0p7:5802240:3e8ba802eec79a2dcf175b0ada50ddd203355a9c:5843200:eba13a62d5c0f2192dcad85e1f43338ecc7c7863 has unexpected contents.");
[not rooted--cannot access protected file/partition]


Selected file to process:
/storage/sdcard0/Download/MG5_to_ND4_Update_TWRP.zip
================
Analysis
================
statements read: 1550
expressions processed: 391
true statements: 389
false statements: 2
inaccessible count: 0
- there were (2) failed expressions encountered (see details above)
Device information:
Device: goghvmu
Maker: samsu


This was the same result as the non altered update he first provided.



I tried installing the non altered update from stock recovery and it failed.


The altered update immediately had a "signature verifcation" error but continued the process. There was no status bar to speak of but some text went by and it said that the update was installed from sdcard...maybe it took?


I'm currently looking for a way to verify...

Edit:

The samsung updater through google services is still showing that I have the system update available so I assume that it did not work. Hmmm..

 

[Madbat]

Your phone must not be stock mg5 for the update to take. What is your build/baseband number? If it ends in mg5 This backup I have will put you to STOCK rooted mg5. Stock-MG5
https://drive.google.com/folder/d/0B7FbX6-171skclBLaGVNSFBVbEU/edit
Restore as you would do your own twrp backup. Then the update I linked will work (the no props one). Its how I did it. I was assuming you were already stock mg5.


Edit: I just saw that you said update was successful. Check in settings/about phone/baseband and also build to see if they end in nd4. If they do, the update worked and no further action is needed.

 

[ZROE01]

Im reading L300VPAMG5

Going to download your stock and go from there. Headed to work for ten hours but I'll update as available. Thanks so much for everything. Have a great day!

Do I download all of those files into a zipped folder? What of them actually gets flashed

 

[Madbat]

You can put those files into one of your TWRP backup folders, replacing the ones in there. Or make a new folder in twrp/backups/"serial number"/ "put files here". You can also make a backup of only boot, then go to that folder and delete what is in it and put the files there. You just need them in that path, twrp/backups/serial number/name of backup. Serial number will be you phones serial number, that's why its easier to make a small backup (boot or cache) to let twrp make the folder for you. DON'T flash the file, RESTORE it as you would your own backup. You need all of the files, its a complete backup.
Let us know how it goes. A few people have used this backup when they couldn't narrow down which file was stopping the update.

Here I put them all in one folder Stock-MG5
https://drive.google.com/folder/d/0B7FbX6-171skclBLaGVNSFBVbEU/edit if it makes it a little easier. Just put folder into twrp/backups/serial number/ . then just restore MG5 in twrp.

 

[scary alien]

ZROE01,

In this AF post by g60madman, he details the partition layout for your Victory:

/dev/block/platform/msm_sdcc.1/by-name:

aboot -> /dev/block/mmcblk0p5
backup -> /dev/block/mmcblk0p20
boot -> /dev/block/mmcblk0p7 this is the boot partition
cache -> /dev/block/mmcblk0p17
efs -> /dev/block/mmcblk0p11
fota -> /dev/block/mmcblk0p19
fsg -> /dev/block/mmcblk0p21
grow -> /dev/block/mmcblk0p23
modem -> /dev/block/mmcblk0p1 this is your radio (I'm assuming)
modemst1 -> /dev/block/mmcblk0p12
modemst2 -> /dev/block/mmcblk0p13
pad -> /dev/block/mmcblk0p9
param -> /dev/block/mmcblk0p10
persist -> /dev/block/mmcblk0p16
recovery -> /dev/block/mmcblk0p18
rpm -> /dev/block/mmcblk0p6
sbl1 -> /dev/block/mmcblk0p2
sbl2 -> /dev/block/mmcblk0p3
sbl3 -> /dev/block/mmcblk0p4
ssd -> /dev/block/mmcblk0p22
system -> /dev/block/mmcblk0p14
tz -> /dev/block/mmcblk0p8
userdata -> /dev/block/mmcblk0p15

So, I'm guessing at some point you've updated your boot.img and your radio, which is why you're still seeing OTA Verifier point-out mis-matched SHA1 sums for those components.

It looks like Madbat's got the con (most appreciated! :thumbup so I'll hang back for now.

Cheers!

 

[Madbat]

Scary Alien, your help is appreciated as well. I had the victory for about a year and my wife still has 1, so I have all the files and links for it. I like helping when I can. Folks here helped me when I needed it, so I enjoy doing the same.

 

[ZROE01]

Well gentlemen...IT WORKED!!!

I cannot believe it(though I knew it was possible)

This has been such a bothersome occurence in the last few weeks I had almost decided to abandon ship and get a new phone(s)...now if there was some way to get around VM throttling me past 2.5gb/month(hah!)

Although, I've always been a believer that when it comes to computers if it's not hardware related, it's fixable.

I don't know for the life of me what the hell could have happened.

Maybe in flashing around custom roms and creating backups/restoring backups I replaced the essential files as you had broken down there in that listing, Alien.

Either way I'm staring at baseband and build both ending in ND4 after it successfully took, no updates available and I can finally move on to any other number of projects on my to-do list.

I wish I had some way to thank the both of you beyond my eternal gratitude, my lady will be so happy the prompt will finally leave us be...maybe we can send you some cookies as thanks

You are both true altruists, enthusiasts, and humanitarians. I hope karma rains plentiful upon you.

Hopefully this thread will save some other poor sap a lot of frustration in the coming weeks.

 

[Madbat]

Glad it worked for you. Remember not to restore any of your old twrp backups, as they are no longer compatible. Make a new backup now. This will be your stock backup for future endeavors. Again, MAKE A BACKUP NOW! Lol. Have fun bro.

 

[ZROE01]

Perhaps I spoke too soon...

Was setting up my new flash of cataclysm rom and the prompt popped up, same 88.2mb update...

now what! @_@

I did let it download and restart, it rebooted, flashed a quick appearance of an install in TWRP and rebooted, now nothing is there. IDK what that was, here's hoping it was just some fluke leftover

 

[insanelycool]

Perhaps I spoke too soon...

Was setting up my new flash of cataclysm rom and the prompt popped up, same 88.2mb update...

now what! @_@

I did let it download and restart, it rebooted, flashed a quick appearance of an install in TWRP and rebooted, now nothing is there. IDK what that was, here's hoping it was just some fluke leftover

Did you flash cataclysm? That is an MG5 ROM, it's not compatible with ND4... so that's why you got the update message.

We cannot go back from here, only forward.

 

[ZROE01]

Sure did and that never dawned on me. I'm still showing my baseband as nd4 though so I'll just load that recovery after the initial fix and leave it be.

Thanks for that

 

[ZROE01]

As if I haven't demonstrated enough foolishness here in the last day...

The recovery I created after getting the nd4 update completed, has had me stuck at the Samsung bootlogo for about 30mins, I take it that's not normal.

Could I have done something wrong in creating that recovery?

 

[insanelycool]

Sure did and that never dawned on me. I'm still showing my baseband as nd4 though so I'll just load that recovery after the initial fix and leave it be.

Thanks for that

I am a big fan of Cataclysm as well... Moonknightus did an amazing job with that ROM. I am looking into doing something similar for ND4, but I've been reluctant to say anything since I've been really busy lately. I've barely had time to even work on the kernel improvements that are on my agenda. Even Nick seems to be pretty busy lately, but we've been chatting about collaborating on CM or the like. I still think I can bring some improvements to the kernel if I can ever find the time I need to research and implement some better memory management.

I love this phone, but it regularly slows to a crawl at times (if I run a lot of apps and such and leave the phone running for long periods) and it drives me crazy! Here's hoping I can find some time On the bright side though, I'm not planning to jump ship for any phones currently on the market, so my priority is to maximize what this phone is capable of.

 

[insanelycool]

As if I haven't demonstrated enough foolishness here in the last day...

The recovery I created after getting the nd4 update completed, has had me stuck at the Samsung bootlogo for about 30mins, I take it that's not normal.

Could I have done something wrong in creating that recovery?

Did you wipe cache and Dalvik? If so, then you will probably want to download the stock ND4 backup HERE.

 

[ZROE01]

I had not wiped the dalvik nor regular cache, silly me.

It is a shame cataclysm doesn't work with this at present but hey, if it's meant to be at the graces of the guru's, so it shall. I'm a little sad there's no cynogenmod after having a virgin mobile triumph running that for like 2years. It was so clean. I don't really want to upgrade anything either myself, with these new data caps an s3/4/5 is going to mow through the cap if I have that kind of processing power.

I'll try that stock ND4, was actually about to just update the other 2 victories I have and re-backup them and see if that worked. Either way, thank you.

Edit:Yep that ND4 took you provided. Thanks!

 

[loseallthegames]

Not to necro an old thread, but is the MG5 to ND4 update the update for a rooted phone?

I currently have a rooted victory, and I want to install the newest system update.

I see that you posted some links earlier, but I just want to make sure updating will not brick my phone (or unroot).

I created a backup with TWRP just now.
Can you relink me a flashable install that will allow me to utilize the update without having to re-root my phone?
Also, I was hearing that even a recovery would not restore nd4 BACK to md5?